Friends All of us facing the problems in unloking bootloaders
I have an better solution for 50% error..
while unlocking bootloader please use and old pc with low coniguration and try in 5 to 10 days from request apporved.
main 50% stuck problem is due to drivers [ADB].
hence use old pc bcoz old pc manually and automatically download the drivers.
hence who get 50% stuck problem i request these peoples to use old pc. these is working for all and worked for me also.
thanks in advance
sharing is caring.
post your questions about these in comments....
Related
So I've been following the bootloader unlock instructions on the Sony-Ericsson site and when I have plugged the phone in and the instructions say it should ask me for drivers it just plays the driver install failed noise, so in device manager I have the S1Boot Fastboot listed but when I point the driver update wizard to the adb folder where the driver is it just says it cannot find it. Anyone had an issue like this or knows how to fix it or have I done something completely idiotic because it's 6am and I haven't slept for 2 days?
you need the google usb drivers (android sdk) good luck !
Yeah I got past this bit and have the phone unlocked now but during the proccess my camera, lockscreen and a couple of other bits have stopped working and I can't simply revert back to the original software as sony's tool won't allow that. Also can't find a clockworkmod recovery image for the device so have no clue how to put the cyanogenmod nightly that's out on.
Can't you use flashtool to flash a stock rom ?
Yup, all recovered now.
It would be much better if this most essential of sites for people mucking around with there android phones had a section for the Xperia Pro, there are already plenty of threads for the device but they are spread over every other Sony section and makes finding the thread that will help quite difficult.
So , I'm trying to unlock my Xperia Ray's boot loader however i come across a problem. Once the pc detects the phone in S1 Fast boot mode , it try's to automatically find the drivers from the windows database thing. This is where i encounter the problem , Sony's Guide says to point it to the android_winusb.inf it asked me to replace earlier , however i see absolutely no option to do so. Any help would be much appreciated
-
Boot loader is unlock-able
[HELP] Root, Optimizations, Overclock, Battery, and More Tutorials (updated for ICS
should help you eneugh, I got the job done anyhow
Hello there!
I've been trying to install a custom rom to my sk17i running 4.1.B.0.587, I'm also using Windows 8 64 bit.
I first follow this http://forum.xda-developers.com/showthread.php?p=31376248#post31376248 initially as it seems that it's a complete guide. But in that thread, I was unable to unlock the bootloader as the command is not letting me run the fastboot.exe -i 0x0fce getvar version / fastboot device etc.
So I end up trying this thread http://www.androidgadgematic.com/2012/11/how-to-unlock-any-sony-xperia-bootloader-easily.html
Which I able to run those commands ( fastboot.exe.... etc ) but when I run this command to unlock the bootloader ( fastboot.exe -i 0x0fce oem unlock.. ) I got an error " failed remote oem unlock " so I double checked the IMEI and got new bootloader key. Then I tried again, I got an error this time " too many links ". As per other thread, they advised to clear cache ( fastboot clear cache ) but it doesn't made any difference.
After too many trials, I decided to use this http://forum.xda-developers.com/showthread.php?t=1879982 (using flashtool and flashmode) I was able to get 14% when the LED light on my xperia gone. Then what I did was I reconnected the cable then proceeded with flashtool method.
At this point, when I rerun flashtool, it's stock at 2% with checking headlines. Goes about more than 10mins on that phase so I decided to reconnect it. Then my computer crashed, so I have to restart. When I turned my computer on, It loaded for 5 mins then I got a pop up message, "upgrading android" afterwards, other programs loaded but then at the end, I got another error saying " Unfortunately, startup programs stopped..." then it restarts itself continuously that I have to remove the battery to completely turn it off.
I assumed that my phone is now "bricked" that is why i follow this "6. Turning the "brick" into a smartphone" http://forum.xda-developers.com/showthread.php?p=27376017 but it didn't worked. same as the last time I used the flashtools.
Can I still revive my phone? I just want to downgrade it back to GB 2.3 or upgrade it to CM10 JB if possible.
I'm definitely stupid and noob in this field. Can someone help me out for this one? It'll be highly appreciated! Many thanks!
*Drivers are successfully installed.
*downloaded kernels.
*Windows 8 64 bit
I'm on the point of losing hope that I could still use it. =((((
Give this a read - http://www.androidgadgematic.com/2012/06/how-to-fix-bricked-sony-xperia-android.html
Many thanks! I'll give it a try. hope it works. =)):fingers-crossed:
**by the way, I can't see the xperia mini pro component when I try to install the flashtool driver. what component shall I choose?Please advise.Thanks!
Cant find any threads about this. So confusing.
nejakkin said:
Cant find any threads about this.
Click to expand...
Click to collapse
See the general section, everything has been covered before so finding it should be easy.
Hi, i'm starting this thread by excusing myself for this approximativly english, i'm not really an english man :angel:
I don't really like calling help on forum, but at 00:30, with studies tomorrow, i'm really bored.
So, today at 17:30, i have reboot my OPX, simply reboot, and i'm now on a bootloop... I read a looooooot of thing on internet and i deduce that : My bootloader has relocked himself.
Before this reboot, i was on OxygenOS 3.* with TWRPblu****** and an unlocked bootloader. I can't access to recovery, only to a bootloop or fastboot mode.
I've tried :
- Use fastboot commands to flash recoveries, but nothing happen because i can't unlock the bootloader
- Use the MSMdowloadtool like all guide said, but the problem is there i think. My device aren't recognize as a "Qualcomm ***********" is recognize as "Android" or "One plus bootloader device" (i haven't exact name here). I thinked Windows 10 have the faculty to identify android devices, so i've installed on dual boot windows 7, no more results. (Signed Drivers are disabled)
I have no idea, i need u :crying:
If anyone have ever see the same issue, give me ur solution please
I certainly will contact the OnePlusSupport too but i know it's not really a good idea.
I will go to sleep now, i need to go to school tomor... today.
Have a good night !
Nekkoelb said:
Hi, i'm starting this thread by excusing myself for this approximativly english, i'm not really an english man :angel:
I don't really like calling help on forum, but at 00:30, with studies tomorrow, i'm really bored.
So, today at 17:30, i have reboot my OPX, simply reboot, and i'm now on a bootloop... I read a looooooot of thing on internet and i deduce that : My bootloader has relocked himself.
Before this reboot, i was on OxygenOS 3.* with TWRPblu****** and an unlocked bootloader. I can't access to recovery, only to a bootloop or fastboot mode.
I've tried :
- Use fastboot commands to flash recoveries, but nothing happen because i can't unlock the bootloader
- Use the MSMdowloadtool like all guide said, but the problem is there i think. My device aren't recognize as a "Qualcomm ***********" is recognize as "Android" or "One plus bootloader device" (i haven't exact name here). I thinked Windows 10 have the faculty to identify android devices, so i've installed on dual boot windows 7, no more results. (Signed Drivers are disabled)
I have no idea, i need u :crying:
If anyone have ever see the same issue, give me ur solution please
I certainly will contact the OnePlusSupport too but i know it's not really a good idea.
I will go to sleep now, i need to go to school tomor... today.
Have a good night !
Click to expand...
Click to collapse
Fastboot commands : is the phone recognised?
"fastboot oem device-info" output?
Did you tried the Mega unbricked guide?
Which step precisely is a problem?
Kéno40 said:
Fastboot commands : is the phone recognised?
"fastboot oem device-info" output?
Did you tried the Mega unbricked guide?
Which step precisely is a problem?
Click to expand...
Click to collapse
Yes he used..read full op.
Nekkoelb said:
Hi, i'm starting this thread by excusing myself for this approximativly english, i'm not really an english man :angel:
I don't really like calling help on forum, but at 00:30, with studies tomorrow, i'm really bored.
So, today at 17:30, i have reboot my OPX, simply reboot, and i'm now on a bootloop... I read a looooooot of thing on internet and i deduce that : My bootloader has relocked himself.
Before this reboot, i was on OxygenOS 3.* with TWRPblu****** and an unlocked bootloader. I can't access to recovery, only to a bootloop or fastboot mode.
I've tried :
- Use fastboot commands to flash recoveries, but nothing happen because i can't unlock the bootloader
- Use the MSMdowloadtool like all guide said, but the problem is there i think. My device aren't recognize as a "Qualcomm ***********" is recognize as "Android" or "One plus bootloader device" (i haven't exact name here). I thinked Windows 10 have the faculty to identify android devices, so i've installed on dual boot windows 7, no more results. (Signed Drivers are disabled)
I have no idea, i need u :crying:
If anyone have ever see the same issue, give me ur solution please
I certainly will contact the OnePlusSupport too but i know it's not really a good idea.
I will go to sleep now, i need to go to school tomor... today.
Have a good night !
Click to expand...
Click to collapse
Power off your phone, connect to PC with power off holding volume up button. It should detect phone as Qualcomm.
Nekkoelb said:
Hi, i'm starting this thread by excusing myself for this approximativly english, i'm not really an english man :angel:
I don't really like calling help on forum, but at 00:30, with studies tomorrow, i'm really bored.
So, today at 17:30, i have reboot my OPX, simply reboot, and i'm now on a bootloop... I read a looooooot of thing on internet and i deduce that : My bootloader has relocked himself.
Before this reboot, i was on OxygenOS 3.* with TWRPblu****** and an unlocked bootloader. I can't access to recovery, only to a bootloop or fastboot mode.
I've tried :
- Use fastboot commands to flash recoveries, but nothing happen because i can't unlock the bootloader
- Use the MSMdowloadtool like all guide said, but the problem is there i think. My device aren't recognize as a "Qualcomm ***********" is recognize as "Android" or "One plus bootloader device" (i haven't exact name here). I thinked Windows 10 have the faculty to identify android devices, so i've installed on dual boot windows 7, no more results. (Signed Drivers are disabled)
I have no idea, i need u :crying:
If anyone have ever see the same issue, give me ur solution please
I certainly will contact the OnePlusSupport too but i know it's not really a good idea.
I will go to sleep now, i need to go to school tomor... today.
Have a good night !
Click to expand...
Click to collapse
You have noting to do but to flash stock oos 2.1.4 using Qualcomm flasher and driver.I faced the same issue.but I managed to flash using Qualcomm in windows 10.and got my onyx back.
My suggesting is remove the adv or oneplus drivers.just install the Qualcomm driver and connect the device.follow the device manager if the deivce detected or not.it will detect and flash using Qualcomm flasher.
hi everyone, I am not very techy . i am trying "unlocking bootloader'. Installed the apk in phone , got through in depth testing and now my phone is showing "fastbook_unlock_verify ok". But My pc is not detecting my phone, hence fastboot command box is not opening. i tried to command from windows powershell ,it's showing waiting for device. Can i go back from this stage to normal phone?, or any steps to go forward with boothloader unlocking are really appreciated. thanks in advance
Nithin palwai said:
hi everyone, I am not very techy . i am trying "unlocking bootloader'. Installed the apk in phone , got through in depth testing and now my phone is showing "fastbook_unlock_verify ok". But My pc is not detecting my phone, hence fastboot command box is not opening. i tried to command from windows powershell ,it's showing waiting for device. Can i go back from this stage to normal phone?, or any steps to go forward with boothloader unlocking are really appreciated. thanks in advance
Click to expand...
Click to collapse
i think u r probably using Windows 10 right?
many it happens that its not detect the device
try in win8 or 7 its works and aslo enable debugging from developer option
abhi.s4u said:
i think u r probably using Windows 10 right?
many it happens that its not detect the device
try in win8 or 7 its works and aslo enable debugging from developer option
Click to expand...
Click to collapse
What color os version do you have? I am also facing the same issue, I have color os 6 (android 9). And as suggested in the second post, I do have win 10, but I tried it in win 8 as well, and it was the same, so it's not related to windows, but related to color OS version.
try with another realme 1 data cable..
in some cases data cable also be the reason for this type of problem.
btw my device is also running on the same O.S version
but in my view unlocking bootloader of realme1 is useless and also very risky
why useless?
device has no stable and proper custom rom yet..
also after unlocking and rooting the device, u may face security isssue with some banks or payment apps.. they will not run..
why risky?
many members bricked thr device in the process
bcoz realme 1 runs on mediatek processor which is not consider good for rooting and all the stuffs..