Question Where to find a boot.img for [Maltose]? - Redmi Note 10S

I made the mistake of reading that the firmware is the same for all three 10S models, and accidentally flashed the wrong magisk-patched boot.img.
Now, to fix my phone i Need to flash the original boot.img, but I can't find online the ROM for the Maltose variant.
Anyone can help?

I was able to find a dump of the file from here. And though that fixed my boot issue (note: the dump says it's for MIUI V12.5.14.0, whereas my phone has version V12.5.13), I still can't get root because when I patch that file with Magisk, and flash it via fastboot, it doesn't boot, and goes to FastBoot until I reflash the original.
So, the question now is, where can I find a patched boot.img for [Maltose]?
Since there's nearly no threads regarding Maltose, it might be best to leave this thread here for future reference of other users.

armaldon said:
I was able to find a dump of the file from here. And though that fixed my boot issue (note: the dump says it's for MIUI V12.5.14.0, whereas my phone has version V12.5.13), I still can't get root because when I patch that file with Magisk, and flash it via fastboot, it doesn't boot, and goes to FastBoot until I reflash the original.
So, the question now is, where can I find a patched boot.img for [Maltose]?
Since there's nearly no threads regarding Maltose, it might be best to leave this thread here for future reference of other users.
Click to expand...
Click to collapse
maltose is rosemary

Okay, that seems correct. I downloaded the RoseMary IMG version 12.5.13.0 and extracted the boot.img file, after flashing it on my device's boot A & B partitions, it does boot correctly.
I am still having issues rooting my phone, but I guess that's a different issue and requires it's own topic.

Related

[Q] WW 10.26.1.7 firmware zip

Hi there,
I've been searching around to find a specific firmware zip for my new tablet, the SKU: WW, Version: 10.26.1.7.
It appears that asus has pulled this file and was wondering if anyone still has this file available somehow.
I soft-bricked my tablet and am not capable of flashing any other (earlier) firmware zip.
Any help would be greatly appreciated.
Yours sincerely,
Rens "Ikkerens" Rikkerink
Ikkerens said:
Hi there,
I've been searching around to find a specific firmware zip for my new tablet, the SKU: WW, Version: 10.26.1.7.
It appears that asus has pulled this file and was wondering if anyone still has this file available somehow.
I soft-bricked my tablet and am not capable of flashing any other (earlier) firmware zip.
Any help would be greatly appreciated.
Yours sincerely,
Rens "Ikkerens" Rikkerink
Click to expand...
Click to collapse
Why can't you download an earlier firmware?
schmeggy929 said:
Why can't you download an earlier firmware?
Click to expand...
Click to collapse
I can, but it always ends up with some kind of error.
I basically tried following the steps you did:
schmeggy929 said:
i downloaded the asus firmware for 10.14.1.47. extract zip and you get a user.zip. extracted the boot.img. I fastboot erase boot, system, format system, data and cache(as you did)
fastboot -i 0x0B05 flash boot boot.img then
fastboot -i 0x0B05 flash system blob then
fastboot -i 0x0B05 flash system UL-K00C-US-10.14.1.47-user.zip
rebooted back into fastboot and bootloader showed 10.14.1.47 version.
Click to expand...
Click to collapse
But on when trying to flash the ***-user.zip, I get this error message:
Code:
$ fastboot -i 0x0B05 flash system UL-K00C-WW-10.14.1.47-user.zip
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi
Edit: My bootloader version shows: WW_epad-10.26.1.7-20131108
Ikkerens said:
I can, but it always ends up with some kind of error.
I basically tried following the steps you did:
But on when trying to flash the ***-user.zip, I get this error message:
Code:
$ fastboot -i 0x0B05 flash system UL-K00C-WW-10.14.1.47-user.zip
target reported max download size of 643825664 bytes
Invalid sparse file format at header magi
Edit: My bootloader version shows: WW_epad-10.26.1.7-20131108
Click to expand...
Click to collapse
you are going to get that along with a few more errors. Wait until it is done. It will take like 10 mins and finish.
when it is done reboot in bootloader and you should see the version change.
schmeggy929 said:
you are going to get that along with a few more errors. Wait until it is done. I will take like 10 mins and finish.
Click to expand...
Click to collapse
You're getting this wrong, it does not do anything. The process immediately quits.
Ikkerens said:
You're getting this wrong, it does not do anything. The process immediately quits.
Click to expand...
Click to collapse
Ok when you get that message do you get a blinking curser?
Ikkerens said:
Hi there,
I've been searching around to find a specific firmware zip for my new tablet, the SKU: WW, Version: 10.26.1.7.
It appears that asus has pulled this file and was wondering if anyone still has this file available somehow.
I soft-bricked my tablet and am not capable of flashing any other (earlier) firmware zip.
Any help would be greatly appreciated.
Yours sincerely,
Rens "Ikkerens" Rikkerink
Click to expand...
Click to collapse
did you make any backup with cwm recovery?
try this:
unpack blob from 47 update
Code:
fastboot flash staging blob
fastboot flash recovery recovery.img
fastboot reboot-bootloader
load recovery, restore your backup
if you have not made any backup with cwm recovery, tell me.
btw fastboot flash system... is not needed here
lpdunwell said:
did you make any backup with cwm recovery?
try this:
unpack blob from 47 update
Code:
fastboot flash staging blob
fastboot flash recovery recovery.img
fastboot reboot-bootloader
load recovery, restore your backup
if you have not made any backup with cwm recovery, tell me.
btw fastboot flash system... is not needed here
Click to expand...
Click to collapse
I have not made a backup using cwm because there was no CWM available for my version.
My tablet was already updated to 4.3 and I (apparently) could not boot the cwm in the development section.
If I would be able to flash a usable recovery, I wouldn't be in this situation anyway as the asus update (.47) is flashable (found an updater-script in the zip).
Ikkerens said:
I have not made a backup using cwm because there was no CWM available for my version.
My tablet was already updated to 4.3 and I (apparently) could not boot the cwm in the development section.
If I would be able to flash a usable recovery, I wouldn't be in this situation anyway as the asus update (.47) is flashable (found an updater-script in the zip).
Click to expand...
Click to collapse
forget what I wrote here. I opened a thread with unbricking instructions. Good luck
lpdunwell said:
forget what I wrote here. I opened a thread with unbricking instructions. Good luck
Click to expand...
Click to collapse
Won't do me any good at the moment, I already managed to brick it even further (couldn't even get into fastboot mode anymore), so I RMA'd it.
Ikkerens said:
Won't do me any good at the moment, I already managed to brick it even further (couldn't even get into fastboot mode anymore), so I RMA'd it.
Click to expand...
Click to collapse
oh crap. sorry about that. I know there's the nvflash, too, but I have no idea how to use that so far...
would you mind telling what exactly happened?
lpdunwell said:
oh crap. sorry about that. I know there's the nvflash, too, but I have no idea how to use that so far...
would you mind telling what exactly happened?
Click to expand...
Click to collapse
Nvflash is inaccessible at the moment, it requires some preparation (you have to prepare it BEFORE you brick it)
Anyway, basically, I bought the tablet a few hours earlier.
Wanted to root it to remove some bloatware and restore some titanium backup thingies.
So I unlocked, rooted, basic stuff.
Went into TB, removed bloatware such as Amazon Kindle and some other irrelevant titles.
That action however, somehow caused it to be unbootable.
So I went into some basic repair stuff, as usual.
Tried to flash a recovery, only to find out, there is no working recovery. Only CWM, which required an earlier version of my bootloader.
So, what next. Restore stock? Downloaded the firmware, found out it was the earlier version of my device, because Asus removed the 4.3-EU version from their website.
So, I downloaded the .47-EU version, opened it. Saw there were no images, merely plain files meant for /system and an updater-script.
I ended up attempting to package my own system.img after that. Created an ext4 image on my computer, moved the files there. Followed the instructions in updater-script, which were mostly symlinks and stuff.
In the end of the updater-script they flashed blob to /staging and boot.img to /boot.
So, I flashed my custom system.img to /system.
Flashed boot
Flashed the blob
And beyond that point, I ended up in a bootloop of my bootloader. I could not hold down volume to enter fastboot or anything. All I could do was watch the asus logo as it constantly rebooted. (And ofcourse, no way to turn it off other than waiting for the battery to die)
Ikkerens said:
Nvflash is inaccessible at the moment, it requires some preparation (you have to prepare it BEFORE you brick it)
Anyway, basically, I bought the tablet a few hours earlier.
Wanted to root it to remove some bloatware and restore some titanium backup thingies.
So I unlocked, rooted, basic stuff.
Went into TB, removed bloatware such as Amazon Kindle and some other irrelevant titles.
That action however, somehow caused it to be unbootable.
So I went into some basic repair stuff, as usual.
Tried to flash a recovery, only to find out, there is no working recovery. Only CWM, which required an earlier version of my bootloader.
So, what next. Restore stock? Downloaded the firmware, found out it was the earlier version of my device, because Asus removed the 4.3-EU version from their website.
So, I downloaded the .47-EU version, opened it. Saw there were no images, merely plain files meant for /system and an updater-script.
I ended up attempting to package my own system.img after that. Created an ext4 image on my computer, moved the files there. Followed the instructions in updater-script, which were mostly symlinks and stuff.
In the end of the updater-script they flashed blob to /staging and boot.img to /boot.
So, I flashed my custom system.img to /system.
Flashed boot
Flashed the blob
And beyond that point, I ended up in a bootloop of my bootloader. I could not hold down volume to enter fastboot or anything. All I could do was watch the asus logo as it constantly rebooted. (And ofcourse, no way to turn it off other than waiting for the battery to die)
Click to expand...
Click to collapse
Since you are unlocked, you can try to flash the recovery (extract it first) of the US version 1.7, should be the same as wwe. Or just even try to flash the whole us update manually. And later change back to the wwe version when it comes available. The 47 update was only a minor ota for 4.2 so no image of recovery or bootloader there.
Sad story. What would have been the safe thing to do, if others wish to root their devices?
Snah001 said:
Since you are unlocked, you can try to flash the recovery (extract it first) of the US version 1.7, should be the same as wwe. Or just even try to flash the whole us update manually. And later change back to the wwe version when it comes available. The 47 update was only a minor ota for 4.2 so no image of recovery or bootloader there.
Click to expand...
Click to collapse
I still had the original recovery flashed, I never overwrote it actually. I needed a custom recovery (such as CWM, TWRP).
Flashing an US update is not possible alltogether, there are some minor differences with hardware compitability and such.
Problem is, I could've downloaded the .47 update, but I had already updated to 4.3 (BL 10.26.1.7)
Ikkerens said:
I still had the original recovery flashed, I never overwrote it actually. I needed a custom recovery (such as CWM, TWRP).
Flashing an US update is not possible alltogether, there are some minor differences with hardware compitability and such.
Problem is, I could've downloaded the .47 update, but I had already updated to 4.3 (BL 10.26.1.7)
Click to expand...
Click to collapse
I don't know if it isn't possible. On the TF700 it was only a line in the build.prop file that made the difference.
I would try it because now you have nothing and when it works you have the us version yes, but at least it works.
pelago said:
Sad story. What would have been the safe thing to do, if others wish to root their devices?
Click to expand...
Click to collapse
This guide worked fine for me; http://forum.xda-developers.com/showthread.php?t=2516215
It's only about what you do with the root ^^
Snah001 said:
I don't know if it isn't possible. On the TF700 it was only a line in the build.prop file that made the difference.
I would try it because now you have nothing and when it works you have the us version yes, but at least it works.
Click to expand...
Click to collapse
Already too late, it has been RMA'd, and then, I had nothing to flash it with.
Ikkerens said:
This guide worked fine for me; http://forum.xda-developers.com/showthread.php?t=2516215
It's only about what you do with the root ^^
Click to expand...
Click to collapse
Well I meant, what should a root user do to try and protect themselves against bricking their device like you did? Is it a matter of making sure that CWM or TWRP is on the device as a recovery partition? And are those available on TF701T yet?
Oh dear. That's a lot gone wrong.
Cwm is available and that works.
It's made by drgravy. I use it in my unbrick tut.
All i can say is, root --> cwm --> backup.
Sent from my GT-I9505 using xda app-developers app
That CWM wouldn't boot for me :/

Attempt to unbrick Axon M with provided Firehose and Firmware files.

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.

Nokia 4.2 Bricked, but can still enter FastBoot

Hello everyone :laugh:!
Tried rooting the Nokia 4.2, did not know which img to use exactly so I tried one from some other shady site and messed up. Luckily, the recovery partition was still working. After trying to boot lots of images, I got tired and accidentally even flashed a Nokia 6.2 TWRP image to my recovery partition. Then I completely messed up. The phone only gets into fastboot now. May I please ask some help of you? I've been trying for days to fix things. I just wanted to root the original firmware. Now when I try to flash TWRP, it even says that the 'recovery' partition has no partition table! I can still write to boot_a and boot_b though. The phone originally had the October patch level, but before bricking it I upgraded it to the December level.
Kind regards,
Alexander47u
Search on google and try do download and flash the stock firmware (unrooted)
Phone does not get detected by QFIL
thegamingcat13 said:
Search on google and try do download and flash the stock firmware (unrooted)
Click to expand...
Click to collapse
I have tried this using QFIL, however the phone is not detected. The phone also goes into fastboot as soon as the cable is plugged in, even when the phone is off.
Have also installed appropiate drivers for QFIL, but no luck.
Extract the system, boot, dtbo, vbmeta and vendor img's from the downloaded archieve and flash those using fastboot
Works, Thank you!
thegamingcat13 said:
Extract the system, boot, dtbo, vbmeta and vendor img's from the downloaded archieve and flash those using fastboot
Click to expand...
Click to collapse
Thank you! This worked flawlessly.
#metoo
Haha, I have done the EXACT same thing as you. Now I can only enter fastboot mode and when I try to flash anything I have downloaded I get an error about missing partitions. I have looked everywhere for details on the partition sizes, mount points and so on but nobody has uploaded the information. In the end I went and purchased a second device in order to dump the entire stock ROM in order to fix the first phone. I've got the second phone running in ADB-mode but I can only backup to an .ab file so now I am back at square one. All of the guides I can find on how to dump the ROM involves flashing TWRP recovery but THERE IS NONE FOR THE 4.2 :crying: And after researching Android forensics I have found a guide to dumping the ROM but it needs root access in the phone shell. All I wanted was root (and LineageOS). Does anyone feel like patching the stock ROM and making a zip-file containing the img-files from all of the partitions?
Hi. You need to check which slot is in use, A or B. You can also choose slot A or B with fastboot. Then you flash the images to the partitions by appending _a or _b to the partition name.
E.g.
fastboot --set-active=a
fastboot flash boot_a boot.img
Etc.
You also need to make sure you have a recent version of fastboot, as the fastboot in some Linux package managers or blog posts for Windows give you the older one, which does not support changing active slots.
Inside the stock rom that can be found online, there is another archive containing the needed images.
alexander47u said:
Hi. You need to check which slot is in use, A or B. You can also choose slot A or B with fastboot. Then you flash the images to the partitions by appending _a or _b to the partition name.
E.g.
fastboot --set-active=a
fastboot flash boot_a boot.img
Etc.
You also need to make sure you have a recent version of fastboot, as the fastboot in some Linux package managers or blog posts for Windows give you the older one, which does not support changing active slots.
Inside the stock rom that can be found online, there is another archive containing the needed images.
Click to expand...
Click to collapse
Thanks for the tip! Looks like I solved it earlier, I found a "user_update" zip in one of the downloaded ROMs and used fastboot update user_update.zip. Wuhu! I did not specify the slot but the system boots up. On the first boot I got an error message asking me to restore factory settings which seemed to work. Now all I need to do is get root access... Alexander, did you manage to flash a rooted recovery now? Thanks in advance!
You need to put the stock boot.img unaltered on a sdcard or the internal storage and then run the Magisk android app. It will offer an option to patch the boot.img. Then you can place the patched boot.img back on your computer and flash it using fastboot.
alexander47u said:
You need to put the stock boot.img unaltered on a sdcard or the internal storage and then run the Magisk android app. It will offer an option to patch the boot.img. Then you can place the patched boot.img back on your computer and flash it using fastboot.
Click to expand...
Click to collapse
I was able to succesfully patch boot.img with magisk, then I copied the patched boot image to my computer with linux. Fastboot flash boot boot.img worked but upon reboot I got an error message saying "corrupt data" and offered to do a factory reset. Any chance you can upload your patched boot image so I can use yours?
Magisk boot.img patched.
http://s000.tinyupload.com/index.php?file_id=49342816027254664129
Posted
alexander47u said:
Magisk boot.img patched.
http://s000.tinyupload.com/index.php?file_id=49342816027254664129
Click to expand...
Click to collapse
You legend! Thank you. Now to see if I can get it to work... what security patch is this up to?
Oslokalle said:
You legend! Thank you. Now to see if I can get it to work... what security patch is this up to?
Click to expand...
Click to collapse
Up to March. I used the stock rom that is floating around on the internet. Not sure if I am allowed to post stock roms.
I was able to update to April using Magisk but not any further than that.
thegamingcat13 said:
Extract the system, boot, dtbo, vbmeta and vendor img's from the downloaded archieve and flash those using fastboot
Click to expand...
Click to collapse
Tried this using a user_update.zip file from www[.]getdroidtips[.]com/stock-rom-nokia-4-2-firmware/. My phone boots again, but Wi-Fi doesn't work. My model # is TA-1133. What should I do?
Edit: tried to install the latest security OTA from t[.]me/nokiarepoen/379, V2.29C, but I get
Code:
E:Package is for source build 00WW_2_29B but expected 00WW_1_17I
. Is there a base user_update for build 00WW_2_29B floating around?
Oslokalle said:
Thanks for the tip! Looks like I solved it earlier, I found a "user_update" zip in one of the downloaded ROMs and used fastboot update user_update.zip. Wuhu! I did not specify the slot but the system boots up. On the first boot I got an error message asking me to restore factory settings which seemed to work. Now all I need to do is get root access... Alexander, did you manage to flash a rooted recovery now? Thanks in advance!
Click to expand...
Click to collapse
Kindly provide me that zip too.

Could someone please post 10.0.14 fastboot?

Hi everyone,
I have some months before accidentally reset after ota update on magisk and lost root. Unfortunately I cant find this FW anywhere since it was almost immediatly been replaced by 10.0.16, and the only thread having such old firmware was using filehosting from which the links expired.
I tried doing a system ota, but it won't work. I don't expect anyone to extract the boot.img for me just share the 10.0.14. if available, i would prefer not to wipe system data, since now without root i can't backup, and Helium is no longer supported.
Thank You.
Ikarus01 said:
Hi everyone,
I have some months before accidentally reset after ota update on magisk and lost root. Unfortunately I cant find this FW anywhere since it was almost immediatly been replaced by 10.0.16, and the only thread having such old firmware was using filehosting from which the links expired.
I tried doing a system ota, but it won't work. I don't expect anyone to extract the boot.img for me just share the 10.0.14. if available, i would prefer not to wipe system data, since now without root i can't backup, and Helium is no longer supported.
Thank You.
Click to expand...
Click to collapse
OTA updates usually don't touch the boot image so you could use the fastboot or recovery ROM V10.0.13.0 from here https://flashxiaomi.com/download-install-miui-rom-for-xiaomi-mi-a2-all-miui-firmwares/ also you can flash a recovery and backup your boot image to patch it through Magisk or flash directly the zip (a lower version)
SubwayChamp said:
OTA updates usually don't touch the boot image so you could use the fastboot or recovery ROM V10.0.13.0 from here https://flashxiaomi.com/download-install-miui-rom-for-xiaomi-mi-a2-all-miui-firmwares/ also you can flash a recovery and backup your boot image to patch it through Magisk or flash directly the zip (a lower version)
Click to expand...
Click to collapse
Thank you for replying,
i thought about it but if it proves not the case, and they changed the hex i wouldnt like bootloops or problems down the road. If it works i will try to backup and go to latest android 9, since many are complaining about version 10 with emmc apparently forgotten.
Also unfortunately i lost twrp, and don't have a sd cardfor flashing,and wouldn't like to wipe data to install twrp.
I thought about it and my only course of action is getting the boot.img, dd is out of option since I am not rot, is there a non root way to unpack if it turns out 10.0.13 causes a bootloop?
Sorry if some things don't make sense I am getting back to this after a long hiatus, can I still extract the img. from zip, or do I have to upack it with python?
Thank you.
Ikarus01 said:
Thank you for replying,
i thought about it but if it proves not the case, and they changed the hex i wouldnt like bootloops or problems down the road. If it works i will try to backup and go to latest android 9, since many are complaining about version 10 with emmc apparently forgotten.
Also unfortunately i lost twrp, and don't have a sd cardfor flashing,and wouldn't like to wipe data to install twrp.
I thought about it and my only course of action is getting the boot.img, dd is out of option since I am not rot, is there a non root way to unpack if it turns out 10.0.13 causes a bootloop?
Sorry if some things don't make sense I am getting back to this after a long hiatus, can I still extract the img. from zip, or do I have to upack it with python?
Thank you.
Click to expand...
Click to collapse
It was a minor/small update, I doubt it causes a bootloop.
You can flash Orange Fox through fastboot, no need to wipe data and from there either just flash Magisk or backup your boot and patch it if you prefer this method.
Not sure to which image you refer, no need to unpack the image by any method.
SubwayChamp said:
It was a minor/small update, I doubt it causes a bootloop.
You can flash Orange Fox through fastboot, no need to wipe data and from there either just flash Magisk or backup your boot and patch it if you prefer this method.
Not sure to which image you refer, no need to unpack the image by any method.
Click to expand...
Click to collapse
Thank you again, for orange fox especially,
I thought I needed Payload dumper, or is that only after android 10?
Thanks for the help, i only liked your replies, i dont know if they removed thanks globally or only on QA forums
Ikarus01 said:
Thank you again, for orange fox especially,
I thought I needed Payload dumper, or is that only after android 10?
Click to expand...
Click to collapse
No, if you refer to a method to unpack the ROM it comes either in zip format (recovery) or in tar.gz format (fastboot), you just need to unpack it with something like Winrar other 7zip and inside you will find the boot image.
It's a global change, in this new platform they removed the thanks option, I disagree but this is how it is.
SubwayChamp said:
No, if you refer to a method to unpack the ROM it comes either in zip format (recovery) or in tar.gz format (fastboot), you just need to unpack it with something like Winrar other 7zip and inside you will find the boot image.
Click to expand...
Click to collapse
Oh that is good to hear!
Thank You again you really helped me here.
Sadly I can only like your post, I guess that is the new rep system?
Have a good day!
Cheers

Question root failed and bootloop

I got a china version OnePlus 10 Pro
i was flashed in oxygen OS A12 EU
I extract the boot.img (52M) from payload.bin today and use magisk cancy to patch
and then i try to fastboot flash boot boot_patched.img
and now start bootloop on one plus splash screen
I can still go to fastboot and fastbootD , I can still flash the payload again but still bootloop
anyone have idea what can i fo to fix ? thanks
leofung_wai said:
I got a china version OnePlus 10 Pro
i was flashed in oxygen OS A12 EU
I extract the boot.img (52M) from payload.bin today and use magisk cancy to patch
and then i try to fastboot flash boot boot_patched.img
and now start bootloop on one plus splash screen
I can still go to fastboot and fastbootD , I can still flash the payload again but still bootloop
anyone have idea what can i fo to fix ? thanks
Click to expand...
Click to collapse
Hey,
If you've only booted the image, then you only need to reboot and the image is lost, the only way that it would be permanent is if it was flashed: fastboot flash not: fastboot boot.
Usually what happens is when you obtain a firmware to install or in your case change region, and you wish to root this firmware you would extract payload.bin then use fastboot enhance to extract the boot.img
Then copy to your phone and patch it with the latest stable Magisk (in this case 24.3)
So again, if you've only booted the image then just reboot your phone and it'll turn on using the actual flashed boot.img from the firmware, not the one you booted.
If that doesn't work then you must have flashed it. In which case you can either re-flash your original boot.img or boot then direct install a correctly patched image for the correct firmware (after a success boot) via Magisk.
leofung_wai said:
I got a china version OnePlus 10 Pro
i was flashed in oxygen OS A12 EU
I extract the boot.img (52M) from payload.bin today and use magisk cancy to patch
and then i try to fastboot flash boot boot_patched.img
and now start bootloop on one plus splash screen
I can still go to fastboot and fastbootD , I can still flash the payload again but still bootloop
anyone have idea what can i fo to fix ? thanks
Click to expand...
Click to collapse
Here's a good "how to" to follow.
https://www.droidwin.com/how-to-root-oneplus-10-pro-via-magisk-patched-boot-img/
Canuck Knarf said:
Here's a good how to to follow.
https://www.droidwin.com/how-to-root-oneplus-10-pro-via-magisk-patched-boot-img/
Click to expand...
Click to collapse
No he has changed region. This is for color OS...he's already done all this.
If you read the OP, he's already on EU 11_A.12
This would just make matters much worse
dladz said:
No he has changed region. This is for color OS...he's already done all this.
If you read the OP, he's already on EU 11_A.12
This would just make matters much worse
Click to expand...
Click to collapse
what you talking about ...it applies to all ...if hes on colors os....oxgyen os..he stills needs ...boot img...vender_boot...and vbmeta. img and magisk
Canuck Knarf said:
what you talking about ...it applies to all ...if hes on colors os....oxgyen os..he stills needs ...boot img...vender_boot...and vbmeta. img and magisk
Click to expand...
Click to collapse
Are you suggesting that the boot.img in color OS is the same as it is in OOS?
You're mistaken if you do think that
They're completely different operating systems, have different system.img's boot.img's, in fact most if not all images are different, to suggest he should obtain a firmware that he's just changed FROM is a bad suggestion..
That's what I'm talking about.
As per the OP, he has changed region, he is no longer using color OS ( the site you suggested is referring to this firmware)
He is now on oxygen OS using the firmware EU 11_A.12
If he was to attempt to use a color OS boot image his phone would continue to be in a boot loop but for a different reason.
Again, this would make things much much worse.
If what he's advised is true then he's successfully changed OS/region and now wants to root, the only thing he's done thus far is to boot a boot image. I think he's flashed it as booting is not permanent, to suggest to go ahead and attempt to obtain a color OS boot image or vendor image is absolutely ridiculous.
He's on an EU firmware. So he requires an EU boot image.
He's in boot loop cause he is booting to A slot...
Thanks for everyone's reply i did change the boot to A and reflash everyone again it can boot now but when i try to root again , it stuck into fastboot mode
dladz said:
Are you suggesting that the boot.img in color OS is the same as it is in OOS?
You're mistaken if you do think that
They're completely different operating systems, have different system.img's boot.img's, in fact most if not all images are different, to suggest he should obtain a firmware that he's just changed FROM is a bad suggestion..
That's what I'm talking about.
As per the OP, he has changed region, he is no longer using color OS ( the site you suggested is referring to this firmware)
He is now on oxygen OS using the firmware EU 11_A.12
If he was to attempt to use a color OS boot image his phone would continue to be in a boot loop but for a different reason.
Again, this would make things much much worse.
Click to expand...
Click to collapse
oxygen OS using the firmware EU 11_A.12.... He still needs boot img ...vender_boot form the firmware EU 11_A.12 . to root
leofung_wai said:
Thanks for everyone's reply i did change the boot to A and reflash everyone again it can boot now but when i try to root again , it stuck into fastboot mode
Click to expand...
Click to collapse
you need to load the firmware EU 11_A.12 to b slot using fastboot enhance
He already had boot?? What are you talking about???
He had a functional OS, in order to root you only need ONE image.
The boot image which comes from OOS. The link you sent is for Color OS?? Make sense now ??
He just needs to patch it correctly and boot it then direct install.
Im going over this again with someone who's incapable of understanding the basics.
Canuck Knarf said:
you need to load the firmware EU 11_A.12 to b slot using fastboot enhance
Click to expand...
Click to collapse
You do realise that booting an image does not need to be directed don't you?
Only by flashing should you direct the image to a particular slot.
By flashing you are permanently flashing an image.
I don't think you understand this so I'll make it simple for you.
You want to root your phone. You have an image you've just patched, from boot.img to magisk_patched.img
Firstly you would want to send this via fastboot, you do not need fastboot enhance for this.
The preferred way to do this is to fastboot boot magisk_patched.img
Why is this preferred??
Because if it fails as it may. Then you are not stuck in a boot loop, you just reboot and you're back in the OS.
The 2nd method is flashing.
fastboot flash boot_a magisk_patched
Press enter.
fastboot flash boot_b magisk_patched
Press enter
fastboot reboot
Press enter.
Now although this can work it is not the preferred method because you aren't just booting the image you are flashing it, this means that if it fails you cannot just reboot and get back to the OS you have to either obtain a new boot image and patch it although you cannot do this yourself as your phone no longer boots or you obtain an already patched boot image, again the last one I wouldn't recommend..
Thanks again but i had a question , i tried to flash or boot a patched boot img , now i can boot and get into system...but still not root
leofung_wai said:
Thanks again but i had a question , i tried to flash or boot a patched boot img , now i can boot and get into system...but still not root
Click to expand...
Click to collapse
Ok so if you've got into the system..
You need to follow the instructions I have in my guide in order to get root...
You can use the boot image I have there.
leofung_wai said:
Thanks again but i had a question , i tried to flash or boot a patched boot img , now i can boot and get into system...but still not root
Click to expand...
Click to collapse
It is always better to patch boot.img of your own version (you can dump it from payload dumper etc.) and then only fastboot boot patched_image.img and then directly install it via Magisk.
Boot this image.
192 MB folder on MEGA
mega.nz
Yes i did dump from my own and patched by magisk cancy , but it still ...get in normally
Do not flash it.
If your phone boots to the OS, then open Magisk and click install. Direct install and you're done
leofung_wai said:
Yes i did dump from my own and patched by magisk cancy , but it still ...get in normally
Click to expand...
Click to collapse
If you've patched your own image and booted it then click Magisk then install. Then direct install and you're done..
dladz said:
Do not flash it.
If your phone boots to the OS, then open Magisk and click install. Direct install and you're done
Click to expand...
Click to collapse
thanks i success root by your image now
but i had a question, i messed up the slot B and now can only boot through slot A Will it affect anything

Categories

Resources