Related
I screwed and Updated the wrong NV items of the incredible and Now it just reboots. So far I can only get to the "HBOOT" bootloader screen. All other options causes the Dince to reboot and start the endless process again. also I cannot get to recovery mode because any option that requires me to I get out of bootloader starts the booting process and reboots. I have tried flashing stock rom "3.26.605.1" but after the update finished and rebooted it started the endless reboot again. is there a way I can reset the NV items back to the stock setting? Am I screwed?
Some other info that I hope will help.
I have two backups that I made using rom manager prior to the NV updates. I also have a full backup of the NV items using CDMAWorkshop before I did the update as well. Hopefully there's a way for me to write the NV items back
I'm assuming you can't restore your backups? Sounds like you might have to flash the stock recovery image. WWW.dougpiston.com should have a recovery image you can flash in hboot.
Sent from my ADR6300 using XDA App
Nope, that was the first thing I tried. it tells me everything is update and ask me if I want to reboot. once I reboot it keeps rebooting. The way I see it my issue is a little different than the usual end reboot problem. I think most people screwed up the PPC portion of the device so restoring or flashing a stock rom fixes it. I think I screwed up the phone portion of the device which usually don't get effected by a rom update. Is there anything that will clear everything up and force me to reprovision my phone service cause I think that's the only way i can fix this? or is there a way I can connect to diag mode of the phone without it fully booting?
Ok so I did a little more research and this thread here below seems be the solution I'm looking for but would the "HBOOT" image used for the EVO work on the incredible? I of course won't use the radio rom indicated but I was planning on using the other files. Anyone see anything that wouldn't work on my incredible?
http://forum.xda-developers.com/showthread.php?t=805612&page=3
Hm, I really don't know about NV items and messing with your phone on that level. I'm not that technically inclined, I'm sorry!
I've read through threads before where people get stuck in a bootloop and it seems that flashing the PB31IMG.zip in HBOOT usually fixes the problem and restores the phone to an out-of-the-box state. I don't know if that would work for you but that's about all I can think of. Sorry I can't help more.
SUCCESS!!
after much search I manage to find all the Dinc equivalent files in the EVO fix I posted previously and surprisingly enough it works!! Anyone else that has this problem can find the files and instruction in my post here.
http://forum.xda-developers.com/showthread.php?p=12828082#post12828082
Nice, glad you got it working!
I apologize in advance if any of this makes you roll your eyes at my stupidity.
Good Afternoon
I have an ATT samsung galaxy s3, Because of the glitches with 4.3 I was experiencing I decided to install custom software on my phone. So I looked up guides and got everything I needed. I did manage to get root access, and verified with super user. I also installed TWRP and CWM because each kept giving me errors when I tried to install CM 11 onto my phone. I tried CWM first, and when that didn't work I tried TWRP. It says there was no MD5 information found when I try to install any mod. how ever I have used the md5 file checker program and the MD5 matches up to what was listed in this one for example.
http://forum.xda-developers.com/show....php?t=2518998
Download:
CM 11.0 Unofficial Beta 7 for d2tmo and d2att
MD5: ef93957db1e6704f23f9015231a82826
So the MD5 matches, yet when I try to install it keeps giving me errors. I also tried other versions of CM that I found on here via links. Right now my phone has no OS as another guide I read some where also said to wipe system data (sorry if that was stupid, I was just following a guideline) And even more stupid, no I don't have a backup because in my naivety and stupidity I didn't think I'd need one as it seemed so simple from all the guides and videos I'd seen.
Yesterday a friend of mine knowledgeable with tech stuff took one of the original stock Image ROMs I'd downloaded and using linux and some program he managed to do some crazy stuff I can't even describe on here. All I saw was a lot of typing of command lines and it got my phone working again, how ever it wasn't exactly the stock image I guess because the phone would not make or receive calls/texts.
Since my phone was powering on again and the android OS was loading I figured I could connect it to my computer and use KIES to download the official latest update so my phone would be back on the legit software. But trying to do that...well broke my phone again. So I'm at a loss now of what to do. Right now I can still get to download mode on my phone, but when I try to get into recovery mode I get an error that "firmware upgrade encountered an issue. Please select recovery mode in KIES & try again." Which I've tried, and every time I try it gives me an error message.So I'm at a loss of what to do next.
So I'd like to get a working OS on my phone asap so I can get calls and texts.
Any help would be greatly appreciated. And being new I'm sorry if I broke any taboos or did not give some information that is typically given when describing a problem.
gvazquez82 said:
I apologize in advance if any of this makes you roll your eyes at my stupidity.
Good Afternoon
I have an ATT samsung galaxy s3, Because of the glitches with 4.3 I was experiencing I decided to install custom software on my phone. So I looked up guides and got everything I needed. I did manage to get root access, and verified with super user. I also installed TWRP and CWM because each kept giving me errors when I tried to install CM 11 onto my phone. I tried CWM first, and when that didn't work I tried TWRP. It says there was no MD5 information found when I try to install any mod. how ever I have used the md5 file checker program and the MD5 matches up to what was listed in this one for example.
http://forum.xda-developers.com/show....php?t=2518998
Download:
CM 11.0 Unofficial Beta 7 for d2tmo and d2att
MD5: ef93957db1e6704f23f9015231a82826
So the MD5 matches, yet when I try to install it keeps giving me errors. I also tried other versions of CM that I found on here via links. Right now my phone has no OS as another guide I read some where also said to wipe system data (sorry if that was stupid, I was just following a guideline) And even more stupid, no I don't have a backup because in my naivety and stupidity I didn't think I'd need one as it seemed so simple from all the guides and videos I'd seen.
Yesterday a friend of mine knowledgeable with tech stuff took one of the original stock Image ROMs I'd downloaded and using linux and some program he managed to do some crazy stuff I can't even describe on here. All I saw was a lot of typing of command lines and it got my phone working again, how ever it wasn't exactly the stock image I guess because the phone would not make or receive calls/texts.
Since my phone was powering on again and the android OS was loading I figured I could connect it to my computer and use KIES to download the official latest update so my phone would be back on the legit software. But trying to do that...well broke my phone again. So I'm at a loss now of what to do. Right now I can still get to download mode on my phone, but when I try to get into recovery mode I get an error that "firmware upgrade encountered an issue. Please select recovery mode in KIES & try again." Which I've tried, and every time I try it gives me an error message.So I'm at a loss of what to do next.
So I'd like to get a working OS on my phone asap so I can get calls and texts.
Any help would be greatly appreciated. And being new I'm sorry if I broke any taboos or did not give some information that is typically given when describing a problem.
Click to expand...
Click to collapse
same error happened to me yesterday and spent the whole day figuring it out. get into download mode. boot up ODIN and reflash your preferred custom recovery. after that, i couldn't find anything else to restore my phone with so i installed 4.3 leaked from here. doesn't matter which one you select. http://forum.xda-developers.com/showthread.php?t=2498233. place it on your sd card and head into recovery mode, wipe data/factory reset and cache. head to install zip from sd card and select the 4.3 zip you downloaded. reboot system and it should work. the at&t boot screen takes a while so be patient
MrHaPpY66 said:
same error happened to me yesterday and spent the whole day figuring it out. get into download mode. boot up ODIN and reflash your preferred custom recovery. after that, i couldn't find anything else to restore my phone with so i installed 4.3 leaked from here. doesn't matter which one you select. http://forum.xda-developers.com/showthread.php?t=2498233. place it on your sd card and head into recovery mode, wipe data/factory reset and cache. head to install zip from sd card and select the 4.3 zip you downloaded. reboot system and it should work. the at&t boot screen takes a while so be patient
Click to expand...
Click to collapse
First of all thank you for trying to help me, I hope you are having a good Thanks Giving.
I used the thread you linked to, and downloaded the version with out knox. I followed the instructions
transferred ROM and flashed kernel file to SD card
used odin to flash TWRP,
used twrp to flash rom and kernel file.
and it takes the file thankfully, there's only one issue. My phone can't make or receive calls/texts. Is yours able to?
I messed up and was playing with things That I had no business playing with and decided that I should do a restore of a backup (TWRP) I made as soon as I rooted the 4.3 OTA. well it has soft bricked my phone. it was a TWRP 4.3 Nandroid and has me messed up a little.
so far I tried My nandroid (no dice now a soft brick) cleared cache and dalvik, It was booting as far as the white at&t spinning thing,
Factory reset same on booting,
Tried a format of the internal sd this is where it gets sketchy it now goes as far as the second samsung screen(the one that says Samsung GALAXY S III)
4.3 OTA .zip (no dice TWRP wont flash it) same on the booting 2nd samsung boot screen
Tried the files in the link above and got a Hard brick
Used the debricking .IMG file and got TWRP and download mode back
Any suggestions?
Looks like I might need a JTAG/RIFF BOX for this one. If nothing else I spent many Hours of darkness discovering the darkness of android 4.3
If I get recovered from this and with a different rom like 4.1.2 I will be happy. the 4.3 OTA was very stable but I did miss wifi tether and the whole hardbrick thing was kind of a bummer. it would be real nice to have an ODIN file to fix this (AHEM samsung) or atleast perhaps stopped the progression of it to a hard brick.
New update
I got my phone booting up again however there is a catch. That unbrick.img file on my 16GB sd card is still required to boot the phone and I have no cell service what so ever. Tried to check apn settings because at home I sometimes get poor service and I run net10 so I was going to fix my apn and it says insert sim??? the sim is properly inserted???
Next Update
the bootloader I flashed apparently flashed to the external sd card? I flashed another one and it is booting from the internal sd. I had to flash a different modem the one in the bootloader/modem file I flashed from the link above didnt take? I got most everything sorted out, but im getting tired, it has been an all night adventure. its 08:23 est now
sorry for the delay in updating this I had to get some rest.
theramsey3 said:
I messed up and was playing with things That I had no business playing with and decided that I should do a restore of a backup (TWRP) I made as soon as I rooted the 4.3 OTA. well it has soft bricked my phone. it was a TWRP 4.3 Nandroid and has me messed up a little.
so far I tried My nandroid (no dice now a soft brick) cleared cache and dalvik, It was booting as far as the white at&t spinning thing,
Factory reset same on booting,
Tried a format of the internal sd this is where it gets sketchy it now goes as far as the second samsung screen(the one that says Samsung GALAXY S III)
4.3 OTA .zip (no dice TWRP wont flash it) same on the booting 2nd samsung boot screen
Tried the files in the link above and got a Hard brick
Used the debricking .IMG file and got TWRP and download mode back
Any suggestions?
Looks like I might need a JTAG/RIFF BOX for this one. If nothing else I spent many Hours of darkness discovering the darkness of android 4.3
If I get recovered from this and with a different rom like 4.1.2 I will be happy. the 4.3 OTA was very stable but I did miss wifi tether and the whole hardbrick thing was kind of a bummer. it would be real nice to have an ODIN file to fix this (AHEM samsung) or atleast perhaps stopped the progression of it to a hard brick.
New update
I got my phone booting up again however there is a catch. That unbrick.img file on my 16GB sd card is still required to boot the phone and I have no cell service what so ever. Tried to check apn settings because at home I sometimes get poor service and I run net10 so I was going to fix my apn and it says insert sim??? the sim is properly inserted???
Click to expand...
Click to collapse
Go into Settings, About Phone, Status and check to see if your IMEI and Serial Number are present. If you only lost your IMEI there's a guide on how to inject it back (I'm not sure where the guide is). However if you've lost your serial number and don't have a Nandroid that can restore it I don't know what to do.
spongdangly said:
Go into Settings, About Phone, Status and check to see if your IMEI and Serial Number are present. If you only lost your IMEI there's a guide on how to inject it back (I'm not sure where the guide is). However if you've lost your serial number and don't have a Nandroid that can restore it I don't know what to do.
Click to expand...
Click to collapse
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
gvazquez82 said:
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
Click to expand...
Click to collapse
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
theramsey3 said:
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
Click to expand...
Click to collapse
I will give that a shot, but what's an APN, sorry. And how do I create one, and is it needed for me to do so?
gvazquez82 said:
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
Click to expand...
Click to collapse
It should be, I'm working right now so I don't have time to fine the guide on how to inject your IMEI. If I remember correctly it involves using QPST. If you have an old (or any) working Nandroid backup that should fix the problem.
FYI, make sure you don't use the guide for the international S3 as it has different hardware and folder structure/contents.
As for the APN, it should automatically fill itself in since it reads it off the SIM Card (I might be wrong).
theramsey3 said:
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
Click to expand...
Click to collapse
I tried it and it work!!!!!!!!!!!!!!!!!
67 texts just came in. Sir, I thank you oh so kindly. You have made this gloomy rainy day oh so joyous.
No problem. Glad I could help you.
The real credit should go to -Mr.X-, loserskater and anyone else(no disrespect there were alot of files) whose stuff I tried to flash lastnight thank you all in the dev community who contribute.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
So I guess the next question, do I try again to install kit kat on my phone.
I've already made bucks of my existing working phone haha....but I'd still like to have kitkat in place. I believe the issue of my phone not reading MD5 confirmations would still be in place, does anyone know how to remedy that situation?
At the same time I'm more than happy to leave my phone as is.
gvazquez82 said:
So I guess the next question, do I try again to install kit kat on my phone.
I've already made bucks of my existing working phone haha....but I'd still like to have kitkat in place. I believe the issue of my phone not reading MD5 confirmations would still be in place, does anyone know how to remedy that situation?
At the same time I'm more than happy to leave my phone as is.
Click to expand...
Click to collapse
Pretty sure you can turn off MD5 checks in TWRP. Probably in CWM too. Sorry if this has been mentioned. Didn't have time to read the whole thread. Just skimmed through.
2nd, there is a major difference between an IMEI that reads 0 and an IMEI that shows unknown. If it shows an unknown simply reflash your ROM and modem and you will be good to go. Sometimes a reboot is all you need. If your IMEI is showing a 0 on the other hand its gone and will require that it be injected back in which is a messy situation that usually results in tour phone being stuck on EDGE.
3rd, as someone mentioned on the previous page, restoring a working nandroid will NOT reinject your IMEI if it shows up as 0. No amount of flashing anything will get it to come back. Not even stock. It needs to be reinjected manually.
flexfulton said:
Pretty sure you can turn off MD5 checks in TWRP. Probably in CWM too. Sorry if this has been mentioned. Didn't have time to read the whole thread. Just skimmed through.
2nd, there is a major difference between an IMEI that reads 0 and an IMEI that shows unknown. If it shows an unknown simply reflash your ROM and modem and you will be good to go. Sometimes a reboot is all you need. If your IMEI is showing a 0 on the other hand its gone and will require that it be injected back in which is a messy situation that usually results in tour phone being stuck on EDGE.
3rd, as someone mentioned on the previous page, restoring a working nandroid will NOT reinject your IMEI if it shows up as 0. No amount of flashing anything will get it to come back. Not even stock. It needs to be reinjected manually.
Click to expand...
Click to collapse
do you know of a good stable kit kat like ROM I could use for the s3? And any speculation as to why the ROMs werent taking for me?
First person to help gets paid for your time...
Problem: I have a s3 i747 from att.
it has 4.3 stock.
I use srs to unlock all my phones.
well when I went to unlock this one it said it had new security.
Usually when this happens I odin this file that downgrades the modem.
well I did it and now I have null imei and unknown baseband
I tried restoring to stock, didn't help. Through kies and odin.
I need to put it back the way it was... can someone please help..... ill paypal you as soon as its working again...thanks
So you're currently at stock, unlocked? Does the phone boot at all?
These threads may help:
http://forum.xda-developers.com/showthread.php?t=2658486
http://forum.xda-developers.com/showthread.php?t=2722660
yes it is still stock 4.3. no its not unlocked. everything works and boots fine. just no signal because of null imei and unknown baseband.
I think I need to just flash a modem via odin....I just don't know which one
http://forum.xda-developers.com/showthread.php?t=1831898
There's seems to be a rash of this happening in the past month. You'll probably find that link helpful but first check and see if others found a better solution.
Yes. Flash the 4.3 modem.
As of 4.3, flashing any older modem will no longer work, resulting in an unknown imei and baseband version. Flashing back to the correct modem nearly always solves this issue.
It will be like this from now on btw. You cannot use any modem except the one which matches your current firmware build.
This means our free unlock method no longer works unfortunately. But you can get unlocked for just a few bucks using one of the many services online. I know some are on ebay, but google will find others as well.
I installed cwm and downloaded the modem but im lost from there.
do I rename it update.zip?
Nope, just flash like you would any other rom.
Because you asked about renaming it to update.zip though, I have to ask if you are certain you are in cwm? If you had previously updated via ota it may restore the stock recovery every time you reboot. If this is happening, reflash cwm in Odin, but uncheck auto reboot. Wait until it says PASS, then unplug and pull the battery.
Next put the battery back in and boot to recovery. (Volume up, home, power. Release power only after it vibrates)
If you are sure you are in cwm though, just flash the modem normally.
Yes im sure its cmw. when I open recovery and look for the zip its nowhere to be found. that's why I was asking if I should change the name.
I did try it by changing the name but the file still doesn't show up.
It's an IMEI problem. If you haven't made a backup of the IMEI folder you can't do anything.
Sent from my SM-G900H using XDA Free mobile app
daddydv said:
Yes im sure its cmw. when I open recovery and look for the zip its nowhere to be found. that's why I was asking if I should change the name.
I did try it by changing the name but the file still doesn't show up.
Click to expand...
Click to collapse
Make sure the sdcard is mounted. Have you tried getting to it on both internal and external cards?
Thin_Bezel said:
It's an IMEI problem. If you haven't made a backup of the IMEI folder you can't do anything.
Sent from my SM-G900H using XDA Free mobile app
Click to expand...
Click to collapse
Not true. 90% of unknown baseband and imei problems ive helped people with lately just needed the correct modem. And even if it were the imei, I can still help with that. Im convinced in this case its just the modem though.
Thanks doc... that was the problem...imei and baseband are back. donation has been sent....thanks again.
Hey thanks man! I do appreciate it, but I am just glad I could help! I will definitely put it to good use though! (Broke the lcd on my S3 a while back and haven't had the disposable funds to fix it. Something always comes up...lol!) Will be adding it to my savings for this purpose!
Anyway, since we were slightly on the IMEI topic, there is a backup you should do if you haven't already. (Root is required for this to work though.)
Its super simple and will create an on device backup of your nv data. The backup will be stored on a couple of partitions we never touch, not even with firmware flashes. This essentially makes it a permanent backup. The cool thing about it is every time you reboot, the system checks for any corruption, and if detected, it will automatically restore from this backup. So if it were to ever happen, you probably wouldn't ever even notice it!
Install the Terminal Emulator from the play store. Open and enter this:
su
reboot nvbackup
Thats it! Device will reboot and create your backup. This should prevent you from ever suffering from a lost IMEI!
DocHoliday77 said:
Hey thanks man! I do appreciate it, but I am just glad I could help! I will definitely put it to good use though! (Broke the lcd on my S3 a while back and haven't had the disposable funds to fix it. Something always comes up...lol!) Will be adding it to my savings for this purpose!
Anyway, since we were slightly on the IMEI topic, there is a backup you should do if you haven't already. (Root is required for this to work though.)
Its super simple and will create an on device backup of your nv data. The backup will be stored on a couple of partitions we never touch, not even with firmware flashes. This essentially makes it a permanent backup. The cool thing about it is every time you reboot, the system checks for any corruption, and if detected, it will automatically restore from this backup. So if it were to ever happen, you probably wouldn't ever even notice it!
Install the Terminal Emulator from the play store. Open and enter this:
su
reboot nvbackup
Thats it! Device will reboot and create your backup. This should prevent you from ever suffering from a lost IMEI!
Click to expand...
Click to collapse
You can also use qpst to backup imei. Windows app. Free. Lots of walkthroughs around for those less comfortable with cli.
Nvm. 10char
azuziel said:
You can also use qpst to backup imei. Windows app. Free. Lots of walkthroughs around for those less comfortable with cli.
Click to expand...
Click to collapse
I know, I already have it and have used it and other tools to help fix at least 700-800 S3's, probably more! (No, i do not charge for my help either.) I dont tell about it or give it out unless its absolutely needed for a legitimate imei restore though. Too many people try to use it illegally and Im not willing to take the chance. Its the main reason most of the info has been deleted from everywhere. Only a few threads here and there get by the mods it seems.
Anyway, to my knowledge, no one who has run this backup has ever lost their IMEI. It even seems to help for those occasions after flashing a cm rom where the imei displays "unknown". (Apparently, at least on the T999, cm sometimes has problems reading the nv data. If rebooting several times doesnt solve, stock firmware does).
At this point I believe if you run this backup, you will have no need for a .qcn or .txt file backup, which is why I just dont mention it anymore. And if it does happen, people can pm me and ill be happy to help fix it.
Because of how I understand this backup to function, I do believe if it had been run during first boot, we would've never seen so many imei problems to begin with! I just dont understand why Samsung refuses to do this!
Anyway, that's why I dont mention those tools anymore. If you have any questions about any of it, please feel free to PM me and ill try to explain better.
Hi,
I plugged my note 4 into the OEM charger and all of a sudden it just goes into a bootloop continuously.
Occasionally it will reach the home screen and reboot again, but more often than not.. it reboot before the Sprint logo comes up.
Was fine before i plugged it in and was trouble free prior to that.
My phone is stock, not rooted.
The fact that it will reboot even at the Note 4 welcome sign is leading me to believe this could be a hardware issue...
Any ideas?
Anybody had the same situation and had luck troubleshooting or fixing this?
Any and all help i much appreciated...
Regards,
asmd.
Can you boot into recovery?
First thing I'd try is to pull battery, boot into stock recovery and wipe cache and try to boot.
If not booting, try wiping cache and dalvik.
You have the option to just take it in for evaluation but you should determine if you have reactivation lock enabled before doing anything else.
Still not booting? Factory reset. But if you have reactivation lock enabled that is not a good idea. It would be better if one of the two above booted the phone.
If reactivation lock is enabled, you need to install the same update the phone is on to prevent factory reset protection from activating. Don't factory reset yet; Odin or taking in for service may be your only option. If it boots, you should be able to open with same unlock method as before.
If you have reactivation lock disabled, you're free to try factory reset or update to latest through KIES. I've heard Samsung Switch may work too. You could also factory reset and update or emergency recover with one of those.
If still not booting, if it just updated, I'd mention that and not the charger you mentioned. It could be corrupt memory due to battery failing or bad update. The eMMC may be failing too.
Sent from my SM-N910P using Tapatalk
samep said:
Can you boot into recovery?
First thing I'd try is to pull battery, boot into stock recovery and wipe cache and try to boot.
If not booting, try wiping cache and dalvik.
You have the option to just take it in for evaluation but you should determine if you have reactivation lock enabled before doing anything else.
Still not booting? Factory reset. But if you have reactivation lock enabled that is not a good idea. It would be better if one of the two above booted the phone.
If reactivation lock is enabled, you need to install the same update the phone is on to prevent factory reset protection from activating. Don't factory reset yet; Odin or taking in for service may be your only option. If it boots, you should be able to open with same unlock method as before.
If you have reactivation lock disabled, you're free to try factory reset or update to latest through KIES. I've heard Samsung Switch may work too. You could also factory reset and update or emergency recover with one of those.
If still not booting, if it just updated, I'd mention that and not the charger you mentioned. It could be corrupt memory due to battery failing or bad update. The eMMC may be failing too.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply...
Ive been messing with it all morning... and if i leave it a lone and it cools, it will last a little longer than when it becomes warm, rebooting quicker and quicker.
i managed to get into recover and did a factory reset and cleared cache.
it has made no difference.
The longest time its gone before rebooting is the lock screen.... and the it reboots again.
as it warms, it eventually wont even get past the Note 4 welcome screen before rebooting.. and then finally freezing and will require a battery pull.
Makes no difference if its on charge or off.
i have a sinking feeling about this.....
Could be terminal but you haven't tried to flash firmware on partitions with Smart Switch, KIES or Odin yet. Right? You can check the phone status while in download mode to verify reactivation lock is disabled.
Try one of those on PC or take it to Sprint to have it flashed again.
If you purchased at Best Buy and they have a Samsung Experience kiosk, they can do that too. Dunno, maybe it doesn't matter if you purchased there or not but they've flashed my phone a couple of times.
I've tried to guide you down the path of least effort to restore your, if possible. There's still some hope of recovery.
Edit: Your battery could be suspect. Let it cool and plug in to make sure it's at least 60% or higher. If the battery is near a year old, I'd suggest fully charging but get a replacement if you frequently discharge it to 15% or lower. Especially if you use fast charging.
But you've most likely discharged it with all that reboot activity and heating up. Kudos to you if you're managing all that and keep a healthy battery. Otherwise, the battery may be contributing to or causing your issues.
Sent from my SM-N910P using Tapatalk
thank you for the help..
reactivation lock is off.
i can't get it to reliably not reboot anywhere in any screen.. only screen that will stay on for any period of time is recovery... but the phone stays cool.
Its not the battery, i have two, and both do the same thing.. the battery does not get warm, area that gets warm is neft to the battery below the sd card slot. (sd card removed).
Frequency of hang/reboot seems to be related to how warm that area gets.
The most i have managed to do is get into my phone past the lockscreen and it will shortly freeze and reboot as it warms up.. it will reboot at the note 4 welcome screen or sprint logo... and repeat... eventually to hang.
Both batteries are charged fully using the external charger. (samsung oem)
Shame, not a scratch on her....
Oh well, on to Ebay for parts/AS IS and time to move on...
Even if doubtful, I'd still take it back to Sprint or place of purchase.
The Note 4 has a bit of history with eMMC failure. It's even happened with updates and Samsung and Sprint is apparently aware of it. A while back I saw that listed as an ongoing carryover of known issues that needed resolution.
I don't have true stats on exchanges but several users here have repeatedly gotten deals on replacement phones, paying a small percentage when they failed- similar to yours.
OTA updates have also been suspect to cause eMMC failure. But honestly, l don't know what causes this: bad hardware or updates? Maybe it's just bad hardware not taking updates well? Nonetheless, I don't know if I've just been lucky or my hardware is stable. Still going strong here with no hint of failure.
Sent from my SM-N910P using Tapatalk
can i still take it back even though its out of warranty?
nearing 2 years now....
asmd6230 said:
can i still take it back even though its out of warranty?
nearing 2 years now....
Click to expand...
Click to collapse
No promises. Couldn't hurt. If you don't like the answer you get from first Sprint store, try another.
I would mention that bit of history with the updates.
Sent from my SM-N910P using Tapatalk
asmd6230 said:
Hi,
I plugged my note 4 into the OEM charger and all of a sudden it just goes into a bootloop continuously.
Occasionally it will reach the home screen and reboot again, but more often than not.. it reboot before the Sprint logo comes up.
Was fine before i plugged it in and was trouble free prior to that.
My phone is stock, not rooted.
The fact that it will reboot even at the Note 4 welcome sign is leading me to believe this could be a hardware issue...
Any ideas?
Anybody had the same situation and had luck troubleshooting or fixing this?
Any and all help i much appreciated...
Regards,
asmd.
Click to expand...
Click to collapse
I have the exact same issue going on with my wives phone. Just started yesterday out of no where rebooting over and over. Never really getting past the Samsung splash screen. She got an update like a week ago, but other than downloading a new app several hours earlier nothing sticks out to why its happening. I was able to once get into safemode, but the phone rebooted a minute into it and typically doesn't even get to the sprint splash screen when I've tried to do it since. It's totally stock and has not been unlocked or rooted. I thought it could be the battery since so many of these boot issues on the Note4 deal with that when googling, but my battery from my working Note4 in her phone does the same thing and her battery in my phone works just fine. I can get into the recovery options menu (volume up + home + power) and I can get into the download area (volume down + home + power) for loading bootloaders and such for long periods of time with no issues. I've cleared the cache with no luck. Haven't tried factory reset yet because I want to try to recover the photos and stuff first. Searching for the issue on google I came across this software (android-recovery.net/android-recovery-mode.html#two) where I was able to use the download area and connect the phone with this app which used its own bootup and it was able to show me all the files on the phone for recovery so we could retrieve them. It wanted $50 to complete the process though and, knowing the advances that everyone here has made on their phones I decided to decline that and search these forums for a way to just access the file directory of my the phone and retrieve my wives stuff prior to factory resetting it. I believe something is wrong with the bootloader of the phone and that is why it cannot get to the android OS to start up, but I could be wrong. Reading various articles made me to believe that if I just were to unlock the phone for rooting that possibly that could fix this issue with the bootloader or at least be able to recover her photos and stuff. I do have insurance on the phone and could get it fixed or replaced, but that would be a $200 deductible I believe and first thing they're going to try is factory resetting the phone which will lose her data we're trying to save.
It almost seems as if I were to get TWRP installed that I'd be able to access the files without the need of loading any ROMs. But I'm not sure if that will work in my case or erase data when I do it. The threads I'm reading aren't clear on that part. I would really be grateful if anyone could help me out with figuring out the easiest way to recover her stuff or get it working. Its been a long time since I've unlocked any phones and they were all iPhones back in the day when they were only on AT&T and I had T-mobile and wanted to it work.
@dsm_gsx97
I would suggest you try Odin and install the same update, if possible. That may be the most likely to retain your data if it's not corrupted.
Unfortunately, I don't think TWRP recovery works for Note 4 to copy data to PC. But if you go with that, know that it will trip Knox and void factory warranty. But if that's not an issue, you could copy data from internal memory to extSdCard to salvage it if it's not corrupt or private.
I know KIES has an emergency firmware recovery mode that may offer to reprogram it. But you may lose your data. Not sure but I think your phone has to booted into system to backup with KIES or Smart Switch?
This thread has the recent available stock tars, Odin and general instructions to get you started.
http://forum.xda-developers.com/showthread.php?p=63868221
Sent from my SM-N910P using Tapatalk
samep said:
@dsm_gsx97
I would suggest you try Odin and install the same update, if possible. That may be the most likely to retain your data if it's not corrupted.
Unfortunately, I don't think TWRP recovery works for Note 4 to copy data to PC. But if you go with that, know that it will trip Knox and void factory warranty. But if that's not an issue, you could copy data from internal memory to extSdCard to salvage it if it's not corrupt or private.
I know KIES has an emergency firmware recovery mode that may offer to reprogram it. But you may lose your data. Not sure but I think your phone has to booted into system to backup with KIES or Smart Switch?
This thread has the recent available stock tars, Odin and general instructions to get you started.
http://forum.xda-developers.com/showthread.php?p=63868221
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Thank you very much for the quick response. I would rather not void my factory warranty in case I have to use the insurance to replace it so it sounds like TWRP is out which is why I didn't use it yet because I was worried about that. I did try KIES and it said that firmware upgrade and initialization would erase all data. So I ruled out using that too. I did notice while in the recovery menu of her phone that it says she's on N910PVPU1ANIE ...so I put my phone in recovery menu and I'm on N910PVPU4DPH4. Googling her version it looks like hers is very old and mine is fairly new which makes sense because I did the update a few days ago also. I wonder if hers is so old because that's what the other software program put it on to be able to bootload it to recover the files.
Anyways looking at your link I think I'll try oden with one of the more recent TARs after getting her stuff off with that program. Yes I'll just pay the $50 for peace of mind. I really appreciate your advice. Its not easy gathering all the answers without really being involved on this forum so thank you for that thread. None of the TARs listed is the update I have, but that shouldn't matter should it? As long as its a newer one than what it says she has?
dsm_gsx97 said:
Thank you very much for the quick response. I would rather not void my factory warranty in case I have to use the insurance to replace it so it sounds like TWRP is out which is why I didn't use it yet because I was worried about that. I did try KIES and it said that firmware upgrade and initialization would erase all data. So I ruled out using that too. I did notice while in the recovery menu of her phone that it says she's on N910PVPU1ANIE ...so I put my phone in recovery menu and I'm on N910PVPU4DPH4. Googling her version it looks like hers is very old and mine is fairly new which makes sense because I did the update a few days ago also. I wonder if hers is so old because that's what the other software program put it on to be able to bootload it to recover the files.
Anyways looking at your link I think I'll try oden with one of the more recent TARs after getting her stuff off with that program. Yes I'll just pay the $50 for peace of mind. I really appreciate your advice. Its not easy gathering all the answers without really being involved on this forum so thank you for that thread. None of the TARs listed is the update I have, but that shouldn't matter should it? As long as its a newer one than what it says she has?
Click to expand...
Click to collapse
Was it only the OTA update that updated that phone?
NIE is the original-initial release of the Note 4. If OTA tried to update it, it must have failed?
Nonetheless, you should know the history of that phone. I wouldn't install one of those recent updates until you've backed up your data. You may lose your data jumping to a much newer update.
The phone doesn't boot at all? If it does boot, you could run Phone Info for Samsung from Google Play to see what the partitions are actually at. That would help to recover that data if possible to do so. But also KIES could backup data if it boots.
The NIE stock tar is in post #2 of this thread.
http://forum.xda-developers.com/showpost.php?p=56853325&postcount=1
If it boots after Odin, your data may be OK. If not, may be corrupted data or partition.
Sent from my SM-N910P using Tapatalk
samep said:
Was it only the OTA update that updated that phone?
NIE is the original-initial release of the Note 4. If OTA tried to update it, it must have failed?
Nonetheless, you should know the history of that phone. I wouldn't install one of those recent updates until you've backed up your data. You may lose your data jumping to a much newer update.
The phone doesn't boot at all? If it does boot, you could run Phone Info for Samsung from Google Play to see what the partitions are actually at. That would help to recover that data if possible to do so. But also KIES could backup data if it boots.
The NIE stock tar is in post #2 of this thread.
http://forum.xda-developers.com/showpost.php?p=56853325&postcount=1
If it boots after Odin, your data may be OK. If not, may be corrupted data or partition.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
She's done plenty of updates over the last few years since we got the phoens. In fact she did that last update a few days before I did. That's why I was confused when I noticed what it said at the top of the bootloader screen for her update version. The phone does not boot at all. Only to the the Samsung splash screen and never gets to the sprint splash screen. It initially would get further, but now doesn't at all. I went ahead and paid for that software and have now backed up all her stuff. Was hoping to fix it without factory resetting the phone. At this point at least I have a backup, but ideally it would save her from losing all her texts and other crap.
dsm_gsx97 said:
She's done plenty of updates over the last few years since we got the phoens. In fact she did that last update a few days before I did. That's why I was confused when I noticed what it said at the top of the bootloader screen for her update version. The phone does not boot at all. Only to the the Samsung splash screen and never gets to the sprint splash screen. It initially would get further, but now doesn't at all. I went ahead and paid for that software and have now backed up all her stuff. Was hoping to fix it without factory resetting the phone. At this point at least I have a backup, but ideally it would save her from losing all her texts and other crap.
Click to expand...
Click to collapse
In that case, try the most recent stock tar in the first thread you were about to try.
Something seems off but trying to flash the original stock tar would be problematic if it was updated beyond Android 5.0
If it doesn't boot, you'll most likely have to factory reset it.
Sent from my SM-N910P using Tapatalk
Note 4 bootloop
just heat main ic little bit with past and check there is no heatup board on boot.and set is ok.tested
Hey guys, been reading through the threads and not really finding a clear answer or solution to this problem. This is a completely stock sprint sph-l710. I started getting this box with yellow lettering overshadowing the primary display of which I've learned indicates the phone is in 'factory mode'. I thought performing a factory reset would fix this but it did not. I noticed when you boot the phone in recovery mode I see the efs error. I am thinking the underlying issue is with fixing the efs problem. Now that I have reset the phone I no longer have data network access, im guessing because of this factory mode. I am new to this and not real understanding of the lingo everyone uses. From what I've read Im worried im going down a rabbit hole if i start tinkering. I am looking for clear instructions to repair what I think is corrupted software (I'm guessing the operating system software). The instructions I've seen seem to skip steps that are probably rudimentary to everyone else but leaves me without a starting place. I have downloaded oden but i am not certain again without precise instructions that I am not going to permanently mess up my phone.. there appear to be a number of variations of this device and i want to make sure the instructions I get will work on mine. I will take any advise on getting this resolved. I am not opposed to rooting the phone either if that fixes the problem (no idea how to do this, never tried, but some threads on here I think I can follow to do it safely). With that said, different threads also seem to indicate (emphasize 'seem to') that team win recovery can fix this but there are no clear responses regarding my issue of a solid fix. Thank you for any help
timbow4 said:
Hey guys, been reading through the threads and not really finding a clear answer or solution to this problem. This is a completely stock sprint sph-l710. I started getting this box with yellow lettering overshadowing the primary display of which I've learned indicates the phone is in 'factory mode'. I thought performing a factory reset would fix this but it did not. I noticed when you boot the phone in recovery mode I see the efs error. I am thinking the underlying issue is with fixing the efs problem. Now that I have reset the phone I no longer have data network access, im guessing because of this factory mode. I am new to this and not real understanding of the lingo everyone uses. From what I've read Im worried im going down a rabbit hole if i start tinkering. I am looking for clear instructions to repair what I think is corrupted software (I'm guessing the operating system software). The instructions I've seen seem to skip steps that are probably rudimentary to everyone else but leaves me without a starting place. I have downloaded oden but i am not certain again without precise instructions that I am not going to permanently mess up my phone.. there appear to be a number of variations of this device and i want to make sure the instructions I get will work on mine. I will take any advise on getting this resolved. I am not opposed to rooting the phone either if that fixes the problem (no idea how to do this, never tried, but some threads on here I think I can follow to do it safely). With that said, different threads also seem to indicate (emphasize 'seem to') that team win recovery can fix this but there are no clear responses regarding my issue of a solid fix. Thank you for any help
Click to expand...
Click to collapse
Odin will flash the factory firmware for you. Get firmware from sammobile. Look for sph L710 device, and firmware with NJ2 in the name. Put phone in download mode, (power off then hold power+home+volume down) plug in phone to pc. Wait till Odin says added. Click AP in odin, select firmware you downloaded, click start. When it's done, unplug phone, remove battery, put it back in and reboot.
This may not fix your efs partition, but it's the first thing to try.
Odin
I found the thread for nj2 firmware here
issue still persists
Hey Madbat, thank you so much for reaching out to me and giving me the advise. Installing the firmware through odin was really easy. Thank you for that! However, it did not fix the issue. When the phone came back up it still has the exact same problem. I am going to attach a couple pictures to show you what i am seeing... Really appreciate your time and help!
hell, sorry it says im a new user and wont let me post the pictures...
timbow4 said:
Hey Madbat, thank you so much for reaching out to me and giving me the advise. Installing the firmware through odin was really easy. Thank you for that! However, it did not fix the issue. When the phone came back up it still has the exact same problem. I am going to attach a couple pictures to show you what i am seeing... Really appreciate your time and help!
hell, sorry it says im a new user and wont let me post the pictures...
Click to expand...
Click to collapse
Sorry, I never had that issue. Maybe someone else will chime in with experience on the efs partition. That's not a triband s3 is it? (Sph l710t?) T at the end means triband. Second thought, I don't think the firmware would have flashed if it was triband.
How did you wipe your efs?
Its not a tri band. Just SPH-L710. Wish this forum would let me post the pictures of what my phone is doing.. Since the firmware doesnt correct the issue I would think then its a problem with the operating system itself. I have been scouring the web and have found various threads specifically about efs repairs but they entail doing things that seem awful complicated. And i dont know if those things work on my model phone. Maybe rooting the phone gets deep enough to over write or repair the issue. Is there not a way to restore the operating system itself maybe or is that what a replacement ROM does? I am thinking of trying my hand at rooting the phone and seeing what happens. One thread indicated TWRP would backup and restore the EFS file. Im thinking if it backs up a corrupt efs file what good is that, maybe it fixes it too. Found an excellent video on XDA for rooting the S3. Hopefully it or I dont make it worse. Love to get this one fixed but i guess the reality is the phone is old. Thank you for the input
timbow4 said:
Its not a tri band. Just SPH-L710. Wish this forum would let me post the pictures of what my phone is doing.. Since the firmware doesnt correct the issue I would think then its a problem with the operating system itself. I have been scouring the web and have found various threads specifically about efs repairs but they entail doing things that seem awful complicated. And i dont know if those things work on my model phone. Maybe rooting the phone gets deep enough to over write or repair the issue. Is there not a way to restore the operating system itself maybe or is that what a replacement ROM does? I am thinking of trying my hand at rooting the phone and seeing what happens. One thread indicated TWRP would backup and restore the EFS file. Im thinking if it backs up a corrupt efs file what good is that, maybe it fixes it too. Found an excellent video on XDA for rooting the S3. Hopefully it or I dont make it worse. Love to get this one fixed but i guess the reality is the phone is old. Thank you for the input
Click to expand...
Click to collapse
Backing up and restoring it won't help. You already installed a new operating system ( that's what the firmware is).the efs is part of your radios. If I remember correctly it contains your imei and other important things specific to your phone.
You may be out of luck there dude. Don't know how you wiped your efs.
Rooting this phone is simple. Just flash TWRP with Odin. Download the Twrp image from their site. Same as flashing the firmware, only you select recovery instead of AP in odin and select the Twrp image.tar instead of the firmware tar.
https://dl.twrp.me/d2spr/
Use the top on the page. (Newest)
And then use twrp to flash either SuperSU, or Magisk.
Done.
Flashing a custom rom will not fix your issue. You need a working efs. Flashing any operating system will not fix it (you already flashed the whole operating system).
Twrp can restore an efs, but only if you have a working one to backup first. You were right about backing up yours now and restoring will do nothing.
Has it ever been activated?
Prior to this, every once in awhile when i changed a battery out and turned the phone on it would have a pop-up screen tell me something was bad and the phone needed to be reset (something along those lines) and i always just turned the phone back off and on and it booted up fine each time. That may have been an indicator that something, file or system file maybe was corrupted. Then a few week ago when it booted up it started doing this whole thing. Prior to me factory restoring the phone here recently it was completely functional but since the restoration it will no longer connect me to the network. If you goto settings and click on some system features it will turn the network on for that specific function (temporarily) but does not give me any other access. It tells me that the network works but it being blocked (maybe because of the factory mode issue). The wifi works and i can make and receive calls. Still manageable but very annoying. Im going to try your instructions with installing TWRP. If i am successful then maybe i can also get into the system files and possibly restore the broken one.. Thanks again
update
So I have successfully rooted the phone by intstalling TWRP ver 3.2.1 and using TWRP to flash SuperSU ver 2.82. I also installed root explorer to get access to system files. I gained access to the EFS folder and it is empty. So now I'm not understanding if the folder is completely empty how does the phone still work at all? More research led me to a XDA developer that put together a program called EFS Professional which is supposed to backup and restore efs or imei data. Really slick program, basically takes the complication out of locating and backing up the EFS information yourself. (I would include a link but I still cant..) It includes an ADB shell and the ability to make some changes to the phone including directly turning off factory mode . It also had me install an application called BusyBox Pro which is also a very handy tool for getting access to system files. What I don't understand is that the EFS Professional program seems to locate the efs information on my phone and backups it up and then restores it from said backup however when I look at the efs folder its empty. Perhaps not all the efs information is located in the efs folder. And of course since that folder is empty the function of turning factory mode off fails because it cant find the files. I have found a few threads that has very simple instructions once you have super user access you can go right into the efs folder to factory mode and simply turn it off. Mine is empty.. So again the problem continues. Possibly with access to the ADB shell and more help from folks on here I can figure out a way to restore my efs information. I don't know if the efs information can be used from a another same model phone, I'm guessing not if it has a specific imei identification. Im working hard on this but still unsolved. I know way more at this point then I did but I think I still know just enough to be dangerous. Thankfully my phone is still functional at this point..