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
If you try to use the bootloader unlocker apk from Nokia and your Nokia 8 has an android version that's past a certain version, the apk will flat out fail with a "Device not support." error message. And chances are, your Nokia 8 will be at an incompatible android version. So to unlock the bootloader, you will need to downgrade your phone to a legitimate version of android 8.1.0 so the apk will not error out and get you a verification code. This guide will show you how. NOTE THAT THIS METHOD WILL ERASE ALL INTERNAL DATA ON YOUR PHONE.
-
This update zip is what you need for the TA-1004: https://android.googleapis.com/pack.../f9cb380bd9c2bf1b6ddebcab9dcf389843eb2d39.zip
It may be different for the TA-1012, but according to that earlier post, it does not seem to be the case. Nevertheless, just to be safe, here's the zip for the TA-1012: https://android.googleapis.com/pack.../139c94fd08f52fbd3b852ab4ef5c6515fffb784e.zip (I don't have a TA-1012 so I wasn't able to test this particular zip.)
So basically, to make sure there's no problems, make sure in the Developer's options on the phone that OEM unlocking is enabled, then put your SD card into the phone. Plug the phone into your computer. Copy the update zip that you need somewhere onto the SD card. Disconnect the USB cable. Shut down the phone. Then, while holding down the Volume Up button, reconnect the USB cable. You should see a sad android with "No command" displayed. Now release the Volume Up button. Then hold down the power button and then JUST PRESS once on the Volume Up button. You should be at a recovery menu. Using the volume keys, scroll down to the 'Apply update on SD card' option and select it. Select the zip that you copied over to the SD card earlier and then let it install for a while. It will probably pop up with a 'timestamp too old' error, but just ignore this. The update will install anyway. Then once it's done, do a factory reset on the phone and then shut down. MAKE SURE THERE'S NO SIM CARD IN THE PHONE.
Now that's out of the way, boot the phone up again and just click through the first-time setup screens but DO NOT ENABLE WI-FI or any kind of internet connection. We don't want the phone to update itself back to Android 9. Now plug the phone in again. Copy the bootloaderunlocker apk from Nokia's website onto the phone. Install it. Put in the email address you want the unlock key emailed to. Then voila! You'll get the verification code. Put it into the form on Nokia's website and you'll be emailed an unlock.key file. From there, the site will tell you how to proceed.
A HUGE thanks to: THMSP and frankoid
They did all the work. <3
why another topic ?!
foxbatul said:
why another topic ?!
Click to expand...
Click to collapse
Because I don't expect people to dig around in all the Nokia 8 Guide threads to find the exact and, to my knowledge, only way to unlock the bootloader. Furthermore, I found this solution in a sort of unrelated thread, which would make the solution even harder to find for the average user.
S5Guy said:
Because I don't expect people to dig around in all the Nokia 8 Guide threads to find the exact and, to my knowledge, only way to unlock the bootloader. Furthermore, I found this solution in a sort of unrelated thread, which would make the solution even harder to find for the average user.
Click to expand...
Click to collapse
I understant but not.
Here it's not the place for lazy ones. Or for apple boys.
Unlock, modding, ROMs are for people with other approach. So this kind of topics make more noise instead to help.
Just my 2 cents.
BTW - thank you posting "downgrade to oreo" procedure.
it s the offline one ( my choice was to use "register to beta" and" unregister").
no need SD card or something, just a good wifi connection and patience.
Thanks for this. I just noticed that the "OEM unlocking" is disabled and greyed out on my TA-1012 device. Will it still work?
I cant get into the Phone without establishing an Internet connection, any tips?
Thank you so much OP this method worked perfectly I finally was able to unlock the bootloader
There seems no way for me to get past the Wifi selection page, how did all of you got into the system?
Ok solved this one, had to Update to P remove the Google Account linked to the Device and downgrade again.
It's Part of the Factory Reset Protection that you cant skip the Wifi and Update Screens.
Thank you for posting this guide, it got me to unlocking the bootloader on my TA-1004 after I received the described "Device not support" error.
I enabled "OEM unlocking" before downgrading my firmware and the option was grayed out for me afterwards. However the bootloader unlock still worked correctly other than being forced to us a Mac as none of my windows machines would show the device in fastboot mode.
ma401 said:
Thank you for posting this guide, it got me to unlocking the bootloader on my TA-1004 after I received the described "Device not support" error.
I enabled "OEM unlocking" before downgrading my firmware and the option was grayed out for me afterwards. However the bootloader unlock still worked correctly other than being forced to us a Mac as none of my windows machines would show the device in fastboot mode.
Click to expand...
Click to collapse
If only Nokia 8 had support for custom roms. Im stuck on the december security patch of Pie because it has a prerooted boot img posted somewhere on this forum. Ot would be fun to play around with a google-free custom rom like lineageOS. But sadly devs dont seem to give a damn about the phone
MDV106 said:
If only Nokia 8 had support for custom roms. Im stuck on the december security patch of Pie because it has a prerooted boot img posted somewhere on this forum. Ot would be fun to play around with a google-free custom rom like lineageOS. But sadly devs dont seem to give a damn about the phone
Click to expand...
Click to collapse
I think we can thank HMD for that by making unlocking the bootloader so difficult. I only ended up buying the Nokia 8 because I got it for such a good deal ($220 CAD) and needed a temporary phone to tide me over until I can get something better. I feel sorry for anyone who paid full price for this phone and I don't blame developers for moving to something more accessible.
S5Guy said:
If you try to use the bootloader unlocker apk from Nokia and your Nokia 8 has an android version that's past a certain version, the apk will flat out fail with a "Device not support." error message. And chances are, your Nokia 8 will be at an incompatible android version. So to unlock the bootloader, you will need to downgrade your phone to a legitimate version of android 8.1.0 so the apk will not error out and get you a verification code. This guide will show you how. NOTE THAT THIS METHOD WILL ERASE ALL INTERNAL DATA ON YOUR PHONE.
-
This update zip is what you need for the TA-1004: https://android.googleapis.com/pack.../f9cb380bd9c2bf1b6ddebcab9dcf389843eb2d39.zip
It may be different for the TA-1012, but according to that earlier post, it does not seem to be the case. Nevertheless, just to be safe, here's the zip for the TA-1012: https://android.googleapis.com/pack.../139c94fd08f52fbd3b852ab4ef5c6515fffb784e.zip (I don't have a TA-1012 so I wasn't able to test this particular zip.)
So basically, to make sure there's no problems, make sure in the Developer's options on the phone that OEM unlocking is enabled, then put your SD card into the phone. Plug the phone into your computer. Copy the update zip that you need somewhere onto the SD card. Disconnect the USB cable. Shut down the phone. Then, while holding down the Volume Up button, reconnect the USB cable. You should see a sad android with "No command" displayed. Now release the Volume Up button. Then hold down the power button and then JUST PRESS once on the Volume Up button. You should be at a recovery menu. Using the volume keys, scroll down to the 'Apply update on SD card' option and select it. Select the zip that you copied over to the SD card earlier and then let it install for a while. It will probably pop up with a 'timestamp too old' error, but just ignore this. The update will install anyway. Then once it's done, do a factory reset on the phone and then shut down. MAKE SURE THERE'S NO SIM CARD IN THE PHONE.
Now that's out of the way, boot the phone up again and just click through the first-time setup screens but DO NOT ENABLE WI-FI or any kind of internet connection. We don't want the phone to update itself back to Android 9. Now plug the phone in again. Copy the bootloaderunlocker apk from Nokia's website onto the phone. Install it. Put in the email address you want the unlock key emailed to. Then voila! You'll get the verification code. Put it into the form on Nokia's website and you'll be emailed an unlock.key file. From there, the site will tell you how to proceed.
A HUGE thanks to: THMSP and frankoid
They did all the work. <3
Click to expand...
Click to collapse
Hello i too tried unlocking my nokia 8 but the laptop doesnt recognise my phone in fastboot Mode.i need help i installed all drivers but the same problem arises
shivaji namburu said:
Hello i too tried unlocking my nokia 8 but the laptop doesnt recognise my phone in fastboot Mode.i need help i installed all drivers but the same problem arises
Click to expand...
Click to collapse
try fastboot -i 0x2e04 [Your_Command]
sumitinhome said:
try fastboot -i 0x2e04 [Your_Command]
Click to expand...
Click to collapse
Actually even pc doesnt detect the device and it doesn't show in my pc section
---------- Post added at 04:57 PM ---------- Previous post was at 04:55 PM ----------
sumitinhome said:
try fastboot -i 0x2e04 [Your_Command]
Click to expand...
Click to collapse
What is that i didn't get it will it work.....?
If possible put the command clearly ....to understand
shivaji namburu said:
Actually even pc doesnt detect the device and it doesn't show in my pc section
---------- Post added at 04:57 PM ---------- Previous post was at 04:55 PM ----------
What is that i didn't get it will it work.....?
If possible put the command clearly ....to understand
Click to expand...
Click to collapse
If pc is not detecting the phone the its driver problem. try to install proper drivers.
sumitinhome said:
If pc is not detecting the phone the its driver problem. try to install proper drivers.
Click to expand...
Click to collapse
I mean it detects when the phone is in nornal mode but when mobile is booted into fastboot mode it doesn't detect
shivaji namburu said:
I mean it detects when the phone is in nornal mode but when mobile is booted into fastboot mode it doesn't detect
Click to expand...
Click to collapse
Yes i understood, make sure you are using latest adb drivers.
More on it. Make sure you have USB debugging on from Developers options. Also make sure oem unlocking option is on.
1 - Connect your phone to pc while powered on.
2 - From adb folder open command prompt and type adb devices (If your device is detected in adb mode while powered on)
2.1 - if not detected in adb devices.. then go to developer settings and revoke USB debugging authorizations. then again repeat the above process in point no. 2.
3 - if detected now then type adb reboot bootloader, let it reboot in download mode.
4. then type 'fastboot flash unlock [your unlock key]' if this doesnt work then try 'fastboot -i 0x2e04 flash unlock [unlock key]'
5. after that either 'fastboot oem unlock' or 'fastboot -i 0x2e04 oem unlock'
See if this works.
Struck on Nokia Logo
S5Guy said:
If you try to use the bootloader unlocker apk from Nokia and your Nokia 8 has an android version that's past a certain version, the apk will flat out fail with a "Device not support." error message. And chances are, your Nokia 8 will be at an incompatible android version. So to unlock the bootloader, you will need to downgrade your phone to a legitimate version of android 8.1.0 so the apk will not error out and get you a verification code. This guide will show you how. NOTE THAT THIS METHOD WILL ERASE ALL INTERNAL DATA ON YOUR PHONE.
-
This update zip is what you need for the TA-1004: https://android.googleapis.com/pack.../f9cb380bd9c2bf1b6ddebcab9dcf389843eb2d39.zip
It may be different for the TA-1012, but according to that earlier post, it does not seem to be the case. Nevertheless, just to be safe, here's the zip for the TA-1012: https://android.googleapis.com/pack.../139c94fd08f52fbd3b852ab4ef5c6515fffb784e.zip (I don't have a TA-1012 so I wasn't able to test this particular zip.)
So basically, to make sure there's no problems, make sure in the Developer's options on the phone that OEM unlocking is enabled, then put your SD card into the phone. Plug the phone into your computer. Copy the update zip that you need somewhere onto the SD card. Disconnect the USB cable. Shut down the phone. Then, while holding down the Volume Up button, reconnect the USB cable. You should see a sad android with "No command" displayed. Now release the Volume Up button. Then hold down the power button and then JUST PRESS once on the Volume Up button. You should be at a recovery menu. Using the volume keys, scroll down to the 'Apply update on SD card' option and select it. Select the zip that you copied over to the SD card earlier and then let it install for a while. It will probably pop up with a 'timestamp too old' error, but just ignore this. The update will install anyway. Then once it's done, do a factory reset on the phone and then shut down. MAKE SURE THERE'S NO SIM CARD IN THE PHONE.
Now that's out of the way, boot the phone up again and just click through the first-time setup screens but DO NOT ENABLE WI-FI or any kind of internet connection. We don't want the phone to update itself back to Android 9. Now plug the phone in again. Copy the bootloaderunlocker apk from Nokia's website onto the phone. Install it. Put in the email address you want the unlock key emailed to. Then voila! You'll get the verification code. Put it into the form on Nokia's website and you'll be emailed an unlock.key file. From there, the site will tell you how to proceed.
A HUGE thanks to: THMSP and frankoid
They did all the work. <3
Click to expand...
Click to collapse
after this my phone struck on nokia logo, please help,,,,
i'm training to recovery mode \ download mode but not working both
gvreddy said:
after this my phone struck on nokia logo, please help,,,,
i'm training to recovery mode \ download mode but not working both
Click to expand...
Click to collapse
Factory reset by wiping cache and data via recovery. Start over and try again.
"Your device is corrupt, It can't be trusted and will not boot" - 7 Pro 5G (GM1920)
Tried to relock my bootloader and nwo im stuck on "Your device is corrupt, It can't be trusted and will not boot" is there any tool out there that will help to unbrick the 5G version for EU? (GM1920) the MSMTool doesnt seem to support this version or does anyone know how to get out of it?!
Thanks
exxpired said:
Tried to relock my bootloader and nwo im stuck on "Your device is corrupt, It can't be trusted and will not boot" is there any tool out there that will help to unbrick the 5G version for EU? (GM1920) the MSMTool doesnt seem to support this version or does anyone know how to get out of it?!
Thanks
Click to expand...
Click to collapse
You never relock your device until you know it's stock and bootable. Can you get into fastboot?
exxpired said:
Tried to relock my bootloader and nwo im stuck on "Your device is corrupt, It can't be trusted and will not boot" is there any tool out there that will help to unbrick the 5G version for EU? (GM1920) the MSMTool doesnt seem to support this version or does anyone know how to get out of it?!
Thanks
Click to expand...
Click to collapse
We are trying to get an msmtool, but your situation could help us prioritize getting it from OnePlus, pm me
Whoareyou said:
We are trying to get an msmtool, but your situation could help us prioritize getting it from OnePlus, pm me
Click to expand...
Click to collapse
I actually managed to boot to fastboot, change the bootslot and luckily 10.0.0.3 was released which allowed me to install and wipe out TWRP (which I didnt realise got installed, I thought I set it to only boot to it not install it) im guessing this is why it went into the corrupt state.
Hi everyone
I have same problem could you help me pls
hey, I have the same issue and I don't know how to solve it.
phone run out of battery, I connected to charge it and when I started it up, I am getting the message "Your device is corrupt. It can't be trusted and will not boot". This error is looped, phone reboots every few seconds and immediately goes to this message.
I bought the phone in Europe and used it as is... (no mods, no ROM flashing, no fiddling with the Bootloader or the OS.
Now, what is interesting is that I can get into fastboot (by pressing power + vol up + vol down) but I have no idea what to do next. Tried all the options in the menu (recovery mode, restart bootloader, start, power off) and all of them lead to the same message above (your device is corrupt).
if while in fastboot I connect the phone to a PC, and run fastboot.exe devices in command line it does recognize the phone (I can see the serial number).
Any ideas what I should do next?
Long story short converted my phone from TMO to global. Went to relock bootloader but didn't flash the global rom from Oxygen updater and had to MSM back to TMobile. I have all the latest drivers installed and all the latest tools. My pC detects my phone when its booted but when I go into Fastboot I can't send commands to it. ADB Devices runs and says the list but does not show the device number. Sending a command comes back as device not found. If I unplug the phone my pC makes the disconnect sound. There's no sign of my phone in device manager but when I go down to the tool bar I can find Android device attached via USB.
I spent 2 hours already trying to get this to work and I'm out of ideas. I've even googled it and tried everything there. My last thought is to MSM again in hopes that it resets something
Smallsmx3 said:
Long story short converted my phone from TMO to global. Went to relock bootloader but didn't flash the global rom from Oxygen updater and had to MSM back to TMobile. I have all the latest drivers installed and all the latest tools. My pC detects my phone when its booted but when I go into Fastboot I can't send commands to it. ADB Devices runs and says the list but does not show the device number. Sending a command comes back as device not found. If I unplug the phone my pC makes the disconnect sound. There's no sign of my phone in device manager but when I go down to the tool bar I can find Android device attached via USB.
I spent 2 hours already trying to get this to work and I'm out of ideas. I've even googled it and tried everything there. My last thought is to MSM again in hopes that it resets something
Click to expand...
Click to collapse
Update: Looks like I'm good to go. Phone is connected again. B Now when I try to unlock my bootloader I can't flash the unlock token I get an t error cannot load unlock_token.bin
Got it all figured out!
Smallsmx3 said:
Got it all figured out!
Click to expand...
Click to collapse
What did you do for PC to see phone in fastboot mode? I have the same thing where it cannot see in fastboot mode
Arr6 said:
What did you do for PC to see phone in fastboot mode? I have the same thing where it cannot see in fastboot mode
Click to expand...
Click to collapse
Honestly I was typing in adb devices instead of fastboot devices. So I think my computer was detecting it. I did reinstall drivers that I got from the OnePlus site. I made allot of dumb errors