Flashing different Cid RUU - One (M7) Q&A, Help & Troubleshooting

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

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] Restoring 100% to stock, not working as it should...

Hi guys,
First of all, I did read all the topics conserning to RUU, S-On/S-Off, rumrunner, moonshine, firewater, revone, and so on but I can't seem to figure out how to properly do this.
Currently the HTC is running MIUI v5 4.5.16 JB4.2. But for warranty it has to go back to the store and I want to restore it to completly stock ROM etc. without any evidence I had a custom ROM running.
What I did was, follow the steps to unlock the bootloader, flash a custom recover (TWRP v2.6.3.0) and finally root it after MIUI was flashed.
The info you guys prolly need are as followed:
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.26.3263.05
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.161.11
(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: VODAP102
(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-09ff2ded
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.038s
Click to expand...
Click to collapse
I tried to get S-Off but I keep getting strange errors on all of the given methods. This should work somehow I guess but how? Can somebody give me some kind of "roadmap" how to do it properly?
Currently fastboot shows:
*** TAMPERED ***
*** UNLOCKED ***
M7_UL PVT SHIP S-ON RH
HBOOT-1.56.0000
RADIO-4A.26.3263.05
OpenDSP-v32.120.274.0909
OS-4.19.161.11
eMMC-boot 2048MB
Mar 5 2014,15:58:33.0
Click to expand...
Click to collapse
At the moment I'm downloading "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". But I already noticed that if I turn S-On (fastboot oem lock) then the phone is stuck in fast boot mode...
Thanks!
I think S-off is danger may u brick ur phone, it's better to leave it
ahmed blue said:
I think S-off is danger may u brick ur phone, it's better to leave it
Click to expand...
Click to collapse
Yeah but what if I need it to go back to stock ROM?
Now it's running stock ROM but I still get "TAMPERED" and "UNLOCKED" in the bootloader. I once went into the stock recovery, and once rebooted it reset itself and everything was back factory install -again- ...?
This is the fastboot output right now after flashing Guru Reset M7 2.24.161.1.zip :
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.56.0000
(bootloader) version-baseband: 4A.17.3250.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.19.161.11
(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: VODAP102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4185mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-09ff2ded
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
Click to expand...
Click to collapse
The OTA update to 4.3 even fails once it reboots itself for installation. Something wrong or normal?
EDIT:
I've done "fastboot oem lock" and now it's showing (as expected) "RELOCKED".
BETA911 said:
Yeah but what if I need it to go back to stock ROM?
Now it's running stock ROM but I still get "TAMPERED" and "UNLOCKED" in the bootloader. I once went into the stock recovery, and once rebooted it reset itself and everything was back factory install -again- ...?
This is the fastboot output right now after flashing Guru Reset M7 2.24.161.1.zip :
The OTA update to 4.3 even fails once it reboots itself for installation. Something wrong or normal?
EDIT:
I've done "fastboot oem lock" and now it's showing (as expected) "RELOCKED".
Click to expand...
Click to collapse
Yup it will do, the only way to get rid of those flags tampered and unlocked / relocked is to go s-off, which strange messages are you getting whilst trying to s-off ?
I have a backup of the Vodafone Rom which you can restore through twrp, I'll send a link when I get home in a couple of hours, but it won't get rid of those flags, 401.RUU is the wrong RUU, you need 161.
---------- Post added at 05:43 PM ---------- Previous post was at 05:34 PM ----------
Ps there is no danger going s-off, as long as your flashing the correct software for your phone, the only danger is when you don't know what your doing and try to flash something wrong, it won't warn you, won't error and won't fail to flash, but at reboot it also won't come back on again.
Seanie280672 said:
Yup it will do, the only way to get rid of those flags tampered and unlocked / relocked is to go s-off, which strange messages are you getting whilst trying to s-off ?
I have a backup of the Vodafone Rom which you can restore through twrp, I'll send a link when I get home in a couple of hours, but it won't get rid of those flags, 401.RUU is the wrong RUU, you need 161.
---------- Post added at 05:43 PM ---------- Previous post was at 05:34 PM ----------
Ps there is no danger going s-off, as long as your flashing the correct software for your phone, the only danger is when you don't know what your doing and try to flash something wrong, it won't warn you, won't error and won't fail to flash, but at reboot it also won't come back on again.
Click to expand...
Click to collapse
Well... It said it had a OTA update (like before) to 4.3 and I downloaded it. Reboot, installed, reboot --> bootloop. Now it's "HTC - quietly brilliant", black screen for couple of seconds and reboot to start from HTC logo again...
It's really beginning to piss me of.
But anyway, thanks for the help! A TWRP backup of 161 would be nice, then I'll install that one. The servers at htc1guru are giving me headache, speed is only between 50 and 250 kb/sec! I tried to download more then once but they keep failing on me when they reach bigger sizes and at this speed it's really really annoying to start over again...
Does "M7 CWM Nandroid Backup CID VODAP102 1.29.161.7" work for me? I guess not because it's 1.29 and I already have a higher version so it will give me the touchscreen issues?
To be honest, if this phone finally makes it to the store for repair I hope they can't repair it and let me choose an other phone. I had multiple Android phones the past years (with sometimes more then 2-3 different roms per week) and never had any of these long stretching problems!
The problem your having with the ota sounds like whilst you were installing the guru reset file, you must select to wipe data and also install stock recovery, it will fail without stock recovery.
Well, I did select to install the stock recovery and stock radio in the aroma installer. So I'm out of clues why it's giving me so much problems...
EDIT:
I unlocked the bootloader again and flashed TWRP. I'll try with your Vodafone image once you have time to share it with me. Already big thanks for the help!
here's the backup, you will need to extract the zip file and put the folder named backup into SDCARD/TWRP/BACKUPS/"your device serial number/
https://drive.google.com/uc?export=download&confirm=5940&id=0B_nEcSZr5peRZnpMSHRPRjlzX2c
This will put you on Vodafone 4.4.2 with sense 5.5, however you cant send your phone back until you have got rid of those 2 flags in the bootloader, only way to do that is s-off.
Ignore the folder called recovery, its just TWRP recovery to flash.
After installing, download the stock recovery from the link below and flash it to get OTAs
http://d-h.st/Cyq
Hit the thanks button please.
Just finished installing it! It works so far, although it came up with a new 5.16.161.2 update right now (already has been downloaded...). What should I do?
Currently it's still in TAMPERED and UNLOCKED state with TWRP installed.
BETA911 said:
Just finished installing it! It works so far, although it came up with a new 5.16.161.2 update right now (already has been downloaded...). What should I do?
Currently it's still in TAMPERED and UNLOCKED state with TWRP installed.
Click to expand...
Click to collapse
there is no way out of this without s-off, I don't even understand why you are putting efforts on installing ota/guru reset/nandroid backup at this point.
you are on hboot 1.56 means you should try to s-off using firewater.
then you'll be able to remove the tampered flag and set the bootload back to "LOCKED" (not RE-LOCKED)
follow guide linked in my signature for going back to stock
try to s-off using firewater + arhd 31.6 rom
alray said:
there is no way out of this without s-off, I don't even understand why you are putting efforts on installing ota/guru reset/nandroid backup at this point.
you are on hboot 1.56 means you should try to s-off using firewater.
then you'll be able to remove the tampered flag and set the bootload back to "LOCKED" (not RE-LOCKED)
follow guide linked in my signature for going back to stock
try to s-off using firewater + arhd 31.6 rom
Click to expand...
Click to collapse
I know. I tried to get s-off but none of the given tools succeeded. They all complete their full cycle and eventually after the last reboot I go and check the state and it still says s-on... Then I did read I need a proper ROM so the tools can work (better). I tried to install ARHD like you mention, but after flashing it was stuck in a bootloop again. Clearing the cache and davlik didn't solve it.
At the moment I only need to know if it's safe to update to the new 5.16.161.2 update while it's unlocked... I got TWRP installed but I know I have to flash the stock recovery in order to make the update work. But I'm afraid I'm going to brick it again if I lock it again, as I don't know if it's needed to let the update complete without any errors.

[Q] One M7 GPE 5.0.1 No IMEI, Baseband

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

HTC ONE Bootloop

Hello,
I hope somebody can help me with a new HTC One. It stucks in bootloops. Sometimes I can get to the lockscreen: But when I unlock the device the HTC-logo shows up and the phone restarts again. Some ideas to solve my problems? I thought I could flash the ruu with fastboot? but it failed - well, maybe it was the wrong firmware or did another mistake..
The device is locked - so no recovery and no root, but I can reach the bootloader
Hboot 1.57.0000
firmware 5.12.206.3
UPDATE
Oh well. It is an O2-model.. so I need an O2-ruu and if I can't find an O2-ruu I can't unbrick my phone??!!
seven09 said:
Hello,
I hope somebody can help me with a new HTC One. It stucks in bootloops. Sometimes I can get to the lockscreen: But when I unlock the device the HTC-logo shows up and the phone restarts again. Some ideas to solve my problems? I thought I could flash the ruu with fastboot? but it failed - well, maybe it was the wrong firmware or did another mistake..
The device is locked - so no recovery and no root, but I can reach the bootloader
Hboot 1.57.0000
firmware 5.12.206.3
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 4T.27.3218.14
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 5.12.206.3
(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: O2___102
(bootloader) battery-status: good
(bootloader) battery-voltage: 4294mV
(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
UPDATE
Oh well. It is an O2-model.. so I need an O2-ruu and if I can't find an O2-ruu I can't unbrick my phone??!!
Click to expand...
Click to collapse
1st of all delete IMEI No & serial number from your post above
Go to bootloader select recovery
In recovery wipe cache and restart
( If recovery not show menu then press volume up 1st + power button 2nd for 5 secs then leave power button then volume it will show menu )
If wipe cache not working you have to factory reset your phone from bootloader
This problem arises when any installed app trouble with boot or corrupt app data
Thanks for your reply..
but nothing worked. I opened the bootloader and installed cwm. After that I tried to restore an old backup, which I found on the Internet and flashed a custom rom as well... :S
Oh now it boots
But every 2 min my device reboots... ??
seven09 said:
Thanks for your reply..
but nothing worked. I opened the bootloader and installed cwm. After that I tried to restore an old backup, which I found on the Internet and flashed a custom rom as well... :S
Oh now it boots
But every 2 min my device reboots... ??
Click to expand...
Click to collapse
what backup version? If using a backup it must be the same version as your firmware (version shown in bootloader).
You should try to flash a custom like ARHD 83, easiest way to get your device booting again. (use TWRP 2.6.3.3)
There is no RUU for this version, so forget RUU unless you want to convert your phone to another version (s-off required)
alray said:
what backup version? If using a backup it must be the same version as your firmware (version shown in bootloader).
You should try to flash a custom like ARHD 83, easiest way to get your device booting again. (use TWRP 2.6.3.3)
There is no RUU for this version, so forget RUU unless you want to convert your phone to another version (s-off required)
Click to expand...
Click to collapse
hmmm, I already tried AHD 83. but I still get reboots very often
Yes there is no RUU. I thought I could maybe try to get s-off, change the cid and install another RUU.. But I dunno if it would solve my Reboot-problem.. Maybe, but I do not want to pay 25 bucks for nothing (sunshine - HBoot 1.57)
seven09 said:
hmmm, I already tried AHD 83. but I still get reboots very often
Yes there is no RUU. I thought I could maybe try to get s-off, change the cid and install another RUU.. But I dunno if it would solve my Reboot-problem.. Maybe, but I do not want to pay 25 bucks for nothing (sunshine - HBoot 1.57)
Click to expand...
Click to collapse
If you achieve S-Off to flash a Ruu, and your phone still have the rebooting issue, then youll know its an hardware problem. 25$ worth it imo

Categories

Resources