Develop Bugs

Maybe this can help for rooting the new sbf

1. How can I root my phone?
1.1 General information/Basic adb-commands
Rooting a phone enables you to do things, which normally aren't possible for the average user like:
- Removing apps which were preinstalled by the provider (like Orange, Vodafone, etc.). My Tattoo had Vodafone apps for buying music and other sh*t, which was installed on the system partition (to which a "normal" user has no rights to write to, including deleting).
The Tattoo was successfully rooted by a bunch of guys here, namely -bm-, mainfram3 and Coburn64 (maybe, I don't remember quite correctly ). Also the Tattoo was the first phone having a security mechanism hindering a user to mount the filesystems as read/write, which had to be overridden by remapping the read only memory region to a read/write one. This is done by the module Tattoo-hack.ko, also made by mainfram3. He also created the first boot.img, which enabled su directly from adb and loading Tattoo-hack directly from boot on.
A few words about adb:
ADB is a tool for communicating from the PC with the mobile phone. For this a service is running on the phone enabling the communication via Terminal Emulator. Here are the most useful adb-commands:
Code:
adb push localFileFromPC /path/on/mobilephone
-> pushes a file "localFileFromPC" to a specified location on the phone
adb pull /path/to/file pathFromPC
-> receives a file from the phone and stores it to "pathFromPC"
adb remount
-> This is only possible in custom ROMs, remounts the file system to r/w automatically
adb shell "command"
-> executes "command" and returns to the computer shell
adb shell
-> opens a shell session on the phone (from here on you have to be very careful! Also you can execute now normal linux commands like rm, mv, ls, chmod and so on, but not cp (this can done through busybox)). You will have to use this more often, so get used to it
1.2 Do I have to create a goldcard?
I read this question quite often. For rooting, you don't need it, but for SIM-locked phones you can't flash custom unbranded ROMs (I think).
A guide to create a goldcard follow this link: http://forum.xda-developers.com/show...88&postcount=1 (thanks to MiSSigNNo to this point)
1.3 Tools you need
A complete set of tools can be found here Feel free to mirror it:
http://rapidshare.com/files/403766494/Tattoo.rar.html
Mirror(s):
http://www.bild-ton.net/Tattoo.rar
http://www.megaupload.com/?d=CI9AW83F
This package contains:
- adb binaries for Windows (sorry Linux users )
- su (Please note: use the su-binary attached in this post, not the one in the archive!!!!!)
- m7 exploit
- Amon_RA recovery.img
- mainfram3 boot.img
- flash_image binary
- tattoo-hack.ko
1.4 The automated way
This method was created by maverixx and can be found here. This basically consists of a package doing everything you need by itself. It roots the phone and flashes maverixx recovery.img, which (no offense) I don't like as much as I like Amon_RA's one!). Just click the batchfile and it does the rest (you have to connect your phone via USB to your PC though ).
If you want to use the automated way, but flashing Amon_RA's recovery, just replace the recovery.img from maverixx' package with the recovery.img provided in my archive file (see 1.3 for the link).
In my time here I noticed quite a few users experiencing problems either with a fully functional su or with the recovery image not flashing certain update.zip packages. It seems to be a matter of luck.
1.5 The manual way (recommended by the author)
I personally like what is done when and how, that's why I recommend the manual way. So let's get down to business Let's see if you know all the adb-commands I wrote here:
1. Let's say you have everything unpacked into C:\Tattoo
2. In your terminal (on your PC) type:
- adb shell "mkdir /data/local/bin" (if it returns an error it means that the directory already exists, just proceed)
- adb push m7 /data/local/bin/
- adb push su /data/local/bin/
- adb push flash_image /data/local/bin/
- adb push tattoo-hack.ko /data/local/bin/
- adb push recovery.img /sdcard
- adb push boot.img /sdcard
3. We have every needed file on the phone now. Type now (we are still in your terminal):
- adb shell
$ cd /data/local/bin
$ chmod 766 m7 (I don't retain this step as mandatory, so if this process fails, just proceed)
$ while ./m7 ; do : ; done
lots of text until you see something like "wrote shell code", press enter 2 or 3 times enter to see:
#
4. Then perform this:
- # export LD_LIBRARY_PATH=/system/lib
- # export PATH=/system/bin
- # insmod ./tattoo-hack.ko
- # mount -o rw,remount /dev/block/mtdblock5 /data
- # mount -o rw,remount /dev/block/mtdblock3 /system
- # cat ./su > /system/bin/su
- # chmod 4755 /system/bin/su
- # chmod 755 ./flash_image
Questions?
1.6 Problems and (hopefully good) solutions
Q: How do I execute my command line tool?
A: On your Windows host, go to Start->Run...->type "cmd"
Q: Where is my adb? When I type it in my shell it says that it was not found!
A: The adb binary is found in the archive I supplied above or in the Google SDK. As my archive-file is quite smaller than the Google SDK you should take mine. Let's suppose your adb binary is unpacked in C:\Tattoo, then type:
Code:
Your\Current\Location> cd C:\Tattoo
C:\Tattoo> adb <command>Q: adb says "error: device not found" when I try to launch the shell on the phone!
A: Connect the phone with the usb cable and make sure the sd card is not mounted as drive on your PC!!!
Q: When I want to copy something the phone returns that "cp" is not found! Also when I try to move a file, it says "cross-link device".
A: Well, copying from one partition to another is only possible either via busybox or via
Code:
cat file > /location/filename
Example:
cp /data/su /system/bin
is realized by typing
cat /data/su > /system/bin/suAlso make sure that system is r/w!!!
Q: flash_image returns write errors when flashing recovery/boot image!
A:
For boot: Try to redo the flash procedure
For recovery: Note that you can't flash the same recovery.img as the one already installed, so install another recovery.img first (like maverixx) and then Amon_RA's again. If it still doesn't work reboot, remount the partitions r/w, insmod tattoo-hack.ko and retry flashing.
Q: How can I unroot my device?
A: Just delete su from /system/xbin and restore the old boot.img. Alternatively see here for retrieving a stock ROM to flash it on your phone.
i hope someone try this i don't have time

[HOWTO] (Manually) Rooting the Kindle Fire 2 with a Mac

Firstly, Merry Christmas!
Note: This worked on version 10.2.4
I received a Kindle Fire 2 today and since then I've been trying to get it rooted, now that I have I though I'd share it here for other people who might be in the same situation.
This is really just a remixing of the tool made by Bin4ry (http://forum.xda-developers.com/show....php?t=1886460) but I couldn't get the script to run on my Mac...
Step 0 - Preparing
You must enable ADB and Unknown App sources from Settings.
Settings > More > Security > Enable ADB
Settings > More > Device > Allow Installation of Applications
Step 1 is to get that tool from here. and extract it somewhere you'll remember.
Step 2 (you can skip this if you already have the android SDK platform-tools in your PATH)
If you don't have the android SDK or adb installed just add the 'stuff' folder from the tool to your path.
In terminal run
Code:
export PATH=$PATH:/path/to/extracted/tool/stuff/
Step 3 - Push the required files
It's probably easiest if you change into the stuff folder first...
Code:
cd /Users/x/Downloads/Root_with_Restore_by_Bin4ry_v18.7z\ Folder/stuff
Then run the following...
Code:
adb push busybox /data/local/tmp/.
adb push su /data/local/tmp/.
adb push Superuser.apk /data/local/tmp/.
adb push ric /data/local/tmp/ric
Then you need to run an adb shell to set some permissions
Code:
adb shell
(you should get a prompt like [email protected]:/)
Run
Code:
chmod 755 /data/local/tmp/busybox
exit
Step 4 - Rooting
This requires another terminal window. Check that you can run adb from there as well (running adb should print the usage information)
In the first window run:
Code:
adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done" > /dev/null
In the other run
Code:
adb restore fakebackup.ab
You should get a prompt on your Kindle, hit the restore my data button. As you do so the command in the first window should stop (or a few seconds later - if it doesn't stop it and re-run both commands again.)
You can now close the second window!
Run
Code:
adb reboot
, your Kindle should reboot though the screen will be blinking repeatedly (flashing between the lockscreen and the boot animation) don't worry about that as it will be fixed in a sec.
Step 5 - Cleaning Up
Run
Code:
adb shell
If all was successful you should see the prompt change to [email protected]:/
If it did, continue otherwise go back to step 4.
Run these
Code:
/data/local/tmp/busybox mount -o remount,rw /system
/data/local/tmp/busybox mv /data/local/tmp/su /system/xbin/su
/data/local/tmp/busybox mv /data/local/tmp/ric /system/bin/ric
chmod 755 /system/bin/ric
/data/local/tmp/busybox mv /data/local/tmp/su /system/xbin/su
/data/local/tmp/busybox mv /data/local/tmp/Superuser.apk /system/app/Superuser.apk
/data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
chown 0.0 /system/xbin/su && chmod 06755 /system/xbin/su
chmod 655 /system/app/Superuser.apk
chmod 755 /system/xbin/busybox
rm /data/local.prop
reboot
Your Kindle will restart and SuperSU will be available under Apps, your now free to do as you please, though you could follow with Step 3 on this thread to get Google Apps etc working.
Update: a short guide to installing the Play store can be found here.

This worked almost perfect for me but I couldn't get it to run adb commands from the stuff folder so I dumped its contents (minus the adb stuff) into the platform-tools in the android SDK and from then on everything went great. Thanks so much.

didthis work for 10.2.4 users out there
does this work for 10.2.4

worked!
Great work, congratulations and thanks! I'd like to make some comments tho regarding some typos and suggestions.
1.- I'd suggest to install the android SDK as, in fact, adb commands didn't work from the stuff folder. Add a line to .bash_profile with the export PATH command to make permanent access to the adb shell.
2.- Push files from the Root_with_Restore_by_Bin4ry_v18 folder, not the .7z file.
3.- The command is, e.g., adb push busybox /data/local/tmp/ instead of adb push busybox /data/local/tmp/.
4.- In Step 5 the command /data/local/tmp/busybox mv /data/local/tmp/su /system/xbin/su is twice so you'll get an error the second time you execute it.
Also congratulations for instructions on how to install PlayStore - here pay attention to the names playstore.apk and servicesframework.apk which in fact are plstore3.10.10.apk and GoogleServicesFramework.apk respectively -
Once again thanks for your work.

gorganzolia said:
does this work for 10.2.4
Click to expand...
Click to collapse
Yes this worked for 10.2.4

10.2.6
Does this work with 10.2.6?

it worked
Tried it this morning on 10.2.6 and it worked woohoo now how do you stop it from automatically updating
Found out how to stop those automatic updates here http://forum.xda-developers.com/showthread.php?t=2086450

Unlocking DZ ONLY by power button? :)

Hello!
I bought already DZ and everything is fine, but the system of keyboard is pissed off So, I was thinking if is any way to change that when Im opening a phone automatically screen is turned on. I would like to change that, because sometimes when im taking him the phone is trying to open, because of best opening system Screen should turn on only if I will press the power button. Any idea how to resolve that? I'd really appreciate that.

root DZ
IM NOT RESPONSIBLE TO BRICKED DEVICE(S), APOCALYPSE, GLOBAL WARMING AND NUCLEAR WAR
IT WORKED 4ME BUT MAY NOT WORK 4YOU
Download: Attachments (unzip Root.zip to C:/htc/ directory, then copy PC10IMG.zip and .apk files to C:/htc/) PC10IMG.zip link has been dended to your XDA mailbox
Then:
unpack attachment to C:/htc (example)
copy System32.zip files to C:/Windows/System32/
TempRoot:
Run cmd and type:
Code:
adb push C:\htc\fre3vo /data/local/tmp
adb shell
chmod 777 /data/local/tmp/fre3vo/data/local/tmp/fre3vo -debug -start FAA90000 -end FFFFFFFF
This will kick you srom the device shell , but dont worry and DO NOT reboot your device
Change Misc Version:
Code:
adb push C:\htc\misc_version /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/misc_version
adb shell
/data/local/tmp/misc_version -s 1.33.405.5
To get:
Code:
--set_version set. VERSION will be changed to: 1.33.405.5
Patching and backing up partition 17...
Then type:
Code:
sync
Now you must type this GOOD (fail=brick) (still in shell!!!):
Code:
dd if=/dev/block/mmcblk0p17 bs=1 skip=160 count=10
Then type:
Code:
exit
Then copy PC10IMG.zip package:
Code:
adb push C:/htc/PC10IMG.zip /sdcard/PC10IMG.zip
CMDline wont response for 6-10 minutes, its fine, its good
When finish type:
Code:
adb reboot bootloader
Wait until bootloader parse package and press VOL-UP
DO NOT POWER-OFF YOUR DEVICE (PLUG IT TO CHARGER)
When it finish, press POWER button to reboot
You dont must set up android
Switch on usb-debugging (settings/apps/develop)
then plug it to pc and type in cmd:
Code:
adb install C:\htc\AndroidTerm.apk
adb install C:\htc\TotalCommander.apk
adb push C:\htc\busybox /data/local/tmp/
adb push C:\htc\gfree /data/local/tmp/
adb push C:\htc\rage /data/local/tmp
adb push C:\htc\root /data/local/tmp/
adb shell chmod 0755 /data/local/tmp/*
adb push C:\htc\su /sdcard/
adb push C:\htc\Superuser.apk /sdcard/
Then launch Terminal emulator and type:
Code:
/data/local/tmp/rage
to get
"forked xxxxxx childs"
Tap "menu" and select "reset term"
It will kill the terminal
Launch Terminal emulator again, but you will get error wit "force close" (force close it)
Launch Terminal Emulator again and type:
Code:
/data/local/tmp/gfree -f
/data/local/tmp/root
sync
close terminal emulator and launch Total Commander
Go to "system directory" and try to open /data
If succeed (Superuser request): TOU DID (S-OFF, Super-CID (no simlock), root)
You can use RootKeeper.apk to "survive" su binary when installing OTA update (you can root android 2.2 but no android 2.3.3)
Disable root keeper when making nandroid
When you have root you can modify it with flashing another rom
Please hit thanks button

I read that few times to be sure what ive got to do, so tommorow im gonna do the operation Man, you are awsome. In one time I will get root (im doing that from time, when i wrote that thread) and resolve of my unlocking problem Hope, that i will not get lost on that. Cant wait for tommorow..

unlocking DZ
I forgot about one thing: after /data/local/tmp/root you can get error, but it's fine too
If you dont want to check root with Tcmd type "su" in terminal

[Q] How to root Desire Z without USB debugging

Hi. I did a factory reset and now I cannot get past the white HTC welcome screen. I don't have the phone rooted, hboot says S-ON. I had USB debugging disabled when doing the reset, so now I can't turn it on (since I won't get anywhere near the actual system).
Also, I don't know if this is the cause of not having USB debugging on - adb can't seem to find my device. When connected, it shows HBOOT USB PLUG, but adb devices returns an empty list..
Is there a way I can root/unlock the phone, without having debugging on, so that I can flash a recovery and a new system?
Thanks

Not too likely, adb will never work in bootloader mode but fastboot should. adb only works in os and recovery.
What you'll need to do is flash an RUU through bootloader or fastboot to get things working again. Check the development section here for a list of the latest RUUs for the vision
Sent from my Nexus 4 using XDA Premium 4 mobile app

I was swamped and got back to it by now. Thank you for your suggestion. It doesn't work though.
I downloaded the newest RUU from htcdev.com, the phone did get recognized by fastboot and the RUU installer seemed happy. However, when the actual update started, it got stuck on "Rebooting bootloader" or similar for over half an hour. That's when I decided to cancel it.
Next on, I tried steps shown here: androidforums .c o m/htc-desire-s/678126-desire-s-stuck-bootloader.html
fastboot erase cache - this got stuck on 'erasing cache', nothing happened afterwards
fastboot oem rebootRUU - this wrote "..." and nothing else happened
Is there anything else I can try?

ROOT
http://forum.xda-developers.com/showthread.php?t=2348266
http://forum.xda-developers.com/showthread.php?t=1178912
http://forum.xda-developers.com/wiki/HTC_Vision
How To Get R/W Access (Permanent Root / "Permaroot") using gfree v1.0[edit]
Prerequisites
Having the proper USB drivers installed - HTC Sync including Windows USB Drivers for the Vision
Disable auto-run or uninstall Visionary if you have it (It's important!)
adb (installed as part of the Android SDK.) See this guide on how to install/setup adb on your PC.
The HTC Desire Z with a firmware version higher than 1.34, T-Mobile G2 with a firmware version higher than 1.22 and the Desire HD with a firmware version higher then 1.32 have to be downgraded before proceeding.
Downgrading HTC Desire Z, T-Mobile G2 and Desire HD
For the 1.XX firmware HTC Desire Z follow this guide Downgrade DZ till step 12 and then come back.
For the 1.XX firmware HTC Desire HD follow this guide Downgrade HD and then come back.
For the 2.XX firmware HTC Desire Z/Desire HD and T-Mobile G2 follow this guide GUIDE Downgrade G2 2.13.531.8 (2.3.3 T-Mobile Rom w/ S-ON) & DZ 2.3.3 w/ S-ON" and come back. The history can be found in this thread New exploit works with Gingerbread! and Desire Z users see this posting of the thread Desire Z explanation.
Please use your brain when following these postings / guides. Especially make sure that you use a PC10IMG.zip for your device!
1. Necessary files
psneuter psneuter.zip (md5sum 89c2dec8d72d87b4c669f44dd31c8d17)
gfree v1.0 gfree_10.zip (md5sum 0bc9fc22bda897c765b02066f8a3c83b)
root_psn root_psn.zip (md5sum c8fe38ef55eb8951def9ff17b2eb99c1)
Superuser package su-2.3.6.2-efgh.zip (md5sum 43d9a40b63e916635d5ad7ca32433fab)
1.1. engineering hboot
Download the appropriate HBOOT for your phone:
T-Mobile G2: vision.hboot-0.76.2000.zip / Mirror (md5sum 7669AE12DC2FAA10AE555A164980EFD0)
HTC Desire Z: vision.hboot-0.84.2000.zip / Mirrors in this thread (md5sum 2CE1BDD5E4C1119CCFCECB938710D742)
HTC Desire HD: ace_glacier.hboot-0.85.2007.zip (md5sum df4fd77f44993eb05a4732210d2eddc6)
Note that the md5sums are for the actual hboot img contained within the zip file, not the for the zip file itself. Note also that the dz, g2, and dhd each use their own version of the engineering boot, as the phones are partitioned differently. (If you have previously installed the wrong HBOOT for your phone, you may need to reflash everything after partition 18)
1.2. clockwork recovery
Download the appropriate clockwork recovery for your phone:
ClockworkMod Recovery 5.0:
T-Mobile G2 and HTC Desire Z: recovery-clockwork-5.0.2.7-vision.img (md5sum 87a428549440894dbe2f96dd5efc4fb5)
HTC Desire HD: recovery-clockwork-5.0.2.0-ace.img (md5sum b8d77b9352dcbb41839e45342ea35658)
ClockworkMod Recovery 5.8 (touch):
T-Mobile G2 and HTC Desire Z: recovery-clockwork-touch-5.8.1.0-vision.img (md5sum b21aa5a0d593b6ebce880be3316ff64a)
HTC Desire HD: recovery-clockwork-touch-5.8.1.5-ace.img (md5sum fd6abfbc459663455a25b88ca7d77442)
Rename the file to 'recovery-clockwork.img'.
2. Copy the files to the phone
Before you can adb as described below you need to enable debugging in the settings on the phone. In Settings go to "Applications -> Development" and check the "USB debugging" option.
Connect the phone to the USB of your PC. The phone will stay connected during the complete procedure.
Make sure that you do NOT turn on USB storage. There has to be a sdcard in the phone and it has to be mounted to the phone!
In the commands to run below, $ or # represent the prompt and should NOT be entered as part of the commands (in Windows this will be something like C:\> instead).
Unpack all the zip files to a directory on your PC. Open a terminal (or command window) on your PC and change the current directory to where the files are on your PC and execute these commands:
$ adb push psneuter /data/local/tmp/
$ adb push gfree /data/local/tmp/
$ adb push busybox /data/local/tmp/
$ adb push hboot-eng.img /data/local/tmp/
$ adb push root_psn /data/local/tmp/
$ adb push su /sdcard/
$ adb push Superuser.apk /sdcard/
$ adb shell chmod 755 /data/local/tmp/*
2. clockwork recovery for T-Mobile G2 and HTC Desire Z
To copy your clockwork recovery execute the following command in the terminal or command window
$ adb push recovery-clockwork.img /data/local/tmp/recovery.img
3. Temporary root
In the terminal (or command window) execute these commands:
$ adb shell /data/local/tmp/psneuter
$ adb shell
after the last command you should have a root shell in adb (this is indicated by a # prompt). Leave this terminal (or command window) that contains the root shell open.
4 S-OFF, root and its friends Super-CID, SIM-unlock, engineering hboot, clockwork recovery and root
In the following section we are trying to gain write access to the emmc by power cycling it.
We recommend to install the engineering hboot as part of the gfree procedure.
In the root shell (indicated by the #) that you got in the Temporary root section execute the following commands:
# cd /data/local/tmp
# ./gfree -f -b hboot-eng.img -y recovery.img
# ./root_psn
# sync
Wait a few seconds for the changes to "take".
4.1. Automatic gfree hboot verification
As it is very important that the hboot was installed correctly gfree calculates md5sums of the partition. It will calculate the following 3 checksums
md5sum #1 - checksum of partition 18 before the installation
md5sum #2 - checksum of the hboot image that should be installed
md5sum #3 - checksum of partition 18 after the installation
gfree will check the md5sums and give you a proper success or error message. The messages are explained in detail at gfree-wiki
The messages that you want to see are either:
md5sum #1 == md5sum #2 - the hboot image is already installed -> skipping installation
or
md5sum #3 == md5sum #2 - the hboot image was successfully installed -> OK!
If you get a different error message you should run for help at #G2ROOT on Freenode.
If you got one of the two success messages described above -> You are fine, Reboot your phone by executing the following command in the root shell (indicated by the #):
# reboot
5. Verify the success of gfree
You can verify the success of gfree by using gfree_verify.
Download gfree_verify.zip from gfree_verify_v01.zip (md5sum 8e3535fd720d19fa0aec4eb711b897c4)
Unzip gfree_verify_v01.zip to a place on your PC.
Open a terminal (or command window) on your PC and change the current directory to where the files are on your PC and execute these commands:
$ adb push gfree_verify /data/local/tmp
$ adb shell chmod 755 /data/local/tmp/gfree_verify
$ adb shell
In this shell:
Remark: When you run su for the first time in the adb shell make sure the the screen of the phone is unlocked. Because when you enter the command the Superuser app will show up and ask you if you want to grant superuser access to app Unknown (2000).
Check the Remember check box and click allow.
$ su
# cd /data/local/tmp
# stop ril-daemon
# ./gfree_verify
You should see the following output:
gfree verify_cid returned:
@cid: 11111111
OK
gfree verify_secu_flag returned:
@secu_flag: 0
OK
gfree verify_simlock returned:
@simlock= 00
OK
Start the interface layer again (IN THE ADB SHELL ON YOUR PC):
# start ril-daemon
Did it work? Here's what you're looking for:
@cid: 11111111 <--- this response means you have superCID!
@simlock= 00 <--- this means your simlock is off.
@secu_flag: 0 <--- this means your radio is S-OFF.
6. Backup and cleanup
During the process gfree created backups of the partitions that it changed on your sdcard in /sdcard/
The files are called /sdcard/part7backup-.bin, part18backup-<time>.bin (if you installed hboot) and part21backup-<time>.bin. It is highly recommended that you copy these files to a save location on your PC and keep them!
You can delete the files in /data/local/tmp they are not needed anymore.
7. Next steps
Find a custom rom that you would like to install and install it using the clockwork recovery.
Enjoy the freedom of your phone.
If you like free phones and our work we would like to ask you to support the EFF.
Support the EFF[edit]
or
http://forum.xda-developers.com/showthread.php?t=1097977

Recovery Corrupt ?

Hi, i have firm 51.1.1.0 with root and busybox installed, and i'm trying to downgrade to version 51.1.0.2 but in the step 7 on the guide from AFTVNews
7. Run the command: chmod 777 /cache/recovery (HERE SAYS ME No such file or directory ! Already i'm follow whit the 2 commands to create the directory)
mkdir /cache/recovery ( HERE SAYS ME THE FILE ALREADY EXIST !! )
I Try to continue with the guide obviating the error but that not works...
I'm trying to make a factory reset whit te combinations of keys Alt + Print Screen + i and when the recovery screen appears the home button don't show me the options...
What is wrong here? Is a semi brick or what?
Thanks !!

If the mkdir /cache/recovery is exist then do next step chmod 777 /cache/recovery and do continue what the instruction tell you. (I copied from aftvnews (http://www.aftvnews.com/how-to-manually-upgrade-or-downgrade-the-amazon-fire-tv/)
If the Recovery corrupted then you can just insert new recovery image into recovery space and follow this instruction. it will fixes as long as you can able access root priviledge via ADB shell.
install Recovery image (http://www.aftvnews.com/how-to-install-clockworkmod-custom-recovery-on-the-amazon-fire-tv/)
Using DD command and make sure you put recovery.img in /sdcard before do this DD command (dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery)
Hope it helps and let me know.
Code:
1. Run the command: adb shell
2. Run the command: su (If this is the first time you’ve ever run su, a pop-up will appear on the Fire TV, select Grant)
3. Run the command: chmod 777 /cache
4. Run the command: chmod 777 /cache/recovery (Note: If you see a message saying “No such file or directory”, then run the following two commands:)
5. mkdir /cache/recovery
6. chmod 777 /cache/recovery
7. Run the command: cd /cache/recovery
8. Run the command: echo –-update_package=/cache/update.zip > command
9. Run the command: exit
10. Run the command (yes, again): exit
11. Run the command: adb push update.zip /cache (This assumes the update.zip file you renamed in step 2 is in the same directory as adb, otherwise enter the full path to the file like adb push C:\full\path\to\update.zip /cache
Once the update.zip file has finished transferring to the Fire TV, run the command: adb reboot recovery
JonHIV said:
Hi, i have firm 51.1.1.0 with root and busybox installed, and i'm trying to downgrade to version 51.1.0.2 but in the step 7 on the guide from AFTVNews
7. Run the command: chmod 777 /cache/recovery (HERE SAYS ME No such file or directory ! Already i'm follow whit the 2 commands to create the directory)
mkdir /cache/recovery ( HERE SAYS ME THE FILE ALREADY EXIST !! )
I Try to continue with the guide obviating the error but that not works...
I'm trying to make a factory reset whit te combinations of keys Alt + Print Screen + i and when the recovery screen appears the home button don't show me the options...
What is wrong here? Is a semi brick or what?
Thanks !!
Click to expand...
Click to collapse