Related
Hey,
Sorry for the noob question - but I wasn't able to find anything on this. Everyone seems to take this as it is, but I simply want to know why boot.img is flashed in order to get root and how it affects the phone.
I followed this tutorial to get my Rogers Magic rooted.
What did the boot.img do in this case and can I use Amon_RA's RAv1.1.2 ION Recovery or do I need to flash another boot image in order to use a different recovery.img.
Basically, I just want to know why I do the steps that I do.
vladkor said:
Hey,
Sorry for the noob question - but I wasn't able to find anything on this. Everyone seems to take this as it is, but I simply want to know why boot.img is flashed in order to get root and how it affects the phone.
I followed this tutorial to get my Rogers Magic rooted.
What did the boot.img do in this case and can I use Amon_RA's RAv1.1.2 ION Recovery or do I need to flash another boot image in order to use a different recovery.img.
Basically, I just want to know why I do the steps that I do.
Click to expand...
Click to collapse
boot.img contains
the actual linux kernel for the phone
small ramdrive to start the system
system.img contains
android os, libraries,system settings and applications
userdata.img contains apps, and user settings
br
jerpelea said:
boot.img contains
the actual linux kernel for the phone
small ramdrive to start the system
system.img contains
android os, libraries,system settings and applications
userdata.img contains apps, and user settings
br
Click to expand...
Click to collapse
Thanks for the reply! I'm still lost though on the whole 'fastboot flash boot boot.img' part.
Is there a specific/best/newest boot.img that I should be using with the Rogers Magic? Are there different ones out there or is it just one standard one?
I was trying to go back to stock before testing out eduardog131's deodexed rom. I tried my backup boot.img and it failed, so I grabbed the default from here, ADB console says the write is successfulm but it hangs at the splash screen when I try to boot I can get into the bootloader and recovery, and have the PLlIMG.zip I saved long ago (from which I extracted the same boot.img I've used before), but can't copy it over without booting. What on Earth could I have done?
zomgitsanoob said:
I was trying to go back to stock before testing out eduardog131's deodexed rom. I tried my backup boot.img and it failed, so I grabbed the default from here, ADB console says the write is successfulm but it hangs at the splash screen when I try to boot I can get into the bootloader and recovery, and have the PLlIMG.zip I saved long ago (from which I extracted the same boot.img I've used before), but can't copy it over without booting. What on Earth could I have done?
Click to expand...
Click to collapse
I bet the 'PL80IMG.zip' that you have is for 4.1.2
And you updated to 4.2.2
It's 4.2.2
I made it after upgrading so I'd be able to restore system.img , boot.img , and android-info.txt easily
zomgitsanoob said:
It's 4.2.2
I made it after upgrading so I'd be able to restore system.img , boot.img , and android-info.txt easily
Click to expand...
Click to collapse
You are aware that when you go to restore your device with your backup that you don't have to restore everything, right? You can uncheck everything and just leave the boot.img checked. Then swipe to restore in your custom recovery. The boot.img will be put back.
Sent from my C525c using Tapatalk
zomgitsanoob said:
It's 4.2.2
I made it after upgrading so I'd be able to restore system.img , boot.img , and android-info.txt easily
Click to expand...
Click to collapse
So the system.img that you have in the PL80IMG.zip is from a TWRP/CWM backup....it won't flash through bootloader unless you used dd to pull the system.img.....
Other words, you will not be able to flash PL80IMG.zip with a TWRP and or CWM backup of the system.img.....it's not the correct format
Only recovery.img and boot.img from TWRP/CWM backup will flash through bootloader PL80IMG.zip style......
Why not just click 'restore'? While in recovery...
zomgitsanoob said:
I was trying to go back to stock before testing out eduardog131's deodexed rom. I tried my backup boot.img and it failed, so I grabbed the default from here, ADB console says the write is successfulm but it hangs at the splash screen when I try to boot I can get into the bootloader and recovery, and have the PLlIMG.zip I saved long ago (from which I extracted the same boot.img I've used before), but can't copy it over without booting. What on Earth could I have done?
Click to expand...
Click to collapse
You didn't have to go stock to flash his Rom. Its a Rom lol. Its not like an OTA where it does checks on the system files and then patches them.
Take note of that for any future roms down the road.
Sent from my C525c using Tapatalk
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?
So, I ended up soft bricking my device in some way(??) I factory reseted the phone and it loads, i even set up my wifi, but when Im going to put my gmail account it crashes. I just want to restore it to its original settings. I have no backups, I feel screwed, Im literally in tears because this was a gift from my mother. Please Help me. :crying:
Go to page 23 of the blue development thread. The stock .img are there.
How do I use the stock.img to fix my phone?
Does it work as a backup if I place it in my phone?
futuresenseidomo said:
How do I use the stock.img to fix my phone?
Does it work as a backup if I place it in my phone?
Click to expand...
Click to collapse
You need a Windows program called SP Flash Tool and a scatter file for the Pure XL which is also in the development thread. Load the scatter file, select the partitions you want to restore (generally recovery, boot, and system) and load the .IMG files for them (should be recovery.img, boot.img, system.img or something close.)
Or another way to do it, if you have Twrp installed is to add to boot.img and recovery.img along with Meta-inf folder and zip it up. Then flash it in twrp. It will return your device to stock.
futuresenseidomo said:
How do I use the stock.img to fix my phone?
Does it work as a backup if I place it in my phone?
Click to expand...
Click to collapse
Were you able to get it working again? Having a very similar issue.
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.