Related
Hi,
I can't install the A3 recovery, getting the error when I try to enter it or system boots.
boot recovery via fastboot was fine, that way I installed A3.
system seems to be OK, more later...
Any hints how to fix?
Miraculix666 said:
Hi,
I can't install the A3 recovery, getting the error when I try to enter it or system boots.
boot recovery via fastboot was fine, that way I installed A3.
system seems to be OK, more later...
Any hints how to fix?
Click to expand...
Click to collapse
Just flash once more recovery.img. I have the same bug but it's was my fault copy&paste with wrong file name.
After I installed EnergyRom I have been having issues with TWRP (not blaming EnergyRom). I was trying to make a backup and I kept getting an error stating my SDcard did not have enough space (tried both internal and external, both had plenty of space). I tried another SD card, even reformatted it, but to no avail.
I then upgraded TWRP 2.2 to 2.4 and then TWRP got really funky. It no longer recognizes or lists any files, keep getting unable to mount errors, and will not let me reboot, giving an error message 'No OS found'. But when I manually reboot everything seems to work just fine.
Just updated to 2.5 and same exact issue(s). It also wont let me save the log file, so I am writing here:
E: Unable to find partition size for '/misc'
E: Unable to find partition size for '/staging'
E: Unable to find partition size for '/data'
E: Unable to find partition size for '/boot''
E: Unable to find partition size for '/recovery'
Updating partition details...
E: Unable to mount '/system'
E: Unable to mount '/cache'
E: Unable to mount '/cache'
E:TNFunc::Copy_Log -- Can't open destination log file: '/cache/recovery/log'
E: Unable to set emmc bootloader message.
E: Unable to mount '/cache'
Updating partition details...
E: Unable to mount '/system'
E: Unable to mount '/cache'
Any help would be greatly appreciated.
SS823 said:
After I installed EnergyRom I have been having issues with TWRP (not blaming EnergyRom). I was trying to make a backup and I kept getting an error stating my SDcard did not have enough space (tried both internal and external, both had plenty of space). I tried another SD card, even reformatted it, but to no avail.
I then upgraded TWRP 2.2 to 2.4 and then TWRP got really funky. It no longer recognizes or lists any files, keep getting unable to mount errors, and will not let me reboot, giving an error message 'No OS found'. But when I manually reboot everything seems to work just fine.
Just updated to 2.5 and same exact issue(s). It also wont let me save the log file, so I am writing here:
E: Unable to find partition size for '/misc'
E: Unable to find partition size for '/staging'
E: Unable to find partition size for '/data'
E: Unable to find partition size for '/boot''
E: Unable to find partition size for '/recovery'
Updating partition details...
E: Unable to mount '/system'
E: Unable to mount '/cache'
E: Unable to mount '/cache'
E:TNFunc::Copy_Log -- Can't open destination log file: '/cache/recovery/log'
E: Unable to set emmc bootloader message.
E: Unable to mount '/cache'
Updating partition details...
E: Unable to mount '/system'
E: Unable to mount '/cache'
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Please tell me you didn't flash a normal twrp on the new 4.2.1 bootloader.
It would appear that you're recovery isn't compatible with your bootloader, or device all together. It also may be worth asking how you arrived at your new rom -
1. Initial steps, flashing recovery, etc
2. Clearing caches, factory resets, wiping x3, etc
3. Flash new rom, reboot let settle.
If you've just moved to the custom rom, and the recovery was working fine prior to the new rom, list what you were coming from and going to, maybe I can help. I'm not intimately familiar with the Eee Pad but hopefully we can figure this out.
milestoneiii said:
It would appear that you're recovery isn't compatible with your bootloader, or device all together. It also may be worth asking how you arrived at your new rom -
1. Initial steps, flashing recovery, etc
2. Clearing caches, factory resets, wiping x3, etc
3. Flash new rom, reboot let settle.
If you've just moved to the custom rom, and the recovery was working fine prior to the new rom, list what you were coming from and going to, maybe I can help. I'm not intimately familiar with the Eee Pad but hopefully we can figure this out.
Click to expand...
Click to collapse
You don't need to figure it out mate.. I know exactly what he has done.
My post above wasn't really a question. That is what he has done.
JB TWRP
flumpster said:
You don't need to figure it out mate.. I know exactly what he has done.
My post above wasn't really a question. That is what he has done.
Click to expand...
Click to collapse
I upgraded the bootloader to 4.2 when I updated to Energy ROM. It was working just fine (the ROM is still working just fine), I was able to make a back-up. A few days later I wanted to flash another ROM, went to make a backup and then (see initial post). All the TWRP updates I did (2.4 and 2.5) are the JB blobs. When you say 'normal' bootloader what exactly do you mean, ICS?
SS823 said:
I upgraded the bootloader to 4.2 when I updated to Energy ROM. It was working just fine (the ROM is still working just fine), I was able to make a back-up. A few days later I wanted to flash another ROM, went to make a backup and then (see initial post). All the TWRP updates I did (2.4 and 2.5) are the JB blobs. When you say 'normal' bootloader what exactly do you mean, ICS?
Click to expand...
Click to collapse
When you had the first problem that would have been some silly problem. What came next is the problem.
Energy and Hairybeans new versions are using the 4.2.1 bootloader. The versions of TWRP for ICS and Jellybean are not compatible with the 4.2.1 bootloader and gives the error you describe where nothing can mount.
There are loads of people over on the TF300 forums who have done the same and bricked.
In the 4.2.1 upgrade zips that NRG and myself provide there is a custom version of TWRP included that will work on the new 4.2.1 bootloader.
On my thread (Hairybean) I have warnings all over the first post telling people not to install a "normal" version of TWRP onto the 4.2.1 bootloader and to use the downgrade zip if they want to go back to 4.1.1 bootloader and normal TWRP.
Have a read of my last few posts on here and see if any of the ways will fix you. http://forum.xda-developers.com/showthread.php?p=40141480#post40141480
I will probably have to supply you with the Modded TWRP for 4.2.1 in blob file format also. If you need it let me know.
Thanks Flumpster. I was careful to use the Energy update but obviously lacked some common sense when updating the TWRP. If you wouldn't mind passing the modded TWRP blob I'd appreciate it. Can I extract it from your hairybean update zip?
SS823 said:
Thanks Flumpster. I was careful to use the Energy update but obviously lacked some common sense when updating the TWRP. If you wouldn't mind passing the modded TWRP blob I'd appreciate it. Can I extract it from your hairybean update zip?
Click to expand...
Click to collapse
No because that blob file contains the bootloader, recovery and partition table all in one.
I will be at my computer in 20 mins and will upload it here.
---------- Post added at 07:21 PM ---------- Previous post was at 06:48 PM ----------
Here is the blob recovery file for 4.2.1 bootloader.
http://flumpster.lolcakes.com/android/twrp.blob
Either try going into fastboot mode and doing the following (on 4.2.1 you are straight in fastboot when you see the 3 icons). Make sure you have fastboot drivers installed from naked drivers thread.
fastboot -i 0x0b05 flash recovery twrp.blob
If this doesn't work and you don't get a blue line filling after the flash then try the following. Move the twrp.blob to the root of the internal sdcard on prime and then from terminal emulator in android.
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Then reboot normally (NOT to recovery) to complete installation.
Flumpster, thanks TWRP works fine and am backing up now. I still have the same issue of it saying I do not have enough room on my external, though I have over a gig of extra room, I am just going to save to the internal and then transfer it.
Any idea why it reads only part of my external?
Anyway, thanks again!
Wow Flumpster, I'm impressed with your helpfulness and willingness to lend your development skills! It's hard to find people willing to simply explain where someone goes wrong and provide them with the tools to correct it so efficiently. Hats off to you sir!
Sent from my SAMSUNG-SGH-I957 using Tapatalk 2
milestoneiii said:
Wow Flumpster, I'm impressed with your helpfulness and willingness to lend your development skills! It's hard to find people willing to simply explain where someone goes wrong and provide them with the tools to correct it so efficiently. Hats off to you sir!
Sent from my SAMSUNG-SGH-I957 using Tapatalk 2
Click to expand...
Click to collapse
Yeah, Flumpster, big thank you!
Cheers
SS823 said:
Yeah, Flumpster, big thank you!
Cheers
Click to expand...
Click to collapse
You're welcome mate.. Glad it's all sorted.
flumpster said:
No because that blob file contains the bootloader, recovery and partition table all in one.
I will be at my computer in 20 mins and will upload it here.
---------- Post added at 07:21 PM ---------- Previous post was at 06:48 PM ----------
Here is the blob recovery file for 4.2.1 bootloader.
http://flumpster.lolcakes.com/android/twrp.blob
Either try going into fastboot mode and doing the following (on 4.2.1 you are straight in fastboot when you see the 3 icons). Make sure you have fastboot drivers installed from naked drivers thread.
fastboot -i 0x0b05 flash recovery twrp.blob
If this doesn't work and you don't get a blue line filling after the flash then try the following. Move the twrp.blob to the root of the internal sdcard on prime and then from terminal emulator in android.
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Then reboot normally (NOT to recovery) to complete installation.
Click to expand...
Click to collapse
The 2nd solution works for me.... You are the man flumpster... !! :good::good:
Thank you
flumpster said:
No because that blob file contains the bootloader, recovery and partition table all in one.
I will be at my computer in 20 mins and will upload it here.
---------- Post added at 07:21 PM ---------- Previous post was at 06:48 PM ----------
Here is the blob recovery file for 4.2.1 bootloader.
http://flumpster.lolcakes.com/android/twrp.blob
Either try going into fastboot mode and doing the following (on 4.2.1 you are straight in fastboot when you see the 3 icons). Make sure you have fastboot drivers installed from naked drivers thread.
fastboot -i 0x0b05 flash recovery twrp.blob
If this doesn't work and you don't get a blue line filling after the flash then try the following. Move the twrp.blob to the root of the internal sdcard on prime and then from terminal emulator in android.
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Then reboot normally (NOT to recovery) to complete installation.
Click to expand...
Click to collapse
Thanks for this flumpster it saved my aaaaaaasssss! The 2nd method worked for me.
alfalvarez81 said:
Thanks for this flumpster it saved my aaaaaaasssss! The 2nd method worked for me.
Click to expand...
Click to collapse
Flumpster - YOU ARE THE MAN! Your first solution worked like a charm for me. I have been stumped as to how to fix this problem and now I am able to create a backup, root, and flash CM 10.1!
Cheers!
same issue, cant work around it
I did the same thing, installing a newer generic twrp and get the same password prompt. I have one more wrinkle though that fastboot isnt working normally. I get twrp 2.6 on every boot. I cant do anything with the partitions, it cant enumerate the partition size or it cant mount them. I can push things to tmp and it sees them, but it wont flash them successfully.
When i force it into fastboot, if i try to flash something, the command line appears like everything is ok, but the prime has hung at some point. Thats what happened when i tried method 1.
If i force it into fastboot and then load android, the system boots. I then tried the second method i get no errors and it looks like it all succeeded. After it tries to reboot, it dumps back into twrp.
I was thinking of trying rom manager to flash the recovery back, but havent used it before and i dont know if i can pick the recovery you've given out here.
anyone have a tip to help?
thanks
same issue, some progress (sorta)
I erased my recovery partition through fastboot and tried to flash the trwp.blob here to it. My prime hung. On reboot though it booted into android just fine, my fastboot was fine as well. I can get into fastboot through the normal process, but i have no recovery. when i try to load recovery i get a unrecoverable boot error.
So next is i am going to try to verify i have or have no recovery partition and then recreate it and try to flash twrp back into it.
help
I am having same problem with prime. Every time I reboot it goes to twrp. 2.6 asking for password, and does not recognize any internal memory or sd card. how ever I can use adb reboot-bootloader, and do a cold boot to Linux and everything works just fine..I would like clarification on your instructions on how to repair. I'm just a novice. Any help will be greatly appreciated.
carlkelly176 said:
I am having same problem with prime. Every time I reboot it goes to twrp. 2.6 asking for password, and does not recognize any internal memory or sd card. how ever I can use adb reboot-bootloader, and do a cold boot to Linux and everything works just fine..I would like clarification on your instructions on how to repair. I'm just a novice. Any help will be greatly appreciated.
Click to expand...
Click to collapse
I dont know that i've actually fixed anything or just traded one problem for another. I cannot get a recovery flashed onto my device. My system boots normally and fastboot works, but nothing ive come up with will flash a recovery.
On a brighter note, my system is faster, it hasnt bogged down and lagged like it always has. That may be just because of the wiping caches and such though.
What i did was erase my recovery partition from fastboot.I've recreated it, i can see it in root explorer. Its about 420mb in size, i dont know if that size is correct. The only things in it are a couple of log files.
my whole point in messing with this again was to try to flash the newest CM on it. bluetooth is a bit wonky on mine and i hoped a newer stack would help.
good luck. If i get a working recovery, i will post.
I've got the same issue here, except i have a TF300T. I've downloaded the right blob now (4.2 for the TF300)
the adb devices command shows my TF300T.
Im just wondering now, how do I transfer the file to the 'internal sd card' of the tablet and access it if all i can do is entering the twrp recovery?
thanks in advance.
EDIT: Found a way to delete the wrong recovery and now im able to access the fastboot mode ok. However, the tablet freezes everytime I use the flash command on fastboot...
flumpster said:
No because that blob file contains the bootloader, recovery and partition table all in one.
I will be at my computer in 20 mins and will upload it here.
---------- Post added at 07:21 PM ---------- Previous post was at 06:48 PM ----------
Here is the blob recovery file for 4.2.1 bootloader.
http://flumpster.lolcakes.com/android/twrp.blob
Either try going into fastboot mode and doing the following (on 4.2.1 you are straight in fastboot when you see the 3 icons). Make sure you have fastboot drivers installed from naked drivers thread.
fastboot -i 0x0b05 flash recovery twrp.blob
If this doesn't work and you don't get a blue line filling after the flash then try the following. Move the twrp.blob to the root of the internal sdcard on prime and then from terminal emulator in android.
su
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Then reboot normally (NOT to recovery) to complete installation.
Click to expand...
Click to collapse
Having problems flashing CWM to Moto G 4.4 i get"ERROR Max Download size of 536870912 cannot load"
Can anyone help? Thanks
Marcusprit said:
Having problems flashing CWM to Moto G 4.4 i get"ERROR Max Download size of 536870912 cannot load"
Can anyone help? Thanks
Click to expand...
Click to collapse
You're either just going to have to use "fastboot boot recovery.img" (without quotes and where recovery.img is whatever the CWM file is named) instead of "fastboot flash recovery.img" or you will have to find a recovery.img that is small enough to actually flash. If you just use the boot method, this means you will have to reflash it every time you need something done with CWM.
es0tericcha0s said:
You're either just going to have to use "fastboot boot recovery.img" (without quotes and where recovery.img is whatever the CWM file is named) instead of "fastboot flash recovery.img" or you will have to find a recovery.img that is small enough to actually flash. If you just use the boot method, this means you will have to reflash it every time you need something done with CWM.
Click to expand...
Click to collapse
Hi thank you for your reply. I used fastboot boot recovery CWM6046-MotoG44.img but it cannot load recovery. I did read somewhere about sparse chunks in the US being 123 and 012 in the UK whatever that means. Is there anything else i can try?
I have unlocked the bootloader and rooted my phone, i really wanted to try some custom roms but without CWM its not possible
PS I am in the UK.
Marcusprit said:
Hi thank you for your reply. I used fastboot boot recovery CWM6046-MotoG44.img but it cannot load recovery. I did read somewhere about sparse chunks in the US being 123 and 012 in the UK whatever that means. Is there anything else i can try?
I have unlocked the bootloader and rooted my phone, i really wanted to try some custom roms but without CWM its not possible
PS I am in the UK.
Click to expand...
Click to collapse
Looks like you'll need the more updated version of CWM - 6.0.4.7 as that is built with Kit Kat sources and works with both 4.3 and 4.4 bootloaders. Or you can use the new TWRP 2.7.0. You can find links from here: http://forum.xda-developers.com/showthread.php?t=2608377
Hope this helps!
es0tericcha0s said:
Looks like you'll need the more updated version of CWM - 6.0.4.7 as that is built with Kit Kat sources and works with both 4.3 and 4.4 bootloaders. Or you can use the new TWRP 2.7.0. You can find links from here: http://forum.xda-developers.com/showthread.php?t=2608377
Hope this helps!
Click to expand...
Click to collapse
Thank you tried the updated versions but still won't load. I'm not sure what i'm doing wrong. I type in ADB DEVICES thats working fine then FASTBOOT DEVICES thats working too then i type in the recovery image but i get" ERROR CANNOT LOAD"
When i download the recovery image do i need to burn it onto a disk? I tried doing this but it says Disk image isn't valid.
Doesn't look like i'm going to be able to solve this problem.
Marcusprit said:
Thank you tried the updated versions but still won't load. I'm not sure what i'm doing wrong. I type in ADB DEVICES thats working fine then FASTBOOT DEVICES thats working too then i type in the recovery image but i get" ERROR CANNOT LOAD"
When i download the recovery image do i need to burn it onto a disk? I tried doing this but it says Disk image isn't valid.
Doesn't look like i'm going to be able to solve this problem.
Click to expand...
Click to collapse
Your device boots and is already rooted, right? If so, try to flash the updated img files with : https://play.google.com/store/apps/details?id=com.cgollner.flashify
recovery
Thank you I now have recovery
Marcusprit said:
Thank you I now have recovery
Click to expand...
Click to collapse
Hey guys. I'm a newbie and need help as fast as possible. Thanks in advance..
So my problem initially was that since rooting my OnePlus X, I couldn't flash the new OTA patch. Error showing up was "error executing binary".
Kéno40 replied on my post here http://forum.xda-developers.com/one...2-0-coming-t3300825/post65214913#post65214913 to reinstall recovery. I got the twrp image from the official site for my device and flashed it. Since then, its stuck in Bootloop. Everytime I try to reboot in any mode, it shows up TWRP.
What I have tried -
I've made a backup on my SD but when I tried to go back to a previous version of TWRP and came back to the new, it isn't showing up in recovery anymore. Though the file is still there in my SD card consuming 5GB space.
I tried this command - make_ext4fs /dev/block/mmcblk0p15 Didn't work.
I've tried wiping cache/dalvik-cache...seriously, I wiped my whole Internal by wiping /data. Didn't work. I even wiped /system losing the OS and then using the recovery to get it back...still no hope.
So..in short, I'm screwed. Badly. Need help asap.
Any suggestions are appreciated. Please don't ask me why I did what I did, just help me out if possible. Meanwhile I think I'll start downloading OOS 2.2.0 full ROM, just in case. But I hope I don't have to.
Edit : I flashed TWRP both in Boot and Recovery..is this happening because of that?
choubeyaakash77 said:
Hey guys. I'm a newbie and need help as fast as possible. Thanks in advance..
So my problem initially was that since rooting my OnePlus X, I couldn't flash the new OTA patch. Error showing up was "error executing binary".
Kéno40 replied on my post here http://forum.xda-developers.com/oneplus-x/general/oos-2-2-0-coming-t3300825/post65214913#post65214913 to reinstall recovery. I got the twrp image from the official site for my device and flashed it. Since then, its stuck in Bootloop. Everytime I try to reboot in any mode, it shows up TWRP.
What I have tried -
I've made a backup on my SD but when I tried to go back to a previous version of TWRP and came back to the new, it isn't showing up in recovery anymore. Though the file is still there in my SD card consuming 5GB space.
I tried this command - make_ext4fs /dev/block/mmcblk0p15 Didn't work.
I've tried wiping cache/dalvik-cache...seriously, I wiped my whole Internal by wiping /data. Didn't work. I even wiped /system losing the OS and then using the recovery to get it back...still no hope.
So..in short, I'm screwed. Badly. Need help asap.
Any suggestions are appreciated. Please don't ask me why I did what I did, just help me out if possible. Meanwhile I think I'll start downloading OOS 2.2.0 full ROM, just in case. But I hope I don't have to.
Edit : I flashed TWRP both in Boot and Recovery..is this happening because of that?
Click to expand...
Click to collapse
If you can enter in fastboot mode, flash the recovery from fastboot command. Flash blu_sparks recovery, it's better
seems you can still go to TWRP recovery? just flash the OOS 2.2.0 full ROM.
choubeyaakash77 said:
Edit : I flashed TWRP both in Boot and Recovery..is this happening because of that?
Click to expand...
Click to collapse
Obviously...
You told the phone to boot to TWRP by flashing it to 'Boot' and that's exactly what is happening.
Just reflash your ROM and you're good to go.
choubeyaakash77 said:
Kéno40 replied on my post here http://forum.xda-developers.com/one...2-0-coming-t3300825/post65214913#post65214913 to reinstall recovery. I got the twrp image from the official site for my device and flashed it. Since then, its stuck in Bootloop. Everytime I try to reboot in any mode, it shows up TWRP.
Click to expand...
Click to collapse
If you didn't know what you were doing, why ask before doing it?
You always have to flash the recovery .img from fastboot mode via adb. Not flashed by twrp.
Reference thread :
http://forum.xda-developers.com/oneplus-x/general/discussion-how-to-root-oneplus-x-t3242830
Maybe, just flash from adb the OLD recovery.
From this recovery, reinstall your Save.
Then install new recovery via ADB.
Or flash full ROM, then reflash, VIA ADB, the OLD recovery.
Then same as above. Restora + new recovery.
Boot your phone into fastboot mode, connect it to the PC, in adb directory, open cmd promote, type
fastboot flash recovery twrp. img
Click to expand...
Click to collapse
(replace twrp. img to the recovery img you downloaded, and put it under the adb directory). Or you can type
fastboot boot twrp.img
Click to expand...
Click to collapse
, the phone will then boot into the recovery you downloaded, where you can flash a new rom. DON'T flash recovery from recovery!
---------- Post added at 03:11 PM ---------- Previous post was at 03:00 PM ----------
And if you want restore the backup on th sdcard, you might need change the storage location to sdcard in TWRP recovery,
Thanks all you guys. I'm back on with OOS 2.2.0. Had to download the complete ROM and flash it through TWRP.
I didn't wanted to download a whole almost 1 GB zip, so I tried to search for the original OxygenOS boot.img to flash it to boot. It might have worked if I hadn't completely wiped out my OS by wiping /system. Plus its almost impossibe to find that file online...
Anyway, had a nice experience screwing things up and getting back up better than before. Had fun. Learned stuff...so probably I'm not a newbie to rooting anymore.
Thanks guys for your support.
Here's the ROM I downloaded (for future reference) : https://www.androidfilehost.com/?fid=24389512218017971
Boot into your recovery [Vol+ and Power]
Connect your phone to your PC
Execute the following fastboot command on your PC (More informations on fastboot)
Code:
fastboot continue
Your phone will start right away. :good:
FixFaier said:
Boot into your recovery [Vol+ and Power]
Connect your phone to your PC
Execute the following fastboot command on your PC (More informations on fastboot)
Code:
fastboot continue
Your phone will start right away. :good:
Click to expand...
Click to collapse
fking hell.
this helped me a lot.
thx man :good:
Thank you so much. For now just gonna be content witht the stock rom.
I'm using twrp-3.4.0-2-hotdog-unified-mauronofrio and flashed Resurrection (RROS-Q-8.6.6-20210119-hotdog-Official) on one of my slots. However, TWRP won't see anything (storage always showing 0) No prompt for the password if I set up the lockscreen.
The only workaround is to return the stock recovery, then select delete everything.
BUT, if I reboot the phone and pass the welcome screen, the TWRP won't be able to see anything again.
The same thing applies to the stock ROM, even if I didn't set up any screen lock passwords.
That's really frustrating. I don't even have a chance to flash the decryption zip.
How to address this issue? Thanks.
nabor said:
I'm using twrp-3.4.0-2-hotdog-unified-mauronofrio and flashed Resurrection (RROS-Q-8.6.6-20210119-hotdog-Official) on one of my slots. However, TWRP won't see anything (storage always showing 0) No prompt for the password if I set up the lockscreen.
The only workaround is to return the stock recovery, then select delete everything.
BUT, if I reboot the phone and pass the welcome screen, the TWRP won't be able to see anything again.
The same thing applies to the stock ROM, even if I didn't set up any screen lock passwords.
That's really frustrating. I don't even have a chance to flash the decryption zip.
How to address this issue? Thanks.
Click to expand...
Click to collapse
You have to flash twrp before and wipe data prior to installation
toolhas4degrees said:
You have to flash twrp before and wipe data prior to installation
Click to expand...
Click to collapse
when trying to make a Wipe --> Format Data in TWRP, I get the following errors
unable to mount storage
failed to mount'/system_root' (Permission denied)
failed to mount '/vendor' (Permission denied)
Any idea of what's going wrong?
arcadia2uk said:
when trying to make a Wipe --> Format Data in TWRP, I get the following errors
unable to mount storage
failed to mount'/system_root' (Permission denied)
failed to mount '/vendor' (Permission denied)
Any idea of what's going wrong?
Click to expand...
Click to collapse
Do it through fastboot d
toolhas4degrees said:
Do it through fastboot d
Click to expand...
Click to collapse
I also tried through fastboot d
toolhas4degrees said:
Do it through fastboot d
Click to expand...
Click to collapse
Thanks, but no luck with fastboot d either.
arcadia2uk said:
I also tried through fastboot d
Thanks, but no luck with fastboot d either.
Click to expand...
Click to collapse
Only work on custom roms, and you need to wipe all in fastboot d then flash twrp. Are you using chinese twrp?
toolhas4degrees said:
Only work on custom roms, and you need to wipe all in fastboot d then flash twrp. Has to be done before initial boot of rom Are you using chinese twrp?
Click to expand...
Click to collapse
Because that twrp is not updated
I have Lineage 17.1 Unofficial installed, using twrp-3.4.0-2-hotdog-unified-mauronofrio.
I also tried rigorously following instructions provided by LuK1337 @ https://wiki.lineageos.org/devices/hotdog/install still no luck.
I guess I'll just stay on the Lineage 17.1 Unofficial as it works very well as is.