Database Develop

[Q] Failed 'manual' OTA Update

Hey guys
I have the international and unlocked version of the HTC ONE. Since the 4.3 Update for the European Models (I am from Europe) has released a while ago an I did not recieve the update i tried to install it on my own (mistake)
I followed the instructions of this website (link in the txt file). I installed the x.xx.401.x WWE version which seemed to be the right one i picked the 3.62.401.1 firmware and flashed it via fastboot. After doing that my phone won't start up anymore.
I tried to install the stock rom via RUU but it does not work.
I can still reach the bootloader but can't flash a new rom because my phone is not rooted.
Yesterday i spent 6 hours looking for a solution but nothing seems to work.
Does anyone know a solution?
Obviously I am a noob. So if You need any more information please tell me.
Thanks in advance

Fabivons said:
Hey guys
I have the international and unlocked version of the HTC ONE. Since the 4.3 Update for the European Models (I am from Europe) has released a while ago an I did not recieve the update i tried to install it on my own (mistake)
I followed the instructions of this website (link in the txt file). I installed the x.xx.401.x WWE version which seemed to be the right one i picked the 3.62.401.1 firmware and flashed it via fastboot. After doing that my phone won't start up anymore.
I tried to install the stock rom via RUU but it does not work.
I can still reach the bootloader but can't flash a new rom because my phone is not rooted.
Yesterday i spent 6 hours looking for a solution but nothing seems to work.
Does anyone know a solution?
Obviously I am a noob. So if You need any more information please tell me.
Thanks in advance
Click to expand...
Click to collapse
1- can you post a "fastboot getvar all" (remove IMEI and s/n before posting)
2- confirm if your bootloader is unlocked
I'll take a look later

thank you for the fast response! My bootloader is unlocked.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.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: xxx
(bootloader) imei: xxx
(bootloader) meid: xxx
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4172mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0

Fabivons said:
thank you for the fast response! My bootloader is unlocked.
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
Click to expand...
Click to collapse
You can download and flash this Guru Reset ROM: http://www.htc1guru.com/dld/guru_reset_m7_3-62-401-1-zip/ (flash just like a custom ROM, in recovery)
If you want to receive OTAs later then you need to select "stock recovery" in the installer.
You may want to consider S-Off. (But really up to you)
Let me know if you need more help, and hit the Thanks button if I've helped

It did not work. Here is what i did:
(cmd)
C:\Users\xxx\Desktop\OneDrivers_Fastboot\Fastboot>fastboot flash zip Guru_Res
et_M7_3.62.401.1.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1176263 KB)...
OKAY [ 45.755s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 45.778s
after that i tried it this way:
C:\Users\xxx\Desktop\OneDrivers_Fastboot\Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.041s]
finished. total time: 0.042s
C:\Users\xxx\Desktop\OneDrivers_Fastboot\Fastboot>fastboot flash zip Guru_Res
et_M7_3.62.401.1.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1176263 KB)...
OKAY [ 45.751s]
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: 63.147s
when i try to enter the recovery mode it shows a phone withe a red triangle on the screen..

Fabivons said:
It did not work. Here is what i did:
(cmd)
C:\Users\xxx\Desktop\OneDrivers_Fastboot\Fastboot>fastboot flash zip Guru_Res
et_M7_3.62.401.1.zip
when i try to enter the recovery mode it shows a phone withe a red triangle on the screen..
Click to expand...
Click to collapse
no mate, standard custom recovery flash, so first, you need to get yourself a custom recovery from one of the threads on xda, either CWM or TWRP, CWM is here: http://forum.xda-developers.com/showthread.php?t=2173863 don't have the one for TWRP readily available, sorry.
Once you download the recovery____.img place it in your adb folder, then reboot to bootloader/FASTBOOT USB, then in the command prompt:
fastboot erase cache
fastboot flash recovery <name of recovery>.img
fastboot erase cache
fastboot reboot-bootloader
-> enter RECOVERY (this should show you the custom recovery)
now push the Guru ROM to your phone:
adb push Guru_Reset_M7_3.62.401.1.zip /data/media/ <- this will take 5 to 10 minutes
in recovery, select "install zip" -> "choose zip" -> select Guru_Reset_M7_3.62.401.1.zip
go through the installer, here's an EXAMPLE select the options you want (stock recovery & root, whichever suites you): http://forum.xda-developers.com/showpost.php?p=47085377&postcount=44

thanks for your help!
It worked!!! I have a second birthday now
thank your very very much!

Fabivons said:
thanks for your help!
It worked!!! I have a second birthday now
thank your very very much!
Click to expand...
Click to collapse
Congrats mate :good::good:
Could you edit the main thread title to include [SOLVED], thanks.

i want to but i kind of don't know how ^^

Fabivons said:
i want to but i kind of don't know how ^^
Click to expand...
Click to collapse
oh, easy, go to your first post click EDIT then at the bottom of the edit window click GO ADVANCED, that will show you the main thread title which you can edit

[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

[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] ?

Htc One M7 Bricked

Please i need your help i have an M7 bricked
Only the Htc Logo i have the access to bootloader and recovery
(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: FA38HW90xxxx
(bootloader) imei: 3578640xxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4177mV
(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.056s
Please i need your help the give life for my phone and tnx in advnce

i need your help
i need help plz or the correct stock ruu for this phone

Try this.

too large
sending 'zip' (1641983 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.004s

help please
i used an RUU.exe all is ok but phone stuck in bootloop

GIOZOLO22 said:
sending 'zip' (1641983 KB)...
FAILED (remote: 02 data length is too large)
finished. total time: 0.004s
Click to expand...
Click to collapse
Try with newest adb and htc_fastboot.exe
Commands:
fastboot oem rebootRUU
fastboot flash zip ruu.zip (where ruu.zip is downloaded zip, you can drag in command)
And bootloader needs to be locked if you're S-ON.

lucyr03 said:
Try with newest adb and htc_fastboot.exe
Commands:
fastboot oem rebootRUU
fastboot flash zip ruu.zip (where ruu.zip is downloaded zip, you can drag in command)
And bootloader needs to be locked if you're S-ON.
Click to expand...
Click to collapse
the same probleme image too large and phone stuck on bootloop

GIOZOLO22 said:
the same probleme image too large and phone stuck on bootloop
Click to expand...
Click to collapse
Try this TWRP Backup: click
Unlock bootloader and flash twrp from fastboot.

lucyr03 said:
Try this TWRP Backup: click
Unlock bootloader and flash twrp from fastboot.
Click to expand...
Click to collapse
hi how are you am sorry for not responding how to make this flash via twrp ???? i do make a restore ???

GIOZOLO22 said:
hi how are you am sorry for not responding how to make this flash via twrp ???? i do make a restore ???
Click to expand...
Click to collapse
Yes, and read the second post

lucyr03 said:
Yes, and read the second post[/QUOTE
restore failed i believe the emmc
Click to expand...
Click to collapse

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!