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
Related
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.
can anybody help me im trying to overclock my samsung gs4 i337 im using twrp manager but when i try to load file it says twrp not responding. or should i be using odin insted .a link or a you tube video would be good. im trying to install kt-sg4-jb-mri-3.0 intl-05 from this site thanks ive wipe data wipe dalvik wipe data nothing hellllp 2 days now
None of what you said has anything to do with overclocking... In fact, none of it makes any sense at all.
You need to read the stickies before proceeding.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
graydiggy said:
None of what you said has anything to do with overclocking... In fact, none of it makes any sense at all.
You need to read the stickies before proceeding.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I think he is trying to flash a KT kernel... but is failing. Any ways with what he said.. sounds like a person that will be hard to help.
Sent from my GT-I9505 using Tapatalk 2
twrp
Febby said:
I think he is trying to flash a KT kernel... but is failing. Any ways with what he said.. sounds like a person that will be hard to help.
Sent from my GT-I9505 using Tapatalk 2
Click to expand...
Click to collapse
gee thanks guys just new at this
well, more info would help
what rom you on
what build number
it is the i337 att--right?
what twrp version you on and has it worked before for you or is this the first time you used twrp
i don't see a KT kernel with that name on this site or i9505 site
We understand that you are new at this. But you need to be more clear with us so we can provide help. You are holding a $650 phone and entrusting us with helping you modify it. More info is needed and more research is needed on your part. You need to be fully aware that you could end up with a expensive paperweight if something wee to go wrong. I tell this to most new comers. Rooting and custom ROMs are great. But not in the hands of someone that had no real idea of the consequences.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Here's the problem. You have incorrect punctuation in your post. Leads us to believe you have an i337 where from your other posts you say you have a i337m.
You need TMO kernels not one from "this" site
Maybe reflash your recovery, and still need to know what rom you are on as KT has kernels for TW and AOSP. I don't see any listings for "mri" so a link would help.
If you are doing things off the web--stop--and start using XDA for your info and downloads.
There are good Guides here to get you started.
Seems like when you have an issue you just ask someone for the solution, from reading your posts anyway--?
As graydiggy said, lots of reading required here to protect your investment--
rugmankc said:
Here's the problem. You have incorrect punctuation in your post. Leads us to believe you have an i337 where from your other posts you say you have a i337m.
You need TMO kernels not one from "this" site
Maybe reflash your recovery, and still need to know what rom you are on as KT has kernels for TW and AOSP. I don't see any listings for "mri" so a link would help.
If you are doing things off the web--stop--and start using XDA for your info and downloads.
There are good Guides here to get you started.
Seems like when you have an issue you just ask someone for the solution, from reading your posts anyway--?
As graydiggy said, lots of reading required here to protect your investment--
Click to expand...
Click to collapse
my phone is in fact a i337m telus canada im usingtwrp 2.6.0.0 i installed a volume booster with twrp manager ill read some more thanks guys
ron31 said:
my phone is in fact a i337m telus canada im usingtwrp 2.6.0.0 i installed a volume booster with twrp manager ill read some more thanks guys
Click to expand...
Click to collapse
Good Luck on it and keep in mind some folks have issues with 2.6.0.0. So if you do try 2.5.0.2. I have a recovery flashable zip for it and so does xBeerdroiDx in post 2 of his Guide in General.
Sent From My SGH-i337 Using Tapatalk 4
twrp help
ok ill change it twrp keeps saying twrp not responding thanks for the reply
EDIT
Oops--my zip for 2.5.0.2 is for i337--sorry
not sure if there is one for your phone
rugmankc said:
EDIT
Oops--my zip for 2.5.0.2 is for i337--sorry
not sure if there is one for your phone
Click to expand...
Click to collapse
thanks rugmankc i redownloaded the file the one you said i still used twrp 2.6.0.0 and it worked im now clocked at 2100 and also that k tweaker woooo is that loaded with settings wow thanks again
Glad You Got It :good:
Any word a Nightly or M Snapshot for the ATT G2?
Symbian_Black said:
Any word a Nightly or M Snapshot for the ATT G2?
Click to expand...
Click to collapse
ROMs take time to port. It isn't as simple as just changing a few config files and recompiling. There are proprietary drivers, etc. that have to be figured out first.
Be patient. It'll come.
Well no offense but until they create the port and include the features from stock your losing functionality not gaining speed.
Sent from my VS980 4G using XDA Premium 4 mobile app
Methinks that we all need to show a little patience. Feel free to correct me if I am wrong, but it is my belief that until we can unlock our bootloaders, we cannot flash third-party ROMs, no?
MarkAtHome said:
Methinks that we all need to show a little patience. Feel free to correct me if I am wrong, but it is my belief that until we can unlock our bootloaders, we cannot flash third-party ROMs, no?
Click to expand...
Click to collapse
We already have Loki, we can flash roms. IM currently running CleanRom on my G2.
tdevaughn said:
We already have Loki, we can flash roms. IM currently running CleanRom on my G2.
Click to expand...
Click to collapse
We do? I will search for it, as I did not find it during my regular reading. Thanks.
MarkAtHome said:
We do? I will search for it, as I did not find it during my regular reading. Thanks.
Click to expand...
Click to collapse
Look here, http://forum.xda-developers.com/showthread.php?t=2449670
part of the TWRP thread. The recovery is loki'd, but I kept the loki-master zip as well.. just to be safe
MarkAtHome said:
Methinks that we all need to show a little patience. Feel free to correct me if I am wrong, but it is my belief that until we can unlock our bootloaders, we cannot flash third-party ROMs, no?
Click to expand...
Click to collapse
No.
Also there is already a CM10.1 alpha build available. It doesnt do anything though and you dont even have data on it. As others said we need to get proprietary drivers and such sorted out to have anything usable. It will happen, just takes time. Hopefully Nexus 5 rumors are true because if so we will have a ton of great AOSP support really easily on this phone then too since drivers would be nearly (completely?) identical.
Bout how long do you guys think? The S4 was pretty fast to get a stable Cyanogen mod up
screw cm Omnirom is coming lol
I've hard bricked this thing once trying to flash a rom once. Tried to gain custom recovery via AUTOREC. Should be called Autowreck.
Sometimes it is best just to ask to be pointed in the right direction.
I just learned about LOKI and SAFESTRAP. BUT are these just for TW based ROMS? I want a CM based ROM. PACROM, specifically. I see others with this AT&T phone running it.
Will someone please help a noob with a tutorial or advice and stop me from running in circles? W/ rooted 4.4.2, NC1 build.
Start with reading well the SafeStrap thread by Hashcode in Q&A
and the All Thinks ATT, MK2 in General
You can only use SafeStrap and can not flash non TW roms or custom recoveries/kernels, so CM AOSP etc
Sorry
rugmankc said:
Start with reading well the SafeStrap thread by Hashcode in Q&A
and the All Thinks ATT, MK2 in General
You can only use SafeStrap and can not flash non TW roms or custom recoveries/kernels, so CM AOSP etc
Sorry
Click to expand...
Click to collapse
Been reading the safe strap thread. 89 pages! Stumped on the first one. ENCRYPTED? Not sure. How do I tell? Nb1, Mk2, Mf3 software? No idea. Did not see it in settings> about device. How do I tell is the next step I guess.
On to check the All Thinks Mk2 thread. Sorry for my noobness.
New Song said:
Been reading the safe strap thread. 89 pages! Stumped on the first one. ENCRYPTED? Not sure. How do I tell? Nb1, Mk2, Mf3 software? No idea. Did not see it in settings> about device. How do I tell is the next step I guess.
On to check the All Thinks Mk2 thread. Sorry for my noobness.
Click to expand...
Click to collapse
Get a terminal emulator on your phone. In it type:
su
getprop ro.bootloader
What does it say? Look at the last three characters
Edit, in about devices what is your baseband, last three characters?
Sent from my Nexus 5 using XDA Free mobile app
Sorry, I thought you NC1 now?
jd will get you sorted, he is more hands on with safestrap than i am
but, the gist of it is going to All Thinks ATT, MK2 and to post 5
but read all you can in both threads--:good:
Nc1. So this is the SafeStrap file: JFLTE-3.72-kk-B01.apk. How a bow the encryption determination? Sound like a bootloader if it is encrypted.
New Song said:
Nc1. So this is the SafeStrap file: JFLTE-3.72-kk-B01.apk. How a bow the encryption determination? Sound like a bootloader if it is encrypted.
Click to expand...
Click to collapse
Did you get nb1 from your baseband? Is your device encrypted? That's different than than the bootloader. Your bootloader is definitely locked. But you can root by updating to nc1 and using towelroot and then safestrap.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Did you get nb1 from your baseband? Is your device encrypted? That's different than than the bootloader. Your bootloader is definitely locked. But you can root by updating to nc1 and using towelroot and then safestrap.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
NC 1
I am rooted. SS installed. ROM DL'ed ready to go. Creating ROM slot. Or trying t seems stuck. I know it takes about 5 minutes. But it's been about 15-20
sorry for the pic quality. No zoom on this tab 4. It's next.
New Song said:
NC 1
I am rooted. SS installed. ROM DL'ed ready to go. Creating ROM slot. Or trying t seems stuck. I know it takes about 5 minutes. But it's been about 15-20
sorry for the pic quality. No zoom on this tab 4. It's next.
Click to expand...
Click to collapse
You have to use the stock slot, not a secondary slot
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You have to use the stock slot, not a secondary slot
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Aaaaand. S'S stopped working. Uninstalled, reinstalled and the same. Technology fails me.
New Song said:
Aaaaand. S'S stopped working. Uninstalled, reinstalled and the same. Technology fails me.
Click to expand...
Click to collapse
What are you trying to flash? PAC isn't going to work, it's cm based. You can only flash touch wiz based roms
Sent from my Nexus 5 using XDA Free mobile app
Anything else. I have Gravitron zip ready to go. But I cannot even get S'S to open now. "SafeStrap has stopped working". Even after attempted reinstalls. If there was someone here local I could just delegate this to, I would.
New Song said:
Anything else. I have Gravitron zip ready to go. But I cannot even get S'S to open now. "SafeStrap has stopped working". Even after attempted reinstalls. If there was someone here local I could just delegate this to, I would.
Click to expand...
Click to collapse
You probably have to use Odin to re-flash nb1 and start over
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
You probably have to use Odin to re-flash nb1 and start over
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
That may be. Got safestrap to start working by using se linu mode changer. Still stuck at updating partition details. Gonna start a thread on that I think. Maybe one on the search functions too.
New Song said:
That may be. Got safestrap to start working by using se linu mode changer. Still stuck at updating partition details. Gonna start a thread on that I think. Maybe one on the search functions too.
Click to expand...
Click to collapse
Just as an FYI, I've had very good results with Golden Eye installed via SafeStrap. No problems with it, whatsoever, in my experience. That being said, I'm tired of being restricted to touchwiz ROMs so I've bought a T-Mobile S4 (unlocked SIM/Bootloader) and will be selling my ATT one soon.
Marc
Frankenscript said:
Just as an FYI, I've had very good results with Golden Eye installed via SafeStrap. No problems with it, whatsoever, in my experience. That being said, I'm tired of being restricted to touchwiz ROMs so I've bought a T-Mobile S4 (unlocked SIM/Bootloader) and will be selling my ATT one soon.
Marc
Click to expand...
Click to collapse
Starting to feel the same way. Flashing this sgh-i337 is turning out to be quite an infuriating ordeal. So much conflicting info. Allllll these ROMs available for S4, it seems. But they don't work because this version isn't compatible. And the Tw ones I've tried ALL DAY are not working either. Granted, I was not using SS correctly initially, but now that they are successfully loading in the stock slot are not working. Graviton never boots, stays on the ouroboros snake screen. Imperium has no data or wifi etc (i9505 rom? I tried it as it said it was verified working 9th i337. Nope. Figured it was a problem when it said i9505 on my model). Goldeneye, actually can connect, wifi etc. But when I change settings in Wanam, it does not take them (after reboot). Had all the other connectivity issues until I flashed a patch. Also, I was pretty happy to see than I could activate hotspot. But my device was nowhere to be found by other devices. Modules, kernals, patches, oh my... out of all the tutorials for S4's on the wide wide world of internets, nothing seems to fly. This must be the red headed bastard child of Android.
I know it is all user error, but can nothing be simple?
Just want a simple rom and hotspot. That looks awesome. Hrm.
About to try this GE download. GE-XXUGNG4-37.zip. I tried the later NG-8-38 version last time. And yes, I did the ST update at&t module update previously.
Great googley moogley! I think he's finally got it, folks! Ooooh. Niiice. So smooth. Roomy!
This hacking biz ain't for the faint of heart. Thanks guys!!! MUCH APPRECIAT3D! :good:
Paraphrasing, I think, Tom Hanks
"It's suppose to hard, the hard is what makes it great. If it wasn't hard, everyone would do it."
:good:
rugmankc said:
Paraphrasing, I think, Tom Hanks
"It's suppose to hard, the hard is what makes it great. If it wasn't hard, everyone would do it."
:good:
Click to expand...
Click to collapse
Avoid the clap.... Jimmy Dugan.
Hey that's good advice kid....
I am looking to get rid of my htc one m8 and go back to Samsung. I know the s5 does not have an unlocked boot loader but it looks like custom roms can happen via safestrap. My question is, when buying the phone used, is there a specific software version i DO NOT want? The goal is to root, safestrap and then put some sort of custom rom on the phone.
Thanks
dougmod said:
I am looking to get rid of my htc one m8 and go back to Samsung. I know the s5 does not have an unlocked boot loader but it looks like custom roms can happen via safestrap. My question is, when buying the phone used, is there a specific software version i DO NOT want? The goal is to root, safestrap and then put some sort of custom rom on the phone.
Thanks
Click to expand...
Click to collapse
Currently you are good to go even on the latest NI2 update. You only need to downgrade the kernel to NCG via odin, run towel root, then reflash the newest NI2 kernel. There is a good write-up on it. Just look a few posts down.
BladeRunner said:
Currently you are good to go even on the latest NI2 update. You only need to downgrade the kernel to NCG via odin, run towel root, then reflash the newest NI2 kernel. There is a good write-up on it. Just look a few posts down.
Click to expand...
Click to collapse
Thanks for the reply. I'm so excited to get off of the m8. The reception is terrible.
I also see that the dev scene looks pretty limited in the Verizon section. Is that because everything has been unified like the s4 so I can pretty much use any rom? AOsp, cm, etc
dougmod said:
Thanks for the reply. I'm so excited to get off of the m8. The reception is terrible.
I also see that the dev scene looks pretty limited in the Verizon section. Is that because everything has been unified like the s4 so I can pretty much use any rom? AOsp, cm, etc
Click to expand...
Click to collapse
No, unfortunately, things are somewhat limited as the bootloader remains unlocked for the consumer edition so no custom kernels.
I think he meant to say the bootloader remains locked on the retail version.
Sent from my SM-G900V using XDA Free mobile app
kclive said:
I think he meant to say the bootloader remains locked on the retail version.
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
thanks, you are correct :silly: