[Q] Flashing AOKP roms - Sprint Samsung Galaxy S 4 Q&A, Help & Troubleshoot

I'm rooted running a good TW rom at the moment but I have always preferred and ran AOSP roms. So I want to flash Liquid's rom but keep getting error getprop"ro.bootloader". OP said to look for updated bootloader firmware, I have looked for two days and can't seem to find that file or the solution. I am on OUDHS recovery and have tried TWR also but both give me the same error. I have successfully flashed CM10 but I can't flash most of the other AOKPs, I've seen a few others post similar results but no one has stated a sure fix. It seems hit or miss some can flash some can't. What am I missing?? If there is a updated bootloader where would I look to find it? Thanks

furry said:
I'm rooted running a good TW rom at the moment but I have always preferred and ran AOSP roms. So I want to flash Liquid's rom but keep getting error getprop"ro.bootloader". OP said to look for updated bootloader firmware, I have looked for two days and can't seem to find that file or the solution. I am on OUDHS recovery and have tried TWR also but both give me the same error. I have successfully flashed CM10 but I can't flash most of the other AOKPs, I've seen a few others post similar results but no one has stated a sure fix. It seems hit or miss some can flash some can't. What am I missing?? If there is a updated bootloader where would I look to find it? Thanks
Click to expand...
Click to collapse
I believe the latest OTA has an updated bootloader, but I wouldnt take it at this time as the devs are still sorting through it. Take a look at some of the MF9 (I think) threads. Not sure it would solve your aokp issues
Sent from my SPH-L720 using xda app-developers app

I have already run the MF9 update with updated bootloader, it flashed fine but when I tried to flash the ROM again it still gave me the same ro.bootloader error. I'm just going to hang loose and let the developement catch up and then give it another shot later. There are still OTAs hitting with tweaks so no boubt those will end up in rom updates anyway. I don't want to bother the great developers this early in the stages, its all to new yet.

Related

[Q] TWRP = only flash roms that are based on the Asus OTA?

I've had my TF300 for a few weeks now and am disappointed with the sluggishness of the offical JB ROM when compared to my GS2 on AOKP or even my wife's Tablet S with stock ICS. I'd like to try some of the modified official ROMs or CM10.
After searching these forums for a while and reading the various guides, it seems like the easiest way to unlock and root the tablet is to use the Asus unlocker apk then use fastboot to install TWRP. When I downloaded TWRP I noticed it said:
"If you have taken the official Asus Jellybean OTA then be sure to install the '-JB' version of the recovery for your device - and only flash roms that are based on the Asus OTA."
Does this really mean I'm restricted to ROMs based on the official JB? If I go with CWM will I be able to install any ROM? Am I stuck no matter what because I already have the OTA JB? Thanks for the help if anyone can answer, I just couldn't cobble together a clear answer from the threads I read.
You can flash any Rom you like with Twrp. You just have to dl the right version for the bootloader.
I am using Twrp from the beginning and never had any problems with it.
mikaole said:
You can flash any Rom you like with Twrp. You just have to dl the right version for the bootloader.
I am using Twrp from the beginning and never had any problems with it.
Click to expand...
Click to collapse
Thanks for the reply. So is the caution on the TWRP site just superfluous? I have to admit that it makes me nervous going forward.
It means you need to flash roms that support the JB bootloader. So no ICS roms.
there are a few CM roms that are based on JB that will flash fine. Just today I tried 2 CM roms and one hybrid CM+AOKP port on my TF300t that was running the OTA JB update (unlocked and TWRP'd).
Just be for sure anything you flash says for JB bootloader. There are a few 4.1 cm based roms for the old ics bootloader. The warning you saw on the website is just trying to warn because so many people just flash **** without reading.
Sent from my ASUS Transformer Pad TF300T using xda app-developers app
Got it. Thanks guys.
I'll be unlocking and putting TWRP on tonight to see what kind of ROM I like. Appreciate the clarification.
hfeigel said:
Got it. Thanks guys.
I'll be unlocking and putting TWRP on tonight to see what kind of ROM I like. Appreciate the clarification.
Click to expand...
Click to collapse
Care to make a how-to video? Joking of course... Just bemoaning my incompetence... I get the Asus bootloader apk, and I know how to flash roms using twrp (I have used it for about a year on my S2 and S3) but from what I read, installing twrp on the tf300 looks more challenging than on my phone. I will keep searching, but I may be forced to throw on my flame suit and start a thread if I cant get this resolved soon! :laugh:
go the the video thread and look for the video titled
"How to Flash ClockWorksMod Recovery + ROOT ( Works on ALL Fimrware )"
just use the twrp.blob instead of the CM one and you're good to go.

[Q] Help With JB Energy™ Rom

Just recently flashed a friend's phone with Energy Rom. The rom looks amazing and is very well designed. There are just a few issues that he is having and I have not seen anyone else experience these problems in the tread. (Too few posts to post there)
Her camera is not working and I guess her Hotspot gave her a "timed out" message. . . . If anyone else has experienced this, please let me know if you were able to resolve this and how.
Thanks!
marcusw3 said:
Just recently flashed a friend's phone with Energy Rom. The rom looks amazing and is very well designed. There are just a few issues that he is having and I have not seen anyone else experience these problems in the tread. (Too few posts to post there)
Her camera is not working and I guess her Hotspot gave her a "timed out" message. . . . If anyone else has experienced this, please let me know if you were able to resolve this and how.
Thanks!
Click to expand...
Click to collapse
Are you on the 4.1.2 update? If so you will need to flash back down to 4.1.1 kernel because the new kernel is not compatible with the 4.1.1 camera
Sent from my XT907 using Tapatalk 2
marcusw3 said:
Just recently flashed a friend's phone with Energy Rom. The rom looks amazing and is very well designed. There are just a few issues that he is having and I have not seen anyone else experience these problems in the tread. (Too few posts to post there)
Her camera is not working and I guess her Hotspot gave her a "timed out" message. . . . If anyone else has experienced this, please let me know if you were able to resolve this and how.
Thanks!
Click to expand...
Click to collapse
Energy ROM is based off of the the 4.1.1 build, the latest update has the XT907 at 4.1.2. So if her phone was previously on 4.1.2, then flashing this ROM could cause problems as the previous poster mentioned due to the new kernel. Not sure if the developer will update his ROM any time soon (which I loved by the way, and keep checking his thread for any updates),
also, Energy ROM can only be installed via SS right now, and given that the bootloader has been unlocked, I believe that all ROMs will be flashable via TWRP/CWM going forward - thus making SS obsolete for the XT907.
Here's what I suggest though:
unlock bootloader
install TWRP recovery
try out the DeadRage ROM, which is based on the 4.1.2 build: http://www.droidrzr.com/index.php/topic/17778-romretail-deadrage-v12a-05092013-412-base/
if you really want to stick with Energy ROM with working camera, then you still can:
flash back to stock (4.1.1)
root
install SS
unlock bootloader
install TWRP
install Energy ROM on Slot 1
backup Energy ROM via SS
move Energy ROM to stock slot via SS
backup Energy ROM via TWRP (basically making a nandroid, and this can be installed going forward as a backup)
uninstall SS
Thanks!
jco23 said:
Energy ROM is based off of the the 4.1.1 build, the latest update has the XT907 at 4.1.2. So if her phone was previously on 4.1.2, then flashing this ROM could cause problems as the previous poster mentioned due to the new kernel. Not sure if the developer will update his ROM any time soon (which I loved by the way, and keep checking his thread for any updates),
also, Energy ROM can only be installed via SS right now, and given that the bootloader has been unlocked, I believe that all ROMs will be flashable via TWRP/CWM going forward - thus making SS obsolete for the XT907.
Here's what I suggest though:
unlock bootloader
install TWRP recovery
try out the DeadRage ROM, which is based on the 4.1.2 build:
if you really want to stick with Energy ROM with working camera, then you still can:
flash back to stock (4.1.1)
root
install SS
unlock bootloader
install TWRP
install Energy ROM on Slot 1
backup Energy ROM via SS
move Energy ROM to stock slot via SS
backup Energy ROM via TWRP (basically making a nandroid, and this can be installed going forward as a backup)
uninstall SS
Click to expand...
Click to collapse
I will give the first suggestion a reply, if that does not work, the second. I will keep you all posted on results. Thank you!
Kernel?
Any clue of where I can find just the kernel I need to download and flash?
Sorry for coming across as a newbie, but I am used to other phones that have a bit larger of a community. Thanks again.
marcusw3 said:
Any clue of where I can find just the kernel I need to download and flash?
Sorry for coming across as a newbie, but I am used to other phones that have a bit larger of a community. Thanks again.
Click to expand...
Click to collapse
no worries - we all were newbies at some point in time.
I have not seen a thread dedicated to the stock 4.1.1 kernel, but I did find this:
http://forum.xda-developers.com/showthread.php?t=2017200
my advice at this point is to backup your apps/data via TiBu (and then copy that backup folder to your mnt/external1 directory).
so that way, after you pick your ROM, you can re-download your apps from the market (I always recommend doing this as opposed to letting TiBu restore them), then you can use TiBu to restore data ONLY from your apps. I do NOT recommend restore system data though when switching ROMs (however, I do restore WiFi settings and bluetooth pairings).
hope this helps.
All worked out great! I appreciate the help. I ended going with Energy 4.1.1 I have that stupid grateful dead image stuck on first power up due to rage. -Annoying!!
marcusw3 said:
All worked out great! I appreciate the help. I ended going with Energy 4.1.1 I have that stupid grateful dead image stuck on first power up due to rage. -Annoying!!
Click to expand...
Click to collapse
anytime - see this thread regarding the boot logo:
http://www.droidrzr.com/index.php/topic/17708-boot-logos-request-for-custom-one-here/

[Q] Verizon galaxy note 3 om Toubles!

Hi guys, I have a question regarding some roming stuff with the verizon version of the galaxy note 3. I am not new to roms by any means and I have been searching frantically to find one place with the complete answer im looking for. I made the early mistake of taking the OTA upgrade for KK, therefore I am currently running 4.4.2 with the NC4 build and NC4 baseband. Now while i have easily rooted my phone at this point with the towelroot. I also have had no problem getting the new 3.72 safestrap installed and running on my phone. My question now at this point is trying to figure out my next step with a new ROM I am trying install....I have been looking at all of my info to get the Hyperdrive ROM installed and I cant seem to find all the info I need in one location. Can I or can I not flash a new ROM to the NC4 baseband? I have seen some information where some people say I might be able to flash the NC2 kernal using ODIN and others say just trying to flash any ROM in general creates a black screen in which a battery pull needs to be done...yada yada.....? So in short, am I able to flash a ROM to the note 3 at this point or am I S.O.L?
sickorsane1 said:
Hi guys, I have a question regarding some roming stuff with the verizon version of the galaxy note 3. I am not new to roms by any means and I have been searching frantically to find one place with the complete answer im looking for. I made the early mistake of taking the OTA upgrade for KK, therefore I am currently running 4.4.2 with the NC4 build and NC4 baseband. Now while i have easily rooted my phone at this point with the towelroot. I also have had no problem getting the new 3.72 safestrap installed and running on my phone. My question now at this point is trying to figure out my next step with a new ROM I am trying install....I have been looking at all of my info to get the Hyperdrive ROM installed and I cant seem to find all the info I need in one location. Can I or can I not flash a new ROM to the NC4 baseband? I have seen some information where some people say I might be able to flash the NC2 kernal using ODIN and others say just trying to flash any ROM in general creates a black screen in which a battery pull needs to be done...yada yada.....? So in short, am I able to flash a ROM to the note 3 at this point or am I S.O.L?
Click to expand...
Click to collapse
Yes you can!! As long as the rom says that they support it you can. It says right here in red on the hyperdrive op-" This Rom is able to be installed on the Verizon Galaxy Note 3 On KitKat Bootloader with KK Safestrap" so make a backup with safestrap and try it out! And since it doesn't say anything about what specific one to use (I see what you are talking about) you won't have any harm with a backup. By the way the reason why a lot of roms were/are based on NC2 was because it was way more leniant than NC4 but now most if not all roms will support it. Just read the op.
Sent from my GalaxyAwesome
K03WL3R said:
Yes you can!! As long as the rom says that they support it you can. It says right here in red on the hyperdrive op-" This Rom is able to be installed on the Verizon Galaxy Note 3 On KitKat Bootloader with KK Safestrap" so make a backup with safestrap and try it out! And since it doesn't say anything about what specific one to use (I see what you are talking about) you won't have any harm with a backup. By the way the reason why a lot of roms were/are based on NC2 was because it was way more leniant than NC4 but now most if not all roms will support it. Just read the op.
Sent from my GalaxyAwesome
Click to expand...
Click to collapse
Hmmm....well I tried to do the jasmine rom and I seem to have had the same problem that quite a few people are having. I put it in slot 1, created the rom slot and such, reboots into the recovery mode on ss just fine but then it goes to a black screen as if it's off. Have to battery pull. Maybe gonna try a different rom and see where I end up.
I'm running JasmineRom on the stock slot, but I also have the NC2 kernel..
Sent from my GalaxyAwesome
K03WL3R said:
I'm running JasmineRom on the stock slot, but I also have the NC2 kernel..
Sent from my GalaxyAwesome
Click to expand...
Click to collapse
Should I try stock slot then? I used slot 1 with 3.75
You could try that (I would), or just flash the Nc2 stuff, then boot up (on stock), boot back to recovery and flash JasmineRom on stock. Those steps are just what I did and it worked for me. I'm really sorry but for the life of me that's the best I can remember about what I did. If none of that works, I'll try to install Jasmine onto a rom slot when I can.
Sent from my GalaxyAwesome
K03WL3R said:
You could try that (I would), or just flash the Nc2 stuff, then boot up (on stock), boot back to recovery and flash JasmineRom on stock. Those steps are just what I did and it worked for me. I'm really sorry but for the life of me that's the best I can remember about what I did. If none of that works, I'll try to install Jasmine onto a rom slot when I can.
Sent from my GalaxyAwesome
Click to expand...
Click to collapse
I flashed Nc2 from a post on here and still didn't work....I'm about to give up
Have you tried just making a backup and starting over from fresh stock?
Sent from my GalaxyAwesome
---------- Post added at 11:35 PM ---------- Previous post was at 11:27 PM ----------
Also ask here- http://forum.xda-developers.com/showthread.php?t=2780031
Sent from my GalaxyAwesome
You need to flash the rom after you've wiped everything, then reboot to download mode and install the unified firmware via odin. That should work.
Sent from my GalaxyAwesome
K03WL3R said:
You need to flash the rom after you've wiped everything, then reboot to download mode and install the unified firmware via odin. That should work.
Sent from my GalaxyAwesome
Click to expand...
Click to collapse
That did not work as that was the original plan of action. Only to come to a nice black screen
Okay, the dev just posted instructions in his last post on the JasmineRom thread. Check it out, it took me a while for it to work on my phone, it seems like a couple people are like us too.. Just a mix of trial and error
Sent from my GalaxyAwesome
Edit: and sorry I couldn't help so far, I don't really want to go back to stock considering this is my daily and I need a bigger sd card to make a full backup. [emoji53]
K03WL3R said:
Okay, the dev just posted instructions in his last post on the JasmineRom thread. Check it out, it took me a while for it to work on my phone, it seems like a couple people are like us too.. Just a mix of trial and error
Sent from my GalaxyAwesome
Edit: and sorry I couldn't help so far, I don't really want to go back to stock considering this is my daily and I need a bigger sd card to make a full backup. [emoji53]
Click to expand...
Click to collapse
All good! I finally got it working thanks to you saying the dev mentioned something! Jasmine up and running with no issues!
Jasmine V2
I never sign up for web sites but the Jasmine Rom is just so good I had to say thanks. Also concerning the excess power usage, I noticed that when plugged into AC charger the Android OS goes from 40% down to the 20's. Hope it helps. Again thanks to hsbadr for being a great DEV.
PS: K03WL3R I see you helping on hsbadr's forum, please convey my thanks and suggestion to him, for as I am a new member I can not post on his forum.
Thanks
Sorry it took me so long, there's an open discussion in the general/help section for jasminerom! I'm pretty sure new users can post there?

[Q] Phone refuses to boot with a rom

Hi, I've been trying to install a custom rom (at this point ANY custom rom) on my friend's phone. I have worked on several phones before, including my own sprint GS3, but this is my first time trying to work around a locked bootloader, and BOY is it a pain, haha. I'm no dev, but I would like to think that I'm pretty competent.
First a few things to note, are that the phone is currently on NI1 (Been too much of a sissy to go to NJ4 in case it screws something up, I don't even know why), it is the 16Gb version, I am using an external sd card to flash everything, and yes I am flashing loki-doki after everything.
So what I've done so far is:
- Try to install TWRP
- Find out that won't work and finally figure out I need safestrap
- Successfully install safestrap after using towelroot by ODIN-ing the NC1 kernel then going back to the NI1 kernel
- Try to flash Resurrection Remix and KToonsez kernel using a new rom-slot, and wind up soft-bricking (stuck on bootloader screen, can get to download mode)
- ODIN NB1 tar then ODIN NI1 update
- Repeat the last few steps several times because I'm too idiotic to realize that it JUST ISN'T GOING TO WORK!
- Finally find a reference to flashing the ATT kernel modules after the rom. That got me past the soft brick and safestrap screen, but I don't even see a boot animation
As of right now my sequence to successfully not soft-bricking (what an accomplishment) is to flash the rom>gapps>ATT kernel module>supersu>loki-doki>wipe dalvik/cache
Now, is it worth it having already spend a good 7 hours, just to get a custom rom? Of course not, it's not my phone and my friend isn't picky. He'd be just fine with rooted TW. However, It kills me that I don't know what's going on, so here I am lol.
TL;DR: Phone has safestrap, is rooted, but any time I flash a rom it gets past the boot loader/safestrap screen and never shows a boot animation, or anything past that. Can anyone help figure out what's going on please?
Thanks in advance.
You can only flash touch wiz based roms with safestrap and you can't flash kernels with safestrap. That's been your problem with soft bricking.
Edit, see this for roms you can flash http://forum.xda-developers.com/showthread.php?p=53758227
Sent from my Nexus 9 using XDA Free mobile app
http://forum.xda-developers.com/showthread.php?t=2616221
Thanks guys. I thought I read through the whole thread, but there is so much information, it's pretty scattered, I must have missed the thing about only TW roms working.
Now a few more questions:
1) Is it worth updating to NJ4? The phone is new and doesn't have any app data or anything that would be missed by updating. I see quite a few roms in 4.4.4, but it looks like most of them are AOSP based, which leads me to my next question...
2) Is there a way to get AOSP roms to work? I see all of these AOSP based roms, obviously for this phone, but it would be pointless to make them if they don't work.
Masterjuggler said:
Thanks guys. I thought I read through the whole thread, but there is so much information, it's pretty scattered, I must have missed the thing about only TW roms working.
Now a few more questions:
1) Is it worth updating to NJ4? The phone is new and doesn't have any app data or anything that would be missed by updating. I see quite a few roms in 4.4.4, but it looks like most of them are AOSP based, which leads me to my next question...
2) Is there a way to get AOSP roms to work? I see all of these AOSP based roms, obviously for this phone, but it would be pointless to make them if they don't work.
Click to expand...
Click to collapse
It wouldn't hurt to update to nj4. But it's not going to help you either. Only phones on mdb or mdl bootloader can flash non touch wiz based roms using loki. And you can't go back to those bootloaders
Sent from my Nexus 9 using XDA Free mobile app
Alright then. Hyperdrive looks pretty good, I'll try that along with Ktoonsez kernel. I'll report back later to let you know how it goes. Thanks again!
Masterjuggler said:
Alright then. Hyperdrive looks pretty good, I'll try that along with Ktoonsez kernel. I'll report back later to let you know how it goes. Thanks again!
Click to expand...
Click to collapse
Again, you can't flash a kernel in safestrap
Sent from my Nexus 9 using XDA Free mobile app
Oh, I get it now. That didn't quite register before. So just to confirm, after I flash the rom (which already has its own custom kernel included), I still need to flash the stock ATT kernel, correct?
Flash the rom, super su, and the att module for your base. Hyperdrive is a very good rom, good luck. Also the rom doesn't include a kernel, your original kernel stays put. That's why only tw roms work, because your new rom has to be compatible with the kernel already on your phone.
Just reporting in, I now have the phone up and running using Hyperdrive Rom. Thanks for the help!
I actually had a problem where it would not shut down correctly, but found out it was because I was installing the rom in a rom-slot in safestrap. As soon as I tried the stock rom slot, it worked flawlessly.

Tried two roms, getting the 'com.android.phone' has stopped responding (immediately)

I've tried Paranoid Android 4.6 and CM 11, both with the same result.
I could not get any custom bootloader to install, aside from safestrap. This seems to be on there ok now, and I can install PA or CM roms from my sd card.
When they are finished installing though (along with Gapps), when it boots into the OS I instantly get the popup telling me the process com.android.phone has stopped. I hit ok and it comes back immediately, no matter how many times I hit it. I can't get into the menus or setup screens, the popup comes back instantly.
Since PA and CM both did this same thing, I am guessing my problem is perhaps not the rom. Any ideas please on what I might try next? The phone is basically bricked at this point.
Taymar said:
I've tried Paranoid Android 4.6 and CM 11, both with the same result.
I could not get any custom bootloader to install, aside from safestrap. This seems to be on there ok now, and I can install PA or CM roms from my sd card.
When they are finished installing though (along with Gapps), when it boots into the OS I instantly get the popup telling me the process com.android.phone has stopped. I hit ok and it comes back immediately, no matter how many times I hit it. I can't get into the menus or setup screens, the popup comes back instantly.
Since PA and CM both did this same thing, I am guessing my problem is perhaps not the rom. Any ideas please on what I might try next? The phone is basically bricked at this point.
Click to expand...
Click to collapse
Yea, you can't flash cm or pa on your device. They can only be flashed on devices with the mdb or mdl bootloader. If you're using safestrap, and it's the only recovery you can use, you're probably on 4.4.4, nb1 or nc1 or nj4, bootloader. You'll need tw based roms. See the ones that work with safestrap.
Sent from my Nexus 9 using XDA Free mobile app
Thank you,
I flashed to NJ4 after rooting. Could you recommend any custom rom that is tw based please, or am I basically limited to stock?
I tried flashing a new TW rom but now I'm stuck in a recovery mode bootloop (safestrap seems to be gone).
edit: tw = touchwiz? (Sorry, I'm new at this).
Really appreciate the explanation, thanks again.
Taymar said:
Thank you,
I flashed to NJ4 after rooting. Could you recommend any custom rom that is tw based please, or am I basically limited to stock?
I tried flashing a new TW rom but now I'm stuck in a recovery mode bootloop (safestrap seems to be gone).
edit: tw = touchwiz? (Sorry, I'm new at this).
Really appreciate the explanation, thanks again.
Click to expand...
Click to collapse
Your stuck to 4.4.4 unless you do the method mentioned on the forums and GoldenEye comments.
But a caution its not for the new, is risky and you lose the safestrap recovery boot because safestrap is not lollipop compatible right now.
Got it. Thank you.
I finally found a 'stock' firmware that I managed to load via Odin. Looks like AT&T just pushed the lollopop update to my phone as well so I guess stock lollipop will work for me until I upgrade my phone.
Out of interest, I'm looking at the oneplus one phone. Am I correct in thinking I should have way less problems trying to root & install custom roms on that, since it comes loaded with CM and the carrier isn't going to be constantly fixing exploits that allow root?
Really appreciate the help guys, thanks again.
Taymar said:
Got it. Thank you.
I finally found a 'stock' firmware that I managed to load via Odin. Looks like AT&T just pushed the lollopop update to my phone as well so I guess stock lollipop will work for me until I upgrade my phone.
Out of interest, I'm looking at the oneplus one phone. Am I correct in thinking I should have way less problems trying to root & install custom roms on that, since it comes loaded with CM and the carrier isn't going to be constantly fixing exploits that allow root?
Really appreciate the help guys, thanks again.
Click to expand...
Click to collapse
I don't own it so I couldn't tell you but I would look up the forum for it before hand and see what they say about it.
If it's not an ATT and Verizon phone most likely it's not boot loader locked.
Taymar said:
Got it. Thank you.
I finally found a 'stock' firmware that I managed to load via Odin. Looks like AT&T just pushed the lollopop update to my phone as well so I guess stock lollipop will work for me until I upgrade my phone.
Out of interest, I'm looking at the oneplus one phone. Am I correct in thinking I should have way less problems trying to root & install custom roms on that, since it comes loaded with CM and the carrier isn't going to be constantly fixing exploits that allow root?
Really appreciate the help guys, thanks again.
Click to expand...
Click to collapse
Oneplus you will be able to root and recovery, I believe even unlock the bootloader. You just have to pay full price of the phone of course, but it's separate from carrier so no root patching OTAs.
Awesome. Thank you so much guys. I think I'm going to try out the oneplus one. Sounds like it'll be a lot more straightforward than with AT&T's devices.

Categories

Resources