Once I installed Crash rom. It worked ok but there was a few glitches so I decided I was going to install another rom and according to TWRP they install fine but won't get passed the boot screen and the phone starts to get hot
I'm not a pro but not a rockie either.
This also happened with my Samsung tablet. So with Odin I tried going back to stock rooted and it worked fine but as soon as it died my tablet is now completely unresponsive. Now I'm afraid that the same will happen with my phone. And I don't have enough $$$ to risk it
Thanks in advance and sorry if it's a stupid question
Sent from my SM-G925T using Tapatalk
Related
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
I bought a fascinate from good ol craiglist for a friend. When I bought it I noticed the original user had already rooted it and installed CM7.
Because I didnt know what he had done to it I decided to start from scratch and used Odin and flashed powerwashed_20_b3_Full_ec09modem and the atlas_v2.2.2.pit
After that I flashed cwm4_fixed_for_cm7-ODIN.tar and began getting ICS on this baby (teamhacksung-ota-eng.BUILD2.zip followed by build 11 at the time).
Everything was gravy and I gave the phone to my friend who was a happy panda. Several weeks later he calls and tells me the phone is stuck in recovery, I assume he borked something so I headed over thinking I will just Nandroid the ICS ROM that I set up before I gave it to him.
Funny thing was after rebooting from the Nandroid, the phone goes back to recovery! I was a little confused but assumed that maybe the Nandroid went bad when I backed it up. So I decided to just reflash build 11 again, after the flash was successful i reboot and.... back to recovery?
At this point I was pretty confused, CWM appeared to be working but it wasnt. Nothing was working, not even flashing CM7. The only way I got it to work again was to Odin the powerwashed_20_b3_Full_ec09modem and the atlas_v2.2.2.pit again. So that was what I did and got him back to ICS (build 13 this time).
Thinking it was a freak occurence I didnt pay it any mind, until he called me again several weeks later saying its stuck in CWM again!? So I check it out and sure enough it keeps booting to recovery and not able to nandroid or flash anything (even tho it says it does successfully).
At this point I assume its a hardware issue but dont understand what exactly, I bought another on craiglist and will swap with him and further investigate the issue.
I looked around the forums to see if anyone had a similar issue but have not seen anything like this. Anyone have any ideas??
This is most likely caused by doing the three finger reboot on the newer ICS roms. Tell them to pull the battery instead the next time their phone locks up. Also, there is boot loop breaker in the development section.
Sent from my SCH-I500 using xda premium
I assumed that as well, however my friend has no experience with these devices and would never hold down all three buttons for any reason. Both times he had reported that the phone randomly went into recovery on its own.
He could be BSing me of course, but I'll be testing it when I get it back tomorrow and see if I can recreate the scenario.
But I will be including the boot loop breaker file in the SD card and see if that at least makes this phone usable again instead of having to use ODIN every time. So thanks for that info!
Check kernel settings. Sleep Of Death, maybe?
I have been trying to update my S4 (vruame7) to the latest. I'm willing to lose root. The issue I'm having though is one that NOBODY seems to have mentioned anywhere: It started where I couldn't update over the air as the update fails. So I tried to update it with Kies on my mac but the program says I need more memory on my phone even though I already have it. This prompted me to unroot my phone and do the update again, but the issue is still there. So I tried booting into recovery and that worked. I decided then to reboot my phone and add CWM touch via ROM toolbox Pro. It said it worked fine, but now I cannot boot into the recovery mode. It just goes straight into ODIN mode and it won't prompt me to confirm it or not. I get into a very soft boot loop if I try and reboot though Rom Toolbox Pro to go into the recovery. I will land in ODIN and then unless I tell the phone manually to go into ODIN and then NOT proceed than it will be in a soft boot loop. So far I've tried unrooting and using Kies, Rooting and trying to load CWM onto my phone and failing, causing OTA to not be able to even start installing, and I've yet tried to go into safe mode and try to reset my phone that way. I might have to do that. if anyone has any other ideas I am open to that.
Your on me7 so you half to use safestrap that's the on way you can have a recover...... You probably half to Odin your phone back to me7 for the update to work. You can't use cwm or twrp on me7, unless u have safetrap installed and the its a version of twrp in it
hyperdrive powered s4
ebsk8er06 said:
Your on me7 so you half to use safestrap that's the on way you can have a recover...... You probably half to Odin your phone back to me7 for the update to work. You can't use cwm or twrp on me7, unless u have safetrap installed and the its a version of twrp in it
hyperdrive powered s4
Click to expand...
Click to collapse
Thanks. I've got safestrap installed sucessfully (it was so easy), and I'm now trying to install the update by wiping my phone and then doing it. I'll see if that works.
Well, it looks like I may have wiped my phone too far as I'm stuck at the Samsung custom logo and It's not booting farther. i can get into odin but I have a mac, so what do I do?
beez1717 said:
Well, it looks like I may have wiped my phone too far as I'm stuck at the Samsung custom logo and It's not booting farther. i can get into odin but I have a mac, so what do I do?
Click to expand...
Click to collapse
Heimdall is like odin but its mac.compatible
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
Use oden or Heimdall (guess its a Mac thing) to flash back to stock and then you can take the update. You haven't bricked yet but it sounds like you are getting close so be careful.
beez1717 said:
Well, it looks like I may have wiped my phone too far as I'm stuck at the Samsung custom logo and It's not booting farther. i can get into odin but I have a mac, so what do I do?
Click to expand...
Click to collapse
Sounds like you did a full wipe on non safe side "stock rom" of safestrap so your gonna have to flash a whole factory image cause it all gone the whole os
So after working for hoursx and hours, of working at it, I finally found http://sonofgeektalk.wordpress.com/2013/06/13/heimdall-on-a-mac/ <-- that webpage and it helped walk me through using Helmdall and it worked after much fiddling and discovering that I had to plug in my phone AFTER it got into odin but BEFORE I confirmed I wanted to be in odin. I then had to not wipe the phone clean but just do the install with the right files. It worked and I'm so happy. Now to see if I can update the darn phone. Don't know if I can or not but hey, I've got my phone back up and running and that's a GOOD thing.
I don't care about root as much as I care about getting the latest software if it provides enhancements I like, or security features I want. I think that root is fun, but it can be a pain in the butt as I just saw. Now that I know how to do the whole shtick, I should be able to do a lot more with my phone. I remember when I had to learn the ins and outs of my old Xperia Play. Horrible battery life and sub-par graphics chip but an awesome phone that had an awesome utility that could do just about anything with the phone with minimal work.
Looks like the system is updating itself just fine using OTA. What a LONG workaround I had to do. Thank you all for helping me teach myself a lot more about my phone
I'm having trouble trying to update as well. I unrooted and did a factory reset but the update still fails. What should I be trying?
Sent from my SCH-I545 using xda app-developers app
beez1717 said:
So after working for hoursx and hours, of working at it, I finally found http://sonofgeektalk.wordpress.com/2013/06/13/heimdall-on-a-mac/ <-- that webpage and it helped walk me through using Helmdall and it worked after much fiddling and discovering that I had to plug in my phone AFTER it got into odin but BEFORE I confirmed I wanted to be in odin. I then had to not wipe the phone clean but just do the install with the right files. It worked and I'm so happy. Now to see if I can update the darn phone. Don't know if I can or not but hey, I've got my phone back up and running and that's a GOOD thing.
I don't care about root as much as I care about getting the latest software if it provides enhancements I like, or security features I want. I think that root is fun, but it can be a pain in the butt as I just saw. Now that I know how to do the whole shtick, I should be able to do a lot more with my phone. I remember when I had to learn the ins and outs of my old Xperia Play. Horrible battery life and sub-par graphics chip but an awesome phone that had an awesome utility that could do just about anything with the phone with minimal work.
Click to expand...
Click to collapse
I think the problem here was that you tried to take an official update AFTER you messed with your phone... you should take this as a lesson to always flash back to stock before trying any 'official' updates, or better yet just have some patience for the updated files to show up here on the forums so you don't have to deal with OTAs at all. I don't really see the big rush to get the newest MI1 update anyway, it really doesn't provide any huge benefits at all and plus will possibly void your warranty through that stupid Knox thing if you try to root.
One thing I've learned is use patients dont jump the gun and if your not sure before you do something look here cause someone has already screwed up so the right way will be here somewhere and video will be on youtube!!
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:
A couple of weeks ago I bought a Galaxy Note 2 from Simple Mobile began to experiment with it. Later on I managed to root it, but I accidentally flashed a recovery via Rom Manager which after a restart broke my phone.
After that I flashed a OTA through Odin of Verizon 4.1.2. The system booted and everything but the radio was missing meaning that I could not text or use 3G. I looked for many ways to restore it but none worked.
I later on flashed a T-Mobile ROM thinking it will help restore the radio and it did successfully flash the ROM through the recovery. But the ROM turned out to be 4.3 and the radio still didn't work. Later on in the same day I flashed an OTA of T-Mobile through Odin and that's when this happened. My phone bootloops really fast when I turn it on. The recovery doesn't show up at all. And every time I flash anything through Odin it fails. I've felt ashamed all this time and it took me a while to reflect and face what I've done and decided to post on here to get help.
Thanks for reading! Any help is appreciated. I will try every method that gets posted and will post back results.
Chronosin said:
A couple of weeks ago I bought a Galaxy Note 2 from Boost Mobile began to experiment with it. Later on I managed to root it, but I accidentally flashed a recovery via Rom Manager which after a restart broke my phone.
After that I flashed a OTA through Odin of Verizon 4.1.2. The system booted and everything but the radio was missing meaning that I could not text or use 3G. I looked for many ways to restore it but none worked.
I later on flashed a T-Mobile ROM thinking it will help restore the radio and it did successfully flash the ROM through the recovery. But the ROM turned out to be 4.3 and the radio still didn't work. Later on in the same day I flashed an OTA of T-Mobile through Odin and that's when this happened. My phone bootloops really fast when I turn it on. The recovery doesn't show up at all. And every time I flash anything through Odin it fails. I've felt ashamed all this time and it took me a while to reflect and face what I've done and decided to post on here to get help.
Thanks for reading! Any help is appreciated. I will try every method that gets posted and will post back results.
Click to expand...
Click to collapse
I have a very similar problem. hope you get help on this, I have been trying to fix this problem for a month.
The 4.3 update is where the issue came from if it will allow you to flash try using a custom rom to get you out the boot loop but because the 4.3 bootloader is locked you now have another issue you will now have to run a virtual rom and there is a certain way you have to do it or you will completely brick your phone try researching first Google your phone model with the rom build 4.3 root you have to root it now before you can do any modifications at this point
Sent from my SCH-I605 using XDA Free mobile app