Database Develop

Unrooting failed

Recently just bought my one and never realised it was rooted till I got home with it. So I decided last night I would unroot it following a guide on youtube. Successfully relocked bootloader but when I try to flash a ruu I get 12 signature verify fail and a different ruu I get 43 main version check fail.
Hboot-1.54.0000
Radio-4a.17.3250.14
Os-2.24.401.8
Could someone tell me what ruu I should be using to make sure I have downloaded the correct one. I downloaded guru 2.24.401.8.
Thanks in advance.

The guru reset isn't a ruu.
However, you will re-turn to stock, right?
Are you in s-off? s-on?

Guich said:
The guru reset isn't a ruu.
However, you will re-turn to stock, right?
Are you in s-off? s-on?
Click to expand...
Click to collapse
Yeah I am trying to get stock.
How do I find out if S-on or sS-off? I am stuck in bootloader.

In bootloader there is write: s-off or s-on?
Or use the fastboot getvar all and post the result here, without your imei and s/n
Sent from One with Tapa4

Guich said:
In bootloader there is write: s-off or s-on?
Or use the fastboot getvar all and post the result here, without your imei and s/n
Sent from One with Tapa4
Click to expand...
Click to collapse
(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:
(bootloader) imei:
(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: 4191mV
(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.054s

Ok, the guru should work fine, have you flashed it from recovery? Which error did you get?
However, you can put your phone in s-off and port it to fully stock
Sent from One with Tapa4

Guich said:
Ok, the guru should work fine, have you flashed it from recovery? Which error did you get?
However, you can put your phone in s-off and port it to fully stock
Sent from One with Tapa4
Click to expand...
Click to collapse
The guru one gives me 12 signature verify fail. Should I be using 401.1 or 401.8? 8 is the one I have been using.
I thought I couldnt turn s-off due to hboot 1.54.0000.
I dont know how to flash it any other way apart from fastboot.

itsadogslife said:
The guru one gives me 12 signature verify fail. Should I be using 401.1 or 401.8? 8 is the one I have been using.
I thought I couldnt turn s-off due to hboot 1.54.0000.
I dont know how to flash it any other way apart from fastboot.
Click to expand...
Click to collapse
The guru zip need a custom recovery like twrp for flashing...
However, you can put in s-off your phone with 1.54 hboot, you've to ise the rumrunnes tool..
Sent from One with Tapa4

I have tried rumrunner, keep getting error.
What guru version do you suggest I use?

itsadogslife said:
I have tried rumrunner, keep getting error.
What guru version do you suggest I use?
Click to expand...
Click to collapse
The guru 2.24.401.8 should work fine because is the same of your version main.
However, which error do you have with rumrunner?

Guich said:
The guru 2.24.401.8 should work fine because is the same of your version main.
However, which error do you have with rumrunner?
Click to expand...
Click to collapse
401.8 is the version I keep trying but still 12 signature verify fail.
Rumrunner just says error: run rumrunner again and READ

itsadogslife said:
401.8 is the version I keep trying but still 12 signature verify fail.
Rumrunner just says error: run rumrunner again and READ
Click to expand...
Click to collapse
Mate, i think you're trying to flash the Guru zip as a firmware zip and this is wrong.
For flash the guru zip you've to install a custom recovery like TWRP, reboot in it and flash the file from the sd of the phone.
When the installation is finished, your phone will boot.
rumrunners give you an error because you've to use it when you're on android

Guich said:
Mate, i think you're trying to flash the Guru zip as a firmware zip and this is wrong.
For flash the guru zip you've to install a custom recovery like TWRP, reboot in it and flash the file from the sd of the phone.
When the installation is finished, your phone will boot.
rumrunners give you an error because you've to use it when you're on android
Click to expand...
Click to collapse
Yeah I am flashing the zip through fastboot, ie fstboot flash zip ruu.zip.
Do I install th custom recovery the same way?
Sorry for being a noob, htc one is more complicated than samsung galaxy.

itsadogslife said:
Yeah I am flashing the zip through fastboot, ie fstboot flash zip ruu.zip.
Do I install th custom recovery the same way?
Sorry for being a noob, htc one is more complicated than samsung galaxy.
Click to expand...
Click to collapse
There are guides for this.
you've to flash a custom recovery with
Code:
fastboot flash recovery nameofrecovery.img
and after boot in it and flash the guru zip.
If you don't have it on your sd, you've to push it with the code
Code:
adb push nameofrom.zip /sdcard/
Finally you can flash it through recovery

I think my phone has had it.
Tried flash recovey and same error, 12 signature verify fail.

itsadogslife said:
I think my phone has had it.
Tried flash recovey and same error, 12 signature verify fail.
Click to expand...
Click to collapse
Mate are you flashing the file in ruu mode? (fastboot oem rebootRUU)?
If yes, and i think yes, you're wrong.
Please, use this guide for flash a custom recovery... (don't check the points 7, 8 and 9, from 6 go to 10)

Guich said:
Mate are you flashing the file in ruu mode? (fastboot oem rebootRUU)?
If yes, and i think yes, you're wrong.
Please, use this guide for flash a custom recovery... (don't check the points 7, 8 and 9, from 6 go to 10)
Click to expand...
Click to collapse
I finally got it sorted mate. I had to unlock my bootloader again, once that was done the phone booted up straight away. Then I booted the ruu on the phone sd and installed from recovery. Thanks for all your help mate.

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

troubles with update firmaware

hi
i have htc one with :
(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-OFF
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
this steps i have follow:
for update from 1.44.0000 to 4.19.401.9
1.Type: fastboot oem lock (if your device is not relocked yet)
2.Type: fastboot oem rebootRUU and wait for device to reboot
3.Type: fastboot flash zip firmware.zip and wait for process to complete
4.Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
5.Type: fastboot flash zip firmware.zip and wait for process to complete
6.Type: fastboot reboot
troubles after the update :/
1/ i get msg from the battery that he is 4% and that is not right.
i be sure that he is 89% is full
2/ now he is bootlocked and cant get twrp2.6.3.3 on it
3/adb is not working only fastboot
question:
1/have i take the wrong firmware?
so yes where can i find the right firmware for 1.29.401.16
2/ how can i get back bootloader unlock in 4.19.401.9
3/ revone is that working under 4.19.401.9?
i have noidea what i need to do now

aater updation phone stuck
MRX_X said:
hi
i have htc one with :
(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-OFF
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
this steps i have follow:
for update from 1.44.0000 to 4.19.401.9
1.Type: fastboot oem lock (if your device is not relocked yet)
2.Type: fastboot oem rebootRUU and wait for device to reboot
3.Type: fastboot flash zip firmware.zip and wait for process to complete
4.Sometimes flashing for the first time doesn't work, so flash firmware.zip again just to make sure.
5.Type: fastboot flash zip firmware.zip and wait for process to complete
6.Type: fastboot reboot
troubles after the update :/
1/ i get msg from the battery that he is 4% and that is not right.
i be sure that he is 89% is full
2/ now he is bootlocked and cant get twrp2.6.3.3 on it
3/adb is not working only fastboot
question:
1/have i take the wrong firmware?
so yes where can i find the right firmware for 1.29.401.16
2/ how can i get back bootloader unlock in 4.19.401.9
3/ revone is that working under 4.19.401.9?
i have noidea what i need to do now
Click to expand...
Click to collapse
i am having the same problem with a twist. My HTC One duel sim was running on 4.2.2. It is not rooted and is on stock firmware. After updation, the phone is not booting and is stuck on HTC logo. I tried the Power+volume down method(which i read in some other thread) which reveals the bootloader is locked.How and why i dont know. Kindly guide me what to do. Please note that a noob altogather. Regards

MRX_X said:
hi
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
1.Type: fastboot oem lock (if your device is not relocked yet)
i have noidea what i need to do now
Click to expand...
Click to collapse
you don't need to lock bootloader to flash firmware when you are S-Off, those instructions are for S-On!!
Here download this:
fw_TWRP_2.6.3.3_1.26.401.3.zip 8.9 MB
https://mega.co.nz/#!6VcSlICK!lWPl1wgrah43yxom7mLkpPHi71kAXoSk-BdNpaTcxNc
MD5: BF37A63802EB37B37689DE08D133484F
fastboot oem rebootRUU
fastboot flash zip fw_TWRP_2.6.3.3_1.26.401.3.zip
fastboot reboot-bootloader
fastboot erase cache
-> enter recovery
use the following adb commands to unlock your bootloader: http://forum.xda-developers.com/showthread.php?t=2475914
PS: note that the above will change your version-main to 1.26.401.3 (referring to TWRP 2.6.3.3), only the displayed value not the actual firmware, once you flash another firmware, the "displayed" number will change again.
---------- Post added at 12:36 PM ---------- Previous post was at 12:31 PM ----------
asadkhattak said:
i am having the same problem with a twist. My HTC One duel sim was running on 4.2.2. It is not rooted and is on stock firmware. After updation, the phone is not booting and is stuck on HTC logo. I tried the Power+volume down method(which i read in some other thread) which reveals the bootloader is locked.How and why i dont know. Kindly guide me what to do. Please note that a noob altogather. Regards
Click to expand...
Click to collapse
Dual SIM is different that m7_u / ul models, please check Dual SIM threads.

nkk71 said:
you don't need to lock bootloader to flash firmware when you are S-Off, those instructions are for S-On!!
Here download this:
fw_TWRP_2.6.3.3_1.26.401.3.zip 8.9 MB
https://mega.co.nz/#!6VcSlICK!lWPl1wgrah43yxom7mLkpPHi71kAXoSk-BdNpaTcxNc
MD5: BF37A63802EB37B37689DE08D133484F
fastboot oem rebootRUU
fastboot flash zip fw_TWRP_2.6.3.3_1.26.401.3.zip
fastboot reboot-bootloader
fastboot erase cache
-> enter recovery
use the following adb commands to unlock your bootloader: http://forum.xda-developers.com/showthread.php?t=2475914
PS: note that the above will change your version-main to 1.26.401.3 (referring to TWRP 2.6.3.3), only the displayed value not the actual firmware, once you flash another firmware, the "displayed" number will change again.
---------- Post added at 12:36 PM ---------- Previous post was at 12:31 PM ----------
Dual SIM is different that m7_u / ul models, please check Dual SIM threads.
Click to expand...
Click to collapse
i have get the bootloader back in unlock via the link that you have give me.
than i have install TWRP than install the custom rom AR_HDone_52.0
and so far work everything good
thanks for fast respond

MRX_X said:
i have get the bootloader back in unlock via the link that you have give me.
than i have install TWRP than install the custom rom AR_HDone_52.0
and so far work everything good
thanks for fast respond
Click to expand...
Click to collapse
It's just my home-brew of TWRP 2.6.3.3 repackaged in a firmware zip to be able to flash in RUU mode :silly:
you may wanna reconsider reflashing your firmware though, just so your "fastboot getvar all" doesnt show version-main: 1.26.401.3 (a made up version number), the actual firmware is still whatever you flashed, but doesn't show up in the getvar.
the "version-main" is always, the last thing you flashed in ruu mode.
anyway, remember, you don't need to lock with s-off: http://forum.xda-developers.com/showpost.php?p=49832723&postcount=388

nkk71 said:
It's just my home-brew of TWRP 2.6.3.3 repackaged in a firmware zip to be able to flash in RUU mode :silly:
you may wanna reconsider reflashing your firmware though, just so your "fastboot getvar all" doesnt show version-main: 1.26.401.3 (a made up version number), the actual firmware is still whatever you flashed, but doesn't show up in the getvar.
the "version-main" is always, the last thing you flashed in ruu mode.
anyway, remember, you don't need to lock with s-off: http://forum.xda-developers.com/showpost.php?p=49832723&postcount=388
Click to expand...
Click to collapse
I have put your flash ruu in me collection ( have the time is right when i be troubles than i can use it )

MRX_X said:
I have put your flash ruu in me collection ( have the time is right when i be troubles than i can use it )
Click to expand...
Click to collapse
it's very easy to create yourself too, just get whatever recovery you want, rename to recovery.img + an "android-info.txt" with proper MID and CID, and you can even make your "version-main" 6.78.401.9 (as in 6789 but WWE) :silly: in the android-info.txt file (remember it's unix format not dos/windows).
obviously you need to be S-Off to flash it since it's completely unsigned.
only reason you would need it if you locked/relocked bootloader while S-Off, which is completely redundant... no need to lock/relock with s-off

[Q] m7 weird brick need help

Hi guys .last month weird thing happen
My m7 lose signal then i restarted the phOne suddenly bricked ..
the problem
Stuck on bootloop
Lost my access to recovery
RUU not stocking but not showing any error (RUU.exe)
I think its because the kernel i have instaled (elementarX 14)
I think sumting wrong with emmc or mid (pn071****)
My rom arhd62
Cid-11111111
Hboot-1.44.0000
Baseband-4a.14.3250.13
eMMC-boot
M7_ul s-off
Modelid n071
I searched all over the place ..need help ppl

Can u try reflashing recovery through fastboot? Sometines the kernel if flashed improperly can wipe recovery partition and it needs to be reflashed....reflash recovery through fastboot and reflash with fastboot flash recovery yourrecoveryname.img
Sent from my HTCONE using Tapatalk

knockratos said:
Hi guys .last month weird thing happen
My m7 lose signal then i restarted the phOne suddenly bricked ..
the problem
Stuck on bootloop
Lost my access to recovery
RUU not stocking but not showing any error (RUU.exe)
I think its because the kernel i have instaled (elementarX 14)
My rom arhd62
Cid-11111111
Hboot-1.44.0000
Baseband-4a.14.3250.13
eMMC-boot
M7_ul s-off
Modelid n071
I searched all over the place ..need help ppl
Click to expand...
Click to collapse
Post the output of fastboot getvar all except IMEI and S/N.
have you tried to flash your recovery + erase cache?

alray said:
Post the output of fastboot getvar all except IMEI and S/N.
have you tried to flash your recovery + erase cache?
Click to expand...
Click to collapse
I alredy did that ..
i try reflash the twrp then the rom.zip the zip say error not enough space
i try to erase system and stuff failed too

knockratos said:
I alredy did that ..
i try reflash the twrp then the rom.zip the zip say error not enough space
i try to erase system and stuff failed too
Click to expand...
Click to collapse
fastboot getvar all

alray said:
fastboot getvar all
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.401.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN071****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4241mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.092s

knockratos said:
(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.2
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN071****
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4241mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.092s
Click to expand...
Click to collapse
What ruu are you trying to use? With s-off it should be quite easy to restore your phone...
did you modified your MID?

alray said:
What ruu are you trying to use? With s-off it should be quite easy to restore your phone...
did you modified your MID?
Click to expand...
Click to collapse
RUU m7 u jb 50 htc europe 1.29.401.2.r.radio 4a1432501310331150release311663signed24..
First time i bricked and it works ..after that i allways use nandroid ..but now doesnt work and i dont have acces to recovery

knockratos said:
RUU m7 u jb 50 htc europe 1.29.401.2.r.radio 4a1432501310331150release311663signed24..
First time i bricked and it works ..after that i allways use nandroid ..but now doesnt work and i dont have acces to recovery
Click to expand...
Click to collapse
So you are using a ruu.exe. What version of windows do you have? 7, 8 or 8.1?

alray said:
What ruu are you trying to use? With s-off it should be quite easy to restore your phone...
did you modified your MID?
Click to expand...
Click to collapse
knockratos said:
RUU m7 u jb 50 htc europe 1.29.401.2.r.radio 4a1432501310331150release311663signed24..
First time i bricked and it works ..after that i allways use nandroid ..but now doesnt work and i dont have acces to recovery
Click to expand...
Click to collapse
1- JTAG repair ? (thanks @scotty1223 )
2- you have a UL model it seems not a U
@alray link him the MID change tool (not the ENG method ) change mid to PN0710000 then he can go on with an m7_ul ruu... or whatever need to be done, good luck

mid change tool:
http://forum.xda-developers.com/showthread.php?t=2535365

nkk71 said:
1- JTAG repair ? (thanks @scotty1223 )
2- you have a UL model it seems not a U
@alray link him the MID change tool (not the ENG method ) change mid to PN0710000 then he can go on with an m7_ul ruu... or whatever need to be done, good luck
Click to expand...
Click to collapse
Windows 7
What is jtag repair
long time agO the RUU was working fine (the brick was only freeze on bootloop but whit recovery)
But now it REBOOTLOOP over and over and i lost access to recovery ..
The RUU do its job sucessfuly but not stocking (doing nothing)
I guess i didnt chage any mid
I have to change ? How ? And than what ?
Is it possibly that is kernel issue ?
Dont know what to do

knockratos said:
Windows 7
Dont know what to do
Click to expand...
Click to collapse
alray is helping you plenty, so return in kind by at least pressing his thanks button

nkk71 said:
alray is helping you plenty, so return in kind by at least pressing his thanks button
Click to expand...
Click to collapse
Done but im new in here ..

alray said:
mid change tool:
http://forum.xda-developers.com/showthread.php?t=2535365
Click to expand...
Click to collapse
How i can install the mid change if i dont have access to recovery?

alray said:
mid change tool:
http://forum.xda-developers.com/showthread.php?t=2535365
Click to expand...
Click to collapse
Hi tried using fastboot flash zip ..it says failed remote not allowed

knockratos said:
Hi tried using fastboot flash zip ..it says failed remote not allowed
Click to expand...
Click to collapse
download twrp 2.6.3.3 from here and save it to your adb/fastboot folder
check MD5 before flashing: 72067aefb69541d40e8420d7aa46408d
boot phone in bootloader mode and flash the recovery:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootlader
then boot in recovery mode (TWRP main menu)
Download the MID change tool from here and save it to your adb/fastboot folder
check md5 value: ae54b6e28a925270661994dbe16eb742
push the tool:
Code:
adb push MID_Change_1.01.zip /sdcard/
in twrp, select ''install'' browse sdcard and select ''MID_Change_1.01.zip'' then ''swipe to confirm flash''.
The aroma installer will start:
select ''next'' at the ''welcome screen''
Thick the check box ''I agree with these Terms of Use'', then select ''next''
select ''next'' at the ''Credit and Support'' screen
at the CID Options screen, select ''PN0710000'' then select ''next''
at the ''ready to install'' screen, select ''install now''
wait for the mid tool to do its magic (few seconds) and select ''next''
at the ''Actions were successful'' screen, select ''Finish''
Now you are back in TWRP recovery
select ''back'' twice and then ''reboot'' and choose ''bootloader''
You are now back in bootloader mode
change your cid to match the RUU:
Code:
fastboot oem writecid HTC__001
fastboot reboot-bootloader
download the ruu from here
check md5: 9ad4111ce86981e3dffcce6d9ee80551
launch the ruu and follow instructions.
stay s-off and bootloader unlocked.

alray said:
download twrp 2.6.3.3 from here and save it to your adb/fastboot folder
check MD5 before flashing: 72067aefb69541d40e8420d7aa46408d
boot phone in bootloader mode and flash the recovery:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootlader
Not working cant enter to recovery mode and it keeps reboot loop
I think if the recovery start work i will use my nandroid backup ..and the RUU wont be necessary i guess
How to check the md5 value ?? @alray I realy apreciate what u doing to help me .thnks ..
Click to expand...
Click to collapse

knockratos said:
Not working cant enter to recovery mode and it keeps reboot loop
Click to expand...
Click to collapse
You mean the phone bootloop when you are trying to enter recovery or it bootloop as soon you enter bootloader?
Try holding power + vol down until the phone boot in bootloader and stop looping
How to check the md5 value ??
Click to expand...
Click to collapse
check ''not so FAQ #1'' at the end of this post (from nkk71's guide)
or
http://lmgtfy.com/?q=how+do+i+check+md5+windows

alray said:
You mean the phone bootloop when you are trying to enter recovery or it bootloop as soon you enter bootloader?
Try holding power + vol down until the phone boot in bootloader and stop looping
check ''not so FAQ #1'' at the end of this post (from nkk71's guide)
or
http://lmgtfy.com/?q=how+do+i+check+md5+windows
Click to expand...
Click to collapse
It means that boot loop when i enter recovery mode or factory reset mode or turn on the phone( of course)
Keep boot over and over ..
But the bootloader is fine .

[Q] hboot 1.44.00 and can't move forward nor backwards

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