Hi, i flashed the combi file, everything was fine then flashed the stock and it zipped through in 4 seconds and said pass. The phone restarts and boots into the combi file screen. I've tried the original stock rom and 3 others, same happens every time.
I've done this same process about 30 times and never had a problem.
It's an s8 g950f 8.0 on binary 2.
I've added an image of odin.
Any help please?
Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
skg76 said:
Hi, i flashed the combi file, everything was fine then flashed the stock and it zipped through in 4 seconds and said pass. The phone restarts and boots into the combi file screen. I've tried the original stock rom and 3 others, same happens every time.
I've done this same process about 30 times and never had a problem.
It's an s8 g950f 8.0 on binary 2.
I've added an image of odin.
Any help please?
Thanks
Click to expand...
Click to collapse
I see your using EVR. Try the latest firmware. CRF7. Use .csc file not home_csc and enable repartition in odin.
Edit: ignore that I see it's latest. But try with repartition checked and .csc file. It will wipe data
I did try the csc on the first rom after it did the 4 second pass using home csc and odin froze, no errors just stopped on sboot. After 10 minutes i unplugged the phone and got "watchdog detected" at the top of the screen. On the combi start screen it says there's g950fxxu2are1 which is the combi and below next to "phone" g950fxxu2crf1. I haven't tried putting crff1 on it.
I just tried with the csc on this one and it froze again on sboot, i left it this time and it got a fail after 15 minutes!
Btw i used the evr because the phone is locked to ee.
I've just realized there is no rom called crf1, the only binary 2 are cred and crf7 i've tried both twice from different regions, the first 3 times were from tutorials.. Even though odin is saying pass it's obviously not entering the phone. Is there any sort of security triggered by attempting to use the adb frp unlock tool? I've tried 2 versions, one with a bat and one with an interface, the one with the bat had some google login error in the cmd, the interface one kept alternating between online/offline and didn't recognize the phone although it did say pass after clicking unlock.
Thanks
skg76 said:
I did try the csc on the first rom after it did the 4 second pass using home csc and odin froze, no errors just stopped on sboot. After 10 minutes i unplugged the phone and got "watchdog detected" at the top of the screen. On the combi start screen it says there's g950fxxu2are1 which is the combi and below next to "phone" g950fxxu2crf1. I haven't tried putting crff1 on it.
I just tried with the csc on this one and it froze again on sboot, i left it this time and it got a fail after 15 minutes!
Btw i used the evr because the phone is locked to ee.
I've just realized there is no rom called crf1, the only binary 2 are cred and crf7 i've tried both twice from different regions, the first 3 times were from tutorials.. Even though odin is saying pass it's obviously not entering the phone. Is there any sort of security triggered by attempting to use the adb frp unlock tool? I've tried 2 versions, one with a bat and one with an interface, the one with the bat had some google login error in the cmd, the interface one kept alternating between online/offline and didn't recognize the phone although it did say pass after clicking unlock.
Thanks
Click to expand...
Click to collapse
https://updato.com/firmware-archive-select-model?record=58D81E6A803411E89F15FA163EE8F90B
Use this exact firmware.
Use the CSC file. NOT home_csc
Check repartition. It should not fail at sboot.bin
It's the same one as i'm using mate, that's where i got it! Something i missed, on the download on updato it says "phone: G950FXXU2CRF1" which is what i mentioned on my last post. On the front screen when i start the phone it has the pda as the combi but the phone bit is from the stock rom. So the stock rom must be partially loading when it passes.
Here's images of the front screen and the download screen. Download screen says the system is samsung official when it's loading the combi.
Is there any way of just wiping the phone of the os and starting again?
I appreciate your time.
Sussed it! You see on the first screenshot, i wondered what the lz4 extension was, i'd never seen it before. Turns out it's a new extension that 3.12 doesn't support so they brought out 3.13 with lz4 support!
Thanks
skg76 said:
Hi, i flashed the combi file, everything was fine then flashed the stock and it zipped through in 4 seconds and said pass. The phone restarts and boots into the combi file screen. I've tried the original stock rom and 3 others, same happens every time.
I've done this same process about 30 times and never had a problem.
It's an s8 g950f 8.0 on binary 2.
I've added an image of odin.
Any help please?
Thanks
Click to expand...
Click to collapse
Hello, this is my first post on this website, i always found usefull informations on it and i want to submit you a solution for your problem.
I faced the same problem and it was solved by using odin 3.13. With odin 3.12, the flash process was taking only few seconds exactly as you.
Combination file used :
COMBINATION_FA70_G950FXXU2ARE1
Rom file used (flashed with home_csc, not csc) :
G950FXXU2CRF7_G950FOXM2CRF7_XEF
Hope i will help you
Related
Hello,
I was cleaning my closet today and found my long forgotten Galaxy S4. I turned it on and a update notification poped (for 4.4.2), so far so good. The updated installed successfully and everything is wroking fine, however I can't turn Wifi on anymore. It worked just fine before the update!
So far I've tried doing the following:
I'v taken the battery out, both after shutting down the device and while the device is on.
I've factory reseted the device.
I've re-flashed the same official build using odin.
I've rooted the device to check wpa_supplicant.conf permissions and they seem to be fine (system:wifi)
I've flashed Wifi-fix kernel.
None of the above helped. I still can't turn it on. When I click the toggle or swipe the switch in settings it hangs a bit, stays dark then automatically goes back off on it's own.
Any help would be appreciated!
m.alkhalel said:
Hello,
I was cleaning my closet today and found my long forgotten Galaxy S4. I turned it on and a update notification poped (for 4.4.2), so far so good. The updated installed successfully and everything is wroking fine, however I can't turn Wifi on anymore. It worked just fine before the update!
So far I've tried doing the following:
I'v taken the battery out, both after shutting down the device and while the device is on.
I've factory reseted the device.
I've re-flashed the same official build using odin.
I've rooted the device to check wpa_supplicant.conf permissions and they seem to be fine (system:wifi)
I've flashed Wifi-fix kernel.
None of the above helped. I still can't turn it on. When I click the toggle or swipe the switch in settings it hangs a bit, stays dark then automatically goes back off on it's own.
Any help would be appreciated!
Click to expand...
Click to collapse
strange issue after OTA / full package Odin flash
it reminds me kernel mismatch, as seen in this root procedure - http://forum.xda-developers.com/galaxy-s4/general/root-how-to-obtain-root-permissions-t2862768
Maybe this image is incorrect or something.
Try different one.
th3cr0w said:
strange issue after OTA / full package Odin flash
it reminds me kernel mismatch, as seen in this root procedure - http://forum.xda-developers.com/galaxy-s4/general/root-how-to-obtain-root-permissions-t2862768
Maybe this image is incorrect or something.
Try different one.
Click to expand...
Click to collapse
Thanks for the reply. That's the exat same tutorial I used to root my device (so I can check permissions of the wifi config files). I flashed a the official build image after that so the kernel shouldn't be the problem?
Btw I downloaded the image from sammobile and the md5 was correct!
Edit:
Here's what logcat says:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
m.alkhalel said:
Hello,
I was cleaning my closet today and found my long forgotten Galaxy S4. I turned it on and a update notification poped (for 4.4.2), so far so good. The updated installed successfully and everything is wroking fine, however I can't turn Wifi on anymore. It worked just fine before the update!
So far I've tried doing the following:
I'v taken the battery out, both after shutting down the device and while the device is on.
I've factory reseted the device.
I've re-flashed the same official build using odin.
I've rooted the device to check wpa_supplicant.conf permissions and they seem to be fine (system:wifi)
I've flashed Wifi-fix kernel.
None of the above helped. I still can't turn it on. When I click the toggle or swipe the switch in settings it hangs a bit, stays dark then automatically goes back off on it's own.
Any help would be appreciated!
Click to expand...
Click to collapse
I had the same issue with my S4. Had.Had to get the mobo changed.Luckily it was within the warranty period.
50103 said:
I had the same issue with my S4. Had.Had to get the mobo changed.Luckily it was within the warranty period.
Click to expand...
Click to collapse
Did they write the cause in the repair quote?
Two ways of sorting this one.
1/ Flash a stock firmware which will fix your GSM and LTE modems along with the baseband. You'll wipe your internal storage but that's the way to go if you want a clean start.
2/ Flash the right GSM and LTE modems along with the baseband. Good if you want to keep your existing rom and not wipe you internal storage however -
It is essential to run the same versions for the Modem and Non-Hlos files as the chips talk to each other while the phone operates.
MODEM.bin = firmware for GSM Interface
NON-HLOS.bin / Firmware for LTE & WiFi Interfaces
here's where I got my modem and LTE modems from:
http://forum.xda-developers.com/showpost.php?p=50965837
Regards,
David.
duxxyuk said:
Two ways of sorting this one.
1/ Flash a stock firmware which will fix your GSM and LTE modems along with the baseband. You'll wipe your internal storage but that's the way to go if you want a clean start.
2/ Flash the right GSM and LTE modems along with the baseband. Good if you want to keep your existing rom and not wipe you internal storage however -
It is essential to run the same versions for the Modem and Non-Hlos files as the chips talk to each other while the phone operates.
MODEM.bin = firmware for GSM Interface
NON-HLOS.bin / Firmware for LTE & WiFi Interfaces
here's where I got my modem and LTE modems from:
http://forum.xda-developers.com/showpost.php?p=50965837
Regards,
David.
Click to expand...
Click to collapse
Read OP, please.
If my solution doesn't work I can only think of hardware issues. Btw - a thanks for responding is always welcome.
Hi all,
Here's my story. I have a US T-Mobile Galaxy S5. I wanted to try Lollipop as the new Touchwiz wasn't available yet for my device in early April. So hearing that it is very fast I chose CM12 and used their guide for the S5. I had a little trouble (Heimdall didn't work for some reason), but I successfully used Odin to install the custom recovery (TWRP). Then I was able to wipe and install the CM12 nightly image just fine using TWRP.
Since then I realized that my Gear 2 is only partially compatible with CM12. I've yet to find a thread that shows specific steps to get it working well with CM12, only partially, and many have had trouble even getting partial functionality. And now that Lollipop Touchwiz is available for my phone, I'd like to switch to that.
Last weekend I tried just that. I took a second backup of my CM12 build, then restored my backup from touchwiz 4.4. When I booted to it, the phone was severely crippled. The menu bar and navigation drawer were missing, and the home button did not work at all. I performed a factory reset, and it seemed to be working fine again. Next, I tried an OTA update to 5.0. That didn't work: the phone realized it had been tampered with and told me to use Kies. So I installed Kies, and attempted the update there. After some wrestling with it, I finally got the update to 5.0 started. It finished successfully (so it said anyway) but the phone failed to boot up. It was stuck on the Samsung logo screen for quite a long time. There was some blue text about recovery and I was panicking thinking somehow TWRP screwed up my ability to update w/ Kies. I tried rebooting and could not get into recovery or the OS no matter what. I tried Kies' emergency options only to have it not recognize my phone as compatible. So I went to download mode and installed TWRP again using Odin. Then I was able to boot into recovery, and I restored the backup of CM12 I took before I started all this (thank God I did that).
So now I'm back on CM12 with everything working fine, except of course my watch. I did not expect the restore back to Samsung software to be more difficult than going to CM12.
Can anyone see what I did wrong?
I gather I can install a stock rom with Odin. But all the links I find for this download take me to some sketchy download site that crawls at 50 K/s unless you pay. Am I missing something? Kies downloaded the update in a matter of minutes. Maybe that is still somewhere on my system, and I can use that w/ Odin?
bump
Have a look here for a stock ROM for your model S5 (Example, mine is the G900F)
http://forum.xda-developers.com/showthread.php?t=2715487
If there isn't one, you'll need to do the slow-ass download from sammobile dot com, then use ODIN to flash it
*Detection* said:
Have a look here for a stock ROM for your model S5 (Example, mine is the G900F)
http://forum.xda-developers.com/showthread.php?t=2715487
If there isn't one, you'll need to do the slow-ass download from sammobile dot com, then use ODIN to flash it
Click to expand...
Click to collapse
Thanks. That thread is such a mess. I searched for "G900T" and "T-mobile" but couldn't find it. I will use sammobile then. I wasn't sure before whether to trust it. Having a senior member here vouch for it helps a little.
pianowow said:
Thanks. That thread is such a mess. I searched for "G900T" and "T-mobile" but couldn't find it. I will use sammobile then. I wasn't sure before whether to trust it. Having a senior member here vouch for it helps a little.
Click to expand...
Click to collapse
That's where everyone gets them from, there and samsung - updates dot com
Both sites are banned here for linking to, but not because they are dodgy, just because the owners refused to adhere to XDA rules
They are safe to download from
so frustrating
I downloaded the lollipop stock image from sammobile, and installed with Odin. Odin reported success just like Kies did, and also just like the Kies process, my phone is still stuck in the recovery boot loop. It says RECOVERY BOOTING... in blue at the top and shows the Samsung logo powered by android. What a mess.
Is there something I can do from here to fix this?
Try flashing the PIT file along with the stock ROM, that will repartition the phone then flash the ROM, sounds like something got corrupted using KIES maybe
Double check that this is in-fact the exact model phones PIT file first or you could end up with an even worse brick
http://forum.xda-developers.com/showpost.php?p=52767244&postcount=16
More PIT files here
http://forum.xda-developers.com/showthread.php?t=2737448
There's a video of someone using PIT with ODIN on a different phone, but steps are the same
https://www.youtube.com/watch?v=4qtbEevn1VA
Basically you want it looking like this
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Thanks again for your help. I think for now I will stick with 4.4 touchwiz. I hear bad things about the touchwiz 5.0 battery life. I simply restored from the TWRP backup I used when I started all this lollipop experimentation, then did a factory reset. I should have my watch working again later tonight.
After using official CM12 for more thatn one year, I decided to go back to stock to sell phone. I moved out of stock before knox, so I didn't have it on my phone.
First I did exactly as described in this post using Odin: http://forum.xda-developers.com/showthread.php?t=2265477
They indicate 2 ROMs for Brazil, and I chose 4.4.2 - ZTO-I9505VJUFNB2-20140305104104.zip
Everything seemed OK, but there was no wifi. The button to turn it on simply didn't move to ON position. That's when I messed things up.
This is the list of actions I did after that:
1 - Hard reset. No success.
2 - Re-flashed same ROM using re-format and PIT file. No success.
3 - Flashed different modem (VJUFNC1) as described here: http://forum.xda-developers.com/showthread.php?t=2192025. Original modem before that was VJUBMG3 (I'm not 100% sure). Things got worse. I still had no wifi, but I also lost sound (even on boot screen there is no sound. Phone also got very slow stuttering. I'd say it's not usable.
4 - Tried flashing a different ROM form Sammobile specific for my country/carrier: I9505VJUFNC1_I9505ZVVFNC1_ZVV. Stil slow, no wifi, no sound.
I've reflashed these same two ROMs with and without pit a few time now. Tried hard resetting and reverting to original modem. No succes. I'm lost, to be honest. Any ideas how to fix this?
I've attached some screenshots from Phone INFO Saumsung details app:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
perr0.br said:
I've reflashed these same two ROMs with and without pit a few time now. Tried hard resetting and reverting to original modem. No succes. I'm lost, to be honest. Any ideas how to fix this?
Click to expand...
Click to collapse
Problems that i see:
- Bootloader and baseband didn't update for that you still having problems.
SOLUTION:
1. The correct firmware for you is this ONE. Download, unzip it and flash the .tar.md5 via ODIN like on the example (pic attached).
2. Let it boot normally till the final. Shutdown your phone and boot in DOWNLOAD MODE again.
3. Flash the same firmware like in the step 1 via ODIN.
4. Dial *#1234# when the process finish and tell me what appears.
Joku1981 said:
Problems that i see:
- Bootloader and baseband didn't update for that you still having problems.
SOLUTION:
1. The correct firmware for you is this ONE. Download, unzip it and flash the .tar.md5 via ODIN like on the example (pic attached).
2. Let it boot normally till the final. Shutdown your phone and boot in DOWNLOAD MODE again.
3. Flash the same firmware like in the step 1 via ODIN.
4. Dial *#1234# when the process finish and tell me what appears.
Click to expand...
Click to collapse
Hey, you rock! I flashed it only once and everything is working again. Sound, wifi, everything! Should I still flash second time? Since it's all fine I'm afraid of messing again.
Dialing *#1234# gives me:
AP: I9505VJUFNB2
CP: I9505VJUFNB2
CSC: I9505ZTOFNB3
perr0.br said:
Hey, you rock! I flashed it only once and everything is working again. Sound, wifi, everything! Should I still flash second time? Since it's all fine I'm afraid of messing again.
Dialing *#1234# gives me:
AP: I9505VJUFNB2
CP: I9505VJUFNB2
CSC: I9505ZTOFNB3
Click to expand...
Click to collapse
It's not necessary. Everything is solved now. Only press "THANKS" button if I helped you :highfive:
Gonna try this guide too. Im facing the same problems
Sent from my GT-N7105 using Tapatalk
Hey guys,
Have been running a 4.4 ROM for a while (900i) and I finally bit the bullet and installed Phoenix Rom (900F).
It worked fantastically (aside from the NFC). I did notice the GPS failed to hookup. This was a problem so I restored my kitkat backup. However....
The GPS now no longer works!!? I download an original Kitkat Rom for my provider (optus) off Sammobile. Flashed with it with Odin and still it fails to connect.
Googling has led me to no immediate resolutions. I flashed 4.4 stock again with Odin and did a 5.0 Lollipop update OTA in hope that it would fix things.
It hasn't worked thus far. Was hopefing someone would know what was going on or could provide me with some guidance.
Cheers.
Tried a full factory reset from recovery / android settings after flashing the stock ROM ?
*Detection* said:
Tried a full factory reset from recovery / android settings after flashing the stock ROM ?
Click to expand...
Click to collapse
Yep. Still no dice.
Only other thing I can think of is to grab the correct PIT file for your model S5, flash that and a stock ROM at the same time using ODIN
If it still doesn't work after that, it sounds like a hardware issue
You say your phone is the G900I? And you flashed a G900F ROM to it?
Other than that, make sure other devices can get a GPS lock, make sure it's not just the weather stopping it working
*Detection* said:
Only other thing I can think of is to grab the correct PIT file for your model S5, flash that and a stock ROM at the same time using ODIN
If it still doesn't work after that, it sounds like a hardware issue
You say your phone is the G900I? And you flashed a G900F ROM to it?
Other than that, make sure other devices can get a GPS lock, make sure it's not just the weather stopping it working
Click to expand...
Click to collapse
Not exactly sure where to get the correct PIT file to flash.
I'll try disabling all weather settings though, didn't think of that one. Cheers
http://forum.xda-developers.com/showpost.php?p=52329647&postcount=2
Scroll down and choose your model S5 PIT, Extract to .pit, add to PIT section, and flash with the stock ROM in AP or PDA section as normal
And I meant the weather outside stopping the phone seeing the satellites, heavily cloudy days can cause problems sometimes, but check settings, connections, location, is set to high accuracy
*Detection* said:
Tried a full factory reset from recovery / android settings after flashing the stock ROM ?
Click to expand...
Click to collapse
*Detection* said:
Only other thing I can think of is to grab the correct PIT file for your model S5, flash that and a stock ROM at the same time using ODIN
If it still doesn't work after that, it sounds like a hardware issue
You say your phone is the G900I? And you flashed a G900F ROM to it?
Other than that, make sure other devices can get a GPS lock, make sure it's not just the weather stopping it working
Click to expand...
Click to collapse
*Detection* said:
http://forum.xda-developers.com/showpost.php?p=52329647&postcount=2
Scroll down and choose your model S5 PIT, Extract to .pit, add to PIT section, and flash with the stock ROM in AP or PDA section as normal
And I meant the weather outside stopping the phone seeing the satellites, heavily cloudy days can cause problems sometimes, but check settings, connections, location, is set to high accuracy
Click to expand...
Click to collapse
Damn... 'Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again' :crying:
This is what I ran:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
EDIT: Running it again. Appears to be running. I think my USB hub died which is why it 'failed'. Installing applications now and will post back as to whether the GPS is working or not.
I actually have a place to be which is why I'm desperately trying to fix things.
Unfortunately it hasn't fixed the GPS. I'll have to print out the Google Maps instructions.
EDIT 2: Tried this:
Open Phone, as if you were going to make a phone call and dial -
*#9090# (*#197328640# if that doesn't work)
Menu, select Key Input, enter Q
Menu, select Key Input, enter 0000
wait for the next menu. (It takes a while.)
UMTS->COMMON->NV REBUILD->NV REBUILD->SYSTEM->PROTOCOL->GPS->IMS
or, if you don't have UMTS:
UE SETTINGS & INFO->SETTING->SYSTEM->NV REBUILD->ALL
Click to expand...
Click to collapse
No cigar. Will to another factory reset when I have a chance.
EDIT 3: Did another factory reset through the menu and it said location set my GPS. I nearly fell over!
We're working. Thanks for all your help *Detection*
Great!
Hi there , i've had the same problem when installing a custom rom like PopWiz Telstra or other rom don't no why but this fix works for me every time :
Install latest rooted TW (original Samsung Touch wiz rom) like (Alexandr ROM )
Install from play store Shortcut Master or Phone Info
Open ‘Secret Code Explorer’ menu, scroll down to 27663368378 and launch it (select ‘Launch 0’, root is required).
Then select the latest menu option Hardware sensors
Then the latest option restore (rebuild) NVRAM (or something like that. I’m writing this from my memory )
Reboot the phone
Try GPS – it should work
I have just copy paste it from a site in works like a charm on g900f
Alright. I'm unhappy with the Optus Lollipop 5.0 stock. I can't install xposed because its odexed so I'm going back to the Phoenix 900F!
This time I'm going to install it with TWRP.
Will then go through the troubleshooting attempts in an attempt to have a GREAT rom with a fully functional GPS!~
Okay, so here's my predicament:
Updating my S4 to 5.0.1 failed, so I flashed it with the proper one, but I accidentally clicked Nand Reset All, and now, this get's funny, I can't write or flash any official updates or anything, it get's to this:
Nand Reat/Write failed.
BUT HOLD THE HORSES, THERE'S MORE:
My phone says: There as a problem with the firmware, please use recovery in Kies and try again.
And it says a bunch of stuff on the top left.
If you need screenies, I am happy to provide a full video.
EDIT:
So, I got this little error now:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I never tried repartitioning, but I'm going to do some more research on this error, and see if I can't find a solution
Predated said:
Okay, so here's my predicament:
Updating my S4 to 5.0.1 failed, so I flashed it with the proper one, but I accidentally clicked Nand Reset All, and now, this get's funny, I can't write or flash any official updates or anything, it get's to this:
Nand Reat/Write failed.
BUT HOLD THE HORSES, THERE'S MORE:
My phone says: There as a problem with the firmware, please use recovery in Kies and try again.
And it says a bunch of stuff on the top left.
If you need screenies, I am happy to provide a full video.
EDIT:
So, I got this little error now:
I never tried repartitioning, but I'm going to do some more research on this error, and see if I can't find a solution
Click to expand...
Click to collapse
For Re-Partition you require a PIT file. The PIT file has to be specific to the internal storage of your phone.
So the first flash (the one with nand erase all) was successful and any subsequent flash failed?
GDReaper said:
For Re-Partition you require a PIT file. The PIT file has to be specific to the internal storage of your phone.
So the first flash (the one with nand erase all) was successful and any subsequent flash failed?
Click to expand...
Click to collapse
Really? Damn, well, I guess I could grab it, but I now don't see the firmware issue and now see the S4 Bottscreen, but now I can't boot anymore, I'm thinking of reinstalling adb toget rid of this pesky libsub error.
I'll update soon.
I don't know wht I did, but it works, and it's updating now to the newest firmware. I'll update when I wake up on how I fixed it.
This is what I used to restore it to it's normal capacities:
Guys, Kies 3 has a way of re-flashing your device to the latest official firmware for a certain model with a certain Samsung serial number, i.e. even if your device is bricked and Kies 3 cannot detect it, you enter it's model and Samsung serial number and Kies 3 will download and flash the firmware for you, all you need to do is open Kies 3, power up your device and connect it to your PC, you will then open Tools menu and select Firmware Upgrade and Initialization, if Kies 3 can detect your phone it will show you the version of the firmware that will be downloaded and flashed then you will proceed as instructed (very simple procedures), if not you will be asked to enter just your model (for example GT-N8000) and your Samsung Serial Number (usually starts with R can be found on the sticker under the battery) then it will show you the latest official firmware for your device and if you proceed it will download and flash it for you, but be careful (this will be noted by Kies 3 too) you should get a full backup of your phone as it may wipe out everything on the internal storage in the process if it's required (i.e. a bricked phone to the extent of wrong partitioning that lead to loss of imei), needless to say this process depends on your internet connection (it downloads prerequisite files and firmware files which are relatively large), from little experience I have, it's best that you use the conventional official method for any product rather than unconventional ways at the beginning to solve any problem related to any product, if it doesn't help then try your best with any other method that might help you (by the way I tried this with more than one model of Samsung smart phones, tablets and notes and it always ends up solving the problem, in some cases with my friends devices reviving the device again after being totally bricked), hope this helps .
Note: all devices I used this method with were original devices straight from Samsung (International Versions, Unbranded & Unlocked), so the firmware comes straight from Samsung (no modifications done by operators / carriers) so I'm not sure if it will work for other devices (Fake Cloned, Locked or Branded devices with carriers specific settings)
Link at:
Cant post yet.
It's good to know this.
Unfortunately there are a lot of Frankenstein S4s out there. What this means is that the phone has been repaired with mismatched parts from other S4 models, and this may lead to apps reporting a wrong phone model and other errors.
GDReaper said:
It's good to know this.
Unfortunately there are a lot of Frankenstein S4s out there. What this means is that the phone has been repaired with mismatched parts from other S4 models, and this may lead to apps reporting a wrong phone model and other errors.
Click to expand...
Click to collapse
Yeah, but mine's bought from my phone company and never broke internally, no hardware damage or anything like that, but it now bricked itself again, so I ran into another problem, it doen't show up in emergency recovery in Kies, I don't see the phone. Hmm, 'll keep trying and update the thread when I've figured this out.
Predated said:
Yeah, but mine's bought from my phone company and never broke internally, no hardware damage or anything like that, but it now bricked itself again, so I ran into another problem, it doen't show up in emergency recovery in Kies, I don't see the phone. Hmm, 'll keep trying and update the thread when I've figured this out.
Click to expand...
Click to collapse
Why are you trying to flash a 4.4.2 rom? You said you were on 5.0.1 (or at least your tried to flash that) so you probably can't flash a 4.4.2. rom.
Download a Lollipop rom and try flashing it again.
Lennyz1988 said:
Why are you trying to flash a 4.4.2 rom? You said you were on 5.0.1 (or at least your tried to flash that) so you probably can't flash a 4.4.2. rom.
Download a Lollipop rom and try flashing it again.
Click to expand...
Click to collapse
I was on 4.4.3 for a while, but it's fixed guys, I got it, with 5.0.1 rom, thanks guys!