hi, here I am again to ask:
I installed about 2 hours, never restart the phone, the FW: V20C_00 EUR.
I tried to unlock the bootloader but when I reboot instead of giving me the scermata release, I simply restarts.
Question: What firmware should I install? and where can I download?
Thank you very much again for your patience
A lot of people are in your shoes, and this is not fully figured out yet. Some people recently suggested adb version may have something to do with it. Look for their posts for discussion and possible solution. We don't need another post on this.
Meanwhile, you can try again, at least for a few more times (30 min to 1hour waiting with phone on network needed for each try). I got my unlocked the "last time" I would like to try before giving up.
mrmathematica said:
A lot of people are in your shoes, and this is not fully figured out yet. Some people recently suggested adb version may have something to do with it. Look for their posts for discussion and possible solution. We don't need another post on this.
Meanwhile, you can try again, at least for a few more times (30 min to 1hour waiting with phone on network needed for each try). I got my unlocked the "last time" I would like to try before giving up.
Click to expand...
Click to collapse
hello, today I had an idea, I plugged the phone in fastboot mode by following this guide: http://forum.xda-developers.com/showpost.php?p=44578108&postcount=34
I tried if the phone was plugged in, all ok I found. I tried to type the command "fastboot oem unlock" it gives me an error. Now, do you think you could use fastboot to unlock the bootloader?
tonysgh89 said:
hello, today I had an idea, I plugged the phone in fastboot mode by following this guide: http://forum.xda-developers.com/showpost.php?p=44578108&postcount=34
I tried if the phone was plugged in, all ok I found. I tried to type the command "fastboot oem unlock" it gives me an error. Now, do you think you could use fastboot to unlock the bootloader?
Click to expand...
Click to collapse
Negative.
Not all OEM allow that command. LG fastboot don't even allow getvar all.
Related
Hey folks,
So i got my Atrix from RMA today, it has a new mainboard, had WLAN errors before. Tried to unlock it with ihop_bell.sbf, like last time, but it failed. Now it says failed to boot 1, the bootloader is still locked, because fastboot does not know oem unlock.
I can enter fastboot mode. If I start and press volume down it says something about nvflash for 0.5 secs and turns off. RSD detects it as SE Flash Olympus and I can start flashing, but it always fails at "Switching to BP Pass trough mode".
So what now, is it hardbricked?
Before flashing did you check your FW version (i.e. Build number/version) to see what type it was, sometimes after installing new parts they will turn it on and test it to see how it works and may hit update while at it to make sure it is ready to go out of the box
Should be the German Retail 2.3.4, did not check it though. Just made sure the WiFi Error is gone.
Uh, you might have wanted to check. You always want to ensure software revision numbers before attempting the unlock. Even some retail updates can have minor build changes that could result in your bootloader unlock bricking your phone.
So moto-fastboot is not responding to the CMD "oem unlock"? I am just going over all the info to see if I can help, I have had the "Failed to boot #" issue with a multitude of Moto's (CDMA and GSM, and my global Photon) I have also been able to fix them. Was your device fully charged before attempting the SBF flash? that will kill an SBF flash and possibly the phone.
---------- Post added at 01:29 PM ---------- Previous post was at 01:20 PM ----------
It would also appear that FTB 1 is related to not having atleast 50% charge available during the flash. You may want to get a battery charger for it and charger the phone and attempt a flash from there. This thread has a little info in it (if you read the on topic stuff) http://forum.xda-developers.com/showthread.php?t=1491788 . Good luck my friend, I know how it feels, If you have any questions let me know.
Edit: If you can get fastboot to atleast give you info on any bootloader variables (fastboot getvar <variable request>) then you may be able to find out if their was a software revision, i am unsure at this time
OMG!
After I tried flashing the international unlock like 5 times more again and the same error ocurred, I tried to unlock in fastboot after ur last post and IT WORKED
TBH I am a little bit confused, because 1 hour ago it(the unlock) did not work and really can not understand what was wrong before. Still on the same battery.
Now it is unlocked and the message is gone, I can enter e.g. the RSD mode or the recovery.
Maybe it had to do with battery indeed, I dont know, just happy that it works again. Thanks for posting mate!
Haha, That's good. Hope it stays going well for you. I hated when I flashed pudding and it failed then ran the OEM unlock code just to see if it would continue, sure enough it did. Glad to hear it is fixed
Hey everyone,
So I've been having a problem with my Z Ultra that I haven't been able to solve for a number of weeks now.
The service menu on my C6833 specifically says that the bootloader is unlockable, as shown here:
(imgur) com/OO9549 (sorry, XDA won't let me post links yet. ><)
However, when I try unlocking using Sony's official instructions (and using FlashTool) - I get the following:
fastboot -i 0x0ffce oem unlock 0x(my key here)
...
FAILED (remote: Command did not succeed)
finished. total time: 0.027s
I've copied/pasted the key, I've typed it out manually, they all get me the same error. I'm running Windows 8.1 (finally managed to get the drivers installed), yet this also happened on a Windows 7 machine. I've been racking my brain, but I can't find ANYTHING that'll help. The last time I tried, I gave up trying to unlock the bootloader and installed the DualRecovery for locked bootloaders, which ended up bricking my phone and I had to flash back to stock.
Help! I just want to be able to install custom roms again! D:
Hmm, that's strange. I've googled a bit and you're not the first xperia owner with this issue. Some say that updating or re-flashing the ROM will fix it. Which version are you running?
LordManhattan said:
Hmm, that's strange. I've googled a bit and you're not the first xperia owner with this issue. Some say that updating or re-flashing the ROM will fix it. Which version are you running?
Click to expand...
Click to collapse
I've re-flashed the ROM a few times on different versions. I'm currently on 4.2.2 - 14.1.B.2.257.
Mandersoon said:
Hey everyone,
So I've been having a problem with my Z Ultra that I haven't been able to solve for a number of weeks now.
The service menu on my C6833 specifically says that the bootloader is unlockable, as shown here:
(imgur) com/OO9549 (sorry, XDA won't let me post links yet. ><)
However, when I try unlocking using Sony's official instructions (and using FlashTool) - I get the following:
fastboot -i 0x0ffce oem unlock 0x(my key here)
...
FAILED (remote: Command did not succeed)
finished. total time: 0.027s
I've copied/pasted the key, I've typed it out manually, they all get me the same error. I'm running Windows 8.1 (finally managed to get the drivers installed), yet this also happened on a Windows 7 machine. I've been racking my brain, but I can't find ANYTHING that'll help. The last time I tried, I gave up trying to unlock the bootloader and installed the DualRecovery for locked bootloaders, which ended up bricking my phone and I had to flash back to stock.
Help! I just want to be able to install custom roms again! D:
Click to expand...
Click to collapse
I had the same problem when I tried to unlock.
Tried 5 times and then was finally successful. Ensure that you have typed out the commands correctly. Don't copy and paste as that wont work.
Are you getting the same error in Flashtool?
Sent from my C6833 using Tapatalk
LordManhattan said:
Are you getting the same error in Flashtool?
Sent from my C6833 using Tapatalk
Click to expand...
Click to collapse
I can't be sure as it was 3/4 months ago. Kept having issues, and I gave up. Then came back and after many attempts it worked. It was incorrect commands i was typing. 0 or O may have been the problem, or no space where they should be one.
If it says command failed then it sounds like you have the command correct, but the key is incorrect or the format of your input after the command is incorrect.
Also... are you rooted? Root first then try agian
hamdogg said:
I can't be sure as it was 3/4 months ago. Kept having issues, and I gave up. Then came back and after many attempts it worked. It was incorrect commands i was typing. 0 or O may have been the problem, or no space where they should be one.
If it says command failed then it sounds like you have the command correct, but the key is incorrect or the format of your input after the command is incorrect.
Also... are you rooted? Root first then try agian
Click to expand...
Click to collapse
I have copied/pasted, as well as typing out the commands. This has happened with Flashtool as well as in the command prompt.
And the phone is rooted.
EDIT:
I figured out the problem. I ended up using flashtool for the whole process. Windows 8.1's Driver Signature Verification NEEDS to be turned off. I ended up getting a new unlock code from Sony and that worked.
Mandersoon said:
I have copied/pasted, as well as typing out the commands. This has happened with Flashtool as well as in the command prompt.
And the phone is rooted.
EDIT:
I figured out the problem. I ended up using flashtool for the whole process. Windows 8.1's Driver Signature Verification NEEDS to be turned off. I ended up getting a new unlock code from Sony and that worked.
Click to expand...
Click to collapse
Hi Mandersoon,
I am in same problem and do you have any link or email to get new Unlock code from sony?
Thanks.
Encountered this on my first try. Then on the second attempt, it went through.
i had the same problem, it said "FAILED (remote: Incorrect format for unlock data. Should be on the form "0x)" so I did exactly as it said - added "0x" before my code and it worked!
I just removed "0x" from the unlock code given by sony, it worked like a charm. :good:
I dont know why.
BlackCatAlex said:
i had the same problem, it said "FAILED (remote: Incorrect format for unlock data. Should be on the form "0x)" so I did exactly as it said - added "0x" before my code and it worked!
Click to expand...
Click to collapse
can you please share the code i cant understand where to add 0x. i am facing the same issue. reply ASAP
Do not share the code/key. That's your unique key.
@psylbaba: it says "added "0x" before my code", so I assume he means 0x in front of the key when you're unlocking in Flashtool.
I just.....removed 0x and the <> in my code and it worked like a charm. Curious. (XZ1 user here)
Hi, found this thread when I was trying to unlock a Xperia z2, for me worked removing only the <> like this: fastboot oem unlock 0x"CODE"
Right click, administrator mode
Who can help me, I can not unlock my OnePlus 2 A2001. ADB is installed, they see my phone, but if I want to unlock, nothing happens. I do not know how to continue. I use Windows 10
Regards,
Harry
hrvw said:
Who can help me, I can not unlock my OnePlus 2 A2001. ADB is installed, they see my phone, but if I want to unlock, nothing happens. I do not know how to continue. I use Windows 10
Regards,
Harry
Click to expand...
Click to collapse
Did you enable developer settings and enable the option to unlock bootloader?
Sent from my ONE A2005 using XDA-Developers mobile app
hrvw said:
Who can help me, I can not unlock my OnePlus 2 A2001. ADB is installed, they see my phone, but if I want to unlock, nothing happens. I do not know how to continue. I use Windows 10
Regards,
Harry
Click to expand...
Click to collapse
Follow this guide, It will work https://forums.oneplus.net/threads/...wrp-root-nandroid-efs-backup-and-more.345478/
Hello again,
I have followed these steps but it did not work. When I started my OnePlus 2 in bootloder and then you have entered the code fastboot devices and my phone is seen. The Code fastboot devices is also still good but if I fastboot oem unlock code entry, nothing happens I can not choose between one and two I saw hebop an explanation on youtube. Everything just stays the same and my phone is not fully datawiped and all files are still there just. The Code fastboot reboot my phone restarts. what can I do about this?
As I understand you have follow that guide and now you have
enabled in settings, developer options,
OEM unlocking.
Then in fastboot mode device is discovered by "fastboot devices" that means drivers are properly installed.
Whenever your try to execute "fastboot OEM unlock" your device restart but don't unlock the bootloader.
What I would do is different things first to factory reset and try to unlock again.
Try on different computer.
Flash latest official signed rom and try the unlocking procedure again
Sent from my ONE A2005 using Tapatalk
hrvw said:
Hello again,
I have followed these steps but it did not work. When I started my OnePlus 2 in bootloder and then you have entered the code fastboot devices and my phone is seen. The Code fastboot devices is also still good but if I fastboot oem unlock code entry, nothing happens I can not choose between one and two I saw hebop an explanation on youtube. Everything just stays the same and my phone is not fully datawiped and all files are still there just. The Code fastboot reboot my phone restarts. what can I do about this?
Click to expand...
Click to collapse
Hello, have you managed to fix your issue about root as described above? Because I have the same problem and I've tried many tricks without a positive result. Any help, please?
Thanks.
abenguru said:
Hello, have you managed to fix your issue about root as described above? Because I have the same problem and I've tried many tricks without a positive result. Any help, please?
Thanks.
Click to expand...
Click to collapse
I have not tried yet, but go do it within short and then I'll let you know if it worked.
This did not work. do you have any more tips?
So I got this Sony Xperia X model F5121 from one of my relatives, and I ran into quite a few issues when I tried rooting it. it says Bootloader Unlock Allowed: NO, which would mean that i couldn't get into fastboot mode and unlock my bootloader but here's the very specific and weird part: I can get into fastboot mode, at least I believe so. My phone was carrier locked to Vodafone but I payed a professional to unlock that and now I can use every SIM I want. I looked online and the first XDA page said that unlocking the SIM meant that fastboot mode is unlocked as well. So I tried, I plugged my phone in while holding the volume key, a blue light popped up and it meant I was currently using fastboot mode, but when i try doing anything it says "waiting for devices" and doesnt end up working at all. Am I missing some drivers? Is it just impossible? Could one of you be kind enough to provide the needed files and some instructions for this procedure? i'm asking for a lot, I know but if there's anyone kind enough. I'm running the absolute latest version of Android 8 Sony provides.
EDIT: YEs, used adb shell, I have the ADB drivers, I tried the szuzu install or what the TWRP codename for it is, but everything just stops at "waiting for devices" and I can't do anything.
Since you are not allowed to unlock the bootloader - Bootloader unlock allowed - No, there is no way to unlock it and root it. Sorry.
even if you want to try again, make sure to force install googles drivers
instead of sonys
ahsvanz
try
C:\ADB >fastboot devices
C:\ADB >fastboot OEM device-info
etc
replacing
C:\ADB with where ever you fastboot file is located
I too am having the same issue.
I recently wanted to try Android 12, I took a chinnese version of it and my phone is unusable, literally all chinnese.
I want to downgrade, I enabled Debugging and Oeam Unlock in Dev options but I get the ''remote: 'Flashing Unlock is not allowed"" when I try to fastboot oem unlock, I tried different USB ports, I keep updating all my drivers for ADB but nothing is working. I'm panicking a bit cause I don't have a phone to use, and not many people work with ONEPLUS in my country.
If someone has an answer, please save me lol
slimmynine said:
I too am having the same issue.
I recently wanted to try Android 12, I took a chinnese version of it and my phone is unusable, literally all chinnese.
I want to downgrade, I enabled Debugging and Oeam Unlock in Dev options but I get the ''remote: 'Flashing Unlock is not allowed"" when I try to fastboot oem unlock, I tried different USB ports, I keep updating all my drivers for ADB but nothing is working. I'm panicking a bit cause I don't have a phone to use, and not many people work with ONEPLUS in my country.
If someone has an answer, please save me lol
Click to expand...
Click to collapse
have you tried the code above ??
cant you just download the official original firmware and flash that ? im not familiar with the oneplus flashing techniques, ive always had samsungs except for the htc evo 3d back in the day
I tried them all, nothing seems to work
I'm stuck at 'Flashing unlock is not allowed'. I've set up everything I need to in Developer Options, I made sure they're all enabled.
It's really weird, could it potentially be a software issue? The software itself will not allow me to unlock OEM even though the check is turned on?
slimmynine said:
I tried them all, nothing seems to work
I'm stuck at 'Flashing unlock is not allowed'. I've set up everything I need to in Developer Options, I made sure they're all enabled.
It's really weird, could it potentially be a software issue? The software itself will not allow me to unlock OEM even though the check is turned on?
Click to expand...
Click to collapse
how does the one plus flash firmware ? for samsung we use a tool called odin, do you not have a similar tool for your device ?
I don't recall having any toolkit like that, but in order for the toolkit to work.. do you need to have an unlocked bootloader?
Cause the main issue is that I can't unlock it.
i dont think so, if your flashing an official firmware, but for your device i cant be sure of that
?
did you try running your commands as an su , is your device rooted ? you could try sideloading an update.zip maybe
what does it say when you flash this command ? true, true false ?
C:\ADB>fastboot OEM device-info
maybe this will help https://forum.xda-developers.com/t/...us-2-back-to-stock-100.3269543/#post-64279667
slimmynine said:
I too am having the same issue.
I recently wanted to try Android 12, I took a chinnese version of it and my phone is unusable, literally all chinnese.
I want to downgrade, I enabled Debugging and Oeam Unlock in Dev options but I get the ''remote: 'Flashing Unlock is not allowed"" when I try to fastboot oem unlock, I tried different USB ports, I keep updating all my drivers for ADB but nothing is working. I'm panicking a bit cause I don't have a phone to use, and not many people work with ONEPLUS in my country.
If someone has an answer, please save me lol
Click to expand...
Click to collapse
yeah i think some phone makers lock down the bootloader, like its unlocked but when i try to flash a gsi it says device locked state
jamsandpeabug said:
alcatel has a program to download and install firmware but the device is not listed, cannot find fw on the net
Click to expand...
Click to collapse
OK try
c:\adb
Adb fastboot oem device-info
Replacing
C:\adb
With where ever your fastboot is located
Just to check if your device is showing is oem locked or unlocked, it will display with a true or false option. I can't really advise to much as I don't have experience with that device
You could also try
fastboot oem unlock_critical
Not sure if that will work for your device though
Idk what else to recommend, are you stuck at boot ? Can u boot into recovery mode ? Do u have an ext sd card slot
OT-6025D | GSMSERVERPRO
gsmserverpro.com
Is that your firmware
Alcatel 1s Flash File Download [Stock ROM or Firmware
You can Download latest flash file and flash tools for Alcatel 1s phone here. Original stock ROM or Firmware available for free.
mobilereset99.com
Have youlooked at that
if you can confirm your phone has a mtk chipset use mtkclient to bootloader unlock it https://github.com/bkerler/mtkclient
otherwise youre out of luck
But
jamsandpeabug said:
im not stuck at boot, i want to flash gsi but it says device is in locked state even with oem unlocked in dev options, adb debugging enabled etc , and just wont let me flash.. its starts flashing and then fails due to locked state
Click to expand...
Click to collapse
If the flashing starts, and fails, the os would be overwritten and you wouldn't be able to boot. So what you mean is the process trys to start but fails, right yh then I don't know what else I can say to try and help, let's hope mtkclient is an avenue you can pursue
MOD ACTION:
Thread closed since OP has no content.