Jose-MXL said:
CAN ANYONE IN THIS THREAD AND WITH THE INTENTIONS OF UNLOCKING THE BOOTLOADER PLEASE CAPTURE THE OTA PER THE POST BELOW:
http://forum.xda-developers.com/axon-7/how-to/to-unlock-bootloader-hold-help-t3437617
Sorry the harsh capitals, we need more visibility on this.
In case someone with the intentions of unlocking the bootloader reads this, there is an OTA being pushed to devices when they request the bootloader unlock, it is very important for development to capture these OTAs.
Click to expand...
Click to collapse
OK guys this seems to be great NEWS , yeahhh....
Here is the link for the step provided by [email protected] Community.
https://community.zteusa.com/docs/DOC-1193?et=watches.email.document
And I'll add as attachment the PDF file for the steps..so far seems like is super easy.
I'll be writing the steps here later today , I'm using my phone as we speak and is not easy getting all that info here hehehe.
P.S. When doing the " fastboot oem unlock " command line be sure to backup your device THIS WILL WIPE INTERNAL STORAGE AND DATA .....
P.S.S. Looks like one of the Steps for Unlocking is a FOTA (Forcce OTA) without it the steps above are useless
Copy-Paste from the other thread:
If you read the document looks like unlocking the bootloader boils down to "fastboot oem unlock", like you'd do on any Nexus
If this is the case, it's pretty good, because it means that the procedure isn't tied to the phone's IMEI.
Btw, I've tried doing it, and it didn't work, so I guess there'll be another OTA soon to actually activate the unlocking, and that must be the OTA that it's been referred to in the instructions
AlesG87 said:
Copy-Paste from the other thread:
If you read the document looks like unlocking the bootloader boils down to "fastboot oem unlock", like you'd do on any Nexus
If this is the case, it's pretty good, because it means that the procedure isn't tied to the phone's IMEI.
Btw, I've tried doing it, and it didn't work, so I guess there'll be another OTA soon to actually activate the unlocking, and that must be the OTA that it's been referred to in the instructions
Click to expand...
Click to collapse
Did you enable "OEM Unlocking" under Developer Options?
yep, it was enabled
I think they push out an OTA update specific to your device to let this happen. We need someone to capture it.
Actually. It sounds like they will send you a specific file for your device that you will install per instructions.
AlesG87 said:
yep, it was enabled
Click to expand...
Click to collapse
dennis96411 said:
I think they push out an OTA update specific to your device to let this happen. We need someone to capture it.
Click to expand...
Click to collapse
mmmm, i'm doing a Device Backup (Data/Apps , MMS,Text and internal storage) and give it a try...report back as soon i get something.
AlesG87 said:
yep, it was enabled
Click to expand...
Click to collapse
At which point in the process did you notice it not working for you? You do have the B20 update installed, correct?
Well, I skipped all the useless stuff about the SDK since I'm on linux, just made sure adb debug and unlock switches were on and did
adb reboot bootloader
fastboot oem unlock
Got "FAILED (remote: unknown command)" response in the terminal
AlesG87 said:
Well, I skipped all the useless stuff about the SDK since I'm on linux, just made sure adb debug and unlock switches were on and did
adb reboot bootloader
fastboot oem unlock
Got "FAILED (remote: unknown command)" response in the terminal
Click to expand...
Click to collapse
What about "fastboot devices"?
swehes said:
Actually. It sounds like they will send you a specific file for your device that you will install per instructions.
Click to expand...
Click to collapse
Hmm, I was waiting for an email. I checked for an update just in case and lo and behold, I found it waiting. Installing it now.
Wait, try to save the OTA for research purposes before you install!
charlie.s said:
Hmm, I was waiting for an email. I checked for an update just in case and lo and behold, I found it waiting. Installing it now.
Click to expand...
Click to collapse
Same here, I was pushed an update.
charlie.s said:
Hmm, I was waiting for an email. I checked for an update just in case and lo and behold, I found it waiting. Installing it now.
Click to expand...
Click to collapse
were you able to capture it?
and yeah Doesn't work without the OTA for unlocking :'( .....
I hope someone can save it and upload it here so the developers can have a look.
Worked for me. I updated the phone via settings. The file was about 50MB...I think. When connected to the PC, you have to choose "install driver" instead of MTP/PTP.
"P.S. When doing the " fastboot oem unlock " command line be sure to backup your device THIS MAY or WILL WIPE INTERNAL STORAGE AND DATA ....."
There's no MAY, I just did it and it WILL erase your data.
Rats -- I hit the trigger too quickly, so I can't capture the file. For future reference, how can I do that?
CandyFoxJ said:
"P.S. When doing the " fastboot oem unlock " command line be sure to backup your device THIS MAY or WILL WIPE INTERNAL STORAGE AND DATA ....."
There's no MAY, I just did it and it WILL erase your data.
Click to expand...
Click to collapse
Unlocking/locking the bootloader will always format the userdata partition.
charlie.s said:
Rats -- I hit the trigger too quickly, so I can't capture the file. For future reference, how can I do that?
Click to expand...
Click to collapse
Does the update install as soon as it finishes downloading?
Related
Hi, I literally opened the nexus 9 out of the box, powered it on & after choosing a wifi network it began updating, the device crashed during this update and now it won't boot! I've tried & searched for everything, anyone have any ideas?
Booting to recovery with HW buttons, wiping cache/userdata/factory reset - Nada!
Can boot into fastboot, no permission to flash as oem unlock is disabled!
I cant get into the tablet to unlock fastboot oem unlock within devOpitons or usb debugging etc, (com.android.phone has stopped on boot) black screen indefinitely.
I can't flash any images while it is locked
surely there must be a simple method?
desperate here
Return it
I'd just return it. I'm no expert, but I'd seek a way to avoid the update during setup and try to postpone it until you unlock developer options and OEM unlock. I'm not sure how you'd bypass the update during setup, but you're in the right place if it's possible.
VermontKindBud said:
I'd just return it. I'm no expert, but I'd seek a way to avoid the update during setup and try to postpone it until you unlock developer options and OEM unlock. I'm not sure how you'd bypass the update during setup, but you're in the right place if it's possible.
Click to expand...
Click to collapse
Hmm, its one of works, just bought bulk amount of them. surely it can't be stuck in an unescapable cycle?
syko9 said:
Hmm, its one of works, just bought bulk amount of them. surely it can't be stuck in an unescapable cycle?
Click to expand...
Click to collapse
Certainly it can. If it started to install the 5.0.2 OTA, there have been a lot of bricks.
cam30era said:
Certainly it can. If it started to install the 5.0.2 OTA, there have been a lot of bricks.
Click to expand...
Click to collapse
Alright thanks for the info, guess it shall be replaced thanks.
syko9 said:
Alright thanks for the info, guess it shall be replaced thanks.
Click to expand...
Click to collapse
Welcome. And FWIW: there's a button for that.
If I remember correctly you can still flash the stock images even with the boot loader locked. Its only custom images that google will not accept unless you unlock boot loader.
Ripx88 said:
If I remember correctly you can still flash the stock images even with the boot loader locked. Its only custom images that google will not accept unless you unlock boot loader.
Click to expand...
Click to collapse
Bootloader has to be unlocked to "fastboot flash" anything.
You can sideload an OTA with a locked bootloader, but you have to be able to access recovery.
cam30era said:
Bootloader has to be unlocked to "fastboot flash" anything.
You can sideload an OTA with a locked bootloader, but you have to be able to access recovery.
Click to expand...
Click to collapse
Ah ok gotcha. My apologizes, I thought I heard somewhere you could. Thank you for the correction.
Ripx88 said:
Ah ok gotcha. My apologizes, I thought I heard somewhere you could. Thank you for the correction.
Click to expand...
Click to collapse
No problem. That's how we learn.
cam30era said:
No problem. That's how we learn.
Click to expand...
Click to collapse
Indeed I'm still new to nexus devices. I've been flashing on Samsung devices for years so I'm still stuck in my Odin ways. Just got the N9 less then a week ago. The whole fastboot thing was foreign at first but I'm getting there lol. Thank you again.
Hello ?
I'm looking to root my m4 aqua E2303 6.0.1 Bootloader unlock: yes
However I don't want any twrp stuff, last time I rooted this phone I found something on this forum, connected my phone to a pc via USB ran an exe and it got rooted it was soooo simple, and everything worked great, however after Sony released the firmware update(from 5.0.0 to 6.0.1) root dissappeared. Isn't there a similar tool for 6.0.1? I really don't want to get into all the twrp stuff and ehhh you understand, I want to keep it simple.
Thanks in advance.
Procow said:
Hello
I'm looking to root my m4 aqua E2303 6.0.1 Bootloader unlock: yes
However I don't want any twrp stuff, last time I rooted this phone I found something on this forum, connected my phone to a pc via USB ran an exe and it got rooted it was soooo simple, and everything worked great, however after Sony released the firmware update(from 5.0.0 to 6.0.1) root dissappeared. Isn't there a similar tool for 6.0.1? I really don't want to get into all the twrp stuff and ehhh you understand, I want to keep it simple.
Thanks in advance.
Click to expand...
Click to collapse
in Android 6.0.1 Without Unlock Bootloader is Impossible, but if you have Unlock Bootloader Use it,( Just Flash boot.img) : http://forum.xda-developers.com/m4-aqua/general/root-twrp-sony-xperia-m4-aqua-t3503369
And you can try KingoRoot Soft for root without Unlockbootloader
Whaaaaatt?
It just says waiting for device,
Debugging on oem on
Procow said:
It just says waiting for device,
Debugging on oem on
Click to expand...
Click to collapse
Maybe its not working.
Good luck
Yo
EHSAN™ said:
Maybe its not working.
Good luck
Click to expand...
Click to collapse
Let me explain, I'm doing the adb method, when I say fastboot flash boot boot.img it just says waiting for device
My phone doesn't react at all
I haven't manually unlocked the Bootloader it's so hard and time consuming to download all those programs.
I want only the root nothing else.
Procow said:
Let me explain, I'm doing the adb method, when I say fastboot flash boot boot.img it just says waiting for device
My phone doesn't react at all
I haven't manually unlocked the Bootloader it's so hard and time consuming to download all those programs.
I want only the root nothing else.
Click to expand...
Click to collapse
Need to unlock Bootloader for Root With ADB.
I did now
EHSAN™ said:
Maybe its not working.
Good luck
Click to expand...
Click to collapse
EHSAN™ said:
Need to unlock Bootloader for Root With ADB.
Click to expand...
Click to collapse
I did but now when I type fastboot devices
Hdjebshshd(that phone ID u know)
Then I type
Fastboot flash boot boot.img
It says something about downloading, max file size and then says FAILED
Procow said:
I did but now when I type fastboot devices
Hdjebshshd(that phone ID u know)
Then I type
Fastboot flash boot boot.img
It says something about downloading, max file size and then says FAILED
Click to expand...
Click to collapse
You must be going on Fastboot Mod Then Type this in ADB, And Read There Topic that i give you.
Well
EHSAN™ said:
You must be going on Fastboot Mod Then Type this in ADB, And Read There Topic that i give you.
Click to expand...
Click to collapse
I just open a command prompt in the adb folder and type it, it says command line is not allowed even if I try doing it in the administrator rights.
First it says max file size
,,OKAY"
Loaded(0.703seconds)
....,,boot"
Failed(command line is not allowed)
Something similar to this.
What am I doing wrong? How can I check if I actually unlocked the Bootloader(pretty sure I did)
So weird.
Procow said:
I just open a command prompt in the adb folder and type it, it says command line is not allowed even if I try doing it in the administrator rights.
First it says max file size
,,OKAY"
Loaded(0.703seconds)
....,,boot"
Failed(command line is not allowed)
Something similar to this.
What am I doing wrong? How can I check if I actually unlocked the Bootloader(pretty sure I did)
So weird.
Click to expand...
Click to collapse
*#*#7378423#*#* > Service Info > Configuration > Rooting Status:
Figured everything out, just don't know how lol
In the end I now have root ty.
Tell me how you fixed it
to get to the point i used the ota updater for a lineage and it wiped twrp and replaced it with lineage recovery. then i decided to perform a factory reset in sed recovery. that led to boot loop that landed me back in recovery. so i started up lgup and went back to stock oreo and bootloader remained unlocked. now that i'm back on stock oem unlock is greyed out. when in fastboot it says to enable oem unlock. so what do you guys think i should do? unable to flash or fastboot boot twrp at all.
heres the pics
https://imgur.com/a/WiDIqfm
For anyone that happens to run into this issue. Run fastboot OEM lock and it'll fail on the command line but reboot your device and it'll relock the bootloader. Then follow the Frankenstein guide to unlock the bootloader again.
Was able to immediately toggle OEM unlock after this
What error do you get when you try to flash?
Sent from my LG-US998 using Tapatalk
kenbo111 said:
What error do you get when you try to flash?
Click to expand...
Click to collapse
Any fastboot commands fail minus fastboot reboot
Also I have a ls998u that's been converted to us998
R800x_user said:
Any fastboot commands fail minus fastboot reboot
Also I have a ls998u that's been converted to us998
Click to expand...
Click to collapse
It's possible the greyed out button may turn active in a few days. This also happens immediately after bootloader unlock -- it's greyed out, then days later it can be toggled.
ChazzMatt said:
It's possible the greyed out button may turn active in a few days. This also happens immediately after bootloader unlock -- it's greyed out, then days later it can be toggled.
Click to expand...
Click to collapse
I want aware of the wait time. Thanks for the info
R800x_user said:
I want aware of the wait time. Thanks for the info
Click to expand...
Click to collapse
It's mentioned in the WTF instructions. See attached screenshot.
Hopefully this will happen to you, even though slightly different circumstances.
ChazzMatt said:
It's mentioned in the WTF instructions. See attached screenshot.
Hopefully this will happen to you, even though slightly different circumstances.
Click to expand...
Click to collapse
How long would one have to wait? Still grayed out.
Just an update to this.
R800x_user said:
How long would one have to wait? Still grayed out.
Just an update to this.
Click to expand...
Click to collapse
I never measured, but less than a week I think.
ChazzMatt said:
I never measured, but less than a week I think.
Click to expand...
Click to collapse
[email protected] okay, I'll need to try to OEM lock. I'm unsure if it'll even work. At least I have a functional v30. I was thinking using LGup would've relocked the bootloader if I downgraded.
i try the version of Magisk 23.0 but this is not worked.
It's the same with all other Xperia devices without customise recovery.
You first use Unsin (can find it in XDA) to the boot_blahblahblah.sin from stock firmware for unsin it. Therefore you will see a .IMG is generated.
Second, you transfer the .IMG to your phone, and use Magisk to patch (install - select file and patch) the boot file.
After it's patched (you can find it in the Download folder). Transfer the patched one back to your PC, and make phone enter fastboot mode (or the blue light mode). Then you run this command on Windows Shell (Google it, it's easy)
Fastboot flash boot the_file_name.img
After it's done, boot into your phone, you can find icon of Magisk, install it, and your phone is rooted in this stage.
Nevermind figured it out
Kylewolf said:
Nevermind figured it out
Click to expand...
Click to collapse
Before you do anything, a unlocked bootloader is must required.
JaneValley said:
It's the same with all other Xperia devices without customise recovery.
You first use Unsin (can find it in XDA) to the boot_blahblahblah.sin from stock firmware for unsin it. Therefore you will see a .IMG is generated.
Second, you transfer the .IMG to your phone, and use Magisk to patch (install - select file and patch) the boot file.
After it's patched (you can find it in the Download folder). Transfer the patched one back to your PC, and make phone enter fastboot mode (or the blue light mode). Then you run this command on Windows Shell (Google it, it's easy)
Fastboot flash boot the_file_name.img
After it's done, boot into your phone, you can find icon of Magisk, install it, and your phone is rooted in this stage.
Click to expand...
Click to collapse
good job my friend.
JaneValley said:
Before you do anything, a unlocked bootloader is must required.
Click to expand...
Click to collapse
Hello
Did you find Xperia 1 iii on Sony Developer site?
Or how did you achieve the unlock file?
Regards,
Olavbson
Where the hell do i find the official firmware, thats where im stuck
ya id like to unlock bootloader so i can achieve root on us xperia 1 iii. nothing has worked. and xperia 1 iii isnt on sony develope site to unlock bootloader. either. how are people doing this.
jporter396 said:
ya id like to unlock bootloader so i can achieve root on us xperia 1 iii. nothing has worked. and xperia 1 iii isnt on sony develope site to unlock bootloader. either. how are people doing this.
Click to expand...
Click to collapse
same am stuck at bootloader unlock rn. Cannot flash
olavbson said:
Hello
Did you find Xperia 1 iii on Sony Developer site?
Or how did you achieve the unlock file?
Regards,
Olavbson
Click to expand...
Click to collapse
Sorted it? Rooted mine earlier on. To unlock the bootloader you can just pick Xperia 1 or 1II it doesn't matter 1III will be added eventually but doesn't make a difference.
AJHutchinson said:
Sorted it? Rooted mine earlier on. To unlock the bootloader you can just pick Xperia 1 or 1II it doesn't matter 1III will be added eventually but doesn't make a difference.
Click to expand...
Click to collapse
What about DRM keys? how do u deal with that.
AJHutchinson said:
Sorted it? Rooted mine earlier on. To unlock the bootloader you can just pick Xperia 1 or 1II it doesn't matter 1III will be added eventually but doesn't make a difference.
Click to expand...
Click to collapse
Hey sorry another question, i know rooting will kill netfleex and such but did u notice any other side effects, can you still view HDR
rom4ster said:
Hey sorry another question, i know rooting will kill netfleex and such but did u notice any other side effects, can you still view HDR
Click to expand...
Click to collapse
I haven't noticed anything that's not working buddy
AJHutchinson said:
I haven't noticed anything that's not working buddy
Click to expand...
Click to collapse
Thanks, sorry to bother you more but how did you unlock the phone exactly?
I am getting this error on fastboot
fastboot oem unlock 0x2DC728328A49EEAB
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
rom4ster said:
Thanks, sorry to bother you more but how did you unlock the phone exactly?
I am getting this error on fastboot
fastboot oem unlock 0x2DC728328A49EEAB
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
Click to expand...
Click to collapse
Mine was doing the same buddy, make sure you have entered the correct IMEI and that you have OEM unlock and usb debugging turned on in the developer settings
AJHutchinson said:
Mine was doing the same buddy, make sure you have entered the correct IMEI and that you have OEM unlock and usb debugging turned on in the developer settings
Click to expand...
Click to collapse
i verified OEM unlock is on in settings I am copying the IMEI reported by ADB directly, and USB debugging is on yet the error persists. What solved it for you?
rom4ster said:
i verified OEM unlock is on in settings I am copying the IMEI reported by ADB directly, and USB debugging is on yet the error persists. What solved it for you?
Click to expand...
Click to collapse
Check the IMEI by dialing *#06# see if it matches up with that one, if using Dual SIM variant use the first code
AJHutchinson said:
Check the IMEI by dialing *#06# see if it matches up with that one, if using Dual SIM variant use the first code
Click to expand...
Click to collapse
Also is
Code:
Fastboot devices
showing a device? Maybe it's not installed properly?
same issue here. command not supported error. did everything on sony guide to the t. us variant, windows 10. not sure what to do
fastboot shows device too
jporter396 said:
same issue here. command not supported error. did everything on sony guide to the t. us variant, windows 10. not sure what to do
fastboot shows device too
Click to expand...
Click to collapse
Annoying aye, my issue was with the IMEI I must have been putting a wrong digit in but it worked eventually
So, am I correct in assuming I’m unable to do anything with this device until I can sim unlock? Seems that’s a requirement for boot loader unlock. I got one of these for cheap cheap because I need an android device with out gapps but I’m thinking that’s not going to work until it’s sim unlocked. Any info would be appreciated. Thanks!
rcartaz09 said:
So, am I correct in assuming I’m unable to do anything with this device until I can sim unlock? Seems that’s a requirement for boot loader unlock. I got one of these for cheap cheap because I need an android device with out gapps but I’m thinking that’s not going to work until it’s sim unlocked. Any info would be appreciated. Thanks!
Click to expand...
Click to collapse
A couple pages back there is a thread on how to oem unlock without sim unlock. It involves running a debloat script or using adb to get rid of one service. It goes through every step you need to do to unlock.
Link575 said:
A couple pages back there is a thread on how to oem unlock without sim unlock. It involves running a debloat script or using adb to get rid of one service. It goes through every step you need to do to unlock.
Click to expand...
Click to collapse
Thanks! Found it and so far it’s worked. Waiting for response from OnePlus.
rcartaz09 said:
Thanks! Found it and so far it’s worked. Waiting for response from OnePlus.
No problem, it takes almost exactly a week to the hour to get the code. Rest of the guide should be fairly easy to follow too. Just remember if you ever you the MSMTool to get back to stock it relocks your bootloader. You'll need to unlock it again by using the file OP sends you before flashing other nonstock firmwares again
Click to expand...
Click to collapse
rcartaz09 said:
Thanks! Found it and so far it’s worked. Waiting for response from OnePlus.
Click to expand...
Click to collapse
Once you get the code, you can simply use my dummies guide to full rom backup, convert to US OEM (DE2117), and root and has the "oem unlock bypass" command in the guide.
scanman0 said:
Once you get the code, you can simply use my dummies guide to full rom backup, convert to US OEM (DE2117), and root and has the "oem unlock bypass" command in the guide.
Click to expand...
Click to collapse
Saw that, thanks!