Hello, this is a question for the seasoned Linux users.
I have a broken usb x10, with root, unlocked bootloader.
Can I flash Amins kernel via fastboot as following?
open debug on.
adbwireless connected with my pc
go to my adb via android sdk
en type a fastboot command to replace the FXP kernel that i currently have.
Is this possible?
I can't imagine how a broken usb can withhold so many x10 users from flashing a kernel.
No, its not possible, may be you should take a look here :
http://forum.xda-developers.com/showthread.php?p=35993592
Regards
Thanks bares for the link.
but is this not doable through ubuntu commands? I just need a push to right direction without opening x10
Sent from my Wildfire using xda premium
Related
Anyone know if it is posible to root a Samsung Infuse 4G on Mac OSX? I know how to root i just dont know if you can root this phone on this Mac OSX because it only shows that you can root with SuperOneClick (Windows Only). Thanks in advance!
Well since superoneclick can run on a mac, then you could try it. See post #6 here: http://forum.xda-developers.com/showthread.php?t=997475. Make sure you have mono installed: http://www.go-mono.com/mono-downloads/download.html.
Anyway to root it without SuperOneClick?
Like can i use the fastboot commands from the android sdk to unlock the bootloader? And then flash Clockwork Mod with
Code:
./fastboot-mac flash recovery (image here)
? Then of install superuser and the infused ROM. Would that work? Or is superoneclick my only option?
THIS THREAD WAS PUT IN THE WRONG PLACE AND MOVED HERE: http://forum.xda-developers.com/showthread.php?p=19758521#post19758521
Hello everyone, as we all know several people have/had problems unlocking the bootloader @dicxz80 might be on to something here.
Please share what Android Debug Bridge version you used to unlock (or tried to unlock) the bootloader with.
I used Android Debug Bridge version 1.0.31
If you don't know how to check, it's easy. Just go to your adb location (with cmd) and type
Code:
adb version
Hopefully this will give us some more information.
I noticed most of the adb(s) I got from L9 forums have "Android Debug Bridge version 1.0.29"
I'm not sure if the ADB version a made difference, but it's worth checking.
Oh and my P769 is unlocked
Specific adb builds do not allow for adb root.... type adb root and see what it says
Sent from my LG-P769 using xda app-developers app
omgbossis21 said:
Specific adb builds do not allow for adb root.... type adb root and see what it says
Sent from my LG-P769 using xda app-developers app
Click to expand...
Click to collapse
Right, and this has to do with . . .?
I'm just wondering if the adb version played a role in successfully unlocking the bootloader.
Thanks for the info though.
CM 10.1 P769
Just pointing out differences in various builds. It could be possible that the unlock command needs to be passed in adb shell with su acces on some versions. I don't think its likely though possible.
omgbossis21 said:
Just pointing out differences in various builds. It could be possible that the unlock command needs to be passed in adb shell with su acces on some versions. I don't think its likely though possible.
Click to expand...
Click to collapse
Thanks for the info and your efforts. I'm sure you will crack this bootloader thing :thumbup:
Morpheus was just about to crack in the matrix. But that dam Neo saved the day lmao.
CM 10.1 P769
I just noticed I have twrp w/o a unlocked boot loader. Will someone help me on what to do? I seen this guide which made no sense and adb I think can unlock my boot loader, but just in case, can you guys tell me what to do so I won't brick my tablet?
Sent from my KFTHWI using XDA Free mobile app
MinerBoy004 said:
I just noticed I have twrp w/o a unlocked boot loader. Will someone help me on what to do? I seen this guide which made no sense and adb I think can unlock my boot loader, but just in case, can you guys tell me what to do so I won't brick my tablet?
Click to expand...
Click to collapse
Installing TWRP from these forums leverages an exploit that bypasses signatures. Unlocking the bootloader opens advanced recovery capabilities and is (currently) recommended for some of the ROMs under development. However, there are risks to executing the unlock procedure that you need to weigh. A good understanding of each step and how to recover from mistakes is essential. Windows can present an additional challenge as fastboot drivers are notoriously fussy.
If you don't understand the unlock guides that have been posted I suggest you save this for another day. You won't be missing anything unless you just HAVE to be on one of the early CM12 builds.
Hello all. I have had adb working for a while, but fastboot is not recognizing my devices. I am doing fastboot -i 0x1949 devices and it turns up nothing. I have a thor. I am on windows 8.1 64 bit. Any ideas which driver I should install? When I go to device manager in fastboot, I see the Kindle with a caution triangle. Any help would be appreciated.
lekofraggle said:
Hello all. I have had adb working for a while, but fastboot is not recognizing my devices. I am doing fastboot -i 0x1949 devices and it turns up nothing. I have a thor. I am on windows 8.1 64 bit. Any ideas which driver I should install? When I go to device manager in fastboot, I see the Kindle with a caution triangle. Any help would be appreciated.
Click to expand...
Click to collapse
You can try these drivers (not sure if they will work in win 8.1 though).
I had did a wrong boot.img flash and now fastboot is gone. I just want to verify that fastboot was actually located somewhere inside the boot.img.
Side notes..... I have a phone now that doesnt power on cuz the preloader is cooked by flashing that boot.img. If you try to charge the phone ,the battery charging icon does not show so that means I hard bricked phone.
lextacy said:
I had did a wrong boot.img flash and now fastboot is gone. I just want to verify that fastboot was actually located somewhere inside the boot.img.
Side notes..... I have a phone now that doesnt power on cuz the preloader is cooked by flashing that boot.img. If you try to charge the phone ,the battery charging icon does not show so that means I hard bricked phone.
Click to expand...
Click to collapse
Fastboot doesn't actually reside on the phone it is a communication protocol used to flash the specific partitions of the phones layout. Specifically fastboot itself is just a binary (.bin on OS X and Linux and .exe on windows) used to communicate with the fastboot protocol. Correct me if I'm wrong but what I'm guessing what you did is you meant to flash a boot.img to the boot partition and instead you flashed that to the bootloader/preloader partition erasing the bootloader. There is a flag when the bootloader is complied that allows the bootloader to have support for fastboot. Your best bet is to to try and find a factory image for your phone to try and re-flash the stock bootloader through fastboot. A second option is find a friend who has the same phone model as you and that is rooted, then dump there bootloader using terminal emulator or a similar app, transfer it to your computer and then flash it using fastboot. If you have any more questions or just want some more clarification on what I said feel free to ask more then happy to help !
shimp208 said:
Fastboot doesn't actually reside on the phone it is a communication protocol used to flash the specific partitions of the phones layout. Specifically fastboot itself is just a binary (.bin on OS X and Linux and .exe on windows) used to communicate with the fastboot protocol. Correct me if I'm wrong but what I'm guessing what you did is you meant to flash a boot.img to the boot partition and instead you flashed that to the bootloader/preloader partition erasing the bootloader. There is a flag when the bootloader is complied that allows the bootloader to have support for fastboot. Your best bet is to to try and find a factory image for your phone to try and re-flash the stock bootloader through fastboot. A second option is find a friend who has the same phone model as you and that is rooted, then dump there bootloader using terminal emulator or a similar app, transfer it to your computer and then flash it using fastboot. If you have any more questions or just want some more clarification on what I said feel free to ask more then happy to help !
Click to expand...
Click to collapse
Good info here , I did not know that fastboot was outside the android environments. The command I ran was "fastboot flash boot boot.img" if that makes sence. This was on a chinese smartphone that has a chinese only text bootloader. So no other friends will have this phone where I can grab an image from. I ordered a new phone (surprise , surprise right? ) haha , BUT I would still like to get this brick working for learning purposes and root practice.
lextacy said:
Good info here , I did not know that fastboot was outside the android environments. The command I ran was "fastboot flash boot boot.img" if that makes sence. This was on a chinese smartphone that has a chinese only text bootloader. So no other friends will have this phone where I can grab an image from. I ordered a new phone (surprise , surprise right? ) haha , BUT I would still like to get this brick working for learning purposes and root practice.
Click to expand...
Click to collapse
Glad I could help you out ! It must be a bad boot image then that you flashed, but that shouldn't prevent you from accessing the bootloader. When you get your new phone and root it you should be able to pull that stock boot image and then get your old phone working again. As always any questions let me know !
So fastboot doesn't reside in the phone?
I understand that it's a protocol, but how does the phone know to act like a server for the PC fastboot client?
Where does the phone load the protocol rules from?
Can fastboot mode run even without any partition on the phone?
If so the phone would be virtually unbrickable.
I'm just trying to understand.
JackSlaterIV said:
So fastboot doesn't reside in the phone?
I understand that it's a protocol, but how does the phone know to act like a server for the PC fastboot client?
Where does the phone load the protocol rules from?
Can fastboot mode run even without any partition on the phone?
If so the phone would be virtually unbrickable.
I'm just trying to understand.
Click to expand...
Click to collapse
Perhaps the best way to understand how fastboot works is to take a look at it's source code found here https://android.googlesource.com/platform/system/core/+/master/fastboot/fastboot_protocol.txt and the general fastboot code here https://android.googlesource.com/platform/system/core/+/master/fastboot. Let me know if you still have questions.
shimp208 said:
Perhaps the best way to understand how fastboot works is to take a look at it's source code found here https://android.googlesource.com/platform/system/core/+/master/fastboot/fastboot_protocol.txt and the general fastboot code here https://android.googlesource.com/platform/system/core/+/master/fastboot. Let me know if you still have questions.
Click to expand...
Click to collapse
Thanks, I saw but there is no answer there.
THIS GUIDE IS FOR THE MOTO G6 PLUS ONLY
1: Preparing to Unlock Bootloader
Moto does a fine job of breaking down how to unlock the bootloader, but they do not give you much information on using the adb and fastboot programs that are part of the "Android Software Developer Kit(SDK) Platform Tools" which contain over 700+ files. For the procedures listed in this guide, we only need 2 files, adb and fastboot. XDA Moderator @hackslash has created a tool to simplify using adb and fastboot that doesn't include the other 700+ files you don't need.
1A. ADB and Fastboot Installer for Windows - (Download) - When prompted to install a driver type the number 0 and hit enter. This will install the latest version of adb and fastboot where it is system-wide. This eliminates the need for adb.exe or fastboot.exe to be in the same folder as the files you will be working with. NOTE: Windows will flag this as a virus! The installer is open source and made by a Moderator here on XDA. It is a False Positive. You can view a VirusTotal report (https://www.virustotal.com/en/file/25dc5dca2494d1b1d93832b37ba9852b4f076bba86cf5029b4c944a28a1a01a1/analysis/]HERE[/url]). 26 out of 67 virus scanners report it as a virus. If your Anti-Virus is one of the ones that flag it as a virus, I would suggest you explore other Anti-Virus software, but that’s not what this guide is about.
1B. As per the instructions on Moto’s site, you need to download and install the latest official drivers from Moto. (Download)
1C. Head over to the Moto website and follow the instructions to unlock your bootloader. (Moto Website)
After you are done on the Moto website your bootloader will be unlocked! This is necessary to be able to modify system files for root, roms, and other various tweaks!
Hi, the official drivers link not working for me.
https://motorola-global-en-roe.cust...prod_answer_detail/a_id/99344/p/30,6720,10383 <-- Installs the whole Motorola Device Manager along with the usb drivers, which can be also used to update firmware. I don't know if this is good or bad for rooted phones.
https://motorolausbdriver.com/download/motorola-moto-g6-plus <-- just the driver for windows
Thanks for this article and the work that has gone into it.
Just a quick editing note. The 1B line includes a typo in the href attribute, the value of which is:
http://https//motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Click to expand...
Click to collapse
Thanks.
Will the bootloader unlock trigger a factory reset?
Hobbygamer27 said:
Will the bootloader unlock trigger a factory reset?
Click to expand...
Click to collapse
Yes
Sent from my SM-A505U using Tapatalk
I can get into the bootloader on my phone, with `adb reboot bootloader` or pressing the power and volume down key. The problem is that once I'm in the bootloader in fastboot on my pc it doesn't recognise my phone, usb debugging + oem unlock is on in dev settings. I got in once, but after many tries I wasn't able to have a connection anymore. On my phone it says that the usb is connected, so that isn't the problem. I haven't tried it on a 2.0 usb slot yet.
Xplorer4x4 said:
THIS GUIDE IS FOR THE MOTO G6 PLUS ONLY
1: Preparing to Unlock Bootloader
Moto does a fine job of breaking down how to unlock the bootloader, but they do not give you much information on using the adb and fastboot programs that are part of the "Android Software Developer Kit(SDK) Platform Tools" which contain over 700+ files. For the procedures listed in this guide, we only need 2 files, adb and fastboot. XDA Moderator @hackslash has created a tool to simplify using adb and fastboot that doesn't include the other 700+ files you don't need.
1A. ADB and Fastboot Installer for Windows - (Download) - When prompted to install a driver type the number 0 and hit enter. This will install the latest version of adb and fastboot where it is system-wide. This eliminates the need for adb.exe or fastboot.exe to be in the same folder as the files you will be working with. NOTE: Windows will flag this as a virus! The installer is open source and made by a Moderator here on XDA. It is a False Positive. You can view a VirusTotal report (https://www.virustotal.com/en/file/25dc5dca2494d1b1d93832b37ba9852b4f076bba86cf5029b4c944a28a1a01a1/analysis/]HERE[/url]). 26 out of 67 virus scanners report it as a virus. If your Anti-Virus is one of the ones that flag it as a virus, I would suggest you explore other Anti-Virus software, but that’s not what this guide is about.
1B. As per the instructions on Moto’s site, you need to download and install the latest official drivers from Moto. (Download)
1C. Head over to the Moto website and follow the instructions to unlock your bootloader. (Moto Website)
After you are done on the Moto website your bootloader will be unlocked! This is necessary to be able to modify system files for root, roms, and other various tweaks!
Click to expand...
Click to collapse
I need to lock my bootloader again, how do I do that?
andreym_costa said:
I need to lock my bootloader again, how do I do that?
Click to expand...
Click to collapse
Same as unlocking but in reverse order.
Unlocking:
- activate OEM unlocking
- use command 'fastboot oem unlock'
=> First boot with an unlocked bootloader loads your unmodified stock ROM until you flash another ROM.
Here you start locking the bootloader with the same conditions. This means you have to flash the latest stock ROM before doing anything else.
Then (after you successfully boot your unmodified stock ROM once!!) you can boot into fastboot mode and execute 'fastboot oem lock'.
NEVER EVER deactivate the OEM unlock option before everything is ok!! The meaning of ok is, that your locked device will boot into system AND you have a functional Wifi and mobile connection. After this step (and only after that!) you can deactivate the OEM unlocking option.