Hello everyone,
I was wondering if there was a way to flash aboot.mbn to the aboot partition.
I have tried Heimdall however it does not seem to be compatible with the s5 yet and odin v3.09 and v1.85 also gives me problems and thus far have been unable to flash it. I have also tried the dd command from and android terminal emulator
Code:
dd if=/storage/extSdCard/aboot.mbn of=/dev/block/mmcblk0p6
which also did not work and i do not believe that mobile odin can flash aboot either.
So my question is is there any other way to flash aboot or am i stuck until heimdall updates compatibility?
i am on G900T s5.
Thank You.
If u got adb installed on your pc, using following command
fastboot devices
fastboot flash aboot aboot.img
babygau said:
If u got adb installed on your pc, using following command
fastboot devices
fastboot flash aboot aboot.img
Click to expand...
Click to collapse
I tried but i do not think that samsung adds support for fastboot at all since the use their own download mode for odin and stuff
I am still stuck on this last hurdle, any help welcome thanks
I could really use the help, this is the last thing in my way
cm0002 said:
I could really use the help, this is the last thing in my way
Click to expand...
Click to collapse
Can you not be able to reflash stock firmware using Odin???
babygau said:
Can you not be able to reflash stock firmware using Odin???
Click to expand...
Click to collapse
No for whatever reason odin fails to flash when i package aboot.
i package it as a tar with 7zip, just aboot.mbn file nothing special and no special settings, or am i missing something that odin needs?
cm0002 said:
No for whatever reason odin fails to flash when i package aboot.
i package it as a tar with 7zip, just aboot.mbn file nothing special and no special settings, or am i missing something that odin needs?
Click to expand...
Click to collapse
Odin doesn't flash zip file bro
Why not using Odin to flash your complete stock firmware?
Hi,
I am also stuck with flashing aboot.mbn, did you have any luck since?
ferdossi said:
Hi,
I am also stuck with flashing aboot.mbn, did you have any luck since?
Click to expand...
Click to collapse
what is the purpose of just flashing the aboot.img?
youdoofus said:
what is the purpose of just flashing the aboot.img?
Click to expand...
Click to collapse
in fact I don't just flash aboot, my issue occurs when I try to flash the I9505XXUHPK2.tar bootloader which contains also other files but ODIN stops when trying to flash aboot.mbn
Related
My device is Droid turbo 2 . I flashed by RSD but it showed that Failed flashing process. 17/26 flash modem"NON-HLOS.bin" -> Phone returned FAIL.
HELP!
kaisam573 said:
My device is Droid turbo 2 . I flashed by RSD but it showed that Failed flashing process. 17/26 flash modem"NON-HLOS.bin" -> Phone returned FAIL.
HELP!
Click to expand...
Click to collapse
Have you tried flashing manually with fastboot? fastboot flash modem NON-HLOS.bin
Flash modem NON-HLOS.bin manually with fastboot, twice. I don't know why it doesn't work with RSD, but it doesn't.
rodrigoger said:
Flash modem NON-HLOS.bin manually with fastboot, twice. I don't know why it doesn't work with RSD, but it doesn't.
Click to expand...
Click to collapse
Did you have to take out NON-HLOS in order to flash back to stock in RSD? Im having that problem on my Moto X Pure returning to stock Marshmallow.
Use mfastboot
Kir6y said:
Did you have to take out NON-HLOS in order to flash back to stock in RSD? Im having that problem on my Moto X Pure returning to stock Marshmallow.
Click to expand...
Click to collapse
Do not use RSD. Use mfastboot commands (or Minimal ADB and Fastboot), and flash it manually, ok? Follow the order, but the Non-HLOS need to be flashed twice.
rodrigoger said:
Do not use RSD. Use mfastboot commands (or Minimal ADB and Fastboot), and flash it manually, ok? Follow the order, but the Non-HLOS need to be flashed twice.
Click to expand...
Click to collapse
Ok Thanks
rodrigoger said:
Do not use RSD. Use mfastboot commands (or Minimal ADB and Fastboot), and flash it manually, ok? Follow the order, but the Non-HLOS need to be flashed twice.
Click to expand...
Click to collapse
This solved my problem. Thanks dude!:good::good:
Running COS 13 -2JK and when I launch the theme chooser, all themes except the system theme are blank and transparent. Applying any of them crashes the theme chooser. A factory reset didn't cure it. The zip I flashed was straight from cyngn.com/support
Sent from my A0001 using Tapatalk
I had this almost-like problem on 1st cos13 release.after clean flash 2jk it's solved.
avijedi said:
Running COS 13 -2JK and when I launch the theme chooser, all themes except the system theme are blank and transparent. Applying any of them crashes the theme chooser. A factory reset didn't cure it. The zip I flashed was straight from cyngn.com/support
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
can you post the commands you used for flashing the firmware?
hellcat50 said:
can you post the commands you used for flashing the firmware?
Click to expand...
Click to collapse
Flashed via twrp, the signed zip
avijedi said:
Flashed via twrp, the signed zip
Click to expand...
Click to collapse
Use this zip: http://builds.cyngn.com/factory/bacon/cm-13.0-ZNH0EAS2JK-bacon-signed-fastboot-2d1a3b8dca.zip
Extract it, put the files into your adb and fastboot directory, boot into bootloader, connect device with your pc and run these commands:
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash oppostanvbk static_nvbk.bin
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash system system.img
if you need further help with adb and fastboot, how to install und how to use, then feel free to reply.
btw what twrp version are you using?
My words may feel funny but i faced the same problem once
I uninstalled all the 12.1 themes from the phone via link2sd
and my problem get solved try this may it help you in a simple way
I'm having the same issue, my update came from OTA.
What i did to solve this, is formatting the phone, setting it up as new and the making a new cyanogen mod account. Now it works. Try it.
arshu16 said:
What i did to solve this, is formatting the phone, setting it up as new and the making a new cyanogen mod account. Now it works. Try it.
Click to expand...
Click to collapse
I did the same but it allows me to download just one theme after that the theme store hangs or becomes unbearably slow it takes 5-10 touches just to scroll the about section of theme. all other apps work perfectly. also I am not able to update any theme.
Hello, i have ZTE axon 7 ZTE A2017G model. When i bought it from china, via allieexpress, it was on stock 4.0 mifavor chinese version. It was not updating to the latest nougat. I tried updating manually via recovery mode through SD card. I was succesful to update it to 7.1.1 nougat. Unfortunately my Mobile network became completely disabled. I understand that i used an incorrect firmware. Current build number: ZTE A2017GV1.2.0B05. How and what should i do in order to restore my mobile network. I am currently living in UK. Should i completly hard reset, install chinese or Eu version, i am confused. Anyone can help me with this?
Hi,
Hardwares are different between china and europe model, therefore radio firmwares within the roms also.
I would advise you to flash the latest chinese version of the rom to go back to normal.
However if you have an unlocked bootloader, you can try flashing only the radio modem via adb.
Good luck
Cojy said:
Hi,
Hardwares are different between china and europe model, therefore radio firmwares within the roms also.
I would advise you to flash the latest chinese version of the rom to go back to normal.
However if you have an unlocked bootloader, you can try flashing only the radio modem via adb.
Good luck
Click to expand...
Click to collapse
Thank you. And maybe if you would so kind, any links for the best guide how to flash radio modem via adb?
Cheers
A bit of a late reply, I did not get any notification.
First reboot into fastboot (adb reboot bootloader, the screen ued to display fastboot on my other android phone)
After that it is a 'fastboot flash radio signed_radio.img'
You can flash every .img file that you find in a rom via fastboot (if you have issues with gyroscope, modem, radio...)
here are some common commands:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash rpm rpm.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
It is usually fastboot flash <component> <component>.img like flash boot boot.img or flash radio radio.img...
Let us know if it solves your issue
Cojy said:
A bit of a late reply, I did not get any notification.
First reboot into fastboot (adb reboot bootloader, the screen ued to display fastboot on my other android phone)
After that it is a 'fastboot flash radio signed_radio.img'
You can flash every .img file that you find in a rom via fastboot (if you have issues with gyroscope, modem, radio...)
here are some common commands:
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash rpm rpm.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
It is usually fastboot flash <component> <component>.img like flash boot boot.img or flash radio radio.img...
Let us know if it solves your issue
Click to expand...
Click to collapse
Thanks for the reply.
Unfotrunately, i am completely new to this kind of thing. I managed to reboot into fastboot. But now im not sure what to do. Do i just put in commands? Do i need to download the radio.img files or? If you would be so kind to provide a bit more detail to this.
Thanks again
Fruktoze said:
Thanks for the reply.
Unfotrunately, i am completely new to this kind of thing. I managed to reboot into fastboot. But now im not sure what to do. Do i just put in commands? Do i need to download the radio.img files or? If you would be so kind to provide a bit more detail to this.
Thanks again
Click to expand...
Click to collapse
The usual saying is don't do that if you don't know what you are doing ! This could block your phone and you would have a hard time restoring it if you are not at ease with that sort of things.
This being said, you need to retrieve the .img file from your operating system image, put it in your adb folder (or whatever folder but you will have to add the path) and run the aforesaid commands.
This appears. I can not find anything on the internet and I do not know what to do.
KafkaG said:
This appears. I can not find anything on the internet and I do not know what to do.
Click to expand...
Click to collapse
Hi,
extract the original Firmware on your PC, look for boot.img and than in fastboot write "fastboot flash boot boot.img". Error1 disapers. :good:
Sent from my Mi A1 using XDA Labs
yorkberliner said:
Hi,
extract the original Firmware on your PC, look for boot.img and than in fastboot write "fastboot flash boot boot.img". Error1 disapers. :good:
Click to expand...
Click to collapse
Thanks, but how I can do it?
yorkberliner said:
Hi,
extract the original Firmware on your PC, look for boot.img and than in fastboot write "fastboot flash boot boot.img". Error1 disapers. :good:
Click to expand...
Click to collapse
but I have to extract it from the firmware of lineageos I installed or from the original one of stock? and how do I extract it?
Nobody can help me?
KafkaG said:
Nobody can help me?
Click to expand...
Click to collapse
Good evening,
please be patient. DLoad and extract with 7zip the firmware from here. Extract the firmware again. Now you have the original boot.img from MIUI.
In Fastboot flash the boot.img with "fastboot flash boot boot.img".
If above method won't work, re-download the rom file, this seems corrupt.
Next time try to fresh flash the rom instead of ota, some ota are broken and would have some issue like this.
tanapak1 said:
If above method won't work, re-download the rom file, this seems corrupt.
Next time try to fresh flash the rom instead of ota, some ota are broken and would have some issue like this.
Click to expand...
Click to collapse
I downloaded several times the same rom and more versions, the problem is the system
yorkberliner said:
Good evening,
please be patient. DLoad and extract with 7zip the firmware from here. Extract the firmware again. Now you have the original boot.img from MIUI.
In Fastboot flash the boot.img with "fastboot flash boot boot.img".
Click to expand...
Click to collapse
which of those rom? the first one, 8.1 almost destroyed the system (with the boot.img) and I had to put the boot.img back from the twrp backup, so which link is right?
Edit: I think, indeed, I'm sure I need the boot.img of the rom that I have or lineage, but I do not know how to extract it from the zip.
Hi,
okay. I think the best way is you flash first the original Firmware from here with Xiaomi Flash Tool. DLoad and install on your PC. DLoad and read this Site.
Now you have the original Firmware installed. Go to settings, about the Phone, Buildnumber. Tab 7 times on it and than go to the Developer. Open OEM and US-Debugging. Reboot into Fastboot. In ADB/Fastboot write "fastboot devices" and your device must recogniced. Than write "fastboot oem unlock". After this you get a reboot to system. Now look again iin settings, devoloper if oem and usb-debugging on. Reboot in fastboot your Phone. Now write again "fastboot devices". Is everythink okay than write "fastboot boot recovery-3.2.1-2-oreo.img". Now you have twrp installed. In twrp flash the twrp-recoveryinstaller-3.2.1-2-oreo.zip. After this you can flash your favoryte Custom Rom. Good Luck :good:
yorkberliner said:
Hi,
okay. I think the best way is you flash first the original Firmware from here with Xiaomi Flash Tool. DLoad and install on your PC. DLoad and read this Site.
Now you have the original Firmware installed. Go to settings, about the Phone, Buildnumber. Tab 7 times on it and than go to the Developer. Open OEM and US-Debugging. Reboot into Fastboot. In ADB/Fastboot write "fastboot devices" and your device must recogniced. Than write "fastboot oem unlock". After this you get a reboot to system. Now look again iin settings, devoloper if oem and usb-debugging on. Reboot in fastboot your Phone. Now write again "fastboot devices". Is everythink okay than write "fastboot boot recovery-3.2.1-2-oreo.img". Now you have twrp installed. In twrp flash the twrp-recoveryinstaller-3.2.1-2-oreo.zip. After this you can flash your favoryte Custom Rom. Good Luck :good:
Click to expand...
Click to collapse
No thanks, bye
Tested on my own KB2003, work flawlessly. Useful for many cases.
I followed the GUIDE of @s3axel here : https://forum.xda-developers.com/t/...n-os-stock-recovery-with-adb-enabled.4084487/
All credits to him.
Basically, this modded Recovery just saved my a** )))) Just unzip using 7z then flash it to Recovery as normal.
LinhBT said:
Tested on my own KB2003, work flawlessly. Useful for many cases.
I followed the GUIDE of @s3axel here : https://forum.xda-developers.com/t/...n-os-stock-recovery-with-adb-enabled.4084487/
All credits to him.
Basically, this modded Recovery just saved my a** )))) Just unzip using 7z then flash it to Recovery as normal.
Click to expand...
Click to collapse
Can you share your file?
Rootk1t said:
Can you share your file?
Click to expand...
Click to collapse
Sure man, find attachment
Hi, I am facing a strange issue on OOS12 not able to factory reset or enter stock recovery it says boot/recovery.img damaged flash the correct one or contact support can any one help me out with this issue.
houstontaxi said:
Hi, I am facing a strange issue on OOS12 not able to factory reset or enter stock recovery it says boot/recovery.img damaged flash the correct one or contact support can any one help me out with this issue.
Click to expand...
Click to collapse
unpack your firmware, extract stock recovery.img and flash it.
But for flashing do I need to unlock bootloader or it can be done without unlocking?
houstontaxi said:
But for flashing do I need to unlock bootloader or it can be done without unlocking?
Click to expand...
Click to collapse
As far as i remember to flash partitions with stock firmware you don't need unlocked bootloader.
Rootk1t said:
As far as i remember to flash partitions with stock firmware you don't need unlocked bootloader.
Click to expand...
Click to collapse
If it needs to flash recovery the same way as we do for custom roms like fastboot flash recovery in platform tools then i tried that doesn't work to make it work bootloader needs to be unlocked I did that(unlocked the boot loader) then flashed stock recovery and it worked but after locking the boot loader with fastboot oem lock same issue happened again couldn't boot into recovery.
houstontaxi said:
But for flashing do I need to unlock bootloader or it can be done without unlocking?
Click to expand...
Click to collapse
To flash ANY partitions, u must unlock bootloader even if the partition is critical or not. And to prevent the boot/recovery image damaged error, u must flash stock boot/recovery images along with vbmeta.img ( also extracted from stock, same build ).
LinhBT said:
To flash ANY partitions, u must unlock bootloader even if the partition is critical or not. And to prevent the boot/recovery image damaged error, u must flash stock boot/recovery images along with vbmeta.img ( also extracted from stock, same build ).
Click to expand...
Click to collapse
I'm gonna try this also need to know if I have to flash boot.img and recovery.img as there are two files when extracted from the stock rom
houstontaxi said:
I'm gonna try this also need to know if I have to flash boot.img and recovery.img as there are two files when extracted from the stock rom
Click to expand...
Click to collapse
Both, boot.img and recovery.img , also in some case, u must flash dtbo.img too. I dont know the exact situation of you so my advise is to flash both boot.img recovery.img dtbo.img and vbmeta.img
LinhBT said:
Both, boot.img and recovery.img , also in some case, u must flash dtbo.img too. I dont know the exact situation of you so my advise is to flash both boot.img recovery.img dtbo.img and vbmeta.img
Click to expand...
Click to collapse
I'm gonna try that thanks for the help and I hope it resolves my issue with OOS A12 recovery as I don't face this kind of issue on OOS11
1
LinhBT said:
Both, boot.img and recovery.img , also in some case, u must flash dtbo.img too. I dont know the exact situation of you so my advise is to flash both boot.img recovery.img dtbo.img and vbmeta.img
Click to expand...
Click to collapse
Hello, tell me that your recovery cannot decrypt the date section? I need to extract data from the phone, the phone won't boot into the system, I tried to boot into your recovery but I can't access the folders.
lenox30 said:
Hello, tell me that your recovery cannot decrypt the date section? I need to extract data from the phone, the phone won't boot into the system, I tried to boot into your recovery but I can't access the folders.
Click to expand...
Click to collapse
This is simply Stock Recovery with ADB enabled bro. It only can help u in some tasks which need to access adb via Recovery, it won't help to decrypt ur device and/or have any functions as other custom recovery