Long story short, I forgot my screen lock and wiped as a last resort. Realizing too late that a factory reset wouldn't complete, I was left with a paperweight. I was able to get a rooted stock ROM from XDA, flashed it and it seems to be working. I want to get back to viper ROM, preferably marshmallow (I'm currently on lollipop) but I am having a lot of trouble. Attempts to get s-off have been thwarted, and flashing viper (5.0.2) has failed. Any help would be appreciated. I can answer any questions.
What stock ROM did you flash, exactly?
How exactly are you trying to s-off, and what step did you get stuck (error messages, or other results?)?
When the ROM failed, did it give you an error message (or list any other outputs or results)?
Your statements on these last 2 points if far too vague, for us to help properly.
Also, do fastboot getvar all, and post the results (delete IMEI and serial number before posting).
Lmy470.h6 is the ROM I flashed. I've been trying to push firewater via adb to get s off. I can't/won't pay for a sunshine. When flashing other stock Roms, the error is no error. It just says install aborted. When trying to flash viper, it says there's a permission error. When trying to run firewater, it gives me the PIE error. Getvar coming later.
Firewater won't work, Period. It had an online component (had to connec to a server), which the devs stopped supporting in Dec 2014. Nothing you do will make it work, and is a complete waste of time.
That said, you don't need s-off to flash ROMs. And whatever is wrong with flashing ROM, s-off is probably not going to fix.
The fact that multiple ROMs work, indicates user error, and you're incorrectly trying to blame the ROMs ("poop ROM").
What TWRP version? Need that info, and getvar data. But I'm guessing you just have an old version of TWRP (or try another slightly different build TWRP).
I'm actually using philz touch recovery. I only call it a poop ROM because I don't like what it came with and how it looks. Also. The ROM I'm using is the only ROM that works thus far. Most other Roms simply abort. Viper ROM tells me it doesn't have to permissions necessary which indicates the need for s off. I attempted getvar, however the command window just sat idle and wouldn't let me type anything. Am I missing something there?
I should also mention I've been using recovery to flash Roms. Perhaps flashing via adb would work better? Or work at all?
One last thing. Flashing the ROM I'm currently using created new 0 directories. I now have 0/0/0. Any safe way to fix that?
enviouss said:
I'm actually using philz touch recovery.
Click to expand...
Click to collapse
That's the problem right there. Philz hasn't been updated in a long time, maybe 2 years. Its almost certainly the cause for the ROM flashes failing.
Use TWRP, but exact version depends on your current firmware version, indicated in getvar. But probably TWRP 2.8.7 since you indicated you were using Lollipop ROMs okay.
enviouss said:
I only call it a poop ROM because I don't like what it came with and how it looks.
Click to expand...
Click to collapse
So its your personal opinion and preference, and I would recommend you not insulting the work of devs that work so hard (usually for no compensation) to post their work here.
---------- Post added at 10:09 AM ---------- Previous post was at 10:06 AM ----------
enviouss said:
I should also mention I've been using recovery to flash Roms. Perhaps flashing via adb would work better? Or work at all?
Click to expand...
Click to collapse
Sideload adb still needs the proper recovery, adb can't flash a ROM by itself. Sideload just adds move points of failure, not less. I don't recommend it, as I've seen it cause more problems than it solves (fails when simply flashing in recovery works).
---------- Post added at 10:11 AM ---------- Previous post was at 10:09 AM ----------
enviouss said:
I attempted getvar, however the command window just sat idle and wouldn't let me type anything. Am I missing something there?
Click to expand...
Click to collapse
Are you in bootloader-fastboot mode when issuing the command?
If so, try another cable, another USB port, or re-install HTC drivers.
I haven't been I boot loader mode. Will try shortly. Also. Will change to twrp. And yes, I'm on lollipop 5.1. I will change recoveries and attempt getvar. Results will be posted.
Getvar results follow.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.21331147A1.19_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.1540.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(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
all: Done!
finished. total time: 0.048s
Getvar results follow.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.21331147A1.19_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.1540.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(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
all: Done!
finished. total time: 0.048s
enviouss said:
Getvar results follow.
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.19.0.0000
(bootloader) version-baseband: 1.21.21331147A1.19_2G
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 3.28.1540.5
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno:
(bootloader) imei:
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul_ca
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B12000
(bootloader) cidnum: BS_US001
(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
all: Done!
finished. total time: 0.048s
Click to expand...
Click to collapse
Also, flashed your recommended version of TRWP recovery. It is up and running. I am ready for the next phase.
enviouss said:
Also, flashed your recommended version of TRWP recovery. It is up and running. I am ready for the next phase.
Click to expand...
Click to collapse
I'm glad I asked for the getvar data. Your firmware (hboot, radio, etc.)is woefully outdated as its still on kitkat firmware, which I can tell from the radio number and version-main 3.28.1540.5. This alone will prevent LP and MM ROMs from working (no boot or broken WiFi).
There are various ways to update the firmware:
- Restore stock TWRP backup for 3.28.1540.5, and corresponding stock recovery, and perform OTA updates which will also update the firmware.
- Relock bootloader, and flash full stock 6.12.1540.4 firmware following the Method 2 here. After flashing firmware, you can then unlock bootloader again, flash TWRP and flash the desire ROM.
I would greatly prefer not to relock my boot loader,as it requires HTC correspondence to unlock. That could take a while. Can you walk me through your first method? Possibly with links to other threads and downloads?
I messed up. big time. So i found and downloaded your recommended recovery image. Downloaded flashify for root, and flashed the image. Now whenever I try to boot, or enter recovery mode, i get the red triangle of death. Please help! I tried reflashing twrp via adb, but adb doesnt recognize my device anymore! I dont know what to do...
update: performed a factory reset. Was able to get device up and running again. Impatiently awaiting further instruction.
enviouss said:
I messed up. big time. So i found and downloaded your recommended recovery image. Downloaded flashify for root, and flashed the image.
Click to expand...
Click to collapse
What did you download, and from where? Its not clear what you were trying to do here, exactly. You don't need root to flash ROMs or TWRP backups; and I personally dislike using apps like Flashify, for things that are easily accomplished with fastboot, TWRP, etc.
I found the stock nandroid backup suggested and flashed it using flashify. I have an idea what needs to be done here, but if an expert like yourself could leave me some detailed instructions as well ad download links it would really help.
enviouss said:
I found the stock nandroid backup suggested and flashed it using flashify. I have an idea what needs to be done here, but if an expert like yourself could leave me some detailed instructions as well ad download links it would really help.
Click to expand...
Click to collapse
He did give you expert advice, and you didn't follow it. Don't use Flashify. Any instructions you get from anyone here will tell you to use ADB/fastboot.
Also, you are going ahead without proper instructions and you can go ahead and do that, but go to where you got those other instructions from to ask for help.
Actually, in reference to the nandroid backup, he (we are assuming here) never said exactly how to use the files. Just what to do. I need precise instructions with links to fix this issue. This is one I've never dealt with before.
Related
Hello,
today my phone freezed in the Notification panel, while i was checking a new mail.
Then I have performed a "battery pull" with Power and VolUp, since that the screen is black.
The last thing i has done before, was to install the Xposed Framework over the installer App.
The strange is that the phone seems to boot and I can connect to the PC.
I have access to the device via adb and fastboot.
It is possible to boot into the Bootloader and even in Recovery (TWRP).
I can't believe that the Screen is dead after a Software freeze, that would be a strange coincidence.
The last 10 hours i have researched the internet for a solution, without success.
I have found this Thread, but no way to restore a nandroid without access to TWRP GUI, because of the black screen.
http://forum.xda-developers.com/showthread.php?t=2715901
I tried to reflash the original firmware, erase cache and to reflash the Recovery,
but the Screen remains black.
My Device: ROM: ARHD5.0
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.00
(bootloader) version-baseband: 1.15.213315
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: SH435XXXXXX
(bootloader) imei: 35XXXXXXXXXXXXX
(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: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Can someone help me?
Maybe with a instruction, how to restore a Nandroid without accsess to TWRP GUI on the device.
best regards, Toni
Toni10 said:
Hello,
today my phone freezed in the Notification panel, while i was checking a new mail.
Then I have performed a "battery pull" with Power and VolUp, since that the screen is black.
The last thing i has done before, was to install the Xposed Framework over the installer App.
The strange is that the phone seems to boot and I can connect to the PC.
I have access to the device via adb and fastboot.
It is possible to boot into the Bootloader and even in Recovery (TWRP).
I can't believe that the Screen is dead after a Software freeze, that would be a strange coincidence.
The last 10 hours i have researched the internet for a solution, without success.
I have found this Thread, but no way to restore a nandroid without access to TWRP GUI, because of the black screen.
http://forum.xda-developers.com/showthread.php?t=2715901
I tried to reflash the original firmware, erase cache and to reflash the Recovery,
but the Screen remains black.
My Device: ROM: ARHD5.0
(bootloader) version: 0.5
(bootloader) version-bootloader: 3.16.0.00
(bootloader) version-baseband: 1.15.213315
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main:
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: SH435XXXXXX
(bootloader) imei: 35XXXXXXXXXXXXX
(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: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: ab0efa49
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
Can someone help me?
Maybe with a instruction, how to restore a Nandroid without accsess to TWRP GUI on the device.
best regards, Toni
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2718130 they might be able to help u
strikerdj2011 said:
http://forum.xda-developers.com/showthread.php?t=2718130 they might be able to help u
Click to expand...
Click to collapse
I saw that topic, but thought that would be a service where you have to send it to the UK.
I've checked the Thread again.
Thank you for Reply!
Best regards, Toni
the only thing I can think of is the RUU, I dont know if it will work on an unlocked bootloader :|
im not sure if there's an RUU already for the m8.
hope someone can provide a better solution
---------- Post added at 01:17 AM ---------- Previous post was at 01:14 AM ----------
ops.. you did try flashing the stock firmware.
mr.dj26 said:
the only thing I can think of is the RUU, I dont know if it will work on an unlocked bootloader :|
im not sure if there's an RUU already for the m8.
hope someone can provide a better solution
---------- Post added at 01:17 AM ---------- Previous post was at 01:14 AM ----------
ops.. you did try flashing the stock firmware.
Click to expand...
Click to collapse
Yes, I have full accsess via adb and fastboot and the System boots up.
Flashing the Stock Firmware.zip that matches the Rom, which is posted at xda, was one of the first things I've done.
Now I'm looking for a way to return it to Stock, since RUUs are not available at the Moment.
Any Ideas?
Best Regards, Toni
Ok, since the system boots up,i could check my M8 with:
adb shell screencap -p /sdcard/screen.png
+
adb pull /sdcard/screen.png
It is working, so it is no Software Brick.
The Screen is dead, but fortunately the Touch is working.
In the next step I copied my own Stock Nandroid 1.12.401.17 to the internal SD, to /TWRP/Backup/SHXXXXXXXXX.
Then I've managed to restore the Nandroid, blinde with my M7 beside.:fingers-crossed:
Now the M8 is Stock with 1.12.401.17 and 1.54.401.5 Firmware.
Which Stock-Recovery I have to flash, for 1.12.401.17 or 1.54.401.5, or it dosen't matter at all?
->I've Found the answer in the FaQ in this Thread:
http://forum.xda-developers.com/showthread.php?t=2701376
I've figured out, that it is definitely a hardware failure of the display.
With the ADB screencap I was able to operate the device over the touch.
In this way I was able to reset it completely back to stock, including Locked Flag (probably).
Now it's on the way back to the distribution company.
@MOD
The Thread can be closed.
Thanks!
Best regards, Toni.
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?
Alright, yesterday I posted a thread asking for help here. Since this is a different issue I created a new topic instead of posting it in that thread.
Since my Android was screwed up and I wanted to revert back to a Sense ROM for a while now, I thought I might as well do that now. I tried it with this guide. Changed my CID to Super CID, flashed the firmware, and did that factory reset in the bootloader. But, since the OS is screwed up and my recovery is gone, I can't use adb anymore. I also can't use it in the bootloader. So, no OS, no recovery, no adb as far as I can tell.
I'm clueless and having a little panic attack here. Any help would be awesome.
Connect your phone in fastboot and then run fastboot getvar all and post the results (minus your S/N and IMEI) and we'll see what you need to get working again
Alright, here it goes.
(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: 1.54.401.5
(bootloader) version-misc: PVT SHIP S-OFF
(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
This is easy, just flash the 4.16.401.10 RUU and jobs done...
http://forum.xda-developers.com/showthread.php?t=2735235
Step 3 applies to you as Step 1 and 2 you don't need to do but make sure you download the files required (you can do Step 2 if you want to change your CID back but that's up to you)
Alright, thanks. What exactly will this get me? And will I be able to flash a custom Sense based rom like InsertCoin then? If so, what steps do I take from here? I'm not really that experienced and kind of afraid I'll screw up again without someone holding my hand through the process.
This will get your phone running 100% stock Sense Lollipop as if you just took the phone out the box. You can then flash a custom ROM (if you'd like) using the guides on here
I haven't done anything yet, but with my goal being having installed InsertCoin, can I just flash TWRP now and flash the InsertCoin zip? I have already gotten to the point in the video I mentioned where I had to flash the firmware. I stopped at the point he went into Android again to enable USB debugging since I wasn't able to that. I didn't go any further because I was afraid of messing my phone up.
You're better off doing what I suggested to make sure everything is up-to-date firmware wise and then go custom
I did what you told me to and everything was okay after that. Right now I'm on InsertCoin. Thank you very much!
Hi there, I am hoping someone can help me, and make things easy to do cause I am tired of traulling through page after page of failed attempts. So a little background first....
My M8 started coming up with an error to do with google play services not working and it crashing repeatedly, after trying everything under the sun to fix the issue, I decided a factory reset was best. So I attempted to do a factory reset from within the HTC. it seemed to do nothing. So I got in to the HBoot menu and that just goes round in circles. Last time it did something silly like this I had to send it off to HTC for repair, I dont fancy losing my phone for 3 weeks AGAIN, so if someone here can help, I would be very grateful.
I did a "fast boot getvar all" to retrieve the following
C:\fastboot\>fastboot getvar all
(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.61.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: SH*******704
(bootloader) imei: 3*******8447643
(bootloader) imei2: Not Support
(bootloader) meid: 00000000000000
(bootloader) product: m8_ul
(bootloader) platform: hTCBmsm8974
(bootloader) modelid: 0P6B10000
(bootloader) cidnum: ORANG001
(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
all: Done!
finished. total time: 0.257s
Its a UK phone, locked to the EE (orange) network. I've tried various zip files on the SDCard to do the factory reset but it normally comes back with FAILED.
Can someone, anyone, help get the orignal stock ROM and what I need to do to get it to work....... its annoying that HTC didn't reflash the rom on the phone and they arent answering phones or email or their "live chat"
thank you in advanced.
Pete
Petesrepairs said:
Its a UK phone, locked to the EE (orange) network. I've tried various zip files on the SDCard to do the factory reset but it normally comes back with FAILED.
Click to expand...
Click to collapse
One thing you should understand, the term "factory reset" as done in Settings or stock recovery, is a misnomer. All it does is wipe user data. It doesn't restore or affect the software in any way.
By "various zip files" I believe you mean RUU. But you can only run RUUs with the proper version number, and for your CID. Without nowing what zips your tried to run (full file name and/or version number) or what error messages you got, I can't say for sure why they failed.
I don't think your version has RUUs, but if it did, RUU for version 6.12.61.4 is what you need.
Otherwise, you may need to unlock the bootloader, flash custom recovery, and install the stock nandroid 6.12.61.4 from the following thread (with more instruction on how to do so): http://forum.xda-developers.com/htc-one-m8/help/tutorial-how-to-stock-stock-twrp-t3086860
---------- Post added at 01:14 PM ---------- Previous post was at 01:12 PM ----------
Petesrepairs said:
So I got in to the HBoot menu and that just goes round in circles.
Click to expand...
Click to collapse
Meaning it won't stay in fastboot mode (reboots)? If so, that can be a problem.
If so, are there any messages on the screen about trying to install a file, before it reboots?
I'm at my wits end trying to root my wife's HTC One M8 - followed a guide but just hit problems at every step.
AAANYWAY, finally unlocked the thing (haven't done S-off), and confirmed it's rooted through root checker. Been trying to install Cyanogenmod, but I just get Error 7 in TWRP. Nothing seems to fix that.....got fed up and downloaded Slimrom instead. Eventually it stopped giving Error 7 for that when installing through TWRP and successfully installed. Rebooted and.....oh, I'm still on the stock ROM.
Okay, any ideas on what happened there? I haven't even had any luck in google.
did you factory reset before flashing it ?? And did you allow twrp to make modifications? ThIs might help you
Roobwz said:
did you factory reset before flashing it ?? And did you allow twrp to make modifications? ThIs might help you
Click to expand...
Click to collapse
Yeah I did factory reset. When you say Allow TWRP to make modifications, how do you mean?
CapnBloodbeard said:
Yeah I did factory reset. When you say Allow TWRP to make modifications, how do you mean?
Click to expand...
Click to collapse
When you boot twrp for the first time you get a popup asking if you want to allow twrp to make system modifications. If you declined it, then your system isnt writable meaning you cant flash cm13. Try looking in the settings of twrp and im sure youll find it.
Make sure your firmware is up to date, and TWRP is current version (TWRP 3.0).
Do fastboot getvar all, and post the results (delete IMEI and serial number before posting) so we can look at your firmware version, hboot, etc.
redpoint73 said:
Make sure your firmware is up to date, and TWRP is current version (TWRP 3.0).
Do fastboot getvar all, and post the results (delete IMEI and serial number before posting) so we can look at your firmware version, hboot, etc.
Click to expand...
Click to collapse
It's TWRP 3.0
c:\miniadb_m8>fastboot getvar all
(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.841.4
(bootloader) version-misc: PVT SHIP S-ON
(bootloader) serialno: XXXXXXXXXXXXXX
(bootloader) imei: XXXXXXXXXXXXX
(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: 76df2b54
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.031s
Nothing in TWRP to change the settings to enable it to make modifications