Anyone notice the MT4GS Bootloader Unlockable? - T-Mobile myTouch 4G Slide

http://htcdev.com/bootloader/
Not looked to see if it is the current ROM released recently...since just came available I would hope so....hopefully this is good news for folks....

I tried it and it didnt work on my phone at all. I got all the way up to the point where it tells you to use fastboot to upload the unlock_code.bin file and it tells you that you should see a screen that asks if you want to unlock the bootloader or not and nothing showed up for me at all. It was still at the fastboot/bootloader screen.

nice find, it'll make for a nice xmas gift for people with the latest ota

doost650 said:
I tried it and it didnt work on my phone at all. I got all the way up to the point where it tells you to use fastboot to upload the unlock_code.bin file and it tells you that you should see a screen that asks if you want to unlock the bootloader or not and nothing showed up for me at all. It was still at the fastboot/bootloader screen.
Click to expand...
Click to collapse
did you have S-ON or S-OFF at the time?

jaronm said:
did you have S-ON or S-OFF at the time?
Click to expand...
Click to collapse
And are you using the latest update or the previous stock ROM?...

beezie916 said:
http://htcdev.com/bootloader/
Not looked to see if it is the current ROM released recently...since just came available I would hope so....hopefully this is good news for folks....
Click to expand...
Click to collapse
Yeah I noticed earlier
http://phandroid.com/2011/12/26/htc...-4g-slide-now-officially-unlockable-from-htc/

jaronm said:
did you have S-ON or S-OFF at the time?
Click to expand...
Click to collapse
beezie916 said:
And are you using the latest update or the previous stock ROM?...
Click to expand...
Click to collapse
I was using my 2nd MT4GS which I had done nothing with since I got that one. It is fresh from the box and had the new OTA update on it (I updated it myself like an hour before I tried this). I no better then to use the MT4GS that I currently use as my everyday device which does have S-Off.

And now HTC knows which phones to not honor warranty claims from.
Sent via smoke signal.

doost650 said:
I tried it and it didnt work on my phone at all. I got all the way up to the point where it tells you to use fastboot to upload the unlock_code.bin file and it tells you that you should see a screen that asks if you want to unlock the bootloader or not and nothing showed up for me at all. It was still at the fastboot/bootloader screen.
Click to expand...
Click to collapse
Same thing... I got my unlock_code.bin file, flashed it, and didn't get the "are you sure" screen.
There doesn't seem to be any way to contact HTC about this either..?

jonnycat26 said:
Same thing... I got my unlock_code.bin file, flashed it, and didn't get the "are you sure" screen.
There doesn't seem to be any way to contact HTC about this either..?
Click to expand...
Click to collapse
Can you confirm your current bootloader version?
Sent from my NRGZ'D Sensation 4G!

jaronm said:
did you have S-ON or S-OFF at the time?
Click to expand...
Click to collapse
i am getting the same result, the unlock screen does not show up on the phone. i am on the new locked HBOOT, but i have S-OFF from before....

akapaul26 said:
can you confirm your current bootloader version?
Sent from my nrgz'd sensation 4g!
Click to expand...
Click to collapse
hboot 1-45.0013

doost650 said:
I tried it and it didnt work on my phone at all. I got all the way up to the point where it tells you to use fastboot to upload the unlock_code.bin file and it tells you that you should see a screen that asks if you want to unlock the bootloader or not and nothing showed up for me at all. It was still at the fastboot/bootloader screen.
Click to expand...
Click to collapse
I am having same results with hboot 1-45.0013 S-on stock. Hopefully revolutionary gets a hold of this soon!

akapaul26 said:
I am having same results with hboot 1-45.0013 S-on stock.
Click to expand...
Click to collapse
This is very weird.
That's the hboot included in the latest OTA update, which this tool claims to support. I'd hate to think HTC made a mistake in listing our phone....

jonnycat26 said:
This is very weird.
That's the hboot included in the latest OTA update, which this tool claims to support. I'd hate to think HTC made a mistake in listing our phone....
Click to expand...
Click to collapse
I know, but everything works till that point?......

akapaul26 said:
I know, but everything works till that point?......
Click to expand...
Click to collapse
I'm not sure, but I think the tool would work on any HTC phone, but the token would only be accepted if the HBOOT on the phone worked with it.
Just a guess tho...

perhaps there is a glitch that they didn't catch before announcing support for our new HBOOT? a glitch that hopefully they will fix soon...

yogi2010 said:
perhaps there is a glitch that they didn't catch before announcing support for our new HBOOT? a glitch that hopefully they will fix soon...
Click to expand...
Click to collapse
I've sent an email to the support link that's listed in the email with the unlock file. Or at least, I think I have, they don't actually confirm that you've sent a message when you hit send.
If I get any response from them, I'll share it here.

My experience with the new OTA
I flashed the t-mobile signed stock rom PP59IMG.zip through the bootloader then proceeded to download the OTA's. After that I placed the new recovery image in the appropriate place and rebooted bootloader to prepare pushing the recovery through fastboot. What I noticed is that even after installing the OTA in a unrooted totally stock rom, S-off remains, however where "revolutionary" once was written now displays "**Locked**" , so apparently HTC has managed to relock the bootloader even though it shows S-off. It's not totally locked, as I had to reflash the PP59IMG.zip to downgrade hboot again so that I could reuse the revolutionary tool to flash the 4.0.0.8 recovery, then install CWM to update the recovery. As long as "Locked" was sitting where "revolutionary" normally is, I found it impossible to use fastboot, so my guess is security remains off but fastboot is locked. Just my guess anyway.

Jaytex24 said:
I flashed the t-mobile signed stock rom PP59IMG.zip through the bootloader then proceeded to download the OTA's. After that I placed the new recovery image in the appropriate place and rebooted bootloader to prepare pushing the recovery through fastboot. What I noticed is that even after installing the OTA in a unrooted totally stock rom, S-off remains, however where "revolutionary" once was written now displays "**Locked**" , so apparently HTC has managed to relock the bootloader even though it shows S-off. It's not totally locked, as I had to reflash the PP59IMG.zip to downgrade hboot again so that I could reuse the revolutionary tool to flash the 4.0.0.8 recovery, then install CWM to update the recovery. As long as "Locked" was sitting where "revolutionary" normally is, I found it impossible to use fastboot, so my guess is security remains off but fastboot is locked. Just my guess anyway.
Click to expand...
Click to collapse
If Revolutionary worked the way it was supposed to, it wouldn't be locked.

Related

Help MTS4G hboot 1.45.0013

I need help how to root my MTS4g with hboot 1.45.0013 i tried several methods, and i couldnt do it!! help please!!
llager said:
I need help how to root my MTS4g with hboot 1.45.0013 i tried several methods, and i couldnt do it!! help please!!
Click to expand...
Click to collapse
You'll need to wait for HTC to fix their unlock tool, which according to them should be any day now, and then use that. Once you're unlocked, you can flash superuser.
anybody know if this is possible yet?
Some people have been able to use the HTC unlock tool, most people it doesn't work for.
At the moment, that's really all there is...
Sent from my Bulletproof_Doubleshot using xda premium
b1ackhawk said:
anybody know if this is possible yet?
Click to expand...
Click to collapse
Those of us on HBOOT 1.44.0013 are still waiting on an unlock method since HTC's boot unlocker is still borked and people are still trying to figure out a way to downflash to HBOOT 1.44.0007.
b1ackhawk said:
anybody know if this is possible yet?
Click to expand...
Click to collapse
According to the latest email from HTC, it should be fixed by the end of February.
Blue6IX said:
Some people have been able to use the HTC unlock tool, most people it doesn't work for.
At the moment, that's really all there is...
Sent from my Bulletproof_Doubleshot using xda premium
Click to expand...
Click to collapse
Well, I just tried the HTC Unlock tool and it has ended up working. I just need to figure out how to flash Superuser now.. :s
http://forum.xda-developers.com/showthread.php?t=1426179[
I posted a link to instructions
rooted 1.55.531.3 with clockwork recovery and SU
Limewirelord said:
Well, I just tried the HTC Unlock tool and it has ended up working. I just need to figure out how to flash Superuser now.. :s
Click to expand...
Click to collapse
How to fastboot flash recovery
and then:
Gain root access on the latest 1.55.531.3 update, ONLY IF you are S-OFF
At the second link you can find an updated superuser file to flash in your new recovery.
I have an S-On 1.55.531.3 phone. I tried the HTC unlocker (link from nlarge). Everything flashed correctly w/o error, but I did not get the splash screen on my phone at the end that asks if I want to unlock my phone. So my phone is still locked. If anyone has any thoughts on what to try, let me know.
qwerty3656 said:
I have an S-On 1.55.531.3 phone. I tried the HTC unlocker (link from nlarge). Everything flashed correctly w/o error, but I did not get the splash screen on my phone at the end that asks if I want to unlock my phone. So my phone is still locked. If anyone has any thoughts on what to try, let me know.
Click to expand...
Click to collapse
You're part of the group for whom the bootlooader unlock tool doesn't work, and you'll have to wait for HTC to deliver a fix.
For those of us with hboot_1.45.0013..... any way to get recovery? I can flash the recovery but it does not seem to do anything when i boot in to it. When i make any choice like install from zip and select using power button just a logo of rom manager comes up and no action..... any help for my hboot is appreciated. Thanks in advance.
misha said:
For those of us with hboot_1.45.0013..... any way to get recovery? I can flash the recovery but it does not seem to do anything when i boot in to it. When i make any choice like install from zip and select using power button just a logo of rom manager comes up and no action..... any help for my hboot is appreciated. Thanks in advance.
Click to expand...
Click to collapse
Use the trackpad to select options instead of power. Dont forget to hit the thanks button
Sent from my HTC MyTouch 4G Slide using Tapatalk 2
Limewirelord said:
Those of us on HBOOT 1.44.0013 are still waiting on an unlock method since HTC's boot unlocker is still borked and people are still trying to figure out a way to downflash to HBOOT 1.44.0007.
Click to expand...
Click to collapse
So what is it only 1.44.1107 hboot could utilize revolutionary ? I thought any 1.44 could do it ... damn I really did get lucky
Some_dude36 said:
So what is it only 1.44.1107 hboot could utilize revolutionary ? I thought any 1.44 could do it ... damn I really did get lucky
Click to expand...
Click to collapse
Only .007 could use revolutionary. The .006 version shipped s-off.
Hastily spouted for your befuddlement

Upgraded to ICS using RUU, how do I get fastboot back?

Hey all,
I used the 3.24.401.1 RUU and then flashed arhd 6.2.1. Running great, and love ICS...but I would like to get fastboot commands back so I can SuperCID and do other things, such as flash to Mike's custom firmware/other future firmwares more easily.
How do I get back fastboot on the RUU firmware? I had thought I could just use the old 1.17 unlocked bootloader but luckily I checked and found out that it's incompatible and would make my device unbootable with the current firmware, so that isn't an option.
Hmm....
P.S. CID Getter says my CID is: HTC_621
Edit: should I just use the link called "HTC2" at this link: http://forum.xda-developers.com/showthread.php?p=21711154#post21711154 and download the unlocked one?
greves1 said:
Hey all,
I used the 3.24.401.1 RUU and then flashed arhd 6.2.1. Running great, and love ICS...but I would like to get fastboot commands back so I can SuperCID and do other things, such as flash to Mike's custom firmware/other future firmwares more easily.
How do I get back fastboot on the RUU firmware? I had thought I could just use the old 1.17 unlocked bootloader but luckily I checked and found out that it's incompatible and would make my device unbootable with the current firmware, so that isn't an option.
Hmm....
P.S. CID Getter says my CID is: HTC_621
Edit: should I just use the link called "HTC2" at this link: http://forum.xda-developers.com/showthread.php?p=21711154#post21711154 and download the unlocked one?
Click to expand...
Click to collapse
Hi,
Please check HERE ...post # 2 ...HTC Part 2:
It gives you the "unlocked"version of the firmware,also the 1.17 firmware to go back to GB.
ics for sensation
is ics out for sensation xl???
karan231090 said:
is ics out for sensation xl???
Click to expand...
Click to collapse
Hi,
You are in the wrong forum.
This is for Sensation and Sensation XE.
Sorry.
malybru said:
Hi,
Please check HERE ...post # 2 ...HTC Part 2:
It gives you the "unlocked"version of the firmware,also the 1.17 firmware to go back to GB.
Click to expand...
Click to collapse
did that, now im in bootloop... can still get to recovery
greves1 said:
did that, now im in bootloop...
Click to expand...
Click to collapse
Hi,
Have you deleted the PG58IMG.zip after it has updated your phone?
malybru said:
Hi,
Have you deleted the PG58IMG.zip after it has updated your phone?
Click to expand...
Click to collapse
i will do that now, but i dont see how that is the issue exactly? even if you have a p58img.zip on your card, unless you hold down to get to recovery, phone should boot normally, no?
btw thanks for your help, stick around for a minute if you dont mind until im back into my OS pls! haha
im still looping!
greves1 said:
im still looping!
Click to expand...
Click to collapse
totally stuck now, cant even get into recovery!!!! omg
greves1 said:
im still looping!
Click to expand...
Click to collapse
Hi,
Sorry,I missed something.
Which PG58IMG did you flash...
The 1.17 or the 3.24 unlocked?
3.24 unlocked! it flashed fine, said complete at the end
i cant get to any bootloader screen or anything, jeez...
holding down button very firmly, still nothing...
with or without sd card...
greves1 said:
3.24 unlocked! it flashed fine, said complete at the end
i cant get to any bootloader screen or anything, jeez...
Click to expand...
Click to collapse
Hi,
Take the battery out,card out,delete the PG58IMG,battery back,card back ,then super wipe,then flash the ROM...
malybru said:
Hi,
Take the battery out,card out,delete the PG58IMG,battery back,card back ,then super wipe,then flash the ROM...
Click to expand...
Click to collapse
i deleted the pg from within ext4 when i was able to get in, now im unable to get back in. i really dont know why it wont let me in, im holding down...ive done this so many times, i dont think im doing anything wrong...
trying to use adb to get into recovery...works!! yay
man i guess i just have to reinstall the rom?? can i try and do a restore?? relaly thanks for your help btw!
greves1 said:
i deleted the pg from within ext4 when i was able to get in, now im unable to get back in. i really dont know why it wont let me in, im holding down...ive done this so many times, i dont think im doing anything wrong...
trying to use adb to get into recovery...works!! yay
man i guess i just have to reinstall the rom?? can i try and do a restore?? relaly thanks for your help btw!
Click to expand...
Click to collapse
Hi,
PHEW!!
I would start afresh...super wipe and re-flash the ROM.
malybru said:
Hi,
PHEW!!
I would start afresh...super wipe and re-flash the ROM.
Click to expand...
Click to collapse
haha...redownloading 6.2.1 as we speak... im afraid to leave recovery though lol, just wanna make sure i can get back there. wonder why it wasnt working with down button, only adb... will post here with update when its finished.
maybe my old rom didnt work cause it noticed a different bootloader and just...didnt want to boot. does anyone know? it seems like what i tried to do should have worked (just basically switch out stock 3.24 for mikes unlocked 3.24)
i still cannot for the life of me get into bootloader/recovery via power+downvol. any ideas anyone?
greves1 said:
i still cannot for the life of me get into bootloader/recovery via power+downvol. any ideas anyone?
Click to expand...
Click to collapse
Hi,
Have you got your ROM up and running?
Can you use the volume rocker in the ROM to adjust the sound?
hey, still 20 mins left on my ARHD download... hope it works ok. volume rocker works fine if i do adb reboot bootloader, i am able to move up and down. it seems like the firmware flash went fine, still can do everything in recovery. im ready to flash arhd soon as its done downloading, then we'll see if it boots and if i can once again enter bootloader using vol- so weird...
btw the bootloop is very fast. it goes to the first HTC screen, then just for a few seconds to the 2nd screen with the "quietly brilliant", then it just resets itself. (that was what it did before i super wiped, anyway. oh and i also restored from a backup once as well, to no avail.)
http://forum.xda-developers.com/showpost.php?p=20554933&postcount=3
-= NOTE =-
Your probably get into a bootloop after flashing teh 3.24 firmware.
Two way to get into your recovery.
1. Open the cmd and type adb reboot recovery
2.remove your sd and delete the firmware image and reboot into the bootloader and select recovery
this seems relevant..

Flashed wrong boot.img, going through bootloop

I had no idea but I was trying to flash leedroid and then I found out shortly after that leedroid is only available for the international version. I flashed the boot.img (and all went well), but then when I reboot I get the HTC logo and nothing more.
This is not good at all. I'm worried that it might have soft bricked it. But, is it just a matter of loaded up fastboot and flashing the correct at&t boot.img?? If so, do I do it in the same way that I flashed the wrong boot.img?? Also does the bootloader have to be re-locked? I assume so. Maybe not.
Thank you!
Shawn
shgadwa said:
I had no idea but I was trying to flash leedroid and then I found out shortly after that leedroid is only available for the international version. I flashed the boot.img (and all went well), but then when I reboot I get the HTC logo and nothing more.
This is not good at all. I'm worried that it might have soft bricked it. But, is it just a matter of loaded up fastboot and flashing the correct at&t boot.img?? If so, do I do it in the same way that I flashed the wrong boot.img?? Also does the bootloader have to be re-locked? I assume so. Maybe not.
Thank you!
Shawn
Click to expand...
Click to collapse
Just flash the correct one like you flashed the wrong one. The boot loader does not and should not be relocked, it should be unlocked.
shgadwa said:
I had no idea but I was trying to flash leedroid and then I found out shortly after that leedroid is only available for the international version. I flashed the boot.img (and all went well), but then when I reboot I get the HTC logo and nothing more.
This is not good at all. I'm worried that it might have soft bricked it. But, is it just a matter of loaded up fastboot and flashing the correct at&t boot.img?? If so, do I do it in the same way that I flashed the wrong boot.img?? Also does the bootloader have to be re-locked? I assume so. Maybe not.
Thank you!
Shawn
Click to expand...
Click to collapse
is all you flashed, the boot.img or did you flash leedroid too? If you flashed leedroid then do the following:
plug it in to USB while it bootloops type adb reboot recovery
from there you can access your nandroid backup assuming you made one.
if you didn't make a backup then yeah you'll have to flash the 1.85 RUU. To do this, relock the bootloader from adb fastboot oem lock
run the RUU unlock the bootloader then install your recovery and push root files via recovery.
Much easier than having to re-root 1.85 with the new exploit etc.
If he can get to recovery then he can try pushing a ROM to the SD and flashing it first instead of flashing the RUU and all that hassle.
mbh87 said:
If he can get to recovery then he can try pushing a ROM to the SD and flashing it first instead of flashing the RUU and all that hassle.
Click to expand...
Click to collapse
I keep forgetting we have adb through recovery now. Good call. But do we have USB?
Latest TWRP is suppose to have both ADB and USB
You should always back up
Sent from my HTC One XL using Tapatalk 2
kkoshko1 said:
You should always back up
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
Amen.
nandroid is always my first step when flashing a ROM
I just flashed boot.img. I cannot get to recovery.
Also I've been reading about how to flash a rom via fastboot. At the time I thought that the reason it was not working was because I flashed boot.img fist when I should of flashed leedroid first. Then I found out (much, much to my disappointment) that leedroid was only for international phones (which as we all know, have a different cpu).
Anyways, I've read that you should relock the bootloader before proceeding and now I see clearly that I was wrong in doing so. Why oh why don't I wait for you guy's awesome help...?
Anyways, so now I'm relocked. I just need to flash the correct boot.img (as soon as I find it). But I don't think I can do that while I'm locked. Heh. I would think I could just run the one click superCID tool again but I can't do that because the tool tries to reboot the phone using adb shell and the phone isn't fully powered on. I think will have to do it from fastboot, but I am not sure how.
Thank you guys for your help.
mbh87 said:
Latest TWRP is suppose to have both ADB and USB
Click to expand...
Click to collapse
I didn't see any need in backing up because I assumed all would go well and also I don't have any data on here that I want. Lesson learned well though. I will always back up. Now I've gotta get it working...
shgadwa said:
I just flashed boot.img. I cannot get to recovery.
Also I've been reading about how to flash a rom via fastboot. At the time I thought that the reason it was not working was because I flashed boot.img fist when I should of flashed leedroid first. Then I found out (much, much to my disappointment) that leedroid was only for international phones (which as we all know, have a different cpu).
Anyways, I've read that you should relock the bootloader before proceeding and now I see clearly that I was wrong in doing so. Why oh why don't I wait for you guy's awesome help...?
Anyways, so now I'm relocked. I just need to flash the correct boot.img (as soon as I find it). But I don't think I can do that while I'm locked. Heh. I would think I could just run the one click superCID tool again but I can't do that because the tool tries to reboot the phone using adb shell and the phone isn't fully powered on. I think will have to do it from fastboot, but I am not sure how.
Thank you guys for your help.
Click to expand...
Click to collapse
You should only supercid once, doesn't need to be re done, no matter locked or unlocked. Can you get to fastboot, try to ruu back...I dunno if this helps but that's what I would try
Sent from my HTC One XL using Tapatalk 2
shgadwa said:
I just flashed boot.img. I cannot get to recovery.
Also I've been reading about how to flash a rom via fastboot. At the time I thought that the reason it was not working was because I flashed boot.img fist when I should of flashed leedroid first. Then I found out (much, much to my disappointment) that leedroid was only for international phones (which as we all know, have a different cpu).
Anyways, I've read that you should relock the bootloader before proceeding and now I see clearly that I was wrong in doing so. Why oh why don't I wait for you guy's awesome help...?
Anyways, so now I'm relocked. I just need to flash the correct boot.img (as soon as I find it). But I don't think I can do that while I'm locked. Heh. I would think I could just run the one click superCID tool again but I can't do that because the tool tries to reboot the phone using adb shell and the phone isn't fully powered on. I think will have to do it from fastboot, but I am not sure how.
Thank you guys for your help.
Click to expand...
Click to collapse
Download your previous Unlock_code.bin and flash the unlock token again. Your CID should still be SuperCID, installing Rooms or RUUs don't change the CID.
kkoshko1 said:
You should only supercid once, doesn't need to be re done, no matter locked or unlocked. Can you get to fastboot, try to ruu back...I dunno if this helps but that's what I would try
Sent from my HTC One XL using Tapatalk 2
Click to expand...
Click to collapse
Thats actually why I re-locked. I've read that before installing an ruu, you need to re-lock.
I can get to fastboot. I tried to unlock via fastboot but it quickly timesout. I'm currently downloading 1.85 .exe ruu. I will give that a try as soon as its done downloading unless you guys have a better idea.
rohan32 said:
Download your previous Unlock_code.bin and flash the unlock token again. Your CID should still be SuperCID, installing Rooms or RUUs don't change the CID.
Click to expand...
Click to collapse
Thats a great idea! How do I do that via fastboot? I would assume fastboot flash Unlock_code.bin, but that doesn't work. As far as I know you can only flash .img. Or update .zip. What am I doing wrong?
shgadwa said:
Thats a great idea! How do I do that via fastboot? I would assume fastboot flash Unlock_code.bin, but that doesn't work. As far as I know you can only flash .img. Or update .zip. What am I doing wrong?
Click to expand...
Click to collapse
fastboot flash unlocktoken Unlock_code.bin
gunnyman said:
fastboot flash unlocktoken Unlock_code.bin
Click to expand...
Click to collapse
Thanks! That worked perfectly. Now I just need to find a AT&T boot.img.
Man, this international version is really throwing me off. I wish it was called something entirely different. It'd make it a lot easier. Its technically not the same phone at all anyway. Must be a marketing thing.
Anyways, I need to find a AT&T boot.img. I could get it from here http://forum.xda-developers.com/showthread.php?t=1689824 but I'm not sure if thats AT&T. It does say 1.82 is AT&T but mentions nothing else of 1.85 and 1.88. I am downloading the ruu for 1.85 but thats taking forever.
If anyone has a working 1.85 AT&T boot.img or knows where I can get one (maybe the link I gave is correct?)... please let me know.
Again, thank you for your help!
shgadwa said:
Thanks! That worked perfectly. Now I just need to find a AT&T boot.img.
Man, this international version is really throwing me off. I wish it was called something entirely different. It'd make it a lot easier. Its technically not the same phone at all anyway. Must be a marketing thing.
Anyways, I need to find a AT&T boot.img. I could get it from here http://forum.xda-developers.com/showthread.php?t=1689824 but I'm not sure if thats AT&T. It does say 1.82 is AT&T but mentions nothing else of 1.85 and 1.88. I am downloading the ruu for 1.85 but thats taking forever.
If anyone has a working 1.85 AT&T boot.img or knows where I can get one (maybe the link I gave is correct?)... please let me know.
Again, thank you for your help!
Click to expand...
Click to collapse
Link is correct. Pay attention to the subforum. It specifically says AT&T One X, if that is the section you are in.
Just flash an att rom no need to flash boot.img seperately anymore it gets flashed in recovery. All you had to do to begin with is use fastboot to flash recovery then flash a new rom in recovery.
To stop the bootloop just hold the power button down til the buttons flash when the screen goes black hold the volume down button and it will boot into hboot. It's a safety feature htc built in because of no battery access, and it works no matter where you are at in the boot process.
You can use sick sense its an att build and flashes the boot.img while flashing the rom.
smokin1337 said:
Just flash an att rom no need to flash boot.img seperately anymore it gets flashed in recovery. All you had to do to begin with is use fastboot to flash recovery then flash a new rom in recovery.
To stop the bootloop just hold the power button down til the buttons flash when the screen goes black hold the volume down button and it will boot into hboot. It's a safety feature htc built in because of no battery access, and it works no matter where you are at in the boot process.
You can use sick sense its an att build and flashes the boot.img while flashing the rom.
Click to expand...
Click to collapse
Thank you. I do know how to get into hboot. I flashed boot.img and it is now working!
NVM saw your edit lol...

[Q] Help with Sense 6.0 Update

Hey guys!!
I've had PAC-ROM on my M4 for quite a long time now, decided to go back to stock because of reasons today.. Everything's fine, used TWRP to recover my stock ROM - I've made a backup
Now, I got the message for the Sense 6 update and I was so happy, it downloaded successfully, everything's well at this point. I click on Install Now and it boots to TWRP and nothing else happens.. I can't find a way to update. Can someone please help? ;/
Thanks in advance!
P.S. Sorry if I haven't posted any helpful information, I don't know what to post So tell me if you need to know anything, I'll share it right away
Peshyy said:
Hey guys!!
I've had PAC-ROM on my M4 for quite a long time now, decided to go back to stock because of reasons today.. Everything's fine, used TWRP to recover my stock ROM - I've made a backup
Now, I got the message for the Sense 6 update and I was so happy, it downloaded successfully, everything's well at this point. I click on Install Now and it boots to TWRP and nothing else happens.. I can't find a way to update. Can someone please help? ;/
)
Click to expand...
Click to collapse
just flash stock recovery instead of custom TWRP
iourikil said:
just flash stock recovery instead of custom TWRP
Click to expand...
Click to collapse
Ok, thanks.. http://forum.xda-developers.com/showpost.php?p=45905821&postcount=2 Is the first mentioned 'here' gonna work? the 1.31.401.1 one?
Thanks again :3
Edit:
I've flashed the 1.31.401.1 and it worked! Currently installing the update ;3
Peshyy said:
Ok, thanks.. http://forum.xda-developers.com/showpost.php?p=45905821&postcount=2 Is the first mentioned 'here' gonna work? the 1.31.401.1 one?
Thanks again :3
Click to expand...
Click to collapse
use recovery.img from this
firmware m4 OTA 3.10.401.4
https://mega.co.nz/#!eBIRwYIR!vGks0Gloq7VpgAD5POrlbBh1HWPfpRIFAxpMahG7Nk4
iourikil said:
use recovery.img from this
firmware m4 OTA 3.10.401.4
URL HIDDEN
Click to expand...
Click to collapse
Ok, thanks! I'll download it right away.. But here's an issue I got while installing the update with the previous recovery.. I get a phone with a red exclamation mark inside a triangle in the middle of updating.. any help ? ;s
Also, can you tell me is there a specific way of installing this recovery? Because there are multiple files and I don't know what to do with all of them ;/
Third edit:
I've just remembered fastboot flashed multiple partitions, so that's what they must be.. so I tried but I get errors on them except boot.img and recovery.img. The radio.img showed an error that the bootloader isn't the correct version or something..
Peshyy said:
Ok, thanks! I'll download it right away.. But here's an issue I got while installing the update with the previous recovery.. I get a phone with a red exclamation mark inside a triangle in the middle of updating.. any help ? ;s
Also, can you tell me is there a specific way of installing this recovery? Because there are multiple files and I don't know what to do with all of them ;/
Third edit:
I've just remembered fastboot flashed multiple partitions, so that's what they must be.. so I tried but I get errors on them except boot.img and recovery.img. The radio.img showed an error that the bootloader isn't the correct version or something..
Click to expand...
Click to collapse
extract file recovery.img from zip archive
and flash it as usual
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot
iourikil said:
extract file recovery.img from zip archive
and flash it as usual
fastboot flash recovery recovery.img
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
I get the same error... the Phone with a red exclamation mark with a triangle around it.. Is it because I'm rooted. I just searched and it might be it..
Should I follow the guide on theunlockr.com / 2014 / 03 / 18 / unroot-htc-one-mini /
So.. Should I only lock the bootloader or completely unroot it?
I'll try with only locking the bootloader in a sec..
Ok, here's what happens when I use fastboot oem lock : snag.gy / CnD59.jpg .. The bootloader shows as "RELOCKED", which is good.. but I still fail to install the update.. But regarding the un-rooting process, on theunlockr what is posted the .exe is US.. I'm from Bulgaria, which is Europe.. and if I download a UK version of the .exe will it still work ?
Edit.. will a tool like Revolutionary work? I saw it just sets the phone to S-OFF
Peshyy said:
Ok, here's what happens when I use fastboot oem lock : snag.gy / CnD59.jpg .. The bootloader shows as "RELOCKED", which is good.. but I still fail to install the update.. But regarding the un-rooting process, on theunlockr what is posted the .exe is US.. I'm from Bulgaria, which is Europe.. and if I download a UK version of the .exe will it still work ?
Edit.. will a tool like Revolutionary work? I saw it just sets the phone to S-OFF
Click to expand...
Click to collapse
I know that you can't get OTA with unlocked bootloader and rooted, and I don't think you can do it with a re-locked bootloader either.
OTA also failed for me with a "locked" bootloader, where i used revone to set the bootloader to Locked rather than Relocked.
The only way i've gotten OTA to install was to run the Att Ruu.exe to restore to stock. If i run update immediately after that, it works. If i do other things, like unlock, root, etc, the oTA fails, just the same as yours is failing.
If you want sense 6, the easiest way, from where you are now, would be to flash twrp 2.7.1.1 recovery, then install the stock sense 6 rom in the development section. If you're not on the latest firmware (hboot 2.22) then the path is a little longer, as you will have to s-off, then update firmware, then flash sense 6 rom.
jollywhitefoot said:
I know that you can't get OTA with unlocked bootloader and rooted, and I don't think you can do it with a re-locked bootloader either.
OTA also failed for me with a "locked" bootloader, where i used revone to set the bootloader to Locked rather than Relocked.
The only way i've gotten OTA to install was to run the Att Ruu.exe to restore to stock. If i run update immediately after that, it works. If i do other things, like unlock, root, etc, the oTA fails, just the same as yours is failing.
If you want sense 6, the easiest way, from where you are now, would be to flash twrp 2.7.1.1 recovery, then install the stock sense 6 rom in the development section. If you're not on the latest firmware (2.22) then the path is a little longer, as you will have to s-off, then update firmware, then flash sense 6 rom.
Click to expand...
Click to collapse
Ok, thanks for the info.. I don't know how to find my firmware.. It doesn't show up on the About phone menu.. I've gone to the bootloader and it isn't there as well.. if it's the hboot, my hboot is 2.21.0000, meaning it isn't 2.22.. ;/
Also.. can you tell me what *** TAMPERED *** means in the bootloader? Right above *** RELOCKED ***.
And what is the 'Att Ruu.exe'? I don't mind having no root, no unlocked bootloader, etc.. I want the pure HTC experience again..
Edit: I saw that 'Att Ruu.exe' stands for the AT&T model.. the thing is that mine isn't AT&T.. mine is international, I think.. doesn't have any other branding or whatsoever..
Peshyy said:
Ok, thanks for the info.. I don't know how to find my firmware.. It doesn't show up on the About phone menu.. I've gone to the bootloader and it isn't there as well.. if it's the hboot, my hboot is 2.21.0000, meaning it isn't 2.22.. ;/
Also.. can you tell me what *** TAMPERED *** means in the bootloader? Right above *** RELOCKED ***.
And what is the 'Att Ruu.exe'? I don't mind having no root, no unlocked bootloader, etc.. I want the pure HTC experience again..
Edit: I saw that 'Att Ruu.exe' stands for the AT&T model.. the thing is that mine isn't AT&T.. mine is international, I think.. doesn't have any other branding or whatsoever..
Click to expand...
Click to collapse
Hboot was what i was referring to when i said firmware. Sorry, but i don't have any experience with 2.21 so i don't know what ROMs you can flash with it. If i had to guess, i would think one of the older sense 5.5 roms in the dev section would work on it, but i've never been on 2.21, so i can't tell you which ones with any confidence. I don't think any of the sense 6 Roms will work for you, but, again, i don't know for sure as i've never been on 2.21.
Tampered i think comes up when you use custom recovery. I don't know exactly what triggers it, but i don't think just flashing custom recovery does. I think it might happen when you use custom recovery to flash a ROM. It's just a flag and nothing to worry about. It doesn't prevent you from doing anything.
RUUs are executable files that can restore your device to stock. They are carrier and location specific, so you need to make sure you use the one for your carrier and location, if it is available. I said ATT RUU becuase I'm on ATT in the US. RUU files aren't available for every carrier in every country. If you are in the US on Att, i can help you with this. If you are somewhere else or on a different carrier, i can't.
jollywhitefoot said:
Hboot was what i was referring to when i said firmware. Sorry, but i don't have any experience with 2.21 so i don't know what ROMs you can flash with it. If i had to guess, i would think one of the older sense 5.5 roms in the dev section would work on it, but i've never been on 2.21, so i can't tell you which ones with any confidence. I don't think any of the sense 6 Roms will work for you, but, again, i don't know for sure as i've never been on 2.21.
Tampered i think comes up when you use custom recovery. I don't know exactly what triggers it, but i don't think just flashing custom recovery does. I think it might happen when you use custom recovery to flash a ROM. It's just a flag and nothing to worry about. It doesn't prevent you from doing anything.
RUUs are executable files that can restore your device to stock. They are carrier and location specific, so you need to make sure you use the one for your carrier and location, if it is available. I said ATT RUU becuase I'm on ATT in the US. RUU files aren't available for every carrier in every country. If you are in the US on Att, i can help you with this. If you are somewhere else or on a different carrier, i can't.
Click to expand...
Click to collapse
Oh, that's a shame ;//
First - is there a way I can update to 2.22 ? ;/
Second - I mentioned earlier I'm from Bulgaria, which is in Europe. Isn't there an international RUU ? ;(
I've unlocked my bootloader again as I think found a way to make the phone S-OFF.. I just have to root my phone again as it's not rooted -__- I don't want a custom ROM download, I want the stock one with no modifications or anything else.. ;/
Peshyy said:
Oh, that's a shame ;//
First - is there a way I can update to 2.22 ? ;/
Second - I mentioned earlier I'm from Bulgaria, which is in Europe. Isn't there an international RUU ? ;(
I've unlocked my bootloader again as I think found a way to make the phone S-OFF.. I just have to root my phone again as it's not rooted -__- I don't want a custom ROM download, I want the stock one with no modifications or anything else.. ;/
Click to expand...
Click to collapse
Sorry. I missed where you said your location.
To upgrade your firmware, you have to s-off. There's a post somewhere around here that walks you through using revone, which I've done and had success with. I think I linked to it yesterday, so look through my old posts. If you can't find it, I'll send the link later.
But, yes, you have to be rooted to s-off.
I don't know about ruu for Bulgaria. Try looking on the HTC website, or your carrier's website.
The stock roms in the dev section seem to be pretty much 100% stock. I'm not a developer, so I don't know that they are for sure, but I think they are created directly from stock, just modified so you can flash then in recovery.
jollywhitefoot said:
Sorry. I missed where you said your location.
To upgrade your firmware, you have to s-off. There's a post somewhere around here that walks you through using revone, which I've done and had success with. I think I linked to it yesterday, so look through my old posts. If you can't find it, I'll send the link later.
But, yes, you have to be rooted to s-off.
I don't know about ruu for Bulgaria. Try looking on the HTC website, or your carrier's website.
The stock roms in the dev section seem to be pretty much 100% stock. I'm not a developer, so I don't know that they are for sure, but I think they are created directly from stock, just modified so you can flash then in recovery.
Click to expand...
Click to collapse
I tried revone about a hundred times with no success.. I just can't get it to work. I get an error 'Segmentation fault (core dumped)' and that's it -__- I tried googling but with no success.. I'm now trying rumrunner but as I look at the command prompt, it most likely won't succeed as well ;/ Yep.. it failed, said ERROR: looks like device is not rooted AND lacks an unsecure kernel. su or FU!!
!
I'm rooted and with unlocked bootloader, installed CWM as well
Edit:
So I found http://forum.xda-developers.com/htc...-official-stock-sense-6-rom-firmware-t2817921 .. I'm gonna try it out now, it's the same as my update, so yeah..
Peshyy said:
I tried revone about a hundred times with no success.. I just can't get it to work. I get an error 'Segmentation fault (core dumped)' and that's it -__- I tried googling but with no success.. I'm now trying rumrunner but as I look at the command prompt, it most likely won't succeed as well ;/ Yep.. it failed, said ERROR: looks like device is not rooted AND lacks an unsecure kernel. su or FU!!
!
I'm rooted and with unlocked bootloader, installed CWM as well
Edit:
So I found http://forum.xda-developers.com/htc...-official-stock-sense-6-rom-firmware-t2817921 .. I'm gonna try it out now, it's the same as my update, so yeah..
Click to expand...
Click to collapse
I got both of those errors and they were because i really wasn't rooted even though i thought i was.
jollywhitefoot said:
I got both of those errors and they were because i really wasn't rooted even though i thought i was.
Click to expand...
Click to collapse
Yeah, I understood that the hard way.. Tried so many things, nothing worked.. just threw my phone (on a soft place, but still) and won't deal with anything 'til tomorrow.. I'm just so pissed at the moment. The root that should work and has worked before doesn't work now.. I really don't know what's wrong -__- gonna do everything all over again and try to get S-OFF and attempt to fix OTA updates.. ;/
Peshyy said:
Yeah, I understood that the hard way.. Tried so many things, nothing worked.. just threw my phone (on a soft place, but still) and won't deal with anything 'til tomorrow.. I'm just so pissed at the moment. The root that should work and has worked before doesn't work now.. I really don't know what's wrong -__- gonna do everything all over again and try to get S-OFF and attempt to fix OTA updates.. ;/
Click to expand...
Click to collapse
Sorry. I've been there before. If i have time, i'll re-set my phone back to factory, s-on and see if i can remember what i did to fix that error. One possibility was that i didn't have a ROM installed, but i don't remember for sure. I'll see if I made any notes let you know if I remember what i did to fix.
jollywhitefoot said:
Sorry. I've been there before. If i have time, i'll re-set my phone back to factory, s-on and see if i can remember what i did to fix that error. One possibility was that i didn't have a ROM installed, but i don't remember for sure. I'll see if I made any notes let you know if I remember what i did to fix.
Click to expand...
Click to collapse
Whoah, thanks so much! You shouldn't be so kind.. That's so much work to do.. Damn ;/ THANKS!
Peshyy said:
Whoah, thanks so much! You shouldn't be so kind.. That's so much work to do.. Damn ;/ THANKS!
Click to expand...
Click to collapse
What's your exact status:
Unlocked or Relocked?
Tampered?
Which recovery?
Version?
Is there an OS installed or did you wipe?
jollywhitefoot said:
What's your exact status:
Unlocked or Relocked?
Tampered?
Which recovery?
Version?
Is there an OS installed or did you wipe?
Click to expand...
Click to collapse
It's Tampered and Unlocked. I totally formatted everything, put CWM and using stock software.. It's the Sense 5.5 with Android 4.4.2. ClockworkMod Recovery Touch 6.0.3.6

No longer needed

Edit- sunshine can temp root and s-off all versions now so this method is no longer needed
If you are currently on OS 4.17.605.9 you can downgrade to 4.17.605.5 while s-on by using a signed RUU.
Why might one need this? Perhaps a sunshine app update will support it? Dunno
This will NOT wipe your phone.
Option 1
For Lollipop
Download DOTTAT_VZWM8_S_ON_5.0.1_RUU.exe and doubleclick. Allow file to extract and install dependencies and then follow on screen prompts.
Option 2
Copy 0P6BIMG.zip to root of a physical SD formatted to fat32. No exfat! No internal storage! Must be external SD formated to fat32!
Reboot phone to bootloader and follow prompts once RUU is detected by phone.
Option 3
- (use this fastboot https://www.androidfilehost.com/?fid=95784891001612150 )
Fastboot RUU mode . This method assumes you have a working ADB/Fastboot directory on your PC. Download RUUish file and place in your working fastboot/adb directory. Boot your phone to fastboot mode and connect to PC. Issue the following commands.
fastboot oem rebootRUU
###while in this mode your phone will display an HTC logo on the screen
fastboot flash zip 0P6BIMG.zip
##while in this mode you will see an HTC logo on the screen and a green status bar across the bottom of the screen. When command output ##completes it may say reboot required to flush etc... if that's the case issue a "fastboot reboot-bootloader" command and restart option 1 again.
example
## assuming flash completes and no further flushing/reboots are requested from the cmd output you can now reboot IF you simply wish to reboot the system you can issue "fastboot reboot" which will reboot system.
## expect a good 5 minute plus first boot!
Downloads Do NOT mirror these elsewhere.
5.0.1 RUU EXE (single exe don't unzip)
- https://www.androidfilehost.com/?fid=95916177934540519
md5 e0ca625c221724d1e50d27330f97ba32
5.0.1 RUU zip
- https://www.androidfilehost.com/?fid=95916177934540511
md5 6a32ce5d3f86b886d38414e27cf5246e
FIRST!
J/K...
Thanks dottat, that's good information to have! A lot of people will be happy.
Zanzibar said:
FIRST!
Click to expand...
Click to collapse
Congrats...[emoji6]
Sent from my HTC6525LVW using Tapatalk
Will this allow HTCDEV.com to work?
razieltov said:
Will this allow HTCDEV.com to work?
Click to expand...
Click to collapse
No. This just downgrades you from 4.17.605.9 to 4.17.605.5. It does not change your CID to one allowed by HTCdev.com
Sent from my HTC6525LVW using Tapatalk
Quick question from a noob:
You say in the post that this will NOT delete data from the device. But the RUU tool ReadMe has a giant, bold red warning that says "Installing the ROM Update Utility (RUU) will delete ALL information and data on your Android phone."
So... which is it? Will the tool wipe the device or not?
nic0machus said:
Quick question from a noob:
You say in the post that this will NOT delete data from the device. But the RUU tool ReadMe has a giant, bold red warning that says "Installing the ROM Update Utility (RUU) will delete ALL information and data on your Android phone."
So... which is it? Will the tool wipe the device or not?
Click to expand...
Click to collapse
Well geesssh... who you gonna believe? So you are asking me if it's my word or some silly readme? That's a conflict of interest for me to answer of sorts
NO IT WILL NOT WIPE
dottat said:
Well geesssh... who you gonna believe? So you are asking me if it's my word or some silly readme? That's a conflict of interest for me to answer of sorts
NO IT WILL NOT WIPE
Click to expand...
Click to collapse
I don't believe you...[emoji6]
Sent from my unknown using Tapatalk
bschram said:
I don't believe you...[emoji6]
Sent from my unknown using Tapatalk
Click to expand...
Click to collapse
I wouldn't either.. I've got nothing to lose!
>NO IT WILL NOT WIPE
Well gee... if you say so... I guess I'll get a 4th opinion first.
nic0machus said:
>NO IT WILL NOT WIPE
Well gee... if you say so... I guess I'll get a 4th opinion first.
Click to expand...
Click to collapse
Asking whom?
dottat said:
Asking whom?
Click to expand...
Click to collapse
Just messing with you, man.
It just finished, worked perfectly. Thank you!
dottat said:
Asking whom?
Click to expand...
Click to collapse
nic0machus said:
Just messing with you, man.
It just finished, worked perfectly. Thank you!
Click to expand...
Click to collapse
Somehow when he ran the RUU on his device, it wiped my device. Thanks for nothing :/
Hello, after exhaustive novice efforts and following the link rabbit hole, I'm here. I have a Verizon HTC One M7 on lollipop 5.0.2. I'm bootloader locked, s-on and of course not rooted. I tried this thread to no success http://forum.xda-developers.com/ver...root-root-method-bl-unlock-5-0-x-ota-t3122099. That thread deals with kingroot and Sunshine. It looks like I need to get to temproot for Sunshine to work.
This thread looks like it's using downgrading to get to a point where one can attain temproot which will enable Sunshine to run? - that is if I'm understanding correctly.
Will this work for an M7? It looks like it's for an M8.
Is there any other hope for a locked, s-on, unrooted M7 at this point? THANK YOU for what you do.
NoFussGus said:
Hello, after exhaustive novice efforts and following the link rabbit hole, I'm here. I have a Verizon HTC One M7 on lollipop 5.0.2. I'm bootloader locked, s-on and of course not rooted. I tried this thread to no success http://forum.xda-developers.com/ver...root-root-method-bl-unlock-5-0-x-ota-t3122099. That thread deals with kingroot and Sunshine. It looks like I need to get to temproot for Sunshine to work.
This thread looks like it's using downgrading to get to a point where one can attain temproot which will enable Sunshine to run? - that is if I'm understanding correctly.
Will this work for an M7? It looks like it's for an M8.
Is there any other hope for a locked, s-on, unrooted M7 at this point? THANK YOU for what you do.
Click to expand...
Click to collapse
You can get S-OFF using Java card.
http://forum.xda-developers.com/verizon-one-m9/general/m9-java-card-t3063247
When i Try to use the RUU on my M8 to revert the firmware to the earlier version of 5.01 the program get stuck saying updating (0/7) sending and doesnt budge. any help?
revert
rayparlour said:
When i Try to use the RUU on my M8 to revert the firmware to the earlier version of 5.01 the program get stuck saying updating (0/7) sending and doesnt budge. any help?
Click to expand...
Click to collapse
You need to be S-0ff to downgrade to an earlier version.
michaelbsheldon said:
You need to be S-0ff to downgrade to an earlier version.
Click to expand...
Click to collapse
LOL... you missed the thread title?
rayparlour said:
When i Try to use the RUU on my M8 to revert the firmware to the earlier version of 5.01 the program get stuck saying updating (0/7) sending and doesnt budge. any help?
Click to expand...
Click to collapse
Boot phone into fastboot mode and restart the EXE.
Used Fastboot Method
I tried the exe method and it kept getting stuck. I switched over to the Fastboot method and the flash of the ZIP file failed. Tried this twice and it failed both times. I'm S-On with a Verizon M8 (5.0.1). I'm trying to downgrade to root and while I've seen several sites say it couldn't be done, your post gave me a small bit of hope.
Let me know if you have any ideas. Gracias.

Categories

Resources