Develop Bugs

[Q] Noob Question

Okay, I am getting ready to root my phone tonight...
As far as all that - I think I got all that covered.
As far as flashing a recovery - I want to use amon-ra's - RA-evo-v1.8.0 found here - http://forum.xda-developers.com/showthread.php?t=705026
In that post it gives two differant ways to flash the recovery:
via fastboot
Code:
Copy recovery-RA-evo-v1.8.0.img to a location where fastboot can find it.
Boot your phone into fastboot mode
fastboot devices(press enter) (to make sure that fastboot "sees" your phone)
fastboot flash recovery recovery-RA-evo-v1.8.0.img(press enter)
via terminal app or adb => Make sure your rom contains flash_image!!
Code:
Copy recovery-RA-evo-v1.8.0.img to the root of your sdcard
start the terminal app or launch adb
su(press enter)
flash_image recovery /sdcard/recovery-RA-evo-v1.8.0.img(press enter)
reboot recovery(press enter)
My questions are:
first of all - what is "Fastboot"?? I mean is it an application that I can download and install it this way?
second of all - what is a "terminal app"
&
third - what is "adb"?
I keep hearing the term "shell", is a "shell" the same as windows command prompt? Or is that "adb"?
I know these are probably stupid questions for most, but I like to have every thing ready to go before I tackle projects...
Any guidance would be greatly appriciated!!
J

Another option is to install ROM manager and install AmonRa that way. (think you have to pay) Open it and click on Flash Alternate Recovery.
Terminal app is just an application providing terminal-like access to the system. Imagine the command prompt on a Windows system, but understand your phone is running Linux underneath the hood so the commands are different.
adb likely is an acronym for something along the lines of debugger or something. It essentially allows you to communicate with your phone from your computer. So, go to a command prompt and you can enter commands to execute on your phone via adb. (shell = command prompt, adb runs within the shell/command prompt)
You're right in trying to find out as much as possible before tackling something like this.

terrel_b said:
Another option is to install ROM manager and install AmonRa that way. (think you have to pay) Open it and click on Flash Alternate Recovery.
Terminal app is just an application providing terminal-like access to the system. Imagine the command prompt on a Windows system, but understand your phone is running Linux underneath the hood so the commands are different.
adb likely is an acronym for something along the lines of debugger or something. It essentially allows you to communicate with your phone from your computer. So, go to a command prompt and you can enter commands to execute on your phone via adb. (shell = command prompt, adb runs within the shell/command prompt)
You're right in trying to find out as much as possible before tackling something like this.
Click to expand...
Click to collapse
Great, thanks for the response! That helps alot - I searched around a little while waiting for a reply and still didnt clear any thing up. I have already DL'd ROM Manager and I will just use that... I just like to have as much info as I can...
Thank you!
J

How are you going to root? if you are going to use unrevoked (doesn't work with hboot2.02) just open unrevoked without the phone connected and then point it to the amon-ra recovery.img you downloaded, up at the top its under file dropdown or somewhere up there then unrevoked will flash ra for you automatically

fastboot is an option under HBOOT(power of your phone power on pressing power and volume down it is the first option)
terminal app is an app that is like the command prompt in windows on your phone a good one is terminal emulator
adb is is Android debug bridge like stated above. it is for people that like to use the cmd(command prompt) on your computer to do things with your phone like pulling apps off your phone, pushing them on your phone, and other like this most of this can be done using root explorer to place the flies or making a flashable zip. another thing adb is used for is getting your phone out of boot loops that you cant any other way. never had to do this so dont know how. i think adb and adb shell are basically the same thing not 100 on that one. here are some likes about adb for you
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
http://www.gadgetsdna.com/android-terminal-adb-shell-command-list/1168/
as for using terrel_b's suggestion this is a good suggestion. using rom manager you can flash your recovery this way it is very easy way to do this it is free there is a paid version of rom manager it is for using extra things on clockwork recovery, so basically the only thing you will use rom manager for, if you decide to use it, is flashinf your recovery unless you use clockwork. the reason clockwork is not used more is that there are questions if it wipes everything properly and if something is not wiped right it can cause lots of problems. of and just in case you are wonndering rom manager is an app you can get off the market.
hope this helps and if you need anything else ask

ifly4vamerica said:
How are you going to root? if you are going to use unrevoked (doesn't work with hboot2.02) just open unrevoked without the phone connected and then point it to the amon-ra recovery.img you downloaded, up at the top its under file dropdown or somewhere up there then unrevoked will flash ra for you automatically
Click to expand...
Click to collapse
Im using unrevoked... I am still running hboot 0.97.0000... thanks for the input, I appriciate it!!
J

roscoenr said:
fastboot is an option under HBOOT(power of your phone power on pressing power and volume down it is the first option)
terminal app is an app that is like the command prompt in windows on your phone a good one is terminal emulator
adb is is Android debug bridge like stated above. it is for people that like to use the cmd(command prompt) on your computer to do things with your phone like pulling apps off your phone, pushing them on your phone, and other like this most of this can be done using root explorer to place the flies or making a flashable zip. another thing adb is used for is getting your phone out of boot loops that you cant any other way. never had to do this so dont know how. i think adb and adb shell are basically the same thing not 100 on that one. here are some likes about adb for you
http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
http://www.gadgetsdna.com/android-terminal-adb-shell-command-list/1168/
as for using terrel_b's suggestion this is a good suggestion. using rom manager you can flash your recovery this way it is very easy way to do this it is free there is a paid version of rom manager it is for using extra things on clockwork recovery, so basically the only thing you will use rom manager for, if you decide to use it, is flashinf your recovery unless you use clockwork. the reason clockwork is not used more is that there are questions if it wipes everything properly and if something is not wiped right it can cause lots of problems. of and just in case you are wonndering rom manager is an app you can get off the market.
hope this helps and if you need anything else ask
Click to expand...
Click to collapse
Very helpful info - thanks!! I have already DL'd ROM Manger Pro...

Okay - another question, can i place the amon-ra recovery on the SD card BEFORE i root the phone or should I do that AFTER I root the phone? Just curious, I dont even know if it matters one way or the other... Just want to be sure before I do it...

Okay - I ROOTed using unrEVOked3.... Success! I do have a question though - I clicked on the superuser icon and nothing comes up?!? Is that right? I thought it was an app that gave you all kinds of stuff?? I guess I could have misunderstood the purpose of "superuser" - Also, After ROOT, I have not installed a new ROM yet - does the 4G still work with the stock ROM? I clicked the 4G button and it still says 3G... anyway Im gonna flash the Amon-Ra recovery now...

JayStation3 said:
Okay - I ROOTed using unrEVOked3.... Success! I do have a question though - I clicked on the superuser icon and nothing comes up?!? Is that right? I thought it was an app that gave you all kinds of stuff?? I guess I could have misunderstood the purpose of "superuser" - Also, After ROOT, I have not installed a new ROM yet - does the 4G still work with the stock ROM? I clicked the 4G button and it still says 3G... anyway Im gonna flash the Amon-Ra recovery now...
Click to expand...
Click to collapse
Well superuser gives root permissions to new applications loaded on a rooted android 2.2 platform phone.
To load a new ROM, flash via first on recovery.
Hope that helps, sorry I was being in a bit of short there eariler but I edited my post right I hope, others can check too.

alekosy said:
Well superuser gives root permissions to new applications loaded on a rooted android 2.2 platform phone.
To load a new ROM, flash via first on recovery.
Hope that helps, sorry I was being in a bit of short there eariler but I edited my post right I hope, others can check too.
Click to expand...
Click to collapse
No - you were very helpful... I got it ROOTed, now I just want to change my recovery to amon-ra so I can use my 4G...
4G is not working now - so im assuming I need to flash a new recovery... I heard amon-ra does the trick...

JayStation3 said:
No - you were very helpful... I got it ROOTed, now I just want to change my recovery to amon-ra so I can use my 4G...
4G is not working now - so im assuming I need to flash a new recovery... I heard amon-ra does the trick...
Click to expand...
Click to collapse
Edited: http://forum.xda-developers.com/showthread.php?t=715525
see if that helps.
OR
Read this http://forum.xda-developers.com/showthread.php?t=705026

alekosy said:
Edited: http://forum.xda-developers.com/showthread.php?t=715525
see if that helps.
OR
Read this http://forum.xda-developers.com/showthread.php?t=705026
Click to expand...
Click to collapse
Everything is there, pretty much solid on the information. I hope it works out for you, if not don't RUSH and take your sweet old time browsing the forums for help. GL

Strange the wimax should still work did you reboot and try 4g again? Unrevoked isn't known to break wimax
sent from my EVO at the edge of hell

alekosy said:
Edited: http://forum.xda-developers.com/showthread.php?t=715525
see if that helps.
OR
Read this http://forum.xda-developers.com/showthread.php?t=705026
Click to expand...
Click to collapse
cool, I will read them and figure it all out... thanks for the info... i flashed amon ra last night, did a back up w/ TB... did a NAND back up through the recovery of the phone... Im just a little confused on the differant recoveries...

Jbcarrera said:
Strange the wimax should still work did you reboot and try 4g again? Unrevoked isn't known to break wimax
sent from my EVO at the edge of hell
Click to expand...
Click to collapse
I thought I did reboot at least once, when I was preforming the NAND back up - but Im rebooting now and I will test it out again...
I do not have great 4G signal here at my house, so that may be it as well... I will mess with it and see whats up through out the day and let you know tonight...
I have noticed that my touch screen doesnt seem as responsive as it was and the phone in general is kind of glichy...

Ok, my 4G is still working... I must not have had a strong enuf signal at my house for it to kick in... No I'm having problems getting tether to work... I started a new thread on that one though...
Sent from the MATRIX... while plugged into my EVO... using the XDA app... from a galaxy far-far away.......

[Q] ADB shell error 'adb error device not found'

Galaxy Nexus GSM........
I cannot connect via ADB to my phone. ADB shells but 'adb devices' none is found. Drivers are installed correctly per device manager. Debugging is on.
The only thing I've found in the forums is that I can't select 'none' as my USB connection. The two check boxes won't un-check only behave like radio buttons.

I have always had to use "fastboot devices". Not sure if that is what u are looking for.
Sent from my Galaxy Nexus using Tapatalk 2

Uninstall all drivers and install those from the naked driver thread over in development.
'fastboot devices' is used only when on bootloader.
Sent from my i9250

no luck
No luck. Always get 'no drivers for you phone found'. I guess I should have mentioned that I'm on W7/64 I did notice that mentioned a lot in the threads........ Any need to select the type of USB connection (none is not an option) ?
TIA, Jeff

getting there......
OK I am getting further. When I enter adb devices I can see my phone until I type 'adb reboot bootloader'. As soon as I enter that command the phone does reboot into the bootloader but the USB connection drops as well.
Jeff

Try this drivers bro
Galaxy Nexus AOKP m5 Franco kernel m3

[email protected] said:
OK I am getting further. When I enter adb devices I can see my phone until I type 'adb reboot bootloader'. As soon as I enter that command the phone does reboot into the bootloader but the USB connection drops as well.
Jeff
Click to expand...
Click to collapse
That is because you just installed the "adb" driver for your device. You still need to install the "fastboot" driver. It is the same driver, it just needs to be installed twice - once when your device is booted normally, and once when it is booted in fastboot mode. I personally would use the Universal Naked Drivers by 1wayjonny that bk201doesntexist mentioned, not the PDA drivers or Samsumg drivers or any other ones. 1wayjonny's drivers do not install any other software on your PC - they are just the drivers, unlike the PDA drivers.

Thanks all getting there. Thanks efrant that got me to the next problem .
I unlocked the bootloader and pushed su.zip no problem. Now I have flashed su.zip successfully but I don't have root. I have flashed many times with no luck.
Jeff

[email protected] said:
Thanks all getting there. Thanks efrant that got me to the next problem .
I unlocked the bootloader and pushed su.zip no problem. Now I have flashed su.zip successfully but I don't have root. I have flashed many times with no luck.
Jeff
Click to expand...
Click to collapse
Use the version of su.zip from this post. I just made it yesterday with the latest binary and app, so that one will work.

Thanks efrant that worked. I have root and installed busybox.
There was a really good terminal app that showed up when you flashed Cyanogen but I can't find it in the store. Does anyone know the name? The main thing that I need out of this whole endeavor is ssh and the terminal that came on CM8 and/or 9 was perfect.
Jeff

[email protected] said:
Thanks efrant that worked. I have root and installed busybox.
There was a really good terminal app that showed up when you flashed Cyanogen but I can't find it in the store. Does anyone know the name? The main thing that I need out of this whole endeavor is ssh and the terminal that came on CM8 and/or 9 was perfect.
Jeff
Click to expand...
Click to collapse
grab a cm9 nightly zip and extract apk from /system/app

pm setinstall location 2
if you want to set install location to sd card and move all apps to sd then read my thread http://forum.xda-developers.com/showthread.php?t=1754722

Bricked asus transformer prime
Hey i get the same message and i go to devices and it shows my device in fastboot mode but when i go to use the adb shell command and the adb devices it shows no tablet
can you please help
the system is wiped and data is wiped and i cant seem to get it to read my sd card
please help
thanks

NewDev4IOS said:
Hey i get the same message and i go to devices and it shows my device in fastboot mode but when i go to use the adb shell command and the adb devices it shows no tablet
can you please help
the system is wiped and data is wiped and i cant seem to get it to read my sd card
please help
thanks
Click to expand...
Click to collapse
what tablet? this here is galaxy nexus q&a forum, thread was created 2 months ago.
oh and adb isnt available in bootloader, only recovery and android. boot to recovery.
Sent from my i9250

Solution
[email protected] said:
Galaxy Nexus GSM........
I cannot connect via ADB to my phone. ADB shells but 'adb devices' none is found. Drivers are installed correctly per device manager. Debugging is on.
The only thing I've found in the forums is that I can't select 'none' as my USB connection. The two check boxes won't un-check only behave like radio buttons.
Click to expand...
Click to collapse
Make sure that you have your drivers properly installed. View this guide to fix that : http://goo.gl/OS3Vi
If you still encounter the problem then you can use ADBwireless : http://goo.gl/2Ehso
Hope it helps

Need instuctions for ADB pull cracked screen

i have an e4gt screen cracked and i need to get internal sd card data. i have done several searches and have come across ADB pull but not clear on how to perform this. i am rooted w stock 4.1 using whatever recovery came with the stock+rooted ROM. (SPH-D710_GB27_1014481_Rooted_Nodata.tar.md5 from Rwilco12's Android Repository). If I could just remember the exact steps to mount usb from recovery i would be good lol... any suggestions would be greatly appreciated!

Ive the same problem if someone would help.
Sent from my GT-I9300 using xda premium

No need. Just power up your device and connect to your pc. It will connect using mtp and allow you to access your files that way (as long as you hadn't deactivated it prior to cracking your screen.)
Sent from my SPH-D710 using Tapatalk 2

There's a way to get your screen to pc...
Sent from my GT-I9300 using xda premium

hlxanthus said:
No need. Just power up your device and connect to your pc. It will connect using mtp and allow you to access your files that way (as long as you hadn't deactivated it prior to cracking your screen.)
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
i have done that and i get a box that says "there was a problem installing this MTP device." then another box says MTP was not installed correctly. Well i do have the Samsung drivers installed. Even installed a fresh copy direct from samsung support. Maybe something to do with my screen being locked with pin? Just got the Galaxy4 cant wait to get my data back...lol

Okay, assuming you already have android SDK set up and working ( you get adb this way), flash a recovery. I would likely use the direct boot for simplicity.
http://www.rwilco12.com/downloads.p...overy Kernels/GB/Noobnl Direct Boot/One-Click
That is for the one click version of the direct boot kernel/recovery. It is gingerbread based, but that shouldn't matter if it will boot the ROM later a due to kernel mismatch due to the broken screen lol.
Give it some time too verify you are in the recovery. Now the magic. Find where your adb is at, usually within android/platform_tools if memory serves. You can do a system search for adb and it should pop up. Move to that location. Make a note of the exact path to that location. Now open a command prompt (search for cmd.exe). You then need to switch to the location of your adb. It should be something like the "cd c:/path/to/adb" (no quotes) where you fill in the path you noted earlier. Once there, give this a go. Type "adb devices" (again no quotes) and if you get a string of numbers that means you have adb access!!! Then you can just type "adb pull /sdcard/" and that will drop the contents of your internal storage into the folder holding your adb files (kind of a mess but it is the easiest way to do it). If you would rather it be dropped in a location of your choosing, use this "adb pull /sdcard/ /path/to/desired/location/" and note there is a space between /sdcard/ and your path to desired location.
I am not expert at this, but let me know if you get stuck somewhere in this and I will try to help.
Sent from my Nexus 7 using Tapatalk 2

Hi thanks for the detailed response. i will need to make some time to go through these steps lol however i will update!

[Q] Kernal help

Hi i need to find a kernal with usb debugging and adb setting in developer settings automatically ticked because my phone screen is completely broken and im using a program that requires the two settings to be on. Please help if you can thank you!

I don't think a kernel can enable those, only the user can.. You can probably flash a ROM that has them enabled or a script
Sent from my SGH-M919 using Tapatalk

serio22 said:
I don't think a kernel can enable those, only the user can.. You can probably flash a ROM that has them enabled or a script
Sent from my SGH-M919 using Tapatalk
Click to expand...
Click to collapse
I also broke my screen and was looking for this exact thing. It's Android Control and I need adb enabled. I tried various ways I found while searching to try to enable adb through TWRP and an adb shell on my PC, but it wouldn't work ( kept getting a "~ # ?[6n" prompt and "not found" when entering "su" ).
Then I found this kernel kitchen. In that thread the dev says you can make the ramdisk insecure and make adb mode persistent. Anybody able to help me out?

brokenchains said:
I also broke my screen and was looking for this exact thing. It's Android Control and I need adb enabled. I tried various ways I found while searching to try to enable adb through TWRP and an adb shell on my PC, but it wouldn't work ( kept getting a "~ # ?[6n" prompt and "not found" when entering "su" ).
Then I found this kernel kitchen. In that thread the dev says you can make the ramdisk insecure and make adb mode persistent. Anybody able to help me out?
Click to expand...
Click to collapse
What version? Mdl mk2 or nb4? Probably already insecure boot.img unless you're running stock tho
Debugging in dev options would be a different story tho. I might be able to figure out how to enable it thru command line tho
And now that I think about it, I don't even know what would work since you're dual booting.

ShinySide said:
What version? Mdl mk2 or nb4? Probably already insecure boot.img unless you're running stock tho
Debugging in dev options would be a different story tho. I might be able to figure out how to enable it thru command line tho
And now that I think about it, I don't even know what would work since you're dual booting.
Click to expand...
Click to collapse
I figured out how to get adb shell working, but I had to switch TWRP out for CWM non-touch. That let me use adb correctly through recovery and I found a way to enable adb in the ROM that way by pulling settings.db and editing the "adb_enabled" setting there. Now I'm just caught because I can't see the screen to authorize my PC to use adb... I tried to manually put the adb key from my PC's file into the adb_keys file on the phone but that didn't work and I'm pretty sure I did it right. That process is described here for anyone curious.

Software Update Loop Bricked FireTV

OK here is the story
FireTV 51.1.0.2_user_510058520 2 days old
Rooted and installed busybox everything was fine. So I figured I wanted the latest Rootable version.
Followed this guide (http://www.aftvnews.com/how-to-manually-upgrade-or-downgrade-the-amazon-fire-tv/ )
Problems started here: at the end trying to push update.zip to cache got error "cannot stat ‘update.zip’: no such file or directory"
update.zip was in same directory as adb
So I went and Installed Clockworkmod Recovery and pushed it using "adbfire" since it can push files to /sdcard (used this other guide http://www.aftvnews.com/how-to-install-clockworkmod-custom-recovery-on-the-amazon-fire-tv/)
Went and rebooted into clockworkmod and that's when I saw the Previous command running trying to install update.zip wich was not there cuz I was never able to push it in the first place.
Well I could not get out of there by any means since I don't have a USB keyboard with me anymore
well I pushed the update.zip to /sdcard (again using adbfire) and used the mv command to transfer the file to /cache aaaaaaand reboot
Now I have my android logo updating the firmware and rebooting the FireTV when reaching the middle of the process just to start again and again
note: I can still connect to my firetv via adb while the screen is on and lose connection when reboots.
Any help would be greatly appreciated
Thanks in advance

LastDeuS said:
OK here is the story
FireTV 51.1.0.2_user_510058520 2 days old
Rooted and installed busybox everything was fine. So I figured I wanted the latest Rootable version.
Followed this guide (http://www.aftvnews.com/how-to-manually-upgrade-or-downgrade-the-amazon-fire-tv/ )
Problems started here: at the end trying to push update.zip to cache got error "cannot stat ‘update.zip’: no such file or directory"
update.zip was in same directory as adb
So I went and Installed Clockworkmod Recovery and pushed it using "adbfire" since it can push files to /sdcard (used this other guide http://www.aftvnews.com/how-to-install-clockworkmod-custom-recovery-on-the-amazon-fire-tv/)
Went and rebooted into clockworkmod and that's when I saw the Previous command running trying to install update.zip wich was not there cuz I was never able to push it in the first place.
Well I could not get out of there by any means since I don't have a USB keyboard with me anymore
well I pushed the update.zip to /sdcard (again using adbfire) and used the mv command to transfer the file to /cache aaaaaaand reboot
Now I have my android logo updating the firmware and rebooting the FireTV when reaching the middle of the process just to start again and again
note: I can still connect to my firetv via adb while the screen is on and lose connection when reboots.
Any help would be greatly appreciated
Thanks in advance
Click to expand...
Click to collapse
Well you can do
Code:
adb reboot recovery
to get to recovery, Then in one window run
Code:
adb shell
and in then run
Code:
/sbin/recovery-input
and then in another window run adb shell again and this time run killall recovery. Then you can use recovery-input to control recovery. I would recommend pushing one of the prerooted updates, flashing it, doing a factory reset, then reboot and it should be fine. Another option is to use adb sideload.

rbox said:
Well you can do
Code:
adb reboot recovery
to get to recovery, Then in one window run
Code:
adb shell
and in then run
Code:
/sbin/recovery-input
and then in another window run adb shell again and this time run killall recovery. Then you can use recovery-input to control recovery. I would recommend pushing one of the prerooted updates, flashing it, doing a factory reset, then reboot and it should be fine. Another option is to use adb sideload.
Click to expand...
Click to collapse
First thanks for your quick reply
the thing is my current state is Recovery looping while the firetv tries to install the new software so what I see is
Amazon logo
Android logo updating but just the blue bar filling
then shuts down
then android logo again and again
the commands you recommended were adb reboot recovery ----> /sbin/sh: not found
adb shell ---->/sbin/sh: not found
/sbin/recovery-input ----> Welcome to recovery input (this one works but I'm not quite where I need to be to control anything)
killall recovery ----> This command just reboots again into the same state
You also mentioned adb sideload but that's after I regain control of recovery right???
Please let me know other options to get out of this loop
Thanks again

LastDeuS said:
First thanks for your quick reply
the thing is my current state is Recovery looping while the firetv tries to install the new software so what I see is
Amazon logo
Android logo updating but just the blue bar filling
then shuts down
then android logo again and again
the commands you recommended were adb reboot recovery ----> /sbin/sh: not found
adb shell ---->/sbin/sh: not found
/sbin/recovery-input ----> Welcome to recovery input (this one works but I'm not quite where I need to be to control anything)
killall recovery ----> This command just reboots again into the same state
You also mentioned adb sideload but that's after I regain control of recovery right???
Please let me know other options to get out of this loop
Thanks again
Click to expand...
Click to collapse
If recovery is still in some kind of a loop, doing rm /cache/recovery/* while in adb shell should clear that up.

rbox said:
If recovery is still in some kind of a loop, doing rm /cache/recovery/* while in adb shell should clear that up.
Click to expand...
Click to collapse
I tried rm /cache/recovery/* and I think it erases that folder cuz when trying to run same command again it states as no such file or directory but then I wait and reboots again into same loop
again ran killall recovery and nothing reboot again looping T_T

LastDeuS said:
I tried rm /cache/recovery/* and I think it erases that folder cuz when trying to run same command again it states as no such file or directory but then I wait and reboots again into same loop
again ran killall recovery and nothing reboot again looping T_T
Click to expand...
Click to collapse
I dunno. Recovery shouldn't be doing any looping... With an empty /cache/recovery it should just sit there and do nothing. And it makes it more difficult without a usb keyboard.

rbox said:
I dunno. Recovery shouldn't be doing any looping... With an empty /cache/recovery it should just sit there and do nothing. And it makes it more difficult without a usb keyboard.
Click to expand...
Click to collapse
I can bring a keyboard from work tomorrow if that would help us troubleshoot cuz right now my keyboard is wireless
I know I've been asking a lot this last hour but can you please point me in the right direction so tomorrow I can Try something else using an usb keyboard?

Boot to recovery mode with a keyboard. (ALT + PRINT/SYSRQ + i when booting) x 4
Press HOME
Reset Cache
Reboot
or
Boot to recovery mode with a keyboard. (ALT + PRINT/SYSRQ + i when booting) x 4
Press HOME
Reset to factory defaults
Reboot

roligov said:
Boot to recovery mode with a keyboard. (ALT + PRINT/SYSRQ + i when booting) x 4
Press HOME
Reset Cache
Reboot
or
Boot to recovery mode with a keyboard. (ALT + PRINT/SYSRQ + i when booting) x 4
Press HOME
Reset to factory defaults
Reboot
Click to expand...
Click to collapse
Well yesterday I couldn't bring the keyboard but now I have it in front of me but I haven't been able to reproduce the recovery mode with the keyboard combination.
I know it works because the firetv reboots but sometimes goes to the initial amazon logo and sometimes just the same updating android logo
So any suggestions now that we have the keyboard here???

OK I finally figured it out.
All started when I ran the command "echo --update_package=/cache/update.zip > command" to update to a stock ROM but was never able to PUSH the actual file... kept getting error "cannot stat ‘update.zip’: no such file or directory"
THEN
I successfully installed Clockworkmod Recovery (luckily) and when rebooted to recovery I was presented with Clockwmod Recovery asking if sure to install the NON PRESENT "rom.zip"
BUT i didn't have a keyboard with me at that moment and didn't know the "control recovery" command either... SO I thought to find a different way to PUSH the file....
So I used push file function in adbfire to get the file into /sdcard/ and the the mv command to get it to /cache
SO I got my problem right there wich I was able to reproduce today: When you connect to adb during recovery or booting the FireTV you will get this error for most commands including su ----> "/sbin/sh: not found"
NOW if you try to push a file it will say it got pushed but only half of it or some shortcut of it I'm not sure
The thing is with that half pushed file the system now obeys "echo --update_package=/cache/update.zip > command" and starts updating and shuts down reboots and update again, whatever you do it keeps on booting again to the same state(trust me nothing works)
What I did basically with the few seconds I got between reboots I ran "rm -f /cache/*.bin" and rm -f /cache/*.zip to erase all cache folder and then I was again asked to install the file (not there again) and disabled recovery flash
Anyways thanks for all the replys I got really appreciated all your help and keep up the good work ppl I hope this helps someone out there besides me.
I'm now running the latest prerooted rom from rbox thanks again for that
have a good one
question: Is there an actual gui windows app to transfer files to FireTV???
2: Do I need to block updates for this custom rom also or that's already implemented?

The pre-rooted ROM blocks updates. You can check using TiBU. I think three files are frozen.
Glad you pulled out of your crash.

schneid said:
The pre-rooted ROM blocks updates. You can check using TiBU. I think three files are frozen.
Glad you pulled out of your crash.
Click to expand...
Click to collapse
It doesn't. But if you had dcp blocked before installing it, it'll remain blocked. You should always have dcp blocked.

rbox said:
It doesn't. But if you had dcp blocked before installing it, it'll remain blocked. You should always have dcp blocked.
Click to expand...
Click to collapse
TiBU shows mine "frozen". Did I do that previously with something else?

schneid said:
TiBU shows mine "frozen". Did I do that previously with something else?
Click to expand...
Click to collapse
Either you froze it with titanium previously or you did the pm disable command.

rbox said:
Either you froze it with titanium previously or you did the pm disable command.
Click to expand...
Click to collapse
I did do the PM disable thing but thought your rooted ROM would undo it. Guess not. Anyway, I'm happy. Thanks.

Think I bricked mine
Just got my firetv and did the usual ie. rooted, su added , then I Installed Clockworkmod Recovery and tried to upgrade to the latest rootable firmware, using update.zip to /cache and then it just keeps rebooting.
No amazon screen, goes to Andriod loads 1/3 of the way andf reboots, over and over.
picture attached
Cant adb to it , when doing the alt+print screen+i with my keyboard just reboots it faster
Think i'm offically bricked and its a bummer , be careful when changing firmware with CWR and sending your update.zip .
I dont know where it went wrong but it did

Note3usr said:
Just got my firetv and did the usual ie. rooted, su added , then I Installed Clockworkmod Recovery and tried to upgrade to the latest rootable firmware, using update.zip to /cache and then it just keeps rebooting.
No amazon screen, goes to Andriod loads 1/3 of the way andf reboots, over and over.
picture attached
Cant adb to it , when doing the alt+print screen+i with my keyboard just reboots it faster
Think i'm offically bricked and its a bummer , be careful when changing firmware with CWR and sending your update.zip .
I dont know where it went wrong but it did
Click to expand...
Click to collapse
Don't use update.zip and don't put it in /cache. Since so many people seem to be screwing up by doing that, I'm going to disable the automatic flashing in the next version. As for not being able to adb to it, it's probably using a different ip than what you are expecting. In every instance of people doing this, adb has always worked. Then just rm whatever you put in /cache. Next time use sideload or put it in /sdcard.

rbox said:
Don't use update.zip and don't put it in /cache. Since so many people seem to be screwing up by doing that, I'm going to disable the automatic flashing in the next version. As for not being able to adb to it, it's probably using a different ip than what you are expecting. In every instance of people doing this, adb has always worked. Then just rm whatever you put in /cache. Next time use sideload or put it in /sdcard.
Click to expand...
Click to collapse
I send the update.zip to the ftv with Amazon FireTV Utility App and it looked like it went all the way through , by default isnt that where it send it to ? /cache
Ive been trying to ping the ip , or shell to it but how much times could I have when it just keeps cycling. I dont think its possible to adb to it at this point as I get the attached screen for like 10 seconds or something it will just hold at the all white amazon logo if i'm screwing around with the keyboard combantions , i'm just stuck at this point and dont wanna keep burning hours if i cant go further.
I'm assuming its trying to load whatever is in the /cache folder which is either nothing or ave an update.zip file no idea
thanks for the reply as i will try some more to adb in

I am in a similar boat. I tried to install "rom.zip" per the instructions here http://www.aftvnews.com/how-to-install-a-custom-rom-image-on-the-amazon-fire-tv/
but it would not install it from CWM. It would abort the installation instantly. I read another thread where someone wasn't able to do something through ADB Shell because of SU permissions. I tried to uninstalled it and sideloaded SuperSU again. When I accessed it instead of clicking on "Normal" I chose the other option. Well, it's not stuck in the same loop as mentioned here.
I see the Amazon logo briefly, then it shows the android logo and reboots. It disconnects for a few seconds with the TV saying there is no HDMI connection and then shows the amazon logo shortly after again. I can no longer ADB into it.
Please help.

Note3usr said:
I send the update.zip to the ftv with Amazon FireTV Utility App and it looked like it went all the way through , by default isnt that where it send it to ? /cache
Ive been trying to ping the ip , or shell to it but how much times could I have when it just keeps cycling. I dont think its possible to adb to it at this point as I get the attached screen for like 10 seconds or something it will just hold at the all white amazon logo if i'm screwing around with the keyboard combantions , i'm just stuck at this point and dont wanna keep burning hours if i cant go further.
I'm assuming its trying to load whatever is in the /cache folder which is either nothing or ave an update.zip file no idea
thanks for the reply as i will try some more to adb in
Click to expand...
Click to collapse
Hey your problem is really similar to mine and what I did was connect to adb in between the loops and erase all cache
try searching on your router or do a scan on your network and find the correct ip address for the firetv
also don't worry about not being able to SU just erase cache using "rm -f /cache/*.bin" and "rm -f /cache/*.zip"
then it will ask for the actual file and just choose "not to install" then "disable recovery flash"
pd: Don't try to enter recovery by keyboard combinations it's useless trust me I tried A LOT