Related
Hi everyone! My problem is that if I flash any rom (I've tried ARHD, Viper), the phone gets stuck at the boot screen. I've left it in that state for almost an hour and it hasn't progressed further. Restoring my nandroid backups also yields the same result. My fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331831.A15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT45
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(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: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.163s
The phone is currently unlocked, s-off. I tried flashing with both, philz and twrp, none work. Also, these roms worked before on the same phone with the same recovery so I really have no idea of what went wrong. The firmware on the phone is 1.56.720.6 (Asia-India). I have tried clearing the cache partition multiple times, but it doesn't help.
n1234d said:
Hi everyone! My problem is that if I flash any rom (I've tried ARHD, Viper), the phone gets stuck at the boot screen. I've left it in that state for almost an hour and it hasn't progressed further. Restoring my nandroid backups also yields the same result. My fastboot getvar all:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.0000
(bootloader) version-baseband: 1.16.21331831.A15G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: HT45
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(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: c3d94491
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.163s
The phone is currently unlocked, s-off. I tried flashing with both, philz and twrp, none work. Also, these roms worked before on the same phone with the same recovery so I really have no idea of what went wrong. The firmware on the phone is 1.56.720.6 (Asia-India). I have tried clearing the cache partition multiple times, but it doesn't help.
Click to expand...
Click to collapse
The attached image is where it gets stuck. Adb works
E:\m8\>adb devices
List of devices attached
HT45NWM07703 device
@EddyOS, @nkk71 please see this. I think there's something wrong with my /data partition..
Did you recently do the GPE conversion?
May be you should try to flash the stock rom and stock recovery then flash the ruu.
Sir-Fix-a-Lot said:
Did you recently do the GPE conversion?
Click to expand...
Click to collapse
This, the partitions get altered so you can't just simply flash back
According to the OP's getvar output they've NOT done the GPe conversion as the HBOOT version included in the RUU is 3.18.0.0000 and the OP is still on 3.16.0.0000
OP, I'd follow my guide linked in my signature and you should be good to go
Sir-Fix-a-Lot said:
Did you recently do the GPE conversion?
Click to expand...
Click to collapse
Nope
Jyotirdeb said:
May be you should try to flash the stock rom and stock recovery then flash the ruu.
Click to expand...
Click to collapse
I hadn't touched the firmware, so there shouldn't be any problem related to that. Anyways, a rom and recovery do Not affect an RUU flash.
ashyx said:
This, the partitions get altered so you can't just simply flash back
Click to expand...
Click to collapse
Again, nope, I didn't do gpe
EddyOS said:
According to the OP's getvar output they've NOT done the GPe conversion as the HBOOT version included in the RUU is 3.18.0.0000 and the OP is still on 3.16.0.0000
OP, I'd follow my guide linked in my signature and you should be good to go
Click to expand...
Click to collapse
I flashed the international fw zip, and ARHD, (I had checked the hash of the file) and it still didn't work. Also, when I would reboot, some random artefacts would appear during the boot animation (different each time, sometimes wouldn't appear), such as there would be a random flash of purple across the screen or the boot animation would leave a trail behind it (like the effect you get web you would drag a stuck window in win98) etc. sometimes TWRP would act extremely sluggish while sometimes it would be fast and snappy. Quite a few times, while flashing any rom, the screen would go black and reboot to TWRP at random (even after disabling the display timeout). I tried formatting all the partitions on the internal storage. Still gave me problems. I tried to repair file system of each partition in TWRP. The data partition could never get repaired. All of these random problems lead me to believe that this was 99% the fault of the phone/hardware. Luckily I was within the 14 day replacement period and so I went out today after flashing the faux locked/s-on bootloader (I know I should not mess with firmware unless required, and I hadn't till now but I didn't care anymore since I was getting it replaced anyway. I also had 2 dead pixels and a scratch on my camera glass. Now I just have to sit back and wait for a new phone
We've seen this issue on Viper a few times and it usually happened after someone installed e.g. a VZW recovery to the GSM phone or vice versa.
A wrong recovery would flash stuff into the wrong partitions.
A RUU for your device, really just any, should fix it. You should run a RUU and then factory reset right afterwards from bootloader BEFORE flashing another custom recovery.
There is a cingular (AT&T) RUU out right now from HTC here: http://dl3.htc.com/application/RUU_...G_20.31A.4145.02L_release_368350_signed_2.exe which you could try - it is a GSM RUU. We don't really have WWE 401 RUU yet.
Just make sure you don't grab a SPRINT or Verizon RUU if you find any!!!!!!
Sneakyghost said:
We've seen this issue on Viper a few times and it usually happened after someone installed e.g. a VZW recovery to the GSM phone or vice versa.
A wrong recovery would flash stuff into the wrong partitions.
A RUU for your device, really just any, should fix it. You should run a RUU and then factory reset right afterwards from bootloader BEFORE flashing another custom recovery.
There is a cingular (AT&T) RUU out right now from HTC here: http://dl3.htc.com/application/RUU_...G_20.31A.4145.02L_release_368350_signed_2.exe which you could try - it is a GSM RUU. We don't really have WWE 401 RUU yet.
Just make sure you don't grab a SPRINT or Verizon RUU if you find any!!!!!!
Click to expand...
Click to collapse
Too late for trying a fix , I just want to know what caused it, and I'm 1000% sure I had the right recovery, because as I said, I flashed many other roms in the past with the same recovery, and the problem came after I tried ARHD. And this is the gsm phone.
Yeah well no idea then. Just know I've seen this happen from wrong recoveries. Also not the time to dig into it any further if you've gotten that resolved already I'll leave it as is. Thanks for asking me though. Just keep in mind I've been out of XDA since months and am only slowly reading my way back in so I'm sure there are way more knowledgeable guys around regarding firmware, softbricks and the like.
mobile post... lazy typing...
n1234d said:
Too late for trying a fix , I just want to know what caused it, and I'm 1000% sure I had the right recovery, because as I said, I flashed many other roms in the past with the same recovery, and the problem came after I tried ARHD. And this is the gsm phone.
Click to expand...
Click to collapse
In such a big mess! I have the same problem as the OP - same to the last dot. I am on India version of device, and was just trying to update firmware to 4.4.3 and in that quest i flashed firmware from here http://forum.xda-developers.com/showpost.php?p=54899772&postcount=1392.
Post that camera and wi-fi stopped working - so I thought may be I screwed up with boot.img and reflashing Viper/ADHD would solve it. While on my way to install Viper I cleaned/wiped data in recovery and hit reboot accidentally which got the phone to stuck in bootloop. I pushed in back in recovery however, since then I have not been able to install either Viper or ADHD. I even tried doing a nandroid back-up from here: http://forum.xda-developers.com/showpost.php?p=54940131&postcount=1419, however nothing brings me past the splash screen.
Off-late (few hours) I am not been able to do a back-up (nandroid) as my recovery throws cant mount sdcard or sdcard1 both. Please help!
Here is the "getvar all" log:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.16G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.720.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT469WM02625
(bootloader) imei: xxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(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: 42372cde
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
7mojo said:
In such a big mess! I have the same problem as the OP - same to the last dot. I am on India version of device, and was just trying to update firmware to 4.4.3 and in that quest i flashed firmware from here http://forum.xda-developers.com/showpost.php?p=54899772&postcount=1392.
Post that camera and wi-fi stopped working - so I thought may be I screwed up with boot.img and reflashing Viper/ADHD would solve it. While on my way to install Viper I cleaned/wiped data in recovery and hit reboot accidentally which got the phone to stuck in bootloop. I pushed in back in recovery however, since then I have not been able to install either Viper or ADHD. I even tried doing a nandroid back-up from here: http://forum.xda-developers.com/showpost.php?p=54940131&postcount=1419, however nothing brings me past the splash screen.
Off-late (few hours) I am not been able to do a back-up (nandroid) as my recovery throws cant mount sdcard or sdcard1 both. Please help!
Here is the "getvar all" log:
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.18.0.0000
(bootloader) version-baseband: 1.19.21331147A1.16G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 2.10.720.1
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: HT469WM02625
(bootloader) imei: xxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B65000
(bootloader) cidnum: HTC__038
(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: 42372cde
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
Did you re-unlock your phone?
Sent from my HTC One_M8 using Tapatalk
n1234d said:
Did you re-unlock your phone?
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
Yes, I did. Using HTCDev.
At the moment, I would be just happy with someway of going back to the clean slate. Is there a way I could go back to original/stock using ADB/Fastboot as recovery also doesnt seem to work.
Thanks
7mojo said:
Yes, I did. Using HTCDev.
At the moment, I would be just happy with someway of going back to the clean slate. Is there a way I could go back to original/stock using ADB/Fastboot as recovery also doesnt seem to work.
Thanks
Click to expand...
Click to collapse
Bump!
Anyone?
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!
Hello guys, so today i decided to unroot my phone and go back to stock because i want to sell it. I started doing theunlockr.com method (http://theunlockr.com/2014/06/08/how-to-unroot-the-htc-one-m8-video/) in the step of flashing stock nandroid backup, i flashed it using TWRP restore utility, then i didnt find any folder in the gallery and there was around 5 out of 16 GB avaialible only, so i did a "fromat data", since it erases everything, i pushed the firmware 4.16.401.10 using ADB into the TWRP folder (it wasnt there so i created a backup and there i found it). Then i restored the nandroid backup, now there are 4.5GB used which i cant find and some folders still dont appear in file manager... and i have wifi issues, it doesnt connect to wifi and neither does mobile data work. I need help as soon as possible. ANy help is MUCH apprecciated. Than you guys. and if there is any other way to completely unroot hope someone would help.
PS, i am planning to flash stock recovery, its just i want to fix the current problemss then i can flash stock recovery and lock the bootloader.
Need more info. Do an adb getvar all, but remember to delete your IMEI and serial number (those are personal data) before you post the output.
thats what i got
Down...
redpoint73 said:
Need more info. Do an adb getvar all, but remember to delete your IMEI and serial number (those are personal data) before you post the output.
Click to expand...
Click to collapse
Thanks for your reply, i went back rooted because it was unusable without wifi, so here is what i got:
(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: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__J15
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
abdane said:
Thanks for your reply, i went back rooted because it was unusable without wifi, so here is what i got:
(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: xxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxx
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: HTC__J15
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Click to expand...
Click to collapse
The easiest way to go back to stock is to run the appropriate RUU.
Download this RUU onto your PC.
When the download if finished, hook your phone up to your PC and double click on the download.
Follow the prompts.
Super easy.
This will bring you back to stock including your stock recovery. It will also wipe your phone.
redpoint73 said:
Need more info. Do an adb getvar all, but remember to delete your IMEI and serial number (those are personal data) before you post the output.
Click to expand...
Click to collapse
xunholyx said:
The easiest way to go back to stock is to run the appropriate RUU.
Download this RUU onto your PC.
When the download if finished, hook your phone up to your PC and double click on the download.
Follow the prompts.
Super easy.
This will bring you back to stock including your stock recovery. It will also wipe your phone.
Click to expand...
Click to collapse
Thank you so much for your help, i will try this as soon as the download finishes. Is the normal M8 S-OFF or S-ON? and if it is either one, how do i change it? Because i want to go exactly back as it was in order to sell it.
Thanks again for your help ^_^
abdane said:
Thank you so much for your help, i will try this as soon as the download finishes. Is the normal M8 S-OFF or S-ON? and if it is either one, how do i change it? Because i want to go exactly back as it was in order to sell it.
Thanks again for your help ^_^
Click to expand...
Click to collapse
You are already S-On, and will remain that way.
The only differences from the day you bought it will be that the bootloader is unlocked, and the the stock ROM is the latest Android version (5.0.1 Lollipop instead of 4.4.2 Jellybean), just as it would be if you had remained stock and updated through the OTA updates from HTC and your carrier.
xunholyx said:
You are already S-On, and will remain that way.
The only differences from the day you bought it will be that the bootloader is unlocked, and the the stock ROM is the latest Android version (5.0.1 Lollipop instead of 4.4.2 Jellybean), just as it would be if you had remained stock and updated through the OTA updates from HTC and your carrier.
Click to expand...
Click to collapse
But it is easy to re-lock the bootloader, should i do it?
xunholyx said:
You are already S-On, and will remain that way.
The only differences from the day you bought it will be that the bootloader is unlocked, and the the stock ROM is the latest Android version (5.0.1 Lollipop instead of 4.4.2 Jellybean), just as it would be if you had remained stock and updated through the OTA updates from HTC and your carrier.
Click to expand...
Click to collapse
Oh and also as i said above, last time i tried the wifi wasnt working and there was no storage visible (no folders even though there is something taking up space). Will these problems go away?
Thanks again
abdane said:
But it is easy to re-lock the bootloader, should i do it?
Click to expand...
Click to collapse
Without S-Off (which costs $25), you can only set it to re-locked status and not locked, so I wouldn't bother.
abdane said:
Oh and also as i said above, last time i tried the wifi wasnt working and there was no storage visible (no folders even though there is something taking up space). Will these problems go away?
Thanks again
Click to expand...
Click to collapse
Yes, your problems should be fixed.
Which RUU
xunholyx said:
The easiest way to go back to stock is to run the appropriate RUU.
onto your PC.
When the download if finished, hook your phone up to your PC and double click on the download.
Follow the prompts.
Super easy.
This will bring you back to stock including your stock recovery. It will also wipe your phone.
Click to expand...
Click to collapse
Hey,
I was wondering how I could check which RUU I have to download,
I have some problems as well, and am hoping this will fix it.
Thanks in advance!
KodoKevin123 said:
Hey,
I was wondering how I could check which RUU I have to download,
I have some problems as well, and am hoping this will fix it.
Thanks in advance!
Click to expand...
Click to collapse
From your getvar. Hook up to your PC, get into ADB, and enter adb getvar all.
Post the readout here. Edit out your IMEI and serial# from it first. That is private information that you should never post on a public forum.
EDIT: I saw your bootloader readout in the thread you started. There is no RUU available for your device (Vodafone) that I am aware of. Sorry.
xunholyx said:
From your getvar. Hook up to your PC, get into ADB, and enter adb getvar all.
Post the readout here. Edit out your IMEI and serial# from it first. That is private information that you should never post on a public forum.
Click to expand...
Click to collapse
(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.29.161.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAPE17
(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: 26b322e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thank you so much
KodoKevin123 said:
(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.29.161.9
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: VODAPE17
(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: 26b322e5
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Thank you so much
Click to expand...
Click to collapse
I guess you didn't see my edited reply. I don't know of any Vodafone RUUs. I don't think there is one.
xunholyx said:
I guess you didn't see my edited reply. I don't know of any Vodafone RUUs. I don't think there is one.
Click to expand...
Click to collapse
Oh indeed I didn't.
Thank you for searching for me anyway!
Guess there is no other way to restore my phone?
KodoKevin123 said:
Oh indeed I didn't.
Thank you for searching for me anyway!
Guess there is no other way to restore my phone?
Click to expand...
Click to collapse
Answered in the thread you started instead of highjacking this one.
xunholyx said:
Without S-Off (which costs $25), you can only set it to re-locked status and not locked, so I wouldn't bother.
Yes, your problems should be fixed.
Click to expand...
Click to collapse
Hello again, so i did the utility but after clicking "update" it gave me error 155: Unknown error
The ROM Updat Utility cannot update your Androd phone.
Please get the correct ROM Update Utility and try again.
Any suggstions?
abdane said:
Hello again, so i did the utility but after clicking "update" it gave me error 155: Unknown error
The ROM Updat Utility cannot update your Androd phone.
Please get the correct ROM Update Utility and try again.
Any suggstions?
Click to expand...
Click to collapse
Error 155, I guess you'll need to re-lock your bootloader after all.
fastboot oem lock , then run the RUU again.
xunholyx said:
Error 155, I guess you'll need to re-lock your bootloader after all.
fastboot oem lock , then run the RUU again.
Click to expand...
Click to collapse
Yup that did the trick, its now back to stock unrooted and everything is working perfectly fine. Thank you so much ^_^
I followed the instructions fine and never hit a snag, upgrading from Android 4.4.4 stock but rooted to the latest ARHD running Android 5.0.1. I'm not sure if the issue is related to the lollipop update or the rom but once my phone screen locks I lose my WiFi connection. I can go into WiFi and see the available networks, select my one and click connect but nothing happens, the only way to get WiFi working again is to restart the phone which is becoming really frustrating. I have tried forgetting the network then re adding it too but the issue remains. Anyone else had this problem or know of a fix?
On a less annoying note when iIstart up it first acts like it's loafing bootloader with the red text at the bottom of the screen then restarts itself and boots fine.
Firmware Update
Stock rom - ota or s-off flash fastboot
Htc One M8 & Tapatalk
linar10 said:
Firmware Update
Stock rom - ota or s-off flash fastboot
Htc One M8 & Tapatalk
Click to expand...
Click to collapse
Thanks, could you help a little more? I have been reading up but dont fully understand how i know which firmware i need to flash?
enter result of this command
fastboot getvar all
Edit
I suggest you read this topic
http://forum.xda-developers.com/showthread.php?t=2800727
Htc One M8 & Tapatalk
Thanks for getting back to me - I have read that thread but it still doesn't seem to tell me how i work out which firmware I need or im being silly?
If you can point me in the right direction, here was my result:
(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) 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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Also could I get it to install under ARHD but with the stock recovery instead of TWRP?
linar10 said:
enter result of this command
fastboot getvar all
Edit
I suggest you read this topic
http://forum.xda-developers.com/showthread.php?t=2800727
Htc One M8 & Tapatalk
Click to expand...
Click to collapse
t3stin said:
Thanks for getting back to me - I have read that thread but it still doesn't seem to tell me how i work out which firmware I need or im being silly?
If you can point me in the right direction, here was my result:
(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: SH43VWM09276
(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: df77f8b7
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Also could I get it to install under ARHD but with the stock recovery instead of TWRP?
Click to expand...
Click to collapse
Your HTC is WWE and your bootloader is at 3.19 so i suggest to restore a stock backup from here
http://forum.xda-developers.com/showthread.php?t=3086860
Take the 4.16.401.10, that will work. And if you also put back the stock recovery you can also perform official OTA updates.
READ the opening post very carefully as its very good explained !
1.22 radio - firmware 3xxxx
Hboot 3.19 - firmware 3xxx - 4xxxx
Restore backup 3xxx
Flash stock recovery
Ota
Htc One M8 & Tapatalk
Im now back to stock, running the latest firmware - no more updates available and though it was fixed but the wifi has just dropped out and had to restart to get it back (I can see the network it just will not connect). Does this mean it is a Lollipop issue?
Mr Hofs said:
Your HTC is WWE and your bootloader is at 3.19 so i suggest to restore a stock backup from here
http://forum.xda-developers.com/showthread.php?t=3086860
Take the 4.16.401.10, that will work. And if you also put back the stock recovery you can also perform official OTA updates.
READ the opening post very carefully as its very good explained !
Click to expand...
Click to collapse
This backup restore
https://mega.nz/#!uoMHBCZQ!167M3qO9hYCMpeB-aFBrYXgJB459c_bM8I9WJt5Cc7g
Recovery stock
https://mega.nz/#!61llVa5Z!cUFoUaQBRCjX0YOA24GogtkhS_nkMMSK_erc5JvK3lM
Htc One M8 & Tapatalk
t3stin said:
Im now back to stock, running the latest firmware - no more updates available
Click to expand...
Click to collapse
Does that mean you installed an OTA update after returning to stock nandroid and stock recovery?
redpoint73 said:
Does that mean you installed an OTA update after returning to stock nandroid and stock recovery?
Click to expand...
Click to collapse
Correct..
restoring backup which version, if 4xxx restore that which I have given above
Htc One M8 & Tapatalk
t3stin said:
Correct..
Click to expand...
Click to collapse
Post the current getvar all.
Also, you should delete the serial number from your last getvar all (and the new one, of course) as that is personal info.
You may need to OTA again. I think some OTAs had WiFi broken, even on fully stock devices; and it was fixed on a subsequent OTA.
If you restore a backup 4xx10 and made Ota to 4xx13 he did not update the firmware. Must restore the backup 3xxx and make ota. This will solve the problems with wifi.
HtcOneM8 @ Tapatalk
linar10 said:
If you restore a backup 4xx10 and made Ota to 4xx13 he did not update the firmware. Must restore the backup 3xxx and make ota. This will solve the problems with wifi.
Click to expand...
Click to collapse
I was thinking along those lines (why I asked for updated getvar data) as the radio number indicates 3.xx firmware.
But I am surprised up updated at all, with the improper (old) firmware.
I do not see any other reason malfunction wifi, in addition to hardware failure.
The last ota was not large, so it may be that it could be downloaded. Let's wait author may write off something that already everything is running or not
HtcOneM8 @ Tapatalk
Sorry havent been able to get online since - I just tried to download the files you linked to and they are no longer available?
linar10 said:
This backup restore
https://mega.nz/#!uoMHBCZQ!167M3qO9hYCMpeB-aFBrYXgJB459c_bM8I9WJt5Cc7g
Recovery stock
https://mega.nz/#!61llVa5Z!cUFoUaQBRCjX0YOA24GogtkhS_nkMMSK_erc5JvK3lM
Htc One M8 & Tapatalk
Click to expand...
Click to collapse
tried restoring to a 3.xxx and im stuck on the boot screen.
redpoint73 said:
I was thinking along those lines (why I asked for updated getvar data) as the radio number indicates 3.xx firmware.
But I am surprised up updated at all, with the improper (old) firmware.
Click to expand...
Click to collapse
gone back to 4.xxx took the OTA again - getvar:
(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: 4.16.401.13
(bootloader) version-misc: PVT SHIP S-ON
(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: f063fb42
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
redpoint73 said:
Post the current getvar all.
Also, you should delete the serial number from your last getvar all (and the new one, of course) as that is personal info.
You may need to OTA again. I think some OTAs had WiFi broken, even on fully stock devices; and it was fixed on a subsequent OTA.
Click to expand...
Click to collapse
Hi all,
I have an old HTC one m8 which was working fine when I stored it away last year. Today I tried to turn it on and found myself looking at safe mode menu with the heading
"Software status: Modified"
LOCKED
Security Warning
Now I have been going through the form for the last couple of hours trying different things but they dont seem to work.
e.g) I got a ver 4.20 RUU for my phone mentioned in this link
https://forum.xda-developers.com/htc-one-m8/help/finding-ruu-t3283633
but that does not work because my phone currently is on OS-6.13 and apparently I can not downgrade to OS-4 while my phone is S-ON. (I get ERROR 159 IMAGE ERROR)
So i tried to make it S-OFF. Unfortunately from what I have read they only way to do that is through the adb tool which does not work in the fastboot mode I am currently stuck on (fastboot commands work fine from my PC). So I can't downgrade to the only RUU I have found for my modelid and cid. I have no idea how to proceed now.
my phone specs
(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.13.206.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: xxxxxxxxxxxxxx
(bootloader) imei: xxxxxxxxxxxxxxxxx
(bootloader) imei2: Not Support
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Any ideas?
mezomizz said:
apparently I can not downgrade to OS-4 while my phone is S-ON. (I get ERROR 159 IMAGE ERROR)
Click to expand...
Click to collapse
Correct. Downgrading is not allowed with s-on.
mezomizz said:
So i tried to make it S-OFF. Unfortunately from what I have read they only way to do that is through the adb tool which does not work in the fastboot mode I am currently stuck on (fastboot commands work fine from my PC).
Click to expand...
Click to collapse
There is no (current) valid method to s-off using adb. If you are talking about firewater, that method has not worked since 2014, and nothing you do will make it work.
The valid current method to s-off is with sunshine app ($25 US) but also requires a working OS.
You also do not need s-off to get the phone working again. Since a Marshmallow version RUU for your CID/MID is not available, you can restore the stock TWRP backup from the collection in the link below: https://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
Unlock bootloader using HTCDev.com, install custom recovery TWRP, then restore the TWRP backup 6.13.206.5 using the instruction in the link above.