Related
I was restoring a Nandroid on my Note 3 tonight- when I rebooted, I got an error message saying Process System isn't responding - do you want to stop it or wait - no matter which option I chose, the phone would reboot - I tried to restore other nandroids and got the same error,
I tried to Odin back to stock and on reboot - I got the same message.
Not sure what to do ?
It's kind of like the old "death loops' but I don't recall ever seeing that particular error message -
Any suggestions? RIght now I can't do anything with this phone - ???
same problem here..... i get no signal and bootloops
Wtf. Im getting the same thing here. Driving me crazy. Im out of solutions
this worked like a charm for me. Im back up. I even used the same exact backup which was looping after without efs of course.
http://forum.xda-developers.com/showthread.php?t=2471421
1. Reboot to recovery
2. Hit "Advanced" Select "Terminal Command"
3. Hit "Select" (lower right corner)..Do not select any specific folder, just hit select..
4. keyboard will open, type in the following commands, make sure you put the spaces and / where they need to be, it needs to look exactly as outlined..
mke2fs /dev/block/mmcblk0p12
Hit Go - The command will run.
Clear the box, type the following command
mkdir /efs
Hit Go - The command will run.
Clear the box, type the following command
mount -t ext4 /dev/block/mmcblk0p12 /efs
Hit Go - The command will run.
thanks dreisus but i tried your fix many times but no luck still bootloop
trezegol said:
thanks dreisus but i tried your fix many times but no luck still bootloop
Click to expand...
Click to collapse
Well if you get the fix let me know. Im always interested in different solutions. How did bootloops start. Mine started with sinmply trying to install a theme through twrp .
i just did a efs backup after that install recovery boot into recovery didnt flash anything i just restart to system and bootloop started ... ill let you know if i get it fix im willing to try anything even if it hardbrick my phone r doesnt work so if anyone whants me to try something let me know
me also !!!!.. WTF is happening?
I flash it stock firmware 3 times... still same
This problem happen to me yesterday... I just rebooted my phone and it started happening. I get the Process System isnt Responding error message along with an infinite bootloop. I have no signal and my baseband said unknown when I finally got in and then it went to bootlooping again. I don't know WTF is going on lol. I didn't do anything to my device. It was perfect until yesterday. Can else anyone chime in on what the problem may be?
Edit: I performed the "Fix" with wiping the efs but I have to perform it every couple of reboots because after I reboot 2-3 times, it starts happening again.
lm that guy said:
This problem happen to me yesterday... I just rebooted my phone and it started happening. I get the Process System isnt Responding error message along with an infinite bootloop. I have no signal and my baseband said unknown when I finally got in and then it went to bootlooping again. I don't know WTF is going on lol. I didn't do anything to my device. It was perfect until yesterday. Can else anyone chime in on what the problem may be?
Edit: I performed the "Fix" with wiping the efs but I have to perform it every couple of reboots because after I reboot 2-3 times, it starts happening again.
Click to expand...
Click to collapse
Happens to me as well on all roms except jedi elite. I don't know if it's the phone or something I'm doing but I've just accepted jedi for now my buddy can only flash wicked and it happens on all others for him
Jedi Elite Powered T-Mobile Note 3
I just had this happen after a reboot on me today. I rebooted the phone again and it was fine. Stock rooted. Only time it has ever done it.
str8killinya said:
Happens to me as well on all roms except jedi elite. I don't know if it's the phone or something I'm doing but I've just accepted jedi for now my buddy can only flash wicked and it happens on all others for him
Jedi Elite Powered T-Mobile Note 3
Click to expand...
Click to collapse
krelvinaz said:
I just had this happen after a reboot on me today. I rebooted the phone again and it was fine. Stock rooted. Only time it has ever done it.
Click to expand...
Click to collapse
This is so weird. Before, I could flash any ROMS I wanted to with no problems. It started when I was using the ROA ROM but like I said I flashed that ROM many times and was using it for 3 days solid.
But anyways, I sadly had to get rid of mine. No matter what ROM im using results in a instant reboot even on the stock firmware. I just hope I get a new device with knox 0x0 because im staying on stock for a bit.
lm that guy said:
This is so weird. Before, I could flash any ROMS I wanted to with no problems. It started when I was using the ROA ROM but like I said I flashed that ROM many times and was using it for 3 days solid.
But anyways, I sadly had to get rid of mine. No matter what ROM im using results in a instant reboot even on the stock firmware. I just hope I get a new device with knox 0x0 because im staying on stock for a bit.
Click to expand...
Click to collapse
I think I must have wiped my EFS or something got corrupted - I followed Steps posed by Steve Lazarus - in this thread and it worked fine - (I also later found a flashable fix that does the same thing on the N9005 Thread...so if it happens again, that is what I will use.
I do know that the NOTE 3 Seems much more prone to getting soft bricked than just about any other phone I have ever used..
mocsab said:
I think I must have wiped my EFS or something got corrupted - I followed Steps posed by Steve Lazarus - in this thread and it worked fine - (I also later found a flashable fix that does the same thing on the N9005 Thread...so if it happens again, that is what I will use.
I do know that the NOTE 3 Seems much more prone to getting soft bricked than just about any other phone I have ever used..
Click to expand...
Click to collapse
Yeah, im 100% sure it has something to do with the EFS. It somehow got corrupted. Because when I finally get into the system, I check my baseband and it said unknown.
But the thing is, I never touched my EFS at all. I just rebooted one day and it was happening. Also I'd like to mention, that whenever I restored my EFS with the latest TWRP, everything started working again!!! BUT... i would have to perform this every 2-3 reboots because the problem would continue to arrive. So I had 2 choices... Perform an EFS restore every time I boot my phone or just return it.
lm that guy said:
Yeah, im 100% sure it has something to do with the EFS. It somehow got corrupted. Because when I finally get into the system, I check my baseband and it said unknown.
But the thing is, I never touched my EFS at all. I just rebooted one day and it was happening. Also I'd like to mention, that whenever I restored my EFS with the latest TWRP, everything started working again!!! BUT... i would have to perform this every 2-3 reboots because the problem would continue to arrive. So I had 2 choices... Perform an EFS restore every time I boot my phone or just exchange it. I chose the latter.
Click to expand...
Click to collapse
I never touched my EFS either - but somehow when I made a back up on a rom I was using, when I rebooted afterwards I got those nasty reboots. then nothing would work - no other backups - I tried using ODIN To go to stock - nada - but following the instructions from Lazarus - I was able to get it going again.
mocsab said:
I never touched my EFS either - but somehow when I made a back up on a rom I was using, when I rebooted afterwards I got those nasty reboots. then nothing would work - no other backups - I tried using ODIN To go to stock - nada - but following the instructions from Lazarus - I was able to get it going again.
Click to expand...
Click to collapse
If you are referring to wiping the EFS using TWRP I tried that and it worked. But the problem would come back every couple of reboots. And I wasn't about to perform this every time I reboot lol. Now that I think about it, have you ever experienced that followup random reboot when you boot your phone? Maybe that was a warning sign that this was coming
lm that guy said:
If you are referring to wiping the EFS using TWRP I tried that and it worked. But the problem would come back every couple of reboots. And I wasn't about to perform this every time I reboot lol. Now that I think about it, have you ever experienced that followup random reboot when you boot your phone? Maybe that was a warning sign that this was coming
Click to expand...
Click to collapse
I have noticed that occasionally the phone will boot up - look like is almost ready and then reboot - usually only happens once and then the phone boots fine. I have always thought it was the finickyness of the NOTE 3 - and the newness of custom recovery's for the NOTE 3 - I honestly don't know why it does it - the most recent version of TWRP seems more stable - but who knows....?
+Jason Ren https://db.tt/QQfxFQlo this fixed boot my loops. flash in recovery. keep it on your sdcard for future use.
Sent from my SM-N900T using Tapatalk
Hello, there.
Get prepared for a lot of bad bad stuff..
So, my Galaxy Nexus was running on a CM-11 Snapshot build, with AOSP kernel. Yesterday, out of the blue, the phone started to get terribly slow and not responsive at all. After a few minutes, it restarted, only to do the same. A couple of minutes maybe, booting up, then get slow and reboot - it did this constantly, and it still does.
I have tried to go into clockworkmod recovery - wiped cache, wiped dalvik cache, wipe user data (factory reset). The phone booted up again, but my apps, etc. were still there! Nothing had happened. I did it a couple of times, but nothing at all.
Then, I have found a .zip file that was still on my memory, with the latest snapshot I had installed. I tried installing it with the install from sd card option, but when it loaded up again, I was still seeing the same apps, background etc.! Nothing had happened and no error message.
Decided to leave the "custom" days behind, I downloaded the stock image for my Gnex. However, since it is a yakjuxw build, I had to flash the yakju option - so not the ideal "stock" package. Using the google installer, I was unable to proceed, since the bootloader number was different than the one that the installer expected, so it exited.
I have found online the amazing Nexus Root Toolkit from WugFresh. I tried to flash it from there, enabling the "force flash" option.
It started out ok.. But when it went to the "system" portion, it took 25 minutes (!) to complete and then in the "user data" portion, it said "write failure".
Still, rebooted and I was still seeing my apps etc. What on earth is happening?
Honestly, I would expect that it would be bricked by now, with all these rom flashes and factory resets. I even tried flashing the stable CM version for it, but still nothing had changed.
Any help would be greeeeatly appreciated.
Yeah im pretty sure your emmc is fried. So you have two options: buy a new phone or a new motherboard. You van check by locking the bootloader if its still unlocked upon reboot your emmc is fried..
Sent from my Galaxy Nexus using XDA Free mobile app
I runned "fastboot oem lock' from my command line, and I got the status "OK".
Then I pressed "restart bootloader" on my phone, but it still says "lock state - unlocked".
So I suppose, I should let it rest in piece, or change the motherboard?
I think a motherboard is more expensive than a new phone. If it is just let it die. If it isnt you can buy a new motherboard and swap it. But I dont think that is a smart move now. The moto g for example is a awesome phone for (i think) almost the price of a new mobo.
Sent from my Galaxy Nexus using XDA Free mobile app
same problem here
It makes me wonder, I'm having the exact same issue just a couple of days later. Is this the planned obsolescence thing?
withend said:
Hello, there.
Get prepared for a lot of bad bad stuff..
So, my Galaxy Nexus was running on a CM-11 Snapshot build, with AOSP kernel. Yesterday, out of the blue, the phone started to get terribly slow and not responsive at all. After a few minutes, it restarted, only to do the same. A couple of minutes maybe, booting up, then get slow and reboot - it did this constantly, and it still does.
I have tried to go into clockworkmod recovery - wiped cache, wiped dalvik cache, wipe user data (factory reset). The phone booted up again, but my apps, etc. were still there! Nothing had happened. I did it a couple of times, but nothing at all.
Then, I have found a .zip file that was still on my memory, with the latest snapshot I had installed. I tried installing it with the install from sd card option, but when it loaded up again, I was still seeing the same apps, background etc.! Nothing had happened and no error message.
Decided to leave the "custom" days behind, I downloaded the stock image for my Gnex. However, since it is a yakjuxw build, I had to flash the yakju option - so not the ideal "stock" package. Using the google installer, I was unable to proceed, since the bootloader number was different than the one that the installer expected, so it exited.
I have found online the amazing Nexus Root Toolkit from WugFresh. I tried to flash it from there, enabling the "force flash" option.
It started out ok.. But when it went to the "system" portion, it took 25 minutes (!) to complete and then in the "user data" portion, it said "write failure".
Still, rebooted and I was still seeing my apps etc. What on earth is happening?
Honestly, I would expect that it would be bricked by now, with all these rom flashes and factory resets. I even tried flashing the stable CM version for it, but still nothing had changed.
Any help would be greeeeatly appreciated.
Click to expand...
Click to collapse
Google's secret weapon to make us buy the new Nexus 6.
I don't know why that happens though - dual core processor, with this amount of RAM. Tech-specs-wise, GNex has nothing to be jealous about than mid-range smartphones right now.. Unless, the CPU architecture from 2012 is so bad that it can't run properly today's apps.
Hey guys, I have these problems too. Just bought the Galaxy Nexus from a friend for €15 (cracked screen) and from the moment I turn it on, (sometimes at Nexus logo, sometimes on lockscreen.. ) it reebot itself. Again and again.
Unlocked the bootloader by toolkit or manually by fastboot but after the reboot it's locked again, as you said. I've tried Odin too with same results. The strange thing it's that it took time to do things but after the reboot, it's like I haven't done anything. I mean, even if I delete an app, or wipe data from recovery (not custom), when it turns on, it's always the same.
It's like a challenge to me. Anyone can help? I can't just give up >.<
Inviato dal mio Nexus 4
What the hell, just finished answering another thread with same issue (forum.xda-developers.com/galaxy-nexus/help/wipe-flash-restarting-help-t2908788). Happened to me last week, very same, never touched the phone, always stock.
What the hell is going on here???
Is there any way to get any log files to determine what the hell is going on?
Mine opens up for a few minutes, maybe 3-4 and it seems to be working well.. It gradually gets unresponsive and ultimately restarts.. So, if there is anything to do during these 3-4 minutes, I would be glad to know..
If you have backed up your sdcard data to your computer, and are prepared to start from scratch (i.e. flashing bootloader and recovery via fastboot, etc.), you can do a full erasure with "fastboot -w" in fastboot mode. This has worked for me in the past to fix data corruption, of which it sounds like you may be a victim. See if that works, but make sure you've backed up your sdcard backups and other data you want to keep first!!!!!!!!
7175 said:
If you have backed up your sdcard data to your computer, and are prepared to start from scratch (i.e. flashing bootloader and recovery via fastboot, etc.), you can do a full erasure with "fastboot -w" in fastboot mode. This has worked for me in the past to fix data corruption, of which it sounds like you may be a victim. See if that works, but make sure you've backed up your sdcard backups and other data you want to keep first!!!!!!!!
Click to expand...
Click to collapse
Already tried, uneffective. Everything, no matter how low level (e.g. Odin) has no effect, like the memory is write-protected. I've read elsewhere this means the eMMC is fried, but if you go backwards in this forum you see many ppl had the very same problem in the past few days/weeks. Very strange indeed.
I'm having exactly the same issue, was running CM11 mod too. Could it be a cyanogen fail?
Atreb92 said:
I'm having exactly the same issue, was running CM11 mod too. Could it be a cyanogen fail?
Click to expand...
Click to collapse
No. I've always been on stock.
fabrice79 said:
No. I've always been on stock.
Click to expand...
Click to collapse
But could it really be a hardware fail? It's pretty strange tho that multiple device have the same hardware issue in such a short time difference
Atreb92 said:
But could it really be a hardware fail? It's pretty strange tho that multiple device have the same hardware issue in such a short time difference
Click to expand...
Click to collapse
That's what I say, but just go backwards and have a look at older post. I subscribed to ~10 posts until 15 Oct then I got tired of browsing backwards...
I'm allready looking at older posts thats why i'm saying it's pretty strange that there is a massive hardware fail for this many devices. If it's a software fail there must be a solution somehow.
Same problem by 31th December...
Yeah, i have the same problem since august 2014. This thread confirmes for me, that my Gnex is really dead. It is sad, it served my very well and i wanted to use it as secondary phone and as mobile hotspot.
Same for me at the beginning of december
This problem I've faced one time and that meant that EMMC is fried, as fellow members said earlier.
If you overwrite the storage and reboot then everything's the same means that you can't write (somehow) thus emmc is dead. Write failure also means that EMMC is dead.
It's really sad, but that's it
Hello all.
I've read just about every thread on here about these N7 hard bricks to no avail. My 2013 N7 (Wi-Fi) died one day and I hadn't been using it as much so I didn't notice immediately. I went back to use it to find it hard bricked. I think.
I've used Nexus Root Toolkit to flash multiple different builds of 6.0, 5.0 and 4.3, none of which brought the device back. I've locked and unlocked the bootloader thinking the data wipe might help but it didn't. It is weird, because it simply will not boot up. I have no problem getting into bootloader mode, I have the correct factory images downloaded for flo, nothing works.
After each flash, it just sits on the Google splash screen until I turn it off again.
Any suggestions as to what to do here? I don't know what else to do really.
Thanks,
Sam
droidian1441 said:
Hello all.
I've read just about every thread on here about these N7 hard bricks to no avail. My 2013 N7 (Wi-Fi) died one day and I hadn't been using it as much so I didn't notice immediately. I went back to use it to find it hard bricked. I think.
I've used Nexus Root Toolkit to flash multiple different builds of 6.0, 5.0 and 4.3, none of which brought the device back. I've locked and unlocked the bootloader thinking the data wipe might help but it didn't. It is weird, because it simply will not boot up. I have no problem getting into bootloader mode, I have the correct factory images downloaded for flo, nothing works.
After each flash, it just sits on the Google splash screen until I turn it off again.
Any suggestions as to what to do here? I don't know what else to do really.
Thanks,
Sam
Click to expand...
Click to collapse
Sounds like you prefer only stock roms. Do you insist on it? If you do, my suggestion won't be of help. Otherwise, it looks like your hardware still works. This happened to me once, and what I did was install TWRP recovery and wiped everything, then formatted the storage twice (which, depending on the extent of content, might take up to an hour or more each pass). Seemed the old rom left residues in there that prevented the tab from booting up. Then I flashed a custom rom closest to stock and made sure it booted. If you follow this route up to this point, then you can flash a stock rom anew. Good luck.
graphdarnell said:
Sounds like you prefer only stock roms. Do you insist on it? If you do, my suggestion won't be of help. Otherwise, it looks like your hardware still works. This happened to me once, and what I did was install TWRP recovery and wiped everything, then formatted the storage twice (which, depending on the extent of content, might take up to an hour or more each pass). Seemed the old rom left residues in there that prevented the tab from booting up. Then I flashed a custom rom closest to stock and made sure it booted. If you follow this route up to this point, then you can flash a stock rom anew. Good luck.
Click to expand...
Click to collapse
On this tablet I tend to prefer stock roms however I'm not against custom roms. I will give your suggestion a try. Thanks a lot.
Sent from my VS985 4G using Tapatalk
graphdarnell said:
Sounds like you prefer only stock roms. Do you insist on it? If you do, my suggestion won't be of help. Otherwise, it looks like your hardware still works. This happened to me once, and what I did was install TWRP recovery and wiped everything, then formatted the storage twice (which, depending on the extent of content, might take up to an hour or more each pass). Seemed the old rom left residues in there that prevented the tab from booting up. Then I flashed a custom rom closest to stock and made sure it booted. If you follow this route up to this point, then you can flash a stock rom anew. Good luck.
Click to expand...
Click to collapse
Okay. I flashed TWRP recovery however my touchscreen is not working. So I am now back in the corner.
Do you happen to have any other suggestions?
EDIT: Now the screen is working.
It worked! Thanks a lot. I appreciate it.
Sent from my VS985 4G using Tapatalk
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
Ok, So Here's The Deal.. The Thing.. The WTF
So I had an older version of the Scorpion ROM installed and working fine for a while and wanted to change it up. I downloaded the newest TWRP. Both image and installer.zip, newest Magisk and RR 7.
I flashed the latest stock and you know, followed all the proper steps and after I flashed RR 7, it wouldn't boot up. (Not the issue) as others have had the same issue with RR 7. I left a post about that on the RR 7 thread and went about reflashing stock and proceeded to find a different ROM to check out.
No matter what I try to flash: Lineage, Scorpion, RR 7, dotOS the same thing happens... Everything flashes like it should, but then it won't boot, AND THEN every time I boot back to TWRP to try something else the haptic feedback vibration thing on the pixel 3 xl goes banana sandwich crazy and won't shut off until I reboot to fastboot to flashall to start over. LOL
And not only that but when I jump back to TWRP to try to flash something else stored on the phone, it says the storage is empty and there are nothing available in the menu. And I couldn't get a screenshot but there were some errors that have popped up in twrp as well...
Could This Be An Issue WITH TWRP itself? Because it does it with every single ROM I have flashed today. It's very strange. I have never ran into any issues like this when flashing ROMs, Kernals, etc.
I'm lost. Any help would be awesomely appreciated.
UPDATE: It now vibrates constantly in TWRP and when I reflashed to factory it did the corrupt software screen so I gave it a good ole' factory rest and then it was is stuck in a loop at the G while conecting and disconnecting to the USB over and over and over... now back to corrupt software screen.
I guess I'm just going to have to reflash Stock and just leave it.
Update 2: Still Give The Corrupt Software Thing After Performing FlashAll - soooooooooooooooo
Slo-mo Designs said:
Ok, So Here's The Deal.. The Thing.. The WTF
Could This Be An Issue WITH TWRP itself? Because it does it with every single ROM I have flashed today. It's very strange. I have never ran into any issues like this when flashing ROMs, Kernals, etc. I'm lost. Any help would be awesomely appreciated.
UPDATE: It now vibrates constantly in TWRP and when I reflashed to factory it did the corrupt software screen so I gave it a good ole' factory rest and then it was is stuck in a loop at the G while conecting and disconnecting to the USB over and over and over... now back to corrupt software screen.
I guess I'm just going to have to reflash Stock and just leave it.
Update 2: Still Give The Corrupt Software Thing After Performing FlashAll - soooooooooooooooo
Click to expand...
Click to collapse
Couple of things. Yes there was an issue with v3.2.3-4 TWRP and the vibrator, but that is separate from your boot issues. Go to the dedicated TWRP thread. As for your updates, 1) an FDR just deletes your data and so would not solve your issue. and 2) Guessing you removed the -w switch from the flash-all script or you would not be getting the corrupt software screen. Run the script again with the wipe switch in place, allowing it to wipe your partitions and start over. You've already deleted all your data with the FDR so it won't matter. Best of luck!
Always late to the party.
v12xke said:
Couple of things. Yes there was an issue with v3.2.3-4 TWRP and the vibrator, but that is separate from your boot issues. Go to the dedicated TWRP thread. As for your updates, 1) an FDR just deletes your data and so would not solve your issue. and 2) Guessing you removed the -w switch from the flash-all script or you would not be getting the corrupt software screen. Run the script again with the wipe switch in place, allowing it to wipe your partitions and start over. You've already deleted all your data with the FDR so it won't matter. Best of luck!
Click to expand...
Click to collapse
So yeah... I just now logged back on and saw your response [I have had notification issues on everything from Reddit to FB since I have had the 3XL]
About the response, I have had the issue with it showing the corrupt software screen a bunch when flashing new stuff. The reason I perform the Factory Slap is because it allows me to enter the menu where I have the option to "Boot from ADB" or whatever it says, sideloading seems to be the only way I can make progress when it starts giving the corrupt error.. The reason I didn't perform the full wipe but I can't remember exactly why now since that was over a month ago.
But I finally got it fixed, and I was going to repost because I had found a way to prevent the vibration thing from happening in TWRP but by the time I got around to posting, the new update had fixed it. Lol