Develop Bugs

Multiloader v5.67 – Samsung Bada OS Flasher Software

{
"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"
}
Multiloader.is a downloader software used to flash/install/upgrade ROM or firmware on Samsung phone models that running Bada OS and other models that have supported chipset by multiloader.
Chipset supported by multiloader are MSM6250/MSM6250A, MSM6275/MSM6280/MSM6290, MSM6245/MSM6260, MSM7200A, LSI, BRCM2133, BRCM2153, MDM9200, MSM7x30
How to upgrade Firmware on Samsung Bada phone using multiloader?
There is many models of Samsung phone that using Bada OS such as S8500, S8530, M210s, etc. You can see the complete models here.
Below are example guide to flash/ upgrade ROM/firmware on Samsung Wave S8500 :
Samsung Kies need to be installed so S8500 download mode driver will be detected or you can download S8500 Driver here.
[*]Download Multiloader V5.67 from link below.
[*]Check your S8500 firmware by pressing *#1234# and download suitable S8500 firmware.
[*]Check Simlock by pressing *#7465625# and make sure Network lock is OFF. DO NOT flash the firmware if you have S8500 with Network locked since it will make your S8500 phone freezed after upgrade!.
[*]Open multiloader V5.67.
[*]Select LSI.
[*]Tick Full Download if you have boot file on the firmware that you have downloaded or leave it untick if the firmware does not have boot file BUT you need to make sure that the firmware with no boot file are same region with your phone firmware. DO NOT flash the firmware if the firmware boot file is old than phone boot file and DO NOT flash the firmware with no boot file if it different region with your phone firmware, ignoring those will make your S8500 bricked!.
[*]Click Boot and select boot firmware file, leave blank if the firmware does not have the boot file.
[*]Click Amss and select amss firmware file, leave blank if the firmware does not have the amss file.
[*]Click Apps and select apps firmware file, leave blank if the firmware does not have the apps file.
[*]Click Rsrc1 and select rsrc1 firmware file.
[*]Click Rsrc2 and select rsrc2 firmware file, and make sure to select LOW rsrc2 file .
[*]Click Factory FS and select factory fs firmware file, leave blank if the firmware does not have the factory fs file.
[*]Click SHP APP and select shp app firmware file.
[*]Click CSC and select csc firmware file.
[*]Click FOTA and select fota firmware file, leave blank if the firmware does not have the fota file.
[*]Click PFS and select pfs firmware file.
[*]Put your S8500 into download mode by pressing and holding Volume Down + Camera + Power button while the phone in off state.
[*]Plug in USB cable and wait until driver intalled.
[*]Click Port Search and make sure your S8500 detected in multiloader.
[*]Click Download and do nothing until the process is finished.
[*]It’s recomended to do a hard reset on S8500 after upgrade by pressing *2767*3855#.
Download Link : Download

Download link updated

Thanx.
Btw... Is someone able to "remove" these "features" from ML to write private infos to handset... like:
Code:
Windows User
Country
IP address from your PC
Thanx in advance.
Best Regards

Help!
i can't found the pfs file in BADA 2.0 Firmware (India). is it necessary or i can continue flashing?? Thanks.

a year later, someone still benefits from this thread

pls give me instruction for flashing samsung 5220
thanks advance

Which is latest android software flashing box & dongle in 2014 ?
Which is latest android software flashing box,dongle & flasher in 2014 ?

How to password unlock S5222 with flash tool
How to password unlock S5222 with flash tool

Hi
my phone wasn not work properly & when I turn on my phone a blue window was show and after the black page was show( Upload to the PC)
i want to flash my phone but when I click The Download the multiloader said Warring faild...
What am I doing??????????
PLZ HELP ME....

Multiloader 5.67 UI Messed Up!
I know this is wierd, but the UI of 5.67 is messed up on my PC.
5.65 works just fine, but it is made clear that in order to flash badadroid CM11 v 4.3, Multiloader 5.67 is compulsary. So, my question is that can I use 5.65 instead of 5.67?
Sorry for asking it here, but I dont have necessary permissions to post in the development threads.

TheBasterd said:
I know this is wierd, but the UI of 5.67 is messed up on my PC.
5.65 works just fine, but it is made clear that in order to flash badadroid CM11 v 4.3, Multiloader 5.67 is compulsary. So, my question is that can I use 5.65 instead of 5.67?
Sorry for asking it here, but I dont have necessary permissions to post in the development threads.
Click to expand...
Click to collapse
5.67 is necessary for Wave 3. So you can use 5.65

Doubt cleared.
hero355 said:
5.67 is necessary for Wave 3. So you can use 5.65
Click to expand...
Click to collapse
Thank you for the info. I always found the v5.65 to be better in the interface. It says that a guy called "Xenon" improved the interface. Did a good job, atleast I now have a version of multiloader I can always use.

v5.65 by xenon is a version for windows XP and works without problems
best regards

download link for bada 2,0
My phone is freezes after factory reset. Can someone give me bada 2.0 image to flash

You can find Custom-ROM "firefly" and modifyied Stock-ROMs at badania.de in the download section...

unblock
i read your description about flashing, but i have a problem with gt s8500 wave with bada os.
my phone has a phone password, without it, it cannot start. the problem is that i forgot this password. what should i do?

sidrit_d said:
i read your description about flashing, but i have a problem with gt s8500 wave with bada os.
my phone has a phone password, without it, it cannot start. the problem is that i forgot this password. what should i do?
Click to expand...
Click to collapse
First, i'm not sure this is the right topic.
Anyway, you set a password on bada ? Well, if you really forgot it, i don't think there is another option than reseting the phone.
Read this and this, or search a bit more on google, or just flash the phone with any bada rom (you'll loose your datas !).

hello guys my celphone stuck after boot on sim logo ..........what should i do? i flashed bada 2.0 with multibootloader 5.67

It worked With Netlock on!
Thank you so much! I want to Net-Unlock my phone, and there is a thread https://forum.xda-developers.com/showthread.php?t=1473089 with a solution for GT8500, but only if Bada 1.2 odr 2.0 are allready installed. Unfortunately, my phone was still running Bada 1.0. So I took the risk and followed your instructions to flash Bada 2.0. It worked in the end, with some excitement inbetween:
After dowloading the Boot Files, my phone freezed during restart. I took out the batterie, put it back in, tried to put the phone in Dowload Mode, nothing happened. I tried to start restart it, it froze again. I took out the batterie, put it back in, tried to activate Dowload Mode, got a blue screen freeze. Took out the batterie again, put it back in, startet the phone: it froze again during restart. I wated for a longer time, some few minutes, then took out the batterie and tried again to get it in Dowload Mode - and it worked!
Then I completed the whole process as you described and voilà - everything's fine, my phone started and is now running Bada 2.0.
Firmware before: I had Bada 1.0 with Hutchison Drei Austria netlock and branding: S8500NEJE5_S8500DREJE5
For Flashing Bada 2.0 I used the firmware for Hutchison Drei Austria from SamMobile: S8500NELB1_S8500DRELB1.
Now I will try to get rid of the Netlock.
Thanks again!
Maria

[GUIDE] Fix an unflashable or soft bricked N7100!

Hello everyone!
This is a guide dedicated to those who are a bit noobish or new to XDA, so if you're not one, I would advise to stop reading now! (although feedback would be great! )
After my success over at the GSII's boards with over 300,000 thread views all over my threads from all sections, I believe that this board should also get some taste of my how to. I'm going to be explaining step by step what to do and how to do it, while explaining each thing.
Just in case you don't know, a soft brick occurs when you flash a ROM or Kernel, and it doesn't go your way, thus bricking the "soft part", aka Software, of your phone. Therefore, it is easy to recover from. Now, if you poorly flash a ROM and it results in a NAND rw corruption (NAND's read and write function corrupted) it means that it is an issue deeper than a soft brick, but still no reason to be alarmed!
When you can flash a kernel, but you can't flash a ROM due to ODIN errors, that happens because it can't properly read the NAND, but it still can flash a kernel. But you ask, why the kernel? Because flashing a kernel is a bit deeper than flashing a ROM. When you flash a kernel, you're changing/putting new instructions to the hardware, and when flashing a ROM, the instructions that are drewn are different and more "simple" (just pulling and pushing folders without touching partitions), so when flashing, ODIN will say "FAIL" instead of "PASS", or suddenly stopping the flash out of nowhere.
__________________________________________________
IF YOU ONLY HAVE A BOOTLOOP​
Wipe data/factory reset and wipe cache. IF THAT DOESN'T WORK, MOVE ON WITH THE GUIDE
__________________________________________________
Let's start with the basic files, downloads and requirements​
1) You have to know the basics of ODIN and flashing for starters!
2) Just to be safe, please uninstall Samsung KIES. It usually interferes when flashing with ODIN. You must have the USB drivers from your phone, so don't uninstall them. Only uninstall the program KIES.
Just in case you don't have them, here are the Samsung USB drivers
3) Download ODIN v3.07, the tool that we'll use to flash all the things into our loved Galaxy Note 2 N7100!
4) Download the necessary files : the Recovery Package/ROM and the bootloader will be included in the very package. Android 4.1.2, unbranded, XXDLJ2. When you recover the phone, just update it if you want a newer version!
5) You must have WinRAR to unRAR the Recovery Package and to unzip ODIN.
You can also use 7zip if you'd like.
And that is it! Let's get down to business
__________________________________________________
If your GSII has the folowing symptoms :
Bootloop
Stuck on GNII logo, but already removed the battery to try to fix it
Enters Download mode and Recovery mode
It means that you are soft bricked and is easy to solve.
But if your symptoms are the mentioned above, PLUS the symptoms below
Doesn't flash
Bad flash in odin (FAIL after flashing, or the flashing suddenly stops)
Then it means that you have a bigger issue, such as the aforementioned NAND rw corruption.
It's time to open up ODIN and start reviving your phone!
__________________________________________________
First of all, let's just have a quick glance of how ODIN looks like, and where we should put the files :
{
"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"
}
As the picture clearly shows, the green rectangle is where you can tick. Those 2 which are ticked must remain that way. And the red one is well... Where you SHOULDN'T touch
ONLY FLASH WITH RE-PARTITION TICKED AND A PIT FILE IF YOU ARE SURE
THAT THE FLASH WILL SUCCEED.
Which means that you CANNOT have a damaged USB, corrupted drivers and such.
​
When recovering from a soft brick, it is recommended, not mandatory, to have Re-partition ticked with a .PIT file. So you must be extra careful when you are using a .PIT and Re-Partition. And obviously, the red box is the one where you can't and don't want to mess with
But where are the files going, you say?
.PIT -> PIT
BOOTLOADER -> BOOTLOADER (or PDA if flashed alone)
CODE -> PDA
MODEM -> PHONE
CSC -> CSC
***If you have a 1 file .tar package, then flash it in PDA***​
There is only 1 way to recover a soft bricked phone. How to recover from a NAND corruption? We'll get on that later on
__________________________________________________
Recovering a soft bricked phone​
1) Grab the Recovery Package, and you'll see a bunch of .tar files. Take a look at the names. You'll see CODE, MODEM, CSC (and the .PIT). Put each one in its place (EXCEPT the .PIT, refer to the warning below).
2) Turn off your phone. Enter Download mode by presing Volume Down + Home + Power button.
3) Plug in your phone. It will show you, in a blue box in ODIN, ID:COMx (x being the number displayed, sometimes displays 7, sometimes displays 9)
Now here, take a breath​
First try flashing WITHOUT the .PIT and re-partition. And only if it DOESN'T WORK OR FIX then you flash with the .PIT and Re-Partition ticked.
4) Once ready and done all your prayers, press Start. Wait patiently. It usually takes 5-10 minutes to flash.
Have you done everything correctly until now? Then...
Congratulations on recovering your phone!​
You deserve some cake afterwards, and some rest
Now, if your problem is the NAND rw coruption, and wasn't fixed by the above fix, then follow these steps :
WARNING : FLASHING A BOOTLOADER IS DANGEROUS. FLASH WITH EXTREME CAUTION.
4) Open the zip you downloaded and find the Bootloader. Flash it as PDA or Bootloader in ODIN. Without ticking Re-Partition
5) Flash the recovery package, like in steps 1-4 (WITH the re-partition ticked and the .PIT file in place) and that will fix any of your issues
6) After you have recovered your phone, I advise you to have your phone completely up to date by browsing and downloading the firmware for your version through SamMobile!
I hope that this guide was helpful, and if it was, hit the thanks button!
Credits mainly go to as i9000, for his amazing collection of ROMS and files
_______________________
Disclaimer
This is to be used as educational information. I am not liable of any damage that may occur to your phone.

I was wondering where I can download the recovery package? I can not seem to find a link pointing in any directions. All the help would be great. I know my way round odin an stuff but, this new problem is an new playing field for me

Buckers1313 said:
I was wondering where I can download the recovery package? I can not seem to find a link pointing in any directions. All the help would be great. I know my way round odin an stuff but, this new problem is an new playing field for me
Click to expand...
Click to collapse
Oh man, I derp'd on there! Apparently I didn't include the DL link
Will fix in a moment!
EDIT : Hmmm, the link was there all along, in the code at least... Now that was weird

Good.
This should go into general imao
this is XXXDDDAAA

Phistachio said:
Oh man, I derp'd on there! Apparently I didn't include the DL link
Will fix in a moment!
EDIT : Hmmm, the link was there all along, in the code at least... Now that was weird
Click to expand...
Click to collapse
Thanks for that. Everytime I extract the files, I don't get anything for odin just a heap of img and bin files. Am i extracting them wrong?

Buckers1313 said:
Thanks for that. Everytime I extract the files, I don't get anything for odin just a heap of img and bin files. Am i extracting them wrong?
Click to expand...
Click to collapse
You shouldn't extract them. You must put the .tar file in each box, CODE -> PDA, etc

The file which you extracted must be put in pda tab. The. Tar.md5 file. You must not extract that.
this is XXXDDDAAA

Phistachio said:
You shouldn't extract them. You must put the .tar file in each box, CODE -> PDA, etc
Click to expand...
Click to collapse
Thanks for your help. my device isnt flashing anything
just hangs at setupconnect and then fails for different reasons. might try my chances with a warranty :S

Buckers1313 said:
Thanks for your help. my device isnt flashing anything
just hangs at setupconnect and then fails for different reasons. might try my chances with a warranty :S
Click to expand...
Click to collapse
Tell me exactly what you're doing, step by step.

Phistachio said:
Tell me exactly what you're doing, step by step.
Click to expand...
Click to collapse
downloaded the zip
unzipped (all correct tar files where there and the pit)
Opened odin and placed each tar and pit file in the correct place.
Phone placed in download mode (the phone is showing in odin as connected)
Pressed start (tried with pit and no pit)
Put simply the phone isn't receiving anything. Usually when I flash with odin the phone and software do there thing. Download mode isn't even showing any signs of being connected. Setupconnection hangs there for a while and then it fails and sometimes it says pit file mapping (or something) and then fails after 10 mins of hanging there.
I have even tried flashing the bootloader by itself and that doesn't work either.
Cheers for all your help to.

Buckers1313 said:
downloaded the zip
unzipped (all correct tar files where there and the pit)
Opened odin and placed each tar and pit file in the correct place.
Phone placed in download mode (the phone is showing in odin as connected)
Pressed start (tried with pit and no pit)
Put simply the phone isn't receiving anything. Usually when I flash with odin the phone and software do there thing. Download mode isn't even showing any signs of being connected. Setupconnection hangs there for a while and then it fails and sometimes it says pit file mapping (or something) and then fails after 10 mins of hanging there.
I have even tried flashing the bootloader by itself and that doesn't work either.
Cheers for all your help to.
Click to expand...
Click to collapse
Try a different USB cable or a different USB port

Phistachio said:
Try a different USB cable or a different USB port
Click to expand...
Click to collapse
Cheers. I have tried different cables, USBs and even computers. I have tried with or without drivers and all the steps you have suggested.
I find it weird that it boots into download mode but just doesn't download. I'm wondering if something else may have stuffed itself?

Buckers1313 said:
Cheers. I have tried different cables, USBs and even computers. I have tried with or without drivers and all the steps you have suggested.
I find it weird that it boots into download mode but just doesn't download. I'm wondering if something else may have stuffed itself?
Click to expand...
Click to collapse
Usually when it's stuck at setupconnection it means that it can't connect to the NAND, more specifically, to r/w to the bootloader. Have you tried flashing JUST the bootloader?

Phistachio said:
Usually when it's stuck at setupconnection it means that it can't connect to the NAND, more specifically, to r/w to the bootloader. Have you tried flashing JUST the bootloader?
Click to expand...
Click to collapse
Yeah same thing happens. First time around it asks for the pit file though. I have tried flashing it as a bootloader and PDA file, but it still just hangs there.

Buckers1313 said:
Yeah same thing happens. First time around it asks for the pit file though. I have tried flashing it as a bootloader and PDA file, but it still just hangs there.
Click to expand...
Click to collapse
Hmm, that's odd You're using ODIN v3 correct?

It's SDS nothing to do, send back to Samsung service; it means motherboard replacing

almaalma74 said:
It's SDS nothing to do, send back to Samsung service; it means motherboard replacing
Click to expand...
Click to collapse
If it was SDS, would the phone be able to boot into download mode?

Phistachio said:
If it was SDS, would the phone be able to boot into download mode?
Click to expand...
Click to collapse
Yeah, it's called as "half" SDS, it is sad but true... My phone had same issues

almaalma74 said:
Yeah, it's called as "half" SDS, it is sad but true... My phone had same issues
Click to expand...
Click to collapse
Will Samsung know that I have put customer roms on it?

Fail to show as connected
I'm trying to flash out of CWM into TWRP but nether the Toolkit nor Odin shows my device as being connected in debug mode or download mode. What's the way ahead on this? I'm just trying to get another boot loader because I've been having issues with CWM failing on ROM installs from zip files. The only ROM I've been able to install is PAC.

[GUIDE] Flashing Original Firmwares >1GB / Unbrick Procedure (UPDATED 07/12/13)

If you can get in download mode, nothing is lost. You can still go back and restockify you LG Optimus G (stock rom ,locked bootloader ,no root).
Original Work by [email protected] I have only translated it to English
Tested and working on LG-E975
Some tips before you start
As you will see is a fairly simple procedure, but not without risk. Take a quick read the entire guide before you begin: it will help you understand how to move.
The most important thing is to keep calm, do not panic and do not crush random keys. If you do not understand a passage, reread it. If you have not figured it out yet, reread it AGAIN or ASK here for help. No one runs behind you, so do not do things in a hurry.
I DO NOT TAKE ANY RESPONSIBILITY IF YOU BRICK YOUR PHONE.
Given that at end of the flash is recommended to do a hard reset, is a good idea to make a backup of all your personal data (photos, videos, etc etc), contacts , and if you want even applications.
DON'T FORGET TO BACK UP EFS PARTITION!
Prerequisites
1. Download the KDZ with this tool (credits [email protected]) https://mega.co.nz/#!wxoHSayQ!AsUn6wfsc0rts87HIlOSwBd9dilot2229useWzrsH_g
2. Download and install the LG USB drivers LG USB Drivers
3. Download this file. It's a compressed file that contains everything you need NEW KDZ Updater
4. Download and install LG Mobile Support Tool http://csmg.lgmobile.com:9002/client/app/B2CAppSetup.exe
Let's start
1. Extract the "Flashtool" folder on the desktop, or where you want. Open the folder "Flashtool" and install msmxl.msi (if not already installed).
{
"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"
}
2. Turn off the phone and connect it to the PC with the USB cable while holding VOLUME- AND VOLUME +, until you see the download mode logo. The PC will install some drivers. There may be a kind of protection that prevents you enter this mode if there is too little current on the phone.
However, you must be able to get to the screen that's underneath.
4. Go back to Flashtool folder and run as administrator WindowsEnabler.exe. Go to the bar at the bottom right, and click once with the left mouse button over the icon of WindowsEnabler, so that appears the "On"message.
5. Now run as administrator UpTestEX.exe and do the following:
-Select the .KDZ file that you want to flash
-Set "3GQCT"
-Set PhoneMode "EMERGENCY"
Once done, click "Normal web upgrade test"
6. In the next window click "Upgrade Start"
7. Wait a few seconds an a new window will pop up.
- Click "Clear phone.."
- Select different country if you're not in Korea
- Select Language
- Click OK
After this the LG flashing tool should start analyzing your phone and flashing the .KDZ
Once done you can detatch the USB cable and see if the phone boots up. However it will probably bootloop. In this case follow the Hard Reset Procedure below.
Hard Reset Procedure
The phone has to be off. Hold Volume - AND Power , a message will show up confirming the factory reset. Press Power Button twice , than wait. It will auto reboot.
Thanks:
- [email protected] For the realization of the guide
- [email protected] For the big work regarding .KDZ files
- [email protected] Flashing 1 GB and greater .KDZ
Notes
- I have translated this guide because the one I found was little bit tricky unclear and didn't work for me, I hope I have done a good job. I'm anyway available to any modification. Just write below.
- Also I'm Italian so there may be some mistakes in the translation , report back i will correct them with pleasure.
Don't forget to report back if it worked!

reserved 1

Does this ring a bell to you?
http://forum.xda-developers.com/showthread.php?t=2010624
Another question, why place the kdz folder in C:/? I have used kdz updater more than 10 times,it's well placed in D:/Downloads/ folder.It's working everywhere,no need for a special path.
And you didn't mention the 1gb+ file error. kdz updater will not work with bigger files.
What's tricky in potatohead thread?
1.have proper drivers installed,this is universal law for ALL devices. no drivers,not working.
2.download correct kdz file for your phone.
3.download kdz updater
4.enter download mode
5.open kdz updater and choose the file,selecting the right settings.
6.start ,wait to finish and that's it.
If anyone understood something else,it's not the author's fault.

I did all that you point in your guide but during the process, the program went in Not Responding, and after 30s Windows said he closed the program , and now my phone is stuck in Download Mode... Please help me

What windows are you using, also, what machine(laptop/desktop)..
If you are using a desktop,make sure you are using a rear usb port,not front and not through a usb hub,not even an usb extension cable.
if you are using a laptop,be sure you are using usb 2.0,not 3.0.

Rockguy40 said:
5. Now go back in Software Update, select the .KDZ file that you want to flash, and set entries as in the picture. Type "3GQCT" PhoneMode "EMERGENCY".
Click to expand...
Click to collapse
It's not ''Emergency''...phone mode must be ''CS_EMERGENCY'' :good:

Backstaba said:
I did all that you point in your guide but during the process, the program went in Not Responding, and after 30s Windows said he closed the program , and now my phone is stuck in Download Mode... Please help me
Click to expand...
Click to collapse
try using this version, tested windows 7 64 http://www.mediafire.com/download/ekkglj22rh6alho/FlashTool.1.0.54.rar

JasonBourne.Qc said:
It's not ''Emergency''...phone mode must be ''CS_EMERGENCY'' :good:
Click to expand...
Click to collapse
I didn't write the guide as I said , anyway EMERGENCY mode worked for me.

Backstaba said:
I did all that you point in your guide but during the process, the program went in Not Responding, and after 30s Windows said he closed the program , and now my phone is stuck in Download Mode... Please help me
Click to expand...
Click to collapse
As I write in the guide it's normal for the program to go in non respond when decompressing the .kdz but if you don't touch the windows (not a single click) of the updater, windows shouldn't auto kill the program.

it not work
I cant found LG mobile usb modem I am installed driver
Phone was not found from KDZ (
help me..
sorry, my ENG very bad

Rockguy40 said:
If your phone is stuck on the logo LG, do a hard reset .... See below for the procedures.
If the phone starts up as normal, it's recommended to do a hard reset.
Hard Reset Procedure
The phone has to be off. Hold Volume - AND Power , a message will show up confirming the factory reset. Press Power Button twice , than wait. It will auto reboot.
Click to expand...
Click to collapse
My phone get stuck on the logo LG but I can't hard reset ( Hold Volume - AND Power : nothing show on screen ), what do I have to do now?
thank in advance!

Hi,
Interesting post, so this i to unbrick a phone and revert back to original state of the phone (out of the box).
Is this also a possible method to flash any firmware I want. Let me explain, I have my new OG from French Operator SFR with a custom ROM and want to install as a replacement the latest FRA or EUR stock firmware from LG. Can this method be executed safely, OR should I unlock my bootloader and go for a firmware flash through the CWM recovery way instead ?
Thanks for your tip.

bobthedwarf said:
Hi,
Interesting post, so this i to unbrick a phone and revert back to original state of the phone (out of the box).
Is this also a possible method to flash any firmware I want. Let me explain, I have my new OG from French Operator SFR with a custom ROM and want to install as a replacement the latest FRA or EUR stock firmware from LG. Can this method be executed safely, OR should I unlock my bootloader and go for a firmware flash through the CWM recovery way instead ?
Thanks for your tip.
Click to expand...
Click to collapse
Well, i am now root and have unlocked boot loader and installed cwm touch recovery. I feel it was all useless for my purpose being : install à stock firmware instead of my sfr operator ROM.
The right procedure will be through kdz?
CAN i install a lg firmware now from cwm ?

Firmware link update
Please, anyone knows new links to LG E975 original firmware? The link I found for Italy versions are not working anymore. I need unbranded and Vodafone versions. Many thanks.

Lg-firmware.com
Sent from stock LG E975/smart phones,dumb people. now Free

LGE975 firmware
Many thanks for the help but Lg-firmware doesn't work, google suggested lgfirmwares but there is only one type of firmware for LGE975 and the link is broken...
I saw that the link have been only modified in csmgdl lgmobile com but the files are still there.

I just downloaded 10h open romania from that place.
Sent from stock LG E975/smart phones,dumb people. now Free

hi i can't seem to get the KDZX_FW_UPD to open. i've tried running it in admin mode and installing the msxml first but no luck, can someone help?

kimitza said:
I just downloaded 10h open romania from that place.
Sent from stock LG E975/smart phones,dumb people. now Free
Click to expand...
Click to collapse
Does 10h support English...??
Sent from my LG-E975 powering Stock 4.1.2

Yes,it has all the languages...

How To Guide Guide to root Galaxy S22 (B/E/N/0), unlock bootloader and flash official firmware (noob friendly)

Code:
Your warranty is now void.
If you root your device, Your KNOX status will be tripped.
You can still pass the safety net after you root if you follow the instructions.
I am not responsible for bricked devices, dead SD cards although it is not really possible
Please do some research if you have any concerns about doing this to your device
How to flash official firmware? (not the root and unlock bootloader part!)
You will need:
A Galaxy S22 and common sense
Samsung Odin (the flashing tool of the official firmware)
https://dl2018.sammobile.com/Odin3-v3.14.1.zip
You need to extract the zip file and you are going to use the file Odin3_v3.14.1.exe inside the folder.
Samsung Android USB Driver for Windows
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.
developer.samsung.com
Double-click and install the exe file.
Samsung Official Firmware
Release 1.0.3 · zacharee/SamloaderKotlin
Contribute to zacharee/SamloaderKotlin development by creating an account on GitHub.
github.com
[URL='https://samfrew.com/model/SM-S901U1/region/TMB/']https://samfrew.com/model[/URL]
Download the platform you want to download to. (Windows)
You need to extract the zip and double click open the file Bifrost.exe inside the folder.
You need to fill in the Model, Region, press the Check for Updates button and the Download button.
How to find the Model: on your phone → Settings → About Phone → The third row says the Model number and you need to remove the part with the part of /xx, for example, SM-S908B/DS and you only need to type SM-S908B
How to find the Region: You can check the Region at this link https://samfrew.com/model/SM-S901B/ and
https://samfrew.com/model/SM-S901E/ (thank for the reminder from @DarkestSpawn )
You need to find find a three-letter word depending on your carrier and country and type it in Bifrost, for example, EVR
Press the Check for Update button and download it with the Download button.
Put it to a place you can easily find, ie. Desktop.
After downloading it, find the file SM- S908x_x_xxxxxxxx_xxx.zip.enc4 on the place you put it and change the document format from .enc4 to .zip. Then, double click and extract the file.
Open Odin3_v3.14.1.exe and turn off your phone. Connect a side of your USB to your PC/Laptop, keep pressing volume up and down together until you go to Download Mode. Put another side of the USB into your phone. When you arrived at Download Mode press volume up. Go back to Odin3_v3.14.1.exe:
-Click on BL and select BL_S908xxxxxxxxxx.tar.md5
-Click on AP and select AP_S908xxxxxxxxxxx.tar.md5
-Click on CP and select CP_S908xxxxxxxxxx.tar.md5
-Click on CSC and select CSC_OMC_xxxxxxxxxx.tar.md5
Press Start to flash the firmware, after done, your device will automatically reboot to the system.
How to unlock the bootloader?
Go to your phone → Settings → About Phone → Software information → Press Build number 6 times until you see the notice “You’re now a developer”
Go in Settings → Developer options → enable OEM unlocking
Power off your phone first. Then, connect a side of your USB to your PC/Laptop, keep pressing volume up and down together until you go to Download Mode. Put another side of the USB into your phone.
When you arrived at Download Mode, long press volume up until you see the black screen. Confirm to unlock the bootloader and you will erase your device.
How to root your phone?
After you unlock your bootloader, you set up your phone and make sure you do not sign in google account first. Install Magisk https://github.com/topjohnwu/Magisk/releases/download/v24.1/Magisk-v24.1.apk on your phone. Oh yes, in case you do not know, you need to allow the app to install apps so that you can install the apk.
Transfer AP_S908xxxxx.tar.md5 in the firmware you download from your PC/Laptop to your phone.
Open Magisk on your phone and press the install button in the Magisk column. Select 'Select and Patch a File', 'Let's Go' and find the AP_S908xxxxx.tar.md5 and select it. You can have a cup of coffee if you like when you waiting for the patching of the file.
After finishing the patching, you need to transfer the file magisk_patched-24xxx_xxxxx.tar in the Downloads folder back to your PC/Laptop.
Turn off your phone. Connect a side of your USB to your PC/Laptop, keep pressing volume up and down together until you go to Download Mode. Put another side of the USB into your phone. When you arrived at Download Mode press volume up. Open Odin3_v3.14.1.exe on your PC/Laptop:
Click on BL and select BL_S908xxxxxxxxxx.tar.md5
-Click on AP and select magisk_patched-24xxx_xxxxx.tar
-Click on CP and select CP_S908xxxxxxxxxx.tar.md5
-Click on CSC and select CSC_OMC_xxxxxxxxxx.tar.md5
When it finishes flashing it, it will automatically reboot and you can gain root access.
Optional: If you want to have the safety net passed (most of the banking apps use it), then you need to install the zip
as a Magisk module in Magisk https://github.com/kdrag0n/safetynet-fix/releases
How? Go to Magisk → Modules → install from storage and select the zip you downloaded.
How to update system without losing root and data?
Download new firmware of the phone and update the Magisk App if it is not up to date. Unzip the firmware you download and transfer the AP file to your phone. Patch your AP file and transfer it back to your PC (in /sdcard/Download)
Power off phone and reboot to Download mode
Open Odin and put new magisk_patched file in the AP slot, the BL and CP from your new firmware into their respective slots and importantly *HOME_CSC* into the CSC slot.
Press start and let Odin do it's stuff.
When flashed, do not wipe.
Press and hold Vol-down and Power
As soon as screen appears, let go of all buttons.
Within moments without any further user intervention your phone will reboot into your updated Magisk rooted mode, data intact.

OP has the link to the Ultra variant, here is the link to the 22+ variant. This is for the Region section.
https://samfrew.com/model/SM-S906B/

DarkestSpawn said:
OP has the link to the Ultra variant, here is the link to the 22+ variant. This is for the Region section.
https://samfrew.com/model/SM-S906B/
Click to expand...
Click to collapse
Thanks for your reminder, I will change it

I could have sworn when I posted this, this thread was under the S22+ variant....
https://samfrew.com/model/SM-S901B/
https://samfrew.com/model/SM-S901E/
These are for the standard S22 variant

DarkestSpawn said:
I could have sworn when I posted this, this thread was under the S22+ variant....
https://samfrew.com/model/SM-S901B/
https://samfrew.com/model/SM-S901E/
These are for the standard S22 variant
Click to expand...
Click to collapse
Thanks a lot

Can I root Note8 that installed July 2021 security patched?

SLeePLatED said:
Can I root Note8 that installed July 2021 security patched?
Click to expand...
Click to collapse
You are in the wrong forum. It depends on your model

Will this work for the snapdragon varient sm-s901u1

za33ck said:
Will this work for the snapdragon varient sm-s901u1
Click to expand...
Click to collapse
Not USA Snapdragon

Be sure to use a patched Odin for carrier branded devices.

Bummer...the snapdragon never gets any love

za33ck said:
Bummer...the snapdragon never gets any love
Click to expand...
Click to collapse
Sorry to hear that. Other countries' Snapdragon able to unlock bootloader

Is there anyway to get system status back to official after OEM unlock?

persmash said:
Is there anyway to get system status back to official after OEM unlock?
Click to expand...
Click to collapse
Yes, you can do it by flash the official Samsung firmware(the one you have downloaded), however, you will lost root

Williamtung said:
Yes, you can do it by flash the official Samsung firmware(the one you have downloaded), however, you will lost root
Click to expand...
Click to collapse
It is not funny
Of course I asked to have both.

persmash said:
It is not funny
Of course I asked to have both.
Click to expand...
Click to collapse
However, there's no way to fix it (I think there is and I have seen somebody did it. However, it's complicated and I think it is about editing system files)

I flashed my S22 with SM-S901U1 (XAA) US unlocked firmware. My phone's model number changed from U to U1 which is what I wanted, but my service provider software version is still VZW/VZW,VZW/ VZW. Did I do something wrong? The verizon bloatware is gone, and it boots up without Verizon's load screen, but I'm pretty sure the VZWs are not right except for the last one.
Edit: Could this be because my phone is still carrier locked? And once it is carrier unlocked by VZW I can flash it again?

penguin007 said:
I flashed my S22 with SM-S901U1 (XAA) US unlocked firmware. My phone's model number changed from U to U1 which is what I wanted, but my service provider software version is still VZW/VZW,VZW/ VZW. Did I do something wrong? The verizon bloatware is gone, and it boots up without Verizon's load screen, but I'm pretty sure the VZWs are not right except for the last one.
Edit: Could this be because my phone is still carrier locked? And once it is carrier unlocked by VZW I can flash it again?
Click to expand...
Click to collapse
Your model of your phone will never change because that's your model! (Of course you change it by some way, just the display)

So is this correct then? Cuz you can see my model number is now SM-S901U1 but the service provider SW is still VZW which is okay? Right?
{
"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"
}

Assume this is non-US (no U or W variants), correct?

[GUIDE] Repair, Unbrick, Unroot, Re-lock Bootloader and Flash stock firmware in Samsung Devices

Welcome to this easy guide.​
Time needed: 15 / 60min (depends on your internet connection)
Ease of operation: Very easy
Don't be fooled by the length of this guide ... the operations to be done are quick and easy.
NB: I state immediately that this procedure does not restore the state of Knox to 0x0 if by chance you have brought it to 0x1.
To date, this is an irreversible process.
In the next lines we will see how to restore our Samsung device to its original factory conditions, after unlocking the Bootloader, rooting and installing various types of custom installations, such as custom OneUI, AOSP or Google ROM.
It may happen that you want to go back to the original firmware of our Samsung, after trying various custom ROMs, after having rooted and modified the recovery, missing with the phone partitions, lost EFS folder or corrupt IMEI. The reasons can be many. This guide is aimed at all those who, with the classic Odin procedure to install the stock rom, are unable to restore the phone to normal operating conditions.
But it can happen to fail in this thing, even using Odin to put back the original software, Odin himself or the phone can crash to the BOOT partition or generate other errors, with VBMeta or generic errors, including partition ones.
So let's see how to solve all the inconveniences due to modding on our Samsungs to 99%. Let's begin!
- MATERIAL REQUIRED:
Latest version of Frija link
Latest version of Odin link
Samsung USB Driver link
File Manager zip (example 7zip) link
PC with Microsoft Windows 7-8-8.1-10-11
USB type C cable
1 - Download the latest stock firmware for our Samsung:
Download the latest version of Frija and once the program has started, enter the model code of your device and the abbreviation of your CSC.
Make sure the "Auto" checkbox is checked.
Once you have checked everything, click on "Check Update" and click on "Download". Wait for it to download.
{
"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"
}
Once you have downloaded the zip containing the various parts that make up the stock software (see image below), extract it to a folder of your choice. We will have 5 files in total.
2 - Retrieve the original PIT file
To recover the PIT file (partition list) for our device, go to the firmware folder you just downloaded with Frija, locate the "tar.md5" file with the words CSC_OXM_N............., right click on the it and select rename, adding ".zip" at the end to "transform" it into a compressed file that can be opened. This way you will have something like
"CSC_OXM_N975...............REV01_user_low_ship.tar.md5.zip"
Give the Ok and confirm the change of the file extension.
You should now have the same situation as you see in the image below. Total 5 files of which one is a ".zip" files.
Now open the file you just renamed with 7zip, the main window of the 7zip program will open with various files inside:
Now copy the "D2S_EUR_OPEN.pit" file by right clicking and selecting the "copy to ..." item and giving the ok without changing anything. The .PIT file will be copied to the same folder as the previously downloaded firmware.
Once this is done, the folder that appears will look like this (Now, the total files are 6 of which one is a ".zip" files):
Now just put the CSC_OXM ... file back to the previous condition, renaming it one more time and eliminating the ".zip" extension at the end of the name, in order to find an MD5 file again. This will be the file we will have:
"CSC_OXM_N975...............REV01_user_low_ship.tar.md5."
Now we have everything we need. If we have done everything correctly this is the final result (Total 6 files).
3 - Prepare and Configure Odin
Now open the latest version of Odin (as of May 2022 the latest version is 3.14.4), load the corresponding downloaded firmware files in the various slots (BL, AP, CP and CSC) as usual.
In the CSC box, upload the file labeled "CSC_OXM_N975 ............... REV01_user_low_ship.tar.md5."
Did you know that....
The CSC_OXM file is used to restore the internal memory as factory, this will delete all personal data in the phone memory, all applications and data associated with it.
The HOME_CSC_OXM file, on the other hand, will not act in any way on the internal memory. Useful if you want to update while remaining in the same type of ROM. Not recommended if your phone has a Custom ROM installed, as it may not start or give errors in previously installed applications.
If you want to do a clean install of the original ROM, always use the CSC_OMX file!
Click to expand...
Click to collapse
Once this is done, move (still in Odin) to the "Option" tab and check the following items:
Auto Reboot
Nand Erase
Re-partition
F. Reset time
The rest of the items MUST NOT BE SELECTED!
Again in Odin, this time go to the PIT tab, a warning message will appear, give the ok and select the first extracted file which has the unique name "D2S_EUR_OPEN.pit"
If you have done everything right you should have the same situation as the image below:
4 - Return the phone to the original firmware
Connect the USB type C cable to your phone and restart your phone in "Download mode" (check the right combination for your model), or use the Custom Rom to do this, usually all coustom roms or custom recovery offer reboot in Download mode (or Booloader).
In odin in the "Log" tab, you should see the word "Added" with the number of the port to which it is connected (example "0: [COM3]"), if so, press the START key of Odin and wait for the restart (this procedure will delete all data on your device).
If nothing appears, install the Samsung USB drivers and repeat step 4.
5 - Relock the BootLoader
To get rid of that fatal warning message when starting the phone that tells us that the BootLoader is unlocked once and for all, let's put it back in place, relocking the BootLoader.
(Image for demonstration purposes)
Turn off the phone, reconnect the USB cable and immediately press the Volume + and Volume- keys at the same time.
Return to Download mode (albeit a little different), with various options (actually only 3).
In this case, follow the second option (Volume up long press: Device unlock mode) hold down the Volume + key for a few moments until the message "Lock Bootloader?" Appears. To confirm everything, make a single click on Volume + (also in this case the phone will be formatted by the system again) and wait for a complete restart.
6 - Relock OEM (optional but recommended if you want to stick with the Samsung ROM)
Once your phone has restarted and the initial setup is complete, you can also disable the OEM unlock capability and reuse the security features.
To do this, go to Settings / Phone Information / Software Information and tap several times on the wording "Build version" in order to unlock the "Developer options". If prompted, unlock your smartphone with your PIN or sign.
Now go back to the main Settings page, open the Developer Options and check that the "OEM Unlock" item is disabled, otherwise disable it and restart the device.
Well now you have your Samsung with Original firmware again. Enjoy

ExileTM said:
Welcome to this easy guide.​
Time needed: 15 / 60min (depends on your internet connection)
Ease of operation: Very easy
Don't be fooled by the length of this guide ... the operations to be done are quick and easy.
NB: I state immediately that this procedure does not restore the state of Knox to 0x0 if by chance you have brought it to 0x1.
To date, this is an irreversible process.
In the next lines we will see how to restore our Samsung device to its original factory conditions, after unlocking the Bootloader, rooting and installing various types of custom installations, such as custom OneUI, AOSP or Google ROM.
It may happen that you want to go back to the original firmware of our Samsung, after trying various custom ROMs, after having rooted and modified the recovery, missing with the phone partitions, lost EFS folder or corrupt IMEI. The reasons can be many. This guide is aimed at all those who, with the classic Odin procedure to install the stock rom, are unable to restore the phone to normal operating conditions.
But it can happen to fail in this thing, even using Odin to put back the original software, Odin himself or the phone can crash to the BOOT partition or generate other errors, with VBMeta or generic errors, including partition ones.
So let's see how to solve all the inconveniences due to modding on our Samsungs to 99%. Let's begin!
- MATERIAL REQUIRED:
Latest version of Frija link
Latest version of Odin link
Samsung USB Driver link
File Manager zip (example 7zip) link
PC with Microsoft Windows 7-8-8.1-10-11
USB type C cable
1 - Download the latest stock firmware for our Samsung:
Download the latest version of Frija and once the program has started, enter the model code of your device and the abbreviation of your CSC.
Make sure the "Auto" checkbox is checked.
Once you have checked everything, click on "Check Update" and click on "Download". Wait for it to download.
View attachment 5628035
Once you have downloaded the zip containing the various parts that make up the stock software (see image below), extract it to a folder of your choice. We will have 5 files in total.
View attachment 5629259
2 - Retrieve the original PIT file
To recover the PIT file (partition list) for our device, go to the firmware folder you just downloaded with Frija, locate the "tar.md5" file with the words CSC_OXM_N............., right click on the it and select rename, adding ".zip" at the end to "transform" it into a compressed file that can be opened. This way you will have something like
"CSC_OXM_N975...............REV01_user_low_ship.tar.md5.zip"
Give the Ok and confirm the change of the file extension.
You should now have the same situation as you see in the image below. Total 5 files of which one is a ".zip" files.
View attachment 5629261
Now open the file you just renamed with 7zip, the main window of the 7zip program will open with various files inside:
View attachment 5628037
Now copy the "D2S_EUR_OPEN.pit" file by right clicking and selecting the "copy to ..." item and giving the ok without changing anything. The .PIT file will be copied to the same folder as the previously downloaded firmware.
View attachment 5629463
Once this is done, the folder that appears will look like this (Now, the total files are 6 of which one is a ".zip" files):
View attachment 5629465
Now just put the CSC_OXM ... file back to the previous condition, renaming it one more time and eliminating the ".zip" extension at the end of the name, in order to find an MD5 file again. This will be the file we will have:
"CSC_OXM_N975...............REV01_user_low_ship.tar.md5."
Now we have everything we need. If we have done everything correctly this is the final result (Total 6 files).
View attachment 5629265
3 - Prepare and Configure Odin
Now open the latest version of Odin (as of May 2022 the latest version is 3.14.4), load the corresponding downloaded firmware files in the various slots (BL, AP, CP and CSC) as usual.
In the CSC box, upload the file labeled "CSC_OXM_N975 ............... REV01_user_low_ship.tar.md5."
Once this is done, move (still in Odin) to the "Option" tab and check the following items:
Auto Reboot
Nand Erase
Re-partition
F. Reset time
The rest of the items MUST NOT BE SELECTED!
View attachment 5628039
Again in Odin, this time go to the PIT tab, a warning message will appear, give the ok and select the first extracted file which has the unique name "D2S_EUR_OPEN.pit"
If you have done everything right you should have the same situation as the image below:
View attachment 5628043
View attachment 5628045
4 - Return the phone to the original firmware
Connect the USB type C cable to your phone and restart your phone in "Download mode" (check the right combination for your model), or use the Custom Rom to do this, usually all coustom roms or custom recovery offer reboot in Download mode (or Booloader).
In odin in the "Log" tab, you should see the word "Added" with the number of the port to which it is connected (example "0: [COM3]"), if so, press the START key of Odin and wait for the restart (this procedure will delete all data on your device).
If nothing appears, install the Samsung USB drivers and repeat step 4.
View attachment 5628041
5 - Relock the BootLoader
To get rid of that fatal warning message when starting the phone that tells us that the BootLoader is unlocked once and for all, let's put it back in place, relocking the BootLoader.
View attachment 5629449
(Image for demonstration purposes)
Turn off the phone, reconnect the USB cable and immediately press the Volume + and Volume- keys at the same time.
Return to Download mode (albeit a little different), with various options (actually only 3).
In this case, follow the second option (Volume up long press: Device unlock mode) hold down the Volume + key for a few moments until the message "Lock Bootloader?" Appears. To confirm everything, make a single click on Volume + (also in this case the phone will be formatted by the system again) and wait for a complete restart.
6 - Relock OEM (optional but recommended if you want to stick with the Samsung ROM)
Once your phone has restarted and the initial setup is complete, you can also disable the OEM unlock capability and reuse the security features.
To do this, go to Settings / Phone Information / Software Information and tap several times on the wording "Build version" in order to unlock the "Developer options". If prompted, unlock your smartphone with your PIN or sign.
Now go back to the main Settings page, open the Developer Options and check that the "OEM Unlock" item is disabled, otherwise disable it and restart the device.
View attachment 5629493
Well now you have your Samsung with Original firmware again. Enjoy
Click to expand...
Click to collapse
Hi there. I tried it and didn't work for me.
Tried with differents CSC too, but my phone doesn't start the system. Just starts the download and recovery mode
It doesn't even show up the charging screen when powered off
Tried so many things and I can't boot my system...
I made a post with the info about what happened:
Need help with semi-bricked Note 10 Plus (SM-N975F) - Stuck on recovery/download mode
Didn't know where to post this exactly, to be honest. This will be a long post I was flashing AOSP roms in the phone. Tried to go back to One UI for the VoLTE thing In one of the AOSP roms I couldn't install it in Lineage Recovery (older version...
forum.xda-developers.com
Please help...

Ok, tell me where you get stuck ... or can you follow the whole guide but then the phone doesn't start?
Is the model number of your Note10+ is SM-N975F?
What original CSC did you have before you root?
RedSpikeJr said:
Hi there. I tried it and didn't work for me.
Tried with differents CSC too, but my phone doesn't start the system. Just starts the download and recovery mode
It doesn't even show up the charging screen when powered off
Tried so many things and I can't boot my system...
I made a post with the info about what happened:
Need help with semi-bricked Note 10 Plus (SM-N975F) - Stuck on recovery/download mode
Didn't know where to post this exactly, to be honest. This will be a long post I was flashing AOSP roms in the phone. Tried to go back to One UI for the VoLTE thing In one of the AOSP roms I couldn't install it in Lineage Recovery (older version...
forum.xda-developers.com
Please help...
Click to expand...
Click to collapse

ExileTM said:
Ok, tell me where you get stuck ... or can you follow the whole guide but then the phone doesn't start?
Is the model number of your Note10+ is SM-N975F?
What original CSC did you have before you root?
Click to expand...
Click to collapse
I followed the full guide, but I got stuck after flashing the firmware in Odin. It shows the screen of "Erasing data", and after that, nothing more
Even after locking again the bootloader
And yes, I ticked what's needed in Odin and used the .pit file
My model it's SM-N975F
The original CSC it's ZTO. Flashed the latest firmware

Ok so with Odin it didn't give you any problem. Let's say he freezes when he does the first boot that does the factory reset. Right?
Well odd, because once the original firmware is installed, I don't see why it should crash on boot ... unless there is a hardware problem in the phone's internal memory.
I know it may sound trivial, but the usb cable you use is good and did you use the latest version of Odin?
Have you checked maybe if the internal memory is right for you. If it is 256Gb or 512Gb

You could try this, if you see that it does not start try to enter the recovery (the original one) and delete everything you can, like cache and do a reset data directly from the recovery. Then try restarting and see if it starts.

If it still doesn't boot, try this thing.
Install TWRP custom recovery and enter once installed.
Go to Wipe Section in TWRP, Repair or Change partition, System and Data, and Changed Ext4 to EXTFAT. And changed back to Ext4. Eventually rerun the guide again.

ExileTM said:
Ok so with Odin it didn't give you any problem. Let's say he freezes when he does the first boot that does the factory reset. Right?
Well odd, because once the original firmware is installed, I don't see why it should crash on boot ... unless there is a hardware problem in the phone's internal memory.
I know it may sound trivial, but the usb cable you use is good and did you use the latest version of Odin?
Have you checked maybe if the internal memory is right for you. If it is 256Gb or 512Gb
Click to expand...
Click to collapse
The USB it's the original from Samsung.
The device is 256GB
ExileTM said:
You could try this, if you see that it does not start try to enter the recovery (the original one) and delete everything you can, like cache and do a reset data directly from the recovery. Then try restarting and see if it starts.
Click to expand...
Click to collapse
Tried this already. Didn't work
ExileTM said:
If it still doesn't boot, try this thing.
Install TWRP custom recovery and enter once installed.
Go to Wipe Section in TWRP, Repair or Change partition, System and Data, and Changed Ext4 to EXTFAT. And changed back to Ext4. Eventually rerun the guide again.
Click to expand...
Click to collapse
I tried this but not in the process of "Do the format and then do the Odin process" so I can try
I'm trying now with USB OTG to know if I can flash the system.img (and know if from there I can solve this)

ExileTM said:
If it still doesn't boot, try this thing.
Install TWRP custom recovery and enter once installed.
Go to Wipe Section in TWRP, Repair or Change partition, System and Data, and Changed Ext4 to EXTFAT. And changed back to Ext4. Eventually rerun the guide again.
Click to expand...
Click to collapse
Tried from reset data on official recovery to doing the change of format in TWRP and the doing all of the process again. No success.
Also tried with USB OTG with system, vendor, product and boot image. Neither
One thing that happened is that when trying to change the system partition to exFAT, it gave an error (system is not mounted) but changed the format to vFAT. Changing it to another option doesn't give that error, so I tried to do with another option and back to ext4.
I don't think it's a physical issue, if turns on, there is some hope at least

There is almost certainly a solution to your problem. (have you tried to do "format data" and typed "yes" in TWRP recovery?). Anyway, it's night at my place now, I'll see tomorrow to think of some other solution.

Tried already. Also tried to format the data with fastboot (Lineage Recovery gives the option to fastboot in Samsung)

I have the exackt same problem with my note10+ with 256GB and dual sim. and the problem you describe is also 100% what i experienced and still have as an issue... If you get to the point where you can solve the issue then please write me my friend. I will do the same ofcourse... btw can you use your pen in TWRP? i can only mark the files but not click them to run...? i have the idea that the TWRP for our model isnt built right somehow..

I assume you haven't solved the problem yet. In these days I have looked around but I have not found much ...
I saw a video, which through the ADB shell a guy was able to find the list of all partitions with the numbers of all the blocks and information and practically managed to rebuild the system partition from scratch, but I don't know if it works on samsung.
This is video:
Then another thing, what procedure did you follow for rooting? You may have had problems during the rooting process.
I followed this guide:

To update the situation
The battery of the phone inflated like a balloon, so I needed to go to a technician. I don't know for sure if that was caused by something physical, but will update when have some news

Ok, let me know if the technician can get you to restart the phone, and out of curiosity, he can bring the knox back to 0.

Hi, I was trying this today and I'm stuck at "An error has occured while updating the device software."
Odin was stuck at product.img for over an hour so I restarted the phone using volume down and power.
I tried again and it keeps getting stuck at product.img while the phone shows this error. Please could you help me out?
I followed all the steps exactly as you said, but I noticed while in download mode that it showed Warranty Void: 1
I did not root the phone, only flashed Pixel Experience and now trying to go back to OneUI

aaaajwedk said:
Hi, I was trying this today and I'm stuck at "An error has occured while updating the device software."
Odin was stuck at product.img for over an hour so I restarted the phone using volume down and power.
I tried again and it keeps getting stuck at product.img while the phone shows this error. Please could you help me out?
I followed all the steps exactly as you said, but I noticed while in download mode that it showed Warranty Void: 1
I did not root the phone, only flashed Pixel Experience and now trying to go back to OneUI
View attachment 5647587
Click to expand...
Click to collapse
Hello, then, the Warranty Void at 1 is triggered when you install a non-original firmware (in this case the PixelExperience), or when you change Recovery (ex: the TWRP) or you run the ROOT.
Any other software that is not in original firmware triggers the Knox to 0x1 irreversibly.
In your specific case, by installing the LineageOS Recovery and the PixelExperence ROM you have triggered the Knox at 0x1.
I am sorry.
Coming to your problem, the model of your phone what it is (ex: SM-N975F) and the CSC (ex: ITV). Did you download the original software for your exact model? Did you extract the PIT file from the original firmware and put it in the Option tab in Odin?

ExileTM said:
Hello, then, the Warranty Void at 1 is triggered when you install a non-original firmware (in this case the PixelExperience), or when you change Recovery (ex: the TWRP) or you run the ROOT.
Any other software that is not in original firmware triggers the Knox to 0x1 irreversibly.
In your specific case, by installing the LineageOS Recovery and the PixelExperence ROM you have triggered the Knox at 0x1.
I am sorry.
Coming to your problem, the model of your phone what it is (ex: SM-N975F) and the CSC (ex: ITV). Did you download the original software for your exact model? Did you extract the PIT file from the original firmware and put it in the Option tab in Odin?
Click to expand...
Click to collapse
Hello, I got it working just now by using a different cable and USB port. The procedure completed and the phone restarted by itself, and now its perfectly fine. Thank you so much for your help.
Yes, the phone is an SM-N975F. Despite Knox being tripped, my banking and payment apps are still working so I'm happy
I'm sure your article will be helpful to many more users. Thank you!

aaaajwedk said:
Hello, I got it working just now by using a different cable and USB port. The procedure completed and the phone restarted by itself, and now its perfectly fine. Thank you so much for your help.
Yes, the phone is an SM-N975F. Despite Knox being tripped, my banking and payment apps are still working so I'm happy
I'm sure your article will be helpful to many more users. Thank you!
Click to expand...
Click to collapse
OK well. Glad it was helpful. Yes, however, until you root all the apps will work. The only one are some applications by Samsung that will no longer work because they are based on the knox.
Otherwise like Google Pay, all banking and account apps, software updates should work smoothly.

Hi, is this guide usable for the S22 snapdragon version? My device is rooted, and I want to back to original firmware.