Guys, I want to unlock my sim on Desire C. I managed to get phone bootloader unlocked, Rooted, HTC driver installed and a busybox install.
I am following the steps "Sim Unlock Guide [Desire C]"http://forum.xda-developers.com/showthread.php?t=2024422
but the procedure I don't follow.
1) Do I connect the phone with PC with USB cable under bootloader Mode or Recovery mode? I connect the phone with pc with USB, but it is NOT in Bootlaoder or Recovery Mode. I just have the phone boot normally
2) How does busybox work? i just choose the first one in play store, once installed, it is asking for root access, then loading a lot of files, and it asks me to install again, so I did. what else I need to do.
3) I enter command "ADB Shell" in Windows-cmd, a bunch of thing flashed. I didn't get " sh-3.2#" , after I enter "SU", nothing happend on my phone, in cmd command prompt, it says "SU is not recogized command"
I don't think my PC is talking to the phone. what do I do?
many thanks for your help.
i final figure out the problem, it's so silly, i just need to put in a microSD card in the phone, then adb command works perfectly, just log in to phone normally, plug in to your pc via USB, run the adb shell as instructed, unlock the phone is seconds
remember unlock code is 8 digits long, I got two sets of number, one set is 16 digits, it is not the unlock code
Related
Hey guys, I have a problem here. I unlocked the phone, flashed with twrp 3.01 and supersu. Then I installed Resurrection remix, flashed twrp 4.0.1 and supersu again. My phone works, but always had the initial screen "dm-verity". So I searched about it, and I figured out I have to go to bootloader and enter 2 commands. Now, when I enter in cmd and type "adb devices" while op3t in bootloader, my phone is not recognized. (0 devices found). Instead, when in twrp -> advanced-> adb sideload, my phone is listed with serial number. How can I make my phone recognisible by Windows while in bootloader mode, so that I can enter the 2 commands and get rid of dm-verity message? Everything inside the phone and the rom itself work perfect.! Also, when I go to settings/developer, I'm not able to change "oem unlock", it stays forced on OFF... Is that normal? Thank you very much in advance.
Magic Tmac1 said:
Hey guys, I have a problem here. I unlocked the phone, flashed with twrp 3.01 and supersu. Then I installed Resurrection remix, flashed twrp 4.0.1 and supersu again. My phone works, but always had the initial screen "dm-verity". So I searched about it, and I figured out I have to go to bootloader and enter 2 commands. Now, when I enter in cmd and type "adb devices" while op3t in bootloader, my phone is not recognized. (0 devices found). Instead, when in twrp -> advanced-> adb sideload, my phone is listed with serial number. How can I make my phone recognisible by Windows while in bootloader mode, so that I can enter the 2 commands and get rid of dm-verity message? Everything inside the phone and the rom itself work perfect.! Also, when I go to settings/developer, I'm not able to change "oem unlock", it stays forced on OFF... Is that normal? Thank you very much in advance.
Click to expand...
Click to collapse
Did you installed the drivers? I had the same issue and I installed the OP3T USB drivers afterward it shows me the device.
Yes I did. But I can also reinstall them, can you please provide me the driver's link which fixed the same problem? Thanks
Device: Verizon's Motorola Droid Turbo with Android 6.0.1 and build number MCG24.251-5-5
Hey guys. Newbie here.
So recently i accidentally deleted an important video file and searched google for data recovery methods on smartphone. So most of the post that I read mentioned rooting and a recovery software called Dr.Fone etc. So I installed this software, connected my phone, turned on usb debugging and oem unlocking and started the recovery process. But it was not successful because dr.fone could not root my phone for deep data recovery.
so i googled again and tried sunshine, kingroot, kingoapp and iroot.
Then i tried adb and fastboot(to unlock bootloader).
The thing is in adb command line, the command "adb devices" shows my device. Then I wrote "adb reboot bootloader" and my phone rebooted. then i wrote "fastboot oem unlock(or something like this i copy/pasted it)" it told me that "waiting for any device".
I mean whenever i boot my phone into bootloader my "adb devices" command shows no device but i start my phone in normal mode the "adb command" is working.
Another thing, the "fastboot device/devices" is also not working. It just takes me back to a new line to enter a new command.
Any command containing fastboot is not recognizing my device and all the adb commands are recognized easily.
I have installed all the latest device drives including the universal adb drivers and motorola device manager.
Guys, i am open to all suggestions.
Please help me out.
You have to unlock your bootloader to get permanent root, and you have to do it with Sunshine.
Sunshine is a $25 paid app.
There IS an unstable, temporary root method appropriately called "temp root" that is actually the first step to using Sunshine to unlock the bootloader. Some people cheap out and ONLY use that. But it doesn't survive reboots and you have to run a special command to uninstall it, otherwise you bootloop.
https://forum.xda-developers.com/showthread.php?t=3639316
However, it's possible this temp root method will allow Dr. Done software to do what it needs. Read up on it, try it, see. (Ignore the parts about Magisk, you don't need that.) Just be sure to run the correct uninstall commands. But you would have to do that anyways, if you used Sunshine to unlock the bootloader.
ChazzMatt said:
You have to unlock your bootloader to get permanent root, and you have to do it with Sunshine.
Sunshine is a $25 paid app.
There IS an unstable, temporary root method appropriately called "temp root" that is actually the first step to using Sunshine to unlock the bootloader. Some people cheap out and ONLY use that. But it doesn't survive reboots and you have to run a special command to uninstall it, otherwise you bootloop.
https://forum.xda-developers.com/showthread.php?t=3639316
However, it's possible this temp root method will allow Dr. Done software to do what it needs. Read up on it, try it, see. (Ignore the parts about Magisk, you don't need that.) Just be sure to run the correct uninstall commands. But you would have to do that anyways, if you used Sunshine to unlock the bootloader.
Click to expand...
Click to collapse
Thanks man. Will try this method too.
ahm259 said:
Device: Verizon's Motorola Droid Turbo with Android 6.0.1 and build number MCG24.251-5-5
Hey guys. Newbie here.
So recently i accidentally deleted an important video file and searched google for data recovery methods on smartphone. So most of the post that I read mentioned rooting and a recovery software called Dr.Fone etc. So I installed this software, connected my phone, turned on usb debugging and oem unlocking and started the recovery process. But it was not successful because dr.fone could not root my phone for deep data recovery.
so i googled again and tried sunshine, kingroot, kingoapp and iroot.
Then i tried adb and fastboot(to unlock bootloader).
The thing is in adb command line, the command "adb devices" shows my device. Then I wrote "adb reboot bootloader" and my phone rebooted. then i wrote "fastboot oem unlock(or something like this i copy/pasted it)" it told me that "waiting for any device".
I mean whenever i boot my phone into bootloader my "adb devices" command shows no device but i start my phone in normal mode the "adb command" is working.
Another thing, the "fastboot device/devices" is also not working. It just takes me back to a new line to enter a new command.
Any command containing fastboot is not recognizing my device and all the adb commands are recognized easily.
I have installed all the latest device drives including the universal adb drivers and motorola device manager.
Guys, i am open to all suggestions.
Please help me out.
Click to expand...
Click to collapse
Have you tried just connecting to your pc, enable 'Transfer Files'/mtp mode, and using PhotoRec to scan it as attached storage? The video should not have been anywhere you would need root to access, so this should work. I personally haven't used PhotoRec on a phone in several years, but in the past it worked great. It's free software from CGSecurity (often bundled with TesDisk).
http://www.cgsecurity.org/wiki/Phot...data_from_my_phone.2Fdisk.2Fusb_key.2F..._.3F
Just remember, everytime you use the device you risk rendering the video totally unrecoverable. At best you'll get the whole thing back. More than likely if you're lucky, you'll only get part of it and it will be enough that video software can recognize and play what's left. (based on my own experience). It just depends on how large the video was (data-wise) and how many blocks were overwritten by other data.
I installed hisuite which is easily able to access all my device data. Installed adb universal which created c:/abd in my pc or don't know what created that. Installed minimal abd fast boot . Now the problem is, i go to c:/adb and open command line and keep getting "waiting for devices" then goto x86/minimal adb.... Again same thing. Even installed android sdk without even knowing what I'm doing. Now I'm feeling like dumb (probably I'm) and about about to give up. What I'm missing??
What are you trying to do and what commands are you issuing?
I'm assuming at the very least you have phone connected with debugging enabled.
Just trying to follow commands of "Unlock Bootloader, Even without code! by hackintosh5". But first I'm doing some simple commands like "fastboot reboot recovery" or "fastboot devices" but no luck. I must be doing something terribly wrong. At least show me a guide article, cause when i search i get extremely confused.
Some more info.
-usb debugging enabled, and pc authorized (maybe)
-hisuite is able to read everything so i must GUESS i have installed correct driver (tho i have no idea what it is)
Ok, to use the fastboot commands, the phone must be in fastboot mode. This is achieved by when phone is off , hold Vol - and connect phone to PC via USB.
Then try the above commands.
It finally worked, thanks a lot brother :laugh:
An update to Android 12 has been released. Everything seems to be fine. Random reboots appeared.
I tried a full reset of nothing, then downloaded the OTA via adb sideload in the hope that it helps, but to no avail.
And it's sad that the bootloader is locked
device verizon.
Screenshot shows adb sideload error
Who knows what can be done, please tell me.
-------------------------------
After 3 long days of agonizing and torturing Google support, no help from them
Found the adb rescue install file.zip command, in their source code
Because I had coral-ota-sp1a.210812.015 firmware, I needed verizon firmware, for me coral-ota-sp1a.210812.016.a1-37be0022 didn't work, it didn't start
But with this coral-ota-sp1a.211105.002.a1-0939d2dd everything is fine
The main thing is to have the usb cable intact. And the pc connector usb 2.0
1. Go into bootloader
2. Select Rescue mode
3. type in the following words at the command line
adb rescue install file_name.zip
All should go through without errors
May help someone
Sorry for my English.
Hello all, I'm trying to install a new ROM but one of the first steps consists in getting access to adb and fastboot mode.
Unfortunately, I can easily access to adb mode, and adb commands respond well, but when I then go in fastbood mode 'adb reboot fastboot", My phone goes to fastboot with the icon on the screen, but won't answer to any fastboot commands.
I've tried to install adb drivers, uninstall/reinstall the drivers (but it's always the windows drivers that installs first). I even tried to install google usb drivers using SDK manager, but didn't succeed this step.
I've tried to change the usb cable, but with another one, it was worse: even the adb commands would not work. So I guess the one I'm using is ok.
I'd be very happy if someone could help me fixing this frustrating bug!
Model:M1903F11A
kernel:4.14.117-perf-g0f2347b
MIUI Global 12.0.6
Android version : 10 QKQ1.190825.002
Cyjam said:
.. new ROM but one of the first steps consists in getting access to adb and fastboot mode.
...
Click to expand...
Click to collapse
The first step is to unlock the bootloader.
Cyjam said:
... when I then go in fastbood mode 'adb reboot fastboot", My phone goes to fastboot with the icon on the screen, but won't answer to any fastboot commands.
....
Click to expand...
Click to collapse
For fastboot try:
adb devices
........... (here you must see a number)
adb reboot bootloader
fastboot devices
........... (here you must see that number again)
Hi, thanks for trying to help me:
you're right , first is the unlock, but it's done. it's even in "grey" on the screen and written: bootloader is already unlocked. I've tested my phone with "root checker" and test is ok.
you're right about the command, this is the one I've used to go to fastmode and actually this command works: as I said, when in adb mode, it's all good: my phone is connected to pc and accepts the adb commands. But once I switch to fastboot, this is when it's going wrong: my phone's not answering to any commands.
To be more precise: when prompting: adb devices: i get a number. When prompting, in fastbood mode, fastboot devices: i get nothing.
Alleluia!!
Finally found out how to fix it!
After going in fasboot mode with the command: adb reboot bootloader, i opened the windows device manager: There I found a android XXx interface, or something like this: anyway, something barely identified by windows. Right clik, update drivers, manually update, pointing to the folder I store the google usb drivers and : Bingo! It works like a treat.
I now can step further in the process... Hope I won't need to come back with another question in the next minutes!