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 .
Related
Hey guys, so I have a note 3 n9005,which i had rooted previously. This morning, I tried to flash the new touchwiz kitkat firmware via Odin and failed. Now the phone wouldn't boot up, but I an able to make it into the download mode. I have tried flashing several firmwares but neither of them works, I also had cm11 installed, so odpnt know f the bootloader has been updated or not...
So of anybody could please help me with this, that would be greatly appreciated
i have excatly the same problem tried to update s9005 via odin hong kong version to german 4.4.2 and now wont boot, odin fails only 20 seconds in read so many threads would also like to see some solutions to op.
CaptaiinCaveman said:
Hey guys, so I have a note 3 n9005,which i had rooted previously. This morning, I tried to flash the new touchwiz kitkat firmware via Odin and failed. Now the phone wouldn't boot up, but I an able to make it into the download mode. I have tried flashing several firmwares but neither of them works, I also had cm11 installed, so odpnt know f the bootloader has been updated or not...
So of anybody could please help me with this, that would be greatly appreciated
Click to expand...
Click to collapse
You also need to add some of the stuff it is written in download mode and the log in Odin when in fails. If you went to 4.4.2 on N9005 you can not return to 4.3 (which you should have read by now, there are only 200 posts in 50 threads about it). What kind of N9005 was yours (16/32/64GB), what region/CSC?
xclub_101 said:
You also need to add some of the stuff it is written in download mode and the log in Odin when in fails. If you went to 4.4.2 on N9005 you can not return to 4.3 (which you should have read by now, there are only 200 posts in 50 threads about it). What kind of N9005 was yours (16/32/64GB), what region/CSC?
Click to expand...
Click to collapse
I flashed the DBT FW again with this pit file created by HSDPilot http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77.
It worked and lash was complete now however i am stuck in SAMSUNG logo after restart.
ANy help?
solution
newapostlenew said:
I flashed the DBT FW again with this pit file created by HSDPilot http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77.
It worked and lash was complete now however i am stuck in SAMSUNG logo after restart.
ANy help?
Click to expand...
Click to collapse
hi i followed your instructions afte having the same problem.
once it was flashed and at the samsung logo
i took battery out, replaced it and started phone in recovery mode. go to wipe factory reset
then reboot
mine worked and is ok .
CaptaiinCaveman said:
Hey guys, so I have a note 3 n9005,which i had rooted previously. This morning, I tried to flash the new touchwiz kitkat firmware via Odin and failed. Now the phone wouldn't boot up, but I an able to make it into the download mode. I have tried flashing several firmwares but neither of them works, I also had cm11 installed, so odpnt know f the bootloader has been updated or not...
So of anybody could please help me with this, that would be greatly appreciated
Click to expand...
Click to collapse
darkman13 said:
i have excatly the same problem tried to update s9005 via odin hong kong version to german 4.4.2 and now wont boot, odin fails only 20 seconds in read so many threads would also like to see some solutions to op.
Click to expand...
Click to collapse
Do either of you have a 16 GB version?
Hi All,
My problem :
I wanted to install the official kitkat rom but I made a big mystake : I took N900 files instead of N9005...
After that I successfully installed the right bootloader and CWM.
I installed some cuustom roms but the setupwizard crash at the last step
I tried to flash the complete official 4.4.2 rom but odin failed with message on the phone : "ODIN : invalid ext4 image"
Anybody has any idea to help me ?
hi guys i manage to fix it, well mine anyway worked by flashing the pit i found on xda and selecting repartion on odin 3.7 along with german 4.4.2 to my n9005 from Hong Kong, re booted and done a factory reset via volume button also wiped cache and re started and it came back alive on the selected german rom 4.4.2. hope it hels others. ps my note 3 was from hong kong n9005 32gb
xclub_101 said:
You also need to add some of the stuff it is written in download mode and the log in Odin when in fails. If you went to 4.4.2 on N9005 you can not return to 4.3 (which you should have read by now, there are only 200 posts in 50 threads about it). What kind of N9005 was yours (16/32/64GB), what region/CSC?
Click to expand...
Click to collapse
hey, i wasnt trying to downgrade, i was going from cm11 to official 4.4.2. i've got a 32gb model from france i believe (the box has french written all over it so do the manuals)
newapostlenew said:
I flashed the DBT FW again with this pit file created by HSDPilot http://forum.xda-developers.com/showpost.php?p=50614669&postcount=77.
It worked and lash was complete now however i am stuck in SAMSUNG logo after restart.
ANy help?
Click to expand...
Click to collapse
dude, you are god thank you so much for that, working perfect now
xclub_101 said:
You also need to add some of the stuff it is written in download mode and the log in Odin when in fails. If you went to 4.4.2 on N9005 you can not return to 4.3 (which you should have read by now, there are only 200 posts in 50 threads about it). What kind of N9005 was yours (16/32/64GB), what region/CSC?
Click to expand...
Click to collapse
After installing DBT NB4 FW ( or with Polish NB3 FW) my LTE speeds become almost 0.
I tried multiple installs.
Any guidance?
Quick tip: Uninstall KIES.
Kies is like a big brother.
Use ODIN 1.85 and tick update phone bootloader. That's how I fixed mine. The other versions of Odin wouldn't let me update bootloader.
Of course, before you do this Flash/wipe data in recovery mode.
But uninstalling KIES solved my issue.
Sent from my SM-N9005 using Tapatalk
hi i was updating my phone from cm11 m8 to m9 when things went bad e.g. F.C. and there was no way around it so i formatted eveything via cwm (i mean everything) i normally do this when flashing and i flashed EE 4.4.2 NC4 stock firmware which first failed but installed 2nd time. then i tried my root file which again failed and passed 2nd time. last i tried flashing my standard cwm which kept failing so when i powered up my phone and it keeps saying no os installed. odin has always flashed first time round for me but today i dunno what happened. i've been flashing phones for years and i just dont know what i have done wrong today. i have tried odin 3.09, 1.87. tried flashing with pit file and two difernet usb cables. xda fourms seems like theres no soloution or thye links in the threads are removed. cant get into recovery only download mode. atm im on another pc downloading another firmware which is going to take 2.3 hours which is mental. (free registered)
on odin it says "complete write failed"
and in download mode on left corner says "
ODIN MODE,
PRODUCT NAME - GT I9505
CURRENT BINARY CUSTOM
SYSTEM STATUS CUSTOM
KNOX KERNERL LOCK 0X0
KNOX WARRANTY VOID 0X1
CSB-CONFIG-LSB 0X30
write protection enable
eMMc BURST enabled
tried keys which failed me ( no suprise there anyway)
please please is there anyone outthere to help me or atleast give me a link where i can download btu 4.4.2 firmware for free. many thanks
189cutter said:
hi i was updating my phone from cm11 m8 to m9 when things went bad e.g. F.C. and there was no way around it so i formatted eveything via cwm (i mean everything) i normally do this when flashing and i flashed EE 4.4.2 NC4 stock firmware which first failed but installed 2nd time. then i tried my root file which again failed and passed 2nd time. last i tried flashing my standard cwm which kept failing so when i powered up my phone and it keeps saying no os installed. odin has always flashed first time round for me but today i dunno what happened. i've been flashing phones for years and i just dont know what i have done wrong today. i have tried odin 3.09, 1.87. tried flashing with pit file and two difernet usb cables. xda fourms seems like theres no soloution or thye links in the threads are removed. cant get into recovery only download mode. atm im on another pc downloading another firmware which is going to take 2.3 hours which is mental. (free registered)
on odin it says "complete write failed"
and in download mode on left corner says "
ODIN MODE,
PRODUCT NAME - GT I9505
CURRENT BINARY CUSTOM
SYSTEM STATUS CUSTOM
KNOX KERNERL LOCK 0X0
KNOX WARRANTY VOID 0X1
CSB-CONFIG-LSB 0X30
write protection enable
eMMc BURST enabled
tried keys which failed me ( no suprise there anyway)
please please is there anyone outthere to help me or atleast give me a link where i can download btu 4.4.2 firmware for free. many thanks
Click to expand...
Click to collapse
Hi mate ,
For the firmware go here:
http://www.sammobile.com/firmwares/
in case you softbricked the phone:
http://forum.xda-developers.com/showthread.php?t=2265477
ive read that link before and thats like a newbie guide but i did try but no luck. the problem i think is at the end of flashing odin it says complete (write) failed. im guessing the transferring files are not sticking on the phone thus installion isnt possible. ive tried 2 different pit files for gt i9505 and its still not working. im running out f ideas and really dont want to spend 200-300 pounds on a new phone. i have tried 3 differnt firmware one ee and two btu ones but same problem
yes yes! i done it. simple or maybe pure luck...i re installed usb driver and flashed btu and pit file and vola!!. thaks for your help btw
189cutter said:
yes yes! i done it. simple or maybe pure luck...i re installed usb driver and flashed btu and pit file and vola!!. thaks for your help btw
Click to expand...
Click to collapse
Great man!!
Glad you did it.
Hello pros,
I have a S5 (G900F), bought in Germany that has a provider branding from O2 (VIA) I want to get rid off.
After searching and reading many many many threads I wasn't able to find as "safe" solution. There are some threads, where people were able to flash a stock firmware, but it was BTU. Some managed to flash the DBT, but with errors during procedure, workarounds etc.
Since the key to flash from VIA firmware to another seems always to be the correct PIT file and the PIT files also seem to come from this forum I hope to get some professional help to solve my problem. I've already read enough contradictory statements from people who think they might know something, but I'm looking not for assumption.
Here is data from my S5:
AP: G900FXXU1ANG2
CP: G900FXXU1ANG2
CSC: G900FVIA1ANG1
So I have Android 4.4.2 and would like to flash a 5.0 DBT and to keep the KNOX of course.
1. First I wondering why it not working to flash the DBT fw on a VIA S5 with the "original" DBT PIT? If the VIA phones have a different partition layout the PIT for DBT should solve this or not?
2. The most promising solution seems to be use the DBT (it's not state from which to which version the update was done) with special pit version for s5 (also not clear which one was used). When flashing with Odin at the end always a failure message will be displayed. Then disconnect and reconnect the phone and to flash only the PIT after a restart to wipe all. But as mentioned earlier that doesn't sound like a "safe or proven" solution.
Here is the link-> (German) handy-faq.de/forum/galaxy_s5_original_roms_firmware_kies/306126-samsung_galaxy_s5_branding_entfernen_sm_g900f-18.html#post2926313
3. Suppose I use the solution as described in 2. and flash the first 5.0 version (...BNL9) and then perform a update using the build in updated function on my S5 (no Odin, Kies, etc. ) to the second 5.0 version (...BOB7) will the update clean up the possible mess I've done using the procedure above? Or would it be better to use the Kies software on PC to update from 5.0 to 5.0?
I really appreciate competent help on this (and probably many other in the same situation) and no abuse of this thread for other topics .
As step by step guide with a link to PIT file and tool version info (Odin 3.09 etc.) is very welcome.
Cheers!
Flashing the DBT over an o2 branded device is ok. The upcoming error in the end, related to a to small cache.img ext4 partition comes up because of the comparsion by odin of the is and the has to be partition size.
At this stage the DBT rom at the S5 is not installed, it's like a download only. If you now flash the right *.pit as a next step this will adjust the partition size. The installation afterwards will be work and all is on a clean state. Have done this yesterday here in Germany using before o2 branded S5.
Sent from my SM-G900F using XDA Free mobile app
Thank you for the quick reply Endur.
Is there a guide I can follow for the whole procedure (what you did on you phone)? And where can I get the "right" PIT file?
I had some experience flashing a Galaxy S1, so I know this might be tricky and would like to avoid any possible heart attacks during the procedure .
Thanks in advance.
Flash bob7 DBT using Odin (I have used 3.10).
After that you will get the failed message because of wrong partition size.
Unplug USB cable.
Plug USB cable.
Flash *.pit (European for G900F 16GB)
You will get a note now about adjusted partions. The installation of bob7 DBT will start now (you see the green Android spinning). You may wipe cache and data as last step.
Sent from my SM-G900F using XDA Free mobile app
Alright, with mental support of Endur and some courage I just de-branded my phone by updating it from VIA (O2) 4.4.2 (G900FXXU1ANG2) to no branding (DBT) 5.0 (G900FXXU1BOB7). I've used Odin 3.10 and Samsung USB Driver for Mobile Phones 1.5.51.0.
The flashing procedure is basically as described in many other posts, so I don't want to create a copy of a copy. Please take a look for yourself.
Instead I will only add the steps required for O2/VIA de-branding with my experience.
As Endur mentioned the first step with Odin doesn't flash but "copy" the firmware to the phone. Due to different partition layout Odin will show an error. Remove the USB cable and replug it while Odin is still running. Remove the check from "AP" (former PDA) in Odin, select correct PIT, check "Re-Partition" in Odin and press "Start". Now comes the excitement moment. My phone got stack showing Android, powered by Google etc. I had to remove the battery, boot into recovery an wipe data and cache. So it seems to be a must instead of may.
I've used the SM-G900F_pit_16GB.zip (for German / DBT version) from forum.xda-developers.com/showthread.php?t=2737448
Good luck!
Yes, wipe data and cache is a good idea while updating from Android 4.2 up to 5.
There is a lot different for data, Dalvik was changed to ART and much, much more.
I had updated from BTU BNL9 to DBT BOB7 only. The DBT requires the greater partition size for hidden.img while BTU can be flashed without any partition change to a formerly German o2 branded device.
Sent from my SM-G900F using XDA Free mobile app
HI guys
so i just bought an s5 and i have massive screen lag, the phone is basically unusable, ive been told that it started lagging like this when the lollipop update was made, any ideas? cache wipe and factory reset do not fix a thing
cheers
Flash back to KK?
You think this would work? Seems strange screen lag? It's only what the guy said I bought it from could it be hardware?
Only one way to find out - quite a few people have lag issues with LP though
First choice......roll back to 4.4.2.......
Second choice.......Wait it out til you get OTA'd to the next upgrade......but even then, there are no guarantees that the lag will be fixed.......
I'm still on 4.4.2 and have NO INTENTION of upgrading to 5.0.+.......I've seen WAY too many people on XDA saying that LP has "screwed their phones over" in one way or another.........
Sent from my rooted kn0x0 stocKK SM-G900F S5
It's strange, the majority of people have problems with LP, I'm having none at all, immediately after the update I had bad battery life, read that a factory reset should sort it, reset the phone and have had no problems since
Everything works, everything is smooth, animations work great, no crashing, and battery life is fine
It is strange the phone is so slow it is impossible to use day to day, I'm just trying to work outhe if it's hardware or to do with the update, I haven't personally seen what the phone was like before you see
Well you're never gonna know unless you flash back to KK
Yes I will once I'm home, any recommended sources? Is kk still availible on sammobile?
Yea sammobile for the ROM, ODIN to flash
Do I need a certain rom? I'm on BTU - don't really understand it all
sollution
Go to sammobile. Find the latest vesion for ur device.
baseband:
Snapdragon bob7
exynos bob8
Then backup all ur files to a pc.
go to recovery and wipe
data reset
cache
dalvik cache
Then in advanced reboot into download mode
connect to pc
Using odin 3.07 or above select pda and select the rom file
then start. All ur lag should be fixed.
danay said:
Do I need a certain rom? I'm on BTU - don't really understand it all
Click to expand...
Click to collapse
Is your phone a G900F?
If yes, you can use this ROM
https://mega.co.nz/#!89JSAA6B!cxvVzJ6fehliaGgPteMi9WQp1eJcNKVgHha22Dml7Ls
And ODIN here
http://forum.xda-developers.com/showthread.php?t=2711451
Load the .TAR of the ROM into PDA or AP in ODIN, make sure only F-Reset Time and Auto Reboot is checked
Make sure Re-Partition is NOT checked
Put the phone into download mode and hit start
It is the g900f , is the rom standard then? Doesn't matter where the phone is from etc?
It's the UK (BTU) version for the G900F, the exact ROM Samsung would have pushed out to your phone, the same one Im running on my G900F BTU
just before i do it,
SM-G900F
knox warrenty void 0x1
BTU
G900FXXU1BOB7
CSC version shows blank though in the app 'phone info' but there in *#1234#?
and csc version G900FOXA1BOB7 - is this why im having trouble because of the conflicting files?
Bootloader, Baseband and PDA versions all say the same thing on mine (G900FXXU1BOB7)
CSC version shows G900FOXA1BOB7
--
I'd just go ahead and flash it
here goes!
no joy :/ any other ideas? i thought that was a kk rom? seems like the same?
No, that was the latest Lollipop ROM - if you want Kitkat, grab one from sammobile dot com
Search in the firmware section for G900F then BTU for UK
Did you factory reset after flashing this Lollipop ROM?
Hello. I'm a new user of SM G900F (SG). Running on lollipop with latest firmware
Bought it on Dec 26th, the device doesn't have any problem. I was happy back then, jumping form Galaxy Mini 2 to S5 is a big difference experience.
Running on official latest firmware, i only updated the phone once., around 1st - 2nd week of January.
The problem is, on Jan 14th, the G900F fail to boot (bootloop) after i set a new lockscreen from my gallery. It failed to boot, after several attemps, and wipe cache + wipe data, it booted. Haven't backed up my data yet, but i'm happy my phone is working.
On 15th, the same things happened. I set a new lockscreen. It's stil fine. But when a web-browsing on Chrome, the screen is automaically turn off (when not in use in a periout of time), but i immediatey press home button to wake the screen up. the screen didn't turn on, i press the power button. Then the bootloop happened. And this time, i can't go to recovery mode.
I've tried to re-flashing the phone using odin with official firmware, the SG one. But it didn't work. It showed Reset! with blue box on it. But still, m phone is bootlooping. My phone is still bricked. Can't go to the recovery mode either.
P.S: The phone is 2nd handed device from Singapore. I'm an Indonesian, bought the SG version bcs the Indonesia ver (G900H) is still 3G. While the SG one is 4G already. I'm using Indonesian provider (Telkomsel) and works fine on 3G or 4G so i assume the phone is unlocked. I've test the phone imei and it showed that it's the real S5, not the replica one. Antutu test showed 48,xxx score and proved that my device is the real S5 (judge by the name of device written on antutu).
I don't use micro SD. 32 gb is enough for me.
Sorry for long post and bad english. Really desperate to bring life to my phone back. Thanks before.
UPDATE: sometimes when i plugged on the device on my PC with kies on it, it booted to the homescreen. I dont know what exactly i do that caused the device booted, i only remember after stopping the bootloop (installed boot.tar, using this *the 1st method* that caused my knox 0x0, geez i didn't know that), then i flash my phone using the latest firmware (that i believe it's the correct one), then i re-plugged it on my PC with kies open, it booted! But the samsung animation logo played waaaay to long than usual. But it worked. Tried to reboot the phone to check if it's worked completely, unfortunately the device still doing bootloop. Then i tried method 2 from this, failed on odin. Turn on the device, still being jerk by doing bootloop. I gave up. Waiting for solution.
What model number does it say in download mode?
*Detection* said:
What model number does it say in download mode?
Click to expand...
Click to collapse
G900F. I downloaded the G900F SG firmware, too. Since it came from SG.
To rule out firmware (ROM) being the problem, flash this PIT file along with the stock ROM (Same time) in ODIN
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Add the PIT file to the PIT section, and the ROM to the normal PDA or AP section, and flash them together
If it still bootloops after a while after doing that, it's likely a hardware issue
*Detection* said:
To rule out firmware (ROM) being the problem, flash this PIT file along with the stock ROM (Same time) in ODIN
http://forum.xda-developers.com/attachment.php?attachmentid=2721101&d=1399024091
Add the PIT file to the PIT section, and the ROM to the normal PDA or AP section, and flash them together
If it still bootloops after a while after doing that, it's likely a hardware issue
Click to expand...
Click to collapse
what is PIT file? Read the PIT explanation here, i'm afraid it'd made my device being paperweight. So what's actually PIT file do for my bricked G900F?
Thanks.
firareza said:
what is PIT file? Read the PIT explanation here, i'm afraid it'd made my device being paperweight. So what's actually PIT file do for my bricked G900F?
Thanks.
Click to expand...
Click to collapse
It repartitions the phone, 100% wiping any old firmware, then the new stock ROM will be 100% clean and you will know if it is a hardware or software problem
How can something make your bricked phone a paperweight? It already is a paperweight
If you're gonna second guess everything you're told, enjoy your buggy phone