Related
basically every time i try to boot into the bootloader i am presented with a blank screen for about a minute then it reboots back into the OS
i tried letting RSD lite boot into the OS like i have done before but i just get a error
i have the exact same problem... please help!!!!
I don't have a milestone, but I presume the lumping w/ droid 1 is due to similarity
If you've got the "terminal emulator", you may try to do install the bootloader manually using "flash_image recovery /sdcard/recovery-0.99.3b.img"
You can find "flash_image" & lots of recoveries over here (thanks, ted!):
http colon slash slash ted dot servepics dot com slash nap slash droid
[sorry for the 'literals' -- board doesn't want me to post urls until I hit 8 posts in count]
Also, check to see if you'e got a file /etc/install-recovery.sh
IF that file does exist, make it do nothing or even not exist at all -- it reflashes the "stock" recovery, upon reboot. That was very, very annoying; Rom Manager should warn you about the existence of this file in your filesystem.
a_username said:
I don't have a milestone, but I presume the lumping w/ droid 1 is due to similarity
If you've got the "terminal emulator", you may try to do install the bootloader manually using "flash_image recovery /sdcard/recovery-0.99.3b.img"
You can find "flash_image" & lots of recoveries over here (thanks, ted!):
http colon slash slash ted dot servepics dot com slash nap slash droid
[sorry for the 'literals' -- board doesn't want me to post urls until I hit 8 posts in count]
Also, check to see if you'e got a file /etc/install-recovery.sh
IF that file does exist, make it do nothing or even not exist at all -- it reflashes the "stock" recovery, upon reboot. That was very, very annoying; Rom Manager should warn you about the existence of this file in your filesystem.
Click to expand...
Click to collapse
ROM Manager does not work on the Milestone, and I have never heard of a recovery_image file for the Milestone. It sounds like something Droid-specific. You have a Droid I presume?
Sent from my Milestone using XDA Premium App
yes, I do have a droid 1.
Hmmm, why'd they "lump us together" on this board - if we're so different?
When you say "rom manager" 'never worked' - what do you mean?
I prefer using flash_image via command-line - tells you when crud isn't working - but I'm a dinosaur unix geek. It was strange - took many attempts before the recovery flash_image succeeded.
I presume you have "root" - else you'd not be able to run "rom manager" at alll.
Check & see if there is a file "install-recovery.sh" is in your /etc directory - I dunno where I got this file, OTA or where -- it erased my bootloader/"recovery" on at startup after a second reboot.
There's got to be a reason they have droid 1 & milestone together - I could find this out - but eh, ask you anyways, increase my post count if nothing else: what processor does the milestone use? What kernel versions does it use?
a_username said:
yes, I do have a droid 1.
Hmmm, why'd they "lump us together" on this board - if we're so different?
When you say "rom manager" 'never worked' - what do you mean?
I prefer using flash_image via command-line - tells you when crud isn't working - but I'm a dinosaur unix geek. It was strange - took many attempts before the recovery flash_image succeeded.
I presume you have "root" - else you'd not be able to run "rom manager" at alll.
Check & see if there is a file "install-recovery.sh" is in your /etc directory - I dunno where I got this file, OTA or where -- it erased my bootloader/"recovery" on at startup after a second reboot.
There's got to be a reason they have droid 1 & milestone together - I could find this out - but eh, ask you anyways, increase my post count if nothing else: what processor does the milestone use? What kernel versions does it use?
Click to expand...
Click to collapse
Hardware-wise, Milestone and Droid are almost EXACTLY the same. That's why we are paired together. We have separate forums for development, but the General is for both phones.
It's what lies underneath the hardware that makes us so different. Your bootloader is unlocked, whereas ours on the Milestone is not. That allows you to flash custom kernels and modify the bootloader. Milestone users cannot. So we have to bypass that by hacking our stock Motorola recovery using a special sbf and then using a modded version of recovery called OpenRecovery.
I'm pretty sure the install-recovery.sh file that you have (we don't have it on MS), is because of an OTA update. There is a script I think that enables you to remove that script, as it checks for the version of the bootloader and might remove root, etc.
We cannot use ROM Manager or ClockworkMod, as they require an open bootloader. Many, many people have come into the forums and asked why their MS is bricked or bootlooping because ROM Manager isn't working for them. In that case, we need to reflash the 2.2.1 SBF, then flash the Vulnerable Recovery SBF and start over from scratch; A sort of "soft-brick".
Thanks for clarifying!
That SBF is flash-data for use w/ RSD-lite? I think I've had to use that to unbrick my droid, long in the past.
Is the bootloader the only difference? That is, after SBF flash, etc., milestone can run the same kernel as droid 1?
a_username said:
Thanks for clarifying!
That SBF is flash-data for use w/ RSD-lite? I think I've had to use that to unbrick my droid, long in the past.
Is the bootloader the only difference? That is, after SBF flash, etc., milestone can run the same kernel as droid 1?
Click to expand...
Click to collapse
Unfortunately, no. Flashing new kernels requires an unlocked bootloader, so we are stuck with the stock, Motorola-signed kernels.
Sent from my Milestone using xda premium
I claim no credit for this but after the 893 OTA you wont have root and you will have to go this way to get it back.
Original post I robbed this from [HERE]
You will need adb to do this. You can get the download here depending on your operating system. ADB
Download the follow file: it contains the exploit, su, Superuser
Download exploit -->Exploit.zip
1) Unzip contents of folder to your Desktop
2) open a command terminal and navigate to the folder (cd Desktop/Exploit)
3) type the following commands
---> adb push zerg /data/local
---> adb push su /data/local
---> adb push Superuser.apk /data/local
---> adb shell
---> cd /data/local
---> chmod 777 zerg
---> ./zerg
4) Wait for the root to be gained
5) type the following commands
---> adb shell (only type this if you are no longer in [email protected])
---> mount -o rw,remount /dev/null /system
---> cat /data/local/su > /system/bin/su
---> cat /data/local/Superuser.apk > /system/app/Superuser.apk
---> chmod 4755 /system/bin/su
---> chmod 4755 /system/app/Superuser.apk
---> reboot
This is from P3Droid.
Click to expand...
Click to collapse
Worked like a charm. Thanks!
want to do this for my brother, you just connect the phone to the computer with usb debugging mode enabled right?
Fyi if you correctly root and forever root prior to the ota you will retain root. The update does not remove root if it was forever rooted.
Sent from my DROID BIONIC using XDA App
I used this method on a used Bionic I bought that has 5.7.893. It worked perfectly.
Why do you guys make it so difficult? All you need to do is use R3L3AS3DRoot to restore, root, and forever root your Bionic. And, POW! You will have a rooted Bionic once again, without D/L unnecessary software and typing commands. Props to DHacker.
charlie310 said:
Why do you guys make it so difficult? All you need to do is use R3L3AS3DRoot to restore, root, and forever root your Bionic. And, POW! You will have a rooted Bionic once again, without D/L unnecessary software and typing commands. Props to DHacker.
Click to expand...
Click to collapse
Because R3L3AS3DRoot restores a 886 system and not an 893 system, which is the reason you would "D/L unnecessary software."
So, sure you'll be rooted with an 886 system which isn't current.
you forgot last step....then update and youll still have forever root
I restored and forever rooted my bionic, then did OTA, and still have root. I was on rooted stock previously, but restored because I wasn't able to get or pull the OTA update due to "error try again later".
Sent from my DROID BIONIC using Tapatalk
Terror_1 said:
Because R3L3AS3DRoot restores a 886 system and not an 893 system, which is the reason you would "D/L unnecessary software."
So, sure you'll be rooted with an 886 system which isn't current.
Click to expand...
Click to collapse
Let's think about this logically:
D/L and unzip R3L3AS3DRoot and use 3 clicks to restore/forever root your phone, then D/L the update using a 3 clicks.
Or, D/L and install ADB, D/L and install Java SE, and D/L & unzip the Exploit Zip and type in 15 command lines to root your phone.
It's pretty obvious what is considered easier and requires less unnecessary software.
BTW, if you are flashing a ROM, then option 1 is always the best way to go since you don't have to D/L the OTA update since most ROMs have the update built in (and you already have the updated radio).
getting replacement bionic for radio issues tomorrow hopefully. will i have to use this most likely or will it unrootable? any info would be great thanks!
charlie310 said:
D/L and unzip R3L3AS3DRoot and use 3 clicks to restore/forever root your phone, then D/L the update using a 3 clicks.
It's pretty obvious what is considered easier and requires less unnecessary software.
Click to expand...
Click to collapse
You forget that some of us already have all the prerequisites. I personally can't say if your method works or not. It failed several times for me, so I gave up and zerg worked.
luke1333 said:
getting replacement bionic for radio issues tomorrow hopefully. will i have to use this most likely or will it unrootable? any info would be great thanks!
Click to expand...
Click to collapse
I am partial to doing things manually myself but I guess 43v3r does it too.
I personally had no luck with it.
Sent from my DROID BIONIC using XDA App
what version could you not root?
Does zerg work on 5.9.901 ?
luke1333 said:
what version could you not root?
Click to expand...
Click to collapse
893 43v3r doesn't work on, if you restore the 886 then root you should be fine. Just doing the update then trying to gain root isn't going to work.
kris7778 said:
Does zerg work on 5.9.901 ?
Click to expand...
Click to collapse
I don't know for sure but I am pretty confident that it would.
THANKS!
Flawless victory!
Binarality!
Has anyone rooted a previously unrooted device running version 5.9.901? Who's process?
This method worked for me, but I notice that my 3g service was weak and my 4g was gone. Even if i restarted the phone I couldn't get my 4g to work. This was after the 4g issue with VW braking it. Has anyone else had this problem?
1 click method
is there any 1 click method out there that can be used to do this ,,i used 4ever root a couple of time to restore my phone after screwing it up .. but now even that wont work .. so yeah i have the update but no root ...no matter how i try to do it before or after ..
and i unfortunately do not know how to connect to adb to push anything to my phone .. im not that technical with it ....dont have a clue .ive tried but not easy for me that is thanking you in advance Robb
One question, if I update and then for any reason I can't get root can I go back to stock rom you know the one before ota and start over? ???
Sorry for my english lol
Sent from my DROID BIONIC using XDA App
Easy way to speed up your phone
Install instructions:
1. Install Root Explorer
2. Download boost.zip file and then unzip the that file and put in the SD card...
3. Open Root Explorer (Mounted on R / W) / SDCard / menu button / Multi-select / chose boost / Copy / system / bin / then click paste...
4. Open Terminal emulator and taype:
su
boost
5. Your phone is turbo boosted now, enjoy in new speed on your phone...
6. Press thanks if you like my work...
7. Rate my thread...
And what exactly does this "Turbo boost" do?
Have you got any benchmark results or evidence of an performance increase? I'm not giving an program/script root access to my phone, without some proof of an increase.
Upon opening the file with Notepad++ all it had inside was this
#!/system/bin/sh
# Adrenaline Boost
# Brought to you by [email protected] Developers
sync;
sleep 1
echo "3" > /proc/sys/vm/drop_caches;
sleep 1
echo "1" > /proc/sys/vm/drop_caches;
sleep 1
echo " ** Turbo Boosted ** ";
Click to expand...
Click to collapse
Which after some googling found out it does (from a similar script for desktop Linux):
Writing to this will cause the kernel to drop clean caches, dentries and inodes from memory, causing that memory to become free.
Click to expand...
Click to collapse
nejc121 said:
And what exactly does this "Turbo boost" do?
Click to expand...
Click to collapse
Your phone will be faster and working bether...
I just get permission denied in terminal.
spudata said:
I just get permission denied in terminal.
Click to expand...
Click to collapse
Did you type in "su" before "boost"?
Yes, granted su permissions but no joy.
Same thread posted on the i9000 development area. wth
Sorted, had to change permissions of boost file
Can anyone confirm this to work?
Sent from my HTC Desire using Tapatalk
RESERVED.
installed, will update tomorrow with any feedback.
UPDATE: have found it runs pretty much same as V6 Supercharger, drains battery horribly though.
I was on 54% battery last night, data & wifi off and killed tasks before going bed.. I checked CPU Spy, it had been in a deep sleep state for most of the night.
I awoke to a dead phone, which doesn't even happen on the v6 supercharger!
How do I uninstall this script, can I just delete the file from bin?
I tried this but I see no difference ... should i restart the device?
cm 7.2 rc1, smartassv2 264-710 MHz
edit: rebooted the phone....still no difference.....
To really see the benefits of the boost, you need to change the file permissions. Go into a root terminal and type:
chmod +t boost
This gives the boost Time Travel permissions. Now, all processes will be completed before you even run them. Talk about a turbo boost!!
Also set the date of your phone to whatever you want the open the dialer and type "#"#7925#"#" and you'll be timewarped into the future.
Sent from the year 2019 using my years old HTC Wildfire using xda premium
Ok just done a little digging around the op's other thread (which is now locked by a mod) on a different forum as he hasn't exactly explained what this does in any of them which leads me to believe he doesn't exactly know, and probably copied it from someone else, http://forum.xda-developers.com/showthread.php?t=1542602
What this does is clear the cache filesystem. 3 = free pagecache, dentries and inodes, while 1 = just free pagecache. Which in theory will decrease battery life as the cache needs to then be rebuilt afterwards.
This is already included in v6 supercharger so no need to use this if you have v6, just perform the engine flush or whatever its called whenever you want to free up some memory stuck in cache files. Its basically the same thing according to other users, I haven't looked to see if thats true or not but they sounded like they knew what they we're talking about so i believe them.
GlennBrownie said:
UPDATE: have found it runs pretty much same as V6 Supercharger, drains battery horribly though.
I was on 54% battery last night, data & wifi off and killed tasks before going bed.. I checked CPU Spy, it had been in a deep sleep state for most of the night.
I awoke to a dead phone, which doesn't even happen on the v6 supercharger!
How do I uninstall this script, can I just delete the file from bin
Click to expand...
Click to collapse
??
Yes delete and reboot.
Sent from my HTC Wildfire using xda premium
SeeZaar said:
Easy way to speed up your phone
Install instructions:
1. Install Root Explorer
2. Download boost.zip file and then unzip the that file and put in the SD card...
3. Open Root Explorer (Mounted on R / W) / SDCard / menu button / Multi-select / chose boost / Copy / system / bin / then click paste...
4. Open Terminal emulator and taype:
su
boost
5. Your phone is turbo boosted now, enjoy in new speed on your phone...
6. Press thanks if you like my work...
7. Rate my thread...
Click to expand...
Click to collapse
yea, 1star rated as u just copy my work.
Moreover, u didnt give full description and spoiled my fame and work, this should be useful for everyone if they know how to use tis properly
Thread closed as the OP DOESNT have permission fro yhe dev yo post this.
Also he failed to provide credits.
This on XDA is kanging and is not tolerated!!!
I used the bloat removal script after updating to 5.7.906.
It will give errors and reboot the device, but it does work with the update.
I ran both scripts by psuza4 under root using Script Manager. I suggest running both because I have no idea which one worked correctly as I wasn't paying attention.
Some apps are still left behind (ex: VCast Ringtones) but that can easily be removed with Titanium Backup.
Hope this helped!
Doesnt Work!
Both Bloat Removal Scripts (5.5.959 & 5.6.890) do not work on my Droid 3
I have the newest update (Deodexed XT862 .906 SAFE mode from Developer 'davros') which is 5.7.906 on my Droid 3...
-Im 100% Rooted (checked)
-USB debugging is on as well as unknown sources, etc.. (checked)
I have scriptmanager installed & Granted superuser permissions..
I run the scripts and they fail with error messages every time:
"Working, please Wait...
Failed on 'MyVerizon.apk' - Read-only filesystem
Reboot: Operation not permitted"
And I wait for a reboot and there no reboot. it just sits there. I exit script manager and nothing worked...
Ive tried this before on my non-deodexed stock .5.7.906 ROM too and had the same results.
Any help? I dont think im doing anything wrong. The script just doesnt work.
no idea if this will work but use root explorer an change directory to r/w? go into system/apps rename bloat to "bloat.apk.bak"?
missionman said:
Both Bloat Removal Scripts (5.5.959 & 5.6.890) do not work on my Droid 3
I have the newest update (Deodexed XT862 .906 SAFE mode from Developer 'davros') which is 5.7.906 on my Droid 3...
-Im 100% Rooted (checked)
-USB debugging is on as well as unknown sources, etc.. (checked)
I have scriptmanager installed & Granted superuser permissions..
I run the scripts and they fail with error messages every time:
"Working, please Wait...
Failed on 'MyVerizon.apk' - Read-only filesystem
Reboot: Operation not permitted"
And I wait for a reboot and there no reboot. it just sits there. I exit script manager and nothing worked...
Ive tried this before on my non-deodexed stock .5.7.906 ROM too and had the same results.
Any help? I dont think im doing anything wrong. The script just doesnt work.
Click to expand...
Click to collapse
It works fine on stock. However, you can read through the script file and just do the steps manually using a terminal app on the phone.
(In other words, if you want to remove the AdMob service, run the commands from the script:
mount -o remount,rw /dev/block/mtdblock3 /system 2>/dev/null
cd /system/app
mv AdService.apk AdService.apk.bak 2>/dev/null
mv AdService.odex AdService.odex.bak 2>/dev/null
Though, you can leave off the "2>/dev/null" part of those lines. If you get errors, just ignore them, or check for typos.)
Had the exact same issue as missionman on my wife's droid 3. Will not complete the script. Hope someone's got a good answer. I just have what I feel is bloat frozen currently.
Sent from my SCH-I535 using xda premium
Isnt DST more or less the same while having 906 in mind?
http://forum.xda-developers.com/showthread.php?t=1554916
Hi, everybody!
Several days ago i've got OTA update from VERIZON. You can download it from attach.
Changelog from official Motorola site
I agreed and installed this update. After it i had 98.72.18-8 SW version.
So, i have had the trouble: i couldn't got root rights by Dan Rosenberg exploit - Motorola fixed the way, we had root on previous JB 98.72.18 and 98.72.18-2 !
After analysing install-script file from OTA update and thinking around it i decided to downgrade with RSDLite to 98.72.18 and do some manipulations with SU binary:
Start point: 98.72.18-2 installed, rooted
Code:
adb kill-server
adb start-server
sleep 5
adb shell su -c "mount -o remount,rw /system"
adb shell su -c "cd /system/bin/ && mv run-as run-as2 && mv /system/xbin/su run-as" #because of script do chmod on this file
adb reboot recovery
#turn on Sideload manually in recovery
adb sideload Blur_Version.98.72.182.XT894.Verizon.en.US.zip
sleep 400
adb kill-server
adb start-serversleep 5
adb shell run-as -c "mount -o remount,rw /system" #i used RUN-AS instead SU =)
adb shell run-as -c "cd /system/bin/ && mv run-as /system/xbin/su && mv run-as2 run-as"
adb shell su -c "chmod 6755 /system/bin/su"
this way gave me root rights for adb Shell, but applications still not getting root.
Any ideas, how to fix?))
Sorry for mistakes, i've tryed to avoid it)
way to fix
So, i fixed it!
1. At the start, we have 98.72.182 system, rooted by Dan Rosenberg exploit
2. Installing Safestrap recovery
3. Downloading on sdcard-ext latest SuperSU
4. Under Safestrap, installing UPDATE-SuperSU-v1.89.zip
5. Reboot to stock Android, bying SuperSu pro key, installing
6. Going to settings, and uncheck Screen block (set NONE)
7. Going to Superuser -> settings, install checkboxes: Survival mode, Enable su during boot, Trust system user
8. Reboot to the stock recovery, installing OTA update
9. Booting to OS.... (After booting you can return screen block )
10. Enjoy!
Orrrrrrrr update su binaries and back up root with voodoo. Temp disable root install update then voodoo. Restore root and enjoy... now I can only say because this is what worked for me without all the extra hoopla
Sent from my DROID4 using Tapatalk
rruleford said:
Orrrrrrrr update su binaries and back up root with voodoo. Temp disable root install update then voodoo. Restore root and enjoy... now I can only say because this is what worked for me without all the extra hoopla
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
I can take a video with Vodoo, which will fail with restoring root.
Before posting, i've tryed voodo ota keeper, and ota keeper function in another superuser software)
Thanks for the heads up on the update breaking root. I'll have to wipe my phone and start fresh before I do the update......unless I go kitkat.
Update.....
I tried voodoo and the OTA would not come through for me. It looks like the update will be more complicated than it's worth so the kitkat rom's will be in my near future.
Voodooo worked for me on latest O.T.A
karlsdroids said:
Thanks for the heads up on the update breaking root. I'll have to wipe my phone and start fresh before I do the update......unless I go kitkat
Click to expand...
Click to collapse
Voodooo worked for me on latest O.T.A
rruleford said:
Orrrrrrrr update su binaries and back up root with voodoo. Temp disable root install update then voodoo. Restore root and enjoy... now I can only say because this is what worked for me without all the extra hoopla
Sent from my DROID4 using Tapatalk
Click to expand...
Click to collapse
mercermtn said:
Voodooo worked for me on latest O.T.A
Click to expand...
Click to collapse
Voodoo worked for me too. Just got the OTA notice today from VZW. Followed rruleford's steps and it worked.
This was my first time using Voodoo, and possibly my imagination or possibly not - but something funky happned where I needed to reboot the phone and re-check enable in SuperSU, which was obscured by the fact Voodoo was stating it ~had~ root...
So, is there anything besides these bugfixes in the update? Any Android version updates or maybe a fix for the Shift key behaving like a lunatic?
Dang.
My wife already applied the update to her D4 and now I've lost root on that device. Can anyone advise me what to do? Should I use RSDLite like OP states? I am confused because Moto SBF page says "never flash an older version"...
tried using voodoo and the update wouldn't work...dono what to do.
svrnmnd said:
tried using voodoo and the update wouldn't work...dono what to do.
Click to expand...
Click to collapse
Did you disable SuperSU after you backed up w/ Voodoo?
Negative, how do I disable? NOTE I use superuser not superuserSU
Sent from my DROID4 using xda app-developers app
svrnmnd said:
Negative, how do I disable? NOTE I use superuser not superuserSU
Sent from my DROID4 using xda app-developers app
Click to expand...
Click to collapse
Im not 100% sure w/Superuser - its probably similar: in settings uncheck 'Enable Superuser'
Also - if anyone out there has info on helping me w/ my wifes D4 here (a couple posts up) I would appreciate it...
bigmatty said:
Im not 100% sure w/Superuser - its probably similar: in settings uncheck 'Enable Superuser'
Also - if anyone out there has info on helping me w/ my wifes D4 here (a couple posts up) I would appreciate it...
Click to expand...
Click to collapse
Looks like you'll have to wait for a new method to be released orrrrr if another d4 is available that's rooted try downloading voodoo on both devices and backup root on rooted device then copy backup file to unrooted phones voodoo directory and try to restore that way and don't forget to update su binaries
Sent from my XT894 using Tapatalk
rruleford said:
Looks like you'll have to wait for a new method to be released orrrrr if another d4 is available that's rooted try downloading voodoo on both devices and backup root on rooted device then copy backup file to unrooted phones voodoo directory and try to restore that way and don't forget to update su binaries
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
Awesome - thanks for the reply! Yes, I have my D4 same as hers, working well and w/ a Voodoo backup... I had considered this, but couldn't find the Voodoo file backup location. Do you by chance know where it is?
Why are y'all struggling so much with this.
1. You don't need to unroot.
2. You don't need to unfreeze anything.
3. RAZR_BLADE root method still works. You have to clear cache and data and force close Smart Actions before re-rooting.
I've done three Droid 4's already. All had different apps/services frozen via Titanium Backup and all were of course rooted. One (mine) got the SOAK at version .188 and the other two got the roll out at version .189.
Install update, clear Smart Actions and re-root with the razr_blade method .bat files.
Simple, works and reauthorizing Titanium Backup will refreeze all the apps you had frozen before the update.
Sent from my Nexus 10 using Tapatalk
bigmatty said:
Awesome - thanks for the reply! Yes, I have my D4 same as hers, working well and w/ a Voodoo backup... I had considered this, but couldn't find the Voodoo file backup location. Do you by chance know where it is?
Click to expand...
Click to collapse
Not to sure as I deleted all mine when installing cm11 on stock ROM slot. Try above method with RAZR blade?
Sent from my XT894 using Tapatalk
tcrews said:
Why are y'all struggling so much with this.
1. You don't need to unroot.
2. You don't need to unfreeze anything.
3. RAZR_BLADE root method still works. You have to clear cache and data and force close Smart Actions before re-rooting.
I've done three Droid 4's already. All had different apps/services frozen via Titanium Backup and all were of course rooted. One (mine) got the SOAK at version .188 and the other two got the roll out at version .189.
Install update, clear Smart Actions and re-root with the razr_blade method .bat files.
Simple, works and reauthorizing Titanium Backup will refreeze all the apps you had frozen before the update.
Sent from my Nexus 10 using Tapatalk
Click to expand...
Click to collapse
On 1 & 2 - not entirely sure anyone said to unroot or unfreeze, but I did read where it was advised to 'temp disable root', and when I followed that step voodoo did work great to allow me to update and restore root.
THANK YOU for 3!! I assumed based on some of the other comments that it didn't work. I just tried it on the other phone, and it DID restore root. VERY MUCH appreciated!!
So I use voodoo to unroot I disabled superuser but the update starts and fails everytime, I don't know why, the little android starts to update, then just gets a red x through it...
Sent from my DROID4 using xda app-developers app
I have quite a few apps frozen, but apparently nothing that prevented the install from being downloaded automatically. I unrooted with Voodoo, installed the update, restored root and all is well.