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 ?
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.
Hi, I'm trying to revert my HTC one to stock ROM. I'd previously followed a tutorial on flashing it to GPE, but I can't find (or more likely don't have the smarts) to get it back to a stock ROM..
It's a 3 UK model, H3G__001, and I have been having trouble finding a backup, but have found a RAR file called M7 TWRP Nandroid Backup CID H3G 001 2.24.771.3 .rar from the HTC1guru downloads page.
Trouble is - I don't know exactly how to restore this file, and despite my best googling efforts, I'm stuck.
Can anyone help with a step-by-step ? ( Sorry I hate to have to ask )
Phone Info :
C:\sdk-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.1700.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3845mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.068s
Plz help a numpty!
Colinmac said:
Hi, I'm trying to revert my HTC one to stock ROM. I'd previously followed a tutorial on flashing it to GPE, but I can't find (or more likely don't have the smarts) to get it back to a stock ROM..
It's a 3 UK model, H3G__001, and I have been having trouble finding a backup, but have found a RAR file called M7 TWRP Nandroid Backup CID H3G 001 2.24.771.3 .rar from the HTC1guru downloads page.
Trouble is - I don't know exactly how to restore this file, and despite my best googling efforts, I'm stuck.
Can anyone help with a step-by-step ? ( Sorry I hate to have to ask )
Phone Info :
C:\sdk-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.00
(bootloader) version-baseband: 4T.21.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.62.1700.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: SH38EW902402
(bootloader) imei: 357864058120484
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: H3G__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3845mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e82187e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.068s
Plz help a numpty!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2541082
This is the link to the guide. The 4th post is the one which concerns you.
Also, i would suggest that you use this RUU from htc1guru instead of the one you chose:
http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-h3g__001-1-28-771-x-2013-04-09-zip/
The one which u downloaded was TWRP Nandroid. But the guide doesnt explain the TWRP Nandroid as well as CWM Nandroid. So, ive given u the link for the easier method
raghav kapur said:
http://forum.xda-developers.com/showthread.php?t=2541082
This is the link to the guide. The 4th post is the one which concerns you.
Also, i would suggest that you use this RUU from htc1guru instead of the one you chose:
http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-h3g__001-1-28-771-x-2013-04-09-zip/
The one which u downloaded was TWRP Nandroid. But the guide doesnt explain the TWRP Nandroid as well as CWM Nandroid. So, ive given u the link for the easier method
Click to expand...
Click to collapse
the link you gave is 1.28.771 and theirs a good chance with his firmware he will have no touchscreen driver for that Nandroid ...he already has the best file in my opinion
@Colinmac
Easy way back to Sense rom is flash the developer RUU here
http://www.androidruu.com/getdownlo...8_10.38r.1157.04L_release_353887_signed_3.exe
raghav kapur said:
http://forum.xda-developers.com/showthread.php?t=2541082
This is the link to the guide. The 4th post is the one which concerns you.
Also, i would suggest that you use this RUU from htc1guru instead of the one you chose:
http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-h3g__001-1-28-771-x-2013-04-09-zip/
The one which u downloaded was TWRP Nandroid. But the guide doesnt explain the TWRP Nandroid as well as CWM Nandroid. So, ive given u the link for the easier method
Click to expand...
Click to collapse
Ok. I downloaded the linked CWM zip and renamed it ruu.zip for convenience, but when I try and fastboot flash it, I get :
C:\sdk-tools>fastboot flash zip ruu.zip
target reported max download size of 1526722560 bytes
sending 'zip' (963956 KB)...
OKAY [ 39.405s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 39.719s
Should I revert to using the linked one in the article ? I was thinking the zip you linked would be a closer match ?
If I go down the route of flashing the dev RUU - will I need to do anything else post-flash?
I couldn't find much evidence of this being a working option on a retail phone - but that may be old info....
Colinmac said:
Ok. I downloaded the linked CWM zip and renamed it ruu.zip for convenience, but when I try and fastboot flash it, I get :
C:\sdk-tools>fastboot flash zip ruu.zip
target reported max download size of 1526722560 bytes
sending 'zip' (963956 KB)...
OKAY [ 39.405s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 39.719s
Should I revert to using the linked one in the article ? I was thinking the zip you linked would be a closer match ?
Click to expand...
Click to collapse
you can't flash a nandriod backup like a rom
you have to copy it to your phone's clockworkmod/backup folder then restore it from recovery ... same for the TWRP nandriod .. it must be copied to TWRP/BACKUP/YourPhoneSN/Dateofbackup
Like I said lock your bootloader and the Developer edition RUU is your easy out
clsA said:
you can't flash a nandriod backup like a rom
you have to copy it to your phone's clockworkmod/backup folder then restore it from recovery ... same for the TWRP nandriod .. it must be copied to TWRP/BACKUP/YourPhoneSN/Dateofbackup
Like I said lock your bootloader and the Developer edition RUU is your easy out
Click to expand...
Click to collapse
Ok. so I relocked the bootloader, and grabbed that DEV .exe updater.
Sadly, it reboots phone into the silver HTC logo, then checks, and starts to update and then crashes. Rebooting and rerunning produced the same results...
I'm on Win8 - would it be OS related ?
Colinmac said:
Ok. so I relocked the bootloader, and grabbed that DEV .exe updater.
Sadly, it reboots phone into the silver HTC logo, then checks, and starts to update and then crashes. Rebooting and rerunning produced the same results...
I'm on Win8 - would it be OS related ?
Click to expand...
Click to collapse
no if it were windows 8 related the RUU would not have started
how far in was it when it failed. 2 min ? less ? or more?
clsA said:
no if it were windows 8 related the RUU would not have started
how far in was it when it failed. 2 min ? less ? or more?
Click to expand...
Click to collapse
Hi - it gets to the update process - step 1 of 5 or so - then blows up. It did say I needed to get the correct version for my phone ?
Could it be CID ?
Colinmac said:
Hi - it gets to the update process - step 1 of 5 or so - then blows up. It did say I needed to get the correct version for my phone ?
Could it be CID ?
Click to expand...
Click to collapse
I'm not sure .. i guess you should try pushing the TWRP nanadriod again
does your phone boot up to the OS ?
clsA said:
I'm not sure .. i guess you should try pushing the TWRP nanadriod again
does your phone boot up to the OS ?
Click to expand...
Click to collapse
If I powerdown then back up - it boots back into my GPE fine.
The Nandroid backup I have is a .rar file - is it ok to unpack and repack as a .zip or can I just push the rar ?
Also I can't seem to now unlock my bootloader again - if I run the flash unlocktoken, the screen asking if I want to unlock does not reappear as it did the first time.
Man, I'm scratching my head a lot - sorry for being a dud.
Colinmac said:
If I powerdown then back up - it boots back into my GPE fine.
The Nandroid backup I have is a .rar file - is it ok to unpack and repack as a .zip or can I just push the rar ?
Also I can't seem to now unlock my bootloader again - if I run the flash unlocktoken, the screen asking if I want to unlock does not reappear as it did the first time.
Man, I'm scratching my head a lot - sorry for being a dud.
Click to expand...
Click to collapse
Ouch ... your s-off I don't think you needed to relock I made a mistake
what version of TWRP do you have installed ?
clsA said:
Ouch ... your s-off I don't think you needed to relock I made a mistake
what version of TWRP do you have installed ?
Click to expand...
Click to collapse
Its 2.6.0.1
Colinmac said:
Its 2.6.0.1
Click to expand...
Click to collapse
your s-off so we can get this...
first boot to recovery and do a nandroid backup
and then boot the phone back up
then unrar your TWRP backup (that you downloaded) to your pc to a folder called nandroid
you then copy this to the location TWRP/BACKUP/YourPhoneSerialno/Put nandriod here
now reboot recovery and in TWRP choose backup .. nandroid should be their
restore it
clsA said:
your s-off so we can get this...
first boot to recovery and do a nandroid backup
and then boot the phone back up
then unrar your TWRP backup (that you downloaded) to your pc to a folder called nandroid
you then copy this to the location TWRP/BACKUP/YourPhoneSerialno/Put nandriod here
now reboot recovery and in TWRP choose backup .. nandroid should be their
restore it
Click to expand...
Click to collapse
Magic - that's the phone booting back to stock - worked brilliantly cheers !
Now to try and get the stock recovery etc back lol.
Thanks for your help bud !
Ah turns out it's not quite that simple. Android wants to get OTA updates but when the phone reboots to do it - it enters twrp recovery.
I need to get the stock recovery back also - so I downloaded what I think is the right version of recovery.img but when I try and fastboot flash it - it fails.
Would I need the phone back unlocked for this? And if so - how do I go about it now?
Colinmac said:
Ah turns out it's not quite that simple. Android wants to get OTA updates but when the phone reboots to do it - it enters twrp recovery.
I need to get the stock recovery back also - so I downloaded what I think is the right version of recovery.img but when I try and fastboot flash it - it fails.
Would I need the phone back unlocked for this? And if so - how do I go about it now?
Click to expand...
Click to collapse
you can either re-unlock the bootloader with the s-off method (guru bootloader tool) to flash your stock recovery or pack up your recovery.img in a firmware.zip and flash it in ruu mode with a locked bootloader.
To use the guru bootloader tool go to this page: http://www.htc1guru.com/guides/guru-bootloader-reset/
save the zip on your sd card, boot in recovery, select ''install'' and choose the guru bootloader tool. This will open the aroma installer. Chose to unlock bootloader. be careful not turning back s-on with the tool. The tool only work with s-off phones.
edit: oh wait! just realized you are on twrp 2.6.0.1. The tool is intended for 2.6.3.3, not sure if it will work...
alray said:
you can either re-unlock the bootloader with the s-off method (guru bootloader tool) to flash your stock recovery or pack up your recovery.img in a firmware.zip and flash it in ruu mode with a locked bootloader.
To use the guru bootloader tool go to this page: http://www.htc1guru.com/guides/guru-bootloader-reset/
save the zip on your sd card, boot in recovery, select ''install'' and choose the guru bootloader tool. This will open the aroma installer. Chose to unlock bootloader. be careful not turning back s-on with the tool. The tool only work with s-off phones.
edit: oh wait! just realized you are on twrp 2.6.0.1. The tool is intended for 2.6.3.3, not sure if it will work...
Click to expand...
Click to collapse
I agree Stay s-off for as long as possible
just thinking out loud here ..but i think he may need to downgrade his hboot back to 1.44 to get an unlocktoken
alray said:
you can either re-unlock the bootloader with the s-off method (guru bootloader tool) to flash your stock recovery or pack up your recovery.img in a firmware.zip and flash it in ruu mode with a locked bootloader.
To use the guru bootloader tool go to this page: http://www.htc1guru.com/guides/guru-bootloader-reset/
save the zip on your sd card, boot in recovery, select ''install'' and choose the guru bootloader tool. This will open the aroma installer. Chose to unlock bootloader. be careful not turning back s-on with the tool. The tool only work with s-off phones.
edit: oh wait! just realized you are on twrp 2.6.0.1. The tool is intended for 2.6.3.3, not sure if it will work...
Click to expand...
Click to collapse
Ok. The guru tool ran - but I definitely chose unlock bootloader but it hasnt worked.
Can you clarify the RUU flashing business for the recovery ? I figure if I can get the phone to get itself up to date, I can factory reset it to get rid of any odd lingering mods?
does a firmware.zip need anything other than the .img file in it?
clsA said:
I agree Stay s-off for as long as possible
just thinking out loud here ..but i think he may need to downgrade his hboot back to 1.44 to get an unlocktoken
Click to expand...
Click to collapse
I'm happy to retain S-Off until I was to sell the phone on.
Man, I'm so out of my depth now - didn't realise I had upgraded my hboot - how would I go about that ?
Colinmac said:
Ok. The guru tool ran - but I definitely chose unlock bootloader but it hasnt worked.
Can you clarify the RUU flashing business for the recovery ? I figure if I can get the phone to get itself up to date, I can factory reset it to get rid of any odd lingering mods?
does a firmware.zip need anything other than the .img file in it?
Click to expand...
Click to collapse
try and flash this from recovery first then reboot and try the GURU reset tool again
https://www.dropbox.com/s/n49t43thctnl02a/TWRP_2.6.3.3_m7.zip
it's the flashable zip
After months of thinking it through, i finally decided to give up on sense and try cyanogenmod... horrible desicion. I tried the installer and according to to the installer itself the install had concluded without error and all i had to do now was wait for my device to boot. When booting my device off andd after 5 minutes of beeing stuck in a bootloop, i realized that something had gone horribly wrong. I found many solutions online, but ended up narrowimg down to 2 options: wipe data/ factory reset and wipe dalvik through CWM or running a ruu to go bavk to stock and retry from there. Tried doing the wipe but i kept getting the error "Cant mount data" so i pretty much gave up on that option and went for running the RUU. Succesfully locked my bootloader again and all that was left for me to do was run the ruu and wait for my htc one to be running sense again! While going through the installer, i got an error at around the" 1/5" part of the ruu install (i used an exe) which said "error 171, check usb connection" and i also simultaniously got a pop up window that said "htc_fastboot.exe has stopped working" . At this point i really dont know what to do. PLEASE! Someone help me!
josevera30 said:
After months of thinking it through, i finally decided to give up on sense and try cyanogenmod... horrible desicion. I tried the installer and according to to the installer itself the install had concluded without error and all i had to do now was wait for my device to boot. When booting my device off andd after 5 minutes of beeing stuck in a bootloop, i realized that something had gone horribly wrong. I found many solutions online, but ended up narrowimg down to 2 options: wipe data/ factory reset and wipe dalvik through CWM or running a ruu to go bavk to stock and retry from there. Tried doing the wipe but i kept getting the error "Cant mount data" so i pretty much gave up on that option and went for running the RUU. Succesfully locked my bootloader again and all that was left for me to do was run the ruu and wait for my htc one to be running sense again! While going through the installer, i got an error at around the" 1/5" part of the ruu install (i used an exe) which said "error 171, check usb connection" and i also simultaniously got a pop up window that said "htc_fastboot.exe has stopped working" . At this point i really dont know what to do. PLEASE! Someone help me!
Click to expand...
Click to collapse
is your phone recognised by device manager? Are you using Windows and if so what version are you running?
Can you post a fastboot getvar all removing your serial number and imei please and let me know what RUU you are running?
stovie_steve said:
is your phone recognised by device manager? Are you using Windows and if so what version are you running?
Can you post a fastboot getvar all removing your serial number and imei please and let me know what RUU you are running?
Click to expand...
Click to collapse
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.07.1540.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4298mV
(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
all: Done!
finished. total time: 0.081s
im using windows 8 and the ruu is
RUU_M7_UL_K44_SENSE55_MR_BrightstarUS_WWE_4.19.1540.9_Radio_4A.23.3263.28_10.38r.1157.04L_release_353887_signed_3.exe
josevera30 said:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.07.1540.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4298mV
(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
all: Done!
finished. total time: 0.081s
im using windows 8 and the ruu is
RUU_M7_UL_K44_SENSE55_MR_BrightstarUS_WWE_4.19.1540.9_Radio_4A.23.3263.28_10.38r.1157.04L_release_353887_signed_3.exe
Click to expand...
Click to collapse
I think it's down to Windows 8 - fastboot isn't detecting the drivers Which is why it fails with error 171
Have you tried again with a Windows 7 PC?
I think there is a post on here about getting fastvoot drivers to work on Windows 8. I'll have a look
stovie_steve said:
I think it's down to Windows 8 - fastboot isn't detecting the drivers Which is why it fails with error 171
Have you tried again with a Windows 7 PC?
I think there is a post on here about getting fastvoot drivers to work on Windows 8. I'll have a look
Click to expand...
Click to collapse
Please help me! If you can find a fix, please do! i kind of hate the cyangenmod installer for getting me into this mess!! When i get back to stock i'll probably still try to put cyanogenmod on my htc one...
josevera30 said:
Please help me! If you can find a fix, please do! i kind of hate the cyangenmod installer for getting me into this mess!! When i get back to stock i'll probably still try to put cyanogenmod on my htc one...
Click to expand...
Click to collapse
Try this guide
http://forum.xda-developers.com/showthread.php?t=2232799
Followed the guide thoroughly but got this pop up window at the last step.
josevera30 said:
Followed the guide thoroughly but got this pop up window at the last step.
Click to expand...
Click to collapse
Does fastboot work normally or does it only fail when running an RUU, if that's the case uninstall HTC Sync if you have it installed. But leave drivers installed. HTC sync is known to cause problems with RUU's
But there is no RUU that will work for you since your device is s-on and on the latest firmware. Downgrading is not possible with s-on. At this point the best you can hope for is to flash a custom rom. At least you can get the phone booting that way.
Do if adb/fastboot is working normally just push a Rom and install it. If you can't get adb/fastboot working on your Windows 8 pc try my mini guide here to create a bootable Linux pen drive.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Danny201281 said:
Does fastboot work normally or does it only fail when running an RUU, if that's the case uninstall HTC Sync if you have it installed. But leave drivers installed. HTC sync is known to cause problems with RUU's
But there is no RUU that will work for you since your device is s-on and on the latest firmware. Downgrading is not possible with s-on. At this point the best you can hope for is to flash a custom rom. At least you can get the phone booting that way.
Do if adb/fastboot is working normally just push a Rom and install it. If you can't get adb/fastboot working on your Windows 8 pc try my mini guide here to create a bootable Linux pen drive.
Click to expand...
Click to collapse
Fastboot and ADB only fail while running RUU. I thought i could use the ruu since i pretty much had cyangenmod installed (Got stuck in a bootloop). I still want to install cyanogenmod on my phone so if you could help me with that it would be great! Fastboot and ADB work so if you could help me push cyanogenmod on it, this poblem would be fixed! Please help me!
josevera30 said:
Fastboot and ADB only fail while running RUU. I thought i could use the ruu since i pretty much had cyangenmod installed (Got stuck in a bootloop). I still want to install cyanogenmod on my phone so if you could help me with that it would be great! Fastboot and ADB work so if you could help me push cyanogenmod on it, this poblem would be fixed! Please help me!
Click to expand...
Click to collapse
You can't use this RUU on your phone because its an older version. You need s-off to flash lower version RUU. You will need to either s-off your phone or restore it using a nandroid backup of 6.07.1540.1 or flash another custom rom like Danny suggested above. Look in this thread: http://forum.xda-developers.com/showthread.php?t=2355992 you might found a nandroid backup of that version. If you can find it just tell me and I'll upload mine for you. I also have the stock recovery for that version if needed.
to install cyanogenmod you need a recovery with block:by-name support like newer version of TWRP.
http://wiki.cyanogenmod.org/w/Install_CM_for_m7
http://wiki.cyanogenmod.org/w/HTC_fstab_updates
josevera30 said:
Fastboot and ADB only fail while running RUU. I thought i could use the ruu since i pretty much had cyangenmod installed (Got stuck in a bootloop). I still want to install cyanogenmod on my phone so if you could help me with that it would be great! Fastboot and ADB work so if you could help me push cyanogenmod on it, this poblem would be fixed! Please help me!
Click to expand...
Click to collapse
Download the latest CWM recovery and flash it with fastboot. http://downloadandroidrom.com/file/HTCOne/recovery/M7CWM/recovery-clockwork-touch-6.0.4.8-m7.img
Code:
fastboot flash recovery "nameofrecovery".img
fastboot erase cache
Download CM11 here. Rename the file to rom.zip and place it in your fastboot folder on your pc.
http://downloadandroidrom.com/file/HTCOne/M7/roms/CM11/cm-11-20140624-NIGHTLY-m7.zip
Also download gapps rename it to gapps.zip and place it in your fastboot folder.
http://downloadandroidrom.com/file/gapps/PA/pa_gapps-stock-4.4.3-20140608-signed.zip
Boot your phone to cwm recovery and connect usb. Do a factory reset then in the command window type
Code:
adb push rom.zip /sdcard
Wait for the push to compmete
Code:
adb push gapps.zip /sdcard
again wait for completion, it's normal for the command window to appear unresponsive until the push completes.
Now use cwm to install the Rom.zip followed by gapps.zip.
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
josevera30 said:
Fastboot and ADB only fail while running RUU. I thought i could use the ruu since i pretty much had cyangenmod installed (Got stuck in a bootloop). I still want to install cyanogenmod on my phone so if you could help me with that it would be great! Fastboot and ADB work so if you could help me push cyanogenmod on it, this poblem would be fixed! Please help me!
Click to expand...
Click to collapse
Any update?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Danny201281 said:
Any update?
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Click to expand...
Click to collapse
He also asked me (via PM) a TWRP nandroid backup of stock 6.07.1540.1 which I have uploaded for him yesterday.
No update yet, still don't know if the OP will flash the rom or restore the nand but I think he wants to flash the rom (but have the nand just in case).
alray said:
He also asked me (via PM) a TWRP nandroid backup of stock 6.07.1540.1 which I have uploaded for him yesterday.
No update yet, still don't know if the OP will flash the rom or restore the nand but I think he wants to flash the rom (but have the nand just in case).
Click to expand...
Click to collapse
Lol, he was also pm me, last I herd he was having trouble pushing the cm11 Rom. After successful push the Rom was still not on the device.
I instructed him to use "mount usb storage" in cwm. Not heard anything since
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
Solved!
Thank you so much for your help! I did a wipe data/ factory reset and used sideload to push and install cyanogenmod! Thanks for your help :good:
josevera30 said:
Thank you so much for your help! I did a wipe data/ factory reset and used sideload to push and install cyanogenmod! Thanks for your help :good:
Click to expand...
Click to collapse
Thanks for the update, good to know you got it sorted
Sent from my HTC One M7 - ARHD 81.0 Using Tapatalk
If you found my posts helpful, Please click thanks :good:
I recently acquired an htc one m7. i decided it would be cool to root it and put a custom rom ( i have had experience in this i have done it on my s3 my galaxy tab 2.0 and a galaxy express) so i unlocked my bootloader, flashed a custom rom and rooted my device and i decided (stupidly) to erase everything from the device (System, data, internal storage, cache, and dalvik cache) but then i realized i didnt have the file on my phone and couldnt do anything with it so i started researching. i tried to gain s-off but with every solution i need to be booted up but i dont have an os so i cannot. i tried adb sideloading the file and it just errors. i tried pushing the file and flashing it and it errors. i tried fastboot flashing it but it wont verify it. i read on a forum on this site that said to flash roms with s-on you need to flash the boot image after. i tried this and it didnt work either. i also tried flashing the factory RUU with hasoon2000's all-in-one toolkit. this did not work. ive tried different recovery (but not different versions of these recoveries) everytime i try flashing a rom it errors and says it couldnt detect filesystem for /dev/block/plat then it cuts off and after it says mount: failed to mount /dev/block/platform/msn_ then it cuts off then it continues unmount of /system failed: no such volume (even tho in my file directory there defiantly is one) then it says patching system image unconditionally..... failed to open /dev/block/platform/msm_sdcc. 1/b E: error executing epdater binary in zip ' /sdcard then cuts off. i have no idea how to fix this sorry for such a long post please help me.
sethdrak3 said:
(...)erase everything from the device (System, data, internal storage, cache, and dalvik cache) but then i realized i didnt have the file on my phone and couldnt do anything with it so i started researching.
Click to expand...
Click to collapse
This is the most common situation here, no worries, it can be fixed easily.
i tried to gain s-off
Click to expand...
Click to collapse
Why? you don't need s-off to recover from this situation, unless you want to downgrade using a RUU or convert your phone to another variant... Re-flashing another custom rom doesn't require s-off
but with every solution i need to be booted up but i dont have an os so i cannot.
Click to expand...
Click to collapse
Right, you need a working rom to achieve s-off. But you don't need S-OFF to flash a rom...
i tried adb sideloading the file and it just errors. i tried pushing the file and flashing it and it errors.
Click to expand...
Click to collapse
What is the error exactly? What is your TWRP recovery version? What rom exactly?
i tried fastboot flashing it but it wont verify it.
Click to expand...
Click to collapse
You can't flash custom roms from fastboot, it must be flashed from custom recovery. The only things that can be flashed from fastboot are recovery, firmware and ruu + flashing a firwmare or a ruu will require to be booted in RUU mode, not in bootloader mode.
i read on a forum on this site that said to flash roms with s-on you need to flash the boot image after. i tried this and it didnt work either.
Click to expand...
Click to collapse
This is true for most of HTC devices but not for the M7. The boot partition is not secured (not protected by s-on) and is flashed automatically when flashing a rom from custom recovery.
i also tried flashing the factory RUU with hasoon2000's all-in-one toolkit.
Click to expand...
Click to collapse
Which RUU exactly (link please) + post the output of "fastboot getvar all" and finally don't use any toolkits, work directly from the command prompt using fastboot and adb commands. Toolkits are not the best when in this situation.
everytime i try flashing a rom it errors and says it couldnt detect filesystem for /dev/block/plat then it cuts off and after it says mount: failed to mount /dev/block/platform/msn_ then it cuts off then it continues unmount of /system failed: no such volume (even tho in my file directory there defiantly is one) then it says patching system image unconditionally..... failed to open /dev/block/platform/msm_sdcc. 1/b E: error executing epdater binary in zip ' /sdcard then cuts off. i have no idea how to fix this sorry for such a long post please help me.
Click to expand...
Click to collapse
This is the typical error of using an outdated recovery to flash a rom that require "block:by-name" support (e.g like trying to flash Cyanogenmod using twrp older than 2.7.x.x.) so again What is your recovery version and what rom and version is it?
alray said:
This is the most common situation here, no worries, it can be fixed easily.
Why? you don't need s-off to recover from this situation, unless you want to downgrade using a RUU or convert your phone to another variant... Re-flashing another custom rom doesn't require s-off
i thought i heard somewhere you needed s off to flash roms
Right, you need a working rom to achieve s-off. But you don't need S-OFF to flash a rom...
What is the error exactly? What is your TWRP recovery version? What rom exactly?
my twrp is v2.6.0.1 and im trying to flash cm12
You can't flash custom roms from fastboot, it must be flashed from custom recovery. The only things that can be flashed from fastboot are recovery, firmware and ruu + flashing a firwmare or a ruu will require to be booted in RUU mode, not in bootloader mode.
i understand this now i was trying ever possibility and how do you get to RUU mode?
This is true for most of HTC devices but not for the M7. The boot partition is not secured (not protected by s-on) and is flashed automatically when flashing a rom from custom recovery.
Which RUU exactly (link please) + post the output of "fastboot getvar all" and finally don't use any toolkits, work directly from the command prompt using fastboot and adb commands. Toolkits are not the best when in this situation.
i am not sure which RUU i did try the RUU.exe in fastboot mode like it said to do on the htc website and it did not work
This is the typical error of using an outdated recovery to flash a rom that require "block:by-name" support (e.g like trying to flash Cyanogenmod using twrp older than 2.7.x.x.) so again What is your recovery version and what rom and version is it?
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT35XW916185
(bootloader) imei: 354439055703575
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3664mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.040s
output from command "fastboot getvar all"
@alray
thank you for all your help. btw the toolkit is very useful for small things like writing new recoveries it makes it easier plus sometimes its less problematic
Click to expand...
Click to collapse
sethdrak3 said:
i thought i heard somewhere you needed s off to flash roms
Click to expand...
Click to collapse
No, you only need an unlocked bootloader + custom recovery installed.
my twrp is v2.6.0.1 and im trying to flash cm12
Click to expand...
Click to collapse
TWRP 2.6.0.1 is really outdated. Latest official version is 2.8.6.0 or (2.8.6.4 unofficial) and since 2014-05-01 you need at least twrp 2.7.0.8 to flash Cyanogenmod
i understand this now i was trying ever possibility and how do you get to RUU mode?
Click to expand...
Click to collapse
Code:
fastboot oem rebootRUU
but it won't help flashing roms, only for signed RUU and Signed firmware same or newer version that match your CID, MID and base version( x.xx.502.x) so 3.17.502.3 or above
i am not sure which RUU i did try the RUU.exe in fastboot mode like it said to do on the htc website and it did not work
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-main: 3.17.502.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: CWS__001
(bootloader) security: on
Click to expand...
Click to collapse
If you want to flash CM12, update your recovery.
You might want to read this, this and this
TWRP can be downloaded from here and here
thank you very much @alray i flashed a more recent twrp and it worked so thank you for all of your help. it was the toolkit that flashed an old version, so yes the toolkit was not useful in this instance because the files used for the recovery were outdated. they should update them. lol thank you.
sethdrak3 said:
thank you very much @alray i flashed a more recent twrp and it worked so thank you for all of your help. it was the toolkit that flashed an old version, so yes the toolkit was not useful in this instance because the files used for the recovery were outdated. they should update them. lol thank you.
Click to expand...
Click to collapse
you're welcome, that's one example why we are not suggesting to use any toolkits.
can you edit your title to "[SOLVED] Can anyone help me fix my htc one m7?" (go to your first post, click "edit" then click "go advanced" change your title and click "save changes) thanks
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