So I just upgraded to a new phone and wanted to play around with custom roms on my old m7 for funsies. I haven't done this in several years so I made a huge mistake... I forgot to make a recovery image. Oops...
What happened:
I followed this guide: http://forum.xda-developers.com/showthread.php?t=2268963
I unlocked the bootloader just fine, for recovery I went with CWM since that's what I had used in the past. I downloaded a rom from the above tutorial (Bulletproof) and installed it via CWM with no errors... But I forgot to make a recovery.
Now:
My phone gets stuck in a boot loop if I try to boot normally. I have no problem booting into the bootloader. From there I can select fastboot/recovery. If I select either while my phone is connected to my PC my PC makes the "new connection" sound and "fastboot devices" lists the phone. I cannot see my phone via windows explorer and thus can't add a new rom to flash on to my phone. I have tried going in to recovery and selecting to install a zip via sideloading and when I try to push or sideload a file I get "device not found." I am still able to install the rom I have on the sd card... But I still get stuck in a boot loop afterwards.
ex: http://puu.sh/iIY6r/5e0d57e57f.png
Am I hard bricked?
Sorry if I'm lacking any relevant info and thanks for any insight.
-CleanUp
CleanUpOnAisle13 said:
So I just upgraded to a new phone and wanted to play around with custom roms on my old m7 for funsies. I haven't done this in several years so I made a huge mistake... I forgot to make a recovery image. Oops...
What happened:
I followed this guide: http://forum.xda-developers.com/showthread.php?t=2268963
I unlocked the bootloader just fine, for recovery I went with CWM since that's what I had used in the past. I downloaded a rom from the above tutorial (Bulletproof) and installed it via CWM with no errors... But I forgot to make a recovery.
Now:
My phone gets stuck in a boot loop if I try to boot normally. I have no problem booting into the bootloader. From there I can select fastboot/recovery. If I select either while my phone is connected to my PC my PC makes the "new connection" sound and "fastboot devices" lists the phone. I cannot see my phone via windows explorer and thus can't add a new rom to flash on to my phone. I have tried going in to recovery and selecting to install a zip via sideloading and when I try to push or sideload a file I get "device not found." I am still able to install the rom I have on the sd card... But I still get stuck in a boot loop afterwards.
ex: http://puu.sh/iIY6r/5e0d57e57f.png
Am I hard bricked?
Sorry if I'm lacking any relevant info and thanks for any insight.
-CleanUp
Click to expand...
Click to collapse
Bulletproof isn't a rom, its a kernel. The right version of bulletproof must be used depending on your rom version.
post the output of "fastboot getvar all" (remove imei and sn)
post the output of "adb version"
What is your windows version?
What rom do you want to flash?
alray said:
Bulletproof isn't a rom, its a kernel. The right version of bulletproof must be used depending on your rom version.
post the output of "fastboot getvar all" (remove imei and sn)
post the output of "adb version"
What is your windows version?
What rom do you want to flash?
Click to expand...
Click to collapse
Oh I see. Forgive me but what's the difference between a rom and a kernal? And does installing a kernal via CWM remove or mess with the stock rom?
C:\Users\Wyatt\Desktop\Fastboot\adb_fastboot_drivers>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.24.531.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: REDACTED
(bootloader) imei: REDACTED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4193mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-412e361e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
C:\Users\Wyatt\Desktop\Fastboot\adb_fastboot_drivers>adb version
Android Debug Bridge version 1.0.29
Windows 8.1
I prefer MIUI
Thanks!
CleanUpOnAisle13 said:
Oh I see. Forgive me but what's the difference between a rom and a kernal?
Click to expand...
Click to collapse
http://forum.xda-developers.com/wiki/index.php?title=ROM-VS-Kernel
And does installing a kernal via CWM remove or mess with the stock rom?
Click to expand...
Click to collapse
Flashing a custom kernel doesn't remove the stock rom because a kernel isn't a rom, it remove the stock kernel. Does it mess with the rom? Not really but if the kernel installed isn't compatible with your rom then it won't boot or at best it will be unstable.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.03
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.24.531.3
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: remove!
(bootloader) imei: remove!
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0713000
(bootloader) cidnum: T-MOB010
(bootloader) battery-status: good
(bootloader) battery-voltage: 4193mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-412e361e
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
Don't post your IMEI and SN (like I told you above) remove these numbers. Your firmware is really old (3.24.531.3) but that should be fine for MIUI, however you should update it for better performance and stability.
C:\Users\Wyatt\Desktop\Fastboot\adb_fastboot_drivers>adb version
Android Debug Bridge version 1.0.29
Click to expand...
Click to collapse
Outdated, latest version is 1.0.32. Update your android sdk to fix your adb issues.
I prefer MIUI
Click to expand...
Click to collapse
Would recommend that you flash latest TWRP for M7 instead of CWM. With twrp, you'll be able to see your phone storage from your computer when booted in twrp main menu so you'll only have to drag and drop your rom from your computer to your phone storage (my computer --> Htc one --> internal storage --> drag and drop your rom here) without using adb push or sideload. Btw, if you still prefer to use adb sideload, you'll need adb 1.0.32 anyway if using latest twrp.
---------- Post added at 12:35 AM ---------- Previous post was at 12:25 AM ----------
btw if you want to update your firmware, the simplest method would be to relock your boorloader, flash the 3.24.531.3 RUU, update your phone from ota updates to latest version 7.xx.531.xx. Then you can unlock the bootloader again, flash twrp recovery and flash your custom rom.
alray said:
http://forum.xda-developers.com/wiki/index.php?title=ROM-VS-Kernel
Flashing a custom kernel doesn't remove the stock rom because a kernel isn't a rom, it remove the stock kernel. Does it mess with the rom? Not really but if the kernel installed isn't compatible with your rom then it won't boot or at best it will be unstable.
Don't post your IMEI and SN (like I told you above) remove these numbers. Your firmware is really old (3.24.531.3) but that should be fine for MIUI, however you should update it for better performance and stability.
Outdated, latest version is 1.0.32. Update your android sdk to fix your adb issues.
Would recommend that you flash latest TWRP for M7 instead of CWM. With twrp, you'll be able to see your phone storage from your computer when booted in twrp main menu so you'll only have to drag and drop your rom from your computer to your phone storage (my computer --> Htc one --> internal storage --> drag and drop your rom here) without using adb push or sideload. Btw, if you still prefer to use adb sideload, you'll need adb 1.0.32 anyway if using latest twrp.
---------- Post added at 12:35 AM ---------- Previous post was at 12:25 AM ----------
btw if you want to update your firmware, the simplest method would be to relock your boorloader, flash the 3.24.531.3 RUU, update your phone from ota updates to latest version 7.xx.531.xx. Then you can unlock the bootloader again, flash twrp recovery and flash your custom rom.
Click to expand...
Click to collapse
Excellent! I'm up and running again. Thanks for all the help, I really appreciate it.
Related
Hello, I have an HTC One M7 and I'm trying to install the custom ROM Hd revolution. To do this I follow this guide : http://forum.xda-developers.com/showthread.php?t=2265618 . I've already unlock the bootloader and now I'm trying to "Flashing custom recovery" everything is ok till the stage 8, on my terminal they write the good message "OKAY" however my phone is block the white screen with fastboot and I don't have access to do a nandroid backup. Do you have an idea why? thank you very much
ti_coco said:
Hello, I have an HTC One M7 and I'm trying to install the custom ROM Hd revolution. To do this I follow this guide : http://forum.xda-developers.com/showthread.php?t=2265618 . I've already unlock the bootloader and now I'm trying to "Flashing custom recovery" everything is ok till the stage 8, on my terminal they write the good message "OKAY" however my phone is block the white screen with fastboot and I don't have access to do a nandroid backup. Do you have an idea why? thank you very much
Click to expand...
Click to collapse
Can you post a fastboot getvar all, removing the serial number and imei please?
Also, are you trying to run the command "fastboot boot recovery recovery.img"?
What version of recovery are you using?
stovie_steve said:
Can you post a fastboot getvar all, removing the serial number and imei please?
Also, are you trying to run the command "fastboot boot recovery recovery.img"?
What version of recovery are you using?
Click to expand...
Click to collapse
"(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.10.1020.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__247
(bootloader) battery-status: good
(bootloader) battery-voltage: 3920mV
(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!"
No I try to do "fastboot boot recovery.img" as explained in the guide in order to do a nandroid back after. I use TWRP recovery. Thanks for your help
ti_coco said:
"(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.10.1020.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__247
(bootloader) battery-status: good
(bootloader) battery-voltage: 3920mV
(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!"
No I try to do "fastboot boot recovery.img" as explained in the guide in order to do a nandroid back after. I use TWRP recovery. Thanks for your help
Click to expand...
Click to collapse
You can't use fastboot boot recovery with that version of hboot. Only works for hboot 1.44 it mentions in the guide it only works in earlier versions
You have to flash the recovery using the command fastboot flash recovery recovery.img
After that you can make a nandroid backup, but it won't contain stock recovery
stovie_steve said:
You can't use fastboot boot recovery with that version of hboot. Only works for hboot 1.44 it mentions in the guide it only works in earlier versions
You have to flash the recovery using the command fastboot flash recovery recovery.img
After that you can make a nandroid backup, but it won't contain stock recovery
Click to expand...
Click to collapse
Ok, thank you but how can I do a stock recovery then ?
ti_coco said:
Ok, thank you but how can I do a stock recovery then ?
Click to expand...
Click to collapse
I checked and couldn't find one for you. Here are other stock recoveries but none for your version
Are you planning on getting s off after you install your custom ROM? Means you can run an earlier RUU for your CID which will put you completely stock again if you need to return your phone for warranty purposes etc
stovie_steve said:
I checked and couldn't find one for you. Here are other stock recoveries but none for your version
Are you planning on getting s off after you install your custom ROM? Means you can run an earlier RUU for your CID which will put you completely stock again if you need to return your phone for warranty purposes etc
Click to expand...
Click to collapse
Sorry I don't know very well, so I don't understand what you are saying How do I become s-off after my ROM ?And what does it change?
ti_coco said:
Sorry I don't know very well, so I don't understand what you are saying How do I become s-off after my ROM ?And what does it change?
Click to expand...
Click to collapse
If you do not understand what s off is or what it means for your phone, then don't worry. It's not for you
To install the custom ROM, you need to flash the recovery rather than boot recovery as suggested by the guide. If you have any problems installing the ROM I'd be happy to help you along. But continue with the guide in the meantime
stovie_steve said:
If you do not understand what s off is or what it means for your phone, then don't worry. It's not for you
To install the custom ROM, you need to flash the recovery rather than boot recovery as suggested by the guide. If you have any problems installing the ROM I'd be happy to help you along. But continue with the guide in the meantime
Click to expand...
Click to collapse
Ok, just do I need to root my phone to install this ROM ?
ti_coco said:
Ok, just do I need to root my phone to install this ROM ?
Click to expand...
Click to collapse
To install the ROM:
1. Unlock your bootloader
2. Flash TWRP, preferably version 2.6.3.3 and download ROM to your phone
3. Make a nandroid backup in recovery
4. install ROM and follow instructions
stovie_steve said:
To install the ROM:
1. Unlock your bootloader
2. Flash TWRP, preferably version 2.6.3.3 and download ROM to your phone
3. Make a nandroid backup in recovery
4. install ROM and follow instructions
Click to expand...
Click to collapse
I did what you say but now my HTC One is stuck on HTC logo that comes on while switching it on....
ti_coco said:
I did what you say but now my HTC One is stuck on HTC logo that comes on while switching it on....
Click to expand...
Click to collapse
Did you use 2.6.3.3 version of twrp?
When installing the ROM did you choose to do a complete wipe in the options whilst installing it?
make sure you flash the lastest firmware as well...
divxdvd said:
make sure you flash the lastest firmware as well...
Click to expand...
Click to collapse
I believe he is already on the latest firmware for his device
Also, from Vomers Guide:
FIRMWARE FAQ:
Q: Do I need S-OFF for firmware flashing?
A: YES!
OP doesn't have s off
It works now, for information I used clockwork but it didn't work so I reflash my phone wirth twrp-2.6.3.3-m7.img and erase cach. Then I reinstall the ROM and it worked!
I have tried updating the htc one m7 to lollipop and during installation phone went into recovery mode. this is the getvar log from device. currently i have an unlocked bootloader.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.07.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4116mV
(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.049s
can some one guide on how to proceed forward?
One more issue is im unable to connect the phone to laptop. i have tried installing a custom ROM.
[email protected] said:
I have tried updating the htc one m7 to lollipop and during installation phone went into recovery mode. this is the getvar log from device. currently i have an unlocked bootloader.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.28.3218.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.07.1540.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BS_US001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4116mV
(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.049s
can some one guide on how to proceed forward?
One more issue is im unable to connect the phone to laptop. i have tried installing a custom ROM.
Click to expand...
Click to collapse
its very easy to fix, all you have to do is run the dev edition RUU again to make sure everything is fully stock for the update to work, however, your real issue is the fact it wont connect to your laptop, why not ? whats it doing ? what does device manager say ?
Ok. Connecting to computer im least bothered. I need it to be up and running.
I have unlocked bootloader, installed TWRP 2.7.1.1. Where can i get the dev edition RUU? Can i just run it from system by connecting phone in fastboot?
[email protected] said:
Ok. Connecting to computer im least bothered. I need it to be up and running.
I have unlocked bootloader, installed TWRP 2.7.1.1. Where can i get the dev edition RUU? Can i just run it from system by connecting phone in fastboot?
Click to expand...
Click to collapse
your computer needs to see the phone whilst the phone is in fastboot mode in the bootloader for anything to work, but the the updated lollipop RUU is here: http://forum.xda-developers.com/htc-one/general/guide-convert-m7-developer-edition-t2840311
Yeah, system is able to read commands from fastboot. So i have follow the 2nd part of the link above?
[email protected] said:
Yeah, system is able to read commands from fastboot. So i have follow the 2nd part of the link above?
Click to expand...
Click to collapse
yes just the 2nd part as your already on dev edition, if it fails, you may have to download and install the firmware first, due to you running a custom recovery, you can find the firmware here, thanks to @alray https://www.androidfilehost.com/?w=files&flid=20283, you will want the 6.07.1540.2 firmware which matches your version main.
I have connected the device in fastboot and ran the RUU, but it failed saying Recovery, and then it exited the process on computer. But my phone is still in the same silver htc logo, does it mean its installing or it failed to install? And BTW how do i install that firmware and also there a few versions if the same firmware!
If you can help me with sorting out this it would be of great help!! Thanks in advance for all the help till now...
[email protected] said:
I have connected the device in fastboot and ran the RUU, but it failed saying Recovery, and then it exited the process on computer. But my phone is still in the same silver htc logo, does it mean its installing or it failed to install? And BTW how do i install that firmware and also there a few versions if the same firmware!
If you can help me with sorting out this it would be of great help!! Thanks in advance for all the help till now...
Click to expand...
Click to collapse
here you go, easy way, download this: https://www.androidfilehost.com/?fid=95897840722641610 rename it to rom.zip for ease
place it in the same folder as adb and fastboot on your computer, then open a command window there. first you need to get out of RUU mode, so type fastboot reboot-bootloader, your phone should return to the bootloader screen, then enter recovery on your phone, hopefully twrp recovery still, then type adb push rom.zip /sdcard/, takes a while but it will let you know when its done, it will look like its doing nothing whilst its pushing.
unplug your phone and flash the rom, select stock radio and stock recovery when prompted, when the phone starts back up, check for updates, as you are s-on your bootloader will need to be relocked to update.
Thanks man for the help.
let me try and install that thing. Need to know why to relock the boot loader? and how can i relock it?
[email protected] said:
Thanks man for the help.
let me try and install that thing. Need to know why to relock the boot loader? and how can i relock it?
Click to expand...
Click to collapse
just type fastboot oem lock with your phone in fastboot mode, if you need to unlock in the future, just use the unlock token again or goto HTC Dev to get a new one.
Can i locck it belore running RUU or flashing rom?
[email protected] said:
Can i locck it belore running RUU or flashing rom?
Click to expand...
Click to collapse
no, it needs to be unlocked for flashing the reset rom in order to use the custom recovery.
locked / re-locked for running RUU
C:\Users\USER\Desktop\OneDrivers_Fastboot\Fastboot>adb push rom.zip /sdcard/
error: device not found
Im getting this on pushing from recovery mode. How can i resolve this?
[email protected] said:
C:\Users\USER\Desktop\OneDrivers_Fastboot\Fastboot>adb push rom.zip /sdcard/
error: device not found
Im getting this on pushing from recovery mode. How can i resolve this?
Click to expand...
Click to collapse
when your phone is in recovery, have a look in device manager, see what it says for your phone ?
Its not able to find my device properly. Attaching it
[email protected] said:
Its not able to find my device properly. Attaching it
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=52135024
See Question (2 in this faq post to fix your drivers
That worked great man!! I have pushed it to device and now installing.
Its been 10 mins and i can still see the Installing bar running with 0.00%.. Is it correct or abnormal?
[email protected] said:
That worked great man!! I have pushed it to device and now installing.
Its been 10 mins and i can still see the Installing bar running with 0.00%.. Is it correct or abnormal?
Click to expand...
Click to collapse
no that doesnt sound right, has it done anything in aroma, like wipe partitions etc ?
Seanie280672 said:
your computer needs to see the phone whilst the phone is in fastboot mode in the bootloader for anything to work, but the the updated lollipop RUU is here: http://forum.xda-developers.com/htc-one/general/guide-convert-m7-developer-edition-t2840311
Click to expand...
Click to collapse
Seanie280672 said:
no that doesnt sound right, has it done anything in aroma, like wipe partitions etc ?
Click to expand...
Click to collapse
I have choose to wipe partition. Shall i not?
[email protected] said:
I have choose to wipe partition. Shall i not?
Click to expand...
Click to collapse
yes you should, but has the aroma installer done that part yet is what im asking ?
Hey,
My HTC One is notifying me of new updates, after rebooting to recovery it says can't install it.
unknown volume and can't install INTERNAL SD
Informations I know:
Radio: 4T.29.3218.08
S-ON
unlocked Bootloader
rooted
If you need anything else ask and I'll try and find it out.
Tuskone said:
Hey,
My HTC One is notifying me of new updates, after rebooting to recovery it says can't install it.
unknown volume and can't install INTERNAL SD
Informations I know:
Radio: 4T.29.3218.08
S-ON
unlocked Bootloader
rooted
If you need anything else ask and I'll try and find it out.
Click to expand...
Click to collapse
fastboot getvar all would be good, without IMEI or Serial Number please.
On another note, you MUST BE 100% stock to update, no root, no custom recovery, stock kernal, stock rom, stock recovery, all matching your firmware number.
I've been searching for 2 days but couldn't find a RUU to my radio. And I'm unsure if that would be even enough. I didn't install any other rom, I've just rooted it, so I could remove some of the bloatware.
But nonetheless here's my phone's details:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 3987mV
(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.104s
Tuskone said:
I've been searching for 2 days but couldn't find a RUU to my radio. And I'm unsure if that would be even enough. I didn't install any other rom, I've just rooted it, so I could remove some of the bloatware.
But nonetheless here's my phone's details:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.11
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 3987mV
(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.104s
Click to expand...
Click to collapse
first of all, your not on T-Mobile software, your on WWE World wide english (6.09.401.11)
So ive got to ask, which recovery do you have installed ?
---------- Post added at 09:55 AM ---------- Previous post was at 09:41 AM ----------
what you need to do is flash TWRP 2.8.5.0 from here: http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.8.5.0-m7.img
Code:
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
enter recovery and create a simple backup, just something like the boot, then plug your phone into the computer, whilst its still in recovery mode, that recovery supports MTP so your internal storage should open up on your computer, if it doesnt, you have a driver problem, but if it does, then navigate to TWRP/Backup/Phone serial number/todays date and some other details, delete the backup files out of there and place the files inside this zip in there instead, files only not folders:
https://www.androidfilehost.com/?fid=95832962473396067
unplug your phone and restore that backup.
once restored, restart your phone and just do a basic setup.
then boot back to the bootloader and flash this stock recovery:
https://www.androidfilehost.com/?fid=95832962473395870
again:
Code:
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
when you restart your phone you should now be able to update.
OTA's require you to be 100% stock, including all bloatware, no root, nothing custom.
Seanie280672 said:
first of all, your not on T-Mobile software, your on WWE World wide english (6.09.401.11)
So ive got to ask, which recovery do you have installed ?
---------- Post added at 09:55 AM ---------- Previous post was at 09:41 AM ----------
what you need to do is flash TWRP 2.8.5.0 from here: http://techerrata.com/file/twrp2/m7/openrecovery-twrp-2.8.5.0-m7.img
Code:
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
enter recovery and create a simple backup, just something like the boot, then plug your phone into the computer, whilst its still in recovery mode, that recovery supports MTP so your internal storage should open up on your computer, if it doesnt, you have a driver problem, but if it does, then navigate to TWRP/Backup/Phone serial number/todays date and some other details, delete the backup files out of there and place the files inside this zip in there instead, files only not folders:
https://www.androidfilehost.com/?fid=95832962473396067
unplug your phone and restore that backup.
once restored, restart your phone and just do a basic setup.
then boot back to the bootloader and flash this stock recovery:
https://www.androidfilehost.com/?fid=95832962473395870
again:
Code:
fastboot flash recovery (name of recovery).img
fastboot erase cache
fastboot reboot-bootloader
when you restart your phone you should now be able to update.
OTA's require you to be 100% stock, including all bloatware, no root, nothing custom.
Click to expand...
Click to collapse
So you gave me the firmware, its on the phone now.
I had Unlock.bin, but i can see it has supersu installed in it.
i flashed to stockrecovery from where you helped the other guy.
Im waiting for my download OTA update to finish (official).
Will i be able to update it even that i see its rootet (supersu)?
dukocuk said:
So you gave me the firmware, its on the phone now.
I had Unlock.bin, but i can see it has supersu installed in it.
i flashed to stockrecovery from where you helped the other guy.
Im waiting for my download OTA update to finish (official).
Will i be able to update it even that i see its rootet (supersu)?
Click to expand...
Click to collapse
wrong thread lol, answered on your thread.
Thanks a lot! I'm now a proud lollipopper.
A beer is on me
I own an HTC One (M7) phone and recently I wanted to go back to stock rom because I got tired of the installed custom rom.
All my efforts doing that have failed and I think I've run out of options.
First of all, I tried using TWRP to restore to a Nandroid backup (which successfully worked on my other HTC One when I did that), but got a "failed" error in the first 3 seconds.
Finally, when I ran out of options of going back to stock rom, I thought CM12 would be a good option too. So I downloaded the latest CM12 nightly build, followed the instructions, tried installing it though TWRP but failed again. It seems like, no matter what I tried to do with TWRP it fails.
I run version TWRP 2.6.0.1 , so I thought it updating it to the latest version would be an option. But I can't do that since there's no software in my phone and updating it using ADB tools and TWRP doesn't seem to work either.
The device is S-ON, Tampered and the bootloader is unlocked. I also flashed SuperSU but whenever I reboot the phone, TWRP says my phone is not rooted, even if should be and asks me if I want to install SuperSU, but it seems it does nothing.
I figured out maybe you guys could help me.
iamvladish said:
I thought CM12 would be a good option too. So I downloaded the latest CM12 nightly build, followed the instructions, tried installing it though TWRP but failed again. It seems like, no matter what I tried to do with TWRP it fails.
I run version TWRP 2.6.0.1
Click to expand...
Click to collapse
2.6.0.1 is very old and won't flash any newer roms. CM12 also required at least twrp 2.7.1.1 to be flashed.
http://wiki.cyanogenmod.org/w/HTC_fstab_updates
read under "twrp recoveries" in blue
so I thought it updating it to the latest version would be an option. But I can't do that since there's no software in my phone
Click to expand...
Click to collapse
You don't need any software on your phone to flash a custom recovery.
and updating it using ADB tools
Click to expand...
Click to collapse
The recovery must be flashed using fastboot commands, not adb:
Code:
fastboot flash zip name_of_your_recovery.img
fastboot erase cache
fastboot reboot-bootloader
and TWRP doesn't seem to work either
Click to expand...
Click to collapse
You can only update twrp using twrp on newer twrp version where you have the "flash .img file" option which afaik wasn't possible on 2.6.0.1
The device is S-ON, Tampered and the bootloader is unlocked. I also flashed SuperSU but whenever I reboot the phone, TWRP says my phone is not rooted, even if should be and asks me if I want to install SuperSU, but it seems it does nothing.
Click to expand...
Click to collapse
A "rooted phone" is a misconception. You don't root a phone, you root the OS on it. If there is no OS installed on the phone, there is nothing to root so you'll get this twrp message to root the phone until you have a rooted OS installed.
So you'll have to update your twrp recovery so you can flash a rom
Or
there might be a RUU you could flash on your phone to reset it back to stock. You'll need to post the output of "fastboot getvar all" to determine that (do not post imei or serialno)
So, basically, there's no way of updating TWRP from the bootloader or recovery? I tried flashing it using fastboot flash boot twrp.img, but doesn't seem to work. I was wondering. If I install another recovery and then flash the latest version of twrp, will that work? Or should I install an older rom in order to update TWRP?
But, maybe there's something I could flash to go back to stock rom. Thanks again !
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4310mV
(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
However, I managed to search for a RUU file and downloaded it from here
http://forum.xda-developers.com/showpost.php?p=59436794&postcount=2
I found the one which matched the cid and model of my phone.
But I don't know how to use it. I tried installing it through TWRP but it fails.
Tried installing other recoveries but now none of them works. What to do?
iamvladish said:
So, basically, there's no way of updating TWRP from the bootloader
Click to expand...
Click to collapse
Yes like I said above you can flash twrp from the bootloader using fastboot commands.
I tried flashing it using fastboot flash boot twrp.img, but doesn't seem to work.
Click to expand...
Click to collapse
Its "fastboot flash recovery twrp.img" not "fastboot flash boot twrp.img". "boot" is the kernel partition, so you have flashed twrp to your kernel partition instead of the recovery partition...
fastboot flash recovery twrp.img
fastboot erase cache
fastboot reboot-bootloader
But, maybe there's something I could flash to go back to stock rom. Thanks again !
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.10
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__032
(bootloader) battery-status: good
(bootloader) battery-voltage: 4310mV
(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
However, I managed to search for a RUU file and downloaded it from here
http://forum.xda-developers.com/showpost.php?p=59436794&postcount=2
I found the one which matched the cid and model of my phone.
But I don't know how to use it. I tried installing it through TWRP but it fails.
Tried installing other recoveries but now none of them works. What to do?
Click to expand...
Click to collapse
Yes you can use this ruu on your phone but its not flashed using a recovery. Instructions to flash this ruu are posted at post#1 of that same thread.
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
So now I have the latest TWRP version, but somehow flashing that RUU doesn't work.
When I get to the 7th step, I get this
c:\adb>htc_fastboot flash zip RUU.zip
error: preprocess_file : Cannot open file RUU.zip
I got a feeling that I was so close to fix my phone, but now I don't understand why I get that error.
I relocked the bootloader and did everything in the instructions.
Could you please help me get this?
Dragging the folder to the terminal doesn't work either and I get this
c:\adb>htc_fastboot flash zip C:\adb\RUU.zip
error: preprocess_file : Cannot open file C:\adb\RUU.zip
! Late edit: I managed to return my phone to stock rom using that Nandroid backup (http://forum.xda-developers.com/htc...lease-help-t3044972/post59202323#post59202323).
Apparently, using the latest TWRP version could save you a lot of time.
Thanks a lot !
Hi all,
I apologise for this as it seems there are a few soft brick posts to do with the M7 here. I've tried following them but I'm not having much success.
Last night I decided to root my phone in an effort to find a good ROM that looked good but also didn't have the same battery drain as the stock HTC Lollipop update.
Everything was ok to start with. Got the unlock code, followed a process on HTConeroot.com. Other than TWRP probably not being the latest version, all seemed ok. After SuperSU wouldn't start due to the incorrect binaries, I tried to update it through twrp and the trouble started. It would not start the OS and, being the noob, I pressed 'wipe' on twrp and i have no arrived at the following:
I am currently in a boot loop. It will not start the OS. I cannot gain access to recovery mode in TWRP either as the screen flashes up team winning and then just restarts. I can gain access to the Hboot screen and from there can do a USB fastboot link. However, I can't do anything with ADB as it doesn't recognise any device as being connected. Fastboot prompt works fine though.
In a nutshell, I'm looking to get the phone working again. I don't really need to go back to a stock rom - I was looking at google play edition or cyanogen (though I'm told the latter isn't *that* stable). Is someone able to help me?
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.30
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4275mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Phone is stating *unlocked* and *tampered* with S-ON.
Honest989 said:
Hi all,
I apologise for this as it seems there are a few soft brick posts to do with the M7 here. I've tried following them but I'm not having much success.
Last night I decided to root my phone in an effort to find a good ROM that looked good but also didn't have the same battery drain as the stock HTC Lollipop update.
Everything was ok to start with. Got the unlock code, followed a process on HTConeroot.com. Other than TWRP probably not being the latest version, all seemed ok. After SuperSU wouldn't start due to the incorrect binaries, I tried to update it through twrp and the trouble started. It would not start the OS and, being the noob, I pressed 'wipe' on twrp and i have no arrived at the following:
I am currently in a boot loop. It will not start the OS. I cannot gain access to recovery mode in TWRP either as the screen flashes up team winning and then just restarts. I can gain access to the Hboot screen and from there can do a USB fastboot link. However, I can't do anything with ADB as it doesn't recognise any device as being connected. Fastboot prompt works fine though.
In a nutshell, I'm looking to get the phone working again. I don't really need to go back to a stock rom - I was looking at google play edition or cyanogen (though I'm told the latter isn't *that* stable). Is someone able to help me?
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.61.0000
(bootloader) version-baseband: 4T.35.3218.16
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 7.19.401.30
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4275mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-0e2a13e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Phone is stating *unlocked* and *tampered* with S-ON.
Click to expand...
Click to collapse
Edit your post above and remove your IMEI and Serialno, keep these numbers private.
ADB doesn't work from bootloader, only fastboot will. ADB is only available from a custom recovery or from a booted OS with USB debug enabled.
You'll first need a working recovery so reflash twrp recovery:
Code:
fastboot flash recovery name_of_file.img
fastboot erase cache
fastboot reboot-bootloader
Thanks - I think I have it... I part way followed this thread - which means i've relocked the bootloader :/
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
however, I need to find an RUU of 7.19.401.30 - thought I'd found the right version only to get blocked at model number. I'd got the .22 instead.....
To date, I've not been able to...
Honest989 said:
Thanks - I think I have it... I part way followed this thread - which means i've relocked the bootloader :/
http://forum.xda-developers.com/htc-one/general/lollipop-ruu-zip-small-collection-t3053944
however, I need to find an RUU of 7.19.401.30 - thought I'd found the right version only to get blocked at model number. I'd got the .22 instead.....
To date, I've not been able to...
Click to expand...
Click to collapse
There is no 7.19.401.30 ruu, the latest one is 7.19.401.22 and can't be flashed on your phone since its a downgrae in version (requires s-off)
Unlock your bootloader and flash your custom rom.
Thanks - I'm now in a stable TWRP env. I now need to figure out how to push a rom across to the phone.
Next question. Does s-mode have to be off. If so, how is this achieved via fastboot? (or is it a case of more tools and tinkering). As I've already made a hash of things once, I'm loath to do this........
Honest989 said:
Thanks - I'm now in a stable TWRP env. I now need to figure out how to push a rom across to the phone.
Next question. Does s-mode have to be off. If so, how is this achieved via fastboot? (or is it a case of more tools and tinkering). As I've already made a hash of things once, I'm loath to do this........
Click to expand...
Click to collapse
You don't need s-off to flash a rom, if you want s-off for going back to stock using the ruu (downgrade) you'll first need a working rom. S-OFF can only be achieved from a working rom using Sunshine S-OFF
To push a rom to your phone, if you have a recent twrp version (2.8+) just boot your phone in recovery mode connected to your pc using the usb cable and you should be able to see your phone storage (like if it was a usb stick). just drag and drop your rom.zip to your phone and then in twrp select "install" and flash the rom. If you are one an older version of twrp, use adb to push the rom to your phone:
Code:
adb push name_of_rom.zip /sdcard
Thanks guys what solved it was:
Up to date version of TWRP
Latest version of Android revolution.
The reson it wasn't booting or providing some sort of DR was because I had somehow wiped everything from the phone. By way of complete fluke, I now have a rooted phone running on a completely clean install directory. Remind me to back up later on.