Related
Since the information for this device is so fragmented, I decided to attempt to keep it all in one (or a series of) posts. I aim to link to the original posts as well as outline what do to with your device from the time it leaves to box to running the latest and greatest modified rom or CM9 or whatever else is out there. I will not link directly to anything, rather I will link to the thread, and I very seriously recommend reading at least the post, if not the thread, before you begin ANYTHING.
This guide is a work in progress, it is not complete, and I will work on it bit by bit until it's completed!
Section 1: So its shiny and new...how can I MOD IT?
This will be assuming the new shiny toy in question is indeed an Acer Iconia Tab A100, this is not meant to cover any other devices. And, this is assuming it's coming with Honeycomb installed, in stock form. If its used, or comes with ICS, the next section will amuse you.
First thing most users that want to mod their devices do is root their device. Now, rooting is not unlocking, as carrier unlocking is not boot loader unlocking. Rooting a device allows you to access the system in a much more in depth manner, including read/write (R/W) access to the /system partition, among other things. It allows use of programs such as Titanium Backup (TB or TiBu) ROM Toolbox, overclocking or other clock setting utilities such as SetCPU or CPU Master for overclocking (if the kernel supports it) underclocking and undervolting.
So...how do I do that rooting thing? Well assuming you are running Honeycomb and are wanting to update to ICS plus root and unlock the bootloader, we will use the info from this thread Simple Root Method by ZeroNull to update you to ICS and then gain Root access on that new ICS install!
What about rooting Honeycomb? Well most users are already running ICS and prefer it, and those on Honeycomb are likely wanting to update to ICS, so I will leave this out for now. If I have the time I will come back and include the link for that as well.
Now, ICS is installed, and you're rooted, what else can I do? Well you can unlock your bootloader, and load up a custom recovery such as CWM or TWRP and using those, install Custom ROMS! For this, we visit this thread here Install unlocked bootloader by ZeroNull. Follow ALL directions in this thread for a fully unlocked bootloader!
Custom recoveries, what are they and how do I get that shiz? Custom recoveries, CWM and TWRP, allow the user to flash anything they want, provided its for their device and properly packaged. This included custom roms, some tools, and allows you to "wipe" various parts of the device's storage and backup/restore to a previous installation. Powerful, and dangerous, do not go pushing buttons to things you do NOT understand! Also, you MUST delete or rename /system/etc/install-recovery.sh prior to flashing recovery! This will restore stock recovery every time android boots, wiping out your custom recovery. The only time you want that file there is if you are using the crossix mount swap mod, which replaces that file with a modified version that leaves recovery alone.
Safe to do wipe:
Wipe cache, data, dalvik cache, system. Theonew also reports Flex and boot can be wiped as well as SD-EXT. This is not to be confused with External SD, this is a separate partition on your External SD card, wiping it will NOT wipe external SD, only what's installed on that partition, the rest is safe and requires a separate wipe.
If you wipe system you MUST install a new rom or restore from backup!
If you wipe boot please restore or install a new ROM before rebooting! Safety first.
Not safe to wipe:
Don't wipe anything else, and always install a new rom or backup after wiping system!
Never reboot system after wiping without first restoring or installing a new ROM!
Post 2 will cover custom recovery functions in more detail, for both recoveries.
Now that you have an unlocked bootloader, what can I do? Install that custom recovery! There is two flavors, CWM and TWRP, CWM available here CWM Recovery by ptesmoke. Follow the instructions in this post to the letter! Only attempt this after you have ICS, rooted, and unlocked the boot loader correctly! Next we have TWRP Recovery here TWRP Recovery by ZeroNull. Again, follow the instructions to the letter, and attempt only after ICS, root and unlocked boot loader are finished.
Ok, gots me some custom recoveries, what about custom roms? This is why we just did all that work, to prepare for this! Custom ROMs! I'll be listing some (all?) ROMs that you can use, besides stock HC and ICS.
The list in order of version, oldest to newest, updated to retired:
4.0.3
KEBBERSROM by Hardslog Stock based 4.0.3
Flex Reaper by civato ICS 4.0.3 Modified Stock
Green ICS by lgcmn & ZeroNull ICS 4.0.3 Modified Stock
4.0.4
KEBBERSROM SHELLSHOCK by Hardslog 4.0.4, based on A500 and A700 ROMs
Nightly Builds of CM9 by pio_masaki ICS 4.0.4
Aoikaze Modified CM9 by pio_masaki ICS 4.0.4
4.1.1
CM10 Preview builds by waydownsouth 4.1.1
4.1.2
Unofficial CM10 builds by pio_masaki (stock and modded, Phone UI and Tablet UI)
Jellytime Sosei by pio_masaki Jellybean 4.1.2
Cyanosaki_Flex by Hardslog
4.2.2
CarbonROM JB 4.2.2 Unofficial by pio_masaki
These are most of the ROMs. There are others that seem to no longer be in active development and are based on the old leaks that vache was kind enough to grab for us. Development is currently only active in the KEBBERSROM builds by Hardslog, and occasional updated in the CM10 builds by pio_masaki.
That ends Section 1, preparing for awesomeness, and Post 2 will continue with installing your new custom ROM!
Section 2: Recoveries and what they can do for you.
This section will cover recoveries and what they can do, and how to do it. I will be starting with TWRP, as I use that on all of my devices, and after that I will include a CWM section, as a lot, if not most, use that. They are similar in what they do, but different in where things are.
TWRP Recovery
Official TWRP for A100 by linuxsociety
This assumes you have already done everything in section 1, including installed ICS, rooted it, unlocked your bootloader, and installed TWRP custom recovery. Links for this information is provided in Section 1, in the post above.
First thing you should ALWAYS do when you enter recovery, before doing ANYTHING ELSE, is make a nandroid backup!
Getting into recovery: Depending on what ROM you use, this is done a couple ways. First is an AOSP ROM, like CM9/AOKP, which you can hold the power button, then select Reboot, then Recovery. In modified stock or rooted stock ROMs, this menu doesn't exist, you can either use an app like Quick Boot, and select recovery, or power off, then hold the Volume - key (closest to the rotation lock switch) and while holding it, hold power, once the acer screen comes up and starts saying Recovery kernel, release both and recovery will boot provided an update.zip is NOT on the root of your external SD card. This method works for any ROM.
Now I'm in recovery, what do I do? As I mentioned, make a nandroid backup before you do ANYTHING else! From the first screen (home screen) in TWRP select Mount. In mount you can leave everything alone and at the bottom will be two options with Circles. Select Using external SD Card for Backup. This will store your backup on your external SD card, never use internal SD if possible. After you select use external SD, press the Home button in the upper right corner. Now, back on the Home screen, select Backup. Double check the boxes checked are System, Data, Boot and Recovery. At the bottom is a nice little slide bar, slide that over and sit back. Takes about 4-5 minutes depending on how full your device storage is. This does NOT backup internal SD! After this is done, you have created a nandroid backup that when restored will put the system exactly how it was last time you used it. You can make multiple backups of multiple ROMs without issue, just however big your SD card is to hold them.
The restore menu, or the OOPS SAVE MEH menu is your best friend. This will restore you back to the last state your device was in for the backup that is restored. By default TWRP saves by date and time, however you can rename this with any file manager, never caused me any issues. Theonew reminded me of an MD5 issue that can happen on renaming backups, if this does happen, rename it back to the stock naming system to fix it. Generally I'll just append the ROM name to the front, so instead of 2012-6-14--18-25-01 it'll be CM9-2012-6-14--18-25-01. Make sense? That way to restore it in case of error, just drop the name. Easy. Theonew also did some testing, and confirmed that spaces in the folder name WILL cause MD5 errors and fail the restore, please use ONLY dashes and underscores (- and _ lol) in the folder name! To restore make sure you are on the Home screen, then select Restore. In the window you will see a list of your current backups, select one. Next screen has check boxes, make sure System, Data, Boot and Recovery are checked, then slide the bar to begin. This takes a bit, make sure you let it finish! Once done, your system will be at the last point it was used for that backup.
Advanced restore...I'm to lazy to reload and reset up my stuff after a ROM flash, so this is the fast and dirty way of doing it. If you flash a ROM and you don't feel like manually restoring your apps, you can uncheck System, Recovery and Boot, and leave only Data checked. This will restore your user installed apps and settings over the current ROM install. I don't recommend this for different ROMs, only for updates of the same ROM! Up to you but if you get alot of issues, you'll know why. After advanced restoring, go to the Home Screen and select Advanced, then Fix Permissions. Press Home again and select Wipe. Wipe Cache and Dalvik Cache, then reboot system.
Alright, enough already lets get our flash on! From the Home screen, select Wipe, then press on Cache, Dalvik Cache, Factory Reset, and System. Optional you can wipe Battery Stats if your battery seems off. Leave the rest alone. Once these are all wiped, go back to the Home screen, and press Install. The window on the left is your device folders, window on the right is contents of the current folder. I hope you remembered where your rom.zip is, because you select it here. Press on the zip for the ROM of your choice, then slide the bar to flash it. After that is done, select the left button Wipe Cache and Dalvik, then select Reboot system.
OK LETS ROCK THAT ROM! Woah, slow down scooter, there's a few things to do, or not do, first. After it boots, meaning it's past the boot animation and is sitting on the Welcome screen, set it down and leave it alone for 10 minutes or longer. Don't sign in, don't do anything, just leave it be for 10 minutes. If you can't think of what to do to manage the time you have to wait for awesomness of custom ROMs, read the thread of the ROM you chose. Set the thread for 50 posts and just read. After 10 minutes, hold the power key, and either choose Power off or Reboot, Reboot depending on ROM used. After it finishes rebooting (that was alot faster wasn't it?) you can go ahead and do the Welcome stuff, log in to Google, setup your device, download your apps, restore your apps etc. After restoring your apps (try not to restore app + data if possible, though I know games and stuff you'll want to) reboot one more time. After that second reboot, use the tablet as normal. From my experience this offers the BEST possible ROM usage, a vast reduction in lag, bugs, and oddness.
What else can I do with the TWRP Recovery? Well, the most useful tools are Backup, Restore (and advanced restore) and the wipe menu, plus fix permissions. Those generally can fix anything thats wrong. If you notice alot of lagging, FCs or general unruliness, wipe Cache, Dalvik Cache, and Fix Permissions. Another useful ability is ADB, which is beyond the scope of this section, but may be included generally in a later section. ADB can be used to repair otherwise bricked devices, and offers a very large amount of tools that you don't normally get to use in Recovery. Keep in mind ADB is powerful, and can quickly destroy your device, so please, be careful using it.
Placeholder for CWM Recovery section - coming soon!
CWM Recovery for A100 by ptesmoke
Section 3
Additional Recovery tools:
Blackhole Wipe/Nullifier by pio_masaki
These are tools I created to make wiping a little easier, but please read the post completely before deciding to use it! There are multiple versions, and they can and will wipe internal SD, as well as take up to 40 minutes to run (1, not all). Please ask questions if you have them there and I will help as best I can!
AROMA Recovery Touch Recovery
A touch file manger to be used in recovery, even on non touch CWM! Good for renaming backups as soon as you make them (I tend to forget afterwards and get confused by 6 backups with just dates). Also moving a downloaded zip from internal to external or whatever before running a system wipe, any number of things. Please read the post completely before using this tool! It can cause damage if not used properly and with care!
Kernels:
linuxsociety / godmachine's A100 OC Kernel
Plenty of extra balls thrown in for good measure, a good place to look if you like high benchmarks and plenty of extra goodies baked in. Available in a few flavors, with some GPU OC thrown in for good measure.
ezterry's A100 OC/UV Kernel
The only other option for a kernel that we have besides stock and CM9's included kernel. Excellent kernel, really wakes up the A100, allows up to 1.5 GHz for some extra umph and undervolting to help conserve power on our very weak batteries.
PRO TIPS:
The 10 minute rule:
The reason I mention waiting 10 minutes on first boot of a ROM install is this: Alot of things happen the first time the ROM runs, alot of scripts run, the kernel has to settle and search and move things, files are flying all over the nand. Think of a tornado in a cubicle. That's first boot for your device. Allowing it 10 minutes uninterrupted allows all of that to happen and settle down. The following reboot lets all that new info fire up from it's new home and continue settling in. After restoring and downloading apps, that reboot allows that new info to settle into it's new home and the system to catch up. This isn't device specific, rather a general rule of thumb for all devices. Does not really apply to restores unless something is changed.
Undervolting:
Undervolting on this device is only available on ezterry's excellent kernel. The following is a rough guideline of how to do it, and do it right:
Start small, don't just dump it -200 and expect it to work. For the time you're testing, make sure it is NOT set for boot. If something goes wrong you don't want it doing it everytime it boots, right? Go in small increments, -25 is usually OK. For now, don't overclock. Starting at 1 Ghz, lower every speed range down -25, and run the device for at least 10-20 minutes, normal use, hard use, benchmark, browse the web, watch a HD movie. If all is fine and its not lagging, freezing, force closing or heating up more then usual, move everything to -50, and repeat. My device freezes at -150 but runs stable at -145. Every device and chip is different, mine may do -145 yours may do -175 or only -50.
Overclocking
Overclocking is available on ezterry's bodacious (already used excellent) kernel, up to 1.5 GHz, and the CM9 kernel up to 1.4GHz. As with undervolting, this should be done in small steps and tested between to find your max. Generally 1.5 GHz is fine for every device, however all devices and chips are slightly different, and some may not be stable at it. Mixing undervolting and overclocking can be tricky, but following the steps above for undervolting you can find that sweet spot for your device.
Batteries and why they fail
This section is entirely my opinion, other's swear one way, other's another, but this is what I've concluded from multiple posts for this device.
Consider 10% to be 0%. There have been more then a couple posts that say they let their battery fall below 10% and they can NOT get the device to work properly again afterwards. I think there's a few reasons for this, and I'll explain them now. First, a lot of batteries tend to have some kind of breaker protection if the voltage drops below a certain level. This is to prevent damage to the cells, which it does, however we can't close that breaker to restore activity from the battery, IE, it's dead anyways. This threshold varies from one device to another, one battery pack to another, some can go to 0% and be ok, others can't. I say voltage level, because while draining the voltage can spike up, and it can also spike down, which can fall below this threshold even though it says you have 5% battery life remaining, and trigger the protection.
The acer does not seem to power on without a working battery. If the battery is "dead" it doesn't seem to boot. Its basically a brick until either the battery is replaced (by acer I would assume) or the motherboard is replaced due to some sort of damage causing this. Replacing the motherboard costs almost as much as a new unit, so at this point, just save up some more and buy a new one.
For this, I never go below 10% if ever possible. Even on my phones.
Another thing I try not to do is charge in bursts, or at random times. Basically, I plug in at 10%, then allow full charge to 100%, I don't charge in between those ranges, and I don't charge for periods less then 100%. So I don't plug in at 48% then unplug at 60%. I've learned this one from my Evo 4g, the battery was fantastic for months, then I started using the car charger to top off, and the battery life over the course of 2 weeks took a very noticable hit on overall life. I lost easily 4 hours a day usage on it. This on a phone and ROM combo that got me 16 hours a day.
Again this entire section is just what I've noticed and is purely my opinion, please do whatever you please with your device, it is yours after all!
ADB and Fastboot...is it really a faster boot?
No, fastboot isn't a toggle to boot at warp 9. Fastboot is a mode you can put your bootloader into for flashing the system for upgrades, repairs, mods, or general havok if you're not careful. The bootloader is what you see when you first turn on your device, that lovely Acer logo with the text up in the left corner (usually saying bootloader version and Unlocked Mode if unlocked, or nothing if it's locked). If you go into fasboot, it will say download usb protocol, so if you see that, you're in fastboot mode for whatever reason.
How do I get into fastboot mode?
Well you can do this in a couple ways, either Quickboot app (reboot bootloader), if you're on CM9, the power menu will give the option, or you can use ADB for it.
adb reboot bootloader
I'll explain some more about adb after fastboot, I know its odd, but one does have something to do with the other at times.
Once you've rebooted to the bootloader (device will turn off, vibrate, then boot to acer screen) you can then issue your fastboot commands assuming 2 things:
Acer USB drivers are installed and working correctly (if you use adb to reboot, then it is)
Your tablet is connected to your PC over USB.
Now, at this point, its up to you to do whatever you want, but BE CAREFUL USING FASTBOOT FLASH! It doesn't care or check what you're flashing, it'll just flash it. For example, I flashed CWM Touch recovery to boot once because I was distracted and mixed up the images for whatever reason. End result: Can't boot android. Why? Because boot was recovery, it only booted to CWM Touch recovery. Booting to actual recovery booted to TWRP, which was my previously installed recovery. I got it back easy enough once I figured out what I did wrong, but not all mistakes are reversible, or fixable!
General Fastboot uses and commands...
general layout goes like this:
fastboot (this is calling the command) flash (this is what fastboot will do) recovery (where it will send it to) recovery.img (the file it will send)
So, it looks like this:
fastboot flash recovery recovery.img
it will then flash whatever img to whatever partition you said, and let you know when it's done. You can flash any img to any partition, provided it fits, which means you do have to be careful about what you flash to where!
when you are finished with fastboot:
fastboot reboot
There are plenty of other commands, but the general basic use of fastboot is to flash a recovery or bootloader, so that is what I laid out above.
This section is hugely in need of improving, I know, but the guide in general is still rough, my apologies.
What about ADB?
ADB, or Android Debugging Bridge, can be used in System or in custom recoveries to interact with the device behind the curtain, meaning what you do isn't readily apparent on the device itself, unless you do something obvious like reboot it. ADB has a ton of commands, in particular in ADB Shell mode (you drop into the device shell itself, issuing commands from within itself, not from the PC).
Some random ADB commands:
adb reboot (where to reboot to) so:
adb reboot recovery
adb pull (what file to copy) /(where to copy file to) so for example, a recovery log to the adb working folder:
adb pull /cache/recovery/last_log recovery.txt
adb push /(file to copy to) /(file to send to device) so for example, placing that recovery file back into the device:
adb push recovery.txt /cache/recovery/last_log
Thats all the time I have for now, sorry in advance, I'm still working on all of this, I swear lol
Placeholder for additional tips and usage, some ADB stuff, and anything else I can think of.
Placeholder for Toubleshooting.
Placeholder for FAQS.
System Modding
justjackyl's Iconia A100 CM10 Setup & Use Tips/Tricks
A good guide to check out to try to get the most out of your A100 on CM10 (or any JB ROM like Sosei/black bean). A must read for those new to CM10/JB on these devices or in general. Not an outright mod, but a good source of information about some modding you should browse.
Hulu Flash Hack by NoSudo
What the Hulu Flash Hack by NoSudo does is allow you to use our android browser (setup according to the thread) to watch sites like Hulu to play on your android flash player. Its basic function is to scan for, then backup, then place a modified libflashplayer.so file. Setup with script manager and run at boot for best results. As always, read the thread for more information.
Mount Swap by crossix
What the Mount Swap by crossix does is pretty awesome, it mounts your external SD as internal, meaning your 32GB external SD card shows as internal, and is used for your apps, data, downloads, whatever, as if it was your internal SD. Internal SD is then mounted as external SD. It's operation is based on install-recovery being replaced with crossix's version. Instead of replacing recovery, it runs the mount swap. Requires Root, as the file is placed into /system/etc. Designed for stock/modified stock ROMs, it can be used with AOSP/AOKP ROMs by using script manager and setting it to run as Root at Boot. Please read the thread for the files and information on how to use it.
Adapted to ICS Build Prop Mods by patrick_spd4u adapted from crossix
What the Build Prop mods do is pretty basic, however can greatly increase the abilities of the A100, including faster boot times, more apps/games available for download in the Play Store, and tons of other stuff. Adapted from crossix's mods for HC.
Guide to 2 ways of running the crossix mount swap script, Acer based and AOSP/AOKP based
Direct paste from a post I made about this earlier...details using ES File Manager, however you can adapt it for any root file manager.
Using your tab, download the crossix mod zip file.
Unzip the file to get your epic mount swap mod by crossix, it can be unzipped anywhere.
At this point, I'm using ES File Manager but you can use Root Explorer or whatever. I'll be giving directions for ES.
Go into settings, scroll down and check the box for Up to Root.
Scroll a little futher down, same menu, and check the box for Root Explorer. Tap Yes, then allow when SU asks.
Now check the box next to Mount File System.
A little notice should pop up saying system is writable. If it fails at this point, you'll need to reroot, though it should work fine.
Press back, and go to where your crossix install-recovery.sh file is, hold your finger on it, and select Copy from the menu.
Press back and keep pressing it until you get to /. You'll see folders like acct, cache, config, d, etc.
Scroll down to system, and tap on it to go into system
Tap on etc to enter the etc directory.
You should now be in /system/etc, check up top there will be the address bar showing where you are.
You shouldn't have an install-recovery.sh file there, but if you do, long press it and select rename, then rename it install-recovery.bak.
On the upper buttons, select paste.
Now hold on the install-recovery.sh and select Properties, all the way at the bottom of that menu.
Next to where it says permissions, click Change
You will get a new window showing 3 rows of 3 colums of boxes with Xs.
Check the boxes so it looks like this:
XXX
XXX
XXO
Click on OK, then OK again, you should be back to the main ES window. Go ahead and hit home, or hit back over and over to exit.
Stock or Modified stock ONLY
Reboot the device by whatever method you prefer.
Once it finishes booting, wait a minute, then check your Settings>storage and your external SD card should show as internal. You only need to do this 1 time, it will continue to do this after.
AOSP/CM9/AOKP ONLY
Go to the Play store and download Script Manager(smanager).
After it installs, open the app then select Browse as root, Allow when SU asks, then click OK.
It will likely be listing /mnt/sdcard as your default directory, press the folder with .. to go back up until it says /
Click on system, then etc
It should now show /system/etc
Find your install-recovery.sh file, and it will open a new window.
Pay close attention here!
Right under the buttons that say Run Exit Edit Save are some icons,
Fav Su Boot Net Wick Ntfy
Press on Su and Boot, then click on Save.
Now exit smanager and reboot.
Wait a minute, then check settings>storage and your external SD should show up as Internal.
Don't disable smanager from running at boot! If you disable it, your script won't run. smanager must remain installed, or the script won't run.
Thanks to:
ZeroNull: For being one of the pioneers for getting our devices cracked open for our amusement!
ptesmoke: Also for being a pioneer in getting custom recoveries on our devices!
vache: For releasing the ICS leaks way ahead of schedule and hosting them for us to use and abuse!
civato: For releasing his Flex Reaper ROMs on our devices, his modified stock ROMs are still (IMO) the slickest available!
da-pharoah: For helping me understand how recoveries work a little better, allowing me to create Blackhole Wipe/Nullifier, and general encouragement for creating things for this device! (G2x and KF forums)
ezterry: For creating an OC/UV kernel that so far is the best EVER for any ROM on our device!
Theonew: reading ALL of that, and providing some nice info I missed and left out, and catching typos (Almost made it...)
crossix: that mount swap mod is just awesome, I never run a ROM without it!
NoSudo: creating a method to easily modify the system to watch HULU and other sites that normally won't allow it!
There's more I'm forgetting, I'll be adding more as I remember, I promise.
Even though I knew everything you posted, it was very interesting and I recommend everyone (even if you don't need it or already know) to read this guide. Its a marvellous read with some humor to keep you going. One thing though:
- You stated that its only safe to wipe "cache, dalvik cache, data, and system". Technically, this is not true. Flexrom and boot partitions are also safe to wipe (and for some roms for certain devices, the boot partition must be wiped for stable kernel performance, etc.). It's also a good idea to wipe sd-ext if you have it set up (in most cases). Once again, excellent guide (you even did a part of my job ).
Theonew said:
Even though I knew everything you posted, this is a brilliant guide and I recommend everyone (even if you don't need it or already know) to read this guide. Its a marvellous read with some humor to keep you going. One thing though:
- You stated that its only safe to wipe "cache, dalvik cache, data, and system". Technically, this is not true. Flexrom and boot partitions are also safe to wipe (and for some roms for certain devices, the boot partition must be wiped for stable kernel performance, etc.). It's also a good idea to wipe sd-ext if you have it set up (in most cases). Once again, excellent guide (you even did a part of my job ).
Click to expand...
Click to collapse
While sd-ext is safe to wipe, using factory reset wipes that for you, and I think, could be wrong, but cwm does it on data wipes. Part of why I missed it was I confused it with my phone, where wiping sd-ext bricks the phone, and also people mix it up with external SD. I'll add it in as its a very valid point, and I shouldn't let personal things interfere with the guide.
As for boot, our devices don't need that wiped and honestly asks for problems if someone doesn't restore or install a rom to cover it. I've never wiped it on any device, however I will also add that in as it is good info. I left it out of "safe" to prevent possible issues from wiping it.
I forgot about flex and I honestly don't know what it is for lol. Again thanks for reminding me and I'll add it in.
Of course I'm open to posts like these please give some input on what I missed or need to correct, I want this to be the go to guide for the a100 for anything needed!
Tapatalked from my Galaxy S II.
pio_masaki said:
I forgot about flex and I honestly don't know what it is for lol....Of course I'm open to posts like these please give some input on what I missed or need to correct, I want this to be the go to guide for the a100 for anything needed!
Click to expand...
Click to collapse
In your 4th to last sentence of the "Advanced Restore" section, you have a typo . Anyways, according to here: forum.tegraowners.com/viewtopic.php?f=10&t=149, Flexrom is "a partition on the nand that acer made to hold some proprietary apks and build information".
Oh damn almost made it without a typo...not bad for just running through all of that without really checking on it..other then it was english.
Corrections and additions added to the posts, thanks!
pio_masaki said:
Oh damn almost made it without a typo...not bad for just running through all of that without really checking on it..other then it was english.
Corrections and additions added to the posts, thanks!
Click to expand...
Click to collapse
One more thing - This occurred for one of my other devices, but the problem may still exist here. I haven't tried it with TWRP, but renaming CWM backups can cause a md5 mismatch error to occur. If this happens, simply rename it back to a date (in the default format).
I've never ran into that issue on any of my devices in CWM or TWRP, however I have heard of it occuring, definatly something I should add in there. Full of good catches tonight aren't you?
Awesome write up, thanks you guys!!
What about Zeronull's .014 v1.2 rom? http://forum.xda-developers.com/showthread.php?t=1574897
I'm still digging through all the threads for the ROMs, however I included the currently developed or recently released ROMs first, ZN has since released Green ICS, which is included already. I do plan to list every ROM, but it'll take some time to finish this guide up with as much info as possible, then go back and add things in.
pio_masaki said:
I've never ran into that issue on any of my devices in CWM or TWRP, however I have heard of it occuring, definatly something I should add in there. Full of good catches tonight aren't you?
Click to expand...
Click to collapse
I tested it to see if it occurs, and it turns out that it does. I made a backup with CWM, renamed it then tried to restore, and it immediately gave me the "md5 mismatch" error.
Theonew said:
I tested it to see if it occurs, and it turns out that it does. I made a backup with CWM, renamed it then tried to restore, and it immediately gave me the "md5 mismatch" error.
Click to expand...
Click to collapse
That is so weird I never have that issue cwm or twrp. I use es file manager..maybe why?
Tapatalked from my Galaxy S II.
pio_masaki said:
That is so weird I never have that issue cwm or twrp. I use es file manager..maybe why?
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
I renamed it using Root Explorer. Have you tried renaming them to something including spaces?
Theonew said:
I renamed it using Root Explorer. Have you tried renaming them to something including spaces?
Click to expand...
Click to collapse
No, as its a Linux based environment I use dashes and underscores never spaces in directory names. That shouldn't cause md5 fails because the md5 is based per zip not the folder name. If you could try an experiment and rename with es I'd appreciate it, and maybe with and without spaces. I'll try root explorer when I get home and see if it causes issues.
Tapatalked from my Galaxy S II.
pio_masaki said:
No, as its a Linux based environment I use dashes and underscores never spaces in directory names. That shouldn't cause md5 fails because the md5 is based per zip not the folder name. If you could try an experiment and rename with es I'd appreciate it, and maybe with and without spaces. I'll try root explorer when I get home and see if it causes issues.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
Done. The error seems to only occur when spaces are used in the name.
Theonew said:
Done. The error seems to only occur when spaces are used in the name.
Click to expand...
Click to collapse
Thanks for taking the time to figure that one out, I've been testing a new rom on my phone plus a new test T20 kernel for ezterry and getting cm9 build 5 up, just kinda managed to forget that experiment lol
I'll have some time...maybe...to append that new bit into that section tonight. The "free" time has been spent trying to get aokp for the a100 but my lack of experience, random problems with the repos and devs ignoring my PMs its been going slow. And by slow I mean nowhere.
Tapatalked from my Galaxy S II.
Great read. Sorta like flashing for dummies. Thaanks for your work.
Sent from my HTC Glacier using Tapatalk
It's great to have all this information compiled in one location. Looking forward to your next installment. THX
Last week I brought a Morotola Xoom on ebay, it had 4.0 installed but I wasn't that impressed with it having got used to stock 4.1 on my phone.
I came across the great guide at http://forum.xda-developers.com/showthread.php?t=1477024 and used this along with http://wiki.cyanogenmod.org/w/Install_CM_for_wingray to unlock, root and install cyanogenmod 10.1 on it.
It was mostly a stress free install (although I managed to miss renaming the stock files that the post says causes Stock Recovery to overwrite CWM but it seems to still work OK.
My issue now is that I don't seem to have all the Google apps. It has gmail but not maps or market. I assumed that gmail isn't part of cyanogenmod so the 'gapps-jb-20130812-signed' file has installed (I think that file is the correct version).
It's not too clear from the instructions they read to me that you install the main CM zip and then Google apps without needing to re-boot in between, is this correct? I've tried a completely fresh install and also wiping the cache partition but no luck. But have not tried re-booting after installing the CM then installing Google Apps in a second boot, worth a try I guess.
Am I just making a simple noob error here? Thanks in advance for any advice.
A update, I've just tried formatting and re-installing again, only this time allowing a reboot into android prior to trying to install Google apps. One thing I've learnt is that the gmail app is part of the base install. Installing google apps appears to go ok but upon rebooting they aren't there. My next test is to try yet another clean install and an old version of gapps (gapps-jb-20120719-signed).
Chris
Motorola Xoom issues with 'Motorola fast-boot' replacing 'clockwork-recovery'
A further update... It's not gone well, it'd defaulted back to Motorola fast-boot protocol support not clockwork-recovery (after me initially forgetting to rename the files even though it's worked for many re-boots until now).
I've then tried to run back through the guidance at http://forum.xda-developers.com/showthread.php?t=1477024 to re-unlock and re-install clockwork-recovery.
However, it's not gone great, for a start it took me a while to work out to turn on usb debugging in Cyanogenmod 10.1 (see http://wiki.cyanogenmod.org/w/Doc:_developer_options) so adb can see it. After a couple of hours of messing about I've managed to get clockwork-recovery back on it.
However when booted into clockwork-recovery I got a 'error: device not found' from 'adb remount'. So I was not able to rename the files to prevent the Motorola fast-boot overwrite of clockwork-recovery eventually happening. When android is booted and it isn't in recovery I get a 'remount failed: Operation not permitted' response to adb remount. Is there another way to rename '/system/recovery-from-boot.p' and '/system/etc/install-recovery.sh' without having to do it do it at that first boot, it is interesting that clockwork-recovery survived several boots.
I've decided not to risk the install of a potentially unsupported zip of Google apps when my recovery situation isn't solid.
Hmm a fun morning, I've lost times now at how many times I've had to reroot it. I've managed to get the Google play store apk and have tried using that (in addition to installing the gapps zip) it is loading but complaining of no network connection.
With regard to renaming the files ' /system/recovery-from-boot.p' and 'system/etc/install-recovery.sh' I've not managed this, when the tablet reboots into clockwork recordery its connection with adb is dropped. I've also tried doing them in terminal when booted and they don't seem to be there.
There doesn't seem to be anyone else commenting on this so I'll just plod along blindly :silly:
c_dunne said:
A further update... It's not gone well, it'd defaulted back to Motorola fast-boot protocol support not clockwork-recovery (after me initially forgetting to rename the files even though it's worked for many re-boots until now).
I've then tried to run back through the guidance at http://forum.xda-developers.com/showthread.php?t=1477024 to re-unlock and re-install clockwork-recovery.
However, it's not gone great, for a start it took me a while to work out to turn on usb debugging in Cyanogenmod 10.1 (see http://wiki.cyanogenmod.org/w/Doc:_developer_options) so adb can see it. After a couple of hours of messing about I've managed to get clockwork-recovery back on it.
However when booted into clockwork-recovery I got a 'error: device not found' from 'adb remount'. So I was not able to rename the files to prevent the Motorola fast-boot overwrite of clockwork-recovery eventually happening. When android is booted and it isn't in recovery I get a 'remount failed: Operation not permitted' response to adb remount. Is there another way to rename '/system/recovery-from-boot.p' and '/system/etc/install-recovery.sh' without having to do it do it at that first boot, it is interesting that clockwork-recovery survived several boots.
I've decided not to risk the install of a potentially unsupported zip of Google apps when my recovery situation isn't solid.
Click to expand...
Click to collapse
Well, I'm with this problem too. I'm trying to solve this problem by myself, but no success at all. It do FC on google play every time it try to update. Every Google App (besides GMail) is doing FC with this CM build.
I tried to:
- Reinstall google apps
- Install another version (compatible with Android 4.2.2)
- Do the wipes again
- Install google play from an outside source (it doen't come with it).
But no success.
Any ideas?
miraidensetsu sorry for my delay in responding, I'm surprised that no other responses to this tread have been made. An update I've now resorted back to the stable release cm-10.0.0. Given it's nearly a year old I'd hope there'll be a stable release of 4.2 out soon.
Initially I had issues with the stock keyboard crashing all the time. But after searching about this I've installed the Google keyboard app and disabled the stock one.
Q&A for [ROM]TN.kitkat.4.4.2.HTC.evo.supersonic(aosp)viper.mod. a2sd_updated4/26/14
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
I'm running supersonic, hboot 6.16 with S-OFF. Have TWRP 2.8 Installed and flashed the TN kitkat rom and gapps core together but play store and the other Gapps do not show up. Someone suggested that using TWRP 2.7.0.0 worked for them, however, flashing 2.7.0.0 through bootloader gives a Fail-PU Update Fail and trying to flash it via fastboot also fails. So far, 2.7.0.0 is the only version of TWRP that fails to install. Any suggestions for getting gapps to work on this rom? I've tried flashing several other kk gapp packs, but they all fail with a message about not being able to run the update script in the zip file.
paultyler82 said:
I'm running supersonic, hboot 6.16 with S-OFF. Have TWRP 2.8 Installed and flashed the TN kitkat rom and gapps core together but play store and the other Gapps do not show up. Someone suggested that using TWRP 2.7.0.0 worked for them, however, flashing 2.7.0.0 through bootloader gives a Fail-PU Update Fail and trying to flash it via fastboot also fails. So far, 2.7.0.0 is the only version of TWRP that fails to install. Any suggestions for getting gapps to work on this rom? I've tried flashing several other kk gapp packs, but they all fail with a message about not being able to run the update script in the zip file.
Click to expand...
Click to collapse
TWRP 2.8 is probably fine - the GApps packages are likely just too large and the flash is failing because your system partition is full.
What do I need to do to get gapps working then? The posted gapps core package doesn't fail on flash like other gapp packs, but the market and other apps never show up.
paultyler82 said:
What do I need to do to get gapps working then? The posted gapps core package doesn't fail on flash like other gapp packs, but the market and other apps never show up.
Click to expand...
Click to collapse
Have you tried downloading the latest core GApps through the EV Updater in the ROM?
(I assume this ROM has that)
Just tried that, flashed through recovery, EV Update only lets you flash gapps in conjunction with a nightly. Flash seemed to succeed, but no luck. Gapps not appearing, nowhere to enter google account in the UI.
paultyler82 said:
Just tried that, flashed through recovery, EV Update only lets you flash gapps in conjunction with a nightly. Flash seemed to succeed, but no luck. Gapps not appearing, nowhere to enter google account in the UI.
Click to expand...
Click to collapse
Can you use the File Manager in Recovery to navigate to /system/priv-app and look for the Google apps? Maybe try extracting them from the zip and manually copying them and setting permissions? There must be some explanation. I've never had a problem with GApps. Can you try fully wiping (including system) and flash the ROM and core GApps again, just to be sure?
Ok. Wiped and reflashed. Odd thing is, before rebooting, the gapps appear to be in /system, however, on restart, they don't show up and when browsing to /system in ES File Explorer, the gapps have disappeared. I have never seen anything like it before, but then, I haven't played with Evos much.
paultyler82 said:
Ok. Wiped and reflashed. Odd thing is, before rebooting, the gapps appear to be in /system, however, on restart, they don't show up and when browsing to /system in ES File Explorer, the gapps have disappeared. I have never seen anything like it before, but then, I haven't played with Evos much.
Click to expand...
Click to collapse
You are wiping system, right?
Ok, tried a few more times now, let me walk you through what I've done.
First, using TWRP, I go to Wipe>Advanced Wipe and select EVERYTHING except sdcard, do the wipe. No errors.
Next, Install. I've now tried both TN KitKat and gapps together, gapps seperately after KitKat, and gapps seperately before KitKat
Each time the result is the same, new boot into KitKat results in the first run demo and no gapps to be found.
Here is the odd part I've now noticed that makes me think either I'm not doing something right, or TWRP isn't treating system correctly. All references to TWRP's file manager means using Advanced>File Manager.
On a new wipe, TWRP's file manager shows usr and bin directories in /system.
After any of the above methods of flashing, TWRP's file manager shows usr and bin AND everything from the gapps package but nothing from the KitKat package.
After first boot, ES File Explorer shows everything expected from the KitKat package in /system and nothing from gapps.
After first boot, rebooting into TWRP and using it's file manager shows only usr and bin present in /system, none of the KitKat or gapps stuff, yet booting back into the system works fine and ES File Explorer continues to show the KitKat stuff in /system.
Attempting to flash the gapps package in again after first boot gives the same results as above.
Attempting to copy anything into /system via ES File Explorer fails on a Read Only error.
Attempting to copy gapps into /system via TWRP file manager gives the same results as flashing the package.
Some other info that may or may not help... Using the Repair or Change File System tool in the Advanced Wipe menu reports the following for System partition: Mount Point: /system, File System: yaffs2, Present: Yes, Removable: No, Size: 350MB, Used: 317MB, Free: 32MB, Backup Size: 317MB
I appreciate the help, I'm thinking that certainly I've missed something along the way, but I can't figure out what.
paultyler82 said:
Ok, tried a few more times now, let me walk you through what I've done.
First, using TWRP, I go to Wipe>Advanced Wipe and select EVERYTHING except sdcard, do the wipe. No errors.
Next, Install. I've now tried both TN KitKat and gapps together, gapps seperately after KitKat, and gapps seperately before KitKat
Each time the result is the same, new boot into KitKat results in the first run demo and no gapps to be found.
Here is the odd part I've now noticed that makes me think either I'm not doing something right, or TWRP isn't treating system correctly. All references to TWRP's file manager means using Advanced>File Manager.
On a new wipe, TWRP's file manager shows usr and bin directories in /system.
After any of the above methods of flashing, TWRP's file manager shows usr and bin AND everything from the gapps package but nothing from the KitKat package.
After first boot, ES File Explorer shows everything expected from the KitKat package in /system and nothing from gapps.
After first boot, rebooting into TWRP and using it's file manager shows only usr and bin present in /system, none of the KitKat or gapps stuff, yet booting back into the system works fine and ES File Explorer continues to show the KitKat stuff in /system.
Attempting to flash the gapps package in again after first boot gives the same results as above.
Attempting to copy anything into /system via ES File Explorer fails on a Read Only error.
Attempting to copy gapps into /system via TWRP file manager gives the same results as flashing the package.
Some other info that may or may not help... Using the Repair or Change File System tool in the Advanced Wipe menu reports the following for System partition: Mount Point: /system, File System: yaffs2, Present: Yes, Removable: No, Size: 350MB, Used: 317MB, Free: 32MB, Backup Size: 317MB
I appreciate the help, I'm thinking that certainly I've missed something along the way, but I can't figure out what.
Click to expand...
Click to collapse
That's because you have to mount system in TWRP to see the actual contents.
What is the exact GApps package you're flashing?
I tried using both the gapps-core-kk-2013-11-25.zip posted in the OP, as well as gapps-kk442-20131211-core.zip from the EVUpdater.
I think I may have just gotten this to work, Play store is showing up. My solution was to manually mount /dev/block/mtdblock4 to /system via ADB and THEN flash the gapps package. Does TWRP not automatically mount NAND to /system? I didn't see an option anywhere in TWRP to mount partitions, the only thing I saw was the Mount menu item that seemed to be related to USB Media Device mounting, not actually mounting partitions. Did I miss something, for future reference?
paultyler82 said:
I tried using both the gapps-core-kk-2013-11-25.zip posted in the OP, as well as gapps-kk442-20131211-core.zip from the EVUpdater.
I think I may have just gotten this to work, Play store is showing up. My solution was to manually mount /dev/block/mtdblock4 to /system via ADB and THEN flash the gapps package. Does TWRP not automatically mount NAND to /system? I didn't see an option anywhere in TWRP to mount partitions, the only thing I saw was the Mount menu item that seemed to be related to USB Media Device mounting, not actually mounting partitions. Did I miss something, for future reference?
Click to expand...
Click to collapse
In the Mount menu in TWRP, there is a list of partitions and check boxes next to them. If you're not seeing that, then perhaps you have a bad recovery flash.
A recovery log would tell us exactly what's happening when you flash.
Thanks, figured that out now, mount via ADB accomplished the same thing.
Problem solved. The original directions call for both packages to be flashed at the same time, however, at least with TWRP 2.8.0.0, system appears to unmount after KitKat is flashed and gapps is installed to null. On this version of TWRP, you must flash KitKat, then mount system again via the Mount menu or ADB before flashing gapps. It seems that the KitKat package's script causes system to dismount and/or gapps package's script does not properly mount system on it's own.
---------- Post added at 10:18 PM ---------- Previous post was at 10:11 PM ----------
Also, thank you Captain for helping to solve the issue. I was apparently suffering from a serious case of terminal stupidity. It didn't even occur to me to manually mount system until you made the statement about having to mount it.
paultyler82 said:
Thanks, figured that out now, mount via ADB accomplished the same thing.
Problem solved. The original directions call for both packages to be flashed at the same time, however, at least with TWRP 2.8.0.0, system appears to unmount after KitKat is flashed and gapps is installed to null. On this version of TWRP, you must flash KitKat, then mount system again via the Mount menu or ADB before flashing gapps. It seems that the KitKat package's script causes system to dismount and/or gapps package's script does not properly mount system on it's own.
---------- Post added at 10:18 PM ---------- Previous post was at 10:11 PM ----------
Also, thank you Captain for helping to solve the issue. I was apparently suffering from a serious case of terminal stupidity. It didn't even occur to me to manually mount system until you made the statement about having to mount it.
Click to expand...
Click to collapse
Well it's weird that the updater-scripts aren't doing it. Like I said, I've never had an issue with flashing the ROM and GApps in TWRP.
I thought it was a bit weird as well, gonna have a look at the recovery log.
Found it. Gapps update script tries to run /sbin/busybox mount /system. This line fails because busybox isn't there, this failure only shows up in the recovery log, the script messages do not indicate that /system has failed to mount and the update script proceeds to run, installing to null and indicating install was successful.
And then there were two.
I still check in to this forum every day. And as far as I can tell, Vin and Cap are the only reason we are able put our legendary device in our pocket every day and know our rom and recovery are bleeding edge. Lollipop would be huge for our small but dedicated community. But for now the gift of KitKat plus a number of Android 5.0 apps gives me what I like to call "LolliKat". This is the most reliable phone I have ever owned! I hope I get to use it for another four years.
htc supersonic TN 4.4.4 problems
I installed TN 4.4.4 a month or so ago and keep having to reinstall at least once a week. The following problems occur:
Home button softkey quits working, while the menu and back soft keys still work.
Browser is inop, when i click it, it seems like it wants to open because a white screen pops up but then it disappears and goes back to my home screen.
I get no notifications in the status bar for anything.
Calls don't ring, i only know i have missed a call if i check my call history.
Lost theme settings, lost all info i setup on phone. Almost like it reset, except it didn't give me a welcome screen.
I am s-on, but i followed the s-on workaround.
When i hit the home button, catlog shows a keyguard msg, a dropping event because of a non touchable area, and a dalvik VM msg too.
Any ideas or suggestions?
cody85 said:
I installed TN 4.4.4 a month or so ago and keep having to reinstall at least once a week. The following problems occur:
Home button softkey quits working, while the menu and back soft keys still work.
Browser is inop, when i click it, it seems like it wants to open because a white screen pops up but then it disappears and goes back to my home screen.
I get no notifications in the status bar for anything.
Calls don't ring, i only know i have missed a call if i check my call history.
Lost theme settings, lost all info i setup on phone. Almost like it reset, except it didn't give me a welcome screen.
I am s-on, but i followed the s-on workaround.
When i hit the home button, catlog shows a keyguard msg, a dropping event because of a non touchable area, and a dalvik VM msg too.
Any ideas or suggestions?
Click to expand...
Click to collapse
im going to install this today.
---------- Post added at 11:02 PM ---------- Previous post was at 10:59 PM ----------
cryptickid715 said:
im going to install this today.
Click to expand...
Click to collapse
will there be a LP lol
I wanted to install LineageOS.
I followed the tutorial here: https://wiki.lineageos.org/devices/bullhead/install
I completed the folowing steps
Code:
6.) Select Cache, System and Data partitions to be wiped and then Swipe to Wipe.
7.) Go back to return to main menu, then select Install.
8.) Navigate to /sdcard, and select the LineageOS .zip package.
But couln't complete the 8th step becaus I think I don't have the LinageOS zip on my phone, How can I move it there?
How can I send LineageOS install package to my phone so I can install it with TWRP ?
I am using Nexus 5x with Windows 10.
Not to worry
Easy. Just boot up your current ROM and USB, SD Card, Bluetooth, WHATEVER means you have available to move the file to your downloads folder or someplace like that. As long as you can navigate to it, TWRP will let you do that when the time comes. Recommend you put your GApps zip file (I prefer nano) and the appropriate L.O.S. su-addon zip in there as well. After all, what's the use of the ROM if it isn't rooted
Now, fire it up in TWRP and do at least one complete, everything you can include backup of the whole thing before you do ANYTHING else. TWO backups are better if you can move one of them completely off device, as in to a USB stick, etc... The more good backups you have, the less the evil Gods of screwing up installs will try to seek you out. Yes, that has been scientifically proven, even if it sounds like superstitious mumbo-jumbo.
Still good? Wipe dalvik, cache, whatver your build recommends, and flash L.O.S., the su-addon, and GApps all at once. Reboot, be just a little bit patient the first time around, and enjoy. Good Luck.
nezlek said:
Easy. Just boot up your current ROM and USB, SD Card, Bluetooth, WHATEVER means you have available to move the file to your downloads folder or someplace like that. As long as you can navigate to it, TWRP will let you do that when the time comes. Recommend you put your GApps zip file (I prefer nano) and the appropriate L.O.S. su-addon zip in there as well. After all, what's the use of the ROM if it isn't rooted
Now, fire it up in TWRP and do at least one complete, everything you can include backup of the whole thing before you do ANYTHING else. TWO backups are better if you can move one of them completely off device, as in to a USB stick, etc... The more good backups you have, the less the evil Gods of screwing up installs will try to seek you out. Yes, that has been scientifically proven, even if it sounds like superstitious mumbo-jumbo.
Still good? Wipe dalvik, cache, whatver your build recommends, and flash L.O.S., the su-addon, and GApps all at once. Reboot, be just a little bit patient the first time around, and enjoy. Good Luck.
Click to expand...
Click to collapse
Sorry I don't know what you mean exactly. Can you exlain a bit more?
My situation looks like this:
1) I don't need to backup anythig.
2) My problem is that I don't have the lineageOS zip on my phone so I can't install it with TWRP
3) because of step 5,6 on the tutorial I believe I don't have any current ROMS!
step 5,6:
Code:
5) Select Wipe and then Advanced Wipe.
6) Select Cache, System and Data partitions to be wiped and then Swipe to Wipe.
My assumption is that no ROM will load as the current ROM got deleted during step 5&6.
All I get when I start the phone is GOOGLE sign and the lock sign at the bottom.
4) When I go to Reboot inside TWRP and click System I get "No OS Installed! Are you sure you wish to reboot?"
Can you help?
flex567 said:
Sorry I don't know what you mean exactly. Can you exlain a bit more?
My situation looks like this:
1) I don't need to backup anythig.
2) My problem is that I don't have the lineageOS zip on my phone so I can't install it with TWRP
3) because of step 5,6 on the tutorial I believe I don't have any current ROMS!
step 5,6:
Code:
5) Select Wipe and then Advanced Wipe.
6) Select Cache, System and Data partitions to be wiped and then Swipe to Wipe.
My assumption is that no ROM will load as the current ROM got deleted during step 5&6.
All I get when I start the phone is GOOGLE sign and the lock sign at the bottom.
4) When I go to Reboot inside TWRP and click System I get "No OS Installed! Are you sure you wish to reboot?"
Can you help?
Click to expand...
Click to collapse
H'mmm.......... It does appear that you wiped the whole thing, and THAT may make it a bit more of a challenge, but let us try our best. HOPEFULLY your device will recognize the necessary files on a USB stick. You can tell TWRP to MOUNT the USB drive in order to do that if you must, and many devices have no problem and will recognize the device with no added effort, and you just have to navigate to it within TWRP. THAT will be the EASY way, and given what you've described, there isn't anything left on the device to be concerned about with respect to backups, etc... so cross your fingers, and if TWRP can mount and find a USB storage device you just have to flash the three zip files from USB storage as previously described. Otherwise, there is not much I could do personally without the device in hand, although the easiest path forward might be to re-flash a stock ROM and start over again. And please note you would not be the first person reading (or writing) this message to need to do that. Once you get the hang of this, it is not a brutal process, but the first time or two it can be a bit intimidating. Hang in there, the good news is that it is somewhat difficult to totally brick most of these things, so persistence should win out. As long as you can still boot it into TWRP you're fine. Now, one other very important thing. If somehow the bootloader was not unlocked, none of this is going to work at all. SO if that is the case, your only recourse is going to be to get that taken care of first, which requires one of: some finesse with ADB / fastboot, a ROM of some sort (i.e. re-install stock) installed on the device that lets you unlock it by flipping the switch in developer settings , or some other more geeky process that is best supervised by a person who genuinely knows what they are doing and with physical access to the device. There will be no shortage of content out here concerning how-to, but some of the folks writing it are not necessarily technical writers targeting a less experienced audience, even if they are in many cases quite brilliant programmers.
nezlek said:
H'mmm.......... It does appear that you wiped the whole thing, and THAT may make it a bit more of a challenge, but let us try our best. HOPEFULLY your device will recognize the necessary files on a USB stick. You can tell TWRP to MOUNT the USB drive in order to do that if you must, and many devices have no problem and will recognize the device with no added effort, and you just have to navigate to it within TWRP. THAT will be the EASY way, and given what you've described, there isn't anything left on the device to be concerned about with respect to backups, etc... so cross your fingers, and if TWRP can mount and find a USB storage device you just have to flash the three zip files from USB storage as previously described. Otherwise, there is not much I could do personally without the device in hand, although the easiest path forward might be to re-flash a stock ROM and start over again. And please note you would not be the first person reading (or writing) this message to need to do that. Once you get the hang of this, it is not a brutal process, but the first time or two it can be a bit intimidating. Hang in there, the good news is that it is somewhat difficult to totally brick most of these things, so persistence should win out. As long as you can still boot it into TWRP you're fine. Now, one other very important thing. If somehow the bootloader was not unlocked, none of this is going to work at all. SO if that is the case, your only recourse is going to be to get that taken care of first, which requires one of: some finesse with ADB / fastboot, a ROM of some sort (i.e. re-install stock) installed on the device that lets you unlock it by flipping the switch in developer settings , or some other more geeky process that is best supervised by a person who genuinely knows what they are doing and with physical access to the device. There will be no shortage of content out here concerning how-to, but some of the folks writing it are not necessarily technical writers targeting a less experienced audience, even if they are in many cases quite brilliant programmers.
Click to expand...
Click to collapse
The bootloader is unlocked becaues I unlocked it and I see the red sign:
Code:
DEVICE STATE - unlocked
When I click Mount I get the following options, System, Vendor Data, Cache, USB OTG, which one should I select ?
I was able to fix it and I installed it now the Lineage OS works
I had to go to
Code:
Mount > enable MTP
and after that I was able to use
Code:
ADB SHELL
and after that I was able to push the zip to the device. Once it was on the phone I was able to use TWARP to install it.
Code:
$ adb push lineage-15.1-20180430-nightly-bullhead-signed.zip sdcard
The only question I have is why I get this message every time I turn on the phone, how can I remove it? :
Code:
A vendor image mismatch has been detected. Typically this means your vendor images us out of date. Please enousre your vendor image matches OPM2. 171019.029
Since I decided not to install Play Store, how can I now install some programs without the playstore ?
flex567 said:
I was able to fix it and I installed it now the Lineage OS works
I had to go to
Code:
Mount > enable MTP
and after that I was able to use
Code:
ADB SHELL
and after that I was able to push the zip to the device. Once it was on the phone I was able to use TWARP to install it.
Code:
$ adb push lineage-15.1-20180430-nightly-bullhead-signed.zip sdcard
The only question I have is why I get this message every time I turn on the phone, how can I remove it? :
Code:
A vendor image mismatch has been detected. Typically this means your vendor images us out of date. Please enousre your vendor image matches OPM2. 171019.029
Click to expand...
Click to collapse
Wow, you took what I would have thought of as the long way, but so far, so good it would seem. I was thinking you could have simply mounted the USB as an OTG device and flashed directly from that via TWRP. I have ZERO clue about the "vendor image mismatch" message. But now that you have it more or less working, you COULD try putting the zip files into the regular downloads folder, do a dalvik and cache (factory reset) wipe, and re-flash them. You haven't loaded up a bunch of stuff to worry about replacing. Worst case you repeat initial setup. What have you got to lose?
---------- Post added at 08:36 PM ---------- Previous post was at 08:27 PM ----------
flex567 said:
I was able to fix it and I installed it now the Lineage OS works
I had to go to
Code:
Mount > enable MTP
and after that I was able to use
Code:
ADB SHELL
and after that I was able to push the zip to the device. Once it was on the phone I was able to use TWARP to install it.
Code:
$ adb push lineage-15.1-20180430-nightly-bullhead-signed.zip sdcard
The only question I have is why I get this message every time I turn on the phone, how can I remove it? :
Code:
A vendor image mismatch has been detected. Typically this means your vendor images us out of date. Please enousre your vendor image matches OPM2. 171019.029
Since I decided not to install Play Store, how can I now install some programs without the playstore ?
Click to expand...
Click to collapse
Missed that one, sorry. If you did not flash the GApps zip when you installed Lineage, you can hunt down the .APK files for apps you want on the web. That'd be the only way I can think of and a good reason to re-do it before it is too long into the process !!! If you pick the nano or even pico options you won't be dragging much if any Google bloat onto the phone. Personally, while I often find the Play Store to be a pain in the .... I can ignore it until I need something. On some devices it can certainly be most intrusive.
I don't think I will play around with it now for some time.
I was thinking you could have simply mounted the USB as an OTG device and flashed directly from that via TWRP
Click to expand...
Click to collapse
I tried to select the OTG thing but was unable to put the checkmark in.
I also found the fix for Vendor Image mismatch, didn't try if it works though:
https://gist.github.com/MacKentoch/48ad6b91613213ee9774c138267e2ed4#file-fix-lineageos-vendor-mismatch-error-nexus5x-md
I also think this needs to be updated:
https://wiki.lineageos.org/adb_fastboot_guide.html
https://wiki.lineageos.org/devices/bullhead/install
you COULD try putting the zip files into the regular downloads folder
Click to expand...
Click to collapse
I had problems pushing the LineageOS.zip file anywhere else, I coulnt create new folder.
flex567 said:
I was able to fix it and I installed it now the Lineage OS works
I had to go to
and after that I was able to use
and after that I was able to push the zip to the device. Once it was on the phone I was able to use TWARP to install it.
The only question I have is why I get this message every time I turn on the phone, how can I remove it? :
Since I decided not to install Play Store, how can I now install some programs without the playstore ?
Click to expand...
Click to collapse
Congratulations for not installing play store. I think you not installed play services as well. You simply did not install any GApps. That's the first step to get your setup slim and privacy friendly. Next steps are installing f-droid app. From f-droid you can install free software. If you really need apps from play store you can get them with yalp. If they don't run without Google play services you can try microG.
I found a page from which I can download apk files from play store so I will just use that for now.
I set up my new phone yesterday - rooted with some great help from folks on this forum. Everything was going smoothly and working properly until I did something (I was checking out All-in-One Toolbox and a screen popped up about a four-step process to select some particular 'file'). As a result, there are problems with my ability to access local files, for example:
When I open the built-in Files app, it displays an hourglass symbol with the message "Can't load content at the moment". Also, on the slide out panel, the icon that previously read 'Pixel 3XL' is missing.
When I tried to get a screen grab of the above, a notification indicated "Cannot save screenshot due to limited storage space".
When I launch Titanium Backup, it cannot find its backup folder.
Custom ringtones are not be used.
Note that when I use X-Plore, I can navigate to the 'SD Card' folder and all files are there. It is as if a 'symbolic link' was deleted.
Please help me resolve this problem!
groston said:
I set up my new phone yesterday - rooted with some great help from folks on this forum. Everything was going smoothly and working properly until I did something (I was checking out All-in-One Toolbox and a screen popped up about a four-step process to select some particular 'file'). As a result, there are problems with my ability to access local files, for example:
When I open the built-in Files app, it displays an hourglass symbol with the message "Can't load content at the moment". Also, on the slide out panel, the icon that previously read 'Pixel 3XL' is missing.
When I tried to get a screen grab of the above, a notification indicated "Cannot save screenshot due to limited storage space".
When I launch Titanium Backup, it cannot find its backup folder.
Custom ringtones are not be used.
Note that when I use X-Plore, I can navigate to the 'SD Card' folder and all files are there. It is as if a 'symbolic link' was deleted.
Please help me resolve this problem!
Click to expand...
Click to collapse
Just my 2 cents worth, but I've never been a fan of toolkits. They work great sometimes, but then again they don't at times. I think it's better to learn adb/fastboot on your own. I would recommend fastbooting the factory image again, without the -w, and see if that resolves your problem. Then leave well enough alone. And uninstall the toolkit app as well if that's what it is :good:
groston said:
I set up my new phone yesterday - rooted with some great help from folks on this forum. Everything was going smoothly and working properly until I did something (I was checking out All-in-One Toolbox and a screen popped up about a four-step process to select some particular 'file'). As a result, there are problems with my ability to access local files, for example:
When I open the built-in Files app, it displays an hourglass symbol with the message "Can't load content at the moment". Also, on the slide out panel, the icon that previously read 'Pixel 3XL' is missing.
When I tried to get a screen grab of the above, a notification indicated "Cannot save screenshot due to limited storage space".
When I launch Titanium Backup, it cannot find its backup folder.
Custom ringtones are not be used.
Note that when I use X-Plore, I can navigate to the 'SD Card' folder and all files are there. It is as if a 'symbolic link' was deleted.
Please help me resolve this problem!
Click to expand...
Click to collapse
What were you trying/wanting to do when "checking out" the toolkit? I agree with Badger about installing the factory image, but I would go one step further and leave the -w in place just running the flash-all as is. At some point when you have done some normal work on the phone, you can run it again without the -w so you can start to understand what is not deleted as well as how to re-root since you will need to do it every month. From your description, it sounds like you have deleted some stuff on the user side that would not be restored without the -w.
Gents,
I really did nothing with the toolkit other than a) look at the features it offered (was trying to discover which apps were running at boot time) and b) step through the one dialog that messed things up. As such, I would hate to have to reflash and start from ground zero again - especially when I get the sense that there is a simple fix that could resolve this specific issue. (Upon rereading Sliding_billy's response - it seems that reflashing does not impact user files - is this correct? After reflashing, I would have to boot to TWRP, reinstall Magisk, and everything would be good to go?)
FYI - the dialog in question is one that I had seen previously, when I updated my Note 4 from Android 4 to Android 5. It had something to do with selecting the DocumentsProvider location or some such (sorry that I am being so nebulous - I just did a quick search to try to find an example of the dialog, but did not).
groston said:
Gents,
I really did nothing with the toolkit other than a) look at the features it offered (was trying to discover which apps were running at boot time) and b) step through the one dialog that messed things up. As such, I would hate to have to reflash and start from ground zero again - especially when I get the sense that there is a simple fix that could resolve this specific issue. (Upon rereading Sliding_billy's response - it seems that reflashing does not impact user files - is this correct? After reflashing, I would have to boot to TWRP, reinstall Magisk, and everything would be good to go?)
FYI - the dialog in question is one that I had seen previously, when I updated my Note 4 from Android 4 to Android 5. It had something to do with selecting the DocumentsProvider location or some such (sorry that I am being so nebulous - I just did a quick search to try to find an example of the dialog, but did not).
Click to expand...
Click to collapse
Running the flash all with the -w in place will completely wipe your device. If you don't want that then remove the -w. But, without wiping the device there may be something left over that'll continue to cause you your current problem.
Sent from my [device_name] using XDA-Developers Legacy app
groston said:
Gents,
I really did nothing with the toolkit other than a) look at the features it offered (was trying to discover which apps were running at boot time) and b) step through the one dialog that messed things up. As such, I would hate to have to reflash and start from ground zero again - especially when I get the sense that there is a simple fix that could resolve this specific issue. (Upon rereading Sliding_billy's response - it seems that reflashing does not impact user files - is this correct? After reflashing, I would have to boot to TWRP, reinstall Magisk, and everything would be good to go?)
FYI - the dialog in question is one that I had seen previously, when I updated my Note 4 from Android 4 to Android 5. It had something to do with selecting the DocumentsProvider location or some such (sorry that I am being so nebulous - I just did a quick search to try to find an example of the dialog, but did not).
Click to expand...
Click to collapse
jd1639 said:
Running the flash all with the -w in place will completely wipe your device. If you don't want that then remove the -w. But, without wiping the device there may be something left over that'll continue to cause you your current problem.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Exactly what jd said. Running flash-all with no modifications will essentially do a factory restore of that build. Removing the -w (for wipe) from the batch file leaves the non-system files/settings, etc in place and you will then need to fastboot boot TWRP.img and install Magisk. As both of us mentioned, it may be best to get over the pain of a full image instead of seeing what issues remain without the -w in place in the batch. I think the real lesson here is that the folks who make these toolkits do a lot of hard work but it is still better/safer (especially on this device) to understand doing things manually.
I reflashed without the -w and everything seems to be fine. Thanks for the help!