[GUIDE] Flash SBF to Atrix (Mac OS X or Linux) *simple* - Atrix 4G Android Development

//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???

Related

HOW TO: Webtop 2.3.4 HKTW fix

Tested and works (thanks jnl) I'm posting a link to CG61.img for easy loading extracted from 1FF-olympus_hktw-userdebug-2.3.4-4.5.2A-5_OLH-3-110614-test-keys-Retail-05.sbf
Download moto-fastboot for your os from http://forum.xda-developers.com/showthread.php?t=1138092
CG61.img Link - MD5 = 9151fca5183b85953d7afed83364802a
https://www.rapidshare.com/files/4119742271/CG61.img
Steps I followed on OSX:
Download CG61.img (placed in same directory as moto-fastboot)
Place your device in fastboot mode via the volume-down then volume-up procedure and verify it exists with ./moto-fastboot devices
./moto-fastboot flash webtop CG61.img
./moto-fastboot reboot
You might have to reboot the device 2X after this is complete before the webtop option shows up when docked
----=== NO NEED TO FOLLOW THE BELOW STEPS UNLESS YOU EXTRACT FROM THE SBF ===----
Below is from JNL:
Since I have the lapdock and did not want to revert to Froyo, I thought I'd give a more detailed explanation than the hint I worked from to re-enable webtop (with firefox 4.0.1!):
Download the leaked HK/TW sbf file and the 'sbf_flash' for linux (I did this under 32-bit ubuntu).
use sbf_flash -x 1FF-olympus_hktw...sbf
This will extract a collection of .img files.
Place your device in fastboot mode via the volume-down then volume-up procedure and verify it exists with:
sudo ./moto-fastboot32 devices
Then:
sudo ./moto-fastboot32 flash webtop CG61.img
This will run a 3-step flashing process. Once completed, do:
sudo ./moto-fastboot32 reboot
Voila. Webtop works and actually seems faster.
Hope this helps.
mburlingame said:
Steps I followed:
Download CG61.img
./moto-fastboot devices
./moto-fastboot flash webtop CG61.img
./moto-fastboot reboot
Click to expand...
Click to collapse
actually, just to clarify... is that in cmd on windows you're talking about? Where do we put the CG61.img?
s1mpd1ddy said:
actually, just to clarify... is that in cmd on windows you're talking about? Where do we put the CG61.img?
Click to expand...
Click to collapse
I ran this from OSX using the commands I listed jnl ran it from 32-bit ubuntu it looks like via the commands he posted
I placed the image in the same directory as moto-fastboot
Looking at the commands, it is for Linux. Get a Ubuntu LiveCD, very useful tool to have around.
Sent from my MB860 using XDA App
sifon187 said:
Looking at the commands, it is for Linux. Get a Ubuntu LiveCD, very useful tool to have around.
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
I am guessing this should work in Windows as well I am currently installing Windows 7 under VMware Fusion on my mac to confirm.
confirmed I could run this from Windows and did not get any errors back so performing this via the windows moto-fastboot should work as expected
Updated CG61.img link from DropBox to RapidShare due to DropBox shutting the link down due to excessive downloads (according to them)
So, I did the 1st step and nothing happened.
Do I have to do the 2nd step? If yes, where I find "sbf_linux" and "1FF-olympus_hktw...sbf"?
brunnogama said:
So, I did the 1st step and nothing happened.
Do I have to do the 2nd step? If yes, where I find "sbf_linux" and "1FF-olympus_hktw...sbf"?
Click to expand...
Click to collapse
You only need to follow the first section (Download the img file and download moto-fastboot for your os)
Are you saying that after you download the img and run moto-fastboot devices you do not see your device listed?
Can you post exactly whats happening when you run moto-fastboot devices then try to load the image on your device via moto-fastboot flash webtop CG61.img (make sure CG61.img is in your moto-fastboot directory)
So, I did everything again, and it´s still doesnt working.
No one errors appears. But when a plug phone on lapdock, doenst show the webtop´s option. when I execute them, appears an error: "This app Webtop.... has stopped unexpctedly..."
My log:
brunnogama said:
So, I did everything again, and it´s still doesnt working.
No one errors appears. But when a plug phone on lapdock, doenst show the webtop´s option. when I execute them, appears an error: "This app Webtop.... has stopped unexpctedly..."
My log:
Click to expand...
Click to collapse
Are you running the HKTW 2.3.4 image? ( Image from the following thread http://forum.xda-developers.com/showpost.php?p=15020775&postcount=2 )
Yes! I do!
It isnt correct?
brunnogama said:
Yes! I do!
It isnt correct?
Click to expand...
Click to collapse
Hmm yes that is correct - Can you tell me what OS you are using? maybe try another USB port I will do an md5 checksum on the file and post it maybe a bad download?
MD5 = 9151fca5183b85953d7afed83364802a
Did everything correct... Pretty damn sure. Phone won't even power up now.
Pull battery, plug back in usb cable, get green light, it goes out. Got it to fire up once with no sim.
F*ck !
EDIT: Dumb ass. Don't know how battery drained like a MF. Powered up in wall jack.
So, I´m using Windows 7 32.
I tried another port, tried new flash and nothing.. I´still having the same error when I execute webtop.
:/
brunnogama said:
So, I´m using Windows 7 32.
I tried another port, tried new flash and nothing.. I´still having the same error when I execute webtop.
:/
Click to expand...
Click to collapse
Hmm I have not been able to duplicate this issue - Can you confirm the MD5 checksum? Has anyone else seen this issue with Windows 7 and trying to flash this?
does this fix multimedia dock too? i dont get clock option when my phone is on the dock.
So, I tried on Ubuntu and doenst change anything. I still havent the webdock.
I have the clock issue too. When I plug on lapdock, the clock doenst fit on horizontal position.
Does this work with hdmi cable without any dock?
xabierd said:
Does this work with hdmi cable without any dock?
Click to expand...
Click to collapse
No this requires the Media Dock or the Laptop dock in order to work
Any chance to get the Debian 0.2.5 Webtop back?
Cheers

Factory Images for Nexus Devices

The following is the definitive source for Factory ROMS for Nexus Devices:
https://developers.google.com/android/nexus/images
Please also check for updated Nexus7 (nakasi) factory images as well.
After downloading the appropriate image from above link, uncompress it with the following:
tar zxvf nakasi-krt160-factory-"abcxyz".tgz
Then, place your Nexus device into fastboot mode, connect it to your computer, and run the resulting script:
cd nakasi-krt160/
For Unix:
sudo ./flash-all.sh
For Windows:
./flash-all.bat
You may get the following warnings, which you can ignore, the restoration will continue anyway.
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
Then you may lock the device again after another reboot into the fastboot mode:
sudo fastboot oem lock
Does this link do me any good for my tilapia? https://developers.google.com/android/nexus/images#nakasig
Can I use the method above.
jamesDF said:
/snip
Click to expand...
Click to collapse
If you're writing a post like this, you might want to generalize your instructions for Windows and UNIX-like machines (or specify which one; run your commands in Windows and you'll only get errors). More importantly, you may want to mention that the flash-all script includes "fastboot -w", which can be a nasty shock if you're not expecting your partitions to get wiped for one reason or another.
Ultimately, thread will probably be buried though.
anyone getting mismatched MD5 for the wifi version? i've downloaded 3 times, used wifi and ethernet, 2 diff md5 checkers. All seem to be reading the same mismatched MD5 info
Instructions per developers.google.com
Instructions
You will find these files useful if you have used the Android Open-Source Project, flashed custom builds on your device, and wish to return that device to its factory state.
In order to use these files, you need to have the fastboot tool in your PATH. That tool is compiled as part of every configuration of the Android Open-Source Project and is the tool used to flash custom builds on your device. On GNU/Linux systems, this also implies that you have configured USB access as mentioned in the machine setup instructions.
Your device needs to be in fastboot mode, with the bootloader unlocked. The relevant key combinations and commands are documented on the page about building for devices.
You need to uncompress each download before use, which creates a new directory for that exact download. That directory contains a ./flash-all.sh script, which handles the various operations, installs the necessary bootloader, baseband firmware(s), and operating system. Note that this operation deletes all user data by default.
After restoring a factory image, it is recommended that you lock the bootloader, for security reasons.Instructions
You will find these files useful if you have used the Android Open-Source Project, flashed custom builds on your device, and wish to return that device to its factory state.
In order to use these files, you need to have the fastboot tool in your PATH. That tool is compiled as part of every configuration of the Android Open-Source Project and is the tool used to flash custom builds on your device. On GNU/Linux systems, this also implies that you have configured USB access as mentioned in the machine setup instructions.
Your device needs to be in fastboot mode, with the bootloader unlocked. The relevant key combinations and commands are documented on the page about building for devices.
You need to uncompress each download before use, which creates a new directory for that exact download. That directory contains a ./flash-all.sh script, which handles the various operations, installs the necessary bootloader, baseband firmware(s), and operating system. Note that this operation deletes all user data by default.
After restoring a factory image, it is recommended that you lock the bootloader, for security reasons.
digitallure said:
anyone getting mismatched MD5 for the wifi version? i've downloaded 3 times, used wifi and ethernet, 2 diff md5 checkers. All seem to be reading the same mismatched MD5 info
Click to expand...
Click to collapse
me too,any solution??
andrewk2x said:
me too,any solution??
Click to expand...
Click to collapse
I took a risk flashing it and had no problems at all
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Do these have the same 3.1 kernel ?
digitallure said:
I took a risk flashing it and had no problems at all
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I downloaded md5 calculator and i find the correct md5 and flashed with toolkit.
Sent from my Nexus 4 using Tapatalk
jpm168 said:
Do these have the same 3.1 kernel ?
Click to expand...
Click to collapse
Yes, 4.4 still have 3.1.10.
Sent from my Nexus 7 using Tapatalk 4

[TOOLS] Create unlock.img, fix boot.img, repack update.bin (for aboot

The attached archive includes 3 tools for those of you with .3.2.3.2 (or earlier) bootloaders.
Since other tools (and earlier version of these very tools) are available and working well,
this is mostly meant as an entry to an imaginary beauty contest. (JOKING!!!)
cuber.py
a generic gmpy2-free reimplementation of @vortox's signature.py
use this to generate your unlock.img
cuboot.py (uses cuber.py)
a Python-only reimplementation of @vortox's cuber
includes fixes to the kernel command-line and the device-tree
use this to convert a standard Amazon boot.img (>=.4.x.x)
upHDX (uses cuboot.py)
bash script to repack Amazon updates for TWRP
could be DANGEROUS, use with care
tested on Apollo for both 14.4.5.2 and 14.4.5.3
my unit is fully 14.4.5.3 now, except for aboot (which is 3.2.3.2)
should work on Thor as well
Those with bootloader .3.2.6 and lower can downgrade to .3.1.0
and upgrade the bootloader to the latest vulnerable version .3.2.3.2.
Those with .3.2.7 and higher appear to be out of luck with forged signatures, but I hear there's progress on rooting .4.5.2.
The python scripts have been tested on the following OS / Python combinations:
Windows: 2.7.9 and 3.4.3
Linux: 2.7.9 and 3.3.4
OSX: 2.6.? (cannot quite remember)
In addition to the tools themselves, I also included "educational" examples
(examples.sh for Linux/OSX, examples.bat for Windows).
These make use of the split.py script, which is otherwise unnecessary.
(The Windows example also shows that simply echoing your manfid/serial
combo to cuber.py -the way one does in Linux/OSX- won't work due to
the carriage-return character introduced by the echo command.
You'll need to handcraft a file matching the '0x%02x%08xn' format...)
Another batch file py..bat is meant as an extra aid for Windows users
to avoid trouble with setting paths and such. You should be able to simply
download and install your preferred Python version.
Open a command shell (cmd.exe), navigate to wherever you extracted the
archives, and type 'py PYTHON-SCRIPT ARGS' to run the Python scripts.
(This handholding intentionally does NOT work for the upHDX script.)
Hopefully, someone will find these simple tools useful.
EDIT: To unlock your bootloader (<=.3.2.3.2), you'll need adb and fastboot.
On Linux, most distributions package these separately. Look for android-tools-{adb,fastboot} or some such.
For Windows, you can get these from the official Android SDK (which is a **large** download,
with a lot more tools you won't need, if you don't already use them, but it's safe).
Alternatively, there's a very legit-looking project here an XDA, with a much smaller
download, fast install, and exactly the tools you need. I haven't used either... (-;
The actual unlock procedure is described here and here.
EDIT#2: I added another script 'cublock.py' to make unlock.img generation super easy both on Windows and Linux.
MD5( tools.zip) = c17fc91344bd3b4b040129a79a39741f
EDIT#3: Fixed issues with older versions of certain tools on Debian 7.
MD5( tools.zip) = 4f93ab667fd61db26c83675ce0bd6d9f
EDIT#4: Fixed a bug when 'cuber.py' is used directly from the command line.
MD5(tools.zip) = 67b4a6d65aa2b0aa3500b122c8a25290View attachment 3210856
XDA:DevDB Information
HDXtools, Tool/Utility for the Amazon Kindle Fire HDX 7" & 8.9"
Contributors
draxie
Version Information
Status: Alpha
Created 2015-03-13
Last Updated 2015-03-13
Thank for your works.
Can I use upHDX to remove bootloader, recovery from 4.5.3 and flash via TWRP?
Thanks
tuanda82 said:
Thank for your works.
Can I use upHDX to remove bootloader, recovery from 4.5.3 and flash via TWRP?
Thanks
Click to expand...
Click to collapse
Let's hope so. That's what I did, in any case.
I'm an adventurer; so, I ran './upHDX fw update-kindle-14.4.5.3_user_453011120.bin',
pushed the resulting update-kindle-14.4.5.3_user_453011120-upHDXfw.zip to my HDX 8.9
and installed it with TWRP.
Worked for me, but I cannot provide any guarantees, unfortunately.
It may be wise to omit 'fw', and doublecheck that you're happy with the contents of the
updater-script in the newly generated archive.
AND, -of course- make sure your bootloader version is at most .3.2.3.2!!!
draxie said:
Let's hope so. That's what I did, in any case.
I'm an adventurer; so, I ran './upHDX fw update-kindle-14.4.5.3_user_453011120.bin',
pushed the resulting update-kindle-14.4.5.3_user_453011120-upHDXfw.zip to my HDX 8.9
and installed it with TWRP.
Worked for me, but I cannot provide any guarantees, unfortunately.
It may be wise to omit 'fw', and doublecheck that you're happy with the contents of the
updater-script in the newly generated archive.
AND, -of course- make sure your bootloader version is at most .3.2.3.2!!!
Click to expand...
Click to collapse
Thanks. But your upHDX scripts is for linux user only. I am on Windows .
If you have time could you upload your xxxx_14.4.5.3_xxxx.zip? Thanks
draxie said:
The attached archive includes 3 tools for those of you with .3.2.3.2 (or earlier) bootloaders.
Since other tools (and earlier version of these very tools) are available and working well,
this is mostly meant as an entry to an imaginary beauty contest. (JOKING!!!)
cuber.py
a generic gmpy2-free reimplementation of @vortox's signature.py
use this to generate your unlock.img
cuboot.py (uses cuber.py)
a Python-only reimplementation of @vortox's cuber
includes fixes to the kernel command-line and the device-tree
use this to convert a standard Amazon boot.img (>=.4.x.x)
upHDX (uses cuboot.py)
bash script to repack Amazon updates for TWRP
could be DANGEROUS, use with care
tested on Apollo for both 14.4.5.2 and 14.4.5.3
my unit is fully 14.4.5.3 now, except for aboot (which is 3.2.3.2)
should work on Thor as well
Those with bootloader .3.2.6 and lower can downgrade to .3.1.0
and upgrade the bootloader to the latest vulnerable version .3.2.3.2.
Those with .3.2.7 and higher appear to be out of luck with forged signatures, but I hear there's progress on rooting .4.5.2.
The python scripts have been tested on the following OS / Python combinations:
Windows: 2.7.9 and 3.4.3
Linux: 2.7.9 and 3.3.4
OSX: 2.6.? (cannot quite remember)
In addition to the tools themselves, I also included "educational" examples
(examples.sh for Linux/OSX, examples.bat for Windows).
These make use of the split.py script, which is otherwise unnecessary.
(The Windows example also shows that simply echoing your manfid/serial
combo to cuber.py -the way one does in Linux/OSX- won't work due to
the carriage-return character introduced by the echo command.
You'll need to handcraft a file matching the '0x%02x%08x\n' format...)
Another batch file py..bat is meant as an extra aid for Windows users
to avoid trouble with setting paths and such. You should be able to simply
download and install your preferred Python version.
Open a command shell (cmd.exe), navigate to wherever you extracted the
archives, and type 'py PYTHON-SCRIPT ARGS' to run the Python scripts.
(This handholding intentionally does NOT work for the upHDX script.)
Hopefully, someone will find these simple tools useful.
EDIT: To unlock your bootloader (<=.3.2.3.2), you'll need adb and fastboot.
On Linux, most distributions package these separately. Look for android-tools-{adb,fastboot} or some such.
For Windows, you can get these from the official Android SDK (which is a **large** download,
with a lot more tools you won't need, if you don't already use them, but it's safe).
Alternatively, there's a very legit-looking project here an XDA, with a much smaller
download, fast install, and exactly the tools you need. I haven't used either... (-;
The actual unlock procedure is described here and here.
EDIT#2: I added another script 'cublock.py' to make unlock.img generation super easy both on Windows and Linux.
MD5( tools.zip) = c17fc91344bd3b4b040129a79a39741f
Click to expand...
Click to collapse
Thanks a lot for the good work but id like to let tell you that it will be great if you can explain all the entire work in layman's terms because there would be many people having hundreds of questions and concerns.
Just an advice if you feel worthy... No disrespect intended...
I would like it in layman terms...
And how to do it on Windows. This seems like confusion for me. I have no idea where to start.
I did it all in windows 8.1 64 bit edition.
With help from this post:
http://forum.xda-developers.com/showpost.php?p=58897784&postcount=67
get Python 2.7 for windows and install it >>https://www.python.org/download/releases/2.7/
btw I installed the 64 bit edition for both
get GMPY2 for Python 2.7 https://code.google.com/p/gmpy/downloads/list
Follow the post for step by step. I encountered some trouble with fast boot driver, I had to remove the driver and install a generic one I selected from windows then I manually installed it. Ran the fast boot command to unlock and I was unlocked. a lot easier than it looks.
Reckerr said:
I would like it in layman terms...
And how to do it on Windows. This seems like confusion for me. I have no idea where to start.
Click to expand...
Click to collapse
Appreciate it. Will attempt Saturday after a read through.
Works on Windows...
tuanda82 said:
Thanks. But your upHDX scripts is for linux user only. I am on Windows .
If you have time could you upload your xxxx_14.4.5.3_xxxx.zip? Thanks
Click to expand...
Click to collapse
Actually, I tested upHDX in Windows using Cygwin.
I had to select zip and unzip in the Archive group and python in the Python group
in the installer to get all the dependencies in place, and the only issue I faced was a few filename collisions
in the /system/media/audio/ringtones folder (case-sensitivity problem).
Code:
[COLOR="Lime"]>[/COLOR] diff -ru cygwin/ linux/
Only in linux/system/media/audio/ringtones: ANDROMEDA.ogg
Only in linux/system/media/audio/ringtones: CANISMAJOR.ogg
Only in linux/system/media/audio/ringtones: Hydra.ogg
Only in linux/system/media/audio/ringtones: PERSEUS.ogg
Only in linux/system/media/audio/ringtones: URSAMINOR.ogg
These could just be copied from the original update-*.bin after installation.
Reckerr said:
I would like it in layman terms...
And how to do it on Windows. This seems like confusion for me. I have no idea where to start.
Click to expand...
Click to collapse
If you could spell out what you mean by 'it', I might be able to help.
yujikaido79 said:
I did it all in windows 8.1 64 bit edition.
With help from this post:
http://forum.xda-developers.com/showpost.php?p=58897784&postcount=67
get Python 2.7 for windows and install it >>https://www.python.org/download/releases/2.7/
btw I installed the 64 bit edition for both
get GMPY2 for Python 2.7 https://code.google.com/p/gmpy/downloads/list
Follow the post for step by step. I encountered some trouble with fast boot driver, I had to remove the driver and install a generic one I selected from windows then I manually installed it. Ran the fast boot command to unlock and I was unlocked. a lot easier than it looks.
Click to expand...
Click to collapse
Of course, if you want to make it more difficult for yourself,
you can use the older version of my tool as well.
The new one is not limited to Python 2.7, but works on both current Python versions;
and does NOT require GMPY2.
Also, if you are looking to unlock your bootloader, the 'cublock.py' script is your friend.
You just pass in the manfid and serial (separately; no need to fuse them).
Whether you choose to install Python standalone or as part of Cygwin is up to you.
The latter also includes 'bash' and lets you convert the Amazon update to a TWRP-friendly ZIP.
draxie said:
Of course, if you want to make it more difficult for yourself, you can use the older version of ny tool as well.
The new one is not limited to Python 2.7, but works on both current Python versions; and does NOT require GMPY2.
Also, if you are looking to unlock your bootloader, the 'unlock.py' script is your friend.
You just pass in the manfid and serial (separately; no need to fuse them).
Whether you choose to install Python standalone or as part of Cygwin is up to you.
The latter also includes 'bash' and lets you convert the Amazon update to a TWRP-friendly ZIP.
Click to expand...
Click to collapse
I have Windows 7 and Nexus 2.0.5 with bootloader from http://forum.xda-developers.com/kin...p-flashable-3-2-3-bootloader-upgrade-t3025504 installed Python 2.7 and the adb and fastboot and driver package from post 1
Using
adb shell
cat /sys/block/mmcblk0/device/manfid
cat /sys/block/mmcblk0/device/serial
And unlock.py and then
adb reboot-bootloader
And
Fastboot -i 0x1949 devices
fastboot -i 0x1949 flash unlock <unlock file>
fastboot -i 0x1949 reboot
IT was very easy, I only had some driver problems in fastboot mode
Uphdx don't work on debian 7
Bruder Torgen said:
I have Windows 7 and Nexus 2.0.5 with bootloader from http://forum.xda-developers.com/kin...p-flashable-3-2-3-bootloader-upgrade-t3025504 installed Python 2.7 and the adb and fastboot and driver package from post 1
Using
adb shell
cat /sys/block/mmcblk0/device/manfid
cat /sys/block/mmcblk0/device/serial
And unlock.py and then
adb reboot-bootloader
And
Fastboot -i 0x1949 devices
fastboot -i 0x1949 flash unlock <unlock file>
fastboot -i 0x1949 reboot
IT was very easy, I only had some driver problems in fastboot mode
Click to expand...
Click to collapse
FYI - followed this process on an identical environment with identical results. Struggled a bit more with Windows drivers; if you're having trouble this might help (posts 8-10).
im running this version 13.3.0.2 and im a newbe with kindle what should I do
benyo8990 said:
im running this version 13.3.0.2 and im a newbe with kindle what should I do
Click to expand...
Click to collapse
Welcome to the HDX forums. How to proceed depends on what you want to accomplish. Read through the various threads to see what is available and the effort required. If your goal is to root and/or install custom roms you MUST disconnect from WiFi as Amazon will attempt to upgrade your tablet to the lastest Fire OS. Should that happen your options will be severely limited.
Two words of caution:
1) Kindles are not like other devices. Tough to tame and easy to brick. If you approach modding with a casual attitude you'll probably end up with a non-recoverable brick. READ, READ, READ before doing anything. Ask questions when you are ready.
2) There are no tidy fail-safe tutorials for the HDX. There is work and risk involved. You have to do your homework first. No one is going to hold your hand (sorry for the lecture - just trying to set expectations early).
More info please!
dpeddi said:
Uphdx don't work on debian 7
Click to expand...
Click to collapse
Given that it worked for me even in Cygwin on Windows 7, this sounds odd.
Nevertheless, I'd appreciate more info on how it fails (and which flavor of Debian 7
you are using; so, that I have a chance to reproduce your issue).
UPDATE: Nevermind. I fired up a VM with Debian 7.8.0-amd64-standard,
and found out for myself. Apparently, 'df' in 'coreutils 8.13' used here
doesn't support the '--output' option; AND, python 2.7.3 is more strict
about the input types to 'unpack'. I fixed these and the script worked.
I'll post the new version in a second.
DF --optional not supported, $m seems to not be set
Thank you for posting this awesome tool. I am running 13.4.5.2 with a twrp recovery and the most recent available (without breaking twrp) kernel.
My question is, if worst case scenario happens and I try to use cygwin to upHDX, it does not work, but I think it did, and I install a partially working update, am I bricked? Or, will it just write over my kernel and recovery with no hope of going back. As I type this, I am thinking the answer is, both are possible, but thought I would ask before breaking things.
Sent from my KFTHWI using Tapatalk
[Edit] If you know what you are doing, this script is very helpful. I especially enjoy how it explains everything it does as it does it. So, you can see the files it changes. I used cygwin and it worked perfectly. If you understand the Unix command tools, it is a piece of cake. I do not mean to belittle the risk involved, it is significant, however, if you read what is happening, and know this worked, and can be assured there is no issue with your recovery, you can still roll back if something goes wrong. Do not take this comment as minimal risk, the risk is substantial, and you need to wipe to go back. One of my devices did not take the update well (My fault), and, I had to go back. These devices do not handle wipes well. So, the moral of the story.
-This is an excellent and versatile tool,
-There is significant risk
-If you do your research, follow directions, and meet the requirements, you can get success. Have your cake and eat it too on your terms!!
-With this tool, I have the most recent update, root, and twrp (Amazon apps work too).
Thanks again for the tools.
[/Edit]
lekofraggle said:
My question is, if worst case scenario happens and I try to use cygwin to upHDX, it does not work, but I think it did, and I install a partially working update, am I bricked? Or, will it just write over my kernel and recovery with no hope of going back. As I type this, I am thinking the answer is, both are possible, but thought I would ask before breaking things.
Click to expand...
Click to collapse
I saw you managed fine, but just in case anybody else wonders,
the script will bail at the first sign of error and you'll know it.
Of course, this won't guarantee that things cannot go wrong,
but minimizes the chances that they go unnoticed.
NOTE, HOWEVER that:
This has only been tested on 4.5.2 and 4.5.3; and, I would strongly recommend against blindly running it on newer releases (as the pattern matching that's being relied upon for what to throw away --including the anti-rollback fuse stuff-- might easily get broken with relatively minor changes.
A good sanity check is to unzip both the original update and the newly created "sanitized" version, and compare them (e.g. via a recursive diff) to doublecheck if the changes are sensible.

SO... This happened... Secure Boot Error Code 1003 MODIFIED!!!

So, I wanted to go back to stock, after trying multiple steps listed here in XDA-dev, and multiple youtube videos and webpages. I will list the erros bellow :
LgUP - "unknown device"... I been having issues with this software since I first attempt to run it. I tried on 2 different computers and have the same issue. Installed the DLL first (like many suggested ) then LGUP and nothing
Flashtools14 - I get the .kdz and attempt to do either "normal" or "CSE" . after comes another window, stating the progress, do not disconnect the phone .. blah blah. After going thru that it stops at 9 % and nothing happens.
After couple of weeks, I thought that if Relocking the bootloader i would be able to go into the "factory Reset" with out booting from TWRP and going back to stock..*stupid move*, and so I did... And here we are with error 1003 MODIFIED
I been looking for answers in order to fix this issue, but they go to the same path... using LGUP or FLASHtools in which both dont work with me
I have this phone
LG G4 H811 Tmobile
Now im trying to see if i can conver a KDZ into a TOT since that process I also know.
If somebody have another method please let me know!
I cant go into recovery since I keep getting the error. pretty much I have a paper weight.
An3ru said:
So, I wanted to go back to stock, after trying multiple steps listed here in XDA-dev, and multiple youtube videos and webpages. I will list the erros bellow :
LgUP - "unknown device"... I been having issues with this software since I first attempt to run it. I tried on 2 different computers and have the same issue. Installed the DLL first (like many suggested ) then LGUP and nothing
Flashtools14 - I get the .kdz and attempt to do either "normal" or "CSE" . after comes another window, stating the progress, do not disconnect the phone .. blah blah. After going thru that it stops at 9 % and nothing happens.
After couple of weeks, I thought that if Relocking the bootloader i would be able to go into the "factory Reset" with out booting from TWRP and going back to stock..*stupid move*, and so I did... And here we are with error 1003 MODIFIED
I been looking for answers in order to fix this issue, but they go to the same path... using LGUP or FLASHtools in which both dont work with me
I have this phone
LG G4 H811 Tmobile
Now im trying to see if i can conver a KDZ into a TOT since that process I also know.
If somebody have another method please let me know!
I cant go into recovery since I keep getting the error. pretty much I have a paper weight.
Click to expand...
Click to collapse
can you try this file place in c: programfiles /lge/lgup/model
ther error you got am not sure what it is this is for LGUP to recognize your phone.
raptorddd said:
can you try this file place in c: programfiles /lge/lgup/model
ther error you got am not sure what it is this is for LGUP to recognize your phone.
Click to expand...
Click to collapse
Hey Raptorddd
we read each other again, i did put those files in the C:/programFiles(x86)/LGelectronics/LGUP/model
Fire up LGUP and still have the same issue Model " uknonw " COM Ports [ COM41, GENESIS]
An3ru said:
Hey Raptorddd
we read each other again, i did put those files in the C:/programFiles(x86)/LGelectronics/LGUP/model
Fire up LGUP and still have the same issue Model " uknonw " COM Ports [ COM41, GENESIS]
Click to expand...
Click to collapse
have done a search with that specific error see if someone fix it. ?
raptorddd said:
have done a search with that specific error see if someone fix it. ?
Click to expand...
Click to collapse
Wich error you mean, the one in LGUP or The modified 1003?, Yes i have done research on both errors, but nothing seems to work.
An3ru said:
Wich error you mean, the one in LGUP or The modified 1003?, Yes i have done research on both errors, but nothing seems to work.
Click to expand...
Click to collapse
sorry i have no idea. maybe pos in thread go back to stock.
So if I understood you correctly you still have download mode?
Then it can be fixed.
If you want I can guide you through..
For this you need any Linux or best would be if just using FWUL ( http://tinyurl.com/FWULatXDA ).
I recommend to use the persistent mode version so your settings and installations survive a reboot / shutdown.
instructions:
Boot FWUL, choose language & login
Download the KDZ file you want to flash (we need to know the path later e.g. /home/android/Downloads/)
Open the folder LG
Connect device in download mode to the PC
Double click "LG laf NG" icon
Type in the new opened terminal:
sudo python2 auth.py
[*]sudo python2 partitions.py --list
If this lists your partitions then we can proceed with flashing.
Download my brand new kdz manager tool into FWUL: (right click and save as)
When you are not using the persistent mode of FWUL: plug in a big USB stick (e.g. 32 GB or more) into FWUL and extract the attached file there
When you are using the persistent mode of FWUL: just extract it in your download folder
You need to know the full path so best is copying the path from the file manager (e.g. /home/android/Downloads/ ) or leave the file manager open there
Open another terminal (black little icon in the panel)
cd and directly behind this paste the path you copied (e.g. cd /home/android/Downloads/ )
press ENTER
bash kdzmanager.sh -x FILLINFULLPATH-TO-DOWNLOADED-KDZ
(e.g. bash kdzmanager.sh -x /home/android/Downloads/h811blablubb.kdz)
once finished type:
bash kdzmanager.sh --test --flash extracteddz/
(just like this as "extracteddz" is the path generated by the kdzmanager)
This will just test flashing and not actually flash. Let me know the results of this (copy & paste output)
if you can't wait the next step would be actually flashing ofc:
WARNING: by default the kdzmanager will not overwrite userdata (which would be like a factory reset) and I would recommend to leave it out always and better choose the LG factory reset menu (after flashing completed) if required. If you still want to flash it use --with-userdata as a parameter (can take a loooong time then btw).
bash kdzmanager.sh --flash extracteddz/
sfX
Sent from my LG-H815 using XDA Labs
steadfasterX said:
So if I understood you correctly you still have download mode?
Then it can be fixed.
If you want I can guide you through..
For this you need Linux or best would be if to just use FWUL ( http://tinyurl.com/FWULatXDA ). I recommend to use the persistent mode version so your settings and installations survive a reboot / shutdown.
First instructions:
Boot FWUL, choose language & login
Download the KDZ file you want to flash
Open the folder LG
Connect device in download mode to the PC
Double click "LG laf NG" icon
Type in the new opened terminal:
sudo python2 auth.py
sudo python2 partitions.py --list
If this lists your partitions then we can proceed with the flashing.
I have to go to now but will go on tomorrow with the rest of the instructions if you want to go this way..
sfX
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Sure man i will do this and try to instal linux or go into your guide. One questions, which version of linux i need !?. I did a quick read on your post, is quite alot information to take, but i will try it!!!
Edit. I was able to download virtual box with extensions. Plug in my lg g4 and make sure that it read it. Double click on LG laf (auth) - * there is no LG laf NG* - termina opens, open new terminal type first command, ask for password - password is different than the ones mentioned in the OP - error : Python2: cant open file 'auth.py' : [Errno 2]\ No such file or directory
An3ru said:
Sure man i will do this and try to instal linux or go into your guide. One questions, which version of linux i need !?. I did a quick read on your post, is quite alot information to take, but i will try it!!!
Edit. I was able to download virtual box with extensions. Plug in my lg g4 and make sure that it read it. Double click on LG laf (auth) - * there is no LG laf NG* - termina opens, open new terminal type first command, ask for password - password is different than the ones mentioned in the OP - error : Python2: cant open file 'auth.py' : [Errno 2]\ No such file or directory
Click to expand...
Click to collapse
use his FWUL dont use linux use that one he provided. also please hit the thanks buttonto my friend steadfsterx.. on lower part right hand side..:good:
raptorddd said:
use his FWUL dont use linux use that one he provided. also please hit the thanks buttonto my friend steadfsterx.. on lower part right hand side..:good:
Click to expand...
Click to collapse
Hey Raptorddd
yeah I use the program he suggest me, im just waiting on him, also thank you for the help! I appreciate it
An3ru said:
Hey Raptorddd
yeah I use the program he suggest me, im just waiting on him, also thank you for the help! I appreciate it
Click to expand...
Click to collapse
It seems you havent downloaded the latest FWUL version v2.0? In v1 there is no LG laf NG.. But we can use that FWUL version as well. it's just very very outdated
If you want to have the best FWUL experience use v2.0 and download the persistent mode version of FWUL (it's the ZIP) and read the FAQ to make the persistent mode available in VirtualBox!
This combo is fantastic
I come back in about 3 hours to complete the guide...
sfX
Sent from my LG-H815 using XDA Labs
steadfasterX said:
It seems you havent downloaded the latest FWUL version v2.0? In v1 there is no LG laf NG.. But we can use that FWUL version as well. it's just very very outdated
If you want to have the best FWUL experience use v2.0 and download the persistent mode version of FWUL (it's the ZIP) and read the FAQ to make the persistent mode available in VirtualBox!
This combo is fantastic
I come back in about 3 hours to complete the guide...
sfX
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Oh yeah, the main download server was a lil confusing but i was able to download it, i will be out. But i will be reading the FAQ and the new set of instructions!!!!
An3ru said:
Oh yeah, the main download server was a lil confusing but i was able to download it, i will be out. But i will be reading the FAQ and the new set of instructions!!!!
Click to expand...
Click to collapse
sorry for any confusion but thx for reporting. I have updated the OP to point to the new versions more clearly.
will come back asap
OK here you go: https://forum.xda-developers.com/showpost.php?p=73756863&postcount=7
let me know how it goes
steadfasterX said:
So if I understood you correctly you still have download mode?
Then it can be fixed.
If you want I can guide you through..
For this you need any Linux or best would be if just using FWUL ( http://tinyurl.com/FWULatXDA ).
I recommend to use the persistent mode version so your settings and installations survive a reboot / shutdown.
instructions:
Boot FWUL, choose language & login
Download the KDZ file you want to flash (we need to know the path later e.g. /home/android/Downloads/)
Open the folder LG
Connect device in download mode to the PC
Double click "LG laf NG" icon
Type in the new opened terminal:
sudo python2 auth.py
[*]sudo python2 partitions.py --list
If this lists your partitions then we can proceed with flashing.
Download my brand new kdz manager tool into FWUL: (right click and save as)
When you are not using the persistent mode of FWUL: plug in a big USB stick (e.g. 32 GB or more) into FWUL and extract the attached file there
When you are using the persistent mode of FWUL: just extract it in your download folder
You need to know the full path so best is copying the path from the file manager (e.g. /home/android/Downloads/ ) or leave the file manager open there
Open another terminal (black little icon in the panel)
cd and directly behind this paste the path you copied (e.g. cd /home/android/Downloads/ )
press ENTER
bash kdzmanager.sh -x FILLINFULLPATH-TO-DOWNLOADED-KDZ
(e.g. bash kdzextract.sh -x /home/android/Downloads/h811blablubb.kdz)
once finished type:
bash kdzmanager.sh --test --flash extracteddz/
(just like this as "extracteddz" is the path generated by the kdzmanager)
This will just test flashing and not actually flash. Let me know the results of this (copy & paste output)
if you can't wait the next step would be actually flashing ofc:
WARNING: by default the kdzmanager will not overwrite userdata (which would be like a factory reset) and I would recommend to leave it out always and better choose the LG factory reset menu (after flashing completed) if required. If you still want to flash it use --with-userdata as a parameter (can take a loooong time then btw).
bash kdzmanager.sh --flash extracteddz/
sfX
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
Hey steadfasterX, I download version 2 of the FWUL and still have the same error. as Sudo not found. Am I doing something wrong?! o.o
An3ru said:
Hey steadfasterX, I download version 2 of the FWUL and still have the same error. as Sudo not found. Am I doing something wrong?! o.o
Click to expand...
Click to collapse
you double clicked "LG laf NG" icon ? in this terminal u have to type the auth command
consider to come into IRC instead (channel carbon-user on freenode)
or just by clicking this link: http://webchat.freenode.net/?channels=Carbon-user
sfX
Saw something a few posts back about virtualbox or vmware...
FWIW, Historically, virtualized Linux Guests don't do so well with USB. I've always had to install it natively or use a LiveUSB distro with persistence.
barcodelinux said:
Saw something a few posts back about virtualbox or vmware...
FWIW, Historically, virtualized Linux Guests don't do so well with USB. I've always had to install it natively or use a LiveUSB distro with persistence.
Click to expand...
Click to collapse
VirtualBox plus FWUL works like a charm.
Sent from my LG-H815 using XDA Labs
steadfasterX said:
Download my brand new kdz manager tool into FWUL: (right click and save as)
When you are not using the persistent mode of FWUL: plug in a big USB stick (e.g. 32 GB or more) into FWUL and extract the attached file there
When you are using the persistent mode of FWUL: just extract it in your download folder
You need to know the full path so best is copying the path from the file manager (e.g. /home/android/Downloads/ ) or leave the file manager open there
Open another terminal (black little icon in the panel)
cd and directly behind this paste the path you copied (e.g. cd /home/android/Downloads/ )
press ENTER
bash kdzmanager.sh -x FILLINFULLPATH-TO-DOWNLOADED-KDZ
(e.g. bash kdzmanager.sh -x /home/android/Downloads/h811blablubb.kdz)
once finished type:
bash kdzmanager.sh --test --flash extracteddz/
(just like this as "extracteddz" is the path generated by the kdzmanager)
This will just test flashing and not actually flash. Let me know the results of this (copy & paste output)
if you can't wait the next step would be actually flashing ofc:
Click to expand...
Click to collapse
Your tool is far better than this one because your tool has extracted many such partitions of LG G4 H811 20o KDZ which that tool didn't. E.g. PERSISTENT, DEVINFO, MODEMST1, MODEMST2, DRM etc.
rizkhan999 said:
Your tool is far better than this one because your tool has extracted many such partitions of LG G4 H811 20o KDZ which that tool didn't. E.g. PERSISTENT, DEVINFO, MODEMST1, MODEMST2, DRM etc.
Click to expand...
Click to collapse
yea thx!!
and just checkout my new signature
.
steadfasterX said:
yea thx!!
and just checkout my new signature
Click to expand...
Click to collapse
Well. Yet another PhD thesis :good:. There is one thing that I couldn't understand though. At one place you mentioned that Hint: not wiping userdata can occur in a bootloop while at the other place you said WARNING: by default the kdzmanager will not overwrite userdata. Does it mean that flashing can cause bootloop if kdzmanager is used with default options?
Secondly, does it also support TOTs as LGUP does?

Help flashing stock rom to Pixel 4 XL with Pixelbook?

Hello folks!
Its been a while since i posted here - i havent been flashing roms for an age (kids etc got in the way!)
Anyway, i've picked up a Pixel 4 XL, and it was running a custom ROM, i'm trying to move back to stock and have been able to follow all the guides i've found up to using the 'fastboot flashall' in shell.
The command works and delivers the
Bootloader Version...:
Baseband Version.....:
Serial Number........:
values, but then errors out with the following error "fastboot: error: ANDROID_PRODUCT_OUT not set"
I'm stumped what that means and how to fix. I'm doing all of this on my Pixelbook, and have updated fastboot and adb as per the initial steps for flashing.
Can anyone shed any light on what i still need to do to get flashall to work as expected?
Thanks in advance if you are able to help out!
ptm
Welcome Back
Could you post the exact command you are using for fastboot flash please? It sounds like fastboot is not finding the files to flash. Usually, depending on the configuration of the fastboot install, it's easier to place the firmware in the same directory as the fastboot binary.
Thanks! It turns out i've missed this place!
So the firmware files are all on the chromebook and I've used 'shell' to navigate to where I've unzipped. Here's the command line with the command i'm using: "[email protected] ~/Downloads/ota_file $ fastboot flashall"
Before trying a full flash, i was trying to sideload the OTA as per instructions here https://developers.google.com/android/ota#instructions but moving the file from my pixelbook to the 4XL fails at 47% every time.
So i reverted to a full flash as per these instructions - https://developers.google.com/android/images and that is where i'm coming a cropper with the 'not set' error.
Thanks for your help!
ktmom said:
Welcome Back
Could you post the exact command you are using for fastboot flash please? It sounds like fastboot is not finding the files to flash. Usually, depending on the configuration of the fastboot install, it's easier to place the firmware in the same directory as the fastboot binary.
Click to expand...
Click to collapse
I thinnk you may be merging several approaches.
You are using the full factory image downloaded from the https://developers.google.com/android/images page, right? Then, once downloaded, you are unzipping the file and cd into the new directory (from the unzip). The command then should be
Code:
./flash-all.sh
As far as the OTA install is concerned, you are using the command
Code:
adb sideload "ota_file.zip"
, and at 47%, what happens that it appears to fail? My memory on my P3XL is at that point it takes awhile.
If you are using a C to C switch to an A to C cable and try it. You'll want to remove the wipe from the flash-all before you flash the full image and it's the flash all you should be using to flash.
Yeah i think you're right - so now just concentrating on the Full Flash method shown on the Google Developers page, and yes doing it exactly as you'd described.
Ok - using
Code:
./flash-all.sh
now returns the error
Code:
bash: ./flash-all.sh: Permission denied
I have tried to prefix './flash-all.sh' with 'Fastboot' but no dice here either. Is that required at all?
ktmom said:
I thinnk you may be merging several approaches.
You are using the full factory image downloaded from the https://developers.google.com/android/images page, right? Then, once downloaded, you are unzipping the file and cd into the new directory (from the unzip). The command then should be
Code:
./flash-all.sh
As far as the OTA install is concerned, you are using the command
Code:
adb sideload "ota_file.zip"
, and at 47%, what happens that it appears to fail? My memory on my P3XL is at that point it takes awhile.
Click to expand...
Click to collapse
ptm said:
Yeah i think you're right - so now just concentrating on the Full Flash method shown on the Google Developers page, and yes doing it exactly as you'd described.
Ok - using
Code:
./flash-all.sh
now returns the error
Code:
bash: ./flash-all.sh: Permission denied
I have tried to prefix './flash-all.sh' with 'Fastboot' but no dice here either. Is that required at all?
Click to expand...
Click to collapse
You need to give the "flash-all.sh" script execution rights (that is why the permission denied error). Use this code:
Code:
chmod +x ./flash-all.sh
You may need super user/root rights:
Code:
sudo chmod +x ./flash-all.sh
The "flash-all.sh" script is a stand-alone script that sequentially flashes the entire factory package. As was mentioned in another repsonse in this thread, in cases where you want to update, but not lose your installed user apps and data, you would edit the script and remove the "-w" augment. In this case, you are returning to stock and you should perform the wipe (-w).
The dot slash (./) that preceeds the flash-all.sh tells the bash interpreter (what runs commands you give) that the file is right here, in this directory.
The flash-all.sh is a standalone script (series of written instructions) and calls fastboot from within it.
Thanks for sticking with me on this ktmom!
OK, i've used both
Code:
chmod +x ./flash-all.sh
and
Code:
sudo chmod +x ./flash-all.sh
but still getting the permission denied error when i launch ./flash-all.sh
I'll do a screencast vid walking through the entire process i'm following, so that you can see what i'm up too and in case it gives any further clues for a solution.
Thanks again!
ktmom said:
You need to give the "flash-all.sh" script execution rights (that is why the permission denied error). Use this code:
Code:
chmod +x ./flash-all.sh
You may need super user/root rights:
Code:
sudo chmod +x ./flash-all.sh
The "flash-all.sh" script is a stand-alone script that sequentially flashes the entire factory package. As was mentioned in another repsonse in this thread, in cases where you want to update, but not lose your installed user apps and data, you would edit the script and remove the "-w" augment. In this case, you are returning to stock and you should perform the wipe (-w).
The dot slash (./) that preceeds the flash-all.sh tells the bash interpreter (what runs commands you give) that the file is right here, in this directory.
The flash-all.sh is a standalone script (series of written instructions) and calls fastboot from within it.
Click to expand...
Click to collapse
@ptm, No worries, I'll do my best to help. I'm typing this on a chromebook that I also use to fastboot to a P3XL.
Edit 1:
Just to make sure:
1) The bootloader is unlocked?
2) "fastboot devices" returns the serial number of your device?
3) you are running ./flash-all.sh command as root or as the default user? In other words, the same way that fastboot devices returns the serial number. Either sudo fastboot devices or just fastboot devices.
4) if you enter the linux command: ls -al flash-all.sh do you get something like:
-rwxr-xr-x. 1 chronos chronos 957 Jul 18 2019 flash-all.sh
In this example -rwxr-xr-x is depicting the file permissions where there are three groupings; owner group everyone else. The first rwx means read, write and execute permissions for the file owner. Others in the same group and everyone else has read and execute permissions. Execute (x) is required in order for a script to run. If your file does not have three x so that all three groups have permission to execute it, then we need to revisit that.
Edit 2:
Another thought that could be affecting you is ADB and Fastboot are old. in your crosh shell, type:
Code:
[email protected] ~ $ adb --version
Android Debug Bridge version 1.0.41
Version 29.0.5-5949299
[email protected] ~ $ fastboot --version
fastboot version 29.0.5-5949299
Installed as /usr/local/bin/fastboot
If either returns a version older than the output above, then the easy way to update these is to use the script on Nathan Chance's Githuib. This might look a little overwhelming but it's pretty easy. I suggest you read the page, but the operative information is in section 4. Run the setup script:
To install, run
Code:
curl -s https://raw.githubusercontent.com/nathanchance/chromeos-adb-fastboot/master/install.sh | bash
in your shell prompt.
This script very nicely updates your ADB/Fastboot to the newest version which will be required for your P4XL
Are you guys sure you aren't making it too hard? You don't have to give any commands to install the full image. Download the full image and put it into an empty folder, go ahead and extract it in that folder. Create another new folder, Copy everything into it so you still have the full image in the first folder. Now download the tools and put those into a folder and extract them in that folder. Take the entire contents of that folder and add it to the folder you copied the extracted image into. What you should have now is one folder that still has the full extracted image, one that has the full extracted tools, and one that has both. If you have not already done so the phone should have debugging enabled and oem should be on. Go ahead and put it into bootloader mode and plug it in, type cmd in the path bar of the folder with both tools and image and check devices which will tell you if the tools can see the phone. If you get your serial the tools can see the phone. If you're going to wipe you can go ahead and click the flash-all and it will start the process, you do not give any commands. If you don't want to wipe the edit the flash-all to remove the-w, save it, and click on it. Again, no command is given, you just click and the flash-all does the rest.
Edit... And dont forget, A to C, not the provided C to C.
krabman said:
Are you guys sure you aren't making it too hard? You don't have to give any commands to install the full image. Download the full image and put it into an empty folder, go ahead and extract it in that folder. Create another new folder, Copy everything into it so you still have the full image in the first folder. Now download the tools and put those into a folder and extract them in that folder. Take the entire contents of that folder and add it to the folder you copied the extracted image into. What you should have now is one folder that still has the full extracted image, one that has the full extracted tools, and one that has both. If you have not already done so the phone should have debugging enabled and oem should be on. Go ahead and put it into bootloader mode and plug it in, type cmd in the path bar of the folder with both tools and image and check devices which will tell you if the tools can see the phone. If you get your serial the tools can see the phone. If you're going to wipe you can go ahead and click the flash-all and it will start the process, you do not give any commands. If you don't want to wipe the edit the flash-all to remove the-w, save it, and click on it. Again, no command is given, you just click and the flash-all does the rest.
Edit... And dont forget, A to C, not the provided C to C.
Click to expand...
Click to collapse
What Tools do you need to do this?
Same page as the images, scroll up from them and in the description of the process they have a link to the platform tools.
@krabman, Since this is using a chromebook, not a PC, things are flakier than normal. I just replicated the problems experienced by @ptm and some of it is due to old ADB/Fastboot as described in my previous post. Some is because ChromeOS made a change in an update that mounts nearly all of the partitions noexec, which means scripts can not execute and give the reported, "no permissions" error. There is a workaround since /usr/local is mounted executable. It's also possible to remount a partition with exec permissions.
@ptm, as the easiest route, I suggest making sure the ABD is current using the script I linked yesterday, and then going back to the OTA sideload method. I tanked my phone for a few hours yesterday trying to make fastboot get through the entire system image. I finally resorted to my full ubuntu install on my chromebook.
airmaxx23 said:
What Tools do you need to do this?
Click to expand...
Click to collapse
A general Fastboot/ADB tutorial is available here. If you are not using a chromebook, this thread's discussion will just add confusion.
If you are using a chromebook, then you need to enter a crosh shell, make sure adb and fastboot are updated as described in an earlier post and read the rest of the information I posted about the associated problems.
My understanding is the sh should flash on chrome with the latest tools as I described and you use the bat for PC. If the device is down he would have nothing to lose trying, if not I'd be leery of trying it since a partial flash will definitely result in a softie. Of course the possibility that I don't fully understand it may explain my puzzlement.
ktmom said:
A general Fastboot/ADB tutorial is available here. If you are not using a chromebook, this thread's discussion will just add confusion.
If you are using a chromebook, then you need to enter a crosh shell, make sure adb and fastboot are updated as described in an earlier post and read the rest of the information I posted about the associated problems.
Click to expand...
Click to collapse
Thanks, I know how to use ADB on the PC but I have a ChromeBook that I'd like to use as well. I already have it in Developer Mode.
I got it working, I just to run the script to update ADB and Fastboot.
airmaxx23 said:
Thanks, I know how to use ADB on the PC but I have a ChromeBook that I'd like to use as well. I already have it in Developer Mode.
When I open a Crosh Window, type shell, then adb devices my Pixel 4 XL shows up but I get: no permissions; see [http://developer.android.com/tools/device.html]
Click to expand...
Click to collapse
My bet is your ADB/fastboot are to old. Go back to post 9 and read the lower portion under edit2. You should also read forward from that point as there are additional issues that ChromeOS introduced with the noexec mounting of partitions. It will mean that without a workaround, you can not execute the flash-all.sh.
ktmom said:
My bet is your ADB/fastboot are to old. Go back to post 9 and read the lower portion under edit2. You should also read forward from that point as there are additional issues that ChromeOS introduced with the noexec mounting of partitions. It will mean that without a workaround, you can not execute the flash-all.sh.
Click to expand...
Click to collapse
Hey there,
SO i decided to try the OTA sideload method on a friends PC - i got the following response through CMD prompt
Code:
C:\Users\LYALL\Downloads>adb sideload ota-file.zip
Total xfer: 1.00x 1
However the phone is reporting a failure verifying the file signature and giving
Code:
E: Error code: 21
What do you think is causing that? I saw that Google has a new browser based flash tool to allow for AOSP builds to flash - would using that work better for me do you think?
ptm
ptm said:
Hey there,
SO i decided to try the OTA sideload method on a friends PC - i got the following response through CMD prompt
Code:
C:\Users\LYALL\Downloads>adb sideload ota-file.zip
Total xfer: 1.00x 1
However the phone is reporting a failure verifying the file signature and giving
Code:
E: Error code: 21
What do you think is causing that? I saw that Google has a new browser based flash tool to allow for AOSP builds to flash - would using that work better for me do you think?
ptm
Click to expand...
Click to collapse
Make sure you have downloaded the correct OTA and for crosshatch coral. Use the sha256 checksum provided in the download page and ensure the file is not corrupted. I check the integrity of the file before using it especially if I've moved it since the last verification.
You are rebooting to recovery (not rescue mode) and using the OTA sideload action from *within* recovery, before using the adb command, right?
The Google update and repair tool is an option.
ktmom said:
Make sure you have downloaded the correct OTA and for crosshatch. Use the sha256 checksum provided in the download page and ensure the file is not corrupted. I check the integrity of the file before using it especially if I've moved it since the last verification.
You are rebooting to recovery (not rescue mode) and using the OTA sideload action from *within* recovery, before using the adb command, right?
The Google update and repair tool is an option.
Click to expand...
Click to collapse
I think Pixel 4 XL is Coral, not Crosshatch.
I have downloaded the OTA file thats third from the bottom on this page (https://developers.google.com/android/ota) which is the rom number - 10.0.0 (QQ1B.200105.004, Jan 2020).
Yes, followed the instructions and booted to recovery, selected 'update from adb' from within recovery and then checked
Code:
adb devices
to ensure it showed 'sideload'. I then ran the command
Code:
adb sideload ota_file.zip
The transfer seemed to work fine, but then i got the error above showing on the device.
I cant seem to use the Google update and repair tool, as I'm in the UK and it says its not supported.
I can get it working with a VPN but the carrier i'm on doesnt show, although i do have the option of selecting 'other' as the carrier - I'm happy to give that a go, but wanted to get your thoughts on it first. Will selecting carrier as 'other' work ok for a UK based phone?
ptm

Categories

Resources