Related
[SOLVED, see below].
I've also attached the Su flashable zip to this post, as linked below
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
I recently rooted my Desire using unrevoked 3.2.1 Basically, no problems so far.
However, when I have tried to run a few Apps that require ROOT access, the Superuser pop-up screen shows, EVERY TIME.
I have clicked Allow, and made sure to check "Remember", but it comes back every time for the same Apps.
I have double-checked that the Apps requesting Superuser permissions are indeed in the Superuser.apk list for Allow. They are, little green dot and all, but it doesn't seem to matter.
I tried a Batch routine in Titanium Backup, and I had to click that damn Allow button like 150 times!
Does anyone have any idea what's going here? Anyone experienced the same thing?
I wonder if it is related to what mortenmhp mentioned over in this post (post 3, "Cant remove Stock apps? Root Explorer and Unrevoked3"; sorry, I can't link yet)...
the fact that unrevoked3 still does not achieve S-OFF HBOOT and thus doesn't r/w to /system.
Btw. the thread mentioned:
http://forum.xda-developers.com/showthread.php?p=8324672#post8324672
Your problem should not have to do with this though.
The superuser app stores it's list on the data partition, and it should be able to grant su access to anything apart from rw to the protected partitions.
First off:
- Does it happen to all apps requesting su?
- Which version of superuser are you currently using?
- How did you get it? Like was it included in a rom or did you install it by flashing superuser only?
- If included in a rom, which?
And finally. You should start by trying to clear the data associated with the superuser app:
"settings -> applications -> application list* -> Superuser -> clear data button"
*I dont remember the exact name, and the charger for my desire is gone for now
If it does not work, you should also try to do a nandroid backup and a factory reset by wiping the data partition to see, if it doesn't fix it.
Thanks for your response, let me see if I can fill in some of the details:
Yes, it happens AFAIK for ALL Apps requesting Superuser access
Version: Superuser v2.3.6.1 - Added c...
Database version 5
(From the info at the bottom of the Superuser>Settings menu)
IIRC, I may have installed the App myself from the Market...? Is that even possible? Honestly, I may have jumped ahead of my knowledge in this one area. But I'm certain it wasn't from any flashing, unless unrevoked adds the App itself.
ROM, Froyo w/ HTC OTA Sept. update
I rooted with unrevoked3.2.1, but haven't flashed anything
(other than the Clockwork Mod as part of unrevoked, and, the ?re-flash? of Clockwork via ROM Manager)
The most noticeable example of this problem is Titanium Backup; I have to click Allow 14 times each time I open the App. And it is clearly listed in the Superuser List, with a green dot.
UPDATE: It is definitely possible to install this App directly from the Market, as I just re-did it. Then I Rebooted, but it all made no difference, still have 14 Allows in order to launch Titanium Backup
Results
Alright, I tried to "Clear Data", and then I did a reboot for good measure. It did NOT work.
The Superuser list was blank, but as soon as I started Titanium, I had to do the same 14 Allows. The Titanium>Log clearly shows each of them, but it's like the fact that the setting is "Remembered" doesn't have any effect.
I guess I can try the Nandroid back-up/wipe, but that just seems to be in the "format and reinstall Windows" family of solutions (no offense).
Other observation
Here's something else I noticed, may or may not be related.
I have Spare Parts installed, and I was testing the different settings.
First, Reboot/Recovery options ask for Superuser access, but then nothing happens, it just returns to the Spare Parts menu.
I'm interested in "upgrading" my boot animation (I have another thread about that), so I also tried the LeoFroyo Addon of Bootanimation>LeoFroYo BIOS
It Requested Superuser access, delayed while "Working...", and then asked to Reboot. When I clicked Yes, nothing. Just went back to the Spare Parts menu. When I rebooted manually, the stock HTC animation is still what I got.
Relaunching Spare Parts confirmed that the bootanimation setting was still on the upgrade, it apparently just didn't work.
The reason I mention these things is because I wonder if possibly I haven't achieved all the ROOT access that maybe I should have???
Any other thoughts? I'm not sure what else to try, but I can provide any other details that would be useful.
Maybe I'm just fighting a pointless losing battle on this, since I plan to flash to Cyanogen anyway. But it just find it irksome that I can't find a solution to a relatively straightforward issue.
It is because you cannot just install the superuser app from the market, because it needs root in the first place. This might just be your problem. I cant find the update.zip only including superuser right now, so if you want cm anyway, I would just go for it. Otherwise you will have to search for a zip file only including the superuser files or another rom with it included.
edit: and sorry for not replying but i have school as well
edit 2: This should be the zip file to flash to get superuser only hope you can get it to work.
Success
Yessir! That did it.
I think you're right. Don't know what I read to carelessly make me think I could just download Superuser from the Market. Actually, I'm not even too sure why its on there, since it CANNOT work if you install it that way.
I guess when I installed Superuser to grant ROOT permissions, I didn't have ROOT permissions. So, Superuser could grant other Apps ROOT (which did work), but it didn't have ROOT itself to store the Allow list. How ironic.
When I get to a computer, I'll add that linked zip as an attachment to this thread, along with some flashing Instructions in case anyone else is less familiar.
It must be pretty uncommon to do the work to get ROOT and then not flash a custom ROM with Superuser built in.
Thanks for your help. All glory to mortenmhp
okay, i was stupid. this fixed the problem for me too! thanks a lot.
Thank god for this thread
Had same problem
solved for me
And for now, i just want su, no custom rom, they seem to be sometimes unstable
Guide for dummies
just in case(copied),
Transfer this zip file file to your SD card. Remember where you saved it.
Reboot the phone into Recovery
(Boot the phone by holding down either the circle button or Volume Down button, then press the Power button. Select Recovery from the menu. (You can navigate the menus with the volume button, and make selections with the round button thingy).)
Select Install zip from SD card and navigate to where you copied the zip file and install. Watch out: Do NOT select the similar-looking apply sdcard:update.zip menu item. You have to confirm by selecting the correct ZIP file from a list.
reboot phone.
This woked for me too. Thanks a lot it was very annoying.
Oh and thanks for the dummies guide. I have not done anything but a nandbackup do it helped me feel a little more comfortable.
Great . It worked for me as well.
Thanks scott and all
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
Hey.
I come from the Rogers forums. The reason I am making this thread here is because I went over the thread multiple times, including the min-guide and the video-guide for GSM Nexus.
However, myself, as well as a few others, have been having a bit of a problem doing this because it just seems too overwhelming (and complicated) for us, and we were wondering if there is a possibility of getting a "layman's terms" sort of tips, hinters, etc. for it, especially when it comes to backing user data up (like sync accounts, contacts, etc.), and whatnot.
Thanks in advance.
Sorry if I come off as a noob/newb/n00b/whatever. I am a Multimedia student, not a developer or programmer, so I am not familiar at all with Linux programming.
AdelaisAer said:
Hey.
I come from the Rogers forums. The reason I am making this thread here is because I went over the thread multiple times, including the min-guide and the video-guide for GSM Nexus.
However, myself, as well as a few others, have been having a bit of a problem doing this because it just seems too overwhelming (and complicated) for us, and we were wondering if there is a possibility of getting a "layman's terms" sort of tips, hinters, etc. for it, especially when it comes to backing user data up (like sync accounts, contacts, etc.), and whatnot.
Thanks in advance.
Sorry if I come off as a noob/newb/n00b/whatever. I am a Multimedia student, not a developer or programmer, so I am not familiar at all with Linux programming.
Click to expand...
Click to collapse
Its probably better to ask a single particular question when you get stuck, What you have asked is very general.
Go as far as you can with the tool kit and when you have a problem give as much detail as you can so someone can help you.
Tool kits can be fast and easy but you won't learn anything and when you have a bit of trouble its all panic stations.
It's better to learn adb/fastboot, try this guide http://forum.xda-developers.com/showthread.php?t=1529058
gpfnzl said:
Its probably better to ask a single particular question when you get stuck, What you have asked is very general.
Go as far as you can with the tool kit and when you have a problem give as much detail as you can so someone can help you.
Tool kits can be fast and easy but you won't learn anything and when you have a bit of trouble its all panic stations.
It's better to learn adb/fastboot, try this guide http://forum.xda-developers.com/showthread.php?t=1529058
Click to expand...
Click to collapse
Oh. Sorry about that. Well, my main question is how to back user data up using the toolkit. I see options for applications and nandroid and stuff, but I don't see userdata such as contacts, sync accounts, etc. The most important stuff.
That's my main concern first and foremost. Also, I'm checking the guide right now; thanks.
I've just checked the tool kit briefly and don't see an option for what you want to do.
How ever:
contacts will sinc to your google account. On your phone go into
settings>accounts and sync>select your google account and check sync contacts.
"Titanium backup" can save accounts, wifi and alot of other stuff.
gpfnzl said:
I've just checked the tool kit briefly and don't see an option for what you want to do.
How ever:
contacts will sinc to your google account. On your phone go into
settings>accounts and sync>select your google account and check sync contacts.
"Titanium backup" can save accounts, wifi and alot of other stuff.
Click to expand...
Click to collapse
Ah. Alright, contacts, browser, and Google+ are now synced. In terms of user data, what would I really need to back up? I mean, if I flash, I can just redownload Google+, sign in, sync, and get my contacts back and browser data back, right?
EDIT: Also, it says that we need to locate the rom, which has to be .zip. I downloaded it from the Google Developers website, where they have factory images, but they are all .tgz. Is that fine?
EDIT2: Also, under ADB Mode, it never shows my phone's serial, so I can't do backups. :S I have Windows 7 64 bit. Fastboot mode shows the serial, though.
AdelaisAer said:
Ah. Alright, contacts, browser, and Google+ are now synced. In terms of user data, what would I really need to back up? I mean, if I flash, I can just redownload Google+, sign in, sync, and get my contacts back and browser data back, right?
EDIT: Also, it says that we need to locate the rom, which has to be .zip. I downloaded it from the Google Developers website, where they have factory images, but they are all .tgz. Is that fine?
EDIT2: Also, under ADB Mode, it never shows my phone's serial, so I can't do backups. :S I have Windows 7 64 bit. Fastboot mode shows the serial, though.
Click to expand...
Click to collapse
I sync contacts, browser, calendar and gmail with google.
Apps with there user data I save with titanium backup so they can be restored to how they where with the last rom.
The paid version has batch mode so you can do them all at once. After installing a new rom you will have to down load titanium backup again, open it and then restore all your apps.
Factory image: will return your phone to out of the box stock. I personally find stock a bit boring and not so user friendly. Custom roms can be personalized, and the UI easier to use. But thats personal preference.
I have AOKP build 40 that can be down loaded from the xda GNEX development page. use .ZIP roms only
you need to unlock your phone
root
install clockworkmod recovery. the flashing of a new rom is done with clockworkmodrecovery
No serial?
on your PC, go into the"android-sdk-windows" folder, then the "platform-tools folder" and open a command prompt window (shift+right click in the folder then select open command window here)
type in
adb devices
if your serial number does not show up, reinstall the samsung drivers.
gpfnzl said:
I sync contacts, browser, calendar and gmail with google.
Apps with there user data I save with titanium backup so they can be restored to how they where with the last rom.
The paid version has batch mode so you can do them all at once. After installing a new rom you will have to down load titanium backup again, open it and then restore all your apps.
Factory image: will return your phone to out of the box stock. I personally find stock a bit boring and not so user friendly. Custom roms can be personalized, and the UI easier to use. But thats personal preference.
I have AOKP build 40 that can be down loaded from the xda GNEX development page. use .ZIP roms only
you need to unlock your phone
root
install clockworkmod recovery. the flashing of a new rom is done with clockworkmodrecovery
No serial?
on your PC, go into the"android-sdk-windows" folder, then the "platform-tools folder" and open a command prompt window (shift+right click in the folder then select open command window here)
type in
adb devices
if your serial number does not show up, reinstall the samsung drivers.
Click to expand...
Click to collapse
For the rom, can I extract the tgz and re-extract it as a zip?
For the serial/adb stuff - I can't find that folder; where is it supposed to be? Also, do I unlock my phone after this or before? Also how? @[email protected] I totally got lost...
AdelaisAer said:
For the rom, can I extract the tgz and re-extract it as a zip?
For the serial/adb stuff - I can't find that folder; where is it supposed to be? Also, do I unlock my phone after this or before? Also how? @[email protected] I totally got lost...
Click to expand...
Click to collapse
I've never tried the .tgz to .zip so i can't give a accurate opinion.
Have you installed SDK from the guide? or you can google search it and down load it.
It should be in
C:\android-sdk-windows\platform-tools
Titanium backup is only available to root users, so no good for you at the moment.
you can back up apps to google
settings>backup and restore but ive never done it that way, and dont know how well it works.
---------- Post added at 03:06 PM ---------- Previous post was at 03:02 PM ----------
gpfnzl said:
I've never tried the .tgz to .zip so i can't give a accurate opinion.
Have you installed SDK from the guide? or you can google search it and down load it.
It should be in
C:\android-sdk-windows\platform-tools
Titanium backup is only available to root users, so no good for you at the moment.
you can back up apps to google
settings>backup and restore but ive never done it that way, and dont know how well it works.
Click to expand...
Click to collapse
back your sd card up to PC, from memory i think the unlock part wipes your phone
gpfnzl said:
I've never tried the .tgz to .zip so i can't give a accurate opinion.
Have you installed SDK from the guide? or you can google search it and down load it.
It should be in
C:\android-sdk-windows\platform-tools
Titanium backup is only available to root users, so no good for you at the moment.
you can back up apps to google
settings>backup and restore but ive never done it that way, and dont know how well it works.
Click to expand...
Click to collapse
Oh. Well, I downloaded it from the Google Developers (official) website, and they don't offer it in any other file-type. :S I can look it up on Google and see if anyone else says anything about it.
Wait, what? I didn't see SDK in the guide. o___o;
-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-
EDIT:
Okay, let's try again. xD
-I have GNex Toolkit 7.6.
-I installed it.
-I used option 1. to install drivers.
-Fastboot mode works fine. Serial displays.
-ADB mode doesn't (no serial). Apparently, as you say, I need SDK? Didn't see SDK anywhere in the guide, or the video, or the Toolkit software.
ALSO, decided to open the .TGZ file up (that I got from here: https://developers.google.com/android/nexus/images), and here are two screenshots:
http://i49.tinypic.com/2rzb30h.png
http://i47.tinypic.com/96dqo3.png
I tried following this thread and you seem to be talking about two different things. The factory images you downloaded from Google developers, or the .tgz file is what you would use to restore your phone to the factory state, also the state I believe your phone is currently in. Unzipping the appropriate tgz file for your phone will yield the radios and another zip file that will be flashed to restore - do not unzip that file.
As far as your confusion with the android sdk, is your phone currently still locked? It sounds like it is. When I learned to customize my phone I did everything the long way without using a kit - which I highly recommend. That way you not only learn much more, but you'll be able to answer most of the questions you have on your own. Unlocking your phone, fast boot mode, the android platform tools folder, etc have to be properly configured before you can flash anything. You can also do all this via Windows/command prompt, Linux isn't necessary, it's just easier in some respects, ie driver installation and such.
I really would recommend some more research before you jump in and start playing with system/root files.
Sent from my Galaxy Nexus using xda app-developers app
ttahatt said:
I tried following this thread and you seem to be talking about two different things. The factory images you downloaded from Google developers, or the .tgz file is what you would use to restore your phone to the factory state, also the state I believe your phone is currently in. Unzipping the appropriate tgz file for your phone will yield the radios and another zip file that will be flashed to restore - do not unzip that file.
As far as your confusion with the android sdk, is your phone currently still locked? It sounds like it is. When I learned to customize my phone I did everything the long way without using a kit - which I highly recommend. That way you not only learn much more, but you'll be able to answer most of the questions you have on your own. Unlocking your phone, fast boot mode, the android platform tools folder, etc have to be properly configured before you can flash anything. You can also do all this via Windows/command prompt, Linux isn't necessary, it's just easier in some respects, ie driver installation and such.
I really would recommend some more research before you jump in and start playing with system/root files.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Oh. Derp. Well, I edited my post before yours, and I saw it has two images in it (one of them is radio) and a zip file. So yeah, I guess that contributed a lot to my confusion.
Also, I think my phone is still locked. I have done literally nothing to it yet.
Also, I want to flash it because it's currently in a Rogers/Samsung-type OS, where updates aren't pushed because it takes them months to get the A-Okay, for whatever reason. I want to flash it to the Google-line so I can get regular updates without waiting. :S
AdelaisAer said:
Oh. Well, I downloaded it from the Google Developers (official) website, and they don't offer it in any other file-type. :S I can look it up on Google and see if anyone else says anything about it.
Wait, what? I didn't see SDK in the guide. o___o;
-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-==-=-=-=-=-=-=-
EDIT:
Okay, let's try again. xD
-I have GNex Toolkit 7.6.
-I installed it.
-I used option 1. to install drivers.
-Fastboot mode works fine. Serial displays.
-ADB mode doesn't (no serial). Apparently, as you say, I need SDK? Didn't see SDK anywhere in the guide, or the video, or the Toolkit software.
ALSO, decided to open the .TGZ file up (that I got from here: https://developers.google.com/android/nexus/images), and here are two screenshots:
http://i49.tinypic.com/2rzb30h.png
http://i47.tinypic.com/96dqo3.png
Click to expand...
Click to collapse
LOL i'm starting to see the confusion :s
skd is for manual input, better for you in the long run.
You want to use the tool kit to unlock,root & flash CWM? the sdk install is not needed.
If using the tool kit and you have selected your device type and can see your serial number....
you just need to select from the list what you want to do. there is a choice to do all = the one click method available in the list of options.
the only other thing to do is to have your phone in the right mode, either android or adb.
Is your goal to be able to flash new roms/kernels/radio?
Plug your phone in to pc....reboot your phone into fastboot (vol+/vol- and power) see if drivers install (should see bottom right hand side of computer)
gpfnzl said:
LOL i'm starting to see the confusion :s
skd is for manual input, better for you in the long run.
You want to use the tool kit to unlock,root & flash CWM? the sdk install is not needed.
If using the tool kit and you have selected your device type and can see your serial number....
you just need to select from the list what you want to do. there is a choice to do all = the one click method available in the list of options.
the only other thing to do is to have your phone in the right mode, either android or adb.
Is your goal to be able to flash new roms/kernels/radio?
Click to expand...
Click to collapse
My goal is to back my contacts and app data up, and then flash my phone with the new factory os that I got from Google Developer. :S But this whole guide is ajfkjsdkjfksjfkwejfkjsdkjfakw. Also, sorry for ranting. >___<;
See, if Samsung had just pushed updates to Canadian Android phones in the first place like normal people, I wouldn't be here. But instead, they hold onto updates until they (and Rogers) can stamp their names all over it and then takes a few more months just to approve it a second time, for whatever reason. :S
Instead, I have to come here, try to do this whole thing, and then install that factory Google-line OS so I can get regular updates.
Go look in the Rogers community forums - nothing but threads complaining about it. I'm one of very few who actually came to a forum like this.
OP, have a read of the "flash" link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
OP, have a read of the "flash" link in my signature.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Alright, will do.
Also, sorry if my replies get a bit slow now - eating.
EDIT: Ugh, this is getting reaaly confusing now. o-o; Especially the part where you make a backup of the phone build. @[email protected];
When I get home,
If you haven't found a solution,
I will install ToolKit 7.6 and try to do what you are trying to do, then walk you through it.
gpfnzl said:
When I get home,
If you haven't found a solution,
I will install ToolKit 7.6 and try to do what you are trying to do, then walk you through it.
Click to expand...
Click to collapse
Alright. Thank you. :3
So far, I synced my contacts, browser, etc. up with my Google+ account, so that's backed up, and I can go into fastboot no problem and have the toolkit detect it.
I just wanna make sure that there's nothing else that needs backing up (if there is, then what do I backup, and how?), and then just flash my phone with the new 4.1.1, and be done.
Also, thank you so much for actually putting up with me. A lot of people would normally be rather mean/hateful towards new-comers like me, so thank you.
EDIT: Why must this be so complicated... @[email protected] Curse you, Samsung.
Just for the hell of it, back up your SD card.
We all need a bit of help getting started.
Good luck.
gpfnzl said:
Just for the hell of it, back up your SD card.
We all need a bit of help getting started.
Good luck.
Click to expand...
Click to collapse
Er, how do? o-o;
Plug your phone into your PC
open *my computer* select the *galaxy nexus*, select *internal storage* and copy every thing to your computer.
unlock your lock screen on the phone or your computer wont see the internal storage
A week ago I flashed the current (lineage-14.1-20170504-nightly-oneplus3-signed.zip) lineage os nightly to my phone. I did not pay that much attention til I realize the impact, so no guarantee for the temporal order. I am pretty shure, that in the first place, I tried to flash the image via the update menu (is this called OTA update?). The previous update two weeks ago already results in partial data los. By this I mean some (maybe all) apps disappears after the update, but after installing them again, all of them provided the pre-update data - only exception was signal. This time the phone was like in factory state. But when I try to reinstall the telegram app - the app store refuses to install the app because of the presence of a identical named app.
Using adb shell shows me, that all apps and data where still present in the /data subdirectories. Even those I didn't had reinstalled til that time . So I took advantage of momentum and backed up some files and decided to perform a full pre factory reset formatting everything twrp let me format. After flashing the lineage update, another full format because things seems still weird, second lineage nightly flash, realizing I have to first flash OOS-x.y.z and a final third lineage flash, I thought I finally obtain a running system. After initial configuration I decided to only copy my previous wpa_supplicant.conf file back to the system. Since overwriting this file while running android didn't led to anything, I tried to replace this file in recovery mode. Instead of remembering my password, goatish oneplus 3 desides to perform factory reset.
After what seems to be a lower six digit number of flashing attemps I came to the conclusion that performing any modification to the file system while the native kernel is not running results in factory reseting the device. In the mean time I also figured out what dm-verity means - an error message I got used to and maybe a nice feature as long as you don't try to take your old config files to a new system. And I know I am the millionth person facing that problem in a dedicated thread, but I found nothing which links this annoying boot loader message to my reset problem.
I made my previous recovery attemps between the toilet and my bed, so I hadn't any strategy at all. But thank god its friday! I read: dm-verity is a feature of the device mapper which guarantees data integrity. When I alter the data using any other than the native system, the device mapper notices the integrity violation and reports to the system. I am only guessing that this makes the system to reset itself - Am I right? Even if I appreciate this concept, I think this might be a little too ambitious. Can I alter androids behaviour in this point? In the best case I want to temporary disable this feature, do some root stuff and turn it on again. Is this possible?
I could follow one of that numerous tutorials to remove that dm-verity message, but I am not confortable with flashing zip files from dubious file hosters as well as copy-pasting commands without any idea of what I am doing. So maybe someone could provide a little more information than the seven step recipe of getting rid of that error message blog posts.
I really appreciate material which explains my problem. I am quite new to android and I didn't figured out how to maneuver around all these google results which tells me to install a specific app which may will hide my problem. So thank you in advance.
hinerk0815 said:
A week ago I flashed the current (lineage-14.1-20170504-nightly-oneplus3-signed.zip) lineage os nightly to my phone. I did not pay that much attention til I realize the impact, so no guarantee for the temporal order. I am pretty shure, that in the first place, I tried to flash the image via the update menu (is this called OTA update?). The previous update two weeks ago already results in partial data los. By this I mean some (maybe all) apps disappears after the update, but after installing them again, all of them provided the pre-update data - only exception was signal. This time the phone was like in factory state. But when I try to reinstall the telegram app - the app store refuses to install the app because of the presence of a identical named app.
Using adb shell shows me, that all apps and data where still present in the /data subdirectories. Even those I didn't had reinstalled til that time . So I took advantage of momentum and backed up some files and decided to perform a full pre factory reset formatting everything twrp let me format. After flashing the lineage update, another full format because things seems still weird, second lineage nightly flash, realizing I have to first flash OOS-x.y.z and a final third lineage flash, I thought I finally obtain a running system. After initial configuration I decided to only copy my previous wpa_supplicant.conf file back to the system. Since overwriting this file while running android didn't led to anything, I tried to replace this file in recovery mode. Instead of remembering my password, goatish oneplus 3 desides to perform factory reset.
After what seems to be a lower six digit number of flashing attemps I came to the conclusion that performing any modification to the file system while the native kernel is not running results in factory reseting the device. In the mean time I also figured out what dm-verity means - an error message I got used to and maybe a nice feature as long as you don't try to take your old config files to a new system. And I know I am the millionth person facing that problem in a dedicated thread, but I found nothing which links this annoying boot loader message to my reset problem.
I made my previous recovery attemps between the toilet and my bed, so I hadn't any strategy at all. But thank god its friday! I read: dm-verity is a feature of the device mapper which guarantees data integrity. When I alter the data using any other than the native system, the device mapper notices the integrity violation and reports to the system. I am only guessing that this makes the system to reset itself - Am I right? Even if I appreciate this concept, I think this might be a little too ambitious. Can I alter androids behaviour in this point? In the best case I want to temporary disable this feature, do some root stuff and turn it on again. Is this possible?
I could follow one of that numerous tutorials to remove that dm-verity message, but I am not confortable with flashing zip files from dubious file hosters as well as copy-pasting commands without any idea of what I am doing. So maybe someone could provide a little more information than the seven step recipe of getting rid of that error message blog posts.
I really appreciate material which explains my problem. I am quite new to android and I didn't figured out how to maneuver around all these google results which tells me to install a specific app which may will hide my problem. So thank you in advance.
Click to expand...
Click to collapse
Your story is too long to go through. But most likely your issue will be solved if you install blue sparks twrp. Check his thread in the unified section
Today, my phone got bricked after I installed Magisk, am i am looking for a way of sorting it out. The phone was running Android 9 DP3 when rooted, and I was following HighOnAndroids root guide on Youtube for reference,
I unlocked my bootloader and successfully installed TWRP. After this, I installed Magisk, which went throuygh perfectly fine. However, after rebooting the phone, I am stuck on the google splash screen, with a small progress bar that stays for the duration of the time on this screen. After about 2 minutes, the phone reboots into TWRP again.
Does anyone know how I could return to stock Android or at least escape this issue?
Many thanks
James
Jameswebb97 said:
Today, my phone got bricked after I installed Magisk, am i am looking for a way of sorting it out. The phone was running Android 9 DP3 when rooted, and I was following HighOnAndroids root guide on Youtube for reference,
I unlocked my bootloader and successfully installed TWRP. After this, I installed Magisk, which went throuygh perfectly fine. However, after rebooting the phone, I am stuck on the google splash screen, with a small progress bar that stays for the duration of the time on this screen. After about 2 minutes, the phone reboots into TWRP again.
Does anyone know how I could return to stock Android or at least escape this issue?
Many thanks
James
Click to expand...
Click to collapse
Use duces script to flash June google factory image.
jlokos said:
Use duces script to flash June google factory image.
Click to expand...
Click to collapse
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."
Jameswebb97 said:
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."
Click to expand...
Click to collapse
You need this information (the stuff I made bold + the hyperlink):
Code:
If you are having issues with this script:
Download the latest fastboot and adb Platform Tools UPDATED Dec. 22, 2017!!! This is the most common problem!!!
Download/Update Google USB Drivers
Video: Force-Installing the Android USB Drivers Fastboot & ADB
[B]Verify you have the [URL="https://wiki.lineageos.org/adb_fastboot_guide.html"]environment variable (path)[/URL] set for adb and fastboot[/B]
Try a different USB port
Try a different cable
Format Userdata in Stock Recovery
Try to boot stock before doing mods like Locking Bootloader / Kernel / TWRP / Magisk
Jameswebb97 said:
I followed the guide on the DeucesScript XDA page but the command window keeps saying "'fastboot' is not recognized as an internal or external command, operable program or batch file."
Click to expand...
Click to collapse
umph....hate to tell you, but you have a long way to go...
so before going on this "journey", I would suggest you booting into TWRP again, and try installing (not adb sideloading, just in case you're doing that) Magisk again. Also, be sure you are using the latest (might be considered "beta") 16.4 for taimen... I'm thinking your boot.img or dtbo.img simply may have gotten glitchy and repatching (by installing Magisk again) might fix it...
Also, if you want to go a step further, you might want to consider using the official Magisk uninstaller. Since Magisk makes a copy of your stock boot and dtbo image, it may put that back so you can get it in working order to get into the system (although without root), and then figure things out and/or reinstall Magisk (through TWRP is best) while all things Magisk was removed...
Good luck and hope this helps....
Make sure you are trying to open from the correct location, and put .\fastboot
EvilDobe said:
You need this information (the stuff I made bold + the hyperlink):
Code:
If you are having issues with this script:
Download the latest fastboot and adb Platform Tools UPDATED Dec. 22, 2017!!! This is the most common problem!!!
Download/Update Google USB Drivers
Video: Force-Installing the Android USB Drivers Fastboot & ADB
[B]Verify you have the [URL="https://wiki.lineageos.org/adb_fastboot_guide.html"]environment variable (path)[/URL] set for adb and fastboot[/B]
Try a different USB port
Try a different cable
Format Userdata in Stock Recovery
Try to boot stock before doing mods like Locking Bootloader / Kernel / TWRP / Magisk
Click to expand...
Click to collapse
Ive tried all of this now, i got the script working, but now the phne says it is corrupt and i cannot get into recovery. Is this game over do you think?
simplepinoi177 said:
umph....hate to tell you, but you have a long way to go...
so before going on this "journey", I would suggest you booting into TWRP again, and try installing (not adb sideloading, just in case you're doing that) Magisk again. Also, be sure you are using the latest (might be considered "beta") 16.4 for taimen... I'm thinking your boot.img or dtbo.img simply may have gotten glitchy and repatching (by installing Magisk again) might fix it...
Also, if you want to go a step further, you might want to consider using the official Magisk uninstaller. Since Magisk makes a copy of your stock boot and dtbo image, it may put that back so you can get it in working order to get into the system (although without root), and then figure things out and/or reinstall Magisk (through TWRP is best) while all things Magisk was removed...
Good luck and hope this helps....
Click to expand...
Click to collapse
This is good advice, thanks. i have a new problem (ugh), where i got the script working through changing the paths, but now the phone says that it is corrupt and i cannot access TWRP. Game over?
Jameswebb97 said:
Ive tried all of this now, i got the script working, but now the phne says it is corrupt and i cannot get into recovery. Is this game over do you think?
Click to expand...
Click to collapse
With the unlocked bootloader it'll always say the device is corrupt. Manually put the device into the bootloader & flash the DeucesScript. You're basically starting over at this point but it is possible to get up & going again.
Jameswebb97 said:
This is good advice, thanks. i have a new problem (ugh), where i got the script working through changing the paths, but now the phone says that it is corrupt and i cannot access TWRP. Game over?
Click to expand...
Click to collapse
EvilDobe said:
With the unlocked bootloader it'll always say the device is corrupt. Manually put the device into the bootloader & flash the DeucesScript. You're basically starting over at this point but it is possible to get up & going again.
Click to expand...
Click to collapse
EvilDobe might be right...but I have a bit to offer before maybe starting all over...
I doubt you needed to edit the script and "change the paths." Most likely you merely did not have the images (you extracted from the .zip of the Full Factory image you got from the Google Developers site) inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders.
In any case, I suggest you get the TWRP image file [.img] (NOT the installer .zip necessarily), put the .img file "... inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders." (I've seen some users simply cut and paste those 2 .exe files only to the extracted folder -- this is why I state it this way) Then, power down your device. After it's off, hold down the Volume Down button and press & hold the Power button (this is the manual way to get into the Bootloader Mode). Once there, plug your phone into your computer (USB-A to USB-C would be best) and open a command prompt/powershell ("run as administrator" or with administrative priveleges) and direct it to the platform-tools folder (i.e. if I put it on my desktop, it would be "C:\Users\MyName\Desktop\platform-tools"), you can temporarily boot into TWRP via command
Code:
fastboot boot twrp-3.2.1-2-taimen.img
When in TWRP (hopefully), I suggest trying to do what I advised before -- try either Magisk installer to repatch the boot and dtbo image, or Magisk Uninstaller to attempt to replace your boot and dtbo to stock.
*NOTE: Of course, this is assuming you are running Microsoft Windows (if not, you will need to input .\ as @naiku suggested) and also the whole "device is corrupt" is due to "funky" boot image issues. If not, I/we can guide you to flashing the Full Factory back onto the phone (hopefully without losing data and settings)...
Good luck and hope this helps...
simplepinoi177 said:
EvilDobe might be right...but I have a bit to offer before maybe starting all over...
I doubt you needed to edit the script and "change the paths." Most likely you merely did not have the images (you extracted from the .zip of the Full Factory image you got from the Google Developers site) inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders.
In any case, I suggest you get the TWRP image file [.img] (NOT the installer .zip necessarily), put the .img file "... inside the "platform-tools" folder with the adb & fastboot .exe and all the other files and folders." (I've seen some users simply cut and paste those 2 .exe files only to the extracted folder -- this is why I state it this way) Then, power down your device. After it's off, hold down the Volume Down button and press & hold the Power button (this is the manual way to get into the Bootloader Mode). Once there, plug your phone into your computer (USB-A to USB-C would be best) and open a command prompt/powershell ("run as administrator" or with administrative priveleges) and direct it to the platform-tools folder (i.e. if I put it on my desktop, it would be "C:\Users\MyName\Desktop\platform-tools"), you can temporarily boot into TWRP via command
Code:
fastboot boot twrp-3.2.1-2-taimen.img
When in TWRP (hopefully), I suggest trying to do what I advised before -- try either Magisk installer to repatch the boot and dtbo image, or Magisk Uninstaller to attempt to replace your boot and dtbo to stock.
*NOTE: Of course, this is assuming you are running Microsoft Windows (if not, you will need to input .\ as @naiku suggested) and also the whole "device is corrupt" is due to "funky" boot image issues. If not, I/we can guide you to flashing the Full Factory back onto the phone (hopefully without losing data and settings)...
Good luck and hope this helps...
Click to expand...
Click to collapse
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!
Jameswebb97 said:
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!
Click to expand...
Click to collapse
I wouldn't go that far with staying away. When I come across people IRL that want to start doing this stuff I always tell them to read the instructions, step through them, read the instructions again, ask questions (as you did here) BEFORE you get started, read the instructions again, and only when you're confident start messing with your device. This is a fun, and at times stressful, hobby. It's great when everything goes according to plan but it's an omg omg omg omg omg omg moment when you mess something up.
Start with baby steps. The straight upgrade to P is fairly simple provided your device is unlocked. Get that working & you'll be set. I have root on my DP3 & the only thing I've done so far is delete some apps from system that I know I don't want/need. If your main goal is to just enjoy your phone, test out Android P, and maybe go back... root isn't needed. Once everything is squared away & you're running for a day or so you can always fastboot to recovery, make a backup, and then try to add root. I hope you don't shy away & get deeper into the hobby. It truly starts to get fun when you begin to understand more of what is going on.
Jameswebb97 said:
Pleased to be editing this comment; managed to get it working following your step by step. Think i'm going to stay away from rooting something this expensive in the future! Thanks so much!
Click to expand...
Click to collapse
Hey I'm so glad you got it working! Leave me a "Thanks!" would make it up to me ... I'm always happy to help out and get things figured out...yet I don't get the satisfaction of knowing if it does end up helping a lot of the time because a good number don't come back with their experience...so thanks for that! Glad you got it going...
EvilDobe said:
I wouldn't go that far with staying away. When I come across people IRL that want to start doing this stuff I always tell them to read the instructions, step through them, read the instructions again, ask questions (as you did here) BEFORE you get started, read the instructions again, and only when you're confident start messing with your device. This is a fun, and at times stressful, hobby. It's great when everything goes according to plan but it's an omg omg omg omg omg omg moment when you mess something up.
Start with baby steps. The straight upgrade to P is fairly simple provided your device is unlocked. Get that working & you'll be set. I have root on my DP3 & the only thing I've done so far is delete some apps from system that I know I don't want/need. If your main goal is to just enjoy your phone, test out Android P, and maybe go back... root isn't needed. Once everything is squared away & you're running for a day or so you can always fastboot to recovery, make a backup, and then try to add root. I hope you don't shy away & get deeper into the hobby. It truly starts to get fun when you begin to understand more of what is going on.
Click to expand...
Click to collapse
And it's as @EvilDobe means.....
I remember back in the days of the Motorola Droids (OG Droid1, Droid 3, & Droid 4) where you could really mess things up and come out with a big ol' "brick" "paperweight" as there were many instances where you could not come back from (i.e. updating to a certain point, then attempting to downgrade when Google/Motorola/Verizon put blocks that breaks it). But this isn't the case these days. @Jameswebb97, at least with the Pixel 2's, Oreo and/or P(Android OS 9), it's actually more difficult than easy to get that too far gone. The only reason why I can help so many troubleshooting their issues is because I, myself, have wrecked my current device in some serious ways! So I can relate and have experience in helping in the same situations. I've gotten it to where it says "device is corrupt," (which isn't all that uncommon), BUT with the added desperate troubleshooting where I had to wipe/erase, changing partition types, format several partitions, even go about "resizing" the partition to match the "target extraction size" of the Full Factory flash, and even as far as learning to manually flash the various system partitions and that there are two (system_a & system_b) but, in Google's infinite wisdom(?), one flashes to system_a and the other to system_other!!! And I haven't even started on reading others' issues when going after the Slot A and Slot B complications -- I didn't even attempt to touch this in that troubleshooting story.
My point is: I think I've broken my device farther than most people and got it so close to the brink, and yet I was able to bring it back and am still using that same device today (most people would usually, at that point, go and get a RMA replacement). Honestly, as long as you have access to Bootloader Mode (which Google, in their infinite wisdom, seems to have placed it in the main board memory or separate memory rather than storage as to make it always accessible which makes it hard to "lose"), you have a really good (seemingly perfect) "safety net" in which you can always flash back to a working, stock state -- which is why it's the best policy to just make good backups before experimenting so, if anything, you get back to this state and restore all your data. I'm not trying to convince you to root or to try custom ROMs or anything -- even though there are many great reasons and capabilities of rooting -- I am simply appealingl to your sense of curiosity and reassure you so you aren't held back and you don't restrict and limit yourself if you don't want to, but are to fearful to experiment.
I hope you don't take this post as "lecturing" or anything, just some thoughts I hope you consider...
Glad it worked out in the end for you!