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
Hey All,
Just bought a second hand s6 g920 and the back of the phone says g920F but the software on it says G920p. How can this even happen and how can i fix it?
i'd rather have g920F firmware as that is the international one and has more xda community support.
thanks in advance
Same problem... can anyone help?
Starhannes said:
Hey All,
Just bought a second hand s6 g920 and the back of the phone says g920F but the software on it says G920p. How can this even happen and how can i fix it?
i'd rather have g920F firmware as that is the international one and has more xda community support.
thanks in advance
Click to expand...
Click to collapse
DOWNLOAD FIRMWARE OF SM-G920F from sammobile.com and flash it thorugh odian. it is quite easy.
most likely the previous owner has damaged the phone and back glass was replaced.
Put phone in download mode anf check the model number (it cannot be changed ).. Its easy .. Just use a little your brain...
rajaumar77 said:
DOWNLOAD FIRMWARE OF SM-G920F from sammobile.com and flash it thorugh odian. it is quite easy.
Click to expand...
Click to collapse
No! Odin won't flash any non G920P firmware. Flash fails when i try to use SM-G920F
Starhannes said:
No! Odin won't flash any non G920P firmware. Flash fails when i try to use SM-G920F
Click to expand...
Click to collapse
when you start phone in download moder, look on top there will be written model no of your phone. check this is original model of you phone. may be you phone board has been changed.
well... flashed stock g920p firmware through odin, it boots quite fine but with changed imei (it shows s5 when i search imei online... network/data works fine)... g920f firmware flash fails.... also samsung s/n is 000000... restoring efs also doesnt help... flashed back to the software with which it came.. imei back to g920f... s/n still 00000... bootloader g920p... recovery g920p... kernel g920p... baseband g920f... build g920f... anyone???
Hello,
I have checked several threads and didnt find anything specific, so i am going to try and explain myself. I have a SM-G920I phone (galaxy s6), bought in America. I am living in Europe and I have unlocked the network with a code gotten from Samsung. The network and band works great and there is nothing wrong with it even tho the European g920f firmware and g920i have slightly different band/modem.
My friend has a g920f and I have checked in depth her phone and it is exactly the same as mine in everything.
So yes, I want to flash a g920f firmware on my g920i firmware. Please, don't mind why I do it, it is not relevant to my experiment.
I have flashed a modified kernel to my s6 (Droid 5.1.1) in order to root it and back my efs up. Once that is done, I know that if I brick my phone, I can bring it back as long as I have the efs. So okay, I flashed a g920f firmware (Mm) and it failed. I did some research and i guess that there is a file in the md5 which recognizes that my phone is not a g920f and rejects the updating. I have read about pit files and I have seen that all of them set different partition sizes, so I guess that may be another reason why I can't flash the 920f firmware -some file is larger than the current g920i partition-
My question is, if the g920f and g920i phone are TOTALLY equal in hardware, why does it fail? Please, don't give me a silly reason. I am expecting a technical reason.
Also, if I flash on my 920i a pit file according to the g920f firmware, will I be able to flash the F firmware later? If not, why?
Don't worry about band or modem. I will be happy if it gets flashed without any network. It is an experimental thing (i can always go back and flash a g920i firmware)
Thank you!
Hi. First thing's first- I've purchased a Samsung Galaxy J7 (2016) with model SM-J710FN (as written on the back of the phone) variant from France, and as expected, it would have a French (or German) firmware installed (I'm not sure about that). I want to change over to the Indian firmware and I've been trying for a very long time, but I can't get anything. I've done the basics, such as trying to flash the Indian firmware for the correct with ODIN, but every time, an error occurs, saying, "secure check fail" on ODIN. I've also learnt that there is also something as an SSP variant of the device. Can someone please enlighten me on that and give me a link to a proper Indian firmware I can use? Thanks, much appreciated!
Just a quick note: My phone IS still under warranty, I'm not interested in loosing that.
Info about the phone:
Android version: 6.0.1
Baseband version: J710FXXU3AQD2
Build Number: MMB29K.J710FXXS3AQD1
Sahil 1491 said:
Hi. First thing's first- I've purchased a Samsung Galaxy J7 (2016) with model SM-J710FN (as written on the back of the phone) variant from France, and as expected, it would have a French (or German) firmware installed (I'm not sure about that). I want to change over to the Indian firmware and I've been trying for a very long time, but I can't get anything. I've done the basics, such as trying to flash the Indian firmware for the correct with ODIN, but every time, an error occurs, saying, "secure check fail" on ODIN. I've also learnt that there is also something as an SSP variant of the device. Can someone please enlighten me on that and give me a link to a proper Indian firmware I can use? Thanks, much appreciated!
Just a quick note: My phone IS still under warranty, I'm not interested in loosing that.
Info about the phone:
Android version: 6.0.1
Baseband version: J710FXXU3AQD2
Build Number: MMB29K.J710FXXS3AQD1
Click to expand...
Click to collapse
send me an email and I will send link to download the stock firmware with 4 files. first try all 4 files with latest Odin. if that does not work then try AP and CSC only. XDA do not allow me to write link here because I am junior
Hi, guys! I bought a second-hand, unrooted Galaxy S7, model SM-G930S that shows the SK Telecom logo on boot, so it seems it is from South Korea. I want to replace its firmware for the Brazilian one (I suppose it's one of the G930F variants), but since it's my first Samsung phone, I don't know how to do it and if it's possible to do it, but I already know some of the necessary version stuff though:
SM-G930S
AP: G930SKSU1DQJ1
CP: G930SKSU1DQJ1
CSC: G930SSKC1DQJ1
Can someone tell me if it's possible to replace it and how can I do it? Will I need the ODIN tool people talks about a lot here? What else?
If this is your first Samsung device, then I do not recommend you start playing with firmware installs. Try to use it first as it is and then, if you do not like it, custom the firmware.
RossTeagan said:
If this is your first Samsung device, then I do not recommend you start playing with firmware installs. Try to use it first as it is and then, if you do not like it, custom the firmware.
Click to expand...
Click to collapse
I have been with it for two months already. I do not like the korean firmware, thanks.
And, no, I do not want a custom firmware/ROM, a just want to know if it is possible (and how) to flash the Brazilian or International Samsung firmware, like I said above.
giovanealex said:
I have been with it for two months already. I do not like the korean firmware, thanks.
And, no, I do not want a custom firmware/ROM, a just want to know if it is possible (and how) to flash the Brazilian or International Samsung firmware, like I said above.
Click to expand...
Click to collapse
You can't flash the wrong model firmware to your phone
Well u cant just simply flash one varient's firmware over the other though the hardware is almost same. But u can install stock based costum rom like super stock rom which is debloated and a simple stock based rom i am using it right now on my S7 edge. you will like it i am sure. otherwise no way.