Database Users

[Q] Stock AU A500

I figured since getting a replacement A500 and updating to Acer_A500_1.139.04_COM_GEN1 I would update this post with the images.
System.img - http://www.fileserve.com/file/gvemmYd
Flexrom.img - http://www.fileserve.com/file/Suq5yBG
Boot.img - http://www.fileserve.com/file/sSjqpME
Hope this helps anyone.
Kernel Information: Linux localhost 2.6.36.3 #1 SMP PREEMPT Wed May 11 22:11:55 CST 2011 armv7l GNU/Linux

103 views and no-one is able to do it? I am sure there are quite a few Aussies on this forum. :-(

i would if i knew how

splinter6 said:
i would if i knew how
Click to expand...
Click to collapse
Here is your "knew how"... jejeje
You have to ROOT your A500 first... then use terminal emulator and type SU (this will give it Super User Access) then use the following commands:
dd if=/dev/block/mmcblk0p3 of=/sdcard/system.img
dd if=/dev/block/mmcblk0p6 of=/sdcard/flexrom.img
This will give you the actual system image (first command)
Second command gives you the partition where the update information is located.
Let me know if you need help rooting, its really easy, just remember to have your tablet in PORTRAIT not landscape or Gingerbreak will FORCE CLOSE!!!
Hope this helps... jejeje

I got a replacement A500 from JB HiFi. I will update to Acer_A500_1.139.04_COM_GEN1 then create a system.img.

This would be much appreciated! I'm in Australia, and having some issues too. Thanks again.

koprofile said:
This would be much appreciated! I'm in Australia, and having some issues too. Thanks again.
Click to expand...
Click to collapse
I'm at work today. Will hopefully get the system.img uploaded this evening, should take ~2 hours being 600MB and all. :-(
I'm not sure if the flexrom.img is needed though.

that would be appreciated as i have an issue of not being able to update after rooting and NO BACKUP

eliousneo said:
that would be appreciated as i have an issue of not being able to update after rooting and NO BACKUP
Click to expand...
Click to collapse
Here is the untouched Acer_A500_1.139.04_COM_GEN1 system.img.
http://www.fileserve.com/file/gvemmYd

thank you really appreciate it...
question 2 im a noob to all this so could you please let me know how ot install is
i know that it may sound like a dumb question but i have not got a clue.
I only rooted my a500 to be able to install apps to sd and that was a dissapointing move otherwise i think i may keep it stock from now on
thanking you in advance

eliousneo said:
thank you really appreciate it...
question 2 im a noob to all this so could you please let me know how ot install is
i know that it may sound like a dumb question but i have not got a clue.
Click to expand...
Click to collapse
You should be able to just copy the image onto your A500 and run the following as root: dd if=/dev/block/system-1.139.04.img of=/sdcard/mmcblk0p3
Be careful though, I honestly haven't tested the image but it should be fine.
Sent from my A500 using Tapatalk

so that means use command line and copy image onto SD card?
Sounds simple enough just gotta wait for 8 hours for download
Than again juzman very helpfull

Juzman said:
You should be able to just copy the image onto your A500 and run the following as root: dd if=/dev/block/system-1.139.04.img of=/sdcard/mmcblk0p3
Be careful though, I honestly haven't tested the image but it should be fine.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
We ALL should start using the MD5 checksum to rule out corrupted file size produced by online downloading

UnicornKaz said:
We ALL should start using the MD5 checksum to rule out corrupted file size produced by online downloading
Click to expand...
Click to collapse
I used the fsum utility on Windows and believe I created an MD5 checksum: 3A0AF183D5E582CBEA1D1F6BC7A61EA6

Will we need the flexrom as well when flashing this system image?
Also, this thread contains some original kernel modules: http://forum.xda-developers.com/showpost.php?p=13974214&postcount=62
Will the modules linked there be compatible with this current AU system image in the event of gps/wifi issues?
Thanks again!

Juzman said:
I used the fsum utility on Windows and believe I created an MD5 checksum: 3A0AF183D5E582CBEA1D1F6BC7A61EA6
Click to expand...
Click to collapse
Is that definitely the correct md5 checksum? I've downloaded the file twice and both times I get an md5 of 850d68aac56169b211a4913de7e4e8e9
Can anyone else confirm?

mapaz04 said:
Here is your "knew how"... jejeje
You have to ROOT your A500 first... then use terminal emulator and type SU (this will give it Super User Access) then use the following commands:
dd if=/dev/block/mmcblk0p3 of=/sdcard/system.img
dd if=/dev/block/mmcblk0p6 of=/sdcard/flexrom.img
This will give you the actual system image (first command)
Second command gives you the partition where the update information is located.
Let me know if you need help rooting, its really easy, just remember to have your tablet in PORTRAIT not landscape or Gingerbreak will FORCE CLOSE!!!
Hope this helps... jejeje
Click to expand...
Click to collapse
Can you say what terminal emulator to use or which is the best one to use?

urdaddi said:
Can you say what terminal emulator to use or which is the best one to use?
Click to expand...
Click to collapse
I used Better Terminal Emulator (with the extensions installed). Make sure after installing the extensions (after the prompt) to go into options, select root by default, then type exit (or CTRL-D) to close the terminal so it reinitializes with all the extensions (the icon on the taskbar must be gone). Afterwards do your stuff. After flashing the system.img the tablet might reboot (show the android boot logo) and cycle. Just power down holding the button long enough, and power back on, then flash the other img.

Hi Me again
dd if=/sdcard/system.img of=/dev/block/mmcblk0p3
I did the above thingy and it just extracted mmcblk0p3 into sdcard
How do i install it ??
i cant just run it so i presume there is some kind of command or something in terminal?

Is it possible to get the flexrom too?
Thanks

[HOWTO] (moto-fastboot) Flash a build on an unlocked Atrix

Well, after 4 days of having a nearly functional solution to loopback mount 2.3.4 on (locked) 1.8.3 using 2nd-init... my work is useless. But now we can all run 2.3.4, and whatever else we want!
http://forum.xda-developers.com/showthread.php?t=1136261
We don't even have to use RSD or .sbf files anymore. Why? Because our friends at Motorola also made enhancements to fastboot which allow you to flash >256mb partitions. This means we can overwrite large partitions, such as "system" (/system) and "webtop" (/osh), in addition to the blessed "boot" (kernel+ramdisk).
I've compiled it from the opensource.motorola.com (thanks Motorola!) for linux, it is attached to this post.
UPDATE: Looks like romracer came through for all you people who still use windows, the MinGW version is attached. Thanks romracer!
(After you thank romracer's post you can see this guide)
If the files below (for your 32 or 64 [default] bit system) don't work, you can compile from fastbootNfriends yourself with a string like:
Code:
gcc -o fastboot usb_linux.c util_linux.c fastboot.c protocol.c engine.c bootimg.c -lz ../libzipfile/zipfile.c ../libzipfile/centraldir.c -I../include -I../libzipfile -I../mkbootimg
UPDATE: Helpful users [email protected] and waqy. sent OSX binaries (compiled with extra flags "-framework CoreFoundation -framework Cocoa -framework IOKit") now attached.
Next post will tell you exactly how to use it to test out the HKTW 2.3.4 that was leaked a week ago which gave us all these great clues!
For me, when Atrix is connected ("lsusb | grep PCS" on Linux) it shows up as ID 22b8:708c if its in Fastboot mode.
WARNING
The leaked build from Hong Kong / Taiwan was probably not built for a device that is exactly like ours. Test phones can have different hardware. Don't expect everything to work, it's super-duper beta and since we've all only been unlocked 24hrs no one really knows how usable it is! Flash at your own risk... (PS you can 'Skip' Motoblur just by hitting 'Menu' during setup. It won't connect anyway...)
PPS. You can still use "dd" or something dangerous to overwrite your mmcblk0p11 and mmcblk0p12 with new builds, if you are unlocked, but at your own risk.

HKTW instructions!
So, using eval-'s awesome moto-fastboot from the post above this one, combined with the wonders of an unlocked bootloader, we may finally start to enjoy full roms/gingerbread!
To flash the HKTW files, make sure you unlocked your bootloader. Then, download the following:
http://www.megaupload.com/?d=12A2NF3O
http://www.megaupload.com/?d=J2VJSGZ7
http://www.megaupload.com/?d=Z3YKAHNM
Extract them to obtain the following files:
Code:
1c78b33d92f6b956bffbf4b668888ce4 atrix-2.3.4-hktw-boot.img
18effca0371c7dbb36ec54443e72414b atrix-2.3.4-hktw-system.img
b762c2a24a928da633c0f152d2fa7870 atrix-2.3.4-hktw-webtop.img
(Alternatively, you may use sbf_flash -x to extract these files directly from the SBF)
Now boot your phone into fastboot mode, and issue the following commands:
Code:
sudo ./moto-fastboot flash boot atrix-2.3.4-hktw-boot.img
sudo ./moto-fastboot flash system atrix-2.3.4-hktw-system.img
sudo ./moto-fastboot flash webtop atrix-2.3.4-hktw-webtop.img
sudo ./moto-fastboot -w
sudo ./moto-fastboot reboot
Now observe your jaws dropping as you start to explore this awesome build!
Thanks to eval, the2dcour & [mbm] !

Huge! 10char

Sweet!
Sent from my MB860 using XDA App

You guys rock, now eval hit the motorola forum with this
Sent from my MB860 using XDA Premium App

Oh my GOD! thank you a lot!!!
I'll check it out when I get home....

sweetttt, now we wait for devs to make easy deodex flashable update.zip of this build hehehe

Awesome, I'm going to try this now but I need root to use tibu! How do we root this now?

so flashing the HKTW files will get us to an atrix-compatible gingerbread? on an AT&T device?

More targets for webtop, I surmise?

Round of applause to all involved!

airbillion said:
Awesome, I'm going to try this now but I need root to use tibu! How do we root this now?
Click to expand...
Click to collapse
Root solution coming up... also requires fastboot but not the moto one, will work on any previous .sbf up to and including the leaked GB that kenneth has, as I used it to root him =) Watch for a new thread

_unknown said:
So, using eval-'s awesome moto-fastboot from the post above this one, combined with the wonders of an unlocked bootloader, we may finally start to enjoy full roms/gingerbread!
To flash the HKTW files, make sure you unlocked your bootloader. Then, download the following:
http://www.megaupload.com/?d=12A2NF3O
http://www.megaupload.com/?d=J2VJSGZ7
Extract them to obtain the following files:
Code:
1c78b33d92f6b956bffbf4b668888ce4 atrix-2.3.4-hktw-boot.img
18effca0371c7dbb36ec54443e72414b atrix-2.3.4-hktw-system.img
(Alternatively, you may use sbf_flash -x to extract these files directly from the SBF.)
Now boot your phone into fastboot mode, and issue the following commands:
Code:
sudo ./moto-fastboot flash boot atrix-2.3.4-hktw-boot.img
sudo ./moto-fastboot flash system atrix-2.3.4-hktw-system.img
sudo ./moto-fastboot flash -w
sudo ./moto-fastboot reboot
Now observe your jaws dropping as you start to explore this awesome build!
Thanks to eval, the2dcour & [mbm] !
Click to expand...
Click to collapse
i got an error .. it said atrix-2.3.4-hktw-system.img was to big

firefox3 said:
i got an error .. it said atrix-2.3.4-hktw-system.img was to big
Click to expand...
Click to collapse
Are you on windows? Are you using the moto-fastboot in the first post? If you are running linux and using the moto-fastboot from the first post you should have no issues. And of course, you unlocked the bootloader first.
Please read the first post carefully. Motorola modified fastboot. I compiled their mod for linux, if you have linux, you can flash your /system. Please get linux, or compile it for windows. I don't actually run windows so I haven't compiled it for windows.

eval- said:
Root solution coming up... also requires fastboot but not the moto one, will work on any previous .sbf up to and including the leaked GB that kenneth has, as I used it to root him =) Watch for a new thread
Click to expand...
Click to collapse
Hitting F5 every 5 seconds. Waiting for "the" thread.

eval- said:
Are you on windows? Are you using the moto-fastboot in the first post? If you are running linux and using the moto-fastboot from the first post you should have no issues. And of course, you unlocked the bootloader first.
Please read the first post carefully. Motorola modified fastboot. I compiled their mod for linux, if you have linux, you can flash your /system. Please get linux, or compile it for windows. I don't actually run windows so I haven't compiled it for windows.
Click to expand...
Click to collapse
i downloaded fastboot from kenneths website... wont that work?

eval- said:
Are you on windows? Are you using the moto-fastboot in the first post? If you are running linux and using the moto-fastboot from the first post you should have no issues. And of course, you unlocked the bootloader first.
Please read the first post carefully. Motorola modified fastboot. I compiled their mod for linux, if you have linux, you can flash your /system. Please get linux, or compile it for windows. I don't actually run windows so I haven't compiled it for windows.
Click to expand...
Click to collapse
i just deleted linux the other day .... should ii install it again ?

Trying moto-fastboot on ubuntu, but get:
./moto-fastboot: 3: Syntax error: "(" unexpected
???

eval- said:
Are you on windows? Are you using the moto-fastboot in the first post? If you are running linux and using the moto-fastboot from the first post you should have no issues. And of course, you unlocked the bootloader first.
Please read the first post carefully. Motorola modified fastboot. I compiled their mod for linux, if you have linux, you can flash your /system. Please get linux, or compile it for windows. I don't actually run windows so I haven't compiled it for windows.
Click to expand...
Click to collapse
firefox3 said:
i downloaded fastboot from kenneths website... wont that work?
Click to expand...
Click to collapse
Can you read?
firefox3 said:
i just deleted linux the other day .... should ii install it again ?
Click to expand...
Click to collapse
Yes. Or wait for someone to compile it for Windows.

nexxusty said:
Can you read?
Yes. Or wait for someone to compile it for Windows.
Click to expand...
Click to collapse
so the one he made is different from the one i used to unlock my bootloader?

Android L Nexus 7 2013 lte

Who can help me with porting Android L to Lte version
Becouse Nexus 4 have Android L .....flo and deb have minimal hardware difirence
Nexus 7 2013 (32Gb) LTE

I can't help but have been looking for a ROM. So far no luck. I have Android L on a Nexus 4. And I had 4.4.4 on a Xoom before the Nexus 7 LTE 2013 - which still officially is on 4.4.3. Weird.
Sent from my Nexus 4 using XDA Premium HD app

Logcat from deb with Android-L

outlawer-a said:
Logcat from deb with Android-L
Click to expand...
Click to collapse
Ahhh thank you just what I was looking for!

outlawer-a said:
Logcat from deb with Android-L
Click to expand...
Click to collapse
It looks great. Have you managed to run L on deb. Would you please provide the download link for this deb L rom?
Thanks

jayfallen said:
It looks great. Have you managed to run L on deb. Would you please provide the download link for this deb L rom?
Thanks
Click to expand...
Click to collapse
This is not romfor deb
This is flo rom installed pn deb
She doesn't boot
Nexus 7 2013 (32Gb) LTE

Ansanen said:
This is not romfor deb
This is flo rom installed pn deb
She doesn't boot
Nexus 7 2013 (32Gb) LTE
Click to expand...
Click to collapse
Yes, it's true. But this is debug. For now i can't find real problem, but it's info and it can help for run Android L.
jayfallen said:
It looks great. Have you managed to run L on deb. Would you please provide the download link for this deb L rom?
Thanks
Click to expand...
Click to collapse
Quick solution:
Flash original 4.4.3. Start it. Run startup config. IGNORE Google account. Allow USB debug. Approve computer fingerprint. (Optional: Change VM to art).
And now we use flo Android-L preview image. Unpack it. Unpack image-razor-lpv79.zip. We have some filesystem images: boot.img, system.img and etc. Let's flash it to our device. Reboot device into fastboot and run from directory where images.
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img
DON'T flash userdata. And reboot to system. Debug will work, but this method is dirty hack.
Full solution:(may be something missing, I can't check it for now)
For start - we need working deb with working USB debugging for our computer.(I use clear 4.4.3). Backup files for run adb:
Code:
adb pull /data/com.android.providers.settings/databases/settings.db
adb pull /data/misc/adb/adb_keys
And now we use flo Android-L preview image. Unpack it. Unpack image-razor-lpv79.zip. We have some filesystem images: boot.img, system.img and etc. Let's flash it to our device. Reboot device into fastboot and run from directory where images.
Code:
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash cache cache.img
fastboot flash userdata userdata.img
Reboot from fastboot to recovery(We need any custom recovery - i use TWRP 2.7.0.0). Click Mount select system and data(both must be selected).
Code:
adb shell
And on device:
Code:
cd data
mkdir data
mkdir data/com.android.providers.settings
mkdir data/com.android.providers.settings/databases
mkdir misc
mkdir misc/adb
vi /system/build.prop
Go to end of file and add on new line: persist.service.adb.enable=1
Code:
exit
Next upload adb enable and adb keyfiles(run from backup directory)
Code:
adb push settings.db /data/com.android.providers.settings/databases/
adb push adb_keys /data/misc/adb/
And start the android. Adb will work.

outlawer-a said:
Yes, it's true. But this is debug. For now i can't find real problem, but it's info and it can help for run Android L.
Quick solution:
DON'T flash userdata. And reboot to system. Debug will work, but this method is dirty hack.
Full solution:(may be something missing, I can't check it for now)
And start the android. Adb will work.
Click to expand...
Click to collapse
Thanks so much for the detailed solution. So now we could get debug info helping for DEB to run android L, but DEB won't boot anyway:crying:...

I got the best solution for deb users..............wait for it......wait for the official release!
Sent from my Nokia Lumia 920

outlawer-a said:
...I use ...
Click to expand...
Click to collapse
outlawer-a you said "I use" multiple times in your explanation. Are you working on a version for deb?
Does it make sense if I follow your steps and upload a logcat?

I gots a special treat for you guys!! Give me a couple more days though!

skiman10 said:
I gots a special treat for you guys!! Give me a couple more days though!
Click to expand...
Click to collapse
Quit teasing them about what we are doing, lol.
Guys, I need the June 26th preview binaries for deb for this to work. The newest ones are mostly incompatible with with the preview image so we need the second set of preview binaries if not the first set if possible that someone has. Someone must have downloaded them and have them sitting on their computer
Sent from my C6916

sykopompos said:
Quit teasing them about what we are doing, lol.
Guys, I need the June 26th preview binaries for deb for this to work. The newest ones are mostly incompatible with with the preview image so we need the second set of preview binaries if not the first set if possible that someone has. Someone must have downloaded them and have them sitting on their computer
Sent from my C6916
Click to expand...
Click to collapse
You mean the ones that were posted here? https://developers.google.com/android/nexus/blobs-preview

http://forum.xda-developers.com/showpost.php?p=54183670&postcount=648

Can we still have hope for that?

Can you flash the nonlte version on the lte one. And just loose lte functionality.
Sent from my Nexus 7 using XDA Premium HD app

logitechor said:
Can you flash the nonlte version on the lte one. And just loose lte functionality.
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
Actually no you can't but since I just finished up b5 for the n4, I can switch focus back to other devices now that I have a fully permissive sepolicy to get rid of a lot of headaches
Sent from my LG-D851

Thanks very much.
. my A0001 using XDA Free mobile app

Download link for Verizon 5.1 full image is here

Came across this today. I didn't upload it, so thank you to whoever did!
http://www.filefactory.com/file/1bh0acofnjf9/XT1254_QUARK_VERIZON_5.1_SU3TL-38_38_CFC.xml.zip
btw, file factory is slow so be patient.

downloading. Will check the build prop and re upload to file hosts that aren't capped at 50 kb/s in ~7hrs

Found this last night and downloaded overnight.
MEGA mirror: https://mega.co.nz/#!XABCUAKQ!XMAKu5xHTEl06-nXHXUp-R4HrI3NvqfP28pP7dYeXMY
SHA1: e569e17cefe7045c3424a8aae8c7dc0c51f51202
I was able to convert the system.img_sparsechunks by doing:
Code:
simg2img system.img_sparsechunk* system.img.raw
dd if=system.img.raw ibs=2048 skip=64 of=system.img
truncate -s 3539992576 system.img
I don't have enough posts to create a development thread (I'm a quiet dev) but I'll post the stock image + a rooted image once I get it all working.

firstEncounter said:
Found this last night and downloaded overnight.
MEGA mirror: https://mega.co.nz/#!XABCUAKQ!XMAKu5xHTEl06-nXHXUp-R4HrI3NvqfP28pP7dYeXMY
SHA1: e569e17cefe7045c3424a8aae8c7dc0c51f51202
I was able to convert the system.img_sparsechunks by doing:
Code:
simg2img system.img_sparsechunk* system.img.raw
dd if=system.img.raw ibs=2048 skip=64 of=system.img
truncate -s 3539992576 system.img
I don't have enough posts to create a development thread (I'm a quiet dev) but I'll post the stock image + a rooted image once I get it all working.
Click to expand...
Click to collapse
Just FYI - there is a utility that will convert the sparse chunks to a single image ext4 system.img:
http://forum.xda-developers.com/showthread.php?t=2749797
http://forum.xda-developers.com/showpost.php?p=61132614&postcount=3
But there is likely a header and a footer in the file as explained in that thread. Those have to be removed using a HEX Editor before you can flash it using mofo.exe. I wrote out the instructions on how to do that in that thread above.
Then you can root it using @btdownloads7's method found here:
http://forum.xda-developers.com/showpost.php?p=61132621&postcount=4
No need to reinvent the wheel if you have a device running TWRP you can just follow that method.
We have also learned that you have to delete the contents of both /data/dalvik-cache and /cache before you flash an image with Xposed for Lollipop baked into it. This has to do with the conversion from dalvik to ART.
If you are having trouble getting Xposed baked into your image, you can read about @mikeoswego's method here but check to make sure you are using the most recent Xposed files as there have been updates:
http://forum.xda-developers.com/showpost.php?p=61132732&postcount=7

Where does one go about getting these Verizon images? Is it something Verizon issues to the public? If not, how does one trust this image as not being tampered with?

crackd said:
Where does one go about getting these Verizon images? Is it something Verizon issues to the public? If not, how does one trust this image as not being tampered with?
Click to expand...
Click to collapse
They cannot be tampered with, or they cannot be flashed through the signature check, which is what verifies the integrity of the file as well. Mofo, however, does not verify signature for obvious reasons. Where this particular file popped up is hard to say.

http://i.imgur.com/x1OUS1H.png
Working on uploading the images now.

I cannot thank you for this enough. I removed the erase USERDATA line, and I'm hoping that fixes my issue. cross your fingers.

firstEncounter said:
http://i.imgur.com/x1OUS1H.png
Working on uploading the images now.
Click to expand...
Click to collapse
So it worked?

Koneesha said:
So it worked?
Click to expand...
Click to collapse
It did, and we retain the ability to downgrade to 4.4.

firstEncounter said:
It did, and we retain the ability to downgrade to 4.4.
Click to expand...
Click to collapse
how big is the ext4 file?

JulesJam said:
how big is the ext4 file?
Click to expand...
Click to collapse
3376MiB (3539992576 bytes)

firstEncounter said:
http://i.imgur.com/x1OUS1H.png
Working on uploading the images now.
Click to expand...
Click to collapse
Very cool!
I have an XT1225 so root was easy, glad to see Turbo guys can have some fun too.

firstEncounter said:
http://i.imgur.com/x1OUS1H.png
Working on uploading the images now.
Click to expand...
Click to collapse
How did you do it? If it is possible more in detail?

ilia3367 said:
How did you do it? If it is possible more in detail?
Click to expand...
Click to collapse
I posted some more information in this thread, once I get everything settled root-wise and the images uploaded, I'll make a more detailed guide.

firstEncounter said:
Found this last night and downloaded overnight.
MEGA mirror: https://mega.co.nz/#!XABCUAKQ!XMAKu5xHTEl06-nXHXUp-R4HrI3NvqfP28pP7dYeXMY
SHA1: e569e17cefe7045c3424a8aae8c7dc0c51f51202
I was able to convert the system.img_sparsechunks by doing:
Code:
simg2img system.img_sparsechunk* system.img.raw
dd if=system.img.raw ibs=2048 skip=64 of=system.img
truncate -s 3539992576 system.img
I don't have enough posts to create a development thread (I'm a quiet dev) but I'll post the stock image + a rooted image once I get it all working.
Click to expand...
Click to collapse
OMG thanks! i will add it to the main firmware thread!!!!

[Thor][Apollo] Unlocking bootloader with any firmware

Hello. At first, I did not invent anything new, just checked some my guess on a other motherboard. All thanks and credits to our great developers. As always, all at your own risk.
It does not work on the Fire HDX 8.9 (Saturn)!
All steps in this manual are not necessary but they are present for maximum safety. So I highly recommend do anything exactly in this way. Sorry my English as always =)
Update2 - actual method is https://forum.xda-developers.com/showpost.php?p=75284993&postcount=1006
Update: now you can use updated draxie's utility - http://forum.xda-developers.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014
Prerequisites for Installation
- Root
- Installed adb and fastboot drivers - official - https://drive.google.com/open?id=0B2twXJIOgv-UWWdwRl9TQS11b0k (if your system language not English, after fail navigate to "Program Files (x86)\Lab126\drivers" and run dpinst.exe /EL or switch to English =) for x64 need to disable driver signature verification before install ) also you can use pdanet drivers - http://forum.xda-developers.com/showpost.php?p=59268023&postcount=8
Manual:
1. Create unlock file following this instruction - https://forum.xda-developers.com/ki...r-firmware-t3463982/post70881555#post70881555
2. Flash old vulnarable aboot and cubed twrp (just in case). Check that all these commands executed without errors. If you'll get one - read second post below. If your firmware <=13(14)3.2.3.2 skip this step.
Download aboot and twrp for Thor (Kindle Fire HDX 7) https://drive.google.com/open?id=0B2twXJIOgv-UMGxXMUZPZTlZTUk or for Apollo (Kindle Fire HDX 8.9) - https://drive.google.com/open?id=0B2twXJIOgv-URzJDQkczNzRLaHM - and put this two files (twrp_cubed.img and aboot_vuln.mbn) into root of your kindle internal storage.
Run:
Code:
adb shell
su
dd if=/sdcard/twrp_cubed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/aboot_vuln.mbn of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Now you have working twrp recovery. It already works even without unlocked bootloader. You could boot into it by holding volUP during grey kindle logo. But no need to flash anything until unlock. At this point this is just emergency tool if something goes wrong =)
3. Flash unlock file.
Now, if you reboot, you will go straight into fastboot because of old aboot - newest boot.img can't load with it. If your firmware <13(14).4.1.1 you need run "adb reboot bootloader" to boot into fastboot.
Time to flash your unlock file.
Code:
fastboot -i 0x1949 flash unlock 0xmmssssssss.unlock
You must obtain "unlock code is correct".
Grats. You are perfect =)
You can flash:
CM13 - http://forum.xda-developers.com/kin...ment/rom-cm-13-kindle-hdx-2015-11-29-t3259732
CM 12.1 - http://forum.xda-developers.com/kin...ent/rom-cm-12-unofficial-apollo-thor-t3050199
Or stock repacked latest 4.5.5.2 rom - https://drive.google.com/open?id=0B2twXJIOgv-UVFFtN2RYNXNUZ0k (13.x - thor, 14.x - apollo)
Do not flash original stock firmwares.
Regards and thank to all - @dpeddi, @vortox, @draxie, @ggow, @Ralekdev, @jcase, @Hashcode
And greatest thanks for motherboard for my experiments to @MahmudS !

FAQ:​1. if your get "not such file or directory" after su in step 2 (this is SAFESTRAP related possibly)- try to use next commands:
Code:
adb shell
su
dd if=/storage/emulated/0/twrp_cubed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/storage/emulated/0/aboot_vuln.mbn of=/dev/block/platform/msm_sdcc.1/by-name/aboot
http://forum.xda-developers.com/showpost.php?p=68751981&postcount=35

I think you can use greatest @draxie tool - http://forum.xda-developers.com/kindle-fire-hdx/general/multi-platform-1-click-bootloader-t3241014 with doing step2 only. But it need to test. Anyway I highly recommend get your hw id's before any actions.

Daredevil
ONYXis said:
Code:
dd if=/sdcard/aboot_vuln.mbn of=/dev/block/platform/msm_sdcc.1/by-name/aboot
Click to expand...
Click to collapse
Great job! So, simply flashing the vulnerable bootloader "just works"...
Are you absolutely positive?
Although I've been expecting this all along
[but wouldn't dare trying, since the HDX is *still* my only tablet],
I'm wondering what the supposed "rollback protection" after 3.2.8 really covers.
Fixed issue (now hidden)
BTW: I get the exact same MD5 hash for both versions of 'aboot_vuln.mbn' (the two 'cubed_twrp.img' are different).
Code:
66b7df0db97c7c2905d1d61199c816a5 13-aboot_vuln.mbn
66b7df0db97c7c2905d1d61199c816a5 14-aboot_vuln.mbn
087e7125c48fcbebcc2f51a9c46379f2 13-twrp_cubed.img
c06799a4a8d48d9dd55aea002def1caf 14-twrp_cubed.img
H[66b7df0db97c7c2905d1d61199c816a5]=aboot-13.3.2.3.2_user_323001720.mbn
Please double-check to make sure Apollo users won't get fried.
You do say that not all steps are necessary. Can you advise if my thinking below sounds correct?
I'm considering adding this to 1-Click; that's why I'm asking.. (If I could also include a surefire way
to root the device beforehand, we'd be all set for a truly 1-Click experience from scratch, modulo
strange Windows behaviour. [if anybody still cares ;-P])
I suppose getting rid of the potentially dangerous anti-rollback-related files is good measure,
but if they had been making any difference, this method shouldn't really work, right?
So, this may not be needed at all.
I'm also thinking that flashing TWRP in the same step -although nice- is not strictly needed.
Would you agree?

Are you absolutely positive?
Click to expand...
Click to collapse
I tried this with two devices with two firmwares at each after rollback-upgrade proccess to be sure.
Although I've been expecting this
Click to expand...
Click to collapse
Same as I. Just need to be checked.
: I get the exact same MD5 hash for both versions of 'aboot_vuln.mbn
Click to expand...
Click to collapse
Strange, I use same aboots in this tool - http://forum.xda-developers.com/kin...-to-unbrick-kindle-fire-hdx-firmware-t3277197 =) need to fix=)
Re-uploaded aboot from 14.3.2.3.2 - 4A2BE8E374C8D1FCE8E6743AC2D09BB0
Thank you.
'm also thinking that flashing TWRP in the same step -although nice- is not strictly needed.
Click to expand...
Click to collapse
Of course. But... why not? and sometimes fastboot flash recovery at very first time don't work.
but if they had been making any difference, this method shouldn't really work, right?
So, this may not be needed at all.
Click to expand...
Click to collapse
This is need to check. I really do not like that factory_provision_tool.
But I agree that all magic is just dd'ing of old aboot.

ONYXis said:
I tried this with two devices with two firmwares at each after rollback-upgrade proccess to be sure.
Click to expand...
Click to collapse
Sounds good.
ONYXis said:
Same as I. Just need to be checked.
Click to expand...
Click to collapse
Indeed! And, that's quite a daring achievement. Big thanks for that!
ONYXis said:
Strange, I use same aboots in this tool - http://forum.xda-developers.com/kin...-to-unbrick-kindle-fire-hdx-firmware-t3277197 =) need to fix=)
Re-uploaded aboot from 14.3.2.3.2 - 4A2BE8E374C8D1FCE8E6743AC2D09BB0
Thank you.
Click to expand...
Click to collapse
I also verified this, just to be sure; and, chose to hide the issue in my post above.
H[4a2be8e374c8d1fce8e6743ac2d09bb0]=aboot-14.3.2.3.2_user_323001720.mbn
ONYXis said:
Of course. But... why not? and sometimes fastboot flash recovery at very first time don't work.
Click to expand...
Click to collapse
I'll see if including the TWRP images in 1-Click pushes the size of the ZIP over the XDA limit.
I suppose I could opt to fetch from the net if it doesn't, but then I need to enable networking for the VM.
ONYXis said:
This is need to check. I really do not like that factory_provision_tool.
But I agree that all magic is just dd'ing of old aboot.
Click to expand...
Click to collapse
Yes. Please check!

draxie said:
Yes. Please check!
Click to expand...
Click to collapse
Ok. So... Another motherboard with stock 3.2.3.2
Updated it through OTA to 3.2.5 > 4.1.1 > 4.5.2 > 4.5.4 > 4.5.5 > 4.5.5.1 > 4.5.5.2
Rollbacked to 3.2.8, updated to 4.5.5.1, Kingroot.
Code:
adb shell
su
dd if=/sdcard/aboot_vuln.mbn of=/dev/block/platform/msm_sdcc.1/by-name/aboot
reboot
Boot into fastboot. At this point need to have id's already!!!
Flash unlock, flash recovery, flash upHDXed 4.5.5.2 rom. Succesfully booted up. :fingers-crossed:
OP edited.

ONYXis said:
Rollbacked to 3.2.8, updated to 4.5.5.1, Kingroot.
Click to expand...
Click to collapse
I don't suppose this rollback is essential, is it?
It should work just as well to stop the update before the currently unrootable 4.5.5.2, right?
ONYXis said:
Flash unlock, flash recovery, flash upHDXed 4.5.5.2 rom. Succesfully booted up. :fingers-crossed:
Click to expand...
Click to collapse
Nice. I'll PM you soon with an updated 1-Click, for testing, if you don't mind.
(I cannot [and don't even want to] test this on my only tablet.)

draxie said:
I don't suppose this rollback is essential, is it?
Click to expand...
Click to collapse
just checked all variations.
I'll PM you soon with an updated 1-Click, for testing, if you don't mind.
Click to expand...
Click to collapse
Of course.

Can it work on hdx 8.9?

Although I have registered my 'thanks' on various posts it seems hollow to not explicitly recognize @ONYXis and @draxie for their tremendous contributions supporting this device both past and present. The ability to unlock virtually any rooted 3rd gen HDX is a true game changer that will revive interest in this discontinued gem that still competes nicely with contemporary offerings. Well done, gents!

wizard_mini said:
Can it work on hdx 8.9?
Click to expand...
Click to collapse
You mean Saturn? No, sorry.

Hi, i cant get the adb driver to work with my german Win 10 64bit
dpinst.exe /EL starts fine but throws an error while installing.
So i wanted to try the pdanet drivers but im not sure how to get my fire into fastboot mode ("- connect your kindle already waiting in fastboot mode with usb cable to pc").
Any help? :>

Maybe you need to disable driver signature verification before install. Google it.
fastboot -
Code:
adb reboot bootloader

ONYXis said:
Maybe you need to disable driver signature verification before install. Google it.
fastboot -
Code:
adb reboot bootloader
Click to expand...
Click to collapse
Thanks, that worked. Now i have the following problem when trying "python.exe cuberHDX.py 0xmmssssssss": (tried with 64 and 32bit Python + gmpy2, because that seems to be the problem sometimes)
File "cuberHDX.py", line 7, in <module>
from gmpy2 import iroot, mpz
ImportError: DLL load failed: %1 ist keine zulõssige Win32-Anwendung. [last part means not a valid win 32 application]
Thanks for your help!

It is python installation related problem, I really not familar with that. You could post your id's and I'll create and attach your unlock-file.

ONYXis said:
It is python installation related problem, I really not familar with that. You could post your id's and I'll create and attach your unlock-file.
Click to expand...
Click to collapse
0x000015
0x1022b00d
Thank you!

RambaaZambaa said:
0x000015
0x1022b00d
Thank you!
Click to expand...
Click to collapse
Welcome.
Need to unarchive.

ONYXis said:
Welcome.
Need to unarchive.
Click to expand...
Click to collapse
Next problem :silly:
As long as im not su i can cd to sdcard folder (or storage/sdcard0). But then i cant use the "dd if=/sdcard/twrp_cubed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery" command.
So when im SU the command fails and i also cant enter the sdcard folder (no such file or directory). Strange...

RambaaZambaa said:
Next problem :silly:
As long as im not su i can cd to sdcard folder (or storage/sdcard0). But then i cant use the "dd if=/sdcard/twrp_cubed.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery" command.
So when im SU the command fails and i also cant enter the sdcard folder (no such file or directory). Strange...
Click to expand...
Click to collapse
Sorry, really don't understand )
Pls, provide screenshot of cmd with your error.
And try to follow instructions directly.There is no any cd command.