Hello Ive Never Been The Person To Post My Problems because somewhere along the line someone has the same problems as me and i usually find a fix or a flatout yes or no if it can be fixed or id take it upon my self to mess with . but seeing as how this is my first ever decent phone i dont want to mess it up any further than i already have . what i can tell you is that i was switching from the renegade rom Debloated back to a backup i made with twrp after i only rooted it no rom installed on that backup . i didnt like the renegade rom debloated so i wanted to go with the full version however somewhere in between me flashing it just started a boot loop of Optimizing Apps 1-32 then before its even close to being it reboots. so i went and downloaded the latest 6.0.1 firmaware and reflashed . and the same thing is happening and now in download mode it says i dont have an meid and my CURRENT BINARY is Samsung Official But my System status is Custom FRP Lock OFF Secure Download Enabled . i can get to normal default recovery and i can still flash TWRP in odin and use it on my phone . ive exhausted all options ive found online . i would post a logcat but i dont have android studio . last time i had it for some reason it couldnt fully install .
Edit: It makes it to optimizing apps 1 out of 32 then cuts at 31 then reboots and does the same thing all over again
Edit 2 . on back it says model is g920t but everything on the phone says g920P . so I don't want to use .pit yet cuz I don't know what I'm really working with . the phone is sprint but the model letter T is for T-Mobile . so the previous owner unlocked it I assume . so I knows there's more to it than what I can see
. i dk what else to do im screwed .
Yea if its a tmobile thats the issue trying to flash sprint. Now a while back we were haveing issues with lg g3s and g4s being knockoffs. Being sold as refurbs made from many diffrent model nums. Which were causing loads of problems. If the model says tmobile u should only be using tmob firmwares and such. Kinda weird do a serieal number check and see what ot shows it as
---------- Post added at 04:26 PM ---------- Previous post was at 04:24 PM ----------
TheMadScientist420 said:
Yea if its a tmobile thats the issue trying to flash sprint. Now a while back we were haveing issues with lg g3s and g4s being knockoffs. Being sold as refurbs made from many diffrent model nums. Which were causing loads of problems. If the model says tmobile u should only be using tmob firmwares and such. Kinda weird do a serieal number check and see what ot shows it as
Click to expand...
Click to collapse
Might be a refurb with a tmobile casing on it
Thanks . But after i flashed the pit i lost the sprint boot up splash and it only booted the galaxy s6 words over and over so i thought i ruined it so i put it to the side and forgot about it and let it die . Then i look at it today and im like ahh screww it lemme turn it on . And low and behold it fixed itself !!! What ?! Idk w
How but im so happy ! Def gunna leave it stock for a bit lol
Trippyy Doee said:
Thanks . But after i flashed the pit i lost the sprint boot up splash and it only booted the galaxy s6 words over and over so i thought i ruined it so i put it to the side and forgot about it and let it die . Then i look at it today and im like ahh screww it lemme turn it on . And low and behold it fixed itself !!! What ?! Idk w
How but im so happy ! Def gunna leave it stock for a bit lol
Click to expand...
Click to collapse
Thats luck.
hi im having the same issue here, my phone is sprint, i got it unlocked for tmobile, i was on team spr PB6 version, i decided to update to renegades pg1, so i used odin to flash pg1, then i flashed Renegades DB, everything was working fine, until the rom control settings werent working so i thought it was a bad flash, Reflashed renegades and everything seemed to be going okay, until it went to boot, it said "installing system updates" blue screen with a loading bar, it went to 32% then said erasing then booted up, thought that was weird, then it went to android app optimization, it wouldnt pass that screen it just randomly restarted but eventually it went all the way through and phone booted up, but now the phone restarts randomly, ive gotten it past the first screens (inputting wifi passwords the account screen all that stuff) after restarting numerous times i finally can look into the about section for 5-10 seconds before phone restarts, i noticed the imei and all other settings in "status" are either not there or say unknown, also the baseband says version unknown.
anyways im wondering if anyone has any help or can lead me into a direction to fix this. i really need my phone for work and ive been out for 3 days trying to figure this out, hopefully i can fix it and someone can help me. thank you for your time.
timmaaykush said:
hi im having the same issue here, my phone is sprint, i got it unlocked for tmobile, i was on team spr PB6 version, i decided to update to renegades pg1, so i used odin to flash pg1, then i flashed Renegades DB, everything was working fine, until the rom control settings werent working so i thought it was a bad flash, Reflashed renegades and everything seemed to be going okay, until it went to boot, it said "installing system updates" blue screen with a loading bar, it went to 32% then said erasing then booted up, thought that was weird, then it went to android app optimization, it wouldnt pass that screen it just randomly restarted but eventually it went all the way through and phone booted up, but now the phone restarts randomly, ive gotten it past the first screens (inputting wifi passwords the account screen all that stuff) after restarting numerous times i finally can look into the about section for 5-10 seconds before phone restarts, i noticed the imei and all other settings in "status" are either not there or say unknown, also the baseband says version unknown.
anyways im wondering if anyone has any help or can lead me into a direction to fix this. i really need my phone for work and ive been out for 3 days trying to figure this out, hopefully i can fix it and someone can help me. thank you for your time.
Click to expand...
Click to collapse
Its a long shot but it fixed my phone ... let it fully die then charge it and turn it on
Just wanted to confirm, i let my phone reboot itself all night till it died, plugges in the phone for a bit and turned it on. Works magically. Who knows what was wrong thank you for your advice. Looks like my prayers are anwsered.
Common S6 issue, seems to fix most phones with this rebooting problem
Related
Hi, guys im having some issues and would like some expertise. Okay so i have an s4 the model is m919v but the model is unrelated to the problem. I was running custom roms and have been for a few months and i have a phone that has a locked sim. I heard from someone that i can flash an older version of my modem and get the service menu to unlock... point is i did it and it didnt unlock BUT THATS NOT MY ISSUE. I decided to then revert to stock because my phone was being really glitchy after i tried the unlock. Now i restored my phone and got a custom recovery installed a custom rom that was working flawlessly before is now also being glitchy the same way after i tried to unlock it,
These are some glitches im experiencing:
1) phone app is taking a long time to load and it doesnt type in numbers fast
2) when i call someone it just freezes and i cant go to the call screen
3) no notification sounds coming from my phone it just vibrates but doesnt ring
and im sure a few more
IM SURE THESE HAPPENED AFTER I WENT INTO THE SERVICE MENU AND TRIED TO UNLOCK MY DEVICE.
Someone please tell me what i can do to fix this because ive already reverted to stock once.
zee24 said:
Someone please tell me what i can do to fix this because ive already reverted to stock once.
Click to expand...
Click to collapse
You just might want to re-flash the stock rom and before rebooting, clean all the cash and do a factory restore. That should restore the operation to your device.
Only your Pure stock roms will contain any of the modem/boot stuff, if my information is correct.
Aloha and Good Luck!
D851 here, When ever i switched from cloudy 2.5 to blisspop 4.0 and after wiping everything i flashed a various of radios bootstacks and etc to make it boot after many failed attempts to boot ( it boots up but after 4 or so seconds after the lg logo the screen turns black and doesnt turn back on until after i pull out the battery) it worked after i flashed the rom WITHOUT a custom kernel so naturally i booted up just fine and thought maybe now i set up everything on my phone and tweaks i should go back and flash a custom kernel i used to use (777 r16) but then it gave me the problem i faced before the black screen after the lg logo no kernal would work. THEN another problem arised similar to the freezing on the black screen randomly during a usage thru my day the phones screen would be unresponsive animations but touch wouldnt work and i know its not my screen cause when i flash back to cloudy it works fine the freezing happens at least every 5 mins. someone halp?
i know this thread is kinds old...
but i have this same issue too... I found if I switch batteries the problem isn't as bad... but, then it becomes bad again. Its weird. Before I swapped batteries I couldn't even login with my google account, after a fresh flash. then after I swapped batteries (gf has same phone) I was able to get through to the end and setup the phone. But, then an hour later it started happening again....
OP, did you find a solution?
warrior420 said:
i know this thread is kinds old...
but i have this same issue too... I found if I switch batteries the problem isn't as bad... but, then it becomes bad again. Its weird. Before I swapped batteries I couldn't even login with my google account, after a fresh flash. then after I swapped batteries (gf has same phone) I was able to get through to the end and setup the phone. But, then an hour later it started happening again....
OP, did you find a solution?
Click to expand...
Click to collapse
i actaully did i think one of the problems was maybe flashing over the same kernel? see what happened was after i gave up flashing the kernel i just flashed without it and to my surprise the build actually came with the kernel pre-installed...shocker and so i had no need to flash over the kernel that i wants because the maker of g3 tmo blisspop already had it in his build and it boots up fine( DISCLAIMER: i cant say this about other roms because the only one i actually tested and wanted was blisspop)
thelgog said:
i actaully did i think one of the problems was maybe flashing over the same kernel? see what happened was after i gave up flashing the kernel i just flashed without it and to my surprise the build actually came with the kernel pre-installed...shocker and so i had no need to flash over the kernel that i wants because the maker of g3 tmo blisspop already had it in his build and it boots up fine( DISCLAIMER: i cant say this about other roms because the only one i actually tested and wanted was blisspop)
Click to expand...
Click to collapse
Okay.
Well, when I was flashing I never flashed a kernel.
Ill be getting a brand new Anker Battery in the mail today. Ill report my findings.
I ended up going to a stock based rom and the issue never happened. So I stuck with it. Ill have to do some testing later and ill let you know how the battery works.
It's not the battery
I downgraded my T-Mo G3 since I couldn't root it with LP on it. Went back to 4.4.2., rooted it, TWRP'd it, and installed the latest CM12 Nightly, Gapps, SU, etc.
As long as the sim card was OUT the installation was great on wifi only, As soon as I put it in it shut off right after, or during boot up. Take the sim out and it works. And yes, the only way to get back into recovery was pulling the battery and doing the key press to recovery. Mystified.
If I find out anything, I'll post it here.
I'd say do a complete return to stock, upgrade via LG Mobile Support tool all the way to 20G, see how it works stock for a while. Then root ( http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197 using the first method) and see what happens.
so i flashed the official marshmallow for lg g3 on january. everything was fine. today the phone just stopped working. i had no previous signals like glitches or bugs, it was perfect but now its just gone.
so after this 3 months of usage, while listening to music, the phone stopped working (without even touching it)
if i reboot it, it gets me into a boot loop and when it doesn't its just black screen
SOMETIMES THO i have the luck of it booting but i cant do nothing as it constantly shows android.process.com stopped working (i dont remember the exact name) but anyway after 1 minute it reboots himself because of the constant crashes.
if i enter download mode i get a message that sounds like this:
KERNEL CRASH!
demigod crash handler: kernel crash!
*something about dload mode and get ram dump*
*here info about phone like revision and serial*
internal error: oops: PREEMPT SMP ARM
linked in: texfat(p0)
*random numbers*
*error codes*
Kernel panic - not syncing: fatal exception
sorry im so vague about it but im writing this from memory right now. if you need more just ask
as a matter of fact, the only thing that this phone has is the MM official rom flashed (poland one)
its not rooted neither with custom recovery
i still have one year warranty, if i bring it to them its ok or i have to pay? i say this considering mm hasnt arrived yet to my country through ota. the main thing im concerned is if i can recover any of my photos/videos/music as it has some sentimental value but its not a must, the main priority is to get the phone working
and also the phone is recognized as lg g3 when plugged in computer, put cant enter download mode because of the reason above.
no recoveries as i said, and im pretty sure that if i get somehow to factory reset it will stay the same as the kernel doesnt get reflashed (im not a pro, just intuition, correct me if im wrong)
any help is appreciated!thank you in advance
just if anyone gets this problem and doesn't know how to solve it, its a hardware problem, not software, so warranty does cover it
As they won't give me much details, the only thing i know its that a specific component from the phone stopped working
does anyone have an idea of what component from the phone is responsible for that? just so i have an idea of what happened.
Friend of mine got this issue. I changed his emmc, and now worked perfectly
Sent from my LG-D855 using Tapatalk
same issues as mentioned above
wiwid.colgate said:
Friend of mine got this issue. I changed his emmc, and now worked perfectly
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
can u plzz tell in detail how u fixed this
Hi
I've been going back and forth for a couple of days now , thinking if i should post this post or not .
so here it goes , i had a n910p for a couple of months now it was on 4.4.4 when i got it and it worked just fine no problems except some dying battery related problems -phone shuts down when using the flash camera, the phone shuts down without any warning and then i find the battery at 5% when turned back on - ( i didn't know it was a battery problem back then ) , but everything else was just fine .
-i should mention i'm in Jordan not the US so the phone is unlocked sim .
So i wanted to upgrade to Marshmallow maybe the problems got fixed , so in order to upgrade to MM i had to first upgrade to 5.x.x and i did and tested it for a couple of days it had some Freezes but nothing unmanageable , i changed the battery while i was on 5.1.1 there was no problem here no freezes no random shutdowns .
And then i upgraded to MM that's when the problems started to show one after the other , all described here and add to that i had to add and remove the battey 3-4 times in order to turn on the phone.
so i thought to my self it started since i upgraded to MM , maybe if i downgraded to kitkat it'll go away .
i downgraded to 4.4.4 not the stock just to see if it was any better, and it was !!
no freezes no random shutdowns except for one problem if i wanted to shutdown the phone or do a restart i had to remove and add the battery in order to get back on .
so my question is , why is this happening ?
is it a hardware problem and just my luck it started popping out when i started upgrading ?
why is it there is less problems when i downgraded to Kitkat ?
P.S: i upgraded to 5.x.x first by flashing it, because i couldn't upgrade OTA .
Mohannad_Almasharqa said:
Hi
I've been going back and forth for a couple of days now ,
.......
P.S: i upgraded to 5.x.x first by flashing it, because i couldn't upgrade OTA .
Click to expand...
Click to collapse
This problem is a little confusing and beyond me, but I have to ask and suggest one thing.
Instead of doing OTA, Have you tried to just use odin to flash the Marshmallow firmware you want?
Mohannad_Almasharqa said:
Hi
I've been going back and forth for a couple of days now , thinking if i should post this post or not .
so here it goes , i had a n910p for a couple of months now it was on 4.4.4 when i got it and it worked just fine no problems except some dying battery related problems -phone shuts down when using the flash camera, the phone shuts down without any warning and then i find the battery at 5% when turned back on - ( i didn't know it was a battery problem back then ) , but everything else was just fine .
-i should mention i'm in Jordan not the US so the phone is unlocked sim .
So i wanted to upgrade to Marshmallow maybe the problems got fixed , so in order to upgrade to MM i had to first upgrade to 5.x.x and i did and tested it for a couple of days it had some Freezes but nothing unmanageable , i changed the battery while i was on 5.1.1 there was no problem here no freezes no random shutdowns .
And then i upgraded to MM that's when the problems started to show one after the other , all described here and add to that i had to add and remove the battey 3-4 times in order to turn on the phone.
so i thought to my self it started since i upgraded to MM , maybe if i downgraded to kitkat it'll go away .
i downgraded to 4.4.4 not the stock just to see if it was any better, and it was !!
no freezes no random shutdowns except for one problem if i wanted to shutdown the phone or do a restart i had to remove and add the battery in order to get back on .
so my question is , why is this happening ?
is it a hardware problem and just my luck it started popping out when i started upgrading ?
why is it there is less problems when i downgraded to Kitkat ?
P.S: i upgraded to 5.x.x first by flashing it, because i couldn't upgrade OTA .
Click to expand...
Click to collapse
Odin MM like suggested.. Don't do any mods. If it persist, then you might be looking at faulty hardware ie main board.
i just flashed MM after reading your replay , and will test it out.
any tips on what to do with the phone if it's a hardware problem ?
so right at the first boot i had this error shown in the images (attachment)
i removed the battery and restart the phone and it booted correctly , the same problems began to show freezing random restart and it keeps booting to recovery and i had to add and remove the battery a couple of times to turn the phone on .
i returned to stock 5.1.1 apparently it's the most stable thing i can use right now , honestly i'm puzzled on this problem i'm quite sure it's hardware and software somehow and if i send it to a local shop they probably will say "i don't know what seem to be the
problem "
so i'm just going to keep using it until it becomes a replacement parts for his other brothers . :crying:
I'm no expert, but i've poured through dozens, maybe hundreds of pages about this issue. Happened entirely with MM, and most people have thrown their hands up calling it "faulty hardware".
All the accounts, the symptoms, the timing, and the root problem (eMMC error) point to a bug in MM that messes something up when it installs itself- *sometimes*. Those unlucky enough to catch this bug are stuck with it, and end up with essentially a brick or returning it.
Hardware doesn't make sense, not when the issue completely coincides with an update. Unfortunately, I don't know how to completely 100% wipe this device and re-load it from scratch, which is what I think it's gonna take. I don't even know what all *can* be wiped 100% :/
akira6968 said:
I'm no expert, but i've poured through dozens, maybe hundreds of pages about this issue. Happened entirely with MM, and most people have thrown their hands up calling it "faulty hardware".
All the accounts, the symptoms, the timing, and the root problem (eMMC error) point to a bug in MM that messes something up when it installs itself- *sometimes*. Those unlucky enough to catch this bug are stuck with it, and end up with essentially a brick or returning it.
Hardware doesn't make sense, not when the issue completely coincides with an update. Unfortunately, I don't know how to completely 100% wipe this device and re-load it from scratch, which is what I think it's gonna take. I don't even know what all *can* be wiped 100% :/
Click to expand...
Click to collapse
Here is the thing though (I have the same issue). If you remove the battery and put it back in, say 30 seconds later, it won't turn on. If you remove the battery for like 5 minutes and then put back in, it might turn on. I'm talking about the first little vibrate it does when holding the power button to turn on. It really acts like a hardware issue to me. The only work around that has worked for me is an app called wakelock. Using this app and selecting partial partial wake lock makes the phone run completely normal.
What REALLY sucks right now is that I have an OTA update waiting for me and the phone needs to reboot to install. The phone won't reboot. When it turns off, it won't turn back on without removing the battery for 5+ minutes.
IT is the MM Update
Im not an expert or anything but i have the same problem cant update cuz phone has to be restarted i finally had enough of it took it in told them (sprint) to update it thay said thay did but thay didnt. Called and thay couldnt fix it so i said the heck with it and i flashed it still doe the same must use wake lock app wish someone could figuer this out.
gbennett21 said:
Im not an expert or anything but i have the same problem cant update cuz phone has to be restarted i finally had enough of it took it in told them (sprint) to update it thay said thay did but thay didnt. Called and thay couldnt fix it so i said the heck with it and i flashed it still doe the same must use wake lock app wish someone could figuer this out.
Click to expand...
Click to collapse
Yes having the same issue as well but now even the wakelock app won't keep it. The phone wil stay for maybe an hour, then reboots and will continue to reboot until I take the battery and then start it again afterwards. The length of time the phone stays on varies really and it could be as long as 3 or 4 hours, but it will definitely reboots itself, I cannot got 1 day without this happening. At this point the phone is unusable. I am on another phone at the moment.
I did flash the MM updates (even went back 3 or 4 older versions) using ODIN and same issue. I am debating whether I flash an older Lollipop version and see if that makes a difference.
Hello Guys,
This is my first time posting on xda forums,
I rooted my Sm g92t from t mobile,
everything was working fine until i tripped the oem unlock,
restarted the device only to be met with frp block.
searched online and tried to fix it, got it to work
but ended up with unknown baseband and imei null.
Things i've tried
1. Run several roms, all stock
2. tried to use z3x tool to fix but no luck,
3. tried restoring efs backup, no luck since i didnt know much about efs folder by then.
One funny thing is that, whenever i run a new rom,
installing system update which comes up the rom has finished loading doesn't
reach 100%, it gets to 32% and switches to erasing and continues to boot.
I've lost hope, no T-mobile or Samsung service centre close by, i really need help.
Katinc said:
Hello Guys,
This is my first time posting on xda forums,
I rooted my Sm g92t from t mobile,
everything was working fine until i tripped the oem unlock,
restarted the device only to be met with frp block.
searched online and tried to fix it, got it to work
but ended up with unknown baseband and imei null.
Things i've tried
1. Run several roms, all stock
2. tried to use z3x tool to fix but no luck,
3. tried restoring efs backup, no luck since i didnt know much about efs folder by then.
One funny thing is that, whenever i run a new rom,
installing system update which comes up the rom has finished loading doesn't
reach 100%, it gets to 32% and switches to erasing and continues to boot.
I've lost hope, no T-mobile or Samsung service centre close by, i really need help.
Click to expand...
Click to collapse
IDENTICAL Problem. Flashing original ROM T-Mobile QE1 and after reboot it goes to 32% and then resets and gets stock in T-Mobile.
I tried few things nothing is working. I have Z3X box but I am not sure how to pinpoint problem.
Anyone can suggest something >?<
Hey,
were you able to fix your phone? I did fix mine using a combination rom.
Bootloop
How did you fix it with the combination of roms