Related
Moderator Notes: I was asked to sticky this thread as it seems to be a recurring issue and a couple of fixes are in the posts.
Sorry my bad english am latin.
Hi guys first thread here and i need your help. Here s the thing, i was using my tf700, browsering, and the tablet goes off, i tried start up and a bootloop appears. So i go to Recovery (latest TWRP) and i tried to flash a ROM (latest crombi kk), like always i tried to wipe cache and dav bfore flash it but that proces seems to fail, and a couple of messages like unable to mount /data unable to mount /system appears, first time happening, i never had troubles with the tablet. So i tried to get fastboot mode and run the fastboot erase cach command (i read in a forum dat some guy did that and work for him), so i download the adb fastboot files, i connect the tf700 to my laptop (windows 7 64bit) and a installing drivers message and i wait and the driver that is called Transformer did not install, i dont know where to get those drivers, i found a file Asus usb drivers and bla bla but when i unzip the file i get 3 folders and no .exe or installer. So i tried to continue and i enter fastboot mode in the tablet and connect usb tablet-pc, and now another driver installing message appears, now is a driver called Fastboot, so i wait anda again the driver did not install correctly. So i continue and open cmd and tried the comman for erase cache, and only appears the WAITING FOR DEVICE text. i donw know waht to do, i also tried flashing again a ROM, bt only bootloop, trie again to wipe cache and dav but is only unable to mount /data. Any ideas ????
formobicho said:
Sorry my bad english am latin.
Hi guys first thread here and i need your help. Here s the thing, i was using my tf700, browsering, and the tablet goes off, i tried start up and a bootloop appears. So i go to Recovery (latest TWRP) and i tried to flash a ROM (latest crombi kk), like always i tried to wipe cache and dav bfore flash it but that proces seems to fail, and a couple of messages like unable to mount /data unable to mount /system appears, first time happening, i never had troubles with the tablet. So i tried to get fastboot mode and run the fastboot erase cach command (i read in a forum dat some guy did that and work for him), so i download the adb fastboot files, i connect the tf700 to my laptop (windows 7 64bit) and a installing drivers message and i wait and the driver that is called Transformer did not install, i dont know where to get those drivers, i found a file Asus usb drivers and bla bla but when i unzip the file i get 3 folders and no .exe or installer. So i tried to continue and i enter fastboot mode in the tablet and connect usb tablet-pc, and now another driver installing message appears, now is a driver called Fastboot, so i wait anda again the driver did not install correctly. So i continue and open cmd and tried the comman for erase cache, and only appears the WAITING FOR DEVICE text. i donw know waht to do, i also tried flashing again a ROM, bt only bootloop, trie again to wipe cache and dav but is only unable to mount /data. Any ideas ????
Click to expand...
Click to collapse
More likely your data partition got corrupted.
Try wiping it or formatting /data in TWRP to see if that helps? You will lose everything if you don't have backups.
sbdags said:
More likely your data partition got corrupted.
Try wiping it or formatting /data in TWRP to see if that helps? You will lose everything if you don't have backups.
Click to expand...
Click to collapse
i already tried that, wiping (cache, dav, system, ata, factoty reset) anything gives the unable to mount /data error.
formobicho said:
i already tried that, wiping (cache, dav, system, ata, factoty reset) anything gives the unable to mount /data error.
Click to expand...
Click to collapse
You'll need to manually format it using the terminal in TWRP
Make sure data is umounted then run this command. Make sure you have charged it as well or leave it plugged in.
It can take a number of hours to complete.
Code:
mke2fs -T ext4 /dev/block/mmcblk0p8
sbdags said:
You'll need to manually format it using the terminal in TWRP
Make sure data is umounted then run this command. Make sure you have charged it as well or leave it plugged in.
It can take a number of hours to complete.
Code:
mke2fs -T ext4 /dev/block/mmcblk0p8
Click to expand...
Click to collapse
first of all is an honor chat with the legend sbdags!!! second can u guide me step by step. i did enter in twrp and go to advanced then terminal command then a selection menu appear and said browse to starting folder and a list of folder appears and a botton with Select Folder, wich folder i must select now? i tried just hit the select folder button and then i put the command taht u said and in the terminal said mke2fs 1.41.14 (22-dec-2010) nothing more and nothing happen
sbdags said:
You'll need to manually format it using the terminal in TWRP
Make sure data is umounted then run this command. Make sure you have charged it as well or leave it plugged in.
It can take a number of hours to complete.
Code:
mke2fs -T ext4 /dev/block/mmcblk0p8
Click to expand...
Click to collapse
Thank you so much sbdags.
You're a life save thought I had softbricked my tf700
Muchas gracias
formobicho said:
first of all is an honor chat with the legend sbdags!!! second can u guide me step by step. i did enter in twrp and go to advanced then terminal command then a selection menu appear and said browse to starting folder and a list of folder appears and a botton with Select Folder, wich folder i must select now? i tried just hit the select folder button and then i put the command taht u said and in the terminal said mke2fs 1.41.14 (22-dec-2010) nothing more and nothing happen
Click to expand...
Click to collapse
Did you unmount data first?
---------- Post added at 07:25 AM ---------- Previous post was at 07:24 AM ----------
chukkie said:
Thank you so much sbdags.
You're a life save thought I had softbricked my tf700
Muchas gracias
Click to expand...
Click to collapse
You are welcome!
EDIT - somehow the format finally took.. after 5 or 6 reboots.. very strange
okay, i hate to bump this thread. but i have been searching for a few nights and i cannot find a solution. i am having the same problem as OP.
Essentially, my tablet was interrupted mid format. I believe my data partition is corrupted. I can access recovery/fastboot and the tablet accepts commands from my PC. i have TWRP 2.7.1.1 on the tablet right now.
i tried what sdbags said:
You'll need to manually format it using the terminal in TWRP
Make sure data is umounted then run this command. Make sure you have charged it as well or leave it plugged in.
It can take a number of hours to complete.
Code:
mke2fs -T ext4 /dev/block/mmcblk0p8
Click to expand...
Click to collapse
this did not work. i got the same "mke2fs 1.41.14 (22-dec-2010)" output, and then the tablet rebooted back into TWRP over again. (data was not mounted, i cannot mount it at all)
some more output from my tablets TWRP console:
Code:
e:could not mount/data and unable to find crypto footer.
e:unable to mount '/data'
e:unable to recreate /data/media folder/
updating partition details...
e:unable to mount '/data'
e:unable to mount internal storage.
e:unable to mount /data/media during gui startup
full selinux support is present.
e:unable to mount /data/,edia/twrp/.twrps when trying to read settings file.
e:unable to mount '/data'
is there another way to fix my corrupted partition?
this did not work. i got the same "mke2fs 1.41.14 (22-dec-2010)" output, and then the tablet rebooted back into TWRP over again. (data was not mounted, i cannot mount it at all)
Click to expand...
Click to collapse
I have exactly same situation
edit: after running this command
mke2fs -T ext4 /dev/block/mmcblk0p8
Click to expand...
Click to collapse
it prompt
Starting Path : /external_sd
Click to expand...
Click to collapse
and there is also button "KILL" when I hit enter it prompt : /dev/block/mmcblk0p8 is appereatly in use by the system: Will not make a file system here!
Any advice? (sry for being this big noob!)
Code:
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot
Type in those commands via a usb connection to your device whilst it is in recovery.
sbdags said:
Code:
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot
Type in those commands via a usb connection to your device whilst it is in recovery.
Click to expand...
Click to collapse
Wouw thanks for so fast reply :highfive:.
But I think I'll disepoint you "usb debugging is disabled"
---------------------------------------------------------------------------------------------------------------
Any way I can reinstall stock from fastboot? damn it......
brinza said:
Wouw thanks for so fast reply :highfive:.
But I think I'll disepoint you "usb debugging is disabled"
---------------------------------------------------------------------------------------------------------------
Any way I can reinstall stock from fastboot? damn it......
Click to expand...
Click to collapse
No idea how when and after what exactly but the installation of stock rom started by itself after couple of reboots and couple of command i tried. (I had a file : US_epad-user-10.6.1.14.10.zip on my SD card
sbdags said:
Code:
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot
Type in those commands via a usb connection to your device whilst it is in recovery.
Click to expand...
Click to collapse
Probably a Bad Idea - you should unmount /data before formatting. Then it should also not hurt to keep the recovery running.
Unbrick my TF 700t
Accidentally, bricking my tablet
I try Advance and Terminal Command with TRWP at tablet, it did not work
but when I try with command from PC (desktop), it works like a charm. I was able to see internal storage
from that just re install Custom ROM. Thank alot to sdbag
Thanks
sbdags said:
Code:
adb shell
killall -19 recovery
make_ext4fs /dev/block/mmcblk0p8
reboot
Type in those commands via a usb connection to your device whilst it is in recovery.
Click to expand...
Click to collapse
Wow. you are a life saver. that worked for me.
player50 said:
Wow. you are a life saver. that worked for me.
Click to expand...
Click to collapse
Glad it worked. Everyone should keep those commands handy
Thanks a lot...
After a long research I have found your thread.
I have almost given up looking for this damn issue...
At last, It became real! You are a real life saver.
sbdags help!
1) i dont know how to unmount data .
2) when i click advanced then terminal command it opens- Browse to starting folder and gives the file manager kind of view.
3) so i tried using adb on computer
the first three command work(i think but the third gives this error not enough space) .
please suggest a solution. thank you in advance
device moto g xt1033
i tried downgrading from lollipop 5.0 brasilian to kitkat but it wont go past warning bootloader unlocked screen. when i flash cm from twrp, it gives 3 errors
E:/ unable to mount '/data'
E:/ unable to mount '/cache'
E:/ unable to mount internal storage
then when i start it just keeps on loading on cm logo
should i create a separate thread for all this?
'
SemiNoob314 said:
1) i dont know how to unmount data .
2) when i click advanced then terminal command it opens- Browse to starting folder and gives the file manager kind of view.
3) so i tried using adb on computer
the first three command work(i think but the third gives this error not enough space) .
please suggest a solution. thank you in advance
device moto g xt1033
i tried downgrading from lollipop 5.0 brasilian to kitkat but it wont go past warning bootloader unlocked screen. when i flash cm from twrp, it gives 3 errors
E:/ unable to mount '/data'
E:/ unable to mount '/cache'
E:/ unable to mount internal storage
then when i start it just keeps on loading on cm logo
should i create a separate thread for all this?
'
Click to expand...
Click to collapse
Question: Why don't you care to read the short thread from beginning?
das chaos said:
Question: Why don't you care to read the short thread from beginning?
Click to expand...
Click to collapse
i am really sorry if the earlier comment came out as rude.
actually i did all of those steps, using the command terminal, using adb from pc but none of them worked, all of them had some problem
So here's my situation.
I was trying to move a file from my internal storage to my microsd using the twrp file manager, it was successful but file remained in the internal storage at the sametime the file was in my microsd. So i thought it might be a glitch so I rebooted and entered to twrp again, but suddenly the splash screen flashed and froze. So i rebooted it again and tried again, the samething happened. It just flashed and then frozed at the twrp splash screen. I tried to drain my tablet and then turned it on and tried to go to the twrp, but the samething happened. I tried booting to android but it wont boot, i'm using grimlock 4.0 and I'm on data2sd. It's stuck at the pre.init screen. I can use fastboot, i tried to reflash twrp with the lastest one, i erased the previous one and flashed the latest one using fastboot, it worked but it cannot mount any partitions except my microsd card and whenever you reboot it and go back to recovery the twrp screen flashes and freezes. I need help i think i may have doomed my tablet.
P.s i erased the boot, system, partitions in hopes that i can reset everything but apparently it doesn't work.
supernova0 said:
So here's my situation.
I was trying to move a file from my internal storage to my microsd using the twrp file manager, it was successful but file remained in the internal storage at the sametime the file was in my microsd. So i thought it might be a glitch so I rebooted and entered to twrp again, but suddenly the splash screen flashed and froze. So i rebooted it again and tried again, the samething happened. It just flashed and then frozed at the twrp splash screen. I tried to drain my tablet and then turned it on and tried to go to the twrp, but the samething happened. I tried booting to android but it wont boot, i'm using grimlock 4.0 and I'm on data2sd. It's stuck at the pre.init screen. I can use fastboot, i tried to reflash twrp with the lastest one, i erased the previous one and flashed the latest one using fastboot, it worked but it cannot mount any partitions except my microsd card and whenever you reboot it and go back to recovery the twrp screen flashes and freezes. I need help i think i may have doomed my tablet.
P.s i erased the boot, system, partitions in hopes that i can reset everything but apparently it doesn't work.
Click to expand...
Click to collapse
As long as you can fastboot, you have not 'doomed' your tablet.
Flash newest stock ROM from ASUS site and you will be set:
1. Unzip stock ROM zip file twice and you will get a file 'blob'
2. Put blob file into fastboot folder.
3. Fastboot ROM using:
Code:
fastboot -i 0x0b05 flash staging blob [enter]
fastboot -i 0x0b05 reboot [enter]
4. Let blue progressbar finish (will need a long, long time) and tab will reboot itself.
5. Now you should be on working stock ROM and can flash custom TWRP (2.8.x.x).
Good luck!
das chaos said:
As long as you can fastboot, you have not 'doomed' your tablet.
Flash newest stock ROM from ASUS site and you will be set:
1. Unzip stock ROM zip file twice and you will get a file 'blob'
2. Put blob file into fastboot folder.
3. Fastboot ROM using:
Code:
fastboot -i 0x0b05 flash staging blob [enter]
fastboot -i 0x0b05 reboot [enter]
4. Let blue progressbar finish (will need a long, long time) and tab will reboot itself.
5. Now you should be on working stock ROM and can flash custom TWRP (2.8.x.x).
Good luck!
Click to expand...
Click to collapse
I was able to that, but the filesystem that I was using was f2fs so when I booted to the stockrom it said" encryption unsuccessful" so i had to format my data partition to a compatible format. so i flash twrp recovery, but I had the same problem, the screen flashes and then it stays at the twrp splash screen. then I thought it might be a problem with my data partition, so I erased my whole data partition using fastboot, with the command
fastboot format userdata
it worked and the recovery is working also, but my filesystem is on ext3 and I know ext 4 is better than ext 3, so using the twrp recovery I formatted my data partition to ext4 but suddenly the recovery hangs and doesn't finish the format. it there a way that this could be fixed? I really want to use a better file system.
supernova0 said:
..... I formatted my data partition to ext4 but suddenly the recovery hangs and doesn't finish the format. it there a way that this could be fixed? I really want to use a better file system.
Click to expand...
Click to collapse
Probably it didn't hang but you didn't have the patience! Formatting a /data partition to ext4 can last a long, long time. People reportet as much as 90 min. In my case it was 30 min. So, be patient!
das chaos said:
Probably it didn't hang but you didn't have the patience! Formatting a /data partition to ext4 can last a long, long time. People reportet as much as 90 min. In my case it was 30 min. So, be patient!
Click to expand...
Click to collapse
Thanks it worked!!! thank you very much
The file system is now on ext4 but whenever I try to flash it to f2fs it gives me:
Unknown mtp message type 1
And then its unable to format to f2fs.
supernova0 said:
Thanks it worked!!! thank you very much
The file system is now on ext4 but whenever I try to flash it to f2fs it gives me:
Unknown mtp message type 1
And then its unable to format to f2fs.
Click to expand...
Click to collapse
1. You reasonably can only format /data with f2fs
2. Reliable formatting f2fs is possible with newest TWRP 2.8.5.0; Goto tab 'Wipe'=> check only /data=>Change File System=>check f2fs
3. Depending on what ROM you are actually, there might be a command 'mkfs.f2fs' in /system/bin; you can format manually by opening Terminal Emulator typing:
Code:
su [enter]
mkfs.f2fs /dev/block/mmcblk0p8 [enter]
be carefully, what you type! Mistyping can render your tab bricked.
das chaos said:
1. You reasonably can only format /data with f2fs
2. Reliable formatting f2fs is possible with newest TWRP 2.8.5.0; Goto tab 'Wipe'=> check only /data=>Change File System=>check f2fs
3. Depending on what ROM you are actually, there might be a command 'mkfs.f2fs' in /system/bin; you can format manually by opening Terminal Emulator typing:
Code:
su [enter]
mkfs.f2fs /dev/block/mmcblk0p8 [enter]
be carefully, what you type! Mistyping can render your tab bricked.
Click to expand...
Click to collapse
Ok, I found myself here as well. I recovered and have KatKiss 5.0.2 #18 installed and running. I do have TWRP 2.8.5 and it will not convert my /data to f2fs with the same error above. It worked once but then I got hungup on a Google restore and it corrupted everything forcing me to Asus restore. This ROM doesn't have mkfs.f2fs.
How else can I convert to f2fs? Is there another way to do this via ADB or getting the mkfs.f2fs command to drop in /system/bin/?
Thanks--
bretzke said:
Ok, I found myself here as well. I recovered and have KatKiss 5.0.2 #18 installed and running. I do have TWRP 2.8.5 and it will not convert my /data to f2fs with the same error above. It worked once but then I got hungup on a Google restore and it corrupted everything forcing me to Asus restore. This ROM doesn't have mkfs.f2fs.
How else can I convert to f2fs? Is there another way to do this via ADB or getting the mkfs.f2fs command to drop in /system/bin/?
Thanks--
Click to expand...
Click to collapse
Try that mkfs.f2fs command from recovery in a shell from a PC
Or after it fails pull a recovery log .....
Code:
adb pull /tmp/recovery.log
paste it on pastebin or upload it to xda .....
Thx Josh
lj50036 said:
Try that mkfs.f2fs command from recovery in a shell from a PC
Or after it fails pull a recovery log .....
Code:
adb pull /tmp/recovery.log
paste it on pastebin or upload it to xda .....
Thx Josh
Click to expand...
Click to collapse
Thanks for helping...here's the log: http://pastebin.com/Fr5q88PH
Here is the error:
Formatting Data using mkfs.f2fs...
mkfs.f2fs: invalid option -- r
I:mkfs.f2fs -t 1 -r 16384 /dev/block/mmcblk0p8 process ended with ERROR=1
bretzke said:
Thanks for helping...here's the log: http://pastebin.com/Fr5q88PH
Here is the error:
Formatting Data using mkfs.f2fs...
mkfs.f2fs: invalid option -- r
I:mkfs.f2fs -t 1 -r 16384 /dev/block/mmcblk0p8 process ended with ERROR=1
Click to expand...
Click to collapse
Thanks for your assistance Josh. It turns out 2.8.5 has a bug for f2fs conversion on many/most devices. Loaded 2.8.4 and it worked perfectly.
bretzke said:
Thanks for your assistance Josh. It turns out 2.8.5 has a bug for f2fs conversion on many/most devices. Loaded 2.8.4 and it worked perfectly.
Click to expand...
Click to collapse
See you found your own answer and I like that ..... :good:
Thx Josh
I previously ran LolliGPE but was long overdue for an update. I downloaded the latest version and copied the image to my phone and flashed the ROM. I decided to go try a dirty install first to see if I could keep everything I had, since I had already been running a previous version and after reviewing the changelog did not see anything recommending to wipe clean. After installing successfully, Android asked me to enter my password to decrypt my data (I don't recall ever encrypting my data?), and so I did. It then told me that my password was right, but the data was corrupt, and presented me a button to reset my phone. The button redirected me to recovery and automatically attempted to wipe /data and then re-mount it, but the wipe failed. I rebooted again with the same issue, same failed attempt to wipe. I went to install the zip again, and this time do a full wipe, but it was unable to mount my phone's storage nor my SD card. I am not able to mount either at all now.
What's the best course of action? I'd like to retain as much as I can and avoid wiping all of the internal storage clean. Is there a simpler fix to this or am I doomed?
HBOOT: 3.19.0.0000
RADIO: 1.09.20.0926
OS: 3.28.605.4
EDIT: For anyone else having a problem like this that at least wants to get their data back, here's what you should do (I assume you know how to work with Linux!):
Make sure you have the latest version of TWRP and ADB.
Boot the phone into recovery mode and connect the phone to your computer via USB
Run "ls -al /dev/block/platform/msm_sdcc.1/by-name" and check the output. Make a note of the partition marked "userdata" - for me, it was /dev/block/mmcblk0p48.
Either: simply use adb pull to copy this file to your computer (this will require about 26 gigs of space), or attempt to mount the file. To use adb pull, execute "adb pull /dev/block/<ID> ./data" (ID being what you marked down). Your data partition will be copied to /data. To mount, use "mount -t ext4 /dev/block/<ID> /userdata". Whatever's left of your data will be on your phone's new /userdata folder.
Use ADB to pull what files you want from /userdata. If you pulled the partition, skip this step.
If you copied the files you wanted over, you're done. If you pulled the entire partition, you're going to want to try and mount it. On Windows, there are various tools to mount Linux partitions, a quick Google will find some good ones. However, if the data is corrupt, it will not work. I recommend attempting to repair the partition on linux, with the command "e2fsck -f -y /path/to/data", replacing the path to your data file as necessary. Once done, run "mount -t ext4 /path/to/data /mnt/data", replacing the paths as necessary.
Once mounted, you can access your data wherever it was mounted. If e2fsck appeared to fix many errors, chances are most of your data will be in the lost+found folder, and you'll need to sort through this yourself. If you're lucky, then your data will be intact and readily usable. Internal SD card data is located at ./media/0.
To fix the partitions and get Android back up and running, you need to install the latest firmware, format your data in TWRP, factory reset, and then flash a ROM again. Here's what I did to do that, without an SD card. If you have an SD card, simply copy your ROM zip to the SD card and skip the final steps:
Make sure you have the latest version of TWRP and ADB, and download the latest copy of the firmware (check the development forum here).
Boot the phone (doesn't matter to what) and run adb reboot bootloader. When your phone reboots, double-check by running fastboot reboot-bootloader.
Put your phone in RUU mode with fastboot oem rebootRUU. The phone will restart and the HTC logo will come up.
Wait a couple seconds, then run fastboot flash zip firmware.zip, where firmware.zip is the firmware you want to flash.
The first time you do this, it will fail saying something like "FAILED (remote: 90 hboot pre-update! please flush image again immediately)". Ignore this, run the last command again: fastboot flash zip firmware.zip
The progress bar will appear and begin filling. Wait until fastboot is finished flashig it (the progress bar may not fill completely), wait an extra 5 seconds or so, and then do fastboot reboot.
The phone will reboot. Android will still be messed up, but you can verify the partitions are in working order by checking adb shell cat /proc/emmc.
Once you know the partitions are working, get back into TWRP/recovery: adb reboot recovery
Format /data and wipe /cache, /data, dalvik/art cache, etc (factory reset). You will lose the contents of your internal storage and everything else.
If you don't have the ROM zip on an sd card, make sure the zip is in the same directory as adb and run adb push rom.zip /sdcard/rom.zip, where rom.zip is the ROM. You can also copy it to the external sd by swapping /sdcard/rom.zip with /external_storage/rom.zip.
Once copied, reboot into recovery and flash the zip. Back to normal!
Update:
It's a firmware problem. Apparently there was a new firmware update that the ROM uses that I don't have. mmcblk0p42 was changed to "vzw_logger" (which I don't have), making mmcblk0p49 userdata instead of previously mmcblk0p48. The data partition it expects to be /data is /cache. Got this information by comparing 'cat /proc/emmc' with information of the latest version I found here.
Is there a way to fix this that allows me to preserve the contents of my internal storage (/sdcard)? Can I just flash an older version of the ROM to backup my data?
Klayderpus said:
Update:
It's a firmware problem. Apparently there was a new firmware update that the ROM uses that I don't have. mmcblk0p42 was changed to "vzw_logger" (which I don't have), making mmcblk0p49 userdata instead of previously mmcblk0p48. The data partition it expects to be /data is /cache. Got this information by comparing 'cat /proc/emmc' with information of the latest version I found here.
Is there a way to fix this that allows me to preserve the contents of my internal storage (/sdcard)? Can I just flash an older version of the ROM to backup my data?
Click to expand...
Click to collapse
I posted a warning about this change in the general section early on. For you to have the partition changes means you are on the newer firmware which doesn't match what you posted above for os. You very likely at this point have nothing left to salvage. Are you on the latest twrp?
dottat said:
I posted a warning about this change in the general section early on. For you to have the partition changes means you are on the newer firmware which doesn't match what you posted above for os. You very likely at this point have nothing left to salvage. Are you on the latest twrp?
Click to expand...
Click to collapse
I am on the latest TWRP, yes. Since this post, I've actually been making good progress in getting the data partition back, or so I think. I've been using dd to copy /dev/block/mntblk0p48 to an image file, but got stuck when I reached the FAT32 limit, so I re-formatted my SD card, except now it's read-only.
Klayderpus said:
I am on the latest TWRP, yes. Since this post, I've actually been making good progress in getting the data partition back, or so I think. I've been using dd to copy /dev/block/mntblk0p48 to an image file, but got stuck when I reached the FAT32 limit, so I re-formatted my SD card, except now it's read-only.
Click to expand...
Click to collapse
If you Dd the entire data partition it's gonna be almost 25 gigs. If you can't mount data in twrp and find anything usable when browsing via adb in twrp there's probably not anything usable in there.
dottat said:
If you Dd the entire data partition it's gonna be almost 25 gigs. If you can't mount data in twrp and find anything usable when browsing via adb in twrp there's probably not anything usable in there.
Click to expand...
Click to collapse
I did a DD before while in ADB and it only got to about 1.3 gigs, but after running the image through e2fsck I actually found some images and downloads. I think there's usable stuff in there and I'd like to at least try to get it. There's family pictures and stuff on there that have some value to me. My SD card is 32 gigs so I could probably do it if anything for the hell of it.
Do you happen to know how I can get the SD card mounted? mount -o rw,remount /dev/block/mmcblk1p1 [some dir] is what I've been trying, but I've been getting either Read only filesystem or Invalid argument.
I might be a little crazy
Klayderpus said:
I did a DD before while in ADB and it only got to about 1.3 gigs, but after running the image through e2fsck I actually found some images and downloads. I think there's usable stuff in there and I'd like to at least try to get it. There's family pictures and stuff on there that have some value to me. My SD card is 32 gigs so I could probably do it if anything for the hell of it.
Do you happen to know how I can get the SD card mounted? mount -o rw,remount /dev/block/mmcblk1p1 [some dir] is what I've been trying, but I've been getting either Read only filesystem or Invalid argument.
I might be a little crazy
Click to expand...
Click to collapse
Its already mounted.. Just boot into TWRP while connected to your PC. Open cmd prompt in your adb directory.
adb shell
cd sdcard
ls
See if your internal SD card contents are listed.
dottat said:
Its already mounted.. Just boot into TWRP while connected to your PC. Open cmd prompt in your adb directory.
adb shell
cd sdcard
ls
See if your internal SD card contents are listed.
Click to expand...
Click to collapse
TWRP lists the internal SD card as being size 0 under Mount -> Select Storage and /sdcard is empty. I re-formatted my external SD card to make a full size image but that's what wasn't mounting.
Klayderpus said:
TWRP lists the internal SD card as being size 0 under Mount -> Select Storage and /sdcard is empty. I re-formatted my external SD card to make a full size image but that's what wasn't mounting.
Click to expand...
Click to collapse
Did you try the repair option for /data listed under wipe in TWRP?
dottat said:
Did you try the repair option for /data listed under wipe in TWRP?
Click to expand...
Click to collapse
Doesn't work. There's a couple of messages about not being able to mount /data and then:
Code:
Repairing Data using e2fsck...
E:Unable to repair '/data'.
E:Error repairing file system.
Klayderpus said:
Doesn't work. There's a couple of messages about not being able to mount /data and then:
Code:
Repairing Data using e2fsck...
E:Unable to repair '/data'.
E:Error repairing file system.
Click to expand...
Click to collapse
try this
adb shell
mount -t ext4 /dev/block/mmcblk0p49 /userdata
df
show me the output of df...
and if to be sure of which firmware you are on.. reboot recovery... and do the following....
adb shell
mount -t ext4 /dev/block/mmcblk0p48 /userdata
df
and show me that DF
I got all of my data back successfully. I'm updating the OP with the steps I did to get it back.
What's the next step? Change firmware? I have a local copy of what I needed from the phone, so anything's game now.
edit: /dev/block/mmcblk0p48 for me is userdata, 49 does not exist. Both mounts fail.
Code:
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 933044 24 933020 0% /dev
tmpfs 933044 20 933024 0% /tmp
/dev/block/mmcblk0p47 1030828 16464 1014364 2% /cache
/dev/block/mmcblk1p1 30647232 12 29090436 0% /external_sd
/dev/block/mmcblk1p1 30647232 12 29090436 0% /and-sec
Klayderpus said:
I got all of my data back successfully. I'm updating the OP with the steps I did to get it back.
What's the next step? Change firmware? I have a local copy of what I needed from the phone, so anything's game now.
edit: /dev/block/mmcblk0p48 for me is userdata, 49 does not exist. Both mounts fail.
Code:
df
Filesystem 1K-blocks Used Available Use% Mounted on
tmpfs 933044 24 933020 0% /dev
tmpfs 933044 20 933024 0% /tmp
/dev/block/mmcblk0p47 1030828 16464 1014364 2% /cache
/dev/block/mmcblk1p1 30647232 12 29090436 0% /external_sd
/dev/block/mmcblk1p1 30647232 12 29090436 0% /and-sec
Click to expand...
Click to collapse
I would say update firmware. Since you confirmed blk48 as user data I know you don't have lollipop firmware.
I posted a firmware zip that contains the newest twrp which is compatible with lollipop in tigerstowns firmware thread. You can use that to update.
Then wipe and reinstall whatever Rom you want to use.
I fixed it this morning by updating firmware and will update the OP with the rest of the steps for the Googlers. Thanks again.
Klayderpus said:
EDIT: For anyone else having a problem like this that at least wants to get their data back, here's what you should do (I assume you know how to work with Linux!):
Make sure you have the latest version of TWRP and ADB.
Boot the phone into recovery mode and connect the phone to your computer via USB
Run "ls -al /dev/block/platform/msm_sdcc.1/by-name" and check the output. Make a note of the partition marked "userdata" - for me, it was /dev/block/mmcblk0p48.
Either: simply use adb pull to copy this file to your computer (this will require about 26 gigs of space), or attempt to mount the file. To use adb pull, execute "adb pull /dev/block/<ID> ./data" (ID being what you marked down). Your data partition will be copied to /data. To mount, use "mount -t ext4 /dev/block/<ID> /userdata". Whatever's left of your data will be on your phone's new /userdata folder.
Use ADB to pull what files you want from /userdata. If you pulled the partition, skip this step.
If you copied the files you wanted over, you're done. If you pulled the entire partition, you're going to want to try and mount it. On Windows, there are various tools to mount Linux partitions, a quick Google will find some good ones. However, if the data is corrupt, it will not work. I recommend attempting to repair the partition on linux, with the command "e2fsck -f -y /path/to/data", replacing the path to your data file as necessary. Once done, run "mount -t ext4 /path/to/data /mnt/data", replacing the paths as necessary.
Once mounted, you can access your data wherever it was mounted. If e2fsck appeared to fix many errors, chances are most of your data will be in the lost+found folder, and you'll need to sort through this yourself. If you're lucky, then your data will be intact and readily usable. Internal SD card data is located at ./media/0.
[/LIST]
Click to expand...
Click to collapse
I have a laptop running Ubuntu: where do I run the "ls -al /dev/block..." command? As in what folder do I need to be in? The phone only appears in an mtp capacity...
EDIT: I figured that out but now I am stuck at "adb pull /dev/block/<ID> ./data". My ID was mmcblk0p28 but the command returns "Bash: mmcblk0p28: no such file or directory exists"
EDIT 2: Got that command to work but the file is too large to write (My disk is FAT32 ). So I then tried the mount command but again got "no such file or directory exists".
Same Issue "Decryption Unsuccessful"
I was trying to apply the OTA update for 5.1 on my M8 converted to GPE 5.01, but had to update to the stock recovery, and found myself in the same situation with the "Decryption Unsuccessful" message.
Following Klayderpus' steps to recover, but I'm running into a few issues:
1) Windows not Ubuntu so some (many) of the commands do not apply.
2) The device is not responding to adb, although it was prior to the "upgrade". Fastboot is working.
3) TWRP was not on the device, in fact I never could get to the recovery after trying to install the stock recovery when I converted to GPE 5.01 many months ago
I have a fresh nandroid backup, so I am just trying to get the device running. Being without the phone is causing me great pain....
I upgraded the firmware to 4.16 and did the factory reset from the stock 4.16 recovery. The phone boots back to the "Decryption Unsuccessful" message.
I am not sure, but I think the next step for me to try is to install the GPE ROM from graffixnyc from the microSD card (need to find/buy that little SD adaptor)
Any help would be greatly appreciated!!
========================
Update;
Recovery does not see the SD card , so I won't be able to install from there.
I'll try flashing TWRP recover to see if that will show the contents of the external card
========================
Update 2:
TWRP does see the external card, but the install failed as it is unable to mount /data and /storage.
I'm out of ideas....HELP!!
========================
Update 3
I noticed the "factory reset" in HBOOT and thought I'd try that instead of the "Wipe" in TWRP, but only made things worse.
Now the phone comes up to the "Decryption Unsuccessful" where I can then take the reset to get it into TWRP recover
TWRP comes up directly into a screen where it's "Running OpenRecovery Script" and then reboots.
I'm going to quit now, as I am only making matters worse.....
========================
Update 4
I got TWRP to quit whatever it was doing.
Now, In TWRP > Wipe > Advanced Wipe, I cannot wipe or repair the Data partition. I see a message "Could not mount /data unable to find crypto footer". Trying to wipe the Davlik Cache fails, "Unable to mount /data, " Unable to mount storage".
========================
version-bootloader: 3.19.0.0000
version-baseband: 1.25.214500021.06G
version-main: 4.16.401.10
modelid: 0P6B12000
cidnum: 11111111
========================
I've bricked the phone and it looks permanent.
I found another thread where everyone was solving this issue running this command "mke2fs -T ext4 /dev/block/mmcblk0p8" in TWRP. I failed to notice that it was not an M8 device thread. The phone won't boot at all, and windows sees it as a usb drive.
Haste makes waste
Do you still have fastboot?
Check out the RUU collection here and grab what apllies to your device:
http://forum.xda-developers.com/ver...zw-m8-master-ruu-firmware-collection-t2946473
Make sure you use the HTC fastboot.exe from post 3
highplains914drifter said:
I was trying to apply the OTA update for 5.1 on my M8 converted to GPE 5.01, but had to update to the stock recovery, and found myself in the same situation with the "Decryption Unsuccessful" message.
Following Klayderpus' steps to recover, but I'm running into a few issues:
1) Windows not Ubuntu so some (many) of the commands do not apply.
2) The device is not responding to adb, although it was prior to the "upgrade". Fastboot is working.
3) TWRP was not on the device, in fact I never could get to the recovery after trying to install the stock recovery when I converted to GPE 5.01 many months ago
I have a fresh nandroid backup, so I am just trying to get the device running. Being without the phone is causing me great pain....
I upgraded the firmware to 4.16 and did the factory reset from the stock 4.16 recovery. The phone boots back to the "Decryption Unsuccessful" message.
I am not sure, but I think the next step for me to try is to install the GPE ROM from graffixnyc from the microSD card (need to find/buy that little SD adaptor)
Any help would be greatly appreciated!!
========================
Update;
Recovery does not see the SD card , so I won't be able to install from there.
I'll try flashing TWRP recover to see if that will show the contents of the external card
========================
Update 2:
TWRP does see the external card, but the install failed as it is unable to mount /data and /storage.
I'm out of ideas....HELP!!
========================
Update 3
I noticed the "factory reset" in HBOOT and thought I'd try that instead of the "Wipe" in TWRP, but only made things worse.
Now the phone comes up to the "Decryption Unsuccessful" where I can then take the reset to get it into TWRP recover
TWRP comes up directly into a screen where it's "Running OpenRecovery Script" and then reboots.
I'm going to quit now, as I am only making matters worse.....
========================
Update 4
I got TWRP to quit whatever it was doing.
Now, In TWRP > Wipe > Advanced Wipe, I cannot wipe or repair the Data partition. I see a message "Could not mount /data unable to find crypto footer". Trying to wipe the Davlik Cache fails, "Unable to mount /data, " Unable to mount storage".
========================
version-bootloader: 3.19.0.0000
version-baseband: 1.25.214500021.06G
version-main: 4.16.401.10
modelid: 0P6B12000
cidnum: 11111111
========================
I've bricked the phone and it looks permanent.
I found another thread where everyone was solving this issue running this command "mke2fs -T ext4 /dev/block/mmcblk0p8" in TWRP. I failed to notice that it was not an M8 device thread. The phone won't boot at all, and windows sees it as a usb drive.
Haste makes waste
Click to expand...
Click to collapse
If you have fastboot do the following commands
Fastboot oem task 28
Fastboot oem task 29
Then try to flash your rom or ruu.
dottat said:
If you have fastboot do the following commands
Fastboot oem task 28
Fastboot oem task 29
Then try to flash your rom or ruu.
Click to expand...
Click to collapse
No Fastboot, nothing. Device was charged, but now acts as if the battery is dead. the Power button does nothing even after a long press.
Bad day...
Klayderpus said:
I previously ran LolliGPE but was long overdue for an update. I downloaded the latest version and copied the image to my phone and flashed the ROM. I decided to go try a dirty install first to see if I could keep everything I had, since I had already been running a previous version and after reviewing the changelog did not see anything recommending to wipe clean. After installing successfully, Android asked me to enter my password to decrypt my data (I don't recall ever encrypting my data?), and so I did. It then told me that my password was right, but the data was corrupt, and presented me a button to reset my phone. The button redirected me to recovery and automatically attempted to wipe /data and then re-mount it, but the wipe failed. I rebooted again with the same issue, same failed attempt to wipe. I went to install the zip again, and this time do a full wipe, but it was unable to mount my phone's storage nor my SD card. I am not able to mount either at all now.
What's the best course of action? I'd like to retain as much as I can and avoid wiping all of the internal storage clean. Is there a simpler fix to this or am I doomed?
HBOOT: 3.19.0.0000
RADIO: 1.09.20.0926
OS: 3.28.605.4
EDIT: For anyone else having a problem like this that at least wants to get their data back, here's what you should do (I assume you know how to work with Linux!):
Make sure you have the latest version of TWRP and ADB.
Boot the phone into recovery mode and connect the phone to your computer via USB
Run "ls -al /dev/block/platform/msm_sdcc.1/by-name" and check the output. Make a note of the partition marked "userdata" - for me, it was /dev/block/mmcblk0p48.
Either: simply use adb pull to copy this file to your computer (this will require about 26 gigs of space), or attempt to mount the file. To use adb pull, execute "adb pull /dev/block/<ID> ./data" (ID being what you marked down). Your data partition will be copied to /data. To mount, use "mount -t ext4 /dev/block/<ID> /userdata". Whatever's left of your data will be on your phone's new /userdata folder.
Use ADB to pull what files you want from /userdata. If you pulled the partition, skip this step.
If you copied the files you wanted over, you're done. If you pulled the entire partition, you're going to want to try and mount it. On Windows, there are various tools to mount Linux partitions, a quick Google will find some good ones. However, if the data is corrupt, it will not work. I recommend attempting to repair the partition on linux, with the command "e2fsck -f -y /path/to/data", replacing the path to your data file as necessary. Once done, run "mount -t ext4 /path/to/data /mnt/data", replacing the paths as necessary.
Once mounted, you can access your data wherever it was mounted. If e2fsck appeared to fix many errors, chances are most of your data will be in the lost+found folder, and you'll need to sort through this yourself. If you're lucky, then your data will be intact and readily usable. Internal SD card data is located at ./media/0.
To fix the partitions and get Android back up and running, you need to install the latest firmware, format your data in TWRP, factory reset, and then flash a ROM again. Here's what I did to do that, without an SD card. If you have an SD card, simply copy your ROM zip to the SD card and skip the final steps:
Make sure you have the latest version of TWRP and ADB, and download the latest copy of the firmware (check the development forum here).
Boot the phone (doesn't matter to what) and run adb reboot bootloader. When your phone reboots, double-check by running fastboot reboot-bootloader.
Put your phone in RUU mode with fastboot oem rebootRUU. The phone will restart and the HTC logo will come up.
Wait a couple seconds, then run fastboot flash zip firmware.zip, where firmware.zip is the firmware you want to flash.
The first time you do this, it will fail saying something like "FAILED (remote: 90 hboot pre-update! please flush image again immediately)". Ignore this, run the last command again: fastboot flash zip firmware.zip
The progress bar will appear and begin filling. Wait until fastboot is finished flashig it (the progress bar may not fill completely), wait an extra 5 seconds or so, and then do fastboot reboot.
The phone will reboot. Android will still be messed up, but you can verify the partitions are in working order by checking adb shell cat /proc/emmc.
Once you know the partitions are working, get back into TWRP/recovery: adb reboot recovery
Format /data and wipe /cache, /data, dalvik/art cache, etc (factory reset). You will lose the contents of your internal storage and everything else.
If you don't have the ROM zip on an sd card, make sure the zip is in the same directory as adb and run adb push rom.zip /sdcard/rom.zip, where rom.zip is the ROM. You can also copy it to the external sd by swapping /sdcard/rom.zip with /external_storage/rom.zip.
Once copied, reboot into recovery and flash the zip. Back to normal!
Click to expand...
Click to collapse
Hey
I have a HTC one m7 verizon & same problem storage decryption failed. See my case here in below post. And please tell me if anything possible. Please......
http://forum.xda-developers.com/verizon-htc-one/help/storage-encryped-htc-one-m7-vzw-s-t3279869
I woke up to find my 1st Generation Moto G battery was depleted and on charging it a bit., I switched it on only to find it optimizing my apps. All these (battery getting depleted, app optimization) happen all the time and I wasn't the least worried.
I picked up my phone later thinking it must have been done with the app optimization only to discover it was totally dead while still connected to a power bank. When I try to switch it on, it is stuck on the "Unlock Bootloader" page. I have tried flashing a new stock rom and it does not work.
I attached the image I see when I try to use recovery to wipe. Basically, nothing works. Can anybody help as I just fixed the screen and also out of warranty?
Fastboot flash the latest Factory Firmware Image for your model.
Factory Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
lost101 said:
Fastboot flash the latest Factory Firmware Image for your model.
Factory Firmware Images: http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Fastboot Tutorial: http://forum.xda-developers.com/showthread.php?t=2542219
Click to expand...
Click to collapse
Thanks lost101, I do know how to flash perfectly well with fastboot. The problem is it flashes successfully but the phone is still stuck on the Bootloader.
I get this particular message on my recovery when I try to wipe either userdata or cache.
blkdiscard on partition /dev/block/platform/msm_sdcc.1/by-name/userdata failed formatting /userdata failed
formatting cache
and
blkdiscard on partition /dev/block/platform/msm_sdcc.1/by-name/userdata failed formatting /cache
wiping clogo
@NaijaAndroid - Can you try booting into TWRP via: fastboot boot twrp.img
lost101 said:
@NaijaAndroid - Can you try booting into TWRP via: fastboot boot twrp.img
Click to expand...
Click to collapse
I do not have a custom recovery presently but when I try to flash TWRP, it flashes successfully with no error message but the phone is still stuck on the stock recovery.
NaijaAndroid said:
I do not have a custom recovery presently but when I try to flash TWRP, it flashes successfully with no error message but the phone is still stuck on the stock recovery.
Click to expand...
Click to collapse
Read again what I told you to do. I did not say for you to flash anything.
@lost101, I just read your instructions again. I can boot in to TWRP. What else should I do after?
Thanks.
NaijaAndroid said:
@lost101, I just read your instructions again. I can boot in to TWRP. What else should I do after?
Click to expand...
Click to collapse
Via PC, do the following wipe: (requires working ADB setup)
http://forum.xda-developers.com/showpost.php?p=65431978&postcount=22
You could then TWRP > Wipe > Format Data > Yes, and try flashing a custom ROM.
Edit: You should backup photos or important data before hand.
I just downloaded CM 12.1. How can I transfer the ROM to the phone?
Edit: I have done it.
NaijaAndroid said:
I just downloaded CM 12.1. How can I transfer the ROM to the phone?
Click to expand...
Click to collapse
Recovery mode ADB will work with Linux - unsure about Windows. You could boot into an Ubuntu LiveCD (without installing) and transfer the ROM to phone that way. Otherwise, an OTG usb pen would be another option.
adb push rom.zip /sdcard
@lost101, I tried to send the Rom via ADB and I got : failed to copy 'Rom.zip' to '/sdcard//Rom.zip' : Read-only file system.
Also, TWRP made my phone to load as MTP on my PC but I could not transfer through that method also. The transfer kept on failing. Seems my internal memory (eMMC) is now Read-only.
NaijaAndroid said:
@lost101, I tried to send the Rom via ADB and I got : failed to copy 'Rom.zip' to '/sdcard//Rom.zip' : Read-only file system.
Also, TWRP made my phone to load as MTP on my PC but I could not transfer through that method also. The transfer kept on failing. Seems my internal memory (eMMC) is now Read-only.
Click to expand...
Click to collapse
Try sideloading the ROM.
TWRP > ADB sideloadadb sideload rom.zip
lost101 said:
Try sideloading the ROM.
TWRP > ADB sideloadadb sideload rom.zip
Click to expand...
Click to collapse
I got:
Installing zip file '/sideload/package.zip'
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
Can't install this package on top of incompatible data. Please try another package or run a factory reset
Updater process ended with ERROR: 7
I was trying to use CM 12.1.
So sorry for taking your time. Thanks.
NaijaAndroid said:
I got:
Installing zip file '/sideload/package.zip'
detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system
Can't install this package on top of incompatible data. Please try another package or run a factory reset
Updater process ended with ERROR: 7
I was trying to use CM 12.1.
Click to expand...
Click to collapse
Try a CM13 ROM.
lost101 said:
Try a CM13 ROM.
Click to expand...
Click to collapse
Same problem as above. I got the same message.
On PC:
adb shelle2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
lost101 said:
On PC:
adb shelle2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata
Click to expand...
Click to collapse
I got:
/dev/block/platform/msm_sdcc.1/by-name/userdata is in use.
e2fsck: Cannot continue, aborting.
NaijaAndroid said:
I got:
/dev/block/platform/msm_sdcc.1/by-name/userdata is in use.
e2fsck: Cannot continue, aborting.
Click to expand...
Click to collapse
TWRP > MOUNT > Untick /Data
lost101 said:
TWRP > MOUNT > Untick /Data
Click to expand...
Click to collapse
got this after unticking data and trying again:
e2fsck 1.42.9 (28-Dec-2013)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/platform
/msm_sdcc.1/by-name/userdata
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
NaijaAndroid said:
got this after unticking data and trying again:
e2fsck 1.42.9 (28-Dec-2013)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open /dev/block/platform
/msm_sdcc.1/by-name/userdata
The superblock could not be read or does not describe a correct ext2
filesystem. If the device is valid and it really contains an ext2
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
Click to expand...
Click to collapse
A certain percentage of phones end up with corrupt emmc (internal storage) over time. This problem is a fairly common thing. I do recall someone managing to boot an use CM13, despite the read-only userdata. I'm guessing they must have flashed it via TWRP, with the ROM.zip on an OTG usb pen. It may have worked because /system was still partially / fully writeable.
Hi, i have the next versions:
CyanogenMod: 13.0-20161004-NIGHTLY-osprey
Kernel: 3.10.49-MPI24.107-56-g09ff0d1
And when trying to install the 1009-NIGHTLY update i get an error without a log in the cianogenmod recovery. When I try to "Apply update" and then "Choose from emulated", it shows the next message:
"E:failed to mount /data (Invalid argument)
Installation aborted"
Then, i go to see the recovery logs, but it blanks and shows the main menu again.
Why do I want to update to the latest version, having 5 days of difference with the installed version?
Because I'm having repeatedly bugs with the Firefox browser, can't update Telegram, can't connect via Bluetooth to the most of the devices, can't update the binaries of SuperSU, and other minor errors.
Which could be the cause of some of this problems?
Sorry for my poor english, Saludos!
Download the latest nightly and before installing wipe the /system /dalvik cache and /cache partition, just be aware that you will need to reflash your gaps package.
Henriquefeira said:
Download the latest nightly and before installing wipe the /system /dalvik cache and /cache partition, just be aware that you will need to reflash your gaps package.
Click to expand...
Click to collapse
Just did what you said, wiped /cache and /system partition, and when the phone reboots it stays in the Motorola logo. Seems that I can't load the installer using USB, because there is no ROM installed.
The good news are that I have access to emulated.
What am I doing wrong?
Gonzon said:
Just did what you said, wiped /cache and /system partition, and when the phone reboots it stays in the Motorola logo. Seems that I can't load the installer using USB, because there is no ROM installed.
The good news are that I have access to emulated.
What am I doing wrong?
Click to expand...
Click to collapse
You wiped your entire internal storage? If not then there is an issue with your internal storage. I once had a similar issue to this, where my phone would keep wiping it's internal storage and crash a lot, the solution was to reflash the stock ROM. Sorry for the inconvenience that I caused to you
Just as a side question, did anyone got AICP nightlies .zip stuck at extracting image to /system? I tried clean install (wipe /system, /data, /cache and dalvik) but its just stuck there. Tried multiple nightlies. Tried deleting Android and .android_secure folders in both external and internal storage. I haven't tried wiping internal storage yet (I will do it ASAP). Any tips will be great. Thanks
Broadcasted from Zeta Reticuli
Henriquefeira said:
You wiped your entire internal storage? If not then there is an issue with your internal storage. I once had a similar issue to this, where my phone would keep wiping it's internal storage and crash a lot, the solution was to reflash the stock ROM. Sorry for the inconvenience that I caused to you
Click to expand...
Click to collapse
I still don't know why cm installs a recovery that it is unstable and with less tools than TWRP. I believe that they should use at least the code of TWRP.
No problem Henriquefeira, everything has it's solution. Besize, your help was too much better than silence in this post. Now, I have to focus on try to enter to the internal storage and flash the update I have.
For that, I'm using fastboot in linux. But I don't know too much about using it. Next, I'll show you the messages that the terminal sent me:
Code:
[email protected]:~$ fastboot -p xxxxxxxxxx flash /data/media /home/imperial/Android2/cmupdater/cm-13.0-20161009-NIGHTLY-osprey.zip
target reported max download size of 268435456 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 91972855 is not a multiple of the block size 4096
fastboot: /build/android-tools-hIu7Bj/android-tools-4.2.2+git20130529/core/libsparse/sparse.c:143: write_all_blocks: Assertion `pad >= 0' failed.
Abortado
Do you know what it means?
Gonzon said:
I still don't know why cm installs a recovery that it is unstable and with less tools than TWRP. I believe that they should use at least the code of TWRP.
No problem Henriquefeira, everything has it's solution. Besize, your help was too much better than silence in this post. Now, I have to focus on try to enter to the internal storage and flash the update I have.
For that, I'm using fastboot in linux. But I don't know too much about using it. Next, I'll show you the messages that the terminal sent me:
Do you know what it means?
Click to expand...
Click to collapse
You can't flash the zip of a ROM via fastboot, follow this tutorial >goo.gl/JfRzZu and on the next time avoid installing the CM bundled recovery
Solved.
I flashed vía fastboot a stable twrp, then after a lot of errors and strange things i was able to flash the ROM.
Thanks a lot for your help.
I was seeing a bricked phone already jajaja.