Database Develop

[OFFICAL] Work out how to enable fastboot for locked devices / Problem solved :D

So as you may already be aware phones like mine, (orange uk) have the fastboot locked down, and so we cant unlock the bootloader.
I for one believe it can be accessed but needs a little bit of time and research on getting it done.
This thread is aimed for brain-storming for ideas and collecting them for us to try out,
You can de-brand your phone by flashing the software from this thread
http://forum.xda-developers.com/showthread.php?t=1033193
thanks to scott4 for the first upload mirror on page 3
Any ideas on getting the bootloader up and going on locked devices please put them in here
UPDATES
We now have root access thanks to Chainfire's gingerbreak apk which is here
http://forum.xda-developers.com/showthread.php?t=1044765
If your getting "could not extract assets" from gingerbreak
try doing
xperiax10.awesome said:
cool, finally I rooted my xperia ARC
these are very simple steps(copied from different threads):
1. Install the attached apk: Gingerbreak-v1.00
after installing most people getting this error - "could not extract assets".
TO OVERCOME THIS, just copy the attached ADB.zip and extract it on your laptop (windows)
say at
E:\mobile_Xperia\ADB
goto above path in your cmd promt and types these lines (your phone should be connected to laptop in debugging mode)
E:\mobile_Xperia\ADB>adb shell rmdir /data/local/tmp
E:\mobile_Xperia\ADB>adb shell mkdir /data/local/tmp
NOW JUST INSTALL THE apk file again and click on ROOT
Click to expand...
Click to collapse
if that Fails try replacing it with rm -r /data/local/tmp
Update 2
Blagus has kindly opened up this thread here
http://forum.xda-developers.com/showthread.php?t=1063394
We need people with a SIM-FREE phone with a LOCKED bootloader to help us all out, so if thats YOU !!!
Help us poor sods with branded handsets please.
UPDATE 3
Blagus Has come out with his release (As the man who can)
Blagus said:
Omnius for SE v0.23 (30th August 2011)
Added unlocking of S1 MSM7x30 GSM/UMTS phones (testpoint connection to GND is required.)
Added bootloader unlocking for S1 MSM7x30 phones
Anyone who donated (+punk... sorry forgot username, the OP ), contact me for free unlock.
For rest, contact for price (cheaper than at official Omnius resellers).
Click to expand...
Click to collapse
You can contact him here http://forum.xda-developers.com/member.php?u=2645841
Instructions
TESTPOINT INSTRUCTIONS PROVIDED BY mooxie FROM XDA FORUM:
1 turn of the phone
2 take of the backcover
3 remove the battery and sim card
4 take of the plastic covering the test point it's a bit stuck there but the gentle if you can.
5 Find something flexible like a wire or so i used steel wire. Make bend it so you easily can put it on the test point and the ground since you need to hold it there and press the powerbutton in the next step.
6 put in the battery
7 put the wire on the test point and the ground keep it there and press the power button for a few seconds. You wont get any confirmation that it suceeded.
8 Plug in the usb cable in the phone. Windows will now search for a new driver.
If it doesn't install automaticly. Go into the device manager of windows and look up something called SEMC_HUBB think it was that name. Choose update driver and browse to your omnius\driver folder. You will get a warning that the driver isn't signed but press okay and it should install.
9 Now if everything is done right the flashing will start and you should soon have an unlocked phone
Also side note i had problems with
qhsusb_dload driver not installing correctly.
if this is your case right click update and point to the omnius folder and choose update. worked for me.

Have you tried connecting via ADB, and running the command "adb reboot fastboot"?

dh2311 said:
Have you tried connecting via ADB, and running the command "adb reboot fastboot"?
Click to expand...
Click to collapse
What does this command does beside going to the fastboot?

Rithina said:
What does this command does beside going to the fastboot?
Click to expand...
Click to collapse
Well if we can get into fastboot we can unlock the kernal, for the people stuck with not being able to do the normal way

dh2311 said:
Have you tried connecting via ADB, and running the command "adb reboot fastboot"?
Click to expand...
Click to collapse
Reboots back up as normal, also did adb devices and it was there,

Have you tried removing the simlock?

MarylandCookie said:
Have you tried removing the simlock?
Click to expand...
Click to collapse
No not sure how to do it for free, i think someone with a Japaneses version has removed it, i will PM him to ask him

Here's a thought: backup TA. Write random values to security area. If fastboot is disabled/enabled depending on TA simlock info, tampered sec. zone could give you fastboot. Then unlock bootloader and in order to get your phone back to life, restore TA.
Method should be 100% safe as long as you can write TA back.
Sent from my X8 using XDA App

Tampered units wont let the phone boot.

lollylost100 said:
Tampered units wont let the phone boot.
Click to expand...
Click to collapse
But what about flash mode and fastboot? I know they won't boot but that's why in the end TA is restored.

so now all you crazy kids with unlocked phones have root I dont suppose anyone has any more ideas about this problem do they?

I have a few more ieas;
1) I presume you have also tried
adb reboot bootloader
I haven't got my arc yet, Im just saying old ways of getting DHD into bootloader/fastboot
2)
Also, what i think was being mentioned above, Im not too sure what was being said, but on advent vega's and optimus 2x's if you wiped the boot partition, it rebooted into fastboot, because there was no OS installed.
3)
Another one to try is look for market apps that offer reboot into recovery type options and see if they work

have you tried booting your device using the S1 BOOTLOADER method and the S1 DOWNLOAD method? (power off, hold menu + plug battery, then plug cable in pc) you should see a blue LED light. (power off, hold back key + plug battery, then plug cable in pc) you should see a green LED light.
try these two methods and give us a feedback

kazuni said:
have you tried booting your device using the S1 BOOTLOADER method and the S1 DOWNLOAD method? (power off, hold menu + plug battery, then plug cable in pc) you should see a blue LED light. (power off, hold back key + plug battery, then plug cable in pc) you should see a green LED light.
try these two methods and give us a feedback
Click to expand...
Click to collapse
manage to get Green light to come up, and it installs drivers
SEMC Flash Devices installs as the drivers,
After the installation of the new drivers still no blue light
adb reboot bootloader just reboots as normal

Hi !
For me, first method makes my phone booting normaly (no led light).
With the second one, it's OK : green led light appears.
If i can help...
PS : my PC doesn't want to install drivers :-(

punkmonkey1984 said:
manage to get Green light to come up, and it installs drivers
SEMC Flash Devices installs as the drivers,
After the installation of the new drivers still no blue light
Click to expand...
Click to collapse
so that means SEMC Flash is available. Try using Flashtool and flash a UK/Global firmware, and see if it works =)

Skyseb said:
Hi !
For me, first method makes my phone booting normaly (no led light).
With the second one, it's OK : green led light appears.
If i can help...
PS : my PC doesn't want to install drivers :-(
Click to expand...
Click to collapse
Download SEUS. PC Companion doesn't install the right drivers.

kazuni said:
so that means SEMC Flash is available. Try using Flashtool and flash a UK/Global firmware, and see if it works =)
Click to expand...
Click to collapse
Already flashed global firmware,
Still locked,

I guess the lock is actually in the bootloader level, which can't be overridden by writing a ftf package.
Sorry, but no other ideas at the moment =\

??? Have you seen this post ? => http://forum.xda-developers.com/showpost.php?p=13064854&postcount=420
Edit : ok, forget it...
Sorry.

[Q] My Galaxy S not booting after updating via kies

Today I updated my phone using kies. After the update was done the phone tried to boot but it couldn't get past the screen that says "Galaxy S GT-I9000".
So far I have tried to enter recovery/download modes, with no success.
Tried to connect the phone on my computer*, which recognized it (you could hear the "bleep" sound windows makes when a device is connected through usb.) but it didn't appear at Computer menu. Also kies recognized that there was phone connected but it keeps saying "Connecting" under Connected Devices tab.
*I'm using 64bit Windows 7 Ultimate

You'll need to either build or buy a Jig to get it into download mode and then you can reflash with Odin.

Did you ever use a custom rom on the phone? I assume not, but want to make sure.
If not, then you at least have warranty (don't you?) and can send it back for Samsung to revive your phone. Should you consider this, it would probably be wisest to not even try to repair your phone yourself.
However if you want to, here are three tips I found:
1) Connect your phone to your computer, open adb and type 'adb reboot download'. Your phone should reboot into download mode.
2) Originally posted here with a link to the mentioned ZIP: http://forum.xda-developers.com/showthread.php?t=728754 (look under "Manual Method")
For people that don't have the 3 button combo i made a script and a quick tutorial for doing it with ADB
ADB reboot recovery:
a) Download the easy reboot recovery.zip script and unzip it somewhere
b) In your phone's settings make sure USB Debugging is on (in settings -> applications -> development)
c) Connect phone with USB cable to pc
d) Wait until all the drivers are installed
e) Start reboot recovery.bat
f) The phone will now start in recovery
g) Follow step 7 of the normal tutorial
- If this does not work make sure USB debuging is enabled, kies is totally closed, the phone is connected and all the drivers are installed
3) This is from androidforums.com:
- Plug USB cable
- Remove battery
- Press AND HOLD volume down, power and menu key at the same time
- While pressing and holding the mentioned buttons, reinsert the battery (quite fiddly, I know)
- Let go of the buttons and you should go into Download mode.
Please tell me if anything helped.

Thanks for your help guys!
A.G. said:
1) Connect your phone to your computer, open adb and type 'adb reboot download'. Your phone should reboot into download mode.
Click to expand...
Click to collapse
Didn't work, adb gave me error "device not found", which would probably mean that the device isn't properly connected to my computer even though Windows did that bleep voice.
2) Originally posted here with a link to the mentioned ZIP: http://forum.xda-developers.com/showthread.php?t=728754 (look under "Manual Method")
For people that don't have the 3 button combo i made a script and a quick tutorial for doing it with ADB
ADB reboot recovery:
a) Download the easy reboot recovery.zip script and unzip it somewhere
b) In your phone's settings make sure USB Debugging is on (in settings -> applications -> development)
c) Connect phone with USB cable to pc
d) Wait until all the drivers are installed
e) Start reboot recovery.bat
f) The phone will now start in recovery
g) Follow step 7 of the normal tutorial
- If this does not work make sure USB debuging is enabled, kies is totally closed, the phone is connected and all the drivers are installed
Click to expand...
Click to collapse
This is something I didn't even try because I can't turn my phones USB debugging on. (can't access my settings )
3) This is from androidforums.com:
- Plug USB cable
- Remove battery
- Press AND HOLD volume down, power and menu key at the same time
- While pressing and holding the mentioned buttons, reinsert the battery (quite fiddly, I know)
- Let go of the buttons and you should go into Download mode.
Click to expand...
Click to collapse
Didn't work.
And no I have never used any custom ROMs on my phone. Probably taking my phone to the place I bought it from and see if I can get it fixed under warranty. Unfortunately that means I'm not going to have a phone to use for a while since I have no time to go there until sometime next week. If I can't get this thing fixed under warranty I'll probably just order a JIG and fix it that way.
If someone has more ideas please post them anyway, I want to fix this problem as fast as I can.

maybe a stupid question but you know how to get in dowload mode......
vol. down / home / power....
here are samsung drivers for your phone, uninstall everythin having to do with kies and install samsung drivers.
see if you can connect to ODIN now.
http://dl.dropbox.com/u/19506141/flash en drivers/SAMSUNG_USB_Driver_for_Mobile_Phones.exe

Need Help Unlocking Bootloader

I've been trying to get a ROM on my nexus 6, but as I go to unlock the bootloader, I enable usb debugging but get no prompt to authorize my computer's RSA Fingerprint. Any Ideas would be helpful. I've Tried all different combinations of connections (MTP+USB Debugging, etc.), and it still will not prompt me to authorize it. Thanks.

Have you tried Nexus Root Toolkit? I used that back in January to unlock and root my Nexus 6.
Sent from my Nexus 6 using Tapatalk

xt99ikd said:
I've been trying to get a ROM on my nexus 6, but as I go to unlock the bootloader, I enable usb debugging but get no prompt to authorize my computer's RSA Fingerprint. Any Ideas would be helpful. I've Tried all different combinations of connections (MTP+USB Debugging, etc.), and it still will not prompt me to authorize it. Thanks.
Click to expand...
Click to collapse
Reboot the device. Set switches for USB debug and bootloader unlock. Plug in phone. If don't work there a driver problem. If see your drive on PC don't worry about it. If it sees adb and/or fastboot don't worry about it. Don't use toolkit unless already know how to fastboot. If it screws up you are screwed cause don't know what happened.

xt99ikd said:
I've been trying to get a ROM on my nexus 6, but as I go to unlock the bootloader, I enable usb debugging but get no prompt to authorize my computer's RSA Fingerprint. Any Ideas would be helpful. I've Tried all different combinations of connections (MTP+USB Debugging, etc.), and it still will not prompt me to authorize it. Thanks.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2948481

For those who happen across this thread but cannot be bothered to read the link above, here is a little note. You do NOT need USB Debugging to unlock the bootloader. USB Debugging is an ANDROID setting, for use in Android. It has no effect on what happens to USB connections made in the bootloader or recovery.
EDIT> Actually that thread says you do need it. You do not.

danarama said:
For those who happen across this thread but cannot be bothered to read the link above, here is a little note. You do NOT need USB Debugging to unlock the bootloader. USB Debugging is an ANDROID setting, for use in Android. It has no effect on what happens to USB connections made in the bootloader or recovery.
EDIT> Actually that thread says you do need it. You do not.
Click to expand...
Click to collapse
For that thread no you do not need it if boot into the bootloader manually. For others that use the adb reboot bootloader command you will need it.

prdog1 said:
For that thread no you do not need it if boot into the bootloader manually. For others that use the adb reboot bootloader command you will need it.
Click to expand...
Click to collapse
That's not my point.

I have been struggling with drivers have uninstalled and reinstalled multiple times to no luck. For some reason keeps thinking its a Samsung
Any suggestions?
Sorry for Thread Hijack

ostap999 said:
I have been struggling with drivers have uninstalled and reinstalled multiple times to no luck. For some reason keeps thinking its a Samsung
Any suggestions?
Sorry for Thread Hijack
Click to expand...
Click to collapse
Try this:
http://forum.xda-developers.com/showthread.php?t=2588979

The NRT kit should be working! :good:

no luck...
cant figure out what i am not uninstalling...

ostap999 said:
no luck...
cant figure out what i am not uninstalling...
Click to expand...
Click to collapse
I know you said you already did, but uninstall every android driver you find on your PC. Then connect your nexus, while booted to android and let drivers install. Then disconnect, boot your nexus into bootloader, and reconnect again to install fastboot drivers.

Stuck at Fastboot while Rooting

Hi All,
I installed all the drivers for ADB (do I need some for Fastboot?). While rooting my fire does not want to wake up after going into fastboot mode. I can manually turn it off and on back again, but cannot finish rooting as the command shell is waiting for the device to boot and it never boots up.
Also, I cannot hear the device plug in sound in windows while my fire goes into fastboot mode (while I can clearly hear one when watching YT video regarding rooting instructions)... That may be a clue?
Thanks for any help. And Big thanks for all the developers!
Also, I tried to update the drivers one more time to see if they were the problem. And after uninstalling device and pluging it back in, Windows allows me to choose MTP USB device only... When I point the right path to .inf file it gives me an error of:
---------------------------
Select Device
---------------------------
The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems.
---------------------------
OK
---------------------------
Any ideas?

Ok, I managed to install the drivers by turning off the mtp connection in developer settings. But that did not help... Still getting stuck in fastboot mode.

rybaryba33 said:
Ok, I managed to install the drivers by turning off the mtp connection in developer settings. But that did not help... Still getting stuck in fastboot mode.
Click to expand...
Click to collapse
just root with Supersu.zip in twrp
[CUSTOM RECOVERY] TWRP Recovery
Sent from my KFFOWI using Tapatalk

I managed to root using root.bat
I somehow installed fastboot drives and I did it, when I pressed vol up and power button. I acted fast to install the drivers. Then I just followed instructions and gained full root.
Thanks again developers! I shall donate so you can have a few drinks on me

Stuck at loading screen when booting

I found out this morning that my phone had cut off during the night. When I tried to turn the phone back up it just stayed at the loading screen and does not go any further than that. I can get into Fastboot/recovery but not sure what is going on. Phone is locked as well.
I am running on Developer preview 5 and I assuming it has something to do with this. I have read up on others having issues and talk about sideloading the OTA that has resolved the issue but my computer does not even detect the device, so adb does not see the device. Feel like if I can just get my computer to detect my phone I'll be in business.
Really need some help on this one as it is starting to look like I am going to have a nice paper weight the rate its going. Thank you in advance.

cjsill9473 said:
I found out this morning that my phone had cut off during the night. When I tried to turn the phone back up it just stayed at the loading screen and does not go any further than that. I can get into Fastboot/recovery but not sure what is going on. Phone is locked as well.
I am running on Developer preview 5 and I assuming it has something to do with this. I have read up on others having issues and talk about sideloading the OTA that has resolved the issue but my computer does not even detect the device, so adb does not see the device. Feel like if I can just get my computer to detect my phone I'll be in business.
Really need some help on this one as it is starting to look like I am going to have a nice paper weight the rate its going. Thank you in advance.
Click to expand...
Click to collapse
If I understand correctly, you can get to fastboot mode. If you then plug in the usb cable, and type fastboot devices, does the computer recognize it?
Have you ever connected to the phone using your computer and either adb or fastboot? In other words, is there a high level of confidence that the drivers are setup on your computer?

That is correct, I am able to get into fastboot mode, the phone will detect a USB cable "will say transfer mode: USB connected" but when I am in command prompt on my computer and type in "adb devices" it finds nothing.
I've had experience with using adb/fastboot on my moto x 2014 but this is the first time doing this on my nexus and I am pretty sure I had never hooked up my nexus to this computer before this issue happened. So I wouldn't be surprised if it is a driver issue but I have downloaded Android sdk and gone into sdk manager to have it install google drivers. I just now now played around with Nexus Root toolkit to assist in installing drivers with the same results. I had used the tool to uninstall any drivers that could have impacted this and reinstalled with no luck.
ktmom said:
If I understand correctly, you can get to fastboot mode. If you then plug in the usb cable, and type fastboot devices, does the computer recognize it?
Have you ever connected to the phone using your computer and either adb or fastboot? In other words, is there a high level of confidence that the drivers are setup on your computer?
Click to expand...
Click to collapse

cjsill9473 said:
That is correct, I am able to get into fastboot mode, the phone will detect a USB cable "will say transfer mode: USB connected" but when I am in command prompt on my computer and type in "adb devices" it finds nothing.
I've had experience with using adb/fastboot on my moto x 2014 but this is the first time doing this on my nexus and I am pretty sure I had never hooked up my nexus to this computer before this issue happened. So I wouldn't be surprised if it is a driver issue but I have downloaded Android sdk and gone into sdk manager to have it install google drivers. I just now now played around with Nexus Root toolkit to assist in installing drivers with the same results. I had used the tool to uninstall any drivers that could have impacted this and reinstalled with no luck.
Click to expand...
Click to collapse
Do you have an otg cable? Does that work?

I do but I don't have one on me currently. I am currently at work but will be home in about 2 hours.
ktmom said:
Do you have an otg cable? Does that work?
Click to expand...
Click to collapse

cjsill9473 said:
That is correct, I am able to get into fastboot mode, the phone will detect a USB cable "will say transfer mode: USB connected" but when I am in command prompt on my computer and type in "adb devices" it finds nothing.
Click to expand...
Click to collapse
When you are in fastboot mode, and connect to your computer, you should run "fastboot devices", instead of "adb devices".

You are correct, device does show up when type in fastboot devices. Guess that is what I get when trying to do this while I am at work and haven't messed with this type of stuff in months. I really appreciate the fast response on this and my derp moment. Now to try and side load the OTA to see if I can bring my phone back to life. Looks like I just need to go into custom recovery and select "Apply Update from ADB" and hopefully I'll be in business.
jj14 said:
When you are in fastboot mode, and connect to your computer, you should run "fastboot devices", instead of "adb devices".
Click to expand...
Click to collapse

Well at this point I was able to side load the OTA DP5 build and its doing the same thing. Trying a factory reset now to see if that will make a difference but if not looks like I am going to have to go out and get me a new phone till I can get this one fixed or RMA'ed. Just stuck at the loading animation.
Edit: Factory restore finally brought it back to life. Thank you again for the quick help and assistance on this!