I've recently flashed my H811 with cm 13 build cm-13.0-20160724.
I have also tried other build and it always get stuck in "starting apps".
I can recover to the stock rom with the backup and it does work fine.
bernardog said:
I've recently flashed my H811 with cm 13 build cm-13.0-20160724.
I have also tried other build and it always get stuck in "starting apps".
I can recover to the stock rom with the backup and it does work fine.
Click to expand...
Click to collapse
Try going into recovery and wiping dalvik cache and cache
gillim74 said:
Try going into recovery and wiping dalvik cache and cache
Click to expand...
Click to collapse
I've did this multiple times. I have also tried the last 3 builds before the one of Jul 24.
No success
bernardog said:
I've did this multiple times. I have also tried the last 3 builds before the one of Jul 24.
No success
Click to expand...
Click to collapse
Try doing right after you flash the rom and gapps that worked for me
gillim74 said:
Try doing right after you flash the rom and gapps that worked for me
Click to expand...
Click to collapse
It worked for the starting apps message but then it got stuck on "finishing boot" instead.
After a few minutes it reboots by itself and then get stuck on the cyanogen logo.
bernardog said:
It worked for the starting apps message but then it got stuck on "finishing boot" instead.
After a few minutes it reboots by itself and then get stuck on the cyanogen logo.
Click to expand...
Click to collapse
What model phone do you have
gillim74 said:
what model phone do you have
Click to expand...
Click to collapse
lg g4 h811
bernardog said:
lg g4 h811
Click to expand...
Click to collapse
flash stock firmware... if it bootloops then you got bootloop issue. and you have bootloader unlocked that means warranty void... can you try relocking the bootlolader and make video.?
raptorddd said:
flash stock firmware... if it bootloops then you got bootloop issue. and you have bootloader unlocked that means warranty void... can you try relocking the bootlolader and make video.?
Click to expand...
Click to collapse
As I've said, I can recover it to the backup and successfully boot the cellphone. I bought it after this issue and it's serial number was not affected.
It is not "boot looping" also, it is just like this forever.
Again, I have reflashed the stock firmware many times and it works fine.
I think that it started after I've flashed a radio. How can I undo it?
bernardog said:
As I've said, I can recover it to the backup and successfully boot the cellphone. I bought it after this issue and it's serial number was not affected.
It is not "boot looping" also, it is just like this forever.
Again, I have reflashed the stock firmware many times and it works fine.
I think that it started after I've flashed a radio. How can I undo it?
Click to expand...
Click to collapse
i see then it must be something you flashed.. i have never been on twrp on G4.. i remeber on G2 not booting due to different bootstacks... i dont think thers different bootstacks on G4..... wouldnt flashing stock firmware fix it . if you do it LGUP refurbished?
I've tried to flash one of the roms based on the LG one and it keep showing errors for all LG apps.
I cannot open camera or even set a wifi.
bernardog said:
I've tried to flash one of the roms based on the LG one and it keep showing errors for all LG apps.
I cannot open camera or even set a wifi.
Click to expand...
Click to collapse
what version of android you have? were you on MM 20I did you update to 20o?
am just mentioning this as i heard people having problems updating from 20i to 20o. i think the fix is to refurbished LGUP with 20o if thats the case.. they said camera problems and no sound ...
raptorddd said:
i see then it must be something you flashed.. i have never been on twrp on G4.. i remeber on G2 not booting due to different bootstacks... i dont think thers different bootstacks on G4..... wouldnt flashing stock firmware fix it . if you do it LGUP refurbished?
Click to expand...
Click to collapse
same here. iam stuck too. cannot get it back started at all.
indianx said:
same here. iam stuck too. cannot get it back started at all.
Click to expand...
Click to collapse
does it shows al qualcomm 9008 brick.? i think there a fix for h811.
raptorddd said:
does it shows al qualcomm 9008 brick.? i think there a fix for h811.
Click to expand...
Click to collapse
what do you mean show qualcomm. Its just stuck after a while it reboots.
Same issue here. I updated h811 to latest cm13 nightly, booted fine for first time. Then I reflashed custom kernel and that's all she wrote. Keeps getting stuck at starting apps after in optimizes everything. The only thing works is flashing a stock image, then it boots. Flashing any CM yields same results, gets stuck. Even restoring a backup after I wipe entire phone, still gets stuck. Can't figure it out.
indianx said:
what do you mean show qualcomm. Its just stuck after a while it reboots.
Click to expand...
Click to collapse
if its hard brick it wont do a thing... when you connect phone what does it says in device manager.
/
---------- Post added at 09:30 PM ---------- Previous post was at 09:27 PM ----------
malahhaor said:
Same issue here. I updated h811 to latest cm13 nightly, booted fine for first time. Then I reflashed custom kernel and that's all she wrote. Keeps getting stuck at starting apps after in optimizes everything. The only thing works is flashing a stock image, then it boots. Flashing any CM yields same results, gets stuck. Even restoring a backup after I wipe entire phone, still gets stuck. Can't figure it out.
Click to expand...
Click to collapse
try another rom.. or build.. if you are on h811 i heard that beign on 20o works better ive never flashed cm or aosp on mine.. so if it flashes ok with stock and not cm . theres something worng bad download bad rom or update to 20o. note going into 20o you cant downgrade anymore..
I had the same problem. I resolved it by removing sim card and flash the rom again. It can be a sim card compatibility issue.
Related
Trying to check different AOSP ROMs to find the one with minimal a random reboot issue.
At first it was fine but then when I flashed some more and rebooted it would just show the LG logo over and over.
So I reflashed and after a while the flashing would be in progress and the phone would reboot to the LG logo which flashes over and over.
I am not able to proceed. I have tried several different ROMs with the same result.
I can boot into recovery just fine but each time it asks me if i want to reset. If I press yes it enters recovery mode.
Anybody knows what might be causing this?
Should I go back to stock via KDZ method?
I have a D855 32 GB international version
I reverted back to stock via kdz method which was successful but it's still happening!
Thats normal when it asks to reset i would still do the kdz method somethin till aint rite
TheMadScientist420 said:
Thats normal when it asks to reset i would still do the kdz method somethin till aint rite
Click to expand...
Click to collapse
I tried flashing once more and it didn't reboot mid-flash.
However, it still won't boot correctly, gets stuck at LG logo (which blinks over and over)
Could it be a kernel issue?
Tried with 3 different ROMs and it's the same.
I flashed only ROM and nothing else this time. Instead of rebooting into system from recovery I powered it off then powered on using hardware key. I saw the ROM's bootanimation for a second and then it got cut off and back to the LG logo.
I don't understand :/
Now i used to have a prob with my g2 when i flash a rom it bootloop if u have a good twrp back up try flashing rom then restoring only the boot image no system or cache just boot
TheMadScientist420 said:
Now i used to have a prob with my g2 when i flash a rom it bootloop if u have a good twrp back up try flashing rom then restoring only the boot image no system or cache just boot
Click to expand...
Click to collapse
Unfortunately I did not have a backup. I thought maybe the ROM files got corrupted so I copied them again and the flash was successful.
I thought okay great and flashed gapps. Aaaaand it happened again.
So i went back to stock. But it's still happening !!!! The phone won't boot at all. Just flashes the logo
Just for kicks try downloading ure kdz again sometimes they can download corrupted and still flash to the fone
TheMadScientist420 said:
Just for kicks try downloading ure kdz again sometimes they can download corrupted and still flash to the fone
Click to expand...
Click to collapse
I have used the same kdz several times without any problems in the past.
The phone actually did show the setup screen but rebooted by itself and then it was the lg logo again
Im sorry the only other thing i know to do would be the quallcom restore maybe a damaged partition that kdz xosnt touch but i dont no how to doit on g3 only g2 but u gotta have the partition layout for ure model its like fastboot only qualcom usb bulk 9000 somethin like that maybe try booting safe mode
TheMadScientist420 said:
Im sorry the only other thing i know to do would be the quallcom restore maybe a damaged partition that kdz xosnt touch but i dont no how to doit on g3 only g2 but u gotta have the partition layout for ure model its like fastboot only qualcom usb bulk 9000 somethin like that maybe try booting safe mode
Click to expand...
Click to collapse
Apparently it was an issue with the battery (says the service center).
So put in the new battery and seems to boot fine
Thanks so much for your help!
Your welcome
Still No solution for d855 boot loop?
Yea his battery
Hey guys, I need your help!
I tried to make my long story short, but that didn't work, so here's my complete story:
When everything was fine, I had CM13 running with TWRP 2.8.5.0.
My first intention was to restore a Stock 4.4 Backup and update it to 5.x. After restoring it didn't boot, so I did a factory reset and it worked.
Next I wanted to update to 5.0 via OTA, but that ofc couldn't work because of TWRP.
I knew the only way to update to 5.x was to flash a .kdz an lose all data. I didn't want to do that, so instead I tried to flash the official 30B image from here.
I followed the instructions given in the first post (updated TWRP to 2.8.7.0 too), but after flashing the files and hitting the "reboot system" button in TWRP it booted into TWRP again. I tried flashing again because maybe something went wrong. I even downloaded all the files again to make sure I didn't have a bad download, but no luck. So I restored the previous CM13 6.0.1 rom. At first it didn't succeed because my internal memory was full, but after deleting the 30B files it restored just fine. So when it was ready I hit the reboot button aaaannd it booted into TWRP AGAIN...
I searched the internet and found a "LG_G3_Flash2FixStuckRecovery.zip" file, but that didn't help either. (I connected my G3 to my pc using MTP in TWRP to backup all important data, so I don't care if I need to wipe everything.)
Now I knew something went badly wrong and tried using the LG flashtool 2014 for .kdz and another one for .tot files to recover my G3.
Still no luck. When using the 2014 tool and the official 30B kdz it runs till 100% at my phone (at the same time it reaches 80% on my pc at the LG mobile support tool). But then it's only showing the LG logo for some seconds, screen black, lg logo, black, ... an infinite loop.
When using the .tot method I can't get past the "Model Information Check FAIL!" message. It looks like I lost my IMEI because it shows "IMEI: NULL". I got an EFS Backup in a zip file though, so it's not completely lost. I tried both methods on 2 different pc's with win 8.1 and 7 (and win10 for some things), but I always get the same results.
When turning it on using the power button, I see the LG logo followed by a black screen and again the LG logo.
When connecting it to the charger I at first see a charging screen, not the charging animation, but the "loading" battery screen you get before the animation. But after it I get stuck in the above mentioned LG logo.
It's possible to get to the factory reset screen, but I get to the LG logo again after "performing" a factory reset. Note: On the factory reset screen, there is a blue "part" on the top of the screen which looks different compared to when using CM13 and Stock 4.4. The blue color is darker, so I guess, I partly got 30B installed.
I didn't plan to write that much, but I think it's better because I described almost everything I did.
I have no idea what to do now, I tried everything I know and could find on the internet.
So I just hope someone is able to help me getting my G3 working again.
Many thanks!
tl;dr: Only download mode left, but can't succesfully flash any stock rom.
Now... what do u want.... ????
Downgrade from mm to lollipop.... right????
... I can help you... by teamview. Ok
reepje123 said:
Hey guys, I need your help!
I tried to make my long story short, but that didn't work, so here's my complete story:
When everything was fine, I had CM13 running with TWRP 2.8.5.0.
My first intention was to restore a Stock 4.4 Backup and update it to 5.x. After restoring it didn't boot, so I did a factory reset and it worked.
Next I wanted to update to 5.0 via OTA, but that ofc couldn't work because of TWRP.
I knew the only way to update to 5.x was to flash a .kdz an lose all data. I didn't want to do that, so instead I tried to flash the official 30B image from here.
I followed the instructions given in the first post (updated TWRP to 2.8.7.0 too), but after flashing the files and hitting the "reboot system" button in TWRP it booted into TWRP again. I tried flashing again because maybe something went wrong. I even downloaded all the files again to make sure I didn't have a bad download, but no luck. So I restored the previous CM13 6.0.1 rom. At first it didn't succeed because my internal memory was full, but after deleting the 30B files it restored just fine. So when it was ready I hit the reboot button aaaannd it booted into TWRP AGAIN...
I searched the internet and found a "LG_G3_Flash2FixStuckRecovery.zip" file, but that didn't help either. (I connected my G3 to my pc using MTP in TWRP to backup all important data, so I don't care if I need to wipe everything.)
Now I knew something went badly wrong and tried using the LG flashtool 2014 for .kdz and another one for .tot files to recover my G3.
Still no luck. When using the 2014 tool and the official 30B kdz it runs till 100% at my phone (at the same time it reaches 80% on my pc at the LG mobile support tool). But then it's only showing the LG logo for some seconds, screen black, lg logo, black, ... an infinite loop.
When using the .tot method I can't get past the "Model Information Check FAIL!" message. It looks like I lost my IMEI because it shows "IMEI: NULL". I got an EFS Backup in a zip file though, so it's not completely lost. I tried both methods on 2 different pc's with win 8.1 and 7 (and win10 for some things), but I always get the same results.
When turning it on using the power button, I see the LG logo followed by a black screen and again the LG logo.
When connecting it to the charger I at first see a charging screen, not the charging animation, but the "loading" battery screen you get before the animation. But after it I get stuck in the above mentioned LG logo.
I didn't plan to write that much, but I think it's better because I described almost everything I did.
I have no idea what to do now, I tried everything I know and could find on the internet.
So I just hope someone is able to help me.
Many thanks!
tl;dr: Only download mode left, but can't succesfully flash any stock rom.
Click to expand...
Click to collapse
Did you try other version frimwares then 30B because mabye that will work
SpaceRaider said:
Did you try other version frimwares then 30B because mabye that will work
Click to expand...
Click to collapse
Waiting for rom then 30B... how long....???
mchiensd said:
Waiting for rom then 30B... how long....???
Click to expand...
Click to collapse
What do you mean?
mchiensd said:
Now... what do u want.... ????
Click to expand...
Click to collapse
I just want to get my G3 working again, doesn't matter if stock or CM rom
SpaceRaider said:
Did you try other version frimwares then 30B because mabye that will work
Click to expand...
Click to collapse
I tried 21A .kdz and 10E or .tot. When using 21A kdz it gives an error. It tells me something like connect my phone again and try again. Only the 30B was kinda flashable.
mchiensd said:
Waiting for rom then 30B... how long....???
Click to expand...
Click to collapse
Ehm what?
SpaceRaider said:
What do you mean?
Click to expand...
Click to collapse
No... it is not but
Reepie123 cant flash (downgrade) when flash rom kdz 30B...
Yesterday... i aslo was it... for 8h search on 4rum...
I can downgrade it .... and now.. i want help reepie123. Hi.
reepje123 said:
I just want to get my G3 working again, doesn't matter if stock or CM rom
I tried 21A .kdz and 10E or .tot. When using 21A kdz it gives an error. It tells me something like connect my phone again and try again. Only the 30B was kinda flashable.
Ehm what?
Click to expand...
Click to collapse
I think you've hardbricked it
SpaceRaider said:
I think you've hardbricked it
Click to expand...
Click to collapse
No,... i think it is softbrick... but we dont know ways.
SpaceRaider said:
I think you've hardbricked it
Click to expand...
Click to collapse
You mean it's dead, completely? I thought having a download mode and seeing my G3 on my pc with a COM# port is better than seeing some QHBULK_9008 device or similar, where I need to open my G3, connect pins and some sh*t to recover it.
reepje123 said:
You mean it's dead, completely? I thought having a download mode and seeing my G3 on my pc with a COM# port is better than seeing some QHBULK_9008 device or similar, where I need to open my G3, connect pins and some sh*t to recover it.
Click to expand...
Click to collapse
It is not dead, you can always fix it but it is a very weird issue
SpaceRaider said:
It is not dead, you can always fix it but it is a very weird issue
Click to expand...
Click to collapse
Oh ok, that sounds better. So there is hope and we just need someone who knows what to do.
reepje123 said:
Oh ok, that sounds better. So there is hope and we just need someone who knows what to do.
Click to expand...
Click to collapse
Are You have Rom TOT 10x...???
mchiensd said:
Are You have Rom TOT 10x...???
Click to expand...
Click to collapse
Yes, I already tried the 10E tot. But the problem is that the flash tools gives an error: "Model Information Check FAIL!".
reepje123 said:
Yes, I already tried the 10E tot. But the problem is that the flash tools gives an error: "Model Information Check FAIL!".
Click to expand...
Click to collapse
Mabye that's because of your IMEI error
SpaceRaider said:
Mabye that's because of your IMEI error
Click to expand...
Click to collapse
I guess so, but how do I restore my EFS without having TWRP?
reepje123 said:
Yes, I already tried the 10E tot. But the problem is that the flash tools gives an error: "Model Information Check FAIL!".
Click to expand...
Click to collapse
OK.... Now, you flash TOT again with TOT file.... but dont change file DLL you have....
Download... file DLL fix...
https://drive.google.com/file/d/0B0VrTZddvLF7b3Q1b1BlQ2w0clE/view?usp=sharing
Also don't forget: Maybe its because of your OS or even Setup (Hardware/Driver related). Even if it works seemingly at first glance.
That's my experience with all flashing tools that on some machines and setups there will happen some funny stuff and corrupt systems even if its reported to be working initially.
So if you didn't try yet use another PC/Laptop preferably with Windows 7 to 8.0 (only if you disabled driver signatures)
Edit: Also try different USB-Cables.
mchiensd said:
OK.... Now, you flash TOT again with TOT file.... but dont change file DLL you have....
Download... file DLL fix...
https://drive.google.com/file/d/0B0VrTZddvLF7b3Q1b1BlQ2w0clE/view?usp=sharing
Click to expand...
Click to collapse
I couldn't find another dll. Where have you got that from? Is it safe to use?
justyourimage said:
Also don't forget: Maybe its because of your OS or even Setup (Hardware/Driver related). Even if it works seemingly at first glance.
That's my experience with all flashing tools that on some machines and setups there will happen some funny stuff and corrupt systems even if its reported to be working initially.
So if you didn't try yet use another PC/Laptop preferably with Windows 7 to 8.0 (only if you disabled driver signatures)
Edit: Also try different USB-Cables.
Click to expand...
Click to collapse
I already tried 2 PCs, one with 8.1 and another one with 7 (and 10). Both are giving almost the same result. Except the .kdz flash tool crashes on 8.1 at 99%.
I'm using the original USB cable.
reepje123 said:
I couldn't find another dll. Where have you got that from? Is it safe to use?
Click to expand...
Click to collapse
Used file DLL this to restore Lollipop for my LG D855... when i flash KDZ 30B
It safe!!!!
it from user autoprime in 4rum....
I purchased a 5x for my wife so she can get on Project Fi. They said it was stuck boot looping, thinking I could solve the problem.
Here are the basics.
-Yes, I can get into boot loader (the menu of start, recovery, etc), but I can't get into TWRP. Tried flashing TWRP a few times and nothing. SkipSoft recognizes that its installed though.
-After bootlooping for awhile, it will load normally and work fine. However it wants to update to the newest version of android. I run the ota and back to bootlooping. It will show the android dude and say "error". Will eventually start bootlooping and then boot normally.
-I have flashed different stock versions. I tried the newest, the second to newest and the last M available. All will flash but continue the bootlooping.
Bootlooping can be anywhere from 1 minute to 10+.
The device will also first display something like, "Your device software can't be checked for corruptions. Please lock the bootloader"
But it'll show up whether the bootloader is locked or not.
The phone will freeze at some point. Whether right away or after 5 minutes. It freezes and then restarts and goes through the bootloop again.
So what else can/should I do? I've never dealt with Kernels but wondering if the last owner did something to them. Is there a way to flash stock kernels just incase or is this done when I flash a Google Factory Stock Image?
Would flashing a non-stock rom be a good idea?
Thanks
So I tried sideloading. I was able to get into the stock recovery. I tried wiping cache and data, then tried installing the newest stock rom.
Everything seemed to work. Then I had to restart. A message popped up after the same "Your device software can't be checked for corruptions. Please lock the bootloader". It had the title in blue stating "Encryption unsuccessful".
Then said, "Encryption was interrupted and can't complete. As a result, the data on your phone is no longer accessible. To resume using your phone you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account."
Then there is a single button that says, "Reset Phone".
Problem still persists.
Help please...
Why did you bought a bootlooped phone?
Sin Stalker said:
I purchased a 5x for my wife so she can get on Project Fi. They said it was stuck boot looping, thinking I could solve the problem.
Here are the basics.
-Yes, I can get into boot loader (the menu of start, recovery, etc), but I can't get into TWRP. Tried flashing TWRP a few times and nothing. SkipSoft recognizes that its installed though.
-After bootlooping for awhile, it will load normally and work fine. However it wants to update to the newest version of android. I run the ota and back to bootlooping. It will show the android dude and say "error". Will eventually start bootlooping and then boot normally.
-I have flashed different stock versions. I tried the newest, the second to newest and the last M available. All will flash but continue the bootlooping.
Bootlooping can be anywhere from 1 minute to 10+.
The device will also first display something like, "Your device software can't be checked for corruptions. Please lock the bootloader"
But it'll show up whether the bootloader is locked or not.
The phone will freeze at some point. Whether right away or after 5 minutes. It freezes and then restarts and goes through the bootloop again.
So what else can/should I do? I've never dealt with Kernels but wondering if the last owner did something to them. Is there a way to flash stock kernels just incase or is this done when I flash a Google Factory Stock Image?
Would flashing a non-stock rom be a good idea?
Thanks
Click to expand...
Click to collapse
When my Nexus 5x got into bootloop, I sent it to LG and they had to change the whole circuit. So yeah.
When you flash Google Factory Image, it flash the stock kernel.
If you have warranty, then send it to Google/LG. If you haven't got, then you're in problem. New motherboard needed, but it's expensive.
See the following thread for more info.
https://forum.xda-developers.com/nexus-5x/help/5x-bootloop-cause-fix-t3476794/
khalifakk said:
Why did you bought a bootlooped phone?
Click to expand...
Click to collapse
Cause its cheaper.
Sin Stalker said:
Cause its cheaper.
Click to expand...
Click to collapse
Then face the consequences...
khalifakk said:
Then face the consequences...
Click to expand...
Click to collapse
What consequences?
Hardware bootloop can't be fix by software.
Duckscreen said:
Hardware bootloop can't be fix by software.
Click to expand...
Click to collapse
Exactly. Everyone has either been able to get a replacement under warranty or was pretty much screwed if it was out of warranty.
Sent from my Nexus 5X using Tapatalk
Sin Stalker said:
What consequences?
Click to expand...
Click to collapse
A bootlooped phone for ever....
I recommend you will install kernel adiutor app after try rooting
I recommend you will install kernel adiutor app after try rooting
Almost I got no bootloop even no random reboot nexus 5x's state
I searched "stuck at google logo" and "stuck in bootloop on start up" and the only real suggestion I found was using Duece's bootloop tool, but I was hoping to not have to wipe all my data if ipossible.
here's my set up.
Jan factory image
latest twrp
the flash kernel 2.14
and latest magisk
nova launcher
not other mods or xposed
Getting stuck at logo has happened once or twice before, but restarting by pressing the power button has always brought it back.
Tonight, I had to hard restart 6 or 7 times before it rebooted successfully.
Any suggestions other than running the bootlooping script? I'd like to learn the manual way of fixing stuff if possible.
Thank you for any help.
andy6685 said:
I searched "stuck at google logo" and "stuck in bootloop on start up" and the only real suggestion I found was using Duece's bootloop tool, but I was hoping to not have to wipe all my data if ipossible.
here's my set up.
Jan factory image
latest twrp
the flash kernel 2.14
and latest magisk
nova launcher
not other mods or xposed
Getting stuck at logo has happened once or twice before, but restarting by pressing the power button has always brought it back.
Tonight, I had to hard restart 6 or 7 times before it rebooted successfully.
Any suggestions other than running the bootlooping script? I'd like to learn the manual way of fixing stuff if possible.
Thank you for any help.
Click to expand...
Click to collapse
Maybe try fastbooting the factory image with the -w removed out of the flash-all.bat file and then run the script. It won't wipe your data. Let the phone boot up, then go back to bootloader mode and fastboot twrp. Then you can flash the twrp zip, custom kernel, and magisk. Don't know if that'll solve your rebooting problem, but it's a start ?
On 8.0 Unlocked
Did everything you had done and got the same issue. Been over 40 minutes at the G logo with the loading thing on the bottom. Any advice on how to proceed?
DreyX said:
On 8.0 Unlocked
Did everything you had done and got the same issue. Been over 40 minutes at the G logo with the loading thing on the bottom. Any advice on how to proceed?
Click to expand...
Click to collapse
Any luck with a hard restart by holding the power button down?? What exactly did you try flashing?
First attempt was done via TWRP, Second attempt was done via Magisk. With both of them the message was shown that it had completed successfully. Though, after rebooting, the OS would get stuck at the G logo.
No idea on how to proceed honestly
DreyX said:
First attempt was done via TWRP, Second attempt was done via Magisk. With both of them the message was shown that it had completed successfully. Though, after rebooting, the OS would get stuck at the G logo.
No idea on how to proceed honestly
Click to expand...
Click to collapse
What attempt are you referring to?? Updating magisk???? ?
Badger50 said:
What attempt are you referring to?? Updating magisk???? ?
Click to expand...
Click to collapse
An attempt at installing Xposed. Both attempts after installing Xposed, doesn't allow me to get past the G logo anyhow.
I have factory restored the device a few times with the same results.
DreyX said:
An attempt at installing Xposed. Both attempts after installing Xposed, doesn't allow me to get past the G logo anyhow.
I have factory restored the device a few times with the same results.
Click to expand...
Click to collapse
Ah...gotchya. I don't do exposed, but these guys do. Best place for you to seek help my friend. Good luck :good:
https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
Sounds like you have tried to install a boot/dtbo that is a previous release instead of what is currently on the device. This happened to me. Flashing the correct version fixed my problem.
Sent from my Pixel 2 XL using Tapatalk
andrewjt19 said:
Sounds like you have tried to install a boot/dtbo that is a previous release instead of what is currently on the device. This happened to me. Flashing the correct version fixed my problem.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
p.s.: outdated Android Tools could be at fault...
If it is current, there is a flashing tool called Deuce's at https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761.
It has saved my bacon more than once while fiddling with rooting and recoveries.
andrewjt19 said:
Sounds like you have tried to install a boot/dtbo that is a previous release instead of what is currently on the device. This happened to me. Flashing the correct version fixed my problem.
Click to expand...
Click to collapse
I second this. Same thing happened to me. I had to reflash the previous image to get it to boot.
I had the Oreo aoscp rom on it and one day after a power on it went straight to TWRP. Now it only boots to recovery. I have tried wiping and reinstalling aoscp as well as the g6 rom port. So far nothing has worked. TWRP works fine and has no random restarts and stays on until the battery dies. No error messages when flashing either.
Not sure what else could be wrong or where to go from here to fix it.
Any suggestions?
forvrknight said:
I had the Oreo aoscp rom on it and one day after a power on it went straight to TWRP. Now it only boots to recovery. I have tried wiping and reinstalling aoscp as well as the g6 rom port. So far nothing has worked. TWRP works fine and has no random restarts and stays on until the battery dies. No error messages when flashing either.
Not sure what else could be wrong or where to go from here to fix it.
Any suggestions?
Click to expand...
Click to collapse
flash MM KDZ
raptorddd said:
flash MM KDZ
Click to expand...
Click to collapse
Thanks! That did it. I think it's dying anyways though but at least it's usable now!
forvrknight said:
Thanks! That did it. I think it's dying anyways though but at least it's usable now!
Click to expand...
Click to collapse
when ever i try OREO sometimes it happens. i cant go back to nougat.. i must flash KDZ then all is ok.
your welcomed.