i took the 8mb boot.img from the nandroid backup/thread, renamed it to .bin, opened with a hex editor, deleted everything after 2cffff (to make correct size), saved as boot.img and flashed. then updated via recovery. cheers.
Code:
fastboot flash boot test_boot.img
edit: uploaded to my host as well: http://mycarbl0ws.com/test_boot.rar
What do u mean u updated via recovery?
Sent from my Nexus S
k0mpresd said:
i took the 8mb boot.img from the nandroid backup/thread, renamed it to .bin, opened with a hex editor, deleted everything after 2cffff (to make correct size), saved as boot.img and flashed. then updated via recovery. cheers.
Code:
fastboot flash boot test_boot.img
Click to expand...
Click to collapse
nice. testing now
plmiller0905 said:
What do u mean u updated via recovery?
Nevermind..I got it..stupid question
Sent from my Nexus S
Click to expand...
Click to collapse
Nevermind..I got it..stupid question
Sent from my Nexus S
Thanks! I just flashed it, and updated w/ CWR. worked fine, at 2.3.1 now
Luxferro said:
Thanks! I just flashed it, and updated w/ CWR. worked fine, at 2.3.1 now
Click to expand...
Click to collapse
hey when you downloaded the file did you rename the file from .rar to .img to flash???
Does this boot img come with root?
Sent from my Nexus S using Tapatalk
brian6685 said:
Does this boot img come with root?
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
no. this is stock.
JDMSirEK4 said:
hey when you downloaded the file did you rename the file from .rar to .img to flash???
Click to expand...
Click to collapse
an .rar is a compressed file. unrar the file to get the .img
Do u lose clockwork recovery when u reboot? That's the problem I'm having updating to 2.3.1
breaks wifi for me
How do I flash the img? Do I use adb and if so what's the adb commands?
After I flash this, i just go into rom manager and download/install the update and that's it?
Will i lose root by flashing this?
Sent from my Nexus S
k0mpresd said:
no. this is stock.
Click to expand...
Click to collapse
Okay thanks
Sent from my Nexus S using Tapatalk
Can somebody HELP! What I'm I doing wrong that I can't flash the boot.img!!! I'
m getting an error everytime.
This is what i'm typing in "FASTBOOT":
c:\android-sdk-windows\platform-tools>fastboot flash boot test_boot.img
error: cannot load 'test_boot.img'
Silrocco said:
Can somebody HELP! What I'm I doing wrong that I can't flash the boot.img!!! I'
m getting an error everytime.
This is what i'm typing in "FASTBOOT":
c:\android-sdk-windows\platform-tools>fastboot flash boot test_boot.img
error: cannot load 'test_boot.img'
Click to expand...
Click to collapse
test_boot.img should be in the folder, c:\android-sdk-windows\platform-tools\
since that is where you are running flashboot from
graemegb said:
breaks wifi for me
Click to expand...
Click to collapse
looks like installing a rooted img breaks wifi. i did the superboot/paulobrian method then installed the voodoo ext 4 kernel, then wifi was broken.
i reflashed my boot.img and re-updated via recovery and i have wifi back.
vroomr4 said:
test_boot.img should be in the folder, c:\android-sdk-windows\platform-tools\
since that is where you are running flashboot from
Click to expand...
Click to collapse
Thanks for the help...it worked.
worked!!!....so can we gain root access back or we just got to hang tight?
the flash worked but I can't update, it says file_getprop: failed to stat "system/build.prop" No such file or directory.
Error in sdcard/update.zip (status 7)
JDMSirEK4 said:
worked!!!....so can we gain root access back or we just got to hang tight?
Click to expand...
Click to collapse
heres how to get root back:
download the superboot/paulobrian method.
boot phone to fastboot.
Code:
fastboot boot boot.superboot.img
let phone boot, open terminal, su, just to check.
reboot phone.
rooted and ota'd now!
The only .zip I can find already has a modified boot.img that is rooted. I'm looking for a bone stock one so that I can apply the H21120x OTA via TWRP. (I guess I Could just write out the boot.img update from the updater-script).
Anyone have a copy of this from their device or a way to get it from a KDZ?
pizzaboy192 said:
The only .zip I can find already has a modified boot.img that is rooted. I'm looking for a bone stock one so that I can apply the H21120x OTA via TWRP. (I guess I Could just write out the boot.img update from the updater-script).
Anyone have a copy of this from their device or a way to get it from a KDZ?
Click to expand...
Click to collapse
i think you can using ext2explore-2.2.71 you can then get boot.
raptorddd said:
i think you can using ext2explore-2.2.71 you can then get boot.
Click to expand...
Click to collapse
That worked!
I'd also recommend not doing it the way I did (modifying the update.zip and flashing stock boot.img) it seems to have broken Bluetooth.
raptorddd said:
i think you can using ext2explore-2.2.71 you can then get boot.
Click to expand...
Click to collapse
I was able to get a H81120V boot.img extracted from the kdz, but it looks like flashing the update.zip through TWRP breaks bluetooth.
pizzaboy192 said:
I was able to get a H81120V boot.img extracted from the kdz, but it looks like flashing the update.zip through TWRP breaks bluetooth.
Click to expand...
Click to collapse
sorry i just extract and flash ive never modified boot.
What the title says. I'm using the latest Galaxy J6 Firmware. It used to be able to patch the boot.img fine, but for some reason now it's completely impossible. Am I doing something wrong?
AndreM962 said:
What the title says. I'm using the latest Galaxy J6 Firmware. It used to be able to patch the boot.img fine, but for some reason now it's completely impossible. Am I doing something wrong?
Click to expand...
Click to collapse
I got that error on some Samsung boot.img when I forgot to decompress the .lz4 first.
Makes sure you have boot.img and not a boot.img.lz4
Hope it helps.
Sent from my Xperia XZ3.
tys0n said:
I got that error on some Samsung boot.img when I forgot to decompress the .lz4 first.
Makes sure you have boot.img and not a boot.img.lz4
Hope it helps.
Sent from my Xperia XZ3.
Click to expand...
Click to collapse
I am using a Boot.img file, but all I did was change the file extension by erasing the .lz4 at the end. Is that all I need to do, or do I need to do something more to decompress it? Can you explain what, if so?
AndreM962 said:
I am using a Boot.img file, but all I did was change the file extension by erasing the .lz4 at the end. Is that all I need to do, or do I need to do something more to decompress it? Can you explain what, if so?
Click to expand...
Click to collapse
You can use one of method explained here:
https://glamourrom.eu/how-to/extract-lz4-image/
Sent from my SM-N960F via Tapatalk
As stated above, I am trying to unbrick my Axon M with the firehose provided by Unjustified Dev. and firmware from deadman96385. When I tried using QFIL, even placing everything in its own directory on the root of the PC with no spaces in file names, it would get stuck when flashing. And whenever I tried to use MiFlash, I would get the error:"couldn't find flash script" when I selected the firmware folder. Any help is much appreciated.
Just to make sure, When I mentioned to use his firehose, I meant download the other firehose files but then use his firehose as the programmer, did you do that?
edit: I used the edl 37 firmware and the firehose from unjustified, edited the program to remove entire userdata section, renamed unjustified's twrp to recovery.img, edited the boot.img to remove secure boot and used those instead of stock and finally used qfil to flash, I had no errors. but i also used a good cable. Besides the boot and recovery edit, you should be ok as long as the rest was done.
ff7cloudsnobody said:
Just to make sure, When I mentioned to use his firehose, I meant download the other firehose files but then use his firehose as the programmer, did you do that?
edit: I used the edl 37 firmware and the firehose from unjustified, edited the program to remove entire userdata section, renamed unjustified's twrp to recovery.img, edited the boot.img to remove secure boot and used those instead of stock and finally used qfil to flash, I had no errors. but i also used a good cable. Besides the boot and recovery edit, you should be ok as long as the rest was done.
Click to expand...
Click to collapse
I'm confused, I am using Deadmans b37 firmware, and Unjustified's firehose. I removed the entire userdata line from rawprogram0, and used that with the accompanying patch xml file with QFIL. I don't know how to alter boot.img, and where would I place the edited "recovery.img" file? I am using a good USB cable as well.
ehsan96696 said:
I'm confused, I am using Deadmans b37 firmware, and Unjustified's firehose. I removed the entire userdata line from rawprogram0, and used that with the accompanying patch xml file with QFIL. I don't know how to alter boot.img, and where would I place the edited "recovery.img" file? I am using a good USB cable as well.
Click to expand...
Click to collapse
Ignore the img edits, that's what I did but its not necessary. Are you running qfil as admin? Is the directory simple, no spaces or symbols? What is the latest error you are getting?
boot
ff7cloudsnobody said:
Just to make sure, When I mentioned to use his firehose, I meant download the other firehose files but then use his firehose as the programmer, did you do that?
edit: I used the edl 37 firmware and the firehose from unjustified, edited the program to remove entire userdata section, renamed unjustified's twrp to recovery.img, edited the boot.img to remove secure boot and used those instead of stock and finally used qfil to flash, I had no errors. but i also used a good cable. Besides the boot and recovery edit, you should be ok as long as the rest was done.
Click to expand...
Click to collapse
Hello.
Can you share your patched boot image, please? Perhaps, after the removal of secure boot, it will be possible to patch the boot image with Magisk (in working Android), and then flash it with TWRP or QFIL, thus obtaining root?
WBR, Draco.
ff7cloudsnobody said:
Ignore the img edits, that's what I did but its not necessary. Are you running qfil as admin? Is the directory simple, no spaces or symbols? What is the latest error you are getting?
Click to expand...
Click to collapse
I did run qfil as admin. These pictures will show the directory: https://imgur.com/M2TdriT https://imgur.com/BmwyeMa
I did not encounter error, it just gets stuck as shown above.
Drakosha said:
Hello.
Can you share your patched boot image, please? Perhaps, after the removal of secure boot, it will be possible to patch the boot image with Magisk (in working Android), and then flash it with TWRP or QFIL, thus obtaining root?
WBR, Draco.
Click to expand...
Click to collapse
Bam. Let me know how it goes, wasn't gonna mess with root until I finished getting a fully working 8.1 AOSP done. After that, I'm gonna try getting this bad boy all the way to android 10.
ehsan96696 said:
I did run qfil as admin. These pictures will show the directory: https://imgur.com/M2TdriT https://imgur.com/BmwyeMa
I did not encounter error, it just gets stuck as shown above.
Click to expand...
Click to collapse
rename that folder, that name is way too long. Name it z999update37 or something short and sweat like I did and see if that helps, you can also see if it was a bad download by trying a new one. it just seems to be getting stuck on the emmc portion. Like someone else said in the other thread, make sure the config of qfil is for emmc and that not really anything is selected.
edit: I attached my emmc file, try using it in your folder to see if thats the issue
ff7cloudsnobody said:
Bam. Let me know how it goes, wasn't gonna mess with root until I finished getting a fully working 8.1 AOSP done. After that, I'm gonna try getting this bad boy all the way to android 10.
rename that folder, that name is way too long. Name it z999update37 or something short and sweat like I did and see if that helps, you can also see if it was a bad download by trying a new one. it just seems to be getting stuck on the emmc portion. Like someone else said in the other thread, make sure the config of qfil is for emmc and that not really anything is selected.
edit: I attached my emmc file, try using it in your folder to see if thats the issue
Click to expand...
Click to collapse
So, few things. After following all of Undead's installation steps (minus using QFIL), and the steps that I listed at the start of this post, I used the miflash from the axon 7 tutorial page here:https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
For some reason any other Miflash would give the previously stated error. I then installed the ZTE Android drivers provided. And using deadman's B37, Miflash worked like a charm!
ff7cloudsnobody said:
Bam. Let me know how it goes, wasn't gonna mess with root until I finished getting a fully working 8.1 AOSP done. After that, I'm gonna try getting this bad boy all the way to android 10.
Click to expand...
Click to collapse
Hello.
I flashed B37 with your boot image & TWRP successfully (using MiFlash; QFIL stopped at the same emmc_appsboot file). Except for "TV Mode setup" that was blocking the normal startup, everything went smooth. However, when I attempted to flash Magisk-patched boot image using TWRP, the phone refused to boot, so I had to re-flash an original boot.img. I guess, root access will be a bit more complicated since the bootloader appears to be locked indeed...
Can you sign the rooted boot image with the same keys as the rest of the b37 firmware? Perhaps, then it will work?
Best regards,
Draco.
ehsan96696 said:
So, few things. After following all of Undead's installation steps (minus using QFIL), and the steps that I listed at the start of this post, I used the miflash from the axon 7 tutorial page here:https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
For some reason any other Miflash would give the previously stated error. I then installed the ZTE Android drivers provided. And using deadman's B37, Miflash worked like a charm!
Click to expand...
Click to collapse
Weird but awesome that it worked
Drakosha said:
Hello.
I flashed B37 with your boot image & TWRP successfully (using MiFlash; QFIL stopped at the same emmc_appsboot file). Except for "TV Mode setup" that was blocking the normal startup, everything went smooth. However, when I attempted to flash Magisk-patched boot image using TWRP, the phone refused to boot, so I had to re-flash an original boot.img. I guess, root access will be a bit more complicated since the bootloader appears to be locked indeed...
Can you sign the rooted boot image with the same keys as the rest of the b37 firmware? Perhaps, then it will work?
Best regards,
Draco.
Click to expand...
Click to collapse
Right now I'm focused on building the aosp instead of editing the current setup more than have. You can use the android image kitchen to unpack the imgs and edit them. I just used notepad to do my edits.
Root
ff7cloudsnobody said:
Right now I'm focused on building the aosp instead of editing the current setup more than have. You can use the android image kitchen to unpack the imgs and edit them. I just used notepad to do my edits.
Click to expand...
Click to collapse
Can you, please, look into this problem and help us obtain root? It is absolutely necessary for this phone outside of US, right now it's just a small tablet Building AOSP is great, but until it's ready, until it supports dualscreen & e.t.c. - there could be weeks or even months... You edited boot image, and this edited boot worked with locked bootloader - witch means, that it is still signed with OEM keys. Please, do this once more with Magisk-patched rooted image.
Thanks in advance,
WBR - Draco
Drakosha said:
Can you, please, look into this problem and help us obtain root? It is absolutely necessary for this phone outside of US, right now it's just a small tablet Building AOSP is great, but until it's ready, until it supports dualscreen & e.t.c. - there could be weeks or even months... You edited boot image, and this edited boot worked with locked bootloader - witch means, that it is still signed with OEM keys. Please, do this once more with Magisk-patched rooted image.
Thanks in advance,
WBR - Draco
Click to expand...
Click to collapse
Ok, so the boot img I had previously sent did not have all secure options disabled, try this one (already magisk patched)
ff7cloudsnobody said:
Ok, so the boot img I had previously sent did not have all secure options disabled, try this one (already magisk patched)
Click to expand...
Click to collapse
Thanks! Unfortunately, this boot does't work, the phone repeatedly boots into recovery (just like a regular boot image after being patched with Magisk). But thank you for your time anyway, with respect - Draco.
Drakosha said:
Thanks! Unfortunately, this boot does't work, the phone repeatedly boots into recovery (just like a regular boot image after being patched with Magisk). But thank you for your time anyway, with respect - Draco.
Click to expand...
Click to collapse
Doing the unpatched boot with security removed works, so this must be something that is in a subsection of boot.img other than build.prop. I'll have to look at what magisk changes, see what other locks ZTE has inside the image, and go from there.
edit: at this point, this conversation is not related to the post. If I make a breakthrough then I will make a new thread.
Hello, thanks for all people, who have written this thread! I bought an Axon M which was bricked. I tried QFIL with the B30 ATT firmware, but it didn't worked. Than, as already mentioned, i have to remove the userdata line from rawprogram , use the firehose from Unjustified Dev from and with MiFlash it worked without any problems. I had problems with getting into the qdloader mode, but i tried several combinations with Power and Volume Buttons, until i got into the qdloader mode.
Hi all
I need Loader please for this AT&T Z999 model
the one I found in this publication did not work for me : https : // forum.xda-developers.com/axon-m/how-to/rom-zte-axon-m-stock-firmware-firehose-t3909847
I just wish this method would work to update the AT&T Axon M from B30 to B37.
tj65 said:
Hello, thanks for all people, who have written this thread! I bought an Axon M which was bricked. I tried QFIL with the B30 ATT firmware, but it didn't worked. Than, as already mentioned, i have to remove the userdata line from rawprogram , use the firehose from Unjustified Dev from and with MiFlash it worked without any problems. I had problems with getting into the qdloader mode, but i tried several combinations with Power and Volume Buttons, until i got into the qdloader mode.
Click to expand...
Click to collapse
Are you able to provide the firehose that you used?
I tried the B37 and the firehost from this link https://forum.xda-developers.com/t/rom-zte-axon-m-stock-firmware-firehose.3909847/
along with the miflash from this link https://forum.xda-developers.com/t/edl-a2017-a2017u-emergency-dl-mode-twrp-unlock-upgrade.3553514/
But it always fails.
It will simply give an error of "Cannot receive hello packet"
then it will eventually go to the error of
"Object reference not set to an instance of an object."
I am using an AT&T Z999 that is on B30, and I am trying to get it updated to B37 (currently not looking to root or anything else, just want to update without having to have active AT&T service.
Edit: I think I found the right one. https://forum.xda-developers.com/t/...-unofficial-twrp-recovery-for-axon-m.3959314/
So far, copying that firehose file into the B37 folder seems to be allowing it to flash.
Phone updated from 13.0.2.0 to 13.0.4.0 accidentally or by itself, not sure, received the latest OTA and after reboot root is gone...
How can i get root back without loosing data or formatting?
You need to reinstall it using adb method, remember: everytime you update you loose the root
xNAPx said:
You need to reinstall it using adb method, remember: everytime you update you loose the root
Click to expand...
Click to collapse
Will i use data/settings if i reinstall magisk via adb?
You mean lose? Nope you won't as you are not formatting anything
xNAPx said:
You mean lose? Nope you won't as you are not formatting anything
Click to expand...
Click to collapse
Sorry, i meant loose data... And last question, which adb method should i use? I don't have twrp installed either as it wasn't available while i was rooting 13.0.2.0... Not sure if it's available now...?
GODSPD said:
Sorry, i meant loose data... And last question, which adb method should i use? I don't have twrp installed either as it wasn't available while i was rooting 13.0.2.0... Not sure if it's available now...?
Click to expand...
Click to collapse
Adb method doesn't need twrp, it is a bit more difficult to inject the root but you don't need to go through twrp. Just search on Google you will find several guides, I can tell you that you need the boot.img of the installed ROM in order to complete the process. You usually find this file into the fastboot ROM zip package
xNAPx said:
Adb method doesn't need twrp, it is a bit more difficult to inject the root but you don't need to go through twrp. Just search on Google you will find several guides, I can tell you that you need the boot.img of the installed ROM in order to complete the process. You usually find this file into the fastboot ROM zip package
Click to expand...
Click to collapse
So I'm guessing it's the same process as last time, the required boot.img will need to be from the updated 13.0.4.0 version? I barely remember how i did it initially, if you have any guides that work id really appreciate it
For the version 13.0.2.0 I used tge boot.img of the same fastboot ROM, I don't know if it would work with another boot.img honestly
I cannot seem to find the boot.img for the latest ota...
xNAPx said:
For the version 13.0.2.0 I used tge boot.img of the same fastboot ROM, I don't know if it would work with another boot.img honestly
Click to expand...
Click to collapse
cannot find a boot.img for 13.0.4, cannot extract it from payload.bin either via python, nothing seems to be working
xNAPx said:
For the version 13.0.2.0 I used tge boot.img of the same fastboot ROM, I don't know if it would work with another boot.img honestly
Click to expand...
Click to collapse
I tried it and boot looped to the bootloader...try at your own risk
tensux said:
I tried it and boot looped to the bootloader...try at your own risk
Click to expand...
Click to collapse
Did you manage to get it done? Apparently you can extract the 13.0.4 boot.img from the roms payload.bin file but i couldn't get it done myself... Did you manage to root yours?
GODSPD said:
Did you manage to get it done? Apparently you can extract the 13.0.4 boot.img from the roms payload.bin file but i couldn't get it done myself... Did you manage to root yours?
Click to expand...
Click to collapse
no in fact I had to switch to xiaomi.eu. i couldnt get anything else to flash. it kept failing at the same spot, i dont quite remember but had the name "super" in it
Just wait for the fastboot ROM guys
xNAPx said:
Just wait for the fastboot ROM guys
Click to expand...
Click to collapse
if we only knew when and where that will be released
Usually a week or two after the recovery release