Related
Hello,
So I'm trying to unlock and root my tf700t now that my warranty is expired and hope for an ASUS update is diminishing. I downloaded the unlock app from the website and went through the procedure. It took a few weeks and several emails with ASUS support but I think it is unlocked. The reason I say I think its unlocked is whenever I reboot the device, I don't get the message that says its unlocked. The unlock app however says the device is unlocked. So is my device unlocked?
I operated under the assumption that it was and tried to install the twrp recovery using the minimal adb and fastboot exe file. My tablet is recognized by my PC and I put the tablet in fastboot. The error I get when I do that is a writing error. It says writing recovery.... FAILED <remote: <INVALID STATE>>. Does this mean that I am not unlocked or did I do something incorrectly? Any help would be appreciated. I've been working on this for a few weeks and really want to get it moving.
Never heard that before..... If your bootlaoder is unlocked it should say so when you boot up.
Did you run the tool again?
If in doubt call Asus support and check if they have it as unlocked in their database.
But my guess is, since the recovery flash did not take, it's not.
berndblb said:
Never heard that before..... If your bootlaoder is unlocked it should say so when you boot up.
Did you run the tool again?
If in doubt call Asus support and check if they have it as unlocked in their database.
But my guess is, since the recovery flash did not take, it's not.
Click to expand...
Click to collapse
They contacted me today and told me that it is unlocked. Everytime I run the tool, It says the device is unlocked. When I do the power + Vol down, I get the three icons ( RCK, Wipe data, and an android). Ill try applying the recovery again later tonight.
Jkeeper18 said:
They contacted me today and told me that it is unlocked. Everytime I run the tool, It says the device is unlocked. When I do the power + Vol down, I get the three icons ( RCK, Wipe data, and an android). Ill try applying the recovery again later tonight.
Click to expand...
Click to collapse
Sounds like you are all set. You run fast boot from a pc when connected over USB and on that screen with 3 icons If it fails you have a driver issue.
sbdags said:
Sounds like you are all set. You run fast boot from a pc when connected over USB and on that screen with 3 icons If it fails you have a driver issue.
Click to expand...
Click to collapse
I attached a picture of the message I get from the minimal ADB tool. I'm also using the universal Drivers ( the ASUS Fastboot Interface). I tried the ASUS Android Bootloader Interface as well.
Jkeeper18 said:
I attached a picture of the message I get from the minimal ADB tool. I'm also using the universal Drivers ( the ASUS Fastboot Interface). I tried the ASUS Android Bootloader Interface as well.
Click to expand...
Click to collapse
I suspect your bootloader ist not unlocked.
Post a screen shot of when you issue the command 'fastboot devices' please.
berndblb said:
I suspect your bootloader ist not unlocked.
Post a screen shot of when you issue the command 'fastboot devices' please.
Click to expand...
Click to collapse
It says waiting for device. It stayed that way until i manually put it into fastboot. I've attached a screen shot of what it looks like when i did that. If my tablet isnt unlocked, how would I get it unlocked then? The unlock app ( both version) says the device is unlocked.
I am in the same boat - they think it is unlocked but it is not
The Asus v7 and v8 bootloaders both say "device is unlocked" but the fastbook info shows that it is not. I do not see any unlock inormation after the boot process starts. Also , the unlocker did not automatically restart my tablet. It also asked for my google credentials the first 5 times until the unlock said it worked. Now it does not ask that, it just says that it is unlocked. When I try to fastboot install the TWRP rom, it fails.
(remote - invalid state)
I called Asus and they have my tabler listed as unlocked. They are opening a case so that I can prove that it is unlocked.Then hopfully if they reset that setting, I can re-unlock it...
I was following this thread:
http://forum.xda-developers.com/showthread.php?t=2571542
Is there any work around? Please help!
I want TWRP and CM 10.2 on this slow TF700T tablet.
Thanks!
Jkeeper18 said:
It says waiting for device. It stayed that way until i manually put it into fastboot. I've attached a screen shot of what it looks like when i did that. If my tablet isnt unlocked, how would I get it unlocked then? The unlock app ( both version) says the device is unlocked.
Click to expand...
Click to collapse
Well you typed fastboot device not fastboot devices.
Did you 2-step verification enabled for Google by any chance?
I think Asus need to update their database so you get another chance ... Good luck
Sent from my XT894 using Tapatalk
berndblb said:
Did you 2-step verification enabled for Google by any chance?
I think Asus need to update their database so you get another chance ... Good luck
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
No, I did not have two-step verification. I hope Asus creates a case and actually looks into it and resets my device's status in their system. It sounds like that is my only option -- a very lengthy and painful one.
I disabled 2 step authentication since it interfered with the app. I would get invalid password errors until I disabled it and then the app worked.
Well you typed fastboot device not fastboot devices.
Click to expand...
Click to collapse
I attached a picture of what happens when I type the command fastboot devices. It looks like my device is not unlocked and Im going to have to contact ASUS. Are there any other tools that would unlock the device?
Jkeeper18 said:
I disabled 2 step authentication since it interfered with the app. I would get invalid password errors until I disabled it and then the app worked.
I attached a picture of what happens when I type the command fastboot devices. It looks like my device is not unlocked and Im going to have to contact ASUS. Are there any other tools that would unlock the device?
Click to expand...
Click to collapse
Are you sure your device gets recognized at all by your computer?
Usually the dialog just stays on "waiting for device" if the computer detects anything attached.
You have the necessary drivers installed?
Check in Device Manager (if you are running Windows) if there is a yellow triangle next to the entry for your tablet.
There is no other way to unlock. The bootloader is encrypted and only Asus has the key.
berndblb said:
Are you sure your device gets recognized at all by your computer?
Usually the dialog just stays on "waiting for device" if the computer detects anything attached.
You have the necessary drivers installed?
Check in Device Manager (if you are running Windows) if there is a yellow triangle next to the entry for your tablet.
There is no other way to unlock. The bootloader is encrypted and only Asus has the key.
Click to expand...
Click to collapse
The device is recognized by the computer. It says waiting for device when i type in "fastboot device" instead of "fastboot devices". Theres no yellow triangle either. I've sent an email to ASUS and I'm waiting on their reply.
Jkeeper18 said:
The device is recognized by the computer. It says waiting for device when i type in "fastboot device" instead of "fastboot devices". Theres no yellow triangle either. I've sent an email to ASUS and I'm waiting on their reply.
Click to expand...
Click to collapse
Fastboot device doesn't do anything.
I think you just need the right drivers. Let me see if I can dig them up from my collection. No point contacting Asus, they won't help you.
Try these, you need to unzip to same folder as fastboot and update device manager when in fastboot.
http://www.androidfilehost.com/?fid=23212708291675384
sbdags said:
Fastboot device doesn't do anything.
I think you just need the right drivers. Let me see if I can dig them up from my collection. No point contacting Asus, they won't help you.
Try these, you need to unzip to same folder as fastboot and update device manager when in fastboot.
http://www.androidfilehost.com/?fid=23212708291675384
Click to expand...
Click to collapse
Sorry Im still new at this. Where is the fastboot folder?
Jkeeper18 said:
Sorry Im still new at this. Where is the fastboot folder?
Click to expand...
Click to collapse
Where ever you are running fast boot from.
You must open a cmd window in the same directory or change to it using the CD command.
sbdags said:
Where ever you are running fast boot from.
You must open a cmd window in the same directory or change to it using the CD command.
Click to expand...
Click to collapse
So I've been trying for the past couple of days to get root and flash a new rom but it doesnt seem to be working. I've contacted ASUS and they said my tablet is unlocked as of December 16th but they will contact Taiwan to see if something is wrong. Do i have any options if they say the same thing? Thanks again for all your help. I appreciate it.
Jkeeper18 said:
So I've been trying for the past couple of days to get root and flash a new rom but it doesnt seem to be working. I've contacted ASUS and they said my tablet is unlocked as of December 16th but they will contact Taiwan to see if something is wrong. Do i have any options if they say the same thing? Thanks again for all your help. I appreciate it.
Click to expand...
Click to collapse
I have followed the TF700 forums for the last year pretty extensively and until about 2 weeks ago never read about anyone having this problem: Asus database having you unlocked, but it actually isn't. Since then I think I've read about 4 cases.
My best guess: It's a problem with the v8 Unlock app or the way their servers store/process the information they get from the Unlock Tool.
That you got to a support person willing to contact Taiwan is a big plus already. Other users just ran into a wall of: We do not support unlocking this device.
So stick with the person you contacted already. Take pictures of your boot process (to document that it does NOT say: This device is unlocked) and they always seem to ask for a screen shot of your About Tablet page with your SN number and MAC address.
Persistence seems to be the key. And luck to get someone at Asus willing to help....
There is no other way to unlock the bootloader. So you would be limited to rooting the tablet which would give you more freedom to tweak it and uninstall bloatware, but you still would have to deal with the slow stock rom.... :fingerscrossed:
It was late and I was cleaning up my old OP5T, getting it ready to sell. I thought I had plugged in my OP5T, but I still had my OP6 plugged in when I ran "fastboot oem lock". Now it won't boot and I can't unlock it (I'm assuming because I can't get into the OS and "enable OEM unlocking" anymore).
Is there anything I can do?
try using search next time because its already been talked abput here https://forum.xda-developers.com/oneplus-6/help/relock-bootloader-t3798135
Actually, I DID read that. I didn't just roll off the cabbage truck. If you have time to post snippy replies (I also searched YOUR post history), then maybe you can point out where in that thread the answer to my question is. I could see if there was a thread where this specifically happened, or if it had been talked about over and over, but I couldn't find one. You do know this is a fairly new device, right? TBH, you're just being rude. To count on someone to hit the right search terms for a single thread where the info exists is just asinine.
1) I have not seen anyone with this situation on the OP6 yet
2) The OP5T had an unbrick tool
3) Most phones have a way to restore the OS to factory
If it can't be restored without calling OnePlus, then why not just say so? I'll answer for you, it's because you actually enjoy replying in such a manner. Grow up.
Have you tried the mega unbrick guide?
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
Flapjack said:
It was late and I was cleaning up my old OP5T, getting it ready to sell. I thought I had plugged in my OP5T, but I still had my OP6 plugged in when I ran "fastboot oem lock". Now it won't boot and I can't unlock it (I'm assuming because I can't get into the OS and "enable OEM unlocking" anymore).
Is there anything I can do?
Click to expand...
Click to collapse
I don't think relocking your bootloader will disable the "enable OEM unlock" toggle in the OS. You may just be able to unlock your bootloader as normal again. You should be able to use the fastboot recovery method to restore your OS.
[email protected] said:
Have you tried the mega unbrick guide?
https://forum.xda-developers.com/oneplus-6/how-to/guide-mega-unbrick-guide-hard-bricked-t3796051
Click to expand...
Click to collapse
I did, but I got the "software image does not exist" error. Does it matter whether I downloaded the 5.13 or 5.15 vesion?
mikex8593 said:
I don't think relocking your bootloader will disable the "enable OEM unlock" toggle in the OS. You may just be able to unlock your bootloader as normal again. You should be able to use the fastboot recovery method to restore your OS.
Click to expand...
Click to collapse
I tried several times. It throws the following error, which when searched for, always seemed to be someone forgetting to enable OEM unlocking in settings:
Code:
FAILED (remote: oem unlock is not allowed)
Success! I was able to get it to work with the drivers from this post. No other drivers worked. I also forced the COM port to the first available (in my case, COM1) vs the one it popped up on. Until I did that, I would just get a huge list of ports that had no device attached. Once I had it on COM1, it was the only device that showed up in the list. The first time after that, I got a "Sahara Communication Failed" error, but it went away after rebooting the phone back into EDL mode again.
Thanks for the help!
Flapjack said:
Success! I was able to get it to work with the drivers from this post. No other drivers worked. I also forced the COM port to the first available (in my case, COM1) vs the one it popped up on. Until I did that, I would just get a huge list of ports that had no device attached. Once I had it on COM1, it was the only device that showed up in the list. The first time after that, I got a "Sahara Communication Failed" error, but it went away after rebooting the phone back into EDL mode again.
Thanks for the help!
Click to expand...
Click to collapse
Hi buddy,
I tired to relock the bootloader and success in that but the phone stuck at fastboot mode, neither restarting to system nor to anything. Kindly help me if i can flash the stock rom in locked bootloader is so how.
THanks in adv
Did you try msm download tool ?
My OnePlus was bricked and it's bootloader is locked too, I have tried most of the steps like msm and those Bat files etc. But error is coming
"Remote : Flashing is not allowed in locked state"
Even tried that all in one tool that also can't unlock my bootloader
Now plz someone show me steps it will be a great help
Hello,
So, apparently i messed up. I installed nethunter on my phone, everything was working well, finished the configuration and then i had the idiotic idea to lock the bootloader since it was locked at the beginning when i received the phone, so i locked the bootloader not knowing the consequences of that.
Now i don't have how to go to enter in recovery mode, i can't boot. The program adb and fastboot doesn't detect the phone when i do adb devices or fastboot devices. I don't know how to proceed from here.
Any ideas ?
Kind regards,
C666PO said:
Hello,
So, apparently i messed up. I installed nethunter on my phone, everything was working well, finished the configuration and then i had the idiotic idea to lock the bootloader since it was locked at the beginning when i received the phone, so i locked the bootloader not knowing the consequences of that.
Now i don't have how to go to enter in recovery mode, i can't boot. The program adb and fastboot doesn't detect the phone when i do adb devices or fastboot devices. I don't know how to proceed from here.
Any ideas ?
Kind regards,
Click to expand...
Click to collapse
Yes,there are several unbrick tools on the forum i used this one and it worked for me!
I am not able to share links so im posting a few screew shots but if you google oneplus 7 pro unbrick you ahould find this thread easy
C666PO said:
Hello,
So, apparently i messed up. I installed nethunter on my phone, everything was working well, finished the configuration and then i had the idiotic idea to lock the bootloader since it was locked at the beginning when i received the phone, so i locked the bootloader not knowing the consequences of that.
Now i don't have how to go to enter in recovery mode, i can't boot. The program adb and fastboot doesn't detect the phone when i do adb devices or fastboot devices. I don't know how to proceed from here.
Any ideas ?
Kind regards,
Click to expand...
Click to collapse
I replied to you from the xda labs app and i couldnt attach a link but it works from the browser so i apologise for my first reply hope this one is more helpfull
https://forum.xda-developers.com/on...mega-unbrick-guide-hard-bricked-t3934659/amp/
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.
Hello, i wanted to ask how to fix the fastboot mode.
Everytime when i try to access it, it just says "Entering Fastboot..."and thats all.
I dont want to close it, thats not my problem, i just wanna flash a recovery.img, and the fastboot seems not working. Any ideas?
M3DUS4 said:
Hello, i wanted to ask how to fix the fastboot mode.
Everytime when i try to access it, it just says "Entering Fastboot..."and thats all.
I dont want to close it, thats not my problem, i just wanna flash a recovery.img, and the fastboot seems not working. Any ideas?
Click to expand...
Click to collapse
this could be because the galaxy A51 wasnt built with fastboot, and the code to launch this option was just reused from a different device, or because something isnt connecting properly.
Hello, I have the same ... Android 11 (and currently 12) (from Frija). So it is not the fault of incorrect configuration or with connecting. Only something is wrong with this phone ...
I have this device and this solved it for me:
Enable OEM unlocking in developer settings
Shut down the phone
Hold volume up and volume down
Plug in a USB cable connected to a computer (the computer being turned on)
Keep holding
You're in download mode!
Side note: This might not work in USA or Canada, I am from europe and it works here. I have no idea if it works in another region. Also, you can't just flash a recovery.img on Samsung since there is no real "fastboot", you have to use download mode and Odin.
But I know how to enter download mode... Problem is Fastboot mode...
There is no fastboot mode on a modern Samsung device. If there is, it's fake and you cannot flash anything with it. As you can see even from Wikipedia, Odin is the Samsung replacement of fastboot.
So no fastboot, only download mode.
If a guide is saying to use fastboot, it is not compatible with Samsung.
If you would tell me why you specifically need fastboot, I'll be happy to tell you how you can do it with Odin, if possible.
Because I have Samsung Galaxy A51 5G (A516B) with new Android 12 and I can't do a root! Because I can't upload TWRP (custom recovery) because I haven't OEM unlock option in Deveoper Option. I tried trick with set back date by 7days but not succes. Everything I;ve metioned here - I did at my phone with Android 11.
And... I have read that I can turn this fu**ing OEM option by comend at ADB: fastboot oem unlock.
Phew ...
So this fastboot method is the last method to do a root with my phone.
Upload TWRP by Odin in download mode -ends red warning - of corse...
Have you any ideas?
I would be grateful for help...
I have read this fastboot method at:
How to Unlock Bootloader On Samsung Galaxy Phones [EASY GUIDE]
Are you looking for a Complete tutorial on How To Unlock Bootloader on Samsung Galaxy Phones? If yes, then you have come to the right place.
www.guidetoroot.com
Yeah, that guide is not relevant on any modern Samsung device. Besides, even if it was, which it isn't, you would first need to enable OEM unlocking from the Developer Settings.
But the fact that you don't have an option for OEM unlock is weird, since I have the exact same device model and it is there for me.
May I ask what is your region and is your phone locked to a telephone carrier?
My region is PLS - Poland. And not - phone is not locked. Have you the newest system Android 12?
Yes, I do. It's weird that there isn't even an option for you.
I'll try to come up with some new ideas if I have time...
I'll be glad for it...
Hej, do you have any idea?
stanwin said:
Hej, do you have any idea?
Click to expand...
Click to collapse
Have you tried everything listed here?
BloodyFruitDestroyer said:
Have you tried everything listed here?
Click to expand...
Click to collapse
Yes, I did. Evething exept the last one...
You could try it. It might be risky, but it's the only option I personally can come up with right now.
I've tried this option but Odin stuck on "files verification". Any help?
have any of you encountered this problem?
And how did you solve it?
You can also try searching for combination firmware for your device online