Hi, i have a huge problem (probably for me ), my recovery can't mount /data, it goes like this "Failed to mount "/data" invalid argument". Im using TWRP 3.0.0-1
So ROM cant boot it stuck's (before that i have played with many experimental ROM's..)
And kdz updt doesn't work because when i trying to get in e/d mode it turns in fastboot..
What can i do to solve this? I tried something with adb but when i typing commands like adb usb, adb shell it comes with "Error: Closed"
So, friends, please help me, because im fcked out brains with that problem..
LG-E610 user
Ja_Ch said:
Hi, i have a huge problem (probably for me ), my recovery can't mount /data, it goes like this "Failed to mount "/data" invalid argument". Im using TWRP 3.0.0-1
So ROM cant boot it stuck's (before that i have played with many experimental ROM's..)
And kdz updt doesn't work because when i trying to get in e/d mode it turns in fastboot..
What can i do to solve this? I tried something with adb but when i typing commands like adb usb, adb shell it comes with "Error: Closed"
So, friends, please help me, because im fcked out brains with that problem..
LG-E610 user
Click to expand...
Click to collapse
Use format data in recovery and reboot
Jonas Cardoso said:
Use format data in recovery and reboot
Click to expand...
Click to collapse
Thanks a lot man, this helped me out )
The error continues
Jonas cardoso, do you hava nother solution?
askelam said:
Jonas cardoso, do you hava nother solution?
Click to expand...
Click to collapse
Try reflash Stock or format data in twrp
Format /data in Twrp worked
Jonas Cardoso said:
Try reflash Stock or format data in twrp
Click to expand...
Click to collapse
Thanks for it man
askelam said:
Thanks for it man
Click to expand...
Click to collapse
Nice
Related
Recently I had an update from ASUS and at that time I had root on my device...So I guess my phone got brick due to updating while having a rooted device...I have tried all the steps of flashing via adb..Did "fastboot flash boot boot.img" , "fastboot flash recovery recovery.img"...All goes well...
Now the problem is when I get into bootloader(Power + vol up)/recovery/apply update from ADB from my device and on my PC "adb sideload filename.zip" it just does nothing...My cmd just waits and same goes to my device all it is written are
E:Can't open /tmp/update-script.log
Now send the package you want to apply
to the device with adb sideload(filename)"...
EDIT-"adb devices" doesn't recognize my device only "fastboot devices" does
I hope someone could help or maybe lead me to a post which has the same problem...Or maybe I need to send my phone to Asus Service Center for this issue...My bet now if this doesn't works I would try to flash some custom ROM maybe
First step backup u r data by twrp custome recovery..then go to link
www.google.co.in/url?q=http://www.w...ggOMAE&usg=AFQjCNHyTiR4lWYSzNkTaJO83PBJIf9Buw
U r problem will solved
NOTE: U MUST RETURN TO U R STOCK ROM THEN APLLY KITKAT VER 2.20.40.53 THEN LOLLIPOP 3.20.40.52 THEN GO 30.20.40.78...
Same problem with the op. i'll follow the steps u give in the link but it still failed. its says (E: Can't mount /cache/recovery/log), (E: Can't open /cache/recovery/log), (E: failed to mount /cache), and it keeps repeating for (/cache/recovery/last_log), (/cache/recovery/last_insta). So, how do i fix it? anybody knows?
mrsajlast said:
Same problem with the op. i'll follow the steps u give in the link but it still failed. its says (E: Can't mount /cache/recovery/log), (E: Can't open /cache/recovery/log), (E: failed to mount /cache), and it keeps repeating for (/cache/recovery/last_log), (/cache/recovery/last_insta). So, how do i fix it? anybody knows?
Click to expand...
Click to collapse
U reset data and cache ??? From fastboot mode
mrsajlast said:
Same problem with the op. i'll follow the steps u give in the link but it still failed. its says (E: Can't mount /cache/recovery/log), (E: Can't open /cache/recovery/log), (E: failed to mount /cache), and it keeps repeating for (/cache/recovery/last_log), (/cache/recovery/last_insta). So, how do i fix it? anybody knows?
Click to expand...
Click to collapse
yasin0005 said:
U reset data and cache ??? From fastboot mode
Click to expand...
Click to collapse
i have similar problem with mrsajlast, and reset data and cache... how do i fix it ?? please help
UPDATE:
Version v15 seems to work now .. also on N preview now
Update.ZIP_TWRP_dragon_3.0.2-0_v15.zip (to be installed via TWRP)
TWRP_dragon_3.0.2-0_v15.img (to be installed via fastboot)
Download: https://onedrive.live.com/redir?res...17&authkey=!ACPxBsf1QD-Fr0M&ithint=folder,zip
Please test with encrypted data partition.
Big thanks to @NYCHitman1 for his help !
As well .. Thanks to all the encrypted Pixel C owners helping testing !
Thanks
DELETED
Tested version, bit still encypted Storage is not recongnized: Internal Storage 0MB!
RolfFrie said:
Tested version, bit still encypted Storage is not recongnized: Internal Storage 0MB!
Click to expand...
Click to collapse
Thanks for your test and feedback !
Not recognizing encrypted partition here either (NPD35K)
zezayer said:
Not recognizing encrypted partition here either (NPD35K)
Click to expand...
Click to collapse
Yep .. Thanks.
It's not working ... yet.
Not sure by when and by whom it will be implemented.
Will update the first page accordingly ..
EDIT:
You engage me for a new try ..
RolfFrie said:
Tested version, bit still encypted Storage is not recongnized: Internal Storage 0MB!
Click to expand...
Click to collapse
Maybe another test ?
TWRP_dragon_3.0.2-0_v7.img
Pls try the following command in TWRP terminal .. "twrp decrypt yourpassword"
Thanks
followmsi said:
Maybe another test ?
TWRP_dragon_3.0.2-0_v7.img
Pls try the following command in TWRP terminal .. "twrp decrypt yourpassword"
Thanks
Click to expand...
Click to collapse
Failed to decrypt data.
Testing of v7:
TWRP brings up the decrypt screen on booting, asking for a password to be entered.
Unfortunately I get a "Password Failed, please try again!" on entering my password (4 digit PIN)
"Failed to decrypt data " error when attempting via command line.
This appears to be closer than the previous boots, it recognizes the encrypted partition. I will try again with a password rather than pin
Still having the bootloops when booting into TWRP forum.xda-developers.com/pixel-c/help/twrp-bootloops-t3389438
Thanks for testing .. Seen somewhere you may need to enter password twice.. Just as test, try stock kernel for bootloop issue. Thanks
followmsi said:
Maybe another test ?
TWRP_dragon_3.0.2-0_v7.img
Pls try the following command in TWRP terminal .. "twrp decrypt yourpassword"
Thanks
Click to expand...
Click to collapse
twrp now asks for decryption password. But always returns "passwoord failed"
I tried it three ways with the same result "Failed to decrypt data":
At start of twrp
via mount and decrypt
Last version I think there was no decrypt button and there was a check box for data partition. This could not be checked.
Now there is the decrypt button but the data partion is missing. Klciking the button the result is as mentioned above.
via terminal
So we are getting further ...
RoFrie said:
twrp now asks for decryption password. But always returns "passwoord failed"
I tried it three ways with the same result "Failed to decrypt data":
At start of twrp
via mount and decrypt
Last version I think there was no decrypt button and there was a check box for data partition. This could not be checked.
Now there is the decrypt button but the data partion is missing. Klciking the button the result is as mentioned above.
via terminal
So we are getting further ...
Click to expand...
Click to collapse
Are you able to post the recovery.log of your steps ?
Maybe on pastebin.com ...
Thanks
followmsi said:
Are you able to post the recovery.log of your steps ?
Maybe on pastebin.com ...
Thanks
Click to expand...
Click to collapse
Thanks !
New version compiled today .. v8 ...
Code:
could not find any keystore module
Failed to init keymaster
Please mount /system partition before your start to decrypt via terminal ..
Is the recovery.log changing -> ... "could not open keymaster device in keystore .. "
Ot still "could not find kestore module" ?
Thanks for testing ..
NYChitman made also a new Version for encryption... pls test as well. .. http://forum.xda-developers.com/showthread.php?p=67138209
v10 is my last try on encryption .. makes a copy of the current dragon.keystore while starting up recovery.
This version has also a new kernel included and logcat for TWRP was compiled too.
And no bootloops while testing
Cheers
Still the usual loops on my device but only when I start from recovery. Strange thing. And it does not happen when stock recovery is installed. The funniest thing: If stock recovery is installed I can't open it if I want to. It's the red triangle droid. And if TWRP is flashed it opens if I don't want to Tried to flash the whole tablet back to start from scratch.At the moment impossible. Wiped, flashed, wiped and so on. I get the message (factory image): unable to truncate file... File too large failed to extract system.img I/o error. Installing from TWRP works fine. Tried to close and open bootloader: Not possible without stock recovery. Aaargh. I found out: There were some guys having this issue on Nexus devices who re-installed all drivers and software on their PC to solve the problem or used a different PC. That's my next step next Friday. I'm going to get everything on this stupid son of a... on this tablet working, I swear. Now, dear Pixel C, it's something personal Don't mess with an angry social worker!
GonzoKSV said:
Still the usual loops on my device but only when I start from recovery. Strange thing. And it does not happen when stock recovery is installed. The funniest thing: If stock recovery is installed I can't open it if I want to. It's the red triangle droid. And if TWRP is flashed it opens if I don't want to Tried to flash the whole tablet back to start from scratch.At the moment impossible. Wiped, flashed, wiped and so on. I get the message (factory image): unable to truncate file... File too large failed to extract system.img I/o error. Installing from TWRP works fine. Tried to close and open bootloader: Not possible without stock recovery. Aaargh. I found out: There were some guys having this issue on Nexus devices who re-installed all drivers and software on their PC to solve the problem or used a different PC. That's my next step next Friday. I'm going to get everything on this stupid son of a... on this tablet working, I swear. Now, dear Pixel C, it's something personal Don't mess with an angry social worker!
Click to expand...
Click to collapse
Did you found a solution ?
to "close/open" bootloader you need "full" stock !
Afterwards you can flash TWRP via fastboot again.
Maybe it solves your issue.
again one missing flag .. in fstab -> the very last try on encryption
Update.ZIP_TWRP_dragon_3.0.2-0_v11.zip
TWRP_dragon_3.0.2-0_v11.img
Cheers
Hi followfsi,
I tried your last build without encryption and it seems that in this build adbd doesn't accept the connexion anymore
"error: device unauthorized. Please check the confirmation dialog on your device."
That was working in the 6.0 build
Samt434 said:
Hi followfsi,
I tried your last build without encryption and it seems that in this build adbd doesn't accept the connexion anymore
"error: device unauthorized. Please check the confirmation dialog on your device."
That was working in the 6.0 build
Click to expand...
Click to collapse
Thanks for the finding ... V12 arrived
Update.ZIP_TWRP_dragon_3.0.2-0_v12.zip
TWRP_dragon_3.0.2-0_v12.img
Pls check now .. should work again..
And decryption ?
Do you get a password prompt ?
Does it work ?
Cheers
I flashed the new*B336 update for EMUI 5 and when i got into it i saw that there were not any system apps, i checked why and it appeared i had to install another*full_data file or smth, is there any way i can do it now ???
Btw when i try to boot into TWRP it says Your device is booting now... and does nothing
The situation is now even worst, why can`t nobody help?
Please someone help. i really need my phone back and i can`t take it for repairs.
When i try to install stock rom of EMUI 4 the install says error code - 7
failed to mount /vendor (invalid argument)
failed to mount /product (invalid argument)
I have no OS installed and i cant use HiSuite to recover using fastboot.
dload mode says the app update package does not exist when there is a corrent update.app in the dload folder on my SD card
and*i also am sure i*used the right OEMinfo file ;(
please respond someone.
TRY flash SYSTEM.IMG BOOT.IMG RECOVERY. IMG & CUSTS.IMG via ADB
Abdulla7 said:
TRY flash SYSTEM.IMG BOOT.IMG RECOVERY. IMG & CUSTS.IMG via ADB
Click to expand...
Click to collapse
Okay, i will try and see what happens and report back to you. Thanks for the response
Edit: When i try to use ADB to flash*the files to my device it says that the device is unauthorized
theAuxify said:
Edit: When i try to use ADB to flash*the files to my device it says that the device is unauthorized
Click to expand...
Click to collapse
Bootloader still unlocked?
If not, unlock it again with your code via fastboot.
Schlengge said:
Bootloader still unlocked?
If not, unlock it again with your code via fastboot.
Click to expand...
Click to collapse
Yea, the bootloader should be unlocked, when i boot up the device it says that it has been unlocked ;P
theAuxify said:
Yea, the bootloader should be unlocked, when i boot up the device it says that it has been unlocked ;P
Click to expand...
Click to collapse
Does it say "Unlocked" in bootloader mode?
On this screen I mean: Link
Schlengge said:
Does it say "Unlocked" in bootloader mode?
On this screen I mean: Link
Click to expand...
Click to collapse
Yea, says :
Phone unlocked
FRP Unlock
And if i use the command adb devices in fastboot mode no devices appear at all*D:
EDIT : I managed to flash boot.img and recovery.img without errors with the device not showing on the list of devices.
Says everything is okay
But when i try to flash system.img it shows this
C:\Users\Auxify\Desktop\Huawei\Huawei-P9-Lite>fastboot flash system system.img
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (445202 KB)...
OKAY [ 14.775s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 14.828s
It sounds like your SD card is not working because of reasons...
Try flashing TWRP from this thread (http://forum.xda-developers.com/huawei-p9lite/how-to/guide-unlock-bootloader-twrp-root-t3405701) with fastboot. Take the recovery image out of the extracted SRKTool Huawei.
Name should be twrpp9mm.img
Report back if you are able to access recovery again. From there you should be able to recover.
Afaik it is not possible to just reflash EMUI 4 after having updated to the Beta of EMUI 5. Once you have a recovery going, try to follow the exact steps of downgrading that are here on the forums.
Schlengge said:
It sounds like your SD card is not working because of reasons...
Try flashing TWRP from this thread (http://forum.xda-developers.com/huawei-p9lite/how-to/guide-unlock-bootloader-twrp-root-t3405701) with fastboot. Take the recovery image out of the extracted SRKTool Huawei.
Name should be twrpp9mm.img
Report back if you are able to access recovery again. From there you should be able to recover.
Afaik it is not possible to just reflash EMUI 4 after having updated to the Beta of EMUI 5. Once you have a recovery going, try to follow the exact steps of downgrading that are here on the forums.
Click to expand...
Click to collapse
After installing this recovery the phone is stuck at Your device is booting now... screen when entering recovery mode D:
So no recovery is working?
Have you tried flashing Meticulus TWRP or the Nougat Revolution Recovery?
One of these has to work... It also helps you to find out where your phone is stuck. If only Nougat Recovery works, your rollback from N has not worked. That would explain why you cannot launch any Marshmellow based recoveries.
Schlengge said:
So no recovery is working?
Have you tried flashing Meticulus TWRP or the Nougat Revolution Recovery?
One of these has to work... It also helps you to find out where your phone is stuck. If only Nougat Recovery works, your rollback from N has not worked. That would explain why you cannot launch any Marshmellow based recoveries.
Click to expand...
Click to collapse
Yeah.*I can boot into recovery N B9 but when i try to flash/wipe/do anything it says cant mount /vendor /product /version
Hmm okay that's a problem...
I don't really see what to do next honestly. Somehow we need to get fastboot flash working.
Have you tried to get back to a working Nougat build?
So flash BadWolf's Revolution N ROM in TWRP or via fastboot (since TWRP does not seem to work).
Schlengge said:
Hmm okay that's a problem...
I don't really see what to do next honestly. Somehow we need to get fastboot flash working.
Have you tried to get back to a working Nougat build?
So flash BadWolf's Revolution N ROM in TWRP or via fastboot (since TWRP does not seem to work).
Click to expand...
Click to collapse
Can`t do anything,*even wipe.
After wipe says : Successful but in the log view it says
"Updating partition details...
Failed to mount '/product' (Invalid argument)
Failed to mount '/version'*(invalid argument)
Failed to mount '/vendor' (invalid argument)
...Done"
theAuxify said:
Can`t do anything,*even wipe.
After wipe says : Successful but in the log view it says
"Updating partition details...
Failed to mount '/product' (Invalid argument)
Failed to mount '/version'*(invalid argument)
Failed to mount '/vendor' (invalid argument)
...Done"
Click to expand...
Click to collapse
Have you tried this:
https://www.youtube.com/watch?v=VJRKuQf0puE
Schlengge said:
Have you tried this:
https://www.youtube.com/watch?v=VJRKuQf0puE
Click to expand...
Click to collapse
Yea, but thats not for /vendor /product /version*xD
P.s : Happy 2017 ;P
Hmm sorry but I ran out of ideas... Maybe somebody else can help you further. All the standard procedures are not working so without fully knowing what you did and not having your phone to test it is hard to say something.
Hope you will find a way to fix this.
Schlengge said:
Hmm sorry but I ran out of ideas... Maybe somebody else can help you further. All the standard procedures are not working so without fully knowing what you did and not having your phone to test it is hard to say something.
Hope you will find a way to fix this.
Click to expand...
Click to collapse
Meh, i guess ill just drive out and get it fixed xD Its a loooong way though DD
Thanks for all your help brother ;p
theAuxify said:
After installing this recovery the phone is stuck at Your device is booting now... screen when entering recovery mode D:
Click to expand...
Click to collapse
Hey try to download revolution recovery for nougat and flash it using fastboot it will work for recovery
But zip installation will fail due to ( faail to mount vendor, product and version), if anyone knows how ho fix this please help
jkmaziku said:
Hey try to download revolution recovery for nougat and flash it using fastboot it will work for recovery
But zip installation will fail due to ( faail to mount vendor, product and version), if anyone knows how ho fix this please help
Click to expand...
Click to collapse
The best, is to try to install twrpmeticulus, wipe all except external storage property, install oeminfo.zip badwolf, go back to reboot, shut down.
Restarts Dload bxxx.
I only see her.
Hi,
My ZE550KL was locked in boot with this message: "Security Error: This phone has been flashed with an unauthorized software & is locked", so i followed some tutorials and was able to install TWRP recovery (i had bootloader already unlocked). Then when trying to reinstall stock rom, i realized i had to reinstall the stock recovery. I did it and installed the stock rom with version matching with the stock recovery i installed(UL-Z00L-WW-1.17.40.1531-user). Everything was going ok, but when my newly installed stock rom was popping multiple apps stopped working an i was unable to basically do anything. So i tried reinstalling stock rom again, but this is when things collapsed. As i entered recovery to reinstall the rom, it has lots of errors from partition cache
Code:
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
. This same errors happens when i try to wipe it from the recovery, but when i erase the cache partition on fastboot it says "OK". I also tried to reinstall twrp, but apparently my bootloader was blocked again, and it says it is flashed when i try, but when rebooting it boots again on stock recovery.
So i tried just booting twrp, but then it says my bootloader is blocked and can't boot twrp. Also tried sideloading stock rom from adb, but it gets the same cache partition errors. I tried
Code:
fastboot -w
and it says OK but the cache partition errors are still there. I also tried
Code:
fastboot erase ASDF
and i get some errors.
TLDR; I'm stuck at a cycle where i have to remount cache and all other partitions via TWRP, but i can't install TWRP because my bootloader got locked again and i can't unlock it because i need to install some rom to do it, but since my cache partition is destroyed i can't install anything, neither via fastboot on pc nor from recovery on the phone.
Did you tried the unoffical unlock way? It can done via PC in fastboot mode. Also did you tried `fastboot format system` kind of commands?
TheImpulson said:
Did you tried the unoffical unlock way? It can done via PC in fastboot mode. Also did you tried `fastboot format system` kind of commands?
Click to expand...
Click to collapse
I didn't. Can you please explain how to do it? Thanks
VMokaccino said:
I didn't. Can you please explain how to do it? Thanks
Click to expand...
Click to collapse
Damn! I just noticed that you will need to be in system to gain root access. I guess then it won't work. I suggest to try `fastboot format system/userdata/cache` way as it fixed my issues with partitions multiple times.
Here you go for unoffical guide: https://forum.xda-developers.com/ze...de-unlock-bootloader-asus-unlock-app-t3405850
TheImpulson said:
Damn! I just noticed that you will need to be in system to gain root access. I guess then it won't work. I suggest to try `fastboot format system/userdata/cache` way as it fixed my issues with partitions multiple times.
Here you go for unoffical guide: https://forum.xda-developers.com/ze...de-unlock-bootloader-asus-unlock-app-t3405850
Click to expand...
Click to collapse
Well, i tried all these format commands, but nothing has changed
VMokaccino said:
Well, i tried all these format commands, but nothing has changed
Click to expand...
Click to collapse
Did you tried what this guide says: https://www.asus.com/zentalk/thread-116230-1-1.html
TheImpulson said:
Did you tried what this guide says: https://www.asus.com/zentalk/thread-116230-1-1.html
Click to expand...
Click to collapse
I tried this, but my phone is now stuck on Fastboot Mode. It doesn't matter if i press VOL + or VOL -, it always enters in Fastboot Mode
VMokaccino said:
I tried this, but my phone is now stuck on Fastboot Mode. It doesn't matter if i press VOL + or VOL -, it always enters in Fastboot Mode
Click to expand...
Click to collapse
It's because you don't have any recovery or ROM on your device. Try flashing stock recovery.
TheImpulson said:
Did you tried what this guide says: https://www.asus.com/zentalk/thread-116230-1-1.html
Click to expand...
Click to collapse
TheImpulson said:
It's because you don't have any recovery or ROM on your device. Try flashing stock recovery.
Click to expand...
Click to collapse
Well, i tried flashing all stock recovery versions i could find, but none of them worked. I guess my phone is dead.
VMokaccino said:
Well, i tried flashing all stock recovery versions i could find, but none of them worked. I guess my phone is dead.
Click to expand...
Click to collapse
Take your phone to service center I guess.
how to fix it, please, my nook ver 1.1, and i not back up, please help me
Dear Members!
I did the stupid thing of using a tool, not completly knowing what it does.
After using TouchEraser.zip I installed Alpha-FormatTouch-2.zip using clockwork.
I tried to boot the device, no luck...
Clockwork says:
can't mount /cache/recovery/log/log
can't open /cache/recovery/log/log
can't mount /cache/recovery/log/last_log
can't open /cache/recovery/log/last_log
Please help!
pls help
help
Sorry, I don't know what an Eraser is or why you'd use it.
Maybe you killed some partitions or partitioning.
The problem with /cache may be a red herring because normally? it's not the most critical thing.
Did you have ADB working before? What happens when you boot normally? Do you have ADB? Do you have ADB working in CWR?
What is mounted?
Code:
# mount