I upgraded from .79 to .92 and now the phone only boots to the bootloader. I can't do anything with fastboot (remote not allowed) and I'm unsure of what to do from here.
I was trying to upgrade my ROM to Redemptive 2.3 and it said to place the hboot and upgrade it, I did and after it reboots it just instantly goes to the bootloader.
Any ideas?
Flashed this file and it works (I think)
http://files.virtuousrom.com/inc/misc/PB31IMG.zip
This includes a boot image, recovery, and the hboot. I'm guessing the zip I flashed only did the hboot and the rest broke.
Related
I have a rooted version OTA 3.29.651.5 (had stock 3.26, upgraded with OTA, then used UR 3.21 one-click root and gained root and permanent nand unlock, lots of thanks to the unrEVOked team for making it that easy), everything is fine, I don't really have any problems removing bloatware and doing things that root allows you, I'm not a custom rom kind of person, so I am happy keeping the rooted stock rom with the newest radio / PRL / PRI. However, I was doing some research on how to get a custom splashscreen installed with the "fastboot flash splash1 xxxxx.rgb565" command while in fastboot bootloader.
I did that, and I would get something like "send: ok, write: failed, remote: not allowed". I did some research on this, and realized it is because I don't have the extended eng fastboot commands with the 0.79.0000 fastboot (dated Aug 20, 2010). I did some more research, and used the instructions by kpkimmel from "forum.xda-developers.com/showthread.php?t=800859" (thanks for the great and clear instructions) to put 0.76 hboot with the extended ENG commands on as my bootloader (I did it through sdcard root folder and fastboot with PC36IMG.zip). As I was kind of worried about already, the phone would not boot up after I installed 0.76.2000, I assume because the new radio version I have is not compatible with 0.76.2000, the text file in the PC36IMG.zip that I used seems to refer to rom version 1.32.xxx or similar, so it must need an older radio. Well, I don't really want to downgrade the radio or prl on my phone just to get a custom boot screen. Anyway, after successfully installing 0.76.2000 (title said hboot 0.76.2000, ENG S-off), my phone would not ever go past bootloader, I could get clockworkmod recovery to work, but my nandroid restore would fail, it would say "failed loading boot image".
So from what I kinda thought about the radio or something else being incompatible with the older 0.76.2000, I just flashed the custom screen (it worked perfectly with 0.76.2000), then extracted the 0.79.0000 hboot.img (dated Aug 2010) and the text file from a 3.29 rom, put it in a new PC36IMG.zip, and flashed hboot again through bootloader, it went back to 0.79.0000 still with nand unloacked and root, and then the phone booted up just fine, back into my rooted stock 3.29 rom, didn't even have to do a nandroid restore, my phone was exactly as it was before the 0.76.2000 bootloader flash, same radio, kernal, everything, obviously now with a new splash screen, different from the black text on white background stock splash screen.
Sorry for the long expl, wanted to give everyone a background. So my question is: Can I avoid having to flash 0.76.2000 every time I want to flash a new splash screen, and have eng extended fastboot commands while maintaining a bootloader compatible with my radio and rom version? What I'm asking is, is it possible to have a 0.79 hboot version WITH the extended commands? Would anyone, maybe like toast or flipzmod, be able to make that, so there is no need to pull the sdcard several times while in hboot, switch PC36IMG.zip with different hboot versions, then go back to the original after flashing the new splash screen? This would really make things a lot simpler.
Why didn't the nandroid restore work by the way with 0.76.2000? Isn't that a bad thing if even nandroid won't get you back to where you were? I got lucky going back to the stock hboot fixed it.
Thanks
u cant nandroid restore a backup unless ur using same hboot u used when creating the nadroid restore for instance i installed cyanogenmod6 with hboot 76 i couldnt restore my fresh nandroid it kept failing till till i put the hboot back to version 93 then i could restore the nandroid since when i created the nandroid i was on hboot 93 so i had too update my hboot just to restore my nandroid
my solution is to have the diffrent versions of hboot pc136img on your sd so u can flash them on the go see thread http://forum.xda-developers.com/showthread.php?t=801568
so basically if u create a nandroid with with hboot 76 and your on hboot 93 u cant restore it till ur on same hboot vresion u created it with i dont believe its something devs can change it has to do with md5 errors that dont check out prpoperly unless same hboot is used when creating nandroid hope this helps u out a bit feel free to pm me
Simply re-flash your ROM's kernel or the ROM itself, really. That fixes it. Doing a nandroid won't work. I've run into this issue a couple times and that fixed it.
Hi,
may be its already known, but i just realized one cool thing - if u have s-off bootloader, u are still be master of your device, even if u have installed Stock RUU or OTA and lost recovery & root. You want to ask how ?
1) Take somewhere CWM image in .img format and rename it to recovery.img
2) Take file android-info.txt from RUU of Stock ROM u have installed
3) Put above 2 files into PC10IMG.zip archive
4) Copy created PC10IMG.zip to root of your sd card
5) reboot into bootloader mode (press and hold 'volume down' then 'power' until u see bootloader screen.
6) be patient while it find your PC10IMG and ask if you really want to flash it. Here should word RECOVERY.
7) Agree to flash (press 'volume up')
8) Wait while it flashes recovery, when it finish - ask you to press 'power' to reboot
9) Woala! Now you have custom recovery and free to flash any custom ROM or just Superuser update to obtain root with stock rom.
As i understand that way will work to flash any part of ROM (system, boot, etc.)
Btw, for those who scare - just tested that twice: 1st time flash old recovery 3.0.0.5, reboot into recovery and checked that version is 3.0.0.5; then flashed latest one 3.0.2.4 - now recovery is of version 3.0.2.4.
I prepared PC10IMG.zip with clockworkmod recovery 3.0.2.4 - http://www.multiupload.com/6LOA99IGW1 .
i got my phone back from repair unrooted and with stock 2.3.3 rom. somehow it had SHIP S-OFF though and this worked for me. right now i'm doing a backup of the rom, and afterwards i'll try restoring cm7 from before i sent the phone in for repair...i'll keep you posted.
I went through this whole ordeal not long ago. I had eng hboot, radio s-off, root, nine yards. Messed up the rom I had, and had the official GB pc10img on the root of my sd card, not thinking (and needing my phone asap) I went ahead and installed it. I ended up just downloading the official ota update pc10img, flashing it, and rerooting/flashing eng hboot.
As long as you have S-OFF in the bootloader, you can flash ANY pc10img meant for the htc vision.
I managed to install CM6.1.1 so that I would have android 2.2 (not sure if this was necessary), got perma root and pushed ENG HBOOT. Now on CM7.1, no issues to report.
So does it work with stock 2.3.3? Great!
edit, where is "android-info.txt" ? Because i upgraded via OTA.
No, it only works with a previously rooted and s-offed phone with latest RUU installed. Then you still have S-OFF but stock firmware without custom recovery. This method will give clockworkmod back.
God damn it, I think I messed up here. I got a replacement G2 since mine has gone bananas! So I got Rooted with S-Off but I think I flashed the DesireZ PC10IMG.zip since I wanted to install doubleshot roms and so on. However after I flashed it my phone gets stuck at the HTC screen now?
When I try to boot into Recovery it's still under Recovery v3.0.2.4 so I can't even restore my phone to a previous back up since these back ups were created with the latest Recovery version.
I went ahead and downloaded the stock G2 Rom from here: http://forum.xda-developers.com/showthread.php?t=788489
However, when I renamed it to PC10IMG and put it on the the root of the SD-Card Bootloader will not flash the .zip and I get some sort parsing message and I get right back to the Bootloader screen.
I also can't follow the guide here: http://forum.xda-developers.com/showthread.php?t=999796 - to restore the stock H-Boot since I can't even boot the damn thing!
HELP!
Flash a new rom in recovery, or if you have eng hboot, flash latest recovery, restore nandroid.
-Nipqer
What does it say when you go into the bootloader? There should be a hboot version towards the top of the screen?
Also, have you tried flashing a rom using recovery? It sounds like it is working- just get a normal rom, nothing that is named PC10IMG.zip. Maybe try one of the CM stable releases.
Nipqer said:
Flash a new rom in recovery, or if you have eng hboot, flash latest recovery, restore nandroid.
-Nipqer
Click to expand...
Click to collapse
Now see....... Why didn't I think of that?..... FAIL!
I have an incredible that bootloops at the white screen that was s-on that I got to repair. I tried to flash the gingerbread RUU through hboot and the exe and it still bootlooped. I saw that the official unlock method came out so I updated to the 1.02.0000 hboot and unlocked the phone. I flashed cwm through fastboot but the phone still bootloops. Since the official unlock doesn't allow all the fastboot commands, I can't completely wipe the system or flash different radios, hboot, NV etc. I think this phone is completely bricked unless I can find an RUU that will work with the 1.02.0000 hboot. Since you can't flash RUUs while the phone is unlocked, I have to relock and then I get the main version is older error.
Try flashing this one thru hboot. Its stock GB ruu modified for new hboot.
http://dinc.does-it.net/New_Hboot/StockGB/PB31IMG.zip
And also try this. Its cwm recovery updated for the new hboot.
http://dinc.does-it.net/New_Hboot/CWM_5.2.0.2/PB31IMG.zip
thanks for the files. The RUU reads but stops after parsing. The cwm file does flash correctly, but I still cannot access recovery. I think the partitions are corrupt on the internal memory and I can't ADB in to fix them without recovery. Sucks, I spent way too much time trying to fix this phone. Its perfect condition, but its not worth my time anymore. Hopefully I can resell it for what I paid.
these files need to be stickied somewhere. I searched for around 4 hours on how to root after htcdev unlock and finally found this
the modded RUU wont flash via a locked s-on hboot if its not signed by htc. simply pulling the hboot out wont trick the phone into flashing it,as it breaks the signiture.
if flashing it unlocked,the modified RUU is not working for 1 or both of these reasons:
1)the main version may be higher than that on the android info text doccument
2)you need to also pull splash.nb0 and radio out,as htcdev only lets you access boot/system/recovery.
check your main version number in fastboot with fastboot getvar all
make yourself up an "RUU" using only the system/boot/recovery images,and the Android info text document. if your mainversion is less than 4.08.605.2,then your good to go. just realize that this is going to change it to that. if your main version is higher,then youll have to edit the android info to reflect your current main version before zipping it back up with the images. flash it with bootloader unlocked.
if you can at least get a working custom recovery via htcdev(i use fastboot flash rather than PB31IMGs) then you can flash superuser,and mount data,and rewrite your misc image to downgrade.
we are working on downgrading an htcdev hboot to the .79 in this thread: http://androidforums.com/incredible-all-things-root/495687-htc-dev-unlock-problems.html
and the adb commands and such for rewriting the misc image are in this thread: http://androidforums.com/incredible-all-things-root/427344-how-root-2-3-4-downgrade-get-s-off.html (some specific comments on recovery/adb in post #865)
if you cant get a recovery to permanently flsh,try booting it into memory with unlocked hboot and
fastboot boot <recovery name>.img
unfortunately,ive learned alot about htcdevs limitations with my rezound. holler if i can be of further assistance
cmlusco said:
Try flashing this one thru hboot. Its stock GB ruu modified for new hboot.
http://dinc.does-it.net/New_Hboot/StockGB/PB31IMG.zip
And also try this. Its cwm recovery updated for the new hboot.
http://dinc.does-it.net/New_Hboot/CWM_5.2.0.2/PB31IMG.zip
Click to expand...
Click to collapse
Thanks, I did it with this file and it worked like a charm.
Thanks guys
Hi..
I have been flashing roms for a few years now on a previous HTC Desire and now on my HTC One X.
All was well until today.
I decided to go for a JellyBean custom rom and flashed the .boot img in the wrong order. Due to my hboot version (1.28) I was ment to flash the boot.img first (but it never said this in the installation instructions, anyway...)
Basically, I got stuck in a boot loop and not able to get into recovery at all. I can only get into hboot / fastboot.
I have tried installing my stock RUU and relocking bootloader to get completely back to stock but keep getting an error due to the 1.28 hboot not being compatible with it.
I have working roms on my phone I can flash but I just cant get into CWM whatsoever, when I click on Recovery it just reboots itself. Can't install stock RUU.
What are my other options? Can I flash a rom some other way? I'm basically stuck in hboot/fastboot...
tldr;
stuck in hboot, can't get into recovery, stock RUU won't flash due to hboot version.
My phone was fully charged when I started 20 minutes ago.
Please help.
Thank you...:good:
EDDDDIITTTT::
Wow. Just RE-unlocked my bootloader and it rebooted itself straight into the custom rom I was trying to install. Strange!? All is well now.
Anyway, thanks for listening.