Database Users

Reverse tethering for any android(2.3 also)(Google play working and other apps)

In my last post I had a problem related to reverse tethering in devices having android lower than 4.0.4 or having gingerbrand. I have gone through many websites and found a solution for it. The whole credit goes to http://blog.thambaru.com/idea/share-your-pcs-internet-connection-with-android-via-usb/. But when I followed these I faced some problems but finally done . I am having micromax A25 smarty. Now,
NOTE:- YOUR DEVICE MUST BE ROOTED AND HAVE SUPERUSER INSTALLED ON IT
1. the first is you have to download Reverse tethering kit(see attachment) and extract it
2. Install the application named tracetool.apk on you android powered phone
3. now run the androidtool.exe (in reverse tethering folder)
4. connect your device with your computer/laptop via USB cable
5. turn on USB Debugging from developers options in settings (DO NOT ENABLE STORAGE..ONLY USB debugging HAS TO BE TURNED ON)
6. now in androidtool you opened just click "CONNECT" and just wait for superuser dialogue box and allow the USB tunnel(name of tracetool application which u have installed)
7. now wait till it connects your phone. if your phone is not connected at first trial than no problem. Try it for another time or switch off notifications for superuser and then try again
NOW THIS IS THE MAIN STEP FOR ANDROID LESS THAN 4.0.4,
8. Take another phone which is able to make a portable wi-fi hotspot, Turn the hot spot on WITHOUT TURNING ON DATA CONNECTION IN ANY OF THE PHONE
9. connect your phone with this phone via wi-fi and then you are done
10. you will see Google Play(5228) in connections tab in androidtool if you will run and download applications from it
THIS IS FOR ANDROID 4.0.4 AND ABOVE
1.install xposed installer and the goto framework and then press install/update
reboot your phone
2. install hack connectivity service.apk module on your android and enable it from modules tab on you xposed.
3. reboot form your phone
IN THIS METHOD FOR 4.0.4 YOU DO NOT NEED ANY OTHER PHONE
xposed installer also comes for gingerbread but it doesn't worked n my phone due to processor architecture..but you can try on yo gingerbread (see attatchment XPOSEDGBINSTALLER)
NOW YOU SHOULD BE ABLE TO ACCESS INTERNET ON ANY OF THE APPLICATIONS USING IT AND YOU CAN ALSO UPDATE APPLICATIONS VIA GOOGLE PLAY

Many many thanks,got it working just in three minutes........Although I can browse internet and google play too,the download from google play never starts.It is stuck on "waiting for network". I would appreciate if you can work it out

shahrukh.sk said:
Many many thanks,got it working just in three minutes........Although I can browse internet and google play too,the download from google play never starts.It is stuck on "waiting for network". I would appreciate if you can work it out
Click to expand...
Click to collapse
what's your android version?

shahrukh.sk said:
Many many thanks,got it working just in three minutes........Although I can browse internet and google play too,the download from google play never starts.It is stuck on "waiting for network". I would appreciate if you can work it out
Click to expand...
Click to collapse
you need wifi hack service module activated via xposed to get the downloads working

Fire Tv 2 Version 5.0.5.1 (Build 537175520) "Waiting for preloader" problem.

Fire Tv 2 Version 5.0.5.1 (Build 537175520) "Waiting for preloader" problem.
Hello.
I apologize in advance if I am breaking any rules, Sorry.
I am trying to root Fire Tv 2 Version 5.0.5.1 (Build 537175520). I am using the A-to-A USB Cable Method. I follow all the steps. Until I reach to the part where I Run the install_firetv2_recovery.bat file by double clicking it. While it says “Waiting for preloader…” I connect the A-to-A USB cable to the Fire TV and then power up the Fire TV. Nothing happens after that, the computer stays on "Waiting for preloader".
Any help would be very much appreciated.
Please help!

qwe_123 said:
Hello.
I apologize in advance if I am breaking any rules, Sorry.
I am trying to root Fire Tv 2 Version 5.0.5.1 (Build 537175520). I am using the A-to-A USB Cable Method. I follow all the steps. Until I reach to the part where I Run the install_firetv2_recovery.bat file by double clicking it. While it says “Waiting for preloader…” I connect the A-to-A USB cable to the Fire TV and then power up the Fire TV. Nothing happens after that, the computer stays on "Waiting for preloader".
Any help would be very much appreciated.
Please help![/QUOT
Do you have all the drivers install properly? If so then try a different computer.
Click to expand...
Click to collapse

bula1ca said:
qwe_123 said:
Hello.
I apologize in advance if I am breaking any rules, Sorry.
I am trying to root Fire Tv 2 Version 5.0.5.1 (Build 537175520). I am using the A-to-A USB Cable Method. I follow all the steps. Until I reach to the part where I Run the install_firetv2_recovery.bat file by double clicking it. While it says “Waiting for preloader…” I connect the A-to-A USB cable to the Fire TV and then power up the Fire TV. Nothing happens after that, the computer stays on "Waiting for preloader".
Any help would be very much appreciated.
Please help![/QUOT
Do you have all the drivers install properly? If so then try a different computer.
Click to expand...
Click to collapse
Thank you, bula1ca, for your reply, I appreciate it. I follow the guide, I installed all the drivers, and I have tried 4 different computers. The same result, waiting for preloader. About the drivers, when I install Meditek DA usb vcom port, I get : "The software for this device is now installed, but may not work correctly. The device cannot start. (Code 10)." In all 4 computers I get the same think when I install mediatek. And on Device Manager, the MediaTek shows with yellow warnings. Could that be it. I follow the guide for installing MediaTek correctly.
Any help will be appreciated.
Thank you.
Click to expand...
Click to collapse

Driver shows with a yellow warning for me as well. are you sure your are using a correct type cable?

thank you very much, bula1ca, I very much appreciate your help.
you mean A-A usb cable? On the guide it says any any length or version/speed will do. The cable I am using is connected to the usb port of computer one side, the other side is connected to usb port of fire tv. The usb cable I think works ok, because, as the guide suggests, first I connect the computer to fire tv, and computer is able to detect the fire tv.
Installation of VCom drivers doesn't depend on a-a usb cable, right? On all 5 computers (3 of mine, 2 of neighbors) the mediatek drivers show with a yellow warning.
thank you again for your help.
Please help.

qwe_123 said:
thank you very much, bula1ca, I very much appreciate your help.
you mean A-A usb cable? On the guide it says any any length or version/speed will do. The cable I am using is connected to the usb port of computer one side, the other side is connected to usb port of fire tv. The usb cable I think works ok, because, as the guide suggests, first I connect the computer to fire tv, and computer is able to detect the fire tv.
Installation of VCom drivers doesn't depend on a-a usb cable, right? On all 5 computers (3 of mine, 2 of neighbors) the mediatek drivers show with a yellow warning.
thank you again for your help.
Please help.
Click to expand...
Click to collapse
Do me a favor connect everything to the computer but do not plug your FireTV yet (cord unplugged), now start the bat file and when you get the "Waiting for preloader" massage plug FireTv cord into the wall. Post back your findings

Thank you, bula1ca, very much for your help and for not giving up on me.
I did everything as you said, connected everything, but the fire tv, started the bat file, and then plugged fire TV's cord on the wall. The same result, "Waiting for preloader...". I did this many times, the same results.
Thank you again for your help, I appreciate it.
Please help.

qwe_123 said:
Thank you, bula1ca, very much for your help and for not giving up on me.
I did everything as you said, connected everything, but the fire tv, started the bat file, and then plugged fire TV's cord on the wall. The same result, "Waiting for preloader...". I did this many times, the same results.
Thank you again for your help, I appreciate it.
Please help.
Click to expand...
Click to collapse
Are you running the bat file as administrator...not sure if this will change anything but give it a try also take a picture of your install drivers in Device Manager and post it here. The reason you get this "Wait for preloader" is:
- drivers not installed properly
- cable used is not an A to A cable or is defected.
- firetv was plugged in prior running the bat file

Thank you very much, bula1ca, I appreciate your help very much. I got a shot of device manager and I am attaching it.
When I connect fire tv to computer with A-A usb cable, the computer sees the fire tv. Do you think that is an indication that the cable is ok?
Thank you again for your help.
Please help.

qwe_123 said:
Thank you very much, bula1ca, I appreciate your help very much. I got a shot of device manager and I am attaching it.
When I connect fire tv to computer with A-A usb cable, the computer sees the fire tv. Do you think that is an indication that the cable is ok?
Thank you again for your help.
Please help.
Click to expand...
Click to collapse
Do one more test.
- start script, Firetv power off and disconnected from computer
- connect it to computer
- power it on (plug it into the wall)
I am wondering if your cable is not a power cable only and does not carry data...
Take a picture of the device manager now, it should show being connected also take a look at this guide as well maybe you missed something ...http://www.aftvnews.com/how-to-root-the-amazon-fire-tv-2/
BTW this is what I used (just in case you need one) https://www.amazon.com/C2G-54171-Ma...d=1473723835&sr=1-3&keywords=a+to+a+usb+cable

bula1ca said:
Do one more test.
- start script, Firetv power off and disconnected from computer
- connect it to computer
- power it on (plug it into the wall)
I am wondering if your cable is not a power cable only and does not carry data...
Take a picture of the device manager now, it should show being connected also take a look at this guide as well maybe you missed something ...http://www.aftvnews.com/how-to-root-the-amazon-fire-tv-2/
BTW this is what I used (just in case you need one) https://www.amazon.com/C2G-54171-Ma...d=1473723835&sr=1-3&keywords=a+to+a+usb+cable
Click to expand...
Click to collapse
Thank you very much, bula1ca, I very much appreciate your help.
Thank you for the link for the cables, but I wanted to do a test using new cables as soon as possible, so I went out and bought a new power usb a-a cable, very expensive. I followed the guide, everything clean, starting from scratch, from the first line of the guide until "waiting for preloader....." Nothing after that. By the way, when I Install MTK65XX Preloader USB VCom drivers, everything looks the same as before on Device Manager, the same snapshot as the one I attached on my previous post.
The only thing left to suspect is the fact that I bought it brand new, and it comes with Version 5.0.5.1 (Build 537175520). I have stopped the updates. I am checking every time, and it shows Version 5.0.5.1 (Build 537175520). I know that Fire TV 2 Version 5.0.5.1 (Build 537175520) is rootable, and Fire TV 1 Version 5.0.5.1 (Build 537175520) is not rootable. So, are they still selling Fire TV 1? Mine says 4k ultra hd with alexa. So, I believe that's fire tv 2, right?
I know that I am bugging you a lot, bula1ca, so thank you, truly for all your replies.

make sure that USB debugging is enabled in Fire TV settings
check if ADB is working by running
Code:
adb devices
on your PC before using the batch

You have a FireTv2. Problem is program does not handshakes with your unit. I do not know if this will help (it should not) but connect it back to the TV and enable USB debugging under Developer Options (as cybero2912 suggested above) in Settings and then redo the whole process and post back.
If this will not work you can root it with kingoroot and then follow the procedure. Below is a different option of rooting.
http://www.aftvnews.com/how-to-root...covery-and-a-pre-rooted-rom-all-without-a-pc/

Thank you very much bula1ca, cybero2912 and anyone who is helping me now and in the future.
I checked on adb debugging and usb debugging on fire tv, they were on. I ran the command: adb devices. I got this reply:
"C:\WINDOWS\system32>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
XXXXXXXXXXXXXXXX device"
I substituted the numbers with "X". Then I run batch file: I got: "Waiting for preloader..."I tried many things, closed the window, run batch, shut down everything, repeat everything.
I tried Kingroot following the guide bula1ca suggested. I tried Kingoroot. Root failed every time.
Sorry, everyone, I know this is frustrating you too.
Thank you again for all your help.

maybe you mentioned it earlyer (writing from Phone and too lazy to read entire thread again)... but on which Fire OS version you are right now?

No problem, cybero2912, every suggestion is a good on, thank you for your help. I just checked it: Version 5.0.5.1 (Build 537175520). And software update blocking is working, it gives me an error when I try to update.
What about the ADB, do you think it's ok from the data I gave on the previous post? I checked online about ADB, and one suggestion was about ADB shell. They suggested to find sdk folder on my computer. I couldn't find it anywhere. Could that be the problem?
Thank you again for all the help, appreciate it.

Your best bet is still the A to A cable method for this firmware. Kingroot\Kingoroot did not work on all boxes.

from where do you get the plattform-tools (ADB Tools) when I rooted my AFTV1 I used latest SDK from Google

I followed the guide that bula1ca wrote on his previous post:
"http://www.aftvnews.com/how-to-root-...zon-fire-tv-2/"
" Step 2: Prepare Computer and Fire TV
1.If you haven’t done so yet, setup ADB and Fastboot on your computer by following this guide."
I can't write full links here, I am not allowed, right? But I follow the guide from aftnews.
Thank you, cybero2912, for pointing that out. When I tried to google: "SDK from Google", I got:
Google App Engine SDK for Python
Google App Engine SDK for Java
Google App Engine SDK for PHP
Google App Engine SDK for Go
I have no idea how to proceed, can you please advise what to install? Do I have to uninstall the old sdk, can you please tell me how, I would truly appreciate it.
Thank you.

I read the guide for Fire TV 2 on aftvnews
have you followed the guide carefully? especially this part:
Step 2: Prepare Computer and Fire TV
1. If you haven’t done so yet, setup ADB and Fastboot on your computer by following this guide.
2. Install MTK65XX Preloader USB VCom drivers on your computer by following this guide. (Windows 8.1 & 10 users may need to first disable driver verification)
3. Enable ADB debugging and USB debugging on your Fire TV by following this guide.
4. Power off the Fire TV, then connect the A-to-A USB cable to the Fire TV and your computer, and then power the Fire TV on. It’s important to always connect the USB cable first and THEN power on the Fire TV whenever you’re asked to do so in this guide. Wait for Windows to detect the Fire TV and install drivers. It will probably do this twice: once when it first powers up and again when it reaches the HOME screen. It’s fine and expected for Windows to report that not all drivers were installed correctly.
5. After Windows is done detecting the Fire TV, disconnect the A-to-A USB cable and power off your Fire TV. It’s important to always also disconnect the USB cable when asked to power off the Fire TV in this guide because the Fire TV can pull power through the USB cable and actually remain on without the power cable connected.
Click to expand...
Click to collapse

ADB not working

Hi guys...
Yesterday my new PH-1 arrived and today I wanted to use ADB with the app "custom navigation bar". My problem is: i can`t get it to work... I´ve used adb several times with different phones, but with the PH-1 it can´t connect with my Windows 10 computer. Is it possible that I can´t get it to work because Ì´m using a different USB-C cable (took 3 different from Xiaomi another manufacturer)?
How do get it to work? Everytime I connect the phone with the computer, I get the message USB debugging is on and I use MTP to work, but the phone doesn`t show the RSA key fingerprint. Any suggestions?

masterchief_2001 said:
Hi guys...
Yesterday my new PH-1 arrived and today I wanted to use ADB with the app "custom navigation bar". My problem is: i can`t get it to work... I´ve used adb several times with different phones, but with the PH-1 it can´t connect with my Windows 10 computer. Is it possible that I can´t get it to work because Ì´m using a different USB-C cable (took 3 different from Xiaomi another manufacturer)?
How do get it to work? Everytime I connect the phone with the computer, I get the message USB debugging is on and I use MTP to work, but the phone doesn`t show the RSA key fingerprint. Any suggestions?
Click to expand...
Click to collapse
Mines wouldn't connect using the usbc cable it came with I had to use a regular usb to usbc cable for it to work

See your device manager. To see if you are seeing "Mata". You have to download the google usb driver and update it from there
I have S8 from my previous computer but i need to re install the driver again

https://www.youtube.com/watch?v=LbAq6d2Du0U
You can also try this tuturial hope that it is working for you.

Try this > Download and install the essential usb driver > go to device manager and update the driver. Choose the option where you can change the source and select the driver in the list > go to the Essential Folder in Program Files and choose the file named "essentialadb.inf" for your pc. That should work
It's and old thread but if there is someone new to this...

My essential wouldnt work with the previous ADB i had installed that had worked fine with all my other devices.
I installed https://forum.xda-developers.com/showthread.php?t=2317790 and worked just fine. Make sure your device isnt connected as anything other than charging. The previous ADB i was using didnt acknowledge my device but on first try with Minimal i was prompted on my phone right away

I had the same problem when attempting to flash my ph-1, when trying to use the cable that came with the device. I used a standard USB-A to USB-C cable and everything worked just fine. I noticed on the 8.1 update notes for side loading that the team indicates that the cable that comes with the phone is "Primarily" designed for charging and not data transfer. So I'm guessing that it is of lower quality and doesn't handle the transfer speeds.

blackbms said:
I had the same problem when attempting to flash my ph-1, when trying to use the cable that came with the device. I used a standard USB-A to USB-C cable and everything worked just fine. I noticed on the 8.1 update notes for side loading that the team indicates that the cable that comes with the phone is "Primarily" designed for charging and not data transfer. So I'm guessing that it is of lower quality and doesn't handle the transfer speeds.
Click to expand...
Click to collapse
Hold either volume button while connecting cable from phone to pc, it will detect automatically. It may work.

Fire Toolbox

I have two identical Fire HD 10 9th generation. One works seamlessly using the Fire Toolbox. The other gets a message that the device is not authorized. All the settings on both tablets are identical, USB debugging is engaged. The second tablet is identified in the Fire Toolbox (RSK key), but it always asks me to authorize my device. It tells me to unlock my device and that a window should appear with the computer's RSK key and then to tap the box that says "Always allow from this computer". However, no such window ever appears. I have reset the second table to factory default, made all of the appropriate settings (Developer Options - USB Debugging), but to no avail. Does anyone have any suggestions?

PDC07 said:
I have two identical Fire HD 10 9th generation. One works seamlessly using the Fire Toolbox. The other gets a message that the device is not authorized. All the settings on both tablets are identical, USB debugging is engaged. The second tablet is identified in the Fire Toolbox (RSK key), but it always asks me to authorize my device. It tells me to unlock my device and that a window should appear with the computer's RSK key and then to tap the box that says "Always allow from this computer". However, no such window ever appears. I have reset the second table to factory default, made all of the appropriate settings (Developer Options - USB Debugging), but to no avail. Does anyone have any suggestions?
Click to expand...
Click to collapse
You can use another USB-C cable or USB port on your PC.
If you're PC running Windows 7 or 8.1 that causes a driver fails. Try it to upgrade your PC to Windows 10.

I appreciate your work DataStream, thanks for saving me from constantly updating my own scripts and batch files.
One question please:
Does anyone have a method to permanently disable Wi-Fi?
I know it sounds strange to want a Tablet to not have connectivity, but I have a very specific need to do so. I found I could Root the Tablet and run uFirewall to kill Wi-Fi, but the end user can just undue the setting. I am trying to just disable the Wi-Fi and defeat the Toggle Switch. I would prefer not to Root as I have a decent quantity to configure identically. I wouldn't mind preforming Factory Resets if required to re-enable Wi-Fi if ever needed.

Wondering if anybody knows if the Fire Toolbox 16 will work with the new Fire HD 10 plus (2021).

Don Leighton said:
Wondering if anybody knows if the Fire Toolbox 16 will work with the new Fire HD 10 plus (2021).
Click to expand...
Click to collapse
The new version 17 will. Go to the OP in the thread and download it.

Wheres the direct link to download the toolbox since I need to install Google play on my amazon fire 8 please?

removed post and added to the Toolbox thread

Where is the download link for the toolbox?

How To Bypass Fire TV 4K Checking For Updates Screen on Setup

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