anyone getting hot (quick) reboots after installing the rooted stock rom via odin?
It has only happened once so far so maybe I'm getting paranoid but I really hope I didn't break anything. Could it be an app's fault?
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 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!!
I have a Verizon SCH-I605 Note 2. I rooted and unlocked the boot loader when it was on 4.1.2. I have since then flashed 4.3 Roms through TWRP and because of that, it didn't install KNOX at all.
I was having issues with the Bluetooth and WiFi radios recently. Randomly they would stop working and not turn on at all. The toggles would turn light green and act like they were gong to turn on but didnt. They just turned grey again. Then a few hours to a day later they would randomly work and turn on and work. Then randomly they wouldn't work again. I tried to see if there was a pattern to when they would stop working but there wasn't.
At first I thought it was an app that I had installed that was causing it. So I flashed the same and other roms after wiping "everything". That would seem to work for a while but soon it happened again. It even did it without installing any additional apps after flashing. I decided to flash the stock rooted 4.3 OTA. That didn't work either. I then decided to flash stock and unrooted 4.3 using mobile Odin and inject superuser and mobile Odin. Right of the bat WiFi and Bluetooth didn't work. I am ALMOST convinced that it is hardware related now. Any thoughts on what would be causing it?
Also when I flashed it stock and unrooted with mobile odin, It kept root but I lost TWRP. And when I boot into download mode, it doesn't show the KNOX counter line at all so i am assuming that it didnt install it. Is it possible to flash back stock to 4.1.2 with odin and then re root and unlock the boot loader? Or is there another way to get TWRP back?
Any help or feedback is greatly appreciated
Hi all,
I'm trying to help someone fix their S4 that won't boot past the Verizon logo. I had rooted the phone probably a year and half ago but I never put a custom recovery or rom on the phone, as they mostly wanted to be able to use adblock, greenify, etc. The phone has been degrading slowly, lots of "SD card has been removed" errors, and now it simply won't boot past the Verizon logo. I have tried to boot into the stock recovery and clear cache with no luck. I don't want to wipe data if I can avoid it for now.
I was wondering if someone could point me to the proper CWM or TeamWin file and the best way to install it. I'm not sure if a custom recovery will even help me get it booted at this point but I figure I might have a little more luck over using the stock recovery. Any advice is appreciated, thanks.
Do you know what the phone's baseband is? Chances are it's not MDK so that means to CWM, TWRP, etc. Take out the battery, put it back in and then boot to download mode then try and flash a new tar in Odin.
I don't unfortunately. I rooted it about 1.5-2 years ago. I don't remember quite well but I don't think it's been updated since, I think I froze the update notification whenever that started popping up.
Flashing it in Odin will erase all data, correct? I don't know if I have another choice at this point, just curious.
Sounds like you need to odin the stock tar. Reroot and proceede from there. Yes it will wipe user data.
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