Hello all, I have looked everywhere and no one seems to be having the same problem as I have here.
So here is the problem: My note 4 keeps going into recovery and is giving me a few messages.
1) In the stock Android recovery that it boots into, on the bottom it displays "dm-verity verification failed..."
2) When clicking on "apply update from external storage", it gives me "Update from external storage is disabled"
Background:
In a previous post, I was trying to install Xposed framework and had an issue where it would not install. A friendly user suggested I install a different APK and flash a zip file through TWRP. I then installed TWRP through a play store app and booted into it. I installed the zip file, wiped data (including Dalvik) and the problem started.
So I tried flashing original N910T Rom through Odin and this is the log I got
BTW I am still able to access TWRP through holding Volume Up:Homeower but when phone boots up it goes into Android Recovery mode automatically, no bootloop. I tried clearing Data but that didnt help. Should I clear "System" through TWRP and reflash?
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910TUVU1ANIH_N910TTMB1ANIH_N910TUVU1ANIH_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1005)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Superdudekk said:
So I tried flashing original N910T Rom through Odin and this is the log I got
BTW I am still able to access TWRP through holding Volume Up:Homeower but when phone boots up it goes into Android Recovery mode automatically, no bootloop. I tried clearing Data but that didnt help. Should I clear "System" through TWRP and reflash?
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N910TUVU1ANIH_N910TTMB1ANIH_N910TUVU1ANIH_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1005)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
you may need this
http://forum.xda-developers.com/not...f-g-c-t-w8-t3282641/post64569392#post64569392
Unfortunately I tried that but I found a solution! A helpful youtube video showed that with these new Samsung Phones, you can connect to Kie3 or Smart Switch and click "Emergency Software Recovery and Initialization", enter your model and serial number and the program will automatically wipe and flash OEM Samsung ROM onto the phone. Only bad thing is that you have to re-root the phone. Great solution for soft bricks.
Related
Issues began when I installed Lollipop on rooted phone. When flashing a custom rom it will not boot up. I cannot get to a recovery screen but can put it in download mode (Odin). I have downloaded the stock ATT rom and attempted to flash with odin but it fails everytime. I get the following on the screen.
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1100)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1
I have updated the samsung drivers and do not know where to go from here. any help is appreciated.
Gdogius
everytime i flash a custom recovery all i get is the same samsung stock recovery (note 5 sm-n920c)
and i don't know why , and by the way when i flash the custom recovery odin tells that everything is completed without of errors !! , but still getting the stock recovery !
here is what appears in odin when i flash it
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
please help guys :crying:
abodi40400 said:
everytime i flash a custom recovery all i get is the same samsung stock recovery (note 5 sm-n920c)
and i don't know why , and by the way when i flash the custom recovery odin tells that everything is completed without of errors !! , but still getting the stock recovery !
here is what appears in odin when i flash it
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Removed!!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
please help guys :crying:
Click to expand...
Click to collapse
Did you enable OEM UNLOCK under developer options ?
abodi40400 said:
everytime i flash a custom recovery all i get is the same samsung stock recovery (note 5 sm-n920c)
and i don't know why , and by the way when i flash the custom recovery odin tells that everything is completed without of errors !!
Click to expand...
Click to collapse
Flash the recovery with Auto Reboot unchecked.
I was having issues with the WiFi on my phone so I made backups to the SD card, removed it and did a factory reset on the phone. I'm not sure what it was running at the time, but not lolipop. It now boots to AT&T logo and heats up until I pull the battery out (I've waited upwards of 30 mins). I tried flashing stock and 0F3 roms with odin and I get the error:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G870AUCU1ANE4_G870AATT1ANE4_G870AUCU1ANE4_HOME.tar .md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And on the phone it says "SW REV CHECK FAIL : [aboot]Fused 2 > Binary 1"
I've tried flashing with PIT, tried flashing the boot loader, G870AUCU1ANE4_Full_Odin, and G870A_OC5_Bootloader, to no avail. I also downloaded Samsung Kies 3 and tried to do Firmware upgrade and initialization, which also didn't work. It comes up to Firmeware emergency recovery and asks for a recovery code (which I don't have). I've also tried from recovery mode to factory data reset and also tried to flash the roms from external SD. Is there anything else I can try or something I am missing that can get this working? Any help would be greatly appreciated.
I have the SM-G920T S6 and I recently tried to install twrp and root using this guide: http://forum.xda-developers.com/tmo...l/how-to-flash-marshmallow-update-sm-t3362983. I have always used a nexus device so I am not familiar with odin, but I thought I had it figured out. In odin it says the recovery flash was successful and gave me a PASS message. Once I tried rebooting to recovery it was still the stock recovery and no twrp. I have gone back over the instructions, but I still get the same results. I have checked and my system is now marked as custom but Knox is not tripped. Any help would be appreciated.
You are really close. I had similar trouble flashing twrp o. My G920T. I got it to work flash with Odin using twrp by idlekernel. Here is the link download the version to flash with odin under AP or PDA.
I hope this helps.
RedZaton said:
You are really close. I had similar trouble flashing twrp o. My G920T. I got it to work flash with Odin using twrp by idlekernel. Here is the link download the version to flash with odin under AP or PDA.
I hope this helps.
Click to expand...
Click to collapse
Thank you. Which of those md5 files should I download?
I installed "twrp-3.0.2-2-zeroflte.tar.md5" via Odin.
RedZaton said:
I installed "twrp-3.0.2-2-zeroflte.tar.md5" via Odin.
Click to expand...
Click to collapse
I tried it again and it still does not do anything. I unchecked auto reboot and noticed that it still had the download bar up like it did not finish but even after 15 min the bar stayed.
Odin says this when I flash the image:
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
trixter29 said:
I tried it again and it still does not do anything. I unchecked auto reboot and noticed that it still had the download bar up like it did not finish but even after 15 min the bar stayed.
Odin says this when I flash the image:
<OSM> Enter CS for MD5..
<OSM> Binary Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
Make sure auto reboot is unchecked in Odin, flash Twrp and boot directly into it after flash. It should work just fine with MM.
I was using an app to disable the Android APK Signature verification to install the Youtube Vanced APK. Phone rebooted and suddenly I no longer had a system partition. I've tried going through ODIN and flashing the CSC, HOME_CSC, AP, PIT, etc., and in most cases it simply hangs when it tries to write to a partition, then tells me "Complete(Write) operation failed.", I've also tried toggling the Re-Partition option in the Options tab of Odin, but that doesn't help either.
I want to try to do a nand erase, as nothing else seems to working, but I don't know the consequences of that. I can currently still boot into TWRP, as no flashing attempts in Odin were successful, and I've already backed up everything other than the System and System Image options to an SD card. If I do a nand erase, what should I do after?, should I just flash everything normally with that option checked? I'll also post a log from a failed Odin flash if that helps at all.
Code:
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 808 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> param.bin
<ID:0/003> up_param.bin
<ID:0/003> cm.bin
<ID:0/003> keystorage.bin
<ID:0/003> recovery.img
<ID:0/003> modem.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> modem_debug.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> cache.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Daniel41550 said:
I was using an app to disable the Android APK Signature verification to install the Youtube Vanced APK. Phone rebooted and suddenly I no longer had a system partition. I've tried going through ODIN and flashing the CSC, HOME_CSC, AP, PIT, etc., and in most cases it simply hangs when it tries to write to a partition, then tells me "Complete(Write) operation failed.", I've also tried toggling the Re-Partition option in the Options tab of Odin, but that doesn't help either.
I want to try to do a nand erase, as nothing else seems to working, but I don't know the consequences of that. I can currently still boot into TWRP, as no flashing attempts in Odin were successful, and I've already backed up everything other than the System and System Image options to an SD card. If I do a nand erase, what should I do after?, should I just flash everything normally with that option checked? I'll also post a log from a failed Odin flash if that helps at all.
Code:
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 808 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> sboot.bin
<ID:0/003> param.bin
<ID:0/003> up_param.bin
<ID:0/003> cm.bin
<ID:0/003> keystorage.bin
<ID:0/003> recovery.img
<ID:0/003> modem.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> modem_debug.bin
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> cache.img
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
"Total Binary size: 808 M"
You aren't flashing all the required files in odin. Total binary size should be between 4000 and 6000 M (Mb).
Frick_trump said:
"Total Binary size: 808 M"
You aren't flashing all the required files in odin. Total binary size should be between 4000 and 6000 M (Mb).
Click to expand...
Click to collapse
Yup, I was skipping out on the AP file since I didn't want to flash the system yet, only recovery because the real system ap wouldn't flash in another attempt.
For anyone reading in the future, I had to do a nand erase and reflash the latest version of the the system software (all files). An older version wouldn't work, then had to reset a few times to be able to toggle the OEM Unlock option.