Database Users

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?

Cannot return to stock stuck on bootscreen

I have tried to flash the stock rom found on sammobile here http://www.sammobile.com/firmwares/database/SM-N9005/ and the flash is successful but it never finishes boot, just stuck on the samsung loading screen, any suggestions? if I re flash twrp and flash custom ROM it boots but no matter what stock rom I try it never boots

Hey,
try to wipe everything bevor you flash your firmware over odin. Also you need a pit-file to refresh your partition. Use google to find the right one.

pvpwinner said:
Hey,
try to wipe everything bevor you flash your firmware over odin. Also you need a pit-file to refresh your partition. Use google to find the right one.
Click to expand...
Click to collapse
I did flash a pit and it still didnt work, also tried N9005XXUGBNL8_OXAGBNL8_v5.0_Repair_Firmware still no luck, custom roms = good, stock = bad !

Stay away fro PIT. Wrong application will kill the phone.
Are you sure you are flashing the correct stock? What is the phones CSC. Install Phone INFO (Samsung) from playstore and find out the Original CSC code. Post this and maybe we can help.
https://play.google.com/store/apps/details?id=org.vndnguyen.phoneinfo&hl=en

[SOLVED] Galaxy S5 Verizon Back to Stock with Dev aboot.

So, I'm trying to flash everything back to stock before I send this phone back to Samsung for Trade in deal.
I unlocked the bootloader using this guide here https://forum.xda-developers.com/verizon-galaxy-s5/development/rd-unlocking-galaxys-s5-bootloader-t3337909
Using this guide https://forum.xda-developers.com/showthread.php?t=2784880 I tried flashing back to stock using OC4 Stock retail tar.
Unfortunately, I am getting an error on download mode when running in ODIN MODE.
SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1
Not sure how to continue from here, tried searching but couldn't seem to find anything.
The guide said I should backup up the loader before flashing or I could be stuck with a locked bootloader, this is what I want though. I would like the phone to appear stock before I return to Samsung.
Would appreciate some assistance. Thanks in advance.
UPDATE:
Well, I feel pretty silly. I solved my issue. Apparently you can't flash the boot loader if you are on a higher version number and you are trying to flash an older bootloader. I was able to find a newer tar file from here https://forum.xda-developers.com/verizon-galaxy-s5/general/update-qh2-t3672387
I was doing more searching and found the solution to my problem from a Note 3 thread.
Thanks again XDA.

Try a more up-to-date tar, BOK3 at least. Or newer.

bbsc said:
Try a more up-to-date tar, BOK3 at least. Or newer.
Click to expand...
Click to collapse
LoL, yeah, just figured that out.
Thanks for the response though man, I appreciate it.
Although, If you may, is there a way to remove the padlock icon (make it look locked again) from the boot screen?
I'm assuming I must of used a rooted retail rom?

Yes, you need to flash a factory firmware with pit-file. Or something.
Have you got a newer tar?

bbsc said:
Yes, you need to flash a factory firmware with pit-file. Or something.
Have you got a newer tar?
Click to expand...
Click to collapse
I'm using this tar
https://www.androidfilehost.com/?fid=673368273298986905
Can I use this pit?
https://www.androidfilehost.com/?fid=24052804347765167
Thanks again.

Unzip and flash this after flashing that new tar:
https://mega.nz/#!O81HAKwJ!GWPEcA7zUtFIhWJHVF5XLO-Iwhrvy1pbL0cJRqxxm-o
The padlock never gets locked , it simply disappears.
It may disappear after the second reboot.

bbsc said:
Unzip and flash this after flashing that new tar:
https://mega.nz/#!O81HAKwJ!GWPEcA7zUtFIhWJHVF5XLO-Iwhrvy1pbL0cJRqxxm-o
The padlock never gets locked , it simply disappears.
It may disappear after the second reboot.
Click to expand...
Click to collapse
Hmm, okay.
So, first I flashed my pit file I linked earlier, with the tar.
Then I flashed your file after unzipping. (put in odin ap box)
Did a factory wipe, padlock still appearing there.
At Verizon splash screen, its been sitting there quite a while.
Padlock still on splash screen. Will wait a bit and see if it boots into android and reboot again to see if the padlock is gone.

MrTrumpz said:
Hmm, okay.
So, first I flashed my pit file I linked earlier, with the tar.
Then I flashed your file after unzipping. (put in odin ap box)
Did a factory wipe, padlock still appearing there.
At Verizon splash screen, its been sitting there quite a while.
Padlock still on splash screen. Will wait a bit and see if it boots into android and reboot again to see if the padlock is gone.
Click to expand...
Click to collapse
Okay, finally got to the "Android is starting"
"Optimizing apps"
Finally got rid of the padlock.
Thank you so much for your help.
Its more appreciated than you think.

Where are CSC files kept?

So ai bought an S10+ (lightly used) earlier his week and went hrough the grueling process of rooting itnand then installing tWRP and föashing a custom rom from TWRP.
The only firmware for my device and country (which was the recommended firmware to use to flash stock with Magisk patched onto it) on Sammobile was 3-branded. This included a 3-branded boot and shutdown animation tha tis ugly as sin.
No matter, I thought. The custom rom included a custom boot animation. However, once I'd flashed the custom romN the 3-branded boot and shutdown animations remained. I'd even had the custom rom set my CSC to NEE (generic Nordic countries), but it remained 3-branded.
I tried using a file explorer to replace the 3 relevamt qmg files on my phone with the custom animations. Nope, didn't work. I found out that my mistake was using the home_csc file to flash stock + magisk instead of the csc file.
So that got me wondering, where are CSC-specifoc files stored? And is there any quicker way to cjange CSC than having to reflash stock? Because even the HadesRom Aroma installer failed to switch my CSC for some reason.

[sm j730f] Bootloader fail and TWRP boots into black screen

Greetings everyone,
I decided to post my problem with my phone after searching the entire internet for similar problem but with no luck. Anyway I used to play around with my Samsung j7 pro for 2 years, I managed to flash twrp and thus many other custom roms, until last week when I recklessly flashed a sboot.img.tar file through Odin in order to fix cellular network in a rom I flashed earlier, this alone bricked my phone refusing to get past the Samsung logo, so like I do always, I tried to restore my phone by flashing the stock firmware (9.0) which I always keep on my PC, but surprise, the phone refuses to go through the process and gives me this error:
sw rev check fail bootloader device -1 binary 6
(same with 8.0 and 7.0 firmware)
I searched the internet for same error but with no luck, because I understand it's a mismatch between device bootloader current version and the firmware bootloader's, that they should be the same or higher, meaning you can't downgrade, I get that! but I never seen device with negative figure (-1) what that's supposed to mean? my device bootloader used to be on 6, how did it managed to jump to minus one ?
then I tried to flash TWRP to see if I could flash a rom and get around it, so I did, but when booting into recovery the screen goes black, I thought first the phone turned off, but not really, because TWRP seems to work with screen completely black, I knew that because I accidentally touch the screen and I sense vibration, I managed to reboot the phone via twrp just by guessing the buttons location (screen always black) in order to prove that TWRP is working with screen off. I tried to flash multiple TWRP versions but the same problem, no screen just touch, by the way there is nothing wrong with display hardware because it shows Samsung logo at start and also can boot into download mode just fine.
I hope someone could help me overcome this big of an issue, because I tried everything.

Where did you find such sboot.img.tar file?

death.by.confusion said:
Where did you find such sboot.img.tar file?
Click to expand...
Click to collapse
Here
https://forum.xda-developers.com/ga...ow-to-fix-sim-cards-didnt-read-j730f-t3939685

Michelyn50 said:
Here
https://forum.xda-developers.com/ga...ow-to-fix-sim-cards-didnt-read-j730f-t3939685
Click to expand...
Click to collapse
First, can you try installing any custom rom, blindly(since you said the screen is black when you boot in recovery).
Second, can you try flashing stock firmware without the BL part in Odin?

death.by.confusion said:
First, can you try installing any custom rom, blindly(since you said the screen is black when you boot in recovery).
Second, can you try flashing stock firmware without the BL part in Odin?
Click to expand...
Click to collapse
I tried blindly many times flashing any custom rom but with no luck since it's really hard predicting the buttons location on the screen, I probably need another phone replica with working twrp to mimick the exact moves.
For stock firmware, I manage to install it without BL but when booting it's just stuck on the Samsung logo, and when booting into stock recovery nothing just black screen, and booting into download mode it seems that the installation didn't change the binary -1, since I could see it on the screen

death.by.confusion said:
First, can you try installing any custom rom, blindly(since you said the screen is black when you boot in recovery).
Second, can you try flashing stock firmware without the BL part in Odin?
Click to expand...
Click to collapse
This is a screenshot when I try to install stock firmware (with BL)
https://m.imgur.com/a/9vuFqTX

Can you try flash other sboot files from the link you gave me? Try to flash some sboot file, and then make full flash of your stock firmware.
If not, maybe you can try flashing sboot with heimdal https://www.glassechidna.com.au/heimdall/

I have the same issue, any help or advice?

Flash último bootloader e modem CP
Flash Any Custom ROM

Did you flash misc partition ?
If your device keep booting in blackscreen, you need to erase misc partition.
Here, is the guide for erasing MISC partition: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
The guide is for REDMI NOTE 9, so if you try to perform the method 1, you can cause more damages to your device.
Please, follow METHOD 2 only !
If TWRP is not working perfectly, obviously you need to flash stock rom recovery.img.
Good luck