Database Develop

[Q] fastboot mode:show "?????? fastboot"

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

[Q] Help! Bricked my GPE during 4.4 OTA update!

Guys, I was asking about this on another thread about GPE OTA URL, but since I'm running into trouble, maybe I should post here too. After an OTA update to 4.4, the phone is now in bootloop. I tried to do RUU but I can't since my phone is S-ON. I tried to follow thread of revone, but I can't connect to my phone through adb. I also tried factory reset through recovery. I can see the Welcome screen for a second and it boots again.
Now the phone is bricked. Is there anything I can do to solve it?
My Phone:
- Real HTC ONE GPE from google play store
- TAMPERED, RELOCKED(I tried to unlock it through steps from htcdev. I am not see the disclaimer screen now after I could load the Unlock_code.bin to the device already)
- HBOOT 1.54, S-ON
- Stock recovery.

felix1212 said:
Guys, I was asking about this on another thread about GPE OTA URL, but since I'm running into trouble, maybe I should post here too. After an OTA update to 4.4, the phone is now in bootloop. I tried to do RUU but I can't since my phone is S-ON. I tried to follow thread of revone, but I can't connect to my phone through adb. I also tried factory reset through recovery. I can see the Welcome screen for a second and it boots again.
Now the phone is bricked. Is there anything I can do to solve it?
My Phone:
- Real HTC ONE GPE from google play store
- TAMPERED, RELOCKED(I tried to unlock it through steps from htcdev. I am not see the disclaimer screen now after I could load the Unlock_code.bin to the device already)
- HBOOT 1.54, S-ON
- Stock recovery.
Click to expand...
Click to collapse
try finding a full GPE RUU and try to get your phone back. with relocked bootloader and no S-off and HTCdev no working, this is your only option. Don't know where the GPE RUUs are otherwise I would have linked.
so search very well, and make sure it's for your phone (CID & MID) and try it. and don't rush into things!!!
if you have questions, better to ask and wait for a response, before you have a paperweight.

What was the error when you ran the 4.4 non-rooted RUU from: http://forum.xda-developers.com/showthread.php?t=2358781 ?
Remember you have to run the fastboot flash ruu command twice as per that link.

Same Here
Almost exactly the same thing happened to me, my GPe is locked though. I tried all the 4.4, 4.3, and 4.2.2 RUU and get FAILED (remote: 12 signature verify fail).
I tried unlocking bootloader using "fastboot oem unlock" and get this error:
(bootloader) [PG_ERROR] htc_pg_part_traverse(839):
(bootloader) invalid traverse range
(bootloader) [PG_ERROR] htc_pg_part_read(1029):
(bootloader) htc_pg_part_traverse failed
(bootloader) [DISPLAY_ERR] sp_custom partition: unlock_disp_buf.img_buf r
(bootloader) ead error!
(bootloader) [DISPLAY_ERR] Can not load custom splash!
(bootloader) Loading custom splash failed!
OKAY [ 0.543s]
finished. total time: 0.543s
Click to expand...
Click to collapse
I tried unlocking using Unlock_code.bin and it shows the following message which looks fine:
sending 'unlocktoken' (0 KB)...
OKAY [ 0.141s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.003s]
Click to expand...
Click to collapse
But the bootloader is still locked.
Super desperate right now...
btw, my getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.58.1700.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HTxxxxxxxxxx
(bootloader) imei: 3xxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4183mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse

Just tried 4.4 RUU, and I got below error message.
C:\HTC\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk
\platform-tools>fastboot flash zip RUU-HTC_One_GE-4.4-3.58.1700.5.zip
target reported max download size of 1526722560 bytes
sending 'zip' (506183 KB)...
OKAY [ 23.387s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 68.634s

Can you flash a custom recovery? If so, can your phone boot into it?
fastboot flash ruu is failing due to you being S-On.

SaHiLzZ said:
Can you flash a custom recovery? If so, can your phone boot into it?
fastboot flash ruu is failing due to you being S-On.
Click to expand...
Click to collapse
I'm checking on that too. May I know if I'm okay to do so if my bootloader is relocked?

Unlock it.

SaHiLzZ said:
Unlock it.
Click to expand...
Click to collapse
Tried. As I said before, if I follow instructions from htcdev, somehow I'm not getting the disclaimer screen after I flash the Unlock_code.bin. I also tried fastbook oem unlock but no luck. Couldn't find other ways to unlock the bootloader.
May I know if there's any way I can unlock it?

Fastboot oem unlock

I'm have the same issue as others...
Currently my bootloader says i have OS-3.58.1700.5, but no OS will load, and I am on a neverending loop....
Currently my system is locked. (I stupidly followed HTC's advice for updating and relocked my device).
And i no longer have twrp - once again following advice of others and putting on the stock bootloader.
I do have the stock bootloader, but i cannot install anything, and I cannot get past the google start screen (just cycles between Google and black).
I tried re-unlocking, both with the HTCdev tool - which looked like it was successful, but still reads "relocked".
And the fastboot oem unlock gives me the following error:
(bootloader) [PG_ERROR] htc_pg_part_traverse(839):
(bootloader) invalid traverse range
(bootloader) [PG_ERROR] htc_pg_part_read(1029):
(bootloader) htc_pg_part_traverse failed
(bootloader) [DISPLAY_ERR] sp_custom partition: unlock_disp_buf.img_buf r
(bootloader) ead error!
(bootloader) [DISPLAY_ERR] Can not load custom splash!
(bootloader) Loading custom splash failed!
OKAY [ 0.538s]
finished. total time: 0.538s
any attempts to flash a stock ROM using fastboot commands gives me the following error:
target reported max download size of 1526722560 bytes
sending 'zip' (428998 KB)...
OKAY [ 18.008s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 51.867s
I should've just kept 4.3.
I was so desperate I contacted HTC - but my phone says "TAMPERED" and "RELOCKED", so they would definitely have issues up-keeping the warranty.
The rest of the info in my bootloader reads:
M7_UL PVT SHIP S-ON RH
HBOOT-1.54.0000
RADIO-4T.21.3218.21
OpenDSP-v32.120.274.0909
OS-3.58.1700.5
eMMC-boot 2048MB
I would simply be happy to get to where i was before on GPe 4.3, and hopefully with twrp re-installed so i can recover my last backup! Please help, if you can!!!

SaHiLzZ said:
Fastboot oem unlock
Click to expand...
Click to collapse
Thanks for your reply. As I stated earlier, I can't unlock it with fastboot. Here is the error.
C:\HTC\adt-bundle-windows-x86_64-20131030\adt-bundle-windows-x86_64-20131030\sdk
\platform-tools>fastboot oem unlock
...
(bootloader) [PG_ERROR] htc_pg_part_traverse(839):
(bootloader) invalid traverse range
(bootloader) [PG_ERROR] htc_pg_part_read(1029):
(bootloader) htc_pg_part_traverse failed
(bootloader) [DISPLAY_ERR] sp_custom partition: unlock_disp_buf.img_buf r
(bootloader) ead error!
(bootloader) [DISPLAY_ERR] Can not load custom splash!
(bootloader) Loading custom splash failed!
OKAY [ 0.539s]
finished. total time: 0.539s

fastboot boot recovery-clockwork-touch-6.0.4.5-m7ul.img
download this recovery and put it in the fastboot folder and use that fastboot command, if it boot into recovery u then can install a s-on compatible rom that does not bootloop. Credit to nkk71.

SleepingDragon said:
fastboot boot recovery-clockwork-touch-6.0.4.5-m7ul.img
download this recovery and put it in the fastboot folder and use that fastboot command, if it boot into recovery u then can install a s-on compatible rom that does not bootloop. Credit to nkk71.
Click to expand...
Click to collapse
Thanks for your reply!! I went through topics by nkk71. However, I can't find threads about s-on compatible ROM to download. May I know where I can find it? Also, is there any instruction about installing that through clockworkmod recovery?
Really thanks again!

felix1212 said:
Thanks for your reply!! I went through topics by nkk71. However, I can't find threads about s-on compatible ROM to download. May I know where I can find it? Also, is there any instruction about installing that through clockworkmod recovery?
Really thanks again!
Click to expand...
Click to collapse
BTW, thanks for naming me, but if you wanna get my attention use @ as in @nkk71, (like @felix1212) that would show me a mention and I would see it.
So what's your situation, (seems a few cross-posts, so don't wanna mix thinks up, can you give a quick summary, i understand your s-on, but what's your "fastboot getver all" (remove IMEI and s/n), and where did you get stuck.

I'm going through a similar issue right now. I have a HTC one that I had converted to a GPe by changing the CID etc. All was well until the 4.4 OTA update bricked my device. It shows the "GOOGLE" screen, then black then sometimes the screen again, then some error message.
I found a collection of HTC one RUU's here http://forum.xda-developers.com/showthread.php?t=2428276&highlight=4+4
And a little guide on how to flash RUU's here. http://forum.xda-developers.com/showthread.php?t=2251800
Hopefully there is some information in there that will help you out. Keep in mind that when flashing an RUU you will lose all your data. It basically becomes a new phone. But you should be able to do it, no matter what state your phone is in. so long as you have fastboot access.

I appear to be in a similar situation:
- S-ON Google Play Edition HTC One
- Took KitKat 4.4 OTA and ended up in reboot loop
- Cleared all caches + data partition from CWM. Didn't help.
- Decided to try to flash from RUU
- Read that I needed to re-lock my bootloader in order to flash an RUU and get out of this mess
- relocked using fastboot oem lock
- Tried to install several RUUs: 4.4 rooted, 4.4 stock, 4.3 stock.
All of them fail like this:
Code:
[email protected] jb $ fastboot flash zip jb.zip
target reported max download size of 1526722560 bytes
sending 'zip' (388627 KB)...
OKAY [ 17.914s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 53.637s
Tried to re-unlock. That fails like this:
Code:
[email protected] Downloads $ fastboot oem unlock
...
(bootloader) [PG_ERROR] htc_pg_part_traverse(839):
(bootloader) invalid traverse range
(bootloader) [PG_ERROR] htc_pg_part_read(1029):
(bootloader) htc_pg_part_traverse failed
(bootloader) [DISPLAY_ERR] sp_custom partition: unlock_disp_buf.img_buf r
(bootloader) ead error!
(bootloader) [DISPLAY_ERR] Can not load custom splash!
(bootloader) Loading custom splash failed!
OKAY [ 0.537s]
finished. total time: 0.537s
Here's my getvars all:
Code:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: REDACTED
(bootloader) imei: REDACTED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4053mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Some thoughts:
- Being s-off would bypass the signature error during RUU
- I can't s-off in 1.54 without having a bootable phone
- I might be able to get a bootable phone by installing a 4.3 .zip file using CWM or flashing system.img using fastboot, but I can't do those things with a locked bootloader, and can't re-unlock the bootloader due to the above failures.
Open questions:
- Why do the RUU's fail signature validation? They are being presented as stock RUU's.
- Is there an .exe RUU for the GPE HTC ONE?
- Why doesn't 'fastboot oem unlock' work anymore? I thought that was the method for GPE HTC ONEs
This happened to my phone and also my girlfriend's, which are identical phones with identical OS/update situations. I haven't re-locked her bootloader, so there may be more options there, but I wanted to avoid messing with her phone further until I exhaust every path available on mine.

I had the same problem. I found 4.3 stock ROM for Google Play Edition HTC One, used TWRP to push the ROM to storage then from TWRP recovery installed the 4.3 ROM. It worked then updated to JWR66Y.H1 and now am waiting for 4.4 OTA.
Sent from my HTC One using XDA Premium 4 mobile app

tmanonyx said:
I had the same problem. I found 4.3 stock ROM for Google Play Edition HTC One, used TWRP to push the ROM to storage then from TWRP recovery installed the 4.3 ROM. It worked then updated to JWR66Y.H1 and now am waiting for 4.4 OTA.
Click to expand...
Click to collapse
Thanks, I used your method with CWM and M7_UL_JB43_STOCK_UI_S_Google_WWE_3.06.1700.10.zip and got the gf's phone up and running again on jb.
Unfortunately, my phone was the guinea pig earlier on and it's now stuck with a re-locked bootloader and stock recovery .
Looks like my next step is figuring out how to re-unlock the bootloader. Very frustrating. Unlocking/locking are supposed to be easily reversible on google edition devices.

Good, it took me literally 36 hours to get mine up and running.
Sent from my HTC One using XDA Premium 4 mobile app

stucked in HTC logo

good day can you please help me with my problem. i was trying to a flash a custom ROM then then my M7 was stucked in the boot logo.
my hboot version 1.57.000 and flagged as ***TAMPERED*** and ***RELOCKED***. i have S-ON. and here's my getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.707.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35AW907688
(bootloader) imei: *********180157
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 4319mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
your help will be very much appreciated.
thanks and more power

akoskiko99 said:
good day can you please help me with my problem. i was trying to a flash a custom ROM then then my M7 was stucked in the boot logo.
my hboot version 1.57.000 and flagged as ***TAMPERED*** and ***RELOCKED***. i have S-ON. and here's my getvar
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.22.3263.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.13.707.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA35AW907688
(bootloader) imei: *********180157
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: HTC__044
(bootloader) battery-status: good
(bootloader) battery-voltage: 4319mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
your help will be very much appreciated.
thanks and more power
Click to expand...
Click to collapse
why is your bootloader relocked ? Unlock it if you want to flash and use Roms

clsA said:
why is your bootloader relocked ? Unlock it if you want to flash and use Roms
Click to expand...
Click to collapse
i've already unlocked my M7 using HTCDev but still i've encounted and error
c:\fastboot>fastboot flash zip c:\fastboot\firmware.zip
sending 'zip' (433840 KB)...
OKAY [ 18.603s]
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: 18.840s

akoskiko99 said:
i've already unlocked my M7 using HTCDev but still i've encounted and error
c:\fastboot>fastboot flash zip c:\fastboot\firmware.zip
sending 'zip' (433840 KB)...
OKAY [ 18.603s]
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: 18.840s
Click to expand...
Click to collapse
Now why are you flashing firmware ? the bootloader has to be relocked to flash firmware with s-on
You said you were flashing a rom / needs bootloader unlocked / custom recovery installed
flashing firmware / RUU needs bootloader relocked

clsA said:
Now why are you flashing firmware ? the bootloader has to be relocked to flash firmware with s-on
You said you were flashing a rom / needs bootloader unlocked / custom recovery installed
flashing firmware / RUU needs bootloader relocked
Click to expand...
Click to collapse
Looks to me mate like hes renamed the rom to firmware.zip and trying to flash it like firmware, hence the failed to parse Android info.
You can't flash it like that, you need to put the rom you downloaded on your internal storage and flash / install it from within twrp recovery.

clsA said:
why is your bootloader relocked ? Unlock it if you want to flash and use Roms
Click to expand...
Click to collapse
Seanie280672 said:
Looks to me mate like hes renamed the rom to firmware.zip and trying to flash it like firmware, hence the failed to parse Android info.
You can't flash it like that, you need to put the rom you downloaded on your internal storage and flash / install it from within twrp recovery.
Click to expand...
Click to collapse
how can i can put the stock rom in the internal storage if my phone stucked in the boot logo?

clsA said:
Now why are you flashing firmware ? the bootloader has to be relocked to flash firmware with s-on
You said you were flashing a rom / needs bootloader unlocked / custom recovery installed
flashing firmware / RUU needs bootloader relocked
Click to expand...
Click to collapse
hi clsA,
sorry if i confused, um so confused myself. again my apologies.
by this time, i've already unlocked the HBOOT using HTCdev
i've already installed TWRP to flash ROM
but the problem now is how can i transfer a stock rom to my M7 if it is stucked in the boot logo?
i hope i made myself clear to you.
thanks

akoskiko99 said:
hi clsA,
sorry if i confused, um so confused myself. again my apologies.
by this time, i've already unlocked the HBOOT using HTCdev
i've already installed TWRP to flash ROM
but the problem now is how can i transfer a stock rom to my M7 if it is stucked in the boot logo?
i hope i made myself clear to you.
thanks
Click to expand...
Click to collapse
TWRP 2.8.5.0 gives many options you can mount storage as mtp
usb otg
Sideload rom
Adb push

yatindroid said:
TWRP 2.8.5.0 gives many options you can mount storage as mtp
usb otg
Sideload rom
Adb push
Click to expand...
Click to collapse
i did it! man!! i was so close in giving up!!!...
thanks to all you who spent their time replying on my post.
clsA
Seanie
yatindroid
i forget the others. sorry.
Thank you very much!

M7 only boots into bootloader

Was trying to put my HTC One M7 back to stock to give to my mother-inlaw. I was planning on running an RUU on it, so I relocked the bootloader and ever since I can't seem to do anything with it. It will only boot into the bootloader. I can't seem to unlock it using htc dev now either. any ideas? Any help is appreciated.
This is some info.
C:\adb>fastboot getvar -all
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-microp: None
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei:
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4301mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
-all: Done!
finished. total time: 16.711s

When I try to unlock it, this is what I see in my CMD prompt.
C:\adb>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.004s]
finished. total time: 0.147s
But nothing ever comes up on my phone like it shows in the instructions.

HuMpS 97 DoHc said:
When I try to unlock it, this is what I see in my CMD prompt.
C:\adb>fastboot flash unlocktoken Unlock_code.bin
sending 'unlocktoken' (0 KB)...
OKAY [ 0.142s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.004s]
finished. total time: 0.147s
But nothing ever comes up on my phone like it shows in the instructions.
Click to expand...
Click to collapse
what is your original cid number, because 11111111 wont be the original, you cant unlock the bootloader as you locked it with a custom recovery on there, and now the only way to get stock recovery on there or flash an RUU is to know your original cid or version main.

Seanie280672 said:
what is your original cid number, because 11111111 wont be the original, you cant unlock the bootloader as you locked it with a custom recovery on there, and now the only way to get stock recovery on there or flash an RUU is to know your original cid or version main.
Click to expand...
Click to collapse
BM___001 would be my cid.

I've changed my CID back to stock. Now what did I need to do? I can't seem to find an RUU for Bell mobility anywhere.
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT346W903917
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4188mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.051s

When I try to apply a Bell RUU from this thread http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944 This is the error message I get. Any ideas or help???
C:\adb>htc_fastboot reboot-bootloader
rebooting into bootloader... OKAY
Execution time is 40(ms)
C:\adb>htc_fastboot oem rebootRUU
... (bootloader) Start Verify: 3
OKAY
Execution time is 44(ms)
C:\adb>htc_fastboot flash zip RUU.zip
error: preprocess_file : Cannot open file RUU.zip
C:\adb>htc_fastboot flash zip RUU.zip
sending 'zip'... (43286 KB) OKAY
sending time = 2.972 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...
FAILED (status read failed (Too many links))
Execution time is 9(s)
C:\adb>htc_fastboot reboot-bootloader
rebooting into bootloader... FAILED (status read failed (Unknown error))
Execution time is 5(s)

HuMpS 97 DoHc said:
When I try to apply a Bell RUU from this thread http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944 This is the error message I get. Any ideas or help???
C:\adb>htc_fastboot reboot-bootloader
rebooting into bootloader... OKAY
Execution time is 40(ms)
C:\adb>htc_fastboot oem rebootRUU
... (bootloader) Start Verify: 3
OKAY
Execution time is 44(ms)
C:\adb>htc_fastboot flash zip RUU.zip
error: preprocess_file : Cannot open file RUU.zip
C:\adb>htc_fastboot flash zip RUU.zip
sending 'zip'... (43286 KB) OKAY
sending time = 2.972 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...
FAILED (status read failed (Too many links))
Execution time is 9(s)
C:\adb>htc_fastboot reboot-bootloader
rebooting into bootloader... FAILED (status read failed (Unknown error))
Execution time is 5(s)
Click to expand...
Click to collapse
Remove your IMEI number from your above posts! Never post your IMEI.
How did you managed to change your CID with the phone being S-ON ?!!
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) modelid: PN0712000
(bootloader) cidnum: 11111111
Click to expand...
Click to collapse
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
Click to expand...
Click to collapse
You can't use a 7.xx.xxx.x ruu unless your firmware is at least 6.xx.xxx.x (you're not)

alray said:
Remove your IMEI number from your above posts! Never post your IMEI.
How did you managed to change your CID with the phone being S-ON ?!!
You can't use a 7.xx.xxx.x ruu unless your firmware is at least 6.xx.xxx.x (you're not)
Click to expand...
Click to collapse
I removed my imei, thanks. I honestly thought this phone was S-OFF but I hadn't actually used it for much in over a year since I have a m8. Do you have any ideas of what I can do? my bootloader is now relocked and I can't seem to unlock it.

So i was able to flash a signed firmware onto my phone which for my carrier Bell Mobility, its 3.23.666.1. But now where can I go? i still can't seem to unlock the bootloader. any ideas?
my getvar info now.
C:\adb>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.23.666.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3747mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-a6a74fd020
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.234s

Anyone with any ideas??? Please.

HuMpS 97 DoHc said:
Anyone with any ideas??? Please.
Click to expand...
Click to collapse
sorry I struggle to get on here sometimes during the week as my work takes over my life.
could you post a link to the 3.xx.666.x firmware you flashed please.

thats the firmware I used. https://www.dropbox.com/s/m1mha8jx36ceoe5/firmware.zip?dl=0
alray said:
Remove your IMEI number from your above posts! Never post your IMEI.
How did you managed to change your CID with the phone being S-ON ?!!
You can't use a 7.xx.xxx.x ruu unless your firmware is at least 6.xx.xxx.x (you're not)
Click to expand...
Click to collapse
Seanie280672 said:
sorry I struggle to get on here sometimes during the week as my work takes over my life.
could you post a link to the 3.xx.666.x firmware you flashed please.
Click to expand...
Click to collapse

HuMpS 97 DoHc said:
thats the firmware I used. https://www.dropbox.com/s/m1mha8jx36ceoe5/firmware.zip?dl=0
Click to expand...
Click to collapse
I'm unable to check it just yet, but it's just a zip file, so make sure it contains recovery.img, also when you flash it, you will need to flash it twice as the first time is just a pre update, after that, check that you have stock recovery by selecting recovery from the bootlpader screen, you should be presented with a red exclamation mark, volume up and power to get the menu, select factory reset.
Now boot to the bootloader and get a new unlock token from HTC dev website, and try and unlock your bootloader, once done, you can then flash twrp recovery, and flash your stock backup, will post the link later, then reflash stock recovery and update, or try and get s-off with rumrunner before updating.

htc one m7 stuck

please help me
my htc is stuck
-tampered+unlocked but s-on
-recovery twrp-3.0.0-2-m7
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35WW910255
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN071****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4256mV
(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

benn182 said:
please help me
my htc is stuck
-tampered+unlocked but s-on
-recovery twrp-3.0.0-2-m7
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35WW910255
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN071****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4256mV
(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
Click to expand...
Click to collapse
Any background info? What happened? Why is your phone now s-on (a quick look at your "getvar all" and its obvious that it was s-off before).
What is your goal, you want to install a custom rom? Stock rom?

alray said:
Any background info? What happened? Why is your phone now s-on (a quick look at your "getvar all" and its obvious that it was s-off before).
What is your goal, you want to install a custom rom? Stock rom?
Click to expand...
Click to collapse
Yes, before s-off but now s-on
I need stock rom but ruu failed flash
Please help me

benn182 said:
Yes, before s-off but now s-on
Click to expand...
Click to collapse
So why it's s-on now and what happened to your phone?
I need stock rom but ruu failed flash
Click to expand...
Click to collapse
What RUU version was it?

alray said:
So why it's s-on now and what happened to your phone?
What RUU version was it?
Click to expand...
Click to collapse
I do not know how many versions

As @alray pointed out there's need for more information. Why did you go S-ON leaving CID/MID SuperCID and SuperMID. And please try to remember which RUU you tried to flash, as this is ofimpotance as well. And finally what does stuck mean: not booting, stuck on old firmware and so on. We'd try to help if possible and all needed informations are present.

I see 2 possibilities to repair your mysteriously bricked phone
1- Flash an old custom rom (a close to stock rom like ARHD) and achieve S-OFF again, preferrably with Revone or Moonshine since you're on hboot 1.44. Once s-off again, flash the 7.19.401.2 firmware then flash the 7.19.401.52 RUU.
OR
2- Flash back the stock 3.62.401.1 recovery, relock your bootloader, flash the 3.62.401.1 firmware to fix hboot (it should be 1.55 when on firmware 3.62.401.1) and flash the 4.19.401.9 RUU. From there install all remaining ota updates until you are on the latest version/7.19.401.52
Code:
fastboot flash recovery 3.62.401.1recovery.img
fastboot erase cache
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip 3.62.401.1firmware.zip
fastboot flash zip 3.62.401.1firmware.zip
fastboot reboot-bootloader
Flash the 4.19.401.9 ruu.exe
Take all ota updates

alray said:
I see 2 possibilities to repair your mysteriously bricked phone
1- Flash an old custom rom (a close to stock rom like ARHD) and achieve S-OFF again, preferrably with Revone or Moonshine since you're on hboot 1.44. Once s-off again, flash the 7.19.401.2 firmware then flash the 7.19.401.52 RUU.
OR
2- Flash back the stock 3.62.401.1 recovery, relock your bootloader, flash the 3.62.401.1 firmware to fix hboot (it should be 1.55 when on firmware 3.62.401.1) and flash the 4.19.401.9 RUU. From there install all remaining ota updates until you are on the latest version/7.19.401.52
Code:
fastboot flash recovery 3.62.401.1recovery.img
fastboot erase cache
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip 3.62.401.1firmware.zip
fastboot flash zip 3.62.401.1firmware.zip
fastboot reboot-bootloader
Flash the 4.19.401.9 ruu.exe
Take all ota updates
Click to expand...
Click to collapse
thanks I will try point 2

sending 'zip' (46317 KB)...
OKAY [ 2.908s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 3.158s

benn182 said:
thanks I will try point 2
Click to expand...
Click to collapse
sending 'zip' (46317 KB)...
OKAY [ 2.908s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 99 unknown fail)
finished. total time: 3.158s

@alray
What there will be a selection of Indonesian and signals can be used in indoinesia again?

benn182 said:
@alray
What there will be a selection of Indonesian and signals can be used in indoinesia again?
Click to expand...
Click to collapse
I don't really understand your question... The m7 is compatible with these frequencies:
HSPA/WCDMA :
850/900/1 900/2 100 MHz
GSM/GPRS/EDGE :
850/900/1 800/1 900 MHz
LTE:
EU: 800/1800/2600 MHz
Check with your carrier if its compatible.

benn182 said:
thanks I will try point 2
Click to expand...
Click to collapse
alray said:
I don't really understand your question... The m7 is compatible with these frequencies:
HSPA/WCDMA :
850/900/1 900/2 100 MHz
GSM/GPRS/EDGE :
850/900/1 800/1 900 MHz
LTE:
EU: 800/1800/2600 MHz
Check with your carrier if its compatible.
Click to expand...
Click to collapse
thank you master
this successful
:good: