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
Hi guys. Wonder if u could help me out here as i'm new to andriod.
i just got my HTC One and decided to root it.
Downloaded the toolkit from http://forum.xda-developers.com/showthread.php?t=2183942.
Followed the instructions from 1 to 5 and sucessfuly unlocked my bootloader.
After that i flash a recovery (i chose TWRP(SPRINT ONLY).)
The next thing i did, which i think was wrong was to flash the kernel using the TWRP.img provided in the toolkit.
Now whenever i boot up it goes into TWRP.
After some attempts of searching
I managed to find a stock kernel online and attempt to flash it (boot.img).
Now i can go back into the "normal" phone mode but i can't seem to enable my wifi and camera.
Would appreciate if u guys could give me some advice.
Thanks.
i got my set from Singapore so i'm guessing it's a Asia set (LTE edition)
up for awareness~
Where you went wrong was flashing a kernel for no reason. The first flash was incompatible with your stock Rom, and I'm going to shoot in the dark here and say the second flash is for a different handset such as the t-mobile version. What you're going to want to do here is download any Rom and flash it via recovery it will replace your kernel and current Rom. If you want to stay close to stock install android revolution hd. Keep in mind this will wipe all of your data but hey, it's better than nothing.
Sent from my HTC One using xda premium
---------- Post added at 11:55 AM ---------- Previous post was at 11:46 AM ----------
This is of course assuming the reason you rooted was to install custom roms otherwise push different stock kernels until things work. Flashing a new Rom is just less of a pain.
Sent from my HTC One using xda premium
thanks for the advice bro.
I dun think i can flash a custom rom now. i run a check using a root checker app and it indicates that i do not have proper root acess.
i do have my bootloader unlocked and "tampered"
I fired up the TWRP recovery and tried to push the Superuser.zip into the phone to install.
However the command terminal on the TWRP have the following errors:
E: Unable to mount /data
E: Unable to recreate /data/media folder.
Updating paratition details...
E: unable to mount /cache
E: unable to mount .data
E: Unable to mount internal storage.
E: unable to mount /data/media during GUI startup
E: unable to mount /cache
E: TWFunc:: Copy_Log -- Can't open destination location
E: unable to mount /cache
E: Unable to mount /data/media/TWRP/.twrp when
E: unable to mount /data
I'm really lost and appreciate all the help i can get.
Thanks in advance~!
Yeah, it looks like you flashed something incompatible. That messes up your partitions. I don't know why there is still such a disparity between GSM and CDMA.
Partitions messed up = RUU I believe.
Make sure you use the Sprint RUU!
Actually, try side loading a ROM. I hear that works if you can still access recovery.
does sideloading a ROM works even if i have no root access?
I have unlocked and tamper my bootloader. However the root checker app indicates i have no proper root access.
Look up the instructions. I don't think you need root, just an unlocked biotloader and custom recovery. But I could be wrong, I've never done it.
First you have to find out what phone you have ... Even though their is one name for this device HTC made different variants of the device.
2. The way you unlocked / rooted your phone will not allow you to flash any file correctly unless you follow certain procedures. Since you used HTC unlock you are still s-on but are allowed to flash certain things.
3. Why did you flash a sprint version of twrp? Every recovery has mount points for the device set already .. That may be why you are getting errors
Sent from my HTC One using xda premium
hmmm..
things may be a lot easier if i have my hands on the stock RUU for my phone. However a quick check on the official website shows that it's not available for my phone.(yet i hope)
yes i flash the recovery with a TWRP Sprint version.
hmm what do u mean by different mounts bro?
sad_how said:
hmmm..
things may be a lot easier if i have my hands on the stock RUU for my phone. However a quick check on the official website shows that it's not available for my phone.(yet i hope)
yes i flash the recovery with a TWRP Sprint version.
hmm what do u mean by different mounts bro?
Click to expand...
Click to collapse
E: Unable to mount /data
E: Unable to recreate /data/media folder.
Updating paratition details...
E: unable to mount /cache
E: unable to mount .data
E: Unable to mount internal storage.
E: unable to mount /data/media during GUI startup
E: unable to mount /cache
E: TWFunc:: Copy_Log -- Can't open destination location
E: unable to mount /cache
E: Unable to mount /data/media/TWRP/.twrp when
E: unable to mount /data
You see how you got this error...
/data
/cache
/ system ...etc.. Those are mount points so if you flashed a sprint twrp recovery and you have an international HTC one when you try and flash something with twrp it doesnt know how to mount what it needs to mount in order to flash correctly ...
Sent from my HTC One using xda premium
Correct me if I'm wrong but I was wondering why you flashed twrp for sprint when your phone is from Singapore most likely an Asian version of the phone I thought sprint was for us version of the phone?
First of all, hello.
My Moto G 2nd generation died suddenly. And i can't turn it on no way.. It's a XT1068 version.
I've read the forum and tried some things, but they're not working. I got into bootloader and recovery mode. And when i try to ""Wipe data/factory reset" or "Wipe cache partition" i get error messages, saying:
"E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last/install
E: Failed closing /dev/block/platform/ms_sdcc. 1/by-name/misc
(I/0 error)"
I don't know what to do already, i don't understand a lot of phones, and i've done nothing to it, this is the way the phone "came from fabric", so i did not touch a lot of things. And i wonder if anyone has a solution for this..
If i turn the phone on either the screen stays black, or a sign of "dead" android comes up saying "no commands" or the M of motorola start keeps loading forever.
ANY SOLUTION PLEASE? =( THANKS!
Seems like you need to flash a rom because yours isn't working.
1. Is your bootloader unlocked? If not then click here : https://www.youtube.com/watch?v=BLSTDsFG1xw (stop watching at like 4:40) just follow the instructions
2. Download: http://forum.xda-developers.com/mot...dows-tool-moto-g-2014-xt1064-restore-t2957167
3. This should restore your phone back to stock 4.4.4 and stock recovery.
Hope This helped!
(Not my fault if something goes wrong with your phone )
FrankCABJ said:
First of all, hello.
My Moto G 2nd generation died suddenly. And i can't turn it on no way.. It's a XT1068 version.
I've read the forum and tried some things, but they're not working. I got into bootloader and recovery mode. And when i try to ""Wipe data/factory reset" or "Wipe cache partition" i get error messages, saying:
"E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last/install
E: Failed closing /dev/block/platform/ms_sdcc. 1/by-name/misc
(I/0 error)"
I don't know what to do already, i don't understand a lot of phones, and i've done nothing to it, this is the way the phone "came from fabric", so i did not touch a lot of things. And i wonder if anyone has a solution for this..
If i turn the phone on either the screen stays black, or a sign of "dead" android comes up saying "no commands" or the M of motorola start keeps loading forever.
ANY SOLUTION PLEASE? =( THANKS!
Click to expand...
Click to collapse
"came from fabric" so you got broken phone out of box? If so then just return it back.
FrankCABJ said:
First of all, hello.
My Moto G 2nd generation died suddenly. And i can't turn it on no way.. It's a XT1068 version.
I've read the forum and tried some things, but they're not working. I got into bootloader and recovery mode. And when i try to ""Wipe data/factory reset" or "Wipe cache partition" i get error messages, saying:
"E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_install
E: Can't open /cache/recovery/last/install
E: Failed closing /dev/block/platform/ms_sdcc. 1/by-name/misc
(I/0 error)"
I don't know what to do already, i don't understand a lot of phones, and i've done nothing to it, this is the way the phone "came from fabric", so i did not touch a lot of things. And i wonder if anyone has a solution for this..
If i turn the phone on either the screen stays black, or a sign of "dead" android comes up saying "no commands" or the M of motorola start keeps loading forever.
ANY SOLUTION PLEASE? =( THANKS!
Click to expand...
Click to collapse
Just restore it using mfastboot v2 with factory firmware image, it works fine...
Some days back I got same problem when I was trying to flash custom rom but couldn't flash because of these errors. so I restored it to 5.0.2 now it works as expected but I am unable to flash custom roms... what can be the solution for this. if anyone knows... tia
Hey, so I somehow bricked my phone. I wanted to root my phone and I got stuck in download mode. So i flashed it with odin. It passes perfectly everytime, but then I get stuck in android recovery mode, where at the bottom I get these errors:
Suported API: 3
E: failed to mount /efs (Invalid argument)
E: failed to mount /efs (Invalid argument)
E: failed to mount /efs (Invalid argument)
dm-verity verification failed...
Can someone can help me? I'm not a pro at these situations, so I relly need help.
What version did you flash on your phone? And what version were you trying to root
G920FXXU5DQA7_G920FBTU5DQA2_BTU works just fine for me to get at least in recovery mode. I can't tell you what version i used to root my phone, because I don't remember now and I deleted that fille. When I flash it, blue screen with "installing system update" and loading android logo shows up for a few seconds and then immediately recovery mode comes back. And the same 4 errors show up at the bottom.
Kingkhone said:
G920FXXU5DQA7_G920FBTU5DQA2_BTU works just fine for me to get at least in recovery mode. I can't tell you what version i used to root my phone, because I don't remember now and I deleted that fille. When I flash it, blue screen with "installing system update" and loading android logo shows up for a few seconds and then immediately recovery mode comes back. And the same 4 errors show up at the bottom.
Click to expand...
Click to collapse
Well this is the AT&T forum so I'm assuming that you have the AT&T model, after the underscore where it says G920F it should be G920A. Go back and get the correct firmware and it should work.
Sorry about that, wrong forum. I'm new in this web. I'm using G920F
Kingkhone said:
Hey, so I somehow bricked my phone. I wanted to root my phone and I got stuck in download mode. So i flashed it with odin. It passes perfectly everytime, but then I get stuck in android recovery mode, where at the bottom I get these errors:
Suported API: 3
E: failed to mount /efs (Invalid argument)
E: failed to mount /efs (Invalid argument)
E: failed to mount /efs (Invalid argument)
dm-verity verification failed...
Can someone can help me? I'm not a pro at these situations, so I relly need help.
Click to expand...
Click to collapse
Sounds to me like you would need to get a kernel with dm-verify removed or flash magisk, which does that for you.
The_scam said:
Sounds to me like you would need to get a kernel with dm-verify removed or flash magisk, which does that for you.
Click to expand...
Click to collapse
Thank you for your help, but I get the same problem. I tried to to emergency recovery with smart switch, but again I get stuck in recovery mode. When I try to reboot system, it gets stuck on black screen. In TWRP when I select backup, writes 0MB on the efs. Did I somehow wiped my efs partition? Is there any way I can fix it?
Kingkhone said:
Thank you for your help, but I get the same problem. I tried to to emergency recovery with smart switch, but again I get stuck in recovery mode. When I try to reboot system, it gets stuck on black screen. In TWRP when I select backup, writes 0MB on the efs. Did I somehow wiped my efs partition? Is there any way I can fix it?
Click to expand...
Click to collapse
Yes , you can use Odin to flash firmware 5.1.1 or greater
The_scam said:
Yes , you can use Odin to flash firmware 5.1.1 or greater
Click to expand...
Click to collapse
I try to flash 5.1.1, but I get sboot fail in odin. But I think I have bigger problem - I have lost my efs partition without doing any backup of it. Can I somehow reset my efs?
Kingkhone said:
I try to flash 5.1.1, but I get sboot fail in odin. But I think I have bigger problem - I have lost my efs partition without doing any backup of it. Can I somehow reset my efs?
Click to expand...
Click to collapse
No, try using Samsung software instead of Odin ?
The_scam said:
No, try using Samsung software instead of Odin
Click to expand...
Click to collapse
I don't understand what do you mean. Should I do this with smart switch or what?
Kingkhone said:
I don't understand what do you mean. Should I do this with smart switch or what?
Click to expand...
Click to collapse
I believe it was called Kies, if not that, try smart switch
The_scam said:
I believe it was called Kies, if not that, try smart switch
Click to expand...
Click to collapse
I'll try it
samsung galaxy s6 SM-G920A ayuda!!!
Tengo ese mismo problema pero en el samsung SM-G920A at&t soy de REP.DOM. mi whatsapp por si quieres ayudarme 829-367-7120
I get these errors:
Suported API: 3
E: failed to mount /efs (Invalid argument)
E: failed to mount /efs (Invalid argument)
E: failed to mount /efs (Invalid argument)
dm-verity verification failed...
Can someone can help me? I'm not a pro at these situations, so I relly need help.[/QUOTE]
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