Hey guys. About a week or three ago I saw nightlies started rolling out for the D802, and decided to try the third nightly that has been released. While flashing itself went fine, I'm having trouble with getting the ROM to boot. After the LG logo the phone enters a blank screen, and won't do anything at all. I can barely notice that the backlight stays on, and I noticed that during this bootloop or whatever this is, Windows Explorer spams over and over I need to format the disk before I can use it when the phone's plugged in. I've read from someone that I should flash the ROM and google apps simultaneously, thus I've added them to a flashing queue and wiped the Davik cache after the flashing.
At first I thought it might've been my recovery being out of date, since I was running TWRP v2.6.x.x before, so I flashed the most recent version I could find which was v.2.8.3.73.
Doing this however made no difference whatsoever, so I gave up at this point and decided to wait for a week or two for the developer to fix a potential issue on the ROMs end.
Now it's fast forward to two weeks later where I'm typing this post after trying to flash the most recent version of cm13 which was available for my phone (the D802).
The problem is I'm starting to run out of ideas to do, so I'm hoping somebody can hold my hand regarding this issue. I really like to try Marshmallow and it's really irritating it doesn't work.
Thanks in advance guys!
i yhink you need to install boostacks when you install boostacks for your varian. dont reboot into system, just go back to main menu. then reboot into recovery from recovery. then copy the rom. flash and gapps ...
i also ecoment blastagator twrp to prevent ecreen dmage
http://forum.xda-developers.com/lg-g2/development/boot-g2-hybrid-bootstacks-t3183219
http://forum.xda-developers.com/lg-g2/development/twrp-twrp-2-8-0-0-kernel-f2fs-tools-t2898705
Thank you!
I was having the same trouble with lineage OS 14.1 on my D802.
I always got a black screen after the logo of LG appeared.
luckily I could get to TWRP and push the alternative bootstack via "adb push (filelocation) /sdcard/"
Thanks a lot!
thc8 said:
Thank you!
I was having the same trouble with lineage OS 14.1 on my D802.
I always got a black screen after the logo of LG appeared.
luckily I could get to TWRP and push the alternative bootstack via "adb push (filelocation) /sdcard/"
Thanks a lot!
Click to expand...
Click to collapse
Newbie here - I'm having the same problem with my D800 after Lineage OS 14 flash via TWRP. Where do I get an 'alternative bootstack'?
Get bootstack from here!
Check this out: https://forum.xda-developers.com/lg-g2/development/lg-g2-bootstacks-t3173715
Related
Hi guys!
I just registered now but I am not new to this site at all.
Well, I have been using an LG G2 D802 (currently D80230B 5.0.2) for about one and a half years now, and I thought about proceeding further than rooting. I installed TWRP and flashed a volume boost mod with it succesfully.
The problem occured when I tried to flash a custom kernel in the hope of smoother system, features and customizability. I will write down in steps what I did:
1. I downloaded the kernel and put it on the storage of the phone.
2. I booted into TWRP and flashed the zip
3. I Wiped dalvik (or art? idk) / dalvik cache
4. Tried to reboot, I have only seen the lg logo appearing from time to time, but it's stuttering and sometimes the logo has green pixels around the screen. I can get it into download mode, but I had no result with flash tool, the software either stopped responding when I started the update without reading the phone, or it said after a minute of waiting to read the phone that port not found (USB or something).
Any ideas I can unbrick my G2 with, I really don't want to have it gone, I can't afford a new phone yet.
P.S: I have sent it to the service once in the past, so I guess my warranty is void by now.
EDIT: I got it working, the problem was that I didn't set the folder containing the kdz file at 'Work Directory'.
Hello, Newbie Here!
So I recently flashed the Resurrection Remix ROM Build 6.8 and Kernel 6.2.
The Build is rather stable and In my honest opinion better than CM12.1 which I was on previously.
So the normal functions of the phone are normal and I feel this is a much stable build. I use a ASUS Zenfone 5(ASUS_T00F)
But I face random reboots where the phone restarts itself and gets stuck at the boot. Only when i try to force reboot from the bootloop screen does the phone restart normally and even that takes three or four attempts. First I thought it was just getting used to the new Kernel then when this started occurring frequently I became more aware that this might just be a potential risk.
Today afternoon, My Phone was literally stuck at bootloop for 2 hours.... Only when I tried to do three-four manual forced reboots by pressing my power key and with each instance entering the TWRP mode and doing a dalvik and cache wipe only then was I able to boot up my phone normally.....It totally drained the battery though. I was at 78% and when my phone finally booted up I was shocked to see just 1% charge left.
Everytime this issue occurs...either the phone is completly stuck in bootloop or goes to the "Android is upgraing your apps" notification and then again comes back to the bootloop.
I have also done two fresh flashes before this as well so I know its got nothing to do with a dirty flash.
I then started googling for the same issue that other Zenfone 5 users might be experiencing but to my shock...No threads on it could be found with the issue that Im experiencing.
Pretty frustrated right now I have no clue what to do.
Donot want to go back to STOCK ROM..It sucks.
Please help Guys!
Hello.
You should try to format system and reinstall the rom + xposed. After that you can format data, cache, internal storage. I hope that it will help you.
And did you have this problem on CM12.1?
tank0412 said:
Hello.
You should try to format system and reinstall the rom + xposed. After that you can format data, cache, internal storage. I hope that it will help you.
And did you have this problem on CM12.1?
Click to expand...
Click to collapse
Yup. Tried all this.
Just format again and re flash rom with xposed it fixed my bootloop.
The solution is,
Go back to stock rom. ???
Can anyone tell me how to back stock ROM from resurrection remix???
yasin0005 said:
Can anyone tell me how to back stock ROM from resurrection remix???
Click to expand...
Click to collapse
Download latest firmware from Asus' Support Page. And flash it via adb sideload.
I m now on Stock Rom without any problems no screen freeze no bootloops ...
Hi there,
I started this topic because I am out of options and I don't know what to do at this point.
My Phone is a XT1562 DualSim.
I recently flashed http://forum.xda-developers.com/moto-x-play/development/rom-spetrum-mm-volte-t3462690 and I also installed "MODEM" (MPD24.107-70) from page 1, but not right away.
First I wiped everything expect "internal storage". The phone booted but it restarted during boot (which might be okay) but then it rebooted again during boot. The boot process finally finished and I got to the screen "Android is starting - Optimising app x of y." The phone rebooted even during that process and that is definitely not normal I think. So after a couple of reboots android did finally optimise all apps but the phone did still reboot withing the first 30 seconds after it was booted.
From here I did a lot of testing and doing. These are my findings:
- When I set phone to flight mode / airplane mode it does NOT reboot... Hurray!
- When I flash another ROM (Official CM 13, http://forum.xda-developers.com/mot...m-cyanogenmod-13-preview-moto-x-play-t3252255) the phone runs like a charm, NO reboots whatsoever.
- - But as soon as I flash gapps and the phone is booted, I get the reboots again (usually within the first 30 seconds).
- - Again setting the phone to flight mode prevents itself from rebooting.
- - Apparently it doesn't matter what version of gapps I flash. I even tested the light version (ARM, 6.0, Pico, from http://opengapps.org/). It still reboots. I also tried gapps mini and stock.
Oh and I don't think its MODEM (mentioned above) related, because I faced these problems already before I installed / updated the MODEM. Well I thought its MODEM related, that's why I went back to MODEM stock version MPD24.107-52 but that did't help either. I should mention that I am not sure if I had MPD24.107-52 installed originally but spetrum (the rom developer) pointed me to that version: http://forum.xda-developers.com/showpost.php?p=69129552
I also restored my working TWRP backup from an android I used for month and guess what, yep, reboots
brrrrr this is frustrating
I never experienced that before and frankly I am out of ideas.
Anything is welcome and appreciated
Thank you
If nothing helps reflashing the whole firmware is always an option
minimale_ldz said:
If nothing helps reflashing the whole firmware is always an option
Click to expand...
Click to collapse
Thanks I haven't done that.
To be clear, you mean firmware as in stock rom / factory image?
I always go back to flashing stock rom with rsdlite whenever things went wrong and I can't solve it by flashing small fixes.
rancor187 said:
Thanks I haven't done that.
To be clear, you mean firmware as in stock rom / factory image?
Click to expand...
Click to collapse
I mean full stock firmware you flash with fastboot or RSD. Roms are usually only system + kernel, so not very helpful in your case
Guys! Good news. I did go back to stock firmware and from there to official CM13. Of course I had to root and install TWRP again but it was worth it.
I lost a few days spending my time with it but I'm glad its all good now thanks to you.
Without fail every time after the lg logo disappears after flashing a custom rom made for the h918 lg v20 I get a flashing black screen. I'm doing a factory reset/wiping davlik cache/ cache/ and data 3 times each time I flash the custom rom and sometimes I even go as far as wiping the internal memory completely even after a factory reset but no matter what I try without fail I always get the flashing black screen right after the lg logo disappears. I even tried upgrading twrp from 3.0.2.0 to 3.1.1.0 and I even tried flashing the no-verity-opt-encryption 5.1 and 6.0 but nothing I've tried seems to fix it so I'm asking for help now since I've exhausted my knowledge on what could fix it. What can I do to fix that issue so I can finally start using custom roms again? Any help would be most appreciated thanks in advance.
P.S. The only rom I could get to flash successfully was the stock twrp flashable t-mobile rom on one of the threads in the rom section of the lg v20 forum so for now until I can fix that issue I'm currently running that so I have a phone I can still use.
raze5115 said:
Without fail every time after the lg logo disappears after flashing a custom rom made for the h918 lg v20 I get a flashing black screen. I'm doing a factory reset/wiping davlik cache/ cache/ and data 3 times each time I flash the custom rom and sometimes I even go as far as wiping the internal memory completely even after a factory reset but no matter what I try without fail I always get the flashing black screen right after the lg logo disappears. I even tried upgrading twrp from 3.0.2.0 to 3.1.1.0 and I even tried flashing the no-verity-opt-encryption 5.1 and 6.0 but nothing I've tried seems to fix it so I'm asking for help now since I've exhausted my knowledge on what could fix it. What can I do to fix that issue so I can finally start using custom roms again? Any help would be most appreciated thanks in advance.
P.S. The only rom I could get to flash successfully was the stock twrp flashable t-mobile rom on one of the threads in the rom section of the lg v20 forum so for now until I can fix that issue I'm currently running that so I have a phone I can still use.
Click to expand...
Click to collapse
did you ever find a solution? I'm having the exact same issue and am pulling my hair out trying to get something to work
If the version number of twrp your using is in fact 3.1.xx then that could be your problem all the new roms im almost positive need the newest twrp from pheonix i think it 3.2.3.4 its in the deveopment section...ive heard alot of problems on this device with older interations of twrp. I would start there
https://forum.xda-developers.com/showpost.php?p=77177529&postcount=6
Phoenix591 said:
Official lineage 14.1 only works with pre10p h918, some firmware blobs need changed.
I just built an unofficial for my own use a few days ago that should work, but I havnt gotten around to testing it yet.
lineage-14.1-20180721-UNOFFICIAL-h918.zip
lineage-14.1-20180721-UNOFFICIAL-h918.zip.md5
When lineage 15.1 becomes official the h918 builds will be aimed at post10p. x86cpu is currently doing unofficial builds for both.
Click to expand...
Click to collapse
Hi. I’ve got a customer with a j5 that I factory reset as she was having problems with it. But now it will only boot to TWRP which must have been installed before she bought it.
I’ve tried sourcing a stock android but with no luck so I tried a few Roms from here today. I can’t get it to work at all! Here’s what Happens.
From twrp I install CM rom and gapps. When I reboot the phone an orange line appears across the screen followed by the Samsung logo. Then the screen starts fading to green. The screen is in full working order when using twrp.
Does anyone have any ideas?!
Thanks
Davidb8 said:
Hi. I’ve got a customer with a j5 that I factory reset as she was having problems with it. But now it will only boot to TWRP which must have been installed before she bought it.
I’ve tried sourcing a stock android but with no luck so I tried a few Roms from here today. I can’t get it to work at all! Here’s what Happens.
From twrp I install CM rom and gapps. When I reboot the phone an orange line appears across the screen followed by the Samsung logo. Then the screen starts fading to green. The screen is in full working order when using twrp.
Does anyone have any ideas?!
Thanks
Click to expand...
Click to collapse
More than likely that version of twrp is outdated get a .IMG file of twrp version 3.2.1 and flash the image in twrp. Use this https://forum.xda-developers.com/galaxy-j5/development/recovery-samsung-galaxy-j5-t3769408/page5
If that isn't the problem and the problem you have persists than you have either flashed the wrong version file as there is several types of galaxy j5 with different hardware,
Or the bootloader you have on the phone is the wrong version ie. it has marshmallow bootloader and your trying to flash a ROM that only supports lollipop or vice versa. Links for both bootloaders are here
https://forum.xda-developers.com/ga...5-1-1-bootloader-modem-j500xx-t3566801/page14
This should fix your issues hope it helped