Related
Got a very strange issue with my I9020T
after flashing DrewGaren ICS Beta2 from Koush Alpha11 with ROM Manager my phone stop on boot, no boot animation, just Google logo on black screen, also no access via adb or fastboot at this time.
Can easy enter to bootloader (volume up+ power) and have fastboot access
can reflash recovery (have tried different version of CWM).
Can enter in CWM recovery (now have V5.0.2.0) and have adb access, but seems no superuser access
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
~ # su
su
/sbin/sh: su: not found
~ #
have tried to reflash different roms (have plenty on SDcard) but same issue, flashing seems to be ok, but hang on reboot
Have tried to flash I9020XXJK1- GRH78 via Odin, again flash is ok (it is replacing CWM recovery with stock (but i can reflash CWM recovery vwith fastboot) BUT again stop on boot (Google logo)
have also nand backup (created few month ago) if trying to restore from CWM getting following
Checking MD5 sums...
Erasing boot before restore...
Restoring boot image...
Restoring system...
Restoring data...
Error while restoring /data!
Show Log from advanced CWM menu show some issues like
tar: can't make dir data/misc/vpn/profiles: Read-only file system
tar: can't remove old file data/misc/systemkeys/AppsOnSd.sks: Read-only file system
AppsOnSd.sksError while restoring /data!
mtd: successfully wrote block at 0
I: Set boot command '''
any idea?
Have you tried wiping data/cache/dalvik-cache?
BTW, where did you get your CWM? AFAIK, the latest version for Nexus S is 5.0.2.0
sure i did full wipe several times
sorry - my CWM is 5.0.2.0
some strange log issues on data wipe
Formatting /cache
Formatting /sd-ext
Formatting /sdcard/.adndroid_secure...
I: Formatting unknown device.
rm: can't remove '.' or '..'
rm: can't remove '.' or '..'
Data wipe complete
mtd: successfully wrote block at 0
I: set boot command ""
Hmm... If I were in your situation, I would try to downgrade or use another recovery, may be this one is a good start.
I'd also try flashing the latest OTA package from this thread.
same issue with new CWM
also unable to copy Stock ROM(Android 2.3.3/GRI40/XXKB1 Radio/KA3 Bootloader) to SD card.
from CWM enter to mount and storage
than
mount sd card
mount USB
can see SDCARD on my PC and even can copy ROM to /sdcard/ BUT
if try to install ZIP (can select copied zip) getting
Finding update package
Opening update package
e: can\t open /sdcard/blablabla.zip
(bad)
Installation aborted
after recovery rebout can not find newly copied rom in /sdcard/
It looks like some partition is read only and not flashed properly
It looks like file system problem but dont know how to fix
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
353255F7992E00EC recovery
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb remount
remount failed: Unknown error: 0
C:\Program Files (x86)\Android\android-sdk\platform-tools>
Have you cosidered reflashing ICS? The problem may be the rom you installed?
arielgb2 said:
Have you cosidered reflashing ICS? The problem may be the rom you installed?
Click to expand...
Click to collapse
Before i have used Koush alfa11, but same issue with any ROM (have tried few ICS and GB available on my SD Card). Even flashed Stock Rom with with Odin
results are same - rom flashed (i can see changes on bootloader and baseband version from bootloader menu)
but after reboot - same
Google logo with lock at the bottom, after few sec brightness increased and key backlighted... and nothing
Did you remember to wipe the /system partition when going from GB to ICS?
Greetz
frutelaken said:
Did you remember to wipe the /system partition when going from GB to ICS?
Greetz
Click to expand...
Click to collapse
always wipe data/cache/dalvik/
Yes, good, but if you go from GB to ICS, you need to format the /system partition too.
Can be done in 'mounts and storage'.
Greetz
frutelaken said:
Yes, good, but if you go from GB to ICS, you need to format the /system partition too.
Can be done in 'mounts and storage'.
Greetz
Click to expand...
Click to collapse
you dont have to format anything. a simple wipe data/factory reset works just fine.
You should.
I had got stuck at the Google bootscreen trying to do it without a /system format. After I formatted it the ROM booted nicely.
I just verified and all the ICS installation nodes advise to format system, too. Since he's encountering this issue it wouldn't hurt him to try and do the full monty
Greetz
frutelaken said:
You should.
I had got stuck at the Google bootscreen trying to do it without a /system format. After I formatted it the ROM booted nicely.
I just verified and all the ICS installation nodes advise to format system, too. Since he's encountering this issue it wouldn't hurt him to try and do the full monty
Greetz
Click to expand...
Click to collapse
did try everything, can change bootloaders, can flash stock with odin, can restore previously saved backup (with error on data recovery, but i think it should start anyway). BUT always stopped on on reboot at google logo.
Also can mount USB from recovery menu and copy any files from SD card to PC, but any file copied from pc to SD card dissapear after reboot.
It looks like some system file mounting problem
Same boat!
oxothuk_uae said:
It looks like some system file mounting problem
Click to expand...
Click to collapse
FWIW, I seem to be in the same boat today!
NS4G -
I had been successfully bouncing between Koush's rlasalle15 port and AOSP, with no issues. Today got stuck in boot screen.
Tried recovery from CWM 5.0.2.0, no luck, as it doesn't see the SD card.
Tried wipe data/factory, I get this error:
e:format_volume:make_extf4fs failed on /dev/block/platform/s3c-sdhci.0/by-name/userdata
and an error formatting /sdcard/.android_secure!
so, data wipe completes, but something is going on here.
---------- Post added at 08:43 PM ---------- Previous post was at 07:50 PM ----------
So, mine is resolved, although I dont know why.
I connected the NS4g via USB and sat at recovery.
I went into ADB into ADB Shell to see what was up/
There was my /sdcard directory, but it was empty.
OK so the issue is somehow its shot, so I'll just create the clockworkmod folders and then push in my last revoery directory, since I moved a copy to my PC.
Halfway through the push, I get a protocol error, the USB on the PC starts singing (installed uninstall bonks) my screen go blank on the phone.
I do a battery pull and .......
Everything is fine! I get back into my last image on a normal boot, and can see my SD card fine.
WHat is strange is the files I copied during the ADB push are not there, so something is still funky in the file system, but so far, I am back up!
here is what I did:
C:\Users\xxxxxx>adb shell
~ # cd /sdcard
cd /sdcard
/sdcard # mkdir clockworkmod
mkdir clockworkmod
/sdcard # cd clockworkmod
cd clockworkmod
/sdcard/clockworkmod # mkdir recovery
mkdir recovery
/sdcard/clockworkmod # cd recovery
cd recovery
/sdcard/clockworkmod/recovery # mkdir bl
mkdir bl
/sdcard/clockworkmod/recovery # push "C:\Users\xxxxxx\Documents\Nexus-S-Backups\clockworkmod\backup\bl"
C:\Users\xxxxxx>adb push "C:\Users\xxxxxx\Documents\Nexus-S-Backups\clockworkmod\backup\bl" /sdcard/clockworkmod/recovery/bl
push: C:\Users\xxxxxx\Documents\Nexus-S-Backups\clockworkmod\backup\bl/system.ext4.tar -> /sdcard/clockworkmod/recovery/bl/system.ext4.tar
push: C:\Users\xxxxxx\Documents\Nexus-S-Backups\clockworkmod\backup\bl/recovery.img -> /sdcard/clockworkmod/recovery/bl/recovery.img
push: C:\Users\xxxxxx\Documents\Nexus-S-Backups\clockworkmod\backup\bl/nandroid.md5 -> /sdcard/clockworkmod/recovery/bl/nandroid.md5
push: C:\Users\xxxxxx\Documents\Nexus-S-Backups\clockworkmod\backup\bl/data.ext4.tar -> /sdcard/clockworkmod/recovery/bl/data.ext4.tar
protocol failure
schreibman said:
FWIW, I seem to be in the same boat today!
NS4G -
I had been successfully bouncing between Koush's rlasalle15 port and AOSP, with no issues. Today got stuck in boot screen.
Tried recovery from CWM 5.0.2.0, no luck, as it doesn't see the SD card.
Tried wipe data/factory, I get this error:
e:format_volume:make_extf4fs failed on /dev/block/platform/s3c-sdhci.0/by-name/userdata
and an error formatting /sdcard/.android_secure!
so, data wipe completes, but something is going on here.
---------- Post added at 08:43 PM ---------- Previous post was at 07:50 PM ----------
So, mine is resolved, although I dont know why.
I connected the NS4g via USB and sat at recovery.
I went into ADB into ADB Shell to see what was up/
There was my /sdcard directory, but it was empty.
OK so the issue is somehow its shot, so I'll just create the clockworkmod folders and then push in my last revoery directory, since I moved a copy to my PC.
Halfway through the push, I get a protocol error, the USB on the PC starts singing (installed uninstall bonks) my screen go blank on the phone.
I do a battery pull and .......
Everything is fine! I get back into my last image on a normal boot, and can see my SD card fine.
WHat is strange is the files I copied during the ADB push are not there, so something is still funky in the file system, but so far, I am back up!
here is what I did:
C:\Users\xxxxxx>adb shell
~ # cd /sdcard
cd /sdcard
/sdcard # mkdir clockworkmod
mkdir clockworkmod
/sdcard # cd clockworkmod
cd clockworkmod
/sdcard/clockworkmod # mkdir recovery
mkdir recovery
/sdcard/clockworkmod # cd recovery
cd recovery
/sdcard/clockworkmod/recovery # mkdir bl
mkdir bl
/sdcard/clockworkmod/recovery # push "C:\Users\xxxxxx\Documents\Nexus-S-Backups\clockworkmod\backup\bl"
C:\Users\xxxxxx>adb push "C:\Users\xxxxxx\Documents\Nexus-S-Backups\clockworkmod\backup\bl" /sdcard/clockworkmod/recovery/bl
push: C:\Users\xxxxxx\Documents\Nexus-S-Backups\clockworkmod\backup\bl/system.ext4.tar -> /sdcard/clockworkmod/recovery/bl/system.ext4.tar
push: C:\Users\xxxxxx\Documents\Nexus-S-Backups\clockworkmod\backup\bl/recovery.img -> /sdcard/clockworkmod/recovery/bl/recovery.img
push: C:\Users\xxxxxx\Documents\Nexus-S-Backups\clockworkmod\backup\bl/nandroid.md5 -> /sdcard/clockworkmod/recovery/bl/nandroid.md5
push: C:\Users\xxxxxx\Documents\Nexus-S-Backups\clockworkmod\backup\bl/data.ext4.tar -> /sdcard/clockworkmod/recovery/bl/data.ext4.tar
protocol failure
Click to expand...
Click to collapse
but path for my recovery was
....clockworkmod\backup\2011-11-20.15.12.14\
should i create same backup dir?
oxothuk_uae said:
but path for my recovery was
....clockworkmod\backup\2011-11-20.15.12.14\
should i create same backup dir?
Click to expand...
Click to collapse
So, understand mine didn't even 'work', so sure, try it and see. My orig back up was a date like your one as well, I just changed it to make it shorter.
Remember it bombed on my on the PUSH, then everything started to work.
SOMETHING is STILL no 'right', as it is hit or miss if I can even get back into CWM (as of now, no I can't), and 1/2 the time I get stuck booting.....
SO, I'm not completly clean, I'd love to know the ADB commands to do a complete reformat of everything on my NS4g SD card, as I think this has something to do with either the new ICS change to MTP .vs. USB mass storage, or maybe the difference between the koush port and the AOSP port. but I think I got some issues still to iron out.
schreibman said:
So, understand mine didn't even 'work', so sure, try it and see. My orig back up was a date like your one as well, I just changed it to make it shorter.
Remember it bombed on my on the PUSH, then everything started to work.
SOMETHING is STILL no 'right', as it is hit or miss if I can even get back into CWM (as of now, no I can't), and 1/2 the time I get stuck booting.....
SO, I'm not completly clean, I'd love to know the ADB commands to do a complete reformat of everything on my NS4g SD card, as I think this has something to do with either the new ICS change to MTP .vs. USB mass storage, or maybe the difference between the koush port and the AOSP port. but I think I got some issues still to iron out.
Click to expand...
Click to collapse
i have same empty /sdcard on adb shell
but can not push
seems problem can be fixed with full reformat or re-partintion memory
anyway push return this
push
/sbin/sh: push: not found
oxothuk_uae said:
i have same empty /sdcard on adb shell
but can not push
seems problem can be fixed with full reformat or re-partintion memory
anyway push return this
push
/sbin/sh: push: not found
Click to expand...
Click to collapse
Just for grins, try this:
Battery pull.
Insert battery
Hold volume down and power on.
if no luck try
adb shell
cd /sdcard
mkdir /foo
and see if it sees the sdcard
schreibman said:
Just for grins, try this:
Battery pull.
Insert battery
Hold volume down and power on.
if no luck try
adb shell
cd /sdcard
mkdir /foo
and see if it sees the sdcard
Click to expand...
Click to collapse
again
I CAN BOOT into recovery
can adb but any file copied to any dir DISAPPEAR after reboot
Mount comand return
Code:
mount -w
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nodev,noatime,nodiratime)
/dev/block/platform/s3c-sdhci.0/by-name/userdata on /data type ext4 (rw,relatime,barrier=1,data=ordered)
/dev/block/platform/s3c-sdhci.0/by-name/system on /system type ext4 (rw,relatime,barrier=1,data=ordered)
/dev/block/platform/s3c-sdhci.0/by-name/media on /sdcard type vfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
~ #
Hi all,
I'm here because I need your help...
Days ago I installed on my TF101G the recovery CWM 5.8.1.8...
now I can just go into recovery mode and if I try to mount /data I receive the message "no location found"...
how can I push a Rom on my TF to try to install it?
thanks in advance for your help
how to flash a ROM
The ROM to be flashed must be cwm flashable, you cannot flash official firmware unless it is repacked to be cwm flashable.
Your ROM must be a zip file, do not unzip it.
Copy (or adb push) the ROM to /sdcard/
Reboot tab into recovery.
Follow cwm flash instructions. There are many such a manual available on-line, one of them is:
http://www.addictivetips.com/mobile...-and-how-to-use-it-on-android-complete-guide/
You can just jump to section "apply update from sdcard", which tells you how to use cwm recovery to flash a ROM
One thing you should pay attention is:
if the ROM to be flashed is only a update to your current ROM, do not do any wipe work.
If it is a new ROM, you must do the wipe.
You can also try this....
hi Fenice82,
read this forum
http://forum.xda-developers.com/showthread.php?t=1213723
and read message 1 and 313 for mounting and the adb commands for sending cmw flash file to your internal card of your TF.
Make sure you have the cwm flashable rom file on you computer in the adb dir.
good luck.
I'm hege again...
thk nlheiz for your post...
I push the rom in my TF... I tried different location...
data/media
or
data
or
system
or
sdcard
or
sdcard/rom
if I go in adb shell and I use command mkdir to make a new folder like system,data,sdcard I see the the file already exist...
but my tf "can't mount /sdcard/" and at the same time if i try to mount /data from recovery I see the message
"Error mounting /data!"
what can I do now?
edit... maybe this can help you...
via ADB shell
mount data
mount: mounting /dev/block/mmcblk0p7 on /data failed: Invalid argument
How about restore stock recovery and ROM? Here is a recent guide for root/unroot/downgrading:
http://forum.xda-developers.com/showthread.php?t=1622628
I don't have experience with cwm 5.8.1.8, I stayed on 3.2.0.1 because it is possible to flash from external sdcards.
cold you try this:
put our tablet into cwm (volume - plus power and when asked volume +) and connect it to usb on pc.
then on your pc:
adb devices
this should give you a serial number back.....
then try this:
to mount the internal sdcard so that you can push a new rom- use
adb shell
mount /dev/block/mmcblk0p7 /data/
ls /sdcard/
exit
then from your pc, type:
adb push /path/to/your/rom.zip /data/media
I found this here http://forum.xda-developers.com/showthread.php?p=23256536 in post 3......
let me know if this works
e154037 said:
How about restore stock recovery and ROM? Here is a recent guide for root/unroot/downgrading:
http://forum.xda-developers.com/showthread.php?t=1622628
Click to expand...
Click to collapse
thk man... with method 3 I installed new recovery and with it I installed the official update, from external storage, that recovery my tablet...pdate
before official update I tried to install other custom rom but I incurred in encryption problem... with official after the fist boot it automatically resolved the problem
I'm very happy
thk again
Current Situation: Cannot mount /sdcard, /emmc and /data. CWM 6.0.2.3 installed. Can ADB and fastboot into tablet. No rom installed.
I installed CM10 stable but wouldn't run properly since Trebuchet kept crashing preventing me to proceed any further and superuser was corrupted, so now I tried to erase everything so I can start a fresh install but must of done something wrong in the process. Any suggestions to restoring stock rom on my TF300T?
Thanks in advance.
Anybody?
I can access /data now, but /emmc and /sdcard are unable to be accessed or formatted by CWM and fasboot. When I tried 'fastboot -i 0x0B05 flash boot boot.blob' then 'fastboot reboot' it just showed the asus logo with device UnLocked. 'fastboot update WW.zip' which is the 4.1.2 stock rom, and 'adb sideload update.zip' wouldn't work cause it cannot mount /sdcard. Tried formatting from fastboot but it also couldn't format /sdcard and /emmc then did flashall which this came up as error: 'error: could not load android-info.txt: No error'. How come /sdcard is the only thing that's not working?
Fixed it.
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 have bought an gt-n8010, which has lineage os installed, but doesn't boot (just splash screen).
So i tried odin to flash the stock rom, but it failed any writing process on the device. In Download mode there is some info written:
ODIN MODE
PRODUCT NAME: GT-N8010
CURRENT BINARY: Custom
SYSTEM STATUS: Official (What does it mean? Does it mean the Bootloader is locked and the device is bricked?)
RP SWREV: A2
But twrp (2.8.7.0 or so) is/was installed, so i booted into recovery and tried to install other custom roms, but it also failed. "Can't state /data/media".
The File Manager in TWRP shows /data but couldn't enter /data/media.
I remounted /data as RW (at least i thought first, that i did) and the file manager could show me /data/media and i thought i was sucessfull.
But the ROM i had, didn't want to install (it thought this was the wrong hardware) and the /data folder was still mounted Readonly (/cache too).
I loaded another ROM, but that needed a newer TWRP.
So i tried flashing TWRP through TWRP and failed. Tried with Odin and Failed. Tried with the DD command within TWRP and failed.
I realised /cache and /data were still mounted read only (and i assume that this is the same problem in Download Mode when trying to flash with Odin)
So, has anyone any suggestion why i can't get /data and /cache mounted in RW mode and has a solution?
Or are these just symtoms of a locked bootloader.
Finally i got it mounted rw (both Cache and and data) und could copy a file to the /data/media folder, by umount and then mount manually.
Still i either need to upgrade twrp or get a ROM which works with twrp v2.8.7.0, so any suggestions? May be dd with the right /dev/blk.... instead of "dd if=/external_sd/twrp.img of=/dev/block/platform/dw_mmc/by-name/RECOVERY" (fails with writing with I/O Error) may work. But i don´t know which one it is.
Pauleberber said:
I realised /cache and /data were still mounted read only (and i assume that this is the same problem in Download Mode when trying to flash with Odin)
Click to expand...
Click to collapse
I would try to flash a recent TWRP from in the download mode and see if this works.
If there's still the old TWRP after the flash than your eMMC is locked and needs to get replaced.
Is there any other possibility to flash from Download Mode except from Odin3 which i already tried. (Adb doesn´t seem to work detects no devices, fastboot neither).
And why does twrp mount /cache und /data read only on start up?
I also thought that something may be locked, but finally i could mount it RW in twrp by mounting it manually by using umount and mount with tha same options except rw instat of ro.
Pauleberber said:
Is there any other possibility to flash from Download Mode except from Odin3 which i already tried. (Adb doesn´t seem to work detects no devices, fastboot neither).
Click to expand...
Click to collapse
Sure, you could use heimdall (linux). But Odin 3.09 should work fine for example.
Does it even detect your device?
Yes it detects the device, it connects to the device but it seems it can´t write anything. I´ll post a screenshot later.