I'm having some issues with getting the firmware updated on my m7 and hoping someone can help.
I had posted some info in another thread of mine, but the thread is now over a year old so I figured I would start a new one.
First, here is my get-var output
C:\DroidTools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 1.00.20.0626
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 99000146505640
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4001mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.094s
Not sure why the get-var didn't finish out (Too many links) ?
Anyways I tried updating the firmware with the latest I could find for the sprint variant, but I received this error.
"Target didn't report max-download-size"
sending 'zip' (45578 KB)...
OKAY [2.807s]
writing 'zip' . . .
(bootloader) zip header checking . . .
(bootloader) zip info parsing . . .
FAILED (remote: 99 unknown fail)
finished. total tim: 3.067s
I've tried a few different versions of firmware as well and still no luck.
I can just fastboot reboot bootloader and then reboot after that and I'm back to my normal stuff with no issues though.
I was also able to flash a newer twrp recovery without any hiccups.. so not sure what is up.
I am currently running AICP 12.1 but I am getting allot of crashes on random thing, and I suspect my mega-old firmware may be contributing. I also tried the last CyanogenMod that was available (13...?) but I couldn't get data and calls to work.
I also attempted to re-lock the boot-loader and tried flashing the firmware that way, but I received a different error.
"remote 12 signature verify fail"
After that I had to scramble and remember how to unlock the boot-loader again just to get my phone to boot back up lol. I haven't had my unlock file in years so that was fun.
So I'm stuck at 1.44.0000 for now. I'm starting to wonder if i have to find an older firmware first before I can jump to a newer one?
Also slightly confused on the RUU. I am already running custom recovery and custom ROM. Is updating the RUU still necessary?
All feedback and help is welcomed.
Thanks
cloud66 said:
I'm having some issues with getting the firmware updated on my m7 and hoping someone can help.
I had posted some info in another thread of mine, but the thread is now over a year old so I figured I would start a new one.
First, here is my get-var output
C:\DroidTools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 1.00.20.0626
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.31.651.2
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 99000146505640
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: SPCS_001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4001mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
getvar:all FAILED (status read failed (Too many links))
finished. total time: 0.094s
Not sure why the get-var didn't finish out (Too many links) ?
Anyways I tried updating the firmware with the latest I could find for the sprint variant, but I received this error.
"Target didn't report max-download-size"
sending 'zip' (45578 KB)...
OKAY [2.807s]
writing 'zip' . . .
(bootloader) zip header checking . . .
(bootloader) zip info parsing . . .
FAILED (remote: 99 unknown fail)
finished. total tim: 3.067s
I've tried a few different versions of firmware as well and still no luck.
I can just fastboot reboot bootloader and then reboot after that and I'm back to my normal stuff with no issues though.
I was also able to flash a newer twrp recovery without any hiccups.. so not sure what is up.
I am currently running AICP 12.1 but I am getting allot of crashes on random thing, and I suspect my mega-old firmware may be contributing. I also tried the last CyanogenMod that was available (13...?) but I couldn't get data and calls to work.
I also attempted to re-lock the boot-loader and tried flashing the firmware that way, but I received a different error.
"remote 12 signature verify fail"
After that I had to scramble and remember how to unlock the boot-loader again just to get my phone to boot back up lol. I haven't had my unlock file in years so that was fun.
So I'm stuck at 1.44.0000 for now. I'm starting to wonder if i have to find an older firmware first before I can jump to a newer one?
Also slightly confused on the RUU. I am already running custom recovery and custom ROM. Is updating the RUU still necessary?
All feedback and help is welcomed.
Thanks
Click to expand...
Click to collapse
The firmware.zip you are trying to flash (the one linked in the other thread) isn't signed so your phone must be s-off. Sorry I should have mentioned that earlier but didn't noticed yours was s-on.
Its actually s-off now, showing "shipped s-on"?
Not sure what that means but the bootloader is definitely unlocked.
cloud66 said:
Its actually s-off now, showing "shipped s-on"?
Not sure what that means but the bootloader is definitely unlocked.
Click to expand...
Click to collapse
bootloader unlocked doesn't mean s-off. If your phone is s-off you should see "PVT SHIP S-OFF" and "Security: OFF" in your fastboot getvar all output
On a S-ON phone you can only flash signed firmware.zip and it must be done with a locked (or re-locked) bootloader
On a S-OFF phone you can flash signed or unsigned firmware.zip and the bootloader status doesn't matters (can be locked, re-locked or unlocked).
The sprint firmware linked in the other thread, the one that you are trying to flash is an unsigned zip so you need s-off first. Otherwise you can try to update the whole phone using the latest sprint RUU from htc's website, not sure it will work on hboot 1.44. Backup important files before trying, the ruu will wipe and update your rom and firmware. Btw you also need to be locked/re-locked to flash a ruu if your phone is s-on.
alray said:
bootloader unlocked doesn't mean s-off. If your phone is s-off you should see "PVT SHIP S-OFF" and "Security: OFF" in your fastboot getvar all output
On a S-ON phone you can only flash signed firmware.zip and it must be done with a locked (or re-locked) bootloader
On a S-OFF phone you can flash signed or unsigned firmware.zip and the bootloader status doesn't matters (can be locked, re-locked or unlocked).
The sprint firmware linked in the other thread, the one that you are trying to flash is an unsigned zip so you need s-off first. Otherwise you can try to update the whole phone using the latest sprint RUU from htc's website, not sure it will work on hboot 1.44. Backup important files before trying, the ruu will wipe and update your rom and firmware. Btw you also need to be locked/re-locked to flash a ruu if your phone is s-on.
Click to expand...
Click to collapse
Can you help me with an M7 that has these details:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.60.0000
(bootloader) version-baseband: 1.01.20.1225
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid: xxxxxxxxxxxxx
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4305mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-91bb20e1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
The phone won't boot and the version-main is blank. First time I'm handling an M7 since this is a friends and the guides all involve toolkits so kinda lost at the moment. Bootloader is locked
Unlocked the bootloader only to find it has TWRP and no OS
Renosh said:
Can you help me with an M7 that has these details:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.60.0000
(bootloader) version-baseband: 1.01.20.1225
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxx
(bootloader) meid: xxxxxxxxxxxxx
(bootloader) product: m7_wls
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0720000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4305mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-91bb20e1
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
The phone won't boot and the version-main is blank. First time I'm handling an M7 since this is a friends and the guides all involve toolkits so kinda lost at the moment. Bootloader is locked
Unlocked the bootloader only to find it has TWRP and no OS
Click to expand...
Click to collapse
You can flash it back to stock rom using a RUU.
The latest version is here: http://dl3.htc.com/application/RUU_...691.655435036.1511537283-936972463.1506975706
Launch the .exe file with the phone in bootloader mode and showing "fastboot usb" in red
If you are not using a Windows PC you can find the .zip version of the same RUU here: https://androidfilehost.com/?fid=24588232905725176
You can flash it using fastboot in ruu mode:
Code:
htc_fastboot oem rebootRUU
htc_fastboot flash zip PN071IMG_M7WLS_L50_SENSE60_SPRINT_6.23.651.10_signed.zip
htc_fastboot reboot
If you prefer to flash a custom rom instead of stock, just make sure to choose one compatible with the Sprint variant (M7WLS). Push it to your phone memory and flash it using the "install" menu from twrp.
If the phone was sim-unlocked (working on other network than Sprint) you might have to sim-unlock again after flashing a RUU.
alray said:
You can flash it back to stock rom using a RUU.
The latest version is here: http://dl3.htc.com/application/RUU_...691.655435036.1511537283-936972463.1506975706
Launch the .exe file with the phone in bootloader mode and showing "fastboot usb" in red
If you are not using a Windows PC you can find the .zip version of the same RUU here: https://androidfilehost.com/?fid=24588232905725176
You can flash it using fastboot in ruu mode:
Code:
htc_fastboot oem rebootRUU
htc_fastboot flash zip PN071IMG_M7WLS_L50_SENSE60_SPRINT_6.23.651.10_signed.zip
htc_fastboot reboot
If you prefer to flash a custom rom instead of stock, just make sure to choose one compatible with the Sprint variant (M7WLS). Push it to your phone memory and flash it using the "install" menu from twrp.
If the phone was sim-unlocked (working on other network than Sprint) you might have to sim-unlock again after flashing a RUU.
Click to expand...
Click to collapse
Thanks I actually already managed to fix it using this thread:
https://forum.xda-developers.com/showthread.php?t=2795856
I used the full firmware but had to install this redistributable file for RUU to work (Windows 10) after locking bootloader:
https://npackd.appspot.com/p/com.microsoft.VisualCPPRedistributable/9.0.21022.8
I'll have to search for sim unlock, crap
alray said:
bootloader unlocked doesn't mean s-off. If your phone is s-off you should see "PVT SHIP S-OFF" and "Security: OFF" in your fastboot getvar all output
On a S-ON phone you can only flash signed firmware.zip and it must be done with a locked (or re-locked) bootloader
On a S-OFF phone you can flash signed or unsigned firmware.zip and the bootloader status doesn't matters (can be locked, re-locked or unlocked).
The sprint firmware linked in the other thread, the one that you are trying to flash is an unsigned zip so you need s-off first. Otherwise you can try to update the whole phone using the latest sprint RUU from htc's website, not sure it will work on hboot 1.44. Backup important files before trying, the ruu will wipe and update your rom and firmware. Btw you also need to be locked/re-locked to flash a ruu if your phone is s-on.
Click to expand...
Click to collapse
Thanks for the info. I'm going to try this sometime this week hopefully.
I've been running AICP 7.1.1 for nearly 3 weeks so far with minor hiccups now and then so i'm slightly hesitant to screw something up again :-/
I will update this as soon as I try a signed RUU from HTC.
Will a signed RUU destroy my recovery as well?
Also do I need to unlock after I flash the RUU?
Steps would be
1. relock bootloader
2. Install signed RUU
3. Relock Bootloader
4. Install TWRP
5. Install Rom
6. ?
Assuming I have these correct and everything works that is.
cloud66 said:
Thanks for the info. I'm going to try this sometime this week hopefully.
I've been running AICP 7.1.1 for nearly 3 weeks so far with minor hiccups now and then so i'm slightly hesitant to screw something up again :-/
I will update this as soon as I try a signed RUU from HTC.
Will a signed RUU destroy my recovery as well?
Also do I need to unlock after I flash the RUU?
Steps would be
1. relock bootloader
2. Install signed RUU
3. Re-unlock Bootloader (use www.htcdev.com/bootloader)
4. Install TWRP
5. Install Rom
6. ?
Assuming I have these correct and everything works that is.
Click to expand...
Click to collapse
Stock recovery will overwrite twrp when flashing a RUU, not really a concern since it will take only a few minutes to reflash twrp. And yes you'll need to re-unlock the bootloader after flashing the ruu, before you can install twrp back to your recovery partition. Steps 1 to 5 above are correct.
Related
I've flashed multiple ROMS but I don't know what what's up now.
I was stuck on FTS Rom and couldn't flash any other ROMS- they wouldn't take. It would always reboot in FTS.
So in TWRP, I did an advanced wipe... everything was gone including the multiple various ROMS and backups in both TWRP and CLKmod. Trouble is, now I can get as far as flashing various new recoveries from the bootloader, but I can't push any rom to it or flash anything from the bootloader.
Extra kicker- I can NOT mount the phone on my computer. This has been the case for a while, not from any ROM. Not from FTS Rom, not from any recovery... can not mount the phone and transfer files.
HTC Dumlock also did not work.
Specs-
HTC One- unlocked, rooted, HBoot 1.55, S-On, Radio 4%.20.3218.13
Any help would be appreciated.
I did s-off since you're unlocked. Probably the issue. Then I would go into fast boot to either ruu or transfer a rom
I think rumrunner is what works on 1.55 hboot
Sent from my HTC One
krankenator said:
I've flashed multiple ROMS but I don't know what what's up now.
I was stuck on FTS Rom and couldn't flash any other ROMS- they wouldn't take. It would always reboot in FTS.
So in TWRP, I did an advanced wipe... everything was gone including the multiple various ROMS and backups in both TWRP and CLKmod. Trouble is, now I can get as far as flashing various new recoveries from the bootloader, but I can't push any rom to it or flash anything from the bootloader.
Extra kicker- I can NOT mount the phone on my computer. This has been the case for a while, not from any ROM. Not from FTS Rom, not from any recovery... can not mount the phone and transfer files.
HTC Dumlock also did not work.
Specs-
HTC One- unlocked, rooted, HBoot 1.55, S-On, Radio 4%.20.3218.13
Any help would be appreciated.
Click to expand...
Click to collapse
do you know how to use fastboot commands?
post your results from (minus your iemi and serial no)
fastboot getvar all
we can use this info to direct you to the correct RUU to fix your phone
clsA said:
do you know how to use fastboot commands?
post your results from (minus your iemi and serial no)
fastboot getvar all
we can use this info to direct you to the correct RUU to fix your phone
Click to expand...
Click to collapse
Not pro, but I hobble by. Results:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(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: 4350mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
krankenator said:
Not pro, but I hobble by. Results:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4T.20.3218.13
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(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: 4350mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-2da61e5e88
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
Edit your post to match mine.
you have AT&T phone here's the link to the RUU
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
Edit: Keep in mind that resetting your phone with RUU is full wipe and starting from scratch
after it's done you will need to unlock bootloader, flash recovery and Root. Same as if your phone was brand new
clsA said:
Edit your post to match mine.
you have AT&T phone here's the link to the RUU
http://www.htc1guru.com/dld/ruu_m7_...3_10-38j-1157-04_release_334235_signed_2-exe/
Edit: Keep in mind that resetting your phone with RUU is full wipe and starting from scratch
after it's done you will need to unlock bootloader, flash recovery and Root. Same as if your phone was brand new
Click to expand...
Click to collapse
Thanks. I don't suppose there is a Mac version for this? I don't currently have Windows installed. If not, I"ll just have to fix this later.
Thanks for all your help.
krankenator said:
Thanks. I don't suppose there is a Mac version for this? I don't currently have Windows installed. If not, I"ll just have to fix this later.
Thanks for all your help.
Click to expand...
Click to collapse
yes here
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3-decrypted-zip/
-rom.zip can be flashed using
adb reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip (yes do this 2 times)
fastboot reboot
Click to expand...
Click to collapse
files needed >> http://forum.xda-developers.com/showthread.php?t=2390995
clsA said:
yes here
http://www.htc1guru.com/dld/ruu-zip-m7_ul_jb43_sense50_mr_cingular_us_3-17-502-3-decrypted-zip/
files needed >> http://forum.xda-developers.com/showthread.php?t=2390995
Click to expand...
Click to collapse
Thanks for your help. Downloading the RUU now but before I flash this I just want to be clear.
Do I first need to S-Off using Rumrunner? I can't find a mac version, just Linux and Win.
Then do I need to re-lock my bootloader? (I read that step here http://forum.xda-developers.com/showthread.php?t=2251800)
Then at that point I can flash the RUU or can I just flash the RUU without S-Off or re-locking the bootloader
-rom.zip can be flashed using
adb reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip (yes do this 2 times)
fastboot reboot
krankenator said:
Thanks for your help. Downloading the RUU now but before I flash this I just want to be clear.
Do I first need to S-Off using Rumrunner? I can't find a mac version, just Linux and Win.
Then do I need to re-lock my bootloader? (I read that step here http://forum.xda-developers.com/showthread.php?t=2251800)
Then at that point I can flash the RUU or can I just flash the RUU without S-Off or re-locking the bootloader
-rom.zip can be flashed using
adb reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip rom.zip
fastboot flash zip rom.zip (yes do this 2 times)
fastboot reboot
Click to expand...
Click to collapse
I don't think that file requires s-off
but yes a locked boot loader is needed
fastboot oem lock
Well, time to try something else.
Any ideas anyone?
krankenator said:
Something didn't work. It only reboot to the bootloader.
Pro-Mac-Jesseesktop jesse$ ./fastboot oem lock
Click to expand...
Click to collapse
FAILED (remote: 12 signature verify fail)
I'll take a guess this means you need s-off
or a windows PC to run the RUU.exe I posted first
I have been reading a lot of guides and I am still not sure how I can take my Bell phone and bring it back to stock. I have S-OFF and GPE right not which I installed via a zipped RUU.
Now, if I want to get the latest 4.2.2 that Bell made available for the HTC One, I have to somehow be able to get the OTA and have no custom recovery. I could not find an RUU ZIP or EXE for bell (666), only a stock ROM. I could install that but comes the OTA, it won't install because of the custom recovery.
How can I go back to stock from here? I have been told by a few to just stick to the GPE edition but I would like to got back to sense.
Thank you.
Nic2112 said:
I have been reading a lot of guides and I am still not sure how I can take my Bell phone and bring it back to stock. I have S-OFF and GPE right not which I installed via a zipped RUU.
Now, if I want to get the latest 4.2.2 that Bell made available for the HTC One, I have to somehow be able to get the OTA and have no custom recovery. I could not find an RUU ZIP or EXE for bell (666), only a stock ROM. I could install that but comes the OTA, it won't install because of the custom recovery.
How can I go back to stock from here? I have been told by a few to just stick to the GPE edition but I would like to got back to sense.
Thank you.
Click to expand...
Click to collapse
post output of "fastboot getvar all"
remove S/N & IMEI before posting
kamilmirza said:
post output of "fastboot getvar all"
remove S/N & IMEI before posting
Click to expand...
Click to collapse
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ...
(bootloader) imei: ...
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3975mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.076s
Nic2112 said:
C:\Android>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ...
(bootloader) imei: ...
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3975mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-bee46337
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.076s
Click to expand...
Click to collapse
your previous CID was BM_001, right?
look into nkk71 SuperGUIDE in my signature
kamilmirza said:
post output of "fastboot getvar all"
remove S/N & IMEI before posting
Click to expand...
Click to collapse
NKK71 helped me bring the phone back to stock GPE, but I'm getting weird problems and I am not sure why, but I remember I didn't have those problems with stock. Stuff like streaming not working over WiFi, MMS messages not sent when I have WiFi enabled, stuff like that.
The problem is that Bell (x.xx.666x.) has no RUU that I can find, only a nandroid which I could use but that won't give me the option to get the OTA (I think)
kamilmirza said:
your previous CID was BM_001, right?
Click to expand...
Click to collapse
I believe so, yes.
Nic2112 said:
NKK71 helped me bring the phone back to stock GPE, but I'm getting weird problems and I am not sure why, but I remember I didn't have those problems with stock. Stuff like streaming not working over WiFi, MMS messages not sent when I have WiFi enabled, stuff like that.
The problem is that Bell (x.xx.666x.) has no RUU that I can find, only a nandroid which I could use but that won't give me the option to get the OTA (I think)
Click to expand...
Click to collapse
yes sadly there is only nandroid of BM right now
I just updated the firmware today, the one I had was for 4.3 so I upgraded that. I'm just not sure if the problems come from the fact that there is no HTC One google edition in Canada and that either my radios or firmware are not working perfectly on bell.
Nic2112 said:
I just updated the firmware today, the one I had was for 4.3 so I upgraded that. I'm just not sure if the problems come from the fact that there is no HTC One google edition in Canada and that either my radios or firmware are not working perfectly on bell.
Click to expand...
Click to collapse
yeah maybe that could be the problem
why not try the nandroid and see how it goes?
Hmm, you are going to have a HBOOT mismatch if you run the Canadian Restock method in my guide posted in my signature, as it uses 1.55HBOOT for 4.3 JB, but you are on 1.56 HBOOT.
However if you run the RUU ZIP file for TELUS, you will get the right HBOOT. http://www.htc1guru.com/dld/ruu-zip...157-04_release_336571_signed_2_decrypted-zip/
Download and rename to Telus.zip
See if you can do this:
fastboot oem writecid TELUS001
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip Telus.zip
fastboot flash zip Telus.zip (You will need to run this command twice due to HBOOT downgrade)
fastboot reboot (if it doesn't reboot automatically)
NOTE: I have not personally ran the ZIP file above, but it should be fine.
Oh Wow, there is a guide for Canadian HTC One, didn't know that!
Are you sure that a Telus RUU will work on a Bell phone? They use different networks I think
SaHiLzZ said:
Hmm, you are going to have a HBOOT mismatch if you run the Canadian Restock method in my guide posted in my signature, as it uses 1.55HBOOT for 4.3 JB, but you are on 1.56 HBOOT.
However if you run the RUU ZIP file for TELUS, you will get the right HBOOT. http://www.htc1guru.com/dld/ruu-zip...157-04_release_336571_signed_2_decrypted-zip/
Download and rename to Telus.zip
See if you can do this:
fastboot oem writecid TELUS001
fastboot reboot-bootloader
fastboot oem rebootRUU
fastboot flash zip Telus.zip
fastboot flash zip Telus.zip (You will need to run this command twice due to HBOOT downgrade)
fastboot reboot (if it doesn't reboot automatically)
NOTE: I have not personally ran the ZIP file above, but it should be fine.
Click to expand...
Click to collapse
As I said, i have no personally tested it, but thats the only way to bring your HBOOT down to 1.55.
Other option will be to go all the way down to 1.44 HBOOT. You NEED to be comfortable with using adb/fastboot commands REGARDLESS whichever options you decide to go with.
SaHiLzZ said:
As I said, i have no personally tested it, but thats the only way to bring your HBOOT down to 1.55.
Other option will be to go all the way down to 1.44 HBOOT. You NEED to be comfortable with using adb/fastboot commands REGARDLESS whichever options you decide to go with.
Click to expand...
Click to collapse
I know how to go back to 1.44, I have done that before.
So what you are saying is that if I have the nandroid installed, and stock recovery from your thread, the phone will detect the OTA? It should install no problem because it will be a standard recovery.
Yes 1.44 HBOOT, 1.44 Compatible BELL Nandroid, and Stock recovery will give you future OTAs.
SaHiLzZ said:
Yes 1.44 HBOOT, 1.44 Compatible BELL Nandroid, and Stock recovery will give you future OTAs.
Click to expand...
Click to collapse
Thatk you, one last question before I try this, the OTA, will it replace the radios and firmware as well to Bell's? I guess it depends on what they put in the OTA.
Yes, OTA generally contain new OS, HBOOT, Recovery, and RADIO, practically a full RUU replacement, but not all. IF you are S-ON, you will need to lock bootloader after loading stock recovery, but if you are S-OFF, that doesnt matter, and I will suggest to stay S-OFF!
Please help
I have bell HTC one M7 one Hboot 1.56 the phone boot loader is unlocked rooted and soff the mic is not working on phone I need to set back to stock I can have warranty fix phone can anyone please help me get back to stock so they cant tell it was touched
ginuwine96 said:
I have bell HTC one M7 one Hboot 1.56 the phone boot loader is unlocked rooted and soff the mic is not working on phone I need to set back to stock I can have warranty fix phone can anyone please help me get back to stock so they cant tell it was touched
Click to expand...
Click to collapse
Check the signature block of the previous post (nkk71's SuperGUIDE to returning 100% back to stock) or this one Return to 100% Stock Guide and follow it.
Not sure what file I need
majmoz said:
Check the signature block of the previous post (nkk71's SuperGUIDE to returning 100% back to stock) or this one Return to 100% Stock Guide and follow it.
Click to expand...
Click to collapse
This is my phones Info I am not sure what file to use for it ?
bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.23.3263.28
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.666.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4258mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.070s
ginuwine96 said:
This is my phones Info I am not sure what file to use for it ?
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-main: 4.19.666.8
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) modelid: PN0712000
(bootloader) cidnum: BM___001
Click to expand...
Click to collapse
If you're going to follow my guide, you'll need to use CWM method, using this nandroid: http://www.htc1guru.com/dld/m7-cwm-nandroid-backup-cid-bm___001-1-29-666-5-zip/
make sure to have read it once or twice, to be sure you're comfortable with the process
Morning everyone,
I have been reading for days trying to get a handle on downgrading my phone to JB 4.3. I am s-off, unlocked, rooted, with current TWRP installed. I also am using SuperSu. I suspect I am just not using the right combination of programming. My first thought is that I need the correct Hboot to go with the ROM I want. Currently I am on Android 4.4.2 with sense 5.5. Software is 4.18.502.7 CL302626. I have loaded a custom Hboot which removed the developer red text. and have also removed the tampered warning with a bit of help from here. I am quite happy with remaining s-off and unlocked. I am decent with ADB commands. I understand Linux fairly well, and can even use a hex editor in a crude way.
The last 4.3 RUU_exe and RUU_zip would not complete. The EXE stated not compatible. The ZIP failed looking for the Android-info_txt. I looked in the ZIP file thinking it might need modified and did not find the Android-info file at all. Lead me to believe that I may not be hitting the correct file for my use. So, at the risk of asking a repeated question I have finally come here for a push in the right direction.
I have not messed with all of this since I modded my old EVO 4G from Sprint. The new Android system worked well in stock form. I started down this road because of my desire to move back to 4.3
And I did attempt to use the search function but did not find exactly what I want. Appreciate any help I may be able to get.
lonestarmedic said:
My first thought is that I need the correct Hboot to go with the ROM I want.
Click to expand...
Click to collapse
No! you don't have to flash hboot to be able to flash a rom, you can flash a 4.4 Rom even if i.e you are on hboot 1.44.
lonestarmedic said:
Currently I am on Android 4.4.2 with sense 5.5. Software is 4.18.502.7 CL302626. I have loaded a custom Hboot which removed the developer red text and have also removed the tampered warning with a bit of help from here. I am quite happy with remaining s-off
Click to expand...
Click to collapse
I hope so, never turn S-ON with a modded hboot or you will probably brick your phone. Anyway, never S-ON!
lonestarmedic said:
The last 4.3 RUU_exe and RUU_zip would not complete. The EXE stated not compatible.
Click to expand...
Click to collapse
What version of RUU.exe and zip? Please also post the output of fastboot getvar all except IMEI. What was the error code of the ruu.exe and what was the output when attempting to flash the ruu.zip? you were in fastboot ruu mode right? Did you md5 check both the zip and exe?
lonestarmedic said:
The ZIP failed looking for the Android-info_txt. I looked in the ZIP file thinking it might need modified and did not find the Android-info file at all.
Click to expand...
Click to collapse
android-info.txt should be inside ruu.zip, however if you have the correct ruu for your mid/cid you should not have to modify the android-info.txt
Answers
Will do my best to answer.
1) Your example was a newer ROM on an older Hboot. I am going to older ROM on newer Hboot. Any difference.
2) No intention of turning S-on. Understand risks of modified Hboot. I do have stock Hboot if needed.
3) The RUU.exe is RUU_M7_UL_SENSE 5.0_MR_Cingular_US_3.17.502.3_Radio_4A19.3263.13_10.38j.1157.04_release_334235_signed_2
4) The RUU.zip is RUU Zip M7_UL_JB43_Sense50_MR_Cingular_US_3.17.502.3-decrypted
5) I did not copy the prompt screne on the ADB failure. I believe it was a parsing failure 24 on the Android-info.txt
6) Yes, using fastboot mode. Showing Fastboot USB and entering into the screen with the silver HTC logo.
7) I am honestly not sure if I checked both items for md5 sums.
8) I have to copy and paste the get var yet.
Working on the rest.
lonestarmedic said:
Will do my best to answer.
1) Your example was a newer ROM on an older Hboot. I am going to older ROM on newer Hboot. Any difference.
2) No intention of turning S-on. Understand risks of modified Hboot. I do have stock Hboot if needed.
3) The RUU.exe is RUU_M7_UL_SENSE 5.0_MR_Cingular_US_3.17.502.3_Radio_4A19.3263.13_10.38j.1157.04_release_334235_signed_2
4) The RUU.zip is RUU Zip M7_UL_JB43_Sense50_MR_Cingular_US_3.17.502.3-decrypted
5) I did not copy the prompt screne on the ADB failure. I believe it was a parsing failure 24 on the Android-info.txt
6) Yes, using fastboot mode. Showing Fastboot USB and entering into the screen with the silver HTC logo.
7) I am honestly not sure if I checked both items for md5 sums.
8) I have to copy and paste the get var yet.
Working on the rest.
Click to expand...
Click to collapse
1) no
5,7) make sure to md5 check your ruu. Looks like a bad download
3,4,8) still waiting for your getvar
Text files as requested
Getvar results edited out end of serial number and the imei. The meid does come up as all zeros.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT34NW(xxxxxxx)
(bootloader) imei: a very private thing
(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: 4123mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Android-info text from the zip file
modelid: PN0712000
cidnum: CWS__001
mainver: 3.17.502.3
btype:1
aareport:1
DelCache:1
hbootpreupdate:3
Working on back checking md5 sums
Thanks so far.
JB
lonestarmedic said:
Getvar results edited out end of serial number and the imei. The meid does come up as all zeros.
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4T.24.3218.09
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.18.502.7
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT34NW(xxxxxxx)
(bootloader) imei: a very private thing
(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: 4123mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-c6bbb6d4
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Android-info text from the zip file
modelid: PN0712000
cidnum: CWS__001
mainver: 3.17.502.3
btype:1
aareport:1
DelCache:1
hbootpreupdate:3
Working on back checking md5 sums
Thanks so far.
JB
Click to expand...
Click to collapse
you should try to flash the stock hboot and flash the zip ruu again
Reflashin
alray said:
you should try to flash the stock hboot and flash the zip ruu again
Click to expand...
Click to collapse
I was using the stock Hboot from the OTA via AT&T. I put in the modified one to drop the ugly tampered stuff. Though that might have had something to do with my problem. And tried again with the modified Hboot.
Checked both md5s and good to go there.
JB
Flash timeframe
Is it possible I am too impatient on the flash of the Zip file? Phone sat with no progress for about 5-10 minutes on the silver HTC screen.
JB
Output on oemRUU attempt
Here is what I get when I attempt to use the zip file to flash the phone.
It is the same whether unlocked or relocked.
:\Android\platform-tools>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.047s]
finished. total time: 0.047s
C:\Android\platform-tools>fastboot flash zip jelly.zip
sending 'zip' (1114992 KB)...
OKAY [ 57.002s]
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: 68.047s
Think I got it fixed
Very busy right now but will report back and explain what I did.
Mainly due to being unfamiliar with different file types and which uses what method for update/load.
JB
Back to 4.3 succsessfully
Ok, long process of learning. Found my problem was with the RUU that I was using. The md5 was ok. It just was not what was needed for using via fastboot.
Do not know what it is, but it has the following inside the zip file:
1) META INF folder
2)system folder
3)boot.img
Sure does not work for fastboot!!! I found a zip on here that had the right file name and was odexed. Downloaded, checked the md5, then unzipped to read the Android-info.txt file. All looked right. Made a backup of phone and loaded it on in.
Succsess!!! Of course I had to put TWRP back in and root the phone.
So, brief sequence of what I did:
1) OTA update from 4.3 to 4.4.2 caused problems with applications
2) Phone in stock form with Hboot 1.56
3) Unlocked phone - HTCdev website used
4) Rooted phone with SuperSU and installed TWRP
5) Played with ROMS and did not like any of them, decided to revert back to 4,3
6) Phone would not S-off with stock ROM using Rumrunner
7) Ended up with the combination of Android Revolution HD and Firewater. Used my UBUNTU Linux to perform S-off.
8) Back-up performed
9) Used zip file and fastboot to load 4.3
10) Now have Hboot 1.56 with 4.3 unlocked, stock Hboot, and S-off.
Thanks for listening to my rantings.
Maybe this will help someone else with an AT&T HTC One.
JB
Hi, Hope this post is in the right place, apologies if not.
I recently got a HTC One (M7) which was already unlocked, S-OFF and rooted and had 4.4 on it but i wanted to upgrade that OS so installed GPE and then it updated a few times to 5.01 which was all good but now i want to go back to 4.4 and this is the problem i'm having.
I'm in the UK using a O2 UK RUU file which i know does work but now when i go to use it i get as far as 'Checking Header' (5%) and thats it ..it wont go any further? I have tried in compatibility mode but that just returns errors.. I am using Fastboot & ADB tools and tried pushing the firmware but i'm really quite a novice when it comes t stuff like this ..
I tried fastboot getvar and all i get it a list of commands now which i dont understand
I do know my CID is 111111
Here's the Bootloader Info:
*** UNLOCKED***
M7 UL PVT SHIP S-OFF RH
CID 11111111
HBOOT 1.54.0000
RADIO 4T.30.3218.21
OPEN DSP v34.120.274.0429
OS 5.11. 1700 .3
All i want to do it flash the phone back to original Stock with OS 4.4 ..
also, when i try to go into recovery it wont let me, i get the green android laying on his back with a red exclamation on him and pressing up with power dont take me into recovery.
Any idea's please?
I would like to thank xda and it's members for all the help previously.. thanks guys
Craig_CFC said:
Hi, Hope this post is in the right place, apologies if not.
I recently got a HTC One (M7) which was already unlocked, S-OFF and rooted and had 4.4 on it but i wanted to upgrade that OS so installed GPE and then it updated a few times to 5.01 which was all good but now i want to go back to 4.4 and this is the problem i'm having.
I'm in the UK using a O2 UK RUU file which i know does work but now when i go to use it i get as far as 'Checking Header' (5%) and thats it ..it wont go any further? I have tried in compatibility mode but that just returns errors.. I am using Fastboot & ADB tools and tried pushing the firmware but i'm really quite a novice when it comes t stuff like this ..
I tried fastboot getvar and all i get it a list of commands now which i dont understand
I do know my CID is 111111
Here's the Bootloader Info:
*** UNLOCKED***
M7 UL PVT SHIP S-OFF RH
CID 11111111
HBOOT 1.54.0000
RADIO 4T.30.3218.21
OPEN DSP v34.120.274.0429
OS 5.11. 1700 .3
All i want to do it flash the phone back to original Stock with OS 4.4 ..
also, when i try to go into recovery it wont let me, i get the green android laying on his back with a red exclamation on him and pressing up with power dont take me into recovery.
Any idea's please?
I would like to thank xda and it's members for all the help previously.. thanks guys
Click to expand...
Click to collapse
Flash the firmware that matches your RUU first
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
then flash the RUU ... RUU gets stuck on the Hboot update step, flashing firmware first eliminates this problem
clsA said:
Flash the firmware that matches your RUU first
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
then flash the RUU ... RUU gets stuck on the Hboot update step, flashing firmware first eliminates this problem
Click to expand...
Click to collapse
Hi and thank you for your help.. i tried looking for the correct firmware.zip but after trying to flash it i get errors and 'fails' i'm not exactly sure which firmware i should be using - i did go to HTC site and selected what i thought were O2 UK FW files (1 was MR 3, 1 MR2 and 2 x zip files) so i assumed the .zip files were the FW files but its with these i got the errors. When i flashed them it did read them but aftr a few seconds returned a fail.
The RUU i am trying to put back on is RUU_M7_UL_K44_SENSE55_MR_O2_UK_4.20.206.16_Radio_4A.23.3263.28_10.38r.1157.04L_release_353143_signed_2 which i know works on my device as i used it before i installed the GPE.
Any ideas please? I'm sorry i cant provide any more information.
Getvar Info:
C:\Users\Craig\Desktop\platform-tools>fastboot g
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.09.401.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: o2___001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4097mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-5d4c562c
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.152s
C:\Users\Craig\Desktop\platform-tools>
Thanks again!
Craig_CFC said:
Hi and thank you for your help.. i tried looking for the correct firmware.zip but after trying to flash it i get errors and 'fails' i'm not exactly sure which firmware i should be using - i did go to HTC site and selected what i thought were O2 UK FW files (1 was MR 3, 1 MR2 and 2 x zip files) so i assumed the .zip files were the FW files but its with these i got the errors. When i flashed them it did read them but aftr a few seconds returned a fail.
The RUU i am trying to put back on is RUU_M7_UL_K44_SENSE55_MR_O2_UK_4.20.206.16_Radio_4A.23.3263.28_10.38r.1157.04L_release_353143_signed_2 which i know works on my device as i used it before i installed the GPE.
Any ideas please? I'm sorry i cant provide any more information.
Getvar Info:
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.29.3218.08
(bootloader) version-main: 6.09.401.5
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: o2___001
(bootloader) security: off
all: Done!
finished. total time: 0.152s
C:\Users\Craig\Desktop\platform-tools>
Thanks again!
Click to expand...
Click to collapse
Well you phone is having a bit of an identity crises
you have hboot 1.54 ( assume it's the Dark bootloader for GPE)
your Firmware version is 6.x.401.x which is for the International version
and your CID is O2
I'm going to recommend you convert to International by changing you CID
fastboot oem writecid HTC__001
then flash this firmware
https://www.androidfilehost.com/?fid=23329332407574077
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot
followed by this RUU
http://www.androidruu.com/getdownlo...10.38r.1157.04L_release_353069_signed_2-1.exe
or
RUU_M7_UL_K44_SENSE55_MR_HTC_Europe_4.19.401.9_R_Radio_4A.23.3263.28_10.38r.1157.04L_release_353069_signed_2-1.exe - 1.50 GB
Maybe a little late but you could also try this:
http://forum.xda-developers.com/showthread.php?t=2358781
Go to post #2 and follow those instructions. Then flash whatever RUU you want.
I converted to GPE one time, didn't like it and also had trouble getting back to KK.
ANGRY_robert said:
Maybe a little late but you could also try this:
http://forum.xda-developers.com/showthread.php?t=2358781
Go to post #2 and follow those instructions. Then flash whatever RUU you want.
I converted to GPE one time, didn't like it and also had trouble getting back to KK.
Click to expand...
Click to collapse
Thanks again for the help.. much appreciated - im using TWRP v2.7 and wiped the whole phone by accident - i'm trying to push (adb sideload fw_4.19.401.9_custom.zip) but keeps coming back as no device - i have a yellow exclamation in device manager under 'other devices' 'one' and cant seem to find a windows 7 driver for this? once i can push or sideload the firmware i can flash it correct?
Thanks again
So to refresh my memory, you were on stock GPE and want to go back to stock sense correct? Now you have wiped the phone using twrp and twrp is all that is left?
Sent from my HTC One using XDA Free mobile app
ANGRY_robert said:
So to refresh my memory, you were on stock GPE and want to go back to stock sense correct? Now you have wiped the phone using twrp and twrp is all that is left?
Sent from my HTC One using XDA Free mobile app
Click to expand...
Click to collapse
Yes thats correct - i'm new to all this flashing stuff but have been reading lots of various posts on xda ...
This is whats returned from fastboot flash:
C:\Users\Craig\Desktop\platform-tools>fastboot flash zip fw_4.19.401.9_custom.zi
p
target reported max download size of 1526722560 bytes
sending 'zip' (27605 KB)...
OKAY [ 2.357s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 2.408s
C:\Users\Craig\Desktop\platform-tools>
and...
C:\Users\Craig\Desktop\platform-tools>adb push zip fw_4.19.401.9_custom.zip
adb server is out of date. killing...
* daemon started successfully *
error: device not found
i really dont know what to do now - i have all the correct files in the platform tools folder where i run the fastboot & adb commands (firmware & ruu) and have changed the CID to HTC___001
When i'm in recovery mode (TWRP) i get the yellow exclamation (screenshot hopefully attached)
First you need to get the driver working. Click on "one" and see if you can select from a list of devices on the pc. Now if the last working firmware on the phone was gpe then you need to push/sideload a gpe based Rom. This is because the partition structure is different than sense. You need to get a working Rom onto the phone first.
Sent from my HTC One using XDA Free mobile app
Craig_CFC said:
Yes thats correct - i'm new to all this flashing stuff but have been reading lots of various posts on xda ...
This is whats returned from fastboot flash:
C:\Users\Craig\Desktop\platform-tools>fastboot flash zip fw_4.19.401.9_custom.zi
p
target reported max download size of 1526722560 bytes
sending 'zip' (27605 KB)...
OKAY [ 2.357s]
writing 'zip'...
FAILED (remote: not allowed) You get this when the bootloader is locked did you relock the bootloader ?
finished. total time: 2.408s
C:\Users\Craig\Desktop\platform-tools>
and...
C:\Users\Craig\Desktop\platform-tools>adb push zip fw_4.19.401.9_custom.zip This is useless the firmware has to be flashed in fastboot RUU mode
adb server is out of date. killing...
* daemon started successfully *
error: device not found
i really dont know what to do now - i have all the correct files in the platform tools folder where i run the fastboot & adb commands (firmware & ruu) and have changed the CID to HTC___001
When i'm in recovery mode (TWRP) i get the yellow exclamation (screenshot hopefully attached)
Click to expand...
Click to collapse
Read my instructions again in post 4 and follow them
Your drivers are easy to fix see post 2 faq 2 here >> http://forum.xda-developers.com/showthread.php?t=2541082
clsA said:
Read my instructions again in post 4 and follow them
Your drivers are easy to fix see post 2 faq 2 here >> http://forum.xda-developers.com/showthread.php?t=2541082
Click to expand...
Click to collapse
Thank you clsA, i'm doing this now - flashed firmware success.. just adding the RUU now - will let you know how it goes
Craig_CFC said:
Thank you clsA, i'm doing this now - flashed firmware success.. just adding the RUU now - will let you know how it goes
Click to expand...
Click to collapse
All fixed thank you so much - back to good old KitKat thanks for all your help !! very very much appreciated
Craig_CFC said:
All fixed thank you so much - back to good old KitKat thanks for all your help !! very very much appreciated
Click to expand...
Click to collapse
your welcome // Please use the Thanks button below my name
clsA said:
your welcome // Please use the Thanks button below my name
Click to expand...
Click to collapse
Getvar Info:
C:\Users\Craig\Desktop\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.11
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3860mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.076s
Thanks again, ive clicked the like button
Craig_CFC said:
Getvar Info:
C:\Users\Craig\Desktop\platform-tools>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.25.3263.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.401.11
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno:
(bootloader) imei:
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3860mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-4dab9d12
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.076s
Thanks again, ive clicked the like button
Click to expand...
Click to collapse
Looks good .. you should get some OTA updates almost immediately
clsA said:
Looks good .. you should get some OTA updates almost immediately
Click to expand...
Click to collapse
Had 2 OTA's immediately - phone is running sweet again :good: :good:
i attempted to unlock bootloader on my wife's old HTC M7 (Australian/Vodafone), i was able to unlock the bootloader, but had to do some serious trial and error to get a custom recovery installed, eventually got an older twrp loaded, but the phone just refused to boot into recovery.
i then relocked the bootloader (no S-OFF), and when i try and unlock he bootloader now, the phone attempts to boot into the recovery, and is failing...
i've been trying to find an RUU from somewhere, just to blat the phone back to an old state, and try again.
are there RUUs available anywhere? i dont' care if its not for the local carrier, i just want to get a basic android rom on the thing.
However, im curious if i need to s-off to do this (wasnt the case with my previous HTC)
help!
<<<I NOW KNOW WHAT THE ISSUE WAS, I WAS FLASHING RECOVERY FROM THE HTC M8, NOT M7>>>
any ideas?
gjw00 said:
i then relocked the bootloader (no S-OFF), and when i try and unlock he bootloader now, the phone attempts to boot into the recovery, and is failing...
Click to expand...
Click to collapse
Really bad idea to relock the bootloader with a custom recovery, well you shouldn't relock at all if there is anything "custom" installed on your phone.The process of unlocking bootloader requires the stock recovery. The only way to flash the recovery partition is when the bootloader is unlocked or by flashing a signed firmware.zip or ruu.zip. The firmware.zip or ruu.zip must match your version-main, CID and MID.
i've been trying to find an RUU from somewhere, just to blat the phone back to an old state, and try again.
are there RUUs available anywhere? i dont' care if its not for the local carrier, i just want to get a basic android rom on the thing.
Click to expand...
Click to collapse
Its not working like that. If your phone is S-ON the ruu must be made for your carrier (must match CID and MID, must be same or newer version-main)
post the output of "fastboot getvar all" (remove your imei and serialno)
alray said:
Really bad idea to relock the bootloader with a custom recovery, well you shouldn't relock at all if there is anything "custom" installed on your phone.The process of unlocking bootloader requires the stock recovery. The only way to flash the recovery partition is when the bootloader is unlocked or by flashing a signed firmware.zip or ruu.zip. The firmware.zip or ruu.zip must match your version-main, CID and MID.
Its not working like that. If your phone is S-ON the ruu must be made for your carrier (must match CID and MID, must be same or newer version-main)
post the output of "fastboot getvar all" (remove your imei and serialno)
Click to expand...
Click to collapse
ok, i've been trying with a bunch of RUUs i found on the web, and trying to flash inside RUU (wasnt 100% sure what rebooting to RUU was for actually)
the CID is VODAP021, i will need to check when i get back home to see what the MID is, its not the GPE of the m7, if that helps, you reckon if i find an OTA update, and extract out the ruu.zip, it might blat a stock recovery on? will i need to use htc_fastboot, or just the standard fastboot?
my nexus 5 has finally shat it (small child cracked screen, now screen has crapped itself), just want to get a basic android build onto the m7 in the final few weeks before the new pixel phones are out...
gjw00 said:
ok, i've been trying with a bunch of RUUs i found on the web, and trying to flash inside RUU (wasnt 100% sure what rebooting to RUU was for actually)
the CID is VODAP021, i will need to check when i get back home to see what the MID is, its not the GPE of the m7, if that helps, you reckon if i find an OTA update, and extract out the ruu.zip, it might blat a stock recovery on? will i need to use htc_fastboot, or just the standard fastboot?
my nexus 5 has finally shat it (small child cracked screen, now screen has crapped itself), just want to get a basic android build onto the m7 in the final few weeks before the new pixel phones are out...
Click to expand...
Click to collapse
You can extract a firmware.zip (not an ruu) from an ota update and flash it to restore the stock recovery. You must use the right version. Waiting for your fastboot getvar all.
Sent from my HTC One using XDA Labs
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.21.980.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(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
gjw00 said:
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.21.980.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0714000
(bootloader) cidnum: VODAP021
(bootloader) battery-status: good
(bootloader) battery-voltage: 4322mV
(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
Click to expand...
Click to collapse
7.21.980.51 is the latest version for vodap021 and can't find a 7.21.980.51 firmware.zip or ota.zip.
At least there is a 7.21.980.51 ruu on ir-file.com, bad news is that you must register to this website to be able to download (20$ for 30 days)
http://ir-file.com/show.php?token=32375
i can load the phone into the OS btw, i've a feeling that OTA might on the device, you think its' accessible using a non-root browser? i could maybe get the ota zip off the device and try flashing that in RUU?
gjw00 said:
i can load the phone into the OS btw, i've a feeling that OTA might on the device, you think its' accessible using a non-root browser? i could maybe get the ota zip off the device and try flashing that in RUU?
Click to expand...
Click to collapse
Yes, if you can capture the ota this is the best option (because its free). Look in your /download folder, you're looking for a long file name starting with "OTA_M7_UL_L50_SENSE60" and ending with ".zip". Save it on your computer and extract the "firmware.zip" file from it. Then reboot in RUU mode and flash the firmware:
Code:
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot flash zip firmware.zip
fastboot reboot-bootloader
Then you should be able to unlock again.
it worked! thank you..