Apparently VIVO phones are the black horses of the hacking community because they are near impossible to root!
Also I'm new, I hope I'm posting in the right thread.
Now onto the details, I've been trying to root my phone lately and so far absolutely nothing is working at all! I've not seen anyone whatsoever on XDA to root this specific phone. Mostly V3 and Xshot series
I've tried every single rooting app there is, but I noticed that my efforts are worthless because my phone has an impenetrable bootloader! Of course I immediately head to the internet and found about ADB and Fastboot. Now I've been trying to confirm my suspicions about a locked bootloader by using the "device-info" command on ADB, then I get
Code:
<bootloader> unlock:false
.
Now since I was trying to unlock the bootloader and to this day I absolutely CANNOT bust through it. Whenever I use the "oem-unlock" command, it will always say "FAIL: check device or oem lock"
I forgot most of the commands I used on ADB, (first time using it, actually :silly: ) but the commands I used were normally the ones used to unlock a phone's bootloader.
Going to their forums, they always say that they do not allow their users to tamper with their devices and I was this close to giving up, but after going to the phone's recovery mode, I immediately see at the bottom "The Phone: not root" (yes that's what it exactly says, that's not my grammar) which means that it SHOULD be possible to root it in the first place, and because of that I have not stopped trying.
However every last method I tried failed and I am desperate enough to come here, to XDA forums where I learned to root my now 6+ year old Samsung Galaxy Y.
I really need your help, guys.
Nagazumi said:
Apparently VIVO phones are the black horses of the hacking community because they are near impossible to root!
Also I'm new, I hope I'm posting in the right thread.
Now onto the details, I've been trying to root my phone lately and so far absolutely nothing is working at all! I've not seen anyone whatsoever on XDA to root this specific phone. Mostly V3 and Xshot series
I've tried every single rooting app there is, but I noticed that my efforts are worthless because my phone has an impenetrable bootloader! Of course I immediately head to the internet and found about ADB and Fastboot. Now I've been trying to confirm my suspicions about a locked bootloader by using the "device-info" command on ADB, then I get .
Now since I was trying to unlock the bootloader and to this day I absolutely CANNOT bust through it. Whenever I use the "oem-unlock" command, it will always say "FAIL: check device or oem lock"
I forgot most of the commands I used on ADB, (first time using it, actually :silly: ) but the commands I used were normally the ones used to unlock a phone's bootloader.
Going to their forums, they always say that they do not allow their users to tamper with their devices and I was this close to giving up, but after going to the phone's recovery mode, I immediately see at the bottom "The Phone: not root" (yes that's what it exactly says, that's not my grammar) which means that it SHOULD be possible to root it in the first place, and because of that I have not stopped trying.
However every last method I tried failed and I am desperate enough to come here, to XDA forums where I learned to root my now 6+ year old Samsung Galaxy Y.
I really need your help, guys.
Click to expand...
Click to collapse
Can u plz give me ur num
I have Vivo Y55l (1603). I am unable to root this device
I have Vivo Y55l (1603). I am unable to root this device. Please tell me appropriate method for rooting this device.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i unlock bootloader and flash twrp recovery
but not boot
guide :
qiurigao said:
View attachment 4129802
i unlock bootloader and flash twrp recovery
but not boot
Click to expand...
Click to collapse
Any chance you can tell me how you did this.
Rakesh37187 said:
Any chance you can tell me how you did this.
Click to expand...
Click to collapse
add my google talk: [email protected]
or QQ:1239120048
Same problem
Is there any way to root this phone or not?? Tried everything and every root app feeling so low please someone help *=*
OEM Unlock In Developers Options?
Did You Turn On The OEM unlock in Developers Option??
James480 said:
Did You Turn On The OEM unlock in Developers Option??
Click to expand...
Click to collapse
没有用
qiurigao said:
没有用
Click to expand...
Click to collapse
好的,我猜那么
qiurigao said:
没有用
Click to expand...
Click to collapse
Everyone plz join this Telegram Group for further development
Vivo y55
https://t.me/vivoy55Development
are you able to unlock it
Tandyeyd said:
are you able to unlock it
Click to expand...
Click to collapse
plzz tell me how to root vivo y55l (1603)
divu jadeja said:
plzz tell me how to root vivo y55l (1603)
Click to expand...
Click to collapse
y55 dont root
It offered to boot as flashed...if you tapped power, I suppose.
Would it just loop into the notice, and not boot the TWRP recovery if you pressed a hardware key (power, say?) Good effort, keep freeing the MSM8974!
Lugralunoogos said:
Would it just loop into the notice, and not boot the TWRP recovery if you pressed a hardware key (power, say?) Good effort, keep freeing the MSM8974!
Click to expand...
Click to collapse
yes
Unlock Vivo bootloader
Vivo phones bootloader can be easily unlocked with modified fastboot binary
Here's the xda thread with downloads
How to root vivo y71
Related
Hi everyone, I am new to the forum but I have a question that has been giving me a headache for a long time, I have a Redmi Note 3 Pro (Kate) and I can not unlock the bootloader of the device, I tried everything this error appears in the 99% asking me to check the mi unlock status in the device settings. and when I try to add the account appears another error as shown in the image. Does anyone know a definitive solution to this error?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
alvesluscas said:
Hi everyone, I am new to the forum but I have a question that has been giving me a headache for a long time, I have a Redmi Note 3 Pro (Kate) and I can not unlock the bootloader of the device, I tried everything this error appears in the 99% asking me to check the mi unlock status in the device settings. and when I try to add the account appears another error as shown in the image. Does anyone know a definitive solution to this error?
Click to expand...
Click to collapse
Some days ago I flashed latest Global Stable on my Kate just for cleanup and I faced the same problem, but the funniest part: even with that error at 99%, MiUnlock opened my bootloader.
Boot in fastboot, connect the phone to your pc and check your bootloader status.
onliner said:
Some days ago I flashed latest Global Stable on my Kate just for cleanup and I faced the same problem, but the funniest part: even with that error at 99%, MiUnlock opened my bootloader.
Boot in fastboot, connect the phone to your pc and check your bootloader status.
Click to expand...
Click to collapse
how do I check the bootloader status?
alvesluscas said:
how do I check the bootloader status?
Click to expand...
Click to collapse
Reboot in fastboot, connect the phone to your pc, open cmd and type: fastboot oem device-info
You are looking for "device unlocked: true".
onliner said:
Reboot in fastboot, connect the phone to your pc, open cmd and type: fastboot oem device-info
You are looking for "device unlocked: true".
Click to expand...
Click to collapse
I just check here it is not unlocked
device unlocked: false
onliner said:
Some days ago I flashed latest Global Stable on my Kate just for cleanup and I faced the same problem, but the funniest part: even with that error at 99%, MiUnlock opened my bootloader.
Boot in fastboot, connect the phone to your pc and check your bootloader status.
Click to expand...
Click to collapse
Because when u flashed using miflash it did not relock your bootloader and that's why it's still unlocked it happened to me 3 times so this legitimate.
Androbots said:
Because when u flashed using miflash it did not relock your bootloader and that's why it's still unlocked it happened to me 3 times so this legitimate.
Click to expand...
Click to collapse
No, MiFlash blocked my bootloader, I made sure the program did it, I wanted to close my bootloader, after the flashing process I checked it and it was blocked (from fastboot "device unlocked : false".
My Unlock behaves strangely sometimes with Kate devices, in some spanish group, another person commented the same, 99% > error > but bootloader unlocked.
onliner said:
No, MiFlash blocked my bootloader, I made sure the program did it, I wanted to close my bootloader, after the flashing process I checked it and it was blocked (from fastboot "device unlocked : false".
My Unlock behaves strangely sometimes with Kate devices, in some spanish group, another person commented the same, 99% > error > but bootloader unlocked.
Click to expand...
Click to collapse
I see that now...
There is no other reason than your internet connection.
U need working internet connection to verify your device while unlock.
I had same problem. But later when i connected to internet while full process of unlocking it got unlocked...
mohsiin4u said:
There is no other reason than your internet connection.
U need working internet connection to verify your device while unlock.
I had same problem. But later when i connected to internet while full process of unlocking it got unlocked...
Click to expand...
Click to collapse
but the device is connected to the internet
alvesluscas said:
but the device is connected to the internet
Click to expand...
Click to collapse
Your computer Must be connected to internet, and not the device
mohsiin4u said:
Your computer Must be connected to internet, and not the device
Click to expand...
Click to collapse
Yes, my computer is connected to the internet, if I were not connected I would not be able to log in to my unlock
alvesluscas said:
Yes, my computer is connected to the internet, if I were not connected I would not be able to log in to my unlock
Click to expand...
Click to collapse
Your PC connected to ur device hotspot internet connection? If yes then connect another hotspot to ur pc it need when u connect ur Device to PC in fastboot mode
alvesluscas said:
Yes, my computer is connected to the internet, if I were not connected I would not be able to log in to my unlock
Click to expand...
Click to collapse
Hope you got permission from Xiaomi to unlock your account/phone. Then the problem next is just need to map the account for unlocking from phone.
For this follow the instructions below..
Go to Developer settings -> Enable OEM unlocking and also go to Unlock status -> then 'Add my account' for unlocking. (You should see toast message that account is added)
The next painful part is you have to wait 72 hours after adding account. Then try unlock tool (Ver.2) to unlock it.
Hope it helps!
NewBee3 said:
Hope you got permission from Xiaomi to unlock your account/phone. Then the problem next is just need to map the account for unlocking from phone.
For this follow the instructions below..
Go to Developer settings -> Enable OEM unlocking and also go to Unlock status -> then 'Add my account' for unlocking. (You should see toast message that account is added)
The next painful part is you have to wait 72 hours after adding account. Then try unlock tool (Ver.2) to unlock it.
Hope it helps!
Click to expand...
Click to collapse
Yes, I have the permission of xiaomi to unlock the device, being that the problem is that the error is when trying to add the account in my unlock status. an error message appears
Have you try to flash fastboot global or developer with clean flash?
alvesluscas said:
Yes, I have the permission of xiaomi to unlock the device, being that the problem is that the error is when trying to add the account in my unlock status. an error message appears
Click to expand...
Click to collapse
Same error with me as well...i'm gonna try putting only one sim that i use as mi account
Will report if anything changes
PS: i'm new to this device modding and unlocking is really a tricky part here
Any help is appreciated,i wish to unlock officially rather than any dirty hacks
SH3H1 said:
Same error with me as well...i'm gonna try putting only one sim that i use as mi account
Will report if anything changes
PS: i'm new to this device modding and unlocking is really a tricky part here
Any help is appreciated,i wish to unlock officially rather than any dirty hacks
Click to expand...
Click to collapse
try flash stable china rom..
dinoredfield said:
try flash stable china rom..
Click to expand...
Click to collapse
I was told to do this, but mine is Kate (Special Edition) there is no Chinese rom for him
rainsmile said:
Have you try to flash fastboot global or developer with clean flash?
Click to expand...
Click to collapse
I tried both with developer and stable global
Guys, is there anybody please, who can help me with getting Device ID through Fastboot? I can't get it alone without your help, trying it half a day without any success.
I am doing it step by step with LG official guide http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryId=CTULRS0702 , but I can't get much far.
My problem is, that when I am rebooting using "adb reboot bootloader", the device will reboot, after that, I type "fastboot oem device-id" and than, I am stucked at < waiting for any device >. Tried that on 2 WIN PCs and on 1 Macbook Pro, but without any luck, everywhere same thing happens...can you please help me, what can be wrong, what should I do differently or what am I doing wrong?
Thank you very much.
TomasDrabek said:
Guys, is there anybody please, who can help me with getting Device ID through Fastboot? I can't get it alone without your help, trying it half a day without any success.
I am doing it step by step with LG official guide http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryId=CTULRS0702 , but I can't get much far.
My problem is, that when I am rebooting using "adb reboot bootloader", the device will reboot, after that, I type "fastboot oem device-id" and than, I am stucked at < waiting for any device >. Tried that on 2 WIN PCs and on 1 Macbook Pro, but without any luck, everywhere same thing happens...can you please help me, what can be wrong, what should I do differently or what am I doing wrong?
Thank you very much.
Click to expand...
Click to collapse
Not sure why you need the device ID.
See the WTF bootloader unlock Instructions THREAD and unlock bootloader, install TWRP and root -- without having to receive permission from LG.
What you're trying to do (get unlock code from LG) is no longer necessary.
Since you already have H930, just go to that thread and fastboot flash the new_unlock.bin code provided.
Sent via open market LG US998 V30/V30+
ChazzMatt said:
Not sure why you need the device ID.
See the WTF bootloader unlock THREAD and unlock bootloader, install TWRP and root -- without having to receive permission from LG.
What you're trying to do (get unlock code from LG) is no longer necessary.
Since you already have H930, just go to that thread and fastboot flash the new_unlock.bin code provided.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
Well, thank you for your reply..tried the step by step guide from the topic you mentioned, but my problem persits..there is some problem with my PC/phone/FASTBOOT command, because it looks like the PC can´t see the phone in the bootloader mode. I typed "adb reboot bootloader", it works well, but than, when I had to type "fastboot flash unlock new_unlock.bin", same < waiting for any device > on command line keep stucked and nothing more happened.
TomasDrabek said:
Well, thank you for your reply..tried the step by step guide from the topic you mentioned, but my problem persits..there is some problem with my PC/phone/FASTBOOT command, because it looks like the PC can´t see the phone in the bootloader mode. I typed "adb reboot bootloader", it works well, but than, when I had to type "fastboot flash unlock new_unlock.bin", same < waiting for any device > on command line keep stucked and nothing more happened.
Click to expand...
Click to collapse
In the WTF Instructions (Section 7) there are a dozen Trouble Shooting tips. Almost all deal with ADB issues.
Try another (different) source for ADB installation.
Try different USB port, different USB cable, different computer.
That's just a few. See the WTF Instructions Section 7 for all of them and try them all.
TomasDrabek said:
Well, thank you for your reply..tried the step by step guide from the topic you mentioned, but my problem persits..there is some problem with my PC/phone/FASTBOOT command, because it looks like the PC can´t see the phone in the bootloader mode. I typed "adb reboot bootloader", it works well, but than, when I had to type "fastboot flash unlock new_unlock.bin", same < waiting for any device > on command line keep stucked and nothing more happened.
Click to expand...
Click to collapse
There could be an issue with your fastboot drivers. I was also unable to get fastboot commandant to work on my laptop but it worked just fine on my desktop.
After getting root I did try a reinstallation of windows on my laptop and was able to get fastboot to work fine on my laptop though; so if all else fails, including reinstalling fastboot drivers a windows reinstall may help.
I used the adb and fastboot from here https://forum.xda-developers.com/showthread.php?t=2588979
So I figured out what the problem was: when using an original OEM USB-C cable from the box, everything worked great and now I am installing TWRP and trying to root phone...hoping that everything will go through without any problems. In the meantime, thank you all for your answers guys:
TomasDrabek said:
So I figured out what the problem was: when using an original OEM USB-C cable from the box, everything worked great and now I am installing TWRP and trying to root phone...hoping that everything will go through without any problems. In the meantime, thank you all for your answers guys:
Click to expand...
Click to collapse
So "different cable" was the answer.
Exactly
My phone is already rooted (mainly for Adaway), so now, I am 100% satisfied. Thanks a lot.
ChazzMatt said:
Not sure why you need the device ID.
See the WTF bootloader unlock THREAD and unlock bootloader, install TWRP and root -- without having to receive permission from LG.
What you're trying to do (get unlock code from LG) is no longer necessary.
Since you already have H930, just go to that thread and fastboot flash the new_unlock.bin code provided.
Sent via open market LG US998 V30/V30+
Click to expand...
Click to collapse
Me for example, I wouln't like to DOWNGRADE my phone - which is neccessary with the way you suggest.
For me changing USB port in the PC does nor help. And i'm using the original cable from the box.
Have the same problem.
Specs: Lg v30+ Lgh-H930DS rev 1.1
Martinezz123 said:
Me for example, I wouln't like to DOWNGRADE my phone - which is necessary with the way you suggest.
For me changing USB port in the PC does nor help. And i'm using the original cable from the box.
Have the same problem.
Specs: Lg v30+ Lgh-H930DS rev 1.1
Click to expand...
Click to collapse
Go HERE and read about rooting your V30:
ROOT Your LG V30!
https://forum.xda-developers.com/lg-v30/how-to/root-v30-t3927154
Read POST #1.
It will give you an overview of what you need to do and direct you to the WTF Instructions thread.
If you read the that post or even the WTF Instructions, you would understand you are merely TEMPORARILY downgrading to early Oreo to have access to the WTF bootloader unlock exploit. After that you are urged to update back to newer firmware (at least last Oreo, if not Pie).
You are aggravating me. You keep posting in many old threads instead of going to the threads I keep telling you to go to.
Go read all my answers to your questions today and please post in relevant thread I am pointing you to over and over. Is there something about the attached screenshot you cannot read or comprehend? I have posted that link several times now.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In the WTF Instructions thread (Section 7) are over a dozen Touble Shooting tips. You have only mentioned two that I happened to reference here. The full list is in the WTF Instructions.
I understand uou are upset but I can't go through all the pages in a long therad to uncover one answer to a simple problem which sould be explained at the beggining in the first place.
Im' lookng for the simplest metod, and the one from LG seems the most easygoing.
Why can't I get the phone to show me its ID?
It's not the problem of that other topic isn't it?
Martinezz123 said:
I understand uou are upset but I can't go through all the pages in a long therad to uncover one answer to a simple problem which sould be explained at the beggining in the first place.
Im' lookng for the simplest metod, and the one from LG seems the most easygoing.
Why can't I get the phone to show me its ID?
It's not the problem of that other topic isn't it?
Click to expand...
Click to collapse
I'm upset because you're not listening. The answer is EASY.
Yes, it's easy to to bootloader unlock and root the H939DS. But you have to read the WTF Instructions and follow them.
I've given you the link several times.
ALL H930DS bootloader unlocked and rooted HAD to follow those WTF instructions, which I wrote. There is no other method.
Until you unlock your Bootloader and Root, any other questions you ask from any other thread than the WTF INSTRUCTIONS thread, I will ignore because that means you don't actually want help.
___
No one is asking you to go through an "entire thread" for instructions you need to read. If you think that, then you are failing to read basic sentences. You need to read the WTF INSTRUCTIONS and follow them. PERIOD.
_____
You don't need the Device ID whatsoever for bootloader unlock and root. So that's a totally irrelevant question. Which means you aren't paying attention to my answers.
____
I've answered your questions repeatedly and you are not following the simple answer being given.
Seems like you've just ignoed what I said bat anyway I'll manage it by myself.
thanks.
Got Zui Unlock File have tried not translating site both IMEIS all sorts of other random BS
I get this error. USB debugging enabled and OEM unlock on in Devolper settings. Im trying to flash GLOBAL from to Chinese version as my mobile data doesn't work as phone auto popluates with wrong APN settings and I cant change them. It popluates with HOT spot APN settings and the data will work if I send it to another phone so I know it should be possible to get it to work if I can get the right settings in there. Was hoping global from would fix it but I cant flash to global as I get incompatible hardware message likely due to the BOOT loader being locked still.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
this is the error i get.
Have you tried flashing in fastbootd rather than fastboot?
how do i do that
theres the bootloader mode and the fastboot mode. to get into fastboot mode on phone I have to put into recovery mode press power button and volume button up and then I can actually get the phone to be detected in fastboot and have the commands work
EDIT I AM IN FASTBOOTD it says it at the top. thats when i got that error i previousy screenshotted
I can take pictures if not familliar with the specific model.. first person gets 100$ in crypto or fiat via Paypal IDC Im desperate it hasn't been working for months and my other phone I've been hotspotting to it got cracked and is quite old so its either buy an entirely new phone or get this one working fully
can message me on {Mod edit} to exchange info for reward whoever helps fix
Spyrobuddy said:
Got Zui Unlock File have tried not translating site both IMEIS all sorts of other random BS
I get this error. USB debugging enabled and OEM unlock on in Devolper settings. Im trying to flash GLOBAL from to Chinese version as my mobile data doesn't work as phone auto popluates with wrong APN settings and I cant change them. It popluates with HOT spot APN settings and the data will work if I send it to another phone so I know it should be possible to get it to work if I can get the right settings in there. Was hoping global from would fix it but I cant flash to global as I get incompatible hardware message likely due to the BOOT loader being locked still. View attachment 5453391 this is the error i get.
Click to expand...
Click to collapse
Did you specify the drive that contains the file?
For example, if there is a file directly under c drive, it will be c: ¥ sn.img.
Sorry if I'm wrong.
Spyrobuddy said:
how do i do that
theres the bootloader mode and the fastboot mode. to get into fastboot mode on phone I have to put into recovery mode press power button and volume button up and then I can actually get the phone to be detected in fastboot and have the commands work
EDIT I AM IN FASTBOOTD it says it at the top. thats when i got that error i previousy screenshotted
I can take pictures if not familliar with the specific model.. first person gets 100$ in crypto or fiat via Paypal IDC Im desperate it hasn't been working for months and my other phone I've been hotspotting to it got cracked and is quite old so its either buy an entirely new phone or get this one working fully
can message me on {Mod edit} to exchange info for reward whoever helps fix
Click to expand...
Click to collapse
@Spyrobuddy
I'd like to inform you that I've deleted the reference to social media from your quoted post! As an exemption from the last bullet of rule no. 5 of the XDA Forum Rules, we grant only developers the privilege to share references to their social media in their own development threads. These conditions obviously don't apply to your posts or you.
Second, please be aware that we do not allow bounty or donations thread and usually I'd closed this thread. But I decide to leave the thread open because I see that members are trying to help and assist you anyway without focusing on your offer. I've subscribed to the thread now, and I will close the thread if it derails.
8. Donations.
As a user, you're allowed to ask for donations in your signature as a thank you for your hard work, however donations up front are not allowed. This forum is about sharing and not about getting paid to do something... that is what your job is for.
Click to expand...
Click to collapse
Above implies that such offers are also not allowed.
Regards
Oswald Boelcke
Senior Moderator
Spyrobuddy said:
Got Zui Unlock File have tried not translating site both IMEIS all sorts of other random BS
I get this error. USB debugging enabled and OEM unlock on in Devolper settings. Im trying to flash GLOBAL from to Chinese version as my mobile data doesn't work as phone auto popluates with wrong APN settings and I cant change them. It popluates with HOT spot APN settings and the data will work if I send it to another phone so I know it should be possible to get it to work if I can get the right settings in there. Was hoping global from would fix it but I cant flash to global as I get incompatible hardware message likely due to the BOOT loader being locked still. View attachment 5453391 this is the error i get.
Click to expand...
Click to collapse
If you haven't connected it to the USB under the volume button, connect it to the USB under the volume button.
If you are using another USB, it may fail.
If I don't use the side port it won't even show up in fastboot. As for the file and the folder if it is not in the right folder I get a different error. I navigate to the drive then run the command but the phone tells me it is locked so it seems like a catch 22 situation
Spyrobuddy said:
If I don't use the side port it won't even show up in fastboot. As for the file and the folder if it is not in the right folder I get a different error. I navigate to the drive then run the command but the phone tells me it is locked so it seems like a catch 22 situation
Click to expand...
Click to collapse
Have you registered the wrong value for IMEI1?
Click on the link in this tutorial, this link is the best, put your first (top) IMEI number and the correct serial number. People are confusing serial number with the 2nd IMEI number or with something else, I put the wrong one first time but second time got it right. Follow the instructions in this tutorial its the best tutorial. Use the side port not the bottom. I'm enjoying a fully updated, bootloader unlocked and rooted Legion duel 2, its super fast after rooting cos I have gotten rid of all google and lenovo junk, only kept whatI need. All the best guys.
Tutorial: How to Update, Unlock bootloader and Root your CN with Global Rom phone
I received my phone today from Aliexpress and was able to update, unlock bootloader and root my phone so I want to share the steps. Follow them at your own risk, I take no responsibility for any issues or bricking. You should always backup your...
forum.xda-developers.com
If i use the other imei it wont even send the file. I have the file kt just doesnt work due to the error message in the screenshot.
First, have you tried removing a lock on the phone altogether (by setting it to none or swipe and deleting fingerprint)? Second, try running fastboot from /Android/platform-tools/ . Third, when you plug the phone into the bottom port and it is not recognized, go to device manager and look for an exclamation that should state something like fastboot device, right click select properties, select driver update, select browse my computer for driver, select let me pick, scroll down to near bottom and select USB device, there should be a list of three choose winadb (might be winusb). Last, try running the fastboot command from an admin privileged command prompt (right click command prompt, run as admin). These suggestions should lead you to a solution for unlocking the device. I'd appreciate your "offer"; post back results.
I tried downloading something in my developer options and it seemed to work, but when my phone restarted I got a message saying, "your device is corrupt. It Can't be trusted and will not boot". The message seems to be in some sort of boot loop, (keeps restarting with the same message). Is there any way I can fix this without sending my phone in to One Plus? I purchased the phone inside of a Metro store.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If your phone is from T-Mobile or Metro, check out this forum post to recover your phone: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4324431/
If your phone was factory unlocked, contact OnePlus for a repair. The easiest way to tell if your phone is a carrier device or not is to check the back of the phone. If there's an IMEI engraved on the back of the phone, it's a T-Mobile or Metro phone. If there's not IMEI engraver, its factory unlocked.
I think what you used was the DSU Loader.
If I recall earlier posts in this forum correctly, you need to Bootloader Unlock your phone before messing with DSUs, or you will brick your phone.
As Izgmc said, you'll need to use the MSM Download Tools in the thread he linked to fix your phone, assuming you have the T-Mobile or Metro versions; or to contact OnePlus support if you have the factory unlocked variant.
edale1 said:
I think what you used was the DSU Loader.
If I recall earlier posts in this forum correctly, you need to Bootloader Unlock your phone before messing with DSUs, or you will brick your phone.
As Izgmc said, you'll need to use the MSM Download Tools in the thread he linked to fix your phone, assuming you have the T-Mobile or Metro versions; or to contact OnePlus support if you have the factory unlocked var
Click to expand...
Click to collapse
Yeah that was it! Lesson learned. Thank you!
Thats how I managed to mess up my phone and is currently bricked for several months .. no msmdownload for the unlocked .. please try and get a remote session with the oneplus tech guys .. and share if possible
Hold up a second here. If you have tried to relock the bootloader (which will result in the device is corrupt and will not boot message) try this:
Hold down all 3 buttons (Vol+ Vol- and power) for about 8 seconds or so. As soon as the device vibrates quickly release the power button. When you do, the device should be in fastboot. If you are in fastboot you should now be able to connect it to the PC and type the command fastboot oem unlock. This will now attempt to unlock the bootlaoder. Chances are you have previously unlocked the bootloader and have attempted to relock it. Doing so will cause this error message on the UNLOCKED version of the device.
This will wipe the data but return the device to an unlocked state but not completely bricked on stock firmware. Go through the normal prompts to start the device and you should be good.
Remember, if you have fastboot its not COMPLETELY bricked. Not yet anyways.
I had this happened on my OnePlus Nord 200 5g literally the next day after I got it from Metro at T-Mobile. Phone updated as it should but restarted with the same message you received. They tried to accuse me of putting a virus on the phone which did not make any sense and after going through insurance who couldn't accept the claim for "software damage" ... I contacted one plus and had them remote view my laptop with downloaded tar files and had a technician try to reinstall them back to its original factory condition but to no luck. Metro being a franchise company, has the loophole not accepting returned merchandise even under the return policy stated on the receipt, and customer service technically has no control or power over any particular franchise Metro store. I suggest the only answer I had after 2 weeks of frustration from contacting everyone I possibly could to writing corporate, I finally had a CSR tell me to just get a warranty exchange at any Metro store in which I did in two days later I received a new phone which actually works this time so I would suggest just doing the warranty exchange in order to get yourself a workable phone. Hope that helps. \m/
edale1 said:
I think what you used was the DSU Loader.
If I recall earlier posts in this forum correctly, you need to Bootloader Unlock your phone before messing with DSUs, or you will brick your phone.
As Izgmc said, you'll need to use the MSM Download Tools in the thread he linked to fix your phone, assuming you have the T-Mobile or Metro versions; or to contact OnePlus support if you have the factory unlocked variant.
Click to expand...
Click to collapse
I did this exact thing. Mine is the oem unlocked variant. Is contacting oneplus support still the only option? It's on the metro/tmobile network if that matters. I really fcked up here with dsu loader. Pretty desperate right now for a fix. Please.
superspecialgueststar said:
I did this exact thing. Mine is the oem unlocked variant. Is contacting oneplus support still the only option? It's on the metro/tmobile network if that matters. I really fcked up here with dsu loader. Pretty desperate right now for a fix. Please.
Click to expand...
Click to collapse
You can try the MSM Tools and see if it works, if not, then yes, OP Support is your only option.
edale1 said:
You can try the MSM Tools and see if it works, if not, then yes, OP Support is your only option.
Click to expand...
Click to collapse
Thanks, I downloaded msm tools and there are msm tools included in https://www.terabox.com/web/share/link?surl=7fjfMJSEcdl5zCjPT92IKA
for
dre8t_10_O.05_210713.tar.bz2 -can someone point me to the stock firmware I should be using msmtools error device not match image. Can I use the ~3gb ota zips?
Taking a break and then going to look for a guide for MSM tools.
edit - as an additional point of confusion, my bootloader was unlocked, I was rooted with magisk patched upstream boot.img. Did this happen because I did not know about uninstalling magisk and installing magiosk to the inactive slot? My bootloader is still unlocked, but flashing boot backups etc does not get me out of fastboot loop, and unable to verify boot image error when I try to fastboot boot twrp or orangefox.
You're past the point I can help with, maybe someone else has some more advice for you?
Thanks. And technical support turns out is the only way and sending it in is the only way for the oem unlocked version. I requested a remote session and ended up being told the files aren't working so they can't do a remote session. If they arent working how are they going to flash my device lol...who knows.
Superspecialgueststar,
The released MSM tool is only for the carrier variant and cannot be used for the unlocked variant. There is cryptographic security in place to restrict its use.
You can still fix your unlocked device, just use an unbrick guide for the unlocked version.
[GUIDE] How to unbrick your Nord N200 5G (ALL VARIANTS) or switch bootable slot (REQUIRES UNLOCKED BOOTLOADER)
I've seen alooot of issues lately of people "bricking" their Nord N200's without a method of unbricking (at the time of writing, only T-Mobile variant has MSMTool) I've noticed a reoccurring theme. i myself am guilty of doing it and not...
forum.xda-developers.com
or use my unbrick experience and advice
Un-bricking my Nord N200
Don't ask me why, but I tried to upload a GSI using fastboot to my N200. And that didn't work. So I then read online about other people getting the same error I had, and their fix was deleting the "product" partition and erasing the system...
forum.xda-developers.com
Hi everyone, I accidentally locked my phone after I tried to remove the bootloader warning message that booted up everytime I turned on my phone. Now it says that my phone is corrupted in red and I can only boot to fastboot mode. My device is now locked and customer support told me that I needed to go to a OnePlus repair shop. The problem is that I don't live in the US. If anyone can help me I'll be appreciated.
twomad said:
Hi everyone, I accidentally locked my phone after I tried to remove the bootloader warning message that booted up everytime I turned on my phone. Now it says that my phone is corrupted in red and I can only boot to flashboot mode. My device is now locked and customer support told me that I needed to go to a OnePlus repair shop. The problem is that I don't live in the US. If anyone can help me I'll be appreciated.
Click to expand...
Click to collapse
Can you access fastboot? Is the bootloader unlocked or did you lock the bootloader
Kenora_I said:
Can you access fastboot? Is the bootloader unlocked or did you lock the bootloader
Click to expand...
Click to collapse
yes. i can access fastboot mode. Windows recognizes my device when I enter "fastboot devices". I accidentally locked the bootloader while running Pixel Experience 12 GSI and now it says "your device is corrupt. It can't be trusted and will not boot".
twomad said:
yes. i can access fastboot mode. Windows recognizes my device when I enter "fastboot devices". I accidentally locked the bootloader while running Pixel Experience 12 GSI
Click to expand...
Click to collapse
Try to unlock it again with fastboot flashing unlock
Kenora_I said:
Try to unlock it again with fastboot flashing unlock
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
twomad said:
View attachment 5587563
Click to expand...
Click to collapse
this is what is says in Fastboot:
-PRODUCT NAME - holi
-VARIANT - SM_ UFS
-BOOTLOADER VERSION -
-BASEBAND VERSION -
-SERIAL NUMBER - eb375f3e
-SECURE BOOT - yes
DEVICE STATE - locked
twomad said:
this is what is says in Fastboot:
-PRODUCT NAME - holi
-VARIANT - SM_ UFS
-BOOTLOADER VERSION -
-BASEBAND VERSION -
-SERIAL NUMBER - eb375f3e
-SECURE BOOT - yes
DEVICE STATE - locked
Click to expand...
Click to collapse
You'll have to try get into EDL mode, but there's no MSM tool released for the unlocked varient of this phone only the T-Mobile varient
Kenora_I said:
You'll have to try get into EDL mode, but there's no MSM tool released for the unlocked varient of this phone only the T-Mobile varient
Click to expand...
Click to collapse
exactly. I tried to follow this guide https://forum.xda-developers.com/t/...le-slot-requires-unlocked-bootloader.4401113/ but it's only applicable to bricked phones that have bootloader unlocked
twomad said:
exactly. I tried to follow this guide https://forum.xda-developers.com/t/...le-slot-requires-unlocked-bootloader.4401113/ but it's only applicable to bricked phones that have bootloader unlocked
Click to expand...
Click to collapse
Yeah unfortunately you're stuck here, without the MSM tool
You could try calling One Plus customer support, explain there are no OP repair shops locally, and request a remote session to fix it.
It's been a while since anyone tried, you might luck out and they could have the MSM tools for the unlocked variant now. (PLEASE share them if they do, they'll send you a link to download the MSM tools ahead of time for the remote session)
Barring that, they'll probably want you to mail the phone in to get it fixed.
edale1 said:
You could try calling One Plus customer support, explain there are no OP repair shops locally, and request a remote session to fix it.
It's been a while since anyone tried, you might luck out and they could have the MSM tools for the unlocked variant now. (PLEASE share them if they do, they'll send you a link to download the MSM tools ahead of time for the remote session)
Barring that, they'll probably want you to mail the phone in to get it fixed.
Click to expand...
Click to collapse
I was actually looking into this for the OnePlus 10 Pro but it seems unlikely but who knows?
A remote session is how we got the T-Mobile MSM tools. It's just every time someone's tried with the Unlocked variant, they've been told the remote support team doesn't have access to the MSM tools for the Unlocked variant. As I said, it's been a while since the last attempt, so there's a chance they may have gotten it by now.
edale1 said:
You could try calling One Plus customer support, explain there are no OP repair shops locally, and request a remote session to fix it.
It's been a while since anyone tried, you might luck out and they could have the MSM tools for the unlocked variant now. (PLEASE share them if they do, they'll send you a link to download the MSM tools ahead of time for the remote session)
Barring that, they'll probably want you to mail the phone in to get it fixed.
Click to expand...
Click to collapse
yeah, I emailed OnePlus and they immediately told me to send the phone for repair. I emailed them again so that they can provide me an MSM tool so let's see how it goes.
twomad said:
yeah, I emailed OnePlus and they immediately told me to send the phone for repair. I emailed them again so that they can provide me an MSM tool so let's see how it goes.
Click to expand...
Click to collapse
Hopefully it will work, the talk about the unlocked version of the MSM tool has kind of died down for around 2 months or so. (On this forum, at least)
Sorry if I missed something and am plucking at brain cells that have already been plucked, but has anyone tried EDL mode and emmcdl.exe with the available firehose? Its not as straight forward to do being as the n200 is UFS amd not EMMC, but it should still be do'able. Its how I managed to get my brick back to fastboot... For that matter, the UFS provisioning xml is available for QFil. You'd have to determine which storage make you have (samsung or toshiba).... Just a thought
the.real.p3y0t3 said:
Sorry if I missed something and am plucking at brain cells that have already been plucked, but has anyone tried EDL mode and emmcdl.exe with the available firehose? Its not as straight forward to do being as the n200 is UFS amd not EMMC, but it should still be do'able. Its how I managed to get my brick back to fastboot... For that matter, the UFS provisioning xml is available for QFil. You'd have to determine which storage make you have (samsung or toshiba).... Just a thought
Click to expand...
Click to collapse
Thing is we don't have the firehose, otherwise it would be easy with qfil
biff_train said:
Hopefully it will work, the talk about the unlocked version of the MSM tool has kind of died down for around 2 months or so. (On this forum, at least)
Click to expand...
Click to collapse
"About your query, we would like to inform you that, currently, we are unable to perform a remote session for OnePlus Nord N200, in this case, we request you to send the device to the serviceable region to get it repaired." I'm screwed
twomad said:
"About your query, we would like to inform you that, currently, we are unable to perform a remote session for OnePlus Nord N200, in this case, we request you to send the device to the serviceable region to get it repaired." I'm screwed
Click to expand...
Click to collapse
Yeah they did that for the OnePlus 10 Pro as well
Kenora_I said:
Thing is we don't have the firehose, otherwise it would be easy with qfil
Click to expand...
Click to collapse
Firehose should be right inside the (extracted) OPS and common to the variants, but I believe OPlus firehoses are encrypted and can't simply be used with QFIL.
AndyYan said:
Firehose should be right inside the (extracted) OPS and common to the variants, but I believe OPlus firehoses are encrypted and can't simply be used with QFIL.
Click to expand...
Click to collapse
Yeah, we tried it but it's not loading actually