Related
Im trying to unlock my galaxy nexus's bootloader. my phone is in bootloader mode. i cant get my device to be seen, getting the waiting for device command.
i have installed like every driver possible. The whole android sdk with google usb. plus samsung usb drivers.
please help me i dont know what to do next
thanks
This is the best that I have found...... Have you checked in Devices to make sure you do have the ADB drivers or its it still showing the yellow triangle?
http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/
thanks! i managed to get it working. i am now rooted. One more issue... i dont seem to have service anymore???
i havent installed any roms or anything
thanks
I would try a reboot... remove sim... settings and search for networks. Other than that just flash a new rom.. Mine worked fine after root....but I guess it depends on the network.
bootloader
Danny80y said:
I would try a reboot... remove sim... settings and search for networks. Other than that just flash a new rom.. Mine worked fine after root....but I guess it depends on the network.
Click to expand...
Click to collapse
I could really use someone's help i have tried for two days to unlock my bootloader
soicyboy said:
I could really use someone's help i have tried for two days to unlock my bootloader
Click to expand...
Click to collapse
It would really help if you gave some details:
OS
what have you tried
what happened.
If you're on windows Vista or later and can't get the device recognised - that's a common problem, install pdanet, that will pull all the drivers in, and try again.
Otherwise, more details.
File to sd
i have unlock my bootloader and rooted my phone
how do i add a zip file to my sd
card
So, after trying for a month to unlock my bootloader with every single method I can find online, I've come to this:
-There are two methods described on XDA, and those are the official Sony way and the FlashTool way
-Both methods give me an error (see attachment)
-I've heard of a 'testpoint' method, but I can only find a tutorial for 2011 phones (also, there are no visible testpoints on the phone without taking it apart)
-Nobody has helped me yet, as every thread I post in dies as soon as I ask my question...
So, if anyone can help me with my bootloader unlocking, that'd be great... (preferrably with FlashTool or the official way)
I have the drivers installed, and I've tried on 3 different PCs, so I know it's not a USB port going bananas...
Thanks
(and sorry if I missed the correct forum)
and you have tried the sony webpage to unlock the bootloader?
If it's unlockable there shouldn't be any problems using that site.. Or do you get a error there too??
Nope, nothing works...
I don't really know what to do now, since I really am used of ROM flashing back from my Desire days...
The last ROM I tried was MIUI for locked bootloaders, but I got a brick out of that... XD
someone755 said:
Nope, nothing works...
I don't really know what to do now, since I really am used of ROM flashing back from my Desire days...
The last ROM I tried was MIUI for locked bootloaders, but I got a brick out of that... XD
Click to expand...
Click to collapse
Go to the sony official bootloader page and ask for a new one. Just do all the steps again and it will work, it's probably because you used the key and it failed the first time. That's how it worked for me
Nope, that ain't the problem... At least probably not, because I got the same key 3 times from Sony...
I'll check again and report back if it succeeds
Thanks for your help
Well I got a new code (entered another email address and another name, though the IMEI is still the same... (wtf's up with that, anyways?))...
I'm as chilled as a kid on a christmas morning DDD
Gonna try it out
EDIT: I THINK it worked... The CMD window says 'okay' but I'm not sure...
EDIT2: Yay! IT worked!! Thanks a million times DD
Hi All,
First I would like to say that I really like this community, everyone helps one another! Now on to my concern.....
I have the Sony Xperia S and now I would like to flash custom roms onto it. I have done this before with my previous phone which was an HTC Wildfire S, so I know a bit about unlocking/s-off. I know that we need to unlock the bootloader to do so and I have read the guides on this forum. (specifically DooMLoRD's guide) I followed it to the letter and I still have not succeeded.
I believe the problem lies in my IMEI code which when I go to the sony unlockbootloader website gives you the unlock code for your phone. I have been trying to unlock this phone for 2 days now!
Sony's website says that we need to input the first 14 numbers of the IMEI code in order to receive the unlock key. Well my code is 16 numbers long. I have tried entering different numbers in order to get different codes (i know this doesnt help much since the codes are specific to the phone but I am desperate now ) and all of them still give me the same error
(bootloader) Unlock phone requested
FAILED (remote: oem unlock failed!)
finished. total time: 0.020s
I have read that this is mainly due to an incorrect key. I have read around the forums and no one seems to give a definitive answer other than "try entering your IMEI again and get another code". Well that wont work with me since the code given to me is always the same.
Can anyone help resolve this?
P.S.
I have all the drivers, software, etc. Even the one click programs such as SE Bootloader_Unlocking_Relocking_1.6. All give the same oem error. I also rooted my phone successfully using Eroot1014, found it on a different website and was scared at first since it was in chinese or korean but it worked anyway.
Tread3r said:
Hi All,
First I would like to say that I really like this community, everyone helps one another! Now on to my concern.....
I have the Sony Xperia S and now I would like to flash custom roms onto it. I have done this before with my previous phone which was an HTC Wildfire S, so I know a bit about unlocking/s-off. I know that we need to unlock the bootloader to do so and I have read the guides on this forum. (specifically DooMLoRD's guide) I followed it to the letter and I still have not succeeded.
I believe the problem lies in my IMEI code which when I go to the sony unlockbootloader website gives you the unlock code for your phone. For purposes of convenience and time (I have been trying to unlock this phone for 2 days now!) I will post my IMEI code here ( 3529000059203526 ) and the unlock code given to me by sony through email (61CAA387DC11C4CF).
I hope this doesnt break any rules or anything.
I am doing this to see if anyone here can help me. Sony's website says that we need to input the first 14 numbers of the IMEI code in order to receive the unlock key. Well as you can see my code is 16 numbers long, so in effect I only entered up to number "5". I would like to know if anyone is willing to test my IMEI and see if they get the same code. I have tried entering different numbers in order to get different codes (i know this doesnt help much since the codes are specific to the phone but I am desperate now ) and all of them still give me the same error
(bootloader) Unlock phone requested
FAILED (remote: oem unlock failed!)
finished. total time: 0.020s
I have read that this is mainly due to an incorrect key, this is why I am posting. I have read around the forums and no one seems to give a definitive answer other than "try entering your IMEI again and get another code". Well that wont work with me since the code given to me is always the same (as above).
Can anyone help resolve this?
P.S.
I have all the drivers, software, etc. Even the one click programs such as SE Bootloader_Unlocking_Relocking_1.6. All give the same oem error. I also rooted my phone successfully using Eroot1014, found it on a different website and was scared at first since it was in chinese or korean but it worked anyway.
Click to expand...
Click to collapse
One line of advice "PLEASE DO NOT POST YOUR IMEIs" anywhere on the web!!! It is very risky and all xda members will agree with me.
The unlock code which sony gave you isn't the one which will help you unlock your phone. The unlock codes are only numbers and there are 4 level codes like SPCK, NCK. NSCK, CCK. Please check your PM for more details.
abhishek1234321 said:
One line of advice "PLEASE DO NOT POST YOUR IMEIs" anywhere on the web!!! It is very risky and all xda members will agree with me.
The unlock code which sony gave you isn't the one which will help you unlock your phone. The unlock codes are only numbers and there are 4 level codes like SPCK, NCK. NSCK, CCK. Please check your PM for more details.
Click to expand...
Click to collapse
Thanks for the advice, I will edit it ASAP.
abhishek1234321 said:
One line of advice "PLEASE DO NOT POST YOUR IMEIs" anywhere on the web!!! It is very risky and all xda members will agree with me.
The unlock code which sony gave you isn't the one which will help you unlock your phone. The unlock codes are only numbers and there are 4 level codes like SPCK, NCK. NSCK, CCK. Please check your PM for more details.
Click to expand...
Click to collapse
Hey he removed the imei number from his original message but that's pointless unless u remove it from your quote
Sent from my Xperia S using xda app-developers app
I've got nearly the same problem, expect that my bootloader was unlocked for a small time.
Did you already get the problem solved? Because you wrote something with PN...
My other Thread: http://forum.xda-developers.com/showthread.php?t=2198967
Chriszo said:
I've got nearly the same problem, expect that my bootloader was unlocked for a small time.
Did you already get the problem solved? Because you wrote something with PN...
My other Thread: http://forum.xda-developers.com/showthread.php?t=2198967
Click to expand...
Click to collapse
Glad to hear im not alone . No I still haven't found a way to unlock it. Sorry for asking but what does "PN" mean? Just so we are clear.
Ok thanks for your answer. No problem, but its just a mistake. Correctly it should be "PM" for personal message. I thought you would write on this way so I cant read any reasults
UPDATE:
I have tried other processes that all have the same steps, be it they were simplified programs with GUI's. I have come to the conclusion that my fastboot driver was installed incorrectly, because the first time I installed it on my phone I was able to see the S1 bootloader icon on device manager and I was able to click on it fast enough to enable it to install the driver. And correct me if im wrong but when we press UP on the volume rocker on our XS's and connect it to the USB we should see a blue right light? Well that is what happens when I do it so I assume I installed it correctly then.
Now after these first few failed attempts at unlocking I got frustrated and just factory reset my phone, completely ( I made back ups of course). This time however I used a program which is suppose to install all the drivers and simplify the whole unlocking process, I dont remember what program exactly, i'll check my files and get back to you guys on that.
Again it failed, showing the FAILED ("oem" error message) so I checked the steps from Doomlords guide and re checked my device manager. This time when I connect my phone it doesnt show the S1 bootloader icon on Dev manager, instead it shows "android phone ADB Interface". BUT I still get the blue LED when I connect my phone via USB, so does that mean I have fastboot on my phone again? ( I assume I do because the program I used says it did install it correctly and it even showed the "install anyway" window)
I am almost loosing all hope to unlock my XS , maybe I got a lemon phone or did something wrong again. I am willing to do another factory reset and restart the whole process again. This time I will follow every single step on the official website and see what happens.
But before I do that I want to ask, does anyone know of any news or whereabouts for an unofficial unlock bootloader process? I know its a long shot because we already have an official way but as from recent experience it doesnt work 100% of the time.
Really nice discription from you, thanks a lot for that
I think your precess that to tried to unlock was nearly the same as mine, but I didn't recognize any other info in the device manager. It's just this "ADB device installed" or something, but I dont know whether it was the same before the whole problem. I didnt really checked it because my first time unlocking the device was secceeded
Maybe thats one of our problems but how should it work correctly? The summary of the sdk driver program was "installation succeeded"...
Is it possible, that the kernel of the last andoid version (AOKP) i flashed is still "in" my device and just cant answer because the bootloader is closed??? Just an idea :/
Chriszo said:
Really nice discription from you, thanks a lot for that
I think your precess that to tried to unlock was nearly the same as mine, but I didn't recognize any other info in the device manager. It's just this "ADB device installed" or something, but I dont know whether it was the same before the whole problem. I didnt really checked it because my first time unlocking the device was secceeded
Maybe thats one of our problems but how should it work correctly? The summary of the sdk driver program was "installation succeeded"...
Is it possible, that the kernel of the last andoid version (AOKP) i flashed is still "in" my device and just cant answer because the bootloader is closed??? Just an idea :/
Click to expand...
Click to collapse
Thanks for the input. Glad to hear your unlocking succeeded, as to the idea that the AOKP or is it AOSP? Well whatever the acronym is, if the kernel of my phone is a reason for my errors, then I would look into that further, because what I did in my first go was simply follow the guide of Doomlord and when that failed I looked elsewhere.
That was when I tried rooting my phone even with a locked bootloader and it worked. I had to update my kernel to .55 from .45 and used a program that did the rest. That COULD be a cause but if its just a kernel it shouldn't disable my bootloader unlocking process since its just a part of the ROM right? That's my understanding of it. Correct me if im wrong.
Tread3r said:
Thanks for the input. Glad to hear your unlocking succeeded, as to the idea that the AOKP or is it AOSP? Well whatever the acronym is, if the kernel of my phone is a reason for my errors, then I would look into that further, because what I did in my first go was simply follow the guide of Doomlord and when that failed I looked elsewhere.
That was when I tried rooting my phone even with a locked bootloader and it worked. I had to update my kernel to .55 from .45 and used a program that did the rest. That COULD be a cause but if its just a kernel it shouldn't disable my bootloader unlocking process since its just a part of the ROM right? That's my understanding of it. Correct me if im wrong.
Click to expand...
Click to collapse
First off, if you're using Windows 7, chances are that your drivers are at fault. If you have the latest Flashtool, you can use those drivers (C:\Flashtool\drivers or C:\Program Files\Flashtool\drivers). If the drivers are correct, then when you boot into fastboot mode, the blue LED is supposed to stay on with a black screen until you unplug and restart your phone (or whatever the guide says).
It was AOKP, the advanced project for this device.
I think your right, but in how far is the bootloader linked to the needed kernel? And why cant the bootloader be unlocked several times...?
Of course the kernel is a main part of the rom, but without an unlocked bootloader even the kernel would not be accepted by the bootloader. Thats the problem with other firmwares/ roms why you have to unlock it
I remember that there was another way to root the stock rom with a little windows batch file that works like a little restore file for the phone.
You can find the link in this forum or here... http://forum.xda-developers.com/showthread.php?t=1886460
For this tool you just need one of the supported firmwares, then you start it and choose your option for the device like 1 for "normal".
The phone will ask you to restore the data that appears on the touchscreen. If it works the batch file will show you the result, otherwise the programm will run "forever". And of course it doesnt work with my device, but what is such wrong the original stock? Does it also has to do with the bootloader??? Or do I just have the wrong firmware (6.1.A.2.55) ?
razormc said:
First off, if you're using Windows 7, chances are that your drivers are at fault. If you have the latest Flashtool, you can use those drivers (C:\Flashtool\drivers or C:\Program Files\Flashtool\drivers). If the drivers are correct, then when you boot into fastboot mode, the blue LED is supposed to stay on with a black screen until you unplug and restart your phone (or whatever the guide says).
Click to expand...
Click to collapse
I am using Windows 7 and I have used flashtool. I believe the drivers are correct because,as you said, the blue LED does show and stay while I fastboot my phone. Same goes for the green LED when I go to flashboot.
Chriszo said:
I remember that there was another way to root the stock rom with a little windows batch file that works like a little restore file for the phone.
You can find the link in this forum or here... http://forum.xda-developers.com/showthread.php?t=1886460
For this tool you just need one of the supported firmwares, then you start it and choose your option for the device like 1 for "normal".
The phone will ask you to restore the data that appears on the touchscreen. If it works the batch file will show you the result, otherwise the programm will run "forever". And of course it doesnt work with my device, but what is such wrong the original stock? Does it also has to do with the bootloader??? Or do I just have the wrong firmware (6.1.A.2.55) ?
Click to expand...
Click to collapse
I have rooted my phone. But since I factory reset it, I unrooted it to start fresh. Everything on my phone is stock again because I want to eliminate any variables that would otherwise mess up the bootloader unlocking process. which I still have yet to achieve
Tread3r said:
I have rooted my phone. But since I factory reset it, I unrooted it to start fresh. Everything on my phone is stock again because I want to eliminate any variables that would otherwise mess up the bootloader unlocking process. which I still have yet to achieve
Click to expand...
Click to collapse
First, unlock your bl. Then root. I done that on my old Arc S and it works great.
Sent from my LT26i using xda developers-app
@ Tread3r:
Yes the drivers are installed correctly, because the phone starts into fastboot and flashboot with each the right light.
Thats the great problem with our devices. I did it nearly the same way and Ive got a similar problem, as the first answers describe in this post. Actual the original stock rom is installed on my Sony and all works correctly, but its just a short-term workaround
The bootloader unlockind process still end in an error message and that is my problem.
@ Vatih:
Nice try, but this is our problem... :/
---------- Post added at 11:41 AM ---------- Previous post was at 10:57 AM ----------
I cant believe it myself, but the alternative way works, althought I cant read anythink in the tool because of the language...
I've got the superuser app and root permissions and all works.
This link helped me: http://forum.xda-developers.com/showthread.php?p=39498268
It's the tool for the "new" firmware, .55, the latest from sony.
Hope, its also succesfully with your devices
I solved our problem. My bootloader is now open
I did it with the unlock, flashtool tool of this forum that helps you to open the bootloader and flash kernels and roms.
http://forum.xda-developers.com/showthread.php?t=2087337
Seems like just the code was wrong.
It worked with the first try
But be careful, although its just the bootloader, all data will be deleted. My phone is empty again :/ Of course I've got some backups...
Hello,
I`m in need for LG G3 D885 Kitkat Germany Vodafone firmware, the one hosted here (Germany Vodafone D85521A_00.kdz & Vodafone Germany D85510A_00.kdz) cannot be rooted and the other one doesn't work , the one that works seems to be patched by LG and I haven't been successful in rooting it. I have tried the one click method by avicohh thread both the GUI and the script, and the method by digital-bug thread . No other firmware works for me.. with everything else I end up with a bootloop. Unfortunately it seems that LG has stopped hosting firmware files on http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=355673068637086 and to my efforts and me following this guide I haven't been successful in downloading anything. If you happen to have the firmware I need I would be very grateful if you would share it.
Thanks in advance, and I look forward to hearing from you!
Edit: Look at my reply to the post for further info, I need firmware for the LG D85521A, and it needs to be Kitkat, unfortunately.
English is not my native language, so I apologize for any mistakes in my text .
I really really love this glorious phone (sarcasm)
So I found a firmware that I can root, thanks to hyelton. Turns out the Polish firmware hosted on his website can be flashed on my device and can be rooted. I was thrilled... but not for long.. :crying: I immediately tried to flash TWRP so I can finally flash CyanogenMod (my ultimate goal). So I downloaded Rashr - from the play store to flash the recovery, and apparently It did so successfully, so i clicked the button to go to recovery to finally flash CyanogenMod, and i got the Secure Boot error so I turned to Google for help, and help he did. I found this thread, and the end solution turned out to be to follow this thread . And here I am where I started . The solution is to flash Android Kitkat. I need the firmware for the LG D85521A model - this one only successfully flashes - so far.
So to anyone who knows where I can find the firmware that I am looking for I kindly ask of you to share it with me, and help me and others who are possibly going to face this problem in the future.
Thanks in advance, have a pleasant day
I tried unsuccessfully to install TWRP on a Xiaomi Redmi Note 8 Pro.
These are the steps I took:
Unlock the bootloader with MiUnlock.
Downloaded Fastboot.
Copied this CFW TWRP inside the Fastboot folder.
Downloaded these two files and copied inside the Fastboot folder.
fastboot flash preloader preloader_begonia.bin
fastboot flash lk lk.img
fastboot flash recovery twrp-3.3.1-0-begonia_UNOFFICIAL.img
fastboot reboot
And the result is that it no longer turns on. It also fails neither to enter the Fastboot screen, nor in that of recovery.
Windows no longer sees the device, so I can't interact in any way even with the folders inside the phone memory. Finally it is not even seen by Xiaomi Flash Tool (wanting to try to reinstall the official ROM).
The phone, immediately after unlocking it with the Xiaomi tool, had MIUI 12. I don't know which Android mounted (my fault), but I proceeded the same, without doing a downgrade, since in a discussion here on the forum it seemed that it could work same, even without downgrading to Android 9.
Is there any way to fix?
Maybe using Linux, you might be able to interact with the phone memory even if it is turned off / bricked?
Solution
Without hoping in the least, I solved it by following this video step-by-step.
I thank the author of this video a million times.
For anyone who was reading and needed it, there is no need to open the phone, remove the battery, connect various wires... You can do everything from software with a couple of clicks, even if the phone does not seem to want to connect absolutely to the PC.
Follow the linked video, it's very simple and you will save a lot of money!
Only if you have flashed it with a CFW
Angry Unlocker said:
Without hoping in the least, I solved it by following this video step-by-step.
I thank the author of this video a million times.
For anyone who was reading and needed it, there is no need to open the phone, remove the battery, connect various wires... You can do everything from software with a couple of clicks, even if the phone does not seem to want to connect absolutely to the PC.
Follow the linked video, it's very simple and you will save a lot of money!
Click to expand...
Click to collapse
Good for CFW, but if you are on a official MIUI and you've hardbricked it then you have to through an authorised Xiaomi account, in other words, it is a "payable flash" that you have to perform.
I had the same problem
Months ago I tried to install a stock ROM prior to the latest version installed, I got a brick exactly like the one you have, I didn't know who to go with until days ago, in a group on Telegram.
There is a group where a boy from Spain helped me with his authorized account for € 30, if you want to contact him I will leave you the link of the group.
https: //t.me /edlauth
(I put spaces for it to allow me to post the answer)
Thanks for your answers!
kingsemperor said:
Good for CFW, but if you are on a official MIUI and you've hardbricked it then you have to through an authorised Xiaomi account, in other words, it is a "payable flash" that you have to perform.
Click to expand...
Click to collapse
I am not quite clear what you mean exactly, but I, before proceeding with trying to flash a custom ROM, I had connected my original Xiaomi account to the device in question and also had requested the unlocking of the bootloader through the appropriate Xiaomi software (and I finally waited the time indicated by them, before proceeding). So on my Note 8 Pro there was actually the original / official MIUI updated to the latest version and I didn't need to proceed with a payment of any kind following that tutorial.
chumpokemon said:
Months ago I tried to install a stock ROM prior to the latest version installed, I got a brick exactly like the one you have, I didn't know who to go with until days ago, in a group on Telegram.
There is a group where a boy from Spain helped me with his authorized account for € 30, if you want to contact him I will leave you the link of the group.
https: //t.me /edlauth
(I put spaces for it to allow me to post the answer)
Click to expand...
Click to collapse
Thanks for your suggestion, but I have already solved it by following precisely that video.
How could I unlock the bootloader with the device bricked?
I has been trying a to unlock bootloader with MiUnlock but doesn't work. Is there any other way to unlock the bootloader with the bricked device?
Perike said:
How could I unlock the bootloader with the device bricked?
I has been trying a to unlock bootloader with MiUnlock but doesn't work. Is there any other way to unlock the bootloader with the bricked device?
Click to expand...
Click to collapse
You need to unbrick your device, follow the video tutorial
https :// youtu.be /wm0UFvjSvVg
chumpokemon said:
You need to unbrick your device, follow the video tutorial
https :// youtu.be /wm0UFvjSvVg
Click to expand...
Click to collapse
Flashed successfully, but the result is a reboot and This Miui version cant be installed on this device...
Angry Unlocker said:
Solution
Without hoping in the least, I solved it by following this video step-by-step.
I thank the author of this video a million times.
For anyone who was reading and needed it, there is no need to open the phone, remove the battery, connect various wires... You can do everything from software with a couple of clicks, even if the phone does not seem to want to connect absolutely to the PC.
Follow the linked video, it's very simple and you will save a lot of money!
Click to expand...
Click to collapse
Why does it say "this video is private" ?