Database Develop

[GUIDE] Flash SBF to Atrix (Mac OS X or Linux) *simple*

//Version 1.0
Flash any SBF file to your device *without* RSDLite (Mac or Linux)
*using sbf_flash created by [mbm]
**UPDATE: THIS DOES NOT WORK WITH RADIO SBFS. YOU CAN USE CWM TO FLASH RADIO IMGS.
**IF YOU ARE UNLOCKED WITH CWM, YOU REALLY SHOULD HAVE NO NEED TO FLASH FULL SBF FILES. SEE SAMCRIPP'S FRUIT CAKE THREAD
This guide is for Mac OS or Linux users only!! I didn't see any dedicated guide for flashing SBF files for Mac users so i thought I would contribute something to this wonderful community.
Pre-Guide Information (SKIP BELOW FOR ACTUAL INSTRUCTIONS)
The standard prerequisite for flashing SBF files to our devices is RSD Lite, and as we all know, the only platform made available for RSD Lite is Windows. Mac or Linux users have always been required to either run Windows using a virtual machine or find a Windows computer to use. In my opinion, all of these methods are time consuming and can sometimes be very frustrating. Now we can VERY easily flash any SBF file using a simple utility called "sbf_flash" (created by [mbm]). The creator of this wonderful little utility deserves a lot of credit because he was able to make the executable work on both Mac and Linux platforms which is no small feat considering Mac OS X uses the mach-o executable file format while Linux uses ELF. It is very interesting how he was able to accomplish this so if you are interested to find out how or interested in learning more about this nifty little utility, visit his blog.
[mbm]'s Optical Delusion Blog: http://blog.opticaldelusion.org/
DISCLAIMER: The following procedures require you to be somewhat comfortable using terminal and some basic commands. All the standard warnings apply as well. I am not responsible if anything happens to your device. It is your responsibility to ensure you are flashing an SBF that is compatible with your device. Check and then double check for good measure. I also recommend checking the md5sum of the file you choose. Check both the compression md5sum and the actual SBF file md5sum. Follow the instructions carefully and heed the warnings about downgrading.
** DO NOT TRY TO DOWNGRADE TO 1.8.3 IF YOU HAVE FLASHED AN OTA UPDATE OF 4.5.91 **
---------------------------------------------------------------------------------------------------------------------------------------------------
INSTRUCTIONS
SBF_FLASH GUIDE FOR MAC OS X (linux users too)
Required Files to Download:
- sbf_flash utility ---> DIRECT DOWNLOAD
- sbf file of your choice **make 100% sure the SBF file you choose is compatible with your device**
** no drivers needed, thats the beauty of this method. so clean **
**There are 2 sets of Instructions, choose one. Novice and Expert (Scroll below for Expert).**
Detailed Instructions (Novice):
GET READY: As always when flashing SBF files, remove your SIM and microSD cards and power the device on by holding the Vol+ and Power.
Step 1: Download sbf_flash and place it in an easily accessible directory (e.g. /Users/username/Documents)
*You have to rename the file "sbf_flash" to "sbf_flash.sh" (thank you n1ckr0th)
Step 2: Place the SBF file you have chosen in the SAME directory you put sbf_flash (e.g. /Users/username/Documents/).
Step 3: Open up a terminal shell.
Step 4: In terminal, change to the directory where you have placed both files:
* SKIP TO STEP 5 IF YOU KNOW HOW TO USE TERMINAL *
// how to change directories in terminal
* in the following instructions, ignore the brackets when typing in the commands
- the command [cd] is what you use to change the directory. so if the files are in /Users/username/Documents, you would type [cd Documents]
- the command [ls] lists all the files and folders in the current directory. type [ls] and make sure you see both files before proceeding.
Step 5: We first need to make sbf_flash executable (thank you ionstorm3) by doing the following steps:
* once again, ignore the brackets when typing these commands
- type [sudo chmod +x sbf_flash.sh]
- it will now prompt you for your password. enter it *note: [sudo] is a command which gives temporary admin privileges for the preceding command.
- sbf_flash is now executable. continue
Step 6: Flash the image onto your phone:
- type [sudo ./sbf_flash.sh nameofyourSBFfile] (example: if your SBF file is called "atrix.sbf", you would type [sudo ./sbf_flash.sh atrix.sbf]
- once again, it will prompt you for your password. enter it again.
- you are now done.
If you followed the above steps correctly, the SBF file will now begin flashing onto your device. Sit back, grab a brew, and relax.
*TIPS: when you are typing in the names of files or folders in terminal, you can hit the [tab] key after you have typed in the first few letters of the file or folder and terminal will autocomplete the rest. This is especially useful if your SBF file has a long name (e.g. OLYFR_U4_1.8.3_SIGNED_1g_1FF.sbf) in this case, if you just type OLYF then hit the [tab] key, terminal will autocomplete the rest of the filename for you. Very useful!
---------------------------------------------------------------------------------------------
EXPERT INSTRUCTIONS:
1. Download sbf_flash utility and place in easily accessible directory
2. Download SBF file of your choice and place in same directory
3. Open up a terminal shell and [cd] into that directory
4. Execute following command [sudo chmod +x sbf_flash.sh] - this makes sbf_flash exectuable (thanks ionstorm3)
5. Execute following command [sudo ./sbf_flash.sh nameofyourSBFfile] - this flashes your SBF file to your device.
6. Done son.
Well folks, that is it. In my opinion, this is the fastest and easiest way for Mac and Linux users to flash SBF files. Now we can finally do all our rooting/flashing/etc. on one machine. If you have any questions/concerns/problems, please feel free to PM me. Also, if you have any suggestions on improving this guide, let me know. Now it is time for me to give credit to those that deserve it.
CREDITS:
[mbm] for creating sbf_flash and making it work perfectly on both Mac and Linux platforms.
ionstorm3 - thank you very much for not only essentially providing me with the cream of this guide, but promptly responding to my initial concerns.
XDA Community: thank you for well……everything. this is such a great community with many helpful members.

This doesn't work for radio SBFs I believe?
Sent from my MB860 using XDA App

working with Ubuntu
I had no luck using sbf-fash until I updated the udev rules. it would just hang and not flash anything, after updating udev it works perfectly. I do not know if user on Linux other then Ubuntu will have this problem but if they are they may want to check out http://forum.xda-developers.com/showthread.php?t=921169 and look at step 5. This is a walk-through of getting adb setup and working under Ubuntu and is a very helpful post.
neer2005 said:
This doesn't work for radio SBFs I believe?
Click to expand...
Click to collapse
Not sure about that, I will have to test that out tonight.

neer2005 said:
This doesn't work for radio SBFs I believe?
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
this is actually a very good question that I do not know the answer to. but i will do my best to find out

arvindrao86 said:
this is actually a very good question that I do not know the answer to. but i will do my best to find out
Click to expand...
Click to collapse
I can confirm that this (unless terminal lied to me) works with the 4591Radio.sbf file provided by kenn for his rom.
also, you might want to change the op to say that you need to either rename the sbf_flash file to .sh after you download it and change the third step to include the .sh extension (sudo ./sbf_flash.sh nameofradio) or remove it from the first step because it didnt work until i added the .sh and included it in all the commands.

n1ckr0th said:
I can confirm that this (unless terminal lied to me) works with the 4591Radio.sbf file provided by kenn for his rom.
also, you might want to change the op to say that you need to either rename the sbf_flash file to .sh after you download it and change the third step to include the .sh extension (sudo ./sbf_flash.sh nameofradio) or remove it from the first step because it didnt work until i added the .sh and included it in all the commands.
Click to expand...
Click to collapse
thank you for the confirmation of radio flashing and for the obvious flaw in my instructions.

Stop flashing with sbf... You guys have more safer methods using cwm.
Sent from my MB860 using Tapatalk

CWM for radios?

n1ckr0th said:
I can confirm that this (unless terminal lied to me) works with the 4591Radio.sbf file provided by kenn for his rom.
Click to expand...
Click to collapse
Didn't seem to work for me w/Debian Squeeze, I'm afraid.
Code:
debian:/# ./sbf_flash.sh 4591Radio.sbf
SBF FLASH 1.23 (mbm)
http://opticaldelusion.org
=== 4591Radio.sbf ===
00: RDL03 0x00000000-0x002FFFFF 9FC5 AP
01: RDL01 0x00800000-0x008407FF 36FF BP
02: CG05 0x00000000-0x013E3BF7 E0E7 BP
>> waiting for phone: Connected.
>> uploading RDL03: 100.0%
-- OK
>> verifying ramloader
-- OK
>> executing ramloader
-- OK
>> waiting for phone: Connected.
>> sending erase
-- OK
>> rebooting

AnalogXDA said:
Didn't seem to work for me w/Debian Squeeze, I'm afraid.
Code:
debian:/# ./sbf_flash.sh 4591Radio.sbf
SBF FLASH 1.23 (mbm)
http://opticaldelusion.org
=== 4591Radio.sbf ===
00: RDL03 0x00000000-0x002FFFFF 9FC5 AP
01: RDL01 0x00800000-0x008407FF 36FF BP
02: CG05 0x00000000-0x013E3BF7 E0E7 BP
>> waiting for phone: Connected.
>> uploading RDL03: 100.0%
-- OK
>> verifying ramloader
-- OK
>> executing ramloader
-- OK
>> waiting for phone: Connected.
>> sending erase
-- OK
>> rebooting
Click to expand...
Click to collapse
I assume that you can flash other sbf files??
Also for me running Ubuntu 11.04 I have no need to rename it to a .sh but I guess if it works it works, that is the important thing.. Just for myself what shell are you using, I use bash.

Worked for me in Mac OSX (at least the radio flash). Also, no need to add the .sh extension in OSX.
Thanks for posting this, I've been trying to figure out how to use the new sbf_flash. I wasn't aware of the need to mark it as executable.

Tao_Man said:
I assume that you can flash other sbf files??
Also for me running Ubuntu 11.04 I have no need to rename it to a .sh but I guess if it works it works, that is the important thing.. Just for myself what shell are you using, I use bash.
Click to expand...
Click to collapse
Yep, I used sbf_flash to unlock the bootloader. I'm using bash, via Xfce terminal emulator.

getabetterpic said:
Worked for me in Mac OSX (at least the radio flash). Also, no need to add the .sh extension in OSX.
Thanks for posting this, I've been trying to figure out how to use the new sbf_flash. I wasn't aware of the need to mark it as executable.
Click to expand...
Click to collapse
the .sh was only added for consistency throughout the instructions.

The author is [mbm], not "Optical Delusions" ... that's just the name of his blog. And no, it does not flash your radio.
16:03 < [mbm]> anyway, sbf_flash can't reflash baseband
19:21 < [mbm]> right, sbf_flash has never touched the bp
19:21 < [mbm]> it just skips over those sections of the sbf
It's a great tool, but I think this thread belongs in General.

eval- said:
The author is [mbm], not "Optical Delusions" ... that's just the name of his blog. And no, it does not flash your radio.
16:03 < [mbm]> anyway, sbf_flash can't reflash baseband
19:21 < [mbm]> right, sbf_flash has never touched the bp
19:21 < [mbm]> it just skips over those sections of the sbf
It's a great tool, but I think this thread belongs in General.
Click to expand...
Click to collapse
changed guide to reflect correct credits. and agreed. this thread can and should be moved to general.

neer2005 said:
This doesn't work for radio SBFs I believe?
Click to expand...
Click to collapse
Correct, sbf_flash has never flash radio. You will see RDL01 & CG05 don't even upload.
AnalogXDA said:
CWM for radios?
Click to expand...
Click to collapse
Sure. I posted one here for baseband version N_01.100.00R for example. Kudos to SamCripp for discovering we can now CWM the baseband.. in the past, before unlock (and when CWM was not in the recovery partition and ran via the charge_only_mode hack) we could not.
getabetterpic said:
Worked for me in Mac OSX (at least the radio flash)
Click to expand...
Click to collapse
No, it didn't. Prove it to yourself: check the baseband version in about phone. Unless [mbm] in the future adds support for talking to the BP (baseband processor) sbf_flash will not do radio. You will notice the baseband version in 'about phone' doesn't change as you flash different radios.

ceo.mtcl said:
Stop flashing with sbf... You guys have more safer methods using cwm.
Sent from my MB860 using Tapatalk
Click to expand...
Click to collapse
Agree 100%
Sent from my unlocked atrix.

This still worked like a charm so thank you.
Sent from my MB860 using XDA App

Any idea if this can be done for other Moto devices as well? What needs to be changed? I tried it as instructed with my Droid Pro using OSX 10.7.3 and it didn't work. Didn't brick my phone or anything. I can post my output if that would help.

BenSWoodruff said:
Any idea if this can be done for other Moto devices as well? What needs to be changed? I tried it as instructed with my Droid Pro using OSX 10.7.3 and it didn't work. Didn't brick my phone or anything. I can post my output if that would help.
Click to expand...
Click to collapse
Old thread here I know but I am looking for some confirmation and maybe someone will answer. I am wanting to flash my phone back but do not have a carried specific SBF (Alltel). I will have to use a Verizon SBF but I don't want to flash the radio. Are we sure that this will not flash the radio so I will not lose my data connectivity?
I ran through the steps with the phone not connected and this is what I see:
SBF FLASH 1.24 (mbm)
http://opticaldelusion.org
=== SBF.sbf ===
00: RDL03 0x82000000-0x8204CFFF B942 AP
01: RDL01 0x00150000-0x001FFFFF DEFA BP
02: CG03 0x00000000-0x00904367 6F6F BP
03: CG31 0xB0280000-0xB02847FF 0EB7 AP
04: CG33 0xB1900000-0xB24C07FF 5CC1 AP
05: CG34 0xB0700000-0xB07047FF 75F3 AP
06: CG35 0xB1000000-0xB13FFFFF 119D AP
07: CG39 0xB2A00000-0xC41C07FF A8ED AP
08: CG42 0xB0800000-0xB083FFFF AC60 AP
09: CG47 0xB1400000-0xB18FFFFF 5728 AP
10: CG61 0xB0B00000-0xB0B7FFFF 5D7F AP
11: CG64 0xB0000000-0xB00047FF 1768 AP
12: CG65 0xB0180000-0xB01847FF 7167 AP
13: CG66 0xD0000000-0xDFFFFFFF 9B93 AP
>> waiting for phone:
Any help???

How To Use ADB Without SDK

Hello Everyone.
Let me just start by saying I AM NOT a developer and do not take credit for this information. Just did some Googling and came across it and I haven't really seen this in the forum here and I really found it useful. It is a link to an article with instructions on how to set up ADB without the massive developer download that comes packaged with the standard Android SDK. Written by Lalit Indoria on the "Hack My Android" site.
Basically it allows you to easily run ADB commands without ANY complicated set up. Remember you will still need the proper drivers for your device and always follow instructions so you don't bork anything up. I followed this to both flash the new 4.4 image and also root my Nexus 4. With it being the weekend I don't suspect we will get any OTA until Monday at the earliest so for those of us that are growing ever impatient.. here you go. Enjoy. :good:
http://www.hackmyandroid.com/use-adb-fastboot-commands-without-installing-android-sdk/2479

Also on recent debian distributions (currently debian jessie - testing - and debian sid - unstable), or ubuntu quantal and newer, you can simply install adb and fastboot by installing a few packages:
Code:
sudo apt-get install android-tools-adb android-tools-fastboot

jcnbama said:
Hello Everyone.
Let me just start by saying I AM NOT a developer and do not take credit for this information. Just did some Googling and came across it and I haven't really seen this in the forum here and I really found it useful. It is a link to an article with instructions on how to set up ADB without the massive developer download that comes packaged with the standard Android SDK. Written by Lalit Indoria on the "Hack My Android" site.
Basically it allows you to easily run ADB commands without ANY complicated set up. Remember you will still need the proper drivers for your device and always follow instructions so you don't bork anything up. I followed this to both flash the new 4.4 image and also root my Nexus 4. With it being the weekend I don't suspect we will get any OTA until Monday at the earliest so for those of us that are growing ever impatient.. here you go. Enjoy. :good:
http://www.hackmyandroid.com/use-adb-fastboot-commands-without-installing-android-sdk/2479
Click to expand...
Click to collapse
Mini-adb comes with adb.exe, fastboot.exe and two adb .dlls needed to run adb in windows. So basically to run adb all that is required is 3 files. Also fastboot doesn't require anything except the executable. Mini-adb has been out there for about 2 years that I know of on androidforums.

fredericve said:
Also on recent debian distributions (currently debian jessie - testing - and debian sid - unstable), or ubuntu quantal and newer, you can simply install adb and fastboot by installing a few packages:
Code:
sudo apt-get install android-tools-adb android-tools-fastboot
Click to expand...
Click to collapse
If you do that, you also need to do step 1 from here: http://bernaerts.dyndns.org/linux/74-ubuntu/245-ubuntu-precise-install-android-sdk

You can install the Wugs nexus toolkit. It has all the features you need.

eksasol said:
If you do that, you also need to do step 1 from here: http://bernaerts.dyndns.org/linux/74-ubuntu/245-ubuntu-precise-install-android-sdk
Click to expand...
Click to collapse
That was not necessary on my debian Sid install. Yesterday I simply installed the packages, Co nected my nexus 7 and used adb sideload to flash the kitkat ota.
The steps seem to apply to Ubuntu precise. Maybe it is not necessary in newer versions.

A pure C implementation of 'cuber' using OpenSSL's BigNum library

In case anybody cares, here's a pure C reimplementation of 'cuber.py'
(my own earlier reimplementation of @vortox's signature.py).
This is what I'm using in my '1-Click' bootloader unlock VM...
See 'grep ^gcc' for "build instructions".
Hack, you can probably build this for ARM and run it right on your very HDX tablet... (-;
UPDATE (JanuaryFebruary 2017):
OK; so, @zivimo had built this for ARM, but people still haven't noticed.
I repacked his binary from a .tar.gz to a .zip archive and decided to spell out the instructions for use.
Perhaps, this helps... With the right bootloader in place, and adb/fastboot installed (and working),
the unlock is as easy as follows...
Download and extract unlock.zip (SHA256: e40e3010f8eccfa9cbd1e73eecac30cf799099d183de23b2d256fc3407f143f6e5db0b8d82c8fd2a25a22b0a598014d22a2ec33cef27a8d4b65a36acde08f27a)
to the same directory that holds the adb and fastboot executables (unless you have added them to your PATH)
Click on get_code.bat in the extracted folder
-- optional (but commonly required) step(s) --
fix root (roll back, if you need to), flash vulnerable bootloader
[you'll definitely need to perform at least some of these if the last step fails]
Click on unlock.bat in the extracted folder
The archive also includes .sh variants of the .bat files for convenience.
You could also just click to show the hidden section and cut&paste... (-;
Code:
[STRIKE]unzip cuber.zip[/STRIKE]
adb push cuber /data/local/tmp/
adb shell chmod 0755 /data/local/tmp/cuber
adb shell 'id=$(cat /sys/class/block/mmcblk0/device/{manfid,serial}); echo "$id"; echo 0x${id:6:2}${id:11:8} | /data/local/tmp/cuber > /sdcard/unlock.code'
adb pull /sdcard/unlock.code
adb shell rm /sdcard/unlock.code /data/local/tmp/cuber
adb reboot-bootloader
fastboot -i 0x1949 flash unlock unlock.code
NOTE: download and extract the attached 'cuberunlock.zip' and run the above commands
in the directory where 'cuber' got extracted to.

Nice job! Originally I wanted to use OpenSSL BigNum too, but I hadn't enough time and Python was easier to use

hey,
made a static compile with an arm debian (jessie). seemed the easiest solution to me. compile command:
Code:
# gcc -fPIE -static cuber.c -o cuber -lssl -lcrypto
# strip cuber
# ldd cuber
not a dynamic executable
# ./cuber
Usage: cuber [RSA-bytes] < data > sig
seems to work. arm(!) binary attached.

ok draxie, you pointed me here but something seems to be missing. i downloaded unlock.zip, put the files in my adb directory. when i run get_code.bat, it pushes cuber to the kindle in the right directory, changes permissions (dont see any errors there) but then stops saying the system can't find the specified path. Whats funny is i used es file explorer to check the paths in the script, and they are there so not sure where the hang up is.

chin_bone said:
ok draxie, you pointed me here but something seems to be missing. i downloaded unlock.zip, put the files in my adb directory. when i run get_code.bat, it pushes cuber to the kindle in the right directory, changes permissions (dont see any errors there) but then stops saying the system can't find the specified path. Whats funny is i used es file explorer to check the paths in the script, and they are there so not sure where the hang up is.
Click to expand...
Click to collapse
Did you check all three paths?
/data/local/tmp
/sdcard
/sys/class/block/mmcblk0
The 2nd one _may_ be problematic if you're on SafeStrap.
I don't know why. I'm yet to install that on one of my test
devices to investigate. (Or, was that the 1st... )
The 0 in the 3rd one may actually be a 1 on some systems.
I have a few extra lines in my VM script to work around
that, I can easily add that here as well, if that turns out
to be the issue.
BUT, to try and troubleshoot: how far does the script get?
If it didn't complain with the permissions, the 1st path is probably OK.
Does it print your manfid/serial?
If so, mmcblkX would be right as well.
Any chance that you're on SafeStrap?
Can you push/pull to/from /sdcard?
- - - - -
On a second thought: I've only ever tested this on Linux.
String quoting on Windows may work differently, and could *royally* mess up how that more complex command is interpreted.
I'll test tomorrow; it's like 20 past 1am here. I need to get some sleep.
In the meantime, as a workaround, you could just hard-code your manfid/serial, and replace this line:
Code:
adb shell 'id=$(cat /sys/class/block/mmcblk0/device/{manfid,serial}); echo "$id"; echo 0x${id:6:2}${id:11:8} | /data/local/tmp/cuber > /sdcard/unlock.code'
by the decidedly much simpler:
Code:
adb shell 'echo 0xmmssssssss | /data/local/tmp/cuber > /sdcard/unlock.code'

draxie said:
Did you check all three paths?
/data/local/tmp
/sdcard
/sys/class/block/mmcblk0
The 2nd one _may_ be problematic if you're on SafeStrap.
I don't know why. I'm yet to install that on one of my test
devices to investigate. (Or, was that the 1st... )
The 0 in the 3rd one may actually be a 1 on some systems.
I have a few extra lines in my VM script to work around
that, I can easily add that here as well, if that turns out
to be the issue.
BUT, to try and troubleshoot: how far does the script get?
If it didn't complain with the permissions, the 1st path is probably OK.
Does it print your manfid/serial?
If so, mmcblkX would be right as well.
Any chance that you're on SafeStrap?
Can you push/pull to/from /sdcard?
- - - - -
On a second thought: I've only ever tested this on Linux.
String quoting on Windows may work differently, and could *royally* mess up how that more complex command is interpreted.
I'll test tomorrow; it's like 20 past 1am here. I need to get some sleep.
Click to expand...
Click to collapse
It's all good draxie, i figured out what i was doing wrong with the other procedure, that damn STEP 2, once i did it, everything fell into place. Bootloader unlocked and now just trying to figure out which rom to try first. Thanks again, you guys are great and i know how valuable everyones time is. :good:

I keep hitting road blocks, I am rooted and on Fire OS 4.5.5.2 I click get code a screen flashes up then I click Unlock and my Kindle boots to the Grey Kindle screen with Fastboot underneath and nothing else happens. Same happens when I copy and past the code into ADB. What step am I failing at? Thanks for the help!

pdanforth said:
I keep hitting road blocks, I am rooted and on Fire OS 4.5.5.2 I click get code a screen flashes up then I click Unlock and my Kindle boots to the Grey Kindle screen with Fastboot underneath and nothing else happens. Same happens when I copy and past the code into ADB. What step am I failing at? Thanks for the help!
Click to expand...
Click to collapse
@draxie - I have no experience with this tool; python/gmpy2 works reliably for me. Sorry to pull you in ...

Davey126 said:
@draxie - I have no experience with this tool; python/gmpy2 works reliably for me. Sorry to pull you in ...
Click to expand...
Click to collapse
I am up and running now, unlocked and running kk-fire-nexus-rom-thor-20161017. Play store is also up and running.

pdanforth said:
I am up and running now, unlocked and running kk-fire-nexus-rom-thor-20161017. Play store is also up and running.
Click to expand...
Click to collapse
Did you end up using some other method, or did these scripts work for you in the end?
Either way, others may find useful if you could share whatever worked for you. (-;
Unfortunately, I still haven't had a chance to test these scripts in Windows;
so, I couldn't answer your first call for help in a good way. If there's something
wrong and there's enough interest, I'll be happy to fix it as soon as I can.

draxie said:
Did you end up using some other method, or did these scripts work for you in the end?
Either way, others may find useful if you could share whatever worked for you. (-;
Unfortunately, I still haven't had a chance to test these scripts in Windows;
so, I couldn't answer your first call for help in a good way. If there's something
wrong and there's enough interest, I'll be happy to fix it as soon as I can.
Click to expand...
Click to collapse
@stangri did my unlock file and I used this thread to unlock https://forum.xda-developers.com/kindle-fire-hdx/general/thor-unlocking-bootloader-firmware-t3463982
I had trouble making the Unlock file, once that was done and some help from other users I am now up and running!

[REQUEST] Compile for any phone script

I propose a single script that generates images for any android compatible phone. It will (maybe?) require a bootloader unlock, the kernel source, and a cached 'update.zip' or internet connection, but not much else.
Essentially, all you will need to do is plug in your phone and run the script as an admin (sudo sh ubuntuphone-auto.sh). Then, the script will install all of the (cached) dependencies, automatically download (or used the cached one) the system's flash/update zip, and compile ubuntu with the contained images.
It should also do a sideload of a processor test (if compatible) and warn of currently incompatible or too hot/slow hardware while it's compiling on the computer.
This will help clear out that system fragmentation thing where it's hard to develop for all systems. We should add options for a bunch of android app stores to be installed. (Something like 'do you want the play store' and if they press enter it skips it. The generic install without any extras will need you to put a --generic or hold down the enter key)
The script will be just that - a bash or python script that has a comment at the end of each line with a line number and a note briefly explaining what you can change on that line.
We eventually could make it not just for ubuntu, but for every arm based OS like CM13, FireOS, etc.
However, things should start small... Let's just start with Ubuntu.

runed.OS said:
I propose a single script that generates images for any android compatible phone. It will (maybe?) require a bootloader unlock, the kernel source, and a cached 'update.zip' or internet connection, but not much else.
Essentially, all you will need to do is plug in your phone and run the script as an admin (sudo sh ubuntuphone-auto.sh). Then, the script will install all of the (cached) dependencies, automatically download (or used the cached one) the system's flash/update zip, and compile ubuntu with the contained images.
It should also do a sideload of a processor test (if compatible) and warn of currently incompatible or too hot/slow hardware while it's compiling on the computer.
This will help clear out that system fragmentation thing where it's hard to develop for all systems. We should add options for a bunch of android app stores to be installed. (Something like 'do you want the play store' and if they press enter it skips it. The generic install without any extras will need you to put a --generic or hold down the enter key)
The script will be just that - a bash or python script that has a comment at the end of each line with a line number and a note briefly explaining what you can change on that line.
We eventually could make it not just for ubuntu, but for every arm based OS like CM13, FireOS, etc.
However, things should start small... Let's just start with Ubuntu.
Click to expand...
Click to collapse
If that script had existed, we would'nt had a need in developers at all
This script would be a reality only in ideal world with open drivers. Because of rush in smartphone production we have binary blobs with tons of lags and devices with unupgradable kernels at all (that are VERY important for security).
the reality is that not all companies release AOSP sources for their device, this devices need patches in order to provide all functions of phone, and in fact enthuthiasts do a little reverse-engineering work where possible.
This script isn't possible now, maybe in few years when machines will learn reverse-engineering and some logic.
But generally idea is nice, implementation will lack for some time

Haha, look! Ubuntu just made one of these! It only works for their phones, though.

runed.OS said:
Haha, look! Ubuntu just made one of these! It only works for their phones, though.
Click to expand...
Click to collapse
No, it doesn't work as you want.
You still have to download binary drivers and place them manually in corresponding folder. It doesn't automatically port ROM
Plus you have to download precompiled kernel for UT separately.
It's FAR for script you want.

[TOOL] crosshAtchDB: Pixel 3 XL Flash Tool

I'm trying to create an application to make flashing files on our pixel devices easier.
Features:
Install ADB
Unlock bootloader
Reboot to bootloader
Download and install factory images
Download and install TWRP
Download Magisk
Easy to use GUI
Enjoy! :good:
Credit to Dees_Troy and bigbiff for TWRP image.
Feel free to modify and hack away at the source.
WARNING: I am not responsible for anything that goes wrong using this tool, it works fine on my windows 10 machine, and tested on windows 7. However, make sure you know what these tools are doing beforehand.
New update!
Beta Release
What's New?:
All new base being built.
Better .exe support (requires installing the app)
Console interface for now.
Removed some features that were broken in the old app, will add them back one-by-one, but this time, not until they work 100%.
Usage:
Just follow the prompts on screen.
Allows picking the files for booting TWRP or pushing files via ADB.
Install:
Easy method (requires install): https://github.com/boostedd2/crosshatchdb/blob/boostedd2-patch-1/crosshAtchDB-2.3-win32.msi
Install the app with the provided .msi, choose where you want to install it. Open the folder where you installed it and run the crosshatchdbbeta.exe.
Build/Run from source:
Requires:
source .py file: https://github.com/boostedd2/crosshatchdb/blob/boostedd2-patch-1/crosshatchbeta.py
cxfreeze config: https://github.com/boostedd2/crosshatchdb/blob/boostedd2-patch-1/setup.py
To run from source, just install Python on your PC, then from cmd window run : "pip install requests".
Then just double click on the crosshatchdbbeta.py file.
To build the .exe:
You need both files from above.
Install Python
python -m pip install cx_Freeze --upgrade
With setup.py and crosshatchdbbeta.py in the same directory, run "python setup.py build"
This is a very minimal release, I will continue to fix any bugs and add features once they are working better.

Thank you so much for this! I was actually going to unlock my bootloader and root today after work. Now it will only take 2 minutes instead of 20!
I appreciate it and will report back later after testing!
**Didn't want to waste thread space so I'm editing this to reply** - Thank you so much for the response below! Very helpful! I'm up and running and really appreciate the tool and the help!

NippleSauce said:
Thank you so much for this! I was actually going to unlock my bootloader and root today after work. Now it will only take 2 minutes instead of 20!
I appreciate it and will report back later after testing!
Click to expand...
Click to collapse
No problem, quick usage guide to make sure it goes smooth.
Enable OEM unlock in developer options, also enable ADB debugging.
Plug in your phone, run crosshatchdb.
Select option 9, this will auto download and extract adb to your c: drive.
Select option 1 to check for ADB devices, check the box on the dialog that pops up on your phone.
All set. You can download magisk directly to your phone or push it from your PC.
Reboot bootloader option 2, from here you can unlock the bootloader(formats your phone btw).
Setup your phone, enable ADB debugging again and your free to reboot bootloader and download/boot TWRP to flash magisk.(use TWRP img not zip)
Hopefully these instructions are not too confusing, it is pretty easy once you do it once, and the tool really does make the next time you do it faster.
Tested on a windows 7 virtual machine and my own personal windows 10 machine.

NippleSauce said:
Thank you so much for this! I was actually going to unlock my bootloader and root today after work. Now it will only take 2 minutes instead of 20!
I appreciate it and will report back later after testing!
Click to expand...
Click to collapse
The time to unlock a Google purchased Pixel isn't the issue. The factory reset just sucks if you run stock for any time before doing it.

Two things I think you should add.
1) adb sideload for when adb works in twrp.
2) adb logcat for our great developers, so there isn't an excuse for getting them a logcat in event that they need one.
Sent from my Pixel 3 XL using Tapatalk

superchilpil said:
Two things I think you should add.
1) adb sideload for when adb works in twrp.
2) adb logcat for our great developers, so there isn't an excuse for getting them a logcat in event that they need one.
Click to expand...
Click to collapse
Good idea, should be easy to pipe logcat output to a text file.
ADB sideload can be added as well, next update will probably be when TWRP ADB is fixed, or sooner depending how long that takes.
Already thinking of ways to make the current version of this script more automated, but I like to err on the side of explicit is better than implicit.
Thanks for the ideas.

Can this install TWRP ?

Zorachus said:
Can this install TWRP ?
Click to expand...
Click to collapse
No. Everything you need to know is in the OP and everything else you need to know is in the twrp thread.
Sent from my Pixel 3 XL using Tapatalk

superchilpil said:
No. Everything you need to know is in the OP and everything else you need to know is in the twrp thread.
Click to expand...
Click to collapse
This.
It is a good option of you want an easy way to just boot TWRP in 1 button, if you don't want to install a custom recovery like TWRP.

New update coming soon, decided that command line didn't work very well for this purpose...
Also working on making all of the actions smoother.

New update released, let me know if you have any issues or feature requests, still waiting for TWRP to be fully functional before adding ADB sideload options.
CMD window still wants to hang out for now, you can minimize it though if needed.

can you add a (check for update)

Maty360414 said:
can you add a (check for update)
Click to expand...
Click to collapse
Yes, that is on the list for next update.
When TWRP is more reliable I will probably add options for copying TWRP backups to your PC as well.
Still need to get rid of the cmd window and cut down on having to open browser windows or file selection dialogs, just to get it feeling less clunky.

I'd like to send out a big thank you to boostedduece I've used platform tools and google flash all for years with no hitch whatsoever but I tried to glies an update to my kernel and ran into the red corrupt device thing and used my platform tools to flash all and halfway through it stopped and said error. I then tried this tool and it worked perfect!! Thank you so much!

quinejh said:
I'd like to send out a big thank you to boostedduece I've used platform tools and google flash all for years with no hitch whatsoever but I tried to glies an update to my kernel and ran into the red corrupt device thing and used my platform tools to flash all and halfway through it stopped and said error. I then tried this tool and it worked perfect!! Thank you so much!
Click to expand...
Click to collapse
Glad to hear it helped out, working on some new updates to make the UI even better.
Trying to make all of the download links update automatically too, just working on some web scraping again ?
It's a nice little tool if something gets messed up, also for new users to get up and running.

New update released, Download factory image has been overhauled, it will now download the image automatically, check the SHA-256 hash, then unzip it to the correct folder, just run the factory image flash option after and you're set. Be patient, the image.zip can take a while to download, takes several minutes for me, but I'm only at 50mbps down...and who knows if google throttled my connection after all the web scraper testing lol.
Pull TitaniumBackup folder via ADB to your PC, pull TWRP backup might not work it failed for me, but will not cause any damage to your PC or phone, ADB is copying the files read only from your device, and ADB just seemed to crash on me.
CMD window is still here for now until I pipe the output to the built in box on the GUI and bind keyboard keys to interact with it. For now it will help with any debugging.

boostedduece said:
New update released, Download factory image has been overhauled, it will now download the image automatically, check the SHA-256 hash, then unzip it to the correct folder, just run the factory image flash option after and you're set. Be patient, the image.zip can take a while to download, takes several minutes for me, but I'm only at 50mbps down...and who knows if google throttled my connection after all the web scraper testing lol.
Pull TitaniumBackup folder via ADB to your PC, pull TWRP backup might not work it failed for me, but will not cause any damage to your PC or phone, ADB is copying the files read only from your device, and ADB just seemed to crash on me.
CMD window is still here for now until I pipe the output to the built in box on the GUI and bind keyboard keys to interact with it. For now it will help with any debugging.
Click to expand...
Click to collapse
Can't believe I still haven't gotten the Ota Nov update
Will this work on p3?

frewys said:
Can't believe I still haven't gotten the Ota Nov update
Will this work on p3?
Click to expand...
Click to collapse
It will work for pixel 3, but you will need to download the factory image for your blueline device and extract it into c:\crosshatch_stuff\platform-tools. This program is basically a gui wrapper for ADB commands.
Just stick with the ADB tools section and find the downloads you need separately.

boostedduece said:
It will work for pixel 3, but you will need to download the factory image for your blueline device and extract it into c:\crosshatch_stuff\platform-tools. This program is basically a gui wrapper for ADB commands.
Just stick with the ADB tools section and find the downloads you need separately.
Click to expand...
Click to collapse
Right
So it doesn't automate the process the same as for xl?

frewys said:
Right
So it doesn't automate the process the same as for xl?
Click to expand...
Click to collapse
It will still install ADB and allow you to run reboot bootloader, boot TWRP, factory reset, ADB logcat, unlock bootloader.
But the only extra part that is manual would be extracting the factory image into the c:\crosshatch_stuff\platform-tools folder.