Related
is it possible to switch to another custom recovery after I already got clockworks?
I tried unrevoked but its stuck in the reboot (I believe its trying to root my aria again)
not sure what youre trying to do.... i believe Clockwork is the only Recovery for rooted phones. if you want to flash a custom ROM, well that is something else altogether. please be specific as to what you want to flash to the phone. include a link to the flash too
I was trying to flash psfreedom recovery rom from here
http://psfreedom.com/wiki/HTC_Aria
I believe the method on that website was for unrooted arias without clockworks
zyo said:
is it possible to switch to another custom recovery after I already got clockworks?
I tried unrevoked but its stuck in the reboot (I believe its trying to root my aria again)
Click to expand...
Click to collapse
To flash a different custom recovery on your Aria, you need to rename the zip file LIBEIMG.ZIP on the SD card and boot in HBOOT (Power on the phone by holding down VOL DOWN and the Power Button). When it boots to the HBOOT screen you should see text stating that it found LIBEIMG.ZIP and is installing it.
awesome. now before I go ahead, is there any clockworkx recovery image I can revert back to?
zyo said:
awesome. now before I go ahead, is there any clockworkx recovery image I can revert back to?
Click to expand...
Click to collapse
I'm curious, what recovery are you talking about?
thanks for including the link. the instructions are clear.... Root IS required, Clockwork recovery is recommended, the Freedom Aria flash appears to be a custom ROM.
once the phone is Rooted, boot into Recovery, make a Nandroid backup, and flash downloaded zip file from SD card.
if you need help Rooting, there is all sorts of good methods available on this site. I use the Unrevoked method myself, but it works best on Linux or Mac OS
zedbra said:
thanks for including the link. the instructions are clear.... Root IS required, Clockwork recovery is recommended, the Freedom Aria flash appears to be a custom ROM.
once the phone is Rooted, boot into Recovery, make a Nandroid backup, and flash downloaded zip file from SD card.
if you need help Rooting, there is all sorts of good methods available on this site. I use the Unrevoked method myself, but it works best on Linux or Mac OS
Click to expand...
Click to collapse
hmm I think you are looking at the old method which is a custom rom
The new one is a custom recovery which brings me to the question as I dont think you can flash a custom recovery in the clockwork custom recovery.
its possible im looking at the wrong thing, but far as i can tell it states "Recovery Custom ROM" which is totally different from Custom Recovery ROM
From link posted above:
"Update can be installed in recovery mode in Psfreedom settings menu via Update (local) or Update (net) if you have configured your wifi connection. Put the file on your SDCARD and install it.
Download Recovery custom rom : http://alephzain.klutsh.com/aria-recovery.tgz "
tpbklake said:
To flash a different custom recovery on your Aria, you need to rename the zip file LIBEIMG.ZIP on the SD card and boot in HBOOT (Power on the phone by holding down VOL DOWN and the Power Button). When it boots to the HBOOT screen you should see text stating that it found LIBEIMG.ZIP and is installing it.
Click to expand...
Click to collapse
I have similar questions. I was trying to update my version of clockwork also using unrevoked again, but couldn't get it to work. I guess my questions are:
1. Is there any benefit in updating to a newer version of clockwork? My current version is 2.0.x.x and I believe the latest one is 2.5.0.4.
2. Will this same method work to do so? Can I rename the latest clockwork .zip file like this and get it updated?
I thought using the flash clockwork option in ROM Manager would do it, but it doesn't. If I reboot from ROM Manager it goes to the newer version, but if I reboot otherwise it goes to my original. The couple times I've used it, there appears to be maybe some different features/options in the newer one and I feel like I might be missing out on something!
What's the difference with this recovery?
Sent from my Liberty using XDA App
zedbra said:
its possible im looking at the wrong thing, but far as i can tell it states "Recovery Custom ROM" which is totally different from Custom Recovery ROM
From link posted above:
"Update can be installed in recovery mode in Psfreedom settings menu via Update (local) or Update (net) if you have configured your wifi connection. Put the file on your SDCARD and install it.
Download Recovery custom rom : http://alephzain.klutsh.com/aria-recovery.tgz "
Click to expand...
Click to collapse
These are probably two different things. once you got the recovery rom flashed you can upgrade it in recovery mode (hence its different from original clockwork recovery)
Ok bro, I didn't see much info about it so I'm gonna take your word for it.
@brswattt, far as I can tell this is " basically" used for jailbreaking the ps3.
@armyengineer;
you can use unrEVOked to flash the new recovery. if youre a Windows user, download the unrEVOked tool and run the .exe as Administrator. also make sure there are no conflicting s/w on the PC such as HTC Sync and you have all the drivers installed(HBoot, ADB drivers, etc.)
for more info about the PSFreedom Recovery, check out THIS Thread HERE
unrevoked keeps giving me
couldnt find misc
error, is there any other way to flash a recovery?
zedbra said:
@armyengineer;
you can use unrEVOked to flash the new recovery. if youre a Windows user, download the unrEVOked tool and run the .exe as Administrator. also make sure there are no conflicting s/w on the PC such as HTC Sync and you have all the drivers installed(HBoot, ADB drivers, etc.)
Click to expand...
Click to collapse
This still isn't working for me. Everything appears to go well at the start, then I get:
Waiting for root...(safe to restart if this doesn't work)
At which point the only way I can restart is to pull my battery. After doing so, it reboots and I get:
This was a triumph
It is not, however, any such thing. After another minute I get this:
Internal error: couldn't find misc.
So I've still got my original version of clockwork, 2.0.1.3, despite the fact that ROM Manager is telling me I have 2.5.0.1. I'm obviously missing something here.
BTW, if it matters I'm running CM 6.1.0
armyengineer51 said:
I have similar questions. I was trying to update my version of clockwork also using unrevoked again, but couldn't get it to work. I guess my questions are:
1. Is there any benefit in updating to a newer version of clockwork? My current version is 2.0.x.x and I believe the latest one is 2.5.0.4.
2. Will this same method work to do so? Can I rename the latest clockwork .zip file like this and get it updated?
I thought using the flash clockwork option in ROM Manager would do it, but it doesn't. If I reboot from ROM Manager it goes to the newer version, but if I reboot otherwise it goes to my original. The couple times I've used it, there appears to be maybe some different features/options in the newer one and I feel like I might be missing out on something!
Click to expand...
Click to collapse
Although there is a ClockworkMod 2.5.0.4 version, I don't think it is for the Aria. According to ClockworkMod ROM Manager, 2.5.0.1 is the most current one for the Aria so I am believing what ROM Manager is telling me since it is written by the same the vendor.
I have tried CM 6.1.0
original HTC Aria 2.1 International Rom
and FR001 RC1
all no go. I think it has something to do with the phone already been rooted and has clockworks installed which makes unrevoked unhappy
zyo said:
I have tried CM 6.1.0
original HTC Aria 2.1 International Rom
and FR001 RC1
all no go. I think it has something to do with the phone already been rooted and has clockworks installed which makes unrevoked unhappy
Click to expand...
Click to collapse
OK, let's start from the beginning. You asked about installing an alternate recovery (PSFreedom recovery), but apparently it has its own installation procedure that needs to be run on an unrooted Aria.
What you need is to find just the PSFreedom recovery and copy it to your SD called in a file called LIBEIMG.ZIP and that is how you need to install it on a root phone that has ClockworkMod. Perhaps you need to go back to the PSFreedom thread and ask if a LIBEIMG.ZIP can be produced that can be flashed from HBOOT to replace ClockworkMod.
Looks like everything you need is located in the PSFreedom wiki:
http://psfreedom.com/wiki/HTC_Aria
I got a recovery.bin which is suppose to be used with unrevoked.
are you talking about the same one if I just compress it into a zip file?
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...
I had some problems with rooting and flashing ClockworkMod, and when I solved it, sunitknandi asked me if I could post info which some people may find it useful, so here it is.
sunitknandi said:
Things to know while rooting stock ROM:
1. HTC Tattoo is HTC's first NAND locked device preventing users to write to system and recovery under normal conditions.
2. This NAND lock can be defeated by inserting tattoo_hack.ko module. This module was created on taking the help of info from a leaked QualComm datasheet.
3. The module needs to be inserted prior to writing to system or flashing recovery.
4. The manual rooting method and Maveric/NTenisOT 1-click method flashes a custom boot.img after rooting so that the NAND remains unlocked everytime the device is used. On the other hand, Universal Androot unlocks the NAND temporarily while rooting and unrooting. If Androot is used, the device gets permanently rooted, but the NAND locks itself after a reboot, until Androot is used again or tattoo_hack is inserted.
5. Custom 1.6, 2.1, 2.2 roms have tattoo_hack added to their modules list to keep NAND unlocked while device is running. On 2.3, however, the unlock code is compiled into the kernel, so the module is not needed.
6. We deal with this module because no one has developed S-OFF for the Tattoo.
7. Most users forget about this module once their Tattoo is rooted. New users oversee this module and run into problems. The CyanogenMod wiki is misleading in 'How to root Tattoo' because of this.
Click to expand...
Click to collapse
Next post solved my problem. I had 1.6 stock ROM with original recovery, and I just could’t install ClockworkMod recovery via ROM Manager. For rooting I used Universal Androot application (Download link in attachment below).
sunitknandi said:
Go to universal androot. Hit root again. Let it complete.
Then use Root Explorer and mount /system as rw. Or u ca also use Terminal Emulator. Just type these.
su
mount -o remount rw /system
Close terminal.
Go to ROM Manager. Tap Flash ClockWorkMod recovery. First it will take time. Let it successfully flash. Tap again. Let it flash. Tap again. Let it flash.
I am telling you to tap this many times. Because CWM 5.0.2.0 doesnt flash easily. I got so many failed flashes even on CM7. It only gets flashed after a couple of time.
Otherwise, hit menu button on ROM Manager, slect settings and check mark 'Erase recovery before flashing'. Go back and flash recovery twice.
Finally reboot manually. No need to use ROMManager's reboot option. I read that it works rather badly on Android 1.x. Boot with HOME+POWER.
Lemme know.
Btw, the safest method to flash recovery is NTenis's tool. Used it many times without problems because it flashes the boot to disable the write-protection.
Click to expand...
Click to collapse
Thanks again, sunitknandi.
Thanks bro.
Universal Androot users, always remember to re-root and mount ur /system as rw before flashing recovery from ROM Manager if u r using stock ROM. Thats what u need to do in short.
Hope this helps many people, as I know there are guys around who do not like to use a PC to root their Tattoo.
I'm not all that savvy at rooting and messing with Androids. I have a rooted Inspire 4G, but the Nexus 7 is a whole different beast. Some of the methods and things I need to do are kind of confusing, and was hoping I could get some help on my most burning questions.
1. What is the best/safest/most reliable way to root the Nexus 7 at the moment? (I have the latest OTA update JR003D)
2. I have many games that I would like to keep the data for. Is there any way to root my Nexus 7 without wiping the tablet entirely? If necessary, what is the best way to back up app data or the entire tablet?
3. Is there any way I can root my device so that I can still receive OTA updates safely without losing root, or at least be able to get root back easily?
If there's some good answers, hopefully other people can benefit from this too. ^.^
1/2. I used this toolkit. Since most ways that root also have you unlock when you do that it will wipe the device. So if you have stuff on /sdcard Id suggest backing it up to your computer and copy over afterword.
3. If you want to stay OTA and keep root, then you will need to flash the stock recovery back (if you use that toolkit since it flashes Clockwork for you) and use voodoo ota rootkeeper. You can do this by
Download ota rootkeeper and backup your root
Download the system image from here
Extract the recovery.img and stick it in your fastboot folder
boot into fastboot and type fastboot erase recovery
type fastboot flash recovery recovery.img
wait for flash
type fastboot reboot-bootloader
reboot the tab, system update then go back into voodoo and restore root and done!! You can then reflash CWM if you want to go custom again in the future, but keep in mind you need to be on stock recovery to take OTA.
u should of just rooted it right out of box so u wouldnt have to lose any data etc... because u havent done anything on it yet.
yeah thats what I did. Saves the hassle.
Hi, and thanks for your instructions. They are very clear.
Do you recommend that I (typical owner) leave my stock recovery image in place for day-to-day use and switch to CWM only when I desire to reflash? How do you do it? Also, should I make a nandroid backup(s) or is that kind of a waste on my 8GB Nexus?
I am familiar with CWM for flashing and backing up (to rem. SD card) for my phone.
I'd like to ensure I'll receive notifications about Nexus 7 updates. At least for a while or until I decide on a custom ROM. If ever.
Again, many thanks.
Sent from my Nexus 7
NeoMagus said:
1/2. I used this toolkit. Since most ways that root also have you unlock when you do that it will wipe the device. So if you have stuff on /sdcard Id suggest backing it up to your computer and copy over afterword.
3. If you want to stay OTA and keep root, then you will need to flash the stock recovery back (if you use that toolkit since it flashes Clockwork for you) and use voodoo ota rootkeeper. You can do this by
Download ota rootkeeper and backup your root
Download the system image from here
Extract the recovery.img and stick it in your fastboot folder
boot into fastboot and type fastboot erase recovery
type fastboot flash recovery recovery.img
wait for flash
type fastboot reboot-bootloader
reboot the tab, system update then go back into voodoo and restore root and done!! You can then reflash CWM if you want to go custom again in the future, but keep in mind you need to be on stock recovery to take OTA.
Click to expand...
Click to collapse
I just followed the 1.5.2 tool kit to unlock, root and install CWM onto my N7.I would like to remove CWM and replace the stock recovery for OTA updates. I followed your instructions and extracted recovery.img from the nakasi JRN84D image. I installed the android SDk and the 4.1 toolkit but I cannot find the fastboot folder, I found the fastboot exceuter but no fastboot folder in sight.
Any tips?
You want it in the folder with fastboot.exe. On my PC this is in platform-tools
Hi SoHaunted. I haven't heard any reply to my own questions so maybe this thread has been buried in the deluge of Nexus 7 topics.
You might want to go to the Nexus 7 Development forum and look at the topic regarding Nexus Root Toolkit v1.5. It is a Windows program that really helps with the different rooting tasks. It installed CWM for me. I also used it to update to a newer version of CWM.
NeoMagus said:
You want it in the folder with fastboot.exe. On my PC this is in platform-tools
Click to expand...
Click to collapse
thanks thats what I needed to know . 1 more thing, does the N7 have to be in bootloader mode before executing fastboot.exe or can it be on?
danny8 said:
Hi SoHaunted. I haven't heard any reply to my own questions so maybe this thread has been buried in the deluge of Nexus 7 topics.
You might want to go to the Nexus 7 Development forum and look at the topic regarding Nexus Root Toolkit v1.5. It is a Windows program that really helps with the different rooting tasks. It installed CWM for me. I also used it to update to a newer version of CWM.
Click to expand...
Click to collapse
That's the program I used to obtain root and install CWM, What I want to do is remove CWM and replace it with the stock recovery for future OTA updates as I do not plan on installing any roms or kernels at this time, Stock JB is good for me.
SoHaunted said:
thanks thats what I needed to know . 1 more thing, does the N7 have to be in bootloader mode before executing fastboot.exe or can it be on?
Click to expand...
Click to collapse
It needs to be in the screen with the Android where it lists the info on the bottom and says start with the green arrow, after holding the volume buttons and power.
danny8 said:
Hi, and thanks for your instructions. They are very clear.
Do you recommend that I (typical owner) leave my stock recovery image in place for day-to-day use and switch to CWM only when I desire to reflash? How do you do it? Also, should I make a nandroid backup(s) or is that kind of a waste on my 8GB Nexus?
I am familiar with CWM for flashing and backing up (to rem. SD card) for my phone.
I'd like to ensure I'll receive notifications about Nexus 7 updates. At least for a while or until I decide on a custom ROM. If ever.
Again, many thanks.
Sent from my Nexus 7
Click to expand...
Click to collapse
That method I posted was how to flash the stock recovery back to take OTA. If you are familiar with how to use CWM since you flashed it might as well just stick with it. Really only want to stay stock if you want the OTA's then just use rootkeeper