Related
I am selling my phone soon, so I downloaded RUU, did that, then installed the OTA update (4 mb file)
It was all successfull and the phone works.. Does that mean the Phone is back to stock condition (with origional recovery rom etc?)
i ask because when I hold power and home I get the exclamation mark in a triangle... Thanks,
Anthony
Yes.
And probably unrootable to boot
The instant root apk works with the new FOTA update, so no worries.
I have rerooted my phone with instant root, recovery flasher to get amon-RA's image. And flashed the pre-rooted stock rom from modaco's site.
dont worry
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.
Could someone please point me in the direction of where I can get the Evo 4G 4.22 stock recovery image?
Stock recovery is no recovery,what exactly are you looking for?
Sent from my PC36100 using XDA App
I am rooted and have CWM installed. I am looking to put back the stock 4.22 recovery so I may install the the 4.24 OTA update.
I like to keep my Rom stock and prefer to install updates via OTA.
If you take the 4.24 OTA you will no longer be "rooted" Look for one of the rooted ROMs and flash it
Yeah,what he said
Sent from my PC36100 using XDA App
I am using the Unrevoked root method and no update (3.70,4.22) to date has unrooted my phone.
I have simply been restoring the current version of the stock recovery, which I have previously found on the internets, and then running the OTA update as normal. Once done I install CWM and the latest SU updates. Works great.
I would like to perfrom this method once agian to install the 4.24 update and all I need is the 4.22 stock recovery.
If you don't want to be rooted anymore, then just accept the OTA - it'll override your current recovery with the stock recovery, which is actually a lack of recovery.
But as others have said, you won't be able to root again unless you've ran unrevoked or unrevoked forever and remain s-off. In that case, you'll have to flash a recovery and then flash the rooted version. So if you want to stay rooted, you might as well go ahead and do that. You should be able to just wipe cache and dalvik and install, so the end result will be the same but you'll be rooted.
I hope that made sense...
(from... Evo/MIUI/Tapatalk)
kc8emd said:
Could someone please point me in the direction of where I can get the Evo 4G 4.22 stock recovery?
Click to expand...
Click to collapse
You probably want this:
http://forum.xda-developers.com/showthread.php?t=1133379
This is the actual update, but rooted, so you can keep your CWM recovery, get the latest update that was made OTA, but remain rooted. You don't want to just accept the OTA if prompted, your root will go away.
Once you've downloaded it (and the radio update as well), follow the instructions here:
http://forum.xda-developers.com/showpost.php?p=14933526&postcount=31
Thats the problem. I cannot install the OTA 4.24 update with CWM installed, nor can I install the update manually, via renaming and then update method, as it will error out during install.
OTA updates will only install if the proper stock verion of recovery in installed, hence I really need the 4.22 recovery.
Installing OTA updates when using Unrevoked does not change S-OFF, it only overwrites SU which can be easily reinstalled. I know as I rooted my evo way back when it was version 3.26 using unrevoked 3 and have installed every OTA update since using this method and still have S-OFF
Thanks, but I do not need to go that route. My method will update as normal and I wont have to wipe my phone.
dmolavi said:
You probably want this:
http://forum.xda-developers.com/showthread.php?t=1133379
This is the actual update, but rooted, so you can keep your CWM recovery, get the latest update that was made OTA, but remain rooted. You don't want to just accept the OTA if prompted, your root will go away.
Once you've downloaded it (and the radio update as well), follow the instructions here:
http://forum.xda-developers.com/showpost.php?p=14933526&postcount=31
Click to expand...
Click to collapse
kc8emd said:
Thanks, but I do not need to go that route. My method will update as normal and I wont have to wipe my phone.
Click to expand...
Click to collapse
And you won't be rooted anymore. There are only about 3 thousand posts telling people this, and most AFTER they found out the hard way. There are stock Rooted ROMS based on the recovery, as in STOCK! but still rooted, and up to date.
BTW, there are also a lot of posts detailing how the OTA made their phones worse, but if you want to be a hard head, go ahead and bury yourself, but don't come back crying when you figure out.
how come every other incompetent noob can manage to get their phone back to stock and permanently locked/unrooted, yet I cannot manage this feat intentionally?
if I intentionally flash the 4.22 zip from shipped-roms will this eliminate my root and recovery?
well install the 4.22 update from recovery didn't work... it aborted with some error.
ARGHHH!!! SOMEONE HELP ME LOCK MY PHONE PLEASE!!!
I appreciate the heads up, but if done correctly, it does work and has worked great for me the past few OTA updates.
I am aware of all the potential problems and am not the only one successfully installing OTA updates on a rooted evo and staying rooted.
HipKat said:
And you won't be rooted anymore. There are only about 3 thousand posts telling people this, and most AFTER they found out the hard way. There are stock Rooted ROMS based on the recovery, as in STOCK! but still rooted, and up to date.
BTW, there are also a lot of posts detailing how the OTA made their phones worse, but if you want to be a hard head, go ahead and bury yourself, but don't come back crying when you figure out.
Click to expand...
Click to collapse
Bottom line is if you change back to S-ON, and apply the OTA you lose root forever (or until Unrevoked finds a new backdoor). If you leave S-OFF then you can downgrade, and reload a recovery. The stock ROM's you'll find here (ex. Sprint Lover's) are stock, and rooted. They pretty much the same thing you get over the air. Don't be a lid..
I downloaded a from shipped roms the last rom for my evo and downloaded the s-on tool. Ran the tool then connected my phone to the computer and ran the RUU i donloaded. Fully stock unrooted locked phone
I am a noob
First learn the correct terminology for what you are tying to achieve. There is no 4.22 recovery that you can just flash, there is a 4.22 ROM and a 4.22 RUU.
Then check out the WIKI and FAQs these both contain the info you are looking for .
Not trying to be mean. Just do some research before you mess up your phone and come here asking for stuff that doesn't exist.
4.22 ROM = just the ROM
4.22 RUU = .exe that runs on your PC to FLASH your PHONE with new radio, recovery, hboot, rom, etc
exabrial said:
well install the 4.22 update from recovery didn't work... it aborted with some error.
ARGHHH!!! SOMEONE HELP ME LOCK MY PHONE PLEASE!!!
Click to expand...
Click to collapse
http://shipped-roms.com/index.php?category=android&model=Supersonic
http://unrevoked.com/rootwiki/doku.php/public/forever
cddmh said:
I downloaded a from shipped roms the last rom for my evo and downloaded the s-on tool. Ran the tool then connected my phone to the computer and ran the RUU i donloaded. Fully stock unrooted locked phone
I am a noob
Click to expand...
Click to collapse
Well said
This is what you want to do to get to the latest OTA STOCK no root
* if you leave S-Off you can re-root *
Hi
I have a rooted nexus S. When i first rooted it i had this issue
http://forum.xda-developers.com/showthread.php?t=1135929 and solved it using post #3.
Now when i get OTA updates the phone reboots and then the android icon with a package appears. the install begins but fails to and android with an exclamation mark icon.
I dont have logs because when i reboot the update isnt offered anymore for a really long time. does any one have any idea what could be wrong?
thanks in advance
The verify check has to complete and u need to flash it manually in custom recovery
I got this when I rebooted my NxS several times while the OTA was ready to be installed. It somehow got lost and couldn't be retrieved anymore.
As I couldn't find a solution I just reflashed the official 2.3.4 full rom and then got a) a working stock recovery and b) a working OTA again.
Official stock roms are signed and can be flashed via the stock recovery and don't need unlocked bootloader.
Thanks, i think i will wait for ICS and then reflash. I'm too lazy to do it all now and then again in a few months time.
Can you have permanent root with stock everything?
boozelclark said:
Thanks, i think i will wait for ICS and then reflash. I'm too lazy to do it all now and then again in a few months time.
Can you have permanent root with stock everything?
Click to expand...
Click to collapse
Depends on how you define "everything". You'll need at least an open bootloader to flash the superuser zip via a custom recovery(, can relock the bootloader afterwards).
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.