Database Develop

Method: Downgrade from Gingerbread (XXJVK) to Froyo (XXJPY)

Like many I installed the leaked version of Gingerbread on my Galaxy S when it first came out, but now Samsung have finally released Gingerbread in the UK, I would like to install the official release. But need to reinstall the official version of Froyo in order to do this via Kies.
I have had to spend quite a large amount of time looking for the process of doing this, as there seems to be conflicting information/methods out there. Also I understand Gingerbread has a new boot loader (the installed the version including the secondary boot loader) which also needs taking back to original, and I have also found that most of the guides out there always seem to leave a few questions unanswered
So after finding what appears to be the best and I believe the safest method, I thought I would post it on here for others.
Before I go into the steps on how i did this, I need to make a few points:
1) Any firmware installation carries risks. This is not approved by Samsung, and you do it entirely at your own risk....i’m no expert, I simply found a method that works for me. So if it all goes wrong, don’t come crying to me (however, after trying a different method previously, my phone would not boot, but I was able to re-flash with the leaked Gingerbread successfully).
2) Do not try this procedure if you are unable to get your Galaxy S into Recovery mode (Vol Up + Home + Power) and Download mode (Vol Down + Home + Power). A number of these phones have this issue, mine was one of them, there are guides online to fix this issue.
3) There seems to be a number of people who have issues with upgrades on Kies even when they haven’t messed with the firmware, so even if you cannot upgrade thru Kies, it doesn’t mean there has been a problem with Flashing the phone.
4) Backup your phone before flashing, as the phone will be wiped.
5) As far as I understand, this is only for the I9000 model and not for any of the other variants of this phone out there.
6) NEVER try to flash the phone without putting it into Download mode first, you will brick your phone.
------------------------------------------
First of all you will need a Windows PC, USB Cable, 2 Downloads (below)....oh and ideally a Samsung Galaxy S
Download 1 (JPU)
http://hotfile.com/dl/99955459/dea6962/I9000XXJPU.rar.html
Password: samfirmware.com
Contents when extracted:
GT-I9000-CSC-MULTI-OXAJPU.tar.md5
I9000XXJPU-REV03-PDA-low-CL747761.tar.md5
MODEM_I9000XXJPU.tar.md5
s1_odin_20100512.pit
Odin3v1.3
Download 2 (JPY)
http://www.megaupload.com/?d=EWTHLRU6
No Password
Contents when extracted:
JPY_JPY_JPY.tar
The idea is to flash with XXJPU first to get the base version of Froyo which includes the SBL, then to Flash with JPY, this will allow you to use Kies for firmware updates (ensure Kies is completely closed before starting this).
1. Download and extract the above files.
2. Power off phone, remove sim and memory card, then start up in Download Mode and plug USB cable into phone (not PC).
3. Open Odin and select the following Files:
PIT: s1_odin_20100512.pit
PDA: I9000XXJPU-REV03-PDA-low-CL747761.tar.md5
PHONE: MODEM_I9000XXJPU.tar.md5
CSC: GT-I9000-CSC-MULTI-OXAJPU.tar.md5
Ensure the following options are ticked: Re-Partition, Auto Reboot & F.Reset Time
4. Plug the USB into the PC, after a few seconds it should displayan “Added” message in Odin, then click on the ‘Start’ button.
The JPU firmware will then be installed onto the phone, it will take a few minutes and the phone will reboot.
***Under no circumstances unplug the usb cable, press any buttons on the phone or generally do anything that could interrupt the process, until it has complete and the phone is full restarted***
Once this is complete, you are ready to flash the phone with the JPY version, very similar process, but please read as not all of Odin settings are the same.
5. With USB unplugged from PC, power off the phone and restart in Download mode.
6. Re-open Odin and select the following files:
PIT: s1_odin_20100512.pit
PDA: JPY_JPY_JPY.tar
Ensure the following options are Ticked: Auto Reboot & F.Reset Time (NEVER tick ‘Re-Partition’ when using a single firmware file for flashing as this could Brick your phone)
7. Plug the USB into the PC, after a few seconds it should displayan “Added” message in Odin, then click on the ‘Start’ button.
The Firmware will then be installed onto the phone, it will take a few minutes and the phone will reboot.
And thats it, you should now be able to upgrade the firmware via Kies....that’s assuming Kies is working correctly, and your carrier has released it, i’m with T-Mobile UK, but bought my phone through the Carphone warehouse, and was able to update immediately.
--------------------------------------------------------------------------
I hope this has been helpful, if you have any queries, I will try to answer, but as I said I am no expert, i've simply spent alot of time looking for the best method

Just thought I should point out that xxjpy is a european version and is not carrier specific. So it shouldn't matter if your carrier has released gingerbread yet.
This method will allow kies to update your phone to the lastest european firmware.

Why the pain?
No need to go through all this downgrading palava any more. Just use *spooffw and upgrade via kies as normal...easy peasy and no flashing required.
Search for "kies spoof"
*it fools kies into thinking you're on older firmware and offers you the upgrade to current fw

Don't need to tick "update bootloader"?

No, only tick the options stated in the guide.
Also be aware that you do not tick "Re-partition" on the second flash (JPY)
Sent from my GT-I9000 using Tapatalk

Thanks for the guide! I flashed it from a branded FW (was a backup) to stock and until now it's all pink and fuzzy!

Thank you, that's what i was looking for.

I never realized there was a written guide for this.
I just posted a video yesterday on how to debrand, unroot, and then update via kies.
Thus going from any custom kernel/rom theme etc.. to:
JPU, JPY then updating your version via KIES to JVO - good for warranty purposes.

thanks for this guide

Thanks for this guide. I was on JVO (samfirmware) and wanted to downgrade to get the official latest version installed later.
It didn't fully work for me but eventually got it working.
After having flashed from JPU to JPY Kies detected the phone (did not on JPU). However, it said there is no newer firmware version available.
So I flashed I9000XXJQ3_XXJPY_DBTJS2\PDA_JQ3.tar.md5 as PDA and I9000XXJQ3_XXJPY_DBTJS2\CSC_DBT_JS2.tar.md5 as CSC which I got from samfirmware (these were the versions I used to have on my SGS originally from Kies when I was still on 2.2.1).
*edit April 2012:*
had to downgrade again and went same procedure. However, couldn't remember whether I also flashed "phone". So this time I also added I9000XXJQ3_XXJPY_DBTJS2\PHONE_JPY.tar.md5 as PHONE in addition to the files I listed above as well as I ticked re-partition and added the same pit file I used on the first two flashes.
Afterwards, Kies detected the phone and offered the upgrade. Did that and now it has PDA: JVI, PHONE: JVO, CSC: JV2 (DBT)
*edit end*

cookm75 said:
The JPU firmware will then be installed onto the phone, it will take a few minutes and the phone will reboot.
Click to expand...
Click to collapse
How long is a "few minutes"? Odin has been at the following stage for just over half an hour now...
<ID:0/011> SetupConnection..
<ID:0/011> Initialzation..
<ID:0/011> Set PIT file..
<ID:0/011> DO NOT TURN OFF TARGET!!
My phone doesn't appear to be doing anything and just has the yellow/luminous green android figure digging with "Downloading..." beneath it and "Do not turn off Target!!!" showing on the screen.
Should it be taking this long?
I have a Samsung Galaxy S I9000 that was on GB 2.3.4, but due to excessive battery draining, and the phone locking up on a black screen with the only way to recover being to remove battery, it was suggested to me at Carphone Warehouse to try flashing it back to Froyo.

No I had the same issue. From what I understand if there are no file names under the do not turn off target line and no blue progress bar on the phone then you waited too long from connection to flashing. Get everything ready and then connect the phone and start.
Nothing has been done yet at the stage you mention.
G
Sent from my GT-I9000 using XDA Premium App

Just pull out the battery, boot into download mode again and try flashing once more, it will pass successfully this time.
Sent from hell to take your soul

Thank you both gfacer & Lunchbox115.
I have now successfully flashed my phone with Froyo and then re-upgraded to Gingerbread through Kies.
I'm keeping my fingers crossed that the problems my phone was having have now been solved.

thanks, very useful information.

This may be a dumb question, but anyway... Does this whole thing works for samsung galaxy mini? If yes, do you need to unroot it if you already have it rooted.

[Q] Difficult "soft" brick

Hey, guys, long time lurker and first time posting here.
So, I managed to screw up my S4 Active (i9295, international version) somehow and I am out of things to try now.
I have been testing lots of roms and have always been successful using Odin. Never had any problems with it, got quite familiar with the notions of it all.
So tonight I tried to go back to the original stock rom of my phone, and I got a FAIL error at Odin. After that, I just could not flash any other ROM on it for the life of me. I tried the ROM I had just before, fail. Tried a ROM I used some time ago, fail. It seems it fails to flash any rom to it, it always giver an error at the very end of the process.
I CAN:
- flash CWM to it - it works normal
- flash root to it - although i dont really see the point
- access "odin"/download mode
- access cwm recovery
I CAN'T:
- manage to flash stock rom to it
- it always fails at the very end, right after the modem.bin
- Complete(Write) Operation Failed
I already tried:
- changing usb ports
- 3 different stock roms downloaded from sammobile
- closing every single app remotely similar to kies on windows
- reinstalling the samsung android drivers
- removing sim card and external sd card
- wipe data/cache prior to flashing
I'm running out of ideas here. Anyone got any solution I might have skipped?
Thanks and sorry for the long post.

Oh, I also tried getting the firmware using KIES.
It doesn't recognize the phone (just says "Connecting") and it doesn't show on the list for the Emergency firmware recovery.
I also tried the "Firmware upgrade and initilazation" mode, which I have used in the past.
It downloads the firmware, goes to the next step, but when it gets to the part where it sould instruct me to put the phone in download mode, it just shows a warning completely in japanese (probably korean actually, considering... thanks, Samsung! :good: ) and it stops the whole thing.

Downgrading from Nougat

I goofed and updated my Verizon Galaxy S6 Edge (32gb) to Nougat. I'd like to attempt downgrading it back to 6.01 (Marshmellow?) I'm new to modifying my cell phone and would like to outline what I think I should do, and hopefully someone with experience will catch any goofs before they occur.
General Information:
G925V
Build # G925VVRS4DQD1
Hardware # G925V.04
1. Downloaded Samsung Switch, backup everything I can. This step should also place the samsung usb drivers on my pc? (window 10 64bit)
2. Prepare phone? Little foggy on this step, some guides recommended factory restore and erase cache partion first. Remove Sim card.
3. Download firmware from sammobile, I downloaded G925VVRS4CQA3, newest available 6.01. Does it matter that the last four digits don't match the last four of my Build #?
4. Put phone in download mode (reboot, home+power+volume down, volume up to accept)
5. Open Odin (v3.12.5) verify .tar file. I saw the AP file that needs pulled over, guessing there might be other files, firmware download still going.
6. Connect phone, check connection in upper left window of Odin hit start and don't unplug anything
7. When Odin finishes, reboot phone into Recovery mode, select factory reset all user data?
Am I overlooking anything major?
Thanks,
Cole

coleauden said:
I goofed and updated my Verizon Galaxy S6 Edge (32gb) to Nougat. I'd like to attempt downgrading it back to 6.01 (Marshmellow?) I'm new to modifying my cell phone and would like to outline what I think I should do, and hopefully someone with experience will catch any goofs before they occur.
General Information:
G925V
Build # G925VVRS4DQD1
Hardware # G925V.04
1. Downloaded Samsung Switch, backup everything I can. This step should also place the samsung usb drivers on my pc? (window 10 64bit)
2. Prepare phone? Little foggy on this step, some guides recommended factory restore and erase cache partion first. Remove Sim card.
3. Download firmware from sammobile, I downloaded G925VVRS4CQA3, newest available 6.01. Does it matter that the last four digits don't match the last four of my Build #?
4. Put phone in download mode (reboot, home+power+volume down, volume up to accept)
5. Open Odin (v3.12.5) verify .tar file. I saw the AP file that needs pulled over, guessing there might be other files, firmware download still going.
6. Connect phone, check connection in upper left window of Odin hit start and don't unplug anything
7. When Odin finishes, reboot phone into Recovery mode, select factory reset all user data?
Am I overlooking anything major?
Thanks,
Cole
Click to expand...
Click to collapse
1.) From http://www.samsung.com/us/support/smart-switch-support/#!/faqs "The first time you connect your Samsung device to your computer, it will automatically locate and install the necessary drivers. (This process can take a few minutes to complete.) After the drivers are installed, the device will appear in the Smart Switch application.
If the drivers do not install automatically, go to the Samsung Support site and visit your device's support page. Click Manuals & Downloads to download the drivers for your device."
2.) Yeah, I am guessing prepare phone means prepare for total data loss (lol) when you perform a wipe data/factory reset from the recovery mode/menu (which formats /data, /cache and /sbfs partitions).
3.) The last 4 digits are different because you are on the first build of Nougat now (DQD1).
I have no experience with Odin myself, but I do know there are checkboxes, options and such you should do research on beforehand. For example, on sammobile's download page there are instructions saying "Make sure re-partition is NOT ticked" so just saying as there may be special procedures involved specifically when downgrading.
Another potential problem: have you found confirmation that you can downgrade -directly to- the last Marshmallow 6.0.1 build available for this phone (CQA3) -from- Nougat 7.0 (DQD1) and are you sure about it? There is a chance you may need to downgrade to an earlier build first.
Also I've had a strange experience with sammobile, as I downloaded the Nougat firmware for this phone and it is -completely- different (name, size, hash, modified date far before the public release) from other Nougat firmware I downloaded.
I recommend for any firmware build you decide to use: download from multiple sources and compare/verify with HashMyFiles or similar software to make sure it is really what they say it is.
I am awaiting response from a question for this OP; you should check it out as he mentions downgrading and provides download links (note: CQA3 is -not- in the list). https://forum.xda-developers.com/ve...25vvrs4dqd1-odin-nougat-7-0-firmware-t3597591

Thank you for the information @blkt

coleauden said:
Thank you for the information @blkt
Click to expand...
Click to collapse
You can thank me with the "Thanks!" button on my post.

Dying to know if this worked??

SpyderPalo said:
Dying to know if this worked??
Click to expand...
Click to collapse
It worked. I did end up with a bootloop bouncing between the Verizon Screen and the Samsung screen that caused a few grey hairs. Eventually I was able to get into Recovery mode and performing data and cache resets allowed me to power on fully. I had performed a cache reset before starting the downgrade process, but not a data/factory reset. I also had the sim card removed. Either of those might have contributed to the bootloop. First action after google and Samsung account login was running BK Package Disabler and blocking the two sdm packages to hopefully prevent Nougat notifications (process contributed by @wolferno ).
Some information if it helps:
*Odin version was 3.12.5.
*Firmware version was G925VVRS4CQA3_G925VVZW4CQA3_VZW from sammobile (highest 6.01)
Backup was through Smart Switch, to get it running again I had to activate Developer options, enable USB Debugging, and under USB options enable MTP.
Hope this helps!

I have successfully downgraded from Nougat on my G925V 64gb
I used the stock software G925VVRS4CQA3_VZW4CQA3_VZW_USA_Verizon_6.0.1.
I downloaded from AndroidFileHost did the md5 check
It did boot-loop between Verizon and Samsung
Pressing and holding the Volume-down then Power button brought up the Factory reset (DOS-like) screen where I could do another factory reset to get the phone to boot up into setting up the phone starting with logging into the Samsung account.
I had activated another phone before this process so I could still get and make calls if it bricked, I've signed into my Gmail account that I have all apps and setting's saved.
I will be installing a Package Disabler as soon as the apps finish loading and before I activate the phone back onto Verizon.
Much thanks to coleauden for answering a PM and blkt for clarifying with coleauden earlier!!!
Enjoy the Day,
David

SpyderPalo said:
I have successfully downgraded from Nougat on my G925V 64gb
I used the stock software G925VVRS4CQA3_VZW4CQA3_VZW_USA_Verizon_6.0.1.
I downloaded from AndroidFileHost did the md5 check
It did boot-loop between Verizon and Samsung
Pressing and holding the Volume-down then Power button brought up the Factory reset (DOS-like) screen where I could do another factory reset to get the phone to boot up into setting up the phone starting with logging into the Samsung account.
I had activated another phone before this process so I could still get and make calls if it bricked, I've signed into my Gmail account that I have all apps and setting's saved.
I will be installing a Package Disabler as soon as the apps finish loading and before I activate the phone back onto Verizon.
Much thanks to coleauden for answering a PM and blkt for clarifying with coleauden earlier!!!
Enjoy the Day,
David
Click to expand...
Click to collapse
Nice, I didn't realize CQA3 was on AndroidFileHost as well. Which Odin version did you use? Did you remove your sim card? BTW, I think you meant Home/Volume Up/Power for recovery mode (the DOS-like menu) because volume down would put you into download mode. In recent months there have been reports (on google play reviews) of Package Disabler Pro removing the ability to disable certain packages at the request of Samsung (removed from package list, no changelog either). Maybe this has changed; I have not investigated further but there's also BK Package Disabler. Here is a helpful page with all Odin versions. http://www.droidviews.com/download-odin-tool-for-samsung-galaxy-devices-all-versions/

blkt said:
Nice, I didn't realize CQA3 was on AndroidFileHost as well. Which Odin version did you use? Did you remove your sim card? BTW, I think you meant Home/Volume Up/Power for recovery mode (the DOS-like menu) because volume down would put you into download mode. In recent months there have been reports (on google play reviews) of Package Disabler Pro removing the ability to disable certain packages at the request of Samsung (removed from package list, no changelog either). Maybe this has changed; I have not investigated further but there's also BK Package Disabler. Here is a helpful page with all Odin versions. http://www.droidviews.com/download-odin-tool-for-samsung-galaxy-devices-all-versions/
Click to expand...
Click to collapse
Maintenance Boot Mode is what I get into with holding Down volume and holding Power button.
Odin 3.12.5
De-activated SIM still in the phone (activated a iphone for calls)
I ended up buying BK Package Disabler to block the OS upgrade/update.

SpyderPalo said:
Maintenance Boot Mode is what I get into with holding Down volume and holding Power button.
Odin 3.12.5
De-activated SIM still in the phone (activated a iphone for calls)
I ended up buying BK Package Disabler to block the OS upgrade/update.
Click to expand...
Click to collapse
Oh wow, another mode I was not aware of. Thanks! This one is good to know because it is apparently accessed when the phone is still on. Confusing though, because I though volume down + power was to force reboot. The recovery mode I mentioned is done after the phone is off.

blkt said:
Oh wow, another mode I was not aware of. Thanks! This one is good to know because it is apparently accessed when the phone is still on. Confusing though, because I though volume down + power was to force reboot. The recovery mode I mentioned is done after the phone is off.
Click to expand...
Click to collapse
Sorry I didn't clarify......
I pressed the 2 buttons once the phone was off...
In all the times I have ever had to get into the lower (Root) areas of the phone , I've started with the phone off so I assumed this was a known practice.
Apologies

SpyderPalo said:
Sorry I didn't clarify......
I pressed the 2 buttons once the phone was off...
In all the times I have ever had to get into the lower (Root) areas of the phone , I've started with the phone off so I assumed this was a known practice.
Apologies
Click to expand...
Click to collapse
Oh, I thought you used it to get out of the boot loop. No worries, as this video put my brain through a boot loop. https://www.youtube.com/watch?v=9N5Q8RD5QPs

You should be able to downgrade to any firmware that is Revision/Binary 4.
You started with 4DQD1 right?
You should be able to downgrade to any firmware with like 4A, 4B, 4C, 4D, etc.

Galaxy S10 bootloop after updte to Android 10

This morning I saw that I can update to the new Android 10 version on my Galaxy S10.
I was happy and of course updated directly.
Everything worked fine, the update was downloaded, installed and the phone rebooted.
And from there it hung in a boot loop.
I had already unlocked the bootloader 2 months ago, but only to flash the original firmware again because of an unsuccessful attempt to install TWRP.
Now the Galaxy S10 starts up, shows the information that the boot loader has been unlocked and then the boot logo and vibrates.
Then it goes straight off and starts again.
I cannot use the key combinations to get into the recovery or in the download mode.
How can I solve this problem ?
(Sorry for my bad englisch i come from germany)

You can try following:
Plug your phone in the PC with the USB cable. Then press/hold Bixby + Volume Down and hopefully it will boot to download-mode.
Otherwise try (still plugged in) force shutdown/restart by pressing/ holding Volume Down + Power - as soon as the screen turns off shift to pressing/ holding Bixby + Volume Down for download-mode. Try it at few times as its all about timing.
If still no luck, unplug your phone and let the battery run out. Then press/hold Bixby + Volume Down and plug in to get to download-mode. This may take some time as the phone needs to recharge a little before it reacts.
Once in download-mode flash your software before the update via Odin - I would use Home_CSC first trying to save your data.

Got exactly the same problem today. Don't know which one I flashed in november though
So how to keep (maybe) the data? flash only HOME_CSC?

nikolaus2007 said:
Got exactly the same problem today. Don't know which one I flashed in november though
So how to keep (maybe) the data? flash only HOME_CSC?
Click to expand...
Click to collapse
Yes to using Home_CSC but to be safe I would flash all 4 files (AP - BL - CP - HomeCSC) as some people have reported their storage gets corrupted/ shows wrong capacity.
Use either Samsung 10 (BSKO) or latest Pie (ASJG). Both should be ok as you are flashing the bootloader when using all 4 files.

Norup58 said:
You can try following:
Plug your phone in the PC with the USB cable. Then press/hold Bixby + Volume Down and hopefully it will boot to download-mode.
Otherwise try (still plugged in) force shutdown/restart by pressing/ holding Volume Down + Power - as soon as the screen turns off shift to pressing/ holding Bixby + Volume Down for download-mode. Try it at few times as its all about timing.
If still no luck, unplug your phone and let the battery run out. Then press/hold Bixby + Volume Down and plug in to get to download-mode. This may take some time as the phone needs to recharge a little before it reacts.
Once in download-mode flash your software before the update via Odin - I would use Home_CSC first trying to save your data.
Click to expand...
Click to collapse
Thanks!
I got into the download mode.
I used SamFirm to download the firmware but it was Android 10
Right now i am downloading Andoid Pie from updato.com...
No premium, i am just a free member, so it shows me "20 Hours left"
Where can i download the latest SM-G973F Germany (DBT) Android Pie Firmware for free and without that high speed restriction ?
I think i have to put the home_csc file into the CSC field in odin ?

Didn't work for me, neither ASJG (Pie) nor BSKO (Q).
Had to wipe data, beause system nerver booted again.
Lost all my data. Congrats Samsung to this very best update mechanism. Nerver had on any Nexus nor OnePlus.
Maybe you have more luck.

download mode its not opening idk what i need to do im gonna lose my mind ( sorry for my bad english )

c_j_k said:
Thanks!
I think i have to put the home_csc file into the CSC field in odin ?
Click to expand...
Click to collapse
Yes!
maxmelax said:
download mode its not opening idk what i need to do im gonna lose my mind ( sorry for my bad english )
Click to expand...
Click to collapse
Have you tried all 3 of my suggestions listed above?

Norup58 said:
Yes to using Home_CSC but to be safe I would flash all 4 files (AP - BL - CP - HomeCSC) as some people have reported their storage gets corrupted/ shows wrong capacity.
Use either Samsung 10 (BSKO) or latest Pie (ASJG). Both should be ok as you are flashing the bootloader when using all 4 files.
Click to expand...
Click to collapse
I flashed G973FXXS3ASJG to my Galaxy S10.
First i tried only homeCSC but it was still brick.
Then i flashed only AP, it worked.
But after I set up my smartphone again, I saw that I only have 32 GB of storage even though my Galaxy S10 is the 128 GB version.
Then, as you said, I flashed all four files (AP - BL - CP - HomeCSC).
It still shows me that I only have 32 GB of storage

c_j_k said:
I flashed G973FXXS3ASJG to my Galaxy S10.
First i tried only homeCSC but it was still brick.
Then i flashed only AP, it worked.
But after I set up my smartphone again, I saw that I only have 32 GB of storage even though my Galaxy S10 is the 128 GB version.
Then, as you said, I flashed all four files (AP - BL - CP - HomeCSC).
It still shows me that I only have 32 GB of storage
Click to expand...
Click to collapse
When I first read your post I thought:
Seriously…. Seriously…..
I mean, why the heck would you only flash one file (you were actually warned against this) when it is just as easy to fill-out all 4 slots in Odin? People amaze me!
Okay its Xmas, so back to helping:
‘What you have experienced is a side-effect of using Odin to flash an AP file to your device with the CSC slots left empty. Never flash a full AP file on this range of devices without also filling at least the HOME_CSC slot. It is safe, however, to flash only a recovery image in the AP slot.
To attempt to repair the damage, you need to boot to TWRP, select Advanced Wipe, tick Data, select Repair or Change File System followed by Resize File System. Your /data will return to its former size, but you will probably find you have lost some data.’
Above is quoted from #ianmacd
So, if your phone is on stock Pie (minimum ASIG), with OEM unlocked, try this to get TWRP installed in order to use above rescue.
Go here and download Multidisabler: https://forum.xda-developers.com/ga...ynos/g97xf-multi-disabler-encryption-t3919714
Go here and download TWRP Magisk Patched: https://forum.xda-developers.com/ga...ynos/recovery-twrp-galaxy-s10-magisk-t3919248
Now read post #2 in the TWRP thread for installation guidance…. When you get to no.10 flash the Multidisabler you downloaded instead and then skip to no.12
After no.12 reboot, boot back into TWRP and try the Data fix above.
If all goes well you will have full storage capacity again, TWRP installed and rooted with Magisk.

Norup58 said:
You can try following:
Plug your phone in the PC with the USB cable. Then press/hold Bixby + Volume Down and hopefully it will boot to download-mode.
Otherwise try (still plugged in) force shutdown/restart by pressing/ holding Volume Down + Power - as soon as the screen turns off shift to pressing/ holding Bixby + Volume Down for download-mode. Try it at few times as its all about timing.
If still no luck, unplug your phone and let the battery run out. Then press/hold Bixby + Volume Down and plug in to get to download-mode. This may take some time as the phone needs to recharge a little before it reacts.
Once in download-mode flash your software before the update via Odin - I would use Home_CSC first trying to save your data.
Click to expand...
Click to collapse
i am having the same problem but i cant enter download mode and my pc doesnt recognise the phone to use odin
is there any possible solution to that ? thank you in advance

th3maker said:
i am having the same problem but i cant enter download mode and my pc doesnt recognise the phone to use odin
is there any possible solution to that ? thank you in advance
Click to expand...
Click to collapse
Yeah, I can see you have started a thread with your problem.
If the first two of my suggestions doesnt work for you then you have to let the phone bootloop until the battery dies/ runs dry and then try my third suggestion.

Norup58 said:
When I first read your post I thought:
Seriously…. Seriously…..
I mean, why the heck would you only flash one file (you were actually warned against this) when it is just as easy to fill-out all 4 slots in Odin? People amaze me!
Okay its Xmas, so back to helping:
‘What you have experienced is a side-effect of using Odin to flash an AP file to your device with the CSC slots left empty. Never flash a full AP file on this range of devices without also filling at least the HOME_CSC slot. It is safe, however, to flash only a recovery image in the AP slot.
To attempt to repair the damage, you need to boot to TWRP, select Advanced Wipe, tick Data, select Repair or Change File System followed by Resize File System. Your /data will return to its former size, but you will probably find you have lost some data.’
Above is quoted from #ianmacd
So, if your phone is on stock Pie (minimum ASIG), with OEM unlocked, try this to get TWRP installed in order to use above rescue.
Go here and download Multidisabler: https://forum.xda-developers.com/ga...ynos/g97xf-multi-disabler-encryption-t3919714
Go here and download TWRP Magisk Patched: https://forum.xda-developers.com/ga...ynos/recovery-twrp-galaxy-s10-magisk-t3919248
Now read post #2 in the TWRP thread for installation guidance…. When you get to no.10 flash the Multidisabler you downloaded instead and then skip to no.12
After no.12 reboot, boot back into TWRP and try the Data fix above.
If all goes well you will have full storage capacity again, TWRP installed and rooted with Magisk.
Click to expand...
Click to collapse
Hey Bro, I bricked my phone as well in the morning while updating to android 10 but I just had my bootlocker unlocked but no root on it. Could you tell me if there is any possibility to backup the stuff on my phone? Right not Im waiting for my battery to drain to 0% that I can get into download mode and try something out maybe you have a tip for me

Can someone send me a prepatched magisk ap file for HK 9730 Android 10. I don't know what I did. I just pre patched it myself and flashed with odin just like ANY other update but this time, it gets stuck at Samsung logo. I waited a good while too. Maybe I didn't have the right magisk version which is why I'm asking if someone has a pre patched that works, idk but I don't want to lose my data.

BeastyReedhawk said:
Hey Bro, I bricked my phone as well in the morning while updating to android 10 but I just had my bootlocker unlocked but no root on it. Could you tell me if there is any possibility to backup the stuff on my phone? Right not Im waiting for my battery to drain to 0% that I can get into download mode and try something out maybe you have a tip for me
Click to expand...
Click to collapse
My suggestion is to download the complete stock firmware- be it Pie or 10 (Q) - and then when flashing all 4 files via Odin use the Home_CSC file to try to retain your data.
I use FRIJA to download firmwares as the d/l speed is very good.
Bear in mind, if you at some point intend to root and/or install TWRP your phone will be wiped in the process so backup your stuff before going down that road.

Hi, i have the same problem, i can't access to download mode, i have access to twrp recovery but i can't do anything, if i touch the recovery screen, the phone reboot, have you any suggestion please, to recover my phone?
OK, i find a way accidently!
thks

I am also experiencing this issue that the OP is having with their S10. I also have an S10. There was a software update for my phone and now I wake up to my phone boot looping itself to death.
For someone that lives in the United States, which firmware should I use to recover my phone? I ask because there is like 20+ countries to choose from for the exynos G973F model

Norup58 You saved my life!!!! LOVE YOU. i got into download mode THANKS MAN
LOVE UU

My have a similar problem buh worse... Was updating manually then got the error message.
Tried to put it back into download mode the went into black screen and now doesn't respond to anything. Seems dead

RemixDeluxe said:
I am also experiencing this issue that the OP is having with their S10. I also have an S10. There was a software update for my phone and now I wake up to my phone boot looping itself to death.
For someone that lives in the United States, which firmware should I use to recover my phone? I ask because there is like 20+ countries to choose from for the exynos G973F model
Click to expand...
Click to collapse
Hello,
I have a Samsung Galaxy Note 9 (SM-N9600) that will not boot. So far I have flashed 2 official firmwares with Odin, and on the first boot attempt after flashing, it will show a percentage bar that counts up to around 5 or so percent before skipping to 100 then looping again. It only does the percentage thing on the first boot after flashing. When I try a factory reset from the recovery I get a no pdp scenario error also. I have tried all that I can think of and even took it to a Samsung Service centre but no solution. I would really appreciate any help I can get.

Odin stock flash not working, don't know what else to try SM-N960U

Hello everyone- I hope someone can give me some advice i haven't tried yet on my issue. This is my first post and i searched through a million forums for ideas, my apologies if i missed anything or if anything below is unclear. I tried to list everything out that i have tried in case i missed anything.
Note 9 - SM-N960U (TMB) went into a boot loop randomly (possible after a Samsung update as it happened overnight).
Steps I've taken so far:
- Tried the normal steps first as instructed by Samsung, clear cache-partition, factory reset device etc - still stuck in boot loop.
- Took phone to authorized Samsung service center, they could not fix. phone now on blue screen "An error has occurred while updating the device software. Use the Emergency recovery function in the Smart Switch PC Software"
- Smart switch recovery software would not recognize the phone, updated drivers multiple times, still no detection.
-Downloaded stock TMB firmware from SamMobile (N960USQS9FUG2) - Tried to flash with Odin (versions 3.13 and 3.14 - patched and unpatched) kept getting stuck at vendor.img.ext4 in CSC file or system.img.ext4 in the AP file.
-Tried to Re-Partition without Pit file and with the pit file - PIT file name: CROWNQLTE_USA_SINGLE.pit - Odin would get stuck on same files.
-Tried to re-partition with Nand Erase selected and Pit file attached - Odin would freeze at setting the partition.
Is there anything else i can try or is this phone officially a paper weight?

You are able to flash firmware from the emergency screen. When one of my devices did this I was able to get things up and running with Odin flash from that screen. I can't remember what partition was broken when it happened on my Note 8, but the only way to fix was putting in new mother board. I'm not saying go this route. Might try combination firmware. I'm sure someone will chime in if I am wrong. I tried to flash stock on my SM-N950U after being rooted. It would show pass in Odin but would never boot..just bootloader. As I said above my only option was new motherboard. I wish I could find the message from a developer that helps me a ton, and which partition it was that was the issue. If I find it I will let you know.

butchieboy said:
You are able to flash firmware from the emergency screen. When one of my devices did this I was able to get things up and running with Odin flash from that screen. I can't remember what partition was broken when it happened on my Note 8, but the only way to fix was putting in new mother board. I'm not saying go this route. Might try combination firmware. I'm sure someone will chime in if I am wrong. I tried to flash stock on my SM-N950U after being rooted. It would show pass in Odin but would never boot..just bootloader. As I said above my only option was new motherboard. I wish I could find the message from a developer that helps me a ton, and which partition it was that was the issue. If I find it I will let you know.
Click to expand...
Click to collapse
Thanks for the reply @butchieboy, If you find those messages i would definitely appreciate it! I should have specified that i was able to run the Odin flash from the recovery page. That's a good idea to try combination firmware, never done it before though. Would i just try an older AP or CSC with the up to date other files? or just a combination of old and new and see if something happens?
Overall i think i may be in the boat you were in with your Note 8- something seems seriously wrong with the memory partitions that seem like it may be unfixable via flash. i'll have to see if i can find a motherboard that's worth the price to see if it's worth it at this point.

Combo firmware needs be on same bootloader that you are currently on