Related
Hi Guys,
I had rooted my phone using motochopper then yesterday I received OTA update. Everything seems to be fine then later I started getting Samsung Text-to-Speech engine has stopped working everytime I opened Gallery. It was very frustrating, so I did factory Reset. After Factory reset when I go to last screen to startup my phone(Learn about Key Features:Air view, Air gesture) and click Finish. I get "Unfortunately Settings has stopped" error. I found the stock firmware here hxxp://galaxys4root.com/galaxy-s4-stock-firmware/ But every time I use Odin I get PIT Partition not found.
Please help guys, I am stuck, don't know what to do now. :crying:
You can get the stock firmware from the "Development" section and also a step-by-step guide how to do it...search the development section for it. You can also find a lot of information about the issue you are having with the "stopped settings" error, again you can search for the info. I would also suggest you research ODIN to make sure you have the correct boxes checked so you don't hard brick your phone. Good luck.
i had the same exact issue and tried ODIN. didint work. i used to KIES to restore my firmware and it works again! try using KIES.
scott14719 said:
You can get the stock firmware from the "Development" section and also a step-by-step guide how to do it...search the development section for it. You can also find a lot of information about the issue you are having with the "stopped settings" error, again you can search for the info. I would also suggest you research ODIN to make sure you have the correct boxes checked so you don't hard brick your phone. Good luck.
Click to expand...
Click to collapse
I checked all appropriate settings for ODIN before upgrading the firmware. I got the same error all the time. I will research "Stopped Settings" error and let you know if I find anything. Thanks for the quick response.
kuraijay said:
i had the same exact issue and tried ODIN. didint work. i used to KIES to restore my firmware and it works again! try using KIES.
Click to expand...
Click to collapse
Hi I am choosing "Firmware upgrade and initialization" option to download the firmware. I put my phone into recovery mode as per steps mentioned and click "Start Upgrade" it takes around 40-50 minutes to download the firmware, then after sometime I get failed to connect to the phone. It's weird the "Start Upgrade" option is only enabled after I properly connect the cable and Kies have recognized the phone. Then why after some time it would say failed to recognized please try again?
zukaa12 said:
Hi I am choosing "Firmware upgrade and initialization" option to download the firmware. I put my phone into recovery mode as per steps mentioned and click "Start Upgrade" it takes around 40-50 minutes to download the firmware, then after sometime I get failed to connect to the phone. It's weird the "Start Upgrade" option is only enabled after I properly connect the cable and Kies have recognized the phone. Then why after some time it would say failed to recognized please try again?
Click to expand...
Click to collapse
weird mine never said enter recovery. what i did was plugged in my phone and i did the ""Firmware upgrade and initialization" then it gose through all the agreements and downloads the firmware. then it'll auto boot in to download mode for the install. are you using the stock usb? which port are you using on your computer? is KIES up to date? do you have the right drivers?( then again i think kies will install them but just in case) try already being in download mode.
also you can try this http://forum.xda-developers.com/showthread.php?t=2261232
I tried same at&t stock firmware but this time I used Odin 3.0.7 like Adam recommended in another post to upgrade and it worked like a charm. Before I was using Odin 1.8.5 and I was getting Missing PIT partition error all the time.
Thanks all for the quick response.
kuraijay said:
i had the same exact issue and tried ODIN. didint work. i used to KIES to restore my firmware and it works again! try using KIES.
Click to expand...
Click to collapse
I get different errors trying to flash stock ROM in Odin too. Missing PIT error mostly. Now phone is stuck at bad upgrade screen. Kies won't detect phone to use that method to restore either. Any other suggestions??
stumpmuncher said:
I get different errors trying to flash stock ROM in Odin too. Missing PIT error mostly. Now phone is stuck at bad upgrade screen. Kies won't detect phone to use that method to restore either. Any other suggestions??
Click to expand...
Click to collapse
Read the post above yours. Use the latest Odin 3.0.7.
-Sent from my Samsung Galaxy Note II using Tapatalk 2
What NOT to do with a new S4
RMXO said:
Read the post above yours. Use the latest Odin 3.0.7.
-Sent from my Samsung Galaxy Note II using Tapatalk 2
Click to expand...
Click to collapse
Did. Wouldn't have appealed for help without first making sure I followed the OP's instructions perfectly. I know the rules. I read the other posts before posting. I'm here for 2 things: To learn how to get the most potential out of my devices and to contribute from my experiences when I can. Thanks for your prompt reply though...
EDIT: solution to my stuck phone problem was solved by visit to ATT store for replacement. I can tell you what happened to my 7 day old device that brought it to the point where it would not load through Kies or Odin:
Eager to remove Samsung & ATT bloat stuff, I rooted using motochopper then used Titanium Backup to remove all ATT related apps & some of the Samsung apps. I got the unlock icon on lock screen as others have after root. I removed Superuser and replaced with SuperSU. Unlock icon went away and phone status went back to official. This is when I started noticing the Samsung text-to-speech program would frequently FC during the launch of few apps. Internet would also FC during certain operations. I read of others having success installing the stock ROM with ODIN and decided to give it a try. At first I got the no PIT error then finally after a few repeated attempts it moved past that point but then failed for some other reason during installation. I did notice a little activity on the progress bar on my device during Odin flash, but when the flash failed, that was it. My device was locked up. My PC & Kies would detect the device but could never connect or mount the device. My guess is that some of the Samsung apps I deleted were tied to the Samsung engines and the lack of their presence somehow caused FCs. Comments and questions appreciated.
Got the same Odin Mode Recovery Kies problem, No Pit fixed with ODIN 3.07 used PDA and loaded normal firmware.
Hi
I today tried to flash my S5 using this Firmware: -
http://click.xda-developers.com/api... | Samsung Galaxy S 5 | XDA Forums&txt=MegaNZ This is the firmware in the 2nd post on the "[SM-G900F] S5 Firmware Thread "
This is the Official Stock Rom for my device and was under the impression it was not country specific.
I had Lollipop installed already from when it was first released and as always used Odin (3.09 in this instance) to flash. It flashed without problem. I have just been away for 2 weeks and in the meantime, my wife flashed her S5 through Wifi after getting popups reminding her to do so. She had no difficulty upgrading from KitKat to Lollipop either.
However a massive PITA for me was that I could not mute the volume as easily as I could with KitKat and when my wife showed me she could do it, after her upgrade, I simply had to upgrade, her version being the same as the one quoted above.
So this morning I downloaded the file and proceeded to flash (again using Odin 3.09). It got all the way but at the end, just before writing, I got "Fail" - it had completely failed and I was stuck in the "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again." screen." I had never seen this before and thought I'd bricked my phone.
After searching in vain for a solution on this forum, I got nowhere fast. However I wondered if I could take the battery out, replace it to a blank screen and try going into "download mode" once more.
I could indeed! So I then downloaded the same file (I presumed) from Sammobile, to see if I could start over. It worked!!!! And more importantly, I too can mute my phone's volume - Happy Days !!!
But it seems (and from Googling) some of your firmware files are corrupt. Not my PC as I checked the file before using it to ensure it was binary correct.
So I am reporting this officially because I can see no other threads on this subject - maybe in a specific post but not, that I can see, in a specific thread.
I have been a member here for some years and never had an issue like this - your firmwares have been always ok until now. They are faster to download which is why I use them. The Sammobile file took 2 hours to download on their free service but it was fine, unlike the one above.
Any thoughts ?
roz
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 .
I'm pretty sure I've ended by bricking my Note 4 N910G.
1. On stock, the phone started becoming very slow / unresponsive. Not the things a
2. I decided to take the "if it's broken flash it" solution. Flashed to stock but got stuck with a "ODIN flash write failure" message.
3. Have tried multiple approaches including installing TWRP / CWM without any luck. Can't flash a thing through ODIN. I've tried more options than I should have.
Taking it to the service center today. Any advice would help.
Please note:
1. I did not make a mistake with the stock ROM version. It's N910G
2. Not an expert, but have had a Galaxy S and Note 2 before this - so know my way around here. At least, that's what I thought till now.
Took it to the service center today. They're not servicing it since its rooted. Asking for USD 300 to replace the motherboard. SOS - PIT file for N910G is the last resort.
Nothing flashes at all with odin ? I think you may need to flash a pit file.
Have you tried kies emergency firmware restore or mskips toolkit? Mskip usually has an emergency firmware rescue as well. Also if you can connect through adb someone more advanced than me might be able to help you
Sent from my SM-N910F using Tapatalk
Got a huge problem with a AT&T phone Samsung Galaxy Note 4. Got it from an ebay handler. It was supposed to be rooted. However, after installing Magisk software (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) I got the message "System software not authorized by ATT has been found on your phone". Whenever I turn it on, I see it and the phone doesn't start. Since more than 6 months have passed, the ebay handler declined to help. I called AT&T, but since the phone is rooted, they declined to repair it even after I offered to pay. There are some solutions I found online for other samsung galaxy models, but none which works for note 4.
Tried to restore the system to the factory version, it said that restoration has been successful, but I still see the AT&T message.
I followed the instructions to unbrick the phone by reinstalling the firmware - the method that should work for all phones (not just note 3) https://www.youtube.com/watch?v=bv_NCfYemEs with the firmware for SM-N910A , however no matter how long I waited, the download process never completed.
Any suggestions?
Thanks!
vmmessage said:
Got a huge problem with a AT&T phone Samsung Galaxy Note 4. Got it from an ebay handler. It was supposed to be rooted. However, after installing Magisk software (https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445) I got the message "System software not authorized by ATT has been found on your phone". Whenever I turn it on, I see it and the phone doesn't start. Since more than 6 months have passed, the ebay handler declined to help. I called AT&T, but since the phone is rooted, they declined to repair it even after I offered to pay. There are some solutions I found online for other samsung galaxy models, but none which works for note 4.
Tried to restore the system to the factory version, it said that restoration has been successful, but I still see the AT&T message.
I followed the instructions to unbrick the phone by reinstalling the firmware - the method that should work for all phones (not just note 3) https://www.youtube.com/watch?v=bv_NCfYemEs with the firmware for SM-N910A , however no matter how long I waited, the download process never completed.
Any suggestions?
Thanks!
Click to expand...
Click to collapse
Grab latest firmware for N910A from here
https://androidfilehost.com/?fid=745425885120746376
Make sure samsung usb drivers are properly installed on your pc before you begin.
STEPS
1 Download odin and Firmware and Extract it.
2 open odin tool and upload firmware in AP slot.
Odin can take up to 5 minutes to upload firmware so be patient
3 put phone into download mode
4 connect phone via usb cable and hit start.
5 After FLASH once odin shows pass boot into stock recovery by pressing 3 button combo volume up+ home+ power.
6 in recovery do wipe cache+ wipe data factory reset.
7 reboot system and wait 10 to 5 minutes.
DONE
Trex888 method should be good, however you may need to find the pit file and flash it before odin back to stock. I bought my note 4 already rooted, but the person that did it used the wrong files to flash. Mine was good but buggy. The rom flashed was not verizon, and it locked out some partitions including the one where the imei was held. I had to fix the partitions with the pit file then reflash to a different rom and i was good to go after that.
Thanks
Thanks for the reply! Great! I will try that - very hopeful
tattmann said:
Trex888 method should be good, however you may need to find the pit file and flash it before odin back to stock. I bought my note 4 already rooted, but the person that did it used the wrong files to flash. Mine was good but buggy. The rom flashed was not verizon, and it locked out some partitions including the one where the imei was held. I had to fix the partitions with the pit file then reflash to a different rom and i was good to go after that.
Click to expand...
Click to collapse
You dont need dedicated pit file unless your device has errors such as "dm verity verification failed" or failed to mount cache/efs etc etc.
If stock rom flashing by odin went smoothly no require for repartition or pit file.
Playing with pit file and repartition is extremely dangerous and can cause device to hard brick so i would not recommend unless some serious issues with device.
Fyi every samsung stock firmware has pit file in the system image by default and odin take advantage of it by it self during flashing.
Have a nice day.
Trex888 said:
You dont need dedicated pit file unless your device has errors such as "dm verity verification failed" or failed to mount cache/efs etc etc.
If stock rom flashing by odin went smoothly no require for repartition or pit file.
Playing with pit file and repartition is extremely dangerous and can cause device to hard brick so i would not recommend unless some serious issues with device.
Fyi every samsung stock firmware has pit file in the system image by default and odin take advantage of it by it self during flashing.
Have a nice day.
Click to expand...
Click to collapse
in my case, whoever flashed my phone flashed an f file instead of the v file. It lost the imei and would not recognize a sim card. I tried flashing original firmware but the imei was still gone. The ONLY thing that saved mine was to find the correct pit file and flash it before firmware. It fixed my issue and got me back up and running. every original fw flash for me failed until I flashed just the pit. I cannot explain why the original fw included in the odin package would NOT work. Hence the statement of "you may need to" instead of "you will have to".