Database Info

HTC One Mini (M4_U4) Softbricked, OEM not unlocked, USB debug not enabled, bootloop

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?

[Q] FRP lock help--j700T Marshmallow

Hello,
I wonder if someone would help me FRP unlock my phone. It is a T-mobile sm-J700t 2015. I have searched the forum but don't see a clear answer.
I have tried (from Youtube) the USB cable method, the camera method and flashing the 10/2016 stock firmware through ODIN. In Odin I get an error: "Complete(Write) operation failed". I cannot turn on USB debugging of course because I cannot get into the device. Haven't tried updating with Kies yet because I'm nervous they'll patch any additional back doors I could try.
I am somewhat experienced at flashing and such and I think there must be a way to completely wipe the device and flash new firmware but I don't see instructions for that.
Thanks in advance!
Odin v3.10.7 & v3.12.3
Recovery: Haven't changed
USB installed from Samsung Kies (made sure Kies isn't running)
Firmware: J700TUVU2APJ3_J700TTMB2APJ3_TMB.tar.md5
Where I got firmware: https://qc3.androidfilehost.com/dl/...224401143/J700TUVU2APJ3_J700TTMB2APJ3_TMB.zip

Anyone? Still locked out of my phone. :crying:

Reboot normaly > go to settings > developer setting > oem unlock check yes
#gggirlgeek
Reboot normaly > go to settings > developer setting > oem unlock > check yes

I can't get into the phone at all. It is FRP (Google) locked because I did a factory reset from recovery. I can only manipulate it from PC or stock recovery. I have ADB, Odin and Samsung Kies on my PC if that helps.

What is the reason I am getting the ODIN error: "Complete(Write) operation failed"? Is it due to the FRP lock?
If not, would flashing the same stock firmware even help? (I have read that it's not possible to flash older firmware versions.)
Is the boot partition where the FRP status is stored? Is it possible to flash a new boot image to reset it?
I assume flashing a custom recovery would be useless? I doubt it could be done without USB debugging/ADB being enabled anyway.

One of the reason for that odin error is flashing an old build of stock ROM, your guess is right
Even if you are able to flash a stock FW via ODIN you'll still not be able to boot to your OS.
You have to login using the same google id that was previously logged in
OR you have to bypass the Google Account Login Screen.
There are varous method on youtube (i know you saw them) to bypass that screen (Side Sync method worked for me at the 10th attempt) inorder to install a 3rd party app either to
1. enable the developer option or enable OEM unlock ( to flash custom ROM or custom recovery)
OR
2. to overwrite the previous google account saved with your new account details. (THIS ONE HELPED ME)
WITH FRP LOCK ON, ODIN SHOULD NOT GIVE YOU ERROR ONLY IF YOU ARE FLASHING STOCK ROM. BUT STILL YOU WILL BE LOCKED WITH GOOGLE ACCOUNT LOGIN SCREEN BECAUSE OF FRP LOCK ON AND STOCK ROM
FRP info. is saved in Sboot. Flashing a new sboot works only for devices those were never upgraded to Android 6. For J7 2015 that was upgraded to android 6, flashing Sboot bricks the phone as said by a cell phone repair agent
Regards,
Sid

@saddam.khan999 : Thank you so much for replying. This is helpful. :highfive:
What did you do to get the sidesync to work? Mine wouldn't even connect to Sidesync on my PC.
Tried different USB ports, and even different PC's to get it to pop up on the phone. Tried old usb drivers too. Sidesync never senses it, and My Computer only show MTP folder that won't accept any file pasted to it.
You did this with Android 6.0.1 October 2016 update? They fix more holes every time.
Also, can you give me the link to the unlock tutorial you used with Sidesync? Just want to compare my method.

Hi,
gggirlgeek said:
This is helpful. :highfive:
Click to expand...
Click to collapse
How grateful I am to read the above line! Thanks :good:
gggirlgeek said:
You did this with Android 6.0.1 October 2016 update?
Click to expand...
Click to collapse
Yes on Android 6.0.1 but i dont remember the build date.
gggirlgeek said:
Also, can you give me the link to the unlock tutorial you used with Sidesync?
Click to expand...
Click to collapse
I tired two different tutorials of SideSync to crack it. Once I reach home in the next 10 hours from now. I'll search on youtube and give u the links. Right now I cannot remember it.
gggirlgeek said:
What did you do to get the sidesync to work? Mine wouldn't even connect to Sidesync on my PC.
Click to expand...
Click to collapse
I followed below step to fix popup issue
1. Uninstall all samsung apps like, Kies, SmartSwitch, SideSync everything.
2. Uninstall Samsung USB drivers
3. Install SmartSwicth (to get best drivers)
4. Now install SideSync (latest)
5. Open SideSync and check for OTA updates in your PC (update it if available)

I give up. I'm going to pay somebody. He can use one of those low-level programs to unlock it remotely. It only costs $15. Well worth it. Wish me luck!

gggirlgeek said:
I give up. I'm going to pay somebody. He can use one of those low-level programs to unlock it remotely. It only costs $15. Well worth it. Wish me luck!
Click to expand...
Click to collapse
@gsmDabbler this guy says he/she can solve FRP issue for 5$ on skype. I dont know if he's fake or real. Best of luck

1. At welcome screen push next.
2. Connect to wifi and push next.
3. Accept terms and conditions and push next
4. Attempt to sign in to your google account.
5. On loopback to sign in page, push back intel you see the welcome screen again.
6. Push emergency dialer.
7. Dial 112
8. Put in on speaker and when the disbatcher askes what is your emergency, quickly swipe where the speaker option is to your left and click on email.
9. Ask the disbatcher for the number for non-emergency. (EXTREAMLY IMPORTANT TO NOT SKIP THIS STEP)
10. Sign into your email.
11. Compose a new message.
12. On another device download drive.google.com/file/d/0B3quVdCaxqLfaG9VY2xjd3hhWmM/view?usp=drivesdk[/url]
13. Move this file to a microsd card, and put it into the j7.
14. Push attach
15. Locate your sdcard and select es file explorer.
16. Once attached to the email, click on the box inside the email that says es file explorer. If redirected to security setting check the box that says "Unknown Sources".
17. If then redirected to install screen for es file explorer, install app and skip the next step.
18. Push back intel your on the screen with your new composed email with attachment, and once again click on es file explorer, and then install...
19. After install, restart your phone.
20. On welcome screen, plug your j7 into a power source.
21. Toggle your power button off, and then back on.
22. Click on the far right last bubble.
23. On home screen of es file explorer, take the sdcard out of the j7 and put back into the extra device you downloaded es file explorer to, and download these 2 files.
drive.google.com/file/d/0B3quVdCaxqLfNVFvMHlOWnNnY2M/view?usp=drivesdk[/url]
&
drive.google.com/file/d/0B3quVdCaxqLfc0gyRTBTNGNXOTA/view?usp=drivesdk[/url]
24. Copy these files to your microsd card from earlier, and put back into your j7.
------------> continued to next post of mine!
gggirlgeek said:
Hello,
I wonder if someone would help me FRP unlock my phone. It is a T-mobile sm-J700t 2015. I have searched the forum but don't see a clear answer.
I have tried (from Youtube) the USB cable method, the camera method and flashing the 10/2016 stock firmware through ODIN. In Odin I get an error: "Complete(Write) operation failed". I cannot turn on USB debugging of course because I cannot get into the device. Haven't tried updating with Kies yet because I'm nervous they'll patch any additional back doors I could try.
I am somewhat experienced at flashing and such and I think there must be a way to completely wipe the device and flash new firmware but I don't see instructions for that.
Thanks in advance!
Odin v3.10.7 & v3.12.3
Recovery: Haven't changed
USB installed from Samsung Kies (made sure Kies isn't running)
Firmware: qc3.androidfilehost.com/dl/T2pLZbjUe0enTeLqQNLjsA/1482428974/385035244224401143/J700TUVU2APJ3_J700TTMB2APJ3_TMB.zip"]J700TUVU2APJ3_J700TTMB2APJ3_TMB[/URL].tar.md5
Where I got firmware: qc3.androidfilehost.com/dl/T2pLZbjUe0enTeLqQNLjsA/1482428974/385035244224401143/J700TUVU2APJ3_J700TTMB2APJ3_TMB.zip[/URL]
Click to expand...
Click to collapse

gggirlgeek said:
Hello,
I wonder if someone would help me FRP unlock my phone. It is a T-mobile sm-J700t 2015. I have searched the forum but don't see a clear answer.
I have tried (from Youtube) the USB cable method, the camera method and flashing the 10/2016 stock firmware through ODIN. In Odin I get an error: "Complete(Write) operation failed". I cannot turn on USB debugging of course because I cannot get into the device. Haven't tried updating with Kies yet because I'm nervous they'll patch any additional back doors I could try.
I am somewhat experienced at flashing and such and I think there must be a way to completely wipe the device and flash new firmware but I don't see instructions for that.
Thanks in advance!
Odin v3.10.7 & v3.12.3
Recovery: Haven't changed
USB installed from Samsung Kies (made sure Kies isn't running)
Firmware: J700TUVU2APJ3_J700TTMB2APJ3_TMB.tar.md5
Where I got firmware: https://qc3.androidfilehost.com/dl/...224401143/J700TUVU2APJ3_J700TTMB2APJ3_TMB.zip
Click to expand...
Click to collapse
Its simple. Just flash the latest firmware through odin and you'll be booted on stock.
Don't forget to turn on OEM unlock next time

?guys...no.. just Go to settings tap build 7 times go to developer options, turn on oem unlock, turn on usb debugging.ta dah.

mohitmallick17 said:
Its simple. Just flash the latest firmware through odin and you'll be booted on stock.
Don't forget to turn on OEM unlock next time
Click to expand...
Click to collapse
^^^^^^ Does flashing the latest firmware really work
?????????????????????????????????????????????

victhesunshine said:
^^^^^^ Does flashing the latest firmware really work
?????????????????????????????????????????????
Click to expand...
Click to collapse
Just take out your battery and reboot, turn oem unlock on and do whatever.its simple.

gggirlgeek said:
Hello,
I wonder if someone would help me FRP unlock my phone. It is a T-mobile sm-J700t 2015. I have searched the forum but don't see a clear answer.
I have tried (from Youtube) the USB cable method, the camera method and flashing the 10/2016 stock firmware through ODIN. In Odin I get an error: "Complete(Write) operation failed". I cannot turn on USB debugging of course because I cannot get into the device. Haven't tried updating with Kies yet because I'm nervous they'll patch any additional back doors I could try.
I am somewhat experienced at flashing and such and I think there must be a way to completely wipe the device and flash new firmware but I don't see instructions for that.
Thanks in advance!
Odin v3.10.7 & v3.12.3
Recovery: Haven't changed
USB installed from Samsung Kies (made sure Kies isn't running)
Firmware: J700TUVU2APJ3_J700TTMB2APJ3_TMB.tar.md5
Where I got firmware: https://qc3.androidfilehost.com/dl/...224401143/J700TUVU2APJ3_J700TTMB2APJ3_TMB.zip
Click to expand...
Click to collapse
Saw a same issue please check & follow this steps if it helps you some way.
Download the latest samfirm tool available on xda.
Open the samfirm tool. Enter model and region. Tick Auto and binary nature.
Click on Check update. It will show the latest firmware available on samsung server.
Then click on download. It will download four file full firmware. Then flash it through odin.
You need a strong internet connection to download the file.

fullofhell said:
Just take out your battery and reboot, turn oem unlock on and do whatever.its simple.
Click to expand...
Click to collapse
Not so simple.
During FRP Lock you are restricted to the google sign in page, locked out of everything else. Cannot even pull down the status bar. So no way to get to settings.
This can be done via ADB , but only if you had USB Debugging enabled prior.
I just obtained a used J7000T1 and FRP lock is activated , Even on the bootloader it displays "FRP Locked" . USB Debugging was never enabled .
If I find a way , I'll post. Any one have luck yet?
Once " FRP Locked " is off the bootloader, I'm sure we can just load a recovery / rom via Odin .... But that's where I am a stuck of course.

hightech316 said:
Not so simple.
During FRP Lock you are restricted to the google sign in page, locked out of everything else. Cannot even pull down the status bar. So no way to get to settings.
This can be done via ADB , but only if you had USB Debugging enabled prior.
I just obtained a used J7000T1 and FRP lock is activated , Even on the bootloader it displays "FRP Locked" . USB Debugging was never enabled .
If I find a way , I'll post. Any one have luck yet?
Once " FRP Locked " is off the bootloader, I'm sure we can just load a recovery / rom via Odin .... But that's where I am a stuck of course.
Click to expand...
Click to collapse
I had this happen last Feb when I got the phone and was trying to install twrp, and it says frp lock when I tried flashing the recovery tar via odin. I literally took out the battery rebooted back into the OS and turned on oem unlock and USB Debugging and it was fine then when I flashed twrp. I have never heard of this other issue u speak of. The phone has an unlocked bootloader to begin with. If u are stuck in a Google sign in page, I would download the Samsung z3 tool and make sure u have drivers installed and unlock the frp that way.it does have an option for frp lock

fullofhell said:
I had this happen last Feb when I got the phone and was trying to install twrp, and it says frp lock when I tried flashing the recovery tar via odin. I literally took out the battery rebooted back into the OS and turned on oem unlock and USB Debugging and it was fine then when I flashed twrp. I have never heard of this other issue u speak of. The phone has an unlocked bootloader to begin with. If u are stuck in a Google sign in page, I would download the Samsung z3 tool and make sure u have drivers installed and unlock the frp that way.it does have an option for frp lock
Click to expand...
Click to collapse
Thanks.
Drivers are installed.
Just cannot move from the google sign in.
There is a guide that shows how to use a USB drive with a shortcut apk on it , hooked up via OTG and is able to open settings. Although that did not work for me as well...
Maybe N version is different than MM ?

Almost the same problem here.....but in my j700f, I can't boot to recovery at all...can't flash stock firmware also due frp locked

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.

Xiaomi device bricked after reboot

My Xiaomi Redmi Note 8 Pro isn't booting anymore.
I'm stuck in the fastboot screen, I don't even reach the redmi logo in the boot, I need to recover the data on the phone but I have no idea about how to do that.
Any suggestions?
(Already tried going to recovery with power down + volume up, isn't working)

I'm stuck in the fastboot screen
Click to expand...
Click to collapse
I'm assuming you have Fastboot.
Was USB Debugging ON before the device got bricked? If yes then:
> Download TWRP Recovery for Redmi Note 8 Pro from twrp website. Rename the file to: twrp.img
> Download latest Xiaomi USB Drivers for PC from Internet.
> Download 15-Seconds-ADB-Installer for PC from Internet.
> After Installation is over, Restart PC > Windows Explorer > This PC/ My Computer > ADB Folder > Press SHIFT+Right Click Mouse+Open Powershell Window Here > New window opens
> Transfer the twrp.img file to ADB folder.
> Now you can try connecting the XRN8Pro to the PC (while the Fastboot screen is on)
> On the Powershell window you can type one by one:
1) fastboot devices
2) fastboot boot twrp.img
> Your XRN8Pro phone should boot to TWRP Custom Recovery.
> On PC open another Windows Explorer tab and check if your phones Internal Storage is displayed. If yes you can try to copy your phone data to PC.
> After that in TWRP recovery Press Reboot to Bootloader option, It will show Fastboot screen.
> Download XRN8Pro Stock Firmware/Fastboot ROM from Internet to Desktop only.
> Download Mi Flash Tool for XRN8Pro. Double Click on XiaoMiFlash.exe file.
> Connect XRN8Pro to PC (while fastboot screen is on)
> Then on MiFlash window click on folder to link to firmware file on desktop & click on refresh button, then click on Flash. It takes about 17 minutes (for RN8 devices) to flash MIUI ROM.

OldNoobOne said:
I'm assuming you have Fastboot.
Was USB Debugging ON before the device got bricked? If yes then:
> Download TWRP Recovery for Redmi Note 8 Pro from twrp website. Rename the file to: twrp.img
> Download latest Xiaomi USB Drivers for PC from Internet.
> Download 15-Seconds-ADB-Installer for PC from Internet.
> After Installation is over, Restart PC > Windows Explorer > This PC/ My Computer > ADB Folder > Press SHIFT+Right Click Mouse+Open Powershell Window Here > New window opens
> Transfer the twrp.img file to ADB folder.
> Now you can try connecting the XRN8Pro to the PC (while the Fastboot screen is on)
> On the Powershell window you can type one by one:
1) fastboot devices
2) fastboot boot twrp.img
> Your XRN8Pro phone should boot to TWRP Custom Recovery.
> On PC open another Windows Explorer tab and check if your phones Internal Storage is displayed. If yes you can try to copy your phone data to PC.
> After that in TWRP recovery Press Reboot to Bootloader option, It will show Fastboot screen.
> Download XRN8Pro Stock Firmware/Fastboot ROM from Internet to Desktop only.
> Download Mi Flash Tool for XRN8Pro. Double Click on XiaoMiFlash.exe file.
> Connect XRN8Pro to PC (while fastboot screen is on)
> Then on MiFlash window click on folder to link to firmware file on desktop & click on refresh button, then click on Flash. It takes about 17 minutes (for RN8 devices) to flash MIUI ROM.
Click to expand...
Click to collapse
Thanks for the reply, this game me some hope, but I don't think USB Debugging was enabled.
I've never rooted or changed rom, I just rebooted the phone and apparently I triggered the rm -rf / command.

BrickedXiaomi said:
Thanks for the reply, this game me some hope, but I don't think USB Debugging was enabled.
I've never rooted or changed rom, I just rebooted the phone and apparently I triggered the rm -rf / command.
Click to expand...
Click to collapse
No problem, even then TWRP should allow MTP file transfer to PC, so follow all the steps and tell me what happens ok

OldNoobOne said:
No problem, even then TWRP should allow MTP file transfer to PC, so follow all the steps and tell me what happens ok
Click to expand...
Click to collapse
I'll try tomorrow, thanks for all the precious details btw!

Just a question, shouldn't I unlock the phone with mi unlocker before that?

BrickedXiaomi said:
Just a question, shouldn't I unlock the phone with mi unlocker before that?
Click to expand...
Click to collapse
You hadn't already? OMG! Sorry. Yup probably would need bootloader unlocking but you can try to lookup steps for Fastboot commands to unlock bootloader on the internet. But it shouldn't trigger a wipe of any sort or you might lose the data inside. Also, no harm in trying to load TWRP using Fastboot i think, just in case TWRP loads.

OldNoobOne said:
You hadn't already? OMG! Sorry. Yup probably would need bootloader unlocking but you can try to lookup steps for Fastboot commands to unlock bootloader on the internet. But it shouldn't trigger a wipe of any sort or you might lose the data inside. Also, no harm in trying to load TWRP using Fastboot i think, just in case TWRP loads.
Click to expand...
Click to collapse
As said, I never modified this phone, is basically as if it was brand new, OS side.

Maybe I can use https://forum.xda-developers.com/t/unlock-bootloader-without-losing-data.3864667/ to unlock the bootloader without loosing data?

BrickedXiaomi said:
Maybe I can use https://forum.xda-developers.com/t/unlock-bootloader-without-losing-data.3864667/ to unlock the bootloader without loosing data?
Click to expand...
Click to collapse
Wow thats great link, I hope it works so you don't lose data.
The link is fresh so you can also ask there. All the Best

Update: I've tried to contact Xiaomi about the issue.
They said they should be able to help me out with this stuff, and that I shouldn't flash my phone because it's really easy to brick.
I understand that it's the usual support recommendation, but it is possible that they know how to fix this issue?
What should I do, go for their way or go for myself?

BrickedXiaomi said:
Update: I've tried to contact Xiaomi about the issue.
They said they should be able to help me out with this stuff, and that I shouldn't flash my phone because it's really easy to brick.
I understand that it's the usual support recommendation, but it is possible that they know how to fix this issue?
What should I do, go for their way or go for myself?
Click to expand...
Click to collapse
Is your phone In-Warranty? If yes or no i would suggest go your own way, once purchased an used any device, don't connect with OEM servers ever again for any OTA update coz lots of recent cases about OEM(Original Equipment Manufatureres) killing devices with OTA updates and after that the phone doesnt boot, no recovery no fastboot too, so careful with contacting/updating through OEMs if out -of-warranty specially. Once out-of-warranty always use ROM channels to upgrade to new handroid versions instead of direct OTA upgrade/update, that way you may still be able to roll back the OS to previous version in case you don't like the new handroid version, lots of people don't like handroid 12 but they cant roll back to handroid 11 .

> recent cases about OEM(Original Equipment Manufatureres) killing devices with OTA updates
This is considered highly illegal in Europe, I could sue Xiaomi for that, in case, and would be an easy win.
Btw, I'm the one who bought this phone first, it's just out of warranty since I've bought it in nov-19.
After this data recovery I'll be out of the Android world forever, I just care about my data, currently.

BrickedXiaomi said:
> recent cases about OEM(Original Equipment Manufatureres) killing devices with OTA updates
This is considered highly illegal in Europe, I could sue Xiaomi for that, in case, and would be an easy win.
Btw, I'm the one who bought this phone first, it's just out of warranty since I've bought it in nov-19.
After this data recovery I'll be out of the Android world forever, I just care about my data, currently.
Click to expand...
Click to collapse
Yes they might not try doing that with uropean customers but they might try in other countries where there no proper legal system for things like these, also they wont do it with everyone in a particular country to avoid suspicion, theyre smart enough to know what theyre doing, but unofficially speaking many retailers have told me about such a thing (OTA Kill Device) happening in Weaker-Law-N-Order countries, so just saying precaution is always good.

BTW i've put my Retmi Noat 10 up for sale, its still in warranty & I havent used it in the last 10 months, no sim card, unused totally, just once I loaded Gcam to check how the camera is, shamshung is always better than chyneez phones mainly coz better build and component-life, chyneez devices only look shiny from outside but it doesnt last beyond 3-5 yrs, not built to last, just use-n-throw devices u knw. Such devices are only made for mass-surveillance in mind not with customers-focus. This A/B partition thing and super partition thing is adding more bad than good.

I don't think that trick will work. even if it would be possible to cheat that easy, encryption key is bonded* to bootloader lock state. so if you somehow magically managed to unlock bootloader without triggering factory reset, your data could no longer decrypted from android OS and is therefore lost.
Xiaomi support answered they can fix your phone, but they didn't say they can safe your data on it, right!? So try to get a full backup off your device in preloader mode (SLA/DAA bypass and VCOM drivers needed)
After that important step you can unlock bootloader with mtkclient, install TWRP and *proof me wrong (xiaomi devices are hackable/have weak security implementations). In any case do not perform factory reset, your backup is always only backup of android OS and therefore incomplete (there are several OS on every device)
btw fastboot doesn't require usb-debugging (that's adb, not fastboot)

Do you have a tutorial about it?
aIecxs said:
I don't think that trick will work. even if it would be possible to cheat that easy, encryption key is bonded to bootloader lock state. so if you somehow magically managed to unlock bootloader without triggering factory reset, your data could no longer decrypted from android OS and is therefore lost.
Xiaomi support answered they can fix your phone, but they didn't say they can safe your data on it, right!? So try to get a full backup of your device in EDL mode (patched firehose programmer and deep flash cable needed)
Click to expand...
Click to collapse

Question Hidden oem unlock

I upgraded to android 12. Oem unlock is not visible. I went back to android 11 and it still doesn't show. help

hhhhhhhhheeelllpp

And i search on recovery mode tap bootloader but i see black screen

is there no one to answer on huge xda? interesting

I think you can just use the official OEM unlock too app to one-step unlock the BL....

asus bootloader unlock tool apk. I tried maybe 20 times and it didn't work
yurishouse said:
I think you can just use the official OEM unlock too app to one-step unlock the BL....
Click to expand...
Click to collapse

I did not understand anything.
OEM unlock does not visible in developer options. I cannot enter the bootloader in the recovery menu. asus unlock tool.apk doesn't work.
i regret buying an asus phone

Robocop36 said:
I did not understand anything.
OEM unlock does not visible in developer options. I cannot enter the bootloader in the recovery menu. asus unlock tool.apk doesn't work.
i regret buying an asus phone
Click to expand...
Click to collapse
This device does not have OEM unlock. Contact ASUS to try and resolve the issue with the unlock app but I suspect you have a converted phone that is getting rejected by the ASUS side. Attempting too fix it yourself will involve amending some device parameters, I think someone has added some notes somewhere on the forums here..

I made a comment on asus zentalk. I've been waiting for a week, no answer. There are 20 moderators, but one person is not responding. a disgraceful place.
Hey man i went to the internet cafe yesterday to install raw firmware. I downloaded win10 asus qualcom usb drivers , downloaded usb minimal android sdk, pressed the volume up power button, the computer did not see my phone on the start screen, I tried many times and it didn't work.
The computer sees the phone without entering the start screen. I even copied 40 movies to the phone. but every time I press the volume up/power button the computer does not see the phone when the start screen comes up.

Andrologic said:
This device does not have OEM unlock. Contact ASUS to try and resolve the issue with the unlock app but I suspect you have a converted phone that is getting rejected by the ASUS side. Attempting too fix it yourself will involve amending some device parameters, I think someone has added some notes somewhere on the forums here..
Click to expand...
Click to collapse
If I try this, will the computer see my phone on the start screen?
ASUS Android Bootloader Interface Drivers Download for Windows 10, 8.1, 7, Vista, XP
Download the latest drivers for your ASUS Android Bootloader Interface to keep your Computer up-to-date.
www.driverscape.com

hhhhhhhheeeeeellppppp

It had HTC, Samsung, Xiaomi. I switched to ASUS. maybe my version is cn but the chinese changed it to ww! I didn't know it was like this i wouldn't have bought this phone had I known.

How do I get out of this job? I risk losing imei and more. maybe my device will be hard bricked. Flashing raw software takes a lot of effort. first of all, my computer doesn't see my device on the start screen, I couldn't even take a step. I unlocked the bootloader hundreds of times on my previous phones. I rooted hundreds of times , I installed custom roms hundreds of times,. but I could not progress even one step on the Asus phone.

Robocop36 said:
If I try this, will the computer see my phone on the start screen?
ASUS Android Bootloader Interface Drivers Download for Windows 10, 8.1, 7, Vista, XP
Download the latest drivers for your ASUS Android Bootloader Interface to keep your Computer up-to-date.
www.driverscape.com
Click to expand...
Click to collapse
Suggest using the orginal Andrid driver directly from Google. There is no specific ASUS drivers needed for this device although the one in your link may work too. And yes, you do need to sort out your driver before you can flash from PC to the device with Fastboot commands.

Andrologic said:
Suggest using the orginal Andrid driver directly from Google. There is no specific ASUS drivers needed for this device although the one in your link may work too. And yes, you do need to sort out your driver before you can flash from PC to the device with Fastboot commands.
Click to expand...
Click to collapse
Ok

Hi, your device seems to be a converted chinese version (with Tencent Games on the back) so you need to use this method to spoof the region if your phone and force the bootloader unlock: https://forum.xda-developers.com/t/...the-bootloader-of-your-rog-phone5-5s.4371255/

Saying and complaining ain't gonna help you out.
Lost people don't wanna reply as this is covered many times and can be found with search option on this forum.
Anyway his is relevant info for you :
1: The usb c port needed to use to flash etc in bootloader mode is on the side, NOT the bottom one.
2 : if option 1 this Still not working add device manual in driver section of computer, then is driver problem.
3: adb drivers/software/map with adb commands etc needs to be present on computer, or commands will not be executed correctly and give error.
4: of you have a Chinese phone CN FW that is flashed with the WW firmware, you will get problems, only way to solve this is to use correct firmware on device and upgrade.
This is also covered in a big topic on this forum.
5: of you need to go to a internet cafe do to flashing and install firmware, and you had Samsung xaomi etc and can't work this out yourself or Ith search option, o ask myself if you should mess with the phone in the first place,
When it goes wrong, it is bad phone, crap etc.... While it is user error. No hard feelings.
Hope you know enough now and get it fixed
Sending from Rog 5 ultimate android12 fw ww91 unlocked and rooted.

Read this : https://forum.xda-developers.com/t/...the-bootloader-of-your-rog-phone5-5s.4371255/

1: i was plugging it into the bottom usb c port not the side usb c port I'll try it when I have free time. thank you all so much