Related
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.
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 ?
my htc one was stuck in bootloop i try a ruu with no success after that by fastboot unlocked the bootloader, flash a custom recovery (TWRP) and accidental wipe the phone, now i cant flash any zip give me the message unable to mount /data/
i try many roms by push fastboot and by otg cable no success
this is the result of fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: erased by me
(bootloader) imei: erased by me
(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: 4263mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
thanks in advance
mendek said:
my htc one was stuck in bootloop i try a ruu with no success after that by fastboot unlocked the bootloader, flash a custom recovery (TWRP) and accidental wipe the phone, now i cant flash any zip give me the message unable to mount /data/
i try many roms by push fastboot and by otg cable no success
this is the result of fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: removed
(bootloader) imei: erased by me
(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: 4263mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
thanks in advance
Click to expand...
Click to collapse
I would also remove your serialno! Follow the steps in this post. You can use TWRP 2.6.3.3 or TWRP 2.7.1.2 as well as the one in the post.
majmoz said:
I would also remove your serialno! Follow the steps in this post. You can use TWRP 2.6.3.3 or TWRP 2.7.1.2 as well as the one in the post.
Click to expand...
Click to collapse
thank you but where i can find a ruu to my device ? because i have the last ota update before brick
mendek said:
thank you but where i can find a ruu to my device ? because i have the last ota update before brick
Click to expand...
Click to collapse
I couldn't find a RUU for your phone, but here is a nandroid backup use Method 2. If you need the stock firmware you can get it here to run it your bootloader must be LOCK/RELOCK.
majmoz said:
I couldn't find a RUU for your phone, but here is a nandroid backup use Method 2. If you need the stock firmware you can get it here to run it your bootloader must be LOCK/RELOCK.
Click to expand...
Click to collapse
I Flash firmware, unlock the bootloader and restore a nandroid, clear cache, when reboot after HTC logo It makes a horrible noise, White screen and turn off
mendek said:
I Flash firmware, unlock the bootloader and restore a nandroid, clear cache, when reboot after HTC logo It makes a horrible noise, White screen and turn off
Click to expand...
Click to collapse
If I am following you correctly these are the steps you took:
First you flashed the firmware. Which firmware did you flash?
Then you unlocked the bootloader and installed a custom recovery. Which recovery?
Then you restored the nandroid from the post. Did you select root after the nandroid installed?
Then you cleared cache? Why?
majmoz said:
If I am following you correctly these are the steps you took:
First you flashed the firmware. Which firmware did you flash?
Then you unlocked the bootloader and installed a custom recovery. Which recovery?
Then you restored the nandroid from the post. Did you select root after the nandroid installed?
Then you cleared cache? Why?
Click to expand...
Click to collapse
hi flash the last firmware from the ota i has before.
after that flash twrp recovery 2.7.1
select root when restore
clear cache for no reason
but now i can enter in recovery always stuck in entering recovery, tried many versions of twrp and cwm and nothing, try fastboot erase cache no results
now only enter fastboot
already try relock the bootloader and flash firmware, unlock again flash custom recovery but still the same
i really dont know what do next...
mendek said:
hi flash the last firmware from the ota i has before.
after that flash twrp recovery 2.7.1
select root when restore
clear cache for no reason
but now i can enter in recovery always stuck in entering recovery, tried many versions of twrp and cwm and nothing, try fastboot erase cache no results
now only enter fastboot
already try relock the bootloader and flash firmware, unlock again flash custom recovery but still the same
i really dont know what do next...
Click to expand...
Click to collapse
I think the firmware you are using is not a compete package, generally firmware removed from OTA don't have all of the elements just those needed to run the OTA. Get a .401 stock firmware from this Placeholder of HTC One Firmwares.
majmoz said:
I think the firmware you are using is not a compete package, generally firmware removed from OTA don't have all of the elements just those needed to run the OTA. Get a .401 stock firmware from this Placeholder of HTC One Firmwares.
Click to expand...
Click to collapse
which firmware ? i try many but always failed in signature verification
mendek said:
hi flash the last firmware from the ota i has before.
after that flash twrp recovery 2.7.1
select root when restore
clear cache for no reason
but now i can enter in recovery always stuck in entering recovery, tried many versions of twrp and cwm and nothing, try fastboot erase cache no results
now only enter fastboot
already try relock the bootloader and flash firmware, unlock again flash custom recovery but still the same
i really dont know what do next...
Click to expand...
Click to collapse
Hello, i'm sorry i don't know what to say because i have almost the same problem, my htc one m7_UL won't start...is shutsdown sometimes at boot time, when i take photos with it...and sometimes what ever else, but in recovery mode it can still houers and houers. yesterday i brought it to s-off then i installed an RUU...but still the same problem !!! is it a material issue ??? thank you.
Within TWRP you should wipe data (not custom) to recreate data, system, and etc. folders. This will also wipe whats on you sdcard so, you'll have to adb push new files to your sdcard to flash a rom.
ZikoMikoo said:
Hello, i'm sorry i don't know what to say because i have almost the same problem, my htc one m7_UL won't start...is shutsdown sometimes at boot time, when i take photos with it...and sometimes what ever else, but in recovery mode it can still houers and houers. yesterday i brought it to s-off then i installed an RUU...but still the same problem !!! is it a material issue ??? thank you.
Click to expand...
Click to collapse
my start exactly like yours random restarts etc, after unlock bootloader works for another week and when i playing a game turn off and never can put it work again, now even cant enter recovery
mendek said:
which firmware ? i try many but always failed in signature verification
Click to expand...
Click to collapse
5.11.401.10
majmoz said:
5.11.401.10
Click to expand...
Click to collapse
i flash this firmware, unlock bootloader flash twrp now when is enter in recovery i see the twrp logo and after that reboot and stay in a bootloop
mendek said:
i flash this firmware, unlock bootloader flash twrp now when is enter in recovery i see the twrp logo and after that reboot and stay in a bootloop
Click to expand...
Click to collapse
after flashing a recovery, you also need to
Code:
fastboot erase cache
majmoz said:
5.11.401.10
Click to expand...
Click to collapse
now i can access the recovery, if i restore whe it pass the htc logo stucks with some stripes in the screen and turn off, try flash cyanogen it turn on but some times stucks and reboots i dont what to do maybe hardware fault?
mendek said:
now i can access the recovery, if i restore whe it pass the htc logo stucks with some stripes in the screen and turn off, try flash cyanogen it turn on but some times stucks and reboots i dont what to do maybe hardware fault?
Click to expand...
Click to collapse
Try to get back into TWRP, in TWRP flash this stock ROM Method 1. I am guessing that when you say you restore that you are talking about the nandroid backup you got from the site.
Hello there !
I got a prolem with my htc one international.
For a while i had a custom rom and decided to go back to stock rom. After some time trying to go back to stock i got som problems now.
i had TWRP on the phone, and i flashed another recovery.img, now my recovery looks all weird. i'll attach a screenshot from.
Now i cant get my old recovery i have tried everything. is there anybody out there to help me !!
(on the image you can see how it looks after trying an OTA installation)
Dardo27 said:
Hello there !
I got a prolem with my htc one international.
For a while i had a custom rom and decided to go back to stock rom. After some time trying to go back to stock i got som problems now.
i had TWRP on the phone, and i flashed another recovery.img, now my recovery looks all weird. i'll attach a screenshot from.
Now i cant get my old recovery i have tried everything. is there anybody out there to help me !!
(on the image you can see how it looks after trying an OTA installation)
Click to expand...
Click to collapse
Nearly every thread in this section has something to do with not being able to update from kitkat to lollipop on rooted phone.
did you read any of those and try anything before asking for help ?
you make no mention of what phone you have
you need a stock system and stock recovery to take OTA updates have you flash a stock rom before the stock recovery ?
clsA said:
Nearly every thread in this section has something to do with not being able to update from kitkat to lollipop on rooted phone.
did you read any of those and try anything before asking for help ?
you make no mention of what phone you have
you need a stock system and stock recovery to take OTA updates have you flash a stock rom before the stock recovery ?
Click to expand...
Click to collapse
Sure i do mention what phone i have, HTC one m7 !!! and u can see the pic !
i have read many posts on the internet, tried a lot to go back to stock, am on stock right now, the only problem is my recovery mode !
Dardo27 said:
Sure i do mention what phone i have, HTC one m7 !!! and u can see the pic !
Click to expand...
Click to collapse
There is many versions of the M7. You need to post the output of "fastboot getvar all" like we ask in every threads here so we can know exactly what phone you have and which sofmtware/firmware version installed, CID and MID number, S-ON or S-OFF.
i have read many posts on the internet, tried a lot to go back to stock, am on stock right now, the only problem is my recovery mode !
Click to expand...
Click to collapse
What recovery version have you flashed exactly?
Waiting for your "fastboot getvar all" output (remove imei and serialno befor eposting).
Dardo27 said:
Sure i do mention what phone i have, HTC one m7 !!! and u can see the pic !
i have read many posts on the internet, tried a lot to go back to stock, am on stock right now, the only problem is my recovery mode !
Click to expand...
Click to collapse
start by making sure you have the correct stock recovery, look wrong to me, so have a look through the general section for a thread labelled "stock recovery collection" and then download the 6.09.401.11 (your firmware) recovery and flash it, then try and update again.
alray said:
There is many versions of the M7. You need to post the output of "fastboot getvar all" like we ask in every threads here so we can know exactly what phone you have and which sofmtware/firmware version installed, CID and MID number, S-ON or S-OFF.
What recovery version have you flashed exactly?
Waiting for your "fastboot getvar all" output (remove imei and serialno befor eposting).
Click to expand...
Click to collapse
Here you go !
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(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__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4067mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I do not exactly remember what version of recovery it was, but i think was a stockrecovery with the wrong version from what i need!
i locked my bootloader and have no root anymore !!
thank u for your help !
Dardo27 said:
Here you go !
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(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__Y13
(bootloader) battery-status: good
(bootloader) battery-voltage: 4067mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-6d8a0b9b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I do not exactly remember what version of recovery it was, but i think was a stockrecovery with the wrong version from what i need!
i locked my bootloader and have no root anymore !!
thank u for your help !
Click to expand...
Click to collapse
you must use the 6.09.401.11 stock recovery. Since you have re-locked the bootloader, you'll have to unlock it again, restore the stock rom again and then flash the 6.09.40.11 stock recovery so you can use ota updates. No need to relock the bootloader
6.09.401.11 stock recovery here: https://www.androidfilehost.com/?fid=95832962473395870
6.09.401.11 twrp nandroid backup here: https://www.androidfilehost.com/?fid=95832962473396067
Seanie280672 said:
start by making sure you have the correct stock recovery, look wrong to me, so have a look through the general section for a thread labelled "stock recovery collection" and then download the 6.09.401.11 (your firmware) recovery and flash it, then try and update again.
Click to expand...
Click to collapse
i have tried that, this is what i get " (bootloader) signature checking...
FAILED (remote: signature verify fail)"
dont know if i'm using the right method for flash.
Dardo27 said:
i have tried that, this is what i get " (bootloader) signature checking...
FAILED (remote: signature verify fail)"
dont know if i'm using the right method for flash.
Click to expand...
Click to collapse
Failed to flash cos your bootloader is re-locked.
See @alray post above, you will have to start again, you dont need to lock or re-lock the bootloader for an OTA.
Fingerprint error as per your picture is a firmware issue, and as recovery is the only thing you can change whilst s-on, its a wrong recovery error.
the picture says it expects to find 366813.11 (.11 your firmware) but found something different, so failed.
alray said:
you must use the 6.09.401.11 stock recovery. Since you have re-locked the bootloader, you'll have to unlock it again, restore the stock rom again and then flash the 6.09.40.11 stock recovery so you can use ota updates. No need to relock the bootloader
okej ! so first i restore with twrp and then flash it ! do i need to root to use the nandroid for the restore ? or could i just use cmd ?
Thank u for your help !! reallyyyy !!:good:
Click to expand...
Click to collapse
Dardo27 said:
okej ! so first i restore with twrp and then flash it ! do i need to root to use the nandroid for the restore ? or could i just use cmd ?
Thank u for your help !! reallyyyy !!:good:
Click to expand...
Click to collapse
unlock the bootloader
flash twrp recovery
restore the nandroid backup linked above
flash back the stock recovery linked above
alray said:
unlock the bootloader
flash twrp recovery
restore the nandroid backup linked above
flash back the stock recovery linked above
Click to expand...
Click to collapse
do i flash the stock recovery with fastboot or just install with twrp ?
sorry for all the questions...thnx for the help
Dardo27 said:
do i flash the stock recovery with fastboot or just install with twrp ?
sorry for all the questions...thnx for the help
Click to expand...
Click to collapse
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
Dardo27 said:
do i flash the stock recovery with fastboot or just install with twrp ?
sorry for all the questions...thnx for the help
Click to expand...
Click to collapse
If your using TWRP 2.8.5.0 you can flash the recovery.img right from TWRP
clsA said:
If your using TWRP 2.8.5.0 you can flash the recovery.img right from TWRP
Click to expand...
Click to collapse
interesting, how its done? I suppose we must have the recovery image on /sdcard and then we can flash it from the "install" menu?
alray said:
Code:
fastboot flash recovery name_of_recovery.img
fastboot erase cache
fastboot reboot-bootloader
Click to expand...
Click to collapse
looks like i got a red triangle now when i try to get into recovery mode
Dardo27 said:
looks like i got a red triangle now when i try to get into recovery mode
Click to expand...
Click to collapse
its normal, this is the stock recovery screen, reboot your phone in the os and check for updates.
alray said:
its normal, this is the stock recovery screen, reboot your phone in the os and check for updates.
Click to expand...
Click to collapse
should there not be like a menu for wipe and stuff ?? now its just a red triangle nothing more ?
Dardo27 said:
should there not be like a menu for wipe and stuff ?? now its just a red triangle nothing more ?
Click to expand...
Click to collapse
the menu is revealed by holding volume up and hitting power.
alray said:
the menu is revealed by holding volume up and hitting power.
Click to expand...
Click to collapse
info
What's new in 2.8.4.0:
Add flashing of boot and recovery images via the TWRP GUI (Find the Images button on the Install page)
Fix some MTP related crashes and bugs
Eliminate TWRP toggling USB IDs during boot if MTP is enabled
Fix various adb sideload issues
Improve threading of actions
Eliminate separate thread for screen timeout
Update libblkid to 2.25.0
Use power button as back button on watch themes for easier navigation
Add mutex locking to data manager
Improve custom theme handling on encrypted devices
Click to expand...
Click to collapse
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