Database Info

[DUMP] Official Singapore Sense 32A

Hi all,
I've downloaded the RUU and have uploaded the RUU, as well as the images within it.
RUU:
http://rapidshare.com/files/3053191...E_3.03.707.5_R_SG_release_signed_NoDriver.exe
boot.img, recovery.img, splash1_HTC_Magic.nb0, system.img, userdata.img (I know some of these are not needed but I'm just posting things as they are, the original name was rom1.zip):
http://rapidshare.com/files/305319407/system_boot_recovery.zip
boot_special.img, hboot_7200A_1.76.0007_090804.nb0, radio.img (originally rom.zip)
http://rapidshare.com/files/305301844/other_imgs.zip
And yes, you can use the RUU directly but your radio will be overwritten. This is more for the devs/cooks!

failed to unyaffs system.img..when unyaffs to "system/libs",it crashed...sobbing..

Hi, would it be possible to update my radio only? How would I do that?
Replace the radio.img into a zip file with the proper xml and directories and name it as update.zip ?

noob question : can i apply the RUU directly on unrooted magic ?

Remobero said:
noob question : can i apply the RUU directly on unrooted magic ?
Click to expand...
Click to collapse
Yes, you can.

You can but you will get the perfect spl as well.
Ayerwin: thats weird i didnt do anything, got them straight from the ruu. Can someone else try? I dont have access to a pc now.

Wysie said:
You can but you will get the perfect spl as well.
Ayerwin: thats weird i didnt do anything, got them straight from the ruu. Can someone else try? I dont have access to a pc now.
Click to expand...
Click to collapse
i have perfect spl anyway on high built (2.56.415.5) so i guess i can't root my magic anyway .. all i am worried about is the Arabic font .. can i inject it later ?

Wysie said:
Hi all,
I've downloaded the RUU and have uploaded the RUU, as well as the images within it.
RUU:
http://rapidshare.com/files/3053191...E_3.03.707.5_R_SG_release_signed_NoDriver.exe
boot.img, recovery.img, splash1_HTC_Magic.nb0, system.img, userdata.img (I know some of these are not needed but I'm just posting things as they are, the original name was rom1.zip):
http://rapidshare.com/files/305319407/system_boot_recovery.zip
boot_special.img, hboot_7200A_1.76.0007_090804.nb0, radio.img (originally rom.zip)
http://rapidshare.com/files/305301844/other_imgs.zip
And yes, you can use the RUU directly but your radio will be overwritten. This is more for the devs/cooks!
Click to expand...
Click to collapse
Thanks man

Wysie said:
You can but you will get the perfect spl as well.
Ayerwin: thats weird i didnt do anything, got them straight from the ruu. Can someone else try? I dont have access to a pc now.
Click to expand...
Click to collapse
Yes. I succefully unyaffs'ed system.img
Download:
http://rapidshare.com/files/305427401/system_unyaffsed.rar.html
4shared system_unyaffsed.rar
p.s. Can anybody compile mkbootfs, mkbootimg for win32 ?

5[Strogino] said:
Yes. I succefully unyaffs'ed system.img
Download:
http://rapidshare.com/files/305427401/system_unyaffsed.rar.html
4shared system_unyaffsed.rar
p.s. Can anybody compile mkbootfs, mkbootimg for win32 ?
Click to expand...
Click to collapse
Thanks for the update!

Is there a way to have this rom but with a NONPERFECT SPL???

Hmm... Cursed or Blessed?
I am an Android app developer. I just tried using RUU to flash the image with out noticing it has perfected SPL etc....
Now, I am not able to go back to 1.6 custom AmonRA's image..
Am I blessed or Cursed?
THanks.
Andfreek!

So sad but me too!
I really want to get out of the perfected SPL but don't know how. let's pray for the one who save us...
andfreek said:
I am an Android app developer. I just tried using RUU to flash the image with out noticing it has perfected SPL etc....
Now, I am not able to go back to 1.6 custom AmonRA's image..
Am I blessed or Cursed?
THanks.
Andfreek!
Click to expand...
Click to collapse

Thanks for the dumps
Wysie,
Thanks for the dumps. I don't use Windows and I had no access to the contents of the RUU without your dumps.
For the life of me, I can't figure out why companies like HTC which use Free/Open Source Software like Linux don't make their update tools to run on Linux.

flash system.img fails
I have RAmon 1.2.3H recovery. I was able to flash the boot.img from the dump. However it fails on
fastboot flash system system.img

hcadiz said:
I have RAmon 1.2.3H recovery. I was able to flash the boot.img from the dump. However it fails on
fastboot flash system system.img
Click to expand...
Click to collapse
mine too failed at system.img, how to fix it using HTC Magic Rogers 32A

paindoo said:
mine too failed at system.img, how to fix it using HTC Magic Rogers 32A
Click to expand...
Click to collapse
the image file is as big as a hero image, wouldn't fit into you system partition. RUU changes partitioning on the phone to make system bigger as in Hero.
We need to find out how to change the size of a partition in Magic by Hand!

shwan_3 said:
the image file is as big as a hero image, wouldn't fit into you system partition. RUU changes partitioning on the phone to make system bigger as in Hero.
We need to find out how to change the size of a partition in Magic by Hand!
Click to expand...
Click to collapse
It seems you are right, I was able to install non-senseui roms quite easily using the method described in 1st post. How to increase the size of system partition Hmmmmmm!!!

I'm hoping that some developer give us this rom with the radio version and everything but with root...

HTC just released the ROM for other Countrys (Indonesia, Malaysia & Vietnam) but i doubt that there are differences to the Singapore ROM.

LineageOS 13.0 For K10 MTK

Hi all! I build LineageOS 13 for LG K10 MTK. But I can not check on my phone . Who will be able to test? Need wipe data and install LineageOS with TWRP. MOD EDIT

Keep it up!

If I install this rom on my phone and it will not work Can I install firmware rom with lg up, but I need dll file(from .kdz file) to replace in lg up folder. I don't want to have bricked device. (Sorry for bad english)

Singular777 said:
Hi all! I build LineageOS 13 for LG K10 MTK. But I can not check on my phone . Who will be able to test? Need wipe data and install LineageOS with TWRP.
Click to expand...
Click to collapse
I'm glad to see there is development on K10 but why the heck would you make this when on mtk devices can't be flashed anything not even recovery because of "check function" on Qualcomm it was on aboot partition on Mediatek it's probably on lk. Please announce that before someone screw their phone for no reason.
Also if you make a rom thread make it to look like something like pvineth Lineage thread, add some info and device tree and such things with this info it could be tampered bomb inside..

Why u can't?
---------- Post added at 03:43 AM ---------- Previous post was at 03:42 AM ----------
Singular777 said:
Hi all! I build LineageOS 13 for LG K10 MTK. But I can not check on my phone . Who will be able to test? Need wipe data and install LineageOS with TWRP. Download
Click to expand...
Click to collapse
Why u can't test?

it's not working :/
i booted in TWRP then wiped data, installed LineageOS and Gapps and rebooted.
and phone booted to lg logo and showed message device is corrupt and powered off

Singular777 said:
Hi all! I build LineageOS 13 for LG K10 MTK. But I can not check on my phone . Who will be able to test? Need wipe data and install LineageOS with TWRP. MOD EDIT
Click to expand...
Click to collapse
Hello,
Kindly check, confirm if this is useful and safe for other users. Please mention what are the RISKS AND REPERCUSSIONS if the flash is not successful.
It is most important
Thanks

Singular777 said:
Hi all! I build LineageOS 13 for LG K10 MTK. But I can not check on my phone . Who will be able to test? Need wipe data and install LineageOS with TWRP. MOD EDIT
Click to expand...
Click to collapse
I believe that lg's security system from the 2017 febr. update prevents flashing/loading any modified boot image. So you need your stock firmware to be older than 2017 febr. to flash this OS (if i'm not mistaken it only flashes the boot, the recovery and the system partition). On the other hand you cannot modify the recovery partition at all, no matter the security patch date so before flashing this mod you need to backup your recovery partition and restore it after installing this zip - otherwise you will naturaly get shut off after the device corrupt message.
If you could build it for the k8 (k350n) i could give it a try. Please confirm that it only flashes the boot, recovery and system partition and it's not messing with lk, laf and preloader - so we can recover with lg up if anything goes wrong.
Thanks anyways!
PS. do you think its enough if i just exchange the "boot.img-kernel" file in the boot image in you're zip to mine from k8? all other necessery files looks the same (like fstab and init files). I'm also not sure if i should change the .m253. files to .mm1v. files (like ueventd.m253.rc -> ueventd.mm1v.rc and init.m253.rc -> init.mm1v.rc, etc... all files that are m253 in your boot image are mm1v in my boot image but their contents are the same). So should i exchange them or leave them untouched?

So to test it i must downgrade ROM to earlier version than 2017 feb?

a_lewicki said:
So to test it i must downgrade ROM to earlier version than 2017 feb?
Click to expand...
Click to collapse
Exactly. Also i believe that it has to be ported (not built) for each type (or some) of the k10 variants (https://forum.xda-developers.com/lg-k10/development/stock-versions-model-lg-k10-t3457319) since there might be some difference in the hardware.
Another thing is the recovery partition. The zip itself does not contain any recovery related parts. However the OS might check the recovery during boot up and it might change the recovery partition which means it will fail to boot up again. But i didn't find anything in the zip that would change the most important partitions like lk, bootloader and laf so i'm 99% sure that we can use lg up or lg brigde to recover if we get soft bricked.

Singular777 said:
Hi all! I build LineageOS 13 for LG K10 MTK. But I can not check on my phone . Who will be able to test? Need wipe data and install LineageOS with TWRP. MOD EDIT
Click to expand...
Click to collapse
I can confirm that it's not hard bricking the device so the stock firmware can be easily reflashed by lg up (i tested three times). However i tried to port it to my k8 but i didn't succeed (never booted up).
So would you be so kind as building one for the k8? More specifically k8 - k350n. I believe you need the source (i guess it's LGK350N):
http://opensource.lge.com/osSch/list?types=ALL&search=k350n
and maybe device tree (if it is really the device tree):
https://forum.xda-developers.com/lg-k8/development/device-tree-device-tree-lg-k350xxx-t3549783
the firmwares you can find here: https://lg-firmwares.com/lg-k350n-firmwares/
Let me know if you need anything else and thanks in advance.
Naturally i don't expect you to make it, i understand if you don't. It would be just nice if you did and you'd probably make many k8 users happy...

gottlasz said:
I can confirm that it's not hard bricking the device so the stock firmware can be easily reflashed by lg up (i tested three times). However i tried to port it to my k8 but i didn't succeed (never booted up).
So would you be so kind as building one for the k8? More specifically k8 - k350n. I believe you need the source (i guess it's LGK350N):
http://opensource.lge.com/osSch/list?types=ALL&search=k350n
and maybe device tree (if it is really the device tree):
https://forum.xda-developers.com/lg-k8/development/device-tree-device-tree-lg-k350xxx-t3549783
the firmwares you can find here: https://lg-firmwares.com/lg-k350n-firmwares/
Let me know if you need anything else and thanks in advance.
Naturally i don't expect you to make it, i understand if you don't. It would be just nice if you did and you'd probably make many k8 users happy...
Click to expand...
Click to collapse
Hi, I'll try to collect the firmware for K8

Singular777 said:
Hi, I'll try to collect the firmware for K8
Click to expand...
Click to collapse
Thank you for your time and efforts! Let me know if i can help!

This'll not work as long as bootloader acts as if it's not unlocked even though we applied the steps to unlock it.
a_lewicki said:
it's not working :/
i booted in TWRP then wiped data, installed LineageOS and Gapps and rebooted.
and phone booted to lg logo and showed message device is corrupt and powered off
Click to expand...
Click to collapse
And it's this what'll happen.

gottlasz said:
I believe that lg's security system from the 2017 febr. update prevents flashing/loading any modified boot image. So you need your stock firmware to be older than 2017 febr. to flash this OS (if i'm not mistaken it only flashes the boot, the recovery and the system partition). On the other hand you cannot modify the recovery partition at all, no matter the security patch date so before flashing this mod you need to backup your recovery partition and restore it after installing this zip - otherwise you will naturaly get shut off after the device corrupt message.
If you could build it for the k8 (k350n) i could give it a try. Please confirm that it only flashes the boot, recovery and system partition and it's not messing with lk, laf and preloader - so we can recover with lg up if anything goes wrong.
Thanks anyways!
PS. do you think its enough if i just exchange the "boot.img-kernel" file in the boot image in you're zip to mine from k8? all other necessery files looks the same (like fstab and init files). I'm also not sure if i should change the .m253. files to .mm1v. files (like ueventd.m253.rc -> ueventd.mm1v.rc and init.m253.rc -> init.mm1v.rc, etc... all files that are m253 in your boot image are mm1v in my boot image but their contents are the same). So should i exchange them or leave them untouched?
Click to expand...
Click to collapse
@berkantkz
Hey what do you think, is it possible that mtk versions of K10/K8 are using this ?
To your "p.s." It's not enough to replace kernel image and it's files if the rom is built from source it is built for different chipset (still mediatek tho but different) so it probably won't work at all.

Professor Woland said:
@berkantkz
Hey what do you think, is it possible that mtk versions of K10/K8 are using this ?
To your "p.s." It's not enough to replace kernel image and it's files if the rom is built from source it is built for different chipset (still mediatek tho but different) so it probably won't work at all.
Click to expand...
Click to collapse
I didn't understand what you've asked for on that link. It's only a guide.
Chipset model doesn't matter. If the configurations are OK to work on our model, there will be no problem or very little which aren't major.
We need to achieve unlocked bootloader. It can be unlocked by oem unlock command but it isn't actually. We have to manage to fix this. Then everything will be fine that our devices are MTK and easy to port rom stuff.
Sent from my LG K10 using XDA Labs

berkantkz said:
I didn't understand what you've asked for on that link. It's only a guide.
Chipset model doesn't matter. If the configurations are OK to work on our model, there will be no problem or very little which aren't major.
We need to achieve unlocked bootloader. It can be unlocked by oem unlock command but it isn't actually. We have to manage to fix this. Then everything will be fine that our devices are MTK and easy to port rom stuff.
Sent from my LG K10 using XDA Labs
Click to expand...
Click to collapse
Sorry for badly explained question. The link I posted talk about "verified boot" it's used to verify system, kernel and other images, so I thought maybe our phones use this too. But errors are different a little bit here take a look on this too

Professor Woland said:
Sorry for badly explained question. The link I posted talk about "verified boot" it's used to verify system, kernel and other images, so I thought maybe our phones use this too. But errors are different a little bit here take a look on this too
Click to expand...
Click to collapse
Both links regard to the same thing.
You're right, it's used on our devices that's why we can't flash anything over the stocks.
As usual, this warn should gone after bootloader unlock but as I told before, it doesn't act like unlocked, still thinks locked so the warn doesn't go away.
Sent from my LG K10 using XDA Labs

berkantkz said:
Both links regard to the same thing.
You're right, it's used on our devices that's why we can't flash anything over the stocks.
As usual, this warn should gone after bootloader unlock but as I told before, it doesn't act like unlocked, still thinks locked so the warn doesn't go away.
Sent from my LG K10 using XDA Labs
Click to expand...
Click to collapse
It's not the same link, but it doesn't matter, however if this is same thing as on our phones this should be able to help us https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
I don't think that bootloader stay locked but that there is some verification and if it fails device won't boot.

Professor Woland said:
It's not the same link, but it doesn't matter, however if this is same thing as on our phones this should be able to help us https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
I don't think that bootloader stay locked but that there is some verification and if it fails device won't boot.
Click to expand...
Click to collapse
Well, actually, I didn't mention links as the same. They're different links. I meant talks about the same thing. Well, this is not matter.
That thread you linked seems useful. I'll look on it. And your p.s. seems sensible.
Sent from my LG K10 using XDA Labs

XT1575 Stock MPHS24.49-18-16 Files

I am being super kind and uploading stock images of the latest December patch for the Moto X Pure (NOT STYLE). These can be used to relock your bootloader or just reflash stock. HOWEVER I DO NOT HAVE THE STOCK SYSTEM.IMG, BUT I DO HAVE A DECOMPRESSED VERSION. If you can figure out how to compress it into sparse-chunks and make it work, go ahead. I have tried it and it won't flash when the bootloader is locked. I have tested all files, and all of them flash on locked bootloaders/oem lock begin command, EXCEPT FOR SYSTEM.IMG
DRIVE LINK : https://drive.google.com/open?id=0Bzrcf9ndDGw_U19EckExeWxiNG8
PayPal donations are welcome at [email protected]

Did you do it with flashfire app? @parker.stephens

dzidexx said:
Did you do it with flashfire app? @parker.stephens
Click to expand...
Click to collapse
If you're taking about flashing the files no, I use fastboot. If you're taking about how I got the files, I used dd.

There is a tool for splitting the system image into sparse chunks... I'll see if I can find the process.
Can I ask how you got this? Did you extract it from your device because the radio partitions are protected (or so I thought, haven't tried it in a long time).
Just curious how you were able to read some of these partitions...
EDIT: Found it I think: https://forum.xda-developers.com/showthread.php?t=2749797

acejavelin said:
There is a tool for splitting the system image into sparse chunks... I'll see if I can find the process.
Can I ask how you got this? Did you extract it from your device because the radio partitions are protected (or so I thought, haven't tried it in a long time).
Just curious how you were able to read some of these partitions...
EDIT: Found it I think: https://forum.xda-developers.com/showthread.php?t=2749797
Click to expand...
Click to collapse
I used TWRP, but instead of flashing it, I send it as a boot image.
Instead of "fastboot flash recovery twrp.img", I used "fastboot boot twrp.img", which allowed me to get the partitions.
EDIT: SparseConverter gives me different sizes of chunks with MPHS24.49-18-8 with 8, and MPHS24.49-18-16 with 13. MPHS24.49-18-16 has each of the files being 262,144 KB and a total size of 3.17 GB. MPHS24.49-18-8 is only 1.98 GB. Here's the weird part. The decompressed system.img files are on KB apart. MPHS24.49-18-8 is 4,194,180 and MPHS24.49-18-16 is 4,194,304 KB. I'm not sure where things are going wrong, which is why I want someone else to try.

parker.stephens said:
I used TWRP, but instead of flashing it, I send it as a boot image.
Instead of "fastboot flash recovery twrp.img", I used "fastboot boot twrp.img", which allowed me to get the partitions.
EDIT: SparseConverter gives me different sizes of chunks with MPHS24.49-18-8 with 8, and MPHS24.49-18-16 with 13. MPHS24.49-18-16 has each of the files being 262,144 KB and a total size of 3.17 GB. MPHS24.49-18-8 is only 1.98 GB. Here's the weird part. The decompressed system.img files are on KB apart. MPHS24.49-18-8 is 4,194,180 and MPHS24.49-18-16 is 4,194,304 KB. I'm not sure where things are going wrong, which is why I want someone else to try.
Click to expand...
Click to collapse
But how did you extract the radio images? Used to be they were protected, if you tried it looked like it worked but you always got nothing but 0's in the image file for fsg and nonhlos

acejavelin said:
But how did you extract the radio images? Used to be they were protected, if you tried it looked like it worked but you always got nothing but 0's in the image file for fsg and nonhlos
Click to expand...
Click to collapse
Like I said, I used dd. I am going to flash it to my Moto X Pure and double-check it works and edit this post if it does or doesn't.
EDIT: All is well. Wi-Fi works, Cellular on Verizon gets 5 bars, and Bluetooth works also except for the reboot glitch where Bluetooth turns itself off. The command I used were fastboot flash modem NON-HLOS.bin, fastboot flash fsg fsg.mbn, fastboot erase modemst1, and fastboot erase modemst2

parker.stephens said:
Like I said, I used dd. I am going to flash it to my Moto X Pure and double-check it works and edit this post if it does or doesn't.
EDIT: All is well. Wi-Fi works, Cellular on Verizon gets 5 bars, and Bluetooth works also except for the reboot glitch where Bluetooth turns itself off. The command I used were fastboot flash modem NON-HLOS.bin, fastboot flash fsg fsg.mbn, fastboot erase modemst1, and fastboot erase modemst2
Click to expand...
Click to collapse
Awesome! My concern was that in previous devices, extraction of the radio firmware with DD was protected, it would only output all zeros in the image, seems that isn't the case anymore!
I will try to look at the system thing this weekend, I'm out of town til Sunday so i am limited at the moment. Can you put the raw system img file on drive?

why not download the latest software directly from motorola?
XT1575 01-SEP-16 MPH24.49-18_18 6.0 1208
https://motorola-global-portal.custhelp.com/app/standalone%2Fbootloader%2Frecovery-images#

Alibaba0101 said:
why not download the latest software directly from motorola?
XT1575 01-SEP-16 MPH24.49-18_18 6.0 1208
https://motorola-global-portal.custhelp.com/app/standalone%2Fbootloader%2Frecovery-images#
Click to expand...
Click to collapse
Because Motorola doesn't update that. The image there is from November 2015. That is the 1st marshmallow image shipped with Moto X Pure. A.K.A MPHS24.49-18. It is also not the latest.

Alibaba0101 said:
why not download the latest software directly from motorola?
XT1575 01-SEP-16 MPH24.49-18_18 6.0 1208
https://motorola-global-portal.custhelp.com/app/standalone%2Fbootloader%2Frecovery-images#
Click to expand...
Click to collapse
parker.stephens said:
Because Motorola doesn't update that. The image there is from November 2015. That is the 1st marshmallow image shipped with Moto X Pure. A.K.A MPHS24.49-18. It is also not the latest.
Click to expand...
Click to collapse
@parker.stephens is correct, the image on Moto's website is ancient, literally the oldest Marshmallow image ever made for the Moto X. It has been reported to Moto in their official forums like 6 months ago and they said they would get it taken care of but nothing has changed.
We have official leaked factory images up to MPHS24.49-18-8... the OP is trying to get 18-16 for us to use... the one on Moto's website is MPHS24.49-18 (with NO subversion), it is labeled and dated incorrectly.

acejavelin said:
@parker.stephens is correct, the image on Moto's website is ancient, literally the oldest Marshmallow image ever made for the Moto X. It has been reported to Moto in their official forums like 6 months ago and they said they would get it taken care of but nothing has changed.
We have official leaked factory images up to MPHS24.49-18-8... the OP is trying to get 18-16 for us to use... the one on Moto's website is MPHS24.49-18 (with NO subversion), it is labeled and dated incorrectly.
Click to expand...
Click to collapse
Where is the MPHS24.49-18-8 image posted? I could only find MPHS24.49-18-4 on the FirmwareNstuff thread.

annoyingduck said:
Where is the MPHS24.49-18-8 image posted? I could only find MPHS24.49-18-4 on the FirmwareNstuff thread.
Click to expand...
Click to collapse
https://firmware.center/firmware/Motorola/

parker.stephens said:
I am being super kind and uploading stock images of the latest December patch for the Moto X Pure (NOT STYLE). These can be used to relock your bootloader or just reflash stock. HOWEVER I DO NOT HAVE THE STOCK SYSTEM.IMG, BUT I DO HAVE A DECOMPRESSED VERSION. If you can figure out how to compress it into sparse-chunks and make it work, go ahead. I have tried it and it won't flash when the bootloader is locked. I have tested all files, and all of them flash on locked bootloaders/oem lock begin command, EXCEPT FOR SYSTEM.IMG
DRIVE LINK : https://drive.google.com/open?id=0Bzrcf9ndDGw_U19EckExeWxiNG8
PayPal donations are welcome at [email protected]
Click to expand...
Click to collapse
How did you get gpt.bin and bootloader.img?

yk1999 said:
How did you get gpt.bin and bootloader.img?
Click to expand...
Click to collapse
Tapa?
Post #3.

dzidexx said:
Tapa?
Post #3.
Click to expand...
Click to collapse
But there is no pertition called gpt(gpt is the partition table itself)
And bootloader.img contain pmic aboot tz etc i can get them separately using dd but can't get them in one bootloader.img

I didn't think,
Sorry. @yk1999
---------- Post added at 11:37 AM ---------- Previous post was at 11:37 AM ----------
I didn't think,
Sorry.
 @yk1999

is this our nougougt update!?!?
or at least the files we need to get the other ROMs stable??

abense said:
is this our nougougt update!?!?
or at least the files we need to get the other ROMs stable??
Click to expand...
Click to collapse
No, this is marshmallow.

Did anyone already perform a system restore after processing with sparse converter by any chance?

HTC U11+ Stock Recovery 1.24.401.7

Hi everyone! By any chance someone has the stock recovery of U11+ EMEA/Europe version? 1.24.401.7 version..

stock recovery U11+ 1.24.401.7
ShinGaiven said:
Hi everyone! By any chance someone has the stock recovery of U11+ EMEA/Europe version? 1.24.401.7 version..
Click to expand...
Click to collapse
Have a look here if thats what you're looking for
Here is another link, if that helps you. Good Luck

freebsd124 said:
Have a look here if thats what you're looking for
Here is another link, if that helps you. Good Luck
Click to expand...
Click to collapse
Thanks for trying mate! Unfortunately the link is giving me the OTA RUU file, basically what I'm trying to find is only the stock recovery.img file for the specific version.

ShinGaiven said:
Thanks for trying mate! Unfortunately the link is giving me the OTA RUU file, basically what I'm trying to find is only the stock recovery.img file for the specific version.
Click to expand...
Click to collapse
Ok, I understand; still wanna give you a heads up. If you download the RUU file representing your version (1.24.401.7) you need to use the RUU_decrypt_tool to be able to extract the recovery.img
This link might give you the information you possibly need.
I hope it helps you; I know what it feels like not having the .img-files if you, sort of, stuck

freebsd124 said:
Ok, I understand; still wanna give you a heads up. If you download the RUU file representing your version (1.24.401.7) you need to use the RUU_decrypt_tool to be able to extract the recovery.img
This link might give you the information you possibly need.
I hope it helps you; I know what it feels like not having the .img-files if you, sort of, stuck
Click to expand...
Click to collapse
Wow! Thanks for this one when I'm free I'll try that and will update you. In fact the phone I'm using is working out fine. This is a Demo unit for commercial purposes and by default demo content keeps running in the background and wipe out Data agressively..I unlocked bootloader, flashed TWRP, and mount system partition and deleted the Demo file manually. The reason why I need the img file is for me to restore the stock recovery and try if it's gonna work. I've done on my U11 and wanted to give it a try on my plus version..

recovery.img file
ShinGaiven said:
Wow! Thanks for this one when I'm free I'll try that and will update you. In fact the phone I'm using is working out fine. This is a Demo unit for commercial purposes and by default demo content keeps running in the background and wipe out Data agressively..I unlocked bootloader, flashed TWRP, and mount system partition and deleted the Demo file manually. The reason why I need the img file is for me to restore the stock recovery and try if it's gonna work. I've done on my U11 and wanted to give it a try on my plus version..
Click to expand...
Click to collapse
If you extracted the recovery_signed.img file rename it to recovery.img, just to be shure (I did) from there on its just "fastboot flash recovery recovery.img" (without the quotes)

can someone help me get the stock recovery for htc u11 plus 2.19.401.2 EU.
Thanks

Firmware updates for daisy

Hello guys, a brief introduction; All the Xiaomi devices running Miui roms out of the box have a dedicated firmware but I didn´t find for those based on Android One or atleast for Daisy.
Every rom requires a specific Firmware to work well so I´ll share the most used here.
This is intended to flash it as a base to avoid the tedious process to flash the whole rom through MiFlash tool.
But be advised although that some times could be required to do a clean flash through MiFlash tool, for some roms or to fix missed partitions being the case as happen too with all the rest of Xiaomi devices and some times flashing the firmware and the vendor from the same version through fastboot will be enough.
I hope that it´ll be useful, please hit thanks if it works, test it, report and share with others the results.
Download Link:
https://drive.google.com/open?id=1Bbt_aTOHABMYQQlVNTy7X0MVJBJoHqgJ

Dont work on daisy (android one)?:crying:

heyimvitor2 said:
Dont work on daisy (android one)?:crying:
Click to expand...
Click to collapse
They´re for Daisy, stock rom is Android One.

Are these just a repack of the fastboot ROMs available from xiaomi?
They are already listed here. And are .tar.gz rather than .zip
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871

How to use it? Flash via twrp?

fastboot with miflash

a1291762 said:
Are these just a repack of the fastboot ROMs available from xiaomi?
They are already listed here. And are .tar.gz rather than .zip
https://forum.xda-developers.com/mi-a2-lite/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824871
Click to expand...
Click to collapse
Fastboot rom is the whole rom including system, userdata, and more as you know to be flashed through fastboot directly or using a tool like MiFlash but these are not a repack but a flashable zip the way that all the update process to switch to other rom can be done while in TWRP.
Cause all my previous devices were running Miui they had available firmwares and never need to flash all the rom as a base for custom roms and since I bought this device I missed this feature.
Here you have a reference what I´m talking about https://xiaomifirmwareupdater.com

prodang2509 said:
How to use it? Flash via twrp?
Click to expand...
Click to collapse
Yes, as any flashable zip, recommendable as first step (as a base) after to make the wipes and before the other required steps.

dochdoc said:
fastboot with miflash
Click to expand...
Click to collapse
Nope, zips can´t be flashed through fastboot.

https://docs.google.com/spreadsheets/d/1Uy6qouIV0WbVouK4X5PhmUz2quxfLguHDqSf6LYDBO8/edit#gid=0
here you have all flashable stock trough miflash/fastboot

SubwayChamp said:
these are a flashable zip the way that all the update process to switch to other rom can be done while in TWRP.
Click to expand...
Click to collapse
I'm used to the fastboot ROMs but these may prove useful... Is there a process for converting a fastboot ROM into a twrp-flashable ROM?

a1291762 said:
I'm used to the fastboot ROMs but these may prove useful... Is there a process for converting a fastboot ROM into a twrp-flashable ROM?
Click to expand...
Click to collapse
If you refer to the whole rom yes, it does. Other Xiaomi devices have a fastboot (tar) and also a recovery (zip) but TWRP must be adapted to work with.

Thank you for this, it is really helpful.
Last night I played with offains TWRP 3.3.1-0 and restored a firmware backup, but it only got deleted and restoring failed.
Then I flashed your 10.3.0 file and all is good. You also put a custom dark splash.img in it, which I really like (was too lazy to create my own). :good:

Firmware 10.0.15
SubwayChamp said:
Hello guys, a brief introduction; All the Xiaomi devices running Miui roms out of the box have a dedicated firmware but I didn´t find for those based on Android One or atleast for Daisy.
Every rom requires a specific Firmware to work well so I´ll share the most used here.
This is intended to flash it as a base to avoid the tedious process to flash the whole rom through MiFlash tool.
But be advised although that some times could be required to do a clean flash through MiFlash tool, for some roms or to fix missed partitions being the case as happen too with all the rest of Xiaomi devices and some times flashing the firmware and the vendor from the same version through fastboot will be enough.
I hope that it´ll be useful, please hit thanks if it works, test it, report and share with others the results.
Download Link:
https://drive.google.com/open?id=1Bbt_aTOHABMYQQlVNTy7X0MVJBJoHqgJ
Click to expand...
Click to collapse
Do you have also the newest firmware 10.0.15? I have a bug with screen rotation (not longer works after a few hours), i hope firmware 10.0.15 is the solution because because I read that a screen rotation error is known.

counti said:
Do you have also the newest firmware 10.0.15? I have a bug with screen rotation (not longer works after a few hours), i hope firmware 10.0.15 is the solution because because I read that a screen rotation error is known.
Click to expand...
Click to collapse
Firmware is based on major updates i.e. on fastboot global images (full rom) when all partitions are modified but is not included in OTA updates (incremental rom) when mostly only system and vendor (sometimes also kernel) receive modifications but all the other partitions remain untouched.
To better understanding the three next OTA updates (v10.0.14.0, v10.0.15.0 and v10.0.16.0) are using as base v10.0.13.0 firmware.
Just appear the next full rom I will upload it but hopefully it is 10.

Great Job !
SubwayChamp said:
Hello guys, a brief introduction; All the Xiaomi devices running Miui roms out of the box have a dedicated firmware but I didn´t find for those based on Android One or atleast for Daisy.
Every rom requires a specific Firmware to work well so I´ll share the most used here.
This is intended to flash it as a base to avoid the tedious process to flash the whole rom through MiFlash tool.
But be advised although that some times could be required to do a clean flash through MiFlash tool, for some roms or to fix missed partitions being the case as happen too with all the rest of Xiaomi devices and some times flashing the firmware and the vendor from the same version through fastboot will be enough.
I hope that it´ll be useful, please hit thanks if it works, test it, report and share with others the results.
Download Link:
https://drive.google.com/open?id=1Bbt_aTOHABMYQQlVNTy7X0MVJBJoHqgJ
Click to expand...
Click to collapse
Hello Dear SubwayChamp,
It Will Be Very Helpful For US. Thank You Once Again...

Thanks for updating this to 10.0.13.
I wanted to create my own file and have some questions about the file emmc_appsboot.mbn
1. The updater script flashes the above file as an img file. Is it ok to just rename the mbn file or is a program like HxD Hex Editor needed?
2. In your 10.0.13 version there is only the mbn file but not the img file, is that ok? In your 10.0.3 file there is only the img file and in 10.0.9 there are both, so I'm a little confused.

I am seeing a few custom Android 10 roms out there, with the Android 9 base firmware, is not better wait for the android 10 base firmware? and the source code for the kernel.

Pat750 said:
Thanks for updating this to 10.0.13.
I wanted to create my own file and have some questions about the file emmc_appsboot.mbn
1. The updater script flashes the above file as an img file. Is it ok to just rename the mbn file or is a program like HxD Hex Editor needed?
2. In your 10.0.13 version there is only the mbn file but not the img file, is that ok? In your 10.0.3 file there is only the img file and in 10.0.9 there are both, so I'm a little confused.
Click to expand...
Click to collapse
Hi, I switched to other devices since I uploaded these files, anyway thanks for notice that, there was an error on the typo in versions 9, 12 and 13.
Xiaomi fastboot ROMs are mirrored on a lot of sites and I don´t remember now from where I downloaded it and I duplicated from inside the version 10.0.9, it wasn´t right, now all the files were re-uploaded and corrected.
As per mbn files can´t be simply renamed as image, you can look inside and change some values with a HEX editor but is not a good idea to make this without a solid knowledge so it may get corrupted and flashing a corrupted bootloader can seriously brick your device anyway don´t worry about so no need to change nothing, TWRP will place the images in the right places/partitions as they´re originally inside the fastboot ROMs.

SubwayChamp said:
Hi, I switched to other devices since I uploaded these files, anyway thanks for notice that, there was an error on the typo in versions 9, 12 and 13.
Xiaomi fastboot ROMs are mirrored on a lot of sites and I don´t remember now from where I downloaded it and I duplicated from inside the version 10.0.9, it wasn´t right, now all the files were re-uploaded and corrected.
As per mbn files can´t be simply renamed as image, you can look inside and change some values with a HEX editor but is not a good idea to make this without a solid knowledge so it may get corrupted and flashing a corrupted bootloader can seriously brick your device anyway don´t worry about so no need to change nothing, TWRP will place the images in the right places/partitions as they´re originally inside the fastboot ROMs.
Click to expand...
Click to collapse
Thank you. I see the changes.
Good luck with your new device. You did some good things here and helped people a lot.