Database Users

Flash recovery image Droid Eris How To

First of all thanks to Amon_RA for this. I had no part in creating this. I am just providing a how to flash it. There may be an eaiser way but this is what worked for me.
First let me say I am on a Mac. If you are on windows the adb commands should work fine but I can't say how to get adb working for you.
1. download flash_image Here Link updated 3/17/10
2. Open the terminal and copy and paste the following commands.
adb shell [hit enter]
su [hit enter]
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system [hit enter]
3. In a new terminal window (don't close the original one).
adb push flash_image /system/bin [hit enter]
exit [hit enter]
4. Now in the original terminal window
chmod 755 /system/bin/flash_image [hit enter]
5. Now exit all termainl windows and reboot your phone.
6. Download Amon_AR's recovery Here.
7. Mount your phones sd card and drop recovery-RA-eris-v1.6.2.img on to it and eject your phone.
8. Open the Terminal and copy and paste the following commands with the phone connected to your computer.
8. adb shell [hit enter]
9. su [hit enter]
10. flash_image recovery /sdcard/recovery-RA-eris-v1.6.2.img
11. To get into recovery turn off you phone and hold the Volume Up + Power until it boots into recovery.
That's it.
I made an automator script the help all of you having problems getting adb working. Make sure you have the android sdk downloaded and named android-sdk Put it in your home folder and then run this script. Let me know how it works for you.
Disclaimer: I am not responsible for any damage you may do to your phone. I am only providing instructions on what worked for me. This is very beta. Good luck. Enjoy the nandroid goodness.

First link is Dead...........
ooopps Srry my bad, Its up.

You should mention that the chmod command is in the original terminal window. Also, you could do it in one window if you put:
adb remount
adb push bla /bla/bla
at the begining of everything.
adb push flash_image to /system/bin
Click to expand...
Click to collapse
I don't think there's a "to" in that command either. lol

testing567 said:
You should mention that the chmod command is in the original terminal window. Also, you could do it in one window if you put:
adb remount
adb push bla /bla/bla
at the begining of everything.
I don't think there's a "to" in that command either. lol
Click to expand...
Click to collapse
Thanks. I don't think the "to" is going to work either. I made the corrections.

Just a quick question. What does this boot too. Im new to all this phone stuff. I did the upgrade to 2.1 leaked so just been searching the forum here each day to see if a solution has come about. i just noticed v.1.6.2 in there so was curious as to what this will do.

Will this put the regular android on it or keep it the same, sorry just kinda getting started with android

coupla questions -
For northmendo:
Is the reboot in the middle of this even necessary? ( flash_image won't work right if /system is still mounted rw ?)
For testing567:
Do all the adb shell commands run as root against the 2.1_root install ... or maybe the above could be simplified even more by just running "adb root" first?
For Austinjs0102 (not a question)
This process only applies (at the moment) to phones with "2.1_root" - there isn't a path at present to go from "2.1_leak" to a rooted phone. Assuming that a way to roll back (or get root) for "2.1_leak" eventually is found, then the answer to your question is this: it is a process to apply a custom recovery partition to the phone that include tools that will allow you to perform complete phone backups and restore operations. This can be critical for devs who are experimenting with writing boot or system partitions to their phones - if something goes wrong with their experiments, they can "boot" their phone into recovery mode and restore back to a working configuration. To reiterate, though: this only applies to phones that are already rooted.
bftb0

Thanks a bunch that helps clear up info.
hopefully the hard working dev's here find a 2.1 leaked fix for us early people, if not then i may need to lose the phone lol.

Austinjs0102 said:
Just a quick question. What does this boot too. Im new to all this phone stuff. I did the upgrade to 2.1 leaked so just been searching the forum here each day to see if a solution has come about. i just noticed v.1.6.2 in there so was curious as to what this will do.
Click to expand...
Click to collapse
I am in same boat as you...

Let me start off by saying that I'm not a phone dev. I've done software development for many years, but never messed with the phone.
Can someone explain why we can't just load the 1.5 rooted PB001IMG.ZIP file over our 2.1 leaked handset? Is it a matter of the version number being lower? If so, since the 1.5 is rooted, couldn't someone just up the version number to whatever the 2.1 leak is plus one? Then, once it's loaded, write a little app to drop the number back where it should be?
TIA for the education.
Doc

DocTauri said:
Let me start off by saying that I'm not a phone dev. I've done software development for many years, but never messed with the phone.
Can someone explain why we can't just load the 1.5 rooted PB001IMG.ZIP file over our 2.1 leaked handset? Is it a matter of the version number being lower? If so, since the 1.5 is rooted, couldn't someone just up the version number to whatever the 2.1 leak is plus one? Then, once it's loaded, write a little app to drop the number back where it should be?
TIA for the education.
Doc
Click to expand...
Click to collapse
(I suppose I shouldn't respond, 'cuz DocTauri is jacking northmendo's thread. Sorry north!)
Doc,
I understand exactly what you are getting at... and also think I can explain why it's not easy.
First - what has been discovered so far was not a "root break-in", but rather an engineering ROM with root "built in". It is cryptographically signed so that a production phone will recognize the .zip file as a valid ROM. That first validation step has nothing to do with version numbers.
If the "SPL" on an unrooted phone was doing something as simple as looking at a couple of bytes in the initial file downloaded to the phone, then yes - doing what you suggest would work... just patch a few bytes using a hex editor. Unfortunately, the phone SPL is quite sophisiticated: it verifies the crypto signature on the entire zip file first, unpacks that zip, and then examines the contents of an individual file within the zip archive (and possibly even unpacks one of the YAFFS image files and then looks in a file within the YAFFS image) to read version numbers.
That means that the fundamental issue is the cryptographic signature on the .zip file. If you do anything which breaks step #1, step #2 (version # checks) are never reached. Certainly an individual file could be byte-patched, and then images and zip files could be re-assembled... but you would have no way to sign the zip with HTC's private key. Or you could even attempt to byte-patch the zip file - but then that would break the crypto signature. Either way, the crypto signature on the zip file is no longer valid.
If you have HTC's private RSA key, let us know!
bftb0

bftb0 said:
coupla questions -
For northmendo:
Is the reboot in the middle of this even necessary? ( flash_image won't work right if /system is still mounted rw ?)
Click to expand...
Click to collapse
I added the reboot because. All I would get is out of memory errors. The reboot fixed that.
e.g.
mtd: read error at 0x001e0000 (Out of memory)
mtd: read error at 0x00200000 (Out of memory)
mtd: read error at 0x00220000 (Out of memory)
mtd: read error at 0x00240000 (Out of memory)

northmendo -
That first link (that you corrected) now points to the recovery image, not "flash_image".
Note that the "flash_image" executable which Amon_RA originally included with his first recovery (.zip) is identical to the /system/bin/flash_image binary which ships on the Eris with 1.5 (1.17.605.1); the md5sum signature (of both of those files) is:
16559f2c27d08ff1ddfcaca05fbf10fb flash_image
That's also the same md5 signature as the "flash_image" file which was posted to dl.dropbox.
I don't have 2.1_root installed on my phone, but if the same binary is already on the phone after installing the 2.1_root ROM, there's no need to include those steps in your instructions. It is also possible that even if the "2.1_root" version of /system/bin/flash_image is different, it would also work.
Note that the only reason I bring it up is that your instructions might be (a) unnecessary, and (b) are encouraging folks to overwrite a binary that is already on the phone. No harm (but unneeded) if it is the same, and unknown harm if it is different.
Also (while I'm at it)
901167f6b5541b488c8e0404bceb0631 recovery-RA-eris-v1.6.2.img ***
It appears to me ( reading between the lines here ) that Amon_RA is trying to improve his v1.6.2 recovery - folks might want to keep an eye on that thread.
An alternative and quicker method than all of this is what zifnab06 suggested here. It's only two lines long, after all.
bftb0
[Edit]***Wow, my post was obsolete the moment I posted it - don't know how I missed Amon_RA's announcement post. Note that there appears to be several versions of "v1.6.2" floating around now - make sure to check his post if you want the most recent.

bftb0 said:
It appears to me ( reading between the lines here ) that Amon_RA is trying to improve his v1.6.2 recovery - folks might want to keep an eye on that thread.
An alternative and quicker method than all of this is what zifnab06 suggested here. It's only two lines long, after all.
bftb0
Click to expand...
Click to collapse
I will keep the link updated to the newest version here. Also I tried the quicker method without success. I will try it again when I get home from work.
Thanks

bftb0 said:
(I suppose I shouldn't respond, 'cuz DocTauri is jacking northmendo's thread. Sorry north!)
Click to expand...
Click to collapse
Sorry, didn't mean to. Understood on the explaination. I didn't realize it was a different rom image, I thought the key had been broken, allowing someone to resign a modified image.
Thanks!
Doc

I used this method and it was all really easy until I got to the end. It just says usage and then sits their and does nothing. I unplugged it and went into recovery and see the android dude and a yellow traiangle and exclamation point. Did I forget something? Is their an alternative way to flashing this?

sdk issues for flashing recovery...
Hey guys,
Im a noob but here's whats going on, Ive downloaded sdk extracted it to my c drive, ive downloaded all the required packages reccomended in the forum, Ive up dated my driver and still my machine doesnt recognize my phone...
Ive also extracted the recovery image to my tools directory and added the the path in enviromentals...
So at this point Im stuck as to how to get my pc (xp) phone and sdk in sync in order to get this recovery image working...So any advice would be highly appreciated. Thanks in advance.
Chris

Spencer_Moore said:
I used this method and it was all really easy until I got to the end. It just says usage and then sits their and does nothing. I unplugged it and went into recovery and see the android dude and a yellow traiangle and exclamation point. Did I forget something? Is their an alternative way to flashing this?
Click to expand...
Click to collapse
You could try this.
If you have your phone pluged in and type in to the terminal
adb reboot recovery [hit enter]
After you phone reboots it should come up with text options to do back-ups and restores. Do you get any of that?

Anyone know the key combo to get into recovery without adb?

having issues getting adb
got the command prompts working in xp, however while trying the methods here in the forum i am getting adb not foud errors. Any suggestions?

[REQUEST] Acer_A500_1.139.05_COM_GEN1

Can someone dump system and flexrom from ACER_A500_1.139.05_COM_GEN1, so that those that do not get the OTA or have previously flashed the chineese ROM can update manually their devices?
Commands are:
dd if=/dev/block/mmcblk0p3 of=/sdcard/system.img
dd if=/dev/block/mmcblk0p6 of=/sdcard/flexrom.img
Thanks!!!!

Canadian A500 WIFI only Acer_A500_1.139.05_COM_GEN1
http://dl.dropbox.com/u/14023365/flexrom.zip
uploading system.img...

spades said:
Canadian A500 WIFI only Acer_A500_1.139.05_COM_GEN1
http://dl.dropbox.com/u/14023365/flexrom.zip
uploading system.img...
Click to expand...
Click to collapse
Thanks! What modifications does this have?

huxflux2003 said:
Thanks! What modifications does this have?
Click to expand...
Click to collapse
Originally Posted by lord_voldemort666 View Post
do you guys know how to use google? A simple search led me to this...
"Below are the most important product improvements listed being covered by this update, which will further enrich the overall user experience;
1. Bluetooth Keyboard support added (currently for English language mapping only)
1. Touch panel performance improvement
1. G-sensor calibration
1. Fix for A500 turning off and on in sleep mode (Screen turning off and on when asleep?)
Firmware version change after FOTA update: 1.016.05_EMEA_GEN1 --> 1.139.05_EMEA_GEN1
Countries covered by EMEA_GEN1: UK / France / Italy / Spain
This update will also become available for the other countries soon, but as the exact release schedule is not fully available yet we are not able to provide you with any reliable release date at this moment."

i meant the uploaded system.img...like root modules and stuff...

huxflux2003 said:
Thanks! What modifications does this have?
Click to expand...
Click to collapse
I installed a few apps and that's it.
http://dl.dropbox.com/u/14023365/system.7z.001
http://dl.dropbox.com/u/14023365/system.7z.002
My 2 wifi files in the system/lib/module folder if needed..
http://dl.dropbox.com/u/14023365/wifi.zip

spades said:
I installed a few apps and that's it.
http://dl.dropbox.com/u/14023365/system.7z.001
http://dl.dropbox.com/u/14023365/system.7z.002
Click to expand...
Click to collapse
Hmmmmmm, unable to extract when renaming to a .7z extention. Is this an image file, or what should the extention of these files be?????
Thanks

bonzer2u said:
Hmmmmmm, unable to extract when renaming to a .7z extention. Is this an image file, or what should the extention of these files be?????
Thanks
Click to expand...
Click to collapse
It's actually a multi-part 7z. Don't rename, just extract.

spades said:
It's actually a multi-part 7z. Don't rename, just extract.
Click to expand...
Click to collapse
DOH..... works like a charm.

spades said:
Canadian A500 WIFI only Acer_A500_1.139.05_COM_GEN1
http://dl.dropbox.com/u/14023365/flexrom.zip
uploading system.img...
Click to expand...
Click to collapse
I am in Ontario and only have v1.016.05_COM_GEN1
there are no update when hitting the system update button
unrooted ... got it few days ago.

I just flashed the Acer_A500_1.139.05_COM_GEN1 system image and flexrom to my system and I just noticed my version still shows Acer_A500_1.104.05_COM_GEN1
Hrm, is this normal?

Something may have gone wrong during the flash. I just flashed the flexrom and system images and mine reports as 1.139.05_COM_GEN1 now. There seems to be an issue with the wifi and GPS on mine now, though. I ran logcat while trying to enable wifi, and it looks like there's a driver missing.
Code:
E/WifiService( 115): Invoking mWifiStateMachine.setWifiEnabled
E/WifiStateMachine( 115): Failed to load driver!
E/WifiStateMachine( 115): DriverFailedState

kudakeru said:
Something may have gone wrong during the flash. I just flashed the flexrom and system images and mine reports as 1.139.05_COM_GEN1 now. There seems to be an issue with the wifi and GPS on mine now, though. I ran logcat while trying to enable wifi, and it looks like there's a driver missing.
Code:
E/WifiService( 115): Invoking mWifiStateMachine.setWifiEnabled
E/WifiStateMachine( 115): Failed to load driver!
E/WifiStateMachine( 115): DriverFailedState
Click to expand...
Click to collapse
Look here:
http://forum.xda-developers.com/showpost.php?p=13974214&postcount=62
and download the appropriate modules for your new kernel (the old modules don't load because they don't match with the kernel version). The correct ones are those at the bottom, with 991.
Decompress, copy to /system/lib/modules. Use insmod /system/lib/modules/bcm..... and insmod /system/lib/modules/scsi..... (not sure if necessary). Reboot.
BTW - Can anyone tell me where the option to calibrate the g-sensor is after the update? I cannot find it in settings, and the change log claims it's new.
Unfortunately the screen on issue persists after the update.

heyoh said:
I just flashed the Acer_A500_1.139.05_COM_GEN1 system image and flexrom to my system and I just noticed my version still shows Acer_A500_1.104.05_COM_GEN1
Hrm, is this normal?
Click to expand...
Click to collapse
Did you use the commands in the first post by any chance?
dd if=/dev/block/mmcblk0p3 of=/sdcard/system.img
dd if=/dev/block/mmcblk0p6 of=/sdcard/flexrom.img
If yes, you've just overwritten the system.img and flexrom.img on the root of your sdcard. Those commands were for making the images from the actual partitions.
You will need to copy back system.img and flexrom.img to /sdcard. Afterwards do:
dd if=/sdcard/system.img of=/dev/block/mmcblk0p3
dd if=/sdcard/flexrom.img of=/dev/block/mmcblk0p6
Might be a good idea to reboot in between (at least I had to, but I was using the terminal on the A500 to flash the images).
After you're done you will notice you don't have WiFi anymore (it will say Error). See post above about how to get it back.

Odd thing, I still have root after the update (update shows in About correctly). Am wondering if I have missed anything. I had lots of frozen apps, but theoretically they shouldn't have been in the way. I cannot find the G-Sensor Calibration tool either (any idea where it is?)

adancau said:
Look here:
http://forum.xda-developers.com/showpost.php?p=13974214&postcount=62
and download the appropriate modules for your new kernel (the old modules don't load because they don't match with the kernel version). The correct ones are those at the bottom, with 991.
Decompress, copy to /system/lib/modules. Use insmod /system/lib/modules/bcm..... and insmod /system/lib/modules/scsi..... (not sure if necessary). Reboot.
BTW - Can anyone tell me where the option to calibrate the g-sensor is after the update? I cannot find it in settings, and the change log claims it's new.
Unfortunately the screen on issue persists after the update.
Click to expand...
Click to collapse
Aha, thanks! I tried with the kernel version you suggested, but insmod threw an exec failure. I looked at the kernel version again in device info, and it was 2.6.36.3-00001-g9b3ce2b, so I grabbed that archive (the middle of the three in the post you linked) and everything is working great now. I haven't had any luck finding the g-sensor calibration yet, though.

GPS status (https://market.android.com/details?id=app-com.eclipsim.gpsstatus2) I believe has a calibration feature in its new version.

adancau said:
Did you use the commands in the first post by any chance?
dd if=/dev/block/mmcblk0p3 of=/sdcard/system.img
dd if=/dev/block/mmcblk0p6 of=/sdcard/flexrom.img
If yes, you've just overwritten the system.img and flexrom.img on the root of your sdcard. Those commands were for making the images from the actual partitions.
You will need to copy back system.img and flexrom.img to /sdcard. Afterwards do:
dd if=/sdcard/system.img of=/dev/block/mmcblk0p3
dd if=/sdcard/flexrom.img of=/dev/block/mmcblk0p6
Might be a good idea to reboot in between (at least I had to, but I was using the terminal on the A500 to flash the images).
After you're done you will notice you don't have WiFi anymore (it will say Error). See post above about how to get it back.
Click to expand...
Click to collapse
Can you please details how to use these dd commands, I got confused Thank you

lpachuong said:
Can you please details how to use these dd commands, I got confused Thank you
Click to expand...
Click to collapse
dd if=/sdcard/system.img of=/dev/block/mmcblk0p3
dd if=/sdcard/flexrom.img of=/dev/block/mmcblk0p6
input file (if) is the image from the sdcard, output file (of) is the destination partition

where and how do i run these script? Thank you

Rooting ideas and discussion

I just had an idea. What if someone roots a system.img by extracting it from a kdz and then mounting it in linux copying the root files setting the permissions and then flashing that with download mode? A simple
Code:
dd if=/data/local/tmp/system.img of=/dev/block/platform/??????/by-name/system
should do the trick to flash the system.img file replacing the ?????? with the correct directory.
Just a thought.

Wouldn't you have to have read/write access in order to push the system.img?

Impossible,without root.
Sent from my LG-D802 using Tapatalk

l33tlinuxh4x0r said:
I just had an idea. What if someone roots a system.img by extracting it from a kdz and then mounting it in linux copying the root files setting the permissions and then flashing that with download mode? A simple
Code:
dd if=/data/tmp/system.img of=/dev/block/platform/??????/by-name/system
should do the trick to flash the system.img file replacing the ?????? with the correct directory.
-
Click to expand...
Click to collapse

Dennisg34 said:
There's already a thread to discuss root. Please search before posting, thanks.
Sent from my G4 using your mom
Click to expand...
Click to collapse
I think both of the previous threads discussing root have been closed. I haven't seen another - did I miss it?

Already tried something similar. Requires root unless you're one of the lucky few who have such advanced knowledge of hacking bootloaders/exploits....which I unfortunately am not. LOL

rfarrah said:
I think both of the previous threads discussing root have been closed. I haven't seen another - did I miss it?
Click to expand...
Click to collapse
Apologies, I forgot they were.

Hello,
It is possible to rooter lg g4 with : V10B LGH815
thank you :fingers-crossed:

dydyfr said:
Hello,
It is possible to rooter lg g4 with : V10B LGH815
thank you :fingers-crossed:
Click to expand...
Click to collapse
Yes, look in the developer section.

It is possible to dd to partitions using download mode. The only real problem is that the root method would be huge having to include a system.img.

l33tlinuxh4x0r said:
It is possible to dd to partitions using download mode. The only real problem is that the root method would be huge having to include a system.img.
Click to expand...
Click to collapse
Additionally, you'd need a separate one for every carrier/variant.
I guess if it worked though, who cares how many we need or how big they are. Except with dd, one typo and you've got yourself a brick.

tabp0le said:
Additionally, you'd need a separate one for every carrier/variant.
I guess if it worked though, who cares how many we need or how big they are. Except with dd, one typo and you've got yourself a brick.
Click to expand...
Click to collapse
very true.

tabp0le said:
Additionally, you'd need a separate one for every carrier/variant.
I guess if it worked though, who cares how many we need or how big they are. Except with dd, one typo and you've got yourself a brick.
Click to expand...
Click to collapse
l33tlinuxh4x0r said:
very true.
Click to expand...
Click to collapse
Though...wouldn't it still be able to get into download mode? I could be wrong, but that's not on the system partition from my understanding.
I'm on linux and am familiar with dd (I'm a distro-hopper and have no optical drive, so everything gets dd'ed onto usb drive).
Wouldn't we have to specify a block size on that? I know at least on linux distro, if block size isn't specified, I end up in non-boot.

geoff5093 said:
Yes, look in the developer section.
Click to expand...
Click to collapse
Good
Thank's
Sent from my Iconia A3-A20 FHD using XDA Free mobile app

Th3Bill said:
Though...wouldn't it still be able to get into download mode? I could be wrong, but that's not on the system partition from my understanding.
I'm on linux and am familiar with dd (I'm a distro-hopper and have no optical drive, so everything gets dd'ed onto usb drive).
Wouldn't we have to specify a block size on that? I know at least on linux distro, if block size isn't specified, I end up in non-boot.
Click to expand...
Click to collapse
Actually you are correct. The laf partition is the download mode. Flashing recovery is where we have to worry about losing download mode. (I never understood why, but at least with the G2 download mode broke when flashing custom recovery without a certain patch)

The previous root threads were locked because peopel wouldn't stay on topic after multiple warnings...

Eagle1337 said:
The previous root threads were locked because peopel wouldn't stay on topic after multiple warnings...
Click to expand...
Click to collapse
Correction, they were closed per OP request
This one is now clean, lets try to stay on topic,
If anyone feels the urge to regurgitate further horse crap... we'll see what happens

l33tlinuxh4x0r said:
It is possible to dd to partitions using download mode. The only real problem is that the root method would be huge having to include a system.img.
Click to expand...
Click to collapse
How can you confirm being able to dd to partitions using download mode? In download mode isn't the dd running from /system/bin that is mounted as ro. How could you replace /system while it is mounted and running dd from it?

gbgadgets said:
How can you confirm being able to dd to partitions using download mode? In download mode isn't the dd running from /system/bin that is mounted as ro. How could you replace /system while it is mounted and running dd from it?
Click to expand...
Click to collapse
linux loads commands that you are in the process of running into ram. You can even delete a file that you are running and still be able to use it until you close it. Once you close it is when the problem would occur but by that time you would already have the new file in place. Also do NOT run a
Code:
dd if=/dev/zero of=/dev/block/platform/??????/by-name/system
just skip that step otherwise you would lose the ability to dd.
Go directly for a
Code:
dd if=/data/local/tmp/system.img of=/dev/block/platform/??????/by-name/system
also to get a system.img instead of extracting from a kdz you could run
Code:
dd if=/dev/block/platform/??????/by-name/system of=/data/local/tmp/system.img

docfreed said:
Wouldn't you have to have read/write access in order to push the system.img?
Click to expand...
Click to collapse
you can push to /data/local/tmp using adb without root.

[Q]Flashing bootlogo MXPE 6.0 Custom Rom Custom Kernel

Is there a flashing bootlogo for MXPE 6.0 Custom Rom & Custom Kernel guide?
Screenshot below as to what I am running on my my phone. I am specically looking to replace the unlock bootloader warning bootlogo with something nice.
About Phone:

Hitti2 said:
Is there a flashing bootlogo for MXPE 6.0 Custom Rom & Custom Kernel guide?
Screenshot below as to what I am running on my my phone. I am specically looking to replace the unlock bootloader warning bootlogo with something nice.
About Phone:
Click to expand...
Click to collapse
This thread has what you need to get rid of the unlocked bootloader warning. Make sure you read carefully and get the marshmallow logo for your rom.
Here's a kernel tuning guide.

jason2678 said:
This thread has what you need to get rid of the unlocked bootloader warning. Make sure you read carefully and get the marshmallow logo for your rom.
Here's a kernel tuning guide.
Click to expand...
Click to collapse
It says its for
LPH23.116-18
Mine is

Hitti2 said:
It says its for
LPH23.116-18
Mine is
Click to expand...
Click to collapse
The one attached to the OP is for lollipop. You need the marshmallow one that Spasticdroid posted about a dozen pages in.

Gotya.
As if you hadnt known,I am new at this.
What can I use to get the location for the logo after downloading.
Is there like a copy url in es file explorer?
Then I can paste then write it down on paper.

Hitti2 said:
Gotya.
As if you hadnt known,I am new at this.
What can I use to get the location for the logo after downloading.
Is there like a copy url in es file explorer?
Then I can paste then write it down on paper.
Click to expand...
Click to collapse
The easiest thing to do would be to download it to a computer, unzip it, and use fastboot to flash logo.bin with the command in the OP of the logo thread.
Alternately you could probably use dd to flash it if you don't have access to a PC or just don't want to use one. I have not tested and would not recommend that.
Fastboot worked fine. It is far too easy to make a typo and trash your phone with dd; it isn't nicknamed disk destroyer for no reason. Assuming you download it to the default folder, unzip it there with a utility like es file explorer, and are the primary user of this device the command would look like this:
Code:
su
dd if=/data/media/0/Download/logo.bin of=/dev/block/mmcblk0p31
If you do go this route and get a command not found for dd, then you probably need to install busybox. Triple check all your inputs if you do this. Typos with dd can be nasty. I've modded plenty of devices this way, but just use fastboot when it is available. The syntax is easier with fastboot, and you don't have to worry about writing to the wrong block device since it handles them all by name.

Thanks a bunch. Be fire i proceed
Is there a way to backup the unlocked bootloader logo?
So if I ever need to replace it back.
Perferrably through fastboot. I've got a pc ready for adb and fastboot.

Hitti2 said:
Is there a way to backup the unlocked bootloader logo?
Click to expand...
Click to collapse
Essentially just reverse the arguments in the command I posted above.
Code:
su
dd if=/dev/block/mmcblk0p31 of=/data/media/0/Download/logo.img
That should leave you with an image of the logo partition in your /sdcard/Download folder.

jason2678 said:
Essentially just reverse the arguments in the command I posted above.
Code:
su
dd if=/dev/block/mmcblk0p31 of=/data/media/0/Download/logo.img
That should leave you with an image of the logo partition in your /sdcard/Download folder.
Click to expand...
Click to collapse
Do I have to use dd to backup the logo? Is there a cmd in fastboot or adb?
Thnx.

Hitti2 said:
Do I have to use dd to backup the logo? Is there a cmd in fastboot or adb?
Thnx.
Click to expand...
Click to collapse
You could use adb shell, but that just lets you use your computer keyboard instead of trying to type in a terminal app. The command to get a single partition remains the same.
There is an app called partitions backup & restore that can handle this without any command line use. Its available on the play store.

jason2678 said:
You could use adb shell, but that just lets you use your computer keyboard instead of trying to type in a terminal app. The command to get a single partition remains the same.
There is an app called partitions backup & restore that can handle this without any command line use. Its available on the play store.
Click to expand...
Click to collapse
Yea, I don't think I can use dd.
http://www.noah.org/wiki/Dd_-_Destroyer_of_Disks#Why_use_dd_instead_of_cp.3F
For linux. I am on a WIn7x64 computer.
And for Partitions Backup & Restore
one comment
Bricked. So it kinda works. It did keep my phone's efs/imei info. But upon reinstalling by phone was stuck in bootloop. I had to set my phone back to Android 4.0 which means some newer apps do not not work. & trying to reinstall different/newer android ROM is now impossible. I was barely able to get it back to working condition, but now slower than before. Unless you know how to reprogram the partitions, i would not mess with this app.
Click to expand...
Click to collapse
I think Ima leave the bootlogo alone.

Hitti2 said:
Yea, I don't think I can use dd.
http://www.noah.org/wiki/Dd_-_Destroyer_of_Disks#Why_use_dd_instead_of_cp.3F
For linux. I am on a WIn7x64 computer.
Click to expand...
Click to collapse
You're correct, dd is part of GNU coreutils, but you'll be able to use it even if you use adb shell from a windows computer. The dd binary resides on your phone (which is pretty much a linux environment, just android/linux instead of GNU/linux), not on the computer.
I don't think dd is there by default in a typical stock rom, but busybox adds the utilities stock android leaves out. I'm using busybox on rails from the play store with this phone.
I've been using linux for about 15 years, so have a comfortable, if uneasy, feeling for using dd. It is a powerful tool, but it is not fault tolerant and you usually have to run it as root to get the job done. Make a little typo or have an absent minded moment and reverse the if and of arguments and you can have a really bad day.

[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.