Develop Bugs

FreeGee

FreeGee updated recently and now gives me the option to install CWM-6.0.4.7 or TWRP-2.6.3.3. Has anyone tried this yet?

morganstein said:
FreeGee updated recently and now gives me the option to install CWM-6.0.4.7 or TWRP-2.6.3.3. Has anyone tried this yet?
Click to expand...
Click to collapse
I'll tell you right now, i'm not going to try. Without knowing for sure I can have download mode back. No way
Sent from my Nexus 7 using Tapatalk

secret.animal said:
I'll tell you right now, i'm not going to try. Without knowing for sure I can have download mode back. No way
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Ha. That's what I'm waiting for.

Why aren't you wanting to try auto-rec.
http://forum.xda-developers.com/showthread.php?t=2715496
One button operation
Sent from my Nexus 7 using Tapatalk

Already answered.
Deleted.
How rude stealing my post 3 minutes before me secret.animal. lol

I have used it quite a few times and it works fine. Only thing is for me it would hang on install. I would just close the app, clear all tasks by holding down home button, run it again and it would say completed. I know that sounds weird but that used to happen on my old optimus g.
Sent from my LG-LS980 using xda app-developers app

leroybrute said:
Already answered.
Deleted.
How rude stealing my post 3 minutes before me secret.animal. lol
Click to expand...
Click to collapse
Sorry cuz, I got lucky that time.
Sent from my LG-LS980 using Tapatalk

secret.animal said:
Why aren't you wanting to try auto-rec.
http://forum.xda-developers.com/showthread.php?t=2715496
One button operation
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
I've been following the AutoRec thread for a couple days and I'm a little concerned that there's no follow up yet on those white lines that some are getting. I did notice that FreeGee no longer gives me a warning about ZVC being incompatible. Any body know if this means FreeGee is now safe?

whouston.jr said:
I've been following the AutoRec thread for a couple days and I'm a little concerned that there's no follow up yet on those white lines that some are getting. I did notice that FreeGee no longer gives me a warning about ZVC being incompatible. Any body know if this means FreeGee is now safe?
Click to expand...
Click to collapse
I had no issues with autorec. But I tot, rooted then used autorec.
I'm only guessing but it could be because of that. Some that had the lines already had twrp but had broken download before they used autorec. Like I said though, it's a guess.

leroybrute said:
I had no issues with autorec. But I tot, rooted then used autorec.
I'm only guessing but it could be because of that. Some that had the lines already had twrp but had broken download before they used autorec. Like I said though, it's a guess.
Click to expand...
Click to collapse
i got white lines and I was stock rooted, ls980, 4.4.2. had to .tot back.

mtg981 said:
i got white lines and I was stock rooted, ls980, 4.4.2. had to .tot back.
Click to expand...
Click to collapse
Have you rooted again and tried autorec since?

leroybrute said:
Have you rooted again and tried autorec since?
Click to expand...
Click to collapse
I also was rooted on stock ZVC. I installed autorec and let it do its thing. First try, I could not do a backup in TWRP. It would fail everytime. Then I booted to system and thought everything was fine till the screen went off. White lines slowly appeared and stayed. Only fix was to reboot. That got boring so I tot back to ZVC and used ioroot25 to root and then installed autorec. White lines again when screen off then back on. I think waiting until the dev can figure out what is being altered on our ls980, we have to wait.

sclarktay4 said:
I also was rooted on stock ZVC. I installed autorec and let it do its thing. First try, I could not do a backup in TWRP. It would fail everytime. Then I booted to system and thought everything was fine till the screen went off. White lines slowly appeared and stayed. Only fix was to reboot. That got boring so I tot back to ZVC and used ioroot25 to root and then installed autorec. White lines again when screen off then back on. I think waiting until the dev can figure out what is being altered on our ls980, we have to wait.
Click to expand...
Click to collapse
Did you wipe cache and dalvik and try autorec again?
Seems strange that it's working fine for a lot of us and not for others.

leroybrute said:
Did you wipe cache and dalvik and try autorec again?
Seems strange that it's working fine for a lot of us and not for others.
Click to expand...
Click to collapse
I can only think there is some tweak in the modified kernel that breaks us. Ota, tot, no matter what. I can see no matter what in TWRP, but in system it fails. I gone every way.
Just have to wait a bit longer.
Sent from my Nexus 7 using Tapatalk

secret.animal said:
I can only think there is some tweak in the modified kernel that breaks us. Ota, tot, no matter what. I can see no matter what in TWRP, but in system it fails. I gone every way.
Just have to wait a bit longer.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Agreed on modified kernel.
I hope @Cloudyfa sticks around for us, to help the ones that need it. He has contributed so much to the G2 community.

My big concern is that freegee doesn't give any info as to what version of ZVC OTA it's compatible with, and neither does the autorec thread for that method. Like in the ZVA-> ZVC thread, there's a zip of the OTA... which is slightly different than getting the official OTA through system updates on the phone. So I'm afraid to try either method and end up with an unrecoverable brick because I'm on the official OTA.
Anyone on completely stock ZVC, rooted, that has successfully used either method?

agentfusion said:
My big concern is that freegee doesn't give any info as to what version of ZVC OTA it's compatible with, and neither does the autorec thread for that method. Like in the ZVA-> ZVC thread, there's a zip of the OTA... which is slightly different than getting the official OTA through system updates on the phone. So I'm afraid to try either method and end up with an unrecoverable brick because I'm on the official OTA.
Anyone on completely stock ZVC, rooted, that has successfully used either method?
Click to expand...
Click to collapse
Auto-rec works fine. The modified kernel that every app or by manual has used is the same at the time.
The worst it will do if it does not work is give you lines in your display after the screen shuts off. A reboot fixes that. But to fix completely, is to tot back to zvc and stay just rooted.
Sent from my Nexus 7 using Tapatalk

Stock rooted zvc. Auto-rec worked for me. No lines. Everything works.Just downloaded app. From download folder pressed on the app let the phone install it. Then ran it. I did not have download mode at first so reran the app and download mode worked.

secret.animal said:
Auto-rec works fine. The modified kernel that every app or by manual has used is the same at the time.
The worst it will do if it does not work is give you lines in your display after the screen shuts off. A reboot fixes that. But to fix completely, is to tot back to zvc and stay just rooted.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yep. Worked perfectly. No lines at all. Haven't tested download mode yet but system and recovery both work. Wooohoooo.

Glad to hear it worked!

Guide to Update to KitKat on a Rooted Phone

Hi All,
With all the threads about bricked phones, I wanted to take the safer route and outright ask for the best method to upgrade to KitKat on a rooted phone running 4.2.2 stock? I've already 'bricked" my phone once last year doing an OTA update, so I'm trying to avoid doing that again. I know this is a noob question, but I haven't been able to locate a sprint specific guide consolidating all of the information out there. Any help is appreciated.
Sprint LS980ZV7
4.2.2 stock on a rooted phone
twrp installed
IOroot25
Kernel: 3.4.0

thadeus_d3 said:
Hi All,
With all the threads about bricked phones, I wanted to take the safer route and outright ask for the best method to upgrade to KitKat on a rooted phone running 4.2.2 stock? I've already 'bricked" my phone once last year doing an OTA update, so I'm trying to avoid doing that again. I know this is a noob question, but I haven't been able to locate a sprint specific guide consolidating all of the information out there. Any help is appreciated.
Sprint LS980ZV7
4.2.2 stock on a rooted phone
twrp installed
IOroot25
Kernel: 3.4.0
Click to expand...
Click to collapse
Use this thread for the files
http://forum.xda-developers.com/showthread.php?p=51557219
Or you can use this one to flash zvc tot file straight to phone.
http://forum.xda-developers.com/showthread.php?p=45293512
The second post as you read will give information I thought a bit more clear on Sprint.
@#***This will wipe your phone as in complete. Nothing will be left of yours. So copy anything off internal [email protected]#***
Follow the directions, use ioroot25. Root.
If you want custom recovery.
http://forum.xda-developers.com/showthread.php?p=51857807
Use auto-rec from above thread. Thank cloudyfa for putting that together.
If you reboot after and screen shuts off and you get white lines.
You might a well tot back to zvc and just root. @Cloudyfa on that same thread is working out the details to fix.
Sent from my Nexus 7 using Tapatalk

secret.animal said:
Use this thread for the files
http://forum.xda-developers.com/showthread.php?p=51557219
Or you can use this one to flash zvc tot file straight to phone.
http://forum.xda-developers.com/showthread.php?p=45293512
The second post as you read will give information I thought a bit more clear on Sprint.
@#***This will wipe your phone as in complete. Nothing will be left of yours. So copy anything off internal [email protected]#***
Follow the directions, use ioroot25. Root.
If you want custom recovery.
http://forum.xda-developers.com/showthread.php?p=51857807
Use auto-rec from above thread. Thank cloudyfa for putting that together.
If you reboot after and screen shuts off and you get white lines.
You might a well tot back to zvc and just root. @Cloudyfa on that same thread is working out the details to fix.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thank you for the reply. I'll give this a shot tonight!

I have a question: I already screwed up and applied the KitKat update to my rooted G2 without thinking. It's now stuck booting to TWRP, where I was a moron and of course didn't create a backup at any point. Is there a way for me to sideload the ROM onto my phone at this point?
Any ideas?

Coop1979 said:
I have a question: I already screwed up and applied the KitKat update to my rooted G2 without thinking. It's now stuck booting to TWRP, where I was a moron and of course didn't create a backup at any point. Is there a way for me to sideload the ROM onto my phone at this point?
Any ideas?
Click to expand...
Click to collapse
Even sideload may not help you, if you can access down load mode. You might get to use tot, back to stock.
But there is no stock zvc yet for ls980.
Sent from my Nexus 7 using Tapatalk

secret.animal said:
Even sideload may not help you, if you can access down load mode. You might get to use tot, back to stock.
But there is no stock zvc yet for ls980.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Thank you for that suggestion. I was able to use Download Mode to fix my G2 and then OTA the KitKat update. Your post saved my phone.
Sent from my Nexus 7 using Tapatalk

I must have gotten lucky...wasn't thinking and took the OTA a while ago. Lost root but phone is fine.
Now...I'm off to find it again so I can get tether working

thadeus_d3 said:
Thank you for the reply. I'll give this a shot tonight!
Click to expand...
Click to collapse
To the OP, can I ask which method you chose and how it went? I need to do this as well and I'm in the same boat as you (rooted ZVA with custom recovery).
Thanks.
Ed

esoh said:
To the OP, can I ask which method you chose and how it went? I need to do this as well and I'm in the same boat as you (rooted ZVA with custom recovery).
Thanks.
Ed
Click to expand...
Click to collapse
I actually read a bit more and decided to hold off on the update. I'm happy with my phone's performance, so I really don't have the time to troubleshoot should the update go awry.

thadeus_d3 said:
I actually read a bit more and decided to hold off on the update. I'm happy with my phone's performance, so I really don't have the time to troubleshoot should the update go awry.
Click to expand...
Click to collapse
I'm the same way, but I figured that I should just go ahead.
So I'll throw that out, anyone pick one of these methods have a preference? I'm on TWRP, rooted, stock ZVA. Some mods including tether and camera. Thanks.

Help with flashing ZVD Affliction rom

I'm kind of new to the rom stuff. I am using the Lego Rom right now. I downloaded the ZVD Affliction Rom and followed the instructions to flash. It loads the LG screen and then the Android swirly thing but then it just sits at a blank screen.

Blainodraino said:
I'm kind of new to the rom stuff. I am using the Lego Rom right now. I downloaded the ZVD Affliction Rom and followed the instructions to flash. It loads the LG screen and then the Android swirly thing but then it just sits at a blank screen.
Click to expand...
Click to collapse
Lego looks to have been radio zva or zv8. You need to be on zvc, or zvd before flashing this ROM.
Most likely your firmware and radio aren't up to date.
If you can restore your backup. Do so and then best option is to backup anything off phone to computer. Then tot to zvc, root, install auto-rec to get recovery and then flash affliction zvd ROM.
Sent from my Nexus 7 using Tapatalk

I'm not really familiar with the tot thing. Could u point me to a tutorial or something?

secret.animal said:
Lego looks to have been radio zva or zv8. You need to be on zvc, or zvd before flashing this ROM.
Most likely your firmware and radio aren't up to date.
If you can restore your backup. Do so and then best option is to backup anything off phone to computer. Then tot to zvc, root, install auto-rec to get recovery and then flash affliction zvd ROM.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2432476
Go to the first post and scroll past the kdz method. You will see a att, sprint method.
Follow directions.
Sent from my Nexus 7 using Tapatalk

[Q] Lost & Confused...HELP!

H i all Let me start by apologizing as I'm sure I'm doing something here that I'm not supposed too. Although I am new to XDA, until recently I didn't know I was such a tech virgin.. I have spent off and on months trying to figure out why my LG G2 has prematurely entered mechanical menopause. I have read scores of articles, tried numerous "fixes", various roots etc, but I can't get it right because I can't make out what's wrong. About the phone: Sprint Lg G2 LS980 ZVE running Android 4.4.2. I rooted my phone not long after I got it, which was back before the latest updates. Unfortunately I lost my phone for several months and when I got it back it had of course been updated. When installing a root checker the phone says Not Rooted, when it's in download mode or when I tried to use Stumproot it says I'm already Rooted. Upon opening SuperSU I get this warning, "There is no SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 4.3 you need to manually re-root - consult the relevant forums for your device." Upon opening BusyBox I get this message, "There was a problem opening a shell with root access. This is either being caused by Superuser/SuperSU or by a device that is improperly rooted. Try removing permissions, uninstalling and then reinstalling this application, blah blah blah, but of course SuperSU acts as previously mentioned when opened. I don't know what to do besides potentially flash stock but I really don't want to do that. I am a stubborn, learn by doing kind of techie but after months of learning everything but the answer, I raise the white flag. Please someone tell me there is an easy/obvious answer that I missed as I'd rather be a moron with an ignorant miss, than a stubborn ass with time consuming fixes in my immediate future.
Thank you so much, Jo

You will have to use the zve tot that's the only way to fix it, then stump will work perfectly.
Sent from my LG-LS980 using XDA Free mobile app

Thank you
I have gone through the process of flashing back to stock twice now and both times it ends in an error that says there is no kdz file. Any advice please?

Kdz is for Verizon or other carriers. Sprint is strictly tot. Make sure you are following the right directions.
Sent from my LG-LS980 using Tapatalk

i would suggest zv8 and root and custom recovery , after the zvc onto zve,zvd root with stumproot, also do not upgrade(OTA) on a custom recovery, i would hightly consider, downgrade to zv8 updgrade all the way to zvd stumproot and then install custom recovery

Even better, downgrade zv8, root via ioroot25, install auto-rec.
Flash upgraded TWRP, flash resurrection remix, gapps. And be done with it.
Sent from my LG-LS980 using Tapatalk

secret.animal said:
Even better, downgrade zv8, root via ioroot25, install auto-rec.
Flash upgraded TWRP, flash resurrection remix, gapps. And be done with it.
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
yup that is the right way^ thats what i have done i always downgrade because most people who try to get there MSL dont realize you can get it be downgrading to zv8 root and install the recovery, all on that version.

Do you lose band 26/41 LTE by running zv8? I agree with above, must use a tot file to return to stock, then root will work.

secret.animal said:
Even better, downgrade zv8, root via ioroot25, install auto-rec.
Flash upgraded TWRP, flash resurrection remix, gapps. And be done with it.
Sent from my LG-LS980 using Tapatalk
Click to expand...
Click to collapse
How stable is this ROM? Does GPS and everything work on it? Only thing stopping me from doing this is losing stability of stock.

KelevrA_8 said:
How stable is this ROM? Does GPS and everything work on it? Only thing stopping me from doing this is losing stability of stock.
Click to expand...
Click to collapse
I've had no issues and funny thing you ask about GPS. I have never had an issue with any rom with GPS. Though many others do.

secret.animal said:
I've had no issues and funny thing you ask about GPS. I have never had an issue with any rom with GPS. Though many others do.
Click to expand...
Click to collapse
Good deal

How to root i747 on nj1?

Please help, what is the process of rooting a stock 4.4.2 NJ1 i747 on at&t?

Araltd said:
Please help, what is the process of rooting a stock 4.4.2 NJ1 i747 on at&t?
Click to expand...
Click to collapse
I tried some programs, including towelroot, but they are not updated tu support NJ1, I really need to root it too, so we are in the same boat.
Good luck

MarceloUruguay said:
I tried some programs, including towelroot, but they are not updated tu support NJ1, I really need to root it too, so we are in the same boat.
Good luck
Click to expand...
Click to collapse
Look through this thread. I'll bet something in it will work. Enewman17 is a whiz at this.

OKAstro said:
Look through this thread. I'll bet something in it will work. Enewman17 is a whiz at this.
Click to expand...
Click to collapse
Here's the issue I'm having, that thread linked says it will flash a pre-rooted NJ1 rom - ok fine... But as far as I can tell, no one has specifically said they have flashed his pre-rooted rom on top of a stock NJ1 rom. They've all upgraded to NJ1 from NE# using his method.
Obviously the NJ1 'upgrade' was at least in part an attempt to prevent rooting, and I'm not experienced enough to unbrick (or effectively undo) whatever may happen in a botched attempt.
I'm assuming once you're on NJ1 stock rom, rooting is not possible?

Araltd said:
Here's the issue I'm having, that thread linked says it will flash a pre-rooted NJ1 rom - ok fine... But as far as I can tell, no one has specifically said they have flashed his pre-rooted rom on top of a stock NJ1 rom. They've all upgraded to NJ1 from NE# using his method.
Obviously the NJ1 'upgrade' was at least in part an attempt to prevent rooting, and I'm not experienced enough to unbrick (or effectively undo) whatever may happen in a botched attempt.
I'm assuming once you're on NJ1 stock rom, rooting is not possible?
Click to expand...
Click to collapse
Read midway down in the 1st post of the OP I linked...talks about rooting NJ1

I was able to root my ATT S3 that is on NJ1 using this method
http://forum.xda-developers.com/show....php?t=1963790

Dbeayon said:
I was able to root my ATT S3 that is on NJ1 using this method
http://forum.xda-developers.com/show....php?t=1963790
Click to expand...
Click to collapse
The link is incomplete, can you post it again, or better yet, explain how did you do it ?
Thanks!

MarceloUruguay said:
The link is incomplete, can you post it again, or better yet, explain how did you do it ?
Thanks!
Click to expand...
Click to collapse
The correct url is http://forum.xda-developers.com/showthread.php?t=1963790

Root works
wayneneely said:
The correct url is http://forum.xda-developers.com/showthread.php?t=1963790
Click to expand...
Click to collapse
hi, jut to let you know that i tried rooting my s3 on latest 4.4.2 using the link and it works perfectly.

johnye17 said:
hi, jut to let you know that i tried rooting my s3 on latest 4.4.2 using the link and it works perfectly.
Click to expand...
Click to collapse
Which message from that thread did you follow in order to root the phone ?
Thanks!

MarceloUruguay said:
Which message from that thread did you follow in order to root the phone ?
Thanks!
Click to expand...
Click to collapse
I used Odin to flash the latest CF Auto Root for the phone, even without rooting a phone for at least a year (out of practice) I did it in less than 40 secs.

johnye17 said:
I used Odin to flash the latest CF Auto Root for the phone, even without rooting a phone for at least a year (out of practice) I did it in less than 40 secs.
Click to expand...
Click to collapse
Were you using baseband I747UCUFNJ1 ?
I don't want to brick my phone
Thanks!

MarceloUruguay said:
Were you using baseband I747UCUFNJ1 ?
I don't want to brick my phone
Thanks!
Click to expand...
Click to collapse
yes, i was running NJ1, and just so you know, right now im running a Stock Mod Custom ROM

johnye17 said:
yes, i was running NJ1, and just so you know, right now im running a Stock Mod Custom ROM
Click to expand...
Click to collapse
Finally I rooted it without too many problems, I had to re-install super su, but after all, it wasn't too complicated.
The difficult part was to enable tethering, because most fixes still need an AT&T chip.
The solution was this: http://forum.xda-developers.com/moto-x/themes-apps/xposed-moto-x-4-4-native-tether-apk-t2601859
Thnak you very much for everything,
Marcelo

Help
MarceloUruguay said:
Finally I rooted it without too many problems, I had to re-install super su, but after all, it wasn't too complicated.
The difficult part was to enable tethering, because most fixes still need an AT&T chip.
The solution was this: http://forum.xda-developers.com/moto-x/themes-apps/xposed-moto-x-4-4-native-tether-apk-t2601859
Thnak you very much for everything,
Marcelo
Click to expand...
Click to collapse
I am complete noob at this. I am running Nj1 and I have never rooted anything before. I am having battery issues and everything points to deleting the battery bin file. I could really use a little help on how to do this. When I go to the cf auto root page I can't find the file needed for I747UCUFNJ1

BakaRed77 said:
I am complete noob at this. I am running Nj1 and I have never rooted anything before. I am having battery issues and everything points to deleting the battery bin file. I could really use a little help on how to do this. When I go to the cf auto root page I can't find the file needed for I747UCUFNJ1
Click to expand...
Click to collapse
The file for NJ1 is the file listed for SAMSUNG-SGH-I747, which is http://download.chainfire.eu/235/CF-Root/CF-Auto-Root/CF-Auto-Root-d2att-d2uc-samsungsghi747.zip
You will see that the files inside the zip are updated after NJ1 was released.
Best regards from Uruguay,
Marcelo

?
MarceloUruguay said:
The file for NJ1 is the file listed for SAMSUNG-SGH-I747, which is
You will see that the files inside the zip are updated after NJ1 was released.
Best regards from Uruguay,
Marcelo
Click to expand...
Click to collapse
You're awesome. But I have a question. Will this work for 4.4.2? Idk is that is a stupid question or not....

BakaRed77 said:
You're awesome. But I have a question. Will this work for 4.4.2? Idk is that is a stupid question or not....
Click to expand...
Click to collapse
Sure, I have 4.4.2!
It's not an stupid question because probably you saw 4.0.4 at the CF Auto Root page, that's just the first Android version that the s3 i747 used, now the latest official android version is 4.4.2

MarceloUruguay said:
Sure, I have 4.4.2!
It's not an stupid question because probably you saw 4.0.4 at the CF Auto Root page, that's just the first Android version that the s3 i747 used, now the latest official android version is 4.4.2
Click to expand...
Click to collapse
Ok so I went through and got it to say pass on Odin, but it's still not rooted. It said superSU has stopped. Tried a reboot and it keeps saying it. Root checker basic says its def not rooted. Idk where I went wrong.

BakaRed77 said:
Ok so I went through and got it to say pass on Odin, but it's still not rooted. It said superSU has stopped. Tried a reboot and it keeps saying it. Root checker basic says its def not rooted. Idk where I went wrong.
Click to expand...
Click to collapse
Just update superSU using Google Play, and you should be rooted.