Hello and greetings from germany,
I have a problem with my Moto G 2014 XT1068. I'm coming from rooted stock KitKat (Xposed) with open bootloader and TWRP 2.8.6.0. Everything seemed fine until yesterday, when the phone just went off (0% battery) and stayed at boot animation.
I've tried a lot of things, but the phone seems to be hardbricked:
- I can access recovery, but restoring does "FAIL" (restoring boot partition works, though). Restoring "system" aborts at about 18%, "data" immediately.
- I can access the phone through fastboot, but cannot flash anything. Whatever I do, the phone isn't changed. Tried reverting to stock (getting error when flashing gpt.bin, everything else seemed to work without errors, but no changes), tested flashing other recoveries (partition size mismatch, but that seems to be normal, whatever I flash, it keeps being TWRP 2.8.6.0), or even upgrade the bootloader (no errors reported at all, but no changes made to the phone).
- I can access the phone by MTP from TWRP, but cannot write to or delete anything from the internal SD.
Do you have any further ideas or is it an hardbrick?
Thanks in advance
René
Seems like the internal SD card is damaged, or there's a faulty partition table. Have you tried repairing and formatting /system and /data partitions with TWRP? Does it read external sd cards? If yes you could try flashing CM11 (because lollipop roms need an updated bootloader) from an external sdcard and see what happens. Also your backup could be corrupted, that's why it doesn't let you restore it at all.
As for the recovery, try updating your twrp to the latest version available (3.0). You can update twrp from twrp itself, just to see if it's fastboot's fault.
Wiped /system and /data. Didn't help. Wiping /data/media led to an error.
Is there anything beyond "wipe" to repair and format those partitions?
Thanks for the hints, will try updating TWRP and installing 11 this weekend, as external SDs can be accessed.
Greetings from Germany
René
Related
This is related to http://forum.xda-developers.com/showpost.php?p=44237167&postcount=39259
Problem:
Stuck at bootscreen after installing Roboto 4.3 via Rom Toolbox Pro. I'm on ARHD 12.0.
Fastboot erase cache, full wipe, dalvik wipe etc. pp didn't help.
ADB-Sideload also didn't work due to a mysteriously & out of the blue non-mountable internal SD. Something was borked when I installed the new typo, dunno how and why.
So, re-flashing ARHD from my laptop wouldn't work, furthermore I deleted ARHD.zip from my internal SD; but anyway, the SD was to no avail -> no chance to grab a Nandroid.
Solution:
I firstly changed the recovery on my black lady by flashing TWRP in order to substitute CMW. TWRP allowed me to access and mount an USB-OTG, which hasn't shown up on CMW (v6.0.3.4) at all.
So, finally I placed the ARHD.zip on the external drive, mounted the drive and flashed the ROM 2 times, as the first flash freezed on 20%. But then it went throu, the ROM settled down and the bootscreen stuck was gone.
I have a new LG Optimus L90 (D415) with stock 4.4 ROM, and TWRP 2.8.0.0 (and previously, Philz 6.58.7) for recovery. Obviously, the phone is rooted and now has an unlocked bootloader....
My problem is that neither recovery will back up (or even mount) "/data". Note that I put that in quotes because, without having "/storage/sdcard" or something in front of it, I presume that it's an internal folder and not something to do with the external SDcard.
My first guess would be a problem with encryption, because both the phone and the external SD are using it -- and I never get asked for the password. Either way, the actual error in TWRP says "E: Unable to mount 'data'", while Philz says it can't access /data/philz-touch for the .ini file.
I've made several Google expeditions to find the answer, and have come up empty-handed with all of them. I've seen all kinds of fixes, from claims that I have to run chkdsk against the SDcard, to backing up the entire /data partition with a tar file and reformatting it with command line nightmares.
I'll do what I have to in order to fix this, but I'd rather not embark on an experimental goose chase. Any ideas?
I have this same problem. But only for wiping and flashing.
I have no idea for fix if backup also not working !! (Noob)
1.TWRP click backup. Select all except SDcard.
Finish backup.
2.go to Wipe menu.>advanced wipe>select all except System and Sdcard.
Wipe.
(It will skip the error files)
3.Install menu. Select ROM to flash.
Was what I did.
fear2433 said:
I have this same problem. But only for wiping and flashing.
Click to expand...
Click to collapse
I'm not flashing anything, yet. First I need to make a backup of the entire phone (not including the SDcard). That way, if something goes wrong, I can just restore my old, working configuration -- all at once -- and start over.
I can back up and restore apps individually, using Titanium Backup. But what I need here is a Nandroid-type backup... and that generally has to be done from the recovery partition. There is one other way to backup everything, using a laptop/PC and ADB. But I've never tried it, and it wouldn't protect against a ROM meltdown.
Solved, somewhat...
So I did some further experimentation concerning this error. I did a test run to install CyanogenMod, and I found that I couldn't even factory reset certain partitions because of these "Unable to mount /data/" type errors.
What was ultimately the problem? The encryption. Once I decrypted everything, TWRP was able to see, mount, and backup, those partitions.
But I was under the impression that TWRP handles encryption, e.g. asking for the password, or some such. I mean, how can you do a Nandroid-type backup on a phone, if no recovery can mount those kinds of partitions?
So, for the record: "E:Unable to mount" was definitely due to the encryption being turned on for my internal storage. Thus the solution (so far) is to decrypt storage. A wretched solution, but at least it works for the time being.
BTW, In furtherance of this research, I formatted my internal SDcard to NTFS, just to make sure it wasn't misaligned or whatever when it was just FAT32. And I discovered that NTFS takes forever to format (32GB on the order of a couple hours)., FWIW.
The plot thickens. It may not be sufficient just to undo encryption, there may be something wrong with the way that partition was created, or otherwise is constructed.
Even though I now am able to mount /data, I'm not able to format it.... in TWRP it says something like "unknown filesystem 'auto'".
But there is a thread here that describes using Philz recovery to unmount and then format this mess, and I'm about to try it, I just have to flash Philz in place of TWRP. Now let's hope this version works without issues, because I'd have little recourse if things go bad there.
I'm currently using TWRP on my XT1063. I'm having weird problems regarding TWRP's access to the data partition. When I try to do a nandroid backup of the data partition, it gets 10-30% of the way through the backup then crashes and reboots to system.
I've successfully backed up the system partition to my external SD card, so it doesn't seem to be an SD card problem. I did TWRP fix permissions and it appears to have completed successfully. I'm not sure what is causing this nor how to solve it...
I think my next step will be to reinstall TWRP and try again. Failing that, I guess I'll switch to clockwork mod recovery, which I haven't used in a long time. Do you have any suggestions on things I could try before reinstalling recovery?
I updated my twrp from 2.7.1 to 2.8.3.0. I haven't flashed a rom in a while, so I don't know for sure that it was working on the old one but I did install CM11 using 2.7.1. Now with 2.8.3 when I go into recovery and wipe is says it worked, but in red there is the error: "E: unable to mount /system".
I tried to repair it with twrp, using format /system as ext4, then wipe and it seems to work and mount correctly, but if I restart, into recovery the /system no longer mounts and gives the same error if I try to wipe it. When I select repair, it says the partition is 0mb. When I format as ext4 it then shows as the correct size (~1.8GB).
So bottom line is that when I try to flash a new rom, it gets stuck at the formating /system step. I think the problem is with twrp but I'm not sure. Any ideas what to do?
I have a T-mobile HTC one M7. It was CM11, but everything is wiped. TWRP 2.8.3. S-off unlocked bootloader.
Thanks!
modman21 said:
I updated my twrp from 2.7.1 to 2.8.3.0. I haven't flashed a rom in a while, so I don't know for sure that it was working on the old one but I did install CM11 using 2.7.1. Now with 2.8.3 when I go into recovery and wipe is says it worked, but in red there is the error: "E: unable to mount /system".
I tried to repair it with twrp, using format /system as ext4, then wipe and it seems to work and mount correctly, but if I restart, into recovery the /system no longer mounts and gives the same error if I try to wipe it. When I select repair, it says the partition is 0mb. When I format as ext4 it then shows as the correct size (~1.8GB).
So bottom line is that when I try to flash a new rom, it gets stuck at the formating /system step. I think the problem is with twrp but I'm not sure. Any ideas what to do?
I have a T-mobile HTC one M7. It was CM11, but everything is wiped. TWRP 2.8.3. S-off unlocked bootloader.
Thanks!
Click to expand...
Click to collapse
first of all the most reliable version of TWRP recovery is stil 2.6.3.3 or 2.6.3.4, most of the users on here would agree with me on that, newer is not always better.
Also, have you tried the format data option, select wipe then format data button, be warned though, this will wipe everything including your sdcard (internal) if this option works you will then have to sideload or push a rom to your device before you can flash.
Seanie280672 said:
first of all the most reliable version of TWRP recovery is stil 2.6.3.3 or 2.6.3.4, most of the users on here would agree with me on that
Click to expand...
Click to collapse
Agree 100% but CM11 require at least 2.7.0.8 to be flashed (block:by-name) and recommended version of twrp to flash CM11 is 2.7.1.2 http://wiki.cyanogenmod.org/w/Install_CM_for_m7
If not flashing a rom like CM11 still recommend using 2.6.3.3/.4 even if there are newer version.
They are talking about this in ARHD thread.
Seems a updater script problem.
Read here and below!
http://forum.xda-developers.com/showpost.php?p=57985309&postcount=84878
My 2 cents
Fain11 said:
They are talking about this in ARHD thread.
Seems a updater script problem.
Read here and below!
http://forum.xda-developers.com/showpost.php?p=57985309&postcount=84878
My 2 cents
Click to expand...
Click to collapse
Thanks for the link. I tried to find similar threads, but couldn't. They are having the same problem but with a different rom (I was trying to flash Sky Dragon android L). The solution on that thread was to use TWRP 2.6.3.3, but some people reported having no problems with 2.8.3. The install instructions for Sky Dragon say use the latest twrp but doesn't specify a version. I guess I could try TWRP 2.6.3.3 but I'm not sure if it will work since CM requires 2.7.1.
The other solution was to mount the partition manually before flashing using the terminal in recovery. This command was suggested:
Code:
run_program("/sbin/umount", "/system");
Haven't tried any of these solution myself. After 3 hours and wiping my entire data partition by accident, I USB-OTG copied my nandroid backup to my phone and did a complete recovery. Luckily the restore process didn't care about mounting /system. I may try this again with manual mounting, but likely I will wait for a twrp update. I'm not sure if twrp 2.6 supports usb-otg so it will be a pain in the ass if I wipe /data again by accident.
Random side note for anyone googling this, if you accidently wipe all the data from your sdcard and have to copy the nandroid backup for twrp, the the restore function won't recognize the files unless they are in exactly the right directory. The best way to get this is to copy the entire TWRP directory when saving your backup in the first place so you can just copy it back. If you didn't do that then just run a nandroid backup of the blank sdcard and it will recreate the folder structure for you. Then you copy the files into the correct folder.
alray said:
Agree 100% but CM11 require at least 2.7.0.8 to be flashed (block:by-name) and recommended version of twrp to flash CM11 is 2.7.1.2 http://wiki.cyanogenmod.org/w/Install_CM_for_m7
If not flashing a rom like CM11 still recommend using 2.6.3.3/.4 even if there are newer version.
Click to expand...
Click to collapse
Exactly this. I do not know the exact reason CM needs 2.7.1 so therefore I don't know if Sky Dragon needs it as well. The instructions just say use the latest twrp.
http://forum.xda-developers.com/showthread.php?t=2400161
Seanie280672 said:
first of all the most reliable version of TWRP recovery is stil 2.6.3.3 or 2.6.3.4, most of the users on here would agree with me on that, newer is not always better.
Also, have you tried the format data option, select wipe then format data button, be warned though, this will wipe everything including your sdcard (internal) if this option works you will then have to sideload or push a rom to your device before you can flash.
Click to expand...
Click to collapse
I did wipe my entire data partition (by accident), but I did not try to format it as ext4. I did format /system to ext4 (so now the partition was displaying correctly as ~1.8gb). The used the twrp repair, then wipe It seemed to work, but if I restarted right then, without even trying to flash the rom, the /system would not mount on reboot to recovery and would show as 0mb. I used all reasonable combinations and permutations of the wipe, repair and format functions on system, nothing worked.
I finally copied my nandroid backup via usb-otg and recovered back to cm11.
So I have a moto g xt1068 (dual sim), apps started crashing all of a sudden. Including google play store and the rest of the apps. So I:
Tried to factory reset through settings, that didn't work (pushing the 'erase everything' does nothing)
So I unlocked the bootloader and tried to flash a custom recovery, it flashes successfully but gives something like a 'mismatch' error, then I boot to recovery, but its still stock recovery. So I copied a lollipop ota to external card to apply through stock recovery, that didn't work either as the stock recovery refused to show my external SD card.
Then I downloaded the stock lollipop rom to flash with mfastboot, every command line says okay, but when I reboot the device, its still on KitKat.
I then tried to upgrade the bootloader from 0x4807 to the latest bootloader, so I can flash a custom by live booting twrp, flash latest bootloader with fastboot commands, everything says okay,but still on radio, which means I can't flash custom ROM.
So I live booted twrp,then tried to copy ota.zip to internal SD, but it won't copy, I try to format all partitions through twrp, they all format ok, but reboot device back to crashing KitKat, live boot twrp again, copied ota.zip to external SD card first, then use twrp file manager to copy ota.zip to internal SD card, that also brings out another error. Tried to restore the device with twrp backup of stock 5.0.2, boot.IMG flashes fine, but when installing system, it cuts midway with a 'fork' error or something. So I can say that both system and data partition is corrupt. I am currently outta options. I know this device isn't in a hard brick situation. Help anybody