I flashed CM ROM today to try and see what progress has been made. I decided to return to the stock ROM. Flashed the stock ROM and wiped everything except system partition. Rebooted the phone and it is resetting itself at the first logo now. The second stage of boot (animated logo) doesn't initiate.
Download and Recovery modes work. Flashing the stock firmware with both Odin and Smart Switch didn't fix the problem. I tried PIT file and NAND Erase with a no go. Any help would be appreciated.
Edit: After spending some time trying, I realized I can only boot CM. Maybe CM caused this problem or the Gapps package I have been using. I am not sure. I'll be happy if anyone can help me fix this problem.
just flash cm12.1 (clean install without gapps ) do not let device boot just flash and then flash any rom you like it (dirty flash )
sorry for bad english
osamaAlrogi said:
just flash cm12.1 (clean install without gapps ) do not let device boot just flash and then flash any rom you like it (dirty flash )
sorry for bad english
Click to expand...
Click to collapse
this doesnt work mate
I have tried about 4 different zips of the unofficial CM 13 builds, and they always get stuck at "Patching system image unconditionally".
I did the process to root it, flash two, and now I'm here. It doesn't give any errors, just sits forever, upwards of an hour.
I've erased everything, but no difference.
Which recovery are you using?
Like the title says, my phone gets stuck at the boot logo (not bootloader) after I try to flash any custom ROM to which I solve by restoring to a stock rooted nandroid backup of 6.0.
Here's my flash process:
1. Reboot to TWRP
2. Do clean wipe
3. Flash ROM (DU for example)
4. Flash gapps
5. Reboot
TWRP flashes the ROMs and necessary gapps without any issues but no matter what it gets stuck at the boot logo after rebooting. This wasn't a problem in the past as I was using Orion, DU, AICP, etc. Would using the restore-to-stock tool help in this case? The only thing stopping me from using it is the fact that it would wipe my internal storage. Any help would be greatly appreciated. Thanks!
EDIT: I decided to restore to stock and wipe user data and I'm now finally able to get past the the boot logo
How long are you waiting? First boot can exceed 20 minutes just sitting there looking like it's not doing anything...
Sometimes first boot take.more than half an hour
Sorry to revive this but Im getting the same problem... Did u managed to install any rom after u flash the stock rom? Should I do that? How long should I wait on first boot?
Just thought I would tell everybody about my experience. Be careful when flashing ROMs. I was on marshmallow 3.1.1 xdabbebs. On a vs985 by the way. Anyway tried to Flash Jasmine 9.0 again with the 9.1 update...did everything correctly...wipe dalvik cache cache data system...then went on to Flash 35b bootstack...from there flashed Jasmine along with the update then the moderate debloat zip...after that did a factory reset...THEN when I went to reboot the screen was black...no logo no both in but odd thing was I could hear that it was booted...black screen of death...attempted to get into download mode to do a tot back to 10b not ring able to see anything on the phone...tried to Flash and failed every time. So...I tried the kdz method...numerous fails...for 20 minutes...out of nowhere phone vibrates and kicks on...I go to settings and somehow it took the 24b file...don't know how...anyways I tried to tot from there...to 10b...fail fail fail...then I tried the one click root method...nope didn't work...so I did king root...that worked...I then did the autorec twrp method...it flashed it...I then installed twrp manager to get the latest recovery...I flashed that...that seemed good...went to reboot to recovery...I got a security error message...I pulled battery and tried to reboot...same message every time...I then did the power and volume down and managed to get into recovery...thank God...LUCKILY I had a backup of xdabbeb 3.1.1 Rom...restored and I'm back up and running...lol...I think my Rom flashing days are over...lol...anyway...careful guys
matt1285 said:
Just thought I would tell everybody about my experience. Be careful when flashing ROMs. I was on marshmallow 3.1.1 xdabbebs. On a vs985 by the way. Anyway tried to Flash Jasmine 9.0 again with the 9.1 update...did everything correctly...wipe dalvik cache cache data system...then went on to Flash 35b bootstack...from there flashed Jasmine along with the update then the moderate debloat zip...after that did a factory reset...THEN when I went to reboot the screen was black...no logo no both in but odd thing was I could hear that it was booted...black screen of death...attempted to get into download mode to do a tot back to 10b not ring able to see anything on the phone...tried to Flash and failed every time. So...I tried the kdz method...numerous fails...for 20 minutes...out of nowhere phone vibrates and kicks on...I go to settings and somehow it took the 24b file...don't know how...anyways I tried to tot from there...to 10b...fail fail fail...then I tried the one click root method...nope didn't work...so I did king root...that worked...I then did the autorec twrp method...it flashed it...I then installed twrp manager to get the latest recovery...I flashed that...that seemed good...went to reboot to recovery...I got a security error message...I pulled battery and tried to reboot...same message every time...I then did the power and volume down and managed to get into recovery...thank God...LUCKILY I had a backup of xdabbeb 3.1.1 Rom...restored and I'm back up and running...lol...I think my Rom flashing days are over...lol...anyway...careful guys
Click to expand...
Click to collapse
After getting Secure boot error you could have flashed Mr.bump.
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