J5 Prime SM-G570*M* (32GB) Odin = Problems - Samsung Galaxy J5 Questions & Answers

Hello guys. I OEM unlock the device installep TPWR and BeltaOS custom build. Everything was fine up to this point. I went to update to a stock 8, and I did, but the problems started.
The OEM is now locked.
The phone now shows only 16GB.
I've tried to put the original that came with the phone (7) back, but I get errors.
I can only flash with Odin the 8 one AND using the pit file. If I do not specify the pit it fails.
How can I get the phone to partition with the 32GB size?

Related

n910f flashing problem

hallo i bought the note 4 n910f before 1 week and i would like to ask why i can not flash any rom with odin exept the german. with the other roms alwais fail or stuck to hidden.
anyone;;;
ADRIKOS22 said:
anyone;;;
Click to expand...
Click to collapse
hey there to root your Note 4 smn910f you first go to settings/security and then you will see a V behind reactivation deactivate this
after that's done connect to odin and flash cf root
you will see that it will not fail
i dont want to root yet i just want to change official rom and i can't flash via odin
it says when odin write hidden.img.ext4 volume size is too big 81920<184320
Can I ask which firmware you are trying to flash? Is it for the 910f if it's for a different variant that will probably be why
I have the German and I want to flash the Greek I downloaded them from sam mobile for the n910f
just came across the same issue something is messed with hidden partition image size, the default partition size is smaller whereas the the img file on the odin file is much bigger
bala_gamer said:
just came across the same issue something is messed with hidden partition image size, the default partition size is smaller whereas the the img file on the odin file is much bigger
Click to expand...
Click to collapse
Got the same problem today, cant flash any rom other than the latest UK (BTU) When trying to flash any other rom I get this message. Any idea how to fix it?
Some serious problem with Odin flashing the n910f. I have just gone through a night of torment, having tried flashing the newest firmware and getting a failure due to the hidden partition problem mentioned above.
Originally, my firmware was on n910fxxu1anj4. I flashed n910fxxu1ank6, the flash failed on flashing the hidden partition with:
Volume Size is too big 81920 < 204800
ODIN: Invalid ext4 image
and the phone was stuck in a bootloop on the first screen with the text “Note 4”.
Then even with wipe, restore of backup etc the phone wouldn't boot.
Flashed n910fxxu1ank5, same failure, didn't record the numbers, couldn't get it to boot in no way...
Flashed the original n910fxxu1anj4, flash failed also on the hidden partition with:
Volume Size is too big 81920 < 471040
Stuck in bootloop, but upon reflash of CWM recovery and cache and data clean, the phone booted, and I was able to restore a backup which works fine now...
However there must be some serious problem.
Anyone have an idea what this is?
--
白い熊
I think we need a correct PIT file for each firmware maybe ?
ADRIKOS22 said:
hallo i bought the note 4 n910f before 1 week and i would like to ask why i can not flash any rom with odin exept the german. with the other roms alwais fail or stuck to hidden.
Click to expand...
Click to collapse
From what I have gathered on some of the models is that the only firmware that you can flash to your phone are the ones made for the CSC of your phone. Navigate to system/csc then look at the different CSC files in that folder. Those are the only ones I can flash on my H model anyways.
CodeNameRedNeck said:
From what I have gathered on some of the models is that the only firmware that you can flash to your phone are the ones made for the CSC of your phone. Navigate to system/csc then look at the different CSC files in that folder. Those are the only ones I can flash on my H model anyways.
Click to expand...
Click to collapse
I had Swedish firmware with CSC NEE and could flash a firmware with CSC BTU. But I cant flash back the NEE firmware again. And looking at the hidden.img.ext4 and cache.img.ext4 in the only firmware I can flash it has the smallest. All the other firmwares have bigger hidden and cache files. So I think the phone needs to flashed with re-partition checked in Odin and that is not possible without the correct PIT file. I am relly tired of this phone, Samsung has made it too complicated to flash firmwares
easycure1974 said:
I had Swedish firmware with CSC NEE and could flash a firmware with CSC BTU. But I cant flash back the NEE firmware again. And looking at the hidden.img.ext4 and cache.img.ext4 in the only firmware I can flash it has the smallest. All the other firmwares have bigger hidden and cache files. So I think the phone needs to flashed with re-partition checked in Odin and that is not possible without the correct PIT file. I am relly tired of this phone, Samsung has made it too complicated to flash firmwares
Click to expand...
Click to collapse
Have you tried using Kies to do a firmware upgrade and initialization? When you plug your phone in Kies may warn you that it doesn't support your phone but you can still do it. You may be better off just leaving it alone though.
CodeNameRedNeck said:
Have you tried using Kies to do a firmware upgrade and initialization? When you plug your phone in Kies may warn you that it doesn't support your phone but you can still do it. You may be better off just leaving it alone though.
Click to expand...
Click to collapse
Yes tried that but with no luck, seems I am stuck with my BTU firmware. It gets the same error message on the phone "size is too big" and got a new error message on the phone [99] eMMC write fail: HIDDEN
Guys I tried flash latest Sweden and have same problem size too big and ext4 failed,then I flash Philz recovery and voila phone booted everything its ok!!!
Ogy77 said:
Guys I tried flash latest Sweden and have same problem size too big and ext4 failed,then I flash Philz recovery and voila phone booted everything its ok!!!
Click to expand...
Click to collapse
What was your original software? Could root have messed this up? Before rooting I flashed the BTU and DBT and NEE firmwares without problem. But then staying at BTU for some weeks and then rooted. And after that I can flash no other firmware. Trying to restore the phone to the NEE firmware as I am going to sell the phone.
Any more input on this? I did the same as Ogy77 and sure the phone boots but I got some strange crashes and did a factory reset and flashed back the stock recovery. So it boots but the CSC is gone as the cache.img.ext not is flashed so no OTAs will work as Kies does not regonize the phone with a firmware witout CSC?
I have the same problem, Im using xnote as i cant flash my vodafone UK stock rom
I was stuck in a bootloop but flashed twrp and installed xnote again as it was stored on my sd card luckily! I would like to know how to flash back to stock
I have same problem. I have a open 910F and get the same error on odin file size is too big. What can i do?

Odin FAIL, size error

Hello there,
I have to Samsung stocks for my German S5; As the instructions propose; I am using Odin 3.11 to install.
http://www.sammobile.com/firmwares/download/86258/G900FXXS1CPG9_G900FDBT1CPE2_DBT/
the latest unbranded stock rom (6.01) for the S5.
gives me (almost immediately a FAIL with size error)
I did "step back"; and flashed
http://www.sammobile.com/firmwares/download/70389/G900FXXU1CPD3_G900FVD21CPC2_VD2/
bit older, but also 6.01, claims to be branded for Vodafone.
That second one was flashed by the person who sold me that phone last week.
With that second ROM ... Odin keeps working for one, two minutes; before giving me another FAIL / size.
And really funny ... after I flashed the first image, the S5 wouldnt boot any more; tell me about broken installation, and running KIES ...
Now, after I tried to flash the second one (but flashed the first one again afterwards with various PIT files that didn't help) ...
the phone is booting again; showing me exactly the setup that I had before doing the first flash;
all my apps are there, everything. How is that possible?!
Any idea what I could do about that?
Update:
I found another DBT rom, but that one didn't work either.
Finally I pulled the latest "vodafone" ROM and figure a way to overcome the failing ODIN install:
1) I flash the ROM (without using any special PIT files)
2) After flash failing ... I wait some time
3) then I unplug the phone; and restart it into download mode again
4) then I flash the latest twrp recovery
Afterwards, the phone would just boot normally. When flashing the ROM that was previously flashed successfully ... that installation came up;
and when I tried again with the newest vodafone ROM, it did update the apps during startup; and show the new build-time information later on.
So, yes, this worked for me, but obviously a rather weird procedure.

[Firmware] G930TUVS4BQL2 (12/21/2017)

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.

Good S5 dump to bad S5?

I have 2 identical 900V's and one is pooched. It wont get past black S5 screen, but can boot into download, recovery and even safe boot screens. I have flashed it back to 5.0 with ODIN, took the flash no errors, deleted cache, NAND, factory reset, everything I could do to get it to boot. even flashed the PIT with the OG PIT file found online. No other firmwares will flash except the 5.0 without an error. I have another 900V that is working (no SIM, not authorized on a network, just a wifi toy) and running 6.0.1. Can I dump the PIT file, and the firmware into a file and send it over to the frozen S5 via ODIN? It just wont get past the first screen no matter aht I do to it firmware wise.

I accidentally checked the Re-partition button in Odin, the storage only recognize 32GB now

Hello everyone,
I have a phone beyond2qlte and I accidentally checked the "Re-partition" button in Odin without PIT, the storage only recognize 32GB now (The original size is 512GB). i am so stupid and would be so grateful for your kind help.
My phone is Snapdragon and tried every method to flash TWRP but still bootloop. I just want to have a phone for normal use now, but it seems so hard....
I flashed BL,AP,CP, CSC but still failed...
Please help me. Thanks a lot
sonic997 said:
Hello everyone,
I have a phone beyond2qlte and I accidentally checked the "Re-partition" button in Odin without PIT, the storage only recognize 32GB now (The original size is 512GB). i am so stupid and would be so grateful for your kind help.
My phone is Snapdragon and tried every method to flash TWRP but still bootloop. I just want to have a phone for normal use now, but it seems so hard....
I flashed BL,AP,CP, CSC but still failed...
Please help me. Thanks a lot
Click to expand...
Click to collapse
Have you attempted a factory reset?
I think you have to flash PIT file from your S10+ firmware.
here the articles you can follow :
Extract Samsung PIT File from Samsung Firmware | DroidViews
Here're the steps to extract the Samsung PIT file from a Samsung firmware. The CSC binary contains the PIT for your Galaxy device.
www.droidviews.com

Categories

Resources