[Q] Cyanogenmod for ATT G2? - G2 Q&A, Help & Troubleshooting

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

Related

So, i want to root, but I have a couple of questions

I noticed that looking at a blank white page on my Nexus 4 that it wasn't as white as I would love. So I searched and found out I could calibrate it.
I prefer not to use a different kernel, so I would like to use this app: https://play.google.com/store/apps/details?id=com.nexus4displaycontrol
Question #1: Is that app good? Like would it fix my problem?
Question #2: I would like to get updates from Google as well, how does that work with a rooted phone? Will I lose my calibration once I update?
That's all the questions I have.
Thanks!
thenerdal said:
I noticed that looking at a blank white page on my Nexus 4 that it wasn't as white as I would love. So I searched and found out I could calibrate it.
I prefer not to use a different kernel, so I would like to use this app: https://play.google.com/store/apps/details?id=com.nexus4displaycontrol
Question #1: Is that app good? Like would it fix my problem?
Question #2: I would like to get updates from Google as well, how does that work with a rooted phone? Will I lose my calibration once I update?
That's all the questions I have.
Thanks!
Click to expand...
Click to collapse
Yes, check his thread for the kernel a well. http://forum.xda-developers.com/showthread.php?t=2002782
A custom rom will probably give you the Google updates faster. But, you'll be able to get updates as well, yes.
Vangelis13 said:
Yes, check his thread for the kernel a well. http://forum.xda-developers.com/showthread.php?t=2002782
A custom rom will probably give you the Google updates faster. But, you'll be able to get updates as well, yes.
Click to expand...
Click to collapse
What's a kernel? Is it like a Linux Kernel? This seems complicated to me. :| Like if I mess up, I'll mess up my phone. What does this kernel do?
And yeah, I was looking at custom rom's. cyanogenmod specifically, but they're doing nightly updates, so I'm worried that if I do use that rom, it'll be buggy and mess up my phone.
thenerdal said:
What's a kernel? Is it like a Linux Kernel? This seems complicated to me. :| Like if I mess up, I'll mess up my phone. What does this kernel do?
And yeah, I was looking at custom rom's. cyanogenmod specifically, but they're doing nightly updates, so I'm worried that if I do use that rom, it'll be buggy and mess up my phone.
Click to expand...
Click to collapse
Oh boy, you have some catching up to do.. Start here http://forum.xda-developers.com/showthread.php?t=2010338
Roms aren't buggy nowadays, you'll be ok.
Vangelis13 said:
Oh boy, you have some catching up to do.. Start here http://forum.xda-developers.com/showthread.php?t=2010338
Roms aren't buggy nowadays, you'll be ok.
Click to expand...
Click to collapse
I've decided to root, but not use a custom rom. Is that okay? I just want to use it to calibrate my screen using the app I saw. And Maybe. Maybe use roms later.
Excited about this.
thenerdal said:
I've decided to root, but not use a custom rom. Is that okay? I just want to use it to calibrate my screen using the app I saw. And Maybe. Maybe use roms later.
Excited about this.
Click to expand...
Click to collapse
Ok, as in do you have our permission..?
He*l yeah mate, you decide what & how big steps forward you take!
Vangelis13 said:
Ok, as in do you have our permission..?
He*l yeah mate, you decide what & how big steps forward you take!
Click to expand...
Click to collapse
One more question. I have tmobile insurance, if I root it, will they replace it still if something happens?
thenerdal said:
One more question. I have tmobile insurance, if I root it, will they replace it still if something happens?
Click to expand...
Click to collapse
Can't answer that I'm not afraid.
You can always unroot though if phone works. Usually they care about the bootloader being unlocked..
Vangelis13 said:
Can't answer that I'm not afraid.
You can always unroot though if phone works. Usually they care about the bootloader being unlocked..
Click to expand...
Click to collapse
Damn, I know that. Just if the screen is unresponsive, is there a way they will be able to find out I rooted?
thenerdal said:
Damn, I know that. Just if the screen is unresponsive, is there a way they will be able to find out I rooted?
Click to expand...
Click to collapse
If the phone turns on they can see if it is bootloader unlocked or not. If it doesn't, they can't tell.
Sent from my Nexus 4 using Tapatalk 2
joshnichols189 said:
If the phone turns on they can see if it is bootloader unlocked or not. If it doesn't, they can't tell.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Recommend me a way to root please. I tried this: http://www.youtube.com/watch?feature=player_embedded&v=g88PPZyvfDI
But the when i plugged in my device in fastboot with usb debugging on, Windows 7 said it couldn't install the drivers correctly. So I didn't continue.
thenerdal said:
I noticed that looking at a blank white page on my Nexus 4 that it wasn't as white as I would love. So I searched and found out I could calibrate it.
I prefer not to use a different kernel, so I would like to use this app: https://play.google.com/store/apps/details?id=com.nexus4displaycontrol
Question #1: Is that app good? Like would it fix my problem?
Question #2: I would like to get updates from Google as well, how does that work with a rooted phone? Will I lose my calibration once I update?
That's all the questions I have.
Thanks!
Click to expand...
Click to collapse
you cant calibrate without a kernel. the google kernel does not expose the needed interfaces and rgb calibration will get you no where. so, no, it will most likely not fix your problem. if you install a custom kernel, then yes, it will solve your problems.
in case youre interested, i compiled a bunch of calibrated google stock kernels for 4.2.2:
http://forum.xda-developers.com/showthread.php?t=2136295
with these simple rgb calibration will be enough.
First of all if you are on the updated 4.2.2 stock kernel you wont be able to use display control apps to change your gamma settings. Google removed access to change the gamma settings on the stock kernel. So you will have to flash a custom kernel.
You can flash a custom kernel and remain on the stock rom. But will have to return back to the stock kernel in order to receive the OTA updates. There are many kernels so just look around in the development sections or even better search videos.
In terms of rooting many will advise you to manually do it yourself as this is the best way and it will increase your understanding of how everything is done. However, not everyone is confident even after learning how everything is donw and would rather use toolkits to prevent mishaps. I would recommend Wugfresh's toolkit.
So the app i used worked! WAY BETTER. What does gamma do?
Also, I rooted. Now what? How do I backup? I want CyanogenMod, but the monthly version, wondering how I can do that.
Thanks.
thenerdal said:
So the app i used worked! WAY BETTER. What does gamma do?
Also, I rooted. Now what? How do I backup? I want CyanogenMod, but the monthly version, wondering how I can do that.
Thanks.
Click to expand...
Click to collapse
I hate to have to say it like that, directly, but there's no other way around it; search & read up mate!
"Now what"..? :what:
No one is gonna hold your hand and walk you through it step by step, you have to do it yourself. There are guides everywhere, check the Stickies in General.
Vangelis13 said:
I hate to have to say it like that, directly, but there's no other way around it; search & read up mate!
"Now what"..? :what:
No one is gonna hold your hand and walk you through it step by step, you have to do it yourself. There are guides everywhere, check the Stickies in General.
Click to expand...
Click to collapse
True, but sometimes guides miss somethings.
thenerdal said:
True, but sometimes guides miss somethings.
Click to expand...
Click to collapse
No, they don't. The guides that you find in the Stickies are (for their purpose) complete.
It's a phone, won't bite you.. Play around a bit!

[Q] running oudhs auto Loki on Canadian variant

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

[Q] s4 camera

Is there any way to get the s4 camera app to work on a nexus 4? And how can I get it to work? I downloaded the stock s4 rom, found the camera app, tried to install it and it didn't work. I wasn't surprised though lol. So is there a way to get it to install?
The standalone apk won't work, since the app relies on the touch wiz framework. You would need a touch wiz rom for it to work properly.
chromium96 said:
The standalone apk won't work, since the app relies on the touch wiz framework. You would need a touch wiz rom for it to work properly.
Click to expand...
Click to collapse
Oh. It's there any way to get a touchwiz rom? I couldn't find any :/
NuckFuggets said:
Oh. It's there any way to get a touchwiz rom? I couldn't find any :/
Click to expand...
Click to collapse
It's possible but I don't think any developer would want to mess with it to port it onto the Nexus 4.
Sent from my Nexus 4 using Tapatalk 2
scream4cheese said:
It's possible but I don't think any developer would want to mess with it to port it onto the Nexus 4.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Oh ok. What would happen if I flash the s4 rom onto my phone, but then flash the n4 kernel? It would still brick, right?
I don't know about brick, but it would definitely not boot.
Sent from an N4 blessed with AOKP and sanctified by Faux123!
NuckFuggets said:
Oh ok. What would happen if I flash the s4 rom onto my phone, but then flash the n4 kernel? It would still brick, right?
Click to expand...
Click to collapse
Yes, most probably. The rom might try to repartition your device and that'll always lead to bricked devices. Don't even think about doing it.
exb0 said:
Yes, most probably. The rom might try to repartition your device and that'll always lead to bricked devices. Don't even think about doing it.
Click to expand...
Click to collapse
Oh I see. Well I wasn't planning on doing it anyway but why is it that you can't flash another phones rom onto your phone? Like they all run android, so why not?
NuckFuggets said:
Oh I see. Well I wasn't planning on doing it anyway but why is it that you can't flash another phones rom onto your phone? Like they all run android, so why not?
Click to expand...
Click to collapse
because every device has it's different components, and different component means different drivers. If you flash the wrong rom, it may brick your device, or it'll just not boot.
Different drivers (or libs) and different partitions and kernels are the main reason why you can't just flash another rom from another device.
exb0 said:
because every device has it's different components, and different component means different drivers. If you flash the wrong rom, it may brick your device, or it'll just not boot.
Different drivers (or libs) and different partitions and kernels are the main reason why you can't just flash another rom from another device.
Click to expand...
Click to collapse
Oh I see. What if the two phones have the same hardware? Then would you be able to?
NuckFuggets said:
Oh I see. What if the two phones have the same hardware? Then would you be able to?
Click to expand...
Click to collapse
Probably not. There would still likely be some differences. For example the htc desire and the nexus one, are extremely similar phones, however the roms are not interchangeable.
Also sorry to shift the direction of the thread, but does anyone know why some phones arent so easily bricked by software? The htc desire is a great example of this. I have flashed multiple roms and kernels not meant for the phone. Although it wont boot, the phone is not bricked. I can simply full wipe and restore a nandroid or flash a rom to fix it. With the nexus 4, this doesnt seem to be the case.
chromium96 said:
Probably not. There would still likely be some differences. For example the htc desire and the nexus one, are extremely similar phones, however the roms are not interchangeable.
Also sorry to shift the direction of the thread, but does anyone know why some phones arent so easily bricked by software? The htc desire is a great example of this. I have flashed multiple roms and kernels not meant for the phone. Although it wont boot, the phone is not bricked. I can simply full wipe and restore a nandroid or flash a rom to fix it. With the nexus 4, this doesnt seem to be the case.
Click to expand...
Click to collapse
Oh ok. That sucks :/
NuckFuggets said:
Oh ok. That sucks :/
Click to expand...
Click to collapse
That's why each device on XDA has their own little section call home.
Sent from my Nexus 4 using Tapatalk 2
chromium96 said:
Probably not. There would still likely be some differences. For example the htc desire and the nexus one, are extremely similar phones, however the roms are not interchangeable.
Also sorry to shift the direction of the thread, but does anyone know why some phones arent so easily bricked by software? The htc desire is a great example of this. I have flashed multiple roms and kernels not meant for the phone. Although it wont boot, the phone is not bricked. I can simply full wipe and restore a nandroid or flash a rom to fix it. With the nexus 4, this doesnt seem to be the case.
Click to expand...
Click to collapse
Probably the way they chose to assign the partitions on the device. It would be nice if there was a standard that everyone followed, but oh well.
NuckFuggets said:
Oh I see. What if the two phones have the same hardware? Then would you be able to?
Click to expand...
Click to collapse
Even if they have the exact same hardware components (SoC, camera...) but have a different bootloader partition layout you'll end up bricking your device. Imagine the bootloader as a group of containers, and each contains some type of data packages, on some phones the kernel is located (for example) in mmcblk0p5 , on other it can be in mmcblk0p8... And many of those containers contain data that is not to be touched, and overwriting it mostly leads to bricking, and the only solution is to restore the bootloader using a JTAG (if you're device is supported of course).
Sent from my Nexus 7 using xda premium
rayiskon said:
Even if they have the exact same hardware components (SoC, camera...) but have a different bootloader partition layout you'll end up bricking your device. Imagine the bootloader as a group of containers, and each contains some type of data packages, on some phones the kernel is located (for example) in mmcblk0p5 , on other it can be in mmcblk0p8... And many of those containers contain data that is not to be touched, and overwriting it mostly leads to bricking, and the only solution is to restore the bootloader using a JTAG (if you're device is supported of course).
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Hhm alright. Well it would be pretty cool if there was a standard that everyone followed, it would be awesome running s4 rom on the nexus 4 imo
NuckFuggets said:
Hhm alright. Well it would be pretty cool if there was a standard that everyone followed, it would be awesome running s4 rom on the nexus 4 imo
Click to expand...
Click to collapse
in that case it shouldn't be called a Nexus anymore

[Q] Couple noob questions about CyanogenMod

1) What are the benefits of CyanogenMod over stock?
2) Is CyanogenMod rooted or do you have to root it separately?
3) Does anyone know if they implemented TextSecure in their stock messaging yet?
4) Is switching back as simple as flashing the stock rom?
Cyanogenmod is better than stock for so many reasons that I'm not going to type them all out. Google that one.
It is a rooted rom.
I have no idea. Check the changelogs at www.get.cm
Yes.
Keep in mind that Cyanogenmod is only available on a very limited number of S4's running <MF3 firmware. For the majority of users who own thus device, it's not even an option.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
HORiZUN said:
Cyanogenmod is better than stock for so many reasons that I'm not going to type them all out. Google that one.
Keep in mind that Cyanogenmod is only available on a very limited number of S4's running <MF3 firmware. For the majority of users who own thus device, it's not even an option.
Click to expand...
Click to collapse
Googling it came up with conflicting info. My about device page says I337MVLUEMK6, so I should be fine, right?
No. That's a 4.3 OS if I'm correct.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
rbedell said:
No. That's a 4.3 OS if I'm correct.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Yup I misread the less than sign. What would happen if I flashed it? Would the device just be bricked?
Mekanikz said:
Yup I misread the less than sign. What would happen if I flashed it? Would the device just be bricked?
Click to expand...
Click to collapse
Just bricked sounds a little light hearted. Yes probably a paperweight. You aren't even going to get as far as putting the custom recovery on it. If you flashed in safestrap you would wind up with a black screen because no kernel support yet.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
rbedell said:
Just bricked sounds a little light hearted. Yes probably a paperweight. You aren't even going to get as far as putting the custom recovery on it. If you flashed in safestrap you would wind up with a black screen because no kernel support yet.
Sent from my SAMSUNG-SGH-I337 using Tapatalk
Click to expand...
Click to collapse
Having more experience with CM, do you think a version will come out anytime soon for I337MVLUEMK6 or not?
Mekanikz said:
Having more experience with CM, do you think a version will come out anytime soon for I337MVLUEMK6 or not?
Click to expand...
Click to collapse
Not until hashcode can get the custom kernel hand off to work with safestrap. Then they could do something. Until then no AOSP Roms will work.
Sent from my SAMSUNG-SGH-I337 using Tapatalk

Help a noob get PAC on his phone

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....

Categories

Resources