[Q] Soft Brick can't mount /data - Verizon LG G2

Had C-ROM installed, was going to install AOKP. I wiped, then installed the AOKP ROM, followed by GAPPS. It wouldn't go past LG screen, so I rebooted into recovery and now it won't let me do anything because I can't mount /data
I can boot into TWRP, but I can't flash or restore anything...
How can I install a fresh ROM, revert to one of my backups, or get back to stock at least. I saw this thread but I wasn't sure if that would fix my issue since it wasn't caused by accepting an OTA.
Any other info needed?

Not sure how exactly I was able to resolve this, but I have.
Through a series of reboots into recovery, /data eventually was mounted and I was able to complete a wipe and reinstall.

Related

LG optimus 2x bootloop after failed cyanogen mod

Hello!
Today, i decided to install cyanogemmod on my 2x. So i downloaded ROM manager and downloaded cyanogenmod. everything went fine until i was going to boot for the first time. I got into a bootloop. so i tried taking out the battery and all that stuff but it still would't work. So i tried to recover the phone. I recovered it to a month old backup (I could not find the one i made in ROM manager before i installed cyanogenmod) The recovery went fine. But, when i rebooted it got into a loop on the lg logo! (the one without the loading bar) it would just load the lg logo, be there for like 10sec, then it would do the same. I tried recovering one more time, but it didn't work. The same thing happend. What should i do? :S Should i wipe data/factory reset?
EDIT: My phone was on android 2.3.4 before i download cyanogenmod.
BTW before i installed cyanogenmod, i forgot to clear cache and data. I was in a hurry so i did't notice the screen popping up, I automatically pressed "ok" without selecting anything.
Thanks for the help
- Kashif
Different partitions... Look for something called backtoext3 in the dev section (or somewhere else) The problem is that when you flash a custom rom like CM you convert your filesystem to EXT4, while stock is EXT3.
So basically what you have to do is:
1) Reboot into recovery
2) Wipe everything
3) Flash Backtoext3 zip
4) Restore Nandroid.
This should work. this will take you back to stock.
So i have to restart the phone, Choose wipe data/factory reset, then flash backtoext3 (how do i do it? lol) then restore nandroid (the backup i just tried to restore twice?)
kashi169 said:
So i have to restart the phone, Choose wipe data/factory reset, then flash backtoext3 (how do i do it? lol) then restore nandroid (the backup i just tried to restore twice?)
Click to expand...
Click to collapse
Yes
Flashing backtoext3 is just flashing the zip file you put on the sd card. (and then install zip from SD ) an then restore your nandroid stock backup and you're back on stock.
But you said you wanted to try CM right? In that case, wipe everything (factory reset/data + cache + dalvik) and then flash the CM7 rom and you have CM! Don't worry about backtoext3, your partitions are already on EXT4, because of your prior CM flash.
Ohh! Thanks Can you send the files for cm (2.3.4)? I've found some, but im not sure if my phone is compitable with them :S im really afraid to mess something up again
My. Signature. (CM7 temasek's KANG = the best CM7 at the moment )
I did everything and i got into a bootloop at the skating andriod screen again
OK, restored my phone back... Now it wont connect to the network and the battery has a question mark inside it. It also says the battery level is 999% heelp
Nvm, got my phone back to normal still dont understand why cm wont work...
You need cwm5 to flash cm.
I have a G2x, which is basically the same phone. But anyway, I would recommend nvflashing CWM and not getting it from ROM Manager.
CWM 5.0.2.0 will do just fine, but it is indeed old...
Anyway, are you sure you waited long enough on the CM boot screen? The first boot might take a couple of minutes. (4 or 5)

Weird CWM behaviour

Hello!
Before I want to go on to CWM I want to tell you what happened before.
Yesterday I flashed TWRP recovery which resulted in a really bad situation. I was stuck in recovery. If I pressed reboot it went straigt to recovery again, even if I pulled out the battery. So flashed the stock firmware via the KDZ flashing method and everything worked again.
Then I rooted again, installed CWM, installed CM, installed all my apps (TB backup on PC was quite old),....
So all in all it was a big amount of work and it took me a few hours.
Then everything was working again as it should and I updated all my TB backups and then I wanted to make a Nandroid backup so that I wouldnt have to do all that flashing and installing again.
So I went to recovery--> backup and restore --> backup
But it didnt finish. It always stopped with this error: Error while meaking a backup image of /system!
So i thought maybe I should install everything again, which i did. (I had already made a TB backup of all my apps, so i thought this woulb be done fast)
Well, went to recovery again, did a factory reset, wiped dalvik cache and even formated /system. Then I installed the latest CM + GAPPS and rebooted.
And the first thing i recognized was that the screen popped where it says "android is upgrading". And I wondered even more when I realized that all my apps where stille there. So obviously the factory reset and also format /system didnt work properly.
If I format /system and dont install any ROM then the device doesnt boot (which i guess is the normal behaviour). But what I want to say is that the format works there but if I flash CM afterwards all my apps are still there (despite the fact that i also did a factory reset).
All in all the phone does work normal now, but I'm not able to make a Nandroid backup and I'm really wondering why.
(I also reflashed CWM recovery but that didnt change anything)
I would be glad if s1 could help me.
PS: Could the solution be to flash stock again via KDZ and then do everything from the beginning?
Never heard of anything like this before.
Did you flash the recovery as a .IMG or through Rom manager (I would suggest to flash it with Rom manager).
Try this and report back (maybe your recovery image is damaged or smth.)
Sent from my LG-P880
I have no idea what caused this crazy behavoiur of CWM, but I started over again with flashing kdz and now everything is fine
Maybe your SD card is full. Try deleting a few files from your SD and then do the backup.
Sent from my GT-I9070 using xda premium
I dont have any external sd card and on phone memory there were more than 10GB free space

[Q] Flashed zips don't stick, phone keeps resetting to how it was yesterday morning

So I've got an HTC One on T-Mo. The CM10.1 nightly build (8/1) I had installed worked fine for a while.
Yesterday, it rebooted on its own a few times, and each time, everything I'd done since around 7 AM decided to undo itself. Texts I received went missing, apps un-updated, files on internal storage erased themselves. Every time I reboot the phone, it undoes whatever I've done. Rebooting into recovery deletes whatever zip I meant to flash!
So I already had one of the GE ROMs on internal storage. Thought I'd try flashing that. So I went into CWM, formatted /system and /data, flashed the GE ROM, wiped Dalvik, the whole deal. When I rebooted, I was once again greeted with CM10.1 the way I'd left it yesterday morning.
Restoring from a backup doesn't work either.
Tried to flash TWRP over CWM through ADB, rebooted recovery, and it's still CWM.
I'm at a loss. I can't wipe or flash or put files on my phone. Any ideas?
nickcv said:
So I've got an HTC One on T-Mo. The CM10.1 nightly build (8/1) I had installed worked fine for a while.
Yesterday, it rebooted on its own a few times, and each time, everything I'd done since around 7 AM decided to undo itself. Texts I received went missing, apps un-updated, files on internal storage erased themselves. Every time I reboot the phone, it undoes whatever I've done. Rebooting into recovery deletes whatever zip I meant to flash!
So I already had one of the GE ROMs on internal storage. Thought I'd try flashing that. So I went into CWM, formatted /system and /data, flashed the GE ROM, wiped Dalvik, the whole deal. When I rebooted, I was once again greeted with CM10.1 the way I'd left it yesterday morning.
Restoring from a backup doesn't work either.
Tried to flash TWRP over CWM through ADB, rebooted recovery, and it's still CWM.
I'm at a loss. I can't wipe or flash or put files on my phone. Any ideas?
Click to expand...
Click to collapse
Solved. eMMC isn't writing, warranty replacement incoming.

[Q] Questions before flashing custom ROM

I am planning to flash a custom rom on my phone (for the first time).
Model : Xperia SP(C5302)
Build : 12.1.A.1.205 (Stock) running JB 4.3 with LB
I have rooted my phone using the towelroot method and installed supersu. I have also installed custom recovery from here http://forum.xda-developers.com/showthread.php?t=2649923
I am planning to flash this custom rom http://forum.xda-developers.com/xperia-sp/development/cyanogenmod-11-locked-bootloader-users-t2868398
So I have a few questions that I am not clear about(even after searching the forums). And sorry if they are dumb. I really want to understand as much as possible before flashing roms.:fingers-crossed:
1. After reading the thread of my recovery, from what I understand, the recoveries are installed in /system. But on OP of the custom rom, I am about to install, there is an instruction to format /system before flashing the rom. So my question is if I format the /system partition, won’t my recoveries be removed (by the recoveries itself) before I even flash the rom?
2. Also will the recovery still be available to me if say I enter bootloop for some reason during flashing the rom?(asking for the same reason as above that is wiping my /system should also remove my recoveries)
3. Does CM 11 come with any inbuilt custom recovery? If not can I install the one I am already using (assuming installing a custom rom will remove my installed recoveries)?
4. Say I screw up during the flashing procedure. So if I want to rectify this I should first flash the stock .205 ftf, root, install a recovery again and then restore using the nandroid backup. Am I correct?
5. Is it necessary to wipe cache and dalvik cache before flashing rom? I see this instruction in some roms but not in others. And dalvik should be wiped after flashing rom and gapps, right?
6. Should I install supersu again after I flash the rom. I read in an article that it causes problems with CM. As far as I know CM11 comes pre-installed with superuser. But it also supposedly causes some problems.
7. Is it safe to restore user app+data, messages and contacts backed up using Titanium backup on a newly flashed rom? I have seen conflicted views on this.
Click to expand...
Click to collapse
And that’s it for my questions (for now at least... ).
A Big Thanks in advance for all your helpful answers
Prat92 said:
I am planning to flash a custom rom on my phone (for the first time).
Model : Xperia SP(C5302)
Build : 12.1.A.1.205 (Stock) running JB 4.3 with LB
I have rooted my phone using the towelroot method and installed supersu. I have also installed custom recovery from here http://forum.xda-developers.com/showthread.php?t=2649923
I am planning to flash this custom rom http://forum.xda-developers.com/xperia-sp/development/cyanogenmod-11-locked-bootloader-users-t2868398
So I have a few questions that I am not clear about(even after searching the forums). And sorry if they are dumb. I really want to understand as much as possible before flashing roms.:fingers-crossed:
And that’s it for my questions (for now at least... ).
A Big Thanks in advance for all your helpful answers
Click to expand...
Click to collapse
First of all, I am only explaining the one I know about
1. Well, wiping the system will remove the recovery. That's why you'll have to flash the ROM after wiping the system. Do not ever reboot the phone after wiping the system but haven't yet flashed the ROM zip, else you'll have to do more work to flash the Stock ROM. This is due to the fact your phone does not have an OS to boot into! When flashing the ROM zip, the recovery will be automatically installed.
2. This is based on luck, most of time you'll end up unable to boot into anything. A fix is to flash the Stock ROM again.
3. Every ROM has recovery built with it (unless stated otherwise in the thread)! Upon flashing, it will be automatically installed too.
4. The methods you mentioned is correct. However, only restore the nandroid backup if you want to stay on stock. You could always retry to flash the ROM again. Nandroid backup is an image backup of your android. If you restore your nandroid backup, you'll end up with your previous version of android (like the way before you started flashing the ROM)
5. Wiping /cache and dalvik-cache is a really good practise! It doesn't really matter when you will need to wipe them, but personally I wipe them all before flashing the ROM. Wiping /data and performing a factory reset through recovery is recommended if you're coming from a different ROM. That's why backing up user apps through TiB (Titanium Backup) is recommended for you to easily get your installed apps back. Remember, nandroid backup and apps backup from TiB is different to each other.
6. No, this might cause extreme conflicts. No, I am using SuperUser as long as I have used CM. It never fails to give root permission at all despite the hatred I sense in some apps that overly-recommends SuperSU.
7. Of course it is very safe to restore them backups with TiB. However, based on my experience, messages and contacts were unable to be restored due to the difference in ROM version. I don't know if anyone else faces the same problem as mine. As of this, I really recommend your contacts to be synced with Google.
Heads up!
Based on this post, the dev of the ROM you wanted to flash, MrSteve555, recommends PhilZ when flashing the ROM.
TechnoSparks said:
First of all, I am only explaining the one I know about
1. Well, wiping the system will remove the recovery. That's why you'll have to flash the ROM after wiping the system. Do not ever reboot the phone after wiping the system but haven't yet flashed the ROM zip, else you'll have to do more work to flash the Stock ROM. This is due to the fact your phone does not have an OS to boot into! When flashing the ROM zip, the recovery will be automatically installed.
2. This is based on luck, most of time you'll end up unable to boot into anything. A fix is to flash the Stock ROM again.
3. Every ROM has recovery built with it (unless stated otherwise in the thread)! Upon flashing, it will be automatically installed too.
4. The methods you mentioned is correct. However, only restore the nandroid backup if you want to stay on stock. You could always retry to flash the ROM again. Nandroid backup is an image backup of your android. If you restore your nandroid backup, you'll end up with your previous version of android (like the way before you started flashing the ROM)
5. Wiping /cache and dalvik-cache is a really good practise! It doesn't really matter when you will need to wipe them, but personally I wipe them all before flashing the ROM. Wiping /data and performing a factory reset through recovery is recommended if you're coming from a different ROM. That's why backing up user apps through TiB (Titanium Backup) is recommended for you to easily get your installed apps back. Remember, nandroid backup and apps backup from TiB is different to each other.
6. No, this might cause extreme conflicts. No, I am using SuperUser as long as I have used CM. It never fails to give root permission at all despite the hatred I sense in some apps that overly-recommends SuperSU.
7. Of course it is very safe to restore them backups with TiB. However, based on my experience, messages and contacts were unable to be restored due to the difference in ROM version. I don't know if anyone else faces the same problem as mine. As of this, I really recommend your contacts to be synced with Google.
Heads up!
Based on this post, the dev of the ROM you wanted to flash, MrSteve555, recommends PhilZ when flashing the ROM.
Click to expand...
Click to collapse
Thanks for such detailed answers. That cleared most of my doubts
Just some last few questions(promise!)
1. If wiping /system does remove the recovery before I install the rom, how is it possible to access it even to flash the rom? Shouldn't it like just close right when I wipe /system. Or does it not work like that?
2. Just to be sure the nandroid backup I made on my stock rom won't work if I later try to flash it through recovery while using CM,right?
Prat92 said:
Thanks for such detailed answers. That cleared most of my doubts
Just some last few questions(promise!)
1. If wiping /system does remove the recovery before I install the rom, how is it possible to access it even to flash the rom? Shouldn't it like just close right when I wipe /system. Or does it not work like that?
2. Just to be sure the nandroid backup I made on my stock rom won't work if I later try to flash it through recovery while using CM,right?
Click to expand...
Click to collapse
1. Wiping system wont close the recovery at all. It still runs and you can still navigate within it. But remember do not reboot unless you've flashed the ROM! The mechanism of how the magic works is yet to be acknowledged. So I can't tell why it doesn't closes upon wipe. My best guess here is that the recovery might be running on a temporary partition perhaps. I hope a developer see this post and explains the magic.
2. Nandroid backup works all the time (if they are no errors when you are creating them). Nandroid backup is simply a backup of your whole device. If you're on CM, restoring nandroid backup will get your phone back to the way when you attempted the nandroid backup (stock ROM, rooted, and triple recoveries installed). Nandroid backup is useful when you're about to try something that may damage your ROM, without doing so much work to restore your device.
Say, you created a nandroid backup in cwm in which Cyanogenmod was installed. And then you flashed something afterwards. If that "something" damages the ROM and gives you bootloop, you can simply flash Stock ROM, root it again, install recoveries again, and restore the nandroid backup. Then, voilà, cyanogenmod is back. This will simplify your work rather than flash CM again, then gapps, then restore your apps and all those other things that will consume so much time
So a new nandroid backup will backup the whole device, in a form of an image.

[Q] Unable to mount /data, /ss after flashing a ROM

Hello, I'm in a bit of a pickle. I tried to flash this rom (http://forum.xda-developers.com/att-galaxy-s5/development/rom-dynamic-kat-1-0-t2821650), and I evidently screwed up. I can't restore to a previous backup, or even reflash and get past safestrap. I have flashed ROMs in the past. How do I get my phone into a usable state.
Fixed it. I formatted through Safestrap, and I was able to fix the file system and flash the rom and theme.

Categories

Resources