[Q] Device powercycles when trying to make or recieve phone calls - Sprint Galaxy Note 4 Q&A, Help & Troubleshooting

In the past few days after flashing alliance v2 i noticed that my phone would freeze then power cycle when I attempted to make or receive a call. Everything else works, I tried a different rom and still having the same issue. Any ideas?

eeeeeeeeek said:
In the past few days after flashing alliance v2 i noticed that my phone would freeze then power cycle when I attempted to make or receive a call. Everything else works, I tried a different rom and still having the same issue. Any ideas?
Click to expand...
Click to collapse
Take a look at posts 2 and 3 of this thread.
http://forum.xda-developers.com/showthread.php?t=3067828
HELP!!! Need a PIT file for N4
Odd problems that carry past factory reset and ROM flashes require a better flush. And clean install.

samep said:
Take a look at posts 2 and 3 of this thread.
http://forum.xda-developers.com/showthread.php?t=3067828
HELP!!! Need a PIT file for N4
Odd problems that carry past factory reset and ROM flashes require a better flush. And clean install.
Click to expand...
Click to collapse
So I had already started when I saw that, though the second post on that thread is a little confusing. However I had already odin back, booted up, but didn't wipe it, so instead I hooked it up to samsung kies, and did a full restore from kies. Made a test call, still froze, and crashed. So re rooted and put twrp then did an excessive number of advanced wipes. I even used the repair option to repair system then data. Just flashed vision and waiting on it too boot to see. Should I move further questions to that thread?

eeeeeeeeek said:
So I had already started when I saw that, though the second post on that thread is a little confusing. However I had already odin back, booted up, but didn't wipe it, so instead I hooked it up to samsung kies, and did a full restore from kies. Made a test call, still froze, and crashed. So re rooted and put twrp then did an excessive number of advanced wipes. I even used the repair option to repair system then data. Just flashed vision and waiting on it too boot to see. Should I move further questions to that thread?
Click to expand...
Click to collapse
I'd suggest keeping your posts on this thread. Just referred to that to save time.
Try the steps. Ask if not clear. If it sounds too extreme, start with the factory reset, Odin and factory reset again before flashing a deodexed ROM like Alliance. Update with results.

eeeeeeeeek said:
So I had already started when I saw that, though the second post on that thread is a little confusing. However I had already odin back, booted up, but didn't wipe it, so instead I hooked it up to samsung kies, and did a full restore from kies. Made a test call, still froze, and crashed. So re rooted and put twrp then did an excessive number of advanced wipes. I even used the repair option to repair system then data. Just flashed vision and waiting on it too boot to see. Should I move further questions to that thread?
Click to expand...
Click to collapse
Ii did as follows and tried several other ways, same results on factory image, unless I have a bad image, I pulled it off of one of the forums here

Are you powering down prior to Odin of stock tar? Did you use your PC to download the tar? Have you tried doing this without the sdcard? The full wipes are important.
Try the NIE stock tar.
http://forum.xda-developers.com/showthread.php?p=56853341

samep said:
Are you powering down prior to Odin of stock tar? Did you use your PC to download the tar? Have you tried doing this without the sdcard? The full wipes are important.
Try the NIE stock tar.
Click to expand...
Click to collapse
Ive wiped everything and formatted data repeatedly......I had a nand backup i forgot about, I'm going to restore that and see. I haven't tried flashing anything without the sd card from recovery, I have removed my SD card for the moment. It does seem like this is the issue, something with the partition. It's of course possible I didn't follow directions properly, though I feel I have. I'll also try NIE if need be. It's very bizzare issue. everything else works fine.
Update: Flashed NK2 stock tar, tried to make a call, same thing, phone freezes and powercycles.
Update 2: I even tried a different dialer, same results. Could a hardware issue cause this?

My suggestion is to try the factory reset, power down, Odin and Dial*##72786# to reprovision the phone; data profile update and try again.
Still fails? Could be hardware failure.
Anyone else?

samep said:
My suggestion is to try the factory reset, power down, Odin and Dial*##72786# to reprovision the phone; data profile update and try again.
Still fails? Could be hardware failure.
Anyone else?
Click to expand...
Click to collapse
Ive done all of this, even the 72786, tried wifi calling too just to be sure. maybe something with the antennai

Outside of a good suggestion, I'd stay with stock, call Sprint support. If not resolved there, setup a tech appointment.
Sent from my SM-N910P using Tapatalk

Related

My phone is constantly rebooting

I'm having a very strange issue with my device right now. Basically whenever I flash any custom ROM I end up in a boot loop. It started last night after I flashed a couple of CM10 based ROMs and then tried to revert back to Skynote which is touchwiz based. I was able to fix it by using Odin and flashing the stock Rogers ROM .tar file. That fixed everything and stock was running fine all night with no reboots or issues. This morning I did a fresh download of the ROM rebooted to TWRP wiped cache *2, Formatted system *2 and factory reset *2, installed the ROM and rebooted. I should mention I am using TWRP version 2.4.1.0. The ROM usually loads for about 1-2 mins then reboots and repeats over and over. Does anyone have any ideas? I've even formatted the internal and external storage. I did notice there is one folder on my internal SD card that I cannot seem to remove called Z and has a LMT.apk and another folder with wallpapers in it. I cannot delete or remove this folder as it keeps saying the folder is write protected. Even after formatting the internal storage that folder remains which makes me wonder if my SD card is screwed up.
Sorry for the long post but I am running out of ideas and don't want to be stuck on Stock. What could be causing this? I've tried flashing a new kernel from TWRP and still the same results, I've even tried different ROMs just in case but still the same results. The only thing that seemed to work so far was the stock ROM via Odin.
veebomb said:
I'm having a very strange issue with my device right now. Basically whenever I flash any custom ROM I end up in a boot loop. It started last night after I flashed a couple of CM10 based ROMs and then tried to revert back to Skynote which is touchwiz based. I was able to fix it by using Odin and flashing the stock Rogers ROM .tar file. That fixed everything and stock was running fine all night with no reboots or issues. This morning I did a fresh download of the ROM rebooted to TWRP wiped cache *2, Formatted system *2 and factory reset *2, installed the ROM and rebooted. I should mention I am using TWRP version 2.4.1.0. The ROM usually loads for about 1-2 mins then reboots and repeats over and over. Does anyone have any ideas? I've even formatted the internal and external storage. I did notice there is one folder on my internal SD card that I cannot seem to remove called Z and has a LMT.apk and another folder with wallpapers in it. I cannot delete or remove this folder as it keeps saying the folder is write protected. Even after formatting the internal storage that folder remains which makes me wonder if my SD card is screwed up.
Sorry for the long post but I am running out of ideas and don't want to be stuck on Stock. What could be causing this? I've tried flashing a new kernel from TWRP and still the same results, I've even tried different ROMs just in case but still the same results. The only thing that seemed to work so far was the stock ROM via Odin.
Click to expand...
Click to collapse
I should probably add that I was coming from Android 4.2.2 and want to get back on 4.1.2
veebomb said:
I'm having a very strange issue with my device right now. Basically whenever I flash any custom ROM I end up in a boot loop. It started last night after I flashed a couple of CM10 based ROMs and then tried to revert back to Skynote which is touchwiz based. I was able to fix it by using Odin and flashing the stock Rogers ROM .tar file. That fixed everything and stock was running fine all night with no reboots or issues. This morning I did a fresh download of the ROM rebooted to TWRP wiped cache *2, Formatted system *2 and factory reset *2, installed the ROM and rebooted. I should mention I am using TWRP version 2.4.1.0. The ROM usually loads for about 1-2 mins then reboots and repeats over and over. Does anyone have any ideas? I've even formatted the internal and external storage. I did notice there is one folder on my internal SD card that I cannot seem to remove called Z and has a LMT.apk and another folder with wallpapers in it. I cannot delete or remove this folder as it keeps saying the folder is write protected. Even after formatting the internal storage that folder remains which makes me wonder if my SD card is screwed up.
Sorry for the long post but I am running out of ideas and don't want to be stuck on Stock. What could be causing this? I've tried flashing a new kernel from TWRP and still the same results, I've even tried different ROMs just in case but still the same results. The only thing that seemed to work so far was the stock ROM via Odin.
Click to expand...
Click to collapse
Do you have SD Card adapter for the computer? If so, try removing the card from the phone, then plug it into the computer and formatting it that way. For the ROM boot loop issue, try flashing a stock ROM using ODIN, then using whatever method you like the most to flash the ROM you want to use.
thunderx2000 said:
Do you have SD Card adapter for the computer? If so, try removing the card from the phone, then plug it into the computer and formatting it that way. For the ROM boot loop issue, try flashing a stock ROM using ODIN, then using whatever method you like the most to flash the ROM you want to use.
Click to expand...
Click to collapse
I'm now pretty certain its a bootloader issue as I'm downgrading from Android 4.2.2 to 4.2.1 but thanks.
take your external sd card out and see what happens
wase4711 said:
take your external sd card out and see what happens
Click to expand...
Click to collapse
I wiped everythign 2x and then I flashed the file you posted in the other thread and removed my SD card but still getting reboots. Should my SD card be called sdcard0 still in my files?
yes, your card will still be called sdcard0
take your external card out completely, and see if the phone still boot loops
wase4711 said:
yes, your card will still be called sdcard0
take your external card out completely, and see if the phone still boot loops
Click to expand...
Click to collapse
It still loops. This is crazy, when I used Odin to go back to stock it was working ok but everythin else has made it bootloop. I can try using Odin again when I get home and see if the restore SD card file works then. Does anything have to be done to the bootloader?
no, don't mess with the bootloader; you will probably brick it if you do
go back to stock via odin for a day or 2, and make sure its not the hardware itself..
wase4711 said:
no, don't mess with the bootloader; you will probably brick it if you do
go back to stock via odin for a day or 2, and make sure its not the hardware itself..
Click to expand...
Click to collapse
So its not like moving back to ICS from jellybean where you had to flash a new bootloader?
Op you're on Rogers right? Make sure that you have the Skynote without the new modem.
~PsyCl0ne
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
PsyCl0ne said:
Op you're on Rogers right? Make sure that you have the Skynote without the new modem.
~PsyCl0ne
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Click to expand...
Click to collapse
yes I am on Rogers, sorry but how can I tell that?
I don't think I have flashed a new bootloader more than once in the last 6 or7 years, on an htc evo4g..
you should not ever have to do that on this phone
veebomb said:
yes I am on Rogers, sorry but how can I tell that?
Click to expand...
Click to collapse
oh wait I think I see what you're refering to. I wonder how many different mistakes I have actually made durring this fiasco of mine.... I'll give that a try when I get home and post back
veebomb said:
oh wait I think I see what you're refering to. I wonder how many different mistakes I have actually made durring this fiasco of mine.... I'll give that a try when I get home and psot back
Click to expand...
Click to collapse
Okay I'm out right now but I'll check in every once in a while.
~PsyCl0ne
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Same here
I am having the same exact problem you are veeboom. It's not boot-looping because it actually lets me into the phone for about one minute; then it reboots. I have tried everything that you have tried, right along with you and result is nil. It won't stay on for more than a minute. The only difference is that I am just trying to get Roger's Clean Stock ROM working. It sounds like you have accomplished that and are trying to get a custom going. I have tried Odin flashing 3 times; once without the sd card. I am pretty sure SD card is not the issue. I have wiped this phone at least 5 times (everything except the the extSdCard (AKA sdcard1).
I am going to see if I can find some other posts on this problem and will let you know if I finally find a fix. Hope you will do the same.
Happy to report the end of the boot loop!
Although I'm kind of embarrassed to admit it was caused by an incompatible modem file I flashed over and over... :silly:
Thanks for everyone's help.
floykoe said:
I am having the same exact problem you are veeboom. It's not boot-looping because it actually lets me into the phone for about one minute; then it reboots. I have tried everything that you have tried, right along with you and result is nil. It won't stay on for more than a minute. The only difference is that I am just trying to get Roger's Clean Stock ROM working. It sounds like you have accomplished that and are trying to get a custom going. I have tried Odin flashing 3 times; once without the sd card. I am pretty sure SD card is not the issue. I have wiped this phone at least 5 times (everything except the the extSdCard (AKA sdcard1).
I am going to see if I can find some other posts on this problem and will let you know if I finally find a fix. Hope you will do the same.
Click to expand...
Click to collapse
You should have started your own thread but can you give us a run down of what you did prior to having the boot loop?
~PsyCl0ne
Sent from my SAMSUNG-SGH-I317 using xda app-developers app
Things just got worse
I have have the phone for about two months. A week ago I rooted it with Samsung Note II tool box and everything was fine, until I found out that there were these "custom ROMs" available. So I flash one, but it was unstable. I flashed liquid smooth; same thing, then I tried a few ROMS that were a little more mature, but their were always things I could not live with (like no blue tooth or apps crashing). I also found out what a boot loop was all about. It sucked, but the forums help me get it fixed. Now I am tried of messing with all these custom ROMs and I just want my old reliable system back, with root. Currently I am trying to get Roger's CleanROM AT&T Special Edition 1.2 working again (with I believe I started with). I have been unable to remedy boot loops that happen about every minute. I have flashed, wiped (everything), unrooted, re-rooted, flashed with Odin, flashed core kernel via odin per instructions, called it bad names and threatened it; then said I was sorry. I have repeated all these things many times, including with and without the extSdCard. SD card does not seem to be the issue. I am still looking for more things to try. Just now it has started refusing to boot at all. I gets to the boot screen and gets stuck.
I am trying to find out more about how to use ADB to re-partition upon stock ROM flash. You know anything about that? I have been at this all day.
It sounds like you may have done the same thing I did which was flash an incompatible modem file. My suggestion would be for you to use Odin and flash back to the Rogers Stock ROM. It's easy and takes less than 10 minutes.
Basic instructions,
1. Download and unzip Odin
2. Put your phone in download mode (turn off your phone, and press the buttons together: vol down + home + power for a few seconds)
3. Run Odin then hit PDA button on the right side, then find and choose the firmware file you downloaded to be flashed.
4. Make sure your device is recognized in Odin3 (The ID: COM box near the top left part of the Odin program should go yellow once you connect your phone)
5. Make sure re-partition in NOT checked
6.Press Start to initiate flashing
7. Once finished your device should automatically reboot. You may need/want to do a factory reset which will wipe all your data and you would be back to the way your first got your phone. Enter into recovery mode by turning off your phone and next press the three buttons simultaneously: volume up + home + power. After getting into recovery, select Wipe/Factory reset.
8. Reboot
You are now stock 100%
Here is a link to download Odin,
http://www.mediafire.com/?x4356fnc1ge48hf
Here is a link to the Rogers stock ROM you flash with Odin,
http://www.hotfile.com/dl/180165074/47da708/I317MVLALJ2_I317MOYAALJ2_RWC.zip.html
Here is a link to a guide with some instructions and a few pictures,
http://www.andromods.com/unroot-locking/how-to-restore-samsung-galaxy-note-2-to-stock-rom-firmware-with-odin.html

[Q] What kind of brick and what to do about it?

Update The likely culprit, at least for the "install button" problem, appears to be an app called Velis Auto Brightness. A little over three weeks after this problem first arose, I switched my ROM to Dandroid. In deciding what apps gradually to add back, I ran across comments like the following for Velis:
Cannot press install from an APK Found a bug that needs fixing. With this app enabled for some reason installing from an APK it renders the Install button useless but the cancel button still works. As soon as I disabled this App, the Install button worked again.
Click to expand...
Click to collapse
Nice, but one slight issue I really like this app. Very useful and easy to use. My only issue is that when the app is active, if I turn off system auto brightness and try to raise the brightness, Velis overrides this and forces auto brightness.
Click to expand...
Click to collapse
Recently, I had problems with my S3, on which I'd been running Stockorama v2. Starting July 3, the install button stopped working. The eventual solution, alas, was only temporary. I restored a June 27 nandroid and reinstalled apps, except for one that I suspected of causing the problem because it had only recently been installed before the problem occurred,
That worked for almost three weeks, until the phone function stopped working. Whatever telephone number I entered, the phone tried to call 333223. At that point, I had available to me a phone that couldn't make, but could receive, calls or, if I restored a different nandroid, a phone the seemingly functioned fully, except that I could not install any app that required pressing the on-screen install button.
From reading the latter thread and general considerations, I decided to do a clean reinstall of Stockorama. First, I wiped everything and used Odin to install mrRobinson's root66. I wiped again and used mobile Odin to install Stockorama v2. Before doing so, I backed up IMEI and EFS.
Reinstalling Stockorama was frustrating because the Aroma installer kept hanging. Late last night (early this morning), the installer completed. Leaving the phone plugged in to an electric outlet, I went to bed with the screen displaying "Samsung Galaxy SIII." I figured that, come morning, I'd be able to complete the process of setting up the phone.
Instead, I have some kind of brick. When I awoke and checked the phone, the screen had the same display as when I went to bed. Foolishly, perhaps, I thought that pressing the power button might help. It didn't.
Now, although the phone was continuously plugged in, pressing the power button first does nothing or, eventually displays a completely discharged battery with no indication that the phone is charging.
Pressing the power button just now with the phone unplugged again displayed "Samsung Galaxy SIII." FWIW, I've plugged the phone back in.
What to do next is a mystery to me, however.
As always, all advice is appreciated.
I managed to get into Download mode and am using Odin to install, again, root66. Assuming that succeeds, I expect I could use baby-step guidance to prepare the phone for and, once again, install Stockorama. Alternatively, at this point I'd consider another custom ROM that, like Stockorama, is lean and close to stock.
RebDovid said:
I managed to get into Download mode and am using Odin to install, again, root66. Assuming that succeeds, I expect I could use baby-step guidance to prepare the phone for and, once again, install Stockorama. Alternatively, at this point I'd consider another custom ROM that, like Stockorama, is lean and close to stock.
Click to expand...
Click to collapse
1) Aroma is notorious for freezing. Until the recent update, it could, at times, be pretty much unusable. This is not a problem with your device. The new update seems to have fixed those problems, but since Stockorama has not been updated, it is still using the old version.
2) Your issues sound a lot like malware (can't install, can't make outgoing calls). I'm not familiar with any Android malware, but crippling the phone's main functions seems like a good target.
3) You flashed root66 with Odin. Then go on to say you used Mobile ODIN to flash Stockorama. This would imply that your root66 setup was functioning before you flashed Stockorama. Is this true, or have I misunderstood you?
4) Describe to me your "complete wipe" process. Are you using the stock recovery's factory reset? Are you manually wiping the system partition as well? If not stock, what custom recovery are you using, and what version?
5) When you get stuck on the splash screen, you need to factory reset. But, going from one TW ROM to another TW ROM would not require this usually, and could be indicative of another issue. Like bad hardware.
6) If root66 is fine, and you are blaming the ROM, you could go for another one. I personally use S3Rx. I would try Dandroid if it had Wifi Calling. Don't see the point in using TW if I can't have Wifi Calling. Sorry. It's actually pretty handy to have with T-Mobile's less than stellar coverage when out of the city.
7) What firmware are you running? It's an educated guess that you are trying to use the MD5 root66, but what about your bootloader, baseband, rpm, rz, sbl? What versions are those?
Aerowinder said:
1) Aroma is notorious for freezing. Until the recent update, it could, at times, be pretty much unusable. This is not a problem with your device. The new update seems to have fixed those problems, but since Stockorama has not been updated, it is still using the old version.
Click to expand...
Click to collapse
Understood
2] Your issues sound a lot like malware (can't install, can't make outgoing calls). I'm not familiar with any Android malware, but crippling the phone's main functions seems like a good target.
Click to expand...
Click to collapse
You may be right. But I use both Lookout and Avast.
3) You flashed root66 with Odin. Then go on to say you used Mobile ODIN to flash Stockorama. This would imply that your root66 setup was functioning before you flashed Stockorama. Is this true, or have I misunderstood you?
Click to expand...
Click to collapse
Yes, root66 appeared to be functioning. I signed into my Google accounts; reinstalled Root Checker; checked root; and reinstalled Mobile ODIN.
4) Describe to me your "complete wipe" process. Are you using the stock recovery's factory reset? Are you manually wiping the system partition as well? If not stock, what custom recovery are you using, and what version?
Click to expand...
Click to collapse
It was late last night, and I didn't write down my steps. (My bad.) So far as I can recall, from the current TWRP recovery I checked all the available wipe boxes. After wiping, I then went into Download mode, connected the phone to my pc, started Odin, added root66 as the PDA, and clicked start.
I'm not sure what you mean by manually wiping the system.
In installing Stockorama, I chose the full wipe option.
5) When you get stuck on the splash screen, you need to factory reset. But, going from one TW ROM to another TW ROM would not require this usually, and could be indicative of another issue. Like bad hardware.
Click to expand...
Click to collapse
What kind of hardware problem could I have? How do I check?
6) If root66 is fine, and you are blaming the ROM, you could go for another one. I personally use S3Rx. I would try Dandroid if it had Wifi Calling. Don't see the point in using TW if I can't have Wifi Calling. Sorry. It's actually pretty handy to have with T-Mobile's less than stellar coverage when out of the city.
Click to expand...
Click to collapse
I'm not blaming the ROM. I'm simply at a loss.
Why do you use S3Rx? What do you like and dislike about it?
7) What firmware are you running? It's an educated guess that you are trying to use the MD5 root66, but what about your bootloader, baseband, rpm, rz, sbl? What versions are those?
Click to expand...
Click to collapse
I don't know what all the acronyms stand for. But this is what I can tell you.
From "About device," I'm running Android version 4.1.2 and Baseband version T999UVDMD5. The Kernel version is
3.0.31-1128078
[email protected] #2
SMP PREEMPT Mon Apr 15 11:59:10 KST
2013
The Build number is JZ054K.T999UVDMD5
RebDovid said:
Understood
You may be right. But I use both Lookout and Avast.
Yes, root66 appeared to be functioning. I signed into my Google accounts; reinstalled Root Checker; checked root; and reinstalled Mobile ODIN.
It was late last night, and I didn't write down my steps. (My bad.) So far as I can recall, from the current TWRP recovery I checked all the available wipe boxes. After wiping, I then went into Download mode, connected the phone to my pc, started Odin, added root66 as the PDA, and clicked start.
I'm not sure what you mean by manually wiping the system.
In installing Stockorama, I chose the full wipe option.
What kind of hardware problem could I have? How do I check?
I'm not blaming the ROM. I'm simply at a loss.
Why do you use S3Rx? What do you like and dislike about it?
I don't know what all the acronyms stand for. But this is what I can tell you.
From "About device," I'm running Android version 4.1.2 and Baseband version T999UVDMD5. The Kernel version is
3.0.31-1128078
[email protected] #2
SMP PREEMPT Mon Apr 15 11:59:10 KST
2013
The Build number is JZ054K.T999UVDMD5
Click to expand...
Click to collapse
This may not be the case on android, but I know on pc having mulyiple av programs causes all sorts of fun problems! Personally, I don't think any android av apps are worth anything.
Anytime you get hung up at the splash screen, you have to factory reset. If this were hw related it would do this regardless of your rom. And just to clarify, when moving between touchwiz roms, this can happen when when you go backwards from something like MD5 to LJA. This doesn't always happen, but it does happen.
Manually wiping means going into recovery and choosing wipe/format system before flashing your rom.
Sent from my SGH-T999 using xda premium
DocHoliday77 said:
This may not be the case on android, but I know on pc having mulyiple av programs causes all sorts of fun problems! Personally, I don't think any android av apps are worth anything.
Anytime you get hung up at the splash screen, you have to factory reset. If this were hw related it would do this regardless of your rom. And just to clarify, when moving between touchwiz roms, this can happen when when you go backwards from something like MD5 to LJA. This doesn't always happen, but it does happen.
Manually wiping means going into recovery and choosing wipe/format system before flashing your rom.
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
I failed again with Stockorama. To get a working phone, I restored my root66 nandroid.
At all relevant times, I've been on MD5.
I wonder whether I should try:
(a) restoring stock and trying (i) Stockorama or (ii) S3Rx; or
(b) installing S3Rx.
Before trying either, or something else, I'll pull the PIT file for you. Please just give me instructions.

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.

[Q] Recovery bootloop after Odin/Kies/Heimdall STOCK flash, only boots to DL mode

Hi folks, long time reader, first time noob answer seeker.
I'm no stranger to rooting, flashing, hacking about and such - I even spend most of my day as a software engineer, and I've finally given up on this one - so here I am (rock me like a hurricane), please be kind.
SM-900T - It was rocking pretty darn well on Jedi Elite which I had flashed over rooted stock 4.3 MI7 - then (probably after one too many XPosed modules) it just kept rebooting randomly. Thinking it was no biggie, I thought I could just reflash to stock and call it a day. Thirteen or so flashes later, I gave up on 4.3 and figured I'd just take the thing up to 4.4.2 NB4 by upgrading everything to 4.4.2 via Kies.
That's when I first ran into the bootloop issue, read a lot about it, and managed to get it up(ish) on stock, rooted, with Philz 6.X... Couldn't flash a ROM to save myself and wound up with another soft brick.
Flash forward to Friday - decided to start from scratch again - attempted to flash stock 4.4.2 from Kies, from Odin, From Heimdall... Nothing seems to be able to get me out of the current state it's in:
Only boots to download mode. Flashes seem to work fine, but on that first reboot where it tries to go to stock recovery to finish up on the device itself, it never gets there - boot loops trying to load recovery no matter how it wants to get there. If I pull the battery and start up (either straight to system or by cancelling out of download mode), it boot loops trying to load system. Boots fine to download mode, where I attempt to flash again with the same results.
Yes, I've tried Odin 3.0.9, 3.0.7, 1.8.5, Heimdall on Mac, Heimdall on Windows, Kies on Mac, Kies on Windows - repartition via PIT and not. Installed, uninstalled, and reinstalled all software and drivers multiple times, tried multiple cables on multiple USB ports.... Most of the time it looks like it's going to be fine (sometimes the flash fails, usually through Kies), but never surivives that first reboot after the flash.
Every answer I've seen says to do the things I've already done or cannot do (flash stock via Odin, pull the battery and boot to stock recovery and do a factory reset - which I'd LOVE to do, but can't). No problem recognizing the sucker on the PC/Mac
Next step: try flashing a N9005 ROM...
Any other thoughts? I do have another N900T that's working but has a blacklisted IMEI, and I've been tempted to swap the IMEIs a last resort (although either I'm too dumb to make it stick, EFS pro says it succeeds in writing the IMEI after I do a EFS format, but it doesn't stick.... Either I'm missing something, or I need a UART cable) - is there a way of swapping just the radio hardware or just the internal storage? OR, is there a way of taking a full system image of my working phone and making an Odin-flashable tar from that?
Failing any of these options, perhaps I'll wait for an Odin-flashable 4.4.3 if such a thing exists - or, hope to get lucky and swap it out at a store praying they don't see I've tripped Knox.
Looks like you've tried almost everything. Take it in and have them swap it.
Sent from my SM-G900T using Tapatalk
Coming from you...
noobtoob said:
Looks like you've tried almost everything. Take it in and have them swap it.
Click to expand...
Click to collapse
Coming from you (I have read, and am quite thankful for, many of your posts), sounds like that might be the best option, however disconcerting.
bondidave said:
Coming from you (I have read, and am quite thankful for, many of your posts), sounds like that might be the best option, however disconcerting.
Click to expand...
Click to collapse
Well, I do have a few ideas... Got done questions though.
1. Do you have an external SD card?
2. It goes all the way through flash on 4.4 even with heimdall?
3. Is there anything you have left out? Even the smallest detail can help, and by the op you are detail oriented, so I just need to know.
Sent from my SM-G900T using Tapatalk
... is there a way of taking a full system image of my working phone and making an Odin-flashable tar from that?
Click to expand...
Click to collapse
Yes, but I don't have the details handy.
All your attempts suggest to me that you might have some damaged hardware which is causing data corruption during transfer. Open the back and take a good look at the USB port. Tighten the screws and try a transfer while firmly holding the cable in place -- don't move it while transferring.
If that doesn't work then let 'noobtoob' walk you through booting with the removable sdcard. Your second N900T will be needed to write the data to the sdcard. If this works then you can 'dd' write stock partitions to an sd card with #2 then 'dd' write them in #1.
If either of those works then unroot and take it in for warrenty exchange.
Frank
bondidave said:
... then (probably after one too many XPosed modules) it just kept rebooting randomly.
Click to expand...
Click to collapse
This also indicates data corruption, and this is what started it all. Since you have tried various cables and computers that leaves the device, probably the USB port.
Frank
probably the USB port.
Click to expand...
Click to collapse
Swapped the main board with the working phone to rule out the USB port - still no luck.
Definitely interested in trying the boot from external SD, I'll do my own search for it, unless you can quickly provide me with a link - but if it's as easy as it sounds (booting off of an SD in order to be able to send ADB commands to dd copy the partitions from the good phone to SD then from the booted SD back to internal) - I'm happy to give it a shot.
Tempted just to swing by TMO just to see if they'll swap it "under warranty" (despite picking it up from a private sale) - the only way they would notice it's been "tampered" with would be to check the knox counter by attempting to run download mode.
Oh, and yes, it does go all the way through with the flash (at least in Odin - I haven't tried a full flash through heimdall, just boot and recovery, Kies occasionally goes through to the end, but sometimes craps out at the same 57% point at which point the emergency restore screen shows up)
Thanks again guys
bondidave said:
Swapped the main board with the working phone to rule out the USB port - still no luck.
Click to expand...
Click to collapse
OK, but I still think the problem was initially caused by corruption. Maybe the files you have been flashing are corrupt.
Definitely interested in trying the boot from external SD, I'll do my own search for it, unless you can quickly provide me with a link - but if it's as easy as it sounds (booting off of an SD in order to be able to send ADB commands to dd copy the partitions from the good phone to SD then from the booted SD back to internal) - I'm happy to give it a shot.
Click to expand...
Click to collapse
This is the thread, it would be good to read the whole thing but if you need to save time begin at this message: http://forum.xda-developers.com/showpost.php?p=48685247&postcount=158
I have not tried this procedure yet but @noobtoob was actively involved in it.
Tempted just to swing by TMO just to see if they'll swap it "under warranty" (despite picking it up from a private sale) - the only way they would notice it's been "tampered" with would be to check the knox counter by attempting to run download mode.
Click to expand...
Click to collapse
Please try the SD-boot first so that we can add that experience to this newly developed procedure.
Oh, and yes, it does go all the way through with the flash (at least in Odin - I haven't tried a full flash through heimdall, just boot and recovery, Kies occasionally goes through to the end, but sometimes craps out at the same 57% point at which point the emergency restore screen shows up)
Click to expand...
Click to collapse
You have probably tried it, but if not, download fresh copies of everything and check the MD5 values.
Frank
Frank Westlake said:
OK, but I still think the problem was initially caused by corruption. Maybe the files you have been flashing are corrupt.
This is the thread, it would be good to read the whole thing but if you need to save time begin at this message: http://forum.xda-developers.com/showpost.php?p=48685247&postcount=158
I have not tried this procedure yet but @noobtoob was actively involved in it.
Please try the SD-boot first so that we can add that experience to this newly developed procedure.
You have probably tried it, but if not, download fresh copies of everything and check the MD5 values.
Frank
Click to expand...
Click to collapse
This was for hard brick method and no one has verified it works on 4.4 KK yet. There is an image in there though. My mediafire shows it was downloaded 11 times, but yet not a single "this works on KitKat" response. Located here you will find the kkunbrick.img. There is still a problem flashing anything through heimdall after updating to the 4.4 bootloader, so there is no way to tell if the phone actually took the recovery. I have had to switch to Odin for everything afterwards, and in personal experience 3.07 works best with my phone.
@bondidave I was thinking skipping the sd-card trick for now, and trying just a few other things first. Do you have a nandroid of any 4.4 ROMS saved anywhere? I was going to say try and flash the stock image. After it gets through flash and tries to boot into recovery, go back directly to download mode. Flash philz or twrp, whatever you need to. Try and perform a recovery boot, wipe everything, and nandroid restore of a 4.4 if you have one.
Also if you have an external find the efs fix zip and have handy on an sd-card, do the same steps above except the nandroid restore. Basically if we can get into a recovery we should be ok. I had a similar issue when it was just booting over and over into download mode and this was how I fixed it. I have never used the efs fix zip, but many others swear by it. I was able to recover fortunately enough.
Last resort try the sd-card boot. I don't necessarily think it will work with this particular case as you do not have the dreaded QHUSB_MODE and your phone is still recognized by the computer(s) you have been using.
As far as making a complete system backup of your current phone, I highly recommend against it, unless you just want to extract information from it and not re-write it. This could definitely cause some system corruption on a new device.
If none of these methods work, then try and have them swap it under warranty.
Frank Westlake said:
You have probably tried it, but if not, download fresh copies of everything and check the MD5 values
Click to expand...
Click to collapse
Yessirreeebobbyjimmy, tried several copies from several different places - that and Kies is a moron and redownloads it every time anyways.
noobtoob said:
My mediafire shows it was downloaded 11 times, but yet not a single "this works on KitKat" response.
Click to expand...
Click to collapse
I download these things just to have them handy if something fails.
Do you have a nandroid of any 4.4 ROMS saved anywhere? I was going to say try and flash the stock image. After it gets through flash and tries to boot into recovery, go back directly to download mode. Flash philz or twrp, whatever you need to. Try and perform a recovery boot, wipe everything, and nandroid restore of a 4.4 if you have one.
Click to expand...
Click to collapse
I don't think he got that far into installing 4.4, but I recommend not using anything that was saved after this problem began. If the problem was caused by corruption then the restore will reinstall the corruption.
Last resort try the sd-card boot. I don't necessarily think it will work with this particular case as you do not have the dreaded QHUSB_MODE and your phone is still recognized by the computer(s) you have been using.
Click to expand...
Click to collapse
If the problem is bad USB or other bad hardware causing corruption during transfer then the SD-card boot will get past that, then transferring the rest of the partitions by SD-card will continue to be corruption-free. He could then trade-in the phone.
But you are right -- he should try everything else before the SD-card boot. Because if something else succeeds then maybe the hardware is fine, and if he went immediately to SD-card boot he wouldn't know that.
Frank
Thanks for the advice guys - I'm going to try the backup from my other phone, then the efs fix, then the sd-card boot... I'll report back, wish me luck.
A nandroid previous failure, or a ROM install from external SD card was all I meant.
Sent from my SM-G900T using Tapatalk
I got some answers I was looking for here. Glad I read this thread.
Lorettaa said:
I got some answers I was looking for here. Glad I read this thread.
Click to expand...
Click to collapse
Glad something good came out of my frustration!
Here's a quick update: I've done everything but the boot from SD card with no luck (and actually thought I had hard(er?) bricked it for a while after trying to copy over a few images from the other phone - turns out it needed to stay with the battery out for at least 20 minutes).
Good news - walked into a TMO brick-and-mortar last night, showed the guy my endless bootloop, and a replacement is on its way to my house for an affordable $20 warranty service fee.
At this point, I'm thinking the internal flash memory is just bad - as a software engineer, I'm ok with chalking this one up to a hardware issue (as much as I was hoping that my first post on XDA would result in some new profound solution to a longstanding issue common to a few folks).
Oh well - new Note 3 on it's way, and a new S5 shortly behind it (didn't hold out much hope on TMO hooking me up, so I ordered an S5)... let the battle of the Samsungs begin!
Thanks again to you guys who helped out - and the whole XDA community in general, I am very grateful.
Finally you made it fix and enjoy the battle between your phones
Well, sucks it couldn't be fixed, but glad you got a replacement on the way. It pretty much sounded like the partitions were well over written before we attempted anything, but always worth a shot.
Sent from my SM-G900T using Tapatalk
Yes, but I don't have the details handy.
All your attempts suggest to me that you might have some damaged hardware which is causing data corruption during transfer. Open the back and take a good look at the USB port. Tighten the screws and try a transfer while firmly holding the cable in place -- don't move it while transferring. :good:

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. )

Categories

Resources