Hi,
I have faced a problem trying to unlock my bootloader.
On the Mi unlock tool I have pressed the button "unlock". after one week the time required passed, but opening the app on the PC and connecting the phone in fastboot mode anything happens! You can see attached a capture of my PC screen with the phone connected in fastboot mode.
How I can fix it?
Thanks
Is this Windows? Does the OS see the device? (Check "My Computer".) Are the correct drivers installed?
If not, click the cog wheel and install driver, then reboot.
pnin said:
Is this Windows? Does the OS see the device? (Check "My Computer".) Are the correct drivers installed?
If not, click the cog wheel and install driver, then reboot.
Click to expand...
Click to collapse
Yes, it is Windows. not in fastboot mode the computer see my phone. in fastboot mode no.on the unlock tool the refresh and unlock buttons seem to be frozen.
How I can install the driver? on the cogwheel I can see only this (picture attached)...
It is really strange, why one week ago everything was ok? same computer, same phone of course!
In my experience, it's normal to not have any button feedback when the device is in fastboot mode -- only long-press power button to shutdown.
Sorry, can't help you on the rest, never faced this myself.
This is what comes up on the cog in the version I have (just pressed check to install the "drive", before rebooting the phone into fastboot)...
It is really frustrating this.
Any piece of advice?
Hi. I know it might sound silly but have you tried a different USB port on your PC? Preferably a USB 2.0 port.
finally done!
mybe the cable not working I don't know why!
Thanks
Related
hi there.
maybe I am using wrong words but I cannot find any post similar to my subject.
I am on stock ICS but it is not working well - I wanted to downgrade, but it looks like it is not possible to downgrade on stock recovery. I know I have to change the recovery to sth else like ClockWork.
I know about fastboot way - and here my problems starts.
I have all the drivers, phone is visible in Device Manager while it is booten into Android. I can go into Fastboot mode BUT
when phone is in fastboot mode it is not visible in Windows Device Manager at all.
It is not a driver problem. There is no new device I can use the driver for.
I tried different computers. Win7 64bit and 32bit and WinXP 32bit
My phone does not show up on any of them.
I think it ia a problem with the bootloader - my current version is XXKL1 - as when I am in the fastboot mode my volume keys are not working, while they work perfectly well in recovery or in the OS.
Any ideas appreciated.
Cheers
My phone wasn't showing in w7 i had turn on usb debugging in settings -> developer options. I m not sure if this helps but might be worth a try
Sent from my Nexus S using Tapatalk
Thx gm'
It is not an issue for me to connect to Windows when I am booten into android.
Only when I am in fastboot mode the phone is not discovered by windows - and in fastboot mode thre is no USB debbuging - but thx anyway
..
vstar said:
Thx gm'
It is not an issue for me to connect to Windows when I am booten into android.
Only when I am in fastboot mode the phone is not discovered by windows - and in fastboot mode thre is no USB debbuging - but thx anyway
Click to expand...
Click to collapse
Know what u mean.
Windows finds u phone but not in recovery mode.
Download pdanet for android and this will solve ur problem buddy.
http://junefabrics.com
I just realize that what I done a while ago.
You don't need install pdanet app on ur phone as long u have drivers u might get some errors if u press not install but will work anyway.
Hope this will help.
Sent from my Nexus S using Tapatalk
XXK1 sounds like the baseband/radio to me. Granted I never actually looked in the bootloader for a model number. You sure that's not the radio?
What rom is on the phone now? Does it work? Are you rooted? If you got working phone with root you can flash custom recovery from inside the os. Boot directly into it via terminal or adb or any app that does it.
The volume buttons not working sounds odd and does worry me though
did you try to boot into bootloader/fastboot without being connected to any machine (holding vol up + power) to check if your volume keys work or not?
your issue might not be driver related, but you can always try if the test above was ok.
http://forum.xda-developers.com/showthread.php?t=1138755
best of luck
OK guys. I am on 4.0.3 stock. Works almost fine. This phone is unlocked but not rooted. So no chance for any other recovery but the stock one as far as I know. So I am not able to downgrade easily. Yes I can boot into fast boot without being attached to USB. Volume keys still not working here. But working in recovery mode no problem. GM no drivers will help if phone does not show in windows device menadzer at all. I have tried Linux approach but it looks phone is not being discovered there in fast boot mode as well. I have tried unbrick software - does not discover the phone.
And yes it says on fast boot screen boot loader : I9020XXK1
I have run out of ideas.
Downgrade would be best but how to put any recovery manager without root privileges
Sent from my Nexus S using XDA App
you can use ROM manager to jump back to 2.3.x
..
I am not rooted so I cannot use from manager and I do have stock recovery not clockwork so I cannot install superuser.zip
Sent from my Nexus S using XDA App
And for SuperOneClick phone needs to be visible in fastboot mode.
Sent from my Nexus S using XDA App
vstar said:
And for SuperOneClick phone needs to be visible in fastboot mode.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
for SuperOneClick phone needs to be visible in usb debugging mode.
Sorry mate but it only starts in USB Debug/Android mode - then it reboots the phone to fastboot shell and then same issue - phone is not discovered by windows hence nothing else happens.
Is there no other way of gaining root access instead of fastboot option - this would solve all my pains
Thx everyone for input
..
i suggest just follow zedomax tutorial on how to root your ics phone. He also have the download links for all the files that you will need. once your phone is rooted then you can download the old stock version of your phone.
http://nexusshacks.com/nexus-s-root/how-to-root-nexus-s-or-nexus-s-4g-on-ics-or-gingerbread/
Looks like a driver issue, when phone isn't discovered by windows in fast boot mode. (You are booting with vol up+power, right?)
Forget about any one-click-stuff etc - unlocking and cwm is the way to go. Everything else just makes troubles.
What I don't get is how you unlocked your phone without fastboot working?! That's not possible... for the moment forget about rooting - superuser isn't needed to flash stuff via fastboot/cwm.
Concentrate on getting fastboot to work. After that it's a piece of cake. Check you have drivers and fastboot set up properly on your PC.
Edit:
By this I mean following the sticky-guides, using the sdk from Google (not any downloads pretending to make it quick'n'easy. Go the official way!)
You should also give the 4.0.4-stockrom (ported from ns4g-leak) a try - it's way better than 4.0.3!
Edit: talking about this one: http://forum.xda-developers.com/showthread.php?t=1474878
OK guys - I have no idea how should I say it in different way - this is not a matter of a driver - the phone is physically not visible to the computer. There is no unknown device of anykind so I have nothing to use a driver for. It is not that fastboot command does not recognize the phone - the phone does not exists in Windows Device Manager. Looks like when phone is in fastboot mode the usb port is dead. So no chance of rooting in standard way.
And I have unlocked it as it was working before. I did realize it is not working when I tried to downgrade recently.
Election Day: I have tried 3 different cables, couple of computers and 3 different operating systems - ubuntu included. How this trick with hairdrier works? If it is a flash why does it work for everything else but not fastboot mode? Should I heat it up without cover and battery? Any specific area? Should I plug in while hot?
Thx guys.
usb working with sys booted up, but broken on bootloader?! makes no sense at all, i hope you can see that for yourself. can't be a hw-failure (then it would be broken everywhere).
have you reinstalled the driver from the sdk? the problem is on your pc, not the phone...
and forget about rooting for the moment, you don't need that to flash a rom. or are you mixing things up?!
that nonsense about heating up the phone with a hair drier was a joke, right?
..
im trying to unlock my bootloader but i cant!
the drivers are installed but when my device is in that mode from pressing volume botton down and power button the pc doesnt recognizes it!
i checked a few many times and its just telling me the the latest drivers are installed..
when i write the fastboot oem unlock it says (waiting for device) what should i do?
thanks!
adi90004 said:
im trying to unlock my bootloader but i cant!
the drivers are installed but when my device is in that mode from pressing volume botton down and power button the pc doesnt recognizes it!
i checked a few many times and its just telling me the the latest drivers are installed..
when i write the fastboot oem unlock it says (waiting for device) what should i do?
thanks!
Click to expand...
Click to collapse
Did you follow this, especially the Driver Instalation part?
Sent from my Nexus 5
adi90004 said:
im trying to unlock my bootloader but i cant!
the drivers are installed but when my device is in that mode from pressing volume botton down and power button the pc doesnt recognizes it!
i checked a few many times and its just telling me the the latest drivers are installed..
when i write the fastboot oem unlock it says (waiting for device) what should i do?
thanks!
Click to expand...
Click to collapse
You should install drivers 2 times..
Once when it is booted..
And again when it is in fastboot mode..
Since mode changes, your pc recognizes your device as new one.
So install drivers again after connecting in fastboot mode..
adi90004 said:
im trying to unlock my bootloader but i cant!
the drivers are installed but when my device is in that mode from pressing volume botton down and power button the pc doesnt recognizes it!
i checked a few many times and its just telling me the the latest drivers are installed..
when i write the fastboot oem unlock it says (waiting for device) what should i do?
thanks!
Click to expand...
Click to collapse
You have to install the drivers manually. You can do this by downloading the drivers in the SDK manager and installing them in the device manager.
This might help you solve the problem...
http://forum.xda-developers.com/showthread.php?t=2532297
This may be just me but its a good plan to make sure your pc can see your device when developer Mode is enabled before you go into fastboot this will make sure all the drivers are in order, Not sure if this makes a difference but i also make sure when enabling Developer mode that MTP and Camera Are both unchecked as it can mix up the drivers on my system anyway
When I plug my device into my computer, run an ADB command window and type "adb devices", my phone isn't recognized. I'm running 5.0 right now, but I switched back to a sense based ROM and it still isn't recognized. I looked online and it said to check if the correct drivers are installed, but when I plug my phone in nothing happens and I'm not sure where to check to see if they're installed or not. I'm trying to figure this out so I can flash the newer 4.4.4 or 5.0 firmware, but I can't if my device isn't recognized. Thanks so much, I really appreciate it!
tannerrblake said:
When I plug my device into my computer, run an ADB command window and type "adb devices", my phone isn't recognized. I'm running 5.0 right now, but I switched back to a sense based ROM and it still isn't recognized. I looked online and it said to check if the correct drivers are installed, but when I plug my phone in nothing happens and I'm not sure where to check to see if they're installed or not. I'm trying to figure this out so I can flash the newer 4.4.4 or 5.0 firmware, but I can't if my device isn't recognized. Thanks so much, I really appreciate it!
Click to expand...
Click to collapse
I assume that you are using Windows?
Click on Start\All Programs\HTC and you should see HTC Driver in there.
Have you tried a different USB cable?
jsaxon2 said:
I assume that you are using Windows?
Click on Start\All Programs\HTC and you should see HTC Driver in there.
Have you tried a different USB cable?
Click to expand...
Click to collapse
I haven't tried a new cable, I don't have any others with me unfortunately. I see the HTC driver folder, it looks to me like the drivers are installed, but I'm still not sure. I'm running Windows 8.1
Also, how can I check which firmware I'm currently running?
tannerrblake said:
I haven't tried a new cable, I don't have any others with me unfortunately. I see the HTC driver folder, it looks to me like the drivers are installed, but I'm still not sure. I'm running Windows 8.1
Also, how can I check which firmware I'm currently running?
Click to expand...
Click to collapse
You need to go into the bootloader to see your firmware version.
Hold Power + Vol Up and as soon as the screen goes off, slide your finger down to Vol Down while still holding Power.
jsaxon2 said:
You need to go into the bootloader to see your firmware version.
Hold Power + Vol Up and as soon as the screen goes off, slide your finger down to Vol Down while still holding Power.
Click to expand...
Click to collapse
I did that, but I still don't know how to comprehend all the stuff on that screen. Which one of the lines in the firmware version? I still can't get ADB to recognize my device, I'm starting to get frustrated haha. I've tried multiple ROM backups that I have, I uninstalled HTC Sync Manager and installed it again, I can't get anything to work. Anyone have any more suggestions?
its the drivers
From time to time my computer doesn't like to bring up the drivers when I plug mine in. The driver is definitely the issue though. Make sure the drivers are installed, then plug your phone in and restart your machine. It might find your phone at boot. It's worked for me a few times.
tannerrblake said:
I did that, but I still don't know how to comprehend all the stuff on that screen. Which one of the lines in the firmware version? I still can't get ADB to recognize my device, I'm starting to get frustrated haha. I've tried multiple ROM backups that I have, I uninstalled HTC Sync Manager and installed it again, I can't get anything to work. Anyone have any more suggestions?
Click to expand...
Click to collapse
Do you have USB debug enabled on your phone?
damn straight its the drivers
Uninstall all the drivers you have to do with your phone right now. Then follow this tutorial.
/watch?v=afrvSGiMAtk
It's on YouTube but I can't post links
I was at the same exact spot yesterday but I followed this guy's instructions now I'm s off rooted and unlocked
Good Luck
Hi,
First of all the bootloader is already unlocked.
Two problems:
1. - I was trying to flash twrp.img on my mobile but I am not getting that green android to show up in my screen all I get a black screen with blue led light, I usually power off the mobile, hold volume up and then connect the USB cable to my mobile.
2. - Can't find mobile device while using flash or fastboot, my mobile Developer option and USB debugging are turn on, mobile drivers and adb-setup-1.4.3 are installed, I have access to my mobile on my PC , when I do the process of flashing or fastboot I turn off the mobile and I unplug USB cable from my mobile, I press the keys to do flash or fastboot (I don't see no green android just a led light turn on) and connect the USB cable, problem is my PC can't find the mobile device, I use adb function eg. adb devices or fastboot devices I get nothing no device no info.
Is this problem with Win 10?
Was my problem understood in 2. - ?
Sa9aX said:
Is this problem with Win 10? Was my problem understood in 2. - ?
Click to expand...
Click to collapse
Most likely a drivers problem, Windows10 fails to tell you that it's not installed the drivers that you pressed the install button on. It also fails to assign the right drivers when you add the phone in flashmode/fatsboot.
You will need to add them manually.
Go into safe mode and use 'driver signing disabled', try adding the drivers again. Then plug in you phone in flashmode/fastboot, then look in the device manager for the phone and change it
Several people have reported success with Zdiag drivers
Didgesteve said:
Most likely a drivers problem, Windows10 fails to tell you that it's not installed the drivers that you pressed the install button on. It also fails to assign the right drivers when you add the phone in flashmode/fatsboot.
You will need to add them manually.
Go into safe mode and use 'driver signing disabled', try adding the drivers again. Then plug in you phone in flashmode/fastboot, then look in the device manager for the phone and change it
Several people have reported success with Zdiag drivers
Click to expand...
Click to collapse
Thanks! Great Info.
I removed the drivers manually in device manager and then used Zadig, now in command mode I getting something.
Next I have to figure how root the phone, do I need to flash twrp.img ?
I have all this stuff and I got confused which one I need to do next:-
boot.img
boot-G8141-47.2.A.10.45-hideunlock-rooted.img
twrp.img
twrp-3.2.1-0-maple
xperifix.zip
ss_maple.zip
zestmaple-latest.zip
ScriptWINg-master.zip
Sa9aX said:
Thanks! Great Info.
I removed the drivers manually in device manager and then used Zadig, now in command mode I getting something.
Next I have to figure how root the phone, do I need to flash twrp.img ?
I have all this stuff and I got confused which one I need to do next:-
boot.img
boot-G8141-47.2.A.10.45-hideunlock-rooted.img
twrp.img
twrp-3.2.1-0-maple
xperifix.zip
ss_maple.zip
zestmaple-latest.zip
ScriptWINg-master.zip
Click to expand...
Click to collapse
Back again...
I figured all out:-
twrp-3.2.1-0-maple.img
boot-G8141-47.2.A.10.45-hideunlock-rooted.img (latest firmware)
Magisk Manager
I corrupted my phone's root/system/etc files and when I restarted it, it wouldn't turn on and got stuck on the realme logo. i hold my phone vol+ and - and power key and when the realme logo comes up, i release the power key, i think download mode opens, but it usb device is faulty for 1-2 seconds and disappears immediately, meanwhile in device manager it shows unknown device for 1-2 seconds and disappears. After 10-15 seconds there is a usb connection sound but nothing happens. I can send adb commands but I have to confirm the confirmation window but I cant.
Please help me, how can I fix it?
Does adb devices say "unauthorized"?
Are you sure that it's ADB and not fastboot or EDL that is appearing?
You can use usblog.exe to see what's popping up and down. Just run it.
Install Unisoc/Spreadtrum drivers and then see if your device is recognised as a SPD USB device under device manager and let me know here
Renate said:
Does adb devices say "unauthorized"?
Are you sure that it's ADB and not fastboot or EDL that is appearing?
You can use usblog.exe to see what's popping up and down. Just run it.
Click to expand...
Click to collapse
Yes, I get the unauthorized message as below. If I can somehow authorize it, I will be able to enter fastboot mode and flash the stock rom.
mvikrant97 said:
Install Unisoc/Spreadtrum drivers and then see if your device is recognised as a SPD USB device under device manager and let me know here
Click to expand...
Click to collapse
Okay, I'm trying
mvikrant97 said:
Install Unisoc/Spreadtrum drivers and then see if your device is recognised as a SPD USB device under device manager and let me know here
Click to expand...
Click to collapse
Please try a different usb port on your computer.
Don't use USB 3.0 port.
If nothing works then either the phone's usb is malfunctioning or your PC.
Don't use USB extension to connect your phone, plug directly to your computer port.
Also update your PC drivers using driver booster free software and then set restart and try again
mvikrant97 said:
Please try a different usb port on your computer.
Don't use USB 3.0 port.
If nothing works then either the phone's usb is malfunctioning or your PC.
Don't use USB extension to connect your phone, plug directly to your computer port.
Also update your PC drivers using driver booster free software and then set restart and try again
Click to expand...
Click to collapse
I updated with Driver Booster, no luck.
I only tried the front USB ports, do I need the back ones? There are 2 2.0 and 1 3.0 port on the front
The computer is new so I don't think it's defective, the phone is charging and I was using it before it went brick.
I also modified the boot file to install a new GSI and used the following guide.
Spoiler
First, you need to unlock fastbootd:
1. Download the stock ROM version 91: Download and extract the .pac file Link
2. Install the SPD research tool and drivers: GDrive
3. Open it
4. Click on the single gear icon
5. Select the .pac file of the stock rom
6. Wait until it loads
7. Click on the two gear icon
8. Find BOOT in the list
9. Right-click on the path next to it
10. Download here and select boot_r1.img
11. Click OK and then click the arrow icon
12. Turn off your phone
13. Press and hold Power + VolumeDown until you see the text "Downloading"
14. Release the buttons after seeing
15. Wait until you see the text "Passed"
16. Click on the Stop icon, disconnect your phone and turn it on
[/ISPOILER]
@leanord Can you help me?
The 0000/0002 is standard Linux goofiness when you enable USB gadget but you don't initialize anything or add any functions.
This often pops up during boot sequences. It means nothing. It does cause Windows to say "Invalid device".
The 22d9/2769 appears to be normal ADB and since you're getting "unauthorized" shows that everything is fine.
Are you in recovery or regular Android?
Stock recovery usually is ADB secure and you don't have the keys for it.
Renate said:
The 0000/0002 is standard Linux goofiness when you enable USB gadget but you don't initialize anything or add any functions.
This often pops up during boot sequences. It means nothing. It does cause Windows to say "Invalid device".
The 22d9/2769 appears to be normal ADB and since you're getting "unauthorized" shows that everything is fine.
Are you in recovery or regular Android?
Stock recovery usually is ADB secure and you don't have the keys for it.
Click to expand...
Click to collapse
I don't fully understand your question, but I have the stock recovery, I didn't install TWRP, and I installed dotOS 5.2 as GSI. I think I corrupted the fastboot, download mode boot files in the root files. I will take it to the service center, but if you have a solution, you can write, I don't want to give money.
It's gone to stock recovery and you don't have keys.
You need to try buttons to get it into bootloader (fastboot). Or did they disable that?
Renate said:
It's gone to stock recovery and you don't have keys.
You need to try buttons to get it into bootloader (fastboot). Or did they disable that?
Click to expand...
Click to collapse
It may have been disabled or because I corrupted system files.
Wanted? I came, to flash the phone, you do not need to press anything except the volume keys, the power button is only a catalyst, you need to hold it down until the screen goes out, and then just Keep the volume - and flash as usual, the main thing is to keep it immediately plugged into the PC with a ready-made flasher
What I have done:
1. The screen is off
2. I hold down the volume - and power button.
3. The phone vibrates and as soon as the realme logo appears, I plug the usb into the phone and release the power button.
4. The computer receives the message "USB Device not recognized, malfunctioning" and the unknown device is added to the device manager (It doesn't come anymore, I don't know what happened, I installed a lot of drivers.)
5. After 20 seconds, the USB connection sound is heard and the name of my phone is added to the "universal serial bus devices" section of the device manager.
Luuukie said:
What I have done:
1. The screen is off
2. I hold down the volume - and power button.
3. The phone vibrates and as soon as the realme logo appears, I plug the usb into the phone and release the power button.
4. The computer receives the message "USB Device not recognized, malfunctioning" and the unknown device is added to the device manager (It doesn't come anymore, I don't know what happened, I installed a lot of drivers.)
5. After 20 seconds, the USB connection sound is heard and the name of my phone is added to the "universal serial bus devices" section of the device manager.
Click to expand...
Click to collapse
Why are you doing it? You should sit in the flash driver, and not watch how the device is connected, Windows will not have time to see exactly what is connected until you start flashing
leanord said:
Why are you doing it? You should sit in the flash driver, and not watch how the device is connected, Windows will not have time to see exactly what is connected until you start flashing
Click to expand...
Click to collapse
SP Flash Tool doesn't see my device so I can't flash it. If you mean Fastboot, I can't get into it.
By the way, that font that's showing up in my UsbLog is UGLY.
I readjusted things, you can download a new copy that is prettier.
Oh, this is a Unisoc.
I know a lot about Qualcomm, some about Mediatek and almost nothing about Unisoc.
Surely there is some way to get this into Unisoc ROM bootloader mode?
There are either test points or you can disable the eMMC?
If you could pull recovery and mod ro.adb.secure=0 you'd have recovery with ADB at least.
Renate said:
Oh, this is a Unisoc.
I know a lot about Qualcomm, some about Mediatek and almost nothing about Unisoc.
Surely there is some way to get this into Unisoc ROM bootloader mode?
There are either test points or you can disable the eMMC?
If you could pull recovery and mod ro.adb.secure=0 you'd have recovery with ADB at least.
Click to expand...
Click to collapse
I'm sorry, I don't know that much. But if you tell me the steps how to do it, I can do it.
@leanord when installing GSI, I flashed boot_r1.img from your Realme C21Y GSI installation guide, did you disable fastboot or something?