Develop Bugs

corrupt bootloader s-off

hi
i just downgraded my desire hd and then did a radio s-off but then i wanted to do a S-OFF.
i used the easyS-off but then it said bootloader corrupt do not reboot.
i already tried without "I Have Radio S-OFF" then it just says connection problem
i have charged only and debugging turned on
what now?
thnx

hmm what about Easy Radio Tools?

i used that for radio s-off

it worked now!! thnx to this guy
http://forum.xda-developers.com/showthread.php?t=999219
second post!!

I would be hesitamt to reboot though, haven't used the easytool as I personally prefer to know what steps are being carried out, but if it warns that the bootloader is corrupt I wouldn't reboot until I knew the situation is corrected.

Hello guys (I suppose most of the visitors are in fact guys ),
I downgraded my DHD to 1.32 this week and managed to get root-access and did a successful Radio S-OFF using the One click Radio S-OFF.
However; this morning I tried the One click ENG S-OFF but the first time I tried to run the tool I got an error stating "Connection error (SD)". Rebooted my phone and tried again.
This time I got the error "Bootloader corrupt, contact XDA".
After I almost crapped myself I started to search for a solution; someone on this forum stated to go to application settings - superuser - and clear data. Did it and then I got a bunch of applications which did a forced close.
Tried the One click tool again and got the same error (Bootloader corrupt).
In the meanwhile I got all this popups regarding android.process.acore needed to close which finally resulted in an unusable phone so I rebooted...
Thank god this went alright and my phone is up and running again but...
I think the last failure was probably caused by the One click app that doesn't have root access (didn' t get a popup though), but I'm a little afraid to try it again.
Does anyone know if it's save to try it again?

enz0123 said:
Does anyone know if it's save to try it again?
Click to expand...
Click to collapse
Why not do it longhand? Concise instructions are available here, I realise you already have root but even if you follow the instructions from the begining they aren't gonna do any harm.

Thanks, that could be a solution however I found out that I didn't check the box "I have Radio S-OFF
Tried again with the checkbox checked but got the same error again.
The files that were copied to my SD-card at the first attempt are still there.
Is it safe to remove these files?
Maybe that solves it...

It is very important, that you agree the super user request while the tool does its job.
I had the same problems some weeks ago (bootloader corrupt), because during the flash my display timeout was reached and the super user request failed (black locked screen).
If the tool can not get root, it can not copy the bootloader. The message "bootloader is corrupt" is confusing, because nothing has happend.

KaseDesire said:
If the tool can not get root, it can not copy the bootloader. The message "bootloader is corrupt" is confusing, because nothing has happend.
Click to expand...
Click to collapse
Which is one reason I favour doing it long hand at least then youd know it's failed to flash the bootloader

Hmm, strange.
When I boot into the bootmenu (vol. down + power) it states the I'm already ENG s-OFF and hav CID 111111...
Something must have gone right....
However I can't find the line anymore that states that I have Radio S-OFF, is this normal behaviour?

KaseDesire said:
It is very important, that you agree the super user request while the tool does its job.
Click to expand...
Click to collapse
Exactly! The instructions don't mention it, but when you run the easy s-off exe, it goes through a few steps and then your phone will ask you to allow superuser access. So have your screen on and be ready, and THEN run the easy s-off utility. That's all it was for me. I hit "OK" on the error message, tried it again but this time watched my phone and allowed SU access, and it worked fine.

Hi,
I'm posting here because i had the same problem ( Bootloader corrupt etc ... ).
First I rooted my DHD, and made it Eng s-off and installed a rom a few month ago.
Today I wanted to install another rom, and flash the radio.
But I did not remenbered if I already had the radio s-off, so i installed the 1.32 stokified rom, used the easy radio tool ( v2.2 ) and when i wanted to use the easy s-off tool ( v05 ), the program gave me the error message concerning the bootloader corrupt and stuff. I tried it with "I have radio s-off" ticked, and when I try it with unticked, I have a connection error message.
I tried to delete the data from SU, but it didn't help, and then I noticied ( remenbered ) that SU did not asked me the authorizations when I used easy radio tool ans easy s-off.
Anyone have an idea how I can fix that ? Maybe unistall/reinstall SU ?

HTC Desire HD radio S-OFF steps
http://www.youtube.com/watch?v=dTFphGbgqbQ&feature=player_embedded

Yes I did that after reinstalling the 1.32 rom, excepted the Visionary steps.
The root is permanent no ? I did it on my previous rom, so I don't have to root it again when I install another rom ?
Anyway, my DHD rebooted when I tried to secure the battery compartment, the bootloader wasn't corrupted, it's fine.
So I checked the bootload, I have ENG s-off and Cid 1111... this mean that my device is radio s-off too right ?

HornAdama said:
I have ENG s-off and Cid 1111... this mean that my device is radio s-off too right ?
Click to expand...
Click to collapse
Yes, you can install custom roms and flash radios now.

[Q] still "s-on" after using the aahk kit => what can I do?

Hello
I tried to root my desire hd by using the aahk kit. I strictly followed the efffen manual, but somehow the bootloader still states that the device is in "s-on" mode. I can install custom roms, but I only get the screen showing the htc logo when rebooting the device. I can only access the bootloader and the recovery mode. (the connection to my computer works)
I already tried:
to unlock the bootloader with the help of htcdev.com (=> worked)
to apply the aah Kit a second time => does not work (I get the message that no device is found. Alternatively I can start the hack while the device is switched off. This way the device is found, but the hack doesn't succeed.
Is there anything else I can try? I hope somebody has an advice.

Steph.xda said:
Hello
I tried to root my desire hd by using the aahk kit. I strictly followed the efffen manual, but somehow the bootloader still states that the device is in "s-on" mode. I can install custom roms, but I only get the screen showing the htc logo when rebooting the device. I can only access the bootloader and the recovery mode. (the connection to my computer works)
I already tried:
to unlock the bootloader with the help of htcdev.com (=> worked)
to apply the aah Kit a second time => does not work (I get the message that no device is found. Alternatively I can start the hack while the device is switched off. This way the device is found, but the hack doesn't succeed.
Is there anything else I can try? I hope somebody has an advice.
Click to expand...
Click to collapse
You can't use AAHK on an unlocked bootloader. Relock it and try AAHK again if you want S-OFF. If you are okay with S-ON, you need to flash the boot.img each time you flash a ROM. Otherwise, your phone will hang on the HTC screen like yours is right now.
You might have used AAHK to downgrade the first time, which would be why you were still S-ON. If your phone is on 2.3.5, AAHK needs to be run twice: once to downgrade, once to root.

bananagranola said:
You can't use AAHK on an unlocked bootloader. Relock it and try AAHK again if you want S-OFF. If you are okay with S-ON, you need to flash the boot.img each time you flash a ROM. Otherwise, your phone will hang on the HTC screen like yours is right now.
You might have used AAHK to downgrade the first time, which would be why you were still S-ON. If your phone is on 2.3.5, AAHK needs to be run twice: once to downgrade, once to root.
Click to expand...
Click to collapse
Thanks for your quick reply! I successfully relocked the bootloader. However, as you may see in the screen shot the AAHK doesn't work properly.
Anyway, I do not necessary need S-Off. Where can I find information about how th flash the boot.img? (Is the boot.img extracted from the stock RUU suitable?) What's the best way to continue? Flashing the boot.img and installing a custom rom directly afterwards?
in addition:
I tried to use a different sd-card => same error.
As suggested I flashed the boot.img. It worked but I still can't use custom ROMs. What do I do wrong???
== >> Got it If anyone else has a similar problem: http://forum.xda-developers.com/showpost.php?p=31211732&postcount=396

Steph.xda said:
Thanks for your quick reply! I successfully relocked the bootloader. However, as you may see in the screen shot the AAHK doesn't work properly.
Anyway, I do not necessary need S-Off. Where can I find information about how th flash the boot.img? (Is the boot.img extracted from the stock RUU suitable?) What's the best way to continue? Flashing the boot.img and installing a custom rom directly afterwards?
Click to expand...
Click to collapse
For AAHK: I think your sdcard may be corrupted for use as a goldcard, which can happen when it's improperly dismounted; though you can access data, you can't use it for AAHK. Get a brand-new one and try it.
For boot.img when S-ON: look in post #7's PDF in the Ace Think Tank thread linked in my signature. Instructions are in there someplace, but I can't remember the page number off the top of my head. You will need to flash the ROM, then fastboot flash the boot.img, each time.

Steph.xda said:
Thanks for your quick reply! I successfully relocked the bootloader. However, as you may see in the screen shot the AAHK doesn't work properly.
Anyway, I do not necessary need S-Off. Where can I find information about how th flash the boot.img? (Is the boot.img extracted from the stock RUU suitable?) What's the best way to continue? Flashing the boot.img and installing a custom rom directly afterwards?
in addition:
I tried to use a different sd-card => same error.
As suggested I flashed the boot.img. It worked but I still can't use custom ROMs. What do I do wrong???
== >> Got it If anyone else has a similar problem: http://forum.xda-developers.com/showpost.php?p=31211732&postcount=396
Click to expand...
Click to collapse
That seems to be a connectivity issue. Have you installed the drivers with the phone unplugged?

[Q] desire hd not booting after unlocking bootloader

Hi all,
I have spent the last week trying to solve my problem. Basically I tried to unlock the bootloader on my HTC desire HD using the instructions supplied by HTCDEV. Something happened during the unlocking process and now I have an unlocked bootloader and a phone that doesnt boot. The unlocking process didnt go through as I didnt get to the part where I have to work with the token. However, if I boot into bootloader, it shows that it is unlocked and s-on. I can get to the fastboot menu and the phone only boots to the HTC screen.
I have followed the instructions from the many posts in this forum without any luck. I cant seem to be able to flash anything through fastboot. I keep getting errors such signature failed error 132 and error 131. I cant access recovery. It gives out errors whenever i try to access it. ADB doesnt work. The device doesnt get picked up in windows. I tried flashing recovery without any luck. The CID is HTC_612. The firmware version is 1.31.405.6.
I tried to use an RUU but I always get the error that the RUU that i am using is not the one for my rom or that the signature verification is wrong.
Any advice?
Thanks

Galam said:
Hi all,
I have spent the last week trying to solve my problem. Basically I tried to unlock the bootloader on my HTC desire HD using the instructions supplied by HTCDEV. Something happened during the unlocking process and now I have an unlocked bootloader and a phone that doesnt boot. The unlocking process didnt go through as I didnt get to the part where I have to work with the token. However, if I boot into bootloader, it shows that it is unlocked and s-on. I can get to the fastboot menu and the phone only boots to the HTC screen.
I have followed the instructions from the many posts in this forum without any luck. I cant seem to be able to flash anything through fastboot. I keep getting errors such signature failed error 132 and error 131. I cant access recovery. It gives out errors whenever i try to access it. ADB doesnt work. The device doesnt get picked up in windows. I tried flashing recovery without any luck. The CID is HTC_612. The firmware version is 1.31.405.6.
I tried to use an RUU but I always get the error that the RUU that i am using is not the one for my rom or that the signature verification is wrong.
Any advice?
Thanks
Click to expand...
Click to collapse
Damn. If you had S-OFF you could have flashed a recovery and it would have been easier for you. Post in the thread linked in my signature (Ace Think Tank) and you'll hopefully get some help from someone (most likely Glevitan)

Galam said:
Hi all,
I have spent the last week trying to solve my problem. Basically I tried to unlock the bootloader on my HTC desire HD using the instructions supplied by HTCDEV. Something happened during the unlocking process and now I have an unlocked bootloader and a phone that doesnt boot. The unlocking process didnt go through as I didnt get to the part where I have to work with the token. However, if I boot into bootloader, it shows that it is unlocked and s-on. I can get to the fastboot menu and the phone only boots to the HTC screen.
I have followed the instructions from the many posts in this forum without any luck. I cant seem to be able to flash anything through fastboot. I keep getting errors such signature failed error 132 and error 131. I cant access recovery. It gives out errors whenever i try to access it. ADB doesnt work. The device doesnt get picked up in windows. I tried flashing recovery without any luck. The CID is HTC_612. The firmware version is 1.31.405.6.
I tried to use an RUU but I always get the error that the RUU that i am using is not the one for my rom or that the signature verification is wrong.
Any advice?
Thanks
Click to expand...
Click to collapse
thanks GuyInTheCorner I have posted the question is the thread as required.

[q] help. How to run ruu on verizon to get back to stock

Hey, i'm new to this forum but i have tried everything and cant figure it out. Its probably just me because i'm not too good with this stuff.I bought this phone used and it was rooted when i got it. im pretty sure i unrooted it but somewhere along the way while trying to get it back to stock i reset the phone and it must have deleted something important because when i try to download the OTA update it simply wont install after i download it. Recovery used to work but now it just sits at the loading screen and then reboots the phone. I managed to re-lock the bootloader and it is on S-off. I tried to get back to stock using the ruu.exe but the video i was following had the link for every ruu except verizon. Figures. Then i searched around and cant seem to find a verizon Ruu.exe file. Please any help would be appreciated i just want to be able to update to the latest firmware.

Follow the steps carefully
http://forum.xda-developers.com/showthread.php?t=2588979 -------------adb setup best tried my self
http://forum.xda-developers.com/showthread.php?t=2765784 ----------- RUU/VZW/KitKat4.4.2/Sense 6/S-OFF only!
http://forum.xda-developers.com/showthread.php?p=46342232 ------ [how to] remove your "tampered" banner
http://forum.xda-developers.com/showthread.php?p=46301380#post46301380 -------- to unlock bootloader
This will help you as in my case i also had the same problem . unlock your bootloader and you must be soff this ruu works fine just follow the steps. First install the htc sync manager to your pc and then uninstall it ( only sync manager ) not the drivers.
:good::good::good::good::good: good luck

Still having problems.
When i get up to the step when you need to type SU into the command promp is where i am getting stuck. My supersu app says "there is no binary file installed" when i try and open it and my phone will not allow me to uninstall the application so im not sure if that is causing the problem

Clean install the super su
ctb3892 said:
When i get up to the step when you need to type SU into the command promp is where i am getting stuck. My supersu app says "there is no binary file installed" when i try and open it and my phone will not allow me to uninstall the application so im not sure if that is causing the problem
Click to expand...
Click to collapse
Dude first specify what is your software number ? I would recommend you to clean your super su install if thats the problem you are facing also do mention the it with a screenshot...so that if some knows can help you
Also i think you are using it to remove the tampered tag right? you can do that later . also no need to unlock bootloader if you have soff

I attached some screenshots hopefully they help. I think I've come to the conclusion I need to flash a recovery but in order to do so my boatloader must be unlocked even if I have s-off. (It says relocked and s-off) only problem is that I can't find a way to unlock the boot loader b/c htcdev doesn't allow Verizon to unlock through there services and the other ways require supersu. The only way to get the correct binary file for super su is to flash it which I can't do without recovery. So I feel like I'm jus stuck right now and can't do anything
Sent from my HTC6500LVW using XDA Free mobile app

Bro Your bootloader is locked you should not have relocked it dude thats the biggest mistake ! and your software number shows that you are running kitkat there is no rooting method till now for that .
What i must say is that you can try to flash the ruu without unlocking the bootloader you are s-off give it a try , if it does then your problem is solved
unlock your bootloader later on. Wish you luck :good:. Also you can ask in the forum itself that will it flash or not
http://forum.xda-developers.com/showthread.php?t=2765784

leech28 said:
Bro Your bootloader is locked you should not have relocked it dude thats the biggest mistake ! and your software number shows that you are running kitkat there is no rooting method till now for that .
What i must say is that you can try to flash the ruu without unlocking the bootloader you are s-off give it a try , if it does then your problem is solved
unlock your bootloader later on. Wish you luck :good:. Also you can ask in the forum itself that will it flash or not
http://forum.xda-developers.com/showthread.php?t=2765784
Click to expand...
Click to collapse
That worked thanks a lot bro apreciate it I was stuck for weeks
Sent from my HTC6500LVW using XDA Free mobile app

leech28 said:
Bro Your bootloader is locked you should not have relocked it dude thats the biggest mistake ! and your software number shows that you are running kitkat there is no rooting method till now for that .
What i must say is that you can try to flash the ruu without unlocking the bootloader you are s-off give it a try , if it does then your problem is solved
unlock your bootloader later on. Wish you luck :good:. Also you can ask in the forum itself that will it flash or not
http://forum.xda-developers.com/showthread.php?t=2765784
Click to expand...
Click to collapse
S off means no need to lock for ruu [emoji1]
ctb3892 said:
That worked thanks a lot bro apreciate it I was stuck for weeks
Sent from my HTC6500LVW using XDA Free mobile app
Click to expand...
Click to collapse

Finally upgrading to Nougat... running into some odd problems.

I simply want to upgrade to 7. I had put it off before the holidays, and now I finally can sit down and do this.
First, I have a SIM-unlocked US HTC 10, on build 1.96.617.2. I am currently S-off, with a locked bootloader, rooted, etc.
The first thing that perplexed me was that I couldn't boot into bootloader (or anything) from ADB. It just rebooted to the OS. I thought maybe I needed to quickly flash the old TWRP (for MM), but then I recalled I had locked my bootloader when I did S-off 5 months ago.
So my first question... is there a way to unlock bootloader without going through all the brain damage through HTC? WIth the HTC One (M8), someone had figured out you could get an ADB shell, get su, then enter:
Code:
echo -ne "HTCU" | dd of=/dev/block/mmcblk0p2 bs=1 seek=33796
I would never presume that this would work on the 10 as the partitions are likely different..
SO my first question is whether anyone knows if there is a simple way to unlock the bootloader without going through HTC and getting the token, etc.?
Secondly, I think to avoid all possible problems, I am just going to back up internal storage and run the RUU 2.28.617.8 (exe) to upgrade (will flash custom roms after this). Since I am S-off, I know that after I upgrade, I can just flash the new TWRP (3.03 Unoffficial) that Captain Throwback, nkk71 and others worked very hard to create. However, what I am completely new and unfamiliar with is attaining root...
I know it will sound strange, but I have no idea what Magisk is (well I understand what it does roughly), but from some threads I have read that only a systemless root is attainable, and other places I have seen that dm_verity needs to be disabled in the kernel ramdisk. I have only used SuperSu since 2011, and I feel a bit befuddled. I thought Chainfire created a new SuperSu for that disabled dm_verity... However, I see that some do not use SuperSu... Can someone give me some advice on the differences (if there are any) between using Magisk (and phh?) or SuperSu to manage root?
Thank you very much in advance!!!
Syntropic
EDIT: Addendum question... I am on TMO. Would it be wiser to flash the recent TMO nougat RUU on my Sim-Unlocked HTC 10??
[Note: I asked this question a few weeks ago...but as I couldn't upgrade before the holidays, I wanted to ask again just to be sure.]

OK... I need some help. please.
Well.... I unlocked the bootloader with my old unlock_code.bin which was obviously stupid because I didn't realize that I needed a locked bootloader to run the RUU. I cannot lock the RUU because I don't know the encryption password.... (I know my screen pattern but that is it).
Just to confirm, I started to run the RUU, but it is prompting me with ERROR[170] USB Connection ERROR. But the USB connection was working fine 10 minutes ago. I am therefore assuming this is because my bootloader is now unlocked. Howver I do not know how to relock the bootloader from TWRP. But it seems odd because I am s-off...so can someone confirm that this is actually what the problem is??
I opted to upgrade using the RUU.exe because I thought it would cause the least amount of potential problems—PLUS I figured that since I was sacrificing all my data anyway, why would I need to know passwords for encryption???
Can someone assist me? I am a bit over my head... However, I have both RUU exe and zip files, and have decrypted them to get firmware and boot images.
Further, if someone does respond to this, I would also really appreciate what I need to do after flashing the new TWRP... I thought this would really be my only question... (see first post), but I seemed to have forgotten everything about rooting this phone the first time.
Again, I would really appreciate instructions on how to solve this problem... I have everything backed up... So I just want to run this RUU (and then root it after I flash TWRP).
Thank you in advance!!!!!!
Thank you

syntropic said:
OK... I need some help. please.
Well.... I unlocked the bootloader with my old unlock_code.bin which was obviously stupid because I didn't realize that I needed a locked bootloader to run the RUU. I cannot lock the RUU because I don't know the encryption password.... (I know my screen pattern but that is it).
Just to confirm, I started to run the RUU, but it is prompting me with ERROR[170] USB Connection ERROR. But the USB connection was working fine 10 minutes ago. I am therefore assuming this is because my bootloader is now unlocked. Howver I do not know how to relock the bootloader from TWRP. But it seems odd because I am s-off...so can someone confirm that this is actually what the problem is??
I opted to upgrade using the RUU.exe because I thought it would cause the least amount of potential problems—PLUS I figured that since I was sacrificing all my data anyway, why would I need to know passwords for encryption???
Can someone assist me? I am a bit over my head... However, I have both RUU exe and zip files, and have decrypted them to get firmware and boot images.
Further, if someone does respond to this, I would also really appreciate what I need to do after flashing the new TWRP... I thought this would really be my only question... (see first post), but I seemed to have forgotten everything about rooting this phone the first time.
Again, I would really appreciate instructions on how to solve this problem... I have everything backed up... So I just want to run this RUU (and then root it after I flash TWRP).
Thank you in advance!!!!!!
Thank you
Click to expand...
Click to collapse
I'm not really sure what went wrong in your sequence of events but since you're s-off I think you should be able to flash that ruu.
In either case have you tried running an ruu zip from your sd card instead of using the ruu.exe?

You're s-off? But you have a locked bootloader? I've never heard of that being possible. On your DM screen it says s-off and it says locked? I've heard of people bricking their pixels by unlocking the bootloader, locking it and trying too unlock again.

GutterParrot said:
You're s-off? But you have a locked bootloader? I've never heard of that being possible. On your DM screen it says s-off and it says locked? I've heard of people bricking their pixels by unlocking the bootloader, locking it and trying too unlock again.
Click to expand...
Click to collapse
It's a sunshine feature.
After successful s-off it sets bootloader back to locked. It's easier to go back to stock.
I don't understand why to tried to unlock your HTC 10? With s-off it doesn't matter if the bootloader is locked or unlocked.
Maybe you should try the RUU.zip variant. After that flash TWRP and SuperSu.
Sent from my HTC 10 using XDA Labs