Database Users

(Q) Phone says its rooted but its not...

Edit : just checked. My phone is running the newest updated but im gonna try to unroot and reroot one more time even though I already tried and it could not unroot.
So I went to install the new update via stock recovery and it seemed to work. I go check system settings and its still showing 2.3.2 and not the newest one. I go to try and root and it says everything works and my phone is rooted. Thing is there is no super user app that appeared on my last droid 2. What's the issue?
Sent from my DROID2 using XDA App

Try it again and use the 1 click root for 2.3.20 from here http://www.mydroidworld.com/forums/droid-2-discussion/5321-2-3-20-1-click-root.html

komputerfreek said:
Edit : just checked. My phone is running the newest updated but im gonna try to unroot and reroot one more time even though I already tried and it could not unroot.
So I went to install the new update via stock recovery and it seemed to work. I go check system settings and its still showing 2.3.2 and not the newest one. I go to try and root and it says everything works and my phone is rooted. Thing is there is no super user app that appeared on my last droid 2. What's the issue?
Sent from my DROID2 using XDA App
Click to expand...
Click to collapse
It might be that you just lost the app and just need to get it off the Market.

JDunc said:
It might be that you just lost the app and just need to get it off the Market.
Click to expand...
Click to collapse
Yeah, I saw it was rooted and just went to market and got Superuser app and installed, I have root. I don't know why it did not show the superuser app even thought it said the apk was transfered.

Mine did the same. After I rooted using the one click method, it said it was a sucess. Tried to use Root Explorer, and it said failed getting superuser permission. Checke my SD card, and there was no Superuser.apk there. I copied it to the SD card from the one click directory, and it was sucessful. When trying to use Titanium Backup, had trouble with Busybox. Titanium downloaded a new Busybox, and all is now well.
Sent from my DROID2 using XDA App

Can't Upgrade to 4.1.83 AT&T

Hello,
I have the version 1.4.57 with GingerBlur 2.5 and try update via OTA to version 1.4.83 and when you start the installation restarted fourth bar and it appears the doll with a warning sign and not much else happens, I have to remove the battery to power off and restart the operating system, anyone know how I can fix it?
Greetings!

Flash the sbf for 1.83 found here in the forums. Over in the development section there is a guide on flashing with Rsd lite.
Sent from my MB860 using XDA App

You cannot install the update over any mods, you have to sbf first.

And if I use the Restore GingerBlur Bloatware?

i had this same problem cause i was rooted, instead download the motorola updater on your computer and use that to update, then when its done your phone might say installation failed, but it actually really didnt fail, if you check the phone settings it shows your on 1.8.3 on 2.2, thaT WAY YOU STILL HVE ALL YOUR OLD APPS AND ETC.

unnkown95 said:
i had this same problem cause i was rooted, instead download the motorola updater on your computer and use that to update, then when its done your phone might say installation failed, but it actually really didnt fail, if you check the phone settings it shows your on 1.8.3 on 2.2, thaT WAY YOU STILL HVE ALL YOUR OLD APPS AND ETC.
Click to expand...
Click to collapse
Uh, but you don't know what may have failed about the update. Just cos the phone settings say 4.1.83 and 2.2.1 doesn't mean all is ok!
Also, you can update over root. You can't however update over deodexed files as with GingerBlur or GreyBlur!
OP, flash 4.1.57 sbf, then update OTA, or try flashing 4.1.83 sbf right off the bat, then Gingerbreak and install GingerBlur again.
Sent from WinBorg 4G using XDA Premium App

Um...where is the 4.1.83 sbf download?

Problems updating liberty

Hey, I'm on liberty 2.0.1and since the recent toolbox update, the file to update to rooted gb has been added to nightlies. I downloaded the file, but when I tried to install it, it says the phone will reboot into recovery and install, but my phone just reboots back to normal. I tried redownloading the file, but it just reboots normally. I've been having issues with my phone freezing lately, so I wanted to update to liberty gb. I tried to email jrummy and message him on twitter, but he never responds, which is **** customer service if you ask me. I just want to get my phone working again. Does anyone know about this issue? Any advice?
Thanks,
Garrette
Sent from my DROIDX using XDA Premium App

I'm not sure about that. You could always update to rooted/blured GB then load up liberty from there.
Sent from my Xoom using XDA Premium App

I did that last night. I had to SBF back to stock group though, reboot, then installed prerooted gb. Dl the Liberty toolbox, dl nightly version gb. O9, and it STILL DOESN'T FREAKING WORK!!!!!!!!
It still doesn't reboot into recovery and just restarts the phone normally. Can I just use bootstrap and install the file from there?

yes, u can use bootstrap

Help new update wont install

I have my rooted transformer and am trying to update but stow a quarter way throught the install and gives me an android Guy with a triangle with a "!" Sign in it... stock everything just rooted please help
Sent from my GT-I9000 using XDA Premium App
Fixed!!!!! I used Brks Asus transformer rootkit script to root which installs an insecure bootimage to work and this is what caused the problem, I just plugged my trandormer in and restored my original files then the update went on fine first try!!!! Thanks for the help!!!!

Did you install Clemsyn/Blades OC kernel? More than likely this is causing your problem.......

I'm getting the same error. Running 3.2 stock but rooted, no modified kernel. Only thing I modified was the Netflix patch which doesn't seem like it's needed now. Is there a flash able zip for this new update?

You can't update the normal way after rooting.
Sent from my Transformer TF101 using XDA Premium App

magicdave26 said:
You can't update the normal way after rooting.
Sent from my Transformer TF101 using XDA Premium App
Click to expand...
Click to collapse
Actually, thats not true. I was running on stock 8.6.5.6 rooted, and was able to update sucessfully. I verified the update in the settings. I have also verified with root checker that i am no longer rooted, as i was before the update. I bought my transformer only a few weeks ago. It came with 3.1 and i updated to 3.2 before rooting. Wonder if that or the rooting method has something to do with why i was able to update while rooted.

I rooted using the method in this thread:
http://forum.xda-developers.com/showthread.php?t=1125714

oilerseberle14 said:
I have my rooted transformer and am trying to update but stow a quarter way throught the install and gives me an android Guy with a triangle with a "!" Sign in it... stock everything just rooted please help
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Same happened to me. As I understand it just rooting doesn't prevent future OTA updates, hence why I was prompted to download this latest, but why it now after failing it tells me there is no longer an update available is beyond me. I can only think ASUS has pulled it for some reason.
---
Sent from my Asus Transformer using Tapatalk

Taomyn said:
Same happened to me. As I understand it just rooting doesn't prevent future OTA updates, hence why I was prompted to download this latest, but why it now after failing it tells me there is no longer an update available is beyond me. I can only think ASUS has pulled it for some reason.
Click to expand...
Click to collapse
You only get it offered the once. Your device is then marked as updated at Asus end. If it didn't work because you were rooted, then tough...

cavsoldier19d said:
Actually, thats not true. I was running on stock 8.6.5.6 rooted, and was able to update sucessfully. I verified the update in the settings. I have also verified with root checker that i am no longer rooted, as i was before the update. I bought my transformer only a few weeks ago. It came with 3.1 and i updated to 3.2 before rooting. Wonder if that or the rooting method has something to do with why i was able to update while rooted.
Click to expand...
Click to collapse
Hmm interesting.
Which method did you use to root it?
Maybe we can pin point why the updates are failing for some people after rooting. I would like to root mine if it was 100% that the OTA updates would still work, even if I had to root it again after each one.

magicdave26 said:
Hmm interesting.
Which method did you use to root it?
Maybe we can pin point why the updates are failing for some people after rooting. I would like to root mine if it was 100% that the OTA updates would still work, even if I had to root it again after each one.
Click to expand...
Click to collapse
I'm having problems with OTA updates and have used Brk's ASUS Transformer HC3.2 RootKit Script to root my device.
I probably did something very stupid...in which I factory reset the device, but noticed that "superuser" is still installed in the apps list. I'm wondering now if i have to re root the device to uninstall superuser and then do another factory reset and then see if the OTA update works? suggestions appreciated

I always look at the updater script in the package before I update. This script contains a bunch of asserts that check the integrity of certain files before it will apply the update. If you can get the update package just open " \META-INF\com\google\android\updater-script" with notepad and that will show everything that's happening when the update occurs including the file asserts it makes. If you've modified these files then it will not update. 8.6.5.6 initially didn't work for me but by checking the script I found the problem was my srs_processing.cfg file because I tried to fix my speaker balance and this was a file that the script asserted. After restoring the original file I was able to update with stock recovery even though I had modified other system files. As long as the specific files the update checks are ok the update will proceed.

aSIMULAtor said:
I'm having problems with OTA updates and have used Brk's ASUS Transformer HC3.2 RootKit Script to root my device.
I probably did something very stupid...in which I factory reset the device, but noticed that "superuser" is still installed in the apps list. I'm wondering now if i have to re root the device to uninstall superuser and then do another factory reset and then see if the OTA update works? suggestions appreciated
Click to expand...
Click to collapse
You need to UnRoot it, I don't think factory reset makes any difference to rooting
http://forum.xda-developers.com/showthread.php?t=1198303

magicdave26 said:
Hmm interesting.
Which method did you use to root it?
Maybe we can pin point why the updates are failing for some people after rooting. I would like to root mine if it was 100% that the OTA updates would still work, even if I had to root it again after each one.
Click to expand...
Click to collapse
The above post about altering certain files appears it might have something to do with it. I rooted using this method... http://forum.xda-developers.com/showthread.php?t=1198303
But it was V2 when i used it. It is now currently V4.

You can re-download the update if you clear your DMClient cache.
Follow the instructions in this thread.
http://forum.xda-developers.com/archive/index.php/t-1106054.html
I had the error with the Android + exclamation mark so I unrooted (reflashed both the stock ROM AND the stock recovery - to get rid of clockworkmod) then cleared the DMClient cache and was I able to update OTA.

As far as I am aware the OTA will not install if you have clockwork Mod flashed for recovery. But if you have rooted without flashing over stock recovery ie clockwork mod not installed the OTA should work but you will lose root by updating.

DT39 said:
As far as I am aware the OTA will not install if you have clockwork Mod flashed for recovery. But if you have rooted without flashing over stock recovery ie clockwork mod not installed the OTA should work but you will lose root by updating.
Click to expand...
Click to collapse
Good point. I did not have clockwork mod recovery installed. Had stock recovery, stock ROM rooted.
Sent from my Inspire 4G using XDA App

I used brk's rootkit script and just restored the original bootimage and it installed perfect let me know if it worked for you guys as well
Sent from my Transformer TF101 using XDA Premium App

I tried flashing back original boot and recovery image, update still failed, and now it fota won't come back. Cleared DMClient cache and hard reset. Guess I'm out of luck until someone releases a flashable version of the update?

Hizpanick said:
I tried flashing back original boot and recovery image, update still failed, and now it fota won't come back. Cleared DMClient cache and hard reset. Guess I'm out of luck until someone releases a flashable version of the update?
Click to expand...
Click to collapse
Same thing happened to me. Tried all the above, and can't get the update to come back.

Have any of you changed original system files whilst rooted? That's why it was failing for me. I managed to get the update again but it failed. I got it once more after it rebooted but took a copy first, unrooting made no difference. Unlike the downloadable firmwares from the ftp site which I checked out, the update script checks the integrity of a ton of files mainly the system apps that cannot be changed without root. If any have changed the script aborts.
Unfortunately even though I had backed up all of them with Titanium Backup, it wouldn't restore them and TB just hung. I tried all its options but nothing helped - a little worrying.
In the end I copied off the TB backup directory to a USB stick and used the NVflash recovery to restore back to factory. I then performed the upgrade again to both the tablet and dock without issues. Four hours later I have it almost back to where I want it.
Hope this helps some of you, even though it's not the best process, but the update imho is worth it
---
Sent from my Asus Transformer using Tapatalk

[Q] 4.5.621 uprgrade failed

I have a droid x that is rooted and has the hack so I can wirelessly tether. I used the voodoo ota root keeper to try and keep my root. When I try to install the update it fails. I also have clockworkmod recovery installed. Any suggestions?
rkshack

Rkshack said:
I have a droid x that is rooted and has the hack so I can wirelessly tether. I used the voodoo ota root keeper to try and keep my root. When I try to install the update it fails. I also have clockworkmod recovery installed. Any suggestions?
rkshack
Click to expand...
Click to collapse
If you do take it there is quite a hassle getting it back to be rootable but if you must? You will need the latest version of rsdlite the desired sbf .602 or .605 which will revert it back to stock then you can take the OTA. My guess is somewhere along the way you froze or uninstalled some of the preinstalled bloatware? Which can cause the update to fail this was my case at least I sbfed to. 602 then took 2 OTA'S to .621 unfortunatley I regreted it you may want to look around at method to freeze updater instead your rooted try a different rom or 2 before making the decision

rom question
Thepooch said:
If you do take it there is quite a hassle getting it back to be rootable but if you must? You will need the latest version of rsdlite the desired sbf .602 or .605 which will revert it back to stock then you can take the OTA. My guess is somewhere along the way you froze or uninstalled some of the preinstalled bloatware? Which can cause the update to fail this was my case at least I sbfed to. 602 then took 2 OTA'S to .621 unfortunatley I regreted it you may want to look around at method to freeze updater instead your rooted try a different rom or 2 before making the decision
Click to expand...
Click to collapse
Where are the best areas to look for info on roms. I have clorkwork rom manager but there are not any roms I recognize.
If I were to back up my rom and then use titatanium back up would I be able to restore to my current state.
rkshack

Rkshack said:
Where are the best areas to look for info on roms. I have clorkwork rom manager but there are not any roms I recognize.
If I were to back up my rom and then use titatanium back up would I be able to restore to my current state.
rkshack
Click to expand...
Click to collapse
RootzWiki is the best place to find roms.
You can make complete backups in ClockworkMod Recovery of your entire rom. I would use MyBackup Root to backup things like individual apps, data, SMS, etc.
Sent from my DROIDX using Tapatalk

update failed
Rkshack said:
I have a droid x that is rooted and has the hack so I can wirelessly tether. I used the voodoo ota root keeper to try and keep my root. When I try to install the update it fails. I also have clockworkmod recovery installed. Any suggestions?
rkshack
Click to expand...
Click to collapse
I also had the same failure, it was due to my having removed some of the bloatware. I loaded the 605 SBF file and rooted this installed al the root programs i would need along with voodoo ota and made a root backup, ran all my programs and did the update, all went ell and I was able to renew root with voodoo ota keeper. so far i have had no problems and am on the 621 update and fully rooted. Titanium backup works fine and I have been able to remove the bloatware.
Hope this helps and i am not too late.

From what every been saying, don't upgrade to 621. Just flash a custom rom right now since you are rooted and you can sbf back to 602 or 605 as needed.
I have 2 Droid X and both running CM7 and its awesome. I tried MIUI and Gummy but couldn't get into it.

4.5.621 install failure
Greetings. This looks like the right thread for this issue, but if not, please redirect me.
Some background:
DroidX
Android version 2.3.3
System version 4.5.605.MB810.en.US
currently rooted
Being a laggard, I did not accept the 621 update when first offered through OTA. My 4.5.605 DroidX was rooted and I'd read that I'd have to either unroot or "hide" root in some manner. It seemed like a bit of trouble and I had other life issues at the time.
After things cleared, I contacted VZ and they pushed the upgrade again. After "unrooting", I accepted the OTA upgrade, but each installation attempt failed after a successful download. No other diagnostics, just "the update failed". I tried this multiple times after reboots, battery removal, cache clearing and such. I then did a factory reset and tried again - still the same sequence, successful download, install now, update failed.
So I called VZ and Moto. They suggested accepting the update while attached to a solid WiFi. All the same tricks were turned as with the OTA (another factory reset, clear cache, remove/replace battery) only these attempts used the WiFi (excellent signal). Same failure.
Moto then suggested I ship in the unit and for $110 they would handle it. Right.
So I found Blur_Version.4.5.621.MB810.Verizon.en.US.zip, downloaded it to the SD card and attempted to install using the recovery mode menu. This also fails but at least offers up the message: assert failed apply_patch ("system/app/AccountAndSyncSettings, apk", "-" then some odd number letter sequences followed by "error in /tmp/sideload/package.zip status 7.
I've since rerooted just out of curiosity to see if that would still work.
All this to fix the irritating bug of the phone powering back on by itself.
Any hints or advice?
Thanks.
-Joe

Sending your device in is not necessary at all.
It seems that you have removed one of the systems stock apps. Replace any apps that you may have removed and attempt to take the update again.
Or, you can SBF back to 602 and take the OTA update to .621. Just be sure to back up everything that you need (not including app data).
Sent from my Galaxy Nexus using Tapatalk 2

missteps
Bloatware was renamed but I've been pretty careful not to delete anything... even kept a list of what was renamed and to what. All that has been rolled back but clearly something was missed. The only thing that threw me a curve was the symlink on the Madden Football app, but even that now looks pre-modified.
I take it that changes to ACLs would also glitch the update, but what about file timestamps? How pristine do these stock apps have to be?
I'll check them again since there's little to lose in doing so. If I can't find a discrepancy, the sbf to 602 will be the next step.
Ironically, the reason for embarking on the bloat removal at the outset was to cure the auto-power on bug, which is now supposedly fixed in 621.
But it's all about the learning.
Thanks again.

Help me please 2.3.3 to 2.3.4
I recently tried updating my phone....When I go to system settings and then go to About phone and then system updates.... I get this update 4.5.621.en.us. Then I click download and then when it finishes...I click install and then it shuts off and then it boots up and says " Failed to update software" Click ok... Then that's it... Someone please help me....
DETAILS of FIRMWARE and ETC..
System Version: 4.5.605.MB810.Verizon.en.us
Model number: DroidX
Android Version: 2.3.3 Gingerbread
Someone please help me with this annoying error

Legit-Reflex said:
I recently tried updating my phone....When I go to system settings and then go to About phone and then system updates.... I get this update 4.5.621.en.us. Then I click download and then when it finishes...I click install and then it shuts off and then it boots up and says " Failed to update software" Click ok... Then that's it... Someone please help me....
DETAILS of FIRMWARE and ETC..
System Version: 4.5.605.MB810.Verizon.en.us
Model number: DroidX
Android Version: 2.3.3 Gingerbread
Someone please help me with this annoying error
Click to expand...
Click to collapse
Have you tried downloading the update via wifi? Is the update appoximately 32MB? Have you tried to flash the 621 sbf?
Sent from my MB860 using xda app-developers app

palmbeach05 said:
Have you tried downloading the update via wifi? Is the update appoximately 32MB? Have you tried to flash the 621 sbf?
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
I don't know how to flash, and yes i've tried multiple times downloading the update....help

Legit-Reflex said:
I don't know how to flash, and yes i've tried multiple times downloading the update....help
Click to expand...
Click to collapse
Download RSD Lite, i think the latest revision is 5.7. then download the 621 sbf, any necessary drivers, and it also helps to have the fastboot/adb package as well (even though fastboot is useless for us, still something good to have).
backup anything you need backed up or do a nandroid. reboot to bootloader. connect device to computer. start up RSD Lite. click show device. click the button that lets you browse for files. select 621 sbf. click start. sit back and let it do its thing and you'll be back up and running in no time

Links files and instruction on how to flash a sbf, are in my list
sd_shadow's [Collection] of Links for: Droid X (MB810)
Sent from my XT862 using Tapatalk

deboyz1014 said:
From what every been saying, don't upgrade to 621. Just flash a custom rom right now since you are rooted and you can sbf back to 602 or 605 as needed.
I have 2 Droid X and both running CM7 and its awesome. I tried MIUI and Gummy but couldn't get into it.
Click to expand...
Click to collapse
621 isn't all bad. It's easy enough to root it now with an apk called Framaroot and you will then have all the latest security updates from Motorola. If you do go with 621 you are then"stuck" there as it is not possible to go back to any earlier versions. Most of the most recently updated Roms work fine with it.
Sent from my SCH-I535 using Tapatalk