Related
So every time I load a 2.2 ROM, My phone starts to wig out and so random things when I am trying to type or anything else. I am rooted and have the ota 2.x radio installed. I keep having to go back to a 2.1 ROM with hydra kernel and everything is stable. I do a factory reset every time but still no go. any ideas?
tlevash said:
So every time I load a 2.2 ROM, My phone starts to wig out and so random things when I am trying to type or anything else. I am rooted and have the ota 2.x radio installed. I keep having to go back to a 2.1 ROM with hydra kernel and everything is stable. I do a factory reset every time but still no go. any ideas?
Click to expand...
Click to collapse
a factory reset is not the same as a wipe from recovery menu afaik (if you mean a factory reset from bootloader (white screen))
boot into clockworkmod recovery and perform a wipe data/cache there, then flash it
some even experience problems with running the wipe from rom manager, so do it in the recovery menu instead
Thanks for the help. I tried what you said above and downloaded Sky raider 2.0 again. renamed it to update.zip then rebooted into clockwork. I did the wipe data/cache but sadly, I get the same results. I cant even get through the setup after the rom is installed. screen is unresponsive to my touch, but seems to have a mind of its own. I had best luck with CM 6 test 8 i downloaded from ROM manger, that ran for a day before starting to screw up.
Hey guys,
Had my Nexus for just over a year now, direct from google. i've been flashing roms and kernels for about 6 months, however since upgrading recovery to CWM 3.0 i've had nothing but problems.
Ive downgraded CWM to 2.5 and even switched to Amon RA 2.2.1, still having issues flashing.
Mainly themes, but alot of roms are refuses to flash too. leaving me stuck on the nexus X splash screen when switching on.
i've just flashed to cm6.1 and tried to flash an old theme i used to use, and even that failed. and im completely stumped.
I can only imagine that when flashing CWM through rom manager, it changed some other system files perhaps? Im not going to even pretend i can hold more than my own, hence this post, im stumped. does anybody know what may/could of happened? and what i can do to fix it?
Thanks in advance
http://forum.xda-developers.com/forumdisplay.php?f=603
when you wipe you do a complete wipe, /system, cache and all?
edit:
try and flash the zip from temasek signature.
http://forum.xda-developers.com/member.php?u=2332422
Try reflash the fastboot region on your phone
Sent from my Nexus One using XDA App
over the last few days I've flashed a number of ROMs, mostly the Google Edition 4.2.2 and 4.3 ones and every single one of them eventually fails to boot hanging on the Samsung bootloader screen. and i say eventually because the first boot is almost always flawless, but then each time i reboot or power down, its almost guaranteed to loop.
I've tried so many different combinations that there's really not a single path I've taken every time, but the general steps are:
-root original firmware using motochopper
-install TWRP via GooManager
-reboot recovery and wipe everything, typically I do Advanced and select everything, then format Data
-then flash through ADB sideload, I do this since I wipe everything before flashing and I don't have an external SD card
-immediately after flashing ROM, I flash loki-doki also through ADB sideload. some of the ROMs I tried said they were lokied, but I still got the ATT invalid ROM message, so I reflashed with loki and it worked.
-then reboot system and the first time it comes up and works fine on every ROM I've tried
But if I power down or restart, on a very rare occasion it'll come up, but almost every time it hangs on bootloader screen. I also noticed once it's stuck on bootloader, power button becomes unresponsive, sometimes holding it powers down device, sometimes does nothing (have to press and hold twice)
If I flash back to stock using Odin, it works, boots, reboots, powers down just fine.
I've also tried flashing with a ROM and then immediately after with the stock ATT kernel, also booted up fine, but looped on restart.
Could this be hardware issue?
I'm about to give up on this and go back to stock for good, which would be really disappointing, can anyone help?
Flash a KT kernel and see what happens, I suppose you know which one correct?
TheAxman said:
Flash a KT kernel and see what happens, I suppose you know which one correct?
Click to expand...
Click to collapse
I assume KT means http://forum.xda-developers.com/showthread.php?t=2292341 ?
I've tried that too with jamal2367's 4.2.2 GE ROM (http://forum.xda-developers.com/showthread.php?t=2341794). It refused to boot all together.
First time I flashed with AOSP version since I thought that was an AOSP ROM, then reading more comments in the other thread it said I needed the TW version for GE ROMs, so I tried that too. Either way, neither of them booted at all, even the first time, so I gave up on KT and only used either ROMs' included kernels or ATT stock.
It is not a hardware issue, I am guessing that you have a US ATT G4 correct? I would odin back to stock, and restart the process again, this is assuming you tried the correct TW kernels. Because I know this error and all it requires is a simple flash of the correct kernel.
TheAxman said:
It is not a hardware issue, I am guessing that you have a US ATT G4 correct? I would odin back to stock, and restart the process again, this is assuming you tried the correct TW kernels. Because I know this error and all it requires is a simple flash of the correct kernel.
Click to expand...
Click to collapse
OK I'll try one more time from scratch, can you verify I'm using the right stuff though for US ATT Galaxy S4:
ROM: http://forum.xda-developers.com/showthread.php?t=2341794
Kernel: http://forum.xda-developers.com/showthread.php?t=2292341 (TW one, specifically http://goo.gl/SiDjB)
And any idea why the ROM's kernel wouldnt work after being lokied?
collegebored said:
OK I'll try one more time from scratch, can you verify I'm using the right stuff though for US ATT Galaxy S4:
ROM: http://forum.xda-developers.com/showthread.php?t=2341794
Kernel: http://forum.xda-developers.com/showthread.php?t=2292341 (TW one, specifically http://goo.gl/SiDjB)
And any idea why the ROM's kernel wouldnt work after being lokied?
Click to expand...
Click to collapse
You know, I don't even look at anything that says loki anymore, I flash the rom I want and use MY carriers kernel, bootloops and hangs are just not there, I do not see these issues everyone has, because, I have this procedure everytime. So...
Btw, your good on your files you want to flash, but, if this does not work ie, GE and that kernel, try a TW rom with the kernel, bet it boots properly. I do not give a rats
a$$ about goole roms. They are not worth it. Btw, I use this procedure on TW and aosp roms, no issues. Just because it says it loki'ed, flash the kernel you know works, loki just confuses people.
The Ax says again an again..My opinion only!
Good luck sir.
BTW, I ran that rom with the kernel you chose, it should work just fine. Remember, flash the TW version.
Thanks Ax for your help here, your welcome.
So I was originally on MDL. AT&T S4 of course. Rooted it, installed custom ROMs, everything good. But recently it seems to have issues. Seems like Original Android ROMs just refuse to start up, like Beanstalk or ShoStock. Shows the Custom Lock boot screen thing, then just restarts to recovery. One of the few that worked fine and just booted normally was Alpha ROM from Android, now on the Tmobile forum I believe and Miui ROM.
So I gave up and tried restocking. Installed the MDL stock ROM again, motochopper, used ROM Manager to install Clockwork Recovery (Touch.), and then another problem. The recovery showed the android mascot laying down and that small red box. It seems to have defaulted to some Android Recovery thing with limited options. Rebooted and tried Clockwork Recovery normal edition this time. Same thing.
Honestly not sure what's wrong. Did I miss something and should have updated something or...?
gerard0986 said:
So I was originally on MDL. AT&T S4 of course. Rooted it, installed custom ROMs, everything good. But recently it seems to have issues. Seems like Original Android ROMs just refuse to start up like Beanstalk. Shows the Custom Lock boot screen thing, then just restarts to recovery. One of the few that worked fine and just booted normally was Alpha ROM from Android, now on the Tmobile forum I believe and Miui ROM.
So I gave up and tried restocking. Installed the MDL stock ROM again, motochopper, used ROM Manager to install Clockwork Recovery (Touch.), and then another problem. The recovery showed the android mascot laying down and that small red box. It seems to have defaulted to some Android Recovery thing with limited options. Rebooted and tried Clockwork Recovery normal edition this time. Same thing.
Honestly not sure what's wrong. Did I miss something and should have updated something or...?
Click to expand...
Click to collapse
Did you use LOKI?
scott14719 said:
Did you use LOKI?
Click to expand...
Click to collapse
Yeah. Had a recovery with auto loki. But I believe a few of the ROMs I tried were lokied already too. Still didn't work.
I just tried using the stock recovery. Restocked, and went straight to recovery. No motochopper or anything.
Still shows the error droid and under the limited option'd "Android system recovery <3e>", it says, in yellow,
"# Manual Mode #"
"-- Applying Multi-CSC..."
"Applied the CSC-code : ATT"
"Successfully applied multi-CSC."
I'm guessing I broke something somehow...but I REALLY hope this is fixable. This recovery lets me reboot system, apply update from ADB, apply update from external storage, wipe data/factory reset, wipe cache partition, and apply update from cache.
Restocked again and used the new CASUAL root. TWRP installed fine from it and works fine, but I tried Beanstalk again and still just reboots into recovery. Even flashed loki twice. What am I missing? Stuck at rooted stock for now.
Bumping this up. Still seem unable to install other ROMs.
gerard0986 said:
Bumping this up. Still seem unable to install other ROMs.
Click to expand...
Click to collapse
No ROMs have worked at all? Have you tried installing a different kernel?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
DeadlySin9 said:
No ROMs have worked at all? Have you tried installing a different kernel?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Seems most I try from the "Original Android" section don't work at all. Starts up, waits at the Custom Lock boot image thing or the stock Samsung logo, and eventually reboots into recovery. Select ones from the "Android" section will work. Alpha I think so far was the only one that I tried and worked fine.
I'll try the kernal thing though, but would that affect the recovery like I mentioned before? Or am I dealing with multiple problems perhaps?
gerard0986 said:
Seems most I try from the "Original Android" section don't work at all. Starts up, waits at the Custom Lock boot image thing or the stock Samsung logo, and eventually reboots into recovery. Select ones from the "Android" section will work. Alpha I think so far was the only one that I tried and worked fine.
I'll try the kernal thing though, but would that affect the recovery like I mentioned before? Or am I dealing with multiple problems perhaps?
Click to expand...
Click to collapse
Kernel shouldn't affect the recovery, just make sure the kernel is patched for loki.
When you are getting back into recovery what recovery is showing? The TWRP recovery or 3e recovery? Kind of sounds like it is defaulting back to the 3e recovery.
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
RockRatt said:
When you are getting back into recovery what recovery is showing? The TWRP recovery or 3e recovery? Kind of sounds like it is defaulting back to the 3e recovery.
Sent From My Spiderman,Ironman,Red,Dark Blue,Green, GreyedOut BadAss Themed I337
Click to expand...
Click to collapse
With the old Motochopper it defaulted to 3e recovery (But didn't before all of these problems.). With the new Java based one it loads TWRP normally again.
I switched to Task's AOKP just fine it seems. Maybe it was just the kernel. This problem is solved for now I guess.
Problem is back. I tried to restock and it seems to have worked, but now it just gets stuck at the AT&T globe logo right after the melody. It just freezes and starts to get hot.
Normally I take for granted that the answer is out there in a forum or some tech blog. I've looked everywhere and unfortunately every guide I followed or Google combination I've tried didn't help.
Just can't get any custom rom to install and boot up, they all hang at the Samsung logo with text in the upper right corner telling me the kernel isn't senforcing.
I have a sgh i337m, it's an mk6 build number if that helps. Currently on stock 4.3 and rooted using saferoot. My carrier is telus and the phone is Sim locked still (is that the issue?)
I have twrp 2.6.1 installed and have flashed multiple roms for the jfltecan which I trust is the right model I need based on goo.manager
I've tried cm11, cm10, gummyrom for 4.4.2, omnirom also for 4.4.2 and they all hang at the splash screen. My method for flash is based on the ultimate guide that is stickied which is to wipe system, data and both the caches. Then flash the zip and the gaaps. I even tried the lokidoki zip in other combinations
Then I tried using cwmod recovery thinking perhaps it is twrp's fault and got the same hanging at the splash screen
I'm now just back to rooted stock 4.3 after restoring my nandroid
Any insights out there that can be deciphered from my rambling would be very much appreciated!!! Frustrated as hell. My nexus 7 was such a breeze and did not expect this to happen on my s4.
wondakson said:
Normally I take for granted that the answer is out there in a forum or some tech blog. I've looked everywhere and unfortunately every guide I followed or Google combination I've tried didn't help.
Just can't get any custom rom to install and boot up, they all hang at the Samsung logo with text in the upper right corner telling me the kernel isn't senforcing.
I have a sgh i337m, it's an mk6 build number if that helps. Currently on stock 4.3 and rooted using saferoot. My carrier is telus and the phone is Sim locked still (is that the issue?)
I have twrp 2.6.1 installed and have flashed multiple roms for the jfltecan which I trust is the right model I need based on goo.manager
I've tried cm11, cm10, gummyrom for 4.4.2, omnirom also for 4.4.2 and they all hang at the splash screen. My method for flash is based on the ultimate guide that is stickied which is to wipe system, data and both the caches. Then flash the zip and the gaaps. I even tried the lokidoki zip in other combinations
Then I tried using cwmod recovery thinking perhaps it is twrp's fault and got the same hanging at the splash screen
I'm now just back to rooted stock 4.3 after restoring my nandroid
Any insights out there that can be deciphered from my rambling would be very much appreciated!!! Frustrated as hell. My nexus 7 was such a breeze and did not expect this to happen on my s4.
Click to expand...
Click to collapse
I too have been plagued by this same issue,
but only on a blue moon so to speak, I kept rebooting
and eventually my phone booted through that silly splash screen!
wondakson said:
Normally I take for granted that the answer is out there in a forum or some tech blog. I've looked everywhere and unfortunately every guide I followed or Google combination I've tried didn't help.
Just can't get any custom rom to install and boot up, they all hang at the Samsung logo with text in the upper right corner telling me the kernel isn't senforcing.
I have a sgh i337m, it's an mk6 build number if that helps. Currently on stock 4.3 and rooted using saferoot. My carrier is telus and the phone is Sim locked still (is that the issue?)
I have twrp 2.6.1 installed and have flashed multiple roms for the jfltecan which I trust is the right model I need based on goo.manager
I've tried cm11, cm10, gummyrom for 4.4.2, omnirom also for 4.4.2 and they all hang at the splash screen. My method for flash is based on the ultimate guide that is stickied which is to wipe system, data and both the caches. Then flash the zip and the gaaps. I even tried the lokidoki zip in other combinations
Then I tried using cwmod recovery thinking perhaps it is twrp's fault and got the same hanging at the splash screen
I'm now just back to rooted stock 4.3 after restoring my nandroid
Any insights out there that can be deciphered from my rambling would be very much appreciated!!! Frustrated as hell. My nexus 7 was such a breeze and did not expect this to happen on my s4.
Click to expand...
Click to collapse
First off I am hoping you are flashing from recovery and not trying something through goo manager. Second, it sounds as though you are skipping the wiping step before installing a new rom, you absolutly have to wipe cache/dalvik/ and factory reset all before flashing any rom.... also I wipe the system too to make it a clean install, make sure you put the rom of choice on the external sd and make sure you have a nanroid backup with your installed recovery twrp or cwm.....
PS lokidokie and saftey starp only apply to US versions (I337) not the Canadian I337M use only the roms build of this model.... I haven't had very good luck with cm based roms in the past so I tend not to flash those... I flashed one rom and the phone got super hot ... not sure what the issue was ... nand back to stock starter over with a differnet rom
Adizzzle said:
I too have been plagued by this same issue,
but only on a blue moon so to speak, I kept rebooting
and eventually my phone booted through that silly splash screen!
Click to expand...
Click to collapse
How long did you wait at the splash screen before booting again and again? After a new installation does the phone take extra time at the splash screen or is it at a different screen?
wondakson said:
How long did you wait at the splash screen before booting again and again? After a new installation does the phone take extra time at the splash screen or is it at a different screen?
Click to expand...
Click to collapse
Please... you need to provide some more info for people to help you..... rom you tried to install and the steps.. not tryin to be mean just hard to help without details....
Ahh I know the problem if your flashing all of them from the att section. It could be that all of those roms you tried have loki built into the kernel and is stopping you from booting. Are u choosing ones that say they are specifically for the Canadian model or the ones for att?
I would also suggest booting once first before flashing gapps. I am using this Carbon rom http://forum.xda-developers.com/showthread.php?t=2568699 and it's universal, for US or CA models. I highly recommend it.