Hey everybody, I need some help perm rooting my HTC G2. Im using these instructions to permroot my G2. http://forum.xda-developers.com/showthread.php?t=1206930
Im stuck on this section....
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.
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...
slufoot69 said:
Hey everybody, I need some help perm rooting my HTC G2. Im using these instructions to permroot my G2. http://forum.xda-developers.com/showthread.php?t=1206930
Im stuck on this section....
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.
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...
Click to expand...
Click to collapse
may sound stupid to say lol but are you hitting the power button or the optical pad button..if you hit power i noticed sometimes it would show the gear with the hat on..try selecting with the optical button instead
Tbbo514 said:
may sound stupid to say lol but are you hitting the power button or the optical pad button..if you hit power i noticed sometimes it would show the gear with the hat on..try selecting with the optical button instead
Click to expand...
Click to collapse
DUDE YOUR THE MAN!!!!!!! This was my first root, bad thing was I upgraded to Gingerbread 2.3.4 before getting S-OFF so I had to downgrade too Froyo 2.2 and go thru all the mumbo jumbo of getting S-OFF and Perma Root. Then reflash Froyo 2.2 with S-OFF so I could upgrade to Gingerbread 2.3.4.
You know how many hours Ive spent on this the last 2 days LMAO to get stuck on the last step in CWM because I was hitting the power button instead of the OPTICAL button lol. My brain was so fried last night. Almost bounced my phone off the wall... Thanks again... +1 for you...
Sean...
How do I give you a +1? Ive seen people do it on here several times. Sorry im new to this forum...
Sean..
slufoot69 said:
How do I give you a +1? Ive seen people do it on here several times. Sorry im new to this forum...
Sean..
Click to expand...
Click to collapse
lol you got it dude. and no problem at all i hate how when someone has a question and no one answers it can be frustrating sometimes. but glad it all worked out for you. hope you didnt have to do some over complicated method lol seems like there are 50 million different ways to root it huh?
anyone curious about the downgrading procedure can check this article out. i know everyone gets tired of reading thirty different methods but this one works no complicated directions and explanations of everything
http://techticians.com/index.php/mobile-tech/14-mobile-phones/27-rooting-the-t-mobile-g2
Tbbo514 said:
lol you got it dude. and no problem at all i hate how when someone has a question and no one answers it can be frustrating sometimes. but glad it all worked out for you. hope you didnt have to do some over complicated method lol seems like there are 50 million different ways to root it huh?
Click to expand...
Click to collapse
Ohhh yea tell me about it. like i said my brain was fried lol
Tbbo514 said:
anyone curious about the downgrading procedure can check this article out. i know everyone gets tired of reading thirty different methods but this one works no complicated directions and explanations of everything
http://techticians.com/index.php/mobile-tech/14-mobile-phones/27-rooting-the-t-mobile-g2
Click to expand...
Click to collapse
Yep same downgrade method I used, just go step by step and it will work for ya...
Related
hello everyone. i been a long time lurker of this site but never had the courage/motive to post. but i have an issue.
after much reading of how great rooting your phone can be. i too wanted to do it. so i looked n looked until i decided that id tryout CM7 cyanogen site
i believe i was able to unlock the bootloader/device. everytime i power up my phone regular start up starts with an unlocked lock at the bottom(like its supposed to right lol)
but here is as far as i get to go. i backed up my apps with astro file manager. then downloaded rom manager n as soon as i open it says "you must root your phone for ROM manager to function. superuser was not found at "/system/xbin/su". use goo search on ur computer to root your phone"
im stuck here because well im a noob and dont know why this is showing up. i was kinda hoping one of you guys could help me out here...
Taking straight from the wiki. Please read it before asking questions.
very generic explanation of steps needed to update a stock phone to custom ROM:
Download the ROM of your choice.
Copy the downloaded ROM image to the SD card
Root if you don't want to unlock bootloader (or just unlock bootloader).
Flash custom recovery image (if not done while rooting)
Turn off the phone
Turn on the phone while holding Volume Down
Select "BOOTLOADER" from the menu
Select "RECOVERY" from the menu
Select "Wipe"
Select "Wipe data / factory reset"
Select "Wipe Dalvik cache"
Return to main recovery menu
Select "Flash update.zip" or "Flash ZIP file"
Turn off verification, if such option is presented
Select your downloaded ROM image
Wait for the flash to finish successfully, if it didn't - do not continue!
Return to main recovery menu
Reboot the phone
You can follow a video walkthrough for this here: How to Flash a Custom ROM
To add to the post above, look at my signature and make sure you read and execute the relevant guide.
Just to clarify what the others are saying. You don't have root because you didn't root your phone.
You only unlocked the bootloader, which allows you to flash partitions through fastboot.
you havent rooted ,just unlocked bootloader
Echo?
Sent from my Nexus One using XDA Premium App
apollofroyo said:
you havent rooted ,just unlocked bootloader
Click to expand...
Click to collapse
yea i since realized that. ive now flashed 2.2.
but cant get the to root it yet
trying to figure things out.. maybe rooting wasnt such a good idea since i cant figure it out
rawskillz said:
yea i since realized that. ive now flashed 2.2.
but cant get the to root it yet
trying to figure things out.. maybe rooting wasnt such a good idea since i cant figure it out
Click to expand...
Click to collapse
since you have a unlocked bootloader you can do fastboot flash..
get amon ra recovery and do fastboot flash recovery recovery.img
after you do that it should say sending flashing and done with no errors
from then reboot into recovery and do a nandroid of rom then do wipe and wipe and flash selected rom you want.. cm7 plus gapps after reboot and you haverom..
nexus one is ez to gainroot if you unlockboot loadder.. if you dont then it gets more complicated..
rawskillz said:
yea i since realized that. ive now flashed 2.2.
but cant get the to root it yet
trying to figure things out.. maybe rooting wasnt such a good idea since i cant figure it out
Click to expand...
Click to collapse
wow thanks alot. it was way easier than i thought it would be. now going to backup my apps and flash cyanogen 7 . the problem is i had installed sdk b4 in wrong folder etc. will take future note. thanks to all
Not applicable
Delete this thread
Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!
Too complicated.
Just:
1. turn on phone by holding volume up + power to go to bootloader
2. fastboot oem unlock (confirm it on the phone)
3. fastboot flash recovery recoveryfilename.img
4. Select recovery on the phone.
5. You're in ClockworkMod. Go flash a new ROM.
Let me answer myself.
I don't think the latest rom 2.3.4 is compatible with the clockwork you supplied. So I have to flash my phone back to GRH78. I downloaded the stock ROM from the internet. and then push all the images file into /sdcard/clockworkmod/backup/2010.xxx.
Next, I restore the image in clockwork menu.
after restore, reboot the phone, now I am back in business.
When the phone is boot, i lost the root again, so i went to modaco.com and get Paul's package. run it, restart, I got the root.
Finally, go to market place and get ROM Manager, install the clockwordmod. and I have a 'proper' phone.
although I don't have the least rom, at least i got a working phone that is rooted.
bante said:
Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!
Click to expand...
Click to collapse
I have the same problem. How did you handle it?
Wow, why risk messing up your phone with flashing a boot.img when you can just rename /etc/install-recovery.sh to something like /etc/install-recovery.bak?
Here's one way to rename (courtesy of Matridom). Another is to use Root Explorer.
Matridom said:
The new update applies the install-recovery.sh script into our phones (not there previously.
Boot into the bootloader
flash CWM
select recovery from the bootloader (DO NOT reboot the phone)
apply the su binary
boot into the OS and test root
make sure busybox is properly installed
run ADB shell
then:
Code:
su
mount -o remount,rw /dev/block/mtdblock3 /system
mv /system/etc/install-recovery.sh /system/etc/install-recovery.bak
Boot back into the bootloader and re-flash CWM, should stay permanent now.l had applied the SU binary at the same time as the OTA update, then renamed the installer script and flashed back CWM.
Click to expand...
Click to collapse
andnaz said:
I have the same problem. How did you handle it?
Click to expand...
Click to collapse
same here someone please help ?
This is a totally unorthodox way to make the custom recovery permanent. If your phone is messed up, good luck fixing it.
There is a much easier and safer way like I mentioned.
PS: flashing recovery for 2.3.4 is the exact same as for 2.3.3!
fastboot flash recovery <recovery .img>
Sent from my Nexus S using XDA App
bante said:
Hello, thanks for the post.
I got a brand new Nexus S, I got a update direct from Google so I just flash it to GRJ22 :-(. I follow your guide (I have to do the step 1/2 in the other post you refer). Now I got clockwork done. But everytime I restart my phone, I always boot into clockwork. I try to 'mount sdcard' and reboot, but still boot into clockwork. How can I boot into the stock ROM?
many thanks!!
Click to expand...
Click to collapse
Hi Bante, I am sorry for the inconvenience. I have revert back the CWM Recovery to 3.0.2.4. You can download it at the link above, and try it again
I hope that the problem you mention wont persist anymore
zero383 said:
This is a totally unorthodox way to make the custom recovery permanent. If your phone is messed up, good luck fixing it.
There is a much easier and safer way like I mentioned.
PS: flashing recovery for 2.3.4 is the exact same as for 2.3.3!
fastboot flash recovery <recovery .img>
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
I am sorry but not all people can successfully use Command Prompt to do so.
I cant use command prompt, as it says "Image cant be loaded".
So I had to use this method.
I search around the forum and seen this as a quite common problem,
so I decided to share it
Hope you understand.
Anyway, thanks for your method too Cheers
andnaz said:
I have the same problem. How did you handle it?
Click to expand...
Click to collapse
The CWM Recovery I supplied is version 3.0.2.5,
which is not compatible.
So I replaced with version 3.0.2.4.
You just download it at the link above and follow all the step again.
You should able to solve this problem
Do notify me if any problem persist
16vMK1 said:
same here someone please help ?
Click to expand...
Click to collapse
The CWM Recovery I supplied is version 3.0.2.5,
which is not compatible.
So I replaced with version 3.0.2.4.
You just download it at the link above and follow all the step again.
You should able to solve this problem
Do notify me if any problem persist
Wow people like to make things complicated. Why install an entire rom to get ride of a script?
if you can flash cwm, you should have some basic understanding of fastboot, adb and the search options in the forums. the answers are all there already.
Sent from my Nexus S
No disrespect, I agree flashing recoverys should only be done after you understand how to use the tools to do it. there is no reason someone who is going to mod systems on their nexus shouldn't be able to use fastboot and adb properly. all the right drivers are in the sdk.
Sent from my Nexus S 4G using Tapatalk
nxt said:
Too complicated.
Just:
1. turn on phone by holding volume up + power to go to bootloader
2. fastboot oem unlock (confirm it on the phone)
3. fastboot flash recovery recoveryfilename.img
4. Select recovery on the phone.
5. You're in ClockworkMod. Go flash a new ROM.
Click to expand...
Click to collapse
This is what I did.
I rooted my NS, which had 2.3.3
Used phone with stock 2.3.3 until I figured out which ROM I want to flash.
Before I flashed any ROM, did a Nandroid Backup through CWM.
Used the ROM for a few days, but when I saw that official update is ready for download for i9020A, did do a restore from the Nandroid backup I created.
Updated from 2.3.3 to 2.3.4, phone works fantastic, video chat also works great.
After update when I tried using any of the apps required SU permission, they didn't work. I tried installing a couple of .apk files, couldn't either install it or after installation it didn't work.
Thought let me try wiping my phone clean and start all over again, may be I will use a custom ROM again, downloaded ROM, went to ROM Manager to reboot into recovery, nothing happens.
Tried booting into Recovery option manually by pressing Volume Up and Power button, nothing happens but the Bot with an Arrow appears on screen.
So, I thought I will follow this procedure to reflash CWM to my phone and get it going. I was able to use the command FastBoot once, and suceeded pushing .img file to my phone but now whenever I try using the commands from my computer, this error message appears : "This application has failed to start becasue AdbWinApi.dll was not found. Re-installing the application may fix this problem."
Why this error message if I have the sdk on my computer already through which I was once able to push .img file without any troubles?
Can anyone tell me what would be a possible solution?
Also, how can I fix this problem and get ClockWorkMod Recovery installed on my NS again?
How can I get stock recovery image on my phone if I want start all over again from scratch?
Thx a million.
Edit ::: I found the answer as to how to how to install CWM again. Thx anyways.
Other question still remains a puzzle... why am I not able to install certain programs or if did manage to install, can't run them?
I ran your method and I think I'm stuck at some step...
My phone now default boots into CWM 3.0.2.4
Recovery boots to a newer recovery I flashed.
How do I get my phone to default boot into the OS again?
Edit: nevermind, just downloaded the full 2.3.4 rom, extracted and flashed the original boot.img.
dreamsforgotten said:
All the right drivers are in the sdk.
Click to expand...
Click to collapse
After installing the sdk and a platform, I have adb, but where is fastboot?
I was getting the same error as "Image cant be loaded". after hours of struggling I found that It's only because I was not in the same directory as the img file. silly eh?
hi,did you repaiar your phone,i have try everything but it just keep going in clockwork mode,if i than pres reboot now in clockworkmode it stays on google padlock
i realy need phone if you can help or someone else,than ....
just tried this method of window7 (thanks for the work) with cwm 3.0.2.4, but got the same result like the others in this thread: cant boot the android 2.3.4, the system is always booting into the cwm, no way out.
I don't think this tool works as it should.
:-(
EDIT:
I didn't realize that window7's tool would install the cwm into the boot-partition instead of the recovery-partition.
To get my boot partition back I downloaded the 2.3.4 firmware image from http://forum.xda-developers.com/showthread.php?t=1056062 and extracted the boot.img from the zip.
with "fastboot flash boot boot.img" I restored my orginal boot partition an can boot into android again.
(fastboot is part of the android sdk)
If you have S-Off and Updated via OTA
Here is the Most Current Amon Ra Recovery
Amon Ra Recovery 2.3
Place PC36IMG.zip on the root of your sd card.
Boot the phone into the bootloader by powering the phone down, then press the power and the volume down buttons at the same time.
Once the phone boots into the bootloader the phone will automatically recognize the zip file. It will ask if you would like to update, select yes and let it do it's thing and you will be good to go
After this you can Flash any Rom of your Choosing and get Super user and Buzy Box back...
What does that Mean you will be Rooted Again
Just make sure you use a Custom Rom or Stock De-odexed or Odexed Rom
I have s-off but I can't go into recovery
jonathan413 said:
I have s-off but I can't go into recovery
Click to expand...
Click to collapse
Did you take the OTA already? If so, you no longer have recovery. As the OP stated, since you still have S-off, you just need to reflash your recovery. Download a PC36IMG of Amon Ra's recovery, and flash it with your bootloader. Then you'll have recovery.
Download Amon RA PC36IMG.zip and install it to the root of your SD card, Then boot into Recovery "Pull the Battery hold the Volume Down Button and Press Power"
The PC36IMG.ZIP should start to read by the recovery it will say update recovery follow what it says it should say up to install down for no, let it finish then after that you can install any rom of your choosing
Idk..every time I put the file on the root of the sdcard it never reads it..even on the older bootloaders.
it is named PC36IMG.zip right if so the bootloader should automatically start reading it you should see a progress bar on the top right of the screen
Here is the Most Current Amon Ra Recovery
Amon Ra Recovery 2.3
Yea its named right..I don't even touch the file I just drop it on the root of the sd but nothing gets read when I go to bootloader
In my previous post i linked the Recovery but here it is again
Here is the Most Current Amon Ra Recovery
Amon Ra Recovery 2.3
Place PC36IMG.zip on the root of your sd card.
Boot the phone into the bootloader by powering the phone down, then press the power and the volume down buttons at the same time.
Once the phone boots into the bootloader the phone will automatically recognize the zip file. It will ask if you would like to update, select yes and let it do it's thing and you will be good to go
Still doesn't work Idk..maybe its the sdcard but I have two sdcards and both are doing the same thing
when you boot to the bootloader does it Say S-Off or S-On
To disable fastboot in ota
Go to settings
Then applications
And disable fastboot
This should allow you to get back into the bootloader
Hope this helps
echarette1 said:
To disable fastboot in ota
Go to settings
Then applications
And disable fastboot
This should allow you to get back into the bootloader
Hope this helps
Click to expand...
Click to collapse
Did it and still a no go
kingakuma said:
when you boot to the bootloader does it Say S-Off or S-On
Click to expand...
Click to collapse
It says s-off
kingakuma said:
If you have S-Off and Updated via OTA
Here is the Most Current Amon Ra Recovery
Amon Ra Recovery 2.3
Place PC36IMG.zip on the root of your sd card.
Boot the phone into the bootloader by powering the phone down, then press the power and the volume down buttons at the same time.
Once the phone boots into the bootloader the phone will automatically recognize the zip file. It will ask if you would like to update, select yes and let it do it's thing and you will be good to go
After this you can Flash any Rom of your Choosing and get Super user and Buzy Box back...
What does that Mean you will be Rooted Again
Just make sure you use a Custom Rom or Stock De-odexed or Odexed Rom
Click to expand...
Click to collapse
I can personally verify that this works.
animal7296 said:
I can personally verify that this works.
Click to expand...
Click to collapse
I wonder why my bootloader doesn't read the file
jonathan413 said:
I wonder why my bootloader doesn't read the file
Click to expand...
Click to collapse
Had that problem on a friends evo. Had to use a bigger sd cardto get it to read it.
Sent from my PC36100 using XDA Premium App
jonathan413 said:
Yea its named right..I don't even touch the file I just drop it on the root of the sd but nothing gets read when I go to bootloader
Click to expand...
Click to collapse
Are you sure you are s-off?
Stuke00 said:
Are you sure you are s-off?
Click to expand...
Click to collapse
Lol I'm positive
After turning off fastboot, did you power off the phone and pull the battery to ensure it did a complete power down? Its only a guess, shouldn't bee behaving like thus if s-off.
echarette1 said:
After turning off fastboot, did you power off the phone and pull the battery to ensure it did a complete power down? Its only a guess, shouldn't bee behaving like thus if s-off.
Click to expand...
Click to collapse
Yea did that too
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...
Okay I verified that if you have s-off you will be able to get root back on your phone if you run the RUU.
As expected the RUU did unroot my phone but it didn't touch s-off. So I downloaded CWM 3.0.0.8 from dougpiston.com and changed it to PB31IMG.zip (this has to be a flashable zip file to work) and it loaded from hboot no problem. I then downloaded the latest superuser app using ROM Manager, version 2.3.6.3 efgh, older versions will not work, and just flashed it through recovery. Superuser does not need to be renamed update.zip you can just leave the name as is and select let me choose zip from sdcard and it installs just fine.
Took a while for me to get superuser running again as I had an older version and I could only find the newest version in ROM Manager.
****YOU MUST HAVE S-OFF FOR THIS TO WORK*********************
kzoodroid said:
Okay I verified that if you have s-off you will be able to get root back on your phone if you run the RUU.
As expected the RUU did unroot my phone but it didn't touch s-off. So I downloaded CWM 3.0.0.8 from dougpiston.com and changed it to PB31IMG.zip (this has to be a flashable zip file to work) and it loaded from hboot no problem. I then downloaded the latest superuser app using ROM Manager, version 2.3.6.3 efgh, older versions will not work, and just flashed it through recovery. Superuser does not need to be renamed update.zip you can just leave the name as is and select let me choose zip from sdcard and it installs just fine.
Took a while for me to get superuser running again as I had an older version and I could only find the newest version in ROM Manager.
****YOU MUST HAVE S-OFF FOR THIS TO WORK*********************
Click to expand...
Click to collapse
I can't seem to find a link to to superuser inside ROM Manager. Can you tell me where to locate it?
thanks,
John
under download rom > extras
kzoodroid said:
under download rom > extras
Click to expand...
Click to collapse
You can also get it from here
Thanks to you both. I didn't even click on the Download ROM because it's premium and I'm still getting my feet wet with the whole root thing. I'm off to try the GB RUU w/radio and then re-root.
What if you have s-on?
You can only re-root if you have s-off. S-on blocks you from replacing the stock recovery with a custom recovery and blocks the installation of superuser into the system folder.
Eventually the Unrevoked team will come up with a new way to root phones but this most likely won't happen till the OTA actually starts to drop and people report how they lost root. And then who knows how long it will take them to do it. Could be a few days to a few months.
kzoodroid said:
You can only re-root if you have s-off. S-on blocks you from replacing the stock recovery with a custom recovery and blocks the installation of superuser into the system folder.
Eventually the Unrevoked team will come up with a new way to root phones but this most likely won't happen till the OTA actually starts to drop and people report how they lost root. And then who knows how long it will take them to do it. Could be a few days to a few months.
Click to expand...
Click to collapse
Jeez, can't believe I screwed myself like that. I'm a regular root/flasher, and no idea how to get my fix now..
deadsoulboy said:
Jeez, can't believe I screwed myself like that. I'm a regular root/flasher, and no idea how to get my fix now..
Click to expand...
Click to collapse
I ran the RUU with all expectations of not being able to re-root my phone just so I could test if the OTA would change the security settings on my phone. I also still wasn't sure if I could even get root back if it was still s-off so I was willing to experiment with knowing full well what could happen. From past experience with the Eris and losing root for about 3 months you have to flash these leaks with all expectations that it will break your phone and not sweat it too much if it does as eventually someone will find a fix.
kzoodroid said:
I ran the RUU with all expectations of not being able to re-root my phone just so I could test if the OTA would change the security settings on my phone. I also still wasn't sure if I could even get root back if it was still s-off so I was willing to experiment with knowing full well what could happen. From past experience with the Eris and losing root for about 3 months you have to flash these leaks with all expectations that it will break your phone and not sweat it too much if it does as eventually someone will find a fix.
Click to expand...
Click to collapse
You're absolutely right. I have no doubt in my mind someone will come up with a way to root 2.3 on the INC
Alright, I've got s-off, downloaded the superuser 2.3.6.3 efgh app from the ROM manager butttt... now what? I've tried to boot into recovery but I just get an icon of a phone with an exclamation mark inside of a triangle, which I'm assuming isn't good.
Flash clockworkmod recovery first, then the superuser zip.
I tried that but it gives me an error saying: "An error occurred while attempting to run privileged commands!".
If you flashed the GB RUU and lost root and/or s-off.
Someone correct me please if I'm wrong but couldn't you download the froyo RUU and load it then root and s-off?
Sent from my ADR6300 using XDA App
How are you trying to flash it? I'd recommend getting the 3.0.0.7 (AMOLED) or 3.0.0.8 (SLCD) recovery from www.dougpiston.com. Flash in hboot. Or is that how you're doing it?
deadsoulboy said:
You're absolutely right. I have no doubt in my mind someone will come up with a way to root 2.3 on the INC
Click to expand...
Click to collapse
The Eris had a manual method (race method) for rooting the phone but I could never find one posted for the Inc. It involved having the phone connected to a pc with adb running and then taking out the sdcard and rebooting, at a certain point of the boot process you counted to 4 and then pushed the sdcard back in. If you did it correctly adb was able to connect to the phone and you could slip a custom recovery and su in. It was rather complicated and only a handful of people ever did it correctly myself included and it was eventually replaced by a one-click method. The one-click method still pretty much does the same thing you just don't have to manually remove the sdcard or have the phone connected to a pc. In some ways the Eris has a lot more support from its community than the Inc does probably because it was Verizons first android phone.
k_nivesout said:
How are you trying to flash it? I'd recommend getting the 3.0.0.7 (AMOLED) or 3.0.0.8 (SLCD) recovery from www.dougpiston.com. Flash in hboot. Or is that how you're doing it?
Click to expand...
Click to collapse
I second this it has to be a flashable version (contains android-info text file + the recovery image) to work. I used the 3.0.0.8 file from doug pistons website which is already to go just needs to be renamed PB31IMG.zip and make sure it isn't being named PB31IMG.zip.zip as file extensions can be hidden especially if you are renaming it on a pc. I downloaded it directly to my phone and renamed it there so the extension wasn't hidden.
swskeptic said:
Alright, I've got s-off, downloaded the superuser 2.3.6.3 efgh app from the ROM manager butttt... now what? I've tried to boot into recovery but I just get an icon of a phone with an exclamation mark inside of a triangle, which I'm assuming isn't good.
Click to expand...
Click to collapse
I beleive that is becasue you stil have the stock recovery? Did you flash the clockwork recovery from dougpiston.com?
I flashed the clockwork mod recovery 3.0.0.7 from dougpiston via hboot.
I tried several different ways to boot into recovery to flash the superuser app but it isn't working. When I try to do it from the clockword mod app it says the same error: "An error occurred while attempting to run privileged commands!".
I tried to manually download the superuser .zip and boot into recovery from the hboot menu, but it still gave me that same phone icon with the exclamation mark and triangle and then nothing.
swskeptic said:
I flashed the clockwork mod recovery 3.0.0.7 from dougpiston via hboot.
I tried several different ways to boot into recovery to flash the superuser app but it isn't working. When I try to do it from the clockword mod app it says the same error: "An error occurred while attempting to run privileged commands!".
I tried to manually download the superuser .zip and boot into recovery from the hboot menu, but it still gave me that same phone icon with the exclamation mark and triangle and then nothing.
Click to expand...
Click to collapse
First thing are you getting into recovery from the hboot menu? And you can't get into recovery from ROM Manager because you need superuser installed to do it that way. It still sounds to me like you don't have ClockworkMod Recovery installed. Maybe only version 3.0.0.8 works I'm not sure but that version is for both amoled and SLCD screens. So either try reflashing your copy of 3.0.0.7 or try flashing 3.0.0.8. I do think I had to flash the recovery a couple times to get it to stick.