Database Users

please help before I brick it

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!!

..

[Q] i9506 4.4.2 Problem

So I flashed 4.4.2 that had been released yesterday with Odin and I got "FAIL! (Size)" when it tries to flash hidden.img. I first thought my phone got bricked as it was only able to get on the download mode and couldn't get to recovery mode and when I tried to flash it again it did the same error. After reading about this problem fro the internet someone said to ignore that error message and go back to download mode after flashing the rom and flash a custom recovery. I did so, went to the recovery mode, wiped data and cache and I was able to boot normally. When my phone booted up I started to have an error message that bothers me the most; "Unfortunately, Samsung keyboard has stopped working". This happens every five seconds or so. Is there any fix for this, as I'd like having Samsung's keyboard working on my phone?

You can't just ignore Odin warnings.
Almost all Odin error can be resolved by the following.
- Different usb cable
- Different usb port
- Different pc
- Reinstalling drivers.

Siura said:
So I flashed 4.4.2 that had been released yesterday with Odin and I got "FAIL! (Size)"
Click to expand...
Click to collapse
Most likely you are flashing different size partitions. Is it stock?
If so, please download pit file for your model, flash with pit file and repartition marked, do not reboot phone, go to recovery, wipe phone and reflash again, this time without pit file and without repartition marked. Shall do the job.
Final tip: NEVER ignore Odin errors messages.

spamtrash said:
Most likely you are flashing different size partitions. Is it stock?
If so, please download pit file for your model, flash with pit file and repartition marked, do not reboot phone, go to recovery, wipe phone and reflash again, this time without pit file and without repartition marked. Shall do the job.
Final tip: NEVER ignore Odin errors messages.
Click to expand...
Click to collapse
Does it have to be 4.4.2 pit file as all I found was a pit file for 4.3? Does it harm my device in any way if I try to flash with that?

Siura said:
Does it have to be 4.4.2 pit file as all I found was a pit file for 4.3? Does it harm my device in any way if I try to flash with that?
Click to expand...
Click to collapse
should not, I used 4.3 pit to flash 4.4.2.

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?

Update Problem

I've just bought an S5 G900F Euro version which had Kitkat on it.
Tried to update Bootloader&Modem so that I could install Lollipop ROM using odin.
It didn't work and phone wouldn't reboot.
From Samsung website downloaded latest Firmware G900FXXU1BOD3, but odin keeps failing because of ext partition.
I installed TWRP, rebooted to recovery, it automatically fixed partion, rebooted but stuck on boot screen.
Re tried again once partition was fixed got the Android is updating but is now stuck on "starting apps".
Any suggestions would be very welcome.
Thanks.

You didn't need to update modem and BL to upgrade from KK to LP
Anyway, try flashing the PIT file along with the stock LP ROM (Same time in ODIN)
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091

*Detection* said:
You didn't need to update modem and BL to upgrade from KK to LP
Anyway, try flashing the PIT file along with the stock LP ROM (Same time in ODIN)
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Click to expand...
Click to collapse
Thanks for the link for the PIT file and information.
Phone now working.
The reason I wanted to update bootloader+modem was that it was a requirement of the ROM I wanted to install.

Error SW REV CHECK FAIL DEVICE 2 BINARY 1

When I restore by Odin my N910H 5.1.1
my Note 4 is hanging SW REV CHECK FAIL DEVICE 2 BINARY 1
Please help!

khongchinhxac said:
When I restore by Odin my N910H 5.1.1
my Note 4 is hanging SW REV CHECK FAIL DEVICE 2 BINARY 1
Please help!
Click to expand...
Click to collapse
pharhaps you have tried to restore downgrade version. plz try to the latest software version.

khongchinhxac said:
When I restore by Odin my N910H 5.1.1
my Note 4 is hanging SW REV CHECK FAIL DEVICE 2 BINARY 1
Please help!
Click to expand...
Click to collapse
i have the same problem...please!!! help me!!!

Probably you've had an OTA (over the air, wifi) update. You should flash latest firmware for your device. Samsung locked the bootloader, it's not possible to install an older firm anymore (until someone finds how).

any solution to fix this problem ?

Any solution to this?

Looking for a solution!!!!

Nixdax said:
Looking for a solution!!!!
Click to expand...
Click to collapse
I fixed my phone by downloading stock 5.1.1, unpacked with 7zip, deleted modem.bin and sboot.bin from the extracted contents, packed the contents again as tar using 7zip and flashed via ODIN.

Looking for an answer as well. Same situation after I wiped cache. Phone is on the fritz. Ive been up for the past 6 hours trying to fix it. Im trying to save my files on my phone in the case I need to wipe everything.

theplagueisback said:
I fixed my phone by downloading stock 5.1.1, unpacked with 7zip, deleted modem.bin and sboot.bin from the extracted contents, packed the contents again as tar using 7zip and flashed via ODIN.
Click to expand...
Click to collapse
do you mean aboot.bin? and when you packed the contents, did you just zip them? then just the extension to .tar? or did you change it to .tar, THEN zip it?

Figured it out on my own. Flashed CF autoroot. Then flashed 5.1.1 which is the most up to date firmware. Im not sure if the issue was because I was doing 5.1.0 and didnt realize that was the most UTD version, or if CF to 5.1.1 was the trigger. Either way, it worked.

I tried this but also failed, then I read somewhere else that I need to remove cm.bin and sboot.bin.
I did and it flashed OK, but phone is stuck in bootloop and wont go to recovery mote form e to reset.
I am presently searching for a way to get it out of bootloop

dannyogolo said:
I tried this but also failed, then I read somewhere else that I need to remove cm.bin and sboot.bin.
I did and it flashed OK, but phone is stuck in bootloop and wont go to recovery mote form e to reset.
I am presently searching for a way to get it out of bootloop
Click to expand...
Click to collapse
try rename firmware file from .md5 to .tar and extract it using 7-Zip, delete or move sboot.bin and modem.bin then make a new 7-Zip archive with .tar extension and install it regulary by Odin

Thanks.
But like I wrote, I have been able to flash, but phone is in bootloop now

use the sboot and modem files from the LATEST update..just swap em out