[Q] fastboot mode:show "?????? fastboot" - Sprint HTC One (M7)

Lately I want to upgrade my htc one m7's firmware.Since my htc one is s-off and I changed its cid to 11111111,I downloaded a zip firmware pakage (include boot.img,hboot.img and recovery.img) ,prepared to install it at fastboot mode. here was my steps:
1.fastboot reboot-bootloader ------>success
2.fastboot oem rebootRUU -------->success, show silvery HTC
3.fastboot flash zip c:\users\requi000\download\firmware.zip ----->failed
Here is the results:
sending 'zip' (71868 KB)...
OKAY [ 4.936s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 6.410s
then I repeated the step 3, it showed
"FAILED (remote: not allowed)"
I thought I should repeat the steps from step 2, so I typed in "fastboot oem rebootRUU ",but it didn't show the silvery word I'd ever seen on screen.
My htc one turned into black.I didn't know why,so I typed in "fastboot devices" to see what it happened.
the result showed on screen realy surprised me:
C:\Users\requi_000>fastboot devices
???????????? fastboot
then I typed in fastboot getvar all,it showed:
C:\Users\requi_000>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: N/A
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN
(bootloader) serialno:
(bootloader) imei: 355195000000010
(bootloader) meid: 00000000000000
(bootloader) product:
(bootloader) platform: HBOOT-8064
(bootloader) modelid: *********
(bootloader) cidnum:
(bootloader) battery-status: good
(bootloader) battery-voltage: 4194mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: UNKNOWN
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.063s
God,I really didn't know what happened,and had no idea,from then on,my one has entirely turned into a brock!
ANY IDEAS? PLEASE!!!!!!!!!!!

Is there a reason you choose that firmware instead of the S-OFF firmware?

Umm well i had a similar issue the other day pushing something fastboot not exactly the same but sort of... I was pushing an hboot and when i typed the full folder location it didnt seem to like that it pushed it and everything but didnt like it gave me some error at the end so instead i dropped the file inside of a newfolder i put fastboot.exe inside of and pushed it with fasboot flash zip whatever.zip... Not exactly sure what the framework issue is on your end just something i did when i got an error for no reason and it seemed to work.
Not sure if that helps in your case if you can still get into fastboot your fine...

thanks for your reply
bigdaddy619 said:
Is there a reason you choose that firmware instead of the S-OFF firmware?
Click to expand...
Click to collapse
thanks for your reply .I just wana to change the previous firmware to anther,so that I can install the HK's Ruu...

sataliulan said:
thanks for your reply .I just wana to change the previous firmware to anther,so that I can install the HK's Ruu...
Click to expand...
Click to collapse
Do you have a Sprint HTC One? If so SuperCID will not allow you to use any RUU other then a Sprint RUU.
Sprint and Verizon Htc Ones are CDMA
All others are GSM

thanks for your reply
Pneuma1985 said:
Umm well i had a similar issue the other day pushing something fastboot not exactly the same but sort of... I was pushing an hboot and when i typed the full folder location it didnt seem to like that it pushed it and everything but didnt like it gave me some error at the end so instead i dropped the file inside of a newfolder i put fastboot.exe inside of and pushed it with fasboot flash zip whatever.zip... Not exactly sure what the framework issue is on your end just something i did when i got an error for no reason and it seemed to work.
Not sure if that helps in your case if you can still get into fastboot your fine...
Click to expand...
Click to collapse
well,i typed fastboot flash sth,but all results showed "not allowed"...
otherwise,thank you.

sataliulan said:
well,i typed fastboot flash sth,but all results showed "not allowed"...
otherwise,thank you.
Click to expand...
Click to collapse
are they both in the fastboot.exe folder?

yep
Pneuma1985 said:
are they both in the fastboot.exe folder?
Click to expand...
Click to collapse
yes

well,I used a fake Ruu
bigdaddy619 said:
Do you have a Sprint HTC One? If so SuperCID will not allow you to use any RUU other then a Sprint RUU.
Sprint and Verizon Htc Ones are CDMA
All others are GSM
Click to expand...
Click to collapse
I downloaded a decrypted ruu ,and changed the modelid in android-info.txt into mine.
it worked at first,but failed in the end

Related

M7 stuck on recovery after relock

Hi guys,
I've been trying to reset my One back to stock and I've accidentally got it stuck in recovery after I reclocked it with the All-in-one toolkit. Every time I restart it won't load Android and instead just goes to recovery.
I'm on Orange UK, HBOOT 1.44 and fastboot gives me:
(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.401.13
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4135mV
(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.039s
Please help I'm really stuck here!
Ok I've unlocked the phone again and now I can boot it up normally.... Can anyone help me with how to go back to stock? I don't want to mess it up again.
I'm running Android Revolution HD 20.2 Android 4.3, Sense 5.0
You can't boot locked with a custom recovery. That was your problem. Just relock and run a RUU right then and there.
iElvis said:
You can't boot locked with a custom recovery. That was your problem. Just relock and run a RUU right then and there.
Click to expand...
Click to collapse
I've found a few RUU's with the right baseband 4A.14.3250.13, but can only find 1.29.401.2 and 1.29.401.15. I tried to use these originally but it wouldn't do it... Any idea which one to go for? Thanks
gemuzz said:
I've found a few RUU's with the right baseband 4A.14.3250.13, but can only find 1.29.401.2 and 1.29.401.15. I tried to use these originally but it wouldn't do it... Any idea which one to go for? Thanks
Click to expand...
Click to collapse
You're on HTC__001, which is the generic European version. Those RUUs ought to work. What error message are you getting?
iElvis said:
You're on HTC__001, which is the generic European version. Those RUUs ought to work. What error message are you getting?
Click to expand...
Click to collapse
Right now I'm having trouble locking the bootloader before running the RUU. Everytime I try to lock I get
C:\Users\George\Desktop\fastboot>fastboot oem lock
...
FAILED (status read failed (Too many links))
finished. total time: -0.000s
Click to expand...
Click to collapse
And fastboot freezes so I have to do a hard reset.
I also tried to run the ruu in All-In-One Toolkit and got this
sending 'zip' (1010379 KB)...
OKAY [ 34.607s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) signature checking...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 162.643s
Click to expand...
Click to collapse
Are you in bootloader or recovery when running fastboot oem lock?
iElvis said:
Are you in bootloader or recovery when running fastboot oem lock?
Click to expand...
Click to collapse
Bootloader in fastboot usb
gemuzz said:
Bootloader in fastboot usb
Click to expand...
Click to collapse
try issuing the command
fastboot oem relock
instead to lock your bootloader
but before relocking your bootloader
download your guru reset from here
install using the custom recovery (twrp/cwm)
during installation, install the stock recovery and do not root
after that, you should be back to to stock and all you need to do is relock your device
why dont you s-off your device so you can be 100% stock and would seem like your phone is out of the box?
Since you're still on hboot 1.44, I recommend you get S-Off using revone, also remove TAMPERED and put it LOCKED (using revone), then you can use the European RUU to downgrade and restore fully to 100% stock.

[SOLVED] Deleted ROM/OS off phone by mistake :eek:!!!! HELP!

So I have done this so many times in the past playing with my HTC AMAZE 4G, to which i thought having some fun with my HTC ONE would be easy enough. But without a SD card.. i feel SOL.
I have been scouring the forums for possible fixes to no solution...
Currently I have the phone unlocked with "tampered" on the top.
My boot loader reads:
M7_UL PVT SHIP S-ON
HBOOT-1.56.0000
RADIO-4A.24.3263.09
OpenDSP-v32.120.274.0909
OS-4.19.531.10
Feb 3 2014,18:42:45.0
For all that is holy, i cannot get this thing to recognize ADB in console. I have been using Hasoon2000's AIO tool, which i used in the past on this phone and my priors.. but when I was in TWRP accidentally deleted my OS..? Everything I have tried has failed.
I am running Windows 8.1 which shouldn't be an issue with my Hboot version, so I am wondering what possible solutions there may be to get this fixed and finally get Cyanogen on this phone!
I have tried using the HTC recovery to go back to stock but i get errors when using the .zip i found which was supposed to be the RUU from the .exe HTC has out and yes i re-locked the phone for this. In terms of anything i think if i were able to get adb working i might be able to send CM11 to my phone directory and "recover" to that?
Thanks in advance!
EDIT: When i tried using the RUU zip i get this in my cmd.
sending 'zip' (227216 KB)...
OKAY [ 12.212s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 37.092s
I also ran Getvar and got this... Some people said it would help to have this info on some other threads....
C:\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.24.3263.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.531.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4161mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
mtywe said:
EDIT: When i tried using the RUU zip i get this in my cmd.
sending 'zip' (227216 KB)...
OKAY [ 12.212s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 37.092s
Click to expand...
Click to collapse
That's not an RUU, and there is no ruu 4.19.531.10 or higher as far as i know.
so do this: http://forum.xda-developers.com/showthread.php?t=2228274&page=3
mtywe said:
So I have done this so many times in the past playing with my HTC AMAZE 4G, to which i thought having some fun with my HTC ONE would be easy enough. But without a SD card.. i feel SOL.
I have been scouring the forums for possible fixes to no solution...
Currently I have the phone unlocked with "tampered" on the top.
My boot loader reads:
M7_UL PVT SHIP S-ON
HBOOT-1.56.0000
RADIO-4A.24.3263.09
OpenDSP-v32.120.274.0909
OS-4.19.531.10
Feb 3 2014,18:42:45.0
For all that is holy, i cannot get this thing to recognize ADB in console. I have been using Hasoon2000's AIO tool, which i used in the past on this phone and my priors.. but when I was in TWRP accidentally deleted my OS..? Everything I have tried has failed.
I am running Windows 8.1 which shouldn't be an issue with my Hboot version, so I am wondering what possible solutions there may be to get this fixed and finally get Cyanogen on this phone!
I have tried using the HTC recovery to go back to stock but i get errors when using the .zip i found which was supposed to be the RUU from the .exe HTC has out and yes i re-locked the phone for this. In terms of anything i think if i were able to get adb working i might be able to send CM11 to my phone directory and "recover" to that?
Thanks in advance!
EDIT: When i tried using the RUU zip i get this in my cmd.
sending 'zip' (227216 KB)...
OKAY [ 12.212s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 37.092s
I also ran Getvar and got this... Some people said it would help to have this info on some other threads....
C:\android-sdk\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.24.3263.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.531.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4161mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.078s
Click to expand...
Click to collapse
Boot your phone in custom recovery
adb push name_of_rom.zip /sdcard/
Wait for the file to transfer (5-10 min)
Install your rom
Sent from my HTC One using XDA Free mobile app
alray said:
Boot your phone in custom recovery
adb push name_of_rom.zip /sdcard/
Wait for the file to transfer (5-10 min)
Install your rom
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
so i run adb push and it shows the time and bytes of the file... but does not show up in my /sdcard/
i also tried sideloading... and got this error, once it finishes loading it over:E:Error executing updator binary in zip '/data/ updating partition details
i think i ran into the same issue two years back when I tried getting pure CM on my last phone...
any ideas?
mtywe said:
i also tried sideloading... and got this error, once it finishes loading it over:E:Error executing updator binary in zip '/data/ updating partition details
i think i ran into the same issue two years back when I tried getting pure CM on my last phone...
any ideas?
Click to expand...
Click to collapse
what is your twrp version?
you might also read this: http://wiki.cyanogenmod.org/w/Install_CM_for_m7
alray said:
what is your twrp version?
you might also read this:
Click to expand...
Click to collapse
OLD.... updating to the newest version now.
alray said:
what is your twrp version?
you might also read this: ]
Click to expand...
Click to collapse
Looks like we have a success!
I tried using the sideloader first which failed but adb push did the trick.
Thanks for the help!
mtywe said:
Looks like we have a success!
I tried using the sideloader first which failed but adb push did the trick.
Thanks for the help!
Click to expand...
Click to collapse
:good:
can you edit your thread title to add [Solved] ?

Im without OS

Im without Os.
(bootloader) version: 0.5
(bootloader) version-bootloader:
(bootloader) version-baseband: 4
(bootloader) version-cpld: None
(bootloader) version-microp: Non
(bootloader) version-main: 5.16.
(bootloader) version-misc: PVT S
(bootloader) serialno: SH36LW901
(bootloader) imei: 3578640560898
(bootloader) meid: 0000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-806
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: goo
(bootloader) battery-voltage: 42
(bootloader) partition-layout: G
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.103s
I tried everything. (i think so)
C:\Users\Orbeet\Desktop\HTC\adb>fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1206124 KB)...
OKAY [ 56.016s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 99 unknown fail)
finished. total time: 56.282s
Or
C:\Users\Orbeet\Desktop\HTC\adb>fastboot flash zip Guru_Reset_M7_2.24.161.1.zip
target reported max download size of 1515692032 bytes
sending 'zip' (1128558 KB)...
OKAY [ 52.967s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 69.887s
Please Help
orbeet said:
Im without Os.
(bootloader) version: 0.5
(bootloader) version-bootloader:
(bootloader) version-baseband: 4
(bootloader) version-cpld: None
(bootloader) version-microp: Non
(bootloader) version-main: 5.16.
(bootloader) version-misc: PVT S
(bootloader) meid: 0000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-806
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: goo
(bootloader) battery-voltage: 42
(bootloader) partition-layout: G
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.103s
I tried everything. (i think so)
C:\Users\Orbeet\Desktop\HTC\adb>fastboot flash zip firmware.zip
target reported max download size of 1514139648 bytes
sending 'zip' (1206124 KB)...
OKAY [ 56.016s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 99 unknown fail)
finished. total time: 56.282s
Or
C:\Users\Orbeet\Desktop\HTC\adb>fastboot flash zip Guru_Reset_M7_2.24.161.1.zip
target reported max download size of 1515692032 bytes
sending 'zip' (1128558 KB)...
OKAY [ 52.967s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 69.887s
Please Help
Click to expand...
Click to collapse
remove your IMEI and serialno from your getvar all.
repost your getvar all correctly so we can see all the info: S-???? 5.16.???????
what firmware.zip are you using (link) and why? you don't need to flash firmware to get an OS on your phone...
fastboot flash zip Guru_Reset_M7_2.24.161.1.zip ---> this can not be flashed this way, must be flashed from a custom recovery, however it also looks like its not the right version. You getvar: 5.16.??? ---> and you are trying to flash a 2.24
You'll probably have to flash a custom rom
orbeet said:
Im without Os.
Please Help
Click to expand...
Click to collapse
Remove the imei and serialno from your getvar all. Also, you have cutoff some important information on the getvar all, i.e., version bootloader, version main. Why don't you think you have an OS? What was the firmware version you were trying to install?
I think your are trying to install the older versions of your phone and that is why it is failing. You are S-ON so you can only install the same or higher versions of OS and firmware.
alray said:
remove your IMEI and serialno from your getvar all.
repost your getvar all correctly so we can see all the info: S-???? 5.16.???????
what firmware.zip are you using (link) and why? you don't need to flash firmware to get an OS on your phone...
fastboot flash zip Guru_Reset_M7_2.24.161.1.zip ---> this can not be flashed this way, must be flashed from a custom recovery, however it also looks like its not the right version. You getvar: 5.16.??? ---> and you are trying to flash a 2.24
You'll probably have to flash a custom rom
Click to expand...
Click to collapse
1. How to do point 1? (remove IMEI and serialno) ?? i dont get it?
2. I dont know how to do this correctly
3. I tried lots of and no one match (around 5) i had searched "radio 4T.27.3218.14"
4. i can not enter my phone from windows. Win7 see only removable disk but its blank.
Photo
orbeet said:
1. How to do point 1? (remove IMEI and serialno) ?? i dont get it? Go to your first post and choose Edit then remove the imei and serial number
2. I dont know how to do this correctly In the command window with your fastboot getvar all... choose select all then copy
3. I tried lots of and no one match (around 5) i had searched "radio 4T.27.3218.14" Radio has nothing to do with it your OS is listed in the screen shot you posted
4. i can not enter my phone from windows. Win7 see only removable disk but its blank. You can only access your phone in windows when it's booted to the OS... you don't have (you say)
Click to expand...
Click to collapse
Try these instructions
Unlock the bootloader at HTCDEV
then from fastboot USB
Flash recovery TWRP 2.6.3.3
http://techerrata.com/browse/twrp2/m7
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
then sideload this Rom to your phone
Guru_Reset_M7_5.11.401.10-TeHashX.zip
http://www.androidfilehost.com/?fid=23501681358543706
TWRP / Advanced / ADB Sideload - swipe to sideload
From PC adb / fastboot folder
you use
adb sideload name-of-rom.zip
make sure the rom is in the same folder as adb / fastboot
Click to expand...
Click to collapse
one more image.
Iv done everything U say and nothing.
??!
Is this all?
People, please help me.
orbeet said:
1. How to do point 1? (remove IMEI and serialno) ?? i dont get it?
2. I dont know how to do this correctly
3. I tried lots of and no one match (around 5) i had searched "radio 4T.27.3218.14"
4. i can not enter my phone from windows. Win7 see only removable disk but its blank.
Click to expand...
Click to collapse
edit your 1st post and remove the EMEI line and the SERIALNO line, these are sensitive number you don't want to share
repost it again and make sure to copy/paste all the content
(bootloader) version: 0.5
(bootloader) version-bootloader: ???????????
(bootloader) version-baseband: 4 ?????????????
(bootloader) version-cpld: None
(bootloader) version-microp: Non
(bootloader) version-main: 5.16.???????????
(bootloader) version-misc: PVT S????????????
(bootloader) serialno: remove!
(bootloader) imei: remove!
(bootloader) meid: 0000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-806
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP102
(bootloader) battery-status: goo
(bootloader) battery-voltage: 42
(bootloader) partition-layout: G
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.103s
Click to expand...
Click to collapse
if you want pple to reply to your post, then quote them or they will not be notified of your post.
try adb push instead of adb sideload
Code:
adb push Guru_Reset_M7_5.11.401.10-TeHashX.zip /sdcard/
then when the file is transferred (wait 5-10 min) install from twrp
orbeet said:
Is this all?
People, please help me.
Click to expand...
Click to collapse
First, hard reboot pressing the power and volume down buttons until you see the bootloader and then scroll through the options to hit "REBOOT" not "REBOOT BOOTLOADER" you'll probably boot into your rom after a couple of minutes but thats not a fix, it's just a way to use your phone for now.
Having no OS means you probably tried to flash a custom firmware or downgrade your FW but you can only do that while S-OFF
OR you where using a different kind of recovery like multirom or an old clockworkmod recovery or something, give us a little bit more info on what you where doing before you "lost" your OS and what recovery, what ROM and what you where hoping to accomplish just so we can see what went wrong. It's best when you need to do something to read the guide your using from top to bottom twice, most guides go through multiple posts not just the first to point out areas you might run into problems and things to avoid. I recently had a similar problem trying to remove multirom and reverting to stock, I was flashing the 1.57 FW with TWRP but after flashing ARHD 71.1 it still gave me "no OS installed", I reverted to stock using the RUU.zip install method with all partitions and FW and ROM to complete stock.

No OS, Relocked Bootloader, Tempered, S-ON.

Hi
In past few days, i wanted to root my HTC One m7. I did it with some of the tutorials from YT or your site. I did some mess i think. Now when i try to turn on my device, i only get HTC logo and that's it. I can get into recovery mode , where i get this :
,,TEMPERED
RELOCKED
Security Warning
S-on
Hboot 1.61
OS 7.19.401.51."
What can i do to make my device working again? Please help me. I tryied to fix this in couple ways, for example , downloaded RUU from htc site. Little diffrent version ,,7.17..." and open the exe file. But when i trying to open it, nothing works.
Other way was that i try command ,,fastboot flash .... zip" but i get message ,,load_file: could not allocate 1606550528 bytes error: cannot load 'ruu.zip': Not enough space. "
babel007 said:
Hi
In past few days, i wanted to root my HTC One m7. I did it with some of the tutorials from YT or your site. I did some mess i think. Now when i try to turn on my device, i only get HTC logo and that's it. I can get into recovery mode , where i get this :
,,TEMPERED
RELOCKED
Security Warning
S-on
Hboot 1.61
OS 7.19.401.51."
What can i do to make my device working again? Please help me. I tryied to fix this in couple ways, for example , downloaded RUU from htc site. Little diffrent version ,,7.17..." and open the exe file. But when i trying to open it, nothing works.
Other way was that i try command ,,fastboot flash .... zip" but i get message ,,load_file: could not allocate 1606550528 bytes error: cannot load 'ruu.zip': Not enough space. "
Click to expand...
Click to collapse
flash the 7.19.401.51 RUU. You'll find the file in the general section (see the ruu collection thread in the sticky threads).
RUU at post #2 of that thread, instructions how to flash at post #1 (don't forget to use the fastboot version specified in that post).
NEED PC
This is the link to the RUU. Install the file on PC (it is a big file) and connect your phone and run it.
Should return you to Lollipop 5.0.2 with Sense 6.
Download the right one for your variant:
htc.com/us/support/htc-one/news/ (Unlocked/Developer Edition)
htc.com/us/support/htc-one-t-mobile/news/
htc.com/us/support/htc-one-sprint/news/
htc.com/us/support/htc-one-verizon/news/
htc.com/us/support/htc-one-att/news/
pinnydiaj said:
NEED PC
This is the link to the RUU. Install the file on PC (it is a big file) and connect your phone and run it.
Should return you to Lollipop 5.0.2 with Sense 6.
Download the right one for your variant:
htc.com/us/support/htc-one/news/ (Unlocked/Developer Edition) x.xx.1540.x ---> Wrong base
htc.com/us/support/htc-one-t-mobile/news/ x.xx.531.x ----> Wrong base
htc.com/us/support/htc-one-sprint/news/ x.xx.651.x ---> Wrong base and wrong phone variant (M7_WLS)
htc.com/us/support/htc-one-verizon/news/ x.xx.605.x ----> Wrong base and wrong phone variant (M7_WLV)
htc.com/us/support/htc-one-att/news/ x.xx.502.x ----> Wrong base
Click to expand...
Click to collapse
Sorry but none of the above files will work on OP's phone. His phone is running 7.19.401.51 which is the latest version for the x.xx.401.x base (WWE Europe). His phone is S-ON so he can only flash a RUU that is the exact same (or newer) version than what is already installed on the phone. So 7.19.401.51 is the only one he can use since its the latest one...
However, thanks for links, they might be helpful for someone else :good:
Maybe wrong thread, but no one has a week to go through everything to find my topic. Sorry but this is what came up for my search.
m7, s-on but accepting and working with other carrier sims (installed diff carrier sim but no prompt for code).
Will I be able to root with s-on?
M9 battery crapped out (along with usb data comm and functionality), so going back to the 3 year older m7.
Is this the same company that came up with the Desire HD?!? geeeees! And they wonder why ppl buy chinese!
squidstings said:
Maybe wrong thread, but no one has a week to go through everything to find my topic. Sorry but this is what came up for my search.
m7, s-on but accepting and working with other carrier sims (installed diff carrier sim but no prompt for code).
Will I be able to root with s-on?
M9 battery crapped out (along with usb data comm and functionality), so going back to the 3 year older m7.
Is this the same company that came up with the Desire HD?!? geeeees! And they wonder why ppl buy chinese!
Click to expand...
Click to collapse
You need an unlcoked bootloader in order to root your rom. S-ON is fine (unless you have the verizon m7 variant).
Hi,
I need help. I have HTC One M7. Stuck on HTC logo, S-On, bootloader unlocked, TWRP recovery. Cid is HTC__E11. I need flash stock rom, because I deleted system in TWRP.
some info about HTC:
Code:
fastboot getvar all
(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.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35WW904679
(bootloader) imei: 354436058617737
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4071mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s
I tried flash firmware from https://pakfones.com/htc-m7-official-lollipop-ruu-collection/ and choose
Code:
N07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2 2_Radio_4T.35.3218.16_10.33
Q.1718.01L_release_430964_signed.zip
via fastboot but unsuccessfully.
Code:
fastboot-win>htc_fastboot flash zip PN07IMG.zip
sending 'zip'... (50280 KB) OKAY
sending time = 2.849 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAIL99 unknown fail
FAILED (remote: 99 unknown fail)
Execution time is 9(s)
Can someone help me? Thank you
nulda said:
Hi,
I need help. I have HTC One M7. Stuck on HTC logo, S-On, bootloader unlocked, TWRP recovery. Cid is HTC__E11. I need flash stock rom, because I deleted system in TWRP.
some info about HTC:
Code:
fastboot getvar all
(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.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35WW904679
(bootloader) imei: 354436058617737
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4071mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: RUU
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s
I tried flash firmware from https://pakfones.com/htc-m7-official-lollipop-ruu-collection/ and choose
Code:
N07IMG_M7_UL_L50_SENSE60_MR_HTC_Europe_7.19.401.2 2_Radio_4T.35.3218.16_10.33
Q.1718.01L_release_430964_signed.zip
via fastboot but unsuccessfully.
Code:
fastboot-win>htc_fastboot flash zip PN07IMG.zip
sending 'zip'... (50280 KB) OKAY
sending time = 2.849 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAIL99 unknown fail
FAILED (remote: 99 unknown fail)
Execution time is 9(s)
Can someone help me? Thank you
Click to expand...
Click to collapse
Since your phone is S-ON and running 7.19.401.51, you can only use the 7.19.401.51 RUU not the 7.19.401.2 (this one is a downgrade).
https://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
And you must use htc_fastboot.exe to flash the RUU, not fastboot.exe
Thanks, but...
I downloaded file
Code:
7.19.401.51 Signed https://www.androidfilehost.com/?fid=24369303960689843
and result is
Code:
htc_fastboot flash zip PN07IMG.zip
sending 'zip'... (50228 KB) OKAY
sending time = 2.917 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAIL99 unknown fail
FAILED (remote: 99 unknown fail)
Execution time is 9(s)
I did:
htc_fastboot oem rebootRUU
htc_fastboot flash zip filename.zip
... archive is broken. I cant unzip it
nulda said:
Thanks, but...
I downloaded file
Code:
7.19.401.51 Signed https://www.androidfilehost.com/?fid=24369303960689843
and result is
Code:
htc_fastboot flash zip PN07IMG.zip
sending 'zip'... (50228 KB) OKAY
sending time = 2.917 secs
writing 'zip'... (bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAIL99 unknown fail
FAILED (remote: 99 unknown fail)
Execution time is 9(s)
I did:
htc_fastboot oem rebootRUU
htc_fastboot flash zip filename.zip
... archive is broken. I cant unzip it
Click to expand...
Click to collapse
Sorry, forgot to mention that since your bootlooder is S-ON you must relock it (only s-off bootloader can flash a RUU when unlocked)
So do
Code:
htc_fastboot oem lock
before doing
Code:
htc_fastboot oem rebootRUU
htc_fastboot flash zip filename.zip
the archive isn't broken, this is an encrypted file and it can't be unzipped.
---------- Post added at 10:43 AM ---------- Previous post was at 10:42 AM ----------
You can re-unlock the BL after the RUU if you want to reflash twrp.
Super, it is ok. Now is phone boot to android.
And now, when I want install any else firmware, because there is only 5 languages, I must do S-OFF, change CID and upload via fastboot firmware for CID? Or can I change CID without S-ON?
nulda said:
Super, it is ok. Now is phone boot to android.
And now, when I want install any else firmware, because there is only 5 languages, I must do S-OFF, change CID and upload via fastboot firmware for CID? Or can I change CID without S-ON?
Click to expand...
Click to collapse
Changing CID requires S-OFF but there is a trick to add languages without flashing another RUU. This will requires at least TWRP installed on your phone and that you perform a factory reset after the trick is done.
What language/country do you need?
TWRP is installed. I need czech language. Maybe phone has simlock, because when I put another sim, so I cant connect to gsm because signal isnt.
edit: I did factory reset via TWRP, but nothing.
nulda said:
TWRP is installed. I need czech language. Maybe phone has simlock, because when I put another sim, so I cant connect to gsm because signal isnt.
edit: I did factory reset via TWRP, but nothing.
Click to expand...
Click to collapse
boot in twrp, copy /system/customize/cid/default.xml to your computer. open default.xml with notepad++ and add cs_CZ in the "total_list" string. Create a new string with this value: <item type="boolean" name="cs_CZ">yes</item>
save the file and push back to /system/customize/cid/default.xml using twrp.
factory reset the phone and check if the czech language is available.
If your phone was sim-locked you should be prompted to enter the sim unlock code when the OS boot.
I copied default.xml, opened it and check it. Default.xml is in attachment. Strings what you wrote me are in file. So I dont understand it.
nulda said:
I copied default.xml, opened it and check it. Default.xml is in attachment. Strings what you wrote me are in file. So I dont understand it.
Click to expand...
Click to collapse
Ok I read on another thread that you can change the default.xml file name to match your cid and it should enables all languages listed in default.xml
1- pull /system/customize/cid/default.xml on your pc
2- rename default.xml to HTC__E11.xml
3- Using twrp push HTC__E11.xml to /system/customize/cid/HTC__E11.xml this will overwrite the already existing HTC__E11.xml file that only contains a few language option.
4- reset phone
Dont forget that it must be done from twrp unless you have a custom kernel with "/system write protection" disabled. If not all change made to any file in /system will be reverted back to stock after reboot.
Thank you. Now is all ok.
I have a problem with my htc one m7_u
After 2 years I turned on my phone and saw it was in Htc logo and started looping
After that I used maximusHD_53 to start flashing, but same problem again
Finally i used my old TWRP backup to restore, but it didn’t work and same problem.
I already have TWRP v3.2.1 recovery
This is details about my phone in Hboot
***TAMPERED***
***UNLOCKED***
M7_U PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4A.25.3263.21
OpenDSP-v32.120.274.0909
OS-
eMMC-boot 2048MB
Mar 3 2014,21:11:29.0
I can’t see my CID number, It seems to have disappeared
And this is my fastboot getvar
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH42MW901632
(bootloader) imei: 354435055915581
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4257mV
(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
Can anyone help me how to fix my phone?
Sorry for my bad language

HTC One M7 - Bricked?

Hey guys.
I was wondering if anyone could take some time and help figure out what's wrong with my Htc one!
So my new phone broke and so i went back to my One that i haven't used in ages.
Anyways it was alredy rooted with S-Off and first thing i was trying todo was to install TWRP and a new rom.
After i installed twrp and rebooted the phone and upon start i sent me directly in to the "power off + Volume down" menu and i tried to enter Recovery.
All i get is "Active cmdline overflow! (2169 Bytes)" then nothing more.
So i tried some fastboot commands and this is what i get from
Fastboot devices ҟÀü«/륑-1ý}ËÙ fastboot
I reckoning something is wrong here because the name has never shown like this before.
If i try adb devices i get nothing.
So i started to belive that maybe the cable was ****ed and now i almost tried 7 diffrent cables and all of them is giving me the same message.
I tried a diffrent computer, i tried in windows 10 and now im in Ubuntu 16.04 and still cant get adb to show the device.
This is what i get from "fastboot getvar all"
HTML:
sudo fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN SHIP S-OFF
(bootloader) serialno: ҟ���/륑-1�}��
(bootloader) imei: ****************** <---------- CHANGED THIS ONE TO STARS!
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: �
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3776mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-01dc707e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
Anyway the (bootloader) serialno: ҟ���/륑-1�}�� and (bootloader) modelid: � dosent look good right ?
Well i did follow this guide "https://forum.xda-developers.com/showthread.php?t=2739126" and i can install twrp and everything but i cant enter it and the adb commands further in the guide dosent work because adb wont list the phone.
I also tried:
HTML:
sudo fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.039s]
finished. total time: 0.039s
sudo fastboot flash zip 1.29.401.12_hboot_1.44.zip
target reported max download size of 1514139648 bytes
sending 'zip' (501 KB)...
OKAY [ 0.243s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 0.644s
And there's something wrong with the mode id
What is my option, is the phone ****ed or is it possible to fix it ?
Thanks in advanced!
Have you tried to flash stock recovery or RUU?
JB_ said:
Hey guys.
I was wondering if anyone could take some time and help figure out what's wrong with my Htc one!
So my new phone broke and so i went back to my One that i haven't used in ages.
Anyways it was alredy rooted with S-Off and first thing i was trying todo was to install TWRP and a new rom.
After i installed twrp and rebooted the phone and upon start i sent me directly in to the "power off + Volume down" menu and i tried to enter Recovery.
All i get is "Active cmdline overflow! (2169 Bytes)" then nothing more.
So i tried some fastboot commands and this is what i get from
Fastboot devices ҟÀü«/륑-1ý}ËÙ fastboot
I reckoning something is wrong here because the name has never shown like this before.
If i try adb devices i get nothing.
So i started to belive that maybe the cable was ****ed and now i almost tried 7 diffrent cables and all of them is giving me the same message.
I tried a diffrent computer, i tried in windows 10 and now im in Ubuntu 16.04 and still cant get adb to show the device.
This is what i get from "fastboot getvar all"
HTML:
sudo fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: UNKNOWN SHIP S-OFF
(bootloader) serialno: ҟ���/륑-1�}��
(bootloader) imei: ****************** <---------- CHANGED THIS ONE TO STARS!
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: �
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 3776mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-01dc707e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.061s
Anyway the (bootloader) serialno: ҟ���/륑-1�}�� and (bootloader) modelid: � dosent look good right ?
Well i did follow this guide "https://forum.xda-developers.com/showthread.php?t=2739126" and i can install twrp and everything but i cant enter it and the adb commands further in the guide dosent work because adb wont list the phone.
I also tried:
HTML:
sudo fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.039s]
finished. total time: 0.039s
sudo fastboot flash zip 1.29.401.12_hboot_1.44.zip
target reported max download size of 1514139648 bytes
sending 'zip' (501 KB)...
OKAY [ 0.243s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 0.644s
And there's something wrong with the mode id
What is my option, is the phone ****ed or is it possible to fix it ?
Thanks in advanced!
Click to expand...
Click to collapse
What roms did you flashed (post a link) ? Active cmdline overflow is caused by a corrupted misc partition, most of the time because the user flashed a rom for another device than the m7. During the installation, the updater script of that rom flash images to wrong partitions (since all phone models have a different partition layout). Some partitions are unique to each m7 and if they get corrupted, a simple ruu flash will not solve your problem.
Your adb problem is most likely a driver issue. Make sure you have the latest drivers from HTC (those that are bundled with HTCSync) and try again. The only way out of this is to make p19 healthy again by following that guide you linked (if it was caused by an incompatible rom flash...waiting for your link).
Btw do not attempt to downgrade to hboot 1.44 if you're using windows 8/10 or you'll also loose fastboot connectivity.
alray said:
What roms did you flashed (post a link) ? Active cmdline overflow is caused by a corrupted misc partition, most of the time because the user flashed a rom for another device than the m7. During the installation, the updater script of that rom flash images to wrong partitions (since all phone models have a different partition layout). Some partitions are unique to each m7 and if they get corrupted, a simple ruu flash will not solve your problem.
Your adb problem is most likely a driver issue. Make sure you have the latest drivers from HTC (those that are bundled with HTCSync) and try again. The only way out of this is to make p19 healthy again by following that guide you linked (if it was caused by an incompatible rom flash...waiting for your link).
Btw do not attempt to downgrade to hboot 1.44 if you're using windows 8/10 or you'll also loose fastboot connectivity.
Click to expand...
Click to collapse
Well as I want to remember it I don't think I have flashed a rom yet, I never got that far I just tried to flash twrp 2.8.4.0.
Do i even need drivers in Ubuntu ? I was under the influence that I didn't need any.
JIMSHERIKO said:
Have you tried to flash stock recovery or RUU?
Click to expand...
Click to collapse
Well if I understand it right when I try to flash a RUU it just says unknown modelid and I think because it's corrupted or something. :/
JB_ said:
Do i even need drivers in Ubuntu ? I was under the influence that I didn't need any.
Click to expand...
Click to collapse
No you don't, only on windows, sorry. ADB should work fine from twrp and no drivers required on ubuntu, adb will not work from the bootloader.
alray said:
No you don't, only on windows, sorry. ADB should work fine from twrp and no drivers required on ubuntu, adb will not work from the bootloader.
Click to expand...
Click to collapse
Ah so i need to get TWRP up and running for adb to work then.
Well looks like i got my awnser then. Thank you for your time!

Categories

Resources