Related
I have created this thread for all you SG-SIII Noobs & Senior Members!
The purpose of this thread is to limit the number of (sometimes useless) threads, that are created over a simple problem that can easily be solved by READING OR SEARCHING.
This is the Emergency thread!
*Did you run into a problem and need quick assistance?
*Do you have a question or concern about your SG-SIII device?
Don't panic just ask here and I or WE THE SG-SIII COMMUNITY will gladly help!
In case of emergency!
Okay I guess I'll be the first to post.
About an hour ago my phone shut off at 26% battery (16gb galaxy S3 running CM10.1 nightly 01/16). As I went to turn it back on it will boot into the CM splash screen spin a few times and just shut off. I attempted to charge it, and turn it back on but same thing. After that an attempt to get into CWM, which I was able to get in and it shut off while I was in it. I also tried putting the phone in download mode and about the same time frame it took for the other attempts resulted in a shut down.
Any advice? Or am I stuck doing a warranty exchange?
Rayman0625 said:
Okay I guess I'll be the first to post.
About an hour ago my phone shut off at 26% battery (16gb galaxy S3 running CM10.1 nightly 01/16). As I went to turn it back on it will boot into the CM splash screen spin a few times and just shut off. I attempted to charge it, and turn it back on but same thing. After that an attempt to get into CWM, which I was able to get in and it shut off while I was in it. I also tried putting the phone in download mode and about the same time frame it took for the other attempts resulted in a shut down.
Any advice? Or am I stuck doing a warranty exchange?
Click to expand...
Click to collapse
Sounds like its your battery not a hardware problem. Leave it overnight or a couple hours charging and if it indeed boots up its your battery.
If it doesn't then flash stock and test it if the same result then call up that Warranty. I've seen this same issue with other devices where the battery dies at 50%+ and usually replacing the battery fixes the problem. Test your battery for overheating or swollen.
Sent from my HTC One S using Tapatalk 2
...Awesome... said:
Sounds like its your battery not a hardware problem. Leave it overnight or a couple hours charging and if it indeed boots up its your battery.
If it doesn't then flash stock and test it if the same result then call up that Warranty. I've seen this same issue with other devices where the battery dies at 50%+ and usually replacing the battery fixes the problem. Test your battery for overheating or swollen.
Sent from my HTC One S using Tapatalk 2
Click to expand...
Click to collapse
The battery isnt swollen, thats one of the things I checked also. I thought it might be that, the only other option I have is to try a different battery. The good thing is I work in a tmobile store so im gonna give that a shot tomorrow.
Sv: ***Emergency Thread*** Here To Help!
Can you start it without battery connected to the wall charger? If so try wipe cache. Or after reflash ROM.
Sent from my LG-P990 using xda app-developers app
lintz said:
Can you start it without battery connected to the wall charger? If so try wipe cache. Or after reflash ROM.
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
Phone wont boot without the battery in, and with it in I cant stay in recovery without with rebooting.
Rayman0625 said:
The battery isnt swollen, thats one of the things I checked also. I thought it might be that, the only other option I have is to try a different battery. The good thing is I work in a tmobile store so im gonna give that a shot tomorrow.
Click to expand...
Click to collapse
Even better then lol just test it out at work. I'm about 80% its your battery specially if you OV/UC.
I have the t-mobile US t999.
Last night I was having an odd issue with the networking dropping. I've had the phone for about a month, modded since day 1 with a CM10 variation of a rom (sorry, I forget the exact rom). I had no issues whatsoever up until this point. After a few restarts thinking maybe it was a fluke issue with the network, or network signal in my room, the phone forced itself into emergency call mode only. I couldn't get it to come out.
So I decided I was going to odin on a stock rom as I could get it into download mode, that went through successfully. When the phone boots, I get the android taking off (Tmobile 4g) logo. Then the white samsung logo, and it doesn't go beyond this. I know this can take long so I left it there for about an hour, nothing. The phone also displays a blue led the entire time it's hanging as well.
Also worth noting, when I attempt to boot into recovery it just vibrates over and over.
Not sure what my next steps should be. Any help would be greatly appreciated.
heartspains88 said:
I have the t-mobile US t999.
Last night I was having an odd issue with the networking dropping. I've had the phone for about a month, modded since day 1 with a CM10 variation of a rom (sorry, I forget the exact rom). I had no issues whatsoever up until this point. After a few restarts thinking maybe it was a fluke issue with the network, or network signal in my room, the phone forced itself into emergency call mode only. I couldn't get it to come out.
So I decided I was going to odin on a stock rom as I could get it into download mode, that went through successfully. When the phone boots, I get the android taking off (Tmobile 4g) logo. Then the white samsung logo, and it doesn't go beyond this. I know this can take long so I left it there for about an hour, nothing. The phone also displays a blue led the entire time it's hanging as well.
Also worth noting, when I attempt to boot into recovery it just vibrates over and over.
Not sure what my next steps should be. Any help would be greatly appreciated.
Click to expand...
Click to collapse
after you odin, you need to wipe data/ factory reset to boot. If you can't get into recovery ( Power, Home Button, and Volume Up), then try reflashing your stock image in Odin and check your MD5 sum, so you can rule out a bad download
Thanks for the reply, I'm re-downloading the stock rom now to verify it's integrity and do a new flash. I cannot get into recovery, so we will see after the new flash. Pleading ignorance on one subject, how would I go about checking the MD5 sum to verify the file has no issues?
Additionally I did try to Odin recovery and still could not boot into it, this was however before attempting to re-download and flash a stock rom again.
**Edit//Update** Re-downloaded and flashed stock rom, was able to get into recovery and wipe, booted up fine.
Wow.. great idea for a thread and THANK YOU!!
Perfect timing too cause i need a little help please.
I am not new to android but new to samsung (WOW, didnt realize it would be so different from HTC ont he rooting and flashing side of things).
Long story short. I have a tmo s3. Bought it today and wanted to root. phone was working perfectly as it shoudl on stock rom unrooted. I downloaded the tool kit v7, used that to root adn install TWRP and rebooted into the stock rom that is now rooted. Still everything working perfect.
Here is what i did next and where the issues start.
Downloaded Synergy r290, went to recovery.
Wiped Cache, Dalvik, Data, and System (made a backup first)
flashed the rom and rebooted to system
However, nothing ever happened. I see the samsung logo, then all goes black and nothing happens (left it there for 10min)
I cant seem to get back into recovery holding vol up, home and power either and have no adb access to use that. I AM able to get into download mode which i know i can fix my problem here with odin, but i am just not sure what to flash and where.
Is there an easier way??
Thanks in advance for any help!
frettfreak said:
Wow.. great idea for a thread and THANK YOU!!
Perfect timing too cause i need a little help please.
I am not new to android but new to samsung (WOW, didnt realize it would be so different from HTC ont he rooting and flashing side of things).
Long story short. I have a tmo s3. Bought it today and wanted to root. phone was working perfectly as it shoudl on stock rom unrooted. I downloaded the tool kit v7, used that to root adn install TWRP and rebooted into the stock rom that is now rooted. Still everything working perfect.
Here is what i did next and where the issues start.
Downloaded Synergy r290, went to recovery.
Wiped Cache, Dalvik, Data, and System (made a backup first)
flashed the rom and rebooted to system
However, nothing ever happened. I see the samsung logo, then all goes black and nothing happens (left it there for 10min)
I cant seem to get back into recovery holding vol up, home and power either and have no adb access to use that. I AM able to get into download mode which i know i can fix my problem here with odin, but i am just not sure what to flash and where.
Is there an easier way??
Thanks in advance for any help!
Click to expand...
Click to collapse
If you absolutely can't get into recovery to restore your backup..
Flash the UVDLJA root66 file in this thread http://forum.xda-developers.com/showthread.php?t=1949687 via odin. You will have the latest UVDLJA JB update, and will be rooted. From there, install goo manager from the play store to flash TWRP.
After that you're all set to flash whatever you want (just make sure it's for the Tmobile s3).
Sent from my SGH-T999 using Tapatalk 2
Towle said:
If you absolutely can't get into recovery to restore your backup..
Flash the UVDLJA root66 file in this thread http://forum.xda-developers.com/showthread.php?t=1949687 via odin. You will have the latest UVDLJA JB update, and will be rooted. From there, install goo manager from the play store to flash TWRP.
After that you're all set to flash whatever you want (just make sure it's for the Tmobile s3).
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Ok, easy enough, but do i put that in the PDA field in Odin or phone?
This sounds MUCh easier than what i thought i would have to do.. thanks a ton!
frettfreak said:
Ok, easy enough, but do i put that in the PDA field in Odin or phone?
This sounds MUCh easier than what i thought i would have to do.. thanks a ton!
Click to expand...
Click to collapse
Just upload the file to PDA and hit start. Make sure to let it finish completely, once the phone reboots, it's done.
Sent from my SGH-T999 using Tapatalk 2
Flashing stock with Odin can take up to ten minutes its normal like the man said above just let it do its thing
Towle said:
Just upload the file to PDA and hit start. Make sure to let it finish completely, once the phone reboots, it's done.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
Worked great! Thanks!!
http://forum.xda-developers.com/showthread.php?t=2113883
Let's see if you have any solution for me?
Weird problem. When I set kernel frequencies on my phone, they at some point get locked at the maximum frequency. This has happened every time I flash a new ROM or kernel, and I'm worried that it will soon start to affect the battery. I'm using the msmdvcs governor on both kernels that I've tried (stock and faux)
ohshootrawr said:
Weird problem. When I set kernel frequencies on my phone, they at some point get locked at the maximum frequency. This has happened every time I flash a new ROM or kernel, and I'm worried that it will soon start to affect the battery. I'm using the msmdvcs governor on both kernels that I've tried (stock and faux)
Click to expand...
Click to collapse
Do u happened to have apps that control frequency like setcpu etc? They might be conflicting each other
Sent from my HTC One S using Tapatalk 2
So, here's how it went. :crying:
I just bought my Note 8.0. Came with KitKat - don't remember which firmware. In Kies I tried to update it with latest firmware, when something happened and tablet rebooted with message:
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
At first, it sounded simple to me. I tried connecting tablet in Kies, but it was looping in "Connecting", and it never did connect. At all.
I thought, fine, I can try Odin. Once I started flashing KitKat based stock firmware, it fails all the time and it goes like:
...
sboot.img
NAND Write start!
FAIL!
...
"NOT COOL"
Tried out flashing .pit file too but it gets stuck at "Get .PIT for mapping"
And I cannot do anything with my new tablet anymore and I'm stuck. I have tried re-installing drivers, trying out differen USB cables/ports, yet nothing has worked...
And yeah, it shows KNOX Warranty Void : 1, after trying out Odin, so I am screwed too.
And now after battery has depleted, the screen is flickering all the time, and when I try to charge it the charger and the tablet gets hot extremely fast. Does this mean I wasted my money? LOL.
Hi,
I have the exact same problem with my wifey's tablet.
I am working on it at the moment. (which model is yours? hers is SGH-I467)
I believe we should be able to bypass this error by manually flashing certain partitions (leaving out the sboot, which cannot be downgraded, thus causing the error)
I'll be putting together a package for this shortly. (or else my wifey is gonna hulk smash me)
re: battery being dead/screen flicker:
Use a higher wattage charger if you have one. The charger that comes with the gnote8 pulls 8 to 10 watts, random OEM chargers tend to put out less. I was getting the flickering while plugged into usb, but plugged into the charger i'm not.
Da_G said:
Hi,
I have the exact same problem with my wifey's tablet.
I am working on it at the moment. (which model is yours? hers is SGH-I467)
I believe we should be able to bypass this error by manually flashing certain partitions (leaving out the sboot, which cannot be downgraded, thus causing the error)
I'll be putting together a package for this shortly. (or else my wifey is gonna hulk smash me)
Click to expand...
Click to collapse
Mine's GT-N5110. 16GB Wi-Fi model.
Pretty lame that tablet got bricked under 24hrs. *achievement unlocked* :crying:
I have never had such terrible problems with any other Samsung device...
Actually, I tried the Kies again, with Firmware Upgrade and Initialization Tool, looked like it would install just fine, BUT it got a write fail....ffs... Gonna try it again soon. I am trying to charge it up for now.
Da_G said:
re: battery being dead/screen flicker:
Use a higher wattage charger if you have one. The charger that comes with the gnote8 pulls 8 to 10 watts, random OEM chargers tend to put out less. I was getting the flickering while plugged into usb, but plugged into the charger i'm not.
Click to expand...
Click to collapse
The flickering goes away if I leave it to charge it a bit. Just found that out. I just can't charge it for a long time, not going to talk about overnight, because it overheats too much.
I guess it only flickers when battery is going low, and connecting it with USB doesn't help it either.
Kies attempts to flash a full image, which contains an older sboot.img. Once the sboot has been upgraded, it can't be downgraded. This is why you are getting a failure each time.
Unless Kies updates to a newer version of the sboot.img, it won't work to fix this issue. The key should be using odin to flash everything but the sboot.img. I'm working on it now. I don't have the same model as you however, but the method to create an image should be exactly the same for that model, just have to start with a different set of files.
Da_G said:
Kies attempts to flash a full image, which contains an older sboot.img. Once the sboot has been upgraded, it can't be downgraded. This is why you are getting a failure each time.
Unless Kies updates to a newer version of the sboot.img, it won't work to fix this issue. The key should be using odin to flash everything but the sboot.img. I'm working on it now. I don't have the same model as you however, but the method to create an image should be exactly the same for that model, just have to start with a different set of files.
Click to expand...
Click to collapse
OK, so I tried to do this again. This time I let tablet charge so while firmware gets recovered, screen doesn't flicker and do weird stuff, aaand....
Recovered the firmware succesfully, BUT it got bricked and has a boot loop. That's just naaaasty.
Katflakes said:
OK, so I tried to do this again. This time I let tablet charge so while firmware gets recovered, screen doesn't flicker and do weird stuff, aaand....
Recovered the firmware succesfully, BUT it got bricked and has a boot loop. That's just naaaasty.
Click to expand...
Click to collapse
Done, I have found out that I repedeately tried to install the wrong firmware. Ex., I have tablet with stock XEO firmware, and I tried to install SEB firmware. Thats why it didnt let me install the firmware I wanted to, because I was stupid. well best 10gb ever spent!
Help Please!
Need help !!
my note 8.0 gt-n5110 get the same error when flashing the stock 4.4.2 kitkat
sboot.img
NAND Write start!
FAIL!
i can enter the recovery and download mode but when flashing i get the error
Pleeease HELP!!!!
Lemme see here... You stated it was already 4.4.2 and broke when upgrading f/w. I assume you are using keis for 4.2.2... You will need to uninstall it, and install the latest kies for 4.4.2. Then see if you can fix your broken flash.
Hey y'all... looks like I'm in the same miserable boat. I'm trying to sell my Sammy Note 8 to Amazon but had to remove the root and Cyanogen 4.4.4 ROM before sending it in. After reading a bunch of articles, I came to this page: http://forum.xda-developers.com/showthread.php?t=2773712 After waiting about 20 minutes and not seeing any progress, I thought it was stuck. So, I rebooted into recovery and tried again. Like the OP, Odin peters out at the recovery.img stage and Fails. Now, I'm getting the super fast screen flashing which I've learned is a low battery issue. It's on charge now and hope in an hour or two can try again. My question to you guys, am I using the right img for a US N5110? Or do you guys know a better way to flash this baby back to original the original unrooted, 4.2.2 state?
Any help is VERY MUCH appreciated!
Da_G said:
Kies attempts to flash a full image, which contains an older sboot.img. Once the sboot has been upgraded, it can't be downgraded. This is why you are getting a failure each time.
Unless Kies updates to a newer version of the sboot.img, it won't work to fix this issue. The key should be using odin to flash everything but the sboot.img. I'm working on it now. I don't have the same model as you however, but the method to create an image should be exactly the same for that model, just have to start with a different set of files.
Click to expand...
Click to collapse
HI! I have the same model as your wife and same problem! Can you please teach me how to do it!
You can't go from kk (4.4) to jb(4.2). Kitkat has a locked bootloader.
You might try stock kk flash.
Sent from my GT-N5100 using XDA Free mobile app
If you have the ATT SGH i467 the Kit Kat ROM is not available to the public.
I sat with mine in the exact same state as yours & the OP until I found out you can take your Note 8 to a Samsung Experience center (they are in a LOT of Best Buy stores!! 4 in Columbus Ohio) and they will flash Kit Kat on it for you for free!! I was stoked to get my tablet back to working order. The original issue that got me into this problem (my IMEI disappeared and no I have NEVER rooted this tab) is what I am currently trying to have them fix without as much luck as they had fixing the stuck in downloading mode. The quality of the employees varies GREATLY from store to store. The 1st tech fixed me up great and hung in there even though the low charge battery issue was looking like it would make the reflash fail but the next tech at a different store literally just sat and looked down not saying a word waiting for me to give up and leave because "their laptop didn't have enough free disk space to download the ROM". If ANYONE from Samsung would have watched the situation and his actions he would have been fired on the spot. So be patient if the 1st tech you talk to is clueless because they CAN fix your issue.
I have a very strange problem with this device (g920p), Backstory: i got it with the screen broked so i replaced it. There was no problem until the sound stopped working. I pressed vol - and power button but it never came to life.
What i did / Result:
Hard Reset (wipe cache and data, cache partition). / Same status Softbricked
Installed custom recovery and wiped out caches dalvik. / Still Bricked
Download and installed stock ROMS: CPD2, CPB6 (6.0.1) / After the odin procedure, it reboots and then it updates system, later says "optimizing apps" and when finish the phone stucks at "Starting Apps" (for hours) and it never starts. If i reboot it, after the samsung logo it just shows blue light blinking but the screen stays black.
I have downgraded to almost all 5.1.1 ROMS / Same result as above.
I have installed almost all ROMS after wipes (with stock recovery and custom) / no sucess.
I have tried to recover it with Smart Swich but i cant get the s/n, barcodes only shows MEID but no serial.
I have left the battery die then i do all the previuos trys with no sucess, i can just get to "Android is Upgrading - starting apps" screen.
I have tried installing custom kernels after rom installs / NO luck.
Safemode does nothing.
Any clues to get my s6 back to life?
If it's the 32gb version, I recommend flashing the pit file found in the general section.
Sent from my SM-G920P using Tapatalk
elesbb said:
If it's the 32gb version, I recommend flashing the pit file found in the general section.
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
Yep its the 32gb varient, i cant locate the pit file.
elesbb said:
If it's the 32gb version, I recommend flashing the pit file found in the general section.
Sent from my SM-G920P using Tapatalk
Click to expand...
Click to collapse
i found "ZEROFLTE_USA_SPR.pit" and i got the same result, shows the samsung logo then the screen goes black, it stucks at Starting apps screen.
pablitokio said:
i found "ZEROFLTE_USA_SPR.pit" and i got the same result, shows the samsung logo then the screen goes black, it stucks at Starting apps screen.
Click to expand...
Click to collapse
You need to make sure you are flashing the proper stuff. You can't just go throwing random sh*t at it.
This is the proper PIT for your device: https://www.androidfilehost.com/?fid=24499762636008230
If you were to look through the thread, specifically the general section, as I mentioned, you would have found it
Flash the PIT file by selecting "PIT" inside odin and NOTHING else. Then reboot and flash the stock tar.
elesbb said:
You need to make sure you are flashing the proper stuff. You can't just go throwing random sh*t at it.
This is the proper PIT for your device: https://www.androidfilehost.com/?fid=24499762636008230
If you were to look through the thread, specifically the general section, as I mentioned, you would have found it
Flash the PIT file by selecting "PIT" inside odin and NOTHING else. Then reboot and flash the stock tar.
Click to expand...
Click to collapse
Thanks a lot, i did look for it and found the other one. After flashing the PIT i flashed the .tar (CPB6) and the result was the same, blackscreen with blue light dimming intermitent. This time the "optimizing apps screen" didnt show up. i havent touched the device yet, im waiting for the optimization screen to show up. Im waiting 30min if it doesnt works im gonna reboot the device and do the wipes and reboot.
elesbb said:
You need to make sure you are flashing the proper stuff. You can't just go throwing random sh*t at it.
This is the proper PIT for your device: https://www.androidfilehost.com/?fid=24499762636008230
If you were to look through the thread, specifically the general section, as I mentioned, you would have found it
Flash the PIT file by selecting "PIT" inside odin and NOTHING else. Then reboot and flash the stock tar.
Click to expand...
Click to collapse
Didnt work but i realized now it has no IMEI or MEID.
pablitokio said:
Didnt work but i realized now it has no IMEI or MEID.
Click to expand...
Click to collapse
Let it die completely. Once it dies attempt to boot into download mode until it wont anymore (completely dead), charge to about 15%, reboot. Should be fixed. If not retry. What happened I think is the minute reboot with no signal/baseband/imei etc., except you flashed a rom or something to try to fix it so now it appears to bootloop but really is doing the same minute automatic reboot no signal issue. I had same happen to me when i flashed a rom trying to fix it, it "bootlooped", but being the first boot taking the standard additional time it never made it to the full boot up, until letting it die, then all was good. Nothing else is needed except complete drain of battery
droseofc said:
Let it die completely. Once it dies attempt to boot into download mode until it wont anymore (completely dead), charge to about 15%, reboot. Should be fixed. If not retry. What happened I think is the minute reboot with no signal/baseband/imei etc., except you flashed a rom or something to try to fix it so now it appears to bootloop but really is doing the same minute automatic reboot no signal issue. I had same happen to me when i flashed a rom trying to fix it, it "bootlooped", but being the first boot taking the standard additional time it never made it to the full boot up, until letting it die, then all was good. Nothing else is needed except complete drain of battery
Click to expand...
Click to collapse
Thank you im gonna try this for sure. I have worked all day long with this device. and i am not giving up until it totally die or work.
UPDATE (Battery not drained yet):
I realized about some things when i flash the stock rom, after odin finish the phone shows a screen that says "updating system" a progress bar loads but only reaches to 32% then says Erasing and reboots, then just hangs at "starting apps" screen.
Same result as previous ones. Stucked at "Starting Apps". After the flash .pit file, i flash the .tar, then when finish the devices reboots and the screen shows a progress bar that reads "Installing system update" but it only reaches to 32%.
That is odd. Did the sound ever come back? Maybe it has something to do with the hardware fix. Wherever you got the replacement from were there any reviews that may indicate others having similar issues or contacting whoever u got it from? If the sound stopped working and then you reset it and etc and now its not booting fully up maybe it does some type of hardware check and reboots if and when it fails.. idk truthfully, if it were me Id go back to looking at the screen replacement
i'll try doing all the previous steps but with the original screen. i'll update the post ASAP
My g920p got exactly the same problem. It die for 2 weeks. I try every thing i can but it can't get out of "starting apps". So i place it in my desk until today i boot it up and actually, it start. Still have no sound, but when it check for update and i press update now, the "starting apps" loop show up. Have you fixed your phone yet?
Sorry for my bad English.
It looks like you really did a number on it!
Good Luck!
Help
Does anyone have the same problem???
Samsung S6- G920P impossible to Fix
Had same problems with my G920P and nobody even replied to my cry for help....thanks guys! No really,without help i had to learn the hard way. Anyways, I flashed the Pit file then flashed a boot file, then a modem file, then last but not least the complete Home tar. Let me know if this works for you. According to my G920P it took me 48 days, and very long nights to get it back up and running. Hard bricked a Galaxy S7 in the process........next project i guess!
Samsung S6- G920P impossible to Fix
Had same problems with my G920P and nobody even replied to my cry for help....thanks guys! No really,without help i had to learn the hard way. Anyways, I flashed the Pit file then flashed a boot file, then a modem file, then last but not least the complete Home tar. Let me know if this works for you. According to my G920P it took me 48 days, and very long nights to get it back up and running. Hard bricked a Galaxy S7 in the process........next project i guess! Having trouble uploading those files to you but i will get them out tonight. By the way, theyre PI3 files. i was on PB6 but the only thing that worked was to bump up a couple versions.
Mrm35150 said:
Had same problems with my G920P and nobody even replied to my cry for help....thanks guys! No really,without help i had to learn the hard way. Anyways, I flashed the Pit file then flashed a boot file, then a modem file, then last but not least the complete Home tar. Let me know if this works for you. According to my G920P it took me 48 days, and very long nights to get it back up and running. Hard bricked a Galaxy S7 in the process........next project i guess! Having trouble uploading those files to you but i will get them out tonight. By the way, theyre PI3 files. i was on PB6 but the only thing that worked was to bump up a couple versions.
Click to expand...
Click to collapse
bro, im having the same problem, can u elaborate step by step how you did it?
RadarZgin said:
bro, im having the same problem, can u elaborate step by step how you did it?
Click to expand...
Click to collapse
I will get the files together and get them to you
Mrm35150 said:
I will get the files together and get them to you
Click to expand...
Click to collapse
thanks bro
Have had this problem for about two weeks now. Every time I get the phone able to boot (either by reflashing a rom or odin) it will work for a few hours then it'll freeze in the middle of use or idle and restart. After restarting a few times the phone will no longer boot and I have to reflash it with odin or TWRP. It's happened so much though that as of today even if I get it to start it'll end up freezing up shortly after booting, get stuck on the black start screen and hang there until I pull the battery. At that point the phone will only boot into download or recovery. I'm at the end of what I can do and out of ideas.
So far I have tried
Odin to:
N910PVPS4COK1_N910PSPT4COK1_N910PVPS4COK1_HOME.tar.md5
N910PVPU4DPH4_N910PSPT4DPH4_N910PVPU4DPH4_HOME.tar.md5
and flashing multiple different roms to try to fix it.
Sometimes it won't even mount data, cache, system, etc within twrp.
I've also tried to format each individual partition when it wouldn't start no matter what and that did make it so it was able to start but the same problems were there after it did start.
I've searched and I cannot find a solution to anything similar to the problem I'm having. If anyone has any ideas they'd be greatly appreciated.
justintworley said:
Have had this problem for about two weeks now. Every time I get the phone able to boot (either by reflashing a rom or odin) it will work for a few hours then it'll freeze in the middle of use or idle and restart. After restarting a few times the phone will no longer boot and I have to reflash it with odin or TWRP. It's happened so much though that as of today even if I get it to start it'll end up freezing up shortly after booting, get stuck on the black start screen and hang there until I pull the battery. At that point the phone will only boot into download or recovery. I'm at the end of what I can do and out of ideas.
So far I have tried
Odin to:
N910PVPS4COK1_N910PSPT4COK1_N910PVPS4COK1_HOME.tar.md5
N910PVPU4DPH4_N910PSPT4DPH4_N910PVPU4DPH4_HOME.tar.md5
and flashing multiple different roms to try to fix it.
Sometimes it won't even mount data, cache, system, etc within twrp.
I've also tried to format each individual partition when it wouldn't start no matter what and that did make it so it was able to start but the same problems were there after it did start.
I've searched and I cannot find a solution to anything similar to the problem I'm having. If anyone has any ideas they'd be greatly appreciated.
Click to expand...
Click to collapse
Try falsh repair firmware with pit file in odin.
Do factory reset immediately from recovery after flash firmware to get clean OS.
You can download repair firmware from here
https://www.androidfilehost.com/?fid=24591020540821805
Extract firmware you will get pit file inside of it.
Trex888 said:
Try falsh repair firmware with pit file in odin.
Do factory reset immediately from recovery after flash firmware to get clean OS.
You can download repair firmware from here
https://www.androidfilehost.com/?fid=24591020540821805
Extract firmware you will get pit file inside of it.
Click to expand...
Click to collapse
I used both of them for a restore and did a factory reset and things looked good for about 30 minutes and now its back to the random freezes that turn into a restart
justintworley said:
I used both of them for a restore and did a factory reset and things looked good for about 30 minutes and now its back to the random freezes that turn into a restart
Click to expand...
Click to collapse
I suppose this is a long shot, but are you running on the original or an old battery? It's possible that a bad battery is causing the reboots. I was back and forth to the Sprint store about 4 times in one week. They first tried flashing the firmware. (Yeah, I could have done it, but I have insurance.) They sent me home and on the way my phone rebooted itself. I got a replacement Note 4, but it started getting hot, then also rebooting. They "let" me upgrade to a Note7, which I loved. I had to give it back even though it was from the new, supposedly safe batch. At this point, I couldn't even get the Note 4 to boot at all. Boot loops, or would boot into download mode. Couldn't do anything with it, except pull the battery. Got a third Note 4, but also ordered a new battery pack from Sprint. They were and still are, only $24.95, with free shipping! You get a new battery, an external charging unit and a carrying case for the battery. (You have to use your own charger.) This finally fixed the problem. I had two batteries when I ordered the new one. I'm pretty sure one of the older batteries was defective, even though it wasn't bulging. I'm still using the other one that's also older, even though it is bulging a bit. It charges and runs fine. No over-heating. So, my problem was a combination of a defective battery and a couple of bad phones. The other thing was some of the previous firmware seemed to make some Note 4s run hot or get hot while charging. Things are much better since PG1. YMMV.
I had this issue and sent my phone back to Samsung THREE TIMES, I thought I bricked my phone from custom rom.
Turns out it was my battery. Sounds dumb, but true. Strangely even with battery out, I was having issue. Once I put in new good battery issue resolved.
I had that issue on my pc and my note. I had a creepy stalker in full control of my device (which basically was a virtual machine). I could tell when I was on the right track to get rid of him because it shut me down. I can't say that's what's going on with you but it is a thing.
Sent from my SM-N910P using Tapatalk
Note 4 batteries are dying for lots of people anywhere from 18 months to just over 2 years, and the symptom is often fail to boot, boot loops, etc. As piggynuts said, it's not logical, but it's true. It happened to me, and when I replaced the battery, everything was fine.
Hello!
I purchased a Galaxy S6 two days ago and have yet to really use it...
I wanted to have a fully fresh phone so i flashed the latest firmware available to me (USA, Sprint, sm-g920p, zerofltespr, QB1)
Everything flashed as normal (not my first S6, I'm familiar with ODIN) but upon booting up the first time it goes to a blue screen that says initializing update.. then the progress bar goes to 32% and then says erasing.. then it reboots and i get to optimizing apps (starts at some random number 8 of 33, 13of 33, 12 of 33, etc.) and then reboots and goes back to optimizing apps again... it's maddening!!!
I've tried at least 5 different firmwares, all with the same result. Always to 32% then bootloop on optimizing apps
I've tried using the PIT file for my phone along with flashing the firmwares, same result
When i try to enter recovery to wipe cache or factory reset, i get the blue screen that says initializing update then i get some yellow exclamtion warning for a second and i get to recovery... i wipe cache, reboot... same boot loop result
Back to recovery, factory reset, reboot... same boot loop result trying to optimize apps.
I've tried adb sideloading a couple different ROMS but those just bootloop at the Galaxy S6 logo splash screen.
I've run out of ideas for what to do to fix this.. every great once in awhile ill get to the welcome screen and itll get to Setting up your device for first time use... then itll just reboot and go right back to that screen... i havent been passed that once...
Please any ideas would really be great. Thanks
Saafir said:
Let the phone battery run dead. Then charge 15% and boot it. Problem will likely have fixed itself. [Not joking]
Click to expand...
Click to collapse
Do what @Saafir says, it usually works.
Saafir said:
Let the phone battery run dead. Then charge 15% and boot it. Problem will likely have fixed itself. [Not joking]
Click to expand...
Click to collapse
thanks so much for your response... Just got to work for my 12 hour shift... ill let it boot loop til it dies... im so curious to see if thats what will work..
thanks again!
Edit: just noticed your profile.... GO BLUE!!!!!!!!! (huge Michigan fan here) Aint that right, Koop?
blacksantron said:
thanks so much for your response... Just got to work for my 12 hour shift... ill let it boot loop til it dies... im so curious to see if thats what will work..
thanks again!
Edit: just noticed your profile.... GO BLUE!!!!!!!!! (huge Michigan fan here) Aint that right, Koop?
Click to expand...
Click to collapse
If you get this going, please send me (or post here via file attach) the file: /proc/last_kmsg -- you need to be rooted to get that so hopefully you are. To get this right, you need to copy that file to /sdcard (or somewhere there) and only on the first successful boot.
I want to see what is complaining so I can (hopefully) write a fix for future sufferers that won't require the reboot til dead game.
Sent from my iPad using Tapatalk
tdhite said:
If you get this going, please send me (or post here via file attach) the file: /proc/last_kmsg -- you need to be rooted to get that so hopefully you are. To get this right, you need to copy that file to /sdcard (or somewhere there) and only on the first successful boot.
I want to see what is complaining so I can (hopefully) write a fix for future sufferers that won't require the reboot til dead game.
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Right on, unfortunately i wont be rooted since Im bootlooping right after flashing stock firmware..
I cant believe that worked!!!!!!!!!!!!!!!!
If you were anywhere near me id buy ya a beer... i swear i tried everything for two days... so many firmwares i downloaded... oh my word...
thanks so much1
blacksantron said:
I cant believe that worked!!!!!!!!!!!!!!!!
If you were anywhere near me id buy ya a beer... i swear i tried everything for two days... so many firmwares i downloaded... oh my word...
thanks so much1
Click to expand...
Click to collapse
If you ever need, I try to keep the latest firmware posted here: https://forum.xda-developers.com/sp...uide-links-files-update-root-restore-t3366862
Hey guys I'm in need of some help, I've flashed my s6 sm-g920p phone about 7 times and it still won't boot up it gets to the lte screen just before startup and keeps rebooting what might be the problem ? Might it be the battery is not good ?