scottdog129
Member
And afterwards I should be able to root using the previous method?
DroidForums.net | Android Forum & News
This is a sample guest message. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!
Downgrade to 902 - No app or data loss
- Thread starter SamuriHL
- Start date
And afterwards I should be able to root using the previous method?
Theoretically, but, again, I wasn't the one thinking this is going to fix that for you.
I don't have any idea what's causing that issue for you. But it's worth a shot at this point. Alternatively you could root now on 905 with motofail, install voodoo rootkeeper, and see if it'll keep root through the update. That'd be my recommendation.Seriously .. thank you for this thread and for all the support you've given since you started it. Really awesome.
I ended up here because I stumbled my way into a mess when I attempted to follow some guide to root that involved editing the /system/mount_ext3.sh. Something went wrong and I couldn't get past the big red M splash screen. I could get RSD lite to see the phone, but I couldn't figure out how to get ADB to see the phone in fastboot .. maybe it's not supposed to. Anyway, another friendly fellow recommended I give this a try so I did (sort of). Here's what happened..
Since my phone was not bootable, I started from the fastboot screen and ran everything from there. All was grand until I got to the part where I boot into recovery and apply the updates from the SD card. I either missed those parts of the nistructions, or because my phone was not bootable, getting the updates onto the sd card didn't work. So I powered down, pulled the battery, put my sd card into a friends phone, moved the updates to the sd card and went back into recovery mode to apply the updates. For some reason the recovery mode wouldn't mount the sd card and I was not able to apply the updates. I don't know what's up with that.
I rebooted the phone and lo and behold the phone booted up just fine. I'm 5.9.902_XT875, no data lost. Thank you Samuri!
It does seem a tad glitchy .. the Google Play process has been force closed several times .. and the screen has flickered once or twice as though some message were flashed for a nanosecond.
Given the process didn't run as expected .. probably because I messed it up and started from an unknown state, what would you recommend I do from here?
I ended up here because I stumbled my way into a mess when I attempted to follow some guide to root that involved editing the /system/mount_ext3.sh. Something went wrong and I couldn't get past the big red M splash screen. I could get RSD lite to see the phone, but I couldn't figure out how to get ADB to see the phone in fastboot .. maybe it's not supposed to. Anyway, another friendly fellow recommended I give this a try so I did (sort of). Here's what happened..
Since my phone was not bootable, I started from the fastboot screen and ran everything from there. All was grand until I got to the part where I boot into recovery and apply the updates from the SD card. I either missed those parts of the nistructions, or because my phone was not bootable, getting the updates onto the sd card didn't work. So I powered down, pulled the battery, put my sd card into a friends phone, moved the updates to the sd card and went back into recovery mode to apply the updates. For some reason the recovery mode wouldn't mount the sd card and I was not able to apply the updates. I don't know what's up with that.
I rebooted the phone and lo and behold the phone booted up just fine. I'm 5.9.902_XT875, no data lost. Thank you Samuri!
It does seem a tad glitchy .. the Google Play process has been force closed several times .. and the screen has flickered once or twice as though some message were flashed for a nanosecond.
Given the process didn't run as expected .. probably because I messed it up and started from an unknown state, what would you recommend I do from here?
You mixed ICS data with GB at this point which is something I highly recommend against. IMO, I would recommend a full FXZ back to 902, 905 update, then 232. The full FXZ WILL wipe your data and put you back to factory defaults. That's really the safest way at this point.
I am not sure if this has been mentioned or not, but if your flashing to 232 and you disabled apps in 230, re-enable them before flashing or else you won't be able to update. I didn't know until I found this thread. http://www.droidforums.net/forum/droid-bionic-tech-support/198293-update-failure-due-missing-corrupted-system-files-your-rooted-fix.html
I FXZ back to 902, but I still get the same error message assert failed: mount ("ext3.... etc) when trying to update to 905 via the batch file. Any suggestions?
I FXZ back to 902, but I still get the same error message assert failed: mount ("ext3.... etc) when trying to update to 905 via the batch file. Any suggestions?
Last edited:
That's not exactly true though. True, it won't update if you've uninstalled stock apps but if they are frozen (disabled) it should still work fine. I had at least 5 or 6 frozen when I did my upgrade and had zero problems.
I also had lots of frozen apps and without unfreezing went from 2233 to 230 to 232 without wiping data.
Sent from my DROID BIONIC using Tapatalk 2
Now that you mentioned it, I think I may have uninstalled an app?
Same here. I haven't unfrozen any of the bloatware using my script and I've had no problems. That mount_ext3.sh file, however, has nothing to do with freezing or unfreezing apps....that is SOLELY a forever root thing and it MUST be fixed before the update will apply. Trust me, I had to do it to my own phone when I went from 905 to the first leak. Also CWR/SafeStrap/etc must all be removed.
Sorry I am a total noob when it comes to rooting the Bionic, this is actually my first root, how would I go about fixing the mount file?
I was reading a post on android central about someone having the same problem and you actually telling them how to fix it. Quick question, I would need to purchase root explorer to modify the the chmod lines? Or did I look up the wrong root explorer?
I was reading a post on android central about someone having the same problem and you actually telling them how to fix it. Quick question, I would need to purchase root explorer to modify the the chmod lines? Or did I look up the wrong root explorer?
Last edited:
I think ES File Explorer also has the ability to use root to modify system files. But yes, follow my instructions or find an unmodified version of the file kicking around and simply replace it. Or run my script.
Haha I had the problem when I ran the script =(
@aceman1ac - I would say that if you are very new to rooting and flashing you definitely want to use SamuriHL's script. I am almost positive that it will fix your previous root issues and get you where you need/want to be. Follow the instructions to the letter and you will be golden.
EDIT: Just saw your post ^^^. You may be looking at a full FXZ if the script didn't work for you unfortunately. I really did think that it fixed the forever root files though...
EDIT: Just saw your post ^^^. You may be looking at a full FXZ if the script didn't work for you unfortunately. I really did think that it fixed the forever root files though...