I tried to revert back to stock to have t-mobile unlock my phone; i tried to flash gb through odin.
When it restarted it keeps crashing on the "touch android to begin"
I came from Infamous 2.9
I appreciate any help, I have to leave out of the country in two days and was hoping to get my phone unlocked and ready.
tia
mikejackal said:
I tried to revert back to stock to have t-mobile unlock my phone; i tried to flash gb through odin.
When it restarted it keeps crashing on the "touch android to begin"
I came from Infamous 2.9
I appreciate any help, I have to leave out of the country in two days and was hoping to get my phone unlocked and ready.
tia
Click to expand...
Click to collapse
when you say crashing do you mean the phone locks up, or just reboots? Sounds like a bad d/l of the stock image. I would redownload...
Have you tried to factory reset in recovery to see if it will boot after that?
sent from my T989 full of CM awesomeness and a touch of Venom from the Darkside!!
Make sure you use one of these stock GB or ICS from this thread with Odin
http://forum.xda-developers.com/showthread.php?t=1414341
I experienced the same thing. A bunch of force closes at the first screen. So, I Odin the phone with stock ICS rom to get everything back in the working condition. This resolved all the issues.
Change the kernels too, you said u were on infamous (ics) and go back to gb
Sent From My Galaxia with The Jedi
thanks for the help guys, i changed back to a stock rom and it all worked, sorry forgot which one, t-mobile sent me an email saying they couldnt give me an unlock code, so i just ordered an unlocked phone and hopefully it will get here in time for my trip.
Hey everyone,
So two night ago I received a notification on my GS3 saying a new update was out.
When I tried installing the update it rebooted into recovery and failed at 24%....weird. I was running Rogers stock rom and recovery at the time so this shouldn't have happened, and I would like to know why for future reference.
I also tried updating via samsung kies. But when I tried this, it said my device wasn't compatible to update via kies????
So I ended up download the LK4 update off sammobile website and installed it using odin.
Anyways, I now have the new update installed. I've noticed two weird things:
1. When I go to about phone in settings and go into software update, it shows a screen "checking for software updates..." and doesn't go away unless I press back or home button. Why can't I search for new updates????
2. My google now voice isn't working. It recognizes what I say to it but when it gives the flashcard response, it doesn't talk back like it normally does. I have it set to English US, and yes my media volume is up at full volume.
Anyways I'm a little frustrated at this point. I can't figure out how to fix these problems so any help would be greatly appreciated. Thanks
So I had my phone rooted sometime around the point when the 4.1.2 OTA came out. I went back to stock recovery and a nandroid backup that I made before rooting. Now, about once a week, I get the notification that the update is available but it doesn't work. My phone reboots like its going to update, I get the android guy with the spinning graphic thing, then it reboots the same as it was before.
I tried searching but couldn't find a solution...if my searching skills suck just let me know
THANKS!
I have been having issues with my Note3 ever since the kit kat update back in April. It worked flawlessly on Jelly Bean and I had no issues for over 3 months. I updated to kit kat via Kies with everything completely stock. Since then I get completely random reboots, it could happen when launching an app or even unlocking the screen, and it happens 2 or 3 times a day. So far I have tried 2 factory resets, clearing dalvik cache, and replacing the battery with an Anker replacement. I have tried turning off auto-updating of apps, and turning off wifi scanning. I have also tried running the phone with no apps installed. So far nothing has worked.
I have read several posts with people blaming the stock kernal for these reboots, but there is no definitive solution to this problem. I am looking for any and all help the community has to offer.
Some additional info:
Running latest stock rom- rooted via effortless method
Stock Recovery
Knox is still 0x0
No sd card in phone
Since you have no issues doing a factory reset, I recommend the following:
1.). Backup all the data you need
2.) Download the newest carrier available firmware for you from sammobile.com
3.) Flash via Odin
4.) Once finished and phone has rebooted, return to stock recovery and perform another data wipe
That will 100% fix your issues, sounds like maybe a corrupt system partition or libs
icenight89 said:
Since you have no issues doing a factory reset, I recommend the following:
1.). Backup all the data you need
2.) Download the newest carrier available firmware for you from sammobile.com
3.) Flash via Odin
4.) Once finished and phone has rebooted, return to stock recovery and perform another data wipe
That will 100% fix your issues, sounds like maybe a corrupt system partition or libs
Click to expand...
Click to collapse
Thanks, I'll give this a try. Last night I uninstalled a bunch of bloat ware with titanium backup to make sure it's still not an app issue. If it reboots again I'll reflash the firmware. Since I'll. Be flashing stock it shouldn't trip knox right?
No, latest firmware complete stock will not trip Knox, as long as you're either doing a parallel upgrade NF9 > NF9 or NB4 > NF9. A downgrade will either fail or trip.
For anyone reading this, i tried to reflash the stock nf9 kernal to see if that was the issue, but i got a restart about 4 hours later. I am going to reflash the firmware via odin and report back.
I am having this issue for a long time. i have done everything, and finally i gave up, as i think it is a hardware issue. what make me confuse is the problem start since the day i upgrade to kit-kat. with every firmware come out i have a new problem. the latest "NF9" my phone just hang and black screen untill i press the power button for 30 second, then will restart. what make crazy is that it shuts off at night, and when i woke up i miss the alarm.
I'm sad to report that the reflash didn't work. I reflashed the NF9 firmware using odin about 4 days ago and it was fine for awhile, but I got 2 reboots today. I'm not sure what is causing this, but I am still open to suggestions. I don't think its hardware related since it didn't do this before kitkat. I still have my samsung warranty until february I believe, so if worst comes to worst then ill have to send it in, but i'm not sure what they will do about it.
The only thing I havent tried is replacing the sim card. Could a sim card cause a reboot issue like this?
i have already done it, even the SD card, still same problem.
Is there some kind of log feature in android that logs crash events or errors somewhere so i can maybe figure out what the problem is?
by the way i think i have solve my problem by updating busybox and supersu. i had to install busybox to system/xbin. and since that day i haven't encounter any restart or freez. almost 2 week. i hope that fix your problem as well.
makki666 said:
by the way i think i have solve my problem by updating busybox and supersu. i had to install busybox to system/xbin. and since that day i haven't encounter any restart or freez. almost 2 week. i hope that fix your problem as well.
Click to expand...
Click to collapse
I do not have busybox installed, and SuperSU is up to date. Also, the restarts happen with or without root ie without SuperSU. I still dont think its an app problem.
Just an update for anyone reading this. I have installed SetCPU to manage cpu clock speeds. I have had it installed for about a week and have not had an update with my custom profiles. It seems the restarts occur when cpu speed is at about ~675MHz. Not sure if its hardware or software yet. Any help is appreciated!
Update. I sent my phone in to samsung for repair. It looks like they just reflashed the firmware. After having it up and running again for 15 minutes the phone rebooted again. I contacted samsung and they recommended sending it in again. I'm not sure if it's worth it to send in again or if i should break my warranty and flash a custom rom. Any suggestions are welcome!
I get restarts because the modem crashes... its a known issue apparently
gtharea said:
I get restarts because the modem crashes... its a known issue apparently
Click to expand...
Click to collapse
I cant believe its taken over a year for this issue to get fixed. Im almost positive its a software issue since it never happened on jelly bean. It's strange that not a lot of people have this problem though. A lot of people must have already flashed custom roms I may send it in again since I still have knox 0x0 and see if they do anything else besides reflash the firmware this time. If they only do a reflash again i will just flash a new rom and hopefully everything will be fixed
Final Update:
I sent my phone back to Samsung, apparently my issues were a hardware problem. This time they replaced the "PBA assembly" aka the mainboard. I have had the phone back for almost two weeks without a single restart. I believe my restart problems are over. I hope this information helps anyone with similar issues. I would recommend sending it to Samsung for warranty repair if you are still under warranty. :good:
_bhaves_ said:
Final Update:
I sent my phone back to Samsung, apparently my issues were a hardware problem. This time they replaced the "PBA assembly" aka the mainboard. I have had the phone back for almost two weeks without a single restart. I believe my restart problems are over. I hope this information helps anyone with similar issues. I would recommend sending it to Samsung for warranty repair if you are still under warranty. :good:
Click to expand...
Click to collapse
I had the same problem but already tripped knox so iffy on sending it in. Funny thing is I did the external sd write fix and the phone has not rebooted since, going on 3 days.
meoshe said:
I had the same problem but already tripped knox so iffy on sending it in. Funny thing is I did the external sd write fix and the phone has not rebooted since, going on 3 days.
Click to expand...
Click to collapse
I would get reboots even without an SD card put in the phone, so I don't think that would have helped me. I havent had a reboot since I've had the device back
tonight i decided to update my rom from Danvdh's 4.3 GPE to his 5.0 version. the update went flawlessly but i felt like wifi was very slow. i decided to flash my baseband from mk2 to nh7(sammobile). now, rather than seeing the lovely 5.0 bootup animation, my phone endlessly plays the tmobile bootup animation. i can't boot into recovery but i am able to boot into download mode
what was the problem with what i did? and what can i do to fix it?
tonight i decided to update my rom from Danvdh's 4.3 GPE to his 5.0 version. the update .................................
what was the problem with what i did? and what can i do to fix it?
***** QUOTE ****
The main problem was probably that you didn't READ, there are several threads started as well as a QBot thread, that pertain to issues and problems (some major like phone replacement) concerning GPE 5.0. If you read these postings you would or wouldn't have an answer to your boot loops, or you would had figured out that this 5.0 update is trashing a bunch of phones and maybe I shouldn't flash it.
Only thing I can suggest is reflash again, it may fix it. ???
Pp.
i know this problem came from my lack of understanding. but it had nothing to do with 5.0 GPE...
anyways some point after rebooting/reflashing/flashing a root tar, i was able to get passed the tmobile animation and into the stock s4 setup. it was then that i realized that what i did was flash the stock rom, not just the baseband. i was finally able to get into recovery and wipe everything. flashed the 5.0 rom. everything works and now i actually have the nh7 baseband
Glad it worked out for you. Good recovery. Profit.
Pp.