Hello
I have problems with adaway .I installed adaway and if I won't activate it he dated me hosts can't copy. My phone is rooted
Kevinkuensken said:
Hello
I have problems with adaway .I installed adaway and if I won't activate it he dated me hosts can't copy. My phone is rooted
Click to expand...
Click to collapse
Turn off /system partition write protection.
http://forum.xda-developers.com/axon-7/help/command-to-root-changes-to-persist-t3440276
Only write this Line in Mini adbshell and that was all?
Kevinkuensken said:
Only write this Line in Mini adbshell and that was all?
Click to expand...
Click to collapse
Right. Enable developer options, enable USB Debugging, connect A7 to your computer, make sure you accept the connection on the phone, then open up Minimal ADB, type in "adb devices" to make sure that the ADB daemon is running and detects your phone, and if it does type in the command "adb shell reboot disemmcwp". The phone will reboot (maybe twice), then go and download & apply AdAway blocklists.
Thx it work
Related
I have troubles with developer mode on my phone.
Enable usb debug option is checked, but adb (running under gentoo linux, ubuntu, windows 7) doesn't show any devices.
But when recovery (CWM) is loaded, everything works well.
When I'm trying to start adbd with
Code:
#adbd start
I get message "cannot bind tcp:5037"
I thought it appears because adbd is already running but
Code:
ps aux | grep adb
gives nothing
Any ideas what to do? Does anyone have problems with adb even if Usb debug is turned on?
I use Debian and my command is adb start-server.
Give it a try.
Fr0zen1977 said:
I use Debian and my command is adb start-server.
Give it a try.
Click to expand...
Click to collapse
It doesn't help
Shtsh said:
...But when recovery (CWM) is loaded, everything works well...
Click to expand...
Click to collapse
Looks like ROM problem. Did you tried another one??
Yes. I'm tried several stock ROMs (2.3.6, 2.3.5), cranium, broodROM. Factory reset doesn't help.
I was trying this recovery screenshot tool http://forum.xda-developers.com/showthread.php?p=50029759#post50029759 without installing adb. I followed the instructions and wrote the width 240 and the height 320 (I am not at all sure of those) and when it tried to take the framebuffer i got the error "adb is not properly connected" and asks me to try to unplug and reinsert the usb cable. I then installed adb using this procedure http://forum.xda-developers.com/showthread.php?p=48915118#post48915118 and after successful installation i got the same error.
thanks in advance
maged rifaat said:
I was trying this recovery screenshot tool http://forum.xda-developers.com/showthread.php?p=50029759#post50029759 without installing adb. I followed the instructions and wrote the width 240 and the height 320 (I am not at all sure of those) and when it tried to take the framebuffer i got the error "adb is not properly connected" and asks me to try to unplug and reinsert the usb cable. I then installed adb using this procedure http://forum.xda-developers.com/showthread.php?p=48915118#post48915118 and after successful installation i got the same error.
thanks in advance
Click to expand...
Click to collapse
Make sure you have USB debugging enabled in your phone settings
You can test if adb is connected by doing the following
Open a command prompt where you have adb.exe
Type the following
adb devices
You will then get a list of devices connected
Remember not all kernels support adb in recovery mode
not all kernels?
marcussmith2626 said:
Make sure you have USB debugging enabled in your phone settings
You can test if adb is connected by doing the following
Open a command prompt where you have adb.exe
Type the following
adb devices
You will then get a list of devices connected
Remember not all kernels support adb in recovery mode
Click to expand...
Click to collapse
I have the debugging mode enabled and when i tried the "adb" devices command in the adb.exe directory it didnt show that there is any device connected.
about the "not all kernesupport adb" note how about stock kernel? and what best kernels work with adb and doesnt affect my systemfile and other things?
Edit: i flashed savie's kernel and i think it works
problems with the tool
I now have a problem that when i try to make a configuration file all screenshots in the pixel_formats folder are disturbed in a certain pattern (every line is a bit compressed vertically and the line is with a slope so the picture is completely disturbed)
I managed to get a clear screenshot using manual mode but the problem there that i sometimes scroll to something in the recovery and i take the screenshot i found it didnt scroll i then try to open a menu or so and take the screenshot it gives me a hollow screenshot with only the background of the CWM it happens nearly always so i cant get proper screenshots what i can do? and also i found the manual mode is a bit hard as i have to change the setting every time isnt there any tool easier than this
thanks in advance
maged rifaat said:
I have the debugging mode enabled and when i tried the "adb" devices command in the adb.exe directory it didnt show that there is any device connected.
about the "not all kernesupport adb" note how about stock kernel? and what best kernels work with adb and doesnt affect my systemfile and other things?
Edit: i flashed savie's kernel and i think it works
Click to expand...
Click to collapse
It's the kernel & cwm build - I don't know exactly what has to be enabled in the kernel & the CWM build but unless they support adb in recovery it won't work
Think manual mode is the best way as the galaxy y is ldpi - There probably are other tools out there you just have to search around
thanks !
marcussmith2626 said:
It's the kernel & cwm build - I don't know exactly what has to be enabled in the kernel & the CWM build but unless they support adb in recovery it won't work
Think manual mode is the best way as the galaxy y is ldpi - There probably are other tools out there you just have to search around
Click to expand...
Click to collapse
I cant thank you enough whenever i have a problem i find you helping me really thanks
Hi.
I have a nexus 7 2012 edition which turns on with The Google written logo and under the screen with a padlock. After that it will be in bootloop with a black screen ( I can see the backlight turning on/off). This is also if pressing the power+volume down combination. Seems bootloader is corrupted. Anyway I installed everything on pc plus I'm using the WugFresh Nexus Root Toolkit and here are some examples which show what errors I'm encountering when trying to flash stock firmware .
Log:
Checking ADB/FASTBOOT Connectivity
adb devices
015d4a5ed8500c01 unauthorized
fastboot devices
There is also a notification popup which tells me:
"An ADB Interface device was found but it was listed as "unauthorized"
-Accept the RSA security prompt and check "Always allow from this computer"
At this point I don't know what to do, can you help me?
Same issue - following
I have the same issue now after trying to flash a kernel to fix the slow charging issue. Following this post for any update.
Sunil_511 said:
I have the same issue now after trying to flash a kernel to fix the slow charging issue. Following this post for any update.
Click to expand...
Click to collapse
Hi, Sunil_511...
Bit speculative this, and I can't say for certain if the following solution would work, because I've never had this problem myself. It also requires that your Nexus 7 be in a fully bootable state.
Go to your Nexus 7 Developer Options in the devices settings and tap on 'Revoke USB debugging authorisations'. Tap on OK to confirm. See attached screenshot.
This, theoretically, should wipe the slate clean.
Reboot both your N7 and your PC/laptop and when you next reconnect your N7 to your PC/laptop, you'll be asked to authorise this new USB connection when you perform some action that requires it.
Well, that's the plan anyway.
Good luck?.
Rgrds,
Ged.
Nope, in my case my tab is not booting to recovery or system. The only option is adb and it is showing unauthorized. My last option what i think off is to change the motherboard.
Following
I have the same error and like to follow
Sunil_511 said:
I have the same error and like to follow
Click to expand...
Click to collapse
Google search is your friend. I found the following two methods which seems to have worked for some people.
1. If you are using OS X*:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
*For Windows 10, .android directory is located in your the base of your C:\User\user_name directory.
2. Go to where you have stored adb files, open that folder and press "CTRL+SHIFT+Right Click" and select and click on Open Command Prompt option
Now enter following command
adb start-server (Enter)
adb usb (Enter)
After that your device is no longer unauthorized and you should be able to use any command in your Android Mobile using PC/ Computer.
If these fixes don't work, SEARCH.
thanks buddy, i have tried pushing the adb keys but no luck. I will try tge second option. Will let you know after trying.
No difference still the same
BxG4ever said:
Hi.
I have a nexus 7 2012 edition which turns on with The Google written logo and under the screen with a padlock. After that it will be in bootloop with a black screen ( I can see the backlight turning on/off). This is also if pressing the power+volume down combination. Seems bootloader is corrupted. Anyway I installed everything on pc plus I'm using the WugFresh Nexus Root Toolkit and here are some examples which show what errors I'm encountering when trying to flash stock firmware .
Log:
Checking ADB/FASTBOOT Connectivity
adb devices
015d4a5ed8500c01 unauthorized
fastboot devices
There is also a notification popup which tells me:
"An ADB Interface device was found but it was listed as "unauthorized"
-Accept the RSA security prompt and check "Always allow from this computer"
At this point I don't know what to do, can you help me?
Click to expand...
Click to collapse
tnsmani said:
Google search is your friend. I found the following two methods which seems to have worked for some people.
1. If you are using OS X*:
Reboot your phone into recovery mode.
Connect it to your computer.
Open the terminal and type:
cd ~/.android
adb push adbkey.pub /data/misc/adb/adb_keys
All done! Just adb shell reboot and feel the power!
*For Windows 10, .android directory is located in your the base of your C:\User\user_name directory.
2. Go to where you have stored adb files, open that folder and press "CTRL+SHIFT+Right Click" and select and click on Open Command Prompt option
Now enter following command
adb start-server (Enter)
adb usb (Enter)
After that your device is no longer unauthorized and you should be able to use any command in your Android Mobile using PC/ Computer.
If these fixes don't work, SEARCH.
Click to expand...
Click to collapse
Tried your suggestion.. Which i might have tried eventually from googling.. Doesn't make any difference.
Fixed
After doing all the researches, i had to buy a new motherboard and then replace it. Installed new rom and now using it. Spared about 1400INR for a 32 gig version.
As the title says, I'm fed up with the Google News Application. But the thing is., It is installed as a system app and I don't want that- Disable is the only option that exists for me. I've been disabling it everyday. Even I've disabled Auto-Update for that but still it ENABLES by itself and even UPDATES BY ITSELF.
I've even seeked the help of customer care but they told me to visit SERVICE CENTRE and I even did the same. When I visited the service centre, they just Hard resetted my device and I told them that I've done it more than 6 times at home. They started arguing with me thereby accusing me with bad words...
My phone is still under warranty and I don't want to lose it by installing TWRP and rooting it...
Any kind SUGGESTIONS are HEARTLY WELCOME.
Use ADB.
Download ADB from Google to your PC. (Minimal ADB did not work for me, The one from developers.google.com is the one that works for me)
After ADB, Go to settings and about phone, Tap on build number 7 times. Now you will enable developer options.
Go to deverloper options and enable USB debugging. Now connect phone and open cmd from the folder where you installed adb(Just type cmd in the address bar of the folder). Now a black window will open on your PC.
Then type adb devices on your PC. Now there will be a prompt on your phone asking allow access to the PC.
Select yes and then go to your pc and type-
Code:
adb shell
Code:
pm uninstall -k --user0 com.google.android.apps.magazines
Then press enter.
Now Google News will be uninstalled.
(I tested this, And also used this various apps, They work fine. Your OTA will not break and the apps will not come back after an system update also)
Cheers
SnapDrag910 said:
Use ADB.
Download ADB from Google to your PC. (Minimal ADB did not work for me, The one from developers.google.com is the one that works for me)
After ADB, Go to settings and about phone, Tap on build number 7 times. Now you will enable developer options.
Go to deverloper options and enable USB debugging. Now connect phone and open cmd from the folder where you installed adb(Just type cmd in the address bar of the folder). Now a black window will open on your PC.
Then type adb devices on your PC. Now there will be a prompt on your phone asking allow access to the PC.
Select yes and then go to your pc and type-
Code:
adb shell
Code:
pm uninstall -k --user0 com.google.android.apps.magazines
Then press enter.
Now Google News will be uninstalled.
(I tested this, And also used this various apps, They work fine. Your OTA will not break and the apps will not come back after an system update also)
Cheers
Click to expand...
Click to collapse
Okay. Thank you. But it gets only HIDDEN not completely uninstalled. As of I know, I can't uninstall permanently without root access.
SnapDrag910 said:
Use ADB.
Download ADB from Google to your PC. (Minimal ADB did not work for me, The one from developers.google.com is the one that works for me)
After ADB, Go to settings and about phone, Tap on build number 7 times. Now you will enable developer options.
Go to deverloper options and enable USB debugging. Now connect phone and open cmd from the folder where you installed adb(Just type cmd in the address bar of the folder). Now a black window will open on your PC.
Then type adb devices on your PC. Now there will be a prompt on your phone asking allow access to the PC.
Select yes and then go to your pc and type-
Code:
adb shell
Code:
pm uninstall -k --user0 com.google.android.apps.magazines
Then press enter.
Now Google News will be uninstalled.
(I tested this, And also used this various apps, They work fine. Your OTA will not break and the apps will not come back after an system update also)
Cheers
Click to expand...
Click to collapse
Btw, should I install GOOGLE DRIVERS or NOKIA DRIVERS? I had tried installing Nokia drivers previously which didn't work properly..
PiXinCreate said:
Use ADB.
Download ADB from Google to your PC. (Minimal ADB did not work for me, The one from developers.google.com is the one that works for me)
After ADB, Go to settings and about phone, Tap on build number 7 times. Now you will enable developer options.
Go to deverloper options and enable USB debugging. Now connect phone and open cmd from the folder where you installed adb(Just type cmd in the address bar of the folder). Now a black window will open on your PC.
Then type adb devices on your PC. Now there will be a prompt on your phone asking allow access to the PC.
Select yes and then go to your pc and type-
Btw, should I install GOOGLE DRIVERS or NOKIA DRIVERS? I had tried installing Nokia drivers previously which didn't work properly..
Click to expand...
Click to collapse
Nokia's drivers are the only ones you need to install.
Yes, Using this ADB method will not uninstall this app from the system rather it disables the app for you. But this disabled app will not come back unless you want it too, Not even after OTA.
SnapDrag910 said:
Nokia's drivers are the only ones you need to install.
Yes, Using this ADB method will not uninstall this app from the system rather it disables the app for you. But this disabled app will not come back unless you want it too, Not even after OTA.
Click to expand...
Click to collapse
Honestly speaking, in New to using ADB... But knew sp flash tool and I had thought that both are similar but not.
Are Nokia drivers are same as Google drivers?
Can you share me the step by step procedure is you enough time now, sir?
I just downloaded latest usb driver from developer.android.com
Hey Guys let me tell you I do get automatic installation (via Google Play) for the Google News app (yes frustrating ) but what I did is uninstalled updates emptied it's data and forced stop / disabled it.
As of this comment I do get automatic installation request via Google Play but Google News doesn't updates. This worked for me.
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