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.
Related
I have an interesting problem, kind of. Bought my phone second hand as supposedly unlocked & debranded but on boot up it after the HTC logo I get the Virgin Media logo, not really an issue though. Anyway the problem is when I switch the phone off and then switch on again it boots up fine to the home screen and then it will reboot itself and carries on doing this. i.e. boot up to home screen then reboot again continuously.
To get out of this reboot loop I have to remove the sim & boot the phone with no sim in it then switch off and insert my normal Vodafone phone sim and switch on again. after that the phone is fine until I power down and then the same thing happens.
Anybody else experienced this or got any ideas?? It came with 1.15.405.4 firmware already installed and I have tried reflashing with the same firmware using the goldcard method & it worked but the problem remains. When the sim registers on the network is when the reboot loop seems to start.
did you try reflashing it ?
hold down the side button (down) and press on at the same time.
then select erase data and press on again
if you bought it second hand, its hard to say what the previous user has done with it ...
Yep tried reflashing it, just about to reflash again with an older rom. It's just wierd that a sim card authenticating to the network would cause a reboot loop.
TieT said:
did you try reflashing it ?
hold down the side button (down) and press on at the same time.
then select erase data and press on again
if you bought it second hand, its hard to say what the previous user has done with it ...
Click to expand...
Click to collapse
Maybe it's a dumb question - But I'm having some issues that doesn't seem to get solved by a factory reset - Would it be an idea to reflash it for this, so the phone gets a fresh rom?
How would I do it specifically? Do you know of a guide somewhere?
sudman said:
Yep tried reflashing it, just about to reflash again with an older rom. It's just wierd that a sim card authenticating to the network would cause a reboot loop.
Click to expand...
Click to collapse
have you tried a different sim card ?
Ye tried a different sim card, boots fine and all is good till you reboot the phone and then the same happens again. Anyways flashing was a disaster this time round as I was doing it on my work pc and Symantec kicked in thinking it found a virus with adb.exe and halted the process & quarrantined the file. Now everytime I try and reflash on a different PC I get the dreaded error(110):file open error. Disconnect the phone & all I get is a black screen & HTC logo. Nice. Thanks Symantec you've just bricked my Desire!!
*UPDATE* - Fixed.
Removed the battery, left it for a few hours then reflashed on a different pc and it flashed fine. Then thought I'd try & repeat so reflashed with the older rom from here (originally used the newer rom posted on Modaco) and got the error again and again couldn't flash back to the newer. Removed the battery left for an hour and then could reflash again and get it working!! Wierd
I had the same problem.
My Solution: remove battery, remove the SIM, put battery reboot, turnoff, remove battery, put SIM, put battery, boot
first i want to excuse my bad english,hope you will undestand what i´m trying to say.
i have the same problem since a few days.
first time i notice it,was when the desire was charching and i used it a bit,it restarts again and again.so i put out the battery and wait a few minutes,than it works.
it´s also,when i use it a long time with wifi or 3G....the the phone turns off and i have the boot loop.
but when i take out my sim,it works fine.
my question is,do i need a new sim or is it a hardware problem?
does anybody know?
greetz from germany!
sorry, wrong thread
same here.
Tequila98 said:
first i want to excuse my bad english,hope you will undestand what i´m trying to say.
i have the same problem since a few days.
first time i notice it,was when the desire was charching and i used it a bit,it restarts again and again.so i put out the battery and wait a few minutes,than it works.
it´s also,when i use it a long time with wifi or 3G....the the phone turns off and i have the boot loop.
but when i take out my sim,it works fine.
my question is,do i need a new sim or is it a hardware problem?
does anybody know?
greetz from germany!
Click to expand...
Click to collapse
i have the exact same problem!! any solution? after that the phone will boot loop over and over! damn!
I had the same problem last week.
I suspected it had to do with the EXT3 partition.
Solved it by first flashing the OTA 2.2 ROM (for rooted users) as this does not use the EXT3. Then used Rom manager to recreate the EXT3.
Now all ROMs that use the EXT3 run fine!
hmmp
as long as i know, i did not install anything on my phone lately so thats the problem so far and i think tequila98 also having the same problem as me, cause when i remove my sim card the phone works fine. but ive reset my phone yesterday and not restarting so far hope this will continue.
I really wished there was a dead fix to this problem we are all having!
My problem:
My phone was running fine until a few weeks ago. There was no rebooting problems when I first got my phone (April) and when I flashed my phone for the first time (May). Happened a few weeks ago when I was browsing on YouTube where my phone suddenly restarted on it's own.
Before it was once a couple of days, now it has gotten more frequent and annoying.
I don't think the heat is the problem because I don't go on the internet much because of my data plan. I use wifi when I browse the web, youtube, etc. And I certainly don't use Google maps or any heavy duty applications. That's just what I think...
My phone rebooted 3 times today in a time span of 4 hours? I noticed that my phone rebooted itself when I use the camera to take a picture or video. Doesn't happen everytime, but that's what happened today. Also, when my phone rebooted today, my application Advanced Task Killer was automatically removed from my phone! That was weird... But I experienced another reboot even after having the app removed.
I really hope someone can find the core of this problem and fix it!
My phone is running on DeFroST 2.0b Android 2.2
My battery stats: 42% for display, 26% for cell standby, 21% for phone idle, 4% for android system, 3% for voice calls, 2% for android OS
jxleung said:
I really wished there was a dead fix to this problem we are all having!
My problem:
My phone was running fine until a few weeks ago. There was no rebooting problems when I first got my phone (April) and when I flashed my phone for the first time (May). Happened a few weeks ago when I was browsing on YouTube where my phone suddenly restarted on it's own.
Before it was once a couple of days, now it has gotten more frequent and annoying.
I don't think the heat is the problem because I don't go on the internet much because of my data plan. I use wifi when I browse the web, youtube, etc. And I certainly don't use Google maps or any heavy duty applications. That's just what I think...
My phone rebooted 3 times today in a time span of 4 hours? I noticed that my phone rebooted itself when I use the camera to take a picture or video. Doesn't happen everytime, but that's what happened today. Also, when my phone rebooted today, my application Advanced Task Killer was automatically removed from my phone! That was weird... But I experienced another reboot even after having the app removed.
I really hope someone can find the core of this problem and fix it!
My phone is running on DeFroST 2.0b Android 2.2
My battery stats: 42% for display, 26% for cell standby, 21% for phone idle, 4% for android system, 3% for voice calls, 2% for android OS
Click to expand...
Click to collapse
same problem here guys why desire have a this problem ? why no one cant find any solution ?
PLZ help us
Ehsan021 said:
same problem here guys why desire have a this problem ? why no one cant find any solution ?
PLZ help us
Click to expand...
Click to collapse
It's probably hardware problem with motherboard. Therefore I recommend you to take your phone to repair center and they should replace mobo with new one. That's what I did and now everything is ok.
I am having the exact same problem. Seems to be related to the SIM.
But the SIM works fine in another phone.
Did anyone find any more information?
If you get random reboots its most likely ther motherboard there is a massive thread about it on the forums. You need to send it off to a HTC repair centre.
Just got this problem.
I rooted yesterday. Today I made a nandroid backup. After that the phone is in a reboot loop.
How is this possible from just and backup???
Tnx.
R
Edit:
Restored backup and is working fine again.
nandroid backup loop
rottunix said:
I rooted yesterday. Today I made a nandroid backup. After that the phone is in a reboot loop.
How is this possible from just and backup???
Click to expand...
Click to collapse
I have the same problem.
rottunix said:
Restored backup and is working fine again.
Click to expand...
Click to collapse
I will try it. Maybe the backup is not only a backup but also a remove? Strange.
I will comment if this works also for me.
EDIT: Restore helps
Hello!
For some time now my phone's been rebooting itself completely random it seems. I just got it back after sending it away to get this issue fixed. Obviously the "repair" didn't really do anything at all. All they did was to flash the latest software apparently.
I got quite fed up with the crashing and rebooting stuff, and figured that it wouldn't hurt to try to flash a custom ROM, in this case I chose to root the phone and try MiUi. I had no clue wether it would solve the issue I'm having, but I figured it was worth a try. So i rooted the phone and flashed the latest version of MiUi (1.11.18).
At the start it seemed like it had worked, and had stopped the phone from crashing. But after some time I realized that the issue is still there, only difference now is that it ONLY crashes when I lock the screen with the Power-button. EVERY SINGLE TIME I do this, in a matter of minutes it will either reboot or just turn black and totally unresponsive. Only way to get it on again is to take out the battery and put it back in.
This is starting to annoy the **** out of me, so I talked to my brother for advise this morning, and he told me to wipe my Dalvik Cache. So I did, and nothing changed, the phone keeps on living it's own life.
I have absolutely no clue what info you guys might need to help me with this, but I'll start with this:
Phone: HTC Desire HD
Android-version: 2.3.7
Kernel-version: 2.6.35.14-cyanogenmod-g319b6e2
ROM: MiUi 1.11.18
Also, the motherboard's been switched once, cause of another issue that is now gone.
ANY help is appreciated, I just want to be able to use the phone normally!
EDIT: Also it seems that the phone won't reboot or crash whenever it's charging.
Sounds like a hardware/software issue your best bet is getting a replacement and re rooting .
Sent from my Tweaked out RCmix3D myTouch 4G via xda premium !
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've had the premium for almost 3 weeks now. On the second day it crashed whilst I was listening to music +browsing in chrome. Thr screen turned inky and then turned off. Since then I haven't had anything similar happen, but I have had 1 or 2 reboots. Are these signs something could be wrong with my phone? I have like a week to get a replacement. It's rev 2, other than this I have no complaints.
Try to remove cach in recovery mode, maybe that will fix your problem. If not let me know
This has been happening to me as well and actually results in boot loops. Since I have Liveboot, I can see the dmesg output. It says "Failed to start system services. Invalid abi: ABI" or something like that. I'm RomAur so maybe that has something to do with it?
It has happened to me 3 times this week. Also RomAur 1.1. It seems to happen when i am heavy multitasking, definitely related to chrome I think.
I'm completely stock... I use chrome as my main browser. The last time it happened it froze on wake whilst it was charging... The first time I was listening to music and doing something else which I can't recall. The phone has 3gb of ram so I don't really clear my recent apps as often as I did on my S4. It happens once a week on average for me. Cache wipe didn't do anything.
You could've easily gotten a faulty device. A but load of hardware issues can do that and I would advice you to do a factory reset, update to the latest F/W (flash it if not available in ur region), see if it happens again and if it does - get a replacement
Gd luck
If you're totally stock this might not help but I narrowed my problem down to xposed being unstable as crap on mine at least. Hasn't happened since I went back to stock fw (using. 200 generic FR). But I tried to install xposed and I got the three light reboot immediately.
TheImmutable said:
If you're totally stock this might not help but I narrowed my problem down to xposed being unstable as crap on mine at least. Hasn't happened since I went back to stock fw (using. 200 generic FR). But I tried to install xposed and I got the three light reboot immediately.
Click to expand...
Click to collapse
exactly like that on my z5 . when i flash the xposed uninstaller , it doesnt randomly reboot, but when i flash xposed , it does.i was thinking of flashing .200 ftf and then flashing xposed from the beggining (before i install any apps ) to see if it helps , but you said you did it??
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