Custom OS: Tried Reverting to Stock and Failed. - Verizon Samsung Galaxy S7 Questions & Answers

My phone was rooted but recently apps randonly started crashing so I decided to return to stock.
I used the following to try to return to stock.
https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
When it started downloading it threw an error:
fused 3 > binary 1
Odin threw a:
<Auth Failed>
I am unable to boot it up after "Update Failed Connect To Verizon Software Update to Fix". I don't believe it can even charge at this point.
I am still able to reach the area that is used to flash.
How do I fix?

The Firmwares in that thread are not up to date at all. The bootloader versions are behind what you are probably on right now. You need to download more recent firmware for your handset from updato. You cant roll back to a bootloader older then what you are already on.
The example from that thread for G930V is
G930VVRU2APE1
In this case the bootloader version it is trying to flash is underlined, being 2.
Most up to date firmware is:
G930VVRS4BRA1
With the 4 being the latest firmware. You can check what you are on now by going to settings about phone baseband version. You can flash separate basebands but typically they are flashed as one package together.

Related

[Q] Odin Flashing Problems with Note 3 and Kitkat

I have rooted my Samsung Note 3 with a custom rom running Jellybean 4.3 with clockwork mod recovery. I have tripped knox due to rooting it. When Kitkat came out March 17th 2014, I wanted to upgrade and go back to official firmware with Kitkat to try it out. Since I have rooted my phone to run viper4android audio kernel I am unable to do an official OTA or Kies update. That said I went about downloading the new Bell Canada Note 3 firmware 4.4.2. I was told to flash a Jellybean Bell Firmware first before flashing the Kitkat version to avoid boot loops or other problems. Trying to do so with Odin in download mode ended in failure just trying to flash jellybean stock. Didnt get that far really. It showed a fail in the Note 3 screen to this effect in read this message (sw rev check fail : sbl1 fused 2 binary 1) . Odin didnt load like I am usually use to seeing by unzipping the firmware into a folder and adding it to the PDA field. After I loaded the .tar file (md5) file into pda it checked it and then told me its finished successfully but the next line it said CS Fail. After hitting start it said fail instantly in the odin window and on the Note 3 I did see a bar showing me the progress of install for 1 second until odin told me of the fail. Now my Note is in download mode and can't get past this problem to get it running again! Please any help would be greatfull to getting me past this problem and onto Kitkat or even back to Jellybean. Any other questions you may have I will supply you the info.
Thanks
Nervous Android user!
weston109 said:
I have rooted my Samsung Note 3 with a custom rom running Jellybean 4.3 with clockwork mod recovery. I have tripped knox due to rooting it. When Kitkat came out March 17th 2014, I wanted to upgrade and go back to official firmware with Kitkat to try it out. Since I have rooted my phone to run viper4android audio kernel I am unable to do an official OTA or Kies update. That said I went about downloading the new Bell Canada Note 3 firmware 4.4.2. I was told to flash a Jellybean Bell Firmware first before flashing the Kitkat version to avoid boot loops or other problems. Trying to do so with Odin in download mode ended in failure just trying to flash jellybean stock. Didnt get that far really. It showed a fail in the Note 3 screen to this effect in read this message (sw rev check fail : sbl1 fused 2 binary 1) . Odin didnt load like I am usually use to seeing by unzipping the firmware into a folder and adding it to the PDA field. After I loaded the .tar file (md5) file into pda it checked it and then told me its finished successfully but the next line it said CS Fail. After hitting start it said fail instantly in the odin window and on the Note 3 I did see a bar showing me the progress of install for 1 second until odin told me of the fail. Now my Note is in download mode and can't get past this problem to get it running again! Please any help would be greatfull to getting me past this problem and onto Kitkat or even back to Jellybean. Any other questions you may have I will supply you the info.
Thanks
Nervous Android user!
Click to expand...
Click to collapse
you cant flash back to 4.3 when you on 4.4.2 and did you succeed when flashing 4.4.2?
Flashing
hhai2pth said:
you cant flash back to 4.3 when you on 4.4.2 and did you succeed when flashing 4.4.2?
Click to expand...
Click to collapse
I havent been able to do anything. I was on Jellybean 4.3.2 custom rom with a custom recovery and tried to flash it back to a stock version of Jellybean before the update to Kitkat. I didnt get that far to even try flashing Kitkat because flashing Jellybean Canadian stock rom was unsuccessful with the errors I mentioned in my earlier post. Now I am stuck in download mode and unable to flash using odin.
weston109 said:
I havent been able to do anything. I was on Jellybean 4.3.2 custom rom with a custom recovery and tried to flash it back to a stock version of Jellybean before the update to Kitkat. I didnt get that far to even try flashing Kitkat because flashing Jellybean Canadian stock rom was unsuccessful with the errors I mentioned in my earlier post. Now I am stuck in download mode and unable to flash using odin.
Click to expand...
Click to collapse
I think you can power if off by pressing the power button for a few seconds. And then flash a custom recovery, reboot and flash a Kit Kat custom rom via Odin or Custom recovery. Hope it helps.
weston109 said:
I havent been able to do anything. I was on Jellybean 4.3.2 custom rom with a custom recovery and tried to flash it back to a stock version of Jellybean before the update to Kitkat. I didnt get that far to even try flashing Kitkat because flashing Jellybean Canadian stock rom was unsuccessful with the errors I mentioned in my earlier post. Now I am stuck in download mode and unable to flash using odin.
Click to expand...
Click to collapse
Knox was tripped. You said it yourself. Go and read up on Knox.
The answer will be very clear afterwards. It's quite clear to me.
Also, don't take this the wrong way.... but you probably should not have done any of this my friend. Your skill level makes this obvious.
I suggest not getting a Samsung phone next time as Knox is hard to get around (it's possible, I was rooted on 4.3 and I am now on 4.4.2 stock flashed with Odin and Knox is still 0x0).
weston109 said:
I havent been able to do anything. I was on Jellybean 4.3.2 custom rom with a custom recovery and tried to flash it back to a stock version of Jellybean before the update to Kitkat. I didnt get that far to even try flashing Kitkat because flashing Jellybean Canadian stock rom was unsuccessful with the errors I mentioned in my earlier post. Now I am stuck in download mode and unable to flash using odin.
Click to expand...
Click to collapse
what's the CSC of your phone? you should try the one newer vesion of 4.3 cause if it's an older firmware it refused flash

Help: Unknown IMEI, IMEI SV, baseband version. N-9005 LTE

I have decided to root my N9005 2 days ago. So this is what i've done:
I was on version 5.0, I downgraded it to 4.4
i flashed Stock official ROM with a version of 4.4 using odin.
After that, my phone stop at Samsung logo. I then removed the battery and hold volume -, home, and power button.
I Flashed the CF-root. I tripped my knox 0x1 and i don't care since my warranty is due. Then i flash a recovery soon after i flashed a custom ROM.
After so, i checked my "about device => Status"
I found unknown IMEI and unknown IMEI SV", also i notice that i have unknown baseband version.
I then power off my phone, boot into recovery, and wipe cache partition and did full wipe.
I reboot to "Download" (The recovery ask me to install root, i chose "no")
Then i flash again the 4.4 official version.
Waited till it boot. After boot was completed, i immediately Checked my IMEI, and found out, it was still unknown.
My question is How to get back my IMEI, IMEI SV, Baseband version?
Thank you!
whymewho007 said:
I have decided to root my N9005 2 days ago. So this is what i've done:
I was on version 5.0, I downgraded it to 4.2
i flashed Stock official ROM with a version of 4.2 using odin.
After that, my phone stop at Samsung logo. I then removed the battery and hold volume -, home, and power button.
I Flashed the CF-root. I tripped my knox 0x1 and i don't care since my warranty is due. Then i flash a recovery soon after i flashed a custom ROM.
After so, i checked my "about device => Status"
I found unknown IMEI and unknown IMEI SV", also i notice that i have unknown baseband version.
I then power off my phone, boot into recovery, and wipe cache partition and did full wipe.
I reboot to "Download" (The recovery ask me to install root, i chose "no")
Then i flash again the 4.2 official version.
Waited till it boot. After boot was completed, i immediately Checked my IMEI, and found out, it was still unknown.
My question is How to get back my IMEI, IMEI SV, Baseband version?
Thank you!
Click to expand...
Click to collapse
1. Why you downgraded your device to root it?
2. Why you didn't create a backup of your IMEI before make a downgrade that is risky for your device?
3. Flash the latest stock ROM via ODIN with .PIT file and clicking the Re-partition box. This method doesn't work maybe, but you don't have so much choices. Try it and if works, you will recover your real IMEI. You will have a beaty paperweight if not.
Joku1981 said:
1. Why you downgraded your device to root it?
2. Why you didn't create a backup of your IMEI before make a downgrade that is risky for your device?
3. Flash the latest stock ROM via ODIN with .PIT file and clicking the Re-partition box. This method doesn't work maybe, but you don't have so much choices. Try it and if works, you will recover your real IMEI. You will have a beaty paperweight if not.
Click to expand...
Click to collapse
i downgraded because i can't see note 3 being rooted on version 5.0, therefore i follow this guide:
http://forum.xda-developers.com/galaxy-note-3/development/root-guide-note-3-lte-sm-n9005-lollipop-t3093183
I follow the part 1 procedure and yes i was able to downgrade from 5.0 - 4.4 version.
After im done with the downgrade, i checked this CF-auto-root guide: http://forum.xda-developers.com/showthread.php?t=2466423
I notice in the download area this "
SM-N9005 (International Qualcomm): CF-Auto-Root-hlte-hltexx-smn9005.zip
(only works on 4.4 bootloaders, if you're still on 4.3 use the old version which you can find here: http://d-h.st/J32)
Also the reason why i downgraded my version.
I was not able to back up my IMEI since i don't know that it will be wipe out after installing custom rom. I was not able to find a guide that i should back up my IMEI before flashing custom roms. Also i anticipate
that it would not be wipe out. Like on HTC Sensation, flashing custom roms does not give unknown IMEI, if ever it happens, i have no idea since i was not able to experience it on my part rooting a Sensation.
I already fix my IMEI number.
-I am here in Philippines, so what i'ved downloaded was Philippine Official Firmware ROM 4.4. Then i realize that my phone came from Singapore, Therefore i downloaded a Singapore Official Firmware ROM 4.4.
-I go into recovery, wipe cache, format and full wipe.
-I was going to boot on download mode. Whenever exiting the recovery coming from full wipe, it tells me that "NO ROOT" was found, Install SU or NO. I chose "NO".
-Then im on download mode, i use ODIN, Flash my Singapore Official Firmware ROM.
-After 5-10 minutes, my Note boot up, and noticed i already have signal bar, IMEI, IMEI SV and baseband.
I will now back up my IMEI number.

com.sec.edpg error..what is it.

hi all,
i decided to unroot my device and flashed stock firmware through odin, now when the phone restarts i get this error and the touch is unresponsive i am not able to enter app drawer and the it takes repeated attempts to get into power off menu.
what has happened did i miss some imp step, was i suppose to uncock bootlaader under usb debugging etc etc. i tried flashin fw without BL file still same error.
this was an ebay purchase UK unocked model, which i believed was flashed with indian nougat firmware which i again reflashed to G935FXXU1DPLT, OTA updated to G935FXXU1DQB3 prior to rooting.
not able to boot into recovery also
currently iam flashing G935FXXU1DPLT or am i supposed to flash G935FXXU1DQB3

SM-T580 Unable to flash MM version OS after 7.0 OTA update

Hi there,
My tablet got updated to 7.0 Nougat here the other day. Now a few functions I needed in 6.0.1 is no longer working in Nougat.
So I of course I downloaded stock rom, odin, and added the files to their corresponding selections, and as I hit Start, it reads the file, and as it goes on to flash system or data, it just fails right out of the blue. This is early start even before its flashed anything it seems.
The error code showing on the tablet is: "system rev. check fail device:1 Binary:0"
FRP lock is OFF aswell. Tried flashing it over a custom ROM aswell, but same error persists. It actually started asking for PIT file all of sudden. But even with that handled, it still gave fail on same place. Tried 3 different OS versions of 6.0.1 for my tablet.
Any idea how to bypass this version check? It's like the tablet has added some data into its motherboard saying its on 7.0 and nothing below is allowed except custom. Is there any way to flash the downloaded stock ROM to be flashed in Odin, in TWRP?
Also just using a custom ROM isnt an option due to safetynet is a part of some of the functions I require.
EDIT:
Just after typing this, I managed to use V5 of Ultra Lean ROM for T580, did full unroot of SuperSU after a full boot, and said yes to attempt Stock Boot Image, and No on Stock Recovery. Now safetynet gave validated status

Downgrade firmware from July to April

Hi, I have a S8 that is currently flashed with firmware version G950FXXU3CRGB (July). For research purposes I would like to flash this firmware back to G950FXXU1CRD7 (April). Is this possible? Odin keeps giving failed messaged on either sboot.img or boot.img. I tried building a new AP package which only includes system.img, but this one also fails...
Is it at all possible, or is the bootloader/Download-mode preventing me from downgrading?
thereof said:
Hi, I have a S8 that is currently flashed with firmware version G950FXXU3CRGB (July). For research purposes I would like to flash this firmware back to G950FXXU1CRD7 (April). Is this possible? Odin keeps giving failed messaged on either sboot.img or boot.img. I tried building a new AP package which only includes system.img, but this one also fails...
Is it at all possible, or is the bootloader/Download-mode preventing me from downgrading?
Click to expand...
Click to collapse
You cannot downgrade firmware with a lower bootloader version than what is installed on your phone ie: your current bl is ver 3 and your trying to flash bl ver 1
spawnlives said:
You cannot downgrade firmware with a lower bootloader version than what is installed on your phone ie: your current bl is ver 3 and your trying to flash bl ver 1
Click to expand...
Click to collapse
That's what I expected... I'm guessing this also goes for the system image itself? I don't really care about the bootloader, but I would like the system image to be as close as possible to that of April (especially `init`, `vold`, `blkid` and `zygote`). Otherwise I'm just going to search for a non-updated second hand phone.
thereof said:
That's what I expected... I'm guessing this also goes for the system image itself? I don't really care about the bootloader, but I would like the system image to be as close as possible to that of April (especially `init`, `vold`, `blkid` and `zygote`). Otherwise I'm just going to search for a non-updated second hand phone.
Click to expand...
Click to collapse
This is one of the many reasons why I'm still on nougat ( ver 1 bl )- the inability to downgrade. I would also say going the other way holds true too upgrading the firmware without the upgrading the bootloader version would also cause issues.
I've also heard that doing a complete nandroid backup then upgrading then trying to restore does not work either.

Categories

Resources