Database Develop

Need help with firmware 6.13.707.1

G'day all,
I'm from Malaysia and the latest firmware has just been released which is the 6.13.707.1 and I've found a link to download this firmware here. However, I understand that flashing firmwares may cause the sdcard to be wiped. I'm hoping someone could give me a pointer on how to mod or remove any components in this firmware zip to avoid it from wiping the sdcard before I flash it. Thanks!

HI there,
just remove all dzdata* files from firmware.zip.

wlteh said:
G'day all,
I'm from Malaysia and the latest firmware has just been released which is the 6.13.707.1 and I've found a link to download this firmware here. However, I understand that flashing firmwares may cause the sdcard to be wiped. I'm hoping someone could give me a pointer on how to mod or remove any components in this firmware zip to avoid it from wiping the sdcard before I flash it. Thanks!
Click to expand...
Click to collapse
That's only the untouched firmware that I uploaded for those who want to revert to original firmware after he flashed a modded firmware like the one with removed red text warning. And it won't wipe your sdcard.
What actually you want to achieve ? If it is to update your ROM to 4.4.3, this won't work.
If you plan to update the firmware only then use a custom 4.4.3 ROM, then this should be ok.
See this if your intention is to update to Stock 4.4.3 ROM : http://forum.xda-developers.com/showpost.php?p=55002536&postcount=7644

darkarvan said:
HI there,
just remove all dzdata* files from firmware.zip.
Click to expand...
Click to collapse
Thanks I'll give it a try.

ckpv5 said:
That's only the untouched firmware that I uploaded for those who want to revert to original firmware after he flashed a modded firmware like the one with removed red text warning. And it won't wipe your sdcard.
What actually you want to achieve ? If it is to update your ROM to 4.4.3, this won't work.
If you plan to update the firmware only then use a custom 4.4.3 ROM, then this should be ok.
See this if your intention is to update to Stock 4.4.3 ROM : http://forum.xda-developers.com/showpost.php?p=55002536&postcount=7644
Click to expand...
Click to collapse
Thanks a lot for the firmware bro! I'm currently on a custom 4.4.3 ROM and I'd like to update the firmware to 6.13.707.1 which is the closest to our country.

wlteh said:
Thanks a lot for the firmware bro! I'm currently on a custom 4.4.3 ROM and I'd like to update the firmware to 6.13.707.1 which is the closest to our country.
Click to expand...
Click to collapse
I see ... if that's the case remove the boot.img and recovery.img from the firmware.zip so you don't have to reflash custom recovery and kernel.

ckpv5 said:
I see ... if that's the case remove the boot.img and recovery.img from the firmware.zip so you don't have to reflash custom recovery and kernel.
Click to expand...
Click to collapse
Thank you very much, really appreciate it!

[GUIDE] Get rid of balong bug/get back local update on 6.0/unlock bootloader[ALE-L21]

First of all, what is balong bug?
Balong Bug is when you update to a newer firmware that was not meant for your country, your phone doesn't recognize the correct version of your software(instead of correct version it will show balongc53b311) and you can't do ota update.
So in order to get rid of balong bug, when you update your software to a newer version, in the archive you've downloaded there are 2 folders: one contains the firmware update and one folder named custom or vendor which contains update.app for balong bug.
So all you have to do is to install via local update the update.app from vendor/custom folder.
I've tried to find for as many as possibile versions i could find.
I've made an archive of all vendor folders. Download from here
Here is the list from archive:
B049
B120
B130
B132
B133
B171
B551
Now, in order to get local update back, you'll need to have unlocked bootloader and twrp installed because you'll need to flash an archive.
First, make sure you have installed the correct drivers, then enable usb debugging from developer options(tap 7 times on build number to unlock developer)
To unlock bootloader you'll need to register on huawei then enter your details here.
If you have dual sim,enter your main imei;
After you've done all this you'll have a 10 digit code number, save it.
Now download minimal adb fastboot from here and install it.
Plug the phone into pc, open cmd window in minimal folder(shift + right click -> open new command here), type:
Code:
adb devices
and in return it will show something like
Code:
123213asdsa231 device
. After this type
Code:
adb reboot bootloader
. Now you are in fastboot and here you'll unlock your bootloader by tiping this command:
Code:
fastboot oem unlock yourcode
. If you done all this, now it will show on the bottom Phone Unlocked.
Now you need TWRP from here.
Flash it via fastboot with this command:
Code:
fastboot flash recovery image_name.img
.
Enter twrp, flash this archive.
Now you've got back your local update!.
In order to get back stock recovery, donwload your current firmware version, use huawei extractor to extract recovery.img from update.app and flash it via fastboot with the same command used to flash twrp.
If you have questions, ask here.

Please add the newer B564 to the patch

I'm sorry, but i can't find for b564 ...

hey i tried updating locally on b560, but am stuck at 19% for like half an hour...

Bootloader is now unlocked, fast boot works as i can boot to bootloader but i cant push twrp for some reason.
Edit: fixed, wasn't looking for the correct file to put twrp into.
So i flashed B550 i think which doesn't have Vendor file, how can i get to B551 or one that does, will i need to downgrade first.

BigD18t said:
Bootloader is now unlocked, fast boot works as i can boot to bootloader but i cant push twrp for some reason.
Edit: fixed, wasn't looking for the correct file to put twrp into.
So i flashed B550 i think which doesn't have Vendor file, how can i get to B551 or one that does, will i need to downgrade first.
Click to expand...
Click to collapse
Search for the program that can change your vendor info.
amageek said:
hey i tried updating locally on b560, but am stuck at 19% for like half an hour...
Click to expand...
Click to collapse
What version do you currently running??

VladHD said:
Search for the program that can change your vendor info.
What version do you currently running??
Click to expand...
Click to collapse
I did do that, but it caused my sim to not work at all, not sure what i did after but i now have it all working correctly and no bug.

VladHD said:
Search for the program that can change your vendor info.
What version do you currently running??
Click to expand...
Click to collapse
hey i successfully flashed it... thanks anyways...
P.S. I was on b560 (Poland)...

please reupload archive/files to fix balong bug.
given download link is not working anymore.

huawei2016 said:
please reupload archive/files to fix balong bug.
given download link is not working anymore.
Click to expand...
Click to collapse
Here is the link for vendor information file
https://yadi.sk/d/vxXXNOxss6hjK
Credits: @sokkoban

miststudent2011 said:
Here is the link for vendor information file
https://yadi.sk/d/vxXXNOxss6hjK
Click to expand...
Click to collapse
many thanks dear, many vendors files failed. but your zip file worked well.
now p8 lite dual sim, ale l21 is showing c432b574full update is available. current version is c432b204.

huawei2016 said:
many thanks dear, many vendors files failed. but your zip file worked well.
now p8 lite dual sim, ale l21 is showing c432b574full update is available. current version is c432b204.
Click to expand...
Click to collapse
Good to hear that you solved your problem.
All the credits for the Zip file goes to @sokkoban you should thank him for all his efforts.

My South African ALE-L02 is currently running Android 6.0 C636B530, with the Balong error after the firmware upgrade.. Would I be able to simply flash the Vendor (Custom) file, or do I need to follow other steps first?

hi,
kindly provide the update firmwarefor huawei balong c52b311, and provide solution for locked bootloader to unlock , thanks

Hi im from iran
and my build number is balongc50b311
can I fix it by flashing this file?
menu language is not important for me im using english.

gholamzadeh.mr said:
Hi im from iran
and my build number is balongc50b311
can I fix it by flashing this file?
menu language is not important for me im using english.
Click to expand...
Click to collapse
Yes. Or simply install clean b638 and then personas rom

thank u
i used the app and it worked good.
now my build is c432b132. can i directly flash c432b638 rom?

gholamzadeh.mr said:
thank u
i used the app and it worked good.
now my build is c432b132. can i directly flash c432b638 rom?
Click to expand...
Click to collapse
Not sure but yes try it. First, full wipe everything, than install stock b638 than personas mod.

I did it,
first,I flashed recovery ( it was twrp) and installed stock recovery,
then installed c432b638
my data and apps was not deleted.

@VladHD link is not working

[CUST] Universal Cust Mod

Here is the universal cust mod. If you have a Helium (64/128gb) Mi Max and want to flash the Global ROM on it, the cust mod will unlock all Locales. Merged is the cust from the 32GB Global ROM and the Chinese 64/128GB rom. The Chinese region is set to US as well. I removed the extra unnecessary preinstalled apps from the cust folders as well. To flash the global rom simply fastboot flash the boot.img and system.img from the global rom through fastboot. Then make sure you have TWRP installed and boot into it immediately after flashing the global rom and flash the Universal Cust Mod. Then (optional) flash SuperSU in TWRP. After a reboot you'll be on the Global rom on your Helium.
Current Version:
https://drive.google.com/file/d/0B5I_q70mNuR4enNsU3hjbnpNeGs/view?usp=sharing​

ajsmsg78 said:
Here is the universal cust mod. If you have a Helium (64/128gb) Mi Max and want to flash the Global ROM on it, the cust mod will unlock all Locales. Merged is the cust from the 32GB Global ROM and the Chinese 64/128GB rom. The Chinese region is set to US as well. I removed the extra unnecessary preinstalled apps from the cust folders as well. To flash the global rom simply fastboot flash the boot.img and system.img from the global rom through fastboot. Then make sure you have TWRP installed and boot into it immediately after flashing the global rom and flash the Universal Cust Mod. Then (optional) flash SuperSU in TWRP. After a reboot you'll be on the Global rom on your Helium.
Current Version:
https://drive.google.com/file/d/0B5I_q70mNuR4enNsU3hjbnpNeGs/view?usp=sharing​
Click to expand...
Click to collapse
Do not flash boot img from hydrogen to helium, otherwise bricked device guaranteed.
Flashing different boot.img on locked bootloader will result a hardbrick and only testpoin method will work.

Doom Slayer said:
Do not flash boot img from hydrogen to helium, otherwise bricked device guaranteed.
Flashing different boot.img on locked bootloader will result a hardbrick and only testpoin method will work.
Click to expand...
Click to collapse
The boot.img from each model is pretty much the same. I don't recommend flashing anything other than stock roms with a locked bootloader, I would unlock the bootloader first before flashing any custom roms or mods. I also have a Global rooted ROM for the Helium I'm testing with google apps and Adaway. I should have a release tomorrow.

ajsmsg78 said:
The boot.img from each model is pretty much the same. I don't recommend flashing anything other than stock roms with a locked bootloader, I would unlock the bootloader first before flashing any custom roms or mods. I also have a Global rooted ROM for the Helium I'm testing with google apps and Adaway. I should have a release tomorrow.
Click to expand...
Click to collapse
Well, I got instruction posted how to flash custom roms and get root without unlocking bootloader, posted in guides section.
I tried flashing global rom for hydrogen on my helium then your mod and ended up with a hardbrick.
Then I tried to flash it with boot.img and the same result.
Had to put device in EDL with testpoint.
I guess it doesn't work with locked bootloader, while custom roms work fine.
I am also a ROM/Kernel developer but I just don't want to unlock my device, unless they release kernel sources.
But I was developing for Sony, there are no cust at least for Z Ultra.
Did I get that correctly and it's just unlocking languages that are in the rom?

Doom Slayer said:
Do not flash boot img from hydrogen to helium, otherwise bricked device guaranteed.
Flashing different boot.img on locked bootloader will result a hardbrick and only testpoin method will work.
Click to expand...
Click to collapse
Hey Doom, it'll be extremely helpful if you could write a guide about using that test point... I read some russian and I still couldn't get how exactly you connect it to battery from that 4PDA guide!? Best start with how you open the phone.
It'll help a lot of people seeing so many bricked devices...
Thank you for all the useful info you bring here!

Doom Slayer said:
Well, I got instruction posted how to flash custom roms and get root without unlocking bootloader, posted in guides section.
I tried flashing global rom for hydrogen on my helium then your mod and ended up with a hardbrick.
Then I tried to flash it with boot.img and the same result.
Had to put device in EDL with testpoint.
I guess it doesn't work with locked bootloader, while custom roms work fine.
I am also a ROM/Kernel developer but I just don't want to unlock my device, unless they release kernel sources.
But I was developing for Sony, there are no cust at least for Z Ultra.
Did I get that correctly and it's just unlocking languages that are in the rom?
Click to expand...
Click to collapse
Yeah the cust mod unlocks most Languages and unlocks all regions but those are the things you enter at the beginning steps when you first flash a rom or go back to stock.

nijel8 said:
Hey Doom, it'll be extremely helpful if you could write a guide about using that test point... I read some russian and I still couldn't get how exactly you connect it to battery from that 4PDA guide!? Best start with how you open the phone.
It'll help a lot of people seeing so many bricked devices...
Thank you for all the useful info you bring here!
Click to expand...
Click to collapse
I added hardbrick recovery to my tutorial. , since one guy in my thread flashed rom for different device.
I am making some kind of a universal guide.
So I gonna add what is necessary.

Doom Slayer said:
I added hardbrick recovery to my tutorial. , since one guy in my thread flashed rom for different device.
I am making some kind of a universal guide.
So I gonna add what is necessary.
Click to expand...
Click to collapse
Thank you! Now I got how test point is used. I have another question in that matter but I'll leave it for the new thread. :good:

How to update unlocked and rooted stock rom?

Hello there.
My G5s+ is suggesting a security update. But since I did unlock the bootloader and rooted it with magisk I did not install it.
My question is: What is the best way to update the phone?
Just flash the new stock rom? And where do I get those?
Thanks in advance.

Nobody here that can tell me how to upgrade?
Should I just flash the new version if I get it somewhere?

Mr.Chainsaw said:
Nobody here that can tell me how to upgrade?
Should I just flash the new version if I get it somewhere?
Click to expand...
Click to collapse
Unlocked bootloader will not affect the OTA installation..!
The reason the OTA-Update fails is that one of the boot, system, logo or recovery partitions are changed.
Magisk modifies the boot image.
On rooted device..OTA may brick the device..so avoid OTA installation..!
Reply your current build Number from about phone..
Do a clean flash.

crazytech2 said:
On rooted device..OTA may brick the device..so avoid OTA installation..!
Click to expand...
Click to collapse
Thats why I did not do it yet. But I still want to do the update somehow.
crazytech2 said:
Reply your current build Number from about phone..
Click to expand...
Click to collapse
The Build No is
NPSS26.116-26-8

Mr.Chainsaw said:
Thats why I did not do it yet. But I still want to do the update somehow.
The Build No is
NPSS26.116-26-8
Click to expand...
Click to collapse
Flash 26-11 full firmware

Where can I find full firmware versions of the stock rom to flash?
My build version is: NPSS26.116-26-4
As I understand it, there are two new security patches since that version? If I'm flashing one of the newer versions, is it just a case of dirty flashing it normally through twrp? No need to factory reset?

Chemacky said:
Where can I find full firmware versions of the stock rom to flash?
My build version is: NPSS26.116-26-4
As I understand it, there are two new security patches since that version? If I'm flashing one of the newer versions, is it just a case of dirty flashing it normally through twrp? No need to factory reset?
Click to expand...
Click to collapse
If that is the firmware build you need, you could try the firmware here: https://firmware.center/firmware/Motorola/Moto G5s Plus/Stock/ but ensure you download the correct firmware. (credit to: https://forum.xda-developers.com/moto-g5s-plus/how-to/xt1804-able-to-lock-bootloader-npss26-t3722572) Also, verify it is the firmware you require and was the latest firmware build on your device - please don't downgrade with stock firmware (else you may hard brick with OTA updates corrupting your bootloader)...
Stock OTA updates, as mentioned above, require fully stock firmware - they will not flash with root, modifications or TWRP (and attempting to flash via TWRP may soft bootloop your device). Thus, you must re-flash the stock firmware - you may be able to save your data by omitting the 'fastboot erase userdata' command and you do not have to re-lock your bootloader. However, I'm not familiar with the G5S Plus and I hope another user can provide you with flashing commands.
I would still recommend you make a backup of your device in TWRP and keep that safe, in case you have to wipe your data for stability.

[Root][sm-n9600]Root no TWRP method[Sept 21]

This method really is only a workaround for root while TWRP is getting it's finishing touches
You need oem unlock to complete this root method.
Magisk modules aren't installing, but may be an easy environmental fix. But root is there.
This boot.img has been taken from TGY Hong Kong firmware. There is a big chance this won't work on any other firmware. If you want to risk it, then have a full Odin firmware ready to flash.
If you upload your stock boot.img to me, I will pre patch them also but the method is really quite simple to do yourself.
Magisk has the ability to patch a boot.img that is on your sdcard. So by installing the magisk manager apk, you can then patch the boot.img. Then all you have to do is package it into a .tar and flash it with Odin.
Download folder
https://mega.nz/#F!H19RQLRD!f9lCXblRXyfZ6b090eU73w
--->

Incredible! Thank so you much.
I have the same model and Hong Kong firmware. So am I to just download and odin flash the tar file?
Latest odin will do? Or is the modified version preferred?

How can you tell if you have Hong Kong firmware on your device

Mekael162 said:
How can you tell if you have Hong Kong firmware on your device
Click to expand...
Click to collapse
Look for TGY under software information/software provider SW ver

FYI I have just found modules don't install, but root is present at least.
[emoji450] --->

Root for N9600 running nicely for me here

Thanks for work!!.

Do you have to run that crom app to unlock the bootloader?

elevatorguy said:
Do you have to run that crom app to unlock the bootloader?
Click to expand...
Click to collapse
Nope just need oem unlocked.

TGY firmware patch boot image file failed
SM-N9600ZKDTGY
AP-N9600ZHU1ARH2
- Copying image to cache
- Device platform: arm64-v8a
- Existing zip found
- Extracting files
- Unpacking boot image
MagiskBoot v17.1(17100) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
! Sony ELF64 format detected
! Stock kernel cannot be patched, please use a custom kernel
! Installation failed
My English is pretty basic, please don't mind... :silly::silly::silly:

Hello everyone. Can you tell me if this model N9600 can use the stock FM Radio after Rooting? Thanks

chengddjack said:
SM-N9600ZKDTGY
AP-N9600ZHU1ARH2
- Copying image to cache
- Device platform: arm64-v8a
- Existing zip found
- Extracting files
- Unpacking boot image
MagiskBoot v17.1(17100) (by topjohnwu) - Boot Image Modification Tool
Parsing boot image: [/data/user_de/0/com.topjohnwu.magisk/install/boot.img]
! Sony ELF64 format detected
! Stock kernel cannot be patched, please use a custom kernel
! Installation failed
My English is pretty basic, please don't mind... :silly::silly::silly:
Click to expand...
Click to collapse
TGY is the img i rooted already. Just download that.
--->

jotade said:
Hello everyone. Can you tell me if this model N9600 can use the stock FM Radio after Rooting? Thanks
Click to expand...
Click to collapse
I have radio on the TGY firmware
--->

lawtq said:
Incredible! Thank so you much.
I have the same model and Hong Kong firmware. So am I to just download and odin flash the tar file?
Latest odin will do? Or is the modified version preferred?
Click to expand...
Click to collapse
Im pretty sure im using stock odin, and yes to just flash the file.
--->

Mentalmuso said:
I have radio on the TGY firmware
--->
Click to expand...
Click to collapse
Thanks Friend. Im buying this model because i want to root it and also i need FM Radio. Is everything working after root?

jotade said:
Thanks Friend. Im buying this model because i want to root it and also i need FM Radio. Is everything working after root?
Click to expand...
Click to collapse
So far I haven't noticed any issues except for Magisk root itself. Modules can't be installed, but I may figure a workaround for that if TWRP doesn't rectify a few things soon. It's probable TWRP will be fully functional soon though. It's all related to the kernel.
--->

TGY
Mentalmuso said:
TGY is the img i rooted already. Just download that.
--->
Click to expand...
Click to collapse
Thank you for everything you have done for me,
This is a great help, I will do a flash test later and pay back.
If you are free, can you explain the error there?
Very grateful!!!

Questions from a samsung-noob:
1. Will this method also trip knox?
2. Do I still need to factory reset after enabling oem unlock?

chengddjack said:
Thank you for everything you have done for me,
This is a great help, I will do a flash test later and pay back.
If you are free, can you explain the error there?
Very grateful!!!
Click to expand...
Click to collapse
I don't know where you got that kernel from to patch, but seeing that it says Sony in the error. I would imagine it is the seeing boot.img
[emoji450]--->

otaconremo said:
Questions from a samsung-noob:
1. Will this method also trip knox?
2. Do I still need to factory reset after enabling oem unlock?
Click to expand...
Click to collapse
Yes and yes.
Rooting will always trip Knox. Basically anything that mods away from stock will trip Knox. And there is no going back after. You will never be able to use Samsung pay or secure folder again after.
[emoji450]--->