Database Users

Flashing won't work unless I wipe data

UPDATE: After completely wiping everything(recovery, ROM, bootloader, etc), and putting it back in with fastboot I no longer have this problem. My recovery probably just got corrupted or something while getting sent over to the device.
Got my Nexus 7 3 days ago, had it unlocked and all that jazz within the hour(thanks to the people who put the stuff together). It's great, but I have a problem with flashing .zip files in recovery. It doesn't matter what type of thing I'm wanting to flash(ex-kernel,rom, or even the uber-simple 720p camera mod), if I don't do a full wipe before flashing, then it just ends up boot looping my device. The boot loop doesn't turn the phone all the way off, just the boot animation. Sometimes the launcher will pop up for half a second and then go back to the boot animation.
For example, whenever I flashed the rasbeanjelly rom, I first flashed that, then rebooted(got excited and forgot about gapps) and checked it out. Remembering about gapps, I went back to recovery and flashed gapps. Then it boot looped the animation. After flashing gapps again(trying different combos of wiping cache/davlik), I flashed the rasbeanjelly rom again, and then gapps immediately afterwards. Still a bootloop. So I did a full wipe(including data this time), sideloaded my .zips, and then it flashed and rasbeanjelly booted up with gapps just fine.
This exact same problem has been happening with every .zip that I try to flash(running TWRP, yes all my stuff is updated). If I want to flash a kernel, I have to flash it when I flash my ROM or else I'll get boot loop. I can't really make any modifications without having to completely wipe my device(which is annoying because I carry a lot of data around on my stuff)
I'm asking if there is a way to flash a .zip without having to completely wipe my device. I'm not a noob to android at all(ROM cooker over at androidforums), but I can't figure it out, I'd love to make stuff for the grouper but this is kind of a big roadblock for me. Logcat isn't helping either. Hopefully I just skimmed over something and it's a simple fix. Thank you for your tips/suggestions/solutions.
EDIT: forgot to mention something. When I flash a new ROM and get it going, I always make a full backup in recovery. If I flash something, and boot loop it, I can't restore it correctly. Recovery says that it restores all good, but it still boot loops(even though I just restored a backup of a non-boot looping system from no more than 5 minutes ago).

If I read your post correctly, you've only tried this on one ROM. Try the same thing on CM10 or PA or whatever you want.

korockinout13 said:
If I read your post correctly, you've only tried this on one ROM. Try the same thing on CM10 or PA or whatever you want.
Click to expand...
Click to collapse
I've actually used several, and it seems to be happening on all of them. I've tried flashing things with PA, CM10, Stock, and RasberryJelly. The kernels I have attempted to flash have been Trinity, Motley, and Franco. All with no success and boot looping me :/

[Q] question: infinite boot image with custom rom

I know it has been asked before, and I have searched the threads. reverting to stock is not a problem.
nexus 7 grouper when installing a custom rom (liquid smooth v2.9 specifically) I get stuck on the liquid boot image.
I have successfully installed v2.7 and am able to revert back to stock or custom.
after a data format, factory reset, and wiping all caches, installing the zip file from abd sideload, or directly from the device the new rom that has flashed will not get past the boot image. am I doing something wrong, or could I do something differently so that the new v2.9 boots up correctly?
I know it has been asked, but the most common answer is to go back to stock. okay, I get that. but I know this rom will run (it is flawless on my s3,) but I cant seem to get it working on the nexus.
thank you.

aircooledbusses said:
I know it has been asked, but the most common answer is to go back to stock. okay, I get that. but I know this rom will run (it is flawless on my s3,) but I cant seem to get it working on the nexus.
Click to expand...
Click to collapse
There have been numerous reports of bootup problems with "clean" LiquidSmooth ROMs in v2.7, 2.8 and 2.9.
Some possible solutions are:
Dirty flash on top of a LS ROM that boots (for instance dirty flash 2.9 on top of 2.7). When doing this you DON'T clear data and cache, but flashes new rom directly, along with gapps and kernel, and boots up. This has worked for some.
Another option when you get stuck on boot screen is to boot into recovery, and do factory reset and clear caches one more time, and try to reboot. It might take several times booting into recovery, and clear data/caches before it boots up, but again this has worked for some.
Finally you could also try the order in which you flash stuff. For instance try ONLY flashing rom, then reboot. If it works, then flash gapps. If it gets stuck, try flashing both rom and gapps in recovery, then reboot etc.
Hope that gives you something to play with! And I'm pretty sure that if you're insistent enough, you will eventually get it to boot! :good:

ameinild said:
There have been numerous reports of bootup problems with "clean" LiquidSmooth ROMs in v2.7, 2.8 and 2.9.
Some possible solutions are:
Dirty flash on top of a LS ROM that boots (for instance dirty flash 2.9 on top of 2.7). When doing this you DON'T clear data and cache, but flashes new rom directly, along with gapps and kernel, and boots up. This has worked for some.
Another option when you get stuck on boot screen is to boot into recovery, and do factory reset and clear caches one more time, and try to reboot. It might take several times booting into recovery, and clear data/caches before it boots up, but again this has worked for some.
Finally you could also try the order in which you flash stuff. For instance try ONLY flashing rom, then reboot. If it works, then flash gapps. If it gets stuck, try flashing both rom and gapps in recovery, then reboot etc.
Hope that gives you something to play with! And I'm pretty sure that if you're insistent enough, you will eventually get it to boot! :good:
Click to expand...
Click to collapse
I will keep trying. getting liquid to run on the fascinate was curious as well, but after a few flashes it took. I'll keep trying on the nexus.
Update: yes, persistence is the key. thanks
What I did was from v2.8 a factory reset, wipe cache and dalvik and flash from sideload
as expected it boot looped. manually booted into fastboot and flashed v2.9 again with only a cache and dalvik wipe.
this time it booted and I flashed gapps.
at the reboot I set up the rom to my liking and it seems to boot normally now.

aircooledbusses said:
at the reboot I set up the rom to my liking and it seems to boot normally now.
Click to expand...
Click to collapse
Yes, after it boots through the first time, I've only seen it boot normal from that point on.

[Q] Bootloop on L7. Help pls!

Hello,
First, sorry for my bad english and knowledge on flash/root.
I flashed Slimbean on my P700, everything worked fine, expect of the modem. I tried other ones, but didn't work.
So I decided to change the ROM and flashed CM10.2 on my L7 which was working fine until battery was empty. After loading my phone, I wanted to start it, but it stayed in a bootloop on the boot animation. I tried everything, wipe/dalvik wipe, flashing slimbean --> still bootloop
Now I thought, maybe CM11 could work, but still the same problem, I formated everything expect of sd, wipe/dalvik wipe, flashed the ROM, Gapps and kernel, but still the bootloop...
Any ideas?

It may take a while on first boot. But if it don't load you could restore a backup of you have one or flash a kdz or use LG update tool to fix your issue. Other than that make sure you have word everything in recovery and format system, data and cache before flashing a rom. Do not flash kernel before first boot unless it's required.

I can add to that to flash ROM only without gapps just to get OS to boot correctly.

I already solved it.
I whiped everything, formatted everything except of external sd and than first only flashed the ROM and rebooted, all worked, than i installed the Gaps, rebooted, and last i flashed the kernel, now it works fine but i will never ever reboot my phone or let battery get empty ^^ no more
thanks for your help

Stuck in bootloop in all LOS and OOS based roms

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

Nexus 6p bootloop (NOT same as Infamous BLOD)

Hi! Guys I have a problem, which doesn't resemble the BLOD, so here is what has happened. I was running stock android June build on 6p, rooted. And my phone started random reboots. I thought it could be fixed with either stock or custom rom. So I decided to flash AOSPA. I went into twrp but could not flash it, phone rebooted each time. I tried stock images via flash all command as well as manual. No rom worked although I could flash kernel etc. I used The Flash's custom twrp and fixed data and was able to flash rom easily, but it bootlooped on google logo, and rebooted. Now I can flash roms etc but it bootloops. Although Tesla rom did go into bootanimation before bootlooping.
So what can I do? Is it software related? What do you guys say!
PS. I did look into other threads, nothing was similar, although I did try a few mentioned fixes.

osamaasif786 said:
So what can I do? Is it software related? What do you guys say!
Click to expand...
Click to collapse
Use fastboot to FORMAT system, userdata and cache. Note any errors during the FORMAT process.... and then try flashing a full image from Google using flash-all.bat

v12xke said:
Use fastboot to FORMAT system, userdata and cache. Note any errors during the FORMAT process.... and then try flashing a full image from Google using flash-all.bat
Click to expand...
Click to collapse
It gives no error and did try the flash-all.bat method no luck.

osamaasif786 said:
It gives no error and did try the flash-all.bat method no luck.
Click to expand...
Click to collapse
I'd say you were squarely in a small group of people who are able to access and fully use Recovery but still boot loop after formatting and installing a clean image. If you've already tried a factory reset from the stock recovery I think you are done. Hardware issue. Replacing the motherboard is a fix, but not economically viable.

I had the same issue formatting data and cache to Ext4 and flashing modified stock ROM fixed. It would boot to Google logo freeze reboot and sometimes get to boot animation freeze and reboot.

Exodusche said:
I had the same issue formatting data and cache to Ext4 and flashing modified stock ROM fixed. It would boot to Google logo freeze reboot and sometimes get to boot animation freeze and reboot.
Click to expand...
Click to collapse
Which modified one, can you share the link?

osamaasif786 said:
Which modified one, can you share the link?
Click to expand...
Click to collapse
Cortex ROM it's flashable stock firmware with extras . Though my symptoms where the same I hope I'm not giving you false hope. Worth a shot though.

The only was I recover my phone without replacing is using https://forum.xda-developers.com/nexus-6p/general/boot-images-bootloop-t3633723 < method from here... but the phone is lag af as it is only running 1 core on stock july build. Good luck for that.

I have the same issue going on. i was trying to flash magisx and suddenly it is stuck in bootloop. i tried flashing stock images and everything. i can access twrp and flash eveything and they are getting flashed fine but still it is stuck on the bootloop.

TheTickReborn said:
I have the same issue going on. i was trying to flash magisx and suddenly it is stuck in bootloop. i tried flashing stock images and everything. i can access twrp and flash eveything and they are getting flashed fine but still it is stuck on the bootloop.
Click to expand...
Click to collapse
So have you used fastboot to FORMAT system, userdata and cache? Did each format command complete with no errors?