Hi,
Just flashed the latest firmware on a wiped 1st gen box.
the boot menu is there, twrp recovery loads too, root checker shows that device is rooted, but judging by the "[email protected]:/ $" in the command line the bootloader is not fully unlocked and Im pretty sure the unlocking procedure went smooth when I was doing it.
so when I try to perform any commands via shell it fails:
pm disable com.amazon.device.software.ota
Error: java.lang.SecurityException: Permission Denial: attempt to change compone
nt state from pid=11712, uid=2000, package uid=32011
push C:\Users\****\Downloads\aftv-full-unlock /data/local/tmp/ </system/bin/sh: adb: not found
Not sure what I'm doing wrong or missing here, any ideas anyone?
P.S. not sure how that "Helo" appeared in the beggining of the topic title
seems like there some SU related issue.
is that how its supposed to look in the application manager?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
mrwp said:
Hi,
Just flashed the latest firmware on a wiped 1st gen box.
the boot menu is there, twrp recovery loads too, root checker shows that device is rooted, but judging by the "[email protected]:/ $" in the command line the bootloader is not fully unlocked and Im pretty sure the unlocking procedure went smooth when I was doing it.
so when I try to perform any commands via shell it fails:
pm disable com.amazon.device.software.ota
Error: java.lang.SecurityException: Permission Denial: attempt to change compone
nt state from pid=11712, uid=2000, package uid=32011
push C:\Users\****\Downloads\aftv-full-unlock /data/local/tmp/ </system/bin/sh: adb: not found
Not sure what I'm doing wrong or missing here, any ideas anyone?
P.S. not sure how that "Helo" appeared in the beggining of the topic title
Click to expand...
Click to collapse
Seems like you did but did you trype "su" in the terminal? Also if its 1st time using it, a popup will come up on the TV asking to grant su permissions for on adb shell
mrwp said:
seems like there some SU related issue.
is that how its supposed to look in the application manager?
Click to expand...
Click to collapse
Thats how it looks on everyone's. With rbox roms you cant open supersu app.
KLit75 said:
Seems like you did but did you trype "su" in the terminal? Also if its 1st time using it, a popup will come up on the TV asking to grant su permissions for on adb shell
Thats how it looks on everyone's. With rbox roms you cant open supersu app.
Click to expand...
Click to collapse
yeah I did type 'su' quiet a few times untill su popup appeared and Im not sure what was wrong untill then, but it worked on the next day itself kinda. at least I dont recall doing anythng specific for it to work.
still not able to start the full unlock procedure tho, gives me the same error even with root prompt
screenshot
mrwp said:
screenshot
Click to expand...
Click to collapse
adb push is run from your machine, not the firetv shell. I think from looking at this thread, you might want to really read through a guide a few more times and make sure that every single step is followed. I'm not trying to be rude, but I don't want you bricking your device.
ImCoKeMaN said:
adb push is run from your machine, not the firetv shell. I think from looking at this thread, you might want to really read through a guide a few more times and make sure that every single step is followed. I'm not trying to be rude, but I don't want you bricking your device.
Click to expand...
Click to collapse
I am running adb push from my machine, from adb shell
mrwp said:
I am running adb push from my machine, from adb shell
Click to expand...
Click to collapse
If you don't understand the difference between your pc's command prompt and firetv shell you aren't ready. the command adb push can't be run from adb shell as you are seeing.
I was using "ADB Shell" button on an adbLink application for windows to call up the shell, thought it was the same as using command prompt. (screenshot)
Anyway, tried command prompt too and it seems I'll have to either factory-reset or reinstall SU. Because when I do the procedure through the windows command prompt (installed adb after this discussion) it errors too, but later when I type 'su' (screenshot)
found this in a discussion: screen
UPD: after reinstalling the rom (without factory reset) 'su' worked, but then I still got the "error: only position independent executables (PIE) are supported." error...
mrwp said:
I was using "ADB Shell" button on an adbLink application for windows to call up the shell, thought it was the same as using command prompt. (screenshot)
Anyway, tried command prompt too and it seems I'll have to either factory-reset or reinstall SU. Because when I do the procedure through the windows command prompt (installed adb after this discussion) it errors too, but later when I type 'su' (screenshot)
found this in a discussion: screen
UPD: after reinstalling the rom (without factory reset) 'su' worked, but then I still got the "error: only position independent executables (PIE) are supported." error...
Click to expand...
Click to collapse
The full unlock is only for OS3. If you are on OS5 and you haven't already fully unlocked, you cannot do it.
rbox said:
The full unlock is only for OS3. If you are on OS5 and you haven't already fully unlocked, you cannot do it.
Click to expand...
Click to collapse
alright, thanks!
decided to leave it for some other time, when theres more use for it. dont feel like downgrading and starting it all over again.
mrwp said:
alright, thanks!
decided to leave it for some other time, when theres more use for it. dont feel like downgrading and starting it all over again.
Click to expand...
Click to collapse
Well you can't downgrade... so it doesn't matter.
ok, but I was following the guide at: http://www.aftvnews.com/how-to-fully-unlock-the-amazon-fire-tv-bootloader/
and it says:
Important
If your Fire TV software is…
Any of rbox’s Pre-Rooted Custom ROMs, then you DO NOT need to downgrade. You may proceed with this guide and unlock your bootloader.
and I'm on your latest rom (bueller-5.2.1.0-rooted_r1)
I started with a rooted 51.1.1.0_user_511069920 and went through all necessary guides to get the latest rooted rom on the box (bueller-5.2.1.0-rooted_r1)
so, Im a bit confused now
mrwp said:
ok, but I was following the guide at: http://www.aftvnews.com/how-to-fully-unlock-the-amazon-fire-tv-bootloader/
and it says:
Important
If your Fire TV software is…
Any of rbox’s Pre-Rooted Custom ROMs, then you DO NOT need to downgrade. You may proceed with this guide and unlock your bootloader.
and I'm on your latest rom (bueller-5.2.1.0-rooted_r1)
I started with a rooted 51.1.1.0_user_511069920 and went through all necessary guides to get the latest rooted rom on the box (bueller-5.2.1.0-rooted_r1)
so, Im a bit confused now
Click to expand...
Click to collapse
If you were on 51.1.1.0, then you already unlocked...?
rbox said:
If you were on 51.1.1.0, then you already unlocked...?
Click to expand...
Click to collapse
Actually I double checked. I think what got me confused is the prefix "shell" when I connect to the box via adb. because guide at http://www.aftvnews.com/how-to-check-if-your-fire-tvs-bootloader-is-unlocked says if you have "shell" prefix then its locked, if you get "root" you are unlocked. But I thought if it starts showing 'root' only after performing 'su' then it means its locked or partly locked, if it shows 'root' right after I connected to the box via adb without performing any other command then it is unlocked.
so now I typed 'su' and then cat /proc/cmdline and I indeed got the "androidboot.unlocked_kernel=true" statement, that means it's indeed fully unlocked?
Sorry, I just haven't grasped on this whole hacking android thing but seems I managed it afterall
mrwp said:
Actually I double checked. I think what got me confused is the prefix "shell" when I connect to the box via adb. because guide at http://www.aftvnews.com/how-to-check-if-your-fire-tvs-bootloader-is-unlocked says if you have "shell" prefix then its locked, if you get "root" you are unlocked. But I thought if it starts showing 'root' only after performing 'su' then it means its locked or partly locked, if it shows 'root' right after I connected to the box via adb without performing any other command then it is unlocked.
so now I typed 'su' and then cat /proc/cmdline and I indeed got the "androidboot.unlocked_kernel=true" statement, that means it's indeed fully unlocked?
Sorry, I just haven't grasped on this whole hacking android thing but seems I managed it afterall
Click to expand...
Click to collapse
Yes. If unlocked is in cmdline then it is unlocked. OS5 stopped doing the auto root thing.
rbox said:
Yes. If unlocked is in cmdline then it is unlocked. OS5 stopped doing the auto root thing.
Click to expand...
Click to collapse
cool, then I'm all set. still lots of things to grasp though.
thanks a lot!
Did you find a fix?
Hey, just curious to see if you found a fix for this. I had a similar issue. I upgraded my friends AFTV to os5 from 3. Everything was unlocked and rooted but something went wrong when installing Xposed. Basically I didn't realize I had a boot issue at first and it didn't take. Now the AFTV skips TWRP and just goes into the normal AFTV OS. The OS still seems rooted just doesn't bring up the recovery. But I also cannot ADB into it either. Keep getting permissions errors.
Any idea to fix this? Or any idea on how to even connect into it again?
Also here is what I posted on AFTVnews when it happened:
"Wat happens if you sideload xposed before installing the installer it in TWRP? Because I did not read (and did just that (Step 3 before step 2) though I did not launch it) and side loaded it. Now I my AFTV 1 skips TWRP and just goes into the Amazon Home Screen. I also keep getting permission errors in ADB. Also says [email protected], instead of [email protected] Is there anyway to reverse this? It had TWRP running and newest RBOX FireOS5. I’m not bricked, just lost boot to SPMC and recovery access."
AND
"Correction, it’s “127|[email protected]”"
Related
First of all, unforgiven512 deserves most of the credit for coming up with the initial tutorial for perm root and s=off for the new HTC devices. Also, thanks to adwinp for the instructions on hexeditting the kernel module to make it work with the MT4G.
This was a collaborative #g2root effort, primarily involving scotty2, tmzt, IntuitiveNipple but also many others!
Ok, so the usual disclaimers go here:
I am not responsible for your bricked phone or the ignorance that may or may not have caused it based on the fact that you CHOSE to follow these steps. Read through the forums and LEARN before you attempt to flash any device. You have been warned.
This method only works for those devices who have already received their OTA update!!!
Now that that is out of the way here we go:
First make sure you have visionary installed!
Root.rar (all files plus a script to make things a little easier. )
http://www.mediafire.com/?flit79p2y069bb3
md5sum: 46361b0cc8652d88688c0ab66d44950b
1. Download the root.rar file and unzip it to /sdcard on your device.
2. Run VISIONary to gain temp root.
Now I am going to run two different sets of instructions (you'll understand why in a minute):
Terminal Emulator Method
3a. Start terminal emulator up on your device.(I prefer this method b/c you can see the output.)
a. type "su" + enter to gain root privileges.
b. Type "cd /sdcard/root" + enter.
c. Type "sh root.sh" + enter.
d. Follow the on screen prompts.
File Explorer Method
3b. Start up root explorer, sufbs, or some other type of file browser with root privileges.
a. Navigate to /sdcard/root on your device.
b. Click on root.sh and allow it to run. Some file browsers ask you if you want to or not.
c. Now wait about 18 to 20 seconds and restart your device into the bootloader to check if S=off is displayed.
4. Start the device back up.
5. Run visionary again and reboot again. This will make root stick.
You can now uninstall visionary and enjoy permaroot.
Alternative Root Process
First, uninstall visionary and superuser and restart your device to wipe out temp root.
Second, download MT4G Modperm.zip and unzip its contents to your sdk tools directory.
MT4G Modperm.zip: http://www.mediafire.com/?eaw0q0zjc7rrrwh
MD5Sum: 3ea4a7a6ddee711d12f7350ce60fae33
Then:
Windows Users:
1a. Using Explorer navigate to the root of your sdk. Hold shift and right mouse click on the tools folder. Select "Open command window here".
2a. Type "adbbat" + enter. Wait till the batch file finishes.
Linux Users:
1b. Using file browser of your choice (or terminal) navigate to the tools folder of your sdk and double click on adbbat.sh (type sh adbbat.sh if you are using terminal). Credit for adbbat.sh goes to slhpss.
2. Disconnect your phone from the PC.
3. Open terminal emulator on the phone and type "/data/local/rage" + enter. Wait for "Forked XXXXXXXX children" to appear and then close the terminal.
4. Start terminal back up. It should force close.
5. Start terminal back up, again. This time it should stay open and you should have a "#" prompt instead of a "$" prompt. Then type "/data/local/temp.sh.
6. When the script finishes run /data/local/rage again and sit tight. The phone should start acting weird and do a soft reboot. Then right after everything loads it should do a hard reboot. After the hard reboot reboot and check S.(If it doesn't do the two reboots just reboot into hboot yourself after rage finishes with the "forked xxxxxxxx children" message.
7. Enjoy root!
If you still have problems getting su to work after this uninstall visionary, shutdown, pull battery, and restart. Should work after that. Props to PolishDude for figuring that one out.
If you have tried EVERYTHING and still cannot get it to work for through the process and wait 30 minutes to an hour. The driver might have a cache delay write and you may need to give it some time to allow the sync command to work. This has worked for one other person (mfouco). BTW, this was figured out by coachmai. Props man!
If su doesn't stick, flash again! You can't overroot it!
Process for turning S back on
Download this file and unzip it to /sdcard on your device.
unroot.rar
http://www.mediafire.com/?12oi5elu7v2y8og
md5sum: aad4e64126cf8d92d7e8b5abb48fdadd
Terminal Emulator Method
1. Open up terminal editor on your device.(I prefer this method b/c you can see the output.)
a. Type "su" + enter to gain root privileges.
b. Type "cd /sdcard/unroot" + enter.
c. Type "sh unroot.sh" + enter.
d. Follow the onscreen prompts.
File Explorer Method
2. Open root explorer, sufbs, or some other file browser with root access.
a. Navigate to /sdcard/unroot.
b. Click on unroot.sh and allow it to run. Some file browsers ask permission before they execute scripts.
c. Wait 18 to 20 seconds and reboot your phone into the bootloader to check if S=on.
You now have S=ON again.
Since we opened up the nand to writes you should still retain persistent root privileges.
Hope this makes it all easier for you.
Cheers --grankin01
For everyone that is have trouble writing to the protected areas of the system after following the rooting procedures.
Reboot into Clockwork recovery and choose the mounts and storage option. From there choose mount system (or whichever protected directory you want access to) and click the trackpad. When unmount system shows you have rw access to the /system directory and all of its subs.
Great I just saw this on PaulObrians twitter so this is great news.
Mackster248 Macky Evangelista
@PaulOBrien will your visionary app tomorrow be able to root the mytouch 4g as well? Since it roots the desire hd.
Pual's answer:
PaulOBrien Paul O'Brien
@
@Mackster248 Possibly...
Question, Did you recompile the kernel for the MT4G yourself? A big thanks to everyone. We all need to dig in out pockets to these developers and not forget them.
No, I really didn't do much of anything but legwork on this, lol.
I had to hexedit the wpx.ko module to add our kernel version (instructions and hboot file in the desire hd permaroot thread thanks to adwinp). I then uploaded both and pasted the links here.
Good job man, can you post an image of the bootloader with s-off?
Testing now. I don't have my USB cable with me at the moment so I couldn't execute the ADB commands, however I moved the files to their relevant positions via Root Explorer app.
EDIT: I has a ROOT. Glacier PVT ENG S-OFF ftw!
EDIT2:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry for the bad quality, but there ya go!
EDIT3: For those who were wondering, I did everything I could through Terminal Emulator with Fast Boot off and not through ADB. Once the hboot_dhd.nb0 file had completed, I believe I sync'd, then I attempted to run VISIONary which said the phone was already rooted. Went ahead and hit "Restart," then ran VISIONary one more time when it was done and restarted again to get it to stick.
unremarked said:
Testing now. I don't have my USB cable with me at the moment so I couldn't execute the ADB commands, however I moved the files to their relevant positions via Root Explorer app.
Click to expand...
Click to collapse
Please Let us know how it goes. And also does this require the OTA update to 2.2.1?
grankin01 said:
No, I really didn't do much of anything but legwork on this, lol.
I had to hexedit the wpx.ko module to add our kernel version (instructions and hboot file in the desire hd permaroot thread thanks to adwinp). I then uploaded both and pasted the links here.
Click to expand...
Click to collapse
There were actually three files on the G2 thread. Two were slightly different versions - pre-OTA and post OTA update. Which is the one here - pre or post OTA?
I have the OTA update, and am hoping I don't have to roll back to do this.
In any case - great job for getting it up for the MT4G. Just want to be sure what i am working with.
Getting my MyTouch in a couple of hours. Can't wait for the new challenge.
-kmobs
Bump for great success! I'll try to post a picture of my S-OFF.
Mmarzex said:
Please Let us know how it goes. And also does this require the OTA update to 2.2.1?
Click to expand...
Click to collapse
I'm going to assume so since I was on 2.2.1 and it worked.
Double post, all the way! What does this meeeeaaan?
Guys might be a stupid question but how do you get into the hboot on mytouch 4g. I thought it was the power button and camera but that doesn't seem to work.
Mmarzex said:
Guys might be a stupid question but how do you get into the hboot on mytouch 4g. I thought it was the power button and camera but that doesn't seem to work.
Click to expand...
Click to collapse
Turn off "Fast Boot" under Applications then power on holding Power + Vol Down
unremarked said:
Bump for great success! I'll try to post a picture of my S-OFF.
Click to expand...
Click to collapse
This is for after the OTA. I figured everyone had already gotten it and didn't worry with the two versions. If that becomes a problem I will edit the file again and post a pre-OTA file on here.
I am also trying to post a pic. I wasn't ignoring everyone its just that my phone is my camera and I was trying to track an old phone or something down. LOL
persiansown said:
Getting my MyTouch in a couple of hours. Can't wait for the new challenge.
-kmobs
Click to expand...
Click to collapse
I'm loving it bro. Coming from n1 too
grankin01 said:
This is for after the OTA. I figured everyone had already gotten it and didn't worry with the two versions. If that becomes a problem I will edit the file again and post a pre-OTA file on here.
I am also trying to post a pic. I wasn't ignoring everyone its just that my phone is my camera and I was trying to track an old phone or something down. LOL
Click to expand...
Click to collapse
Likewise! LOL Trying to find a program to turn my netbook's camera on real quick.
wow guys that was fast!
OP has been updated with a pic of s=off.
Cheers guys.
Link Down
hboot_dhd.nb0 link not working
edit: i guess its back online
any word on clockwork now that we have perm root?
Dead Link
the link for hboot_dhd.nb0 is dead. anyone want to post a mirror? it would be appreciated.
Thanks in advance.
EDIT: Nevermind...guess it working. Megaupload was having a glitch.
So I was messing around with different one clicks since I got ADB going on my kindle fire and I was able to Successfully use SuperOneClick 2.2 to root my kindle fire!
Sorry for the mess. Its late, and I wanted to type this up so I could crash...
To get adb going you must download the android sdk (google it).
*Run SDKManager.exe and download the google-usb_drivers package from "3rd party tools"
* Download platform-tools as well
Open a command prompt and run adb update usb to get the .android folder to appear.
goto: %USERPROFILE%\.android and edit the adb_usb.ini and add this to the end of the file and save:
Code:
0x1949
then go into where you have the sdk at and open the google-usb_driver folder and edit android_winusb.inf and add this to the [Google.NTx86] section and [Google.NTamd64] section:
Code:
;Kindle Fire
%SingleAdbInterface% = USB_Install, USB\VID_1949&PID_0006
%CompositeAdbInterface% = USB_Install, USB\VID_1949&PID_0006&MI_01
save and close
If you have already plugged your kindle into the usb you may have to open device manager and find "Kindle" under other devices and choose the android_winusb.inf file.
Turn on Installation of apps from unknown sources: tap the top bar>choose more...(+)>device
open a command prompt and run adb kill-server then try adb devices..
you should see a device listed.
go here: http://forum.xda-developers.com/showthread.php?t=803682a
download and run SuperOneClick and choose the "root" option. let it go!
Enjoy!
Proof:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Awesome!
Why do I have a mac
That was quick. I wonder if Amazon prefers the device to be rootable or not? Normal Kindle is quite easy to root too.
soundslikemitch said:
Why do I have a mac
Click to expand...
Click to collapse
^^ now THAT is funny ^^
Magnesus said:
That was quick. I wonder if Amazon prefers the device to be rootable or not? Normal Kindle is quite easy to root too.
Click to expand...
Click to collapse
Supposedly it was supposed to be easy to root. So I would think so. I am sure amazon could have made it a lot harder if they wanted to.
aimbdd said:
Supposedly it was supposed to be easy to root. So I would think so. I am sure amazon could have made it a lot harder if they wanted to.
Click to expand...
Click to collapse
I almost suspect from their coy comments (yes, it will be rooted, no we don't care, type of thing) That they're just after market share, period. Now let's bring on CM ICS! (impatient optimist in me, sorry!)
My question is can anyone get TTS to work?
soundslikemitch said:
Why do I have a mac
Click to expand...
Click to collapse
I lawl'd
* * *
Amazon said they wouldn't get in the way of root.
wow, this was quick! i hope we get custom gingerbread and later on ICS roms quick
Rooted Fire
Death2All - Rooting instructions worked like a champ!
Thanks for posting.
Donation to Shortfuse OTW.
Kind regards
Worked Beautifully!
Success!
My Kindle Fire is rooted and happily working with ADB.
Now lets get some dev-action love going on here . Thanks.
Good work
hey so can we now get the Amazon VOD app on our android phones with this root? If So...How do we do it?
soundslikemitch said:
Why do I have a mac
Click to expand...
Click to collapse
You could do it manually using the zergRush exploit, SuperOneClick just makes it easier for Windows people.
zergRush exploit: http://forum.xda-developers.com/showthread.php?t=1296916
(Usage instructions are there, it's fairly simple - push the binary to device with adb, chmod binary and then execute binary. this gives temp root, push su and busybox binaries for perm root and install superuser.apk)
[This replaces the SuperOneClick part of the original post, you still need to do everything leading up to that (editing adb_usb.ini etc.) - some parts may be changed slightly for mac/linux e.g. I would assume you need to edit a different file than "android_winusb.inf"]
EDIT: Guide for getting ADB working on Mac: http://blog.actlocalmedia.com/2011/11/developing-on-kindle-fire.html (probably applicable to Linux too). Do this, then you can manually root via ADB and zergRush.
Did rooting break video on demand playback for anyone else? When i go to watch a prime instant video now the play buttons are greyed out, and my device is "no longer configured correctly to play Amazon videos.
death2all110 said:
<snip> To get adb going you must already have the sdk on your machine and used it. <snip>
Click to expand...
Click to collapse
Never used it, but I have it installed. I don't even know where to begin
mipakr said:
Never used it, but I have it installed. I don't even know where to begin
Click to expand...
Click to collapse
to get the adb_usb file to show up, you can go into the tools directory of the sdk, open a command prompt and run android update adb - thatll at least create the file, then you just edit it as the directions state.
abremel said:
Did rooting break video on demand playback for anyone else? When i go to watch a prime instant video now the play buttons are greyed out, and my device is "no longer configured correctly to play Amazon videos.
Click to expand...
Click to collapse
Ditto for me. I called customer service, they claim to be looking into it. Debating whether to do factory reset and see what happens.
Sent from my ADR6300 using xda premium
smtom said:
Ditto for me. I called customer service, they claim to be looking into it. Debating whether to do factory reset and see what happens.
Sent from my ADR6300 using xda premium
Click to expand...
Click to collapse
Actually an easy fix - the unroot button on superoneclick unroots it, and a reboot restores video playback - the instant video app must have some sort of check in place to see if the device is rooted.
abremel said:
to get the adb_usb file to show up, you can go into the tools directory of the sdk, open a command prompt and run android update adb - thatll at least create the file, then you just edit it as the directions state.
Click to expand...
Click to collapse
You also need to install the Google USB driver via the SDK Manager I think to generate the other files that need editing.
All you need is working adb and fastboot on your PC.
Just like doing "idme bootmode 4002" in 6.2 but working in 6.2.1.
Download the attached fbmode.zip and run:
Code:
adb push fbmode /data/local/tmp
adb shell chmod 755 /data/local/tmp/fbmode
adb shell /data/local/tmp/fbmode
adb reboot
Then follow instructions to flash TWRP or whatever.
Experimental Version 0.9: includes nbmode for setting normal boot (4000) and rcmode for setting recovery boot (5000). Untested, PM me if there's a problem.
This should allow users who chmod'd/deleted /system and no longer have root to reboot to fastboot, correct?
I haven't tested it in that scenario, but it should. It shouldn't need anything more than adb. It's even static since I was too lazy to figure out why I was having trouble with shared libs.
pokey9000 said:
I haven't tested it in that scenario, but it should. It shouldn't need anything more than adb. It's even static since I was too lazy to figure out why I was having trouble with shared libs.
Click to expand...
Click to collapse
Confirmed, works fine for ppl that screwed off /system without a recovery.
*Stickyfied for awesomeness.
hello
thanks for your help
but it doensn't work for me
i booted the KF with the standard usb cable to use ADB
but refused this line : "adb shell /data/local/tmp/fbmode"
and impossible to go further
thanks if you have an idear
jluc
lucien12 said:
hello
thanks for your help
but it doensn't work for me
i booted the KF with the standard usb cable to use ADB
but refused this line : "adb shell /data/local/tmp/fbmode"
and impossible to go further
thanks if you have an idear
jluc
Click to expand...
Click to collapse
First make sure adb i even functioning
Code:
adb shell
if you get a $ or # prompt then it is,
then exit
Code:
exit
then
Code:
adb push fbmode /data/local/tmp
adb shell chmod 755 /data/local/tmp/fbmode
adb shell /data/local/tmp/fbmode
adb reboot
Worked like a charm recovering a bricked KF 6.2.1.
applied this, installed TWRP, modified the driver, rebooted in recovery, and installed the stock update to 2.6.1 without wiping.
Now my KF is working again. this would have been a sad long day if you weren't here. thanks pokey9000
Thanks a ton! This works great! Any chance you're willing to release the source code to this?
jonas3d said:
Thanks a ton! This works great! Any chance you're willing to release the source code to this?
Click to expand...
Click to collapse
No, I'm hoping to make it a little harder for Amazon to close this up. That said, you could recreate this very quickly from an strace.
Sent from my SAMSUNG-SGH-I777 using xda premium
done that. device reboot and then pc show device as "unknown".
tried to install recovery no good. device not found.
only after "reboot normal" the pc find the device but then its like before: abdb cannot ......
please help
ilanlen said:
done that. device reboot and then pc show device as "unknown".
tried to install recovery no good. device not found.
only after "reboot normal" the pc find the device but then its like before: abdb cannot ......
please help
Click to expand...
Click to collapse
Sounds like you have a problem with fastboot on your PC. Search in General, there are a bunch of threads on this.
Sent from my SAMSUNG-SGH-I777 using xda premium
thepsman said:
Worked like a charm recovering a bricked KF 6.2.1.
applied this, installed TWRP, modified the driver, rebooted in recovery, and installed the stock update to 2.6.1 without wiping.
Now my KF is working again. this would have been a sad long day if you weren't here. thanks pokey9000
Click to expand...
Click to collapse
Did the same but did wipe. Now my Fire is stuck in the Kindle Fire logo. It doesn´t flash like before, but i wait more than 20 minutes and it doesn´t pass the logo.
I´ll try with the factory cable when the pieces arrive.
osozraz said:
Did the same but did wipe. Now my Fire is stuck in the Kindle Fire logo. It doesn´t flash like before, but i wait more than 20 minutes and it doesn´t pass the logo.
I´ll try with the factory cable when the pieces arrive.
Click to expand...
Click to collapse
Yes. This didn't really do anything for me.
Got excited when someone said that this should work for people who had screwed the system permissions.
---------- Post added at 10:41 AM ---------- Previous post was at 10:02 AM ----------
Okay okay. I won't question the usefulness of this again.
Got TWRP installed via the use of the OP. Had the yellow traingle crap happen but got around that with this advice:http://www.jayceooi.com/2011/12/27/how-to-solve-stuck-at-yellow-triangle-issue-on-kindle-fire/
Cheers pokey9000. Saved the day.
Cheers
Can someone help me out? I'm trying to get this working and after I type in adb shell I get this message:
exec '/system/bin/sh' failed: no such file or directory (2)
Any ideas? My KF is stuck on the notorious "your Kindle Fire has detected a problem" screen. I'm also looking at this thread but I'm thoroughly confused.
http://forum.xda-developers.com/showthread.php?t=1423099
I also tried the command in the first post and after adb push fbmode I get:
cannot start 'fbmode': no such file or directory
A little more info, when I go to the Amazon Kindle USB Device properties in Device Manager, under Volumes I click populate and I get this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Basically my attempt at a partition using partition utility went horribly wrong.
Matt V said:
A little more info, when I go to the Amazon Kindle USB Device properties in Device Manager, under Volumes I click populate and I get this.
Basically my attempt at a partition using partition utility went horribly wrong.
Click to expand...
Click to collapse
Do you have FIREFIREFIRE or TWRP installed? The best route is to install FFF 1.1 if you can, rebuild the partition table, then install the stock image from TWRP.
I don't have anything installed, flashing the 6.2.1 update.zip removed everything. Is there a way to install FFF or TWRP without getting it to boot? I get the system/bin error anytime I try to execute anything in KFU.
Matt V said:
I don't have anything installed, flashing the 6.2.1 update.zip removed everything. Is there a way to install FFF or TWRP without getting it to boot? I get the system/bin error anytime I try to execute anything in KFU.
Click to expand...
Click to collapse
We are in the same situation. Without a working shell we are screwed. If only we could execute this without calling adb shell, but i think that´s impossible. Try to buy/build a factory cable to boot in fastboot. I´m still waiting for the pieces to build mine, will report when done.
osozraz said:
We are in the same situation. Without a working shell we are screwed. If only we could execute this without calling adb shell, but i think that´s impossible. Try to buy/build a factory cable to boot in fastboot. I´m still waiting for the pieces to build mine, will report when done.
Click to expand...
Click to collapse
Factory cable is probably your best route, though if you don't mind opening your Fire you could do this instead: http://forum.xda-developers.com/showthread.php?t=1405052&highlight=rekindle which will get you TWRP and FFF installed. Instead of using the FFF included (u-boot.bin) you should get the newer 1.1 release and run "fastboot oem format" before running "fastboot boot..." to put your partitions back to normal.
I did the same, but now I got splash screen "Kindle Fire" and now adb is not recognize my KF.
Please help!
In this guide i will show you how to root a JXD S18 03-xxxx device.
This method was tested on the following device:
OS: Android 4.1.1
Kernel: 3.0.36+ Feb 2
Soc: Rk2926
Model: S18-03-201304-4GB-00727
Root:
0. Download files.zip(from here) extract it and open it in explorer.
1. Connect your device to your computer (micro-usb)
2. Unmount all storage devices (TF/SD card, onboard TF/SD, etc..)
3. Enable USB Debugging (Under settings > Options for developers > Enable USB Debugging)
4. Open ''AdbDriverInstaller.exe'' and install the universal ADB driver
5. Automated process for rooting the device ''ROOT ME.bat'' Press any key and just wait and let the tablet reboot.
6. Manual root:
Code:
adb shell
mount -o remount,rw -t rfs /dev/block/st19 /system
exit
adb push busybox /system/bin
adb push su /system/bin
adb shell
chmod 4755 /system/bin/busybox
chmod 4755 /system/bin/su
mount -o remount,ro -t rfs /dev/block/st19 /system
exit
adb reboot
And now you have root.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Make sure to update su(super user) after rooting. Because it is outdated.
You can either use adb push for this or you can use the Google Play store to download the latest bin.
CWM-recovery
Download: http://files.androtab.info/rockchip/rk2928/20130425/S18-03_CWM.zip
From adb root shell
1. extract flash_image and recovery.img from CWM.zip
2. put flash_image and recovery.img into device, e.g.
adb push flash_image /dev/
adb push recovery.img /dev/
3. enter root shell (adb shell)
4. flash recovery.img into recovery partition with flash_image, e.g.
chmod 755 /dev/flash_image
/dev/flash_image recovery /dev/recovery.img
Read this when you have any issues
CWM installation problems, please try another method if this doesn't work for you.
Link: http://androtab.info/clockworkmod/rockchip/install/
If you have any issues while rooting please try:
adb kill-server
adb devices
And see if the devices is listed after killing the server.
If it is not than u may have another soc (older version does have other rockchip and the adb driver wont work properly).
This guide is for the latest version as if 1st May 2013: S18-03-XXXX (4.9.2013)
If you still have no output from adb devices you can try one more thing!
By editing android_winusb.inf in C:\Windows\System23\Drivestore\Filerepository\android_winusb.inf_amd64_neutral_<random_chars>
You will see two of those folders.
Open it with a text editor like notepad++ or notepad make sure you have nt authority rights
android_winusb.inf:
Code:
;------------------------------------NTx86------------------------------------
[Google.NTx86];
For loopback testing
And add this after the first space of declaring hardware ids;
Code:
%SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0010&MI_01
%SingleAdbInterface% = USB_Install, USB\VID_2207&PID_0010
%CompositeAdbInterface% = USB_Install, USB\VID_2207&PID_0010&MI_01
Tested and working on the following devices:
Audiosonic T-17B 7" tablet (Kmart webshop version) ✓
S18-03-XXXX (4.9.2013) ✓
S18-03-201302 (4gb-00905) ✓
S18-02-XXXX (x.x.2012) ?
Credits: me, icood70pro, fun_ for modding CWM for rockchip, all credit goes to original CWM author koush and all its contributors.
How about S18-02-xxxx ?
I got myself a S18-02-xxxx, The ADB drivers behave oddly for this gadget. The driver installs, but SuperOneClick can't locate the device.
It does have SuperUser installed, but only the .apk file, not the permissions required to run it.
Think you can setup something?
macrat said:
It does have SuperUser installed, but only the .apk file, not the permissions required to run it.
Click to expand...
Click to collapse
Can you get access to adb shell and what os are you running? Modified adb doesn't seem to work properly on windows 8 you need to change this in order to make it work for windows 8 i think (at least you can try).
Start -> Run -> Type: "gpedit.msc" (Without quotes) -> Computer Configuration -> Administrative Templates -> Windows Components -> Application Compatibility -> Turn off Application Compatibility Engine <- Disable this
It might be the S18-02-xxxx. Model 02 has another soc i think, can you download a app in the play store for me? Type in: "Cpu info", download and install -> "CPU / RAM / DEVICE Identifier". And tell me what soc you have in it. Because the older versions may have a a9 amlogic 8726-m3l soc in it.
Please try that and verify if that worked for you or if you get adb shell access. Thanks,
and sorry for the late reply.
Just wanted to confirm I have successfully rooted my Audiosonic T-17B &" tablet (AUS KMart version) using your guide!
Although I'll note that the BAT file didn't succeed for some reason. Manually following the commands worked fine though, but I didn't bother with CWM as yet.
EDIT: Figured it out. It's the 'exit' commands you've stuck in there, it terminates the whole batch command instead of just restarting ADB. Can you edit that and re-upload the zipfile?
switchblade88 said:
Just wanted to confirm I have successfully rooted my Audiosonic T-17B &" tablet (AUS KMart version) using your guide!
Although I'll note that the BAT file didn't succeed for some reason. Manually following the commands worked fine though, but I didn't bother with CWM as yet.
EDIT: Figured it out. It's the 'exit' commands you've stuck in there, it terminates the whole batch command instead of just restarting ADB. Can you edit that and re-upload the zipfile?
Click to expand...
Click to collapse
Yes i can and sorry for that mistake. Thanks for confirming that it did work for you on another device with the same soc.
Resquest download password
NiTrOwow said:
0. Download files.zip(from) extract it and open it in explorer.
Click to expand...
Click to collapse
I not success download the zip file because ask me for a password. It's possible obtain this password please?
Stef20 said:
I not success download the zip file because ask me for a password. It's possible obtain this password please?
Click to expand...
Click to collapse
Seems like a bug.. in the forum software handling the bbcode..
Just remove the <br /> at the end of the url and it works.
And my content does not even include <br /> == space/enter ...
FYI. PROBLEM IS SENT TO FORUM ADMIN.
Oh yes I not viewed this... Normaly I take care :silly:
I edit manually the link and work good. Thank you for the reply!
Stef20 said:
Oh yes I not viewed this... Normaly I take care :silly:
I edit manually the link and work good. Thank you for the reply!
Click to expand...
Click to collapse
Alright man good luck and let me know if it works for you and let me know the model number
I will for sure. I wait a new tablet S18 from China just I'm not sure if I will have a s03 or s02 model. I suppose is a S03.
NiTrOwow said:
Seems like a bug.. in the forum software handling the bbcode..
Just remove the <br /> at the end of the url and it works.
FYI. PROBLEM IS SENT TO FORUM ADMIN.
Click to expand...
Click to collapse
Thanks. This problem is now fixed. it will not ask for a password now.
Mike
Alright then, only thing that i miss on this tab is a uhm extra ogt support and a good data sheet of the soc. Else would have made a small shell/nas/webserver from out of it.. But modding requires me a data sheet or else i have to reserve engineer the soc and then try to mod it with luck(?)
MikeChannon said:
Thanks. This problem is now fixed. it will not ask for a password now.
Mike
Click to expand...
Click to collapse
Thanks Mike that was fast :')
Sent from my HTC Sensation using xda app-developers app
NiTrOwow said:
Alright then, only thing that i miss on this tab is a uhm extra ogt support and a good data sheet of the soc. Else would have made a small shell/nas/webserver from out of it.. But modding requires me a data sheet or else i have to reserve engineer the soc and then try to mod it with luck(?)
Click to expand...
Click to collapse
If I receive a S03 and I hope is this, I will try your tutorial, if is a S02 I will try other thing because I suppose is not the same CPU and this risk not work?
About the OTG, I have read a guy success use it on the S18 with a external power on the OTG. He say it's a power problem only. Just I lost the link where is this message.
I hope my english is OK because is not my language.
Stef20 said:
If I receive a S03 and I hope is this, I will try your tutorial, if is a S02 I will try other thing because I suppose is not the same CPU and this risk not work?
About the OTG, I have read a guy success use it on the S18 with a external power on the OTG. He say it's a power problem only. Just I lost the link where is this message.
I hope my english is OK because is not my language.
Click to expand...
Click to collapse
No i understand you if you get your S03 or 02 you will have to open it up and have a look at it yourself i made some close up images of the board.
They can be found right here
http://forum.xda-developers.com/showthread.php?t=2253706
So you can look at your device and mine from the inside and look what is diffrent
:good:
NiTrOwow said:
No i understand you if you get your S03 or 02 you will have to open it up and have a look at it yourself i made some close up images of the board.
They can be found right here
http://forum.xda-developers.com/showthread.php?t=2253706
So you can look at your device and mine from the inside and look what is diffrent
:good:
Click to expand...
Click to collapse
It's fun view the inside without open it I view have a little more space for a bigger battery
Stef20 said:
It's fun view the inside without open it I view have a little more space for a bigger battery
Click to expand...
Click to collapse
Forgot to say that this battery for the S18-03 has a pcb on the battery (fail safe, anti-overvolt). It did surprise me because most cheap china products don't have that and it is a risk if you want to use it a lot because it may someday explode if you don't have this haha .. Battery looks like a BL-5B/BLC-2 from nokia without the plastic housing.
Finaly I received my S18 today and it's a S03, just a big trouble... after only few hours of use, the power button refuse work now... It's a cra* product I received...
I'm a little sad not success try your tutorial because my S18 are dead before... Now I not able start my tablet... I will return it!
I purchase a Asus Me172v and success root it . I used this tutorial http://forum.xda-developers.com/showpost.php?p=42047570 , just I'm not able write in this section because I suppose I'm new or I need have more messages.
Stef20 said:
I'm a little sad not success try your tutorial because my S18 are dead before... Now I not able start my tablet... I will return it!
I purchase a Asus Me172v and success root it . I used this tutorial http://forum.xda-developers.com/showpost.php?p=42047570 , just I'm not able write in this section because I suppose I'm new or I need have more messages.
Click to expand...
Click to collapse
Oke that sucks to have a DOA.
I hope they will resort this, and that you will be able to try my guide.
Good luck man.
NiTrOwow said:
Oke that sucks to have a DOA.
I hope they will resort this, and that you will be able to try my guide.
Good luck man.
Click to expand...
Click to collapse
I wait a new S18, just it's very long to receive it with the cheap post chipping.
I want root it because I hate not have the control
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