Related
Hi all,
Could anyone please show me where are image files after building Android source code? I have successfully run "make" but have no idea where are image files that I can flash to my Nexus One.
You'll find them in the ./out folder
Hi cursordroid,
Could you please give me more detail? I am a newbie to Android. Although I know all the result of compilation is stored on ./out directory, I still can not figure out what and where are image files I need.
In particular,
Code:
~/mydroid$ find ./ -type f -name *.img
./out/target/product/generic/ramdisk.img
./out/target/product/generic/userdata.img
./out/target/product/generic/system.img
./out/target/product/generic/obj/PACKAGING/systemimage_unopt_intermediates/system.img
So, I think my specific questions are:
1. Can I flash above generic/*.img to my N1 using "fastboot flash partition_name partition.img"?
2. What is the difference between two system.img files?
3. Where is boot.img that I can use?
4. What is ramdisk.img?
By the way, I downloaded latest Android source code, i.e. Android 2.1_update1 so I suppose I do not have to provide any parameter when run "make" and the compiled images are flashable to N1. Correct me if I am wrong.
reddevil00 said:
Hi cursordroid,
Could you please give me more detail? I am a newbie to Android. Although I know all the result of compilation is stored on ./out directory, I still can not figure out what and where are image files I need.
In particular,
Code:
~/mydroid$ find ./ -type f -name *.img
./out/target/product/generic/ramdisk.img
./out/target/product/generic/userdata.img
./out/target/product/generic/system.img
./out/target/product/generic/obj/PACKAGING/systemimage_unopt_intermediates/system.img
Click to expand...
Click to collapse
Well...
ramdisk + kernel = boot.img
you might be interested in reading this topic: http://forum.xda-developers.com/showthread.php?t=551711
after that you should build an update.zip - signed file.
Good luck
You don't want to build Generic either.
If you run lunch, you should see an option of Passion for the N1. I don't believe AOSP has that yet. Cyanogen has made device configurations for the N1 available through his git repository, but I'd recommend just taking a look at Cyanogenmod and building from that. It is mostly AOSP with some extras thrown in. For additional help, you might want to stop in the IRC chatroom.
I build Cyanogenmod from source for my N1, so it is possible, but it does take a little massaging to make it work. I haven't looked at the straight AOSP for months.
I've decided to make all these new useful tools a lot easier to access.
How to use:
1. Download python (Version 2.7)
2. Download androidtools.zip from below
3. Unzip to wherever you'd like
4. You'll need to update tools the first time you run
5. Then just select which tool you'd like to use
Updates:
You can find the source HERE that shows all updates for all these apps.
The "Update Tools" option pulls straight from git, so you can have the latest version at all times!
NOTE: It will create a tools folder (which contains all of the tools) in the directory that androidtools.py is in.
Fore More info on what each tool does, visit their thread:
Boot Script Generator
(This has been added to the current kernel's source, so if you're using the latest nbh/zImage, it should work fine)
Key Mapper
NBH Editor
If you have any questions or problems with those programs, please post in those threads. If you have issues with the Android Tools program itself, please ask in this thread!
Thanks to l1q1d for the TONS of help over the past few weeks.
//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???
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
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.