Related
I've been searching for the stock kernal for at&t users for s bit now, can't find it I'm trying to fix the annoying "updating camera firmware,please wait..." message. Unless there's a better way, I'll just assume you have to flash the sock kernal to update it. But if you flash the sock Kernal, wouldn't the phone fail on boot?
Sent from my GT-I9505 using xda app-developers app
bubblebuddyi said:
I've been searching for the stock kernal for at&t users for s bit now, can't find it I'm trying to fix the annoying "updating camera firmware,please wait..." message. Unless there's a better way, I'll just assume you have to flash the sock kernal to update it. But if you flash the sock Kernal, wouldn't the phone fail on boot?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
What ROM are you running? Omega?
Sent from my GT-I9505 using xda app-developers app
rcklss1 said:
What ROM are you running? Omega?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
No, I'm running Wanamlite v1.0.
I just reinstalled the stock AT&T rom to allow the camera to update, but when I ran the camera, no update appeared. So I figured it was all set. After re-rooting, I re-installed Wanamlite and KT kernal, open up the camera, and sure enough the message re-appears. I didn't perform any wipes. But it looks like I'll have to because all the AT&T bloatware was re-installed again.
bubblebuddyi said:
No, I'm running Wanamlite v1.0.
I just reinstalled the stock AT&T rom to allow the camera to update, but when I ran the camera, no update appeared. So I figured it was all set. After re-rooting, I re-installed Wanamlite and KT kernal, open up the camera, and sure enough the message re-appears. I didn't perform any wipes. But it looks like I'll have to because all the AT&T bloatware was re-installed again.
Click to expand...
Click to collapse
Your mistake was reinstalling Wanamlite again. Here's how you install non AT&T ROMs
1. Root your phone. I used the one click TWRP and Loki method.
2. Factory Reset and install custom ROM.
3. Install AT&T kernel. Let it boot up. Open Camera.
4. Reboot to recovery. Install custom kernel. Wipe cache and Dalvik. Fix Permissions.
5. Reboot. All done.
Sent from my Galaxy S4
Baldilocks said:
Your mistake was reinstalling Wanamlite again. Here's how you install non AT&T ROMs
1. Root your phone. I used the one click TWRP and Loki method.
2. Factory Reset and install custom ROM.
3. Install AT&T kernel. Let it boot up. Open Camera.
4. Reboot to recovery. Install custom kernel. Wipe cache and Dalvik. Fix Permissions.
5. Reboot. All done.
Sent from my Galaxy S4
Click to expand...
Click to collapse
Thanks, you're right about my mistake lol I ended up just installing someone else's ROM and it works perfectly. I'm a bit lost reading your instructions, It was my understanding that custom ROM's would not load with stock kernel?
bubblebuddyi said:
Thanks, you're right about my mistake lol I ended up just installing someone else's ROM and it works perfectly. I'm a bit lost reading your instructions, It was my understanding that custom ROM's would not load with stock kernel?
Click to expand...
Click to collapse
You need a carrier kernel for your custom ROM.
Sent from my Galaxy S4
Baldilocks said:
You need a carrier kernel for your custom ROM.
Sent from my Galaxy S4
Click to expand...
Click to collapse
can you link to a stock kernel for the AT&T i337?
xxhorseriderxxx said:
can you link to a stock kernel for the AT&T i337?
Click to expand...
Click to collapse
Exactly, its nice he can recommend installing a stock kernel, but they are not to be found. I asked in another thread and didn't get an answer. I somehow got it to work just wiping and installing Omega 5.0 Then to get wifi to work I installed ktoonez kernel.
Sent from my GT-I9505 converted SGH-I337
highaltitude said:
Exactly, its nice he can recommend installing a stock kernel, but they are not to be found. I asked in another thread and didn't get an answer. I somehow got it to work just wiping and installing Omega 5.0 Then to get wifi to work I installed ktoonez kernel.
Sent from my GT-I9505 converted SGH-I337
Click to expand...
Click to collapse
okay, assuming you're using the AT&T variant, I did this:
I got the looping "installing camera firmware" and tried faux an ktoonsez with no luck
I flashed this tmobile stock kernel and the camera firmware updated successfully by going into the camera app.
I then just flashed faux kernel back and everything worked great.
http://forum.xda-developers.com/showthread.php?t=2271976
I use shabbypenguin's auto loki CWM recovery, but you'll have to definitely flash the loki patch after the tmo kernel to make this work.
http://forum.xda-developers.com/showthread.php?t=2291956
I've been trying many things to no avail. I am able to get recovery on my i9505G (which I have read is built into the CWM version now for the i9505) and it seems to work fine. I have the 01/08 nightly CM11 on the phone, but whenever I reboot and select "recovery" it gives me this error. Sometimes if I hit the restart the device, it will boot into recovery correctly. I've even started fresh by wiping the entire phone and the multiple partitions (from having started on 4.2) and flashed a fresh 4.4.2 stock (rooted) tar through odin. From there I flashed the recovery, installed CM as I always have, but it is still happening.
What am I doing wrong?
The photo u attached is STOCK RECOVERY. If u want install CUSTOM RECOVERY for install CUSTOM ROMS: HERE
* EDIT: Dont flash custom recovery/Roms/Kernels/Basebands of i9505 for ur i9505G. Its completely different
Joku1981 said:
The photo u attached is STOCK RECOVERY. If u want install CUSTOM RECOVERY for install CUSTOM ROMS: HERE
* EDIT: Dont flash custom recovery/Roms/Kernels/Basebands of i9505 for ur i9505G. Its completely different
Click to expand...
Click to collapse
That is the weird thing, it does have the custom CWM recovery on it, but this happens when I click to reboot into recovery in CM11. I've tried reinstalling CWM numerous times, but I still get this same situation after the first time.
mrmartin86 said:
That is the weird thing, it does have the custom CWM recovery on it, but this happens when I click to reboot into recovery in CM11. I've tried reinstalling CWM numerous times, but I still get this same situation after the first time.
Click to expand...
Click to collapse
Coz u are installing CWM for i9505 no for i9505G maybe?
Joku1981 said:
Coz u are installing CWM for i9505 no for i9505G maybe?
Click to expand...
Click to collapse
I've read on many of the threads here that the i9505G build-specifics were incorporated into "jfltexx" builds.
mrmartin86 said:
I've read on many of the threads here that the i9505G build-specifics were incorporated into "jfltexx" builds.
Click to expand...
Click to collapse
No:
- GT-i9505 is into "jfltexx" builds
- GT-i9505G is into "jgedlteue" builds
Joku1981 said:
No:
- GT-i9505 is into "jfltexx" builds
- GT-i9505G is into "jgedlteue" builds
Click to expand...
Click to collapse
What I meant was the i9505G specifics were builts in the CWM and Cyanogenmod builds of the jfltexx.
mrmartin86 said:
What I meant was the i9505G specifics were builts in the CWM and Cyanogenmod builds of the jfltexx.
Click to expand...
Click to collapse
Yes and no, but we dont gona speak about that now. It will be soooo long :highfive:. You asked one thing sir in this thread... If i helped ya Im happy for it :good:
Joku1981 said:
Yes and no, but we dont gona speak about that now. It will be soooo long :highfive:. You asked one thing sir in this thread... If i helped ya Im happy for it :good:
Click to expand...
Click to collapse
Well here is what I am trying to do. Root isn't a problem, but getting recovery on it is. I've been using the jltflexx builds of CWM and Cyanogen because I read that it was built into it. They both install with no problem and I can get up and running. The problem I run into is getting back into custom recovery and I get that picture error above when I try. I don't know if the custom recovery is getting overwritten by something or what, but it does get installed otherwise I wouldn't be able to get CM11 on it in the first place.
mrmartin86 said:
Well here is what I am trying to do. Root isn't a problem, but getting recovery on it is. I've been using the jltflexx builds of CWM and Cyanogen because I read that it was built into it. They both install with no problem and I can get up and running. The problem I run into is getting back into custom recovery and I get that picture error above when I try. I don't know if the custom recovery is getting overwritten by something or what, but it does get installed otherwise I wouldn't be able to get CM11 on it in the first place.
Click to expand...
Click to collapse
How i see u still having the STOCK RECOVERY and u was telling me it worked ok. If i was u i will try the post #2
Joku1981 said:
How i see u still having the STOCK RECOVERY and u was telling me it worked ok. If i was u i will try the post #2
Click to expand...
Click to collapse
That is what I don't get. How could I have flashed the custom CWM recovery, used it to install CM, but then have stock recovery and can't get back into the custom one all the time? It is really bizarre.
mrmartin86 said:
That is what I don't get. How could I have flashed the custom CWM recovery, used it to install CM, but then have stock recovery and can't get back into the custom one all the time? It is really bizarre.
Click to expand...
Click to collapse
These are my sources about the i9505 jltflexx builds.
http://forum.xda-developers.com/showthread.php?t=2370101
http://forum.cyanogenmod.com/topic/75444-gt-i9505g-cyanogenmod/
EDIT: Seems this is a problem with CWM itself. When I just used TWRP to do all the same things, everything worked fine.
mrmartin86 said:
These are my sources about the i9505 jltflexx builds.
http://forum.xda-developers.com/showthread.php?t=2370101
http://forum.cyanogenmod.com/topic/75444-gt-i9505g-cyanogenmod/
EDIT: Seems this is a problem with CWM itself. When I just used TWRP to do all the same things, everything worked fine.
Click to expand...
Click to collapse
CWM 6.0.4.4 work fine on the i9505G. I use it on mine and have since it came out.
Hey!
I recently rooted my GS4 i337. Everything is all working as of now. However, I want to flash an AOSP ROM onto it. So, I followed instructions and at first, I flashed TWRP to my phone. It said it was successful, but when I go to recovery it puts me in ODIN. I then uninstalled TWRP and got the latest version that is said to support i337 GS4. Flashed successfully, but when I boot it still goes ODIN.
I tried both manually recovery booting with the buttons, and the UI on the actual app. Boots ODIN both ways.
Is there something I'm doing wrong? How can I boot into TWRP or CWM so I can make a quick ROM backup and flash an AOSP ROM?
Cheers! And if this is the wrong section, can a moderator please move it? I'm new to this forum.
Thanks. :laugh:
Check your firmware version then do a lot of reading.
jd1639 said:
Check your firmware version then do a lot of reading.
Click to expand...
Click to collapse
Explain please?
nhannon9 said:
Explain please?
Click to expand...
Click to collapse
Unless your on mdl firmware you can't flash twrp or cwm. I'm guessing you're not.
jd1639 said:
Unless your on mdl firmware you can't flash twrp or cwm. I'm guessing you're not.
Click to expand...
Click to collapse
Don't think so, my baseband is UCUEMK2 on 4.3. So, there's no way to get any custom ROMs on this? What can I do so I can?
nhannon9 said:
Don't think so, my baseband is UCUEMK2 on 4.3. So, there's no way to get any custom ROMs on this? What can I do so I can?
Click to expand...
Click to collapse
Google i337 safestrap mk2 xda
jd1639 said:
Google i337 safestrap mk2 xda
Click to expand...
Click to collapse
I found this a video on how to use Safestrap on 4.3.
It's for the Verizon variant but the SE Linux matches, can I give Safestrap a shot?
EDIT: Scratch that, I've found an ATT compatible version (3.71) and it booted into it perfectly! Now I can backup my stock ROM real quick and flash on my new one! Thanks!!
Hey I just have a quick question here. Is there a way to get wifi to work on a custom rom on the ATT GS4 (MK2) because not matter what rom I flash on it the wifi always breaks but when I go back to stock it works just fine. I even tried flashing the modem file but to no avail. If I can't I can understand I was just wanting to know if there's a workaround to this. Thanks to anyone who helps .
You need to flash the MK2 modules. Do some more reading. The modules are in the Safestrap thread.
Sent from Black<3's I337 running Foxhound ROM
DeadlySin9 said:
You need to flash the MK2 modules. Do some more reading. The modules are in the Safestrap thread.
Sent from Black<3's I337 running Foxhound ROM
Click to expand...
Click to collapse
Well when I first tried to install a custom rom I used this website to flash the modules and that was when I realized my wifi wasn't working on it. I'll just read up some more I suppose. Thanks for the response .
Rytiou said:
Well when I first tried to install a custom rom I used this website to flash the modules and that was when I realized my wifi wasn't working on it. I'll just read up some more I suppose. Thanks for the response .
Click to expand...
Click to collapse
Those are all Verizon modules. You need the att ones
Edit, read through this. http://forum.xda-developers.com/showthread.php?p=45693712
jd1639 said:
Those are all Verizon modules. You need the att ones
Edit, read through this. http://forum.xda-developers.com/showthread.php?p=45693712
Click to expand...
Click to collapse
Aah I see. Thanks man
Hoping someone can help me ASAP. I was running sacs v3. I started getting issues when I opened up settings on my phone so I tried to dirty flash over the same ROM. Did that then had no network. Looked into that found it said to reflash NAE modem did that. But then I got a blue android guy. I am able to get into recovery when i try to install ROM it goes really fast then I reboot it says to fix root I say yes. Then it stalls on samsung galaxy S4 screen. Help please
eazy401 said:
Hoping someone can help me ASAP. I was running sacs v3. I started getting issues when I opened up settings on my phone so I tried to dirty flash over the same ROM. Did that then had no network. Looked into that found it said to reflash NAE modem did that. But then I got a blue android guy. I am able to get into recovery when i try to install ROM it goes really fast then I reboot it says to fix root I say yes. Then it stalls on samsung galaxy S4 screen. Help please
Click to expand...
Click to collapse
Can you ODIN back to NAE stock and see if that fixes it? Then try your ROM of choice after going back to complete stock?
VandyCWG said:
Can you ODIN back to NAE stock and see if that fixes it? Then try your ROM of choice after going back to complete stock?
Click to expand...
Click to collapse
I'm trying that right now
eazy401 said:
I'm trying that right now
Click to expand...
Click to collapse
Got it working by flashing Stock NAE rom thank you