Related
Hi.
I'm trying to fix my boss' tab, SPH-P100 (Sprint).
I have tried all kinds of things and nearly bricked it (got the phone ! computer symbol, but it still accepted uploads, so I was OK).
Here's the issues:
- Continuous loop of Samsung logo on boot
- From Recovery screen, I performed a factory reset, but it didn't help - same logo loop
- In the Recovery screen, I get errors similar to the ones quoted above:
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
I read all kinds of posts about simply flashing the stock ROM, and I found the ROM that was mentioned multiple times in these forums to be the right one for this tab (it did change the first boot animation, though...). The ROM I used is tab_sprint_noModem_20101226.tar inside Tab_Stock_-_No_Modem.rar.
I tried:
-ODIN with the stock ROM posted in this thread. It works, but it doesn't fix anything. I tried with and without the PIT file (one thread specifically warned NOT to use the PIT file, but in the end I tried it anyway - I think I did NOT hit Repartition, so it probably didn't do anything...).
-Heimdall doesn't seem to work at all for me. I found version 1.3.1, and the instructions in post 21 of the thread linked above don't seem to apply to this version. I finally figured out that I need to be in the FLASH tab, but I can't add files without the PIT file, it won't let me add the zImage file for recovery (or at least complains that there's no .bin file ending), and when I checked "Repartition", I got the error:
ERROR: Partition corresponding to -21 argument could not be located
Ending session...
Yes, I installed the drivers that came with Heimdall.
-Following other posts with very similar errors, I formatted the SD card in Windows using FAT32 - no change.
-I looked into another thread talking about parted, but I don't have root on that device, and I'm not sure what my boss would think about me rooting his pad... I also don't know enough to figure out which rooted ROMs would go with it - I'm scared enough with the "official stock rom" I'm using
I'm fairly tech savvy, know a little about Linux and have used adb to root my own phone, but otherwise a lot of the things I read here only make enough sense to me to follow the instructions and not get lost.
Maybe there's a different version of Heimdall that I should be using, or maybe I did something else wrong, but I'm sure I followed the instructions here.
Any help would be greatly appreciated!
Thanks in advance!
(PS, I originally posted this at the end of the thread I mentioned here but did not get an answer - I'm sorry, I had not read the post about not asking questions in that forum, even if it was attached to another post where similar questions were asked and answered, so I'm moving this post here instead.)
Update:
Found a different Rom in this thread - same situation:
I can flash it, but nothing changes, and I still get the error message I showed. The main change is that this ROM is the first I have found that has the same Sprint boot animation that the tab originally had.
The new information is that once it resets after flashing, it briefly shows a few messages - one said that if failed to wipe the cache, and I think the others showed the same error about /dev/block/mmcblk0p1 but I can't be sure (tried to get video of it, but I was too slow, and it's blurred - I'll try again later to get the exact error messages).
Update 2:
Found yet another ROM in this thread and tried it, and this one doesn't seem to work at all with this tab (tried with and without pit/re-partitioning) - the boot fails and immediately boots into Recovery by itself and shows the following:
-- bootmode=7 from cmdline
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/command
-- Wiping data...
Formatting /data...
E:format_volume: rfs format failed on /dev/block/mmcblk0p2
Formatting /dbdata...
Formatting/cache...
E:format_volume: rfs format failed on /dev/block/mmcblk0p1
Data wipe failed.
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/recovery_kernel_log
E:copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (No such file or directory)
Click to expand...
Click to collapse
Will try to flash the other ROM again to try and get a precise look at its error message...
UPDATE 3:
Flashed the first ROM again - no error message, just the same Samsung logo cycle that freezes briefly and then starts over.
Flashed the second ROM again (the one that has the correct Spring animation), and this time I got the error messages on video.
-- Wiping DATA:...
Formatting DATA:...
DATA: wipe failed.
-- Wiping CACHE:...
Formatting CACHE:...
CACHE: wipe failed.
--Wiping DBDATA:...
Formatting DBDATA:...
E:Can't mount /dev/block/mmcblk0p2
(No such file or directory)
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
Rebooting...
Click to expand...
Click to collapse
Still hoping for ideas, but I think I'm at the end of what I can try...
Is it likely or possible that the internal memory got damaged?
I don't know exactly what my boss did to the tab, but he mentioned something about "the cold" meaning Minnesota winter cold - we had about 12 degrees last week, so maybe that's the cause...
Have you found and tried the EA24 stock flash tool?
Sent from my SPH-P100 using xda premium and ICS
Thanks for the reply!
If that's this file:
Sprint Galaxy Tab EA24 Flasher.zip
Then I have tried the ROM in it with Odin, but not the actual tool that came with it.
I'll see if I can get my boss to give me another shot with it (unless he's already returned it - I've had it for a few days already...).
Thanks!
has anyone found a solution to this? I am having the exact same issue...
Not sure why or how it happened everything was fine one day and next day wont go past logo and keeps rebooting.
Same problem here
My P100 started this problem last night, which was the first time it's been turned in in several days. It's fully stock, never had any rooting or flashing performed on it.
Booting into recovery mode shows failed mounts on everything it tries to do, and all the options for recovery also fail - except for "reboot system now", which does reboot it, but then it just sits on the pulsing Samsung logo endlessly. And I do mean endlessly, I let it go four hours last night, after which the battery ran out. Plugged it in after that, and it's right back to the same thing.
Every other thread I've found with this problem listed it as an after-effect of having attempted to flash a new ROM, but that is not the case with mine...
Hoping someone has the answer...
Thanks!
-mike
Same exact symptoms, and when I tried CM9 or other ICS ROMs this errors lead into the dreaded "Encryption Unsuccessful" bug.
At this point I'm just trying to get the device to boot consistently.
ChrisCTX said:
Same exact symptoms, and when I tried CM9 or other ICS ROMs this errors lead into the dreaded "Encryption Unsuccessful" bug.
At this point I'm just trying to get the device to boot consistently.
Click to expand...
Click to collapse
Did you try to do full restock (include bootloader and repartition)?
or you can try CM9 again with a fixed kernel by cdesai or jt. look at this conversation:
http://forum.xda-developers.com/showpost.php?p=28584567&postcount=2320
yappoe said:
Did you try to do full restock (include bootloader and repartition)?
or you can try CM9 again with a fixed kernel by cdesai or jt. look at this conversation:
http://forum.xda-developers.com/showpost.php?p=28584567&postcount=2320
Click to expand...
Click to collapse
I'm on it ASAP, thanks a ton for that
Edit: If possible mind giving a link to that specific kernel (or flashable .zip with it)?
Do you have this on your screen:
http://forum.xda-developers.com/attachment.php?attachmentid=1193979&d=1342124106
If so, we're in the same boat
Btw, I used a full repartition and boot following this thread:
http://forum.xda-developers.com/showpost.php?p=17817287&postcount=2
and same error occurs.
Bump in hopes of solving this issue.
My tab is basically bricked. I have this same issue after putting CM9 on it. Those errors consistently pop up. and thats it.
I guess its a paper weight now.
you may try flashing pit file and stock rom with micro SD inserted during flashing. that's what I did to my Samsung GT-I9003 when it failed to read the internal SD. At first, the camera may not work. Just root the device after flashing pit/ROM and do SD Swap Mod (external SD as internal SD).
Not sure if it's gonna work with Galaxy Tab. Give it a try. Hope this helps.
Hey guys, it appears JimRich is working on a solution for the CDMA (verizon and sprint) versions of thsi device, keep checking and be sure to let him know there are other people with this problem. http://forum.xda-developers.com/showthread.php?t=1789728
Long story short,
Purchased a Tmobile HTC One, Planned on taking it over to Straight Talk.
I have not asked any questions because I can usually figure this out.
Facts:
Unlocked using All In One
TWRP recovery
Issue:
Keep rebooting once it gets to the HTC One screen with Beats Audio
I am about 22 hours into this and very frustrated, it seems as though I do not have an O.S.
Cannot mount E:
rafalk86 said:
Long story short,
Purchased a Tmobile HTC One, Planned on taking it over to Straight Talk.
I have not asked any questions because I can usually figure this out.
Facts:
Unlocked using All In One
TWRP recovery
Issue:
Keep rebooting once it gets to the HTC One screen with Beats Audio
I am about 22 hours into this and very frustrated, it seems as though I do not have an O.S.
Cannot mount E:
Click to expand...
Click to collapse
Use the ADB Sideload option(follow the directions carefully) in the All-in-One Toolkit to load a ROM.
unremarked said:
Use the ADB Sideload option(follow the directions carefully) in the All-in-One Toolkit to load a ROM.
Click to expand...
Click to collapse
I have tried a couple of times (following directions closely - have done this before on a inspire) and keep getting
"E:unable to mount '/data'" on the phone side & "error: closed"
rafalk86 said:
I have tried a couple of times (following directions closely - have done this before on a inspire) and keep getting
"E:unable to mount '/data'" on the phone side & "error: closed"
Click to expand...
Click to collapse
Hmm. Have you attempted to format data while in TWRP recovery? Also a few more details please--once you had unlocked the bootloader and installed TWRP, did you attempt to install a ROM from that point or boot into stock? If it's the latter, have you attempted to fastboot flash a boot.img from a stock ROM/NAND backup?
rafalk86 said:
I have tried a couple of times (following directions closely - have done this before on a inspire) and keep getting
"E:unable to mount '/data'" on the phone side & "error: closed"
Click to expand...
Click to collapse
I have always had better luck with CWM clockworkmod recovery than TWRP for these kind of situations. So you might want to use the all in one and put Clockwork on. Also when sideloading a rom make sure to rename the rom something nice and short like rom.zip no spaces no numbers just simple and short or it will fail.
unremarked said:
Hmm. Have you attempted to format data while in TWRP recovery? Also a few more details please--once you had unlocked the bootloader and installed TWRP, did you attempt to install a ROM from that point or boot into stock? If it's the latter, have you attempted to fastboot flash a boot.img from a stock ROM/NAND backup?
Click to expand...
Click to collapse
1. Have NOT tried to format data
2. Originally tried to install cm touch, which at that time seemed like it didnt work (could not boot into rom) so I tried to install TWRP for some reason
3. I have attempted to boot stock rom, but always gets hung up on "beats audio" audio screen
unremarked said:
Hmm. Have you attempted to format data while in TWRP recovery? Also a few more details please--once you had unlocked the bootloader and installed TWRP, did you attempt to install a ROM from that point or boot into stock? If it's the latter, have you attempted to fastboot flash a boot.img from a stock ROM/NAND backup?
Click to expand...
Click to collapse
Wow, saved my ass. I formatted /data and now I can finally boot into CM after a fresh ROM install.
Thanks
nullkill said:
I have always had better luck with CWM clockworkmod recovery than TWRP for these kind of situations. So you might want to use the all in one and put Clockwork on. Also when sideloading a rom make sure to rename the rom something nice and short like rom.zip no spaces no numbers just simple and short or it will fail.
Click to expand...
Click to collapse
1. Loaded ClockworkMod Recovery v6.0.3.1
2. Rebooted to recovery
Result:
Loaded CM Recovery and at the bottom it says:
"E: Cant mount /cache/recovery/command
E: Cant mount /cache/recovery/log
E: Cant open/cache/recovery/log
E: Cant mount /cache/recovery/last_log
E: Cant open/cache/recovery/last_log"
Q: Should I try formatting the drive
nullkill said:
I have always had better luck with CWM clockworkmod recovery than TWRP for these kind of situations. So you might want to use the all in one and put Clockwork on. Also when sideloading a rom make sure to rename the rom something nice and short like rom.zip no spaces no numbers just simple and short or it will fail.
Click to expand...
Click to collapse
Side loaded the rom through cwm recovery.
"sideload started...
failed to open driver control: No such file or directory
Restarting adbd...
failed to open driver control: No such file or directory
E: Can't mount /cache/recovery/last_install
E: failed to open last_install: Invalid argument
Finding update package...
Opening update package...
Installing update...
E: Cant mount /cache/recovery/log
E: Cant open/cache/recovery/log
E: Cant mount /cache/recovery/last_log
E: Cant open/cache/recovery/last_log"
UPDATE: After I rebooted it just cycles for the CyanogenMod boot then restarts etc etc...
rafalk86 said:
Side loaded the rom through cwm recovery.
"sideload started...
failed to open driver control: No such file or directory
Restarting adbd...
failed to open driver control: No such file or directory
E: Can't mount /cache/recovery/last_install
E: failed to open last_install: Invalid argument
Finding update package...
Opening update package...
Installing update...
E: Cant mount /cache/recovery/log
E: Cant open/cache/recovery/log
E: Cant mount /cache/recovery/last_log
E: Cant open/cache/recovery/last_log"
UPDATE: After I rebooted it just cycles for the CyanogenMod boot then restarts etc etc...
Click to expand...
Click to collapse
Two things here:
1) Clearing Cache fixes the cache issue you see...
2) To fix the boot loop, you need to `Format /data and /data/media` under `Mounts and Storage`.
That should fix you up.... side loading wont fix a bad /data partition.
kenyu73 said:
Two things here:
1) Clearing Cache fixes the cache issue you see...
2) To fix the boot loop, you need to `Format /data and /data/media` under `Mounts and Storage`.
That should fix you up.... side loading wont fix a bad /data partition.
Click to expand...
Click to collapse
1. Cleared cache - fixed
2. Both datas formatted
Q: Its been a long 24hrs, now I load rom, correct?
rafalk86 said:
1. Cleared cache - fixed
2. Both datas formated
Q: Its been a long 24hrs, now I load rom, correct?
Click to expand...
Click to collapse
It sounds like you have a ROM loaded if its cycling at the BeatsAudio screen. Yes, you can do the ROM now. Make sure you do a factory reset before installing the ROM (or after I suppose)
rafalk86 said:
Long story short,
Purchased a Tmobile HTC One, Planned on taking it over to Straight Talk.
I have not asked any questions because I can usually figure this out.
Facts:
Unlocked using All In One
TWRP recovery
Issue:
Keep rebooting once it gets to the HTC One screen with Beats Audio
I am about 22 hours into this and very frustrated, it seems as though I do not have an O.S.
Cannot mount E:
Click to expand...
Click to collapse
Are you using Mac OSX? What is the format of the external_sd card? Is it formatted FAT, FAT32, or EX_FAT?
Clockworkmod does not support EX_FAT, so you must format it to FAT in order for it to mount. OSX can't format FAT32, so you must format FAT.
Have a HTC One, and after trying to install wrong zip file. The following show up in CWM/TWRP. Wont mount SDcard
E: unable to mount /cache
E: unable to mount /data
E: unable to mount /system
Phone is with Rogers Canada, and there is NO RUU available. Phone is NOT S-Off/SuperCID
I am not able to do adb push xxx /data.
How to proceed? Thanks!
Thoughts?
Time to S-Off and install custom recovery.
Can't adb push revone, have you tried factory reset through bootloader? Ah it won't mount though huh. Did you figure it out already?
Sent from my HTC One using Tapatalk 4
No.. Can't S-Off without going to OS..
Time to ADB push a rom to your device and sideload it
sideload without a working sdcard??
Hoping ADB sees the sd partition even tho the recovery programs do not. It's worth a shot, given you don't have an RUU
How about fastboot flash a system.img? And boot.img? Maybe that'd work. And if you need a system.img I think cwm is able to make one, I can check it out if you need it
Sent from my Nexus 4 using Tapatalk 4 Beta
I have a system.img I dd'd from a cm10 ROM, I figured it would be lighter than sense and get you booting if you haven't yet. Let me know.
Sent from my One using Tapatalk 4 Beta
Just another thread about the One becoming stuffed and not able to operate. I feel sorry for you son, same how I feel for myself.
Either there is a real issue with the One or there are issues with the recoveries, this is becoming far to common now, having our phones fail
Hi, I hope some can help me
Here´s my story, the phone is a Galaxy Ace GT-S5830m, that had GingerBread 2x, I wanted to take it to Kit kat 4x, then I downloaded the CWM 6.0.4.6, but, because of my ignorance, I didn't downloaded the KitKat rom file at the same time, I successfully installed the CWM file, but after this the phone won't boot. The only thing it does is:
Enter recovery mode by pressing Volume Up+Home+Power
Show the Samsung logo
But I cannot make it enter download mode, if I hit VolumeDown+Home+Power it just shows the Samsung logo
If I connect it to the PC via USB cable, the PC won't recognize the phone on the USB drivers list. I already downloaded the Samsung USB drivers
When I enter recovery mode I see the four options for
rebbot system now
apply update from sdcard
wipe date/factory reset
wipe cache partition
And below that I see --Appling Multi-CSC --
E:failed to mount /system (Invalid argument)
E:failed to mount /system (Invalid argument)
What can I do? I'm I done? Please help! Thanks!
egomezmx said:
Hi, I hope some can help me
Here´s my story, the phone is a Galaxy Ace GT-S5830m, that had GingerBread 2x, I wanted to take it to Kit kat 4x, then I downloaded the CWM 6.0.4.6, but, because of my ignorance, I didn't downloaded the KitKat rom file at the same time, I successfully installed the CWM file, but after this the phone won't boot. The only thing it does is:
Enter recovery mode by pressing Volume Up+Home+Power
Show the Samsung logo
But I cannot make it enter download mode, if I hit VolumeDown+Home+Power it just shows the Samsung logo
If I connect it to the PC via USB cable, the PC won't recognize the phone on the USB drivers list. I already downloaded the Samsung USB drivers
When I enter recovery mode I see the four options for
rebbot system now
apply update from sdcard
wipe date/factory reset
wipe cache partition
And below that I see --Appling Multi-CSC --
E:failed to mount /system (Invalid argument)
E:failed to mount /system (Invalid argument)
What can I do? I'm I done? Please help! Thanks!
Click to expand...
Click to collapse
Hi
Flash a custom recovery like cwm v5 n then erase all like data sytem etc then download the .zip file that roots ur fone n flash it n then do a wipe data n thn place any custom rom of ur device n flash. . . If dsnt wrk do tl me
Hit Thanks
more questions
Raakib Zargar said:
Hi
Flash a custom recovery like cwm v5 n then erase all like data sytem etc then download the .zip file that roots ur fone n flash it n then do a wipe data n thn place any custom rom of ur device n flash. . . If dsnt wrk do tl me
Hit Thanks
Click to expand...
Click to collapse
Hi Raakib, thanks for taking the time to answer! But how can I put the cwm v5 in the phone if the PC doesn't see the phone? Sorry for the basic questions? I'm new in this things. The first time I did this I pluged the phone to the PC and I was able to see the memory card in the windows explorer so I only did a drag and drop, but that doesn't work any more, please advice, thanks!
just do 1 thing download the recovery file on your pc and then plug your sd card using any sort of card reader and then copy the file to memory card . Then insert the memory card in the phone and go to recovery and flash it. Hit thanks.
---------- Post added at 03:30 AM ---------- Previous post was at 03:28 AM ----------
if u want that your pc should recognize your phone, take it to download mode and see it gets detected in odin or not , if not then swap the drivers maybe upgrade or downgrade.
still no luck
Raakib Zargar said:
just do 1 thing download the recovery file on your pc and then plug your sd card using any sort of card reader and then copy the file to memory card . Then insert the memory card in the phone and go to recovery and flash it. Hit thanks.
---------- Post added at 03:30 AM ---------- Previous post was at 03:28 AM ----------
if u want that your pc should recognize your phone, take it to download mode and see it gets detected in odin or not , if not then swap the drivers maybe upgrade or downgrade.
Click to expand...
Click to collapse
Hi Raakib, just to let you know that I haven't had any luck with this, this is what I have tried, with a memory card reader connect to my PC, because the PC still doesn't see the phone
Using CWM v5.0.2.6 and with that version trying to install the original rom I get this
-- Installing: /sdcard/Downloads/S5830MUMnD1_S5830MTCEND1_TCE.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted.
So my attempt to recover gingerbread was unsuccessful, now, in all honesty I have no idea if I'm using the correct zip file of gingerbread, I mean, I downloaded from the sammobile page and choose the one for my country, but the instructions call for odin and to unzip the fiel, so I don't know if this zip file can just be copied to the SDcard and be unziped with CWM. So CMW needs special rom files different from the ones odin uses?
On my second attempt using CWM 6.0.4.6 to try to install kit kat 4.4 using the instructions from the androidcure website called "How to install Android KitKat on Samsung Galaxy Ace S5830", it mentions that I must use cwm v6 and the rom file called cm-11.0.0-RC4-GT-S5830-cooper-PS.zip I get this
-- Install /sdcard/Downloads ...
Finding update package...
Opening update package...
This package is for "cooper.GT-S5830" devices: this is a "".
E:Error in /tmp/sideload/package.zip
(status 7)
Installation aborted
If I use cwm v5 to try to mount /system (which is permanently un-mounted) I get this
mount: mounting /dev/block/stl9 on /system failed: Invalid argument
W:failed to mount /dev/block/stl9 (File exists)
W:failed to mount /dev/blockstl9 (no such device)
Error mounting system!
The phone still won't go in download mode and is still not visible by the PC
Any other suggestion? Thanks!!!!
egomezmx said:
Hi Raakib, just to let you know that I haven't had any luck with this, this is what I have tried, with a memory card reader connect to my PC, because the PC still doesn't see the phone
Using CWM v5.0.2.6 and with that version trying to install the original rom I get this
-- Installing: /sdcard/Downloads/S5830MUMnD1_S5830MTCEND1_TCE.zip
Finding update package...
Opening update package...
Installing update...
Installation aborted.
So my attempt to recover gingerbread was unsuccessful, now, in all honesty I have no idea if I'm using the correct zip file of gingerbread, I mean, I downloaded from the sammobile page and choose the one for my country, but the instructions call for odin and to unzip the fiel, so I don't know if this zip file can just be copied to the SDcard and be unziped with CWM. So CMW needs special rom files different from the ones odin uses?
On my second attempt using CWM 6.0.4.6 to try to install kit kat 4.4 using the instructions from the androidcure website called "How to install Android KitKat on Samsung Galaxy Ace S5830", it mentions that I must use cwm v6 and the rom file called cm-11.0.0-RC4-GT-S5830-cooper-PS.zip I get this
-- Install /sdcard/Downloads ...
Finding update package...
Opening update package...
This package is for "cooper.GT-S5830" devices: this is a "".
E:Error in /tmp/sideload/package.zip
(status 7)
Installation aborted
If I use cwm v5 to try to mount /system (which is permanently un-mounted) I get this
mount: mounting /dev/block/stl9 on /system failed: Invalid argument
W:failed to mount /dev/block/stl9 (File exists)
W:failed to mount /dev/blockstl9 (no such device)
Error mounting system!
The phone still won't go in download mode and is still not visible by the PC
Any other suggestion? Thanks!!!!
Click to expand...
Click to collapse
the stock/original rom wont flash in the recovery. try to flash some other custom rom in CWM 5 and before flahing any rom you need to do a full factory reset and whether in cwm5 or 6 i m nt sure go into advance and wipe efs etc there then flash a rom. If still nothing then contact me i will tell you some great thing +918715031141. (my personal number)
Hello everyone,
First off all, Im not very experienced with all the android stuff, so I tried to flash some custom rom on my Huawei P9 but before flashing I did an andvanced wipe on my TWRP 5.1.0-.0.
The problem is, that I peace of s**t wiped all options, from Davlik/ART Cache about system to version.
I luckily did a nandroid backup before do this, so I restored it but now Im getting the failure every time I try to flash the custom rom or do a factory reset...
Failed to mount ´/vendor´ (Invalid argument)
Failed to mount ´/product´ (Invalid argument)
Failed to mount ´/version´ (Invalid argument)
On every boot it restarts to the eRecovery, what should I do?
Bluesyle said:
Hello everyone,
First off all, Im not very experienced with all the android stuff, so I tried to flash some custom rom on my Huawei P9 but before flashing I did an andvanced wipe on my TWRP 5.1.0-.0.
The problem is, that I peace of s**t wiped all options, from Davlik/ART Cache about system to version.
I luckily did a nandroid backup before do this, so I restored it but now Im getting the failure every time I try to flash the custom rom or do a factory reset...
Failed to mount ´/vendor´ (Invalid argument)
Failed to mount ´/product´ (Invalid argument)
Failed to mount ´/version´ (Invalid argument)
On every boot it restarts to the eRecovery, what should I do?
Click to expand...
Click to collapse
If you can still get into TWRP then try flashing the backed up (or stock, extracted from a stock ROM) boot.img first. This will bring those partitions back (I think). Don't do this with the restore method in twrp, instead use the install button then change from .zip to .img.
Have you tried the dload method to flash back to stock or the huawei updater and hisense? Then redo everything from unlocking the bootloader to installing twrp and root. From there try to restore your backup. As far as i know this should work if all else fails, having done the exact same thing myself as you previously.
In the future when installing a custom rom the only partitions you need to wipe for a clean install are
Dalvik/ART
Cache
System
Data
Internal Storage (optional)
lostunsunghero said:
If you can still get into TWRP then try flashing the backed up (or stock, extracted from a stock ROM) boot.img first. This will bring those partitions back (I think). Don't do this with the restore method in twrp, instead use the install button then change from .zip to .img.
Have you tried the dload method to flash back to stock or the huawei updater and hisense? Then redo everything from unlocking the bootloader to installing twrp and root. From there try to restore your backup. As far as i know this should work if all else fails, having done the exact same thing myself as you previously.
In the future when installing a custom rom the only partitions you need to wipe for a clean install are
Dalvik/ART
Cache
System
Data
Internal Storage (optional)[/Q
Hey, thank u for the answere,
I tried the dload methode, I just booted to the stock recovery for about 2 hours...
About the boot.img: I didnt found any boot.img based on the stock rom on the internet... Should I try the pre-rooted img form this Thread ?
Click to expand...
Click to collapse
Bluesyle said:
Hey, thank u for the answere,
I tried the dload methode, I just booted to the stock recovery for about 2 hours...
About the boot.img: I didnt found any boot.img based on the stock rom on the internet... Should I try the pre-rooted img form this Thread ?
Click to expand...
Click to collapse
Only if you were on b378 before you messed up the phone or plan on flashing a b378 based ROM. Otherwise you will have to download a stock firmware and extract the boot.img from there. You can find stock firmwares in this thread:
https://forum.xda-developers.com/p9/development/rom-stock-rom-eva-l19c636b168-t3419586
Bluesyle said:
Hello everyone,
Click to expand...
Click to collapse
Reflash stock rom Boot into stock recovery after flash and wipe data factory reset.
Sent from my NATASHA using Tapatalk
Same Problem with Huawei Honor 8 FRD-L04
Having the same issue only without these vendor, version, etc mounting, nothing will flash...including stock. Bootloader works, TWRP works, cant mount, repair, or format partitions. This happened after flashing Revolution I believe. If anyone has a walk through for a potential fix, I'm all ears!
chemicalfx said:
Having the same issue only without these vendor, version, etc mounting, nothing will flash...including stock. Bootloader works, TWRP works, cant mount, repair, or format partitions. This happened after flashing Revolution I believe. If anyone has a walk through for a potential fix, I'm all ears!
Click to expand...
Click to collapse
were you able to find a fix?
Failed to mount
Hi everyone,
I did a disaster My Huawey P9 have non OS installed. I can only enter into TWRP 3.1.0-3 version.
The TWRP write:
Updating partition details...
Failed to mount '/cust' (Invalid argument)
Failed to mount '/system' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/product' (Invalid argument)
Failed to mount '/version' (Invalid argument)
...done
Full SELinux support is present.
MTP Enableb
What can I do to install the OS and unbrick the phone? Can you help me step by step?
Thank you very much
cfrisen said:
Hi everyone,
I did a disaster :
Click to expand...
Click to collapse
Man, i am in same problem like you did. If you find solution please pm me, i will do the same.
džejms din said:
Man, i am in same problem like you did. If you find solution please pm me, i will do the same.
Click to expand...
Click to collapse
Guy please tell me how you solved this problem!!!
Bluesyle said:
Guy please tell me how you solved this problem!!!
Click to expand...
Click to collapse
Sorry to say you but there was no solution for it. I did send my phone to servise and still wait for call.. in theory fix should be easy (with their tools etc..) but i am still not sure will they fix it or not.
When they call me i will tell you how much it cost and what they did to it..if they could. Worst case scenario i will sell my phone in parts and get some money back.
chemicalfx said:
Having the same issue only without these vendor, version, etc mounting, nothing will flash...including stock. Bootloader works, TWRP works, cant mount, repair, or format partitions. This happened after flashing Revolution I believe. If anyone has a walk through for a potential fix, I'm all ears!
Click to expand...
Click to collapse
Every few days somebody opens such a thread, having the phone similarly bricked. When asking what did you do, it turns out that he was on some of the AOSP based custom ROMs (there are couple of them), and he wanted to go back to stock, or he wanted to try/flash to the other custom ROM, etc.
I really wonder (I never tried those AOSP based custum ROMs - AFAIK, drivers for camera are not published and all those AOSP ROMs cannot utilize the main strength on this phone, the camera. Besides, I'm happily using another custom ROM that is stock based [hence havint the stock Camera app] but debloated, prerooted by Magisk, etc) do the corresponding AOSP custom ROM threads provide FAQ or information how to go back to stock (maybe they do but people don't bother to read)?
If they don't provide such info, why people do not first ask there (before bricking the phone)? IMO, developers of those custom ROKs would know the answer, if asked (supposidely they test their custom ROMs on various configurations and they have to go back to stock and forth to custom).
It will be helpful to ask and to get the answer in those threads for future users who will similarly come to try the ROMs, but maybe then also want tto go back to stock - to prevent that they similarly brick the phones.
---------- Post added at 12:28 AM ---------- Previous post was at 12:26 AM ----------
džejms din said:
Sorry to say you but there was no solution for it. I did send my phone to servise and still wait for call.. in theory fix should be easy (with their tools etc..) but i am still not sure will they fix it or not.
When they call me i will tell you how much it cost and what they did to it..if they could. Worst case scenario i will sell my phone in parts and get some money back.
Click to expand...
Click to collapse
DC Phoenix (15 EU) might be cheaper than service shop:
https://www.dc-unlocker.com/DC-Phoenix-flash-repair-tutorial
Chrome will automatically translate:
https://www.android-hilfe.de/forum/...-wiederherstellung-mit-dc-phoenix.818669.html
cfrisen said:
Hi everyone,
I did a disaster My Huawey P9 have non OS installed. I can only enter into TWRP 3.1.0-3 version.
The TWRP write:
Updating partition details...
Failed to mount '/cust' (Invalid argument)
Failed to mount '/system' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/product' (Invalid argument)
Failed to mount '/version' (Invalid argument)
...done
Full SELinux support is present.
MTP Enableb
What can I do to install the OS and unbrick the phone? Can you help me step by step?
Thank you very much
Click to expand...
Click to collapse
Do not worry. First when u r in twrp wipe your system , cache, and dalvik cache partitions. Then extract the big update.app file and extract the boot, recovery and system images. Then flash recovery first and boot image and system image using fastboot. Then take a microsd card create a folder dload and place the big update.app file inside it and put it in ur phone.
Now press vol up vold down and power button till u see the huawei logo.
Wait for some time. You will see the device starts updating. After the update finishes reboot phone.
There you go phone starts working. Now huawei logo will flash for some time. If it is taking too long go to recovery by pressing vol up and power then do wipe data and cache. The process might fail but no problem press reboot and your phone will work.
---------- Post added at 09:45 AM ---------- Previous post was at 09:22 AM ----------
cfrisen said:
Hi everyone,
I did a disaster My Huawey P9 have non OS installed. I can only enter into TWRP 3.1.0-3 version.
The TWRP write:
Updating partition details...
Failed to mount '/cust' (Invalid argument)
Failed to mount '/system' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/product' (Invalid argument)
Failed to mount '/version' (Invalid argument)
...done
Full SELinux support is present.
MTP Enableb
What can I do to install the OS and unbrick the phone? Can you help me step by step?
Thank you very much
Click to expand...
Click to collapse
Do not worry. First when u r in twrp wipe your system , cache, and dalvik cache partitions. Then extract the big update.app file and take oou the boot, recovery and system images. Then flash recovery first and boot image and system image using fastboot. Then take a microsd card create a folder dload and place the big update.app file inside it and put it in ur phone.
Now press vol up vold down and power button till u see the huawei logo.
Wait for some time. You will see the device starts updating. After the update finishes reboot phone.
There you go phone starts working. Now huawei logo will flash for some time. If it is taking too long go to recovery by pressing vol up and power then do wipe data and cache. The process might fail but no problem press reboot and your phone will work.
Thank you!
King_of_Android said:
Do not worry. First when u r in twrp wipe your system , cache, and dalvik cache partitions. Then extract the big update.app file and extract the boot, recovery and system images. Then flash recovery first and boot image and system image using fastboot. Then take a microsd card create a folder dload and place the big update.app file inside it and put it in ur phone.
Now press vol up vold down and power button till u see the huawei logo.
Wait for some time. You will see the device starts updating. After the update finishes reboot phone.
There you go phone starts working. Now huawei logo will flash for some time. If it is taking too long go to recovery by pressing vol up and power then do wipe data and cache. The process might fail but no problem press reboot and your phone will work.
---------- Post added at 09:45 AM ---------- Previous post was at 09:22 AM ----------
Do not worry. First when u r in twrp wipe your system , cache, and dalvik cache partitions. Then extract the big update.app file and take oou the boot, recovery and system images. Then flash recovery first and boot image and system image using fastboot. Then take a microsd card create a folder dload and place the big update.app file inside it and put it in ur phone.
Now press vol up vold down and power button till u see the huawei logo.
Wait for some time. You will see the device starts updating. After the update finishes reboot phone.
There you go phone starts working. Now huawei logo will flash for some time. If it is taking too long go to recovery by pressing vol up and power then do wipe data and cache. The process might fail but no problem press reboot and your phone will work.
Click to expand...
Click to collapse
Thank you :good: @King_of_Android.. I had a same issue in my Honor-5c Indian variant for Vendor and System.. Followed your simple steps and it worked flawlessly. BTW few applications are missing like Clock, themes, file explorer..... Do you any idea ?
When I try to flash the system.img, it comes the following message:
Code:
fastboot flash system SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (460631 KB)...
OKAY [ 12.205s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 12.241s
When I try to check the unlock status it comes:
Code:
fastboot getvar unlocked
getvar:unlocked FAILED (remote: Command not allowed)
finished. total time: 0.008s
And at last:
Code:
fastboot oem unlock *code*
...
FAILED (remote: already fastboot unlocked)
finished. total time: 0.005s
Any idea? :silly:
did u found a fix??
cfrisen said:
Hi everyone,
I did a disaster My Huawey P9 have non OS installed. I can only enter into TWRP 3.1.0-3 version.
The TWRP write:
Updating partition details...
Failed to mount '/cust' (Invalid argument)
Failed to mount '/system' (Invalid argument)
Failed to mount '/vendor' (Invalid argument)
Failed to mount '/product' (Invalid argument)
Failed to mount '/version' (Invalid argument)
...done
Full SELinux support is present.
MTP Enableb
What can I do to install the OS and unbrick the phone? Can you help me step by step?
Thank you very much
Click to expand...
Click to collapse
did you found the correct metheod to fix it.
TWRP builds for P9 Android MM, N, O
TWRP must be ported to the particular device and firmware to support its partitions set-up, encryption, etc
No wonder that installing inappropriate TWRP and using it to flash something can brick your device
For Huawei it means that different ports of TWRP are required for different EMUI versions (4, 5 or 8)
In other words, depending on your P9 stock Android version, the following TWRP builds are proven (and AFAIK the newest)
- For Marshmallow, P9-EVA-TWRP-Android-6 from this post:
https://forum.xda-developers.com/showpost.php?p=72153575&postcount=2
- For Nougat, twrp-3.1.1-1-eva_extended from this post:
https://forum.xda-developers.com/showpost.php?p=75787111&postcount=1
- For Oreo, P9-EVA-8.0.0-TWRP-v4 from this post
https://forum.xda-developers.com/showpost.php?p=77161313&postcount=2
Bluesyle said:
Hello everyone,
First off all, Im not very experienced with all the android stuff, so I tried to flash some custom rom on my Huawei P9 but before flashing I did an andvanced wipe on my TWRP 5.1.0-.0.
The problem is, that I peace of s**t wiped all options, from Davlik/ART Cache about system to version.
I luckily did a nandroid backup before do this, so I restored it but now Im getting the failure every time I try to flash the custom rom or do a factory reset...
Failed to mount ´/vendor´ (Invalid argument)
Failed to mount ´/product´ (Invalid argument)
Failed to mount ´/version´ (Invalid argument)
On every boot it restarts to the eRecovery, what should I do?
Click to expand...
Click to collapse
I managed to fix this. My P9 was bricked, fastboot display an erro(11) and the above when trying to flash a rom in TWRP.
First download a stock rom, if possible the rom version that came with your phone, unzip update.zip to get update.app. Download app extractor and extract vendor.img, product.img, verlist.img, system.img then flash all img in fastboot, i.e., fastboot vendor vendor.img..
Erecovery mode will now be possible, connect to wifi and recover phone.
dimsum888 said:
I managed to fix this. My P9 was bricked, fastboot display an erro(11) and the above when trying to flash a rom in TWRP.
First download a stock rom, if possible the rom version that came with your phone, unzip update.zip to get update.app. Download app extractor and extract vendor.img, product.img, verlist.img, system.img then flash all img in fastboot, i.e., fastboot vendor vendor.img..
Erecovery mode will now be possible, connect to wifi and recover phone.
Click to expand...
Click to collapse
Does you need to re-unlock your phone after this ?
Bluesyle said:
Hello everyone,
First off all, Im not very experienced with all the android stuff, so I tried to flash some custom rom on my Huawei P9 but before flashing I did an andvanced wipe on my TWRP 5.1.0-.0.
The problem is, that I peace of s**t wiped all options, from Davlik/ART Cache about system to version.
I luckily did a nandroid backup before do this, so I restored it but now Im getting the failure every time I try to flash the custom rom or do a factory reset...
Failed to mount ´/vendor´ (Invalid argument)
Failed to mount ´/product´ (Invalid argument)
Failed to mount ´/version´ (Invalid argument)
On every boot it restarts to the eRecovery, what should I do?
Click to expand...
Click to collapse
Bro today i found solution for this problem i was also getting error i was very frustrated
first of all download the original firmware from the manufacturer and unzip all the files you will find many images file such as boot.img,vbmeta.img...etc extract all the img files from the rom and place it in your desktop.
then whatervr invalid arguments you were getting such as vendor product etc this all comes inside the SUPER.IMG file you have to do only one thing go to fastboot mode and flash super.img file while booting your phone in fastboot mode
command:
fastboot flash super super.img
then it will take a while and congtrats all errors fixed after struggling and searching almost two hour i didnt gat a way out i wan not able t copy super.img file directly into storage i dont know why but after this the phone became normal
if you face any issues then tell i will send screenshots of everything