Related
Just got a "factory refurbished" Kindle Fire 8.9 HD for a STEAL (Amazon gave $50 back on the refurb).
Anyway, now that I have it and have been playing with it for a few weeks, I've realized that the current root methods (including Root Many Android) say they have rooted it, but I don't quite have all the SU access. Digging deeper, I've found that I have System Version 8.4.9.
I can get a partial root, but cannot mount the system to RW
Anyone out there working on the Root of Kindle Fire 8.4.9?
I would just downgrade it and flash a custom rom.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
I would just downgrade it and flash a custom rom.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Stunts,
I'd love to do that, but one of the issues with the current root is I can't use KFFirstAide to do much of anything. I would like to keep the KF as close to stock as I can, as I have kids and the FreeTime app is nice. I'm mostly looking to get the Google Play store up and working.
I've done a search but don't see anything on how to downgrade the KF from 8.4.9 without having root.
What am I missing?
You don't need root. When you initially power the device on it should briefly be detected as a jem device. Download then drivers in my signature and extract them somewhere. Now open the device manager and plug the kindle in while off, when you see the jem device, right click it and hit update drivers, and tell it to look where you extracted mine. If this is windows 8 you will have to disable driver signature enforcement first. If you can manage to get this step completed the rest is simple, it basically involves this: grab a utility like kindle fire first aid and shift + right click it and hit new command window here. With the kindle off and unplugged type
Code:
fastboot -I 0x1949 getvar product
once it says waiting for device plug the kindle in while it is off, it should enter fastboot, from there you can use kffa to downgrade it.
Sent from my Amazon Tate using Tapatalk
stunts513 said:
You don't need root. When you initially power the device on it should briefly be detected as a jem device. Download then drivers in my signature and extract them somewhere. Now open the device manager and plug the kindle in while off, when you see the jem device, right click it and hit update drivers, and tell it to look where you extracted mine. If this is windows 8 you will have to disable driver signature enforcement first. If you can manage to get this step completed the rest is simple, it basically involves this: grab a utility like kindle fire first aid and shift + right click it and hit new command window here. With the kindle off and unplugged type
Code:
fastboot -I 0x1949 getvar product
once it says waiting for device plug the kindle in while it is off, it should enter fastboot, from there you can use kffa to downgrade it.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Tried to downgrade. I can get to fastboot without any issues, but it looks like there are issues with KFFA (I'm using 4.1.87-beta). I get the following when trying to "Completely Restore the KFHD 8.9 8.1.4" (Option 7)
(snipped to the last one for space, all have the final "Unable to establish SSL Certificate)
**********************************************************************
*I Have Fetched The recovery.img - 1 More To Download................*
**********************************************************************
--2014-06-14 13:04:18-- y
<snip> (don't have 10 posts so can't post all the links)
HTTP request sent, awaiting response... 302 FOUND
Cookie coming from address attempted to set domain to dropbox.com
Cookie coming from address attempted to set domain to dropbox.com
Location: (removed as I don't have 10 posts)] [following]
--2014-06-14 13:04:18-- (removed as I don't have 10 posts)
Connecting to address... connected.
ERROR: cannot verify address's certificate, issued by `address High Assurance Server CA':
Unable to locally verify the issuer's authority.
To connect to address insecurely, use `--no-check-certificate'.
Unable to establish SSL connection.
****************************************************************************************
*I Have Fetched The system.img - I Am Ready To Flash The 3 Images......................*
****************************************************************************************
Press any key to continue . . .
target reported max download size of 1006632960 bytes
error: cannot load 'boot.img': No error
target reported max download size of 1006632960 bytes
error: cannot load 'recovery.img': No error
target reported max download size of 1006632960 bytes
error: cannot load 'system.img': No error
Would You Like To Wipe Data And Cache (y/n) ?
After this, I wipe data and cache and then didn't finish the registration (so I didn't get "pushed" an update, just in case)
Come back up and I'm still in 8.4.9
I've gone in to dropbox and pulled all the images to my computer. Is there a way to move these and get them properly mounted in adb? I'm a relative n00b but getting a bit more comfy in the adb environment and may be able to do it from there, with a bit of help?
Thanks!
Do not actually use KFFA use this method --> http://forum.xda-developers.com/showthread.php?t=2468988
You only need kffa for adb.exe and fastboot.exe ect.
PS. Be sure NOT to to connect to the Internet after until you have OTA blocked, and if you Like you can manually upgrade to what ever firmware you would like, I went back to v848
jmpiv4 said:
Do not actually use KFFA use this method --> http://forum.xda-developers.com/showthread.php?t=2468988
You only need kffa for adb.exe and fastboot.exe ect.
PS. Be sure NOT to to connect to the Internet after until you have OTA blocked, and if you Like you can manually upgrade to what ever firmware you would like, I went back to v848
Click to expand...
Click to collapse
Now I'm stuck in the Kindle Fire boot screen - orange. I got through all the flashes without an issue and unplugged on the final reboot per your instructions. I try to adb to it and there are no devices found.
Edit: Whoops. Was using my old shortcut command keys (arrows) and just changed what flashed to system - forgot to flash to the right places. Trying again!
Illinifan97 said:
Now I'm stuck in the Kindle Fire boot screen - orange. I got through all the flashes without an issue and unplugged on the final reboot per your instructions. I try to adb to it and there are no devices found.
Edit: Whoops. Was using my old shortcut command keys (arrows) and just changed what flashed to system - forgot to flash to the right places. Trying again!
Click to expand...
Click to collapse
Hi guys, thx for all tutorials in this site, but i can't root my Kindle Fire HD 8.9...this is the error
"/system/bin/sh su cannot execute permission denied "
KatanAlive said:
Hi guys, thx for all tutorials in this site, but i can't root my Kindle Fire HD 8.9...this is the error
"/system/bin/sh su cannot execute permission denied "
Click to expand...
Click to collapse
Is your Kindle up and running? I also have a Kindle Fire HD 8.9 and yesterday I downloaded latest update.bin file (8.4.9) from Amazon and updated my Kindle and later rooted it using the manual method described in http://forum.xda-developers.com/showthread.php?t=2069117 thread. It was total success. Just don't miss a single step from that method.
Actually I had my Kindle (ver 8.4.8) rooted before and Google Play installed with the same method but I was having some issues (not because of rooting but because I had been tinkering with the system apps) so decided to update to overcome those glitches. I installed RootKeeper from Google Play and told it to protect my root access during update process but this crap could not. After update I lost my root and now Google Play Store and related services stopped working, as I didn't have root access so couldn't manage to delete their apks from System apps. So I decided to root it again with the same method and I did it, after rooting it again I went to system apps and deleted old apks of Google Play and other related apks. Then I agin installed Google Play using the automatic method mentioned in above thread.
Sorry if this story is irrelevant but I just wanted to share my experience so any one searching for something could find a clue from it. One thing is confirmed here, KFFirstAid can easily install Google Play after 8.4.9 update and the above mentioned manual method can root it successfully. I am not sure about automatic method though.
you have been very usefull! Thx...but, i still can't root with any method
Can i ask you for some help (i've actually the 8.4.9 version) in private?
KatanAlive said:
Hi guys, thx for all tutorials in this site, but i can't root my Kindle Fire HD 8.9...this is the error
"/system/bin/sh su cannot execute permission denied "
Click to expand...
Click to collapse
KatanAlive said:
you have been very usefull! Thx...but, i still can't root with any method
Can i ask you for some help (i've actually the 8.4.9 version) in private?
Click to expand...
Click to collapse
Of course. I am not very knowledgable but I would try my best to share my experience.
akb1ajay said:
Of course. I am not very knowledgable but I would try my best to share my experience.
Click to expand...
Click to collapse
I write you a pm
I just tried the fastboot stuff and it will not enter fastboot. Do i need a fastboot cable?
Also i would like to remove all things kindle aka custom roms. So thats a non issue meaning if the only way to root a hd 8.9 with 8.4.9 rom version that was some how pushed on to my kindle via ota that i had turned off but got turned back on some how. Then thats fine and infact i want to remove amazons crap rom any how.
Nanaki-seto said:
I just tried the fastboot stuff and it will not enter fastboot. Do i need a fastboot cable?
Also i would like to remove all things kindle aka custom roms. So thats a non issue meaning if the only way to root a hd 8.9 with 8.4.9 rom version that was some how pushed on to my kindle via ota that i had turned off but got turned back on some how. Then thats fine and infact i want to remove amazons crap rom any how.
Click to expand...
Click to collapse
Read post 9 on previous page.
akb1ajay said:
Read post 9 on previous page.
Click to expand...
Click to collapse
Already tried this. It works partially only once it is fully done rebooting the kindle fire is running so slowly as to be unworkable for any thing. Also the lock swipe etc looks torn inhalf. At this point i have to use recorvery to get it to respond properly. I need to root or change rom out right (preferably) But the fast boot commands do nothing. Tried getting it to show up as gem device and use the other drivers that are suppose to let me enter fast boot by a fastboot command. It does not seem to work.
So after trying the method in post 9 again i need to recover to factory again. As it is running extremely slow
stunts513 said:
I would just downgrade it and flash a custom rom.
Sent from my Amazon Tate using Tapatalk
Click to expand...
Click to collapse
Stunts what is the best surefire way to downgrade? My previously rooted kindlefire hd 8.9 just got ota updated to 8.4.9. I had disabled ota i thought but it would seem it wasnt. Now i can not reroot it properly. I want to just go with a custom rom and be done with this mess. I do not have a fastboot cable. But it would seem there are ways around that such as the fastboot -i etc etc how ever i tried that and it did not work (including getting the drivers to the jem. I think i may be missing the chance to get the update drivers bit done intime (not sure here). At any rate help!!! heh
Again what i want to do
Downgrade to easiest rom ver to flash from to a custom rom using what ever meathod is the most effective minus fastboot cable. also recommendations on rom to use are very welcome.
akb1ajay said:
Is your Kindle up and running? I also have a Kindle Fire HD 8.9 and yesterday I downloaded latest update.bin file (8.4.9) from Amazon and updated my Kindle and later rooted it using the manual method described in http://forum.xda-developers.com/showthread.php?t=2069117 thread. It was total success. Just don't miss a single step from that method.
Actually I had my Kindle (ver 8.4.8) rooted before and Google Play installed with the same method but I was having some issues (not because of rooting but because I had been tinkering with the system apps) so decided to update to overcome those glitches. I installed RootKeeper from Google Play and told it to protect my root access during update process but this crap could not. After update I lost my root and now Google Play Store and related services stopped working, as I didn't have root access so couldn't manage to delete their apks from System apps. So I decided to root it again with the same method and I did it, after rooting it again I went to system apps and deleted old apks of Google Play and other related apks. Then I agin installed Google Play using the automatic method mentioned in above thread.
Sorry if this story is irrelevant but I just wanted to share my experience so any one searching for something could find a clue from it. One thing is confirmed here, KFFirstAid can easily install Google Play after 8.4.9 update and the above mentioned manual method can root it successfully. I am not sure about automatic method though.
Click to expand...
Click to collapse
This worked for getting root back, but didn't initially work for the Google apps. It looks like Amazon filled the file system /system leaving no room for the apps. Since I don't use Text To Speech, I removed /system/tts/ivona/vox_en_us_salli22i which is 100+MB, freeing plenty of space for Google apps. I saved a copy to /sdcard just in case. I recommend saving a copy of system.img first, since my first attempts at removing files deleted the apk, but didn't free the space and I had to do a restore once.
Full Manual Root - Kindle Fire HD 8.9 System Version 8.4.9 on Ubuntu Linux 14.04
Hi Guys,
If none of the usual methods work, here is a method for rooting Kindle Fire HD 8.9 with the new 8.4.9 system version. It was written for and tested on Linux, but should work on Windows as well.
Requires Linux and "DOS" scripting knowledge - particularly if anything goes wrong. If you are not familiar with linux shell, please do not try!
USE AT YOUR OWN RISK!!!
I was struggling a whole day with rooting my Kindle Fire HD 8.9 with the 8.4.9 stock rom. I use Linux (Ubuntu 14.04) and don't really have access to Windows. I've tried several methods, including several versions of the Bin4ry method, but the result was:
a) nothing happened at the end,
b) the system was hell slow, but did not get the root prompt/access.
Finally I've managed to root with a full manual - no script running - method. It was based on Bin4ry v18.5.1 root: the tools were uploaded to the kindle from the package, and the rooting steps were based on the RunMe.bat (manually entering step-by-step). It requires an installed adb on the linux machine (I have it from an Android SDK install)!
Sources:
http://forum.xda-developers.com/showthread.php?t=2277105 : I've started from here. I recommend to read this before starting the process.
http://forum.xda-developers.com/showthread.php?t=2069117 : "C-2) The next steps are used to Root the Kindle - Alternative Method (Manual Version)"
http://pocketnow.com/2012/10/10/root-without-unlocking : for understanding the exploit
Requirements:
1. Install adb on the linux machine.
2. Download Root MANY ANDROID 32-bit!(Dropbox): https://dl.dropbox.com/u/54456659/Win32.zip and extract.
Rooting:
The steps are based on manually entering the commands of the "1)Normal" method of the RunMe.bat:
1) In a terminal change to the directory where Win32.zip was extracted and enter:
Code:
adb push stuff/busybox /data/local/tmp/.
adb push stuff/su /data/local/tmp/.
adb push stuff/Superuser.apk /data/local/tmp/.
adb shell chmod 755 /data/local/tmp/busybox
2) Restore the fake “backup”. Note: _do not click restore on your Kindle device_! Just enter the command into the command prompt on your PC and press the enter key:
Code:
adb restore fakebackup.ab
3) Run the “exploit”:
Code:
adb shell “while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done”
(It will display a lot of "link failed File exists" lines)
4) Now that the “exploit” is running, click restore on your device.
5) Once it finishes, reboot your device. Note: Don’t use your kindle yet, this exploit reboots into emulator mode which will be laggy with a flickering screen (or no display at all). This is normal.
Code:
adb reboot
6) Once rebooted, open a shell:
Code:
adb shell
Check: Once you do step 6, your should have a root shell (your prompt should be #, not $). If it’s not #, start again from step 2.
7) Continue with the steps of the RunMe.bat - now entering the commands in the root shell:
Code:
/data/local/tmp/busybox mount -o remount,rw /system
/data/local/tmp/busybox mv /data/local/tmp/su /system/xbin/su
/data/local/tmp/busybox mv /data/local/tmp/Superuser.apk /system/app/Superuser.apk
/data/local/tmp/busybox cp /data/local/tmp/busybox /system/xbin/busybox
chown 0.0 /system/xbin/su
chmod 06755 /system/xbin/su
chmod 655 /system/app/Superuser.apk
chmod 755 /system/xbin/busybox
rm /data/local.prop
reboot
Done .
The Method described above didn't work for me.
Tried to do it step by step but the exploit part is not working, gives me a syntax error.
Then i used runme.bat and the exploit seems to work (slow reboot, scrambled kindle logo) but root isn't working properly afterwards.
It's kinda half-rooted now, with SuperSU working and displaying "granted root access..."-messages but if i try to install the play store i'm stuck.
ESexplorer is in root mode, mounted system R/W but when i try to move vending.apk to system/app it fails. No root access it seems
Opening SuperSU results in a failed update process....
Any kind of help is deeply appreciated...
Fixing that syntax error
Toastytwo said:
The Method described above didn't work for me.
Tried to do it step by step but the exploit part is not working, gives me a syntax error.
Then i used runme.bat and the exploit seems to work (slow reboot, scrambled kindle logo) but root isn't working properly afterwards.
It's kinda half-rooted now, with SuperSU working and displaying "granted root access..."-messages but if i try to install the play store i'm stuck.
ESexplorer is in root mode, mounted system R/W but when i try to move vending.apk to system/app it fails. No root access it seems
Opening SuperSU results in a failed update process....
Any kind of help is deeply appreciated...
Click to expand...
Click to collapse
This method worked for me! I also got a syntax error the first time arround but I fixed it by splitting this command (adb shell "while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done") into 2 separate command 1) adb shell, 2) while ! ln -s /data/local.prop /data/data/com.android.settings/a/file99; do :; done
After taking away the quotes it worked exactly as described!
Q&A for FireTV Full Bootloader Unlock
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for FireTV Full Bootloader Unlock. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Worked perfectly for me. Just wanted to say thanks!
Stuck at CHMOD step...
I've rooted my Fire TV, but when I try to unlock the bootloader I can't get past the step:
chmod 755 /data/local/tmp/aftv-full-unlock
I've tried on both OSX and Windows. It tell me that "No such file or directory". I know that the file is on the FireTv, bc when I issue a Pull command through adbFire, it gives a list of files in that directory on the Fire TV, and aftv-full-unlock is one of them.
I do have BusyBox installed and I granted permission in SuperSU
My version is 51.1.0.1_user_510055620
What am I missing here...?
RuffRhyno said:
I've rooted my Fire TV, but when I try to unlock the bootloader I can't get past the step:
chmod 755 /data/local/tmp/aftv-full-unlock
I've tried on both OSX and Windows. It tell me that "No such file or directory". I know that the file is on the FireTv, bc when I issue a Pull command through adbFire, it gives a list of files in that directory on the Fire TV, and aftv-full-unlock is one of them.
I do have BusyBox installed and I granted permission in SuperSU
My version is 51.1.0.1_user_510055620
What am I missing here...?
Click to expand...
Click to collapse
I don't know your level of experience so I'm going back to basics.
You mentioned that you tried in Windows and OSX.
Where exactly are you issuing the command?
Are you in the adb shell?
Did you type 'adb shell' after pushing the file to the FTV?
After full unlocking of boot loader and using an ssh server on the firetv, when I connect I am stuck with a root prompt. is there a way to step down the shell to manage package installations. for some reason "pm" command is not functioning correctly with root. I wish to use this for remote administration, I suppose, using the commands "start adbd" and "stop adbd" from within an ssh term session and then connecting to adb port might suffice but I would prefer to keep adb service stopped since it is not password protected. campuses are always full of prowlers and pranksters at all times. thanks
Hey Guys,
I have followed all steps and rebooted my FireTV using "adb reboot bootloader". The FireTV did reboot on command and has stopped on the white Amazon logo. I then unplugged the usb A to A cable and rebooted the device via hard reset. The FireTV did start up normally upon plugging the device back in the AC adapter.
My main concern is if I did in fact fully unlock the bootloader. After rebooting the FireTV there was no other information on the command prompt after running the command "adb reboot bootloader" so this is why I question it. I did enter command "adb shell" which then gives me "[email protected]".
Just a noob (I know you heard that before) looking for reassurance. Thank you in advance. You all do amazing work!
mozzer27 said:
Hey Guys,
I have followed all steps and rebooted my FireTV using "adb reboot bootloader". The FireTV did reboot on command and has stopped on the white Amazon logo. I then unplugged the usb A to A cable and rebooted the device via hard reset. The FireTV did start up normally upon plugging the device back in the AC adapter.
My main concern is if I did in fact fully unlock the bootloader. After rebooting the FireTV there was no other information on the command prompt after running the command "adb reboot bootloader" so this is why I question it. I did enter command "adb shell" which then gives me "[email protected]".
Just a noob (I know you heard that before) looking for reassurance. Thank you in advance. You all do amazing work!
Click to expand...
Click to collapse
That is normal and yes your root is fully unlocked if you get [email protected] when adb shell command is being sent.
Could this be used on the fire TV stick? version 54.1.0.2_user_102018720?
I still have a sealed german fire tv, which came with 51.1.3.0_user_513010720, for which no software root is known.
After having studied the unlock-code at the original Fire HDX thread and the modified tool for the Fire TV I wonder if the following might be possible.
From the hdx thread the first steps:
Code:
adb shell
cat /sys/block/mmcblk0/device/manfid
cat /sys/block/mmcblk0/device/serial
create a file unlock.img with following content:
0xmmssssssss
where mm=manfid and ss=serial
encrypt it with my vortox fork of signing tool at
https://github.com/dpeddi/Cuber
./cuber_unlockbl --sign ./unlock.img ./unlock.signed
This seems identical, what the routine at https:// github.com/androidrbox/aftv-full-unlock/blob/master/jni/aftv-full-unlock.c does.
rbox said:
For now, this requires root. Apparently, the IDs that are required for this can be gotten through fastboot, so if someone can figure that out, then brand new Fire TVs with 51.1.0.2 or older can be unlocked and have recovery installed before booting the first time.
Click to expand...
Click to collapse
For what exactly is root necessary? You can get the manfid and serial without root.
The fire-tv-tool then base64 encodes the signed result from cuber.
Code:
snprintf(idme_cmd, sizeof(idme_cmd), "idme unlock_code %s\n", bptr->data);
system(idme_cmd);
That should be also possible without uid 0.
Before I brick my fire tv. I wondered if someone could shed some light, if I might succeed trying
a) using cuber manually to sign the unlock data, base64-encode it and unlock my bootloader with idme unlock
b) using cuber manually to sign the unlock data and use ./fastboot flash unlock unlock.signed like it is possible with the Fire HDX-devices.
After that I could fastboot boot twrp and finally get root and downgrade. Possible or did I miss something?
The bootloader on your fire tv is not vulnerable to this exploit so it is not going to work. That is the reason "Fire TVs with 51.1.0.2 or older" is stated.
adb after full-unlock-bootloader
Can someone please help me? AFTER installing unlocked bootloader, when connected to fire tv via adb, I no longer get a pop up window for Superuser request: Adb on the fire tv. I need to know if that is normal and if ADB automatically gets SuperSu rights?
PS: Adb still works fine just no popup asking me for Superuser request or a pop up saying saying Adb has been granted permission. Thanks
Hey guys I was able to install latest recovery on 8520, my ? is, when I go to check unlock status I still get [email protected], I thought you couldnt install recovery if loader was locked, and am I safe to install boot menu
goodbye hppalm said:
Hey guys I was able to install latest recovery on 8520, my ? is, when I go to check unlock status I still get [email protected], I thought you couldnt install recovery if loader was locked, and am I safe to install boot menu
Click to expand...
Click to collapse
You most probably have a partial not a full unlock bootloader, that is why. CWM only needed a partial bootloader and so is boot menu however go ahead a fully unlock it, will help you later if for some reason box gets bricked.
Ty bula for comments, I think I screwed my firetv, by the thread it said if u have recovery working everything should be fine, I tried the boot menu, now stuck on white logo and no response, is it hard bricked now
Downgrading AFTV using a Mac
PLEASE HELP!
Has there been any update to AFTVnews posting titled "How to manually upgrade or downgrade the amazon fire tv". The instructions are old (June 2014)and don't seem to work. I've searched the internet and can't seem to find any way to downgrade AFTV before unlocking the bootloader.
Also, I can't find anything detailing how to use adbfire in order to downgrade AFTV.
In addition, I found information on how to downgrade AFTV firmware, but nothing for Mac users.
Your help would be greatly appreciated!!
i used the guides on aftvnews.com to unlock the bootloader on my original firetv. they worked great and I was using a mac
I'm running Pre-rooted 51.1.4.0_user514006420 and I'm fairly certain I need to update my Clockwork which is why i'm trying to follow the unlock guide online to fully unlock from following instructions.
However I hit a dead wall when just getting the process going. I've been stuck here long ago and I'm not revisiting this same issue once again.
When running the command.
Code:
[email protected]:/ adb push aftv-full-unlock /data/local/tmp/
My return is
Code:
adb push aftv-full-unlock /data/local/tmp/
cannot stat 'aftv-full-unlock' : No such file or directory
1|[email protected]:/ $
I have the file in the adb directory as instructed.
I really hope someone has some insight. I can't go beyond this version unless figured out to maintain root and when getting to this current firmware I'm on my FireTV doesn't ever sleep anymore.
Thanks!
May I suggest using this utility to automate the procedure?
http://forum.xda-developers.com/showthread.php?t=2736774
is this for aftv2 also???
i'm rooted at 5.2.1 r2 . twrp 3.0.0 recovery . disabled all updates app and blocked address in router setting.
if yes i should downgrade to 5.0.5.1?
thanx
htchd2fix said:
is this for aftv2 also???
i'm rooted at 5.2.1 r2 . twrp 3.0.0 recovery . disabled all updates app and blocked address in router setting.
if yes i should downgrade to 5.0.5.1?
thanx
Click to expand...
Click to collapse
No
If you are like me you are constantly fiddling and hacking with your phone. I’m also cheap so when I came across an Amazon Fire Phone from my local AT&T store for $150 I had to jump. After all I’m an Amazon Prime customer, so with the year of Prime it made the phone about $50. Anyways, I have been lurking on the Fire Phone XDA forum for a bit and have been using GGOW’s CM11 build since it came out. Every now and then, however, I want to go back to stock. After figuring it all out, I’ve kind of gotten it down to a pretty quick process and thought I would right a quick post on how to take your Fire Phone back to stock.
Ok so first off you have to prep your computer. You will need several things. First off you will need the Android Debug Bridge installed on your computer, also known as ADB. Instead of downloading the entire Android SDK to get ADB, you can follow the instructions on Lifehacker to install ADB pretty quickly. You will also need the OS files for your Fire Phone. You can download them from Amazon. For right now you need to make sure you download the correct file for whether your phone is unlocked or not. I believe the 4.6.6 update unifies the two, but for now it’s better to be safe.
Once you have installed ADB and have the .BIN file from Amazon, it is time to work. You need to make sure your phone is turned off and plugged in to your computer via USB. You will need to turn your phone on by holding down the power button and the volume up button and continue to hold them until you see the “Fire System Recovery” menu. You should see several options, you will need to select the “apply update from ADB” selection. Now with your phone plugged into your computer you need to go to a terminal/command prompt window. You will type
Code:
add sideload <filename>
where you replace <filename> with the path to your .BIN file. For instance on my computer (which runs OSX) I would type:
Code:
adb sideload ~/Downloads/update-kindle-32.4.6.5_user_465000520.bin
Now your update will begin and once it is done all you have to do is restart the phone.
Links:
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
http://www.amazon.com/gp/help/customer/display.html?nodeId=201607550
th3rmite said:
If you are like me you are constantly fiddling and hacking with your phone. I’m also cheap so when I came across an Amazon Fire Phone from my local AT&T store for $150 I had to jump. After all I’m an Amazon Prime customer, so with the year of Prime it made the phone about $50. Anyways, I have been lurking on the Fire Phone XDA forum for a bit and have been using GGOW’s CM11 build since it came out. Every now and then, however, I want to go back to stock. After figuring it all out, I’ve kind of gotten it down to a pretty quick process and thought I would right a quick post on how to take your Fire Phone back to stock.
Ok so first off you have to prep your computer. You will need several things. First off you will need the Android Debug Bridge installed on your computer, also known as ADB. Instead of downloading the entire Android SDK to get ADB, you can follow the instructions on Lifehacker to install ADB pretty quickly. You will also need the OS files for your Fire Phone. You can download them from Amazon. For right now you need to make sure you download the correct file for whether your phone is unlocked or not. I believe the 4.6.6 update unifies the two, but for now it’s better to be safe.
Once you have installed ADB and have the .BIN file from Amazon, it is time to work. You need to make sure your phone is turned off and plugged in to your computer via USB. You will need to turn your phone on by holding down the power button and the volume up button and continue to hold them until you see the “Fire System Recovery” menu. You should see several options, you will need to select the “apply update from ADB” selection. Now with your phone plugged into your computer you need to go to a terminal/command prompt window. You will type
Code:
add sideload <filename>
where you replace <filename> with the path to your .BIN file. For instance on my computer (which runs OSX) I would type:
Code:
adb sideload ~/Downloads/update-kindle-32.4.6.5_user_465000520.bin
Now your update will begin and once it is done all you have to do is restart the phone.
Links:
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
http://www.amazon.com/gp/help/customer/display.html?nodeId=201607550
Click to expand...
Click to collapse
When I boot to recovery and adb sideload there is no adb device when I type adb devices.
Windows 7 64bit.
Cool I found easy solution...I downloaded this program and runned it when phone was in sideload mode, it installed drivers and voila
http://adbdriver.com/downloads/
everything is still installed and camera still doesnt work
did I miss a step or something? lol. all my apps including nova launcher are still installed and my camera still doesn't work, but it looks like 4.6.6 is installed
ianedward said:
did I miss a step or something? lol. all my apps including nova launcher are still installed and my camera still doesn't work, but it looks like 4.6.6 is installed
Click to expand...
Click to collapse
Since it is official update it won't perform factory reset...
ianedward said:
did I miss a step or something? lol. all my apps including nova launcher are still installed and my camera still doesn't work, but it looks like 4.6.6 is installed
Click to expand...
Click to collapse
you need to wipe the device after flashing the new rom
C:\Program Files\Minimal ADB and Fastboot>adb sideload update-kindle-35.4.6.6_u
er_466000820.bin
loading: 'update-kindle-35.4.6.6_user_466000820.bin'
* cannot read 'update-kindle-35.4.6.6_user_466000820.bin' *
---------- Post added at 09:15 AM ---------- Previous post was at 08:25 AM ----------
C:\Program Files\Minimal ADB and Fastboot>adb sideload update-kindle-juniper-35.
4.6.3_user_463001420.bin
loading: 'update-kindle-juniper-35.4.6.3_user_463001420.bin'
* cannot read 'update-kindle-juniper-35.4.6.3_user_463001420.bin' *
C:\Program Files\Minimal ADB and Fastboot>adb sideload update.bin
loading: 'update.bin'
* cannot read 'update.bin' *
---------- Post added at 09:16 AM ---------- Previous post was at 09:15 AM ----------
i download many files but all BIN files fails to sideload
aamszia said:
C:\Program Files\Minimal ADB and Fastboot>adb sideload update-kindle-35.4.6.6_u
er_466000820.bin
loading: 'update-kindle-35.4.6.6_user_466000820.bin'
* cannot read 'update-kindle-35.4.6.6_user_466000820.bin' *
Click to expand...
Click to collapse
You should be able to manually update your phone to Fire OS 4.6.6 by following the steps at this link: Update Your Fire Phone Software.
jack9955 said:
You should be able to manually update your phone to Fire OS 4.6.6 by following the steps at this link: Update Your Fire Phone Software.
Click to expand...
Click to collapse
Fire phone stucked on recovery .. only option i have is by sideload . .. and sideload is not working for me ..
i have downloaded 5 firmwares .. but same error in all files ..
.....
aamszia said:
Fire phone stucked on recovery [...]
Click to expand...
Click to collapse
Please stick to asking questions for one problem in one thread at a time, thank you.
I replied in the other thread (bricked fire phone / sideloading by ADB), since it's more related to your questions.
aamszia said:
Fire phone stucked on recovery .. only option i have is by sideload . .. and sideload is not working for me ..
i have downloaded 5 firmwares .. but same error in all files ..
.....
Click to expand...
Click to collapse
If you mean you are stuck in Safestrap recovery, then follow @ggow post to flash Fire OS. The links you will need for the flashable images are here and here.
If you are not stuck in Safestrap recovery and your phone is still under warranty, you may want to contact Amazon for a replacement phone.
jack9955 said:
If you mean you are stuck in Safestrap recovery, then follow @ggow post to flash Fire OS. The links you will need for the flashable images are here and here.
If you are not stuck in Safestrap recovery and your phone is still under warranty, you may want to contact Amazon for a replacement phone.
Click to expand...
Click to collapse
i am stuck on Stock Recovery ...
Is there anyway to boot in to safestrap recovery and not the stock recovery. I have a back up on safestrap boot stuck on amazon screen and I can omly get im to stock recovery.
th3rmite said:
If you are like me you are constantly fiddling and hacking with your phone. I’m also cheap so when I came across an Amazon Fire Phone from my local AT&T store for $150 I had to jump. After all I’m an Amazon Prime customer, so with the year of Prime it made the phone about $50. Anyways, I have been lurking on the Fire Phone XDA forum for a bit and have been using GGOW’s CM11 build since it came out. Every now and then, however, I want to go back to stock. After figuring it all out, I’ve kind of gotten it down to a pretty quick process and thought I would right a quick post on how to take your Fire Phone back to stock.
Ok so first off you have to prep your computer. You will need several things. First off you will need the Android Debug Bridge installed on your computer, also known as ADB. Instead of downloading the entire Android SDK to get ADB, you can follow the instructions on Lifehacker to install ADB pretty quickly. You will also need the OS files for your Fire Phone. You can download them from Amazon. For right now you need to make sure you download the correct file for whether your phone is unlocked or not. I believe the 4.6.6 update unifies the two, but for now it’s better to be safe.
Once you have installed ADB and have the .BIN file from Amazon, it is time to work. You need to make sure your phone is turned off and plugged in to your computer via USB. You will need to turn your phone on by holding down the power button and the volume up button and continue to hold them until you see the “Fire System Recovery” menu. You should see several options, you will need to select the “apply update from ADB” selection. Now with your phone plugged into your computer you need to go to a terminal/command prompt window. You will type
Code:
add sideload <filename>
where you replace <filename> with the path to your .BIN file. For instance on my computer (which runs OSX) I would type:
Code:
adb sideload ~/Downloads/update-kindle-32.4.6.5_user_465000520.bin
Now your update will begin and once it is done all you have to do is restart the phone.
Links:
http://lifehacker.com/the-easiest-way-to-install-androids-adb-and-fastboot-to-1586992378
http://www.amazon.com/gp/help/customer/display.html?nodeId=201607550
Click to expand...
Click to collapse
Please help me when i type adb sideload "filname.bin" , It gives me an error cannot read "filname.bin" ??
Please tell me how could i fix this ??
Hussain_97 said:
Please help me when i type adb sideload "filname.bin" , It gives me an error cannot read "filname.bin" ??
Please tell me how could i fix this ??
Click to expand...
Click to collapse
Did you have any luck reviving your phone?
why not just factory reset using the official recovery? this seems like an awful lot of extra work :|
i am stuck on Stock Recovery elso with my phone .
i test sideload tool give me his msg on CMD windows after type add sideload commend
C:\tools>adb sideload c:/tools/rom.bin
opening 'c:/tools/rom.bin'...
connecting...
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
falling back to older sideload method...
terminate called after throwing an instance of 'std::bad_alloc'
what(): std::bad_alloc
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
@amr1406
try to find Android SDK Platform-tools v 25.0.3
I feel like a bonehead cuz I bricked my FireTV by getting ahead of myself. This FTV came shipped with 51.1.3.0 and I have always had updates blocked in my router. I purchased a SD-card adapter and was able to gain root by injecting su into /system/xbin, Installed busybox, and all that fun stuff. Everything was going along just fine, until i tried to install RBox's boot menu/Recovery without fully understanding everything. Following a guide, I ran the full bootloader unlock script and it seemed to complete fine and FTV would still boot normally with root access. What I did next is the following, trying to install recovery I download the bootmenu.img file, uploaded it to my sd card and issued the following commands:
mount -o remount,rw /system
mkdir /system/boot
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/system/boot/boot.img
mount -o remount,ro /system
dd if=/sdcard/bootmenu.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
exit
exit
adb rebootMy FTV restarted and has been stuck at the FireTV Logo every since. Not exactly sure where I went wrong. Did I have to downgrade before trying to install the boot menu? I did to the checksum test on the file before using it and it matched. Anyways, I tried factory reseting by holding the back/right remote control keys....no joy, tried the alt+prtsc+i keyboard procedure....nothing, tried a fastboot cable recovery.......got the drivers installed, firetv listed in devices using kindle usb driver, but although fastboot would connect and communicate to the FTV, it wouldn't respond to any fastboot commands.
I have the ability to gain direct access to the FTV's file system, but although my electronic skills are superb, my linux/android skills are quite lacking. When I disable the CPU and connect the flash to my Ubuntu 15 VMWare system via usb, I am able to mount up 6 linux partitions from the FTV. I explored around them, but don't want to go plowing through anything like a bull in a china shop until I have a direction to take from someone who actually knows what they are doing to get my beloved Firetv booting again. Any suggestions would be GREATLY appreciated. Thanks in advance.
Plug in the fire TV with a USB to USB to your PC. If the boot loader is fully unlocked you should be able to fastboot boot clockwork recovery and flash the rom that doesn't require boot menu.
{ParanoiA} said:
Plug in the fire TV with a USB to USB to your PC. If the boot loader is fully unlocked you should be able to fastboot boot clockwork recovery and flash the rom that doesn't require boot menu.
Click to expand...
Click to collapse
I mentioned in my OP that I have already tried this and although the fastboot drivers install correctly, the "fastboot devices" command returns nothing, and the "fastboot reboot recovery" command waits for about 10 seconds, then returns "no reply received by device". So this is a dead end and I guess the problem lies in the fact that my bootloader failed to unlock. I was also guessing that the solution would be to put the stock bootloader back onto the FireTV, but cannot figure out where it goes on the fire's 6 mounted partitions in linux using the soldered-in USB flash device. I can access the /system directory, but cannot locate the /dev/block/platform/msm_sdcc.1/by-name/boot folder where the bootmenu.img file was written to which caused the bricking. Any other ideas?
No I'm not that familiar with the partitions. @rbox would probably be the best one to answer this
Adaptel said:
I mentioned in my OP that I have already tried this and although the fastboot drivers install correctly, the "fastboot devices" command returns nothing, and the "fastboot reboot recovery" command waits for about 10 seconds, then returns "no reply received by device". So this is a dead end and I guess the problem lies in the fact that my bootloader failed to unlock. I was also guessing that the solution would be to put the stock bootloader back onto the FireTV, but cannot figure out where it goes on the fire's 6 mounted partitions in linux using the soldered-in USB flash device. I can access the /system directory, but cannot locate the /dev/block/platform/msm_sdcc.1/by-name/boot folder where the bootmenu.img file was written to which caused the bricking. Any other ideas?
Click to expand...
Click to collapse
boot is partition 10. You should be able to use gdisk on the mmc device to see the partition table with the partition labels.
rbox said:
boot is partition 10. You should be able to use gdisk on the mmc device to see the partition table with the partition labels.
Click to expand...
Click to collapse
Thank you for chiming in Rbox. I am in awe of your amazing work with FireTV and keep up the spectacular work!!!
Anyways, I wanted to attach a screenshot of my dead fireTV1's MMC partition layout, but becasue I am new here, the forum won't let me add a screenshot jpg. I used gparted because as I said before, I am a linux novice and couldn't get gdisk to show me what I wanted to. Partition 10 is labeled "boot", is 10MB in size, and shows up as having a file system type "Unknown". Should I dd the stock recovery file to this partition, or what do I need to do to undo these commands which bricked my device. (Which I am pretty sure due to the fact that I didn't get the bootloader unlocked correctly).
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/system/boot/boot.img
mount -o remount,ro /system
dd if=/sdcard/bootmenu.img of=/dev/block/platform/msm_sdcc.1/by-name/bootThank you so much for your help in advance!
Adaptel said:
Thank you for chiming in Rbox. I am in awe of your amazing work with FireTV and keep up the spectacular work!!!
Anyways, I wanted to attach a screenshot of my dead fireTV1's MMC partition layout, but becasue I am new here, the forum won't let me add a screenshot jpg. I used gparted because as I said before, I am a linux novice and couldn't get gdisk to show me what I wanted to. Partition 10 is labeled "boot", is 10MB in size, and shows up as having a file system type "Unknown". Should I dd the stock recovery file to this partition, or what do I need to do to undo these commands which bricked my device. (Which I am pretty sure due to the fact that I didn't get the bootloader unlocked correctly).
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/system/boot/boot.img
mount -o remount,ro /system
dd if=/sdcard/bootmenu.img of=/dev/block/platform/msm_sdcc.1/by-name/bootThank you so much for your help in advance!
Click to expand...
Click to collapse
You can just dd that boot.img in /system/boot back to the partition to undo what you did.
rbox said:
You can just dd that boot.img in /system/boot back to the partition to undo what you did.
Click to expand...
Click to collapse
That did the trick & my FTV is now booting and still has root and all my stuff just where I left it......you are the best!
Should I not even try to install boot menu/recovery? I thought i was on 51.1.3.0, but I just now checked and I am actually on 51.1.4.0. I ran the full bootloader unlock script right before I reflashed the recovery partition which bricked my fire. Is it because 51.1.40 is the version-of-no-return for installing recovery, should I have ran the partial bootloader unlock, or something else? Any advice? I am happy to have my Fire TV working again, but half the fun of this is learning and understanding what goes on inside and how it works. THANKS AGAIN!!!!!
Adaptel said:
That did the trick & my FTV is now booting and still has root and all my stuff just where I left it......you are the best!
Should I not even try to install boot menu/recovery? I thought i was on 51.1.3.0, but I just now checked and I am actually on 51.1.4.0. I ran the full bootloader unlock script right before I reflashed the recovery partition which bricked my fire. Is it because 51.1.40 is the version-of-no-return for installing recovery, should I have ran the partial bootloader unlock, or something else? Any advice? I am happy to have my Fire TV working again, but half the fun of this is learning and understanding what goes on inside and how it works. THANKS AGAIN!!!!!
Click to expand...
Click to collapse
You can't unlock that version. You should block updates and wait until I release TWRP and prerooted fireos5 roms.
hey rbox, quick question: once you release the prerooted fireos5 is it possible to dd recovey.img through hardware mmc to get the unlocked bootloader?
my firetv got bricked using supersu me and now i wonder what the best way is to bring it back alive..
Adaptel said:
That did the trick & my FTV is now booting and still has root and all my stuff just where I left it......you are the best!
Click to expand...
Click to collapse
Can you tell me the command wich give you finally the success ?
Another question by me is how to create a system.img from the bin files.
I know that there is folder in the bin-zip but how to create from them a system.img or how to create a valid stuck-recovery.img
Greetings by Idijt
I_did_it_just_tmrrow said:
Can you tell me the command wich give you finally the success ?
Click to expand...
Click to collapse
Certainly. The process I went through (using Ubuntu Linux 15 with Fire's eMMC chip connected via USB via hardware mod) is as follows (keep in mind I'm not a Linux genius but know enough to get by:
When eMMC is successfully connected, Ubuntu auto-mounted 6 partitions with partition names/ids that consisted of a long string of hex digits.
By looking around these ext4 partitions, I noticed that one of them was obviously the entire contents of the Fire's /system folder.
I navigated to /system/boot/ and saw that the boot.img file was in there. I right clicked on it, selected Properties to gain a full path of the files location and copied it
I installed and ran gparted partition editor to view the partition layout of the eMMC. There are a total of 20 partitions on fire's disk, (/dev/sdb1 through /dev/sdb20 on my system) but most of them aren't mounted because they use a non-linux standard file format).and as Rbox said. Partition 10 was 10.00MB in size, type=unknown, name=boot, and was located at /dev/sdb10 (on my system).
Now all I had to do was issue this command: sudo dd if=/<long string of hex digits described abouve>/system/boot/boot.img of=/dev/sdb10
Remove 4 wires soldered to Firetv, Solder CPU oscillator pads together, Reboot and CheerThe fire tv rebooted fine and everything was good....but I do have an update with even more good news. I felt emboldened having access to my MMC ao since my software was on version 51.1.40, I was able to then follow the guide (EXACTLY) at http://solderwiresandplastic.com/20...the-amazon-firetv-to-achieve-root-privileges/starting at "Step 2", and was able to successfully install the latest clockworkmod recovery, RBox's AWESOME boot menu, and install RBox's latest prerooted rom. This worked because I was on version 51.1.4.0 and the bootloader eFuse freeze occurred on 51.1.4.1 (so don't even think of trying the steps in this link if your box has 51.1.4.1 or higher on it. Hope this makes sense and helps in some way.
mrchrister said:
hey rbox, quick question: once you release the prerooted fireos5 is it possible to dd recovey.img through hardware mmc to get the unlocked bootloader?
my firetv got bricked using supersu me and now i wonder what the best way is to bring it back alive..
Click to expand...
Click to collapse
No. To unlock your bootloader you need an old version of the aboot partition. But if you're on the latest software, you will brick if you attempt to flash that old version.
thanks, good to know!
Sent from my iPhone using Tapatalk
Hello. I have a bricked fire tv because of supersu me. I've extracted a system.img from a working one via adb. My problem is, that i don't know how to install this on my bricked one with hardware mod (card reader). Any advice?
where did you find the 5.0.5 image i need it also , mines bricked also from super sume just waiting for EEMC chip to come in..
geist_patrick said:
Hello. I have a bricked fire tv because of supersu me. I've extracted a system.img from a working one via adb. My problem is, that i don't know how to install this on my bricked one with hardware mod (card reader). Any advice?
Click to expand...
Click to collapse
---------- Post added at 01:21 PM ---------- Previous post was at 01:18 PM ----------
[/COLOR]
geist_patrick said:
Hello. I have a bricked fire tv because of supersu me. I've extracted a system.img from a working one via adb. My problem is, that i don't know how to install this on my bricked one with hardware mod (card reader). Any advice?
Click to expand...
Click to collapse
think you could send me your img file thanks. as im on 5.0.5 firmware bricked also. thanks
Rootet system.img
https://drive.google.com/open?id=0B8P7DODeSgf8cmk5UUx4UUFXYkk
NOTICE: Several users have reported issues downgrading from v7.2.x, so it might require some additional experimentation to downgrade from that version.
-
Missing your screenshot or twitch streaming functionality? Hate the new launcher layout w/ its tiny one row of icons and its numerous rows of psychologically-aggressive suggestion imposition?
Well, now you can stop cursing at Nvidia, because they provided a way (albiet, a highly technical and mostly-undocumented way), to load any version of their OS that you choose.
I've seen others wanting to downgrade (including myself), so I've collected the relevant steps which I used to successfully revert to an earlier version. This guide assumes a bit of technical working knowledge, so I apologize if you are one of the 'normal' people that Nvidia has bulldozed over...
All the usual "don't blame me for bricked devices" caveats apply.... please be careful, know what each step does! research each step!
Best of luck...
0 - prereqs
make sure your PC & nvidia shield are both plugged into a UPS, b/c a power failure during a flashing operation is not very pleasant.
make sure you have (or do get) the adb & fastboot binaries ("commands") for your computer
make sure that you get all your userdata off the device, because it will be erased by this process
1 - using a web browser
register for an nvidia developer account (which you will have an opportunity to do if you attempt the next step)
download the 6.3 'developer os' rom for your particular model
https: //developer.nvidia.com/shield-developer-os-images (sorry, noob filter won't allow the real/clickable url)
NB: The 6.3 developer rom for the 2017 console is missing the userdata.img, there are currently no reports (on this thread) if a different userimage (pre-6.3 or for the 2015 version) works on the 2017 console (testers welcome!).
NB: if the cost of being identified as a developer offends you (i.e. yielding a name, company, email, etc), then you can probably dig up a link to the roms in the comments or elsewhere on the xda forums.
2 - on the device
enable developer mode by clicking the 'build' entry in settings->info
enable usb debugging in settings->developer-options
plug it into your computer using the usb port furthest from the hdmi port
3 - in a terminal
unzip the downloaded rom & cd into the resulting directory
edit the 'flash-all.sh' script to add the following line just before the final reboot:
fastboot flash userdata userdata.img
#(this will add even more wall-time to the flashing process, but will clobber the already-erased newer 7.0 user partition data with the old)
adb reboot bootloader
fastboot oem unlock && ./flash-all.sh
NB: Now confirm your willingness to lose all your data. On the 2015 'pro' version of the console, this is accomplished by pressing (or holding) the nvidia logo 'button'... AND WILL TAKE NEARLY TWO HOURS. Others use the x/y/a/b buttons on the game controller connected to the usb port nearest to the hdmi port.
[... time passes ...]
NB: the 7.0 to 6.3 was a clean backstep for me, but if you are going between other versions, I can see that this script might stall in the middle if the device does not come back up with adb services available... in which case you will need to enter fastboot manually using a hardware method.
4 - Break TegraOTA
You have now flushed the correct version onto your device, but we can't complete the setup process... if you were to try, the final step would immediately and automatically start downloading & applying the latest (7.0) experience update! Therefore, we must neuter the updater itself.
Still in the terminal:
adb root
adb remount
adb shell
# now these commands are run in the adb shell (technically on the phone through the PC terminal)
# the first path was the right one for me, but I'm putting here all the paths known to me in case you are using a different version
rm -rf /system/priv-app/TegraOTA
rm -rf /system/app/TegraOTA
rm -rf /system/app/TegraOTA.apk
sync
reboot
5 - you should now be able to setup and pain-stakingly reconfigure your nvidia shield to the way it was before you blindly trusted an OEM update without doing extensive research beforehand.
PS: if you fear that netflix or amazon-video will at some point stop working because of this process, you might wish to "fastboot oem lock" the device (knowing that an unlock will erase your user-data, but having the developer rom means you can always get root access via adb).
I hope you find this useful.
Thanks! I will be trying this tonight! I miss 6.3 and PLEX is BROKEN in 7.0!
Any idea if this can be done without needing a controller? My buddy has a shield TV but bought it used without a controller.
rossbeck said:
Thanks! I will be trying this tonight! I miss 6.3 and PLEX is BROKEN in 7.0!
Any idea if this can be done without needing a controller? My buddy has a shield TV but bought it used without a controller.
Click to expand...
Click to collapse
Plex is NOT broken in 7.0 i use it everyday.
Builtfordtough1 said:
Plex is NOT broken in 7.0 i use it everyday.
Click to expand...
Click to collapse
I use it every day too... and since Plex v6.13, files fail to play after 3 seconds unless you run them a 2nd time.
It's a known issue that everyone is having due an acknowledged bug in exoplayer2 with certain containers like mkv. Since 7.0/oreo has plex v6.14 baked in as a system app, it's impossible to downgrade to v6.12 to get rid of the issue until Plex fixes it... and they've known about it for 2 months now. Since quantity has been their focus over quality lately, I'm not holding my breath for a fix.
The solution is to downgrade to 6.3, manually install plex v6.12, and turn off app updates.... so that's my plan.
rossbeck said:
Any idea if this can be done without needing a controller? My buddy has a shield TV but bought it used without a controller.
Click to expand...
Click to collapse
I think it depends on the model. AFAIK, the newer 2017 ones need a controller (or possibly a USB keyboard) to confirm the userdata partition wipe.
Osndok said:
I think it depends on the model. AFAIK, the newer 2017 ones need a controller (or possibly a USB keyboard) to confirm the userdata partition wipe.
Click to expand...
Click to collapse
Ahhh, good call. I'll have him try a usb keyboard.
doesnt work for me... i have a nvidia shield tv 2015. i tried with flash-all.bat
and im stuck after reboot. is there any other way?
crazyscow said:
doesnt work for me... i have a nvidia shield tv 2015. i tried with flash-all.bat
and im stuck after reboot. is there any other way?
Click to expand...
Click to collapse
What command did the script stop at? and how 'stuck' are you (i.e. can you get to fastboot?).
I imagine that if you started with the wrong rom, it would likely fail to boot.
thanks for the fast reply, i just manually installed it without the bat file
I went manually into the fastboot mode by unplugging the power pressing the power button and plugging it back in until fastboot mode comes.
then i typed
fastboot flash staging blob
fastboot flash boot boot.img
wait until the sound on windows comes then - adb devices
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot
and then it booted
crazyscow said:
thanks for the fast reply, i just manually installed it without the bat file
I went manually into the fastboot mode by unplugging the power pressing the power button and plugging it back in until fastboot mode comes.
then i typed
fastboot flash staging blob
fastboot flash boot boot.img
wait until the sound on windows comes then - adb devices
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot
and then it booted
Click to expand...
Click to collapse
How did you get past the forced update? I was able to flash 6.3, but it forces the update during setup and I don't have ADB access yet because usb debugging isn't turned on. Can't disable the OTA updates without it!
Basically I've successfully flashed 6.3 and am sitting at a working fastboot prompt. Not sure what to do from here.
rossbeck said:
How did you get past the forced update? I was able to flash 6.3, but it forces the update during setup and I don't have ADB access yet because usb debugging isn't turned on. Can't disable the OTA updates without it!
Basically I've successfully flashed 6.3 and am sitting at a working fastboot prompt. Not sure what to do from here.
Click to expand...
Click to collapse
Disabling the OTA update is step four, if ADB does not work, I would guess that you forgot to flash userdata.img in the previous step(s).
Osndok said:
Disabling the OTA update is step four, if ADB does not work, I would guess that you forgot to flash userdata.img in the previous step(s).
Click to expand...
Click to collapse
So you did what to get userdata.img? Created it in TWRP or something? It's not included with the recovery images... and this basically bypasses the OOBE/setup stuff?
Thanks man
rossbeck said:
you did what to get userdata.img? ... It's not included with the recovery images... and this basically bypasses the OOBE/setup stuff?
Click to expand...
Click to collapse
userdata.img is inside the ZIP from the nvidia developer website, as can be seen here:
Code:
$ jar tf nv-recovery-image-shield-atv-pro-6.3.0-dev_rooted.zip | grep user
nv-recovery-image-shield-atv-pro-6.3.0-dev_rooted/userdata.img
rossbeck said:
[the userdata.img] basically bypasses the OOBE/setup stuff?
Click to expand...
Click to collapse
No... not really. The userdata.img from the developer pack both (1) matches the 6.3 version (doesn't have any of the newer, potentially incompatible entries), and (2) has developer-mode & adb enabled by default.
So in addition to it probably just working better, flashing the userdata will let you get adb access, and thus break the OTA, and thus complete the setup w/o the update.
I thought it would boot up, but im still stuck on the android loading screen!
Ill try to reflash the rom again tonight.
update:
I got it to work now, without update having to update to 7.0.2
Code:
adb reboot bootloader
fastboot flash staging blob
fastboot flash boot boot.img
fastboot reboot
//waiting for nvidia logo and the Windows PC to make the connection noise
//otherwise you can check by typing
adb devices
// if it shows something then continue
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot flash userdata userdata.img
fastboot reboot
once it booted it up, i went thru the procedure of setting it up with my network and google account, then the window pop-up "downloading version 7.0.2" then i followed the guide in the first post
Code:
adb root
adb remount
adb shell
# now these commands are run in the adb shell (technically on the phone through the PC terminal)
# the first path was the right one for me, but I'm putting here all the paths known to me in case you are using a different version
rm -rf /system/priv-app/TegraOTA
rm -rf /system/app/TegraOTA
rm -rf /system/app/TegraOTA.apk
sync
reboot
after that it booted up into android 7 with not OTA update notification.
thank you!
hello, thanks for the contribution, but when decompressing the image of developer 6.3 of shield tv 2017 I do not know where to get the file userdata.img, could you give me where to get it?
lohengrim93 said:
when decompressing the image of developer 6.3 of shield tv 2017 I do not know where to get the file userdata.img, could you give me where to get it?
Click to expand...
Click to collapse
As I said in #13, I found the userdata.img inside the archive from nvidia (the 2015 "pro" version to be exact), and I don't know why it is missing from (at least) the 6.3 archive for the 2017 device.
If you are feeling adventurous, you can try downloading either of the 2015 zips, and use its userdata.img... maybe the 16gb one?
I would be eager to know if that works for you, since I'm unsure if the userdata.img can be mixed between different versions of the console...
JUST BE VARY CAREFUL to not mix up your directories and start flashing the wrong blobs & boots... that would be a recipe for a brickin', methinks.
crazyscow said:
I got it to work now, without ... having to update to 7.0.2
... i followed the guide in the first post...
after that it booted up into android 7 [without] OTA update notification.
thank you!
Click to expand...
Click to collapse
I'm quite pleased to hear that it worked for you... (my first success report!).
Adb root
When I attempt to run the adb root command it just errors on me at the end, do I need to have the shield booted into setup for it to work?
Insatiablejimmy said:
When I attempt to run the adb root command it just errors on me at the end, do I need to have the shield booted into setup for it to work?
Click to expand...
Click to collapse
You forgot to include (or even describe) the actual error message, so I can only guess as to what is wrong.
However, since "adb root" is the linchpin of the developer rom, I would assume that you did not flash a developer rom (or as indicated above concerning the 2017 model) are missing the "userdata.img", which could also cause this behavior.