Database Info

[Q] Trouble unrooting Desire S

Hello!
Recenty I rooted my HTC Desire S and want it unrooted again to install ICS.
I tried to install ICS, but the install keeps failing.
Problem is I am unable to reverse the root.
1. Phone is rooted (and still running Gingerbread)
2. HDBOOT has been updated to 2.00.0002
3. Phone is S-ON (never had it S-OFF I think because I used HTCDev to root it)
Can someone PLEASE help me with this? I really do not know what to do now and desperatly want to install ICS.
Thank you and kind regards!

reboot to bootloader, connect to pc, type in cmd
Code:
fastboot oem lock
then run the RUU
this topic was discussed thousand of times in the very recent threads. It will be much helpful both for you and your device if you do some reading to make sure that you completely understand what are you doing to the phone before actually doing anything

Thank you very much for your help and advice, it would indeed be better to double-check everything in the future...
I tried your advice, but the cmd gives me the following error:
Microsoft Windows [versie 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Alle rechten voorbehouden.
C:\Users\WarBlade>cd..
C:\Users>cd..
C:\>fastboot oem lock
...
FAILED (status malformed (1 bytes))
finished. total time: 0.016s
C:\>
Click to expand...
Click to collapse

Quirania said:
Thank you very much for your help and advice, it would indeed be better to double-check everything in the future...
I tried your advice, but the cmd gives me the following error:
Click to expand...
Click to collapse
Make sure you have fastboot properly installed, HTC Drivers as well, if yes try another USB cable. Make sure that FASTBOOT USB is written on the device screen when issuing the command. Make sure that the out put of the
Code:
fastboot devices
command gives you your serial number, not an empty line

Seems to work now! Thank you!
PS: Installed and rebooted correctly, but the UI is loading for allready 15 minutes or so? Should I wait or just try to reboot it again (while it's still loading)?
Again, thank you for your assistance!

Fastboot issues - Can't Get it to Work

I have a Nexus 5, returned to factory specifications (many times) with backup & restore inhibited. I am trying the “very simple” process of unlocking it, without any success. My problem is repeated many times on the web, Fastboot does not work, but ADB does.
I run the following command:
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb devices
List of devices attached
0315c2d60935c160 device
Then I run the following command:
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot devices
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
ADB sees the phone; Fastboot does not.
The solution is well documented on the web: Install new drivers. I have been installing drivers from just about everywhere for the last week without success. With the phone connected, I get this from Device Manager:
Computer
Android Device
Android Composite ADB Interface
The driver information is as follows:
Driver Provider: Google, Inc.
Driver Date: 7/9/2013
Driver Version: 8.0.0.0
Driver Signer: Google, Inc.
Driver Details:
Driver Files:
C:\Windows\System32\Drivers\Winsub.sys (File Version 6.2.9200.16384(Win8_rtm.120725-1247))
C:\Windows\System32\WdfcoInstaller01009.dll(File Version 1.9.7600.16385 (Win7_rtm.090713-1255)
C:\Windows\System32\WinUSBCoInstaller2.dll (File Version 6.1.7600.16385 (win7_rtm.090713-1255))
I am running a Dell XPS-17 I7 laptop with Windows 8 (not 8.1) 64 bit
If I could find a way to unlock without using Fastboot, that would probably be a good solution, but I can’t. And I have absolutely no success at getting Fastboot to work.
I do notice that the Device Manager lists Android Composite ADB interface (ADB works) but noting about a Fastboot interface. Does that mean anything?
Please help I am at my wit’s end.
For what it is worth, I did read all the tutorials here, and the only thing I could figure out was if I have the right drivers everything works fine. I also reviewed the posts here, including "Diagnosing USB Driver and ADB issues in Windows," which discusses ADB (which I have no problem with)

this article helped me out a bunch. http://blog.dantup.com/2012/10/fixing-adb-device-not-found-with-nexus-7-in-recovery-mode/
you'll have to edit the "android_winusb.inf" with the correct hardware id.
in Device Manager make sure you go to "Android Device" > "Android Composite ADB Interface" go to Properties. on the Details tab and then click on the drop down box and select "hardware ids" you might see 2 ids there. i believe the one you'll need is the bottom one. if you only have one. thats fine too.
so, read the article. grab your hardware id and edit your driver. see if it works. you may have to reboot after you edit the driver. hope this works for you.

krdu said:
I have a Nexus 5, returned to factory specifications (many times) with backup & restore inhibited. I am trying the “very simple” process of unlocking it, without any success. My problem is repeated many times on the web, Fastboot does not work, but ADB does.
I run the following command:
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb devices
List of devices attached
0315c2d60935c160 device
Then I run the following command:
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot devices
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
ADB sees the phone; Fastboot does not.
Click to expand...
Click to collapse
OK, please don't be offended, but I have to ask a really dumb question. You aren't running the "fastboot devices" command while in recovery, right? I read the above twice and didn't see where you booted into bootloader after running the "adb devices" command. Unless I'm missing something, fastboot won't find any devices unless you are in the bootloader.

Sounds like you need to boot your phone into fastboot mode. Power off the phone and hold volume down and hit the power button.
Then the fastboot devices command should work and you should be able to unlock the boot-loader then. Unlocking the boot-loader will wipe your phone just so you know.

erikivy said:
OK, please don't be offended, but I have to ask a really dumb question. You aren't running the "fastboot devices" command while in recovery, right? I read the above twice and didn't see where you booted into bootloader after running the "adb devices" command. Unless I'm missing something, fastboot won't find any devices unless you are in the bootloader.
Click to expand...
Click to collapse
Actually, the answer to that question is "Yes, and no." I was not aware that Fastboot only worked in the bootloader, but I could never get it to work there either. However, when I copied the previously posted listings I was not in the bootloader, I was in normal booted mode.
I then went and tried it in the bootloader, to copy listings to post, and here's what I got!
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb devices (In normal Mode)
List of devices attached
0315c2d60935c160 device
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb reboot bootloader (rebooted to Bootloader)
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb devices
List of devices attached
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot devices
0315c2d60935c160 fastboot
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot oem unlock
...
OKAY [ 41.215s]
finished. total time: 41.215s
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
As you can see it unlocked the phone but I have absolutely no clue why it unlocked this time and never did before. I hope to God I never have to unlock it again.
Also, it appears that in the bootloader, ADT is NOT working but Fastboot is! (now)

You realize that the two command line interfaces (ADB and fastboot) don't work in the same state, right? ADB is for use in recovery and while booted, whereas fastboot only works in bootloader. It sounds to me like everything is working exactly as it should.
I'm no expert or anything, but I always assumed that they were two different ways to interact with your device while it is in different states. If I'm mistaken, someone please correct me.

krdu said:
Actually, the answer to that question is "Yes, and no." I was not aware that Fastboot only worked in the bootloader, but I could never get it to work there either. However, when I copied the previously posted listings I was not in the bootloader, I was in normal booted mode.
I then went and tried it in the bootloader, to copy listings to post, and here's what I got!
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb devices (In normal Mode)
List of devices attached
0315c2d60935c160 device
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb reboot bootloader (rebooted to Bootloader)
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb devices
List of devices attached
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot devices
0315c2d60935c160 fastboot
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>fastboot oem unlock
...
OKAY [ 41.215s]
finished. total time: 41.215s
C:\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>
As you can see it unlocked the phone but I have absolutely no clue why it unlocked this time and never did before. I hope to God I never have to unlock it again.
Also, it appears that in the bootloader, ADT is NOT working but Fastboot is! (now)
Click to expand...
Click to collapse
ADB is used in android and the recovery.
Fastboot is used only in the bootloader.

Sony Xperia 5 II XQ-AS62 root

Happy new year! I was hoping to bring in the new year with root, but strangely with this version when ever I boot into "bootloader" from the recovery menu, the device screen is blank, and adb does not detect anything.
Would someone be gracious enough to provide a step by step root for this particular US variant? I can send you a gift card if you get me running with just root!
Thank You!

It's a $100 USD Gift card btw. I would send it to you via a direct message, or I can send you some crypto if you provide me your wallet should the root prove successful (for same amount). Thank you and have a happy new year!

BurnsMotorCycle said:
It's a $100 USD Gift card btw. I would send it to you via a direct message, or I can send you some crypto if you provide me your wallet should the root prove successful (for same amount). Thank you and have a happy new year!
Click to expand...
Click to collapse
On other thread you mentioned that `fastboot devices` gives nothing. I suspect that you are missing drivers for your device so try installing drivers first. Try these: Xperia 5 II driver - Sony Developer World ?

I saw that link before, but my device was not specifically listed. I'll try it anyway and hope that it works.

I boot into the "Fastbootd" menu on the phone, and then plug the device into my machine. when I run the "fastboot device" command I get:
fastboot: usage: unknown command device
When I then try the second method of connecting to fastboot (by holding down the volume up button while at the same time plugging the device in as per the instructions here: https://developer.sony.com/develop/...der/how-to-unlock-bootloader/#tutorial-step-2), the phone screen is blank.
I then try running the command "fastboot device" and I just get a "waiting for any device". Thanks for taking a look and let me know what else needs to be done!
Also I tried installing the drivers, and that did not work either. I still get the error "fastboot: usage: unknown command device"

BurnsMotorCycle said:
I boot into the "Fastbootd" menu on the phone, and then plug the device into my machine. when I run the "fastboot device" command I get:
fastboot: usage: unknown command device
When I then try the second method of connecting to fastboot (by holding down the volume up button while at the same time plugging the device in as per the instructions here: https://developer.sony.com/develop/...der/how-to-unlock-bootloader/#tutorial-step-2), the phone screen is blank.
I then try running the command "fastboot device" and I just get a "waiting for any device". Thanks for taking a look and let me know what else needs to be done!
Also I tried installing the drivers, and that did not work either. I still get the error "fastboot: usage: unknown command device"
Click to expand...
Click to collapse
Did you follow: Install OEM USB drivers | Android Developers ?
If so Can you see if device is detected properly in Device Manager?

PPGX5II said:
Did you follow: Install OEM USB drivers | Android Developers ?
If so Can you see if device is detected properly in Device Manager?
Click to expand...
Click to collapse
I see the issue now, I've been typing "Fastboot device" instead of "fastboot devices". I managed to successfully unlock the bootloader! Now how do I go about achieving root access?
btw the screen is still blank when I plug in the phone via the "Volume Up + USB connect" way of getting access to fastboot, if that makes a difference.
Also as A WARNING for anyone following this thread, unlocking the bootloader immediately initiates a wipe of the device. I had no problem with that since this is a brand new phone that I just got and am trying to unlock. Also, I am on:
Android 10
Build #: 58.0.A.22.21

BurnsMotorCycle said:
I see the issue now, I've been typing "Fastboot device" instead of "fastboot devices". I managed to successfully unlock the bootloader! Now how do I go about achieving root access?
btw the screen is still blank when I plug in the phone via the "Volume Up + USB connect" way of getting access to fastboot, if that makes a difference.
Also as A WARNING for anyone following this thread, unlocking the bootloader immediately initiates a wipe of the device. I had no problem with that since this is a brand new phone that I just got and am trying to unlock. Also, I am on:
Android 10
Build #: 58.0.A.22.21
Click to expand...
Click to collapse
Follow this guide to get root access: [GUIDE][WIN10] Bootloader Unlock/Re-Lock, Rooting with Magisk and flashing Firmwares | XDA Developers Forums (xda-developers.com)
As you have unlocked bootloader I believe you only need steps 25-27 to get root access.
Note: Read thread completely so that you can take backup if needed and also make sure you install all required things.

PPGX5II said:
Follow this guide to get root access: [GUIDE][WIN10] Bootloader Unlock/Re-Lock, Rooting with Magisk and flashing Firmwares | XDA Developers Forums (xda-developers.com)
As you have unlocked bootloader I believe you only need steps 25-27 to get root access.
Note: Read thread completely so that you can take backup if needed and also make sure you install all required things.
Click to expand...
Click to collapse
I'll try this out when I get back to my house. If it works, ill send you the gift card information. Please note that the gift card that I have works only in the US, so if you want to make some other arrangement, let me know.

BurnsMotorCycle said:
I'll try this out when I get back to my house. If it works, ill send you the gift card information. Please note that the gift card that I have works only in the US, so if you want to make some other arrangement, let me know.
Click to expand...
Click to collapse
Thanks! But I just wanted to help you out. I won't be taking any gift cards in return!
If you want you can donate it to some of these developers so that they can work on supporting more!
Cheers and Happy New Year!

It Worked! I appreciate your help, but I mostly just followed the link you provided from
Miustone. Thank you to him and you both! That Thread should definitely be pinned in the
"Sony Xperia 5 II ROMs, Kernels, Recoveries, & Othe" section too!
Ill donate to Miustone, and have a happy new year!
EDIT: Darn looks like Miustone only takes paypal, which I don't have (I have crypto). Thanks again for the help everyone!

Quick Question, how do you tell which region firmware is on your phone?

Do *#*#7378423#*#* go to Service Info >> Software Info and you will get Firmware details

PPGX5II said:
Do *#*#7378423#*#* go to Service Info >> Software Info and you will get Firmware details
Click to expand...
Click to collapse
you are so kindful!

Hi to participants of this thread,
can you tell me how you backed up the DRM keys before rooting?

klausstoertebeker said:
Hi to participants of this thread,
can you tell me how you backed up the DRM keys before rooting?
Click to expand...
Click to collapse
No because you can't

I also have Sony Xperia 5 II XQ-AS62 and I've found myself in a similar situation as burnsmotorcycle but I think it's because I have TWRP installed. More specifically, I see my device when I run "adb devices", I get nothing when I run "fastboot devices", and I get TWRP when I run "adb reboot recovery".
Does anyone know how I can uninstall TWRP? Please note, my device still has the bootloader unlocked, fastboot commands are unresponsive now that TWRP is present, and ADB and Magisk seems to be the only tools available to me right now.

[Redmi Note 8] Unlock the bootloader while bricked

I was using my phone normally yesterday (Saturday) 12/06, I left it charging and when I looked at it again, it was restarting non-stop. It's a Redmi Note 8, I held the power button, but it wouldn't turn on, it just went back to the bootloader screen, I didn't try to format it as I'm trying to recover my files. So I thought about unlocking the bootloader to have access to my files, I used Mi Unlock Tool, but it doesn't work because it asks me to add my account to the device (It was already added before this happened). I still have access to my account phone number, and email. But I couldn't unlock by this fastboot method, so I tried using the "fastboot oem unlock" command, which didn't work either, it showed these two messages.
'Fastboot boot command is not available in locked device'
FAILED (remote: 'Token Verify Failed, Reboot the device')
fastboot: error: Command failed
The versions of MiFlash Unlock I used were
"miflash_unlock-en-5.5.224.55" and "miflash_unlock-en-5.5.224.24".
The device is not recognized by the "Mi PC Suite".
The device still appears in fastboot devices, but not in adb devices

bump

When unlocking phone's bootloader automatically all user-data get lost.

Hint: Add Redmi Note 8 to this thread's title thus mainly owners of such phone get addressed.

jwoegerbauer said:
When unlocking phone's bootloader automatically all user-data get lost.
Click to expand...
Click to collapse
I was trying this and this [GUIDE]

jwoegerbauer said:
Hint: Add Redmi Note 8 to this thread's title thus mainly owners of such phone get addressed.
Click to expand...
Click to collapse
Ok!

When using "MiFlash Pro", I managed to reach 100% (?), but the device resets, gets stuck in the MIUI screen for 2 minutes and then resets again to the bootloader screen. I was flashing the same ROM i was using, the "V12.0.4.0.QCOMIXM".
Video flashing the ROM

What Am I Doing Wrong? (Rooting/Bootloader Unlocking)

Hopefully someone here can help me through my problem,
Device Details: BLU G60/BLU VIVO X6
Android 9/Pie
OEM Unlocking: Allowed
USB Debugging: Enabled
Hey, I'm pretty new to this way of customizing my phone (adb, root, roms etc), and I'm trying to root my phone with Magisk. I have a patched boot.img, my bootloader is allowed to be unlocked and I'm doing exactly what the root guide says (https://www.mobilewithdrivers.com/magisk-root/blu-g60-64gb-3gb-ram) but it wont work, I keep getting different errors and I see all my fellow droid users so happy with their rooted devices, I want to root mine too. So what I'm asking is; Can someone with an actual brain (Mine wont work) to try and help me out or walk me through step-by-step?
Thanks for reading!
Some of the issues I have:
"adb reboot booter" and "fastboot reboot bootloader" both reboot the device but in the top left corner it says "fastboot mode" and just freezes, when I do any command it just says "device null" but when I reconnect the USB cable, it just powers off.
"fastboot flashing unlock" results in "FAILED (remote: Not implemet.)" Yes, spelt like that.
"fastboot oem unlock" says, unkown cmd...

Wrong driver in use. Use the one provided by BLU suitable to your phone.

i couldnt find any drivers for the exact device, only google ones...
any ideas?

If you have a mac, you could try that. They usually don't require drivers.