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
Related
When unlocking the bootloader for the tablet Z i xperienced some problems.
So I made a more extensive guide than the one from Sony
You can find it Here
Greetings!
Sieth said:
When unlocking the bootloader for the tablet Z i xperienced some problems.
So I made a more extensive guide than the one from Sony
You can find it Here
Greetings!
Click to expand...
Click to collapse
Wow, that's a long guide. Is the main/only reason to unlock the bootloader to install custom roms (can't this be done with just root access?).
I have root, but don't really wish to install custom roms. I don't have the bootloader unlocked, but I know it can be unlocked
why to unlock bootloader?
why to unlock bootloader?
1. u can flash custom ROMs/Kernels
2. u dont need to worry if the new firmware can be rooted or not as with unlocked bootloader u can always ROOT ur device
3. Sony gives sneak-peaks/preview builds of latest OS which requires unlocked bootloaders, as they did with Xperia 2011/2012 line, so who knows may be Sony may give early builds of next android OS
Best guide I found online. Thanks!
suleiman.aql said:
Best guide I found online. Thanks!
Click to expand...
Click to collapse
I think it would be wise to mention not to forget to backup TA partition with DRM keys before bootloader unlock.
Thank you very much. This tutorial covered all the issues I ran into so I knew what to do.
Btw, the .bat for allowing unsigned drivers doesn't work on Windows 8. A quick google search helped me but maybe you might want to add that to your tutorial for other, less techy users.
Rootk1t said:
I think it would be wise to mention not to forget to backup TA partition with DRM keys before bootloader unlock.
Click to expand...
Click to collapse
Wish I saw this post earlier. Oh well.
its not asking me for the driver at step 14, anyone have suggestions on what to do
Sieth said:
When unlocking the bootloader for the tablet Z i xperienced some problems.
So I made a more extensive guide than the one from Sony
You can find it Here
Greetings!
Click to expand...
Click to collapse
Thank you so much, you saved my bricked tablet!
I won't go into details but I really messed up and this saved me, I would hit that thanks button a million times if I could!
any help
Hi all I have the lte tablet z. When I go to the service menu I can see it cant be unlocked. Dose that mean I cant root it to put a custom recoveryand custom Rom on it. Sorry to sound noob
abbo76 said:
Hi all I have the lte tablet z. When I go to the service menu I can see it cant be unlocked. Dose that mean I cant root it to put a custom recoveryand custom Rom on it. Sorry to sound noob
Click to expand...
Click to collapse
if your bootloader can't be unlocked it means that you can root your device, but won't be able to install any custom firmware. But you can install XZDR recovery.
Once you get the bootloader unlocked what is the root method? Also, is there a different process for flashing roms?
kuhl_man said:
Once you get the bootloader unlocked what is the root method? Also, is there a different process for flashing roms?
Click to expand...
Click to collapse
to root device you don't have to unlock bootloader. Unlocking is for installing custom ROMs.
That I understand. Thank you. I was asking since i already unlocked the bootloader and am unrooted. What is the process to gain root at this point?
kuhl_man said:
That I understand. Thank you. I was asking since i already unlocked the bootloader and am unrooted. What is the process to gain root at this point?
Click to expand...
Click to collapse
flash or hotboot kernel (or flash recovery to FOTA partition) with recovery and flash SuperSU from it.
Wow bro u just copy my work from htcmania this is the link
http://www.htcmania.com/showthread.php?t=706381 is easy thrue just delete my Spanish traduction and look for the date I make it in 2013 bro very nice copy and paste from my work only u just delete my spanish
unlock bootloader on SGP312
Hi
any reason why after following all step to unlock the bootloader on my SGP312 I get lock in a boot loop.........
As soon as the boot animation start it freeze and the tab reboot........
Fastboot command work after Fastboot -i............... the PC show the amount of second........
I got my number from Sony to unlock...
Curiosity...........
Thanks.......
MikeViller said:
Hi
any reason why after following all step to unlock the bootloader on my SGP312 I get lock in a boot loop.........
As soon as the boot animation start it freeze and the tab reboot........
Fastboot command work after Fastboot -i............... the PC show the amount of second........
I got my number from Sony to unlock...
Curiosity...........
Thanks.......
Click to expand...
Click to collapse
Bro if u fallow my link in htcmania is really good is working but this guy copy my work just follow the instructions in my link many users of htcmania unlock the bootloader of the tablet
---------- Post added at 12:12 AM ---------- Previous post was at 12:09 AM ----------
Sieth said:
When unlocking the bootloader for the tablet Z i xperienced some problems.
So I made a more extensive guide than the one from Sony
You can find it Here
Greetings!
Click to expand...
Click to collapse
I don't say thank you for your copy, this is u steal my work u don't deserve nothing soon I will post my work from htcmania here
Don't suppose anyone can help please. I am trying to unlock my bootloader. I have successfully connected to my computer by fastboot and everything is recognised and looks to be fine right up until I put the unlock command in and I get this error.
c:\sdk\platform-tools>fastboot devices
CB5A1WYECJ fastboot
c:\sdk\platform-tools>>fastboot -i 0x0fce oem unlock 0xFBCD6A2B26CB8F88
'-i' is not recognized as an internal or external command,
operable program or batch file.
c:\sdk\platform-tools>
its now starting to drive me crazy. Thanks very much in advance
kingguff said:
Don't suppose anyone can help please. I am trying to unlock my bootloader. I have successfully connected to my computer by fastboot and everything is recognised and looks to be fine right up until I put the unlock command in and I get this error.
its now starting to drive me crazy. Thanks very much in advance
Click to expand...
Click to collapse
Use Flashtool. It can automatically unlock bootloader. Only unlock code 0xFBCD6A2B26CB8F88 is needed.
Cant figure out which file to replace and where it is. Can get my tab to recognize in adb devices mode but nothing is coming up when i type fastboot devices in adb. It is not recognized. I am stuck. Any help will be appreciated. I have got unlock code and the usb inf file but no light further.
Hi everyone!
This is my first time here so bear with me. I recently tried flashing cm12 on my kindle fire hdx 7" and apparently flashed it in the wrong place. Right now its stuck in fastboot mode and everytime I try and flash something it gives me this error:
Code:
FAILED (remote: flashing not allowed for locked hw)
I don't know what i'm doing wrong and it won't leave fastboot mode. Can any of you all help me?
tekmeister98 said:
Hi everyone!
This is my first time here so bear with me. I recently tried flashing cm12 on my kindle fire hdx 7" and apparently flashed it in the wrong place. Right now its stuck in fastboot mode and everytime I try and flash something it gives me this error:
Code:
FAILED (remote: flashing not allowed for locked hw)
I don't know what i'm doing wrong and it won't leave fastboot mode. Can any of you all help me?
Click to expand...
Click to collapse
Oh I forgot to mention I was on fire os 4.5.2 before this happened.
You can't flash CM12 on 4.5.2 — or any other ROM, for that matter.
EncryptedCurse said:
You can't flash CM12 on 4.5.2 — or any other ROM, for that matter.
Click to expand...
Click to collapse
well this happened before i acutally did that. It was trying to flash either twrp or safestrap.. one of the two. i think i flashed one of them in the boot partition and its locked up now
tekmeister98 said:
well this happened before i acutally did that. It was trying to flash either twrp or safestrap.. one of the two. i think i flashed one of them in the boot partition and its locked up now
Click to expand...
Click to collapse
I guess what i'm asking is how to fix it. No matter what I do its just telling me I can't flash to locked hw.
tekmeister98 said:
I guess what i'm asking is how to fix it. No matter what I do its just telling me I can't flash to locked hw.
Click to expand...
Click to collapse
And I can't get to adb shell... so I need help.
Adb commands do not work in fastboot. What you need to do is reboot it with the fastboot version of the adb command that got you there.
Something like fastboot reboot recovery (I do not remember if there was a reboot system command). You can find the commands in the unlock boot loader thread in the original dev section.
lekofraggle said:
Adb commands do not work in fastboot. What you need to do is reboot it with the fastboot version of the adb command that got you there.
Something like fastboot reboot recovery (I do not remember if there was a reboot system command). You can find the commands in the unlock boot loader thread in the original dev section.
Click to expand...
Click to collapse
I've tried that but I'm stuck in a bootloop.
In the bootloop, if you have a grey and orange logo, and you have enabled adb, you can use adb commands. With root, even shell. However, if it only boots to fastboot, your system is corrupted. Try holding down the plus volume button on boot to see if you can get to recovery.
lekofraggle said:
In the bootloop, if you have a grey and orange logo, and you have enabled adb, you can use adb commands. With root, even shell. However, if it only boots to fastboot, your system is corrupted. Try holding down the plus volume button on boot to see if you can get to recovery.
Click to expand...
Click to collapse
Yeah that doesn't work. Is there any fix for a corrupted system?
The only fix if your bootloader is locked (which it almost definitely is), is to get fastboot to install an oem system or recovery image. I do not think it will work though. Read up on fastboot. Use the number code for our device before each operation.
lekofraggle said:
The only fix if your bootloader is locked (which it almost definitely is), is to get fastboot to install an oem system or recovery image. I do not think it will work though. Read up on fastboot. Use the number code for our device before each operation.
Click to expand...
Click to collapse
hmmm.. okay. Are you able to give me a cat /sys/block/mmcblk0/device/manfid and a cat /sys/block/mmcblk0/device/serial on a device of yours so I can try and unlock it?
No, those numbers are custom to devices and non-transferable. Also, my bootloader is old and unlocked. Sorry.
lekofraggle said:
No, those numbers are custom to devices and non-transferable. Also, my bootloader is old and unlocked. Sorry.
Click to expand...
Click to collapse
dang. Okay. Thanks for the help though. I'll just have to keep at it.
did you ever get your bootloader unlocked?
bowman1966 said:
did you ever get your bootloader unlocked?
Click to expand...
Click to collapse
Nope. I tried a bunch of stuff but it didn't work.
Well, the bootloader of versions 3.2.3.2 and lower can be unlocked only, so unsurprisingly your (tekmeister98) 4.5.2 bootloader couldn't be unlocked. But why you, bowman1966, can't do it if you had TWRP installed remains a mystery to me.
Cl4ncy said:
Well, the bootloader of versions 3.2.3.2 and lower can be unlocked only, so unsurprisingly your (tekmeister98) 4.5.2 bootloader couldn't be unlocked. But why you, bowman1966, can't do it if you had TWRP installed remains a mystery to me.
Click to expand...
Click to collapse
Thats just par for my coarce lol.
Ill let it sit awhile and play another day....
Resurrecting this thread... Any new fixes out yet? I've seen workarounds for starting with stock os but other than that I don't know.
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?
Ive tried all the normal ways fastboot oem lock ect ect
And it it safe for me? Are there any prequisite's?
Thanks
medseven said:
Ive tried all the normal ways fastboot oem lock ect ect
And it it safe for me? Are there any prequisite's?
Thanks
Click to expand...
Click to collapse
The "fastboot oem lock" command does not exist, it is certainly not a normal way
The best method to lock bootloader is searching for the Service rom on https://androidhost.ru/ and doing the dload method. Process will erase all the data from your device !
(Before you do anything, read carefully Software Upgrade Guidline in "ReleaseDoc" . With Service ROM you will get full stock with locked bootloader (warranty will not void any more).)
Hi thanks a lot for your reply, Unfortunately I cannot find such rom on the site for the life of me.
medseven said:
Hi thanks a lot for your reply, Unfortunately I cannot find such rom on the site for the life of me.
Click to expand...
Click to collapse
Hi, which build number do you run? (e.g. ANE-LX1 9.1.0.306 (C432))
bozka1 said:
The "fastboot oem lock" command does not exist, it is certainly not a normal way
The best method to lock bootloader is searching for the Service rom on https://androidhost.ru/ and doing the dload method. Process will erase all the data from your device !
(Before you do anything, read carefully Software Upgrade Guidline in "ReleaseDoc" . With Service ROM you will get full stock with locked bootloader (warranty will not void any more).)
Click to expand...
Click to collapse
bozka1 said:
Hi, which build number do you run? (e.g. ANE-LX1 9.1.0.306 (C432))
Click to expand...
Click to collapse
it is ane-lgprs-ovs 9.1.0.13 it does not show me the c variant.
I see your replying to my other thread aswell, no point having 2 so I will carry on here.
I have downloaded a rom called Huawei P20 Lite ANE-LX1 ANE-L01 hw eu HLRCF Anne-L01 8.0.0.167(C432) Firmware 8.0.0 r1 EMUI8.0 05015ACF [androidhost.ru] so I am going to try this with HuRUUpdater 0.4
medseven said:
it is ane-lgprs-ovs 9.1.0.13 it does not show me the c variant.
Click to expand...
Click to collapse
It can be found in System - About phone . It's very important.
all it gives me in build number is ANE-LGRPS-OVS 9.1.0.132
there really is no brackets or c variant
medseven said:
all it gives me in build number is ANE-LGRPS-OVS 9.1.0.132
there really is no brackets or c variant
Click to expand...
Click to collapse
Strange, maybe you tried to install some firmware manually before, hm?
Connect your phone in fastboot mode to PC , open 'Minimal ADB and fastboot' and use command
fastboot oem get-build-number
Unfortunately not even HuRUUpdater 0.4 is working with this particular rom it reports unknown error so I am at a complete loss really
bozka1 said:
The "fastboot oem lock" command does not exist, it is certainly not a normal way
The best method to lock bootloader is searching for the Service rom on https://androidhost.ru/ and doing the dload method. Process will erase all the data from your device !
(Before you do anything, read carefully Software Upgrade Guidline in "ReleaseDoc" . With Service ROM you will get full stock with locked bootloader (warranty will not void any more).)
Click to expand...
Click to collapse
bozka1 said:
Hi, which build number do you run? (e.g. ANE-LX1 9.1.0.306 (C432))
Click to expand...
Click to collapse
bozka1 said:
Strange, maybe you tried to install some firmware manually before, hm?
Connect your phone in fastboot mode to PC , open 'Minimal ADB and fastboot' and use command
fastboot oem get-build-number
Click to expand...
Click to collapse
even with fastboot its the same, no brackets or c variant!
on another not are the service roms called 'board software' ?
medseven said:
even with fastboot its the same, no brackets or c variant!
Click to expand...
Click to collapse
it should now be clear that you have installed the wrong version of firmware, IMO...
I can't you help anymore, sorry.
ok thanks for your time
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