Related
I successfully rooted my phone but after trying to get Cyanogen running view ROM Manager, really hosed things.
I HAD made a nandbackup that I had successfully rested to, but doing so now gives an error.
My situation is that when I try to start from scratch, I can't--resetting the phone to factory settings doesn't work either. I've followed the directions here:
How to start over: Fully rooted stock 1.47.651.1 in one shot (no adb!)
forum.xda-developers.com/showthread.php?t=715915
and here:
[TUTORIAL] How To Root The HTC EVO ~ Part-1 \0/
forum.xda-developers.com/showthread.php?t=690762
But the issue seems to be that whenever I get into the Bootloader, the PC36IMG.zip file isn't being found. I've uncompressed it to ensure its not corrupt.
When the boot loader comes up, it's version is HBOOT-0.76.2000, and even though I'm following the directions from the 1st link above, the PC36IMG.zip file just doesn't get found and I'm in an endless world in the bootloader.
How can I figure out what I need to do to get my Evo working again?
aagha said:
I successfully rooted my phone but after trying to get Cyanogen running view ROM Manager, really hosed things.
I HAD made a nandbackup that I had successfully rested to, but doing so now gives an error.
My situation is that when I try to start from scratch, I can't--resetting the phone to factory settings doesn't work either. I've followed the directions here:
How to start over: Fully rooted stock 1.47.651.1 in one shot (no adb!)
forum.xda-developers.com/showthread.php?t=715915
and here:
[TUTORIAL] How To Root The HTC EVO ~ Part-1 \0/
forum.xda-developers.com/showthread.php?t=690762
But the issue seems to be that whenever I get into the Bootloader, the PC36IMG.zip file isn't being found. I've uncompressed it to ensure its not corrupt.
When the boot loader comes up, it's version is HBOOT-0.76.2000, and even though I'm following the directions from the 1st link above, the PC36IMG.zip file just doesn't get found and I'm in an endless world in the bootloader.
How can I figure out what I need to do to get my Evo working again?
Click to expand...
Click to collapse
Did you make sure you have the PC36IMG.zip is on the root of your sd card?
Also, you can just boot into recovery from hboot and just flash your custom rom again to get out of it.
jxr94 said:
Did you make sure you have the PC36IMG.zip is on the root of your sd card?
Click to expand...
Click to collapse
Yes, I did.
jxr94 said:
Also, you can just boot into recovery from hboot and just flash your custom rom again to get out of it.
Click to expand...
Click to collapse
When I boot into Recovery and get taken to ClockworkMod and try to do a recover of the 1st (funtioning) Nand backup I made, the whole backup restores in ClockworkMod only, but when I reboot, I get sent to the bootloader and can't get out of it--which is my original problem.
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.
Hi, everyone who have been waiting for a way to downgrade their HBOOT so that they can get S-OFF, cause they upgraded to the Official RUU Rom... I think I found a solution for you!
Also give you permanent ClockWork Recovery!
I haven't test it on any other Slide, cause I have only one. So, sorry if it didn't work for you.
Here is what I did, in case you're wondering, I downloaded the Official RUU from HTC Support website, extracted the 'rom.zip' file from Windows Temp folder that it creates, replaced the newer 1.02 HBOOT with 0.52 HBOOT, that I got from 'ESPRIMG.zip' (the Stock rom).
And also replaced the recovery.img with ClockWork Recovery img file.
Then I just renamed the 'rom.zip' file to 'ESPRIMG.zip'
Put it in the root of my memory card, powered off, rebooted into BOOTLOADER, and it detected the file and asked me if I wanted to update, I chose YES, and it went on without a hitch. Next thing I knew, I had 0.52.0000 HBOOT, with permanent ClockWork Recovery(so I dont have to use 'update.zip' anymore), and also the Official Latest 2.15.531.3 unmodified rom, (I like stock Espresso, that's why I bought it ) but you will LOSE ROOT but SuperOneClick method works for me to gain root - http://forum.xda-developers.com/showthread.php?t=803682
Method:
1. Download this 'ESPRIMG.zip' file - http://www.mediafire.com/file/cuemg74en7kk0a3/ESPRIMG.zip
2. copy/paste it to your memory card, in the root, not on any folder.
3. Make sure your card formatted to FAT32 file system, or it won't detect it.
4. Do a Nandroid BACKUP, if you can, cause I don't know if this will work for you. But it will wipe all your data and setting. SO BACKUP!
5. First you need to wipe data and factory setting, and wipe cache and wipe davlik cache (Otherwise it bootlooped for me). So boot into recovery first!
You can do that by going into BOOTLOADER first then selecting Recovery ( for that remove memory card from mobile or else it will start update) or if you have ROM Manager then you can use that to reboot into Recovery, any recovery will do stock or clockwork.
6. Ok, so after Wiping from recovery. PULL battery, then insert back the memory card with ESPRIMG.zip file on it. Reboot into BOOTLOADER, and apply the update.
It should do a reboot automatically to downgrade the HBOOT.
You will see the change if it worked. After applying the update, reboot phone normally.
And if all done correctly, you should have 0.52.0000 HBOOT, and also a permanent ClockWork Recovery. Now you can root by using SuperOneClick method. And also get S-OFF (I didn't need it, cause I have permanent S-OFF! , at least that's how I explain it)
Im guessing it worked for me because I have a factory unlocked S-OFF HBOOT from HTC. Because, to try this out first, I updated my phone via the OFFICIAL RUU from HTC Support Website and it showed S-OFF on my 1.02.0000 HBOOT.
Then I tried this method and it did downgrade my HBOOT and I still had S-OFF without doing the AlphaREV method.
So I guess I have a kind of permanent S-OFF??! :S :?
Hit thanks if it helped.
I am no developer but I am learning
Any feedback would be appreciated.
And yes, my major is CS and I LOVE IT!
any one test this yet?
If i try this and it does not downgrade my HBOOT will my phone be bricked? Will I lose root? I would love to try, but would like a little certainty.....
DylanTheVillian said:
If i try this and it does not downgrade my HBOOT will my phone be bricked? Will I lose root? I would love to try, but would like a little certainty.....
Click to expand...
Click to collapse
I don't think that you phone will be bricked, it would just not downgrade it but the HBOOT will remain. Yes you will lose root, but that can be gained easily by SuperOneClick Root Method.
I not certain myself about the brick. Flash at your own risk.
Could you provide a download link of your ESPRIMG.zip?
lvzhuyiyi said:
Could you provide a download link of your ESPRIMG.zip?
Click to expand...
Click to collapse
LINK updated in main post.
Good job thnx
MamaRisha said:
Good job thnx
Click to expand...
Click to collapse
Did it work?
has this worked for anyone?
I'll be trying it once the download finishes for me. I'll update you guys on whether or not it worked for me.
I'm using a full stock phone btw, factory reset and blank sdcard as well. Hopefully this works for me.
UPDATE:
Looks like this was a dud.
I applied the update 3 times to my phone, but my Hboot still didn't downgrade. It's still on 1.02.0000. Also didn't flash the permanent Clockwork Recovery that we were hoping for either.
I'm guessing your permanent s-off is what let you use this successfully. So for anyone who has S-OFF already this would probably work fine.
On the plus side, it didn't brick me =)
AlanB412 said:
I'll be trying it once the download finishes for me. I'll update you guys on whether or not it worked for me.
I'm using a full stock phone btw, factory reset and blank sdcard as well. Hopefully this works for me.
UPDATE:
Looks like this was a dud.
I applied the update 3 times to my phone, but my Hboot still didn't downgrade. It's still on 1.02.0000. Also didn't flash the permanent Clockwork Recovery that we were hoping for either.
I'm guessing your permanent s-off is what let you use this successfully. So for anyone who has S-OFF already this would probably work fine.
On the plus side, it didn't brick me =)
Click to expand...
Click to collapse
Well thanks for the feedback, yes I think its the permanent S-OFF too. So does that mean I have a phone that was permanently UNLOCK my T-mobile or HTC it self for testing purposes? Is there some way to use this to unlock that 1.02.0000 HBOOT?
any updates on how to downgrade?
i need to downgrade my Espresso, i have the latest official t-mobile update.
i have already followed instructions very carefully missing no details.
i have searched everywhere and tried everything. thank you.
ESPRESSO PVT SHIP S-ON
Hboot: 1.02.0000
MICROP-0620
TOUCH PANEL-SYNW0101
RADIO-7.15.35.16
Nov 26 2010,20:43:01
'ESPRIMG.zip' cannot be downloaded
Gold Card
Would using a GoldCard get us around this problem?
1) can the stock 2.3.4 rom be flashed via CWM recovery?
(i know i can rename it to PD15IMG and "update" it that way but i'm more comfortable using the cwm recovery)
2)after flashing a rooted stock 2.3.4 rom, will i still have cwm recovery, unlocked bootloader ect. ?
I think that your recovery MAY get wiped, you will keep s-off and you will lose root
Then again I don't know anything
N_otori0us_ said:
I think that your recovery MAY get wiped, you will keep s-off and you will lose root
Then again I don't know anything
Click to expand...
Click to collapse
Place the stock zip on the root of SD card then reboot into recovery by holding volume down and power and it dose the rest no need for flashing. And you do loose root and cwm I just found out and now cant root and try my new Rom :crying: Damn you Windows 8.1 Damn you!!! Cant find the drivers
keifus.rahn said:
Place the stock zip on the root of SD card then reboot into recovery by holding volume down and power and it dose the rest no need for flashing. And you do loose root and cwm I just found out and now cant root and try my new Rom :crying: Damn you Windows 8.1 Damn you!!! Cant find the drivers
Click to expand...
Click to collapse
Dual boot linux mint.
Sent from my HTC Glacier
N_otori0us_ said:
Dual boot linux mint.
Sent from my HTC Glacier
Click to expand...
Click to collapse
Ive tryd putting duelboot on my new laptop its way to much truble than what its worth im just gonna have to dig out my old one
Hi
I was just trying to relock my bootloader on my device, so I patched the boot.img with magisk and ran unlockbl.sh again, it locked it fine but now it boot loops. I tried restoring a backup through twrp (I just boot the image) but doesn't work. Is there a way I can flash the .zip file downloaded from Asus? Anyone have any ideas?
Thanks
mike_1983 said:
Hi
I was just trying to relock my bootloader on my device, so I patched the boot.img with magisk and ran unlockbl.sh again, it locked it fine but now it boot loops. I tried restoring a backup through twrp (I just boot the image) but doesn't work. Is there a way I can flash the .zip file downloaded from Asus? Anyone have any ideas?
Thanks
Click to expand...
Click to collapse
I managed to boot it using the patched_boot.img so I went ahead and unlocked the bootloader again, it's booting now normally but I still wanted to lock the bootloader and put it back to factory settings? I tried booting with the boot.img from the asus website download but it freezes it.
mike_1983 said:
I managed to boot it using the patched_boot.img so I went ahead and unlocked the bootloader again, it's booting now normally but I still wanted to lock the bootloader and put it back to factory settings? I tried booting with the boot.img from the asus website download but it freezes it.
Click to expand...
Click to collapse
Not sure why you want to re-lock the bootloader, but if you do, you've re-enabled image verification, so it won't allow your patched_boot to load. Other changes made are stopping even the factory boot.img from being able to successfully complete.
You can very easily just go back to full stock, by simply installing the entire factory image from the Asus website. Just throw it on your sd card or somewhere on your internal storage that you can find, and install it with TWRP.
HTH
beachfl said:
Not sure why you want to re-lock the bootloader, but if you do, you've re-enabled image verification, so it won't allow your patched_boot to load. Other changes made are stopping even the factory boot.img from being able to successfully complete.
You can very easily just go back to full stock, by simply installing the entire factory image from the Asus website. Just throw it on your sd card or somewhere on your internal storage that you can find, and install it with TWRP.
HTH
Click to expand...
Click to collapse
Hi
Thanks for the help! I have managed to get it back to completely stock with locked bootloader. I am thinking of selling it so wanted it back to stock. I spent ages on it this afternoon! I did try and flash the factory image in twrp before, but it must have been when the bootloader was locked so it wasn't flashing properly (I also probably needed to have the .zip on a sd card rather than internal storage like I had before!) So I flashed it when the bootloader was unlocked and it booted up correctly, after a long anxious wait! Then I booted the patched_boot and it needed to update magisk so I could get su access, copied the unlockbl.sh files to the correct directory and ran the program it locked it and booted up normally, then I factory reset again to get rid of magisk manager.
Thanks again!
mike_1983 said:
Hi
Thanks for the help! I have managed to get it back to completely stock with locked bootloader. I am thinking of selling it so wanted it back to stock. I spent ages on it this afternoon! I did try and flash the factory image in twrp before, but it must have been when the bootloader was locked so it wasn't flashing properly (I also probably needed to have the .zip on a sd card rather than internal storage like I had before!) So I flashed it when the bootloader was unlocked and it booted up correctly, after a long anxious wait! Then I booted the patched_boot and it needed to update magisk so I could get su access, copied the unlockbl.sh files to the correct directory and ran the program it locked it and booted up normally, then I factory reset again to get rid of magisk manager.
Thanks again!
Click to expand...
Click to collapse
Well done ? so glad it got sorted x
Sent from my Asus P027 using XDA Labs