Hi,
Gods and gurus of flashing I need your help on getting my M8 on T-MOB101 back to life. I've been trying update it to marshmallow and (long story short) I'm currently looking at empty flash wit only access to fastboot and ability to install/use TWRP.
Can someone supply me with a source of an RUU that will bring me back to stock? Sadly I'm S-ON with no access to the system obv.
Is there any other way to get it back to life?
Please help
My device info:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH51EWM02678
(bootloader) imei: 357336067173523
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: T-MOB101
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 4c3fbd70
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Best help is self help I guess - I used this thread with great success: http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Thanks
So I recently went back to stock so that I could update to MM via t-mobile OTA (I am S-ON as well). So what I did was to first find a stock version of the ROM and recovery I was running when I loaded TWRP onto it, this is key.
Because custom roms don't update firmware you need to go back to a un-rooted stock ROM. Once you find it, you also need to match the recovery to the firmware to the ROM. All 3 must match or it won't work.
So I installed the ROM and rebooted to fastboot (note: do not install su), and then I installed the stock recovery via fastboot. Booted up and did a basic setup of the phone (updating software etc), and then once it was done I did the OTA and prayed. Because of my lack on knowledge it took me a couple a tries, mainly because the recovery I first installed was 1 version newer than what the ROM or firmware was.
Once done, I had to dev-unlock again. I now keep a copy for myself of the original recovery and initial stock backup.
Hope this helps
-brad
Related
I was (CID=TELST001). I wanted to flash VenomOne ROM. I rooted, unlocked bootloader and flashed Venon ROM. Then found that WiFi didn't work as I had not upgraded firmeware to the right base.
So I had to go back to stock to upgrade firmware and then reflash Venom ROM. I restored a stock nandroid (1.12 firmware). I then found n OTA which included 1.54 upgrade, another a 2.23 upgrade to fw and yet another to 3.23 firmware, all with matching CID. All went well until last firmware flash.
I flash fw.zip by extracting it from the OTA.zip and flashing it according to instructions here - http://forum.xda-developers.com/showthread.php?t=2696282
But since flashing 3.23 fw.zip and when it rebooted it gets stuck on the white HTC/powered by Android screen and doesn't proceed. I don't think it's just a slow boot - it has sat there for over half hour. Powering down doesn't work (either power button nor power + vol down) - it just comes back to same screen.
I had to reset by power+VolUp and then Switch to power+voldown - got back to hboot/fastboot. Below are the getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.22.21331147A1.29G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.32.841.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B11000
(bootloader) cidnum: TELST001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: a3d0cb0d
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Above shows I am on the right firmware and HBOOT to now flash Venom. But I can't boot up into stock. is there something wrong with the boot.img? Should I proceed to unlock and flash Venom ROM even though I can't successfully boot into stock before doing so?
Yep just flash the new rom.
Hello xda-Community!
First off, I have posted this a couple of weeks ago in the general help thread, however it quickly got swarmed and lost, so I wanted to try again.
I have run into some trouble with my O2 HTC One M8. First, my readout from fastboot:
Code:
fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA13G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2:
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: O2___102
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
I have been running CM11 for some months and am pretty happy with it, but I want to upgrade to Lollipop. However, the phone won't let me do that, as hboot is only version 3.16.0.0000 and Lollipop needs 3.19 (apparently). The version_main is empty for some reason, I did not erase that part.
But now comes the kicker: To upgrade hboot, I need to return to stock (or set the CID to SuperCID), right?
Now, I cannot return to stock, because there is no RUU / nandroid backup for my CID (O2___102).
As I don't have S-OFF, I cannot install any other RUU. To get S-OFF with SunShine, I need to be on stock though, because right now I get the following error message: "Your device has a debuggable ramdisk (ro.debuggable=1). You need to flash a non-debuggable boot.img, stock would be best."
So basically: I need to get back to stock to go back to stock, or am I reading this wrong?
Is there a way out of this?
In the general help thread, someone said I should flash a ROM close to stock (he/she suggested Maximus HD) for this to go away, but I cannot flash any ROM besides the CM11 one I am already on, as none of the other ROMs allow me to boot - I simply get stuck during boot-up and have to reflash CM11 to use the phone.
The recovery I am using is TWRP 2.7.0.2 if that information is necessary or helpful.
Thanks in advance for anybody who can help me.
Have you try stock nandroid backup 1.54.206.5 or 1.12.206.17 from this thread ?
http://forum.xda-developers.com/showthread.php?t=2701376
ckpv5 said:
Have you try stock nandroid backup 1.54.206.5 or 1.12.206.17 from this thread ?
http://forum.xda-developers.com/showthread.php?t=2701376
Click to expand...
Click to collapse
Well god damn it. I had tried those but apparently, they got corrupted in the download. Just tried again (from my laptop) and it worked marvellously. Thank you for your reply!
Hey there,
C:\adb\adb>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 098a72e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.072s
http://forum.xda-developers.com/showthread.php?t=2701376
several months ago I have unlocked my phone, reset it to factory several times and in general just tried out installing custom recoveries to ultimately install a custom rom.
I eventually stopped before flashing a custom rom.
A few days ago I started really trying again and I have noticed that i can not install any custom roms without updating my firmware first.
My current version is 1.41.5 and i run android 4.4.2, way too outdated to do anything.
The real problem is that even relocking the bootloader, resetting to factory settings and trying to manually flash a firmware update it will not work.
I am stuck. There is no stock rom available for my third party german carrier anywhere on the internet. (Mobilcom Debitel)
It appears it is impossible to get back the bloatware that came with the phone which is required to update, right?
I don't know how to proceed at this point.
Is there any thing I can do?
Would going s-off help?
I would be very appreciative of any help you guys can give me.
I read in the following thread: http://forum.xda-developers.com/showthread.php?t=2701376
Q : Can i apply an official HTC OTA on my stock rooted rom?
A : Yes but the system apps (carrier branded apps included) has to be 100% intact.
There seems to be no way to get the carrier brand apps for me. Is there a different way?
Edit: If I achieve s-off, would that be a way around my issue?
With your current knowledge base S-OFF would surely lead to a brick. I would wait on that. You need to return to stock recovery, take your carriers OTA's of which there will be at least three or four, then you will be able to install any current ROM. Search return to stock thread for a 1.54.xxx recovery for your CID.
crovean11 said:
Hey there,
C:\adb\adb>fastboot getvar all
< waiting for device >
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: INVALID_VER_INFO
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__102
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 098a72e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.072s
http://forum.xda-developers.com/showthread.php?t=2701376
several months ago I have unlocked my phone, reset it to factory several times and in general just tried out installing custom recoveries to ultimately install a custom rom.
I eventually stopped before flashing a custom rom.
A few days ago I started really trying again and I have noticed that i can not install any custom roms without updating my firmware first.
My current version is 1.41.5 and i run android 4.4.2, way too outdated to do anything.
The real problem is that even relocking the bootloader, resetting to factory settings and trying to manually flash a firmware update it will not work.
I am stuck. There is no stock rom available for my third party german carrier anywhere on the internet. (Mobilcom Debitel)
It appears it is impossible to get back the bloatware that came with the phone which is required to update, right?
I don't know how to proceed at this point.
Is there any thing I can do?
Would going s-off help?
I would be very appreciative of any help you guys can give me.
I read in the following thread: http://forum.xda-developers.com/showthread.php?t=2701376
Q : Can i apply an official HTC OTA on my stock rooted rom?
A : Yes but the system apps (carrier branded apps included) has to be 100% intact.
There seems to be no way to get the carrier brand apps for me. Is there a different way?
Edit: If I achieve s-off, would that be a way around my issue?
Click to expand...
Click to collapse
First of all, delete the IMEI from your post. Never put that on a public forum.
Yes, S-Off would be a way, but the safest would be to run an RUU to update. Hook your phone up to your PC, and get into fastboot.
Download the 4.16.401.10 WWE RUU from here.
When the download if finished, double click it, and follow the prompts.
When it's finished, turn on your phone, go through the setup, and enjoy Lollipop.
Make sure to back up anything that is important to you, because this will wipe your phone.
Thank you for the replies, I will report on my success once I have tried what you have proposed, thanks!
Hi everyone,
I attempted to root my HTC One M8 a few months ago and I got completely stuck and soft bricked my phone.
I now just want to try to get it working any way I can (back to stock or rooted whichever is easiest)
My bootloader is unlocked
I have S-ON (and I'm not sure of the best method to gain S-OFF if this is required, as there is a lot of conflicting information)
and I have TWRP v2.8.7.0 installed (I know this must be an old version now)
My region is United Kingdom/ carrier EE
Can anyone please advise me how I might be able to get my phone working again? (back to any working state is fine)
If this is any help... when I do fastboot getvar all, this is the information which comes up
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks for taking the time to read this!
TMJay said:
Hi everyone,
I attempted to root my HTC One M8 a few months ago and I got completely stuck and soft bricked my phone.
I now just want to try to get it working any way I can (back to stock or rooted whichever is easiest)
My bootloader is unlocked
I have S-ON (and I'm not sure of the best method to gain S-OFF if this is required, as there is a lot of conflicting information)
and I have TWRP v2.8.7.0 installed (I know this must be an old version now)
My region is United Kingdom/ carrier EE
Can anyone please advise me how I might be able to get my phone working again? (back to any working state is fine)
If this is any help... when I do fastboot getvar all, this is the information which comes up
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.29.214500021.12G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 6.12.401.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__001
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: on
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thanks for taking the time to read this!
Click to expand...
Click to collapse
You have European version htc m8 .
The easiest method is running a RUU for going back to stock .
Relock your bootloader .
Go to bootloader
Give command
Fastboot oem lock
Download this RUU
https://www.androidfilehost.com/?fid=24369303960687057
Rename it 0P6BIMG.zip
Place it in sd card
Boot to bootloader
It will automatically read the ruu file and proceed with instructions.
HiT Thanks if SomeBody Helps you..
Thanks so much for the fast reply and perfect solution!!!
Hi sonnu0100.
I am in the exact same position as TMJay, however the only difference for me is that my CIDnum is "orange001".
Do you know which RRU I can use as the one you've provided for TMJay doesn't work for me. The error I receive is:-
"CID incorrect!
Update Fail!
Device halted due to Large Image update fail!
Press <POWER> to reboot"
My issue isn't as a result of me flashing things without care. I think there is an onboard memory problem as when I was using my M8 as my primary phone last year (before my HTC 10) it lost the OS without me doing anything. I was able to recover and get a working device again but can't remember what I did. I've gone to hand the phone to someone else to use and it's seemingly died again.... could just be erroneous.
Help appreciated.
Many thanks,
Hi,
For info, I've found a solution by referring to this thread - https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
So I'm back up and running with a working phone for now at least .
Cheers
I did post a week or so ago about installing an RUU and the S-off status of my phone. I've since unlocked the bootloader using HTC-Dev, and have flashed TWRP with the aim of installing a custom ROM. TWRP flashed fine but won't load. I really have no idea what I can do from here. I've tried flashing earlier versions but they still won't load. My getvar all info - minus the IMEI - is:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.15.2133156.UA12.5mv
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 1.54.401.109
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: MB524WM06330
(bootloader) imei: --------------
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 0mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
I honestly don't know where to go from here so any help would be much appreciated!
It seems you have a pre-production unit.
Try to update it to current firmware level - https://forum.xda-developers.com/showpost.php?p=64926626&postcount=6
Then install latest TWRP, then install any custom rom that you like.
Thanks for the info! I followed the steps but the RUU 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip
wouldn’t flash. I then tried flashing a firmware.zip 6.12.401.4 from this link:
https://docs.google.com/spreadsheets/d/1aNd_nm4Em1wamRLFT7qHM2c3O9_sg_H3ztBrGq1u9Ws/pubhtml
zipped with TWRP which was successful and enabled me to flash the latest TWRP v 3.2.3.0, but I wasn’t able to flash Lineage 14.1 with the error “Failed to mount ‘/carrier’ (invalid argument).
Is this a partition issue? Or something else maybe?
I actually installed an S-team marshmallow ROM which flashed fine. I was then able to wipe and flash Lineage 14.1 Nougat. Not sure why, but maybe too big a gap between kit kat & nougat, bridged by marshmallow. Very un-technical I know, I'm sure there's a reason why.
Swell6 said:
I followed the steps but the RUU 0P6BIMG_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_Radio_1.29.214500021.12G_20.72.4196t.01_release_464360_signed.zip
wouldn’t flash. I then tried flashing a firmware.zip 6.12.401.4 from this link:
Click to expand...
Click to collapse
Probably would have made sense to try the RUU again, after flashing the firmware. Hard to say, since you didn't give details on how the RUU failed.