Samsung Galaxy S6 failed to mount EFS ! Please help ! - Galaxy S6 Q&A, Help & Troubleshooting

Hi,
My device is kind of bricked, since it doesn't boot up due to EFS mounting problems.
I tried to restore through adb but there is no /dev/block/mmcblk0p3 location.
Any ideas how I should restore the EFS folder (i have an efs.img saved in my pc) ?
Thanks !

merandrei0508 said:
Hi,
My device is kind of bricked, since it doesn't boot up due to EFS mounting problems.
I tried to restore through adb but there is no /dev/block/mmcblk0p3 location.
Any ideas how I should restore the EFS folder (i have an efs.img saved in my pc) ?
Thanks !
Click to expand...
Click to collapse
There is no mmcblk0p3 for galaxy s6.
Efs mount can be found in the block > /dev/block/sda3

batuzai04123 said:
There is no mmcblk0p3 for galaxy s6.
Efs mount can be found in the block > /dev/block/sda3
Click to expand...
Click to collapse
Thanks!
I succesfully mounted the sda3 block, but still not passing the logo.
Any idea how may I unbrick this guy ?

Hmm try my method
http://forum.xda-developers.com/showpost.php?p=63693480&postcount=28
Dont forget to mount /system partition in custom recovery before doing adb commands

batuzai04123 said:
Hmm try my method
http://forum.xda-developers.com/showpost.php?p=63693480&postcount=28
Dont forget to mount /system partition in custom recovery before doing adb commands
Click to expand...
Click to collapse
Thanks a lot!
I managed to make it boot, now is usable but still, if I type *#06# it shows me a generic IMEI 3500...06/02 and my SN disappeared, and when I flashed a stock rom have the same problem (stuck at logo).
I've been flashing UniKernel again with odin and all was good.
Is there any chance that I can run stock rom and kernel, and make this go away?
Thank you again !

Hmm ur imei i guess is broken. Did you tried to backup first and restore the efs?
Im not sure but im unable to get my phone to stock . Only custom recovery works for me.

Related

[Q] Enrcyption Support for ClockWorkMod Recovery

Hello,
i have just installed the official stock ICS 4.0.3 Rom to my Nexus S and everything was really fine... until i tried to root it. As someone who tries to take security seriously, i immediately encrypted the device using the tools provided by ics (works ok).
but unfortunatly it's now not possible anymore to mount /sdcard while in recovery, which makes rooting and installing updates impossible (or is there any other way? eg. fastboot?).
therefore my question: will clockworkmod recovery support ics encrypted devices in the (near) future? i know its gonna be a p.i.a. to type a password with only the volume buttons, but hey
i like the encryption and would like to keep it, but not beeing able to use recovery like before is a big drawback...
greetings
Georg
Same for me.
Hope to see encryption support in clockworkmod soon.
I bought Rom manager premium even if I never flash from rm just to support the developers... hope they will be able to get it sorted out
Op -- I'm interested in this for when my phone (EVO 3D) finally gets ICS. Will you post an update to this thread if you hear anything?
BTW, with TWRP getting touchscreen support, it can't be too much longer before CWM gets touchscreen since I think the guys in TWRP were going to start contributing to CWM, from what I've heard anyway. So that would solve the password typing problem.
Georg, thanks for asking this question as I've been wondering the same exact thing. Hopefully we'll get a good answer soon.
Alternatives for ClockworkMod Recovery
I encrypted my device (the Exchange account I added required it) n... now I cant do anything in recovery ... it wont mount the drive ... any suggestions for a replacement ...
thanks ...
mrosensweig said:
I encrypted my device (the Exchange account I added required it) n... now I cant do anything in recovery ... it wont mount the drive ... any suggestions for a replacement ...
thanks ...
Click to expand...
Click to collapse
Its because the way encryption works you have to boot and enter code, that's the whole point, no recovery can do it atm
Sent from my ice cream powered Nexus S
small update:
nothing new on the subject, but i didnt check out the new touch recovery (anyone tried it yet?).
in the mean time i went back to an unencrypted CM9...
I didn't read anything about encryption so did not upgraded to the touch recovery yet
you should lock the bootloader if someone is nagging you
jomir said:
small update:
nothing new on the subject, but i didnt check out the new touch recovery (anyone tried it yet?).
in the mean time i went back to an unencrypted CM9...
Click to expand...
Click to collapse
Jomir, what was the procedure you used to get back to CM9? Is it possible to repartition, erasing the encrypted partitions so a new rom can be flashed? How?
Thx,
rmsilva
rmsilva123 said:
Jomir, what was the procedure you used to get back to CM9? Is it possible to repartition, erasing the encrypted partitions so a new rom can be flashed? How?
Thx,
rmsilva
Click to expand...
Click to collapse
Restore a backup or do a clean install(format boot, system, cache and data)
Sent from my ice cream powered Nexus S
DarkhShadow said:
Restore a backup or do a clean install(format boot, system, cache and data)
Sent from my ice cream powered Nexus S
Click to expand...
Click to collapse
Thanks for the reply, DarkhShadow. The problem is that CWM can't wipe or format these partitions, since it can't mount /sdcard (which is encrypted). If I could only access the external sdcard from within CWM, I could just wipe everything and then install a new rom. But since it can't mount /sdcard, I can't access sd-ext. nvflash is not an option, since my TF101 is B90. Is there a way to either restore the stock recovery (overwrite CWM) or boot from the external SD so I can run a script such as "super wipe full" (http://forum.xda-developers.com/showthread.php?t=1245892)? Maybe there's a way to run the wipe script through adb? If I can just format the partitions (which is what the script does), then CWM would be able to mount /sdcard and, consequently, the external SD and I can flash a new rom (such as revolution HD 3.0.1).
Thanks,
rmsilva
Honestly idk then, try a factory reset on phone(ie booted up) and then maybe it will be unencrypted?
Sent from my ice cream powered Nexus S
The funny thing is that stock recovery on an encrypted phone can write to the disk, but only from a warm reboot (perhaps the kernel stays resident?).
When I say write to disk I say apply the leaked OTA update, 4.0.4 for the VZ Gnex. And correct me if I am wrong, it's writing and mounting the disk, no?
Anyhow, this is done from stock recovery which is open source. So you ask yourself, why can't Koush support mounting the disk from a warm recovery state reboot? Maybe he doesn't know this?
DarkhShadow said:
Its because the way encryption works you have to boot and enter code, that's the whole point, no recovery can do it atm
Sent from my ice cream powered Nexus S
Click to expand...
Click to collapse
rmsilva123 said:
Jomir, what was the procedure you used to get back to CM9? Is it possible to repartition, erasing the encrypted partitions so a new rom can be flashed? How?
Thx,
rmsilva
Click to expand...
Click to collapse
i did a factory reset (from the settings menu), installed recovery per adb/fastboot and installed cm9 from sdcard in recovery.
Use tmpfs to install a new ROM in crypted system
Hello Everyone
To flash a new ROM you can do as follows:
boot in Recovery
format cache partition
from your PC use adb to mount /sdcard as tmpfs:
adb shell mount -t tmpfs none /sdcard​
put your ROM on the (fake) sdcard
adb push <your rom> /sdcard​
use the recovery to flesh the ROM as usual
This worked form me.
Sorry to be late...
What about a nandroid backup or restore? How big is /cache?
orcruin said:
Hello Everyone
To flash a new ROM you can do as follows:
boot in Recovery
format cache partition
from your PC use adb to mount /sdcard as tmpfs:
adb shell mount -t tmpfs none /sdcard​
put your ROM on the (fake) sdcard
adb push <your rom> /sdcard​
use the recovery to flesh the ROM as usual
This worked form me.
Sorry to be late...
Click to expand...
Click to collapse
Sorry I didn't try with a nandroid backup but I think it is too big to fit the device memory...
You can backup data inside the sd partiton (phone up and running, just to don't lose data...), boot into recovery, format sdcard partition, mount it, put the backup in the sdcard and after install the nandroid backup...
I think that it could work but I am not sure. If after formatting the sdcard you can mount it, the task is done. You can put the backup on it using adb push and flash using recovery.
If you try please give me some news.
Regards
orcruin said:
Hello Everyone
To flash a new ROM you can do as follows:
boot in Recovery
format cache partition
from your PC use adb to mount /sdcard as tmpfs:
adb shell mount -t tmpfs none /sdcard​
put your ROM on the (fake) sdcard
adb push <your rom> /sdcard​
use the recovery to flesh the ROM as usual
This worked form me.
Sorry to be late...
Click to expand...
Click to collapse
I'm kind of a noob when it comes to adb. What is that process doing exactly? How big is the fake sdcard? I want to make sure I understand all the implications before I dive in. Of course I need HTC to release a ICS ROM first. ;-)
thx1200 said:
I'm kind of a noob when it comes to adb. What is that process doing exactly? How big is the fake sdcard? I want to make sure I understand all the implications before I dive in. Of course I need HTC to release a ICS ROM first. ;-)
Click to expand...
Click to collapse
First it formats the cache partition. Then mount the /sdcard so that you can access it from your pc. After you mount the /sdcard, you can put your rom zip into it. After the zip has been transferred into /sdcard, you can flash the zip as usual.
Since nexus s doesn't have sdcard slot, it mounts the internal storage as '/sdcard' to treat it like a sdcard, thus 'fake' sdcard. The 'fake' sdcard is around 13GB.

[Q] [BRICK'd?] Can't mount /data /cache /system

One day, about 2-3 weeks ago, on my way to home, I decided to install an other ROM (5.1.1 ivanchi -> CM9). Went straight into recovery (TWRP 2.8.5 or 6) and formatted everything except microsd, everything seemed to go as planned. Then proceeded to install the ROM; it gets stuck, can't get pass the booting screen even after 20-30 minutes. Force-Reboot into recovery and receive "unable to mount /data | /system | /cache error". Tried changing fs-type of /data /cache /system to any other type, no success.
Got back home, tried installing RUU. Got stuck at 39%. every. single. time. !! Tried an older RUU, same response.
Then tried even oem lock + flash recovery_signed.img + boot boot.img with fastboot and then RUU install. Then again with unlocked bootloader. Still no! But, I didn't tried lock + recovery signed + boot + S-On, because I am afraid not to be able to regain S-Off at this state.
Even tried a parted format, implying that one guy managed to make it work in the end. See topic here : link.
Tried doing guy's steps but after parted /dev/block/mmcblk0 I receive Error: Can't have overlapping partitions. Tried then parted /dev/block/mmcblk0p23 (userdata), it works, and if I try mkfs/rm on partition 1, it says it's in use (p23p1 ...).
Output:
~ # parted /dev/block/mmcblk0p23
parted /dev/block/mmcblk0p23
GNU Parted 1.8.8.1.179-aef3
Using /dev/block/mmcblk0p23
Welcome to GNU Parted! Type 'help' to view a list of commands.
(parted) print
print
print
Model: Unknown (unknown)
Disk /dev/block/mmcblk0p23: 1253MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Number Start End Size File system Flags
1 0.00B 1253MB 1253MB ext4
(parted) rm
rm
rm
Partition number? 1
1
1
Error: Partition /dev/block/mmcblk0p23p1 is being used. You must unmount it
before you modify it with Parted.
(parted) mkfs
mkfs
mkfs
Warning: The existing file system will be destroyed and all data on the
partition will be lost. Do you want to continue?
Yes/No? yes
yes
yes
Partition number? 1
1
1
Error: Partition /dev/block/mmcblk0p23p1 is being used. You must unmount it
before you modify it with Parted.
I can format my /data /system /cache one at the time, after doing reboot recovery and that's only in CWM 6.0.1.2. But this CWM isn't able to install ROMs somehow, wether it gets stuck of just plain fails. So, if I want to install a ROM, after the format, I have to install 4Ext (latest) recovery and do it there. Install everything from recovery, boot, sign in for GApps etc etc and while trying to install apps from Google Play, after about 4 to 6 apps, it gives a black screen, leaving no option but remove battery and reboot. Do that and get stuck on bootsplash / bootscreen. Everytime!
If then I try formatting paritions using 4Ext most of the time it fails, making them unmountable again after all.
Tried everything mentioned running PG58IMG with firmware 3.33, Hboot 1.27.1100, worldwide english (.104.). Tried fashing rom.zip as the PG58IMG.zip from fastboot in rebootRUU (gets stuck at [RUU]WP,dzdata,0) and now even from sdCard (gets stuck at [6] USERDATA).
I dug furthermore into bricked Sensation, seeing a QHSUSB brickbug (thread). It is refeered to be a bootloader brickbug; problem which I am not facing right now. Eventho, followed OP's instruction my freshly installed Ubuntu 14.04 can't detect my HTC. Also did some of the YouTube instructions, connecting sdcard's plate with lower pin from the back (trolled?!) (video), yet nothing.
Out of disperation, asked hinxnz and rzr86, and both of you adviced me to try thread 1 or 2 (relying on sdCard as primary/sec partitions). Good advices but I don't consider this be the best solution for this problem; STILL HAVE HOPE MAKING INTERNAL SD TO WORK! :d
ASK ME ANYTHING REGARDING MY PROBLEM! Will post every bit of information you consider relevant.
PLEASE HELP!
u tried ruu, didnt work, tried firmware, didnt work. @rzr86 and @hinxnz gave u those guides coz its the only known way to fix/bypass that problem on xda. maybe there is another way but no one has found it yet. u could take ur phone to a repair shop, pay bout a hundred bucks, connect it to jtag and hope for the best, but that might not even flash partitions back.
personally i dont see how twrp is still allowed to be downloaded on xda in the sensation thread coz it keeps killing peoples phones. that jus my opinion tho.
Atm my phone is literally bricked, QHSUSB brick because of my stupidity... Maybe I will make it to work again; anyways...
For the partition problem, don't the HTC has some kind of .pit files like Samsung does? They should! Also, what if someone with a 'healthy' Pyramid does a dd of the /dev/block/mmcblk* for those with fk'd partitions to use ?
Hi, one more here with wrecked partitions by TWRP factory reset....
Trying to Ruu the Sensation, but RUU has been getting stuck in the process ... I'll edit if I success.
Thanks for all the info out htere!
Edit: no success, even tried at last to fix partitions (parted and fdisk) via ADB, device is now dead. So sad HTC or any ever gave the details for the partition table, a simple script might have solved this.
I'm just catching up on this one.
If I read this right,the information on the partitions was trashed by TWRP recovery?
There was a member that stated the HTC Desire used to be able to have it's partitions reconfigured,IIRC.
Perhaps this is the first step to achieving that with the Sensation?
Sent from my SM-N915W8 using XDA-Developers mobile app
I'm too woried nowadays....i got the error can't mount system,data,cache inmy xolo a600...i can't flash custom rom or can't do factory data reset...but when i try to factory reset using my stock firmware recovery it's done...but in twrp & cwm recoverys say can't mount system,data,cache...i also can't connect my device to pc using usb mode,mtp...my pc said unknown device detected...what to do?...i just really tired & tensed please please please guys give me the solution...please...!!

How Can I Get Out of This Bootloop on My Moto G

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 sideload​adb sideload rom.zip​
lost101 said:
Try sideloading the ROM.
TWRP > ADB sideload​adb 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 shell​e2fsck /dev/block/platform/msm_sdcc.1/by-name/userdata​
lost101 said:
On PC:
adb shell​e2fsck /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.

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

[Corrupt EMMC] [Unable to Mount] Bootlop on YU logo, Unable to Mount anything in TWRP

Background: I have a YU Yuphoria running latest cm13 snapshot (16 Sep, 2016), with latest Xposed framework and TWRP 3.0.2
* I woke up today to find a blank screen, battery reset gives "Encryption Unsuccessful" error message
* Booted to TWRP, unable to mount /data, /cache or /system (All 0 mb in Advanced wipe)
* Couldn't restore Nandroid backup, unable to mount /system
* Booted to fastboot, tried to do factory flash using flash_all.bat, everything succeeds except for system : "remote: flash write failure"
* Reformatted data, cache and system from adb shell, still no dice
What would you suggest i do now?
Is there a way to write those partitions to a microSD card, and make the phone think of it as internal storage?
Looking at this forum (and official YU forums), it seems like this is becoming a rather common problem [1 2 3 4 5 6 7]. How is it possible that so many users come to face this exact problem at the same time (In spite of being on different ROMs)?
reserved
A_K_S_H_ said:
Background: I have a YU Yuphoria running latest cm13 snapshot (16 Sep, 2016), with latest Xposed framework and TWRP 3.0.2
* I woke up today to find a blank screen, battery reset gives "Encryption Unsuccessful" error message
* Booted to TWRP, unable to mount /data, /cache or /system (All 0 mb in Advanced wipe)
* Couldn't restore Nandroid backup, unable to mount /system
* Booted to fastboot, tried to do factory flash using flash_all.bat, everything succeeds except for system : "remote: flash write failure"
* Reformatted data, cache and system from adb shell, still no dice
What would you suggest i do now?
Is there a way to write those partitions to a microSD card, and make the phone think of it as internal storage?
Looking at this forum (and official YU forums), it seems like this is becoming a rather common problem [1 2 3 4 5 6 7]. How is it possible that so many users come to face this exact problem at the same time (In spite of being on different ROMs)?
Click to expand...
Click to collapse
i'm also facing same problem. any solution u found?
Manish Adak said:
i'm also facing same problem. any solution u found?
Click to expand...
Click to collapse
Nope, ended up buying a new phone (Redmi Note 4)
A_K_S_H_ said:
Background: I have a YU Yuphoria running latest cm13 snapshot (16 Sep, 2016), with latest Xposed framework and TWRP 3.0.2
* I woke up today to find a blank screen, battery reset gives "Encryption Unsuccessful" error message
* Booted to TWRP, unable to mount /data, /cache or /system (All 0 mb in Advanced wipe)
* Couldn't restore Nandroid backup, unable to mount /system
* Booted to fastboot, tried to do factory flash using flash_all.bat, everything succeeds except for system : "remote: flash write failure"
* Reformatted data, cache and system from adb shell, still no dice
What would you suggest i do now?
Is there a way to write those partitions to a microSD card, and make the phone think of it as internal storage?
Looking at this forum (and official YU forums), it seems like this is becoming a rather common problem [1 2 3 4 5 6 7]. How is it possible that so many users come to face this exact problem at the same time (In spite of being on different ROMs)?
Click to expand...
Click to collapse
same problem....... i flash stock yu5010a firmware from fastboot.. now:good: but when i flash some files in twrp,strucked on boot animation....so im searching for only fastboot roms..........
A_K_S_H_ said:
Nope, ended up buying a new phone (Redmi Note 4)
Click to expand...
Click to collapse
which varient?
Vimalvt said:
same problem....... i flash stock yu5010a firmware from fastboot.. now:good: but when i flash some files in twrp,strucked on boot animation....so im searching for only fastboot roms..........
Click to expand...
Click to collapse
You mean flashing yu5010a firmware solves the problem for yu5010 [Cyanogen version] ? If so, could you post a link to the firmware version you used?
Manish Adak said:
which varient?
Click to expand...
Click to collapse
13k version (4gb, 64gb)
Vimalvt said:
same problem....... i flash stock yu5010a firmware from fastboot.. now:good: but when i flash some files in twrp,strucked on boot animation....so im searching for only fastboot roms..........
Click to expand...
Click to collapse
Change ur twrp to 3..0.2.0. That should solve the problm
13k version (4gb, 64gb)[/QUOTE]
tell me ur personal user exprience about note 4.....spcly camera...
Manish Adak said:
i'm also facing same problem. any solution u found?
Click to expand...
Click to collapse
Same problem here too! No solution yet.
Internal memory 0 mb
unable to mount system (invalid argument)
unable to mount data (invalid argument)
unable to mount cache (invalid argument)
samujjwalk said:
Same problem here too! No solution yet.
Internal memory 0 mb
unable to mount system (invalid argument)
unable to mount data (invalid argument)
unable to mount cache (invalid argument)
Click to expand...
Click to collapse
The same
Try changing partitions to f2fs or any other partition and change back to default partition...
AmalRam said:
Try changing partitions to f2fs or any other partition and change back to default partition...
Click to expand...
Click to collapse
In TWRP?
If yes, I tried that already.
Tried to convert to all available options and reverted back: FAT, EXT2, EXT3,EXT4, F2FS, VFAT
Nothing works actually.
The internal memory still shows 0 MB
I used a tool also called YUware. There is an option to format all partitions. It formats all but the system partition is failed to get formatted as well.
Twrp version?
try to erase persist.img and flash the persist.img
arun531 said:
try to erase persist.img and flash the persist.img
Click to expand...
Click to collapse
Doesn't work. Gives the same error message : "FAILED (remote: flash write failure)"
how did u flash...? can you lock bootloader ...?
arun531 said:
how did u flash...?
Click to expand...
Click to collapse
Using
fastboot -i 0x2a96 flash persist persist.img
(Source : https://forum.xda-developers.com/yu-yuphoria/general/guide-bricklooping-lettuce-yu-yuphoria-t3181864 )
arun531 said:
can you lock bootloader ...?
Click to expand...
Click to collapse
Yes.
try to flash cm12 fastboot pkg.... or try the qfil flashing...
i also faced this type problem but when i erase and reflash the system and persist... it fixed.
arun531 said:
try to flash cm12 fastboot pkg....
Click to expand...
Click to collapse
That is what i did, as i mentioned in OP :
A_K_S_H_ said:
* Booted to fastboot, tried to do factory flash using flash_all.bat, everything succeeds except for system : "remote: flash write failure"
Click to expand...
Click to collapse
arun531 said:
or try the qfil flashing...
i also faced this type problem but when i erase and reflash the system and persist... it fixed.
Click to expand...
Click to collapse
Isn't qfil flashing meant for Hard Bricked devices? (My device doesn't show up as QHUSB_BULK when connected to PC)

Categories

Resources