Hey, I'm in a very strange situation. The thing is I left my phone to charge overnight just like usual (made it reboot before doing so), when I woke up today I've noticed that it was bootlooping like crazy along with being very hot to the touch, like it was about to go off :x. Rebooting resulted in nothing, phone still bootloops. After entering TWRP and trying to look for my backup I also noticed that it shows "Internal storage (0mb)", what is totally weird considering that I've been doing absolutely no software modifications lately (I'm on Lineage). I also cannot mount data in "Mount" section, backing it up is also not an option.
I havent't tried yet to restore my full back up I've made around a month ago, is there any way I can revive the data partition?
Ok, since my backup is missing I've decided to reinstall the rom. But I can't format the Data partition at all . TWRP just goes "Failed to mount '/data' (Invalid argument), Unable to wipe /data). What should I do? Is the phone internal memory dead or what?
OK SOLVED. I entered erecovery and formatted my data. Now I reinstalled Lineage and everything works again... apart from photos of my doggy lost . Damn, I have completely no idea what caused that Data partition failure
Related
I had to restore a backup because my G1 was stuck on the G1 screen. I've done restore before and it all worked fine. This time, I got an error...
1. First, I am running CM5.0.8 with 1.0.7 recovery.
2. Went into recovery and tried nand restore and got the following error telling me to running recovery via console using 'nandroid-mobile.sh restore'
3. Went into console and ran it and got the following error:
error: unable to mount /data, aborting
I've tried to use a copy of my backup files that I had on my computer by moving it to the sd card and still get the same errors.
I'm a complete noob and seem to have messed things up trying to learn more!
Any help would be greatly appreciated.
Thanks
It sounds like you might be having a problem with the SD card, take it out and see if the phone boots up. SD cards die all the time and give you various symptoms. If that doesn't work, put 5.0.8 on the card and re-flash it. Sometimes my nandroid restore gives me a error if I have too many backups saved, I just have to mount SD card go to nandroid folder -> (device id) folder -> and there will be a folder for each back-up you have made, get rid of all but the last 2 and run it again. This always works for me.
Sounds more like something happened to the userdata partition.. otherwise the error would indicate /sdcard or a md5sum error. (Not sure what I've seen such things but they where entirely my fault.)
From fastboot screen try running 'fastboot erase system -w' from your computer, booting recovery and trying again.
Thank you for the replies.
I think I messed something up due to user error. I was playing with turning swap on and off via a script I had installed (a great script by a member steveo I think). I turned it on correctly by using swapon30 from the terminal but I didn't turn it off correctly (used swapoff instead of swap-off I think). When the blue led wouldnt turn off, I tried rebooting and got stuck on the G1 screen. (I really have no clue if that's where I messed up but that was what I was doing when it got stuck on reboot).
Anyway, I did a wipe/factory reset then it started up fine. I then went back into recovery and restored my last backup from last night which went fine as well. Only kind of weird thing I noticed was that I had to reinstall Google Maps from the market and now it's showing as installed in "system" whereas before it was showing as "internal".
When I did a factory reset and then ran a recovery, perhaps I needed to reflash the google apps that is part of the original CM5 install?
Appreciate the replies guys!
So recently I formatted my internal storage mainly to start fresh and clear out all the crapi didn't want, but since then whenever I reboot three phone gets stuck at the splash screen and will not function again until I pull the battery, reboot recovery, format data/media again, and flash something clean. When this happens and I reboot into recovery it prompts me to enter a password as if the data is encrypted. When I open the command line to see what it says it reads E: unable to decrypt storage... Or something to that effect. In on the most updated tarp and I've tried several Roms to see if there was something going wrong there but no. I would hardly consider myself a noob, and I have exhausted all other options with the exception of back to 100% stock and start from scratch unless anyone has any input... I can't even reboot without wiping my internal storage, please help!
janob09 said:
So recently I formatted my internal storage mainly to start fresh and clear out all the crapi didn't want, but since then whenever I reboot three phone gets stuck at the splash screen and will not function again until I pull the battery, reboot recovery, format data/media again, and flash something clean. When this happens and I reboot into recovery it prompts me to enter a password as if the data is encrypted. When I open the command line to see what it says it reads E: unable to decrypt storage... Or something to that effect. In on the most updated tarp and I've tried several Roms to see if there was something going wrong there but no. I would hardly consider myself a noob, and I have exhausted all other options with the exception of back to 100% stock and start from scratch unless anyone has any input... I can't even reboot without wiping my internal storage, please help!
Click to expand...
Click to collapse
i had this problem as well, and only thing i found to fix it was to completly odin back to stock, since then ive had no problems.
That's what I figured I might have to do.
Much appreciated
About a year ago, my Nexus 7 (2012 wifi) started occasionally locking up, then (after a couple of minutes) rebooting and getting stuck on the boot animation. This would happen once every month or two. The only fix was to disconnect the battery, then reboot to recovery and do a restore. Sometimes I only needed to restore /system; sometimes I had to restore /data too. This continued after I moved from Kitkat to Lollipop.
The other night it happened again, and this time things are worse. I boot into TWRP and try to restore, but it only finds /system. It can't see /data or /cache.
I'd love to solve the underlying problem, but for now, any ideas on how to resurrect /data?
A very long story short, I have learned that I should not seek out a career in phone repair.
I've bricked my phone by trying to flash a custom ROM onto it. I don't quite remember how I did it, but I wound up wiping the system partition. It won't recognize internal storage, TWRP says I have a storage size of 0 MB, wiping does nothing, changing file systems does nothing, formatting does nothing, I am unable to install anything on the device. Custom firmware won't install because of invalid partition names.
Through all of the guides I've found online, nothing has worked so far. Fails to mount '/data' as that is an invalid argument, unable to mount storage, can't repair internal storage as it gives me an "invalid partition selection" messasge, everything I do just pops up more and more errors and I'm worried that I've wasted even more money.
Any help would be much appreciated.
Update: Woke up this morning, booted the phone up ready to struggle with it even further, only to have it boot up to AEX and go through the setup process. I have no clue whatsoever how or why it is working, but I have a functional phone now.
I had LineageOS 17.1 + TWRP running fine on my Galaxy S5 klte, then the glue on the top part of the screen came away and disconnected the screen while the phone was on. After that it would only boot to part way through the Lineage animation, dimming to low brightness in the middle of it and rebooting into recovery.
Wiping the cache in recovery did nothing, but wiping the data partition fixed it, so I guess the data partition became corrupted. Restoring the data partition from an old TWRP backup of the same install works too. The hardware and ROM seem fine.
I made a full backup of the bad install, so is there anything I could do to try to get that working again or diagnosing what happens at boot? Any cache/settings files I could try deleting from the image if that's possible? I did find stuff about getting the last kmsg output but that doesn't seem to work with this phone/Android build. I wish I'd though about running fsck on the partition before I wiped it. No idea if the screen thing is a red herring or not.