Help with Unroot - Volume Buttons not working - Droid Incredible Q&A, Help & Troubleshooting

Hey guys I need some help. The standard unroot process requires me to use the volume buttons to unroot my device, mine are broken. Is there any way I can unroot my incredible with HTC sync? Or is there a way to do it through clockworkmod?
Any help is appreciated! I need to get the phone back to verizon asap.

You can run the RUU from a Windows PC- see this thread http://www.incredibleforum.com/foru...s/5723-how-get-back-complete-stock-s-off.html

Thank you very much, I am giving it a try now.

The RUU isn't working.. I flashed to a stock sense rom so that it would recognize it. I start the RUU and I click through all of the preliminary stuff and it starts to flash.
In the progress box it says "rebooting to bootloader" and then it stops.
a box pops up and i get a [ERROR 155]: UNKNOWN ERROR.
I don't know what to do. Please help.

Try ROM Manager. You can boot into Clockwork from there.

thejdog55 said:
Try ROM Manager. You can boot into Clockwork from there.
Click to expand...
Click to collapse
are you saying run the RUU on my computer while in Clockwork?

The app ROM Manager, allows you to not only download and flash ROMs from the device, you can also use it to reboot you phone into recovery without using the volume keys.

thejdog55 said:
The app ROM Manager, allows you to not only download and flash ROMs from the device, you can also use it to reboot you phone into recovery without using the volume keys.
Click to expand...
Click to collapse
Yes, but i'm trying to unroot my device using HTC Sync and an RUU.
Could I flash a .zip in recovery to unroot my phone?

I found the log files of the RUU if this helps
Code:
<LOG>
<T180836><INFO><VERSION>1.0.2.10</VERSION></INFO></T180836>
<T180836><DEBUG><PAGE>====== WelcomeDlg ======</PAGE>
</DEBUG></T180836>
<T180842><DEBUG><PAGE>====== VerifyingMobileDlg ======</PAGE>
</DEBUG></T180842>
<T180842><DEBUG><CMD>adb devices</CMD>
</DEBUG></T180842>
<T180843><DEBUG><OUT>List of devices attached
HT04HHJ02720 device
</OUT>
</DEBUG></T180843>
<T180843><DEBUG><CMD>adb devices</CMD>
</DEBUG></T180843>
<T180844><DEBUG><OUT>List of devices attached
HT04HHJ02720 device
</OUT>
</DEBUG></T180844>
<T180844><DEBUG><CMD>adb devices</CMD>
</DEBUG></T180844>
<T180846><DEBUG><OUT>List of devices attached
HT04HHJ02720 device
</OUT>
</DEBUG></T180846>
<T180846><DEBUG><CMD>adb -s HT04HHJ02720 shell cat /sys/class/power_supply/battery/capacity</CMD>
</DEBUG></T180846>
<T180847><DEBUG><OUT>57</OUT>
</DEBUG></T180847>
<T180847><DEBUG><PAGE>====== VerificationDlg ======</PAGE>
</DEBUG></T180847>
<T180847><DEBUG><CMD>adb devices</CMD>
</DEBUG></T180847>
<T180848><DEBUG><OUT>List of devices attached
HT04HHJ02720 device
</OUT>
</DEBUG></T180848>
<T180848><DEBUG><CMD>adb devices</CMD>
</DEBUG></T180848>
<T180850><DEBUG><OUT>List of devices attached
HT04HHJ02720 device
</OUT>
</DEBUG></T180850>
<T180850><DEBUG><CMD>adb -s HT04HHJ02720 shell getprop ro.build.description</CMD>
</DEBUG></T180850>
<T180851><DEBUG><OUT>1.22.605.2 CL161494 release-keys</OUT>
</DEBUG></T180851>
<T180852><DEBUG><PAGE>====== ComparisonDlg ======</PAGE>
</DEBUG></T180852>
<T180852><DEBUG><CMD>adb devices</CMD>
</DEBUG></T180852>
<T180854><DEBUG><OUT>List of devices attached
HT04HHJ02720 device
</OUT>
</DEBUG></T180854>
<T180854><DEBUG><CMD>adb devices</CMD>
</DEBUG></T180854>
<T180855><DEBUG><OUT>List of devices attached
HT04HHJ02720 device
</OUT>
</DEBUG></T180855>
<T180855><DEBUG><CMD>adb -s HT04HHJ02720 shell getprop ro.build.description</CMD>
</DEBUG></T180855>
<T180856><DEBUG><OUT>1.22.605.2 CL161494 release-keys</OUT>
</DEBUG></T180856>
<T180903><DEBUG><PAGE>====== UpdatingDlg ======</PAGE>
</DEBUG></T180903>
<T180907><DEBUG><CMD>adb devices</CMD>
</DEBUG></T180907>
<T180909><DEBUG><OUT>List of devices attached
HT04HHJ02720 device
</OUT>
</DEBUG></T180909>
<T180909><DEBUG><CMD>adb devices</CMD>
</DEBUG></T180909>
<T180910><DEBUG><OUT>List of devices attached
HT04HHJ02720 device
</OUT>
</DEBUG></T180910>
<T180910><DEBUG><CMD>adb -s HT04HHJ02720 shell reboot oem-78</CMD>
</DEBUG></T180910>
<T180911><DEBUG><OUT>reboot: no such tool</OUT>
</DEBUG></T180911>
<T180933><DEBUG><CMD>adb devices</CMD>
</DEBUG></T180933>
<T180934><DEBUG><OUT>List of devices attached
HT04HHJ02720 device
</OUT>
</DEBUG></T180934>
<T180934><DEBUG><CMD>adb devices</CMD>
</DEBUG></T180934>
<T180935><DEBUG><OUT>List of devices attached
HT04HHJ02720 device
</OUT>
</DEBUG></T180935>
<T180938><DEBUG><PAGE>====== VerificationDlg ======</PAGE>
</DEBUG></T180938>
<T180938><DEBUG><CMD>adb devices</CMD>
</DEBUG></T180938>
<T180939><DEBUG><OUT>List of devices attached
HT04HHJ02720 device
</OUT>
</DEBUG></T180939>
<T180939><DEBUG><CMD>adb devices</CMD>
</DEBUG></T180939>
<T180941><DEBUG><OUT>List of devices attached
HT04HHJ02720 device
</OUT>
</DEBUG></T180941>
<T180941><DEBUG><CMD>adb -s HT04HHJ02720 shell getprop ro.build.description</CMD>
</DEBUG></T180941>
<T180942><DEBUG><OUT>1.22.605.2 CL161494 release-keys</OUT>
</DEBUG></T180942>
<T180945><DEBUG><PAGE>====== ComparisonDlg ======</PAGE>
</DEBUG></T180945>
<T180945><DEBUG><CMD>adb devices</CMD>
</DEBUG></T180945>
<T180946><DEBUG><OUT>List of devices attached
HT04HHJ02720 device
</OUT>
</DEBUG></T180946>
<T180946><DEBUG><CMD>adb devices</CMD>
</DEBUG></T180946>
<T180947><DEBUG><OUT>List of devices attached
HT04HHJ02720 device
</OUT>
</DEBUG></T180947>
<T180947><DEBUG><CMD>adb -s HT04HHJ02720 shell getprop ro.build.description</CMD>
</DEBUG></T180947>
<T180948><DEBUG><OUT>1.22.605.2 CL161494 release-keys</OUT>
</DEBUG></T180948>
<T180954><DEBUG><PAGE>====== UpdatingDlg ======</PAGE>
</DEBUG></T180954>
<T180958><DEBUG><CMD>adb devices</CMD>
</DEBUG></T180958>
<T181000><DEBUG><OUT>List of devices attached
HT04HHJ02720 device
</OUT>
</DEBUG></T181000>
<T181000><DEBUG><CMD>adb devices</CMD>
</DEBUG></T181000>
<T181001><DEBUG><OUT>List of devices attached
HT04HHJ02720 device
</OUT>
</DEBUG></T181001>
<T181001><DEBUG><CMD>adb -s HT04HHJ02720 shell reboot oem-78</CMD>
</DEBUG></T181001>
<T181003><DEBUG><OUT>reboot: no such tool</OUT>
</DEBUG></T181003>

I also took a picture of the box right before the error comes up
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

and here is the picture of the error

Grabbing at straws here but try this on instead..
http://dougpiston.com/files/RUU/RUU...4k_NV_1.50_PRL58006_release_143351_signed.exe

doug piston said:
Grabbing at straws here but try this on instead..
http://dougpiston.com/files/RUU/RUU...4k_NV_1.50_PRL58006_release_143351_signed.exe
Click to expand...
Click to collapse
Nope :/ Still getting the exact same error.

What does it say in hboot? S-on or off? Baseband?

doug piston said:
What does it say in hboot? S-on or off? Baseband?
Click to expand...
Click to collapse
S-on when i checked before flashing a sense based rom. I can't check anymore because i can't boot into Hboot. my volume buttons don't work
I don't know about the the baseband. I did just recieve a ota update for 2.2. if i install that should root disappear???

With clockwork still on the device, no. You can manually flash a stock recovery with adb commands and then accept the update..
http://theunlockr.com/2009/10/15/how-to-flash-a-new-recovery-image-if-you-are-already-rooted/
You'll just need to get a stock recovery.img do what the link above describes and then accept the OTA.
Or try this
http://forum.xda-developers.com/showthread.php?t=727263
I make no promises as it sounds like something is proper effed with your phone.

JustinMurphy said:
Yes, but i'm trying to unroot my device using HTC Sync and an RUU.
Could I flash a .zip in recovery to unroot my phone?
Click to expand...
Click to collapse
Yes you should be able to flash a normal image to go back to stock. Search the forums for topics about going back to stock. There are a lot of step by step guides, that will show you how to get back to stock just by flashing through Clockwork.

doug piston said:
With clockwork still on the device, no. You can manually flash a stock recovery with adb commands and then accept the update..
http://theunlockr.com/2009/10/15/how-to-flash-a-new-recovery-image-if-you-are-already-rooted/
You'll just need to get a stock recovery.img do what the link above describes and then accept the OTA.
Or try this
http://forum.xda-developers.com/showthread.php?t=727263
I make no promises as it sounds like something is proper effed with your phone.
Click to expand...
Click to collapse
Would this be the proper 2.1 recovery for my phone? - http://adrynalyne.us/?p=41

Yes, but on a side note did you install the HTC sync?

doug piston said:
Yes, but on a side note did you install the HTC sync?
Click to expand...
Click to collapse
Yep, i did that before i started trying the flash the RUU

Related

[GUIDE] Perma-root and S-OFF!! (Both manually or if you used VISONary r12)

FINALLY!!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
WARNING: THIS COULD PERMENANTLY BRICK YOUR PHONE, INSTEAD OF ROOT IT IF YOU DO THE EVER-SO-SLIGHTEST THING WRONG. YOU'VE BEEN WARNED. I AM NOT LIABLE FOR YOUR STUPIDITY. ALSO, THE HBOOT FILE LOCATED HERE SHOULD ONLY BE USED ON THE G2. IF YOU SO CHOOSE TO USE THIS ON YOUR DESIRE Z, DESIRE HD, MOTOROLA RAZR, WHATEVER, IT WILL PROBABLY SCREW THINGS UP. YOU HAVE BEEN WARNED, ONCE AGAIN!
The next person to spam or hijack the thread with immature pics or comments will get a perm Ban!!!!​
Whoa, where did that comment above come from?? =P Thanks mods, I appreciate it!
On that note, I would not recommend this on any phone other than the G2, as I have not personally tested it.
NOTES: This thread is not working in Tapatalk for some reason. Click here to open it in your browser. Also, this will not fix your phone's hinges, your nagging girlfriend, or world hunger. It is what it is.
If you perma-rooted with VISIONary r12, you only need to follow steps 5, and 7. All other steps can be omitted. If you would like to do this all manually, you can still use VISIONary r12, however, instead of using the "PERMANENT" option, use the "TEMPORARY" option, where applicable.
VISIONary r12 has been temporarily pulled.
Expect an update to work with VISIONary r14 soon!
Credit goes out to scotty2, and all of the wonderful folks at #G2ROOT! WE LOVE YOU! <3
Donate to scotty2 (for root): [email protected] (PayPal)
Donate to me (for this guide): [email protected] (PayPal)
You need these files:
hboot-eng.img
wpthis-OTA.ko
wpthis-pre-OTA.ko
MIRRORS:
http://bt.microcozm.net/vision-perm-root.zip
MD5s:
Code:
4ed6ac813dbea0ee263ba0f6dc288693 wpthis-OTA.ko
8ac8e7a331a199a48001c691e59b1b33 wpthis-pre-OTA.ko
7669ae12dc2faa10ae555a164980efd0 hboot-eng.img
Step 1
Firstly, run VISIONary to gain temp root
Step 2
Push the .ko file appropriate for your phone, and hboot-eng.img to /data/local/
Step 3
Open a terminal on your phone, or open an adb shell from your computer.
Step 4
Code:
$ su
# insmod /data/local/wpthis-[YOUR_VER].ko
It should return:
Code:
init_module 'wpthis-OTA.ko' failed (Function not implemented)
That is good.
Step 5
FINAL WARNING: THIS STEP COULD SEVERELY DAMAGE YOUR PHONE. USING THE INCORRECT FILE COULD CAUSE IRREPARABLE DAMAGE, MAKING YOUR PHONE NOTHING MORE THAN A BRICK.
That noted, if you would like S-OFF, go ahead and run this command in your terminal.
Code:
# dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18
Step 6
Note: This step is not required if you have used VISIONary r12 to perma-root.
If VISIONary gives you issues about already being rooted here, go ahead and skip this step. After you complete the guide and reboot, go ahead and run VISIONary, and hit "ROOT NOW", wait a minute or two, and reboot again. At this point, you will be fully rooted.
Close your terminal. If you are in adb shell, disregard
Run VISIONary again, this will lock in root. But wait, you're not done yet.
Step 7
This step will lock in your perma-root and S-OFF. If you are using adb shell, you should still have your shell open. If you have used VISIONary r12 to perma-root, and are just wanting to apply S-OFF, your terminal should still be open. If you have just completed step 6, go ahead and reopen your terminal, and type su and press enter to regain root access.
Code:
# sync
Wait a minute or two, and reboot. Congratulations, you are S-OFF!! Go ahead and power off your phone, and hold down VOL DOWN and press POWER to boot up into your bootloader. Check the top line to confirm you have S-OFF. Enjoy!!
Thanks again, everybody!
This is most excellent. 3 cheers to all behind this
Edit: Sent $5 to Scotty2's beer fund
<3 #g2root
win.
Just a WARNING - screwing up this command:
Code:
# dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18
can turn your new phone into a very pretty paperweight.
Caution!
It should be noted in the post that this was a collaborative #g2root effort, primarily involving scotty2, tmzt, IntuitiveNipple but also many others!
skyjumper said:
Just a WARNING - screwing up this command:
Code:
# dd if=/data/local/hboot-eng.img of=/dev/block/mmcblk0p18
can turn your new phone into a very pretty paperweight.
Caution!
Click to expand...
Click to collapse
Maybe this should be edited with 20-font, underlined and bolded in the OP You know someone will screw it up, ***** about it and blame unforgiven512 for their mistake.
edit: though I see that he already put a warning up on the post...LOL.
good work folks in #g2root!
has anyone done this?
Nevermind - Got it.
Here's what the error should look like.
Thanks!
ramainli said:
Where should I push the .ko files to and where? Using ADB to push it?
Click to expand...
Click to collapse
No offense man, but if you have to ask, you didn't take the time to read the post, you shouldn't be doing this.
i can mirror them on my 4shared account. let me download them now and put them up
Mediafire links to the same files.
hboot-eng.img
wpthis-OTA.ko
wpthis-pre-OTA.ko
EDIT: I was blind, the md5sums were already in the post. Verified to be the same in the above links.
unforgiven512 said:
EDIT: Can someone mirror these files for me? I forgot to pay my hosting bill, and I know I only have so much bandwidth on Dropbox. Thanks in advance!
Click to expand...
Click to collapse
Mirror for all 3 files
Wait...
REALLY?
Sent from my T-Mobile G2 using Tapatalk
mirrors
HF
Code:
http://hotfile.com/dl/81463991/019567e/hboot-eng.img.html
http://hotfile.com/dl/81464095/afc52d4/wpthis-OTA.ko.html
http://hotfile.com/dl/81464138/d441072/wpthis-pre-OTA.ko.html
RS
Code:
http://rapidshare.com/files/429789096/hboot-eng.img
http://rapidshare.com/files/429789097/wpthis-OTA.ko
http://rapidshare.com/files/429789098/wpthis-pre-OTA.ko
Mirror -
http://hotfile.com/dl/81465009/05845ea/wpthis-pre-OTA.ko.html wpthis-pre-TOA.ko
http://hotfile.com/dl/81465176/726aa62/hboot-eng.img.html hboot-eng.img
http://hotfile.com/dl/81465326/207607c/wpthis-OTA.ko.html wpthis-OTA.ko
here you guys go:
MIRROR
hboot-eng.img
wpthis-OTA.ko
wpthis-pre-OTA.ko
lol, guess we have plenty of mirror for this now, lol
Will this also work with folks with the European Desire Z?
HBOOT: VISION PVT SHIP S-ON 0.85.0005
Baseband: 12.28b.60.140eU_26.03.02.26_M
Build: 1.34.405.5 CL273326

How to make custom Odin images

Hey folks,
XDA is down, so I can't tell how much has been done, development wise, but its looking bleak. I'd like to help out, even though I do not have the device.
First, we need to get some Odin images going. This is BEST done with somebody who has a stock, but rooted, Samsung Continuum.
This has been adapted from here:
Creating Custom ROMs/Backups for Odin - Android Forums
First, you need to root, via either one of the one click methods, or z4root.
Then, you must setup adb, if you haven't already. Alternatively, you could be a masochist and use the terminal on the device, downloaded from the market.
As root (#)
To backup kernel parition:
Code:
dd if=/dev/block/bml7 of=/sdcard/kernel bs=4096
To backup recovery partition (probably the same as the kernel):
Code:
dd if=/dev/block/bml8 of=/sdcard/kernel bs=4096
To backup system:
Code:
dd if=/dev/block/stl9 of=/sdcard/system bs=4096
Backup the kernel, system, and recovery images from your sdcard to your computer. Make backups!
Rename kernel to: zImage
Rename recovery to recovery.bin
Rename system to factoryfs.rfs
The next part requires linux, OS X, or cygwin.
Cygwin
If you are using heimdall, the above images are ready for flashing.
If using Odin, we must still package them.
Code:
$ tar -H ustar -c image_1 [image_2 ...] > your_odin_package.tar
If you want an all in one package, put each image name in. if not, make one image per tar file.
Example: tar -H ustar -c zImage > zImage.tar
This would give us a zImage.tar file. Now we will turn it into a tar.md5 file, so that Odin can make sure its not corrupt before flashing.
Code:
$ md5sum -t your_odin_package.tar >> your_odin_package.tar
$ mv your_odin_package.tar your_odin_package.tar.md5
using the above example, your final file would be zImage.tar.md5.
This gets used with Odin3 v.1.30, in the PDA section. You need to install Samsung usb drivers prior to, of course, and the phone must be in download mode.
ALWAYS USE THE PDA SECTION IN ODIN.
Odin can be found here:
http://adrynalyne.us/files/odin/Odin3v1.3.exe
Download mode (on the Fascinate anyway), can be achieved by powering off device, holding DOWN volume, and plugging in the usb cable, or hitting power.
I plan on posting some other stuff here, so PLEASE, someone make these images for everyone! Its essential to have a fall back. I do not own the device, so I cannot.
I have the images and they have been restored onyo 3 devices without flaw. Ill release them tomorrow.
Sent from my SCH-I400 using XDA App
It's not my intention to resurrect such an old thread, but here's a little more info about this method.
If you're using Mac OS, the commands are a bit different.
Instead of:
tar -H ustar -c image_1 [image_2 ...] > your_odin_package.tar
tar --format ustar -c image_1 [image_2 ...] > your_odin_package.tar
Instead of:
md5sum -t your_odin_package.tar >> your_odin_package.tar
md5 -r your_odin_package.tar >> your_odin_package.tar
Pastor! thanks for the info, how do i convert the rom cwm zip i have to a flashable tar?
joshkoss said:
Pastor! thanks for the info, how do i convert the rom cwm zip i have to a flashable tar?
Click to expand...
Click to collapse
put boot.img in that tar. it is said to flash like a charm.
If you want to create flashhable kernel tar file, then download the attached tar template, and using Total Commander, copy your kernel into it. This file is OK with Odin Attached Files
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
kernel_base.tar
mai77 said:
put boot.img in that tar. it is said to flash like a charm.
Click to expand...
Click to collapse
Put boot.img into the odin, and it will almost certainly fail. And way to bump a dead thread
Lol, ^
Well since this thread is bumped anyways, I guess it's as good as place as any to ask; Imnuts, do you think there is a possibility you could work your kernel magic and maybe make us one now that we have source? thanks in advance, lol
Sent from my SCH-I400 using xda premium
Peanut butter jelly time!
Sent from my ADR6425LVW using Tapatalk
trailblazer101 said:
Lol, ^
Well since this thread is bumped anyways, I guess it's as good as place as any to ask; Imnuts, do you think there is a possibility you could work your kernel magic and maybe make us one now that we have source? thanks in advance, lol
Sent from my SCH-I400 using xda premium
Click to expand...
Click to collapse
now i only downloaded sources and took a look at txt files. kernel sources state "HOW TO BUILD KERNEL 2.6.35 FOR SCH-I400" now i looked at imnuts kernel building guide and seen that we would need the correct initramfs for it to boot correctly? and isnt 2.6.35 a GB kernel so maybe we can do something. I will be working on BRICKYOURPHONE.tars when i get my pc back in the same town as i. I might just rent a laptop if it doesnt happen soon lol
pretty sure imnuts knows something about this... (what we would need for custom kernel and GB ASOP?)
update on me:
PC still packed, finals over, and should be grabbing my pc in a week or so before spring quarter starts ive been missing thememing and posting more relevant things lol.

XBMC Installer for FireTV for Windows (by Senaxx)

This is a Windows application which simplifies the whole process of installing XBMC to the Amazon Fire TV. It was written by a fellow named Senaxx and is quite useful.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
DOWNLOAD LINK: http://rghost.net/54708228
INSTRUCTIONS: How-To Guide
Resolved- please ignore.
..
Do you have manual steps? I could write a universal installer in Java.
XBMC ANDROID said:
This is a Windows application which simplifies the whole process of installing XBMC to the Amazon Fire TV. It was written by a fellow named Senaxx and is quite useful.
DOWNLOAD LINK: http://rghost.net/54708228
INSTRUCTIONS: How-To Guide
Click to expand...
Click to collapse
Trauma_Hound said:
Do you have manual steps? I could write a universal installer in Java.
Click to expand...
Click to collapse
SET /P M=Type 1, 2, 3 or 4 then press ENTER:
IF %M%==1 GOTO INSTALL
IF %M%==2 GOTO AUTOPILOT
IF %M%==3 GOTO SURE
IF %M%==4 GOTO EOF
:INSTALL
powershell -Command read-host "Enter your Fire TV IP" ; > ip.txt & set /p ip=<ip.txt
start /b /wait adb kill-server
start /b /wait adb start-server
start /b /wait adb connect %ip%
start /b /wait adb install -r ./xbmc/xbmc-*-Gotham-armeabi-v7a.apk
GOTO START
:SURE
SET /P ANSWER1=Are you sure you want to uninstall? (yes/no)?
if /i {%ANSWER1%}=={yes} (goto :UNINSTALL)
if /i {%ANSWER1%}=={y} (goto :UNINSTALL)
if /i {%ANSWER1%}=={no} (goto MENU)
if /i {%ANSWER1%}=={n} (goto MENU)
:UNINSTALL
powershell -Command read-host "Enter your Fire TV IP" ; > ip.txt & set /p ip=<ip.txt
start /b /wait adb kill-server
start /b /wait adb start-server
start /b /wait adb connect %ip%
start /b /wait adb uninstall org.xbmc.xbmc
:AUTOPILOT
powershell -Command read-host "Enter your Fire TV IP" ; > ip.txt & set /p ip=<ip.txt
start /b /wait adb kill-server
start /b /wait adb start-server
start /b /wait adb connect %ip%
start /b /wait adb install -r ./other/Autopilot.apk
GOTO START
:MENU
cls
GOTO START
:EOF
exit
Download link appears to be dead. Is there a mirror anyone has up?
..
Ignore my ignorance.. but will this replace the Amazon interface? I love the FireTv.. I'm not new to rooting/android but this I am.. working with this type of device.. Looks very interesting.
Funny to see my little app I made in a quick few minutes. I noticed that the version I released didn't work with other versions then nightly versions. I had posted a updated version for it.. but since then didn't update it anymore.
I was working on a windows version but the Amazon FireTV Side App Installer by imtiajmeah made it obsolete.
the link is dead. is there a new link?
fiddystorms said:
the link is dead. is there a new link?
Click to expand...
Click to collapse
i see there is a link to a ZIP file above, it worked fine. thank you again for this BAT file. Simplified things greatly.
Error Message
Hi,
I'm trying to install XBMC on my Fire TV.
I'm trying using the app you developped but I have the following error.
...............................................SENAXX AMAZON FIRE TV XBMC INSTALLER...............................................
1 - Install / Upgrade XBMC
2 - Install Autopilot
3 - Uninstall XBMC
4 - Exit
Type 1, 2, 3 or 4 then press ENTER:1
Enter your Fire TV IP: 192.168.1.203
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
connected to 192.168.1.203:5555
1122 KB/s (58919272 bytes in 51.262s)
pkg: /data/local/tmp/xbmc-13.2-Gotham-armeabi-v7a.apk
Failure [INSTALL_FAILED_CONTAINER_ERROR]
..............................................
Do you have an idea why I have this kind of message ?
Thanks
can i ask why this tool now? we have been able to install xbmc for a long time via the FTV utility app and fireadb. Both install xbmc and then some. this tool seems very unnecessary. with that said thank you
This thread was started in April.
Sent from my SCH-I545 using Tapatalk
This thread should probably be closed since the author is no longer supporting the tool. You're better off using adbFire in the future.

FireTV boot animation replacement

Here is a replacement for the Amazon FireTV bootanimation. With the new root available for the Amazon FireTV2, I decided to make a new boot animiation for it.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is a 1920x1080 version of the bootanimation.zip.
http://www.mediafire.com/file/ciybr59yw5sjgrn/bootanimation_-_freedom1_-_1920_30fps.zip/file
(fixed zip file. was zipped with wrong compression. bootanimation files need to be zipped using compression method as 'store', not 'normal'.)
If there is any desire for a lower res bootanimation, let me know.
Here are the basic Windows steps to replace the bootanimation per
http://www.aftvnews.com/how-to-customize-the-boot-animation-on-a-rooted-fire-tv-or-fire-tv-stick/
adb connect 192.168.xx.xxx (your ip)
adb push c:\'directory'\bootanimation.zip /sdcard/
adb shell
su
mount -o remount,rw /system
rm -f /system/media/bootanimation.zip
cd /system/media
cp /sdcard/bootanimation.zip /system/media/bootanimation.zip
chmod 0644 /system/media/bootanimation.zip
exit
exit
reboot FireTV
If you don't see an animation during boot up, the bootanimation file is not supported.
Freedom 2
Or another one.
http://www.mediafire.com/file/fn6l61kntd6xnr6/bootanimation_-_freedom2_-_1920_30fps.zip/file
(fixed zip file. was zipped with wrong compression. bootanimation files need to be zipped using compression method as 'store', not 'normal'.)
My freedom.
http://www.mediafire.com/file/s8d03ts18tsnct5/bootanimation_-_my_freedom_-_1920_24fps.zip/file
Have a bunch more and will upload as I get time...
http://www.mediafire.com/file/52tskf4j10a1th4/bootanimation_-_firetv-_1920_24fps.zip/file
http://www.mediafire.com/file/mk1fhrbuz53afr2/bootanimation-min.zip/file
Haven't been able to test this one yet but here it is. Hopefully the audio works correctly.
Sloane FireTV 2
Excellent work mate exactly what I was looking for
Thanks appreciated big time
ATV 11 Bootanimation
0815hoffi said:
ATV 11 Bootanimation
Click to expand...
Click to collapse
I like this one @0815hoffi, excellent work thanks again, somehow it froze on the coloured dots first reboot, (sloane)
I reboot twrp wipe cache, all good friend. :good:
scottcruss said:
http://www.mediafire.com/file/mk1fhrbuz53afr2/bootanimation-min.zip/file
Haven't been able to test this one yet but here it is. Hopefully the audio works correctly.
Click to expand...
Click to collapse
best bootanimation ever, but after installation (
scottcruss said:
http://www.mediafire.com/file/mk1fhrbuz53afr2/bootanimation-min.zip/file
Haven't been able to test this one yet but here it is. Hopefully the audio works correctly.
Click to expand...
Click to collapse
Best bootanimation ever, but after installation (AFTVnews) firestick4k does not boot. Any idea?
adb shell "cp /sdcard/bootanimation.zip /system/media/bootanimation.zip"
adb shell "chmod 644 /system/media/bootanimation.zip
0815hoffi said:
adb shell "cp /sdcard/bootanimation.zip /system/media/bootanimation.zip"
adb shell "chmod 644 /system/media/bootanimation.zip
Click to expand...
Click to collapse
I did, by using chmod "0644" via terminal in TWRP. File has different attributes by viewing it with "7zip under Windows" ( all "store").
try to delete /system/media/bootanimation.zip an check if it now boots
stick boots, by displaying "android"
Ok than there is a problem with the zip.
try with my bootanimation
https://forum.xda-developers.com/attachments/bootanimation-zip.5135003/
works, it's the nice "ATV11", the zip-file seems to be defect! I will try again with a new download.
Many THX
Fire TV Boot Lite New Interface
works fine on my firestik4k, THX
Thanks bro .
Used to work before but with newest firmware it seems something has changed. Did anyone got theese working again on stick 4k yet?
Okay i got it working again.
For anyone else:
If you have some magisk modules active check the file in the directory:
/data/adb/modules/"your module"/system/media/bootanimation.zip
and
/system/media/bootanimation.zip
you need to replace both zip-files in order to get the custom boot animation to work again.
If you often update and test your new bootanimation.zip then you may want to check my update script. Will be improving it from time to time to get a more fluid and fast way to update.
FireTV-boot-animation-update-script/bar.sh at c0b8a222cdafbccf281c9a6adcac0c5d7c6629a2 · SoulInfernoDE/FireTV-boot-animation-update-script
Makes it easier to update bootanimation.zip from twrp recovery terminal - FireTV-boot-animation-update-script/bar.sh at c0b8a222cdafbccf281c9a6adcac0c5d7c6629a2 · SoulInfernoDE/FireTV-boot-animatio...
github.com

General 📌 [Shared] TWRP by skkk

POCO F5 / Redmi Note 12 Turbo (marble)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
REC VERSION
Install with TWRP or fastboot***
flash recovery_ab twrp.img(cmd)
or
./flash recovery_ab twrp.img(Power Shell)
***After flash used this command:
./fastboot reboot recovery (Power Shell)
fastboot reboot recovery(cmd)
---------------------------------------------------------------------------------------------------------
DOWNLOAD REC VERSION
Recovery for Xiaomi devices - Browse /marble at SourceForge.net
List of relevant recovery in one place
sourceforge.net
------------------------------------------------------------------------------------------------------------------
BOOT VERSION
Installation:
Phone in fastboot mode
Cmd:
fastboot boot twrp.img
or
Power shell
./fastboot boot twrp.img
then in Twrp go to Advanced -> flash current TWRP.
-----------------------------------------------------------------------------------------------------------------
DOWNLOAD BOOT VERSION
2.71 GB folder on MEGA
32 files and 13 subfolders
mega.nz
--------------------------------------------------------------------------------------------------------------------​
i'm wrong
C:\Windows\system32>fastboot boot C:\Users\Admin\Desktop\platform-tools\twrp.img
downloading 'boot.img'...
OKAY [ 2.569s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Bad Buffer Size)
finished. total time: 2.872s
nentv99 said:
i'm wrong
C:\Windows\system32>fastboot boot C:\Users\Admin\Desktop\platform-tools\twrp.img
downloading 'boot.img'...
OKAY [ 2.569s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Bad Buffer Size)
finished. total time: 2.872s
Click to expand...
Click to collapse
My bad it's a REC version, added the BOOT version.
Use the command where the twrp is.
REC VERSION
Install with TWRP or fastboot*** flash recovery_ab twrp.img
***After flash used this command:
./fastboot reboot recovery (Power Shell)
fastboot reboot recovery(cmd)​
Is this recovery will make custom ROM release soon, right?
culec said:
Is this recovery will make custom ROM release soon, right?
Click to expand...
Click to collapse
Twrp and AOSP rom two different things.
Does this TWRP support encrypted device?
fubo73 said:
Does this TWRP support encrypted device?
Click to expand...
Click to collapse
Normally yes, to try, it's the first version, in case of decryption problem remove the security on the lock screen.
Why not Development instead of General?
culec said:
Why not Development instead of General?
Click to expand...
Click to collapse
SKKK is the DEV, not me, hence sharing.
What's a different between REC and Boot version?
hydelezz said:
What's a different between REC and Boot version?
Click to expand...
Click to collapse
None, just the installation method differs.
can u share the tree?
few__ said:
can u share the tree?
Click to expand...
Click to collapse
As mentioned in the thread title "SHARED", which means I'm not the DEV.
can be by:
Build software better, together
GitHub is where people build software. More than 100 million people use GitHub to discover, fork, and contribute to over 330 million projects.
github.com
Update V7.8
Recovery for Xiaomi devices - Browse /marble at SourceForge.net
List of relevant recovery in one place
sourceforge.net
I downloaded from the link given but the file name is [email protected]_3_A12.zip
Is this OFOX for TWRP?
disconmair said:
I downloaded from the link given but the file name is [email protected]_3_A12.zip
Is this OFOX for TWRP?
Click to expand...
Click to collapse
The links provided, Boot or Rec, do not lead to O.F.
You are on the wrong thread.
Recovery for Xiaomi devices - Browse /alioth at SourceForge.net
List of relevant recovery in one place
sourceforge.net
NOSS8 said:
The links provided, Boot or Rec, do not lead to O.F.
You are on the wrong thread.
Recovery for Xiaomi devices - Browse /alioth at SourceForge.net
List of relevant recovery in one place
sourceforge.net
Click to expand...
Click to collapse
Oh, it was sourceforge that made me confused. I'd just clicked the wrong link.
What do REC or BOOT versions even mean? Can anyone explain that? Thanks.
disconmair said:
What do REC or BOOT versions even mean? Can anyone explain that? Thanks.
Click to expand...
Click to collapse
As I told you, you are not on the right thread and your device only has one version of Twrp, the boot.

Categories

Resources