Android OS Forum banner
1 - 9 of 9 Posts

· Registered
Joined
·
4 Posts
Discussion Starter · #1 ·
I'm having a boot loop issue the moment I install AOKP.

I've successfully installed AOKP on my Samsung Galaxy S4 from T-Mobile (SGH-M919) a few months back (aokp_jfltetmo_nightly_2013-06-09). I used the same process as before but the difference of course is that it's now boot looping after I install any new mod.

At first I tried the latest nightly as that was the point of the install, updating my ROM. After the boot looping issue I just decided to go back to the original nightly that worked before but is also boot looping on me.

Here is my process:

-I start with using Odin3 to revert to the Galaxy S4 Stock Firmware (M919UVUAMDL_M919TMBAMDL_M919UVUAMDL_HOME.tar.md5)

-I then wipe all user data.

-After a reset I flash the CF-Auto-Root-jfltetmo-jfltetmo-sghm919.tar.md5 to root the phone.

-I restart again and then flash the OUDHS-Recovery-jfltetmo-1.0.3.3.

-Before and after each new flash I wipe partition cache and dalvik cache.

-After all of this the phone boots up, rooted and working fine.

-I even install TriangleAway and reset the phone each time before installing the AOKP mod.

The issue is when I flash the nightly. It installs fine, I reset the phone and it gets stuck on the boot screen. I have waited as long as 20 minutes with no change.

I have even used both Odin3 v1.85 and v3.07 for the complete process.

I have also done this process on 2 separate computers (both Windows 7 - 64 bit)

Does anyone have a suggestion as to what I'm doing wrong with the process?

Thanks for any and all help!
 

· Tweaker
Joined
·
1,190 Posts
After looking up what recovery you are using it appears that even though it is based on CWM, it has not updated when they have. Try using the latest CWM recovery from http://www.clockworkmod.com/rommanager and see if that makes a difference. What I think may be happening is that your custom recovery is not sticking after you reboot and it is getting replaced by the stock recovery.
 

· Registered
Joined
·
4 Posts
Discussion Starter · #3 ·
Thanks for the reply!

It was a good suggestion BUT unfortunately, while the new CWM touch recovery is pretty cool, getting the latest version for my phone (recovery-clockwork-6.0.3.6-jfltetmo) still does not fix the boot loop issue.

Its very confusing because I used the same apps, rom, programs and process as before when it actually worked and now it is not working at all.
 

· Registered
Joined
·
4 Posts
Discussion Starter · #5 ·
I'm not 100% sure what you mean by restoring system data. You mean resetting the phone to defaults after it loads? I flash the stock firmware and then wipe user data in recovery mode, but that's it. Also, no, haven't formatted the /system, but I will try that when I can devote some downtime to my phone later.

Once again, thanks for the suggestions its super helpful!
 

· Tweaker
Joined
·
1,190 Posts
I'm not 100% sure what you mean by restoring system data. You mean resetting the phone to defaults after it loads? I flash the stock firmware and then wipe user data in recovery mode, but that's it. Also, no, haven't formatted the /system, but I will try that when I can devote some downtime to my phone later.

Once again, thanks for the suggestions its super helpful!
I meant using an app like titanium backup to restore app and system data. But /system should be formatted when flashing the stock firmware and when you do a factory reset. And no problem, glad to help.
 
1 - 9 of 9 Posts
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top