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?
I need some help. I have been looking to update my epic to 2.2 and I am interested in either installing the leaked 2.2 update or a custom rom. I want to be able to revert back to stock in case a legit update is released. I currently only have access to an Apple but will have access to a PC in the not so distant future. I have looked at some threads but they arent very clear cut for people without experience.
Thanks!!
To get to the leaked DK28, just download the leaked update.zip (LINK with instructions) and flash it through your phones recovery menu. Boot into recovery with PWR+Camera+Vol Down buttons and hold the keys til you get to the recovery menu, and if your phone is already booted, additionally hold Volume Up to initiate a reboot. This will remove any root that you have installed, so might as well do this first if your gonna upgrade to 2.2.
If you want to root and install CWM, there is a oneclick for OSX, but it uses an older joey-krim root method, but if your gonna flash a custom rom anyway, it wont matter. Here is the LINK to the OSX one click root and CWM.
Lastly, if everything goes pear shaped, be prepared to use Odin to restore your phone back to stock, but that WILL require a Windows PC.
Thanks,
I rooted and then tried to load the dk28 from the update.zip. I keep getting an error when I try and run the update.zip from the recovery mode. I am wondering if it is due to the root. Is there a way I can uninstall the root via osx?
If you can get to a computer I would use Odin to update to dk28. That way if the ota comes and youwant o go back to stock you can just Odin back to stock to get the ota
djcslice said:
Thanks,
I rooted and then tried to load the dk28 from the update.zip. I keep getting an error when I try and run the update.zip from the recovery mode. I am wondering if it is due to the root. Is there a way I can uninstall the root via osx?
Click to expand...
Click to collapse
First, did you rename it to update.zip? is it in the root folder of your sdcard? and are you trying to flash the update.zip through CWM or the stock recovery? CWM has green text, and you need to use the camera button to make selections, and the stock recovery has blue text, and you need to use the home button to make selections. If flashing through CWM, try flashing through stock recovery (goto advanced, and choose 'reboot recovery', it should take you to stock, I think ). If that still doesn't work, try downloading the zip file once again to make sure everything is complete.
Alternately, try the modem and rom from THIS post, as this will enable you to update your DI18 modem to DK28 through CWM (note, this is usually not the case, and only possible when an update.zip is released including the delta file for that modem, i.e specifically for changing from DI18 to DK28 only) and also allow you to load a prerooted DK28 stock rom without using Odin.
Koadic said:
First, did you rename it to update.zip? is it in the root folder of your sdcard? and are you trying to flash the update.zip through CWM or the stock recovery? CWM has green text, and you need to use the camera button to make selections, and the stock recovery has blue text, and you need to use the home button to make selections. If flashing through CWM, try flashing through stock recovery (goto advanced, and choose 'reboot recovery', it should take you to stock, I think ). If that still doesn't work, try downloading the zip file once again to make sure everything is complete.
Alternately, try the modem and rom from THIS post, as this will enable you to update your DI18 modem to DK28 through CWM (note, this is usually not the case, and only possible when an update.zip is released including the delta file for that modem, i.e specifically for changing from DI18 to DK28 only) and also allow you to load a prerooted DK28 stock rom without using Odin.
Click to expand...
Click to collapse
yes, yes, both (while clockwork was installed), i tried downloading the update multiple times. I unrooted and saw the same issues. I am not sure how to get rid of the clockworkmod but I am not sure if this would affect it.
In that case, read the second paragraph in my previous post to update through CWM
Koadic said:
In that case, read the second paragraph in my previous post to update through CWM
Click to expand...
Click to collapse
I read the thread and I am not quite sure how to go about the process. Can you enlighten me. Thanks!!
Flash the two zips (rom and modem) through CWM... I would flash the modem first (the second link) then flash the DK28 rom...
So, download the zip files and copy them to your sdcard (no need to rename or anything), boot into CWM, choose 'install zip from sdcard', choose the zip file containing the modem (http://firon.net/xda/stock.dk28.modem.update.signed.zip)... this will update the modem on the phone to the newest version... then do the same thing for the DK28 rom (http://www.sdx-downloads.com/devs/noobnl/noobnl.MODS+STOCK.DK28.update[HOTFIX].zip). When all done, back out to the main menu and choose 'reboot system now', and when your phone boots up, you should have DK28 Froyo 2.2.1.
If you run into any force close issues, I would suggest going back into CWM and doing a 'wipe data/factory reset', and also 'wipe cache partition', then reflash the rom again. If you dont have anything important on the phone (like if your contacts are all saved with your google account instead of just on the phone), then I would suggest doing it right off the bat. This will erase any programs you have downloaded, text messages, etc.
djcslice said:
I read the thread and I am not quite sure how to go about the process. Can you enlighten me. Thanks!!
Click to expand...
Click to collapse
If you are just looking to go to 2.2, Odin is easiest IMO.
Here are the stock files:
http://forum.xda-developers.com/showthread.php?t=794138
Here are the step by step instructions to install:
http://forum.xda-developers.com/showthread.php?t=794138
For custom roms, it gets more cloudy because some (only a few) require CWM 3 and some (most I think) work on CWM 2.5 or earlier but not CWM 3. Just read through the requirements of the rom before attempting to install. I found Randy Shear's vids on youtube to be very helpful when reading through these threads only got me so far.
I agree, Odin probably is the easiest method, but the OP states that he only has access to a Mac at the moment, and not a PC.
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.
HI
I would like to ask if there is some way how to remove clockwork mode without reflashing back to stock ROM.
The reason: I am not able to use standard update for 1.82 stock. My mobile is rooted and use OC mode. Everytime I download update and try to update the phone get some error about signature after reboot in cwm. If I switch checking the signature off and manualy choose the file it always ends with error....My gues is that it is due to cwm.
Thanks,
Grab your stock recovery image from your specific stock ROM zip file (they might all be the same, but I've never checked). Then use something like flash_image to flash it to your phone. Or if you have the engineering HBOOT installed, you could use fastboot from your computer to install it (search for guides on that).
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.