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!
Related
I'm (or rather, was) on CM13 nightly, today I downloaded TWRP through Flashify and flashed it, previously I was using Philz Touch, now I have a bootloop. I just had a bootloop a few days ago and had to install everything over again, and I really don't feel like doing it again. What can I do?
Error503 said:
I'm (or rather, was) on CM13 nightly, today I downloaded TWRP through Flashify and flashed it, previously I was using Philz Touch, now I have a bootloop. I just had a bootloop a few days ago and had to install everything over again, and I really don't feel like doing it again. What can I do?
Click to expand...
Click to collapse
Can you enter the recovery mode? And if so I would recommend reflashing everything, that usually helps xD
Summoned Egar said:
Can you enter the recovery mode? And if so I would recommend reflashing everything, that usually helps xD
Click to expand...
Click to collapse
Yes I can, but I reeeeeally don't feel like going back to stock AGAIN, I was thinking maybe flashing CyanogenMod Recovery would help fix the issue since TWRP is apparently not compatible with Marshmallow, the problem is I can't get my PC to recognize my phone in fastboot mode therefore I can't flash the new recovery. Any ideas?
Error503 said:
Yes I can, but I reeeeeally don't feel like going back to stock AGAIN, I was thinking maybe flashing CyanogenMod Recovery would help fix the issue since TWRP is apparently not compatible with Marshmallow, the problem is I can't get my PC to recognize my phone in fastboot mode therefore I can't flash the new recovery. Any ideas?
Click to expand...
Click to collapse
Why didn't you backup your data? Always backup your data! Moreover, put the image to flash on your sd card
Summoned Egar said:
Why didn't you backup your data? Always backup your data! Moreover, put the image to flash on your sd card
Click to expand...
Click to collapse
Alright, I can do that. How do I flash it after it's on my SD?
Error503 said:
Alright, I can do that. How do I flash it after it's on my SD?
Click to expand...
Click to collapse
Wipe as usual, then in TWRP go to mount and choose external_sd, after that navigate up until you find the folder external_sd and load from there
You don't need to go back to stock. If you can enter recovery, you can wipe system (only) and dirty flash your cm13 over it. It usually works and dont lose your personal files nor installed apps. If it don't, do a full wipe and flash your rom again.
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.
***SOLVED***
Hello, I had cm14 installed and I was trying to update it. after the update, the device always boots to recovery(TWRP).
I tried the full wipe and flash again the rom, again boot to recovery. what is the solution for it?
lsdream said:
Hello, I had cm14 installed and I was trying to update it. after the update, the device always boots to recovery(TWRP).
I tried the full wipe and flash again the rom, again boot to recovery. what is the solution for it?
Click to expand...
Click to collapse
what version of twrp are you running? do you have a nandroid backup that you could restore? sometimes the partitions can get messed up during an update. if nothing helps, just follow this unbrick guide which will revert your phone completely back to stock, with all the storage partitions intact.
3.0.2-1
lsdream said:
3.0.2-1
Click to expand...
Click to collapse
yeah, everyone's got that one, but there are many versions of it usually a number, like 3.0.2-1 (22) for example, and each one build for specific cases. except you got it from the official twrp web, then there shouldn't really be problems with cm14.1
what about nandroid? can you restore one?
do you have any idea how to boot it?
lsdream said:
do you have any idea how to boot it?
Click to expand...
Click to collapse
please use the quote function so i get a notification when you reply.
i do, right in my first post here is a link to an unbrick guide which will help you because clearly something in your phone's storage is messed up. just follow it and you'll be back at stock with a fully functional phone
bombaglad said:
please use the quote function so i get a notification when you reply.
i do, right in my first post here is a link to an unbrick guide which will help you because clearly something in your phone's storage is messed up. just follow it and you'll be back at stock with a fully functional phone
Click to expand...
Click to collapse
Thanks, I just flash the stock rom and it boot normally.
lsdream said:
Hello, I had cm14 installed and I was trying to update it. after the update, the device always boots to recovery(TWRP).
I tried the full wipe and flash again the rom, again boot to recovery. what is the solution for it?
Click to expand...
Click to collapse
I had the same situation. You get out of this by fastboot flashing cm recovery, booting to it, then flash twrp back in fastboot. I think the ota doesnt fully work with twrp.
Flash the modified twrp from the second post in this forum
http://forum.xda-developers.com/oneplus-3/how-to/rom-community-build-3-5-5-t3490939
Hi, I just bought a second hand OP3, the version installed was the last Open BETA 26.
So everything was working properly but when I reset it the phone was extremly laggy, even the bootamination.
And when the phone booted-up it was very laggy and after some seconds it crash (freeze and turn off after few seconds).
I tried a lot of flashs :
- ADB slideload (impossible to flash a firmware, sometimes the command don't work and when it works it stops after 47% or 97/94%
- The ultimate flash for bricked devices (https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/), the flash worked, but the freeze problem was still here even if the version flashed was OxygenOS 3.1.2
- From this firmware I managed to flash OxygenOS 4.5.1 (the last stable one) with ADB Slideload and same problem again.
- I tried to lock / unlock the bootloader but changed nothing, I even tried to flash TWRP to flash a custom rom but impossible to find a working version.
Now I need the help of XDA Gods !
Sorry for my bad english :silly:
The worst case scenario here is that you have a bad case of corrupted or broken storage (by 'storage' I mean the entirety of the phone's NAND storage) — have you tried wiping /data (labeled as Internal Storage in TWRP) or switching its filesystem back and forth (so, for example, if you have F2FS you'd need to switch to EXT4).
I'd say you might want to start backing up whatever data left in the phone.
try turning off advanced 4g mode. I have the same problem when flashing oos (cpu usage at 50%+ when idle) and this helped me.
F4uzan said:
The worst case scenario here is that you have a bad case of corrupted or broken storage (by 'storage' I mean the entirety of the phone's NAND storage) — have you tried wiping /data (labeled as Internal Storage in TWRP) or switching its filesystem back and forth (so, for example, if you have F2FS you'd need to switch to EXT4).
I'd say you might want to start backing up whatever data left in the phone.
Click to expand...
Click to collapse
Thanks for your answer, I didn't find a working version of TWRP to test (every TWRP i tried was black screen or stuck on TWRP logo) but I already tried full wipes from stock recovery (very very many times), I will try all TWRP avaliables and try your method.
But now I think the problem is the worst case that you said :/
hellcat50 said:
try turning off advanced 4g mode. I have the same problem when flashing oos (cpu usage at 50%+ when idle) and this helped me.
Click to expand...
Click to collapse
Thx i'll try if the phone don't freeze before I access settings^^
where is exacly this option ?
Bryandu13 said:
Thanks for your answer, I didn't find a working version of TWRP to test (every TWRP i tried was black screen or stuck on TWRP logo) but I already tried full wipes from stock recovery (very very many times), I will try all TWRP avaliables and try your method.
But now I think the problem is the worst case that you said :/
Click to expand...
Click to collapse
Definitely try all available TWRP and see if any of them works. If the storage actually broke, it'd be pretty catastrophic and would be hard to recover or manually fix.
F4uzan said:
Definitely try all available TWRP and see if any of them works. If the storage actually broke, it'd be pretty catastrophic and would be hard to recover or manually fix.
Click to expand...
Click to collapse
Okay i'll focus on it ! Thanks !
Bryandu13 said:
Okay i'll focus on it ! Thanks !
Click to expand...
Click to collapse
https://forum.xda-developers.com/devdb/project/dl/?id=27068
the twrp i recommned
Bryandu13 said:
Thx i'll try if the phone don't freeze before I access settings^^
where is exacly this option ?
Click to expand...
Click to collapse
It is where you can set up apn and switch data roaming
I have the exact same problem
Changing the data format doesnt work for me.
Skinpipe said:
https://forum.xda-developers.com/devdb/project/dl/?id=27068
the twrp i recommned
Click to expand...
Click to collapse
Thanks, this TWRP works !
F4uzan said:
Definitely try all available TWRP and see if any of them works. If the storage actually broke, it'd be pretty catastrophic and would be hard to recover or manually fix.
Click to expand...
Click to collapse
I tried change everything to EXT4 (only DATA wasn't EXT4 but "emmc") but it doesn't worked
zainhateszayn said:
Changing the data format doesnt work for me.
Click to expand...
Click to collapse
That's sad :/
I hope we'll find a solution
Bryandu13 said:
I tried change everything to EXT4 (only DATA wasn't EXT4 but "emmc") but it doesn't worked
Click to expand...
Click to collapse
Unbrick guide method 2 doesn't work? I'll say start contacting Oneplus.
Puddi_Puddin said:
Unbrick guide method 2 doesn't work? I'll say start contacting Oneplus.
Click to expand...
Click to collapse
Yes, it don't work...
I don't know about conctacting OnePlus because it's a second hand model without bill, only the box.
Now I noticed that is was possible to flash any OxygenOS ROM or any OxygenOS based ROM with TWRP (the problem is still here) but impossible to get a booting AOSP based or any no-OxygenOS based ROM.
I'm trying to get the bill to get the help from OnePlus customer service.
So my phone is dead right ? We can't even find a motherboard on internet :/
Can you try
"fastboot format userdata"
"fastboot format cache",
"fastboot format system",
" fastboot erase recovery"
"fastboot reboot bootloader"
commands than flashing Oxygen recovery w/fastboot than flashing open beta 26 with Oxygen recovery? This may help.
qhsusb_bulk said:
Can you try
"fastboot format userdata"
"fastboot format cache",
"fastboot format system",
" fastboot erase recovery"
"fastboot reboot bootloader"
commands than flashing Oxygen recovery w/fastboot than flashing open beta 26 with Oxygen recovery? This may help.
Click to expand...
Click to collapse
Thanks I will try, but I don't understand your last sentence "commands than flashing Oxygen recovery w/fastboot than flashing open beta 26 with Oxygen recovery?"
Bryandu13 said:
Thanks I will try, but I don't understand your last sentence "commands than flashing Oxygen recovery w/fastboot than flashing open beta 26 with Oxygen recovery?"
Click to expand...
Click to collapse
It is your choice, you can copy zip with TWRP then flash Oxygen recovery via fastboot or just sideload it with ADB.
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