From what I understand, the bootloader program (hboot) is completely separate from the rest of the operating system and recovery programs. It's the first program that loads when the phone is started and orchestrates the rest of the boot process.
The bootloader need to be replaced in order to root the phone. But once this is done is it never needed to be touched ever again? When rooted, does this mean you can replace your bootloader at any time without affecting access to your installed recovery program?
cytherian said:
From what I understand, the bootloader program (hboot) is completely separate from the rest of the operating system and recovery programs. It's the first program that loads when the phone is started and orchestrates the rest of the boot process.
The bootloader need to be replaced in order to root the phone. But once this is done is it never needed to be touched ever again? When rooted, does this mean you can replace your bootloader at any time without affecting access to your installed recovery program?
Click to expand...
Click to collapse
With our heroc's the bootloader isn't needed to root and install a custom recovery. However people generally do it so you can flash via fastboot if ever needed.
Once you unlock (or install the eng-spl) hboot no it's never touched or needed to be touched again unless you RUU. You could replace the bootloader whenever you wanted and not effect anything else but there really isn't much of a point.
Shelnutt2 said:
With our heroc's the bootloader isn't needed to root and install a custom recovery. However people generally do it so you can flash via fastboot if ever needed.
Once you unlock (or install the eng-spl) hboot no it's never touched or needed to be touched again unless you RUU. You could replace the bootloader whenever you wanted and not effect anything else but there really isn't much of a point.
Click to expand...
Click to collapse
Thanks for the info, Shelnutt.
I'm kind of in a peculiar "Nexus" that I'm trying to extricate myself from. I have S-ON presently. I would like to change it to S-OFF, but I can't seem to do it. I suspect it's the bootloader preventing me, which is hboot 1.7. So, I tried to replace the bootloader and the attempts fail. I've tried it through the adb shell, fastboot, terminal emulator on the phone, and via the recovery manager (TWRP). Attempting to replace the bootloader results in "signature verify fail". Through TWRP, it also said verification failed.
I also tried to retrieve the identifier token (HTC dev) so that I could unlock the phone that way, but "fastboot oem get_identifier_token" fails with a "Command error" (although I can execute "fastboot oem rebootRUU" with no problem).
I also tried to use Regaw's boot mod tool, which replaces the bootloader and turns S-OFF. But it aborts because my Hero is already rooted. So I went into my z4Root application and selected "un-root". It said "done", but the phone remains rooted. I even tried to "Re-root" but it wouldn't complete (thinking if I root it again, I could then try another un-root).
I'm thinking I should just flash back to stock, but... I don't have any fresh nandroid backups to use. TWRP doesn't do nandroid. It does its own thing, which becomes a problem because TWRP needs Android 2.2 or higher. So... does that mean I need to install ROM Manager again, do a nandroid backup, then run an RUU back to full stock again?
For the eng-spl when it says signature failed, you just need to disable signature checking. In CWM it's in the flash .zip menu. Not sure where it's at for TWRP. If you have the 1.47 hboot like you say thought you can't flash to 1.46 without being s-off first.
For regaw's hboot, he hard hard coded radios version into it. So in all likelyhood you're error is about the radio. It never checks for root inside the room, as it doesn't effect flashing a new hboot. My suggestion is to flash this radio and see if regaw's method works.
https://docs.google.com/open?id=0B9lyYjZr_O3gYy1xclMzbURyd0k
Shelnutt2 said:
For the eng-spl when it says signature failed, you just need to disable signature checking. In CWM it's in the flash .zip menu. Not sure where it's at for TWRP. If you have the 1.47 hboot like you say thought you can't flash to 1.46 without being s-off first.
For regaw's hboot, he hard hard coded radios version into it. So in all likelyhood you're error is about the radio. It never checks for root inside the room, as it doesn't effect flashing a new hboot. My suggestion is to flash this radio and see if regaw's method works.
https://docs.google.com/open?id=0B9lyYjZr_O3gYy1xclMzbURyd0k
Click to expand...
Click to collapse
Thanks, you're right... in TWRP there's a checkbox to control that. There's also one to verify md5, but it requires a file (I guess it looks for [filename].md5). In any case, getting past that resulted in failure to load hboot 1.46 as you surmised.
The issue with Regaw doesn't seem to be the radio. It simply reports that there's nothing to do because the phone is already rooted. Apparently it will only run if the phone is not rooted. And to unroot, it appears the only way is by RUU. Z4Root is supposed to allow it, but when selected it doesn't do anything.
So, I finally came up with something that got me on the right path. :good:
I re-installed ROM Manager and flashed the latest ClockworkMod to Recovery. From there I could apply the hboot 1.46 ENG-SPL with no issues. I rebooted into the bootloader and saw................ HERO XC ENG S-OFF, HBOOT-1.46.2000. :highfive:
Related
GSM SLCD Nexus One
Hboot 0.35.0017
S-On
Locked Bootloader
Somehow I managed to get stuck here, I'm still not sure how. If I had to guess it would be the bootmanager application, although I haven't used it since this morning.
I really would like to keep the bootloader locked if at all possible. The phone was rooted before.
I figured I could just flash a recovery that's signed (hboot signature verification fails on cwm and amon_ra, via fastboot) but I can't for the life of me find one.
In the bootloader, I click on recovery, shows the n1 splashscreen briefly, then sends me to fastboot.
Thanks for the help.
You won't be able to put a custom recovery on there without unlocking the bootloader or reseting your phone. If you are really wanting to keep the bootloader intact, the easiest thing would be to do the PASSIMG method. Have a look in the wiki and it will explain everything to you. Then once you get back into Android, root the phone before it updates to Gingerbread and then install ROM Manager to get your custom recovery back.
I actually just ended up unlocking it and using fastboot to put a new recovery on it. I didn't know about the PASSIMG method. Thanks for your response anyway though.
I recently came across a modified Google Nexus One (N1) that has been experimented on. Upon boot up, I get a black screen with the HTC logo and four exclamation marks inside triangles in each of the four corners of the screen. As I attempted to enter hboot, I saw it has been replaced with Blackrose which leads me to believe it has been unlocked/rooted at some point in time. ( I am fairly new at this, but I lurk around the forum ). I tried hooking the N1 up to RUU to flash it back to a stock ROM, however that proved unsuccessful - the phone boots up to the above mentioned logo and stays that way. When I try to go to recovery/hboot, instead of the usual menu choices, there's only RUU as an option... Is the phone bricked, and if not, how can I revert it to a working state ?
I have attached pictures of what the boot screen looks like, as well as the recovery menu.
Thank you in advance.
It's in the middle of RUU mode, entered by executing "fastboot oem rebootRUU" (I might not remember it 100% correct, so check it with Google).
This should be enough for you to check with Google how you exit RUU mode.
The only way I see to exit this mode is if I flash it with something via fastboot ( since no recovery works, custom or stock ). What image file or zip do I flash it with, in order to revert it back to complete stock ( stock hboot, stock recovery, stock ROM ) - I want the phone like it was out of the box, so I can reroot it and unlock it myself.
I tried flashing it with PASSIMG_Passion_Google_WWE_3.13.1700.1_GRK39F_release_signed.zip through fastboot, for a moment it seemed to be going ok, then at the very end, while it was unpacking the [user data] image I get a partition update fail message 51, and after reboot - still the gray HTC letters and Blackrose instead of HBOOT.
Any suggestions ?
Short googling with the error would have revealed you the bad news.
Partition update fail means bad stuff - your NAND is malfunctioning, which equals a dead phone.
Have you tried to uninstall Blackrose?
tommert38 said:
Have you tried to uninstall Blackrose?
Click to expand...
Click to collapse
doesn't the phone need to be working in order for me to hook it up to Blackrose ? As of now, with this screen, the PC doesn't seem to detect it as a working phone, only fastboot. And Blackrose just says waiting for device... how do I uninstall it then?
I also tried this RUU: RUU_Passion_Vodafone_Generic_3.11.151.3_GRJ22_release, flashing the ROM to an image version 3.11.151.3, but at the end I get a message saying ERROR [110]: FILE OPEN ERROR. The RUU cannot open the requested files or the files are damaged. The RUU cannot continue with the update. Please get a complete RUU package and try again. Can someone please refer me to a working RUU package for the Nexus One, I am really scared of experimenting trying to find one by myself, seeing how the phone is already hanging in the balance, I would be thankful
You could try to flash this stock HBOOT, and if you have resized partitions I guess you could always use blackrose_manual_120421.zip to change to stock partition layout (145/95/196).
Edit: I've never flashed a HBOOT this way, and I never resized my partitions the manual way, so I would check the Blackrose for details. And I'm not responsible if you brick your phone
Edit2: I see you haven't got working recovery, so you should find a way to flash the HBOOT via fastboot. Maybe the Blackrose developer dla5244 can help you out (or Google).
Edit3: You could also try to flash this engineering HBOOT
tommert38 said:
You could try to flash this stock HBOOT, and if you have resized partitions I guess you could always use blackrose_manual_120421.zip to change to stock partition layout (145/95/196).
Edit: I've never flashed a HBOOT this way, and I never resized my partitions the manual way, so I would check the Blackrose for details. And I'm not responsible if you brick your phone
Edit2: I see you haven't got working recovery, so you should find a way to flash the HBOOT via fastboot. Maybe the Blackrose developer dla5244 can help you out (or Google).
Edit3: You could also try to flash this engineering HBOOT
Click to expand...
Click to collapse
Thanks for your time friend, I tried the above mentioned steps, it says OK all across the board in fastboot while I flash, but after I reboot it just goes back to the same screen, stuck in RUU. I did some digging around and found this which seems to be exactly my problem:
RUU PROBLEMS
"I tried using a RUU, but it failed, and now my phone is stuck on a black HTC Screen with /!\ In every corner!"
Possible Causes:
- You were S-OFF and you flashed a custom bootloader from alpharev
- You didn't check the MD5 Sums before proceeding, and the download may have been corrupted.
- You tried using the wrong RUU
Fixing your problem
Your phone is stuck in RUU mode. RUU mode is like fastboot mode, and can still receive fastboot commands, therefore it can be easily "fixed".
It helps to have a goldcard for this problem, so that you can use any RUU you want.
S-OFF
[STEP1]- download "Bravo Stock" from Alpharev
[STEP2]- download Android Flasher
[STEP3]- use android flasher to flash "Bravo Stock"
[STEP4]- run the RUU again and wait for it to finish
S-ON
If you're S-ON it eliminates the possibility of you having a custom bootloader, and the only possibility now is that the RUU was corrupted or you
used the wrong RUU for your device. Therefore, for this process you need a goldcard.
[STEP1]- Create the goldcard from the tutorial
[STEP1]- Use the WWE RUU
However, this is from a thread for the HTC Bravo. Anything similar for the N1 ?
Edit1: Could it be that the hboot partition was resized with Blackrose and therefore the RUU I tried to flash it with needs stock partition layout ?
Your partitions ARE resized. 2nd picture 2nd line JB-220/10/206. If it's b*tching about the resized partitions, then that would be about your cache partition (which is 85MB smaller than its stock size).
Edit: you should also try to wipe your partitions with fastboot, then flash the img's that are inside the passimg
what's the command line to wipe the partition ? fastboot format hboot/recovery/system ?
Dude, your Nexus One is dead, the internal NAND is damaged and therefore unrecoverable.
Sent from my Nexus S using Tapatalk 2
fastboot erase system/cache/userdata/boot
Basically I successfully did everything necessary to unlock the bootloader and root the phone and I also flashed Superuser and had it confirmed by rootchecker. Where my phone got screwed is when i attempted to flash Android Revolution HD.
After flashing the ROM and pressing restart within TWRP recovery my phone went straight to the bootloader. Anything I did, from attempting to enter recovery or even power off the phone just sent me back to the bootloader.
I managed to re-flash TWRP and am able to access recovery BUT my entire phone is wiped (no backups ,roms, etc.) and my attempt to revert back to the original Sprint RUU has failed 3 times.
What I've noticed in the videos of people updating to the original Sprint RUU is that their image version for the current version is 1.2xxxx and is identical to the one they're updating to while mine is from: 1.31.651.2 to: 1.29.651.10.
Desperately in need of help as this phone is not even 2 weeks old.
MrAdrianP said:
Basically I successfully did everything necessary to unlock the bootloader and root the phone and I also flashed Superuser and had it confirmed by rootchecker. Where my phone got screwed is when i attempted to flash Android Revolution HD.
After flashing the ROM and pressing restart within TWRP recovery my phone went straight to the bootloader. Anything I did, from attempting to enter recovery or even power off the phone just sent me back to the bootloader.
I managed to re-flash TWRP and am able to access recovery BUT my entire phone is wiped (no backups ,roms, etc.) and my attempt to revert back to the original Sprint RUU has failed 3 times.
What I've noticed in the videos of people updating to the original Sprint RUU is that their image version for the current version is 1.2xxxx and is identical to the one they're updating to while mine is from: 1.31.651.2 to: 1.29.651.10.
Desperately in need of help as this phone is not even 2 weeks old.
Click to expand...
Click to collapse
Here you can find the RUU. I don't know wich one you want ..
Install this RUU in Fastboot (USB) otherwise it won't recognize your phone!
MrAdrianP said:
Basically I successfully did everything necessary to unlock the bootloader and root the phone and I also flashed Superuser and had it confirmed by rootchecker. Where my phone got screwed is when i attempted to flash Android Revolution HD.
After flashing the ROM and pressing restart within TWRP recovery my phone went straight to the bootloader. Anything I did, from attempting to enter recovery or even power off the phone just sent me back to the bootloader.
I managed to re-flash TWRP and am able to access recovery BUT my entire phone is wiped (no backups ,roms, etc.) and my attempt to revert back to the original Sprint RUU has failed 3 times.
What I've noticed in the videos of people updating to the original Sprint RUU is that their image version for the current version is 1.2xxxx and is identical to the one they're updating to while mine is from: 1.31.651.2 to: 1.29.651.10.
Desperately in need of help as this phone is not even 2 weeks old.
Click to expand...
Click to collapse
If you can still access TWRP, load another ROM onto a USB drive and plug it into your phone with an adapter. Flash properly by doing a complete wipe with TWRP and do a boot. It could have been a bad download initially. Did you do a MD5 sum check? As for the RUU, I've never done one (As I've never required an RUU *Knock on wood*) but from what I've read and seen, you need to revert everything you've done as in relocking the bootloader and reverting S-OFF if you've done that.
Athrun88 said:
If you can still access TWRP, load another ROM onto a USB drive and plug it into your phone with an adapter. Flash properly by doing a complete wipe with TWRP and do a boot. It could have been a bad download initially. Did you do a MD5 sum check? As for the RUU, I've never done one (As I've never required an RUU *Knock on wood*) but from what I've read and seen, you need to revert everything you've done as in relocking the bootloader and reverting S-OFF if you've done that.
Click to expand...
Click to collapse
Didn't check the MD5 & when attempting to use the RUU I did have S-ON(Never had S-OFF) and had the bootloader locked. But is there a way for me to push a rom to the phone using adb? I've tried before but it always says device not found.
Also, whenever i try to use the RUU the error I get has to with an incorrect Hboot version. Currently my Hboot is 1.44.0000.
MrAdrianP said:
Didn't check the MD5 & when attempting to use the RUU I did have S-ON(Never had S-OFF) and had the bootloader locked. But is there a way for me to push a rom to the phone using adb? I've tried before but it always says device not found.
Also, whenever i try to use the RUU the error I get has to with an incorrect Hboot version. Currently my Hboot is 1.44.0000.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2318497
Try this
MrAdrianP said:
What I've noticed in the videos of people updating to the original Sprint RUU is that their image version for the current version is 1.2xxxx and is identical to the one they're updating to while mine is from: 1.31.651.2 to: 1.29.651.10.
Click to expand...
Click to collapse
If your are S-ON you cannot flash an RUU that is older than your current firmware that's why its not working, you either have to stay on the same firmware or upgrade but you cannot downgrade so what you have to do is sideload a ROM using the tutorial dgtiii provided and everything will be back to normal, don't worry
I have a Sprint HTC One. I previously unlocked the boot loader and installed clock work mod recovery. I achieved SU and partial Super CID. I tried flashing Viper ROM after relocking the boot loader, which failed. when I went to reboot the phone, I was in boot loader without a system ROM. so I installed the stock ROM and updated firmware. the phone now works. however, I lost su and my custom recovery. I tried to unlock the bootloader , reinstall Viper, but neither will work it fails every time. I am experienced at following instructions on this website, but I lack the knowledge to know exactly what I am doing with each action.
Please help me get either su, custom recovery or the boot loader unlocked. I still have S-off and I am at a loss. Thank you!
patrickgartner said:
I have a Sprint HTC One. I previously unlocked the boot loader and installed clock work mod recovery. I achieved SU and partial Super CID. I tried flashing Viper ROM after relocking the boot loader, which failed. when I went to reboot the phone, I was in boot loader without a system ROM. so I installed the stock ROM and updated firmware. the phone now works. however, I lost su and my custom recovery. I tried to unlock the bootloader , reinstall Viper, but neither will work it fails every time. I am experienced at following instructions on this website, but I lack the knowledge to know exactly what I am doing with each action.
Please help me get either su, custom recovery or the boot loader unlocked. I still have S-off and I am at a loss. Thank you!
Click to expand...
Click to collapse
... simply flash appropriate custom recovery from fastboot. boot into recovery and try to reboot from there and it will ask you if you want to root the device. root it. reboot normally and you will see SU app. open it and update binaries. thats it, you are rooted ...
Failure
Okay, so I appreciate the attention and help, but it fails to install recovery, flash roms, or unlock the bootloader from fastboot. I can flash firmware and run an RUU from my desktop. As well, I can run the Sprint OTA update from the phone, but I have not done that yet. I have hboot 1.55. I have tried to flash things from terminal emulator, but I'm having trouble. I can access and use the phone for Sprint, but the CID says 11111 and won't let me change carriers. Once again, I have S-off.
Thoughts:
Run Sprint update and try to start from scratch, if all else fails, sell it.
Can I flash SU from bootloader? I haven't tried that yet, although I doubt it will work given my other problems.
patrickgartner said:
Okay, so I appreciate the attention and help, but it fails to install recovery, flash roms, or unlock the bootloader from fastboot. I can flash firmware and run an RUU from my desktop. As well, I can run the Sprint OTA update from the phone, but I have not done that yet. I have hboot 1.55. I have tried to flash things from terminal emulator, but I'm having trouble. I can access and use the phone for Sprint, but the CID says 11111 and won't let me change carriers. Once again, I have S-off.
Thoughts:
Run Sprint update and try to start from scratch, if all else fails, sell it.
Can I flash SU from bootloader? I haven't tried that yet, although I doubt it will work given my other problems.
Click to expand...
Click to collapse
... slow down and calm down. i think you are hasting things. dont worry and do whatever you wanna do step by step. its not clear to me what you want to achieve, you wanna switch carriers ? want ota ? want custom rom ? you are s-off but cant flash recovery !!!! please explain exactly what you want and what errors are you getting and doing what
i think you cant have SU from bootloader and certainly terminal emulator doesnt flash recoveries and rom., fastboot does recovery and recovery flashes rom. dont play with your phone like this without proper knowledge. ask whatever doubts you have prior doing anything ...
Straight Talk
You're funny. Yes, I am in a hurry to use my new phone... Ultimately, I want to use it on straight talk. It is S-off, and the boot loader will not unlock, the phone won't flash a recovery and I have lost su. It's the weirdest thing! I haven't had this problem before. Usually you flash stock firmware and ruu and you're back at square one, but not this time.
I would pay you to visit my problem via Teamviewer? Interested?
-Patrick
patrickgartner said:
You're funny. Yes, I am in a hurry to use my new phone... Ultimately, I want to use it on straight talk. It is S-off, and the boot loader will not unlock, the phone won't flash a recovery and I have lost su. It's the weirdest thing! I haven't had this problem before. Usually you flash stock firmware and ruu and you're back at square one, but not this time.
I would pay you to visit my problem via Teamviewer? Interested?
-Patrick
Click to expand...
Click to collapse
... Dear if you wanna network unlock your phone, follow the steps exactly as described.
1. Flash this and only this RUU (first link - http://forum.xda-developers.com/showthread.php?t=2250904 ), no need to relock bootloader if unlocked as you are s-off.
2. Download the recovery for sprint variant and flash it in fastboot mode (fastboot flash recovery recovery.img) (link - http://forum.xda-developers.com/showthread.php?t=2651035).
3. Boot in to recovery and press reboot and then system, it will ask for your permission to root, root it. restart normally and open SU app and update its binaries. phone will reboot itself in recovery and back in normal mode. You will be rooted then. :victory:
then ping me for sim unlock ...
im not really sure what happened...
i was trying to root then s-off today. i got htcdev.com unlocked, was able to flash custom recovery (philz) and flash superuser. when i tried to s-off (firewater) i got the whelp this sucks error (im still not really sure why or what that means)
i tried to then flash a custom rom, and now it wont boot past the htc flash screen with the red text ( this may be because i didnt flash firmware with the rom i tried to install?)
i have tried to flash firmware, and run a ruu and nothing is doing anything...
please please please someone help
What firmware version do you currently have installed? What ROM were you trying to flash?
Take a look at this thread below for info on how to flash the latest RUU. If you have a HK version you'll need the HK RUU. After you run the RUU you'll need to reroot your phone. You'll also need to use the SunShine exploit to gain S-off (the "whelp" message means Firewater won't work on your device). I also recommend Captain Throwback's TWRP 2.8.0.0. recovery.
http://forum.xda-developers.com/showthread.php?t=2880328
im not sure which of these are the firmware...
hboot - 3.16.0.0000
radio - 1.05.20.0321_2
os - 1.54.654.9
Firmware is your radio version. Use the RUU from the link below. Follow the instructions for the manual system update. You'll need to relock your bootloader beforehand using the command "fastboot oem lock" while connected via Fastboot USB mode.
http://www.htc.com/us/support/htc-one-m8-harman-kardon-edition-sprint/news/
ohh i forgot about having to relock for ruu
trying that now
I downloaded the ruu, but when I run it it can't find my phone... I think it wants me to be booted into the ROM but I can't boot the only thing I can access is the bootloader
knock.back said:
I downloaded the ruu, but when I run it it can't find my phone... I think it wants me to be booted into the ROM but I can't boot the only thing I can access is the bootloader
Click to expand...
Click to collapse
RUU's are run from the bootloader...make sure it says fastbootusb when connected to your PC.
it did say that
Make sure you have HTC Sync installed on your computer.
I have that installed too... I got it to boot, ended up flashing different recovery then a different rom and that worked... Never got the ruu to work tho... Anyway, thanks for your help