Related
Hey everybody! I went to stock from CyanogenMod Nightlyes, and flashed stock 2.3.2 nandroid.
Then I flashed the 2.3.3, it works just fine! But my bootloader is still unlocked!
First thing that i thank was just to install Superuser, but it doesen't work.
I connected it to Pc in fastboot mod, and ran install-superboot-windows.bat (one click root)
But now, it just stuck in Google logo, and I don't know what to do next... I tryed to pull out the battery, nothing...
Update: just reflashed recovery via fastboot flash recovery recovery.img, and got the CWM. Now restoring to 2.3.2.
I think that we can just flash CWM after update, and then install superuser. I'll try and will ask you about any changes.
Update 2:: So, it ran just fine, first installed 2.3.2, then updated it to 2.3.3, and then flashed CWM. It boots up just fine, but in CWM I tried to install superuser.zip, it says: invalid to install
maybe reinstall your backup from CWM?
also the one click root you need to be in a rom and using adb
I did the same thing and ended up in the same situation...ive fixed like this...downloaded odin got back to stock 2.3.1 then downloaded the update,flashed it through stock recovery then flashed recovery.img....flashed su and everything is back on normal now
Hope it helps
Sent from my Nexus S using XDA App
If you unlock already, it is very easy to root again
1. fastboot boot recovery.img
2. flash su.zip
3. reboot
all done
Yeah, but it says, that it can't install superuser.zip (bad) I don't know what it means..
2.3.3 root question
Ok so currently I'm rooted on stock 2.3.2
How do I update to 2.3.3 and
1. not lose root
2. not have to reinstall all user apps
3. not have to redo all my settings
Is there a way to do this?
This does not belong in development.
Sent from my MattedBlues CM7 Google Nexus S!
I have a question is there a way to make the phone as if it was never messed about with, just incase it was ever needed to get repaired under the warrenty
Trinitronik said:
Yeah, but it says, that it can't install superuser.zip (bad) I don't know what it means..
Click to expand...
Click to collapse
mount /system inside of clockwork then try.
Sent from my Nexus S using XDA App
Jnowak1981 said:
Ok so currently I'm rooted on stock 2.3.2
How do I update to 2.3.3 and
1. not lose root
2. not have to reinstall all user apps
3. not have to redo all my settings
Is there a way to do this?
Click to expand...
Click to collapse
Try this..
From Android 2.3.2 /rooted/locked bootloader
1) Fastboot boot recovery.img..to boot into recovery CW recovery screen
2) Apply 2.3.3 update.zip ..
=>Do not reboot ,as this 2.3.3 has Bootloader change that disable fastboot boot for locked bootloader.
3) Without rebooting , mount system, apply su.zip
4) Reboot..
Click to expand...
Click to collapse
I am just posting the concept..you need to find out the details steps
Ill keep 2.3.2 until than
Sent from my Nexus S using XDA App
Follow the link, i managed to retain root after 2.3.3 update.
http://forum.xda-developers.com/showpost.php?p=11626567&postcount=70
Code:
I manage to keep the root for 2.3.3 with the flashing sequence listed below.
From Android 2.3.2 /rooted/locked bootloader
1) Fastboot boot recovery.img..to boot into recovery CW recovery screen
2) Apply 2.3.3 update.zip ..
=>After applying update DO NOT REBOOT ,as this 2.3.3 has Bootloader change that disable fastboot boot for locked bootloader.
3) Without rebooting , mount system, apply su.zip
=> This step is to reapply Superuser.apk permission setting
4) Reboot..
I am highlighting the concept, for details inter steps..please refer to the first post on the link.
2.3.3 root
is there a method to root 2.3.3 or is it to early i tried allgamer way but it failed
Or you can simply restore 2.3.3 its in the development forum. It had root already on it
Sent from my Nexus S using XDA App
There is a 2.3.3 rooted nandroid backup in development section.
Sent from my Nexus S using XDA App
well tryind to do from 2.3.3
Based on this change from 2.3.2 to 2.3.3, does it make sense just to unlock the bootloader?
Yes, I know it'll wipe my device, but is that the only thing? I can just use Titanium Backup and restore everything anyway right?
Are there advantages/disadvantages to the locked bootloader? I never bothered just because I was just learning how to root and picked a method almost at random.
kaimyn said:
Based on this change from 2.3.2 to 2.3.3, does it make sense just to unlock the bootloader?
Yes, I know it'll wipe my device, but is that the only thing? I can just use Titanium Backup and restore everything anyway right?
Are there advantages/disadvantages to the locked bootloader? I never bothered just because I was just learning how to root and picked a method almost at random.
Click to expand...
Click to collapse
If I were currently locked bootloader, I would run a full titanium backup of apps+data, and copy over your entire sdcard contents to your pc, along with the titanium backups (remember, the oem unlock wipes the sdcard also, not just internal space).
Then unlock the bootloader. Easiest way to deal with custom recovery in the future.
There are steps in the 2.3.3 link thread here describing how you can update and get root back even with the locked bootloader; which might be less of a hassle then going through a wipe.
squattingb said:
I tried to do this in clockwork but the installation kept failing, I was getting some messages about "assert failed", wasn't quite clear so I couldn't really make out what the problem was, does anyone have any insights into this? I downloaded the update from http://forum.xda-developers.com/showthread.php?p=11566707 for Nexus S.
Click to expand...
Click to collapse
I'm having the same issue. Any idea how to fix this?
Just load the Nandroid as charlieb620 said. If your already on 2.3.3 you won't lose nowt, just backup your data first.
All,
I have updated to 2.3.4, lost root as expected and tried to reroot 2.3.4.
I had no luck, once i ran ./Gingerbreak the script would sit and not do anything after displaying the initial text.
Has anyone successfully done this?
I thought about updating with the prerooted 2.3.4, but the devs started to add all sorts of stuff in there, and right now that is not what I am after.
Thanks!
Also anxiously waiting for a 2.3.4 root option.
- No custom boot loader means I can't use the current SU.zip process.
- I didn't unlock the boot loader on the phone and now really don't want to go through the hassle of having the phone reset when I do... too much on it.
- Can't do a nandroid backup (to unlock) because I don't have root.
Catch 22 circle. Am keeping my eyes open, hopefully someone comes up with an alternate method. Once I get root again I will unlock the boot loader after making a backup so this doesn't happen again.
51Cards said:
Also anxiously waiting for a 2.3.4 root option.
- No custom boot loader means I can't use the current SU.zip process.
Click to expand...
Click to collapse
Custom bootloader? Just unlock the one you have and flash a new recovery. It takes a whopping 3 minutes to flash recovery, then SU, and reboot. If you want to keep everything stock so you can OTA, the stock ROM will overwrite the recovery when you boot and you'll end up with rooted stock ROM with OEM recovery. If you want to then flash a custom rom, you can do so through ROM manager.
Want to unroot? Download the FRG33 passimg.zip and boot into bootloader.
This stuff is stupid easy on the N1.
ATnTdude said:
Custom bootloader? Just unlock the one you have and flash a new recovery.
Click to expand...
Click to collapse
Ok so feeling like a newb here.
First I meant 'custom recovery', not 'custom boot loader'... mixup in terms on my part.
But to put in a custom recovery I need to unlock the phone. Once I unlock the boot loader doesn't the phone reset to factory state? I had seen that mentioned several times and in the unlock video I was watching. After the phone was unlocked it went back to "Welcome to Android" etc on the next startup. Have far too much in the phone I don't wish to loose and I can't Nandroid it without root.
Thanks for the info.
I had used Gingerbreak on my 2.3.3 - after 20 seconds of searching on XDA I found that you can simply install ROM Manager, flash RA custom recovery, boot into recovery, remove signature verification, flash update.zip followed by su.zip and you keep root .... all this WITHOUT an unlocked bootloader...
I am attempting to keep my phone as stock as possible and only root to block ads and sometimes push some new app that google wont release to the n1.
I really don't want to mess with custom anything on my daily driver (used for business also). I have my g1 for that
SO....has anyone used gingerbreak successfully on 2.3.4?
Disregard. I misread the post.
MitchRapp said:
I had used Gingerbreak on my 2.3.3 - after 20 seconds of searching on XDA I found that you can simply install ROM Manager, flash RA custom recovery, boot into recovery, remove signature verification, flash update.zip followed by su.zip and you keep root .... all this WITHOUT an unlocked bootloader...
Click to expand...
Click to collapse
Yeah, the ROM manager option would have worked well before I did the OTA for 2.3.4 and lost root. I will keep it in mind for the future, thanks!
I'm sure there's a better, faster, more direct way, but here's how I went from 2.3.4 stock to 2.3.4 rooted without unlocking the bootloader.
1. Flash FRG33 as passimg.zip on SD card.
2. Flash FRG33 to GRI40 as update.zip on SD card using stock recovery.
3. Root GRI40 2.3.3 using Gingerbreak.
4. Install ROM Manager app and install Clockworkmod Recovery.
5. Open GRI40 to GRJ22 update zip file and REMOVE Recovery folder from it.
6. Boot into Clockworkmod Recovery and flash modified update.zip from step 5.
7. Install SU.zip from Clockworkmod right.
Voila! Rooted GRJ22 2.3.4 with locked bootloader. Lot of steps, but I don't think it took more than 10-15 minutes.
Exactly what I did. Works smoothly and you're all set in minutes. As long as you had root in the first place, on 2.3.3.
Sent from my Nexus One using XDA Premium App
DownloaderZ said:
All,
I have updated to 2.3.4, lost root as expected
Click to expand...
Click to collapse
This was the same lesson I learned when I rushed in with Froyo --> GRI40 update the moment it became available. I lost my root and had to wait for Gingerbreak release. Now when they release OTAs, I wait until I understand how to keep the root under the new update before accepting it. Seems like a better approach to me.
Sent from my Nexus One using XDA App
GnatGoSplat said:
I'm sure there's a better, faster, more direct way, but here's how I went from 2.3.4 stock to 2.3.4 rooted without unlocking the bootloader.
1. Flash FRG33 as passimg.zip on SD card.
2. Flash FRG33 to GRI40 as update.zip on SD card using stock recovery.
3. Root GRI40 2.3.3 using Gingerbreak.
4. Install ROM Manager app and install Clockworkmod Recovery.
5. Open GRI40 to GRJ22 update zip file and REMOVE Recovery folder from it.
6. Boot into Clockworkmod Recovery and flash modified update.zip from step 5.
7. Install SU.zip from Clockworkmod right.
Voila! Rooted GRJ22 2.3.4 with locked bootloader. Lot of steps, but I don't think it took more than 10-15 minutes.
Click to expand...
Click to collapse
I'm looking to download all the files for this so I'm set from the start. I found FRG33 here but I haven't found the GRI40 update yet (although I haven't really looked yet either, that's not my question). I'm wondering, the site I listed has FRG83 as well as 33, does it matter which to use? 33 mentions a possible error.
What's the deal?
Thanks,
I think you should be able to use FRG83 instead. All you really need is something that can be named passimg.zip installed by the bootloader itself.
I got the GRI40 update from here:
http://android.clients.google.com/p...b119f8.signed-passion-ota-102588.656099b1.zip
GRI22 update:
http://android.clients.google.com/p....signed-passion-GRJ22-from-GRI40.71d2f9ec.zip
That sucked!!! I lost all my settings and apps when I moved back to froyo?? I wasn't expecting that
Oh yeah, I forgot about that. Flashing PASSIMG.zip wipes out everything because it's a full flash.
brettbellaire said:
That sucked!!! I lost all my settings and apps when I moved back to froyo?? I wasn't expecting that
Click to expand...
Click to collapse
There is no way to downgrade Android without wiping everything, as a downgrade is only possible with leaked shipped ROMS (i.e., ROMs that re-write the entire NAND flash memory on the device...
droidexplorer said:
This was the same lesson I learned when I rushed in with Froyo --> GRI40 update the moment it became available. I lost my root and had to wait for Gingerbreak release. Now when they release OTAs, I wait until I understand how to keep the root under the new update before accepting it. Seems like a better approach to me.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
I do that as well now. However I have some steps I figured out that work for me. It's more direct (only 2 flashes, plus su), but you have to pay attention. If you didn't already have a CWM backup though, it will wipe everything:
1) Flash to FRG33 using PASSIMG_Passion_Google_WWE_2.16.1700.1_FRG33_release_signed.zip (rename to PASSIMG.ZIP), takes you to 2.2
2) Root using Super-One-Click
3) Install ROM Manager and flash CWM
4) Flash b90257ed8cd3.signed-passion-GRJ22-from-FRG33-121341.b90257ed.zip, takes you directly to 2.3.4
5) DON'T LET PHONE REBOOT into Android, go to recovery then Flash su-2.3.6.1-ef-signed.zip
6) Remove/rename /system/etc/install-recovery.sh via ADB
7) If you have a recent backup, use CWM to 'advanced restore' the data portion.
8 ) Profit! (or root)
Step 5 may require explanation:
Android will reboot at least once during the flash, this is ok, as it loads right back into recovery. However after the second reboot, it will boot normally. You must INTERRUPT this boot process (hold power button, battery pull, etc). At this point CWM is still on there (don't know why, I thought flash was going to wipe it).
The reason you have to interrupt the boot process (for anyone who doesn't know) is because of the install-recovery.sh script. Stock android will automatically flash the stock recovery on bootup.
So boot into CWM, then flash su. After bootup up again, CWM will be gone, but we have root! So remove (I renamed) that file (/system/etc/install-recovery.sh), then reflash CWM using ROM Manager.
EDIT: After posting this, I had a thought: it should be possible to remove install-recovery.sh via CWM using ADB. That would remove the step of reflashing CWM a second time. I updated the step-by-step, but left the explanation as-is.
When I originally wrote these steps a few months ago, gingerbreak wasn't released. So I don't rely on it.
Just wondering, but would you always be safe and able to root by flashing SU.zip if you just never let it overwrite the custom recovery?
I thought you can always pull out the Recovery folder from the update zip file and it won't overwrite your custom recovery. Granted, that will require you to download updates manually rather than OTA, but that's easy enough.
GnatGoSplat said:
Just wondering, but would you always be safe and able to root by flashing SU.zip if you just never let it overwrite the custom recovery?
I thought you can always pull out the Recovery folder from the update zip file and it won't overwrite your custom recovery. Granted, that will require you to download updates manually rather than OTA, but that's easy enough.
Click to expand...
Click to collapse
In theory. It does seem to work for other devices (gTablet). I haven't had much luck with modifying the updater-script inside the zip file however. Whenever I change one, I get errors when I flash the zip. That's why I haven't tried that method.
I wanted to make my own flashable zips to tweak ROMs on my own, but never could get it to work, so I abandoned my work.
In addition though, you could just try to replace the recovery.img in the zip file with CWM. That might work too, as long as signature verification is off. I don't remember if I tried that.
EDIT: Forgot one key thing: Doing this won't prevent the OS from reflashing the stock back anyway on bootup (using install-recovery.sh). You MUST remove that file regardless, if you're on a stock ROM. If you want to remove that from the zip you can, but again requires updater-script changes. However if you want to OTA, then I'd recommend just renaming it, since some OTA's update that file. That way you can rename it back for the update.
On the GRI40 to GRJ22 update, I didn't have to do anything too complicated like modifying scripts. I simply yanked the Recovery folder out of the update and that seemed to do the trick with no error messages and CWM still intact.
How many of you have tried updating to a new firmware and you got the yellow exclamation mark?
Well, you probably have a combination of these modifications:
Custom Kernel
ClockworkMod Recovery
Rooted
If you have any of these, this is what you should do.
First, download and run this ONLY FOR INSTALLING/UNINSTALLING STOCK/CLOCKWORKMOD RECOVERY. - Thread
Read the instructions on how to boot into APX Mode.
Backup your /data with CWM.
After you have backed up your data, you should restore the STOCK ROM of your device.
When you get an update, it /should/ complete without any errors.
DO NOT DO ANYTHING TO THE ROM AT THIS POINT.
Alright. So at this point, you should have a completely stock, updated ROM.
Here are the next steps.
DO NOT ROOT YOUR ROM. DO NOT CHANGE A KERNEL.
Boot into APX Mode.
Make a backup of the STOCK Recovery. (Download From Linked Thread If You Haven't.)
Reboot into APX Mode.
Install ClockworkMod Recovery. (Using Brk's RootKit Script.) Once again. Without Rooting. Without changing the kernel.
Update ClockworkMod Recovery to 3.2.0.1. - Thread
Make a backup of EVERYTHING. (boot, system, data, cache, sd-ext).
After the backup is complete, you can ROOT and install a custom Kernel.
When You Get A New Update: DO NOT INSTALL. DO NOT POSTPONE.
Boot into ClockworkMod Recovery.
Restore the stock Boot.
Restore the stock System.
Boot into APX.
Restore stock recovery. (Using Brk's RootKit Script.)
Now everything should be back to stock.
Your data should still be intact.
When you apply the update, it should complete without a hitch.
Complete these steps again to be ready for the next update.
Cheers.
Thanks !! This did the trick for me. Had previously un-rooted and lost the update. Couldnt get it back until I did this !
I have a question.
I used the root method mentioned above a few weeks ago and everything went perfectly. I did not install CWM, only root.
I used the Netflix hack but managed to erase the original lib file.
I received the update and got the yellow exclamation point.
Last night I used BRK's pure root method and attempted to restore boot image and recovery image hoping it would return my lost lib file. I did not attempt to unroot.
When you mention "stock rom", where do I find the stock US rom?
I have an Epic 4G and run custom roms but I think the Transformer is fine and honestly don't care about root now that Netflix and ad-hoc appear to be working. I would like to end up with a stock Transformer that receives regular updates.
Is this the method for me, or something else?
Thanks
bmcgarry67 said:
I have a question.
I used the root method mentioned above a few weeks ago and everything went perfectly. I did not install CWM, only root.
I used the Netflix hack but managed to erase the original lib file.
I received the update and got the yellow exclamation point.
Last night I used BRK's pure root method and attempted to restore boot image and recovery image hoping it would return my lost lib file. I did not attempt to unroot.
When you mention "stock rom", where do I find the stock US rom?
I have an Epic 4G and run custom roms but I think the Transformer is fine and honestly don't care about root now that Netflix and ad-hoc appear to be working. I would like to end up with a stock Transformer that receives regular updates.
Is this the method for me, or something else?
Thanks
Click to expand...
Click to collapse
You should go here: http://tabletroms.com/forums/transf...stock-3-2-recovery-roms-unbricking-tools.html
Make sure you backup your data for your applications and the internal sdcard. They will be erased.
Install the 8.4.4.5.
Then you should go here and update to the latest version they have available.
Follow the instructions for this.
http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#download
Select Android and download your firmware.
Then you should get your update working after that.
Use this guide, then restore your data using clockworkmod.
Thanks and follow up
The Dark Lestat said:
You should go here:
Make sure you backup your data for your applications and the internal sdcard. They will be erased.
Install the 8.4.4.5.
Then you should go here and update to the latest version they have available.
Follow the instructions for this.
Select Android and download your firmware.
Then you should get your update working after that.
Use this guide, then restore your data using clockworkmod.
Click to expand...
Click to collapse
I just had a couple of questions?
You mentioned updating to 8.4.4.5, them updating to 8.6.5.6.
They have the NVFlash with 8.6.5.6. Has that changed since you advised me or should I do it in 2 steps?
Do I download the Asus Rom to the transformer or download to computer, then copy to SD card to install?
Now, I just noticed that 8.6.5.9US is available from Asus. Does this change my procedure?
Thanks again
bmcgarry67 said:
I just had a couple of questions?
You mentioned updating to 8.4.4.5, them updating to 8.6.5.6.
They have the NVFlash with 8.6.5.6. Has that changed since you advised me or should I do it in 2 steps?
Do I download the Asus Rom to the transformer or download to computer, then copy to SD card to install?
Now, I just noticed that 8.6.5.9US is available from Asus. Does this change my procedure?
Thanks again
Click to expand...
Click to collapse
When I NVFlashed to 8.6.5.6, I could not receive the update.
Since I used the file from Asus to update, it enabled FOTA somehow.
Anyways, the guide is the same.
If 8.6.5.6 is available, then you can NVFlash 8.6.5.6, then download and update to 8.6.5.9
Thank you.
I NVFlashed to 8.6.5.6 and wiped everything.
The FOTA arrived immediately and updated flawlessly.
Thanks again
Is this update even worth unrooting then root again?
it does fix the issue with browser shortcuts. You no longer have to rotate the screen.
I have not played with it. But it is said to allow Netflix and adhoc without root and patches. Those were the 2 reasons that I rooted.
Why jump through all these hoops?
Step 1: Download the clockworkmod update posted.
Step 2: Flash it.
daoist said:
Why jump through all these hoops?
Step 1: Download the clockworkmod update posted.
Step 2: Flash it.
Click to expand...
Click to collapse
Because if you do that, for some reason, FOTA doesn't enable.
AND you will have to wait for a flashible zip to become available.
Not hoops.
I've already tested that route. It didn't work for me.
bmcgarry67 said:
I have not played with it. But it is said to allow Netflix and adhoc without root and patches. Those were the 2 reasons that I rooted.
Click to expand...
Click to collapse
Has this been verified?
pigskins said:
Has this been verified?
Click to expand...
Click to collapse
Verified.
Netflix and Adhoc work WITHOUT root.
No need to root for those two options.
I personally root because of Titanium Backup.
Even if I have CWM installed.
The Dark Lestat said:
Verified.
Netflix and Adhoc work WITHOUT root.
No need to root for those two options.
I personally root because of Titanium Backup.
Even if I have CWM installed.
Click to expand...
Click to collapse
TY!
Did you root after getting the update and if so, how? Did you follow the steps in this thread?
pigskins said:
TY!
Did you root after getting the update and if so, how? Did you follow the steps in this thread?
Click to expand...
Click to collapse
Yes. The thread that I posted has all the updated CWM and Root methods. You can use those to root.
The Dark Lestat said:
Because if you do that, for some reason, FOTA doesn't enable.
AND you will have to wait for a flashible zip to become available.
Not hoops.
I've already tested that route. It didn't work for me.
Click to expand...
Click to collapse
Why do you want FOTA enabled?
Why be bothered when a release that won't work (without jumping through hoops) is available?
The whole point of installing CWM is that you're going to be managing your tablet rather than letting ASUS do it. If you're going to unroot, FOTA, and reroot every time, just leave it unrooted.
I had successfully update my transformer through OTA without doing all those steps. I just had to root it again after update is done.
daoist said:
Why do you want FOTA enabled?
Why be bothered when a release that won't work (without jumping through hoops) is available?
The whole point of installing CWM is that you're going to be managing your tablet rather than letting ASUS do it. If you're going to unroot, FOTA, and reroot every time, just leave it unrooted.
Click to expand...
Click to collapse
You don't have to root to use CWM. FOTA won't work with CWM.
I use Root only for setCPU and Titanium.
I like getting the update as soon as possible. Not waiting a couple days for it.
Sei911 said:
I had successfully update my transformer through OTA without doing all those steps. I just had to root it again after update is done.
Click to expand...
Click to collapse
If you just rooted and did not make any changes to the system, then in theory, it should work. Depending on the root method.
Much thanks for boykloy
Follow his instructions here
http://forum.xda-developers.com/showpost.php?p=20393465&postcount=14
For me I just extracted the root.zip from ics+root-fastboot-recovey.zip and flashed that in cwm recovery. Apps are now given root access even when they were not given in 2.3.6
---------------------------------- below this is old information and only work partially --------------------
I posted this on the main ics upgrade thread but think it will be lost in the thread really soon. http://forum.xda-developers.com/showpost.php?p=20388165&postcount=739
This is what I did
Ok I finally bit the bullet and did it.
01. Recovery wipe everything including factory reset Flash 2.3.6
02. reboot, login to market
03. reboot recovery, flash su
04. reboot to 2.3.6 again, download otaRootKeeper, open up said app
05. Click Protect root
06. Reboot to recovery/bootloader, I forgot if it went direct to recovery or had to bootloader flash the img, anyway onto recovery
07. flash the update to ics did not wipe anything what so ever
08. Boot into ics
8a open up otaRootKeeper
8b click restore root or whatever the button at the bottom is
09 Superuser now seems to acknowledge titanium backup and allows root.
Try it out guys, works for me. Going to try and test other apps that needs su.
Click to expand...
Click to collapse
All thanks goes to SuperCurio, the super dev for his otaRootkeeper app.
Works for me **** partially
So I did a little more testing, it seems that whatever you have allowed to access root when you were in 2.3.6 will be ok when you go to ics, and nothing extra will be allowed in ics
Do you have a step missing between these two?
08. Boot into ics
09 Superuser now seems to acknowledge titanium backup and allows root.
Click to expand...
Click to collapse
(i.e. copy the 'su' binary back from the backup directory to step #05 copies it into?)
If not, steps 05-06 aren't needed... The 'su' binary and Superuser.apk app simply remain untouched by the update from 2.3.6 to 4.0.3 since no wipe/factory reset was done.
rub1k said:
Do you have a step missing between these two?
(i.e. copy the 'su' binary back from the backup directory to step #05 copies it into?)
If not, steps 05-06 aren't needed... The 'su' binary and Superuser.apk app simply remain untouched by the update from 2.3.6 to 4.0.3 since no wipe/factory reset was done.
Click to expand...
Click to collapse
heh you are right, in my happiness, i derped
..
8a open up otaRootKeeper
8b click restore root or whatever the button at the bottom is
..
-------------- updated OP
Flashing su gives me an error of signature verification failed. Plz help
Doesn't work for me. Still not rooted.
same problem for me
doesn't work
The Alliance Needs You!
Help us Obi Wan, you're our only hope!
Hey guys,
Just finished loading up all the apps from titanium backup and then see this.
Did a little more checking and it seems that whatever you have allowed root access when you are in 2.3.6 will carry through onto ics. It seems that nothing new can be allowed access when you flash ics.
I am going to try to update the su and superuser.apk and see if that helps. Do not really want to go through the whole restoring on 2.3.6 THEN restoring on ics. I guess this is the life of a crack flasher, eh?
***** update even later, its a no go on everything I tried. so it seems that according to jishnu7 http://forum.xda-developers.com/showpost.php?p=20389400&postcount=770 ... although this gives me an idea.... be back soon
**** nope the idea did not work
So heres what I am thinking. If superuser.apk was backed up when you are in the 2.3.6 stage and when you get to ics, you might be able to retain the root access for the different apps that have already been granted. Anyone care to test it out, I am tired from flashing and reflashing, have done it at least 5 times now testing this.
I will lay the steps out below if you are interested to test it out. The only additional steps is 5a and 5b. I am too lazy to test it, tired too. I am betting that by tomorrow superuser.apk or su will be updated and this will not be needed.
01. Recovery wipe everything including factory reset Flash 2.3.6
02. reboot, login to market
03. maybe need to flash the img from bootloader to reboot into cwm recovery, flash su (Superuser-3.0.7-efgh-signed.zip)
04. reboot to 2.3.6 again, download otaRootKeeper, open up said app
05. Click Protect root
5a restore everything that you use that needs root
5b allow access for those said apps
06. Reboot to recovery/bootloader, I forgot if it went direct to recovery or had to bootloader flash the img, anyway onto recovery
07. flash the update to ics did not wipe anything what so ever
08. Boot into ics
8a open up otaRootKeeper
8b click restore root or whatever the button at the bottom is
09 Superuser now seems to acknowledge titanium backup and allows root.
my titanium still not working on the ics as others said su need to be update. titanium works under 2.3.6 so i restored all the apps then apply the ics update without wipe
Burninator said:
Help us Obi Wan, you're our only hope!
Click to expand...
Click to collapse
The dark side has clouded everything. Hard to see, the future is.
I created a .zip (CWM) for root access, thanks to zdo: http://www.megaupload.com/?d=S67I9Q0L
Finally root access
Ok i have finally done it.
Instuctions:
* flash the 2.3.6 stock rom
* sign in with google account
* reboot into stock recovery -do not wipe anything
* install update zip ( ICS ROM)
* Let it boot into ics
*Enable usb debugging and connect the usb cable
*Download this : http://www.multiupload.com/BZ5A87HYIG
*Extract it to dectop of your pc
* ran the run.bat
* follow instrunctions
* REBOOT.NOW YOU HAVE ROOT ACCESS AND RECOVERY
Ok I finally bit the bullet and did it.
01. Recovery wipe everything including factory reset Flash 2.3.6
02. reboot, login to market
03. reboot recovery, flash su
04. reboot to 2.3.6 again, download otaRootKeeper, open up said app
05. Click Protect root
06. Reboot to recovery/bootloader, I forgot if it went direct to recovery or had to bootloader flash the img, anyway onto recovery
07. flash the update to ics did not wipe anything what so ever
08. Boot into ics
8a open up otaRootKeeper
8b click restore root or whatever the button at the bottom is
09 Superuser now seems to acknowledge titanium backup and allows root.
Try it out guys, works for me. Going to try and test other apps that needs su.
Click to expand...
Click to collapse
Actually this works, or at least it worked for me with some minor changes
Things I did differently:
I did all flashing with ClockworkMod, by "fastboot-linux boot recovery3101.img" or which in your case should prolly be "fastboot boot recoveryXXX.img"
03. reboot recovery, flash su
Click to expand...
Click to collapse
*Please realize su is the problem here, as even if you get a message that your root was successful that wasn't the case, as su isn't giving out the permissions.
*I rebooted recovery, and I flashed su, but I flashed it with "Superuser-3.0.7-efgh-signed" (just Google it and you'll find it available for download)
*To give more insight, when it comes to "controversy" around step 6, what I did as part of step 5 after I protected my root I also flashed ClockworkMod recovery. And without rebooting installed the ICS.
*Btw, when it asked me if I wanted to remove anything, I only selected Dalvik Cache, as by also removing data I would lose my previous su "status"
*Either way, after I booted into ICS I successfully restored my root. Also, make sure you don't allow Google to restore your installed applications, as it'll restore different version of su and ruin this whole effort.
boykioy said:
Ok i have finally done it.
Instuctions:
* flash the 2.3.6 stock rom
* sign in with google account
* reboot into stock recovery -do not wipe anything
* install update zip ( ICS ROM)
* Let it boot into ics
*Enable usb debugging and connect the usb cable
*Download this : http://www.multiupload.com/BZ5A87HYIG
*Extract it to dectop of your pc
* ran the run.bat
* follow instrunctions
* REBOOT.NOW YOU HAVE ROOT ACCESS AND RECOVERY
Click to expand...
Click to collapse
so new apps that require root can have access? Nice work if it does? Can anyone else confirm?
*Please realize su is the problem here, as even if you get a message that your root was successful that wasn't the case, as su isn't giving out the permissions.
*I rebooted recovery, and I flashed su, but I flashed it with "Superuser-3.0.7-efgh-signed" (just Google it and you'll find it available for download)
*To give more insight, when it comes to "controversy" around step 6, what I did as part of step 5 after I protected my root I also flashed ClockworkMod recovery. And without rebooting installed the ICS.
*Btw, when it asked me if I wanted to remove anything, I only selected Dalvik Cache, as by also removing data I would lose my previous su "status"
*Either way, after I booted into ICS I successfully restored my root.
Click to expand...
Click to collapse
But for me when i go into adb, I am able to get to su and it works. Does this still mean that su is the problem? I did use Superuser-3.0.7-efgh-signed
suomaf said:
so new apps that require root can have access?
Click to expand...
Click to collapse
i install titsnium and root explorer and remount system normally as you can see from the picture
Chamb' said:
I created a .zip (CWM) for root access, thanks to zdo: http://www.megaupload.com/?d=S67I9Q0L
Click to expand...
Click to collapse
Thank You! It worked!
Chamb' said:
I created a .zip (CWM) for root access, thanks to zdo
Click to expand...
Click to collapse
I had to manually update Superuser through the markat as the one in your zip kept force closing, but it works perfectly after that - root access back!
Chamb' said:
I created a .zip (CWM) for root access, thanks to zdo: http://www.megaupload.com/?d=S67I9Q0L
Click to expand...
Click to collapse
Works! Only issue I have is Superuser doesn't appear to be working properly...it allows every su request without prompt.
OK, for starters:
Tablet's current stats:
ROM: CWM-Rooted_Acer_A500_7.006.01_COM_GEN2
Recovery: Stock US 1.141.07_COM_GEN1
Root status: Rooted
Problem at hand: Cannot install OTA updates. I used Acer Recovery Installer to originally install CWM so I could flash ROMs (duh). So I used Acer Recovery Installer to have it install the stock recovery image so I could actually install the OTA updates. I know this likely means I would lose root, and that is OK.
When I installed the stock recovery back, I tried to let it install the update. It would reboot, show the package opening (little box that was open and a progress bar showed up). The bar got about 25% completed, then it changed into a triangle with a "!" inside it, and the little Android dude below it. After a few minutes, it would reboot by itself. Once booted up, I would get a message that simply said "Update Failed".
I brought this up in another thread, and someone suggested I unroot as well. I immediately tried to do that, but IconiaRoot gives me the following:
Removing superuser.apk
Removing /system/xbin/su
Sleeping in 5 seconds...
Something went wrong.. you are still root?!?!
I can confirm I am still rooted by going into terminal emulator and running su and I get a # sign. So I am at a loss now on what else to try. With the stock recovery, if I tell Acer Recovery Installer to reboot into recovery, when it reboots, all I get is the triangle with a "!" in it. I noticed the ROM has GEN2 and my stock recovery has GEN1, and the OTA update ends with GEN2, is that an issue?
EDIT: I also know now there are other rooted ROMs with these OTAs applied. I'd like to unroot and go back to stock, so please do not recommend this.
Ok did you make a backup via CWM ?
In the other thread the recovery i restored was the backup i made of my one via Acer recovery,
If i was you i would reinstall CWM and make sure that recovery is working then wait for someone to come in and tell you the correct stock recovery for your one is.
oh i get u now, u got the gen2rom installed and u want back to your own stock gen1 to get the OTA, correct?
u need a cwm backup of 3.2 gen1 stock, when u restore it, u should receive an OTA notification for the 3.2.1 GEN1 OTA. Before you download it, u need to be rooted, use the backdoor/OTA method of timmyDeans. It will create a backdoor so after you have installed the OTA you can get in to run the installtools command again to root and install cwm again. AND you will still recieve OTA's.
Iconia Root - only works on 3.1, it will not work for 3.2, so it will throw an error.
But i'm sure root wont prevent the install as the OTA overwrites system files and resets the permissions, it also checks all system apps are there, so if you;ve deleted any bloatware or changed build.props the update will fail.
I have spent the last week trying to get back to stock so i can OTA. I have read hundreds of posts and tried all the methods that had been posted. The easiest and quickest and most successful way of achieving this was the backdoor method. Yes you need adb installed but you dont actually use it, it is all done for you. there is a very good walkthrough here http://www.chdcomputers.gr/en/mnu-kb-en/mnu-kb-android-en/mnu-kb-android-devices-en/mnu-kb-android-a500-en/254-art-kb000005-en
Then install the backdoor v3 (link in sig) -have a look and see if that will get u to where u wanna be!
Decideed it was easieeer to just install one of the prerooted roms from the dev forum. Running 7.014.14.com gen 1 now. Thanks guys.