Related
My nephew managed to get into TWRP and somehow wiped the entire thing clean. I purposely keep a recovery .zip in there but even that's gone. When the Kindle is turned on it displays the Fire triangle but then the screen goes black and stays like that. I can boot into TWRP but can't use the mount option or adb because my computer, and the three others I've tried, refuses to recognize the Kindle. It shows up in Device Manager as Unknown and I can't manually install the driver. I've tried every combination of booting it with the computer off or on, uninstalling the Unknown driver, everything. Can you kind folks please save my butt? Thanks in advance for your responses.
wiped in TWRP and Windows only displays device as Unkown
Lance Uppercut,
Have you tried starting adb services and going back through the FireFireFire Utility, this has fixed a lot of boot errors that I had in the pass?
Let me know if you need help with starting adb services.
Thanks,
JohninLex
Thanks for your reply
Can you please elaborate on this a bit more? Maybe I'm not understanding correctly but I thought starting adb services wouldn't do anything in this instance since it wouldn't recognize the Kindle as being there at all? For instance, when I run Kindle Fire Utility it shows adb devices as being offline. If I could get the Kindle to show up as anything other than Unknown I'm certain I could just update the driver to an android device and have KFU take it over from there.
wiped in TWRP and Windows only displays device as Unkown
Lance Uppercut,
Did you root your Kindle "adb devices"
and the following commands?
adb shell chmod 777 /data/local/tmp
adb install Burritoroot3.apk
or did you download a file from the market to get root?
if you did it the above way with adb commands from a terminal would be great.
Either way lets set the driver, download the Kindle Fire Utility extract it to your desktop. or take note where you extracted it. Then go to your device manager and right click on the Kindle (unknown device) look for update driver and browse the the Kindle Fire Utility folder double click on the drivers folder and let it update the right driver you need for your OS (XP,Vista, 7 x86 or 64). Once it finds the right driver Open up a command prompt by going to start run and typing cmd and hitting enter. Once that is done download the KindleADB files and place them in the C:\ (drag and drop should be fine here ) go back to your command prompt and do the following commands:
** urname** C:\ " cd KindleADB " then hit enter
and then do " adb devices " it may or may not come back with your device sn but as long as it has started is what we are looking for.
Once that is done go back to your desktop leaving everything open and look through the Kindle Fire Utility until you find a file named Run.bat double click and hit run this will reinstall twrp and allow it to be remount-able. If you need a stock Kindle rom with update 6.2.2 I have a back up I can share with you.
I hope this helps but if it does not let me know and we can go back over the the driver section.
Thanks,
JohninLex
I've attempted installing the driver manually many times like you stated and on different PCs all containing KFU and the modified .ini file in the .android folder and the message I get when I attempt to manually update the driver is "The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems." When I first got the message I attempted to do it in an x86 system and the driver would still not install. My inability to get ANY computer to read the kindle as anything other than Unknown is the main issue. Even if I could make it read as the default "kindle" with the exclamation point it would be enough for me to fix it. But if I can't get a driver to load I'm hopeless to fix it in any way.
Use Android composite driver on your PC to get adb working. Once the adb is working, there multiple ways to boot or install a new ROM. I recommend to start doing the following commands:
Fastboot mode.
Try these ADB commands:
fastboot -i 0x1949 oem idme bootmode 4000
fastboot -i 0x1949 reboot
or
adb shell idme bootmode 4000
adb shell reboot
Ng you have an Android phone, connect to you PC first to see if adb is working using composite ad driver for Windows operating system
Sent from my Amazon Kindle Fire using Tapatalk
I can't use android composite driver. Every time I attempt to install the driver manually I get the error listed above. No matter what I do I can't get the Kindle to be anything other than Unknown
i had a problem where i could only get the fire symbol screen computer would not recognize. I had to start the kindle fire utility plug my kindle into the computer then turn it off, then have kfu install latest twrp again when it says waiting for device turn device on and it will reinstall that and get you back to the recovery. so maybe you can do the same with obtain stock update. not really sure to the kindle. my computer would recognize kindle fire for a few seconds and thats how i could install new twrp
about drivers:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
if you can't get rid of the drivers:
http://forum.xda-developers.com/showthread.php?t=1430038
nevertheless i would never install the original stock rom cause you loose fff,twrp and root
use one of the prerooted stock roms instead:
http://forum.xda-developers.com/showpost.php?p=22393194&postcount=20
I had this exact same problem and ended up with a bricked kindle for a few weeks. I tried everything on the forum...uninstalling/reinstalling drivers/sdk/etc. At the end of it all I had the drivers installed properly (which was a real pain in the keyster) but my computer still would not recognize my device.
I found 2 posts that finally helped me:
1) in the .android file for adb_usb.ini, you need to add in 0x006 in another line. Also dont forget to add the 3-line code @ [Google.NTx86] and [Google.NTamd64]
Here is a link. This link has just about everything else you need to do to solve this issue.
http://www.kindle-fireforum.com/forum/amazon-kindle-fire-development/1086-adb-issues-solved-how.html
2) manually mount the drive and flash update.zip. For some reason my kindle got locked in fastboot, then when i switched it to normal it would get stuck on the loading animation. If this happens you probably need to flash and start over.
Here is that process.
http://forum.xda-developers.com/showpost.php?p=22433402&postcount=4
hope this helps and good luck
Help me save my kindle fire
I used KFU to install TWRP and up to CM9. But after that i restore to rom stock 6.2.
But after kindle start the error sorry loop in screen . I can not access to kindle.
process.android.acore force close
We try to connect and re install TWRP but not successfull. when i connect kindle to my pc (XP and window 7) it only recognize kindle as disk driver (athough i try to uninstall and setup manual driver )..
Help me urgent.
Thanks alot
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
mhb1509 said:
I had this exact same problem and ended up with a bricked kindle for a few weeks. I tried everything on the forum...uninstalling/reinstalling drivers/sdk/etc. At the end of it all I had the drivers installed properly (which was a real pain in the keyster) but my computer still would not recognize my device.
I found 2 posts that finally helped me:
1) in the .android file for adb_usb.ini, you need to add in 0x006 in another line. Also dont forget to add the 3-line code @ [Google.NTx86] and [Google.NTamd64]
Here is a link. This link has just about everything else you need to do to solve this issue.
http://www.kindle-fireforum.com/forum/amazon-kindle-fire-development/1086-adb-issues-solved-how.html
2) manually mount the drive and flash update.zip. For some reason my kindle got locked in fastboot, then when i switched it to normal it would get stuck on the loading animation. If this happens you probably need to flash and start over.
Here is that process.
http://forum.xda-developers.com/showpost.php?p=22433402&postcount=4
hope this helps and good luck
Click to expand...
Click to collapse
This comment gave a ton of hope since I have tried everything that has been mentioned already except for adding 0x006 but sadly it did not work. There's absolutely nothing I can do to get out of the Unknown state. I've never had my ass kicked this hard by a piece of hardware. I surrender.
maybe this as a last resort:
http://forum.xda-developers.com/showthread.php?t=1430038
b63 said:
maybe this as a last resort:
http://forum.xda-developers.com/showthread.php?t=1430038
Click to expand...
Click to collapse
I was reading through that earlier and it was a little too intimidating. I'm just going to sit here and cry for a couple of minutes.
Kindle still recognize as disk driver
I try to do something but adb not working (device not found because it recognize as normal disk driver). My pc use window xp professional.
How can i solve this
My kindle still recognize as normal disk driver
I try to test on some computers (xp, win7) but unfortunately, my kindle still recognize as normal usb only. (not adb device).
So i don know how to fix this problem
Please help me, or give me a hint
xp is a good choice - you don't have to care about the uac (user acces control)
have you checked according to my post #12 above ?
to shorten things up i could take a look with teamviewer if you like
just gimme a pm ...
Have you added the second vendor and the second set of USB command lines in your google/extras folder? If not add those turn off the kindle then turn it back on do "fastboot devices" then put the update.zip in your platform-tools folder then push the update to your kindle to be flashed by twrp. The command for that would be "advt push update.zip /sdcard/update.zip" you can have the kindle already in twrp by this point. Also when all is over you will have to reroot and reinstall fff and twrp. If you need help send me a message.
Sent from my Kindle Fire using Tapatalk
Hard reset on main-board KF
My KF is frozen. I try to do hard reset by hold pw button 20s, but not effected.
So i've just open back-slide my KF, and see KF main-board.
Have hard reset trick on this main-board.
Help me please.
After reading around, I've learnt that MinimalTouch 1.1beta5 is a reliable way to root my new Nook Simple Touch. Since I intend selecting the package version in the beta5 folder, I must choose between the "START" zips: beta5-2 XUFullTouch-PART-1-START and beta5-2 XWFullTouch-PART-1-START. I gather the first zip is ADB over USB, and the second, ADB over WiFi, but have found little documentation on either, except that ADB is a method to connect your home computer to your Nook.
The above link states that all W zips install ADB wireless Uramdisk, and all U zips install ADB USB Uramdisk + ADB widget to enable wireless adb at need. Am I right that ADB over USB is the best choice because both USB and WiFi are available after rooting? If so, would anyone select the ADB over WiFi option?
Can someone please explain how and why one chooses between the two options when rooting the Nook?
On startup the ADB daemon, adbd looks at the property service.adb.tcp.port
If it is set it uses that value as the port number over TCP (presumably over WiFi) to listen for connections.
If it is not set it tries to connect over USB.
I'm not sure how these applications that switch mode work.
They probably kill the daemon and restart it.
The only difference between the two versions of W and U is the line:
Code:
service.adb.tcp.port=5555
Renate NST said:
The only difference between the two versions of W and U is the line:
Code:
service.adb.tcp.port=5555
Click to expand...
Click to collapse
Thanks for your help. I've taken a while to make sense of your post since all this is new to me - I rarely use a mobile phone.
I've just looked at contents of both the "START" zip files and noticed they're the same, except that the file uRamdisk in the folder boot of the WiFi option is marginally bigger. You have shown me the difference lies in the property service.adb.tcp.port in the Java source code, and that property determines whether the rooted Nook tries to connect by WiFi or USB. In other words, the two zips are identical except for ADB connection.
But my opening post, in ignorance, attempted to ask a more trivial question. I know whenever I wish to access any laptop computer from my desktop computer under Windows XP, I can connect the two using a network cable from the laptop to my wireless router/modem or, more simply, by activating WiFi on the laptop. Similarly, I am assuming I can connect the rooted Nook to my desktop either by cabling the Nook microUSB port to a USB port on my desktop, or by activating WiFi on the Nook. I expect to connect every few days. Since the USB "START" zip of MinimalTouch 1.1beta5 provides an ADB widget to enable wireless adb at need, what is the point - for the end user - of a separate WiFi only "START" zip file?
In other words, in routinely connecting my rooted Nook to the desktop computer every few days, why on earth would I or anyone benefit from having had the two "START" zip options available in MinimalTouch 1.1beta5?
I'm currently getting some strange errors while trying to control my N4 over adb.
http://prntscr.com/1km24i
On Ubuntu I get "device unauthorized" and on Windows 8 I get "device offline".
Same thing happens over USB.
Any idea?
PS: I'm currently on 4.2.2. I where on 4.3 yesterday but installed 4.2.2 again after some strange errors.
HashWorks said:
I'm currently getting some strange errors while trying to control my N4 over adb.
http://prntscr.com/1km24i
On Ubuntu I get "device unauthorized" and on Windows 8 I get "device offline".
Same thing happens over USB.
Any idea?
PS: I'm currently on 4.2.2. I where on 4.3 yesterday but installed 4.2.2 again after some strange errors.
Click to expand...
Click to collapse
As the message have stated, you need to allow the adb access on your phone.
You need to first connect the phone to your PC with USB cables, then the authorization message will pop out on the screen. Tick remember your choice, then allow it.
ksilver89 said:
As the message have stated, you need to allow the adb access on your phone.
You need to first connect the phone to your PC with USB cables, then the authorization message will pop out on the screen. Tick remember your choice, then allow it.
Click to expand...
Click to collapse
I'm not getting any message.
Maybe because I already authorized my pc before. A few weeks ago adb worked just fine.
HashWorks said:
I'm not getting any message.
Maybe because I already authorized my pc before. A few weeks ago adb worked just fine.
Click to expand...
Click to collapse
Remove /data/misc/adb/adb_key, reboot your phone and try connect again. The message should come up.
Perfect, worked. Thanks!
I just got my phone back from LG (the mainboard "Fried"). I have the new update pushed to the phone. I have to re-root the phone now as its basically a new phone.
I am getting the Device offline as well message in ADB. As I don't have root, how can I fix this error? I can't navigate to that particular directory. I had no authotization message show up on my computer when I plugged the phone in for the first time... so not sure how to get past this...
usafle said:
I just got my phone back from LG (the mainboard "Fried"). I have the new update pushed to the phone. I have to re-root the phone now as its basically a new phone.
I am getting the Device offline as well message in ADB. As I don't have root, how can I fix this error? I can't navigate to that particular directory. I had no authotization message show up on my computer when I plugged the phone in for the first time... so not sure how to get past this...
Click to expand...
Click to collapse
This shouldn't be happening on new phone, because the key won't be created if you haven't authorized it.
Can you check your adb version? Try updating it with android sdk manager.
I am going to try and re-download the ADB SDK. I think it's an issue with whatever version I downloaded. I've tried to run the ADB Manager.exe and nothing happens. Currently flying to London so it will have to wait until I get back. Nice of LG to fix my phone and they didn't charge me a dime. Although I did lose everything.
Hello,
I'm having the same problem "Please check the confirmation dialog on your device", but there is no such dialog on the device.
Things I tried and DID NOT SOLVE:
1) Remove /data/misc/adb/* - Failed, there was nothing there (full wipe before flash a new rom)
2) Try different ROMs - Failed, tried AOKP Milestone 1 and 2 and CM10. Dialog never showed up.
3) Try different usb cable OR usb port - Failed, adb is recognized, but no confirmation dialog on the device (device shows as unauthorized)
4) Removed all drivers and installed them again - Failed, same problem;
5) Updated android-sdk (or full delete and reinstall [remembering to adb kill-server]) - Failed, problem continues even with platform-tools up-to-date.
6) Removed all folder C:\Users\Myself\.android - Failed, it was never recreated;
7) Tried to connect via adb over wifi, device is found but unauthorized persists;
Things that gave me some clues:
1) Reboot to recovery mode allowed me to use ADB without any authorization (only while in recovery);
2) Recovery sideload works without any problem;
3) HOWEVER, when connecting to another computer (Windows XP, fresh install on a virtual machine), dialog appears and adb works!
The scenario:
1) Devices tried: Galaxy Nexus / Galaxy S3 I9300
2) ROMs tried: AOKP (4.2.2) / CM10 (4.2.2)
3) Windows 7 x64
The problem is on the computer side, that's a fact. However, I would like to SOLVE it without having to reformat my computer, or change my OS.
Where to start?
Thanks!
legalbrr2 said:
Hello,
I'm having the same problem "Please check the confirmation dialog on your device", but there is no such dialog on the device.
Things I tried and DID NOT SOLVE:
1) Remove /data/misc/adb/* - Failed, there was nothing there (full wipe before flash a new rom)
2) Try different ROMs - Failed, tried AOKP Milestone 1 and 2 and CM10. Dialog never showed up.
3) Try different usb cable OR usb port - Failed, adb is recognized, but no confirmation dialog on the device (device shows as unauthorized)
4) Removed all drivers and installed them again - Failed, same problem;
5) Updated android-sdk (or full delete and reinstall [remembering to adb kill-server]) - Failed, problem continues even with platform-tools up-to-date.
6) Removed all folder C:\Users\Myself\.android - Failed, it was never recreated;
7) Tried to connect via adb over wifi, device is found but unauthorized persists;
Things that gave me some clues:
1) Reboot to recovery mode allowed me to use ADB without any authorization (only while in recovery);
2) Recovery sideload works without any problem;
3) HOWEVER, when connecting to another computer (Windows XP, fresh install on a virtual machine), dialog appears and adb works!
The scenario:
1) Devices tried: Galaxy Nexus / Galaxy S3 I9300
2) ROMs tried: AOKP (4.2.2) / CM10 (4.2.2)
3) Windows 7 x64
The problem is on the computer side, that's a fact. However, I would like to SOLVE it without having to reformat my computer, or change my OS.
Where to start?
Thanks!
Click to expand...
Click to collapse
Make sure to use the latest ADB executable, also check if you don't have any other adb.exe in your computer, from command promt: where adb.exe
maxrfon said:
Make sure to use the latest ADB executable, also check if you don't have any other adb.exe in your computer, from command promt: where adb.exe
Click to expand...
Click to collapse
Hello,
No, adb.exe is up-to-date and there's a single instance of it on my computer.
Problem must be somewhere else.
Thanks anyway
legalbrr2 said:
Hello,
No, adb.exe is up-to-date and there's a single instance of it on my computer.
Problem must be somewhere else.
Thanks anyway
Click to expand...
Click to collapse
Hello,
please delete the sdk settings folder on your pc, on my linux box i deleted ~/.android and it worked
Regards
c.cicali said:
Hello,
please delete the sdk settings folder on your pc, on my linux box i deleted ~/.android and it worked
Regards
Click to expand...
Click to collapse
Doesn't work yet..
Tried to delete "C:\Users\Myself\.android" and "Documents\.android".
Did a full search on filesystem, and found no other .android folders.
Thanks anyway.
legalbrr2 said:
Doesn't work yet..
Tried to delete "C:\Users\Myself\.android" and "Documents\.android".
Did a full search on filesystem, and found no other .android folders.
Thanks anyway.
Click to expand...
Click to collapse
After removing your .android directories, you need to restart the adb server to send fresh credentials to the phone.
First unplug the phone from your computer, then run:
Code:
$ adb kill-server
$ adb start-server
Now plug your phone back in and you should see a dialog on the device asking to confirm new credentials for your computer.
After confirming the credentials you should be able to connect to your device.
I hope that this helps...
legalbrr2 said:
Hello,
I'm having the same problem "Please check the confirmation dialog on your device", but there is no such dialog on the device.
Things I tried and DID NOT SOLVE:
1) Remove /data/misc/adb/* - Failed, there was nothing there (full wipe before flash a new rom)
2) Try different ROMs - Failed, tried AOKP Milestone 1 and 2 and CM10. Dialog never showed up.
3) Try different usb cable OR usb port - Failed, adb is recognized, but no confirmation dialog on the device (device shows as unauthorized)
4) Removed all drivers and installed them again - Failed, same problem;
5) Updated android-sdk (or full delete and reinstall [remembering to adb kill-server]) - Failed, problem continues even with platform-tools up-to-date.
6) Removed all folder C:\Users\Myself\.android - Failed, it was never recreated;
7) Tried to connect via adb over wifi, device is found but unauthorized persists;
Things that gave me some clues:
1) Reboot to recovery mode allowed me to use ADB without any authorization (only while in recovery);
2) Recovery sideload works without any problem;
3) HOWEVER, when connecting to another computer (Windows XP, fresh install on a virtual machine), dialog appears and adb works!
The scenario:
1) Devices tried: Galaxy Nexus / Galaxy S3 I9300
2) ROMs tried: AOKP (4.2.2) / CM10 (4.2.2)
3) Windows 7 x64
The problem is on the computer side, that's a fact. However, I would like to SOLVE it without having to reformat my computer, or change my OS.
Where to start?
Thanks!
Click to expand...
Click to collapse
I know that this post is old, but I came across the same problem while attempting to root my Galaxy S4 today. This ended up being the solution:
1. Grant yourself root access on the PC that is running adb
2. Remove RSA Keys:
rm /home/username/.android/*
3. Restart adb server:
adb kill-server
adb start-server
I hope that this helps.
SOLVED!
I guess I should have read the previous post before I posted this but anyway maybe this helps.
I had this happen to my Verizon Samsung Galaxy S4 SCH-I545 running 4.3 (VRUEM2K) after I rooted using saferoot, then removed the SuperSU app using SuperSU's so-called "safely unroot" menu option. It will no longer request the RSA key from the Ubuntu system I previously authorized (and used to root) and won't re-root using saferoot or motochopper. But since I dual-boot Windows 7 (I hardly use it, came with the laptop), I figured I'd give Odin a try and re-flash it to stock which didn't do anything to the "custom" flag and I still got "unauthorized" in adb in Ubuntu, but I noticed it does show up fine with adb in Windows. I tried the windows verison of saferoot and it was able to re-root my phone and re-install SuperSU just fine. Phone still showed "unauthorized" in Ubuntu.
After posting this I saw the previous comment saying to rm -rf ~/.android/ in Ubuntu. I also cleared all previously authorized computers and disable dev mode on my phone, rebooted, turned dev mode back on, rebooted again. Not sure if this helped, but I went through the following steps as root:
[email protected]:~# adb kill-server
[email protected]:~# adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
15506b89 unauthorized
At this point I pretty much said "F it, not gonna work" and walked away to get a snack, leaving my phone plugged in. I was only gone a couple minutes and when I came back, the RSA authorization request had popped up on my phone. I checked the box to always allow this computer and authorized it. Then SUCCESS, as seen below:
[email protected]:~# adb devices
List of devices attached
15506b89 device
Removing the .android directory seemed to do it, but you need to wait a few minutes for the computer to re-request the RSA key.
after a week of searching. I NEVER KNEW it pop to accept to authorized. WOW cant believe it... after reading this thread im lol'ding right now.
I had tried to kill adb etc but keep saying aunauthorized. solution was to reboot my phone with usb connected,after boot it the dialog to connect appear and my s4 got authorized. backup success.
thanks to the adb kill-server guy! worked for me
gonpwnya said:
thanks to the adb kill-server guy! worked for me
Click to expand...
Click to collapse
Ditto
Just checking it there is some way to recover files. I previously rooted it and can't remember if that means there's any way to get at it via ADB or otherwise to recover files before transfering to a new device
Well, if you have ADB working you can just transfer the files.
Or you could use my AdbSync.exe (along with ADB) to backup.
Code:
C:\>mkdir whatever
C:\>adb devices
C:\>adbsync /hcsu /s /v C:\whatever sdcard
ADB doesn’t seem to be working or at least via USB… And I can’t get on it to select a Wi-Fi network. Wondered if there is some way of forcing it to boot in Adb mode or something that doesn’t rely on screen interaction
mrbryan said:
ADB doesn’t seem to be working or at least via USB… And I can’t get on it to select a Wi-Fi network. Wondered if there is some way of forcing it to boot in Adb mode or something that doesn’t rely on screen interaction
Click to expand...
Click to collapse
You're the second person in a week or so that seems to have this issue and it got me curious. There's a message at the beginning of NookManager about starting WiFi if you want to directly connect with the device via SSH(?) or ADB. I've always ignored it but I just tried it to see what would happen. After you elect to start WiFi (your NST must have been known to your network beforehand, password entered, etc.), you are given the option to start either SSH or ADB (the IP address is displayed at the top of the screen).
When I chose ADB I was then able to start up ADB on my PC and connect to the IP address shown on the NST screen. Of course.....if your screen is broken........Maybe you know the IP address of your NST already or could find it by starting WiFi and then consulting your router?
Anyway, the advantage with NookManager is that everything is done with the side hardware buttons. If you can't read your screen at all I can see that even that would be a problem, though. If you have some partial display, you might be able to limp along until you have ADB connected and then handle everything from your PC. Or I could supply you with a button-push sequence to try.
To just get this working you can make a NookManager card--no need to make the updates I described elsewhere.
thanks so much for the suggestion. I'll have to think that through and whether I have my current wifi set up ( edit: in the nook already).
maybe I can hack around in the scripts for nook manager in case I can set it to go right to the ADB on boot and inject a wifi name & key too
Get an image for the old noogie and put it on an SD card.
Boot up, you should have ADB.
Or do the whole OmapLink procedure and boot from there.
Or connect to the 1.8V UART root console inside the case.
The process is very simple. You need an unlocked bootloader and TWRP. You also need to edit the file, build.prop and add this following tweak below:
#Enable ADB Debugging By Default & Disable USB Debugging Popup
persist.adb.notify=0
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
Then go ahead pair your Fire TV remote upon setup wizard, plug in your Fire TV 4K into your computer and allow adb prompt. After you've done those things type in adb shell monkey -p com.amazon.tv.oobe -v 1000. BE sure your out of the pause and play to continue and it'll bypass the checking for updates screen!
Doesn't work for me on mantis, I've tried it several times. Installed 6.2.7.6, added options to build.prop on TWRP. Rebooted, paired remote and powered off the stick. Connected to computer, received adb authorization window and accepted. Pushed play/pause to start and on language selection screen, entered adb shell monkey command. Then what I assume are very fast auto button presses pass the screen, leaving me at network selection (green or yellow rectangles on item selections are shown). After I connect, the stick starts searching for updates normally. What am I doing wrong? Cheers.
gabardal said:
Doesn't work for me on mantis, I've tried it several times. Installed 6.2.7.6, added options to build.prop on TWRP. Rebooted, paired remote and powered off the stick. Connected to computer, received adb authorization window and accepted. Pushed play/pause to start and on language selection screen, entered adb shell monkey command. Then what I assume are very fast auto button presses pass the screen, leaving me at network selection (green or yellow rectangles on item selections are shown). After I connect, the stick starts searching for updates normally. What am I doing wrong? Cheers.
Click to expand...
Click to collapse
That's normal for it to show the network selections and green/yellow boxes. You'd have to keep inputting the command really fast. It'll force the updates screen and go back to it. Try putting the monkey command 3-4 times until it goes to the device registration screen. It takes a few tries to bypass
So, what screen would I be watching to know it has worked?
Edit: It eventually worked, but it's hit and miss I guess . You just have to keep trying, thank you very much for this.
Skel40 said:
The process is very simple. You need an unlocked bootloader and TWRP. You also need to edit the file, build.prop and add this following tweak below:
#Enable ADB Debugging By Default & Disable USB Debugging Popup
persist.adb.notify=0
persist.service.adb.enable=1
persist.service.debuggable=1
persist.sys.usb.config=mtp,adb
Then go ahead pair your Fire TV remote upon setup wizard, plug in your Fire TV 4K into your computer and allow adb prompt. After you've done those things type in adb shell monkey -p com.amazon.tv.oobe -v 1000. BE sure your out of the pause and play to continue and it'll bypass the checking for updates screen!
Click to expand...
Click to collapse
This seems like an easier method:
How to block updates on a rooted Fire TV or Fire TV Stick by setting a custom Fire OS version number
This is a new method of blocking software updates on a rooted Fire TV or Fire TV Stick. It involves setting a custom software version number in the device's build.prop configuration file. Rbox came up with this idea and asked me to test if it works.
www.aftvnews.com
Just boost the build number to 9..., and it should think it's already upgraded.
It doesn't work for me because the stick won't show up in adb devices. I've tried diffrent cables, PCs and even FireOS (6.2.7.7 and 6.2.7.6) versions but it simply won't show up as an adb device. Any idea what's wrong here?
Ungeskriptet said:
It doesn't work for me because the stick won't show up in adb devices. I've tried diffrent cables, PCs and even FireOS (6.2.7.7 and 6.2.7.6) versions but it simply won't show up as an adb device. Any idea what's wrong here?
Click to expand...
Click to collapse
Did you add the tweaks through your computer and adb them back to your 4K? Try adding the tweaks in the build.prop file and try again. If that doesn't work I'd be nice enough to post a rom containing the tweak for adb to work
Skel40 said:
Did you add the tweaks through your computer and adb them back to your 4K? Try adding the tweaks in the build.prop file and try again. If that doesn't work I'd be nice enough to post a rom containing the tweak for adb to work
Click to expand...
Click to collapse
No, I added them manually on the stick itself inside TWRP (I checked for typos), since I can't reboot it to recovery whilst connected to my PC. I'm updating it right now to the latest firmware where I can enable ADB so I can reboot to recovery and then downgrade to 6.2.7.7 and see if that works.
EDIT: It works now, I had to be on 6.2.8.0 so I can reboot to recovery and from the recovery I wiped 6.2.8.0, flashed 6.2.7.7, Magisk and edited the build.prop all without disconnecting the FireTV from my PC. After that it showed up as an ADB device.
Hey so. I don't know if I'm missing something here or but whenever I connect my stick to my PC, I really don't know how to boot into twrp and keep twrp on while connected to my PC
The prompt lasts only but 5 seconds and without any external otg keyboard or mouse connected I can't manage to hold the stick in recovery as it directly boots to system after when disconnected and connected again.
If there's any chance someone can guide me to a way that would help me enable adb and keep the stick in twrp while connected to the PC I'll be thankful.
If the initial Setup is done, you can enable adb in the Settings.
If not , it can only be done by rerooting with unlock script ( if you have no otg adapter).
0815hoffi said:
If the initial Setup is done, you can enable adb in the Settings.
If not , it can only be done by rerooting with unlock script ( if you have no otg adapter).
Click to expand...
Click to collapse
I'm looking to bypass the updates at the initial setup screen actually. I don't get ADB enabled at the setup screen even after replacing the edited build.prop file through the twrp file manager and using an otg usb stick to copy it over in the system directory.
What other way is there I can use to do that? If I disconnect the power it only shows the twrp prompt which I can't access because there's no otg adapter connected.
Edit: Forgot to mention I have to remove the OTG because the PC doesn't recognize the firestick when I connect it through that. If I connect it directly it works absolutely fine.
nagi_007pk said:
I'm looking to bypass the updates at the initial setup screen actually. I don't get ADB enabled at the setup screen even after replacing the edited build.prop file through the twrp file manager and using an otg usb stick to copy it over in the system directory.
What other way is there I can use to do that? If I disconnect the power it only shows the twrp prompt which I can't access because there's no otg adapter connected.
Edit: Forgot to mention I have to remove the OTG because the PC doesn't recognize the firestick when I connect it through that. If I connect it directly it works absolutely fine.
Click to expand...
Click to collapse
Go to this post, it will bypass setup screen enable accessibility and app widget also, Skel40 removed some things also but i may upload a clean 6.2.8.1 setup later.
if you are in fastboot/recovery/system you can use the following command to open twrp when you are connected via pc
Code:
adb reboot recovery
for system and twrp
Code:
fastboot reboot recovery
to launch twrp from fastboot
now if you can start your stick and can access adb (i know you can't otherwise you already should have bypassed OOBE) then you can open twrp from the adb and you can use adb sideload also
if you have a usb otg + hub then put the zip in pendrive connect it to hub along with mouse and install it from there.
if you dont have a hub then you will have to use kamakiri again, after bootrom-step it will open hacked bl, you can use fastboot-step.sh to flash twrp again, when TWRP is open you can sideload the file to the twrp.
it will bypass the OOBE and also block system update natively.
SweenWolf said:
Go to this post, it will bypass setup screen enable accessibility and app widget also, Skel40 removed some things also but i may upload a clean 6.2.8.1 setup later.
if you are in fastboot/recovery/system you can use the following command to open twrp when you are connected via pc
Code:
adb reboot recovery
for system and twrp
Code:
fastboot reboot recovery
to launch twrp from fastboot
now if you can start your stick and can access adb (i know you can't otherwise you already should have bypassed OOBE) then you can open twrp from the adb and you can use adb sideload also
if you have a usb otg + hub then put the zip in pendrive connect it to hub along with mouse and install it from there.
if you dont have a hub then you will have to use kamakiri again, after bootrom-step it will open hacked bl, you can use fastboot-step.sh to flash twrp again, when TWRP is open you can sideload the file to the twrp.
it will bypass the OOBE and also block system update natively.
Click to expand...
Click to collapse
What if i'm trying to install 6.2.7.7 and not 6.2.8.1?
Edit: Also because of the kodi passthrough and otg mounting script developed by pretorian as I want to stay and set this firmware up without it looking for updates in the beginning.
nagi_007pk said:
What if i'm trying to install 6.2.7.7 and not 6.2.8.1?
Edit: Also because of the kodi passthrough and otg mounting script developed by pretorian as I want to stay and set this firmware up without it looking for updates in the beginning.
Click to expand...
Click to collapse
I'm assuming you can use TWRP and have 6.2.7.7 installed with pretorianos kernel
Flash this along with Pretorianos kernel
clear data and cache
then just boot.
it will skip it, you may have to set IR twice but it will go through, tell me how many times it asked to setup IR
SweenWolf said:
I'm assuming you can use TWRP and have 6.2.7.7 installed with pretorianos kernel
Flash this along with Pretorianos kernel
clear data and cache
then just boot.
it will skip it, you may have to set IR twice but it will go through, tell me how many times it asked to setup IR
Click to expand...
Click to collapse
does this zip work for any build ? or just for 6.2.7.7 ?
tokoam said:
does this zip work for any build ? or just for 6.2.7.7 ?
Click to expand...
Click to collapse
This zip is fully compatible with 8.0 and 8.1 because its pulled from 6.2.8.1
It will certainly bypass any build that is 6.2.7.7 or greater
It will not run on older builds like 7.1 or 7.3
SweenWolf said:
This zip is fully compatible with 8.0 and 8.1 because its pulled from 6.2.8.1
It will certainly bypass any build that is 6.2.7.7 or greater
It will not run on older builds like 7.1 or 7.3
Click to expand...
Click to collapse
I do have another question if you have TWRP installed and installed a custom rom isnt twrp suppose to prevent it from effecting efuse by default ? even if an update is done within the os ? this is unclear to me as I heard it suppose to . Also is there any other easy way to check the status of an efuse other than taking it apart and connecting it to kamakir and running lsusb command to check for bootrom-step ?
tokoam said:
I do have another question if you have TWRP installed and installed a custom rom isnt twrp suppose to prevent it from effecting efuse by default ? even if an update is done within the os ? this is unclear to me as I heard it suppose to . Also is there any other easy way to check the status of an efuse other than taking it apart and connecting it to kamakir and running lsusb command to check for bootrom-step ?
Click to expand...
Click to collapse
TWRP cannot prevent efuse burning, efuse is burnt by the system while booting to prevent a system downgrade (mostly for security purposes, samsung also does this).
The file responsible for burning efuse is present in /system/bin partition which can be accessed by the system to check the status of the fuse.
You don't have to worry about efuse if you never flashed 6.2.8.0 or higher.
The system will blow efuse only if there is a change in the critical partitions.
6.2.7.7 does have efuse files present in the system but because there were no updates to the critical partitions so it didn't blew anything. It will blow only if you flash stock >8.0
If you were on 6.2.7.7 and used my method to upgrade then
it upgraded your system
then updated TZ then removed the efuse writer
so it never got to know that an update was performed, so your fuse is intact.
There is nothing on your system which will blow your efuse.
SweenWolf said:
TWRP cannot prevent efuse burning, efuse is burnt by the system while booting to prevent a system downgrade (mostly for security purposes, samsung also does this).
The file responsible for burning efuse is present in /system/bin partition which can be accessed by the system to check the status of the fuse.
You don't have to worry about efuse if you never flashed 6.2.8.0 or higher.
The system will blow efuse only if there is a change in the critical partitions.
6.2.7.7 does have efuse files present in the system but because there were no updates to the critical partitions so it didn't blew anything. It will blow only if you flash stock >8.0
If you were on 6.2.7.7 and used my method to upgrade then
it upgraded your system
then updated TZ then removed the efuse writer
so it never got to know that an update was performed, so your fuse is intact.
There is nothing on your system which will blow your efuse.
Click to expand...
Click to collapse
well in my case I flashed rbox version of from first being rooted 8.0 then upgraaded to 8.1 with the version skel40 posted
tokoam said:
well in my case I flashed rbox version of from first being rooted 8.0 then upgraaded to 8.1 with the version skel40 posted
Click to expand...
Click to collapse
Then you're safe