[Q] Help M7 stuck in fastboot - One (M7) Q&A, Help & Troubleshooting

Hi.
I've been trying to follow instructions from several threads about restoring an M7 to un-rooted, relocked, stock O2 ROM.
Things have gone badly from the start and I've tried so many different people's posts about what I should do that I'm completely confused now and need some help getting back on track.
At the moment all I've got is a hboot screen with fastboot working (unable to boot into recovery)
The last thing I did before this all went bed was to use 'fastboot oem relock' (which worked) I've tried 'fastboot oem unlock' but that says '[ERR] Command error !!!'.
I've tried flashing a stock rom.zip extracted from an O2 RUU but it fails with the code 'FAILED (remote: 22 loading zip info fail Please check if you flash part)'.
This is the 'getvar all' result.
C:\flashing\mini-sdk>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ????
(bootloader) imei: ????
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4229mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Any help appreciated.
Thanks.

thintin said:
Hi.
I've been trying to follow instructions from several threads about restoring an M7 to un-rooted, relocked, stock O2 ROM.
Things have gone badly from the start and I've tried so many different people's posts about what I should do that I'm completely confused now and need some help getting back on track.
At the moment all I've got is a hboot screen with fastboot working (unable to boot into recovery)
The last thing I did before this all went bed was to use 'fastboot oem relock' (which worked) I've tried 'fastboot oem unlock' but that says '[ERR] Command error !!!'.
I've tried flashing a stock rom.zip extracted from an O2 RUU but it fails with the code 'FAILED (remote: 22 loading zip info fail Please check if you flash part)'.
This is the 'getvar all' result.
C:\flashing\mini-sdk>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: O2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4229mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Any help appreciated.
Thanks.
Click to expand...
Click to collapse
remove your imei and serial number from your output above, its dangerous to post them.
according to your hboot which is 1.57 you wont beable to use that ruu, you cant back flash unless you have s-off.
also, only way to unlock your bootloader is at HTC dev again, you cant use a command to do it, so start there.

Seanie280672 said:
remove your imei and serial number from your output above, its dangerous to post them.
according to your hboot which is 1.57 you wont beable to use that ruu, you cant back flash unless you have s-off.
also, only way to unlock your bootloader is at HTC dev again, you cant use a command to do it, so start there.
Click to expand...
Click to collapse
Thanks for the tip (oops) So is that the first step I need to do, unlock the bootloader again? Just checking before I go ahead. Thanks.
Update...
I went to the HTCDev site to unlock again (I know I'm impatient but I'm running out of time to get this done) but it didn't work. This is what the site reported back:-
We're sorry, but it appears your attempt to unlock the bootloader on this device has failed. This could be caused by several factors including simple errors in the entry of the unlock token, problems with your device, or a lack of manufacturer support for the unlocking process. Please see the specific error code listed below, and try again if necessary.
Error Code: Invalid Bootloader Token Length.
Error Reason: The submitted Token appears to be the wrong length and won't work.
Click to expand...
Click to collapse
I tried again and made sure the entire code was included as well as the start and finish tags but still it failed.
Help .... :-l

thintin said:
Thanks for the tip (oops) So is that the first step I need to do, unlock the bootloader again? Just checking before I go ahead. Thanks.
Click to expand...
Click to collapse
yes that's the first step, then you need to decide if you want to go s-off and flash that original rom of yours, or go unbranded, or just flash a custom recovery and a custom rom.
---------- Post added at 07:15 PM ---------- Previous post was at 06:59 PM ----------
in fact, thinking about it, you will have to go with custom rom and recovery as you need a rom on your phone to go s-off.
---------- Post added at 07:17 PM ---------- Previous post was at 07:15 PM ----------
thintin said:
Thanks for the tip (oops) So is that the first step I need to do, unlock the bootloader again? Just checking before I go ahead. Thanks.
Update...
I went to the HTCDev site to unlock again (I know I'm impatient but I'm running out of time to get this done) but it didn't work. This is what the site reported back:-
I tried again and made sure the entire code was included as well as the start and finish tags but still it failed.
Help .... :-l
Click to expand...
Click to collapse
strange, that's the only way your going to be able to unlock your bootloader, and unfortunately, there's nothing you can do with a relocked bootloader, can you post your token here so I can look over it.

Seanie280672 said:
yes that's the first step, then you need to decide if you want to go s-off and flash that original rom of yours, or go unbranded, or just flash a custom recovery and a custom rom.
---------- Post added at 07:15 PM ---------- Previous post was at 06:59 PM ----------
in fact, thinking about it, you will have to go with custom rom and recovery as you need a rom on your phone to go s-off.
---------- Post added at 07:17 PM ---------- Previous post was at 07:15 PM ----------
strange, that's the only way your going to be able to unlock your bootloader, and unfortunately, there's nothing you can do with a relocked bootloader, can you post your token here so I can look over it.
Click to expand...
Click to collapse
Sure, I appreciate your help with this
<<<< Identifier Token Start >>>>
5A5F19A2F517CC2BEA0DDADB1C3924C7
FA7846F59B3E38FC5897B053899BA233
824B607DDBDD9CE31E453E48CBE4EF5C
8ECD29487C09FE311D30DA91386C56C5
FF130E636BA23977B05905925EB17FC6
3EBBCC1BFCB2383B1A7DAFDCBFBE0AA7
8DA65BF8F702E6F44F24743AFA8573EB
AE8D23E995EED6E7CBC5981CEBBAFC66
694176C863DB9858CC535ED2D3EC609C
043196ED2CDF60AC13DEBBB636AA348E
E748366B4CA16747C0593C363D6B98E2
81C2699B2D1D979E7ACAC97D4187788E
85AEA5F27B48A9F8278A0B49D0D3838B
92E2EDFE6B16EEEDE98F322D92294ED0
E43D1945184BBF8A0CB9661B92CB9E38
040AAF8857A0FC1A4C7682ACF8120340
<<<<< Identifier Token End >>>>>
Click to expand...
Click to collapse
I'm s-on BTW in case that makes a difference; never been s-off.

thintin said:
Sure, I appreciate your help with this
I'm s-on BTW in case that makes a difference; never been s-off.
Click to expand...
Click to collapse
that's very strange, just tried mine and it worked, tried yours and I got the same messages as you, but they are the same length etc.
Is this how you unlocked your bootloader before ? do you still have your original token anywhere ?

Seanie280672 said:
that's very strange, just tried mine and it worked, tried yours and I got the same messages as you, but they are the same length etc.
Is this how you unlocked your bootloader before ? do you still have your original token anywhere ?
Click to expand...
Click to collapse
This is how I unlocked it originally. I don't have the token but I do have the email they send afterwards with the bin file attached. Shall I try and use that again?

thintin said:
This is how I unlocked it originally. I don't have the token but I do have the email they send afterwards with the bin file attached. Shall I try and use that again?
Click to expand...
Click to collapse
yes defiantly, download the attachment and click the link on the email to continue the instructions.

Seanie280672 said:
yes defiantly, download the attachment and click the link on the email to continue the instructions.
Click to expand...
Click to collapse
Okay, that worked! (Phew). I now have an unlocked bootloader again.
So to get from my custom ROM, custom recovery and 'unlocked/tampered' state back to a stock rom/recovery and locked bootloader......what order do I have to do things? I know this is a big ask but I don't want to end up in a muddle again! Thanks.

thintin said:
Okay, that worked! (Phew). I now have an unlocked bootloader again.
So to get from my custom ROM, custom recovery and 'unlocked/tampered' state back to a stock rom/recovery and locked bootloader......what order do I have to do things? I know this is a big ask but I don't want to end up in a muddle again! Thanks.
Click to expand...
Click to collapse
if you have a working rom on there now then you will have to get s-off to do everything you want to do.
Try firewater first: http://firewater-soff.com/instructions/
if that fails then you will have to use sunshine, but you do have to pay for that: http://theroot.ninja/
out of interest, which rom are you running at the moment ?

Seanie280672 said:
if you have a working rom on there now then you will have to get s-off to do everything you want to do.
Try firewater first: http://firewater-soff.com/instructions/
if that fails then you will have to use sunshine, but you do have to pay for that: http://theroot.ninja/
out of interest, which rom are you running at the moment ?
Click to expand...
Click to collapse
I'm just trying the firewater method ATM. The ROM currently on the device is Revolution HD One 71.1

thintin said:
I'm just trying the firewater method ATM. The ROM currently on the device is Revolution HD One 71.1
Click to expand...
Click to collapse
ok good, also could you post a link to the O2 RUU you downloaded earlier

Seanie280672 said:
ok good, also could you post a link to the O2 RUU you downloaded earlier
Click to expand...
Click to collapse
GRRR!
Following firewater instructions...
adb reboot <–important!!!!
Click to expand...
Click to collapse
this caused loads of text to scroll down the cmd window but the device didn't reboot - not sure if it was supposed to?
adb wait-for-device push firewater /data/local/tmp
Click to expand...
Click to collapse
did this - cmd said that daemon was not running and started it but then nothing...no command prompt, phone doing nothing...eventually I closed the window. Now ADB wont recongnise the phone!
???
The stock O2 RUU was from HTC1guru.com (I think) I had to dig around quite a lot to find it. If I find the address I'll post it here.

thintin said:
GRRR!
Following firewater instructions...
this caused loads of text to scroll down the cmd window but the device didn't reboot - not sure if it was supposed to?
did this - cmd said that daemon was not running and started it but then nothing...no command prompt, phone doing nothing...eventually I closed the window. Now ADB wont recongnise the phone!
???
The stock O2 RUU was from HTC1guru.com (I think) I had to dig around quite a lot to find it. If I find the address I'll post it here.
Click to expand...
Click to collapse
try this version of adb and fastboot instead, sounds like its out of date and also check your device manager, make sure it says MyHTC when your phone is plugged in: http://forum.xda-developers.com/showthread.php?t=2588979

thintin said:
GRRR!
Following firewater instructions...
this caused loads of text to scroll down the cmd window but the device didn't reboot - not sure if it was supposed to?
Click to expand...
Click to collapse
It looks like you typed adb reboot <–important!!!! the <-important!!! should not have been typed. It is just a comment. You will notice on the firewater page it is bold where the rest of the type is not.

majmoz said:
It looks like you typed adb reboot <–important!!!! the <-important!!! should not have been typed. It is just a comment. You will notice on the firewater page it is bold where the rest of the type is not.
Click to expand...
Click to collapse
Don't worry, I didn't type the important! bit
I'm not sure how much more time I want to spend trying to reset this device, maybe I'll just return it to O2 as it is and see if they even care that it's been unlocked!
I'll try the link you suggested and report back :tired:

Hi.
I think my guardian angel must have had a hand in this because I was only trying to reset the phone to return it due to the microphone not working. After all of these failed attempts I factory reset the current rom and bingo! Microphone working again and no need to return to O2
But thanks for all of the help you offered, I would have a lot less hair and more wrinkles without you.

Related

[Solved] Need Help with S-On

Hey guys need ur help with going back to stock.Essentially I flashed the stock ruu and locked the bootloader and toggled my device from S-OFF to S-ON but i forgot to flash the stock recovery after rooting my phone using TWRP. Now my device is S-ON with bootloader locked and with custom recovery.I tried to use revone-0.2.1 to S-OFF and then unlock my bootloader but after few tries it says successful but when i checked the bootloader it shows S-ON and tampered.I even used firewater thta was also unsuccessful so please i need urgent help.
P.S My phone is still rooted.
You don't need to soff to flash stock recovery. You need unlocked bootloader. Unlock it using aio kit and you can flash stock recovery after that. You cannot flash recovery with a locked bootloader.
Sent from my All Metal HTC One.
Android 4.4.2 - Sense 6.0
well i tried using revone's option of unlocking bootloader shows error code -1
Hboot is 1.44
and if ur talking about using the unlock bin code i need stock recovery for that.Can someone provide me a signed stock recovery as i tried to flash a recovery from ruu but it shows signature verification failure.
Bump need urgent help
Slim Shady said:
Bump need urgent help
Click to expand...
Click to collapse
what's your current "fastboot getvar all" (except IMEI and s/n)
nkk71 said:
what's your current "fastboot getvar all" (except IMEI and s/n)
Click to expand...
Click to collapse
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.707.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 4179mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.044s
Slim Shady said:
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.707.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_u
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__038
finished. total time: 0.044s
Click to expand...
Click to collapse
well I couldn't find signed ruu, OTA, or signed firmware for your version, so best to start over from the beginning (unlock, s-off, etc), and do it again.
but one thing:
Essentially I flashed the stock ruu and locked the bootloader and toggled my device from S-OFF to S-ON but i forgot to flash the stock recovery after rooting my phone using TWRP
Click to expand...
Click to collapse
the RUU already has stock recovery, so why would you have TWRP there?
EDIT: if you have the recovery.img, maybe make a TWRP flashable zip and install it using twrp. Don't know if that works though.
nkk71 said:
what's your current "fastboot getvar all" (except IMEI and s/n)
Click to expand...
Click to collapse
nkk71 said:
well I couldn't find signed ruu, OTA, or signed firmware for your version, so best to start over from the beginning (unlock, s-off, etc), and do it again.
but one thing:
the RUU already has stock recovery, so why would you have TWRP there?
Click to expand...
Click to collapse
actually after applying the ruu i rooted the phone using twrp then locked the bootloader and then S-on the device.
Slim Shady said:
actually after applying the ruu i rooted the phone using twrp then locked the bootloader and then S-on the device.
Click to expand...
Click to collapse
see my last edit:
EDIT: if you have the recovery.img, maybe make a TWRP flashable zip and install it using twrp. Don't know if that works though.
Thats what I thought... restoring via RUU restores the recovery also.
nkk71 said:
see my last edit:
EDIT: if you have the recovery.img, maybe make a TWRP flashable zip and install it using twrp. Don't know if that works though.
Click to expand...
Click to collapse
Not even able to access twrp now. Is there any way u can help me ???
Slim Shady said:
Not even able to access twrp now. Is there any way u can help me ???
Click to expand...
Click to collapse
why can't you access TWRP
anyway, start from the beginning, unlock, s-off, etc.
nkk71 said:
why can't you access TWRP
anyway, start from the beginning, unlock, s-off, etc.
Click to expand...
Click to collapse
tried firewater not working asking to start the process again saying nasty chaser , then tried revone it reports success but when i check the bootloader it says s-on i just don't know what to do.
What happens when you choose recovery from bootloader?
finally success took a leap of faith used unlock token from htc and it worked yay.
Thanks to all the people who advised me and helped me troubleshoot.
can i run the ruu after i lock bootloader and return to s-on ???
also wanted to ask this
first i should get rid of tampered and lock my bootloader
then i should flash the ruu and them i should go S-on
right ?
Slim Shady said:
can i run the ruu after i lock bootloader and return to s-on ???
also wanted to ask this
first i should get rid of tampered and lock my bootloader
then i should flash the ruu and them i should go S-on
right ?
Click to expand...
Click to collapse
can you check my guide on how to do it: http://forum.xda-developers.com/showthread.php?t=2541082
RUU.ZIP method using this http://www.htc1guru.com/dld/ruu-zip...0-01_release_312087_signed_2_4_decrypted-zip/
this is a decrypted ruu.zip, so it only works with S-OFF.
got a new problem tampered text is not going away
getting error code -2 with revone
Slim Shady said:
got a new problem tampered text is not going away
Click to expand...
Click to collapse
WHY?? (how about more details next time )
EDIT: read the guide!!
nkk71 said:
WHY?? (how about more details next time )
EDIT: read the guide!!
Click to expand...
Click to collapse
Actually issue was dd commands and revone wasn't working for tampered so tried the guru rest and voila it worked.Now atlast everything's back to stock now i can give htc my phone and tell them to change it or repair it cause of the imsi issue im facing with the phone which happened after i got jtag brick repair.

No OS, S-ON need desperate help

I need really bad help with my phone, it's s-on i cant install any roms and i cant restore from a backup anymore, i have twrp installed as of now, I have tried every method for getting s - off in the past but that was with a custom crappy rom so it didnt work.
Att htc one m7 32gb please add me on skype, i need direct help and i cannot just waiting on somebody to reply to this thread, please i seek desperate help my skype name is rtorr724, please i need someone that knows a lot about android and could help me fix this problem.
i can give you any other info you may need on skype to help me fix my problem. thanks.
rtorr724 said:
I need really bad help with my phone, it's s-on i cant install any roms and i cant restore from a backup anymore, i have twrp installed as of now, I have tried every method for getting s - off in the past but that was with a custom crappy rom so it didnt work.
Att htc one m7 32gb please add me on skype, i need direct help and i cannot just waiting on somebody to reply to this thread, please i seek desperate help my skype name is rtorr724, please i need someone that knows a lot about android and could help me fix this problem.
i can give you any other info you may need on skype to help me fix my problem. thanks.
Click to expand...
Click to collapse
Reboot into fastboot mode.
Hold Power + Volume Down until, select Fastboot.
Run this command:
Code:
fastboot getvar all
We can then get the CID/Model and Fastboot version so you can use an RUU to recover the device.
DennisBold said:
Reboot into fastboot mode.
Hold Power + Volume Down until, select Fastboot.
Run this command:
Code:
fastboot getvar all
We can then get the CID/Model and Fastboot version so you can use an RUU to recover the device.
Click to expand...
Click to collapse
I did not know what to look for so i just copy nd pasted all of it
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: 000000000
(bootloader) imei: 0000000000
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3959mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
rtorr724 said:
I did not know what to look for so i just copy nd pasted all of it
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3959mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
you can use that RUU to restore your phone: http://www.htc1guru.com/2014/03/att-ruu/
with s-on you must have a locked or re-locked bootloader use it.
and btw, remove imei and serialno from your above post.
alray said:
you can use that RUU to restore your phone:
with s-on you must have a locked or re-locked bootloader use it.
and btw, remove imei and serialno from your above post.
Click to expand...
Click to collapse
I install it through sideload correct?
also what could someone do with my imei and serialno?
rtorr724 said:
I install it through sideload correct?
Click to expand...
Click to collapse
No its an .exe file. You must launch that executable using a windows pc with the phone connected to it and booted in bootloader mode.
also what could someone do with my imei and serialno?
Click to expand...
Click to collapse
Someone could use it to clone your phone.
alray said:
No its an .exe file. You must launch that executable using a windows pc with the phone connected to it and booted in bootloader mode.
Someone could use it to clone your phone.
Click to expand...
Click to collapse
Well thank you for telling me about it I wouldn't have wanted that to happen.
The download is pretty slow so when its done ill post back here with my results
rtorr724 said:
Well thank you for telling me about it I wouldn't have wanted that to happen.
The download is pretty slow so when its done ill post back here with my results
Click to expand...
Click to collapse
ok, also make sure to check that the MD5 value of your downloaded file will match the value given on the website.
should be: 5f121d72b8fa3f6f1704588467752605
you can use winMd5 program to check the value.
alray said:
ok, also make sure to check that the MD5 value of your downloaded file will match the value given on the website.
Click to expand...
Click to collapse
The program failed to work and got error 155, the md5 value matched and my phone just went to a black htc screen.
Like i said before if someone could add me on skype so it would be easier to help that would be great
rtorr724 <- skype
rtorr724 said:
The program failed to work and got error 155, the md5 value matched and my phone just went to a black htc screen.
Like i said before if someone could add me on skype so it would be easier to help that would be great
rtorr724 <- skype
Click to expand...
Click to collapse
is your bootloader locked or unlocked?
alray said:
is your bootloader locked or unlocked?
Click to expand...
Click to collapse
unlocked
rtorr724 said:
unlocked
Click to expand...
Click to collapse
so go back and read post #4 again...
alray said:
so go back and read post #4 again...
Click to expand...
Click to collapse
._. im really stupid xD
so what do i do now?
rtorr724 said:
._. im really stupid xD
so what do i do now?
Click to expand...
Click to collapse
relock the bootloader and run the ruu....
to lock the bootloader:
Code:
fastboot oem lock
alray said:
relock the bootloader and run the ruu....
to lock the bootloader:
Code:
fastboot oem lock
Click to expand...
Click to collapse
Thanks so much! but how do i get unlocked again?
rtorr724 said:
Thanks so much! but how do i get unlocked again?
Click to expand...
Click to collapse
you can unlock again the same way you did the first time, using the unlock_code.bin you have received from htcdev.com. if the unlock code you already have doesnt work anymore, request a new unlock code by submitting you identifier token again.
alray said:
you can unlock again the same way you did the first time, using the unlock_code.bin you have received from htcdev.com. if the unlock code you already have doesnt work anymore, request a new unlock code by submitting you identifier token again.
Click to expand...
Click to collapse
I have one last problem, i got s-off and everything and now im trying to get cm12 5.0 and everytime i try to install it, it returns with the error
E:Error in /data/media/0/cm.zip
(Status 0)
Installation aborted.
And above that it says a bunch of stuff of failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system:no such file or directory
and then it says the same thing for the unmount
rtorr724 said:
I have one last problem, i got s-off and everything and now im trying to get cm12 5.0 and everytime i try to install it, it returns with the error
E:Error in /data/media/0/cm.zip
(Status 0)
Installation aborted.
And above that it says a bunch of stuff of failed to mount /dev/block/platform/msm_sdcc.1/by-name/system at /system:no such file or directory
and then it says the same thing for the unmount
Click to expand...
Click to collapse
Which recovery are you using?
DennisBold said:
Which recovery are you using?
Click to expand...
Click to collapse
TWRP and CWM i get an error for both, i think its because when I wipe data/factory reset it gets rid of systtem
rtorr724 said:
TWRP and CWM i get an error for both, i think its because when I wipe data/factory reset it gets rid of systtem
Click to expand...
Click to collapse
I was more or less asking for your preference.
Your phone has partitions of memory which hold data, and when you update or install a custom ROM, the recovery utility mounts the partitions so they can be accessed to write and read data. Android does this every-time you turn on your phone. Formatting a partition doesn't delete it, it simply removes everything. CyanogenMod incorporated "block by name" mounting. Which basically makes it easier to mount partitions without being device specific.
Try this version of TWRP: http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.7.1.1-m7.img
Anything above 2.7.1.1 should work, anything below will not.
For ClockWorkMod anything above 6.0.4.8 will work.

[Q] Downgrade to KitKat+Root - Help?

So my M7 started heating up, chewing battery. Everything was fine with the first L update, but after the second one, something went wrong.
Now, I don't really want to do a factory reset - if I don't have to. And to be honest, it never helped with these random battery/cpu hogs in Android.
So!
- Could anyone link me the latest KitKat RUU? OR whatever I have to flash/install?
- The warranty is now gone for the phone, so I also want to root. How should I root? Via HTCDev? Sunshine?
If I can install KitKat somehow without losing files, I would just Sunshine - would save me tons of work (restore).
Thanks!
Ps.: I am not lazy, and I really tried to find the answers - but compared to how easy to flash an LG or Samsung, HTC looks like a spacecraft.
Seriously, while the two other have simple firmware files, and a simple app to flash, HTC got RUU, different unlocks, different firmwares, etc.
* I also thought about switching it to GPE, but honestly, 5.1 is not any better.
And it's the last update for the M7... it's a dead end anyhow.
KitKat will serve this phone perfectly fine for +1-2 years.
h8Aramex said:
- Could anyone link me the latest KitKat RUU? OR whatever I have to flash/install?
Click to expand...
Click to collapse
Impossible to tell without knowing your phone info. Post the output of "fastboot getvar all" remove imei and sn before posting.
- The warranty is now gone for the phone, so I also want to root. How should I root? Via HTCDev? Sunshine?
Click to expand...
Click to collapse
If your goal is to return to kitkat then
1- return to kitkat, how exactly will be determined after you have posted your "fastboot getvar all"
2- root the phone (unlock the bootloader, flash a custom recovery, flash latest supersu.zip)
---------- Post added at 12:20 PM ---------- Previous post was at 12:18 PM ----------
If I can install Kitat somehow without losing files
Click to expand...
Click to collapse
RUU will wipe everything
Flashing a rom requires an unlocked bootloader, unlocking the bootloader wipes everything.
So you will lose your files, backup first.
Sorry for the noob question, command issued while in normal mode through ADB?
Or in fastboot through ADB?
alray said:
Impossible to tell without knowing your phone info. Post the output of "fastboot getvar all" remove imei and sn before posting.
If your goal is to return to kitkat then
1- return to kitkat, how exactly will be determined after you have posted your "fastboot getvar all"
2- root the phone (unlock the bootloader, flash a custom recovery, flash latest supersu.zip)
---------- Post added at 12:20 PM ---------- Previous post was at 12:18 PM ----------
RUU will wipe everything
Flashing a rom requires an unlocked bootloader, unlocking the bootloader wipes everything.
So you will lose your files, backup first.
Click to expand...
Click to collapse
h8Aramex said:
Or in fastboot through ADB?
Click to expand...
Click to collapse
fastboot commands are always/can only be issued when the phone is booted in bootloader mode with "fastboot usb" red caption showing.
adb commands are/can only be used when booted in the OS with usb debug turned on or from a custom recovery no matter if usb debug is turned on or off.
alray said:
fastboot commands are always/can only be issued when the phone is booted in bootloader mode with "fastboot usb" red caption showing.
adb commands are/can only be used when booted in the OS with usb debug turned on or from a custom recovery no matter if usb debug is turned on or off.
Click to expand...
Click to collapse
Sorry for the delay.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.22
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: --------------
(bootloader) imei: 1111111111111111
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4068mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.073s
Click to expand...
Click to collapse
I want the latest 4.4 FW/ROM, preferably stock.
(But if that Revolution rom works fine, I am also fine with that one.)
--------------------------------
UPDATE:
Ok, so I thought I will try things by myself... it cannot be that hard.
I was wrong.
I am now more confused than ever.
h8Aramex said:
Sorry for the delay.
I want the latest 4.4 FW/ROM, preferably stock.
(But if that Revolution rom works fine, I am also fine with that one.)
--------------------------------
UPDATE:
Ok, so I thought I will try things by myself... it cannot be that hard.
I was wrong.
I am now more confused than ever.
Click to expand...
Click to collapse
Since that your phone is s-on you can not use a RUU to downgrade, you will have to unlock your bootloader, flash a custom recovery and finally flash a 4.4 rom. You'll will not be able to downgrade the firmware with S-ON, you can only change your rom.
to unlock the bootloader go at www.htcdev.com/bootloader and follow the instructions
once done flash a custom recovery, preferably TWRP 2.8.6.0:
Code:
fastboot flash recovery twrp-2.8.6.0-m7.img
fastboot erase cache
fastboot reboot-bootloader
boot in recovery and transfer the rom zip file you want to flash to your phone storage.
in twrp select "install" and flash your rom.
alray said:
////
Click to expand...
Click to collapse
Could you link me a 4.4 ROM, please?
Preferably Stock, HTC Sense one.
I checked the pinned thread, but every file is 404 (missing) by now, since it's a very old thread/post.
Thank you!
h8Aramex said:
Could you link me a 4.4 ROM, please?
Preferably Stock, HTC Sense one.
I checked the pinned thread, but every file is 404 (missing) by now, since it's a very old thread/post.
Thank you!
Click to expand...
Click to collapse
Stock 4.4.2 rom, latest version before lollipop (6.09.401.12)
https://www.androidfilehost.com/?fid=95916177934521261
Thank you!
I have managed to unlock + root (that wasn't really so hard, using Sunshine would have been harder). Will try to stay on L now, see if the reset helped with the battery drain. If not, it's time for Kitkat!

[Q] In Deep Trouble with MID Change. HELP PLEASE!!!

I tried changing my HTC One M8_WHL PVT SHIP S-OFF into developer edition using the guide on http://htc-one.wonderhowto.com/how-...edition-for-super-fast-sense-updates-0156524/ . I successfully changed the MID and the CID without breaking a sweat. After, I used TWRP to restore the backup which the guide instructed me to download and restore. After restoring that backup, device could only boot HBOOT. Now I tried running the RUU.exe for Developer Edition and I get the error which asks that I run the correct RUU for the device. Now, the device doesn't boot pass HBOOT
What I can do ...
1. Boot into TWRP recovery
2. Give fastboot commands with HBOOT
3. Boot into RUU via fastboot
What I can't do ...
1. Boot the device
2. Revert the MID change to its original state cos I will need to run ADB Shell to do that, which cannot be done from HBOOT
3. No RUU.exe is responding to flashing the device
The specific help I need ...
1. Be able to Change MID using Fastboot so I can run a SPRINT RUU
fastboot getvar all results ...
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.24.21331147A1.09G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.16.1540.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: Mod Edit
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: Mod Edit
(bootloader) product: m8_whl
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US002
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 3aa067db
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
PLEASE HELP!
You forgot the most important thing to do before doing something like this....read.
Your M8 must be a GSM model, like AT&T, T-Mobile, and most international variants.
Click to expand...
Click to collapse
Have you tried running the command to change the MID while booted to twrp?
As I have been using my GSM SIM in it, it didn't occur to me that it could be any different from a GSM Model. When I bought it, it came with S-Off and CID 11111111, though the bootloader was locked (like any other locked HBOOT from factory, not relocked).
BD619 said:
You forgot the most important thing to do before doing something like this....read.
Have you tried running the command to change the MID while booted to twrp?
Click to expand...
Click to collapse
Kindly show me direct me to a thread on how I can change the MID while booted to twrp. Thank you.
Economistaterry said:
My M8 is a GSM Model. I use to use my GSM SIM in it.
Click to expand...
Click to collapse
HTC One M8_WHL
Click to expand...
Click to collapse
is Sprint which is CDMA not GSM.
You said in your first post you could not revert your MID because you can't run adb shell... adb works in recovery...it's worth a shot.
Try changing your CID to SuperCID then try the Sprint RUU.
BD619 said:
is Sprint which is CDMA not GSM.
You said in your first post you could not revert your MID because you can't run adb shell... adb works in recovery...it's worth a shot.
Click to expand...
Click to collapse
ADB Shell won't start in TWRP sideload. But ADB devices comes out positively with the list of devices attached.
BD619 said:
Try changing your CID to SuperCID then try the Sprint RUU.
Click to expand...
Click to collapse
This was one of my first options. Didn't work.
Economistaterry said:
This was one of my first options. Didn't work.
Click to expand...
Click to collapse
Have you tried changing it back to Sprint CID?
BD619 said:
Have you tried changing it back to Sprint CID?
Click to expand...
Click to collapse
I haven't. The device came with Super CID. Let me try that and see. However, I tried flashing the firmware of Sprint via RUU with Super CID. The MID error showed up. I feel same will happen even if I change to Sprint CID, but I'll give it a shot.
BD619 said:
Have you tried changing it back to Sprint CID?
Click to expand...
Click to collapse
No luck.
adb should work in twrp(dont use adb sideload option, it should work without doing anything), try reinstalling TWRP i just tested it on v2.8.6 2015-04-22 p1
---------- Post added at 05:06 AM ---------- Previous post was at 05:00 AM ----------
Economistaterry said:
Kindly show me direct me to a thread on how I can change the MID while booted to twrp. Thank you.
Click to expand...
Click to collapse
here is the link(post #2 has code for sprint), please be very careful it can easily turn your M8 into a piece of aluminum.
Vcek said:
adb should work in twrp(dont use adb sideload option, it should work without doing anything), try reinstalling TWRP i just tested it on v2.8.6 2015-04-22 p1
---------- Post added at 05:06 AM ---------- Previous post was at 05:00 AM ----------
here is the link(post #2 has code for sprint), please be very careful it can easily turn your M8 into a piece of aluminum.
Click to expand...
Click to collapse
Bookmarked thanks.
vcek said:
adb should work in twrp(dont use adb sideload option, it should work without doing anything), try reinstalling twrp i just tested it on v2.8.6 2015-04-22 p1
---------- post added at 05:06 am ---------- previous post was at 05:00 am ----------
here is the link(post #2 has code for sprint), please be very careful it can easily turn your m8 into a piece of aluminum.
Click to expand...
Click to collapse
yes! Yes! You are a life saver! Thank you so much!
It worked! It worked!
Phone is back alive! Wheew!

HTC One m7 sprint Bricked??

Hey guys, so recently I purchased a htc one m7 (sprint) off of ebay. I planned to fix it because it was listed as in a bootloop. I thought this would be easy to fix, but I have run into some trouble. The phone does not boot, it just sits on the htc screen. Phone is currently s-on. I have full access to fastboot, but thats it. I feel like I have looked everywhere for a solution, but nothing has worked for me. Any help would be greatly appreciated.
Things I have tried:
1. factory reseting from bootloader menu.
2. entering recovery mode through bootloader menu. (goes back into bootloop, assuming recovery is corrupted)
3. unlocking the bootloader with htcdev, but after selecting yes on the popup menu on the phone to unlock, it just goes back into a bootloop, stays locked.
4. flashing twrp (fails due to locked bootloader)
5. using a RUU.exe to flash back to stock (bootloop, gets hung up on "waiting for bootloader..". If i manually put it back into fastboot I get a connection error)
6. using a RUU.zip and flashing through fastboot, but the "fastboot oem rebootRUU" command throws it back into a bootloop. Tried flashing without rebootRUU and got a verification error.
So, any ideas or is this thing bricked? Thanks.
Are you trying to run the RUU while already in fastboot, or are you trying to let the exe boot to fastboot for you? I'm assuming that you are running the RUU from fastboot, and the rebootRUU from the exe is looping you again?
Have you tried flashing the stock recovery?
Have you tried fastboot erase cache? (probably won't help in your situation, but why not?)
Those are some things you could try.
I am having this thread moved to the M7 Q&A forum. You'll have a good chance there of someone providing the steps you need to take to get yourself fixed up.
I suggest that you post the results of fastboot getvar all (minus you IMEI/MEID and serial# of course) so we have a better understanding of your firmware version and such.
Good luck!
yeah, im running the exe while in fastboot, and the rebootRUU loops me. I havent flashed stock recovery. will that allow me to flash anything to get this working? and i did try to wipe cache from fastboot.
so I tried flashing the stock recovery, and got a signature verification error.
here is the result of my getvar.
still not booting.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.01.20.1225
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.651.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4296mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
murphyhobo said:
so I tried flashing the stock recovery, and got a signature verification error.
here is the result of my getvar.
still not booting.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 1.01.20.1225
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.23.651.7
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4296mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
What is the current status of the bootloader? Locked or Relocked?
Can you please provide a link to the RUU your trying to flash.
If your using an RUU.exe then you don't need to use the Reboot RUU command. Just connect the device in fastboot usb mode and run the RUU. The RUU will boot to RUU mode for you :good:
Sent from my SM-T230 using Tapatalk
Danny201281 said:
What is the current status of the bootloader? Locked or Relocked?
Can you please provide a link to the RUU your trying to flash.
If your using an RUU.exe then you don't need to use the Reboot RUU command. Just connect the device in fastboot usb mode and run the RUU. The RUU will boot to RUU mode for you :good:
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
ok heres the link http://forum.xda-developers.com/showthread.php?t=2795856.
and my bootloader is locked.
I have tried just letting the .exe boot me to RUU, but it was stuck at "waiting for bootloader..". I waited for a little bit, but my phone kept vibrating and rebooting, and then eventually it lost connection and closed. I have tried multiple times.
murphyhobo said:
ok heres the link http://forum.xda-developers.com/showthread.php?t=2795856.
and my bootloader is locked.
I have tried just letting the .exe boot me to RUU, but it was stuck at "waiting for bootloader..". I waited for a little bit, but my phone kept vibrating and rebooting, and then eventually it lost connection and closed. I have tried multiple times.
Click to expand...
Click to collapse
I asked @coal686 about this, and he thinks it is probablya hardware problem. If so, you'll have to take it to a shop for repairs.
But there is a possibility that the previous owner wiped /system in fastboot. Highly unlikely, but fastboot erase system would cause something similar, I would imagine. Without knowing what the previous owner did to get it into this state makes it hard to narrow down.
Is there any chance you could contact the previous owner and ask what it is exactly before the phone pooched out? Let him know that there is nothing to hide now that you are the new OWNER of the phone.
xunholyx said:
I asked @coal686 about this, and he thinks it is probablya hardware problem. If so, you'll have to take it to a shop for repairs.
But there is a possibility that the previous owner wiped /system in fastboot. Highly unlikely, but fastboot erase system would cause something similar, I would imagine. Without knowing what the previous owner did to get it into this state makes it hard to narrow down.
Is there any chance you could contact the previous owner and ask what it is exactly before the phone pooched out? Let him know that there is nothing to hide now that you are the new OWNER of the phone.
Click to expand...
Click to collapse
well I would ask them, but the seller is a cell phone repair shop, so im guessing that somebody couldn't get it fixed, so they sold it to this shop, and the people probably don't have a clue what's wrong with it. I wont be worth it to try and repair it cuz it only cost me 30 bucks. It seems that the only solution here would be a RUU, but that aint working so I guess im stuck here.
murphyhobo said:
well I would ask them, but the seller is a cell phone repair shop, so im guessing that somebody couldn't get it fixed, so they sold it to this shop, and the people probably don't have a clue what's wrong with it. I wont be worth it to try and repair it cuz it only cost me 30 bucks. It seems that the only solution here would be a RUU, but that aint working so I guess im stuck here.
Click to expand...
Click to collapse
Unfortunately I think it is a lost cause . If the bootloader is not stable then it's almost certainly a hardware problem.
Even if it was some low level software issue without a stable bootloader there is no way to flash anything to the device.
Maybe sell it on eBay as Spares to try get something back from it.
Sent from my SM-T230 using Tapatalk
Alright, thanks for the help!
I have same problem htc one m7 wls
Download from http://forum.xda-developers.com/showthread.php?t=2250904
Flash in recovery
Copy zip to internal storage by enabling MTP in recovery
raghav9 9 said:
I have same problem htc one m7 wls
Download from http://forum.xda-developers.com/showthread.php?t=2250904
Flash in recovery
Copy zip to internal storage by enabling MTP in recovery
Click to expand...
Click to collapse
Not really a good idea, OP is on 6.23.651.7...... And since the OP can't even boot in recovery how he is supposed to flash this?....
alray said:
Not really a good idea, OP is on 6.23.651.7...... And since the OP can't even boot in recovery how he is supposed to flash this?....
Click to expand...
Click to collapse
Use firewater or revan to s-off first
Then unlock by htc dev
Flash cwm or twrp recovery
If you successfully 1st step then u can do easy
raghav9 9 said:
Use firewater or revan to s-off first
Then unlock by htc dev
Flash cwm or twrp recovery
If you successfully 1st step then u can do easy
Click to expand...
Click to collapse
Sorry but what you are saying is making me believe you didn't read what the OP said at all except maybe the first few lines...
Use firewater or revan to s-off first
Click to expand...
Click to collapse
Firewater is discontinued and doesn't work anymore, Revone S-OFF is for hboot 1.44 only, OP's phone is on 1.61. Achieving S-OFF requires a booting phone, exactly what the OP doesn't have. And BTW there a much newer RUU he could use than the one you have posted above that wouldn't requires S-OFF.
Then unlock by htc dev
Click to expand...
Click to collapse
I guess you missed that part:
3. unlocking the bootloader with htcdev, but after selecting yes on the popup menu on the phone to unlock, it just goes back into a bootloop, stays locked.
Click to expand...
Click to collapse
If you successfully 1st step then u can do easy
Click to expand...
Click to collapse
Not possible since like OP said:
6. using a RUU.zip and flashing through fastboot, but the "fastboot oem rebootRUU" command throws it back into a bootloop.
Click to expand...
Click to collapse
Its either a corrupt bootloader/firmware or an hardware problem and like Danny said its a lost cause.

Categories

Resources