Related
Hi all,
I am generally not a XDA active reply user. I worked on a lot of Android fixing project. And here is one of mine result.
Please read the whole thread before working on it.
I know everyone is frustrating in upgrading to 4.4.2 but brick during odin process (ext4 fail) and stuck in 4.4.2 bootloader.
PS: This method is currently work on HK note3, but i think this method would work on all note3, Please try this will your own risk, I would not be responsible to all trouble according to this method. Varied N9005 would require different N9005 4.3 Firmware, I personally use HK Firmware because Mine is 16gb Note 3.
Here is the method to solve this problem:
Before working on it, we have to prepare the following things:
1. Odin 3.07 (Yes, 3.09 does not work)
2. HK firmware odin pack (Pit, BL (DO NOT WORK WITH IT, AP, CP, CSC) (Sorry for it is a Chinese link)
OR Workable N9005 4.3 firmware
3. 4.4.2 leaked firmware
4. 4.4.2 rom (I used sweet rom v.7 to fix it)
5. 4.4.2 recovery cwm @Chenglu
5. Samsung driver (bullshxt)
Now lets get started:
1. Flash the 4.4.2 firmware BL by odin.
2. Flash the HK Firmware AP, CP &CSC (Do not use the HK firmware BL)
3. once it done, turn to Download mode again and flash 4.4.2 recovery cwm by odin
4. Run Recovery
5. Wipe everything
6. Flash 4.4.2 rom ( I flashed sweet rom v7 currently)
7. Boot to system and do all the setting ( The sound and the signal are not working)
8. Boot back to download mode
9. Boot the 4.4.2 leaked firmware's CP ( DO NOT WIPE AFTERWARD)
10. Prepare coffee and cookies
11. Enjoy your device!
karnavont said:
Hi all,
...
Click to expand...
Click to collapse
Please edit your title to reflect that (at least at this point) your fix should be considered primarily for the Hong Kong Note 3 bricked by writing XEO 4.4.2.
xclub_101 said:
Please edit your title to reflect that (at least at this point) your fix should be considered primarily for the Hong Kong Note 3 bricked by writing XEO 4.4.2.
Click to expand...
Click to collapse
Actually not, its to all varied Note3 but I do not have all sources given to it, it is generally working on all Note3 who fail in flashing to 4.4.2(to any error in progress during Odin upgrading)
And I did a lot of researches, This problem is not only reflect to HK Note 3 only, there are a lot of people would upgrading to 4.4.2 and stuck in Download mode with UDC start (Not able to downgrade).
karnavont said:
Actually not, its to all varied Note3 but I do not have all sources given to it, it is generally working on all Note3 who fail in flashing to 4.4.2(to any error in progress during Odin upgrading)
And I did a lot of researches, This problem is not only reflect to HK Note 3 only, there are a lot of people would upgrading to 4.4.2 and stuck in Download mode with UDC start (Not able to downgrade).
Click to expand...
Click to collapse
Well, if/when people will post in this thread reporting that the method (which is highly similar to methods that were already posted by other users, most notably Volrath and rinuvimal - which you have not credited anywhere) - then we will know that the method is applicable, and to which specific models!
In other words people using the method on untested models should be warned that they are just doing something that might have never been tested on their model.
xclub_101 said:
Well, if/when people will post in this thread reporting that the method (which is highly similar to methods that were already posted by other users, most notably Volrath and rinuvimal - which you have not credited anywhere) - then we will know that the method is applicable, and to which specific models!
In other words people using the method on untested models should be warned that they are just doing something that might have never been tested on their model.
Click to expand...
Click to collapse
Okay, i changed it, in term of a reference instead
Hi guys, I had the same issue with the 16GB Honk Kong version, and this is how I have finally resolved, trying the methods you suggested and others, and finally got it back to life this way (I'm posting in case this might be useful for any of you as well)
1.- Flash bootloader from N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX (Leaked Kit Kat version)
2.- After reboot, flash bootloader, CP and CSC from the same version (N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX). Flashing bootloader again might not be necessary, but this is how I did it, and how it worked, so I cannot confirm otherwise
3.- Flash AP from N9005ZHUBMI7 (Honk Kong version)
4.- Enter recovery mode and wiped system, cache and dalvik (just in case)
4.- Flash autoroot (n9005-cwm-recovery-6.0.4.6-kitkat(0113).tar)
5.- Flash CWM recovery for KitKat (n9005-cwm-recovery-6.0.4.6-kitkat(0113).tar)
6.- Installed the latest version of SweetRom (SweetROM_V7.00_NA6_4.4.2_N9005.zip) from this thread: http://forum.xda-developers.com/show....php?t=2487425
So long it seems to be working correctly, battery consumption has increased, but this seems normal every time I change my ROM. Thanks again for all your help, and hopefully this will help someone else resolve the issue until the official version for the HK 16GB version is available.
My friend wants to ask this question because he is unable to post a reply with a photos attached.
Is my N9005 32gb Baseband/Bootloader from Hong Kong also?
Kindly see my ScreenShots beloe please. I just don't know where my Note 3 came from.
Thanks in Advance & God Bless
AldrichDSaints said:
My friend wants to ask this question because he is unable to post a reply with a photos attached.
Is my N9005 32gb Baseband/Bootloader from Hong Kong also?
Kindly see my ScreenShots beloe please. I just don't know where my Note 3 came from.
Thanks in Advance & God Bless
Click to expand...
Click to collapse
I think you are using a Custom Rom so there is a posibility it won't be accurate kabayan. But according to your bootloader and baseband its the same as my Hongkong version. And my advice hide your IMEI nexttime.
maumarti2k said:
Hi guys, I had the same issue with the 16GB Honk Kong version, and this is how I have finally resolved, trying the methods you suggested and others, and finally got it back to life this way (I'm posting in case this might be useful for any of you as well)
1.- Flash bootloader from N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX (Leaked Kit Kat version)
2.- After reboot, flash bootloader, CP and CSC from the same version (N9005XXUENA6_N9005OXXENA5_N9005XXUENA2_OXX). Flashing bootloader again might not be necessary, but this is how I did it, and how it worked, so I cannot confirm otherwise
3.- Flash AP from N9005ZHUBMI7 (Honk Kong version)
4.- Enter recovery mode and wiped system, cache and dalvik (just in case)
4.- Flash autoroot (n9005-cwm-recovery-6.0.4.6-kitkat(0113).tar)
5.- Flash CWM recovery for KitKat (n9005-cwm-recovery-6.0.4.6-kitkat(0113).tar)
6.- Installed the latest version of SweetRom (SweetROM_V7.00_NA6_4.4.2_N9005.zip) from this thread: http://forum.xda-developers.com/show....php?t=2487425
So long it seems to be working correctly, battery consumption has increased, but this seems normal every time I change my ROM. Thanks again for all your help, and hopefully this will help someone else resolve the issue until the official version for the HK 16GB version is available.
Click to expand...
Click to collapse
What version of Odin did you used? For the past 24 hours is it stable and any FC's? Are all apps working? I wanna try your guide. Having problem on the O.P. guides.
I am in the exact same situation, all over methods have failed, im going to try this!
3. 4.4.2 leaked firmware is a dead link!
AldrichDSaints said:
My friend wants to ask this question because he is unable to post a reply with a photos attached.
Is my N9005 32gb Baseband/Bootloader from Hong Kong also?
Kindly see my ScreenShots beloe please. I just don't know where my Note 3 came from.
Thanks in Advance & God Bless
Click to expand...
Click to collapse
Fist dude you should never post your IEM EVERRRR
Second you can always hook the phone to Kies and it will tell you what you have
jetbruceli said:
Fist dude you should never post your IEM EVERRRR
Second you can always hook the phone to Kies and it will tell you what you have
Click to expand...
Click to collapse
Seems I have had some success. Although, I found a couple of the instructions difficult to understand. Thanks for posting this, as I no longer have a brick.
Cheers.
filchi756 said:
I think you are using a Custom Rom so there is a posibility it won't be accurate kabayan. But according to your bootloader and baseband its the same as my Hongkong version. And my advice hide your IMEI nexttime.
Click to expand...
Click to collapse
My friend didn't continue to flash the Poland's leak. He will just wait for the OTA on his phone because he is afraid to have a softbrick and I told him also that if he had softbrick his phone the only thing that he can use now is by flashing custom ROM
Samsung Note 3 Region Taiwan Softbrick UDC START
AldrichDSaints said:
My friend didn't continue to flash the Poland's leak. He will just wait for the OTA on his phone because he is afraid to have a softbrick and I told him also that if he had softbrick his phone the only thing that he can use now is by flashing custom ROM
Click to expand...
Click to collapse
does anyone with Samsung Note 3 Taiwan Region?
i got this "UDC START" thing while upgrade to 4.4.2 Region Poland Official ROM
but i dont want to trip knox, better i got back to shop and claim for warranty..
or should i just wait for Official Kit Kat Region Taiwan?
i am still waiting..
if anyone can help, thank you very much.
Samsung Note 3 Region Taiwan Softbrick UDC START
karnavont said:
Actually not, its to all varied Note3 but I do not have all sources given to it, it is generally working on all Note3 who fail in flashing to 4.4.2(to any error in progress during Odin upgrading)
And I did a lot of researches, This problem is not only reflect to HK Note 3 only, there are a lot of people would upgrading to 4.4.2 and stuck in Download mode with UDC start (Not able to downgrade).
Click to expand...
Click to collapse
does anyone with Samsung Note 3 Taiwan Region?
i got this "UDC START" thing while upgrade to 4.4.2 Region Poland Official ROM
but i dont want to trip knox, better i got back to shop and claim for warranty..
or should i just wait for Official Kit Kat Region Taiwan?
i am still waiting..
if anyone can help, thank you very much.
budi_west said:
does anyone with Samsung Note 3 Taiwan Region?
i got this "UDC START" thing while upgrade to 4.4.2 Region Poland Official ROM
but i dont want to trip knox, better i got back to shop and claim for warranty..
or should i just wait for Official Kit Kat Region Taiwan?
i am still waiting..
if anyone can help, thank you very much.
Click to expand...
Click to collapse
i also have the same problem. what should i do
Samsung note 3 Region Taiwan UDC START
sagsans said:
i also have the same problem. what should i do
Click to expand...
Click to collapse
Where do you come from?
i will try the solution given by members from Hongkong Region with flashing CWM recovery and SweetROM, but i just do not know will it work for Taiwan Region, cause Hongkong Firmware is ZHU and Taiwan is ZTU something unique there..
budi_west said:
Where do you come from?
i will try the solution given by members from Hongkong Region with flashing CWM recovery and SweetROM, but i just do not know will it work for Taiwan Region, cause Hongkong Firmware is ZHU and Taiwan is ZTU something unique there..
Click to expand...
Click to collapse
i have try sweetrom, it's not working on my note3 taiwan version. anything for me to try?
Samsung Note 3 Taiwan UDC START
sagsans said:
i have try sweetrom, it's not working on my note3 taiwan version. anything for me to try?
Click to expand...
Click to collapse
How do you flash the SweetROM what version? have you try locky guide?
Technology: The Ultimate Guide To Unbrick 16 Gb International Samsung Galaxy Note 3
http://forum.xda-developers.com/showthread.php?t=2627291
by: Locky Loki
Try this something else out
[ROM]N9005ZHUENB1 Android 4.4.2 Kitkat
http://forum.xda-developers.com/showthread.php?t=2636699
Or
[SOLUTION] Successful flash of leaked NA6 ROM on Hong Kong 32g N9005
http://forum.xda-developers.com/showthread.php?t=2613374
Actually i have started a question [Q] about Note 3 Taiwan UDC START at this forum but with no reply
[Q] Samsung Galaxy Note 3 SM-N9005 Region Taiwan Softbrick UDC START
http://forum.xda-developers.com/showthread.php?p=50061661
Lately i found out somebody posting That he is from Region taiwan anda he is able to flash firmware from region Hongkong and Taiwan Only..
So, i suppose Taiwan Region can seek help from Hongkong Region
Hi guys,
My phone is originally from Colombia. Since I was anxious to get on Lollipop I ended up flashing my phone with the B137 UPDATE_CUST.app, which now only allows me to flash the European firmware. I would like to get back to the Colombian version, but I'm unable to figure out, how? I have tried flashing a vendor.img with hw/nla, but it failed with Command not allowed. I took a look at the files that are included in the B137 UPDATE_CUST, in the hopes that I could create one for B120, which is the version I am currently on, but I have absolutely no idea how to go about it. I would really appreciate any advice and help I can get.
Thanks!
IDK how region works but I mine's from the Philippines and the version was B120SP04. I kept on upgrading and downgrading to and from B324 because of bugs.
I used B125SP02 from Romania and Italy, B120SP04 South East Asia, and will be using the B326 South Africa.
Flash B324 and flash B300 Transition Pack. After successful flashing of B300, flash B120.
Hope this answers your question.
markchong89 said:
IDK how region works but I mine's from the Philippines and the version was B120SP04. I kept on upgrading and downgrading to and from B324 because of bugs.
I used B125SP02 from Romania and Italy, B120SP04 South East Asia, and will be using the B326 South Africa.
Flash B324 and flash B300 Transition Pack. After successful flashing of B300, flash B120.
Hope this answers your question.
Click to expand...
Click to collapse
You can find out what region yours is for by dialing *#*#2846579#*#* go to ProjectMenu, then Networking, then vendor and country info. Mine use to say hw/nla, which stands for North Latin America, but now it says hw/eu for Europe. This happened after flashing the B137 UPDATE_CUST.app, what I want now is to get it back to North Latin America, so that I can flash the B327 from Colombia.
Bonnie1977 said:
Hi guys,
My phone is originally from Colombia. Since I was anxious to get on Lollipop I ended up flashing my phone with the B137 UPDATE_CUST.app, which now only allows me to flash the European firmware. I would like to get back to the Colombian version, but I'm unable to figure out, how? I have tried flashing a vendor.img with hw/nla, but it failed with Command not allowed. I took a look at the files that are included in the B137 UPDATE_CUST, in the hopes that I could create one for B120, which is the version I am currently on, but I have absolutely no idea how to go about it. I would really appreciate any advice and help I can get.
Thanks!
Click to expand...
Click to collapse
es file manager is great in device /system and /build prop ..
where did you get the update_cust.app file from?
No need to change anthing, mine is also nla version, i've already upgrade to B522. I am on B511 first(tried several times cannot upgrade.to B522), then I downgrade to B324, and then use B522 full package upgrade directly.
---------- Post added at 04:20 AM ---------- Previous post was at 04:15 AM ----------
B324 you can download from here
http://forum.xda-developers.com/mate-7/general/huawei-mt7-l09-l10-stock-firmware-ota-t3275784
when I change the region change the LTE bands too? Because my mate 7 don't have LTE Band 20[emoji22]
Gesendet von meinem HUAWEI NXT-L29 mit Tapatalk
changing region
This works perfectly for me:
ministryofsolutions [dot] com/2016/09/guidehow-to-change-region-of-mate7-mate8.html
xstu25 said:
This works perfectly for me:
ministryofsolutions [dot] com/2016/09/guidehow-to-change-region-of-mate7-mate8.html
Click to expand...
Click to collapse
Yes, it's work perfect :
http://ministryofsolutions.com/2016/09/guidehow-to-change-region-of-mate7-mate8.html
I saw that android 6.0 was avaible for G920F and i have a G920I,since they have the same hardware i was wondering if it is possible to install the G920F firmware on a G920I
victor1342 said:
I saw that android 6.0 was avaible for G920F and i have a G920I,since they have the same hardware i was wondering if it is possible to install the G920F firmware on a G920I
Click to expand...
Click to collapse
Pertty sure u cant cuz the bootloader and modem are unique to ur device and without a 6.0.1 bootloader for your device it will just bootloop
xstokerx said:
Pertty sure u cant cuz the bootloader and modem are unique to ur device and without a 6.0.1 bootloader for your device it will just bootloop
Click to expand...
Click to collapse
But can't i install the G920F 6.0.1 bootloader in the G920I?
victor1342 said:
But can't i install the G920F 6.0.1 bootloader in the G920I?
Click to expand...
Click to collapse
I know you can't wait to try marshmallow on the i variant. The marshmallow bootloader and modem are meant for F variant. Best wait for unifed S6 rom or official I variant marshmallow.
Loving 14nm Exynos
defybest said:
I know you can't wait to try marshmallow on the i variant. The marshmallow bootloader and modem are meant for F variant. Best wait for unifed S6 rom or official I variant marshmallow.
Loving 14nm Exynos
Click to expand...
Click to collapse
Ok,thx for the help
well i did the opposit, instaled the 920f on my 920i and it works perfectly
tntgdh said:
well i did the opposit, instaled the 920f on my 920i and it works perfectly
Click to expand...
Click to collapse
You installed G920F firmware on G920i and it worked? Which android version ?
Yeah. And I'm using it right now. 5.1.1
The latest one from mexico
tntgdh said:
Yeah. And I'm using it right now. 5.1.1
The latest one from mexico
Click to expand...
Click to collapse
Can you try 920F VOD firmware and confirm if it is working?
I also have 920I and cant wait to get my hands on MM
Dude I was about to install it but gave up when I realized that would have to use a pit file. I don't want to end up with a locked bootloader if any problem happens
tntgdh said:
Dude I was about to install it but gave up when I realized that would have to use a pit file. I don't want to end up with a locked bootloader if any problem happens
Click to expand...
Click to collapse
Can you try XEF (France) Firmware ? I think it is de-branded!
victor1342 said:
I saw that android 6.0 was avaible for G920F and i have a G920I,since they have the same hardware i was wondering if it is possible to install the G920F firmware on a G920I
Click to expand...
Click to collapse
things should happen if you flash incorrect ROM
1 BOOTLOOPS
2 your phone can go down anytime this is if flash pass
3 loosing imei
4 giving you errors during flashing stock
4 KNOX bye bye
5 a nice piece of junk between your hands to smile at it and you know you are screwed because this junk loose signal every Minute
6 every time you see your phone its Like someone saying to you ( hello retard )
and this is my story
am done with samsung moving to moto or nexus or sony
tntgdh said:
Dude I was about to install it but gave up when I realized that would have to use a pit file. I don't want to end up with a locked bootloader if any problem happens
Click to expand...
Click to collapse
are you on 920F VOD? or locked to any carrier?
if not locked, you can flash the unlocked versions of MM 920F, as I dont think you need pit files as some guys have flashed 920F MM over 920F 5.1.1 without pit.
Tried several times with ODIN. Fails everytime. Lost my phone data as well while trying when I formatted everything without a backup. I am a Certified retard!
Ok so myself and also some other people on the Australia post have tried to flash the G920F MM firmware (VOD or XEF) on a G920i and it has never worked - coming from a Custom 5.1.1 Rom or an official 5.1.1.
Odin simply refused to flash the firmware so you actually don't lose any data and don't damage your phone.
massacreur75010 said:
Ok so myself and also some other people on the Australia post have tried to flash the G920F MM firmware (VOD or XEF) on a G920i and it has never worked - coming from a Custom 5.1.1 Rom or an official 5.1.1.
Odin simply refused to flash the firmware so you actually don't lose any data and don't damage your phone.
Click to expand...
Click to collapse
Hi
Have your firends and you tried to convert your G920i 5.1.1 to a G920f 5.1.1 first, before trying to update to MM?
I ask because one user up in the thread said that he had successfully flash a Mexico G920f 5.1.1 firmaware to his G920i 5.1.1 phone.... but he did not flash with MM, because he was scared of flashing a pit file...
Thanks!
G920I
I have a Galaxy S6 , G920I model for the other models, or at least for the G920F , the marshmallow was released, how do you have the new update in my G920i ? Who can help me thank you.
I have got an unlocked Galaxy S7 (G930F) and have flashed the android nougat update (BTU - UK - 7.0). It is working fine.
Since I have updated to nougat, there are some updates released (bug fixes, I can confirm this on sammobile site) but are not available when I check for the updates in settings.
Any idea on what this issue might be.
If you have either root or custom recovery you can't receive OTAs but you can update using SmartSwitch on your PC
kamranali44 said:
I have got an unlocked Galaxy S7 (G930F) and have flashed the android nougat update (BTU - UK - 7.0). It is working fine.
Since I have updated to nougat, there are some updates released (bug fixes, I can confirm this on sammobile site) but are not available when I check for the updates in settings.
Any idea on what this issue might be.
Click to expand...
Click to collapse
hi mate
Updates ( if you are not rooted) are CSC carrier dependent , if your carrier or CSC do not issue any updates ...you will not have them.
When you checked in sammobile you checked if your carrier / CSC had updates?
No updates on Smart switch
userName'dYa said:
If you have either root or custom recovery you can't receive OTAs but you can update using SmartSwitch on your PC
Click to expand...
Click to collapse
I do not have root or custom recovery. I have downloaded the firmware from sammobile and checked that the knox warranty is not tripped over and the device status is still official.
MAX 404 said:
hi mate
Updates ( if you are not rooted) are CSC carrier dependent , if your carrier or CSC do not issue any updates ...you will not have them.
When you checked in sammobile you checked if your carrier / CSC had updates?
Click to expand...
Click to collapse
The BTU firmwares in the UK are not network dependent as far as I know and they come installed in unlocked devices with no network bloatware.
I do remember flashing the CSC (G930FOXA1DPLT - that's the current one) which came with the BTU firmware. The new CSC has updates (G930FOXA1DQB1).
Am I missing something or is the device still dependent on a network to approve this.
Do you get any error?
userName'dYa said:
Do you get any error?
Click to expand...
Click to collapse
No, it says "the latest updates have already been installed "
I even had this issue on Android 6 so I downloaded the Android 7 and flashed it via odin. Now there are updates but I would like to get the OTA to update it.
kamranali44 said:
No, it says "the latest updates have already been installed "
I even had this issue on Android 6 so I downloaded the Android 7 and flashed it via odin. Now there are updates but I would like to get the OTA to update it.
Click to expand...
Click to collapse
Are these bug fixes for the country AND the carrier you are using
userName'dYa said:
Are these bug fixes for the country AND the carrier you are using
Click to expand...
Click to collapse
Yes the bug fixes are for this country (UK).
I am not sure if they are carrier dependent as it is an unlocked software (I am on O2 and there is a different firmware for O2 locked devices).
Are they still carrier dependent is the phone is unlocked?
kamranali44 said:
Yes the bug fixes are for this country (UK).
I am not sure if they are carrier dependent as it is an unlocked software (I am on O2 and there is a different firmware for O2 locked devices).
Are they still carrier dependent is the phone is unlocked?
Click to expand...
Click to collapse
Yes the carrier matters even for unlocked phones
userName'dYa said:
Yes the carrier matters even for unlocked phones
Click to expand...
Click to collapse
Okay, in this case I think I will have to wait for O2 to approve them.
I thought the idea of having an unlocked phone from samsung is to use any sim and get updates directly from Samsung when they release it.
kamranali44 said:
The BTU firmwares in the UK are not network dependent as far as I know and they come installed in unlocked devices with no network bloatware.
I do remember flashing the CSC (G930FOXA1DPLT - that's the current one) which came with the BTU firmware. The new CSC has updates (G930FOXA1DQB1).
Am I missing something or is the device still dependent on a network to approve this.
Click to expand...
Click to collapse
Hi
You get updates either by the carrier or by the CSC , in your case you have an unbranded firmware , BTU, so no carrier updates...you will get an update only when an update for BTU unbranded firmware is release it , independently if there are other firmwares newer than yours around....only way to keep updated to the latests is flashing it yourself any new release , check this thread if you deciede to go that way
Try to get your CSC code by installing Phone Info from the market : I too have flashed the first official Nougat BTU UK 7.0 firmware with Odin, with a complete reset of the phone, but in my case I still have CSC = ITV and not BTU.
This seems to prevent us from getting the new OTA update : somewhere I've read that after the Odin procedure I should have entered recovery and factory reset the phone from there to get the CSV changed to BTU as the installed firmware is a "multi-csc" variant.
We still can download today's new firmware from SamMobile and use home_csc to avoid resetting again the phone.
Hope someone more expert than me can confirm/correct my statements
Inviato dal mio SM-G930F utilizzando Tapatalk
I was wondering the same and SergioA is right. I still have the DBT CSC although I was flashing the BTU Firmware. Thanks for clarification
userName'dYa said:
Yes the carrier matters even for unlocked phones
Click to expand...
Click to collapse
So my S7(Sprint) running on G930U firmware will go back to Sprint Nougat firmware full of bloatware?
MAX 404 said:
Hi
You get updates either by the carrier or by the CSC , in your case you have an unbranded firmware , BTU, so no carrier updates...you will get an update only when an update for BTU unbranded firmware is release it , independently if there are other firmwares newer than yours around....only way to keep updated to the latests is flashing it yourself any new release , check this thread if you deciede to go that way
Click to expand...
Click to collapse
The BTU has a firmware update available on sammobile but not it's not OTA update on my phone.
What if I download the new update and flash it via odin with HOME_CSC file added. Will it start the updates by carrrier?
SergioA said:
Try to get your CSC code by installing Phone Info from the market : I too have flashed the first official Nougat BTU UK 7.0 firmware with Odin, with a complete reset of the phone, but in my case I still have CSC = ITV and not BTU.
This seems to prevent us from getting the new OTA update : somewhere I've read that after the Odin procedure I should have entered recovery and factory reset the phone from there to get the CSV changed to BTU as the installed firmware is a "multi-csc" variant.
We still can download today's new firmware from SamMobile and use home_csc to avoid resetting again the phone.
Hope someone more expert than me can confirm/correct my statements
Inviato dal mio SM-G930F utilizzando Tapatalk
Click to expand...
Click to collapse
My S7 DUOS FD and my wife's S7 F both recieved the Nougat OTA update DQB1 today, mine was originally CSC XSG (UAE) and mi wife's was CSC TTT (Trinidad And Tobago), and both were updated to CSC BTU Nougat Final release, changing the CSC to BTU (this will wipe out your memory in the process but for a newer OS version it is recommended). I had doubts about getting any OTA updates since my S7 is the FD version which does not exists as a BTU phone originally, but in the end I got the update.
Long story short, if you want to recieve OTA updates after sideloading firmware with ODIN with a different CSC, you should fully convert to that new CSC, otherwise you won't get the OTA's.
kamranali44 said:
The BTU has a firmware update available on sammobile but not it's not OTA update on my phone.
What if I download the new update and flash it via odin with HOME_CSC file added. Will it start the updates by carrrier?
Click to expand...
Click to collapse
Hi
if you have a DPLT firmware you should get it soon.....unless your system by some reason is not set as original ( even if knox is tripped but your system is set as original you will get it) anyhow is faster if you download it yourself and flash it , use home_csc so you will not factory reset your phone , NOTE: has to be the same home_csc that you have in your phone right now , not any home_csc for example:
Lets say you want to flash the latest firmware and it happens to be from France and you do not want to loose any of your apps , config or data
1 find out what CSC is installed in your phone ( phoneinfo app is great for that) in your case BTU
2 download the latest possible firmware for your CSC and extract from it the home_csc file , save it , discard the rest
3 download the latest firmware available , in our example France , extract from it download the MAIN-file and extract AP BL & CP save it , discard the other 2 files ( home_csc and CSC from France firmware
4 now take AP BL & CP from the latest firmware ( in our example France) and take the home_csc from a BTU firmware ( why , because is the CSC installed in your phone) and flash the together
In that way you can always have the latest in your phone without waiting for it , phone will not be knox tripped , will be 100%official as is all official firmware
If your using the btu version for UK phones, then how did you manage not to brick your phone? The UK phones do not have snapdragon, they have the Samsung chips.
MAX 404 said:
Hi
if you have a DPLT firmware you should get it soon.....unless your system by some reason is not set as original ( even if knox is tripped but your system is set as original you will get it) anyhow is faster if you download it yourself and flash it , use home_csc so you will not factory reset your phone , NOTE: has to be the same home_csc that you have in your phone right now , not any home_csc for example:
Lets say you want to flash the latest firmware and it happens to be from France and you do not want to loose any of your apps , config or data
1 find out what CSC is installed in your phone ( phoneinfo app is great for that) in your case BTU
2 download the latest possible firmware for your CSC and extract from it the home_csc file , save it , discard the rest
3 download the latest firmware available , in our example France , extract from it download the MAIN-file and extract AP BL & CP save it , discard the other 2 files ( home_csc and CSC from France firmware
4 now take AP BL & CP from the latest firmware ( in our example France) and take the home_csc from a BTU firmware ( why , because is the CSC installed in your phone) and flash the together
In that way you can always have the latest in your phone without waiting for it , phone will not be knox tripped , will be 100%official as is all official firmware
Click to expand...
Click to collapse
Thank you, you are a hero :good:. I did update via odin and installed it without losing any data.
As I have said I have previously (about a week ago) used the CSC file rather than HOME_CSC.
I have the Phone Info app, The Orignal CSC code is blank(is it normal?), Does this look normal as I have not checked the CSC before updating to android nougat. I have added a screenshot of it.
Greeting, folks. Yesterday a got a brand new Mate 9 with a carrier in Colombia (South America). SInce I did some research I found that my current version (MHA-L09C25B16) is a custom ROM (I don't really know if the version is for the country or the carrier). I was wondering some things.
1. I searched on the web and used FF but could not find a ROM compatible with my current version
2. I'd like to know if there is some chance of updating without having to unlock the bootloader and install a ROM by flashing the device.
3. I need some guide on how to change my software to an European version so I can have the latest updates always.
Thanks in advance.
Sojiroska said:
Greeting, folks. Yesterday a got a brand new Mate 9 with a carrier in Colombia (South America). SInce I did some research I found that my current version (MHA-L09C25B16) is a custom ROM (I don't really know if the version is for the country or the carrier). I was wondering some things.
1. I searched on the web and used FF but could not find a ROM compatible with my current version
2. I'd like to know if there is some chance of updating without having to unlock the bootloader and install a ROM by flashing the device.
3. I need some guide on how to change my software to an European version so I can have the latest updates always.
Thanks in advance.
Click to expand...
Click to collapse
Hmmm.
1. I found only MHA-L09C25B106 OTA in FF. It is old version.
2. No chance. In case of rebranding you have to unlock bootloader, cause need change oeminfo.
3. There is guide but there is one problem also.
You have MHA-L09 that is one-sim model.
Oeminfo mha-l09c432 is not original, it was created from dual-sim model. Even if you're rebranded to this you will get gui elements of second sim.
Guide to rebrand: https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
Additional problem is that you can't back to C25 region. MHA-L09C25B106 is OTA rom, not Full-ota. It can't be installed over other regions.
P.s. it would be better to sell this model and get dual-sim L29 model. Even if you're not using second sim, you are able to use sdcard in second slot.
Well...I went a little deeper in my "search" and found something (I think).
Officially there's no C25 Software model... It´s a Custom ROM for the carrier Claro (CUST C25D005). A custom, I SUPPOSE, was created from C605 Official Software (which happens to be, Official Colombia Model...Other Mate 9 sold unlocked in Colombia are MHA-L09C605).
So...my guess is... Even if the version is the C25 custom...could I install a C605 ROM?
And...in case I could do it...how would I do it?
Thanks a lot 5[Strogino]
Sojiroska said:
Well...I went a little deeper in my "search" and found something (I think).
Officially there's no C25 Software model... It´s a Custom ROM for the carrier Claro (CUST C25D005). A custom, I SUPPOSE, was created from C605 Official Software (which happens to be, Official Colombia Model...Other Mate 9 sold unlocked in Colombia are MHA-L09C605).
So...my guess is... Even if the version is the C25 custom...could I install a C605 ROM?
And...in case I could do it...how would I do it?
Thanks a lot 5[Strogino]
Click to expand...
Click to collapse
I never faced with this customization and never read that anyone did it.
There are some ROMs for L09C605, so you can go to this region, but imho you need L09C605 oeminfo.
Huawei uses localization model of ROMs. When flashing phone looks like generic model (M300). Then script finds metadata in oeminfo to generate product and vendor partitions. If metadata is not match, you will get wrong info in "About phone".
Maybe I can be wrong and in your case there is simple process of inherited region. But who knows? As I said, there is no way to return to stock state.
5[Strogino] said:
I never faced with this customization and never read that anyone did it.
There are some ROMs for L09C605, so you can go to this region, but imho you need L09C605 oeminfo.
Huawei uses localization model of ROMs. When flashing phone looks like generic model (M300). Then script finds metadata in oeminfo to generate product and vendor partitions. If metadata is not match, you will get wrong info in "About phone".
Maybe I can be wrong and in your case there is simple process of inherited region. But who knows? As I said, there is no way to return to stock state.
Click to expand...
Click to collapse
Well then. Whenever the OREO update is released for the C605 region I would definitely do it. Would you please indicate me how to change the OEM info file? And how do I update when I have the .zip file? Do not know much about these processes.
I was wondering too... Why some updates contain three zip files?
Sojiroska said:
Well then. Whenever the OREO update is released for the C605 region I would definitely do it. Would you please indicate me how to change the OEM info file? And how do I update when I have the .zip file? Do not know much about these processes.
Click to expand...
Click to collapse
Main thread to rebrand is https://forum.xda-developers.com/mate-9/how-to/guide-mate-9-flash-update-package-t3593108
To change oeminfo, you can place L09C605 oeminfo into directory for oeminfos
Or you can change bin file in TWRP backup and restore it.
Sojiroska said:
I was wondering too... Why some updates contain three zip files?
Click to expand...
Click to collapse
1. Update.app is general solid file of ROM
2. Public.zip - additional apps
3. Hw/<region> - apps and customizations for specific region.