I have a US AT&T HTC ONE M7 that shipped to me.
I unrooted it fine using htcdev and getting the unlock_code.bin. Then I uploaded a recovery TWRP just fine and got in there and saw that it worked fine. Rebooted into normal and copyed the Revolution HD zip to my phone, but reading the thread it said that i needed to update my firmware.
I followed the guide it refferenced http://forum.xda-developers.com/showthread.php?t=2183023
To here http://forum.xda-developers.com/showthread.php?t=2182823
And it said to do the command to get your cid, which I did and got idnum: CWS__001
So I looked and found that I needed to get firmware.zip from 1.29.206.11
But the link on that page takes you to a firmware of 3.06.1700.01 or something close to that. I didn't notice the numbers were different so I did the flash with fimware 3.06.1700.01 instead of the 1.29.206. 11.
Booting the phone does nothing, it sits on the HTC one screen with Beats audio. Also the AT&T chimes no longer chime when on that page and then it just sits there. When booting with the down volume button I get a black screen instead of white screen. With a dead android on the bottom instead of the 3 little androids dancing (or whatever they are doing).
I was able to get recovery back and boot into recovery but I am not sure what to do.
WIth finding instructions I have tried to download a stock RUU which I found here.
http://forum.xda-developers.com/showthread.php?t=2428276
But without any instructions to use it. I assume you need to run it from TWRP recovery but I cannot get the computer to recognize the phone anymore as a drive in order to put the RUU on the phone
I just got this phone today and wanted to root it right away and I think I broke it already.
PLEASE HELP
Are you s-off?
Sent from my One using XDA Premium 4 mobile app
---------- Post added at 11:43 PM ---------- Previous post was at 11:41 PM ----------
When you flashed that firmware it also flashed a kernel so try to flash a working kernel
Sent from my One using XDA Premium 4 mobile app
dirtbikerr450 said:
Are you s-off?
Sent from my One using XDA Premium 4 mobile app
---------- Post added at 11:43 PM ---------- Previous post was at 11:41 PM ----------
When you flashed that firmware it also flashed a kernel so try to flash a working kernel
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Honestly I have no idea what that means. I have seen S-off and s-on but I am still a n00b. I have also edited my post above as I was able to get recovery installed again. It didn't before because I had relocked it and I unlocked it again
Now the issue is that I cannot get my computer to recognize the phone as a drive to put the RUU on it
Hold power and volume down and get to fastboot/bootloader
Sent from my One using XDA Premium 4 mobile app
dirtbikerr450 said:
Hold power and volume down and get to fastboot/bootloader
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I can get into that fastboot/bootloader but then what? I am here and again - it is a black screen with a dead android on the bottom which is not the same as the white screen I had before. Which clearly tells me something is wrong.
How do I load a stock kernel? Again, I have no access to the filesystem to put files onto the phone, only have access to using the commands like fastboot
I found a file on the internet
RUU_M7_UL_JB_50_Cingular.exe
Which i guess is for AT&T even thought it haven't been Cingular for years. And I go into this which says it is the HTC Android Phone ROM update utility 2.0.4.2013. Say yes to everything. It says it is going to go from 3.06.1700.10 to image version 1.26.502.12
Which is also an issue I think because the guide I found this on said that these numbers should be the same. This goes back to me flashing the 3.06.1700.10 instead of the correct firmware. I tell it to do it's thing but it errors out.
It says it will take about 10 minutes, so I wait - after about 5 minutes I get an error error [155] the ROM update utility cannot update your android phone. Please get the correct ROM update ulitity and try again.
Its an issue since 3.06 firmware is for Google play edition try to flash any other firmware to do the RUU
Sent from my One using XDA Premium 4 mobile app
---------- Post added at 12:15 AM ---------- Previous post was at 12:11 AM ----------
http://forum.xda-developers.com/showthread.php?t=2316726
Sent from my One using XDA Premium 4 mobile app
dirtbikerr450 said:
Its an issue since 3.06 firmware is for Google play edition try to flash any other firmware to do the RUU
Sent from my One using XDA Premium 4 mobile app
---------- Post added at 12:15 AM ---------- Previous post was at 12:11 AM ----------
http://forum.xda-developers.com/showthread.php?t=2316726
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I just tried another firmware from that page I referenced in the OP for "x.xx.401.x - World Wide English (WWE)"
http://forum.xda-developers.com/showthread.php?t=2182823
Which came out as 2.24.401.1 and when flashing it gives me the error. failed (remote: 41 model id check fail)
I also tried to get kernels from htcdev.com/devcenter/downloads
Downloaded 1.26.502.12 and 1.26.502.10 from this page and neither worked. Giving me the error failed (remote: 12 signature verify fail)
Flash this one http://click.xda-developers.com/api...l unmodified&jsonp=vglnk_jsonp_13785283880456
Sent from my One using XDA Premium 4 mobile app
dirtbikerr450 said:
Its an issue since 3.06 firmware is for Google play edition try to flash any other firmware to do the RUU
Sent from my One using XDA Premium 4 mobile app
---------- Post added at 12:15 AM ---------- Previous post was at 12:11 AM ----------
http://forum.xda-developers.com/showthread.php?t=2316726
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
dirtbikerr450 said:
Flash this one http://click.xda-developers.com/api...l unmodified&jsonp=vglnk_jsonp_13785283880456
Sent from my One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
OK, this file I downloaded - 1.29.401.12.zip
And it gave me the error FAILED (remote: 41 model id check fail)
I googled S-OFF and I am not S-OFF, my top of my phone says S-ON. I followed a guide to root my phone which the last step was to install SuperSU and it worked fine. SuperSU worked fine as well so I thought I was rooted. I don't know if I was S-OFF before I flashed the firmware that caused this whole thing or not.
AMDZen said:
OK, this file I downloaded - 1.29.401.12.zip
And it gave me the error FAILED (remote: 41 model id check fail)
Click to expand...
Click to collapse
You are s-on. You should not be able to flash any firmware that's not for your phone, but because the Google edition has the same model ID as the AT&T it allowed it. I've seen a few people do this. You can not go back because on hboot 1.54 there is no s-off. The firmware you've flashed is newer than AT&T's, and you can't downgrade without s-off.
Use the custom recovery to flash a custom ROM. It will work and your phone will be fine.
You will be stuck on the Google edition firmware until AT&T releases newer firmware, or someone accomplishes s-off on 1.54 Hboot.
In the future don't flash anything that you don't fully understand.
Edit:
I should also add that I also have an AT&T One. I'm running the newest InsertCoin on the 4.3 leaked base, and my phone also has Google's firmware on it from when I did the full conversion a while back, I can testify that everything works perfectly with the firmware.
Sent from my HTC One using XDA Premium 4 mobile app
AMDZen said:
OK, this file I downloaded - 1.29.401.12.zip
And it gave me the error FAILED (remote: 41 model id check fail)
Click to expand...
Click to collapse
Ok, I followed your info and found that you just flashed the 3.06 firmware package that has the stock Google Play kernel in it.
Everything is fine with your device, but that kernel is why your system won't boot. Since you already have AHRD installed simply flashing the stock kernel from ARHD will get your phone back to booting.
Do this:
Open the AHRD.zip (the rom you installed)
Inside that zip you should see boot.img (if it is not at the root of the zip search for it, windows can search through a zip file)
Extract that file to your fastboot/adb folder.
Then flash that kernel by connecting the USB while the dark bootloader screen is up and it should say Fastboot USB on the phone.
Now issue this command:
Code:
fastboot flash boot boot.img
If you do not have ADB/fastboot setup then just install this toolkit:
http://forum.xda-developers.com/showthread.php?t=2183942
Then open the tool and choose Flash a kernel from the Extra's section. It will want to reboot the phone into fastboot, so just close that window since you are already there and then it should prompt you for the location of that boot.img file I referenced earlier. It will then issue the fastboot command to flash the kernel. After that I bet your phone will boot normally.
If you have issues or questions, just let me know. If needed I could teamviewer into your system and have you running in a few minutes.
Best of luck.
Crush
crushalot said:
Ok, I followed your info and found that you just flashed the 3.06 firmware package that has the stock Google Play kernel in it.
Everything is fine with your device, but that kernel is why your system won't boot. Since you already have AHRD installed simply flashing the stock kernel from ARHD will get your phone back to booting.
Do this:
Open the AHRD.zip (the rom you installed)
Inside that zip you should see boot.img (if it is not at the root of the zip search for it, windows can search through a zip file)
Extract that file to your fastboot/adb folder.
Then flash that kernel by connecting the USB while the dark bootloader screen is up and it should say Fastboot USB on the phone.
Now issue this command:
Code:
fastboot flash boot boot.img
If you do not have ADB/fastboot setup then just install this toolkit:
http://forum.xda-developers.com/showthread.php?t=2183942
Then open the tool and choose Flash a kernel from the Extra's section. It will want to reboot the phone into fastboot, so just close that window since you are already there and then it should prompt you for the location of that boot.img file I referenced earlier. It will then issue the fastboot command to flash the kernel. After that I bet your phone will boot normally.
If you have issues or questions, just let me know. If needed I could teamviewer into your system and have you running in a few minutes.
Best of luck.
Crush
Click to expand...
Click to collapse
Wow. This is confusing. OK the thing I flashed that messed this up was the zip file 3.06.1700.10.zip - so I am assuming that is what you mean by my AHRD. I took that, took the boot.img file out of it by itself and did as you said
fastboot flash boot boot.img
sending 'boot' (5794 KB)...
OKAY [ 0.919s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.416s
EDIT: I realized I didn't do the reboot so I did
fastboot oem rebootRUU
And then did it again, but I still got an error
fastboot flash boot boot.img
< waiting for device >
sending 'boot' (5794 KB)...
OKAY [ 0.916s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 1.412s
CoryTallman said:
You are s-on. You should not be able to flash any firmware that's not for your phone, but because the Google edition has the same model ID as the AT&T it allowed it. I've seen a few people do this. You can not go back because on hboot 1.54 there is no s-off. The firmware you've flashed is newer than AT&T's, and you can't downgrade without s-off.
Use the custom recovery to flash a custom ROM. It will work and your phone will be fine.
You will be stuck on the Google edition firmware until AT&T releases newer firmware, or someone accomplishes s-off on 1.54 Hboot.
In the future don't flash anything that you don't fully understand.
Edit:
I should also add that I also have an AT&T One. I'm running the newest InsertCoin on the 4.3 leaked base, and my phone also has Google's firmware on it from when I did the full conversion a while back, I can testify that everything works perfectly with the firmware.
Sent from my HTC One using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I thought I did understand though. I didn't just dive into this, I researched everything all day and thought I had everything worked out. I first read teh instructions on Android Revolution HD which said that I needed to update the firmware, I followed those instructions as well and got:
fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.06.1700.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36KW901887
(bootloader) imei: 354439051471532
(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: 3890mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s
The cidnum that the page clearly references as needing the firmware I downloaded. Everything checked out. And now I am stuck.
Any way - I have done as you say and tried to install a ROM using fastboot as well. Keep in mind that I cannot load a ROM onto the phone and load the ROM using TWRP like all the guides I've seen say to do. I did
fastboot flash zip ROM.zip - the ROM being TrickDroid_10.0.0 and it didn't work:
fastboot flash zip ROM.zip
sending 'zip' (1068303 KB)...
OKAY [ 38.982s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 52.508s
crushalot said:
Ok, I followed your info and found that you just flashed the 3.06 firmware package that has the stock Google Play kernel in it.
Everything is fine with your device, but that kernel is why your system won't boot. Since you already have AHRD installed simply flashing the stock kernel from ARHD will get your phone back to booting.
Do this:
Open the AHRD.zip (the rom you installed)
Inside that zip you should see boot.img (if it is not at the root of the zip search for it, windows can search through a zip file)
Extract that file to your fastboot/adb folder.
Then flash that kernel by connecting the USB while the dark bootloader screen is up and it should say Fastboot USB on the phone.
Now issue this command:
Code:
fastboot flash boot boot.img
If you do not have ADB/fastboot setup then just install this toolkit:
http://forum.xda-developers.com/showthread.php?t=2183942
Then open the tool and choose Flash a kernel from the Extra's section. It will want to reboot the phone into fastboot, so just close that window since you are already there and then it should prompt you for the location of that boot.img file I referenced earlier. It will then issue the fastboot command to flash the kernel. After that I bet your phone will boot normally.
If you have issues or questions, just let me know. If needed I could teamviewer into your system and have you running in a few minutes.
Best of luck.
Crush
Click to expand...
Click to collapse
OK Update. I was able to flash the boot after unlocking my phone again:
fastboot oem rebootRUU
...
(bootloader) Start Verify: 3
OKAY [ 0.047s]
finished. total time: 0.048s
fastboot flash boot boot.img
sending 'boot' (5794 KB)...
OKAY [ 0.912s]
writing 'boot'...
OKAY [ 0.612s]
finished. total time: 1.529s
So I got that part done. I downloaded the tool and couldn't get that portion of your instructions to work. If you have the time, I installed teamviewer and set it up in my firewall so I would like to give that a try. Never used it before but I am desperate.
EDIT AGAIN: OK I got the ALL IN ONE Tool working. Apparently that doesn't run correctly if its in a folder that has a space in it. I changed the folder name that all this stuff was in to just one word no space and got it working:
sending 'boot' (5794 KB)...
OKAY [ 0.914s]
writing 'boot'...
OKAY [ 0.614s]
finished. total time: 1.530s
However the phone still doesn't boot - it still has no sound on the AT&T part of booting and then the next screen just sits there and does nothing
EDIT 2: OHHHHHHHHHHHH Light bulb went off. By AHRD you meant ARHD - meaning the custom ROM. Sadly - I never got this custom ROM installed. I was following the instructions on that site on what I needed:
Code:
You need:
HTC One unlocked with htcdev.com (S-ON) or S-OFF
Custom recovery
[B]Firmware package from here (recommended but not needed for now)[/B]
Read this flashing guide - [GUIDE] Complete Flashing Guide | Rooting | Going Back To Stock
It said recommended but not needed for now. I thought it was best to do it and that's what got me in the mess. The ROM on the phone is still whatever came from the factory.
AMDZen said:
Wow. This is confusing. OK the thing I flashed that messed this up was the zip file 3.06.1700.10.zip - so I am assuming that is what you mean by my AHRD. I took that, took the boot.img file out of it by itself and did as you said
fastboot flash boot boot.img
sending 'boot' (5794 KB)...
OKAY [ 0.919s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 1.416s
EDIT: I realized I didn't do the reboot so I did
fastboot oem rebootRUU
And then did it again, but I still got an error
fastboot flash boot boot.img
< waiting for device >
sending 'boot' (5794 KB)...
OKAY [ 0.916s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 1.412s
I thought I did understand though. I didn't just dive into this, I researched everything all day and thought I had everything worked out. I first read teh instructions on Android Revolution HD which said that I needed to update the firmware, I followed those instructions as well and got:
fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.18.3263.15
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.06.1700.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36KW901887
(bootloader) imei: 354439051471532
(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: 3890mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-94cf81a8fd
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s
The cidnum that the page clearly references as needing the firmware I downloaded. Everything checked out. And now I am stuck.
Any way - I have done as you say and tried to install a ROM using fastboot as well. Keep in mind that I cannot load a ROM onto the phone and load the ROM using TWRP like all the guides I've seen say to do. I did
fastboot flash zip ROM.zip - the ROM being TrickDroid_10.0.0 and it didn't work:
fastboot flash zip ROM.zip
sending 'zip' (1068303 KB)...
OKAY [ 38.982s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
FAILED (remote: 24 parsing android-info fail)
finished. total time: 52.508s
Click to expand...
Click to collapse
Hold on now. You are doing a lot things wrong, but the good news is since you are s-on, you can't screw up bad. I was talking about the kernel from the rom (Android_Revolution_HD-One_20.1.zip) which I thought you had installed already.
So do I understand correctly that you did the firmware update first before flashing the Android Revolution rom, so you have the stock software (rom) installed?
However you don't have the rom file (Android_Revolution_HD-One_20.1.zip) or any others on your sdcard?
You can't flash a rom (TrickDroid) in fastboot mode.
Why exactly can't you sideload or push a rom to install from TWRP which it sounds like you have installed? Does your touch interface work in TWRP recovery?
If it doesn't then you just need to flash the latest version. Sideload is ok but you might have better luck by putting the rom file in your adb folder and issue this command while the system is booted into twrp recovery:
Code:
adb push TrickDroid.zip /data/media/0/
Then the rom will be on the root of your sdcard partition and you can install with TWRP.
---------- Post added at 03:02 AM ---------- Previous post was at 02:59 AM ----------
I saw your edit, but I didn't have mine posted in time to let you know about the kernel. Your best bet now is to install a custom rom. I didn't realize you had relocked.
Let me know where your recovery stands and if you have a rom file on the sdcard.
crushalot said:
Hold on now. You are doing a lot things wrong, but the good news is since you are s-on, you can't screw up bad. I was talking about the kernel from the rom (Android_Revolution_HD-One_20.1.zip) which I thought you had installed already.
So do I understand correctly that you did the firmware update first before flashing the Android Revolution rom, so you have the stock software (rom) installed?
However you don't have the rom file (Android_Revolution_HD-One_20.1.zip) or any others on your sdcard?
You can't flash a rom (TrickDroid) in fastboot mode.
Why exactly can't you sideload or push a rom to install from TWRP which it sounds like you have installed? Does your touch interface work in TWRP recovery?
If it doesn't then you just need to flash the latest version. Sideload is ok but you might have better luck by putting the rom file in your adb folder and issue this command while the system is booted into twrp recovery:
Code:
adb push TrickDroid.zip /data/media/0/
Then the rom will be on the root of your sdcard partition and you can install with TWRP.
---------- Post added at 03:02 AM ---------- Previous post was at 02:59 AM ----------
I saw your edit, but I didn't have mine posted in time to let you know about the kernel. Your best bet now is to install a custom rom. I didn't realize you had relocked.
Let me know where your recovery stands and if you have a rom file on the sdcard.
Click to expand...
Click to collapse
Yes on the highlighted in both cases. I'm in LUCK. Thanks so much for your help. I took the boot.img out of the stock RUU - RUU_M7_UL_JB_50_Cingular - 1.26.502.12 - Decrypted.img and ran fastboot to flash that and it booted up. I am now on a working HTC ONE
:victory::highfive:
AMDZen said:
Yes on the highlighted in both cases. I'm in LUCK. Thanks so much for your help. I took the boot.img out of the stock RUU - RUU_M7_UL_JB_50_Cingular - 1.26.502.12 - Decrypted.img and ran fastboot to flash that and it booted up. I am now on a working HTC ONE
:victory::highfive:
Click to expand...
Click to collapse
Glad your back up.
crushalot said:
Glad your back up.
Click to expand...
Click to collapse
So now I have installed ARHD custom ROM using TWRP as well.
Based on everything that has happened and the things the other person was saying about being on a newer firmware. Are there any issues I should be aware of for having this going forward?
AMDZen said:
So now I have installed ARHD custom ROM using TWRP as well.
Based on everything that has happened and the things the other person was saying about being on a newer firmware. Are there any issues I should be aware of for having this going forward?
Click to expand...
Click to collapse
Just that you can't gain s-off until a new hack is discovered for hboot 1.54. Also I am not sure if it will allow you switch back to the HTC firmware (as opposed to the Google Edition which is an unbranded bootloader) when a new base is release since you have s-on. Shouldn't be a big deal. You will probably be able to run most roms on that firmware for a long time.
Related
Hello,
I unlocked my bootloader through HTC, placed TWRP in the same folder such as adb and then booted into it. However, when I try to run any of the options such as install, it prompts me to swipe to unlock but I'm unable to swipe to unlock.
I've found that if I press the hard home key, I can then swipe to unlock, but it acts as if I never selected an option. Has anyone had this happen?
rpinney said:
Hello,
I unlocked my bootloader through HTC, placed TWRP in the same folder such as adb and then booted into it. However, when I try to run any of the options such as install, it prompts me to swipe to unlock but I'm unable to swipe to unlock.
I've found that if I press the hard home key, I can then swipe to unlock, but it acts as if I never selected an option. Has anyone had this happen?
Click to expand...
Click to collapse
Make sure you have the right firmware/TWRP combination. 4.2.2 firmwares work with TWRP 2.6.0.1 (TWRP was updated to support the touch drivers in the 2.17 and 2.24 version firmwares. 4.1.2 firmwares work with an M7 specific version of TWRP 2.5.0.0.
dgtiii said:
Make sure you have the right firmware/TWRP combination. 4.2.2 firmwares work with TWRP 2.6.0.1 (TWRP was updated to support the touch drivers in the 2.17 and 2.24 version firmwares. 4.1.2 firmwares work with an M7 specific version of TWRP 2.5.0.0.
Click to expand...
Click to collapse
Crap. I'm using 2.6.0.0, but it was the one that was listed to use if you have a Sprint One. It didn't give an option to use .01.
rpinney said:
Crap. I'm using 2.6.0.0, but it was the one that was listed to use if you have a Sprint One. It didn't give an option to use .01.
Click to expand...
Click to collapse
Sprint is different, I am not sure of the version for your device if its Sprint. Did you check on the Sprint HTC One forum?
dgtiii said:
Sprint is different, I am not sure of the version for your device if its Sprint. Did you check on the Sprint HTC One forum?
Click to expand...
Click to collapse
I looked through and did a search, but I didn't see anything relevant. Should I repost in there?
rpinney said:
I looked through and did a search, but I didn't see anything relevant. Should I repost in there?
Click to expand...
Click to collapse
Yeah, I would repost there too!
dgtiii said:
Yeah, I would repost there too!
Click to expand...
Click to collapse
I actually ended up figuring out how to fix:
Version 2.6.0.0 from TWRP is bad. What you'll have to do is download 2.5.0.0. and put the recovery file into your android\sdk\platform-tools folder and use this command to push it to your phone: fastboot flash recovery openrecovery-twrp-2.5.0.0-m7wls.img.
Yep, that's how you flash a recovery. Good job, I'm glad you figured it out! Sorry I couldn't help more.
Stuck on twrp can't swipe
I really need help on this one. I been searching for the night till today morning and nver find a soulution to problem.
I have HTC One Lte. International since i bought it one of the mall in Qatar. Yesterday, i Decide to Unlock bootload and Root it. I use AIO 3.1.
Now its tampered and unlocked and select perm root.
I booted on system and find the SU is not intalled. So what i do is fastboot again and select perm. boot again. then i reboot after. Then After entering to twrp 2.5 recovery. I can swipe the screen. then i search and find 2.6.1.download it, but when i try connect it to AIO. Can find the my phone. So i decide to do it manually by going to cmd and push twrp 2.6.1.
Now when i booted, twrp is working well. i was able to back up. but after rebooting to system. twrp 2.5.0 open up. Now my phone running both twrp 2.5 and 2.6.1!
Thsi the detail of my phone.
(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.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4095mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Hope someone can help.
---------- Post added at 10:01 AM ---------- Previous post was at 09:57 AM ----------
By the way. Hope someone can tell me step by step on resolving this issue. i can only fast on cmd but not on AIO. I hope i didnt brick my phone.
Manay thanks for those will reply to my SOS!
blackknightrealms said:
I really need help on this one. I been searching for the night till today morning and nver find a soulution to problem.
I have HTC One Lte. International since i bought it one of the mall in Qatar. Yesterday, i Decide to Unlock bootload and Root it. I use AIO 3.1.
Now its tampered and unlocked and select perm root.
I booted on system and find the SU is not intalled. So what i do is fastboot again and select perm. boot again. then i reboot after. Then After entering to twrp 2.5 recovery. I can swipe the screen. then i search and find 2.6.1.download it, but when i try connect it to AIO. Can find the my phone. So i decide to do it manually by going to cmd and push twrp 2.6.1.
Now when i booted, twrp is working well. i was able to back up. but after rebooting to system. twrp 2.5.0 open up. Now my phone running both twrp 2.5 and 2.6.1!
Thsi the detail of my phone.
(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.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 4095mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d16dc66985
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Hope someone can help.
---------- Post added at 10:01 AM ---------- Previous post was at 09:57 AM ----------
By the way. Hope someone can tell me step by step on resolving this issue. i can only fast on cmd but not on AIO. I hope i didnt brick my phone.
Manay thanks for those will reply to my SOS!
Click to expand...
Click to collapse
So what version works? 2.6.0.1?
Which version does your phone boot into when you select 'recovery' in bootloader?
Can you still access your working phone/ROM?
blackknightrealms said:
I really need help on this one. I been searching for the night till today morning and nver find a soulution to problem.
I have HTC One Lte. International since i bought it one of the mall in Qatar. Yesterday, i Decide to Unlock bootload and Root it. I use AIO 3.1.
Now its tampered and unlocked and select perm root.
I booted on system and find the SU is not intalled. So what i do is fastboot again and select perm. boot again. then i reboot after. Then After entering to twrp 2.5 recovery. I can swipe the screen. then i search and find 2.6.1.download it, but when i try connect it to AIO. Can find the my phone. So i decide to do it manually by going to cmd and push twrp 2.6.1.
Now when i booted, twrp is working well. i was able to back up. but after rebooting to system. twrp 2.5.0 open up. Now my phone running both twrp 2.5 and 2.6.1!
---------- Post added at 10:01 AM ---------- Previous post was at 09:57 AM ----------
[/COLOR]By the way. Hope someone can tell me step by step on resolving this issue. i can only fast on cmd but not on AIO. I hope i didnt brick my phone.
Manay thanks for those will reply to my SOS!
Click to expand...
Click to collapse
I am not sure what you mean when you said you cannot connect to AIO, I assume you mean ADB. You may have to update your SDK files to get ADB to work.
Next issue. What do you mean when "So i decide to do it manually by going to cmd and push twrp 2.6.1". Fastboot flash recovery recovery.img is the command you need to upgrade your TWRP version (for example, fastboot flash recovery TWRP_2.6.0.1.img, or whatever the name of your TWRP file is). I think you still have TWRP version 2.5 installed, use the command I listed to install 2.6.01. Make sure the 2.6.0.1 file is in the same folder as your fastboot SDK files.
Thsi what happen. I use all in onw toolkit 3.1. done everything there.tampered and unlock.. I rebooted my One. then i see there is no supersu. so i fastboot again and push perm root on ALL in One toolkit. the reboot. then TWRP shown which i can't swipe. i fastboot again. then try connecting it again to AIO 3.1 but device not detected. So i decided by using adb by pushing TWRP 2.6.1 which i find. It load. go to recovery. backup.install SU. the reboot to to system. After it reboot to HTC logo. Then TWRP 2.5.0 showned next. then i can't swt to unlock or even the butoon are not running.
Apology. i kind noob in this way and trying to find answer for the pas 25 hrs. kinda paranoid. thanks for reply too. hope this can be solved
---------- Post added at 11:44 AM ---------- Previous post was at 11:37 AM ----------
redbull123 said:
So what version works? 2.6.0.1?
Which version does your phone boot into when you select 'recovery' in bootloader?
Can you still access your working phone/ROM?
Click to expand...
Click to collapse
2.6.01. is working. but when i boot to system. it rebooted back to 2.5.0
By using All in One tool kit. Not possible. but by using CMD line. I was able to access detail of my phone. how can i remove twrp 2.5??/
so 2.6.1 will be remain. Still now i can able to pass 2.5 to reboot on my phone..
---------- Post added at 11:50 AM ---------- Previous post was at 11:44 AM ----------
dgtiii said:
I am not sure what you mean when you said you cannot connect to AIO, I assume you mean ADB. You may have to update your SDK files to get ADB to work.
Next issue. What do you mean when "So i decide to do it manually by going to cmd and push twrp 2.6.1". Fastboot flash recovery recovery.img is the command you need to upgrade your TWRP version (for example, fastboot flash recovery TWRP_2.6.0.1.img, or whatever the name of your TWRP file is). I think you still have TWRP version 2.5 installed, use the command I listed to install 2.6.01. Make sure the 2.6.0.1 file is in the same folder as your fastboot SDK files.
Click to expand...
Click to collapse
i place 2.6.1 along side of c: android. Inside this folder are adb exe,adbwinapi.dll, fastboot and twrp 2.6.1. I already push this version and it work. but i thought it will over write twrp 2.5.
Should i put back the files inside the folder of skd??
Where is the command to install this 2.6.1 and over write or remove 2.5.?
blackknightrealms said:
Thsi what happen. I use all in onw toolkit 3.1. done everything there.tampered and unlock.. I rebooted my One. then i see there is no supersu. so i fastboot again and push perm root on ALL in One toolkit. the reboot. then TWRP shown which i can't swipe. i fastboot again. then try connecting it again to AIO 3.1 but device not detected. So i decided by using adb by pushing TWRP 2.6.1 which i find. It load. go to recovery. backup.install SU. the reboot to to system. After it reboot to HTC logo. Then TWRP 2.5.0 showned next. then i can't swt to unlock or even the butoon are not running.
Apology. i kind noob in this way and trying to find answer for the pas 25 hrs. kinda paranoid. thanks for reply too. hope this can be solved
---------- Post added at 11:44 AM ---------- Previous post was at 11:37 AM ----------
2.6.01. is working. but when i boot to system. it rebooted back to 2.5.0
By using All in One tool kit. Not possible. but by using CMD line. I was able to access detail of my phone. how can i remove twrp 2.5??/
so 2.6.1 will be remain. Still now i can able to pass 2.5 to reboot on my phone..
Click to expand...
Click to collapse
Ok, first of all - stop using the toolkit.
Go into fastboot in your bootloader so it shows 'FASTBOOT USB' then command
Code:
fastboot devices
If your device shows, command
Code:
fastboot erase cache
Once this is done, make sure your 2.6.0.1.img file is in your fastboot folder and command
Code:
fastboot flash recovery name_of_your_2.6.0.1_recovery.img
redbull123 said:
Ok, first of all - stop using the toolkit.
Go into fastboot in your bootloader so it shows 'FASTBOOT USB' then command
Code:
fastboot devices
If your device shows, command
Code:
fastboot erase cache
Once this is done, make sure your 2.6.0.1.img file is in your fastboot folder and command
Code:
fastboot flash recovery name_of_your_2.6.0.1_recovery.img
Click to expand...
Click to collapse
ok. this what i do as instructed.
C:\Android>fastboot devices
XXXXXXXXX fastboot
C:\Android>fastboot erase cache
erasing 'cache'...
OKAY [ 0.038s]
finished. total time: 0.038s
C:\Android>fastboot flash recovery openrecovery-twrp-2.6.0.1-m7.img
sending 'recovery' (8014 KB)...
OKAY [ 1.241s]
writing 'recovery'...
OKAY [ 0.648s]
finished. total time: 1.890s
then push power to hboot. then to recovery. Recover to twrp 2.6.1. ok.
first and second try. when i rebooted to system. it recover again to 2.5...
blackknightrealms said:
ok. this what i do as instructed.
C:\Android>fastboot devices
SH35XW900196 fastboot
C:\Android>fastboot erase cache
erasing 'cache'...
OKAY [ 0.038s]
finished. total time: 0.038s
C:\Android>fastboot flash recovery openrecovery-twrp-2.6.0.1-m7.img
sending 'recovery' (8014 KB)...
OKAY [ 1.241s]
writing 'recovery'...
OKAY [ 0.648s]
finished. total time: 1.890s
then push power to hboot. then to recovery. Recover to twrp 2.6.1. ok.
first and second try. when i rebooted to system. it recover again to 2.5...
Click to expand...
Click to collapse
Weird.. I've never heard of that.. So what is it you want to do while in 2.6.0.1? If it were me ( I'm not saying this is the correct answer), I would try flashing a stock ROM like this one then root it later:
http://forum.xda-developers.com/showthread.php?t=2224752
Or now might be a good chance for you to try out a close-to-stock custom ROM such as 'ARHD' which comes already rooted.
redbull123 said:
Weird.. I've never heard of that.. So what is it you want to do while in 2.6.0.1? If it were me ( I'm not saying this is the correct answer), I would try flashing a stock ROM like this one then root it later:
http://forum.xda-developers.com/showthread.php?t=2224752
Or now might be a good chance for you to try out a close-to-stock custom ROM such as 'ARHD' which comes already rooted.
Click to expand...
Click to collapse
Lets say your are me. Which is the best option. Anything support my current version? and will not give me head ache in the end but enjoy the phone?
Does this stock rom will do for my psoted version??pleaseeee! I need this phone!:crying:
Thanks in advance! and waiting for your recommendation.
well, using AIO toolkit and asb is not a good partner.
What do you think is common reason why i arrived to this?? I booted to my system before i reboot to 2.5 which i can't use. so thats why i try 2.6.1. And why this 2.5 kept staying on?? Does the procedure in flashing rom in AOI place it in different place so that this 2.6.1 seem can't over write it??
any one suggestion???
TWRP 2.6.1 and 2.5 on my ONE
Guys! any taker??? please share your knowledge on a noob like me. is there anyway i can remove TWRP 2.5 and leave TWRP 2.6.1?
Appreciate for a big help! thanks
blackknightrealms said:
Guys! any taker??? please share your knowledge on a noob like me. is there anyway i can remove TWRP 2.5 and leave TWRP 2.6.1?
Appreciate for a big help! thanks
Click to expand...
Click to collapse
Did you try flashing a rom like I said?
Sent from my HTC One using xda premium
redbull123 said:
Did you try flashing a rom like I said?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Bro. Do you think the present available rom should work on my unit specs?? Thats the only stopping me. i already collected and download needed files. But after i messed up my One. I have to make sure what step should i do. I will not blame it on anyone. Its really hard to read all post. its really quite long. Just only making sure that a same unit already installed with the same rom. But i'm still thinking which are better. but my first choice will ARHD. Since they put so much improvement. And I only making sure thats the last option i will take. If there is no other solution to resolve my present predicament then so be it. If i was able to flash back my stock rom. So please guide me if you don't mind. So what do you think bro?? Thanks again for responding to my SOS. Good day!
Hello
I have HTC one m7_u cid 332 hboot 1.55
For my phone there is no stock RUU searched every where
Phone is hang on HTC logo
I can go to fast boot menu tryed to unlock bootloader with htcdev but not work
My question is there any way to s-off or unlock boot loader without USB debugging on ?????
Tanx
afghan-gsm-mastermind said:
Hello
I have HTC one m7_u cid 332 hboot 1.55
For my phone there is no stock RUU searched every where
Phone is hang on HTC logo
I can go to fast boot menu tryed to unlock bootloader with htcdev but not work
My question is there any way to s-off or unlock boot loader without USB debugging on ?????
Tanx
Click to expand...
Click to collapse
bootloader is unlocked with fastboot not adb, so usb debugging is not required. Btw usb debugging only affect the usb connection when the phone is booted in the OS so its does not affect bootloader unlocking, fastboot commands or adb commands from recovery.
alray said:
bootloader is unlocked with fastboot not adb, so usb debugging is not required. Btw usb debugging only affect the usb connection when the phone is booted in the OS so its does not affect bootloader unlocking, fastboot commands or adb commands from recovery.
Click to expand...
Click to collapse
I tried unlocking bootloader with htcdev all thing gose OK but after restart phone is lock again I should say phone is dead and hang on HTC logo
Waiting for help .......
afghan-gsm-mastermind said:
Waiting for help .......
Click to expand...
Click to collapse
how are we suppose to help you with a locked bootloader ?
clsA said:
how are we suppose to help you with a locked bootloader ?
Click to expand...
Click to collapse
I've told him this in a previous thread. . Without an unlocked bootloader he is stuck.. He has to unlock first...
Sent from my GT-I9505 using XDA Premium 4 mobile app
s-on, No Os, unlocked, got twrp. Cant install stock RUU!!
Hi. Im a little bit confused with my HTC__016 One M7, My phone is currently S-On with no Os and no recovery image. I cant transfer a stock ruu to my phone or twrp to install. I have tried using adb and fastboot, I have cleared all caches too. If i boot into recovery and i use twrp to fix permissions it says E: Unable to mount data and cache. I have tried adb sideload aswell and it seems to work but then always fails at the certificate verification.. I assume that this is S-On's fault. How should i proceed? I dont want to hard brick my device, i still have my basebands too thank goodness..
What can I do to fix my phones file system or how can i transfer the stock RUU.. I have tried 3 diferent stock RUUs and they all fail at certificate verification. I would really appreciate the help..
Thanks A lot
AnonZA said:
Hi. Im a little bit confused with my HTC__016 One M7, My phone is currently S-On with no Os and no recovery image. I cant transfer a stock ruu to my phone or twrp to install. I have tried using adb and fastboot, I have cleared all caches too. If i boot into recovery and i use twrp to fix permissions it says E: Unable to mount data and cache. I have tried adb sideload aswell and it seems to work but then always fails at the certificate verification.. I assume that this is S-On's fault. How should i proceed? I dont want to hard brick my device, i still have my basebands too thank goodness..
What can I do to fix my phones file system or how can i transfer the stock RUU.. I have tried 3 diferent stock RUUs and they all fail at certificate verification. I would really appreciate the help..
Thanks A lot
Click to expand...
Click to collapse
Post a fastboot getvar all minus imei no and serial no. Post links to recovery's you have tried and links to RUU'S. and also commands you have tried to flash recovery and RUU's
Sent from my GT-I9505 using XDA Premium 4 mobile app
AnonZA said:
Hi. Im a little bit confused with my HTC__016 One M7, My phone is currently S-On with no Os and no recovery image. I cant transfer a stock ruu to my phone or twrp to install. I have tried using adb and fastboot, I have cleared all caches too. If i boot into recovery and i use twrp to fix permissions it says E: Unable to mount data and cache. I have tried adb sideload aswell and it seems to work but then always fails at the certificate verification.. I assume that this is S-On's fault. How should i proceed? I dont want to hard brick my device, i still have my basebands too thank goodness..
What can I do to fix my phones file system or how can i transfer the stock RUU.. I have tried 3 diferent stock RUUs and they all fail at certificate verification. I would really appreciate the help..
Thanks A lot
Click to expand...
Click to collapse
sounds like your trying to sideload a RUU.zip .. that won't work
to flash RUU.zip use
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip <<yes two times
fastboot reboot
you just need the rom.zip in the same folder as fastboot
HTC__016
bored_stupid said:
Post a fastboot getvar all minus imei no and serial no. Post links to recovery's you have tried and links to RUU'S. and also commands you have tried to flash recovery and RUU's
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__016
(bootloader) battery-status: good
(bootloader) battery-voltage: 3847mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bb768ae1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.045s
---------- Post added at 04:00 PM ---------- Previous post was at 03:55 PM ----------
clsA: I tried those command million of times. It kept coming back with "boot loader signature verification..." My phone is WIPED as you can see. So usb debugging is off presumably..
Click to expand...
Click to collapse
You have the international M7 ul so download and install this rom. Follow the guide on installing
http://www.htc1guru.com/dld/ruu_m7_...0-38r-1157-04l_release_353069_signed_2-1-exe/
Sent from my GT-I9505 using XDA Premium 4 mobile app
I Formatted partition using "How to: Fix a corrupted DATA partition on the HTC One" Then tried these commands (1) fastboot oem rebootRUU (2) fastboot flash zip rom.zip
{C:\Users\####\Desktop\Mini SDK>fastboot flash zip rom.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1239446 KB)...
OKAY [ 46.879s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 61.244s
I think my next step is a stock stock RUU right?
Thanks a lot for the help..
Wrong one Apparently..
bored_stupid said:
You have the international M7 ul so download and install this rom. Follow the guide on installing
(LINK)
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I ran with admin rights, went through all the windows till i said update.. then i get error code 155, and that error code means incorrect ROM according to the programs readme!
What other ROM should I try?
Sorry to be such a pain.. I just need to use my device again.. lol
AnonZA said:
I Formatted partition using "How to: Fix a corrupted DATA partition on the HTC One" Then tried these commands (1) fastboot oem rebootRUU (2) fastboot flash zip rom.zip
{C:\Users\####\Desktop\Mini SDK>fastboot flash zip rom.zip
target reported max download size of 1526722560 bytes
sending 'zip' (1239446 KB)...
OKAY [ 46.879s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 24 parsing android-info fail)
finished. total time: 61.244s
I think my next step is a stock stock RUU right?
Thanks a lot for the help..
Click to expand...
Click to collapse
Basically you are trying to flash a file in the bootloader that is not intended to be flashed that way. Use custom recovery or it may be an update, in that case it needs stock recovery.
Sent from my GT-I9505 using XDA Premium 4 mobile app
Hey guys, this is my first thread in XDA have quite some experience with samsung android but pretty new with HTC.
So, I dropped my HTC one day and it got stuck in a bootloop after few days. I havent change anything, stock, unrooted, never flashed any ROM into it, etc. I tried flashing RUU into it using fastboot command but it ddnt work since its still S-on.
Im working on mac as a platform and i dont think this is a major issue?
I am able to access recovery mode and fastboot mode, but wasnt able to push any file into it since debugging mode is off before the bootloop. ./adb devices command wont detect the phone. I also have HTC Sync installed on my mac but again, it wont detect the phone.
I also printed the getvar all result here:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.631.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36xxxxxxx7
(bootloader) imei: 3544xxxxxx23453
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3876mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
also attached is screenshot of bootloader mode.
please help. my phone have been like this for 2-3 weeks now
RoyalChalksHere said:
Hey guys, this is my first thread in XDA have quite some experience with samsung android but pretty new with HTC.
So, I dropped my HTC one day and it got stuck in a bootloop after few days. I havent change anything, stock, unrooted, never flashed any ROM into it, etc. I tried flashing RUU into it using fastboot command but it ddnt work since its still S-on.
Im working on mac as a platform and i dont think this is a major issue?
I am able to access recovery mode and fastboot mode, but wasnt able to push any file into it since debugging mode is off before the bootloop. ./adb devices command wont detect the phone. I also have HTC Sync installed on my mac but again, it wont detect the phone.
I also printed the getvar all result here:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.631.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT36xxxxxxx7
(bootloader) imei: 3544xxxxxx23453
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3876mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e47fb74b
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
also attached is screenshot of bootloader mode.
please help. my phone have been like this for 2-3 weeks now
Click to expand...
Click to collapse
First of all is there any warranty left on the device. If there is it would be a good idea to take advantage of that before tampering with it. Especially as this happened after you dropped the phone. So there's a good chance it's a hardware problem.
I assume you've tried to factory reset from stock recovery?
If there's no warranty your best option is to unlock the bootloader. This will allow you to flash a Custom recovery. Then you can push a Rom to the phone, as adb will work in a custom recovery weather debugging is enabled or not.
I recommend TWRP 2.6.3.3 recovery it's not the latest twrp but is the most stable.
Danny201281 said:
First of all is there any warranty left on the device. If there is it would be a good idea to take advantage of that before tampering with it. Especially as this happened after you dropped the phone. So there's a good chance it's a hardware problem.
I assume you've tried to factory reset from stock recovery?
If there's no warranty your best option is to unlock the bootloader. This will allow you to flash a Custom recovery. Then you can push a Rom to the phone, as adb will work in a custom recovery weather debugging is enabled or not.
I recommend TWRP 2.6.3.3 recovery it's not the latest twrp but is the most stable.
Click to expand...
Click to collapse
yes ive tried factory reset too. I bought it in september 2013 from someone else and i think i lost the receipt, so i dont think I can take advantage of the warrant. i will keep looking though. is there any good link to unlock the bootloader?
RoyalChalksHere said:
yes ive tried factory reset too. I bought it in september 2013 from someone else and i think i lost the receipt, so i dont think I can take advantage of the warrant. i will keep looking though. is there any good link to unlock the bootloader?
Click to expand...
Click to collapse
www.htcdev.com to unlock the bootloader. You'll need to register an account. Then go to the Unlock my Bootloader section. Follow the instructions to get the Unlock code
I tried resetting rooted device... it rebooted in trwp... so i wiped it from there
when i reboot it doesn't move from the htc logo screen
when i try to power off, the soft keys blink and thats it.. nothing more.. i don't know what else to
@CallMe_Y_C said:
I tried resetting rooted device... it rebooted in trwp... so i wiped it from there
when i reboot it doesn't move from the htc logo screen
when i try to power off, the soft keys blink and thats it.. nothing more.. i don't know what else to
Click to expand...
Click to collapse
When you say you wiped it in twrp, did you Factory Reset or did you Format Data?
If you used Format Data then you wiped your entire device including the installed Rom. You should be able to force the device to power of by holding the power button for 60secs.
Then power on while holding volume down to get to the bootloader. Then you can boot to recovery and push a Rom with adb. :good:
awesome, thanks @Danny201281 i got TWRP to work on my HTC one. now on to custom rom. Which one is the best for HTC One? Any suggestion anyone? =)
RoyalChalksHere said:
awesome, thanks @Danny201281 i got TWRP to work on my HTC one. now on to custom rom. Which one is the best for HTC One? Any suggestion anyone? =)
Click to expand...
Click to collapse
Hehe I will always recommend Android Revolution HD because it's my favorite
But honestly is depends what you want from a Rom. ARHD is close to stock. It's very stable with no real bugs. It also has xposed support so you can make your own modifications. For me this gives a more personal experience.
MaximusHD is also a very popular close to stock Rom.
Or then you have the likes of Viper Rom or insertcoin which are more heavily modified.
But either way you look at it ARHD is a good place to start. It should be flashed with TWRP 2.6.3.3 TO avoid problems installing as most newer versions of TWRP don't seem to agree with the Aroma installer the Rom is packaged with :good:
Danny201281 said:
Hehe I will always recommend Android Revolution HD because it's my favorite
But honestly is depends what you want from a Rom. ARHD is close to stock. It's very stable with no real bugs. It also has xposed support so you can make your own modifications. For me this gives a more personal experience.
MaximusHD is also a very popular close to stock Rom.
Or then you have the likes of Viper Rom or insertcoin which are more heavily modified.
But either way you look at it ARHD is a good place to start. It should be flashed with TWRP 2.6.3.3 TO avoid problems installing as most newer versions of TWRP don't seem to agree with the Aroma installer the Rom is packaged with :good:
Click to expand...
Click to collapse
hey. ok so i downloaded AICP and installed them through TWRP and everything works fine. BUT, when i got to my homepage and use the phone for a couple of minutes, it restarted on its own. Any idea on why this is happening?
RoyalChalksHere said:
hey. ok so i downloaded AICP and installed them through TWRP and everything works fine. BUT, when i got to my homepage and use the phone for a couple of minutes, it restarted on its own. Any idea on why this is happening?
Click to expand...
Click to collapse
Go to Setting>About>Phone Identity
Is your IMEI displayed properly there?
Also check Setting>About>Software Information>More
Is your Baseband displayed correctly here?
Danny201281 said:
Go to Setting>About>Phone Identity
Is your IMEI displayed properly there?
Also check Setting>About>Software Information>More
Is your Baseband displayed correctly here?
Click to expand...
Click to collapse
oh they are both unknown. what should I do?
RoyalChalksHere said:
oh they are both unknown. what should I do?
Click to expand...
Click to collapse
9 times out of 10 this is a Hardware problem. You can try and flash a Firmware package and after that the only thing left Is to s-off and try an ruu. But if firmware doesn't fix it an ruu probably won't either.
As the phone had been dropped there's a high chance it's a hardware problem.
But I'll see if I can find a firmware package you can try. It's worth a go before writing it off.
Danny201281 said:
9 times out of 10 this is a Hardware problem. You can try and flash a Firmware package and after that the only thing left Is to s-off and try an ruu. But if firmware doesn't fix it an ruu probably won't either.
As the phone had been dropped there's a high chance it's a hardware problem.
But I'll see if I can find a firmware package you can try. It's worth a go before writing it off.
Click to expand...
Click to collapse
oh. so i guess warranty is the only way to go. or new phone. =( i even lost pictures from internal storage.
I couldn't find a firmware package but I did find this OTA. It contains the firmware we need. Download it and open the zip on your pc. Extract the firmware.zip and put the firmware.zip in your fastboot folder.
http://www.htc1guru.com/dld/ota_m7_...-19-631-9_release_372926h4tumwerl14wrs0u-zip/
Reboot the phone to the bootloader and Connect fastbootusb. Now open your Fastboot command line and type
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Code:
fastboot oem rebootRUU
< --- case sensitive. ---^^^
The phone will reboot to a black screen with a Silver HTC LOGO. This is RUU mode. Now we're going to flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash will be short. It's just a preupdate preparing the hboot for the new firmware. So we need to do the same command again.
Code:
fastboot flash zip firmware.zip
The second flash will take a little longer and this time it will flash the full firmware. The progress bar on the phone screen will not reach 100% this is normal as long as the command window has completed its output the flash is done.
Code:
fastboot reboot-bootloader
Now you will need to unlock the bootloader again with your Unlock_code.bin
Flash TWRP and Flash your Rom again before the phone will boot. Then reboot the phone. :fingers-crossed:
If that doesn't do it Warranty is a possibility but you will need s-off to remove the signs the phone was tampered with.
---------- Post added at 10:01 AM ---------- Previous post was at 09:59 AM ----------
Yeah unfortunately Unlocking the Bootloader Wipes the device.
Danny201281 said:
I couldn't find a firmware package but I did find this OTA. It contains the firmware we need. Download it and open the zip on your pc. Extract the firmware.zip and put the firmware.zip in your fastboot folder.
http://www.htc1guru.com/dld/ota_m7_...-19-631-9_release_372926h4tumwerl14wrs0u-zip/
Reboot the phone to the bootloader and Connect fastbootusb. Now open your Fastboot command line and type
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Code:
fastboot oem rebootRUU
< --- case sensitive. ---^^^
The phone will reboot to a black screen with a Silver HTC LOGO. This is RUU mode. Now we're going to flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash will be short. It's just a preupdate preparing the hboot for the new firmware. So we need to do the same command again.
Code:
fastboot flash zip firmware.zip
The second flash will take a little longer and this time it will flash the full firmware. The progress bar on the phone screen will not reach 100% this is normal as long as the command window has completed its output the flash is done.
Code:
fastboot reboot-bootloader
Now you will need to unlock the bootloader again with your Unlock_code.bin
Flash TWRP and Flash your Rom again before the phone will boot. Then reboot the phone. :fingers-crossed:
If that doesn't do it Warranty is a possibility but you will need s-off to remove the signs the phone was tampered with.
---------- Post added at 10:01 AM ---------- Previous post was at 09:59 AM ----------
Yeah unfortunately Unlocking the Bootloader Wipes the device.
Click to expand...
Click to collapse
so, it failed and shows this:
Mustafas-MacBook-Airlatform-tools mustafafarhanarifin$ ./fastboot flash zip OTA_M7_UL_K44_SENSE60_MR_Rogers_WWE_5.11.631.8_R-4.19.631.9_release_372926h4tumwerl14wrs0u.zip
target reported max download size of 1514139648 bytes
sending 'zip' (720552 KB)...
OKAY [ 28.648s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 111.120s
RoyalChalksHere said:
so, it failed and shows this:
Mustafas-MacBook-Airlatform-tools mustafafarhanarifin$ ./fastboot flash zip OTA_M7_UL_K44_SENSE60_MR_Rogers_WWE_5.11.631.8_R-4.19.631.9_release_372926h4tumwerl14wrs0u.zip
target reported max download size of 1514139648 bytes
sending 'zip' (720552 KB)...
OKAY [ 28.648s]
writing 'zip'...
(bootloader) signature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 111.120s
Click to expand...
Click to collapse
You flashed the wrong zip. The firmware zip is inside the OTA
Open the OTA_M7_UL_K44_SENSE60_MR_Rogers_WWE_5.11.631.8_R-4.19.631.9_release_372926h4tumwerl14wrs0u.zip On your pc inside it is a firmware.zip extract the firmware.zip and flash it with the previous procedure
Danny201281 said:
I couldn't find a firmware package but I did find this OTA. It contains the firmware we need. Download it and open the zip on your pc. Extract the firmware.zip and put the firmware.zip in your fastboot folder.
http://www.htc1guru.com/dld/ota_m7_...-19-631-9_release_372926h4tumwerl14wrs0u-zip/
Reboot the phone to the bootloader and Connect fastbootusb. Now open your Fastboot command line and type
Code:
fastboot erase cache
fastboot oem lock
fastboot reboot-bootloader
Code:
fastboot oem rebootRUU
< --- case sensitive. ---^^^
The phone will reboot to a black screen with a Silver HTC LOGO. This is RUU mode. Now we're going to flash the firmware.
Code:
fastboot flash zip firmware.zip
The first flash will be short. It's just a preupdate preparing the hboot for the new firmware. So we need to do the same command again.
Code:
fastboot flash zip firmware.zip
The second flash will take a little longer and this time it will flash the full firmware. The progress bar on the phone screen will not reach 100% this is normal as long as the command window has completed its output the flash is done.
Code:
fastboot reboot-bootloader
Now you will need to unlock the bootloader again with your Unlock_code.bin
Flash TWRP and Flash your Rom again before the phone will boot. Then reboot the phone. :fingers-crossed:
If that doesn't do it Warranty is a possibility but you will need s-off to remove the signs the phone was tampered with.
---------- Post added at 10:01 AM ---------- Previous post was at 09:59 AM ----------
Yeah unfortunately Unlocking the Bootloader Wipes the device.
Click to expand...
Click to collapse
Danny201281 said:
You flashed the wrong zip. The firmware zip is inside the OTA
Open the OTA_M7_UL_K44_SENSE60_MR_Rogers_WWE_5.11.631.8_R-4.19.631.9_release_372926h4tumwerl14wrs0u.zip On your pc inside it is a firmware.zip extract the firmware.zip and flash it with the previous procedure
Click to expand...
Click to collapse
youre amazing man. looks fine so far. baseband and IMEI is registered. im currently on android lollipop, and couldnt find any suitable gapps file. do you happen to know?
ok, so I shut down the phone to get back into fastboot mode with the button combo, but now it is not even turning on. black screen, not even charging. wtf.
Danny201281 said:
When you say you wiped it in twrp, did you Factory Reset or did you Format Data?
If you used Format Data then you wiped your entire device including the installed Rom. You should be able to force the device to power of by holding the power button for 60secs.
Then power on while holding volume down to get to the bootloader. Then you can boot to recovery and push a Rom with adb. :good:
Click to expand...
Click to collapse
i think i did both
i will try that after i get some charge on it
battery died last night
---------- Post added at 12:49 PM ---------- Previous post was at 12:23 PM ----------
@CallMe_Y_C said:
i think i did both
i will try that after i get some charge on it
battery died last night
Click to expand...
Click to collapse
can i get a suggested rom or supm to follow?
steps
thanks
RoyalChalksHere said:
youre amazing man. looks fine so far. baseband and IMEI is registered. im currently on android lollipop, and couldnt find any suitable gapps file. do you happen to know?
Click to expand...
Click to collapse
RoyalChalksHere said:
ok, so I shut down the phone to get back into fastboot mode with the button combo, but now it is not even turning on. black screen, not even charging. wtf.
Click to expand...
Click to collapse
Sorry man I had to get some sleep, So it was looking good for while then
What happened exactly? You flashed the firmware and Rom and all was ok. Then you just power off to go to bootloader and it never came back on? Did you flash anything in between that or that was it? You say you had a lollipop Rom can you provide a link to it please?
Is the device detected when you connect it to your pc? Does it show on device manager, maybe as Unknown device or QHSUSB_DLOAD?
---------- Post added at 04:09 PM ---------- Previous post was at 03:59 PM ----------
@CallMe_Y_C said:
i think i did both
i will try that after i get some charge on it
battery died last night
---------- Post added at 12:49 PM ---------- Previous post was at 12:23 PM ----------
can i get a suggested rom or supm to follow?
steps
thanks
Click to expand...
Click to collapse
I'd be happy to make a suggestion but can you post your getvar all? Not all roms are compatible with all devices.
It's kind of important to know what I'm recommending a Rom for
Hy guys, my htc one m7 is bricked (hard) no boot,no recovery... i want that my htc return stock for solve the problem but the problem is that i can't find the right RUU for my terminal. My CID is H3G__402. How can resolve this serious problem ?
Thank for eventually answer.
This is status of the terminal
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(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: H3G__402
(bootloader) battery-status: good
(bootloader) battery-voltage: 3963mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae8bbb39
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.043s
HELP MEE PLEASEE
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck
R_a_z_v_a_n said:
Sir,
Please wait until mods will move this thread to the device specific forum for more relevant answers.
Stand by
Good luck
Click to expand...
Click to collapse
hope to solve the problem :crying:
Giuliusss said:
hope to solve the problem :crying:
Click to expand...
Click to collapse
its not hard bricked if you can get into the bootloader, its still fixable, what do you mean no recovery, what happens when you select recovery ?
the only way to get rid of the security warning that you have is to get s-off and to get s-off on your current HBOOT, you need a working rom and will have to pay $25
Seanie280672 said:
its not hard bricked if you can get into the bootloader, its still fixable, what do you mean no recovery, what happens when you select recovery ?
the only way to get rid of the security warning that you have is to get s-off and to get s-off on your current HBOOT, you need a working rom and will have to pay $25
Click to expand...
Click to collapse
I can get into recovery but if reset the system with a factory reset the terminal crashes on a htc quietly brillant, i can't install a new rom because this is an error in a flash a new rom (REMOTE NOT ALLOWED)
C:\Users\Frisone\Desktop\jkj>fastboot flash zip Super_Su.zip
sending 'zip' (1756 KB)...
OKAY [ 0.364s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 0.386s
C:\Users\Frisone\Desktop\jkj>fastboot flash zip rom1.zip
sending 'zip' (203246 KB)...
OKAY [ 10.527s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 10.558s
So, this is the situation in a recovery
View attachment 3142171
View attachment 3142172
View attachment 3142173
View attachment 3142174
apparently there isn't firmware
Giuliusss said:
I can get into recovery but if reset the system with a factory reset the terminal crashes on a htc quietly brillant, i can't install a new rom because this is an error in a flash a new rom (REMOTE NOT ALLOWED)
C:\Users\Frisone\Desktop\jkj>fastboot flash zip Super_Su.zip
sending 'zip' (1756 KB)...
OKAY [ 0.364s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 0.386s
C:\Users\Frisone\Desktop\jkj>fastboot flash zip rom1.zip
sending 'zip' (203246 KB)...
OKAY [ 10.527s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 10.558s
So, this is the situation in a recovery
View attachment 3142171
View attachment 3142172
View attachment 3142173
View attachment 3142174
apparently there isn't firmware
Click to expand...
Click to collapse
OS and version main missing is normal for having a custom recovery installed, nothing to worry about.
remote not allowed is because your flashing those zip files the wrong way, they need to be flashed from recovery you cant flash them from fastboot like that.
flash TWRP recovery 2.6.3.3 from here: http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.6.3.3-m7.img
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
Next download this sense based rom: https://www.androidfilehost.com/?w=files&flid=22071 once downloaded just rename it to rom.zip
Next, enter recovery, at this point I would suggest to do a full wipe then reboot back into recovery for the changes to take full effect, it will say you have no OS installed, just ignore it, it will also ask if you want to install SuperSU, select do not install, the rom you install will most likely already be rooted, then when recovery starts back up, with recovery main screen only showing, put the rom.zip file that you want to flash in the same folder as fastboot and adb on your computer, open a CMD window and then type the below command, make sure your phone plugged into the computer at the same time:
adb push rom.zip /sdcard/
and wait, takes about 5 to 10 mins to push depending on the file size, it will let you know when its done, when it is done, unplug your phone and install the rom, during the install it will ask you if you want to full wipe at the beginning of the aroma installer, select yes to wipe, DO NOT WIPE ANYTHING ONCE THE ROM IS INSTALLED, a flresh clean rom install on a fresh clean slate does not require anything wiping, just restart and let it boot, again it can take 15 to 20mins to boot the first time.
follow these instructions properly, do not skip any steps and you'll be back up and running in 30 mins tops.
Seanie280672 said:
OS and version main missing is normal for having a custom recovery installed, nothing to worry about.
remote not allowed is because your flashing those zip files the wrong way, they need to be flashed from recovery you cant flash them from fastboot like that.
flash TWRP recovery 2.6.3.3 from here:
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
Next download this sense based rom: once downloaded just rename it to rom.zip
Next, enter recovery, at this point I would suggest to do a full wipe then reboot back into recovery for the changes to take full effect, it will say you have no OS installed, just ignore it, it will also ask if you want to install SuperSU, select do not install, the rom you install will most likely already be rooted, then when recovery starts back up, with recovery main screen only showing, put the rom.zip file that you want to flash in the same folder as fastboot and adb on your computer, open a CMD window and then type the below command, make sure your phone plugged into the computer at the same time:
adb push rom.zip /sdcard/
and wait, takes about 5 to 10 mins to push depending on the file size, it will let you know when its done, when it is done, unplug your phone and install the rom, during the install it will ask you if you want to full wipe at the beginning of the aroma installer, select yes to wipe, DO NOT WIPE ANYTHING ONCE THE ROM IS INSTALLED, a flresh clean rom install on a fresh clean slate does not require anything wiping, just restart and let it boot, again it can take 15 to 20mins to boot the first time.
follow these instructions properly, do not skip any steps and you'll be back up and running in 30 mins tops.
Click to expand...
Click to collapse
it work !! thank you for all...only two question: but in the future can i flash another different rom ? can i proceed to s-off with firewater with this rom or need a cyanogen mod for firewater ? :angel::angel::laugh:
Giuliusss said:
it work !! thank you for all...only two question: but in the future can i flash another different rom ? can i proceed to s-off with firewater with this rom or need a cyanogen mod for firewater ? :angel::angel::laugh:
Click to expand...
Click to collapse
Yes you need to use that rom to get s-off, CM wont work, Firewater is discontinued, sunshine is the only way to s-off your HBOOT now and that will cost you $25. http://theroot.ninja/
Yes you can change roms at anytime, just follow these instructions again, just using a different rom and also make sure you read the op for the rom incase it requires a different recovery, not all roms will install or boot on TWRP 2.6.3.3 so make sure you read the OP.
htc m7 pn07110 bricked
htc m7 pn07110 bricked
hi i have a problem when usin my phone it suddenly freezers and was not able to get acces to anything (Was rooted/Bootloader Unlocked/having Custom Rom/TRWP/S-ON).. tried to restore my rom by usin twrp 2.8. but there was no file and it cannot mount my storage...
Then, found on a thread to restore stock ROM via RUU, so i relocked my bootloader and then find myself stuck at everything
When I plug in AC adapter for charging, phone load in bootloader, and whenever i press "Fastboot/Factory Reset" my phone freezes
Even fastboot and ADB command freezes my phone,
I need help please.
Code:
*** TAMPERED ***
*** RELOCKED ***
*** SECURITY WARNING ***
M7_U PVT SHIP S-ON RH
HBOOT-1.57.0000
RADIO-4T.28.3218.04
OpenDSP-v32.120.274.0909
OS-6.09.401.111
eMMC-boot 2048MB
Nov 12 2014,21:44:28.0
Hello,
My HTC one got stuck in boot loop after i tried to update to Lollipop OTA. (the phone is official, never modified it). Red exclamation with error : Can not mount sd card...
The only solution that worked for me is :
- unlock bootloader (htcdev.com)
- installed TWRP (with WinDroid_Universal_Android_Toolkit)
- installed MIUI rom
The phone is working fine, but i want to turn back to official Rom and update to lollipop. What i have to do ?
imothep00 said:
Hello,
My HTC one got stuck in boot loop after i tried to update to Lollipop OTA. (the phone is official, never modified it). Red exclamation with error : Can not mount sd card...
The only solution that worked for me is :
- unlock bootloader (htcdev.com)
- installed TWRP (with WinDroid_Universal_Android_Toolkit)
- installed MIUI rom
The phone is working fine, but i want to turn back to official Rom and update to lollipop. What i have to do ?
Click to expand...
Click to collapse
"can not mount sd card" error is normal, its always displayed when entering the stock recovery.
post the output of "fastboot getvar all" (remove imei and serialno before posting)
(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.09.401.111
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_u
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0711000
(bootloader) cidnum: HTC__J15
(bootloader) battery-status: good
(bootloader) battery-voltage: 3848mV
(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.060s
I have no idea what i am doing, but i will try to flash "Guru Reset M7 2.24.401.8" with TWRP.
Hope it will work
imothep00 said:
I have no idea what i am doing, but i will try to flash "Guru Reset M7 2.24.401.8" with TWRP.
Hope it will work
Click to expand...
Click to collapse
no it wont work, that guru reset is too old and will boot loop on your hboot when you try to update, follow these instructions, exactly the same for your phone:
http://forum.xda-developers.com/showpost.php?p=59273464&postcount=4
no it wont work, that guru reset is too old and will boot loop on your hboot when you try to update, follow these instructions, exactly the same for your phone:
http://forum.xda-developers.com/show...64&postcount=4
Click to expand...
Click to collapse
It works. Thank you.
In fact, it works but only the first part.
Now, Stock 4.4 booted et works fine.
but i the recovery, no
Code:
sending 'recovery' (12570 KB)...
OKAY [ 1.619s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.718s
imothep00 said:
In fact, it works but only the first part.
Now, Stock 4.4 booted et works fine.
but i the recovery, no
Code:
sending 'recovery' (12570 KB)...
OKAY [ 1.619s]
writing 'recovery'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 2.718s
Click to expand...
Click to collapse
sorry, you need the M7_U recovery file not the UL, 1 sec.
in fact, easier way, do this instead:
download the OTA, select install later, plug your phone into the computer and pull the OTA off the phone to your computer desktop, its in the downloads folder on your internal storage.
open the OTA, its just a zip file, inside is another zip called firmware.zip, open that zip and take out the recovery.img, flash that one, thats your stock recovery.
Seanie280672 said:
sorry, you need the M7_U recovery file not the UL, 1 sec.
in fact, easier way, do this instead:
download the OTA, select install later, plug your phone into the computer and pull the OTA off the phone to your computer desktop, its in the downloads folder on your internal storage.
open the OTA, its just a zip file, inside is another zip called firmware.zip, open that zip and take out the recovery.img, flash that one, thats your stock recovery.
Click to expand...
Click to collapse
I've done this, recovery flash gone successful. But again, when i try to update OTA, i get this : check attachment
Can someone help me please
Please, don't let me down...
imothep00 said:
Please, don't let me down...
Click to expand...
Click to collapse
go is settings --> about --> software info.
can you take a screenshot of your software version and post it please.
Looks like you have not flashed the right rom. Im pretty sure it will say 6.09.401.11 but it should be 6.09.401.111 hence the "variant version" error.
alray said:
go is settings --> about --> software info.
can you take a screenshot of your software version and post it please.
Looks like you have not flashed the right rom. Im pretty sure it will say 6.09.401.11 but it should be 6.09.401.111 hence the "variant version" error.
Click to expand...
Click to collapse
You're right. It's 6.09.401.11
What should i do now ? reflash a new backup with TWRP ? Which one ? I'm sick and lost with all theses files/versions.
Thank you in advance.
imothep00 said:
You're right. It's 6.09.401.11
What should i do now ? reflash a new backup with TWRP ? Which one ? I'm sick and lost with all theses files/versions.
Thank you in advance.
Click to expand...
Click to collapse
firmware and software version must match so you must flash the 6.09.401.111 rom not the 6.09.401.11. There is nandroid backup here: http://forum.xda-developers.com/htc-one/development/backup-100-stock-6-09-401-111-twrp-t2992871
so reflash twrp
restore the nandroid backup of 6.09.401.111
then flash the 6.09.401.111 stock recovery (available at the same link)
and then take the ota update from 6.09.401.111 to 7.19.401.102
@alray
Ok, my phone is now 6.09.401.111
OTA update launch installation et get this :
imothep00 said:
@alray
Ok, my phone is now 6.09.401.111
OTA update launch installation et get this :
Click to expand...
Click to collapse
looks like you have flashed the 7.19.401.2 stock recovery instead of the 6.09.401.111 stock recovery....
---------- Post added at 09:19 AM ---------- Previous post was at 09:15 AM ----------
btw you can use the recovery packed in the ota update.
download the ota update, select install later.
when download is complete plug your phone to your computer, copy the ota zip file from the download folder to your computer. Open the ota.zip (best achieved with 7zip) you'll find another zip file inside called "firmware.zip". Extract this file from the ota.zip to your desktop. Then open the firmware.zip file with 7zip, extract the "recovery.img" file and flash it to your device. Reboot and try to install the ota again.
alray said:
go is settings --> about --> software info.
can you take a screenshot of your software version and post it please.
Looks like you have not flashed the right rom. Im pretty sure it will say 6.09.401.11 but it should be 6.09.401.111 hence the "variant version" error.
Click to expand...
Click to collapse
alray said:
looks like you have flashed the 7.19.401.2 stock recovery instead of the 6.09.401.111 stock recovery....
---------- Post added at 09:19 AM ---------- Previous post was at 09:15 AM ----------
btw you can use the recovery packed in the ota update.
download the ota update, select install later.
when download is complete plug your phone to your computer, copy the ota zip file from the download folder to your computer. Open the ota.zip (best achieved with 7zip) you'll find another zip file inside called "firmware.zip". Extract this file from the ota.zip to your desktop. Then open the firmware.zip file with 7zip, extract the "recovery.img" file and flash it to your device. Reboot and try to install the ota again.
Click to expand...
Click to collapse
All good now. problem solved. Thank you very much