Ramdom reboots, lag, freeze, and a kernel panic - Sprint Galaxy Note 4 Q&A, Help & Troubleshooting

I've had nothing but issues for the past month. I was running Hybrid X series on OG5 without issue. I then decide to update to OK1 so that I could run Ultimate Note 5 Hybrid from. That's when I experienced lagginess and what not. I even thought I bricked my phone (see this thread) but after getting back the phone I am still experiencing a lot of problems. Below, is what I've experienced.
Problems
-lagginess
-swipe to unlock would lock up then, screen would go black then eventually unlock
-random reboots on stock OK1
-automatically boot into download mode
-couple of failed Odin attempt due to "MMC: mmc_write fail"
-reboot system within TWRP and it wouldn't reboot and the power button wouldn't boot the phone either. Had to pull the battery for a bit to get it to boot
-randomly attempt to wake the phone and receive no response, no lights. Phone would eventually wake
-kernel panic (this happened only once which was last night running stock odexed root ROM by tx_dbs_tx)
Things I've done to attempt to resolve my frustration
-Odin stock OK1
-Odin stock OG5 took OK1 ota update
-mulitple factory resets using stock recovery
-flashed tx_dbs_tx stock OK1 deoxed ROM
Right now, I'm extremely frustrated and have got back to my trusty stock Note II and am sourcing another Note 4. Can someone confirm this is an hardware issue so that I can move on from this particular Note 4 and on to a "new" used one.
Thanks for reading,
Jeremy

gimmezell said:
I've had nothing but issues for the past month. I was running Hybrid X series on OG5 without issue. I then decide to update to OK1 so that I could run Ultimate Note 5 Hybrid from. That's when I experienced lagginess and what not. I even thought I bricked my phone (see this thread) but after getting back the phone I am still experiencing a lot of problems. Below, is what I've experienced.
Problems
-lagginess
-swipe to unlock would lock up then, screen would go black then eventually unlock
-random reboots on stock OK1
-automatically boot into download mode
-couple of failed Odin attempt due to "MMC: mmc_write fail"
-reboot system within TWRP and it wouldn't reboot and the power button wouldn't boot the phone either. Had to pull the battery for a bit to get it to boot
-randomly attempt to wake the phone and receive no response, no lights. Phone would eventually wake
-kernel panic (this happened only once which was last night running stock odexed root ROM by tx_dbs_tx)
Things I've done to attempt to resolve my frustration
-Odin stock OK1
-Odin stock OG5 took OK1 ota update
-mulitple factory resets using stock recovery
-flashed tx_dbs_tx stock OK1 deoxed ROM
Right now, I'm extremely frustrated and have got back to my trusty stock Note II and am sourcing another Note 4. Can someone confirm this is an hardware issue so that I can move on from this particular Note 4 and on to a "new" used one.
Thanks for reading,
Jeremy
Click to expand...
Click to collapse
It's hardware failure. If you have have TEP (Sprint insurance), Sprint will replace it, free.

Thanks for the reply @LMMT. Yeah, I had a feeling. Of my list, what is the main symptom of a hardware failure? Unfortunately, I do not have TEP. I will more than likely be purchasing this used/new Note 4.

gimmezell said:
Thanks for the reply @LMMT. Yeah, I had a feeling. Of my list, what is the main symptom of a hardware failure? Unfortunately, I do not have TEP. I will more than likely be purchasing this used/new Note 4.
Click to expand...
Click to collapse
Pretty much everything you described. I had the same problem, a week and a half ago. There's a thread discussing it, I Q&A.

My phone also just started to do this. All your symptoms is what mine is doing as well.

dannieboiz said:
My phone also just started to do this. All your symptoms is what mine is doing as well.
Click to expand...
Click to collapse
I ended up getting a used Note 4 from swappa.com. It sure is nice to have a working Note 4 again!

Confused how can it be hardware issue if you stated it worked fine at hybrid x

angel85lxnote2 said:
Confused how can it be hardware issue if you stated it worked fine at hybrid x
Click to expand...
Click to collapse
I was getting more and more eMMC write errors as well as no PIT partition while attempting to flash the stock OG5 tar vian Odin.
I can sometimes flash TWRP but now all I get is the flash screen in TWRP, then the phone goes black.
The furthest I got was yesterday, when I was able to flash TWRP and install tx_dbs_tx stock OK1 rooted ROM but when I power down the phone it wouldn't come back on until after removing the battery for an extended period of time.

gimmezell said:
I was getting more and more eMMC write errors as well as no PIT partition while attempting to flash the stock OG5 tar vian Odin.
I can sometimes flash TWRP but now all I get is the flash screen in TWRP, then the phone goes black.
The furthest I got was yesterday, when I was able to flash TWRP and install tx_dbs_tx stock OK1 rooted ROM but when I power down the phone it wouldn't come back on until after removing the battery for an extended period of time.
Click to expand...
Click to collapse
OK mine let's me flash all I want. I finally got this cm remix ROM to work and been having no issues for the last day. I used open gapp pico with it . I had to try a lot of gapps and finally got it working. You should try it.

After letting the phone sit untouched overnight, I was able to successfully flash back to OG5. However, after it got the the yellow Sprint screen it rebooted, went into download mode and gave an error along the lines of "failed" boot. I also got the emmc error.
I want to believe that I can resurrect the phone but the fact I'm getting the emmc error's leads me to believe it's a hardware issue. I've since purchased a used untouched Note 4 and it works as it should. I'm very hesitant to root it because of the what happened to my original Note 4.

I commented on the other section but long story short. I had the same issues as mentioned on the first post. Last night my phone would not turn on at all after trying all methods (soft reboot, recovery, battery pull etc) nothing worked. Phone wouldn't even get a flashing light. I took it to the sprint store today and 2 hours later they tell me there in a crack inside of my glass (digitizer?) which is not even visible unless you take a flashlight and can barely see it. I told them that I have been having these random boot, laginess etc issues and they said that this was the cause. Does that make sense? I really don't feel like paying a $200 deductible to get another phone especially if that is not the cause.

No, it wont make sense!!
In short i too have this issue :- ( i suspect temperature to be the issue

Related

[Q] Random Reboots

I rooted and ran a couple diff custom ROMs: cm10.1.3 and infamous alpha, both with oc kernels (never set mhz past 2051). Began getting random reboots, alot while running the Alpha ROM, and a couple while running cm10.1.3 which I thought was weird because its a RC. should be stable, right? Anyway, got tired of RRs, so I decided to unroot and got stock, till I had some free time.to tinker with it. Well guess what, getting RRs EVEN IN UNROOTED STOCK. Any ideas?
I'm not exactly sure what steps you have taken to get back to Stock, where you're still having random reboots, but I'll let you know what I've done in the past to get to Stock which resolved the issues:
- Factory reset device from device. Save and/or move your Internal files/data prior as you'll be wiping Internal. I'd remove my extSdCard prior to Factory reset and after moving files to it.
- ODIN Samsung Stock Firmware
http://samsung-updates.com/details/9595/Galaxy_S_4_T-Mobile/SGH-M919/TMB/M919UVUAMDL.html
- After the device boots, you'll probably get stuck on the Samsung splash boot screen. After a few minutes - -
- pull the battery, replace the battery but Don't power the device on
- Place device in Stock Recovery mode by pressing Power and Vol up buttons at the same time.
Release the buttons when you see the blue letters appear in the upper left hand corner of the screen.
- Scroll to Factory reset using the volume buttons.
(During the above process, you'll see the Android on its side with a Red X on him/her.)
- press the power button to lock in Factory reset
Let the Recovery scroll through its script
(during this process the Android will come to life )
- After the script is completed which takes less than a minute or so, scroll to reboot and select it with the power button.
- the device will now boot.
Important: while the device is booting, the screen will stay on the T-Mobilessplash screen for what will seem forever. Don't panic. The screen will show T-Mobile across the screen for about 15 or so minutes. Could be a little more or a little less. The device will then continue and complete the booting cycle.
Some notes:
1) during the above process, I have removed my extSdCard card as I didn't want tottake a chanceiit would be wiped. ODIN doesn't wipe extSdCard card but I don'tbneed it during theiprocess so I remove it in case Murphy decides to pay a visit.
2) during ROM flashes, I've experienced almost every issue youccan imagine. This occurred while using TWRP 2.5.0.2, but only when flashing ROMs with Aroma. For months prior, I had zero issues.
The problems I was experiencing were:
Random reboots, splash screen freezes, bootloops, installation of choices in Aroma which only partially installed, issues which didn't seem to havesan answer, and when you found the solution, that solution wouldn't work when the issue appeared again.
- constantly ODINing back to stock
- sometimes in Recovery, I couldn't get past the TWRP lockscreen, and only wiping Internal SD resolved the issue so I could do a Factory reset. I was doing this so often, that I left all files on my extSdCard so Iewouldn't lose my data when I had to wipe internal. It was faster this way as I didn't have to keep moving stuff back & forth.
After endless hours of troubleshooting and aggravation, I changed Recoveries.
I installed Philz Touch Recovery, and I have had Zero issues since installing it about 3 or so weeks ago, which have included multiple ROM flashes with Aroma.
I didn't want to switch Recoveries as I was very used to TWRP, but I just couldn't deal with the new found issues I was having so I made the switch and haven't looked back. Some people don't have issues with TWRP, but I wasn't one of them
Hopefully you can relate to some of my experiences which I have written above, which may help you to resolve some of the issues you're experiencing.
Yes. Thats the file I used and also the steps. I dont know what the deal is.
twatts723 said:
Yes. Thats the file I used and also the steps. I dont know what the deal is.
Click to expand...
Click to collapse
If you:
Wiped Internal SD
ODINd Stock Firmware
which flashed successfully
and are still having random rebooting.....
I can only suggest:
Check your device settings, if you haven't done so already to insure you're running:
Stock ROM
Stock modem/radio
And that all settings are stock.
If everything checks out, I can only suggest to:
Download the Samsung Stock Firmware file again
Check the md5 checksum
ODIN Samsung Stock Firmware again
And see how it goes.
So it turns out, if once you flash the stock firmware through odin, you just have to let it "settle in" for a couple days and all the problems go away. Thanks man.
twatts723 said:
So it turns out, if once you flash the stock firmware through odin, you just have to let it "settle in" for a couple days and all the problems go away. Thanks man.
Click to expand...
Click to collapse
Glad everything worked out for you.
Don't shy away from custom ROMs though, as you'll be missing out on some good stuff
As a note, there can be many thinks which can contribute to issues after the installation of a Custom ROM, Kernels, etc. such as:
Bad downloads, corrupted files, app conflicts, dirty flashes instead of Full wipes, etc., etc.
Another issue can be related to the Recovery you are using.
I had many, many issues regarding flashing ROMs which installed with Aroma.
Prior to ROMs w/Aroma, I had Zero issues.
I suggest using Philz Touch Recovery.
In case you don't have it installed and want to try it, I'll post a link to the download page.
Flash the proper file for your specific carrier.
Install the tar file with ODIN or
Flash the zip file with your Recovery......
Well, I come from sgs2. On that device, I could flash everything through cmw, and just use darkside super wipe and darkside cache wipe. No problem. Every rom from cm to amatuer custom blibbidy blobbidy, no problem. When I rooted my s4, I went straight to twrp because everyone said it was better. I flashed cm10.1.3 rc - rr. Infamous alpha v.7, which was supposed to be stable - rr. I went back to stock, rooted again, and kept stock tw, and only flashed ktoonz kernel, which is supposed to be one of the best for this device. Everything ran great, but guess what - rr. So I gave up. Went back totally stock. Working a lot of hours at work right now. We slow down after thanksgiving, so I'll probably start flashing again around that time. Thanks for thw help though
cheers.

Strange Boot Loop With NO CWM Recovery

I've got a T-Mobile Note 3 that I picked it up on launch day last Thursday at a T-mobile store. I proceeded to root the phone with Odin, then restore via Titanium Backup and then fix the backup with "restorecon -R -v /data". Life has been great until last night. Initially I got a circle with a line through it instead of the mobile signal and my cellular link would not connect, but my wifi was fine. When the problem was sill occurring this morning I figured it was an odd cellular problem and rebooted the phone this morning when it persisted. Now the phone is rebooting a few minutes after it completes booting.
It will boot normally, then I'll unlock the phone and get my window manager (Holo)...then I'll get the error "Process system isn't responding. Do you want to close it?". Then I get the error "Unfortunately, Favorite Apps has stopped." Regardless whether I interact with those error messages the phone then reboots a minute later. I have *not* done a restore from CWM ever and the phone doesn't seem to have suffered any physical damage.
The things I've tried include:
*) power down, remove sdcard, then reboot
*) power down, remove sim card, then reboot
*) power down, remove sim card, remove sdcard, then reboot
*) clear cache, then reboot
*) clear dalvik-cache, then reboot
*) clear dalvik-cache and cache, then reboot
*) clear dalvik-cache, clean cache, then wipe to factory, then reboot
In all the above scenarios nothing has changed. The phone reboots after it completes booting.
In the past, I've rooted and flashed on a G1, a G2, and an S3. I've bricked my S3 that had to be repaired via JTAG. This reboot problem with my Note 3 is completely unlike any of the things I've seen with previous phones.
I've read through some of the other threads about reboot loops, but all the threads I've read were caused by a CWM restore and have no solution yet.
Does anyone know the cause of this and what could fix it?
digitalfiend said:
I've got a T-Mobile Note 3 that I picked it up on launch day last Thursday at a T-mobile store. I proceeded to root the phone with Odin, then restore via Titanium Backup and then fix the backup with "restorecon -R -v /data". Life has been great until last night. Initially I got a circle with a line through it instead of the mobile signal and my cellular link would not connect, but my wifi was fine. When the problem was sill occurring this morning I figured it was an odd cellular problem and rebooted the phone this morning when it persisted. Now the phone is rebooting a few minutes after it completes booting.
It will boot normally, then I'll unlock the phone and get my window manager (Holo)...then I'll get the error "Process system isn't responding. Do you want to close it?". Then I get the error "Unfortunately, Favorite Apps has stopped." Regardless whether I interact with those error messages the phone then reboots a minute later. I have *not* done a restore from CWM ever and the phone doesn't seem to have suffered any physical damage.
The things I've tried include:
*) power down, remove sdcard, then reboot
*) power down, remove sim card, then reboot
*) power down, remove sim card, remove sdcard, then reboot
*) clear cache, then reboot
*) clear dalvik-cache, then reboot
*) clear dalvik-cache and cache, then reboot
*) clear dalvik-cache, clean cache, then wipe to factory, then reboot
In all the above scenarios nothing has changed. The phone reboots after it completes booting.
In the past, I've rooted and flashed on a G1, a G2, and an S3. I've bricked my S3 that had to be repaired via JTAG. This reboot problem with my Note 3 is completely unlike any of the things I've seen with previous phones.
I've read through some of the other threads about reboot loops, but all the threads I've read were caused by a CWM restore and have no solution yet.
Does anyone know the cause of this and what could fix it?
Click to expand...
Click to collapse
I would just Odin to stock and restart. I'm guessing some app your restored form another phone did it.
YellowGTO said:
I would just Odin to stock and restart. I'm guessing some app your restored form another phone did it.
Click to expand...
Click to collapse
I don't believe it was an app that was restored because the restore had run perfectly for 5 full days. I completed the restore last Thursday...that's what makes this so unusual.
Do you know where to get the stock zips to use with Odin?
digitalfiend said:
I don't believe it was an app that was restored because the restore had run perfectly for 5 full days. I completed the restore last Thursday...that's what makes this so unusual.
Do you know where to get the stock zips to use with Odin?
Click to expand...
Click to collapse
There's some stock Odin tar files in the Android development forum. Download and flash using Odin. Once it reboots, remove battery and manually boot into stock recovery and do a factory reset/wipe. Reboot and it should work.
Sent from my SGH-T889
jmerlos said:
There's some stock Odin tar files in the Android development forum. Download and flash using Odin. Once it reboots, remove battery and manually boot into stock recovery and do a factory reset/wipe. Reboot and it should work.
Sent from my SGH-T889
Click to expand...
Click to collapse
It looks as if the stock tar in zip format (N900TUVUBMI7_N900TTMBBMI7_TMB.zip) can be downloaded from either of these links:
http://forum.xda-developers.com/showthread.php?t=2465764 (faster download link)
http://forum.xda-developers.com/showthread.php?t=2468275 (slow download link)
I just finished downloading from the first link and after extracting the zip file I have these files:
N900TUVUBMI7_N900TTMBBMI7_N900TUVUBMI7_HOME.tar.md5
SS_DL.dll
This seems like an obvious thing, but want to ask because of how odd this problem is: Do I simply flash the "N900TUVUBMI7_N900TTMBBMI7_N900TUVUBMI7_HOME.tar.md5" file the same way that I flashed the CWM through Odin?
Yes, but IIRC, just uncheck reboot, reboot manually into recovery, then wipe, factory reset, etc. Pull your battery, reboot. Check the TWRP thread, it has exact directions.
sgh-TWEAKED-889©
Warrior1975 said:
Yes, but IIRC, just uncheck reboot, reboot manually into recovery, then wipe, factory reset, etc. Pull your battery, reboot. Check the TWRP thread, it has exact directions.
sgh-TWEAKED-889©
Click to expand...
Click to collapse
Got it, thank you! Here's what I'm referencing for the Odin options:
http://forum.xda-developers.com/showpost.php?p=46110842&postcount=2
I'll flash this and update the thread.
Good luck bro!!
sgh-TWEAKED-889©
Ok, I flashed with Odin then once it completed I got the "PASS!" status in Odin. I shut down Odin, pulled the battery from the Note 3, then allowed the phone to boot. There was a "booting recovery" message in blue at the top of the screen before the phone booted, then it booted to the "samsung logo", then the animated circular logo, then the white screen with the "T-Mobile 4G LTE" logo, then rebooted. The second boot, it did the same thing but stayed on the "T-Mobile 4G LTE" screen for many minutes...then it seemed as if it was completing it's reboot because I got the notification bar with the time and the circle with the line through it for the cell signal strength. I got the same error when the phone seemed to have completed booting, then a reboot. Now it's back to the same place it started in it's rebooting cycle.
This makes absolutely no sense at all. If I'd have done a CWM restore then I could understand that...but there's no reason for this that I can see. The phone acts as if it was knocked off of the T-Mobile network and now it finishes it's booting cycle long enough to be rebooted.
So now I have a useless Note 3. I'm game for taking the phone back to the T-Mobile store and requesting that they replace the phone, which they probably would, but I have no guarantee that this wouldn't happen again. I'm open to suggestions as long as they don't cause me to brick my phone completely.
I finished installing TWRP and darthrom successfully. However, after the darthrom finishes booting I have the exact same problem with the phone rebooting that the stock ROM had.
I'm back to square one.
I'm open to suggestions.
There are a lot of people having boot loop problems even without root though they are spread out among various sub forums. Try this thread for example:
http://forum.xda-developers.com/show....php?t=2467005[Q] Reboot cycle after restart help
Sent from my SAMSUNG-SGH-I317
Dumbo53 said:
There are a lot of people having boot loop problems even without root though they are spread out among various sub forums. Try this thread for example:
http://forum.xda-developers.com/show....php?t=2467005[Q] Reboot cycle after restart help
Sent from my SAMSUNG-SGH-I317
Click to expand...
Click to collapse
I saw a couple threads last night when I was searching around on the web about other models of phones with SIM socket and SIM card issues. I'm beginning to think that my issue is hardware-related, and not software. I did another wipe last night based on this thread's post: http://forum.xda-developers.com/showpost.php?p=46157872&postcount=6&nocache=1&z=7848000959493220
Instead of simply wiping, I formatted /data/, then wiped, then I flashed on the stock ROM, then flashed on the darth rom. I got slightly different results once the phone was done with it's firstboot - it kept giving me the error that a new SIM card had been installed and the phone needed to be rebooted. This causes me to suspect the physical hardware of my Note 3 or the SIM card. I have ruled out the SIM card because I've been using it in my old G2 since this started, via an adapter for the G2's SIM socket, and it's been fine. I'm planning on taking the phone to T-Mobile today and seeing what they can sort out with either a SIM exchange or phone exchange.
The note 3 misbehaved the same way while in the T-Mobile store. They swapped the phone out under warranty after asking only the basic questions and trying a factory reset. The same SIM card in the new note 3 works fine.
I'm on the same boat. Got my Note 3 this morning, rooted an hour ago with CMW, made backup and flashed Stock ROM from Jovy. Result: bootloop. Restore backup and still on bootloop. DLing the Odin stock .tar to see if it helps. Any more suggestions?
Edit: After flashing with Odin the stock tar from Sammy all it's good...at least for now.
Wally72 said:
I'm on the same boat. Got my Note 3 this morning, rooted an hour ago with CMW, made backup and flashed Stock ROM from Jovy. Result: bootloop. Restore backup and still on bootloop. DLing the Odin stock .tar to see if it helps. Any more suggestions?
Edit: After flashing with Odin the stock tar from Sammy all it's good...at least for now.
Click to expand...
Click to collapse
How far into the booting process would you get before the phone rebooted?
digitalfiend said:
How far into the booting process would you get before the phone rebooted?
Click to expand...
Click to collapse
Never passed Samsung! In my case, flashing the .tar with Odin from Samfirmware fixed my issue. I think imma wait for a more stable recovery.
Sent from my SM-N900T using Tapatalk now Free
Wally72 said:
Never passed Samsung! In my case, flashing the .tar with Odin from Samfirmware fixed my issue.
Click to expand...
Click to collapse
Interesting...it sounds like you had the boot loop that many others have had...it's cool to hear that you got it fixed. I think my problem was hardware-based since the phone completed it's boot process and *then* had issues. Luckily T-Mobile was there for me and helped out.
Wally72 said:
I think imma wait for a more stable recovery.
Click to expand...
Click to collapse
I know what you mean as far as waiting for a stable recovery. If it's any help, I've decided to stay far away from the recovery restore and simply use Titanium backup to do restores. It's more work than a nandroid recovery, but it reliably does it's job well for me.
digitalfiend said:
Interesting...it sounds like you had the boot loop that many others have had...it's cool to hear that you got it fixed. I think my problem was hardware-based since the phone completed it's boot process and *then* had issues. Luckily T-Mobile was there for me and helped out.
I know what you mean as far as waiting for a stable recovery. If it's any help, I've decided to stay far away from the recovery restore and simply use Titanium backup to do restores. It's more work than a nandroid recovery, but it reliably does it's job well for me.
Click to expand...
Click to collapse
Well...I'm doing a lot of reading. I can't stand this "stock look" and me, every time I root a phone, I always do my own modifications within the ROM I choose to flash. SystemUI and apk's. I only change the .png's, therefore, getting the visual look I want/like. Always done it with certain ROMs/Themes. I downloaded Jovy's stock ROM and made the visual changes I wanted. I flashed and got into that bootloop scenario. Restore backup with CWM provided by Zedomax and made it worse. I think the problem is recovery (at least from what I've read). In this case, CWM been less unstable than TWRP. I f you read a bit around, must ppl if not all, had the "dead bootloop" issue with TWRP. I haven't read from anybody yet having the "dead bootloop" with CWM. Ppl with CWM that flashed their backup and got that bootloop, fixed it flashing back to stock, where ppl that had TWRP have tried to flash back to stock and their phones never boot completely
Again...imma wait a little more for good reports as far as recovery goes!
Bigbiff has a file he uploaded, it may be a fix for the bootlooping issue. You'd be the first to try at this point. It's linked below, but the entire thread is in the OG development of tmobile.
http://forum.xda-developers.com/showthread.php?p=46379854
sgh-TWEAKED-889©
I've never seen so many issues with a brand new flagship phone before. Makes me think it wasn't tested fully before release. I mean all these problems!
Even though I returned my N3 after I tried restoring and getting bootloop of death, I feel this model is really flawed. Hearing new things everyday.

What the What?!

Moderators, please forgive me in not in the right place...
Came home from a glorious week of camping and decided to check out some 4.4.4 ROM's on my phone...
Already running older version of C-ROM, so backed up and flashed the KK 4.4.4 version. That's where it the wheels came off my bus..
Phone booted so damn slow, then there were hundred's of FC's, rendering the phone unuseable. Rebooted, cleared Dalvik and Cache but same difference. The phone died, the battery would NOT charge! No matter what! Try as I may...NO GO!!! For hours! Feared it was that issue wherein the S3 motherboard dies and the phone has to be replaced by Samsung. Kept trying...finally get the phone to boot into TWRP. Whew!!! Still the phone kept complaining that the battery was dead. WTF?!
Restored the back up I had made...accidentally grabbed another backup from december of last year (Cyanogenmod), so had to recover my C-ROM back instead...RESTORE FAILS! Tried a few times but still failed. Tried to re-flash the latest C-ROM, but STILL fails...everything I'm trying fails.
I read the output and see an error, "Unable to wipe /system" ...found a thread where a user, using TWRP, had the same error with their ROM they were trying to flash. Eventually, the fix was to delete the make_4fs (or whatever it's called) from /sbin directory. Did so and was able to flash my Cyanogen, but could not restore my C-ROM backup. That STILL fails, however, no error in the live output while it's restoring. Just ends up Failing at the end of the restore process. The live logs indicate that it's using the 2fs (or whatever it's called), which was successful in flashing my Cyanogen ROM...why will it not restore my C-ROM back? :crying:
Any help would be greatly appreciated.
kojam said:
Moderators, please forgive me in not in the right place...
Came home from a glorious week of camping and decided to check out some 4.4.4 ROM's on my phone...
Already running older version of C-ROM, so backed up and flashed the KK 4.4.4 version. That's where it the wheels came off my bus..
Phone booted so damn slow, then there were hundred's of FC's, rendering the phone unuseable. Rebooted, cleared Dalvik and Cache but same difference. The phone died, the battery would NOT charge! No matter what! Try as I may...NO GO!!! For hours! Feared it was that issue wherein the S3 motherboard dies and the phone has to be replaced by Samsung. Kept trying...finally get the phone to boot into TWRP. Whew!!! Still the phone kept complaining that the battery was dead. WTF?!
Restored the back up I had made...accidentally grabbed another backup from december of last year (Cyanogenmod), so had to recover my C-ROM back instead...RESTORE FAILS! Tried a few times but still failed. Tried to re-flash the latest C-ROM, but STILL fails...everything I'm trying fails.
I read the output and see an error, "Unable to wipe /system" ...found a thread where a user, using TWRP, had the same error with their ROM they were trying to flash. Eventually, the fix was to delete the make_4fs (or whatever it's called) from /sbin directory. Did so and was able to flash my Cyanogen, but could not restore my C-ROM backup. That STILL fails, however, no error in the live output while it's restoring. Just ends up Failing at the end of the restore process. The live logs indicate that it's using the 2fs (or whatever it's called), which was successful in flashing my Cyanogen ROM...why will it not restore my C-ROM back? :crying:
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Have you tried using ODIN to restore back to stock? If you can get the phone up and running, you may be able to restore from your old backups.
Bass_Man25 said:
Have you tried using ODIN to restore back to stock? If you can get the phone up and running, you may be able to restore from your old backups.
Click to expand...
Click to collapse
Thanks bud.
Oh, I got the phone up and running on the Cyanogen dated dec/2013.
ODIN? Never thought of it. Been such a long time. I do need to get stock on here so I can all the latest official radios etc, then put custom ROMs.
Been such a loooooong time since used ODIN though. Shouldn't be hard to get back on the horse.
Thanks for the suggestion!!!
any idea why this happened? anyone?
as an fyi, I tried to put the lastest SlimROM on but same difference. (i'm really pressed for time always. so I decided this is the quickest thing to try). seems the only thing that will flash is my Cyanogen from December. Strange...
Will have to give ODIN a try if I can ever get the time some day..
Odin shouldn't be a much longer process. Start flash, walk away. When you return 10 minutes to a few hours later, it'll be sitting there waiting for you, all nice and stock!
Anyway, one thing I dont recall seeing you tried is a factory reset. Chances are, that's what caused all your FC. Roms will always take a while on first boot. But all those FC were likely due to incompatible data. Then you may have encountered more data corruption as the system worked overtime trying to resolve all those conflicts.
Its purely a theory, but there's a good chance you will never be able to find exactly what caused all of your issues. Dont lose sleep over it is my best advice! A couple of tips though....
Never wipe/format system! Had you been able to successfully do so, and then nothing would still flash, there would no longer be an o/s to boot into! All roms will format your system partition as the first step in the flash, so there's just no need to do this manually. Most flash failures occur before the flash actually starts, meaning if there's a problem, most times you'll still be able to reboot normally.
Update your firmware. If its been a while since taking an ota or updating via Odin, you're probably on an older firmware build which is known to cause problems with many more recent roms. Most simply will not flash if not updated.
Also, by flashing your up to date firmware in Odin, you will likely fix any corruption which may have occurred on some of those partitions. Good chance you'll be able to flash whatever you want after an Odin firmware update and factory reset.
Hope that helps! Good luck!
DocHoliday77 said:
Odin shouldn't be a much longer process. Start flash, walk away. When you return 10 minutes to a few hours later, it'll be sitting there waiting for you, all nice and stock!
Anyway, one thing I dont recall seeing you tried is a factory reset. Chances are, that's what caused all your FC. Roms will always take a while on first boot. But all those FC were likely due to incompatible data. Then you may have encountered more data corruption as the system worked overtime trying to resolve all those conflicts.
Its purely a theory, but there's a good chance you will never be able to find exactly what caused all of your issues. Dont lose sleep over it is my best advice! A couple of tips though....
Never wipe/format system! Had you been able to successfully do so, and then nothing would still flash, there would no longer be an o/s to boot into! All roms will format your system partition as the first step in the flash, so there's just no need to do this manually. Most flash failures occur before the flash actually starts, meaning if there's a problem, most times you'll still be able to reboot normally.
Update your firmware. If its been a while since taking an ota or updating via Odin, you're probably on an older firmware build which is known to cause problems with many more recent roms. Most simply will not flash if not updated.
Also, by flashing your up to date firmware in Odin, you will likely fix any corruption which may have occurred on some of those partitions. Good chance you'll be able to flash whatever you want after an Odin firmware update and factory reset.
Hope that helps! Good luck!
Click to expand...
Click to collapse
What's up, Doc? Sorry for that...
I downloaded Odin this morning. I should have gotten the link from XDA. The site i got it from looked official, however, tons of endless pop-ups after I installed it. Freak!!!
Then found the xda links. Not sure which version to get because i didn't see which one handles the S3. The latest version (3.09) should, no?
As well, where do i get the stock ROM from? Forgive me for all these questions. Been extremely busy with work these past few months. No time to play around with my phone everything. I'm forgetting more than I know.
A full wipe was done. In TWRP, system was check (it's always checked) automatically when wiping to flash a new ROM.
Thanks again!
Everything you need is in my sig. Go to the firmware thread and the stock or root66 firmware listed there us what you flash in odin. Version 3.09 is fine btw.
DocHoliday77 said:
Everything you need is in my sig. Go to the firmware thread and the stock or root66 firmware listed there us what you flash in odin. Version 3.09 is fine btw.
Click to expand...
Click to collapse
Thanks!
S.O.S!!!
kojam said:
Thanks!
Click to expand...
Click to collapse
Downloaded the rooted firmware from your link and the ODIN (3.09)...
Flashed the firmware (making sure to get the correct one for WIND)...ODIN did it's thing...got a green pass...the phone rebooted...got the Samsung symbol, little swoosh animation, and the accompanying sound effect that goes with the swoosh-thing...THE PHONE NEVER BOOTED UP AN O/S!
Did it at about 11:30 last night, left it, got up this morn, and phone STILL in same status!
Found out that site where I downloaded the firmware had an issue last night. They posted this morn, apologizing to people about a D.O.D attack that may have caused dropped downloads. I downloaded the firmware again this morn, flashed with ODIN, got a pass....SAME THING!!! Phone
Had to quickly pack up my laptop to bring with me to the office. Will try the official, non-rooted firmware to see if I can get it to go.
Problems' that my team went from 12 to 2 people...my partner's off today...and I got a LOUD MOUTH across from me who WILL NOT leave me alone, no matter what I say or do. LOL.
Any suggestions?
In the words of George Costanza:
"I'm BACK, babyyyyyyy!!!!!"
The official firmware worked!
Phone's back online. Thanks for all your help. Will have to see about rooting later...as well, want to see how the battery operates on stock firmware. I've tried EVERYTHING under the sun to preserve batt life and NOTHING worked!!!
Tried EVERY KERNEL noted to be good on battery life, tried TONS of apps that were supposed to help, turned off as much as I could, etc....
batt still not good. I give up. Every diagnostic app says batt is very good. I dunno...
Earplugs! Lol! I definitely feel for you about your work status! Been there!
About the firmware though, if the download had been corrupted, it would've failed the initial check done by Odin. You are probably ok. Dont worry just yet!
If it is hanging up at the Samsung screen, you probably just need to factory reset. Almost always fixes this. (It happens due to incompatible data left from your previous rom)
This will wipe internal sdcard though, so if you haven't backed up yet, the next thing to fo is flash TWRP via Odin. You can then use its built in file manager to copy whst you need first. Or you can then flash an insecure kernel and use adb if you're familiar with that.
The Doc is in!
if the download had been corrupted, it would've failed the initial check done by Odin
Click to expand...
Click to collapse
That's EXACTLY my thought too. That was really perplexing...
I am up again...
Facotry Reset? How do I do that if stuck at the Samsung splash though?
Now that i know the official firmware works, maybe i'll, try again with the rooted firmware, try to factory reset when stuck, and continue to flash TWRP as you described above. Don't mind factory resetting. I've taken everything I need.
Oh!!!!
I noticed that all the apps I had before flashing the firmware are STILL on my phone. I would have thought that they would have been wiped out completely when lord ODIN was doing her thing.
....and battery life is STILL pretty bad...
Phone's been charging...became fully charged...unplugged it..it was down to 84% after only about 30/mins.
Will see how it goes after doing the factory wipe.
Again, how do i do a factory wipe if stuck at the Samsung swoosh after I re-flash the rooted firmware ?
Maybe your battery is dying. it happens. That would explain a big drop from the start.
To factory reset if you're stuck at boot up, turn the phone off, then boot up into recovery. Hold volume up, home and power. After it vibrates, release power only, continue holding the other two until you see recovery booting up.
If stock recovery is installed, choose factory reset.
In TWRP (probably similar in cwm) go to Wipe and choose factory reset there. In TWRP and CWM, factory resetting does not wipe your internal sdcard. Stock recovery will.
And as for Odin, it doesn't actually touch the user data partition, so all your apps and data are preserved. This is great when just upgrading from one build to the next, but is the reason a factory reset is required if coming from a non touchwiz rom.
---------- Post added at 03:59 PM ---------- Previous post was at 03:53 PM ----------
How old is your battery? The S3 is at the age where people who bought it when it was first released will start to notice the battery is beginning to degrade.
You can also get an app called Better Battery Stats here on xda (paid version in the play store). Its the goto utility for investigating problems with battery drain. Run it for a day after a full charge and then check its logs for persistent wakelocks. The app thread should explain its use better than I can, but if you are having trouble you can always post your bbs log here for one of us to look over. (This isnt my strongest area, but there are a few others around that may also be able to help. )

Note 4 Help!

Like many other sprint users, I experienced serious problems with 5.1.1. This resulted in battery pulls and even a downloading boot. I starting looking into a fix. After flashing about every ROM for sprint N910P on this website, I either result in bootloop or the same problems persist. The problems are as follows:
-Can't boot, so I have to wait ~5 minutes to try again
-Boots straight to downloading, mmc read fail
-Boots fine
-Crashes to black screen around 80-90% battery (back to problem 1)
I cannot figure how to use odin anymore because it fails on nearly every rom I attempt. My reactivation lock is OFF.
I'll try to provide as much detail as I can, but I'm at my wits end with this phone.
Thanks!
If you can Odin OK1 stock tar, there is another root alternative: root stock with Chainfire Auto Root. CFAR has been updated for Android 5.1.1 Note 4
http://forum.xda-developers.com/showpost.php?p=55865442&postcount=3
Custom ROMs will take longer than 5 minutes to boot initially after flash. TWRP has been known to fail to flash or not properly flash after trying repeatedly to flash wrong tar with Odin or flash with reactivation locked. Which, if any, apply to you? I hope it's not hardware failure...
Sent from my SM-N910P using Tapatalk
Chainfire was going to be my next option. I think the first time I attempted using chainfire through odin, it ended in a bootloop. I haven't tried the update version though. I'll give that a shot.
Is there any way to fix this problem with TWRP (delete it and reflash)?
I'm starting to think its a hardware failure, which would suck because knox is tripped and warranty expired a few days ago anyway I believe.
I downloaded the updated CFAR last night to verify it was updated. It's bundled with Odin 3.10.6 Use the defaults with that for stock OK1 tar.
You should know that CFAR is primarily for rooted stock.
If you want a custom ROM, you may have to use Philz CWM touch recovery for Note 4. TWRP just gets inoperative for some time for some users when tars fail in repeated attempts. Philz' seems to flash where TWRP doesn't if that's the case.
http://downloadandroidrom.com/file/GalaxyNote4/CWM/philz_touch_6.59.0-trlte.tar
Sent from my SM-N910P using Tapatalk
Sorry to be the bearer of bad news, but this is most likely a hardware problem. I've had two Note 4's do exactly this. Flashed the stock rom on both with Odin, problems still persisted. It would just get random restarts and sometimes boot into "panic mode", whatever that is. The quality control on these phones is terrible. I baby them and never rooted any of them, yet two of them messed up like that, and all 3 of course have GPS issues. If it worked like it's supposed to it would be amazing, my friend has had one since my first Note with 0 issues, super jealous.
I hope its ok for me to post this here i couldnt find any threads on this issue and i didnt want to make new one just for this one problem so i figure i post it here since the post doesnt really point out to nothing specific and its on note 4 thread so i know ill get faster response than if i posted it in help thread ,but if i'm in wrong please feel free to delete this post at once . With that out of the way heres my issue and i hope theres an easy fix for it i was on latest pl1 build of 6.0.1 stock rooted i got tired of playing pokemon so i decided i want my themed look back so i restored my backup of 5.1.1 cog5 build ,everything works fine but my wifi ,its grayed out and when i try to turn it on it stays in "turning on " possition but it never does come on it eventualy goes back to " to see the list of networks turn on the wifi" .Now my question is is there any way to fix this wifi without flashing srock 5.1.1 i know there used to be fix for it back when i was on note 3 but this was yeaaaaars ago and i dont have that file any more thanks a million.
bigbabo said:
I hope its ok for me to post this here i couldnt find any threads on this issue and i didnt want to make new one just for this one problem so i figure i post it here since the post doesnt really point out to nothing specific and its on note 4 thread so i know ill get faster response than if i posted it in help thread ,but if i'm in wrong please feel free to delete this post at once . With that out of the way heres my issue and i hope theres an easy fix for it i was on latest pl1 build of 6.0.1 stock rooted i got tired of playing pokemon so i decided i want my themed look back so i restored my backup of 5.1.1 cog5 build ,everything works fine but my wifi ,its grayed out and when i try to turn it on it stays in "turning on " possition but it never does come on it eventualy goes back to " to see the list of networks turn on the wifi" .Now my question is is there any way to fix this wifi without flashing srock 5.1.1 i know there used to be fix for it back when i was on note 3 but this was yeaaaaars ago and i dont have that file any more thanks a million.
Click to expand...
Click to collapse
To fix the WiFi and camera focus, get the bootloader for OG5 from OP in this thread and flash it in Odin.
https://forum.xda-developers.com/showthread.php?p=66352412
The ones labeled firmware are bootloaders. You don't have to flash the whole OG5 stock tar but you still could. Just make sure the flash restores that bootloader and you should be set.
Likewise, you could still restore a MM backup and restore its bootloader.
I think you should backup your keepsakes in internal memory and wipe internal memory before restoring a backup that crosses Android versions. With backups on extSdCard, you could wipe everything but that but I'd think you could factory reset, wipe internal memory plus the Android folder on extSdCard and have a good transition with the bootloader flash. Otherwise, a factory reset would be the minimum step but may leave some residual information you may not need cluttering your memory along with what you want to keep. Seems I recall some having issues coming back to lollipop from MM without wiping internal memory?
Just curious, do you recall what you wiped going back to lollipop?
Sent from my SM-N920P using Tapatalk
Nothing i just go back n forth between lp and mm depending on lvl of interest in pokemon lol i have backups of 6.0.1 and 5.1.1 i just restore backups without wiping it restores fine aside from wifi not turning on i have no other issues
Edit: sorry meant to quote the post above me
bigbabo said:
Nothing i just go back n forth between lp and mm depending on lvl of interest in pokemon lol i have backups of 6.0.1 and 5.1.1 i just restore backups without wiping it restores fine aside from wifi not turning on i have no other issues
Edit: sorry meant to quote the post above me
Click to expand...
Click to collapse
Gotcha. Just an old question in the back of my mind from early days of MM. I researched the TWRP thread, the developers recommended a factory reset.
If you've ever noticed internal memory available seemingly smaller than usual, it could be the extraneous folders.
Thanks.
Sent from my SM-N920P using Tapatalk

Help - Galaxy Tab S 10.5 Bootloop Out of Nowhere

So...
Last week, my wife's Tab S went into a bootloop. She runs complete stock, we haven't rooted, or anything. There had been a notification about an update, but she hadn't touched it. She'd updated to Lollipop at some point last year, but hadn't applied the absolute latest update. One day last week, she just turned it on, and it started bootlooping.
Because it was so stock, there were no backups, no nandroids, or anything like that. No Custom Recovery. I told her "well, we can just do a factory reset. You'll lose everything, but once we get you back up and running, it'll just re-download everything from the Goog." So we factory reset it. Looked good for a minute, booted into the first screen, enter in your Wi-Fi password, all that. As soon as we got the Wi-Fi password entered, however, it re-booted. And keep rebooting. Bootloop city. No problem. I walked her through (over the phone) using Odin to flash the latest Lollipop firmware. No dice. It appeared to flash successfully, but still bootlooped.
Over the weekend, I tried using Kies to flash the most official firmware I could find. Everything was successful -computer recognized the device, was able to download "direct from the source," as it were, but it got stuck at 69% twice before failing. I read somewhere that one had to run Kies in administrator mode to get it to successfully complete. So I did, and it got past 69%, successfully completing the flash. STILL NO LUCK. STILL WITH THE BOOTLOOPS.
Last night, I realized that I hadn't flashed in Odin using Administrator Mode. Tried it, using latest 5.0.2 (XAR-Cellular South). Flashed successfully, all appeared well. Still bootlooped.
So, I'm stuck. I can get into recovery, I can get into Download Mode, I can successfully flash. I just can't get the darn thing booted.
Thoughts, anyone? Should I try flashing a Custom ROM? How hard is that using Odin? Thanks in advance.
Ok this will take a few tries but here is my method of dealing with this situation
1) Flash stock using Odin
2) AS SOON AS the screen goes blank, start holding Power+Volume Up+Home
3) When recovery boots, release the buttons
4) Use the volume buttons to select "Wipe data/factory reset"
5) Press power to confirm
6) Reboot
If that doesn't work, you may either:
1) (more likely) Installing a ROM will fix the problem
2) (unlikely but possible) You might have worn NAND pages, which I doubt but could cause this behavior.
Nandr0idC0nsumer said:
Ok this will take a few tries but here is my method of dealing with this situation
1) Flash stock using Odin
2) AS SOON AS the screen goes blank, start holding Power+Volume Up+Home
3) When recovery boots, release the buttons
4) Use the volume buttons to select "Wipe data/factory reset"
5) Press power to confirm
6) Reboot
If that doesn't work, you may either:
1) (more likely) Installing a ROM will fix the problem
2) (unlikely but possible) You might have worn NAND pages, which I doubt but could cause this behavior.
Click to expand...
Click to collapse
Thanks, I'll try these steps tonight when I get home, and report back!
All right, here's something interesting. Before I tried your first step, I remembered that the other night, I left it stuck at the Samsung logo -it was just kind of stuck there, and since the behavior was a little different than I'd seen before (not continuous bootlooping), I thought I'd boot into recovery and wipe. I did, I wiped (factory reset), and rebooted. The tablet booted into the first screen, Accessibility/Wi-Fi, blahblah. This was where it usually rebooted. On a hunch, I bypassed entering in my WiFi key. I then bypassed almost everything else (Samsung account, Google account, etc.), expecting that the tablet would reboot at any moment. But I made it to the front apps page, where it shows you the side-launcher, the Magazine-Flipboard thingie, and whatnot. Wi-Fi still not connected, though. I opened up the app drawer, and scrolled around. Looked really good for a moment. I even took a picture with the camera, and viewed it in Gallery! Feeling brave, I thought, "well, maybe it just needed a couple of minutes before firing up the radio." So I went into settings, and inputted my WiFi key. It connected. And rebooted into its bootloop. (getting so tired of that boot-sound).
Went ahead and flashed the most original stock firmware I could find. As always, flashed successfully. As soon as it booted, I made my way to recovery, and wiped, per your instructions. No luck. Bootloop again.
It's something in the WiFi is what I've come to think as a result of the above. Which I don't entirely understand, as I thought the radio got re-flashed with the firmware.
I'm ready to try flashing a Custom Rom. Can I do that through Odin, or should I try and flash TWRP, and do it through there? Will TWRP flash without a working (bootable) OS?
All right. Thanks for your response!
Try this as a test.
First make a full backup of every partition with twrp including the EFS <<IMPORTANT!
Get it booting again without wifi then root the device and delete the EFS folder or delete it in recovery.
Reboot the device and try and enable wifi.
ashyx said:
Try this as a test.
First make a full backup of every partition with twrp including the EFS <<IMPORTANT!
Get it booting again without wifi then root the device and delete the EFS folder or delete it in recovery.
Reboot the device and try and enable wifi.
Click to expand...
Click to collapse
Got TWRP installed. Won't backup. Fails at 16% (system partition, I think). Just powers down to battery indicator in the middle of the backup. Looks like it backs up the EFS, though, since it's the first one. And when I go into TWRP's Restore option, there's a backup there (though I don't dare try and restore it).
Now I have to figure out a way to get the Custom ROM and GAPPS I downloaded onto the tablet without a reliable boot... It's gotten to the front screen a time or two tonight, but starts looping even when I bypass the WiFi setup.
Entered adb/TWRP interface. Tried to push two files, a Custom ROM file, and a GAPPS file. The ROM failed, with some sort of "Error 7," incompatible data, blahblah... Just out of curiosity, I tried to push the GAPPS file, and that failed after about 6%, and the tablet powered off.
I'm running out of ideas.
copied a custom rom to a USB/OTG stick (thumbdrive), and plugged it in. Fired up TWRP, tried to install. Wouldn't. Wouldn't install GAPPS, either. Looks like the only way it wants to flash anything is through ODIN or KIES.
The Latest...
All right...
I remembered that sometimes the TWRP version mattered. When I installed TRWP last night, I installed the latest and greatest, 3.0.2. Last night after I gave up, I remembered that sometimes, the latest and greatest TWRP doesn't install things perfectly. So, this morning, I downloaded TWRP 2.8.6-ish onto the USB/OTG device, and re-flashed the recovery partition. To be honest, I was surprised that TWRP was even able to flash that (but the TWRP image is only like 9.8 MB, so...)...
Got TWRP 2.8.6.0 flashed, and rebooted into TWRP. Immediately decided to try and re-flash the custom ROM that I'd tried unsuccessfully to flash last night, since the thumbdrive was still plugged in. Resurrection Remix Lollipop. Lined up GAPPS in the queue, as well. The ROM *appeared* to flash better than it had in TWRP 3.0.2, but it was sort of hard to see... GAPPS failed, and I was prepared to watch another round of bootloops. It did bootloop, sort of. The RR splash screen appeared, said that it was installing (or preparing) xx out of XX apps. Then, it rebooted. I figured it was doing its bootloop thing. However, it got to the same screen, "installing xx out of XX apps. Except that XX number had gone down, and the xx number had gone up. It repeated this action about 4 times --the last time I saw it reboot, it was "installing 1 out of 2 apps." And then...?
It booted into the RR lockscreen.
Of course, there were no GAPPS. In fact, there are something like only 20 apps total on the tablet. But it appears somewhat stable at the moment. (See picture).
Afraid to try and connect WiFi, afraid that it'll just bootloop.
Speaking of bootloop. At one point, once we got it booted, my wife hit an option in the Settings. LCD Density, I believe. As soon as she hit it (she literally just placed her finger over the 320 default option), the tablet rebooted. No loop, though. Rebooted straight back to the RR lockscreen.
So I appear to have a somewhat stable OS flashed onto the tablet at the moment. No GAPPS, though. No WiFi.
Anybody have a suggestion on where to go from here? I have my doubts as to whether or not I can even back up this configuration.
Sorry about all the updates. I kind of figured that if *anyone* else ever goes through what I'm going through, they'll have some sense of all the different things that can be tried in resurrecting a bricked/bootlooping device. I appreciate everyone's efforts to date -thank you so much, @Lightn1ng and @ashyx.
All right, because I can't leave well enough alone....
I got WiFi up and working. Tablet still stable and working. Wheeeee.... No GAPPS, though.
Downloaded GAPPS, second-smallest package from opengapps- only 128M (5.1 ARM package). Downloaded it in Android, from the tablet! Tried to flash it in TWRP. Failed, tablet rebooted halfway (not even) through. Now it's bootlooping again...
I should've left well enough alone, and waited for someone. Have tried re-installing Resurrection Remix, but tablet keeps failing to flash. Might have to try and flash a different TWRP. I don't know...
Have you tried another Gapps? Also, is this the WiFi only model or the LTE model we're talking about?
Lightn1ng said:
Have you tried another Gapps? Also, is this the WiFi only model or the LTE model we're talking about?
Click to expand...
Click to collapse
It's the WiFi-only model - SM-T800.
It's kind of weird. I thought it might be some sort of internal memory problem (like the worn Nand pages you mentioned), since almost anything I try to do in TWRP fails (although I was able to flash an entire Custom ROM the one time AND get it booted) -but backing up isn't working, whether it's to internal/external SD. And the fact that I can flash perfectly (subjective term there) well using Odin or Kies tells me that whatever problems the tablet is having, something's getting through.
I'll try a different GAPPS package. Right now, though, TWRP isn't letting me flash hardly anything, and moving files back and forth on this thing is just awful.
AGH - I was so close!
daina said:
It's the WiFi-only model - SM-T800.
It's kind of weird. I thought it might be some sort of internal memory problem (like the worn Nand pages you mentioned), since almost anything I try to do in TWRP fails (although I was able to flash an entire Custom ROM the one time AND get it booted) -but backing up isn't working, whether it's to internal/external SD. And the fact that I can flash perfectly (subjective term there) well using Odin or Kies tells me that whatever problems the tablet is having, something's getting through.
I'll try a different GAPPS package. Right now, though, TWRP isn't letting me flash hardly anything, and moving files back and forth on this thing is just awful.
AGH - I was so close!
Click to expand...
Click to collapse
I'm running out of ideas!
Maybe somebody else with a T800 could backup their entire EMMC using
Code:
dd if=/dev/mmcblk0 of=/sdcard/full_nand_dump.bin
And you take the file on your tablet and do
Code:
dd if=/sdcard/full_nand_dump.bin of=/dev/mmcblk0
And restore YOUR efs folder using TWRP.
THIS IS A DANGEROUS OPERATION AND I AM NOT RESPONSIBLE FOR ANYTHING THAT GOES WRONG!
---------- Post added at 08:01 PM ---------- Previous post was at 07:57 PM ----------
@ashyx Any more ideas before I go ahead with my evil world domination plan to recover this device?
I wouldnt carry out any risky operations until a full backup can be made with twrp or you may end up with an unrecoverable device.
If twrp cannot backup the system partition then there is an issue with the partition.
Try backup again and post the recovery log, it may contain some relative information.
I have the same issues and have tried eveything. I was rooted and running the latest Pheonix rom on my sm-t800. Last Wednesday (8-10) I starting getting boot loops out of nowhere, no new apps nothing just a daily driver. I've been through everything on here and have gone back to bone stock but to no avail, the boot loops just keep coming. I can connect to wifi and get things set up but if I try to use anything more than 'light usage' the tab starts its boot loops again and rows fits for about 10 minutes and always different timing on the boot. Sometimes it will make it to the Samsung logo, sometime only to Tab S and sometimes about 10 seconds of usage.. I know this isn't helping much but wanted to let you know there are more of us with the same problem. Will be blab to try anything to help said issue.
Exactly the same issue on my LTE version.
Samsung support just asked me 230€ for a new motherboard.
I refused to repair. I think it is related to nand memory..
Hello I have both the 8.4" and 10.5" I updated the 8.4" to Android 5.02 nothing but boot loops my other is still on 442 and I wont be updating it as its working fine. I have been reading a few posts and the problem was right in front of me all the time I have 2 internet connections 2.4 GHZ and 5.0 GHZ if I connect to the 5.0 GHZ I get boot loops but if I stay on 2.4 GHZ no problems what so ever so I may just install a custom rom and my 10.5 tab and stay clear of the faster internet.
srfairhurst said:
Hello I have both the 8.4" and 10.5" I updated the 8.4" to Android 5.02 nothing but boot loops my other is still on 442 and I wont be updating it as its working fine. I have been reading a few posts and the problem was right in front of me all the time I have 2 internet connections 2.4 GHZ and 5.0 GHZ if I connect to the 5.0 GHZ I get boot loops but if I stay on 2.4 GHZ no problems what so ever so I may just install a custom rom and my 10.5 tab and stay clear of the faster internet.
Click to expand...
Click to collapse
Why not just update to Marshmallow? Absolutely no issues for me.
ashyx said:
Why not just update to Marshmallow? Absolutely no issues for me.
Click to expand...
Click to collapse
Now i figured out its the wifi thats causing the problem i will update to android 6.01 or if i can find a good custom rom il risk that.
daina said:
It's the WiFi-only model - SM-T800.
It's kind of weird. I thought it might be some sort of internal memory problem (like the worn Nand pages you mentioned), since almost anything I try to do in TWRP fails (although I was able to flash an entire Custom ROM the one time AND get it booted) -but backing up isn't working, whether it's to internal/external SD. And the fact that I can flash perfectly (subjective term there) well using Odin or Kies tells me that whatever problems the tablet is having, something's getting through.
I'll try a different GAPPS package. Right now, though, TWRP isn't letting me flash hardly anything, and moving files back and forth on this thing is just awful.
AGH - I was so close!
Click to expand...
Click to collapse
DrinkSlinger said:
I have the same issues and have tried eveything. I was rooted and running the latest Pheonix rom on my sm-t800. Last Wednesday (8-10) I starting getting boot loops out of nowhere, no new apps nothing just a daily driver. I've been through everything on here and have gone back to bone stock but to no avail, the boot loops just keep coming. I can connect to wifi and get things set up but if I try to use anything more than 'light usage' the tab starts its boot loops again and rows fits for about 10 minutes and always different timing on the boot. Sometimes it will make it to the Samsung logo, sometime only to Tab S and sometimes about 10 seconds of usage.. I know this isn't helping much but wanted to let you know there are more of us with the same problem. Will be blab to try anything to help said issue.
Click to expand...
Click to collapse
Hello,
and the rest of story??
i can flash TWRP in download mode, and i can intall zip by TWRP , the lineage rom,
but, cant odin flash official md5 file, it stucks on logo.

Categories

Resources