I have tried to flash the Android 5.0.1 stock firmware N910FXXU1BOC3 on my Note 4 N910F and I'm getting some error in Odin when it's writing the hidden.img.ext4 and failing. On the device, in Download Mode i see the error message volume size is too big.
Right now i'm on Android 4.4.4 N910FXXU1ANK4.
First thought was that i left Reactivation Lock on and saw a bunch of other threads where it says that this might be the main issue as I am flash a different CSC Region ROM. I managed to get back to N910FXXU1ANK4 after the failed flash of N910FXXU1BOC3 with Kies3 and Emergency re-initialization (thank you Samsung for finally doing something useful with Kies). I disabled the reactivation lock and attempted again to flash N910FXXU1BOC3 but failed with the same error.
After some searching, i found that the issue might be because i have to re-partition the device in order to fit the new partiton sizes for Android 5.0.1.
This should be done with the Odin option to Re-partition but that requires a PIT file in order to have the re-partition information.
I have looked into the md5 archive for the N910FXXU1BOC3 ROM and initial 5.0.1 release for N910F N910FXXU1BOB4 ROM but I could not find a PIT file in order to re-partition.
Now my question is, when going from Android 4.4.4 N910FXXU1ANK4 to Android 5.0.1 N910FXXU1BOC3, do I have to re-partition with Odin, and if so, where do I get the correct PIT file ?
Thanks.
lolozaur said:
I have tried to flash the Android 5.0.1 stock firmware N910FXXU1BOC3 on my Note 4 N910F and I'm getting some error in Odin when it's writing the hidden.img.ext4 and failing. On the device, in Download Mode i see the error message volume size is too big.
Right now i'm on Android 4.4.4 N910FXXU1ANK4.
First thought was that i left Reactivation Lock on and saw a bunch of other threads where it says that this might be the main issue as I am flash a different CSC Region ROM. I managed to get back to N910FXXU1ANK4 after the failed flash of N910FXXU1BOC3 with Kies3 and Emergency re-initialization (thank you Samsung for finally doing something useful with Kies). I disabled the reactivation lock and attempted again to flash N910FXXU1BOC3 but failed with the same error.
After some searching, i found that the issue might be because i have to re-partition the device in order to fit the new partiton sizes for Android 5.0.1.
This should be done with the Odin option to Re-partition but that requires a PIT file in order to have the re-partition information.
I have looked into the md5 archive for the N910FXXU1BOC3 ROM and initial 5.0.1 release for N910F N910FXXU1BOB4 ROM but I could not find a PIT file in order to re-partition.
Now my question is, when going from Android 4.4.4 N910FXXU1ANK4 to Android 5.0.1 N910FXXU1BOC3, do I have to re-partition with Odin, and if so, where do I get the correct PIT file ?
Thanks.
Click to expand...
Click to collapse
hi,
i have a N910F.. When i went from stock Android v 4.4.4 to Lollipop .. German Rom.. BOB4 and after that again to BOC3 I did not repartion anything. in fact repartion must be untick , I only made sure that auto reboot was ticked and F. Reset Time ticked then, place the tar/(md5 )file in AP section of Odin. Switch phone off, boot into download mode, connect phone via usb and wait for blue color to light up ID:COM box (above auto reboot) check if everything is connected and correct boxes ticked and then flash.( see screenshot ) After flash your phone will "try" to boot up but will optimise apps first. This can take some time (my case about 10 min? or so)
Plse take note that i am referring from stock Rom v4.4.4 to stock Lollipop
v 5.0.1 Also you only flash the one file....... "tar"/(md5 ) thats all.
good luck
willcor said:
hi,
i have a N910F.. When i went from stock Android v 4.4.4 to Lollipop .. German Rom.. BOB4 and after that again to BOC3 I did not repartion anything. in fact repartion must be untick , I only made sure that auto reboot was ticked and F. Reset Time ticked then, place the tar/(md5 )file in AP section of Odin. Switch phone off, boot into download mode, connect phone via usb and wait for blue color to light up ID:COM box (above auto reboot) check if everything is connected and correct boxes ticked and then flash.( see screenshot ) After flash your phone will "try" to boot up but will optimise apps first. This can take some time (my case about 10 min? or so)
Plse take note that i am referring from stock Rom v4.4.4 to stock Lollipop
v 5.0.1 Also you only flash the one file....... "tar"/(md5 ) thats all.
good luck
Click to expand...
Click to collapse
Thank you for the reply, thinking back I don't think i tried to flash BOB4 first and then BOC3. I will try this today and come back with some feedback.
lolozaur said:
Thank you for the reply, thinking back I don't think i tried to flash BOB4 first and then BOC3. I will try this today and come back with some feedback.
Click to expand...
Click to collapse
hi ,
i personally , don't think it will make any difference or matters,
if you flash the one or the other ..but hey ..who knows ..?
Only reason ,i flashed BOB4 as it was the first Lollipop available and BOC3 was a later date ( March 2015 )
good luck
I have the similar issue. KK and BOB4 roms work and install perfectly. however I am having the same issues while installing BOC3 rom be it Stock or Custom.
So I finally managed to solve the issue. Seems that the image I was downloading from Sammobile was not that good.
I was trying to install N910FXXU1BOC3_N910FVFG1BOC2_CNX - Romania Vodafone. I was unable to install it no matter what I tried.
I was able to install N910FXXU1BOC3_N910FTPD1BOC1_TPD - Netherlands unknown, without any issues.
Something that i noticed is that when loading the tar with issues in Odin, total binary size was shown as 0 mb, while on the Netherlands tar file it was showing 3.3gb.
Also the tar sizes where a bit strange : RO CNX 3.6gb - NL TDP 3.4gb. So I would imagine that extra 200mb might be an issue for the partition size (suspecting bloatware maybe?).
Long story short, the tar file I was trying was the issue and downloading a different CSC file solved this for me.
Also, I tried an advice from the forum, where you extract the recovery.img and convert to tar and first flash that tar before the ROM, but that did not work in this case.
Thank you for the replies and support.
Does it void the warranty ? I am also on 4.4.4 ANK version and want to update fo 5.0.1 BOC3.
Sent from my SM-N910F using XDA Free mobile app
I installed the BOB4 like said willcor and do an antutu and, I know that it are subjective information, but I was exhausted of see the Meizu above our fairy note 4 (including with the last 4.4.4), but now, I will sleep much more well than yesterday...
Beko68 said:
Does it void the warranty ? I am also on 4.4.4 ANK version and want to update fo 5.0.1 BOC3.
Sent from my SM-N910F using XDA Free mobile app
Click to expand...
Click to collapse
If you're talking about knox (hehe of course, what else) knox still 0x0 after installation...
Doing this kept my knox counter at 0x0, but I did not root or install any custom recovery.
Slightly off topic but I would stay away from BOC3. Many people I know have had problems with BOC3 Firmware.
I am going to be re-flashing BOC3 when I get back home... I must admit when I flashed BOC3 I didn't do a fresh wipe before flashing it so might have been my problem.
Have you wiped your phone before flashing the firmware?
BNerd89 said:
Slightly off topic but I would stay away from BOC3. Many people I know have had problems with BOC3 Firmware.
I am going to be re-flashing BOC3 when I get back home... I must admit when I flashed BOC3 I didn't do a fresh wipe before flashing it so might have been my problem.
Have you wiped your phone before flashing the firmware?
Click to expand...
Click to collapse
Yes, I wiped from the recovery before and after the BOC3 upgrade and I must say that I like how BOC3 feels.
Battery life feels about the same for me - 50% when I get home (9-5), considering i have BT on all day as i have a smartwatch paired, exchange account, 3 gmails, skype push and a few others.
Love the new Smart Lock features with Trusted Places an On Body Detection.
One thing I noticed, manual check for updates on Security Policy Updates does not give any results, not sure if that is working correctly.
I tried rooting my galaxy j7 with Odin and the feedback I get Is binary size too large
Kindly help me out
#19
I have fixed when up wrong file pit
My phone is samsung note9 128gb
When i try to up file pit on rom . I had loss my store from 128gb to 32gb
I don't find any solotion on web
And i have go to setting , open development setting. Choose lock OEM. After that my phone restart and recover to 128gb
Please share this solution . I hope it can help many people up wrong file pit and loss data store like me .
File up wrong pit file odin by Lock Oem
Recover Lost data store .
Ages ago because i was impatientto update my phone so i flashed the Polish Stock using Odin, since then i have used Odin to flash the UK Stock, though when i wipe and reset the phone it still initially comes up with the polish language, (not a massive issue i know but i want to get UK OTA if it ever comes) also if i go to sell the phone at the end of this year when the Note5 is out im sure the new owner would want to turn it on and see english.
Ive tried
Clearing the EFS cache and resetting the phone from recovery before and after flashing BTU
I made sure reactivation lock was off as I wondered if that would cause an issue though that hasn't helped. does anyone have any other ideas?
Im un-routed as i sometimes use my phone to test out corporate BYOD so cant root of flash a custom rom.
thanks all for any help.
ooMoo said:
Ages ago because i was impatientto update my phone so i flashed the Polish Stock using Odin, since then i have used Odin to flash the UK Stock, though when i wipe and reset the phone it still initially comes up with the polish language, (not a massive issue i know but i want to get UK OTA if it ever comes) also if i go to sell the phone at the end of this year when the Note5 is out im sure the new owner would want to turn it on and see english.
Ive tried
Clearing the EFS cache and resetting the phone from recovery before and after flashing BTU
I made sure reactivation lock was off as I wondered if that would cause an issue though that hasn't helped. does anyone have any other ideas?
Im un-routed as i sometimes use my phone to test out corporate BYOD so cant root of flash a custom rom.
thanks all for any help.
Click to expand...
Click to collapse
Download Phone INFO Samsung from Play and check the CSC.
But it might be you are rebooting into DL mode instead of shutting down the phone then starting it in DL mode. I usually remove the battery for a bit and hold the power button for a few secs to make sure the mainboard is completely discharged. Odin (& other methods) all have problems changing BL and Modem if you just do a reboot into DL.
You might want to take a look at Multiboot and Recovery for the possibility of having the ROM you want, rooted etc. AND still have a stock ROM you can choose to boot into for work purposes.
I have a uk unbranded 900f. I got it a month ago agony almost straight away it upgraded from kitkat to lollipop. I find it can lag when pressing the home screen, the recent app button and starting he camera. Also firefox is buggy and can lag and he text will blur at times. Previously I had a htc one x running viper rom. I don't find the S5 on lollipop to be any faster than my one x running jellybean viperx.
I heard that the s5 on kitkat has less problems so want to down grade to find out. I want to try kitkat stock first so want to know he easiest way to do this? Ie factory reset, odin flash etc. Also I need to know if there are any problems to look out for or special prep I should do. I am rooted, have twrp installed and have the reactivation unchecked. Alao whicj version of kitkat would bw the best to go to? Any advice is appreciated Thanks.
Factory resetting after upgrading to Lollipop solves a lot of issues, Id try that first
Latest KK G900F Stock ROM here and ODIN to flash it
Extract ROM
Load it into AP or PDA in ODIN
Stick phone into download Mode (Volume down & Home & Power)
Connect to USB PC
Hit start once ODIN says it's happy
Thanks Detection. I'll try the reset first then and go from there.
So when this phone was on stock fng2 firmware long ago when it was current firmware. I sent it off to a guy who was offering very cheap unlock. used it fine since then. but wanted to put stock rom on it and make it completely Samsung official with no problems. so it is ready for selling. but when I get the latest firmware which is ok3 and flash with odin. after booting in those crashes start happening about 2 times per second. phone is useless. I made it to settings menu and looked at baseband and software version both show unknown so I flash stock ok3 modem still samething. then I try these full firmware images:I flash od2, same thing oh1, same thing, factory reset doesn't do a thing on the rom with issues. then I try fng2 it works perfect. then I use use od2 oh1 ok3 update.zip to get ti to latest version and it works perfect. modems upgrade and work fine. but when on latest version I reset phone from the settings menu to factory default same issue after phone as booted. so currently phone is useless if it is ever resetted. so no selling. any solutions.
the issue seems to reside with the modem. probably guy messed up a lot of settings in service mode?
You name it I have tried it most likely
any ideas anyone?
anyway to reset nvram to factory default.
i have reseted it in service mode. were it says a golden backup exists. that didnt solve anything
I've tried many many things but nothing seems to work for that issue. Only way I've gotten around it is by doing a dirty flash of kitkat with odin.
So this is a bit of an odd situation my friend is having. He bought his Note 4 off eBay over a year ago, and it was (and still is) a rooted mess. And I mean a big mess. Now I'm trying to help him fix it, because he can't update his phone at all whatsoever from 5.1.1. So I send him 6.0.1 firmware for O2U and have him go into Download mode, odin, all that fun stuff. Download mode says SM-N910T. Settings says SM-N910F. Anyway, he tries flashing the firmware via odin, fails, I have him try multiple things (I'm pretty tech savvy when it comes to this type of stuff) but it always failed. Also, "Current Binary" and "System Status" are both custom, and the KNOX counter is 0x1.
So what I'm asking is, how to fix this problem for him? What steps should he take (or should I help him take)? Is this actually a T-Mobile phone from the USA, but rooted to work with O2 sim cards? The hell is going on here?
Thanks for any replies, and all suggestions will be taken seriously and addressed.
Install the Phone INFO Samsung APK by vndnguyen and see what it's written there.
Get the serial number - example: mine is a 910C with serial RF8H70D.... and so on (obviously I can't write it all here)
With this serial number try with Samsung Smart Switch on the PC and see what info you get. Also you have the possibility to get the latest original firmware installed on the phone.
Good luck.
Gunshots911 said:
So this is a bit of an odd situation my friend is having. He bought his Note 4 off eBay over a year ago, and it was (and still is) a rooted mess. And I mean a big mess. Now I'm trying to help him fix it, because he can't update his phone at all whatsoever from 5.1.1. So I send him 6.0.1 firmware for O2U and have him go into Download mode, odin, all that fun stuff. Download mode says SM-N910T. Settings says SM-N910F. Anyway, he tries flashing the firmware via odin, fails, I have him try multiple things (I'm pretty tech savvy when it comes to this type of stuff) but it always failed. Also, "Current Binary" and "System Status" are both custom, and the KNOX counter is 0x1.
So what I'm asking is, how to fix this problem for him? What steps should he take (or should I help him take)? Is this actually a T-Mobile phone from the USA, but rooted to work with O2 sim cards? The hell is going on here?
Thanks for any replies, and all suggestions will be taken seriously and addressed.
Click to expand...
Click to collapse
Looks like its an refurbished note 4 original motherboard is N910T and faked with N910F software cuz N910F has more value in Market.
So the bottom line is you have N910T Tmobile note 4 and you have to flash N910T firmware but after flash firmware from odin you have to immediately boot into stock recovery by pressing 3 button combo and do factory reset to get clean fresh opreating system otherwise it will get stuck in a bootloop at samsung logo.
First boot after flash and factory reset can take upto 10 minutes.
You can get firmware from www.sammobiles.com/firmwares
Or from link below for faster download.
https://androidfilehost.com/?fid=890129502657581810
Remember once you flash this latest marshmalow firmware there is no way you can ever downgrade to 5.1.1 again.
Good luck
Trex888 said:
Looks like its an refurbished note 4 original motherboard is N910T and faked with N910F software cuz N910F has more value in Market.
So the bottom line is you have N910T Tmobile note 4 and you have to flash N910T firmware but after flash firmware from odin you have to immediately boot into stock recovery by pressing 3 button combo and do factory reset to get clean fresh opreating system otherwise it will get stuck in a bootloop at samsung logo.
First boot after flash and factory reset can take upto 10 minutes.
You can get firmware from www.sammobiles.com/firmwares
Or from link below for faster download.
https://androidfilehost.com/?fid=890129502657581810
Remember once you flash this latest marshmalow firmware there is no way you can ever downgrade to 5.1.1 again.
Good luck
Click to expand...
Click to collapse
Thanks so much! Everything is flashing on his phone right now like it should be. Appreciate it a bunch!
I also used samsung-firmware.org. I would use sammobile but I only had enough on my card for a 48 hour upgrade.