Updating SM-92A8A to Nougat - Galaxy S6 Edge+ Q&A, Help & Troubleshooting

Hi,
I am trying to update my Samsung S6 Edge + (5.1.1 lolipop) to Nougat 7.0.
Phone Specs:
Android: 5.1.1
Baseband: G928AUCU2AOJ1
Build Number: LMY47X.G928AUCU2AOJ1
I have downloaded Nougat firmware SS-G928AUCS4CQB2-to-U4EQC6-UP.
But I can't update my phone to Nougat. I have read many post on net about updating the phone. But its not working.
I have tried Odin different version, 3.10.6, 3.10.7, 3.12.3 but non able to update the phone.
The lower version of Odin mostly crashes when Start button is clicked. I have to close Downloading screen and again go to Downloading screen on phone to go a little further but it isn't doing anything.
Mostly it stuck at 'Nand write Start' and freezes for every.
I have download the PIT file as well to use in Odin, but nothing.
I am on Windows 10, using high quality USB cable, also tried different USB ports. But update process not completing.
So please tell me what to do, is there any better Nougat Firmware that i should use (for SM-G928A)?
Btw, do i have to root my phone, that is what I have not done, is it necessary? If it is please guide be the proper way for s6 edge+.
I am really looking to some help here.
Thanks in advance.

gurupak said:
Hi,
I am trying to update my Samsung S6 Edge + (5.1.1 lolipop) to Nougat 7.0.
Phone Specs:
Android: 5.1.1
Baseband: G928AUCU2AOJ1
Build Number: LMY47X.G928AUCU2AOJ1
I have downloaded Nougat firmware SS-G928AUCS4CQB2-to-U4EQC6-UP.
But I can't update my phone to Nougat. I have read many post on net about updating the phone. But its not working.
I have tried Odin different version, 3.10.6, 3.10.7, 3.12.3 but non able to update the phone.
The lower version of Odin mostly crashes when Start button is clicked. I have to close Downloading screen and again go to Downloading screen on phone to go a little further but it isn't doing anything.
Mostly it stuck at 'Nand write Start' and freezes for every.
I have download the PIT file as well to use in Odin, but nothing.
I am on Windows 10, using high quality USB cable, also tried different USB ports. But update process not completing.
So please tell me what to do, is there any better Nougat Firmware that i should use (for SM-G928A)?
Btw, do i have to root my phone, that is what I have not done, is it necessary? If it is please guide be the proper way for s6 edge+.
I am really looking to some help here.
Thanks in advance.
Click to expand...
Click to collapse
Try this :
https://docs.google.com/uc?id=0B4sOy1rlqVoYcVZIWUN6U0h5VUE&export=download

Thank you for the firmware. I am trying it on phone now. But it is everytime stuck on File Analysis:
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1203)..
<ID:0/006> File analysis..
I am using Odin 3.12.3. What is blocking it?
Best regards,

Is there any other way then Odin to install the firmware on s6 edge plus?

Related

[Q] HELP!! I9505 bricked when flashing Odin 3.04 XXUDMH8

hello! can someone please help me with my galaxy s4 GT-i9505. I really need your help on this!
this is what happened,
a few days ago, I Got my phone unlocked from its carrier GLOBE here in Philippines.
the tech flashed it with older firmware before unlocking my phone. all went well after that.. but my phone was running an older firmware since the tech flashed it with older firmware before unlocking it.
the next day, I decided to flash it and upgrade with the firmware I9505XXUDMH8 from this website http://www.ibtimes.co.uk/articles/504394/20130907/galaxys4-gti9505-official-android422-xxudmh8-jellybean-update.htm
all went well after that. but I encountered problems on rooting and flashing with custom kernel. I've learned that the firmware I flashed from this http://www.ibtimes.co.uk/articles/504394/20130907/galaxys4-gti9505-official-android422-xxudmh8-jellybean-update.htm website includes Samsung KNOX which they say can cause rooting problems and etc.
knowing all that stuff, I decided again to revert to an earlier version of android 4.2.2 for gt-i9505 which is the I9505XXUBMG5 which I got from sammobile.com. hoping to stay clear of the KNOX rooting issues.
when I tried to flash the I9505XXUBMG5 firmware with odin 3.07, it said FAILED and now I can't basically use my phone. I'm stuck on "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
I tried flashing back the I9505XXUDMH8 which I got from here http://www.ibtimes.co.uk/articles/504394/20130907/galaxys4-gti9505-official-android422-xxudmh8-jellybean-update.htm but it still fails!! why???
I've read somewhere that the latest firmware I9505XXUDMH8 that contains KNOX can cause issues when you would try to downgrade to an earlier firmware.
I've just read that thing after I flashed to an earler version. hohohoh. has anyone been in this situation?
please help! I hope someone could help me on this. all insights will be greatly appreciated. thank you in advance!
Go to recovery and factory reset, should fix it.
If not Just flash MH8 again in Odin and then factory reset.
Sent from my GT-I9505
Obagleyfreer said:
Go to recovery and factory reset, should fix it.
If not Just flash MH8 again in Odin and then factory reset.
Sent from my GT-I9505
Click to expand...
Click to collapse
hey bro. I can't go to recovery. whenever I try to press and hold vol up+home+power, the screen would still show up the "firmware upgrade encountered an issue. please select recovery mode in kies and try again" message..
i'm really getting worried. (((
{
"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"
}
this what showed up when I tried flashing back the MH8 firmware.
jarold143 said:
View attachment 2276766
this what showed up when I tried flashing back the MH8 firmware.
Click to expand...
Click to collapse
1, Make sure u have no Kies programme running in the background kill all that and try flashing the firmware using odin
2 , if that does not wrk try flashing with "pit" file along and see the result make sure to use the correct pit file or use the link Here
Also try some different latest stock firmware u have it available
One suggestion don't panic all will be fine I have been to this situation more then 6 times using different galaxy devices all were recovered
U can also use the help thread link on my sign
Edit : http://forum.xda-developers.com/showthread.php?t=2419762 one more helpful link here
I had the same issue while flashing mh1 modem. I changed to different usb port and flashed my old modem back with newer odin.
View attachment 2276845
<ID:0/006> Added!!
<ID:0/006> Removed!!
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505XXUDMH8_I9505OXXDMHA_I9505XXUDMH8_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Set PIT file..
<ID:0/006> DO NOT TURN OFF TARGET!!
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl2.mbn
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
Click to expand...
Click to collapse
this is what odin showed up. I used different cable and different port. daaaang! what am I gonna do. huhuhu
jarold143 said:
View attachment 2276845
this is what odin showed up. I used different cable and different port. daaaang! what am I gonna do. huhuhu
Click to expand...
Click to collapse
Repeat procedure with odin 3.04
Sent from my Galaxy Nexus using xda premium
jarold143 said:
View attachment 2276845
this is what odin showed up. I used different cable and different port. daaaang! what am I gonna do. huhuhu
Click to expand...
Click to collapse
Try using Odin 3.07
or some firmware
Best option use link below amd post there he is best at this
http://forum.xda-developers.com/showthread.php?t=2265477&highlight=stock+firmware
UPDATE! problem SOLVED
thank you for all your responses. I've figured out the problem and found the culprit.
It was the USB ports of the PC I was using to flash the phone.
FIX: I tried flashing the phone from my gf's laptop with the MH8 firmware and wallah!! odin did not show any fail and I was able to use my phone back..
after everything went fine, I tried flashing back the UBMG5 firmware just for the heck of it. then ODIN showed failed. so I flashed back again to MH8 firmware and everything went OK again..
FOLLOW up Questions:
1. can't we really go back to an older firmware version?
2. I wonder what was causing my phone to constantly disconnect from the USB port. but in my gf's laptop seems to be ok and working
(I have tried it from two PC's.. it disconnects on my pc at home and my work pc)
jarold143 said:
FOLLOW up Questions:
1. can't we really go back to an older firmware version?
2. I wonder what was causing my phone to constantly disconnect from the USB port. but in my gf's laptop seems to be ok and working
(I have tried it from two PC's.. it disconnects on my pc at home and my work pc)
Click to expand...
Click to collapse
You are stuck with MH8 firmware, worse you have KNOX and can't use all those neat little apps that require system access to run.... Even if rooted...
The new bootloader that Samsung released is REALLY going to kill Samsung support in this community. Bit stupid really as most of the latest features on their new phones started out as an idea on this site by people who wanted more out of their phones and worked out how to do it....
ultramag69 said:
You are stuck with MH8 firmware, worse you have KNOX and can't use all those neat little apps that require system access to run.... Even if rooted...
The new bootloader that Samsung released is REALLY going to kill Samsung support in this community. Bit stupid really as most of the latest features on their new phones started out as an idea on this site by people who wanted more out of their phones and worked out how to do it....
Click to expand...
Click to collapse
damn. we'll i'm still hoping some developer would find a work around about this knox issue.
Same thing happened to me with MH6 (Singapore)
So here's the thing - I have a mild vision impairment and having bold fonts throughout the entire OS helps a lot. I've always used "MyFont" to change the UI font to Akzidenz Grotesk Bold (gorgeous font, really)
So anyway the MH6 update broke MyFont - something KNOX related I suppose - it couldn't apply the font changes anymore, even though it worked perfectly fine on stock unrooted MG5 firmware
So I dug up my old XXMEA firmware, Odined my phone... then I had the worst "bricking" experience I ever had
a. Couldn't make calls (black screen)
b. No sound output from speakers whatsoever (no boot sound, no touch tones, the phone doesn't "beep" when adjusting the volume, etc)
c. Erratic connectivity to H+
d. WiFi unable to turn on
e. Very unresponsive UI
So I updated to MH6 through Kies (on another PC), wiped data, and then it refused to get past the "Samsung Galaxy S4" screen - it just hung there. I flashed broodplank's vanilla 4.3 over it, and managed to at least boot up (albeit with the same issues). THEN I noticed that the baseband was still MEA - which meant that Kies kinda failed as it upgraded ONLY the main firmware but not the modem - perhaps that's why it wouldn't boot up?
After many hours of trial and error - I managed to get my phone back in working order.
1. Flashed XXUDMH6 modem
2. Downloaded XXUDMH6 (MM1, my telco) from samsung-updates.com, Odined it
3. Success
But it's kinda disheartening that Samsung "locked down" the phone with these latest updates.. what a shame. Definitely getting a Nexus when my contract is up.. even though here in Singapore they're overpriced
Hope this helps anybody stuck in the same scenario - the gist of it is.. if you want your phone to work properly, you can't downgrade your firmware. Kinda like Apple.
If irony were made of strawberries, we'd all be drinking a lot of smoothies right now - Newscaster Ned, South Park
Thank you adrian - I had exactly the same problems after I tried to re-install an older stock rom after the Knox install.
I had no wifi, the phone dialler would show a black screen and would crash the phone, plus i no longer had any system sounds.
This was down to an incorrect baseband and firmware combination that needed to be reflashed via Odin in the order that you mention in your post.
I have a German Telekom.de SGS4 and now have the following config:
Baseband I9505XXUDMH9
Kernel 3.4.0- 1220396 [email protected] #1
Build number JDQ39.I9505XXUDMH9
SELinux status: Enforcing
Thank you!
adrian3 said:
Same thing happened to me with MH6 (Singapore)
So here's the thing - I have a mild vision impairment and having bold fonts throughout the entire OS helps a lot. I've always used "MyFont" to change the UI font to Akzidenz Grotesk Bold (gorgeous font, really)
So anyway the MH6 update broke MyFont - something KNOX related I suppose - it couldn't apply the font changes anymore, even though it worked perfectly fine on stock unrooted MG5 firmware
So I dug up my old XXMEA firmware, Odined my phone... then I had the worst "bricking" experience I ever had
a. Couldn't make calls (black screen)
b. No sound output from speakers whatsoever (no boot sound, no touch tones, the phone doesn't "beep" when adjusting the volume, etc)
c. Erratic connectivity to H+
d. WiFi unable to turn on
e. Very unresponsive UI
So I updated to MH6 through Kies (on another PC), wiped data, and then it refused to get past the "Samsung Galaxy S4" screen - it just hung there. I flashed broodplank's vanilla 4.3 over it, and managed to at least boot up (albeit with the same issues). THEN I noticed that the baseband was still MEA - which meant that Kies kinda failed as it upgraded ONLY the main firmware but not the modem - perhaps that's why it wouldn't boot up?
After many hours of trial and error - I managed to get my phone back in working order.
1. Flashed XXUDMH6 modem
2. Downloaded XXUDMH6 (MM1, my telco) from samsung-updates.com, Odined it
3. Success
But it's kinda disheartening that Samsung "locked down" the phone with these latest updates.. what a shame. Definitely getting a Nexus when my contract is up.. even though here in Singapore they're overpriced
Hope this helps anybody stuck in the same scenario - the gist of it is.. if you want your phone to work properly, you can't downgrade your firmware. Kinda like Apple.
If irony were made of strawberries, we'd all be drinking a lot of smoothies right now - Newscaster Ned, South Park
Click to expand...
Click to collapse
adrian3 said:
Same thing happened to me with MH6 (Singapore)
So here's the thing - I have a mild vision impairment and having bold fonts throughout the entire OS helps a lot. I've always used "MyFont" to change the UI font to Akzidenz Grotesk Bold (gorgeous font, really)
So anyway the MH6 update broke MyFont - something KNOX related I suppose - it couldn't apply the font changes anymore, even though it worked perfectly fine on stock unrooted MG5 firmware
So I dug up my old XXMEA firmware, Odined my phone... then I had the worst "bricking" experience I ever had
a. Couldn't make calls (black screen)
b. No sound output from speakers whatsoever (no boot sound, no touch tones, the phone doesn't "beep" when adjusting the volume, etc)
c. Erratic connectivity to H+
d. WiFi unable to turn on
e. Very unresponsive UI
So I updated to MH6 through Kies (on another PC), wiped data, and then it refused to get past the "Samsung Galaxy S4" screen - it just hung there. I flashed broodplank's vanilla 4.3 over it, and managed to at least boot up (albeit with the same issues). THEN I noticed that the baseband was still MEA - which meant that Kies kinda failed as it upgraded ONLY the main firmware but not the modem - perhaps that's why it wouldn't boot up?
After many hours of trial and error - I managed to get my phone back in working order.
1. Flashed XXUDMH6 modem
2. Downloaded XXUDMH6 (MM1, my telco) from samsung-updates.com, Odined it
3. Success
But it's kinda disheartening that Samsung "locked down" the phone with these latest updates.. what a shame. Definitely getting a Nexus when my contract is up.. even though here in Singapore they're overpriced
Hope this helps anybody stuck in the same scenario - the gist of it is.. if you want your phone to work properly, you can't downgrade your firmware. Kinda like Apple.
If irony were made of strawberries, we'd all be drinking a lot of smoothies right now - Newscaster Ned, South Park
Click to expand...
Click to collapse
can i have a step by step of you have done?I got similar problem with your phone...I upgraded to 4.4.2, it wasn't good then I succesfully downgraded to 4.2.2 but not wifi, no sound, and dialer and ui problem. Im currently running on XXUAMDD fw...I tried flashing via odin 3.04, 3.07 and 3.09 I9505XXUEMK9 and I9505XXUEMKE firmwares but it always fails.
agent2727 said:
can i have a step by step of you have done?I got similar problem with your phone...I upgraded to 4.4.2, it wasn't good then I succesfully downgraded to 4.2.2 but not wifi, no sound, and dialer and ui problem. Im currently running on XXUAMDD fw...I tried flashing via odin 3.04, 3.07 and 3.09 I9505XXUEMK9 and I9505XXUEMKE firmwares but it always fails.
Click to expand...
Click to collapse
Means u cant downgrade no more bro. Once you have updated to a newer firmware, it also means that ur bootloader has also been changed.
So when u try to downgrade, u are only downgrading the firmware. But the bootloader still stays the same which only works for the latest firmware u've flashed. This might explain why some things i ur fone doesnt work after the downgrade.
Hope this answered ur question
Sent from my SM-N9005 using XDA mobile app

Noob - Rooted Samsung Note 4 randomly turning on and off

Hi ,
I recently rooted my Samsung Note 4 (running Lolly Pop 5.1.1) and about 5 days later it started turning on and off by itself. I noticed it only started doing it when I went to update the apps. Often when it self restarts it will get into a stuck loop, where it gets to the load screen, freezes, and re-starts again. The only method to get it to work again is to leave it with the battery out for 30 + mins and it always seems to right itself - except.. I thought it would be a smart idea to do a factory reset. Now it keeps getting stuck in the loop on the load screen of optimizing apps, and since this is a bit a of a lengthy process, it always resets itself now.
What can I do? Any help from experienced individuals appreciated!
Really don't want to brick a 4 month old $899 phone.
Thanks in advance people
Make a clean rom installation; download the latest firmware for your variant, clean dalvick, cache, system, and data. Then, flash the firmware through ODIN. After that, root with a custom kernel. If you have an N910C I recommed you this kernel:
http://forum.xda-developers.com/showthread.php?t=3206548
Hi Bryan,
Samsung Kies will not let me do a latest firmware install, it just keeps popping up 'device not supported' when I try to do a software reinstall and upgrade via Kies on my laptop
Is there anyway to do this on the fly?
Thanks for your help
bryanstevecl said:
Make a clean rom installation; download the latest firmware for your variant, clean dalvick, cache, system, and data. Then, flash the firmware through ODIN. After that, root with a custom kernel. If you have an N910C I recommed you this kernel:
http://forum.xda-developers.com/showthread.php?t=3206548
Click to expand...
Click to collapse
Jason040 said:
Hi Bryan,
Samsung Kies will not let me do a latest firmware install, it just keeps popping up 'device not supported' when I try to do a software reinstall and upgrade via Kies on my laptop
Is there anyway to do this on the fly?
Thanks for your help
Click to expand...
Click to collapse
Visit SamMobile and register, then search the appropriate firmware for your phone variant.
Example: My phone is an Exynos-Note 4 (N910C) and my operator is Tigo Colombia which in SamMobile appears COL. You just have to register, search the firmware for your phone and flash it using ODIN 3.10. (ODIN is a program you use to install firmwares in Samsung phones) There are lots of tutorials for flashing, it is quite simple.
bryanstevecl said:
Visit SamMobile and register, then search the appropriate firmware for your phone variant.
Example: My phone is an Exynos-Note 4 (N910C) and my operator is Tigo Colombia which in SamMobile appears COL. You just have to register, search the firmware for your phone and flash it using ODIN 3.10. (ODIN is a program you use to install firmwares in Samsung phones) There are lots of tutorials for flashing, it is quite simple.
Click to expand...
Click to collapse
Okay, thanks for that Bryan. I understand now.
bryanstevecl said:
Visit SamMobile and register, then search the appropriate firmware for your phone variant.
Example: My phone is an Exynos-Note 4 (N910C) and my operator is Tigo Colombia which in SamMobile appears COL. You just have to register, search the firmware for your phone and flash it using ODIN 3.10. (ODIN is a program you use to install firmwares in Samsung phones) There are lots of tutorials for flashing, it is quite simple.
Click to expand...
Click to collapse
Won't let me do a flash Bryan, I get this error message
"ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)"
Any ideas? Thanks
bryanstevecl said:
Visit SamMobile and register, then search the appropriate firmware for your phone variant.
Example: My phone is an Exynos-Note 4 (N910C) and my operator is Tigo Colombia which in SamMobile appears COL. You just have to register, search the firmware for your phone and flash it using ODIN 3.10. (ODIN is a program you use to install firmwares in Samsung phones) There are lots of tutorials for flashing, it is quite simple.
Click to expand...
Click to collapse
Okay, all fixed now. Disregard last message. Thanks for your help mate, much appreciated!!!

Unflashable S7Edge?

I have an S7 Edge from Verizon that I had previously flashed U on. I was going to try flashing the AT&T FW so I could flash the unreleased final Nougat.
I found the AT&T stock FW (G935AUCS4APK1) but Odin would not flash it. It stalls at
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
and the phone displays "Odin protocol version error!". So I canceled the flash and rebooted, and got a screen that said "An error has occurred while updating the device software. Use the emergency recovery function in the Smart Switch PC software".
Now, I can't flash anything. Every FW I try to flash with Odin results in the "Odin protocol version error!". Smart Switch does not recognize the phone either.
A little help please?
Maybe try a diff USB port/cable? Did you have more than one of each file like ap others?
Sent from my SM-G935U using Tapatalk
I had two CSC files. Hone_csc and CSC.
I had several different FW that I tried, the AT&T one I mentioned, PI3 Vzw and pl4 U. None will flash. I noticed that download mode shows the model number as g935a now. I tracked down a newer version of Odin that's supposed to work with the att model, but I haven't had a a chance to try it yet.
Edit: The 3.12 version of Odin worked and I got the AT&T APK1 to flash. Time to go flash Nougat!
raduque said:
I had two CSC files. Hone_csc and CSC.
I had several different FW that I tried, the AT&T one I mentioned, PI3 Vzw and pl4 U. None will flash. I noticed that download mode shows the model number as g935a now. I tracked down a newer version of Odin that's supposed to work with the att model, but I haven't had a a chance to try it yet.
Edit: The 3.12 version of Odin worked and I got the AT&T APK1 to flash. Time to go flash Nougat!
Click to expand...
Click to collapse
Don't you have a. Verizon sim though I flashed the update before nougat and could not make calls and data was also flakey.
Sent from my SM-G935V using XDA-Developers Legacy app
Crsdr37 said:
Don't you have a. Verizon sim though I flashed the update before nougat and could not make calls and data was also flakey.
Click to expand...
Click to collapse
I don't have a SIM card in it, though. Just using it to play around with the OS. SO far, it reminds me of my Note 7. I put the phone away in a drawer, just too depressing to use. I wish I never got rid of my Note 7.

FRP locked tab a, need some "special" help

So, i recently (like a month or so ago) bought a tab a (from Ger, since i live here) and directly rooted it.
Now since i have some rooting exp from rooting my samsung s4 and my xperia play (who remembers that phone lol) and i didnt find anything new during my (rather short) research, i directly got odin, got twrp and just went right ahead. I did NOT read about the fact that there is a FRP lock and that i have to do the OEM unlock thing in the dev options. This went well a few weeks until i started my tab a yesterday and got the FRP msg on boot. I did some more research, banged my head against a wall for not reading enough beforehand and got a (to my knowledge) stock firmware with recovery ( T580ZCU2AQH2_T580CHN2AQH2_CHN )
and tried to flash that over Odin. It didnt work and i get this
<ID:0/008> Added!!
<ID:0/008> Odin engine v(ID:3.1207)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Set PIT file..
<ID:0/008> DO NOT TURN OFF TARGET!!
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> NAND Write Start!!
<ID:0/008> SingleDownload.
<ID:0/008> sboot.bin
<ID:0/008> param.bin
<ID:0/008> cm.bin
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> FAIL!
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
in the command line thingy with the text
FRP is enabled, ignore PIT download
SW REV. Invalid type.
FRP is enabled, not allow download non-FRP BOOTLOADER binary
can anyone tell me whats wrong, and suggest what to do instead?
same issue.. Did you manage to get a fix for this?
RenVilo said:
same issue.. Did you manage to get a fix for this?
Click to expand...
Click to collapse
actually yes, i did this a few months ago already, but iirc i flashed a stock rom from the web (just google it theyre not hard to find), without any rooting shenanigans and disabled the lock and then went through the whole process again
you might need to boot into the rom a few times to make it install the stock recovery tho
FRP lock should not prevent you from flashing a stock ROM via Odin. But you have to flash the correct Android 6 ROM. Go to Sammobile and enter SM-580 and then chose your region. Then download the ROM ending in PL4. When it boots, it will ask for your Google login and password. It is only if you don't know those that the FRP becomes a problem. If you can't flash the PL4 ROM, your problem is NOT the FRP lock, even if Odin says it is. Also, once you get Android 6 to boot, your tablet will automatically update to the latest version from Samsung so long as you don't try to root or install TWRP before it has a chance to update.
edit: BTW, when flash the PL4 ROM, flash only the AP and BL modules.
Yeah i did some research following all that up and noticed i had the wrong ROM because some sites on the internet are very non descriptive, but like i said above i got it working shortly after and i now have a linageOS rom with a more recent android version, all working, thank you anyways for responding how to properly resolve this ^^
New user in need of help
lewmur said:
FRP lock should not prevent you from flashing a stock ROM via Odin. But you have to flash the correct Android 6 ROM. Go to Sammobile and enter SM-580 and then chose your region. Then download the ROM ending in PL4. When it boots, it will ask for your Google login and password. It is only if you don't know those that the FRP becomes a problem. If you can't flash the PL4 ROM, your problem is NOT the FRP lock, even if Odin says it is. Also, once you get Android 6 to boot, your tablet will automatically update to the latest version from Samsung so long as you don't try to root or install TWRP before it has a chance to update.
edit: BTW, when flash the PL4 ROM, flash only the AP and BL modules.
Click to expand...
Click to collapse
Hello, I was trying to Root my Samsung SM-T510 10.1 Tablet. I am now stuck in the Download Mode in Odin & only have red writing up in the left hand corner. Any Help or advice is much appreciated. I've tried holding the buttons and it pops right back up to the same screen saying Don't power down. with the android logo! Any Advice?
---------- Post added at 05:45 PM ---------- Previous post was at 05:27 PM ----------
johnnyonetime said:
Hello, I was trying to Root my Samsung SM-T510 10.1 Tablet. I am now stuck in the Download Mode in Odin & only have red writing up in the left hand corner. Any Help or advice is much appreciated. I've tried holding the buttons and it pops right back up to the same screen saying Don't power down. with the android logo! Any Advice?
Click to expand...
Click to collapse
The error codes I'm getting are
VBMETA: ERROR VERIFYING VBMETA IMAGE: OK_NOT_SIGNED (3)
CUSTOM VBMETA
VBNETA : NO SIGN INFO
VBNETA ,
It's all in red letters.
Thanks for any advice!
Hallo @ all. I hope your can help me with a Problem.
I bought last week from Amzon a Samsung Galaxy Tab S6 Lite P610.
I do not can Setup this Tablet why the WiFi Switch turn off by selfe. It is so fast that I am not able to put in the WiFi password. So I set up the Tablet with cable connection between the Tab and my Galaxy note 10 +. Only my accounts are not copied why for that it needed WiFi.
I searched for this Problem on Google and it seems a lot of People has this Problem after the Update to Android 11 but nowhere is a Way to solve this Bug. Also Bluetooth crashes with the Message App will be end.
So I thought it is a Problem with the OTA and when not all People has the Problem than I will flash the Rom new through Odin.
So I loaded Frija (SamFirm are not able to download a Rom). I typed in SM-P610 and csc is DBT.
It loaded the Rom.
In the zip are no CP File but I never flashed a Tab so maybe it is ok.
I restarted the Tab in the download Mode.
In Odin I set up BL, AP, and in CSC I set CSS Tar not Home CSC.
Than I started the Flash Process.
Odin still Flash and hung on download File (system.img).
On the Tab comes the Message:
FRP Lock
FRP Lock Pit File ignored Download.
On the Tab are no changes. I can still reboot in system. So I google and thought ok I reset the Tab. So I did it and repeated the Prozedure but the same Problem, FRP block the flash of the Firmware. Samsung can not help. The customer service only says do a reset. The Android 12 Update comes in May 22. But without Internet the Tab is useless.
Anybody maybe has a Idea?
I do not has make changes. I do not turn on USB debugging, do not activate OEM Unlock and do not activated the Developer Option.
wulfgardodin said:
Hallo @ all. I hope your can help me with a Problem.
I bought last week from Amzon a Samsung Galaxy Tab S6 Lite P610.
I do not can Setup this Tablet why the WiFi Switch turn off by selfe. It is so fast that I am not able to put in the WiFi password. So I set up the Tablet with cable connection between the Tab and my Galaxy note 10 +. Only my accounts are not copied why for that it needed WiFi.
I searched for this Problem on Google and it seems a lot of People has this Problem after the Update to Android 11 but nowhere is a Way to solve this Bug. Also Bluetooth crashes with the Message App will be end.
So I thought it is a Problem with the OTA and when not all People has the Problem than I will flash the Rom new through Odin.
So I loaded Frija (SamFirm are not able to download a Rom). I typed in SM-P610 and csc is DBT.
It loaded the Rom.
In the zip are no CP File but I never flashed a Tab so maybe it is ok.
I restarted the Tab in the download Mode.
In Odin I set up BL, AP, and in CSC I set CSS Tar not Home CSC.
Than I started the Flash Process.
Odin still Flash and hung on download File (system.img).
On the Tab comes the Message:
FRP Lock
FRP Lock Pit File ignored Download.
On the Tab are no changes. I can still reboot in system. So I google and thought ok I reset the Tab. So I did it and repeated the Prozedure but the same Problem, FRP block the flash of the Firmware. Samsung can not help. The customer service only says do a reset. The Android 12 Update comes in May 22. But without Internet the Tab is useless.
Anybody maybe has a Idea?
I do not has make changes. I do not turn on USB debugging, do not activate OEM Unlock and do not activated the Developer Option.
Click to expand...
Click to collapse
There is no CP because it is a tablet and not a phone. The CP is for the phone modem. You must enable Dev Options and OEM unlock to flash anything. Even stock. But before I'd try flashing a new ROM, I'd factory reset the tablet via recovery to see if that would fix the wifi and bluetooth problems.
Ok. I have solved the Problem. My Odin Version was to old. I User Odin 3.7.x
But to new flash the Rom solved not the Problem. Wifi still turns off by selfe. I send the Tqb back to Amazon. Friday I get a new one not from Amazon Warehous. Still lower Space, the 64 GB Variant. I hope it has still Android 10. When it has Android 10 and WiFi works, I do not update for the Moment.

SM-G950W Update Problems

I have a Samsung Galaxy SM-G950W device and I have been trying to update it since 2018 but no luck. It’s still running Android 8. And the patch update from 2018.
It won’t let me update within the settings, and have tried to flash the firmware multiple times, but I always get the Device Info error (with multiple different files)
Does anyone know maybe what I am doing wrong or what I can do to update the device to a newer version (9.0)
Try to download firmware from https://samfw.com/firmware/SM-G950W and flash with odin
hernanquiroz1999 said:
Try to download firmware from https://samfw.com/firmware/SM-G950W and flash with odin
Click to expand...
Click to collapse
I have tried but it fails each time
you must download one that is superior to binary 5 you have 4. it may be that
What I had to do Was Turn On USB Debugging because it turned of, then put the PIT file in which I got from the CSC extract, run it with the new BT and the PIT file and then do the whole package and it worked

Categories

Resources