Database Develop

HELP! Bell i9000m, stuck on boot loop

I have a Bell i9000m. Few months ago, I was running 2.1 and decided to finally update to Froyo (Doc's Rom). Today I decided to upgrade to CM7. I've already upgraded a i9000 international version to CM7 few days ago so I knew what I was supposed to do. I followed every step and successfully flashed speedmod's kernel, back-uped the efs and flashed the cm7 kernel, however when installing the initial package, i got the error something along the line:
E:Error in /mnt/sdcard
I tried to reflash the kernels and still get the same error everytime.
- I decided to revert back and first used Darky's Resurrection but got stuck in a boot loop
- I never got to update to the JL2 bootloader, so i am not sure if i can flash that
- I've searched and used several firmwares from samfirmware, flashed them with re-partition using odin and they get stuck and the screen turns green, white, or blue, and stays there.
I could still get to download mode, but I am not sure what files to flash using odin. Any help is greatly appreciated!
EDIT:
Tried doing it again, flashing UGJG8, and it flashed successfully
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> cache.rfs
<ID:0/003> dbdata.rfs
<ID:0/003> factoryfs.rfs
<ID:0/003> modem.bin
<ID:0/003> param.lfs
<ID:0/003> zImage
<ID:0/003> Removed!!
<ID:0/003> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
However, now it's stuck on a blinking grey circular loading bar, and I am unsure what to do
EDIT2:
seems like it's stuck on a boot loop. once i unplug the phone from the computer, it just continually flashes the boot animation
i think i could still get into download mode and that's it

Help anyone??

Have you tried to flash stock jl2 for the new bootloader since it came out?
Once you flash it's on and you can go to other roms. This secondary boot loader is apparently the fix to our phones. If it doesn't work sounds like it may need a board replacement.
Good luck!

Not yet, I will flash it now. But should I flash the bootloaders as well, since I never updated?
Thank you!

I just had this same thing happen to me , flashin that lil circle or if unplugged from usb flashing boot screen. Lost recovery mode , download mode still working....also bell i9000m about 2 mths old now. I have been trying many combinations to make this work , the phone gets a bit further if you use 513 pit file but still wont completely load....Help

to update i just flashed stock jl2 2.2 on mine with 512 pit file and pda selected and checked off repartition , phone efs clear , phone bootloader update using odin 1.82 and it says success but when it finishes phone comes up with an error in recovery mode about needing to format internal card or something , i try to do it nothing happens so I hit reboot now ...it loads almost all the way than just blackscreens and vibrates until i pull the battery out......
ANY ideas anyone?

Try updating the bootloaders as well. Unfortunately I can't think of too many success stories when you get to this point. If all else fails search for a thread about filing a ccts complaint and bell should ship you a new one. Everyone who submitted got a new phone and credit as far as I know.
Sent from my GT-I9000M using XDA App

updating the bootloaders ? how?

There's a box you can check in odin. apparently the sbl.bin file is what is crucial to save sd cards and once you've flashed jl2 it's always there so you can flash whatever rom you want after.
So far I don't think repartitioning has saved anyone yet either. when I had it happen I had to send mine for repair.
Sent from my GT-I9000M using XDA App

stevenca said:
updating the bootloaders ? how?
Click to expand...
Click to collapse
Did it work?

I don't see the box

stevenca said:
I don't see the box
Click to expand...
Click to collapse
It is the checkbox beside EFS Clear, says Bootloader update
It is beside or under the re-partion, auto-reboot, etc checkboxes depending on your odin version i think

my phone is on its way back to samsung , they can worry about it. It better come back with a good os on it too, bell is killing to many phones here

stevenca said:
my phone is on its way back to samsung , they can worry about it. It better come back with a good os on it too, bell is killing to many phones here
Click to expand...
Click to collapse
Yeah, I'll be giving them a call tomorrow too

Bell may only repair your phone if you call them. Go to this link and you can submit a complaint to the CCTS. Then Bell corporate will call you and ship you a new phone and you send them your broken one back.
If you deal with Bell or Samsung to repair it may take up to 4 weeks in the shop. We can't let Bell or Samsung get away with crappy hardware and want to make it cost them!
forum.xda-developers.com/showthread.php?t=883820

I tried calling Bell and they won't send me a replacement phone, they said I have to send my phone over and would take 3-6 weeks. How are you guys doing it??

Fwapi said:
I tried calling Bell and they won't send me a replacement phone, they said I have to send my phone over and would take 3-6 weeks. How are you guys doing it??
Click to expand...
Click to collapse
I had the same thing happen to my phone after Christmas when I upgraded via kies. Bell officially pulled off the upgrade after a couple days because it was corrupting internal SD cards. I went to a bell world store and asked them to deal with it. They told me that I would have to call a number and provide details. The guy at the store also told me that Bell had stopped sending out the phones for repair and Samsung was dealing with the SD card problems. So, I call the number, and after letting the "tech" know what happened, he told me a new phone would be sent via courier to me and warranty from the original would be transferred to the new replacement. He also told me that I would be getting a $100 credit on my bill. Five days later, I got my new replacement and sent in the old one back along with charger, battery, etc. New phone came with 2.2 JL2 installed. Hope this info helps.

Fwapi said:
I tried calling Bell and they won't send me a replacement phone, they said I have to send my phone over and would take 3-6 weeks. How are you guys doing it??
Click to expand...
Click to collapse
Go to the link I posted in my last post or search for CCTS in the forums
Sent from my GT-I9000M using XDA App

Tried those... Apparently they don't do replacement and don't give $100 credit anymore. They said it ended on Jan. 28th. I guess I will have to send my phone in for repairs

Did you go through the whole complaint filing process? I think you should get it exchanged no problem! What's the month and year of production? Should be underneath the battery under IMEI. Did you call bell or did they call you?
Sent from my GT-I9000M using XDA App

[Q] switch P1000 firmware from CHN to XEU

Hi,
My wife got me a Galaxy Tab GT-P1000 for my birthday. We live in China so it's a international model with CHN firmware preinstalled, which I updated from Froyo to Gingerbread using Samsung Kies.
The update was successful but unfortunately the Android Marketplace app (and Google Mail, and Google Maps, and Google anything) isn't included with this firmware (and Samsung Apps doesn't work just on wifi without a SIM card!) so I'm looking to flash it to XEU (Europe) and hoping that the XEU firmware includes all the Google apps... so I will be able to use my Tab as more than just a web browser.
I tried the Kies Registry Patcher to spoof the current firmware to an old XEU firmware (I used this string: "P1000XWJJ3/P1000XEUJJ3/P1000XXJID/P1000XWJJ3") and this worked as far as Kies recognising it as an out-of-date XEU firmware and telling me that there is an upgrade available. But after telling Kies to go ahead, I get this error: "the latest version is already installed on connected device". This then gets stuck in a loop - as long as I'm still spoofing the old firmware version, Kies tells me there is an upgrade available, but the update fails with the same message each time. When I stop spoofing, Kies goes back to normal, recognising that I have the latest Chinese firmware installed.
Q1: is there a fix for the error message above?
Not having any luck with Kies, I downloaded Check Fus and downloaded the latest XEU firmware (this one: P1000XWJMI/P1000XEUJM5/P1000XXJMA/P1000XWJMI) and now I have a TAR file which I unpacked and found lots of useful-looking files:
boot.bin
cache.rfs
factoryfs.rfs
hidden.rfs
modem.bin
P1_add_hidden.pit
param.lfs
Sbl.bin
zImage
I have Odin v1.7 but no idea how to configure it correctly to use the firmware I downloaded. I don't want to brick the device by flashing it incorrectly.
Q2: is there a guide to Odin so I can be sure to set it up correctly?
Any help much appreciated.
Cheers,
Larry

Hi Larry,
I upgraded mine recently and the thread is here
http://forum.xda-developers.com/showthread.php?t=1291217
Down the page is a thread by bongski55 which has link for Overcome.
and Homey, on page 3 of the thread has a great post with a You Tube link!!
http://forum.xda-developers.com/showthread.php?t=1291217&page=3
There are lots of other threads about ODIN and the procedure to follow..
This thread might have good information
http://forum.xda-developers.com/showthread.php?t=1193064
I had a bricked tablet at that time, and got lots of advice there..
Good luck,
Ofiaich

Thanks Ofiaich, I reviewed the threads and despite not being able to access the video on youtube (even through my VPN... thanks China!) I found sufficient instructions to give it a shot.
Download mode is easy - hold volume-down and power until the "Android at Work" yellow triangle shows on device - plug it in, then run Odin.
Looks like Odin only needs a couple of things:
1. PIT file (goes in PIT section)
2. TAR file (goes in PDA section)
And the PIT file is in the TAR file
Hit start.
Currently in download mode, hooked up through Odin and flashing the ROM I downloaded from Samsung earlier.
Will post back to let you know how it went. Fingers crossed.
Cheers,
Larry

Flashing in progress. Here's the Odin log... so far.
<ID:0/012> Added!!
<ID:0/012> Odin v.3 engine (ID:12)..
<ID:0/012> File analysis..
<ID:0/012> SetupConnection..
<ID:0/012> Initialzation..
<ID:0/012> Set PIT file..
<ID:0/012> DO NOT TURN OFF TARGET!!
<ID:0/012> Get PIT for mapping..
<ID:0/012> Firmware update start..
<ID:0/012> boot.bin
<ID:0/012> Sbl.bin
<ID:0/012> param.lfs
<ID:0/012> zImage
<ID:0/012> cache.rfs
<ID:0/012> hidden.rfs
The progress bars (on device about 5% complete; in Odin about 50% complete) haven't apparently made any progress in the (roughly) 15 minutes since Odin started flashing the hidden.rfs file. Granted that's the largest (343MB) file in the set to flash but long pauses make me nervous. Anyway, a problem shared and all that. I'm going to have a cup of tea and wait a bit more. Maybe it's using USB 1.0 for the transfer and Odin only updates the progress bar when the file completes (not during...).
L

Still stuck on hidden.rfs. Is it really supposed to take this long? I don't want to (actually, can't see any way to) interrupt it without unplugging the device or killing Odin. That sounds like a fast way to brick... but I can only wait until it's out of power anyway. Suppose I could leave it overnight.
Just for interest, I did a comparison of the size of the contents of the two ROMs I downloaded. First one is the one direct from Samsung (which I am trying to flash now). I downloaded that using Check Fus. It's apparently the latest XEU firmware. Second one is the P1000XXJQ1 firmware from samfirmware.com which is the latest that they have, but I suspect it's a bit old... which is why I'm trying the Check Fus one instead.
P1000XWJMI P1000XXJQ1
P1000XXJMA P1000XXJQ1
P1000XEUJM5 P1000XXJPZ
HOME HOME
Contents Size (bytes) Size (bytes) Same?
boot.bin 262144 262144 Yes
cache.rfs 8294400 2465792 No
factoryfs.rfs 323633152 318148608 No
gt-p1000_mr.pit 2008 Yes (as P1_add_hidden.pit)
hidden.rfs 351780864 35598848 No
modem.bin 12582912 12582912 Yes
P1_add_hidden.pit 2008 Yes (as gt-p1000_mr.pit)
param.lfs 565248 565248 Yes
Sbl.bin 1310720 1310720 Yes
zImage 7860352 7860352 Yes
Note that I've not done a binary comparison. This is just comparing the file sizes.
L

Well, the first flash I did got stuck on the hidden.rfs partition for over an hour so I killed Odin and that got me to the same soft brick state as described in this thread: http://forum.xda-developers.com/showthread.php?t=1193064
Lucky it was you Ofiaich who had that problem earlier and had already referred me to a thread with the strange "download mode" graphic (cartoon phone that can't connect to a computer). So, recognising that, I followed the instructions to unbrick on this page: http://forum.xda-developers.com/showthread.php?t=1133590
I reflashed again using the samfirmware.com ROM and the Odin flash went well (completed in about 3 minutes), the Tab rebooted, showed me the Galaxy Tab boot logo but has now got stuck at the Samsung "pulsing light" OS logo.
So now I'm guessing the XEU firmware doesn't work on the device I've got. Which is a pity because although I guess I can flash back to the Chinese firmware, I'm not sure if I can get Google apps now...
Any more tips appreciated.
Cheers,
Larry

problems Overcome
Last update today...
I've followed the instructions at http://p1000.teamovercome.net/?page_id=64 to get from non-booting image to a stock ROM which was working - Marketplace present and working
I decided to take the next step and go through with the Overcome update too and that is all working nicely.
Thanks to Ofiaich for the pointers.
Cheers,
Larry

Hi Larry!
I am glad those pointers helped! I received a lot of help from people in those threads and during the flashing procedures, was aware of a twinge of panic in my ascending colon, but now am very happy with my tablet!
Only trouble now is a young friend wants to steal it from me for her school work!
You live in China?
Oh! I hope to visit Shanghai --> Qindao -> Beijing, next May and travel with my Japanese friend. Hope to meet my friends in Qindao and Beijing!
I need to learn about China's bullet trains, overseas rail passes, and oh! Everything! I can only speak a little Mandarin!
Any advice and pointers about, what will be my first trip to China, much appreciated
Ofiaich

Yes, Beijing. Which is why I was a little surprised that my WCDMA Tab worked with the Overcome ROM which clearly says: "of course, it will not work for CDMA models!". Maybe it just means the USA CDMA models, not the China WCDMA?
On-topic content completed I can now blether about China. Actually, better than posting lots of off-topic chat here, how to contact you directly? Is there a private message in this forum or any way to swap email addresses without exposing them to spam bots?
L

Hi Guys,
i am looking for CSC for ITV italy so i can use with KIES for the future updating..
can you please help??
thanks

mphoneclinic said:
Hi Guys,
i am looking for CSC for ITV italy so i can use with KIES for the future updating..
can you please help??
thanks
Click to expand...
Click to collapse
Try this

Spoof FW from market worked for me and now kies consider my tab as the new region in all aspects. After upgrade root is gone ;-)
Read more here: http://forum.xda-developers.com/showthread.php?t=959806

Thanks guys, i will give them a shot

Dear Friends...
I use p1000 galaxy tab...I want to setup an stock Xeu firmware...
I am trying to update p1000XWjj3 Xeu firmware with odin but when it came to hidden.rfs it was freeze and waiting long...and they didnt do something...after that I plug off my tab...I tried XWJP9 Xeu firmware same again...I think there is a problem but what it is...hidden file is 320 mb...it is interesting...other firmware has 40 mb hidden file...
did you find a something about this situation?
I need XWJMI JMA JM5 XEU stock Rom...Do You Have it?
Could You Help Me Please

Questions about upgrading my GS5 4.4.2 to 5 or 6...

Hey all, there's a reason I want to switch to an upgraded version. I hear they have Wi-Fi calling, and that feature for me is important since I can do MMS pictures through wifi and not have to go through all types of hoops to do so. I have a few questions about this upgrade though:
Does the upgrade really implement WiFi Calling?
Are there any significant bugs which most people get?
Is there a root for GS5 with updated builds?
Is it possible to downgrade after going higher?
I was going to use this guide to upgrade.
Thanks!

What I can answer, WIFI Calling works with AT&T, If you are on a MVVNO provider such as Consumer Cellular, then no. The guide you referred to is fine.

Chuckles5150 said:
What I can answer, WIFI Calling works with AT&T, If you are on a MVVNO provider such as Consumer Cellular, then no. The guide you referred to is fine.
Click to expand...
Click to collapse
Well, I tried to update it in Odin, and I got an error
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> aboot.mbn
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
I did everything as instructed but thats what happened... Any suggestions?
Edit: I updated to 5.1.1 and it worked flawlessly. So now maybe installing 6 would work easier.

TWRP flash on Samsung Note 8; now no boot, no recovery, and Odin fails to reflash

I’m stuck and would appreciate advice with how to proceed with rooting my Samsung Note 8. The goal is to successfully root and then install Dr.Ketan ROM
Background:
I’m a curious and tenacious novice. This is also my first post. I appreciate your patience if I screwed something up.
I’ve successfully rooted a Samsung S7 Edge but that’s it. I’ve invested time reading posts about similar rooting-Note-8 issues. Despite the research, I’m still not sure how to proceed. In advance, I’m grateful for your advice.
Summary:
• Attempted root of Samsung Galaxy Note 8 (SM-N950F, Exynos chipset)
• After root, it successfully initiated the stock Android setup process (e.g., connect to WiFi, etc…)
• I was silly and didn’t complete the new device setup and instead, powered it down and went to bed That was apparently a really poor choice!
• Next day, I attempted to boot the phone. It wouldn’t boot normally and instead, I got the dreaded “Only official released binaries are allowed…” message
• Attempted to reflash TWRP using ODIN but it now fails
• Can only boot into download mode
What I originally did:
Rooted using ODIN
o I successfully flashed TWRP using:​-- Odin3_v3.13.1​-- twrp-3.3.1-0-greatlte.img.tar​-- Credit -- “Max Lee process”; reference galaxynote8root.com​
o Next, I flashed the other items that Max Lee recommends. I believe these items successfully flashed.​-- samsung-antiroot-removal-2.4.zip​-- RMM-State_Bypass_Mesa.zip​-- Magisk-v16.0.zip​
As previously described, after what I believe was a successful initial root, the phone initiated what appeared to be the stock-Android-first-time setup; and, unfortunately I failed to complete it :crying: and instead powered it off
What I’ve tried since:
• Power On: After powering the Note 8 on, it will not startup normally
o It says “Only official released binaries are allowed…” and promptly powers itself down​
{
"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"
}
• Boot to Recovery: Attempt boot into Recovery but it fails to start TWRP
o It says “Only official released binaries are allowed…” and promptly powers itself down​
• Boot into Download Mode: It will boot into download mode and displays the following:
• I’ve tried re-flashing TWRP using two different USB-C cables and two different PCs; all attempts failed
One specific question: Moving forward, if the best thing to do is to un-root and then re-root, is there a way to do it that will avoid another 7-days of FRP lock / jail hell? If so, I’d love specific guidance on how to do that.
In case it’s meaningful, there is no SIM card currently installed. Please advise if that is a problem

I'm a novice too so I always stick to the easy way.
I Flash in a prerooted rom.
I like the stock rom so I chose a custom rom that send to be a rom with very minimal tweaks but rooted.
For your case, you need to first download your official stock rom and flash it in with odin to solve the current problem.
Switch on and complete setup.
Then go back odin and flash in twrp
Then flash in a custom rom of your choice.
Sent from my SM-N950F using Tapatalk

Avoid FRP Lock?
vash_h said:
I'm a novice too so I always stick to the easy way.
I Flash in a prerooted rom.
I like the stock rom so I chose a custom rom that send to be a rom with very minimal tweaks but rooted.
For your case, you need to first download your official stock rom and flash it in with odin to solve the current problem.
Switch on and complete setup.
Then go back odin and flash in twrp
Then flash in a custom rom of your choice.
Sent from my SM-N950F using Tapatalk
Click to expand...
Click to collapse
First - thank you for your kind and helpful response! I didn't realize doing that was even an option.
Follow up questions:
• In the process of flashing the stock ROM and the custom ROM, is it inevitable that I the FRP lock will be triggered and I will get to wait 7 days?​• If it's not inevitable but is still a potential risk, any tips for what to not do so I can avoid lock jail?​
I admit that I'm probably a little paranoid about the FRP lock thing. While I've attempted to educate myself about what triggers it, it's still not crystal clear

Hi everybody, i've tried the oem trick to show the oem selector, i've tried to flash the TWRP but nothing, cant' root my phone. So i tried also to repack the AP file by magisk...nothing to do. I triend with chimera tool also, nothing to do
My pone has the revision firmware N950FXXS7DSH1_N950FOXM7DSG1 (ITV)
Name file:
AP_N950FXXS7DSH1_CL16168780_QB25173099_REV00_user_ low_ship_meta_OS9.tar
BL_N950FXXS7DSH1_CL16168780_QB25173099_REV00_user_ low_ship.tar
CP_N950FXXS7DSG1_CP13244265_CL16168780_QB24712629_ REV00_user_low_ship.tar
CSC_OXM_N950FOXM7DSG1_CL16168780_QB24712629_REV00_ user_low_ship.tar
When i try to flash the recovery, odin fails with the message "only official releasewd binaries...".
Any idea?

OneFineGuy said:
I’m stuck and would appreciate advice with how to proceed with rooting my Samsung Note 8. The goal is to successfully root and then install Dr.Ketan ROM
Background:
I’m a curious and tenacious novice. This is also my first post. I appreciate your patience if I screwed something up.
I’ve successfully rooted a Samsung S7 Edge but that’s it. I’ve invested time reading posts about similar rooting-Note-8 issues. Despite the research, I’m still not sure how to proceed. In advance, I’m grateful for your advice.
Summary:
• Attempted root of Samsung Galaxy Note 8 (SM-N950F, Exynos chipset)
• After root, it successfully initiated the stock Android setup process (e.g., connect to WiFi, etc…)
• I was silly and didn’t complete the new device setup and instead, powered it down and went to bed That was apparently a really poor choice!
• Next day, I attempted to boot the phone. It wouldn’t boot normally and instead, I got the dreaded “Only official released binaries are allowed…” message
• Attempted to reflash TWRP using ODIN but it now fails
• Can only boot into download mode
What I originally did:
Rooted using ODIN
o I successfully flashed TWRP using:​-- Odin3_v3.13.1​-- twrp-3.3.1-0-greatlte.img.tar​-- Credit -- “Max Lee process”; reference galaxynote8root.com​
o Next, I flashed the other items that Max Lee recommends. I believe these items successfully flashed.​-- samsung-antiroot-removal-2.4.zip​-- RMM-State_Bypass_Mesa.zip​-- Magisk-v16.0.zip​
As previously described, after what I believe was a successful initial root, the phone initiated what appeared to be the stock-Android-first-time setup; and, unfortunately I failed to complete it :crying: and instead powered it off
What I’ve tried since:
• Power On: After powering the Note 8 on, it will not startup normally
o It says “Only official released binaries are allowed…” and promptly powers itself down​
• Boot to Recovery: Attempt boot into Recovery but it fails to start TWRP
o It says “Only official released binaries are allowed…” and promptly powers itself down​
• Boot into Download Mode: It will boot into download mode and displays the following:
• I’ve tried re-flashing TWRP using two different USB-C cables and two different PCs; all attempts failed
One specific question: Moving forward, if the best thing to do is to un-root and then re-root, is there a way to do it that will avoid another 7-days of FRP lock / jail hell? If so, I’d love specific guidance on how to do that.
In case it’s meaningful, there is no SIM card currently installed. Please advise if that is a problem
Click to expand...
Click to collapse
If it specifies only user release builds can be flashed, can't you use ODIN to flash back to the stock FW you were on before, and then just restart the process from square 1? You shouldn't have to sit with an unbootable device if it will accept the same stock build you started with.
If it worked once, it should realistically work again. 7 days might be a long time to wait, but it beats a non-usable device any day of the week.

Eager for the next step
vash_h said:
I'm a novice too so I always stick to the easy way.
I Flash in a prerooted rom.
I like the stock rom so I chose a custom rom that send to be a rom with very minimal tweaks but rooted.
For your case, you need to first download your official stock rom and flash it in with odin to solve the current problem.
Switch on and complete setup.
Then go back odin and flash in twrp
Then flash in a custom rom of your choice.
Click to expand...
Click to collapse
Delgoth said:
If it specifies only user release builds can be flashed, can't you use ODIN to flash back to the stock FW you were on before, and then just restart the process from square 1? You shouldn't have to sit with an unbootable device if it will accept the same stock build you started with.
If it worked once, it should realistically work again. 7 days might be a long time to wait, but it beats a non-usable device any day of the week.
Click to expand...
Click to collapse
@Delgoth and @vash_h -- Thank you for your guidance. I tried a few things, am still stuck, and would love your ideas for next possible steps.
Summary
I downloaded stock firmware using the SamFirm app / downloader and attempted to flash using Odin. Odin reports "FAIL!"
Details of what I've done:
* Used SamFirm_v0.3.6 to download stock firmware (see "SamFirm Detail" and image below).
* My device model # is SM-N950F. I don't know what version of stock firmware the device is expecting. I decided to download a UK version of ROM because English is my native language. However, I do remember seeing Spanish or Portuguese (or similar) as the default language on the device before I started rooting it.
** NOTE: I don't know what firmware shipped with this phone. I purchased it used and made the novice mistake of not documenting what was there before starting. And now, it won't boot so I don't know how to figure that out.​
* Used Odin v3.13.1 as well as v3.12.7 in my attempt to flash the stock firmware. Ran both versions of Odin as an Administrator
* In both instances, Odin fails on sboot.bin (see details below)
Code:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1207)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> FAIL!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Questions
* Any ideas on what I'm doing wrong?
* In its current state, how can I determine what version of stock firmware shipped with this phone (now that the phone will not boot normally)?
* Maybe stock firmware flash fails because the version I'm attempting to flash uses an bootloader version that is older (than what is currently in use)?
** If that is a possibility, I would love guidance on how to determine the version of bootloader the device is using​** Download screen on device reports​RP SWREV: B:4 K:2 S:2​
* Is using "Emergency Firmware Recovery" option in Samsung Kies 3 app a good option to move forward?

OneFineGuy said:
@Delgoth and @vash_h -- Thank you for your guidance. I tried a few things, am still stuck, and would love your ideas for next possible steps.
Summary
I downloaded stock firmware using the SamFirm app / downloader and attempted to flash using Odin. Odin reports "FAIL!"
Details of what I've done:
* Used SamFirm_v0.3.6 to download stock firmware (see "SamFirm Detail" and image below).
* My device model # is SM-N950F. I don't know what version of stock firmware the device is expecting. I decided to download a UK version of ROM because English is my native language. However, I do remember seeing Spanish or Portuguese (or similar) as the default language on the device before I started rooting it.
** NOTE: I don't know what firmware shipped with this phone. I purchased it used and made the novice mistake of not documenting what was there before starting. And now, it won't boot so I don't know how to figure that out.​
* Used Odin v3.13.1 as well as v3.12.7 in my attempt to flash the stock firmware. Ran both versions of Odin as an Administrator
* In both instances, Odin fails on sboot.bin (see details below)
Code:
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1207)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> FAIL!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Questions
* Any ideas on what I'm doing wrong?
* In its current state, how can I determine what version of stock firmware shipped with this phone (now that the phone will not boot normally)?
* Maybe stock firmware flash fails because the version I'm attempting to flash uses an bootloader version that is older (than what is currently in use)?
** If that is a possibility, I would love guidance on how to determine the version of bootloader the device is using​** Download screen on device reports​RP SWREV: B:4 K:2 S:2​
* Is using "Emergency Firmware Recovery" option in Samsung Kies 3 app a good option to move forward?
Click to expand...
Click to collapse
Your 4 file firmware image you posted lists the AP and BL files as being Bootloader revision 1 (1AQI1). The first picture looks as if you are trying to download the revision 7 FW, but the 4 files you have listed underneath are from a revision 1 firmware. This would indicate why your flash fails at sboot.bin. Because it seems you would be flashing too old of a revision to the device.
"RP SWREV: B:4 K:2 S:2" seems to indicate you're device is on a Revision 4 bootloader. Samsung Smart switch may be a good candidate to use if the program will detect the device still. But if you can still flash in download mode you should be able to get smart switch to pick up the device and give you some details. I would say maybe try using another source to acquire the Firmware and trying again with a Revision 4 or 5 firmware package at least.

Delgoth said:
Your 4 file firmware image you posted lists the AP and BL files as being Bootloader revision 1 (1AQI1). The first picture looks as if you are trying to download the revision 7 FW, but the 4 files you have listed underneath are from a revision 1 firmware. This would indicate why your flash fails at sboot.bin. Because it seems you would be flashing too old of a revision to the device.
"RP SWREV: B:4 K:2 S:2" seems to indicate you're device is on a Revision 4 bootloader. Samsung Smart switch may be a good candidate to use if the program will detect the device still. But if you can still flash in download mode you should be able to get smart switch to pick up the device and give you some details. I would say maybe try using another source to acquire the Firmware and trying again with a Revision 4 or 5 firmware package at least.
Click to expand...
Click to collapse
First, thank you again for your patience and tenacity in helping me through this issue! I've done some more homework and have a couple more questions I'd love to run past you:
1. Because I'm simply trying to load stock firmware so I can resume and complete the root, does it matter which region- or carrier-specific (CSC) stock firmware version I use?
Naturally, it's well understood that using legit stock firmware that is specifically for the SM-N950F is mission critical. I ask because I don't know what the original CSC version of my phone was, I don't know how to find that out now that it won't boot up, and the vast array of Region / Carrier versions available is dizzying.
2.a. Will you help me confirm what the revision # is for the boot loader file shown below? I think the "7" that I've highlighted means it is version 7 (but I'm not totally sure because the file name seems to be missing the letter to indicate the calendar month of the release date).
Background: I recently downloaded "XEU" flavored stock firmware from SamFirm. I highlighted parts of the filename and attempted to provide an interpretation about what things mean based on what I think I know.
2.b. Regarding the firmware file naming scheme, is the letter that refers to the month of release (that follows the "year" code) optional? I'm confused because (in the images above), I was expecting another letter to follow the blue-colored-highlighted "S" [in order to indicate the month of release]. Instead, the "S" is followed by the number "7" (which seems to refer to the revision #, rather than the month). Can you confirm or advise?
3. When you look at the image of this other firmware file set I've downloaded, do you see any reason why it shouldn't work? I'm simply asking for advice based on your experience, and certainly not asking to try and hold you responsible if it doesn't work: the responsibility is all mine.

Hi. Are you still stuck?
If you are, try to locate the box your phone came with.. Let us know the exact model and what's written on the bar code labels..
It'll better help us understand the origin of the phone (which region) and we can better identify which firmware you need.
Sent from my SM-N950F using Tapatalk

You can't do downgrade with that version I think

Making Progress
vash_h said:
Hi. Are you still stuck?
If you are, try to locate the box your phone came with.. Let us know the exact model and what's written on the bar code labels..
It'll better help us understand the origin of the phone (which region) and we can better identify which firmware you need.
Sent from my SM-N950F using Tapatalk
Click to expand...
Click to collapse
Thank you for reaching out and asking. The spirit of helpfulness you embody is awesome and is part of what makes XDA Developers such a gem. I have good news and a couple of things I would love your help with. Questions are below in hot pink.
* The good news is that I finally got a stock version of Android successfully reinstalled. I'm waiting for my 7-day OEM unlock, which is due tomorrow. I'm excited to restart the rooting process and nail it this time!
* One thing I'd love your input with is this: Is it likely that having installed the wrong region-specific version of stock android is causing the phone to ask for a "Network Unlock Code"?
** The region-specific version of stock Android that I successfully installed is for the UK and parts of Europe. That was my best guess (at the time) as to the flavor of stock Android that my phone shipped with. I now know that the region-version I installed was not the correct one.
** When I insert my SIM card, it asks for a Network unlock code. I've not yet successfully gotten past that.
** I bought the phone used from Amazon Warehouse and it was specifically listed as an unlocked phone. When asked about the issue, Amazon tech support believed it wants a SIM card PUK code (from my network provider) in order to unlock.
** I called my cellular phone provider, got my PUK code, entered it, and it didn't work. They believe it is a network lock placed by the phone's previous cellular network provider
** By enlisting the services of CanadaUnlocking.com, I learned that my phone was originally used on the iusacell network in Mexico
** iusacell was purchased by AT&T a few years ago. I contacted AT&T and supplied my IMEI #. They said they don't even have that IMEI on record
** I decided to just pay UnlockBase.com to unlock it for me
** UnlockBase worked on it for a few days and then refunded my money. They weren't clear as to why. One possible implication was that it wasn't even locked to begin with
** I then paid doctorSIM for a blacklist report and it came back clean. The isuacell network was even specifically listed with a green check mark next to it.​
The theory I've come up with to try and explain why the phone is asking for a Network Unlock Code is this: it's simply freaking out because I installed the wrong region-specific version of Android. Is that likely, in your opinion?
Regardless of the root cause, any ideas for unlocking it?

OneFineGuy said:
Thank you for reaching out and asking. The spirit of helpfulness you embody is awesome and is part of what makes XDA Developers such a gem. I have good news and a couple of things I would love your help with. Questions are below in hot pink.
* The good news is that I finally got a stock version of Android successfully reinstalled. I'm waiting for my 7-day OEM unlock, which is due tomorrow. I'm excited to restart the rooting process and nail it this time!
* One thing I'd love your input with is this: Is it likely that having installed the wrong region-specific version of stock android is causing the phone to ask for a "Network Unlock Code"?
** The region-specific version of stock Android that I successfully installed is for the UK and parts of Europe. That was my best guess (at the time) as to the flavor of stock Android that my phone shipped with. I now know that the region-version I installed was not the correct one.
** When I insert my SIM card, it asks for a Network unlock code. I've not yet successfully gotten past that.
** I bought the phone used from Amazon Warehouse and it was specifically listed as an unlocked phone. When asked about the issue, Amazon tech support believed it wants a SIM card PUK code (from my network provider) in order to unlock.
** I called my cellular phone provider, got my PUK code, entered it, and it didn't work. They believe it is a network lock placed by the phone's previous cellular network provider
** By enlisting the services of CanadaUnlocking.com, I learned that my phone was originally used on the iusacell network in Mexico
** iusacell was purchased by AT&T a few years ago. I contacted AT&T and supplied my IMEI #. They said they don't even have that IMEI on record
** I decided to just pay UnlockBase.com to unlock it for me
** UnlockBase worked on it for a few days and then refunded my money. They weren't clear as to why. One possible implication was that it wasn't even locked to begin with
** I then paid doctorSIM for a blacklist report and it came back clean. The isuacell network was even specifically listed with a green check mark next to it.​
The theory I've come up with to try and explain why the phone is asking for a Network Unlock Code is this: it's simply freaking out because I installed the wrong region-specific version of Android. Is that likely, in your opinion?
Regardless of the root cause, any ideas for unlocking it?
Click to expand...
Click to collapse
Thanks for the compliments. To be completely honest with you, i have no idea about the network unlock code as operators in my country do not lock the phones, and is illegal to do so.
However, doing a search on the internet shows it is part of the process of unlocking the phone (from network lock).
Do you have this problem when you first receive the phone?
Now that you can confirm your phone is mexican in origin, ISUACELL in particular, you can try to flash in their rom and see if it solves the problem. But i would wait for the unlock code that you will receive tomorrow and use that first.
https://www.sammobile.com/samsung/galaxy-note-8/firmware/sm-n950f/IUS/
Hopefully this helps.

Now running its native Mexico IUS firmware
vash_h said:
Thanks for the compliments. To be completely honest with you, i have no idea about the network unlock code as operators in my country do not lock the phones, and is illegal to do so.
However, doing a search on the internet shows it is part of the process of unlocking the phone (from network lock).
Do you have this problem when you first receive the phone?
Now that you can confirm your phone is mexican in origin, ISUACELL in particular, you can try to flash in their rom and see if it solves the problem. But i would wait for the unlock code that you will receive tomorrow and use that first.
https://www.sammobile.com/samsung/galaxy-note-8/firmware/sm-n950f/IUS/
Hopefully this helps.
Click to expand...
Click to collapse
Re: "Do you have this problem when you first receive the phone?"
That's a fantastic question. The issue is that I don't know. I didn't insert the SIM card and check for network connectivity before I proceeded to root. I'm normally very methodical, but unfortunately not this time.​
Update:
* Since my last post, I passed the 7-day waiting period for OEM Unlock and the unlock option never appeared. Frustrating.
* Because I now know the exact flavor of the original stock ROM, I then decided to flash it to my phone. I was able to do that without issue. It's now running N950FXXS5CSB4 Firmware, Mexico (IUS)
** Thanks to Sammobile.com for the firmware!​* However, upon inserting my SIM card it still asks for a Network Unlock Code. I've still been unable to unlock it.
** I was hoping that the Network Unlock issue would disappear because the phone was now running it's mother ROM again (and not even ask for a Network Unlock Code)​** I did enter my SIM card PUK # but it didn't accept that​
I'd love input on two things:
1. Any ideas as to why the OEM Unlock option never did appear? (i.e., before I flashed it to N950FXXS5CSB4 Firmware)
** The phone had been running continuously over 300 hours (uptime) since reboot​** Near the beginning, I did log into my Google account on the device​** Note: I didn't log into a Samsung account on the phone. Maybe that is the problem??​
2. Any suggestions on threads to read (or search terms to use) to get more ideas on how to network unlock this phone?
* I've done a lot of Googling and have run out of ideas

hey,
so were you able to sort this out at all or not. the oem unlock usually takes 15 days to reappear in most cases. the rerial no of your device should help you get all details about its origins there is an app called phone info which is very handy to find out all details of your device if you have root then it will give you everything you need to know and can get you into engineering mode too

sm-g781V to sm-g781u

Hi,
I spent the last few hours trying all the roms for the single sim variants of s20fe on sm-g781v, hoping any of these roms will fix the touch issue but sadly all gave the same error message
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Re-Partition operation failed.
My question is:
If I extracted the pit file of sm-g781u and added it to the Odin while installing the rom + ticking on nand erase , will this hard brick my device?
it's very weird and annoying why they decided to lock this model specially, I have s21 and managed to install the unlocked firmware without any issues.
Thanks everyone

if the touch issue was entirely software related it would have been possible to fix in the year plus the FE has been around.
can't remember which phone it is, another phone that shares the same panel as ours also has touch issues I've heard.