Develop Bugs

Flashing I9000DXJF5 firmware..

Im using I9000DXJF4 (Asia) firmware atm and now samsung-firmware.webs.com has released I9000DXJF5(Europe) so..
Is it worth the upgrade? Why there is no change log or some sort of information provide at all?
I just dont wanna brick my $900 :-S
Oh.. and do I need to root the phone first before flashing firmware?

hey i flashed from the singtel firmware too. no need to root before flashing. just follow the instructions given on the fw website. should not brick if you do it correctly
cheers

twit_xp said:
hey i flashed from the singtel firmware too. no need to root before flashing. just follow the instructions given on the fw website. should not brick if you do it correctly
cheers
Click to expand...
Click to collapse
Yeah but I'd like to know the changes first. I dont wanna risk it before I even know what I put in it.

just flashed jf5 , system is faster and more stable . market speed increased a lot !
with odin bricking the device is quite impossible... i suggest flashing

zomg just flashed to jf5 and i booted with some language (russian or something) any idea how to switch it back to english?
edit: nevermind stuck my sim card in and it went to english automatically lol

twit_xp said:
zomg just flashed to jf5 and i booted with some language (russian or something) any idea how to switch it back to english?
Click to expand...
Click to collapse
Did you flash with the included CSC? i believe the CSC is still F3..

daduzzo888 said:
just flashed jf5 , system is faster and more stable . market speed increased a lot !
with odin bricking the device is quite impossible... i suggest flashing
Click to expand...
Click to collapse
This sounds good, did you come from F4 firmware before the upgrade?

Ferdimage said:
Did you flash with the included CSC? i believe the CSC is still F3..
Click to expand...
Click to collapse
yup i used all the 3 included files for the flash

what are you guys using to backup your apps and contact, email etc before flashing?

Can you see with the new JF5 version non-free Apps in market?

Can anyone tell me, does flashing these updated firmwares void your warranty?
The firmwares seem official, but also i guess not official as they are not available directly from samsung?

Odin
In odin after clicking start i see
<ID:0/018> Added!!
<ID:0/018> Odin v.3 engine (ID:18)..
<ID:0/018> File analysis..
How long does file analysis take? because mine is busy for 15 minutes now

krotwijk said:
In odin after clicking start i see
<ID:0/018> Added!!
<ID:0/018> Odin v.3 engine (ID:18)..
<ID:0/018> File analysis..
How long does file analysis take? because mine is busy for 15 minutes now
Click to expand...
Click to collapse
Odin and your phone are not connected correctly. It should fly....
Are you using Windows 7 64bit?
You should try to connect your phone to your pc and then try to boot your phone in to download mode.

kimatrix said:
Odin and your phone are not connected correctly. It should fly....
Are you using Windows 7 64bit?
You should try to connect your phone to your pc and then try to boot your phone in to download mode.
Click to expand...
Click to collapse
yes, windows 7 64 bit.
this fixed it.
I've assigned the
CODE_I9000XWJFB.tar to PDA
CSC_I9000SERJF3.tar to CDC
MODEM_I9000XXJF5.tar to Phone
After reboot, the sim card must be in the phone, otherwise i had russian language
But samsung apps is still in russian and the sim unlock screen too instead of dutch
After setting the apn to vodafone the sim unlock screen is dutch language, but samsung apps not

krotwijk said:
yes, windows 7 64 bit.
this fixed it.
I've assigned the
CODE_I9000XWJFB.tar to PDA
CSC_I9000SERJF3.tar to CDC
MODEM_I9000XXJF5.tar to Phone
After reboot, the sim card must be in the phone, otherwise i had russian language
But samsung apps is still in russian and the sim unlock screen to instead of dutch
Click to expand...
Click to collapse
Can you get another CSC from another firmware that has Eng,
Im gonna flash it alter tonight but i will leave the CSC as is...

mine is stuck at
<OSM> All threads completed. (succeed 0 / failed 0)
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> factoryfs.rfs

discophil said:
Can anyone tell me, does flashing these updated firmwares void your warranty?
The firmwares seem official, but also i guess not official as they are not available directly from samsung?
Click to expand...
Click to collapse
bump! .

it will be good if we can see some change logs...

Wow flashing was easy as, thanks to guides and peoples feedback, very happy with the falsh all my apps msg etc are intact, just settings have changed.. JF5 is a good update my phone feels 10% quicker

@discophill As long as you reflash the FW that shipped with your phone before sending it in, the peeps at Samsung should not be able to tell that you meddled with it in the first place =D

[Q] Am I Soft AND Hard Bricked At The Same Time?

Hello there people. I'd not new to this website.... I've just been a ghost that was finally forced to register for this site.
I have a
Tmobile Galaxy S3 (SGH T-999)
Now, I rooted my phone with CWM a while back.
So then after a couple of days, I decided that I wanted a Custom Rom. Turns out that it wasn't compatible for my phone.
So I got put in a bootloop.
I was able to Access Recovery and Download mode.
I factory reset my phone from there, formatted dalvik, all of that.
I downloaded a stock bootloader and stock Rom from here for my phone
I tried to use odin to flash the stock bootloader onto my phone. From what i can remember i saw, boot.img, Compete(Write) operation failed.
Now when i booted my phone all i see is
it just...... Activates
Firmware upgrade encountered an issue. Please select recovery mode in kies and try again.
Therefore i cannot access recovery mode anymore but i can still access Download Mode. I cannot see it boot at all.
Some Info while in download mode:
ODIN MODE
Product Name: SGH-T999
Custom Binary Download: Yes(1Count)
Current Binary:Samsung Official
System Status:Custom
Qualcom Secureboot:Enable
Warranty Bit:0
Bootloader Ap swaev:1
Here's how it looks when i try to flash stock rom or virtually anything onto my phone.
Code:
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've given up on trying to do this myself and I now have to suck up my pride and ask for help.
Is there still hope, or do i have a $500 Paper Weight? Please Help.

What file did you download and flash? You posted in the sprint section sph710. If you flashed something for this model instead of your model that could be the problem.

metalfan78 said:
What file did you download and flash? You posted in the sprint section sph710. If you flashed something for this model instead of your model that could be the problem.
Click to expand...
Click to collapse
Sorry about that. I was rushing lol. I forgot what rom i downloaded. It was off an rooted app. I think it was ROM Manager.

That doesn't help. If you have a T-Mobile phone and you flashed something for a sprint phone then you need to download a T-Mobile ROM and flash. Or use a stock T-Mobile tar file and use Odin.

metalfan78 said:
That doesn't help. If you have a T-Mobile phone and you flashed something for a sprint phone then you need to download a T-Mobile ROM and flash. Or use a stock T-Mobile tar file and use Odin.
Click to expand...
Click to collapse
I remember now. I downloaded a CyanogenMod Rom. I did rebooted without deleting everything on my phone. Then i got soft brick. And I'm pretty sure, It will say Get pit file....... Complete(Write) Fail. As usual.

Great news. I tried to flash root66 on my phone. Which almost installed but failed. Now when i boot up my phone, I get put in the boot loop BUT I can access the recovery mode from there now. Now what? Do I install CMW or something or just stock?

Sir, just download a ROM for your phone model. But as I can see (and I think others members too) the safest is going back to stock until you understand the difference between your phone model and others.
Sent from my SPH-L710

Do you realize you keep posting in the sprint section? Thats going to make a huge difference. I keep asking because I don't think you realize you are in the sprint section and I'm assuming you keep downloading and flashing Sprint roms.

metalfan78 said:
Do you realize you keep posting in the sprint section? Thats going to make a huge difference. I keep asking because I don't think you realize you are in the sprint section and I'm assuming you keep downloading and flashing Sprint roms.
Click to expand...
Click to collapse
I know I'm posting in the sprint model, I didn't know when I first made this thread because I was in panic mode and I was about to be late for my mid term while making this thread. Can you give me a break? I really don't have time to make another one in the proper section.. + I didn't flash any sprint roms. I have a T mobile galaxy s3. And the Root66 Rom i attempted to flash was for SGH T-999. It failed but I was able to actually get into recovery mode again but it's stock recovery.

I wasn't trying to be a jerk, just trying to clarify. You'll get more help in the correct forum. Just because it's the same phone doesn't mean everything works the same. There are differences from one model to the next.

metalfan78 said:
I wasn't trying to be a jerk, just trying to clarify. You'll get more help in the correct forum. Just because it's the same phone doesn't mean everything works the same. There are differences from one model to the next.
Click to expand...
Click to collapse
ok, I will. And I know that. Look at the first post of the thread, I know the different model. I just posted in the wrong section due to rushing and stress.

Understandable, I've just seen quite a few confused people here

metalfan78 said:
Understandable, I've just seen quite a few confused people here
Click to expand...
Click to collapse
This thread can be closed now. I've made a new one in the proper section and more understanding.

It always comes in as 'I had time to mess with it but don't have time to fix it.' Sheez.

Kevets said:
It always comes in as 'I had time to mess with it but don't have time to fix it.' Sheez.
Click to expand...
Click to collapse
No. I had time at 5PM at home after returning from school. 3AM it got bricked. Went to sleep, Woke up at 7:40AM, Had to rush to get ready for school to take Midterms at 8:15AM + Make this thread. And there's no where in any of my posts where you see me say I don't have time to FIX it. I said I didn't have time to POST IN THE RIGHT SECTION.
Moral of this reply: You don't know me.
If you're not here to help, You can find your way out of my thread with your useless post. Sheesh.

Help unbrick note 3

I am not new to the rooting scene, however I have a problem that I can't seem to figure out. I've been reading now for the past 2 days, tried several things and still can't get this resolved. I've never had any issues in the past with odin and rooting samsung phones before, including ones with locked bootloaders. However, I've met my match. I tried following the tutorial listed on this site for rooting the samsung note 3 from tmobile. I watched the video and followed along with the files listed here
http://forum.xda-developers.com/note-3-tmobile/#root
My problem is as follows: I tried rooting with odin, installed kies for the usb support but halfway through the root process I get the big RED FAILED! phone's progress bar stops and it hangs. I though this was strange and never encountered this before. I then tried repeating the same process and same results, however this time around I am only able to bring the phone into "odin" mode "download" and not the original stock rom.
At first I was getting the original "the firmware encountered an upgrade issue" and couldn't bypass this unless I opted for download mode. I've tried the same steps to "unbrick" via oden with stock tmobile firmware for this phone and yet it yields the same results, big exclamation failed on odin. I then tried the process with the .pit file to partition that I found online somewhere and that fails too. My note starts up now, but stuck at the samsung galaxy note 3 screen. I've tried several versions of odin, switching usb cables, usb ports and I am unable to root this phone or even get it unbricked! i've read extensively here and can't seem to find a solution to my problem. Can someone PLEASE point me in the right directions?? BTW, I am using a mac with VMWARE, i've never encountered any issues with vmware in the past while running windows 8.
Phone says the following:
Once in download mode my phone says the following:
ODIN MODE
PRODUCT NAME: SW-N900T
CURRENT BINARY: CUSTOM
SYSTEM STATUS: OFFICIAL
KNOX KERNEL LOCK: 0X0
KNOX WARRANTY VOID: 0X0
QUALCOM SECUREBOOT: ENAMBLE
RP SWREV: S2, T2, A2, A3 P2
WRITE PROTECTION: ENABLE
UOC START
and I get these results from ODIN:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N900TUVUCNB4_N900TTMBCNB4_N900TUVUCNB4_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Try a new computer...
Sent from my SM-N900T using Tapatalk

dobbs3x said:
Try a new computer...
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
You think a new computer might solve this?

Try using Heimdall. That should work natively on your Mac.
You can read about it and download it from here http://forum.xda-developers.com/showpost.php?p=7679702&postcount=1

xmatic said:
You think a new computer might solve this?
Click to expand...
Click to collapse
Actually, he might be right. But you may need to just try a different USB port instead of a new computer.
I had a problem with Odin failing when I tried to install a ROM. I remembered something about there being problems with certain USB ports, so I switched it to a port on the front of my PC and it worked. This was despite the fact that Odin recognized the device in the first port.
Hope that helps.
TL;DR: Just read through your post again and saw that you already tried that. Sorry.

dragonstalker said:
Try using Heimdall. That should work natively on your Mac.
You can read about it and download it from here http://forum.xda-developers.com/showpost.php?p=7679702&postcount=1
Click to expand...
Click to collapse
I use Odin all the time for rooting Samsung phones. Never used Heimdall, but love the idea of using it in my Mac.
Does this works with Note 3?

dragonstalker said:
Try using Heimdall. That should work natively on your Mac.
You can read about it and download it from here http://forum.xda-developers.com/showpost.php?p=7679702&postcount=1
Click to expand...
Click to collapse
Thanks for all the help, I was able to install the original rom back and restore the phone to it's original state through my mac side. I have downloaded Heimdall, but what are the steps necessary to root my phone? I only see an option to load package, flash or create package but it seems it's requiring a "PIT" file. Can anyone point me in the right direction of which particular file I need to root this note 3 with Heimdall? Thanks!

xmatic said:
Thanks for all the help, I was able to install the original rom back and restore the phone to it's original state through my mac side. I have downloaded Heimdall, but what are the steps necessary to root my phone? I only see an option to load package, flash or create package but it seems it's requiring a "PIT" file. Can anyone point me in the right direction of which particular file I need to root this note 3 with Heimdall? Thanks!
Click to expand...
Click to collapse
CF_Autoroot does not work with Heimdall? I have yet to use it eventhough i have a Ubuntu Box. So i'm curious to know also.

dragonstalker said:
CF_Autoroot does not work with Heimdall? I have yet to use it eventhough i have a Ubuntu Box. So i'm curious to know also.
Click to expand...
Click to collapse
The auto root is not working for me period! it bricked my phone 3 times already and I had to unbrick. It was a pain in the butt. All ulitmately due to odin failing with the flashes. I've tried different versions of Odin, different versions of windows within vmware and different usb slots/cables. All fail! Is there another way to root this phone guys! Please help? I am on a mac. Obviously Odin is now out of the question.

xmatic said:
The auto root is not working for me period! it bricked my phone 3 times already and I had to unbrick. It was a pain in the butt. All ulitmately due to odin failing with the flashes. I've tried different versions of Odin, different versions of windows within vmware and different usb slots/cables. All fail! Is there another way to root this phone guys! Please help? I am on a mac. Obviously Odin is now out of the question.
Click to expand...
Click to collapse
Um please don't yell at me, but, are you using the cf_autoroot from the N9005 or the N900T. The N900t version doesn't work. You have to use the N9005 CF_Autoroot.
Try This. Although its a mirror. PLEASE go to CHAINFIRE page and thank him. http://tekhd.com/downloads/CF-Auto-Root-hlte-hltexx-smn9005.zip

dragonstalker said:
Um please don't yell at me, but, are you using the cf_autoroot from the N9005 or the N900T. The N900t version doesn't work. You have to use the N9005 CF_Autoroot.
Try This. Although its a mirror. PLEASE go to CHAINFIRE page and thank him. http://tekhd.com/downloads/CF-Auto-Root-hlte-hltexx-smn9005.zip
Click to expand...
Click to collapse
That is what I used but get on a PC. Go over a friends house and borrow his.
TWEAKED N3

dragonstalker said:
Um please don't yell at me, but, are you using the cf_autoroot from the N9005 or the N900T. The N900t version doesn't work. You have to use the N9005 CF_Autoroot.
Try This. Although its a mirror. PLEASE go to CHAINFIRE page and thank him. http://tekhd.com/downloads/CF-Auto-Root-hlte-hltexx-smn9005.zip
Click to expand...
Click to collapse
My apologies, I didn't think I was yelling, and I didn't mean to be ass. I am just a little frustrated because i've never had any issues before in the past rooting a phone, especially a samsung phone via Odin. I'll try this as I was using the n900t auto root. I'll advise how it goes.

xmatic said:
My apologies, I didn't think I was yelling, and I didn't mean to be ass. I am just a little frustrated because i've never had any issues before in the past rooting a phone, especially a samsung phone via Odin. I'll try this as I was using the n900t auto root. I'll advise how it goes.
Click to expand...
Click to collapse
OH no. i was saying don't yell at me for asking the question.
If you still have issues pm me. i'll give you my number and we'll walk thru it.

BACARDILIMON said:
That is what I used but get on a PC. Go over a friends house and borrow his.
TWEAKED N3
Click to expand...
Click to collapse
I failed again, can't get it to work. I wouldn't be surprised if it's a vmware thing. I just can't find anyone with a pc around.

xmatic said:
I failed again, can't get it to work. I wouldn't be surprised if it's a vmware thing. I just can't find anyone with a pc around.
Click to expand...
Click to collapse
Sorry bro I just don't know enuff about Mac products to point you in the right direction.
TWEAKED N3
---------- Post added at 11:05 AM ---------- Previous post was at 10:48 AM ----------
dragonstalker said:
Um please don't yell at me, but, are you using the cf_autoroot from the N9005 or the N900T. The N900t version doesn't work. You have to use the N9005 CF_Autoroot.
Try This. Although its a mirror. PLEASE go to CHAINFIRE page and thank him. http://tekhd.com/downloads/CF-Auto-Root-hlte-hltexx-smn9005.zip
Click to expand...
Click to collapse
https://plus.google.com/app/basic/stream/z12yzpirzqf4srxw204cjl1aoor5ezninhc
He just updated the apps like 50 min ago
TWEAKED N3

xmatic said:
You think a new computer might solve this?
Click to expand...
Click to collapse
This is the same exact problem I'm having. Also not new to rooting.
Guess what. I'm also trying on a mac with VMWARE. Makes me wonder. But I've rooted so many times this way. What makes this android any different. Tomorrow I'll try making a boot able window HD.
Sent from my SM-N900T using xda app-developers app

starscrean said:
This is the same exact problem I'm having. Also not new to rooting.
Guess what. I'm also trying on a mac with VMWARE. Makes me wonder. But I've rooted so many times this way. What makes this android any different. Tomorrow I'll try making a boot able window HD.
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
Yeah, i've given up with rooting via VMWARE and Odin, it just doesn't work, period. I've tried to virtual machines, a win 8 and win 7 all with the same results. I have a feeling it's VMware, I am trying parallels now and I'll post updates afterwards. Thanks to everyone for contributing. BTW, does anyone know if it's even possible to root with Heimdall?

Update:
I was able to root fine without any issues, it seems the issue was ONLY because I used VMWARE! To all you mac users out there, I tried Parallels 9 and voila it worked!

xmatic said:
Update:
I was able to root fine without any issues, it seems the issue was ONLY because I used VMWARE! To all you mac users out there, I tried Parallels 9 and voila it worked!
Click to expand...
Click to collapse
This is good to hear. I'll give a try and update later. Thanks
Sent from my SM-N900T using xda app-developers app
---------- Post added at 05:21 AM ---------- Previous post was at 05:07 AM ----------
In the future another easy way to unbrick your Samsung just open Kies in tools drop down select the emergency firmware. A pop up will ask you to put in your phone model and S/N. Kies restores firmware via download mode. This is how I restored from 5 bricks.
Sent from my SM-N900T using xda app-developers app

xmatic said:
Yeah, i've given up with rooting via VMWARE and Odin, it just doesn't work, period. I've tried to virtual machines, a win 8 and win 7 all with the same results. I have a feeling it's VMware, I am trying parallels now and I'll post updates afterwards. Thanks to everyone for contributing. BTW, does anyone know if it's even possible to root with Heimdall?
Click to expand...
Click to collapse
MUCH THANKS !!! To you my friend. I must've bricked my phone 5x trying to gain root using vmware.
So I downloaded the parellel 9. And BOOMMMM. I was so glad to see a big green pass in Odin lol.
Sent from my SM-N900T using xda app-developers app

Galaxy Tab S help (SM-T807P)

Hello,
I have ran into a huge problem with my tab S and I have been trying to fix this problem for weeks on end. The problem is I can't seem to flash my tablets stock rom without it giving me some error message saying "invaild ext4 image". I have done some research and from what I've found I need the PIT file but I can't find it at all. I know you can extract the PIT file from your device but I don't have access to the OS right now, just ODIN and my custom recovery. The OS is 4.4.2 and the Version is T807PVPU1ANK1 before It messed up. I have also tried to flash a higher OS version like 6.0 to the device but every time I try I get a message that says "Image file too large 5000 > 54466" or something like that. The device was not rooted before it broke either. This tablet is very expensive so If someone could please provide me with the PIT file for this device I would greatly appreciate it. (Image below is what the error is)

irontaco1 said:
Hello,
I have ran into a huge problem with my tab S and I have been trying to fix this problem for weeks on end. The problem is I can't seem to flash my tablets stock rom without it giving me some error message saying "invaild ext4 image". I have done some research and from what I've found I need the PIT file but I can't find it at all. I know you can extract the PIT file from your device but I don't have access to the OS right now, just ODIN and my custom recovery. The OS is 4.4.2 and the Version is T807PVPU1ANK1 before It messed up. I have also tried to flash a higher OS version like 6.0 to the device but every time I try I get a message that says "Image file too large 5000 > 54466" or something like that. The device was not rooted before it broke either. This tablet is very expensive so If someone could please provide me with the PIT file for this device I would greatly appreciate it. (Image below is what the error is)
Click to expand...
Click to collapse
Post the link to the firmware and a screenshot of odin.

ashyx said:
Post the link to the firmware and a screenshot of odin.
Click to expand...
Click to collapse
Link to firmware: https://samsung-firmware.org/download/Galaxy Tab S 10.5/2q34/SPR/T807PVPU1ANK1/T807PSPT1ANK1/
Odin Screenshot:
View attachment 3889452
Thank you for assisting me!

irontaco1 said:
Link to firmware: https://samsung-firmware.org/download/Galaxy Tab S 10.5/2q34/SPR/T807PVPU1ANK1/T807PSPT1ANK1/
Odin Screenshot:
View attachment 3889452
Thank you for assisting me!
Click to expand...
Click to collapse
When Odin fails like that it usually means the firmware is not correct for your device.
It seems here you are trying to flash a very old kitkat firmware.
This may not be allowed by the bootloader if you are attempting to downgrade.
Try the firmware below. I also advise you upgrade your version of ODIN to at least 3.10.6
http://www.sammobile.com/firmwares/download/63988/T807PVPU1BOL3_T807PSPT1BOL3_SPR/

ashyx said:
When Odin fails like that it usually means the firmware is not correct for your device.
It seems here you are trying to flash a very old kitkat firmware.
This may not be allowed by the bootloader if you are attempting to downgrade.
Try the firmware below. I also advise you upgrade your version of ODIN to at least 3.10.6
http://www.sammobile.com/firmwares/download/63988/T807PVPU1BOL3_T807PSPT1BOL3_SPR/
Click to expand...
Click to collapse
Unfortunately I got the same results
Odin:
View attachment 3890264
I assure you that (SM-T807P) is the correct model number because I wrote it down and made sure it was correct. Unless you have the PIT file for the device I doubt I'll get it working again. It needs to be re-partitioned while the OS is installed because no matter what I flash I get the same error.

irontaco1 said:
Unfortunately I got the same results
Odin:
View attachment 3890264
I assure you that (SM-T807P) is the correct model number because I wrote it down and made sure it was correct. Unless you have the PIT file for the device I doubt I'll get it working again. It needs to be re-partitioned while the OS is installed because no matter what I flash I get the same error.
Click to expand...
Click to collapse
Pit file.
http://chomikuj.pl/WymianaLCD/GSM/FLASH/SAMSUNG/SM-T807P

ashyx said:
Pit file.
http://chomikuj.pl/WymianaLCD/GSM/FLASH/SAMSUNG/SM-T807P
Click to expand...
Click to collapse
First, thank you for finding the pit file for me. I flashed the firmware in Odin along with the pit file but this time I got a new error message I'm beginning to think this tablet is not going to recover now. I've tried three different firmwares one gave me the "invalid ext4 image" while other firmwares gave me the error message "Volume Size is too big 5120000 < 5929600"

irontaco1 said:
First, thank you for finding the pit file for me. I flashed the firmware in Odin along with the pit file but this time I got a new error message I'm beginning to think this tablet is not going to recover now. I've tried three different firmwares one gave me the "invalid ext4 image" while other firmwares gave me the error message "Volume Size is too big 5120000 < 5929600"
Click to expand...
Click to collapse
I would use Smartswitch or kies to download your firmware to ensure its correct.
Select firmware upgrade and type in your model and serial.

ashyx said:
I would use Smartswitch or kies to download your firmware to ensure its correct.
Select firmware upgrade and type in your model and serial.
Click to expand...
Click to collapse
I've already tried that method. Kies won't detect the device when I plug it in.

irontaco1 said:
I've already tried that method. Kies won't detect the device when I plug it in.
Click to expand...
Click to collapse
It doesn't need to detect it, just type in the model and serial and it will download the firmware.

ashyx said:
It doesn't need to detect it, just type in the model and serial and it will download the firmware.
Click to expand...
Click to collapse
Okay I know what the model is but I'm not sure what the serial is.

irontaco1 said:
Okay I know what the model is but I'm not sure what the serial is.
Click to expand...
Click to collapse
Its usually on a sticker on the back or on the box.

ashyx said:
Its usually on a sticker on the back or on the box.
Click to expand...
Click to collapse
I looked at the back and I didn't see anything but I took the back off and found this on the battery, is this it?

irontaco1 said:
I looked at the back and I didn't see anything but I took the back off and found this on the battery, is this it?
Click to expand...
Click to collapse
I don't think it is. I entered it in kies and it said it was wrong.

ashyx said:
Its usually on a sticker on the back or on the box.
Click to expand...
Click to collapse
I think I know why I get an error when I flash firmware now. The pit file I flashed to my tablet wasn't for the 10.5in version it was for the 7in model. I don't know if the 10.5in and 7in share the same pit file but if they don't then that's my problem.

irontaco1 said:
I don't think it is. I entered it in kies and it said it was wrong.
Click to expand...
Click to collapse
Thats the serial for the battery. Try downloading Samsung phone info. Im not sure if it gives the serial or not, cant remember.
Also not sure what you mean about the pit file, its definitely for the t807p?

ashyx said:
Thats the serial for the battery. Try downloading Samsung phone info. Im not sure if it gives the serial or not, cant remember.
Also not sure what you mean about the pit file, its definitely for the t807p?
Click to expand...
Click to collapse
I guess it is the right pit file I don't know. Where can I get this samsung phone info thing?

irontaco1 said:
I guess it is the right pit file I don't know. Where can I get this samsung phone info thing?
Click to expand...
Click to collapse
Play store.

ashyx said:
Play store.
Click to expand...
Click to collapse
I guess I forgot to mention I don't have access to the OS just download and recovery mode.

irontaco1 said:
I guess I forgot to mention I don't have access to the OS just download and recovery mode.
Click to expand...
Click to collapse
OIC. [emoji54]
You could always try flashing the custom rom made by DUHasianskillz with twrp.

Can't flash new Verizon variant S20 5G UW model with stock firmware.

For some reason none of the stock firmware files I am trying are working to flash my phone to the unlocked stock version. I have tried the latest Odin, have the drivers installed, and have tried the patched versions of Odin as well. Each time I get the obvious SHA256 error on stock, but when I try the patched versions I get a "re-partition operation failed" error and it just fails after the "set PIT file" command. Am I wrong to assume this is just another S20 model? I am making sure to use the SM-G981u1 firmware that I have tried from two different sites. The third one I can try, being from sammobile won't be done for another 6 hours because I don't want to pay $7.50 a month for a file that I have to download once.
Is there something I am doing wrong? I am using a USB 3.0 port directly on the back of my motherboard, the original cable with an adapter that came with a WD hard drive, and all the latest drivers are installed. If anyone has any tips or was successful in flashing please let me know what you did and how you got it working.
The error I get through USB 2.0 with the adapter is
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 8662 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Try using a normal 2.0 USB port. This could be the reason. Saw this issue before.

From0toHero said:
Try using a normal 2.0 USB port. This could be the reason. Saw this issue before.
Click to expand...
Click to collapse
Tried and no luck. I think the only thing to try is the firmware file from sammobile and see if that gives me any issues. I am also going to try and see if updating the phone helps at all before flashing, so that's going now. If it does work I will update the original post.

cadcamaro said:
Tried and no luck. I think the only thing to try is the firmware file from sammobile and see if that gives me any issues. I am also going to try and see if updating the phone helps at all before flashing, so that's going now. If it does work I will update the original post.
Click to expand...
Click to collapse
are u putting the pit file in pit tab? also try using patched odin.. if still fails try extracting firmware then putfing back into tar without the pit file.. u get the idea..
does it give any error on phone when u get that error in odin?

I'll give that a try tonight. I've been meaning to do a factory reset since my Bluetooth is iffy.

elliwigy said:
are u putting the pit file in pit tab? also try using patched odin.. if still fails try extracting firmware then putfing back into tar without the pit file.. u get the idea..
does it give any error on phone when u get that error in odin?
Click to expand...
Click to collapse
Stupid question, but are all csc files password protected? I have three that I tried all need a password to extract the contents.
Tried with the newest version, extracted the .pit file with 7zip and
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1401)..
<ID:0/004> File analysis..
<ID:0/004> Total Binary size: 8662 M
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004>
<ID:0/004> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Removed!
Same with G981U1UES1ATE4 version, error on the phone shows "SECURE CHECK FAIL : PIT"

Why are you trying to repartition and use a pit file?
Leave odin settings as default and load the 4 parts of the firmware into their relevant odin sections and hit start

*Detection* said:
Why are you trying to repartition and use a pit file?
Leave odin settings as default and load the 4 parts of the firmware into their relevant odin sections and hit start
Click to expand...
Click to collapse
Because that doesn't work. It flat out seems that the verizon model of the S20 is different.

cadcamaro said:
Because that doesn't work. It flat out seems that the verizon model of the S20 is different.
Click to expand...
Click to collapse
secure check fail means ur using the wrong firmware or the firmware was somehow modified..
whats your exact model and exactly what firmware are you trying to flash and where did you get it?
and no, stock firmware is not password protected.. only time ive seen password protected files is if u dl from some website that zips it and puts a password on it

elliwigy said:
secure check fail means ur using the wrong firmware or the firmware was somehow modified..
whats your exact model and exactly what firmware are you trying to flash and where did you get it?
and no, stock firmware is not password protected.. only time ive seen password protected files is if u dl from some website that zips it and puts a password on it
Click to expand...
Click to collapse
You're right, it's an SM-G981V which I thought was just a crappy way for verizon to rename their model considering they sell flashable s20+/ultra variants. It's just a totally new model though so it's not working. Also as far as the password protection, it was only on winrar and the files extracted fine in 7zip.
The fw files I've tried came from sammobile, and the download tool directly from the xda app. Multiple versions and no success.

cadcamaro said:
You're right, it's an SM-G981V which I thought was just a crappy way for verizon to rename their model considering they sell flashable s20+/ultra variants. It's just a totally new model though so it's not working. Also as far as the password protection, it was only on winrar and the files extracted fine in 7zip.
The fw files I've tried came from sammobile, and the download tool directly from the xda app. Multiple versions and no success.
Click to expand...
Click to collapse
considering u have a g981V then u are flashing wrong firmware.. u need to flash G981V firmware

elliwigy said:
considering u have a g981V then u are flashing wrong firmware.. u need to flash G981V firmware
Click to expand...
Click to collapse
The problem is I don't want the 981v firmware which is why I was trying to flash it to the carrier unlocked firmware. Either way I'm stuck with it so there's the answer for everyone else.

cadcamaro said:
The problem is I don't want the 981v firmware which is why I was trying to flash it to the carrier unlocked firmware. Either way I'm stuck with it so there's the answer for everyone else.
Click to expand...
Click to collapse
Everyone else already knew you have to flash the correct firmware for your device model....

Use frija (you can download it here on xda), punch in model SM-G981V / VZW and it should pull the firmware direct from Samsung.
If you don't want the vzw firmware, punch in XAA for the CSC. You'll need to flash it with patched Odin for it to work.

Da_G said:
Use frija (you can download it here on xda), punch in model SM-G981V / VZW and it should pull the firmware direct from Samsung.
If you don't want the vzw firmware, punch in XAA for the CSC. You'll need to flash it with patched Odin for it to work.
Click to expand...
Click to collapse
he wanted the U1 firmware lol.. the carrier specific models dont have multi csc.. he probably only has vzw csc and maybe gcf csc
he also can only flash g981v firmware since its a carrier specific model signed with different keys than U U1 W models hence his secure check fail error

Yeah, the VZW variant has physical hardware differences also, so getting a U1 firmware to flash would probably go badly as far as booting.
Looks like there are only two regions available, on SM-G981V, VZW and CCT (Comcast)
elliwigy said:
he wanted the U1 firmware lol.. the carrier specific models dont have multi csc.. he probably only has vzw csc and maybe gcf csc
he also can only flash g981v firmware since its a carrier specific model signed with different keys than U U1 W models hence his secure check fail error
Click to expand...
Click to collapse

*Detection* said:
Everyone else already knew you have to flash the correct firmware for your device model....
Click to expand...
Click to collapse
That's weird, because I routinely Flash U1 on to U, U onto XU, CZ onto literally anything I can so I can get past FRP locks... On older phones I used to flash carrier specific combination files onto the wrong devices so I had OEM unlocking in the developer options of AT&T devices. Maybe you just didn't know that it was actually a hardware limitation rather than a software limitation. I didn't. I that's why I'm here. And I know for a fact that it's possible to flash the wrong model/variant firmware onto a device, even if you don't. But hey that's XDA for you. Ask a question that requires a modicum of thought, and get a snarky answer from a "senior member" that doesn't know what they're talking about.
Anyway, to the OP, I'm also trying to flash the Xfinity splash screen off some unlocked G981V devices. It may be a lost cause because it's a hardware compatibility issue but I know a few people that might want to take a crack at it with me and I'll let you know how it goes. It was a good question. It just sucks that you always seem to get one headass in the replies.

Hi Cadcamero
In also trying to restore my S20 back to original flash.
I bought it rooted, but certain apps that I need do not work on rooted phones.
Could you by any chance share a link to the stop by step process that you follow. I've never done this before and a little overwhelmed....
I've downloaded odin ah the firmware off sammobile. Just need to now know what to do with them :silly:
Thanks a million
Lee

cadcamaro said:
The problem is I don't want the 981v firmware which is why I was trying to flash it to the carrier unlocked firmware. Either way I'm stuck with it so there's the answer for everyone else.
Click to expand...
Click to collapse
Did you ever find a solution? I am having the EXACT same problem on a Verizon S20 FE. I want to load the unlocked American XAA firmware onto it. I am getting the same error. I wonder what Verizon has come up with to stop this? I have ALWAYS done this with my Verizon phones until now.