Stuck in install loop - keeps getting wiped on boot? - LineageOS Questions & Answers

I'm trying to install LineageOS 17 on a OnePlus 6.
I can boot into twrp and the install process appears to work successfully. I can swap slots and install into either slot.
When I reboot the phone I get to the screen that says "Start" and "Fastboot mode" at the top. If I try to start the phone it comes back to this screen. When I go back into twrp, the contents of /sdcard is empty. I can copy over files using adb push, install the rom and then reboot. However, every time I reboot it seems like it completely wipes the phone including the install it's just done and /sdcard is also wiped.
When I booted into twrp previously, it required my unlock code. It now no longer does that. I wonder if this is part of the problem?
If I install just oxygenos, it takes me to the oxgenos recovery screen but I cant' do anything from there. I'm guessing that won't allow me to boot with an unlocked bootloader?
Can anyone advise how I can get out of this? Installing anything using twrp looks like it works, but it's like it gets wiped every time I reboot.
I can't even seem to get OxygenOS back to working.
Can anyone give me some tips on where to go from here? Nothing I can do from TWRP seems to help. I have tried wiping everything in both slots and reinstalling oxygen, no luck

Still stuck?

Related

How to repair Wileyfox Swift when I can get into TWRP but not bootloader

Hi. I've just updated CM13 to the latest nightly using TWRP, but now the system just boots into TWRP - that's whether I select boot system, recovery, or bootloader. I tried restoring from a TWRP backup or another copy of the nightlies zip - it all seems to work fine but doesn't solve the problem. I can connect to the 'recovery' device using adb but adb restart bootloader just loads TWRP again. I've tried wiping first the dalvik/cache, then everything but the internal card, then finally everything but nothing seems to work.
I did get something a little bit like this a few days ago because SuperSU was complaining that I needed to update the binary. I let it do it the way that it suggested one does when TWRP is installed and afterwards couldn't reboot into system, but after a few minutes of frustration sorted things by wiping various partitions.
I attempted to load the full system restore files (cm-13.1-ZNH2KAS29G-crackling-signed-fastboot-74bb753396.zip) using TWRP but that didn't work (I imagine because they're designed to be run via fastboot). I tried loading them via the ADB sideloader option included in TWRP but it failed after a few seconds (I think the message was 'transmitting 0.0x'
I opened that zip and copied the various files to the external card, but I then baulked at installing the image files manually because the only partition option I'm given is boot and my understanding is that each image file should go into its own partition.
The only other potentially pertinent information I can think of:
TWRP keeps reporting "E: Unable to find partition size for '/recovery'"
Has anyone got any ideas please? I had been musing that my next phone would have OTG and NFC, but I wasn't planning to upgrade just yet if I don't absolutely have to.
Have you got it fixed? And if yes - how? I am stuck in a similar situation and can't find a solution for it. Tnx in advance.

problem after updating rom/soft-bricked?

So I was updating six rom and phone went into continuous boot. So went into recovery and wiped all but internal memory and reinstalled. Same boot problem. Went into fast boot and pushed another over as well as a vendor image. Tried installing the new rom, beans gaps, super su and same result. I've left the phone for over 20 mins with no result but the boot screen.
I'm having a similar problem.
My status- Unlocked bootloader, twrp accessible, devices not getting detected in fastboot mode by the pc, rooted, restoring using the backup results in a bootloop, correct drivers installed on the pc, superSU and full backup in the mobile.
i cant transfer files since device not getting detected.
my timeline- i followed every instruction on https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930 and everything went successful, but when it rebooted to the 'Welcome' page (the page which comes when u open mobile for the first time) i restarted my nexus 5x 32gb to recovery mode and then the every boot procedure doesn't complete for several minutes(doesn't go ahead the ball animation)

[solved ]Update with Flashfire and current factory image leads to bootloop into twrp

Hi,
I wanted to update my Pixel C to the most current factory image with flashfire as i did it before a few times without problems.
So I DL'd current factory image from https://developers.google.com/android/images#ryu, opened it in flashfire and said it should flash the normal partitions except recovery as i don't want that it overwrites my TWRP.
Flashfire analyzed the zip file and after i said "flash" it restarted my Pixel into a black screen. At this point i was wondering that nothing more happened.
I waited for 10 minutes so that maybe something in the background could happen, but there was no further action. The screen kept black.
After these 10 minutes i restarted the device but now it always runs into TWRP directly instead of starting the system
I also tried to install the zip manually in TWRP but it tells me
"Could not find 'META-INF/com/google/android/update-binary' in the zip file.
Error installing the zip file '/usb-otg/ryu-n2g48c-factory-0bc0ee15.zip'"
As you can see from the error message i also tried to dl the file again and install it via OTG but the same thing.
If I go into the file manager in TWRP i can still access the folders from the sdcard.
The bootloader is unlocked of course.
Anyone an idea what i can do without loosing all the data?
Thanks in advance
Download the full system image and extract it. There should be a flash_all-file (bat for windows of sh for linux). Open it with an editor and remove the "-w" option in fastboot. "-w" is the switch for wipe. After you removed it, you can flash the complete image and your system should boot again into android. After that you can install a custom recovery, etc. again.
Thank you peter, worked like a charm for the system flash. Now follows the TWRP etc again
EDIT: ok, the system flash was the only thing that worked like a charm. I tried flashing TWRP with NRT but didn't work. I am stuck now at a "no command" screen when i start the device.
To install the custom recovery NRT tells me that i will loose all my data, so i wanted to backup everything.
Unfortunately i can't backup everything now as the temp booted TWRP demands a password to decrypt the sdcard, but i only have a pattern and no password set.
So now i try to flash everything again and to install twrp without loosing all the data.
Hey everyone I have flashed android 7.1.2 August again and android started afterwards without any problems. I was able to restore the backup of all the apps from Google.
Than I wanted to get back root and flashed TWRP with Nexus Root Toolset, but now only TWRP starts every time I switch on the tablet. Any ideas what I can do?
EDIT: I fixed it somehow with flashing the whole firmware package again and than the TWRP wich broke the startup again so i ended up in a TWRP bootloop. Therefore i flashed android again and TWRP 3.0.0.0 than TWRP 3.0.2.4 (something like that) and after like 3 to 4 different flashing steps it worked again. I have no idea what happened during the first flash of Andoir 7.1.2 but i think that something broke there.

Format failed when doing a full wiping of OnePlus 3

Hi,
I need some help with my OnePlus 3 running the latest or close to latest Android 8 OTA stock rom. It started half year ago, suddenly the phone was in a boot loop. I switched it on and off and I managed it to start again, doing a factory reset and wiping cache data. Then I reentered my details and selected a password. It was working for some days again, but I struggled to enter the right password after a while. Not because I'm stupid, it's pretty easy and I did it again and again. Then it was accepted and the phone was running again. I backuped my data and wiped it again just to check whats going on with that password. After restart I reentered all my data with password 0000. After restarting, it started again having trouble to enter the right password... not accepted. Switching on and off and then suddenly 0000 was accepted.... I don't know, I was tired to use this phone anymore and left it on my desktop.
Now half a year later. I want to fix this somehow and I thought, ok nothing to lose. I try that new Android 9 beta with adb sideload. Before that I'll do a full wipe loosing all my data (no problem). The wiping bar stucks at 99% and then it says "Format failed" with the only option "Yes". So stuck there, not started to sideload so far.
Update 1:
If I select that "Yes", I'm back in that erasing menu, with 3 options factory reset, wiping cache and erasing everything... if I select the last option again, it takes a second saying "Format failed"... I could do this forever. But if I select another option like wiping data something strange happens. It opens up a password screen asking for password... none of my passwords are working there. It is starting to decrypt... but stops with vibration and I'm back in that password screen. Only option that is left is "Forget password". If I select that, it is warning me, that I'll lose all my data. I say "Yes" and it's rebooting with a Chinese screen with a bar stucking at 99% again. That after a while the screen turns black. Phone is rebooting into that Chinese screen again, animating the bar to 100% again, switching itself off. If I start normal, Android logo appears, thats it, no OnePlus circle is coming up. Then I did it once more... "Chinese init/wiping loop" again. So I can restart normally having this or restart in recovery to do all the things as before.
Update 2:
After showing up the Chinese init/wipe loop again it restarted but now with red/white OnePlus circle animation. As you read this, it's still rotating...
Are there any thoughts about it... has this phone a hardware damage or what can I do? I appreciate any ideas.
Cheers, cyx
cyx said:
Hi,
I need some help with my OnePlus 3 running the latest or close to latest Android 8 OTA stock rom. It started half year ago, suddenly the phone was in a boot loop. I switched it on and off and I managed it to start again, doing a factory reset and wiping cache data. Then I reentered my details and selected a password. It was working for some days again, but I struggled to enter the right password after a while. Not because I'm stupid, it's pretty easy and I did it again and again. Then it was accepted and the phone was running again. I backuped my data and wiped it again just to check whats going on with that password. After restart I reentered all my data with password 0000. After restarting, it started again having trouble to enter the right password... not accepted. Switching on and off and then suddenly 0000 was accepted.... I don't know, I was tired to use this phone anymore and left it on my desktop.
Now half a year later. I want to fix this somehow and I thought, ok nothing to lose. I try that new Android 9 beta with adb sideload. Before that I'll do a full wipe loosing all my data (no problem). The wiping bar stucks at 99% and then it says "Format failed" with the only option "Yes". So stuck there, not started to sideload so far.
Update 1:
If I select that "Yes", I'm back in that erasing menu, with 3 options factory reset, wiping cache and erasing everything... if I select the last option again, it takes a second saying "Format failed"... I could do this forever. But if I select another option like wiping data something strange happens. It opens up a password screen asking for password... none of my passwords are working there. It is starting to decrypt... but stops with vibration and I'm back in that password screen. Only option that is left is "Forget password". If I select that, it is warning me, that I'll lose all my data. I say "Yes" and it's rebooting with a Chinese screen with a bar stucking at 99% again. That after a while the screen turns black. Phone is rebooting into that Chinese screen again, animating the bar to 100% again, switching itself off. If I start normal, Android logo appears, thats it, no OnePlus circle is coming up. Then I did it once more... "Chinese init/wiping loop" again. So I can restart normally having this or restart in recovery to do all the things as before.
Update 2:
After showing up the Chinese init/wipe loop again it restarted but now with red/white OnePlus circle animation. As you read this, it's still rotating...
Are there any thoughts about it... has this phone a hardware damage or what can I do? I appreciate any ideas.
Cheers, cyx
Click to expand...
Click to collapse
Try THIS version of TWRP to format and flash.
tnsmani said:
Try THIS version of TWRP to format and flash.
Click to expand...
Click to collapse
Update 3:
Before following tnsmani's advice to install TWRP I did something that makes things worse. Because I couldn't wait, I sideloaded the new Android 9 zip without any problems in sideload mode. It was installed and the loading circle was coming up. It took a while and finally the phone switched off. Now the phone is booting up to a new rounded edge OnePlus splash screen without any animation and It's not possible to start the old recovery mode anymore. So I can't connect to adb or fastboot to install that TWRP. All what is coming up are different menus without the options I need. I attached two new pictures to show them. But I can't establish a connection to my pc anymore. No devices showing up.
Update 4:
Ok, it seems that fastboot is communicating when I'm in that green/red menu which says start but my command:
fastboot flash recovery twrp-3.2.3-10-oneplus3.img
fails with the output:
target reported max download size of 440401920 bytes
erasing 'recovery'...
FAILED (remote: Partition erase is not allowed)
finished. total time: 0.019s
Update 5:
Ok, I followed this steps:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
to unbrick the device with MSMDownloadTool and Qualcomm drivers, but with no real success so far. But I can start recovery mode again and adb sideload is working as well.
But with anything else, I have no luck. After a new sideload it's keeps anĂ­mating the Oneplus dots and I can't install TWRP to do a clean wipe.
All I want to have is a booting up final or beta stock rom working as before, without any specials.
cyx said:
Update 5:
Ok, I followed this steps:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
to unbrick the device with MSMDownloadTool and Qualcomm drivers, but with no real success so far. But I can start recovery mode again and adb sideload is working as well.
But with anything else, I have no luck. After a new sideload it's keeps anĂ­mating the Oneplus dots and I can't install TWRP to do a clean wipe.
All I want to have is a booting up final or beta stock rom working as before, without any specials.
Click to expand...
Click to collapse
Is fastboot/bootloader working or not? If it is, simply flash the TWRP first and then proceed with ROM.
If the MSM Download Tool succeeded, you should be able to boot. If not, it means that it did not succeed. Try it a few more times since for some people, repeated attempts are required before the phone boots.
cyx said:
Update 5:
Ok, I followed this steps:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
to unbrick the device with MSMDownloadTool and Qualcomm drivers, but with no real success so far. But I can start recovery mode again and adb sideload is working as well.
But with anything else, I have no luck. After a new sideload it's keeps an
Click to expand...
Click to collapse
What I noticed from your SS is that your bootloader is locked. So no way you can flash or run a custom recovery til the time you actually unlock your bootloader.
I will advise to unlock bootloader first, flash TWRP fixed version (somewhere in LOS thread is the link), "format" /data partition, flash your desired OOS Rom and then try again and see if it works.
@cyx
Boot into the bootloader and on the PC enter this command: fastboot oem unlock.
This should unlock the bootloader. Then flash TWRP, boot back into it and flash ROM etc.

Pixel Experience boot loop + string of stupid decisions: is there any way out?

Hi there,
I think I (soft? hard?) bricked my whyred today after trying to install Pixel Experience (Android 10). At this time, I'm left with a flashed PE Plus that is stuck at the Google logo animation (e.g. unable to access USB debug settings); stock MIUI recovery; and fastboot, which is not recognized by ADB as I haven't had a successful boot since I flashed PE, so I can't turn USB debug on. I think I've exhausted my options, but maybe someone has a smart solution.
For those who think they can help, let me describe in detail what I did:
0) I became a dev, turned USB debug on, installed Minimal ADB and Fastboot, latest Xiaomi drivers, moved flashable zips into internal storage etc.
1) I unlocked my bootloader through Mi Unlock.
2) I successfully flashed TWRP-3.3.1.0-whyred via ADB/Fastboot and rebooted. After getting back into MIUI, I booted into recovery, which was back to stock (MIUI seems to have overwritten my recovery). At that point (probably a big mistake) I gave up on flashing TWRP and went ahead to boot right into it via ADB instead, without flashing.
3) After a successful boot into TWRP 3.3.1.0, it asked me for a decryption password. Nothing worked, so I kept googling and found out that my version of android needs TWRP 3.3.1.1, which was not on the official TWRP website yet, to decrypt automatically. I booted into TWRP 3.3.1.1 via ADB (but didn't flash), made a backup of my stock ROM, did a wipe (art/dalvik cache, cache, data, system, vendor), flashed Pixel Experience and rebooted.
4) Bootloop, I was stuck on the Google loading animation for over 20 minutes, nothing happened.
5) I panicked.
6) I tried to flash TWRP 3.3.1.1 via ABD but my PC didn't recognize my phone - probably because, for lack of successful boots, I have not managed to turn on USB debug.
7) I tried to connect to Mi Assistant through stock recovery. It didn't recognize my phone, probably for the above reason.
8) I did a data wipe through stock recovery and rebooted, hoping for whatever issue kept PE from booting normally to get resolved.
9) I'm stuck on the same Google loading animation for over 40 minutes now, no progress.
Does any of you guys see a way out, or is this story over? To recap, I have: 1) PE Plus in bootloop, no access to dev settings, 2) stock MIUI recovery with options to reboot, wipe data or connect to Mi Assistant, 3) stock fastboot, 4) a backup of my previous system on internal storage, 5) ADB on my computer that doesn't recognize my phone - no USB debugging. I don't know where to turn. I don't care much about data, I have everything in the cloud, but I'd like to save the phone if possible.
Thanks a lot.
Edit: Problem resolved - even though the connected device didn't show up in ADB on PC (adb devices came back empty), the phone was still responsive to fastboot reboot and fastboot flash recovery via PC, so I could flash TWRP 3.3.1.1 & clean flash PE. For anyone struggling with PE bootloops: make sure to 1) use TWRP 3.3.1.1 to flash, 2) do a dalvik/cache wipe after flashing the ROM and 3) not to install the TWRP app before the first successful boot - it was neglecting either 2) or 3) that caused my bootloop. The ROM itself is amazing!
mkohan said:
Hi there,
I think I (soft? hard?) bricked my whyred today after trying to install Pixel Experience (Android 10). At this time, I'm left with a flashed PE Plus that is stuck at the Google logo animation (e.g. unable to access USB debug settings); stock MIUI recovery; and fastboot, which is not recognized by ADB as I haven't had a successful boot since I flashed PE, so I can't turn USB debug on. I think I've exhausted my options, but maybe someone has a smart solution.
For those who think they can help, let me describe in detail what I did:
0) I became a dev, turned USB debug on, installed Minimal ADB and Fastboot, latest Xiaomi drivers, moved flashable zips into internal storage etc.
1) I unlocked my bootloader through Mi Unlock.
2) I successfully flashed TWRP-3.3.1.0-whyred via ADB/Fastboot and rebooted. After getting back into MIUI, I booted into recovery, which was back to stock (MIUI seems to have overwritten my recovery). At that point (probably a big mistake) I gave up on flashing TWRP and went ahead to boot right into it via ADB instead, without flashing.
3) After a successful boot into TWRP 3.3.1.0, it asked me for a decryption password. Nothing worked, so I kept googling and found out that my version of android needs TWRP 3.3.1.1, which was not on the official TWRP website yet, to decrypt automatically. I booted into TWRP 3.3.1.1 via ADB (but didn't flash), made a backup of my stock ROM, did a wipe (art/dalvik cache, cache, data, system, vendor), flashed Pixel Experience and rebooted.
4) Bootloop, I was stuck on the Google loading animation for over 20 minutes, nothing happened.
5) I panicked.
6) I tried to flash TWRP 3.3.1.1 via ABD but my PC didn't recognize my phone - probably because, for lack of successful boots, I have not managed to turn on USB debug.
7) I tried to connect to Mi Assistant through stock recovery. It didn't recognize my phone, probably for the above reason.
8) I did a data wipe through stock recovery and rebooted, hoping for whatever issue kept PE from booting normally to get resolved.
9) I'm stuck on the same Google loading animation for over 40 minutes now, no progress.
Does any of you guys see a way out, or is this story over? To recap, I have: 1) PE Plus in bootloop, no access to dev settings, 2) stock MIUI recovery with options to reboot, wipe data or connect to Mi Assistant, 3) stock fastboot, 4) a backup of my previous system on internal storage, 5) ADB on my computer that doesn't recognize my phone - no USB debugging. I don't know where to turn. I don't care much about data, I have everything in the cloud, but I'd like to save the phone if possible.
Thanks a lot.
Click to expand...
Click to collapse
I'm new to this phone as well (but not to Android). Try the following:
Download TWRP from here -> https://androidfilehost.com/?fid=6006931924117884758
Download Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip from here -> https://zackptg5.com/downloads/Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip
Power off phone. Hold down volume down and power button to boot into fastboot
Give the command fastboot flash recovery twrp-3.3.1-1-whyred.img to flash the recovery you downloaded earlier.
Boot into recovery
Flash Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip that you downloaded earlier
The above steps will at least ensure that you retain TWRP and it doesn't get overwritten by stock MIUI recovery
After that, check whether or not your phone/ROM has anti-rollback enabled and take appropriate steps accordingly.
Ok so i flashed PE 10 plus today and was met with the same problem.
Heres how i solved it
Goto fastboot option by pressing volume down and power button
Connect to pc (If it doesnt recognize, reinstall Adb drivers and phone drivers)
If it asks for decryption password just press cancel
Wipe data/internal/vendor (wont be able to wipe dalvik as it wont mount)
Flash PE 10 Plus and nothing else.
It should boot just fine.
However i run into bootloop if i flash latest magisk so i cant root my phone :/
Hope this helps
mkohan said:
Edit: Problem resolved - even though the connected device didn't show up in ADB on PC (adb devices came back empty), the phone was still responsive to fastboot reboot and fastboot flash recovery via PC, so I could flash TWRP 3.3.1.1 & clean flash PE. For anyone struggling with PE bootloops: make sure to 1) use TWRP 3.3.1.1 to flash, 2) do a dalvik/cache wipe after flashing the ROM and 3) not to install the TWRP app before the first successful boot - it was neglecting either 2) or 3) that caused my bootloop. The ROM itself is amazing!
Click to expand...
Click to collapse
hey read your post
actually adb and fastboot are two different things.
and recovery is flashed using fastboot commands not adb.
sometimes if a rom is not booting it may have issues with encryption.

Categories

Resources