Hi,
Recently my galaxy note was in repair at samsung. After I took it with everything wiped out and android 5.1.1, I rooted and installed twrp. I was able to install an aosp rom via recovery (the unofficial cm-13).
Now I cant flash anything via Odin without getting "sw rev check fail fused 2 binary 1" and every stock rom I flash via twrp give me bootloop.
ticiano_arraes said:
Hi,
Recently my galaxy note was in repair at samsung. After I took it with everything wiped out and android 5.1.1, I rooted and installed twrp. I was able to install an aosp rom via recovery (the unofficial cm-13).
Now I cant flash anything via Odin without getting "sw rev check fail fused 2 binary 1" and every stock rom I flash via twrp give me bootloop.
Click to expand...
Click to collapse
how did you solve yhis i have the same problem
ahmd gomaa said:
how did you solve yhis i have the same problem
Click to expand...
Click to collapse
It's not possible.
ticiano_arraes said:
Hi,
Recently my galaxy note was in repair at samsung. After I took it with everything wiped out and android 5.1.1, I rooted and installed twrp. I was able to install an aosp rom via recovery (the unofficial cm-13).
Now I cant flash anything via Odin without getting "sw rev check fail fused 2 binary 1" and every stock rom I flash via twrp give me bootloop.
Click to expand...
Click to collapse
Just flash it again but use different usb ports. It is the usb ports problems.
ticiano_arraes said:
Hi,
Recently my galaxy note was in repair at samsung. After I took it with everything wiped out and android 5.1.1, I rooted and installed twrp. I was able to install an aosp rom via recovery (the unofficial cm-13).
Now I cant flash anything via Odin without getting "sw rev check fail fused 2 binary 1" and every stock rom I flash via twrp give me bootloop.
Click to expand...
Click to collapse
And when it bootloops boot into stock recovery and do a factory reset. That will clear all the crap out from CM-13.
Related
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
Hi,
I encountered error during flashing of XXUGNG4 official firmware using odin 3.09. It did not completed successfully. I have tried to change usb port but still got the same error. I managed to flash the custom recovery and restore my previous rom backup but got a warning 'kernel is not seandroid enforcing' and when my phone boot my camera and sound (volume,etc) is not working.
Question: Can I flashed XXUGNG4 official firmware even if my custom rom is XXUGNG8? I really need to go back to stock official firmware in order to fix the problems I encountering on camera and sound
Really need your help...
Thanks
kraven0731 said:
Hi,
I encountered error during flashing of XXUGNG4 official firmware using odin 3.09. It did not completed successfully. I have tried to change usb port but still got the same error. I managed to flash the custom recovery and restore my previous rom backup but got a warning 'kernel is not seandroid enforcing' and when my phone boot my camera and sound (volume,etc) is not working.
Question: Can I flashed XXUGNG4 official firmware even if my custom rom is XXUGNG8? I really need to go back to stock official firmware in order to fix the problems I encountering on camera and sound
Really need your help...
Thanks
Click to expand...
Click to collapse
Hi,
You cannot flash an older version of your firmware without encountering problems.
You need to flash XXUGNG8 or later.
Look here:
http://forum.xda-developers.com/showthread.php?t=2265477
Don't forget to wipe data and cache before and after flashing the firmware
malybru said:
Hi,
You cannot flash an older version of your firmware without encountering problems.
You need to flash XXUGNG8 or later.
Look here:
http://forum.xda-developers.com/showthread.php?t=2265477
Don't forget to wipe data and cache before and after flashing the firmware
Click to expand...
Click to collapse
I will try to download the XXUGNG8 firmware and hopefully it will fixed my problems and back to official firmware.
Okay, So I was trying to flash stock rom (4.4.2) in Odin and It failed. IT left me with the error, SW REV CHECK FAIL : [aboot]Fused 4 > Binary 1
I get this error every time I try to flash. And I tried to do an Emergency Software Recovery and it just fails after it downloads the Update. I am able to access Android Recovery and Download Mode Aswell. I think when I tried to factory reset I deleted The whole OS. I really hope I am not out a brand new phone. I already tried to flash like 3 different stock roms from different websites same error!
Phone was Not rooted.
No Custom Rom installed.
Android 5.1.1 Was installed before.
Also, I heard that some users have been able to flash the pit and fix this, How can I find my Pit File. Samsung Galaxy S5 SM-G900A
2 days ago i flashed twrp on my pure stock note 4, i did backup my rom including EFS using twrp and then flash kyubi rom with nameless kernel, it all went well. just now i wipe data ,system, cache on twrp and restore my backup stock rom and it went well too...and then i try to flash stock rom using odin so i can get back the stock recovery mode for OTA update when MM releases.. the flashing was a sucess and phone booted but my data inside werent wipe.
so i went to recovery mode and saw this dm-verity verification failed on the bottom i proceed to wipe data and reboot my phone, its all working now no problems except i cant reset my phone with the setting inside it will just bring me to recovey mode and stay there with that message.
now i did some research, some saying will bootloop and stuffs but mine is all ok no problem except i cant reset it inside the settings..
anyone can help me get rid of that message/problem?
If you format everything in advance format in twrp and then flash stock firmware this message will go away.
got the same problem. Then I went to a local store. They helped me. Here are steps
1. Pull out your battery, check your serial number (S/N:....)
2. Download smart switch, enter emergency software recovery..... Enter your serial number
3. Turn off your phone. Enter download mode or sth ( I don't remember it clearly. just power + vol down or up. just try it)
4. Smart switch will recognize your phone. Choose a firmware to download. then wait
5. Enjoy stock firmware
Use kies3 reinstall drivers, then use emergency recovery in kies to reinstall your current firmware or opt to update to latest or most recent release or version then follow kies instructions
rooted s5 smg900r4
Hello everyone
I have found a way to fix dm-verity and DRK issues and it works like official, meaning no errors in stock recovery and OTA works with Official firmware, the problem is related to corrupted/deleted 3 files on /efs partition. I have tested it on SM-N910C so I guess it works on other Exynos variants, perhaps even on snapdragon if the partition layout is similar? Kies won't restore DRK or dm-verity check because it doesn't write to EFS. I can fix yours if someone is interested via Team Viewer, you will need the following:
1. PM contact me for Skype ID
2. Stock rom, rooted (any root method)
3. Adb debugging enabled and drivers installed (Kies or SmartSwitch)
After repair you can enter your stock recovery and confirm there is no DRK/dm-verity red letters error.
Regards,
magix01
please guide us the proceedure here .. i have a phone with same problem & i have to update it to MM ...
dork997 said:
If you format everything in advance format in twrp and then flash stock firmware this message will go away.
Click to expand...
Click to collapse
Mine still says fail. but it also says "need to check drk first" could anyone possibly help me im stuck.the phone loads up and everything. but when i try to root or anything or flash any other firmware than n910pvpu5dqi5 it fails about 4 seconds in to flashing on odin. ive downloaded every possible firmware specific to the SM-N910P but only one worked.
im a big noob with the note 4 this is my first luckily its not my daily phone yet. im very familiar with the note 3 n900t but im finding they are very different. any advice would be appreciated!
Sir, please reply
When i unlocked my bootloader on my redmi phone this warning comes, but after clicking power button it will successfully boot to system but i m confused did i flash any rom in it, is it safe or not
Manish_k said:
Sir, please reply
When i unlocked my bootloader on my redmi phone this warning comes, but after clicking power button it will successfully boot to system but i m confused did i flash any rom in it, is it safe or not
Click to expand...
Click to collapse
If you just unlocked your bootloader and thats it, your rom should still be the stock one.
I am new to flashing and custom roms but i have had lineage OS installed for awhile on my old galaxy note 3 SM-N900W8. When i went to OTA update lineage it caused my note 3 to go into a recovery Bootloop. I could not actually boot into recovery or boot system it kept restarting. So i read some forums and watched some videos. It kept saying seandoid not enforcing. I went and got a original note 3 md5 file and put it into odin put my old phone into download mode and connected it to Odin Loaded the md5 file in to the AP section of odin and hit start. Now it says firmware upgrade encountered please select recovery mode in kies. Also at the top left it says
Current Binary: Samsung Official
System Status: Custom
Does anyone know how i could fix this or if i could reinstall a custom binary or kernel from lineage.
I would like to just get my old pictures off the phone. Or would i have to connect to kies and install original firmware and just re flash a new rom?
If i brick the phone i brick it i use a S7 now. I don't know if this makes sense but i might need some help.
Try flashing TWRP again.