Database Users

[Q] Help! my phone is block in factory fs

Hi!
I tried to upgrade from jpy to jvp with odin, I used the correct settings in odin but the levels get stuck in factory fs, I still have the download mode and the connection is good but nothing seems to happen. I tried again and again and it does the same everythime, any idea?

Sounds like you had a lagfix on JPY.
The only thing you can really do is pull the plug, and hope you can get back into download mode.
Flash a 3 file firmware with a 512 pit and re-partition.
Download JVP from this thread, it's a 3 file firmware.
http://forum.xda-developers.com/showthread.php?t=1102881

Thanks, actually I managed to solve the problem by reinstalling jpy without repartition, it changed my kernel to the default one as I had speedmod and and then I upgraded to jvp with repartition....thanks again for your help.

cgo372 said:
Thanks, actually I managed to solve the problem by reinstalling jpy without repartition, it changed my kernel to the default one as I had speedmod and and then I upgraded to jvp with repartition....thanks again for your help.
Click to expand...
Click to collapse
I have had this issue a number of times when flashing stock Gb firmwares, it will not flash when using .pit file for some reason..
But not selecting .pit and deselecting Repartition seems to work fine.
I have been running XXJVP for a good few days without any issues!

Here is Odin flashable EF02 upgradable to EF10 Modem with complete package

Here is the modem from EF02. Extract from zip and flash with odin. I am using it on Froyo. Use either odin version.
This allows you to do a firmware upgrade to EF10 also......again, I am using it on Froyo
Edit: I have added a zip file containing the exact files that I am successfully using to flash. Download the zip, extract the files, put the pit in the pit, the modem in the pda and flash.

shiftr182 said:
Here is the modem from EF02. Extract from zip and flash with odin. I am using it on Froyo. Use either odin version.
Click to expand...
Click to collapse
Is This 4 Real ??!?!?!?!?

do i need a pit? there's been debate over this recently

I always use a pit

CARPLUNK - this didn't work

shiftr182 said:
I always use a pit
Click to expand...
Click to collapse
Have one to spare? Apparently, I've been getting very lucky by flashing modems without one.

The Root said:
do i need a pit? there's been debate over this recently
Click to expand...
Click to collapse
NO, but it you can use it.

The Root said:
Have one to spare? Apparently, I've been getting very lucky by flashing modems without one.
Click to expand...
Click to collapse
Here is the pit. Extract from the zip.

heathmcabee said:
CARPLUNK - this didn't work
Click to expand...
Click to collapse
Has this worked for anyone yet?

I just used it(I have flashed a few times to make sure it works) . It works. Im using the old odin.

Playing with both modems now. EF02 was eh ok in my area. 4g was 5.5d 1.6 u. GPS locked faster than i've ever seen. Just pushed to EF10 and rejected it's love of looking for random updates.
Flashed back to EF02 over a thought that they're sacrificing GPS for speed or can't figure out how or why to release them in a modem together. I believe the EF02 amazing modem might be true.
Final verdict: EF02 is the ****. Instant GPS lock and 6-7mbs d/1.6 mbs u on 4g avg. I don't know what went wrong in EF10
Btw, no one got me a pit in time and now I've learned my phone clearly doesn't care.

shiftr182 said:
I just used it(I have flashed a few times to make sure it works) . It works. Im using the old odin.
Click to expand...
Click to collapse
Gonna try using the old Odin to see if I can the update. Thanks for the files though man! i dont have anymore thanks left for today, but will hit you up tomorrow with due thanks.

Make sure you extract the tar from the zip. I was trying all kinds of things to get this to work, and finally got it.

how can i get this EF02 to EF10?
i tried firmware, profile, prl but nothing it say problem while updating try again later am i doing something wrong?

shiftr182 said:
Here is the modem from EF02. Extract from zip and flash with odin. I am using it on Froyo. Use either odin version.
This allows you to do a firmware upgrade to EF10 also......again, I am using it on Froyo
Edit: I have added a zip file containing the exact files that I am successfully using to flash. Download the zip, extract the files, put the pit in the pit, the modem in the pda and flash.
Click to expand...
Click to collapse
Please help. Did I just brick my phone? Here's what I did.
Saved and extracted the pit and the modem to the desktop
Booted phone to Download mode
Opened Odin and selected the PIT in the PIT area and the Modem in the Phone slot.
Click Start.
Odin went through ok.
Phone rebooted. But never came back on.
Only at that time did I realize that the Re-Partition box was also checked.
I know... 2 mistakes. Phone slot instead of PDA and Re-Partition was checked.
Is there anything I can do? I've tried booting normally. Booting to download mode. Booting to CWM. First night of rooting and it was going so well until I started to try different modems.

romowens01 said:
Please help. Did I just brick my phone? Here's what I did.
Saved and extracted the pit and the modem to the desktop
Booted phone to Download mode
Opened Odin and selected the PIT in the PIT area and the Modem in the Phone slot.
Click Start.
Odin went through ok.
Phone rebooted. But never came back on.
Only at that time did I realize that the Re-Partition box was also checked.
I know... 2 mistakes. Phone slot instead of PDA and Re-Partition was checked.
Is there anything I can do? I've tried booting normally. Booting to download mode. Booting to CWM. First night of rooting and it was going so well until I started to try different modems.
Click to expand...
Click to collapse
Sorry. Found out a way to fix.
(Take battery out. Hold 1 + Power. Put battery back in).
Was able to reload everything back to stock.
Thought the phone was a goner. Had no signs of life at all.

Camera Failed

Hi Guys,
Currently Running 2.3.3 I9000XXJVK and when i open the camera , where the picture is ment to be is Black and after a Few minutes it Says "Warning Camera Failed" My SGS is not Rooted
Ive Reinstalled 2.3.3 and Its still not working.
Do you have any Idea What I need to do to fix this?
If I need to root the device to fix this , Please link me to the Root Image Please
Thanks

Anyone??????

if you dont have a long list of apps, why not try download JVP firmware..
when u r installing 2.3.3 JVK, r u doing it via kies or Odin?
if u r flashing thru odin, r u doing it through a 3 part package or a single .tar file ?
please try with a 3 part package, select .512 PIT file, click re-partition.

lycan_codex said:
if you dont have a long list of apps, why not try download JVP firmware..
when u r installing 2.3.3 JVK, r u doing it via kies or Odin?
if u r flashing thru odin, r u doing it through a 3 part package or a single .tar file ?
please try with a 3 part package, select .512 PIT file, click re-partition.
Click to expand...
Click to collapse
There Doesn't appear to be a JVP Firmware for 2.3.3 - Im in the UK (Europe)
If i Use a 512.Pit File - is that re-installing the Phone from Scratch? - I think the Camera's Files has become Damaged - Would a 3 Part Firmware Have The firmware for the camera included on the formware?
the 512 pit files - are the ones on samfirmware safe to use? I supose where it says 512 pit next to the firmware name you use a 512 pit file?? on samfirmware??

Spitfire22 said:
There Doesn't appear to be a JVP Firmware for 2.3.3 - Im in the UK (Europe)
If i Use a 512.Pit File - is that re-installing the Phone from Scratch? - I think the Camera's Files has become Damaged - Would a 3 Part Firmware Have The firmware for the camera included on the formware?
the 512 pit files - are the ones on samfirmware safe to use? I supose where it says 512 pit next to the firmware name you use a 512 pit file?? on samfirmware??
Click to expand...
Click to collapse
yes, using re-partition is like reinstalling phone from scratch!
JVP is 2.3.4 firmware which was leaked few weeks back. For official stock one, pick a firmware for your region. make sure its a 3 part one. use the .512 PIT. There is a thread in the general section by RAMAD where he has listed almost all stock firmwares region wise. Download the firmware from there.
I am assuming you have 3e recovery.

lycan_codex said:
yes, using re-partition is like reinstalling phone from scratch!
JVP is 2.3.4 firmware which was leaked few weeks back. For official stock one, pick a firmware for your region. make sure its a 3 part one. use the .512 PIT. There is a thread in the general section by RAMAD where he has listed almost all stock firmwares region wise. Download the firmware from there.
I am assuming you have 3e recovery.
Click to expand...
Click to collapse
This Didn't Work

Spitfire22 said:
This Didn't Work
Click to expand...
Click to collapse
Can you please elaborate what you did?

I Used Odin with a 512 Pit , And 3 Files
it Flashed OK - Phone Booted up Ok - But still no Camera - everything else is working fine

Any Other Advise from other Members?

Spitfire22 said:
Any Other Advise from other Members?
Click to expand...
Click to collapse
this feels to me like a hardware failure.

my phone does exactly the same but i put *#34971539# (Camera Firmware Update) and after i updated ...camera failure.....so what can i do....i tryed 4 version 2.2.1 jpk jpy and 6 factory reset and one full factory reset.,...nothing works....please help me....what can i do.... in samsung kies there is something wiht install drivers.....can i connect my phone and and install some drivers.....maybe works?help me

Man if you dialed *#34971539# and "updated" the driver you probably have opsbdd07 or smth like that ...
reinstalling a rom will not work..
1.so search xda for samsung wave camera firmware for sgs the copy the files with rootexplorer in a folder i don`t remeber the name but its camera related
OR
2.you can "brick" your phone and send it to a samsung/carrer service and tell them that when you woked up your phone stoped working OR tell them you did a hard reset and the boom the camera stopt working
i did both variants but finaly i sent my phone in service it worked

[Q] Hong Kong 32GB n9005 and PIT

I want to flash an Aussie ROM on my HK 32GB n9005. I've been doing some reading and what I think I need to do is as follows...
ghibli3's thread at http://forum.xda-developers.com/showthread.php?t=2550823 specifically addresses this issue and thanks to those contributing there and elsewhere.
Now to check I understand what they are saying before I brick my phone.
I have these:
CSB_signed_HLTE_EUR_OPEN_32G_0718.pit
CSB_signed_HLTE_EUR_OPEN_32G_0805.pit
ghibli3-N9005.pit
ratcom-N9005.pit
I also used ghibli3's N9005-SaveMyPit from http://forum.xda-developers.com/attachment.php?attachmentid=2426123&d=1385903491 to get a copy of my current pit.
I have my original HK MI7 stock, a HK stock MK2 (used to root my phone originally using RDLV) and both an MI7 and MJ7 Aussie ROMs.
So... here is what I think I need to do... Please let me know if this is correct or tell me how to do it better.
Using Odin and with phone in DL mode, USB Debugging on, Samsung drivers and ADB setup on PC...
1. Load a PIT file in [PIT] in Odin and tick [Re-Partition] then [Start]
(1st question, do I reboot the phone or just go to the next step?)
2. Follow RDLV steps to flash the Aussie MJ7 to root the phone.
(2nd question, should I drop back to the MI7 version for the root operation? I don't think it is needed as when I rooted my phone with HK version, I had HK MI7 on the phone and used HK MK2 to root it)
(3rd question, I have Kies 3 on my PC - should I uninstall it before doing any of this or might it be helpful to have it still installed?)

OK, so no comments so far... let's try a slightly different approach.
(4th question, Can I load the PIT into Odin, tick [Re-Partition] and add in the VEGA version of the AP (from RDLV) and then flash them as one?

Journyman16 said:
OK, so no comments so far... let's try a slightly different approach.
(4th question, Can I load the PIT into Odin, tick [Re-Partition] and add in the VEGA version of the AP (from RDLV) and then flash them as one?
Click to expand...
Click to collapse
For using PIT file, you need to add the PIT to Odin when you flash so it'll repartition as it's flashing. However, don't take that as a solid cause I am not 100% sure myself as I haven't messed with PIT files (yet) - but from what I have read that is how it is done. - Have a scan through the HK bricked (solved) threads to be doubley sure cause yeah, it's easy to end up with a brick

Thanks for that. Kinda what I was planning to do but I'm not sure if I do the PIT flash first then do the rest or if I do it all as one process. I'll check out that thread... been looking anywhere I could find a PIT reference.

Well, that was fun... not.
I tried the PIT files with NAND erase all, re-partition f. reset time and Auto reboot all ticked - it failed - I got a systemconnection error. I tried again with each of the PITs listed above except ratcom's - his is from an MJ7 build and I was unsure if that would trip Knox or not.
2 hours pass, with me looking all around XDA and trying a variety of things. Incidentally I think maybe the systemconnect thing might be related to not restarting the phone to get the error screen. It seems Odin can do things when that screen is on that it can't do in plain Download mode. At least, on mine, the eventual fix worked only AFTER I had the error screen (shows the hone pic and a PC pic)
I didn't try flashing CWM. Nor doing anything that might add an MJ7 or KK bootloader. If I trip Knox I want it to be by my choice, not because I can't fix something.
But clearly I am doing something wrong in trying to repartition my phone - none of the PIT flashes worked. None of the flash ROM's worked. I looked around for a MJ3 or less ROM with the 4 files - figured I could get that I could try using a PIT for the right CSC and those files and solve both issues at once.
I tried my MK1 HK Vega image and no go. So I sat and thought it through and realised that last time I had problems I had the error screen NOT download mode so I rebooted the phone and Voila! up popped the error screen. Odin promptly flashed my HK MK1 version and now I am restoring my apps from the extSDcard. Got a bit of setup work to do but it's up and running again.
But I will have to trip Knox now - I'm sick of not having a Nandroid backup that could just restore everything where it was instead of me having to manually put things back as they were.
Any ideas as to what I did wrong?

Journyman16 said:
Well, that was fun... not.
I tried the PIT files with NAND erase all, re-partition f. reset time and Auto reboot all ticked - it failed - I got a systemconnection error. I tried again with each of the PITs listed above except ratcom's - his is from an MJ7 build and I was unsure if that would trip Knox or not.
2 hours pass, with me looking all around XDA and trying a variety of things. Incidentally I think maybe the systemconnect thing might be related to not restarting the phone to get the error screen. It seems Odin can do things when that screen is on that it can't do in plain Download mode. At least, on mine, the eventual fix worked only AFTER I had the error screen (shows the hone pic and a PC pic)
I didn't try flashing CWM. Nor doing anything that might add an MJ7 or KK bootloader. If I trip Knox I want it to be by my choice, not because I can't fix something.
But clearly I am doing something wrong in trying to repartition my phone - none of the PIT flashes worked. None of the flash ROM's worked. I looked around for a MJ3 or less ROM with the 4 files - figured I could get that I could try using a PIT for the right CSC and those files and solve both issues at once.
I tried my MK1 HK Vega image and no go. So I sat and thought it through and realised that last time I had problems I had the error screen NOT download mode so I rebooted the phone and Voila! up popped the error screen. Odin promptly flashed my HK MK1 version and now I am restoring my apps from the extSDcard. Got a bit of setup work to do but it's up and running again.
But I will have to trip Knox now - I'm sick of not having a Nandroid backup that could just restore everything where it was instead of me having to manually put things back as they were.
Any ideas as to what I did wrong?
Click to expand...
Click to collapse
2nd link in my signature.
Follow it to step 6. Then flash whatever ROM you want. Make sure your phone is 32 gigs or more. Won't work on 16 gb version.

So this gets a bit strange now... I downloaded Phone Info from Play Store and ran it. I did that because I noticed I was having Wifi issues - it was working but kept thinking it was off - I'd click it to turn it on and the button wouldn't go green, but I had signal in the Notification bar. Going to Recovery to clear cache showed it was now applying CSC-code as BTU instead of TGY, so SOMETHING worked when I was doing the PITs.
So, Phone Info shows my Region Code as BTU, my CSC country as UK/IRE and my CSC Country ISO as GBBut I have a mix of ROM info:
Bootloader: ZHUBMI7
Baseband: ZHUDMJ9
PDA: XXUDMK2
CSC: OXADMK2
So, PDA and CSC are from a UK MK2 I tried to use early on and failed with, while BL and BB are from the original HK MI7 (BL) and the HK MK1 I rooted with.
So my question is now, can I now flash a BTU or other normal ROM onto my phone, using the RDLV process to make sure I get root and don't trip Knox?
IIRC I think the process works up to MK2 (and certainly does to MK1 as that what I used originally) so I should be able to DL (say) XXUBMJ1 to use for the BL and use XXUDMK2 for the root process. (i.e. the same as I did using HK MI7 for the BL and HK MK1 for the root process)
3 questions:
1. Is it the PDA that determines the partition Hong Kong users have such problems with? Or is it the Bootloader?
2. Can anyone think of a reason why this would not work? (now my CSC is BTU)
3. Could I now use an Aussie ROM to run the RDLV process?

FeralFire said:
2nd link in my signature.
Follow it to step 6. Then flash whatever ROM you want. Make sure your phone is 32 gigs or more. Won't work on 16 gb version.
Click to expand...
Click to collapse
Thanks for the Reply.
For now I'd prefer to stay away from KK ROMs - too many people having issues, and the prevention of returning to 4.3 is, to me, a killer until Samsung get the bugs out. Given that many people are doing OK with KK, I think it is unlikely Samsung will do much about the bugs until a larger number of people have problems and start bombarding their support lines.
Plus, on 4.3 I have a very fast phone that gives more than 2 days use even with fairly heavy use (for me) and up to 4 days for light use. Why make an irreversible change when the phone is doing well already? For me the next step is custom recovery - I don't like not having a Nandroid BU and several times now after restoring apps I find I need to fix permissions - without custom recovery that means a laborious uninstall/reinstall from Play Store, one app at a time. Pisses me off...
I find it interesting that Samsung are clearly using users such as XDA members as their testing area, while at the same time shutting down the activities we like to do. (Custom ROMs etc) I say clearly using us because otherwise there is no excuse for the regularity of leaked ROMs - Samsung pass it on to us to try and I would bet, have staff watching us to see what issues we have.
So it seems a bit counter-productive to work so hard to lock the phones so we can't play with them.

Journyman16 said:
Thanks for the Reply.
For now I'd prefer to stay away from KK ROMs - too many people having issues, and the prevention of returning to 4.3 is, to me, a killer until Samsung get the bugs out. Given that many people are doing OK with KK, I think it is unlikely Samsung will do much about the bugs until a larger number of people have problems and start bombarding their support lines.
Plus, on 4.3 I have a very fast phone that gives more than 2 days use even with fairly heavy use (for me) and up to 4 days for light use. Why make an irreversible change when the phone is doing well already? For me the next step is custom recovery - I don't like not having a Nandroid BU and several times now after restoring apps I find I need to fix permissions - without custom recovery that means a laborious uninstall/reinstall from Play Store, one app at a time. Pisses me off...
I find it interesting that Samsung are clearly using users such as XDA members as their testing area, while at the same time shutting down the activities we like to do. (Custom ROMs etc) I say clearly using us because otherwise there is no excuse for the regularity of leaked ROMs - Samsung pass it on to us to try and I would bet, have staff watching us to see what issues we have.
So it seems a bit counter-productive to work so hard to lock the phones so we can't play with them.
Click to expand...
Click to collapse
You need the international pit file in your phone. Flashing the CSC file will put that pit in your phone. It won't touch the bootloader or the system files.

FeralFire said:
You need the international pit file in your phone. Flashing the CSC file will put that pit in your phone. It won't touch the bootloader or the system files.
Click to expand...
Click to collapse
Unfortunately, PIT's don't seem to come easy. As above I have about 4 of them I tried. There seems a bit of a disconnect between what the AP/CP/CSC are and what the files in a ROM are e.g. in XXUBMH1 there's boot.img, recovery.img, system.img.ext4, userdata.img.ext4, persdata.img.ext4, persist.img.ext4 and in XXUBMI7 there's sbl1.mbn, aboot.mbn, rpm.mbn, tz.mbn, sdi.mbn, NON-HLOS.bin, boot.img, recovery.img, system.img.ext4, modem.bin, cache.img.ext4, hidden.img.ext4
While I've been around a while now, this seems to be a blank spot for me at present - how do I flash a CSC? From reading it seems some ROM.s come with 4 or 5 files, e.g. see attachment - but I haven't been able to find one yet. (the one in the pic was hosted on Hotfiles which is now defunct thanks to the Almighty USA draconian control freaks. )
Update: I think I have found a copy of it so I can try that when it finishes DL'ing.
Other than that, anyone know of where there might be another such ROM to DL? Also if I am flashing a CSC file do I flash the PIT as well (i.e. at the same time) or do the PIT first?
Which Odin options get ticked for a PIT? I tried [F. Reset Time] [Re-Partition] [Auto Reboot] [Nand Erase All] previously and it didn't seem to work. I saw a recovery type post that suggested ticking [Phone EFS Clear] but seems to me that is a tick towards Brick - and the Recovery being offered was to a KK ROM anyway.

FeralFire said:
2nd link in my signature.
Follow it to step 6. Then flash whatever ROM you want. Make sure your phone is 32 gigs or more. Won't work on 16 gb version.
Click to expand...
Click to collapse
FeralFire said:
You need the international pit file in your phone. Flashing the CSC file will put that pit in your phone. It won't touch the bootloader or the system files.
Click to expand...
Click to collapse
I just looked at your post again - I realise I might have a wrong idea. Although the leaked ROM is KK, I was assuming flashing the CSC would upgrade my phone - is that the case or can I use your 6 steps just to change my PIT and then do the 4.3 RDLV process to have a root 4.3 phone?
Downloading it now - started with the torrent but that's running slow; I will let it run to completion to maybe help some others get it faster but I've got the Storage Cow one running as well. We'll see which one arrives first Either way I'll leave it seeding.

Journyman16 said:
I just looked at your post again - I realise I might have a wrong idea. Although the leaked ROM is KK, I was assuming flashing the CSC would upgrade my phone - is that the case or can I use your 6 steps just to change my PIT and then do the 4.3 RDLV process to have a root 4.3 phone?
Downloading it now - started with the torrent but that's running slow; I will let it run to completion to maybe help some others get it faster but I've got the Storage Cow one running as well. We'll see which one arrives first Either way I'll leave it seeding.
Click to expand...
Click to collapse
Yeah, you should be able to.
I tried flashing the MK2 ROM after flashing that CSC. It worked perfectly. But then I upgraded to kitkat. So I can't test JB stuff anymore.

FeralFire said:
Yeah, you should be able to.
I tried flashing the MK2 ROM after flashing that CSC. It worked perfectly. But then I upgraded to kitkat. So I can't test JB stuff anymore.
Click to expand...
Click to collapse
Well, it let me flash the vega BTU MK2 ROM but now there's a wifi problem. Still waiting for cygwin to download so I can RDLV on the XSA ROM. There seems to be some kind of conflict between BTU and Australian settings. Says to turn on wireless and actually finds my SSID's but then doesn't connect properly. le sigh...

Well it's been coming up to 24 hours with no phone but I seem to have found my way.
The problem seems to have been a mismatch between BL, CSC and PIT. In trying to get off the Hong Kong set up I wound up with a ZHU BL, BTU CSC and XSA CP and AP. It worked but I had no wifi. tried a few things to get it working and in trying to flash an XSA CSC (I think it was XSA) I got the Knox bit change. With no wifi I thought maybe the problem was the BUT-based CP needed changing. In trying to fix that, somehow I triggered Knox
I tried DL & Install of Omega 6 (it's a 4.3 - not ready to go KK yet) but although it completed nicely (so many ROM's got hidden or system errors in Odin) the phone didn't start. I tried installing Philz so I could run things from the extSDcard but an XSA wouldn't work nor would anything I had below MJ7. Last Phone Info view I had I still had a ZHU CP, even though AP and CSC were XSA-based.
Finally I got the MJ7 ROM from http://forum.xda-developers.com/sho...9005xxudmj7-pre-rooted-knox-free-odex-bl-free and it did the trick.
It's been a learning experience but I'd be happier if I knew for sure both what triggered the Knox bit (I was being very careful about it) and why some of the other ROM installs simply didn't work.

Resurrecting this one because I'm looking for info on flashing my 32G HK Note 3, but it came with KK pre-installed. So I'm not sure what differences I have to be aware of. Any tips?

For whoever still experiences issues with HK 32GB n9005 devices, After wasting half a day on that crap, i was able to flash N9005ZSUGOK2_N9005OZSGOK2_TGY from sammobile coupled with the PIT attached.

sm-n900
sm-900 and pit

[Solved] Need Guidance flashing stock on SM-935V.

The other day I followed the thread
Root_Method_Rev_B/11_Bootloader_Using_Combo_Firmware
This is a root method for the s7 and s7 edge on bootloader 11 (B) phones using the combination firmware. I really dont think it will do much but I will post it and maybe someone will do something with it Downloads...
forum.xda-developers.com
and though it works it is super buggy and constant crashes after reflashing several times. SO I wish to return the phone to complete stock. Is there a way to do this? I have read over several post about this and I just get errors or varying results no matter what method/rom I try to use.

panowolf said:
The other day I followed the thread
Root_Method_Rev_B/11_Bootloader_Using_Combo_Firmware
This is a root method for the s7 and s7 edge on bootloader 11 (B) phones using the combination firmware. I really dont think it will do much but I will post it and maybe someone will do something with it Downloads...
forum.xda-developers.com
and though it works it is super buggy and constant crashes after reflashing several times. SO I wish to return the phone to complete stock. Is there a way to do this? I have read over several post about this and I just get errors or varying results no matter what method/rom I try to use.
Click to expand...
Click to collapse
What version of Odin are you using, and what firmware are you trying to flash?
Have you tried a different USB cable?
Generally flashing Samsung devices works pretty much the same. If you're returning to stock from a custom ROM or otherwise want to wipe data, use the CSC_xxxxx instead of HOME_CSC_xxxxx file in the CSC slot. Data doesn't mix and match well, so if you didn't wipe after coming from a custom ROM or other firmware, that could be the reason for the instability.

V0latyle said:
What version of Odin are you using, and what firmware are you trying to flash?
Have you tried a different USB cable?
Generally flashing Samsung devices works pretty much the same. If you're returning to stock from a custom ROM or otherwise want to wipe data, use the CSC_xxxxx instead of HOME_CSC_xxxxx file in the CSC slot. Data doesn't mix and match well, so if you didn't wipe after coming from a custom ROM or other firmware, that could be the reason for the instability.
Click to expand...
Click to collapse
I've tried several ODIN versions. 3.12,3.13, 3.14, 2 different modified versions and it seems to be the same.
I have tried 3 different cables, no change.
I have tried using the normal CSC and HOME_CSC but I still return errors.
I can flash the combination firmware and the stock MM rom listed in the original post but no matter what other post I try to follow I can not get any to take. How can I get rid of this combination firmware and return to stock completely?

panowolf said:
I've tried several ODIN versions. 3.12,3.13, 3.14, 2 different modified versions and it seems to be the same.
I have tried 3 different cables, no change.
I have tried using the normal CSC and HOME_CSC but I still return errors.
I can flash the combination firmware and the stock MM rom listed in the original post but no matter what other post I try to follow I can not get any to take. How can I get rid of this combination firmware and return to stock completely?
Click to expand...
Click to collapse
I think what you need to do is re-partition the device using the factory PIT file that's located in the CSC package. In the Odin options tab, check the NAND Erase and Re-Partition boxes, then in the PIT tab, select the PIT file you extracted from the CSC_xxxx.tar
DO NOT check Re-Partition without using the PIT file. Make sure you're using the correct firmware for your device as this could result in a brick.

V0latyle said:
I think what you need to do is re-partition the device using the factory PIT file that's located in the CSC package. In the Odin options tab, check the NAND Erase and Re-Partition boxes, then in the PIT tab, select the PIT file you extracted from the CSC_xxxx.tar
DO NOT check Re-Partition without using the PIT file. Make sure you're using the correct firmware for your device as this could result in a brick.
Click to expand...
Click to collapse
Where should I get the PIT file from? Any particular site/rom file?

panowolf said:
Where should I get the PIT file from? Any particular site/rom file?
Click to expand...
Click to collapse
As I stated above, it should be in the CSC file.

Well, after many many hours of trying what seems like countless roms/files I have finally got it back to stock Oreo but the lag and stability is horrible. It is pretty much unusable, music apps crash/stutter, Playstore takes about 3 minutes to start up and can't even be scrolled through, returning to the home screen takes about 2 minutes as you watch each and every element load in one at a time including the wallpaper. I think the phone is trash now? I'm on B/11 (G935VVRSBCTC1) if that helps with any suggestions.

panowolf said:
Well, after many many hours of trying what seems like countless roms/files I have finally got it back to stock Oreo but the lag and stability is horrible. It is pretty much unusable, music apps crash/stutter, Playstore takes about 3 minutes to start up and can't even be scrolled through, returning to the home screen takes about 2 minutes as you watch each and every element load in one at a time including the wallpaper. I think the phone is trash now? I'm on B/11 (G935VVRSBCTC1) if that helps with any suggestions.
Click to expand...
Click to collapse
did you flash stock with odin?

Sorry for the late reply. Yes, I got the rom from samfw and flashed with Odin. Then I tried using Smart switch to update it and it was all successful but the phone is still fairly jittery. It's not as bad as it was on the combo rom but music apps still stutter and the system overall is pretty laggy.
Side note: The phone ran like new prior to flashing the combo rom.
jrkruse said:
did you flash stock with odin?
Click to expand...
Click to collapse

panowolf said:
Sorry for the late reply. Yes, I got the rom from samfw and flashed with Odin. Then I tried using Smart switch to update it and it was all successful but the phone is still fairly jittery. It's not as bad as it was on the combo rom but music apps still stutter and the system overall is pretty laggy.
Side note: The phone ran like new prior to flashing the combo rom.
Click to expand...
Click to collapse
You need to extract the pit file from the stock firmware regular CSC file and load it in the pit tab in odin along with the other files and you need to flash regular CSC not home CSC

jrkruse said:
You need to extract the pit file from the stock firmware regular CSC file and load it in the pit tab in odin along with the other files and you need to flash regular CSC not home CSC
Click to expand...
Click to collapse
I did. I'll try it again Monday and see if it makes any difference. I appreciate the help.

panowolf said:
I did. I'll try it again Monday and see if it makes any difference. I appreciate the help.
Click to expand...
Click to collapse
it sounds like you didnt wipe data so reboot too stock recovery and wipe data

I think it's running about as good as it's going to. I reflashed the stock Oreo firmware and extracted the pit, nand erase, re-partitioned, wiped data /cache. Still a bit jittery but it'll do. Just need it to play music while at work.
Thanks for the advice.