i need help with my XT1068 (dual sim moto g 2014)
my moto g has an unlocked bootloader, TWRP installed, stock 5.0.2 firmware with root acess.
yesterday i installed xposed for lollipop and gravitybox for lollipop, yes both are alpha versions, but i am that kind of early adopter and i wanted to try it. everything ran smooth, xposed and gravitybox successfully installed and worked.
however i noticed i can't take a screenshot or photo anymore. so i tried via solid explorer to create a folder/file on sdcard0 (internal) and sdcard1 (external sdcard), both failed stating "permission denied". also via MTP on my computer i can't write to both partitions.
so i restored my nandroid backup i did before i installed xposed. problem still exists, my phone works fine but i can't write to both sdcards.
a factory reset wipe doesn't work, after the installation-process were i set language and stuff the system-ui closes and i can't do anything.
i tried all kind of wipes in twrp (system, internal, dalvic cache and cache of course) but nothing worked.
also tried commands like fsck_msdos /dev/block/vold/179:65 (which is my external sdcard) and fsck_mdos /storage/emulated/legacy (which gave me error ** /storage/emulated/legacy (NO WRITE)" ) or restorecon -v -R /data/media (also no change, still not writeable)
in TWRP i can modify folders in the filemanager...
never had any similar situation before. maybe someone has an advice for me.
EDIT:
i decided to go back to the start and get this phone working again. so i downgraded to official kitkat firmware and installed the lollipop ota update. then recovery and supersu and now it is working again.
Related
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.
See post# 2
Update but need some help
Figured everything out after doing more research. I successfully downgraded to 4.4.2 and unlocked using towelroot.
I have a couple of questions if anyone can answer them:
I don't see Safestrap in Busybox's list
Safestrap installed fine and I an access it etc. but a backup fails if I try it:
Says:
Safestrap 3.75 (TWRP v2.7.1.0)
ROM Slot: stock
Data and System are checked
Enable compression and Skip MD5 are unchecked.
Backup Fails:
Unable to mount internal storage.
Unable to mount /external_sd during GUI startup (I have no external sd card in the phone)
Full SELinux support is present
Unable to mount /external_sd/TWRP/. twrps when trying to read settings file
Updating partition details
Unable to mount internal storage
FAIL
Any advice XDA?
Thanks in advance
Figured it out. Stupid simple mistake. I didn't have internal storage mounted. Backup worked great afterwards.
For others searching the same issue, go into Safestrap and click Mount>click internal storage.
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é
Hello guys, i was trying to update my CM 13 today and it didn't work. It made the download but once in the recovery, nothing happened :S i'm trying to understand why and i hope some of you know of this.
By the way, my TWRP version is the 2.8.7.0 if it helps..
ugh...Can't really understand what happened
You installed via OTA/cm updater? meaning you downloaded with your phone
Just download the zip directly and flash it with twrp
You'll also need to re-flash gapps unless you're using TWRP 3.0.0
Make sure that you have not installed any additional mods which alters system partition (kernels, soundmods etc.) If not, easiest solution would be to dirtyflash new one or clean install.
Same problem here.
405. CM13. TWRP 3.0.0. Merged SD card with internal storage.
In Recovery I can see folder structure but no files. I know its because of SD-encryption but I hoped I could at least see files in internal storage to update. Hope there's a solution soon. Does anyone have a workaround?
Gesendet von meinem LG-D405 mit Tapatalk
Filesystem of sdcard mount point
What is your /sdcard mount point filesystem? Mine is 'auto' (Maybe that might be causing the problem?) , and you can check by going into TWRP -> Wipe -> sdcard -> Repair or Change File System
Thank you for your answer. I checked that quickly, but couldn't find the option 'repair or change filesystem' without actually wiping the storage... I'll check again later if there's more time.
I found and changed the option from exFAT to ext4. All folders on the SD were lost in TWRP. Changed back to exFAT: couldn't see them either..
When using adopted storage (i.e. formatting external SD and using it as internal storage), then /sdcard in Android becomes /emmc in TWRP. At least it's what I see here using TWRP 3.0.0 Dark Blue.
From what I've looked, all internal storage is used only for app and app data once I started using adopted storage, so the only way I can think of using internal storage in TWRP to flash anything is either sideloading or using MTP in TWRP.
I managed updating through sideload.
1. Connect your phone to your computer via USB
2. Activate sideload in TWRP (advanced)
3. In platform-tools folder press Shift+right click to open commandline
4. If your device is connected properly ('adb devices') you can sideload zips (in platformfolder) via the command 'adb sideload filename.zip'
5. Restart device. Note: It took a few minutes for all apps to appear in the appdrawer again.
Thank you all for your help! I will looks after the folder emmc, but as I see no files, just folders anywhere, I am not that hopeful. But at least it works now
kreativpause said:
I managed updating through sideload.
1. Connect your phone to your computer via USB
2. Activate sideload in TWRP (advanced)
3. In platform-tools folder press Shift+right click to open commandline
4. If your device is connected properly ('adb devices') you can sideload zips (in platformfolder) via the command 'adb sideload filename.zip'
5. Restart device. Note: It took a few minutes for all apps to appear in the appdrawer again.
Thank you all for your help! I will looks after the folder emmc, but as I see no files, just folders anywhere, I am not that hopeful. But at least it works now
Click to expand...
Click to collapse
What did you wipe prior to your sideload? I want to do a wipe and fresh install of gapps and cm13, but I am afraid I could soft brick my phone.
I chose both. Dalvik and the other option ( I believe cache). No issues.
kreativpause said:
I chose both. Dalvik and the other option ( I believe cache). No issues.
Click to expand...
Click to collapse
Mine gets stuck at "detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system" then it just reboots to TWRP again. Sideload says "
serving: 'cm-13.0-20160322-NIGHTLY-w7.zip' (~0%) * failed to read command: No error". Did you wipe system before you sideloaded?
I did not wipe anything beforehand.
This problem has been solved by @Didgesteve
Thank you very much, Didgesteve!
For everyone who is a genius(like me), read his post.
Hi Community,
short story: my device seems kind'a bricked, because i am not able to install a rom via twrp; error: unable to mount /data /cache and /system.
What I did:
I unlocked my bootloader via the official sony method > everything worked flawlessly
I bootet my device into fastboot mode and flashed twrp onto it > everything still workes fine
I wiped /data /cache and /system according to the normal cm13.0 installation process > still finr
I installed the cm13.zip from an external sd-card > no errors
I installed the gapps.zip from the sd-card > Nothing unusual
I booted into cm13, configured it and installed some apps > works as usual
I noticed that a new version of the rom was published, so I booted into twrp > worked
I wiped /data /cache and /system > worked
I reallized, that i could flash my external sd-card, too because i wanted to install the new cm13-version via adb-sideload > now the errors came in
So i thougt retrying wiping /data /cache and /system and the same errors occured > holy sh*t
Last I tried simply installing the cm13.zip from the external sd-card > same errors
What the errors are for wiping(those for install are basically the same:
Code:
could not mount /data and unable to find crypto footer
failed to mount /data (no such device)
Unable to recreate /data/media folder
Failed to mount /system (Invalid argument)
Failed to mount /cache (Invalid argument)
Unable to mount storage
Same goes for using the official cyanogen recovery and other cyanogenmod versions.
I am also not able to find/mount it via adb shell.
The images, etc:
CM13: http://forum.xda-developers.com/z3-compact/development/rom-cm13-t3277402/page7 version by @nelvinchi on 25th February 2016, 12:39 PM
TWRP: https://twrp.me/devices/sonyxperiaz3compact.html
Gapps: https://www.androidfilehost.com/?fid=24269982087021755
Additional information:
OS: Mac OSX El Capitan and Linux Mint 17.3
Sd-Card: SanDisk Ultra 64GB micro sdxc
Phone: Sony Xperia Z3 Compact D5803 (colorrange)
My ideas for fixing this:
-manually adding the partitions via adb shell
+required: correct partiton table and adb commands
+don't now, if this would work
Hope i didn't miss anything and there is someone out there, how can help me,
yours sincerely,
Niggl
Well I followed your method up to step 8 and the point of wiping system in recovery mode. Even if you were flashing a completely different rom, you shouldn't have to touch system unless you're coming from LL to CM for the first time. Updating roms to a later version should only require a wipe of dalvik/cache. By the sound of it there are no system files for it to boot into, either that or the partition tables are corrupt.
Have you got flashtool working? Have you tried pushing a stock tft? to see if you can repair it?
There is Sony Bridge, which if it does the same as the PC version will repair the phone to stock, as long as you can still get into Flashmode.
The chances of being able to repair it back into CM are slim, I suspect you're going to have to start from scratch, get stock working then go back to CM after.
**SOLVED**
Thank you for your help!
Didgesteve said:
Well I followed your method up to step 8 and the point of wiping system in recovery mode. Even if you were flashing a completely different rom, you shouldn't have to touch system unless you're coming from LL to CM for the first time. Updating roms to a later version should only require a wipe of dalvik/cache. By the sound of it there are no system files for it to boot into, either that or the partition tables are corrupt.
Click to expand...
Click to collapse
The partition tables were(because of bull**** or something like that) corrupted(I checked it: not because of the wiping, but i will not wipe /system at an update in the future)
Didgesteve said:
There is Sony Bridge, which if it does the same as the PC version will repair the phone to stock, as long as you can still get into Flashmode.
Click to expand...
Click to collapse
I can boot into recovery and fastboot/flash mode.
Xperia companion and sony bridge are both not working because of "modified software".
Flashtool worked for the stock tft.
So THANK YOU VERY MUCH,
you are my savior!
I hope nobody else, will be a genius like me
Thx again,
Niggl1999