Related
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.
Hey guys!
To start, I want to say what an amazing place XDA is and how much information and knowledge you can get from here and how awesome the moderators are. I don't think I could ever find another amazing and/or helpful community such as those found here! Thanks to all who have helped me out with my Android issues!
Now to my issue and I apologize ahead of time if there is another thread (or related thread) found in the forum.
As the title states, I have a 2013 Motorola Moto G XT1031 Boost Mobile device. I had upgraded it to Lollipop 5.0.2 or 5.1 when it came out (I can't remember which one it was) and I had then decided to root it. I can say that I believe I was successful in rooting the device because I was able to install Supersu and use RootChecker to verify the install. Everything was going okay until i decided to research and eventually install a custom recovery and attempt to install a custom ROM. Well, let's just say that the recovery install was a bust...
In doing my research for a custom recovery, I found that TWRP had a custom recovery for my phone and apparently for my firmware via TWRP's app on the Play Store. So, I searched for my device in their in-app search for a custom recovery, downloaded it and installed it from the app. Now, my gut told me that this probably wouldn't work and that I should probably be installing a custom recovery via CLI. Nope. I didn't do this. Instead, like I said, I installed a custom recovery from the app itself. That screwed things up for me. I have no idea if it was the install, but my phone began to act incredibly strange. When in the TWRP recovery, my screen had this line that would continuously scroll from top to bottom. It wasn't a completely solid line, but it was transparent, almost like an empty thermometer glass stick was going down the screen. It was weird and not normal. I figured the phone's software was partially broken. It only did this in the TWRP recovery. Nowhere else did this happen. It was slightly annoying.
Later on I decided to install a custom ROM. Again, I did the necessary research to find out if there were any ROMs available for my phone (using XDA of course and others) and found that there were a few out there. So, I downloaded one (wish I could remember which one) and attempted to install it...keyword there. After attempting the install, my phone would not boot. Like at all. Dead. So back to the drawing board I went to try and reverse the damage. Using XDA (ironically) and a plethora of other sites, I tried to resurrect my phone and bring it back to life. After countless hours of trying and trying and trying and more and more research, I just gave up. The phone is dead. Great. $170 spent on a phone to break it a year later.
It's been roughly 4-5 months since I have attempted to redo the process and after another minor attempt, somehow I was able to remove the root completely, including the custom recovery and ROM. I don't know what the heck I did, but it worked....sort of. The phone is now stuck in a bootloop on the logo and sometimes the "bootloader has been unlocked" screen when try and factory reset the phone from the default recovery. When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set and to have this and that. I have this and that installed on my PC, but obviously cannot enable USB-debugging which is needed for ADB and fastboot to recognize my device.
So, my question for anyone who would like to help me out is this: what are my options? Is the phone recoverable? Is there any way I can get ADB/fastboot to see my device and finally install the stock firmware on the phone? I have the proper drivers installed and ADB/fastboot are on my PC. Any help would be amazing, even if you have to tell me to junk it.
blckdragn22 said:
When trying to reinstall the stock firmware, I read everywhere that I need the phone to have USB-debugging set
Click to expand...
Click to collapse
This is incorrect, where did you read that? To reinstall the stock firmware using fastboot, you must be able to boot to the bootloader menu only.
I heard this from a few websites actually, although I could never find a situational fix for my phone. I am trying to restore back to Lollipop without a custom recovery, because within the past hour I found out TWRP was never fully removed when I tried booting into recovery from the AP Fastboot menu when doing to power+vol down option. The TWRP logo shows for about 10 seconds and then the phone tries booting normally, showing the unlocked bootloader warning.
So, yes I can boot into the bootloader menu all day long with no problems. It's just an selection I make doesn't get me anywhere. My question I guess now is: how do I go about reinstalling stock firmware via the bootloader menu. I have Minimal ADB and Fastboot installed on my PC. If I need the full ADB, I can download that. And of course I'd need the firmware, too.
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
This thread had the firmware I was looking for thank you. I believe I have the flashing stock firmware process down, I hope. I'l refer to the guide if I need help. Thank you so much!
_that said:
You can find stock firmware images in this thread, there's also a link to an installation guide there:
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795
Click to expand...
Click to collapse
I am trying to follow the steps listed here http://forum.xda-developers.com/showthread.php?t=2542219&page=35 and for some reason I cannot run any of the commands pertaining to the sparsechunks. This is what I get:
Is there anything you could tell me about that?
Edit: I was able to figure what the issue was when trying to write the sparsechunks. I had to insert a "." after 'sparsechunk' because that is how the file is named in the folder. However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
blckdragn22 said:
However, now I am getting a new error, but it takes place on the phone screen. Every time I attempt to write a sparsechunk, it will initiate the process of doing so, but on the phone I'll get what appears to be an error saying, "Image is too large" in pink lettering. Why does this happen? Each sparsechunk file is at least 4MB less than the max-sparse-size according to the ADB and my phone, which is set to 256MB. Is there any way to change that?
Click to expand...
Click to collapse
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
_that said:
Check which sparsechunk files you have and make sure you flash all of them in ascending order. If it still fails, copy/paste the contents of your command prompt window (no screenshots please).
Click to expand...
Click to collapse
I will try that. There was a ...sparsechunks.0 as well apart from sparsechunks.1, sparsechunks.2 and sparsechunks.3. Shall I include that, too?
And adding the screenshot was an amateur mistake. My bad.
@_that this worked like a charm. Phone is 100% working ans usable now. Incredibly helpful. Thank you so much!
hopefully this will help out some people and the developers to make,fix,restore a not so popular phone. I did a total firmware dump and have uploaded to my 4shared folder. If anyone is interested or can tell me how to upload it here for developing i will be more than happy to share with those in need. I also have a spare phone that i would be willing to test anything made from the firmware dump i created.
PLEASE link?
Some time after rooting my Optimus Zone 3 VS425PP, I got locked into a boot loop. There are no custom ROM's, neither recovery nor OS. It's not bricked. Yet, anyway. The loading screen functions, then a little window that says "OPTIMIZING APPS 1 OF 5, PLEASE DO NOT REMOVE THE BATTERY..." appears. I've seen this before, but now, upon reaching "APP 5 OF 5," it reboots and repeats. I've tried several factory resets via the LG RECOVERY (MODIFIED,) as well as safe mode to no avail. Anyone? Anything? Help? The only recourse I can think of would be to re-flash the stock ROM, which I cannot find. Anywhere. Thanks, guys.
i tried contacting judthro for the same file; no luck
Cruise Elroy said:
Some time after rooting my Optimus Zone 3 VS425PP, I got locked into a boot loop. There are no custom ROM's, neither recovery nor OS. It's not bricked. Yet, anyway. The loading screen functions, then a little window that says "OPTIMIZING APPS 1 OF 5, PLEASE DO NOT REMOVE THE BATTERY..." appears. I've seen this before, but now, upon reaching "APP 5 OF 5," it reboots and repeats. I've tried several factory resets via the LG RECOVERY (MODIFIED,) as well as safe mode to no avail. Anyone? Anything? Help? The only recourse I can think of would be to re-flash the stock ROM, which I cannot find. Anywhere. Thanks, guys.
Click to expand...
Click to collapse
Unfortunately, I don't think this file is actually out there. I have REALLY been looking, even contacted the LG Development team. The LG Support Tool, etc. are not going to help you yet as they do not have the firmware on their servers yet. That's why the LG Support Tool will freeze when trying to do an Update Recovery on this phone. -- And I've tried them all: LG Mobile Support Tool, LG PC Suite, Verizon VS425PP Update Tool (from the mounted drive on the phone), LG Flash Tool 2014 to force different KDZ files. All provide nothing. All dead ends. The Optimus won't grab a COM unless it is the right signed firmware for the phone. You'll just sit there in Download Mode or in Debug mode forever with no result. We have to wait for the first update from LG from version VS425PP1 to whatever comes next so they have something to stick on their server. But...if you find something before then, please let me know! The update will eventually be released to the public. It'll probably just take a year or so.
Good thing is Wal-Mart sells these for under $12 (yes, that's right). I picked up seven of these quad-core bad boys at that deal. Just bugs the hell out of me I can't fix the one I over rooted.
this *might* be promising...
Cruise Elroy said:
Some time after rooting my Optimus Zone 3 VS425PP, I got locked into a boot loop. There are no custom ROM's, neither recovery nor OS. It's not bricked. Yet, anyway. The loading screen functions, then a little window that says "OPTIMIZING APPS 1 OF 5, PLEASE DO NOT REMOVE THE BATTERY..." appears. I've seen this before, but now, upon reaching "APP 5 OF 5," it reboots and repeats. I've tried several factory resets via the LG RECOVERY (MODIFIED,) as well as safe mode to no avail. Anyone? Anything? Help? The only recourse I can think of would be to re-flash the stock ROM, which I cannot find. Anywhere. Thanks, guys.
Click to expand...
Click to collapse
well i'll be. this may be a promising link:
google "4share lgvs425pp" and scroll down to the 4shared link. There is a 999MB RAR file claiming to be the VS425PP ROM dump. I'm downloading it now...checking it out.
It works???!!! i have to root this cellphone because i need use with other company...
its not super useful yet
johhnyapplefake said:
well i'll be. this may be a promising link:
google "4share lgvs425pp" and scroll down to the 4shared link. There is a 999MB RAR file claiming to be the VS425PP ROM dump. I'm downloading it now...checking it out.
Click to expand...
Click to collapse
hopefully the op will chime in for insight. The 999MB isn't much good. It appears to be a RAR dump of all the partitions, perhaps made from a lglaf.py script while in download. Nevertheless, i havent found any way yet to push the firmware dump onto the phone.
I've had no luck, either.
johhnyapplefake said:
hopefully the op will chime in for insight. The 999MB isn't much good. It appears to be a RAR dump of all the partitions, perhaps made from a lglaf.py script while in download. Nevertheless, i havent found any way yet to push the firmware dump onto the phone.
Click to expand...
Click to collapse
Meanwhile, as my LG cycles endlessly through my really cool "Jolly Roger" boot animation, I stumbled across a Kyocera Hydro Wave at Walmart for $20. I snapped it up to replace the LG Optimus Zone 3. I had big plans to root it, too., but I should've researched it first. The specs are great... but one check on Cyanogen's website probably would've saved me some trouble. Not one Kyocera device is listed there. XDA thread also throws red flags-no one can get root to stick. Well, I at least learned a lesson. Next time, I plan to purposefully buy a phone that can be rooted, has been rooted, has instructions online to do so, AND has at least one custom ROM available! No wonder this thing was $20! Keep us all posted if you stumble across a bootloop fix of some kind, and I'll do the same.
here is stock recovery for this device https://www.dropbox.com/home/Apps/Flashify/VS425PP/recovery
matt4787!
Either I am unable to open that link from an Android device OR the link given is to an unshared folder? It just asks me to log in and then says 'that folder does not exist in your DropBox...' PLEASE check out the SHARE link from within your DropBox and maybe share a new folder (and drop the stock ROM in there, along with what you might've used to flash it maybe?) We'd be very grateful!
Recovery
https://drive.google.com/file/d/0B1Nk8cx3_QgAeGNxZ1JrUmtFS0E/view?usp=drivesdk
Try now
hope my post helped some ppl. now to get twrp recovery ported here.
Thank you matt4787!!
Sent from my C6740 using XDA-Developers mobile app
To all who have a bricked,phone this phone has an update. Download the LG software assistant and put assistant in repair mode then boot phone normally and wait a bit. Run the repair assistant and let it run. Hopefully if everything runs well as it did me. Mine is restored and running.
Just ordered one. Is there root for this phone? Unlocked bootloader or forgetaboutit?
I rooted this phone and then tried to de-bloat, but I must have deleted too much. Now when I boot all I get is "Security Error - Authentication Fail #9"
I can get to Download mode, but none of the recovery programs recognize the phone. I installed the drivers, but still nothing. Is there anything I can do?
matt4787 said:
To all who have a bricked,phone this phone has an update. Download the LG software assistant and put assistant in repair mode then boot phone normally and wait a bit. Run the repair assistant and let it run. Hopefully if everything runs well as it did me. Mine is restored and running.
Click to expand...
Click to collapse
was your phone in a "security error" loop? for some reason the software assistant won't recognize my phone. it'll identify a plugged in phone when I connect it in download mode, but the device model never shows up
nikicollazo said:
was your phone in a "security error" loop? for some reason the software assistant won't recognize my phone. it'll identify a plugged in phone when I connect it in download mode, but the device model never shows up
Click to expand...
Click to collapse
i forgot to mention that you have to be in download mode to make the assistant recognize the phone. plus make sure the drivers for the phone are installed on your pc
matt4787 said:
i forgot to mention that you have to be in download mode to make the assistant recognize the phone. plus make sure the drivers for the phone are installed on your pc
Click to expand...
Click to collapse
hello as you did to install the drivers , I find no way to reconnoitre the mtp device ! Thank you
angelgabg said:
hello as you did to install the drivers , I find no way to reconnoitre the mtp device ! Thank you
Click to expand...
Click to collapse
this one is troubling. hmm you got the stock rom from lg? if so then try downloading the drivers from verizon.
Any updates on recoveries? I hate being scared of tweaking due to not having a backup .-. Anyone find something? Plz lemme know, thx! Btw kingo root 4.5 seems to have root for this phone but super sume seems to brick it. Just a heads up eace:
Hopefully it isn't but I have a bad feeling.
I haven't been here for a long time, life got in the way and I didn't have time to play around with things. A few years back, I rooted my TF101 and installed Cyanogenmod. It sat in a drawer for most of the last year.
A few days ago, I decided to try a different rom that sounded cool. Attempted to flash it but it didn't go right. Could only boot into recovery. So I tried to sideload TWRP via ADB. I followed some steps I found here, or somewhere else on the internet, not sure now, but it said to delete pretty much everything first. I deleted everything it said to, but I think that was a bad move.
I can now only boot to APX mode. I have tried using Easyflasher to "unbrick" it, but Nvfalsh just hangs. Same if I try to install a recovery with it.
So is it time to give it up and use it for a target the next time I do some target shooting?
EDIT: Sorry, I kept getting interrupted with work calls. When I said I could only boot to recovery after attempting to install the new rom, I meant fastboot. When I used volume up to select recovery, I got an unrecoverable bootloader message. It was at this point that I used fastboot to try to install TWRP. After doing that, it hangs on the ASUS splash screen and APX is all I have now.
Well I really screwed up! Like I said, it sat in a drawer for a year, and I don't know WHY I had it in my head that it was a 101. It's a TF701T. So attempting to flash a 101 rom has probably totally hosed it.
If anyone has any suggestions, that would be great. Otherwise, I have a new target this weekend!
Bluze said:
Well I really screwed up! Like I said, it sat in a drawer for a year, and I don't know WHY I had it in my head that it was a 101. It's a TF701T. So attempting to flash a 101 rom has probably totally hosed it.
If anyone has any suggestions, that would be great. Otherwise, I have a new target this weekend!
Click to expand...
Click to collapse
I know this is a few weeks old but in case you are tracking, how about heading over to the tf701t thread and see if you can find anything helpful. the 701t would be worth the hassle of trying to unbrick
Did you know the Virtual Machine? Any kind(Virtual Box, VMware, etc...). I think that you can use virtual machine to create a Windows XP. In the WinXP, driver verification problem did not like Win7, Win8.1, Win10, you can easily install APX Driver without any problems, and i guess you can run the "Easyflasher" correctly.
I had the same problem when i use the latest "Clock Work Mod" recovery for TF101, the recovery can't mount SD card, so if you can flash back to asus rom with Easyflasher, I suggest you flash the TWRP V2.8.1.1, the flash file can be found on XDA Forum, hope you can resolve your problem
Hi all, a few months ago i had a perfectly running rooted TF101 with stock asus firmware. It has CWM recovery v6.0.1.3 and i had the CWM app installed.
somewhere along the timeline i decided it was a good idea to backup the whole thing using the CWM app just in case anything funny happens. Now don't ask me how or why it went the way it did, but the CWM app seemingly performed its backup, there was a disclaimer warning somewhere about possibly losing root access, to which i think i said "yes", the device rebooted and my entire image was gone - only left with CWM recovery mode.
I have been trying to reflash it with stock recovery image, but the SD card won't mount. I am also unsure whether i still have root access or not.
in terms of connectivity, all i was able to get back was ADB access, which i was able to search xda and find threads such as these to try and fake an sdcard then reflash
https://forum.xda-developers.com/showthread.php?t=911228
I've tried katkiss image and stock image but everytime i get a status 7 error or an error 21
https://forum.xda-developers.com/nexus-6p/help/zip-file-signature-verification-error-t3561054
https://www.**********.com/fix-status-7-error-while-installing-ota-update-or-roms/
I'm not exactly an ADB crackhead and I'm not able to get past it so i've searched some more and found on xda again threads on using EasyFlasher, I've followed the instructions but can't get the APX drivers installed on windows 10.
https://forum.xda-developers.com/showthread.php?t=1688012
basically, at this stage i've read many articles, many posts, none have worked because links are outdated or instructions are outdated and mostly i'd rather stop trying all i am finding without really understanding before i brick this device for good out of ignorance.
sure it's old but it was functioning properly and was being used actively by my kids. if i can get it back to life, that'd be nice.
has someone experienced (and fixed) something similar or feel can contribute to unbricking my device?
Thanks guys.
I'm a noob myself, but I managed to get the APX driver installed on Win 10 (just now) by following the directions at how to geek dot com. I used "Option two: Use an Advanced Boot Option."
Good luck!