I've been trying to find a way to disable fastboot, and I've scoured the internet and my device settings to try to find a way to disable the fastboot. My device is an iDeaUSA CT702 - MID A777 running Android ICS 4.0.3. It's a 7" Tablet, and not one of those big company devices, so answers are difficult to find. I can only tell you where the fastboot setting is NOT in:
1. "Settings - Power", because there is not Power settings.
2. "Settings - Applications"
3. "Settings - Developer Options" Since it's ICS, Developer Options are NOT under Applications.
I think there should be a way to disable fastboot using Terminal, or maybe ADB. Could anyone see if it's possible?
After installing the latest update of Marshmallow (6.0.1) on my Nexus 7 (2013 Edition) the touch functionality got totally broken. I am not able to do nothing using the touchscreen so I can not access UI to enable developer options and then allow USB connection. Is there any way I can allow this option using a command line? I have tried everything, I restarted to bootloader , I went to recovery mode and delete cache and also reset to factory settings. And the touch functionality keeps broken. I need to remove marshmallow and go to a previous version but for doing that I need to be able to allow the usb access to my nexus without using the UI.
I will appreciate any thought.
Thanks!!
arkdna said:
After installing the latest update of Marshmallow (6.0.1) on my Nexus 7 (2013 Edition) the touch functionality got totally broken. I am not able to do nothing using the touchscreen so I can not access UI to enable developer options and then allow USB connection. Is there any way I can allow this option using a command line? I have tried everything, I restarted to bootloader , I went to recovery mode and delete cache and also reset to factory settings. And the touch functionality keeps broken. I need to remove marshmallow and go to a previous version but for doing that I need to be able to allow the usb access to my nexus without using the UI.
I will appreciate any thought.
Thanks!!
Click to expand...
Click to collapse
install the latest twrp via bootloader, go to recovery, twrp should have usb access you may need to plug in to your comp then in twrp reboot to recovery and your pc should show your device. as for enabling it via command IDK
also search xda "how to control device with broken screen" may help
I have a Samsung Galaxy A5 2017 (SM-A520F/a5y17lte/android 8.0.0 oreo) but I cannot install TWRP on it. I tried many methods but its not letting me to do it:
-unlock bootloader /failed
-OEM unlock in dev options /hidden and cannot access/failed
-flash stock rom to unlock OEM /failed
-root phone with adb /no fastboot access /failed
-root phone with Odin /failed
-flashing TWRP with adb /no fastboot access/failed
-flashing twrp with odin /"only official binaries are allowed to be flashed" error message in download mode /failed
-uding heimdall (wtf is this program ive never heard it b4) /failed
Anyone got solution to install TWRP ? So i can flash to android 9 and also root my phone. Thank you if you suggest any solution that actually works.
ItsSuperPlayz said:
I have a Samsung Galaxy A5 2017 (SM-A520F/a5y17lte/android 8.0.0 oreo) but I cannot install TWRP on it. I tried many methods but its not letting me to do it:
-unlock bootloader /failed
-OEM unlock in dev options /hidden and cannot access/failed
-flash stock rom to unlock OEM /failed
-root phone with adb /no fastboot access /failed
-root phone with Odin /failed
-flashing TWRP with adb /no fastboot access/failed
-flashing twrp with odin /"only official binaries are allowed to be flashed" error message in download mode /failed
-uding heimdall (wtf is this program ive never heard it b4) /failed
Anyone got solution to install TWRP ? So i can flash to android 9 and also root my phone. Thank you if you suggest any solution that actually works.
Click to expand...
Click to collapse
Hello and good afternoon, @ItsSuperPlayz
Welcome to XDA. I hope you'll always get the support you require.
However, prior to your next posting please read the guidances that are stuck on top of every forum like
[ATTN] : Read before posting - Any questions posted here will be MOVED or CLOSED
Please read the below before posting. Any questions not development related will be moved or closed. Forum Searching | Posting | The Basics: (Make sure you've read them before starting a new thread) Forum Rules Forum Search Google Forum...
forum.xda-developers.com
and the others. I've moved your thread to Android Q&A.
Thanks for your cooperation!
Regards
Oswald Boelcke
Senior Moderator
First you have to access developer mode. You have to tap several times on the build number. (Settings/about the phone) In developer mode you heve to enable oem unlocking and usb debugging. Wait for permission request on the phone for access of your PC when attached to the phone.
Next step is to unlock the bootloader.
After this you will be able to install TWRP, which finally gets you to the point where you can install a new ROM. Just follow step by step:
Install LineageOS on a5y17lte | LineageOS Wiki
wiki.lineageos.org
Of course, instead of Lineage, you can use any suitable ROM
chrysopra said:
First you have to access developer mode. You have to tap several times on the build number. (Settings/about the phone) In developer mode you heve to enable oem unlocking and usb debugging. Wait for permission request on the phone for access of your PC when attached to the phone.
Next step is to unlock the bootloader.
After this you will be able to install TWRP, which finally gets you to the point where you can install a new ROM. Just follow step by step:
Install LineageOS on a5y17lte | LineageOS Wiki
wiki.lineageos.org
Of course, instead of Lineage, you can use any suitable ROM
Click to expand...
Click to collapse
Thank you for replying but as I said above i cannot unlock bootloader in any way i tried. So maybe can u find another solution? (Note: i tried following the link u send me and its not working)
How far did you get? OEM unlocking and usb debugging successful?
When putting your phone in fastboot mode and attaching it to the pc, check with "adb devices", if your phone is properly recognised. Using windows, it´s often the drivers. On my system, I had to manually select the ADB driver, since I got no connection before.
chrysopra said:
How far did you get? OEM unlocking and usb debugging successful?
When putting your phone in fastboot mode and attaching it to the pc, check with "adb devices", if your phone is properly recognised. Using windows, it´s often the drivers. On my system, I had to manually select the ADB driver, since I got no connection before.
Click to expand...
Click to collapse
thanks for replying again
i tried to oem unlocking and usb debugging but unsucessful
furthermore my pc cant even recognise my phone when i turn on usb debugging or change the usb to media transfer protocol (mtp) mode after i flash stock firmware (it worked before i flash the firmware)
how am i gonna install anything if my pc cant even recognise my phone????
(ps: your question "how far did you get" my answer is i cant flash any mods or unlock anything. bootloader locked.)
Can you see the "developer options" in settings/system when scrolling down ? If not, then:
How to access developer options in Android
Step 1: Go to Settings > About Phone.
Step 2: Tap Software Info > Build Number.
Step 3: Tap Build Number seven times. ...
Step 4: Once developer options are activated, you will see a message that reads, You are now a developer.
Within developer options there are options to enable usb debugging and oem unlock. I recently did this on a Galaxy tab and saw..nothing.
First I had to establish a network connection to my wifi base. Weird, but this brought those wanted menu items...
For further connection, check your computer drivers. Both the manufacturers usb drivers and adb driver are necessary. While connected to a PC, check, if you´re on Windows, the device manager, if the proper driver is chosen.
chrysopra said:
Can you see the "developer options" in settings/system when scrolling down ? If not, then:
How to access developer options in Android
Step 1: Go to Settings > About Phone.
Step 2: Tap Software Info > Build Number.
Step 3: Tap Build Number seven times. ...
Step 4: Once developer options are activated, you will see a message that reads, You are now a developer.
Within developer options there are options to enable usb debugging and oem unlock. I recently did this on a Galaxy tab and saw..nothing.
First I had to establish a network connection to my wifi base. Weird, but this brought those wanted menu items...
For further connection, check your computer drivers. Both the manufacturers usb drivers and adb driver are necessary. While connected to a PC, check, if you´re on Windows, the device manager, if the proper driver is chosen.
Click to expand...
Click to collapse
I see the developer options and the usb debugging switch
But there are 2 problems
1. My pc running windows 10 cannot detect my device (like showing it as a disk so i can copy files to )
2. In developer setting there is no OEM unlock option, which is weird. I triee many solutions but cannot get acess to OEM unlock. I even tried to unlock it with ADB ut its useless since my phone cant even access fastboot mode.(download mode is considered to be fastboot but ADB wont recognise my phone)
*why are you putting so much effort replying me*
*also drivers seem to be down*
As for the drivers, you could try:
Samsung Galaxy A5 (2017) USB Driver for Windows (Official Mobile Driver)
Download the official USB Driver for Windows Computer.
gsmusbdriver.com
As for the OEM unlocking, Samsung seems to be tricky:
How to Fix Missing OEM Unlock in Developer Options on Samsung
Are you looking for the OEM Unlock in developer options but couldn't find it? Here's how to fix missing OEM unlock in developer options.
www.ytechb.com
or:
How to fix the missing OEM unlock in developer options on Samsung devices - KrispiTech
There are different methods available to fix the missing OEM unlock in developer options on Samsung devices. By using this option, you will
krispitech.com
ItsSuperPlayz said:
*why are you putting so much effort replying me*
Click to expand...
Click to collapse
Maybe I´m a reincarnation of genghis khan, trying to earn some good karma...
chrysopra said:
As for the drivers, you could try:
Samsung Galaxy A5 (2017) USB Driver for Windows (Official Mobile Driver)
Download the official USB Driver for Windows Computer.
gsmusbdriver.com
As for the OEM unlocking, Samsung seems to be tricky:
How to Fix Missing OEM Unlock in Developer Options on Samsung
Are you looking for the OEM Unlock in developer options but couldn't find it? Here's how to fix missing OEM unlock in developer options.
www.ytechb.com
or:
How to fix the missing OEM unlock in developer options on Samsung devices - KrispiTech
There are different methods available to fix the missing OEM unlock in developer options on Samsung devices. By using this option, you will
krispitech.com
Maybe I´m a reincarnation of genghis khan, trying to earn some good karma...
Click to expand...
Click to collapse
heimdall finally recognise my phone but whenever i try to flash twrp.img it says
"Only official binaries are allowed to be flashed(RECOVERY)" (the phone itself) HELP!!!!
*good karma +1*
On any other device, you would have enjoyed your new TWRP since several days. But Samsung is eager to build as many hurdles as possible, to prevent changing the original software. They invented "KnoxGuard" to "protect" the phone. In your case, it´s aprotection against it´s owner
The error message means, that your phone isn´t successfully unlocked.
Try this:
"FIXED IT!!
The time trick actually worked.
All I had to do was turn back the time by like a year, reboot, enter recovery mode, delete cache, re-enable OEM unlock, spam the update phone button, and boot into download mode!"
The following Link may also be of interest:
Prevent Prenormal KG/RMM State on Samsung Galaxy Devices (Guide)
Is the OEM unlock toggle missing on your Samsung Galaxy device? That's probably because your phone has entered Prenormal KG/RMM State. In this guide, we will show you how to prevent Prenormal KG/
www.thecustomdroid.com
chrysopra said:
On any other device, you would have enjoyed your new TWRP since several days. But Samsung is eager to build as many hurdles as possible, to prevent changing the original software. They invented "KnoxGuard" to "protect" the phone. In your case, it´s aprotection against it´s owner
The error message means, that your phone isn´t successfully unlocked.
Try this:
"FIXED IT!!
The time trick actually worked.
All I had to do was turn back the time by like a year, reboot, enter recovery mode, delete cache, re-enable OEM unlock, spam the update phone button, and boot into download mode!"
The following Link may also be of interest:
Prevent Prenormal KG/RMM State on Samsung Galaxy Devices (Guide)
Is the OEM unlock toggle missing on your Samsung Galaxy device? That's probably because your phone has entered Prenormal KG/RMM State. In this guide, we will show you how to prevent Prenormal KG/
www.thecustomdroid.com
Click to expand...
Click to collapse
Sorry to say this but the method is useless. Its never gonna work.
Perhaps this (long) Thread may be helpful:
[GUIDE][17.06.2019] RMM/KG bypass - Root/Install TWRP on Exynos Samsung after 2018
UPDATE 17.06.2019 - NEW RMM/KG bypass patch UPDATE 23.02.2019 - Pie and more Please take some time and read carefully the whole post. I am not and i won`t be responsable for anything. Disclaimer I am not responsible for bricked devices, dead...
forum.xda-developers.com
I am trying to install a custom ROM on my sons MI PAD 4.
I originally bought the tablets on aliexpress.
The current MIUI version is 9.6
The tablets are unlocked, showing unlocked on the boot screen screen with an open lock image.
After enabling developer options, the developer options menu shows, but it is empty.
Previously I never bothered with a MI account. I registered a MI account but that should not even be required as the tablets are supposedly already unlocked.
How do I enable USB debugging or get the developer options menu to be populated?
you don't need usb-debugging for fastboot