I wanted to change fonts but accidently i got problem at system/fonts.
So I got in loop as below. can I have any help here?
Bagunny said:
I wanted to change fonts but accidently i got problem at system/fonts.
So I got in loop as below. can I have any help here?
Click to expand...
Click to collapse
Restore to defaults it [should] work
Sent from my KFTT using Tapatalk 2
..
..
ybs485 said:
I have tried many solutions.But it did not work.
1. Select 'Restore to defaults' : not work
2. Adb command by kinlde cable : not work
3. Fastmode command by Factory cable : not work -> device detected 'android adb interface'
4. Factory Reset 20s solution: not work
Is there another solution? :crying:
Click to expand...
Click to collapse
1. Restore to defaults will not change anything outside the sdcard folder even if it has been altered. Remember you are not even suppose to have access to make changes to those folders, so why would a factory reset need to affect any of those files.
2. If your computer is registering your device as "android adb interface" then you do not have the right drivers installed or something has happened to the ones you did. These links are the easiest way to absolutly insure you have the proper drivers:
https://developer.amazon.com/sdk/fire/connect-adb.html
https://developer.amazon.com/sdk/fire/setup.html#step6
3. Are you sure you are using a "factory cable". When you power down the device and plug it in using a factory cable it should boot to a screen with a logo- "FASTBOOT Kindle Fire". If yes,(i recommend everyone read this thread before doing anything to their devices) :
http://forum.xda-developers.com/showthread.php?t=1930656
And maybe keep an eye on:
http://forum.xda-developers.com/showthread.php?t=1944718
Hope some of this helps, sorry but with a signed bootloader and no custom recovery your options are very limited. The only thing I can see is to hope someone posts a copy of a system partition and flash it through fastboot.
Does anyone know why PTP mode would not be retained across a reboot? It seems to revert to MTP when rebooting into either the bootloader menu or into regular user mode.
I am trying to unlock the bootloader on my Nexus 6 running the latest build N6F27C of 7.1.1 that was sideloaded over 7.0 using ADB from my Mac. Now I'd like to start again and perform a clean flash of the 7.1.1 using ADB.
In normal user mode I can enable USB debugging in Developer Options and when PTP USB mode is selected then ADB will list my device just fine, I can trigger a reboot, etc.
However, after rebooting into the bootloader menu ADB shows that it has lost connection with my device, even though the screen shows that USB is connected. The ADB device list is empty.
On subsequent reboot into user mode I can see that USB debugging mode is still on but PTP connection mode has reverted to MTP, which (at least on a Mac) can account for ADB's lost USB connection to the device.
ADB debugging in PTP mode has worked fine for me in the past, but the phone now has been through several factory resets and restores from Google's backups, plus it is on 7.1.1.
Hello,
I got my phone brand new about 4 months ago. I rooted it and got TWRP installed with no issues. Fastboot and ADB were working fine but now when I try to connect my phone via USB and use ADB I get unauthorized whenever I type adb devices. Typically this happens because your phone is prompting you to allow the computer to have root access but I am not getting that popup window at all.
Things I've tried;
Uninstalled ADB/Updated ADB
Deleted adbkey folder under C:\Users\name\.android
Stopped and Started the adb server again after computer and phone reboot
Deleted ADB_keys folder on android in \data\misc\adb folder on phone itself, followed by a restart
Turning off then back on USB Debugging
Turning off then back on USB Debugging & Developer Options
(Including Revoking USB Debugging Authorizations both times)
Even tried copying the following from PC to phone ~/.android/adbkey.pub inside the /data/misc/adb/adb_keys
Still no luck, I'm not sure why it would just stop working out of nowhere. Nothing has changed since I used it a few months ago.
Also another strange occurrence is that if I turn off USB Debugging / Developer Options then reboot. Once the phone gets to the home screen both USB Debugging and Developer Options are enabled again without me doing it.
Anyone else have a similar issue and figure it out?
vulcanrvn said:
Hello,
I got my phone brand new about 4 months ago. I rooted it and got TWRP installed with no issues. Fastboot and ADB were working fine but now when I try to connect my phone via USB and use ADB I get unauthorized whenever I type adb devices. Typically this happens because your phone is prompting you to allow the computer to have root access but I am not getting that popup window at all.
Things I've tried;
Uninstalled ADB/Updated ADB
Deleted adbkey folder under C:\Users\name\.android
Stopped and Started the adb server again after computer and phone reboot
Deleted ADB_keys folder on android in \data\misc\adb folder on phone itself, followed by a restart
Turning off then back on USB Debugging
Turning off then back on USB Debugging & Developer Options
(Including Revoking USB Debugging Authorizations both times)
Even tried copying the following from PC to phone ~/.android/adbkey.pub inside the /data/misc/adb/adb_keys
Still no luck, I'm not sure why it would just stop working out of nowhere. Nothing has changed since I used it a few months ago.
Also another strange occurrence is that if I turn off USB Debugging / Developer Options then reboot. Once the phone gets to the home screen both USB Debugging and Developer Options are enabled again without me doing it.
Anyone else have a similar issue and figure it out?
Click to expand...
Click to collapse
Go Here and download the Fastboot drivers. follow the directions on the razor dev portal. I had the same issue and this fixed it for me. https://developer.razer.com/razer-p...94.1708481542.1586624574-305520188.1586475530
If your adb-server is not started with root/admin rights, your phone will never prompt you for authorization unless you choose a different USB Mode (MTP, PTP, etc.) than Charge Only. I suspect this is done to prevent certain malicious actions being performed without the user being aware.
If you start your adb-server with root/admin rights (by typing "sudo adb start-server", make sure you've killed your existing daemons before doing so), you can use ADB while in Charge Only mode, provided you've subsequently authorized the PC to do so. However, unlike normal adb server, the fingerprint may occasionally change and you may need to redo the authorization again.
Rooting Black Shark 3 / 3 Pro the Correct & Easy Way - BL Unlocking, TWRP & OTA Fix
Greetings fellow Black Shark users!
This guide is made for Black Shark 3 Pro Global version, but in theory it should work with any version if the bootloader is unlocked.
Warning: Before you start, backup your phone data as this would wipe your phone!
Do this at your own risk, I'm not responsible if you break your phone!
Prerequisites:
- Update your phone to the latest version possible.
- Download ADB, BOOTLOADER UNLOCK TOOL & TWRP Installer for Black Shark 3 Pro Global or Black Shark 3 Global.
On Phone:
1- Enable Developer Options. (Go to Settings, then About Phone, then Tap on Build number 7 times, then enter your password if needed)
2- Enable OEM unlocking. (Go to Settings, then Additional Settings, then Developer Options, then enable OEM unlocking option, then enter your password if needed)
3- Enable USB Debugging. (Go to Settings, then Additional Settings, then Developer Options, then enable USB Debugging option)
On PC:
4- Run BS3Pro_by_KM Installer. (Use the right version for your device. Right click and choose run as administrator. On driver installation popup click Next, then Install and Finish. Also Install dotNet3.5 if it ask for it. You must reboot your PC after the installation.)
5- Connect your Phone to PC using USB cable.
On Phone:
6- When Allow USB debugging popup appear, tap OK. (Tick Always allow from this computer)
On PC:
7- Make sure google drivers installed correctly and that your PC can see your Phone. (Android ADB Interface)
8- Open Command Prompt as administrator. (Type CMD in Windows search bar, then right click on Command Prompt ‘cmd’ and click on Run as administrator)
9- In CMD type:
Code:
cd c:\adb
Then press Enter key.
10- In CMD type:
Code:
adb devices
Then press Enter key. (If you can see a Device ID with ‘device’ written on its right, then continue to next step, if not then recheck your drivers. If you see a Device ID with ‘unauthorized’ written on its right, then go back to step 6)
11- In CMD type:
Code:
adb reboot edl
Then press Enter key. (To enter EDL mode)
On Phone:
12- You will only see a black screen on your phone. (This is normal, but your phone will be connected to your PC)
On PC:
13- Disconnect and reconnect your Phone to PC using USB cable then make sure the drivers are installed correctly and that your PC can see your Phone. (Qualcomm HS-USB QDLoader 9008)
14- Go to C:\adb and run MiFlash application, then click “refresh”. (You should see your device in the table now)
15- Click “select” and choose “C:\adb\Unlock” folder, then click “OK”, then click “flash”. (When it says done go to next step)
On Phone:
16- Disconnect the USB cable from your Phone, then hold power button and volume down button for 15 seconds until the phone reboots into Fastboot mode.
17- Make sure you see Fastboot mode on your phone screen. (With big green START on top)
On PC:
18- Reconnect your Phone to PC using USB cable then make sure google drivers installed correctly and that your PC can see your Phone. (Android Bootloader Interface)
19- In CMD type:
Code:
fastboot devices
Then press Enter key. (If you can see a Device ID, then continue to next step, if not then recheck your driver setup)
20- In CMD type:
Code:
fastboot flashing unlock
Then press Enter key. (This will unlock the bootloader, if you see an error make sure that your model is supported)
21- In CMD type:
Code:
fastboot erase userdata
Then press Enter key. (This will wipe userdata “Factory Reset”)
22- In CMD type:
Code:
fastboot getvar current-slot
Then press Enter key. (This will show you which slot you’re currently using, note it down)
23- In CMD type:
Code:
fastboot boot twrp.img
Then press Enter key. (This will boot TWRP, if it doesn’t work the first time, then force reboot your phone and repeat steps 16-21, you can skip step 20-22 if you already performed them)
On Phone:
24- Make sure TWRP is booted on your phone.
On PC:
25- In CMD type:
Code:
adb pull /dev/block/bootdevice/by-name/boot_a stock_boot_a.img
Then press Enter key. (This will copy the stock boot_a.img into your current directory)
26- In CMD type:
Code:
adb pull /dev/block/bootdevice/by-name/boot_b stock_boot_b.img
Then press Enter key. (This will copy the stock boot_b.img into your current directory)
On Phone:
27- In TWRP, go to Reboot, then system.
28- Download and install Magisk Manager from here. (Once the phone is booted correctly)
On PC:
29- In CMD type:
Code:
adb push stock_boot_X.img /sdcard/Download
Then press Enter key. Change ‘X’ to your current slot from step 22, mine was ‘stock_boot_a.img’. (This will copy your stock boot.img to your phone’s Downloads directory)
On Phone:
30- Run Magisk Manager, tap on the first INSTALL button on the top right, when it asks you to Install Magisk tap INSTALL, then tap on Select and Patch a File, and choose your stock_boot_X.img from ‘Download’ directory. When it’s done it will create a new file in your ‘Download’ directory named magisk_patch.img. (Don’t tap Reboot, just tap back and close the App)
On PC:
31- In CMD type:
Code:
adb pull /sdcard/Download/magisk_patched.img
Then press Enter key. (This will copy the patched boot.img to your current ‘adb’ directory)
32- In CMD type:
Code:
adb reboot bootloader
Then press Enter key. (To enter Fastboot mode)
33- In CMD type:
Code:
fastboot flash boot_x magisk_patched.img
Then press Enter key. Change ‘X’ to your current slot from step 22, mine was ‘boot_a’. (This will flash Magisk to your boot)
34- In CMD type:
Code:
fastboot reboot
Then press Enter key. (This will reboot your phone)
On Phone:
35- Run Magisk Manager, check if Magisk is installed and you have two green ticks on the left.
Congratulations! Now you have successfully rooted your Black Shark 3 Pro !
Fingerprint Calibration Tutorial (This is needed if the fingerprint sensor is stopped working)
1- Dial this from your phone
Code:
*#*#466349#*#*
This will take you to the fingerprint calibration page.
2- Tap on 售后校准, then you will be ask you to add the FLASH FLA.
3- Now tap START, and then immediately press your thumb on the fingerprint scanner area, keep you finger pressed until the step is completed.
4- Now it will ask you to add the black FLAT. (This means you have to wear a 'black' cloth on your thumb or a black glove before pressing your thumb on the fingerprint scanner, then hold your thumb on the fingerprint scanner area until the calibration is complete.)
5- When done successfully, reboot your device then try to add your fingerprints.
Full OTA Factory Image for Black Shark 3 Pro Global “MBU-H0" - Fix most phone's issues and restore it to factory state. This also fixes OTA updating issues.
1- Download this zip file MOBS2005121OS00MP1.
2- Rename km_update.zip to update.zip and move it to “ota” directory in your phone.
3- Dial this from your phone
Code:
*#*#1027#*#*
Then press "LOCAL UPDATE" and start updating your device. (You might need to do this twice)
4- Update your device to the latest version from the settings.
Special thanks to:
@John Eveline for the Bootloader Unlocking Tools.
@wzsx150 for Black Shark 3 Pro TWRP.
@topjohnwu for Magisk.
@Snoop05 for ADB Installer Code.
PS: I put a lot of time and effort in making this guide, if you want to copy it to somewhere else, then at least give credit!
miflash keep says no fastboot
cant recognize my phone
rowihel2012 said:
miflash keep says no fastboot
cant recognize my phone
Click to expand...
Click to collapse
Please redownload it, it should work fine now.
KM7 said:
Please redownload it, it should work fine now.
Click to expand...
Click to collapse
Ok thanks my friend
KM7 said:
Please redownload it, it should work fine now.
Click to expand...
Click to collapse
same problem
no fastboot
all drivers installed
rowihel2012 said:
same problem
no fastboot
all drivers installed
Click to expand...
Click to collapse
Try downloading it again, sorry for this a file was misplaced. Fixed now.
KM7 said:
Try downloading it again, sorry for this a file was misplaced. Fixed now.
Click to expand...
Click to collapse
sorry bro
no fastboot
it cant detect my phone
same problem
when i try to unlock the bootloader
i got an error : the write timed out
rowihel2012 said:
sorry bro
no fastboot
it cant detect my phone
same problem
Click to expand...
Click to collapse
Make sure the drivers are installed correctly and reboot your PC. I've just tried it and everything work just fine on my PC.
stark7i said:
when i try to unlock the bootloader
i got an error : the write timed out
Click to expand...
Click to collapse
You mean in MiFlash or Fastboot? please specify which step # you are stuck in.
KM7 said:
You mean in MiFlash or Fastboot? please specify which step # you are stuck in.
Click to expand...
Click to collapse
i am stuck at step 13. the miflash cant find my phone. i have re-downloaded everything and still doesnt work. any suggestions?
appless said:
i am stuck at step 13. the miflash cant find my phone. i have re-downloaded everything and still doesnt work. any suggestions?
Click to expand...
Click to collapse
Make sure your drivers are installed correctly as shown above. When in edl mode the drivers are different than fastboot. Try reinstall the application with right click and ‘run as administrator’.
Do you know how to relock the bootloader?
KM7 said:
You mean in MiFlash or Fastboot? please specify which step # you are stuck in.
Click to expand...
Click to collapse
its was in the miflash but it works fine now i have changed my usb cable to an original one and it works fine , i have successfully rooted my BS3 with TWRP thanks alot
KM7 said:
Make sure your drivers are installed correctly as shown above. When in edl mode the drivers are different than fastboot. Try reinstall the application with right click and ‘run as administrator’.
Click to expand...
Click to collapse
still a no go for me. i have reinstalled every driver and still doesnt work. nothing is showing up on miflash. the pc made the sound when i connected but still nothing. my pc sees the device but the miflash cant. any suggestions?
appless said:
still a no go for me. i have reinstalled every driver and still doesnt work. nothing is showing up on miflash. the pc made the sound when i connected but still nothing. my pc sees the device but the miflash cant. any suggestions?
Click to expand...
Click to collapse
Use your original usb cable from blackshark. Mine works and use other cable wont work..
chaict said:
Use your original usb cable from blackshark. Mine works and use other cable wont work..
Click to expand...
Click to collapse
using the original cable still doesnt work. now its just saying no fastboot.
stark7i said:
its was in the miflash but it works fine now i have changed my usb cable to an original one and it works fine , i have successfully rooted my BS3 with TWRP thanks alot
Click to expand...
Click to collapse
Glad that it worked for you, enjoy.
appless said:
using the original cable still doesnt work. now its just saying no fastboot.
Click to expand...
Click to collapse
It seems that there is something wrong with the drivers, or maybe the adb installation. Try to find other fastboot.exe and adb.exe then delete all duplicates except for "C:\adb", and don't forget to restart your PC.
jekz_07 said:
Do you know how to relock the bootloader?
Click to expand...
Click to collapse
This should do it but, I'm not sure if this is going to work on a rooted device.
Code:
fastboot flashing lock_critical
fastboot flashing lock
Reboot Your Device Into Recovery Mode
There are multiple ways to reboot an Android device into recovery mode. But after the latest OneUI 3.0 update, Samsung does not allow booting into recovery without connecting your phone to a PC with a USB-C cable. Here's a solution to easily reboot to recovery.
The steps mentioned can be applied to boot into both the stock recovery as well as a custom recovery if you have one installed.
Reboot to recovery without root access and without connecting your phone to Laptop/Pc.
Download & Install LADB - Local ADB shell from playstore or download it directly from here.
Open Settings > About Phone and tap on the “Build number” field 7 times. This will enable “Developer Options.”
Go to Settings > System > Developer Options and enable “USB debugging” and “Wireless debugging.”
Open the LADB app. It will show a “Pairing information” dialog.
Open the recent apps screen. Press and hold on the app’s icon and tap “Split Screen” to open LADB in split-screen multitasking view.
On the bottom half, open Settings. Go to System > Developer Options > Wireless debugging. Tap on “Pair device with pairing code.” You’ll see a “Pair with device” dialog pop-up.
Copy the 6 digit “Wi-Fi pairing code” and paste it into the “pairing code” box in LADB. Copy the 5 digit port number from the IP address (the 5 numbers after the colon) and paste it into the “Port” box in LADB.
Hit “OKAY” in LADB and you should hopefully see text that says "Hello World”
Enter "reboot recovery"
And done now your phone will automatically reboot to recovery.
Note :
You can even try out different adb commands like deblooting system apps, allow permissions to apps like macdriod, system ui turner, etc and many more other adb commons without root and without a PC. (tested on Galaxy M30s)
Thanks to the developer of LADB
For downloads and other instructions : Click here
Reserved..
thanks .. good tut and very useful
Power off, then hold volume up and bixby button till recovery comes up. Works without a pc or cable.
realbbb
Moldly Going
realbbb said:
Power off, then hold volume up and bixby button till recovery comes up. Works without a pc or cable.
realbbb
Moldly Going
Click to expand...
Click to collapse
It's for users without root and pc
razs.originals said:
It's for users without root and pc
Click to expand...
Click to collapse
Power off, then hold volume up and bixby button till recovery comes up works for root, no-root, pc, or no-pc. It does not matter what version of OneUI.
realbbb
Purely Board
realbbb said:
Power off, then hold volume up and bixby button till recovery comes up works for root, no-root, pc, or no-pc. It does not matter what version of OneUI.
realbbb
Purely Board
Click to expand...
Click to collapse
Okay it might be working that way for you but many users reported that without connecting USB they aren't able to boot into recovery
recovery mode in android 11 one ui 3.1
Guys anybody know that how to go recovery mode in android 11 ( one ui 3.1 )
r2.community.samsung.com
Will this let me unlock bootloader?