Related
I am using clockwork for my recovery and I have been getting an error while in recovery "can't mount SD". The problem is, when this happens I can not flash a rom, update Gapps, cant flash a nand back-up etc.. When this happens I will reboot my phone and sometimes after several hours many attempts I will try and it will work.
I have upgraded recovery I have downgraded recovery and still getting the same issue. My last thought is to go back to stock and start over. Any one know why I am getting this?
jdh10475 said:
I am using clockwork for my recovery and I have been getting an error while in recovery "can't mount SD". The problem is, when this happens I can not flash a rom, update Gapps, cant flash a nand back-up etc.. When this happens I will reboot my phone and sometimes after several hours many attempts I will try and it will work.
I have upgraded recovery I have downgraded recovery and still getting the same issue. My last thought is to go back to stock and start over. Any one know why I am getting this?
Click to expand...
Click to collapse
Flash via 'fastboot flash recovery recoveryname.img'
Have you tried twrp http://forum.xda-developers.com/showthread.php?t=2507851
or philz http://forum.xda-developers.com/showthread.php?t=2565174
GUGUITOMTG4 said:
Flash via 'fastboot flash recovery recoveryname.img'
Have you tried twrp http://forum.xda-developers.com/showthread.php?t=2507851
or philz http://forum.xda-developers.com/showthread.php?t=2565174
Click to expand...
Click to collapse
I tried to flash recovery with fastboot all went well but I wasn't able to access sd again. I ended up going stock with factory image and all is good now. Thanks for the heads-up on philz recovery I really like it.
Actually it might be a little more complicated...
Full story: I was trying to flash cyanogenmod so I unlocked the bootloader and flashed cwm and SuperSU. Until this point everything worked just fine. I copied the CM-zip to the root of my phone. When trying to install CM however I got an error saying "Some changes failed" (Status 7), basically this. Also I started having trouble booting the system normally. The phone would either get stuck at the bootloader unlocked screen or just boot into recovery. I had done a backup at some point (not prior to starting to try to flash CM, I didn't really think I'd need one since the phone was brand new and I didn't there was any data on it I'd miss... yeah, well...) and sometimes restoring it would enable me to boot normally. However, after the factory reset before my nth attempt to install CM, that was gone as well. After doing a bit of research I found this thread. Since I had version 6.0.13 of cwm as well, I flashed twrp v2.7.1.2 instead. The interface is a little friendlier, but other than that there have been no changes.
Now I can't boot the system normally, not even by selecting "System" when rebooting it from recovery, it will just keep booting into recovery. I can still fastboot, though. My CM-zip is gone since that infamous factory reset and I can't get it back on the phone, or anything else for that matter, since my pc only detects the phone when it's booted normally. I tried pushing CM with adb but when I try to mount any partition I get an error saying E: Unable to find storage partition to mount to USB.
Any ideas how I could fix this mess? Or suggestions on how to avoid ****ing it up any further...
If you can adb, you can adb push... You are just adb push'ing to the wrong place I suppose.
Code:
adb push blah.zip /sdcard/
Should work...
Or even better, just sideload (put phone in recovery & 'sideload mode' before running):
Code:
adb sideload blah.zip
Either way, CWM for our device is ancient and does not support the latest ROM's. The version of TWRP should work fine, as should the latest OpenRecovery (2.09 IIRC).
Sideload worked perfectly! Thank you so much!
cm11 working only TWRP here , with cwm appears same error
mmichaelalves said:
cm11 working only TWRP here , with cwm appears same error
Click to expand...
Click to collapse
Did you not read my post?
arrrghhh said:
Either way, CWM for our device is ancient and does not support the latest ROM's. The version of TWRP should work fine, as should the latest OpenRecovery (2.09 IIRC).
Click to expand...
Click to collapse
I unlocked the bootloader through mi unlock tool. I flashed official twrp from their site, 3.3.1-0-violet.img but when I tried booting it into recovery, it got stuck at twrp logo. Then I learnt that it's necessary to wipe userdata using fastboot first so I did that. Then, when twrp started, it was unable to install/wipe/mount any partition. Tried installing magisk using sideload, did work but then device stopped booting.
Figured out a way on how to fix the mount issue, twrp working fine, but then I accidentally wiped /system. Now my device only opens in fastboot, even though I've tried installing, erasing and reinstalling that twrp recovery as well as a couple of others I found in pixel experience forums for my device.
I've got all the stuff needed to install pixel experience, fcrypto disabler, xiaomi latest firmware and the rom itself. Can anyone guide me on how to install it using fastboot?
Also whenever I try booting the recovery image straight from fastboot, it says that command failed, too many links.
I can't boot into recovery via vol up + power button, fastboot doesn't recognize command fastboot reboot recovery.
you need to install stock rom ,then flash twrp but newer unofficial twrp and orangefox twrp boots into recovery even if system partition is empty.
try installing unofficial twrp or orangefox.
orangefox is recommended .
Hey all!
I've been trying to install TWRP on my google pixel (32 GB/ 4GB). It runs Android 10, has an encrypted filesystem and the boot loader is unlocked. I booted into fastboot mode, then used fastboot boot twrp.img to boot into TWRP and it worked perfectly fine. Then, after decrypting, I tried flashing the TWRP zip I had on my phone. But it failed to do so, giving these errors - Failed to mount /system_root (invalid argument); Failed to mount /vendor (invalid argument). When I checked the mounted partitions in TWRP, system and vendor were unchecked and I couldn't check them.
Next, I tried to use fastboot flash recovery to flash the TWRP image directly from fastboot but this didn't work either.
Finally, I tried to flash a TWRP image after booting to TWRP. I chose the install to recovery ramdisk option but it didn't install, giving me the same failed to mount errors.
So right now I'm stuck at this point. Any help will be really appreciated
Thanks
-Keith
keith-james said:
Hey all!
I've been trying to install TWRP on my google pixel (32 GB/ 4GB). It runs Android 10, has an encrypted filesystem and the boot loader is unlocked. I booted into fastboot mode, then used fastboot boot twrp.img to boot into TWRP and it worked perfectly fine. Then, after decrypting, I tried flashing the TWRP zip I had on my phone. But it failed to do so, giving these errors - Failed to mount /system_root (invalid argument); Failed to mount /vendor (invalid argument). When I checked the mounted partitions in TWRP, system and vendor were unchecked and I couldn't check them.
Next, I tried to use fastboot flash recovery to flash the TWRP image directly from fastboot but this didn't work either.
Finally, I tried to flash a TWRP image after booting to TWRP. I chose the install to recovery ramdisk option but it didn't install, giving me the same failed to mount errors.
So right now I'm stuck at this point. Any help will be really appreciated
Thanks
-Keith
Click to expand...
Click to collapse
You should indicate which image you are booting and flashing. There are several and from what I gather, not all are compatible with 10.
Tulsadiver said:
You should indicate which image you are booting and flashing. There are several and from what I gather, not all are compatible with 10.
Click to expand...
Click to collapse
Hello! Thank you so much for the reply. I was flashing and booting twrp 3.5.1_9-0 for sailfish.
keith-james said:
Hello! Thank you so much for the reply. I was flashing and booting twrp 3.5.1_9-0 for sailfish.
Click to expand...
Click to collapse
Try 3.3.0 instead (for both). The last I can find on my records that I used is 3.1.0.
Edit:
fastboot boot image
Flash twrp zip
Flash magisk zip
Reboot
Should be rooted with twrp installed.
This is how it used to work at least.
Okay I will try that out thank you!
Tulsadiver said:
Try 3.3.0 instead (for both). The last I can find on my records that I used is 3.1.0.
Edit:
fastboot boot image
Flash twrp zip
Flash magisk zip
Reboot
Should be rooted with twrp installed.
This is how it used to work at least.
Click to expand...
Click to collapse
Hey! I tried what you said, booted into twrp using fastboot. But when I entered my password to decrypt data it says "password failed, please try again". This did not happen when I used the other img.
keith-james said:
Hey! I tried what you said, booted into twrp using fastboot. But when I entered my password to decrypt data it says "password failed, please try again". This did not happen when I used the other img.
Click to expand...
Click to collapse
I read through the twrp thread. I don't think they ever got deception working on 10. Not by installing, just booting.
Tulsadiver said:
I read through the twrp thread. I don't think they ever got deception working on 10. Not by installing, just booting.
Click to expand...
Click to collapse
So should I install the img via fastboot?
keith-james said:
So should I install the img via fastboot?
Click to expand...
Click to collapse
I don't think you can on Android 10. You can try but I think people just booted twrp when they wanted to use it.
I think I'm having the same problem or at least a very similar one, I get the same errors in TWRP (started with ""fastboot boot twrp.img") saying unable to mount /system_root and /vendor but i am still told installation was successful anyway. Unfortunately, when I reboot to recovery, it seems to try and start TWRP but the phone restarts after the google boot logo and this will happen every time.
You can get the older verson of (temporary) TWRP Tulsadiver suggested using past the decrypting stage simply by removing your password/pin in settings > security > screen lock but using this version didn't help me at all.
I have tried going back to an earlier stock rom using google's images and trying to install TWRP again but this didn't work either.
Please let me know if you get anywhere with this.
I also have the same problem. It just saying unable to mount /system_root (Invalid argument)
And the /system is read-only,
I need to modify the files on /system partition, what should I do?
I've tried 3.4.0.0 and 3.3.0.0 and 3.6.9.0-9-0 but all failed.
Thank you all!
the-blind-bandit said:
I think I'm having the same problem or at least a very similar one, I get the same errors in TWRP (started with ""fastboot boot twrp.img") saying unable to mount /system_root and /vendor but i am still told installation was successful anyway. Unfortunately, when I reboot to recovery, it seems to try and start TWRP but the phone restarts after the google boot logo and this will happen every time.
You can get the older verson of (temporary) TWRP Tulsadiver suggested using past the decrypting stage simply by removing your password/pin in settings > security > screen lock but using this version didn't help me at all.
I have tried going back to an earlier stock rom using google's images and trying to install TWRP again but this didn't work either.
Please let me know if you get anywhere with this.
Click to expand...
Click to collapse
I have this problem too. Pixel sailfish on Android 10, tried to install TWRP zip file using the TWRP temp boot, and it will say unable to mount system_root and vendor but still successful, but unable to boot to recovery (restarts after Google boot logo).
Any idea how to install TWRP on Pixel with Android 10?
I have a Redmi note 8 with MIUI 12 installed. Bootloader is unlocked and the phone is rooted.
When I try to flash TWRP recovery in fastboot mode using my PC, it successfully flashes and boots into the TWRP recovery. TWRP does not ask for any password for decrypting the files, and when I go to install>sdcard then the storage is all in random letters, completely unrecognizable.
I have tried a lot of tutorials on youtube but none of them worked. I tried flashing the latest version of TWRP, didn't work. I tried formatting all data and rebooting back into recovery mode, didn't work. (if you reboot to system after installing TWRP, the phone automatically deletes TWRP and the next time you open recovery mode you just get the default MI recovery, and you have to flash TWRP again to open TWRP recovery.) I tried almost everything on the internet but none of it worked. Is there any way I can make it ask for the decryption password? or have my files decrypted? I just need the TWRP for a one-time-use to install a custom ROM. I don't need it to be installed permanently, but no problem even if it does get installed permanently. I just want my custom ROM.
Please help
does that work?:
Boot into twrp, then
Code:
adb shell
twrp decrypt myPassword
(myPassword is your user password)
User699 said:
does that work?:
Boot into twrp, then
Code:
adb shell
twrp decrypt myPassword
(myPassword is your user password)
Click to expand...
Click to collapse
It didnt work, "failed to decrypt data" i typed the right password
#JKTheBaskieBoy said:
It didnt work, "failed to decrypt data" i typed the right password
Click to expand...
Click to collapse
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.
the correct and recommend way to install TWRP is
Flash TWRP
Erase userdata partition <~ it's important to do this as soon as possible since booting your device would just encrypt everything again
Format userdata partition
by doing this you would be able to access data partition files and folder would not be random letters.
User699 said:
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.
Click to expand...
Click to collapse
Sorry for the late reply. Earlier i just gave up on installing the custom ROM and continued with my stock from. Today a tried again, installed TWRP and turns out it is not showing random letters now. its all regular storage. i didn't even do anything to decrypt it lol it just fixed itself. Now I will install the room myself. Thank you for your help though
Ah sh** here we go again. So i installed the custom rom successfully and everything worked fine, the TWRP too. but when I tried to flash a magisk patched image (the image that I used to root my phone in MIUI) then it got stuck in the boot screen. I had to flash the stock fastboot rom again.. And as expected from my piece of **** that xiaomi calls a phone, TWRP will show encrypted folders, and does not ask for a password. Same problem. Rooted my phone again, using the magisk root image, and it worked like usual, the phone rooted. Now i am stuck again in this bs. I guess I will wait for about 4-5 days and continue using the phone like normal. Maybe it will work again this time. I will try your method here first
User699 said:
Okay, interessting. What's the exact error?
However, since you only want to use twrp to flash a custom OS, you could try to boot twrp (without flashing)
Code:
fastboot boot twrp.img
and then wipe data via twrp and then install your custom OS. You can use sideload which should be located under "advanced" I guess.
Code:
adb sideload myCustomOS.zip
EDIT: Don't boot out of twrp before sideloading, since your os should encrypt everything again after wiping which makes it unpossible for twrp to decrypt again (at least in your case, since it failed for some reason).
If you booted out of twrp, just wipe again and then sideload.
Click to expand...
Click to collapse
Okay i tried wiping the data, cache and dalvik but it shows a huge essay of "error opening xxx/xxxx" in red text. Data wipe failed.
See you after like 4-5 days... hopefully
Update. I finally found a solution. It took literal hours of experimenting to find this.
-Flashed the fastboot ROM of the phone
-Rooted the phone by flashing magisk patched image
-Flashed Inception kernel via FK kernel manager
-Rebooting after flashing the kernel, It will get stuck in a black screen with no text whatsoever (probably a bootloop)
-Installed TWRP (This time TWRP does not show encrypted letters), Wiped all data, Transferred the custom ROM zip to the phone (while in TWRP) and flashing the rom
-The rom is flashed successfully. On the first reboot you get greeted with another bootloop. Fortunately the phone booted into TWRP. This time the folders are encrypted again.
-Successfully wiped the data (advanced>wipe data). No errors in data wiping this time.
-A fully working Corvus OS setup appears on rebooting.
I think the whole TWRP problem was fixed by the custom kernel. Anyways I am finally done with this now. You probably enjoyed seeing all this xD
#JKTheBaskieBoy said:
Update. I finally found a solution. It took literal hours of experimenting to find this.
-Flashed the fastboot ROM of the phone
-Rooted the phone by flashing magisk patched image
-Flashed Inception kernel via FK kernel manager
-Rebooting after flashing the kernel, It will get stuck in a black screen with no text whatsoever (probably a bootloop)
-Installed TWRP (This time TWRP does not show encrypted letters), Wiped all data, Transferred the custom ROM zip to the phone (while in TWRP) and flashing the rom
-The rom is flashed successfully. On the first reboot you get greeted with another bootloop. Fortunately the phone booted into TWRP. This time the folders are encrypted again.
-Successfully wiped the data (advanced>wipe data). No errors in data wiping this time.
-A fully working Corvus OS setup appears on rebooting.
I think the whole TWRP problem was fixed by the custom kernel. Anyways I am finally done with this now. You probably enjoyed seeing all this xD
Click to expand...
Click to collapse
I like that you keep trying and finding a solution, even though you had to invest hours to make it work!
Let's hope it will work if you update the OS though – I'd actually suggest a backup of all of your data before you do an update in the future, just to be safe!
#JKTheBaskieBoy said:
I have a Redmi note 8 with MIUI 12 installed. Bootloader is unlocked and the phone is rooted.
When I try to flash TWRP recovery in fastboot mode using my PC, it successfully flashes and boots into the TWRP recovery. TWRP does not ask for any password for decrypting the files, and when I go to install>sdcard then the storage is all in random letters, completely unrecognizable.
I have tried a lot of tutorials on youtube but none of them worked. I tried flashing the latest version of TWRP, didn't work. I tried formatting all data and rebooting back into recovery mode, didn't work. (if you reboot to system after installing TWRP, the phone automatically deletes TWRP and the next time you open recovery mode you just get the default MI recovery, and you have to flash TWRP again to open TWRP recovery.) I tried almost everything on the internet but none of it worked. Is there any way I can make it ask for the decryption password? or have my files decrypted? I just need the TWRP for a one-time-use to install a custom ROM. I don't need it to be installed permanently, but no problem even if it does get installed permanently. I just want my custom ROM.
Please help
Click to expand...
Click to collapse
tell me how to turn off a smartphone with a non-working sensor?
you can still use adb push command from pc to transfer files to your phone :
adb push "nameoffile" /sdcard
(place the file in your adb folder) I was able to root a phone that had this issue using this technique.
I think u should flash dm verity becoz when i flashed the rom and flashed dm verity it worked fine