Related
OK! So, finally got this working. Thought I share how i did this...
I had previously installed CM 10.1, but wanted to try out the stock firmware (I9505XXUBMEA_I9505OXABMEA). As I do not have windows, I had to use Heimdall under Ubuntu 13.04 64-bits. As far as I know, there is no post on this for our device.
I will keep this simple. I did not succeed with Heimdall 1.3, but Heimdall 1.4 R1 worked fine (R2 untested).
In brief, I ran the following commands as root (given that heimdall executable is in the untarred folder of the firmware):
Code:
heimdall flash --APNHLOS NON-HLOS.bin
heimdall flash --ABOOT aboot.mbn
heimdall flash --BOOT boot.img
heimdall flash --HIDDEN hidden.img.ext4
heimdall flash --MDM modem.bin
heimdall flash --RECOVERY recovery.img
heimdall flash --RPM rpm.mbn
heimdall flash --SBL2 sbl2.mbn
heimdall flash --SBL3 sbl3.mbn
heimdall flash --SYSTEM system.img.ext4
heimdall flash --TZ tz.mbn
heimdall flash --CACHE cache.img.ext4
This will reboot the device multiple times, and can of course be done more elegantly in one simple command. However, this is how I did it.
The last command (CACHE) reboots the device into recovery (So recovery must be flashed first).
Flashing is fast, only minutes. No troubles or reflashes. Everything appears to work, including wifi and 4G.
Hope you will find this useful. Now...lets try Omega ROM 5.0....:laugh: (Ubuntu Touch coming up???)
A million thanks to Benjamin Dobell (http://www.glassechidna.com.au/) who wrote Heimdall!
Best regards,
I have tested this flashing stock ROM, CM, Omega 5/6, modems.
No reflashes, no problems.
Those having difficulties with wifi/LTE and having to reflash modem multiple times may want to check it out....
Only tested under Ubuntu 13.04 64. You need Heimdall 1.4R1 or later...
Problems with WiFi after upgrade???
For upgrading from Omega 5 to Omega 6 do this:
1. Flash Omega 6 from Recovery (I use Phil's, effortless, no wiping).
2. Put heimdall 1.4R1 (or later) into a seperate folder together with NON-HLOS.bin and modem.bin from the I9505XXUBMF4_modems.tar
3. Than boot i9505 into download mode and issue...
sudo heimdall flash --APNHLOS NON-HLOS.bin
Click to expand...
Click to collapse
4. This will automatically poweroff your device. Reboot into download mode and from terminal issue...
sudo ./heimdall flash --MDM modem.bin
Click to expand...
Click to collapse
5. This will poweroff your i9505. Fire it up and you are good to go!
Modems are flashed and Wifi works. Easy piecy...nice and clean...works at first shot!
How do you install Heimdall?
I tried downloading and using the .deb file, but it hangs when trying to flash firmware.
Ending session...
Re-attaching kernel driver...
Click to expand...
Click to collapse
After that, I uninstalled Heimdall and tried compiling from source. It gave an error when I tried flashing.
ERROR: Failed to access device. libusb error: 0
Click to expand...
Click to collapse
Ubuntu 13.04 64bit
I'm using 32-bits ubuntu.
Got msg.
Code:
flash --SYSTEM system.img.ext4
ERROR: Failed to open file "system.img.ext4"
How to fix this?
Did you also flash bootloader?
Sent from my GT-N7100 using Tapatalk 4 Beta
echo_rc said:
Did you also flash bootloader?
Sent from my GT-N7100 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes. All others stock files have flashed.
Also I recompile heimdall with -D_FILE_OFFSET_BITS=64
Code:
Session begun.
Downloading device's PIT file...
PIT file download successful.
Uploading SYSTEM
100%
ERROR: Failed to confirm end of file transfer sequence!
ERROR: SYSTEM upload failed!
Ending session...
Rebooting device...
Releasing device interface...
Re-attaching kernel driver...
Thanks a lot for this info, managed to reflash my i9505 correctly in OSX with the latest release (4.3) XXUEMJ5 after trying odin under vmware and failing.
You could use this one line:
--APNHLOS NON-HLOS.bin --ABOOT aboot.mbn --BOOT boot.img --HIDDEN hidden.img.ext4 --MDM modem.bin --RECOVERY recovery.img --RPM rpm.mbn --SBL2 sbl2.mbn --SBL3 sbl3.mbn --SYSTEM system.img.ext4 --TZ tz.mbn --CACHE cache.img.ext4
svs57 said:
I'm using 32-bits ubuntu.
Got msg.
Code:
flash --SYSTEM system.img.ext4
ERROR: Failed to open file "system.img.ext4"
How to fix this?
Click to expand...
Click to collapse
I get the same error. I think I'm also running 32-bit. But I forgot.
lzk123 said:
How do you install Heimdall?
I tried downloading and using the .deb file, but it hangs when trying to flash firmware.
After that, I uninstalled Heimdall and tried compiling from source. It gave an error when I tried flashing.
Ubuntu 13.04 64bit
Click to expand...
Click to collapse
Hi I use mint 15 (13.04)
I went to the heimdall website and grabbed the latest amd64 deb files. I also installed the 32bit libraries from the ubuntu and mint depo's
Then installed the deb files.
I use sudo heimdall to do my flashes.
Does the hanging occur on your PC or just download mode?
lzk123 said:
How do you install Heimdall?
I tried downloading and using the .deb file, but it hangs when trying to flash firmware.
After that, I uninstalled Heimdall and tried compiling from source. It gave an error when I tried flashing.
Ubuntu 13.04 64bit
Click to expand...
Click to collapse
U need to have the "sudo" command in front because libusb requires root privilege.
so do this instead:
sudo heimdall flash --MDM blah blah blah
you are require to enter your username password
Just tried with Heimdall 1.4.0 on OS X (on i9505, stock 4.3) and it seems to have worked!
the one command for this is: heimdall flash --APNHLOS NON-HLOS.bin --ABOOT aboot.mbn --BOOT boot.img --HIDDEN hidden.img.ext4 --MDM modem.bin --RECOVERY recovery.img --RPM rpm.mbn --SBL2 sbl2.mbn --SBL3 sbl3.mbn --SYSTEM system.img.ext4 --TZ tz.mbn --CACHE cache.img.ext4
hope this helps someone
When I untar the stock firmware I don't see any bin files
9195XXUBML4_I9195O2UBMJ1_I9195XXUBML4_HOME.tar.md5
rpm.mbn system.img.ext4
aboot.mbn sbl1.mbn tz.mbn
boot.img sbl2.mbn
recovery.img sbl3.mbn
Only boot and recovery.img and some .mbn files
What am I missing?
9195XXUBML4_I9195O2UBMJ1_I9195XXUBML4_HOME.tar.md5
paamet said:
OK! So, finally got this working. Thought I share how i did this...
I had previously installed CM 10.1, but wanted to try out the stock firmware (I9505XXUBMEA_I9505OXABMEA). As I do not have windows, I had to use Heimdall under Ubuntu 13.04 64-bits. As far as I know, there is no post on this for our device.
I will keep this simple. I did not succeed with Heimdall 1.3, but Heimdall 1.4 R1 worked fine (R2 untested).
In brief, I ran the following commands as root (given that heimdall executable is in the untarred folder of the firmware):
Code:
heimdall flash --APNHLOS NON-HLOS.bin
heimdall flash --ABOOT aboot.mbn
heimdall flash --BOOT boot.img
heimdall flash --HIDDEN hidden.img.ext4
heimdall flash --MDM modem.bin
heimdall flash --RECOVERY recovery.img
heimdall flash --RPM rpm.mbn
heimdall flash --SBL2 sbl2.mbn
heimdall flash --SBL3 sbl3.mbn
heimdall flash --SYSTEM system.img.ext4
heimdall flash --TZ tz.mbn
heimdall flash --CACHE cache.img.ext4
This will reboot the device multiple times, and can of course be done more elegantly in one simple command. However, this is how I did it.
The last command (CACHE) reboots the device into recovery (So recovery must be flashed first).
Flashing is fast, only minutes. No troubles or reflashes. Everything appears to work, including wifi and 4G.
Hope you will find this useful. Now...lets try Omega ROM 5.0....:laugh: (Ubuntu Touch coming up???)
A million thanks to Benjamin Dobell (http://www.glassechidna.com.au/) who wrote Heimdall!
Best regards,
Click to expand...
Click to collapse
complience said:
When I untar the stock firmware I don't see any bin files
9195XXUBML4_I9195O2UBMJ1_I9195XXUBML4_HOME.tar.md5
rpm.mbn system.img.ext4
aboot.mbn sbl1.mbn tz.mbn
boot.img sbl2.mbn
recovery.img sbl3.mbn
Only boot and recovery.img and some .mbn files
What am I missing?
9195XXUBML4_I9195O2UBMJ1_I9195XXUBML4_HOME.tar.md5
Click to expand...
Click to collapse
Hello!
You don't have to worry. Flash it. In some packages it is like that. When I tried to flash Ace stock ROM, it was like that.
Code:
heimdall flash --ABOOT aboot.mbn --RECOVERY recovery.img --RPM rpm.mbn --SBL1 sbl1.mbn --SBL2 sbl2.mbn --SBL3 sbl3.mbn --SYSTEM system.img.ext4 --TZ tz.mbn
Use the above code to flash. For your own safety, re-check the code and also check whether every files are included in it.
Kindly,
MZ
Code:
$ sudo heimdall flash --pit s4pit.pit --APNHLOS NON-HLOS.bin --MDM modem.bin --SBL1 sbl1.mbn --SBL2 sbl2.mbn --SBL3 sbl3.mbn --ABOOT aboot.mbn --RPM rpm.mbn --TZ tz.mbn --SYSTEM system.img.ext4 --CACHE cache.img.ext4 --BOOT boot.img --RECOVERY recovery.img --HIDDEN hidden.img.ext4
ERROR: Failed to open file "system.img.ext4"
Guys what's wrong? I've just installed heimdall & heimdall-frontend from source (1.4.1), I'm trying to instal stock ROM on my i9505. I'm using Ubuntu 14, 32 bit. I cannot find any solution so far ..
kujawek said:
Code:
$ sudo heimdall flash --pit s4pit.pit --APNHLOS NON-HLOS.bin --MDM modem.bin --SBL1 sbl1.mbn --SBL2 sbl2.mbn --SBL3 sbl3.mbn --ABOOT aboot.mbn --RPM rpm.mbn --TZ tz.mbn --SYSTEM system.img.ext4 --CACHE cache.img.ext4 --BOOT boot.img --RECOVERY recovery.img --HIDDEN hidden.img.ext4
ERROR: Failed to open file "system.img.ext4"
Guys what's wrong? I've just installed heimdall & heimdall-frontend from source (1.4.1), I'm trying to instal stock ROM on my i9505. I'm using Ubuntu 14, 32 bit. I cannot find any solution so far ..
Click to expand...
Click to collapse
Hi kujawek! It is some problem with your system image of the stock ROM you downloaded. Try to re-download the stock ROM and do it again. Hope it works!
~~MZ~~
Muhammed Zakhir said:
Hi kujawek! It is some problem with your system image of the stock ROM you downloaded. Try to re-download the stock ROM and do it again. Hope it works!
~~MZ~~
Click to expand...
Click to collapse
I did it more than few times.
I've read somewhere that in latest Heimdall version it uses some different thing named "libusb" and that it's only possible to do it on Windows with heimdall 1.4.1.rc2 version. But it was easier for me to just use Odin on friend's computer
To install libusd on Linux Ubuntu :
Code:
Code:
sudo apt-get install libusb-dev
Upgrade:
Code:
sudo bash -c "apt-get update && apt-get upgrade"
~~MZ~~
Can I use Heimdall (the Mac OSX GUI) to flash a nandroid backup to my 9505?
In the nandroid there are all these files: boot.img, data.ext4.tar, recovery.img, system.ext4.tar - will this be the same as if I would restore the nandroid backup with CWM?
My phone doesnt start anymore and I tried a lot already, but CWM doesn't work anymore, so I look for a way to revive it.
I have all these files from the original image from a Note 4 stock, so which files are pertinent for each option in Odin, for BL, AP, CP, CSC
aboot.mbn
boot.img
cache.img.ext4
modem.bin
NON-HLOS.bin
recovery.img
rpm.mbn
sbl1.mbn
sdi.mbn
system.img.ext4
tz.mbn
Obviously, modem.bin --> CP but anything else in CP ?
And what for the others ?
// ========================================================================
Not life and death anymore... here's what I have so far:
-------------------------------------------------------------------
- aboot.mbn - BL
- boot.img - AP/PDA
- cache.img.ext4 - CSC
- modem.bin - CP
- NON-HLOS.bin - CP
- recovery.img - AP/PDA
- rpm.mbn - BL ???? not sure
- sbl1.mbn - BL
- sdi.mbn - BL ???? not sure.
- system.img.ext4 - AP/PDA
- tz.mbn - BL
--------------------------------------------------------------------
BL -> aboot.mbn sbl1.mbn tz.mbn
CP -> modem.bin NON-HLOS.bin
CSC -> cache.img.ext4
AP/PDA -> boot.img recovery.img system.img.ext4
-------------------------------------------------------------------
Got mine back running the way I wanted with help from this post: https://forum.xda-developers.com/no...rom-n910t3uvs3eqb1-stock-rooted-odex-t3576481
You need to flash .tar file on the Ap only one file
Do not extract the image
Enviado do meu SM-N910F através de Tapatalk
pitelasssss said:
You need to flash .tar file on the Ap only one file
Do not extract the image
Enviado do meu SM-N910F através de Tapatalk
Click to expand...
Click to collapse
Obrigado, resolvi o meu problema depois de muito apanhar.
Thanks problem solved, after a long battle.
De nada. Um abraço disponha
Enviado do meu SM-N910F através de Tapatalk
What is a blankflash file? I have seen people requesting blankflash file for their phones...
Does it help to recover device from bootloop/brick?
A good question.
I see a lot of people glibly saying, "Oh, you have to blankflash first".
I don't know and I have a suspicion that the people who use it don't know either.
I can go to EDL mode (on Qualcomm processors) and wipe every byte in flash to zero (0x00).
Presumably this mystic "blankflash" is something more.
Maybe it's some OEM enforced stupidity where it wipes everything then puts in a signature to say, "No, really, I'm erased".
So, to answer my own question:
Blankflash is a Motorola invention of throwing a bunch of partitions into a tar archive.
You can list it/extract it using 7zip or other utilities.
It's tar-"like", but not tar. Packed inside is:
Code:
programmer
gpt
aboot
rpm
tz
devcfg
cmnlib
cmnlib64
keymaster
prov
sbl1
This is the absolute minimum you need to flash to get fastboot running from aboot.
All of these (except the GPT) are either 32 or 64 bit ELF files with Qualcomm signing.
See: http://www.temblast.com/qcomview.htm
Note, none of this precludes you from using any EDL client to just write all your partitions
Hello, ALOT of people have been having tons of errors from wrong commands lying on the internet. I made a guide to fix that. Hope it works :highfive:
I am not responsible for any bricks but will help for a solution
You Must have your bootloader unlocked.
Android 10: use this link for retail firmware, will work on all device channels excluding AMX. beware.
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
After downloaded, unzip, open the folder containing all of the files and open powershell or cmd promt window here (shift + right click)
After that use
adb devices
Click to expand...
Click to collapse
to check and make sure your device is recognized. Use these commands after that.
fastboot --set-active=a
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta_a vbmeta.img
fastboot flash vbmeta_b vbmeta.img
fastboot flash modem_a NON-HLOS.bin
fastboot flash modem_b NON-HLOS.bin
fastboot flash fsg_a fsg.mbn
fastboot flash fsg_b fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth_a BTFM.bin
fastboot flash bluetooth_b BTFM.bin
fastboot flash dsp_a dspso.bin
fastboot flash dsp_b dspso.bin
fastboot flash logo_a logo.bin
fastboot flash logo_b logo.bin
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash dtbo_a dtbo.img
fastboot flash dtbo_b dtbo.img
fastboot flash system_a system.img_sparsechunk.0
fastboot flash system_a system.img_sparsechunk.1
fastboot flash system_a system.img_sparsechunk.2
fastboot flash system_a system.img_sparsechunk.3
fastboot flash system_a system.img_sparsechunk.4
fastboot flash system_a system.img_sparsechunk.5
fastboot flash system_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash oem_a oem.img
fastboot flash oem_b oem_other.img
fastboot flash vendor_a vendor.img_sparsechunk.0
fastboot flash vendor_a vendor.img_sparsechunk.1 fastboot flash vendor_b vendor.img_sparsechunk.0 fastboot flash vendor_b vendor.img_sparsechunk.1 fastboot erase carrier
fastboot erase userdata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
Android 9: Please don't use android 9.
A quick just so you know. TWRP doesn't boot on Android 10. a fix for that is coming soon.
WARNING: DO NOT DOWNGRADE FIRMWARE/ANDROID VERSIONS. IT WILL BRICK YOUR DEVICE!
Good luck all
Hi, for amx devices. How it Will work?
My code Is: amxpe.
I bought in operator from Peru. . I install android 10 soak test AND then pone started having problems with WiFi and I downgrade to android 9. And now its softbricked. I install some android 10 zip from lolinet but its stuck. I have bootloops or initial error message. Please any help
Jidnet said:
Hi, for amx devices. How it Will work?
My code Is: amxpe.
I bought in operator from Peru. . I install android 10 soak test AND then pone started having problems with WiFi and I downgrade to android 9. And now its softbricked. I install some android 10 zip from lolinet but its stuck. I have bootloops or initial error message. Please any help
Click to expand...
Click to collapse
I said in the warning don't install this specific firmware on AMX. I also said don't downgrade, wtf.
@SnowTalker these commands are not working for people same. They are also posing issues for certain users. Like i hard bricked with these commands. Stop posting half-baked stuff! harcd brick.
methuselah said:
@SnowTalker these commands are not working for people same. They are also posing issues for certain users. Like i hard bricked with these commands. Stop posting half-baked stuff! harcd brick.
Click to expand...
Click to collapse
These commands work only fro android 10 firmware and with a unlocked bootloader. I've tested them already they work.
SnowTalker said:
These commands work only fro android 10 firmware and with a unlocked bootloader. I've tested them already they work.
Click to expand...
Click to collapse
lol then again, probably i have also tried them for android 10! And then still it caused hard brick in my device case
methuselah said:
lol then again, probably i have also tried them for android 10! And then still it caused hard brick in my device case
Click to expand...
Click to collapse
What device channel.
I tested your codes in my phone : amxpe, and it works well , I recieve a message at the benning but i think is not main problem , phone now works. thanks I hope you can improve the codes
SnowTalker said:
Hello, ALOT of people have been having tons of errors from wrong commands lying on the internet.
Click to expand...
Click to collapse
The easiest way to fix the problems caused by wrong flash commands is not to post any command.
As you can see nobody cares about your warnings. But later you are the one to blame for it.
Even if you write "your device will self-destruct after using the commands", would they use them anyway.
Always refer to the flashfile.xml
Just a heads-up for anyone with the XT2019-1 version. I just successfully flashed the RETEU
https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
version of Android 10 using my FlashAllPartitions.bat based on flashfile.xml
[url]https://drive.google.com/file/d/1nGl1saSSJEZkCLAucU8RHVNuFQFamP1C/view?usp=sharing
Working great.
WoKoschekk said:
The easiest way to fix the problems caused by wrong flash commands is not to post any command.
As you can see nobody cares about your warnings. But later you are the one to blame for it.
Even if you write "your device will self-destruct after using the commands", would they use them anyway.
Always refer to the flashfile.xml
Click to expand...
Click to collapse
xda has changed a lot. Now anyone with half baked info just comes here and paste something and people tries it and brick their devices. I also used these commands and had flashed ROM which snowy has posted here, even that guy didn't replied afterwards lol when i said my device is hard bricked. So just wait and see what vache says. its horrible to do stuff with this device without proper info.
i guess these threads are nothing more than thanks meter increasing stuff.
methuselah said:
xda has changed a lot. Now anyone with half baked info just comes here and paste something and people tries it and brick their devices. I also used these commands and had flashed rom which snowy has posted here, even that guy didn't replied afterwards lol when i said my device is hard bricked. So just wait and see what vache says. Its horrible to do stuff with this device without proper info.
i guess these threads are nothing more than thanks meter increasing stuff.
Click to expand...
Click to collapse
i said what is your device channel!
methuselah said:
xda has changed a lot. Now anyone with half baked info just comes here and paste something and people tries it and brick their devices. I also used these commands and had flashed ROM which snowy has posted here, even that guy didn't replied afterwards lol when i said my device is hard bricked. So just wait and see what vache says. its horrible to do stuff with this device without proper info.
i guess these threads are nothing more than thanks meter increasing stuff.
Click to expand...
Click to collapse
And when did I once ask for a thanks on this post?
SnowTalker said:
And when did I once ask for a thanks on this post?
Click to expand...
Click to collapse
I do understand the intention of your first post. But you made the same mistake as other users made. Let me explain why.
All firmware .zips for Moto devices on mirrors.lolinet.com or Telegram groups were originally downloaded from Motorola's cloud servers. They are designed to be installed with the manufacturer's flash tools (e.g. LMSA). These tools use the .xml files (flashfile and service) to execute the flash commands that are needed to install the firmware images.
So that means this is Motorola's recommended way to flash your device.
1. By flashing the complete firmware (start with gpt.bin, the GUID partition table) your device switches automatically to slot A. I would like to explain you why but I don't know it exactly.
Since fastboot always uses the active slot, there's no need to specify slot A within your commands. It's not wrong or would mess up sth, but it's not needed.
2. Just because there's a corresponding partition on slot B you don't need to flash all images on A and B. Only images named like '*_other.img' are intended for this.
You also ignored the bootloader in this context. The bootloader consists of several partitions which are also devided in A and B (example Moto G6 Plus)
mmcblk0p1 -> xbl_a
mmcblk0p2 -> xbl_b
mmcblk0p3 -> tz_a
mmcblk0p4 -> tz_b
mmcblk0p5 -> rpm_a
mmcblk0p6 -> rpm_b
mmcblk0p7 -> hyp_a
mmcblk0p8 -> hyp_b
mmcblk0p9 -> devcfg_a
mmcblk0p10 -> devcfg_b
mmcblk0p11 -> pmic_a
mmcblk0p12 -> pmic_b
mmcblk0p13 -> abl_a
mmcblk0p14 -> abl_b
mmcblk0p15 -> cmnlib_a
mmcblk0p16 -> cmnlib64_a
mmcblk0p17 -> cmnlib_b
mmcblk0p18 -> cmnlib64_b
mmcblk0p19 -> keymaster_a
mmcblk0p20 -> keymaster_b
mmcblk0p21 -> storsec_a
mmcblk0p22 -> storsec_b
mmcblk0p23 -> prov_a
mmcblk0p24 -> prov_b
The bootloader.img is structured like the firmware .zip. It contains all the images which define the 'bootloader' and it also contains the commands to flash the images. You'll find them in the header.
<flash partition="xbl" filename="xbl.elf"/>
<flash partition="prov" filename="prov64.mbn"/>
<flash partition="cmnlib" filename="cmnlib.mbn"/>
<flash partition="cmnlib64" filename="cmnlib64.mbn"/>
<flash partition="abl" filename="abl.elf"/>
<flash partition="keymaster" filename="keymaster.mbn"/>
<flash partition="storsec" filename="storsec.mbn"/>
<flash partition="rpm" filename="rpm.mbn"/>
<flash partition="pmic" filename="pmic.elf"/>
<flash partition="hyp" filename="hyp.mbn"/>
<flash partition="tz" filename="tz.mbn"/>
<flash partition="devcfg" filename="devcfg.mbn"/>
I don't know if it's possible to use 'fastboot flash bootloader_b ...' at all.
You should understand that every image of the .zip only needs to be flashed once to the correct partition. So it doesn't make sense to post or use other's flash commands. Which commands need to be used depends on which images you want to flash. This defines the correct flash commands for you.
WoKoschekk said:
I do understand the intention of your first post. But you made the same mistake as other users made. Let me explain why.
All firmware .zips for Moto devices on mirrors.lolinet.com or Telegram groups were originally downloaded from Motorola's cloud servers. They are designed to be installed with the manufacturer's flash tools (e.g. LMSA). These tools use the .xml files (flashfile and service) to execute the flash commands that are needed to install the firmware images.
So that means this is Motorola's recommended way to flash your device.
1. By flashing the complete firmware (start with gpt.bin, the GUID partition table) your device switches automatically to slot A. I would like to explain you why but I don't know it exactly.
Since fastboot always uses the active slot, there's no need to specify slot A within your commands. It's not wrong or would mess up sth, but it's not needed.
2. Just because there's a corresponding partition on slot B you don't need to flash all images on A and B. Only images named like '*_other.img' are intended for this.
You also ignored the bootloader in this context. The bootloader consists of several partitions which are also devided in A and B (example Moto G6 Plus)
mmcblk0p1 -> xbl_a
mmcblk0p2 -> xbl_b
mmcblk0p3 -> tz_a
mmcblk0p4 -> tz_b
mmcblk0p5 -> rpm_a
mmcblk0p6 -> rpm_b
mmcblk0p7 -> hyp_a
mmcblk0p8 -> hyp_b
mmcblk0p9 -> devcfg_a
mmcblk0p10 -> devcfg_b
mmcblk0p11 -> pmic_a
mmcblk0p12 -> pmic_b
mmcblk0p13 -> abl_a
mmcblk0p14 -> abl_b
mmcblk0p15 -> cmnlib_a
mmcblk0p16 -> cmnlib64_a
mmcblk0p17 -> cmnlib_b
mmcblk0p18 -> cmnlib64_b
mmcblk0p19 -> keymaster_a
mmcblk0p20 -> keymaster_b
mmcblk0p21 -> storsec_a
mmcblk0p22 -> storsec_b
mmcblk0p23 -> prov_a
mmcblk0p24 -> prov_b
The bootloader.img is structured like the firmware .zip. It contains all the images which define the 'bootloader' and it also contains the commands to flash the images. You'll find them in the header.
<flash partition="xbl" filename="xbl.elf"/>
<flash partition="prov" filename="prov64.mbn"/>
<flash partition="cmnlib" filename="cmnlib.mbn"/>
<flash partition="cmnlib64" filename="cmnlib64.mbn"/>
<flash partition="abl" filename="abl.elf"/>
<flash partition="keymaster" filename="keymaster.mbn"/>
<flash partition="storsec" filename="storsec.mbn"/>
<flash partition="rpm" filename="rpm.mbn"/>
<flash partition="pmic" filename="pmic.elf"/>
<flash partition="hyp" filename="hyp.mbn"/>
<flash partition="tz" filename="tz.mbn"/>
<flash partition="devcfg" filename="devcfg.mbn"/>
I don't know if it's possible to use 'fastboot flash bootloader_b ...' at all.
You should understand that every image of the .zip only needs to be flashed once to the correct partition. So it doesn't make sense to post or use other's flash commands. Which commands need to be used depends on which images you want to flash. This defines the correct flash commands for you.
Click to expand...
Click to collapse
The thing is I have no intention of just jumping inside the threads. Whenever I read the things that i did wrong and the half baked stuff what comes from unreliable sources, I just try people not to make same mistakes that i did.
methuselah said:
The thing is I have no intention of just jumping inside the threads. Whenever I read the things that i did wrong and the half baked stuff what comes from unreliable sources, I just try people not to make same mistakes that i did.
Click to expand...
Click to collapse
ok sir. Whatever you say
Thanks Lollyjay, works a treat & got me out of trouble.
Hi,
I just bought an old Samsung Galaxy A5 (SM-A500FU) phone for experimenting purposes. I'd like to install LineageOS on this phone.
Apparently the phone has already been fiddled with. When booting into Download mode, it says "Current binary: Custom". So I downloaded the official firmware from sammobile.com and flashed it using Heimdall (I'm running Linux on my laptop):
Code:
heimdall flash \
--APNHLOS NON-HLOS.bin \
--MODEM modem.bin \
--SBL1 sbl1.mbn \
--ABOOT aboot.mbn \
--RPM rpm.mbn \
--QSEE tz.mbn \
--QHEE hyp.mbn \
--sec sec.dat \
--BOOT boot.img \
--RECOVERY recovery.img \
--SYSTEM system.img.ext4 \
--CACHE cache.img.ext4 \
--HIDDEN hidden.img.ext4
The official LineageOS documentation for my phone states to unlock the bootloader via the "OEM unlock" option in the developer options. Unfortunately this option is not showing on my phone, and judging from the number of blog posts on the web, I'm not the only one who's having this problem. Unfortunately the "solutions" offered on the web are not working, and most of them seem to be clickbait trash anyway.
Which leaves me clueless on how to unlock my bootloader. Any suggestions ?
PS : if you want to help, please post a method that works in your reply. Not some weird invitation to Discord, Telegram or some other obscure communication channel. This forum will do perfectly.
Hello kikinovak,
i have the same problem, but with a win10-pc. Because there is Stock-Android 6 on the mobile phone, there is no "OEM Unlock" in the developer options... Odin finds the device in fastboot mode, but i've to unlock the bootloader first...
Not really an advice, but who knows... ;o)
greetings from austria
on https://www.getdroidtips.com/oem-unlocking/ there is a new (but not helpful for me) info:
Now for devices launched in 2015 or later, type the following command: fastboot flashing unlock.
For devices launched prior to 2015, type the following command: fastboot oem unlock.
kikinovak said:
Hi,
I just bought an old Samsung Galaxy A5 (SM-A500FU) phone for experimenting purposes. I'd like to install LineageOS on this phone.
Apparently the phone has already been fiddled with. When booting into Download mode, it says "Current binary: Custom". So I downloaded the official firmware from sammobile.com and flashed it using Heimdall (I'm running Linux on my laptop):
Code:
heimdall flash \
--APNHLOS NON-HLOS.bin \
--MODEM modem.bin \
--SBL1 sbl1.mbn \
--ABOOT aboot.mbn \
--RPM rpm.mbn \
--QSEE tz.mbn \
--QHEE hyp.mbn \
--sec sec.dat \
--BOOT boot.img \
--RECOVERY recovery.img \
--SYSTEM system.img.ext4 \
--CACHE cache.img.ext4 \
--HIDDEN hidden.img.ext4
The official LineageOS documentation for my phone states to unlock the bootloader via the "OEM unlock" option in the developer options. Unfortunately this option is not showing on my phone, and judging from the number of blog posts on the web, I'm not the only one who's having this problem. Unfortunately the "solutions" offered on the web are not working, and most of them seem to be clickbait trash anyway.
Which leaves me clueless on how to unlock my bootloader. Any suggestions ?
PS : if you want to help, please post a method that works in your reply. Not some weird invitation to Discord, Telegram or some other obscure communication channel. This forum will do perfectly.
Click to expand...
Click to collapse
Hello,
Create a Windows VM and pass through all USB-input. It makes a lot easier!
You have to download the Samsung Drivers & Odin3 to your PC - install them.
Boot your phone ->ADB enabled (you don´t need the OEM-Unlock function, since it unlocks itself while flashing TWRP)<- into download mode (Vol. down + home + power).
Now flash your device specific TWRP with the AP-button using Odin3.
Make sure to uncheck auto reboot in Odin!
Unplug your phone, and hold Vol. up + home + power to boot into TWRP.
If you want to flash Lineage 18, make sure the TWRP version is at least 3.2, otherwise you´ll end up with error 7.
Feel free to ask me for help, in case you should need any!
Useful Links:
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.
developer.samsung.com
[RECOVERY][ROOT][TWRP 3.0.2-1]Samsung Galaxy A5(2015) SM-A500F/FU/G/H/M
Unofficial release -TWRP recovery for the Galaxy A5 - SM-A500F/FU/G/H/M, Qualcomm MSM8916 https://twrp.me/site/update/2016/04/05/twrp-3.0.2-0-released.html SEANDROID warning fix Recovery reboot fix Modem, APNHLOS, EFS and Recovery partition...
forum.xda-developers.com
Releases · DeadSquirrel01/lineage-17_a5_releases
lineageos 17 releases for Galaxy A5. Contribute to DeadSquirrel01/lineage-17_a5_releases development by creating an account on GitHub.
github.com
Download Odin 3.13.1 - Samsung Odin download with ROM Flashing Tool
Odin download. Download Samsung odin 3.13.1, latest Samsung ROM Flashing Tool for android - Samsung odin download
odindownload.com
This is what i´ve tested on my SM-A500FU.