I have recently tried unlocking my bootloader on my Arc S using fastboot with this nice video that taught me how but when i go to put this code in the CMD (fastboot.exe -i 0x0fce getvar version) i get something saying "waiting for device"
i dont whats wrong i have ADB installed and everything else to perform this unlock, could anyone please tell me how to fix this problem for the Xperia Arc S thank you
- Bootloader Unlockable: Yes
- Build: 4.0.2.a.0.62
- Version: 2.3.4
I want to unlock my bootloader so i can install custom kernels and also root my phone
Edit: not allowed to link the video due to not enough posts (im new)
Just try with flashtools, search in the forum there are many guides on how to do it, unlock bootloader, root, and flash rom etc.... with flashtools
I had this problem yesterday, the problem I had was the phone was not going in to fastboot mode. Is the light on your phone going blue and staying blue while the screen is black? On mine the light flicked onfor 5 seconds then off and the phone then went into recovery.
Related
Hey everyone, I just relocked my arc so that I could update via SEUS. After the update, initially it entered fastboot mode but for some reason fastboot was't working. Now, the Blue LED does not even come on on my phone. It just glows green for a while and thats it.
Anyone with any ideas on how to fix this problem?
Thanks in advance!
after rolocking fastboot will become unavailable.
you should have read a little through the forum.
Fastboot is only available for bootloader unlocked devices
all you can do is re-unlock again using your old key
Did the same. Your original code will unlock it again.
sinkster
Im lost I m not sure if mines locked or not
Lol if I put my phone in fast boot and type fast boot devices I get a return with a device
But when I try fastboot flash boot.img I get no partision lol any one care to help
Ps I unlocked it bricked it tryed to lock again so I could use seus it worked , but when I try to unlock again it says command not found
Lol
Sent from my U20i using XDA App
Hi, I recently unlocked the bootloader of my XPERIA M device through Sony's fastboot method but after doing it successfully my phone stuck into bootloop in which the wavy animation of color appears and vanish. However the phone is visible in the fastboot devices in cmd prompt.
HOW TO FIX THIS??????
Mohit005 said:
Hi, I recently unlocked the bootloader of my XPERIA M device through Sony's fastboot method but after doing it successfully my phone stuck into bootloop in which the wavy animation of color appears and vanish. However the phone is visible in the fastboot devices in cmd prompt.
HOW TO FIX THIS??????
Click to expand...
Click to collapse
This thread will be moved to Xperia M Q&A, Help & Troubleshooting
this always happens after unlocking bootloader, just reflash stock rom via flashtool
flash the stock firmware
Mohit005 said:
Hi, I recently unlocked the bootloader of my XPERIA M device through Sony's fastboot method but after doing it successfully my phone stuck into bootloop in which the wavy animation of color appears and vanish. However the phone is visible in the fastboot devices in cmd prompt.
HOW TO FIX THIS??????
Click to expand...
Click to collapse
flash the stock firmware of your phone .. this will fix bootloop
Welcome. I have Xperia T3 D5103 with locked Bootloader, status NO. BUT, when i flashed i clicked wrong Volume button and i pressed UP for Fastboot, no DOWN for flashmode. But.. It joins Fastboot, i had Blue LED. So can i flash what i want? i dont want to brick my phone, im not new in it but.. You know. Stress I have now android 4.4.4 stock without anything. Please help me ;c
So the phone shows up when you run the command fastboot devices? Interesting, but I don't think you can flash anything since the bootloader is locked.
hehe, you can flash but probably you could not boot phone, turn on.
Hi
Did you see that? Is it fake?
http://bootloader-unlock-allowed-no...ow-to-unlock-bootloader-which-is-non.html?m=1
Hello.
I've searched forums and found some threads like this but my problem is a bit like them and a little bit different at the same time.
Sorry for my ENGRISH
I have Sony Ericsson Arc S, (LT18i). My brother bought it from UK and bringed to me, to Türkiye (Turkey). As you guessed, Turkish simcards didn't work and my brother gave money to a mobile phone seller to unlock it's simlock. After this, we able to use phone with Turkish simcards in Turkey.
The other day, after a couple years, I wanted to install a custom ROM on my Arc S.
This is how everything started.
I searched XDA forums and took notes. How can I do it, which programs needed etc.
Preparing
First, I did a factory reset.
After the phone opened, I changed usb connection to MSC, allowed Unknown sources and opened USB debugging.
I installed Flashtool 0.9.10.0. I readed a couple posts about that, previous versions gives no errors.
Under /drivers folder I found a driver package. Installed it with just Flashmode, Fastboot and Sony Ericsson Arc drivers selected.
Pluged in my phone and checked if it's drivers installed or not. Success. I can see my phone in device manager.
Installing
I readed a few guides and they say I have to Unlock bootloader. So I clicked Bootloader Unlock option in Flashtool. Followed the instructions, gone into flashmode, restart, gone into fastmode with pressing menu button and plugging the usb cable etc. There was a window with my IMEI and I followed the instructions and I get a code (long, including letters and numbers) from official sony website. I entered this code to that window and it said my bootloader is unlocked.
After that, I rooted the device. No errors.
Installed CWM via Flashtool. No errors as far as I remember.
AND THIS: Flashing a ROM. I found an Android 5.0.1 ROM and it said that I had to flash boot.img. So I did. I mean, I tried. I GOT ERROR. And, BUM. Something happened and I couldn't open the phone.
After a search, I found a solution says using Sony Companion may restore the phone. I tried this. Follow the instructions and my phone opened with ICS 4.0.4 instead of old version, 2.3. And now, it says, INSERT THE SIM CARD.
I searched the forums about 2 days and didn't find a solution to this. It ignores my sim card. Then, I saw a secret code about simlock and bootloader status and entered that code *#*#7378423#*#*
Under Simlock option,
They say there must be X's. At least the first one must have X on simlock screen but it hasn't. And there are all 0's. No X's, and zeros. So this is bad i think.
Under Configuration
In configuration section, it says Bootloader Unlock Allowed: No. As far as I learned from XDA forums, that means bootloader is locked again. Because it must be unlocked or unlock allowed: yes.
So i tried to unlock bootloader again. I had no idea what I've done. First, it said go flashmode. Done. And it said go into Fastboot. I couldn't. No Blue LED.
You see the thing? => Flashtools says go Fastboot to run Bootloader unlocker. I can't. Forums says I have to bootlocker unlock to enter fastboot. Bootloader unlock to enter fastboot. But enter fastboot to boot unlock. Wow.
Lastly, I tried flashing custom TFT's to see if it can flash or not. IT FLASHED. I can flash STOCK TFT's, even a KERNEL i downloaded from here. I can Root, install Busybox ( I don't know what is it haha), Install CWM 5.0.
But since it can't see my Sim Card, i didn't try to install custom ROM.
What I have to do? How can I unlock to simcard lock if it's locked? is my bootloader locked?
My brain hurts.
I wrote all things because it's easy to solve a problem with more information. So a few things more:
I use Windows 10.
I didn't use original cable at first. But you know, no errors now. It's not important at this point I think.
I unistalled mobile device from devices manager and delete the driver. I installed inf file from sony website and selected it for ADB driver. It says now Sony sa01102 ADB Interface Driver. If Fastboot needs correct drivers, I installed from it's official site, offical one.
I didn't tried another computer because again; no errors from Flashtool.
THANK YOU ALL.
I maybe copy this to other websites.
About Loader.sin Error
I did get Loader.sin Error a few times. But when I use previous Flashtool version, there was no loader.sin error.
"In configuration section, it says Bootloader Unlock Allowed: No. As far as I learned from XDA forums, that means bootloader is locked again. Because it must be unlocked or unlock allowed: yes." It means you cannot unlock bootloader! Its not possible , your phone is locked , i mean you cant run fastboot mode , its locked , install stock firmware and thats all , you cant install any custom firmwares as Cyanogenmod or custom kernel anymore. If you can't understand it sorry because english is not my main language.
Calling all the Huawei Experts to help me out on this!!
Short Summary of problem
On my Ascend Mate 7 MT7-TL10 (running Android 5.1.1 version B326) -The bootloader shows as unlocked but I still can't flash a custom recovery - It gives error 'FAILED (remote: image verification error)'. I am using the lastest version of ADB/Fastboot, I have USB drivers installed and I also have the Bootloader Unlock code from Huawei, which works and shows 'Done'
Please read the details below first and kindly see all attachments
Click to expand...
Click to collapse
Little bit more information
- On the Bootloader screen of my MT7-TL10 (Gold 32 GB, 3 GB RAM version), I see "Phone Unlocked" in red, which means that my bootloader is unlocked. (refer to attachment)
- When I run the command 'Fastboot OEM get-bootinfo', it returns 'UNLOCKED'.
- However, whenever I try to flash a custom recovery, it gives me an error 'FAILED: (remote: image verification error).
- At the same time, if I flash stock recovery, it is successful.
Detailed Information
- When I run the command 'fastboot oem get-bootinfo' it returns 'UNLOCKED'.
- However, when I run the command 'fastboot oem get-lockstate', it returns 'Locked'
- I rolled back to KitKat 4.4.2 - But the process of roll-back to KitKat 4.4.2 was not as simple as it was described in many forums and I first ended up soft-bricking the device
- I followed the restore process described on Huawei's website and ended up flashing a chinese ROM (JAZZ) on my MT7-TL10 and there were plethora of chinese apps
- Then, I unlocked the bootloader using (fastboot oem unlock <unlock code>) and on KitKat, both commands 'fastboot oem get-bootinfo' and 'fastboot oem get-lockstate' returned 'UNLOCKED' (Hurray!, That's what I thought but...)
- Realizing that the bootloader was finally unlocked, with the help of @acbka, I was finally able to restore Lollipop (version 5.1.1 - B326) and to my utter disgust, after upgrading, I found out that I was again not able to flash a custom ROM - On Lollipop, the command 'fastboot oem get-lockstate' again returned 'LOCKED' and the command 'fastboot oem get-bootinfo' returned 'UNLOCKED'
- As you can see, I was back to square 1 and I still can't unlock the bootloader and therefore, I cannot root my phone
Final statement
- When I rolled back to KitKat, the Bootloader showed as Unlocked and I was able to flash custom recovery TWRP
- After upgrading to Lollipop (5.1.1 B324 and B326), I am unable to flash custom recovery (somehow, the bootloader shows as 'Locked' when I run 'fastboot oem get-lockstate')
- If I flash stock recovery, it is successful
- The error 'FAILED (remote: image verification error)' implies that the bootloader is locked and that's why it forbids flashing of custom recovery BUT it allows flashing stock recovery
Please see the attached pictures, which will show what I mean.
I will really appreciate any help to enable me to flash a custom recovery!! Please help!
i also face the same problem any one can help us ?
try another bat file to flash recovery,
http://forum.xda-developers.com/mate-7/orig-development/tool-android-4-4-5-1-pc-t3186984
Thanks for replying. However, this won't help because I am directly running the fastboot command (not using a .bat file). The link that you posted is dead...
Please read this: I have explained in my post with scrrenshots that the fastboot command 'fastboot oem unlock CODE' works and shows 'Done', which means that it has unlocked the bootloader. If you repeat the command, it shows 'user already unlocked', which is a proof that the Fastboot command is working.
However, the problem is that flashing a custom Recovery shows a 'remote' error, which means that it is the bootloader, which is preventing the flashing of the custom recovery.
The problem is that on Android 5.1.1, the bootloader is appearing as locked even though the fastboot procedure shows that the bootloader was unlocked.
I have tried different fastboot binaries and also tried different procedures (including BAT files) but not able to beat this problem.
Sent from my HUAWEI MT7-TL10 using Tapatalk
prahastaabenk said:
try another bat file to flash recovery,
http://forum.xda-developers.com/mate-7/orig-development/tool-android-4-4-5-1-pc-t3186984
Click to expand...
Click to collapse
kingrk said:
Thanks for replying. However, this won't help because I am directly running the fastboot command (not using a .bat file). The link that you posted is dead...
Please read this: I have explained in my post with scrrenshots that the fastboot command 'fastboot oem unlock CODE' works and shows 'Done', which means that it has unlocked the bootloader. If you repeat the command, it shows 'user already unlocked', which is a proof that the Fastboot command is working.
However, the problem is that flashing a custom Recovery shows a 'remote' error, which means that it is the bootloader, which is preventing the flashing of the custom recovery.
The problem is that on Android 5.1.1, the bootloader is appearing as locked even though the fastboot procedure shows that the bootloader was unlocked.
I have tried different fastboot binaries and also tried different procedures (including BAT files) but not able to beat this problem.
Sent from my HUAWEI MT7-TL10 using Tapatalk
Click to expand...
Click to collapse
Edit: The link that you posted is not dead - it didn't open on my smartphone. The author of that post ACBKA helped me and we both tried it but could not beat the bootloader. While it shows that it is unlocked, it is still restrictive and doesn't allow flashing of custom recovery.
awzx_77 said:
i also face the same problem any one can help us ?
Click to expand...
Click to collapse
I have an idea!
I remember that when I was troubleshooting the problem (my smartphone was soft-bricked when I tried to rollback to KitKat and I ended up flashing Chinese 'Jazz' version on my TL10), I had realized that the bootloader was FULLY UNLOCKED on the chinese Jazz ROM and I could actually install a custom recovery. So, here is the idea:
a) First roll back to KitKat 4.4.2 --> I believe that there is a procedure on XDA to roll-back to KitKat
b) Change the phone's location to China
c) Install custom recovery and root phone by flashing superuser
d) Upgrade to Lollipop 5.1.1 (Chinese version)
e) Upgrade to Marshmallow beta (Chinese version)
f) Install custom recovery and root phone
same problem
just unlock the bootloader again using unlock code!
it worked for me
+1 for @xAghilx. Same here.