My wife is making me return my phone to Walmart so I can purchase it again but take advantage of the $100 gift card deal. If I do a NANDroid backup before returning the phone to the stock ROM will the backup work on the new phone when I get it back on the Jelly Bean ROM I'm using?
Yeah.
Sent from my SGH-I747 using xda premium
Yes +1
Here's a wee entertaining story...I hope.
Wife and I have HD2. Well, mine was resting away since I have my S3 now.
Wife drops phone and destroys screen. Unreadable...just some chicken scratch light and lines, nothing remotely legible.
Her Xday is the next day. So I brainstormed for 30min and then...voila!!!
I Turned both our HD2's on, and booted into CWM with hardware buttons. Very simple.
Then I performed a backup of my HD2 in CWM via the hardware buttons..WHILST copying/mimicking every move BLIND onto the broken HD2.
Then I removed the External SDcard from the broken HD2 and the Sim as well...and placed both into my old HD2....booted into CWM, performed a RESTORE of the newly created image....booted up and BAMM!!!!
My wife has a new HD2 CLONED 100% with everything in place the way she left off the day before. Not a pixel out of place. Took 20min!!!
Lets see an iCrap phone do that!!!
(not to mention, the HD2 is originally a WinMo phone)
My guess would be you won't even have to return it. If you're within your return period, if they have any sense, they should just process a return and resale in the register while you stand there and hold your phone.
It would make absolutely no sense to actually take your phone back and give you a brand new one. Ergo, I'd definitely call or talk to them before you go through all the trouble of resetting.
There's a THANKS button around here somewhere!
Hi I have a confusing situation. I was customizing my newly re-installed FK23 ROM for a couple hours, and while my phone was loading a widget on my homescreen, it froze. So i pulled the battery like I do when I am having issues and i rebooted it. It booted to the sprint splash screen, chime and all, but right after the animation, it reset and boot again, and now everytime I try it is stuck on the boot logo. I have suspected my battery to be going bad for weeks now, but the last time I checked it out, it wasn't swollen or warped. But today I noticed that it was bulging just from feeling it with my hands, not severely, but noticeable to the touch, not to the eye, and it can also spin for a second or two. I am confused to whether this is some sort of major software snafu resulting in a soft-brick or just the fact that my battery is bad. My theory is that the phone wouldn't even start to turn on if the battery was completely shot, so I suspect it may indeed be a soft-brick, but if the phone can still function marginally with a shot battery, that makes it very complicated. I checked and I can still boot to recovery (unfortunately I'm on stock recovery so I can't try reflashing the ROM), and I can also boot to download mode. I know that I can flash a stock tar with PC Odin and be up and running, theoretically, but if my battery is truly shot, isnt it VERY likely that it would fail in the middle of the flash which could result in a hard brick? The reason I am so concerned is because I don't have TEP on my plan, so for me its between spending $10 on Amazon and buying a new battery, or spending $100 for a repair/replacement for sprint. So my question is, if the battery truly is the culprit as opposed to a software/firmware soft brick, would the phone be able to boot into recovery/download mode?
Also, I had deleted some bloatware apks from the preload folder (Mattix's ROM) using Root Explorer earlier but I hadn't yet rebooted the phone. I deleted Sprint ID, TV, nascar, nova hd, telenav and music plus.
reflash your rom
i am having the same problem. though battery was going bad and replaced it and now i can only get to the samsug boot screen an then it restarts, i can still get ihnto odin and rcovery but thats about it... any suggestions would greatly help
bcparker said:
Hi I have a confusing situation. I was customizing my newly re-installed FK23 ROM for a couple hours, and while my phone was loading a widget on my homescreen, it froze. So i pulled the battery like I do when I am having issues and i rebooted it. It booted to the sprint splash screen, chime and all, but right after the animation, it reset and boot again, and now everytime I try it is stuck on the boot logo. I have suspected my battery to be going bad for weeks now, but the last time I checked it out, it wasn't swollen or warped. But today I noticed that it was bulging just from feeling it with my hands, not severely, but noticeable to the touch, not to the eye, and it can also spin for a second or two. I am confused to whether this is some sort of major software snafu resulting in a soft-brick or just the fact that my battery is bad. My theory is that the phone wouldn't even start to turn on if the battery was completely shot, so I suspect it may indeed be a soft-brick, but if the phone can still function marginally with a shot battery, that makes it very complicated. I checked and I can still boot to recovery (unfortunately I'm on stock recovery so I can't try reflashing the ROM), and I can also boot to download mode. I know that I can flash a stock tar with PC Odin and be up and running, theoretically, but if my battery is truly shot, isnt it VERY likely that it would fail in the middle of the flash which could result in a hard brick? The reason I am so concerned is because I don't have TEP on my plan, so for me its between spending $10 on Amazon and buying a new battery, or spending $100 for a repair/replacement for sprint. So my question is, if the battery truly is the culprit as opposed to a software/firmware soft brick, would the phone be able to boot into recovery/download mode?
Also, I had deleted some bloatware apks from the preload folder (Mattix's ROM) using Root Explorer earlier but I hadn't yet rebooted the phone. I deleted Sprint ID, TV, nascar, nova hd, telenav and music plus.
Click to expand...
Click to collapse
If your still within a year with your phone you can go to Sprint and get a new battery.
Or just Odin to EL29 or EL26 and reflash same rom or a back up you did.
I don't think it's the battery. It might be one of those one off things. Deleted something, did you do a clean install.
I was having problems with FK23 the first time booting after a fresh install. It took me 3 to 4 battery pulls to get it to boot. Cuz it boot looped or froze after the 4g screen.
Sent from my SPH-D710 using xda app-developers app
I had a verified md5 download. New battery clean flash. Got it working no problem. I rebooted after pulling battery to put in another new battery that was charging externally. Won't go passed Samsung galaxy s2. jb seems to be an easy OS to Piss off. I hadn't even removed any apps. Just used Autostarts to stop some programs. Didn't stop systemui or anything. Just Tapatalk and a few other user app. And email. Just when you are changing something be near PC Odin. Just in case.
sent from MY BAD A$$ ET4G
patrao_n said:
I had a verified near download. New battery clean flash. Got it working no problem. I rebooted after pulling battery to put in another new battery that was charging externally. Won't go passed Samsung galaxy s2. jb seems to be an easy OS to Piss off. I hadn't even removed any apps. Just used Allstate to stop some programs. Didn't stop systemui or anything. Just Tamarack and a few other user app. And email. Just when you are changing something be near PC Odin. Just in case.
sent from MY BAD A$$ ET4G
Click to expand...
Click to collapse
Wow, I feel stupid. I crossed my fingers and used Odin to flash a tar and everything is working again, so it seems it wasn't the battery causing the boot stick at all. So I guess the problem was the ROM, I will be getting a new battery within the next month in order to nip that in the bud and save myself from potential grief in the future. Thanks to everyone for the input, and be careful flashing out there!
Just went thru that exact same thing. I thought it may be the battery too. My battery was bad, so I got a brand new one & it didn't solve the issue. So I had to reset my phone. Sucked cuz I lost so much important stuff... )0:
Sent from my SPH-D710 using xda app-developers app
Hello Note 4 XDA family. My girlfriend has a note 4 completely stock. I don't use the device regularly as I have n6. She's experiencing some problems when the phone goes to sleep it never wakes back up. You have to do a battery pull in order to get it to boot back up. She is at work and dealing with it. But every time it boots back up its insanely laggy like 7-12 seconds frozen, with no force closes. Then once it comes back it works fine until she turns the screen off again. Then enormous lag and no power back on until another battery pull. I'm guessing its a problem with the device, I haven't seen anyone else with the same issues. Wondering if anyone has some input, I am going to do a hard reset tonight. Backup everything and (I don't know if Odin is still a thing but I'll figure it out) reflash the phone to factory and see if that helps. If not sprint should replace it I would imagine.
When it starts to lag. Does the device ever get really warm or instantly hot? It might be an application running in a background that's hogging insane amounts of CPU.
skuddy said:
Hello Note 4 XDA family. My girlfriend has a note 4 completely stock. I don't use the device regularly as I have n6. She's experiencing some problems when the phone goes to sleep it never wakes back up. You have to do a battery pull in order to get it to boot back up. She is at work and dealing with it. But every time it boots back up its insanely laggy like 7-12 seconds frozen, with no force closes. Then once it comes back it works fine until she turns the screen off again. Then enormous lag and no power back on until another battery pull. I'm guessing its a problem with the device, I haven't seen anyone else with the same issues. Wondering if anyone has some input, I am going to do a hard reset tonight. Backup everything and (I don't know if Odin is still a thing but I'll figure it out) reflash the phone to factory and see if that helps. If not sprint should replace it I would imagine.
Click to expand...
Click to collapse
It's a software related problem i had the similar problem in the 1st weeks i got my phone it used to freeze for a second once every 10 second
I did soft and hard reset and the problem was still there.
But the new firmware came out which is the current one, i decided to do another hard reset to take the update and since then my phone is back alive no lag.
If the hard reset doesn't fix it for you wait for lollipop and do s hard reset before taking the update
Sent from my SM-N910P using JellyBombed Tapatalk 2
We took it to the sprint store. She had an old class 2 SD card it it from my original galaxy s or HTC desire (don't remember which). The rep there said to take out the SD card and it will fix the problem. So she took it out. And no issues since. That seems like a really really weird bug to me. But he said its common in the note 4 with the slower class cards....? Whatever. No issues since.
So the company I work for requires that you fully encrypt your mobile device if you want to check your company email account via Outlook. I charged my phone up to 92%, began the encryption process, kept the phone plugged into a 2.0 charger and 5 hours later its still stuck on the Verizon boot image. I have about 18gb of music on the internal storage, a literal **** ton of pictures (also on the internal), and another literal **** ton of apps. I have a 128gb micro SD card in there as well but never got around to moving much over to it.
So here's my question: is my rooted G4 bricked or could the process be taking so long because of how much literal **** I have stored throughout the phone?
I'd greatly appreciate any advice, my occupation revolves around our phones so I'm literally F'ed in the Aye if I'm without my phone in the field tomorrow.
Well scratch my plea for help off of your evening To-Do lists. As the 6th hour post-encryption drew near I said screw it and pulled the battery and was eventually greeted with my lock screen and the encryption password so all is well.
Installed CyanogenMOD and it still resets, locks up and has other performance related issues.
I did an OTA update to Marshmallow originally. This corrupted my SD card and then caused about 10 resets a day, ranging from when I was using it lightly to heavily or even when it was sleeping/screen off. If I woke it up it would reset or I could feel it reset when it was in my pocket.
First thing I did was a factory reset. I tried other tricks such as swapping out the battery, SD card (or none at all), clearing cache, etc.... Nothing worked. So I tried installing CyanogenMOD, and I failed. But I got the phone back to BPA1. I updated back to marshmallow via my computer and the Verizon software updater.
About a day later the resets and lockups came back. I kept it light of apps but did slowly begin to reinstall some of my usuals (from the play store).
I had some more time so I tried installing Cyan again and was successful. It took a long time to load and optimize but it worked. I used gapps mini and the only step I did not follow in the guide was I did not install xposed.
It's been running for about 12 hours and has hanged, locked up and rebooted on me multiple times. Chrome even locks up (it will stop resounding, I'll get the message asking if I want to wait or close at the same time it starts responding again.)
When it reboots, it still takes forever and even optimizes apps (that I assume have already been optimized). I've seen two boot screens for it, one the little alien guy and the other with gears turning. It did the gears the second time I booted and then I haven't seen them again.
I'm not sure what my next step should be. Maybe I'll try reflashing Cyanogen. I have a feeling it's a hardware issue at this point, but I'm open to ideas. Are there any good diagnostic tools that could help my situation?
The phone is out of warranty and I'm sure that now that I've installed Cyanogen, the warranty was voided anyway. It's a shame because this phone was perfect up until the marshmallow update. I probably had 5 lockup/boots in the year or two I've had it.
Why are you using cyanogenmod in the first place. The support for that has ended. Go to the lineage os nougat thread and use that instead.
HORIZONx720 said:
Why are you using cyanogenmod in the first place. The support for that has ended. Go to the lineage os nougat thread and use that instead.
Click to expand...
Click to collapse
Admittedly, I did not even know about lineage until my phone was wiped with no OS. I did a quick Google search for it but could not find a Verizon note 4 mod. Now that I am not pressured to find a fix, I'll research it a bit more. Thank you.
I tried EmotionOS and NSeven, but both share the same error.
Emotion FCs random processes sporadically and then when my cell/data switches to Searching, it crashes multiple processes until the UI (trebuchet is default for Emotion?) and/or settings FCs and I have to restart. I am also stuck on 3G on that platform. I'm guessing network connectivity / switching is the root of the problems.
Nseven installed and right at the Welcome Screen where I pick my language, Google Play Services started crashing. I only had the option to click OK and then every 5 seconds after that, it kept crashing. I set up the phone, restarted and Google Play Services started crashing again. I am in the process of restoring back to Emotion, as it is the most stable platform so far.
I tried a new SIM card, hoping this was the problem but to no avail.
Does anyone have any other suggestions? I'm guessing its hardware at this point, but since it happened on an OTA Update and I can reproduce the same errors every time, I'm hoping there's still an option left for a fix.
Holy crap. As I was typing this and restoring Emotion, it fully installed and booted. I have 4G! I don't know if that will fix the FC issues, but I have regained a little hope!
I'm still getting FCs and restarts. The more I use it the more it happens, but at least with EmotionOS, It's more limited. Only about 3 or 4 a day compared to 10-20.
I'll try one more flash and I guess tough it out until my contract is up in April.
I can't help you with EmotionOS (haven't tried it yet), but if you want to stop the Google Play Services crashing in NSeven you can make your way to Settings - Applications, then select Google Play Services - Permissions and give it all permissions. It's a bit of a chore to get there when the warning pops up every five seconds, but it will stop once you do that.
So my plan is up and I'm probably switching away from Samsung after this incident. Looking into the pixel or XL. If the v20 is out for Verizon, I might get that but I'll see what looks good when I go to the store today or tomorrow.
I think I've narrowed down my issue to a heat issue. I fixed the 4g and Google play crashes but my phone still locks up or apps start a cascade of crashes. If I power down, I can't restart the phone. If I restart, it powers down but does not turn back on. I remove the battery for 10+ seconds, put it back in for 10+ seconds and it won't turn back on. I'll leave the battery out for minutes to an hour and its a crap shoot.
I can only boot normally or to download mode. TWRP no longer loads. I tried reflashing it and I get a no pit fail. I'd probably look into fixing this but at this point it's not worth it.
What I discovered works is putting the battery and phone on a cool surface, putting the battery back in and placing that on a cool surface and then try to boot up. However, neither my phone nor the battery feel warm to the touch. So that indicates to me something is either off in the sensors, preventing it from turning on or more likely it's a power issue or at least a hardware issue, preventing a constant current or something along those lines. Dips in power could explain apps crashing and the system inexplicably turning off. It would also explain why I can't turn it on easily.
It's really a shame because I liked this phone so much and if the new note was out, I might give it the benefit of the doubt. But last night my Samsung tablet decided to install the updates I've been putting off because they're the same ones that broke this phone. So timing wise, I'm done with Samsung and will try a new brand. Only issue I see with pixel is it doesn't have a removable battery so hopefully I don't run into this issue on that device!
Thanks for all the help xda. If it was a solvable problem, I'm sure I could have fixed it with your help.
Final entry.
I got the v20, and spent a day trying to get my note back to factory. I thought I was doing something wrong, but eventually flashed a kernel, recovery, bootloader and then full Rom (I think it was BPA1 but it could have been CPF3, I don't have it in front of me). I was getting error after error, no PIT partition, mmc check fail, use the Samsung Recovery Assistant, and a few others (again, it's not in front of me so I may have gotten it wrong). The big one was a write disk failure when I was trying to flash the full Rom. I fixed that by flashing kernel, bootloader, recovery, then sticking the battery and the phone on the freezer for ~5 minutes before trying to flash the full Rom.
I updated via USB after that using recovery assistant. Probably completely unnecessary, they just needed to get to the factory reset screen, but when I bought my phone, I couldn't trade in the note because i couldn't turn it on. They gave me $86 for it. Anything less and i would have considered just taking a hammer and microwave to it. Good riddance!
Still a little sad, I loved this phone right up until marshmallow dishonored and killed her.
trickyvinny said:
Final entry.
I got the v20, and spent a day trying to get my note back to factory. I thought I was doing something wrong, but eventually flashed a kernel, recovery, bootloader and then full Rom (I think it was BPA1 but it could have been CPF3, I don't have it in front of me). I was getting error after error, no PIT partition, mmc check fail, use the Samsung Recovery Assistant, and a few others (again, it's not in front of me so I may have gotten it wrong). The big one was a write disk failure when I was trying to flash the full Rom. I fixed that by flashing kernel, bootloader, recovery, then sticking the battery and the phone on the freezer for ~5 minutes before trying to flash the full Rom.
I updated via USB after that using recovery assistant. Probably completely unnecessary, they just needed to get to the factory reset screen, but when I bought my phone, I couldn't trade in the note because i couldn't turn it on. They gave me $86 for it. Anything less and i would have considered just taking a hammer and microwave to it. Good riddance!
Still a little sad, I loved this phone right up until marshmallow dishonored and killed her.
Click to expand...
Click to collapse
I know a lot of people are blaming software, but I'm fairly certain that the problems in many cases are caused by failing hardware. I went through many of the same trials and tribulations with my Note 4 (except I never rooted the phone). I finally contacted Samsung Customer Support and sent the phone in for repair. They replaced a lot of the hardware including the motherboard and returned the phone in "like new" condition. I've been using it for a few weeks now and the performance is flawless.
I was planning to get either the V20 or the G6 if I wasn't able to get the phone fixed. How do you like the V20?
I'd agree that it's most likely hardware and having to put everything in the freezer for it to when confirms it for me although I have no real expertise to say so. But I'd argue that the update created the hardware issue, it was night and day with the update. It was working 100% and then directly after the update to marshmallow, it started having catastrophic issues. Oh well, it's nice not having to pull the battery every hour or so.
V20 is pretty nice. Having used EmotionOS for a few months the switch to the Nougat was pretty smooth. The xda forums for it are a little more limited but I didn't start messing with my phone until it broke and I'm hesitant to try with a new phone given my limited knowhow.
To be honest it's not a big difference in day to day usage from the note 4. Which I like!
+ I never used the finger print scanner but really like it on the v20. I didn't bother with a screen lock before but now I'm protected and have a just as quick access.
-the grip is too slick, I feel like I will drop it. The note had that rougher back which I liked better. A case or a replacement cover should fix that though.
+ I like this top menu screen, I have quick access to a few select apps or can turn the flashlight on or whatever. I'd like it more customizable, I find I switch screens too much when trying to just pull my top menu down. If I could put everything on one tab and combine their special buttons (ie the flashlight button) with apps, it would be perfect.
-the back button and menu button are switched. I can probably customize that but I don't yet know how and by the time I figure it out, I will have relearned that habit. It actually is probably a better placement for how I hold the phone but I'm a big fan of choices.
+ upgraded camera, sound, storage. I don't notice the screen size difference, but it is a lighter phone.
-bloatware
All in all its a good shift from the note 4. I'm happy to be off of Samsung and still have the same basic user experience.
trickyvinny said:
So my plan is up and I'm probably switching away from Samsung after this incident. Looking into the pixel or XL. If the v20 is out for Verizon, I might get that but I'll see what looks good when I go to the store today or tomorrow.
I think I've narrowed down my issue to a heat issue. I fixed the 4g and Google play crashes but my phone still locks up or apps start a cascade of crashes. If I power down, I can't restart the phone. If I restart, it powers down but does not turn back on. I remove the battery for 10+ seconds, put it back in for 10+ seconds and it won't turn back on. I'll leave the battery out for minutes to an hour and its a crap shoot.
I can only boot normally or to download mode. TWRP no longer loads. I tried reflashing it and I get a no pit fail. I'd probably look into fixing this but at this point it's not worth it.
What I discovered works is putting the battery and phone on a cool surface, putting the battery back in and placing that on a cool surface and then try to boot up. However, neither my phone nor the battery feel warm to the touch. So that indicates to me something is either off in the sensors, preventing it from turning on or more likely it's a power issue or at least a hardware issue, preventing a constant current or something along those lines. Dips in power could explain apps crashing and the system inexplicably turning off. It would also explain why I can't turn it on easily.
It's really a shame because I liked this phone so much and if the new note was out, I might give it the benefit of the doubt. But last night my Samsung tablet decided to install the updates I've been putting off because they're the same ones that broke this phone. So timing wise, I'm done with Samsung and will try a new brand. Only issue I see with pixel is it doesn't have a removable battery so hopefully I don't run into this issue on that device!
Thanks for all the help xda. If it was a solvable problem, I'm sure I could have fixed it with your help.
Click to expand...
Click to collapse
I have had the exact same problem with my note 4. It wouldn't last 30 seconds at a lock screen from a cold battery before it would start boot looping, and the longer you left it in, the worse it got. Google told me I needed a new battery from several other forums and places I read. So I ordered one and replaced with a genuine Samsung one direct from them, and it didn't change anything.
I figured out it was heat related and I had it sit on an ice pack and it would run and work fine as long as the ice pack held out, about 2 hours. I've down graded, flashed, rooted the boot loader, installed a recovery console, flashed to different versions, all have the same problem. So I've kind of reserved myself to the fact it must be a hardware problem. Perhaps it was caused by the update, but nothing software change wise seems to be able to fix it. Did wake-loc fix as well. I've spent the last week with mine trying everything in the world and every evening having it on the ice pack hooked up trying whatever I could think of or read up on doing, and basically as soon as it warms up, it starts doing it again.
Heres a pic; http://imgur.com/a/5L64V
In my experience, it gets worse and worse. The day I bought my v20, I tried to trade it into Verizon but couldn't even turn it on in front of the rep. I thought I had timed the new phone perfectly but still wanted the $80! Fortunately I got it working after the weekend and just stuck everything in the freezer before I walked to Verizon.
trickyvinny said:
In my experience, it gets worse and worse. The day I bought my v20, I tried to trade it into Verizon but couldn't even turn it on in front of the rep. I thought I had timed the new phone perfectly but still wanted the $80! Fortunately I got it working after the weekend and just stuck everything in the freezer before I walked to Verizon.
Click to expand...
Click to collapse
Just out of curiosity, what phone did you wind up going to?
The LG v20 and so far so good!