Question Bootloop after turning off developer settings - ASUS ROG Phone 5 / 5s

Hi everyone
I was just trying to get a banking app to work and turned off developer settings as it seemed to be detecting that, this worked brilliantly except that I needed to restart after making a change to the phone and I had completely forgot to turn it back on and now it's on a bootloop. Windows in device manager does detect it "Android bootloader interface" but ADB doesn't detect it when in the bootloader.
When I did have usb debugging on it was detecting the phone at this stage perfectly and nothing else has changed so I know that the ADB drivers and the cable are working, unless theres been an update since I last installed it around a year and a half ago which would fiix this.
The bootloader is also unlocked too.
Would doing a factory reset help from within the bootloader help at all?
I'm not sure how to fix this and any help would be very much appreciated.
EDIT: Fixed, I could still flash the RAW file.

Related

Help with Locked Proscan PLT-7035-PL Factory Restore.

Hello everyone and well I have to say I am at my wits end over here.
I have literally just spent hours trying to find the solution without luck. So any help will be greatly appreciated.
I am completely new to android as well and this only makes things much more worse.
I have a Proscan PLT-7035 a cheap tablet by all means and my son accidentally locked the screen under too many password attempts.
I have been trying to factory restore it only to learn this Chinese hardware apparently was not shipped with a recovery option.
This means I cannot put it under USB debugging and I cannot disable mount the mass storage device. So when I connect it to my computer I am able to access all the files but that is it. Honestly it is the biggest 4G usb stick I have ever owned.
Anyway I have tried multiple guides to root and what not as well as I tried multiple button combinations to no avail. It also seems I am able to enter recovery mode by clicking the power button + volume down after shutting the device.
You can hear the sounds in windows of a device being connected and disconnected. There was also an uninstalled driver when i checked Device manager. This is how I was ultimately able to install the drivers as per this guide
It now shows under Android Device as Android Composite ADB Interface.
Now I have tried using Rockchip Batch Tool but It also gets stuck on <Layer 3-3> Test Device Start.
I have tried ICS Root Unlocker and I get error :device not found.
I try adb devices and no devices are listed.
My device is clearly not being detected and I do not know if this is due to driver incompatibility or due to the fact I cannot set the device to USB debugging.
I already disabled driver signature enforcement I'm on Win8Enterprise N x64.
Now someone here was kind enough to upload these and I have absolutely no idea. How to install them or have them run.
So you all can see I've been almost everywhere and in all honesty I have no idea what to do next.
Any lleads will be Godsend. Thanks in advance.
Please let me know if this is in the wrong category. Thanks

[Completed] HELP!!! Unbrick Xperia S (bootloader problem no flashmode)

I have a Xperia S running cm 12.1 with unlocked bootloaders TWRP installed and i tried to partition my SD card [http://forum.xda-developers.com/showthread.php?t=2584759] but clearly something went wrong and now the phone wont boot. I made a lot of research and tried everything but all the guides require to be able to boot into flashmode . My phone is dead the only sign of life is a red led when its charging which after some hours of charge will shut off. When the light is off and the phone connected on PC, the PC can recognize the device on unspecified devices (QHSUSB_DLOAD). i have installed all the needed drivers from Sony, google drivers from sdk, and adb drivers(adb wont see the device and i tried everything to do so, but nothing seem to work). I got a market for android on my pc called mobogenie that when i connect the phone it detects that a phone is connected but wont see what phone.The hardware reset buttons work but its useless in the current position. Concluding, the phone is bricked and wont open in fastboot-flashboot-bootloader-TWRP, its recognized as a device but not as "Xperia s" i got all the drivers and i want to flash the original firmware (already downloaded) to fix it. A possible problem is that the partition table is destroyed and after the flash it will hopefully be restored. The problem is not on the hardware but on software. I tried to trigger the download mode with the Samsung way (USB jig, 300k ohm ) but nothing happened as expected. Every solution i found required flash mode which is not accessible at the moment and i tried lots of things to go into fastboot(ever the rubber band trick,remove the battery etc). PLEASE help i dont know what to do, please help me flash it (i already got flashtool, Emma) or anohter solution. Thanks for the help in advance. (its my first thread in the forum, i hope to post it on the right section, i posted it here because i need the assistance of the developers i guess)
Hi,
You've asked in the correct section: http://forum.xda-developers.com/xperia-s/help/how-to-unbrick-xperia-s-lt26i-tried-t3265523/
so I'll close this thread.

Broken Screen, how to get to my files? Need an android expert!

Hello everybody,
I know there are many threads with broken screens and so on, but I've been searching the internet the whole day & night and tried nearly every solution.
My Smartphone fell on the ground two days ago, I can see everything, but touch isn't working anymore.
Usually I'm rooting my phones but i didn't root my XZ5 so far (big mistake!), so I don't have a custom recovery.
I have USB Debugging activated, but I haven't connected my phone since it updated to the new firmware, so I'm getting RSA Fingerprint Message which I can't allow.
After my Z5 fell on the ground, the fingerprint didn't work so I had to restart my phone - now I'm forced to enter the key to unlock the system.
At first, I tried "Android Control" with adb, but when I connect my phone, adb says "unauthorized" - no remote control possible.
After that, I bought a OTG Cable and plugged in a mouse. This isn't working, because I have to search for a plugged-in USB device first in the settings (the phone doesn't recognize the USB device itself).
Fastboot & Flash Mode are still working.
Is there a possibility to skip RSA Fingerprint with USB debugging or deleting my lock screen? I thought of unlocking my bl and installing TWRP, but then the mobilephone would be wiped as far as I know.
Maybe someone of you knows a "temporary recovery" which can be booted from SD-Card or another way to get to my internal data..
It would be awesome, if someone could help me with this!
Many thanks in advance!
Only way i can think of are to downgrade to lollipop with flashtool without wipe.
Then the usb mouse should start to work directly if im not mistaken.
Atleast i think it was this they before mm upgrade.
Did you try to boot the phone with the mouse connected?
Skickat från min E6653 via Tapatalk
yes, unlocking would completely wipe your phone, including internal memory so it's not a solution.
Rsa key request means you cannot run any adb command right, included adb shell right?
Did you try to do an extensive google search with "broken screen rsa"?
Particularly, http://stackoverflow.com/questions/...b-rsa-key-with-broken-touch-screen-on-android
talks about rebooting in "recovery mode", so you could try to use adb commands in fastboot mode (or download mode)
bobrovsky35 said:
Hello everybody,
I know there are many threads with broken screens and so on, but I've been searching the internet the whole day & night and tried nearly every solution.
My Smartphone fell on the ground two days ago, I can see everything, but touch isn't working anymore.
Usually I'm rooting my phones but i didn't root my XZ5 so far (big mistake!), so I don't have a custom recovery.
I have USB Debugging activated, but I haven't connected my phone since it updated to the new firmware, so I'm getting RSA Fingerprint Message which I can't allow.
After my Z5 fell on the ground, the fingerprint didn't work so I had to restart my phone - now I'm forced to enter the key to unlock the system.
At first, I tried "Android Control" with adb, but when I connect my phone, adb says "unauthorized" - no remote control possible.
After that, I bought a OTG Cable and plugged in a mouse. This isn't working, because I have to search for a plugged-in USB device first in the settings (the phone doesn't recognize the USB device itself).
Fastboot & Flash Mode are still working.
Is there a possibility to skip RSA Fingerprint with USB debugging or deleting my lock screen? I thought of unlocking my bl and installing TWRP, but then the mobilephone would be wiped as far as I know.
Maybe someone of you knows a "temporary recovery" which can be booted from SD-Card or another way to get to my internal data..
It would be awesome, if someone could help me with this!
Many thanks in advance!
Click to expand...
Click to collapse
So I recovered my password from the dust and figured this is my chance to help..
Better be working..
I dropped my z3c while I was holding my newborn baby, it contained all the pictures from birth, ****ing fool I am for not backing up..
Get that short '.. to usb' - thing from the box. Use that to connect your Bluetooth mouse and tada that should work. Use it to unlock your phone and do you what you want to do.
It worked for me, hope I can help you.

(SOLVED) Custom binary blocked by FRP lock message when i try to boot my phone

Edit: It seemed as it solved itself, look in the replies for details
So i have had my gs7 rooted for a year or longer. Yesterday i rebooted my phone and got the error message "Custom binary blocked by FRP lock". Sadly, when i enter download mode and plug it into a pc with odin installed, it is not recognised. Odin does not say anything about a phone plugged in, and windows says the usb is not recognized.
What i think have caused this:
I downloaded an app that allowed me to record internal audio
I turned off developer options, and my stupid ass did not realize that is where oem unlock is located.
What i have tried:
Resetting to factory settings (from recovery mode)
Deleting cache (from recovery mode)
Using odin, but odin does not even recognize my phone
Tried using another computer with odin
tbh, looking at the other posts, i think i messed up. I dont want to send it in for repairing because i will have to pay a lot of money. I have tried sending it in for repairing a while ago. Then my problem was that i could not call with it, but they wanted me to pay the price for a new phone to repair my old phone, since i had rooted it. I did not accept it so i got my phone back, and managed to fix the issue myself. I hope i manage to fix the issue this time aswell.
There are lots of guides online on how to resolve this issue, please Google and read. Please make sure you have Samsung USB drivers installed on your pc
cooltt said:
There are lots of guides online on how to resolve this issue, please Google and read. Please make sure you have Samsung USB drivers installed on your pc
Click to expand...
Click to collapse
I have samsung usb drivers installed, and download mode has always been working and has always been recognized by odin ever since this happened. And online all i find is that i should boot into download mode and try using odin, but odin does not recognize my phone, nor does my computer.
10krlan said:
I have samsung usb drivers installed, and download mode has always been working and has always been recognized by odin ever since this happened. And online all i find is that i should boot into download mode and try using odin, but odin does not recognize my phone, nor does my computer.
Click to expand...
Click to collapse
Please pay attention to guides when messing about with your phone, OEM and Debugg are critical to being able to modify.
Look here for a solution.
https://www.mobikin.com/android-backup/computer-does-not-recognize-android-phone.html
cooltt said:
There are lots of guides online on how to resolve this issue, please Google and read. Please make sure you have Samsung USB drivers installed on your pc
Click to expand...
Click to collapse
SOLVED!
The issue fixed itself, im not sure what i did. I was suddenly able to connect my phone to odin. Just incase someone reads this with the same problem. This is what i did: installed smart switch and rebooted my computer. Uninstalled and reinstalled samsung usb drivers.
Before i did those things the issue was still there, i was ready to use smart switch, but i tried odin one last time and it worked. Now samsung pass tells me my phone is rooted, even though it is not (my root dissapeared after resetting my phone), its not that big of an issue, just thought id let you know

Updated to KB2005_11.c.11 and now USB Debugging malfunctions

I have a KB2005 that was working normally and communicating with my Windows computer when on the A11 version of OxygenOS. It was unrooted and had only the stock applications that came with the operating system. Today I installed the A12 upgrade using the Full-OTA that I downloaded from the OnePlus website (international version). I enabled USB debugging but even so, when I now connect the phone to my computer I don't get the usual message asking if I give permission for ADB. That is, "Allow USB Debugging? This computer's RSA Key Fingerprint is such and such etc. Always Allow from this computer?"
Also, in the Windows Device Manager, the device doesn't show up until I put it into bootloader mode (I have to use the volume + power because ADB commands have no effect). Having run out of solutions, I allowed the phone to install an incremental upgrade to KB2005_11_C33 but that didn't fix the problem. I toggled USB debugging off and on, re-started several times and did a factory reset but still can't use ADB commands. Fastboot commands seem to be working as expected, though. My other KB2005 that is still on A11 is not having this problem with ADB. Any idea what is the source of the problem?
I have never had that problem, so I can't tell you how to fix it.
You might want to try:
- Changing Settings>System settings>Developer options> Default USB configuration and Select USB configuration
- Settings>System settings>Back up and reset>Reset phone: either Reset all settings or Erase all data (backup your data to a PC before doing this)
When I first installed OOS 12 I had a number of problems that all went away after doing a factory reset.
Thank you, Bill. I was most curious to hear from you because I recall you mentioning you had upgraded to A12 and stayed with the stock OS so obviously it was working out for you. I tried both of those things you suggested. I was most hopeful about the factory reset but no luck. I also restarted my PC and re-installed the OnePlus drivers. That said, I haven't noticed a lot people complaining about this so maybe I'll just roll it back to A11, relock the boot loader and take another stab at it.
UPDATE: USB debugging still wasn't working after the roll-back to A11 so I toggled off USB debugging, revoked previous debugging authorizations, deleted the windows drivers, then re-installed them from the copy that is stored on the phone. After that, I toggled on USB debugging and it worked normally again. That's a clue. I'll re-try the A12 upgrade this weekend and report if it works on a 2nd attempt.
I hope it works for you now.
I restarted from scratch and this time the upgrade to A12 worked and I didn't lose the USB Debugging functionality. After installing the full-OTA for my KB2005 (version 11.c.11), I went ahead updated the firmware to KB2003_11.c.33 so I could use TWRP. Everything seems to be working as intended now. I'm happy to report that the rollback app from OnePlus worked flawlessly.

Categories

Resources