Hi guys, been using my rooted but otherwise stock OOS rom with TWRP and Magisk for the past few weeks. Today I decided to take the plunge and try either the Lineage OS or Resurrection Remix roms.
I'm using the latest OFFICIAL TWRP.
So I decrypted following the instructions to flash "no-verity-opt-encrypt-5.1.zip", then format data. All went well, so I then sent over the ROMS I wanted to try out. I started with the official ResurrectionRemix. Bootloop. Then the unofficial LineageOS. Bootloop.
Ok, well I guess I'm not gonna get to use any of the cool new OS's for awhile. I'll install the full stock firmware zip so I can have a working phone again. Bootloop.
Now when I say bootloop, the phone is booting to the BootAnimation and just repeating it. It shows the proper boot animation for whatever zip I have installed (resurrection/LOS/OOS), but it stays on there for up to 20 minutes before I have to hard reboot to the recovery again.
I decided to install the stock recovery trying a few methods. I first tried the ALL-IN-ONE tool. It said it flashed the recovery fine, so I booted to the recovery and after staying on a black screen for too long, the language options came up and I sighed a breath of relief. But before I could select English with the volume buttons, it rebooted by itself. It did this again when I manually entered recovery. So I figured maybe the tool flashed the wrong version, so I googled stock recovery for OnePlus 5, I found a few random links for stock recoveries for the OP5 and flashed them, but they more or less do the same thing or not boot at all.
I've tried changing the filesystem for both Data and System using any combinations of EXT4 and F2FS. Everything results in boot animation bootloops.
I have been flashing Roms since the Samsung Galaxy S3 and every phone since and never had any problems.
Currently when trying to install the stock Full OOS official zip with TWRP, the phone won't even go to the boot animation, it only goes to a black screen with the top LED in a light blue color.
I have also tried every version of TWRP there is for the OnePlus 5. Unofficial, Official, 3.1.1-0 and 3.1.1-1.
So I guess my question is....What filesystem is each partition supposed to be on and for which OS?
Lineage based:
System: ?
Data: ?
OOS Based:
System: ?
Data: ?
And any ideas on getting my phone running again?
And anyone have an official confirmed working version of the stock recovery? The one from ALL-IN-ONE TOOL doesn't work for me. It loads the language selection, then the screen goes black with a light blue LED on the top of the phone.
Actually I'm getting that on some roms instead of the bootanimation, like FreedomOOS. What does it mean when you have a black screen and a white LED?
Man, I really thought I was getting somewhere. If I boot into TWRP, change the Data partition to "F2FS", then flash the stock recovery, the stock recovery will boot, however, when inside the stock recovery and I try to flash the stock zip, it says "Flashing, don't turn off your device" for about 5 seconds and then goes back to the list of roms on the SD card, not having flashed anything at all.
Ok, I have the official stock recovery from the OnePlus site, but still can't use it. Here is was happens depending on how I left it with TWRP:
System: F2FS
DATA: F2FS
- Stock recovery will load after some time, freeze, then the screen goes black with white LED on top.
System: EXT4
DATA: F2FS
- Stock recovery loads fine, I can go through the settings and install from SD card, but when I do it says "Flashing, don't turn off your device" for about 5 seconds and then goes back to the list of roms on the SD card, not having flashed anything at all.
System: EXT4
DATA: F2FS
- If I try to flash stock rom through TWRP, it just boot loops on the animation forever.
I have now also tried flashing the stock boot.img, but no difference.
I have 2 things you can try!
First, replace the bootloader with stock and do a factory reset:
1. flash the stock recovery over
2. then in fastboot mode enter, fastboot oem lock (This forces the phone to wipe cache and data, and also do a complete reset)
Did it work? if yes YAY if not go to Second!
Second if your system.img is ****ed up you have to replace it!
Download the newest version of the stock rom from oneplus link here
Unpack it
research how to use an extractor to convert the system.new.dat to system.img
once thats completed enter fastboot mode and flash the new system.img over with Fastboot flash system system.img
now go into recovery and do a factory reset and wipe cache, and dalvik
Please reply back wether or not this work
"Ihave 2 things you can try! First, replace the bootloader with stock and do a factory reset..."
Is the bootloader simply the boot.img?
After doing the first thing, it simply says that the device is corrupt and will not boot. But it is locked again.
But I will have to unlock it again to do any further flashing.
Hmm, I think I may have gotten it. After unlocking again, flashing the stock recovery and boot.img, then locking again and wiping in the stock recovery, I have finally booted into the stock rom.
I still have no idea what went wrong, and I really want to know, so that in the future I can flash other Roms, like LineageOS.
I mean, I followed the steps exactly.
If it says the device is corrupt it simply means you got something else besides stock rom.
So now unlock it and try the system.img instead
It was because I still had TWRP with the stock rom.
I got it working though, thanks for your help.
Do you have any idea on what might have went wrong when trying to flash the lineageOS based roms and why it got messed up so royally?
Great to hear you fixed it ^_^
Probably some minor bug, if you wanna try installing lineageos again use the 3.1.1 TWRP build that supports backups and do a full backup so you don't have to go thru all this again
---------- Post added at 12:17 AM ---------- Previous post was at 12:13 AM ----------
Not really just try again but remember to use TWRP 3.1.1, as 3.1.0 don't support backup and probably have been part of your problem
If your trying again and gets it successfully installed could you do me a favor and test if Drivedroid works on it? And pm me the result, I'm looking for a rom where Drivedroid will work... Haven't found one so far
You know, I did do a backup with the OFFICIAL TWRP, but it also resulted in a bootloop. I made the backup after decrypting, so I don't know why it bootlopped.
https://forum.xda-developers.com/oneplus-5/development/rom-unified-lineageos-7-1-2-t3635483
Is this the one you tried installing?
I tried like every ROM at one point yesterday, but I think I started with
https://forum.xda-developers.com/oneplus-5/development/rom-resurrection-remix-n-7-1-2-t3636578
Did you remember Gapps?
Also in some cases its better not to root before you have the custom rom running, you usually only need a custom bootloader like TWRP
Yeah, I tried with Gapps, and I never rooted before first trying to boot.
As of yesterday Ressurrection remix, released the first official stable build so try again your should'nt have any problems if you follow the guide 100%
Ever find a solution? I'm stuck here now. Can't get any ROM to boot up, they all get stuck on the boot animation
Bump. I am also stuck in this state
I installed TWRP 3.1.1 using the ODIN patched version and was successful. I had let the system boot into the samsung original stock from where you see "HI" then I rebooted it into TWRP to attempt flashing and I got the /data partition couldn't be wiped. So I ran some of the other repair functions in TWRP and that appear to have fixed it. I then flashed with the latest LineageOS, Gsap, and Magistk20. When it boots up the LineageOS I'm stuck on the Lineage Splash screen. I've let it run over night and it has't changed anything. Any advice?
I recommend trying to wipe the system and reinstall LineageOS with flashing Magisk. If the same problem occurs. Just wipe the system and flash LineageOS without installing Magisk.
secretwolf98 said:
I recommend trying to wipe the system and reinstall LineageOS with flashing Magisk. If the same problem occurs. Just wipe the system and flash LineageOS without installing Magisk.
Click to expand...
Click to collapse
Here's how I think I fixed it.
booted into TWRP
advanced wipe, Factory reset
booted it into TWRP
Flashed the LineageOS
boot into LineageOS
boot it into TWRP
flashed the Gapps.
I'm up and running now. I tried different iterations and It really bothered me because it worked fine on another one. I was also at time flashing it with SuperSU and other times with Magisk. It didn't matter which one I used it got stuck on the LineageOS splash screen.
dizzymon said:
Here's how I think I fixed it.
booted into TWRP
advanced wipe, Factory reset
booted it into TWRP
Flashed the LineageOS
boot into LineageOS
boot it into TWRP
flashed the Gapps.
I'm up and running now. I tried different iterations and It really bothered me because it worked fine on another one. I was also at time flashing it with SuperSU and other times with Magisk. It didn't matter which one I used it got stuck on the LineageOS splash screen.
Click to expand...
Click to collapse
By the way, it's called the boot animation. The splash screen is like the Samsung screen that says powered by Android.
Possible corrupted file
secretwolf98 said:
By the way, it's called the boot animation. The splash screen is like the Samsung screen that says powered by Android.
Click to expand...
Click to collapse
So far you're quite correct I personally have three SM-T580's and they all seem to work just a little bit different. Might I suggest doing an MD5 Sumcheck? The device shouldn't be getting into a bootloop unless there was something wrong with the files, or the device.
Hi,
I used Lineage OS 17.1 Lavender on my Xiaomi Redmi Note 7. I used their recovery to install the ROM and open gapps. Recently I downloaded the Brave Browser and I wanted to enable rewards. I than googled, that Brave doesn't allow rewards on rooted phones. I decided to wipe the entire phone, since I don't use the root functionality and to re-flash Lineage OS 17.1. I factory reseted the phone and wiped everything, just like I did, when I installed Lineage for the first time. I clicked on "Yes" when prompted that the ISO couldn't be verified, and waited for the flash. After a while I was "greeted" with Updater process ended with Error 7. I did some research and found out that it is something to do with the updater file verification and that I should try and delete some lines. I did that, but the error persisted. I than decided to try another ROM. I used Pixel Experience since it was working on my device before. Unfortunatly I had no luck. Same error message. I than tried to flash TWRP with fastboot, which worked. Wiped my device, just like they say it in all the guides (Dalvik, Data, Cache) and tried to flash Lineage (still no luck), than PixelExperience (still no luck) and Magisk worked. After I flashed Magisk I tried Lineage and Pixel once again, but still the same error.
If you know, how to fix that error I will be so glad. Is it possible that my device is bricked and beyond recovery? Thank you in advance.
update your tvvrp
Which firmware do you have installed? Use stable to maximum compatibility, on some ROMs if you have latest you gonna get that error. Also, use the latest TWRP or Orange Fox.
As Tatoh said, this error occurs when you have old firmware flashed on your RN7, some roms require specific version but usually flashing latest stable will give you best compatibility, here you have xda links to latest xiaomi firmware files: https://forum.xda-developers.com/redmi-note-7/development/firmware-xiaomi-redmi-note-7-t3925871
I wanted to upload a new rom to my phone (pine, 16GB), but it will never boot. Always after rebooting, TWRP will be loaded again. I'm tried multiple ROMs (LineageOS, DotOS, MokeeOS ), but the problem occurs for all rom. TWRP says, flash succed for every one system, but not booting after reboot.
I'm used twrp-3.5.0_9-20210101-pine-arm64 version. Only I can do flash a stock rom using MiFlash, but no custom rom via TWRP.
Mi device is correctly unlocked via Official Unlock Tool app.
Can you tell me why?
Thanks
Maybe try another twrp version or another completely like OrangeFox can't really tell you why i don't have as much knowledge in why or how it works but i have tried a lot on mine so this should be ur first troubleshooting step from my point of view also have you flashed the ROMs with their instructions some say the sequence you should format or wipe ur data etc...
Working for now,
The problem was that I didn't choose to Format data
This phone has had a number of previous installs of ResurrectionRemix (2019), LineageOS 18.1 different versions and there has not been any problems to install custom ROMS. Just recently, after recharging the phone, the phone would not boot. Kept hanging on the LOS boot animation. I have reverted to Stock ROM successfully, and after that tried several LOS reinstalls with the recovery bootloader (either TWRP or LineageOS's own) but every time the LOS install starts hanging on the boot animation. Timeout. And I am trying to reinstall same versions that have been working before. Total mystery. How do I get a working LOS back on the phone? Strange thing is that a ResurrectionRemix install seems to work. No hanging at boot there at least.
What is causing this peculiar error? NB: I have never used any apps like Magisk or similar.
BR /Johan
try it with twrp
I have tried with TWRP running from 3.3.0+ up to 3.6+ . No difference here. It feels like the LOS installation is missing something. A partition or what not. adb logcat does not work when I boot so I can't see what's going on during boot, but I can use adb with the LOS recovery to look for things .
Update: Finally got the boot logging to work. It turns out that my fingerprint sensor is dead, and LOS gets into a bootloop when it tries to access it via HAL(?!). I am no expert on debugging - thanks to guys over at #lineageos. But it is worth noting that LOS might get into a boot loop if the fingerprint sensor is dead for some reason, be it an electrical failure of some kind or firmware issue.