Related
Uploaded with ImageShack.us
Uploaded with ImageShack.us
Uploaded with ImageShack.us
Uploaded with ImageShack.us
Uploaded with ImageShack.us
Uploaded with ImageShack.us
Uploaded with ImageShack.us
Uploaded with ImageShack.us
Uploaded with ImageShack.us
for the love of God can some body help me?
i just dont know what to do, this is the oem rom update and why the unit is not able to find the update in the sd card?
This post isn't about development, you posted the same thing in multiple places, and you can't install the AT&T update with clockwork, you need the stock recovery.
marvin02 said:
this post isn't about development, you posted the same thing in multiple places, and you can't install the at&t update with clockwork, you need the stock recovery.
Click to expand...
Click to collapse
yes thanks
where can i find it and how can i flash it?
elmanortega said:
yes thanks
where can i find it and how can i flash it?
Click to expand...
Click to collapse
+1
Please god, Ive been stuck on this **** for 14 hours now. SOLUTION PLEASE!
I've experience rooting/roming over 50 phones, and this is getting irritating!
CWM doesnt flash .pkg's, and I'm coming in way to late in the process to understand this QueTip program or w-e. A simple stock recovery flash tutorial n link would be amazing.
this will happen too when you flash it over 2.2 already but in your case your on 16 ryt?i would suggest google search for the stock 1.6 6601 recovery image and flash it and then flash clockwork and then apply the update.
try to look here.
http://forum.xda-developers.com/showthread.php?t=778397
try here also.
http://android.modaco.com/content/d...uide-to-upgrading-and-downgrading-the-streak/
whats your baseband prior to this update?
I suggest that you use streakdroid recovery to make a nandroid backup before you revert to the stock recovery,
Download stock recovery from here. Make sure it is on your computer in the same folder as fastboot.exe
Excerpted from this streakdroid guide:
Shut down your Streak, then hold down the camera button (all the way) as you turn it back on.
The screen should turn white; press ‘Fastboot’ in the top right hand of the screen.
Plug in the USB cable – the Streak should now display ‘FASTBOOT_MODE’ at the bottom of the screen.
Open a command window and use ‘cd’ to change to the same directory as qdltool.
Run: fastboot -i 0x413c flash recovery recovery.img
Run: fastboot -i 0x413c reboot
Either rename the file you downloaded to recovery.img or change the name of the file to flash in step 5 to match the file downloaded.
Boot into recovery and you should now have a stock recovery.
You can boot your phone and try downloading and installing the OTA upgrade or you can place the upgrade file on your SD card and name it upgrade.pkg and try to install it using the stock recovery.
I suggest that you use streakdroid recovery to make a nandroid backup before you revert to the stock recovery.
Make sure that any ROM you try to install on your phone is appropriate for your hardware and carrier.
I personally was on the 318 build of 2.2... Downgraded to O2 2.1, then to O2 1.6, then to AT&T 1.6 with the BB downgrade... then upgrade to AT&T 340 2.2, its not that hard... get to stock AT&T 1.6 and leave the 340 "update.pkg" in the root of the SD card.
Instructions to get to AT&T 1.6 here > http://forum.xda-developers.com/showpost.php?p=8558692&postcount=4
marvin02 said:
I suggest that you use streakdroid recovery to make a nandroid backup before you revert to the stock recovery,
Download stock recovery from here. Make sure it is on your computer in the same folder as fastboot.exe
Excerpted from this streakdroid guide:
Shut down your Streak, then hold down the camera button (all the way) as you turn it back on.
The screen should turn white; press ‘Fastboot’ in the top right hand of the screen.
Plug in the USB cable – the Streak should now display ‘FASTBOOT_MODE’ at the bottom of the screen.
Open a command window and use ‘cd’ to change to the same directory as qdltool.
Run: fastboot -i 0x413c flash recovery recovery.img
Run: fastboot -i 0x413c reboot
Either rename the file you downloaded to recovery.img or change the name of the file to flash in step 5 to match the file downloaded.
Boot into recovery and you should now have a stock recovery.
You can boot your phone and try downloading and installing the OTA upgrade or you can place the upgrade file on your SD card and name it upgrade.pkg and try to install it using the stock recovery.
I suggest that you use streakdroid recovery to make a nandroid backup before you revert to the stock recovery.
Make sure that any ROM you try to install on your phone is appropriate for your hardware and carrier.
Click to expand...
Click to collapse
I don't have a fastboot option, and am unfamiliar with QDLtool? Can I pick up on these steps even with CWR already installed?
here are my videos of my device turning on and going into clockwork etc
http://www.youtube.com/watch?v=u0wSH64PlsM
http://www.youtube.com/watch?v=zMiRGekzT_I&feature=mfu_in_order&list=UL
Truaim said:
I don't have a fastboot option, and am unfamiliar with QDLtool? Can I pick up on these steps even with CWR already installed?
Click to expand...
Click to collapse
If you are not on at&t's 1.6 than this is your only option. Also your only way to go back to the 1.6 is using essentially same steps as above. So just make sure fastboot is set up and follow the steps listed above. It will work regardless of os you are running now. I just did it and I was on dj steve's 1.8. On a side note how is the upgrade working for you?(those that installed it)
dacho said:
If you are not on at&t's 1.6 than this is your only option. Also your only way to go back to the 1.6 is using essentially same steps as above. So just make sure fastboot is set up and follow the steps listed above. It will work regardless of os you are running now. I just did it and I was on dj steve's 1.8. On a side note how is the upgrade working for you?(those that installed it)
Click to expand...
Click to collapse
hi do you have a chance to help me out with this?
how do you install universal androot? it only says install and run it
dowloading to my pc and click it doesnt work, copying to root of the sd card and trying to installed with clock work doesnt work
software upgrade via update.pkg on sd card doesnt work
im just thinking that im just plain stupid
is there a video tutorial?
is there some one that can help me i will pay im just tired.
You need fastboot. Plain and simple.
sent from my re-engineered dInc
Hellzya said:
You need fastboot. Plain and simple.
sent from my re-engineered dInc
Click to expand...
Click to collapse
i have fastboot
Yeah my installation came up with an error and it would not boot after it was applied so previously posted stock recovery does not work. So what you have to do is follow the steps to go back to stock at&t 1.6 rom. Here are the directions http://forum.xda-developers.com/showpost.php?p=8558692&postcount=4
I am in a process of doing this now so i'll keep you posted. However, once you do the downgrade from the link above you should be able to just install latest at&t rom without any problems. Hope that helps.
dacho said:
Yeah my installation came up with an error and it would not boot after it was applied so previously posted stock recovery does not work. So what you have to do is follow the steps to go back to stock at&t 1.6 rom. Here are the directions http://forum.xda-developers.com/showpost.php?p=8558692&postcount=4
I am in a process of doing this now so i'll keep you posted. However, once you do the downgrade from the link above you should be able to just install latest at&t rom without any problems. Hope that helps.
Click to expand...
Click to collapse
thanks ok first how do you install universallandroot?
elmanortega said:
thanks ok first how do you install universallandroot?
Click to expand...
Click to collapse
it should be in the market. I used to use SuperOneClick it should work for 2.2 and 1.6. just google the SuperOneClick.exe and you run this from the computer not the phone. universalandroot you run from the phone.
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.
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.
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...