Database Users

[Recovery] RA Revamped for Iconia HC&ICS

Note 3.16 and below are for HoneyComb bootloader 3.17 & up are for ICS patched bootloader.
This is built from my forked Amon Ra recovery source.
WARNING UNLESS YOU ARE VERY FAMILIAR AND COMFORTABLE USING COMMANDLINE/TERMINAL DO NOT MESS WITH THE EXT3|EXT4 MENU. MESSING WITH THE PARTITION FORMATS CAN LEAVE YOUR ICONIA IN A STATE THAT IS UNABLE TO BOOT NORMALLY AND REQUIRES FIXING VIA COMMANDLINE. Fix for ignoring this warning is done by running "iconia_repair.sh help" from command line in recovery.
Full source for both Apache licensed recovery and GPL licensed kernel & busybox are here
Recovery Features:
Special features for acer iconia :
Touch enabled UI
Can use usb flash drive or normal sdcard as sdcard to flash roms and to use in nandroid backup/restore.
Automatically runs itsmagic on boot
External sdcard mass storage works on iconia
Automatically backs up usb serial (uuid) and the start of mmcblk0 in nandroid backup.
Will not remove /data/media unless full ext wipe option is selected (off by default)
ADB as root user
USB-MS Toggle :mounts sdcard as mass storage
Backup/Restore:
Nand Backup : Select Items to backup with the [X]
Nand Restore : browse to and select nandroid backup items with [X] to restore
Nand Restore Clockwork : browse to and restore cwm backup
Flash Zip From Sdcard: Update.zip must be in root of sdcard or you can directory browse.
Toggle Signature Verify : Toggle on/off signature checking on flashing zips
Wipe Menu:
Wipe data/factory reset: wipes all (data, cache, android_secure & dalvik if outside of /data)
Wipe cache
Wipe Dalvik cache : Wipes Dalvik cache in all possible locations if moved by apps2sd
Wipe SD:ext : Wipes Apps2sd ext partition
Wipe Battery Stats
Wipe rotate settings
Wipe data only
Wipe system
Wipe sdcard
Wipe .android secure : Wipes froyo+ native .android_secure on sdcard
Toggle full ext wipe: Toggles full or quick wipe of ext partitions
Partition Sdcard:
Partition SD: Partition's sdcard for apps2sd (this formats card so all non backed-up data is lost)
Repair Sd:ext
SD:ext2 to ext3 : coverts apps2sd ext2 partition to ext3
SD:ext3 to ext4 : same as above but ext3 to ext4 (
Mounts:
Gui mounts to avoid typing in terminal to mount system, data, cache, sd-ext (if exists), sdcard
Other:
Fix Permissions
Move recovery log to SD
Key Test : Output keycodes for debugging recovery
Check Battery Lvl
Ext3|4 menu: Formatting and re-formatting of partitions
Developer menu:
Make and flash boot from zImage : This makes a mkboot folder on sdcard and mounts sdcard as mass storage then you copy a zImage and kernel modules into this folder and it will create a new boot like anykernel and flash it.
Install su & superuser: Installs or fixes su & superuser install (removes old if exists)
Install eng (unguarded) su: Installs engineering su that doesn't use superuser (removes old su & superuser if exists)
Reboot to bootloader: reboots to bootloader/hboot
Reboot recovery : reboots phone back into recovery
Trouble Shooting:
Use option under Other menu to move recovery log to sd. Mount your sdcard to pc and read that file called recovery.log which will be on your external sdcard. It should have detailed cause of error if its not self-explainatory upload it here as an attachment and then post details about the error. Posts without the log are a complete waste of my time and will be ignored as there is no usable info to assist me in troubleshooting it. You will also be told to go visit /dev/null.
Special Thanks:
Thanks to :
Amon Ra
Koush
Sc2k for itsmagic and getuid.ko
Gweedo767 & CEnnis91 for the touch ui
Skrilax_CZ for patched ICS bootloader & setbootmode

Download Section:
To flash on HC bootloader(requires root):
run itsmagic then
Code:
adb push recovery-ra-iconia-3.13-gnm.img /sdcard
adb shell
su
dd if=/sdcard/recovery-ra-iconia-3.13-gnm.img of=/dev/block/mmcblk0p1
sync
reboot recovery
To flash on ICS Patched Bootloader:
fastboot flash recovery nameofrecovery.img
V3.17 Recovery flashable zip : recovery-ra-iconia-3.17-gnm.zip
ICS recovery-ra-iconia-3.17-gnm.img
md5sum e74dd63395baed6d00c724024ab2d5cc recovery-ra-iconia-3.17-gnm.img
recovery-ra-iconia-3.16-gnm.img
md5sum 357a7033171585005db89d505b6b7c65 recovery-ra-iconia-3.16-gnm.img
recovery-ra-iconia-3.15-gnm.img
md5sum f40fc8fe8708df75583338d09be33ea0 recovery-ra-iconia-3.15-gnm.img
recovery-ra-iconia-3.14-gnm.img
md5sum d69390b62dd914a440ca2ae90ff95a0a recovery-ra-iconia-3.14-gnm.img
recovery-ra-iconia-3.13-gnm.img
md5sum 292d0a37cc7971baab2b32d6dae0d74c recovery-ra-iconia-3.13-gnm.img
Flashable zip for 3.13 is here http://forum.xda-developers.com/showpost.php?p=21727826&postcount=13
Changelog 3.14 :
Added menu option to wipe flexrom and also included it in the default wipe all
Added option to flash a zip from internal storage
Added warnings on using the ext3|4 menu
Added recovery shell script called iconia_repair.sh for users that ignore the above warning and have corrupted their partitions. To use call "iconia_repair.sh help" from adb shell in recovery.
Changelog 3.15
Fixed wipe boot option on emmc devices
Fixed ext3|ext4 format menu for iconia & updated the iconia_repair.sh script to match (still may error 1st time if users used this option on 3.13 or 3.14 to format use script to repair and it will work properly from there out)
Itsmagic is now built into recovery binary
Sdcard is now unmounted after flashing a zip from it.
Changelog 3.16
Fixed nandroid restore from usb stick
Added ability to nandroid restore a cwm backup from usb stick
Changelog 3.17
Updated for ICS patched bootloader
Removed auto run of itsmagic (still there from cmd line)
Updated Mass storage in recovery to 2.6.39 kernel
Compiled setbootmode into recovery -- call setbootmode from cmd line to use
Default quick wipe and nandroid backup skips /data/linux directory if present -- toggling full ext wipe will still remove and reformat 100% of /data
Note: nandroid backup folder is changed from nvmem=* to your devices serial # so you may need to manually move old RA backups into new folder.
Updated su & superuser.apk to current

Seems cool ill try it out in am.
Sent from my HTC Inspire 4G using Tapatalk

Thanks bro. Just downloaded it. Will give it a try in the am. Off to bed!

Just gave it a quick test. Seemed to work fine (touch controls & backup). Haven't tried a restore yet, which is the true test.
Much thanks! This looks extremely promising.

just curious, being a first time venturing a little bit with my a500, how does one run "itsmagic"? i'm having issues with my windows 7 x64 pc recognizing my tablet running thor's latest ICS build 89 over adb, so would it be possible for somebody to make this as a flashable zip from the recovery i already have installed? or is that crazy... i flash new recoveries all the time for my fascinate or droid 1 in CWMR so I'm just curious. thanks!

Same here ive looked at the old its magic thread from way back and still not sure how to call it.
would some one be able to put together s CWM .zip for us to save alot of the same posts?

C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
0123456789ABCDEF device
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
0123456789ABCDEF device
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push recovery-ra-i
conia-3.13-gnm.img /sdcard
1665 KB/s (5001216 bytes in 2.932s)
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
[email protected]:/ # su
su
[email protected]:/ # su
su
[email protected]:/ # dd if=/sdcard/recovery-ra-iconia-3.13-gnm.img of=/dev/block/mmc
blk0p1
a-3.13-gnm.img of=/dev/block/mmcblk0p1 <
/sdcard/recovery-ra-iconia-3.13-gnm.img: cannot open for read: Not a directory
1|[email protected]:/ # sync
sync
[email protected]:/ # sudo
sudo
sh: sudo: not found
127|[email protected]:/ # su
su
[email protected]:/ # exit
exit
[email protected]:/ # ^C
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
[email protected]:/ # su
su
[email protected]:/ # itsmagic
itsmagic
sh: itsmagic: not found
127|[email protected]:/ # ^C
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
0123456789ABCDEF device
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb push recovery-ra-i
conia-3.13-gnm.img /sdcard
1932 KB/s (5001216 bytes in 2.527s)
C:\Program Files (x86)\Android\android-sdk\platform-tools>adb shell
[email protected]:/ # su
su
[email protected]:/ # dd if=/sdcard/recovery-ra-iconia-3.13-gnm.img of=/dev/block/mmc
blk0p1
a-3.13-gnm.img of=/dev/block/mmcblk0p1 <
/sdcard/recovery-ra-iconia-3.13-gnm.img: cannot open for read: Not a directory
1|[email protected]:/ #
this is what i get. not a directory? Does thor's ICS have something set up differently? I'd love to get a legit recovery up in here. Thanks.
---------- Post added at 11:56 AM ---------- Previous post was at 11:43 AM ----------
just for anyone looking in, joe9002 for example, I followed the steps from here to find out you have to run the second set of command in the terminal on the tablet. much easier with a usb keyboard, i might add. got it installed and running nicely. it ain't pretty, but the touch does work. I guess i was expecting more like TWRP with big icons, but not having to use the way too recessed volume buttons is awesome. thanks guys!!!!!

please provide a flashable zip....lazy kid)

easy install
i have used acer recovery installer
http://forum.xda-developers.com/showthread.php?t=1226191

josinpaul said:
please provide a flashable zip....lazy kid)
Click to expand...
Click to collapse
+1, would someone please do a cwm flashable zip for this ?
Thank a million
Sent from my A500 using Tapatalk

If This is a .img. put on your sd card at the same place as the cwm thors recovery .. Acer Recovery installer should See and Install this.. Or am i missing something..
DO NOT TRY JUST BECAUSE I AM ASKING THIS.. But sounds logical.

I just created and tested a CWM flashable file of this image. There's one in the attachment of this post, or you can download it HERE

erica_renee said:
If This is a .img. put on your sd card at the same place as the cwm thors recovery .. Acer Recovery installer should See and Install this.. Or am i missing something..
DO NOT TRY JUST BECAUSE I AM ASKING THIS.. But sounds logical.
Click to expand...
Click to collapse
NOT logical at all!
You need a script run to install it. See post above!!!!

kjy2010 said:
I just created and tested a CWM flashable file of this image. There's one in the attachment of this post, or you can download it HERE
Click to expand...
Click to collapse
You rock! Thanks a ton, as I don't do ADB since I have too many Android devices in this house, and every time I get one connected to my desktop it breaks the connection of the others.
Now, am I reading correctly that we have to manually run itsmagic with this or does it automatically do it? I think I speak for more than just myself when I say I have no idea how or even when to do this.
Has anyone done a successful recover?

internetpilot said:
You rock! Thanks a ton, as I don't do ADB since I have too many Android devices in this house, and every time I get one connected to my desktop it breaks the connection of the others.
Now, am I reading correctly that we have to manually run itsmagic with this or does it automatically do it? I think I speak for more than just myself when I say I have no idea how or even when to do this.
Has anyone done a successful recover?
Click to expand...
Click to collapse
If I read it correctly, you needed to run It's Magic to install it, then the Recovery ran it on it's own, as there's no way to manually run it's magic from recovery, but that's a moot point as I created the flashable zip to install it

kjy2010 said:
If I read it correctly, you needed to run It's Magic to install it, then the Recovery ran it on it's own, as there's no way to manually run it's magic from recovery, but that's a moot point as I created the flashable zip to install it
Click to expand...
Click to collapse
Oops...see that now in the OP. Thanks. Sorry, the running itsmagic as part of the install process through me for a loop. I know that I've seen Thor's CWM recovery automatically loading it, and I was worried that with this recovery we'd have to do it manually.
Alright. Maybe I'll be the guinea pig and try a restore.

kjy2010 said:
If I read it correctly, you needed to run It's Magic to install it, then the Recovery ran it on it's own, as there's no way to manually run it's magic from recovery, but that's a moot point as I created the flashable zip to install it
Click to expand...
Click to collapse
Yes itsmagic is needed to call the bootloader re-write of partition checksums. Itsmagic is executed in both my recovery and thor's on boot. To call it manually in either recovery which is not needed as its already done you would do either "itsmagic" from adb shell in recovery or from updater-script run_program("/sbin/itsmagic"); or call it in a script in a flashable zip.
internetpilot said:
Alright. Maybe I'll be the guinea pig and try a restore.
Click to expand...
Click to collapse
It works I developed and tested this on my own a500 I just got a few days ago. The beta restore CWM backup option only works for a true sdcard not the usb_drive. The amon ra backup & restore options will work with both usb_drive and sdcard fyi.

drellisdee said:
Yes itsmagic is needed to call the bootloader re-write of partition checksums. Itsmagic is executed in both my recovery and thor's on boot. To call it manually in either recovery which is not needed as its already done you would do either "itsmagic" from adb shell in recovery or from updater-script run_program("/sbin/itsmagic"); or call it in a script in a flashable zip.
It works I developed and tested this on my own a500 I just got a few days ago. The beta restore CWM backup option only works for a true sdcard not the usb_drive. The amon ra backup & restore options will work with both usb_drive and sdcard fyi.
Click to expand...
Click to collapse
Thanks again dell! We needed an alternative to the GPL non-compliant CWM that we had!
Your work is GREATLY appreciated and the touch screen is an added bonus!

Very nice addition to the A500, thanks for the hard work.

[Guide][NOOB-Friendly] How to share your Nandroid Backup and Modem

As we are having a lot of Jelly Bean leaks lately, a lot of users want to share the Nandroid backup to others but sometimes they make mistakes which ends up in md5 mismatches or some of them don't know how to create a share-able zip.
I have tried to create this guide to enable them in doing so. Hope this will help everyone.
Requirement:
CWM Recovery
7zip, Winrar or any file compressing tool
ADB setup in your PC
Click to expand...
Click to collapse
Once you have applied the OTA and done a factory reset, Follow the process given below:-
If your have ClockworkMod Touch Recovery 6.0.1.2 (Believe me it is easier and better in Touch recovery - Get it from here) follow these:-
In CWM Recovery
Reboot into Recovery => Hold Volume Up + Home + Power buttons together for about 5-7 seconds, release the buttons when you see the recovery menu
Choose -> Backup and Restore
Chooose -> Choose Backup Format (Optional)
Change Backup format to tar (Optional)
Choose -> Create image.zip
This will create an image.zip and an image folder in your Internal Sdcard inside the clockworkmod>backup folder
Copy the image.zip file to your PC, rename it to the software version you are sharing for e.g. GT-I9300-XXXXXXXX. Important do not put spaces in the name.
Upload this zip to whichever Filehosting site you want to share with.
*this image.zip can be flashed in CWM directly without having the need to extract the files inside*
Click to expand...
Click to collapse
If you have ClockworkMod Recovery 5.5 (Get it from here) Follow these:-
In CWM Recovery
Reboot into Recovery => Hold Volume Up + Home + Power buttons together for about 5-7 seconds, release the buttons when you see the recovery menu
Choose -> Backup and Restore
Choose -> Backup (either Internal or External SDcard by default it will backup to ExtSDcar)
Your Backup will now be there inside the clockworkmod>backup folder, Copy this folder to your PC
Zip the Folder and give it a name for e.g. GT-I9300-XXXXXX (Dont use spaces)
Now you can upload this zip to any filehosting service of your choice
Click to expand...
Click to collapse
How to extract the modem:-
For extracting the modem you need to be rooted (If you are not or want to know how go here)
Using ADB (Go here if you want to know how to set up ADB)
Connect your phone to you PC (Please ensure that ADB debugging option is checked in Developer Options)
Type
Code:
adb devices
You will get something like this:
Code:
List of devices attached
XXXXXXXXXXXXXX device
It shows your device is connected via ADB
Type
Code:
adb shell
You will get a output like this:
Code:
C:\adb>adb shell
[email protected]:/ $
Type
Code:
su
You will get:
Code:
su
[email protected]:/ #
(Those who are using Terminal Emulator can start from this step)
Type
Code:
dd if=/dev/block/mmcblk0p7 of=/sdcard/modem.bin bs=4096
You will get
Code:
[email protected]:/ # dd if=/dev/block/mmcblk0p7 of=/sdcard/modem.bin bs=4096
dd if=/dev/block/mmcblk0p7 of=/sdcard/modem.bin bs=4096
8192+0 records in
8192+0 records out
33554432 bytes transferred in 2.892 secs (11602500 bytes/sec)
[email protected]:/ #
Your modem.bin file is copied to the root of your sdcard, copy it to your PC and upload it to the file hosting site of your choice
Click to expand...
Click to collapse
I have tried to write everything to the best of my knowledge. If anyone feels that I have missed something or I have written something wrong please let me know. I will make the changes.

Thanx for this very useful
Sent from my GT-I9300 using Tapatalk 2

anurag549 said:
Thanx for this very useful
Sent from my GT-I9300 using Tapatalk 2
Click to expand...
Click to collapse
will be helpful for many ... nice work buddy

Q: When I dump modem I get a modem.bin and its ~30mb, while shipped modems in stock fw is ~12mb, why is this?

Perka said:
Q: When I dump modem I get a modem.bin and its ~30mb, while shipped modems in stock fw is ~12mb, why is this?
Click to expand...
Click to collapse
Well that escapes me..may be someone knowledgeable can shed some light on it..
Sorry..
Maybe the that provided with the firmware is a patch..I know OTA files are patches but can't say much about full firmwares..

I'm trying to do this using the terminal emulator in Rom toolbox and u keep getting permission denied?
(from what I understood we had two ways of doing this correct? A computer and adb or TE, correct?)

Danielhammons1 said:
I'm trying to do this using the terminal emulator in Rom toolbox and u keep getting permission denied?
(from what I understood we had two ways of doing this correct? A computer and adb or TE, correct?)
Click to expand...
Click to collapse
You have to type su in terminal to gain root access. It's just like a standard Linux terminal.

[HOW-TO] Lenovo IdeaTab A1000 Rooting

HOW TO ROOT YOUR LENOVO IDEATAB A1000​
<DISCLAIMER>​
By attempting these steps, your warranty will be void. Even worse than that, it might cause crashes, freezes, random explosions, 2nd degree burns, or even turn your beloved tab into $100+ paperweight. What works on mine might not work on yours, so don't attempt if you don't know what you're doing. Do at your own risk. Corrections are welcome. I must admit that I'm not an expert, so any info I posted might be wrong, and I can't offer you much help. I'm not responsible for anything arising from the use of this how-to. I can only wish you good luck.
<WHY ROOT?>​
- Without root or OTA upgrades (at time of writing, Indonesian customers still can't get it), you'll be stuck with ~500MB internal memory. That's annoying.
- You're stuck with the default IO scheduler (cfq) and governor (hybrid, haven't heard that one..)
- You have an incredibly large amount of bloatware you can't get rid of, in that already cramped up internal storage
- Did I mention freedom?
<REQUIREMENTS>​
This method is originally used to root Acer Iconia B1-A71. Somehow I noticed that the two actually has the same chipset, MTK8317 (if it really was relevant ). So I tried the method, and through sheer n00b's luck, it worked like a charm!
Lenovo IdeaPad A1000-G --> 4GB storage, 2G/EDGE. This method haven't been tested on A1000-T/F, different storage cap (16GB, etc.) or other variants, but it should work with slight modification. Screenshots of my specs are attached below. Remember, proceed at your own risk!
A Linux System. Never tried on Windows or Mac. I personally used Linux Mint 15. The source post uses Ubuntu.
working ADB (android-tools-adb). You can get this from synaptics, apt-get, etc. If your system can detect adb devices, you should be fine.
Superuser Binary
Busybox Binary (You can get these two from the links on original post. XDA says noobs can't post links :'( )
ORIGINAL THREAD
<CREDITS>​
XDA Senior Member entonjackson, for writing such a noob-friendly how-to for rooting Acer Iconia B1-A71 and for allowing me to use it for this how-to.
XDA Member alba81, for discovering the method as acknowledged on the original post by entonjackson
All awesome gurus on XDA which I can't mention one by one.
<THE STEPS>​
1. Extract the android sdk to your home folder, e.g. a user named Bob will use like /home/bob
2. Open a terminal
3. Now plug your A1000 into your machine and turn on Debugging Mode (Go into Settings -> Developer Tools, turn on Developer tools, then turn on USB Debugging Mode)
4. Now back at the keyboard of your Linux machine in your terminal type:
Code:
sudo adb devices
The output should be something like:
Code:
123456789ABCDEF device
If it's not, google for it. Somehow your Linux hasn't detected the A1000, although the android sdk for Linux brings all needed drivers with it.
If your device was found, congratulations. The adb connection between your linux machine and your tablet is intact.
5. Now extract the downloaded busybox archive to your home folder, in it there should be a busybox binary. So Bob does:
Code:
sudo ./adb push /home/bob/busybox /data/local/tmp
Code:
sudo ./adb shell
Code:
chmod 755 /data/local/tmp/busybox
6. You should copy the busybox binary into a directory where you can access it as a plain non-root user on the tablet. We need this binary. so we can apply unix tools like telnet, dd, cat, etc. But for now we need it to establish a telnet session between our tablet and our linux machine.
(This point is written on original post. Seems important, but as soon as I finished step 5, I can use those tools)
7. Dial *#*#3646633#*#* to enter Engineer Mode
8. Go to Connectivity -> CDS Information -> Network Utility
9. type the following command:
Code:
/data/local/tmp/busybox telnetd -l /system/bin/sh -p 1234
Advice from original poster: copy and paste it from the browser on your tablet, because dependent on which keyboard app installed, this can be freakin tricky. In the next step you will learn, why it's so important why this command should be correct.
10. Tap on Run. You won't get any feedback, so you will never know if the entered command runs properly or not. That's why you should make sure the command is ok.
Now we have started our telnet server on the tablet.
11. Back in the terminal type:
Code:
/data/local/tmp/busybox telnet 127.0.0.1 1234
If you now get an error like couldn't find busybox or something, then either adb push failed or you forgot to chmod, in step 5
12. Now enter:
Code:
cat /proc/dumchar_info
You should get a bunch of lines, try to find a line containing the partition named android
{..... partition list .....}
android 0x0000000028A00000 0x00000000020E8000 2 /dev/block/mmcblk0p3
{..... partition list .....}
13. We will create a dump of our android system. This is the point where different variants *MIGHT* have different parameters. This step is important, as wrong parameter will result in unmountable image.
Stop. Take a deep breath. If you're not familiar with dd, find a good doc of it. There's a plethora of them.
Get yourself a programmer's calculator (Linux Mint 15 has one built in).
Here's what you'll do :
Convert the hex number on the 3rd column into decimal. In my case (0x20E8000) will yield 34504704. Divide by 4096. The result (8424) goes to the skip parameter.
Convert the hex number on the 2nd column. In my case (0x28A00000) will yield 681574400. Divide by 4096. The result (166400) goes to the count parameter.
So the full dd command will look like :
Code:
dd if=/dev/block/mmcblk0 bs=4096 skip=8424 count=166400 | gzip > /cache/system.img.gz
Do a full sanity check before hitting enter! It will take about 5 minutes.
14. After it's finished we must make the image readable for adb, so we do:
Code:
chmod 777 /cache
and
Code:
chmod 777 /cache/system.img.gz
15. Leave the telnet, and then adb shell session by:
Code:
exit
Code:
exit
16. Now we pull our image by
Code:
sudo adb pull /cache/system.img.gz
wait 1-2 minutes.
It should be then located inside /home/bob. It did for me. If not, do a search . It should be a .gz, extract it right there (or /home/bob if it isn't there)
17. Now we need to modify our system image by adding the tiny but helpful su binary. Extract the SU binary to /home/bob.
18. We create a folder where we will mount our system image to. To create it do:
Code:
sudo mkdir /media/a1000
19. Now we mount it:
Code:
sudo mount -o loop /home/bob/system.img /media/a1000
if it fails, then you entered wrong parameters on step 13
20. Now we copy our SU binary to our mounted system image:
Code:
sudo cp /home/bob/su /media/a1000/bin
21. the su binary needs to have the proper rights to make it usable, so we 'suid' it with:
Code:
sudo chmod 06755 /media/a1000/bin/su
22. Let's unmount our baby by:
Code:
sudo umount /media/a1000
and because bob doesn't like a messed up system, he does:
Code:
sudo rm -rf /media/a1000
because he hopefully won't need it anymore.
23. We have to gzip it again to bring it back to where it belongs to. this we do by:
Code:
cd /home/bob
Code:
gzip /home/bob/system.img
24. So here we are now, we made it to the final Boss fight! The next steps are dangerous and should be performed with caution. We copy back our modified system image, which can brick your device, if you do a mistake! Enter adb shell again :
Code:
sudo adb shell
25. Remove the old boring image:
Code:
rm /cache/system.img.gz
26. Leave adb shell
Code:
exit
27. copy our cool new system image containing the su binary:
Code:
sudo adb push /home/bob/system.img.gz /cache
28. Enter adb shell again
Code:
sudo adb shell
29. Usually the telnet server on the tablet is still running, at least in my case it's been like that. That's why we can directly connect to the telnet server with:
Code:
/data/local/tmp/busybox telnet 127.0.0.1 1234
If this doesn't work, then obviously your telnet server isn't running anymore. So on your tablet if the telnet command is still entered (see step 9), tap on Run again and repeat step 29.
30. Now this is the most dangerous step in this how to (no it wasn't the mkdir one). You can copy following command to make sure everything is fine and paste it into your telnet session on your linux terminal.
<WARNING! SANITY CHECK! MAKE SURE *ALL* THE DD PARAMETERS MATCH THE FIRST DD (STEP 13) OR YOUR A1000 WILL TURN INTO A VERY EXPENSIVE PAPERWEIGHT!>
Code:
[B]/data/local/tmp/busybox zcat /cache/system.img.gz | dd of=/dev/block/mmcblk0 bs=4096 seek=8424 count=166400[/B]
After 1-2 minutes you're done, if your tablet or pc or yourself didn't catch fire, everything's fine.
31. Leave telnet / adb shell by doing
Code:
exit
Code:
exit
32. Reboot your A1000 via ADB, then exit
Code:
sudo adb reboot
Code:
exit
33. Unplug your tablet from PC
34. Install Superuser (No, not SuperSU, cause it won't work!). I personally use Superuser by ChainsDD, from Play Store
35. Be lucky. Your tablet and thus you are now free!
Don't forget to hit thanks, if this helps ​

hi, after step 13 (i double checked the command), i get this error
Code:
/system/bin/sh: can't create /cache/system.img.gz: Permission denied
/dev/block/mmcblk0: cannot open for read: Permission denied
I have the WiFi 4G version

Im too stuck in step 13.....nothing wrong with the script, can u give me a solution?
Im using A1000G also

@ts
Your guide work perfectl, in windows enviroment but mount step still need linux,
I've question are you using DirectoryBinding? Mine always close when playing Real Racing, its very annoying
You have suggeztion or alternative for DirectoryBinding?

Root with Windows ?
Hi,
I am a new member because i bought this tblet but i can't root. I don't have a linux environment, so there is a solution with W8 Pro 64 ?
Thanks a lot for you help,

ulisez said:
hi, after step 13 (i double checked the command), i get this error
Code:
/system/bin/sh: can't create /cache/system.img.gz: Permission denied
/dev/block/mmcblk0: cannot open for read: Permission denied
I have the WiFi 4G version
Click to expand...
Click to collapse
have you chmod-ed the busybox (or is the chmod successful without error)? Try chmod-ing the /cache before attempting step 13. It seems that you still don't have access to the NAND device (mmcblk0). Have you updated firmware via OTA?
artonelico said:
Im too stuck in step 13.....nothing wrong with the script, can u give me a solution?
Im using A1000G also
Click to expand...
Click to collapse
Do you encounter the same error message like ulisez had? Could you post the screenshot of the partition list (the lines after you execute dumchar_info)?
rmage said:
@ts
Your guide work perfectl, in windows enviroment but mount step still need linux,
I've question are you using DirectoryBinding? Mine always close when playing Real Racing, its very annoying
You have suggeztion or alternative for DirectoryBinding?
Click to expand...
Click to collapse
I personally use Link2SD by Bulent Akpinar to link apps to 2nd partition on my SDcard.
Letsar said:
Hi,
I am a new member because i bought this tblet but i can't root. I don't have a linux environment, so there is a solution with W8 Pro 64 ?
Thanks a lot for you help,
Click to expand...
Click to collapse
The original developer who posted the method (entonjackson) plans to integrate the method in the next release his toolkit, the Acer Iconia Toolkit. I think you should check his thread : http://forum.xda-developers.com/showthread.php?t=2240029

sammymaddog said:
have you chmod-ed the busybox (or is the chmod successful without error)? Try chmod-ing the /cache before attempting step 13. It seems that you still don't have access to the NAND device (mmcblk0). Have you updated firmware via OTA?
Do you encounter the same error message like ulisez had? Could you post the screenshot of the partition list (the lines after you execute dumchar_info)?
I personally use Link2SD by Bulent Akpinar to link apps to 2nd partition on my SDcard.
The original developer who posted the method (entonjackson) plans to integrate the method in the next release his toolkit, the Acer Iconia Toolkit. I think you should check his thread : http://forum.xda-developers.com/showthread.php?t=2240029
Click to expand...
Click to collapse
Link2SD doesn't link app data, do you have any option?

yes i had same message with ulyses, by the way im from indonesia too can i contact you through chat client?
oh yeah im using windows 7 and using cmd as a terminal in linux
thx before bro

sammymaddog said:
The original developer who posted the method (entonjackson) plans to integrate the method in the next release his toolkit, the Acer Iconia Toolkit. I think you should check his thread : http://forum.xda-developers.com/showthread.php?t=2240029
Click to expand...
Click to collapse
Ok, i see his toolkit. It's very good. I'll wait

rmage said:
Link2SD doesn't link app data, do you have any option?
Click to expand...
Click to collapse
I'm not sure whether the stock kernel of our devices supports init.d, thus supports CronMod/Data2SD. Lenovo locked our bootloader, and currently there's no way around it. So I personally think, Link2SD method are the best option for now.
Let's give it several months until our dev gurus bring their miracles upon this device

The attached image shows mt6577 Hardware, can u provide the Soc details please

Hi, Can any one upload Lenovo ideatab A1000 system.img

in step 20, it appears you are writing to a /bin directory on the android system. However such a directory is not visible either through shell or the system telnet account.
Do I need to understand something else about android to make sense of this.
regards
vidya

one month gone past but the op seems to be in caves or has bricked the device

STOCK ROM
CAN ANY BODY PROVIDE ME A STOCK ROM OF THIS DEVISE
I HV ROOTED SUCCESSFULLY BY A VERY EASY METHOD
BUT SCREWED UP WHILE UPDATING IT SO PLZ PLZ HELP ME OUT
THE DEVICE BOOTS BUT ALL THE APP CRASHES :crying::crying:

VR.gtmini said:
The attached image shows mt6577 Hardware, can u provide the Soc details please
Click to expand...
Click to collapse
VR.gtmini said:
one month gone past but the op seems to be in caves or has bricked the device
Click to expand...
Click to collapse
sorry to make you wait. I'm a last grader university student, and final project stuffs have got me pinned down. Hope you understand
Actually the SoC is MT8317. For some god-knows reason Mediatek have made this SoC with signatures similar to MT6577. But somehow CPU tweaker correctly detects the SoC (MT8317). Maybe it's the CPU-Z bug?
unknown_world said:
Hi, Can any one upload Lenovo ideatab A1000 system.img
Click to expand...
Click to collapse
zod0070 said:
CAN ANY BODY PROVIDE ME A STOCK ROM OF THIS DEVISE
I HV ROOTED SUCCESSFULLY BY A VERY EASY METHOD
BUT SCREWED UP WHILE UPDATING IT SO PLZ PLZ HELP ME OUT
THE DEVICE BOOTS BUT ALL THE APP CRASHES :crying::crying:
Click to expand...
Click to collapse
I'm uploading the modified .img. Let's pray my old HSPA modem won't catch fire by the morning.
vidyadhara said:
in step 20, it appears you are writing to a /bin directory on the android system. However such a directory is not visible either through shell or the system telnet account.
Do I need to understand something else about android to make sense of this.
regards
vidya
Click to expand...
Click to collapse
I think you got it wrong. The write process does not take place on the device. It's on the loop-mounted .img in /mnt/a1000 on your computer (step 18-19). Cheers!

Here's the ALREADY BUSYBOX-ED .img for Ideapad A1000-G 4GB EDGE version. Hope it helps :
www dropbox com/s/rmpnz7c285t5sqz/system.7z

sammymaddog said:
Here's the ALREADY BUSYBOX-ED .img for Ideapad A1000-G 4GB EDGE version. Hope it helps :
www.dropbox.com/s/rmpnz7c285t5sqz/system.7z
Click to expand...
Click to collapse
Thanks for coming back, could u post the MD5 of the system.7z & system.zip.
Also could u provide simple way/steps to directly flash this .img without extracting existing stock system image
My tab A1000-G

do you have stockROM for lenovo A1000G
I need this :crying:

raffly said:
do you have stockROM for lenovo A1000G
I need this :crying:
Click to expand...
Click to collapse
Don't worry, the above link is a stock Lenovo A1000 G ROM, but with pre-root files having no superuser app. Just extract the .7z file
System.7z MD5: 658CA71AC8A230B244F267513857F9A5

How to manually upgrade/downgrade your Amazon FireTV

-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Update 02/03/2015
This guide I posted is well out of date, there are other methods to follow now days.
Please use http://www.aftvnews.com/tag/guide/ as it is up to date and current.
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Thanks to AFTVNews.com for the OTA link and rbox for pointing me in the right direction I've successfully manually upgraded to the latest firmware, downgraded back to 51.1.0.2 and am now upgrading back to 51.1.1.0.
This is the process I followed. I take it for granted that you rooted, have SU and Busybox free installed.
Don't blame me if you **** your device up and you have a brick.
So lets get to it:
1. Download which ever firmware you wish to restore to:
Code:
51.1.0.1
http://amzdigitaldownloads.edgesuite.net/obfuscated/e6f65fefb36aaf7b94fd370f516b9c11/bueller-ota-51.1.0.1_user_510055620-signed.bin
51.1.0.2
http://amzdigitaldownloads.edgesuite.net/obfuscated/cec02756d1964c9cb1f71d52056cc81a/bueller-ota-51.1.0.2_user_510058520-signed.bin
51.1.1.0
http://amzdigitaldownloads.edgesuite.net/obfuscated/568eef32595f034b4304e19aa566befb/bueller-ota-51.1.1.0_user_511069920-signed.bin
51.1.1.0 Update 1
http://amzdigitaldownloads.edgesuite.net/obfuscated/4edaba705e98dee475680c33d3f41132/bueller-ota-51.1.1.0_user_511070220-signed.bin
2. Rename which ever one you wish to restore to update.zip
3. adb shell
4. su
5. chmod 777 cache
6. cd cache
7. chmod 777 recovery
8. cd recovery
9. echo --update_package=/cache/update.zip > command
10. ctrl + c
11. adb push update.zip /cache
--- Go make coffee or take a ****....The pushing of 466MB takes forever over wireless.---
An alternative is to copy update.zip to a USB Flash Drive, use StickMount to mount on the FireTV then copy it with the following command:
cp /sdcard/usbStorage/sda1/update.zip /cache
12. adb reboot recovery
Now it should reboot and start installing whatever update you downloaded and called update.zip :good:
If you get the out of space error:
roligov said:
No it's not because the updates are blocked, it's because you out of space in your cache partition. ADB shell to the box and run
ll /cache
If you have any bin files, delete them.
Click to expand...
Click to collapse
1. adb shell
2. su
3. rm /cache/*.bin

Nice

Nice work and great news! No reason not to update to the latest version since we can downgrade too.

Thanks. Should we delete the file after the update to save on the space or is it automatically deleted?

It automatically gets deleted. It's late this side so I'm going to bed.
Will do some testing tomorrow before I give the go ahead and tell everyone it's all working!

Wow!! I knew someone would figure it out, just did not think it would be this soon. Thank you for the work!!
One step closer to an unlocked bootloader...

Super guide, worked like a charm - thank you!

Good work! Thank-you.

zahir32 said:
Super guide, worked like a charm - thank you!
Click to expand...
Click to collapse
would there be a way to do this via shh

you should probably make a mirror of those firmware bundles. :good:

wavrunrx said:
you should probably make a mirror of those firmware bundles. :good:
Click to expand...
Click to collapse
Good point. I'll dl them tonight and leave them on my NAS. Eventually i"ll put them on dropbox or other filelocker for safekeeping

Getting It Done
bdscds said:
would there be a way to do this via shh
Click to expand...
Click to collapse
This method gets it done. I've tried others, but these instructions - and the fact that the OP has kindly prepared the "command" file for us - make it an easy ride. Just put the update zip in the same folder as your ADB setup, open your command window in that folder and adb will find it.

Thanks!
With this we can safely update to latest version!

Nice guide
Sent from my iPhone using Tapatalk

Can this be done over a local network or do I have to hook the Fire TV up to my PC using a USB (Male to Male) lead?

gazdaman. said:
Can this be done over a local network or do I have to hook the Fire TV up to my PC using a USB (Male to Male) lead?
Click to expand...
Click to collapse
http://www.firetvnews.com/how-to-sideload-apps-to-your-amazon-fire-tv-using-a-windows-pc/
network
shows you how to use adb, so you can do "adb shell"
be careful though, if you were to mess anything up in the process you could render your fire tv useless.

roligov said:
Thanks to FireTVNews.com for the OTA link and rbox for pointing me in the right direction I've successfully manually upgraded to the latest firmware, downgraded back to 51.1.0.2 and am now upgrading back to 51.1.1.0.
This is the process I followed. I take it for granted that you rooted, have SU and Busybox free installed.
Don't blame me if you **** your device up and you have a brick.
So lets get to it:
1. Download which ever firmware you wish to restore to:
Code:
51.1.0.1 update
http://amzdigitaldownloads.edgesuite.net/obfuscated/e6f65fefb36aaf7b94fd370f516b9c11/bueller-ota-51.1.0.1_user_510055620-signed.bin
51.1.0.2 update
http://amzdigitaldownloads.edgesuite.net/obfuscated/cec02756d1964c9cb1f71d52056cc81a/bueller-ota-51.1.0.2_user_510058520-signed.bin
51.1.1.0 update
http://amzdigitaldownloads.edgesuite.net/obfuscated/568eef32595f034b4304e19aa566befb/bueller-ota-51.1.1.0_user_511069920-signed.bin
2. Rename which ever one you wish to restore to update.zip
3. adb shell
4. su
5. chmod 777 cache
6. cd cache
7. chmod 777 recovery
8. cd recovery
9. wget http://dl.dropboxusercontent.com/u/16913146/command
10. ctrl + c
11. adb push update.zip /cache
--- Go make coffee or take a ****....The pushing of 466MB takes forever.---
12. adb reboot recovery
Now it should reboot and start installing whatever update you downloaded and called update.zip :good:
Click to expand...
Click to collapse
Thanks for the info! I hear the new update offers nothing new and causes more problems than good by disrupting the alphametical order of sideloaded apps. Is it worth updating for or will there be no significant differences? It's funny because amazon.com don't mention a new update release.
Also does you update method require you to re-root the device or does root survive the update? Thanks very much!

Got it working with Windows 7
This is how I done it.
(Ensure you have ADB installed - If not google "ADB setup 1.3 windows")
Download the chosen firmware and rename it to update.zip
Download roligov's command file
remove the .txt extension that windows gives it when you download it. The filename should just be "command" with no extension otherwise you will get the failed message when you reboot to recovery.
Now run command prompt as Administrator
(I will use C:\ as the file location example)
adb kill-server
adb start-server
adb connect "Fire TV IP Address"
adb shell
su
chmod 777 cache
cd cache
chmod 777 recovery
ctrl + c
adb push C:\command /cache/recovery
adb push C:\update.zip /cache
--- Go make coffee or take a ****....The pushing of 466MB takes forever.--- (Took 2 minutes over LAN for me)
adb reboot recovery
Done
Many thanks to roligov for the initial find to set me on my way.

Yeah my FireTV is hooked up to my Wireless so it takes forever to push the update.

roligov said:
Yeah my FireTV is hooked up to my Wireless so it takes forever to push the update.
Click to expand...
Click to collapse
if one has a usb thumb drive and stick mount installed, copying the .bin to the /cache folder step might be faster?
User copies .bin file(s) and command file to a folder on thumb drive where a script file which lists .bins in thumbdrive folder and allows user to choose a numeral and then executes commands for update process would be cool for newbies. even having the script "autocreate" the command file.

[ROOT Update] 5.3.0.1 to 5.0.4 (3 min method)

This guide assumes you are already rooted on 5.0.3.1 (this will work for future updates as well if @zeroepoch push out new rooted images) I will just need to update the hash check accordingly
Now before I go any further **this can brick your device** so you assume all risk associated with this method.
I have tested this on 2 of my AFTV2 devices no less than 50 times so it was safe for me. There are factors that cant be accounted for such as bad blocks on the nand. I have put in a lot of checks into this script to go off without a hitch. If something doesn't match up the script will tell you and drop you back to terminal. The safest method to date is using @zeroepoch diff and waiting 2 hours.
Or wait until someone like @rbox comes up with a custom recovery solution.
This method came down to necessity for me as I wasn't getting the 5.0.4 update (waited a week on each of my devices)
Plus I cant stand waiting around for 2 hours. @xenoglyph started this off by being the first to use the dd method and after seeing his success I figured I would automate the process because some users bricked their device because of a simple mistake (failing to unpack the .gz for the images).
I have only tested this over USB (use over network at your own risk but if you happen to please report back if it works)
How to:
All-in-One package - https://mega.nz/#!1YJXDbJa!jzy1g78qIUdsRwY4Pzw2yLLyH9pB2uo9imDaskbotY0
Mega decryption key - !jzy1g78qIUdsRwY4Pzw2yLLyH9pB2uo9imDaskbotY0
Script only package is below (you will need to download and decompress all images)
MicroSD Method:
1. Extract the .zip to a microSD card and place the card in the AFTV
2. Plug in your USB A to A cable
3. Turn on USB Debugging
4. Make sure your system sees the AFTV (adb devices) (or over wifi/wired adb connect 192.168.1.xxx -=tested see post #7 & #28=-)
5. Open adb shell (adb shell)
6. Enter the commands one at a time below
Code:
su
cd /storage/sdcard1
chmod 775 root.sh
sh ./root.sh
The device will reboot when finished (if for some reason it doesn't reboot on its own and drops you the terminal after the 60 second message, you can just pull the plug)
Internal Storage Method:
1. Extract 5.3.0.1-5.0.4-local-script.zip and adb push it to /data/local/tmp (this is the script, busybox, and verify.md5 only) you have to push images (see below)
2. Plug in your USB A to A cable
3. Turn on USB Debugging
4. Make sure your system sees the AFTV (adb devices) (or over wifi/wired adb connect 192.168.1.xxx -=tested see post #7 & #28=-)
5. Open adb shell (adb shell)
6. Enter the commands one at a time below
Code:
su
cd /data/local/tmp
chmod 775 root.sh
sh ./root.sh
The device will reboot when finished (At the moment reboot and busybox reboot aren't working. The script will give you a message when to reboot at the end)
After the device reboots disable OTA again just to be on the safe side:
Code:
adb shell
su
pm disable com.amazon.device.software.ota
I have a class 10 microSD and the process takes exactly 3 mins from the second you run root.sh
If you have a slower card expect it to take up to 5 mins.
If the script is tampered with it will error on the hash check
Here are the hashes for each file:
MicroSD Method md5:
Code:
c230711c59ec66a67229449afbf84291 verify.md5
e7c105e97a797f451c1e6ca7a1d950d6 root.sh
dedf4203ca67fa067dc658c8a1325b4f busybox
Local Storage Method md5:
Code:
ef110ab79458f3263fbdba4492125f48 verify.md5
e40dafa35b7d694f8c13b95446b84a3a root.sh
dedf4203ca67fa067dc658c8a1325b4f busybox
5.0.4 Image md5:
Code:
4cc42c5a4ded1eb4d9529b2aede1dfb7 boot.img
f0b05f68cbcecb96722a4637eb06a8a0 lk.img
53649663ee0fa2f7c434b5acdbfddcda preloader.img
3aa70baba1bbb8b29f7d2fa7428e4e1e recovery.img
57bad37f08489b228ae71fc1246adb53 system.root.img
Images for script only download:
http://download.zeroepoch.com/aftv2/5.0.4/boot.img.gz
http://download.zeroepoch.com/aftv2/5.0.4/lk.img.gz
http://download.zeroepoch.com/aftv2/5.0.4/preloader.img.gz
http://download.zeroepoch.com/aftv2/5.0.4/recovery.img.gz
http://download.zeroepoch.com/aftv2/5.0.4/system.root.img.gz
I will maintain the script until a custom recovery arrives.
Special thanks to @zeroepoch for rooting the AFTV2 and maintaining a git/wiki
Also thanks to everyone else working on the AFTV(2)
@rbox, @ImCoKeMaN, @xenoglyph

Nice, thanks for this guide and script!
I just manually updated and did the 2 hr method last night or I would have done this. It's nice to have a way to do the updates as they happen, thanks for sharing your work

thanks for doin it proper man, been super busy

xenoglyph said:
thanks for doin it proper man, been super busy
Click to expand...
Click to collapse
No problem
Thanks for being the first one to risk bricking with this method!

Thanks @aboshi and @xenoglyph!
aboshi said:
This guide assumes you are already rooted on 5.0.3.1
Click to expand...
Click to collapse
1) Does this script assume anything besides firmware 5.0.3.1 rooted? (see EDIT below)
2) Does it matter that apps may have altered /system after the 5.0.3.1 root? (for instance I have AdAway which edits /system/etc/hosts)
3) You said this takes only 3 minutes to run. Does that mean you can successfully run sync after dd?
4) The Mega link asks for a decryption key to download. Are you making this available only to a select group of people?
EDIT: Noticed that busybox is part of this rooting package. If I already have busybox on the box, should I uninstall that before running this script?

@Patrick_445
The script doesn't need to assume firmware version currently, it will only verify the script, .md5, busybox, and images being used.
Im sure I can put in a verify build prop but I have not done that yet. The only reason that would be needed is if someone downgraded when new FW comes out and that might brick their system and I believe it amazon burns fuses now so you cant downgrade.
I posted the decryption key for Mega. I don't know why it was asking you for one because the whole link includes the key.
It doesn't matter that apps alter anything in /system because its getting overwritten/upgraded anyway.
Yes it runs sync at the very end. As for time running it's really only 2 mins. I added a 60 sec sleep at the end right before the reboot just to be safe.
You do not need to delete busybox if you installed it already. busybox is included to run everything statically from the same dir and it must be present or the script will exit as soon as it does the hash check. I have done it this way because I felt it was safer than just linking.

adb over network
Hi aboshi,
first of all I want to thank you for your script. It makes updating the AFTV2 quite painless.
Otherwise I'd like to report that I did the update using adb over the network (wired) which thankfully worked, but not completely perfect.
When I ran your script in the networked adb shell it did everything as expected up to writing
"Copying system.root.img"
to the screen. Then nothing further seemed to happen. I expected that step to run a little longer, since system.root.img is by far the largest file to be written. But after some minutes, I started to get nervous. I tried to ping my AFTV2, but it wasn't reachable over the network anymore. When I looked at the TV, which is connected to my AFTV2 (different room), I could see, that the AFTV2 had rebooted and it was stuck at the colored amazon logo. I waited for about 20 further minutes, but nothing changed.
Reading about all the brick-stories here, I feared my AFTV2 was dead now. So I gave it a last chance and powercycled my AFTV2. At that second boot, the AFTV made it and after some minutes of "optimizing apps aso." it really came up. I checked the os version and I had 5.04.
So I can only guess what had happened. While writing the system image obviously the network connection got lost and thus the adb shell session terminated. The script probably continued to run, because it managed to write enough of the system image to create a working system. Probably it even ran until the end, since my AFTV2 rebooted by itself. BUT, I can't be sure about it, because I never saw the correspondig lines in my adb shell and the first reboot didn't really work out.
So my conclusion: I wouldn't recommend using the script over the network unless you are a very adventurous person or you have no other possibility. In my case I was to lazy to carry my laptop over to the AFTV2 and to install the USB drivers and adb on it. Also I just hoped the update would work. In the end I did carry my laptop over and repeated the update over USB, just to be sure. This time it worked perfect.
Greets,
Christian

@skyball2
Thank you for testing over network. I knew more than likely something like that would happen and thats why it should be done over USB.
It is due to all system files being overwritten and linking. You might have also noticed when it upgraded from 5.0.3.1 to 5.0.4 that the system black screens in the middle of the copy (but not when overwriting 5.0.4 to 5.0.4). Thankfully the script finished its job and you have a working system.
Im sure it can be done over network for others as a last resort, but I wouldn't do it personally because we have no recovery options at the moment. If anyone else wants to do this over network I HIGHLY suggest that you wait at least 10 mins before you reboot after you lose network connection, and after the reboot I would wait another 10 mins before power cycling again if stuck at the amazon logo. (so in other words UPDATE OVER USB!)

aboshi said:
This guide assumes you are already rooted on 5.0.3.1 (this will work for future updates as well if @zeroepoch push out new rooted images) I will just need to update the hash check accordingly
Now before I go any further **this can brick your device** so you assume all risk associated with this method.
I have tested this on 2 of my AFTV2 devices no less than 50 times so it was safe for me. There are factors that cant be accounted for such as bad blocks on the nand. I have put in a lot of checks into this script to go off without a hitch. If something doesn't match up the script will tell you and drop you back to terminal. The safest method to date is using @zeroepoch diff and waiting 2 hours.
Or wait until someone like @rbox comes up with a custom recovery solution.
This method came down to necessity for me as I wasn't getting the 5.0.4 update (waited a week on each of my devices)
Plus I cant stand waiting around for 2 hours. @xenoglyph started this off by being the first to use the dd method and after seeing his success I figured I would automate the process because some users bricked their device because of a simple mistake (failing to unpack the .gz for the images).
I have only tested this over USB (use over network at your own risk but if you happen to please report back if it works)
How to:
All-in-One package - https://mega.nz/#!5JhhWJjJ!7ziTq93zhvlyPYnZtH1H4xXQBl1yWxQG5zD8Ezn0ldY
Mega decryption key - !7ziTq93zhvlyPYnZtH1H4xXQBl1yWxQG5zD8Ezn0ldY
Script only package is below (you will need to download and decompress all images)
1. Extract the .zip to a microSD card and place the card in the AFTV
2. Plug in your USB A to A cable
3. Turn on USB Debugging
4. Make sure your system sees the AFTV (adb devices) (or over wifi/wired adb connect 192.168.1.xxx -=tested see post #7=-)
5. Open adb shell (adb shell)
6. Enter the commands one at a time below
Code:
su
cd /storage/sdcard1
chmod 775 root.sh
sh ./root.sh
The device will reboot when finished (if for some reason it doesn't reboot on its own and drops you the terminal after the 60 second message, you can reboot manually just type reboot or pull the plug)
I have a class 10 microSD and the process takes exactly 3 mins from the second you run root.sh
If you have a slower card expect it to take up to 5 mins.
If the script is tampered with it will error on the hash check
Here are the hashes for each file:
Code:
c230711c59ec66a67229449afbf84291 verify.md5
e7c105e97a797f451c1e6ca7a1d950d6 root.sh
dedf4203ca67fa067dc658c8a1325b4f busybox
4cc42c5a4ded1eb4d9529b2aede1dfb7 boot.img
f0b05f68cbcecb96722a4637eb06a8a0 lk.img
53649663ee0fa2f7c434b5acdbfddcda preloader.img
3aa70baba1bbb8b29f7d2fa7428e4e1e recovery.img
57bad37f08489b228ae71fc1246adb53 system.root.img
Images for script only download:
http://download.zeroepoch.com/aftv2/5.0.4/boot.img.gz
http://download.zeroepoch.com/aftv2/5.0.4/lk.img.gz
http://download.zeroepoch.com/aftv2/5.0.4/preloader.img.gz
http://download.zeroepoch.com/aftv2/5.0.4/recovery.img.gz
http://download.zeroepoch.com/aftv2/5.0.4/system.root.img.gz
I can modify the the script to use /data/local/tmp
So if you want to push all files to the AFTV over adb because you don't have a microSD card let me know.
I believe @zeroepoch will host this on the git as well. I will maintain the script until a custom recovery arrives.
Special thanks to @zeroepoch for rooting the AFTV2 and maintaining a git/wiki
Also thanks to everyone else working on the AFTV(2)
@rbox, @ImCoKeMaN, @xenoglyph
Click to expand...
Click to collapse
Hello,
when I enter the command: chmod 775 root.sh I get the following error: Unable to open root.sh No such file or directory
any ideas why? I checked that fire tv is connected using adb devices. Also entered adb shell with no problems as well as su, and
cd /storage/sdcard1
thanks
Edit: btw I'm on Windows 7 64 bit. Fire TV 2 shows up in Device Manager as Portable Device

Don't know why you're having an issue with chmod but just do this:
Code:
su
mount -o rw,remount /storage/sdcard1
cd /storage/sdcard1
chmod 775 root.sh
sh ./root.sh

aboshi said:
Don't know why you're having an issue with chmod but just do this:
Code:
su
mount -o rw,remount /storage/sdcard1
cd /storage/sdcard1
chmod 775 root.sh
sh ./root.sh
Click to expand...
Click to collapse
thanks for the reply. Still same error after chmod.... no error when mount -o rw,remount /storage/sdcard1 though just at the chmod command.

dk1keith said:
thanks for the reply. Still same error after chmod.... no error when mount -o rw,remount /storage/sdcard1 though just at the chmod command.
Click to expand...
Click to collapse
Still don't see how you're having an issue but try this and let me know:
Instead of chmod 775 root.sh type this:
chmod 775 ./root.sh
And there's no need to remount sdcard1 because the script will handle that.

aboshi said:
Still don't see how you're having an issue but try this and let me know:
Instead of chmod 775 root.sh type this:
chmod 775 ./root.sh
Click to expand...
Click to collapse
I just looked again at the files on the sdcard and there is no root.sh file. Should I try and download the all in one package again?
the zip file I downloaded doesn't have root.sh in the archive? Or am I downloading the wrong file?

I'll DL the zip right now and look.
*edit*
The zip contains root.sh, verify.md5, and busybox
Make sure your are copying them all to the microsd.
I will now go back and edit my other posts because there is no reason to remount anything for the end user.

aboshi said:
Still don't see how you're having an issue but try this and let me know:
Instead of chmod 775 root.sh type this:
chmod 775 ./root.sh
And there's no need to remount sdcard1 because the script will handle that.
Click to expand...
Click to collapse
I'm being a bone head.....I didn't download the script and unzip it to the sdcard just unzipped the all in one file. I just unzipped the script file and put root.sh on the sdcard

dk1keith said:
I'm being a bone head.....I didn't download the script and unzip it to the sdcard just unzipped the all in one file. I just unzipped the script file and put root.sh on the sdcard
Click to expand...
Click to collapse
I just copied the root.sh from the script file to the sdcard the chmod command worked and I am on 5.0.4
---------- Post added at 06:01 PM ---------- Previous post was at 05:59 PM ----------
aboshi said:
I'll DL the zip right now and look.
*edit*
The zip contains root.sh, verify.md5, and busybox
Make sure your are copying them all to the microsd.
I will now go back and edit my other posts because there is no reason to remount anything for the end user.
Click to expand...
Click to collapse
Yes. Sorry if I wasn't clear. I only downloaded the all-in-one zip file. I didn't download the file with the script in it so the script wasn't on the sdcard. I got it sorted and I am on 5.0.4. Thanks for the help

dk1keith said:
I just copied the root.sh from the script file to the sdcard the chmod command worked and I am on 5.0.4
---------- Post added at 06:01 PM ---------- Previous post was at 05:59 PM ----------
Yes. Sorry if I wasn't clear. I only downloaded the all-in-one zip file. I didn't download the file with the script in it so the script wasn't on the sdcard. I got it sorted and I am on 5.0.4. Thanks for the help
Click to expand...
Click to collapse
The all in one has the script as well.

Everything works perfectly except at the end I got "Reboot not found" I just rebooted manually and after booting the screens displays "optimizing system storage and aplications... this will take 10 min"
Now I am back in business but what is the difference with 5.04 version ?

aboshi said:
The all in one has the script as well.
Click to expand...
Click to collapse
Not sure if my anti virus blocked it but I downloaded the all in one zip twice and I didn't get the script file when I extracted the files to sdcard. I then downloaded the script.zip unzipped it and copied the root.sh to sdcard. In any case I am on 5.0.4 and I really appreciate your help and all your work on this root method.

No you are correct, I am repacking the all in one zip now, it was missing root.sh
I will update the OP with the new link.
*Update*
Ok repacked with root.sh and updated new link on OP