Alright So I am new to this forum but Im not new to the scene. I cant figure this problem out after days of searching and restoring. So I just got my note last week been loving it coming from my old 4s. Anyways My problem is I did a fresh factory restore rooted with dags kernel (tried both stock root and Oc kernel). I have clockwork recovery installed btw. So usually everything goes smooth. I clear all caches phone boots up runs smooth, I install root then my basic apps. Now I was doing them one by one and restarting.
Well long story short. At random any one of these times I reboot the device I come back into the lock screen Ill unlock and it force closes everything and just keeps rerunning media scanner looping. (force close twlauncher calenders google sync etc like really anything usually its twlauncher thats first I click ok it goes back to lock screen freezes for a second then reboots media scanner. It doesnt find service or even attempt it. The only thing I can do is restore and try again. I have done this over 10 times just this past week. I have fixed permissions in both rom manager and clockwork. Though it was good until last night it just completely restarted on its own and when I booted back up it was force closing.
I even did a fresh format wiped everything reinstalled stock att unrooted Rom then rooted and I have to be afraid of my phone dying or just randomly crashing and that when I restart its not gonna make it back into gingerbread without a restore. Now this will happen whether I have no apps or some apps. I can seem to find anything triggering it. Is this a defect in the phone maybe? Should I restore to stock and exchange at at&t or am I missing something? Please help guys. Ive only been able to get about a day before everything force closes. And that is unacceptable for an 700 dollar phone when all these others are running smooth.
Did you happen to mess with any overclock values? I had the problem you explain only after I overclocked to much and it was unstable
Solution: put into download mode and flash back to total stock with odin and start over. It worked for me. Restoring backup did not work
Sent from my SGH-I717R using Tapatalk
It is a problem with CWM. You should look for and download darkside super wipe. If I were you I would probably flash the stock Odin tar and start fresh. Make sure you install the latest CWM.. I believe beta4. You should not have to reboot your phone after every new app install.
Use the super wipe from in CWM (install from zip) and then use Odin to get back to stock.
You most likely have an older version of the CWM, I don't think anyone has reported any problems with beta 4 and force closing issues.
I have CWM 5.0.2.7 on here. I dont have to restart everytime I install. I was doing it to see if there was a certain app triggering it thats all. Cuz if the phone goes off and reboots to lockscreen thats when the FC happens. It never happens while Im actually in use. First time this happened it was stock clock speed and its happened whether its 1.83 or 1.56 or stock rooted rom. And I had tried both restarting stock att rom with bloat and from my first backup after odin root.
Where do i find beta 4? I originally got this cwm from rootgalaxynote.com
Nevermind I found it I pulled a n00b. Ok Imma give that a try right now I see this is older version so HOPEFULLY thats it. Thanks a bunch Ill check back in after to let you know. Pretty crazy in the back of my mind I felt like CWM was the only thing I didnt check out.
Stuck in firmware upgrade encountered an issue. I cant do anything Odin wont write the stock firmware back on after wipe. What do I do? No cwm or anything phone just boots to telling me to restore with kies?
h3r3tic said:
I have CWM 5.0.2.7 on here. I dont have to restart everytime I install. I was doing it to see if there was a certain app triggering it thats all. Cuz if the phone goes off and reboots to lockscreen thats when the FC happens. It never happens while Im actually in use. First time this happened it was stock clock speed and its happened whether its 1.83 or 1.56 or stock rooted rom. And I had tried both restarting stock att rom with bloat and from my first backup after odin root.
Where do i find beta 4? I originally got this cwm from rootgalaxynote.com
Nevermind I found it I pulled a n00b. Ok Imma give that a try right now I see this is older version so HOPEFULLY thats it. Thanks a bunch Ill check back in after to let you know. Pretty crazy in the back of my mind I felt like CWM was the only thing I didnt check out.
Click to expand...
Click to collapse
The version of CWM you were using was most likely for the international Note and therefore incompatible with the Note you have.
---------- Post added at 09:03 PM ---------- Previous post was at 09:00 PM ----------
h3r3tic said:
Stuck in firmware upgrade encountered an issue. I cant do anything Odin wont write the stock firmware back on after wipe. What do I do? No cwm or anything phone just boots to telling me to restore with kies?
Click to expand...
Click to collapse
You may want to join the IRC channel and see if anyone there can offer you a solution.
irc.irondust.net
#attgalaxynote
Just for Clarification
I too had the TwLauncher issue and tried clearing the Dalvik cache, cache, etc. This then sent me into a boot loop into recovery. (My CWM is the 5.0...version too). Tried the restore, no luck, wipe, no luck etc.
My PC doesn't see the phone, so I need to basically start the root process over again and install the Beta4 CWM. Am I understanding correctly?
I have the same problem and its driving me crazy. Can some one please help me out step by step Im new to this any help would be gratefully appreciated
Related
very odd ... nandroid restore i have a feeling its gonna be
Well good luck with a nandroid if it's voodoo.
As a last resort...
theres a "Odin Restore files to get you to stock - xda-developers" thread, sorry can't link yet but yeah you can find that one easily
try wiping and see what happens
Clearing delvik cache normally helps with force closes in my experiences with clockwork and android.
Sent from my SPH-D700 using XDA App
So basically I factory restored and I'm doing okay now. I tried to go into clockwork recovery and restore my latest backup and I just get the force closes again but I'm safe to assume I do not have root currently so should I re root them try to restore my backup?
Did you flash a regular kernel over voodoo without disabling?
Same Problem.
I had this problem. Unfortunatly I did not have a backup, no biggie for me. I had to restore to stock using ODIN, then wipe data and had a brand new phone. I attribute it to the fact that I started changing Kernals more than my underware. After re-rooting I am ready to start flashing Kernals again, which means I will more than likely be restoring to factory again..... Maybe I should back-up current ROM. Oh, and I did flsh a ROM over Voodoo, don't do that.
well i have a backup but yes i tried to flash the 1200 zip over a deodexed system with voodoo lag fix ON so im guessing i shouldnt of done that. im getting super slow boots and still a **** load of force closes ... so im thinking the odin fix and starting fresh is the way to go for me.
so i flashed the restore through odin and i think im okay ... normal boot time and everything seems to be working fine ... had to format my SD card and everything. im gonna reroot and start everything over .. wish me luck!! haha
EDIT: well i spoke too soon im not getting any cell service on my device now hmm
EDIT: nevermind i do have service google just isnt connecting hmm this is ****ty
I just want to stress out how important it is to read every single word in the instructions and follow every single word....please check the stickied thread at top on how to install voodoo kernels...it has all the links you need....but seriously, many people have flashed tons of kernels and did many changes without a single hiccup... If things went wrong, then you misses an important step.
tats_06 said:
I just want to stress out how important it is to read every single word in the instructions and follow every single word....please check the stickied thread at top on how to install voodoo kernels...it has all the links you need....but seriously, many people have flashed tons of kernels and did many changes without a single hiccup... If things went wrong, then you misses an important step.
Click to expand...
Click to collapse
+1
Sent from my SCH-I500 using XDA App
I followed everything and when I disabled it, like have 15 times before, it just got caught in a bootloop and I had to restore yesterday. I think the voodoo fix we have now is just really touchy.
Same deal with mine
I've been swapping the voodoo kernels like crazy the last couple days and just found JT's "1200_interactive_bfq". Figuring I was running voodoo kernels and not that bogus lagfix junk, I used CWM and loaded JT's kernel. When it booted I got tons of the force closes and was unable to absolutely anything with the phone. Here's the simple way I got mine back to operating...
-Shut off phone
-Hold down volume key while powering up to get into factory boot loader mode.
-Once in, run update.zip to get into CWM
-Once in CWM installed the last voodoo kernel I had been running and rebooted the phone.
-Good as gold.
Now...in order to install the new JT interactive kernel do I have to disable the voodoo kernel or do I have to go back to a stock kernel first?
~Johnny
Although I only had the phone for a day now, I've been reading the forum for a month trying to get the info I needed so that when it arrived, I'd be able to load up froyo, wifi calling and be done quickly. I set it all up and downloaded ryan's OCLF, ran it, rooted, installed the ext files, then the v2 lag fix it said to. Everything was great.
Later I downloaded a few apps and titanium backup, but didn't back up yet. I ran the battery down low. Went into the clockwork app that I downloaded and did a backup restore.
About an hour later the battery finally died. I read that you should turn it on until it won't anymore before finally plugging in to charge and wiping the battery settings. Problem is it wouldn't boot up again. Hung on the Galaxy S screen with the shining S.
I could still reboot into recovery and into download. Was going to ODIN back, but my PC was giving me trouble. I pulled the micro sim and thre the ASOP 2.2 rom on it from another laptop dragged it to card removed and popped it back in. I tried to reboot to recovery which worked, then reinstall, nothing. Tried to get to the SD card, but it doesn't find it.
Finally gave up and went back into recovery and did a factory data wipe reset or whatever it is called. When the phone rebooted it all booted fine, no problems at all however I lost every setting account etc..
So here's where I'm at now, i mounted it as USB and looked at the phone from the PC, in the clockwork folder is my backup I just can't get it to load.
I went back to the market and redownloaded the ryan OCLF and removed the lag, ext and root and I'm back to stock. Phone will turn off and back on.
What now? Where did I go wrong, it doesn't make any sense, I followed every instruction exactly as it was written.
I'm a little concerned to root again, but I want to backup settings, accounts etc.. in case this happens again.
first...welcome to XDA...the baddest forum on the planet...
second....this is the wrong section for this topic....should be in Q & A section...but a Mod will take care of that....
third....read this.....http://forum.xda-developers.com/showthread.php?t=849028
the author worked hard on this to become a sticky so noobs will see it first...if u need more info....there is another sticky in the general section...good luck!!
Thanks, I'll read through it now. I thought I had a good idea to drag the new rom to the sd card and fire it up from there, but it failed. Happy I didn't brick the phone. I saw a lot of posts saying ODIN was the only way back, guess I got lucky with the data wipe.
I've had iphones for 2 years and when this happened it would be a conflict with programs, is there a list like that for android like there was for cydia in the iphone info?
I don't know.... but make sure you read carefully before you flash... in a nutshell the steps for ROM flashing is.
1. Root
2. Download and install ROM Manager from market
3. Flask clockwordmod recovery
4. Nandroid (backup)
5. Backup SD card to pc(just in case)
6. Flash your ROM from clockworkmod recovery.
Sent from my XDA app cuz I'm stalking your mom....
Here's a question I don't think is answered after reading the post. So rooting via OCLF without installing the lag fix v2 is exactly the same as rooting by dragging and dropping.
Rooting in itself can't cause the phone to not reboot, but if you flash incorrectly or apply lag fix and flash over them you could run into trouble. I just can't seem to figure out where the error was. I didn't delete the update zip after rooting, thats the only error I see.
Other issue I noticed is that on mounting to USB after booted I can see the backups, but I can't locate the ROM zip I put on the SD card or the SD card at all.
So let me get this straight... you rooted via OCLF.. but did not apply the lagfix?
Edit: oh I see... u tried to flash a froyo Rom then go back to stock?...
Sent from my XDA app cuz I'm stalking your mom....
No I rooted then applied the lag fix it had available which was version two I believe
Sent from my SGH-T959 using XDA App
Ok... try ODIN back to stock...make sure you have the correct drivers
Sent from my XDA app cuz I'm stalking your mom....
Let me correct what I'm saying, the phone went into the stuck glowing S screen when trying to turn it back on after I ran the battery down to nothing. It wouldn't boot past that point. I tried reinstall, reboot, etc..from the menu in clockwork recov in recov screen as that was all i could get to. When that failed I tried just loading a 2.2 ROM to the sd card direct from my laptop, thought I could just flash from that screen right over everything, didn't work either. Thats when I tried delete all info as a last effort, but then it magically booted back 100% stock, but still rooted. So i reloaded OCLF and unrooted because I don't know what caused the phone to be stuck in the S screen, I didn't flash anything, just did the root and oclf all from ryan's OCLF app
I tried to reroot manual, didn't work, lots of issues, wouldnt root. Went back for OCLF gone. Went for the z4 gone. Found links for both, tried the z4 didnt' work, superuser continiously popping up for permissions, went back removed that and reloaded oclf from web, ran and fixed boot and rerooted, all good. Went back and downloaded and flashed Vibrant AOSP ish JK2 1.1 Official FROYO. Absolutely love it so far. I've been waiting for wifi calling for a long time, it actually works. Problem is I'm not really sure if I rebackup everything now or leave the backups I have from clockwork for stock. I keep reading everything and feel like I'm missing something. I have Vibrant AOSP ish JK2 1.1 Official FROYO saved so I guess if it crashes I just reflash that and don't need a backup, but should titanium backup the whole thing instead now? Sorry if no one replies i get it. Two years of iphone jailbreaking is a waste, nothing like this at all! I will say I never bricked an iphone, feel like i'm gonna brick this thing.
I want to run the OCLF v2, but concerned it's going to cause issues as it's running so smooth right now.
It works fine
Sent from my SGH-T959 using XDA App
version 2 isn't an option, i'm running lag fix one, seems ok I'm having some other issues, but its running
If your still having problems odin back to stock and start over it always safer and will cause less problems
Sent from my SGH-T959 using XDA App
All my issues were because busy box was messed up, all good now
Sent from my SGH-T959 using XDA App
Just to throw it in there... you should always backup your current ROM and all apps using both ROM Manager AND Titanium Backup. It makes it THAT much easier if you do, by chance, have to use ODIN or run a recover, to get your settings, apps, saved data, etc. back without much hassle.
I run a Titanium backup on all of my apps I have loaded (NOT SYSTEM APPS as they are backed up by ROM manager I believe) once a month or so, just to keep fairly recent. It makes it to where, if it does need to be restored, the apps all get re-installed at once including saved data within the app (saved game progress, etc.). This is handy because you don't have to remember what all you had installed and you don't have to go searching through marketplace to get those apps back.
If you are running a custom homescreen (Launcher Pro, etc.), you should also use their backup option to save your homescreen settings.
In short, backup everything you can... it makes 3 hours worth of reloading things condense into a nice little 10-15min "install", "ok" button pressing fiesta!
And, to let you know, I've (as just about 100% of XDA users) flashed, and ODIN'd nearly a thousand times and have yet to brick a phone. These things are crazy indestructible. There's 3 or 4 different ways to get into Download Mode if you get the computer!phone screen... so don't worry about it. The only thing you really lose is time spent getting things back to normal if you screw up. But read up on everything, which it sounds like you already do, before you even attempt anything that could kill the phone. I don't post much on here because just about everything is already answered... you just have to search a little bit.
So I updated to the newest software MI5. Went from that and did the root which was sucessfully. I had put on OUDHS Touch CWM-based Recovery thru ODIN which was sucessful as well. After doing all of that, I downloaded Josh Beach's Jellybomb test rom. The steps I did was booted into recovery which is the one above, factory data reset, wiped cache, and wiped dalvik, then flashed the zip. The zip looked to flash ok but when i went to reboot, it just keeps getting stuck at the samsung galaxy note 3 screen, then it will reboot then go to the same screen. Did I do something incorrect? This happened to me on this ROM and the stock MI5 ROM rooted.
Might want to read through this thread...
http://forum.xda-developers.com/showthread.php?t=2473036
Process system isn't responding
Sent from my Note 3 on Android
runner77 said:
Might want to read through this thread...
http://forum.xda-developers.com/showthread.php?t=2473036
Process system isn't responding
Sent from my Note 3 on Android
Click to expand...
Click to collapse
so it sounds like i cant flash any custom roms right now? Just odin back to stock and root it and leave it at that?
this probably wont help for this particular problem, or maybe it will.. but for anyone else getting a bootloop..
i just now had a bootloop experience that i got out of.. and here's how it started - i have not rooted my note 3 (i have rooted my galaxy gear though, but i don't think that would affect the note 3).. anyway, i use the nova launcher as my main launcher.. and just before i got stuck in a loop, i had been playing with a new launcher called Themer... i just started it without setting it as default.. then i went back to my main launcher and i noticed that almost all ram was used up and i thought i might as well do a restart as it has been a while... and then it just would not start.. i got to the lock screen image, and then it would restart again and again, with no sound for the animated logo.... it eventually booted up ok, but i have no idea how i got it to work... however, i held down the power button for a while longer and it would "force" a new restart and basically abort the one already in progress, and if i did that, the boot up sound would come back... i continued doing that a couple of items and then it finally worked.
use twrp or phones as of right now dont like cwm recovery...found this out the hard way
odin back to stock rom non root wipe phone using default recovery odin back to stock again root your phone use twrp to flash whatever rom u want
lunchboxVA said:
use twrp or phones as of right now dont like cwm recovery...found this out the hard way
odin back to stock rom non root wipe phone using default recovery odin back to stock again root your phone use twrp to flash whatever rom u want
Click to expand...
Click to collapse
And when flashing make sure to wipe dalvik/caché several times for good measure.
Sent from my SM-N900P using Tapatalk
checking in to add that i found a new solution to my own problem here.... it "magically" started the last time just by me keeping on rebooting.. but that's not really a good solution and i don't think it lasts
and for me it didn't... as today i did a new restart, and it got the same stuck in a loop again, however, i followed the first mentioned workaround in this link here and it worked perfectly.. it was really that simple in my case it seems, i have done several restarts now and the bootloop is gone!...
oops, seems i cant post any links for not having enough posts yet...
i'll just add the steps mentioned instead
1 . Remove the battery and the SD card.
2. Put the battery back in and turn on the device.
3. Try Menu > Settings > Wi-Fi > Menu > Advanced and uncheck Always allow scanning.
4. Now you should be able to turn the device off and reinsert the SD card.
5. Boot it up and your problem might be gone
i have no idea how it works though as i personally don't understand the connection between then external sd card and the setting you turn off in the wifi advanced options..
cheers!
So ,im sorry but its a long story. Hopefully someone can help. My note is Rooted Ive been using TWRP. Everything had been fine until 2 days ago. I tried flashing a ROM i found on Goomanger.( I had been running liquid smooth) just wanted to try something different. Anyways it got stuck on a boot loop. Cant remember the name of the Rom. Anyways i was able to get back to recovery, thankfully. But when i wiped and flashed back to liquid smooth it would say optimizing apps, then it would reach a certain number then reboot and star all over again. So then i tried another Rom and the same thing happened. tried flashing back to stock rooted but it would turn on then completely crash and star booting up again. So finally i was able to flash paraandroid 4.1.2 and Gapps, but here is the kicker i have no service (AT&T) says cannot locate network, my IMEI is gone basically the cellular isn't working. Everything else works fine WiFi,apps, camera. Just cant make calls. I really need your guys help please.:crying:
If you have a suggestion please let me know, i hate using an old Iphone
dar101978 said:
So ,im sorry but its a long story. Hopefully someone can help. My note is Rooted Ive been using TWRP. Everything had been fine until 2 days ago. I tried flashing a ROM i found on Goomanger.( I had been running liquid smooth) just wanted to try something different. Anyways it got stuck on a boot loop. Cant remember the name of the Rom. Anyways i was able to get back to recovery, thankfully. But when i wiped and flashed back to liquid smooth it would say optimizing apps, then it would reach a certain number then reboot and star all over again. So then i tried another Rom and the same thing happened. tried flashing back to stock rooted but it would turn on then completely crash and star booting up again. So finally i was able to flash paraandroid 4.1.2 and Gapps, but here is the kicker i have no service (AT&T) says cannot locate network, my IMEI is gone basically the cellular isn't working. Everything else works fine WiFi,apps, camera. Just cant make calls. I really need your guys help please.:crying:
If you have a suggestion please let me know, i hate using an old Iphone
Click to expand...
Click to collapse
Just odin back to stock. Get a complete factory stock image from the main sticky thread and flash it with Odin and Download Mode. There's a bug on one of the TWRP versions with 4.3-based ROMs that will put it into a bootloop by breaking device reboots. I was unable to flash my way out of the problem and was forced to do a complete reimage which solved all the problems and put me right back to clean-out-of-the-box state, then I reinstalled TWRP (though an older version before the boot loop bug) and re-flashed my custom ROM. The package I used was the stock image and Odin tool all in one .exe, just plug in to download mode and run it and it flashed bootloader, recovery, system, kernel, etc. all back to stock.
CalcProgrammer1 said:
Just odin back to stock. Get a complete factory stock image from the main sticky thread and flash it with Odin and Download Mode. There's a bug on one of the TWRP versions with 4.3-based ROMs that will put it into a bootloop by breaking device reboots. I was unable to flash my way out of the problem and was forced to do a complete reimage which solved all the problems and put me right back to clean-out-of-the-box state, then I reinstalled TWRP (though an older version before the boot loop bug) and re-flashed my custom ROM. The package I used was the stock image and Odin tool all in one .exe, just plug in to download mode and run it and it flashed bootloader, recovery, system, kernel, etc. all back to stock.
Click to expand...
Click to collapse
Thanks thats what i did, I just basically had to use KIES to use the emergency recovery, then root my phone again. My question is what version of TWRP causes this? cause i used the newest version i could find off GOO. My other concerne is, will it accept or be safe to use a custom ROM? Well i gues ill find out :laugh: THANKS AGAIN!
Everyone with the sgh-i717 is having problems with the latest TWRP and the most stable version is 2.5.0.0. Go with that one or you'll be starting all over again I imagine. And don't just stop at the download link in the OP's, read the thread and find out what's going on. The problems with TWRP have been going on for a while and the development threads have a lot of comments about the latest build causing problems. Good luck! :good:
So I was having an issue with an older version of fre ROM where the screen wouldn't turn on. Usually I could just do a battery pull and reboot and that would fix it. Recently it got worse where the screen would be blank even after a battery pull, you could hear the device booting as well as vibrate upon turning on but the screen was just blank and unresponsive. I figured out that I could boot download mode first and reboot from there and that would fix the problem on the first try. Today my screen turned off and nothing would fix it: rebooting phone, trying to boot into recovery, booting into download mode, nothing.
So I get home and charge the phone hoping I would be able to run ODIN without the screen being visible. Thankfully after about an hour on the charger I was able to get the phone to finally boot with the screen on, lol. Figuring this was a sign that I should stop being lazy I ODIN'ed Android 4.4, ODIN'd TWRP recovery, then did a full install of the latest fre rom. When the phone booted and Android finished updating everything was set up exactly the way it was before I started the process.
My noob question is this: how does Android remember all your settings and apps even after doing a full wipe through ODIN? I mean I didn't even have to log into Google or anything. Does ODIN not fully wipe the phone like it did back in the day?
Thats weird. At the very least you should have had to log back in with Google acct. Odin should wipe everything. Ive heard of it wiping ext sd card on some devices.
Real_JESRadio said:
Thats weird. At the very least you should have had to log back in with Google acct. Odin should wipe everything. Ive heard of it wiping ext sd card on some devices.
Click to expand...
Click to collapse
Yeah I know. I remember it happened the last time I ODIN'd too. Not that I'm complaining, it makes life way easier, but I wish I knew how to get a complete wipe for future use. Maybe I need to check reformat if I want to get full wipe.
1greek4u said:
Yeah I know. I remember it happened the last time I ODIN'd too. Not that I'm complaining, it makes life way easier, but I wish I knew how to get a complete wipe for future use. Maybe I need to check reformat if I want to get full wipe.
Click to expand...
Click to collapse
What version of Odin are you using? I've had the best luck on 1.85
Real_JESRadio said:
What version of Odin are you using? I've had the best luck on 1.85
Click to expand...
Click to collapse
I used 3.09. I have no problems flashing. I'm on the new version of Android that I flashed. It's just when I start up the phone my desktop is setup exactly the way it was and all the apps I already had are either already on the phone or download/update themselves. I never even have to log into Google or re-enter passwords for facebook, pandora, wifi, etc. Maybe it's a feature of fre ROM or something but I find it weird that it would remember all that considering I used ODIN with stock 4.4.4 before I flashed fre ROM. Where would that information even get stored?
1greek4u said:
I used 3.09. I have no problems flashing. I'm on the new version of Android that I flashed. It's just when I start up the phone my desktop is setup exactly the way it was and all the apps I already had are either already on the phone or download/update themselves. I never even have to log into Google or re-enter passwords for facebook, pandora, wifi, etc. Maybe it's a feature of fre ROM or something but I find it weird that it would remember all that considering I used ODIN with stock 4.4.4 before I flashed fre ROM. Where would that information even get stored?
Click to expand...
Click to collapse
No way you are getting a full clean wipe then. Search Odin v 1.85 here on XDA and try that. On my Note 3 i Odin d back to 4.4.2 rerooted and installed Philz recovery. Solved almost all issues i was having. My phone did not like NH7 4.4.4. Supposed to be an update coming December early to fix those issues but i just grabbed a Note 4