I've been doing the custom ROM game for 13 years and somehow tonight I've managed to brick my phone for the first time ever.
Here's the breakdown.
Started with my S-OFF, SuperCID M8 Unlocked WWE which was running the Skydragon 6.0 GPE ROM with associated firmware.
I decided I wanted to try the latest 6.0 Sense rom, so downloaded the 6.0 Firmware zip and Maximus 12 ROM.
From a bit of reading I saw that to get my Sense partition back and be able to install the relevant ROM to go with it, I'd need to flash the Sense firmware, which I did, and that seemed to go OK.
I rebooted into TWRP and went to do a wipe, and was greeted with the following error:
"could not mount /data and unable to find crypto footer"
Followed by lots of
"Unable to mount /data" error messages.
If I leave the phone to boot, it asks me for my password and says that the data is no longer there and I need to reset, but I'm hesitant to do that as I expect I would be left completely shafted then.
I tried reflashing the GPE Firmware but it looks like the damage has been done.
Desperately need some help in getting myself back to working. Any ideas please?
You missed a step.
After firmware is flashed and twrp is installed, you need to format data (not wipe data).
Further update. I followed the back to sense guide, got to the point of re-flashing TWRP but now when I try to enter recovery from the bootloader it goes to the screen saying "entering recovery..." and then reboots, but there's no ROM to boot into so it tries to reboot into recovery again, and fails etc...
Flashed the 6.0 Sense firmware again, managed to install and get into TWRP. Now installing MaximusHD 12...fingers crossed...
ckpv5 said:
You missed a step.
After firmware is flashed and twrp is installed, you need to format data (not wipe data).
Click to expand...
Click to collapse
Hmm, maybe I made this all way too complicated for myself! At the uncomfortably long stage of first boot. Hopefully it will make it through...
It worked. Running fine now. I'll keep the format idea in mind if there's ever a next time
Sent from my HTC One_M8 using Tapatalk
Related
help! lol
my dilemma, i updated to 4.4.3, rooted, created a nandroid backup.
then i installed viperone 2.5
all going well till phone stopped sending texts (ee update fault, common fault)
after checking solutions all say factory reset, did that, phone booted, but i couldnt log into google, kept saying could not connect to servers
thought ive had enough, restore my nand, and now its stuck on load screen, been left for 15 mins and no joy, i can still get into twrp but im at a loss at what i can do.
twrp wont let me mount internal storage so i can send another backup, only mounts sd card
s-on so limited options
houston33 said:
help! lol
my dilemma, i updated to 4.4.3, rooted, created a nandroid backup.
then i installed viperone 2.5
all going well till phone stopped sending texts (ee update fault, common fault)
after checking solutions all say factory reset, did that, phone booted, but i couldnt log into google, kept saying could not connect to servers
thought ive had enough, restore my nand, and now its stuck on load screen, been left for 15 mins and no joy, i can still get into twrp but im at a loss at what i can do.
twrp wont let me mount internal storage so i can send another backup, only mounts sd card
s-on so limited options
Click to expand...
Click to collapse
If you can get into recovery, you can get into your bootloader. Flash a new ROM using ADB.
Also, only factory reset as a last resort. There's usually a way to fix stuff without resorting to that.
xunholyx said:
If you can get into recovery, you can get into your bootloader. Flash a new ROM using ADB.
Also, only factory reset as a last resort. There's usually a way to fix stuff without resorting to that.
Click to expand...
Click to collapse
i thought flashing a new rom on the m8 required the firmware setup?
so i can just reinstall viperone 2.5 again?
408
so from where i am now i can just go to twrp and install android rev 21? or do i have to use adb sideload?
is 21 even compatible?
i swore i wasnt gonna mess on with this phone.........
houston33 said:
i thought flashing a new rom on the m8 required the firmware setup?
so i can just reinstall viperone 2.5 again?
Click to expand...
Click to collapse
You sure can. The newer firmware is needed for 4.4.4 ROMs. If you had 2.5, reflash it. It will work with the newest firmware as well. Just not the old stuff.
Here's a pointer: A dirty flash of the ROM you are currently running will reset your tweaks, and often fix problems you are having. When I start having glitches, I first reboot. If that didn't work; and I can't find a solution on XDA easily, I reflash my ROM; the dirty way. It really does help to clear up stuff, especially if you are using themes and tweaks.
Sadly didn't work.
Will have to use one of the stock na droid backups from the collection on here once the thread is up and running again
How do I access phone memory to copy the backup over? I only have boot loader and twrp
houston33 said:
Sadly didn't work.
Will have to use one of the stock na droid backups from the collection on here once the thread is up and running again
How do I access phone memory to copy the backup over? I only have boot loader and twrp
Click to expand...
Click to collapse
In TWRP, you can manage files easily.
Click advanced > file manager
There you can copy files, move them and change permissions. Plus deleting and renaming them.
Hi,
I'm having some issues with updating CM so I tried to do it via TWRP instead but it cannot mount E: therfor cannot see my internal storage. I cannot wipe anything but fastboot seems to work but I have no used it apart from rooting my phone.
Could someone help me to fix this, I dont care if i wipe my phone to fix this.
Thanks.
Seeing a lot of this: http://i.imgur.com/CRiJdKY.png
I have the same issue. If it is the same issue, the problem is that TWRP thinks Data is encrypted. In my case, it's not and I have never attempted to do so, but following the flashing of any 5.1 ROM (GPE or AOSP-based) TWRP gets this strange idea Data is encrypted.
The solution is to get the RUU, which will wipe your phone. XDA has one for Verizon. Not sure about the others, but they most likely do. The RUU is a zip you rename and stick on your SD card (root directory) and it will automatically flash. Won't wipe the SD card though. It'll leave you stock and rooted. Then you just fastboot oem flash the TWRP recovery (there's a special one that can be flashed via fastboot) and then you can flash whatever, but flashing 5.1 anything will put you right back in the same situation.
You CAN flash 5.1 ROMs, but you can only do so once and then you have to stay there. You won't be able to update the ROM, or flash another 5.1 ROM, unless you wanna RUU first, then re-fastboot flash TWRP, and then flash the update.
It'll probably resolve itself in August when 5.1 comes officially to the M8 and more people start having this problem. I suspect it's a TWRP thing, but I think TWRP is the only recovery we can use. Philz Touch (CWM fork) hasn't been updated in about a year, so I wouldn't trust it to flash newer ROMs. (Generally, I don't trust recoveries that came out before the Android version of the ROM I'm flashing.) And CWM doesn't seem to support anything after ~2013, so I'm not sure what's up with them. But I like TWRP, it looks nice, and before 5.1, it's never done me wrong. I'm not 100% sure it's doing me wrong now, but it seems to be at fault, and there have been a few times, especially with Lollipop, where you have to use a certain version or higher or you run into a lot of red text.
Helloes ^^
I was trying to root HTC One M8 following a guide. I managed to unlock the bootloader and install TWRP 2.7.0.2 but I accidentally deleted the system partition :SS I hope I left everything else intact..
I downloaded OTA_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_R-4.16.401.13 and tried flashing it but Im getting
mount failed to mount /dev/block/platform/msm_sdcc.1/by-name/userdata
Click to expand...
Click to collapse
Package expects build fingerprint of htc/htc_europe/htc_m8:5.0.1./LRX22C/448934. 13:user/release-keys...
Click to expand...
Click to collapse
I also downloaded RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4 and tried to update but it fails with error 155(I tried locking the bootloader and running it again but it still gives me the same error
My bootloader is unlocked atm and S-on...
Is it possible to recover the os in any way?
------
After trying to flash like 5 roms flashing InsertCoin worked somehow...
Qitsch said:
Helloes ^^
I was trying to root HTC One M8 following a guide. I managed to unlock the bootloader and install TWRP 2.7.0.2 but I accidentally deleted the system partition :SS
Click to expand...
Click to collapse
Why did you flash such an old version TWRP? That one is from about 3 years ago, and will cause lots of problems!
Couple simple rules to live by, when modding these phones:
1) Do not wipe things in TWRP willy-nilly, without knowing what they are, or what the result will be. The option to wipe "system" is in the Advance wipe section. It's called "Advanced" for a reason. That alone would have been a warning to be careful, and not mess with things, unless you know what you are doing. It also clearly says in TWRP wipe screen, that most of the time, the default wipe (cache, Dalvik/ART and data) is all you ever need. It says that for a reason.
2) Right after you install TWRP, and before messing around with anything, you should make a TWRP backup of your current stock ROM. Definitely do that, before trying to flash root, ROMs, or any other mods. That way, if anything goes wrong (or you simply screw up, and wipe system) you have a backup, that you can easily restore.
Qitsch said:
I downloaded OTA_M8_UL_M60_SENSE70_MR_HTC_Europe_6.12.401.4_R-4.16.401.13 and tried flashing it but Im getting
Click to expand...
Click to collapse
In general, you should never flash a file named "OTA" unless you know exactly what you are doing. The requirements for an OTA on this device are steep:
a) Must currently have the version number directly before the OTA number (you can't skip or flash the same number OTA)
b) Must have stock recovery installed (not TWRP)
c) Must match your version (CID, MID). Do you have the Euro version? You never stated this info.
Qitsch said:
I also downloaded RUU_M8_UL_M60_SENSE70_MR_BrightstarUS_WWE_6.12.1540.4 and tried to update but it fails with error 155(I tried locking the bootloader and running it again but it still gives me the same error
Click to expand...
Click to collapse
This RUU is only for the US Developer's Edition version M8. Will not work on any other version.
Even if you had the US Dev Ed (which is unlikely) this RUU would require the firmware being flashed, before the RUU will install (thus, Error 155).
In short, it seems like you are just guessing at solutions. Not a good idea.
Hi! I was playing around with my phone and I might have wrecked it somehow. My twrp is password protected, which I have no clue what it is, and therefore can't install roms or restore backups. The phone is not booting into the rom no matter what I do either. Twrp boots everytime I power on my device.
Please help!
Flash stock image and stock recovery (and wipe cache). Then after if it will boot into OOS recovery just click "reboot now".
Were you able to get into twrp? The password is usually the one you set up for your login to andriod system.
If you can get in, then no need worry. i had exact experience last week. Just remember to clear both cache, system, and data. Just keep internal storage intact. Then try to flash stock rom without rooting.
See if you can get it.
The cause of having this issue may due to flashing rom without uninstallng magisk first.
Good luck.
stellarroar said:
Hi! I was playing around with my phone and I might have wrecked it somehow. My twrp is password protected, which I have no clue what it is, and therefore can't install roms or restore backups. The phone is not booting into the rom no matter what I do either. Twrp boots everytime I power on my device.
Please help!
Click to expand...
Click to collapse
Siljorfag said:
Flash stock image and stock recovery (and wipe cache). Then after if it will boot into OOS recovery just click "reboot now".
Click to expand...
Click to collapse
Stock image is the stock OOS rom right?
lyrebird said:
Were you able to get into twrp? The password is usually the one you set up for your login to andriod system.
If you can get in, then no need worry. i had exact experience last week. Just remember to clear both cache, system, and data. Just keep internal storage intact. Then try to flash stock rom without rooting.
See if you can get it.
The cause of having this issue may due to flashing rom without uninstallng magisk first.
Good luck.
Click to expand...
Click to collapse
The twrp password is known only to god because I've tried every pin/password I have ever used on all roms I've tried so far but none of them work. Which is why I can't flash any rom as my storage is encrypted. Most of the times I have a pattern lock set but that can't be mapped to a password can it?
I decided to start from scratch and installed stock recovery and then adb sideloaded first the stock Nougat OOS and then later 5.1.1 stock OOS, but both times in vain. Both times the phone gets stuck on the startup setup saying "just a sec", endlessly. On the very first activity it shows a message, that disappears in a few seconds, saying "Disabled or missing download manager. Can't download voice pack". How can I fix this? Help please.
stellarroar said:
I decided to start from scratch and installed stock recovery and then adb sideloaded first the stock Nougat OOS and then later 5.1.1 stock OOS, but both times in vain. Both times the phone gets stuck on the startup setup saying "just a sec", endlessly. On the very first activity it shows a message, that disappears in a few seconds, saying "Disabled or missing download manager. Can't download voice pack". How can I fix this? Help please.
Click to expand...
Click to collapse
I would fully wipe, then format, but make sure you have the contents from your storage backed up externally. This is the only way to insure there's nothing left over from previous flashes. And then sideload 5.1.1-full update, you should be good from there. I had the same issue after flashing a OOS custom build.
Sent from my ONEPLUS A5010 using XDA Labs
blas4me said:
I would fully wipe, then format, but make sure you have the contents from your storage backed up externally. This is the only way to insure there's nothing left over from previous flashes. And then sideload 5.1.1-full update, you should be good from there. I had the same issue after flashing a OOS custom build.
Sent from my ONEPLUS A5010 using XDA Labs
Click to expand...
Click to collapse
Formatting everything did the trick. I thought sideloading OOS would implicitly do that but I was wrong. Thanks a lot man! Now is there any way I can keep my device unencrypted going ahead? I don't want Twrp to ask me for a password when I'm booting it.
Earlier today I tried to reboot my BND-L24 into TWRP, but I got seriously stuck and have been unable to get unstuck ever since.
TWRP will not load. It starts to load and then gets stuck on the splash screen.
I have tried to wipe from (standard) recovery, but that doesn't work either.
I have tried to install several different TWRPs (fastboot seems to be working ok).
If I could just get into TWRP I should be able to restore the System partition. I had previously installed the Morfuz kernel, but I would have to be able to get into TWRP to restore the original kernel.
I'm seriously stuck. Any advice??
Thanks!
I dont understand. What do you mean by "seriously stuck?"
Use these TWRPs....
https://drive.google.com/open?id=18uHjW73Th8iYKIs5m_QgwleMIOjsZd7S
RECOVERY TWRP OREO 3.2.1
the file is automated. http://zipansion.com/2t6QB
https://forum.xda-developers.com/devdb/project/dl/?id=28883
TWRP will not load - it is stuck at the flash screen. I've tried several variants of TWRP and will try yours as well.
I've flashed the first one before without any luck. The second failed with "FAILED (remote: partition length get error). Didn't matter whether I flashed to recover-ramdisk or recovery, same error both ways.
egalambos said:
I've flashed the first one before without any luck. The second failed with "FAILED (remote: partition length get error). Didn't matter whether I flashed to recover-ramdisk or recovery, same error both ways.
Click to expand...
Click to collapse
it is recovery_ramdisk... that is the partition, not "recover-ramdisk" or "recovery"
I finally got into TWRP!!! Progress!!
I thought I had a good System partition backup, but apparently I don't.
How can I use TWRP to install a good System.img file that I do have?
egalambos said:
I finally got into TWRP!!! Progress!!
I thought I had a good System partition backup, but apparently I don't.
How can I use TWRP to install a good System.img file that I do have?
Click to expand...
Click to collapse
you should always use fastboot to flash .img files. at this point, i suggest you wipe internal storage, cache, dalvik and art cache, system, and data. then flash hurupdater and get back to stock.
I did that, except that I left the Data and the internal partition alone and it worked. I'm in the process of re-installing Magisk, etc., but, from what I can see, everything seems to be pretty much back to normal.
Thanks for the help! It was unbelievably frustrating. Can't believe I mixed up a dash with an underscore!
PS Do you have any idea why I was unable to do a System Update before I re-installed TWRP? I believe I was about as stock as stock can be at that point!
egalambos said:
I did that, except that I left the Data and the internal partition alone and it worked. I'm in the process of re-installing Magisk, etc., but, from what I can see, everything seems to be pretty much back to normal.
Thanks for the help! It was unbelievably frustrating. Can't believe I mixed up a dash with an underscore!
PS Do you have any idea why I was unable to do a System Update before I re-installed TWRP? I believe I was about as stock as stock can be at that point!
Click to expand...
Click to collapse
probably because the bootloader was unlocked. one way to install updates manually is using firmware finder app, if the update is approved.