Database Info

[Q] Got OTA 2.3.2 update, still rooted!!!!

don't know why - but my phone still rootedm, even after 2.3.2 update
Any idea how come?

oxothuk_uae said:
don't know why - but my phone still rootedm, even after 2.3.2 update
Any idea how come?
Click to expand...
Click to collapse
By "still rooted" do you mean you still have the superuser.apk or can you actually still boot into CWM? Because an OTA will not delete those apps but it WILL break root.

oxothuk_uae said:
don't know why - but my phone still rootedm, even after 2.3.2 update
Any idea how come?
Click to expand...
Click to collapse
The update doesn't wipe the phone at all, it only patches certain files in the /system partition, so it doesn't actually delete the su binary in /system/bin or the superuser.apk in /data/apps.
The update script does, however, do a recursive chmod of the permission on /system/bin, and that broke root on my phone. Even though the files were still there, and some apps thought that I was still rooted, many root things (like Titanium and Root Explorer's ability to mount /system as R/W) wouldn't work.
I've seen some reports that root stuck, but I'd advise flashing the su update again...it's quick and easy to do with CWM, and it will fix the permissions to make sure none of your apps have any issues.
Are you sure the update actually occurred? Your android version and build number have changed?

so, now i have
Android version - 2.3.2
Kernel - 2.6.35.7-g7f1638a
Build number - GRH78C
if start titanium backup - can see that superuser permission granted
Market access working perfectly - i hav an acces for paid apps
Can grab screen with ShootMe
dont remember how did i root - seems i just run some script on ubuntu notebook
Thanks for everybody for replies

yes, going into CWR can easily update the permissions recursively

not sure but probably i am on superboot loader (not SWR)

being rooted does not stop OTA updates, it never has. being on a ROM other than stock is when you cant get the updates. if i root, and leave on the stock ROM, the update should come thru jsut fine. at least that was my understanding.

RogerPodacter said:
being rooted does not stop OTA updates, it never has. being on a ROM other than stock is when you cant get the updates. if i root, and leave on the stock ROM, the update should come thru jsut fine. at least that was my understanding.
Click to expand...
Click to collapse
He's saying that he thought the OTA would unroot him, not that being rooted would keep him from OTAing.
Funny how the update seems to impact the root of people differently. It definitely broke mine, even though it didn't erase the files.

Oh oops my bad I mis read!

The update didn't break my root

sagech said:
The update didn't break my root
Click to expand...
Click to collapse
it seems new uppdate does not unroot phones with superboot rooting

No Update
Hello,
I tried to update my phone but I am now looking since 10 minutes at the little Android and nothing happens.
There was a short message where the Clockworkrecovery said something like it could not verfy the update file.
Should I just put out the battery and try to reboot?
Edit:
The Clockwork recovery came up again and I selected to reboot the phone. Now it's still running on 2.3.1.
What have I done wrong?

Is it the little android and a triangle with a ! inside it? That happened to me also and I found out that if u change any system files like patching the 3d gallery apk or in my case I deleted the genie widget apk, it will cause ota's not to take.
Sent from my Nexus S

Bronk93 said:
Is it the little android and a triangle with a ! inside it? That happened to me also and I found out that if u change any system files like patching the 3d gallery apk or in my case I deleted the genie widget apk, it will cause ota's not to take.
Sent from my Nexus S
Click to expand...
Click to collapse
Yes, exactly!
So is the solution maybe to wait till the 2.3.2 version is available at the ROM Manager?

[Q][A700] Post OTA Update Rooting.

After the recent update (AV043_A700_RV07RC06_PA_CUS1 / AV043_A700_1.029.00_PA_CUS1) which wiped unlocked bootloader and root.....
I've re-unlocked my bootloader. Had a few issues with system hanging, that I didn't have before, but it seems the unlock was a success as outlined in the thread by alx5962.
I'm not prepared to root again using method 2 (which worked just peachy, by the way) until I hear if the existing files/method will work with the new OTA firmware or if I would end up bricked.
Has anyone tried to root since the OTA?

ExtremeRyno said:
After the recent update (AV043_A700_RV07RC06_PA_CUS1 / AV043_A700_1.029.00_PA_CUS1) which wiped unlocked bootloader and root.....
I've re-unlocked my bootloader. Had a few issues with system hanging, that I didn't have before, but it seems the unlock was a success as outlined in the thread by alx5962.
I'm not prepared to root again using method 2 (which worked just peachy, by the way) until I hear if the existing files/method will work with the new OTA firmware or if I would end up bricked.
Has anyone tried to root since the OTA?
Click to expand...
Click to collapse
I was able to root the new update no problem with one of the scripts I downloaded here.
I can post it later after work if you want.
Its whichever one has the ICS Batch script in it that reboots your tablet into fast-boot, it worked.

Itchiee said:
I was able to root the new update no problem with one of the scripts I downloaded here.
I can post it later after work if you want.
Its whichever one has the ICS Batch script in it that reboots your tablet into fast-boot, it worked.
Click to expand...
Click to collapse
Yes, please. Post script if possible.
Please also let us know of any post rooting issues with the new update.

OK, I'll post it up when I get home.
I haven't noticed any issues, but then I haven't been really using it much since I got my Nexus 7 ♥
Edit - OK, I used the attached zip file, extract, right click the flash-ICS-patchedBoot.bat file and run as administrator.
Make sure USB debugging is checked on the tablet before running this file.

After you run the script it will boot the tablet into boot loader mode, it will copy over a few files, then the tablet will reboot with the script saying waiting for device, and will wait and wait... Once your tablet is up again it will have SuperUser installed, then you can install Busy box if you wish, or my fave Root Explorer, and the script will still be waiting for device... You can close it.

Yep, confirmed Method 2 still works. Hooray! Was a pain in the butt not having Button Savior.

Somewhat worried...

Hi people. Just this morning, I finally got the nerve to unlock. I had to downgrade doing it. Now, I heard after unlocking, an ota will brick tablet. For some reason, the new firmware downloaded. It's trying to update, and I don't know how to stop it. Also, stock browser disappeared too. What can I do before tablet bricks?

redheadplantguy said:
Hi people. Just this morning, I finally got the nerve to unlock. I had to downgrade doing it. Now, I heard after unlocking, an ota will brick tablet. For some reason, the new firmware downloaded. It's trying to update, and I don't know how to stop it. Also, stock browser disappeared too. What can I do before tablet bricks?
Click to expand...
Click to collapse
go to the root of your external sd card and delete all the zip file(s), you probably left it there when you downgrade. Also delete file from internal sdcard in /cache/recover if any. Once you unlocked you shouldn't receive anymore OTA.

redheadplantguy said:
I finally got the nerve to unlock. I had to downgrade doing it.
Click to expand...
Click to collapse
Strange, many people said the unlock tool works fine on JB.
redheadplantguy said:
Now, I heard after unlocking, an ota will brick tablet.
Click to expand...
Click to collapse
Where?
I don't say it cannot brick your tablet, but I am not aware of any reports that it does.

redheadplantguy said:
Hi people. Just this morning, I finally got the nerve to unlock. I had to downgrade doing it. Now, I heard after unlocking, an ota will brick tablet. For some reason, the new firmware downloaded. It's trying to update, and I don't know how to stop it. Also, stock browser disappeared too. What can I do before tablet bricks?
Click to expand...
Click to collapse
As said by the first responder, you can delete the cached firmware file. I do not expect the OTA to brick your tablet, but you could interrupt the process if you really wanted to.
Even with a brick, there are loads of possibilities of flashing a firmware file from ASUS' repository. Then you'd have a fresh tablet OS to your convenience. The situation you describe above does not exactly ruffle any my feathers.
EDIT: just in case you are not yet on .30 or higher... get Nvflash on there!

MartyHulskemper said:
As said by the first responder, you can delete the cached firmware file. I do not expect the OTA to brick your tablet, but you could interrupt the process if you really wanted to.
Even with a brick, there are loads of possibilities of flashing a firmware file from ASUS' repository. Then you'd have a fresh tablet OS to your convenience. The situation you describe above does not exactly ruffle any my feathers.
EDIT: just in case you are not yet on .30 or higher... get Nvflash on there!
Click to expand...
Click to collapse
i could be mistaken. alas, i can't get nvflash. i wish i could. i didnt expect firmware to come in after unlock.

redheadplantguy said:
i could be mistaken. alas, i can't get nvflash. i wish i could. i didnt expect firmware to come in after unlock.
Click to expand...
Click to collapse
If you unlocked your device, there will be NO OTA update, unless the download happened before you unlocked or you may have the update software sitting in your external SDcard or in internal SDcard /cache/recovery.

buhohitr said:
If you unlocked your device, there will be NO OTA update, unless the download happened before you unlocked or you may have the update software sitting in your external SDcard or in internal SDcard /cache/recovery.
Click to expand...
Click to collapse
It downloaded, showing a progress bar. Later I reset, and this morning, it downloaded again. It showed it actually downloading.

redheadplantguy said:
It downloaded, showing a progress bar. Later I reset, and this morning, it downloaded again. It showed it actually downloading.
Click to expand...
Click to collapse
You must be "the chosen one", first I heard of OTA stills working after you unlocked. Just verify that you actually "unlocked", by reboot your device and it should shows "your device is unlock" during booting up. If it does, then you are the chosen one. You can update as long as you are pure stock rom, and if you have root, just use OTA root keeper to keep root then you can update your pure stock rom to the new version. If you mod/freeze system apps then the update will fail. I never heard of updating of a stock rom with unlocked bootloader will brick your device. It will brick your device if you modded or using custom rom.
EDIT: If you don't want to do through OTA, you could download full package rom from Aus site, unzip then copy the new zip file to the root of your external SDcand. Disabled wifi (no more download) then delete the update file located in your internal memory /cache/recovery. Turn off your device, go into recovery mode by hold down volume down+power button, then install from there.

buhohitr said:
You must be "the chosen one", first I heard of OTA stills working after you unlocked. Just verify that you actually "unlocked", by reboot your device and it should shows "your device is unlock" during booting up. If it does, then you are the chosen one. You can update as long as you are pure stock rom, and if you have root, just use OTA root keeper to keep root then you can update your pure stock rom to the new version. If you mod/freeze system apps then the update will fail. I never heard of updating of a stock rom with unlocked bootloader will brick your device. It will brick your device if you modded or using custom rom.
EDIT: If you don't want to do through OTA, you could download full package rom from Aus site, unzip then copy the new zip file to the root of your external SDcand. Disabled wifi (no more download) then delete the update file located in your internal memory /cache/recovery. Turn off your device, go into recovery mode by hold down volume down+power button, then install from there.
Click to expand...
Click to collapse
Thanks. Yeah, says "the device is unlocked." In tiny white letters very top left. I hope my glitch doesn't interfere in me flashing new ROM's
Odd, did factory reset, and lost root AND twrp. Had to reflash it.

redheadplantguy said:
Thanks. Yeah, says "the device is unlocked." In tiny white letters very top left. I hope my glitch doesn't interfere in me flashing new ROM's
Odd, did factory reset, and lost root AND twrp. Had to reflash it.
Click to expand...
Click to collapse
That does sound like it actually flashed something (at least partly). I would run that unlock tool another time just to be sure I wouldn't get into trouble down the road (Having an ASUS OTA flash right on top of your CleanROM/CM10/AOKP could be a minor disaster, or a pretty disastrous disaster, depending on what ROM of these you were on. Flashing over stock, well... minor nuisance, but it would be majorly inconvenient to have to flash root and stuff all the time.)

MartyHulskemper said:
Having an ASUS OTA flash right on top of your CleanROM/CM10/AOKP could be a minor disaster, or a pretty disastrous disaster, depending on what ROM of these you were on.
Click to expand...
Click to collapse
No, it just doesn't work. The updater-script inside the OTA package compares the checksums of the system apps to be patched, and aborts as soon as one doesn't match the previous stock ROM.
The only potential danger I see is the communication with the bootloader which kernel to boot - the OTA downloader (DMClient) somehow has to instruct the bootloader to load the recovery kernel to install the dlpkgfile from /cache, and if that process is still not understood by custom recovery creators (there were some problems apparently, I don't know if they are solved), you might end up with a device that only boots into the recovery and not into Android.

Thanks. I will.
Sent from my SGH-T679 using Xparent ICS Blue Tapatalk 2

Used RootKeep but still lost root

Hello:
I'm trying to root my JB (.25) TF700. Yesterday, I was able to downgrade to ICS, root, temp unroot and then install JB (.25). But - after installing JB, the TempRoot was gone. What's up with that?
Here's my method:
From JB (.25), downloaded ICS (.30), extracted it to MicroSD and downgraded without issue. I tried to do this through factory recovery (Volume Down, release and then Volume Up); however, I'd get the Android+red triangle error. Instead, I just inserted the card on the home screen and the system pushed the downgrade itself.
Once I installed ICS, I rooted without issue. Downloaded RootKeeper, created backup and temp unrooted.
Then, here's were I went wrong probably, used the same method as stated above to install the JB (.25) firmware. I downloaded .25 from ASUS, extracted onto MicroSD and then inserted the card at home screen. The OS prompted the firmware update and JB was installed. I did create a TempRoot (backup) before installing JB.
Like I said above, JB installed but TempRoot was gone. I'm assuming that I used the wrong technique for upgrading to JB. But I always seem to get the Android + red triangle when I go through recovery mode.
Any ideas? Thanks.

-lukin- said:
Hello:
I'm trying to root my JB (.25) TF700. Yesterday, I was able to downgrade to ICS, root, temp unroot and then install JB (.25). But - after installing JB, the TempRoot was gone. What's up with that?
Here's my method:
From JB (.25), downloaded ICS (.30), extracted it to MicroSD and downgraded without issue. I tried to do this through factory recovery (Volume Down, release and then Volume Up); however, I'd get the Android+red triangle error. Instead, I just inserted the card on the home screen and the system pushed the downgrade itself.
Once I installed ICS, I rooted without issue. Downloaded RootKeeper, created backup and temp unrooted.
Then, here's were I went wrong probably, used the same method as stated above to install the JB (.25) firmware. I downloaded .25 from ASUS, extracted onto MicroSD and then inserted the card at home screen. The OS prompted the firmware update and JB was installed. I did create a TempRoot (backup) before installing JB.
Like I said above, JB installed but TempRoot was gone. I'm assuming that I used the wrong technique for upgrading to JB. But I always seem to get the Android + red triangle when I go through recovery mode.
Any ideas? Thanks.
Click to expand...
Click to collapse
OK, what's going on here is you're using the Asus full firmware upgrade which will wipe your root. You need to use the dlpkgfile incremental upgrade method can be found here http://forum.xda-developers.com/showthread.php?t=1803090
It's a pain since you need to go one upgrade at a time -.30 then .16 then .18 you got the idea!

buhohitr said:
OK, what's going on here is you're using the Asus full firmware upgrade which will wipe your root. You need to use the dlpkgfile incremental upgrade method can be found here http://forum.xda-developers.com/showthread.php?t=1803090
It's a pain since you need to go one upgrade at a time -.30 then .16 then .18 you got the idea!
Click to expand...
Click to collapse
Thanks. Can't do one firmware upgrade, darn. How many increments are there?

-lukin- said:
Thanks. Can't do one firmware upgrade, darn. How many increments are there?
Click to expand...
Click to collapse
To do it right, .16,.18,.20,.23,.25 ...total of 5, (unless you unlock your device). You may get away with just .16,.18, then .25.(bootloader is the same after .18). Your auto OTA is not working??

buhohitr said:
To do it right, .16,.18,.20,.23,.25 ...total of 5, (unless you unlock your device). You may get away with just .16,.18, then .25.(bootloader is the same after .18). Your auto OTA is not working??
Click to expand...
Click to collapse
Well, at ICS .25, I checked for OTA and there was nothing. Not sure how long I should be waiting. I've had problems with OTA in the past and just assumed I screwed the pooch somehow. Should I be able to OTA at ICS .25?
Thanks.

-lukin- said:
Well, at ICS .25, I checked for OTA and there was nothing. Not sure how long I should be waiting. I've had problems with OTA in the past and just assumed I screwed the pooch somehow. Should I be able to OTA at ICS .25?
Thanks.
Click to expand...
Click to collapse
Well, I suggest at the least you should do .16, .18 then .25, since it's incremental change, one change depended on the previous change so some stuff may not working correctly if you decided to skip.

buhohitr said:
Well, I suggest at the least you should do .16, .18 then .25, since it's incremental change, one change depended on the previous change so some stuff may not working correctly if you decided to skip.
Click to expand...
Click to collapse
Okay - I have found all the firmwares here http://forum.xda-developers.com/showthread.php?t=1946456and here http://support.asus.com/download/options.aspx?SLanguage=en. I will try to do the incremental upgrades - but the step by step process isn't exactly clear from the link provided above. For example, what is the first step with "WW_epad-user-10.4.4.16.zip"? Do I extract the blob and if so so where to? How is "dlpkgfile" involved? Thanks.

-lukin- said:
Okay - I have found all the firmwares here http://forum.xda-developers.com/showthread.php?t=1946456and here http://support.asus.com/download/options.aspx?SLanguage=en. I will try to do the incremental upgrades - but the step by step process isn't exactly clear from the link provided above. For example, what is the first step with "WW_epad-user-10.4.4.16.zip"? Do I extract the blob and if so so where to? How is "dlpkgfile" involved? Thanks.
Click to expand...
Click to collapse
Both links you provide are full stock firmware, not going to work. You need dlpkgfile only, can be found here http://forum.xda-developers.com/showthread.php?t=1926147
Just download them and make sure the final name is dlpkgfile (no extention, exactly like that).
also download command file and the name is command (exactly like that, no extention)
copy them these directories:
command goes to /cache/recovery
dlpkgfile goes to /cache
Make sure the files are named exactly as shown above. No capitals, no file extensions, etc.
Make sure the permissions for both files are changed to RW-RW-R for both.
This is how it should be after copied:
/cache/recovery/command
/cache/dlpkgfile
power off, then boot into recovery and wait a 10sec it should update. Remember if it failed or boot back into the OS, you need to verify if the two files still there, one of them will be erase and you have to recopy then do it again.

buhohitr said:
Both links you provide are full stock firmware, not going to work. You need dlpkgfile only, can be found here http://forum.xda-developers.com/showthread.php?t=1926147
Click to expand...
Click to collapse
Thanks. I'm working on getting these downloaded. But I notice that the dlpkgfile is considerably smaller than full firmware. Is that right?

-lukin- said:
Thanks. I'm working on getting these downloaded. But I notice that the dlpkgfile is considerably smaller than full firmware. Is that right?
Click to expand...
Click to collapse
Yes, depend on how much upgrade, but they are much smaller around 14meg. Full firmware is around 455-485meg.

-lukin- said:
Thanks. I'm working on getting these downloaded. But I notice that the dlpkgfile is considerably smaller than full firmware. Is that right?
Click to expand...
Click to collapse
The dlpkgfile that updates from ICS to JB is almost 200 MB, the others are around 15 MB each.

buhohitr said:
Yes, depend on how much upgrade, but they are much smaller around 14meg. Full firmware is around 455-485meg.
Click to expand...
Click to collapse
We're in business. I've got ICS, rooted and JB .16 - now working on .18
Thanks for taking the time to help today
P.S. Never forget to unroot! That's how I got here in the first place. Cheers.

Not bad, you're a pretty smart guy after all.
Sent from my ASUS Transformer Pad TF700T using xda premium

[Q] Lost root after latest firmware update

Just wanted to give everyone a heads up about the recent firmware update (build 10.6.1.15.3) for the TF300T. I had root before the update and all was well in the world and then I saw the update notification. I checked voodoo to make sure I had root backed up and I did. I performed the update and now no root and voodoo is not restoring it. I fired up adb and found su binary and busybox are missing from bin and xbin It appears asus decided to overwrite my system directory in this update and wipe out all those files that I so carefully placed to gain root access.
I think I am now officially stuck unrooted. :crying:
Unfortunately unlocking the bootloader is not an option for me for work related reasons. If anyone has any other information about this update or how I can restore root, please help!
Otherwise you would be wise to stay away from this update if you are currently locked and want to keep root.

This might help you:
[JB ROOT] motochopper works! (Root JB 4.1.1 & 4.2.1 with locked bootloader!)
And a little searching might find it even quicker than asking!

Someone just confirmed it is still working with the latest upgrade.
Would have been surprised, if Asus had broken it that quickly.
Sent from my TF300T using Tapatalk HD

ccb1208 said:
Just wanted to give everyone a heads up about the recent firmware update (build 10.6.1.15.3) for the TF300T. I had root before the update and all was well in the world and then I saw the update notification. I checked voodoo to make sure I had root backed up and I did. I performed the update and now no root and voodoo is not restoring it. I fired up adb and found su binary and busybox are missing from bin and xbin It appears asus decided to overwrite my system directory in this update and wipe out all those files that I so carefully placed to gain root access.
I think I am now officially stuck unrooted. :crying:
Unfortunately unlocking the bootloader is not an option for me for work related reasons. If anyone has any other information about this update or how I can restore root, please help!
Otherwise you would be wise to stay away from this update if you are currently locked and want to keep root.
Click to expand...
Click to collapse
I got root back from voo doo. In your message you say you had checked root backed up. You didnt say you took the next step and hit temp unroot so that system appears unrooted whilr updating.
Just wondering.
Woody
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2

woodsonmh said:
I got root back from voo doo. In your message you say you had checked root backed up. You didnt say you took the next step and hit temp unroot so that system appears unrooted whilr updating.
Just wondering.
Woody
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
I actually did that. I temp unrooted before I updated which in hindsight might have been part of my issue. Anyways, I am going to be using motochopper to reroot but my tmp directory thinks it is a file now :silly:
I am currently downloading the asus firmware file so I can manually update (even though i am already on 4.2.1) and that is suppose to re-write my system directory so my tmp directory will be restored and I can push all the needed files. I will report back with how it goes.
[UPDATE] I was able to apply asus firmware manually (which factory reset my device in the process) then ran motochopper successfully. I backed up root with voodoo and this time updated firmware OTA without temp unrooting. After the update was applied, I restored root with voodoo and all is well now! Thank you everyone for your help

Root for build 10.6.1.15.3
ccb1208 said:
Just wanted to give everyone a heads up about the recent firmware update (build 10.6.1.15.3) for the TF300T. I had root before the update and all was well in the world and then I saw the update notification. I checked voodoo to make sure I had root backed up and I did. I performed the update and now no root and voodoo is not restoring it. I fired up adb and found su binary and busybox are missing from bin and xbin It appears asus decided to overwrite my system directory in this update and wipe out all those files that I so carefully placed to gain root access.
I think I am now officially stuck unrooted. :crying:
Unfortunately unlocking the bootloader is not an option for me for work related reasons. If anyone has any other information about this update or how I can restore root, please help!
Otherwise you would be wise to stay away from this update if you are currently locked and want to keep root.
Click to expand...
Click to collapse
**********
I lost root as well after update to build 10.6.1.15.3,however, all I needed to do is reinstall TWRP and install UPDATE-SuperSU-v1.25.zip and I'm again rooted. You can do a search for UPDATE-SuperSU-v1.25.zip file here on XDA...it will come up. Hope this helps.
Regards,
Julian

julianikos said:
**********
I lost root as well after update to build 10.6.1.15.3,however, all I needed to do is reinstall TWRP and install UPDATE-SuperSU-v1.25.zip and I'm again rooted. You can do a search for UPDATE-SuperSU-v1.25.zip file here on XDA...it will come up. Hope this helps.
Regards,
Julian
Click to expand...
Click to collapse
I was able to reaquire root by using motochopper but thanks for the advise. Sounds like your device is unlocked which like I said was not an option for me.
BTW, if you are unlocked, why are you running stock asus firmware??? You can find AOKP builds over at rootzwiki. http://rootzwiki.com/topic/27152-aokp-build-38-unofficial/