I unlocked my bootloader awhile back when the exploit first came to light and have been enjoying it mostly problem free since.
I've been using CWM with CM10.1 for the most part but the issues I was having with CM were finally getting to me so I thought I'd just try a debloated stock ROM, and thought it was a good time to try out TWRP while I was clearing everything out.
So I loaded up Matt's tool and flashed the stock ROM back (because for some reason my computer doesn't like to recognize CM over USB), no problems there. At the suggestion of the tool I also flashed the stock recovery (since I intended to flash TWRP I figured it was a good idea). Here's where my problem lies now: The phone boots fine back into stock ROM and I can get back into fastboot no problem but if I try to get into recovery (after flashing stock, CM or TWRP) I only get the opened up Android with the red triangle/exclamation.
Is there some step I need to take that I'm not?
I boot into fastboot and flash recovery (stock). Boot normally wait a couple min (skip setting up accounts, etc) then flash the custom recovery but I seem to end up back at the broken android every time.
EDIT: I might just be an idiot. I completely forgot to root the stock ROM before trying to put the custom recovery back.
Broken android is stock recovery...
Sent from my XT907 using Tapatalk 4
I recently got a nexus 7 2012. I unlocked it and installed the custom recovery (CWM) according to the guides given in the forum and elsewhere. The problem comes when I install a custom ROM like CM10.2, It installs fine, but the boot does not resume after the CM animation. I tried another rom like AOKP and even TWRP as recovery, still the problem persists. My bootloader is 4.23 and flashing back to stock ROM works as normal. Please help.
What recovery you use. And what tool you use to root. For I use WUG toolkit. And install TWRP. And install CM 10.2 with no problem. Maybe you not really root. Update your superuser before that
Sent from my Nexus 7 using XDA Premium 4 mobile app
Stupid question: are you sure you are flashing grouper ROMs?
Tried a lot of combinations with ROMs and recoveries finally I solved it. CWM wasn't working with its wipe options and tried TWRP and gave the full wipe of all partitions before flashing CM and gapps and it worked!!!!
Anyone else getting bootloops on all custom Roms I unlocked the bootloader and installed twrp latest version though wugs nexus program and I have rooted stock with custom kernel which works fine but is missing a few features I would like to have so I try factory reseting and installing for example chroma or minimal and they both bootloop on fresh install not sure what I'm doing wrong even tried cm13 and same thing but if I flash stock rooted it works fine like normal never had this problem on nexus 5. Any help would be much appreciated.
Did you flash vendor?
Sent from my Nexus 6P using Tapatalk
Ovrclck said:
Did you flash vendor?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Not sure what you mean like Rom from google direct?
Ovrclck said:
Did you flash vendor?
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Not sure that would be an issue, I ran a ROM with an outdated vendor and all that happened was I'd get a popup reminding me that it was out of date
Chief_runningwater said:
Anyone else getting bootloops on all custom Roms I unlocked the bootloader and installed twrp latest version though wugs nexus program and I have rooted stock with custom kernel which works fine but is missing a few features I would like to have so I try factory reseting and installing for example chroma or minimal and they both bootloop on fresh install not sure what I'm doing wrong even tried cm13 and same thing but if I flash stock rooted it works fine like normal never had this problem on nexus 5.
Click to expand...
Click to collapse
WOW! What a sentence! :silly:
Chief_runningwater said:
Anyone else getting bootloops on all custom Roms I unlocked the bootloader and installed twrp latest version though wugs nexus program and I have rooted stock with custom kernel which works fine but is missing a few features I would like to have so I try factory reseting and installing for example chroma or minimal and they both bootloop on fresh install not sure what I'm doing wrong even tried cm13 and same thing but if I flash stock rooted it works fine like normal never had this problem on nexus 5. Any help would be much appreciated.
Click to expand...
Click to collapse
I'm having the same problem as you. No matter what I end up bootlooping at the rom splash screen eventually. Even after the rom appears to be doing well.
dirtyreturn said:
I'm having the same problem as you. No matter what I end up bootlooping at the rom splash screen eventually. Even after the rom appears to be doing well.
Click to expand...
Click to collapse
Most likely a vendor issue. I had the same. Most roms are fine with the stock Google vendor, except for SinLess rom (which I use) that has its own vendor file. Its a new thing that came with the 6P and 5X I believe.
If you're on stock already and you have the factory image from Google, extract it, you'll find the flashall script with another zip file containing system and other images. If you're fine with flashing over, run the script. If not just extract the second file, you'll get the system, boot, cache.. imgs as well as vendor.img
Code:
fastboot flash vendor vendor.img
Dissmeister said:
Most likely a vendor issue. I had the same. Most roms are fine with the stock Google vendor, except for SinLess rom (which I use) that has its own vendor file. Its a new thing that came with the 6P and 5X I believe.
If you're on stock already and you have the factory image from Google, extract it, you'll find the flashall script with another zip file containing system and other images. If you're fine with flashing over, run the script. If not just extract the second file, you'll get the system, boot, cache.. imgs as well as vendor.img
Code:
fastboot flash vendor vendor.img
Click to expand...
Click to collapse
Must we flash the vendor.img after every rom?
dirtyreturn said:
Must we flash the vendor.img after every rom?
Click to expand...
Click to collapse
Nope, once, and you should be good. Unless you somehow managed to erase it in recovery or something. If you see a bootloop again, you know what to do. Its just another partition like system, cache, recovery..
Like I said, only some roms require you to flash their own vendor images. From what I know so far, SinLess and PureNexus.
I'd try a stock rom with the stock vendor first, if I were you, just to get things running. Then flash a custom rom.
Dissmeister said:
Nope, once, and you should be good. Unless you somehow managed to erase it in recovery or something. If you see a bootloop again, you know what to do. Its just another partition like system, cache, recovery..
Like I said, only some roms require you to flash their own vendor images. From what I know so far, SinLess and PureNexus.
I'd try a stock rom with the stock vendor first, if I were you, just to get things running. Then flash a custom rom.
Click to expand...
Click to collapse
Slight correction, aside from screwing over with the actual partitions being the cause, it's mandatory for every major android update from google (e.g. 6.0 --> 6.0.1) if you want to update your rom to the following android version (For just nexus as far as i'm aware).
The images that needs to be flashed when updating are radio, vendor, boot and bootloader. (Unless stated otherwise by the developer of the rom you wanna use)
Sent from my Nexus 6P using Tapatalk
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
Hey y'all, I've been away from the development community and tinkering with this device, work and life got in the way. I've been running a custom rom (sky dragon) and I believe it's based off 9.013 Android for over a year now. It's a great custom rom but it's time for something different.
I'd like to flash the latest and greatest stock oxygen OS which is now Android v10. Being a longtime pixel user, I'm very comfortable updating via fastboot. I was wondering if I downloaded the full ROM from oneplus' website and used the flash-all. bat method if that would be a smooth way to cleanflash the device. I'll make sure to back up everything I need so wiping the device entirely is no issue.
Thanks!
I personally prefer the Fastboot ROMs it will do both slots at once.
OhioYJ said:
I personally prefer the Fastboot ROMs it will do both slots at once.
Click to expand...
Click to collapse
can I flash the latest stock fastboot ROM coming from Android 9 though?
You'll have to choose reset everything option in the factory recovery for it to boot (under advanced IIRC) to get it to boot. Otherwise it will most likely just keep booting to recovery. Thats what happens when you go from a custom ROM to a OOS too.
OhioYJ said:
You'll have to choose reset everything option in the factory recovery for it to boot (under advanced IIRC) to get it to boot. Otherwise it will most likely just keep booting to recovery. Thats what happens when you go from a custom ROM to a OOS too.
Click to expand...
Click to collapse
I figured it wouldn't be a smooth process!!! So if I fastboot flash the latest Android 10 build from a custom Android 9, I'll boot loop into recovery but choosing "reset everything" should allow me to boot into the OS? I'll give it a shot! thanks.