Related
Hello.
I have a Samsung Relay that is rebranded by Cellular One of North East AZ. They have a fancy super thin sticker over the Tmobile logo on the glass. lol... But the firmware in the device is branded by Cellular One.
I cannot find that firmware anywhere and want to know if anyone has any directions on how to back up the firmware so It could be loaded onto a t-mobile Relay to "brand" it for Cellular One.
Appreciate any help you can offer.
Thanks.
(I normally play in CDMA world, but I moved to po dunk nothing ville and VZW Sucks here, so had to go with Cell One. First real experience with GSM)
I've never done this before and I'm not 100% sure if it can be done. But there probably are ways if you're clever enough. So here's what I would try if I were in your position:
1. Check if there's a way to dump it with Odin. You can google around to see if it's possible but I'm pretty sure it's a feature in Odin (Whether our phone supports it is another story). You would have to boot into download mode, (vol down + home + power when powering on) and then follow whatever directions you find for dumping a rom. Just make sure you don't flash anything to your device. And make sure you know what you're doing with Odin because it can brick your phone if you push the wrong buttons.
2. The other way to do it is to dump your partition contents with the dd command (I would do it through an adb shell). This would require you to have root. I'm not sure of how to get root without modifying your ROM (kind of defeats the purpose of what you're trying to do if we have to change the ROM) but there are usually ways to get a temp root. Not sure how to do it on our phone but maybe someone else can help you with that part. Or maybe do some googling. The dd part I've at least done for the boot partition. Basically what you want to do is open an adb shell and run:
"ls -l /dev/block/platform/msm_sdcc.1/by-name/"
This will give you a list of all the partition name symlinks and show you the block devices they point to. For example, when I was getting boot.img I found that the "boot" symlink pointed to "/dev/block/mmcblk0p7". Find all the partitions you want to image in this list and figure out which block devices they point to.
The next part is to figure out how big each of the partitions is. You can find this in /proc/partitions. So from your adb shell you would run:
"cat /proc/partitions"
This will print out all of your flash block devices (look at the ones you were interested in from above). The 3rd column in this list will be the # of blocks in the partition. I believe the block size is 1k (1024 bytes). For example, my boot partition was 10240 blocks which comes out to 10 Megs, which sounds about right. The 1k assumption also agrees with the total device flash size, which is 7634944 blocks (mmcblk0) which is just under the 8GB they say the phone has. So I'm pretty confident about the block size.
So now we're at the part where things get a little hairy. I'm assuming you've found some way to get root in your adb shell. Be very careful with these dd commands and if you don't know what you're doing, don't do it. You would want to run something like the following:
"dd if=/dev/block/<partition name> of=/storage/sdCard/<name of image file> bs=1024 count=<# of blocks for partition you found in /proc/partions>"
You would do this for each partition you want dumped.
Again, be careful if you decide to try and do any of this stuff (especially with the dd commands, if you mix up the in file and out file you can brick your device). But like I said this worked for me to get boot.img and I was able to extract it and get the kernel and ramdisk. Hope this helps and sorry I don't know more about getting you a temp root without modifying your ROM.
Jeff
Can you send me a screenshot of your about phone screen?
Sent from my SGH-T699 using Tapatalk
hello everyone,
i resurrection this thread so bring some information to pepole who want to backup stock rom so they can flash it back with odin.
i constructed a list of partitions names/partition location nb./partition block size for a refreance of what to backup:
block size partition block location partition name
7634944 /dev/block/mmcblk0 Whole SSD on Device
2048 /dev/block/mmcblk0p5 aboot
6144 /dev/block/mmcblk0p20 backup
10240 /dev/block/mmcblk0p7 boot
860160 /dev/block/mmcblk0p17 cache
13952 /dev/block/mmcblk0p11 efs
10240 /dev/block/mmcblk0p19 fota
3072 /dev/block/mmcblk0p21 fsg
5120 /dev/block/mmcblk0p23 grow
61440 /dev/block/mmcblk0p1 modem
3072 /dev/block/mmcblk0p12 modemst1
3072 /dev/block/mmcblk0p13 modemst2
512 /dev/block/mmcblk0p9 pad
10240 /dev/block/mmcblk0p10 param
8192 /dev/block/mmcblk0p16 persist
10240 /dev/block/mmcblk0p18 recovery
512 /dev/block/mmcblk0p6 rpm
128 /dev/block/mmcblk0p2 sbl1
256 /dev/block/mmcblk0p3 sbl2
512 /dev/block/mmcblk0p4 sbl3
8 /dev/block/mmcblk0p22 ssd
1228800 /dev/block/mmcblk0p14 system
512 /dev/block/mmcblk0p8 tz
5386240 /dev/block/mmcblk0p15 userdata
so all you have to do is to use this command via terminal:
"dd if=/dev/block/<partition name> of=/storage/sdCard/<name of image file> bs=1024 count=<# of blocks for partition>"
you can cnange "sdCard" for "extSdCard" if you wish.
this will make you the raw imgae of all partitions and then you will need to use tar in linux to make a tar.md5 file for odin.
use the commands below in terimanl to do so:
"tar -H ustar -c image1 image2 image3 etc... > package_name.tar"
"md5sum -t package_name.tar >> package_name.tar"
"mv package_name.tar package_name.tar.md5"
remember you will need superuser on you phone to do this, also the commands are without the quotation mark.
the only thing left to know is what partitions you must backup to beable to restore fully to stock with/without data.
i know you should backup the boot/efs/recovery/system partitions for clean stock + userdata/cache if you want your data back.
does anybody know of other critical partitions to backup?
I am able to connect my phone (BLU STUDIO 6.0 HD) to my computer and use ADB, then type in fastboot oem unlock. However, when I try to use my Volume Up button in order to select to unlock the bootloader, it wont work. Only the Volume Down button is working, which cancels the command. I am doing this in order to get a custom recovery and in turn get CyanogenMod working. I've been working on this all day and have found no solution. :crying: I would appreciate any help.
volume up not working in bootloader
I am able to connect my phone (lenovo vibe c2 k10a40) to my computer and use ADB, then type in fastboot oem unlock. However, when I try to use my Volume Up button in order to select to unlock the bootloader, it wont work. Only the Volume Down button is working, which cancels the command. I am doing this in order to get a custom recovery and in turn get CyanogenMod working. I've been working on this all day and have found no solution. I would appreciate any help.
I'm sorry for my English, I'm brazilian
same here im on a figo gravity x55l i sent in a ticket to figo support and they just ignored it but anyway
i tried
fastboot oem unlock
fastboot oem unlock-go
and also activating oem unlock in dev settings and doing fastboot methods again...nothing
i looked up that a phone unlocks its bootloader by enableing oem unlock in dev settings and doing a format and still nothing
---------- Post added at 03:15 PM ---------- Previous post was at 02:56 PM ----------
has anyone tried with a headset with volume buttons? i know it is crazy but i dont have a pair to try lol
GREAT NEWS I MANAGED TO GET ROOT WITHOUT UNLOCKING THE BOOTLOADER ALL YOU NEED IS TO
1.download your firmware and extract it
2.extract the boot.img from the firmware and put it on your phone REMEMBER WHERE YOU PUT IT SINCE YOU WILL NEED THIS!
3download magiskmanager install it and open it.
4click install and choose the boot.img it will install magisk into it
5.put it back in your firmware folder on your pc
6 look for a file that says Checksum_gen and run it
7 once that completes use spflash tool and load your scatterfile and flash JUST THE BOOT.IMG wait for the reboot and you have root!
THANK YOU DEVELOPERS OF MAGISKMANAGER!
Click like if this helped to get the word out...I think that's how it works
SP6RK said:
GREAT NEWS I MANAGED TO GET ROOT WITHOUT UNLOCKING THE BOOTLOADER ALL YOU NEED IS TO
1.download your firmware and extract it
2.extract the boot.img from the firmware and put it on your phone REMEMBER WHERE YOU PUT IT SINCE YOU WILL NEED THIS!
3download magiskmanager install it and open it.
4click install and choose the boot.img it will install magisk into it
5.put it back in your firmware folder on your pc
6 look for a file that says Checksum_gen and run it
7 once that completes use spflash tool and load your scatterfile and flash JUST THE BOOT.IMG wait for the reboot and you have root!
THANK YOU DEVELOPERS OF MAGISKMANAGER!
Click to expand...
Click to collapse
I'm new to mediatek and I have the same problem volume up won't unlock bootloader. I had the same idea you did and hopefully you can help.
First off I'm not sure I have the right firmware I have a Blu studio m5 plus is what the box says. The stock recovery calls it Blu dash xl when I look up firmware for Blu studio m5 plus it has one from need rom and you need to pay for an account to download. If you look up the dash xl firmware I was able to find it free and its specs match my phone I think it's the right firmware. If I patch the boot img from magisk. I need help with flashing with sp flash tool. Did you replace the actual boot img from the firmware with the new patched boot img or did you just load the new boot img from another folder. See I don't know what the Android scatter file really does. Does the boot img have to be in the same folder as firmware to flash because the scatter file finds that folder or not? And help with the checksum gen I'm unfamiliar how do I use it? What does it do? How do I use it to verify?
SP6RK said:
GREAT NEWS I MANAGED TO GET ROOT WITHOUT UNLOCKING THE BOOTLOADER ALL YOU NEED IS TO
1.download your firmware and extract it
2.extract the boot.img from the firmware and put it on your phone REMEMBER WHERE YOU PUT IT SINCE YOU WILL NEED THIS!
3download magiskmanager install it and open it.
4click install and choose the boot.img it will install magisk into it
5.put it back in your firmware folder on your pc
6 look for a file that says Checksum_gen and run it
7 once that completes use spflash tool and load your scatterfile and flash JUST THE BOOT.IMG wait for the reboot and you have root!
THANK YOU DEVELOPERS OF MAGISKMANAGER!
Click to expand...
Click to collapse
You need to try twrp porter from hovatek YouTube channel you can flash twrp without unlocking the bootloader.
https://forum.hovatek.com/thread-21839.html
I first made a backup with Wwr tool from hovatek without having root or unlocking bootloader then I patched my bootimg with magisk. Copied the boot img and scater file that Wwr tool also makes into a folder flashed the patched boot Img with S P flash tool rebooted was rooted with magisk. Then I used twrp booter and it takes like 3 minutes to make you a twrp out of your backup you get from Wwr tool. Without any work I just hit 6 enter puts out twrp recovery and I flashed that with s p flash tool rebooted directly into twrp recovery from phone off and it works great. With a locked bootloader.
SP6RK said:
GREAT NEWS I MANAGED TO GET ROOT WITHOUT UNLOCKING THE BOOTLOADER ALL YOU NEED IS TO
1.download your firmware and extract it
2.extract the boot.img from the firmware and put it on your phone REMEMBER WHERE YOU PUT IT SINCE YOU WILL NEED THIS!
3download magiskmanager install it and open it.
4click install and choose the boot.img it will install magisk into it
5.put it back in your firmware folder on your pc
6 look for a file that says Checksum_gen and run it
7 once that completes use spflash tool and load your scatterfile and flash JUST THE BOOT.IMG wait for the reboot and you have root!
THANK YOU DEVELOPERS OF MAGISKMANAGER!
Click to expand...
Click to collapse
Thank you so much for this guide, really worked like a charm. Been having troubles with flashing from fastboot mode due to button trouble.
Many thanks!!!
This method is interesting, does it really work? I am trying to get ROOT on this BLU Studio 6.0 HD D651 terminal, but it is useless, I cannot pass the bootloader security sector, I CANNOT flash the Recovery Partition, I am also trying to create the TWRP for a BLU Studio 6.0 HD D651 with this Hovatek program, but I can't conclude the flashing of this file
"ERROR in partition size", read Fastboot mode with Advenger Box and everything is fine, except the protected sector of the computer, bootloader locked ON. I leave here the Registry to see if you can help me. I also tried SP Flash Tools and it is the same, the Flash concludes well (GOOD / OK) but I restart in Recovery and it is the same Recovery Stock.
I also asked the people of Hovatek and they say that it is necessary to unlock the bootloader of the terminal, so what the partner says above I do not understand how I manage to circumvent security!
Posd. On the TWRP Team page the file “TWRP Custom Recovery 2.8 for BLU Studio 6.0 HD” was deleted! (Can anyone share it?)
Fastboot Reading phone info Avengers Box 0.6.2
max-download-size: 134217728
partition-size: userdata: 32000000
partition-type: userdata: ext4
partition-size: cache: 7e00000
partition-type: cache: ext4
partition-size: system: 3e800000
partition-type: system: ext4
partition-size: expdb: a00000
partition-type: expdb: raw data
partition-size: logo: 300000
partition-type: logo: raw data
partition-size: misc: 80000
partition-type: misc: raw data
partition-size: sec_ro: 600000
partition-type: sec_ro: ext4
partition-size: recovery: 1000000
partition-type: recovery: raw data
partition-size: boot: 1000000
partition-type: boot: raw data
partition-size: uboot: 60000
partition-type: uboot: raw data
partition-size: seccfg: 20000
partition-type: seccfg: raw data
partition-size: protect_s : a00000
partition-type: protect_s : ext4
partition-size: protect_f: a00000
partition-type: protect_f: ext4
partition-size: nvram: 500000
partition-type: nvram: raw data
partition-size: pro_info: 300000
partition-type: pro_info: raw data
partition-size: ebr1: 80000
partition-type: ebr1: raw data
partition-size: mbr: 80000
partition-type: mbr: raw data
partition-size: preloader: 1400000
partition-type: preloader: raw data
off-mode-charge: 1
warranty: yes
unlocked: no
secure: yes
kernel: lk
product: J805B_BLU
version: 0.5
Capture CMD ERROR:
EngelP said:
This method is interesting, does it really work? I am trying to get ROOT on this BLU Studio 6.0 HD D651 terminal, but it is useless, I cannot pass the bootloader security sector, I CANNOT flash the Recovery Partition, I am also trying to create the TWRP for a BLU Studio 6.0 HD D651 with this Hovatek program, but I can't conclude the flashing of this file
"ERROR in partition size", read Fastboot mode with Advenger Box and everything is fine, except the protected sector of the computer, bootloader locked ON. I leave here the Registry to see if you can help me. I also tried SP Flash Tools and it is the same, the Flash concludes well (GOOD / OK) but I restart in Recovery and it is the same Recovery Stock.
I also asked the people of Hovatek and they say that it is necessary to unlock the bootloader of the terminal, so what the partner says above I do not understand how I manage to circumvent security!
Posd. On the TWRP Team page the file “TWRP Custom Recovery 2.8 for BLU Studio 6.0 HD” was deleted! (Can anyone share it?)
Fastboot Reading phone info Avengers Box 0.6.2
max-download-size: 134217728
partition-size: userdata: 32000000
partition-type: userdata: ext4
partition-size: cache: 7e00000
partition-type: cache: ext4
partition-size: system: 3e800000
partition-type: system: ext4
partition-size: expdb: a00000
partition-type: expdb: raw data
partition-size: logo: 300000
partition-type: logo: raw data
partition-size: misc: 80000
partition-type: misc: raw data
partition-size: sec_ro: 600000
partition-type: sec_ro: ext4
partition-size: recovery: 1000000
partition-type: recovery: raw data
partition-size: boot: 1000000
partition-type: boot: raw data
partition-size: uboot: 60000
partition-type: uboot: raw data
partition-size: seccfg: 20000
partition-type: seccfg: raw data
partition-size: protect_s : a00000
partition-type: protect_s : ext4
partition-size: protect_f: a00000
partition-type: protect_f: ext4
partition-size: nvram: 500000
partition-type: nvram: raw data
partition-size: pro_info: 300000
partition-type: pro_info: raw data
partition-size: ebr1: 80000
partition-type: ebr1: raw data
partition-size: mbr: 80000
partition-type: mbr: raw data
partition-size: preloader: 1400000
partition-type: preloader: raw data
off-mode-charge: 1
warranty: yes
unlocked: no
secure: yes
kernel: lk
product: J805B_BLU
version: 0.5
Capture CMD ERROR:
Click to expand...
Click to collapse
Yeah it works try it but remember your bootloader is still locked so installing twrp might softbrick your device...find a way to unlock your bootloader
SP6RK said:
GREAT NEWS I MANAGED TO GET ROOT WITHOUT UNLOCKING THE BOOTLOADER ALL YOU NEED IS TO
1.download your firmware and extract it
2.extract the boot.img from the firmware and put it on your phone REMEMBER WHERE YOU PUT IT SINCE YOU WILL NEED THIS!
3download magiskmanager install it and open it.
4click install and choose the boot.img it will install magisk into it
5.put it back in your firmware folder on your pc
6 look for a file that says Checksum_gen and run it
7 once that completes use spflash tool and load your scatterfile and flash JUST THE BOOT.IMG wait for the reboot and you have root!
THANK YOU DEVELOPERS OF MAGISKMANAGER!
Click to expand...
Click to collapse
I tried this and it worked !
I've been trying to Flash-Root MTK 6580 Blu studio G2 HD,
Volume Up wasn't working to Unlock Bootloader . (I had to unlock it)
Flashed the patched boot.img with Spflash and it worked, i rooted my phone without unlocking bootloader.
Someone in the above comments said to Unlock Bootloader somehow, Flashing anything with TWRP or anyother software may brick phone.
(I think you shouldn't unlock bootloader unless you absolutely need it)
Volume up button
I was having the same trouble.
Check if you have any software update .
Update them and try again i hope it will work.
It works for me samsung a10s
Techguy777 said:
You need to try twrp porter from hovatek YouTube channel you can flash twrp without unlocking the bootloader.
https://forum.hovatek.com/thread-21839.html
I first made a backup with Wwr tool from hovatek without having root or unlocking bootloader then I patched my bootimg with magisk. Copied the boot img and scater file that Wwr tool also makes into a folder flashed the patched boot Img with S P flash tool rebooted was rooted with magisk. Then I used twrp booter and it takes like 3 minutes to make you a twrp out of your backup you get from Wwr tool. Without any work I just hit 6 enter puts out twrp recovery and I flashed that with s p flash tool rebooted directly into twrp recovery from phone off and it works great. With a locked bootloader.
Click to expand...
Click to collapse
Thanks SO much Techguy777!! I can absolutely confirm that after MANY, MANY days day of trying to get my MTK6582 device rooted , this process worked perfectly without unlocking the bootloader. I already had the Magisk patched boot image file and all the SP Flash tool set but didn't know how to use them correctly. I followed the step-by-step guide here:
SP Flash Tool - Basic User Guide
Install Mediatek Drivers Extract the Mediatek_USB_Driver_Auto-Installer zip file. Run the installer file that is extracted from zip by right clicking the .exe file and click on "Run as Administrator". ( the exe file that comes out of zip = Mediatek_Driver_Auto-Installer.exe ) Click on "Install"...
gpdcentral.com
Enjoy!
SP6RK said:
GREAT NEWS I MANAGED TO GET ROOT WITHOUT UNLOCKING THE BOOTLOADER ALL YOU NEED IS TO
1.download your firmware and extract it
2.extract the boot.img from the firmware and put it on your phone REMEMBER WHERE YOU PUT IT SINCE YOU WILL NEED THIS!
3download magiskmanager install it and open it.
4click install and choose the boot.img it will install magisk into it
5.put it back in your firmware folder on your pc
6 look for a file that says Checksum_gen and run it
7 once that completes use spflash tool and load your scatterfile and flash JUST THE BOOT.IMG wait for the reboot and you have root!
THANK YOU DEVELOPERS OF MAGISKMANAGER!
Click to expand...
Click to collapse
Thank you. This really works to get magisk so easily installed without having to unlock bootloader. No need to even install TWRP recovery.
SP6RK said:
GREAT NEWS I MANAGED TO GET ROOT WITHOUT UNLOCKING THE BOOTLOADER ALL YOU NEED IS TO
1.download your firmware and extract it
2.extract the boot.img from the firmware and put it on your phone REMEMBER WHERE YOU PUT IT SINCE YOU WILL NEED THIS!
3download magiskmanager install it and open it.
4click install and choose the boot.img it will install magisk into it
5.put it back in your firmware folder on your pc
6 look for a file that says Checksum_gen and run it
7 once that completes use spflash tool and load your scatterfile and flash JUST THE BOOT.IMG wait for the reboot and you have root!
THANK YOU DEVELOPERS OF MAGISKMANAGER!
Click like if this helped to get the word out...I think that's how it works
Click to expand...
Click to collapse
What is Checksum_gen file? I can't find it in firmware folder
lyehengfoo said:
Thank you. This really works to get magisk so easily installed without having to unlock bootloader. No need to even install TWRP recovery.
Click to expand...
Click to collapse
Please guide me too. What is Checksum_gen file? I can't find it in firmware folder
After hours of research over the internet and a couple of nights in front of my computer, I finally found a method who can help resurrect any Mate 8 variant which is stuck on bootloop.
You will need 3 things:
- DC Phoenix New Account (it costs 15 euros for 15 credits to use for 72h after initial flash (small price to pay compared to sending to repair shop or having a useless brick) -
- An UPDATE.APP at your choice for your phone (AL10 or L29, both are interchangeable) -
- This file with partition rework and factory firmware - DOWNLOAD -
Steps:
1. Make sure you have at least 30% of battery.
2. Open DC Phoenix and login with your credentials.
3. Put your phone in fastboot mode (Vol. - + Power).
4. Select «fastboot mode» in DC Phoenix and then go to the «IMG FILES» tab.
5. Select the «NXT-AL10_M00A102_Factory_firmware_Global_Nonspecific_Android_6.0_EMUI_4.0» file and hit Open.
6. Click on «Update» and be patient. This should take 10 minutes.
7. Follow the log on the left. When it says «writing success», reboot your phone (Vol. - and Power until display goes off). The phone should normally boot into a Chinese-like ROM.
8. Put your phone back in fastboot mode and select the «APP FILES» tab in DC Phoenix.
9. Select your UPDATE.APP file and hit Update. Be patient. This may take up to 20 minutes.
10. Again, look at the log for «writing success» line and then reboot your phone.
Enjoy!
You can unlock your bootloader if it is not locked and install TWRP.
WOOOT This worked but HOW!?! And what is this backdoor hack to load the image (see log ) ? LOL!
ps: the downloaded file has a different name: NXT-AL10_M00A102_Factory_firmware_Global_Nonspecific_Android_6.0_EMUI_4.0.dgtks
in the here above filename is wrong/different: NXT-L29_NV_partitions_backup.dgtks (Corrected by TS)
Corrected: ps I checked the MEGA download file with the DC-Unlocker download ( https://files.dc-unlocker.com/user.html?v=files/57694006a60d7 )
they are the same:
K:\>fc /b NXT-AL10_M00A102_Factory_firmware_Global_Nonspecific_Android_6.0_EMUI_4.0_DC_UNL.dgtks NXT-AL10_M00A102_Factory_firmware_Global_Nonspecific_Android_6.0_EMUI_4.0_Mega.dgtks
Comparing files NXT-AL10_M00A102_Factory_firmware_Global_Nonspecific_Android_6.0_EMUI_4.0_DC_UNL.dgtks and NXT-AL10_M00A102_FACTORY_FIRMWARE_GLOBAL_NONSPECIFIC_ANDROID_6.0_EMUI_4.0_MEGA.DGTKS
FC: no differences encountered
anyway
i loaded up the downloaded NXT-AL10_M00A102_Factory_firmware_Global_Nonspecific_Android_6.0_EMUI_4.0.dgtks from MEGA ( see download link from djmitza222)
into DC 0.0.35 and this happened ( see log )
options:
Force upgrade OFF
not erase NV ON
Not Erase oeminfo ON
after this the Phone boots ands is all OK and i have C900B320
ps: My phone was bootloader unlocked and FRP Locked
i dont have installed some sort of virus / backdoor ?!
and can somebody explain why i spend days with tools and stuff but this actually worked ( for 15 euro ok ) ??
########################DC LOG #################### #
The file was loaded successfully
Device found: QHC021******9247
IMEI: 86840*********23
Build number: :NRD90M test-keys
Product model: NXT-L29
Erasing nvme partition
ERASE partition nvme ...FAILED
Cannot get FBlock info from device
Activating backdoor: DONE
Erasing nvme partition
Partition nvme erased
Erasing cust partition
Partition cust erased
Erasing misc partition
Partition misc erased
Writing xloader partition with file fastbootimage/sec_xloader.img
xloader partition UPDATE ...OK
Writing ptable partition with file fastbootimage/ptable.img
ptable partition UPDATE ...OK
Writing fastboot partition with file fastbootimage/sec_fastboot.img
fastboot partition UPDATE ...OK
Writing dts partition with file fastbootimage/sec_dt.img
dts partition UPDATE ...OK
Writing fw_lpm3 partition with file fastbootimage/sec_lpm3.img
fw_lpm3 partition UPDATE ...OK
Writing sensorhub partition with file fastbootimage/sec_sensorhub.img
sensorhub partition UPDATE ...OK
Writing fw_hifi partition with file fastbootimage/sec_hifi.img
fw_hifi partition UPDATE ...OK
Writing teeos partition with file fastbootimage/sec_trustedcore.img
teeos partition UPDATE ...OK
Writing recovery partition with file fastbootimage/sec_recovery.img
recovery partition UPDATE ...OK
Writing recovery2 partition with file fastbootimage/sec_erecovery.img
recovery2 partition UPDATE ...OK
Erasing cache partition
Partition cache erased
Writing cache partition with file fastbootimage/cache.img
cache partition UPDATE ...OK
Writing boot partition with file fastbootimage/sec_boot.img
boot partition UPDATE ...OK
Writing nvme partition with file fastbootimage/nvme.img
nvme partition UPDATE ...OK
Writing trustfirmware partition with file fastbootimage/sec_bl31.bin
trustfirmware partition UPDATE ...OK
Writing modem partition with file fastbootimage/sec_balong_modem.bin
modem partition UPDATE ...OK
Writing modem_dtb partition with file fastbootimage/sec_modem_dt.img
modem_dtb partition UPDATE ...OK
Writing modemnvm_update partition with file fastbootimage/nv.bin
modemnvm_update partition UPDATE ...OK
Writing modem_dsp partition with file fastbootimage/sec_lphy.bin
modem_dsp partition UPDATE ...OK
Writing modem_om partition with file fastbootimage/modem_fs.img
modem_om partition UPDATE ...OK
Writing modemnvm_img partition with file fastbootimage/modem_nv.img
modemnvm_img partition UPDATE ...OK
Writing 3rdmodem partition with file fastbootimage/3rdmodem.img
3rdmodem partition UPDATE ...OK
Writing 3rdmodemnvm partition with file fastbootimage/3rdmodemnvm.img
3rdmodemnvm partition UPDATE ...OK
Writing 3rdmodemnvmbkp partition with file fastbootimage/3rdmodemnvmbkp.img
3rdmodemnvmbkp partition UPDATE ...OK
Erasing userdata partition
Partition userdata erased
Writing userdata partition with file fastbootimage/userdata.img
userdata partition UPDATE ...OK
Writing system partition with file fastbootimage/system.img
system partition UPDATE ...OK
Writing splash2 partition with file fastbootimage/splash2.img
splash2 partition UPDATE ...OK
Writing frp partition with file fastbootimage/frp.img
frp partition UPDATE ...OK
Erasing cust partition
Partition cust erased
Writing cust partition with file fastbootimage/cust_factory.img
cust partition UPDATE ...OK
Writing secure_storage partition with file fastbootimage/secure_storage.img
secure_storage partition UPDATE ...OK
Software written
5/1/2017 9:28:59 PM Writing device finished OK
Current version: NextL09C999B100EMUI41
Extracting partitions
Cannot create extract directory: K:\DC_Phoenix\tmp\20170501_213206_UPDATE\
Extract files to directory: K:\DC_Phoenix\
Extracting partition: XLOADER OK
Extracting partition: FW_LPM3 OK
Extracting partition: FASTBOOT OK
Extracting partition: MODEMNVM_UPDATE OK
Extracting partition: TEEOS OK
Extracting partition: TRUSTFIRMWARE OK
Extracting partition: SENSORHUB OK
Extracting partition: FW_HIFI OK
Extracting partition: BOOT OK
Extracting partition: RECOVERY OK
Extracting partition: RECOVERY2 OK
Extracting partition: DTS OK
Extracting partition: MODEM OK
Extracting partition: MODEM_DSP OK
Extracting partition: 3RDMODEM OK
Extracting partition: SYSTEM OK
Extracting partition: CUST OK
Extracting partition: MODEM_DTB OK
Device found: 012345*********BCDEF
IMEI: 868*******692123
Build number: HLNXTAL10BM00A102
Product model: HUAWEI
Writing XLOADER partition with file K:\DC_Phoenix\XLOADER.img
XLOADER partition UPDATE ...OK
Writing FW_LPM3 partition with file K:\DC_Phoenix\FW_LPM3.img
FW_LPM3 partition UPDATE ...OK
Writing FASTBOOT partition with file K:\DC_Phoenix\FASTBOOT.img
FASTBOOT partition UPDATE ...OK
Writing MODEMNVM_UPDATE partition with file K:\DC_Phoenix\MODEMNVM_UPDATE.img
MODEMNVM_UPDATE partition UPDATE ...OK
Writing TEEOS partition with file K:\DC_Phoenix\TEEOS.img
TEEOS partition UPDATE ...OK
Writing TRUSTFIRMWARE partition with file K:\DC_Phoenix\TRUSTFIRMWARE.img
TRUSTFIRMWARE partition UPDATE ...OK
Writing SENSORHUB partition with file K:\DC_Phoenix\SENSORHUB.img
SENSORHUB partition UPDATE ...OK
Writing FW_HIFI partition with file K:\DC_Phoenix\FW_HIFI.img
FW_HIFI partition UPDATE ...OK
Writing BOOT partition with file K:\DC_Phoenix\BOOT.img
BOOT partition UPDATE ...OK
Writing RECOVERY partition with file K:\DC_Phoenix\RECOVERY.img
RECOVERY partition UPDATE ...OK
Writing RECOVERY2 partition with file K:\DC_Phoenix\RECOVERY2.img
RECOVERY2 partition UPDATE ...OK
Writing DTS partition with file K:\DC_Phoenix\DTS.img
DTS partition UPDATE ...OK
Writing MODEM partition with file K:\DC_Phoenix\MODEM.img
MODEM partition UPDATE ...OK
Writing MODEM_DSP partition with file K:\DC_Phoenix\MODEM_DSP.img
MODEM_DSP partition UPDATE ...OK
Writing 3RDMODEM partition with file K:\DC_Phoenix\3RDMODEM.img
3RDMODEM partition UPDATE ...OK
Writing SYSTEM partition with file K:\DC_Phoenix\SYSTEM.img
SYSTEM partition UPDATE ...OK
Erasing CUST partition
Partition CUST erased
Writing CUST partition with file K:\DC_Phoenix\CUST.img
CUST partition UPDATE ...OK
Writing MODEM_DTB partition with file K:\DC_Phoenix\MODEM_DTB.img
MODEM_DTB partition UPDATE ...OK
Software written
5/1/2017 9:34:22 PM Writing device finished OK
Thank you for your remark! I edited the post with the correct filename.
Concerning the flash method, I think it's based on some sort of exploit. If you looked into the about section of factory firmware, you may notice that it's Android 4.3. This method is awesome because it restores the partition layout back. So if you screw something up, you have a rescue.
flashing the device 2 times 1-factory firmware 2-update.app should cost me 15 or 30 ?
No, it will cost you only 15 € / device. Lifetime. You can flash it as many times you want.
my phone back to work thanks
confirmed
phone is back to work
this is the only solution that i didn't try to avoid pay the 15 euro
but after downloading all the Failes from the internet i give this one a shot and its works
my phone was stack on boot loop and cant boot recovery twrp
phonw unlocked
Fr unlocked
to those how have same problem this is the only way don't waste your Time
thanks again
I have a huawei mate 8 al10 version, can I use the l29 firmware for unbrick and then I also get the international firmware on my phone?
Hi,
this tool really unbricked my Mate 8.
But one thing is that my serialnumber is not correct (0123456789ABCDEF). >> There is the HCU Client to fix this, I haven´t checked yet.
The other thing is, the Internet Connection does not work good. The phone is connected with wifi or mobile LTE
but it always says "no Connection to the Internet".
Do These two things stuck together or are These sepaerate Problems ??
What can I do with Internet failure ?
Greez Rainer
The internet its a common problem for B320 and B330 software versions. You cannot fix them only by flashing a different modem firmware.
Concerning thr serial, you should restore your OEMInfo backup. If you don't have it, then you should fix it via HCU Client and generate your new bootloader unlock code.
Thanks for your answer. But how can I fix the Internet Problem ?
djmitza222 said:
Thank you for your remark! I edited the post with the correct filename.
Concerning the flash method, I think it's based on some sort of exploit. If you looked into the about section of factory firmware, you may notice that it's Android 4.3. This method is awesome because it restores the partition layout back. So if you screw something up, you have a rescue.
Click to expand...
Click to collapse
So that file linked to post #3 will set the phone back to an android 4.3 base? Would it be possible do you think, to flash that through DC, and then be able to put an EMUI 4 rom like B211 on to try to get better battery life back?
Thanks for this guide, at least my phone is working again at all! :good:
But I'm facing some problems flashing a new TWRP (regardless of which version). Maybe you have a hint for me?
I am no longer have this device so I cannot assist you more than this. It's a very good device but with very poor support from developers.
djmitza222 said:
I am no longer have this device so I cannot assist you more than this. It's a very good device but with very poor support from developers.
Click to expand...
Click to collapse
Fair enough! I don't think I'll try it - juuuuust in case
djmitza222 said:
I am no longer have this device so I cannot assist you more than this. It's a very good device but with very poor support from developers.
Click to expand...
Click to collapse
Ok, still thanks for the reply. However it'll turn out, this guide was a HUGE step forward and absolutely worth the 15 bucks. :good:
question??
Patneu said:
Thanks for this guide, at least my phone is working again at all! :good:
But I'm facing some problems flashing a new TWRP (regardless of which version). Maybe you have a hint for me?
Click to expand...
Click to collapse
man ve u unbricked a mate 8 with this program?? i need to know becuase i don t want to waste 15 euro :laugh: (sry for bad english i m italian xD)
DangerousKai said:
man ve u unbricked a mate 8 with this program?? i need to know becuase i don t want to waste 15 euro :laugh: (sry for bad english i m italian xD)
Click to expand...
Click to collapse
Yes, here's what worked for me. Also, note my little update here. Hope it works out for you, too.
Patneu said:
Yes, here's what worked for me. Also, note my little update here. Hope it works out for you, too.
Click to expand...
Click to collapse
Man ty i ve unbricked my mate 8 only one questio, i ve installed my ROM stock b192 . i can update to b560 with ota autoupdate?
My stock build is L29C652B101 (demo firmware)
Is it possible to restore an update.app from L29C432B330 (european build)?
When I tray to enter in fastboot the screen is black and the PC can't see the phone
This is what i was able to... Um pull from the manufacturer website it explains a clearly documented exploit
MSM8937 platform AP is the eight-core A53 processor, divided into two clusters, the highest frequency support 1.4GHZ, PMIC has two combinations: PM8937 + PMI8937 and PM8937 + PMI8952.
Qualcomm platform starts from the PBL, that is, the internal ROM to start running, PBL load SBL1 and RPM part, SBL1 start running, SBL1 load RPM part, TZ, APPSBL (aboot). After loading should start lk, but SBL1 will not directly start lk, but by the TZ to start, TZ is divided into two parts: QSEE, QHEE. SBL1 operating environment tax 32bit, while the TZ is 64bit. Therefore, in the SBL1 last jump to QSEE need to switch to aarch64, and then trigger a warm reset, this will start to QSEE 64bit operating environment by QSEE run. QSEE will inform the RPM to start running, then QHEE start running, and finally by QHEE start lk.
SBL1 in general to modify a few places are: 1) CDT, here to change the platform information, such as MTP or QRD, etc., there is the DDR parameters; 2) UART port, if you want to see SBL1 print information, then you must To configure the UART port, of course, if the default UART port just like the hardware connection, then this does not have to change. If not consistent, then need to modify uart_sbl_8937.xml as follows:
According to the hardware to modify UART_PHY_DEVICE_X, X can be 1,2,3,4. Serial port baud rate of 115200.
Debugging encountered a very strange problem is that SBL1 finally jump to QSEE trigger warm reset when the system restart, because there is no UART inside the TZ print, it is not clear when the switch to TZ when the problem is still in the Run TZ when the problem is still in the start lk when the problem. And later made a lot of attempts to find that may be related to the control of the UART port. Hardware UART port is UART1, and the default configuration of the version of the UART2, the value of SBL1 and modified, but also in the TZ configuration, TZ BLSP will be the various QUP and UART access control interface The And UART1 default access is TZ, that is, only by the TZ access, but in the initialization of lk also need to initialize the UART port for print output, this will lead to conflict caused the system to restart. Need to modify the TZ is an xml file. After the re-translation devcfg.mbn, so that the system can see the lk run the log.
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.