PHP:
I can boot into twrp... However, when I try and flash the installer it says failed to mount system and another partition. Tried several variants, every way I can think of. Anyone else having this prob?
Zooandbio4me said:
PHP:
I can boot into twrp... However, when I try and flash the installer it says failed to mount system and another partition. Tried several variants, every way I can think of. Anyone else having this prob?
Click to expand...
Click to collapse
Have you tried flashing the twrp 3.3.0-0.img file to the recovery ramdisk partition instead of using the zip file?
Zooandbio4me said:
PHP:
I can boot into twrp... However, when I try and flash the installer it says failed to mount system and another partition. Tried several variants, every way I can think of. Anyone else having this prob?
Click to expand...
Click to collapse
TWRP gives this error but it still works. The system partition can't be mounted in 10 as of yet. I haven't had a problem flashing anything though. It will give that error after every flash but so far everything works.
PIXEL 2XL TRWP Android 10 PROBLEM
hi, i have the same isue with the stock Android 10 and twrp-3.2.3-1.... i cant mount SYSTEM and VENDOR and i dont know how to remove TRWP... any help please...?
EDIT: this is what i get when i try to start in recovery mode:
them he erase all and reboot
EDIT: i have the TRWP in the slot A then i cant boot the system in the slot B, the photo is when i try to boot in recovery mode on the slot B i think...
estemanito said:
hi, i have the same isue with the stock Android 10 and twrp-3.2.3-1.... i cant mount SYSTEM and VENDOR and i dont know how to remove TRWP... any help please...?
this is what i get when i try to start in recovery mode:
them he erase all and reboot
Click to expand...
Click to collapse
Fastboot the stock boot.img to remove twrp. Then try using twrp version 3.3.0-0. You will still throw mounting errors when you flash zips, but it will still work :good:
it worked thank you !
EDIT: twrp-3.3.0-0 still not working on my PIXEL 2XL TAIPEN
Badger50 said:
Fastboot the stock boot.img to remove twrp. Then try using twrp version 3.3.0-0. You will still throw mounting errors when you flash zips, but it will still work :good:
Click to expand...
Click to collapse
murphyjasonc said:
TWRP gives this error but it still works. The system partition can't be mounted in 10 as of yet. I haven't had a problem flashing anything though. It will give that error after every flash but so far everything works.
Click to expand...
Click to collapse
+11111
Just ignore the warning and pretend it doesn't exist, known issue, no effect on the installs.
andy6685 said:
+11111
Just ignore the warning and pretend it doesn't exist, known issue, no effect on the installs.
Click to expand...
Click to collapse
I know it works for installs, but what about nandroid backups?
andy6685 said:
+11111
Just ignore the warning and pretend it doesn't exist, known issue, no effect on the installs.
Click to expand...
Click to collapse
I'm on the Android 10 version of pixel dust rom and I had to side load the rom, trwp, and magisk because I kept getting those errors. After the rom booted up, I booted back into twrp via the rom and everything was fine. Super weird, but everything worked ?.
jlokos said:
I know it works for installs, but what about nandroid backups?
Click to expand...
Click to collapse
On Android 10 the /system partition is locked at read only so it can't be mounted in TWRP as read write. To do a nandroid backup go to mount and select mount partitions as read only and check /system and /vendor then do the backup
Related
I just recently got an HTC one m7 that I've fully unlocked, s-off'd, and rooted and now when I try to install a Rom it fails or I should say it hangs on 1% never advancing. Furthest I've gotten is 7% on santod's nusensesixMAX Rom but it wouldn't finish. Is it my recovery? I'm on the latest TWRP. Anyone with any input please
Have you tried the No data Wipe RUU and see if it takes?
No I haven't
I would suggest doing that RUU. it is the one @dottat made where he says it will not wipe SD card that way you do not lose anything on the card. If it is a borked emmc chip and needs fixing, Dottat has some tricks up his sleeve that may work.
What's really weird is every time I boot into twrp I'm having issues with mounting system.
Do u have a link I can't seem to find it
eriknors said:
What's really weird is every time I boot into twrp I'm having issues with mounting system.
Do u have a link I can't seem to find it
Click to expand...
Click to collapse
Thanks to dottat!!!! It's here: http://forum.xda-developers.com/verizon-htc-one/help/exe-ruu-vzw-m7-4-4-3-s-users-t2919442
eriknors said:
What's really weird is every time I boot into twrp I'm having issues with mounting system.
Do u have a link I can't seem to find it
Click to expand...
Click to collapse
Update your twrp recovery to the latest. That is why system won't mount in recovery.
I wanted t oinstall Cm13 so booted into bootloader and unlocked it.
Then I installed TWRP 2.8.7.2 as my recovery. Then booted into recovery and flashed CM13 of 20/12.
It then started bootlooping the bootanimation. I waited for half an hour. The phone became heated and I switched it off.
I then decided to go back to stock 6.0.1 but I could flash using flash-all.sh. I then decided to flash manually each image and was able to flash boot, cache and recovery. But cannot flash system and vendor. Can someone help me i this.
Can anyone provide a twrp backup that I can use. (I didn't do a backup myself).
Please can someone help. Just bought the phone 2 days back. Please help.
eNVy said:
I wanted t oinstall Cm13 so booted into bootloader and unlocked it.
Then I installed TWRP 2.8.7.2 as my recovery. Then booted into recovery and flashed CM13 of 20/12.
It then started bootlooping the bootanimation. I waited for half an hour. The phone became heated and I switched it off.
I then decided to go back to stock 6.0.1 but I could flash using flash-all.sh. I then decided to flash manually each image and was able to flash boot, cache and recovery. But cannot flash system and vendor. Can someone help me i this.
Can anyone provide a twrp backup that I can use. (I didn't do a backup myself).
Please can someone help. Just bought the phone 2 days back. Please help.
Click to expand...
Click to collapse
post a screenshot from cmd here to see the error you get from fastboot...
kopfik said:
post a screenshot from cmd here to see the error you get from fastboot...
Click to expand...
Click to collapse
There is no error. When I manually try to flash system or vendor there is the message sending 'vendor' or sending 'system' and gets stuck with that message. waited for almost half an hour and still no change.
When I booted into twrp, it says cannot mount /vendor and /system.
Edit : I use Linux by the way.
eNVy said:
There is no error. When I manually try to flash system or vendor there is the message sending 'vendor' or sending 'system' and gets stuck with that message. waited for almost half an hour and still no change.
When I booted into twrp, it says cannot mount /vendor and /system.
Edit : I use Linux by the way.
Click to expand...
Click to collapse
well, interesting. i've never experienced problem like you have... have you already tried to do it in windows? or install TWRP v2.8.7.0 and format partitions in that version and then reflash original ROM. but remember, with 2.8.7.0 you wont be able to flash CM13 (at least on my N5X i wasn't....)
kopfik said:
well, interesting. i've never experienced problem like you have... have you already tried to do it in windows? or install TWRP v2.8.7.0 and format partitions in that version and then reflash original ROM. but remember, with 2.8.7.0 you wont be able to flash CM13 (at least on my N5X i wasn't....)
Click to expand...
Click to collapse
Shouldn't you be using the latest twrp 2.8.7.2? Ive had issues flashing roms without using the latest version. You could also have issues with older versions of twrp and encryption. Id suggest wiping data from twrp and then flashing the factory image from bootloader.
Sent from my Nexus 5X using Tapatalk
Im in the exact same situation and my fastboot is broken. My PC isnt recognizing a device is attached anymore. No system or vendor mount in twrp
I think to be able to really do anything you need to get into bootloader and have fastboot recognize the device. Make sure the files from 6.01 are all correct and you're flashing in the right order. Follow the guide item #8 http://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930 If you can get the system.img and vendor.img flashed and then lock the bootloader it will wipe everything to factory, internal storage included. If you do that you must have stock recovery.img flashed as well. If downloading system.img hangs reboot and try it again.
kopfik said:
well, interesting. i've never experienced problem like you have... have you already tried to do it in windows? or install TWRP v2.8.7.0 and format partitions in that version and then reflash original ROM. but remember, with 2.8.7.0 you wont be able to flash CM13 (at least on my N5X i wasn't....)
Click to expand...
Click to collapse
Sorry, I was using v.2.8.7.2.
mnehring said:
Im in the exact same situation and my fastboot is broken. My PC isnt recognizing a device is attached anymore. No system or vendor mount in twrp
Click to expand...
Click to collapse
I got it to work. I just had to change the USB port.
Why don't you try a different USB port or a different cable. Or even try on a different computer.
Once again I am stuck in same situation.*
I can only boot on restored twrp backup.*
I cant boot on any other custom roms.*
It install perfectly but after i reboot it gets stuck on 1+ boot logo.*
op3lite
saultanised cm
cm14
be it any rom i am already on 3.2.7 firmware.*
Followed mega unbrick guide and restored stock partitions. the phone boots properly. but when i remove encryption via fastboot,phone doesnt boot after that. again i have to go through all unbrick guide. back to stock 3.1.2. none of the roms boot except twrp restore.*
I m totally fed up. Please help.
nikhilsnigam said:
Once again I am stuck in same situation.*
I can only boot on restored twrp backup.*
I cant boot on any other custom roms.*
It install perfectly but after i reboot it gets stuck on 1+ boot logo.*
op3lite
saultanised cm
cm14
be it any rom i am already on 3.2.7 firmware.*
Followed mega unbrick guide and restored stock partitions. the phone boots properly. but when i remove encryption via fastboot,phone doesnt boot after that. again i have to go through all unbrick guide. back to stock 3.1.2. none of the roms boot except twrp restore.*
I m totally fed up. Please help.
Click to expand...
Click to collapse
What twrp version are you using?
Piyush lalwani said:
What twrp version are you using?
Click to expand...
Click to collapse
latest official twrp
nikhilsnigam said:
latest official twrp
Click to expand...
Click to collapse
Can you give a try to nodded twrp and one more thing mount system before flashing any ROM.
Note: after decrypting if you want too boot into OOS you need to Flash SuperSU or otherwise the OOS will force encryption and that may create problem.
Piyush lalwani said:
Can you give a try to nodded twrp and one more thing mount system before flashing any ROM.
Note: after decrypting if you want too boot into OOS you need to Flash SuperSU or otherwise the OOS will force encryption and that may create problem.
Click to expand...
Click to collapse
I did that already. after flashing supersu immediately then also stuck at boot screen. tried with modded twrp too 3.0.2.22
Piyush lalwani said:
Can you give a try to nodded twrp and one more thing mount system before flashing any ROM.
Note: after decrypting if you want too boot into OOS you need to Flash SuperSU or otherwise the OOS will force encryption and that may create problem.
Click to expand...
Click to collapse
okay now after few trial and error method i have come to the conclusion that this happens only after unencrypting the device. after eunencrypting it wont boot any other roms except those which have been already backed up.
So,
can i flash roms on encrypted device? I mean i test a lot of roms and i change frequently.
I guess no, right?
Yes try with encryption as the ROMs doesn't require decrypting the device. Decrypted device is only required if you want to use multirom.
Good Luck.
Piyush lalwani said:
Yes try with encryption as the ROMs doesn't require decrypting the device. Decrypted device is only required if you want to use multirom.
Good Luck.
Click to expand...
Click to collapse
but every time we try to reboot in recovery it asks for password to decrypt.
and if i enter default password storage shows only 32gb. that is strange
nikhilsnigam said:
but every time we try to reboot in recovery it asks for password to decrypt.
and if i enter default password storage shows only 32gb. that is strange
Click to expand...
Click to collapse
In nodded recovery too?
Piyush lalwani said:
In nodded recovery too?
Click to expand...
Click to collapse
going to try with modded recovery this time
nikhilsnigam said:
going to try with modded recovery this time
Click to expand...
Click to collapse
Yeah give a try
Piyush lalwani said:
Yeah give a try
Click to expand...
Click to collapse
how does modded recovery helps in this btw?
hope it works
OK So I am able to flash any rom with encrypted storage and latest modified twrp.
This is working for me right now but still haven't found solution why it wouldn't work on unencrypted storage.
Thank you.
This guide solved everything
http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-decryption-ultimate-guide-t3497940
FOR SOLUTION READ POST:
[SIZE="5"]https://forum.xda-developers.com/showpost.php?p=71007646&postcount=6[/SIZE]
Long time silent reader here. I always find solutions for my problems in xda-devs, until now.
Hope you guys can help me once again..
So, yesterday I messed up my OP3 and wiped all partitions on my phone.
I've tried many steps, trying to flash a flashable stock rom (the one with boot.img and system img) in fastboot, result= installation succeed, but getting blackscreen on boot.
Installing full OOS rom from adb sideload using stock recovery, result= failed (* cannot read 'OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip' *)
Installing full OOS rom from adb sideload using TWRP recovery, result= failed (* cannot read 'OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip' *)
Copy the rom to my phone, and installing the zip with TWRP, result failed (error=7)
So far these are my references:
https://forums.*neplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip
OnePlus3Oxygen_16_OTA_008_all_1606122244_e0cfc5ffc8bf411a.zip
oxygen-os-3.2.5-fastboot-flashable.zip
twrp 3.0.3
https://forum.xda-developers.com/showthread.[/CODE]php?t=2588979
Click to expand...
Click to collapse
applsaus said:
Long time silent reader here. I always find solutions for my problems in xda-devs, until now.
Hope you guys can help me once again..
So, yesterday I messed up my OP3 and wiped all partitions on my phone.
I've tried many steps, trying to flash a flashable stock rom (the one with boot.img and system img) in fastboot, result= installation succeed, but getting blackscreen on boot.
Installing full OOS rom from adb sideload using stock recovery, result= failed (* cannot read 'OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip' *)
Installing full OOS rom from adb sideload using TWRP recovery, result= failed (* cannot read 'OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip' *)
Copy the rom to my phone, and installing the zip with TWRP, result failed (error=7)
So far these are my references:
Click to expand...
Click to collapse
So twrp is working right?
Flash any rom say lineage os
Flash multirom by BitOBSessiOn
Flash multirom twrp
Flash oos as secondary rom
And then swap oos to primary rom
try with some other TWRP . May be v16 blu_spark
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Ye sideboard gives me issues aswell, push the zip and manually flash it In twrp: "adb push romzipname /sdcard/", the file is now ib the folder /sdcard/.
Puddi_Puddin said:
Ye sideboard gives me issues aswell, push the zip and manually flash it In twrp: "adb push romzipname /sdcard/", the file is now ib the folder /sdcard/.
Click to expand...
Click to collapse
tried it with OOS 3.2.8 and OOS 4.0.2, both give me ERROR=7
abhi0502 said:
So twrp is working right?
Flash any rom say lineage os
Flash multirom by BitOBSessiOn
Flash multirom twrp
Flash oos as secondary rom
And then swap oos to primary rom
Click to expand...
Click to collapse
Working on it. Flashed lineage os, looks like working.
Still waiting on boot screen tho (15 mins & counting, hope it won't be bootloop)
hyperorb said:
try with some other TWRP . May be v16 blu_spark
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Click to expand...
Click to collapse
Good idea, I'll put ur idea for the next try
applsaus said:
tried it with OOS 3.2.8 and OOS 4.0.2, both give me ERROR=7
Working on it. Flashed lineage os, looks like working.
Still waiting on boot screen tho (15 mins & counting, hope it won't be bootloop)
Good idea, I'll put ur idea for the next try
Click to expand...
Click to collapse
Then it's a twrp issue. I'm currently in Bluspark v16 so
Error 7 in TWRP AFAIK is an issue with using an incompatible recovery, try the latest one 3.0.4-1 I think it is from this forum.
Puddi_Puddin said:
Then it's a twrp issue. I'm currently in Bluspark v16 so
Click to expand...
Click to collapse
ghostofcain said:
Error 7 in TWRP AFAIK is an issue with using an incompatible recovery, try the latest one 3.0.4-1 I think it is from this forum.
Click to expand...
Click to collapse
I flash twrp bluspark as @Puddi_Puddin suggested and flashing Freedom OS. After that, I restore my data using my last Nandroid backup, then the bootloop comes again. Tried it several times using TWRP Bluspark with different ROMs, still no luck. So I suggest, there's nothing I can do to restoring my phone's data.
I read across the XDA forums and Oneplus forums that some people had similar issues for me, and they suspected something's wrong about corrupted partition, not because twrp version. And I also had tried flashing a few ROM in the past using the same TWRP 3.03 version without any problems. Strange.
Anyway, problems solved, my phone's up and running.
CASE CLOSED.
Thanks XDA
P.S: MODS Please Lock/Close this thread
applsaus said:
Anyway, problems solved, my phone's up and running.
CASE CLOSED.
Thanks XDA
P.S: MODS Please Lock/Close this thread
Click to expand...
Click to collapse
And, what was the solution ?
Restarting from Zero I guess.
Donglip said:
And, what was the solution ?
Click to expand...
Click to collapse
This:
hyperorb said:
try with some other TWRP . May be v16 blu_spark
https://forum.xda-developers.com/devdb/project/?id=15934#downloads
Click to expand...
Click to collapse
emuandco said:
Restarting from Zero I guess.
Click to expand...
Click to collapse
Better than not starting at all, at least.
I have this weird situation where I have working fastboot and recovery (TWRP 3.3.1.0) however I cannot write any roms to the device.
When I try to install a rom, everything seems to be working but then after the reboot I get stuck at the animation screen. When I reboot
back into TWRP, I see that the system partition is empty. It is as if TWRP thinks it is writing the files but they are not written. I don't know. I am really
confused. Can anybody help me with this?
Considering that TWRP is accessible, I am not counting this as a brick, yet.
bgenc said:
I have this weird situation where I have working fastboot and recovery (TWRP 3.3.1.0) however I cannot write any roms to the device.
When I try to install a rom, everything seems to be working but then after the reboot I get stuck at the animation screen. When I reboot
back into TWRP, I see that the system partition is empty. It is as if TWRP thinks it is writing the files but they are not written. I don't know. I am really
confused. Can anybody help me with this?
Considering that TWRP is accessible, I am not counting this as a brick, yet.
Click to expand...
Click to collapse
Hi folks,I have the same problems any ideas? Thanks
cripa-fr said:
Hi folks,I have the same problems any ideas? Thanks
Click to expand...
Click to collapse
Format (not wipe) the partitions completely. It works.
bgenc said:
Format (not wipe) the partitions completely. It works.
Click to expand...
Click to collapse
But be careful, you will lose everything on the internal storage. So first back up things from twrp to pc.
@bgenc
That WORKS, Thanks!