Develop Bugs

[Q]Desire Z keeps rebooting after few seconds on home screen

Hi,
I ve been through all this forum and the rest of the internet, but I couldnt find the answer ... so hopefully you will help me.
I have Desire Z - about 3 months old.
I ve rooted the phone and flashed to cyanogenmod 7.1 stable. All the time Ive followed guides here or on cyanogen section/wiki. CM has been running stable for a month maybe until today.
This morning I couldnt make a call - so I rebooted phone.
After reboot phone gets to the home screen and automatically reboots itself after 5 seconds.
info from hboot
VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC1011000)
MICROP-0425
eMMC-boot
OS ver 1.34.707.3
CID 1111111111
Click to expand...
Click to collapse
Ive already tried:
Wipe cache / davik cache
Wipe battery status
Recover to CM - backup created right after first flash - successfully - problem remains
Recover to original ROM - successfully - problem remains
any ideas?
also - if you dont have any advice to fix this problem - Id like to ask you, if you could point me to the best way, how to unroot/(s-on) etc. phone and make it look like its like stocked one for the purpose of waranty. - i dont mind any data nor in phone nor on sdcard, everything I need is synced to gmail acc. Thank you

cyber-mythius said:
Hi,
I ve been through all this forum and the rest of the internet, but I couldnt find the answer ... so hopefully you will help me.
I have Desire Z - about 3 months old.
I ve rooted the phone and flashed to cyanogenmod 7.1 stable. All the time Ive followed guides here or on cyanogen section/wiki. CM has been running stable for a month maybe until today.
This morning I couldnt make a call - so I rebooted phone.
After reboot phone gets to the home screen and automatically reboots itself after 5 seconds.
info from hboot
Ive already tried:
Wipe cache / davik cache
Wipe battery status
Recover to CM - backup created right after first flash - successfully - problem remains
Recover to original ROM - successfully - problem remains
any ideas?
also - if you dont have any advice to fix this problem - Id like to ask you, if you could point me to the best way, how to unroot/(s-on) etc. phone and make it look like its like stocked one for the purpose of waranty. - i dont mind any data nor in phone nor on sdcard, everything I need is synced to gmail acc. Thank you
Click to expand...
Click to collapse
Pull /proc/last_kmsg and see what it says; should help you narrow it down.
Sent from my HTC Vision using XDA App

could you gimme hand how? - the only point where I can get in the phone is to bootloader / recovery.
so i cant run terminal from apps in phone.

+ could anyone help me how to charge up battery with my problem? I have about 20% on both batteries and I dont want to loose them during repair progress.
to the /proc/last_kmsg - i could not find anything like this on sd

cyber-mythius said:
+ could anyone help me how to charge up battery with my problem? I have about 20% on both batteries and I dont want to loose them during repair progress.
to the /proc/last_kmsg - i could not find anything like this on sd
Click to expand...
Click to collapse
Sorry, I just got to work. The last_kmsg is on your device, not the sdcard. If you have ADB set up you should be able to access it by connecting your phone to your computer
Sent from my HTC Vision using XDA App

I have everything installed on the other PC where Ill be on monday. Maybe Ill find some time to look through it tommorow.
Thank you now for pointing me somewhere - Ill add more info when I ll have it.

I had a similar problem after flashing new rom. My Desire Z was also rebooting after a few seconds.
I downloaded 1.34.707.3 firmware(used to downgrade Desire Z from gingerbread) from CM wiki, installed it through fastboot (step 8) , rooted my phone once again following the wiki and since then my phone is working without any problems.
Battery can be charged up while the phone is turned off.

well I flashed phone with the downgrading rom as you mentioned and it helped a little
- phone is running and not restarting after few seconds - but randomly after 5-60 seconds (so I am able to do at least something ))...
On monday I ll root that bi*ch again, pull there CM7 or some other ROM and post here actual status.
Thank you so far

Similar problem
Hi, I have the exact same problem with my Desire Z. I've attached the last_msg if someone could help me with that.. also, my sdcard is not partitioned so could that have anything to do with it? Thanks, hopefully I'll get an answer soon

Resurrecting a bit of an old thread here but I have just experienced these exact symptoms.
A friend gave me his old Desire-Z so of course I immediately set about rooting it and trying some ROMs.
As a start I went with the most recent Cyanogenmod which is 7.2 at this time. Everything was going smoothly and was just getting used to the phone and it's physical keyboard. My biggest worry was that the battery life wouldn't be good enough for me so I was running a test to see how long it would last. I am a very light phone user. With background wifi disabled, gps disabled and the phone set to 2G only it ran for 7days and 3 hours! No problems there even with a well used battery. When it eventually died I hit the power button to wake it and it started booting and then shutdown again as you would expect. However after I had fully charged it it booted no problems but then went into the boot loop described above. It boots successfully to the home screen but then after 10-15 seconds it reboots. Frustrating!
I tried some things:
Clear cache from CWM: No change
Factory reset from CWM: No change
Reflash CM7.2 from CWM: No change
Clear Dalvik Cache from CWM: No change
Clear Battery stats from CWM: No change. I was hopeful this might be the problem as the battery had been unusually flat, perhaps some flag had been set that caused the reboot.
I have now recovered by reflashing the exploitable original image, PC10IMG.zip, and then going back through the rooting process. I wouldn't want to have to do it again though.
Possible explainations for the behaviour: I was running a battery monitor app (GSam Battery Monitor) which runs continuously and has various power related functions. Though I would have thought anything that was doing would have been removed by factory reset or reflashing CM.
During the 7 days I was testing ROM manager prompted me to update it and then to update the version of CWM that I had. This is perhaps more likely as would have survived everything else I tried to recover until I reflashed the original recovery.
Hope that helps someone and if anyone has any insight on this I'd lobe to hear it.
Steve

Looks like I spoke too soon. First time I had to reboot the phone I got stuck in the reboot loop again.
Hmm, really confused now. No idea what can be causing this that isn't solved by reflashing CM7.2 but is by going back to the original rom?
Steve

the only thing, that helped me back then was to flash another ROM ... give it a try.
there is several other ROMs based on CM, I'm pretty sure, that you'll find one, that will suit you best.

Thanks for the reply I appreciate you taking the time.
It's very odd I can't think what might be causing this. I ran CM7.2 with zero issues for a week. Then first time I had to reboot it gets stuck in the loop.
Since I was away from home I could not get into recovery. I could get into HBoot (by holing Vol. Down + Power) but because I had a PC10IMG.zip file on my sdcard it would just go straight in to asking if I wanted to update from that with no way to select recovery. And of course I needed to have the sdcard in the phone to get an image from it!
So I have been running from the exploitable 2.2 Rom from the rooting procedure since. That can reboot no problems.
Today I tried a much more recent CM10.1 based rom - stuck in boot loop.
Then a tried the Rooted G2 stock ROM which is obviously much older. It booted correctly one time. Then I rebooted it (actually shutdown and then turned on, it doesn't have a reboot option) and now I'm stuck in the reboot loop.
I'm doing a factory reset and clearing the Dalvik cache after flashing each ROM.
I have also tried booting without the sdcard or SIM card, no change.
Something I have observed is that the phone will reboot once after flashing with every ROM, even the original ROM, but then either runs correctly or continuously reboots.
I can only think that possibly I have wrong phone model. I know that the previous owner bought this contract free so it may be some import. Perhaps it's actually a G2 and I'm using the wrong HBoot? I think that's unlikely as it would show an error during the rooting process.
Steve

I doubt you have the wrong hboot, it wouldn't even start if you did. I would do a complete wipe and format maybe change firmware as well. Backup SD and reformat that as well. If you have true radio soff (rooted via gfree) then you are safe to use one of the pc10img.zips I created here
http://forum.xda-developers.com/showthread.php?p=27796375 (see post 30)
Make sure to remove it from SD this time or at least change the name when done
This will give you new engineering hboot, updated 4ext recovery, .19 radio but all can be changed to whatever if you want.
After the flash reformat all in recovery and flash a new rom
Sent from my Nexus 7 using xda premium

Thanks for your input.
Updating the radio rom does seem tempting if potentially dangerous! The claimed power saving especially. I haven't ever used 4ext recovery but given how CWM seems to be failing me I might give it a try.
I don't wan to speak too soon here (but doing so anyway!) it looks like I may have corrected the problems by using SuperWipeG2+ from here: http://forum.xda-developers.com/showthread.php?t=1044992
After running that, which can easily be done from CWM, the phone booted first time with no reboots.
I'll update this if that did not fix it.
Steve

Yep spoke too soon!
However I have found a way to reliably recover but it's not straight forward.
Boot to recovery. Run SuperWipeG2+.
Attempt to boot the phone, boot fails as there is no ROM installed. This step seems important.
Boot to recovery. Install ROM from zip and Gapps from zip.
Reboot and phone will boot successfully and stay booted!
I then have to recover all my contacts and apps from Google which takes a further 20/25 mins.
Having done that I still cannot reboot the phone. If I reboot (or shutdown and power on) it is then stuck ion the boot loop and I have to do that all over again!
This means I cannot ever allow the phone to go flat.
Aaarrgh!
Any suggestions? It has been suggested that installing another ROM could fix this. Any specific ROM? Any idea why that would work?
I have found that the light sensor doesn't seem to be working and the suggested fix for that is to install a Sense based ROM and then switch back. I can't see how that could work either.
Steve

Yeah I've heard the sense ROM thing works, I don't see how but people seem to swear by it. I would suggest you change all your firmware, new hboot, new radio, new recovery and what not a new ROM. There are lots of good ROMs to choose from so I wouldn't know what to recommend for you, personally I almost always use gingerbread based ones
Sent from my Nexus 7 using xda premium

[Q] hensemod problem

Hello,
I've installed Hensemod a few times now, without any problems the first time I boot the phone.
Only after that, when restarting or turning the phone on again, it takes very long to start, like it's installing again and then the internal memory is suddenly full, even though I had about 100mb when turning the phone off. Also, all apps I installed are gone. In the applications list (in settings) they seem to still be there, but they're all 0kb and there's no shortcuts to them in the programs overview... Like I said, I've installed the Hensemod a few times now, and every time this happens.
Anyone knows how to solve this? I really like this rom, I can finally install and update all apps I want without the phone becoming unusable because of full internal memory! Thanks!
Carolien

I used HenseModv3 is a nice ROM, u must have to wipe all the data, cache and dalvick cache in the CWM recovery section, then install the HenseMod ROM.
If any other problem, plz share.

I followed all the steps stated in the development forum post, it works fine, just cant restart the phone because it will stop working...

My phone just continuesly restart...

Plug off ur battery, then go to CWM recovery, try to intall any other/different ROM.
I install each ROM by above method,i didn't use fastboot uncheck option.

Never mind I was just being stupid... I wiped the cache partition and not the dalvik cache. Sorry about that! Let's see if it will work now. Installing rom at the moment.

And again... first boot worked fine, after that I'm stuck in a bootloop now... Just like couldzxz. Too bad! I'll have to try yet another mod. Hope the next update of hensemod will solve this!

yes, u can try different custom ROM if any problems with a particular ROM
wait for next updates from Henry_01

I got stuck in bootloop too. I reqlly like the rom but well.. :/
Sent from my HTC Wildfire S A510e using xda premium

Okay, i've seen your problems.
I've tested latest build, but didnt rebooted it.
I suggest you all use a previous version (3).
Problem can be also kernel related.
I don't have time now (exams), I will make a proper working build after some weeks.
Don't hesitate to post here further, I want to know if it is ROM or phone related.
BIG EDIT: i will include link for version 3.
Thanks to djpc for a new hack which will solve reboot/kernel/overclock problems.
Expect a build and a proper test on friday or saterday.
I will change links now so that you will get a good version lol.

Somehow, the fifth time in installed the latest Hensemod rom, it worked like a charm. I can reboot, have installed and updated all apps I wanted and still got like 90mb remaining. Fantastic! Finally after 6 months I have the phone I wanted.
First and second install I couldn't reboot
Third install I got stuck in a bootloop
Fourth install gapps crashed every 2 seconds (due to calendar and contacts synchronization)
Fifth install = perfect!
I don't know how it happened, I just kept on installing this one so I could copy another rom on the sd card since I don't have an adapter or card reader for it.
Thanks!

[Q] ICS 8.0 Gone wrong. How to fix it?

Hi,
I'm not a very well versed with this rooting thing so I hope you guys can help me out here with some guidance. I have rooted a Desire HD for my friend quite some time ago. I follow step by step tutorial and managed to get it up and working with a custom ROM despite not knowing what half the steps are about.
Now, I tried to flash ICS 8.0 for him and it seems that it wasnt flashed properly as it is on a reboot loop over and over again. I did a factory restore before flashing and flashed using clockworkmod.
The main problem lies within I only remember parts and pieces of how I manage to root his phone the last time. How can I get it back working again without wiping off the root and s-off etc. Or is this just a small problem where I can reflash the rom without having to do all those again?
Let me know if you need any information about the phone. Thanks

If you are still able to get into recovery, make sure you do a FULL WIPE. Afterwards re-flash the rom and reboot your phone, should be fine.
---------- Post added at 10:07 AM ---------- Previous post was at 10:04 AM ----------
And something more:
if you're not sure what is the correct wipe you must do before installing a new rom, download this Super Wipe script (it's actually from ARHD but works with any rom ofcourse as it's just a full wipe), then you are 100% sure the problem will not lay with the wiping.

I tried to hold on to volume up key while powering on and all I get is 3 short vibrates and the yellow led on top blinking. The screen is blank, not even lit. Any idea what this means?

turn the phone off, pull the battery out and turn the phone on while holding the volume down button.
Now get into recovery and to a full wipe
so clear the cache partitions etc.
than flash again
btw ICS 8.0 does not excist
i gues you mean the 8.0 build from lord C ?

hi!
I've managed to get it to boot up in recovery mode! It was my stupidity to boot it up while pressing volume up when actually you had to press volume down. Got ICS up and running. Sorry for the confusion. Yep I was referring to the version 8 of the IceColdSandwich
I'll be sure to lurk around for more updates!!

orenzai said:
hi!
I've managed to get it to boot up in recovery mode! It was my stupidity to boot it up while pressing volume up when actually you had to press volume down. Got ICS up and running. Sorry for the confusion. Yep I was referring to the version 8 of the IceColdSandwich
I'll be sure to lurk around for more updates!!
Click to expand...
Click to collapse
No problem youre welcome
no questions anymore?
maybe about ics?

haha some bugs so far. the camera stopped working after 1 day. it focuses and snaps but the photo isnt saved. it worked when i first flashed it yesterday

Happend to me too. Use an alternative camera app for the issues with the cam
Sent from my Desire HD using xda premium

This is what happens when you dont read. These roms are always in the beta considered beta nad not really meant for people that dont know what they are doing or not willing to spend the time to read about it. Custom roms are not meant to be flashed to be part of the cool crowd. They are meant to help people learn how to do develop things on their own and how to trouble shoot issues.

zelendel said:
This is what happens when you dont read. These roms are always in the beta considered beta nad not really meant for people that dont know what they are doing or not willing to spend the time to read about it. Custom roms are not meant to be flashed to be part of the cool crowd. They are meant to help people learn how to do develop things on their own and how to trouble shoot issues.
Click to expand...
Click to collapse
I was expecting bugs. I'm on that likes to try out the newest things. But never mind, it's my friends phone and he couldnt bear with the bugs. It rebooted a few times randomly last night. Told me to flash it back to gingerbread for him. I'll keep an eye for the thread for more updates. Thank you all so much for the help guys!:laugh:

[GUIDE]Aroma Freeze FIX (test)

So I was having the same issues as everybody else was with Aroma freezing a million times when trying to install a ROM. I tried a few things but eventually stumbled apon a workaround that seemed to work.
I'll explain what I did then others can try it out. If it works for more/everyone else then happy days. If not then maybe I just got lucky.
OK so firstly I was on rooted stock ROM. I'm sure that it's not important really. But I want to mention every step.
I flashed TWRP recovery.
Rooted etc...Standard stuff
Then I used ROM managed to flash non touch recovery via the app itself.
Then made sure CWM was my default recovery in Rom manager.
Rebooted to recovery from Rom Manager.
Wipe data + caches
Install zip. In my case Trickdroid 5.1.0
Then as Aroma is booting up don't touch your phone for a good 2 minutes. I was actually out doing shopping and got to the till so left my phone untouched as it as on the welcome screen.
Then using the touch screen to select what I wanted etc I just went straight through. Not one freeze or install crash. First time.
I think it could be a few things perhaps. Maybe heat with Aroma putting high loads on the phone. Maybe the extra time sat let it cool a bit before getting going. Also perhaps Aroma just needs a little extra time to fully load properly.
Anyway please try my guide out. Maybe you cab miss some bits out. Hopefully it works. Post up if it did or didn't.
Good luck and happy flashing!
Sent from my Tricked out 'One'

My suggestion is that do not connect the USB cable when using Aroma, you should get less chance of freezing.

willingtonyuan said:
My suggestion is that do not connect the USB cable when using Aroma, you should get less chance of freezing.
Click to expand...
Click to collapse
Yes. I think this may be to do with the heat increase.
Sent from my HTC One using xda app-developers app

I tried your method this morning and Aroma froze on 30%. Tried it again and it froze on 3%.
Restored my nandroid and half an hour later tried the 'normal' method for installing a new Rom and it went though without a problem.
Sent from my HTC One

Tried it ...
It freezed on 80%

Damn seems like I was just lucky then. That sucks a bit.
Sent from my Tricked out 'One'

Actually does it matter if your AROMA freezes or not? Because my AROMA has froze on 2 occasions for both installations (One was 30% and the other was 97%) on both ROMs (Renovate and ARHD) and there were no errors or whatsoever when rebooted right after the freeze. Is it just me or..? Hmmm.

LordKuroda said:
Actually does it matter if your AROMA freezes or not? Because my AROMA has froze on 2 occasions for both installations (One was 30% and the other was 97%) on both ROMs (Renovate and ARHD) and there were no errors or whatsoever when rebooted right after the freeze. Is it just me or..? Hmmm.
Click to expand...
Click to collapse
well if it doesnt go fully through i would not trust it flashed fully one bit. i am too paranoid.

Dont use the touch function in Aroma Installer! Choose the options with volume and power button... It works for me!

LordKuroda said:
Actually does it matter if your AROMA freezes or not? Because my AROMA has froze on 2 occasions for both installations (One was 30% and the other was 97%) on both ROMs (Renovate and ARHD) and there were no errors or whatsoever when rebooted right after the freeze. Is it just me or..? Hmmm.
Click to expand...
Click to collapse
It doesn't harm your phone it just means it hasn't worked. You have to long hold the power then just try again until it works.
Sent from my Tricked out 'One'

yes only with volume and power button to operate the Aroma installer ...
works for my (previously only problems)
send for my HTC One

The War Horse said:
It doesn't harm your phone it just means it hasn't worked. You have to long hold the power then just try again until it works.
Sent from my Tricked out 'One'
Click to expand...
Click to collapse
Yes it has been successfully flashed, I was on Renovate ROM before my AROMA installation (for ARHD) froze on 30%. I might have left it there for awhile, thinking that the installation is still going on. I long hold the power button, rebooted and I've successfully flashed ARHD when I checked my settings. No crashes or errors at all.

Try clockworkmod touch freezes less, also I did what someone mentioned to clear dalvic and cache before attempting to install a rom, flashing everything else like trikdroid tweaks works allright..

LordKuroda said:
Yes it has been successfully flashed, I was on Renovate ROM before my AROMA installation (for ARHD) froze on 30%. I might have left it there for awhile, thinking that the installation is still going on. I long hold the power button, rebooted and I've successfully flashed ARHD when I checked my settings. No crashes or errors at all.
Click to expand...
Click to collapse
It will hang on 30% for a while anyway but still be installing. Perhaps you missed it finishing up?
Sent from my Tricked out 'One'

None of these work for me....I managed to get through a full ROM install ONCE but since then I haven't had any luck. Talk about annoying....

aroma kept freezing on me. what i did to finally get it to complete was dalvik/cache wipe in cwm classic first.
once aroma was booted be quick choosing your selections using the power button/volume controls then stuck my hand in the freezer with the phone monitoring the install so when it would complete i could be quick to click the next and reboot buttons.

I tried all recoveries.
Aroma always freezes/crashes.
This is so annoying.

I think at this point it is more of a luck of the draw type of things. I have tried a lot of combinations and after trying like 20 times, it finally went through. Still freezes if I want to install tweaks or themes but less than for a ROM....go figure.

I think everyone should have a go at unchanging between the home key for advanced and occasionally if it's stops vibrating feedback then use next button.
I've had a lot more success this way
Sent from my HTC One using xda premium

tontondavid said:
I think at this point it is more of a luck of the draw type of things. I have tried a lot of combinations and after trying like 20 times, it finally went through. Still freezes if I want to install tweaks or themes but less than for a ROM....go figure.
Click to expand...
Click to collapse
What works for me EVERY time with zero freezes is when you are at the first Aroma screen, hold both volume up and volume down at the same time, then push power while holding all three. It will advance to the next screen. Do the same for every screen and dont touch the screen unless you are selecting to remove or add something. I also found that if I wait too long on a screen before making a choice, it will freeze.

Battery Issue (?) Weirdest thing ever. HELP!

Hey guys, I've been having a really weird issue for a couple of days now. For your better understanding I'll list the things that I did with my d855 (Including some stupid ones)
1. I was on a cm 13 nightly rom, I was getting pretty bored so I decided to try out the fulmics 4.2 . So, I did. I flashed it without any hiccups. Everything seemed to be going fairly well. (I did make a TWRP backup and i also checked md5 of the zip file. It matched out)
2. I installed all of my apps that i use, Set up my wallpapers, nova, etc. I used it for a whole day and i noticed that the sot improved quite a bit from cm 13.
3. I'm in my bed, obviously not sleeping, you know how we do. And an incredibly stupid idea came to my mind. I thought "Hey! It's 4'o clock in the morning and i have school tomorrow, BUT WHO GIVES TWO ****S?! why not try out the lg g4 camera app ?!? Now, I had tried it before a long time ago, The camera didn't work, But the phone definitely did. So I wasn't paying too much attention on what the thread said about which version of android it was for. And just like a complete moron i downloaded the thing and proceeded to place the apk and 'libs' folder on my phone. I did give them proper permissions.
4. After that I went ahead and rebooted my phone. It booted just fine. I tapped on the camera app and it gave me an error. So i rebooted again, same as last time it booted up just fine but the camera didnt seem to work. Then suddenly it just shut down and then the lg logo flashed. It booted to the homescreen just fine. Then it turned off again and rebooted again. This loop started to go on and on forever.
5. So I decided to boot into twrp and wipe my art/dalvik cache and normal cache. Then i pressed on reboot. This time the phone didnt turn off, it optimized all of my apps. It took a while but i was on my homescreen and it didnt turn off. So I went ahead and opened up root explorer, located to where i pasted the camera, deleted the libs folder and the apk and also renamed my original camera app from .bak to .apk . Then I rebooted again, and it started the weird looping thing once again.
6. I realized that it boots up just fine if it's plugged in. But it seemed to turn off after 5 mins or so even when plugged in. I thought I messed up my rom or something so i decided to check by entering into recovery. But the result was the same. It just turns off. So since it was turning off even when i was in recovery i thought it was a faulty battery.
7. So i busted out my ZTE pocket wifi router and proceeded to take its battery and hold it up against my d855's battery pins with my finger. (Probably not safe) And the phone seemed to work just fine. I could use it for days without any issues. So at that point im like 110 percent sure its a faulty battery. Fair enough.
8. But, just to be certain i thought lets try doing a factory reset and flash the fullmics again. Result = Wank.
Then I wiped the cache again. Result = Wank. Then i decided to restore to the backup i made earlier that day. Result = An oreo to be given to the one with the correct guess.
9. At this point i wasn't 110 percent sure that it was a faulty battery. I KNEW it was a faulty battery. I was feeling it in my left testicle. So I decide to finally sleep cuz you know, gotta get some sleep, got a big day ahead of me tomorrow. Cuz I dont have my phone. So, I prepare myself and go to sleep.
10. The next day I decide to give it one last shot. I was thinking about wiping it clean and restoring to the backup again.
11. This is where the interesting thing happens. Bear in mind, I am NOT plugged in. Im on my G3's battery. I hold down the volume down and power button. The lg logo shows up. I let go of the buttons. I press them again. The white factory reset screen shows up. Now, I left my phone on that screen for legit 20 mins ladies and gentlemen and it didnt turn off once. But as soon as i click yes for twrp to launch the phone turns off before the twrp logo can show up. I tried the same thing with the ZTE battery as well, and it worked just fine. Only this time it actually booted to twrp. And it booted into the system as well.
Now, wtf is this? Wouldn't the phone turn off in the factory reset screen if it was faulty? And if the battery isn't faulty, then why does it work with a different battery but not with the lg one?
Now, My question to you guys, WHAT SORCERY IS THIS?
Help me out people. Expert help needed. TIA
*sigh*

Interesting story bro
---------- Post added at 04:44 PM ---------- Previous post was at 04:43 PM ----------
Let's see if I can reply today when I'm home

Hnk1 said:
Interesting story bro
---------- Post added at 04:44 PM ---------- Previous post was at 04:43 PM ----------
Let's see if I can reply today when I'm home
Click to expand...
Click to collapse

2000ftt said:
Click to expand...
Click to collapse
Hi
well, I have had used different variants of LG G3s and I found that some ROMS had certain bugs. Like in Fulmics and Cloudy, if you turn off your device on AT&T variant, you can not turn it on again unless you replace the battery again. Even that used to occur on a reboot so it depends really which bugs you might face.
It could be your battery but I will suggest you few things you can do. Firstly, charge your battery to 100% and wait half an half more before you unplug your charger. Next thing, You calibrate your battery as well, maybe there might be an issue. You can find battery calibration tool by Nema in the playstore.
Next thing I would suggest you to move back to STOCK Lollipop / Marshmallow which you can flash via TWRP or KDZ or TOT method. See if that works for you or not. When I faced the issue of my device not booting after a restart or power off unless i reinsert the battery, this helped!
Last, clear dalvik cache / etc and see that helps too. (Would be done if you flash the KDZ)
Also, if you are flashing roms, for example lollipop stock before you flash a new custom rom, make sure you restart in betwee. i.e
flash lollipop stock via twrp. Restart and then install custom rom of your choice. Flashing over sometimes does not work well.
Good Luck and I hope you have a better story for me where everyone lives happily ever after!