Related
NOTE: For those of you that are looking to root thier Inc and already have the latest 2.2+ OTA released in November, these steps will not work. Changes have been made to the ROM so until a new root application has been developed by the unrEVOked team, I am afraid you are left with a stock phone. Sorry. If new updates come out, I will try to post them here.
NOTE: I have uploaded the 2.1 and 2.2 RUUs to Rapidshare and updated the links.
First, let me say that I did not come up with this nor did I create any of the tools. I am passing all this on in a single thread to let people know how update thier Droid Incredible to the OTA 2.2 and have root access if they have it in any of the following conditions:
1. Stock 2.1 without root or unrEVOked Forever
2. Stock 2.1 with root and no unrEVOked Forever
3. Stock 2.1 with root and unrEVOked Forever
4. Stock 2.2 without root and with unrEVOked Forever
5. Stock 2.2 without root and no unrEVOked Forever
6. Custom ROM with root and S-OFF
7. Getting free WiFi Tethering on 2.2
8. Removing unwanted preloaded applications.
NOTE: This may work with custom ROMs, but I have not verified it.
NOTE: SOME PEOPLE, INCLUDING ME HAVE HAD THE PROBLEM OF BEING STUCK IN HBOOT AFTER LOADING A ROM IMAGE. IF THIS HAPPENS TO YOU AFTER LOADING THE 2.1 OR 2.2 ROM, DO NOT PANIC, JUST REAPPLY THE ROM AND ALL WILL BE FINE. FOR SOME REASON THE ROM DOES NOT LOAD CORRECTLY ON THE FIRST TRY BUT DOES ON THE SECOND.
I am passing this on because I loaded the OTA 2.2 without unrEVOked forever loaded on my phone. What a mess. I tried everything (I thought) to try and downgrade it back to stock 2.1 but with no luck. If you do not know, unrEVOked3 cannot currently root a 2.2 updated Droid Incredable and if you have not used unrEVOked forever, you can not get clockworkmod recovery to reload on the phone. I tried the 2.1 RUU to downgrade, but never could get it to connect to the phone. I then tried to use the 2.1 PB31IMG.zip to load and the HBoot loader would just tell me that it was an older image and not load it. I thought I was hosed until the unrEVOked team breaks the code on the 2.2 HBoot loader until I got pointed in the right direction (sort of).
TNS201 pointed me to the following thread: http://forum.xda-developers.com/showthread.php?t=768295
I gave this a try and still could not downgrade my phone. I searched around and after much trial and error, I was able to put together the correct steps to downgrade my phone and then applied unrEVOked3, unrEVOked forever, the OTA 2.2 update, and then reroot the phone. Anyway, here is what I have come up with:
** NOTE: THIS WILL TOTALY WIPE YOUR PHONE CLEAN!!! BACKUP ANYTHING YOU WANT BACK ON THE PHONE!!! **
Condition 1
1. Go to the following link and follow the instructions: http://forum.xda-developers.com/showthread.php?t=709220 Only do the steps for getting ADB loaded on your computer!
This will get ADB loaded on your computer which you will need when doing customizations to the phone. It will also walk you through rooting your phone and doing a lot of other things. Good thread for us noobs.
2. Download unrEVOked Forever from here: http://unrevoked.com/rootwiki/doku.php/public/forever
3. Copy the file to the root of your sdcard.
4. Reboot your phone into clockworkmod recovery and load the unrEVOked Forever zip file. This will turn S to off and allow unsigned images to be loaded.
When you reboot your phone, you will have a fully rooted and S-OFF stock 2.1 Droid Incredible.
NOTE: If you are having troubles downloading the OTA 2.2 RUU, use this link to download the ROM. Just delete the "_2.2" from the file name and go straight to step 12. http://rapidshare.com/files/418523008/PB31IMG_2.2.zip
To load 2.2, do the following:
5. Download the OTA 2.2 RUU from here: http://rapidshare.com/files/418527589/RUU_Incredible_VERIZON_WWE_3.21.605.1_Radio_2.15.00.07.28_2k4k_NV_1.50_PRL58006_release_1433.exe
6. Connect your phone to your computer and ensure you have USB DEBUG turned on and CHARGE ONLY selected.
7. Run the RUU and update your phone to 2.2. If the RUU updates your phone, go on to step 15. If the RUU will not connect to your phone Go to step 8.
8. Start the RUU.
9. Go to your computers temp directory and locate the folder that contains the file rom.zip.
10. Once you locate this file, copy it to any folder (or your desktop).
11. Rename rom.zip to PB31IMG.zip
12. Copy PB31IMG.zip to the root of your phones sdcard.
13. Reboot your phone into HBoot. HBoot will load and then load PB31IMG.zip. This will take a while, so be patient.
14. Follow the instructions to have HBoot install PB31IMG.zip.
Whether you used the RUU or HBoot and PB31IMG.zip, at this point, you should have 2.2 loaded on your phone, but you will no longer have root. You will have S-OFF.
To regain root access, do the following:
15. Download clockworkmod recovery from here: http://downloads.unrevoked.com/forever/recovery/clockworkmod/PB31IMG.ZIP
16. Download the payload update from here: http://forum.xda-developers.com/attachment.php?attachmentid=388592&d=1282834695
17. Download superuser from here: http://dl.dropbox.com/u/6408470/su-releases/su-2.3.4-ef-signed.zip
18. Copy all three files to the root of the phones sdcard.
19. Reboot your phone into HBoot. HBoot will load and then load PB31IMG.zip.
20. Follow the instructions to have HBoot install PB31IMG.zip. Since the phone is still S-OFF, this will reload clockworkmod recovery on the phone.
21. Boot the phone into recovery and load the two zip files downloaded in steps 16 and 17. This will root the phone and reload superuser.
If all went well, when the phone reboots, it should now be loaded with 2.2 and have full root and S-OFF. Enjoy.
Condition 2
1. Do steps 2 through 21 under Condition 1.
Condition 3
1. Do steps 5 through 21 under Condition 1.
Condition 4
** NOTE: THIS ONE DOES NOT WIPE YOUR PHONE!! **
1. Do steps 15 through 21 under Condition 1.
Condition 5
This is a tuffer one and requires the phone to be downgraded to 2.1 before upgrading it back to 2.2. Anyway, here are the steps:
NOTE: YOU MUST USE THE 2.1 RUU I HAVE LINKED AND THE MTD0.IMG FILE I HAVE ATTACHED OR THIS MAY NOT WORK!!!
NOTE: If you are having troubles downloading the 2.1 RUU, use this link to download the ROM. Just delete the "_2.1" from the file name and go straight to step 5 after completing step 1 and 2 (skip step 3 and 4). http://rapidshare.com/files/418141003/PB31IMG_2.1.zip.html
1. Do steps 1 and 2 under Condition 1.
2. Download the attached zip file. It contains the files I had a hard time finding.
3. Download the 2.1 RUU file from here: http://rapidshare.com/files/418525132/RUU_Incredible_Verizon_WWE_1.22.605.2_Radio_1.00.03.04.06_hboot_0.79_.exe
4. Follow steps 8 through 11 under condition 1 to get a good copy of the 2.1 ROM.
5. Copy the 2.1 ROM to the c:\android-sdk-windows\tools folder.
6. Unzip the files downloaded in step 2 to the c:\android-sdk-windows\tools folder.
7. Copy the unrevoked-forever.zip to the c:\android-sdk-windows\tools folder.
Note: At this point, you should have the following files copied to your c:\android-sdk-windows\tools folder:
PB31IMG.zip (this is the 2.1 ROM)
unrevoked-forever.zip (will set S-OFF)
rageagainstthecage-arm5.bin (this is a root exploit - gives you temperary root)
mtd0.img (need to research this one)
flash_image (this flashes images)
7. Connect your phone to your computer and ensure you have USB DEBUG turned on and CHARGE ONLY selected.
8. Open a command promt window and change to the c:\android-sdk-windows\tools folder.
9. Enter adb push unrevoked-forever.zip /sdcard/ and then press enter.
10. Enter adb push flash_image /data/local/ and then press enter.
11. Enter adb push rageagainstthecage-arm5.bin /data/local/tmp/ and then press enter.
12. Enter adb push mtd0.img /sdcard/ and then press enter.
13. Enter adb push PB31IMG.zip /sdcard/ and then press enter.
14. Enter adb shell and then press enter.
15. Enter cd /data/local/tmp/ and then press enter.
16. Enter chmod 777 /data/local/tmp/rageagainstthecage-arm5.bin and then press enter.
17. Enter cd /data/local/ and then press enter.
18. Enter chmod 777 /data/local/flash_image and then press enter.
19. Enter cd /data/local/tmp/ and then press enter.
20. Enter ./rageagainstthecage-arm5.bin and then press enter. You will now see some text on your cmd prompt screen explaining the exploit. Wait for the adb shell to go away, and it will dump you into your windows command prompt again (no shell) should look something like this:
C:\android-sdk-windows\tools>
21. Enter adb shell and then press enter. You will see you now have a # instead of a $ prompt.
22. Enter cd /data/local and then press enter.
23. Enter ./flash_image misc /sdcard/mtd0.img and then press enter. This will flash your misc partition with Toast's mtd-eng.img and should return you to a # prompt.
24. Enter reboot bootloader and press enter.
25. HBoot will load. Select bootloader and HBoot will then load PB31IMG.zip.
26. Follow the instructions to have HBoot install PB31IMG.zip.
Once it is finished, select restart. You now are on the stock 2.1 build of Android. Now you can follow steps 3 through 21 under condition 1 and get your phone loaded back with 2.2 and have root and S-OFF.
Condition 6
1. Do steps 5 through 21 under Condition 1.
Condition 7
The following steps will allow you to use the 3G Mobile Hotspot that comes with the OTA 2.2 update and not have Verizon charge you for using it:
1. On your phone, bring up the dialer and dial ##778. This will load EPST.
2. Select EDIT.
3. Enter 000000 for the password.
4. Select SECURITY.
5. Select the username that has [email protected].
6. Edit the username to read [email protected] (delete "dun.").
7. Click the back button to return to the list.
8. Select M.IP DEFAULT PROFILE.
9. Repeat steps 5 and 6.
10. Click on MENU and select COMMIT.
At this point, your phone will reboot and you will be able to use the 3G Mobile Hotspot application to get free WiFi tethering. Enjoy.
Condition 8
I have so far found three options for removing the preloaded apps. They all require the phone to be rooted. Here they are:
1. The first way is to get Titanium Backup. You will also need to donate (as little as $3.99) to get full functionality of Titanium Backup, but it is well worth it. If you do not want to physically remove the application, you can use the FREEZE function and the application will be removed from the app list, but physically will still be on the phone. If you really want to get it off, you can uninstall and then deleted from the phone. All of this through a user interface that is pretty easy to use. By the way, it also does backups of apps and data.
2. Another option is to get Root Explorer. You have to pay for this one. It will let you mount the system folders on the phone as read/write and allow you to move and/or delete apps from the apps folder on the phone. This is a good app and worth having even if you do not use it to remove apps.
3. The final way is to use ADB and the command prompt to remove or move any application you do not want. This is tried and true, but combersome. You do not have to buy it, but there is no GUI to help you out.
My thanks to all the folks here on XDA that made it possible for us to release the possibilities of the Droid Incredable. As I stated above, I did not create the apps or the steps, I just put them together for others to use. I wish I could thank all the individuals that made this possible, but I did not get thier IDs, so in lew of an individual thank you, I am posting this group THANK YOU. Keep up the good work!
Thanks, I have a question on condition 4
4. Stock 2.2 without root and with unrEVOked Forever
If I do the steps and since I am not loading RUU (I manually updated the offical OTA and have S-off) will this still wipe my phone clean? Looks like all I am doing is loading clockwork back on and load superuser..etc, that shouldn't wipe all the data right?
Scblacksunshine said:
Thanks, I have a question on condition 4
4. Stock 2.2 without root and with unrEVOked Forever
If I do the steps and since I am not loading RUU (I manually updated the offical OTA and have S-off) will this still wipe my phone clean? Looks like all I am doing is loading clockwork back on and load superuser..etc, that shouldn't wipe all the data right?
Click to expand...
Click to collapse
No, in the case of having 2.2 already loaded and S-OFF, you are correct, the phone will not get wiped. The steps will root the phone and load superuser back on.
confirmation
Can anyone confirm option 4 working??
RBurn said:
Can anyone confirm option 4 working??
Click to expand...
Click to collapse
Those are steps I used to get root back on my phone after I update to 2.2. As I stated, I messed up the first time and did not load unrEVOked forever and could not root the phone, so I had to downgrade to 2.1 first and then go through the rooting process. That time I made sure to load unrEVOKED forever. After that, all went well.
Sent from my HTC Incredible.
RBurn said:
Can anyone confirm option 4 working??
Click to expand...
Click to collapse
I did option 4 early this morning. Worked perfectly.
Thank-you to all involved.
Thanks for the write up =)
I am trying condition five and on step 18 and after running ./rageagainstthecage-arm5.bin it exectues so I move to step 18 and type adb shell but it remains, $ not root(#). Does anyone know if This has worked yet?
also Im running Ubuntu 10.04 if that makes a difference
adb shell
cd /data/local/tmp
chmod 0755 /data/local/tmp/rageagainstthecage-arm5.bin
cd /data/local
chmod 0755 /data/local/flash_image
cd /data/local/tmp
./rageagainstthecage-arm5.bin
This worked
PimpShit420 said:
adb shell
cd /data/local/tmp
chmod 0755 /data/local/tmp/rageagainstthecage-arm5.bin
cd /data/local
chmod 0755 /data/local/flash_image
cd /data/local/tmp
./rageagainstthecage-arm5.bin
This worked
Click to expand...
Click to collapse
I tried this and it did not work for me. It looked as if it did. It gave me the proper prompt, but on reboot, no root access. I had to use chmod 777 instead of chmod 0755.
PimpShit420 said:
Thanks for the write up =)
I am trying condition five and on step 18 and after running ./rageagainstthecage-arm5.bin it exectues so I move to step 18 and type adb shell but it remains, $ not root(#). Does anyone know if This has worked yet?
Click to expand...
Click to collapse
I made a mistake, the line should have had 777 after chmod, not 0755. I have updated the instructions. If other individuals that use 0755 instead of 777 get the above to work, let me know. I do not know what the difference is. All I know is 0755 did not work for me. I had to use 777. I think I will do some research on chmod.
Hope other individuals find this helpful.
well I got to root in the shell and everyting seemed to work up until I tried to flash the PB31IMG, is says the main version is older and just reboots
I dont know what the difference is but it could be we are running different OS, windows vs linux but I have no clue
PimpShit420 said:
well I got to root in the shell and everyting seemed to work up until I tried to flash the PB31IMG, is says the main version is older and just reboots
Click to expand...
Click to collapse
This is the problem I had. Try 777 instead of 0755 after each of the chmod commands. That is what worked for me.
you were right, the first time 0755 gave me root but did not let me flash the PB file, the second time 0755 didnt work, and 777 did but it still says update fail
chmod 0755 vs chmod 777
PimpShit420 said:
I dont know what the difference is but it could be we are running different OS, windows vs linux but I have no clue
Click to expand...
Click to collapse
Well, I looked the chmod 777 and chmod 0755 commands up. Both commands change the read/write state for a file. 0755 changes the permissions for a specific group and user. 777 changes the permissions for everyone. You can find an explanation here: http://ss64.com/bash/chmod.html
0755 did not work for me, but 777 did. I am going to keep the instructions as they are unless I get feedback that 0755 is working for other people. If I do, I will add them as an alternative.
PimpShit420 said:
you were right, the first time 0755 gave me root but did not let me flash the PB file, the second time 0755 didnt work, and 777 did but it still says update fail
Click to expand...
Click to collapse
Are you using 777 for each chmod command?
Also, I was reading through the steps and found an error with step 16. It said the following:
16. Enter chmod 777 /data/local/tmp/rageagainstthecage-arm5.bin and then press enter.
It should have said this:
16. Enter chmod 777 /data/local/rageagainstthecage-arm5.bin and then press enter.
I have updated the steps on post 1.
Thanks very much for this thread!
My phone was in Condition 3. Instructions worked for me!
BNG303 said:
Thanks very much for this thread!
My phone was in Condition 3. Instructions worked for me!
Click to expand...
Click to collapse
Your welcome. I am glad it helped.
bagery77 said:
I did option 4 early this morning. Worked perfectly.
Thank-you to all involved.
Click to expand...
Click to collapse
Glad this helped. I wanted to give everyone a one stop shop for updating and root for 2.2. Also hoped everyone would not have to go though all that I did.
Originally i ported PRIMEv1.4 by Roach2010, an honeycomb 3.1 rom from Asus to Iconia A500..Its now a more Acer specific rom based on acer drivers and software but with 3.1 features. We are still waiting for the kernel source, so limits of a stock kernel apply, which is one, using the new feature PS3 controller joypad's. Until source is out, these functions are missing.
You can also follow updates on Twitter now: Dexter Picard (DexterPicard) on Twitter or
me a Red bull, and you're sure i stay up working on this mod or you can visit my new homepage at Dexter's mods
Kernel source of "angel" is found here
BRIEF HOWTO
Download AcerRecoveryInstaller from Market or from apps section of A500 here. or use the old solution from this post .
Boot into ClockWorkRecovery (POWER ON + VOL-) and do a full backup.
put PRIMEE v1.4 zip on your sdcard and install using ClockWorkRecovery
NEW USERS - do a factory reset (WIPE) in ClockWorkMod when installing for the first time.
What does this rom offer
99% of all the new 3.1 features including;
Google Video (i think it was 3.1 only)
Google Books (i think it was 3.1 only)
Google VideoEditor
Asus Book Reader
Enhanced exchange support
Faster Browser
resizable widgets (new launcher 3.1)
multilanguage
enhanced task manager
added filesystem tweaks (kernel 2.6.36.3 features)
added 3G Huawei dongle support
added international keyboard layout support
SIP supported & SMS supported
enhanced network driver
root'd + superuser.apk included
DLNA support
Latest updates (P8-patch3)
[*] 2.6.36.4 kernel with CIFS/NFS/3G support. Optional OC upto 1700Mhz.
[*] Now with PS3 controller support
[*] A Splashtop HD fix here in this attachment
[*] Asus book reader app fix.
added SMS functionality with 3G, and enable SIP phone over wifi function, use SMS app from Market(handcent sms) with mobile part.
rearranged boot image parameters a little.
Media scanner both see internal & external directories now perfectly.
disabled adb at bootup, so Internal storage shows on windows ( through Portable devices - A500)
GoogleVideos app added (tested and working from USA)
Changed boot.img, so "am,install" etc works from adb again.
Added AcerSync (Request)
Replaced Asus Camera with Acer Camera (Request)
changes to mounted ext4 filesystems (small optimization)
Wifi fix added for EU users to build.prop "ro.wifi.country=EU"
Full fix for storage locations: Now its simple /mnt/sdcard , /mnt/external_sd , /mnt/usb_storage
bootanimation update .. Thanks to boggio95
Dock station + remote controller fix
LetsGolf included in full image , i just had to
Settings -> Battery stats is now included
[Bugs confirmed]
rotation lock key does not work (it serves no function in Asus firmware)
Don't mess with! (NOW YOU ARE WARNED!)
Disabling Phone+TelephonyProvider can cause unstable OS, settings crash, tablet freeze etc..
Removing apps from system folder can cause bootloop's
[PRIMEE_p8-3.zip] (patch goes on top of above existing full p8 image)
MD5: 4a48c21b4dc6cbfd6d074105318c88c4
[PRIMEE_acerA500-p8.zip]
MD5: 4efd9fcfdbe918c8ac696467a05a0ae7
See post #2 for installation and all other guides
You do all this and you take the risk. But remember if you got the CWM working, you should be safe and you can run itsmagic from CWM if you are in doubt. I take no responsibilites if you damage or brick your device. But if you do think its bricked, and you get checksum errors both at boot and recovery, sc2k might be able to help if you saved your UID number.
The GUIDES!!
INSTALL RECOVERY.IMG with ITSMAGIC (proceed at your own risk) Recommended is to follow original guide
Alternatively, a new easy installer solution for adding the new recovery.img see AcerRecoveryInstaller from Market.
0. Please read the guide below to get your UID ( see How to get the USB serial number for more info)
1. Extract the recovery.zip and copy the contents, recovery.img, to your a500. normally /data/local is a sure location to write it to.
2. so copy using adb like this
adb push recovery.img /data/local
adb push itsmagic /data/local
3. open adb shell
4. execute commands
su -
chmod 755 /data/local/itsmagic
/data/local/itsmagic
5. if the itsmagic works, you see the "done" information etc... BUT if its not working, don't do the commands below...try and figure out why its not working.
6. IMPORTANT - if all is ok, continue with the commands to remove any chance of corrupting recovery.
mount -orw,remount /system
rm /system/etc/install-recovery.sh
(this command can fail ie. not found (its ok if it does))
mount -oro,remount /system
6a. Next these commands below will install the new recovery.
cat /dev/block/mmcblk0p1 >/data/local/oldrecovery.img
chmod 777 /data/local/oldrecovery.img
cat /data/local/recovery.img >/dev/block/mmcblk0p1
/data/local/itsmagic
sync
Copy the /data/local/oldrecovery.img to your pc.
Execute this command on your pc.
adb pull /data/local/oldrecovery.img oldrecovery.img
1. with adb you can restore the "oldrecovery.img" like this
adb push oldrecovery.img /data/local
adb push itsmagic /data/local
2. open adb shell
3. execute commands
su -
chmod 755 /data/local/itsmagic
/data/local/itsmagic
5. confirm itsmagic works.
6 if all is ok, continue with the commands
cat /data/local/oldrecovery.img >/dev/block/mmcblk0p1
/data/local/itsmagic
sync
INSTALL CUSTOMROM GUIDE (proceed at your own risk)
make sure you validate the MD5SUM of the rom zipfile if possible for you, to ensure file is ok, or manually extract content on pc/mac/windows to verify zipfile is ok.
copy the PRIMEEv14_acerA500.zip to your sdcard, if md5sum / zip file is ok.
run the recovery (POWER off tablet.. then press and hold POWER button and hold VOL- until text in upper left corner appear and stop pressing VOL-)
use ClockWorkMod as normal (assumed is you tried cwm before) and wipe data/cache areas.
install zip file sdcard, and select the PRIMEEv14_acerA500.zip, and chose YES to install.
wait for installation to finish, and then choose reboot now
the zip file contains itsmagic and will execute at finish, so a reboot should run fine and boot your new custom rom.
How to get the USB serial number:
1. Connect Iconia to your PC
2.a Linux
call lsusb -v
read the value of iSerial for Iconia
2.b Windows
- Open Device manager
- Goto Properties of Android USB Devices->Acer Composite ADB Interface
- Goto "Details" Tab
- Select "Parent" from the property selection.
- Read the value. It looks like this:
USB\VID_0502&PID_3325\370014740c00594
- The number after the last "/" is the UID.
2.c Windows (alternative method)
Download this tool (download link is nearly at the end of the page):
- Open the tool
- Sort after VendorID
- Check all devices with VendorID = 0502 and ProductID = 3325 . There is also a "Serial Number" column.
Backup all of your partitions on your iconia A500
Connect Iconia to your PC or open a terminal on your tablet. make sure you got a sdcard inserted to with at least 1GB free space
if you are on stock rom, location of sdcard is /mnt/external_sd , if you are already on 3.1 its /data/Removable/MicroSD, put that into first step below, where i wrote you should.
so execute the commands below, and you got a full backup of your device..Remember to execute the "itsmagic" command, if you restore this backup.
BACKUP COMMANDS
export SDCARD=[YOUR SDCARD LOCATION] (ie. SDCARD=/mnt/external_sd)
cat /dev/block/mmcblk0p1 >$SDCARD/mybackup_mmcblk0p1
cat /dev/block/mmcblk0p2 >$SDCARD/mybackup_mmcblk0p2
cat /dev/block/mmcblk0p3 >$SDCARD/mybackup_mmcblk0p3
cat /dev/block/mmcblk0p5 >$SDCARD/mybackup_mmcblk0p5
cat /dev/block/mmcblk0p6 >$SDCARD/mybackup_mmcblk0p6
cat /dev/block/mmcblk0p7 >$SDCARD/mybackup_mmcblk0p7
RESTORING FILES
If you want to restore the files, open the CWM recovery you installed and log in with adb.
make sure all partitions are unmounted. execute the commands in the adb here.
make a copy of the "itsmagic" application to your sdcard location as well.
RESTORE COMMANDS
mount /sdcard
export SDCARD=/sdcard
cat $SDCARD/mmcblk0p1 >/dev/block/mmcblk0p1
cat $SDCARD/mmcblk0p2 >/dev/block/mmcblk0p2
cat $SDCARD/mmcblk0p3 >/dev/block/mmcblk0p3
cat $SDCARD/mmcblk0p5 >/dev/block/mmcblk0p5
cat $SDCARD/mmcblk0p6 >/dev/block/mmcblk0p6
cat $SDCARD/mmcblk0p7 >/dev/block/mmcblk0p7
mount /system
copy $SDCARD/itsmagic /system/bin/
chmod 755 /system/bin/itsmagic
/system/bin/itsmagic
Wow! very prompt progress to custom rom. Thanks dexter!
Is that the recovery you included the CWM?
Can I understand that the recovery.img should be flashed using itsmagic method. After that, we get a custom recovery (CWM) to restore your update.zip.
And your update.zip will not contain anything that would alter the kernel such that you will not run itsmagic again in your update.zip. Am I correct? Thanks.
ardatdat said:
And your update.zip will not contain anything that would alter the kernel such that you will not run itsmagic again in your update.zip. Am I correct? Thanks.
Click to expand...
Click to collapse
my update.zip WILL install a custom boot.img , as HC3.1 uses a different boot, so its unavoidable..
but i have included itsmagic in the zip, and when the "system" is unpacked, it leaves it unmounted until itsmagic has run, so the libraries are available to execute the application which is done at the end in the updater-script.
I have tested it and it works and installs the new boot with this recovery.img (this image got busybox in /sbin which is important)
sorry, little tech, but required to explain how i did it.
So exciting cant wait to try this out tomorrow
Oh YEAH! Was still hoping for this coz customROMs came to other devices with locked bootloader too!
Now its here!
Will definetly try this when i have time this afternoon
OMG so greaaaaat, thanks pal!!!
edit: downloading
dexter, can you make a guide for newbie to install this rom ? or may be any one?
Working great so far. Quite stable.
interqd said:
dexter, can you make a guide for newbie to install this rom ? or may be any one?
Click to expand...
Click to collapse
Soon, i will do even better.. ill dig up an old application used on FlipOut to install a recovery.. this app will then install the recovery.img and run the "itsmagic" application. but that for later.
but here is my way of seeing it simple, if you can use adb and a shell in a rooted a500.
See post #1 for the GUIDE(s)
Dexter_nlb said:
Soon, i will do even better.. ill dig up an old application used on FlipOut to install a recovery.. this app will then install the recovery.img and run the "itsmagic" application. but that for later.
but here is my way of seeing it simple, if you can use adb and a shell in a rooted a500.
See post #1 for the GUIDE(s)
Click to expand...
Click to collapse
I got a itsmagic: not found
when I try to execute :S i dont understand why, is there a permission to be set or something?
on itsmagic post just say "call itsmagic" but bunno what this mean its a command? just #itsmagic?
thanks in advance
EDIT:
I think this need to be posted on OP
2. so copy using adb like this
adb push recovery.img /data/local
adb push itsmagic /data/local
3. open adb shell
4. execute commands
cd /data/local
su -
chmod 755 itsmagic
./itsmagic
Click to expand...
Click to collapse
Alejandrissimo said:
I got a itsmagic: not found
Click to expand...
Click to collapse
thanks.. i updated post #1.
Boot perfectly!!!! thanks a TON for your work!!!!
btw, this recovery its 100% functional? for custom.zip files and stuff?
Can root explorer and terminal emulator be used to execute the above commands from the device or is adb the only option?
Sent from my A500 using XDA Premium App
bochocinco23 said:
Can root explorer and terminal emulator be used to execute the above commands from the device or is adb the only option?
Sent from my A500 using XDA Premium App
Click to expand...
Click to collapse
I think yes, you can use terminal emulator
Any impressions so far?
huxflux2003 said:
Any impressions so far?
Click to expand...
Click to collapse
marvelous just want to figureout how play videos everything else its a lot of smooth (youtube HD works)
It plays YouTube videos fine...
Alejandrissimo said:
marvelous just want to figureout how play videos everything else its a lot of smooth
Click to expand...
Click to collapse
what about install moboplayer?
even 3rd party cant play videos?
and, does usb host is functioning?
keyboard, mouse, gamepad, hdd, td, etc
3.1 should have them to run by default right ?
Language support
Hi, does your ROM supports all languages like Android 3.1, or did you remove e.g. Czech language?
Anyway, sounds great, I will try it today.
These are my notes and guide for rooting the Kindle with 6.2.1 firmware. If I left something out, or something is not working, please leave a comment and I'll try to update.
Credit goes to JCase for the root. Please consider making a donation to him here:
https://market.android.com/details?id=net.andirc.jcasedonate
Original procedure is here:
http://www.androidpolice.com/2011/1...on-kindle-regardless-of-its-software-version/
ADB INSTALL AND TEST - Method 1 (skip to the ROOT INSTALL section if you already have a working ADB)
NOTE: ADB = Android Debug Bridge. It is a command line interface to the android device. A working ADB is required before you can root your Kindle. ADB is installed on a PC and accesses the Kindle via USB cable.
Install Java SE Development Kit 7 on PC
The Android SDK Manager requires Java SDK
http://www.oracle.com/technetwork/java/javase/downloads/jdk-7u1-download-513651.html
Install Android SDK Manager on PC
The Android SDK has the drivers and ADB needed to perform the root procedure
http://developer.android.com/sdk/index.html
Uncheck Android 4.0
Check 2.33
Ensure Google USB Driver is checked
Install to c:\android to make typing easier later on
NOTE: The install can take a long time!
Manually update files so drivers will properly install
Open c:\users\your account name\.android\adb_usb.ini (or c:\documents and settings... if you have XP) and add the following
Code:
0x1949
Open c:\android\extras\google\usb_driver\android_winusb.inf and make additions as shown:
Code:
[Google.NTx86]
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
....
[Google.NTamd64]
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
Install drivers
Find the Kindle device in device manager and update drivers. Point to the location with android_winusb .inf
Verify ADB works
Open a command prompt
CD to c:\android\platform-tools
Code:
adb kill-server
adb devices
If it's working, ADB will return a large number, like this:
Code:
312342134231342 device
ADB INSTALL AND TEST - Method 2
NOTE: I have not tried this, but Vashypooh's app can apparently handle the driver install, and run ADB without installing the above software. If all of this works, then his app would be the best way IMO.
NOTE 2: I've seen a lot of comments suggesting the driver install in Vashypooh's app doesn't work at this point.
http://forum.xda-developers.com/showthread.php?t=1399889
ROOT INSTALL - Method 1
Install JCase's kindleroot_androidpolice.apk
JCase's app gives ADB root access. Once this is done, you still need to install the superuser app
Download kindleroot_androidpolice.apk to PC
http://www.multiupload.com/VNZ6Y41EQF
Ensure the Kindle is connected via USB, and copy file to Kindle sdcard
Using ES File Explorer on Kindle, navigate to the kindleroot_androidpolice.apk and launch
Follow prompts and click root
Install superuser app
Download superuser-2 to PC
http://www.multiupload.com/M2CX14W7Y0
Unzip to c:\download\sufiles
Use ADB to install SU app
Code:
adb root
adb remount
adb push c:\download\sufiles\su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb install c:\download\sufiles\Superuser.apk
adb reboot
ROOT INSTALL - Method 2
NOTE: I have not tried this, but Vashypooh's app can apparently handle the root process.
BurritoRoot (Temporary)
Install Permanent Root with Superuser
http://forum.xda-developers.com/showthread.php?t=1399889
A+ instructions, wish I could write my own that good lol.
jcase said:
A+ instructions, wish I could write my own that good lol.
Click to expand...
Click to collapse
Thanks to you for the root. I hope the guide will help those trying to root!
Thanks for the clear and easy steps.
Great guide Ectoplasmic!
One thing I would add though, in step 5 "Verify ADB Works", before you use the "adb devices" command, you need to type "adb kill-server". If you don't type in "adb kill-server" first, the device won't show up when you use the "adb devices" command. Or at least it didn't for me.
Otherwise, everything worked FLAWLESSLY. I verified I was rooted using Root Checker. Thank you!
zopzop25 said:
Great guide Ectoplasmic!
One thing I would add though, in step 5 "Verify ADB Works", before you use the "adb devices" command, you need to type "adb kill-server". If you don't type in "adb kill-server" first, the device won't show up when you use the "adb devices" command. Or at least it didn't for me.
Otherwise, everything worked FLAWLESSLY. I verified I was rooted using Root Checker. Thank you!
Click to expand...
Click to collapse
Thanks, I added this to the guide.
Hi I use JCase method to root my 6.2.1 KF, then I need to unroot it so my kids can still enjoy the prime video, but I cannot. I try rootkeeper but failed. I also try the "kindleroot_androidpolice.apk" and click the unroot button, but it still cannot unroot. Pls help!
Get help in irc from jcase and vashypool theyll probably be able to help u
tkcctkcc said:
Hi I use JCase method to root my 6.2.1 KF, then I need to unroot it so my kids can still enjoy the prime video, but I cannot. I try rootkeeper but failed. I also try the "kindleroot_androidpolice.apk" and click the unroot button, but it still cannot unroot. Pls help!
Click to expand...
Click to collapse
Unroot in my app (BurritoRoot) does not remove su, it just turns off adb root (which is what my app turns on) sorry for the confusion.
Will add in the future when I release burritomod
Here's the equivalent instructions for Mac
I am pretty new myself, but I'm happy to share what I've come up with so far. I am on a Mac OS X 10.6.8
Download the Android SDK for Mac (dl.google.com/android/android-sdk_r16-macosx.zip), the easiest place to put it is at the top of your user directory, from the browser download window chose your username from places on the left side, then name the zip "Android"
Next from Finder, navigate to the place where you downloaded the SDK, and double-click on it which should unzip it and create a folder of the same name e.g "Android". Open that and inside it will be a folder "tools", and inside that there will be a file "android". Double-click that to run it and the "Android SDK Manager" program window will pop up, you will also see a Terminal window in the background, don't worry about that. Uncheck all the boxes, then check "Android SDK Platform-tools" which should be the third from the top, and click install. This gets you the actual "dab" program.
Once adb is setup, to get it to recognize your kindle fire on your mac, you may need to make an entry in a config file if you haven't already.
Start Terminal Applications > Utilities > Terminal or if you are used to using spotlight, simply type in "Terminal". (here's an intro to using Terminal guides.macrumors.com/Terminal) and navigate to the directory where you have adb, e.g. if you placed it at the top of your user directory that would be
Code:
cd Android
or if you left it in the default downloads directory it would be
Code:
cd Downloads/android-sdk-macosx/
then enter the following commands
Code:
mkdir ~/.android
You may get the following error
Code:
mkdir: /Users/<username>/.android: File exists
If so, that is fine, continue to the next step
Code:
touch ~/.android/adb_usb.ini
open -e ~/.android/adb_usb.ini
TextEdit will open with that file open, you should have an entry in it on a single line that says
Code:
0x1949
if not, copy that in, then save and close it, then
Code:
./adb kill-server
Connect your kindle to the mac if it isn't already, then
Code:
./adb devices
You should see a message like
Code:
List of devices attached
2ED6000600000001 device
On your kindle, make sure you have a file navigation app, the example above ES FileExplorer is excellent and is the one I use from Amazon app store
Download Burrito Root from Android Police ( androidpolice.com/2011/12/23/exclusive-how-to-easily-root-the-amazon-kindle-regardless-of-its-software-version/)
Also download the Superuser.zip from the same page (multiupload.com/ONH28CB1GU) and unzip, then make sure you move the contents "su" and "Superuser.apk" into the same directory as adb
Through Finder copy the "kindleroot_androidpolice.apk" file you downloaded earlier to your kindle, some place like "download" so you can find it easily later
Now on the Kindle, tap disconnect on your KIndle so you can get back to the apps screen, launch the file explorer you installed earlier, navigate to folder you copied it to, e.g. "download" then install the "kindleroot_androidpolice.apk", open it, and go through the steps to launch click "Root"
Back on the Mac, in the terminal window where you had adb going, enter the commands
Code:
./adb root
./adb remount
./adb push su /system/xbin/su
./adb shell chown 0.0 /system/xbin/su
./adb shell chmod 06755 /system/xbin/su
./adb install Superuser.apk
./adb reboot
You should be rooted now, then you can follow the other instructions out there for getting Android market, etc working
TIP
here's a tip if you don't want to have to type in the period and slash ahead of adb every time. from your terminal window enter the
Code:
cd ~
touch .profile
open -e .profile
That will open text editor, and paste in the following line,
Code:
PATH=${PATH}:/Users/<username>/<sdk-directory>/platform-tools
replacing both our user name and the path to where you have sdk e.g. in my case
Code:
PATH=${PATH}:/Users/kbiz/Android/platform-tools
Then close the terminal window and reopen a new one and you should be good to go, now you'll only need to type in "adb".
Let me know if I missed something, trying to give back since this forum has been super helpful.
---------- Post added at 01:04 AM ---------- Previous post was at 12:58 AM ----------
tkcctkcc said:
Hi I use JCase method to root my 6.2.1 KF, then I need to unroot it so my kids can still enjoy the prime video, but I cannot. I try rootkeeper but failed. I also try the "kindleroot_androidpolice.apk" and click the unroot button, but it still cannot unroot. Pls help!
Click to expand...
Click to collapse
OTA Rootkeeper should work but since its not, try this (courtesy rootkindlefire.com/kindle-fire-unroot/how-to-unroot-kindle-fire/)
Code:
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
rm /system/app/Superuser.apk
rm /system/xbin/su
reboot
after your Kindle restarts you won't have root and Amazon Video should work just fine.
Hello,
I have successfully rooted my device with the above instructions. While installing the Android market I was abusing of my root privileges and I've successfully "burned" my device. That is, the Kindle won't start up anymore (it stays forever in the initial phase showing the kindleFire logo).
I don't know where else to turn for help so I'm writing about this here. If anyone has hints of how I could recover my kindle from the void, please let me know
Cheers
http://forum.xda-developers.com/showthread.php?t=1356257
Yesssssssssss
Yesssssssssssssssssss. So nice to have root again. My Titanium Backup and SUFBS works again
I had ADB and SDK working when I had my Glacier, but since I have gotten my SGS2, and my Kindle, Android SDK Manager will not open... It just opens a command prompt, and then closes.. I have reinstalled both the SDK Manager and the Java Kit... Any ideas?
EDIT:
I must have messed with something in my system settings somewhere to corrupt a bunch of stuff... I did a system restore to the 18th of December, reinstalled, and everything works perfect now... Oh well! Haha
Hey, I used a combo of the link JCase gave me when I had questions, this guide, and the links off the rootzwiki guide and managed to get it first try. It was actually easier than I thought it was going to be. I've never rooted anything before, I didn't even have ADB or the SDK until tonight. The process (while using both guides and video tut) went smoothly without a hitch. I just finished installing the Android Market but have to wait til morning to access it, as I have no WiFi at home, and its too late for me to be driving to a hotspot. Thank you very much. You(JCase) and your comrades who put this all together f**king rule.
a really clear and easy guide ! - congratulations - you shoud try to let it pin on top !
Ectoplasmic said:
NOTE 2: I've seen a lot of comments suggesting the driver install in Vashypooh's app doesn't work at this point.
Click to expand...
Click to collapse
the reason people have problems with vashipooh's driver installation seems to be the old drivers - they don't manage to clean up the old drivers:
disconnect KF
Open an (elevated for win7) command prompt:
set devmgr_show_nonpresent_devices=1
devmgmt.msc
device manager opens - click "view" - click "show hidden devices"
now you see all devices ever connected/installed
uninstall all devices regarding "kindle" and "android (composite) adb device"
connect KF - will startup by itself
select the most recent driver (that you have installed before by install_driver.bat from KFU) manually (check date/time)
now you should be set up with a good driver installation
btw. i'm on xp - it's working for xp and 7, 32 and 64 bit
Enter recovery and sideload CN ROM
http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ME176C-CN-3_2_23_182.zip
To return to WW rom its a litle complicated becouse when you try to sideloade ww version it gives error for not having inough space. So you need to give command to recovery to instal zip from location you want.
1. root with rootzenfone.apk
http://23pin.logdown.com/posts/230216-root-rootzenfone-14r
2. turn on usb debuging
3. download ww rom and rename it update.zip
http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ME176C-WW-3_2_23_182.zip
4. download es or some other file menager that has root access.
5. go to / (root) and manualy copy update.zip to /data folder
6. Download https://drive.google.com/file/d/0B6...drivesdk&resourcekey=0-W0btfSuQS9kq5iNNsCuWgQ and copy command file to cache/recovery folder
6. open ADB and type line by line:
adb remount
adb shell
su
echo 'boot-recovery ' > /cache/recovery/command
echo '--update_package=/data/update.zip' >> /cache/recovery/command
echo '--wipe_cache' >> /cache/recovery/command
echo 'reboot' >> /cache/recovery/command
reboot recovery
after this reboot to recovery and automaticly instal ww rom
This is fantastic, and smart move making a new thread...
Thanks,
sutekh137
And if you're not bricked, but can't update from the old software version. Copy and paste the commands in terminal emulator to force the update. Worked out great. Thanks for the tip.
slayeralive said:
Enter recovery and sideload CN ROM
http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ME176C-CN-3_2_23_182.zip
To return to WW rom its a litle complicated becouse when you try to sideloade ww version it gives error for not having inough space. So you need to give command to recovery to instal zip from location you want.
1. root with rootzenfone.apk
http://23pin.logdown.com/posts/230216-root-rootzenfone-14r
2. turn on usb debuging
3. download ww rom and rename it update.zip
http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ME176C-WW-3_2_23_182.zip
4. download es or some other file menager that has root access.
5. go to / (root) and manualy copy update.zip to /data folder
6. open ADB and type line by line:
adb remount
adb shell
su
echo 'boot-recovery ' > /cache/recovery/command
echo '--update_package=/data/update.zip' >> /cache/recovery/command
echo '--wipe_cache' >> /cache/recovery/command
echo 'reboot' >> /cache/recovery/command
reboot recovery
after this your device will reboot to recovery and automaticly instal ww rom
Click to expand...
Click to collapse
I'm having a lil problem here. Could you elaborate a little more, like in /root. <-- What does this mean? Do i write root or am I to go to root of the tablet's memory? And should I use adb on my PC connecting by usb cable to the tablet? I'm having a little problem understanding some of the steps.
(Remember, it's my sex life that it's in danger here)!
bravesoul said:
I'm having a lil problem here. Could you elaborate a little more, like in /root. <-- What does this mean? Do i write root or am I to go to root of the tablet's memory? And should I use adb on my PC connecting by usb cable to the tablet? I'm having a little problem understanding some of the steps.
(Remember, it's my sex life that it's in danger here)!
Click to expand...
Click to collapse
I would assume root of the device itself as the next step is to put update.zip in /data
(Get me in on the fun. I helped. )
I tried terminal emulator to write adb remount, but just after I wrote it, it gives me an error.
I've put the the update.zip in data folder. but there's like two data folders in my tablet's memory root. Do I put it after mnt or before (I,m using root browser v2.3)? Like in the real root of everything? Another question. Must I use the zip inside another zip of the asus ww rom, or just the unzipped zip file. (LOL, confusing, i know).
(I dunno JerBear, they're very peculiar about what/who they blow)!!
bravesoul said:
I tried terminal emulator to write adb remount, but just after I wrote it, it gives me an error.
I've put the the update.zip in data folder. but there's like two data folders in my tab memory's root. Do I put it after mnt or before?
Click to expand...
Click to collapse
They should be symlinked to the same thing. Let me check...
Well. I only have the data folder that's in the root. Peculiar.
As for the zip file question, go for trial and error. Worst case scenario recovery rejects it.
(We'll work around it )
This is what I get in terminal emulator:
Me176c
bravesoul said:
This is what I get in terminal emulator:
Click to expand...
Click to collapse
You need that command only when you are using ADB over PC
Thanks, but I have other issues.
What zip file should I use? The original we download from ASUS or the zip file inside the original.
JerBear told me to try one or another, but he doesn't know I'm in a place where Internet speed is like 50 Kbps... Which means it takes about two hours to download the original file.
However,(and this will sound strange), if anyone can give me the original names of both the original .182 zip file and the one inside the original, I think I can use a previously (and renamed) downloaded .182 ROM.
Me176c
bravesoul said:
Thanks, but I have other issues.
What zip file should I use? The original we download from ASUS or the zip file inside the original.
JerBear told me to try one or another, but he doesn't know I'm in a place where Internet speed is like 50 Kbps... Which means it takes about two hours to download the original file.
However,(and this will sound strange), if anyone can give me the original names of both the original .182 zip file and the one inside the original, I think I can use a previously (and renamed) downloaded .182 ROM.
Click to expand...
Click to collapse
Use zip inside original.
slayeralive said:
Use zip inside original.
Click to expand...
Click to collapse
So to be clear. I'll use ES File Manager to rename the file (update.zip) and copyit into Root->Data->Turn off the tablet and on again->enter into recovery->in PC I'll use adb->type adb remount and other commands->The tablet will reboot and update into the WW.182 ROM.
Right?
Me176c
bravesoul said:
So to be clear. I'll use ES File Manager to rename the file (update.zip) and copyit into Root->Data->Turn off the tablet and on again->enter into recovery->in PC I'll use adb->type adb remount and other commands->The tablet will reboot and update into the WW.182 ROM.
Right?
Click to expand...
Click to collapse
No man can you read? Do not turn of. Connect to pc and use adb or use terminal. If you are using terminal skip adb commands and start at "su" command. After typing last command it will automaticly reboot to recovery and start instalation than just wait...
slayeralive said:
No man can you read? Do not turn of. Connect to pc and use adb or use terminal. If you are using terminal skip adb commands and start at "su" command. After typing last command it will automaticly reboot to recovery and start instalation than just wait...
Click to expand...
Click to collapse
Ok, ok. Don't get your intelligence in a twist.
Thanks for helping me with my absurd noobiness. :good:
bravesoul said:
Ok, ok. Don't get your intelligence in a twist.
Thanks for helping me with my absurd noobiness. :good:
Click to expand...
Click to collapse
Have fun with your "reward"
Not yet I'm afraid. I've tried via terminal emulator and indeed it goes to recovery, but afterwards, it just reboots into the CN version untouched.
(And JerBear, i'm kidding about the chicks...They aren't 3. It's only one).
Try again you did somethin wrong
Folow the steps download->extract->rename to update.zip->copy to /data folder->type in terminal
bravesoul said:
Not yet I'm afraid. I've tried via terminal emulator and indeed it goes to recovery, but afterwards, it just reboots into the CN version untouched.
(And JerBear, i'm kidding about the chicks...They aren't 3. It's only one).
Click to expand...
Click to collapse
If you missd or typed wrong one character in terminal it wont work. Try again.
bravesoul said:
Not yet I'm afraid. I've tried via terminal emulator and indeed it goes to recovery, but afterwards, it just reboots into the CN version untouched.
(And JerBear, i'm kidding about the chicks...They aren't 3. It's only one).
Click to expand...
Click to collapse
From the top, you must be rooted and you must know what that is.
I used the file from inside the download. I believe it has user in the name.
Rename this file to be update.zip.
Place update.zip into the data folder in the root directory, ie. root/data/update.zip.
Back out of that when it's finished and find the original post with the instructions, touch it and touch the message symbol like you are going to reply.
Copy all of the commands from after su, to the end.
Open terminal emulator, Type su and give root permission at the prompt, touch and paste, you should see what you copied, if you don't, do it again. If you do, touch enter and the process will begin.
Do not do anything until the device reboots COMPLETELY. It will go through several reboots, just wait.
Viola, you will be updated.
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