!!!HTC Amaze bootloader locked!!! - HTC Amaze 4G

I am very sad at this point, one I was happy at the beginning when I followed Hasoons2000 root toolkit to root my HTC amaze, the steps were easy to follow UNtil , I started to poke into an area I wasnt familiar with, the S-Off /ON and when I ran the exploit for Hasoon S-off, trouble began. My phone was up and running, it installled supersu, everything was fine, Now I cant even get the phone to turn on. I read some threads saying I need to download and install new rom, or stock rom, . ..Im ok with that part, However I read another thread saying I needed to relock the phone. And things became worst. Now its on Relocked, S-On, tried to root , was successful, now all I see is the bootloader screen with no OS, no img, its tough at this point. But I am sure someone out there can help me rebuild and start over again. Help me please!

---

Need @ravike14 he'll help you out!
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app

---

Put the ruu file in the ext sd and flash it thru bootloader your amaze will be up and running and unlock bootloader again before doing this with new unlock code from htc dev
If you need an even detailed process post again and you should at least search once this is not an uncommon problem and watch a video before doing s-off
Sent from my HTC_Amaze_4G using Tapatalk

---

http://forum.xda-developers.com/showthread.php?t=2437057
[TOOL] [10.15.13] WinDroid HTC Amaze 4G Toolkit v2.1 | Unlock | Root | Flash | S-OFF
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
---------- Post added at 03:35 PM ---------- Previous post was at 03:35 PM ----------
You don't need a new unlock code if you kept the bin file.
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
---------- Post added at 03:36 PM ---------- Previous post was at 03:35 PM ----------
Tool kit is more up to date
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app

---

old bin file
chevycowboyusa said:
http://forum.xda-developers.com/showthread.php?t=2437057
[TOOL] [10.15.13] WinDroid HTC Amaze 4G Toolkit v2.1 | Unlock | Root | Flash | S-OFF
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
---------- Post added at 03:35 PM ---------- Previous post was at 03:35 PM ----------
You don't need a new unlock code if you kept the bin file.
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
---------- Post added at 03:36 PM ---------- Previous post was at 03:35 PM ----------
Tool kit is more up to date
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
i heard if you have relocked your boot loader you coudnt unlock it by the old unlock code.

---

Old bin
Muneeb Saeed said:
i heard if you have relocked your boot loader you coudnt unlock it by the old unlock code.
Click to expand...
Click to collapse
I just did it...
I messed up and forgot to change the partition to flash the system to and had to go back to an ruu
I still had the bin file.
I flashed the ruu
then I used the windroid toolkit and did the unlock bootloader and used the old bin file.
then i pushed the recovery image and then flashed viper again and
back to normal!

---

chevycowboyusa said:
I just did it...
I messed up and forgot to change the partition to flash the system to and had to go back to an ruu
I still had the bin file.
I flashed the ruu
then I used the windroid toolkit and did the unlock bootloader and used the old bin file.
then i pushed the recovery image and then flashed viper again and
back to normal!
Click to expand...
Click to collapse
+1
It happened to me at one point when I ported sense 4.1, I had to relock, flash the ruu, and unlock the bootloader again. Then I simply used the perm root zip, flashed a recovery, one of my roms, done.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

---

Although I'm s-on, I too have had to reflash back to stock after monkeying around with some tweaks meant for other HTC devices. Long story short, the partition schemes vary between devices and I hosed something important, causing a bootloop. I was easily able to relock my bootloader, flash factory ruu, then unlock again using the same blob from HTC dev. Keep the unlock blob somewhere safe and handy. You never know when it might be needed again.

---

If you accidentally flash to block 17 or 18 you'll need a jtag! Most others are recoverable.
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app

---

chevycowboyusa said:
If you accidentally flash to block 17 or 18 you'll need a jtag! Most others are recoverable.
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the heads up Chevy. Thank goodness it was block 22 not the ones you mentioned. Actually, I was trying to flash the leedroid tweaks, but from the EVO 3d GSM, not the sensation, over the bone stock latest ruu. I had just deodexed the ROM in the kitchen and was trying to see how I could modify it on the handset.. Obviously I know now that they aren't as compatible as I was hoping. LOL
How did you guys port those tweaks? When I tried using the leedroid zip from the sensation in the kitchen it would boot, but never make it to the lock screen. Same when I tried the Dark Forrest tweaks. After those failures, I'm thinking about trying out exposed instead. Maybe I'll have better luck.

---

Odysseus1962 said:
Thanks for the heads up Chevy. Thank goodness it was block 22 not the ones you mentioned. Actually, I was trying to flash the leedroid tweaks, but from the EVO 3d GSM, not the sensation, over the bone stock latest ruu. I had just deodexed the ROM in the kitchen and was trying to see how I could modify it on the handset.. Obviously I know now that they aren't as compatible as I was hoping. LOL
How did you guys port those tweaks? When I tried using the leedroid zip from the sensation in the kitchen it would boot, but never make it to the lock screen. Same when I tried the Dark Forrest tweaks. After those failures, I'm thinking about trying out exposed instead. Maybe I'll have better luck.
Click to expand...
Click to collapse
Eek! Block 22 is scary too. That's the boot partition!
29 30 & 31 are our main partitions.
29 is system
30 is cache
31 is data
22 boot image
The venom tweaks were already in viper as it was ported from sensation.
There may be some smali editing. Afnan could guide you better on the tweaks than I could.
I've really just recently got into the deeper editing of the Roms.
I've been losing hair and brain cells working with ravike14 on the two Roms and the kernel.
There will be more of a stock 4.5 jellybean and a stock sense 5. We will turn these loose on the forum and let others go in depth for tweaking. It's been damn hard enough just trying to get sensors and stuff working.
Can't post the Roms in any part until he can upload his kernel source.
Chevy.
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app

---

chevycowboyusa said:
Eek! Block 22 is scary too. That's the boot partition!
29 30 & 31 are our main partitions.
29 is system
30 is cache
31 is data
22 boot image
The venom tweaks were already in viper as it was ported from sensation.
There may be some smali editing. Afnan could guide you better on the tweaks than I could.
I've really just recently got into the deeper editing of the Roms.
I've been losing hair and brain cells working with ravike14 on the two Roms and the kernel.
There will be more of a stock 4.5 jellybean and a stock sense 5. We will turn these loose on the forum and let others go in depth for tweaking. It's been damn hard enough just trying to get sensors and stuff working.
Can't post the Roms in any part until he can upload his kernel source.
Chevy.
Sent from my HTC_Amaze_4G using XDA Premium 4 mobile app
Click to expand...
Click to collapse
That explains why I didn't hose my handset. The boot partition is pretty small and the kernel image read only on my s-on device. So probably only a few bits of data got squeezed into there causing no harm. Since then I've flashed back the latest stock kernel and libs, so I got lucky and escaped.