p6800 16 gb internal sd-card bugs - Galaxy Tab 7.7 Q&A, Help & Troubleshooting

There is a problem. Tablet worked on paranoid 4.1.2. However, after some time began to go into a reboot. And when it started to reboot read \ write sd-card partition (internal memory). Then he reboot directly with the logo OS. Restoring from a backup - reboot. In cwm firmware to produce results.
Saved only - pit + odin + stock ics. All data is jammed. 3 weeks later - again, on the same firmware (2.53 paranoid) started rebooting when accessing the sd-card. Again pit + odin + stock solved the problem.
What could be the problem?

you might have a corrupt partition...

edan1979 said:
you might have a corrupt partition...
Click to expand...
Click to collapse
And what can I do with it?

madosis said:
And what can I do with it?
Click to expand...
Click to collapse
Use ADB shell to scan and repair errors with your /data partition.
Follow part 3 of this guide to check and repair errors with your /data partition. 3) Meet another good friend : e2fsck
http://forum.xda-developers.com/showthread.php?t=1862294

Related

[Q]My 9003 is broken

My 9003 can't work from last week.
I just got the "com.sec.android.app.twlaucher" broken(force close) and all other applications are also broken even I flashed with any new ROM.
The whole broken story is here:
1. I installed XXKPQ with CWM, and created a backup with CWM
2. Then flashed it with DDKP2 by Odin
3. I got a application broken, and tried to backup DDKP2 with CWM and stopped by incident
4. I tried to restore OS with the backup in step 1
5. I got many Force Close after I restored the OS
6. I tried to flash with any ROM, but always got Force close for any application(even the com.sec.android.phone)
Can anyone give advice for it?
Or I have to change a new memory chip?
Thanks!
realcode said:
My 9003 can't work from last week.
I just got the "com.sec.android.app.twlaucher" broken(force close) and all other applications are also broken even I flashed with any new ROM.
The whole broken story is here:
1. I installed XXKPQ with CWM, and created a backup with CWM
2. Then flashed it with DDKP2 by Odin
3. I got a application broken, and tried to backup DDKP2 with CWM and stopped by incident
4. I tried to restore OS with the backup in step 1
5. I got many Force Close after I restored the OS
6. I tried to flash with any ROM, but always got Force close for any application(even the com.sec.android.phone)
Can anyone give advice for it?
Or I have to change a new memory chip?
Thanks!
Click to expand...
Click to collapse
Dont restore the backup of one firmware over another firmware.
Flash xxkpe twice aand over it flash xxkpq with factory reset after flashing each time. Use this guideforum.xda-developers.com/showthread.php?t=1133787
Sent from my GT-I9003
I tried to format the data, but it didn't work. I can see the previous installed application broken even I flashed with new ROM(Re-partion).
It seems something was locked by system.
Follow this guide to flash XXKPQ Check if everything works well. Try to restore your CWM backup
I tried to flash XXKPE/XXKPQ, but I got a wrong message "E: failed to mount /data (Invalid argument)" when the phone startup".
And the phone repeated to restart, I can't the normal phone.
It seems there is something wrong with the partion of /data.
Is there other way to fix it?
the /data is ext4, I am not sure XXKPQ support ext4 or not.
When flashing XXKPE with pit and all the other stuff you should see Re-Partition checked. Then everything should be formatted with the standard RFS filesystem unless you convert it. The stock Kernel doesn't support ext4, but that doesn't mean that you can't try to flash a Kernel that supports ext4.
Did you let the phone boot up completly after every flash?
I didn't let XXKPE boot up completely after flash.
It seems that the /data partion was not reset in flashing with the "Re-partion" selected.
I got error message when I tried to check the disk status.
/sbin # fsck.ext4 /dev/block/mmcblk0p3
fsck.ext4 /dev/block/mmcblk0p3
e2fsck 1.41.6 (30-May-2009)
/dev/block/mmcblk0p3: recovering journal
fsck.ext4: unable to set superblock flags on /dev/block/mmcblk0p3

partitions seem to be locked, cant format

i had a recent soft brick in which for some reason, i couldnt decrypt, with this, i couldnt load anything on android besides twrp and fastboot.. when i try reformatting and wiping data, it seems to fail.. for example, i go to format with twrp and it hangs, if i try installing anything itll fail to load any data onto that partition.. if i could reformat that partition back to its useful state, without the encryption issue i could reinstall a rom and fix this issue
any ideas?
when i attempt to do anything in twrp.. i get this error
Updating partition details
E: error opening ' /data/media '
E: error: No such file or directory
just a test, i tried to create a new folder in /data, and it says its a read-only filesystem
jason41987 said:
i had a recent soft brick in which for some reason, i couldnt decrypt, with this, i couldnt load anything on android besides twrp and fastboot.. when i try reformatting and wiping data, it seems to fail.. for example, i go to format with twrp and it hangs, if i try installing anything itll fail to load any data onto that partition.. if i could reformat that partition back to its useful state, without the encryption issue i could reinstall a rom and fix this issue
any ideas?
when i attempt to do anything in twrp.. i get this error
Updating partition details
E: error opening ' /data/media '
E: error: No such file or directory
just a test, i tried to create a new folder in /data, and it says its a read-only filesystem
Click to expand...
Click to collapse
Your partition is probably encrypted. The only way to access to your data is to decrypt it before you can do anything. Do you have a password for it?
LetMeKnow said:
Your partition is probably encrypted. The only way to access to your data is to decrypt it before you can do anything. Do you have a password for it?
Click to expand...
Click to collapse
no, any way i can erase all the data, the partition and start fresh?
jason41987 said:
no, any way i can erase all the data, the partition and start fresh?
Click to expand...
Click to collapse
"Format data" should do this. In which way doesn't it work for you?
_that said:
"Format data" should do this. In which way doesn't it work for you?
Click to expand...
Click to collapse
when i attempt to format data, format fails, it will not let me touch the /data partition, when it does mount, it mounts as read-only.. the partition itself, possibly partition table or something is damaged because it cannot be formatted and nothing can be written to it
it would seem like the internal storage is screwed.. but the other partitions seem to work fine, even able to use command-line from twrp to check fstab and try to mount manually... im not sure how to completely delete and recreate a partition in fdisk, if possible on here
jason41987 said:
when i attempt to format data, format fails
Click to expand...
Click to collapse
No error message? No log file? Just "fails"?
You could try running "/sbin/make_ext4fs /dev/block/mmcblk0p8" manually from adb shell.
jason41987 said:
it would seem like the internal storage is screwed.. but the other partitions seem to work fine, even able to use command-line from twrp to check fstab and try to mount manually... im not sure how to completely delete and recreate a partition in fdisk, if possible on here
Click to expand...
Click to collapse
You can't use fdisk on the internal storage - it uses a combination of GPT and a proprietary partition table.
_that said:
No error message? No log file? Just "fails"?
You could try running "/sbin/make_ext4fs /dev/block/mmcblk0p8" manually from adb shell.
You can't use fdisk on the internal storage - it uses a combination of GPT and a proprietary partition table.
Click to expand...
Click to collapse
the errors i receive are above..trying different things ive received the error that the partition is write one... are there any tools for redoing the entire internal storage?
maybe this could work.. since the other partitions seem to work just fine, as they were not encrypted, what if i edited fstab to mount partitions on a MicroSD card pre-partitioned to act as /data and /cache, then install a rom... unless there are ROMs designed to utilize an external SD for installation?... either way if i can work around these two partitions i could get into a working android system where i can find more tools to assist in removing and recreating those broken partitions
ive considered trying to use fastboot to replace the twrp recovery with a stock asus recovery partition and try to fix the issue from that, but i doubt that would be of any use
jason41987 said:
ive considered trying to use fastboot to replace the twrp recovery with a stock asus recovery partition and try to fix the issue from that, but i doubt that would be of any use
Click to expand...
Click to collapse
Instead you should try it cause i'm pretty sure it will fix your partition.Just install the stock recovery and do a Wipe Data first. If all goes well you can go ahead and flash a stock rom from MicroSD or install the TWRP again and check if it's working.
Here you can find the latest stock recovery - - > http://forum.xda-developers.com/showthread.php?p=44280630
Pretoriano80 said:
Instead you should try it cause i'm pretty sure it will fix your partition.Just install the stock recovery and do a Wipe Data first. If all goes well you can go ahead and flash a stock rom from MicroSD or install the TWRP again and check if it's working.
Here you can find the latest stock recovery - - > http://forum.xda-developers.com/showthread.php?p=44280630
Click to expand...
Click to collapse
are you saying write over twrp with the stock recovery partition with fastboot, then boot into the recovery partition from the power + volume down menu and see if that recovery image will reset to factory defaults?... if so, where would i even get that recovery image?.. and if you mean just try installing a stock rom through TWRP, ive already been there, done that, and it hangs on formatting
jason41987 said:
are you saying write over twrp with the stock recovery partition with fastboot, then boot into the recovery partition from the power + volume down menu and see if that recovery image will reset to factory defaults?... if so, where would i even get that recovery image?.. and if you mean just try installing a stock rom through TWRP, ive already been there, done that, and it hangs on formatting
Click to expand...
Click to collapse
If you follow the link i posted previously you will find the stock recovery (from the latest asus firmware) as an attachment to that post.
After you flash it via Fastboot, do a Wipe Data from the bootloader menu (the one with the 3 icons) after that just follow "restore with stock recovery" procedure from my All in One Thread (it's a sticky post under General Forum).
That should fix your issue and get you to a new clean starting point.
Pretoriano80 said:
If you follow the link i posted previously you will find the stock recovery (from the latest asus firmware) as an attachment to that post.
After you flash it via Fastboot, do a Wipe Data from the bootloader menu (the one with the 3 icons) after that just follow "restore with stock recovery" procedure from my All in One Thread (it's a sticky post under General Forum).
That should fix your issue and get you to a new clean starting point.
Click to expand...
Click to collapse
well, ill try that as soon as i wake up.. if it doesnt work though i am prepared to install something thatll run those partitions of an external microsd though.. wonder why no roms exist specifically for that?... seems like an ultra-secure rom for the ultra-paranoid to be able to pop out their microsd and hide it with all user data stored on it
jason41987 said:
well, ill try that as soon as i wake up.. if it doesnt work though i am prepared to install something thatll run those partitions of an external microsd though.. wonder why no roms exist specifically for that?... seems like an ultra-secure rom for the ultra-paranoid to be able to pop out their microsd and hide it with all user data stored on it
Click to expand...
Click to collapse
Data2SD already exists.
Did you already try to format your data partition from adb shell?
data2sd seems to be something thats applied after a rom is successfully installed, not sure that would help me
anyway, i tried the stock recovery image and it just hangs on an android graphic with a rotating blue wireframe inside its chest and a blue progress bar, but it doesnt actually do anything else
edit: wait a minute.. i see how this goes with the data2sd... i download a data2sd kernal, since i install cleanrom i can add this to the installations list of kernals, the data2sd kernal will mount external SD cards as the /data, cache, and sdcard partitions, allowing me to bypass the issue im having completely and use a 64gb microsd card as my primary storage... very interesting indeed
aah, fantastic, cant even get into fastboot mode to put twrp back on for the data2sd method.. so it would seem now my tablet is COMPLETELY toast
jason41987 said:
aah, fantastic, cant even get into fastboot mode to put twrp back on
Click to expand...
Click to collapse
What happens when you try?
_that said:
What happens when you try?
Click to expand...
Click to collapse
when i hold power and volume down it goes straight to the robot with the blue spinning wireframe graphic,, i dont get an option to go to fastboot.. i can also use power and volume up to go into apx mode but no idea what thats even used for as i find very little reference to it online
jason41987 said:
when i hold power and volume down it goes straight to the robot with the blue spinning wireframe graphic,, i dont get an option to go to fastboot..
Click to expand...
Click to collapse
I see, that's forced boot to recovery because of "wipe data" selected from the bootloader menu.
I don't know how long wiping data takes, maybe you are just not patient enough to let it finish?
_that said:
I see, that's forced boot to recovery because of "wipe data" selected from the bootloader menu.
I don't know how long wiping data takes, maybe you are just not patient enough to let it finish?
Click to expand...
Click to collapse
no, it finished, then said it was booting the recovery image afterwards, then i let it sit for about 2 hours when i went to do something else and it hanged on that screen... no way to fix this from apx mode?
jason41987 said:
no way to fix this from apx mode?
Click to expand...
Click to collapse
APX mode is only useful if you have nvflash, the wheelie tool, and the blob file for your device, which you'd have needed to create with firmware 9.4.5.26 or earlier and the hacked bootloader from androidroot.mobi.

[Q] Help i may have doomed my tablet.

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

Error trying to wipe Internal Storage (TWRP)

Hi, I tried to do a full wipe from TWRP, but I was unable to wipe Interal Storage, next message appeared:
E:mount -o bind '/data/media/0' '/sdcard' process ended with ERROR=255
Anyways, the message of succesfull wipe appeared (and internal storage was in fact wiped). I don't know if I should worry (everything works fine after installing CM.12.1 nightly 08/06). The previous firmware installed was OxygenOs (I had a remote session thinking they would accept a RMA but they instead installed Oxygen with the latest drivers ). Every time I try to wipe that partition again I get the same message (but it gets wiped).
Thanks for your help and sorry for my english!
trionic said:
Hi, I tried to do a full wipe from TWRP, but I was unable to wipe Interal Storage, next message appeared:
E:mount -o bind '/data/media/0' '/sdcard' process ended with ERROR=255
Anyways, the message of succesfull wipe appeared (and internal storage was in fact wiped). I don't know if I should worry (everything works fine after installing CM.12.1 nightly 08/06). The previous firmware installed was OxygenOs (I had a remote session thinking they would accept a RMA but they instead installed Oxygen with the latest drivers ). Every time I try to wipe that partition again I get the same message (but it gets wiped).
Thanks for your help and sorry for my english!
Click to expand...
Click to collapse
hey and welcome ,
you should always install the newest Twrp. Just download it via playstore
an other method. Download multirom and install twrp from there.
For the next time. Wipe partitions. Try to repair theme and flash it back to ext4.
Now everything should be clean.
If your system runs without any problemes or issues its just a cosmetic issue not more.
regards
Are you using latest 2.8.6.0/2.8.6.1?
davebugyi said:
Are you using latest 2.8.6.0/2.8.6.1?
Click to expand...
Click to collapse
real_pac said:
hey and welcome ,
you should always install the newest Twrp. Just download it via playstore
an other method. Download multirom and install twrp from there.
For the next time. Wipe partitions. Try to repair theme and flash it back to ext4.
Now everything should be clean.
If your system runs without any problemes or issues its just a cosmetic issue not more.
regards
Click to expand...
Click to collapse
I am using 2.8.6.1 (latest version). Unfortunately twrp doesn't allow me to repair / format that partition.
Thanks you both for your response
trionic said:
I am using 2.8.6.1 (last version). Unfortunately twrp doesn't allow me to repair / format that partition.
Thanks you both for your response
Click to expand...
Click to collapse
You're welcome but please don't a new thread write in the specific thread..
please reinstall twrp via playstore flashable zip or just flash the recovery img via adb or any oneplus one toolkit regards
real_pac said:
You're welcome but please don't a new thread write in the specific thread..
please reinstall twrp via playstore flashable zip or just flash the recovery img via adb or any oneplus one toolkit regards
Click to expand...
Click to collapse
I installed again with TWRP Manager and everything works perfectly now (no error message). Thanks again
trionic said:
Hi, I tried to do a full wipe from TWRP, but I was unable to wipe Interal Storage, next message appeared:
E:mount -o bind '/data/media/0' '/sdcard' process ended with ERROR=255
[...]
Click to expand...
Click to collapse
I faced this error once on twrp 2.8.6.1 a week ago. I wanted to restore my nandroid and the error repeatedly happened while restoring data-partition. I then booted the system and deleted some files from internal storage (which was about half full at the time the error occurred). Afterwards I rebooted to twrp and could successfully restore my complete nandroid. It's a bit shocking if you face this error when restoring a nandroid, because the restore process wipes the data partition first and then begins the restore.
real_pac said:
hey and welcome ,
you should always install the newest Twrp. Just download it via playstore
an other method. Download multirom and install twrp from there.
For the next time. Wipe partitions. Try to repair theme and flash it back to ext4.
Now everything should be clean.
If your system runs without any problemes or issues its just a cosmetic issue not more.
regards
Click to expand...
Click to collapse
That tip worked for me (i9192), I just install the last TWRP (I think this is not needed) and wipe /Data with ext4, wipe again to F2FS and restore, thank you.

unable to mount /system /data /cache internal storage

can any one help me
what i did was, formatting the system ,data partion using wipe option in recovery (twrp), by mistake the battery got removed during the process since then the problem occured..
my yuphoria device stuck on the boot logo
is not able to mount /system /data /cache and internal storage
it is booting in fastboot mode as well as in recovery but i m not able to flash any rom, in recovery its giving the error as unable to mount /system /data /cache, showing 0mb space in internal storage and system
i also tried to flash using fastboot but giving error at the system partition sowing system write failure.. can some one identify provide me with the solution .. thanks
Same problem
harshgoswami said:
can any one help me
what i did was, formatting the system ,data partion using wipe option in recovery (twrp), by mistake the battery got removed during the process since then the problem occured..
my yuphoria device stuck on the boot logo
is not able to mount /system /data /cache and internal storage
it is booting in fastboot mode as well as in recovery but i m not able to flash any rom, in recovery its giving the error as unable to mount /system /data /cache, showing 0mb space in internal storage and system
i also tried to flash using fastboot but giving error at the system partition sowing system write failure.. can some one identify provide me with the solution .. thanks
Click to expand...
Click to collapse
I'm also facing same problem.......shows 0MB in Internal storage(twrp).......and stuck with YU logo doesnt go further....
I am also facing the exact same problem. Did you find any solution ??
BOTDeveloper said:
I am also facing the exact same problem. Did you find any solution ??
Click to expand...
Click to collapse
same here. any solution?? please help guys !
Facing same problem. Did anyone solve the issue?
cm-13.0-20161219-NIGHTLY-lettuce.zip apply this update from sd card it works
Guys ,..... anybody plz any solutions..... developers!!
facing exact same problem
guys facing exact same problem. searched everywhere but couldn't find any solution. im very much frustrated right now. tried everything . nothing works
facing same problem
any update on howm top solvew thisa guys?
Solution for 0 MB storage in TWRP
Hi Brothers!
It's my first time posting here , so if i make a mistake i am sorry in advance for that.
Solution for 0 MB storage in TWRP is very easy.
You need to boot your phone into TWRP.
In 2nd step you need to go to WIPE option .
Select Data and click on FS Options e.g. trying to change its partition format, most phones use Ext4.
Do same with the Data.
And TADA!!!!
Your problem is solved
I hope it helps you guys getting answer after a long time because i saw it late. Sorry for that.
same problem
BOTDeveloper said:
I am also facing the exact same problem. Did you find any solution ??
Click to expand...
Click to collapse
Try to wipe everything
Format data using twrp
It should be solved.
Hi my YU Yuphoria 5010 started acting up since last week ,when i noticed that the phone was restarting randomly and the settings was missing and even if i clicked on the settings logo in the notification panel, nothing would happen .So i decided to flash a Cusstom ROM instead and boot into recovery.While trying to wipe cache,dalvik and data I got an error message "uable to mount data,cache ,system(invalid argument) and internal memory* was showing up as 0.So i thought my phone was bricked and tried reviving it with the sd card method.But everything else except for system flashed , and got an error FAILED (remote: flash write failure ) just for system .Anyway now I could boot into recovery using fastboot boot command and the internal memory started showing up correcty. The fastboot command is the only way i could get into recovery, if i try power+volume down it would just come up with the empty battery logo. After this i installed qualcomm drivers and manually changed the driver to Qualcomm HS-USB QD Loader 9008 and tried flashing through QFil with a flashable stock ROM and ended up with the error message:"Download Fail:System.Exception: Unable to download Flash Programmer using Sahara Protocol** at QC.QMSLPhone.Phone.QPHONEMS_SaharaArmPrgDownload(String sFileName)** at QC.SwDownloadDLL.SwDownload.QPHONEMSSaharaDownloadArmPrg(UInt64& version, String armPrgPath)
Download Fail:Sahara FailSahara Fail".
But after going through some of the posts I found that my phone might not be bricked in the first place.My device just shows up as 'Android' under Other devices in Device Manager.
The following are the details from device manager.
Device type: Other devices
Manufacturer: Unknown
Location Port_#002.Hub_#003
Problem code : 0000001C
Physical Device Object name: \Device\USBPDO-6
Hardware IDS: USB\VID_2A96&PID_300A&REV_0100
USB\VID_2A96&PID_300A
{259abffc-50a7-47ce-af08-68c9a7d73366}[13]: 6.0
{6a3433f4-5626-40e8-a9b9-dbd9ecd2884b}[4]: <true>
{6a3433f4-5626-40e8-a9b9-dbd9ecd2884b}[6]: <true>
I also tried to restore through TWRP recovery using the back up my brother created on his YU 5010A to no success.Changing the file system type and back to ext4 also didnt help. I use a Windows 10 64bit Laptop.
What could I possibly do to revive my phone?Kindly help.
Sent from my HUAWEI Y560-L01 using XDA Free mobile app
Not working for me
rahman.khan001 said:
Hi Brothers!
It's my first time posting here , so if i make a mistake i am sorry in advance for that.
Solution for 0 MB storage in TWRP is very easy.
You need to boot your phone into TWRP.
In 2nd step you need to go to WIPE option .
Select Data and click on FS Options e.g. trying to change its partition format, most phones use Ext4.
Do same with the Data.
And TADA!!!!
Your problem is solved
I hope it helps you guys getting answer after a long time because i saw it late. Sorry for that.
Click to expand...
Click to collapse
Not getting any help as the same failed to mount issue is continuing.
puriadeb said:
Not getting any help as the same failed to mount issue is continuing.
Click to expand...
Click to collapse
Wipe everything include system,internal storage and data.
Reboot TWRP to recovery again
Now check your internal storage will be mounted
After it connect phone with pc in mtp mode ( TWRP)
Copy any custom ROM
Then install it through recovery
Enjoy
nischait said:
Wipe everything include system,internal storage and data.
Reboot TWRP to recovery again
Now check your internal storage will be mounted
After it connect phone with pc in mtp mode ( TWRP)
Copy any custom ROM
Then install it through recovery
Enjoy
Click to expand...
Click to collapse
Hi,
I have tried this several times without any help.
Cache format issue .Solved using advanced wipe in TWRP
harshgoswami said:
can any one help me
what i did was, formatting the system ,data partion using wipe option in recovery (twrp), by mistake the battery got removed during the process since then the problem occured..
my yuphoria device stuck on the boot logo
is not able to mount /system /data /cache and internal storage
it is booting in fastboot mode as well as in recovery but i m not able to flash any rom, in recovery its giving the error as unable to mount /system /data /cache, showing 0mb space in internal storage and system
i also tried to flash using fastboot but giving error at the system partition sowing system write failure.. can some one identify provide me with the solution .. thanks
Click to expand...
Click to collapse
open TWRP recovery.Go to wipe section and select advanced wipe option here .Now select data and cache from check boxes.then click on change partition format.Select ext4fs .Wipe it then wait for sometime because sometimes it takes approximately 15-20 mins so be patient .It will successfully wipe and then you can see that everything is up to the mark !
puriadeb said:
Hi,
I have tried this several times without any help.
Click to expand...
Click to collapse
flash stock cyanogen rom again. Then install TWRP. Cross check at your end. We actually don't know which process you are following!
I have a YU5510A running Quarkos and YU5010A running AOSP Extended. I also flash a lot of custom Roms but never get any issue.
did you find any solution for this i can only access cyanogen recovery and fastboot mode .
harshgoswami said:
can any one help me
what i did was, formatting the system ,data partion using wipe option in recovery (twrp), by mistake the battery got removed during the process since then the problem occured..
my yuphoria device stuck on the boot logo
is not able to mount /system /data /cache and internal storage
it is booting in fastboot mode as well as in recovery but i m not able to flash any rom, in recovery its giving the error as unable to mount /system /data /cache, showing 0mb space in internal storage and system
i also tried to flash using fastboot but giving error at the system partition sowing system write failure.. can some one identify provide me with the solution .. thanks
Click to expand...
Click to collapse
duskyrahul said:
did you find any solution for this i can only access cyanogen recovery and fastboot mode .
Click to expand...
Click to collapse
Flash stock ROM using fastboot
For yu5010a you got fastboot package
Open flash all.bat
Just remove device code
02x1ebf or anything I don't remember what it was.
Remove it from all lines
Save flash all.bat
Run it
---------- Post added at 01:29 PM ---------- Previous post was at 01:26 PM ----------
duskyrahul said:
did you find any solution for this i can only access cyanogen recovery and fastboot mode .
Click to expand...
Click to collapse
Flash stock ROM using fastboot
For yu5010a you got fastboot package
Open flash all.bat
Just remove device code
02x1ebf or anything I don't remember what it was.
Remove it from all lines
Save flash all.bat
Run it
For 5510a
Download ygdp 5.0
Select developer option
Select CBP file
Wait for tool extract it
Now minimize tool
Go to folder
Ygdp 5.0
You find here downfiles folder
Copy it and paste in c:\
Run flash all.bat
Done
---------- Post added at 01:35 PM ---------- Previous post was at 01:29 PM ----------
If any one got error in mounting using twrp
Just follow steps
Goto wipe -> advance wipe-> format data->
Type yes
Wait for process completion
Now reboot twrp to recovery
You see everything is mounted successfully.
Note :- with this step you format everything from your phone so don't reboot to system
Now connect phone with pc and copy any downloaded custom ROM in external SD
Flash it
Enjoy

Categories

Resources