[HOWTO] How to Boot into Recovery - Huawei Ascend Mate 2

Hello everyone,
After a few tries, I have found out how to boot into our phone's stock recovery. We are now one step closer to root and flashing new ROMs! I know all of us can't wait for that.
Edit (September 6): ROOT AND UNLOCKED BOOTLOADER ACHIEVED! Check out the thread here. If you need help, don't be afraid to post in that thread! We'll get to you ASAP.
1) Turn off the phone.
2) Hold the power button and volume +.
3) Once the Huawei logo pops up, let go of the power button but not the volume + button.
4) The recovery will pop up, and you can let go of the volume button.
It'll look like this:
{
"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"
}

Good Job

recovery ,root ,Roms its gonna be a long ride for mate 2

Scoob I really appreciate what you and Modding.My.Mind have done today.
We aren't there yet, but we're so much closer to root because of you guys.
Thanks alot.
Sent from my MT2L03 using XDA Free mobile app

Nice find! Just ordered one on amazon tonight. Cant wait til i get it. Ive been flashing phones since the OG evo 4G. Hope we see root for this device soon!

If I had this device in my hand I could tackle it personally. Unfortunately, that is not the case, but I hope you guys see root soon. Now that you guys/gals know about this feature on your device it is just a matter of signing the update.zip properly which I sent to @ScoobSTi a few days back. The updater-script is written so that it will work in a stock recovery but without an acceptable signature the stock recovery will sadly deny it.

Modding.MyMind said:
If I had this device in my hand I could tackle it personally. Unfortunately, that is not the case, but I hope you guys see root soon. Now that you guys/gals know about this feature on your device it is just a matter of signing the update.zip properly which I sent to @ScoobSTi a few days back. The updater-script is written so that it will work in a stock recovery but without an acceptable signature the stock recovery will sadly deny it.
Click to expand...
Click to collapse
Do you mind if I post the link to the file here? Maybe one/some of our users actually understands this stuff lol.

ScoobSTi said:
Do you mind if I post the link to the file here? Maybe one/some of our users actually understands this stuff lol.
Click to expand...
Click to collapse
Go ahead man, no problem. It's made public on my dev host account. I recommend you make a notice in bold red in case you get that one guy lol. A disclaimer of some sort for development purposes.

Modding.MyMind said:
Go ahead man, no problem. It's made public on my dev host account. I recommend you make a notice in bold red in case you get that one guy lol. A disclaimer of some sort for development purposes.
Click to expand...
Click to collapse
Thanks! I'll just attach it here haha.
For those that don't know: attached is the flashable ZIP file that Modding made for us. If successful it will grant us root permissions, but at the moment it doesn't work, because it is not signed correctly. If anyone knows anything about signing, please try and work your magic! :good:

Man, hopefully we will see root very soon.
I almost ditched the phone for a Galaxy S5.
Glad I didn't.
I'd much rather see root versus Kit Kat update.

Following is a little bit more info:
Confirmed this device (MT2-L03) bootloader is locked.
I press and hold "volume down" and "power" keys for more than 10 seconds, I got into the fastboot screen, it displayed that bootloader is LOCKED.
http://www.emui.com/plugin.php?id=unlock&mod=detail
http://www.emui.com/plugin.php?id=unlock&mod=step
Above is in chinese, google translate should give OK to understand like:
https://translate.google.com/transl...//www.emui.com/plugin.php?id=unlock&sandbox=1
https://translate.google.com/transl....com/plugin.php?id=unlock&mod=step&edit-text=
And get-bootinfo show same:
D:\Android\android-sdk\platform-tools>fastboot oem get-bootinfo
...
(bootloader) *******************************************
(bootloader) Bootloader Lock State: LOCKED
(bootloader) System State: need to verify
(bootloader) Boot image need to be verified
(bootloader) Recovery image need to be verified
(bootloader) Bootloader Version: 001.001.000
(bootloader) *******************************************
OKAY [ 0.058s]
finished. total time: 0.061s
P.S., I have sent email to their support ask if they have any plan to add "MT2-L03" device to their request page. Let's wait and see.

xordos said:
Following is a little bit more info:
Confirmed this device (MT2-L03) bootloader is locked.
I press and hold "volume down" and "power" keys for more than 10 seconds, I got into the fastboot screen, it displayed that bootloader is LOCKED.
http://www.emui.com/plugin.php?id=unlock&mod=detail
http://www.emui.com/plugin.php?id=unlock&mod=step
Above is in chinese, google translate should give OK to understand like:
https://translate.google.com/transl...//www.emui.com/plugin.php?id=unlock&sandbox=1
https://translate.google.com/transl....com/plugin.php?id=unlock&mod=step&edit-text=
And get-bootinfo show same:
D:\Android\android-sdk\platform-tools>fastboot oem get-bootinfo
...
(bootloader) *******************************************
(bootloader) Bootloader Lock State: LOCKED
(bootloader) System State: need to verify
(bootloader) Boot image need to be verified
(bootloader) Recovery image need to be verified
(bootloader) Bootloader Version: 001.001.000
(bootloader) *******************************************
OKAY [ 0.058s]
finished. total time: 0.061s
P.S., I have sent email to their support ask if they have any plan to add "MT2-L03" device to their request page. Let's wait and see.
Click to expand...
Click to collapse
I'm curious, but could you try:
Code:
fastboot oem unlock
May or may not work, so it's an idea. Not all devices can use this directly without taking other necessary steps.

Modding.MyMind said:
I'm curious, but could you try:
Code:
fastboot oem unlock
May or may not work, so it's an idea. Not all devices can use this directly without taking other necessary steps.
Click to expand...
Click to collapse
Hi Modding.MyMind, First want to thank you give us MATE2 forum your help, and that su binary flash zip. Unfortunately, I tried a tools called Auto_Sign, and also use my own key to sign, both zip cause "Installation Aborted".
That's why I post above locked bootloader info, but still due to my limited knowledge of Android, I am not sure the relationship between the root and locked boot loader.
I read some articles like this:
http://forum.xda-developers.com/wiki/Bootloader
http://www.xda-developers.com/tag/bootloader/
Those give me mixed info, I even see some phone can root first, then flash a unlocked bootloader.
OK, back to topic, following is the output:
Code:
D:\Android\android-sdk\platform-tools>fastboot oem unlock
...
FAILED (remote: Please input key)
finished. total time: 0.009s
And even tried a dummy unlocked code (this should be 16 digit as the huawei website example says):
Code:
D:\Android\android-sdk\platform-tools>fastboot oem unlock 1234567812345678
...
(bootloader) Unlocking ...
OKAY [ 0.018s]
finished. total time: 0.021s
But, no, its not working, the phone display "Invalid Key" and rebooted.
P.S., I am Chinese and own a different HuaWei phone before. The official way is to use their website to request the unlock code, Huawei will record your SN number, and give you correct key to unlock it. That's the reason I have sent email to them to see if they can support this MT2-L03 in their request page.
Actually I just own this phone a few days, and starting reading the forum post, I think "ScoobSTi" actually tried the unlock before with similar result.
Anyway please let me know if you want me to test anything else.
Thanks.

unlocking that bootloader could possibly make some of the previous root methods several people have tried actually successful.
Oh this is getting interesting. We seem so close.

For some devices unlocking the bootloader would allow installing root similiar to what I shared. For most, it isn't enough. For the majority out there it is likely that a custom recovery be available to successfully gain root (which in turn would require an unlocked bootloader). Each device is different in these cases. For my current device, an unlocked bootloader is required so that a custom recovery may be allowed to overwrite the stock recovery.
Though, I will say, that by having an unlocked bootloader, the possibilities will most surely increase.
---------- Post added at 05:44 PM ---------- Previous post was at 05:41 PM ----------
This is a bit off topic here, but TWRP is built to root devices if one by chance is developed and built properly for the "given" device. Saves the hassle of having to make flashable zips lol.
I actually need to rebuild TWRP for my device . Just got to sync omnirom after accidently screwing up my linux system this past weekend.

xordos said:
Hi Modding.MyMind, First want to thank you give us MATE2 forum your help, and that su binary flash zip. Unfortunately, I tried a tools called Auto_Sign, and also use my own key to sign, both zip cause "Installation Aborted".
That's why I post above locked bootloader info, but still due to my limited knowledge of Android, I am not sure the relationship between the root and locked boot loader.
I read some articles like this:
http://forum.xda-developers.com/wiki/Bootloader
http://www.xda-developers.com/tag/bootloader/
Those give me mixed info, I even see some phone can root first, then flash a unlocked bootloader.
OK, back to topic, following is the output:
Code:
D:\Android\android-sdk\platform-tools>fastboot oem unlock
...
FAILED (remote: Please input key)
finished. total time: 0.009s
And even tried a dummy unlocked code (this should be 16 digit as the huawei website example says):
Code:
D:\Android\android-sdk\platform-tools>fastboot oem unlock 1234567812345678
...
(bootloader) Unlocking ...
OKAY [ 0.018s]
finished. total time: 0.021s
But, no, its not working, the phone display "Invalid Key" and rebooted.
P.S., I am Chinese and own a different HuaWei phone before. The official way is to use their website to request the unlock code, Huawei will record your SN number, and give you correct key to unlock it. That's the reason I have sent email to them to see if they can support this MT2-L03 in their request page.
Actually I just own this phone a few days, and starting reading the forum post, I think "ScoobSTi" actually tried the unlock before with similar result.
Anyway please let me know if you want me to test anything else.
Thanks.
Click to expand...
Click to collapse
Thanks for trying! We may finally be getting closer now. I'm seriously missing a lot of the root tweaks I had on my old phone.

Teeny-tiny update.
It seems Huawei has updated the Emui website, most likely because of the Mate7. It is now both in English and Chinese.
The bootloader unlocking website has also been updated in the same fashion. The Mate2 now shows up, but unfortunately it's the MT2-C00 version, not our MT2-L03/5. Hopefully Xordos's email will help!

Thats it....Bootloader is now unlocked !!!! and rooting is successful !!!!
http://forum.xda-developers.com/ascend-mate2/general/progress-rooting-ham2-t2867975
Let's the party begin.... :laugh:

xordos said:
Thats it....Bootloader is now unlocked !!!!
http://forum.xda-developers.com/ascend-mate2/general/progress-rooting-ham2-t2867975
Let's the party begin.... :laugh:
Click to expand...
Click to collapse
:good::good::good::good::good: x 2349872378349057340985903948590

xordos said:
Thats it....Bootloader is now unlocked !!!! and rooting is successful !!!!
http://forum.xda-developers.com/ascend-mate2/general/progress-rooting-ham2-t2867975
Let's the party begin.... :laugh:
Click to expand...
Click to collapse
Updated OP with this link!

Related

Black screen after kernel(s) flash

Hello
I hope I'm not making a double post or something...
So I tried to flash the alliance kernel, but got issues with it.
I tried the stock 1.4 full logo, cm9 full and lite logo
(found here: http://forum.xda-developers.com/showthread.php?t=1566871)
Each time, I got a black screen after 1st vibration at boot.
And nothing happens.
I tried flashing with flashtool and fastboot command line.
Same problem.
Hopefully, i can reflash the original kernel from original ftf file to make it work again, but why do I got this issue, as when I read all thread, no one got this problem.
ps: Neo V mt11i / 4.0.4 / rooted / unlocked BT
I think the newest CM9 is not compatible with the Alliance 1.4 kernel. The kernel is based on the FXP128 kernel. Try flashing the kernel from the cm9 zip.
Sent from my Sony Xperia Neo using xda app-developers app
Hmm maybe I explained wrong..
I don't want to install CM9 rom.
I just want to flash the alliance kernel (and after, maybe [email protected] rom)
how you flash kernel with fastboot command?please explain here what you have and what you do...
Ok let's try to explain what I did:
I first d/led stock 1.4 kernel (link in 1st post).
I used fastboot command line to flash it.
Flash in 1.9sec, all seems to be ok.
I reboot the phone.
Vibration and black screen.
Have to replace battery to reboot again.
But always the damn black screen.
Then I use flashtool to flash the official ftf file (431 central europe 3), but only the kernel and wipe cache.
Now the phone boot normally.
I tried the other kernels given on alliance post, but always the same screen.
After reflashing with flashtool my BL is locked again (damn it), so tonight i will "test point" it again...
And then, retry another kernel or this again if I found a solution.
My Bootloader didnt locked again after flashing FTF file with flashtool,how did u can lock again?
My BL will relock if i used restore button on S1tool...
try again till succes....
Ok, i think there was a mistake this afternoon, because I just check at home, and BL is unlocked, so all is good.
But!.. I just try another kernel (http://forum.xda-developers.com/showthread.php?t=1679771) and also with suave kernel, and guess what...
Black screen again...
I really don't understand...
Maybe your problem related to this....
http://forum.xda-developers.com/showthread.php?p=22688611
u succes to unlock BL but you won't have fastboot
megatpanji said:
Maybe your problem related to this....
http://forum.xda-developers.com/showthread.php?p=22688611
u succes to unlock BL but you won't have fastboot
Click to expand...
Click to collapse
thanks for answer, but I think i'm not concerned, because I bought my mt11i "naked", and the bootloader status says unlocking is allowed...
Is there another way (s1tools) to know if BL is unlocked?
(And now, I'm afraid to flash a locked BL custom rom for testing.. lol)
fruity101079 said:
thanks for answer, but I think i'm not concerned, because I bought my mt11i "naked", and the bootloader status says unlocking is allowed...
Is there another way (s1tools) to know if BL is unlocked?
(And now, I'm afraid to flash a locked BL custom rom for testing.. lol)
Click to expand...
Click to collapse
I unlocked my bootloader via test point. At service menu the status still says bootloader unlock allowed yes, also it is unlocked.
On my lww which I unlocked via official Sony method the status says bootloader unlocked yes.
When you are able to flash a custom kernel than you have an unlocked bootloader.
Gesendet von meinem MT11i mit Tapatalk 2
ok and then?
I think I don't understand your post..
fruity101079 said:
ok and then?
I think I don't understand your post..
Click to expand...
Click to collapse
I wanted to tell you that i unlocked bootloader of both phones. From live with walkman and the neo v.
Neo v via test point. Service menu still says bootloader unlock allowed yes
Lww via SE Bootloader Unlocking Relocking 1.6 tool (equal to sony method). Service menu has changed to status bootloader unlocked yes
Link to SE Bootloader Unlocking Relocking 1.6 tool: http://forum.xda-developers.com/showthread.php?t=1560613
Both phones are unlocked and the status is not the same. neo v still has the same status before i unlocked it. i thought that it will change to same status as the lww.
But it's (neo v) bootloader is unlocked, because i could flash a custom kernel (night elf ics 1.4).
{
"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"
}
1. Are you sure your bootloader is unlocked, if yes how did you do it?
2. Are you sure you downloaded a working flash tool and installed all needed drivers?
hooo ok ok ^^
1. So yes, I'm sure BL is unlocked, I verified with s1tools and service menu.
2. I think flashtool is ok because I can reflash the stock kernel. But maybe i should check the drivers.
fruity101079 said:
hooo ok ok ^^
1. So yes, I'm sure BL is unlocked, I verified with s1tools and service menu.
2. I think flashtool is ok because I can reflash the stock kernel. But maybe i should check the drivers.
Click to expand...
Click to collapse
Really strange behaviour.
I never hat any problems like you.
1. Please take a screen from service menu with the status of your bootloader.
2. Tell us which method you used to unlock your bootloader.
3. Try again flashing a kernel and post us the log fron flash tool.
I just reinstall drivers and flashtool.
I tried to flash differents kernels but always this black screen.
To unlock BL, I used Testpoint Method.
Here is the message i got:
Code:
writing 'boot'...
(bootloader) Download buffer format: boot IMG
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00000280-0x000002e3
(bootloader) Erase operation complete, 2 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 1.236s]
finished. total time: 1.919s
As you can see, there a strange thing at line 5...
fruity101079 said:
I just reinstall drivers and flashtool.
I tried to flash differents kernels but always this black screen.
To unlock BL, I used Testpoint Method.
Here is the message i got:
Code:
writing 'boot'...
(bootloader) Download buffer format: boot IMG
(bootloader) Flash of partition 'boot' requested
(bootloader) S1 partID 0x00000003, block 0x00000280-0x000002e3
(bootloader) Erase operation complete, 2 bad blocks encountered
(bootloader) Flashing...
(bootloader) Flash operation complete
OKAY [ 1.236s]
finished. total time: 1.919s
As you can see, there a strange thing at line 5...
Click to expand...
Click to collapse
Hi my friend.
Yeah, line five is the answer to all your problems. Bad blocks at the bootloader are worse. I searched a bit with the help of google and some german forums.
Thats what they wrote down there.
A bad block at a custom kernel results in a not booting rom, while the stock kernel results in a booting rom.
The reason they wrote at at german forum is, that the stock kernel detects the bad sector and marks it to not use it. That's the reason why the stock kernel ist still functioning.
I am no kernel technican and i can't answer you if you can repair your bootloader.
But it would help, if the programmer of custom kernels could also implement a routine for detecting and marking such bad blocks like a stock kernel.
Sorry for bad news.
Well too bad for me...
But many thanks for searching and finding a answer ^^
(I think I will stop my try for the moment.)
Thanks
motorazrv3 said:
Hi my friend.
Yeah, line five is the answer to all your problems. Bad blocks at the bootloader are worse. I searched a bit with the help of google and some german forums.
Thats what they wrote down there.
A bad block at a custom kernel results in a not booting rom, while the stock kernel results in a booting rom.
The reason they wrote at at german forum is, that the stock kernel detects the bad sector and marks it to not use it. That's the reason why the stock kernel ist still functioning.
I am no kernel technican and i can't answer you if you can repair your bootloader.
But it would help, if the programmer of custom kernels could also implement a routine for detecting and marking such bad blocks like a stock kernel.
Sorry for bad news.
Click to expand...
Click to collapse
I never knew that
Btw does it mean custom kernels could damage your bootloader??
Ty in adv
Sent from my MT11i using xda premium
blank screen
After Flashing A Kernel In My Xperia Go In Flash Tool It Shows A Message Of SUCCESSFUL And When I Turn My Phone It Vibrate And After That Just A Black Screen...
it will solve the problem??

[Script] Super CID for HTC S-Off Devices

This tool will grant you Super CID on your HTC Device
Tested on the following devices:
HTC One M7_UL
HTC One X/XL Evita
{
"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"
}
What is a CID?
CID lock (aka vendor lock): Carrier Id - put on your device by the manufacturer to prevent installation of a ROM not released by them. Commonly used in the form `CID-Unlocking`. If you purchase your phone (example) from 3Mobile (3Mobile is the ‘carrier’), your phone will only accept 3Mobile ROMs (the carrier’s ROMs). If you want to flash ROMs from other carrier, you’ll need to CID-unlock your phone, so that your phone will accept other ROMs. All bootloaders (apart from HardSPL and SSPL) will only allow a ROM with the correct CID to be flashed onto the device. A device which has been CID unlocked will have ‘SuperCID’ which allows ANY ROM to be loaded onto the device, SuperCID also unlocks the Ext_ROM and allows it to be mounted. Note: In general, the phrase ‘unlock your phone’ usually refers to SIM-unlock, not CID unlock.
What is Super CID?
SuperCID : by CID unlocking your device the value of the CID is changed to SuperCID . This allows the flashing of ANY ROM/RUU to the device regardless of the carrier and also unlocks the read/write capability of the Ext_ROM.
How to use the script?
Download the attached file
Extract the file
boot your phone into bootloader
Run the script and follow the on screen instructions
How do i get my phone into bootloader?
Power down the device
hold vol down and power at the same time
You can get the script and full CID guide here http://forums.team-nocturnal.com/showthread.php/3162
one more for future use
thanks a lot, Im downloading now, finished, that was awesome,
Edit all that's missing is to change the splash screen to a black htc...
Bloody marvelous. Worked like a champ!
So I Finally Came Around and Rooted My One... So Happy I Did.
I Have A Question... Can This Performed On a Mac? If So May I Please Have Some Guidance In Doing So? :fingers-crossed:
Thanks In Advance!
PlankLongBeard said:
So I Finally Came Around and Rooted My One... So Happy I Did.
I Have A Question... Can This Performed On a Mac? If So May I Please Have Some Guidance In Doing So? :fingers-crossed:
Thanks In Advance!
Click to expand...
Click to collapse
If you have adb on the mac, just open the script in a text editor and copy the commands I put I there. It's all the same.
Stroked from my Dirty Nocturnal'd HTC M7
Fast boot Method... Much Easier.
Once S-Off why can't we just goto bootloader and do a "fastboot oem writecid 11111111"? that's what others are reporting in the revone thread.
dankerton said:
Once S-Off why can't we just goto bootloader and do a "fastboot oem writecid 11111111"? that's what others are reporting in the revone thread.
Click to expand...
Click to collapse
That's what I did. No issues flashing the latest firmware with just the fastboot oem command.
I wouldn't mess around with hex editing.
Sent from my HTC One using Tapatalk 4 Beta
XsMagical said:
This tool will grant you Super CID on your HTC Device
Tested on the following devices:
HTC One M7_UL
HTC One X/XL Evita
What is a CID?
CID lock (aka vendor lock): Carrier Id - put on your device by the manufacturer to prevent installation of a ROM not released by them. Commonly used in the form `CID-Unlocking`. If you purchase your phone (example) from 3Mobile (3Mobile is the ‘carrier’), your phone will only accept 3Mobile ROMs (the carrier’s ROMs). If you want to flash ROMs from other carrier, you’ll need to CID-unlock your phone, so that your phone will accept other ROMs. All bootloaders (apart from HardSPL and SSPL) will only allow a ROM with the correct CID to be flashed onto the device. A device which has been CID unlocked will have ‘SuperCID’ which allows ANY ROM to be loaded onto the device, SuperCID also unlocks the Ext_ROM and allows it to be mounted. Note: In general, the phrase ‘unlock your phone’ usually refers to SIM-unlock, not CID unlock.
What is Super CID?
SuperCID : by CID unlocking your device the value of the CID is changed to SuperCID . This allows the flashing of ANY ROM/RUU to the device regardless of the carrier and also unlocks the read/write capability of the Ext_ROM.
How to use the script?
Download the attached file
Extract the file
boot your phone into bootloader
Run the script and follow the on screen instructions
How do i get my phone into bootloader?
Power down the device
hold vol down and power at the same time
You can get the script and full CID guide here http://forums.team-nocturnal.com/showthread.php/3162
Click to expand...
Click to collapse
So I have supercid but how do I install roms from different carriers? Tried installing the ruu.exe and got the wrong ruu error
Thanks
So what's the deal with Team Nocturnal's site? It looks like it's down
whitetiger_0603 said:
So what's the deal with Team Nocturnal's site? It looks like it's down
Click to expand...
Click to collapse
Bumping this query. Still down.
Here is how you do it, you don't need a script.
reboot into your bootloader with key combo, adb or app from the market
use fastboot to set the cid
fastboot oem writecid 11111111
aleph23 said:
Bumping this query. Still down.
Click to expand...
Click to collapse
Yah I cant get to site either. I get this error:
There is a serious error and the page cannot be rendered
Click to expand...
Click to collapse
edit: just saw the team's post on FB:
"We got a new server yesterday that can handle the large amounts of traffic, We have the main page 100% ready to go and are currently working on the DNS settings for the forums to take effect."
Team Nocturnal Forums will be getting revamped shorty!
Click to expand...
Click to collapse
Okay soooooo sorry for the noob question , but if i change cid , i can run any sprint rom.....? thanks in advance, will return the answer with many thanks ...lol:fingers-crossed:
Website is down or what?
Sent from my HTC One using xda premium
KingDavid63 said:
Website is down or what?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Can someone who has downloaded the script for S-Off PM me so i can get the file.
Also has anybody confirmed if this will work with the .11 software that was pushed out at the end of July.
Ive read elsewhere that most of the s-off scripts only work with .8 software..
Thanks
IAmSixNine said:
Can someone who has downloaded the script for S-Off PM me so i can get the file.
Also has anybody confirmed if this will work with the .11 software that was pushed out at the end of July.
Ive read elsewhere that most of the s-off scripts only work with .8 software..
Thanks
Click to expand...
Click to collapse
Is there new download link?
---------- Post added at 07:04 PM ---------- Previous post was at 07:02 PM ----------
XsMagical said:
This tool will grant you Super CID on your HTC Device
Tested on the following devices:
HTC One M7_UL
HTC One X/XL Evita
What is a CID?
CID lock (aka vendor lock): Carrier Id - put on your device by the manufacturer to prevent installation of a ROM not released by them. Commonly used in the form `CID-Unlocking`. If you purchase your phone (example) from 3Mobile (3Mobile is the ‘carrier’), your phone will only accept 3Mobile ROMs (the carrier’s ROMs). If you want to flash ROMs from other carrier, you’ll need to CID-unlock your phone, so that your phone will accept other ROMs. All bootloaders (apart from HardSPL and SSPL) will only allow a ROM with the correct CID to be flashed onto the device. A device which has been CID unlocked will have ‘SuperCID’ which allows ANY ROM to be loaded onto the device, SuperCID also unlocks the Ext_ROM and allows it to be mounted. Note: In general, the phrase ‘unlock your phone’ usually refers to SIM-unlock, not CID unlock.
What is Super CID?
SuperCID : by CID unlocking your device the value of the CID is changed to SuperCID . This allows the flashing of ANY ROM/RUU to the device regardless of the carrier and also unlocks the read/write capability of the Ext_ROM.
How to use the script?
Download the attached file
Extract the file
boot your phone into bootloader
Run the script and follow the on screen instructions
How do i get my phone into bootloader?
Power down the device
hold vol down and power at the same time
You can get the script and full CID guide here http://forums.team-nocturnal.com/showthread.php/3162
Click to expand...
Click to collapse
Is there a new download link?
chesterx1 said:
Is there new download link?
---------- Post added at 07:04 PM ---------- Previous post was at 07:02 PM ----------
Is there a new download link?
Click to expand...
Click to collapse
Nope because the servers died and X has been to busy with work and other stuff, but I'll upload it later and get you a link if you still need it.
Edit: Ok any looking for This just go to my 1.27.531.11 thread and check 2nd post all credit goes to Xsmagical.
Team-Noctural.com is on its way to being back up and running just having to get the new software. Be ready
Can someone please explain why one would do this instead of going to HTCDEV.com and getting the unlock token from the site? Is what we are talking about in this thread different from that?

X727 (US Model) Persistent bootloader unlock from 5.8.019s

WARNING: This ABSOLUTELY HAS THE POTENTIAL TO BRICK YOUR DEVICE. Please tread carefully. I am NOT responsible if you damage your device. This can be very dangerous, PLEASE do not do this unless you know you absolutely want/need to. You have been warned.
Important information:
This is for US Model x727 running the 5.8.019s version of the US ROM. If you flashed the chinese ROM, this will not help you at all.
Afterwards you should still have US ROM and features at version 5.8.019s
Your device should be persistently unlocked after successfully performing this procedure.
This zip file replaces the aboot and xbl (basically, the bootloader) with the versions from the LE_ZL1_LEX720-CN-FN-WAXCNFN5801811021S-5.8.018S.zip ROM file. I can't guarantee this will work for everyone (or even anyone). I can only tell you that it worked for me.
NOTE: If this makes you happy, please consider donating by clicking on the "donate to me" button under my handle at the left. I am broke and trying to recoup the cost of this device
Requirements (what I *think* you'll need):
US Le Pro3 running the US ROM updated to 5.8.019s OTA (If you're running the chinese ROM because you were impatient and didn't want to wait for the grownups to work out a procedure, this will not help you).
TWRP Image (I used the chinese one)
Zip File listed below
Somewhere to put the zip file for flashing if you don't want to have to wipe your device (I've heard of people successfully using an OTG storage device? I just wiped mine so you're on your own to figure this out)
This is the procedure I followed:
Have ADB/Fasboot tools on your computer (I am not helping you here, it you're lucky, maybe your friends will help)
Make sure you have enabled the developer tools, turned on USB debugging, and authorized your computer on your device (again, I'm not helping with that)
Make sure adb can see your device when you run "adb devices"
Run "adb reboot bootloader"
Run "fastboot devices" to make sure you see your device
Run "fastboot oem unlock-go" to unlock your device temporarily
Run "fastboot oem device-info" to verify unlock status
Run "fastboot boot recovery_twrp.img" (or whatever the twrp image filename is on your computer) to boot up to TWRP
NOTE: If you don't read chinese and you haven't done this before, you'll be presented with a screen in chinese with two buttons next to each other and a swipe underneath them. THE BUTTON ON THE RIGHT lets you change the language. Press it, thank me later.
If you have an OTG device with the bootloader replacement zip on it, skip this step. If you have to use your device's storage, and your storage is encrypted, you'll have to wipe all the data. Go to Wipe, choose Format Data and follow the instructions. YOU WILL LOSE EVERYTHING ON YOUR DEVICE. Be warned.
If you wiped your data partition, you'll need to push the zip file to the storage. Run "adb push x727-5.8.019s_bootloader-unlock.zip /sdcard/"
Now press "Install", select the x727-5.8.019s_bootloader-unlock.zip file and flash it.
Reboot back to your system. If you wiped data, your device will now proceed to re-initialize itself as if from the factory
Your system should still be running the full US ROM, but it should also now be persistently unlocked. Don't do any updates, your device likely won't remain unlocked if you run an update. And there's no guarantee you'll be able to re-unlock after doing so.
NOTE: If you flash TWRP to the recovery partition, the OS will likely reset it to the factory recovery UNLESS YOU ROOT THE SYSTEM. Your device is still unlocked, the recovery was just restored by the system, don't freak out. Be warned. I don't have time to answer stupid questions, neither does anyone else.
Download: x727-5.8.019s_bootloader-unlock.zip
MD5: 8eff2a1e29c9959259e7db1dd5c74a67
Special thanks to @hondajohn88 for taking the leap and experimenting with the chinese rom on his own device.
Reserved
Is it possible to have the chinese bands with the US rom on the x727? because I'm bringing the phone to asia and i need band 41
How about pulling us the modem image from the US version now since you have it unlocked. The Grossoshop is great except a few of us have flashed this over the CN ROM and the CN modem seems to be lacking a few bands.
awesome job! i knew we'd figure out root/unlock eventually. wonder if Le Eco accidently let this happen or did it on purpose so they can have plausible deniability
edit - did you also by chance backup the stock bootloaders?
Kick ass man!!! I get my phone next week when my dad comes down to visit me in Colombia. Can't wait to do this once it arrives
I was happy till I saw .. "Run "fastboot oem unlock-go" to unlock your device temporarily"
for some reason I don't get it to work like you guys do. it will give the same error as with the original firmware. Ill try but I doubt it will work for me
Its going to be pointless for me to try .. I don't understand why you guy can have temp bootloader while I cant
And yes, I am on 19s
C:\adb>fastboot oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.005s
C:\adb>fastboot oem device-info
...
(bootloader) Device product name: [le_zl1_oversea]
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.091s]
finished. total time: 0.094s
bulls4ever said:
I was happy till I saw .. "Run "fastboot oem unlock-go" to unlock your device temporarily"
for some reason I don't get it to work like you guys do. it will give the same error as with the original firmware. Ill try but I doubt it will work for me
Click to expand...
Click to collapse
Yeah I absolutely have tried like 6 different adb/fastboot's and nothing works for me either.
Not my first rodeo with annoying Windows drivers too.
I reset it to factory.. downloaded the 19s and upgraded again .. nothing will make it to allow oem unlock
If i try to run "fastboot boot recovery_twrp.img" will it brick the phone or just wont work?
---------- Post added at 06:20 PM ---------- Previous post was at 06:19 PM ----------
can you upload the "ADB/Fasboot tools" you used? maybe that is the problem but i doubt it
Just to make sure, you guys are checking "OEM Unlocking" in developer options, correct?
bulls4ever said:
I reset it to factory.. downloaded the 19s and upgraded again .. nothing will make it to allow oem unlock
If i try to run "fastboot boot recovery_twrp.img" will it brick the phone or just wont work?
---------- Post added at 06:20 PM ---------- Previous post was at 06:19 PM ----------
can you upload the "ADB/Fasboot tools" you used? maybe that is the problem but i doubt it
Click to expand...
Click to collapse
It won't be the fix. If adb/fastboot recognize the devices, changing versions shouldn't work. Sorry :-/ That being said, I suppose there's no hurt in trying. FWIW this is what worked for me on my Windows 7 box:
Code:
C:\Users\dr4stic>adb version
Android Debug Bridge version 1.0.36
Revision 19394af606f6-android
C:\Users\dr4stic>fastboot --version
fastboot version 19394af606f6-android
I got them by installing the Android SDK. The SDK manager indicates that my "Android SDK Platform Tools" (that the tools come from) are at version 24.0.4 and I can upgrade to revision 25.
This may be a dumb question, but I'm assuming you've set the "allow device bootloader unlocking" (or whatever it's called) in the developer settings... right?
ExTREmE99 said:
awesome job! i knew we'd figure out root/unlock eventually. wonder if Le Eco accidently let this happen or did it on purpose so they can have plausible deniability
edit - did you also by chance backup the stock bootloaders?
Click to expand...
Click to collapse
I did, but I didn't really need to. They're in the 5.8.019s OTA. They're the emmc_appsboot.mbn and xbl.elf files in the firmware-updates folder.
dr4stic said:
It won't be the fix. If adb/fastboot recognize the devices, it won't work. Sorry :-/
This may be a dumb question, but I'm assuming you've set the "allow device bootloader unlocking" (or whatever it's called) in the developer settings... right?
Click to expand...
Click to collapse
yes, i did
ITs bizarre that some can get the tem unlock and some don't.
Like I said . I reset to fabric, re-updated using the 19s that is in the forum. Enabled developer tools. Enabled OEM unlock and USB dev. I tried to mimic a brand new update to 19s ...
I wonder if it actually enable OEM but adb/fastboot wont say it is unlocked? unlikely but .. hey.. I'm desperate at this point lol
---------- Post added at 06:36 PM ---------- Previous post was at 06:33 PM ----------
My version is 1.0.32 ...
---------- Post added at 06:39 PM ---------- Previous post was at 06:36 PM ----------
no donuts
C:\adb>adb version
Android Debug Bridge version 1.0.36
Revision e02fe72a18c3-android
C:\adb>fastboot oem unlock-go
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.015s
C:\adb>
bulls4ever said:
yes, i did
ITs bizarre that some can get the tem unlock and some don't.
Like I said . I reset to fabric, re-updated using the 19s that is in the forum. Enabled developer tools. Enabled OEM unlock and USB dev. I tried to mimic a brand new update to 19s ...
I wonder if it actually enable OEM but adb/fastboot wont say it is unlocked? unlikely but .. hey.. I'm desperate at this point lol
---------- Post added at 06:36 PM ---------- Previous post was at 06:33 PM ----------
My version is 1.0.32 ...
Click to expand...
Click to collapse
Who knows, maybe the lower version is misinterpreting the output. If you're really determined you can try upgrading your version of adb/fastboot. Like I said I use the sdk from google, so it's as updated as it'll get. Anything else is just someone repackaging what already exists.
After you "fastboot oem unlock-go" try booting the twrp image anyway. I doubt it'll work if it's misinterpreting the response (it would have be interpret it properly to send the boot image to the device for booting), but who knows. Maybe it will work anyway.
Saikou0taku said:
Just to make sure, you guys are checking "OEM Unlocking" in developer options, correct?
Click to expand...
Click to collapse
yes
Going to try the Android SDK shortly
bulls4ever said:
yes, i did
ITs bizarre that some can get the tem unlock and some don't.
Like I said . I reset to fabric, re-updated using the 19s that is in the forum. Enabled developer tools. Enabled OEM unlock and USB dev. I tried to mimic a brand new update to 19s ...
I wonder if it actually enable OEM but adb/fastboot wont say it is unlocked? unlikely but .. hey.. I'm desperate at this point lol
Click to expand...
Click to collapse
You know... if worse comes to worst and you desperately want to unlock, couldn't you just try installing the Chinese ROM listed by some of the other users? I don't know how that ROM would react to your phone being that it isn't unlocking at all, maybe it'll brick it, maybe it won't (I doubt it). The consequences of that would completely be of your own undertaking...
That being said, the chinese rom people talk about is signed by LeEco and thus would likely install without question. And it's bootloader would then be unlocked. We could make plans to return you to stock US firmwares at a later date. I suspect we're gonna have to get a solution together for that at some point anyway... My only suggestion would be that you do it while coming from the 5.8.019s (which you already are) because that's where my firmwares are coming from.
Android SDK will give the same results as expected ...
Not that desperate ... I'm desperate to keep LeEco cause I like it. But do not want to go to Chinese way as it will lose bands and currently we don't even have ways to come back to US rom.
My "desperation" is that the deadline to decide if I will keep the phone or return is approaching.
What I need to figure it out is why some have tem unlock and some don't. My windows is 10. Maybe windows issue (I doubt it)? will try windows 7 later
bulls4ever said:
Android SDK will give the same results as expected ...
Not that desperate ... I'm desperate to keep LeEco cause I like it. But do not want to go to Chinese way as it will lose bands and currently we don't even have ways to come back to US rom.
My "desperation" is that the deadline to decide if I will keep the phone or return is approaching.
What I need to figure it out is why some have tem unlock and some don't. My windows is 10. Maybe windows issue (I doubt it)? will try windows 7 later
Click to expand...
Click to collapse
No, windows should have nothing to do with it. I'm assembling a "return to US" rom as we speak... but I won't feel comfortable about releasing it until it's been tested. And also I need lunch...
dr4stic said:
No, windows should have nothing to do with it. I'm assembling a "return to US" rom as we speak... but I won't feel comfortable about releasing it until it's been tested. And also I need lunch...
Click to expand...
Click to collapse
I'm going to use this method later today and can report back any issues. By the way, you are the man!
Is super super flash able after bootloader is unlocked?
yeah .. windows wasn't the issue. I tested on Ubuntu and it was a no go.
Is it possible that LeEco released like 2 versions being the first a mistake of leaving the bootloader sort of unlocked and then a second with it locked?
I am running out of reasons for not being able to unlock it while some are able to

root for lg tribute dynasty sprint version

anyone find root method for android 7.1.2 lg tribute dynasty? if so please help if not we need to develope one
Ehacksa said:
anyone find root method for android 7.1.2 lg tribute dynasty? if so please help if not we need to develope one
Click to expand...
Click to collapse
No we realy want root for this phone
Ditto for root on lg tribute dynasty
Mag xx said:
No we realy want root for this phone
Click to expand...
Click to collapse
Ditto for root on lg tribute dynasty, would like to have it. Just putting it out there as a request, thanks.
if we get a custom recovery first get root will be easier
Are there any updates on this?
Can you unlock the bootloader on the sprint/boost variant? If so we can make a TWRP recovery for it and flash magisk for root
jasonmerc said:
Can you unlock the bootloader on the sprint/boost variant? If so we can make a TWRP recovery for it and flash magisk for root
Click to expand...
Click to collapse
Yeah you can unlock the bootloader. All you need to do is go to dev options and enable OEM unlock. I was wondering if there's any cross compatibility between LG software and if it's at all possible to root it using a TWRP recovery intended for a similar phone. I don't want to try it on my new phone yet though considering the risky nature of rooting.
Kevin4762 said:
Yeah you can unlock the bootloader. All you need to do is go to dev options and enable OEM unlock. I was wondering if there's any cross compatibility between LG software and if it's at all possible to root it using a TWRP recovery intended for a similar phone. I don't want to try it on my new phone yet though considering the risky nature of rooting.
Click to expand...
Click to collapse
That's not all you need to do. Once you flip the oem unlock switch you then need to reboot to the bootloader and run the appropriate command--THEN you will really see if your bootloader can be unlocked. I don't know the command off hand but a google search should say what it needs to be
And as far as your other question, yes it is possible to use twrp for a similar phone. However it doesn't look like there is a similar phone with a similar chipset like this that has twrp already but I could be wrong. Note that cross compatibility like this is only for custom firmware like twrp, stock firmware IS NOT CROSS COMPATIBLE.
jasonmerc said:
That's not all you need to do. Once you flip the oem unlock switch you then need to reboot to the bootloader and run the appropriate command--THEN you will really see if your bootloader can be unlocked. I don't know the command off hand but a google search should say what it needs to be.
Click to expand...
Click to collapse
You're right there's more, I wasn't familiar with how bootloaders were unlocked until you mentioned that. After some research, unfortunately, LG has pretty much nailed tight the bootloader for all but a select few LG devices. Still, I followed a guide on how to use ADB and Fastboot in an attempt to reboot into bootloader, but sadly all it does is restart the phone normally. As far as I know, it's impossible to unlock the bootloader on this phone so I guess we're all SOL when it comes to rooting.
{
"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"
}
Kevin4762 said:
You're right there's more, I wasn't familiar with how bootloaders were unlocked until you mentioned that. After some research, unfortunately, LG has pretty much nailed tight the bootloader for all but a select few LG devices. Still, I followed a guide on how to use ADB and Fastboot in an attempt to reboot into bootloader, but sadly all it does is restart the phone normally. As far as I know, it's impossible to unlock the bootloader on this phone so I guess we're all SOL when it comes to rooting.
Click to expand...
Click to collapse
Try the process anyway. My friend said he managed to unlock it on a device that wasn't listed but that was a while ago. If there's something where you put in a serial number or IMEI see if it'll take yours
jasonmerc said:
Try the process anyway. My friend said he managed to unlock it on a device that wasn't listed but that was a while ago. If there's something where you put in a serial number or IMEI see if it'll take yours
Click to expand...
Click to collapse
So far I've tried booting to bootloader through recovery mode and ADB, both ending up booting to the system normally. I'm not sure I understand what you mean by "something where you put in a serial number or IMEI." Is there any way you can find out how your friend managed to do this?
Kevin4762 said:
So far I've tried booting to bootloader through recovery mode and ADB, both ending up booting to the system normally. I'm not sure I understand what you mean by "something where you put in a serial number or IMEI." Is there any way you can find out how your friend managed to do this?
Click to expand...
Click to collapse
For some LG phones there's a process you have to go through on their website to request an "unlocking binary". I believe its something like Motorola's bootloader unlock program. You put in some phone specific info (s/n, IMEI, or something) and if its eligible to be unlocked LG will send you an unlocking binary. Then once you get the binary there's some sort of special fastboot command you have to enter, utilizing that binary, to open up your bootloader
I haven't done this myself so I don't 100% know the process, but this is what I've heard other people discussing in the past. I'll reach out to people and see if I can find the site again
jasonmerc said:
For some LG phones there's a process you have to go through on their website to request an "unlocking binary". I believe its something like Motorola's bootloader unlock program. You put in some phone specific info (s/n, IMEI, or something) and if its eligible to be unlocked LG will send you an unlocking binary. Then once you get the binary there's some sort of special fastboot command you have to enter, utilizing that binary, to open up your bootloader
I haven't done this myself so I don't 100% know the process, but this is what I've heard other people discussing in the past. I'll reach out to people and see if I can find the site again
Click to expand...
Click to collapse
First off, I appreciate you taking the time to help me out. I found what you're talking about, but it's specific to only a few devices and LG SP200 isn't one of the models listed. Also, in order to get the device ID, you first need to enter fastboot mode, which I can't get to work.
[email protected] every cool phone i get i cant root ... :/
Alldayismokebomb said:
[email protected] every cool phone i get i cant root ... :/
Click to expand...
Click to collapse
I think they skipped over the "Unlock OEM" in the developer settings. The device is a mcv150 close to the cv1. Search up LG Aristo 2 TWRP and see if the TWRP flashes to your device. If it works then I can fix the device specific bugs.
It appears that no one has replied to this thread in almost 3 years (as of this post). To resurrect this thread, I have quite a couple of things about this device to say:
I don't think accessing the bootloader is possible for whatever reason. I've tried rebooting into the bootloader (with "Enable OEM Unlock" enabled) through adb reboot bootloader but to no avail.
Root is possible.The Tribute Dynasty (SP200) contains a MediaTek MT6750 SoC. Combined with the last security patch being November 1, 2019 (an interesting coincidence), this makes this device vulnerable to the mtk-su temporary root exploit.
I remember following a guide somewhere else on XDA, but I can't recall which guide (nor can I find it right now). I remember using mtk-easy-su for this purpose, but then that's all I can remember.
There might be some other developments with this phone that I might know about, but all of this I find from experience.

Question Metro PCS Bootloader Unlocking

Has anyone been able to get past this yet.... Not T-Mobile but the Metro PCS bootloader. If so please post here... Many many people are pulling their hair out waiting to a fix to this problem....
I did however find this if any DEV's what some bootloader hacking insight and a tool to do it....
halloweenm925 said:
How to Unlock Bootloader on OnePlus (Unlocked / T-Mobile)
Here is a complete walk-through and guide on how to unlock bootloader on OnePlus phones. Whether you are looking to install a custom ROM or trying to root
teamandroid.com
View attachment 5833761
Click to expand...
Click to collapse
halloweenm925 said:
How to Unlock Bootloader on OnePlus (Unlocked / T-Mobile)
Here is a complete walk-through and guide on how to unlock bootloader on OnePlus phones. Whether you are looking to install a custom ROM or trying to root
teamandroid.com
View attachment 5833761
Click to expand...
Click to collapse
The link does not work...
halloweenm925 said:
How to Unlock Bootloader on OnePlus (Unlocked / T-Mobile)
Here is a complete walk-through and guide on how to unlock bootloader on OnePlus phones. Whether you are looking to install a custom ROM or trying to root
teamandroid.com
View attachment 5833761
Click to expand...
Click to collapse
This no longer works, the links are dead. there is no information on which version of deep testing you have to have as they are all version specific for each phone so you can all ignore this and if anyone has a RECENTLY tried and tested method that works post it here. If its old and no longer functiining like this guide here, do not post it as it does ot work....
halloweenm925 said:
How to Unlock Bootloader on OnePlus (Unlocked / T-Mobile)
Here is a complete walk-through and guide on how to unlock bootloader on OnePlus phones. Whether you are looking to install a custom ROM or trying to root
teamandroid.com
View attachment 5833761
Click to expand...
Click to collapse
Does not work the link to OnePlus is dead. So its a waste of time....
Anyone have a way that does not involve dead links that get you no where?
How to Unlock Bootloader on OnePlus (Unlocked / T-Mobile)
Here is a complete walk-through and guide on how to unlock bootloader on OnePlus phones. Whether you are looking to install a custom ROM or trying to root
teamandroid.com
{
"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"
}
yes this has worked for me for years to get oem unlocked. type in PowerShell:
adb shell pm disable-user com.qualcomm.qti.uim
oem toggle will not be greyed out after or you can use this one+ tool to get oem unlock https://1drv.ms/u/s!AqDQuxOzB8wghvoaD02pqZRbUL4eXw
once u type that command in turn oem unlock on in developer options and USB debugging.just in case u haven't yet u need to tap build version under about phone 7x to unhide that menu. make sure you have a backup of your device including firmware for your specific device in case issues and so you can extract your boot img to patch with magisk, also if custom recovery is available for the device might want to find and USB adb drivers then open power shell in windows and type adb reboot bootloader to get into fastboot. once in fastboot type ./fastboot oem unlock. should with no issues a pop-up on device stating if you want bootloader unlock device has to be factory reset. accept and your device will reset and reboot then to get root once booted to welcome screen just hit skip to get through setup just in case something happens your going to have to do it all over. you can fully setup later. once on home screen download magisk from GitHub only and install open it after installed and on main screen your gonna want to patch your boot img you got from firmware extraction and patch with magisk. I believe file will be in downloads folder then send that to Windows adb folder and reboot to fastboot again then type ./fastboot flash boot (magisk-patched file).img and now your rooted and restart
just found this as well. claims to have almost 100% success https://optool.daxiaamu.com/wiki_pctool. has support for all one+ devices
halloweenm925 said:
How to Unlock Bootloader on OnePlus (Unlocked / T-Mobile)
Here is a complete walk-through and guide on how to unlock bootloader on OnePlus phones. Whether you are looking to install a custom ROM or trying to root
teamandroid.com
View attachment 5833761
Click to expand...
Click to collapse
The link does not work...
halloweenm925 said:
How to Unlock Bootloader on OnePlus (Unlocked / T-Mobile)
Here is a complete walk-through and guide on how to unlock bootloader on OnePlus phones. Whether you are looking to install a custom ROM or trying to root
teamandroid.com
View attachment 5833761
Click to expand...
Click to collapse
As I have stated the OnePlus support link no longer works so this guide is irrelavant.
paulb1977 said:
once u type that command in turn oem unlock on in developer options and USB debugging.just in case u haven't yet u need to tap build version under about phone 7x to unhide that menu. make sure you have a backup of your device including firmware for your specific device in case issues and so you can extract your boot img to patch with magisk, also if custom recovery is available for the device might want to find and USB adb drivers then open power shell in windows and type adb reboot bootloader to get into fastboot. once in fastboot type ./fastboot oem unlock. should with no issues a pop-up on device stating if you want bootloader unlock device has to be factory reset. accept and your device will reset and reboot then to get root once booted to welcome screen just hit skip to get through setup just in case something happens your going to have to do it all over. you can fully setup later. once on home screen download magisk from GitHub only and install open it after installed and on main screen your gonna want to patch your boot img you got from firmware extraction and patch with magisk. I believe file will be in downloads folder then send that to Windows adb folder and reboot to fastboot again then type ./fastboot flash boot (magisk-patched file).img and now your rooted and restart
Click to expand...
Click to collapse
Thats if you have the bin code which for what ever reason OnePlus has shut down that link...So not going to work on Metro PCS with a locked boot loader...
paulb1977 said:
once u type that command in turn oem unlock on in developer options and USB debugging.just in case u haven't yet u need to tap build version under about phone 7x to unhide that menu. make sure you have a backup of your device including firmware for your specific device in case issues and so you can extract your boot img to patch with magisk, also if custom recovery is available for the device might want to find and USB adb drivers then open power shell in windows and type adb reboot bootloader to get into fastboot. once in fastboot type ./fastboot oem unlock. should with no issues a pop-up on device stating if you want bootloader unlock device has to be factory reset. accept and your device will reset and reboot then to get root once booted to welcome screen just hit skip to get through setup just in case something happens your going to have to do it all over. you can fully setup later. once on home screen download magisk from GitHub only and install open it after installed and on main screen your gonna want to patch your boot img you got from firmware extraction and patch with magisk. I believe file will be in downloads folder then send that to Windows adb folder and reboot to fastboot again then type ./fastboot flash boot (magisk-patched file).img and now your rooted and restart
Click to expand...
Click to collapse
Thats just unlocks The ability to run it on any network that does not unlock a METRO PCS locked bootloader. You have to get a bin file or a expolit, the ADB method does not work on locked bootloaders
jayram1408 said:
Thats just unlocks The ability to run it on any network that does not unlock a METRO PCS locked bootloader. You have to get a bin file or a expolit, the ADB method does not work on locked bootloaders
Click to expand...
Click to collapse
I have three PCS phones and none of them have unlocked bootloaders. 2 N20's and a N200
<Moderator Note>:
Please, everyone - instead of making three to five posts in a row, sometimes quoting the same previous post, please just Edit your existing post with the additional information.
I've merged all the posts in a row by the same users in this thread. I did accidentally make a mistake, so the second post in this thread was what came after the now third post, and there's no easy way to undo that. Apologies.
Much appreciated.
Thank you,
@roirraW "edor" ehT
Bro just use the Tmobile portal through oneplus there is a thread with the link on this forum.
yes sir it has worked on nord n10, n100 , and op 9 without getting the unlock bin. the adb she'll command allows the OEM toggle to be ungreyed then type ur unlock bootloader commands but make sure u have dev potions enabled and you are on your home screen beforehand. also make sure your device is connected to the internet. I've heard that I won't work if not. I haven't had any problems with it though. there is also an option in the OnePlus tool to allow oem unlock to be toggled as well and it all should work without network unlock or the unlock.bin
Does anyone actually try to use the link or are we all just copy and pasting. The links do not work.....if anyone has a good working link. That you have TRIED first... please post it here.
On another note, have any Devs seen the information I posted about bootloader hacking. My technical skills are more suited to fixing cars but I did accidently stumble upon how some group made a tool and complete instructions to unlock any and all bootloaders wether its on phones, computers, or basicly any electronic device. There was a lot of information there but it's beyond my scope of being able to implement. A person with the right background can probably read it and have the ability to hack a great many things afterwords. It went over hacking Tv's, video game consoles, phones, industrial control, computers, systems ect.... they claim with the knowledge they posted and the tool they invented that ALL bootloaders can now be circumvented.

Categories

Resources