[Q] One M7 GPE 5.0.1 No IMEI, Baseband - One (M7) Q&A, Help & Troubleshooting

Hi everyone,
So, I upgraded my wifes M7 to a 4.4.4 GPE ROM from a Rogers stock ROM. I unlocked the bootloader from HTCDev and then got S-OFF with firewater. All went swimmingly, until we got the two OTAs for Lollipop. About 4 days ago, the service went out on the phone. In settings, there is no IMEI or Baseband listed, they both say unknown. I checked in fastboot with the getvar all command and the IMEI is there. I tried flashing the radio from the 5.0.1 OTA file, but it says "command rejected" to which it SOUNDS like my S-OFF isn't there anymore, even though the getvar and fastboot screen show it S-OFF.
Here is the getvar output:
C:\Users\Jeff>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4T.30.3218.21
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.11.1700.3
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: H**************
(bootloader) imei: 3************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: GOOGL001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3848mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-e135dbf9
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.114s
So, where do I go from here... It's pretty coincidental that this happened RIGHT around the time that the M7s had the audio bug, but this doesn't sound like the same issue. I think reflashing the radio would work, but it keeps kicking me back, and I've read around here and am unsure of how to re-SOFF the phone. Any help would be appreciated. My wife is not beyond putting the Rogers RUU back on and just waiting for an official GTC update to Lollipop... if that's easier.
Thanks everyone.

First of all try to wipe all phone(full stock reset) and install android gpe 5.0.1 in recovery(you can find it on forum easy) than write me and say if you still have wrong baseband and imei(also probably your phone is not abble to read simcard numbers?)

If fastboot displays the proper imei, best guesses sounds like there is something wrong with the rom or radio that is causing it to report the incorrect imei.
If you have a custom recovery installed (since it appears you are s-off) you could just backup that current rom, wipe/factory reset it to see if it works and if it was something that borked up during the update.
If it still reports the incorrect imei after factory reset, try flashing some known working rom (cm11, omni, etc) and see if everything's working fine in there. Restore your backup after you are done.
That would confirm it's a software-related issue and you can proceed from there.

Tried Factory Reset
So I tried a factory reset from fastboot... no nice. I actually have the stock recovery on the unit so I could receive OTAs from google and not have to jigger around with anything (since it's my wifes phone) ... I THINK I'm S-OFF, but the fact that I couldn't flash a radio.img file in fastboot has me worried that the 5.0.1 update may have partially rescinded it, and I don't want to make things worse by something borking in the middle of a flash.
Would an RUU be the way to go here? Or just try stuffing TWRP onto it and try CM11 ...

if you confirm it's soff, or just even htcdev unlocked (as fastboot would say) you can always flash back stock recovery if you decide to change your mind.
You can extract the recovery img from a working stock rom/ruu, in the meantime flashing twrp/philz opens you for advanced recovery options.
You just flash the recovery in fastboot mode.
fastboot flash recovery twrp-etc.img
fastboot flash recovery nameofstockhtcrecovery.img
As for the radio, not sure what to say. Perhaps try extracting it (from your update file if possible) and flash it from there?

Still no dice
So I flashed TWRP and CM11 ... still no baseband or IMEI. I found a few flashable zips for radio images and still nothing.
I relocked my bootloader, and tried to push a Rogers RUU signed exe, to which I got Error 158 Image Error. No other information is given. I am going down in versions, but as far as I can see, my S-OFF is still in effect.

ssign said:
So I flashed TWRP and CM11 ... still no baseband or IMEI. I found a few flashable zips for radio images and still nothing.
I relocked my bootloader, and tried to push a Rogers RUU signed exe, to which I got Error 158 Image Error. No other information is given. I am going down in versions, but as far as I can see, my S-OFF is still in effect.
Click to expand...
Click to collapse
fastboot oem writecid 11111111
Now you can flash any RUU
Flash your Rogers RUU (after you confirm the md5 matches), and report back :good:

Update: Cannot flash RUU
Hi Again,
So I set SuperCID and tried to reflash the RUU. It got a little further, but hung on the "checking headers" but for almost an hour... so I reset the phone since I had to leave for XMas plans. Now, it gives me an error 155 Image Error when I try to use it. I've seen elsewhere that might need to downgrade my hboot? Since I'm on 1.57.0000? Any ideas about that? Thanks

Related

[Q] Returned to stock, still have Google logo on boot

I've got a Rogers M7 that I had transmorgrified into a Google Play Edition HTC One. That was fun for a bit, but I'm putting back to stock to sell. I got through the CID change, stock nandroid restore, stock recovery flash. But I have an interesting issue - when the phone boots I always get the Google logo first, then the HTC logo and then into the OS. Would anyone have some hints as to how I make the phone behave like stock again on boot?
You either need to flash a Rogers firmware file or run a full sense RUU (International/Dev/etc) I am suspecting thats where the boot screen is showing up from. Keep the phone S-OFF to guard yourself from any issues that may arise. Your buyer wont care, or may even be pleased.
SaHiLzZ said:
You either need to flash a Rogers firmware file or run a full sense RUU (International/Dev/etc) I am suspecting thats where the boot screen is showing up from. Keep the phone S-OFF to guard yourself from any issues that may arise. Your buyer wont care, or may even be pleased.
Click to expand...
Click to collapse
Thanks - oddly enough I just did a factory reset and I'm back to stock. I still can't manage to delete Superuser yet, but I'll figure that out.
SaHiLzZ said:
You either need to flash a Rogers firmware file or run a full sense RUU (International/Dev/etc) I am suspecting thats where the boot screen is showing up from. Keep the phone S-OFF to guard yourself from any issues that may arise. Your buyer wont care, or may even be pleased.
Click to expand...
Click to collapse
There's no full sense RUU for Rogers - or at least that I've found. I flashed a stock Rogers nandroid, and I can get OTA updates. Turns out recovery is borked - I flashed a recovery file for a HBOOT 1.54. Would that be the issue?
(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.631.9
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: *redacted
(bootloader) imei: *redacted
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0712000
(bootloader) cidnum: ROGER001
(bootloader) battery-status: good
(bootloader) battery-voltage: 3911mV
(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
Since you are s-off make a firmware.zip with splash1.nb0 from an RUU and flash it in fastboot to restore the stock splash screen. Set the mainver in the andriod-info.txt to the same version that's currently on the phone.
I followed the guide to return to stock - flipped the CID, flashed an RUU file that got me all the way back to here:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.44.0000
(bootloader) version-baseband: 4A.17.3250.20
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.26.502.15
(bootloader) version-misc: PVT SHIP S-OFF
I flashed TWRP, restored a nandroid backup and then checked to see the OS was ok - everything seemed cool. I booted back into bootloader and flashed the stock recovery, erased cache and booted back into the OS. I did a factory data reset, booted back into bootloader, booted to cwm and used Guru to lock & untamper. When I rebooted and tried the OTA update, the update failed. Now I can get to stock recovery but when I boot I get a cyan screen, a magenta screen then frozen at an HTC boot screen where the green is wrong and "beats" is blue. Any suggestions from here?
Stay again with ruu. And don't change anything.
sent from my mobile device
So RUU on Cingular, run all the updates via wifi then change CID back for my carrier and flash recovery?
Sent from my SM-N900W8 using Tapatalk
Is there a reason for changing your CID back/flash recovery?
In my opinion, do NOT S-ON, or lock your bootloader, and flash US Dev RUU http://www.androidruu.com/getdownlo...3_SENSE50_MR_BrightstarUS_WWE_3.22.1540.1.exe
You can leave the CID as 11111111 or change to BS_US001
Bringing it back to stock to send to HTC RMA
Sent from my SM-N900W8 using Tapatalk
Crap.. you will then want to follow post #2 in my guide for Canadian restock. There are some reports of Tampered sign showing up even on 1.44 HBOOT, however you would hope it doesn't.
Good luck.
SaHiLzZ said:
Crap.. you will then want to follow post #2 in my guide for Canadian restock. There are some reports of Tampered sign showing up even on 1.44 HBOOT, however you would hope it doesn't.
Good luck.
Click to expand...
Click to collapse
I re-unlocked the bootloader from the HTC Dev site. Re-flashed TWRP, restored Nandroid backup for 1.44HBOOT. Validated all looked ok, booted back to recovery and un-rooted. Booted back to bootloader, flashed stock recovery (+ erase cache) then rebooted back to bootloader and ran a factory reset. THEN when I jumped back into the OS and ran the OTA. Back to the cyan then magenta screen and the freeze. GRRR. I guess I need to start from scratch and use RUU to get to the right HBOOT version that will work!
Why are you running OTA? Get it right on 1.44hboot and send it in for warranty
sent from my mobile device
SaHiLzZ said:
Why are you running OTA? Get it right on 1.44hboot and send it in for warranty
sent from my mobile device
Click to expand...
Click to collapse
Good point. I was assuming they'd expect latest version, but I guess if I'm on any supported version they shouldn't care. Right now I'm toying with different recoveries - the OTA update fails to update anything, so I thought I'd restore the Nandroid backup and flash a different recovery version and see if OTA works. If that doesn't work I'll just restore the nandroid backup, flash stock recovery for 1.44 and factory reset and it's good to go.
Thanks!
cdnchris said:
Good point. I was assuming they'd expect latest version, but I guess if I'm on any supported version they shouldn't care. Right now I'm toying with different recoveries - the OTA update fails to update anything, so I thought I'd restore the Nandroid backup and flash a different recovery version and see if OTA works. If that doesn't work I'll just restore the nandroid backup, flash stock recovery for 1.44 and factory reset and it's good to go.
Thanks!
Click to expand...
Click to collapse
I flashed the 1.55 stock recovery on the 1.44 HBOOT and the update actually worked this time. I'm up to latest stock for my carrier, still S-OFF and unlocked bootloader.
I'm told futuretel denies warranty on s-off. Unless you are sending somewhere else. On 1.55 hboot, if you s-on, the tampered sign will come back after a few restarts. If it doesn't you are good to go.
sent from my mobile device

stuck in boot mode

hi guys, I am stuck in boot mode after removing cyanogen mod, I have tried installing the RUU.exe but it will not complete - I think the reason for this is that S-ON. I can't seem to find a solution to achieve S-off anywhere without having to be into the phones OS.
I have tried pushing the rom to my phone but I just keep getting 'no device found'
The usb recognises the phone but the adb commands do not work at all
any further info suggested would be massively appreciated.
edit:
got adb commands working by following this guide
(not allowed to post links yet)
progress so far:
I have managed to sideload a relevant ROM but it has now been saying 'installing update' for quite a while and I am not sure whether to touch it
on another note, the image verification thing on this forum is very, very annoying.
ok so I sideloaded a ROM and it aborted the installation, totally at a loss now
grantymc said:
ok so I sideloaded a ROM and it aborted the installation, totally at a loss now
Click to expand...
Click to collapse
Boot your phone in bootloader mode and type fastboot getvar all. copy/paste the output here except IMEI and SERIALNO. Also, I need to know what recovery you are using and its version and what custom rom and its version you are trying to flash.
alray said:
Boot your phone in bootloader mode and type fastboot getvar all. copy/paste the output here except IMEI and SERIALNO. Also, I need to know what recovery you are using and its version and what custom rom and its version you are trying to flash.
Click to expand...
Click to collapse
I am using clockwork recovery, I was trying to flash a stock RUU zip - I could not find one to match my exact baseband version so I tried
"RUU Zip M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4.zip" but just got the message 'installation aborted' after sideloading
forgive me I can't paste links yet
I also tried the latest version of CM as this is what I was trying to revert back from this installed but just said 'installing' for nearly an hour then after I rebooted it left with a constant CM loading screen
I have a feeling I need S-OFF but can't seem to achieve through any of the methods described
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.55.0000
(bootloader) version-baseband: 4A.21.3263.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.63.61.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA385W914634
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: ORANG001
(bootloader) battery-status: good
(bootloader) battery-voltage: 4325mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-b0a25cb2
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
grantymc said:
I am using clockwork recovery, I was trying to flash a stock RUU zip - I could not find one to match my exact baseband version so I tried
"RUU Zip M7_UL_JB_50_HTC_Europe_1.20.401.1_Radio_4A.13.3227.06_10.27.1127.01_release_308001_signed_2_4.zip" but just got the message 'installation aborted' after sideloading
Click to expand...
Click to collapse
Ruu.zip are not installed with a custom recovery/sideloaded!! It must be flashed via fastboot ruu mode. Anyway this ruu is not for your phone, its a .401 base and you need a .61 base ruu of same version or higher than 3.63.61.1 but afaik there is no ruu for your phone... BTW the 1.20.401.1 ruu is a pre-release version without OTA updates so it a bad idea to use it.
grantymc said:
forgive me I can't paste links yet
I also tried the latest version of CM as this is what I was trying to revert back from this installed but just said 'installing' for nearly an hour then after I rebooted it left with a constant CM loading screen
Click to expand...
Click to collapse
Either because of a bad rom/download or because your recovery version is outdated. Flash twrp 2.6.3.3 or 2.6.3.4. Also clear cache every time your flash something and md5 check your roms/recovery before you flash them.
grantymc said:
I have a feeling I need S-OFF but can't seem to achieve through any of the methods described
Click to expand...
Click to collapse
S-OFF is not require to flash a custom rom like CM only if you want to convert your phone using a ruu not intended for your version.

[Q] RUU stuck at "checking headers"

I have an HTC One M7 (European unlocked version). I'm trying to restore it to the stock software, but I don't care about the "locked/re-locked" status, so I didn't bother getting s-off. Right now I have the stock odexed ROM that I got from here and TWRP 2.6.3.3.
This is the RUU file I'm trying to use. (The "stock ROM" I have now is version 4.19.401.8 instead, and has support for OTA updates, but it says my phone is up to date even if it's not.)
I know that to get a RUU working on an HTC phone, you have to re-lock the bootloader. So I did. This is my fastboot info now:
Code:
C:\Windows\system32>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: CENSORED
(bootloader) imei: CENSORED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4302mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.059s
At the top the screen says "tampered" and "relocked."
So, still being on fastboot and aware that all the data in the phone would be gone, I ran the RUU file on my windows pc. It started up and I went through the setup. It rebooted my phone to a black screen with a gray htc logo and started the process.
However, I've noticed it's been at 5% and saying "checking headers" for a bit too long now. I waited an hour and it was still stuck. I held down the power button on my phone until it rebooted. It still booted up and worked fine, nothing was deleted. Tried again, same thing. I'm sure I'm using the right RUU file, and the MD5 checks fine. I remember doing this on an htc one v, I was in the same exact situation and everything went through. Why doesn't it work with my m7?
Now my bootloader is locked and if I re-unlock it, it will delete all my stuff. I can still use the phone fine, but I want stock rom, recovery and everything, so I can also get the official sense 6 update. I could do s-off if I really have to, if that's what it takes to get the RUU working. My phone's still rooted, but I don't think the firewater or whatever utility to get s-off works with a locked bootloader. What I'd like to do is just get the RUU working, but it's not. Have I screwed up? Do I re-unlock the bootloader and have to resort to custom roms on this phone? Please help. If I didn't provide enough info, tell me.
XDA Dev said:
I have an HTC One M7 (European unlocked version). I'm trying to restore it to the stock software, but I don't care about the "locked/re-locked" status, so I didn't bother getting s-off. Right now I have the stock odexed ROM that I got from here and TWRP 2.6.3.3.
This is the RUU file I'm trying to use. (The "stock ROM" I have now is version 4.19.401.8 instead, and has support for OTA updates, but it says my phone is up to date even if it's not.)
I know that to get a RUU working on an HTC phone, you have to re-lock the bootloader. So I did. This is my fastboot info now:
Code:
C:\Windows\system32>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.54.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: CENSORED
(bootloader) imei: CENSORED
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4302mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-d959c75800
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.059s
At the top the screen says "tampered" and "relocked."
So, still being on fastboot and aware that all the data in the phone would be gone, I ran the RUU file on my windows pc. It started up and I went through the setup. It rebooted my phone to a black screen with a gray htc logo and started the process.
However, I've noticed it's been at 5% and saying "checking headers" for a bit too long now. I waited an hour and it was still stuck. I held down the power button on my phone until it rebooted. It still booted up and worked fine, nothing was deleted. Tried again, same thing. I'm sure I'm using the right RUU file, and the MD5 checks fine. I remember doing this on an htc one v, I was in the same exact situation and everything went through. Why doesn't it work with my m7?
Now my bootloader is locked and if I re-unlock it, it will delete all my stuff. I can still use the phone fine, but I want stock rom, recovery and everything, so I can also get the official sense 6 update. I could do s-off if I really have to, if that's what it takes to get the RUU working. My phone's still rooted, but I don't think the firewater or whatever utility to get s-off works with a locked bootloader. What I'd like to do is just get the RUU working, but it's not. Have I screwed up? Do I re-unlock the bootloader and have to resort to custom roms on this phone? Please help. If I didn't provide enough info, tell me.
Click to expand...
Click to collapse
Great information! Your post is a model of HOW a question should be posted!
Anyway, if 4.x.401.x RUU is NOT working, try another computer, if it is still not working, then yes, S-OFF, flash 1.44 HBOOT, and run the http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/ RUU. This will take you back a few months ago, but you will be able to OTA all the way upto Sense 6!
SaHiLzZ said:
Great information! Your post is a model of HOW a question should be posted!
Anyway, if 4.x.401.x RUU is NOT working, try another computer, if it is still not working, then yes, S-OFF, flash 1.44 HBOOT, and run the http://www.htc1guru.com/dld/ruu-zip...1-27_10-31-1131-05_release_310878_signed-zip/ RUU. This will take you back a few months ago, but you will be able to OTA all the way upto Sense 6!
Click to expand...
Click to collapse
Haha, thanks, I guess nearly 3 years of lurking on these forums taught me something about posting.
I was using a Windows Vista SP2 PC to try this. I've just tried it on my Mac running Windows 7 SP1 with bootcamp, the RUU file (which still checks out with the correct MD5 hash) starts the installshield wizard normally, but as soon as I accept the terms and conditions, the program closes and nothing opens again. I checked on task manager, the process closes shortly after accepting the terms. I tried restarting and looking up for a solution but I couldn't find anything that worked.
Is Vista really the only reason it's stuck at checking headers? I know Vista is rather despised by a lot of people, but by 2014 it did get better. I'd rather use that machine because on my Mac running Windows 7 the RUU could not start up because I've made the Windows partition too small. (It has around 3gb free now whereas the vista machine has more than 150).
Sorry for the double post, but it's probably my last one on this thread.
Even if my boot loader was re-locked, I tried running the firewater program to get s-off, and it worked. (As a bonus it re-unlocked my boot loader without wiping the phone, but I re-locked it again to get the ruu working).
Then I tried downgrading to hboot 1.44, but for some reason it kept giving an error like "failed: remote 42 custom id check fail." I decided to try the sense 5.0 ruu anyway (on my vista PC), and it worked! The phone now says "relocked" but tampered is gone of course, and I have hboot 1.44, android 4.1 and htc sense 5.0, but still s-off.
The first update popped up (and it's not android 4.4 with sense 6, it's something in between) so I'm going to update until no more updates are available. Then I'm going to re-unlock the boot loader because I want to root my phone, and then set up all my stuff. When a new update comes out, I can just flash the original recovery, apply the update and then re-flash twrp to root again.
Thank you for the suggestion to install the older ruu. I'm still stumped on why the newer one didn't work (it would have caused much less hassle), but whatever. At least my phone is much cleaner now. It feels good to have it like this again, I'm not against custom roms but I like the stock software too.
I'm using my iPhone to write this, but trust me, my htc is in full working order now.
Until next problem I can't solve myself
Sent from my iPhone using Tapatalk
Thanks for updating back. Don't S-ON.
SaHiLzZ said:
Thanks for updating back. Don't S-ON.
Click to expand...
Click to collapse
Yeah, I'm not going to. I've updated to android 4.3 now and I'm still downloading updates--it updated hboot to 1.55 but I still have s-off, so I believe it stays s-off if I don't run the command to (I guess irreversibly) go back to s-on, which I don't even know. (I didn't do s-off before because I didn't care about the extra privileges and was afraid of bricking my phone, but now that I have it I don't mind so I'm keeping it).
Sent from my iPhone using Tapatalk

[Q] HTC One Vodafone System Update 6.12.161.5

Last night I got a notification for a System Update to version 6.12.161.5.
Has anyone tried this yet? And any problems found?
With the last two updates over the last 3-4 months I have had major problems:
1. When VodaFone forced the Rich Communication Suite / Service upon us; abysmal battery performance and terrible instability problem with phone frequently crashing on incoming calls and texts - which I 'solved' by Disabling RCS.
2. When VodaFone pushed the next update that greyed out the box to Disable RCS (they appeared to fix the instability and battery drain problem, but now I don't even have the option to disable RCS).
After lots of self-help and web searching I now have a stable phone with decent battery life again, and given those past painful experiences I am somewhat reluctant to blindly update.
Has anyone tried this Update yet, and can you comment after a few days of usage, particuarly on stability and battery usage?
Thanks
David
I had the 6.12.161.5 update a few days ago. Ive just had the 6.12.161.8 download now. Whats the difference?
Pilch2k said:
I had the 6.12.161.5 update a few days ago. Ive just had the 6.12.161.8 download now. Whats the difference?
Click to expand...
Click to collapse
Yeah, I also just had the 6.12.161.8 update. I've still not installed the previous one. I'm planning to wait this one out, after problems in the past. Will wait until some other folks try it first
daveingram said:
Yeah, I also just had the 6.12.161.8 update. I've still not installed the previous one. I'm planning to wait this one out, after problems in the past. Will wait until some other folks try it first
Click to expand...
Click to collapse
To be honest i've not noticed any issues yet, or any changes!
needed Ota file 6.12.161.8
Hi!
Would someone be so nice to post a link to his copy of this OTA? I need it desperately to revive my bricked One m7...
I've tryed anything but to flash this one on my s-on device..
Please help to save an Htc's life!! :cyclops:
Seymour2002 said:
Hi!
Would someone be so nice to post a link to his copy of this OTA? I need it desperately to revive my bricked One m7...
I've tryed anything but to flash this one on my s-on device..
Please help to save an Htc's life!! :cyclops:
Click to expand...
Click to collapse
you can not flash OTA to unbrick a phone. You need to flash the complete rom. And btw, OTA can not be flashed manually with S-ON, it must be initiated from the OS .
Flash firmware from OTA...
alray said:
you can not flash OTA to unbrick a phone. You need to flash the complete rom. And btw, OTA can not be flashed manually with S-ON, it must be initiated from the OS .
Click to expand...
Click to collapse
Well reading this sound like different from what you say... http://forum.xda-developers.com/showthread.php?t=2182823; but probably I'm wrong...
The actual thing is there's no Ruu nor OTA nor Zip for CID VODAP405 around... Or does?
Seymour2002 said:
Well reading this sound like different from what you say... http://forum.xda-developers.com/showthread.php?t=2182823;
Click to expand...
Click to collapse
Dont know what you are referring to.
The actual thing is there's no Ruu nor OTA nor Zip for CID VODAP405 around... Or does?
Click to expand...
Click to collapse
Unfortunately, there is not much files for that CID.
I don't understand what you want to attempt with an OTA file. Firmware included in OTA are not complete, it only contain files to be updated in an incremental way. If you manually flash a firmware from an OTA updates and you do it over the wrong version (currently installed on your phone) this could end with a bricked phone (hardbrick)
Flashing the entire OTA zip file will not help either. OTA files are patches that must be installed over a working rom and proper rom version. It also must be flashed using the "software update" option within the OS (unless the phone is s-off)
what you should do imo, is to start over fresh, flash twrp recovery 2.6.3.3 and flash a "close to stock" rom
Flash firmware from OTA...
First I want to thank for your help...
Then just to explain things, here's my awkward situation:
- I have a working rom but with battery that always stays at 1% no matter what, I get an ota update but I can't update since it says there's not enought battery...
the ota It gets is a 4.19.1540.9 which doesn't match with the follwing:
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.12.161.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH37WW904203
(bootloader) imei: 357864057367987
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP405
(bootloader) battery-status: good
(bootloader) battery-voltage: 4261mV
(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
To finish the cake: recovery doesn't work and bootloader is relocked and doesn't unlock anymore....
Any suggestion?
Seymour2002 said:
First I want to thank for your help...
Then just to explain things, here's my awkward situation:
- I have a working rom but with battery that always stays at 1% no matter what, I get an ota update but I can't update since it says there's not enought battery...
the ota It gets is a 4.19.1540.9 which doesn't match with the follwing:
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.12.161.8
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: ***************
(bootloader) imei: *********************
(bootloader) meid: 00000000000000
(bootloader) product: m7_ul
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PN0710000
(bootloader) cidnum: VODAP405
(bootloader) battery-status: good
(bootloader) battery-voltage: 4261mV
(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
To finish the cake: recovery doesn't work and bootloader is relocked and doesn't unlock anymore....
Any suggestion?
Click to expand...
Click to collapse
how did you manage s-on + locked bootloader + no recovery ?
was this phone converted to DE or GPE at one time ?
Flash firmware from OTA...
I actually didn't do anything extraordinary except maybe to have flashed a rom with a different cid which got an update and brought me almost a this situation.
Then I wanted to bring the device to stock, so I flashed the original recovery and relocked the booloader. Nothing else.
I don't know why at the moment there's no way to enter recovery and if I try to unlock the bootloader again I reach the screen where I must agree on the device's screen to unlock, but then It just stuck on htc logo whilw trying to enter recovery..
Seymour2002 said:
I actually didn't do anything extraordinary except maybe to have flashed a rom with a different cid which got an update and brought me almost a this situation.
Then I wanted to bring the device to stock, so I flashed the original recovery and relocked the booloader. Nothing else.
I don't know why at the moment there's no way to enter recovery and if I try to unlock the bootloader again I reach the screen where I must agree on the device's screen to unlock, but then It just stuck on htc logo whilw trying to enter recovery..
Click to expand...
Click to collapse
are you sure your not just going to stock recovery ?
have you done the fastboot erase cache ?
followed by fastboot reboot-bootloader ?
what was the last custom recovery you had on their and what happened to make it gone ? RUU ?
Flash firmware from OTA...
clsA said:
are you sure your not just going to stock recovery ?
have you done the fastboot erase cache ? Yes, several times...
followed by fastboot reboot-bootloader ? Yes....
what was the last custom recovery you had on their and what happened to make it gone ? RUU ?
Click to expand...
Click to collapse
I was usimg twrp recovery, then I'm pretty sure I flashed the stock recovery, I don't know what happened to make it disappear, It just happened! I haven't been able to use any Ruu well since I never found the right one matching my CID., so I always got an error..
Seymour2002 said:
I was usimg twrp recovery, then I'm pretty sure I flashed the stock recovery, I don't know what happened to make it disappear, It just happened! I haven't been able to use any Ruu well since I never found the right one matching my CID., so I always got an error..
Click to expand...
Click to collapse
if you flashed the stock recovery correctly you go to the bootloader choose recovery hit power button
the screen will go black push volume up and tap power again to see the recovery menu, choose format data . factory reset
after it finishes reboot the phone and try again to unlock the bootloader
Flash firmware from OTA...
clsA said:
if you flashed the stock recovery correctly you go to the bootloader choose recovery hit power button
the screen will go black push volume up and tap power again to see the recovery menu, choose format data . factory reset
after it finishes reboot the phone and try again to unlock the bootloader
Click to expand...
Click to collapse
Once I select recovery from the bootloader menu and I press power button the phone reboots the bootloader...
SOLVED! Unbrikked THC ONE M/!!!!!
So thanks to MIke 1986 and his great page link:http://forum.xda-developers.com/showthread.php?t=2182823, I managed to recover my very very hrad brikked phone!!!!!!!!!
Here's what I did:
1- checked all phone's details with fastboot getavar all---> took note of CID - MID - versione OS installed etc.
2- took the OTA update corresponding to the firmware installed and extracted the firmware.zip
3- flashed the firmware.zip via fastboot (fastboot oem rebootRUU - fastboot flash zip firmware.zip [thanks to mike 1986]) ; #Alray: since a phone is S-On there's no risk to flash a wrong firmware and as I did anyone can do it via normal fastboot command with no issue!:angel:
4-In this way I recovered stock recovery and the possibility to unlock the bootloader again!!
5-moved a CWM nand backup to phone sd using sideload push command ( sideload push nandbackupname.zip /sd/cwm/backup/dateof backup - just make a nand backup yourself first to get exact loaction)
6-recovered from nandbackup using proper tool of cwm.
7-enjoyED MY revived device!!!!!! NOT THANKS TO ALRAY....http://cdn4.xda-developers.com/images/icons/icon8.gif
Seymour2002 said:
So thanks to MIke 1986 and his great page link:http://forum.xda-developers.com/showthread.php?t=2182823, I managed to recover my very very hrad brikked phone!!!!!!!!!
Here's what I did:
1- checked all phone's details with fastboot getavar all---> took note of CID - MID - versione OS installed etc.
2- took the OTA update corresponding to the firmware installed and extracted the firmware.zip
3- flashed the firmware.zip via fastboot (fastboot oem rebootRUU - fastboot flash zip firmware.zip [thanks to mike 1986]) ; #Alray: since a phone is S-On there's no risk to flash a wrong firmware and as I did anyone can do it via normal fastboot command with no issue!:angel:
4-In this way I recovered stock recovery and the possibility to unlock the bootloader again!!
5-moved a CWM nand backup to phone sd using sideload push command ( sideload push nandbackupname.zip /sd/cwm/backup/dateof backup - just make a nand backup yourself first to get exact loaction)
6-recovered from nandbackup using proper tool of cwm.
7-enjoyED MY revived device!!!!!! NOT THANKS TO ALRAY....http://cdn4.xda-developers.com/images/icons/icon8.gif
Click to expand...
Click to collapse
Glad you got your phone revived :good:
since a phone is S-On there's no risk to flash a wrong firmware
Click to expand...
Click to collapse
The risk is there, if you flash a firmware patch (ota firmware) over the wrong version (i.e 5.xx.xxx.x over 3.xx.xxx.x), this could brick. Happened many times that's why its mentioned in some threads. There is no risk flashing the same version like you did

Flashing different Cid RUU

Hi
Apologies in advance if this is an obvious question; I have looked through the forum but cant find a concise answer to my queries. I am coming from a HOX and my friend gave me his broken screened UK O2 branded LTE M7 as such not yet familiar with the M7. I have replaced the broken screen and fitted a new battery which was a great deal more awkward than working on the HOX!
The CId is 02_001 running HBOOT 1.61 and S-ON, I have unlocked the bootloader via HTC Dev however this is where I become unsure as to what avenues I can explore for flashing.
I'm assuming as I've now unlocked the bootloader I can flash a TWRP recovery but as I'm S-ON I can only flash unencrypted roms and as such cannot flash say the HTC Europe unbranded RUU? I want to try and stay on a stock type unbranded Sense ROM if possible rather than flashing a custom or CM based ROM until I am more familiar with the M7.
There is a plethora of info and hence I'm finding it difficult to get to grips with what ROMs would be suitable.
alangordon73 said:
Hi
Apologies in advance if this is an obvious question; I have looked through the forum but cant find a concise answer to my queries. I am coming from a HOX and my friend gave me his broken screened UK O2 branded LTE M7 as such not yet familiar with the M7. I have replaced the broken screen and fitted a new battery which was a great deal more awkward than working on the HOX!
The CId is 02_001 running HBOOT 1.61 and S-ON, I have unlocked the bootloader via HTC Dev however this is where I become unsure as to what avenues I can explore for flashing.
I'm assuming as I've now unlocked the bootloader I can flash a TWRP recovery but as I'm S-ON I can only flash unencrypted roms and as such cannot flash say the HTC Europe unbranded RUU? I want to try and stay on a stock type unbranded Sense ROM if possible rather than flashing a custom or CM based ROM until I am more familiar with the M7.
There is a plethora of info and hence I'm finding it difficult to get to grips with what ROMs would be suitable.
Click to expand...
Click to collapse
With a S-ON phone you can only flash Signed RUU that are for your phone CID, MID and version-main. You also can't flash older RUU than your version-main.
With S-OFF, you can flash Signed/Un-signed RUU of your choice (you'll have to change your CID and maybe your MID)
Flashing a stock rom (not talking about a RUU here, but a stockish unbranded custom rom) doesn't requires S-OFF, simply flash using custom recovery. ARHD 93 is a good starting point imo.
Many thanks for the reply - I am aware that the question is slightly noobish and as such I am appreciative. I'll install the suggested ROM and work from there.
Again many thanks
Unable to entery custom recovery
okay this is less than ideal... flashed every type of custom recovery to no avail but unable to boot into recovery.
Tried fastboot erase cache before and after flashing recoveries.
When selecting recovery 'entering recovery' appears at the top of the screen, after a few seconds the screen goes black for a second or so then back to the 'entering recovery' which never actually happens - Its like it hangs on loading the recovery.
Result of fastboot allvars query:
(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.18.206.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA3C6W904988
(bootloader) imei: xxxxxxxxxxxxxxxxx
(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: 4047mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-868a9c98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Does anyone have any ideas?
This phone/brick is vexing to say the least!
alangordon73 said:
okay this is less than ideal... flashed every type of custom recovery to no avail but unable to boot into recovery.
Tried fastboot erase cache before and after flashing recoveries.
When selecting recovery 'entering recovery' appears at the top of the screen, after a few seconds the screen goes black for a second or so then back to the 'entering recovery' which never actually happens - Its like it hangs on loading the recovery.
Result of fastboot allvars query:
(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.18.206.51
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: FA3C6W904988
(bootloader) imei: xxxxxxxxxxxxxxxxx
(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: 4047mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-868a9c98
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Does anyone have any ideas?
This phone/brick is vexing to say the least!
Click to expand...
Click to collapse
Flash mdmower's twrp recovery
http://android.cmphys.com/twrp-m7/
Right it seems I've managed to make a mess of this - I've foolishly relocked the booloader on a custom recovery and now I can't get it unlocked again - It reboots to recovery and just hangs and wont unlock the bootloader.
I've tried using the rom.zip from the RUU and flashing it in fastboot to which it reports it cannot allocate the space in bytes.
I've tried running the RUU which fails at checking headers on step 1/5
RUU I'm trying to use 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
Is the recovery partition perhaps corrupt as I'm getting absolutely nowhere with this paperweight?
I'm now at a loss and most peeved!
alangordon73 said:
Right it seems I've managed to make a mess of this - I've foolishly relocked the booloader on a custom recovery and now I can't get it unlocked again - It reboots to recovery and just hangs and wont unlock the bootloader.
I've tried using the rom.zip from the RUU and flashing it in fastboot to which it reports it cannot allocate the space in bytes.
I've tried running the RUU which fails at checking headers on step 1/5
RUU I'm trying to use 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
Is the recovery partition perhaps corrupt as I'm getting absolutely nowhere with this paperweight?
I'm now at a loss and most peeved!
Click to expand...
Click to collapse
You can't flash a RUU version that is older than your actual version-main when the phone is S-ON. To unlock a bootloader that was relocked with a custom recovery installed, you either need to reflash a signed(official) firmware or a ruu since this is the only thing that the phone will accept in this state (locked and s-on).
Unfortunately i can't find any 7.18.206.51 firmware so you'll have to reflash the whole phone using the 7.18.206.51 RUU which will reset everything back to stock and wipe your files.
https://www.androidfilehost.com/?fid=24352994023702662
Code:
fastboot oem rebootRUU
htc_fastboot flash zip PN07IMG_M7_UL_L50_SENSE60_MR_O2_UK_7.18.206.51_Radio_4T.35.3218.16_10.33Q.1718.01L_release_459056_signed.zip
fastboot reboot-bootloader
than you'll be able to unlock again.
Don't forget to use htc_fastboot.exe for the flash zip command (not the regular fastboot.exe). A quick search on androidfilehost.com for "htc_fastboot" and you'll be able to download it if you don't have it already.
Outstanding... Flashed back and unlocked the boot loader. Spent enough time and frustration this week so early night and will try flash a recovery and ArHD tomorrow.
Can't thank you enough
Grrrr... Flashed the recovery suggested above and the phone just does not want to go into recovery.
I've tried:
Powering down from Android and then going into Bootloader just stops on Entering Recovery.
Power down, entering bootloader then reseting the phone - again stops on Enterng Recovery.
Power down from Android, power back up, master reset - again just stops on entering recovery.
screams...
alangordon73 said:
Grrrr... Flashed the recovery suggested above and the phone just does not want to go into recovery.
I've tried:
Powering down from Android and then going into Bootloader just stops on Entering Recovery.
Power down, entering bootloader then reseting the phone - again stops on Enterng Recovery.
Power down from Android, power back up, master reset - again just stops on entering recovery.
screams...
Click to expand...
Click to collapse
Did you tried the old TWRP 2.6.3.3 version? Ive seen a lot of pple only being able to use this version when newer ones will cause the exact problem you are experiencing. Might worth a try.
Solved! TWRP 2.6.3.3 works.
alray said:
With a S-ON phone you can only flash Signed RUU that are for your phone CID, MID and version-main. You also can't flash older RUU than your version-main.
With S-OFF, you can flash Signed/Un-signed RUU of your choice (you'll have to change your CID and maybe your MID)
Flashing a stock rom (not talking about a RUU here, but a stockish unbranded custom rom) doesn't requires S-OFF, simply flash using custom recovery. ARHD 93 is a good starting point imo.
Click to expand...
Click to collapse
Then I can flash any Ruu I want if I change Cid and Mid to match Ruu with S-off? Even if it's from 4.3 to kit Kat or Lollipop?
Thanks and sorry for hijacking the thread.
Enviado desde mi Nexus 5 mediante Tapatalk
JabboMaster said:
Then I can flash any Ruu I want if I change Cid and Mid to match Ruu with S-off? Even if it's from 4.3 to kit Kat or Lollipop?
Thanks and sorry for hijacking the thread.
Enviado desde mi Nexus 5 mediante Tapatalk
Click to expand...
Click to collapse
not exactly,it depend what phone variant you have. If its a M7_UL or M7_U then you can flash any M7_UL or M7_U RUU youd like by changing the CID and MID. If you want to flash a lollipop RUU you need to have at least hboot 1.57 with a 6.xx.xxx.x firmware already installed on the phone. Firmware can easily be updated if needed when s-off.
alray said:
not exactly,it depend what phone variant you have. If its a M7_UL or M7_U then you can flash any M7_UL or M7_U RUU youd like by changing the CID and MID. If you want to flash a lollipop RUU you need to have at least hboot 1.57 with a 6.xx.xxx.x firmware already installed on the phone. Firmware can easily be updated if needed when s-off.
Click to expand...
Click to collapse
Ok, thanks.
Gonna try flashing first a Kitkat Ruu and then updating via Ota to Lollipop.
Enviado desde mi Nexus 5 mediante Tapatalk

Categories

Resources