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.
Someone please please help me. I am in desperate need of a solution. And before I lay out the issue I am having, I would like to thank everyone for taking their time to read through my post and give their input. I truly appreciate it everybody. Much much thanks.
Just as a disclaimer, I've looked all over the internet, everywhere I can possibly find for days on end, and none of what I found worked for me. It feels like I tried everything there could be, and that is why I am coming here. Again, thank you.
So here's a little background information: I have a Verizon Samsung Galaxy S4 (SCH-I545). I got the phone over the summer, and as soon as I received the phone I was updated to the apparently dreadful VRUMAE7 update. There afterwards, I tried rooting the phone. I've had rooting experience before with decent success, and never ran into problems like I did. It took awhile for me root my S4, but after awhile I was able to successfully root it. Although, I'm pretty sure I may have done something wrong. You will see why shortly.
So a week or two back, my S4 prompted me to update to the next update. I believe it was Android 4.3 (VRUEMJ7). I was very excited for the update and tried running it. But every time I accepted the update and tried updating, my phone went into Recovery to download the new update and stalled out with an error. Thereafter I would have to reboot the phone to get it working again. After failing to update multiple times, I realized that it is probably because I messed up my root. So without doing much research, I simply tried flashing the stock firmware that came with my phone thinking it should work pretty flawlessly.
I have a Mac OS, so using VmWare Fusion with Windows 7, I downloaded Odin and booted up my phone on Recovery mode, downloaded the stock VRUMAE7 firmware I found online, and began flashing. But Odin threw me a error, so I tried rebooting my phone thinking it would go back to normal. BUT this time, it kept going into recovery mode with a yellow Triangle saying firmware was installed incorrectly, etc. I was so frustrated at this point, thinking that I truly may have bricked my phone.
I began on this long journey of going through all the sources I could find online possible, downloading every type of Verizon S4 firmware I can find, trying every Odin method possible, and spending long long hours of the night biting my fingers at my dreadful fate. I even tried flashing the stock PIT File along with my stock firmware, to see if that would fix it. But no luck. I also tried using a standard windows machine rather than VMware, still with no luck.
I ask you all to please suggest any ideas, thoughts, or inputs you possibly can. I am willing to try anything and everything at this point. Please do help. I appreciate you guys reading through my lengthy question, sorry for that. Just wanted to lay everything out.
Thank you very very much.
muazra said:
Someone please please help me. I am in desperate need of a solution. And before I lay out the issue I am having, I would like to thank everyone for taking their time to read through my post and give their input. I truly appreciate it everybody. Much much thanks.
Just as a disclaimer, I've looked all over the internet, everywhere I can possibly find for days on end, and none of what I found worked for me. It feels like I tried everything there could be, and that is why I am coming here. Again, thank you.
So here's a little background information: I have a Verizon Samsung Galaxy S4 (SCH-I545). I got the phone over the summer, and as soon as I received the phone I was updated to the apparently dreadful VRUMAE7 update. There afterwards, I tried rooting the phone. I've had rooting experience before with decent success, and never ran into problems like I did. It took awhile for me root my S4, but after awhile I was able to successfully root it. Although, I'm pretty sure I may have done something wrong. You will see why shortly.
So a week or two back, my S4 prompted me to update to the next update. I believe it was Android 4.3 (VRUEMJ7). I was very excited for the update and tried running it. But every time I accepted the update and tried updating, my phone went into Recovery to download the new update and stalled out with an error. Thereafter I would have to reboot the phone to get it working again. After failing to update multiple times, I realized that it is probably because I messed up my root. So without doing much research, I simply tried flashing the stock firmware that came with my phone thinking it should work pretty flawlessly.
I have a Mac OS, so using VmWare Fusion with Windows 7, I downloaded Odin and booted up my phone on Recovery mode, downloaded the stock VRUMAE7 firmware I found online, and began flashing. But Odin threw me a error, so I tried rebooting my phone thinking it would go back to normal. BUT this time, it kept going into recovery mode with a yellow Triangle saying firmware was installed incorrectly, etc. I was so frustrated at this point, thinking that I truly may have bricked my phone.
I began on this long journey of going through all the sources I could find online possible, downloading every type of Verizon S4 firmware I can find, trying every Odin method possible, and spending long long hours of the night biting my fingers at my dreadful fate. I even tried flashing the stock PIT File along with my stock firmware, to see if that would fix it. But no luck. I also tried using a standard windows machine rather than VMware, still with no luck.
I ask you all to please suggest any ideas, thoughts, or inputs you possibly can. I am willing to try anything and everything at this point. Please do help. I appreciate you guys reading through my lengthy question, sorry for that. Just wanted to lay everything out.
Thank you very very much.
Click to expand...
Click to collapse
Hi there,
it seems an easy problem but do it at your own risk I don't take responsibility of bricked device,etc
so lets go with what you need:
A- Odin [I believe you already have it]
B- stock rom go to this site:
androidayos.com/samsung-galaxy-s4-odin-stock-firmware/
and choose the suitable stock rom based on your Baseband version
C- Drivers installed for your device [if your mac/laptop recognizes your device then skip this step if not google it,download the drivers and install them]
IMPORTANT:Make sure you have 80% or more on battery
after you get these stuff install the device drivers as mentions in C then turn your device off and power it while holding volume up it should take you to download.now open odin and navigate it to the rom which you downloaded from B and flash it .wait for green color to appear and your back to your stock now it should open normally hope that I helped
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!
Hey! I don't know if this is the right place, but I'll try to explain my problem.
Yesterday I got a notification of an update(think it's 6.0.0 (MRA58N)). Today, when I tried to install it I just got an "Error!" message.
I tried to reboot the phone, but nothing happened. It doesn't turn on. However, I can get it into that fastboot screen or what it's called.
Haven't had any problems before, and Im kind of a beginner on these technical issues regarding phones.
So could someone please explain what I should do(hopefully nothing to complicated).
Thanks!
That sounds like a rooted phone. Is it? Have you owned the phone from new, or is it second-hand?
dahawthorne said:
That sounds like a rooted phone. Is it? Have you owned the phone from new, or is it second-hand?
Click to expand...
Click to collapse
It was new when I bought it (april 2014). I have only installed updates when getting a notification on the phone. I got a notification to do an update yesterday. Did it today. But while updating it just stopped and said "Error!". Turn the phone off, tried to turn it on but nothing happened.
What's the easiest way to make the phone work again?
Have in mind that Im not experienced at all with these stuff . Never had had any problems before
Thanks
Were you already on a version of Marshmallow? They are both version 6.0.0 regardless of the name (MRA58K/N).
Was there any message apart from just "Error"? Do you remember what it looked like?
I take it that you have enough battery?
I have no idea of the answer, just trying to get some clues.
(Oh, and at worst you can probably flash a new ROM. Don't get too worried just yet... )
dahawthorne said:
Were you already on a version of Marshmallow? They are both version 6.0.0 regardless of the name (MRA58K/N).
Was there any message apart from just "Error"? Do you remember what it looked like?
I take it that you have enough battery?
I have no idea of the answer, just trying to get some clues.
Click to expand...
Click to collapse
Yes, I updated to marshmallow a couple of weeks ago.
Yes, I was on about 75% battery when trying to update.
As far as I recall it was just the android guy and a red text saying Error! (well it said Fel! because it's in swedish.)
It started to install the updates, but just stopped halfway(rough estimate).
Hmm :/
EDIT: Yes, I've asked on other forums, and they have been saying to flash(it's called taht right?) But since I'm new to this stuff, I want to check all possible alternatives first. And if I decide to do this, I'll have to feel fully prepared on what to do, don't want to screw up things even more
To give you at least some hope have a look at this thread:
http://forum.xda-developers.com/google-nexus-5/help/stuck-launching-flashstock-bat-t3244470
If you've never done any flashing before, I recommend that you install Wugfresh's Nexus Root Toolkit. It can be used to flash a new ROM, but I'm becoming more convinced that the people in these forums are right in saying that it's good to try things manually rather than relying on a toolkit. I suggest that you use the toolkit's tutorial to set up your PC with all the right drivers & programs (ADB/Fastboot) so that you're prepared for typing in the commands.
dahawthorne said:
To give you at least some hope have a look at this thread:
http://forum.xda-developers.com/google-nexus-5/help/stuck-launching-flashstock-bat-t3244470
If you've never done any flashing before, I recommend that you install Wugfresh's Nexus Root Toolkit. It can be used to flash a new ROM, but I'm becoming more convinced that the people in these forums are right in saying that it's good to try things manually rather than relying on a toolkit. I suggest that you use the toolkit's tutorial to set up your PC with all the right drivers & programs (ADB/Fastboot) so that you're prepared for typing in the commands.
Click to expand...
Click to collapse
Thanks, I'll have a look at it.
Just to be sure. A factory reset wont work, right?
I don't know - I suppose it's worth trying. But if the phone doesn't turn on, you'll have to go through the PC setup anyway so that you can work on the phone. Besides, it will come in very useful when you need to do any maintenance on the phone in future (if that's what you want).
Or is there a factory reset in stock recovery? I don't use it myself, so I don't know.
CoJonees said:
Thanks, I'll have a look at it.
Just to be sure. A factory reset wont work, right?
Click to expand...
Click to collapse
Wug's toolkit needs a fix. It will not load the new Mashmellow either
Want to learn something instead of using a toolkit to do stuff for you?
1) http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
2) http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Both these threads are unavailable, possibly deleted.
Sent from my Nexus 5 using Tapatalk
beekay201 said:
Want to learn something instead of using a toolkit to do stuff for you?
1) http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
2) http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Click to expand...
Click to collapse
@beekay
"Want to learn something instead of using a toolkit to do stuff for you?"
You convinced me, but I think that the NRT has a lot of great help in setting up a PC so that you can actually start learning about ADB/Fastboot manual commands.
Although I'd done some minor fastboot stuff before, I'd never done the full Monty and installed a ROM, but I found the experience strangely pleasurable...
@op found help yet :what::what::what::what:
I spent half yesterday, into the wee hours of the morning trying to get my pixel back to life. Figured I'd post my goof as it may help someone later.
I flashed the aosp build using the android flash tool just out of curiosity. Realizing dual sim did not work on asop without gapps of some sort, I decided to go back to the public builds. That's where things went crashing down, fast and hard. Literally 6 hours trying everything I knew and everything I could find. Tried 3 different computers, multiple different cables, made sure adb and fastboot were updated like 5 times, tried using the flash tool, tried downloading and using flash all, tried erasing everything and starting over, tried lineage, tried side loading via adb, tried fastboot flashing individual images... All failed, flash tool complaining about not enough space, local installs complaining about missing partitions, not valid files, just everything that could go wrong did. The only thing I could successfully get installed was aosp.
The solution? What was preventing it? I use ublock and privacy badger. Disabling those, off to the races, everything went smoothly and I'm back up and running. What puzzled me, how could I used the flash tool to go to aosp but not back? Why, or how was it interfering with a local flash? Maybe things got screwed up somehow and that was messing with the local flash...idk but if you're in my position try disabling those and give it a whirl.
Which flash tool are you talking about? Everything you're doing sounds overly complicated.
I recommend sticking with cmd for windows, and terminals in linux .
noidea24 said:
Which flash tool are you talking about? Everything you're doing sounds overly complicated.
I recommend sticking with cmd for windows, and terminals in linux .
Click to expand...
Click to collapse
I tried that, I tried using the flash all bat for windows and then I tried flashing individual images via adb. Nothing worked. I have no clue why the local installations kept failing unless, as I said something got messed up using the android flash tool via chrome.
Here's the flash tool which I used to load aosp.
I can't understand what problem you were facing:
use newest platform tools
use newest Google USB drivers
use firmware image of google developers page
reboot into fastboot (by volDown + Power or via adb)
flash-all
working smooth like butter if you can read
hanni2301 said:
I can't understand what problem you were facing:
use newest platform tools
use newest Google USB drivers
use firmware image of google developers page
reboot into fastboot (by volDown + Power or via adb)
flash-all
working smooth like butter if you can read
Click to expand...
Click to collapse
I'm guessing you can't read, I did all that. I'm simply posting this in case someone else runs into the same issue I did. As I said, I'm not sure if trying the aosp build changed anything or any of my numerous attempts fouled something. The only way back was disabling ublock and privacy badger and using the flash tool. For clarification, I've been doing this since the very first android, the T-Mobile G1 and am not new to this game.
You were right, I didn't read carefully enough, or to call it by it's name, I misunderstood your posts. The title of your thread lets believe that you have trouble returning to stock and you need help on that.
That something goofy kicked you out of routine I didn't read (was reading from newest to oldest post, so tbh, that was not clever)
I'm also not new to this, so let us stay calm. Nice that you share your experiences.
I would suggest to change the title in: 'try this if you have trouble with returning to stock' I r something similar.
Have a good time!
hanni2301 said:
You were right, I didn't read carefully enough, or to call it by it's name, I misunderstood your posts. The title of your thread lets believe that you have trouble returning to stock and you need help on that.
That something goofy kicked you out of routine I didn't read (was reading from newest to oldest post, so tbh, that was not clever)
I'm also not new to this, so let us stay calm. Nice that you share your experiences.
I would suggest to change the title in: 'try this if you have trouble with returning to stock' I r something similar.
Have a good time!
Click to expand...
Click to collapse
No problem. I'm still at a loss as to what went wrong but needless to say, for myself, I won't be trying AOSP via the flash tool again.
Little late on this, but I was in a rut as well then realized I had adblockers on which caused issue with the flash tool.
Easiest way to get back to stock is by using Android Flash Tool https://flash.android.com/back-to-public