Related
I'M NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR PHONE
Infos
Why Should I root my phone?
Read Here
What can I do with recovery?
With recovery you can principally flash cooked roms, but also other things like make nandroid backups (Internal memory backups), partition your sdcard, fix problems etc...
If you want root there are 2 methods:
First Method
Is very simple, just download and install InstantRoot.apk (attached)
To install this from sdcard you need a file explorer like ASTRO
After the install a notify that says root access gained should appear, if not try second method
Second Method
This will install also recovery
1. Enable Debug USB from Settings->Applications
2. Download flashrec and install it with file manager like ASTRO
3. Download Amon_RA's recovery and put it in your sdcard
4. Run flashrec and tap Backup Recovery
5. Tap in the textbox and write this path:
Code:
/sdcard/recovery-RA-hero-vx.x.x.img
At moment of writing last version is 1.5.2, so the path should be
Code:
/sdcard/recovery-RA-hero-v1.5.2.img
6. Tap Download then flash recoery
7. If you get an error retry from step 3, else continue
8. Turn off your phone and reboot it keeping pressed Home button, recovery should start
9. Connect your phone via usb
10. Download Android SDK and extract all in the same folder
11. Download this and extract it in your sdk/tools folder
12. Open cmd (if you are on windows, if you are on a mac or on linux open terminal) and move to sdk/tools folder using this command
Code:
cd path
13. Give this commands in order
On windows:
Code:
adb shell mount /system
adb push su /system/bin/
adb shell chmod 4755 /system/bin/su
adb push Superuser.apk /system/app/
adb shell umount /system
adb shell reboot
On linux/mac
Code:
./adb shell mount /system
./adb push su /system/bin/
./adb shell chmod 4755 /system/bin/su
./adb push Superuser.apk /system/app/
./adb shell umount /system
./adb shell reboot
14. Now you have root access on your phone
If you want recovery:
Just follow root's second method to the step 7
Flashing Custom roms using recovery:
Custom roms are in Zip format, to flash it is really easy once you have recovery.
Once downloaded a rom put it in your sdcard root, then reboot into recovery (Keep home button pressed while turning on your phone)
Now make a wipe going to Wipe->Wipe data, then come back to main menu and go to Flash zip from sd card, select your zip and you're done
Thanks for the guide How does Nandroid backup fit into this?
maybe you need to tell how to downgrade(or a link to a guide )
nice guide, only i have already rooted my phone(2 months ago or something xD)
@Culturelol
nandroid backup is recommeded when you install a new rom, so you can always back to your original/past rom
So i root with this guide, then nandroid and then i can flash the new rom?
One more small question Is there anything special i should know about flashing the radio?
culturelol said:
So i root with this guide, then nandroid and then i can flash the new rom?
Click to expand...
Click to collapse
Yep
culturelol said:
One more small question Is there anything special i should know about flashing the radio?
Click to expand...
Click to collapse
No, only that you can't flash a GSM radio on a CDMA phone and back, if you do this you'll brick your phone
Exit93 said:
Yep
No, only that you can't flash a GSM radio on a CDMA phone and back, if you do this you'll brick your phone
Click to expand...
Click to collapse
Is that done the same way? Boot to recovery and then flash the radio? And is this done before or after wipe / install of the new rom?
culturelol said:
Is that done the same way? Boot to recovery and then flash the radio? And is this done before or after wipe / install of the new rom?
Click to expand...
Click to collapse
You can install radio whenever you want, it's flashed in another nand partition
nice rom - but the Home button doesnt work - is that normal?
krueck83 said:
nice rom - but the Home button doesnt work - is that normal?
Click to expand...
Click to collapse
Wrong discussion...
If you refer to CKDroid you need to flash googlebits to get home button working...
Exit93 said:
You can install radio whenever you want, it's flashed in another nand partition
Click to expand...
Click to collapse
But it is flashed through the recovery screen?
culturelol said:
But it is flashed through the recovery screen?
Click to expand...
Click to collapse
Yes, it is
Thank you - it works.
Thanks for the instructions.
1-Do you need to follow step 8-12 to get root and flash rom`s or is the android sdk and superuser only if you want to develope yourself?
2- If ypu do this and after want back to stock rom . As far as i`ve read it`s as easy as just flashing from HTC website and you`re back ? Won`t recovery still be left on your phone?
Thanks
Rui-Cruz said:
Thanks for the instructions.
1-Do you need to follow step 8-12 to get root and flash rom`s or is the android sdk and superuser only if you want to develope yourself?
2- If ypu do this and after want back to stock rom . As far as i`ve read it`s as easy as just flashing from HTC website and you`re back ? Won`t recovery still be left on your phone?
Thanks
Click to expand...
Click to collapse
1. Steps from 8 to 12 are only to get root access on stock rom, if you want to change rom you don't need to make those steps
2. To get back to stock rom just flash official update, as far as i know recovery will be deleted
Thanks
Thanks for the guide.
Was being anal and following the guide to the letter (not wanting a brick!) and it just rebooted to stock recovery
Code:
4. Run flashrec and tap Backup Recovery
5. Tap in the textbox and write this path: /sdcard/recovery-RA-hero-v1.5.2.img
6. If you get an error retry from step 3, else continue
Should we be tapping the download button once we entered the img location?
Ne0
alfie196 said:
Thanks for the guide.
Was being anal and following the guide to the letter (not wanting a brick!) and it just rebooted to stock recovery
Code:
4. Run flashrec and tap Backup Recovery
5. Tap in the textbox and write this path: /sdcard/recovery-RA-hero-v1.5.2.img
6. If you get an error retry from step 3, else continue
Should we be tapping the download button once we entered the img location?
Ne0
Click to expand...
Click to collapse
Yes, sorry it's my fault, correcting...
Sorry silly question
Please could someone tell me, if using the first method the InstantRoot.apk. Will this wipe the current ROM/data/apps etc from the phone or will it just enable Root privilages and leave everything else the same?
Many thanks
Jeremy
It just roots your phone and leaves everything in tact, just did it now.
The guide is not clear on how to flash the rom though. Because it says "If you want recovery" I don't want recovery I just want to flash. I have root now what's next? In simple steps, no recovery required just want CKDroid.
hatski said:
It just roots your phone and leaves everything in tact, just did it now.
The guide is not clear on how to flash the rom though. Because it says "If you want recovery" I don't want recovery I just want to flash. I have root now what's next? In simple steps, no recovery required just want CKDroid.
Click to expand...
Click to collapse
You need recovery to flash roms, it's written on the start of the first post
Root from Paul didn't come with one, and seeing as we can't get full system access (from what i understand) im curious as to if we can actually get busybox?
The 'busybox on rooted desire' on MoDaCo didn't help at all.
I've installed bb via Titanium, yet Metamorph didn't recognise it anywhere.
Cheers in advance for help
It comes with A2SD - but you can push the busybox binary to /system while the phone is in recovery.
If you pushed bb yourself, use its absolute path (like /data/somewhere/busybox) or put its path in your $PATH to get it going. I personally, without root, put busybox in the free-to-write-to /sqlite* directory (I put * because I don't recall the full name) and it runs fine from there.
do you have a link to apps2sd & does it come with a guide as to how to install it so noobs can understand?
A2SD was taken down "temporarily".
http://android.modaco.com/content/h...ide-now-with-new-improved-easier-root-method/
Sorry
Although this still seems to work:
http://android.modaco.com/content/htc-desire-desire-modaco-com/307398/apps2sd-miniguide/
LeszekSwirski said:
Although this still seems to work:
http://android.modaco.com/content/htc-desire-desire-modaco-com/307398/apps2sd-miniguide/
Click to expand...
Click to collapse
Bare in mind I think it was taken down as (for some) it 'removed root' and also got some phones stuck in a reboot loop. Bad times.
GANJDROID said:
Root from Paul didn't come with one, and seeing as we can't get full system access (from what i understand) im curious as to if we can actually get busybox?
The 'busybox on rooted desire' on MoDaCo didn't help at all.
I've installed bb via Titanium, yet Metamorph didn't recognise it anywhere.
Cheers in advance for help
Click to expand...
Click to collapse
You didn't read to the end of that thread
* install Titanium
* run Titanium
* click the "problems" button and install Busybox
* boot into recovery
* adb shell from my Mac
* mount /system
* cp /data/data/com.keramidas.TitaniumBackup/files/busybox /system/bin
* cd /system/bin
* ./busybox --install -s .
Click to expand...
Click to collapse
By what I've read, though, Metamorph dies on its arse because of the lack of system rw access.
Loccy said:
You didn't read to the end of that thread
Click to expand...
Click to collapse
Aye, I read that, but no Mac, and I can't get to the folder where Titanium saved bb to (assuming that because it's not on the sd card in any data or the titanium folders) the phone system(?)
jayshah said:
Bare in mind I think it was taken down as (for some) it 'removed root' and also got some phones stuck in a reboot loop. Bad times.
Click to expand...
Click to collapse
Had heard about that, but I think he may be working for a solution?
From what I can remember from the rooting guide he said it was 'currently unavailable'
GANJDROID said:
Had heard about that, but I think he may be working for a solution?
From what I can remember from the rooting guide he said it was 'currently unavailable'
Click to expand...
Click to collapse
Yeah, hence it's hopefully only temporary.
GANJDROID said:
Aye, I read that, but no Mac, and I can't get to the folder where Titanium saved bb to (assuming that because it's not on the sd card in any data or the titanium folders) the phone system(?)
Click to expand...
Click to collapse
Install Titanium. Then get your phone into recovery using Paul's Linux ISO. In the Linux console (i.e. where you'll have typed ./step2.sh to get the recovery up), you should be able to do adb shell from there. Then follow my instructions from mount /system onwards.
I didn't follow Pauls guide as I only have access to Windows, so I used the lanarchy guide, which I think might have been taken from The Unlockr.
Maybe fill me in w/ bb according to that?
i am a bit ashamed to ask this but:
....
* boot into recovery
* adb shell from my Mac
* mount /system
....
boot into recovery -> ok
adb shell from mac.. ok? hm, i have macos as a seperate installation and i used it for rooting, so there is a pushfiles folder with recovery-mac.sh.. sudo ./recovery-mac.sh?
How do i mount /system then? Don't know where to navigate to find access to the sdcard . @volumes there are only my harddrive partitions, can't see the sdcard?
No idea, sorry, first time (ok, second time after root) i get in touch with adb, mac, sudo wtf?
Ok, all you need is some kind of environment where adb actually works.
Get your phone into recovery (the green menu screen) using whatever means or method you have.
Then, if you have Windows, you'll need the Android SDK. Ditto on a Mac. Anything with adb so that you can plug your device into your computer, do adb shell, and get a shell window up. Then
mount /system
onwards.
The key is that your phone needs to be in recovery before you do adb shell, otherwise you have no r/w access to /system.
ah! ok, perfect. The android sdk is on my windows computer, the push-files on my mac, that's the problem
thanks for your help!
the recovery is not the problem, but mount /system did nothing because there is no android sdk on my mac.. got it now i think.
mount system -> ok
copy busybok -> ok
when i try to install i get dozens of lines with "no such file or directory".
reboot -> phone not booting, hangs when displaying the HTC Logo omg
flash rom again?
same problem as watercool. Loads of "No such file or directory" messages.
But, I rebooted and it went through as normal, booted the OS fine.
hm, dont want to wipe again, pff..
flashed AhmgskMod mod again without wiping, everything ok now
watercool said:
mount system -> ok
copy busybok -> ok
when i try to install i get dozens of lines with "no such file or directory".
reboot -> phone not booting, hangs when displaying the HTC Logo omg
flash rom again?
Click to expand...
Click to collapse
Sounds like you missed the . off of the end of the
./busybox --install -s .
command.
You need that . if you're following my instructions.
ok, i did it with and without the "."
With the dot there was no response (so probably it installed correctly?).
Anyway it didn't boot afterwards. i will try it again
edit: ok, tried again and my phone stucks @ htc screen
i think busybox is installed but for some reason it doesn't boot (using the ahmgsk mod)
anyway, thanks for your kind help!
I'm trying to remove some preinstalled apps from /system/app folder. My phone is rooted.
When I'm trying this over adb it says that I only have Read permissions. What am I doing wrong?
Put the phone into recovery mode then do the adb commands.
You only have read access while booted. R/W access while in recovery.
Mh I tried this but I couldn't even open the shell, said something.sh is missing.
You mean the normal recovery and not Clockworkmod or something, right?
You have to put it in the custom recovery. Clockworkmod or whichever one you use.
Ah okay, thank you, I will try that.
Though I need to use the normal recovery.
I tried it with clockwork now. It works but when I do "cd system" and do "ls" it's empty...so I can't see any app-folder?!
Edit: Oh I forgot - do I need to mount system first using the partitions menu?!
Eggcake said:
I tried it with clockwork now. It works but when I do "cd system" and do "ls" it's empty...so I can't see any app-folder?!
Edit: Oh I forgot - do I need to mount system first using the partitions menu?!
Click to expand...
Click to collapse
Code:
mount /system
At the adb shell.
Oy, thanks now I finally got it
Remove worked, pull didn't (or it took >5min for a simple apk file and I aborted it too early).
after rooting, unlocking nand etc.
do I still have to reboot in to recovery with "recovery-windows.bat", or should I be able to do it without it????
thanks for answering
I'm a new too, but I don't think you need it. If you install a custom recovery and select 'Recovery' from the bootloader, it should launch your custom recovery. If you want to get to recovery without going into the bootloader, check out Quick Boot. It's much easier than going through the bootloader.
Provided you flashed a custom recovery you do not need to use a computer to boot into recovery
thanx for your replies
can you please post a link how to flash recovery and which
bklynfire said:
thanx for your replies
can you please post a link how to flash recovery and which
Click to expand...
Click to collapse
I personally like the AmonRA recovery because of the easy navigation using the few buttons we have. Others prefer Clockwork; though with that one, some have noticed that when wiping,the recovery doesn't exactly wipe completely (or something to that effect, I could be wrong). Try downloading ROM Manager, from there you can flash Clockwork or an alternative recovery, which would be AmonRA. Otherwise, go to the Development forum and search for how to flash AmonRA recovery.
horiveira said:
I personally like the AmonRA recovery because of the easy navigation using the few buttons we have. Others prefer Clockwork; though with that one, some have noticed that when wiping,the recovery doesn't exactly wipe completely (or something to that effect, I could be wrong). Try downloading ROM Manager, from there you can flash Clockwork or an alternative recovery, which would be AmonRA. Otherwise, go to the Development forum and search for how to flash AmonRA recovery.
Click to expand...
Click to collapse
I am trying to use rom manager i get this error
"an error occurred while attempting to run privileged commands"
bklynfire said:
I am trying to use rom manager i get this error
"an error occurred while attempting to run privileged commands"
Click to expand...
Click to collapse
I don't know much about Clockwork, but that message makes it sound like you don't have full root.
Are you root yet? If so, did you give ROM Manager su (super user) permission?
i rooted fine i think (cuz I added foreign fonts succesfuly)
how would I check it
???
if you have your phone connected to your computer and adb running proper
from a command line run
adb shell
Click to expand...
Click to collapse
should return
$
Click to expand...
Click to collapse
type
$ su
Click to expand...
Click to collapse
press enter and it should change to
#
Click to expand...
Click to collapse
if you dont see a # or you get a "permission denied" youre not root. try again.
nenn said:
if you have your phone connected to your computer and adb running proper
from a command line run
should return type
press enter and it should change to
if you dont see a # or you get a "permission denied" youre not root. try again.
Click to expand...
Click to collapse
this is what i got
C:\androidsdk\tools>adb shell
adb server is out of date. killing...
* daemon started successfully *
# su
su
#
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