Develop Bugs

[D855 32 GB] Reboot problems (brick or hardware defect?)

Hello guys,
I managed again to brick my phone.
I flashed Fulmics as I wanted to swap from those not fully stable nougat roms. Well, I have no idea what caused my problem - Fulmics run without prolbems for a 2 or 3 days including xposed etc.
Then today I changed my ChromePie options and that's when the reboots began. I don't know if this the real cause was though.
So I tried to flash another rom but always got random reboot even in recovery after few minutes/seconds. So I went all the way back to stock rom (4.4.2) with LG Flash tool - which worked after a few tries. Then I installed MM rom via .kdz file and flash tool 2014, which also worked after a few more tries. But then the reboots started again. Can't say if the 4.4.2 rom was without boots because I updated to 6.0 quite quickly.
The strange thing is that after some reboots phone won't boot again and I have to take and leave out the battery for some time to boot the phone again.
Any solutions for my problems?
Best regards

..bumped into the same 1/2 year ago. Didn't want to put to much effort so,..went to stock and back, worked for me.
Good luck.

Gerhard.M said:
..bumped into the same 1/2 year ago. Didn't want to put to much effort so,..went to stock and back, worked for me.
Good luck.
Click to expand...
Click to collapse
Which stock and how did you go back?
As mentioned I already went back to stock but the issue kept occuring.

Hi, got the same problem with my G3
wi fi and bluetooth didn't work and phone loop rebooted
Here below the steps I followed to solve
1) First attempt (didn't solve): had cloudy rom, got back to stock official but still rebooting, tried fulmics and other rom but problem persisted.
2) second attempt (didn't solve): went back to stock and changed battery (found somewhere in internet), now I have a brand new battery but a phone still loop rebooting
3) third attempt (SOLVED): found that the wi-fi / bluetooth chip (one for both) copuld have unwelded and solved so (it appears I can't post outside link, delete spaces to have the correct link):
youtube .com / watch?v=1zWpzYh2DPI&t=15s"
youtube .com/ watch?v=6_0jzp65eLY&t=256s
Now i'm on fulmics and no more loop reboot
Hope you can solve
[sorry for my english]

frosty234 said:
Which stock and how did you go back?
As mentioned I already went back to stock but the issue kept occuring.
Click to expand...
Click to collapse
http://stockroms.net/file/LGG3/D855/European/BIN_LGD855AT-00-V10e-EUR-XX-JUL-08-2014-32G-0.zip
http://storagecow.eu/index.php?dir=Xda/LG+G3/Stock/D855/
used flashtool
have to say restoring and/or flashing isn't always that stable. I've experienced it sometimes needs a 2nd try.
Hopefully it isn't a hardware issue in your case.

So I tried all of oyur suggestions but nothing seems to work.
On the contrary I ended up in a status where I can't even flash a new firmware.
In LG Flash Tool 1.8.1 I get the error
"Donwload Fail!!!"
PID: NULL
IMEI: NULL
MODEL:
DLL: D855
BIN: LGD855AT.....
SWV:
SWOV:
Model Information Check Fail!
000000000
Click to expand...
Click to collapse
In LG Flash Tool 2014 (flashing MM with kdz file) phone shuts down in middle of process.
But I can still access Download Mode.

No more ideas?
I really think I finally broke my phone... But the fact that I can still access download mode keeps my hopes up.

So, after 2 months I just tried to reawaken my phone. Still the exact same problem. It just keeps shutting down aber some while, but just when I start flashing something. If it stays connected to computer whitout doing anything it can stay on for like ever.
Can anyone confirm that this could be a hardware defect?

[Help] My HTC One M8 not booting

Hello everyone. Since the Title has character limit im gonna have to explain myself here better.
Ive had my HTC One M8 for 4 years now. Pretty much since it came out in 2013. I installed ARHD back in 2014 and its been working just fine ever since. A couple of months ago i decided to go back to 45.0. Everything went smooth and everything works just fine.
But a week ago the phone decided to just go woopdido and it wouldnt open up any apps in Playstore although i could still see them. So i tried to restart it and when i did it got stuck at the HTC Logo. I tried to restart it a few times but it kept getting stuck. I was super confused due to the reason that i havent really done anything with my phone besides since the day i installed ARHD 45.0. I got desperate so i reinstalled it but this time with 53.1 and that went fine too except for one fishy thing and that was that i remember before when installing ARHD, when it got 30% it wouldnt take 2-3 minutes for it to finally start installing the ROM. It would take a couple of seconds for it to start right away and be done.
After installing 53.1 phone worked just as fine except for the fact that it was slower than it has ever been before. Which was also weird. Either way. After a couple of hours of it working, setting up every app i needed i restarted it and again it was stuck at the HTC Logo. Welp i guess..
So after that crap i went back to 45.0 again. It went good and all except it keeps getting stuck at 30% for a while but whatever. Going back to 45.0 though didnt help. Keeps repeating the same crap after a while. After a restart when having the phone doing nothing for hours gets it stuck at HTC Logo again. I literally cannot do anything with it atm and i have no clue how to go further from here as i have not had this before.
The HTC One M8 is rooted. S-Off everything you really need. The current TWRP version i have is 3.1.1.0.

Your firmware may be outdated. I would think it would be, as you said you haven't installed anything to the phone since 2014.
This (old firmware) alone would play havoc with the current ROMs. And also not play well with current TWRP, which may explain why going back to ARHD 45 is still resulting in problems.
What goes it day for OS number on the bootloader screen? If blank, what are the hboot and radio numbers?
The original issue could have just be due to some damage or corruption to the OS. It happens.
Also, the phone was released in 2014, not 2013.

redpoint73 said:
Your firmware may be outdated. I would think it would be, as you said you haven't installed anything to the phone since 2014.
This (old firmware) alone would play havoc with the current ROMs. And also not play well with current TWRP, which may explain why going back to ARHD 45 is still resulting in problems.
What goes it day for OS number on the bootloader screen? If blank, what are the hboot and radio numbers?
The original issue could have just be due to some damage or corruption to the OS. It happens.
Also, the phone was released in 2014, not 2013.
Click to expand...
Click to collapse
It was released in 2014? Welp why did i think it was 2013? Either way.
You missunderstood me but its all good because its on me. I was meant to say that i havent touched anything since i installed 45.0 a couple of months ago right. The firmware is fine and all for the current version i have. It was for 53.1 too.
And out of the blue it just got stuck on the HTC Logo. I tried something and it was updating the SuperSU which actually was the reason why it got stuck on the HTC Logo. I installed 2.79 and now it boots just fine and the phone is back on speed again. Apparently 2.82 has issues which is the version i assume it tried to update to through both TWRP and Playstore.

sp3tan said:
You missunderstood me but its all good because its on me. I was meant to say that i havent touched anything since i installed 45.0 a couple of months ago right .
Click to expand...
Click to collapse
Ah, I do see now that you stated you installed ARDH 45 a couple months ago. There is a lot of info there, so I missed that part.
Glad to hear you sorted it out. It's unusual to see a simple SuperSU update cause such a chain of event; but s#it happens I suppose.

redpoint73 said:
Ah, I do see now that you stated you installed ARDH 45 a couple months ago. There is a lot of info there, so I missed that part.
Glad to hear you sorted it out. It's unusual to see a simple SuperSU update cause such a chain of event; but s#it happens I suppose.
Click to expand...
Click to collapse
Yeah it does. I also forgot to mention that my microphone went to sh*t also. But its not because of this event. Although after this last reinstall i did the microphone picks up my voice better than it did before it went crap. But people cant still hear me when they call me

T800: Can't complete boot when using 7.x.x roms

I had the latest 6.0.1 samsung rom (CPK2) which was giving me problems with freezing. So I am trying to upgrade to an 7.x.x rom, either RR, AIPC, or Lineage. But none of these roms allow the T800 boot to get beyond the initial splash logo screen. I am using latest TWRP, 3.1.1 to wipe and install rom. I am not getting any install errors. Boot loader is confirmed as CPK2.
FYI, I am able to get back to the samsung rom by reflashing it with Odin.
Update 1: In the final attempt of upgrading I installed the official 6.0.1 fw which boots fine unlike the aforementioned alternatives (very strange). However, lock ups and now screen blanking more frequent. This time wiped everything including storage. It looks more like a hardware issue but I wonder if this could be malware even after wiping everything. I will have to take this in for repair but have little hope of solving this problem.

mach281 said:
I had the latest 6.0.1 samsung rom (CPK2) which was giving me problems with freezing. So I am trying to upgrade to an 7.x.x rom, either RR, AIPC, or Lineage.
Update 1: In the final attempt of upgrading I installed the official 6.0.1 fw which boots fine unlike the aforementioned alternatives (very strange). However, lock ups and now screen blanking more frequent. This time wiped everything including storage. It looks more like a hardware issue but I wonder if this could be malware even after wiping everything. I will have to take this in for repair but have little hope of solving this problem.
Click to expand...
Click to collapse
My wife has the US Cellular 10.5 variant (T807R4). It was freezing so frequently it had become almost unusable for anything but watching videos. Rooting and disabling most of the Samsung apps did not fix the problem. I wiped the system with TWRP only to discover that none of the custom ROMs would work on this model. I downloaded and flashed the stock Samsung MM firmware (and it sat on the opening splash screen for at least 15 minutes before it finally booted up) and for the hour I used it after setting it up, I had no problems. I had previously cleared the cache with Titanium Backup and that also seemed to be a temporary fix. My conclusion is that something is happening when the cache fills up that causes the freezes but I'll need more data to say that for sure.

Just an update: I was going to have the hardware looked at so I wiped everything including the storage. But when I took it to the shop and was asked to demonstrate the freezing the tablet wouldn't. So I took it back and it was running OK until a couple weeks later when the same problems reared there heads.
Somehow I managed to get a 7.1.2 installed and the T800 is running great...so far. I'll post back if the freezing starts again.

mach281 said:
Just an update: I was going to have the hardware looked at so I wiped everything including the storage. But when I took it to the shop and was asked to demonstrate the freezing the tablet wouldn't. So I took it back and it was running OK until a couple weeks later when the same problems reared there heads.
Somehow I managed to get a 7.1.2 installed and the T800 is running great...so far. I'll post back if the freezing starts again.
Click to expand...
Click to collapse
Please explain the steps to install 7.1.2 (and which ROM you used) and update on the freezing issue. Most of the freezing issues I have read about seem to be on LTE variants (SM-T807x) so I was about to buy a wifi only (T800) tablet, thinking that would be a solution to the problem. If that's not the case, then I shouldn't waste my money.

The instructions for installing a non-stock ROM are on the dev's host page in Tab s forums. I first tried Resurrection Remix and now am on LineageOS. It was only after I wiped the internal storage area that I was able to get past the 7.x.x boot screens.
I found the stock rom 6.0.1 freezing issue persistent. I believe the problems started for me with XAR H4 and really picked up with K2 (roms supplied by sammobile). The tablet would frequently just freeze while working in an app: the screen and hardware buttons would not respond at all. Never had that problem with Android 5. The only thing I was able to do to unfreeze it was to reboot into download mode then restart the OS from there. I sometimes found that if I left it frozen overnight it would unfreeze itself by morning.

Dead Tab ? Help ! - Free beer

I've searched far and wide, but nothing seems to resolve my issue.
The case:
I have 2 Galaxy Tab S(T800).
One, the oldest, has always run a stock rom + Root
One, I have on LOS 7.1.2.
The oldes one rebooted spontaniously. After searching, i thought it was the battery. On the web people say it often happens with this device. So cracked up de back and checked everything. Thing were looking fine (similar to the working one). Also: in download mode or recovery, it doesn't restarts.
So it has to be software, right? RIGHT ??
I've wiped everything. Factory, Data, Cache. No luck.
Installed the stock rom; no luck. And TWRP then LOS; no luck.
Here is where i loose my mind: Odin gives a pass. The Tab starts perfectly, but upon booting, it quits. On 4.4.2, 5.0.1, 6.0.1. The furthest i've come was the startscreen of LOS, but upon Wifi settings, it reboots again.
Tried to re-partition with the .pit file : no succes either.
HELP wanted. Maybe I can do something with my other, still working tablet.
A free beer for my saviour!

quintinliono said:
I've searched far and wide, but nothing seems to resolve my issue.
The case:
I have 2 Galaxy Tab S(T800).
One, the oldest, has always run a stock rom + Root
One, I have on LOS 7.1.2.
The oldes one rebooted spontaniously. After searching, i thought it was the battery. On the web people say it often happens with this device. So cracked up de back and checked everything. Thing were looking fine (similar to the working one). Also: in download mode or recovery, it doesn't restarts.
So it has to be software, right? RIGHT ??
I've wiped everything. Factory, Data, Cache. No luck.
Installed the stock rom; no luck. And TWRP then LOS; no luck.
Here is where i loose my mind: Odin gives a pass. The Tab starts perfectly, but upon booting, it quits. On 4.4.2, 5.0.1, 6.0.1. The furthest i've come was the startscreen of LOS, but upon Wifi settings, it reboots again.
Tried to re-partition with the .pit file : no succes either.
HELP wanted. Maybe I can do something with my other, still working tablet.
A free beer for my saviour!
Click to expand...
Click to collapse
It looks like a failure in the EMMC .. they were defective in these plates (Toshiba brand) mine has that problem and every 3 days they start restarting and I have to reinstall ..

Gen1 FireTV stuck in reboot loop

So, I have a rooted 1st gen FireTV (aka bueller). I have no recollection what I did to it long time ago when I rooted it, other than it worked fine but was stuck on old software (5.0.x?). So I wanted to run newer apps on it, and I updated it with 5.2.7.3 rooted image. It reboot, went through the 10 min "system storage and applications" and was working, new UI and everything.... but when I tried updating the apps, it complained that the app store is too old. A few minutes later it rebooted.....and did the same "optimization" gig for like 10 mins.... then it rebooted, and now it reboots over and over, sometimes doing optimization, sometimes not, and sometimes I see the UI come up a second before it reboots again. TWRP bootloader works, so I can try flashing it back with older FW, I but I really would rather go forward. Any way to find out what is happening? I tried ADB, but it does not seem to connect when "optimization" is running
Thanks

hichhiker said:
So, I have a rooted 1st gen FireTV (aka bueller). I have no recollection what I did to it long time ago when I rooted it, other than it worked fine but was stuck on old software (5.0.x?). So I wanted to run newer apps on it, and I updated it with 5.2.7.3 rooted image. It reboot, went through the 10 min "system storage and applications" and was working, new UI and everything.... but when I tried updating the apps, it complained that the app store is too old. A few minutes later it rebooted.....and did the same "optimization" gig for like 10 mins.... then it rebooted, and now it reboots over and over, sometimes doing optimization, sometimes not, and sometimes I see the UI come up a second before it reboots again. TWRP bootloader works, so I can try flashing it back with older FW, I but I really would rather go forward. Any way to find out what is happening? I tried ADB, but it does not seem to connect when "optimization" is running
Thanks
Click to expand...
Click to collapse
FWIW, Several more re-flashes back and forth and a wipe, and it is now working