Related
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.
As I've seen a few people around having some checksum erros, I decided to write a small HOWTO.
!!!
The most important information needed to recover from a bricked device is the UID
If your device is not bricked and you read this thread ensure that you have saved your UID!
!!!
Because some people do not read big red text, here it is once again:
GET YOUR UID even if your device is not bricked.
If you need help please contact me with PM or ask for help in this thread.
If your device does not boot anymore it may display the following checksum erros:
"LNX checksum error" - when trying to boot into normal mode
"SOS checksum error" - when trying to boot into recovery (VOL- + Power pressed)
<CASE 1> SOS checksum error
Steps:
- Switch off your device by pressing power for ~8sec
- Switch on your device and boot into normal mode
- If LNX checksum error is displayed, stop here and see <CASE 3>
- Download itsmagic (see this thread). Extract "itsmagic" to the tools folder of android sdk.
- Connect your device to your PC (Windows: drivers can be obtained from Acer website)
- If not already done, get your UID using Method 1 of "How to get the UID"
- If not already done, get a dump of mmcblk0_start (see "How to get a dump of mmcblk0_start")
- In the command window type:
Code:
adb push itsmagic /data/local
adb shell
su -
chmod 755 /data/local/itsmagic
/data/local/itsmagic
exit
- If everything went fine you should see some output of itsmagic
- Reboot and check if you can boot again
- Store your UID and mmcblk0_start to some safe place
Possible reasons for this error
- You tried to install a new recovery without calling itsmagic before
- You have not remove /system/etc/install-recovery.sh
- Your recovery partition is corrupt
<CASE 2> LNX checksum error
Steps:
- Switch off your device by pressing power for ~8sec
- Switch on your device and boot into recovery by pressing VOL- + Power
- If SOS checksum error is displayed, stop here and see <CASE 3>
If you have stock recovery:
- If not already done, get your UID using Method 2 of "How to get the UID"
- Apply an official OTA, see this thread
If you have thor's CWR:
- If not already done, get your UID using Method 1 of "How to get the UID".
- Select "reboot system now"
If you have any other recovery (that does not have itsmagic integrated):
- If not already done, get your UID using Method 1 of "How to get the UID". If Method 1 does not work, try Method 2
- DO NOT apply any official update.zip . Otherwise you will end up in <CASE 3>
- send me a PM or ask for help in this thread.
Possible reasons for this error
- You tried to install install a new kernel / stock update.zip without calling itsmagic (will not occur with thor's CWR)
<CASE 3> SOS and LNX checksum error
- If available, upload the "mmcblk0_start" dump to some file hoster (e.g. dropbox)
- Send me a PM with your UID and a link to "mmcblk0_start"
- If you do not have your UID: DO NOT connect your device to your PC:
- Pray that you are able to recover the UID from a PC the Iconia was already connected once.
- Windows: Try Method 2 of "How to get the UID" but DO NOT connect your device to your PC.
- Linux/Mac: Check old syslogs for messages where your device was connected to your PC (normally some "usb " kernel messages)
Possible reasons for this error
- You tried to install a new kernel athough you already have a SOS checksum error
- You tried to install a new recovery altough you aleady have a LNX checksum error
How to get the UID
Method 1
- If not already done, follow the instruction "Howto install ADB" below
- In the command shell, type:
Code:
adb devices
and press RETURN
This will output something like this:
Code:
List of devices attached
370014740c00594 device
The number is your UID.
- Save this number somewhere it won't get lost
Method 2
- Connect your device to your PC and ensure that drivers are properly installed (Windows: Can be downloaded from Acer website)
Windows:
Download this tool (download link is nearly at the end of the page):
- Open the tool
- Sort after VendorID
- Find all devices with VendorID = 0502 and ProductID = 3325. Check the "Serial number" column for these devices.
Linux:
Call (as root) and see the iSerial field for Iconia.
Code:
lsusb -v
Mac:
- Should be visible in system profiler. Sadly I don't own a mac. So if anyone can help me out with this?
How to get a dump of mmcblk0_start
- If not already done, follow the instruction "Howto install ADB" below
- In the command shell, type:
Code:
adb shell
su -
dd if=/dev/block/mmcblk0 bs=512 count=13312 of=/sdcard/mmcblk0_start
exit
exit
adb pull /sdcard/mmcblk0_start .
- This will create a file "mmcblk0_start" in the tools folder of your android-sdk.
- Copy this file to some safe place
How to install ADB
1. Download android SDK from here. Windows: Download the .zip file instead of the exe file.
2. Extract android SDK somewhere
3. Open a command shell:
- Windows: Press Winkey+R . Some small window appear. Enter "cmd" and click ok. A black command promt window will open.
- Linux/Mac: Open a terminal window
4. "cd" to the "tools" folder of the android sdk by typing the following in the command shell:
- Windows:
Code:
cd "<path to tools folder>"
Sample:
Code:
cd "c:\android\android-sdk-windows\tools"
- Linux/Mac:
Code:
cd /path/to/tools/folder
5. Ensure that your device is connected, that drivers are installed and that USB debugging is enabled (on Iconia: Settings->Applications->Development->USB Debugging)
reserved for me
Im just asking, in case3 u need dump of mmcblk0_start ,but what if dont have it, only UID?
Should i make dump of mmcblk0_start just in case to be insured that evrything will be ok if smth happens?
Any way thks fo tutorial)
Glebaka said:
Im just asking, in case3 u need dump of mmcblk0_start ,but what if dont have it, only UID?
Should i make dump of mmcblk0_start just in case to be insured that evrything will be ok if smth happens?
Any way thks fo tutorial)
Click to expand...
Click to collapse
Having a dump in <case 3> makes everything easier. But it is not mandatory. Nevertheless it's generally a good idea to backup mmcblk0_start.
btw: thor's CWR will backup mmcblk0_start since version 1.2 if you do a nandroid backup.
sc2k said:
How to get a dump of mmcblk0_start
- If not already done, follow the instruction "Howto install ADB" below
- In the command shell, type:
Code:
adb shell
dd if=/dev/block/mmcblk0 of=dd if=/dev/block/mmcblk0 bs=512 count=13312 of=/sdcard/mmcblk0_start
exit
adb pull /sdcard/mmcblk0_start .
- This will create a file "mmcblk0_start" in the tools folder of your android-sdk.
- Copy this file to some safe place
Click to expand...
Click to collapse
Hi there,
after i typed "dd if=/dev/block/mmcblk0 of=dd if=/dev/block/mmcblk0 bs=512 count=13312 of=/sdcard/mmcblk0_start" in the adb shell i got an invalid argument error:
Code:
if: illegal argument combination or already set
What i should do?
when i get a SOS checksum error and a LNX checksum error,can i copy files from pc to a500 device? how?
dmue said:
Hi there,
after i typed "dd if=/dev/block/mmcblk0 of=dd if=/dev/block/mmcblk0 bs=512 count=13312 of=/sdcard/mmcblk0_start" in the adb shell i got an invalid argument error:
Code:
if: illegal argument combination or already set
What i should do?
Click to expand...
Click to collapse
Sorry, there was a typo. Should be correct now
Thanks for the hint.
kimycai said:
when i get a SOS checksum error and a LNX checksum error,can i copy files from pc to a500 device? how?
Click to expand...
Click to collapse
The procedure for this case is much more complex. If you do something wrong, it is getting even more complicated.
I will not publish details currently, sorry. If you get this error, contact me.
As soon as some tools are finished i will update the OP.
Sent from my HTC Desire using XDA App
sc2k said:
Sorry, there was a typo. Should be correct now
Thanks for the hint.
Click to expand...
Click to collapse
Ah ok, thx.
thank you sc2k!
sc2k said:
The procedure for this case is much more complex. If you do something wrong, it is getting even more complicated.
I will not publish details currently, sorry. If you get this error, contact me.
As soon as some tools are finished i will update the OP.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
really？
waiting……
Hi
After I typed "dd if=/dev/block/mmcblk0 bs=512 count=13312 of=/sdcard/mmcblk0_start" in adb i got: "dd if=/dev/block/mmcblk0 bs=512 count=13312 of=/sdcard/mmcblk0_start /dev/block/mmcblk0: cannot open for read: Premission denied"
What i done wrong?
Raphaello said:
Hi
After I typed "dd if=/dev/block/mmcblk0 bs=512 count=13312 of=/sdcard/mmcblk0_start" in adb i got: "dd if=/dev/block/mmcblk0 bs=512 count=13312 of=/sdcard/mmcblk0_start /dev/block/mmcblk0: cannot open for read: Premission denied"
What i done wrong?
Click to expand...
Click to collapse
You need to be root
Type
Code:
su -
before.
I will update the guide
Thanks but it's doesn't work yet. I have root access. I tried type "su-" but it is the same message "cannot open for read: Premission denied". I install usb drivers and the others think from guide hmmmm....
Raphaello said:
I tried type "su-" but it is the same message "cannot open for read: Premission denied".
Click to expand...
Click to collapse
Did you type su- or su - (notice the space between su and -)?
Also you'll have to confirm su permissions on the tablet.
I typed "su -" with space between su and -
I have USB debugging turn on
When i type "su -" it say "Premission denied"
I really sorry for problem and thanks you for trying to help me
Is your device rooted? Because it has to be.
And if it's rooted did you notice a superuser app popping up after you run the command.
What a shame, I did not notice a superuser app popping up :/ Now it's ok. Thank You very much. I must learn a lot. Only think was taht I can't pull this file to my computer via "adb pull /sdcard/mmcblk0_start" but i copy it directly from device Now I feel safe.
Thanks a lot guys
Well, actually you should be able to dump directly to adb without copying to device to save some time.
like dd if=/dev/mmcblk0p1 count=X bs=Y
but without specifying of= or using of=-
and don't forget to redirect it to file. like "adb shell "dd if ..." > dump_p1". Not sure it will work fine, but I used it once on another device to dump block device image.
i download the android sdk zip file, but is seems that the "tools" folder doesn't include the adb executable file , how should i do?
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
Guys, firstly thank you for an awesome community.
Ok, here's the problem, I've got two Brand New A500's
I've followed Civato's guide for the ICS V3 unlocked bootloader and custom recovery. First Tab went flawless and I was done within 25mins.
But now the second Tab give me the following when I do "adb devices"
"C:\Program Files (x86)\Android\android-sdk\platform-tools>adb devices
List of devices attached
11525233415 device
C:\Program Files (x86)\Android\android-sdk\platform-tools>"
That is only a 11-digit number and not 15 as it is suppose to be.
Thus I get the following when I check my SBK number
"If your SBK is wrong, you'll get this:
rcm version 0X4
Command send failed (usb write failed)"
Any Ideas please??
EDIT: I AM A NOOB, and did not READ properly... I've already flashed the ICS Rom and should do the following...
"ON ICS ROM or ICS booloader (0.3.11 or 0.3.12) do this to get your cpuid:
Or you Install and launch Android terminal app on tablet. Run the following command: dmesg>/mnt/external_sd/dmesg.txt
Open up dmesg.txt (will be stored on your external SD) and look for androidboot.serialno. That is your CPUID."
When I use my CPUID extacted by the following method...
"ON ICS ROM or ICS booloader (0.3.11 or 0.3.12) do this to get your cpuid:
Or you Install and launch Android terminal app on tablet. Run the following command: dmesg>/mnt/external_sd/dmesg.txt
Open up dmesg.txt (will be stored on your external SD) and look for androidboot.serialno. That is your CPUID."
I get my CPUID, but when I use the created SBK in nvflash I get the following
"C:\nvflash>nvflash --bl bootloader.img --sbk 0x97FE1E00 0x846FF106 0x6B261504 0x
30772103 --sync
Nvflash started
USB device not found"
Really not sure what to do here.
Currently on Rooted OTA ICS
Thank You
~Solved~
May I PLEASE have the NOOB award??!!
Wasn't in APX Mode.
All fine!
Krypt0n1te said:
May I PLEASE have the NOOB award??!!
Wasn't in APX Mode.
All fine!
Click to expand...
Click to collapse
Hold the reset button then the power button.
This is with a usb connected to your tab
The tab will go black and you do your upgrades through the pc to the tab.
For flashing different situations.
I have a 3rd Gen fire hdx 8.9 on 14.3.2.6. Safestrap is installed. I want to roll back and unlock my bootloader to install the nexus rom.
Is there a tutorial available? Do I need to uninstall safestrap first?
Check page 1 of this thread, basically it's all there, so read the info & the linked threads. Any questions ask first, i.e. before you brick your kindle.
Note that you can NOT use the rollback images, nor edit the build number. You must use the procedure described in post 1 of the thread and download the rollback zip I linked in post 4, you need to scroll down to get to the 3.2.5/3.2.6 procedure.
Cl4ncy said:
Check page 1 of this thread, basically it's all there, so read the info & the linked threads. Any questions ask first, i.e. before you brick your kindle.
Note that you can NOT use the rollback images, nor edit the build number. You must use the procedure described in post 1 of the thread and download the rollback zip I linked in post 4, you need to scroll down to get to the 3.2.5/3.2.6 procedure.
Click to expand...
Click to collapse
I followed the procedure but I'm not clear that I downgraded correctly. No when I look at my system update, it says I am on 14.3.0.0_user_300079820. I thought I was supposed to be on 14.3.1.0_user_310079820? The file I downloaded from the thread is indeed "update-kindle-14.3.1.0_user_310079820.bin". Is there something else I need to do to downgrade before updating the bootloader?
rootnooby said:
I followed the procedure but I'm not clear that I downgraded correctly. No when I look at my system update, it says I am on 14.3.0.0_user_300079820. I thought I was supposed to be on 14.3.1.0_user_310079820? The file I downloaded from the thread is indeed "update-kindle-14.3.1.0_user_310079820.bin". Is there something else I need to do to downgrade before updating the bootloader?
Click to expand...
Click to collapse
I checked the rollback.zip for Apollo, it seems to be in the build.prop file, so nothing to worry about.
Now you should install TWRP via adb, update the 3.2.3.2 bootloader in TWRP, and finally unlock the bootloader.
Be sure to root and disable OTA via HDXToolkit, and enable USB debugging in Fire OS, before you flash TWRP.
And be sure to create a backup of Fire OS in TWRP before you flash any custom ROM.
Thanks. Is there a link outlining the steps to install twrp via add? Sorry for the need to have my hand held through this!
rootnooby said:
Thanks. Is there a link outlining the steps to install twrp via add? Sorry for the need to have my hand held through this!
Click to expand...
Click to collapse
You must have Minimal ADB and Fastboot installed, download the Apollo TWRP Image here, copy it to the root of the sdcard (i.e. the directory you see in Explorer when you connect the HDX to your PC, so don't open any directory there),then you open a DOS box, change dir to the adb directory (enter cd\adb), then execute the commands mentioned in the TWRP thread with the correct file name for the Apollo TWRP image.
Thanks so much. I'll give it a go tonight.
rootnooby said:
Thanks so much. I'll give it a go tonight.
Click to expand...
Click to collapse
looks like I got through everything except the last remaining step of unlocking the bootloader. I confirmed that I am rooted and OTA is blocked. Not sure how to get this unlocked so I can finally have a real ROM!
rootnooby said:
looks like I got through everything except the last remaining step of unlocking the bootloader. I confirmed that I am rooted and OTA is blocked. Not sure how to get this unlocked so I can finally have a real ROM!
Click to expand...
Click to collapse
OK, so you have Minimal ADB and Fastboot installed, unlocking the bootloader is really simple (with a little knowledge about command prompts), so download these drivers you need to install when the good ol' "waiting for device" issue occurs (check device manager then, the HDX probably has a yellow exclamation mark there).
You must download the software and the Python script mentioned here, and then follow the path outlined there, or (after installation of the required software) also here. Basically you just need to open a couple of command prompts (DOS boxes), change dir to the adb directory (enter cd\adb - or cd\python27 to go to the Python directory), then get the ID and serial, use the Python script with them, and finally execute the fastboot commands to unlock the bootloader.
That's it - and it's a no brainer, you can't mess up anything, if the unlock code is incorrect, it just won't flash (well, you must enter the fastboot commands correctly of course).
Cl4ncy said:
OK, so you have Minimal ADB and Fastboot installed, unlocking the bootloader is really simple (with a little knowledge about command prompts), so download these drivers you need to install when the good ol' "waiting for device" issue occurs (check device manager then, the HDX probably has a yellow exclamation mark there).
You must download the software and the Python script mentioned here, and then follow the path outlined there, or (after installation of the required software) also here. Basically you just need to open a couple of command prompts (DOS boxes), change dir to the adb directory (enter cd\adb - or cd\python27 to go to the Python directory), then get the ID and serial, use the Python script with them, and finally execute the fastboot commands to unlock the bootloader.
That's it - and it's a no brainer, you can't mess up anything, if the unlock code is incorrect, it just won't flash (well, you must enter the fastboot commands correctly of course).
Click to expand...
Click to collapse
Thanks. Running into an error creating the unlock file. I installed python, but I don't think i installed gmpy2-2.0.7-cp27-none-win_amd64.whl (md5) properly. The error I'm getting when I run the following command "python.exe cuberHDX.py 0xmmssssssss" "is "no module named gmpy2". I am using my correct code in the previous command. When I downloaded the gmpy2-2.0.7-cp27-none-win_amd64.whl (md5), I copied into the Python27 directory. Not sure if this is correct.
rootnooby said:
Thanks. Running into an error creating the unlock file. I installed python, but I don't think i installed gmpy2-2.0.7-cp27-none-win_amd64.whl (md5) properly. The error I'm getting when I run the following command "python.exe cuberHDX.py 0xmmssssssss" "is "no module named gmpy2". I am using my correct code in the previous command. When I downloaded the gmpy2-2.0.7-cp27-none-win_amd64.whl (md5), I copied into the Python27 directory. Not sure if this is correct.
Click to expand...
Click to collapse
Try to use the exe installer for 2.0.6 from here. If it still fails, PM me your ID and serial, I'll create the .unlock file for you then.
Cl4ncy said:
Try to use the exe installer for 2.0.6 from here. If it still fails, PM me your ID and serial, I'll create the .unlock file for you then.
Click to expand...
Click to collapse
Thanks. It worked. I now have an unlock code. I'm not clear where my fastboot directory is? It says I need to "copy that file to your fastboot directory" before i run the commands. Would that just be the root of the kindle itself? Sorry for the question.
rootnooby said:
Thanks. It worked. I now have an unlock code. I'm not clear where my fastboot directory is? It says I need to "copy that file to your fastboot directory" before i run the commands. Would that just be the root of the kindle itself? Sorry for the question.
Click to expand...
Click to collapse
If you installed Minimal ADB and Fastboot, it's the adb directory (e.g. C:\adb), you should have fastboot.exe in there as well. Just copy/move the .unlock file in the adb directory, open two DOS boxes, enter cd\adb in both,
then enter adb reboot-bootloader in the first one,
and the fastboot commands
fastboot -i 0x1949 devices
fastboot -i 0x1949 flash unlock 0xmmssssssss.unlock (mm=your ID, ssssssss=your serial)
fastboot -i 0x1949 reboot
in the second (again: if you see "waiting for device" on the fastboot prompt, install these drivers in device manager for the HDX (probably sitting there with a yellow exclamation mark).
Cl4ncy said:
If you installed Minimal ADB and Fastboot, it's the adb directory (e.g. C:\adb), you should have fastboot.exe in there as well. Just copy/move the .unlock file in the adb directory, open two DOS boxes, enter cd\adb in both,
then enter adb reboot-boorloader in the first one,
and the fastboot commands
fastboot -i 0x1949 devices
fastboot -i 0x1949 flash unlock 0xmmssssssss.unlock (mm=your ID, ssssssss=your serial)
fastboot -i 0x1949 reboot
in the second (again: if you see "waiting for device" on the fastboot prompt, install these drivers in device manager for the HDX (probably sitting there with a yellow exclamation mark).
Click to expand...
Click to collapse
Wow. I think it all worked! Assuming that's it. I can go ahead and load ROMs!
rootnooby said:
Wow. I think it all worked! Assuming that's it. I can go ahead and load ROMs!
Click to expand...
Click to collapse
If it looked like this, i.e. unlock code is correct, then yes.
Enjoy your "free" HDX.
yes, it does look like that so I have unlocked successfully! I ran a backup using twrp, and that worked well. One problem I'm having now is that my computer doesn't seem to recognize the Kindle when connected via USB any more. I'm getting a message that says some candles are not compatible and a separate file needs to be downloaded. When I go to the Kindle support website, this is applicable for older systems running Windows XP. Have you seen this problem before? Now that I have a backup I want to move it over to my PC so I don't use all that storage.
rootnooby said:
yes, it does look like that so I have unlocked successfully! I ran a backup using twrp, and that worked well. One problem I'm having now is that my computer doesn't seem to recognize the Kindle when connected via USB any more. I'm getting a message that says some candles are not compatible and a separate file needs to be downloaded. When I go to the Kindle support website, this is applicable for older systems running Windows XP. Have you seen this problem before? Now that I have a backup I want to move it over to my PC so I don't use all that storage.
Click to expand...
Click to collapse
Yes, it seems that the drivers required for fastboot cause such a problem, remove them in device manager (select to delete the driver files), then dis- and re-connect the HDX, so the original HDX drivers will be re-installed. Should do the trick in this case.