Related
Can anyone help? I started experiencing the problem with xtr rom and decided to flash a different rom to try and fix. Problem still persists. Tried a nand restore to a previous rom, no luck there either. Right now I'm on FROYO and I love it but it did it again a while after i flashed the rom. Speakerphone works but ear speaker doesn't. Wiped data and dalvik both times. Anyone have any suggestions, I'm desperate! Donation comes to the dev who can figure this out!
If its been happening repeatedly with several roms, i may suggest you roll back your device to stock ROLLBACK FOR ROOT and try rooting and flashing roms again. however it could be a hardware issue with the phone as well but i would give the rollback a shot before returning the phone beings as its practice for what youll have to do before you return it anyway. =)
Willing to give it a try but the link you provided only tells me how to get from stock to rooted. I'm already rooted
Sent from my FroyoEris using XDA App
Hello folks I just bought the 32gb TF300T at Best Buy tonight. Got the price match via the "Office Max" ad for $349.99 plus tax...
Anyhow some questions.
I have rooted, rom'd, themed, ect... the heck out of my DroidX and am generally very comfortable mucking around in that territory but I'm reading various threads here and about concerning the permanent bricking of the TF300 if a person does something wrong. I'm used to being able to SBF & restore the DroidX if something goes amiss and bring the 'brick' alive again. That being said, I'm a bit squeemish at the moment to do any modifications with the TF300 but of course will be itching to nontheless... Mainly would like to definitely Root-Unlock(?)-Flash Roms. Any suggestions or particular threads to point me to concerning this? I've done a little looking around but there seems to be multiple methods discussed for even rooting and I'm a little uncertain on where to begin realizing this is likely a bit different than the DroidX.
Any recommendations as to "Must Have" apps and/or do most apps that work on the DroidX for example, still work on this tablet?
My uses will be for both work and play. A lot of web surfing, email, and media.
Any and all tips are appreciated! Thanks
Once you unlock the bootloader you should be good to go. Just make sure you follow directions and read up before you do anything new. Also just so you know once you unlock you cannot go back to locked and you will not get updates from asus. Currently I'm just going with it locked and rooted and I'm happy. Ics is so good already plus there aren't too many rooms out yet. Give it time though and once they start to roll out and I get sick of stock ill start flashing. I'm also holding out so that if anything goes wrong my warranty is still valid and I can get it replaced.
Sent from my ASUS Transformer Pad TF300T using xda premium
Howdy!
First off, nice buy, I do so enjoy my TF300T, and I'm sure you will as well.
As you prolly know from the cheaper price, Asus also used cheaper parts to build their tablets. Make sure the screen is free of defects, so you can return it for a new one if something goes wrong. It's a beautiful tablet as long as your luck is up and you don't brick it by mistake. My advice: wait a week or two. If you're happy, go ahead and visit this thread ( http://forum.xda-developers.com/showthread.php?t=1669827) for a cyanogenmod 9 port. The Nightlies are stable, I'm using it right now, but there are still issues with GPS and Sound, which will be fixed with time and patience.
You can root (if you haven't updated past .17 and don't want to install CM9 yet) easy by using sparkyroot at: http://forum.xda-developers.com/showthread.php?t=1526487 ))) But if you have, do some research, and you'll find what you"re looking for.
If you do, here's something to help you along: http://www.android.gs/update-asus-t...anogenmod-9-android-4-0-4-ice-cream-sandwich/
There's more, but you have to search for it! Google is your friend.
------------------------------------
If I've helped you, please don't forget to thank me!
TDinsmoor said:
As you prolly know from the cheaper price, Asus also used cheaper parts to build their tablets. Make sure the screen is free of defects, so you can return it for a new one if something goes wrong.
Click to expand...
Click to collapse
I second this completely. I'm on my third tablet. The first one had a dead pixel, and the second had a hardware defect where the touchscreen went crazy if I applied any amount of pressure to the left edge of the tablet. The second one took me a few days to figure out what exactly was happening.
Thanks for the replies! I did actually take that update from Asus last night after powering it up.
My Kernel version is 2.6.39.4
Wonder if I can even root now at this moment?
Thinking of holding out for now regarding unlocking as I would sooner keep it within warranty at this time plus it doesn't seem like there are any real perks in unlocking currently if the Roms & Kernels out now are still young in development.
I would like to root though if I haven't screwed up by already taking the update so I can run TB, ect...
Thanks again guys. I'm sure there will be many questions to come!
Yer very welcome.
I do recommend the updated build.prop, it's low-profile, but helps with things such as battery life and other optimization. You need root, however.
TDinsmoor said:
Yer very welcome.
I do recommend the updated build.prop, it's low-profile, but helps with things such as battery life and other optimization. You need root, however.
Click to expand...
Click to collapse
Thanks! I did get my root very easily per this thread: http://forum.xda-developers.com/showthread.php?t=1689193
The thing is I tried to get the CWR via:
3. If you have root and need CWM recovery.
Why? Nandroid backups and restores. Debrick. Flexibility. Numerous other reasons. ( but no OTA)
- Step 1. Run the tool "1-Click Transformer Root.bat"
- Step 2. You'll be presented with a menu. Choose option (3)
- You'll have CWM Recovery
Click to expand...
Click to collapse
And was unable to as option #3 is simply "Quit" :silly:
I'm wondering if one needs to be "Unlocked" to obtain CWM recovery?
Anyhoo, yea, could you point me to this updated "build.prop" discussion and method for obtaining? Anything in particular to be cautious of when doing it?
Thanks!
lazer9 said:
Thanks! I did get my root very easily per this thread: http://forum.xda-developers.com/showthread.php?t=1689193
The thing is I tried to get the CWR via:
And was unable to as option #3 is simply "Quit" :silly:
I'm wondering if one needs to be "Unlocked" to obtain CWM recovery?
Anyhoo, yea, could you point me to this updated "build.prop" discussion and method for obtaining? Anything in particular to be cautious of when doing it?
Thanks!
Click to expand...
Click to collapse
You need to be unlocked for CWM. In relation to the modified build.prop AFAIK there isn't one made for the lastest firmware (.30), but here's the main thread for it: http://forum.xda-developers.com/showthread.php?t=1641219
jgaf said:
You need to be unlocked for CWM. In relation to the modified build.prop AFAIK there isn't one made for the lastest firmware (.30), but here's the main thread for it: http://forum.xda-developers.com/showthread.php?t=1641219
Click to expand...
Click to collapse
Thanks for that info. I'll read up on the process now so I will have a good grip on it if/when one becomes available for the current firmware.
jgaf said:
....In relation to the modified build.prop AFAIK there isn't one made for the lastest firmware (.30), but here's the main thread for it: http://forum.xda-developers.com/showthread.php?t=1641219
Click to expand...
Click to collapse
Wait... From that thread: Post #261 http://forum.xda-developers.com/showpost.php?p=27666040&postcount=261
It seems there are actually two for the latest firmware or am I reading something wrong?
Edit: Disregard the above. I just realized those are for the WW version and not US. If I'm understanding correctly... Whew, so much to be careful about.
I'll start off by giving some background information. I ordered my Nexus 4 back in March and ran stock up until about July/June. Prior to the Nexus I had the HTC G2. I don't know how to root and and use custom ROMs and I have looked at the root guide for the Nexus but it's a huge barrage of information and some terms that I don't know what they are. However, this question doesn't involve rooting. I gave my Nexus 4 to a friend, who also has the Nexus, to root for me and use a custom ROM. In this process however, he did something that he told me to never do (I really don't know why..) and he ended up soft bricking my phone. He did that because my phone was stuck on the "Google" start up screen for over 40 minutes. Basically, he wiped the entire phone, I think. Due to some issues, we are no longer on speaking terms and he was the only person I knew who knows how to deal with rooting and custom ROMs.
Now I don't have the original back up of the stock. My question is, if I ever needed to send my phone back to Google for repairs or anything else, would I be able to somehow get the phone back to it's stock state?
Also, where could I find some resources that aren't a barrage of information? When I go to those threads like the Nexus rooting guide, it's just so much information and I get lost (I don't even quite know what a ROM is, my current interpretation is an operating system). Currently, I think I know how to update the ROM, I'm currently using Paranoid Android.
I apologize if this issue of mine can easily be solved with a search. I have googled this issue numerous times and I could not really find a solid answer.
Fubs261 said:
I'll start off by giving some background information. I ordered my Nexus 4 back in March and ran stock up until about July/June. Prior to the Nexus I had the HTC G2. I don't know how to root and and use custom ROMs and I have looked at the root guide for the Nexus but it's a huge barrage of information and some terms that I don't know what they are. However, this question doesn't involve rooting. I gave my Nexus 4 to a friend, who also has the Nexus, to root for me and use a custom ROM. In this process however, he did something that he told me to never do (I really don't know why..) and he ended up soft bricking my phone. He did that because my phone was stuck on the "Google" start up screen for over 40 minutes. Basically, he wiped the entire phone, I think. Due to some issues, we are no longer on speaking terms and he was the only person I knew who knows how to deal with rooting and custom ROMs.
Now I don't have the original back up of the stock. My question is, if I ever needed to send my phone back to Google for repairs or anything else, would I be able to somehow get the phone back to it's stock state?
Also, where could I find some resources that aren't a barrage of information? When I go to those threads like the Nexus rooting guide, it's just so much information and I get lost (I don't even quite know what a ROM is, my current interpretation is an operating system). Currently, I think I know how to update the ROM, I'm currently using Paranoid Android.
I apologize if this issue of mine can easily be solved with a search. I have googled this issue numerous times and I could not really find a solid answer.
Click to expand...
Click to collapse
Is the phone booting into PA? If not try holding the power button and the volume down at the same time. It should boot into recovery. If it does all you need to do is flash a rom "install a os".
Sent from my Nexus 4 using xda app-developers app
Tunderpimp said:
Is the phone booting into PA? If not try holding the power button and the volume down at the same time. It should boot into recovery. If it does all you need to do is flash a rom "install a os".
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Ohh yes, I should clarify. Currently the phone is working and I have it up to date on Paranoid Android. The only issue I had when updating Paranoid Android was that I could not use the kernel my friend had supplied me with (I think it was the Franco kernel). When I would flash the kernel, it would get stuck on the Google logo screen. I would have to get out of that by re-flashing Paranoid Android again and I've been unsuccessful in flashing any kernels. The main reason I wanted to root my phone was a custom kernel, to help with battery life.
My main question is that I wanted to know if I could ever get it back to stock (as to not void a warranty) if I were to ever need to for any reason.
Fubs261 said:
Ohh yes, I should clarify. Currently the phone is working and I have it up to date on Paranoid Android. The only issue I had when updating Paranoid Android was that I could not use the kernel my friend had supplied me with (I think it was the Franco kernel). When I would flash the kernel, it would get stuck on the Google logo screen. I would have to get out of that by re-flashing Paranoid Android again and I've been unsuccessful in flashing any kernels. The main reason I wanted to root my phone was a custom kernel, to help with battery life.
My main question is that I wanted to know if I could ever get it back to stock (as to not void a warranty) if I were to ever need to for any reason.
Click to expand...
Click to collapse
which franco kernel, was it compatibke with your rom? i mean are you on android 4.3 and the kernel 4.2.2(or vice versa)? when you flashed the kernel, did you flash with the rom then boot up, or did you just flash the kernel alone? did you try redownloading the kernel, maybe a bad download? was it a jss kernel or a jwr kernel?
Fubs261 said:
My main question is that I wanted to know if I could ever get it back to stock (as to not void a warranty) if I were to ever need to for any reason.
Click to expand...
Click to collapse
Yes you can.
Read the guides as slowly as you need to...stopping to research anything you don't understand...
Or just use those no brainer toolkits that teach you nothing.
And stick to stock until you know what's going on within your device when you do these things.
simms22 said:
which franco kernel, was it compatibke with your rom? i mean are you on android 4.3 and the kernel 4.2.2(or vice versa)? when you flashed the kernel, did you flash with the rom then boot up, or did you just flash the kernel alone? did you try redownloading the kernel, maybe a bad download? was it a jss kernel or a jwr kernel?
Click to expand...
Click to collapse
I'm not sure what version it was, I guess that might have been the issue. Would that have caused it to stay on the Google logo screen? I'll make sure to double check for that next time I try to do something.
studacris said:
Yes you can.
Read the guides as slowly as you need to...stopping to research anything you don't understand...
Or just use those no brainer toolkits that teach you nothing.
And stick to stock until you know what's going on within your device when you do these things.
Click to expand...
Click to collapse
Thank you for answering. Could you link a good starter thread for me? I was hesitant to use a custom ROM or even to root my phone. What compelled me to do it was the kernels extending battery life. Because I was so lost and felt overwhelmed, I had my friend help me but now we are no longer on talking terms so I'm lost.
Again, I wish to apologize, I know I should just look this up myself, but with the possibility of bricking/soft-bricking my phone, I want to get as much help as possible. Whatever small nudge, I will take.
Your questions can be answered by reading the stickies thread in the general section. Just follow the instructions to flash back to factory stock:
http://forum.xda-developers.com/showthread.php?t=2010312
If you flash a kernel and the phone won't boot, that kernel or version of the kernel isn't compatible with that rom or particular version of Android.
sent from xda premium app
---------- Post added at 06:09 AM ---------- Previous post was at 06:06 AM ----------
Fubs261 said:
Because I was so lost and felt overwhelmed, I had my friend help me but now we are no longer on talking terms so I'm lost.
Click to expand...
Click to collapse
I hope it's not because he messed up your phone, it's not his fault that you trusted him to do it in the first place. If not, well nevermind.
sent from xda premium app
It's very simple to get it back to stock. You'd just need to find a copy of the stock Rom (which I can assure you is probably on this very website floating around somewhere) and flash it in recovery like you would any other Rom.
Sent from my 16GB Blue Verizon Galaxy S3 running MIUI v5 with KT kernel
---------- Post added at 03:14 AM ---------- Previous post was at 03:12 AM ----------
Also keep in mind, custom roms usually come with custom kernels. So you shouldn't even have to worry about kernel flashing. If you want to preserve battery you should focus more on under clocking and thermal throttling...
You can find guides on here somewhere for that too...
Sent from my 16GB Blue Verizon Galaxy S3 running MIUI v5 with KT kernel
So... I did the stupid thing. I attempted to go back to my old MF9 backup through TWRP after upgrading to MJA, and now my wifi won't even turn on. I've been trying to figure this out for a few hours now, trying various fixes. I've tried to use ODIN to flash back to complete stock, but that just destroys my phone until I flash a recovery through ODIN. Everything I've seen on the forums so far has made it seem as though there is no hope since Samsung added in Knox.
I'm sorry if this has been resolved elsewhere, but I've literally been searching the General. Q&A, Android Development, Original Android Development, and Developer forums for several hours today with no luck. Can someone please help me with this? I just want my phone to be fully functional again...
EDIT:
Here's the deal; my main problem was with Wifi not working. The Stock MF9 Kernel was not working, but the 4.2.2 TW Kernel found here finally did.
did you try this?
leaderbuilder said:
did you try this?
Click to expand...
Click to collapse
Yes. Nothing changed when I did that. I suppose that I should call out that I am currently on MF9.
dante042 said:
So... I did the stupid thing. I attempted to go back to my old MF9 backup through TWRP after upgrading to MJA, and now my wifi won't even turn on. I've been trying to figure this out for a few hours now, trying various fixes. I've tried to use ODIN to flash back to complete stock, but that just destroys my phone until I flash a recovery through ODIN. Everything I've seen on the forums so far has made it seem as though there is no hope since Samsung added in Knox.
I'm sorry if this has been resolved elsewhere, but I've literally been searching the General. Q&A, Android Development, Original Android Development, and Developer forums for several hours today with no luck. Can someone please help me with this? I just want my phone to be fully functional again...
Click to expand...
Click to collapse
i just gave up on trying to do a restore. I actually used Titanium to get as much information from my old backup as possible then just rolled with it. I know that probably isn't what you wanted to hear but that what worked for me.. hope that helps
I have read that the WiFi issue may be a Kernel issue.. Did you try a different TouchWiz kernel and see if it worked out?
Sent from my SPH-L720 using XDA Premium 4 mobile app
lmayes69 said:
i just gave up on trying to do a restore. I actually used Titanium to get as much information from my old backup as possible then just rolled with it. I know that probably isn't what you wanted to hear but that what worked for me.. hope that helps
Click to expand...
Click to collapse
This is actually what I was trying to do, sadly. Titanium was backing up my info to the phone storage rather than the SD card, and I had to do a data wipe to get to MJA, so I lost them. I figured I could restore to my MF9 backup to redo them, and that's when the trouble started.
I finally got it working. I had to try several different kernels until one finally worked. Now about flashing a new ROM...
rosa styhome
dante042 said:
I finally got it working. I had to try several different kernels until one finally worked. Now about flashing a new ROM...
Click to expand...
Click to collapse
What kernel did you use and how did you install it? I'm having a similar issue and can't find a fix.
Scott02 said:
What kernel did you use and how did you install it? I'm having a similar issue and can't find a fix.
Click to expand...
Click to collapse
Scott, check my first post. I edited it with a link to the page with the kernel I used. Make sure that you choose the correct kernel for your Android version. The MF9 and MJA designators have nothing to do with which kernel you need, so make sure to check in your "aboout phone" section to find out what android version you're running. Using the 4.3 kernel on 4.2.2 will cause a bootloop, which is easily fixed by flashing the correct kernel.
I've tried this two times and both I had the same result. I downgraded back to 4.2.2 with the D80110g_00.kdz for the tmobile g2. Then I rerooted it and added philz touch recovery. I flashed with the kitkat baseband in the cloudystock 1.1 fourm, then the rom with the patched 801 kernel after. Everything boot's up ok, and the phone works. But when I turn off the screen and back on its all grayed out with yellow lines. I have the reboot the phone for the screen to show up again. Can someone tell me what I am doing wrong?
Do the same process except do not use 80110g. Find the 80110c kdz.
Sent from my LG-D801 using xda app-developers app
Thank you, that fixed the problem. Another question I have is that when I flash the baseband, do I have to keep reflashing it when I move to another kitkat rom?
JPrinceStar said:
Thank you, that fixed the problem. Another question I have is that when I flash the baseband, do I have to keep reflashing it when I move to another kitkat rom?
Click to expand...
Click to collapse
baseband stays the same when flashing other roms. Pretty sure the rom zips don't touch baseband unless specified otherwise. Glad it worked for ya btw
Sent from my LG-D801 using xda app-developers app
Problem came back, turn off screen and its grayed out when back on unless reboot. I dont have this problem when I root 4.2.2. Am I flashing the files in the wrong order, or am I missing something.
JPrinceStar said:
Problem came back, turn off screen and its grayed out when back on unless reboot. I dont have this problem when I root 4.2.2. Am I flashing the files in the wrong order, or am I missing something.
Click to expand...
Click to collapse
Doesn't seem like you are flashing in wrong order. If you boot up and everything runs...it's probably just due to the fact this isn't an official release and there may be bugs
Sent from my LG-D801 using xda app-developers app
v2.2v said:
Doesn't seem like you are flashing in wrong order. If you boot up and everything runs...it's probably just due to the fact this isn't an official release and there may be bugs
Sent from my LG-D801 using xda app-developers app
Click to expand...
Click to collapse
I have the exact issue...here is a picture of what it looks like, maybe this will help so that people can see what we talking about
batmanonastick said:
I have the exact issue...here is a picture of what it looks like, maybe this will help so that people can see what we talking about
Click to expand...
Click to collapse
same issue here. Cannot run any stock KK roms at all. I've flashed so many times and have had to return to stock. I wish this problem could be identified.
Did anyone out there figure this out?
I'm having the same problem on my device, tried several stock ROMs but nothing works even when using different basebands.
I have this problem as well and no, you're not doing anything wrong. Devs have absolutely no idea why this is happening. It seems that this is only happening with users that bought the phone and have the G build pre-installed. People that bought the phone earlier with the C build don't have this problem.
I gave up and just flashed the official KK TMO ROM with root installed. I lost my recovery but hopefully devs can get recovery on stock KK. If anything, I can always KDZ back to 4.2.2 and re-install the recovery if I want to go back to AOSP ROM's.
FWIW, I bought the G2 a week ago. When did you get yours?
I think you hit the nail on the head with G build comment. I got my phone about a month ago from TMO and it came pre-installed. I wonder if something in the actual hardware is ever so slightly different with the latest G2s...
I flashed with the C build and it didn't fix it also, guess I'll stay on 4.2.2 till there is a official kitkat root.
Anyone around in this thread with the line problem willing to test a kernel?
mackster248 said:
I have this problem as well and no, you're not doing anything wrong. Devs have absolutely no idea why this is happening. It seems that this is only happening with users that bought the phone and have the G build pre-installed. People that bought the phone earlier with the C build don't have this problem.
I gave up and just flashed the official KK TMO ROM with root installed. I lost my recovery but hopefully devs can get recovery on stock KK. If anything, I can always KDZ back to 4.2.2 and re-install the recovery if I want to go back to AOSP ROM's.
FWIW, I bought the G2 a week ago. When did you get yours?
Click to expand...
Click to collapse
How do you find if you have G or C build? I thought all tmobile g2's are c build. I am getting mine tomorrow, hope it is shipped with JB rom - if so, i think it will be better to stay. After reading a bit, i heard many say tot method is working fine as explained here.
Which rom (xd thread?) are you using? Does wifi calling work?
sam298 said:
How do you find if you have G or C build? I thought all tmobile g2's are c build. I am getting mine tomorrow, hope it is shipped with JB rom - if so, i think it will be better to stay. After reading a bit, i heard many say tot method is working fine as explained here.
Which rom (xd thread?) are you using? Does wifi calling work?
Click to expand...
Click to collapse
If you go to software you can see the build, it either ends with C or D. Most likely D since you'll just be getting it. And it will be JB not KK. There's a new AutoRec file that gives KK users recovery, but since you'll be getting the D version, you'll most likely have the white line glitch issue. There's a way around it, just PM me for further questions and I'll help ya out.
v2.2v said:
Do the same process except do not use 80110g. Find the 80110c kdz.
Sent from my LG-D801 using xda app-developers app
Click to expand...
Click to collapse
KennyJive said:
same issue here. Cannot run any stock KK roms at all. I've flashed so many times and have had to return to stock. I wish this problem could be identified.
Click to expand...
Click to collapse
JPrinceStar said:
Did anyone out there figure this out?
Click to expand...
Click to collapse
SeVIIn said:
I'm having the same problem on my device, tried several stock ROMs but nothing works even when using different basebands.
Click to expand...
Click to collapse
i really want to root but this is making me nervous. Only things i want to change is the camera mod and sound mod really.
dr87 said:
Anyone around in this thread with the line problem willing to test a kernel?
Click to expand...
Click to collapse
I am in the same boat as most these people.. bought my phone a week ago, i am rooting as i type. Will probably have the issue and completely willing to test a kernel. Should i flash your rom as well first?
---------- Post added at 11:59 AM ---------- Previous post was at 11:56 AM ----------
mackster248 said:
If you go to software you can see the build, it either ends with C or D. Most likely D since you'll just be getting it. And it will be JB not KK. There's a new AutoRec file that gives KK users recovery, but since you'll be getting the D version, you'll most likely have the white line glitch issue. There's a way around it, just PM me for further questions and I'll help ya out.
Click to expand...
Click to collapse
Hmmm.. so i have a completely stock g2 non rooted (working on rooting right now actually) but when i go into settings, my build number ends with an 'A' ?? not c, d or g.... what does this mean? Man, rooting seemed so much easier on my HTC or samsung phones! No complaints though, i love this phone
frettfreak said:
i really want to root but this is making me nervous. Only things i want to change is the camera mod and sound mod really.
I am in the same boat as most these people.. bought my phone a week ago, i am rooting as i type. Will probably have the issue and completely willing to test a kernel. Should i flash your rom as well first?
---------- Post added at 11:59 AM ---------- Previous post was at 11:56 AM ----------
Hmmm.. so i have a completely stock g2 non rooted (working on rooting right now actually) but when i go into settings, my build number ends with an 'A' ?? not c, d or g.... what does this mean? Man, rooting seemed so much easier on my HTC or samsung phones! No complaints though, i love this phone
Click to expand...
Click to collapse
It does seem confusing, but I promise you that it's a bit more painless than you think. I'm assuming your phone did indeed ship with TMO KitKat? Then in that case, once you're done rooting, all you have to do is install the AutoRec apk and that's it! Let me know if you need a link for AutoRec.
mackster248 said:
It does seem confusing, but I promise you that it's a bit more painless than you think. I'm assuming your phone did indeed ship with TMO KitKat? Then in that case, once you're done rooting, all you have to do is install the AutoRec apk and that's it! Let me know if you need a link for AutoRec.
Click to expand...
Click to collapse
yeah it did ship with KK. pretty sure i have seen the thread regarding the autorec app. But will let you know! Thanks!
mackster248 said:
It does seem confusing, but I promise you that it's a bit more painless than you think. I'm assuming your phone did indeed ship with TMO KitKat? Then in that case, once you're done rooting, all you have to do is install the AutoRec apk and that's it! Let me know if you need a link for AutoRec.
Click to expand...
Click to collapse
Mackster I'm on 4.2.2 which is rooted, is there anyway I could use a custom kitkat rom without getting the white lines? I dont want to keep downgrading everytime it happens.