I honestly don't know where to start, I bought the Samsung galaxy s4 i337m from virgin mobile, and use it with my Bell carrier. I was browsing the internet when I come to a video that states that you can flash i9505 roms on my i337/i337m phone! So silly of me to try that, it actually worked. When I was tired of that ROM, I go on this forum thread and look for another ROM, a ROM that is i337m cooked, and it soft bricked my phone, 3 times for 3 different i337m ROMS, at this point I have absolutely no clue what is going on with my phone, is the bootloader unlocked? WTF IS LOKI?? WHY does a i9505 ROM work on my phone, and a i337m cooked ROM does not, I just need some answers!! I have been flashing my phone with ROMs since my s1 and now the s4 comes along and completely wipes any knowledge I had before I got the phone, if anyone can help me on which ROMS I can and/or can't flash, that would be great, sorry for english not my first language!
Read and do some research. Just because you flashed a number of other phones doesn't mean you know how to flash this one. Every phone is different. It would also help to know what roms you flashed that didn't work.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
We are in trouble.
Loki is for locked bootloaders..which you do not have..you need to do some serious reading.
TheAxman said:
We are in trouble.
Loki is for locked bootloaders..which you do not have..you need to do some serious reading.
Click to expand...
Click to collapse
I still don't understand, I have the north american version of the i337m from Canada....
Dragosmp said:
I still don't understand, I have the north american version of the i337m from Canada....
Click to expand...
Click to collapse
What roms did you try to flash? Where did you get them? The boot loader is not locked and they should flash. Did you check the md5sum? They could be bad downloads.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Loki is needed for phones purchased through at&t. The Canadian version is the same phone, but without a locked boot loader, so the Loki hack is not needed.
What I have found is that some of the custom recoveries don't wipe out the phone properly. Try using Odin and go back to stock, wipe, then restart fresh
Also make sure you do a full wipe after flashing a Rom
Sent from my SGH-I337 using xda app-developers app
Matridom said:
Also make sure you do a full wipe after flashing a Rom
Sent from my SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
I'd do the full wipe before flashing. If you wipe after DON'T wipe system or you'll be in trouble.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Actually, I totally found that the Loki fix was needed for my Canadian i337m device (Bell). Many ROMs wouldn't work without it; they'd just get stuck in the boot logo (including SlimRom and CyanogenMod).
Just flash the ROM, then flash the Loki-Fix and you should be good to go.
If you're seriously stuck and you can't get back into your custom recovery, let me know and I'll help you out.
Now I am confused. Why would the I337m need a loki anything?
It is not needed. I surprised it even flashed.
TheAxman said:
Now I am confused. Why would the I337m need a loki anything?
Click to expand...
Click to collapse
I honestly have no idea; I just found that it worked for me. I was also very frustrated at first when I started flashing ROMs, until I tried the Loki Fix.
Te3k said:
I honestly have no idea; I just found that it worked for me. I was also very frustrated at first when I started flashing ROMs, until I tried the Loki Fix.
Click to expand...
Click to collapse
Do you know what your stock firmware was before you started flashing custom roms?
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Te3k said:
I honestly have no idea; I just found that it worked for me. I was also very frustrated at first when I started flashing ROMs, until I tried the Loki Fix.
Click to expand...
Click to collapse
U sure it is the canadian version? J/k. That is strange. What happens if you flash a rom and not the loki fix?
jd1639 said:
Do you know what your stock firmware was before you started flashing custom roms?
Click to expand...
Click to collapse
I didn't check the first time, but ever since I had to reflash to stock I started using this firmware: I337MVLUAMDJ_I337MOYAAMDJ_I337MVLUAMDJ_HOME and this kernel:
Samsung-Updates.com-KERNEL-SGH-I337M-BMC-I337MVLUAMDJ-1366643831. It was necessary for me to Odin back to stock completely a couple of times.
TheAxman said:
U sure it is the canadian version? J/k. That is strange. What happens if you flash a rom and not the loki fix?
Click to expand...
Click to collapse
If I flash a ROM but not the Loki Fix, one of the following scenarios happens: 1. the ROM gets stuck in a boot-loop (continually restarts), or 2. gets to the boot logo and stays there forever (10+ minutes). But if I reboot into recovery, wipe everything again, reflash the ROM and then the Loki Fix, the phone boots up in less than a minute. Is this very weird? The phone is i337m from Bell, Canada.
Te3k said:
I didn't check the first time, but ever since I had to reflash to stock I started using this firmware: I337MVLUAMDJ_I337MOYAAMDJ_I337MVLUAMDJ_HOME and this kernel:
Samsung-Updates.com-KERNEL-SGH-I337M-BMC-I337MVLUAMDJ-1366643831. It was necessary for me to Odin back to stock completely a couple of times.
If I flash a ROM but not the Loki Fix, one of the following scenarios happens: 1. the ROM gets stuck in a boot-loop (continually restarts), or 2. gets to the boot logo and stays there forever (10+ minutes). But if I reboot into recovery, wipe everything again, reflash the ROM and then the Loki Fix, the phone boots up in less than a minute. Is this very weird? The phone is i337m from Bell, Canada.
Click to expand...
Click to collapse
It behaves just like the locked boot loader on the US version.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jd1639 said:
It behaves just like the locked boot loader on the US version.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Strange. If it's relevant, I did encounter a lot of trouble sim-unlocking this phone for use on other networks. Using the Debug Menu on the phone's keypad didn't work as a method for me, although it had been reported to work for many others, including those with i337m's. I had to use a USB tether hack (FastGSM) to finally unlock the darn thing. Perhaps some models have locked bootloaders and others don't.
Te3k said:
Strange. If it's relevant, I did encounter a lot of trouble sim-unlocking this phone for use on other networks. Using the Debug Menu on the phone's keypad didn't work as a method for me, although it had been reported to work for many others, including those with i337m's. I had to use a USB tether hack (FastGSM) to finally unlock the darn thing. Perhaps some models have locked bootloaders and others don't.
Click to expand...
Click to collapse
Which custom recovery are you using to flash with and how did you get it on your phone?
Te3k said:
Strange. If it's relevant, I did encounter a lot of trouble sim-unlocking this phone for use on other networks. Using the Debug Menu on the phone's keypad didn't work as a method for me, although it had been reported to work for many others, including those with i337m's. I had to use a USB tether hack (FastGSM) to finally unlock the darn thing. Perhaps some models have locked bootloaders and others don't.
Click to expand...
Click to collapse
This is just not true. No way. Friggin way weird.
scott14719 said:
Which custom recovery are you using to flash with and how did you get it on your phone?
Click to expand...
Click to collapse
Using Open Recovery, and put it on the phone via an ADB interface (over USB debugging) using the Canadian i337m "3way" .BAT tool (root/CWM/OpenRecov).
And Axman, I just don't know what to say, lol!
Te3k said:
Using Open Recovery, and put it on the phone via an ADB interface (over USB debugging) using the Canadian i337m "3way" .BAT tool (root/CWM/OpenRecov).
And Axman, I just don't know what to say, lol!
Click to expand...
Click to collapse
You are the first. When you were on stock, what did it identify the phone as?
What does the model # say under the battery?
---------- Post added at 07:33 PM ---------- Previous post was at 07:30 PM ----------
Te3k said:
Using Open Recovery, and put it on the phone via an ADB interface (over USB debugging) using the Canadian i337m "3way" .BAT tool (root/CWM/OpenRecov).
And Axman, I just don't know what to say, lol!
Click to expand...
Click to collapse
And this procedure worked for you? You said you had to loki, where did that come in?
TheAxman said:
You are the first. When you were on stock, what did it identify the phone as?
What does the model # say under the battery?
And this procedure worked for you? You said you had to loki, where did that come in?
Click to expand...
Click to collapse
Phone identified as i337m from settings menu prior to any flashing. Model number under battery matches: Model: SGH-I337M / IC: 649E-I337M.
Using Loki came in where I found that flashing ROMs wasn't working. I had already rooted and tried to unlock the phone through the debug menu. Unlocking didn't work, but rooting did and I could load custom recoveries without problem. I thought that I should try flashing other ROMs to see if I could unlock the device through their debug menus, but no luck. The first ROM I tried to flash was a SlimRom nightly. That one appeared to flash properly (recovery said "success"), but upon reboot I got stuck in a boot loop. I then went back to recovery and messed around trying to flash other ROMs and ran into the same issue persistently. I eventually panicked and Odined back to stock ROM and kernel (numbers previously mentioned). Everything was fine after I figured out how to make Odin work. (I even learned how to make signed-MD5 tarballs with Cygwin to try to make flashing recoveries and roots simpler by using Odin.) After wondering why I couldn't flash any custom ROMs, I dug around a bit and found out that some ROMs' first-posts mentioned that certain fixes had to be applied—some of which were labelled ROM-specific (e.g. GOLDENEYE-i337m-FiX-XXUBMF8) and others that just said that they required a Loki fix, and sometimes provided a link to download it. At the time I didn't know what Loki was, and I wasn't understanding why certain ROMs would come pre-"Lokified" (brain was full after hacking around for >6h). So in the moment it made no sense not to try flashing that to see if it would help. Lo and behold, it worked! I started flashing Loki after every ROM install from then on out. Previously not-working ROMs that I had already tried suddenly worked just fine (I didn't redownload them; I kept the same zip files and just started flashing the Loki Fix after each of them to make them work).
It's still the case that when I want to flash a new ROM, I wipe everything from recovery and flash the ROM. If it doesn't boot, I flash the Loki Fix and then it does boot properly.
Related
I really love tasks ROM and want to pick up the S4. Can I run the recovery with auto Loki on my Canadian variant, so that I can run ATT roms? I am not completely up to speed on whether that is possible...
Sent from my SGH-I747 using xda premium
Manufactured consent said:
I really love tasks ROM and want to pick up the S4. Can I run the recovery with auto Loki on my Canadian variant, so that I can run ATT roms? I am not completely up to speed on whether that is possible...
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
You don't need to follow the Loki recovery instructions since your bootloader is already unlocked, just flash the ROM according to the OP instructions.
Manufactured consent said:
I really love tasks ROM and want to pick up the S4. Can I run the recovery with auto Loki on my Canadian variant, so that I can run ATT roms? I am not completely up to speed on whether that is possible...
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
If you're not up to speed then I recommend searching the forum before asking lol :silly:
Anyways no, you don't run Loki-fied files on the canadian variants. Also I believe Task650 isn't loki-fying his ROM anymore and is strictly leaving it up to OUDHS Recov to apply the loki patch. If this is the case, all you need to do is use TWRP and flash the ROM. Again though I can't say for sure and you're gonna have to actually read his thread.
Thermalwolf said:
If you're not up to speed then I recommend searching the forum before asking lol :silly:
Anyways no, you don't run Loki-fied files on the canadian variants. Also I believe Task650 isn't loki-fying his ROM anymore and is strictly leaving it up to OUDHS Recov to apply the loki patch. If this is the case, all you need to do is use TWRP and flash the ROM. Again though I can't say for sure and you're gonna have to actually read his thread.
Click to expand...
Click to collapse
The aboot.img in the ROM MUST be patched for it to run on ATT phones. It doesn't matter either way with a Canadian variant.
LostInMyHead said:
The aboot.img in the ROM MUST be patched for it to run on ATT phones. It doesn't matter either way with a Canadian variant.
Click to expand...
Click to collapse
My bad you're right, I didn't realize I only said canadian.
Thermalwolf said:
My bad you're right, I didn't realize I only said canadian.
Click to expand...
Click to collapse
It's all good man. We ATT folks can also run non-patched ROMs but must flash a patched kernel just afterwards.
LostInMyHead said:
It's all good man. We ATT folks can also run non-patched ROMs but must flash a patched kernel just afterwards.
Click to expand...
Click to collapse
Yep, also doesn't OUDHS Recovery automatically loki patch flashed files now? If this is the case then we won't even need to loki patch a darn thing, just flash and be on our marry way
Thermalwolf said:
Yep, also doesn't OUDHS Recovery automatically loki patch flashed files now? If this is the case then we won't even need to loki patch a darn thing, just flash and be on our marry way
Click to expand...
Click to collapse
ATM no it doesn't, the ROM still needs patching. For ROMs like CM and SLIM, they are working on a way for them to be patched automatically for their nightlies / weeklys.
I just read a couple of posts by peeps saying that at the moment Task's rom will still not work on Canadian variant....
Sent from my SGH-I747 using xda premium
So would we (canadian users) have issues trying to flash the roms that rely on auto loki? Is there any chance of brick or things like that or is it relatively safe to just try it and see?
Manufactured consent said:
I just read a couple of posts by peeps saying that at the moment Task's rom will still not work on Canadian variant....
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
Firestar292 said:
So would we (canadian users) have issues trying to flash the roms that rely on auto loki? Is there any chance of brick or things like that or is it relatively safe to just try it and see?
Click to expand...
Click to collapse
I honestly see no reason why it can't be flashed to a Canadian S4. Task usually only supports his carrier though.
Also, if bricking were an issue, I'm pretty sure it would be a huge disclaimer in the Loki FAQ
LostInMyHead said:
I honestly see no reason why it can't be flashed to a Canadian S4. Task usually only supports his carrier though.
Also, if bricking were an issue, I'm pretty sure it would be a huge disclaimer in the Loki FAQ
Click to expand...
Click to collapse
I don't mean only tasks rom, I'm concerned for basically all roms that us canadian users are going to get left out
Thanks for the reply.. I think I'll give it a try
Firestar292 said:
I don't mean only tasks rom, I'm concerned for basically all roms that us canadian users are going to get left out
Thanks for the reply.. I think I'll give it a try
Click to expand...
Click to collapse
EDIT - I have been told by a Slim Developer that flashing a Loki ROM to a non-Loki device will result in a bootloop. I apologize for the misinformation.
LostInMyHead said:
EDIT - I have been told by a Slim Developer that flashing a Loki ROM to a non-Loki device will result in a bootloop. I apologize for the misinformation.
Click to expand...
Click to collapse
Ok no problem.. But if it's meant to be auto loki'd is it still edited as a loki rom, or is it completely normal?
LostInMyHead said:
EDIT - I have been told by a Slim Developer that flashing a Loki ROM to a non-Loki device will result in a bootloop. I apologize for the misinformation.
Click to expand...
Click to collapse
Yeah, that's why I am a little confused. It seems I am getting mixed information. But I noticed task took Loki out of his title, that's why I was curious about how fast this is evolving and what has changed
Sent from my SGH-I747 using xda premium
Firestar292 said:
Ok no problem.. But if it's meant to be auto loki'd is it still edited as a loki rom, or is it completely normal?
Click to expand...
Click to collapse
Manufactured consent said:
Yeah, that's why I am a little confused. It seems I am getting mixed information. But I noticed task took Loki out of his title, that's why I was curious about how fast this is evolving and what has changed
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
ATM, an ATT phone must be running a Loki recovery, and the ROM must be Loki patched, unless you flash non-Loki ROM, then a Loki Kernel.
Flashing a Loki ROM to a Canadian phone will bootloop. I will try to ask Task about his ROM.
@Manufactured consent
Since your bootloader is unlocked, and I see no mention of Task's ROM being Loki patched, you should just be able to flash it.
You can flash it but it won't be supported. Task won't support anything he can't test. Questions about it just derails the thread.
Sent from my SAMSUNG-SGH-I337 using xda premium
Does having a custom recovery mean your bootloader is unlocked? I have TRWP installed, in download mode it says samsung offical yada yada.
The boot loader is not unlocked. Do some more reading about your phone before you start doing something with your custom recovery. Many people have bricked their phones because they did not understand what they were doing. There is a lot of good advice here. Look for threads by axman, adamoutler,beerdriod, to name a few. They'll keep you out of trouble. Just some friendly advice
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
jd1639 said:
The boot loader is not unlocked. Do some more reading about your phone before you start doing something with your custom recovery. Many people have bricked their phones because they did not understand what they were doing. There is a lot of good advice here. Look for threads by axman, adamoutler,beerdriod, to name a few. They'll keep you out of trouble. Just some friendly advice
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
I know that the boot loader is not unlocked but rather is a patch. What I'm asking is is having a custom recovery make it safe to flash a rom.
AdePower said:
I know that the boot loader is not unlocked but rather is a patch. What I'm asking is is having a custom recovery make it safe to flash a rom.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2292157
AdePower said:
I know that the boot loader is not unlocked but rather is a patch. What I'm asking is is having a custom recovery make it safe to flash a rom.
Click to expand...
Click to collapse
The post above has a great link for you to research.
Basically, having a custom recovery means that you can flash roms that have had the loki patch applied to them or you can flash roms from similar hardware then flash a kernel that has been loki patched, or you can flash a rom from similar hardware using a recovery that has auto loki, or you can flash a rom from similar hardware and follow that by flashing loki-doki.zip.
Plenty of options, but if you have to ask, you shouldn't be flashing, Read the link above and everything else you can about loki and the att i337. Making a mistake with a brand new cellphone can be costly so research is imperative.
Not trying to discourage you from trying a custom rom, just trying to let you know that there's a lot of information you should have first.
acruxksa said:
The post above has a great link for you to research.
Basically, having a custom recovery means that you can flash roms that have had the loki patch applied to them or you can flash roms from similar hardware then flash a kernel that has been loki patched, or you can flash a rom from similar hardware using a recovery that has auto loki, or you can flash a rom from similar hardware and follow that by flashing loki-doki.zip.
Plenty of options, but if you have to ask, you shouldn't be flashing, Read the link above and everything else you can about loki and the att i337. Making a mistake with a brand new cellphone can be costly so research is imperative.
Not trying to discourage you from trying a custom rom, just trying to let you know that there's a lot of information you should have first.
Click to expand...
Click to collapse
Its just confusing. I've been flashing roms since my HTC HD2 days, yet im still confused about this phone. I guess, ill just have to read some more. Seems to complicated.
AdePower said:
Its just confusing. I've been flashing roms since my HTC HD2 days, yet im still confused about this phone. I guess, ill just have to read some more. Seems to complicated.
Click to expand...
Click to collapse
Once you get the hang of it, it's not that difficult. It's just slightly different than flashing with an unlocked boot loader. The main difference it that whatever you flash has to have a kernel with the loki patch applied before rebooting out of recovery. The patch can be applied to the roms kernel before you flash, it can be applied to the roms kernel by the recovery you use to flash, it can be applied by flashing a loki patched kernel after flashing the rom, or it can be applied by flashing loki-doki after flashing the rom.
The roms come from identical snapdragon 600 equipped S4's, not the octa-core models and you apply the loki patch as needed with one of the methods above.
essentially it's an extra step in the process with several different places you can put it.
If you've flashed other roms, it won't take too much reading before you get the hang of it, but it's still best to put a little time into research before pulling the trigger.
acruxksa said:
Once you get the hang of it, it's not that difficult. It's just slightly different than flashing with an unlocked boot loader. The main difference it that whatever you flash has to have a kernel with the loki patch applied before rebooting out of recovery. The patch can be applied to the roms kernel before you flash, it can be applied to the roms kernel by the recovery you use to flash, it can be applied by flashing a loki patched kernel after flashing the rom, or it can be applied by flashing loki-doki after flashing the rom.
The roms come from identical snapdragon 600 equipped S4's, not the octa-core models and you apply the loki patch as needed with one of the methods above.
essentially it's an extra step in the process with several different places you can put it.
If you've flashed other roms, it won't take too much reading before you get the hang of it, but it's still best to put a little time into research before pulling the trigger.
Click to expand...
Click to collapse
So the best option would be the recovery that applies the patch automatically correct?
AdePower said:
So the best option would be the recovery that applies the patch automatically correct?
Click to expand...
Click to collapse
It is the easiest way yes.
AdePower said:
Its just confusing. I've been flashing roms since my HTC HD2 days, yet im still confused about this phone. I guess, ill just have to read some more. Seems to complicated.
Click to expand...
Click to collapse
It is easier than the HD2, I had that phone, and it was a nightmare to flash, it is not confusing, I give a STEP BY STEP in my guide, how easy is it...
5 step flash process...I don't get it, HOW HARD CAN IT BE?
here is an example...
1 - get a bowl
2 - open the box of cereal
3 - pour cereal in bowl
4 - add milk to cereal
5 - eat cereal and enjoy
it is NO DIFFERENT than that. If you can do that, you can flash roms.
go here, if you can't do this, then you need to keep your phone stock forever.
http://forum.xda-developers.com/showthread.php?t=2295557
I will help you, although, I can't flash it for you, you must pay attention.
good luck sir.
TheAxman said:
It is easier than the HD2, I had that phone, and it was a nightmare to flash, it is not confusing, I give a STEP BY STEP in my guide, how easy is it...
5 step flash process...I don't get it, HOW HARD CAN IT BE?
here is an example...
1 - get a bowl
2 - open the box of cereal
3 - pour cereal in bowl
4 - add milk to cereal
5 - eat cereal and enjoy
it is NO DIFFERENT than that. If you can do that, you can flash roms.
...
Click to expand...
Click to collapse
I've tried this, but all I get is cereal. I've repeated it exactly as written like 15 times and I think I going to be sick.
I am confused to why everyone has this problem, it is crazy. I am like you, it is embedded into my brain, my wife had to wake me up one time, because she said I kept saying flash it, flash it, over and over. Oh well.
I have seen some people, they don't like going through all the posts to find an answer, back in my early days they included a new feature called BOOKMARKS...I ask myself, what does that do...hmm it takes me to places that I have been before, that dare I say...dare dare.. explain what to do so I could reference back.
Hey guys. So i've been beating my head against the wall here, trying to search ( yes as in using google and the xda search ) for a solution.
I keep trying to flash stock based samsung roms, they would flash, but when i try to open the camera, it opens but it freezes and then comes back saying camera failed. So I wait about 10 minutes, and the camera works...but only for about a minute, then it freezes and then never opens again.
I've tried flashing all of faux123 kernels, only one worked ( 006-MDX ) but the camera still has issues and I can't seem to find any other kernels compatible with the I337M.
Anyways, I've now tried flashing a I337M firmware based custom rom and it boots but now there it just wont boot up at all, just gets to the samsung logo and sits there, I've tried flashing other kernels but nothing will help. I'm going to have to Odin back to stock, but I'm wondering what Kernels are ok to use with the I337M so that this doesn't happen to me again in the future.
Any help and I'll have my thanks finger ready
EDIT: Ok, so after some poking around, it seems that T-Mobile kernels work well with the I337M. Can anyone confirm this for me before I bork my device again? (currently doing an odin back to stock and re-rooting... =(
It is not wise to use other carriers kernels. Not a good idea. The att i337m kernels are just as good as the others. How would you benefit from it?
Btw the answer to your problem is you have the wrong kernel. Get into recovery and flash the kernel for your device.
TheSmokingAndroid said:
Hey guys. So i've been beating my head against the wall here, trying to search ( yes as in using google and the xda search ) for a solution.
I keep trying to flash stock based samsung roms, they would flash, but when i try to open the camera, it opens but it freezes and then comes back saying camera failed. So I wait about 10 minutes, and the camera works...but only for about a minute, then it freezes and then never opens again.
I've tried flashing all of faux123 kernels, only one worked ( 006-MDX ) but the camera still has issues and I can't seem to find any other kernels compatible with the I337M.
Anyways, I've now tried flashing a I337M firmware based custom rom and it boots but now there it just wont boot up at all, just gets to the samsung logo and sits there, I've tried flashing other kernels but nothing will help. I'm going to have to Odin back to stock, but I'm wondering what Kernels are ok to use with the I337M so that this doesn't happen to me again in the future.
Any help and I'll have my thanks finger ready
EDIT: Ok, so after some poking around, it seems that T-Mobile kernels work well with the I337M. Can anyone confirm this for me before I bork my device again? (currently doing an odin back to stock and re-rooting... =(
Click to expand...
Click to collapse
9505 kernels work. Flash Adam kernel directly after flashing the ROM. If you still have problems with the camera, flash ROM, go into camera and let it update firmware, immediately flash Adam kernel then reboot.
blyndfyre said:
9505 kernels work. Flash Adam kernel directly after flashing the ROM. If you still have problems with the camera, flash ROM, go into camera and let it update firmware, immediately flash Adam kernel then reboot.
Click to expand...
Click to collapse
Ya, I've done the whole adam kernel in the past, updated the camera firmware, everything was fine, but this time around, the firmware didn't need updating, at least i don't think so, considering the camera app launches, but sits at a black screen and then gives me a message that camera failed. it never tries to update the firmware like it did in the past. thanks though =)
TheAxman said:
It is not wise to use other carriers kernels. Not a good idea. The att i337m kernels are just as good as the others. How would you benefit from it?
Btw the answer to your problem is you have the wrong kernel. Get into recovery and flash the kernel for your device.
Click to expand...
Click to collapse
Ya, I have been trying the correct firmwares for my device and nothing seems to fix it, thanks though
TheAxman said:
It is not wise to use other carriers kernels. Not a good idea. The att i337m kernels are just as good as the others. How would you benefit from it?
Btw the answer to your problem is you have the wrong kernel. Get into recovery and flash the kernel for your device.
Click to expand...
Click to collapse
Most of the AT&T kernels are Loki :s... with a custom recovery that auto Loki I don't understand why to Loki a Rom... besides making it only for AT&T :s
I have a stock kernel that I backed up with twrp... the rest are T-Mobile
Sent from my i337M
blyndfyre said:
9505 kernels work. Flash Adam kernel directly after flashing the ROM. If you still have problems with the camera, flash ROM, go into camera and let it update firmware, immediately flash Adam kernel then reboot.
Click to expand...
Click to collapse
Wait, on the unlocked bootloader devices, you mean the other carriers kernels is ok to flash? man, I seriously wish our att was unlocked, this is good to know thanks.
---------- Post added at 07:23 AM ---------- Previous post was at 07:21 AM ----------
TheSmokingAndroid said:
Ya, I've done the whole adam kernel in the past, updated the camera firmware, everything was fine, but this time around, the firmware didn't need updating, at least i don't think so, considering the camera app launches, but sits at a black screen and then gives me a message that camera failed. it never tries to update the firmware like it did in the past. thanks though =)
Ya, I have been trying the correct firmwares for my device and nothing seems to fix it, thanks though
Click to expand...
Click to collapse
I stand corrected, your device from the post earlier says you can use other kernels. what a concept.
TheAxman said:
Wait, on the unlocked bootloader devices, you mean the other carriers kernels is ok to flash? man, I seriously wish our att was unlocked, this is good to know thanks.
Click to expand...
Click to collapse
Yeah us SGH-I337M users can use other device ROM's and Kenels. (Doubt not the 9500 because of hardware differences)
We pay for our unlocked bootloader in outrageous plans from our mobile providers though!
im in winnipeg here on the i337m rogers and have no problem with the kernal in my signature
blyndfyre said:
Yeah us SGH-I337M users can use other device ROM's and Kenels. (Doubt not the 9500 because of hardware differences)
We pay for our unlocked bootloader in outrageous plans from out mobile providers though!
Click to expand...
Click to collapse
I can imagine, I still have a g3 that is in working order with a sim, and it is cool to see the loader unlocked. although on the g4, as long as I can flash a rom, I do not care how it works. I am a happy camper right now.
Thanks for clearing up the kernel question I had, can use that info when helping others. Thanks.
TheAxman said:
I can imagine, I still have a g3 that is in working order with a sim, and it is cool to see the loader unlocked. although on the g4, as long as I can flash a rom, I do not care how it works. I am a happy camper right now.
Thanks for clearing up the kernel question I had, can use that info when helping others. Thanks.
Click to expand...
Click to collapse
I guess with LOKI you are still set, the biggest drawback with the locked bootloader is probably slower device reboots, as you see the custom screen?
Your welcome about the kernel question I always see you helping others. Fell free to toss me a thanks.
blyndfyre said:
I guess with LOKI you are still set, the biggest drawback with the locked bootloader is probably slower device reboots, as you see the custom screen?
Your welcome about the kernel question I always see you helping others. Fell free to toss me a thanks.
Click to expand...
Click to collapse
I have no problem on the thanks, but I have none left today, you and another killed em up...I will catch you though.
Thanks, here, and 1 a coming.
Could somebody please share a link to download Rogers/Fido stock kernel (rooted or not rooted) for i337M please ?
Thanks!
fmark said:
Could somebody please share a link to download Rogers/Fido stock kernel (rooted or not rooted) for i337M please ?
Thanks!
Click to expand...
Click to collapse
Thread containing Canadian SGH-i337m stock firmware and kernels:
http://forum.xda-developers.com/showthread.php?t=2269304
Link to Rogers kernel:
http://hotfile.com/dl/215149326/c15...GH-I337M-RWC-I337MVLUAMDJ-1366643831.tar.html
Realizing I can't unlock my bootloader via motopocalypse because its latest OTA and I can't GSM unlock it for use on US carriers. Am I stuck on stock with Verizon?
xlxcrossing said:
Realizing I can't unlock my bootloader via motopocalypse because its latest OTA and I can't GSM unlock it for use on US carriers. Am I stuck on stock with Verizon?
Click to expand...
Click to collapse
You can GSM unlock regardless of OTA version. There are a few stock-based ROMs out there for Safestrap once you root.
Sent from my XT907 using Tapatalk 4
OK I didn't have any luck with the radiocomm app and editing the nv item. I have root currently but that's it. I've never flashed a ROM without an unlocked bootloader so can you direct as to how this works as well as describing "safestrap".
xlxcrossing said:
OK I didn't have any luck with the radiocomm app and editing the nv item. I have root currently but that's it. I've never flashed a ROM without an unlocked bootloader so can you direct as to how this works as well as describing "safestrap".
Click to expand...
Click to collapse
http://blog.hash-of-codes.com/how-to-safestrap/
Thanks for the info. One question. Since virtual ROM slots use storage as would the stock system am I able to create a virtual ROM, install a custom ROM and delete the stock system?
I've used safe strap on the og RAZR and the d4... it does use the internal SD storage space... and I do not believe you can delete the stock slot nor flash anything on the stock slot... tho it may differ on this device...
Sent from my XT907 using xda app-developers app
xlxcrossing said:
Thanks for the info. One question. Since virtual ROM slots use storage as would the stock system am I able to create a virtual ROM, install a custom ROM and delete the stock system?
Click to expand...
Click to collapse
I wouldn't do that because the ROM slots depend on the stock boot.img to run. However, there is a restore procedure that should work. You can set up a slot, flash the ROM, set it up, and then back it up. Once you have it backed it up, you can restore (not flash) over your stock slot. Then you can delete the custom slot. I've never used this procedure, but I have seen quite a few people do this with success.
I see you're saying you can end up using your stock slot through this method. Basically what I want to know is if I flash a ROM on a virtual slot does my old stock ROM just sit on my sys partition without being used?
xlxcrossing said:
I see you're saying you can end up using your stock slot through this method. Basically what I want to know is if I flash a ROM on a virtual slot does my old stock ROM just sit on my sys partition without being used?
Click to expand...
Click to collapse
Yeah, supposedly you can use your stock slot. I'll post the link to the post on DroidRzr.com where it's discussed. Don't quote me on this, but I think it does sit there unused. The other slots only use its boot image. I'm pretty positive it doesn't do anything else when you boot into the safe side.
http://www.droidrzr.com/index.php/topic/11600-installing-custom-rom-to-stock-using-ss-312/
That app didn't work for me at all. Each time I installed to a ROM slot it would boot to a black screen, couldn't ever get a ROM to load. A bunch of people had the same issue. Tried reinstalling the slot multiple times before giving up. This phone has given me hell since I got it. Motorola phones are really locked down.
xlxcrossing said:
That app didn't work for me at all. Each time I installed to a ROM slot it would boot to a black screen, couldn't ever get a ROM to load. A bunch of people had the same issue. Tried reinstalling the slot multiple times before giving up. This phone has given me hell since I got it. Motorola phones are really locked down.
Click to expand...
Click to collapse
What ROMs were you trying? There are very few SS compitble ROMs out there. The app can still work for you, as far as making backups,etc.
I tried slimbean. I didn't know there was a requisite for what ROM you could flash. I'm selling the phone I'm not terribly concerned any more.
xlxcrossing said:
I tried slimbean. I didn't know there was a requisite for what ROM you could flash. I'm selling the phone I'm not terribly concerned any more.
Click to expand...
Click to collapse
Yeah, with SS you can only flash SS compatible ROMs. Slim Bean is not SS compatible. Either way, good luck with the sale.
RikRong said:
I wouldn't do that because the ROM slots depend on the stock boot.img to run. However, there is a restore procedure that should work. You can set up a slot, flash the ROM, set it up, and then back it up. Once you have it backed it up, you can restore (not flash) over your stock slot. Then you can delete the custom slot. I've never used this procedure, but I have seen quite a few people do this with success.
Click to expand...
Click to collapse
I asked about this before and couldn't get confirmation that this could be done. Suppose someone on droidrzr.com might know for sure? I want to do just as you say with a debloated stock "plus goodies" ROM and then restore over the stock slot.
HemRoyd said:
I asked about this before and couldn't get confirmation that this could be done. Suppose someone on droidrzr.com might know for sure? I want to do just as you say with a debloated stock "plus goodies" ROM and then restore over the stock slot.
Click to expand...
Click to collapse
The person that did the write up on DroidRzr did it and know other people have done it. I never did it but it makes sense that it should work. Just have utility or XML ready if something goes bad.
With a rooted, but locked bootloader, I will still be able to flash a SS rom that allows me to tether?
At this point, that and debloating are my main reasons for rooting.
I'm looking to upgrade from a Thunderbolt to a Razr M. I want to make sure I'm not trading one set of problems for a new set.
FirePsych said:
With a rooted, but locked bootloader, I will still be able to flash a SS rom that allows me to tether?
At this point, that and debloating are my main reasons for rooting.
I'm looking to upgrade from a Thunderbolt to a Razr M. I want to make sure I'm not trading one set of problems for a new set.
Click to expand...
Click to collapse
Yep. You can tether on stock actually... If you're on a share everything, you get it out of the box, otherwise you need to do a hack using sqlite editor or something
Sent from my Nexus 7 using Tapatalk 4
So which ROMs are safestrap compatabile with the locked bootloader? I am trying to help a friend with his phone unfortunately he took the ota update and his bootloader will stay locked for the moment. That said I rooted and installed safestrap so I'm looking to install a compatible ROM and get this phone on straight talk with a ST SIM card. Any suggestions?
Sent from my XT875 using XDA Premium 4 mobile app
So I'll start by saying I made a boo boo and this is 100% my fault.
I rooted my stock D800 and flashed TWRP. I flashed Cyanogenmod but where I messed is up when I flashed the D802 ROM and not the D800. I figured I'd just boot into recovery again using the hardware buttons, but all that happens is the screen turns on but nothing actually displays.
After that, I figured I'd just flash a stock ROM and basically start over using Download Mode and FlashTool. Unfortunately, I can't flash the stock firmware because the phone is NOT identifying itself as a D800, it's identifying as a D802, so FlashTool will not allow me to flash the proper files.
What I don't understand is why was I able to get into TWRP that one instance and flash the ROM but now whenever I attempt to get into recovery again the screen just turns on but recovery doesn't show. Makes no sense to me. I've tried getting into recovery using the hardware buttons a million times after but no dice.
I know it's not much, but I'm willing to throw in 10 bucks via PayPal for whoever can help me fix this.
bbeaulieu said:
So I'll start by saying I made a boo boo and this is 100% my fault.
I rooted my stock D800 and flashed TWRP. I flashed Cyanogenmod but where I messed is up when I flashed the D802 ROM and not the D800. I figured I'd just boot into recovery again using the hardware buttons, but all that happens is the screen turns on but nothing actually displays.
After that, I figured I'd just flash a stock ROM and basically start over using Download Mode and FlashTool. Unfortunately, I can't flash the stock firmware because the phone is NOT identifying itself as a D800, it's identifying as a D802, so FlashTool will not allow me to flash the proper files.
What I don't understand is why was I able to get into TWRP that one instance and flash the ROM but now whenever I attempt to get into recovery again the screen just turns on but recovery doesn't show. Makes no sense to me. I've tried getting into recovery using the hardware buttons a million times after but no dice.
I know it's not much, but I'm willing to throw in 10 bucks via PayPal for whoever can help me fix this.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2582845 This ROM is compatible with both d800 and d802 variants. You can try flashing this just to get your phone up and running
Art Vanderlay said:
http://forum.xda-developers.com/showthread.php?t=2582845 This ROM is compatible with both d800 and d802 variants. You can try flashing this just to get your phone up and running
Click to expand...
Click to collapse
Unfortunately I can't do that because I can't get into recovery mode
Im in the same situation as you bro. Tried to use LG flash tools to flash my sprint back to stock and its detecting my phone as a d801. No help yet
same here from 2 weeks..
EVERYONE! I have found a resolution for this.
First, visit this thread.
Download the DLL from this post and flash with a normal stock ROM. I used this combo and it flashed WITHOUT issue. Hope it helps you guys out as well.
bbeaulieu said:
EVERYONE! I have found a resolution for this.
First, visit this thread.
Download the DLL from this post and flash with a normal stock ROM. I used this combo and it flashed WITHOUT issue. Hope it helps you guys out as well.
Click to expand...
Click to collapse
Yeah this should Definitely be in a FAQ somewhere
Sent from my LG-D800 using xda app-developers app
afrojoc said:
Yeah this should Definitely be in a FAQ somewhere
Sent from my LG-D800 using xda app-developers app
Click to expand...
Click to collapse
No you guys just need to slow down.
Sent from my SCH-I545 using XDA Premium 4 mobile app
JCBiznatch said:
No you guys just need to slow down.
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So it doesn't need to be in FAQ somewhere?Lol it would've helped me out dramatically! It's not my fault that there are recoveries that mess up your phone. Coming from Samsung phones I didn't think that someone would release faulty software that would render your phone unusable.