[Q] Help: Failed Kindle Fire 6.3 rooting/ fastboot problems (Linux), and ROM choice
Hello, everyone!
I have a Kindle Fire running OS 6.3, and I've decided to root it so I can use custom ROMs, and have access to the Google Market from the Caribbean.
Despite lots of reading and several attempts, I haven't been successful in my attempts to root my Kindle Fire from my Linux laptop. (Ubuntu 12.04.)
I've set up and rechecked adb and fastboot as outlined on this page:
http://androidforums.com/i7500-all-things-root/32481-howto-linux-adb-fastboot-mass-storage.html
And I've been trying the rooting method outlined in this thread:
http://forum.xda-developers.com/showthread.php?t=1568340
ADB successfully sees my device, as confirmed when I type
./adb devices
into my terminal with the KF attached to my USB cable.
The first set of adb commands seems to work fine:
adb push fbmode /data/local/fbmode
adb shell chmod 755 /data/local/fbmode
adb shell /data/local/fbmode
adb reboot
...but the first fastboot command doesn't seem to do anything- I get "waiting for device" and nothing more.
I should note that "fastboot devices" command doesn't result in any output from the terminal.
What should I do next?
Also, what recommendations for a custom ROM can you folks suggest?
I am an avid reader and a gamer. I may watch some YouTube videos or sitcom reruns, but hi-def video isn't important to me at all; neither the Fire's storage nor my bandwidth are well suited to HD.
I'm currently looking at MoDaCo and MIUI.
thanks in advance,
adrian.
Any ideas, anyone?
Try turning your device off then restarting after you see the <waiting for device>
If that doesn't work you can still use adb to root your device before installing TWRP and FireFireFire. (just skip the fastboot steps)
After you are rooted you can use "Gscripts" to install FireFireFire and custom recovery
Sent from my Amazon Kindle Fire using xda premium
Just curious, what are the exact fastboot commands you are using; exactly how you typed them.
Sent from my Amazon Kindle Fire using xda premium
If you followed that guide to set up your udev rules, it may be insufficient to get it working with adb. Try this Kindle Fire specific guide...
http://forum.xda-developers.com/showthread.php?t=1475740
As for fastboot, you'll probably need elevated privileges to get that working. Switch to root or use sudo when executing fastboot commands.
Thanks for the replies!
I'm trying the suggestions now, detailed responses to follow.
Reply
The ADB commands went fine, as before.
The first Fastboot command
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
seemed also to succeed, giving OKAY status reports for downloading and booting, and ending with the feedback "finished".
The Kindle Fire then booted into recovery; I pressed the Reboot button, and the device was "stuck" on the Yellow Triangle. This is the first time I've seen this- I think it may be because I edited the adb_usb.ini file tonight.
Anyway, when I entered
fastboot oem idme bootmode 5002
I only got the "waiting for device" response.
Power cycling didn't make any difference.
I checked my adb_usb.ini and udev rules files, and they look fine.
guttaperk said:
Reply
The ADB commands went fine, as before.
The first Fastboot command
fastboot -i 0x1949 boot twrp-blaze-2.0.0RC0.img
seemed also to succeed, giving OKAY status reports for downloading and booting, and ending with the feedback "finished".
The Kindle Fire then booted into recovery; I pressed the Reboot button, and the device was "stuck" on the Yellow Triangle. This is the first time I've seen this- I think it may be because I edited the adb_usb.ini file tonight.
Anyway, when I entered
fastboot oem idme bootmode 5002
I only got the "waiting for device" response.
Power cycling didn't make any difference.
I checked my adb_usb.ini and udev rules files, and they look fine.
Click to expand...
Click to collapse
Turn off the device. Run the fastboot command (you'll probably want bootmode 4000 to get to normal) just before powering the device up again. fastboot will tell you that it's waiting for device and it will send the command when FireFireFire goes into temporary fastboot mode. Then you can run the fastboot reboot command and it should boot to your system. Since you have FFF loaded, you can always get to recovery by pressing power during startup without using bootmode 5001 (not sure if 5002 will work anyway).
kinfauns said:
Turn off the device. Run the fastboot command (you'll probably want bootmode 4000 to get to normal) just before powering the device up again. fastboot will tell you that it's waiting for device and it will send the command when FireFireFire goes into temporary fastboot mode. Then you can run the fastboot reboot command and it should boot to your system. Since you have FFF loaded, you can always get to recovery by pressing power during startup without using bootmode 5001 (not sure if 5002 will work anyway).
Click to expand...
Click to collapse
It didn't work. But, I booted into Windows and got KFU to switch the KF to normal boot mode, so that's OK.
So, I now have FFF. But:
adb shell mount system
results in
Usage: mount [-r] [-w] [-o options] [-t type] device directory
and
adb push su /system/xbin/su
results in a warning that I don't have write access.
What should I do from here?
guttaperk said:
It didn't work. But, I booted into Windows and got KFU to switch the KF to normal boot mode, so that's OK.
So, I now have FFF. But:
adb shell mount system
results in
Usage: mount [-r] [-w] [-o options] [-t type] device directory
and
adb push su /system/xbin/su
results in a warning that I don't have write access.
What should I do from here?
Click to expand...
Click to collapse
That mount command should work in TWRP 2.0.0. I'm guessing that you are trying this while booted into the system or another version of TWRP. This one should work better in a wider range of situations....
Code:
adb shell mount -o remount,rw /system
The same problem
Hi, I have the same problem.
I stuck in the command
fastboot -i 0x1949 flash bootloader fire.zip
ok
fastboot -i 0x1949 flash recovery twrp.img
ok
fastboot reboot
My kindle fire reboot but i don't see any thing, the screen has not thing, not yellow triangle.
I hold on the power button 20s to restart. Then the power botton did not come red. My kindle fire not power on.
The adb command did not work.
The fastboot say: wait for devices
Please help me!
trungblc said:
Hi, I have the same problem.
fastboot -i 0x1949 flash bootloader fire.zip
Click to expand...
Click to collapse
This is where you screwed up. You need to read about what you are installing BEFORE you install it. The above named file is in .zip format. The newest version of FireFireFire was put in a .zip format for flashing in recovery.
If you use the "fastboot flash bootloader" command, you can only flash files in a .bin format. You now have a broken bootloader resulting in one of the hardest of bricks.
Research Firekit LiveUSB because that's your only hope at this point.
And let this be a lesson to anyone who wants to make ANY modification to their bootloader...Pay attention!
Thanks you so much
Thanks you so much. I will try and post the result soon.
I've owned you a beer now
Sorry to hear about your trouble trungblc at least you have two of the very best here watching your thread kinfauns and soupmagnet if anyone can get you out of a brick like this it would be them for sure good luck
Update status
I had used Firekit LiveUSB, and short the CPU method.
[email protected]:~/firekit# usb_fix_parts_and_install_fff_twrp
Loading FFF through USB...
?
waiting for OMAP44xx device...
sending 2ndstage to target...
waiting for 2ndstage response...
sending image to target...
Fixing partitions...
< waiting for device >
...
OKAY [ 0.073s]
finished. total time: 0.073s
Installing x-loader...
sending 'xloader' (128 KB)...
FAILED (status read failed (Protocol error))
finished. total time: 55.162s
Flash FFF...
sending 'bootloader' (211 KB)...
FAILED (status read failed (No such device))
finished. total time: 211.638s
Flash TWRP...
< waiting for device >
After that, kindle boot in TWRP, but when i reboot, it still not power on.
Have you tried holding the power button for 30 seconds and trying again?
Oh.
soupmagnet said:
Have you tried holding the power button for 30 seconds and trying again?
Click to expand...
Click to collapse
Oh holding for 30s? I had tried with 20s. But kindle fire still not power on.
I will try again now
Pls help me more.
[email protected]:~/firekit# usb_fix_parts_and_install_fff_twrp
Loading FFF through USB...
?
waiting for OMAP44xx device...
sending 2ndstage to target...
waiting for 2ndstage response...
sending image to target...
Fixing partitions...
< waiting for device >
...
OKAY [ 0.072s]
finished. total time: 0.072s
Installing x-loader...
sending 'xloader' (128 KB)...
OKAY [ 0.036s]
writing 'xloader'...
OKAY [ 0.279s]
finished. total time: 0.314s
Flash FFF...
sending 'bootloader' (211 KB)...
OKAY [ 0.057s]
writing 'bootloader'...
OKAY [ 0.042s]
finished. total time: 0.099s
Flash TWRP...
sending 'recovery' (5260 KB)...
OKAY [ 1.319s]
writing 'recovery'...
OKAY [ 4.118s]
finished. total time: 5.437s
Resetting bootmode to standard boot...
...
OKAY [ 0.079s]
finished. total time: 0.079s
Loading TWRP...
downloading 'boot.img'...
OKAY [ 1.319s]
booting...
OKAY [ 0.004s]
finished. total time: 1.323s
In the TWRP, I mount the SDCARD and copy the amazon update.zip (rename from update-6.2.1.bin) to sdcard. The install - Flash - Reboot.
The Kindle Fire still not power on. I really don't know why.
It appears you did all the right stuff with the firekit but then you wiped that out by installing stock 6.2.1 are you getting the fff screen ? Can you still get into twrp? Shame you got that far with the firekit only to put yourself in the same situation might wanna try the firekit again
Thepooch said:
It appears you did all the right stuff with the firekit but then you wiped that out by installing stock 6.2.1 are you getting the fff screen ? Can you still get into twrp? Shame you got that far with the firekit only to put yourself in the same situation might wanna try the firekit again
Click to expand...
Click to collapse
I had been tried to do that before. I just pressed reboot button when it gets into TWRP many times but nothing happened. After that, I had tried to flash room again but still the same.
I don't know why.
I am so frustrated. I tried rooting the kindle last week and it went into an endless loop of turning on and off. So I ordered a factory cable and when I plugged it in, it stayed on and fastboot recognized the device.
I tried a few commands and now it's turning on and off again! I can no longer get commands to read the device through fastboot.
what the hell do I do?
EDIT: Sorry I forgot to check off "this thread is a question"
Ok so if I leave the tablet unplugged for a while and replug it, I can send a command and have it go through before the tablet resets again.
But I don't know how to get it to stay in fastboot mode, and I don't know what to do once i'm actually IN fastboot mode (I dont have TWRP or whatever installed).
Any help is appreciated
EDIT: I tried this command:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot -i 0x1949 boot c:\twrp-fire-2.1.0.img
creating boot image...
creating boot image - 10240 bytes
< waiting for device >
downloading 'boot.img'...
FAILED (command write failed (No such file or directory))
finished. total time: 0.005s
Hmmm did you try the kfu or the kindle fire unbrick utility?
Step-by-step
1) Make sure you have some charge left in your bricked Kindle. (one of my mistakes
2) Download "Kindle Fire Utility" or other utility that has the fastboot.exe command available.
3) Download twrp-blaze-2.0.0RC0.img (just google it)
4) Without connecting anything, run the command:
fastboot.exe -i 0x1949 boot twrp-blaze-2.0.0RC0.img
5) Connect the factory cable to your Kindle Fire
6) Connect the factory cable to you PC
7) Wait about 10 seconds.
8) DONE!!!!
all these steps above taken from http://forum.xda-developers.com/showthread.php?p=25113108&posted=1#post25113108
the OP deserves the credit if this works for you
You're doing it wrong. Unlike TWRP 2.0.0RC0, 2.1.0 is not supposed to be loaded into boot and your system is probably panicking. You need a bootloader first.
First you need a bootloader with recovery selection. There are several to choose from at this point.
I would recommend FIREFIREFIRE 1.3 or 1.2
Download one of them and extract the bin somewhere. Lets say c:\firebuild\
Next we need a recovery partition, you already have that in the twrp-fire-2.1.0.img, so you should be set. Copy that to c:\firebuild\ as well.
Now, lets make sure you have the andriod sdk in your path. This way you don't have to be in the C:\Program Files (x86)\Android\android-sdk\platform-tools folder to run commands and your images can be elsewhere.
1. right click on computer and select properties.
2. click on advanced settings on the left of the window.
3. click on environment variables at the bottom right of the window.
4. in the system variables section scroll down until you find path, highlight it, and select edit.
5. paste the following at the end of the line.
Code:
;C:\Program Files (x86)\Android\android-sdk\platform-tools;C:\Program Files (x86)\Android\android-sdk\tools;
For example, my path is:
Code:
C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;;C:\Program Files\Lucidlogix Technologies\VIRTU;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files (x86)\Android\android-sdk\platform-tools;C:\Program Files (x86)\Android\android-sdk\tools;
Now that your path is set, lets go into the command prompt.
First lets change the directory to c:\firebuild\ :
Code:
cd c:\firebuild
In this folder we should have u-boot.bin and twrp-fire-2.1.0.img.
First lets load your bootloader.
Code:
fastboot -i 0x1949 flash bootloader u-boot.bin
and start your device.
I would recommend rebooting after flashing this, so run
Code:
fastboot reboot
if it does not reboot on its own.
Now lets run
Code:
fastboot flash recovery twrp-fire-2.1.0.img
Note: Because we have the bootloader now the -i 0x1949 is no longer needed.
After running the above, the kindle should automatically start into recovery.
From here you will be able to mount it as an external drive and copy over any rom you would like to use.
Pick something from here Kindle Fire Development *FULL LIST* - 17.04.2012 - under the Custom / Stock Roms section.
three-p-o said:
You're doing it wrong. Unlike TWRP 2.0.0RC0, 2.1.0 is not supposed to be loaded into boot and your system is probably panicking. You need a bootloader first.
First you need a bootloader with recovery selection. There are several to choose from at this point.
I would recommend FIREFIREFIRE 1.3 or 1.2
Download one of them and extract the bin somewhere. Lets say c:\firebuild\
Next we need a recovery partition, you already have that in the twrp-fire-2.1.0.img, so you should be set. Copy that to c:\firebuild\ as well.
Now, lets make sure you have the andriod sdk in your path. This way you don't have to be in the C:\Program Files (x86)\Android\android-sdk\platform-tools folder to run commands and your images can be elsewhere.
1. right click on computer and select properties.
2. click on advanced settings on the left of the window.
3. click on environment variables at the bottom right of the window.
4. in the system variables section scroll down until you find path, highlight it, and select edit.
5. paste the following at the end of the line.
Code:
;C:\Program Files (x86)\Android\android-sdk\platform-tools;C:\Program Files (x86)\Android\android-sdk\tools;
For example, my path is:
Code:
C:\Program Files (x86)\NVIDIA Corporation\PhysX\Common;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;;C:\Program Files\Lucidlogix Technologies\VIRTU;C:\Program Files (x86)\QuickTime\QTSystem\;C:\Program Files (x86)\Android\android-sdk\platform-tools;C:\Program Files (x86)\Android\android-sdk\tools;
Now that your path is set, lets go into the command prompt.
First lets change the directory to c:\firebuild\ :
Code:
cd c:\firebuild
In this folder we should have u-boot.bin and twrp-fire-2.1.0.img.
First lets load your bootloader.
Code:
fastboot -i 0x1949 flash bootloader u-boot.bin
and start your device.
I would recommend rebooting after flashing this, so run
Code:
fastboot reboot
if it does not reboot on its own.
Now lets run
Code:
fastboot flash recovery twrp-fire-2.1.0.img
Note: Because we have the bootloader now the -i 0x1949 is no longer needed.
After running the above, the kindle should automatically start into recovery.
From here you will be able to mount it as an external drive and copy over any rom you would like to use.
Pick something from here Kindle Fire Development *FULL LIST* - 17.04.2012 - under the Custom / Stock Roms section.
Click to expand...
Click to collapse
Thank you SO MUCH! I was able to get both files on. I don't know how to get into recovery, but here is the output:
c:\firebuild>fastboot -i 0x1949 flash bootloader u-boot.bin
< waiting for device >
sending 'bootloader' (203 KB)...
OKAY [ 0.055s]
writing 'bootloader'...
OKAY [ 0.051s]
finished. total time: 0.106s
c:\firebuild>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.002s
c:\firebuild>fastboot flash recovery twrp-fire-2.1.0.img
sending 'recovery' (6 KB)...
OKAY [ 0.006s]
writing 'recovery'...
OKAY [ 0.045s]
finished. total time: 0.051s
c:\firebuild>fastboot -i 0x1949 reboot
rebooting...
finished. total time: 0.003s
c:\firebuild>fastboot -i 0x1949 boot twrp-fire-2.1.0.img
creating boot image...
creating boot image - 10240 bytes
downloading 'boot.img'...
OKAY [ 0.006s]
booting...
OKAY [ 0.003s]
finished. total time: 0.010s
When you first turn the kindle on you will get a yellow triangle (FFF 1.2) or a Kundle Fire logo with the Android (FFF 1.3). When in that screen tap the power button until it turns orange. It should then boot you into TWRP.
From there you can goto mount and then click mount usb storage, this will allow you to copy the rom you picked to the SDCard.
After copied, unmount, then goto install and select to install the rom.
Oh, one more thing. Don't forget to wipe cache, dalvik-cache, and factory restore.
How to Gain S-OFF on the HTC Droid Incredible 2
After you have S-OFF, you can root it, or install a custom rom, like CyanogenMod 9
Please don't forget to rate and thank the thread so I can get this stickied!
UPDATES:
July 25th
For all those people receiving ERROR 43 codes please read. Note that this is just a test so it may not work. In the attached files I have a flash-able .zip file (SetMainVersionLOW.zip) that should set your misc_version to 1.00.000 and allow and RUU to be flashed to the phone. Just boot into recovery and flash the file from the root of your sd card. I have not been able to test this as I am already s-off so anyone that tries this please provide feedback =D
July 23rd
Updated the downgrading process for better clarity and fixed a file name. Also updated the RUU download link.
June 28th
In step n. (where you flash the RUU file be aware that in the name there is a space in the word radio. Please delete this space as it is not supposed to be there. (for some reason i am unable to remove the space.)
June 20th, 2012
A few people have reported to me that they are running sense roms without the vicious bootloops! This could just be luck of the draw, however I am looking into the stability of this phenomenon. (I did experince the wrath of bootloops after downgrading myself, but fixed the issue with ease by flashing an AOSP rom)
June 27th, 2012
IF ANY DEVS NEED THE 6.01.605.05 PLEASE PM ME. I NOW HAVE THE SYSTEM FOLDER!
DISCLAIMER:
This process will void the worthless warranty on your Incredible 2. If you read all the steps first before doing this, then do it following every step very carefully, I can guarantee you that your phone will be just fine. I recommend doing this in Linux, because it works best that way, but it can be done in Windows... it's just harder and there is a greater chance you will run into problems. I also understand that this guide has been posted elsewhere by me but i feel it will be more useful under the development section. There are other guides on this but i feel they are outdated and cause quite a bit of confusion to some members, so i tried to clear a few bits and pieces as best i could :victory:
1. Setup
Download both the misc_version and tacoroot.sh files that are attached, you also need the RUU 2.3.3 File which can be found here
Windoze users:
a. Uninstall anything that is HTC related on your computer, such as HTC Sync.
b. Install the HTC Drivers at this link: http://downloads.unr...er3.0.0.007.exe
Linux Users:
a. Install the ia32-libs package. If you are on Ubuntu or Debian, type this in the terminal:
Code:
sudo apt-get install ia32-libs
c. ALL THESE STEPS ARE ASSUMING YOU ARE USING COMMAND PROMPT AS ADMINISTRATOR (open start menu and type cmd, the right click<run as administrator)
d. DISABLE FASTBOOT in Settings/Power (possibly causes bootloops with tacoroot)
e. Turn on USB Debugging in under Settings > Applications > Development > USB Debugging
f. Place the misc_version and tacoroot.sh into your /Android/android-sdk/Platform-tools folder. (platform-tools may also just be named platform, depends on which sdk version you have)
g. Place the RUU_Vivo.....zip folder in the /Android/android-sdk/tools folder. (Leave it as a .zip file, do NOT extract the contents to the tools folder)
2. Tips
Here are a couple tips you may want to try that could possibly help the process run smoother.
-Make sure you have a SD card in your SD card slot and its mounted.
-Between each script wait 5-10 seconds after the previous script has completed before moving on to the next step.
-After each phone reboot, wait for the phone to completely reboot and start up before proceeding to the next step.
-Run in 'Charge Mode Only'
-Back up your SD card and Format it.
3. Downgrading
a. In cmd type cd C:\Program Files (x86)\Android\android-sdk\platform
(your destination folder may be different, but you want to use the file path for where ever your Platform-tools or platform folder is. In this case mine is in my local directory under platform not Platform-tools)
b. adb push tacoroot.sh /data/local/
c. adb shell chmod 755 /data/local/tacoroot.sh
d. adb shell /data/local/tacoroot.sh --setup
d1. This should boot your phone into recovery, when you see the red exclamation mark, hit Volume Up and Power to get into the stock recovery, once in stock recovery, HOLD Volume Up Volume Down and Power to force reboot the phone.
e. adb shell /data/local/tacoroot.sh --root
e1. Wait for the phone to reboot back up, if everything worked up until now, adb should have root (you can try by typing 'adb shell' and seeing if you get a #, if you do this means tacoroot was successful in gaining a tmp reoot, type 'exit' to get out of shell mode)
===side note=== Your device may bootloop after this process, if it does don't be alarmed its normal.
f. adb push misc_version /data/local/tmp/misc_version
g. adb shell chmod 777 /data/local/tmp/misc_version
h. adb shell sh -c '/data/local/tmp/misc_version -s 2.18.605.3'
i. adb shell /data/local/tacoroot.sh --undo
j. adb reboot bootloader
k. Now we want to change directories to the tools folder so type cd C:\Android\android-sdk\tools (again, this file path will differ for you depending on where your android tools folder is located)
l. fastboot oem rebootRUU
m. fastboot erase cache
n. fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip
(If you are having problems with this step please refer to the UPDATES section at the beginning of the post!)
o. fastboot reboot
4. Gaining S-Off
WARNING! This will void your warranty... but, it's not yours till you void the warranty.
a. Download revolutionary from here.
b. Run revolutionary. It should do all the work for you. Just get a beta key on the website.
c. Revolutionary should ask you if you want to flash ClockworkMod when it's done. Say yes if you want it. (your going to want it!)
Troubleshooting
IF: you get an error that looks something like
Code:
FAILED (remote: 43 main version check fail)
THEN: This is a error related to the misc_version not being properly "replaced". In many cases people have forgotten to use the code "adb push misc_version /data/local/tmp/misc_version" which took care of the problem for the most part. Still troubleshooting methods to get around the error for people that cannot get it to work, check back later.
IF: you get
Code:
Unable to chmod /data/local/misc_version: No such file or directory
THEN: This again is with the misc_version not being placed properly. (Where many errors will occur). If this error happens to you try using steps f and g without the tmp. So it would look like this
f. adb push misc_version /data/local/misc_version
g. adb shell chmod 777 /data/local/misc_version
IF: You get an error stating something along the lines of 99 version check fail
THEN: You must have an unlocked bootloader and must relock it. To do this type "fastboot oem lock"
IF: you still can't get the misc_version steps to work
THEN: You can manually change the version by looking at this great post by drellisdee here
Below is what a successful downgrade should look like after finished
Code:
C:\Program Files (x86)\Android\android-sdk\tools>cd C:\Program Files (x86)\Andro
id\android-sdk\platforms
C:\Program Files (x86)\Android\android-sdk\platforms>adb push tacoroot.sh /data/
local
297 KB/s (2129 bytes in 0.007s)
C:\Program Files (x86)\Android\android-sdk\platforms>adb shell chmod 755 /data/l
ocal/tacoroot.sh
C:\Program Files (x86)\Android\android-sdk\platforms>adb shell /data/local/tacor
oot.sh --setup
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg first). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into recovery, please press Volume+, Volume- and Power at the same tim
e, and reboot the system.
C:\Program Files (x86)\Android\android-sdk\platforms>adb shell /data/local/tacor
oot.sh --root
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg first). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Rebooting into root.
C:\Program Files (x86)\Android\android-sdk\platforms>adb push misc_version /data
/local/tmp/misc_version
1896 KB/s (367096 bytes in 0.189s)
C:\Program Files (x86)\Android\android-sdk\platforms>adb shell chmod 777 /data/l
ocal/tmp/misc_version
C:\Program Files (x86)\Android\android-sdk\platforms>adb shell sh -c '/data/loca
l/tmp/misc_version -s 2.18.605.3'
--set_version set. VERSION will be changed to: 2.18.605.3
Patching and backing up misc partition...
C:\Program Files (x86)\Android\android-sdk\platforms>adb shell /data/local/tacor
oot.sh --undo
TacoRoot: HTC Edition v1
By Justin Case (jcase)
Presented by TeamAndIRC, RootzWiki and AndroidPolice
With great assistance from Reid Holland (Erishasnobattery)
----------
TacoRoot: HTC Edition v1 is based on a vulnerability independently discovered by
both Justin Case and Dan Rosenberg (Rosenberg first). I believe unrevoked and
AlpahRev were also aware of it.
----------
Usage:
--recovery : For this exploit to work, you must have booted recovery at least on
ce after your last factory reset.
--setup : Setup the phone for root, must be done before --root.
--root : Root the phone.
--undo : Remove TacoRoot.
----------
Root removed, rebooting
C:\Program Files (x86)\Android\android-sdk\platforms>adb reboot bootloader
C:\Program Files (x86)\Android\android-sdk\platforms>cd C:\Program Files (x86)\A
ndroid\android-sdk\tools
C:\Program Files (x86)\Android\android-sdk\tools>fastboot oem rebootRUU
... OKAY [ 0.147s]
finished. total time: 0.147s
C:\Program Files (x86)\Android\android-sdk\tools>fastboot erase cache
erasing 'cache'... OKAY [ 0.117s]
finished. total time: 0.117s
C:\Program Files (x86)\Android\android-sdk\tools>fastboot flash zip RUU_Vivo_W_G
ingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487
_si.zip
sending 'zip' (292817 KB)... OKAY [ 48.539s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOchecking custom ID...
INFOchecking main version...
INFOstart image[hboot] unzipping for pre-update check...
INFOstart image[hboot] unzipping & flushing...
INFO[RUU]UZ,hboot,0
INFO[RUU]UZ,hboot,100
INFO[RUU]WP,hboot,0
INFO[RUU]WP,hboot,100
INFOstart image[boot] unzipping & flushing...
INFO[RUU]UZ,boot,0
INFO[RUU]UZ,boot,31
INFO[RUU]UZ,boot,73
INFO[RUU]UZ,boot,100
INFO[RUU]WP,boot,0
INFO[RUU]WP,boot,99
INFO[RUU]WP,boot,100
INFOstart image[recovery] unzipping & flushing...
INFO[RUU]UZ,recovery,0
INFO[RUU]UZ,recovery,22
INFO[RUU]UZ,recovery,43
INFO[RUU]UZ,recovery,63
INFO[RUU]UZ,recovery,84
INFO[RUU]UZ,recovery,100
INFO[RUU]WP,recovery,0
INFO[RUU]WP,recovery,99
INFO[RUU]WP,recovery,100
INFOstart image[system] unzipping & flushing...
INFO[RUU]UZ,system,0
INFO[RUU]UZ,system,5
INFO[RUU]UZ,system,8
INFO[RUU]UZ,system,13
INFO[RUU]UZ,system,16
INFO[RUU]UZ,system,22
INFO[RUU]UZ,system,25
INFO[RUU]UZ,system,31
INFO[RUU]UZ,system,37
INFO[RUU]UZ,system,42
INFO[RUU]UZ,system,48
INFO[RUU]UZ,system,53
INFO[RUU]UZ,system,56
INFO[RUU]UZ,system,61
INFO[RUU]UZ,system,65
INFO[RUU]WP,system,0
INFO[RUU]WP,system,5
INFO[RUU]WP,system,8
INFO[RUU]WP,system,13
INFO[RUU]WP,system,16
INFO[RUU]WP,system,22
INFO[RUU]WP,system,25
INFO[RUU]WP,system,30
INFO[RUU]WP,system,33
INFO[RUU]WP,system,39
INFO[RUU]WP,system,42
INFO[RUU]WP,system,47
INFO[RUU]WP,system,50
INFO[RUU]WP,system,55
INFO[RUU]WP,system,59
INFO[RUU]WP,system,65
INFO[RUU]UZ,system,65
INFO[RUU]UZ,system,67
INFO[RUU]UZ,system,71
INFO[RUU]UZ,system,73
INFO[RUU]UZ,system,77
INFO[RUU]UZ,system,79
INFO[RUU]UZ,system,82
INFO[RUU]UZ,system,85
INFO[RUU]UZ,system,87
INFO[RUU]UZ,system,89
INFO[RUU]UZ,system,93
INFO[RUU]UZ,system,95
INFO[RUU]UZ,system,98
INFO[RUU]WP,system,65
INFO[RUU]WP,system,67
INFO[RUU]WP,system,70
INFO[RUU]WP,system,73
INFO[RUU]WP,system,76
INFO[RUU]WP,system,79
INFO[RUU]WP,system,82
INFO[RUU]WP,system,85
INFO[RUU]WP,system,88
INFO[RUU]WP,system,91
INFO[RUU]WP,system,94
INFO[RUU]WP,system,97
INFO[RUU]WP,system,100
INFOstart image[sp1] unzipping & flushing...
INFO[RUU]UZ,sp1,0
INFO[RUU]UZ,sp1,100
INFO[RUU]WP,sp1,0
INFO[RUU]WP,sp1,100
INFOstart image[dzdata] unzipping & flushing...
INFO[RUU]UZ,dzdata,0
INFO[RUU]UZ,dzdata,100
INFO[RUU]WP,dzdata,0
INFO[RUU]WP,dzdata,100
INFOstart image[tp] unzipping & flushing...
INFO[RUU]UZ,tp,0
INFO[RUU]UZ,tp,100
INFO[RUU]WP,tp,0
INFOstart image[tp] unzipping & flushing...
INFO[RUU]UZ,tp,0
INFO[RUU]UZ,tp,100
INFOstart image[radio] unzipping & flushing...
INFO[RUU]UZ,radio,0
INFO[RUU]UZ,radio,7
INFO[RUU]UZ,radio,13
INFO[RUU]UZ,radio,21
INFO[RUU]UZ,radio,27
INFO[RUU]UZ,radio,34
INFO[RUU]UZ,radio,42
INFO[RUU]UZ,radio,48
INFO[RUU]UZ,radio,55
INFO[RUU]UZ,radio,62
INFO[RUU]UZ,radio,69
INFO[RUU]UZ,radio,76
INFO[RUU]UZ,radio,83
INFO[RUU]UZ,radio,90
INFO[RUU]UZ,radio,97
INFO[RUU]UZ,radio,100
INFO[RUU]WP,radio,0
INFO[RUU]WP,radio,5
INFO[RUU]WP,radio,12
INFO[RUU]WP,radio,19
INFO[RUU]WP,radio,26
INFO[RUU]WP,radio,33
INFO[RUU]WP,radio,42
INFO[RUU]WP,radio,100
OKAY [197.732s]
finished. total time: 246.272s
C:\Program Files (x86)\Android\android-sdk\tools>fastboot reboot
rebooting...
finished. total time: 0.144s
Hopefully this works for everyone as it did for me, If not feel free to PM me or post below with any further questions and i'll be happy to help
, also don't for get the push the THANKS button! :good:
Thank you for this!!!!!!!!!! The only issue I had was when you tell it to flash the ruu, where it says signed.zip, I looked at your list of a complete code and it was si.zip. So I changed it and somehow that made it work Again thanks a lot!
accord1 said:
Thank you for this!!!!!!!!!! The only issue I had was when you tell it to flash the ruu, where it says signed.zip, I looked at your list of a complete code and it was si.zip. So I changed it and somehow that made it work Again thanks a lot!
Click to expand...
Click to collapse
Hahah great! im glad it worked for you! :good:
Thanks for writing this up. I'm waiting on a warrantied replacement of my DInc 2 (the "1" on the alpha keyboard no longer works) and I'm a little concerned about rooting because of the need to downgrade (something that wasn't required when I rooted originally) but this makes it look fairly manageable.
My biggest concern? Making sure I hit the volume up AND down buttons in conjunction with the power button!
If someone could instead of just pulling the modules, do a pull of /system .....?
Sent from my vivow using xda premium
I just got my replacement and will try to pull this today. Will just need to look up how to first lol.
CondemnedSoul said:
If someone could instead of just pulling the modules, do a pull of /system .....?
Sent from my vivow using xda premium
Click to expand...
Click to collapse
I'm assuming from before we do anything? I have a replacement that should be at my house when I get home today, I'll be attempting this tonight. If you need me to pull something I can, just have to tell me how. Feel free to PM me.
adb pull /system (insert where to place it) then put it in a zip file
Sent from my vivow using xda premium
CondemnedSoul said:
adb pull /system (insert where to place it) then put it in a zip file
Sent from my vivow using xda premium
Click to expand...
Click to collapse
uploading to my dropbox now.
Orange Terror said:
uploading to my dropbox now.
Click to expand...
Click to collapse
Sweet, thanks!
Sent from my vivow using xda premium
so where is the RUU for this?
Edit, nevermind, I'm an idiot, just had to read
Orange Terror said:
so where is the RUU for this?
Edit, nevermind, I'm an idiot, just had to read
Click to expand...
Click to collapse
haha yeah i had to sneak it in there
if any of the devs need the 6.01.605.05 folder please pm me and i will send it to you.
Ok, I tried this, following the steps accordingly and my device is stuck in the HTC screen after
Code:
fastboot oem rebootRUU
and
Code:
fastboot erase cache
and when I try flashing it I get this:
Code:
error: cannot load 'RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487_signed.zip'
Any thoughts? should I try this from the start again?
cowboyv said:
Ok, I tried this, following the steps accordingly and my device is stuck in the HTC screen after
Code:
fastboot oem rebootRUU
and
Code:
fastboot erase cache
and when I try flashing it I get this:
Code:
error: cannot load 'RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Radio_1.09.01.0622_NV_VZW1.92_release_199487_signed.zip'
Any thoughts? should I try this from the start again?
Click to expand...
Click to collapse
For the
Code:
fastboot oem rebootRUU
and
Code:
fastboot erase cache
you should only see the HTC logo. This is normal. As for not being able to load the RUU file did you place it in your Android\android-sdk\tools folder?
dets34 said:
For the
Code:
fastboot oem rebootRUU
and
Code:
fastboot erase cache
you should only see the HTC logo. This is normal. As for not being able to load the RUU file did you place it in your Android\android-sdk\tools folder?
Click to expand...
Click to collapse
I'm also having an issue while running the command to flash the RUU file, I'm gonna try from scratch
Sent from my ADR6350 using xda app-developers app
dets34 said:
As for not being able to load the RUU file did you place it in your Android\android-sdk\tools folder?
Click to expand...
Click to collapse
Yep, I just opened it to make sure. I'm gonna start it from scratch following the steps again, will report once I'm done.
Stiil getting an error trying to load RUU file...
Edit: I think i got it! There were a couple spaces in the code that i didnt see
Triscuit said:
Stiil getting an error trying to load RUU file...
Edit: I think i got it! There were a couple spaces in the code that i didnt see
Click to expand...
Click to collapse
:good: let me know if it worked!
cowboyv said:
Yep, I just opened it to make sure. I'm gonna start it from scratch following the steps again, will report once I'm done.
Click to expand...
Click to collapse
double check your typing the file name correctly. its long and annoying to type :silly:. Also make sure you don't unzip it. (im sure you didn't, but just triple checking)
If it still doesn't work you may want to try to download the same RUU file but from a different source. Sometimes the files get corrupted and do not load correctly.