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.
Related
Full Rom link
http://android.clients.google.com/p...2cf141e6a.signed-soju-ota-102588.f182cf14.zip (89.9 MB)
Link for GRH78C
http://android.clients.google.com/p...9e.signed-soju-GRI40-from-GRH78C.98f3836c.zip
Link for GRH78 only
http://android.clients.google.com/p...2bf.signed-soju-GRI40-from-GRH78.e0b546c4.zip
As posted here by Matrik: http://forum.xda-developers.com/showpost.php?p=11616226&postcount=389
I figured I'd get this unburied for everyone interested (which is likely a lot of folks).
If you're stock and unrooted - download this and place it on the root of the SD card - named update.zip. Boot into recovery. Hold Pwr and then Vol up and then choose to apply update.zip.
just got it on mine too.
does anyone know if this build is still rootable in the same method of 2.3.2? just curious
krohnjw said:
http://android.clients.google.com/p...2bf.signed-soju-GRI40-from-GRH78.e0b546c4.zip
As posted here by Matrik: http://forum.xda-developers.com/showpost.php?p=11616226&postcount=389
I figured I'd get this unburied for everyone interested (which is likely a lot of folks).
Also Mirrored if the download breaks for some reason:
http://hotfile.com/dl/107285073/f39f21c/e0b546c442bf.signed-soju-GRI40-from-GRH78.e0b546c4.zip.html
Click to expand...
Click to collapse
WOW - didn't think I'd see this so soon - thanks for digging it out man.
Guess I'll be the guinea pig
jaker.the.skater said:
just got it on mine too.
does anyone know if this build is still rootable in the same method of 2.3.2? just curious
Click to expand...
Click to collapse
If your bootloader is unlocked then rooting is as easy as flashing CWM and flashing the SU binary.
If the bootloader is locked then the changelog indicates that you will not longer be able to use fastboot boot to load CWM and root that way.
With that said, I applied a lot of updates on my Nexus One without losing root and kept the boot loader locked the whole time. You'll need to pay attention, but you should be able to do the following.
Download the SU binary zip and place that on the SD card.
The OTA will not overwrite CWM until it actually boots. So, after you apply the OTA boot directly into recovery and apply the SU zip. This will give you root. (Just pay attention and hold vol up when it goes to reboot)
When you subsequently load up android CWM will be overwritten. At this point you can use the flash_image binary to manually flash CWM to recovery (or potentially ROM Manager).
ok my bootloader is unlocked. so basically i just do like before where you rename the install recovery.sh file so that cwm sticks? if so then cool beans.
jaker.the.skater said:
ok my bootloader is unlocked. so basically i just do like before where you rename the install recovery.sh file so that cwm sticks? if so then cool beans.
Click to expand...
Click to collapse
Yes sir. 10 chars
very cool.
Can i dowload this on a stock Ns
Sent from my Nexus S using XDA App
doesnt work for me - failed at file_getprop("/system/build.prop"
this update seems to be for build GRH78 - GRI40 ie 2.3.1 to 2.3.3
Im on 2.3.2 .......
any idea's???
moon-unit said:
doesnt work for me - failed at file_getprop("/system/build.prop"
this update seems to be for build GRH78 - GRI40 ie 2.3.1 to 2.3.3
Im on 2.3.2 .......
any idea's???
Click to expand...
Click to collapse
same here..... hmmm
krohnjw said:
If your bootloader is unlocked then rooting is as easy as flashing CWM and flashing the SU binary.
If the bootloader is locked then the changelog indicates that you will not longer be able to use fastboot boot to load CWM and root that way.
With that said, I applied a lot of updates on my Nexus One without losing root and kept the boot loader locked the whole time. You'll need to pay attention, but you should be able to do the following.
Download the SU binary zip and place that on the SD card.
The OTA will not overwrite CWM until it actually boots. So, after you apply the OTA boot directly into recovery and apply the SU zip. This will give you root. (Just pay attention and hold vol up when it goes to reboot)
When you subsequently load up android CWM will be overwritten. At this point you can use the flash_image binary to manually flash CWM to recovery (or potentially ROM Manager).
Click to expand...
Click to collapse
So what your saying is we can ( Possibly ) install 2.3.3 via the link with rooted devices with an unlocked bootloader ( if the 2.3.3 does not lock bootloader / root ) and then just re install superuser e.c.t and were away ?
Same here, update fails. I am on 2.3.2 and Stock non-rooted.
hutzdani said:
So what your saying is we can ( Possibly ) install 2.3.3 via the link with rooted devices with an unlocked bootloader ( if the 2.3.3 does not lock bootloader / root ) and then just re install superuser e.c.t and were away ?
Click to expand...
Click to collapse
Yes - if you're unlocked then you'll only need to remove the isntall-recovery.sh and reflash CWM/su and you're golden.
It's a bit trickier for users who rooted without unlocking the boot loader and do not want to unlock at this point.
Looks like this is for GRH78, NOT GRH78C- we'll have to wait for that package still.
Update is for build number GRH78 only :-(
Wow!
Thx)
SupaDupaFly24 said:
Update is for build number GRH78 only :-(
Click to expand...
Click to collapse
Yeah, that is, only for 2.3.1 until now.
We'll have to wait for the GRH78C (2.3.2) build update.
this really pisses me off. i was on 2.3.2 and i got the ota but when i tried to install it from cwm it didn't work. so then when i saw this one i gave up on the one i had and now its gone. turns out i should've just did a logcat and got the one for 2.3.2.
oh well it'll be up soon
Sweet. I was trying to get to stock ROM and i was on 2.3.1
2.3.3 Flashed just perfectly
I did a nandroid backup to 2.3.1 and then installed the update and it worked fine.
Please, Could you make step by step guide, how to apply update from that link on stock, nonroot device. Thanks.
Sent from my Nexus S using XDA App
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.
For those of you wondering why the S-OFF feature was worth your extra time to update, this is a prime example of why S-OFF kicks royal behind.
So here is the situation I was having. Friday morning, T-Mo showed me some love and sent me the Gingerbread update. I didn't have my morning coffee so I wasn't thinking strait and authorized the update. I forgot that it would probably interfere with good ol' ClockworkMod Recovery. Sure enough, it did. So, after the OTA failed due to the recovery, I haven't been able to get T-Mo to show me some OTA love again.
However, I had previously invoked the S-OFF feature when it was discovered how to.
After following the guide at http://forum.xda-developers.com/showthread.php?t=1202060 I found myself with a G2 using stock recovery and bone stock Gingerbread (S-OFF still invoked).
After some thought, I decided to do the following:
Flash ClockworkMod via the bootloader screen, and flash SU via the ClockworkMod screen.
Note: You can only do this if you have S-OFF! And since my guide writing skills are not so pristine, I'm assuming you have some sort of working adb/bootloader/recovery knowledge.
Save the attached files (PC10IMG.zip & su.zip) to your sdcard. Reboot into the bootloader either by using the adb command adb reboot bootloader or by powering off, and then holding Vol-Down+Power.
The bootloader will scan for PC10IMG.zip and then ask you if you want to flash the recovery. Yes! You do!
After this, reboot the phone. Reboot into recovery by using the adb command adb reboot recovery, or booting back into the bootloader and navigating to the Recovery console (if you didn't delete the PC10IMG.zip, bootloader will scan it, but don't let it update again, this is redundant).
Once you are in ClockworkMod, navigate to "install zip from sdcard", then to "choose zip from zip card". Select the su.zip file from the list, and authorize the recovery console to flash the zip. Reboot the phone.
Now, you will see the coveted SuperUser app in your drawer. I figured this was wayyyy to easy to have worked, so I tested some root dependent apps, they work flawlessly. I also used the adb command adb shell followed by su once in the shell. SuperUser requested my permission and after granting it, I am able to remove the bloatware that was replaced during the downgrade, also, rebooting the phone as normal and from a removed battery does not remove this root. So I'll say it's a permaroot.
I compiled the attached files specifically for this. The ClockworkMod Recovery version is 3.0.2.4, SuperUser version is 2.3.6.1.
Thanks!
It sounds like you started where I am: Clockwork Mod, S-OFF and stock Froyo 2.2.
Q. How did you follow the steps in the thread to get onto Gingerbread? Did you remove ClockworkMod? If yes, how did you revert to stock recovery? This is the step that I'm caught on, and can't find a thread regarding. Thanks!
Edit to add:
Did you unroot the phone using these steps?
If so, were you at all scared about the warning regarding PC10IMG.zip?
I ended up using the entire stock 2.2 PC10IMG which wiped clockwork off the phone to stock recovery. I didn't do anything to unroot, since the stock rom replaced recovery, system etc but left s-offf in tact.
ETA: I also didn't read either of those articles and wasn't aware of the bricking issue, I've done the phone flashing, modding and unbricking for about 2 years now and just used experience as a guide..
Sent from my T-Mobile G2 using Tapatalk
rdmerck said:
I ended up using the entire stock 2.2 PC10IMG which wiped clockwork off the phone to stock recovery. I didn't do anything to unroot, since the stock rom replaced recovery, system etc but left s-offf in tact.
ETA: I also didn't read either of those articles and wasn't aware of the bricking issue, I've done the phone flashing, modding and unbricking for about 2 years now and just used experience as a guide..
Sent from my T-Mobile G2 using Tapatalk
Click to expand...
Click to collapse
Okay, so just to verify, you flashed CWM recovery while running the GB update? When you adb shell you open a # prompt? I've been gfree s-off'd since I got my phone so even with the leak or otherwise I've been able to just reflash the stock 1.19/1.22OTA and reroot it but I didn't think to try flashing cwm while it's stock gb'd....so tempted.
I compiled the attached files specifically for this. The ClockworkMod Recovery version is 3.0.2.4, SuperUser version is 2.3.6.1.
Click to expand...
Click to collapse
So I sit down to write up a quick guide this morning and what do I find? Nicely done. Couple of points I wanted to add to why this works -
This method fixes the things that the OTA breaks for root: New stock hboot and stock recovery are flashed and on the rom side it wipes /system/xbin which breaks the su symlink.
Flashing the PC10IMG above fixes the recovery.
Flashing the superuser package reinstalls Superuser.apk, the su binary and fixes the symlink to xbin.
But, still not hboot-eng so your fastboot options are limited.
When I did this I had replaced the DZ engineering hboot.img in rmk's package with the G2 engineering hboot.img and edited android.txt for the new G2 build. This allows you to take care of both in once flash.
Hope this is useful to someone and thank you for saving me from writing a guide!
8/27/2011 Edit:
Realized ro.secure=0 so I repacked the stock boot.img from the 2.3.4 PC10IMG.zip with the below changes to default.prop. This allows use of the "adb remount" so files can be pushed to system folders without needing to go into terminal and mounting rw.
Code:
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
Modified installation instructions for full root:
Flash the PC10IMG.zip with the G2 engineering bootloader in this post
Flash the superuser update.zip in the OP
Extract the attached boot.img to the platform-tools directory
Remove the PC10IMG from your sdcard and reboot into bootloader
Select fastboot
Enter the following command in terminal or cmd:
Code:
fastboot flash boot boot.img
fastboot reboot
Kind Regards,
Kevin
zkid2010 said:
Okay, so just to verify, you flashed CWM recovery while running the GB update?
Click to expand...
Click to collapse
Yes. Just flash the PC10IMG and you have clockwork recovery again. However, you absolutely need SuperCID set while in froyo or this does not work.
Kind Regards,
Kevin
Confirm Here that it works...
Root and S-OFF
Gingerbread OTA 2.3.4
Thanks Guys for your help!
Flawless!
This worked flawlessly!!
I admire you so much for figuring this out!!
Thank you so much!
HELP!
sort of noobie here..
so i just updated my g2 to 2.3.4 following http://forum.xda-developers.com/showthread.php?t=1202060
and now i want to perm root my phone and overclock it but im having troubles.
1. how do i get clockworkmod installed? i know you can install this from rom manager but it requires root. right?
cause you said.. "Just flash the PC10IMG and you have clockwork recovery again"..
i tried flashing the PC10IMG.zip but got an error and says aborted.
any help please?
thanks in advance
If you are already on 2.3.4 and had not previously rooted then this thread will be of no use to you since your G2 does not have SuperCID (again, read the wiki.)
You will need to downgrade back to froyo (other threads on this and links in the wiki.) Once rooted, then install one of the rooted stock roms in this forum or follow this guide to reinstall the recovery and superuser (hboot optional.)
Hope that gets you going in the right direction.
Kind Regards,
Kevin
Sent from my T-Mobile G2 using Tapatalk
G2 Problems??
Hi, how can i get S-OFF on my g2 since it seems i can not generate a beta key from the revolutionary website cause g2 it's not in the drop down list, don't know what to pick and i want to be able to have my g2 rooted with android 2.3.. can somebody help me please?
Thanks.
Revolutionary is not available for the Desire Z/G2. Have you flashed the leaked 2.3.3 and trying to root? PM please.
Hey I notice most of the people in this thread are Americans - would this method work for the DZ or is it just for the G2?
Sorry if this is a noobish question.
Not a noob question, this one is new for me too. Fundementals are the same, process would be the same. I don't know if there is any issue using a PC10IMG with the info for a G2 (contained in the file called android-info) so may need rebuild one modified with DZ information.
Proceed with caution and do not do anything you are not 100% sure about.
Sent from my T-Mobile G2 using Tapatalk
I'll hold off on confirming the update in that case! I'm still on stock firmware, didn't apply the update from March either. When I've read enough to be confident on how to perma-root the current firmware I might risk following the method in this thread. Then I'll post back to let you know if it works on the DZ.
My DZ came with 1.34 firmware, I rooted it on this firmware. I accidentally upgraded it and am now on the OTA gingerbread ROM. Is this method suitable in this situation or do I require to flash a rooted stock ROM for this method to work.
Accidentally manually applied the OTA? Should work, you have a G2 now!
Sent from my HTC ThunderBolt using Tapatalk
Is there any newbie guide for how to do this? From getting Clockwork on there to getting this rooted 2.3.4 on. I have a rooted 2.2 with S-OFF right now, stock. Just don't really know what to do from this point on.
How to is in the OTA thread (which needs a helping of Iron Fist.) Come back here when ready to re-root.
Sent from my T-Mobile G2 using Tapatalk
rdmerck said:
Save the attached files (PC10IMG.zip & su.zip) to your sdcard. Reboot into the bootloader either by using the adb command adb reboot bootloader or by powering off, and then holding Vol-Down+Power.
The bootloader will scan for PC10IMG.zip and then ask you if you want to flash the recovery. Yes! You do!
After this, reboot the phone. Reboot into recovery by using the adb command adb reboot recovery, or booting back into the bootloader and navigating to the Recovery console (if you didn't delete the PC10IMG.zip, bootloader will scan it, but don't let it update again, this is redundant).
Once you are in ClockworkMod, navigate to "install zip from sdcard", then to "choose zip from zip card". Select the su.zip file from the list, and authorize the recovery console to flash the zip. Reboot the phone.
Now, you will see the coveted SuperUser app in your drawer. I figured this was wayyyy to easy to have worked, so I tested some root dependent apps, they work flawlessly. I also used the adb command adb shell followed by su once in the shell. SuperUser requested my permission and after granting it, I am able to remove the bloatware that was replaced during the downgrade, also, rebooting the phone as normal and from a removed battery does not remove this root. So I'll say it's a permaroot.
I compiled the attached files specifically for this. The ClockworkMod Recovery version is 3.0.2.4, SuperUser version is 2.3.6.1.
Click to expand...
Click to collapse
**** Im at the step above finally lol this is my first root and I had to downgrade, man Ive been doing this for hours and hours. My brain is fried LMAO **** I currently have my G2 with S-OFF and a stock Gingerbread 2.3.4. I have the PC10IMG.zip and su.zip in the root or directly in my sdcard. In no folders im trying to say... I reboot into the bootloader. The bootloader will scan for PC10IMG.zip and then ask you if you want to flash the recovery. Yes! You do!
Well when I do it it doesnt ask me to "flash the recovery" it says "Parsing....(SD ZIP)
(1) RECOVERY
Do you want to start the update?
<VOL UP> YES
<VOL DOWN> NO
I accept the update by pressing vol. up. It comes back and says Update comeplete... - OK
Press Power to Reboot
I reboot and get into clockworkmod it says click "install zip from sdcard" I click it and a little hat appears but it doesnt do anything from there. I let it set a couple of min but still nothing... I have to pull battery out to get it to reboot. help pls....
Sean...
I've been looking at the threads but so far I don't believe there's one that tells you what to do if you've actually installed the official OTA update?
I.e. I have an rooted 2.3.4 GT-I9023 with an unlocked bootloader. With no clockwork or anything, as to be honest the last time I used it (on my old HTC DHD) it made my phone unstable (the phone would sometimes boot up of its own accord and stop at the clockwork screen).
Does anyone know how to re-root the NS after it's installed the official OTA update without clockwork?
Thanks
Edit: Downloading the OTA update won't relock the boot-loader will it?
dccxviii said:
I've been looking at the threads but so far I don't believe there's one that tells you what to do if you've actually installed the official OTA update?
I.e. I have an rooted 2.3.4 GT-I9023 with an unlocked bootloader. With no clockwork or anything, as to be honest the last time I used it (on my old HTC DHD) it made my phone unstable (the phone would sometimes boot up of its own accord and stop at the clockwork screen).
Does anyone know how to re-root the NS after it's installed the official OTA update without clockwork?
Thanks
Edit: Downloading the OTA update won't relock the boot-loader will it?
Click to expand...
Click to collapse
You cannot get root back without a custom recovery. OTA will not relock the bootloader, you'll just lose root and custom recovery.
You need to flash custom recovery using fastboot, then flash superuser to get root back. There are plenty of guides in the stickies describing the process.
Ok, so i'm updated to 2.3.6 but of course have lost root (never had CWM to begin with on this phone). Anyone know where I can DL CWM (i'm assuming it needs to be flashed via platform-tools directory in the android sdk per normal) and the latest su file?
EDIT: nvm, I found the latest CWM and successful flashed (my method was correct). However I've not been able to find the latest superuser.zip to flash yet. Also, I don't know why ppl say to use the market as I don't see how that method can work. I've already got superuser installed from before I updated but that doesn't help me get root. Only flashing the zip from recovery (as I understand it) would. Which renders the market useless in this regard.
/confused
The superuser app checks to see if you have the latest superuser binary and will download and instalk it. Or download superuser from within rom manager.
Sent from my Nexus S 4G using xda premium
Ok..the binary update fails (because i don't have root) so it's chicken and egg as far as I can tell.
You where already told. Flash custom recovery via fastboot. Boot into it and flash su.zip Same way it was done prior to update to the ota. Same as it always was and will be.
dccxviii said:
Ok, so i'm updated to 2.3.6 but of course have lost root (never had CWM to begin with on this phone). Anyone know where I can DL CWM (i'm assuming it needs to be flashed via platform-tools directory in the android sdk per normal) and the latest su file?
EDIT: nvm, I found the latest CWM and successful flashed (my method was correct). However I've not been able to find the latest superuser.zip to flash yet. Also, I don't know why ppl say to use the market as I don't see how that method can work. I've already got superuser installed from before I updated but that doesn't help me get root. Only flashing the zip from recovery (as I understand it) would. Which renders the market useless in this regard.
/confused
Click to expand...
Click to collapse
You can find superuser zip here:
http://rootzwiki.com/showthread.php?231-Superuser-2.3.6.3-17-June-2011&
3rd one down, efgh.
Flash in custom recovery.
albundy2010 said:
You where already told. Flash custom recovery via fastboot. Boot into it and flash su.zip Same way it was done prior to update to the ota. Same as it always was and will be.
Click to expand...
Click to collapse
You've misunderstood what i'm after. Thanks for trying to help tho
irishrally said:
You can find superuser zip here:
http://rootzwiki.com/showthread.php?231-Superuser-2.3.6.3-17-June-2011&
3rd one down, efgh.
Flash in custom recovery.
Click to expand...
Click to collapse
Thanks! As far as I can tell you're the first with the link I was after the entire time.
EDIT: Bah, I get a signature verification error when applying the update >.<
dccxviii said:
You've misunderstood what i'm after. Thanks for trying to help tho
Thanks! As far as I can tell you're the first with the link I was after the entire time.
EDIT: Bah, I get a signature verification error when applying the update >.<
Click to expand...
Click to collapse
Turn off signature verification in CWM and try again.
irishrally said:
Turn off signature verification in CWM and try again.
Click to expand...
Click to collapse
Turns out that CWM got overwritten by stock android recovery. Re-flashing CWM and then flashing su did the trick. I'm rooted once more!
Thanks for your help kind sir!
Curious as to how to make CWM stick for next time tho *shrug*
dccxviii said:
Turns out that CWM got overwritten by stock android recovery. Re-flashing CWM and then flashing su did the trick. I'm rooted once more!
Thanks for your help kind sir!
Curious as to how to make CWM stick for next time tho *shrug*
Click to expand...
Click to collapse
You're welcome.
If you stick with a stock ROM then recovery will reflash every time you reboot. To prevent this you can go to system>etc, and change the file install-recovery.init to something else like install-recovery.init.bak.
I have seen misinformation regarding the ota process on the nexus s repeated so many times and its driving me nuts so I made this thread.
1. You CAN be rooted. Yes you can. Anybody that says otherwise is wrong
2. You can have a custom recovery and you SHOULD! Unless you're going to be running a logcat and trying to grab the ota URL when it first starts rolling out there is no need for stock recovery. In fact. You WON'T be able to install it manually on stock recovery. Yes you WON'T. If you're on stock recovery you either have to wait for it to be pushed to your device or flash custom recovery and flash the update zip manually. You CAN'T manually do it with stock anymore. Anybody that says otherwise is wrong.
3. Bootloader unlocked has no.effect.
4. I am not going into what rom you need on the phone or what else the updater script checks for. Since I don't see people constantly misinformed about it.
Lastly. If you're not unlocked (bootloader) now and not rooted with custom recovery you will NOT be able to flash jelly bean as soon as the ota update zip is posted. You will have to wait for it be pushed to your device or unlock and flash custom recovery..
"Real ota(?)" Is pushed by google and installs automatically, IMO.
Sent from my Nexus S using xda app-developers app
albundy2010 said:
I have seen misinformation regarding the ota process on the nexus s repeated so many times and its driving me nuts so I made this thread.
1. You CAN be rooted. Yes you can. Anybody that says otherwise is wrong
2. You can have a custom recovery and you SHOULD! Unless you're going to be running a logcat and trying to grab the ota URL when it first starts rolling out there is no need for stock recovery. In fact. You WON'T be able to install it manually on stock recovery. Yes you WON'T. If you're on stock recovery you either have to wait for it to be pushed to your device or flash custom recovery and flash the update zip manually. You CAN'T manually do it with stock anymore. Anybody that says otherwise is wrong.
3. Bootloader unlocked has no.effect.
4. I am not going into what rom you need on the phone or what else the updater script checks for. Since I don't see people constantly misinformed about it.
Lastly. If you're not unlocked (bootloader) now and not rooted with custom recovery you will NOT be able to flash jelly bean as soon as the ota update zip is posted. You will have to wait for it be pushed to your device or unlock and flash custom recovery..
Click to expand...
Click to collapse
1. Spot on, reading the update script it doesn't look for additional files. I said otherwise previously, my bad.
2. Also true. Updater script does no hash check on the two recovery files either, so even if you deleted /system/etc/install-recovery.sh it will still be fine. My bad also.
3. Spot on.
Thanks for this writeup albundy :good:
So I was running ics roms well before they came to my ns4g... I didn't bother with ota since there was already a port available almost immediately... that fixed most of the bugs we experienced with pre-ota ports...
My question is, I'm running RemICS UX v1.3... what would I need to do to get PTA when its available for our phones?
I'm sure they'll have a flashable rom almost immediately so this question might be null anyways... but it is good to know these things...
Sent from my Nexus S 4G using Tapatalk 2
ioplkj13 said:
"Real ota(?)" Is pushed by google and installs automatically, IMO.
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Yes, but the question is when that will happen. Google pushes updates in waves, it could take weeks before it gets pushed to your phone.
And all those people already getting anxious now how to prepare their phone for ota-push don't strike me as the waiting kind... in fact, it's really silly making all that fuzz now, still another 2 weeks before 4.1 gets released.
the1dynasty said:
My question is, I'm running RemICS UX v1.3... what would I need to do to get PTA when its available for our phones?
I'm sure they'll have a flashable rom almost immediately so this question might be null anyways... but it is good to know these things...
Click to expand...
Click to collapse
So far the NS4G always had to wait to get an official update, Sprint taking it's time. The first OTA's will probably be for 9020T/9023 again, different radio. So unless you are willing to wait, you need a custom-zip anyway, don't use the dl-link from Google that will be floating around in 2 weeks.
But to answer your question:
First OTA's have always been incremental updates, so one needed to be on prior stock-rom to apply it. (In this case: 4.0.4 stock -> 4.1 update)
Of course they could change it this time and release everything at once (full rom, factory images, all models), but I heavily doubt it.
I'm on stock 4.0.4 rooted with no custom recovery. The way i see it i have 2 options:
1. Make an OTA update. I will not lose any app or data, but what about the root? It will be lost?
2. Flash CWM and the flash the update zip. In this case the root is surely gonna be in the zip file, but what about the apps and data. Will i lose them?
grigri444 said:
I'm on stock 4.0.4 rooted with no custom recovery. The way i see it i have 2 options:
1. Make an OTA update. I will not lose any app or data, but what about the root? It will be lost?
2. Flash CWM and the flash the update zip. In this case the root is surely gonna be in the zip file, but what about the apps and data. Will i lose them?
Click to expand...
Click to collapse
Re #1: Yep, root will be lost. You shouldn't loose and app / data.
RE #2: You only loose data when you do 'wipe data' in CWM, which you should do when installing a new ROM.
If you install 'Titanuim Backup' you can back up and then later restore all your APPs. After you back up APPs, you will need to transfer these to a PC, and wipe the phone, install new ROM, and then transfer APP backups back to SD Card on phone, install them using Titanium Backup. The PRO version allows you to do this in batch mode (much quicker).
ac17 said:
Re #1: Yep, root will be lost. You shouldn't loose and app / data.
RE #2: You only loose data when you do 'wipe data' in CWM, which you should do when installing a new ROM.
If you install 'Titanuim Backup' you can back up and then later restore all your APPs. After you back up APPs, you will need to transfer these to a PC, and wipe the phone, install new ROM, and then transfer APP backups back to SD Card on phone, install them using Titanium Backup. The PRO version allows you to do this in batch mode (much quicker).
Click to expand...
Click to collapse
I have Titanium backup pro. But which method is the wiser?
OTA and reroot or update zip and re-install all apps?
@ re #2: why the transfer of backups to PC?! They're saved on sdcard, it never gets wiped automatically (except when unlocking boot loader). And there's no need to do it manually.
caliban2 said:
@ re #2: why the transfer of backups to PC?! They're saved on sdcard, it never gets wiped automatically (except when unlocking boot loader). And there's no need to do it manually.
Click to expand...
Click to collapse
Because, i will make a wipe data in order to get a clean install of the new ROM. In our case the 4.1 stock.
you don't have to wipe sdcard to get a clean install... but go ahead, it won't do any harm.
will I get the OTA?
So I've got cyanogen mod 9 on my nexus s with Clockwork mod bootloader will I get the OTA update? if not what changes do I have change back? ps I would rather not format the Internal USB drive.
Ah you people complicated it for me, this is what I was thinking of doing
I'm on CyanogenMod 9 RC1, when Jelly Bean starts going OTA, there should be a flashable ZIP available, right? I know when I was on GB, and waiting for OTA for my country is never gonna happen, I just downloaded update.zip and flashed it.
1. Download ZIP, put it on SD Card, along with full stock 4.0.4 flashable ZIP, and Superuser.zip
2. Make Titanium Backup of apps
3. Go to CWM
4. Wipe data
5. Flash stock 4.0.4
6. Flash update to make it Jelly Bean
7. Flash Superuser
8. Boot to Jelly Bean
9. Explore around, download ROM Manager, install CWM again through it, because it will probably be gone once I boot into JB for the first time
10. Done
Correct me if I'm wrong.
JavaJunkay said:
Ah you people complicated it for me, this is what I was thinking of doing
I'm on CyanogenMod 9 RC1, when Jelly Bean starts going OTA, there should be a flashable ZIP available, right? I know when I was on GB, and waiting for OTA for my country is never gonna happen, I just downloaded update.zip and flashed it.
1. Download ZIP, put it on SD Card, along with full stock 4.0.4 flashable ZIP, and Superuser.zip
2. Make Titanium Backup of apps
3. Go to CWM
4. Wipe data
5. Flash stock 4.0.4
6. Flash update to make it Jelly Bean
7. Flash Superuser
8. Boot to Jelly Bean
9. Explore around, download ROM Manager, install CWM again through it, because it will probably be gone once I boot into JB for the first time
10. Done
Correct me if I'm wrong.
Click to expand...
Click to collapse
Too many steps. From what i have learned, download the JB flashable zip (probably it will be available the same day when ota is pushed) put to sdcard, make a wipe data and flash through cwm. The ics zip was releashed the same day, was root, busybox and superuser.
On stock 4.0.4 official with custom recovery...
Download ota zip
Boot to custom recovery
Flash ota zip
Directly after ota zip finishes, flash latest Superuser.zip (In same recovery session)
Wipe cache
Reboot----> Now you have latest ota JellyBean with Root.
Change permissions of recovery-from-boot & install-recovery.sh to 000 (so you will keep custom recovery upon reboot)
Re-flash custom recovery with JoeyKrim's Flash_Image GUI
Hungry Hungry Hippo Time
Can you have a custom kernel ??
Sent from my Nexus S using xda app-developers app
snandlal said:
On stock 4.0.4 official with custom recovery...
Download ota zip
Boot to custom recovery
Flash ota zip
Directly after ota zip finishes, flash latest Superuser.zip (In same recovery session)
Wipe cache
Reboot----> Now you have latest ota JellyBean with Root.
Change permissions of recovery-from-boot & install-recovery.sh to 000 (so you will keep custom recovery upon reboot)
Re-flash custom recovery with JoeyKrim's Flash_Image GUI
Hungry Hungry Hippo Time
Click to expand...
Click to collapse
Every stock zip contains a directory called "recovery". Delete it before flashing and you don't have to care about cwm getting overwritten.
btw are really needed only stock rom and stock kernel???
what about the 'ota survival' option present in superuser?
albundy2010 said:
I have seen misinformation regarding the ota process on the nexus s repeated so many times and its driving me nuts so I made this thread.
1. You CAN be rooted. Yes you can. Anybody that says otherwise is wrong
2. You can have a custom recovery and you SHOULD! Unless you're going to be running a logcat and trying to grab the ota URL when it first starts rolling out there is no need for stock recovery. In fact. You WON'T be able to install it manually on stock recovery. Yes you WON'T. If you're on stock recovery you either have to wait for it to be pushed to your device or flash custom recovery and flash the update zip manually. You CAN'T manually do it with stock anymore. Anybody that says otherwise is wrong.
3. Bootloader unlocked has no.effect.
4. I am not going into what rom you need on the phone or what else the updater script checks for. Since I don't see people constantly misinformed about it.
Lastly. If you're not unlocked (bootloader) now and not rooted with custom recovery you will NOT be able to flash jelly bean as soon as the ota update zip is posted. You will have to wait for it be pushed to your device or unlock and flash custom recovery..
Click to expand...
Click to collapse
I suspect in some of the "misinformation" you have missed the distinction between preparing the phone for automatically receiving and automatically installing properly an actual Over the Air update from Google, vs. preparing for you actually installing an OTA file, or some form of new Jelly Bean. You don't explicitly make this distinction or don't really clearly say which you are discussing. The title of your post points one direction, but the contents the other. Or maybe the "rant" style of writing just confuses people more, including me.