Related
Hey guys,
Long time lurker, ROM user since the Galaxy S days.
Weird, intractable bootloop problem here. Gets to boot animation sometimes gets to the "upgrading android" screen, then bootloops in a few seconds after upgrading a few apps. Usually bootloops during the boot animation (doesn't matter what ROM or Stock ROM I try). Ocassionally gets to my "SIM PIN" screen, then reboots before I have a chance to enter anything.
Normal State have Cyanogenmod and Franco Kernel running buttery smooth. (CM10.1M3 Snapshot + Franco 376 when problem started)
Problem Started When I tried to update CM to the new RC1 from the Cyanogenmod upgrade button in "settings". I had SuperSU installed overtop the built-in superuser. Everything was working fine.
What I have tried:
Have latest CWM: Have flashed, reflashed, wiped and re-wiped everything imaginable through CWM. All Caches, system sdcard, you name it, if it's an option in CWM I have tried formatting or wiping it and reflashing a ROM.
ROMs I have tried - CM10.1M3 Snapshot, CM10.1RC1 CM10.1RC2, ParanoidAndroid 3.5+ (Latest), Bigxie Maguro Latest.
Finally I got fed up and decided to go back to STOCK, unrooted, unlocked using fastboot.
I did:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader magurobootloader.img
> fastboot reboot-bootloader
> fastboot flash radio radioxxlj1.img
> fastboot reboot-bootloader
> fastboot -w update image-maguro-jdq39.zip
And after booting back into the STOCK google recovery (man I haven't seen that screen in AGES) and resetting factory clearing cache. Low and behold -
STILL BOOT LOOPS!!!! What the hell!?!
I'm at my wits end. Any suggestions would be great. What am I forgetting here?! I am absolutely desperate.
What is in the update image and where did you get it? I'd flash everything manually, skip the update command.
bodh said:
What is in the update image and where did you get it? I'd flash everything manually, skip the update command.
Click to expand...
Click to collapse
Ok good idea, I'll try. The update image was the stock image from google (can't post link - low post count) I just didn't remember the filenames when I was making the original post - but they are the official STOCK images - for the radio, the bootloader and the ROM.
Vihsadas said:
Ok good idea, I'll try. The update image was the stock image from google (can't post link - low post count) I just didn't remember the filenames when I was making the original post - but they are the official STOCK images - for the radio, the bootloader and the ROM.
Click to expand...
Click to collapse
Okay I tried flashing boot, system, userdata, and recovery manually with fastboot flash and after that I STILL get the rebootloop from google logo to boot animation to google logo. So weird.
Any other ideas?
Vihsadas said:
Okay I tried flashing boot, system, userdata, and recovery manually with fastboot flash and after that I STILL get the rebootloop from google logo to boot animation to google logo. So weird.
Any other ideas?
Click to expand...
Click to collapse
So decided to try TWRP just to see...well I dunno.
Interstingly enough when I got to hit "reboot" in TWRP it says "OS not installed!!" which is weird because I basically flashed the stock everything 4.2.2 (bootloader recovery, system, boot, everything) from fastboot. Then JUST flashed the TWRP recovery.
I really don't know what to make of this. I just tried keeping the battery out for like 2 minutes, then going back into fastboot and manually flashing:
bootloader
boot
radio
recovery
system
userdata
relocked bootloader
of the STOCK google maguro 4.2.2 (MD5 sum is good. It checked out)
And I still get a continuous reboot loop that doesn't even get past the "X" animation screen. Very ocassionally (1/10) it does get past that screen and I get to the screen where you choose your language, but right when I choose my language, the phone reboots and then continues the loop.
Honestly...Unless someone has another idea, I think I'm going to get another phone tomorrow and pray I'm under warranty. I hate to do it, because I've never had to do that before through all my flashing/ROM adventures...but I don't know what else to do. I've been using sideload for everything (except of course the fastboot flashing back to stock), but I doubt that has anything to do with it...I dunno crap.
anyone have any words of advice?
One thing I thought i might work was redoing the partition table in Odin. So I tried this method:
http://forum.xda-developers.com/showthread.php?t=2065470 (Thanks to Samersh72)
ODIN worked perfectly, download mode worked well, installed fine, and...
still bootloops!
Sometimes gets to "updating android" does a few apps, then bootloops. Once got to the screen where I select language, and before I could select anything - bootloop!
Do you guys think this is hardware? Right now I've installed stock 4.2.2 through ODIN and locked the bootloader in anticipation of returning the phone...
give a try to omap flash
Good Luck
samersh72 said:
give a try to omap flash
Good Luck
Click to expand...
Click to collapse
I looked into the OMAP flash method - that's some hardcore stuff. It looks like it's more for phones that can't access recovery, or hard seemingly bootbricked. I can actually do all of those things with my phone - I can write a new recovery no problem, I have fastboot access (Works well), I can even seemingly install ROMs - for instance the cyanogenmod boot animation plays fine - but everything boot loops.
I'm a bit worried to try OMAP Flash because it seems from the thread that some people are having their IMEI numbers erased or set to generic and I don't want that to happen since I'm actually still under warranty right now...
Do you think it's worth it to try?
Vihsadas said:
I looked into the OMAP flash method - that's some hardcore stuff. It looks like it's more for phones that can't access recovery, or hard seemingly bootbricked. I can actually do all of those things with my phone - I can write a new recovery no problem, I have fastboot access (Works well), I can even seemingly install ROMs - for instance the cyanogenmod boot animation plays fine - but everything boot loops.
I'm a bit worried to try OMAP Flash because it seems from the thread that some people are having their IMEI numbers erased or set to generic and I don't want that to happen since I'm actually still under warranty right now...
Do you think it's worth it to try?
Click to expand...
Click to collapse
you tried almost everything.... still on warranty:good:, everything is stock, so what are you waiting for, take it to service center
samersh72 said:
you tried almost everything.... still on warranty:good:, everything is stock, so what are you waiting for, take it to service center
Click to expand...
Click to collapse
Yeah you're right. OK done.
While I agree that the safest route is to return the device to warranty, omapflash is a tool which communicates with omap chip before even fastboot/bootloader is installed.
Have you tried viewing logcat/dmesg while device is booting to see why and/or its bootlooping?
Sent from my Nexus
bk201doesntexist said:
While I agree that the safest route is to return the device to warranty, omapflash is a tool which communicates with omap chip before even fastboot/bootloader is installed.
Have you tried viewing logcat/dmesg while device is booting to see why and/or its bootlooping?
Sent from my Nexus
Click to expand...
Click to collapse
I can't seem to get at logcat from this state. even if I try adb -d logcat or something similar it doesn't work. It doesn't pick up the log from the boot. Is it because USB debugging is disabled by default on the stock OS?
Vihsadas said:
I can't seem to get at logcat from this state. even if I try adb -d logcat or something similar it doesn't work. It doesn't pick up the log from the boot. Is it because USB debugging is disabled by default on the stock OS?
Click to expand...
Click to collapse
Yes, but There's a build.prop property that enables ADB debugging.. Since you have access to a custom recovery, you can mount /system rw and make your changes there.
Sent from my Nexus
Similar issue
Hey guys,
I am having a similar issue with my Nexus. It is running Phandroid 3 and one day just locked up, rebooted, and shortly after reboot (15-30 sec. after the OS loads) it freezes. I can still boot into CWM recovery and into fastboot mode, and have tried to flash it with the stock rom and bootloader. I also tried an OMAP flash, but that did not change anything as well. The odd thing is that when I try to flash a new rom (I have tried stock and other custom roms) it flashes as if everything is fine, but when I reboot it still has the phandroid rom on it. Another odd note is that when phandroid boots it notifies me that I have an incoming text message, but I removed the SIM card over a month ago. I have been struggling with this and would love any thoughts or opinions anyone has to offer. Thanks a lot!
lsal25 said:
Hey guys,
I am having a similar issue with my Nexus. It is running Phandroid 3 and one day just locked up, rebooted, and shortly after reboot (15-30 sec. after the OS loads) it freezes. I can still boot into CWM recovery and into fastboot mode, and have tried to flash it with the stock rom and bootloader. I also tried an OMAP flash, but that did not change anything as well. The odd thing is that when I try to flash a new rom (I have tried stock and other custom roms) it flashes as if everything is fine, but when I reboot it still has the phandroid rom on it. Another odd note is that when phandroid boots it notifies me that I have an incoming text message, but I removed the SIM card over a month ago. I have been struggling with this and would love any thoughts or opinions anyone has to offer. Thanks a lot!
Click to expand...
Click to collapse
I dont know if you already did but try to wipe /system also and then flash a ROM.
Sent from my Galaxy Nexus using XDA Premium HD app
A very good friend of mine donated me his Kindle Fire; because he doesn't like it, and OS from Amazon in particular.
I've tried to root the kindle following this: http://forum.xda-developers.com/showthread.php?t=2074565; but the process always went with errors, reporting that some files do not exist. I am using NixOS at the moment and I haven't seen Windows since 2000, so please don't send me to Windows-only rooting.
After that, I tried to install 2nd bootloader/recovery, following the guide: http://forum.xda-developers.com/showthread.php?t=2100963; but something went wrong. I got blue fire logo, but it never booted and was stuck on the "loading" screen. I let the battery go flat; then charged from the wall charger and booted into normal mode - that went OK.
I am wondering if I have chosen wrong files or made a device identification error?
I know the kindle was bought from Amazon in November 2012 on promotional offer. The device information is the following: system version 10.4.6_user_4620220. Serial number D026 A0A0 2464 01LW.
Lilybet said:
A very good friend of mine donated me his Kindle Fire; because he doesn't like it, and OS from Amazon in particular.
I've tried to root the kindle following this: http://forum.xda-developers.com/showthread.php?t=2074565; but the process always went with errors, reporting that some files do not exist. I am using NixOS at the moment and I haven't seen Windows since 2000, so please don't send me to Windows-only rooting.
After that, I tried to install 2nd bootloader/recovery, following the guide: http://forum.xda-developers.com/showthread.php?t=2100963; but something went wrong. I got blue fire logo, but it never booted and was stuck on the "loading" screen. I let the battery go flat; then charged from the wall charger and booted into normal mode - that went OK.
I am wondering if I have chosen wrong files or made a device identification error?
I know the kindle was bought from Amazon in November 2012 on promotional offer. The device information is the following: system version 10.4.6_user_4620220. Serial number D026 A0A0 2464 01LW.
Click to expand...
Click to collapse
thats definately a kf2, if it got stuck on the blue logo then maybe you either didnt tell it to go into recovery or you forgot to flash a custom recovery. as long as you have the blue logo i believe you can get into fastboot without a fastboot cable and flash a custom recovery. Or try boting into it with the key combo for kf2 that i don't know of offhand.
stunts513 said:
thats definately a kf2, if it got stuck on the blue logo then maybe you either didnt tell it to go into recovery or you forgot to flash a custom recovery. as long as you have the blue logo i believe you can get into fastboot without a fastboot cable and flash a custom recovery. Or try boting into it with the key combo for kf2 that i don't know of offhand.
Click to expand...
Click to collapse
Thanks. Perhaps I made a mistake falshing recovery. Fixed now, TWRP works OK.
Now I am stuck with getting a working combination of ROM + GAPPS: Tried
1) cm-10.2-20131102-SNAPSHOT-M1-otter2.zip + gapps-jb-20130813-signed.zip --- get "unfortunately com.android.phone stopped".
2) cm-10.2-20131102-SNAPSHOT-M1-otter2.zip + gapps-jb-20130301-signed.zip --- get "unfortunately, android keyboard (AOSP) stopped" Clear data + clear cashe do not solve the problem.
3) cannot flash any cm-11 from download.cyanogenmod.org/?device=otter2&type=snapshot : get message set_metadata_recursive: some changes failed. E: Error executing updater binary in zip 'sdcard/cm-11*/ Error flashing zip 'cm-11-*'.
Something is telling me that TWRP v2.6.3.0 is not compatible with CM11 and Android KK. Is it correct?
Thus I need a working combination of CM10.? and JB GAPPS.
Tried this one early morning today: http://forum.xda-developers.com/showthread.php?t=2146030
Flashing was OK, but cannot boot afterwards: get a screen with rotating/flying triangles, nothing else.
Alright, the only combination with CM 10.2 that works at this moment for me is JB 4.3 with CM10.2/SGT7:
http://forum.xda-developers.com/showthread.php?t=2416561&nocache=1
The other threads seem to have links incompatible roms/gapps due to updates...
Not 100% sure of best place to post this, but I'm getting desperate now...
I'm pretty worried I've killed my device. After following the guide on how to root with Magisk, my phone is stuck on the white "loading" screen with a G logo. I've since tried to restart, but I can either go into fastboot mode or get the white screen when attempting to boot into android.
Tried to flash the latest factory image to fix it, but that couldn't get that to work. Now the phone isn't showing up on adb devices either. panicking a little bit here.
Does anyone know what to do?
ADB won't work unless the phone is booted into Android or in stock recovery for a sideload.
Does your computer recognize the device when you are in Fastboot mode and type "fastboot devices"? Try flashing the factory image again but make sure you have the most up to date platform tools from Google. Old versions are a common cause of issues.
Did you flash TWRP recovery or just boot to it to root? If you still have stock recovery you can try a factory reset from there but any modified images you installed might be the issue.
like Fury said, your platform tools need to be updated, same thing happened to me.
What didn't work when you flashed the factory image? Do you have the latest sdk tools version of fastboot and adb?
Sent from my [device_name] using XDA-Developers Legacy app
fury683 said:
ADB won't work unless the phone is booted into Android or in stock recovery for a sideload.
Does your computer recognize the device when you are in Fastboot mode and type "fastboot devices"? Try flashing the factory image again but make sure you have the most up to date platform tools from Google. Old versions are a common cause of issues.
Did you flash TWRP recovery or just boot to it to root? If you still have stock recovery you can try a factory reset from there but any modified images you installed might be the issue.
Click to expand...
Click to collapse
Thanks so much, this is where I was going wrong. Have gone into recovery and rescued it.
Tried the process again to get Magisk working, but ended up the same although this time the white screen only went on for a while before I got an error saying my data was corrupted. Tbh, after all the stress I'm just going to give up on this and live with the phone in stock. All my drivers and adb were installed and setup today, so everything is up to date.
edit...
Not out of the woods yet. After restarting the phone and going through the setup, it's not detecting the SIM card or any wifi networks. I've installed the OTA and wiped data once more after having this problem, still not resolved.
Nick676 said:
Thanks so much, this is where I was going wrong. Have gone into recovery and rescued it.
Tried the process again to get Magisk working, but ended up the same although this time the white screen only went on for a while before I got an error saying my data was corrupted. Tbh, after all the stress I'm just going to give up on this and live with the phone in stock. All my drivers and adb were installed and setup today, so everything is up to date.
Thanks again for helping.
Click to expand...
Click to collapse
It sounds like you are trying to install Magisk v17.1 like I tried. If so you need to use v17.3 beta. If you follow this thread you should be fine. It even tells you what to do for your original problem, just takes some reading and patience.
Misterxtc said:
It sounds like you are trying to install Magisk v17.1 like I tried. If so you need to use v17.3 beta. If you follow this thread you should be fine. It even tells you what to do for your original problem, just takes some reading and patience.
Click to expand...
Click to collapse
I tried it with both 17.1 and 17.3, so not sure what the issue is. Seem to have finally booted up properly with wifi and signal working, so hopefully it's all good now. Gonna give up on rooting.
Nick676 said:
Not 100% sure of best place to post this, but I'm getting desperate now...
I'm pretty worried I've killed my device. After following the guide on how to root with Magisk, my phone is stuck on the white "loading" screen with a G logo. I've since tried to restart, but I can either go into fastboot mode or get the white screen when attempting to boot into android.
Tried to flash the latest factory image to fix it, but that couldn't get that to work. Now the phone isn't showing up on adb devices either. panicking a little bit here.
Does anyone know what to do?
Click to expand...
Click to collapse
you may want to try to totally uninstalling Magisk frist with the official latest Magisk uninstaller and reboot and then do a complete factory reset. this has helped me in the past.
my new pixel 3XL will be the first Android phone that I owned that will not be rooted.
Hi everyone
After some research, I can't find a succeful way to install TWRP recovery instead of Lineage stock recovery.
It's really embarasing because I'm currently setting up my brand new XZ2c compact to run the way I want it to on Lineage OS 17.1 with Magisk and Xposed modules, and I experienced 3 or 4 endless bootloop that led me to fully format my phone after bunch of hours setting it and tailoring it up... Huge waste of time, frustration overload, as you could expect. So, I really miss tremendous TWRP backup fonctionnality I used to run frequently on my old Z5c... :crying:
Does anyone here as figured out how to replace Lineage stock recovery on this device? Is so, I'd really to hear him out
Have a good week-end!
tomboudiboudi said:
Hi everyone
After some research, I can't find a succeful way to install TWRP recovery instead of Lineage stock recovery.
It's really embarasing because I'm currently setting up my brand new XZ2c compact to run the way I want it to on Lineage OS 17.1 with Magisk and Xposed modules, and I experienced 3 or 4 endless bootloop that led me to fully format my phone after bunch of hours setting it and tailoring it up... Huge waste of time, frustration overload, as you could expect. So, I really miss tremendous TWRP backup fonctionnality I used to run frequently on my old Z5c... :crying:
Does anyone here as figured out how to replace Lineage stock recovery on this device? Is so, I'd really to hear him out
Have a good week-end!
Click to expand...
Click to collapse
You don't install a recovery, but only temporally boot one
https://wiki.lineageos.org/devices/xz2c/install
kurtn said:
You don't install a recovery, but only temporally boot one
https://wiki.lineageos.org/devices/xz2c/install
Click to expand...
Click to collapse
Thanks for replying!
Ok, but if I want this recovery bootable permently away from my computer?
kurtn said:
You don't install a recovery, but only temporally boot one
https://wiki.lineageos.org/devices/xz2c/install
Click to expand...
Click to collapse
Thanks for your (minimalist) advice. Literally just lost 1 hour fixing the bootloop it just caused by following it, I'm delighted.
Behind my post, I was hoping to find someone who could explain a bit more the process of replacing/flashing/booting/(wateveryouwanti'mnotanexpert) a recovery, and at the same time avoiding me wasting more hours in bootlooping/formating/reinstalling. Hopefully, this time I succeed to came out of the bootloop without formating and reseting eveything, but I almost lost my nerves.
All of this is a bit cloudy for me, could you (or someone else that would give me a little of his time to) be pedagogue and explain clearly the whole proccess (and especially what you should avoid if you don't want to get stuck in a bootloop/getting scarying corrupted device message) ?
No one?
tomboudiboudi said:
No one?
Click to expand...
Click to collapse
Wrong forum. Search in you device section.
Hi guys!
Today I tried again to install TWRP on my Sonyh Xperia XZ2C because LineageOS Recovery doesn't provide Nandroid backup, which is a shame.
I tried many ways described over the web, none of those worked, and I ended up with a boot loop at startup with that naughty message "your device is corrupted it cannot be trusted and will not boot". I can't boot to Lineage, neither to recovery. I'm stuck.
With device turned off, I can eventually press volume down, plug it to computer, access fastboot mode (blue led), flash+boot the LineageOSrecovery.img, then the device restart, Sony logo appears... and that's all, I'm stuck with logo in boot loop, and I can't go anywhere further.
I tried to change boot slot (without knowing if it could help with this problem at all) but I alway get "unknown option".
I'm panicking right now, I can't find any way out to this bootloop, if someone could help it will be sooo appreciated!
I tried hard to find a solution for 4 hours now, I'm completly stuck and I can't even sleep. That's why I finally reached out here.
tomboudiboudi said:
Hi guys!
Today I tried again to install TWRP on my Sonyh Xperia XZ2C because LineageOS Recovery doesn't provide Nandroid backup, which is a shame.
I tried many ways described over the web, none of those worked, and I ended up with a boot loop at startup with that naughty message "your device is corrupted it cannot be trusted and will not boot". I can't boot to Lineage, neither to recovery. I'm stuck.
With device turned off, I can eventually press volume down, plug it to computer, access fastboot mode (blue led), flash+boot the LineageOSrecovery.img, then the device restart, Sony logo appears... and that's all, I'm stuck with logo in boot loop, and I can't go anywhere further.
I tried to change boot slot (without knowing if it could help with this problem at all) but I alway get "unknown option".
I'm panicking right now, I can't find any way out to this bootloop, if someone could help it will be sooo appreciated!
I tried hard to find a solution for 4 hours now, I'm completly stuck and I can't even sleep. That's why I finally reached out here.
Click to expand...
Click to collapse
In fastboot mode you should be able to flash stock rom
Is there any way to make the device boot on the Lineage partition without wiping everything?
For an unknown reason, I succed to boot on Lineage Recovery (not TWRP) this morning. I flashed LineageOs rom.zip using adb sideload. After rebooting, the recovery tolds me that I had to wipe everything because the system partition seems to be corrupted, so I did.
I'm a bit tired to lost everything since I made all of this to do Nandroid backups with TWRP........ but I have a fresh new install, my phone works again so it's fine.
But I still need to make Nandroid backups.
Kurtn, you seem to have skills and knowledge. As you can see, I didn't succeed to boot Twrp since october 2020. I don't see why it would be impossible with my device, I'm probably messing something somewhere.
Would you share your knowledge and help me booting/flashing TWRP without bricking everything again?
Could you make an answer instead of a single smiley?
tomboudiboudi said:
Could you make an answer instead of a single smiley?
Click to expand...
Click to collapse
Sorry, i cant. I don't backup and I don't have an a/b device.
Ok, thanks anyway!
tomboudiboudi said:
I didn't succeed to boot Twrp since october 2020. I don't see why it would be impossible with my device, I'm probably messing something somewhere.
Would you share your knowledge and help me booting/flashing TWRP without bricking everything again?
Click to expand...
Click to collapse
Btw.
Code:
fastboot flash boot recovery.img
DOES install the recovery, since it's permanently flashed. Don't know why they (lineage) didn't change that.
kurtn said:
You don't install a recovery, but only temporally boot one
https://wiki.lineageos.org/devices/xz2c/install
Click to expand...
Click to collapse
However @tomboudiboudi , you could boot twrp manually using
Code:
fastboot boot twrp.img
With that, twrp should appear and ask for a password to decrypt your userdata partition.
If that works, you could try to flash boot this very same twrp.img. Maybe you need an additional twrp.zip too which will be sideloaded within twrp itself.
A note for you which might help: I wanted to update my lineage recovery manually using fastboot (older lineage recovery to newer one) and found that nothing (except fastboot) was booting at all after flashing this.
However, after dirty flashing lineageOS.zip, everything worked fine again.
Keep in mind that flashing a recovery will modify your boot.img. If this one doesn't work / is corrupt etc., your os won't boot up.
User699 said:
Btw.
Code:
fastboot flash boot recovery.img
DOES install the recovery, since it's permanently flashed. Don't know why they (lineage) didn't change that.
However @tomboudiboudi , you could boot twrp manually using
Code:
fastboot boot twrp.img
With that, twrp should appear and ask for a password to decrypt your userdata partition.
If that works, you could try to flash boot this very same twrp.img. Maybe you need an additional twrp.zip too which will be sideloaded within twrp itself.
A note for you which might help: I wanted to update my lineage recovery manually using fastboot (older lineage recovery to newer one) and found that nothing (except fastboot) was booting at all after flashing this.
However, after dirty flashing lineageOS.zip, everything worked fine again.
Keep in mind that flashing a recovery will modify your boot.img. If this one doesn't work / is corrupt etc., your os won't boot up.
Click to expand...
Click to collapse
I fear you still haven't realized, what a/b means. The classic concept of having a recovery partition, where you can boot twrp at any time - doesn't apply.
kurtn said:
I fear you still haven't realized, what a/b means. The classic concept of having a recovery partition, where you can boot twrp at any time - doesn't apply.
Click to expand...
Click to collapse
You're right, there is no recovery partition.
As I said: Flashing a recovery.img will modify the boot.img.
Hi all,
I'm coming back to Android after an absence and would like to run Lineage on a new US unlocked 9P. I followed the directions in the Lineage OS website and unfortunately the phone now is stuck in a constant animation of the blue circle moving left over the arc, and there isn't much I think I will be able to do about it until the battery runs out.
Here's what I did as per the directions:
-got and installed adb and fastboot from the Windows zips from Google
-added the install location to the path enviro variable
-installed the Universal ADB driver from Github
-activated USB debugging and OEM unlocking on the phone
-got the phone repeatedly into fastboot mode but then got stuck since 'fastboot devices' didn't show anything
-got bailed out by another thread here that one needs to check for updates with phone connected and Win will download the relevant USB drivers. Thanks!
-unlocked the bootloader
-downloaded and flashed the 18.1-20210803 recovery img
-sideloaded the copy-partitions 20210323 zip and it got stuck at 47% just like the website said
-did the factory reset
-sideloaded the the LOS 2020210803 zip to the phone and rebooted
When I rebooted it just plays the animation I mentioned at the beginning, so it looks like it's stuck in a permaloop.
I should mentioned that after I flashed recovery and booted into the normal Oxygen mode it would take much longer to boot so perhaps there was something already creating the loop.
I am grateful for any assistance.
Thanks,
How long have you left it? First install of Lineage spins for ages
I think I left it for an hour or so. Thanks for the info - I just turned it on and will let it spin for a while and see what happens.
I let it run until the battery died. I fully recharged it and am letting it run again. Same result of blue circle tracing arc to the left.
Success!
I tried to install the prior version (0720) which was then rejected for being too old. I wiped the storage and then tried 0803 again and it installed. I turned it on, the circle moved for a while and then the Lineage logo came up. I just finished setup, and it looks beautiful.
So far so good!
lexcimer said:
Success!
I tried to install the prior version (0720) which was then rejected for being too old. I wiped the storage and then tried 0803 again and it installed. I turned it on, the circle moved for a while and then the Lineage logo came up. I just finished setup, and it looks beautiful.
So far so good!
Click to expand...
Click to collapse
Everytime you flash a new rom you need to wipe data after
Anytime that happens you just go back into recovery and wipe data a few times and it should work after that.
It would've been due to encryption. Each time you flash a new rom you need to wipe userdata which removes your lock and also removes encryption. If you try to install a rom without doing this first, the rom cannot access that partition, because it doesn't yet know the unlock code/pattern, which is why it just gets stuck trying to do so.
Thank you to the 3 posters above, and I appreciate DJ Sub's explanation, makes sense in hindsight and I'll keep it in mind for the future.
PS - I'm glad to be back to the Android modding community, it's refreshing to be able to steer what OS my phone is running
I had the same problem (also a couple of different boot loop problems) when flashing LineageOS.
I did many things, so can't say for sure which one helped me to fix that, but the things I did were:
Restore from boot loop via MSM tool flashing EU image.
Updating that OxygeneOS to the latest using internal updater.
Repeating the LOS installation process several times in different conditions to isolate the source of the problem. I was changing LineageOS package, OpenGapps package, etc.
One of the problems I've found was that latest OpenGapps package (July 28th if I'm correct) was causing the boot loop on first start (very similar to what you're describing):
Phone tries to boot showing the LOS animation.
It goes for several minutes.
Then the phone vibrates, reboots and it continues from the start.
If I'm not mistaken, it was fixed by using the version from July 24th. The latest package also were removed from the OpenGapps page later AFAIR.
Second problem was after the successful boot. The phone was rebooting from the first setup wizard, booting to recovery (or some other partition) and proposing to make a factory reset.
Not sure which of my steps solved this, but I was updating back to the last LOS package watching closely that I'm flashing the same slot on each step and also making sure that slots are properly copied from one to another with the corresponding script.
Even in the most stable setup I was probably having some setup wizard loop problems, so I was skipping account setup steps and doing that manually later.
I'd say that installing LOS on OnePlus 9 Pro was most difficult and problematic installation in my experience and I did that a lot previously: HTC Wildfire S, THL 5000, Zuk Z1, Xiaomi Mi 5s, Xiaomi Mi 9T (Redmi K20) and several other devices.