G930TUVS4BQL2_CL12142063_QB16000831_REV02_user_low_ship_MULTI_CERT_meta.tar.rar
Thanks. I will try it on my boot looped SM-G930T tonight.
First off, Thank you to muniz_ri for the zip.
I have a 930A (S7) running ATT firmware and having some issues every now and then running the ATT firmware on TMobile (my phone suddenly is not recognized by TMo and 4G data stops working. I have to switch the SIM card with another TMo user and switch back to my SIM and it starts working...).
I tried to load the previous version yesterday of the TMo firmware posted by muniz_ri (G930TUVS4BQJ2) and Odin (Prince) failed with a Write failure- some file was larger than could be written (ext4 fail). It then stuck at boot.
I was able to recover by flashing the ATT firmware back again.
Question- How do I get this latest TMo firmware onto the phone? Do I need to repartition or something?
Thanks for your time.
webzo said:
First off, Thank you to muniz_ri for the zip.
I have a 930A (S7) running ATT firmware and having some issues every now and then running the ATT firmware on TMobile (my phone suddenly is not recognized by TMo and 4G data stops working. I have to switch the SIM card with another TMo user and switch back to my SIM and it starts working...).
I tried to load the previous version yesterday of the TMo firmware posted by muniz_ri (G930TUVS4BQJ2) and Odin (Prince) failed with a Write failure- some file was larger than could be written (ext4 fail). It then stuck at boot.
I was able to recover by flashing the ATT firmware back again.
Question- How do I get this latest TMo firmware onto the phone? Do I need to repartition or something?
Thanks for your time.
Click to expand...
Click to collapse
I figured I would try flashing the new software you have provided above, and maybe have better luck. But no, still same deal. I captured the log messages this time-
Odin stated-
system.img.ext4
FAIL! (ext4)
Complete (write) operation failed
On the phone, I see this-
Volume size is too big 1228800 < 1254400
ODIN: Invalid ext image
[18] eMMC write fail system
So, something is too big to be written into the existing partition, I guess.
It sounds like, reading through some posts, I need to use a PIT file and re-partition or something
Any ideas on how to approach this?
By the way, yesterday, I was able to get out of the boot loop by using Odin Prince Comsey to flash to G930AUCS4BQE1 (ATT firmware from june-2017)
Today, Prince comsey wouldn't work. It ended up at-
FAIL! Model dismatch fail
After some digging around, it seemed like Odin Prince Comsey is not to be used for Stock ROMs... tried with Odin 3.12.3 and that never got past "SetupConnection". Tried again with Odin 3.12.10 and that worked.
Anyway, back to the problem at hand.... I am at G930AUCS4BQE1 (ATT from June) and need to get to G930TUVS4BQL2 (TMo, December) or G930UUEU4BQJ5 (latest 930U).
Any pointers are greatly appreciated..
Thanks.
I believe flashing the csc file rather than the home_csc automatically reformats the partitions for the rom you are flashing. If it does not, you are correct that you need the pit file which is used to reformat partitions accordingly. The pit file for TMobile can be found around this forum.
Related
Hello peeps a Happy New Year to all!
I tried searching the forums and google but no luck on my case. I am trying to install hyperdrive and am following instructions, downloaded files multiple times on multiple computers and i337m itself. Aroma opens fine and works through fine untill it tries to flash kernel it says:
flashing kernel
file_getprop: failed to stat "/tmp/aroma/kernel.prop": No such file or directory.
So I thought it was just missing a kernel, so continued and installed the att compatibility pack and all i get is ODIN/download mode. I then tried flashing kstoonez kernel and same thing.
I am using Philz Touch latest version on Canadian s4
Any ideas?
The_SilverOne said:
Hello peeps a Happy New Year to all!
I tried searching the forums and google but no luck on my case. I am trying to install hyperdrive and am following instructions, downloaded files multiple times on multiple computers and i337m itself. Aroma opens fine and works through fine untill it tries to flash kernel it says:
flashing kernel
file_getprop: failed to stat "/tmp/aroma/kernel.prop": No such file or directory.
So I thought it was just missing a kernel, so continued and installed the att compatibility pack and all i get is ODIN/download mode. I then tried flashing kstoonez kernel and same thing.
I am using Philz Touch latest version on Canadian s4
Any ideas?
Click to expand...
Click to collapse
The kernel message was no problem for me.using safe strap?
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
the kernel error is common just proceed as you did
did you wipe all including system before flashing? i don't usually wipe in aroma unless no choice given
did you choose your correct carrier--who is your carrier--that info helps us tp help you--
i don't have i337m so can't be specific on things relating to that phone. you say i337m and i337 is in your sig
if you have i337 you need to flash loki-doki after rom
maybe try twrp--i use 2.5.0.2--i have, and there is a flashable zip for it (i337)
got to go for now--
rugmankc said:
the kernel error is common just proceed as you did
did you wipe all including system before flashing? i don't usually wipe in aroma unless no choice given
did you choose your correct carrier--who is your carrier--that info helps us tp help you--
i don't have i337m so can't be specific on things relating to that phone. you say i337m and i337 is in your sig
if you have i337 you need to flash loki-doki after rom
maybe try twrp--i use 2.5.0.2--i have, and there is a flashable zip for it (i337)
got to go for now--
Click to expand...
Click to collapse
Thank you both for your replys, your help is very much appreciated.
So I wiped it with recovery not aroma.
Carrier is Fido (Rogers subsidiary)
Phone is Canadian S4 variant (SGH-I337m) I believe it is the same as i337 (The m being a canadian designation) but don't quote me on that.
I was under the assumption that Canadian s4 Didn't need lokidoki.
Can you elaborate on safestrap?
No matter what I try it goes boots to download mode. Even if I plug it in to charge not pressing any power button.
Canadian s4 doesnt need loki doki. And your not on safestrap if you have twrp.
As far as your problem. Did it complete the install of the rom even after it said it failed the kernel?
I suggest installing then flashing a 4.3 tw kernel for your device before rebooting system. You shouldn't need a compatibility pack as your not att. Plus im pretty sure the compat pack has loki in it which may cause problems. I also remember philz recovery as having auto loki. So I dont know if you've used philz recovery b4 successfully. If you haven't then id suggest trying twrp. Definitely just try a kernel for your device though. Ktoons worked for me. Other kernels left me stuck at spash screen
SelfElevated2 said:
Canadian s4 doesnt need loki doki. And your not on safestrap if you have twrp.
Click to expand...
Click to collapse
I believe that my phone's bootloader is unlocked (as with most other jtflecan models), but again don't quote me. As a result I have never used safestrap. Should/could I still use it if my bootloader is unlocked?
SelfElevated2 said:
As far as your problem. Did it complete the install of the rom even after it said it failed the kernel?
Click to expand...
Click to collapse
It seemed that way as that was the only error, and aroma proceeded through. First time I tried without the ATT compatibility pack, no go, then with and still no go. Then i tried with a few kernels and same thing.
SelfElevated2 said:
I suggest installing then flashing a 4.3 tw kernel for your device before rebooting system. You shouldn't need a compatibility pack as your not att. Plus im pretty sure the compat pack has loki in it which may cause problems. I also remember philz recovery as having auto loki. So I dont know if you've used philz recovery b4 successfully. If you haven't then id suggest trying twrp. Definitely just try a kernel for your device though. Ktoons worked for me. Other kernels left me stuck at spash screen
Click to expand...
Click to collapse
I transitioned from cwm to philz for ntfs capability as my external sdcard is ntfs. I remember reading somewhere that autoloki was not included and some have complained about it so im not sure if it was added in a later build. In any case I just tried flashing twrp and got a mushy brick.
Now Im curious if I should restore to original and use safestrap or what as my phone does nothing but odin mode.
As always thanks for your valued input.
Your boot loader is definitely not locked. If it was you wouldnt have a custom recovery. So you don't need safestrap. Just restore and reroot and get a recovery. What you put on your phone after that is up to you. I know hyperdrive wouldn't boot for me with most kernels it was just stuck on the splash screen. But it booted for kt kernel. I would honestly find another Rom if I was in the same position
MINI UPDATE:
Phone was bootlooping so I tried to restore to stock 4.2.2 but ODIN failed continuously. Tried 4.3 stock (mk6) and odin failed, tried older odin and succeeded but it bootlooped and went to the kies upgrade error. Tried multiple Computers (2PC 1OSX) multiple ports and cables and all failed.
Trying to figure this out but not much help out there with regards to canadian s4, att guides ok? any suggestions? trying kies restore now but kies hangs after it downloads firmware. urgh
ODIN Outuput:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I337MVLUEMK6_I337MOYAEMK6_I337MVLUEMK6_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> __Xmit Write fail
<ID:0/003> XmitData Fail..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
ODIN seems to fail at different points, sometimes in recovery, or modem or etc.
do i need to repartition?if so where do i find the pit file for my device?
im reading that im screwed and praying its not true.
Thanks for any help
You cant get into recovery? Only odin? Just keep looking around. I bet its because the aroma flashed a incomplete flash. But I dont know the difference between i337 and i337m so I dont know what to tell you. I suggest keep trying to Odin. If it doesn't work I believe theres a tool to force a stock image onto the phone but I cant remember what its called
SelfElevated2 said:
You cant get into recovery? Only odin? Just keep looking around. I bet its because the aroma flashed a incomplete flash. But I dont know the difference between i337 and i337m so I dont know what to tell you. I suggest keep trying to Odin. If it doesn't work I believe theres a tool to force a stock image onto the phone but I cant remember what its called
Click to expand...
Click to collapse
no i only get odin.
phone only turns on when plugged in to usb on pc, otherwise unresponsive to hardkeys.
Every instance of ODIN flashing fails. No matter which firmware or computer i used, either write failure or PIT failure. both of which im attributing to an incomplete flash, and its making me think that the partition tables are chewed.
im stumped and phonless
any idea what that app was called? google yields no results
thanks for your help
Heres something to read. I dont know if you need the.Canadian pit or reg att pit. Dont just flash one. Get informed first
http://www.droidviews.com/how-to-unbrick-your-bricked-samsung-galaxy-s4-gt-i9500-gt-i9505/
SelfElevated2 said:
Heres something to read. I dont know if you need the.Canadian pit or reg att pit. Dont just flash one. Get informed first
http://www.droidviews.com/how-to-unbrick-your-bricked-samsung-galaxy-s4-gt-i9500-gt-i9505/
Click to expand...
Click to collapse
Thank you very much for that link. It summed up everything i have been reading for the past 24 hours, but alas i have yet to figure out which pit to use, whether I can use the att pit, wind (different provider, uses aws (2 different frequencies from gsm standard) as opposed to gsm although they may have changed that recently),find a rogers pit, since they and fido are essentially the same network or continue searching for a fido pit.
Knowing what the pit does, would it really be carrier specific (asides from the difference in radios between fido/rogers and wind)? Is it ROM version and android version specific?
Update:
-Have Tried all options for recovery in KIES on multiple Pcs and Multiple Macs
-Download/Odin Mode Reads:
ODIN MODE
PRODUCT NAME: SGH-I337M
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
KNOX KERNEL LOCK: 0x0
KNOX WARRANTY VOID: 0x1
CSB-CONFIG-LSB; 0x30
WRITE PROTECTION: Enable
eMMC BURST MODE: enabled
START [224,1440]
BAR [240,1440
Questions:
Before this whole fiasco ODIN didnt show KNOX. I assume thats from the 4.3 revert i tried?
Does Write Protection have anything to do with it? I do recall being able to odin flash with this before.
eMMC Burst is new to me, havent seen this before
BAR pops up before failing but not seconds before, maybe a minute before.
Still Stumped
Edit: Even if i were to find the pit file, i cant seem to find modem, csc, and bootloader to add to odin. (unless they are all combined in that md5 file) so i wouldnt be able to flash until having all the necessary items as pit rewrites the partitions and all data is lost.
i also remembered one odd thing, may or may not apply here, but just before flashing to hyperdrive, i was not able to properly format. it would take a few tries to format data or whichever for example, before files were actually gone.
tried reverting to MDJ got vibrate loop
trying again to MK6
The_SilverOne said:
Hello peeps a Happy New Year to all!
I tried searching the forums and google but no luck on my case. I am trying to install hyperdrive and am following instructions, downloaded files multiple times on multiple computers and i337m itself. Aroma opens fine and works through fine untill it tries to flash kernel it says:
flashing kernel
file_getprop: failed to stat "/tmp/aroma/kernel.prop": No such file or directory.
So I thought it was just missing a kernel, so continued and installed the att compatibility pack and all i get is ODIN/download mode. I then tried flashing kstoonez kernel and same thing.
I am using Philz Touch latest version on Canadian s4
Any ideas?
Click to expand...
Click to collapse
Hi, I am currently having this problem after trying to install RLS15.
After trying to flash the new ROM, phone would not boot, and I was no longer able to install ROMS or Restore backups.
When I would try to restore a backup, it would get to Restoring Data, and immediately fail.
When installing the ROM and its kernel, I got the same message as you:
flashing kernel
file_getprop: failed to stat "/tmp/aroma/kernel.prop": No such file or directory.
I've tried:
flashing kernels before flashing the ROM
re-install of Loki + TWRP + Motochopper Casual (Did not revert back to stock before doing this)
flashing the AT&T Compatibility pack.zip for RLS15 Before and After flashing the ROM
Fixing permission
I've noticed once or twice, when trying to restore a backup, a message in TWRP saying that SuperUser was not installed, and it asked if I wanted to install it. So I did the "Swipe to install" in TWRP, but the phone quickly reboots and again doesn't get passed the boot logo.
Sooo, I'm not too sure where to start on this one
d9vabder said:
Hi, I am currently having this problem after trying to install RLS15.
After trying to flash the new ROM, phone would not boot, and I was no longer able to install ROMS or Restore backups.
When I would try to restore a backup, it would get to Restoring Data, and immediately fail.
When installing the ROM and its kernel, I got the same message as you:
flashing kernel
file_getprop: failed to stat "/tmp/aroma/kernel.prop": No such file or directory.
I've tried:
flashing kernels before flashing the ROM
re-install of Loki + TWRP + Motochopper Casual (Did not revert back to stock before doing this)
flashing the AT&T Compatibility pack.zip for RLS15 Before and After flashing the ROM
Fixing permission
I've noticed once or twice, when trying to restore a backup, a message in TWRP saying that SuperUser was not installed, and it asked if I wanted to install it. So I did the "Swipe to install" in TWRP, but the phone quickly reboots and again doesn't get passed the boot logo.
Sooo, I'm not too sure where to start on this one
Click to expand...
Click to collapse
What variant do you have?
So I figured out my problem. In TWRP recovery, I went to mounts, and mounted my micro SD card. It was mounted to internal memory and I guess that was screwing up flashes. Hope this works for you too!
Sent from my SAMSUNG-SGH-I337 using xda premium
good evening
I am in a bit of tight spot
and before a srew it up (more) I wonder if you could help
I have a SM-G900V which is rooted and I had TWRP working just fine
I tried to flash a rom (project infinity) with aroma which freezed on installing aroma
the developer replied to me that the problem was from TWRP which had a bus and that I should instal CWP
I tried to install CWP on top of TWRP through ODIN and got a failure message
as of now I have neither TWRP or CWP or any rom flashed in mydevice
once I go into recovery mode and try to flash the previous rom that I had through the sdcard it says "footer is wrong signature fail" an reboots and gets stuck with no rom
just tried to reinstall TWRP through ODIN and got the failure message again
with the folowing message:
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth) <OSM> All threads completed. (succeed 0 / failed 1)
please help
Hey man,
Sounds like you're in a bit of a pickle. Not sure if this would be a bit extreme, but I'd download the stock firmware and flash it through Odin. After that, reflash recovery and retry your rom.
I kind of see flashing back to stock a 'fail safe' in most cases, so it's always handy to have the stock firmware stored somewhere anyway. ?
Sent from my SM-G900I
..
fffft said:
Don't flash anything until someone discerns what went wrong..
being impatient at this point will put you at high risk of bricking or worse.
The phone boots normally up until the footer error?
What is the exact error message that you see?
What version of TWRP did you have?
Any backups? If so, do they include your baseband, EFS & PIT?
16 GB ROM?
Did you have a Verizon ROM when this happened?
Rooted?
.
Click to expand...
Click to collapse
let me start by thank you for your time!
I am a bit new to all this, I have flashed some roms in the past so I am also familiar with some stuff...
The phone doesn't boot it gets stuck like the attached picture, the OS doesn't start.
I don't see any message as it is stuck like I mentioned before, I just saw a message of "FAIL!" in Odin when I tried to install CWM on top of TWRP
my version of TWRP was 2.7.1.0
I had a backup on TWRP but as I dont see TWRP working anymore I dont know if its still available
my phone is 16GB
my SM-G900V is rooted and at the moment I had working perfectly SpeedROM v1 Rev2
if you would like to contact me through chat let me know, and again thank you very much!!
Try this
..
fffft said:
Okay, on the positive side there isn't anything to suggest that your bootloader is corrupt which would make this a lot harder. Probably the failed aroma install just messed your kernel up. But I don't want to recommend messing around with shortcut solutions e.g. just flashing the kernel that may or may not work, but would put you at unnecessary further risk.
The earlier suggestion to flash a full stock image is generally sound advice, but it does not apply to all situations. My questions were basically aimed at getting a sense of whether you have corrupted the bootloader or partitioning which has a bearing on how to best recover your phone.
First, I am assuming that you do not have the Dev (unlocked bootloader) version S5. If you have the Dev edition with the unlocked bootloader, do not proceed with the rest of this post until we discuss that.
On the assumption that you have a regular 16 GB Verizon SM-G900V S5, then I would like to see you Odin flash a full stock S5 Verizon image that has been rooted. Unfortunately I couldn't find anyone who has made and posted a stock rooted Verizon S5 image like that. I don't mean a stock rooted (custom) ROM.. I mean the full stock firmware image, including the bootloader, but rooted.
That's fine. The rooted part would just be a little extra insurance put against theoretical possible snags i.e. Knox issues. So I will suggest that you use Odin to flash a full stock Verizon S5 image, with an explicit partition table. Normally we don't touch the partition information (PIT) in Odin, but in your case we need to.
Download the files below from this thread
Unless you already have the file on your PC
Verizon S5 Retail Tar 4.4.2 NCG baseband and Mar 31 kernel
MD5: 699a949b57c771b00db9f3ed675c7a5e
NCG Pit
MD5: 3dd82f91a02c82e60e0a1f9964fdb5c0
Odin 3.09
MD5: 810ad286967d0a33881fd8181d35959f
You should thank the OP in that thread for collating the files that you need in one place.
Particularly that all important PIT file.
Start Odin and check these three boxes only: Auto reboot, Re-Partition, F. Reset Time
Choose the PIT file in the PIT window. Note that the PIT file needs to be extracted. Do not leave it zipped.
Choose the stock firmware tar.md5 file in the PDA window. The tar.md5 file needs to remain tarred i.e. tar.md5 or .tar
Put your phone into download mode. Ensure that your phone is off, remove the battery for a few seconds if necessary, then press volume down + home + power until you see the android robot screen come up. If it doesn't go into download mode, repeat these steps. And in the very unlikely event that you can't get into the download mode at all, stop and post that information
Connect your phone to your PC, Odin should say that it has detected your phone
Press start and let Odin flash your phone
Basically we are replacing all of the system files and assuring that your partitioning has not been corrupted
When Odin finishes with a success message your phone should be back to normal. Do a normal reboot to confirm
If you did not backup your phone, your user files in the /data partition might still be accessible
Decide if you wish to back them up or not. Do so if you need them. Then do a factory reset from the Settings menu
You will need to re-root and reinstall your apps, etc
If you run into any difficulties:
If the Odin write fails, note the error message and double check that your Odin settings were correct
Do not close Odin. Pull the battery from your phone for ten seconds.
Then replace the battery and go into download mode again (vol down + home + power)
Note whether Odin detects the phone
Then try flashing with Odin again. Note that you are not closing the Odin program if the first flash attempt fails
Odin can be a bit picky and it is not unheard of to have to reset the phone like this and run the session a second time
Odin is also picky about USB cables. If you still continued trouble, try a different USB cable and USB port
Don't despair if anything goes astray. There is almost always an alternate way to go about something.
Let us know your results so that we can (hopefully) celebrate. Or at least regroup.
.
Click to expand...
Click to collapse
you senior member??? pppffffffff
you should OWN this forum!!! thanx a lot for your extended time in this explanation mate, I will proceed and let you know
Agreed. I use a Dell and sometimes I have problems with odin using the front usb. I have to use the read usb and then no problems.
Hi Guys!!
I am back, back with my phone completely restored
A special THANX to fffff for your help!!
..
Hello, I am relatively inexperienced when it comes to flashing and have managed to brick my s5(rogers(SM-G900W8)canadian). I have looked around and it seems as though in order to get my phone to work I need a pit file for my phone. Problem is, I can't find one. If anyone could help it would be greatly appreciated. Thanks. by the way I have rooted and enabled usb debugging prior to being bricked
http://forum.xda-developers.com/attachment.php?attachmentid=2800218&d=1402859206
so that should work?
Well that's the PIT file for your model phone, whether or not it unbricks it depends on what you did to brick it
I bricked it by attempting to flash philz touch recovery in odin 3.09 and it failed. Now I have the message:"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." on my phone, I tried doing exactly that but kies detects my phone but never finishes loading it up. So I tried flashing the stock firmware for my device model and got the same issue I did when attempting to flash the recovery. As far as i know I didn't do anything wrong as i was very careful to select the right files, etc. but clearly I did.
Well you've got nothing to lose by trying the PIT file
Not flashed PIT before so read up on exactly how to do it first, this is the thread I got the link for your phone from
http://forum.xda-developers.com/showthread.php?t=2737448
Tried flashing the file and that failed as well... not looking too good.
I guess my phone's useless now.
Did you check the "Re-Partition" in ODIN?
Are you using the latest version of ODIN3 (3.10.6) ?
Try ODIN3 version 3.0.7 too
(Obviously) Got phone in download mode
Tried just flashing a stock ROM from sammobile
Tried flashing the stock ROM along with the PIT file & Stock ROM together?
tried it all, when trying to flash the pit file as well though it gives me "SECURE CHECK FAIL : PIT" on my phone. whenever I try to flash it it always fails at system.img.ext4 with Complete(Write) operation failed.
I think I know the issue now, I'm using VMware, which apparently doesn't work. Will try on a windows pc in a while. thanks
Ah right, yea always best from a native PC
Let us know if you get it working
It worked and then I installed the newest cyanogenmod.
Alright I was wondering if some kind person could post the pit file for the verizon galaxy s7. This is what happened. I flashed the g930u files with odin and everything worked fine with root and debloated rom. Then, I wiped cache and wiped data factory reset and flashed the t-mobile rom, and it worked. But hear is where the problems began. I tried to flash back both the verizon rom, and the 930u unlocked rom, and they wouldn't flash using the PrinceComsy odin or any other odin for that matter. So, I said, well I'm stuck and flashed the t-mobile rom again, part by part, because when I tried the whole thing, it wouldn't flash either. Then at reboot, nothing. So, I flashed the pit file with the t-mobile rom, and the whole thing flashed in one wop, but still after boot, nothing. I used the pit file because I read in another guide it would get a t-mobile device back up when flashing it with the t-mobile rom, and no other rom would flash. So, I guess my last hope is that someone will have the verizon pit file or the original verizon rom.tar.md5 not one with out the pit file. If this doesn't work, I think I'm screwed. Please post it if you have it or if some one could pull it from there device.
Thanks
got it all working but on t-mobile
Alright, got everything working, but I want to share the final result. Flashed t-mobile pit file. Then flashed full t-mobile rom and pit file together. Of course wiped data and cache before doing any of this. Now just like a t-mobile phone, including band 12 and wifi calling. Can not flash back to verizon though, with out pit file, just for anyone else that wants to try this. I don't have another verizon phone to gather the pit file from, so, t-mobile is fine especially with unlimited data.
gigawatt said:
Alright I was wondering if some kind person could post the pit file for the verizon galaxy s7. This is what happened. I flashed the g930u files with odin and everything worked fine with root and debloated rom. Then, I wiped cache and wiped data factory reset and flashed the t-mobile rom, and it worked. But hear is where the problems began. I tried to flash back both the verizon rom, and the 930u unlocked rom, and they wouldn't flash using the PrinceComsy odin or any other odin for that matter. So, I said, well I'm stuck and flashed the t-mobile rom again, part by part, because when I tried the whole thing, it wouldn't flash either. Then at reboot, nothing. So, I flashed the pit file with the t-mobile rom, and the whole thing flashed in one wop, but still after boot, nothing. I used the pit file because I read in another guide it would get a t-mobile device back up when flashing it with the t-mobile rom, and no other rom would flash. So, I guess my last hope is that someone will have the verizon pit file or the original verizon rom.tar.md5 not one with out the pit file. If this doesn't work, I think I'm screwed. Please post it if you have it or if some one could pull it from there device.
Thanks
Click to expand...
Click to collapse
Ok so here's my issue
For a very long time since the G930U firmware was available to install, I've been using that. Well I decided to want to get my phone unlocked for GSM using those services but it needs Stock Firmware.
So I tried to restore to the latest G930P firmware and ODIN is giving a Volume size error for the system.img.ex4. I've tried now a couple different firmwares and no luck. Any idea?
The latest Firmware is PH7 I don't recommend it. PG1 on down are good to go. Extract zip stock firmware to a folder and add it in to Odin all the slots accordingly. BL AP CP CSC the last slot CSC is HOME_CSC not CSC_SPT and start flashing. It always works for me.
I ended up figuring it out. I had to find the stock G930P .PIT mapping's and re-partition because G930U ended up changing the sizes.
Oh good to know. Thank for sharing
Why do you not recommend PH7 update? I've heard it helps with battery life.
Could you share the pit file you used. I tried the same thing with a pit file i found online how ever since the pit i am able to flash bootloader but unable to flash system.ext4. Odin gives me a "failed (auth)" and neyjer the 930u version or the f2 or any of the other stock roms wont flash.... Help please
Don't you just love it when people "figure it out" and then don't share how? lol
Here... Since nobody gave you this. This may not be your problem.
https://drive.google.com/file/d/0BzyeAt2hy6XeenhWM2dNSU40TDA/view?usp=sharing