[Completed] [Q] Problems with SuperSU SU Binaries on LG G2 - XDA Assist

Hello there.
I have been trying to learn and use custom ROMs on my LG G2 for a couple of weeks now, so far I haven't been doing too well. Luckily, smarter people than I on this forum have always brought me back from the brink of me causing a nuclear meltdown on my phone! Especially:
http://forum.xda-developers.com/showthread.php?t=2451696
Today, when I received an automatic update to SuperSU, a notification appeared in my notification shade informing me that my "SU Binaries Needed to be Updated!". I tapped on it, wanting to know more about these binaries that apparently required an update. This opened up the SuperSU app on my phone with a pop-up that also said the the SU binaries needed to be updated; I tapped continue. Another pop-up appeared telling me that if I had TWRP the binaries could possibly be updated through it (A "normal" option was also shown). My eager and naive mind chose to update via TWRP. My eagerness grew as my LG G2 booted into TWRP and seemed to install something. During this process, the phone rebooted again and my phone seemed to be just fine for ~1 minute.
Mission Accomplished!
Nope. To my utter horror (Though it was kind of expected) the phone force rebooted into TWRP again and attempts at rebooting to system have been met with being booted right back into TWRP. A factory reset had no effect as well. Following pattern, I made my way back to XDA and sniffed around for a while trying to find a thread where people had experienced something similar to myself. Unfortunately (or rather fortunately ), no one had. Then, I thought back to the post I posted above. FOTA is "firmware over the air" doesn't it? Could the command listed in the above post get me back to stock? Like I said before I'm a huge noob with a final goal of actually being able to contribute to XDA and others in the future. The key phrase being "I am a huge noob".
Minimal Information About The Phone (I am so sorry)
Android 4.4.2 Stock (Rooted)
Rooted With TowelRoot as I wanted to see if it actually worked
Installed TWRP with AutoRec (I'll link it below)
SuperSU as Root Manager (Installed from Play Store)
Verizon Model (VS980)
My Internal Storage was deleted about a week ago and I unfortunately did not make an NAndroid backup before I made this foray into unknown territory, I am terrible.
Link to AutoRec
http://forum.xda-developers.com/showthread.php?t=2715496
Thank you so much for reading all of that, if you did! If you have any suggestions/links to any good tutorials for LG G2 ROMs they would be greatly appreciated! I have had some trouble with CM 11 in the past, but I think that was due to my own personal failings.

Hi,
It's great that you are trying to learn and doing your homework! That's what XDA is all about. ?
For many questions, try this thread...
http://forum.xda-developers.com/showthread.php?t=2692223
And here is a thread for getting back to stock, which you can also ask for help in,
http://forum.xda-developers.com/showthread.php?t=2705259
Good luck!

KJ said:
Hi,
It's great that you are trying to learn and doing your homework! That's what XDA is all about. ?
For many questions, try this thread...
http://forum.xda-developers.com/showthread.php?t=2692223
And here is a thread for getting back to stock, which you can also ask for help in,
http://forum.xda-developers.com/showthread.php?t=2705259
Good luck!
Click to expand...
Click to collapse
Hey there!
Sorry for not responding to you for so long! I ended up using the FOTA command from the link I posted above and it worked like a charm! (Though it did once again delete my data ) Currently reinstalling everything and making an nandroid backup. Thank you for providing me with the help forums as well, they are quite good at what they do! Happy Sunday! Cheers!

Thank you. Thread closed.

Related

Lenovo IdeaTab A2107A-F

I am starting this thread to hopefully encourage discussion on the Lenovo A2107A-F tablet variant.
I am aware there is an existing thread on the A2107 here:
http://forum.xda-developers.com/showthread.php?t=1982334
but that thread is concentrating on the A-H (dual sim + wifi) variant which is somewhat different from the A-F (wifi only).
So far I have not found any custom rom development, which is disappointing as the stock rom leaves a lot to be desired IMHO. While the current OTA update is fine for web surfing, reading emails etc, HD video playback (particularly YouTube HD) is very poor. Also the recent OTA update forces an optimization of apps on bootup which leads to long boot times
You can root and install CWM by following steps 1-5 from the 1st post here:
http://forum.xda-developers.com/showthread.php?t=2044496
Note that "-Update 3-" mentioned in the post does not appear to work for the A-F model!
So, has anybody any leads on possible development on this tab?
Any tips on improving performance?
My first tip:
If after installing CWM you cannot get to the CWM recovery screen after powering down the device, look for for the file "/system/reboot-from-recovery.p". If it's there, either delete it or move it to some other place. This file restores the default recovery on a system reboot.
I got bitten by this a couple of times
Thanks for starting a separate thread for the A2107A-F. I'm new to Android devices and just got this one two weeks ago. I'd like to get rid of several of the apps that I have no use for and from what I understand that means I have to root it. I got lost in the details of the other thread, but I tried reading all of it. I'm on Vista and somewhere along the line I installed one of the suggested ADB drivers via PDAnet. Device Manager is showing Android Phone and under that Android ADB Interface. I wasn't sure if that matched closely enough with the step-by-step threads since I don't really think of the device as a phone, so I've been holding off on going further. I've tried using a few other drivers that were suggested in the large thread and some other threads, but Vista always tells me the current driver is the most up-to-date one.
Do you know if it's okay for it to say Android Phone rather than something else?
Thanks. I've got some other questions about the specifics of some of the other steps, but this is probably enough to get started.
My apologies in advance if my posts are too long and my questions are too basic for these forums. Feel free to point me somewhere else based on what I'm asking for. I'd honestly appreciate any leads towards my goal of getting rid of the bloat on this device and making it more responsive. (Wow! The portrait to landscape lag is really bugging me now after reading around here).
Anyway, my primary purpose is to remove the seemingly unneeded programs, services and widgets that come with the tablet. Maybe I'm just ignorant about these things, but at this time things like messaging (IMO), mapping, and some of the other default features are of no use to me. They seem to be eating up a lot of resources. I can kill some of the services I think they are associated with, but they keep popping back up.
I did watch the "noob" video (color me a tiny ant to be squashed) and did try to search for an answer to get me even started. I've read the huge main A2107A thread (80+ pages) and tried three of the suggested ADB drivers with my Vista 32 setup for my A2107A-F. The only one that even seemed to connect was ADPnet and it showed the tablet as a Android Phone. Maybe I'm just too paranoid, but after the multiple "brick" posts I'd like to make sure I'm on the right path before trying to "root" the device which appears to be the first step in removing all the extra stuff Lenovo added.
Not that it matters, but I've had the tablet for almost two weeks now and my favorite things are Slacker Radio, Scrabble, Roll It and Zen pinball. I do play Words with Friends with my wife, but I don't like it since some of the words they allow are not valid in Scrabble (which I used to play as an expert competitively face-to-face).
If you are so inclined, feel free to PM me for a Scrabble game. I promise I will not use anything other than my brain and the built in dictionary to make my plays. (I'm a bit rusty since I gave up competitive Scrabble in 2006).
So, long story short... Thanks in advance for any and all advice you can give on slimming down the Lenovo A2107A-F. And if you want an honest Scrabble challenge feel free to PM me.
As far as checking if your drivers are installed properly I would open a dos (command) prompt in window and from within the window change to the directory where you have the 4.03root files. From the command prompt type 'abd.exe shell' and you should see something like "[email protected]:/ $". If you don't see this then you will not be able to root! You need to make that USB debugging is turned on on your device you have an entry in the device manager for ADB Interface (expand on the device which you have showing up).
I am no expert, and I struggled with this on my first go also
Once rooted you can then install Titanium Backup from the play store and use it to get rid of the bloatware! Proceed with caution however as it is possible to remove critical system apps!
degsie said:
As far as checking if your drivers are installed properly I would open a dos (command) prompt in window and from within the window change to the directory where you have the 4.03root files. From the command prompt type 'abd.exe shell' and you should see something like "[email protected]:/ $". If you don't see this then you will not be able to root!
Click to expand...
Click to collapse
Thanks! That's the type of test suggestion I was looking for to make sure I was on the right path with the driver.
So has anyone tried creating a rom for this tab yet? I've been doing some research into porting another rom to work on the A2107A-F, but want to make sure there isn't one already.
I just received a notification of a new firmware update for the A2107A-F. This would be the second available update.
Has anyone else gotten this and taken the plunge yet? I'm curious if this is possibly Jellybean, as some of the larger screen IdeaTab models run this.
Sent from my IdeaTab A2107A-F using xda app-developers app
ssenemosewa said:
I just received a notification of a new firmware update for the A2107A-F. This would be the second available update.
Has anyone else gotten this and taken the plunge yet? I'm curious if this is possibly Jellybean, as some of the larger screen IdeaTab models run this.
Sent from my IdeaTab A2107A-F using xda app-developers app
Click to expand...
Click to collapse
DON'T DO THE UPDATE!!! I lost root access and now I don't know whether or not if I try to re-root if its gonna brick my tablet!
Kevin147 said:
DON'T DO THE UPDATE!!! I lost root access and now I don't know whether or not if I try to re-root if its gonna brick my tablet!
Click to expand...
Click to collapse
I lost root after applying the first update a while back. That's typical when updating. Afterward, I was able to re-root mine again using the same procedure as before. All was well. So, don't panic...yet.
Can you report on what other changes the update made? Is it Jellybean? Or maybe ICS 4.04?
ssenemosewa said:
I lost root after applying the first update a while back. That's typical when updating. Afterward, I was able to re-root mine again using the same procedure as before. All was well. So, don't panic...yet.
Can you report on what other changes the update made? Is it Jellybean? Or maybe ICS 4.04?
Click to expand...
Click to collapse
Well, I just re-rooted my tablet and everything was successful! There is absolutely no difference AT ALL with that so called "update".
Kevin147 said:
Well, I just re-rooted my tablet and everything was successful! There is absolutely no difference AT ALL with that so called "update".
Click to expand...
Click to collapse
Although I have my A2107A rooted and tweaked to my satisfaction, there are a few lingering issues that I'd hoped an update would correct:
1) The neutered Bluetooth stack. The tablet is supposed to work with Bluetooth keyboards, mice, etc. It doesn't. Although I've gotten it to talk to an external GPS module, other Bluetooth data connections simply will not work. Oh, and Bluetooth audio? Forget about it!
2) Some settings that are present in stock ICS builds are just omitted in this one. As an example, the ability to specify a default TTS voice. It's present under settings in my wife's tablet and every other ICS build I've ever encountered. Not this one!
Sent from my IdeaTab A2107A-F using xda app-developers app
Kevin147 said:
DON'T DO THE UPDATE!!! I lost root access and now I don't know whether or not if I try to re-root if its gonna brick my tablet!
Click to expand...
Click to collapse
I was rooted too, lost root access (only with some apps!) after the 130221 update Feb 28. I'll try the same root procedure as before to see if I can get it back. Glad to see a thread on the popular US version A2107A-F. Maybe someone will port Jelly Bean to this tablet! Doesn't appear Lenovo wants to do it...
Rob
I cannot get this 'update' to install after downloading. The tablet reboots to CWM during the install (I am rooted with CWM installed) and when I attempt to manually select the update.zip from /sdcard/googleota/ I get on error (status 7). In desperation I re-loaded the stock rom that I found on another thread and when the tablet attempts to update I get a "assert failed apply_patch_check( /system/app/applicationsprovider.apk)" error Anybody any ideas?
degsie said:
I cannot get this 'update' to install after downloading. The tablet reboots to CWM during the install (I am rooted with CWM installed) and when I attempt to manually select the update.zip from /sdcard/googleota/ I get on error (status 7). In desperation I re-loaded the stock rom that I found on another thread and when the tablet attempts to update I get a "assert failed apply_patch_check( /system/app/applicationsprovider.apk)" error Anybody any ideas?
Click to expand...
Click to collapse
I'm in exactly the same boat as you. I'm getting the same exact error. except that I do not have CWM installed (I am rooted though). Perhaps there's a problem with the update.zip?
Something odd that I noticed however: After the tablet reboots into recovery mode, the update fails, and I go to browse for the update.zip, the sdcard/googleota directory is missing (along with everything that follows it alphabetically). They reappear upon normal boot. I've tried copying it to a directory closer to the beginning of the alphabet and it does show up while in recovery mode. But it still will not install.
Maybe I somehow do not have the available space to perform the update? Is that possible? I show plenty of available space on both sdcards. Could we somehow be below a certain ROM space threshold necessary for an update?
I think in my case because I loaded a 'stock' rom I got from another thread, this rom is failing a verification test the update is doing before install. I do not know how to get around this! I'm continuing my search, but I am not so confident this will be resolved easily...
degsie said:
I think in my case because I loaded a 'stock' rom I got from another thread, this rom is failing a verification test the update is doing before install. I do not know how to get around this! I'm continuing my search, but I am not so confident this will be resolved easily...
Click to expand...
Click to collapse
Well, I am running a stock rom. I am unwilling to "mess with success" until there's a 100% reproducible way of recovering if it fails. And, so far, everything I've read in the other A2107A thread has been hit or miss for the A2107A-F people.
Anyway, If the update is performing a verification test, then it my "virgin stock ROM" should certainly pass it. The only thing that I did is to root it. Hmmm...could the update be testing for that and refusing to install if it detects a rooted device? I would tend to doubt that, since the previous ota update went just fine. I lost root in the process but easily reapplied it afterward.
Thoughts?
Interestingly, I flashed the A2107A-F_S483_121115 rom (again, found in another thread) as I was having verification problems with the OTA update just released from lenovo which was available from the A2107A-F_S484_121211 flashed rom. While the S483_121115 rom appears to be older, I no longer get the option to update via OTA as the tablet is telling me that my s/w is up to date! Go figure.
It's really too bad this device hasn't taken off. If I actually knew how to dev then I would start developng ROMs for it. I'm enjoying it now that I have root and got rid of bloat.
Hey guys. Just wanted to say if someone can send me a stock rom and be willing to test, I'll try to do up a good rom for the -f models. I'd use mine for the stock rom, but I've edited a lot of the system, so no go there. If you have the stock rom or want to be a tester, let me know.

[Completed] Root Galaxy Tablet SCH-I905 Tryed everything

I've tryed everything to try and root my Samsung Galaxy Tablet 10.1 4G(Verizon) SCH-I905. I've used Bin4ry, tryed to flash cwm via odin(says it successfully flashes, then i try to flash superuser, the recovery still says android.) I've searched and tryed everything to no avail. Can anyone point me to some good directions on how to root this dang device.
Specs:
Samsung Galaxy Tab 10.1 16GB
SCH-I905
Current Android Version: 4.0.4
Anything else just ask.
Hi,
Please give me a few minutes to see what I can come up with as I don't find that device on XDA.
Back soon with my findings- check Post #4.
I'm pretty sure this is the guide that can help. It even claims to be super easy.
http://forum.xda-developers.com/showthread.php?t=1657758
People report success in the thread. But as hinted above, may want to ask in this thread if its for sure for your model.. Before flashing anything.
Good luck!
Edit: I looked through the thread a bit....apparently its outdated. Also, there's posts claiming there's no root method for 4.0.4 for the i905. Perhaps my colleague above will have better luck.
Pony Express said:
Hi,
Please give me a few minutes to see what I can come up with as I don't find that device on XDA.
Back soon with my findings- check this post.
Click to expand...
Click to collapse
Edit: Here is a post on XDA that will hopefully guide you to success in rooting your SCH I905.
And a bit more info from Google.
Also be cautious as Verizon models have been known to be difficult or even not possible to root.
As always, read carefully before proceeding and remember to make a backup first.
Update: Tryed using this meathod: http://forum.xda-developers.com/showthread.php?t=1837605
Official ClockworkMod 6.0.1.2 Recovery:
When i try t flash it says
"Write data size is too big[8|SOS]! [Data:5685248(B) -> Part: 2560/2560(2kb)]
Tegra_Nand_Write: Error to DownloadPartition_odin![0xffffffff]"
The problem I see here is most the guides and posts about that device are quite old. Links end up dead after so long and the files are hard to find.
Its not part of XDA, so use at own risk , but the link "Google" that Pony Express posted may be your best bet.
Hopefully it works out. ?
Pony Express said:
Edit: Here is a post on XDA that will hopefully guide you to success in rooting your SCH I905.
And a bit more info from Google.
Also be cautious as Verizon models have been known to be difficult or even not possible to root.
As always, read carefully before proceeding and remember to make a backup first.
Click to expand...
Click to collapse
I just keep getting the same crap "Signature verification failed" I still have the "Android system recovery <3e>" I've tryed to get CWM recovery flashed but get the error i posted in the last reply i posted.
I can only find out dated info here on XDA. And dead links.
Did you try the Google link above?
Also i've tryed that google one 5 times to no avail says everything goes smooth but then i try root checker or look for SU, nope lol. I mean i've never rooted a tablet before but many phones like Droid X, Droid X2, Rzr Maxx, Rzr Maxx HD. So i mean i know the gist of what should happen yet nothing.
Well, honestly, I could post a dozen links to other websites here....but I don't know what works and what doesn't out there.
My advice at this point. Google "root sch-i905 2014". Look for things posted from this year. I've seen a lot, but can't read them all, or try them obviously. Lol
Hopefully you find what you need. Seems there's others as frustrated as you with the same device. That's what happens when devices age.
Again, good luck!
lancemdewitt said:
I just keep getting the same crap "Signature verification failed" I still have the "Android system recovery <3e>" I've tryed to get CWM recovery flashed but get the error i posted in the last reply i posted.
Click to expand...
Click to collapse
It has been known to happen that once root has been achieved on a device, a manufacturer or carrier will come back and provide an update that causes the root exploit not to work. I have had that personal experience while helping a friend root a device a few months ago.
In summary - your process appears to be sound - unless however there is a device specific recovery ( the one above is for a galaxy s 3 ) that is released after the last carrier/manufacturer update it is likely not to work.
Well thanks for the help anyways I guess I'm SOL, sucks because I don't even like this POS figured I'd like it more rooted....

[Completed] Phone inoperable did nothing but followed steps.

Ok so I am unsure if someone is filtering out OLD topics but i keep coming across FORUM posts from people and it seems like they are getting no help or being referred to NON existent topics.
I just recently bought a HTC ONE M8 H/K from sprint. I have had android for a decade and am seriously tired of the ROOT it people. so I figured why not no down falls and everyone says it is easy. Well I am Murphy last name law and you people have not seen or know the things I am about to post
I recently spent over 32 hours watching video and preparing for ROOTING. I unlocked phone got Pilz touch recovery and everything worked fine. I even got CWM and SUPERSU and Busy box. all of which needed OTHER files to work properly. Again a few forced quits everything was fine.
I wanted to Switch to TWRP and the install didnt go through. however now I have BOOTloop. trust me this is the tip of the berg at this point.
Just short of finding NO help after another 24hrs binge session on the CPU and just shy of RUNNING MY PHONE OVER WITH A DAMN CAR>
I get oh so simple easy fix and the only posts I see are FIXED IT!!! so that helps me approximately as much as my phone helps me make phone calls currently.
After the boot loop SEVERAL friends versed in this so called ROOTING (which I still find to be a hoax and not actually possible by any means at this point and time.) and no one has any clue. Tried flashing ROMS RUU's everything comes back to NO will not work.
Then it brings me to the STOCK RUU config for the HK M8 which seemed like it was going to work through ADB flash but guess what. 2 hrs idle NOTHING. after that The recovery program dropped out and boot loader only stated RUU in the menu. (something never before logged in a forum or post as I can tell) after many attempts to do GOD KNOWS WHAT WITHOUT ANSWERS as i was about to smash my beautiful gold phone into a dozen tiny peices and claim accident the Recovery came back to...... You guessed it NOTHING. All directories are UNMOUNTED and cannot be mounted.
I am stuck. Seriously you all fix my phone or help i am willing to send gifts because I am out 700$ now on this nice paperweight but everything and everyone tells me. OH SO SIMPLE you have recovery it aint no thang.
Well guess what it is and I am tired of being so PISSED OFF for something that was so automated.
Again I am Murphy and what you attempt to get me to follow will come up with some REALLY weird repercussions I will post back.
Please oh mighty gods of ruining my life. Spare me this one thing I will never ask for another again.
How do I get my phone to just WORK, Simple. Right?
Hi there! I think I found a thread that can get you back on track. Please read every word carefully and follow every step. If you have further trouble or want to clarify anything, please ask in the thread. They know the device best and can help you I'm sure.
http://forum.xda-developers.com/showthread.php?t=2503646
I'm afraid that is the extent of what we do in the XDA Assist Section. We are guides...pointing people in the right direction when they can't find what they are looking for. Unfortunately we don't do hands on support in this section, so as I said....if you need a further hand, I am sure someone in the thread I linked can help.
And make sure anything you download and flash is for your model. And as always, do a Nandroid backup in recovery... before flashing anything new....it can be a lifesaver to help restore you when you hit trouble.
Good luck!
Details
Let me re iterate.
All guides are demanding S-Off (cannot as I cannot acess phone apps to do so)
All guides need HOME access for apps to modify certain things
I cannot:
Push packet through adb as they are unreadable
Get past boot screen
Recovery is only 40% operational with visibilty of phone only working sometime.
Cannot flash
Cannot push
Cannot fastboot
Cannot see device on CPU as it is stuck in recovery
ALL DIRECTORIES in /SDCARD have been removed
No Firmware
No RUU
No img
As far as I can tell.....Phone is empty and cannot be populated with anythin. I did manage to get SuperSu pushed through and installed. But how do I open it?
No ROOT access as well in the recovery.
I followed ALL STEPS of EASY guides even downloaded one button app that runs it all for me. Can't talk to phone does not see it in ADB.
The other guide I went to was helpful but I have already attempted all of those things.
With an empty phone NO DATA and no ability to get ADB to even run data over cable I am baffled.
I did exactly like the 500 guides i read said.
1) bootlock unlock
2)instal recovery (Philzmod)
3) get CWM (retrieved from playstore) Need a .zip to run in ADB
Phone worked fine until I changed from Philz mod to TWRP which never took place. Philz mod still runs but TWRP said it installed.
Now I have a completely worthless empty phone and I have cried about a tub worth of tears over the 700 i will be dropping over the next year for a piece of metal.
Oh and 99.9% of time if ADB DOES do something either no directory once pushed, cannot read or cannot FIND/Open directory stating BAD installation aborted I NEED a better recovery
I understand your frustration. Not a fun situation at all.
As I said, XDA Assist is here to help navigate the website. Not to troubleshoot I'm afraid.
The purpose of XDA Assist... http://forum.xda-developers.com/showthread.php?t=2764768
The very best place to ask for help in your situation is right here, in the Q&A section for your device... http://forum.xda-developers.com/showthread.php?t=2764768
The people there know your device best. Start a thread that's to the point, polite and accurate....what is exactly wrong, and the exact steps you took to get there. And hopefully help will follow.
Hope it can be solved for you!

[Completed] [Q] Unable to Install Safestrap

So I have bitten the bullet after all of the issues that I was having with my phone today and I did an SBF flash of my Droid 4's firmware. I rooted successfully and installed Busy Box, but I am unable to install Safestrap v3.72
I get to the 60/100 point where it is "Running Installation Script" but it never gets beyond that. I have also tried to Uninstall in case one of the several tries worked behind the scenes, but that also gets stuck at 60/100. This allegedly has something to do with Busy Box not being installed, but I have done that for sure.
Update: Just repeated the root process with SafeRoot and that installs Busy Box as part of the process. Completed successfully, and I'm still hanging at 60/100...
What else am I forgetting to do?
@joefuf
You have already created a question on this topic which is being worked with you by one of our XDA Assist staff members.
HERE: http://forum.xda-developers.com/general/xda-assist/enter-safestrap-recovery-t3099529
Please follow XDA Rules regarding double posting.
This thread closed

[Completed] [Q] cant install any roms ls980 other than cloudyg2

After I had downloaded the 5.0.2 lolipop update for my sprint G2, I quickly began to hate it. battery died too fast, seemed slower, didn't like the look or really any thing on it. As a result i decided to root my phone and try to get back to android kit kat. After several hours of reading, and many trials and errors (most methods didn't work) I got it rooted through kingroot, as well implemented 2.8.6.1 TWRP recovery with autorec. After, I downloaded the cm11 rom and attempted to install it through the recovery (just as every single tutorial on the internet had done it) and all i got was. "error executing updater binary in zip." even after downloading other roms from different developers, none worked, and all got the same error. (and yes, I made sure all of the roms were compatible for my G2)
the only one that did work was cloudyg2, although I couldn't enable data even after spending 3 hours applying patches and trying other fixes. then I tried to install another TWRP version, but none will work, and subsequently end up giving me an error when I try to boot into recovery.
Overall, I would just like to know, what the heck is up with my phone, and why is nothing working, and maybe point me to a solution to reunite me with my beloved kit kat. doing this Would make me a very very happy android noob.
Hi, thank you for using XDA Assist. I see you've asked this in a couple of places. But the best place is in your device's specific forum here,http://forum.xda-developers.com/sprint-g2. I'm going to ask a moderator to move your question to here, http://forum.xda-developers.com/sprint-g2/help. Also, in the future, only ask your question once per XDA rules. It gets really confusing if you ask in multiple places.
Thread closed.

Categories

Resources