Howdy fellas. So im pretty hooped here. First of all let it be said i am a total noob and this has solidified my standing as a noob. Bought a used M7 (Rogers), came rooted BL unlocked, s-on, running cm 11. I wanted to install ARHD 83.1 Thought hey why not start from scratch, unroot flash stock RUU etc. So i made a backup of the Cm11 rom just incase in twrp 2.8.3.0. Relocked BL, then google Rogers M7 RUU , downloaded a 4.4, sense 5.5 one and ran it. Got an error message about 3 min in from windows explorer saying htc.fastboot.exe has stopped, everything closed and my phone just rebooted back to fastboot. SO i thought i better restore my backup. Went to unlock bootloader, hit yes and my phone was booting into cm 11... stuck at boot logo for an hour till it got quite warm. So i hard reset it, went into recovery to restore backup and voila, I have 0 MB internal storage with no files at all. Can someone please help? Ill even donate if you can help me get my phone back
Many thanks
butthurtlocker said:
Howdy fellas. So im pretty hooped here. First of all let it be said i am a total noob and this has solidified my standing as a noob. Bought a used M7 (Rogers), came rooted BL unlocked, s-on, running cm 11. I wanted to install ARHD 83.1 Thought hey why not start from scratch, unroot flash stock RUU etc. So i made a backup of the Cm11 rom just incase in twrp 2.8.3.0. Relocked BL, then google Rogers M7 RUU , downloaded a 4.4, sense 5.5 one and ran it. Got an error message about 3 min in from windows explorer saying htc.fastboot.exe has stopped, everything closed and my phone just rebooted back to fastboot. SO i thought i better restore my backup. Went to unlock bootloader, hit yes and my phone was booting into cm 11... stuck at boot logo for an hour till it got quite warm. So i hard reset it, went into recovery to restore backup and voila, I have 0 MB internal storage with no files at all. Can someone please help? Ill even donate if you can help me get my phone back
Many thanks
Click to expand...
Click to collapse
looks like your data partition is corrupted. This should be easy to fix but first post the output of "fastboot getvar all" except your IMEI and SERIALNO.
BTW do you prefer to go back to stock rom or CM?
alray said:
looks like your data partition is corrupted. This should be easy to fix but first post the output of "fastboot getvar all" except your IMEI and SERIALNO.
BTW do you prefer to go back to stock rom or CM?
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.20.3263.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.22.631.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4259mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-fe1214a4f2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I much prefer stock! Thanks so much for the reply too i hope i can get this going somehow
butthurtlocker said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-main: 3.22.631.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) security: on
I much prefer stock! Thanks so much for the reply too i hope i can get this going somehow
Click to expand...
Click to collapse
Sorry for late reply, we have some serious power outages here in Quebec (damn freezing rain!)
Download TWRP 2.6.3.3 and save it to your adb/fastboot folder on your computer
With your phone connected to your computer and booted in bootlloader/fastboot usb mode, open a command prompt from your adb/fastboot folder:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Boot in recovery mode (TWRP), select Wipe, Advanced Wipe, then select everything and "Swipe to wipe". When completed, go back in the main menu, select Wipe then "Format Data". When format data is completed reboot the recovery.
When rebooted in recovery, select "backup" then select "boot" only and swipe to backup, go back in the main menu
Download this nandroid backup and save it to your desktop.
Extract the backup zip files, put all the files in a folder and name that folder "MYBACKUP"
move that folder in the same folder where you have adb and fastboot on your computer
with your phone still in twrp main menu, adb push the backup to your phone:
Code:
adb push MYBACKUP /sdcard/TWRP/BACKUPS/[COLOR="Red"]Your_Serial_Number[/COLOR]/MYBACKUP
(replace text in red by your phone's serial number. You can find your serial number in your "fastboot getvar all")
This will take a while and your command prompt will be unresponsive during the transfer. When the command prompt is responsive again, then the transfer is complete.
In twrp select "restore", select "MYBACKUP", select all partitions then "swipe to restore"
reboot phone and confirm everything is working fine
alray said:
Sorry for late reply, we have some serious power outages here in Quebec (damn freezing rain!)
Download TWRP 2.6.3.3 and save it to your adb/fastboot folder on your computer
With your phone connected to your computer and booted in bootlloader/fastboot usb mode, open a command prompt from your adb/fastboot folder:
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-bootloader
Boot in recovery mode (TWRP), select Wipe, Advanced Wipe, then select everything and "Swipe to wipe". When completed, go back in the main menu, select Wipe then "Format Data". When format data is completed reboot the recovery.
When rebooted in recovery, select "backup" then select "boot" only and swipe to backup, go back in the main menu
Download this nandroid backup and save it to your desktop.
Extract the backup zip files, put all the files in a folder and name that folder "MYBACKUP"
move that folder in the same folder where you have adb and fastboot on your computer
with your phone still in twrp main menu, adb push the backup to your phone:
Code:
adb push MYBACKUP /sdcard/TWRP/BACKUPS/[COLOR="Red"]Your_Serial_Number[/COLOR]/MYBACKUP
(replace text in red by your phone's serial number. You can find your serial number in your "fastboot getvar all")
This will take a while and your command prompt will be unresponsive during the transfer. When the command prompt is responsive again, then the transfer is complete.
In twrp select "restore", select "MYBACKUP", select all partitions then "swipe to restore"
reboot phone and confirm everything is working fine
Click to expand...
Click to collapse
Wow man, you did it. It works! Thanks so much. You got a paypal i can donate to? Im happy to throw a few bucks your way. One last question, Im wondering if the radio/firmware that nandroid is running is new enough that i can install a rom like ARHD 84 or insert coin etc? Or Do i need to update it somehow? And if so how would i go about doing that? your step by step was amazing by the way,
butthurtlocker said:
Wow man, you did it. It works! Thanks so much.
Click to expand...
Click to collapse
You're welcome!
You got a paypal i can donate to? Im happy to throw a few bucks your way.
Click to expand...
Click to collapse
If you feel that I deserve it, you can use the "donate to me" button below my avatar
One last question, Im wondering if the radio/firmware that nandroid is running is new enough that i can install a rom like ARHD 84 or insert coin etc? Or Do i need to update it somehow?
Click to expand...
Click to collapse
I think it should be good with those roms but it wouldn't hurt to update it. 3.22.631.1 is a pretty old firmware.
And if so how would i go about doing that?
Click to expand...
Click to collapse
Well the easiest way would be to flash the stock recovery back and take all ota updates to latest version. Otherwise you could use the 4.19.631.9 and then take the remaining ota updates.
your step by step was amazing by the way
Click to expand...
Click to collapse
Thanks :highfive:
alray said:
You're welcome!
If you feel that I deserve it, you can use the "donate to me" button below my avatar
I think it should be good with those roms but it wouldn't hurt to update it. 3.22.631.1 is a pretty old firmware.
Well the easiest way would be to flash the stock recovery back and take all ota updates to latest version. Otherwise you could use the 4.19.631.9 and then take the remaining ota updates.
Thanks :highfive:
Click to expand...
Click to collapse
y
In either case, could you step ny step me into how to do either? As in how to take stock recovery then otas as well as the new actual firmware. Would i need s-off for either? Sorry to ask so much but im just a bit overwhelmed by all this being new to it. And yeah im totes gonma slang you some coin when im home from work
butthurtlocker said:
y
In either case, could you step ny step me into how to do either? As in how to take stock recovery then otas as well as the new actual firmware. Would i need s-off for either? Sorry to ask so much but im just a bit overwhelmed by all this being new to it. And yeah im totes gonma slang you some coin when im home from work
Click to expand...
Click to collapse
Download your stock recovery and save it to your adb/fastboot folder on your computer.
reboot your phone in bootloader/fastboot usb mode
Start a command prompt from ADB/Fastboot folder
Code:
fastboot flash recovery recovery_stock_155hboot_htc_one_m7.img
fastboot erase cache
fastboot reboot
Wait for the phone to reboot in the OS
go in Settings --> About --> Software updates Check for new updates and install them
repeat steps 4 and 5 until your phone is running the latest version with Android 4.4.3 and HTC Sense 6
Then your phone will be updated to latest software and firmware (6.XX.631.X)
alray said:
Download your stock recovery and save it to your adb/fastboot folder on your computer.
reboot your phone in bootloader/fastboot usb mode
Start a command prompt from ADB/Fastboot folder
Code:
fastboot flash recovery recovery_stock_155hboot_htc_one_m7.img
fastboot erase cache
fastboot reboot
Wait for the phone to reboot in the OS
go in Settings --> About --> Software updates Check for new updates and install them
repeat steps 4 and 5 until your phone is running the latest version with Android 4.4.3 and HTC Sense 6
Then your phone will be updated to latest software and firmware (6.XX.631.X)
Click to expand...
Click to collapse
Thanks man, trying now. Just donated
NOTE- i could only update to 4.4.2, Sense 6. My radio now reads 4T.27.3218.14, Hboot 1.57. This doesnt match the newer version number! IS there any thing else i could do to further update my firmware?
alray said:
Download your stock recovery and save it to your adb/fastboot folder on your computer.
reboot your phone in bootloader/fastboot usb mode
Start a command prompt from ADB/Fastboot folder
Code:
fastboot flash recovery recovery_stock_155hboot_htc_one_m7.img
fastboot erase cache
fastboot reboot
Wait for the phone to reboot in the OS
go in Settings --> About --> Software updates Check for new updates and install them
repeat steps 4 and 5 until your phone is running the latest version with Android 4.4.3 and HTC Sense 6
Then your phone will be updated to latest software and firmware (6.XX.631.X)
Click to expand...
Click to collapse
Hope you got my donation! Thanks again for the help. I do have one additional questions however. So i did what you said flashed that stock recovery, then update as far as my OTAS would go. then re flashed TWRP so i could flash ARHD. But im wanting to re flash stock recovery now! So i see my Hboot has changed to 1.57. Could you link me to the new proper stock recovery for my updated device?
butthurtlocker said:
Hope you got my donation! Thanks again for the help. I do have one additional questions however. So i did what you said flashed that stock recovery, then update as far as my OTAS would go. then re flashed TWRP so i could flash ARHD. But im wanting to re flash stock recovery now! So i see my Hboot has changed to 1.57. Could you link me to the new proper stock recovery for my updated device?
Click to expand...
Click to collapse
Don't reflash the stock recovery if you are using a custom rom like arhd, keep twrp recovery.
Stock recovery is not useful at all when using custom roms, only needed for stock roms.
And I need to know your main version to direct you to the correct stock recovery version
Code:
fastboot getvar version-main
Related
Hello,
I Flashed the Android Revolution ROM (International version) on my HTC One, had no problems whatsoever
(i used TWRP)
However, somehow i deleted my OS..
Now, i pushed the rom to my HTC One, and i can install the rom via TWRP.
However, i'm stuck at the HTC One boot logo.
Can anyone help
Im using the HTC One international version.
Btw, i erased the cache and flashed the boot.img via cmd, still not getting anything.
Nickkrommenie said:
Hello,
I Flashed the Android Revolution ROM (International version) on my HTC One, had no problems whatsoever
(i used TWRP)
However, somehow i deleted my OS..
Now, i pushed the rom to my HTC One, and i can install the rom via TWRP.
However, i'm stuck at the HTC One boot logo.
Can anyone help
Im using the HTC One international version.
Btw, i erased the cache and flashed the boot.img via cmd, still not getting anything.
Click to expand...
Click to collapse
Did you check the download is not corrupt? Check the MD5 sum, sounds like a bad download.
No need to flash boot.img as this comes as part of the ROM, but you can (within recovery) erase cache and Dalvik.
Still sound like a bad download IMHO.
nkk71 said:
Did you check the download is not corrupt? Check the MD5 sum, sounds like a bad download.
No need to flash boot.img as this comes as part of the ROM, but you can (within recovery) erase cache and Dalvik.
Still sound like a bad download IMHO.
Click to expand...
Click to collapse
How can i check the MD5 sum?
And if it's a bad download, do i just need to re-download the ROM? / Flash another rom
Nickkrommenie said:
How can i check the MD5 sum?
And if it's a bad download, do i just need to re-download the ROM? / Flash another rom
Click to expand...
Click to collapse
Here's a simple program that will do the job: www.WinMD5.com
The original MD5 is usually mentioned in the OP, or the download section. once you compare that to the one you downloaded, HAPPY FLASHING.
Remember to hit the Thanks button if I helped
nkk71 said:
Here's a simple program that will do the job: www.WinMD5.com
The original MD5 is usually mentioned in the OP, or the download section. once you compare that to the one you downloaded, HAPPY FLASHING.
Remember to hit the Thanks button if I helped
Click to expand...
Click to collapse
Nice, unplugged my HTC and plugged it in 15 minutes later, and ADB doesnt recognise my phone..
I typed adb devices and all i get is: list of devices attached.
Nothing more
Never mind, PC does recognise phone now.
However, i tried another ROM. pushed it onto my phone and flashed it.
However, now i´m stuck at the Insertcoin bootlogo =/
Im totally stuck here.
Nickkrommenie said:
Never mind, PC does recognise phone now.
However, i tried another ROM. pushed it onto my phone and flashed it.
However, now i´m stuck at the Insertcoin bootlogo =/
Im totally stuck here.
Click to expand...
Click to collapse
Are you checking the MD5 sums? Also can you post a "fastboot getvar all" (remove IMEI and s/n).
nkk71 said:
Are you checking the MD5 sums? Also can you post a "fastboot getvar all" (remove IMEI and s/n).
Click to expand...
Click to collapse
I will post a fastboot getvar all when i get home.
could this maybe be a problem with the memory of the HTC One? The rom just doesn't boot.(gets stuck at homescreen, and tried different roms). even tried the boot.img method but that didn't work either..
EDIT: This is what i get :
(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: XXXXXX
(bootloader) imei: XXXXXX
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__E11
(bootloader) battery-status: good
(bootloader) battery-voltage: 3696mV
(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!
So, to sum up things:
I flashed a custom rom, no problems at all.
When i tried to wipe the data of my phone, i accidently wiped my OS.
However, my HTC gets recognised by my W7 pc, and i have no problem pushing Custom ROMS to my HTC (bootloader and recovery are accessible).
However, when i flash a custom rom, the phone gets stuck at the HTC boot-logo
I tried the fastboot erase-cache, then flash the boot.img and installed the ROM etc,
I tried that in every order possible.
P.s i checked the MD5 sums
Nickkrommenie said:
So, to sum up things:
I flashed a custom rom, no problems at all.
When i tried to wipe the data of my phone, i accidently wiped my OS.
However, my HTC gets recognised by my W7 pc, and i have no problem pushing Custom ROMS to my HTC (bootloader and recovery are accessible).
However, when i flash a custom rom, the phone gets stuck at the HTC boot-logo
I tried the fastboot erase-cache, then flash the boot.img and installed the ROM etc,
I tried that in every order possible.
P.s i checked the MD5 sums
Click to expand...
Click to collapse
Strange indeed! So there are only two things I can think of:
1- It's a hardware defect; I've read of 1 incident (again 1) where they guy actually to the phone back to the shop and they confirmed it was a defective memory board. (for now let's assume this is NOT your case)
2- you said "i accidently wiped my OS", which I assume you did by formatting something (probably /system) in TWRP, which could have messed or corrupted your partitions. have you tried different recoveries?
Here's what I'm thinking: flash a different recovery, format pretty much everything, adb push the ROM again, and hope it works.
So if you're up to it:
1- Download the following CWM recovery (that way I can follow you as it's the same one on my phone at the moment):
recovery-clockwork-touch-6.0.3.2-m7--v2.img (7.2 MB)
https://mega.co.nz/#!6E8RiIrQ!GF5LyhmEdg8OQJxuQVVjwSxBljxhW7xsZAHLzjVACsc
MD5: 1c6afb14db3f305b0ad7d85d5af80bef
2- flash it in bootloader:
fastboot erase cache
fastboot flash recovery recovery-clockwork-touch-6.0.3.2-m7--v2.img
fastboot erase cache
fastboot reboot-bootloader
-> enter RECOVERY and confirm you're on attached screen, and we'll proceed from there...
nkk71 said:
Strange indeed! So there are only two things I can think of:
1- It's a hardware defect; I've read of 1 incident (again 1) where they guy actually to the phone back to the shop and they confirmed it was a defective memory board. (for now let's assume this is NOT your case)
2- you said "i accidently wiped my OS", which I assume you did by formatting something (probably /system) in TWRP, which could have messed or corrupted your partitions. have you tried different recoveries?
Here's what I'm thinking: flash a different recovery, format pretty much everything, adb push the ROM again, and hope it works.
So if you're up to it:
1- Download the following CWM recovery (that way I can follow you as it's the same one on my phone at the moment):
recovery-clockwork-touch-6.0.3.2-m7--v2.img (7.2 MB)
https://mega.co.nz/#!6E8RiIrQ!GF5LyhmEdg8OQJxuQVVjwSxBljxhW7xsZAHLzjVACsc
MD5: 1c6afb14db3f305b0ad7d85d5af80bef
2- flash it in bootloader:
fastboot erase cache
fastboot flash recovery recovery-clockwork-touch-6.0.3.2-m7--v2.img
fastboot erase cache
fastboot reboot-bootloader
-> enter RECOVERY and confirm you're on attached screen, and we'll proceed from there...
Click to expand...
Click to collapse
Okaj, i am at the exact same screen at this moment
Nickkrommenie said:
Okaj, i am at the exact same screen at this moment
Click to expand...
Click to collapse
Okay, now go to "mounts and storage"
start formatting:
- format /system
- format /data
- format /cache
- format /sdcard
- format /data and /data/media (/sdcard)
***go back***
adb push <name of rom>.zip /data/media/
- install zip
and flash it
nkk71 said:
Okay, now go to "mounts and storage"
start formatting:
- format /system
- format /data
- format /cache
- format /sdcard
- format /data and /data/media (/sdcard)
***go back***
adb push <name of rom>.zip /data/media/
- install zip
and flash it
Click to expand...
Click to collapse
Did everything, however when i wanted to push the rom to my phone, adb doesnt recognise my phone...
EDIT: I figured it out, however when i try to push the ROM to the phone, CMD says : protocol failure..
Nickkrommenie said:
Did everything, however when i wanted to push the rom to my phone, adb doesnt recognise my phone...
Click to expand...
Click to collapse
reboot phone: go to "advanced" and select "reboot recovery"
and also reboot PC
Don't forget to unplug phone and later replug after reboot. then confirm adb is working again.
EDIT: and while you're there, wipe dalvik
nkk71 said:
reboot phone: go to "advanced" and select "reboot recovery"
and also reboot PC
Don't forget to unplug phone and later replug after reboot. then confirm adb is working again.
EDIT: and while you're there, wipe dalvik
Click to expand...
Click to collapse
Did that, when i plug my phone into the computer you can here the "connected tune" from windows.
However, 5 seconds after i wanted to push the rom, you can hear the "disconnected tune" and it just says protocol failure.
Nickkrommenie said:
Did that, when i plug my phone into the computer you can here the "connected tune" from windows.
However, 5 seconds after i wanted to push the rom, you can hear the "disconnected tune" and it just says protocol failure.
Click to expand...
Click to collapse
silly question, but is the phone charged enough? also try a different USB port. I know this is a bit of trial and error to get adb to work sometimes. I remember you having this problem before no?
Did you update drivers and adb?
nkk71 said:
silly question, but is the phone charged enough? also try a different USB port. I know this is a bit of trial and error to get adb to work sometimes. I remember you having this problem before no?
Did you update drivers and adb?
Click to expand...
Click to collapse
Yes the phone was charged enough, "sideloaded" the ROM and installed it. Now i just have to wait and hope for the ROM to boot.
EDIT: ROM Doesn't boot, just reboots in recovery after a while
Nickkrommenie said:
Yes the phone was charged enough, "sideloaded" the ROM and installed it. Now i just have to wait and hope for the ROM to boot.
Click to expand...
Click to collapse
keep me posted, I'm F5'ing this thread like a hawk :cyclops:
nkk71 said:
keep me posted, I'm F5'ing this thread like a hawk :cyclops:
Click to expand...
Click to collapse
First of all, even when i wont be able to fix this phone. I would like to thank you for your support and time!
Nickkrommenie said:
First of all, even when i wont be able to fix this phone. I would like to thank you for your support and time!
Click to expand...
Click to collapse
"even when i wont be able to fix this phone" let's keep that an IF, I'm not ready to give up just yet fingers still crossed :fingers-crossed:
Hello everybody I have a little big problem
3 days ago my brain wanted to root the phone to try a custom rom so I started looking in forums how to do it how to unlock bootloader and so on after a few hours succeeded unlock the bootloader got rooted and installed a custom recovery
After the successful instal i had in mind to try cm11, installed the cm 11 everything was OK WiFi working everything worked, what do I get in mind hmm..... How about to go back to stock to see if was OK and easy to do it and go back to forum read most of the topic and i saw that the best idea was to lock the bootloader and try go back to stock... Done.. The next minute the bootloader wiped everything I mean everything there is no data no nothing only the recovery tried push with adb a new system FAILED tried with obd cable and a stick USB ( I put 3 custom roms and cm11 too) flashed goes to boot screen and stays there forever with every ROM i flashed got bootloop I unlocked the bootloader again tried again everything no success
And my question is there a way to that my HTC One to get back to life?
Sorry about the topic and sorry about my bad english but i miss my HTC One
Sent from my SM-N9005 using XDA Premium 4 mobile app
No one could help me?
Sent from my SM-N9005 using XDA Premium 4 mobile app
Laurentiu27 said:
Hello everybody I have a little big problem
3 days ago my brain wanted to root the phone to try a custom rom so I started looking in forums how to do it how to unlock bootloader and so on after a few hours succeeded unlock the bootloader got rooted and installed a custom recovery
After the successful instal i had in mind to try cm11, installed the cm 11 everything was OK WiFi working everything worked, what do I get in mind hmm..... How about to go back to stock to see if was OK and easy to do it and go back to forum read most of the topic and i saw that the best idea was to lock the bootloader and try go back to stock... Done.. The next minute the bootloader wiped everything I mean everything there is no data no nothing only the recovery tried push with adb a new system FAILED tried with obd cable and a stick USB ( I put 3 custom roms and cm11 too) flashed goes to boot screen and stays there forever with every ROM i flashed got bootloop I unlocked the bootloader again tried again everything no success
And my question is there a way to that my HTC One to get back to life?
Sorry about the topic and sorry about my bad english but i miss my HTC One
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Please ensure you have a custom recovery (TWRP) and your bootloader is UNLOCKED if you are going to side load or push a custom rom onto your phone. If you are going to use the RUU route, then you need to have the bootloader LOCKED or RELOCKED. Here is a post that explains the steps to each method.
Laurentiu27 said:
Hello everybody I have a little big problem
3 days ago my brain wanted to root the phone to try a custom rom so I started looking in forums how to do it how to unlock bootloader and so on after a few hours succeeded unlock the bootloader got rooted and installed a custom recovery
Click to expand...
Click to collapse
After the successful instal i had in mind to try cm11, installed the cm 11 everything was OK WiFi working everything worked, what do I get in mind hmm..... How about to go back to stock to see if was OK and easy to do it and go back to forum read most of the topic and i saw that the best idea was to lock the bootloader and try go back to stock... Done..
Click to expand...
Click to collapse
Locking the bootloader is only needed if you want to go back to stock using a RUU. I don't know if its what you have tried to do or any other method (guru reset rom, nandroid backup, stock odexed rom, Ruu.zip or ruu.exe?) The output of "fastboot getvar all" could help (dont post IMEI and SN) + what recovery and version # are you using?
The next minute the bootloader wiped everything I mean everything there is no data no nothing only the recovery
Click to expand...
Click to collapse
bootloader can't wipe anything by itself. You probably did something wrong, can't tell you what at this point.
tried push with adb a new system
Click to expand...
Click to collapse
Which one? You need to be more precise i.e I tried to adb push X rom X version #.
FAILED
Click to expand...
Click to collapse
Again, be more precise. What was the error code/message? + post a screenshot of the cmd prompt when it fail
tried with obd cable and a stick USB ( I put 3 custom roms and cm11 too) flashed goes to boot screen and stays there forever with every ROM i flashed got bootloop I unlocked the bootloader again tried again everything no success
Click to expand...
Click to collapse
Stop rushing things, or you'll probably make the situation worst. We will help you step by step if needed.
And my question is there a way to that my HTC One to get back to life?
Click to expand...
Click to collapse
Probably but:
what is your goal? you want to flash a custom rom or return back to stock rom?
Post the output of fastboot getvar all excluding imei and sn
what is your recovery + what is the version?
post a picture of the bootloader screen
when you speak about a rom/recovery always be specific what name and version
Soon as I get my HTC back from a friend ho want to try do it i will post everything thing that is needed with screenshots and errors
Sent from my SM-N9005 using XDA Premium 4 mobile app
ok got my htc one back still dead
im using twrp recovery latest one
now pls guide me step by step how to do it
i don't care if is a custom or stock just want my htc back to life
This is what i got on it in the white screen is Android revolution hd tring to bot(installed with otg cable and USB) the other 2 pictures are the the data from bootloader and the twrp recovery
Sent from my SM-N9005 using XDA Premium 4 mobile app
alray said:
Locking the bootloader is only needed if you want to go back to stock using a RUU. I don't know if its what you have tried to do or any other method (guru reset rom, nandroid backup, stock odexed rom, Ruu.zip or ruu.exe?) The output of "fastboot getvar all" could help (dont post IMEI and SN) + what recovery and version # are you using?
bootloader can't wipe anything by itself. You probably did something wrong, can't tell you what at this point.
Which one? You need to be more precise i.e I tried to adb push X rom X version #.
Again, be more precise. What was the error code/message? + post a screenshot of the cmd prompt when it fail
Stop rushing things, or you'll probably make the situation worst. We will help you step by step if needed.
Probably but:
what is your goal? you want to flash a custom rom or return back to stock rom?
Post the output of fastboot getvar all excluding imei and sn
what is your recovery + what is the version?
post a picture of the bootloader screen
when you speak about a rom/recovery always be specific what name and version
Click to expand...
Click to collapse
i atached up a few pictures about my phone you can read there what are they
i just want my phone back to life no matter if stock or custom
thank you
Laurentiu27 said:
ok got my htc one back still dead
im using twrp recovery latest one
now pls guide me step by step how to do it
i don't care if is a custom or stock just want my htc back to life
Click to expand...
Click to collapse
@alray asked for more info:
* Post the output of fastboot getvar all excluding imei and sn
* what is your recovery + what is the version?
* post a picture of the bootloader screen
* when you speak about a rom/recovery always be specific what name and version
and "latest" is not a version, you need to post a real version number and link to location/thread where you got your files from (both recovery and ROM)
this is the data from fastboot getvar all
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__032
battery-status: good
battery-voltage: 3750mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e47fb74b
hbootpreupdate: 11
gencheckpt: 0
im using twrp 2.7.1.1
custom rom android revolution hd 71.1
nkk71 said:
@alray asked for more info:
* Post the output of fastboot getvar all excluding imei and sn
* what is your recovery + what is the version?
* post a picture of the bootloader screen
* when you speak about a rom/recovery always be specific what name and version
and "latest" is not a version, you need to post a real version number and link to location/thread where you got your files from (both recovery and ROM)
Click to expand...
Click to collapse
this is the data from fastboot getvar all
version: 0.5
version-bootloader: 1.57.0000
version-baseband: 4T.27.3218.14
version-cpld: None
version-microp: None
version-main:
version-misc: PVT SHIP S-ON
serialno:
imei:
meid: 00000000000000
product: m7_ul
platform: HBOOT-8064
modelid: PN0710000
cidnum: HTC__032
battery-status: good
battery-voltage: 3750mV
partition-layout: Generic
security: on
build-mode: SHIP
boot-mode: FASTBOOT
commitno-bootloader: dirty-e47fb74b
hbootpreupdate: 11
gencheckpt: 0
im using twrp 2.7.1.1
custom rom android revolution hd 71.1
and tere is a few post earlier 3 pictures one about bootloader one about booting the rom and last is the twrp
this is the thread of the rom http://forum.xda-developers.com/showthread.php?t=2183023
Laurentiu27 said:
i atached up a few pictures about my phone you can read there what are they
i just want my phone back to life no matter if stock or custom
thank you
Click to expand...
Click to collapse
download twrp recovery 2.6.3.3 and save it to your adb/fastboot folder.
Make sure md5 match: 72067aefb69541d40e8420d7aa46408d
plug your phone to your computer and boot it in bootloader
open a command prompt from your adb/fastboot folder
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-booloader
now download this rom and save it to your adb/fastboot folder
Make sure md5 match:: CCC848CBF2B74C5FA33FD7E2269B0499
boot your phone in twrp recovery main menu
open a command prompt from your adb/fastboot folder
Code:
adb push Android_Revolution_HD-One_71.1.zip /sdcard/
wait for the file to transfer, there is no progress bar, just wait until adb show the file transfer is completed (5-10 min)
then in twrp, select ''install'' browse the sdcard content and select "Android_Revolution_HD-One_71.1.zip"
and swipe to confirm flash. When asked to wipe your phone, select yes.
reboot phone to OS and see if it works or not.
@nkk71 is it fine to flash arhd with twrp 2.7.1.1 or should it still be done using 2.6.3.3/.4 ?
alray said:
@nkk71 is it fine to flash arhd with twrp 2.7.1.1 or should it still be done using 2.6.3.3/.4 ?
Click to expand...
Click to collapse
many have said 2.7.1.1 works fine, i haven't tried and am quite happy with 2.6.3.3... the 2.7 series not only had problems with flashing and charging, but also nandroids, but not sure about 2.7.1.1
but from the 3rd screenshot of the OP, that doesn't look like an m7 ROM, the bootanimation is distorted indicated it's not for 1080x1920 display.
PS: he should also format data, system and cache within twrp 2.6.3.3
alray said:
download twrp recovery 2.6.3.3 and save it to your adb/fastboot folder.
Make sure md5 match: 72067aefb69541d40e8420d7aa46408d
plug your phone to your computer and boot it in bootloader
open a command prompt from your adb/fastboot folder
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.3-m7.img
fastboot erase cache
fastboot reboot-booloader
now download this rom and save it to your adb/fastboot folder
Make sure md5 match:: CCC848CBF2B74C5FA33FD7E2269B0499
this is what i get
adb push Android_Revolution_HD-One_71.1.zip /sdcard/
boot your phone in twrp recovery main menu
open a command prompt from your adb/fastboot folder
Code:
adb push Android_Revolution_HD-One_71.1.zip /sdcard/
wait for the file to transfer, there is no progress bar, just wait until adb show the file transfer is completed (5-10 min)
then in twrp, select ''install'' browse the sdcard content and select "Android_Revolution_HD-One_71.1.zip"
and swipe to confirm flash. When asked to wipe your phone, select yes.
reboot phone to OS and see if it works or not.
@nkk71 is it fine to flash arhd with twrp 2.7.1.1 or should it still be done using 2.6.3.3/.4 ?
Click to expand...
Click to collapse
this is what i get
adb push Android_Revolution_HD-One_71.1.zip /sdcard/
error:device not found
update:seems that now is pushing it
flashed now waiting to boot
nkk71 said:
many have said 2.7.1.1 works fine, i haven't tried and am quite happy with 2.6.3.3... the 2.7 series not only had problems with flashing and charging, but also nandroids, but not sure about 2.7.1.1
but from the 3rd screenshot of the OP, that doesn't look like an m7 ROM, the bootanimation is distorted indicated it's not for 1080x1920 display.
PS: he should also format data, system and cache within twrp 2.6.3.3
Click to expand...
Click to collapse
the image is when tries to boot but i can asure is 71.1 ARH i downloade it 4 times from their server
that is the image when it tries to boot i get that screen
Laurentiu27 said:
the image is when tries to boot but i can asure is 71.1 ARH i downloade it 4 times from their server
that is the image when it tries to boot i get that screen
Click to expand...
Click to collapse
check md5 and you'll know if its the right rom. must match the md5 value I posted above.
if it still dont work, do what nkk71 said above, format data cache and system. you'll have to push to rom again after formatting.
to format data, go in twrp, ''wipe'' ---> "Format data"
to format system and cache go in "wipe" --> advanced wipe --> select cache and system and swipe to wipe
then adb push the rom again and install it again.
From flash screenshots
Sent from my SM-N9005 using XDA Premium 4 mobile app
Laurentiu27 said:
From flash screenshots
Sent from my SM-N9005 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
so does it boot or not?
alray said:
so does it boot or not?
Click to expand...
Click to collapse
thank you!!! Thank you!!! It worked!!!
Laurentiu27 said:
thank you!!! Thank you!!! It worked!!!
Click to expand...
Click to collapse
:highfive:
Alright, I recently purchased a phone that was stuck at the screen with the download icon in the arrow circle (http://forum.xda-developers.com/album.php?albumid=11886). When it is like this is can not be put into hboot. I then somehow got the phone into a boot loop. I did wipe the cache and that did not fix the problem. I did a factory reset via hboot, and it sent me back to the screen I mentioned before (http://forum.xda-developers.com/album.php?albumid=11886). I've now gotten the phone back into boot looping so I can access hboot. Recovery does work and you can access all the options. This phone is basically a stock HTC One M7. Has not been rooted, is locked, and it S-ON. Any help would be appreciated.
Thank you!
Flash a RUU
jdgreat4 said:
Flash a RUU
Click to expand...
Click to collapse
Could you link me to a tutorial? Apparently I need to know my MID and CID, and the video I did find to do that, needed usb debugging turned on in the settings which I don't even know if that is on. Can you link me to a how to tutorial for how to do this?
CloudHD said:
Could you link me to a tutorial? Apparently I need to know my MID and CID, and the video I did find to do that, needed usb debugging turned on in the settings which I don't even know if that is on. Can you link me to a how to tutorial for how to do this?
Click to expand...
Click to collapse
post the output of "fastboot getvar all", remove your imei and serialno before posting it
alray said:
post the output of "fastboot getvar all", remove your imei and serialno before posting it
Click to expand...
Click to collapse
Do I need a computer to do this? There's no option for this under fastboot in hboot. Currently don't have a computer available to me.
CloudHD said:
Do I need a computer to do this? There's no option for this under fastboot in hboot. Currently don't have a computer available to me.
Click to expand...
Click to collapse
Yes you need a computer with the latest android sdk installed and latest HTC drivers installed.
Btw, why did you buy this phone?
alray said:
Yes you need a computer with the latest android sdk installed and latest HTC drivers installed.
Btw, why did you buy this phone?
Click to expand...
Click to collapse
I bought it for a friend. He wanted something other than his locked up att samsung s4 active. He doesn't have much money and he figured he could fix this one and if he could't, he would just sell it again. I am personally used to iPhones (typing this on a jailbroken 4s right now) so this is all pretty new to me. We started troublesing it yesterday and he seemed to get stumped. He hates forums so I went ahead and signed up and made this post for him. Currently I have no access to a computer right now (at least one where I can install sdk and so on), but will have access later today. Will post when I have it.
CloudHD said:
I bought it for a friend. He wanted something other than his locked up att samsung s4 active. He doesn't have much money and he figured he could fix this one and if he could't, he would just sell it again. I am personally used to iPhones (typing this on a jailbroken 4s right now) so this is all pretty new to me. We started troublesing it yesterday and he seemed to get stumped. He hates forums so I went ahead and signed up and made this post for him. Currently I have no access to a computer right now (at least one where I can install sdk and so on), but will have access later today. Will post when I have it.
Click to expand...
Click to collapse
Latest HTC driver here: http://www.mediafire.com/download/8pawcxm9walwras/HTC_Driver_4.14.0.001.exe
You can install minimal adb and fastboot instead of the complete sdk, will be easier to use for you: http://forum.xda-developers.com/showthread.php?t=2317790
Once you have both installed, connect the phone to your computer, make sure its booted in bootloader mode --> fastboot mode and showing "fastboot usb" in red.
On your computer: Start menu --> Programs --> Minimal adb and fasboot --> minimal adb and fastboot
in the command prompt, type:
Code:
fastboot getvar all
copy and paste the output here (except the imei and s/n)
see you later
alray said:
Latest HTC driver here: http://www.mediafire.com/download/8pawcxm9walwras/HTC_Driver_4.14.0.001.exe
You can install minimal adb and fastboot instead of the complete sdk, will be easier to use for you: http://forum.xda-developers.com/showthread.php?t=2317790
Once you have both installed, connect the phone to your computer, make sure its booted in bootloader mode --> fastboot mode and showing "fastboot usb" in red.
On your computer: Start menu --> Programs --> Minimal adb and fasboot --> minimal adb and fastboot
in the command prompt, type:
Code:
fastboot getvar all
copy and paste the output here (except the imei and s/n)
see you later
Click to expand...
Click to collapse
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(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) battery-status: good
(bootloader) battery-voltage: 3921mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
CloudHD said:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.502.2
(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) battery-status: good
(bootloader) battery-voltage: 3921mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Ok well there is no RUU you can use with s-on so while the bootloader is locked all you can do is try to flash the current firmware. If the phone doesn't boot after that you will need to unlock the bootloader.
Download the firmware here https://www.androidfilehost.com/?fid=23501681358543602 put the zip in your fastboot folder on your pc and rename it "firmware.zip" Now with fastboot usb connected in the bootloader flash the firmware with the following fastboot commands
Code:
fastboot erase cache
fastboot oem rebootRUU
case sensitive
Your phone will reboot to a black screen with silver HTC logo. This is ruu mode we can now flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash is just a pre-update. The screen will go off and then return to ruu mode. Flash the zip again immediately.
Code:
fastboot flash zip firmware.zip
The second flash will flash the firmware, the progress bar on the screen will not reach 100% this is normal as long as the command line has finished it's output it's done.
Code:
fastboot reboot-bootloader
Now try to reboot the phone. If it doesn't boot you should now at least be able to do a factory reset. But you will need to unlock the bootloader at www.htcdev.com register an account and follow the instructions in the Unlock My Bootloader section. :good:
Danny201281 said:
Ok well there is no RUU you can use with s-on so while the bootloader is locked all you can do is try to flash the current firmware. If the phone doesn't boot after that you will need to unlock the bootloader.
Download the firmware here https://www.androidfilehost.com/?fid=23501681358543602 put the zip in your fastboot folder on your pc and rename it "firmware.zip" Now with fastboot usb connected in the bootloader flash the firmware with the following fastboot commands
Code:
fastboot erase cache
fastboot oem rebootRUU
case sensitive
Your phone will reboot to a black screen with silver HTC logo. This is ruu mode we can now flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash is just a pre-update. The screen will go off and then return to ruu mode. Flash the zip again immediately.
Code:
fastboot flash zip firmware.zip
The second flash will flash the firmware, the progress bar on the screen will not reach 100% this is normal as long as the command line has finished it's output it's done.
Code:
fastboot reboot-bootloader
Now try to reboot the phone. If it doesn't boot you should now at least be able to do a factory reset. But you will need to unlock the bootloader at www.htcdev.com register an account and follow the instructions in the Unlock My Bootloader section. :good:
Click to expand...
Click to collapse
Followed your instructions. Everything went good. I did a factory reset and the phone actually ended up rebooting. It's now just sitting here, and seems to be stuck at the htc logo. Going to go ahead and follow the steps to unlock my bootloader then report back.
@Danny201281 Boot loader is now unlocked!
CloudHD said:
@Danny201281 Boot loader is now unlocked!
Click to expand...
Click to collapse
Now the bootloader is unlocked you will need to flash a custom recovery and install a new Rom.
Download this http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.8.5.0-m7.img *<<<<< Put this in your fastboot folder and rename it recovery.img
Download this https://www.androidfilehost.com/?fid=23501681358545274
Boot the device to the bootloader and connect fastboot usb. Flash the recovery with fastboot
Code:
fastboot erase cache
fastboot flash recovery recovery.img
fastboot reboot-bootloader
When back in the bootloader select Recovery from the menu to load TWRP recovery. Before we do anything else a little spring cleaning. Select "Wipe" from the TWRP menu the "Format Data" You will be prompted to type yes to continue. When its done Select "Reboot" then "Reboot Recovery" You will see a message "No OS Installed" Reboot anyway and say No when asked to install supersu.
Now back in TWRP recovery you should be able to see the Internal Storage on your PC. Copy the rom file to the Internal Storage then from the TWRP menu select install and choose the rom .zip :good:
During the install with Aroma choose these options
Stock Radio = Yes
Stock Recovery = Yes
Root = No
When the install is completed reboot the device and hopefully it should boot up normally without any problems :good: :fingers-crossed:
P.S The first boot after a new flash can take an extended amount of time. Don't be supprised if it's stuck on the HTC logo screen for 15 minutes+ Just be patient
Danny201281 said:
Now the bootloader is unlocked you will need to flash a custom recovery and install a new Rom.
Download this http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.8.5.0-m7.img *<<<<< Put this in your fastboot folder and rename it recovery.img
Download this https://www.androidfilehost.com/?fid=23501681358545274
Boot the device to the bootloader and connect fastboot usb. Flash the recovery with fastboot
Code:
fastboot erase cache
fastboot flash recovery recovery.img
fastboot reboot-bootloader
When back in the bootloader select Recovery from the menu to load TWRP recovery. Before we do anything else a little spring cleaning. Select "Wipe" from the TWRP menu the "Format Data" You will be prompted to type yes to continue. When its done Select "Reboot" then "Reboot Recovery" You will see a message "No OS Installed" Reboot anyway and say No when asked to install supersu.
Now back in TWRP recovery you should be able to see the Internal Storage on your PC. Copy the rom file to the Internal Storage then from the TWRP menu select install and choose the rom .zip :good:
During the install with Aroma choose these options
Stock Radio = Yes
Stock Recovery = Yes
Root = No
When the install is completed reboot the device and hopefully it should boot up normally without any problems :good: :fingers-crossed:
P.S The first boot after a new flash can take an extended amount of time. Don't be supprised if it's stuck on the HTC logo screen for 15 minutes+ Just be patient
Click to expand...
Click to collapse
Thank you! My friend wanted to ask about soff and root for his device
CloudHD said:
Thank you! My friend wanted to ask about soff and root for his device
Click to expand...
Click to collapse
For s-off he will have to use Sunshine App it's the only working method for hboot 1.57. It does cost $25 but It's very easy. Just install and run the app :good:
Rooting can be done a number of ways the 2 easiest are to allow TWRP to install SupeSu when leaving recovery. Or you can install root with the Guru reset rom by selecting root during the installer. Also if he want's to keep the TWRP recovery don't take the stock recovery during the rom install.
Danny201281 said:
For s-off he will have to use Sunshine App it's the only working method for hboot 1.57. It does cost $25 but It's very easy. Just install and run the app :good:
Rooting can be done a number of ways the 2 easiest are to allow TWRP to install SupeSu when leaving recovery. Or you can install root with the Guru reset rom by selecting root during the installer. Also if he want's to keep the TWRP recovery don't take the stock recovery during the rom install.
Click to expand...
Click to collapse
alright. when formatting, I have been getting an unable to mount /cache and /system. should i be worries. Also, so when I do install the supesu? Can you give me some more detailed instructions like you have been doing? They're very helpful!!2220
CloudHD said:
alright. when formatting, I have been getting an unable to mount /cache and /system. should i be worries. Also, so when I do install the supesu? Can you give me some more detailed instructions like you have been doing? They're very helpful!!2220
Click to expand...
Click to collapse
Unable to mount /cache and /system happens during format or after? Did you reboot recovery after the format?
When you exit recovery TWRP will detect wheather or not the device is rooted. If it's not rooted TWRP will ask if you want to install supersu to root the phone. Say yes and TWRP will install root.
Although you could just install root when you install the rom. Just install with these options instead
Stock = Recovery No
Stock = Radio Yes
Root = Yes
Danny201281 said:
Unable to mount /cache and /system happens during format or after? Did you reboot recovery after the format?
When you exit recovery TWRP will detect wheather or not the device is rooted. If it's not rooted TWRP will ask if you want to install supersu to root the phone. Say yes and TWRP will install root.
Although you could just install root when you install the rom. Just install with these options instead
Stock = Recovery No
Stock = Radio Yes
Root = Yes
Click to expand...
Click to collapse
It seems to say this while it is updating partition details. Havent rebooted it as I wasn't sure about the cache and everything. So I guess before.
CloudHD said:
It seems to say this while it is updating partition details. Havent rebooted it as I wasn't sure about the cache and everything. So I guess before.
Click to expand...
Click to collapse
Reboot Recovery and then copy over and install the rom :good:
When you format data it is like repartitioning the phone. All the partitions are gone until you reboot. That's the reason they won't mount
Danny201281 said:
Reboot Recovery and then copy over and install the rom :good:
Click to expand...
Click to collapse
Alright, Thank you very much!!!
Will update how it all wetn when finished.
THIS IS A GUIDE ON HOW TO INSTALL THE LOLLIPOP OTA UPDATE ON A ROOTED INTERNATIONAL HTC ONE M7 WITH A CUSTOM RECOVERY AND A STOCK HTC SENSE ROM
Disclaimer: I am making this guide to help you if I can. I am doing that because I have spent more than 10 hours trying to upgrade my phone; and because I am new at this, I soft bricked my phone. I did unbrick it and install lollipop eventually but I am making this for the people like me, so that you don’t make the same mistakes. Oh, and, never tick “system” when doing a wipe trough TWRP recovery XD With that said, I am not a pro, but I have learned a lot trough trial and error; so, follow the instructions carefully and be patient!!! I am not responsible if something goes horrendously wrong, good luck! Also, sorry for the weird formatting, I am very new to that as well.
Hey everybody, as you probably know, HTC has started rolling out Lollipop to M7s.
If you are like me and love to have control over your phone and its customization, you probably rooted your device and installed a custom recovery to have more options like full system backups...
Well, now that the update is out, you might have tried to upgrade following the on screen instructions for the OTA (Over The Air) update and found out it can’t be done just like that. I am here to tell you, don’t worry, don’t bang your head against the table, there is a way, and it is simple. This is a collection of some of the things that I have learned in the previous two days:
You will need a couple of things:
*Your International HTC One M7
You can be S-OFF OR S-On
*The Android SDK
Your alternative would be the Minimal ADB and Fastboot because that’s the part of the sdk we will be using for this. I recommend the SDK if you don’t quite now what you are doing because I will be explaining how to use that, otherwise, feel free to use the Minimal ADB and Fastboot. But, if you are going to use the Minimal ADB and Fastboot don’t forget to create a desktop shortcut, it will make things easier later.
*The OTA zip itself
We will need this to get the stock recovery image, I will explain why soon.
*Your htcdev.com account
We will need it to unlock your boot loader later because in order to complete this, you will
temporarily relock your bootloader.
*Your phones drivers ( If you do install the drivers I linked, you should probably uninstall HTC sync,
just to be on the safe side)
*Your PC (I will write for Windows because that’s what I have)
THE LINKS TO EVERYTHING YOU NEED:
-The Tools:
Android SDK (Android Sutdio): http://developer.android.com/sdk/index.html
Minimal ADB and Fastboot: http://forum.xda-developers.com/showthread.php?t=2317790
-The phone drivers:
https://www.youtube.com/watch?v=afrvSGiMAtk (This video is really good, it shows you how you can get the drivers to work so that adb recognizes your phone even in recovery, it is useful for side loading and stuff... I recommend doing this just to be safe, you can install HTC sync later if you want)
Ok, let’s begin:
1. Download the OTA zip file on to your phone as you normaly would, but don’t click install. Instead, copy the file to a folder on your desktop (name the folder what you want).
2. Right click the zip and click “Extract to .......” (with the ..... being the name of the OTA file)
3. In there, there will be another zip file called “firmware.zip”
4. Extract that one, we will use it to get the stock recovery. Why do we need the stock recovery if the custom one is better? We need it to install the OTA update because of the way that OTA files are made and the way that the stock recovery works. The stock recovery is made to do two things, preform a factory reset and to install OTA updates. The OTA update zips are made to be only installed trough the stock recovery. I don’t know why, but that’s what I found out, simple as that.
5. Now, Copy that recovery.img file back in to the main folder on your desktop (you don't need the OTA zip on your computer anymore, if you want delete it)
6. In order to apply the OTA update file, you will need to temporaroly relock your bootloader and flash the stock recovery. To do that:
1) Boot your phone in to the bootloader by holding Vol Down + Power
2) Navigate with the volume keys and click the power button to select. Select the “fastboot mode” it should show up red and say fastboot. (fastboot usb if connected to pc)
3) Connect the phone to the PC via USB 2.0 (USB 3.0 might not work)
4) Go to folder where you installed Android SDK and go in to the “platform-tools” folder and while holding shift right click in the empty space of the folder and click open command window here .
5) Type in “fastboot devices” (witouth the quote marks) this will make sure your PC sees your phone.
If a radnom set of numbers appears and by it fastboot or something like that, you are good, if not check the connection and the drivers. I will link to how to get drivers to work because there are known issues when using windows 8/8.1
6) Next thing is to copy the recovery file from the desktop folder in to the platform-tools folder.
7) Type in “fastboot flash recovery recovery.img”
8) Type in “fastboot reboot-bootloader”
9) Type in “fastboot oem lock” (This will lock the bootloader, we will unlock it again later)
7. Boot your phone up and normaly install the OTA update.
8. To reinstall the custom recovery, just download the latest TWRP or Clockworkmoad recovery for the M7 and copy it in to the platform tools folder. Boot the phone in to fastboot again and type in “fastboot flash recovery ****.img” (wher **** is the name of your custom recovery image)
9. To unlock your bootloader, do the same as you did the first tame you did it, follow the htcdev.com instructions. If you still have the unlock token, just put it in to the platform-tools folder. Boot in to fastboot and type in “fastboot flash unlocktoken Unlock_code.bin”
If for any reason you get into a boot loop, just reboot into recovery trough the bootloader and wipe cache and dalvik cache
That’s it, you should now have a rooted HTC One M7 running stock Lollipop sense.
And, some sugestions:
-Keep the stock recovery somewhere if you ever need it again. I say this because when I was searching for the stock recovery image, people were saying to download one from the internet but to be careful... That would be much more complicated because there is no guaranty that the recovery you download is right for your exact phone! This is the simplest way, and it is guarantied to work because in the OTA zip for your phone is the recovery that is made to work on your phone!
-Keep the unlocktoken in order to easily unlock your bootloader if you ever need to relock it again, it just saves you time.
MrSolution98 said:
THIS IS A GUIDE ON HOW TO INSTALL THE LOLLIPOP OTA UPDATE ON A ROOTED INTERNATIONAL HTC ONE M7 WITH A CUSTOM RECOVERY AND A STOCK HTC SENSE ROM
Disclaimer: I am making this guide to help you if I can. I am doing that because I have spent more than 10 hours trying to upgrade my phone; and because I am new at this, I soft bricked my phone. I did unbrick it and install lollipop eventually but I am making this for the people like me, so that you don’t make the same mistakes. Oh, and, never tick “system” when doing a wipe trough TWRP recovery XD With that said, I am not a pro, but I have learned a lot trough trial and error; so, follow the instructions carefully and be patient!!! I am not responsible if something goes horrendously wrong, good luck! Also, sorry for the weird formatting, I am very new to that as well.
Hey everybody, as you probably know, HTC has started rolling out Lollipop to M7s.
If you are like me and love to have control over your phone and its customization, you probably rooted your device and installed a custom recovery to have more options like full system backups...
Well, now that the update is out, you might have tried to upgrade following the on screen instructions for the OTA (Over The Air) update and found out it can’t be done just like that. I am here to tell you, don’t worry, don’t bang your head against the table, there is a way, and it is simple. This is a collection of some of the things that I have learned in the previous two days:
You will need a couple of things:
*Your International HTC One M7
You can be S-OFF OR S-On
*The Android SDK
Your alternative would be the Minimal ADB and Fastboot because that’s the part of the sdk we will be using for this. I recommend the SDK if you don’t quite now what you are doing because I will be explaining how to use that, otherwise, feel free to use the Minimal ADB and Fastboot. But, if you are going to use the Minimal ADB and Fastboot don’t forget to create a desktop shortcut, it will make things easier later.
*The OTA zip itself
We will need this to get the stock recovery image, I will explain why soon.
*Your htcdev.com account
We will need it to unlock your boot loader later because in order to complete this, you will
temporarily relock your bootloader.
*Your phones drivers ( If you do install the drivers I linked, you should probably uninstall HTC sync,
just to be on the safe side)
*Your PC (I will write for Windows because that’s what I have)
THE LINKS TO EVERYTHING YOU NEED:
-The Tools:
Android SDK (Android Sutdio): http://developer.android.com/sdk/index.html
Minimal ADB and Fastboot: http://forum.xda-developers.com/showthread.php?t=2317790
-The phone drivers:
https://www.youtube.com/watch?v=afrvSGiMAtk (This video is really good, it shows you how you can get the drivers to work so that adb recognizes your phone even in recovery, it is useful for side loading and stuff... I recommend doing this just to be safe, you can install HTC sync later if you want)
Ok, let’s begin:
1. Download the OTA zip file on to your phone as you normaly would, but don’t click install. Instead, copy the file to a folder on your desktop (name the folder what you want).
2. Right click the zip and click “Extract to .......” (with the ..... being the name of the OTA file)
3. In there, there will be another zip file called “firmware.zip”
4. Extract that one, we will use it to get the stock recovery. Why do we need the stock recovery if the custom one is better? We need it to install the OTA update because of the way that OTA files are made and the way that the stock recovery works. The stock recovery is made to do two things, preform a factory reset and to install OTA updates. The OTA update zips are made to be only installed trough the stock recovery. I don’t know why, but that’s what I found out, simple as that.
5. Now, Copy that recovery.img file back in to the main folder on your desktop (you don't need the OTA zip on your computer anymore, if you want delete it)
6. In order to apply the OTA update file, you will need to temporaroly relock your bootloader and flash the stock recovery. To do that:
1) Boot your phone in to the bootloader by holding Vol Down + Power
2) Navigate with the volume keys and click the power button to select. Select the “fastboot mode” it should show up red and say fastboot. (fastboot usb if connected to pc)
3) Connect the phone to the PC via USB 2.0 (USB 3.0 might not work)
4) Go to folder where you installed Android SDK and go in to the “platform-tools” folder and while holding shift right click in the empty space of the folder and click open command window here .
5) Type in “fastboot devices” (witouth the quote marks) this will make sure your PC sees your phone.
If a radnom set of numbers appears and by it fastboot or something like that, you are good, if not check the connection and the drivers. I will link to how to get drivers to work because there are known issues when using windows 8/8.1
6) Next thing is to copy the recovery file from the desktop folder in to the platform-tools folder.
7) Type in “fastboot flash recovery recovery.img”
8) Type in “fastboot reboot-bootloader”
9) Type in “fastboot oem lock” (This will lock the bootloader, we will unlock it again later)
7. Boot your phone up and normaly install the OTA update.
8. To reinstall the custom recovery, just download the latest TWRP or Clockworkmoad recovery for the M7 and copy it in to the platform tools folder. Boot the phone in to fastboot again and type in “fastboot flash recovery ****.img” (wher **** is the name of your custom recovery image)
9. To unlock your bootloader, do the same as you did the first tame you did it, follow the htcdev.com instructions. If you still have the unlock token, just put it in to the platform-tools folder. Boot in to fastboot and type in “fastboot flash unlocktoken Unlock_code.bin”
If for any reason you get into a boot loop, just reboot into recovery trough the bootloader and wipe cache and dalvik cache
That’s it, you should now have a rooted HTC One M7 running stock Lollipop sense.
And, some sugestions:
-Keep the stock recovery somewhere if you ever need it again. I say this because when I was searching for the stock recovery image, people were saying to download one from the internet but to be careful... That would be much more complicated because there is no guaranty that the recovery you download is right for your exact phone! This is the simplest way, and it is guarantied to work because in the OTA zip for your phone is the recovery that is made to work on your phone!
-Keep the unlocktoken in order to easily unlock your bootloader if you ever need to relock it again, it just saves you time.
Click to expand...
Click to collapse
You sir are a genius. I was just about to throw the phone and laptop out the window. 3 days of getting nowhere and then i found this. Thank you. Just have a question. What will happen now with further updates? HTC have only released 5.0 as far as i know but 5.1 has been rolled out to some already? Will future updates go back to normal?
:good:
Really interesting. Thanks
stef6692 said:
You sir are a genius. I was just about to throw the phone and laptop out the window. 3 days of getting nowhere and then i found this. Thank you. Just have a question. What will happen now with further updates? HTC have only released 5.0 as far as i know but 5.1 has been rolled out to some already? Will future updates go back to normal?
Click to expand...
Click to collapse
Hey, thank you! It really means a lot! I know the struggle of thinking you broke your very expensive smart phone... I soft bricked my phone after this by wiping everything trough the recovery because I didn't read what i checked on the wipe list... My phone is working now, I installed an aosp lollipop rom because I didn't like that htc stuck with sense 6 when releasing lollipop for the M7... I just felt it didn't have all the features I was looking for. To answer your question: go to this website (just copy it to a new window in your browser and delete the spaces; I can't post outside links yet...) http : // androidcommunity.com/ htc-one-m7-could-be-updated-to-android-5-1-20150323/
martin1984 said:
:good:
Really interesting. Thanks
Click to expand...
Click to collapse
Thank you. Glad I could help!
keep getting this error during flash.
system/lib/modules/ansi_cprng.ko has unexpected content, flash aborted
any help?
ljy1 said:
keep getting this error during flash.
system/lib/modules/ansi_cprng.ko has unexpected content, flash aborted
any help?
Click to expand...
Click to collapse
You have flashed a custom kernel. YOu have to restore your rom to 100% stock,
ljy1 said:
keep getting this error during flash.
system/lib/modules/ansi_cprng.ko has unexpected content, flash aborted
any help?
Click to expand...
Click to collapse
I think @alray is right. Do you have the OTA zip file? Because if you do, I think you can fix this problem by flashing the firmware.zip that is located in the ota zip. @alray am I correct? This came to mind because I had to do that when I was installing a new rom, it needed to have the stock firmware. If you do, and this is correct, come back to this thread and I will do my best to help you
MrSolution98 said:
I think @alray is right. Do you have the OTA zip file? Because if you do, I think you can fix this problem by flashing the firmware.zip that is located in the ota zip. @alray am I correct? This came to mind because I had to do that when I was installing a new rom, it needed to have the stock firmware. If you do, and this is correct, come back to this thread and I will do my best to help you
Click to expand...
Click to collapse
Flashing the stock firmware won't change anything to /system. He must restore the stock rom because his custom kernel made some changes in /system.
alray said:
Flashing the stock firmware won't change anything to /system. He must restore the stock rom because his custom kernel made some changes in /system.
Click to expand...
Click to collapse
Hmmm :silly: @alray Maybe he could try the Android Revolution Rom, it is basically stock lollipop sense. I have tried it as well as the original software, didn't run into any differences or problems... Maybe that would be easier than trying to find the original software for his specific phone... I managed to sideload this rom using twrp when my phone was soft bricked... So, I think flashing the rom won't be a problem if he has a working phone. But, also, I think he will have to flash the firmware.zip to install this rom, that's what I was talking about earlier,
MrSolution98 said:
Hmmm :silly: @alray Maybe he could try the Android Revolution Rom, it is basically stock lollipop sense. I have tried it as well as the original software, didn't run into any differences or problems... Maybe that would be easier than trying to find the original software for his specific phone...
Click to expand...
Click to collapse
It might be really easy to find the original rom for his phone, its all depend what version he is currently on. I agree that if he can't find it, using a custom rom like arhd is good alternative. We can help him find the required files (if they exist) but he will first need to post the output of "fastboot getvar all"
alray said:
It might be really easy to find the original rom for his phone, its all depend what version he is currently on. I agree that if he can't find it, using a custom rom like arhd is good alternative. We can help him find the required files (if they exist) but he will first need to post the output of "fastboot getvar all"
Click to expand...
Click to collapse
Okay, and thanks for the replies! I am relatively new to this and want to learn something from this If and when he does do that, we will continue this
Also, I don't know about finding the software for his specific phone being easy... Could you explain? @alray When I was looking for the software for my phone I read about the CID number having to mach up and that the phones, even though they are from the same variant, they are different for different parts of the world... I couldn't even manage to find the recovery.img that worked on my phone... That's why I think I was lucky to have the ota zip on my computer... I found the stock recovery and the firmware zip which I needed later on... From all that, I kinda got the impression that finding the exact software is not impossible but hard if you don't understand what exactly you are looking for... That's why I would recommend arhd if you just want the stock experience but don't want to mess around too much.
Goofed during recovery replacement
Alray, I accidentally flashed boot instead of recovery in an attempt to get the LP OTA going. I can't find a replacement to get it working again. I used a Guru Reset zip, but after the first reboot, it took me to a jacked boot img. What can I do. I really just want AT&T Lollipop.
C:\Users\markm_000\Dropbox\Apps\HTCOne>fastboot.exe
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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) battery-status: good
(bootloader) battery-voltage: 4312mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
mmccurdy said:
Alray, I accidentally flashed boot instead of recovery in an attempt to get the LP OTA going. I can't find a replacement to get it working again. I used a Guru Reset zip, but after the first reboot, it took me to a jacked boot img. What can I do. I really just want AT&T Lollipop.
C:\Users\markm_000\Dropbox\Apps\HTCOne>fastboot.exe
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4M.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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) battery-status: good
(bootloader) battery-voltage: 4312mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-1f512bb6
(bootloader) hbootpreupdate: 11(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Lock your bootloader and run the RUU from this post.
Was desperate for a quick fix
majmoz said:
Lock your bootloader and run the RUU from this post.
Click to expand...
Click to collapse
Thanks. In the meantime, I only found salvation by installing a generic rom, S-OFF'ing, changing the CID/MID, and using the developer RUU. I couldn't find the RUU for my particulars.. I should probably switch back to S-ON unless there's a good reason to leave it.
can u help me
after i received lollipop update in my brother M7 DUAL SIM
i successfully downloaded it , and when i press install now the phone reboot to bootloader and nothing happens
i tried this more than one time and every time it take me to bootloader
can u help me ....
i tried ur method but nothing change
TAMPERED
RELOCKED
security warning
M7CDUG PVT SHIP S-ON RL
HBOOT-2.49.0000
RADIO-U3.15.3509.12
phone never rooted
and i have no recovery " when i try to enter recovery from bootloader nothing happen
Possibly a stupid question, but:
Will this wipe the user data from the phone? I don't see why reverting to stock would do that, but doesn't using the HTCDevs to unlock the bootloader wipe the phone?
Thanks!
toycar69 said:
Possibly a stupid question, but:
Will this wipe the user data from the phone? I don't see why reverting to stock would do that, but doesn't using the HTCDevs to unlock the bootloader wipe the phone?
Thanks!
Click to expand...
Click to collapse
What is your situation and your goal exactly? You might not need to follow this guide.
Yes unlocking the bootloader wipe the phone
Hi Alray,
my current situation is I have an HTC M7, S-OFF and rooted, running stock ROM on Android 4.4.4 and TWRP recovery. I've been holding back, but now I'd like to try the stock Lollipop upgrade. I have no modifications to the system partition, except the SuperSU binary.
Is it possible for me to just flash the stock recovery and run the OTA then?
Thanks!
toycar69 said:
Hi Alray,
my current situation is I have an HTC M7, S-OFF and rooted, running stock ROM on Android 4.4.4 and TWRP recovery. I've been holding back, but now I'd like to try the stock Lollipop upgrade. I have no modifications to the system partition, except the SuperSU binary.
Is it possible for me to just flash the stock recovery and run the OTA then?
Thanks!
Click to expand...
Click to collapse
I would indeed try to do this first as it will only take you 5 minutes to flash the stock recovery back. If the ota fails (red triangle) then its because something isn't 100% stock and you'll have to flash a lollipop RUU.
Hi,
I've kind of soft bricked my phone. Good thing is still able to fastboot as my PC detects it via USB.
I am new to Android rooting, flashing etc.
I had android Lollipop before I messed up phone. I've downloaded Nandroid backup and RUU for Indian version of HTC One 802d from other threads on XDA.
I am not sure of process to use that Nandroid backup. I've CWM recovery but don't have root access. Bootloader iss unlocked.
For other thing i.e. RUU that I downloaded is a zip file. But for some strange reason I'm not able to extract it on windows 7. It says compressed zip folder is invalid. I also downloaded Chinese RUU which is again zip and doesn't extarct, gives same error.
I am new to all this though I've some knowledge about computers and gadgets.
Please help me on how to get back my phone working may by Nandroid or RUU or anything else.
Please let me know if any details or information is needed.
Greatly appreciate any help in this regard. Thank you!
Hi,
Can someone please help me with this? :crying:
First of all, you can't unzip RUU.zip because it's encrypted. And why are you trying to unzip it anyway? Other thing - your phone is most likely S-on, so, in order to flash RUU.zip, you need stock recovery and locked or relocked bootloader. My suggestion is to go and do some reading on how to flash RUU. There are loads of tutorials online. And make sure you understand everything before you go ahead with flashing
donkeykong1 said:
First of all, you can't unzip RUU.zip because it's encrypted. And why are you trying to unzip it anyway? Other thing - your phone is most likely S-on, so, in order to flash RUU.zip, you need stock recovery and locked or relocked bootloader. My suggestion is to go and do some reading on how to flash RUU. There are loads of tutorials online. And make sure you understand everything before you go ahead with flashing
Click to expand...
Click to collapse
Thanks a lot for your reply!
Okay I get a point about RUU.zip not opening. I was trying it at first place cause I saw it some video that he opens it and then runs a setup file in it which opens windows wizard which then guides step by step to flash RUU from GUI.
Yes, my phone is S-On and I've been doing quite a lot reading since past couple of days and understading things better with every reading.
Now, I need further help. I'll first briefly explain how I messed up my phone. I had android L with Sense 6 in my cellphone before I started playing with it and decided to root. After watching few tutorials I first unlocked Bootloader then flashed cwm recovery. After that I took a backup from cwm and then installed SuperSu.zip from cwm recovery and rebooted phone normally. It started but SuperSu installed earlier was stopping regularly throwing error messages. I also downloaded rootChecker app and it showed that I didn't have root access.
Here, I slightly panicked as this is first time I was playing around with it. I rebooted my phone, went to cwm recovery and tried restoring back up that I took earlier as said above. But I didn't have root access and since then my phone went in bootloop and not starting.
My PC detects it when I connect in fastboot USB and i am able to execute fastboot commands.
=======================================================================================
Now, I,ll explain steps I am following to get my phone working :
1) I downloaded few RUU zip latest being from here --> http://www.mediafire.com/download/k...1_09B_release_391798_signed+by+jamesjerss.zip
2) Downloaded stock recovery for KITKAT from other xda thread --> http://forum.xda-developers.com/showthread.php?t=2617159
3) flashed this stock recovery then relocked my phone. fastboot oem lock.
4) executed fastboot oem rebootRUU
5) executed fastboot flash zip ruu.zip with the ruu zip downloaded in step 1 above
but it fails with version check failed , some error like this don't remember exact wording of it. I can get you that if needed by trying one more time.
Also, I can provide other information like getvar all and hboot version etc if required but kindly help me get out of this. Really appreciate your help.
I just want to highlight one more thing that I visited HTC care centre yesterday and without looking much at device just by looking at bootloader and cwm recovery he said that OS is corrupt and I'll need to replace mother board which costs half the price of phone. I don't believe him. It is just soft bricked and am able to connect in fastboot USB.
Please guide me on how to proceed further ahead.
Thank you once again!
<<Just getting you the output after running flash zip>>
C:\Users\OneDrivers_Fastboot\OneDrivers_Fastboot\Fastboot>fastboo
t flash zip ruukkn.zip
target reported max download size of 1542111232 bytes
sending 'zip' (1344718 KB)...
OKAY [ 75.112s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 190.871s
Post a fastboot getvar all please. Don't forget to remove your IMEI and serial no. That guy at HTC care is an idiot ?
donkeykong1 said:
Post a fastboot getvar all please. Don't forget to remove your IMEI and serial no. That guy at HTC care is an idiot
Click to expand...
Click to collapse
Lol. He certainly seems to be one.
Below is result of getvar all -->
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 2.49.0000
(bootloader) version-baseband: 2.04.30.0316
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.17.720.15
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: A1000037A674B4
(bootloader) product: m7cdwg
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0751000
(bootloader) cidnum: HTC__038
(bootloader) battery-status: good
(bootloader) battery-voltage: 4314mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d0e3b226
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
OK. The reason for "signature verify fail" error is because you're trying to flash older firmware than your current one. Find a matching or newer firmware, and flash away. Just don't unzip it ?
donkeykong1 said:
OK. The reason for "signature verify fail" error is because you're trying to flash older firmware than your current one. Find a matching or newer firmware, and flash away. Just don't unzip it
Click to expand...
Click to collapse
he he I won't do that definitely.
But earlier yesterday I had tried with Lollipop RUU downloaded from -->
androidfilehost.com/?fid=24052804347774374
but that too failed with similar signature verify fail.
What should I do?
<<<<<<<<<<<<<<Just to point out>>>>>>>>>>>>>>>>>>>>>>>>>>
Lollipop RUU that I downloaded is like PN07IMG_M7C_DWG_L50_SENSE60_MR_hTC_Asia_India_]7.17 .720.6_Radio_1237.29.35.0903 release_426120_signed.zip whereas from getvar results shared above it shows version like --> bootloader) version-main: 7.17.720.15
does it make a difference? if yes, that's the latest RUU I can find online.
How can I proceed in this scenario?
So, you can't flash a RUU, because there isn't one for your phone. Now, unlock your bootloader again, and flash TWRP recovery for your phone
donkeykong1 said:
So, you can't flash a RUU, because there isn't one for your phone. Now, unlock your bootloader again, and flash TWRP recovery for your phone
Click to expand...
Click to collapse
Okay but what after flashing TWRP recovery? How will it help?
yogeshchaudhari21 said:
Okay but what after flashing TWRP recovery? How will it help?
Click to expand...
Click to collapse
We'll find a TWRP nandroid backup and restore it [emoji6]
donkeykong1 said:
We'll find a TWRP nandroid backup and restore it [emoji6]
Click to expand...
Click to collapse
oh I see.
In that case I've CWM nandroid backup again downloaded from other XDA thread I shared earlier though it's for android 4.2.2
CWM Nandroid Backup (Android 4.2.2):
M7DWG_CWM_Nandroid_Backup_CID_HTC__038_2.37.720.1. zip - 998.74 MB
But as I'm doing all this for first time and am pretty much noob , I'm not sure how to use it to my benefit.
Can you please guide how can I use that nandroid back up to restore it in my phone?
Thank you!
yogeshchaudhari21 said:
oh I see.
In that case I've CWM nandroid backup again downloaded from other XDA thread I shared earlier though it's for android 4.2.2
CWM Nandroid Backup (Android 4.2.2):
M7DWG_CWM_Nandroid_Backup_CID_HTC__038_2.37.720.1. zip - 998.74 MB
But as I'm doing all this for first time and am pretty much noob [emoji14] , I'm not sure how to use it to my benefit.
Can you please guide how can I use that nandroid back up to restore it in my phone?
Thank you!
Click to expand...
Click to collapse
For that one you need CWM recovery. I'll be home in about 20 minutes and I'll walk you through the process
donkeykong1 said:
For that one you need CWM recovery. I'll be home in about 20 minutes and I'll walk you through the process
Click to expand...
Click to collapse
Oh sure! I'll be waiting.
I do have a cwm recovery although it's not touch version but that doesn't matter I guess.
Really appreciate your support. Thanks!
I'm back. did you flash the recovery yet?
donkeykong1 said:
I'm back. did you flash the recovery yet?
Click to expand...
Click to collapse
Hey hi!
Yes, I did.
yogeshchaudhari21 said:
Hey hi!
Yes, I did.
Click to expand...
Click to collapse
OK. Now enter your recovery and choose backup. Wait till it's done, so we can put your new backup in the same folder
donkeykong1 said:
OK. Now enter your recovery and choose backup. Wait till it's done, so we can put your new backup in the same folder
Click to expand...
Click to collapse
OMG something weird. Phone is not entering recovery after I flashed cwm recovery again. It's coming to bootloader but not going to recovery and just restarting. :| Let me keep trying.
yogeshchaudhari21 said:
OMG something weird. Phone is not entering recovery after I flashed cwm recovery again. It's coming to bootloader but not going to recovery and just restarting. :| Let me keep trying.
Click to expand...
Click to collapse
Did you unlock your bootloader again?
donkeykong1 said:
Did you unlock your bootloader again?
Click to expand...
Click to collapse
Yes I did unlock and then flashed recovery. I've been doing it quite a few times since yesterday so got used to it. This is something strange happening.