I had android 4.4 Omnirom on my phone earlier today and yesterday. Today there was an update for the nightly. I decided to download it and updated through the recovery as a normal update would've. However, after waiting for almost an hour for the android is upgrading prompt to go away, I figured it was stuck in a boot loop. Well it turns out it more than likely was so don't say I'm impatient :d. So I forced it to shut down and it rebooted, but it didn't get past the Omni logo for almost an hour as well. So I decided to downgrade to the previous nightly. That didn't fix anything. After that, I tried to restore to cm 10.2 but it wouldn't let me for some reason. So I figured I was screwed. I downloaded Odin and attempted to restore to the stock rom. Well, Odin failed. So I was literally desperate and out of nowhere decided to try to downgrade the kernel. I attempted a downgrade to AJK 4.9 mic swap and it worked. So I installed MIUI after that (I'm too lazy to try adb) and it loaded up fine. I was so happy that at least something worked. After that I noticed the back and search buttons were not functioning. I decided to restore to cm 10.2 and it worked. Everything SEEMS fine but I'm not too sure if everything is. Can anyone tell me if my process is correct? Or if I messed up everything
Thanks!
I had to wipe the caches after i flashed the nightly to get it to boot.
The CM nightlies didnt work for me either. Something about the build.prop in Omni calling my phone both the ATT and ST version of the phone. I did what you did. Flashed AJ 4.7 i had, rebooted the Recovery, and Nandroid restored.
I liked Omni and ill be back but that battery life right now Ugh. Good luck Entropy and Co!
Related
Hello XDA Dev. I, Azeem, come to you guys with a problem and I need you all's help on solving it. Here's the story.
I was previously on Cyanogenmod 10.1.3 Stable for my phone and decided to try out the new 9-28 nightly of CM 10.2. However, when installing the rom, I rebooted in to recovery after installing it, gapps 4.3, and ajk 4.9 AOSP, but it got stuck at the Samsung logo and I could not enter recovery mode anymore nor could I boot to the homescreen. Knowing using odin to go back to stock would fix the issue, I did just that, and booted to the homescreen. Btw, I odined back to ICS 4.0.4 since I couldn't find an Odin-able tar file for Jellybean UCMD8 (if you know of any, please tell and link it to me). Anyway, I went and installed Mobile Odin to my phone and the N.E.A.K kernel ( http://forum.xda-developers.com/showthread.php?t=1614150 ) for the ICS stock ROM, booted into recovery, wiped data, cache, and dalvik cacke, installed Cyanogenmod 10.2 nightly, gapps 4.2, went to advanced, and clicked reboot into recovery.
Next thing I knew, guess what? It was back to being stuck on the damn samsung logo and I couldn't boot into recovery, yet again! I went and though why not give it another try, so I redid all the procedures I had done prior, but this time flashed the 10.1.3 stable, AND IT HAPPENED AGAIN! I was like wtf! That leads me to the question. Is there anything I can do to prevent this from happening again? I really like cyanogenmod and would love to go back, but I don't want to repeat all of this a 4th time. Thanks for your help in advance!
EDIT: Nevermind. I got UCMD8 Cooked to work, but I am scared to flash 10.1.3/10.2 because I don't want to have to deal with doing all that I did in OP again. However, I really want CM 10.1.3/10.2 back. A dilema.
I don't do any AOSP versions, so I won't be any help there.
You can download UCMD8 from the Download Repository. It's at the bottom of the page. You can also always get the stock distributions from two sites:
http://www.sammobile.com/firmware/ (Need to be registered)
http://samsung-updates.com/ (Registration not needed)
Both of these sites are free to use.
creepyncrawly said:
I don't do any AOSP versions, so I won't be any help there.
You can download UCMD8 from the Download Repository. It's at the bottom of the page. You can also always get the stock distributions from two sites:
http://www.sammobile.com/firmware/ (Need to be registered)
http://samsung-updates.com/ (Registration not needed)
Both of these sites are free to use.
Click to expand...
Click to collapse
I got it to work. I want to go back to CM 10.1.3 but don't want to risk having the same problem again. Do you think it is safe for me to go back to CM 10.2 now?
azeem40 said:
I got it to work. I want to go back to CM 10.1.3 but don't want to risk having the same problem again. Do you think it is safe for me to go back to CM 10.2 now?
Click to expand...
Click to collapse
One of my advice is ignoring the kernel for now. I don't know why you keep flashing 3rd-party kernel.
Just flash the ROM and its gapps only, boot it and see what happens.
Also, CM 10.2 needs gapps 4.3, not 4.2
votinh said:
One of my advice is ignoring the kernel for now. I don't know why you keep flashing 3rd-party kernel.
Just flash the ROM and its gapps only, boot it and see what happens.
Also, CM 10.2 needs gapps 4.3, not 4.2
Click to expand...
Click to collapse
I fixed the issue by doing the OP things and just restoring nandroid backup.
Hellybean is by far the best ROM I've used yet on my Note. It runs almost perfectly. I did have to reboot because my bluetooth wouldn't come on (reboot always fixes that). However, when I rebooted it, the phone tried to restart, I saw the Samsung SGH-I717 screen, and then it went black. It never brings up the Hellybean ring of fire. If I pull the battery I see the ring of fire for about 5 seconds, then it reboots, then black screen.
At this point, the only thing I can do is force the phone into TWRP and restore a previous backup. Does anyone have any idea what could cause the phone to not want to reboot back into the system?
I was on the latest Hellybean build and TWRP is up-to-date as well. I had to revert back to the October 10 build though. I just tried rebooting it after a restore and the same thing happens (so it's not specific to a certain date of ROM). As long as I don't reboot I don't have a problem.
Thanks
Chris
MI_SS_IL said:
Hellybean is by far the best ROM I've used yet on my Note. It runs almost perfectly. I did have to reboot because my bluetooth wouldn't come on (reboot always fixes that). However, when I rebooted it, the phone tried to restart, I saw the Samsung SGH-I717 screen, and then it went black. It never brings up the Hellybean ring of fire. If I pull the battery I see the ring of fire for about 5 seconds, then it reboots, then black screen.
At this point, the only thing I can do is force the phone into TWRP and restore a previous backup. Does anyone have any idea what could cause the phone to not want to reboot back into the system?
I was on the latest Hellybean build and TWRP is up-to-date as well. I had to revert back to the October 10 build though. I just tried rebooting it after a restore and the same thing happens (so it's not specific to a certain date of ROM). As long as I don't reboot I don't have a problem.
Thanks
Chris
Click to expand...
Click to collapse
have you tried any other roms?
I have ran every update of Hellybean since its arrival here. I had made a backup and flashed another rom, didn't like so I went to install back up.
it would not install, just kept looping in the boot screen. had to fresh flash the rom. didn't matter which, just had to reflash. screen never went black though. you issue sounds more similar to a stuck power button, which is why I ask if you have had same problem with another rom.
I find it hard to believe this rom wont restore a back up. others have not chimed in with that specific issue. but you and I may just be 2 that have voiced the issue. wasn't that big of issue for me as I thought it more an oddity. my back up wouldn't install at all in 3 attempts, so again, whyi question your power button.
try another rom real quick if you can. don't have to like or want it, but this is a test right?
let us know what happens
captemo said:
have you tried any other roms?
I have ran every update of Hellybean since its arrival here. I had made a backup and flashed another rom, didn't like so I went to install back up.
it would not install, just kept looping in the boot screen. had to fresh flash the rom. didn't matter which, just had to reflash. screen never went black though. you issue sounds more similar to a stuck power button, which is why I ask if you have had same problem with another rom.
I find it hard to believe this rom wont restore a back up. others have not chimed in with that specific issue. but you and I may just be 2 that have voiced the issue. wasn't that big of issue for me as I thought it more an oddity. my back up wouldn't install at all in 3 attempts, so again, whyi question your power button.
try another rom real quick if you can. don't have to like or want it, but this is a test right?
let us know what happens
Click to expand...
Click to collapse
Let me clarify ... I'm not having a problem restoring or installing Hellybean or any other ROM. It's after I install or restore and the ROM is running fine (for days even) ... at some point I have to reboot for some reason and it's then that it won't boot back into the ROM. In other words I can't reboot my system because it never comes back to the ROM. I have to then boot to TWRP, restore something else and then that will boot to the ROM. If I reboot again after the ROM is up and running, I get the same thing, it won't boot back into the ROM, I have to restore again. That rules out a power button ... if it was stuck I would never get back in.
I've tried most of the ROMs out there, but since Hellybean I haven't tried any others (because this is the best one). You think there's any possibility dirty flashing all of the Hellybean builds over top of each other could cause it? Maybe I'll try installing the latest one from a full wipe.
Thanks
Chris
MI_SS_IL said:
Let me clarify ... I'm not having a problem restoring or installing Hellybean or any other ROM. It's after I install or restore and the ROM is running fine (for days even) ... at some point I have to reboot for some reason and it's then that it won't boot back into the ROM. In other words I can't reboot my system because it never comes back to the ROM. I have to then boot to TWRP, restore something else and then that will boot to the ROM. If I reboot again after the ROM is up and running, I get the same thing, it won't boot back into the ROM, I have to restore again. That rules out a power button ... if it was stuck I would never get back in.
I've tried most of the ROMs out there, but since Hellybean I haven't tried any others (because this is the best one). You think there's any possibility dirty flashing all of the Hellybean builds over top of each other could cause it? Maybe I'll try installing the latest one from a full wipe.
Thanks
Chris
Click to expand...
Click to collapse
I have dirty flashed every one. the only thing I try to do when gong dirty is to still give it that 10 settle time. no particular reason other than my OCD
Okay, thanks for the replies. I'll play around with it some more, maybe try a fresh install and see if that changes anything. I'll let you know if I figure it out.
Chris
I figured it out. Not Hellybean at all. It was TWRP. I reverted back to an early build and then reinstalled 2.6.3.0 and now it reboots fine.
Chris
I guess I can't edit the title to reflect the correct issue? Thread can be deleted if the moderators want. Hellybean is running strong ... it's the first ROM I get 0 random reboots.
Thanks for the help captemo and to the makers of Hellybean.
Chris
beanstalk
I got exactly same problem with beanstalk 4.3.
I tried reinstall recovery but no luck. Every time powering off or rebooting need a fully wipe and restore.
Do you think other or older recovery will work?
hotgly said:
I got exactly same problem with beanstalk 4.3.
I tried reinstall recovery but no luck. Every time powering off or rebooting need a fully wipe and restore.
Do you think other or older recovery will work?
Click to expand...
Click to collapse
Same issue. Any of the 4.3 ROMS.
MI_SS_IL said:
I figured it out. Not Hellybean at all. It was TWRP. I reverted back to an early build and then reinstalled 2.6.3.0 and now it reboots fine.
Chris
Click to expand...
Click to collapse
So did you:
1- restore a stable backup
2- boot to recovery and flash TWRP (which version?)
3- Boot back into recovery
3- wipe and flash HellyBean
Is this correct?
I'm sure people were getting pretty tired of hearing about the radio issues when people flashed cyanogenmod (ie, LTE worked, but no SMS, MMS, or voice calls, odin didn't fix, the only solution was to factory restore from WITHIN a TW ROM). After waiting a while for things to calm down, I'm ready to try to install Cyanogenmod again but I am naturally hesitant.
Has this issued resolved itself? I'm running rooted and unlocked MC3 with CWM installed. I heard somewhere that flashing the MJ9 radio BEFORE Cyanogenmod 10.2 / 11 fixed the problem?
I would really appreciate any input or personal experience here!
As far as I know, the issue has not resolved itself. I tried flashing the newest CM 11 a couple of days ago (I think it was the nightly build on the 22nd), and I still had the funky radio issues. However, I tried this, and it fixed all the radio issues with CM 11 (and any other Android 4.4 ROMS - I'm running Slim ROM at the moment)... Here is my post from another thread.
Hey all, I got it working (the data/network connection that is), with a little effort. Here is what I did in sequence...
1) Reflash the ORIGINAL VRALJB image via ODIN. I used the one found here. You want to make sure you get the one that replaces EVERYTHING, i.e., NOT the alternative restore.
2) I set up my phone and used it normally for about four hours. (This may or may not be necessary, I'm not entirely sure. I also rebooted the phone about five times during that time frame.)
3) I unlocked and rooted the phone via the method outlined here. After that was done, I installed CWM 6.0.4.3 via TWRP (which the unlocking process installs).
4) I then installed CM 11 and the respective Google apps. (I first did a backup, then a factory reset, then cache wipe, then dalvik wipe. The next thing I did was install CM 11, then Gapps.)
5) Restart the phone and success!
Click to expand...
Click to collapse
The reason why I found out that this method would work, is that I tried installing CM 11 on my dad's phone. He has had a TW ROM (Beans build to be exact) since the phone came out. And he has been running the stock VRALJB radio. With that said, I figured I would try flashing the stock ODIN files to restore my phone back to the VRALJB. (I think I was running the MJ9 prior to this) That worked, and the SlimROM has been working perfectly ever since!
[Also, if you wanted to check out SlimROM, you can find a link to it here.]
Still looking for some more feedback from users! Anyone successfully flashed CM 10.2 / CM 11 from MC3 without problems / fixed the problems?
I went from stock to rooted, TWRP, S-off, CM 10.2. The first time I tried it, the phone immediately required activation. So I went back to a stock rooted ROM performed the activation and then went back to CM 10.2. I tested calling, Data, and text everything worked. 2 hours later I tried to place a call and the phone wanted to be activated again. Everything I've found referring to this issue says going back to stock and activating before flashing the ROM fixes this problem. Any ideas?
I purchased an AT&T SGH-i717 and was told everything worked. When I checked it out, everything seemed fine too. After using it for a couple hours I realized it just seemed to reboot at random. I rebooted into recovery and did a factory reset and wiped the cache. After rebooting it...it would get stuck at the AT&T screen. I then installed the latest stock rom 4.4.2 using Odin and it booted up fine but I got the no sim card error. I put in an AT&T sim card and rebooted but got a sim not provisioned error. I then tried a T-Mobile card and I didn't get the error and it showed signal bars but when I tried to dial it said emergency calls only. I tried a Verizon sim card just to see what kind of error I would get but it was just the same as the T-Mobile sim. I thought it might a corrupted rom so I tried installing the latest nightly CyanogenMod using CWM but got error status 7. I then tried various custom and stock roms including AOKP, BeanStalk, and several different versions of CyanogenMod but always got the same error status 7 msg. I then came across a forum posts stating that CWM no longer works for the SGH-i717. I downloaded the latest TWRP touch recovery and was able install the latest stable CyanogenMod but it would not boot past the animated CyanogenMod logo even after sitting for over an hour. At that point I gave up and decided to just go back to the stock rom. I rebooted into TWRP and the slide to unlock would not work anymore. I had to install CWM using Odin which allowed me to flash back to the stock 4.4.2 rom. After doing another factory reset and wiping the cache then rebooting...the touch screen stopped working. I then flashed it back to the stock 4.0.4 rom but the touch screen still does not work. While trying to figure out what happened I realized the pen still works and touch screen buttons on the bottom but thats it. Also the pen only works on the screen and not on the touch screen buttons. I've been messing with this for 3 days and will probably just sell it for parts but wanted to post this problem so if anyone else had this problem they would know what I've already tried. I did also take apart the phone and clean the connections but that didn't help either.
If anyone has a suggestion for something I haven't tried...please let me know. My last attempt will be install the Padawan JB rom from this post:
http://forum.xda-developers.com/showthread.php?t=1907203
Thanks
Right out of tge gate, there is no stock 4.4.2 for this device. Not official anyway. 4.1.2 is official OS.
Status 7 means your recovery needs updating.
CWM does work and the newest CWM touch is just dandy.
I would try going all the way back. You need to be totally clean.
Factory
Cache
Davlik
Format
Go to Kies and go with emergency firmware recovery.
Get back to stock and see what is working.
Clean clean clean, the best way for anyone to help you. You would be at the best starting point.
Maybe do a little reading as many of your issues have been documented and solved. None of them are major.
Start from scratch and folks can get you running again.
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
captemo said:
Right out of tge gate, there is no stock 4.4.2 for this device. Not official anyway. 4.1.2 is official OS.
Status 7 means your recovery needs updating.
CWM does work and the newest CWM touch is just dandy.
I would try going all the way back. You need to be totally clean.
Factory
Cache
Davlik
Format
Go to Kies and go with emergency firmware recovery.
Get back to stock and see what is working.
Clean clean clean, the best way for anyone to help you. You would be at the best starting point.
Maybe do a little reading as many of your issues have been documented and solved. None of them are major.
Start from scratch and folks can get you running again.
Sent from my SAMSUNG-SGH-I527 using xda app-developers app
Click to expand...
Click to collapse
Thanks for replying...I hadn't used Kies in awhile becuase it never seemed to work right. I downloaded the latest version and it looks like they made a lot of improvements. I did the factory restore and wiped the cache then installed the latest firmware thru Kies. Everything seemed to work fine but after rebooting the touch screen doesn't work at all, not even with the pen. The touch screen buttons seem to still work but its stuck at the AT&T Ready2go screen because I can't hit cancel or get started buttons.
Thanks
cycloneus said:
Thanks for replying...I hadn't used Kies in awhile becuase it never seemed to work right. I downloaded the latest version and it looks like they made a lot of improvements. I did the factory restore and wiped the cache then installed the latest firmware thru Kies. Everything seemed to work fine but after rebooting the touch screen doesn't work at all, not even with the pen. The touch screen buttons seem to still work but its stuck at the AT&T Ready2go screen because I can't hit cancel or get started buttons.
Thanks
Click to expand...
Click to collapse
well my friend, you had the phone apart once already, I am no expert, but my guess is this is no software issue. maybe some connections came loose. in my time here, I have not come across this issue. I do not have the brain pan nor the courage to take my phone apart.
good luck to you.
maybe someone else will mosey on by.
cycloneus said:
Thanks for replying...I hadn't used Kies in awhile becuase it never seemed to work right. I downloaded the latest version and it looks like they made a lot of improvements. I did the factory restore and wiped the cache then installed the latest firmware thru Kies. Everything seemed to work fine but after rebooting the touch screen doesn't work at all, not even with the pen. The touch screen buttons seem to still work but its stuck at the AT&T Ready2go screen because I can't hit cancel or get started buttons.
Thanks
Click to expand...
Click to collapse
My guess is the digitizer has gone bad if odin &/or kies can't fix the issue at hand.