Related
Hey, there seems to be a few of us(or maybe it's just me) confused about how we can root after the new update.
I just wanted to know if there was a confirmed safe way to restore root.
Thanks
Update:
Thanks to superkev. Manual way works. I can also confirm it also.
Also remember to keep your phone awake (ie. not in the locked screen)
superkev said:
I tried the manual instructions from here: http://briefmobile.com/motorola-atrix-4g-root
Step 6 failed for me, possibly because I had used this method to root 2.3.4. The rest of it went perfectly. I think the 2.3.6 update changed the permissions of the su binary, so these instructions just reset that to what they're supposed to be. I am rooted again!
Click to expand...
Click to collapse
I can't seem to find any root information on bell atrix 2.3.6 either.
saw some unconfirmed reports that superoneclick worked, but it doesn't work for me just sits at "Failed to set prot mask"
and then "WaitforDevice" forever...
if anyone has legit root info for the bell atrix 2.3.6 posting it would be greatly appreciated.
All I want is to install it! But im in usa so I need someone to make a fruitcake of it for me. Oh and I have also read super one click is supposedly working for some.
Sent from my MB860 using Tapatalk
I've got super one click working but superuser keeps denying all my root permissions without giving me a prompt.
DANGER!
So I tried SuperOneClick 2.3.1 and got my Bell Atrix 2.3.6 rooted.... all seemed good and Root Checker told me I was rooted. Light Flow got Super User permission and I thought I was gold!
Then my phone started freezing up and rebooting. Now I can't use the phone because it is crashing every 30 seconds. I would say avoid SuperOneClick (at least this version) for now!!
Oh, and SuperOneClick won't unroot my device so I'm kind of stuck. I would rather not reset my device and have to reinstall all my apps (which are backed up with Titanium Back-up, but which of course needs root to work...).
I'm just trying GingerBreak to unroot so we'll see how that goes.....
---------- Post added at 02:51 AM ---------- Previous post was at 02:44 AM ----------
... OK... so GingerBreak unrooted my phone but it is still completely hooped and the crashing woes continue... anyone with a solution on which system files I might be able to replace to fix this?!?!?
Aaaarrrg!
I tried wit Pete's first and it failed but super one click worked right from the first attempt. Before doing that though, I did a factory reset and started from scratch. Then I restored my apps only with TB. All is OK except that in market my apps list is empty with a message saying that my purchased apps will appear here. I have read that it is a known problem, but not necessarily with this update or because of rooting. In my experience super one click has otherwise been OK. Hope that helps. Don't have a solution for you except maybe trying to do a factory reset first if you are able to and then try again.
Sent from my MB860 using xda premium
Hey thanks. Yes, I ended up having to do a reset from the boot menu (power+vol down) and do an 'Android Recovery' which apparently wipes the system files and reinstalls the OS. My TB backups are still sitting on the internal SD but I am hesitant to re-root so I can reinstall TB and restore... what build of SuperOneClick did you use?
I tried with SuperOneClick 2.3.1.0 (latest). It says that it worked, but even after rebooting, my apps are being denied root access.
UPDATE:
I tried the manual instructions from here: http://briefmobile.com/motorola-atrix-4g-root
Step 6 failed for me, possibly because I had used this method to root 2.3.4. The rest of it went perfectly. I think the 2.3.6 update changed the permissions of the su binary, so these instructions just reset that to what they're supposed to be. I am rooted again!
I just updated to 2.3.6 and used the Briefmobile method to root and can also confirm that it is working. I had previously used this method to do 2.3.4 and had no issues on 2.3.6. Cheers
I might caution those who are not on AT&T about using the "manual" root method from BriefMobile. It was built with AT&T 2.3.4 files. Flashing the root.img in fastboot flashes those files to your /preinstall folder possibly hosing your Bell specific files. This has in the past, and possibly could in the future cause issues when trying to install future updates.
For those of you who have done it, can you look in /preinstall/md5 and see if you have att files?
Sent via 2.3.4 Rooted/Unlocked Moto Atrix using Tapatalk
superoneclick 2.3.1.0
this works flawlessly and on first attempt. so easy!
gingerbreak 1.2 didn't work this time, but it was useful to me for unrooting.
just make sure you do that before installing the update, and follow the superoneclick instructions.
too early to comment on battery life, and other than the keyboard I don't notice any aesthetic changes.
bell atrix
Remember to flash back the original preinstall image to avoid update issues.
Cheers!
das8nt said:
For those of you who have done it, can you look in /preinstall/md5 and see if you have att files?
Click to expand...
Click to collapse
That directory does contain some ATT and Cingular files. However, I used this method to root 2.3.4 and it didn't prevent me from installing the 2.3.6 update. I'm hoping I won't have any trouble going to ICS (fingers crossed that such a thing will even happen!)
superkev said:
That directory does contain some ATT and Cingular files. However, I used this method to root 2.3.4 and it didn't prevent me from installing the 2.3.6 update. I'm hoping I won't have any trouble going to ICS (fingers crossed that such a thing will even happen!)
Click to expand...
Click to collapse
Good deal. I had to help a few revert that folder when updating from 2.2.2 to 2.3.4 due to missing the gameloft stuff, but if it didn't effect your update that's good news.
Just in case, here's the 2.3.6 Bell stock preinstall.img to flash via moto-fastboot (thanks to NFHimself's new Gobstopper): http://www.megaupload.com/?d=C098P9IV
Sent via 2.3.4 Rooted/Unlocked Moto Atrix using Tapatalk
I used the manual way to root with the 2.3.6 update but TB is saying it can't can't gain root access and su keeps fc'ing on me. Anyone have any ideas what could be causing this? I also tried the superone click method but during the exe install on my pc it keeps stopping saying i don't have an internet connection????
j7logan said:
I also tried the superone click method but during the exe install on my pc it keeps stopping saying i don't have an internet connection????
Click to expand...
Click to collapse
that's weird. you definitely don't need internet access to perform the root (i was offline), provided you have superoneclick and phone drivers installed i'd say. does the driver check feature complain about it too?
Yeah, i thought it was strange too. It doesn't give me that error with the driver check, only when it is going through the install process of the exe.
Sometimes you need to treat your phone like a computer when it starts acting weird, save yourself some hassle and just do a format/factory reset and start fresh.
i used Doomlord's Rooting Toolkit: http://forum.xda-developers.com/show....php?t=1319653 it worked in 30 sec
Link to the exact Superoneclick you used? I tried the Doomloader link but it's broken.
Today someone asked me to help him. He said when he tried to root, it told him he was already rooted and when he tried to unroot, it said he wasnt rooted. Also 8 failed boot factory reset showed no changes except would result in hang from nook Zergy. I offered my services because I was in town. This is how I got his device working and what I went through. Maybe this will help you.
Story: This guy got his nook tablet from craigs list and it still had all the previous owners information on it. So, not knowing any better, they just went to the menu and used the factory reset option on a rooted device. This caused a wipe, but there were problems. All the personal info was gone, but when trying to reroot with nook zergy, either the script froze or said it was already rooted. After doing the 8 failed reboots- the same happened. Over the next few days I am going to try and video tape this and see if I can recreate it and show you all step by step how to fix it.
Symptoms:
Nook zergy script failing half way or saying already rooted even though there are no root apps or SU after full wipe
What I tried: I tried 8 failed boot reset to fix and it would not completely wipe the root, for some reason, something was still there telling the zergy script that it was still rooted, or would allow initial script to run and freeze
What worked: So, since something still thinks it is rooted and I cant use the unroot app unless there is a super user app to gain permission, the only solution was to download the super user apk, sideload it and then sideload and run the unroot script. After this is done, the unroot script can then get superuser permissions to fully unroot the tablet so the scripts can fully run again. This worked Flawlessly
I hope this helps you, I am going to try to replicate this and shoot a video of it over the next few days.
This Also Seemed to Work...
My root went through fine, but after the root my "n" buttom quit working and
I wound up in almost exactly the same place as above. I got out of it by:
1) Downloaded the "acclaim_update.zip" image found in the thread about Nook 1.4.0 from SDCard above, putting that on an SDCard and the rebooting to run and load it. When it first rebooted, the "n" worked but as is typical with Android
there were "leftovers" (files, etc.) still left from the previous installs.
2) So I went in to Settings and ran the "Erase and Deregister" option which seemed to clean out the leftovers and leave everything where it should have
been.
Hope this helps someone else.
Rev
albertwertz said:
What worked: So, since something still thinks it is rooted and I cant use the unroot app unless there is a super user app to gain permission, the only solution was to download the super user apk, sideload it and then sideload and run the unroot script. After this is done, the unroot script can then get superuser permissions to fully unroot the tablet so the scripts can fully run again. This worked Flawlessly
Click to expand...
Click to collapse
This fix worked for me as well.
I had my tablet rooted and when the ota got pushed out it broke my root. So I went back to 1.4.0 and re-rooted. But the script died halfway through and had the same symptoms listed above. Not fully rooted, but not fully unrooted either.
I had to sideload the superuser app and then unroot. Then start the root process all over again.
Unroot NT but it stops in the registration
I unroot the tablet with the file acclaim, but when i go to the registration come out the error"sorry we're having trouble setting up your nook.please shutdown the device and try again".I try hard reset more times but nothing.Can i by-pass the registration or root the device at start?
andrea89 said:
I unroot the tablet with the file acclaim, but when i go to the registration come out the error"sorry we're having trouble setting up your nook.please shutdown the device and try again".I try hard reset more times but nothing.Can i by-pass the registration or root the device at start?
Click to expand...
Click to collapse
Albert Wertz posted a video showing how but I'm not allowed to post outside links yet. Go to youtube and search for this video: sAASnHPn4PM
albertwertz said:
Today someone asked me to help him. He said when he tried to root, it told him he was already rooted and when he tried to unroot, it said he wasnt rooted. Also 8 failed boot factory reset showed no changes except would result in hang from nook Zergy. I offered my services because I was in town. This is how I got his device working and what I went through. Maybe this will help you.
Story: This guy got his nook tablet from craigs list and it still had all the previous owners information on it. So, not knowing any better, they just went to the menu and used the factory reset option on a rooted device. This caused a wipe, but there were problems. All the personal info was gone, but when trying to reroot with nook zergy, either the script froze or said it was already rooted. After doing the 8 failed reboots- the same happened. Over the next few days I am going to try and video tape this and see if I can recreate it and show you all step by step how to fix it.
Symptoms:
Nook zergy script failing half way or saying already rooted even though there are no root apps or SU after full wipe
What I tried: I tried 8 failed boot reset to fix and it would not completely wipe the root, for some reason, something was still there telling the zergy script that it was still rooted, or would allow initial script to run and freeze
What worked: So, since something still thinks it is rooted and I cant use the unroot app unless there is a super user app to gain permission, the only solution was to download the super user apk, sideload it and then sideload and run the unroot script. After this is done, the unroot script can then get superuser permissions to fully unroot the tablet so the scripts can fully run again. This worked Flawlessly
I hope this helps you, I am going to try to replicate this and shoot a video of it over the next few days.
Click to expand...
Click to collapse
Hi Albert
sorry to be bothering you , but i know your prolly the only one that can help me with this problem i have with my nook tablet
im replying to your reply :
so regarding this , im in need of your help here , same thing happend to me , didnt have superuser and was not fully rooted or not fully unrooted , but i did as you said i sideloaded superuser and unroot off this therd you posted and still the same probleam eco worked problem , what am i doing wrong ... the superuser doesnt seem to pop up when i run unroot ... how can i make superuser work properly ?
hope to can help
- Erik
Hopefully Albert has the answer for you. He's a clever one.
If this post helped click the thanks button!
Droid X2 owners i have figured out how to root the new 2.3.5/1.3.418 update. I spent a couple hours trying to get this figured out. Its simple and very easy to do well may not be for some but here you go just follow these simple steps and all that trouble that everybody is having.... here is the solution! First off do a hard reset from phones setting under privacy make sure to copy and paste pictures, music etc. to your computer cause you will have to check internal storage to be deleted for this to work ..after the reset u are going to sbf back to original 2.3.4 with (RSD Lite) Remember it has to be done in this order just take my word for it ...when finished.. phone will reboot let all factory apps download and install including gmail,
vz navigator, google books etc. You will not have to keep these apps you just have to let them install for this update after you sbf 2.3.4 and back to original. When your done with sbf file and have re-activated phone added google account etc... Get (Petes Motorola RootTools_v1.07.zip) no other rooting methods worked ive tryed it.. type that into google search it should find his site.. and make sure to download (Windows Universal drivers) for computer depending on what you have 32 bit operating system or 64 bit.. both of these files can be found on petes site. After downloading drivers and zip file..... unzip petes zip and click on (petes motorola root tools). I had one issue with this when trying to root device i had to put phone into pc mode for some reason. And if still having issues try running the adb temp rooting procedure this seems to work everytime. Run rooting method till done then u should be rooted after this is done dont mess with SU leave it as is for now.... Now you are going to want to head to the the google market on your phone and type (ota rootkeeper) and download that app. After this is done you can go to that app and and press protect root it should say something like su safe or something like that at the bottom after u have pressed it. Now when u are sure u have all these done correctly go to your phone settings and go to about phone and press on system update and download and install the OTA update 1.3.418 to your phone. It will reboot and and install update after this is done let phone load back up and do what it needs to do. Now go back to google market and install (ota rootkeeper) again and you should get only one option and that is to restore root.. press that and there you have it. Now you can update SU, remove unwanted apps, etc.. Do whatever you please. This update has caused so many droid x2 owners to get very ticked off but luckily i found the solution to all the problems. If anybody is having any issues trying to get this done leave posts and messages i will help you out as much as i can. This process went really smooth you should have no issues at all. And if ur wondering about 2.3.5/1.3.418 update it is definitely snappier with and even more snappier with bloatware apps removed. Install the droid X2 bootstrap manager just like u always would. Dont hesitate to leave questions i will try to get back to them as soon as i can. HAVE FUN ROOTING> 2.3.5 And by the way for the people wondering I run this all on stock rom I dont use eclipse, affinity , etc or any other custom rom this is all straight stock rom
ZergRush also works for 2.3.4
RacerXFD said:
ZergRush also works for 2.3.4
Click to expand...
Click to collapse
Heard zergrush changes something and won't let update work or something have to use Petes
Sent from my DROID X2 using XDA
2.3.5 ruined my root droid x2
Got my phone unrooted from this update. I SBFd it back to 2.3.4 in a similar manner using moonshadows post on how to do that. (Took forever) than I rerooted with Petes 1 click roo also downloaded voodoos rootkeeper. Moved it to SD card with TB backup Saved my root. Backed up all my stuff (including rootkeeper) with paid titanium backup app...booted phone on fast boot. Wiped files. Booted back up. Did all the updates than loaded rootkeeper(which was on my SD ccard. Restored root with no problems ran TB backup installed update to 2.3.5 angreat. everything is running great. Running stock ROM. Don't know much but can try to help. Not** I couldn't load my nandroid back up using Tom manager system recovery after update
Thanks for the help.
mnkurk1989 said:
Droid X2 owners i have figured out how to root the new 2.3.5/1.3.418 update. I spent a couple hours trying to get this figured out. Its simple and very easy to do well may not be for some but here you go just follow these simple steps and all that trouble that everybody is having.... here is the solution! First off do a hard reset from phones setting under privacy make sure to copy and paste pictures, music etc. to your computer cause you will have to check internal storage to be deleted for this to work ..after the reset u are going to sbf back to original 2.3.4 with (RSD Lite) Remember it has to be done in this order just take my word for it ...when finished.. phone will reboot let all factory apps download and install including gmail,
vz navigator, google books etc. You will not have to keep these apps you just have to let them install for this update after you sbf 2.3.4 and back to original. When your done with sbf file and have re-activated phone added google account etc... Get (Petes Motorola RootTools_v1.07.zip) no other rooting methods worked ive tryed it.. type that into google search it should find his site.. and make sure to download (Windows Universal drivers) for computer depending on what you have 32 bit operating system or 64 bit.. both of these files can be found on petes site. After downloading drivers and zip file..... unzip petes zip and click on (petes motorola root tools). I had one issue with this when trying to root device i had to put phone into pc mode for some reason. And if still having issues try running the adb temp rooting procedure this seems to work everytime. Run rooting method till done then u should be rooted after this is done dont mess with SU leave it as is for now.... Now you are going to want to head to the the google market on your phone and type (ota rootkeeper) and download that app. After this is done you can go to that app and and press protect root it should say something like su safe or something like that at the bottom after u have pressed it. Now when u are sure u have all these done correctly go to your phone settings and go to about phone and press on system update and download and install the OTA update 1.3.418 to your phone. It will reboot and and install update after this is done let phone load back up and do what it needs to do. Now go back to google market and install (ota rootkeeper) again and you should get only one option and that is to restore root.. press that and there you have it. Now you can update SU, remove unwanted apps, etc.. Do whatever you please. This update has caused so many droid x2 owners to get very ticked off but luckily i found the solution to all the problems. If anybody is having any issues trying to get this done leave posts and messages i will help you out as much as i can. This process went really smooth you should have no issues at all. And if ur wondering about 2.3.5/1.3.418 update it is definitely snappier with and even more snappier with bloatware apps removed. Install the droid X2 bootstrap manager just like u always would. Dont hesitate to leave questions i will try to get back to them as soon as i can. HAVE FUN ROOTING> 2.3.5 And by the way for the people wondering I run this all on stock rom I dont use eclipse, affinity , etc or any other custom rom this is all straight stock rom
Click to expand...
Click to collapse
The above instructions worked for me without factory resetting my phone and without wiping any of my data and thanks to those instructions, my phone is now rerooted with the OTA Update 1.3.418. I thank you for sharing with all of us.
1. DO NOT factory reset your phone or wipe your data.
2. Re-flash your DroidX2 with the sbf file and re-activate your phone.
3. Get Pete’s Motorola RootTools_v1.07.zip. To find it, search google to find his site. Make sure to download (Windows Universal drivers) for computer depending on what you have 32 bit operating system or 64 bit. Both of these files can be found on Pete’s site.
4. Install the Windows Universal Drivers, unzip Pete’s zip file and run Pete's Motorola Root Tools.exe. Wait for Pete’s root tool to finish.
5. Now that you are rooted again, go to the google market on your phone and search for ota rootkeeper. Download the app, run it, and press protect root.
6. Go to your phone settings and go to about phone and press on system update and download and install the OTA update 1.3.418 to your phone.
7. After the phone reboots, run the ota rootkeeper and restore root.
zergrush does not work on 2.3.5
tshelby73 said:
Heard zergrush changes something and won't let update work or something have to use Petes
Sent from my DROID X2 using XDA
Click to expand...
Click to collapse
zergrush does not work!! To all that that wondering why it dosent work it changes something in the build prop or local prop not sure but it does not work for rooting 2.3.5. And also.. For some people they may not have to do a internal factory reset, in my case i did for what reason.. i dont know. Every time i tryed installing OTA update it failed. For the people getting this error you will most likely have to reset your device and follow my instructions. PLEASE READ MY INSTRUCTIONS first before making any changes if u dont want to lose root lose saved music , apps etc.... Remember internal factory reset erases everything in internal memory. Move your things you want to save to ur sdcard
Thanks mnkurk! Saved me a lot of time - work right the first time and allowed me to fully restore my setup from titanium (with backup folder on the sd card).
Using voodoo root keeper to root 2.3.5 update has been known since the update came out.
zerg rush cant be used for a number of reasons,.some people might be able to get away with it, but a lot of times it will cause the 2.3.5 update tofail the signature check , it removes/changed files on system besides just su, to make room for root.
jagsil said:
The above instructions worked for me without factory resetting my phone and without wiping any of my data and thanks to those instructions, my phone is now rerooted with the OTA Update 1.3.418. I thank you for sharing with all of us.
1. DO NOT factory reset your phone or wipe your data.
2. Re-flash your DroidX2 with the sbf file and re-activate your phone.
3. Get Pete’s Motorola RootTools_v1.07.zip. To find it, search google to find his site. Make sure to download (Windows Universal drivers) for computer depending on what you have 32 bit operating system or 64 bit. Both of these files can be found on Pete’s site.
4. Install the Windows Universal Drivers, unzip Pete’s zip file and run Pete's Motorola Root Tools.exe. Wait for Pete’s root tool to finish.
5. Now that you are rooted again, go to the google market on your phone and search for ota rootkeeper. Download the app, run it, and press protect root.
6. Go to your phone settings and go to about phone and press on system update and download and install the OTA update 1.3.418 to your phone.
7. After the phone reboots, run the ota rootkeeper and restore root.
Click to expand...
Click to collapse
Some questions please...
After all these steps are done,
1. Will my sd card still have it's contents in memory?
2. Will all my programs will still be there?
3. I'm not sure how rooting and unrooting will affect already installed programs. Can you please expain.
Thanks for your help!
joliett said:
Some questions please...
After all these steps are done,
1. Will my sd card still have it's contents in memory?
2. Will all my programs will still be there?
3. I'm not sure how rooting and unrooting will affect already installed programs. Can you please expain.
Thanks for your help!
Click to expand...
Click to collapse
1 yes, does nothing to sd card, even if you wipe data in recovery
2 yes, if you don't bootloop and have to wipe data
3 no effect, once root is restored
The link to Droid X2 2.3.4 sbf is down
http://forum.xda-developers.com/showthread.php?t=1201534
Considering I have to flash my ROM i'd prefer a reliable source to get the file.
Edit:
Perhaps a little more browsing was in order, here a few sbf files from MoonShadow's X2 rooting thread
Moon Shadow - NM said:
a. Froyo 2.2.2 SBF File (you may have to right click and select "Save Link As")
b. Gingerbread 2.3.3 SBF File (you may have to right click and select "Save Link As")
c. Gingerbread 2.3.4 SBF File (you may have to right click and select "Save Link As")
Click to expand...
Click to collapse
Daerogami said:
The link to Droid X2 2.3.4 sbf is down
http://forum.xda-developers.com/showthread.php?t=1201534
Considering I have to flash my ROM i'd prefer a reliable source to get the file.
Click to expand...
Click to collapse
If you can get/have the 2.3.3 file, just flash that...then take the ota once and you will be on 2.3.4
should I root 2.3.3-> ota 2.3.4-> ota 2.3.5
or Flash 2.3.3-> ota 2.3.4 then Root-> ota 2.3.5
What is the benefit of going as far back as 2.3.3?
Daerogami said:
should I root 2.3.3-> ota 2.3.4-> ota 2.3.5
or Flash 2.3.3-> ota 2.3.4 then Root-> ota 2.3.5
Click to expand...
Click to collapse
Wait till 2.3.4 to root
No reason to root 233 it will just lose root when you ota any ways
Root .4
Then root keeper app
Then ota .5 and restore root with root keeper app
If going to flash a ROM after that, after you restore root, delete the su backup using the root keeper app before you flash the ROM or the rom flash will fail on ya
---------- Post added at 02:49 PM ---------- Previous post was at 02:45 PM ----------
Daerogami said:
should I root 2.3.3-> ota 2.3.4-> ota 2.3.5
or Flash 2.3.3-> ota 2.3.4 then Root-> ota 2.3.5
What is the benefit of going as far back as 2.3.3?
Click to expand...
Click to collapse
I don't know of there is any KNOWN benefit
But i know that before when i had a bunch of battery issues and other things acting weird, i went ALL THE WAY to froyo, then rode all the ota's back to 2.3.4 and things seemed better for me.
Take with a grain of salt tho, i never did any "official" testing on it., just know it fixed weird issues i had with device not sleeping properly.
i was just suggesting it cause it it's easier than having to find and then wait for 2.3.4 sbf file to download If you already had the 2.3.3 file
So, now there is a gray triangle in the top right (which apparently stands for roaming) I checked my phone status and it reads
Network: Unknown
My Phone Number: 000-000-7729
I went against your advice because I already had 2.3.4, but that shouldn't have caused this, right?
few options
reboot
wipe data or just cache in android recovery
dial *228
turn on airplane mode or turn on wifi then turn off, reboot
all SBF or here ezSBF/ RSD lite/ SBF/ drivers by 1KDS or here
Droid SBF files http://sbf.droid-developers.org/
edit: some people with issues, have reported had to wipe data before and after, and even flashing SBF twice, before getting it fixed
but the options I listed first usually fix network connection errors
not listed in any order, just as they popped in my head
As stated above
Just dial *228
Should fix that
it gives you two options i believe.
Do both if first doesn't fix it
Thanks so much! If i could thank you more than once I would!
I had to leave for work and I was so bummed out my phone wasn't getting service.
All I had to do was activate it
2.3.5 (Still wish it was ICS) and rooted!
Thanks again!
The above instructions worked for me without factory resetting my phone and
without wiping any of my data my phone is now rerooted with the OTA Update 1.3.418.
1. DO NOT factory reset your phone or wipe your data.
2. Re-flash your DroidX2 with RSDlite using the original sbf file.
RSDlite:
http://forum.xda-developers.com/attachment.php?attachmentid=784077&d=1321414457
My original flash file here:
http://www.general-files.com/downlo...Z_MB870_4.5.1A-DTN-150-30_1FF_01.sbf.zip.html
3. Re-activate your phone with *228.
4. Using Pete’s Motorola RootTools_v1.07.zip run Pete's Motorola Root Tools.exe.
Wait for Pete’s root tool to finish.
5. Now that you are rooted again, run ota rootkeeper, press protect root.
6. Go to your phone settings, About Phone and click on system update and
download and install the OTA update 1.3.418 to your phone.
7. After the phone reboots, run the ota rootkeeper and restore root.
jt
Rooted 2.3.4 to rooted 2.3.5
I'm on 2.3.4, rooted. I have downloaded but not installed 2.3.5. I previously froze, but didn't delete bloatware using Titanium.
Do you think I can just install rootkeeper, defrost bloatware, then install 2.3.5 & keep root?
I'm kind of an idiot trying to keep it simple.
Thanks in advance,
George
Success!!! This worked nicely. It just took a long time to defrost the bloatware, then freeze even more bloat when it was re-rooted as there was so much on there.
OTA Rootkeeper is a thing of beauty, it's fast & noob-proof. Thanks for that!
I upgraded to 4.0.3R5 a few weeks ago and rooted straight away. The rooting process didn't seem successful until I noticed Titanimum Backup saying I have Root. So I assumed I had and proceeded to restore a backup up my apps and re-install the missing ones from the store. I have now noticed when I power cycle I loose root. Power cycle again and I have root. Everything works fine (except stuff requiring root) until I go back to the Root version of the boot. I have noticed that when I'm on a rooted version I have 2 or more extra apps (the position of SuperSU moves to the next page) and using root explorer I notice my Vendor folder is there, it's missing when I boot and don't have root)
So any idea whats going on ? Is it and easy fix ?
Reroot I had no problems
Sent from my LT28i using xda app-developers app
defsix said:
I upgraded to 4.0.3R5 a few weeks ago and rooted straight away. The rooting process didn't seem successful until I noticed Titanimum Backup saying I have Root. So I assumed I had and proceeded to restore a backup up my apps and re-install the missing ones from the store. I have now noticed when I power cycle I loose root. Power cycle again and I have root. Everything works fine (except stuff requiring root) until I go back to the Root version of the boot. I have noticed that when I'm on a rooted version I have 2 or more extra apps (the position of SuperSU moves to the next page) and using root explorer I notice my Vendor folder is there, it's missing when I boot and don't have root)
So any idea whats going on ? Is it and easy fix ?
Click to expand...
Click to collapse
There are two system partitions.... system0 & system1.... seems yor tab does not like the rooted system so chooses to boot the normal system from time to time. Weird Try to reinstall the rom then reboot and see if your on the same one still. Then reboot couple of times and check.... then proced with root.
Mine was doing this I had r5 and r1a rooted.... it was a pain in the arse too
So do you think I could delete one of the systems?
I will stick it out until the next version is out if it's too much hassle.
Sent from my LT26i using XDA Premium HD app
Check out the all in one tool v5 when it comes out tonight my guess is itll fix ure problem!!
Sent from my LT28i using xda app-developers app
Will try at the wknd.
Sent from my LT26i using XDA Premium HD app
stifilz said:
There are two system partitions.... system0 & system1.... seems yor tab does not like the rooted system so chooses to boot the normal system from time to time. Weird Try to reinstall the rom then reboot and see if your on the same one still. Then reboot couple of times and check.... then proced with root.
Mine was doing this I had r5 and r1a rooted.... it was a pain in the arse too
Click to expand...
Click to collapse
So how do I reinstall the rom? mine came with R5 already installed.
Thanks.
[email protected] said:
So how do I reinstall the rom? mine came with R5 already installed.
Thanks.
Click to expand...
Click to collapse
Use AIO tool. 'Rescue back-door'. Then manually flash the file through recovery. Zip file link in signature and a FAQ including how to flash from recovery.
Well, the "Rescue back-door" was the reason I got to the 50% root in the first place...at least it seems like it. I had root working just fine, then tried "Rescue back-door" AIO 4.0 it asked for update, so I did it, and from that it went south.
Anyhow here are the steps I took to fix this :
I've used AIO 5.2 to unroot (had to boot twice to get to the rooted system), then let it download and install update, which it failed at the end as usual. Then started root process in AIO and during first reboot disconnected usb cable, because from previous experience AIO would fail because after first root it would start system without the previous root steps. Then rebooted tablet and plugged in usb cable, let AIO finish rooting and voila, root stayed after reboot, it fixed it.
I don't know if removing cable actually helped, or v5.2 has better rooting process then v5.0 had, or all this is irrelevant because I was messing with the tablet, flashing and trying and trying until it gave in...
[email protected] said:
Well, the "Rescue back-door" was the reason I got to the 50% root in the first place...at least it seems like it. I had root working just fine, then tried "Rescue back-door" AIO 4.0 it asked for update, so I did it, and from that it went south.
Anyhow here are the steps I took to fix this :
I've used AIO 5.2 to unroot (had to boot twice to get to the rooted system), then let it download and install update, which it failed at the end as usual. Then started root process in AIO and during first reboot disconnected usb cable, because from previous experience AIO would fail because after first root it would start system without the previous root steps. Then rebooted tablet and plugged in usb cable, let AIO finish rooting and voila, root stayed after reboot, it fixed it.
I don't know if removing cable actually helped, or v5.2 has better rooting process then v5.0 had, or all this is irrelevant because I was messing with the tablet, flashing and trying and trying until it gave in...
Click to expand...
Click to collapse
So after a few more days messing with this i'm still stuck. I booted into recovery , performed a factory rest, rebooted and did it again. Then I re-installed a full install of R5 , rebooted, factory reset. When I first boot I have (IRC) 30 apps, powercycle again I have 33 (IRC) apps, it appears I have extra ones that only appear in the vendor directory, again IRC. So rooted both partitions , double booting each time AIO said it was rebooting, I had root on both sides, however certain apps when started on the different partition were losing their settings. So with Root Explorer I decided to do a little trimming on one partition, I deleted the vendor and system folders and the tablet rebooted. So now I have one dead partition and one good. The good one works fine and is rooted, when I reboot it gets stuck in a boot loop at the Sony logo, press and hold the power button for a few secs and it reboots again , apps and settings unaffected.
So how do I have 2 partitions and how do i delete one ?
Greetings,
I know the easy answer to this is going to be to flash a new rom, but if I wanted to do that I would have already. I'd rather find and repair the source of the issue and learn from it.
That being said, shortly after getting my tbolt (when they were first released) I used the revolutionary root and added in VPN software for work. Being unaware that OTA updates hadn't been blocked during the rooting, the phone took an update and went into a death-boot-loop. I found a clean updated OTA rom, flashed and unrooted the phone as the VPN software didn't work well for what I intended anyway.
Great, now the phone is all back to stock (or so I thought).. After a while, another OTA update came down, it asked to update, I allowed, and it said update failed.. Repeat ad nauseum for the next several weeks. Since I was happy with the way the phone was operating, I didn't care if it got the updates or not.
So last week, I decided that since the phone is out of warranty anyway, I might as well root and get rid of some of the bloat, and while I'm at it, get rid of the damn nag screen every tine I hook it to a computer. Searched around, found thunderbolt tool 1.0.1, downed it and tried it out, and it proceeded to say unable to lock my phone.
After a little screwing around, the "update status" on the phone itself reports ROM Version: 2.11.605.9, while the tool was getting a response of 2.11.605.5, so it was using the wrong method to get into the phone. So I edited the batch file to use the .9 method no matter what it reported back, and it proceeded to root, add the recovery, and superuser.
Ahhh, life is good, the phone is rooted again, time to start doing my own customization.
Except that after a couple reboots, everything loses the root rights.
Running titanium backup says "asking for root rights" and then "titanium has been granted superuser permissions" but it just hangs there at the "asking for root rights" screen.
Wireless tether similar story... Start the app and it says "press to start tethering" and touching the screen gets "wireless tethering has been granted superuser permissions", then hangs at "please wait while starting".
Won't do anything that requires root, unless I run the tool again and select "S-off but no root", and it will go through a procedure and root will work again for a while.
Also, as I'm typing this, I discovered that it doesn't necessarily require rebooting to lose root. I had root working last night, but when I picked up the phone to get the proper messages to type, it is not showing root again, and it hasn't been rebooted since root was working.
Thoughts on how to repair this without flashing a rom?
Have you attempted to run the "fix permissions" option in your recovery?
If that does not help, You could use something like OTA RootKeeper to protect root, if you loose it you would just click one button to get it back.
Last thing I can think of is to just reflash the same ROM you are using now on top of what you have so you loose no data and any messed up settings or files will be rewrote.
**edit**
You should really think about installing a custom ROM, because until you do, or you block OTA updates, this will be a reoccurring issue.
You could easily install a stock rooted ROM of the exact same thing you have now. nothing would change except it would be properly rooted and OTA updates would be blocked.
That is because only temp root is applied to the official 605.19 Ruu. You need to downgrade back to 605.5 after getting temp root on the 605.19 Ruu then apply the perm root zip in recovery and then flash a newer rom from recovery. If that doesn't work don't lose hope. I may be misunderstanding the situation you have but it sounds like you're only applying temp root. The tool doesn't need to be edited and you may need to flash the 605.19 stock Ruu, relock and s on and then run the tool again.
Sent from my ADR6400L using Tapatalk 2
Milimbar said:
Have you attempted to run the "fix permissions" option in your recovery?
If that does not help, You could use something like -edit- to protect root, if you loose it you would just click one button to get it back.
Last thing I can think of is to just reflash the same ROM you are using now on top of what you have so you loose no data and any messed up settings or files will be rewrote.
**edit**
You should really think about installing a custom ROM, because until you do, or you block OTA updates, this will be a reoccurring issue.
You could easily install a stock rooted ROM of the exact same thing you have now. nothing would change except it would be properly rooted and OTA updates would be blocked.
Click to expand...
Click to collapse
Haven't seen the fix permissions option anywhere I've been, care to point me in the right direction?
I'll check out the rootkeeper.
disconnecktie said:
That is because only temp root is applied to the official 605.19 Ruu. You need to downgrade back to 605.5 after getting temp root on the 605.19 Ruu then apply the perm root zip in recovery and then flash a newer rom from recovery. If that doesn't work don't lose hope. I may be misunderstanding the situation you have but it sounds like you're only applying temp root. The tool doesn't need to be edited and you may need to flash the 605.19 stock Ruu, relock and s on and then run the tool again.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Never took the .19 update, and both the tool and phone report as .05 now. (if I remember correctly the .09 reverts back to .05 to get in)
damm315er said:
Haven't seen the fix permissions option anywhere I've been, care to point me in the right direction?
Click to expand...
Click to collapse
What recovery are you using?
I only use 4ext and would recommend that.
The fix permissions will take up to 5 min and may not help your particular issue, but shouldn't hurt to try.
If 4ext - Boot into recovery, select tools then select fix permissions.
If CWM I think its in the advanced menu.
and If TWRP I think it is in the advanced menu again.
Good luck and listen to the others here, they go out of their way to help people a lot
Ok earlier I misread your post. I thought it said 605.19. Still though something you're doing is causing you to only get temp root. Reread the op of the allinone tool and make sure you meet the requirements before you start it. That away when you run it this time you are in the best possible situation for it to work. Trter is very helpful and if you post your issue in his thread he will probably assist you with anything you need.
Sent from my ADR6400L using Tapatalk 2
I remember having a similar problem about 6-7 months ago.
I would randomly loose root, though not as often as he is describing.
In my case it was a combination of an outdated root method and a flawed ROM.
If everything he is using is current, including the ROM, he shouldn't have an issue.
If it were me I would flash Santod's stock deodexed ROM and be done with it.
It is the stock ROM with nothing changed except it is prerooted.
I understand that you would like to "fix" this issue without flashing a ROM, however the ROM itself could be the problem. this solution is the simplest I can think of.
Using everything from the thunderbolt toolkit, so yes, 4ext.
Found and ran the fix permissions, ran for 15 minutes before it finished so we'll see how it goes.
I get what you're saying about the rom being screwed up, and am starting to think my only choice is to reflash it, so I'll start looking into a new rom.. That being said I'm still pursuing fixing this until I find a rom that serves my purpose.
Is there a good stable ICS for thunderbolt, pre-loaded with root and good battery life?
Yea the one in the post above yours. If you want something a that is faster and has better battery than it then head over to infectedrom.com and check out all the different options santod has made.
Sent from my ADR6400L using Tapatalk 2