Soft Bricked One M8 (AT&T) - One (M8) Q&A, Help & Troubleshooting

I soft bricked my M8 a while back, and I'm stuck on Paranoid Android 4.5. I'd like to get on lollipop, but I don't know how to get lollipop without getting onto my stock firmware backup which got deleted when I soft bricked it. I've tried sunshine, but it says it needs a near stock sense rom, which I tried and it didn't work.
Got any ideas?

geossparta said:
I soft bricked my M8 a while back, and I'm stuck on Paranoid Android 4.5. I'd like to get on lollipop, but I don't know how to get lollipop without getting onto my stock firmware backup which got deleted when I soft bricked it. I've tried sunshine, but it says it needs a near stock sense rom, which I tried and it didn't work.
Got any ideas?
Click to expand...
Click to collapse
Download some stock based sense rom like Skydragon(some guys did s-off with skyadragon rom) and give it a try. Backup first so you do not get into some bad situation :good:

geossparta said:
I soft bricked my M8 a while back, and I'm stuck on Paranoid Android 4.5. I'd like to get on lollipop, but I don't know how to get lollipop without getting onto my stock firmware backup which got deleted when I soft bricked it. I've tried sunshine, but it says it needs a near stock sense rom, which I tried and it didn't work.
Got any ideas?
Click to expand...
Click to collapse
There are three ways to update your firmware to Lollipop.
1: Go to this thread for a stock ROM backup and stock recovery, and update via the OTAs offered by your carrier.
2: Backup your data with TWRP and save it to extSD, run the appropriate RUU for your device, re-flash TWRP and restore data.
3: Flash the MaximusHD ROM (use the version that matches your current firmware, not the newest) and use Sunshine to achieve S-Off, then flash a modified Lollipop firmware package. (The best option IMO) Current and previous versions of MaximusHD can be found here.

geossparta said:
I soft bricked my M8 a while back, and I'm stuck on Paranoid Android 4.5. I'd like to get on lollipop, but I don't know how to get lollipop without getting onto my stock firmware backup which got deleted when I soft bricked it. I've tried sunshine, but it says it needs a near stock sense rom, which I tried and it didn't work.
Got any ideas?
Click to expand...
Click to collapse
Your device is AT&T
Read this : http://forum.xda-developers.com/showthread.php?t=2751432
and install 4.28.502.2 RUU
Relock bootloader before you run the RUU

Related

[Q] Bell Desire Z stok Rom

Hi
I'm desperately looking for any Bell mobility stock 1.34.666.5 or Over.
The camera button is not working so I sent my phone to repair but they send it back because I do not have the right rom that was provided with my phone. I was able to unroot and put back 1.34.666.1 (the only one that is available it seems) but the technical support told me that my phone shipped with 1.34.666.5 and that they can't do anything unless I'm putting back this rom.
I tried getting OTA updates for 1.34.666.1 but it's not available. Minimum rom # to get OTA updates have to be 1.34.666.5
I'm screwed.
Regards
I have a nandroid backup of the stock ROM...it's rooted though.
Will I be able to flash using Clockwork Recovery? I can manage to remove root after flashing, I think.
Yes, flashable via Clockwork.
I'll let you know when I have it uploaded.
...and it's up.
https://xda:[email protected]/_xda/Bell.DZ.Stock.ROOTED.7z
Some notes:
- I only included the system and boot portions of the nandroid backup due to privacy concerns
- As such, you should do a system and boot restore (after a full wipe, of course) under "Advanced Restore"
- As mentioned earlier, this is rooted (so you'll need to unroot)
Hope this helps. Let us know how it goes.
Good news, I have been able to return to stock 1.34.666.5. Thank you very much for your backup.
I was thinking going unrooted was to be easy but i'm a little bit stuck.
How can I unroot and put back stock bootloader without flashing a new rom.
If I have to flash a new rom, is there a way to build one based on the backup you provided?
I've look at software update and there's an OTA update available for my phone. I tried to install but because I do not have the right bootloader (I think that's the problem) I'm unable to do the OTA update.
Thanks.
Tonkadan said:
Good news, I have been able to return to stock 1.34.666.5. Thank you very much for your backup.
I was thinking going unrooted was to be easy but i'm a little bit stuck.
How can I unroot and put back stock bootloader without flashing a new rom.
If I have to flash a new rom, is there a way to build one based on the backup you provided?
I've look at software update and there's an OTA update available for my phone. I tried to install but because I do not have the right bootloader (I think that's the problem) I'm unable to do the OTA update.
Thanks.
Click to expand...
Click to collapse
That's good to hear. I'd recommend making your own nandroid backup immediately.
As for the bootloader, you're sure you flashed the ENG HBOOT during the rooting process? If that's the case, I'm not sure where you can find the stock HBOOT...
Yes, I installed the Eng HBoot.
I'm trying now renaming the OTA update.zip, put on the root of sdcard and make recovery to install that update but I got an error about getprop CID?? and the update failed...
Still looking for a solution.
How did you make out Tonkadan? I'm in the same boat. I heard that if you did apply this update that you would not be able to root your phone anymore.
I' still rooted. I'm unable to go back to stock. I'm using cyanogenmod 7 for now but would really want to go back to stock if somone have the official Bell rom over 1.34.666.5.
... Or any way to get OTA updates for RUU 1.34.666.1 that is available on shippedroms.com

[Q] And the troubles begin again... Help! (stuck at boot)

I was trying to update my firmware in the hope of using one of the custom roms available, and my M8 is now stuck on the boot screen and will not go further. Here is what I did:
Currently have a GPE M8. It is S-Off, SuperCID, Unlocked, and converted to T-Mobile (Sense) stock rom.
Was on 1.54.401.5 firmware attempting to update to a 2.22.xxx firmware.
The exact process I used was:
Boot into fastboot
fastboot oem rebootRUU
fastboot flash zip firmware.zip twice (successful after 2nd time)
fastboot reboot
After this, it will not go past the default boot screen.
I then tried to revert back to 1.54.401.5 firmware using the same process. This time, it will reboot once after the stock boot screen and go into recovery. Still unable to get back to the OS.
What am I doing wrong and how do I get out of it? :crying:
[edit] I tried to install a newer firmware again, as well as a couple of different roms. No luck, still getting stuck at the boot screen or automatically rebooting into recovery. Had to resort to using the T-Mobile RUU to get back a working phone. I still don't know what went wrong with my attempt at trying to install a new firmware or rom. [/edit]
The firmware includes an incompatible kernel, just flash a different kernel or re-install the rom and you should be alright
thom109 said:
The firmware includes an incompatible kernel, just flash a different kernel or re-install the rom and you should be alright
Click to expand...
Click to collapse
I did try to install a couple different roms after installing the firmware, but either the rom fails to install, or even if it appears to install, it still gets stuck at the white boot screen.
I also don't understand how the kernal can be incompatible. In all the threads I've gone through of the custom roms (mainly ARHD), it's always the same story. "Just flash the 2.22.xxxx firmware and you'll be fine". In the threads specifically related to the updated roms, it's the same thing, just flash and go, regardless if you are on stock and some other rom. I, and only a few others, seem to have no luck actually flashing the 2.22.xxxx firmware.
Mpegger said:
I did try to install a could different roms after installing the firmware, but either the rom fails to install, or even if it appears to install, it still gets stuck at the white boot screen.
I also don't understand how the kernal can be incompatible. In all the threads I've gone through of the custom roms (mainly ARHD), it's always the same story. "Just flash the 2.22.xxxx firmware and you'll be fine". In the threads specifically related to the updated roms, it's the same thing, just flash and go, regardless if you are on stock and some other rom. I, and only a few others, seem to have no luck actually flashing the 2.22.xxxx firmware.
Click to expand...
Click to collapse
hmm weird, I have no idea what's going on here ... I had some issues after flashing firmware but new kernel and it worked just fine.
Maybe something in this thread could help you? http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
thom109 said:
hmm weird, I have no idea what's going on here ... I had some issues after flashing firmware but new kernel and it worked just fine.
Maybe something in this thread could help you? http://forum.xda-developers.com/htc-one-m8/development/firmware-flashing-panic-attacks-t2824048
Click to expand...
Click to collapse
Tried that too, same issue. Tried with the phone locked and unlocked, manually with fastboot and automatically via external SDcard (as in that thread), installed SkyDragon, ARHD, and stock after installing the firmware, and it still fails with the same issue. Even trying to revert back to the current firmware after trying to install 2.22.xxx results in the same problem, and the only way to fix it is with the RUU.
I think what I'll try next is to install the rom first, then try to install the firmware. Maybe in that order it will work. But it still doesn't make much sense that I can't install the newer firmware when so many others have had no problems.
Mpegger said:
Tried that too, same issue. Tried with the phone locked and unlocked, manually with fastboot and automatically via external SDcard (as in that thread), installed SkyDragon, ARHD, and stock after installing the firmware, and it still fails with the same issue. Even trying to revert back to the current firmware after trying to install 2.22.xxx results in the same problem, and the only way to fix it is with the RUU.
I think what I'll try next is to install the rom first, then try to install the firmware. Maybe in that order it will work. But it still doesn't make much sense that I can't install the newer firmware when so many others have had no problems.
Click to expand...
Click to collapse
always install rom first then firmware

[Q] Going back to Sense

Hey guys. I've been working on getting my GPE converted device back to sense but I've hit a road block. First off, this device was upgraded to 5.0 while it was a GPE device and all the tutorials I've seen are for devices on KitKat. The point I'm stuck at is where the device was supposed to boot back into the stock rom it didn't. I went ahead and flashed the TWRP recovery to it but now it won't go into trwp it just sits at entering recovery. What went wrong here? I'm trying to install Skydragon ultimately.
UPDATE: I managed to Flash an older version of TWRP and got it booted. I installed SkyDragon Lollipop Sense Rom but I am sitting at the white HTC screen. Just really stuck at this point.
gigamchz said:
Hey guys. I've been working on getting my GPE converted device back to sense but I've hit a road block. First off, this device was upgraded to 5.0 while it was a GPE device and all the tutorials I've seen are for devices on KitKat. The point I'm stuck at is where the device was supposed to boot back into the stock rom it didn't. I went ahead and flashed the TWRP recovery to it but now it won't go into trwp it just sits at entering recovery. What went wrong here? I'm trying to install Skydragon ultimately.
UPDATE: I managed to Flash an older version of TWRP and got it booted. I installed SkyDragon Lollipop Sense Rom but I am sitting at the white HTC screen. Just really stuck at this point.
Click to expand...
Click to collapse
How did you try to convert back. I can help u I just need to know what you did step by step cause I guessing it wasn't done rt.
Tigerstown said:
How did you try to convert back. I can help u I just need to know what you did step by step cause I guessing it wasn't done rt.
Click to expand...
Click to collapse
I used this guide: http://forum.xda-developers.com/showthread.php?t=2733523 to go back but I never was successful. I reverted back to the GPE RUU and then flashed TWRP which I then used to flash the custom M8-GPE rom on the forums. it runs smooth and has sense camera and things so i'm wondering if it's worth going back to stock and installing a sense based lollipop rom. I'd still really like the ability to go back if need be.
gigamchz said:
I used this guide: http://forum.xda-developers.com/showthread.php?t=2733523 to go back but I never was successful. I reverted back to the GPE RUU and then flashed TWRP which I then used to flash the custom M8-GPE rom on the forums. it runs smooth and has sense camera and things so i'm wondering if it's worth going back to stock and installing a sense based lollipop rom. I'd still really like the ability to go back if need be.
Click to expand...
Click to collapse
Is worth it if you want to be running sense ...So if you decide to convert back just hmu an we an convert you back.

Does installing a TWRP Backup also affect phone Firmware?

Hello guys,
following situation:
Long time I had a 4.4.something Rom installed. Before I flashed a custom Lollipop rom, I followed the advice to just go back to stock and let it update to Lollipop so that the firmware will be updated accordingly and I won't run into problems when flashing a Lollipop Custom Rom. Everything worked fine. Now I had to send my phone to HTC for display repair and just to make sure they won't nag about the custom Rom I reflashed some older stock rom via TWRP backup I found here, I think it was a 4.0 or so. The question is, does this also affect my phones firmware or is it still on the current newest level? So when I get it back, would I need to update to stock Lollipop again before flashing a custom rom or can I go for it straight away?
fBx said:
Hello guys,
following situation:
Long time I had a 4.4.something Rom installed. Before I flashed a custom Lollipop rom, I followed the advice to just go back to stock and let it update to Lollipop so that the firmware will be updated accordingly and I won't run into problems when flashing a Lollipop Custom Rom. Everything worked fine. Now I had to send my phone to HTC for display repair and just to make sure they won't nag about the custom Rom I reflashed some older stock rom via TWRP backup I found here, I think it was a 4.0 or so. The question is, does this also affect my phones firmware or is it still on the current newest level? So when I get it back, would I need to update to stock Lollipop again before flashing a custom rom or can I go for it straight away?
Click to expand...
Click to collapse
It won't affect your firmware.
Okay thanks, so Firmware should still be up to date and I can flash a Lollipop Custom Rom. I don't know what they do at HTC repair, if they only reset it or if they also update it, well I'll see.

HTC ONE M8 5.0.1- Failed To Flash Stock Recovery

Stock Recovery
Dear friends,
I have an HTC one M8
Android-5.0.1
Network Provider- Three Republic of Ireland
Bootloader status- Unlocked
S-ON
CID-H3G__001
I am trying to do an OTA-4.25.771.6
I was on TWRP Custom Recovery
I tried to reflash to stock recovery to do the OTA and unsuccessfully tried the below mentioned Stock recoveries from XDA developers.
stock+recovery+1.54.771.5+recovery.img
and
stock+recovery+1.12.771+recovery.img
I see a Red triangle with an exclamation mark when I try to run the Stock Recovery.
Can anybody suggest any solutions
Many Thanks
sijuiv said:
I have an HTC one M8
Android-5.0.1
stock+recovery+1.54.771.5+recovery.img
and
stock+recovery+1.12.771+recovery.img
Click to expand...
Click to collapse
Those recoveries are way too old to work, it needs to match your current firmware (hboot, etc.), which sounds like Lollipop Android 5.0 (those are Kitkat Android 4.4.2 recoveries).
I assume you have the stock Lollipop ROM? Since you need the stock ROM (in addition to stock recovery) to OTA. And trying to install the recent Stagefright OTA?
sijuiv said:
CID-H3G__001
I am trying to do an OTA-4.25.771.6
I was on TWRP Custom Recovery
I tried to reflash to stock recovery to do the OTA and unsuccessfully
Click to expand...
Click to collapse
You need to install 4.20.771.2 stock recovery or the one that from OTA 4.25.771.6.
And make sure you have a non-rooted stock 4.20.771.2 ROM running on your device
redpoint73 said:
Those recoveries are way too old to work, it needs to match your current firmware (hboot, etc.), which sounds like Lollipop Android 5.0 (those are Kitkat Android 4.4.2 recoveries).
I assume you have the stock Lollipop ROM? Since you need the stock ROM (in addition to stock recovery) to OTA. And trying to install the recent Stagefright OTA?
Click to expand...
Click to collapse
dEAR rEDPOINT73
mANY tHANKS FOR THE REPLY,
I am trying to install the recent 4.25.771.6 OTA.
I am on a stock rom.
Can you please give me a link to the Stock Recovery I should flash.
Regards
ckpv5 said:
You need to install 4.20.771.2 stock recovery or the one that from OTA 4.25.771.6.
And make sure you have a non-rooted stock 4.20.771.2 ROM running on your device
Click to expand...
Click to collapse
Dear CKP5
Many thanks for the reply.
Do I need to unroot my Device which is already on Stock Rom to do an OTA.I have'nt messed with any default apps that came with the device. I am already receiving the notifications to do an OTA on the device.
I could'nt find the stock recovery.Can you please give me a link to the same.
Regards
Definitely you need a non-rooted stock ROM.
If you unroot your ROM, most likely it won't work either as the root itself change some files.
Restore the system part only from a non-rooted backup to avoid problem. You can keep your data.
Install stock recovery then do OTA
Check link in my signature for all files that you need.
And FYI .. this OTA will upgrade your system to 5.0.2 but unfortunately the stagefright fix only fix 6/7 vulnerabilities

Categories

Resources