Hi I'm new to all this I unlocked my boot loader which took ages to do and now I can't seem to flash TWRP I keep getting an error message from my command page saying error cannot load twrp.........img. I am trying to do this so I can install the miui 12 as I really like the look of it. Any help would be greatly appreciated as I'm a complete newbie to all this. Thank you.
Did you keep all your adb-files keep in one folder in the root of your PC? Here are my files, you can copy them into C:/ https://drive.google.com/file/d/1SQB8TVIuc4aCq8PE-62ggm451xey6DC0/view?usp=sharing
Maybe, they will help you. Important: In developer options you have to activate USB-Debigging and OEM-Unlock, also set a password for display lock - best is, to use the same password for your sim and display lock. Often the cables are a problem, if you can´t connect your phone to fastboot. After i changed my cable to an older S8-cable, i have had a stable connection.
If your phone is connected after setting USB-Debugging you must accept it on the phone. Tick also, that it remember this PC.
Wish you good luck.
Related
Basically what had happened was I was out on Friday night, drunkenly gave my phone to my friend to keep safe, and then totally forget about it. Fast forward to me panicking and immediately setting a password lock using Android Device Manager. For some reason when setting a password remotely from your PC it can be as long as you want, but when typing it in my phone there was a limit, meaning I could not get in.
Why don't you just use ADM again to reset your password and put a new one?! Well apparently they don't let you form a new password once there is one already locked on your phone. Why don't you try unlocking it via findyoursamsung?! I didn't create a samsung account when prompted to. (hindsight is 20/20)
I also tried some other third-party backup apps such as Kies3 and Samsung Watch, both of which required the phone to be unlocked to function - which is also why I can't simply just connect my phone via USB and drag the data into a folder.
This lead me to doing a ton of research and it seemed the only way to get my pictures and videos back without resetting my phone would be through those coding programs and ADB and such. I am not well versed in this area at all so I looked at a bunch of sites explaining what to do.
From my limited understanding, it came down to a few things:
- My device is a Samsung Galaxy S4, probably kit kat or jelly bean. It is neither rooted nor does it have the "USB debugging" enabled
- I have successfully installed CWM (clockwork mod) and ADB (android debugging bridge) onto my computer/phone because apparently when CWM goes into recovery mode, the debugging is automatically enabled, where I'd then be able to unlock the screen (but I don't seem to know how to input adb commands - where would I do this?!)
- I installed a few other programs that were of no use to me because I had (almost) no idea how to use them (Cygwin, Odin, JOdin3, Heimdall) in conjunction with ADB and the "Download" mode on my phone to flash CWM to be my "custom Recovery" instead of the stock recovery
- I saw there were some third party apps that would automatically (?) unlock your phone screen for you but I wasn't too keen on trusting them seeing as most of thm were outdated , so unless you guys recommend one I would rather not download those
- I think my main issue is not knowing how to simply bring up a terminal and input commands but sometimes they wouldn't even recognize my device (probably because USB debugging is disabled)
I have been infront of my computer for almost a whole day now trying everything and reading everything simply trying to figure out what to do. I have looked at way too many guides and could probably recite them to you. I guess the point of this is I really would prefer not to lose this data as it has a lot of sentimental value, so I'm straying away from those methods that require you to wipe your phone. If any of you know any helpful sites or guides (I probably have seen them) that explains things very formally and easy to understand, let me know, I will be forever gracious for your help.
XDA Visitor said:
Basically what had happened was I was out on Friday night, drunkenly gave my phone to my friend to keep safe, and then totally forget about it. Fast forward to me panicking and immediately setting a password lock using Android Device Manager. For some reason when setting a password remotely from your PC it can be as long as you want, but when typing it in my phone there was a limit, meaning I could not get in.
Why don't you just use ADM again to reset your password and put a new one?! Well apparently they don't let you form a new password once there is one already locked on your phone. Why don't you try unlocking it via findyoursamsung?! I didn't create a samsung account when prompted to. (hindsight is 20/20)
I also tried some other third-party backup apps such as Kies3 and Samsung Watch, both of which required the phone to be unlocked to function - which is also why I can't simply just connect my phone via USB and drag the data into a folder.
This lead me to doing a ton of research and it seemed the only way to get my pictures and videos back without resetting my phone would be through those coding programs and ADB and such. I am not well versed in this area at all so I looked at a bunch of sites explaining what to do.
From my limited understanding, it came down to a few things:
- My device is a Samsung Galaxy S4, probably kit kat or jelly bean. It is neither rooted nor does it have the "USB debugging" enabled
- I have successfully installed CWM (clockwork mod) and ADB (android debugging bridge) onto my computer/phone because apparently when CWM goes into recovery mode, the debugging is automatically enabled, where I'd then be able to unlock the screen (but I don't seem to know how to input adb commands - where would I do this?!)
- I installed a few other programs that were of no use to me because I had (almost) no idea how to use them (Cygwin, Odin, JOdin3, Heimdall) in conjunction with ADB and the "Download" mode on my phone to flash CWM to be my "custom Recovery" instead of the stock recovery
- I saw there were some third party apps that would automatically (?) unlock your phone screen for you but I wasn't too keen on trusting them seeing as most of thm were outdated , so unless you guys recommend one I would rather not download those
- I think my main issue is not knowing how to simply bring up a terminal and input commands but sometimes they wouldn't even recognize my device (probably because USB debugging is disabled)
I have been infront of my computer for almost a whole day now trying everything and reading everything simply trying to figure out what to do. I have looked at way too many guides and could probably recite them to you. I guess the point of this is I really would prefer not to lose this data as it has a lot of sentimental value, so I'm straying away from those methods that require you to wipe your phone. If any of you know any helpful sites or guides (I probably have seen them) that explains things very formally and easy to understand, let me know, I will be forever gracious for your help.
Click to expand...
Click to collapse
Hello, and welcome to XDA!
A bit of a doozy....
This thread may help:
> Samsung Galaxy S 4 i9500, i9505, i9505G, i9506 > Galaxy S 4 Q&A, Help & Troubleshooting > [RESOLVED] HELP please!! Unable to unlock device locked by Google Device Manager
May need to modify solution two to use under CWM. That is, mount data via adb (or via recovery if there's an option) before issuing (the rest of) the adb commands.
By the way, here is a primer to adb:
http://www.xda-developers.com/all-in-one-guide-to-adb/
Hope this helps, and good luck!
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.
Hello,
I am hoping for some advice on how to revert my phone back to its original "factory settings" after a botched instal of GrapheneOS onto an unlocked Google Pixel 3A.
I got to the point at which I needed to Flash the Graphene Rom to the phone, but rather than installing, I received a message from Smart Screen MS edge asking if I really wanted to run as it's protecting my PC - I clicked run anyway and a blank command line window appeared for a second. Now my pc doesn't seem to be recognising the pixel 3A when I type ADB devices. My phone is currently in Fastboot mode "unlocked" and I'm hoping for some advice on what to do next. I'm total noob, so unsure how to start the process over (return the phone to it's previous state) before, maybe, trying again on a different PC.
I have since turned on my phone and Android 11 is still present and seems to work fine (however it gives me a warning on startup that the bootloader is unlocked.
Any help would be very much appreciated - thank you in advance.
Is all what happened that your phone now:
complains about "'maybe not safe bootloader unlocked".
This is just what android does when the bootloader is unlocked.
This you did before trying the flash.
If you want the warning gone simply lock it again.
However if you into the market for graphene OS then I would recomend: along with following their guide to a t to also read up here on xda about the general rooting unlocking thing a bit more so you get the overall process a bit better perhaps next time.
About windows. There are so many tools out there to help ya with disabling some of it's spying, turning off smartscreen, auto - uploads of all your data to M$oft, etc etc.
It's not hard to find.
Thanks for the response - I think I've worked out what is going on.
Typing ADB devices, my PC recognises the phone until I put it into fastboot mode - typing adb devices when in fastboot comes back with nothing and therefore when I try to flash, I assume the devices aren't talking to each other.
Not sure if there's a work around or whether it's a case of finding a new PC to try it on?
Thanks again.
Ignore
deroller said:
Thanks for the response - I think I've worked out what is going on.
Typing ADB devices, my PC recognises the phone until I put it into fastboot mode - typing adb devices when in fastboot comes back with nothing and therefore when I try to flash, I assume the devices aren't talking to each other.
Not sure if there's a work around or whether it's a case of finding a new PC to try it on?
Thanks again.
Click to expand...
Click to collapse
try another USB port first; use USB 2.0 if available! Reinstall google ADB drivers, make sure to use latest!
If above will not help:
on your computer: open device manager; on your phone: put your phone into fastboot; connect your phone to the computer WHILE keeping an eye on device manager; as soon as you'll connect your phone new device will appear in device manager ("unknown device" most likely but it might be some "android device" or "ADB device" too); right click it —> update driver —> automatic driver update worked in most cases for me, if not, go manual way and select google's "android fastboot device" (or something like that, can't remember actual name of the device); after driver install confirmation you should be good to go
Tamsta_T said:
try another USB port first; use USB 2.0 if available! Reinstall google ADB drivers, make sure to use latest!
If above will not help:
on your computer: open device manager; on your phone: put your phone into fastboot; connect your phone to the computer WHILE keeping an eye on device manager; as soon as you'll connect your phone new device will appear in device manager ("unknown device" most likely but it might be some "android device" or "ADB device" too); right click it —> update driver —> automatic driver update worked in most cases for me, if not, go manual way and select google's "android fastboot device" (or something like that, can't remember actual name of the device); after driver install confirmation you should be good to go
Click to expand...
Click to collapse
Hey there,
This is brilliant - thanks for all the advice. Having this support is helping me gain the confidence to learn more, research more, and then give it a go.
All the best.
deroller said:
Thanks for the response - I think I've worked out what is going on.
Typing ADB devices, my PC recognises the phone until I put it into fastboot mode - typing adb devices when in fastboot comes back with nothing and therefore when I try to flash, I assume the devices aren't talking to each other.
Not sure if there's a work around or whether it's a case of finding a new PC to try it on?
Thanks again.
Click to expand...
Click to collapse
thats if I am not wrongly remembering my experience:
because now your phone is in fastboot mode thus it won't show up with that command anymore.
Try: 'fastboot devices'
I imagine you put it into fastboot through: 'reboot fastboot' when you where in adb?
When in fastboot you can go on and flash the recovery and such.
Are you still in need of help here?
Hey, thanks for the clarification - been away and so haven't implemented all suggestions, yet.
I typed "adb reboot booloader" which I assumed put it into fastboot mode and then unlocked it using "fastboot flashing unlock".
I tried fastboot devices but the PC still doesn't see the phone. I'm going to try the update usb driver suggested by Tamsta_T and see how it goes.
Thanks for your help.
Hi everyone, I have a VIvo Y81i (1812). and i forget it's screen lock password.
Issued in format via software that i never enabled it's adb ever nor it's attached to any computer before.So it's only detecting in computers as MTP device only none other than that. Not as Ports and LTP device.
What i have tried so far:
Tried to format with recovery mode which still asked for password to unlock before format.
Miracle tool to format phone but after setup it keep saying the port be occupied even when i tried virtual port software.
FRP by pass tool which need port number of device it's not gonna work because my phone never detect after installed lots of adb,Vcom drivers.
Now i need to unlock my phone but over the week of trying and googling i end up here to get some help from XDA forums.
Please guys help me out in this issue.
Thanks