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
OK, no matter what method I try I am unable to achieve a successful flash of my phone. I have tried it via odin with many different firmware versions but all seem to fail almost immediately. The only way to resolve this is to use samsung switch and reset phone to stock. The problem is stock firmware is german vodafone full of vodafone bloatware, I want to get rid of it and flash a UK unbranded firmware but no matter what I do I am unable to achieve this. I can see from the forum that there are many people out there with the same flashing problem but with no real responses on how to achieve the goal. There must be people out there that have achieved this task but don't seem to be offering up much help?
ok
sinbrad said:
OK, no matter what method I try I am unable to achieve a successful flash of my phone. I have tried it via odin with many different firmware versions but all seem to fail almost immediately. The only way to resolve this is to use samsung switch and reset phone to stock. The problem is stock firmware is german vodafone full of vodafone bloatware, I want to get rid of it and flash a UK unbranded firmware but no matter what I do I am unable to achieve this. I can see from the forum that there are many people out there with the same flashing problem but with no real responses on how to achieve the goal. There must be people out there that have achieved this task but don't seem to be offering up much help?
Click to expand...
Click to collapse
Is your phone international unlocked out of the box? I dont believe it was, because as far as I've read international unlocked phones come with "unbranded" firmware. The unlocked ones I know can be pretty much flashed with "any" international firmware, which is what you are trying to do.
If you dont know for sure. Odin the stock German Vodaphone. Let the phone boot. Boot back to stock recovery, then factory reset and clear cache.
Then let the phone boot...Download phone info app by vndnguyen (free version is fine)...Open the app, go to CSC Code tab. Then that will tell you the active CSC code and your firmware CSC code...you are looking for the line that says Available CSC Codes. If it only lists German Vodaphone (VD2), then I believe you are stuck til the phone is unlocked.
Anyone, jump in here if I'm mistaken. I am using this as reference as, I've checked my G920F. Mine is unlocked tho and I can flash any firmware from any region with no problem. Hopefully I've answered your question.
I had no luck with the firmwares on the firmware page either.
If you are on OI9 check http://forum.xda-developers.com/galaxy-s6/general/guide-android-6-0-marshmallow-beta-how-t3277533
And try flashing the first stock firmware https://drive.google.com/folderview...sharing&tid=0B40ItdHKfkyQd1hJQXVDU3dDU2c#list (not the android M one!) via ODIN.
Basic process is:
Download the above file, extract, there should be 4 files inside (AP,BL,CP,CSC), simply select each one to go in the relevant box on ODIN, then go into download mode on your phone and click start...
N.B. Be aware that the above firmware contains a PIT file which will reformat and resize the partitions on your phone, so make sure you have a copy of the stock firmware that works before trying the flash (i.e. the one which Smart Switch downloads). You can grab it from your windows %TEMP% directory during the smart switch download (it first downloads a file to TMPxxx, then extracts it into a directory of the same name, its these files you want. They should be the four files beginning with the type of ODIN file you are flashing (AP,BL,CP,CSC). The files get deleted after the firmware has flashed so make sure you watch the process. If things go wrong you can re-flash these files via ODIN
As far as I was led to believe and when I purchased the phone it did state factory unlocked. I was able to put in any sim when I received it and didn't have to go through any aftermarket unlock process?
I have the same problem i have a unlocked G-920F with egyptian CSC and firmware 5.1.1 .when i try to flash BTU 5.1.1 via odin, i have the same problem and only way to recover is via smart switch.BTU firmware is from sammobile
abdussamad said:
I have the same problem i have a unlocked G-920F with egyptian CSC and firmware 5.1.1 .when i try to flash BTU 5.1.1 via odin, i have the same problem and only way to recover is via smart switch.BTU firmware is from sammobile
Click to expand...
Click to collapse
So, seems this is not uncommon?
ok the way to do it is download this file
https://drive.google.com/folderview...sharing&tid=0B40ItdHKfkyQd1hJQXVDU3dDU2c#list
its BTU firmware of 5.1.1
and flash this firmware you'll have 4 files AP,BL,CP,CSC,put it in the respective boxes in odin.I have tested this right now and it works
Press "thanks" if i have helped
Well downloaded the app for CSC info and it states available CSC codes are...
ATL, AVF, CNX, CYV, MOB, MTL, OMN, SIM, SWC, TCL, VD2, VDC, VDF, VDH, VDI, VGR, VIP & VOD
Any ideas?
Ok, tried to get stock firmware when samsung smart switch was downloading and installing but couldn't see where the firmware was being downloaded to? Tried windows temp etc but nothing appeared during download and install?
sinbrad said:
Ok, tried to get stock firmware when samsung smart switch was downloading and installing but couldn't see where the firmware was being downloaded to? Tried windows temp etc but nothing appeared during download and install?
Click to expand...
Click to collapse
Just type in %TEMP% into you windows explorer address bar and it will take you there. arrange by date modified and you will see the size ticking up during the download, before the flash starts it will extract into a folder with the same name, the md5 files can be grabbed from there
No probs here
abdussamad said:
I have the same problem i have a unlocked G-920F with egyptian CSC and firmware 5.1.1 .when i try to flash BTU 5.1.1 via odin, i have the same problem and only way to recover is via smart switch.BTU firmware is from sammobile
Click to expand...
Click to collapse
I flashed BTU firmware on my 920F international unlocked that came with UAE firmware without any problems. Idk
sd_N said:
I flashed BTU firmware on my 920F international unlocked that came with UAE firmware without any problems. Idk
Click to expand...
Click to collapse
Which file and which method?
aaronjp said:
Just type in %TEMP% into you windows explorer address bar and it will take you there. arrange by date modified and you will see the size ticking up during the download, before the flash starts it will extract into a folder with the same name, the md5 files can be grabbed from there
Click to expand...
Click to collapse
Ok, Got it this time, all four files. Will give the method above a go and if it fails at least I've got the stock firmware to fall back on?
Magic, have had great success. Now on the BTU firmware and everything is up and running. Got the stock as well just in case but if this continues to work won't be reinstalling stock. So a big thanks to those who helped
sinbrad said:
Magic, have had great success. Now on the BTU firmware and everything is up and running. Got the stock as well just in case but if this continues to work won't be reinstalling stock. So a big thanks to those who helped
Click to expand...
Click to collapse
Glad you are sorted
For all of you out there who happened to get stuck on 955u firmware containing bootloader 2 installed on the 955u1, there is hope!
I have successfully gotten back to 955u1 firmware and running stock OREO. (and have service again for those who are on non-mainstream carriers {Verizon, Sprint, T-Mobile, AT&T})
You will need (links to be added soon) (My Carrier in BL says XAA and these linked are the XAA firmwares):
USB 2.0 PORT
PRINCECOMSEY ODIN 3.12... link
regular ODIN 3.13.1 (what i used) link
G955U1UES2AQL1_G955U1OYM2AQL1 Firmware link
G955U1UEU2CRB9_G955U1OYM2CRB9 Firmware link
Official Samsung Cable that came with phone (preferably)
Windows OS
A Galaxy S8+ 955u1 Phone (only tried with this)
For some reason flashing just the CRB9 firmware would not work, I had to use the AQL1 and then to the CRB9
Instructions:
1. Extract both firmware files/zips (Put in 2 seperate folders so no mixups)
2. Reboot your phone to download mode (Power off then -- Power + Bixby + Volume Down at same time)
3. Open up princecomsey ODIN and then connect your phone to USB 2.0 Port
4. Add in the AQL1 Files - (BL, AP, CP, CSC) -- (I personally first did the AP, CP, and CSC then had it reboot then i restarted and flashed the BL by itself then rebooted) and press start. (I unchecked everything but reboot and f.reset time)
5. Unplug and Wait for it to turn on to the setup screen, then finish the setup (to verify that it runs and the model number is showing the correct #). If you open up settings it will be all jumbled up and weird, but dont worry. If you dont have service yet - dont worry.
6. Now after the phone is all setup (or if you decided to skip), unplug and power off the phone then boot into download mode again.
7. Now open up Regular odin and reconnect the phone
8. Now put in the CRB9 files (BL, AP, CP, CSC) (I put all in this time and i used the Home_CSC this time but you can use csc normal but no guarantee that would work with getting service again as i didnt try it) and press start and wait til it finishes and reboots (same goes here reboot, f stop time. but also check nand erase all -- to fix storage issue)
9. ENJOY!!!
NewDev4IOS said:
For all of you out there who happened to get stuck on 955u firmware containing bootloader 2 installed on the 955u1, there is hope!
I have successfully gotten back to 955u1 firmware and running stock OREO. (and have service again for those who are on non-mainstream carriers {Verizon, Sprint, T-Mobile, AT&T})
You will need (links to be added soon) (My Carrier in BL says XAA and these linked are the XAA firmwares):
USB 2.0 PORT
PRINCECOMSEY ODIN 3.12... link
regular ODIN 3.13.1 (what i used) link
G955U1UES2AQL1_G955U1OYM2AQL1 Firmware (link in an hour or 2)
G955U1UEU2CRB9_G955U1OYM2CRB9 Firmware (link in an hour or 2)
Official Samsung Cable that came with phone (preferably)
Windows OS
A Galaxy S8+ 955u1 Phone (only tried with this)
For some reason flashing just the CRB9 firmware would not work, I had to use the AQL1 and then to the CRB9
Instructions:
1. Extract both firmware files/zips (Put in 2 seperate folders so no mixups)
2. Reboot your phone to download mode (Power off then -- Power + Bixby + Volume Down at same time)
3. Open up princecomsey ODIN and then connect your phone to USB 2.0 Port
4. Add in the AQL1 Files - (BL, AP, CP, CSC) -- (I personally first did the AP, CP, and CSC then had it reboot then i restarted and flashed the BL by itself then rebooted) and press start. (I unchecked everything but reboot and f.reset time)
5. Unplug and Wait for it to turn on to the setup screen, then finish the setup. If you open up settings it will be all jumbled up and weird, but dont worry. If you dont have service yet - dont worry.
6. Now after the phone is all setup (or if you decided to skip), unplug and power off the phone then boot into download mode again.
7. Now open up Regular odin and reconnect the phone
8. Now put in the CRB9 files (BL, AP, CP, CSC) (I put all in this time and i used the Home_CSC this time but you can use csc normal but no guarantee that would work with getting service again as i didnt try it) and press start and wait til it finishes and reboots
9. ENJOY!!!
Click to expand...
Click to collapse
Did you volte work again after you went back to stock u1 firmware. Also is the a quicker way to download AQL1 because sammobile is a joke thanks
Sent from my [device_name] using XDA-Developers Legacy app
bonebeatz1234 said:
Did you volte work again after you went back to stock u1 firmware. Also is the a quicker way to download AQL1 because sammobile is a joke thanks
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Im going to be uploading the firmware and yes the VoLTE is working.
Also When flashing the CRB9 after the ALQ1 -- A repartition or nand erase all should be done as when i looked at my storage last night it was only 16GB but since im back to u1 firmware it shouldnt be hard to fix for me. i will edit with main post after i do it to my phone to ensure which one works.
uploaded
bonebeatz1234 said:
Did you volte work again after you went back to stock u1 firmware. Also is the a quicker way to download AQL1 because sammobile is a joke thanks
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
files are uploaded now -- finally (took a few tries)
NewDev4IOS said:
For all of you out there who happened to get stuck on 955u firmware containing bootloader 2 installed on the 955u1, there is hope!
I have successfully gotten back to 955u1 firmware and running stock OREO. (and have service again for those who are on non-mainstream carriers {Verizon, Sprint, T-Mobile, AT&T})
You will need (links to be added soon) (My Carrier in BL says XAA and these linked are the XAA firmwares):
USB 2.0 PORT
PRINCECOMSEY ODIN 3.12... link
regular ODIN 3.13.1 (what i used) link
G955U1UES2AQL1_G955U1OYM2AQL1 Firmware link
G955U1UEU2CRB9_G955U1OYM2CRB9 Firmware link
Official Samsung Cable that came with phone (preferably)
Windows OS
A Galaxy S8+ 955u1 Phone (only tried with this)
For some reason flashing just the CRB9 firmware would not work, I had to use the AQL1 and then to the CRB9
Instructions:
1. Extract both firmware files/zips (Put in 2 seperate folders so no mixups)
2. Reboot your phone to download mode (Power off then -- Power + Bixby + Volume Down at same time)
3. Open up princecomsey ODIN and then connect your phone to USB 2.0 Port
4. Add in the AQL1 Files - (BL, AP, CP, CSC) -- (I personally first did the AP, CP, and CSC then had it reboot then i restarted and flashed the BL by itself then rebooted) and press start. (I unchecked everything but reboot and f.reset time)
5. Unplug and Wait for it to turn on to the setup screen, then finish the setup (to verify that it runs and the model number is showing the correct #). If you open up settings it will be all jumbled up and weird, but dont worry. If you dont have service yet - dont worry.
6. Now after the phone is all setup (or if you decided to skip), unplug and power off the phone then boot into download mode again.
7. Now open up Regular odin and reconnect the phone
8. Now put in the CRB9 files (BL, AP, CP, CSC) (I put all in this time and i used the Home_CSC this time but you can use csc normal but no guarantee that would work with getting service again as i didnt try it) and press start and wait til it finishes and reboots (same goes here reboot, f stop time. but also check nand erase all -- to fix storage issue)
9. ENJOY!!!
Click to expand...
Click to collapse
Thank you so much! it worked coming from the g955u on verizon.
Was on Verizon 955U CRC5. Did the AQL1 and didn't have any jumbled or weird settings and storage is fine. Regular Odin failed trying to do CRB9. Downloaded the Software Update/OTA CRB9 update and all is good. On build R16NW.G955U1UEU2CRB9 with March 1 Security patch.
Sorry for bugging, newb here. Will this work on my Sprint Galaxy S8 Plus smg955usqs2bql1? And if so if you could spare a few and and help me. I believe I need this right to get root on my device?
sacking76 said:
Sorry for bugging, newb here. Will this work on my Sprint Galaxy S8 Plus smg955usqs2bql1? And if so if you could spare a few and and help me. I believe I need this right to get root on my device?
Click to expand...
Click to collapse
What if you flashed the sm-g955u1 version on to a sprint sm-g955u phone? would there be any way to power that back on, asking for a friend I believe thats what he done. Now his phone will not turn on.
kingjay2013 said:
What if you flashed the sm-g955u1 version on to a sprint sm-g955u phone? would there be any way to power that back on, asking for a friend I believe thats what he done. Now his phone will not turn on.
Click to expand...
Click to collapse
Honestly I do not know all I have is a 955u1 and am unable to test for other models as I don’t have any others, and now since bootloader version 3 is out for the 955u1 it is the end of carrier switching unless there is a workaround found in the near future.
This should still work as long as you keep the device on the same bootloader v2 and not Flash any v3 bootloader Firmware as that will definitely brick the device from what I’ve heard of v3 bootloaders
Sorry for any late replies been really busy lately
kingjay2013 said:
What if you flashed the sm-g955u1 version on to a sprint sm-g955u phone? would there be any way to power that back on, asking for a friend I believe thats what he done. Now his phone will not turn on.
Click to expand...
Click to collapse
Honestly I do not know all I have is a 955u1 and am unable to test for other models as I don’t have any others, and now since bootloader version 3 is out for the 955u1 it is the end of carrier switching unless there is a workaround found in the near future.
This should still work as long as you keep the device on the same bootloader v2 and not Flash any v3 bootloader Firmware as that will definitely brick the device from what I’ve heard of v3 bootloaders
I’m guessing your friend must have flashed firmware running bootloader v3 on it
(To tell what BL ver. The firmware contains look at the 5th character from the end and it is should be a number like xxx1xxxx or xxx2xxxx etc...) and if it was a 3 then that would be why as that firmware will brick the phone if it’s flashed on a different model (until there is a workaround)
Sorry for any late replies been really busy lately
sacking76 said:
Sorry for bugging, newb here. Will this work on my Sprint Galaxy S8 Plus smg955usqs2bql1? And if so if you could spare a few and and help me. I believe I need this right to get root on my device?
Click to expand...
Click to collapse
I haven’t seen any root for 955u/1 models for Oreo yet the only root I’ve seen on the s8 running Oreo is the carrier versions and the international models
NewDev4IOS said:
Honestly I do not know all I have is a 955u1 and am unable to test for other models as I don’t have any others, and now since bootloader version 3 is out for the 955u1 it is the end of carrier switching unless there is a workaround found in the near future.
This should still work as long as you keep the device on the same bootloader v2 and not Flash any v3 bootloader Firmware as that will definitely brick the device from what I’ve heard of v3 bootloaders
I’m guessing your friend must have flashed firmware running bootloader v3 on it
(To tell what BL ver. The firmware contains look at the 5th character from the end and it is should be a number like xxx1xxxx or xxx2xxxx etc...) and if it was a 3 then that would be why as that firmware will brick the phone if it’s flashed on a different model (until there is a workaround)
Sorry for any late replies been really busy lately
Click to expand...
Click to collapse
I greatly appreciate your response, is it any possible way to fix it? right now it won't power up, not even in bootload mode, nor recovery.
Hello guys,
so some months ago my aunt approached me asking me to "repair" her phone which didn't boot anymore after she installled an OTA update.
Now she is been greeted by the Samsung Logo and the message "Custom binary locked by frp lock" and that in an ongoing loop.
What I tried:
> flashing several stock roms (Android 6, Android 7 oldest version and newest versions)
> flashing roms from other countries in EU (UK, Austria, CH)
> flashing with ODIN and KIES (Kies didn't really work tho)
but all of it didn't work.
I fear that I might didn't check if "Re-Partition" was checked in Odion because after several tries and downloading thos Stock Roms with 20 Kb/s I was kinda frustrated when it didn't work..
currently the phone is still boot-looping with the same message as before.
It doesn't matter if I loose every data, as my aunt has a new phone by now!
If the phone has be re-partitioned by Odin is there anyway to fix it or better what are the signs for a Re-Partition?
Thank you in advance!
Paachan said:
Hello guys,
so some months ago my aunt approached me asking me to "repair" her phone which didn't boot anymore after she installled an OTA update.
Now she is been greeted by the Samsung Logo and the message "Custom binary locked by frp lock" and that in an ongoing loop.
What I tried:
> flashing several stock roms (Android 6, Android 7 oldest version and newest versions)
> flashing roms from other countries in EU (UK, Austria, CH)
> flashing with ODIN and KIES (Kies didn't really work tho)
but all of it didn't work.
I fear that I might didn't check if "Re-Partition" was checked in Odion because after several tries and downloading thos Stock Roms with 20 Kb/s I was kinda frustrated when it didn't work..
currently the phone is still boot-looping with the same message as before.
It doesn't matter if I loose every data, as my aunt has a new phone by now!
If the phone has be re-partitioned by Odin is there anyway to fix it or better what are the signs for a Re-Partition?
Thank you in advance!
Click to expand...
Click to collapse
I am a noob in this, but logicaly reasoning i would say you bricked it bad by flashing away with all kind of csc and firmware down and upgrades.
Your aunt will not be happy.
Jopponius said:
I am a noob in this, but logicaly reasoning i would say you bricked it bad by flashing away with all kind of csc and firmware down and upgrades.
Your aunt will not be happy.
Click to expand...
Click to collapse
Well this reply isn't really that helpful...
1st she doesn't care anymore because as mentioned she already has a new phone and said I can just keep it or throw it away.
2nd even if it's bricked there are ways to get it back to working, I soft bricked my old HTC M8 once and restored it.
3rd If you're a noob with this just don't reply, I've never had experience with Samsung phones before thats why I'm seeking for help, if it comes to HTC or LG phones I usually get things done myself. Not in this case tho.
Jopponius said:
I am a noob in this, but logicaly reasoning i would say you bricked it bad by flashing away with all kind of csc and firmware down and upgrades.
Your aunt will not be happy.
Click to expand...
Click to collapse
No, as was already stated, it bricked with an OTA, flashing different stock ROMs & CSCs would not brick it
---
Try using Samsung SmartSwitch emergency firmware recovery, I think you'll need the phones serial number (Box / back of phone)
Other than that, using ODIN 3.12.3 or newer with the correct stock ROM & CSC the phone originally came with (newest available release), using CSC and not HOME_CSC to force a reset after the flash should work, then you'll need her google account login to get past the FRP lock
*Detection* said:
No, as was already stated, it bricked with an OTA, flashing different stock ROMs & CSCs would not brick it
---
Try using Samsung SmartSwitch emergency firmware recovery, I think you'll need the phones serial number (Box / back of phone)
Other than that, using ODIN 3.12.3 or newer with the correct stock ROM & CSC the phone originally came with (newest available release), using CSC and not HOME_CSC to force a reset after the flash should work, then you'll need her google account login to get past the FRP lock
Click to expand...
Click to collapse
These kind of replies is what I need, thank you! Sadly when trying to use Smart Switch it instructs me to use some kind of "Backup Code" from another PC, I know for a fact my aunt doesn't do any backups and she doesn't even have a proper privat PC. I have a the original packaging IME and such at my hands!
You said flashing with Odin after a flash should work, but should I first use the "HOME_CSC" to flash and then the normal "CSC" to reset it afterwards?
The CSC file is a carrier customization file.: https://forum.xda-developers.com/s7-edge/help/csc-home-csc-simple-t3464835
audit13 said:
The CSC file is a carrier customization file.: https://forum.xda-developers.com/s7-edge/help/csc-home-csc-simple-t3464835
Click to expand...
Click to collapse
so in this case with the DBT version it's just the default customization file from Samsung, am I right?
Flashing either Home_CSC or CSC didn't had any effect on the S7 tho, it's still stuck in Boot loop with FRP Lock.
Let's say the phone is soft bricked, is there any way to get it back working, so I can flash the stock firmware afterwards`?
Paachan said:
These kind of replies is what I need, thank you! Sadly when trying to use Smart Switch it instructs me to use some kind of "Backup Code" from another PC, I know for a fact my aunt doesn't do any backups and she doesn't even have a proper privat PC. I have a the original packaging IME and such at my hands!
You said flashing with Odin after a flash should work, but should I first use the "HOME_CSC" to flash and then the normal "CSC" to reset it afterwards?
Click to expand...
Click to collapse
SmartSwitch Windows version shouldn't ask for any backup codes, only maybe the phone serial number
And no, just forget about HOME_CSC, use CSC instead, this will initiate a factory reset after the flash
AP
BL
CP
CSC
Add all 4 parts to ODIN, put the phone in Download Mode (Volume Down & Home & Power) connect to PC USB and hit start on ODIN (3.12.3 or newer)
It "Should" flash the firmware and factory reset, and so long as there is no hardware fault, it should boot into Android and ask for the Google Login that was connected to the phone before it bricked, once you enter that it will allow the rest of the setup to continue and finally to homescreen
It is possible that there is a hardware fault that caused the OTA to brick in the first place, or that the phone is not what it claims to be (Check in download mode which model it says it is, some are faked to look like International G930F when they are actually Snapdragon US models and require different firmware
If it is G930F, then flashing the latest DBT should work fine so long as it is not hardware related
*Detection* said:
SmartSwitch Windows version shouldn't ask for any backup codes, only maybe the phone serial number
And no, just forget about HOME_CSC, use CSC instead, this will initiate a factory reset after the flash
AP
BL
CP
CSC
Add all 4 parts to ODIN, put the phone in Download Mode (Volume Down & Home & Power) connect to PC USB and hit start on ODIN (3.12.3 or newer)
It "Should" flash the firmware and factory reset, and so long as there is no hardware fault, it should boot into Android and ask for the Google Login that was connected to the phone before it bricked, once you enter that it will allow the rest of the setup to continue and finally to homescreen
It is possible that there is a hardware fault that caused the OTA to brick in the first place, or that the phone is not what it claims to be (Check in download mode which model it says it is, some are faked to look like International G930F when they are actually Snapdragon US models and require different firmware
If it is G930F, then flashing the latest DBT should work fine so long as it is not hardware related
Click to expand...
Click to collapse
That actually helps me a ton, the Product name is fine it says it's a SM-930F so non US, I guess?
After flashing it with the newest available Stock Android 6 firmware (on which it was shipped originally) doesn't lead to anything it's still stucked in boot loop.
I guess it's a hardware fault then and not recoverable in the first place, thank you very much for your help!
I'm gonna try one last time with an older Version of Odin, maybe this leads to something!
Have a great day
I recommend flashing the same firmware onto the phone. Trying to flash an older bootloader may cause the flash process to stop as downgrading the bootloader is usually not permitted.
Do you know if oem unlock was enabled in the ROM settings? I'm not 100% but this may contribute to the issues with factory resetting and getting the phone to work.
Partitioning is not usually required if the computer is able to read he phone's partition table information. If a re-partition is required, you need to use the correct pit file for the phone when flashing a stock ROM in Odin.
audit13 said:
I recommend flashing the same firmware onto the phone. Trying to flash an older bootloader may cause the flash process to stop as downgrading the bootloader is usually not permitted.
Do you know if oem unlock was enabled in the ROM settings? I'm not 100% but this may contribute to the issues with factory resetting and getting the phone to work.
Partitioning is not usually required if the computer is able to read he phone's partition table information. If a re-partition is required, you need to use the correct pit file for the phone when flashing a stock ROM in Odin.
Click to expand...
Click to collapse
the OEM unlock setting was on default, so off I guess? It was just a regular OTA update and then the phone was stuck in a boot loop.
As *Detection* said it's probably is a hardware related issue I just now noticed that the status LED doesn't even light up if you charge the device (maybe this is an idicator)
I would've gladly used it as a backup device but I think it's just an expensive paperweight by now.
Still thank you for your help, appreciate it!
Sounds like you have tried all you can on your own. Maybe take it to a cell repair shop and have them try to force flash the phone using hardware such as an octopusbox?
Paachan said:
That actually helps me a ton, the Product name is fine it says it's a SM-930F so non US, I guess?
After flashing it with the newest available Stock Android 6 firmware (on which it was shipped originally) doesn't lead to anything it's still stucked in boot loop.
I guess it's a hardware fault then and not recoverable in the first place, thank you very much for your help!
I'm gonna try one last time with an older Version of Odin, maybe this leads to something!
Have a great day
Click to expand...
Click to collapse
Yep G930F is International Exynos so you should be good
Some people have problems downgrading from 7.0 to 6.0, what I meant was flash the latest available firmware for DBT, which is 7.0
2018-04-23
Germany
7.0
G930FXXS2DRDI
As above, the bootloader can be a pain to downgrade, so always try unbricking with the latest firmware available
Same process as I posted above, only using the firmware in this post ^^
Good luck
---------- Post added at 19:59 ---------- Previous post was at 19:50 ----------
Paachan said:
I just now noticed that the status LED doesn't even light up if you charge the device (maybe this is an indicator)
Click to expand...
Click to collapse
Yea that doesn't sound good, possibly a faulty motherboard, they seem to be quite a high % of hardware faults of the S7 on XDA, at least that is the outcome of sending them in for repair, but also could be the repair centres way of making the most £
Paachan said:
the OEM unlock setting was on default, so off I guess? It was just a regular OTA update and then the phone was stuck in a boot loop.
As *Detection* said it's probably is a hardware related issue I just now noticed that the status LED doesn't even light up if you charge the device (maybe this is an idicator)
I would've gladly used it as a backup device but I think it's just an expensive paperweight by now.
Still thank you for your help, appreciate it!
Click to expand...
Click to collapse
What version bootloader is it running go to download mode to find out top left corner last line of writing will be AP SWREV B:? what number is next to the B you will need to match this to the firmware you are trying to flash for example i use unbranded australian G930FXXU2DRBE firmware and in download mode my AP SWREV is B:2 the number signifies the bootloader its running some exapmes are below for you
AP SWREV B:1 = G930FXX "U1" DRBE
AP SWREV B:2 = G930FXX "U2" DRBE
AP SWREV B:3 = G930FXX "U3" DRBE
You need to match the number next to AP SWREV B:? with the firmware number "U?" For it to work even if it is the same marshmallow or nougat OS it must use the correct bootloader and firmware appropriate to be able to boot i have encountered this problem on numerous occasions if you try to flash a U1 to a U2 binary it will not boot it will not even write it to the memory and you will end uo with a bricked device until the appropriate firmware has been flashed using odin.
You need to also make sure you are using the latest version of odin and have all the drivers installed to your pc for the phone also the status led will not illuminate either while its bricked like this either you will not get this until the OS has been repaired.
If none of this works you could always flash TWRP to it with odin in the AP tab download linage 15.1 oreo 8.1 custom rom for G930F exynos and a gapps .ZIP files move them to an sd card and insert into phone boot into twrp swipe to allow modifications first tap back up and select EFS & BASEBAND and backup this contains your imei number you always should have a back up before flashing a custom rom just incase something goes wrong now after that go to wipe tap the format button on the right and select everything exept otg this will wipe everything and i mean everything OS related which is really want you want to do and also remove the DM verity encryption from the device to be able to boot no after that go to install and select the .ZIP rom and gapps and install after boot you can then re flash stock rom with odin and it should boot however warranty will be void and samsung KNOX will be triggered which means secure file cannot be used nor samsung health app however there is a simple solution i have found to get samsung health running on a rooted device i hope this helps its always worked for me ive purposly bricked my dev G930F so many times on purpose even lost the imei number before and gotten it back without flashing the backup they are really quite hard phones to break software wise.
Thanks
Matty1993
Matty1993 said:
What version bootloader is it running go to download mode to find out top left corner last line of writing will be AP SWREV B:? what number is next to the B you will need to match this to the firmware you are trying to flash for example i use unbranded australian G930FXXU2DRBE firmware and in download mode my AP SWREV is B:2 the number signifies the bootloader its running some exapmes are below for you
AP SWREV B:1 = G930FXX "U1" DRBE
AP SWREV B:2 = G930FXX "U2" DRBE
AP SWREV B:3 = G930FXX "U3" DRBE
You need to match the number next to AP SWREV B:? with the firmware number "U?" For it to work even if it is the same marshmallow or nougat OS it must use the correct bootloader and firmware appropriate to be able to boot i have encountered this problem on numerous occasions if you try to flash a U1 to a U2 binary it will not boot it will not even write it to the memory and you will end uo with a bricked device until the appropriate firmware has been flashed using odin.
You need to also make sure you are using the latest version of odin and have all the drivers installed to your pc for the phone also the status led will not illuminate either while its bricked like this either you will not get this until the OS has been repaired.
If none of this works you could always flash TWRP to it with odin in the AP tab download linage 15.1 oreo 8.1 custom rom for G930F exynos and a gapps .ZIP files move them to an sd card and insert into phone boot into twrp swipe to allow modifications first tap back up and select EFS & BASEBAND and backup this contains your imei number you always should have a back up before flashing a custom rom just incase something goes wrong now after that go to wipe tap the format button on the right and select everything exept otg this will wipe everything and i mean everything OS related which is really want you want to do and also remove the DM verity encryption from the device to be able to boot no after that go to install and select the .ZIP rom and gapps and install after boot you can then re flash stock rom with odin and it should boot however warranty will be void and samsung KNOX will be triggered which means secure file cannot be used nor samsung health app however there is a simple solution i have found to get samsung health running on a rooted device i hope this helps its always worked for me ive purposly bricked my dev G930F so many times on purpose even lost the imei number before and gotten it back without flashing the backup they are really quite hard phones to break software wise.
Thanks
Matty1993
Click to expand...
Click to collapse
Holy, this is a pretty explicit answer, thank you!
Judging by that I seem to have the right firmware for my Boatloader:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sorry for my late reply!
Paachan said:
Holy, this is a pretty explicit answer, thank you!
Judging by that I seem to have the right firmware for my Boatloader:
Sorry for my late reply!
Click to expand...
Click to collapse
No problem for the late reply yep firmware looks good matches to the BL however i noticed its says your binary and OS are custom when it should say official in donload mode was it previously rooted at some point ? Also have you downloaded the firmware from sammobile ? I would suggest using them for full original firmware packages as they have not been altered and will not apprear as custom when you try to flash with odin, does it complete the flash process and say pass or does it say fail ? Youll also notice when you flash on the screen of the phone it will have a progress bar in sync with odin does it complete the process and reboot or does it say blocked by frp lock if it says blocked by frp lock the firmware your trying to flash is not official you will need official firmware also as it already says custom find a twrp recovery.tar from the twrp website open odin place it in the AP section as soon as it reboots hold the power home ans volume up buttons until twrp appears swipe to allow modifications now go to wipe instead of factory resetting there will be a button saying format on the right tap that and type yes this will erase everything including the custom os it has on it i want you to do this step first before trying to flash the original firmware package as it will wipe everything for a fresh clean install.
Paachan said:
Holy, this is a pretty explicit answer, thank you!
Judging by that I seem to have the right firmware for my Boatloader:
Sorry for my late reply!
Click to expand...
Click to collapse
I'm not 100% sure about this, but that firmware states S2 not U2
See here, my BL is B:2 but all of the firmware files I can successfully flash are U2
Matty1993 said:
No problem for the late reply yep firmware looks good matches to the BL however i noticed its says your binary and OS are custom when it should say official in donload mode was it previously rooted at some point ? Also have you downloaded the firmware from sammobile ? I would suggest using them for full original firmware packages as they have not been altered and will not apprear as custom when you try to flash with odin, does it complete the flash process and say pass or does it say fail ? Youll also notice when you flash on the screen of the phone it will have a progress bar in sync with odin does it complete the process and reboot or does it say blocked by frp lock if it says blocked by frp lock the firmware your trying to flash is not official you will need official firmware also as it already says custom find a twrp recovery.tar from the twrp website open odin place it in the AP section as soon as it reboots hold the power home ans volume up buttons until twrp appears swipe to allow modifications now go to wipe instead of factory resetting there will be a button saying format on the right tap that and type yes this will erase everything including the custom os it has on it i want you to do this step first before trying to flash the original firmware package as it will wipe everything for a fresh clean install.
Click to expand...
Click to collapse
Actually scratch that frp lock is on you cannot flash anything custom to it while it is on just download your firmware from sammobile they have every country and are 100% official i will only download my firmwarw from there it is completely free to make an account and download the only thing is download speeds are slow so will take 2-3 hours to download is the only downfall but gauranteed to be official once downloaded place The files in corresponding slots in odin but with CSC just use CSC & not HOME_CSC this will perform a full wipe
Also maybe download U2 firmware aswell as S2 firmware
Matty1993 said:
Actually scratch that frp lock is on you cannot flash anything custom to it while it is on just download your firmware from sammobile they have every country and are 100% official i will only download my firmwarw from there it is completely free to make an account and download the only thing is download speeds are slow so will take 2-3 hours to download is the only downfall but gauranteed to be official once downloaded place The files in corresponding slots in odin but with CSC just use CSC & not HOME_CSC this will perform a full wipe
Click to expand...
Click to collapse
samfirm tool on XDA is full speed and downloads the latest stock ROM for whichever device you enter, direct from samsung servers
*Detection* said:
samfirm tool on XDA is full speed and downloads the latest stock ROM for whichever device you enter, direct from samsung servers
Click to expand...
Click to collapse
Or that also maybe yeah try U2 firmware instead of S2 as far as im aware S2 is the first of the B:2 binary updates
Hello,
I have the G930FD version of S7 (the dual sim version).
I am on the official samsung Firmware but I don't receive OTA updates. Even when I connect to Samsung Kies it also shows there are no updates. last update was security update for April 2017 !!
Please help me.
Who's your carrier and where are you located?
Otherwise flashing the last firmware with Odin and using home_csc will update you without data loss.
Beanvee7 said:
Who's your carrier and where are you located?
Otherwise flashing the last firmware with Odin and using home_csc will update you without data loss.
Click to expand...
Click to collapse
I use the unlocked version of the mobile which I bought from Saudi Arabia. how can I use home_csc since I am a bit noob in these things
https://updato.com/how-to/how-to-install-an-official-samsung-stock-firmware-using-odin
Boot into download mode (VOL DOWN + HOME + POWER until screen goes light blue) to confirm your model number, download the firmware for that model, and put the files into their slots in Odin (i.e. the files called BL_G930FXXX goes into the 'BL' slot etc, but for CSC put use Home_CSC and not normal CSC.