Hello everybody,
My phone had some weird glitches, factory reset didn't work, and the capacative buttons didn't work anymore, and I had to restart the play store to install the apk after it downloaded the app. I made a new User, the buttons worked again and I could normally install apps. But it was a temporary fix, and as I couldn't factory reset I decided to unlock my bootloader because that resets your phone. So what I did is:
1. I installed all the proper drivers
2. I opened an commandprompt in the adb folder
3. I typed adb devices, it said unauthorized, I authorized it on my phone, and it said that it was authorized after that.
4. I typed adb reboot bootloader
5. I waited untill it went into fastboot mode and typed fastboot oem unlock (I had the function to unlock the bootloader enabled in developer options).
My phone rebooted after this, now it only shows the OnePlus logo and powered by android, it doesn't boot further. I can't return the phone as I bought it second hand. When I connect the phone to the laptop that I used for it (The usb cable was connected directly to the motherboard, incase that matters and it was an original 4 pin samsung cable), it recognizes it as an Android device, so I think it's a soft brick.
How to fix this? Thanks in advance.
-Oczosinkoo
Hi !
You can try this tutorial
https://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
Good luck !
Related
So here's my major problem. I factory reset my N5 for my dad to use since I got a 1+1. It was rooted so i went into the settings for supersu and hit full un-root. Well that just broke everything and when I try to boot, I get a bootloop. So at this point i'm like, okay. I've fixed this before. My process. power off>fastboot>recovery>recovery settings>wipe cache/partition>done>factory reset>done.>reboot. Still get bootloop so I thought, okay ****. Flash a factory image and start a-new. I start up fastboot, and plug the phone into computer(Win7 32-bit) and do all this jazz. I realize i factory reset and wiped it so usb debugging won't be checked, so of course my computer doesn't list the device. ****. I check Device Manager and the Android setting shows up so I see it has the "ADB Bootloader Interface" as the driver. Kinda weird since I thought I used "ADB Composite Interface" last time. But my Nexus must be showing up at least in the drivers. So essentially, here's the compounded issues.
1. Bootloop
2. Can't boot so no USB debugging is checked
3 .Can't flash a stock image if device doesn't show up on computer for fastboot stuff.
4. Drivers are all messed up. I got them directly from google too.
5. ****.
I think I'm screwed on this unless I can somehow enable USB debugging from fastboot without the device itself being recognized, or something. Pls help.
My dad thinks i'm a failure now.
You don't need USB debugging for fastboot. It might be a driver issue if fastboot doesn't see it. Maybe try installing them again.
Sent from my Nexus 5 using XDA Premium App
Download some program to wipe all android drivers from the system. Restart the computer. Boot the device to bootloader. Connect the device to the PC. Go to device manager. Manually update those drivers. The drivers are the same for fastboot or adb, it's just that you need to feed Windows the same drivers twice: one when device is in bootloader, another when the device has adbd (adb daemon/server) running. Adbd doesn't run when the device is in bootloader - it's an Android thing.
a maguro wrote this.
Hi all,
My HTC One Mini crashed one month after warranty (Boo!). I can get to the FASTBOOT and BOOTLOADER screen and select options. However, the Factory reset and recovery just cause a vibration and get be back to FASTBOOT menu. The phone is *** LOCKED ***.
After a few false starts on linux and mac machines, I've installed WinDroid Toolkit v3.1 on Windows 7. I have gotten the Token ID and used it to get an Unlock_code.bin via email from the HTC developers website (Cannot link as newb). However, when I follow the instructions in WinDroid it recommends that newer devices require "Enable OEM Unlock" to be set:
I cannot do this now. I continue but when it says a menu will appear on the phone, the menu does not and the phone remains in *** LOCKED *** state. I tried continuing with step 2 "Flashing a TWRP" but it does nothing.
TL;DR Am I screwed with having previously unlocked OEM on my HTC One Mini, now that it is soft-bricked?
I'm not that good at this stuff, but managed to get mine unlocked and a recovery on it via this link
sadly mine still has a problem in that it's now stuck in a boot loop, so don't use Oneclickroot as I did in my post here
hopefully you will get yours to work ok, but when you get to instruction 17 you may find that HTC website is quite fussy with the code you copy/paste
when you copy the Identifier block into Notepad or whatever, ensure you don't get any leading blank spaces before you submit it to HTC.
this excerpt from mine had blank spaces where I have inserted red X's, but it worked with them removed and HTC then emailed me the Unlock_code.bin file
XX<<<< Identifier Token Start >>>>
XX36ADF279412BE14D5002935236B24913
XXetc
XXetc
XX<<<<< Identifier Token End >>>>>
I hope this is of some use mate
---------- Post added at 02:39 PM ---------- Previous post was at 02:26 PM ----------
sorry,
lost the plot on my first reply and forget about the OEM unlock bit ...
to get that OEM unlock bit you would normally
first Enable Developer Modeon your phone by Launching the Settings Application -
Scroll Down and Tap on About Phone(or About Device) - Locate the Build Number Section - Tap on the Build Number Option 7 Times -
Go Back to the Main Settings Page - Scroll Down and Tap on Developer Options and it's found there
but given that you are in is bad a place as me in that we cannot get a bootup, I'm afraid I can't offer any more info,
but it's worth knowing anyway in case you do get booted up
Hi, i have the same issue, but a little different.
My phone was in a box for like 2 months, and then i decide to turn it on again, and i faced the same problem as the OP, but my One Mini is UNLOCKED, and i can't lock it again because i get an error in ADB. I try to enter on recovery (and flashed three differents recoveries without sucess), and reboot in bootloader, then try to factory reset, and reboot bootloader again. It don't do anything, only turn on when i plug the usb and enter in bootloader but no more than that. i've try to flash a RUU too, but it give me the error 171. i tried too the method with the rubber band pressing the power button to cause a reboot loop and get enough charge to launch the system but nothing, i don't see any results. I'm one step closer to give up, please help, i tried everything and nothing has worked for me. If need more information don't doubt on asking me. I really appreciate any help you can provide.
I'll try mate ... but perhaps you are asking for help from the wrong guy! - firstly I have to say mine is still in a very bad place! -
I managed to get a permanent TWRP on it, installed a lovely rom named InsertCoin on it, rebooted, and all seemed fine, but then the battery drained rapidly and it would not charge - that issue is ongoing and I'm spending ages on it just now..
Firstly can you confirm that you can enter Bootloader and select Fastboot, and that your phone is then recognised by your PC?
ie: let me know what happens when you press power and vol down together, select fasboot, goto PC, run ADB, cable phone to PC,
then issue the command ADB devices
can you also upload a photo of your bootloader screen
carkev said:
I'll try mate ... but perhaps you are asking for help from the wrong guy! - firstly I have to say mine is still in a very bad place! -
I managed to get a permanent TWRP on it, installed a lovely rom named InsertCoin on it, rebooted, and all seemed fine, but then the battery drained rapidly and it would not charge - that issue is ongoing and I'm spending ages on it just now..
Firstly can you confirm that you can enter Bootloader and select Fastboot, and that your phone is then recognised by your PC?
ie: let me know what happens when you press power and vol down together, select fasboot, goto PC, run ADB, cable phone to PC,
then issue the command ADB devices
can you also upload a photo of your bootloader screen
Click to expand...
Click to collapse
i don't need to press vol down and power together, the phone enter in bootloader once you plug the usb cable. it do that alone.
This is what i get
C:\adb>adb devices
List of devices attached
C:\adb>
the phone is recognized by HTC Sync manager but i can't see it in ADB.
a few things things jump out at me ...
1. from your photo the screen is shattered! - even though I don't like being beaten by phones I would scrap it
the repair would cost more than you can get one from ebay for - about £40.00
2. "abd devices" should return you something like ... "List of devices attached sh3d7h3dj631f6a7" - when it doesn't it show a device number it's usually your drivers
3. you may think that's not it since you say that it is recognised by HTC Sync when on your PC, but I had read that HTC sync is unreliable and that the drivers are not the best
the one's I used were HTC-Mobile-USB Driver-v4.17.0.001.exe but I can't remember where I got them and will upload them later today and send you a link.
(also, it pays to plug your usb cable into a rear port on your PC when doing this kind of work as front are not as reliable)
4. your Hboot is shown as 2.22 -this also can be a problem for TWRP see this link
5. the download link he has is broken, so get any TWRP above 2.7 from their website here
carkev said:
a few things things jump out at me ...
1. from your photo the screen is shattered! - even though I don't like being beaten by phones I would scrap it
the repair would cost more than you can get one from ebay for - about £40.00
Click to expand...
Click to collapse
Hahaha, i know, i have the replacement here, i'll change it once i solve this problem.
carkev said:
2. "abd devices" should return you something like ... "List of devices attached sh3d7h3dj631f6a7" - when it doesn't it show a device number it's usually your drivers
3. you may think that's not it since you say that it is recognised by HTC Sync when on your PC, but I had read that HTC sync is unreliable and that the drivers are not the best
the one's I used were HTC-Mobile-USB Driver-v4.17.0.001.exe but I can't remember where I got them and will upload them later today and send you a link.
(also, it pays to plug your usb cable into a rear port on your PC when doing this kind of work as front are not as reliable)
4. your Hboot is shown as 2.22 -this also can be a problem for TWRP see this link
5. the download link he has is broken, so get any TWRP above 2.7 from their website here
Click to expand...
Click to collapse
2. I will leave you down here exactly what i get when i type "adb devices" (with an attached image)
3. i have installed the latest HTC drivers, and i tried connecting my phone to front an rear usb ports, both of them. No results.
4. Down here i'll leave you an attached image of what i get when i try to install a recovery by typing "fastboot flash recovery recovery.img" (i changed the name to recovery.img of course) and the phone seems installing the recovery in fastboot but it gave me that error in adb and when i try to enter in recovery it reboots on bootloader.
your first image does not 'see' your device mate, so there is no point in trying a flash of anything
until you get a response from "adb devices" that shows a device number you have no chance of getting anywhere!
I am quite certain that the problem MUST be with your drivers
my advice would be to uninstall the HTC Sync and clean out any drivers on your PC and to install the drivers and flash the TWRP I mentioned earlier
sorry I didn't upload earlier as I've been very busy indeed - they are now on my Google Drive ... links here .... and here
carkev said:
your first image does not 'see' your device mate, so there is no point in trying a flash of anything
until you get a response from "adb devices" that shows a device number you have no chance of getting anywhere!
I am quite certain that the problem MUST be with your drivers
my advice would be to uninstall the HTC Sync and clean out any drivers on your PC and to install the drivers and flash the TWRP I mentioned earlier
sorry I didn't upload earlier as I've been very busy indeed - they are now on my Google Drive ... links here .... and here
Click to expand...
Click to collapse
Ok, don't worry mate, i'll try that and then i'll tell you.
Thanks for taking your time helping me.
EDIT: adb still seeing nothing with that drivers
Little Snevil said:
Ok, don't worry mate, i'll try that and then i'll tell you.
Thanks for taking your time helping me.
EDIT: adb still seeing nothing with that drivers
Click to expand...
Click to collapse
Hello guys, I've been following this thread and I'm having same issue. Adb does not sees my phone.
Fastboot does, but when I run ruu , it disconnects and give error 171
Tried usb 2 instead of 3.nothing.
I also think it's the drivers, but I can't seem to find the correct one for this phone. Any help is appreciated
my phone only starts in bootloader it have s-on and i cant use the toolkit cause usb debugging isnt active
adb writes waiting for device
can anyone help me?
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.
Hi everyone,
A couple of days ago I rooted my Op6 and then decide to flash No limits rom via recovery (blu spark), as I was used to do with my last android phone, the Samsung Galaxy Note II.
Unfortunately I missed something and now it is stuck in the bootloader screen. Nothing works from the phone and I couldn’t revive it. I use a Mac but I tried all tools that are adviced here on XDA with my friend’s Sony Vaio but without success.
I managed to update drivers but I cannot run a flash-all.bat and I cannot use MSMdownload tool.
How can I do? Thanks to anyone who will manage to help me!!
EDIT: Sorry, just noticed you say you cant use the MSM tool. This one worked for me.
You could try this
https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3903272
Worked for me.
Check the guide about unbricking and if You are unable to use flash-all.bat so you Have to flash commands One by One. It's worked for me a few of months ago.
It doesn’t work either that way. I updated my drivers, but no computer is recognizing the phone.
I tried from changing usb cable or port to changing computer, to change methods.
I didn’t found any solution here on XDA, I tried everything!!
Make sure u use the cable included with the phone. Some cables doesn't work
Neither. I tried with the original and two others that I have.
if possible do you have windows? the flash-all.bat works for windows and is better to use(i was unable to use it normally in linux). What happens when you show flash.bat?
I tried Mac and Windows. On Windows it always shows in terminal "waiting for any device", even if I uploaded the drivers and made everything possible.
Did you put your OP6 into fastboot mode in correct way? I mean you might be doing the wrong procedure when entering fastboot mode.
It happened to me for the first time, I came from Samsung and I thought the phone needs to be stayed on the fastboot menu screen just like Samsung but no.
You need to turn it off and reboot it while pressing home and vol down button simultaneously until the PC recognize.
Good luck unbricking~
I always powered it on via power+volume up before connecting to the usb cable, because connecting it while powered off always resulted to power it on automatically on bootloader screen
Hi, I was trying to revert back to realme UI stock from Pixel Experience ROM on my Realme 5i device(RMX 2030 EX). So, first I tried to install stock recovery through Orange fox. But after installing the recovery, my phone got bricked and now it's not even being detected by the pc nor I can access fastboot mode. As PC is not detecting my phone, I can't use Realme Flash tool or cmd to change my recovery. What can I do? Please if you know, give me a fix. I would be so grateful to you. Thanks for your time.
Here are some methods that might work for you.
How to Access an Android Phone with a Broken Screen
Dealing with a broken screen on your Android phone is a hassle. Although phone screens are pretty tough, one nasty drop can shatter them completely. Given that most people have a lot of irreplaceable content on their phones, it is
www.alphr.com
@Aranya Kishor Das
My POV: If on Android device side neither adbd ( requires USB Debugging got enabled ) nor fastbootd ( requires OEM unlock got enabled ) is accessible although the device's matching OEM USB driver got installed on Windows computer, then it's recommended to take phone to authorized service center and let them try to fix it.