Hello, I had some issues with my LG G2 while attemping to flash a new rom, here's my problem:
I checked for the latest crDroid 6.x rom and the gapps, everything went fine, I flashed the rom with no problems at all and then continued with the gapps. But here's the problem, when I tried to boot it, nothing popped out from the display, just the LG logo, then it was completely black. After trying to install another custom rom (cm 13 nightly), nothing happened. Then, I tried to go back to my AICP rom. I had to use ADB installer since I didn't have any zips avaiable, but when I tried to install tk gapps (downloaded from the AICP forum), Error code: 20 came out. I did a research, and this looks weird, because that error only pops when the gapps are not compatible with the current rom, but clearly they were. Any ideas on how to fix this up?
Avrammm said:
Hello, I had some issues with my LG G2 while attemping to flash a new rom, here's my problem:
I checked for the latest crDroid 6.x rom and the gapps, everything went fine, I flashed the rom with no problems at all and then continued with the gapps. But here's the problem, when I tried to boot it, nothing popped out from the display, just the LG logo, then it was completely black. After trying to install another custom rom (cm 13 nightly), nothing happened. Then, I tried to go back to my AICP rom. I had to use ADB installer since I didn't have any zips avaiable, but when I tried to install tk gapps (downloaded from the AICP forum), Error code: 20 came out. I did a research, and this looks weird, because that error only pops when the gapps are not compatible with the current rom, but clearly they were. Any ideas on how to fix this up?
Click to expand...
Click to collapse
for your rom to boot you need hybrid bootstacks
wipe all/flash hybrid/ go to main menu/ then reboot into recovery from recovery/ once in recovery again proceed to flash rom and gapps.
use the one for your variant
http://forum.xda-developers.com/lg-g2/development/boot-g2-hybrid-bootstacks-t3183219
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 have one XT1570(china version with dual sim), falsh lineage 14.1( the latest nightly one) , gapps with twrp, after flash both of them, I click "reboot", then "system". it can't go inside the system, still show with twrp ui.
Now I tried few times, still the same.
But if click "reboot", then "bootloader", after screen goes up, press power button"start", it looks the initiation of android system, but it last for hours, still loading screen.
Any suggestion for this problem?
Thanks.
Los 14.1 is for Marschmallow, one(?) build is for Nougat.
Xt1570 - Lolipop, if you didn't flashed any upper stock rom. @tigerszheng
the original one is Android 7.0 Nougat™ NPH25.200-15, I think this is the previous rom, but when I do factory reset, it boots into twrp directly.
Since I originally want to flash the lineageos 14.1 for clark, so I download the lineage-14.1-20171106-nightly-clark-signed.zip, and the gapps*.zip,
that's the content I used to flash with twrp, but the problem seems that the rom doesn't work properly. or maybe because the xt1570 default to boot into the recovery(twrp)?
not sure about what's the problem of this?
Thanks.
Try AOSP ext. for 7 modem:
https://forum.xda-developers.com/moto-x-style/development/collection-random-projects-t3662970
@tigerszheng
Hi, I tried to encrypt my Mi A1 with Android’s full-disk encryption. Unfortunately something went wrong, so I tried to flash a Rom. First I tried a dirty flash with the official LOS 15.1 (20190224). But the Display went crazy. So I head to flash the stock Rom through fastboot. After this my Mi A1 worked. Next I tried a clean flash with the same LOS-Rom, but I get the same result. I also tried some other versions of LOS, but I get also the same result. I also tried to flash LOS 16.0 (20190301) and also AospExtended v6.3(20190213). The result after flashing those Custom Roms is that the Display stays black, but not like the phone is off. It looks like the display is active but black. I had also tried LOS for microg 15.1(20190310) but the result was the same as flashing LOS 15.1
When I flash LOS 15.1 or the other Roms with the same result and I boot in TWRP the Display there also went crazy.
Sometime when I format or flash something with TWRP I get the message ,,Failed to mount ‘/system’ (Permission denied). But I always get the same result after flashing.
I hope someone could help me.
same to me
just recovey my phone with mi flash y culdnt get a costom rom again
You need to correct youe version of TWRP recovery
Infact, you need to try different versions to see which one works for uh...
Try booting into recovery IMG from Fast boot again and again if uh are really troubled by a permanent recovery.
I followed the instructions from the official website of Lineage OS 16 and I adb sideloaded the ROM first and then the GApps and then made the first boot. But I'm stuck in the lineage os logo. I'm using Arm-64 nano as recommended by Lineage OS. Anyone running lineage os official with GApps please share your experience and how you were able to boot it.
I don't use GApps, but did you clean cash, data etc.... ?
And it will be better to try without GApps and do a first run... going back to recovery after the first run and install Gapps.
Why don't you give any modern ROM based on 4.9 kernel a try? Q ROMs for now. I can highly recommend Havoc by Sairam. 0.1%/h idle drain with BT on almost always and 9%/h active drain over 4G. Plus 4.9 ROMs are simply much more fluid than any 3.18 ROM.