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
First of all, sorry if this has been answered here, I simply can't find a definitive answer for our S6, let me explain better.
As you may know, I'm not a newbie here or in other forums, I've rooted most of my phones (Not this one) and have installed custom roms dozens of times to all of them, BUT, I'm definitely a newbie about what I need here, I'm trying to see if I can change my SM-G920i region from XSA (Australia) to any other one, India in this case. I have read tons of threads and posts and that's what is confusing me, in some threads there are people saying that they did it and is working great, in that same threads there are people saying that they did it but Knox got tripped, there are others that say that the device is soft bricked and others are saying that they have read somewhere that changing the CSC from it's original one may brake future Samsung pay.
So, this phone is paid by my office, they allow me to do what I want to it while I'm able to just put it back as it came from factory, so that means that I can root it if it doesn't trip Knox, that I can install anything while I can simply go back anytime they need me to, and obviously, Samsung pay works when it finally comes. With this in mind, can somebody answer me a couple of questions?
1-) I know it's possible to do it, but is it true that by doing this I'll have Samsung pay issues? I doubt that knox will be tripped if I do it with odin, but besides knox, is there any possibility that Samsung Pay will not work in certain regions (India in this case) and that's why some are saying that it will break it?
2-) If I download the firmware and flash it via Odin, I'm reading that it won't brick the phone is done via Odin, but in worst case scenario I assume that I can always go back to original one and it gets factory reset, am I right?
3-) If I flash it correctly as I expect an it doesn't brick, does this means that it will change PDA and CSC versions all together, that it will basically become a device from the new flashed region? So if I flash the India one to my XSA (Australia) now it will work completely as an India device and should get future OTA like the rest?
Again, sorry if this has been asked and answered but going back a lot of pages here can't give me definitive answer, thanks in advance for those of you kind enough to answer to this.
Flash a G920i ROM via odin other than your own region/country:
http://www.sammobile.com/firmwares/database/SM-G920I/
roydok said:
Flash a G920i ROM via odin other than your own region/country:
http://www.sammobile.com/firmwares/database/SM-G920I/
Click to expand...
Click to collapse
Thanks.
In another thread that I have posted (Brazilian one) I was replied to, so because of that I decided to do it, so far everything is working great as expected. Mine was an Australian baseband (XSA), only thing you I noticed is that when I connect it to Smart Switch app for PC or MAC it will still detects the Original CSC, I was curious about it and installed Phone info apk and it shows correctly the information, both PDA and CSC are now from India but it shows that the Original CSC was XSA (In my case), Firmware's CSC code is INU (India) and Active CSC code it says XSA/INU, so I'm assuming that it's showing multiple CSC.
Does somebody know if having the Active CSC showing XSA/INU causes future OTA issues?
After flashing a ROM its good practice to go to recovery mode and do a full wipe of cache and full reset to change CSC to the default of the ROM you flashed.
roydok said:
After flashing a ROM its good practice to go to recovery mode and do a full wipe of cache and full reset to change CSC to the default of the ROM you flashed.
Click to expand...
Click to collapse
Well, in that case I think I will pass for now, as I did a Full wipe cache and Full reset before the Flash but just did a Wipe cache after I flashed it.
The issue is that I basically just finish setting everything back as it was before (about 3 hours and I still haven't set my Contacts Ringtones and Accounts links) so begin again it's a PITA. Once I finish this I'll do a full nandroid backup to have everything as I want, but if I do the Wipe Data/Full Reset and then restore from the Full backup, does this put everything as it was including CSC again? I've been always confused about how deep this restore goes in the system files. Do you know about it?
Thanks.
Try restoring from your backup after the full wipe from recovery. If everything works then you should be ok. Otherwise start from scratch and reinstall everything one by one.
Will try that later today, thanks.
Goodluck.
roydok said:
Goodluck.
Click to expand...
Click to collapse
I tried that and nothing, still the same, then I decided to remove the Re-activation Lock in Find My Mobile settings, and after that and enter to recovery mode, it changed the CSC to India, so for those of you with same issues, remember about Re-activation lock.
Thanks for your help.
Did you have a SIM card inserted when you flashed your ROM with removed reactivation lock?
I had the SIM card on the phone today all the time as I forgot to bring with me the SIM removal tool and didn't have anything to open the Sim card tray, but last night I didn't have the Sim card installed when I flashed the ROM.
So today after I did the Wipe cache Partition and Data and saw that it still had the same issue, I flashed a UK ROM into a SM-G925f that had some African country ROM (have never heard of it before in my life but for the name it sounded like an African country), anyways I did that and everything went great, so that's when I thought what was different between the devices and then I remember that I had turned on the Reactivation lock in my S6 and not in the S6 Edge, so I turned it off, then went to Recovery mode and for my surprise the CSC was already changed without any other reset or anything.
erasat said:
I had the SIM card on the phone today all the time as I forgot to bring with me the SIM removal tool and didn't have anything to open the Sim card tray, but last night I didn't have the Sim card installed when I flashed the ROM.
So today after I did the Wipe cache Partition and Data and saw that it still had the same issue, I flashed a UK ROM into a SM-G925f that had some African country ROM (have never heard of it before in my life but for the name it sounded like an African country), anyways I did that and everything went great, so that's when I thought what was different between the devices and then I remember that I had turned on the Reactivation lock in my S6 and not in the S6 Edge, so I turned it off, then went to Recovery mode and for my surprise the CSC was already changed without any other reset or anything.
Click to expand...
Click to collapse
can you post a screen of CSC page of Phone ** info ** just for reference?
I see you said that CSC changed to India, but Active CSC or also Original CSC?
What I mean is that, now I have a S6 which has Original, Active CSC as MRU...I'd like to put a European fw on it since I'm based in Europe (got this Middle East / Africa phone just because Dual sim it's not available in europe) but I'm in doubt if putting an european fw will still show that CSC has changed from original one and maybe OTA updates won't work.
thanks
Changing csc!!!
I succesfully installed a G920I indian INU rom in my device which had a XSA rom but when i go to recovery it still shows as XSA ....How do i change that to INU?
Hi i am using a galaxy s6edge+ and i am really struggling with the region lock. I have tried a few options of the factory full reset changing the Apn's to the ones needed and using different sim cards.when it used to go into emergency mode "h+" now it won't connect to any internet at all. Can i possibly have any basic assistance with the rom and resetting options to change the csc when i do a hard reset the csc says it's 'multi'. what does that mean? Any region unlocking help would be appreciated so much!
Thanks guys
Hello
I have the official version of Android 5.1.1 SK region and would like to upload Officiální Android version 5.1.1 CZ region. Flash Odin FAIL. Please someone help? Thank you.
JABV90 said:
Hello
I have the official version of Android 5.1.1 SK region and would like to upload Officiální Android version 5.1.1 CZ region. Flash Odin FAIL. Please someone help? Thank you.
Click to expand...
Click to collapse
Had a similar issue yesterday when I tried to update my rooted 5.0.2 to an official 5.1.1. I have used ODIN many times before since SGS3, and back then you were able to mix your system image from other regions, but that apparantly has been locked down by Samsung. Now you can only update an official version of the rom if it exactly matches your existing region. Because you updated your SK international S6 and tried a region set rom from Czech it most likely failed towards the very end of flash with "FAIL".
Your options are: 1) you download the 5.1.1 version for your region in ODIN format from SAMMobile or 2) you use Smart Switch and let it do it for you - in this case you will need to know the SN of your phone as it is used for verification.
Samsung has locked down the serial number with the regions that come with it. So if you have to install, you should update it or use same region odin file. There is a way to break this chain if you are rooted and some additional files are being used in the odin but I am not completely sure as I have not tried it yet. But there are chances that you may void your warranty if you try that or the worse hard brick as it can sometimes change your serial number if not used properly. but I wouldn recommend that. I'll let you know once I understand the usage correctly.
Hello Guys, this forum is my last hope. I have a problem with my S7 (DBT Germany), I think after flashing an older stock rom and going back to newest, something happened that my phone doesn't detect any sim cards anymore. If I type *#06# , it only shows the SN Number, no IMEI. WIFI still works without problem, but I can not use my sim card anymore, so it's pretty useless now :crying:
The sim card works on another devices, so it's for sure a problem with my s7, I might have messed up something. What do you think is here the problem and how can I solve it? Any help is much appreciated, I really hope to fix this because my phone is only 2 weeks old.
I currently have the latest Firmware for DBT from updato, (December 14, 2017 for Android 7.0)
IMEI = unknown
SIM Card status: Not avaliable
Have you tried a stock ROM from sammobile.com? Updato and sammobile.com should have the same ROM but maybe there is a difference between the 2?
Did you confirm that the phone is running the latest modem?
audit13 said:
Have you tried a stock ROM from sammobile.com? Updato and sammobile.com should have the same ROM but maybe there is a difference between the 2?
Did you confirm that the phone is running the latest modem?
Click to expand...
Click to collapse
I did not try sammobile because updato and sammobile were the same firmware. Sammobile does have a newer firmware from 28/01 but it says I need to join in order to download.
Is there a way I can fix a damaged/corrupted EFS ? My phone is pretty useless now without sim card detection
Sorry, I know of no way to fix imei issue if a combination of Odin and a stock ROM does not work. You may have to take it to a cell repair shop that can force flash the ROM and EFS using hardware like an octopus box: https://octopusbox.com/eng/features/models
audit13 said:
Sorry, I know of no way to fix imei issue if a combination of Odin and a stock ROM does not work. You may have to take it to a cell repair shop that can force flash the ROM and EFS using hardware like an octopus box: https://octopusbox.com/eng/features/models
Click to expand...
Click to collapse
Hey, flashing a Stock Rom with Odin + Root works for me with no problem, how can I flash my EFS? I do know my S/N and IMEI number..
Do you have an EFS backup? If yes, this may help: https://forum.xda-developers.com/showpost.php?p=72355071&postcount=3
audit13 said:
Do you have an EFS backup? If yes, this may help: https://forum.xda-developers.com/showpost.php?p=72355071&postcount=3
Click to expand...
Click to collapse
I don't have an EFS backup. Any chance without a backup? I do know my S/N and IMEI...
You would need a way to recreate the contents of the folder. Unfortunately, I'm not sure how to create the contents.
Maybe this will help: https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
audit13 said:
You would need a way to recreate the contents of the folder. Unfortunately, I'm not sure how to create the contents.
Maybe this will help: https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-fix-check-drk-imei-issues-t3379516
Click to expand...
Click to collapse
Hey, I have finally found the solution and my sim card is working again :victory:
It really was just that the firmware was 1 version older.. I downloaded the latest DBT Firmware from samsung-updates (Build Date: 15/01/2018)
Put Bootloader to BL , AP to AP , CP to CP , CSC (not Home_CSC!) to CSC , flashed it and finally my IMEI etc. is back.
Thank you for taking your time trying to help me
Congratulations on your success
Hi all,
Yesterday I bought an S10e under the impression that it is sm-g970F.
Trying to flash Android 11 I discovered that it is actually sm-g970N.
Is there really a difference between them?
Should I be worried that some functions will be missing/unavailable?
Also, in the settings, it appears as g970F. How did the seller change it??
I have the same problem i tried to update the phone to the latest sm-g970f rom (figured if it's already installed it's possible)
And non of the roms flashed only when i decided to try latest sm-g970n rom it flashed however i bricked the phone and i have no idea what to do now.
almogkm said:
Hi all,
Yesterday I bought an S10e under the impression that it is sm-g970F.
Trying to flash Android 11 I discovered that it is actually sm-g970N.
Is there really a difference between them?
Should I be worried that some functions will be missing/unavailable?
Also, in the settings, it appears as g970F. How did the seller change it??
Click to expand...
Click to collapse
So after digging into the issue since i have the same problem here are my conclusions:
1. The phone is a Korean Variant G970N it is probably a renewed phone and not a new one.
apparently it's okay for an importer to take used phones (from Korea in this case) and replace all the cosmetics but of cause leaving the used MB.
Now here is what you should worry about, in order to flash the G970F Fixed Rom (there is no way you have updates) they used a Custom Kernel which means the phone was rooted and now Knox is tripped (this not reversible).
(Download Phone Info from play store and check knox if it shows 0x1 then your phone warrenty is void and some features won't be available any more for example - Samsung Pay).
So what should you do?
Well if you still have the option i would have demanded my money back!!
One thing that i am perplexed about is how in hell is this legal?!!!
If you no longer have this option or you want to keep the phone you have two option:
1. Flashing Korean Unbranded Firmware (KOO) which is pretty good it doesn't have bloatware or issues as far as i can tell, i only found one down side for it, the phone language selection is small but if you only need English (like any normal Human) then you are golden.
2. Keep the G970F ROM but bare in mind it will receive no updates and no security patches.
I am still looking for a proper way to flash G970F Firmware over G970N for now i haven't found any internet source that will confirm it's even possible.
So how did those importers\sellers did it, they probably flashed it with a Cellphone Lab Software (not Odin solution) and used a custom Kernel to fool Knox, like i said before this is practically a crime and i don't understand how can they sell used phones as new and get away with it!!!!
I had the same suspicions....
I'll try going to the lab that sold the previous owner the device and deal with them tho it looks like I just got scammed...
Sorry to bring this up again but I've just had an idea following JerryRigEverything's video:
What if I transplant SM-G970F components from a broken device that no longer works or in use in my SM-G970N which is supposedly new.
My N device is now bricked for some reason I couldn't solve, though my suspicion is that it has to do with incompatibility with the SIM card I use.
When my device did work, it worked great! ...besides battery issues that are most likely a result of the incompatibility aforementioned.
Will this work? If so, what components do I need? I already know I'll need the logic board but as seen in the video, there are several more antennas, should I just copy what Jerry did?
Vegetto32 said:
I have the same problem i tried to update the phone to the latest sm-g970f rom (figured if it's already installed it's possible)
And non of the roms flashed only when i decided to try latest sm-g970n rom it flashed however i bricked the phone and i have no idea what to do now.
Click to expand...
Click to collapse
Hi Vegetto,
I am from India and buy a galaxy S10e from UAE, It is showing G970F in the Phone's about but the problem is It is a G960N. Now, When I see in Sam Phone Info app there is Bootloader version - G970N, PDA Version - G970F, CSC G970F.
It is also a Knox tripped phone. Knox 0/1.
But if I see in Samsung code by typing in keypad *#12580*369#
it showing like all option in Odin:
BL: G970F
AP: G970F
CP: G970F
CSC: G970F
Does this means I can flash new Firmware on the list of SAM Mobile website, with G970F series firmware, It also showing in SAM Phone Info App that there latest firmware G970FXXSEFUL1/G970FOXMEFUJ2/G970FXXSEFUJ2.
I am in India right now.
Please help me, My email Id is -- [email protected]
It actually means you cannot flash SM-G970F the only roms you can flash are G970N.
Also if you want the phone to get security updates you must flash the original phones bootloader version, my suggestion download the G970N KOO firmware it's a global firmware. As for the knox it is tripped and there is nothing you can do about it.
Vegetto32 said:
It actually means you cannot flash SM-G970F the only roms you can flash are G970N.
Also if you want the phone to get security updates you must flash the original phones bootloader version, my suggestion download the G970N KOO firmware it's a global firmware. As for the knox it is tripped and there is nothing you can do about it.
Click to expand...
Click to collapse
How can I flash the original phone's bootloader version?
Where from I can download the original phone's G970N KOO Firmware and is it official Samsung Firmware?
How are they able to flash G970F? Is it custom Rom or do they use the original one?
I searched that my phone is using G970FXXS4BTB3 firmware which Vietnam XXV and same number found at https://www.sammobile.com/samsung/galaxy-s10e/firmware/SM-G970F/XXV/download/G970FXXS4BTB3/322678/ in an old update in 2020.
So see the attached screenshot, can I flash its latest version with odin. Of course, there is a chinese written in recovery mode installed when I go to its recovery mode for flashing with Odin.
I have a similar problem right now on my Korean S10E. Device is SM-G970N. I need it to be in Turkish. Only Themes item in Settings is in Turkish- very interesting- The rest is in English. App names are mostly Turkish Settings app name is in English.
The bootloader is unlocked but the phone is not rooted, Knox seems not tampered.
Could not start OTA update at first, I have upgraded a few versions from PC via Smartswitch. Just then noticed OTA also started downloading. The rest of the updates went on from the phone until upgrading to 12, there was a message like "All of the updates were not succesful." OTA update no longer responded. This time I turned back to Smart Switch. Update finished this time and finally I am at the latest version.
I only need Turkish in Settings. I used some ADB commands and an app called MoreLocale2. It did not work either. This has to be simple. Turkish exists. Keyboard is Turkish but not Settings. Quick links and most other things are strangely mixed English and Turkish.
How can I enable full Turkish?