[Q] hboot 1.44.00 and can't move forward nor backwards - One (M7) Q&A, Help & Troubleshooting

Hi everyone
Been on Cyanogenmod 11-20140424-NIGHTLY-M7 for far too long and wanted to either upgrade Cyanogenmod or, better yet, move to Viper. I'm somewhat skilled with Windows and Linux, but I can't seem getting things to work.
What I've got:
HTC One M7 (unbranded, bought in Switzerland)
Unlocked S-ON
hboot: 1.44.0000
M7-UL PVT SHIP S-ON RH
RADIO-4A.14.3250.13
OpenDSP-v26-120-274-0202
CID: HTC_102
It's rooted and got CWM ROM-Manager installed
Notebook with Windows 8.1, USB 3.0 all around
What I've tried so far:
Getting S-OFF
- Did not work. revone throws an ERROR=1 at me when I try to ./revone -P. I've tried like a hundred times, with su and all.
Then I tried to relock and get an RUU on it:
- Relocking did not work. Neither with revone (./revone -l or -r is successful on the CLI, but does nothing, i.e. still says *** UNLOCKED *** in the bootloader), nor with fastboot...
- ... as fastboot does not work, either. Tried different drivers and all, but fastboot always says < waiting for device >. So fastboot oem lock achieved nothing, either.
Then I just tried to install an RUU to get to JB and hboot 1.55 to then continue with rumrunner. This got stuck at some boot-image showing the HTC logo and the .exe cancelled.
Is USB3.0 breaking my neck here or do I have any other options to get to ViperOne?
Thanks in advance...

From what i've read in here many times, hboot 1.44 isn't compatiable with windows 8. 1. You need to use a windows 7 machine.

dorsetqpr said:
From what i've read in here many times, hboot 1.44 isn't compatiable with windows 8. 1. You need to use a windows 7 machine.
Click to expand...
Click to collapse
Correct
Hoelli169 said:
Hi everyone
Been on Cyanogenmod 11-20140424-NIGHTLY-M7 for far too long and wanted to either upgrade Cyanogenmod or, better yet, move to Viper. I'm somewhat skilled with Windows and Linux, but I can't seem getting things to work.
What I've got:
HTC One M7 (unbranded, bought in Switzerland)
Unlocked S-ON
hboot: 1.44.0000
M7-UL PVT SHIP S-ON RH
RADIO-4A.14.3250.13
OpenDSP-v26-120-274-0202
CID: HTC_102
It's rooted and got CWM ROM-Manager installed
Notebook with Windows 8.1, USB 3.0 all around
What I've tried so far:
Getting S-OFF
- Did not work. revone throws an ERROR=1 at me when I try to ./revone -P. I've tried like a hundred times, with su and all.
Then I tried to relock and get an RUU on it:
- Relocking did not work. Neither with revone (./revone -l or -r is successful on the CLI, but does nothing, i.e. still says *** UNLOCKED *** in the bootloader), nor with fastboot...
- ... as fastboot does not work, either. Tried different drivers and all, but fastboot always says < waiting for device >. So fastboot oem lock achieved nothing, either.
Then I just tried to install an RUU to get to JB and hboot 1.55 to then continue with rumrunner. This got stuck at some boot-image showing the HTC logo and the .exe cancelled.
Is USB3.0 breaking my neck here or do I have any other options to get to ViperOne?
Thanks in advance...
Click to expand...
Click to collapse
Windows 8 and hboot 1.44 are not compatible. You should use Windows 7 or better still Linux (preferably ubuntu 32bit)
Sent from my M7 ARHD 84-Kitkat

OK, got my hands on a Linux notebook and managed the relock the bootloader. This led to only being able to boot into Bootloader, Recovery and ROM did always boot into Bootloader.
Then I tried to get a RUU with JB4.3 on the device to be able to run rumrunner on hboot 1.55.
#sudo fastboot flash zip RUU.zip
sending 'zip' (1065710 KB)...
OKAY [ 59.411s}
writing 'zip' ...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 171.238s
Now I unlocked the bootloader again to at least be able to boot into CYM again.
Meh, I'm kinda lost here. I feel confused about RUUs, CIDs, Nandroid Backups and where to go from here.
Any ideas?
Edit:*Here's the fastboot-info
(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__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4128mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Edit2:*OK, I'm stuck in the CYM*launcher. Really kinda lost now D:

Hoelli169 said:
OK, got my hands on a Linux notebook and managed the relock the bootloader. This led to only being able to boot into Bootloader, Recovery and ROM did always boot into Bootloader.
Then I tried to get a RUU with JB4.3 on the device to be able to run rumrunner on hboot 1.55.
#sudo fastboot flash zip RUU.zip
sending 'zip' (1065710 KB)...
OKAY [ 59.411s}
writing 'zip' ...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 171.238s
Now I unlocked the bootloader again to at least be able to boot into CYM again.
Meh, I'm kinda lost here. I feel confused about RUUs, CIDs, Nandroid Backups and where to go from here.
Any ideas?
Edit:*Here's the fastboot-info
(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__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4128mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
Edit2:*OK, I'm stuck in the CYM*launcher. Really kinda lost now D:
Click to expand...
Click to collapse
Download this recovery. http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
Put the file in your fastboot folder.
Download this Rom. Put the zip in your fastboot folder and rename it rom.zip
http://www.htc1guru.com/dld/guru_reset_m7_1-29-401-13-zip/
Flash the recovery with fastboot
Code:
fastboot erase cache
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot reboot-bootloader
Select recovery from the bootloader menu. While in TWRP recovery. Push the Rom. Type
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push us complete. Do a full wipe and install the Rom. During the install setup choose these options.
Stock recovery = yes
Stock radio = yes
Root = No
You will now have full stock Rom and recovery. Reboot the device and go to settings>about>Software Updates. Download and install the OTA update. Repeat process untill your on JB 3.xx.401.x firmware. Then use rumrunner to gain s-off. :good:
Sent from my M7 ARHD 84-Kitkat

Danny201281 said:
Download this recovery.
Put the file in your fastboot folder.
Download this Rom. Put the zip in your fastboot folder and rename it rom.zip
Flash the recovery with fastboot
Code:
fastboot erase cache
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot reboot-bootloader
Click to expand...
Click to collapse
Worked!
Select recovery from the bootloader menu. While in TWRP recovery. Push the Rom. Type
Code:
adb push rom.zip /sdcard
The command window will appear unresponsive until the push us complete. Do a full wipe and install the Rom. During the install setup choose these options.
Click to expand...
Click to collapse
This didn't work. While in TWRP, adb was not able to connect. Funnily enough, flashing TWRP*allowed me to boot into CYM again. Activated USB*Debugging and allowed the Host to connect, but still no luck in TWRP.
But since I*had access again I* just copied the Guru image over USB*to the Sdcard, booted back into TWRP*and installed the ROM*manually.
Stock recovery = yes
Stock radio = yes
Root = No
You will now have full stock Rom and recovery. Reboot the device and go to settings>about>Software Updates. Download and install the OTA update. Repeat process untill your on JB 3.xx.401.x firmware.
Click to expand...
Click to collapse
219486214 reboots later... JB*3.62.401.1, hooray!
Then use rumrunner to gain s-off. :good:
Click to expand...
Click to collapse
Another adventure... In the official instructions it says unlocked OR*rooted, so I*did not bother with rooting.
rumrunner then failed and damaged Recovery leading to not being able to boot into TWRP*and thus being unable to install SuperSu zip.
Had to reflash recovery, install SuperSu and run rumrunner again... Which again failed (becuase the screen was off, I did not see that ADB*Shell requested root).
After a couple of tries now it worked ^_^
Thanks a lot for your explanations.
Now I just have to find out how to get to Firmware 5.0.2 to install the latest ViperOne.
Edit:*When I try to run the OTA*update to 4.19.401.11 it just boots into Recovery

Hoelli169 said:
Worked!
This didn't work. While in TWRP, adb was not able to connect. Funnily enough, flashing TWRP*allowed me to boot into CYM again. Activated USB*Debugging and allowed the Host to connect, but still no luck in TWRP.
But since I*had access again I* just copied the Guru image over USB*to the Sdcard, booted back into TWRP*and installed the ROM*manually.
219486214 reboots later... JB*3.62.401.1, hooray!
Another adventure... In the official instructions it says unlocked OR*rooted, so I*did not bother with rooting.
rumrunner then failed and damaged Recovery leading to not being able to boot into TWRP*and thus being unable to install SuperSu zip.
Had to reflash recovery, install SuperSu and run rumrunner again... Which again failed (becuase the screen was off, I did not see that ADB*Shell requested root).
After a couple of tries now it worked ^_^
Thanks a lot for your explanations.
Now I just have to find out how to get to Firmware 5.0.2 to install the latest ViperOne.
Edit:*When I try to run the OTA*update to 4.19.401.11 it just boots into Recovery
Click to expand...
Click to collapse
You need stock rom and recovery to install OTA updates. You can just flash the rom again with stock recovery to take further OTAs.
But as your now s-off you can just flash the firmware manually. You don't need to re lock the bootloader again. That's only for s-on users.
You can download the rest of the firmware updates here https://www.androidfilehost.com/?w=files&flid=32777
You must flash at least one zip for each firmware version. I.e if your on 3.xx.401.x then you have to flash
4.xx.401.x
5.xx.401.x
6.xx.401.x
7.xx.401.x
Then you can flash twrp and install a lollipop rom. You should have the rom on the internal storage before you start as the device won't boot after flashing the firmware as it will replace the stock boot.img. So you will need to flash a rom before it will boot. :good:
Commands for flashing the firmware zip as follows.
Code:
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip "name-of-firmware".zip
fastboot flash zip "name-of-firmware".zip
fastboot reboot-bootloader
Flash TWRP, Install Rom, Done :good:
Sent from my SM-T230 using Tapatalk

Danny201281 said:
You need stock tom and recovery to install OTA updates. You can just flash the rom again with stock recovery to take further OTAs.
But as your now s-off you can just flash the firmware manually. You don't need to re lock the bootloader again. That's only for s-on users.
You can download the rest of the firmware updates here
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
I thought I had to adhere to some upgrade path when handling firmwares but if that's not the case I'll be happy to use the latest, thanks!

Hoelli169 said:
I thought I had to adhere to some upgrade path when handling firmwares but if that's not the case I'll be happy to use the latest, thanks!
Click to expand...
Click to collapse
See my edited post above. You can't just flash the latest firmware. It might work but there's a risk of bricking your phone if you skip firmware versions
Sent from my SM-T230 using Tapatalk

Danny201281 said:
See my edited post above. You can't just flash the latest firmware. It might work but there's a risk of bricking your phone if you skip firmware versions
Sent from my SM-T230 using Tapatalk
Click to expand...
Click to collapse
Ahh yes. Well, another interesting one going through the firmware updates. Going from 5.xx to 6.xx nearly killed my phone. Screen went black no matter how long I*pressed the power button and connecting through USB*mounted some strange folders on the device.
Luckily found Dexter's thread and his unbricking script solved the problem:
http://forum.xda-developers.com/showthread.php?t=2770684
Now ViperOne is updating, yay ^__^

Hoelli169 said:
Ahh yes. Well, another interesting one going through the firmware updates. Going from 5.xx to 6.xx nearly killed my phone. Screen went black no matter how long I*pressed the power button and connecting through USB*mounted some strange folders on the device.
Luckily found Dexter's thread and his unbricking script solved the problem:
http://forum.xda-developers.com/showthread.php?t=2770684
Now ViperOne is updating, yay ^__^
Click to expand...
Click to collapse
[emoji28] few!! Yeah firmware can be tricky. Glad you got it sorted though. Dexter's thread is a life saver. . Enjoy lollipop :good:
Sent from my SM-T230 using Tapatalk

Related

HTC one ....all of out sorts.

I feel like I have a unnique situation and am rather stressed about it. Causing me to not really be able to find answers on my own.
I have the M7 (international version gsm)
anyways like most or some I don't know...I want the latest and greatest rom. Thus being anything 4.4
I was coming from the latest Venom 4.3 rom
so I download the 4.4 rom (android revolution) I read that I needed the latest CWM ..so I checked to see if I had it ...and sure enough I did.
I flash the rom all seems fine but I get this weird..Do you want to fix root access or something after selecting reboot system in CWM so naturally I said yes. Away I went to what I thought was going to be booting into chocolately goodness...but no.
It just boot looped from the main boot HTC logo to it with booting recovery up top. When it boot into recovery it would show the little cwm gear and just go right back to the HTC logo (so not fully booting into recovery)
So I assumed I would still be able to get into fastboot. I was right, I can. so I pushed and flashed the latest TWRP however trying to boot into TWRP just warrants the same as CWM. I get the TeamWin logo and then right back to square one.
So then I decided I would just try to get it back to stock. Which according to the flashing guide on the rom page I was on meant I needed to relock my bootloader....So I did. with fastboot oem lock. And that is where I currently am. I can still fastboot. Just my bootloader is locked.
I just wanted to come here and post and look around for solutions before I tried and failed and messed up the phone even more.
fastboot erase cache
Should get you back into recovery.
Thank you. I think because I relocked the bootloader I lost twrp because after running that cmd I just get brought back to what I think is stock recovery (TAMPERED
RELOCKED FASTBOOT Menu) Where you can select fastboot reboot and reboot bootloader.
that's the fastboot menu, not recovery. stock recovery shows an error triangle.
Are you S-On or S-off ?
if you're s-on your best bet is to track down the RUU for your CID and then run it with your phone in fastboot mode. that will bring you back to stock.
fastboot getvar all
paste the results here (redact the imei and serial plz!)
leveliv said:
Thank you. I think because I relocked the bootloader I lost twrp because after running that cmd I just get brought back to what I think is stock recovery (TAMPERED
RELOCKED FASTBOOT Menu) Where you can select fastboot reboot and reboot bootloader.
Click to expand...
Click to collapse
ipfreelytech said:
that's the fastboot menu, not recovery. stock recovery shows an error triangle.
Are you S-On or S-off ?
if you're s-on your best bet is to track down the RUU for your CID and then run it with your phone in fastboot mode. that will bring you back to stock.
fastboot getvar all
paste the results here (redact the imei and serial plz!)
Click to expand...
Click to collapse
(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.631.17
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid:
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: low
(bootloader) battery-voltage: 3285mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status malformed (0 bytes))
finished. total time: 5.540s
seems I am S-ON. Good news is I am CID Rogers....I am with Tbaytel for the carrier which is powered by Rogers.
I found this RUU but I have no clue how to install it using Fastboot. I am on Ubuntu because my other OS is 8.1 and it broke fastboot apparently.
http://forum.xda-developers.com/showthread.php?t=2207874
Unlock bootloader, install recovery, erase cache, sideload a ROM and then install it.
Trying this now.
You can use my guide post #2, but start from a few steps down to tailor it to your needs or post in the thread..
Actually he really should run an RUU first. His mainver is WAY out of date! Too many people do just what you said and completely forget to pay attention to hboot versions and firmware versions.
I'm having a hard time finding a rogers RUU.
OP, here's a link to a stock nandroid that matches your mainver: http://bugsylawson.com/files/file/1857-m7-cwm-nandroid-backup-cid-roger001-12963117/
unlock your bootloader. Flash recovery. then restore that nandroid.
afterwards, you can use revone to s-off: http://forum.xda-developers.com/showthread.php?t=2314582
once your s-off. change your CID to super cid with fastboot oem writecid 11111111
you can run the 4.4 conversion RUU found here: http://forum.xda-developers.com/showthread.php?t=2358781
That will get you a properly converted GPE 4.4 that will recieve OTA updates [as long as you don't screw with /system and don't install a custom recovery]
BenPope said:
Unlock bootloader, install recovery, erase cache, sideload a ROM and then install it.
Click to expand...
Click to collapse
Maybe you don't read my guide, post is for Canadian devices on 1.44 hboot

[Solved] Bricked my One?

Hello,
i'm reading here for some weeks and this forum helped me much so far. Now I made a bad mistake while flashing the latest firmware on my One and it seems that I have bricked it.
What have I done?
I used ARHD 5.1 GE on my One with an older firmware. Before that I was using ARHD 4.1. Data of my phone:
(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-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4260mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I changed to SuperCID, before that I had VODAP102. Bootloader is relocked.
After flashing latest firmware, my sdcard got wiped. So I have no backups or any other data on my phone. The phone stops booting after the white screen with the "HTC" logo and shows a turquoise color with little stripes and nothing happens.
I tried to flash another firmware, as you can see in the phone's details. That worked, but changed nothing. I can't install a rom, because adb doesn't find my device, but fastboot does. I tried several HTC-drivers and cables and USB-slots. Nothing.
I read several How-To's but I got stuck with this. Even tried to install the 1.28.401.7 RUU, but that stops with Error 155. After first time that error occured I relocked my bootloader, but that didn't help. I can't push files to the phone, because adb doesn't work.
Now only one thing left: Asking you for help. I'm somewhat frustrated.
Peko
pekomane said:
Hello,
i'm reading here for some weeks and this forum helped me much so far. Now I made a bad mistake while flashing the latest firmware on my One and it seems that I have bricked it.
What have I done?
I used ARHD 5.1 GE on my One with an older firmware. Before that I was using ARHD 4.1. Data of my phone:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-main: 3.62.401.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0710000
(bootloader) cidnum: 11111111
I changed to SuperCID, before that I had VODAP102. Bootloader is relocked.
After flashing latest firmware, my sdcard got wiped. So I have no backups or any other data on my phone. The phone stops booting after the white screen with the "HTC" logo and shows a turquoise color with little stripes and nothing happens.
I tried to flash another firmware, as you can see in the phone's details. That worked, but changed nothing. I can't install a rom, because adb doesn't find my device, but fastboot does. I tried several HTC-drivers and cables and USB-slots. Nothing.
I read several How-To's but I got stuck with this. Even tried to install the 1.28.401.7 RUU, but that stops with Error 155. After first time that error occured I relocked my bootloader, but that didn't help. I can't push files to the phone, because adb doesn't work.
Now only one thing left: Asking you for help. I'm somewhat frustrated.
Peko
Click to expand...
Click to collapse
1- remove IMEI and s/n
2- install latest TWRP 2.6.3.3 (needed for 4.4 roms)
You need TWRP 2.6.3.3 (or later) for 4.4 roms, also if you are using a GPE rom, then you need to be s-off.
Download from here: http://techerrata.com/browse/twrp2/m7 don't use a download manager, it will fail; download normally and check MD5 to make sure file is not corrupt,
go to bootloader/FASTBOOT USB, and flash it:
fastboot flash openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
3- confirm adb working in TWRP now, and unlock using: http://forum.xda-developers.com/showthread.php?t=2475914 or "revone -u"
(you don't need to relock if you're s-off)
4- push, sideload, or OTG a ROM and install
5- error 155 occurs due to hboot 1.55+, you'll need to downgrade to 1.44 to run RUU
nkk71 said:
1- remove IMEI and s/n
2- install latest TWRP 2.6.3.3 (needed for 4.4 roms)
You need TWRP 2.6.3.3 (or later) for 4.4 roms, also if you are using a GPE rom, then you need to be s-off.
Download from here: http://techerrata.com/browse/twrp2/m7 don't use a download manager, it will fail; download normally and check MD5 to make sure file is not corrupt,
go to bootloader/FASTBOOT USB, and flash it:
fastboot flash openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
3- confirm adb working in TWRP now, and unlock using: http://forum.xda-developers.com/showthread.php?t=2475914 or "revone -u"
(you don't need to relock if you're s-off)
4- push, sideload, or OTG a ROM and install
5- error 155 occurs due to hboot 1.55+, you'll need to downgrade to 1.44 to run RUU
Click to expand...
Click to collapse
Step 1 already edited, right after posting...
Thanks for now, I have to try that when I am at home. I will post here, if it worked or not.
pekomane said:
Step 1 already edited, right after posting...
Thanks for now, I have to try that when I am at home. I will post here, if it worked or not.
Click to expand...
Click to collapse
no problem, IF you're gonna end up using RUU, you need to downgrade to this hboot: http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
then go to bootloader/FASTBOOT USB:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot flash zip 1.29.401.12_hboot_1.44.zip <- just in case the first one says "failed flush again"
fastboot reboot-bootloader
and run the RUU, should work fine.
nkk71 said:
no problem, IF you're gonna end up using RUU, you need to downgrade to this hboot: http://www.htc1guru.com/dld/1-29-401-12_hboot_1-44-zip/
then go to bootloader/FASTBOOT USB:
fastboot oem rebootRUU
fastboot flash zip 1.29.401.12_hboot_1.44.zip
fastboot flash zip 1.29.401.12_hboot_1.44.zip <- just in case the first one says "failed flush again"
fastboot reboot-bootloader
and run the RUU, should work fine.
Click to expand...
Click to collapse
Thanks for that, but using RUU was only one way I thought of to get my phone working again, because adb push and sideload don't work. If the way you mentioned in your first post works, then I will be absolutely fine without using RUU. Otherwise I will try the RUU option.
It worked! Thanks for your help! :good:
pekomane said:
It worked! Thanks for your help! :good:
Click to expand...
Click to collapse
Cool, if everything OK now, could you edit main thread title to include [SOLVED], Danke
Done.
By the way, it was the first option you posted that did the trick.
pekomane said:
Done.
By the way, it was the first option you posted that did the trick.
Click to expand...
Click to collapse
Sent from my HTC One using Tapatalk
Hello nkk7
S-OFF by rumrunners
bootloader 1.55
Version main 3.62.401.1
Cid HTC001
Mid pn0710000
I have tu use ruu to go back to stock can u please give me step by step guide in sequence pls
Pls
And there is no ruu for 3.62.401.1
Thus I will have downgrade that's why I am confused
Pls give me step by step info
shurahbil said:
Hello nkk7
S-OFF by rumrunners
bootloader 1.55
Version main 3.62.401.1
Cid HTC001
Mid pn0710000
I have tu use ruu to go back to stock can u please give me step by step guide in sequence pls
Pls
And there is no ruu for 3.62.401.1
Thus I will have downgrade that's why I am confused
Pls give me step by step info
Click to expand...
Click to collapse
follow my guide in my signature, there is a RUU.EXE available for CID: HTC__001 and MID: PN0710000 (so you can follow the RUU.EXE procedure)
in my opinion do NOT GO S-ON!!
nkk71 said:
follow my guide in my signature, there is a RUU.EXE available for CID: HTC__001 and MID: PN0710000 (so you can follow the RUU.EXE procedure)
in my opinion do NOT GO S-ON!!
Click to expand...
Click to collapse
Done ok ty
Why do not go s-on
Because you will close an avenue of troubleshooting if you are S-ON..

[Q] No android, no recovery, only bootloader... :(

Dear XDA,
I wanted to update my HTC One to Revolution HD. But there where some requirements before i could install that. Like updating the firmware and installing TWRP recovery. I needed to RELOCK my phone in order to update my firmware. So i did that using a tutorial. After that i only had to push the RUU and i would be back @ stock. And then i could flash Revolution HD to get 4.4!
But!... it went horribly wrong. As of right now, i can only enter fastboot. I cannot enter recovery, and there is no Android installed, so basically i'm screwed.
I do have some flashing experience and I'm not a complete newb, but this is out of my league. Perhaps there are some nice persons here that could help me out. I will try to summarise my phone settings:
My current settings in Fastboot:
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
May 3 2013,17:22:59:-1
CID: HTC_E11
MID: PN0710000
I have a nandroidback, but i can't get into recovery. I tried using ADB but my device is not recognised.... I get the feeling that S-ON needs to change to S-OFF. But if i use a toolkit (from Squabbi) i can't get my device S-OFF (device not recognised..).
As of right now, I'm sitting with my hands in my hair thinking i bricked my phone.
If someone could help me, you would save my day.
Lennard Breevaart.
ps: I'm using windows xp
len.asdf said:
Dear XDA,
I wanted to update my HTC One to Revolution HD. But there where some requirements before i could install that. Like updating the firmware and installing TWRP recovery. I needed to RELOCK my phone in order to update my firmware. So i did that using a tutorial. After that i only had to push the RUU and i would be back @ stock. And then i could flash Revolution HD to get 4.4!
But!... it went horribly wrong. As of right now, i can only enter fastboot. I cannot enter recovery, and there is no Android installed, so basically i'm screwed.
I do have some flashing experience and I'm not a complete newb, but this is out of my league. Perhaps there are some nice persons here that could help me out. I will try to summarise my phone settings:
My current settings in Fastboot:
M7_UL PVT SHIP S-ON RH
HBOOT-1.44.0000
RADIO-4A.14.3250.13
OpenDSP-v26.120.274.0202
eMMC-boot
May 3 2013,17:22:59:-1
CID: HTC_E11
MID: PN0710000
I have a nandroidback, but i can't get into recovery. I tried using ADB but my device is not recognised.... I get the feeling that S-ON needs to change to S-OFF. But if i use a toolkit (from Squabbi) i can't get my device S-OFF (device not recognised..).
As of right now, I'm sitting with my hands in my hair thinking i bricked my phone.
If someone could help me, you would save my day.
Lennard Breevaart.
ps: I'm using windows xp
Click to expand...
Click to collapse
is your bootloader unlocked ? do that first
what version of TWRP do you have (exact name)
do you have fastboot/adb on your pc and do you know how to use them ?
is your bootloader unlocked ? do that first
==> I think so, how can i check?
what version of TWRP do you have (exact name)
==> I have no recovery installed on my phone. But i have TWRP version 2.6.3.3. img on my computer, ready to push it to my phone (but it gives the error: device not found)
do you have fastboot/adb on your pc and do you know how to use them ?
==> I think i do. When i try to do adb shell in command window it replies with either device not found, or adb server out of date. Killing...
Thanks for replying btw!
len.asdf said:
is your bootloader unlocked ? do that first
==> I think so, how can i check?
what version of TWRP do you have (exact name)
==> I have no recovery installed on my phone. But i have TWRP version 2.6.3.3. img on my computer, ready to push it to my phone (but it gives the error: device not found)
do you have fastboot/adb on your pc and do you know how to use them ?
==> I think i do. When i try to do adb shell in command window it replies with either device not found, or adb server out of date. Killing...
Thanks for replying btw!
Click to expand...
Click to collapse
take these files
extract fastboot.zip to c:\fastboot
and install these drivers
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
MD5: e2a21d71954d4164c1a116abb926a363
and see if you can get:
fastboot getvar all
and post the results minus you serial no and IEMI
clsA said:
take these files
extract fastboot.zip to c:\fastboot
and install these drivers
http://www.mediafire.com/download/j55vk6qbbr6250c/HTCDriver_4.8.0.002.exe
MD5: e2a21d71954d4164c1a116abb926a363
and see if you can get:
fastboot getvar all
and post the results minus you serial no and IEMI
Click to expand...
Click to collapse
Thanks! This is what i did to get my results:
1. Downloaded both the fastboot.zip and the drivers (and installed ofcourse).
2. Opened a command window on c:\fastboot
3. typed: fastboot getvar all
Results:
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: -
(bootloader) imei: -
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4222mV
(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.047s
C:\fastboot>
len.asdf said:
Thanks! This is what i did to get my results:
1. Downloaded both the fastboot.zip and the drivers (and installed ofcourse).
2. Opened a command window on c:\fastboot
3. typed: fastboot getvar all
Results:
C:\fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.14.3250.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.29.401.16
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: -
(bootloader) imei: -
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 4222mV
(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.047s
C:\fastboot>
Click to expand...
Click to collapse
Your phone is basically still stock andriod version 4.1.2
(this is good you can s-off pretty easy)
what RUU were you going to flash ?
this is the version of recovery you need
http://techerrata.com/browse/twrp2/m7ul
download it and put it in your fastboot folder
then to flash it:
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img
fastboot erase cache
fastboot reboot-bootloader
now you can enter recovery correct ?
clsA said:
Your phone is basically still stock andriod version 4.1.2
(this is good you can s-off pretty easy)
what RUU were you going to flash ?
Click to expand...
Click to collapse
The RUU i tried was this one: RUU M7 U JB 50 HTC Europe 1.29.401.2 R Radio 4A.14.3250.13 10.33.1150.01 Release 311663 Signed 2 4
(from: http://forum.xda-developers.com/showthread.php?t=2428276)
While installing the RUU it gave me an an error that my CID and MID didn't match.
clsA said:
Your phone is basically still stock andriod version 4.1.2
(this is good you can s-off pretty easy)
what RUU were you going to flash ?
this is the version of recovery you need
http://techerrata.com/browse/twrp2/m7ul
download it and put it in your fastboot folder
Click to expand...
Click to collapse
Downloaded the recovery and put in the the fastboot folder
clsA said:
Your phone is basically still stock andriod version 4.1.2
(this is good you can s-off pretty easy)
what RUU were you going to flash ?
this is the version of recovery you need
http://techerrata.com/browse/twrp2/m7ul
download it and put it in your fastboot folder
then to flash it:
fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img
fastboot erase cache
fastboot reboot-bootloader
now you can enter recovery correct ?
Click to expand...
Click to collapse
While in ADB it gave this error:
C:\fastboot>fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img
sending 'recovery' (9840 KB)...
OKAY [ 1.297s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.891s
C:\fastboot>
edit: I cannot enter recovery yet. Just tried it
len.asdf said:
While in ADB it gave this error:
C:\fastboot>fastboot flash recovery openrecovery-twrp-2.6.3.4-m7ul.img
sending 'recovery' (9840 KB)...
OKAY [ 1.297s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.891s
C:\fastboot>
edit: I cannot enter recovery yet. Just tried it
Click to expand...
Click to collapse
your bootloader is still locked
clsA said:
your bootloader is still locked
Click to expand...
Click to collapse
I checked the md5 (f428caf36c9c337e2ae417fc10fbe165) with the file i downloaded. And it matches
len.asdf said:
I checked the md5 (f428caf36c9c337e2ae417fc10fbe165) with the file i downloaded. And it matches
Click to expand...
Click to collapse
yeah i realize that your bootloader is still locked
you need to go to htcdev and unlock again
then flash recovery
clsA said:
yeah i realize that your bootloader is still locked
you need to go to htcdev and unlock again
Click to expand...
Click to collapse
Ah ok, I will be doing that then . I will update this topic when i'm done.
len.asdf said:
Ah ok, I will be doing that then . I will update this topic when i'm done.
Click to expand...
Click to collapse
be warned unlocking will wipe the phone you'll be starting from nothing
clsA said:
be warned unlocking will wipe the phone you'll be starting from nothing
Click to expand...
Click to collapse
I know! But don't worry, it's the least of my problems now
Unlocked my phone, and gonna flash the recovery aswell!
But to not make the same mistake twice. What is the best way to update my phone to 4.4?
I wanted to install Revolution HD. But maybe you have a better alternative?
And how can i properly thank you? I mean, you just saved my ass!
len.asdf said:
And how can i properly thank you? I mean, you just saved my ass!
Click to expand...
Click to collapse
it's no problem
you should try and get s-off next
http://forum.xda-developers.com/showthread.php?t=2314582 - revone
ARHD is great .. I also use ViperOne
just use the sideload feature in twrp being your phone is wiped
Quote:
Set the device into ADB sideload mode. In TWRP you do this by going to Advanced then ADB Sideload.
From the command line, type adb sideload name_of_rom.zip
or
adb push Rom.zip /data/media/0/
Click to expand...
Click to collapse
clsA said:
it's no problem
you should try and get s-off next
http://forum.xda-developers.com/showthread.php?t=2314582 - revone
ARHD is great .. I also use ViperOne
just use the sideload feature in twrp being your phone is wiped
Click to expand...
Click to collapse
I will get s-off through the HTC One All in one toolkit. But on the ARHD topic, this was posted aswell:
You need:
HTC One unlocked with htcdev.com (S-ON) or S-OFF
Custom recovery
Firmware package from here (recommended but not needed for now)
Read this flashing guide - [GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock
So i tried to get the latest firmware, and that's where the problems started. But shouldn't it be better to have the latest firmware? I mean it stands there for a reason, right? Or am I wrong?
Anyway, i will try ARHD for now, it looks nice
Thanks again!
len.asdf said:
I will get s-off through the HTC One All in one toolkit. But on the ARHD topic, this was posted aswell:
You need:
HTC One unlocked with htcdev.com (S-ON) or S-OFF
Custom recovery
Firmware package from here (recommended but not needed for now)
Read this flashing guide - [GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock
So i tried to get the latest firmware, and that's where the problems started. But shouldn't it be better to have the latest firmware? I mean it stands there for a reason, right? Or am I wrong?
Anyway, i will try ARHD for now, it looks nice
Thanks again!
Click to expand...
Click to collapse
firmware comes after s-off
and ARHD 31.6 is your best bet for now till your s-off

[Q] please help me restore my One

Good day all
I have been running CM 10.2 on my One for some months. Recently its started playing up so ive decided to go back to stock.
Ive googled the process. Fastboot works OK and see's my One connected OK.
Im having issues figuring out what RUU I should be downloading. Initially I went for RUU_M7_U_JB_50_HTC_Europe_1.29.401.2
After a number of minutes it failed and said something like it cannot use this on my phone. My phone is a UK purchased unlocked device. Can anyone point me at the correct RUUI should download?
Looking at the fastboot screen I can see that my OS is 2.24.401.8
hboot is 1.54.0000
Please, any pointers to get a stock OS installed and my device booting again.
phupton said:
Looking at the fastboot screen I can see that my OS is 2.24.401.8
hboot is 1.54.0000
Please, any pointers to get a stock OS installed and my device booting again.
Click to expand...
Click to collapse
you won't get much help till you post your fastboot getvar all results
minus your serial no and IEMI
clsA said:
you won't get much help till you post your fastboot getvar all results
minus your serial no and IEMI
Click to expand...
Click to collapse
Thanks for the starter...
form-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.24.401.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: 00000000000
(bootloader) imei: 0000000000000
(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: 4103mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.080s
phupton said:
Thanks for the starter...
form-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-main: 2.24.401.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
finished. total time: 0.080s
Click to expand...
Click to collapse
You can flash this (compatible with your firmware, CID & MID): http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
if you want to receive OTAs, you'll need to select "stock recovery" (which will overwrite custom recovery).
nkk71 said:
You can flash this (compatible with your firmware, CID & MID): http://www.htc1guru.com/dld/guru_reset_m7_2-24-401-8-zip/
if you want to receive OTAs, you'll need to select "stock recovery" (which will overwrite custom recovery).
Click to expand...
Click to collapse
Happy to go totally stock. Ive unlocked my bootloader again this morning. How would I flash the zip file you have directed me to download. Apologies for my newbie/dangerous ignorance...
phupton said:
Happy to go totally stock. Ive unlocked my bootloader again this morning. How would I flash the zip file you have directed me to download. Apologies for my newbie/dangerous ignorance...
Click to expand...
Click to collapse
by flashing it in custom recovery (CWM or TWRP), just like any custom ROM.
nkk71 said:
by flashing it in custom recovery (CWM or TWRP), just like any custom ROM.
Click to expand...
Click to collapse
My phone will only boot to fastboot at the moment. ITs partially bricked. Any pointers on how to get CWM installed?
phupton said:
My phone will only boot to fastboot at the moment. ITs partially bricked. Any pointers on how to get CWM installed?
Click to expand...
Click to collapse
If you have unlocked bootloaders then download twrp or cwm and rename to recovery put the file in the fastboot folder.
Then type fastboot flash recovery recovery.img
this will flash the custom recovery.
http://forum.xda-developers.com/showthread.php?t=2173863 - CWM
http://forum.xda-developers.com/showthread.php?t=2247900 - TWRP
khandelwalsiddharth said:
If you have unlocked bootloaders then download twrp or cwm and rename to recovery put the file in the fastboot folder.
Then type fastboot flash recovery recovery.img
this will flash the custom recovery.
http://forum.xda-developers.com/showthread.php?t=2173863 - CWM
http://forum.xda-developers.com/showthread.php?t=2247900 - TWRP
Click to expand...
Click to collapse
Thanks. I should be able to get a custom recovery sorted pretty quick. Can you just give me a bit of a pointer on the flashing of the stock rom mentioned earleir
phupton said:
Looking at the fastboot screen I can see that my OS is 2.24.401.8
hboot is 1.54.0000
Please, any pointers to get a stock OS installed and my device booting again.
Click to expand...
Click to collapse
bro hboot 1.54 isn't supported for RUU. u have 2 downgrade 2 hboot 1.44 to use the RUU. follow nkk71's post on returning to stock
phupton said:
Thanks. I should be able to get a custom recovery sorted pretty quick. Can you just give me a bit of a pointer on the flashing of the stock rom mentioned earleir
Click to expand...
Click to collapse
Do one thing install a custom rom like ARHD etc. and then S-off your phone using rumrunner.
This is going to be one of those jobs that just fails and all I end up with is a bricked phone.
I am a mac user and was using a windows XP VM to communicate with me phone using fast boot... When I try to push a recovery image XP fails badly and reboots...
I can't boot camp my mac because I'm running without a CD drive and boot camp needs a CD drive before installation.
Any tips on how to get my phone sorted using a mac?
phupton said:
This is going to be one of those jobs that just fails and all I end up with is a bricked phone.
I am a mac user and was using a windows XP VM to communicate with me phone using fast boot... When I try to push a recovery image XP fails badly and reboots...
I can't boot camp my mac because I'm running without a CD drive and boot camp needs a CD drive before installation.
Any tips on how to get my phone sorted using a mac?
Click to expand...
Click to collapse
1- just use mac versions of fastboot & adb, i believe you can find them here: http://forum.xda-developers.com/showthread.php?t=2365506
(or google for them)
2- do you care about having your phone "out-of-the-box"? that entails much more work.Can you live with an UNLOCKED or RELOCKED bootloader, and possibly the TAMPERED sign?
3- if you don't care about ^^ (2), then just use the Guru Reset ROM, i linked before.
get adb and fastboot working on mac, then in bootloader/FASTBOOT USB:
fastboot flash recovery <name of recovery>.img
fastboot erase cache
fastboot reboot-bootloader
-> enter recovery
adb push <name of guru>.zip /data/media/0/
then in recovery choose "install" and select the Guru Reset ROM.
Ok so i reloaded the recovery image. Rebooted and hey presto Cyanogenmod 10.2 loaded again. Phone is now working BUT I would still like to go back to stock.
With that in mind I followed your instructions above and tried to load the Guru zip on to the SDCARD. The ADB process finishes and it says its copied the file over but I can never seem to find it whe i load the recovery and try to install from a zip file.
Questions. Am I right in thinking I can continue to load the Guru zip to attempt to get back to stock?
What am i doing wrong?
phupton said:
Ok so i reloaded the recovery image. Rebooted and hey presto Cyanogenmod 10.2 loaded again. Phone is now working BUT I would still like to go back to stock.
With that in mind I followed your instructions above and tried to load the Guru zip on to the SDCARD. The ADB process finishes and it says its copied the file over but I can never seem to find it whe i load the recovery and try to install from a zip file.
Questions. Am I right in thinking I can continue to load the Guru zip to attempt to get back to stock?
What am i doing wrong?
Click to expand...
Click to collapse
if your phone is booting up again
just copy the guru.zip to the phone storage from your mac
no need to "push" if your phone is booting up
To confirm, I am now copying the zip over.
Is there a chance of me bricking the phone again or will the Guru zip return the phone to stock and allow OTA updates?
phupton said:
To confirm, I am now copying the zip over.
Is there a chance of me bricking the phone again or will the Guru zip return the phone to stock and allow OTA updates?
Click to expand...
Click to collapse
yeah the Guru reset was designed to put the phone back to stock
it uses an Aroma installer .. choose Stock Recovery to be able to receive OTA in the future. but you won't be able to flash any custom roms or Root with the stock recovery
that seemed to do the trick. phone is back stock.
after initial setup t imediately downloaded and installed a small update. rebooted and then asked to download another 4.3 675mb big update. that one seemed to reset the devce to new again. after setup the 2nd time i can see it didnt work as the phone was as if i had just completed the guru install...
thoughts?
phupton said:
that seemed to do the trick. phone is back stock.
after initial setup t imediately downloaded and installed a small update. rebooted and then asked to download another 4.3 675mb big update. that one seemed to reset the devce to new again. after setup the 2nd time i can see it didnt work as the phone was as if i had just completed the guru install...
thoughts?
Click to expand...
Click to collapse
did the second update give an error or just didn't take ?

[SOLVED] Can anyone help me fix my htc one m7?

I recently acquired an htc one m7. i decided it would be cool to root it and put a custom rom ( i have had experience in this i have done it on my s3 my galaxy tab 2.0 and a galaxy express) so i unlocked my bootloader, flashed a custom rom and rooted my device and i decided (stupidly) to erase everything from the device (System, data, internal storage, cache, and dalvik cache) but then i realized i didnt have the file on my phone and couldnt do anything with it so i started researching. i tried to gain s-off but with every solution i need to be booted up but i dont have an os so i cannot. i tried adb sideloading the file and it just errors. i tried pushing the file and flashing it and it errors. i tried fastboot flashing it but it wont verify it. i read on a forum on this site that said to flash roms with s-on you need to flash the boot image after. i tried this and it didnt work either. i also tried flashing the factory RUU with hasoon2000's all-in-one toolkit. this did not work. ive tried different recovery (but not different versions of these recoveries) everytime i try flashing a rom it errors and says it couldnt detect filesystem for /dev/block/plat then it cuts off and after it says mount: failed to mount /dev/block/platform/msn_ then it cuts off then it continues unmount of /system failed: no such volume (even tho in my file directory there defiantly is one) then it says patching system image unconditionally..... failed to open /dev/block/platform/msm_sdcc. 1/b E: error executing epdater binary in zip ' /sdcard then cuts off. i have no idea how to fix this sorry for such a long post please help me.
sethdrak3 said:
(...)erase everything from the device (System, data, internal storage, cache, and dalvik cache) but then i realized i didnt have the file on my phone and couldnt do anything with it so i started researching.
Click to expand...
Click to collapse
This is the most common situation here, no worries, it can be fixed easily.
i tried to gain s-off
Click to expand...
Click to collapse
Why? you don't need s-off to recover from this situation, unless you want to downgrade using a RUU or convert your phone to another variant... Re-flashing another custom rom doesn't require s-off
but with every solution i need to be booted up but i dont have an os so i cannot.
Click to expand...
Click to collapse
Right, you need a working rom to achieve s-off. But you don't need S-OFF to flash a rom...
i tried adb sideloading the file and it just errors. i tried pushing the file and flashing it and it errors.
Click to expand...
Click to collapse
What is the error exactly? What is your TWRP recovery version? What rom exactly?
i tried fastboot flashing it but it wont verify it.
Click to expand...
Click to collapse
You can't flash custom roms from fastboot, it must be flashed from custom recovery. The only things that can be flashed from fastboot are recovery, firmware and ruu + flashing a firwmare or a ruu will require to be booted in RUU mode, not in bootloader mode.
i read on a forum on this site that said to flash roms with s-on you need to flash the boot image after. i tried this and it didnt work either.
Click to expand...
Click to collapse
This is true for most of HTC devices but not for the M7. The boot partition is not secured (not protected by s-on) and is flashed automatically when flashing a rom from custom recovery.
i also tried flashing the factory RUU with hasoon2000's all-in-one toolkit.
Click to expand...
Click to collapse
Which RUU exactly (link please) + post the output of "fastboot getvar all" and finally don't use any toolkits, work directly from the command prompt using fastboot and adb commands. Toolkits are not the best when in this situation.
everytime i try flashing a rom it errors and says it couldnt detect filesystem for /dev/block/plat then it cuts off and after it says mount: failed to mount /dev/block/platform/msn_ then it cuts off then it continues unmount of /system failed: no such volume (even tho in my file directory there defiantly is one) then it says patching system image unconditionally..... failed to open /dev/block/platform/msm_sdcc. 1/b E: error executing epdater binary in zip ' /sdcard then cuts off. i have no idea how to fix this sorry for such a long post please help me.
Click to expand...
Click to collapse
This is the typical error of using an outdated recovery to flash a rom that require "block:by-name" support (e.g like trying to flash Cyanogenmod using twrp older than 2.7.x.x.) so again What is your recovery version and what rom and version is it?
alray said:
This is the most common situation here, no worries, it can be fixed easily.
Why? you don't need s-off to recover from this situation, unless you want to downgrade using a RUU or convert your phone to another variant... Re-flashing another custom rom doesn't require s-off
i thought i heard somewhere you needed s off to flash roms
Right, you need a working rom to achieve s-off. But you don't need S-OFF to flash a rom...
What is the error exactly? What is your TWRP recovery version? What rom exactly?
my twrp is v2.6.0.1 and im trying to flash cm12
You can't flash custom roms from fastboot, it must be flashed from custom recovery. The only things that can be flashed from fastboot are recovery, firmware and ruu + flashing a firwmare or a ruu will require to be booted in RUU mode, not in bootloader mode.
i understand this now i was trying ever possibility and how do you get to RUU mode?
This is true for most of HTC devices but not for the M7. The boot partition is not secured (not protected by s-on) and is flashed automatically when flashing a rom from custom recovery.
Which RUU exactly (link please) + post the output of "fastboot getvar all" and finally don't use any toolkits, work directly from the command prompt using fastboot and adb commands. Toolkits are not the best when in this situation.
i am not sure which RUU i did try the RUU.exe in fastboot mode like it said to do on the htc website and it did not work
This is the typical error of using an outdated recovery to flash a rom that require "block:by-name" support (e.g like trying to flash Cyanogenmod using twrp older than 2.7.x.x.) so again What is your recovery version and what rom and version is it?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35XW916185
(bootloader) imei: 354439055703575
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3664mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
output from command "fastboot getvar all"
@alray
thank you for all your help. btw the toolkit is very useful for small things like writing new recoveries it makes it easier plus sometimes its less problematic
Click to expand...
Click to collapse
sethdrak3 said:
i thought i heard somewhere you needed s off to flash roms
Click to expand...
Click to collapse
No, you only need an unlocked bootloader + custom recovery installed.
my twrp is v2.6.0.1 and im trying to flash cm12
Click to expand...
Click to collapse
TWRP 2.6.0.1 is really outdated. Latest official version is 2.8.6.0 or (2.8.6.4 unofficial) and since 2014-05-01 you need at least twrp 2.7.0.8 to flash Cyanogenmod
i understand this now i was trying ever possibility and how do you get to RUU mode?
Click to expand...
Click to collapse
Code:
fastboot oem rebootRUU
but it won't help flashing roms, only for signed RUU and Signed firmware same or newer version that match your CID, MID and base version( x.xx.502.x) so 3.17.502.3 or above
i am not sure which RUU i did try the RUU.exe in fastboot mode like it said to do on the htc website and it did not work
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) security: on
Click to expand...
Click to collapse
If you want to flash CM12, update your recovery.
You might want to read this, this and this
TWRP can be downloaded from here and here
thank you very much @alray i flashed a more recent twrp and it worked so thank you for all of your help. it was the toolkit that flashed an old version, so yes the toolkit was not useful in this instance because the files used for the recovery were outdated. they should update them. lol thank you.
sethdrak3 said:
thank you very much @alray i flashed a more recent twrp and it worked so thank you for all of your help. it was the toolkit that flashed an old version, so yes the toolkit was not useful in this instance because the files used for the recovery were outdated. they should update them. lol thank you.
Click to expand...
Click to collapse
you're welcome, that's one example why we are not suggesting to use any toolkits.
can you edit your title to "[SOLVED] Can anyone help me fix my htc one m7?" (go to your first post, click "edit" then click "go advanced" change your title and click "save changes) thanks

Categories

Resources