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.
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.
Hello all. I am a relatively new member to XDA and I have actually posted this issue on the thread to from which I downloaded the custom ROM I'm running. I am using and LG G2 D800 running [ROM][5.0][CM12][UNOFFICIAL][ALL-VARIANTS] CyanogenMod 12.0 For The LG G2, which I installed about a month ago. I originally rooted my phone using towelroot and installed TWRP custom recovery 2.7.0.0. I installed 3 or 4 other custom ROMS, using just my phone, that I honestly had no idea how to root using a computer. Since, then I have learned and acquired the tools I need to root from my computer, and after trying for quite some time, was able to find drivers for my phone that allowed my computer to recognized it.
There are 2 main problems that arose about a day after installing this ROM.
Firstly, after I had installed all of the pertinent files needed to flash the above ROM, I attempted to install the beta version of SU that the thread related to the above ROM said was necessary to keep root. Well, that version did not install correctly, though the ROM did install and is working about as well as an experimental version of a ROM can....
Once the ROM had been running for about a day or so, I realized how buggy it was and decided that it would be smart to go back to a more stable ROM as Lollipop was just around the corner(Or at least a stable CM12).
So, I went to go back into my TWRP custom recovery to do a wipe then install another ROM that I had backed up. When I attempted to do this, I realized the 2nd BIG PROBLEM, my phone had stopped recognizing my internal sd card, so I was unable to view any Backups I had previously saved. So, I started researching and found the the adb shell code to get my phone to recognize my sd card, but when I tried to use the command to do so, I was given the reply that su(part of the command) could not be found. So, I posted again, and was told,"you need to re-root." Well, that is good and well, but I have tried every method I can find to root my phone from my PC, but they are all for LG G2 D800 running some lesser version of android, never 5.0....
Any help would be greatly appreciated, and oh yeah, I was able to get the new Beta super SU file pushed onto my phone and saved in the remaining space it does recognize, but I couldn't actually install it to give me SU priveleges again. Basically, if I can re-root, I can get my SD card back, do a full wipe, then install another more stable ROM ASAP>
Thanks again, so so very much. Please, Please help me get this phone working. I'm feeling more and more like a fool everyday knowing Im paying for a phone I can barely even use....
Happy Holidays,
Thad
Hi,
Asking in the rom thread is a good idea. If you don't find answers there, then you can ask for help in this dedicated help thread in your device section,
> LG G2 > G2 Q&A, Help & Troubleshooting > [HELP THREAD][Noob Friendly] LG G2 Ask any question
XDA Assist is here to help navigate the site, not for support. ?
Good luck!
Hello All,
Well Ive had my head buried in the xda forums for about a week and a half, two weeks now so I decided to post my issue hoping someone could advise me, I rooted my phone LG G2 D80220c-HKG-XXX, kitkat 4.4.2, Ive tried flashing a couple different roms but it would not take, ( I am sure its rooted ) and the last one cm12 I had to abort and at that point I decided I would just go back to stock and unroot, well to my great pleasure (lol) the ota for lollipops push came to my phone and guess what!!! I left it with my dad, and not knowing what it was excepted it thinking it was a app update of some kind, no problem, it was stuck in cwm recovery loop, after researching the forum I used Minimal ADB and Fastboot from 'shimp208' and ADB shell code to boot from 'thecubed'' post [fix] Installed TWRP and now you're stuck OTA, To shorten this long story, Im operating on basic os 4.4.2 now and discovered that my imei # is that of a D800 but my build number is KOT49I.D80220c, baseband version is M8974A-AAAANAZM-1.0.190084 and of course the software is in the above text, so now I have no clue what firmware to use to go back to stock, I'm thinking D800 but I dont no where or even if what I need exists, Ive searched where, does anyone have any ideas, thanks for reading and for any help.
Hi, Nice phone - should be able to find help here lg-g2/help
Hope this helps !!
First a few disclaimers to explain why I'm here.
- My secondary intention with this question is finding some answer as generic as possible to also help other people. Of course my primary intention is fixing my own issue, but the biggest part of it from what I can tell in the past 8 hours have been finding ROM files. All links are broken, except for 4.1.2 and none of those worked for me. In fact, they bricked my phone pretty hard.
- I'm on a mac. It's a nightmare finding tools for the mac, but I doubt any of them would really be any use for my case, one reason why I didn't even bother going for a windows vm. Another one is I'm traumatised by installing and running VMs. Finally this is for the challenge and learning a bit more.
- I've being trying to fix this through lots of research in the past 8 hours and I do know a few bits about going around and doing things (so sad this guide had no repercussion so far). But clearly, I'm dumb enough to brick my phone twice with no backups. At least could figure it out the first time (I had more time in hands as well). Please consider this. This means I've tried a lot of stuff you may wanted to advise, but it also mean I may have missed something obvious in the middle.
Okay...
By "bricked" I mean:
1. I can't go through the same process I did before to flash any CM image. CWM won't flash CM11 and CM12 recovery complains my bootloader isn't 4.4.
2. Both CWM and twrp recoveries should allow touch. None work, so I an't use twrp.
3. Battery keeps getting low and I've got no clue how to charge it to full again or even see how much it is at without installing twrp, which keeps getting uninstalled randomly at reboots, despite all of this topic about a solution. `fastboot getvar battery-voltage` doesn't show it. The mac script (which I was about to write myself based on op) also doesn't seem to help. In my case, I've removed the `./fastboot` because I've got it on my shell path.
I believe (1) happened, as I said on the disclaimer, right after I've flashed one of those 4.1.2 ROMs. By "flashed" I mean running the BAT file which mostly works on mac. ECHO of course wouldn't show the messages of progress there, but all fastboot commands do run.
And I also believe if only I could find 4.4 stock ROM files they might work or, at least, bring bootloader back to where it was so I could install CM12 again. And as far as I could notice without having Windows to try, no windows tool would really help here. That RSD Lite for instance, looks like it's just a GUI to run fastboot commands.
Above ALL
I just wanted to find a ROM stock file which I could fastboot flash into xt925 to reset it as hard as possible from zero and that the link will probably not break in the future for whoever may need it.
I figured THIS shouldn't be too hard to find, even for mac only, but it has been.
PS: Being able to fix the battery thing is also very important and quite a relevant follow up on the question! Right now I'm stuck with a ROM file that might work, but got no battery to try! ( 10 hours debugging now... )
only one stock kitkat rom for XT925 ! i'll upload this for you !
You know, if this works I'll have to, at least, go through some of your 187 posts and find a dozen or so to thank you way more than once!
I've now downloaded [this one](http://forum.xda-developers.com/showpost.php?p=63163078&postcount=6), which [he also posted again later on](http://forum.xda-developers.com/showpost.php?p=63272842&postcount=2), hoping it will do it! If it does, I'll try to upload in this post, as it looks like XDA hosted files last for much longer than anything else.
Only problem for flashing anything now is I can't seem to get enough battery!