Related
I have rooted, unlocked, and flashed CM10, and then flashed the stock ROM. I had trouble downloading the ROM from samsung-updates.com, and found a page with a different link to a file of a different name, but a similiar size. The file name is:
HOME_I535VRALF2_I535VZWALF2_618049_REV09_user_low_ship.tar.md5
I'm curious, has anyone else used this file? Is that the correct file to use? When flashing back to stock rom with that file, do you also get the locked bootloader, the original recovery, and lose root? It seems like it does, but wanted to confirm. Do I still need to flash the bootloader as provided in this post:
http://forum.xda-developers.com/showthread.php?t=1769411
docdockstader said:
I have rooted, unlocked, and flashed CM10, and then flashed the stock ROM. I had trouble downloading the ROM from samsung-updates.com, and found a page with a different link to a file of a different name, but a similiar size. The file name is:
HOME_I535VRALF2_I535VZWALF2_618049_REV09_user_low_ship.tar.md5
I'm curious, has anyone else used this file? Is that the correct file to use? When flashing back to stock rom with that file, do you also get the locked bootloader, the original recovery, and lose root? It seems like it does, but wanted to confirm. Do I still need to flash the bootloader as provided in this post:
http://forum.xda-developers.com/showthread.php?t=1769411
Click to expand...
Click to collapse
Click link and sig and follow section 6...questions are answered there.
droidstyle said:
Click link and sig and follow section 6...questions are answered there.
Click to expand...
Click to collapse
I tried the link in section 6 and it completes after only 5 meg. Question on the kernel, if I didn't flash a new kernel when flashing CM10, did I screw up, and do I still need to flash the stock kernel?
docdockstader said:
I tried the link in section 6 and it completes after only 5 meg. Question on the kernel, if I didn't flash a new kernel when flashing CM10, did I screw up, and do I still need to flash the stock kernel?
Click to expand...
Click to collapse
Cm installs a kernel
piiman said:
Cm installs a kernel
Click to expand...
Click to collapse
OK, and the stock flash doesn't? Cool, thanks. How about ROM manager restore, does that backup and restore the proper kernel?
docdockstader said:
OK, and the stock flash doesn't? Cool, thanks. How about ROM manager restore, does that backup and restore the proper kernel?
Click to expand...
Click to collapse
No but section 6 of the guide does...link fixed btw!
I have LG Nexus 5 Phone rooted recently. With Custom Recovery I have installed some Zips (Called Mods). One of the Zips is Corrupt and my phone is not responding at all. I want to remove the Custom Zip/Mod only as I don't wan to wipe off whole system.
Is there any way to remove that particular Mod using TWRP Manager or any other way without loosing my data/stuff on my phone.
Restore the backup you made before flashing it
Sent from my Nexus 5 using XDA Premium 4 mobile app
pepdavies said:
Restore the backup you made before flashing it
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am not able to find any backup. I think I have not created it. Does this application creates backup automatically?
If in worst to worst case there is no backup, what are all other options I do have here.
Hi,
pepdavies said:
Restore the backup you made before flashing it
Click to expand...
Click to collapse
This, yes... but I doubt he made a backup if he ask how to "remove" the mods...
@anshumangoyal, maybe the there is an "undo" zip file, a revert to stock zip file? What mod have you flashed?
Dirty flash your rom, no wipe, and you won't lose anything...
And no automatic backup, you need to do it yourself in recovery, first thing to do when you flash some stuff.
pepdavies said:
Restore the backup you made before flashing it
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hammer_Of_The_Gods said:
Hi,
This, yes... but I doubt he made a backup if he ask how to "remove" the mods...
@anshumangoyal, maybe the there is an "undo" zip file, a revert to stock zip file? What mod have you flashed?
Dirty flash your rom, no wipe, and you won't lose anything...
And not, no automatic backup, you need to do it yourself in recovery, first thing to do when you flash some stuff.
Click to expand...
Click to collapse
But, how to do this dirty flash. I cannot see any such option in TWRP. Do i need to install some another tool etc??
anshumangoyal said:
But, how to do this dirty flash. I cannot see any such option in TWRP. Do i need to install some another tool etc??
Click to expand...
Click to collapse
Boot in recovery, go to your rom zip file, flash and reboot...
Without more relevant info I can only say that...
Stock rom? Custom rom? Link to the mod you flashed?
Hammer_Of_The_Gods said:
Boot in recovery, go to your rom zip file, flash and reboot...
Without more relevant info I can only say that...
Stock rom? Custom rom? Link to the mod you flashed?
Click to expand...
Click to collapse
It's Stock ROM I have Rooted to, I am not using ay custom ROM. So whare to download this Stock ROM. And also once this Stock ROM is flashed do I need to root the phone again.
I may be asking very silly questions, but this is what I was able to know in last 1-2 months and "still Learning"
Ok, it seems you don't want to post a link to the mod you flashed, or at least say the name, I asked 2 times and maybe we could do a revert zip file for you if we know what you have flashed (it depends of what kind of mod) then...
Take a look here to return to stock: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701.
Or flash a stock rom via recovery? Maybe easier for you...
EDIT: stock roms, flashable zip file: http://forum.xda-developers.com/showpost.php?p=52732041&postcount=4 (two first links), see above to flash...
Hammer_Of_The_Gods said:
Ok, it seems you don't want to post a link to the mod you flashed, or at least say the name, I asked 2 times and maybe we could do a revert zip file for you if we know what you have flashed (it depends of what kind of mod) then...
Take a look here to return to stock: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701.
Or flash a stock rom via recovery? Maybe easier for you...
EDIT: stock roms, flashable zip file: http://forum.xda-developers.com/showpost.php?p=52732041&postcount=4.
Click to expand...
Click to collapse
Oops I am sorry, I was not aware of terminology here. If I see in System Setting I have Build Number: KOT49H and Kernel Version: 3.4.0-gadb2201
Is this information you are looking for. I had unrooted latest android software, which I rooted using wugFresh tool kit software on windows 8.
Model: Nexus 5, LGD820, D821
Android 4.4.2 KOT49H
I hope this will help out.
Nope, it's not what I asked but...
I gave you a link to some full stock roms (rooted) to flash in recovery: http://forum.xda-developers.com/showpost.php?p=52732041&postcount=4 (use the first one for example).
Put it on your phone via computer, reboot in recovery go to the zip file you've just put, flash the zip file and reboot, the modified files from the mods you flashed will be replaced by the original stock files.
Use this link to "learn" how to use some commands (manually) and return to stock when you encounter a plroblem: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701. Here you need to flash the system.img (I guess, since I don't know what you flashed), or "all"...
Maybe harder for you since you used a Toolkit the first time but with time and reading...
If it seems even too hard for you, then in your Toolkit is there an option to return to stock, reflash the system.img?
When I ask you what mod you flashed, I mean it's a theme? A kernel? A sound mod? A camera mod? Because if we know what you flashed, maybe we can do a revert zip file for you by replacing the files by the stock ones in the zip).
What is the exact name of the zip file, the last you flashed and gives you problem?
Read all closely and take your time...
Hammer_Of_The_Gods said:
Nope, it's not what I asked but...
I gave you a link to some full stock roms (rooted) to flash in recovery: http://forum.xda-developers.com/showpost.php?p=52732041&postcount=4 (use the first one for example).
Put it on your phone via computer, reboot in recovery go to the zip file you've just put, flash the zip file and reboot, the modified files from the mods you flashed will be replaced by the original stock files.
Use this link to "learn" how to use some commands (manually) and return to stock when you encounter a plroblem: http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701. Here you need to flash the system.img (I guess, since I don't know what you flashed), or "all"...
Maybe harder for you since you used a Toolkit the first time but with time and reading...
If it seems even too hard for you, then in your Toolkit is there an option to return to stock, reflash the system.img?
When I ask you what mod you flashed, I mean it's a theme? A kernel? A sound mod? A camera mod? Because if we know what you flashed, maybe we can do a revert zip file for you by replacing the files by the stock ones.
What is the exact name of the zip file, the last you flashed and gives you problem?
Read all closely and take your time...
Click to expand...
Click to collapse
Thanks,
Now I understood. These were two Zips I installed were: cargo_N5_RebootMenu_KOT49H_odex.zip and cargo_only_Batt___rechts_odex_N5.zip
These were 2 mods I had.
anshumangoyal said:
Thanks,
Now I understood. These were two Zips I installed were: cargo_N5_RebootMenu_KOT49H_odex.zip and cargo_only_Batt___rechts_odex_N5.zip
These were 2 mods I had.
Click to expand...
Click to collapse
Ok, good.
The first: http://forum.xda-developers.com/google-nexus-5/themes-apps/mod-advanced-4-reboot-menu-odex-t2521809, you have a revert zip file (just below the mod you flashed): Back to stock: cargo_N5_Back_to_stock_RebootMenu_KOT49H_odex.zip.
The second: http://forum.xda-developers.com/goo...ps/mod-center-clock-battery-mod-odex-t2526039, same thing you have a revert zip file in attachment: Back_to_Stock_odex_N5.zip.
Download them and flash them to restore the original files, you really need to read closely before flashing stuff
Hammer_Of_The_Gods said:
Ok, good.
The first: http://forum.xda-developers.com/google-nexus-5/themes-apps/mod-advanced-4-reboot-menu-odex-t2521809, you have a revert zip file (just below the mod you flashed): Back to stock: cargo_N5_Back_to_stock_RebootMenu_KOT49H_odex.zip.
The second: http://forum.xda-developers.com/goo...ps/mod-center-clock-battery-mod-odex-t2526039, same thing you have a revert zip file in attachment: Back_to_Stock_odex_N5.zip.
Download them and flash them to restore the original files, you really need to read closely before flashing stuff
Click to expand...
Click to collapse
This is Super Find. I am sorry, I was not aware of this. Next time I will check this for sure and make sure I also take a backup before doing these nasty things. Many thanks again for your help.
When new factory images are eventually posted, would it be possible to only flash the system.img from the package to update? I'm thinking as long as there are no changes to the bootloader or radio, it might be possible to leave the custom recovery and data alone by only flashing the system files.
Would this work or not? I'm not technically minded enough to know.
What new images? 5.1?
You would need to flash kernel too. Boot.img
rootSU said:
What new images? 5.1?
You would need to flash kernel too. Boot.img
Click to expand...
Click to collapse
Yes, when Google releases some bugfixes for Lollipop I'd like to update without the hassle of reverting to stock for an OTA. So this would be a method to update to newer versions without breaking root or overwriting custom recoveries?
Just flashing 2 images seems like a pretty easy way to upgrade compared to some of the other guides I've seen.
billclay1988 said:
Yes, when Google releases some bugfixes for Lollipop I'd like to update without the hassle of reverting to stock for an OTA. So this would be a method to update to newer versions without breaking root or overwriting custom recoveries?
Just flashing 2 images seems like a pretty easy way to upgrade compared to some of the other guides I've seen.
Click to expand...
Click to collapse
Even easier would be a recovery flashable ROM.zip as per the thread in my signature
rootSU said:
Even easier would be a recovery flashable ROM.zip as per the thread in my signature
Click to expand...
Click to collapse
Your guide is very thorough! Thank you for the help. :good:
I tried to flash CWM made with MTKdroidTools, directly through MTKdroidTools, and it came up (upside down). I then proceeded to select reboot. It just got stuck at a bootloop (also upside down). I did a battery pull after a few minutes, and booted into recovery, which came up with the stock one. I selected wipe emmc (written in chinese, but I have a different phone with the same recovery for reference). Did the wipe, still stuck in bootloop.
Device a is MT6572 Note 4 replica. I have a backup. ADB and Fastboot still work. I can boot into the stock recovery. What should I do?
Jesse72 said:
I tried to flash CWM made with MTKdroidTools, directly through MTKdroidTools, and it came up (upside down). I then proceeded to select reboot. It just got stuck at a bootloop (also upside down). I did a battery pull after a few minutes, and booted into recovery, which came up with the stock one. I selected wipe emmc (written in chinese, but I have a different phone with the same recovery for reference). Did the wipe, still stuck in bootloop.
Device a is MT6572 Note 4 replica. I have a backup. ADB and Fastboot still work. I can boot into the stock recovery. What should I do?
Click to expand...
Click to collapse
So you have a fake note 4 OK
Can you flash a kernel and can you get the boot.IMG
USBhost said:
So you have a fake note 4 OK
Can you flash a kernel and can you get the boot.IMG
Click to expand...
Click to collapse
I'm not sure what you mean about the kernel, can you be more specific?
I have a whole ROM backup, done minutes before I tried to flash the recovery, so I can get the boot.IMG from that
Jesse72 said:
I'm not sure what you mean about the kernel, can you be more specific?
I have a whole ROM backup, done minutes before I tried to flash the recovery, so I can get the boot.IMG from that
Click to expand...
Click to collapse
Then can you just restore that backup?
USBhost said:
Then can you just restore that backup?
Click to expand...
Click to collapse
How do I do that?
Jesse72 said:
How do I do that?
Click to expand...
Click to collapse
How did you even do a full ROM backup
Or you used that tool to do so?
USBhost said:
How did you even do a full ROM backup
Or you used that tool to do so?
Click to expand...
Click to collapse
Did the backup with MTKdroidTools. Its currently on my computer. How can I now restore it to the phone? ADB and fastboot work, but my recovery reverted back to stock?
Sorry for the dumb questions, but this is the first time I've ever created a brick.
Jesse72 said:
Did the backup with MTKdroidTools. Its currently on my computer. How can I now restore it to the phone? ADB and fastboot work, but my recovery reverted back to stock?
Sorry for the dumb questions, but this is the first time I've ever created a brick.
Click to expand...
Click to collapse
NP I was a noob too
What do you mean by adb working
In recovery and or booting up?
If you get adb while the bootloop
Can you do "adb shell mount"
And is your bootloader unlocked
Do you have download mod?
Edit nvm thanks @karandpr
This thread has instructions for backup & restore.
http://forum.xda-developers.com/showthread.php?t=2730031
karandpr said:
This thread has instructions for backup & restore.
http://forum.xda-developers.com/showthread.php?t=2730031
Click to expand...
Click to collapse
Stuck at step 3, won't accept scatter file.
Jesse72 said:
Stuck at step 3, won't accept scatter file.
Click to expand...
Click to collapse
In that case you will need stock firmware ....
I can tell you the procedure but not the solution...
You will need Google and lot of patience ...
First you will need to find phones with specs same(atleast 90% similar) to your phone....
Then you need to download firmwares with the help of Google (there will be a lot)...
Then you need to test them one by one using SP tool...
You will get weird results like touchscreen not working or something...
In case you find the perfect firmware...post in in this thread or make an FAQ ...It will help others ...
karandpr said:
In that case you will need stock firmware ....
I can tell you the procedure but not the solution...
You will need Google and lot of patience ...
First you will need to find phones with specs same(atleast 90% similar) to your phone....
Then you need to download firmwares with the help of Google (there will be a lot)...
Then you need to test them one by one using SP tool...
You will get weird results like touchscreen not working or something...
In case you find the perfect firmware...post in in this thread or make an FAQ ...It will help others ...
Click to expand...
Click to collapse
I have the backup ROM I made, can I just flash it somehow? Its in zip format.
Jesse72 said:
I have the backup ROM I made, can I just flash it somehow? Its in zip format.
Click to expand...
Click to collapse
Make a copy of zip
Open zip and check if there is updater-script ...
If there is then you can flash with recovery. ...
karandpr said:
Make a copy of zip
Open zip and check if there is updater-script ...
If there is then you can flash with recovery. ...
Click to expand...
Click to collapse
Just realised MTKdroidtools is working, so I re-flashed CWM. Putting ROM zip on blank SD card, and will try to flash with CWM.
Am I doing this right?
Jesse72 said:
Just realised MTKdroidtools is working, so I re-flashed CWM. Putting ROM zip on blank SD card, and will try to flash with CWM.
Am I doing this right?
Click to expand...
Click to collapse
I have no hands-on experience with MTK devices.
On normal devices with recoveries , there is a folder Meta-INF and there is updater script and update binary which allows a Zip file o flashed on Android Recoveries (Stock or CWM). Stock recoveries enforce manufacturers signature. Custom recoveries like CWM allow unsigned zips.
Long story short ,check for META-INF folder and check if updater script & updater-binary is present. If not then ,zip won't be flashed with CWM
karandpr said:
I have no hands-on experience with MTK devices.
On normal devices with recoveries , there is a folder Meta-INF and there is updater script and update binary which allows a Zip file o flashed on Android Recoveries (Stock or CWM). Stock recoveries enforce manufacturers signature. Custom recoveries like CWM allow unsigned zips.
Long story short ,check for META-INF folder and check if updater script & updater-binary is present. If not then ,zip won't be flashed with CWM
Click to expand...
Click to collapse
There is no folders in the backup, just individual files. No files called updater script or updater-binary either. And yeah, it didn't flash either. I have 2 backups, one stock ROM, one done today. Both were done with MTKdroidTools, so I expect both to be the same. Any way to get the required files and add them, or do something else to make it flashable?
Jesse72 said:
There is no folders in the backup, just individual files. No files called updater script or updater-binary either. And yeah, it didn't flash either. I have 2 backups, one stock ROM, one done today. Both were done with MTKdroidTools, so I expect both to be the same. Any way to get the required files and add them, or do something else to make it flashable?
Click to expand...
Click to collapse
Try SP tool or it's variant . ..Those backups can only be flashed in SP tool !!
:angel:
It might be possible to extract files if they are not encrypted but it will take a lot of time...
karandpr said:
Try SP tool or it's variant . ..Those backups can only be flashed in SP tool !!
:angel:
It might be possible to extract files if they are not encrypted but it will take a lot of time...
Click to expand...
Click to collapse
SP flashtools isn't working, but I found a guide, which shows how to create a flashable zip from a backup. However it says to get the META-INF folder from a custom ROM for your phone. How specific does this folder need to be? I cant be sure of what my device is completely because it is branded as a note 4, rather than a replica under a brand name.
I can find a MT6572 ROM, but I cant be sure everything would work flawlessly with my phone. Understand what I'm saying?
EDIT: link to article http://www.droidviews.com/create-flashable-zip-cwmtwrp-backup/
Jesse72 said:
SP flashtools isn't working, but I found a guide, which shows how to create a flashable zip from a backup. However it says to get the META-INF folder from a custom ROM for your phone. How specific does this folder need to be? I cant be sure of what my device is completely because it is branded as a note 4, rather than a replica under a brand name.
I can find a MT6572 ROM, but I cant be sure everything would work flawlessly with my phone. Understand what I'm saying?
EDIT: link to article http://www.droidviews.com/create-flashable-zip-cwmtwrp-backup/
Click to expand...
Click to collapse
The binary is generic .The updater script needs to be specific. Special permissions are assigned to files using the script which can make or break the device. You will need a ROM very close to your device for Meta INF.
The article you have listed is for CWM backup which is different from MTK tools backup.
You will need to get SP tools working to get your device working...or search for a working backup for your device.
karandpr said:
The binary is generic .The updater script needs to be specific. Special permissions are assigned to files using the script which can make or break the device. You will need a ROM very close to your device for Meta INF.
The article you have listed is for CWM backup which is different from MTK tools backup.
You will need to get SP tools working to get your device working...or search for a working backup for your device.
Click to expand...
Click to collapse
I'm confused with what you want me to do with SP flash tools. Can you please explain?
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.