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.
Related
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> Enter CS for MD5..
<ID:0/006> Check MD5.. Do not unplug the cable..
<ID:0/006> Please wait..
<ID:0/006> Checking MD5 finished Sucessfully..
<ID:0/006> Leave CS..
<ID:0/006> SetupConnection..
how long does it stay like this for?
What will i do if it doesnt do anything ?
ok think ive done it . hopefully it doesnt get stuck at factoryfs.rfs . all i did was go on process kill kiestrayagent. then i did download mode while the phone was off. not turn the phone on then do download mode as i did. just a care for any1 else . thanks
that should fix it.... never use odin if kies is running thats probably what caused your problem
marcon10 said:
ok think ive done it . hopefully it doesnt get stuck at factoryfs.rfs . all i did was go on process kill kiestrayagent. then i did download mode while the phone was off. not turn the phone on then do download mode as i did. just a care for any1 else . thanks
Click to expand...
Click to collapse
My last odin flash failed on the factory.rfs don't know why ive flashed the phone many times before with odin never had any problems. So i Removed the battery and re flashed with re-partition 512.pit. Working again
Well that was my first flash to darkys 9.2 resurrection and went well. Just learning to configure battery. Just reading on darkys 9.3 .
Sent from my GT-I9000 using XDA App
Hi,
Im stuck at SetupConnection....
smartin said:
Hi,
Im stuck at SetupConnection....
Click to expand...
Click to collapse
Did you close all Kies processes in task manager? If not do so and you should be able to flash now
Odin Problems or im doing Crap? Please Help
<ID:0/006> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> T999UVDMD5_T999TMBDMD5_T999UVDMD5_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> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<ID:0/006> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
Dear all,
I found a new firmware on sammobile site and thought to upgrade my Galaxy note from:
N7000JPLPD_N7000OJPLP7_N7000XXLPT_HOME.tar.md5
to:
N7000JPLR8_N7000OJPLR8_N7000XXLRK_HOME.tar.md5
(Both of them for Pakistan)
First I used Odin 1.83 to flash but after about 20% the Odin turned red indicating 'Fail'
Then I searched the web and (I know it's my fault) somewhere downloaded Odin 1.85, checked all the fields on Odin, like "Re Partition- Autoboot-F reset time"
I check them all and then another mistake.... used the same MD5 file in all 3 'PDA, PHONE, CSC" and flashed again.
And also used the PIT file which was in the Odin 1.85's folder.
Now I can enter the download mode but if I try to flash the new ROM, it goes upto 20% and says something like this:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000JPLR8_N7000OJPLR8_N7000XXLRK_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> hidden.img
<ID:0/009> NAND Write Start!!
<ID:0/009> factoryfs.img
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And If I flash the older ROM it says like:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000JPLPD_N7000OJPLP7_N7000XXLPT_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> cache.img
<ID:0/008> NAND Write Start!!
<ID:0/008> factoryfs.img
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please help
sulemani1 said:
Dear all,
I found a new firmware on sammobile site and thought to upgrade my Galaxy note from:
N7000JPLPD_N7000OJPLP7_N7000XXLPT_HOME.tar.md5
to:
N7000JPLR8_N7000OJPLR8_N7000XXLRK_HOME.tar.md5
(Both of them for Pakistan)
First I used Odin 1.83 to flash but after about 20% the Odin turned red indicating 'Fail'
Then I searched the web and (I know it's my fault) somewhere downloaded Odin 1.85, checked all the fields on Odin, like "Re Partition- Autoboot-F reset time"
I check them all and then another mistake.... used the same MD5 file in all 3 'PDA, PHONE, CSC" and flashed again.
And also used the PIT file which was in the Odin 1.85's folder.
Now I can enter the download mode but if I try to flash the new ROM, it goes upto 20% and says something like this:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000JPLR8_N7000OJPLR8_N7000XXLRK_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> hidden.img
<ID:0/009> NAND Write Start!!
<ID:0/009> factoryfs.img
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
And If I flash the older ROM it says like:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> N7000JPLPD_N7000OJPLP7_N7000XXLPT_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> cache.img
<ID:0/008> NAND Write Start!!
<ID:0/008> factoryfs.img
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Please help
Click to expand...
Click to collapse
Hi friend just try flashing to GB and then to any other.
Use company cable for data transfer, try with another usb port and i hope it must get cleared.
Press THANKS if it helped you
Thank you my friend, but could you guide me where to find GB? And what GB actually is? The older 2.3.6 Ginger bread?
sulemani1 said:
Thank you my friend, but could you guide me where to find GB? And what GB actually is? The older 2.3.6 Ginger bread?
Click to expand...
Click to collapse
GB actually is the older 2.3.6 Ginger
you find GB in sammobile site
If it's failing at factory.fs then you could be in longer term trouble, let us know.
Sent from my GT-N7000 using xda premium
dude... try this,,
just pull out the battery. wait for 10 secs.. reinsert. go back to download mode.. use odin 1.85 and just select the tar.md5 fine in pda section.. donot check repartion.. dont use pit file.
PS: if odin is stuck once.. u cannot continue from there.. the phone needs a reboot for another try
I read somewhere saying that flashing pit file must be accompanied by bootloader or your device might brick.
Sent from my GT-N7000 using xda premium
nokiamodeln91 said:
dude... try this,,
just pull out the battery. wait for 10 secs.. reinsert. go back to download mode.. use odin 1.85 and just select the tar.md5 fine in pda section.. donot check repartion.. dont use pit file.
PS: if odin is stuck once.. u cannot continue from there.. the phone needs a reboot for another try
Click to expand...
Click to collapse
Thanks friend.
I did it. Im ok now.
Thanks to all of you who helped me here.
I've come across various other threads concerning this topic with other devices, but none are exactly like my issue.
I rooted originally with Odin and CF autoroot with no issues. Now me being the noob that I am, I un-rooted with Kies to check for any updates. The process went fine, however my device status still says "custom" and I'm unable to re-root using the same method that I did before. I get a "fail" in Odin after the cache.img process and have to remove the battery to reboot device.
Has anyone had this issue or am I the only idiot to unroot this beast of a phone?
Best bet. Odin back to stock and then reroot and forget about updates.
BAD ASS NOTE 4 + BAD ASS GEAR S
I just tried that. Downloaded the firmware from sammobile and used Odin to install it. Then proceeded to re-root using CF autoroot again. Same "fail" message.
my Odin is as follows:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-trltetmo-trltetmo-smn910t.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img.ext4
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
where's the issue?
I'd try a different version of Odin.
Razorfengraul said:
I just tried that. Downloaded the firmware from sammobile and used Odin to install it. Then proceeded to re-root using CF autoroot again. Same "fail" message.
my Odin is as follows:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-trltetmo-trltetmo-smn910t.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin v.3 engine (ID:3)..
<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> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> cache.img.ext4
<ID:0/003> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
where's the issue?
Click to expand...
Click to collapse
As said diff version or bad cf autoroot download. It can be many things. Try a fresh download of everything. Also when u Odin back to stock it went fine so it is something after. Bad download
BAD ASS NOTE 4 + BAD ASS GEAR S
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.
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.