Database Users

[Q] How to root after the latest update ?

Hi all,
I've just updated my Note3 SM-N9005 via kies to Build number N9005XXUDMK2 and now I can't flash root, It fails every time...
My version is N9005XXUDMJ7 and my build number is N9005XXUDMK2.
I don't know if it has something to do with it, but when I enter download node I see a gray line saying: "Write protection: Enabled".
Can anyone please tell me how can I gain root access again ?
I'm tring to flash this file: "CF-Auto-Root-hlte-hltexx-smn9005.tar.md5" with "Odin3 v3.09.exe"
which I found in this site: http://true-android.blogspot.co.il/2013/12/root-n9005xxudmk2-galaxy-note-3-sm.html

frliran said:
Hi all,
I've just updated my Note3 SM-N9005 via kies to Build number N9005XXUDMK2 and now I can't flash root, It fails every time...
My version is N9005XXUDMJ7 and my build number is N9005XXUDMK2.
I don't know if it has something to do with it, but when I enter download node I see a gray line saying: "Write protection: Enabled".
Can anyone please tell me how can I gain root access again ?
I'm tring to flash this file: "CF-Auto-Root-hlte-hltexx-smn9005.tar.md5" with "Odin3 v3.09.exe"
which I found in this site: http://true-android.blogspot.co.il/2013/12/root-n9005xxudmk2-galaxy-note-3-sm.html
Click to expand...
Click to collapse
Can you paste the Odin log after it fails?
Also you may have the new updated CF Root which has been adapted for KitKat and doesn't work with 4.3 anymore.

Here is the log from odin
radicalisto said:
Can you paste the Odin log after it fails?
Also you may have the new updated CF Root which has been adapted for KitKat and doesn't work with 4.3 anymore.
Click to expand...
Click to collapse
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-hlte-hltexx-smn9005.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I even tries using the same root file I did the first time I rooted my phone...

frliran said:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-hlte-hltexx-smn9005.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I even tries using the same root file I did the first time I rooted my phone...
Click to expand...
Click to collapse
Gave the same error using the original file you used from the first time? -- It is possible it doesn't like MK2, however it should work because I used it fine when I was on it.. Try re-downloading it again and trying again (I don't have it anymore, only the KK version )

Here is the log of the first file
radicalisto said:
Gave the same error using the original file you used from the first time? -- It is possible it doesn't like MK2, however it should work because I used it fine when I was on it.. Try re-downloading it again and trying again (I don't have it anymore, only the KK version )
Click to expand...
Click to collapse
The previous log was from the new file I downloaded today.
This is the log from "Odin3 v3.07" using the first file I rooted my phone with:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-hlte-hltexx-smn9005.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
PLEASE...Can you please help me to re-root my phone.
(And if you can, please send me a link to download root for the KitKat version so that I can re-root it when the update will rollout in my country.)

Just to double check -- you are flashing it via the PDA option correct? and you have unrar'd it so you can see the tar.md5 file ?

yes
radicalisto said:
Just to double check -- you are flashing it via the PDA option correct? and you have unrar'd it so you can see the tar.md5 file ?
Click to expand...
Click to collapse
Yes I am.
But in odin 3.9 there is AP and not PDA.
But I tried both in both odin versions: 3.7 and 3.9.
In odin 3.7 I am using PDA, and in odin 3.9 I am using AP.

Hmm I am stumped I'm afraid. Usually re-flashing it normally works. See if anyone else will chime in and know the answer.

)-;
radicalisto said:
Hmm I am stumped I'm afraid. Usually re-flashing it normally works. See if anyone else will chime in and know the answer.
Click to expand...
Click to collapse
Do you think doing "Wipe cache partition" can fix it ? I don't realy knkow what it means...
Can you please send me a download link for rooting after updating to KitKat ? So I could use it when the update rolls out in my country

frliran said:
Do you think doing "Wipe cache partition" can fix it ? I don't realy knkow what it means...
Can you please send me a download link for rooting after updating to KitKat ? So I could use it when the update rolls out in my country
Click to expand...
Click to collapse
When it rolls out it may be a different version of KK than is currently compatible with CR Root. Better waiting til it comes out then seeing what is available.
**[Side Note... If you want KK now you can flash the Official XEO version depending on your Model (IF Hong Kong then it won't work) - and you can root on that without issue after flashing, but you cannot go bac to 4.3 again]**

hmmm
radicalisto said:
When it rolls out it may be a different version of KK than is currently compatible with CR Root. Better waiting til it comes out then seeing what is available.
**[Side Note... If you want KK now you can flash the Official XEO version depending on your Model (IF Hong Kong then it won't work) - and you can root on that without issue after flashing, but you cannot go bac to 4.3 again]**
Click to expand...
Click to collapse
I prefer to wait till an official KK will roll out and update via kies.
Can you please tell me if I do "Wipe cache partition" will fix the root failure probloem ?
I don't realy know what this wipe does...

Solved it (-:
frliran said:
I prefer to wait till an official KK will roll out and update via kies.
Can you please tell me if I do "Wipe cache partition" will fix the root failure probloem ?
I don't realy know what this wipe does...
Click to expand...
Click to collapse
On the settings page under security..make sure you have reactivation lock uncheck...
Than try again..that's usually the problem

It's always something so simple, Not turned activation lock on myself so never had an issue with it. Glad you got sorted thouugh.

Thank you very much for your help
radicalisto said:
It's always something so simple, Not turned activation lock on myself so never had an issue with it. Glad you got sorted thouugh.
Click to expand...
Click to collapse
Yes (-:
Thanl you very much for your help and consideration

[Q] 900V Odin Mode Loop - About to lose my mind

Bought a GS5 (Verizon) SM-G900V for my friend in Brazil and tried to root it and now the phone is stuck in Odin Mode. I cannot get into recovery mode, and I have tried Odin 3.09 on two different computers. I always get fail trying to write the stock image that was on it (NI2) and it it stuck at system.im.ext4.
I have tried pulling the battery countless times to get into recovery mode and to flash it via Odin. Nothing works. The device is not recognized by Keis on either computer either. It asks for the VZW Software Repair Assistant, but I cannot locate a download for that.
He leaves in a few hours, so I need a fix ASAP. Any help is GREATLY appreciated!
Thanks!

jmorehouse said:
Bought a GS5 (Verizon) SM-G900V for my friend in Brazil and tried to root it and now the phone is stuck in Odin Mode. I cannot get into recovery mode, and I have tried Odin 3.09 on two different computers. I always get fail trying to write the stock image that was on it (NI2) and it it stuck at system.im.ext4.
I have tried pulling the battery countless times to get into recovery mode and to flash it via Odin. Nothing works. The device is not recognized by Keis on either computer either. It asks for the VZW Software Repair Assistant, but I cannot locate a download for that.
He leaves in a few hours, so I need a fix ASAP. Any help is GREATLY appreciated!
Thanks!
Click to expand...
Click to collapse
It sounds like you need to use Odin to flash a complete stock retail ROM and start over with the rooting process. It's kind of confusing trying to figure out the problem you're having though. What recovery are you trying to boot to? The stock recovery or SafeStrap? Like I said though, I would start completely over with these steps.
1. Flash a full retail tar with Odin https://www.androidfilehost.com/?fid=23622183712474060
2. Flash NCG firmware with Odin so you can root http://www.androidfilehost.com/?fid=23610159112652200
3. Root using Towelroot https://www.androidfilehost.com/?fid=23681161096070831
4. After root flash NI2 firmware back with Odin https://www.androidfilehost.com/?fid=23622183712474000
5. Install SafeStrap recovery http://forum.xda-developers.com/devdb/project/?id=4718#downloads
6. Go to the Play Store and download SuperSU and install it
If you follow these steps and it works you'll be good to go.

ludeawakening said:
It sounds like you need to use Odin to flash a complete stock retail ROM and start over with the rooting process. It's kind of confusing trying to figure out the problem you're having though. What recovery are you trying to boot to? The stock recovery or SafeStrap? Like I said though, I would start completely over with these steps.
1. Flash a full retail tar with Odin https://www.androidfilehost.com/?fid=23622183712474060
2. Flash NCG firmware so you can root http://www.androidfilehost.com/?fid=23610159112652200
3. Root using Towelroot https://www.androidfilehost.com/?fid=23681161096070831
4. After root flash NI2 firmware back with Odin https://www.androidfilehost.com/?fid=23622183712474000
5. Install SafeStrap recovery http://forum.xda-developers.com/devdb/project/?id=4718#downloads
6. Go to the Play Store and download SuperSU and install it
If you follow these steps and it works you'll be good to go.
Click to expand...
Click to collapse
Thanks, yes, very confusing. I am tried stock recovery. I will try and do full retail back on now again, but I have been reading there is issues with Odin and Verizon 4.4.4 updates. Heimdall is having issues communicating on my mac too. Is that something you are familiar with (the communications issues that is)?

jmorehouse said:
Thanks, yes, very confusing. I am tried stock recovery. I will try and do full retail back on now again, but I have been reading there is issues with Odin and Verizon 4.4.4 updates. Heimdall is having issues communicating on my mac too. Is that something you are familiar with (the communications issues that is)?
Click to expand...
Click to collapse
Tried flashing your stock rom and below is the output from Odin...
Code:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_user_low_ship_MULTI_CERT.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> 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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

jmorehouse said:
Thanks, yes, very confusing. I am tried stock recovery. I will try and do full retail back on now again, but I have been reading there is issues with Odin and Verizon 4.4.4 updates. Heimdall is having issues communicating on my mac too. Is that something you are familiar with (the communications issues that is)?
Click to expand...
Click to collapse
You will not be able to use the stock recovery for flashing anything. You'll have to use SafeStrap for flashing purposes. But if you're just trying to get a rooted stock ROM working, you won't need to use the recovery at all. It's mainly for flashing custom ROM's on this phone. Odin is our best friend for solving major issues on this device since the bootloader is locked. I hope the steps I listed helps.
And yes, I also have communication problems on a Mac with this phone. My PC will boot to OS X 10.7.2 and Windows 7, but when booted to my Mac drive, it can not see my phone. My friends MacBook Pro doesn't see the phone either. I haven't looked into a work-around yet, I just boot from my Windows drive, or use my Windows laptop if I need to be connected to the computer for any reason.
---------- Post added at 01:39 PM ---------- Previous post was at 01:33 PM ----------
jmorehouse said:
Tried flashing your stock rom and below is the output from Odin...
Code:
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_user_low_ship_MULTI_CERT.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> 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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Try to reinstall the Samsung drivers and try again. Make sure the "Re-partition" box is checked in Odin. Use these drivers http://developer.samsung.com/technical-doc/view.do?v=T000000117#none

ludeawakening said:
You will not be able to use the stock recovery for flashing anything. You'll have to use SafeStrap for flashing purposes. But if you're just trying to get a rooted stock ROM working, you won't need to use the recovery at all. It's mainly for flashing custom ROM's on this phone. Odin is our best friend for solving major issues on this device since the bootloader is locked. I hope the steps I listed helps.
And yes, I also have communication problems on a Mac with this phone. My PC will boot to OS X 10.7.2 and Windows 7, but when booted to my Mac drive, it can not see my phone. My friends MacBook Pro doesn't see the phone either. I haven't looked into a work-around yet, I just boot from my Windows drive, or use my Windows laptop if I need to be connected to the computer for any reason.
---------- Post added at 01:39 PM ---------- Previous post was at 01:33 PM ----------
Try to reinstall the Samsung drivers and try again. Make sure the "Re-partition" box is checked in Odin. Use these drivers #
Click to expand...
Click to collapse
Thanks. I did that, restarted and now I get the following in Odin:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

Is it a factory cable? If it is redownload the file.

Yes sometimes the cable does make a difference. You can try downloading the file again, although, getting a bad download from XDA is pretty rare. I'm not familiar with Odin failing to flash a file. I've never had it happen to me.
Sent from my SM-G900V using XDA Free mobile app

jmorehouse said:
Thanks. I did that, restarted and now I get the following in Odin:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
It is a stock cable. Installed the latest version of the drivers taken from Samsung Kies 3.2.14113.3 (2014-11-20) for Windows and got the following:
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> ALL_VZW_G900VVRU1ANI2_G900VVZW1ANI2_2525521_REV00_user_low_ship_MULTI_CERT.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Added!!
<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> 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> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> sdi.mbn
<ID:0/003> NON-HLOS.bin
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)

I'm starting to think it may be a hardware problem with the phone, because you are following all of the steps exactly how you should. Odin does show that the phone is connected to a Com port right?
Sent from my SM-G900V using XDA Free mobile app

ludeawakening said:
I'm starting to think it may be a hardware problem with the phone, because you are following all of the steps exactly how you should. Odin does show that the phone is connected to a Com port right?
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
That is correct. It shows it on COM3.

I'm really not sure what going on. It should be working. I'll ask someone and see if they have any ideas.
Sent from my SM-G900V using XDA Free mobile app

ludeawakening said:
I'm really not sure what going on. It should be working. I'll ask someone and see if they have any ideas.
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
Please and thank you. I am going to try and get another laptop to try it on.

jmorehouse said:
Please and thank you. I am going to try and get another laptop to try it on.
Click to expand...
Click to collapse
Grabbed a cheap netbook off of CL and boom! There we go, it worked. Thanks so much for the help.

jmorehouse said:
Grabbed a cheap netbook off of CL and boom! There we go, it worked. Thanks so much for the help.
Click to expand...
Click to collapse
No problem. I'm glad it worked out for you. If you have any other issues don't hesitate to PM me. Helping people is one of my favorite things to do on here.

ludeawakening said:
No problem. I'm glad it worked out for you. If you have any other issues don't hesitate to PM me. Helping people is one of my favorite things to do on here.
Click to expand...
Click to collapse
Nice "thorough"job helping out the op!! :thumbup:
Sent from my SM-G900V using XDA Free mobile app

Savagerun said:
Nice "thorough"job helping out the op!! :thumbup:
Sent from my SM-G900V using XDA Free mobile app
Click to expand...
Click to collapse
Thank you. If I do step in to help, I'm the type that will not give up on someone until either the issue is solved, or it's deemed that there is a hardware issue or something and nothing can be done. I remember what it was like being lost on trying to do this stuff. I researched and studied for a long time on how Android works, so I might as well put all that gained knowledge to good use by helping people now. And that's what an awesome community like XDA does, we help each other.

jmorehouse said:
Grabbed a cheap netbook off of CL and boom! There we go, it worked. Thanks so much for the help.
Click to expand...
Click to collapse
I got your PM and I've been trying to send a reply with info on ROM's but it will not send for some reason. I'll just give you the info here. Send me another PM with your email if you don't mind, and we can communicate that way if messages continue to not work.
If you want a ROM that is on the most current base that looks the most unbranded I would go with ACHERON. I say g_ding84 has done a very good job at removing the Verizon bloatware from the ROM. I personally do not care about being on a current, so I am still running Alliance Build 2. It offers the most customization and I just had to freeze five apps to unbrand it. I use Titanium Backup Pro to freeze apps. I don't really like removing apps like that. You'll need to find the apk somewhere, or buy Titanium Backup Pro from the Play Store. I won't post any links to free versions of any apps on here. I really do not condom finding free versions of a paid app because it's not fair to the developer.
Anyway, If you would like to go with Alliance, this is the link for it http://forum.xda-developers.com/verizon-galaxy-s5/development/rom-version-1aosp-love-9-7-14-t2870149
To use this ROM you have to be sure to flash the NE9 firmware back to the phone with Odin. This is the firmware you would need to flash. http://www.androidfilehost.com/?fid=23610159112652201
The apps that you can freeze to debrand it are:
Cloud 14.2.22.2
FamilyBase Companion 4.4.5
My Verizon Mobile 10.0.709
Verizon Location Agent 0.0.2.409
Verizon Login 3.1.19

ludeawakening said:
I got your PM and I've been trying to send a reply with info on ROM's but it will not send for some reason. I'll just give you the info here. Send me another PM with your email if you don't mind, and we can communicate that way if messages continue to not work.
If you want a ROM that is on the most current base that looks the most unbranded I would go with ACHERON. I say g_ding84 has done a very good job at removing the Verizon bloatware from the ROM. I personally do not care about being on a current, so I am still running Alliance Build 2. It offers the most customization and I just had to freeze five apps to unbrand it. I use Titanium Backup Pro to freeze apps. I don't really like removing apps like that. You'll need to find the apk somewhere, or buy Titanium Backup Pro from the Play Store. I won't post any links to free versions of any apps on here. I really do not condom finding free versions of a paid app because it's not fair to the developer.
Anyway, If you would like to go with Alliance, this is the link for it http://forum.xda-developers.com/verizon-galaxy-s5/development/rom-version-1aosp-love-9-7-14-t2870149
To use this ROM you have to be sure to flash the NE9 firmware back to the phone with Odin. This is the firmware you would need to flash. http://www.androidfilehost.com/?fid=23610159112652201
The apps that you can freeze to debrand it are:
Cloud 14.2.22.2
FamilyBase Companion 4.4.5
My Verizon Mobile 10.0.709
Verizon Location Agent 0.0.2.409
Verizon Login 3.1.19
Click to expand...
Click to collapse
Awesome, thanks so much! Can you point me to a tutorial for SafeStrap Recovery?

jmorehouse said:
Awesome, thanks so much! Can you point me to a tutorial for SafeStrap Recovery?
Click to expand...
Click to collapse
You can find a video in this thread http://forum.xda-developers.com/showthread.php?t=2784290
Sent from my SM-G900V using XDA Free mobile app

[Q] Rooting persistently Failed on Samsung Galaxy S5 G900H

Device: Galaxy S6 G900H
ROM: First Lollipop 5.0 then KitKat 4.4.2
Problem: Unable to root phone and install custom recovery
Rooting methods tried:
Odin 3.09 (and 3.07 after 3.09 failed). It got this message:
<ID:0/007> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CF-Auto-Root-k3g-k3gxx-smg900h.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> FAIL!
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
ADB method in Ubuntu Linus as delineated in this thread: http androidforums.com/threads/how-to-root-any-android-device-manually.586982) Sorry, forum rules forbid newbies from posting links. I followed the instructions up to the point when the phone was put in recovery, thereafter the phone did not show up in the Nautillus file browser.
Heimdall
KINGO Root. This always reported success, but Root checker says there is no root. Titanium backup failed to work because there was no root
OneClick Root also failed
SRSRoot for Android also failed
Skipsoft Android Toolkit (Which I paid for) also failed . I contacted the developer through G+ and Twitter and E-mail, but he has not replied
After trying all these methods in LOLLIPOP (and knowing I had enjoyed ROOT in Kitkat before moving on to Lollipop) , I flashed back to KITKAT 4.4.2, and rooting with Odin and all the other methods failed also. Please, note that I had enjoyed rooting on the phone for more than a year, before upgrading to Lollipop 5.0 (BOAD).
Finally, Rooting through Stock Recovery using Phil_Touch also failed at "E-whole file verification failed".
I don't know what to do again. Can someone help please?

same here, can't root! g900h

I have rooted successful with CF-ROOT, no problems.
Sent from my SM-G900H using XDA Free mobile app

Bird100 said:
I have rooted successful with CF-ROOT, no problems.
Sent from my SM-G900H using XDA Free mobile app
Click to expand...
Click to collapse
Thank you, but as you can see from my post, I have tried that method, and it failed. Do you know of any other methods apart from the ones listed above that I can use to root the phone? That's all I'm interested in.

I had the same problem with kitkat but it worked one I've changed the bootloader and the modem version. I had rooted my phone with CF-ROOT After that without any problem.
Try it who knows

davidliu21 said:
same here, can't root! g900h
Click to expand...
Click to collapse
Please let me know if you finally succeed. How many methods have you tried? Have you tried all the methods I attempted?

TheM0r0ccan said:
I had the same problem with kitkat but it worked one I've changed the bootloader and the modem version. I had rooted my phone with CF-ROOT After that without any problem.
Try it who knows
Click to expand...
Click to collapse
This sounds interesting. I had to change my bootloader to Modem_BOB8.tar and modem to G900H-LP-XXU1BOB8-MODEM.tar when updating to LOLLIPOP. Can this be the reason? I do have some questions for you to answer, if you don't mind:
You change your modem and bootloader from what to what?
Is it possible to change back my bootloader and modem to an earlier version while still using lollipop?
Many thanks for this possible lead

Help error aboot

Hello.
I have a T-Mobile Galaxy S5 Model SM-G900T3. It came with Lollipop 5.1.1 installed. I root it and now I want to return the phone to stock. I followed every tutorial and they are all the same so i am doing everything right but each time it fails and the phone gives me in red "secure check fail : aboot"
Odin says:
<ID:0/004> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> G900TUVU1ANCH_G900TTMB1ANCH_G900TUVU1ANCH_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/004> Odin engine v(ID:3.1005)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> aboot.mbn
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I have tried different Odin version, different firmware and different usb ports and cables and the phone is charged 60% of battery.

It's failing at aboot (the bootloader) because it's failing the security check that prevents flashing the wrong firmware. You're gonna need to find actual G900T3 firmware. Why the hell tmo changed it up or what the actual difference is I have no idea but kinda curious
---------- Post added at 11:30 PM ---------- Previous post was at 11:27 PM ----------
Ha found it
http://samsung-firmware.org/download/GALAXY-S5/34q4/TMB/G900T3UVU1FOG6/G900T3TMB1FOG6/
I just downloaded from this site today. Expect a 2 hour download

ShinySide said:
It's failing at aboot (the bootloader) because it's failing the security check that prevents flashing the wrong firmware. You're gonna need to find actual G900T3 firmware. Why the hell tmo changed it up or what the actual difference is I have no idea but kinda curious
---------- Post added at 11:30 PM ---------- Previous post was at 11:27 PM ----------
Ha found it
http://samsung-firmware.org/download/GALAXY-S5/34q4/TMB/G900T3UVU1FOG6/G900T3TMB1FOG6/
I just downloaded from this site today. Expect a 2 hour download
Click to expand...
Click to collapse
Ok solve it. For anyone with the Galaxy S5 Model SM-G900T3 tis is the stock rom to unroot unbrick your phone.
http://www.sammobile.com/firmwares/database/SM-G900T3/

Rooting after upgrade G900T3 to FOG6?
I will soon be upgrading my FOF6-based G900T3 to FOG6 via the firmware listed above.
I realize that once I do that, I will lose root.
Has anyone successfully rooted a FOG6-based G900T3? Does anyone know whether G900T_FOG6_TrapKernel.zip will work on the G900T3, or is that limited to a G900T? Is there perhaps another method for rooting an FOG6-based G900T3?
.​

HippoMan said:
I will soon be upgrading my FOF6-based G900T3 to FOG6 via the firmware listed above.
I realize that once I do that, I will lose root.
Has anyone successfully rooted a FOG6-based G900T3? Does anyone know whether G900T_FOG6_TrapKernel.zip will work on the G900T3, or is that limited to a G900T? Is there perhaps another method for rooting an FOG6-based G900T3?
Click to expand...
Click to collapse
I confirm that G900T_FOG6_TrapKernel.zip indeed works fine for rooting the G900T3.
.​

CRE9 Update GONE WRONG

Help me please, I locked myself out by trying to update my s8 from cre8 to cre9 like a retard and bricked my phone. Won't let me ODIN back to CRD4 as its bootloader 3.
Any solutions other than waiting for them to release an odin copy of bootlader 4?

I guess you can't flash twrp ?

klip1 said:
Help me please, I locked myself out by trying to update my s8 from cre8 to cre9 like a retard and bricked my phone. Won't let me ODIN back to CRD4 as its bootloader 3.
Any solutions other than waiting for them to release an odin copy of bootlader 4?
Click to expand...
Click to collapse
full flash cred etc with odin. to solve

Cant flash twrp cause model 950u, and WHAT DO YOU MEAN BY FULL FLASH CRED. i've tryed everything, can you break it down step by step?

I tryed installing roms etc using cosby odin and others but no dice
I've tryed samfirm's latest, i've tryed installing everything even stock firmware but of course the binary is 4, won't ttake anything less
can you give me links?!
i know how to use odin, flashing firmware etc

klip1 said:
I tryed installing roms etc using cosby odin and others but no dice
I've tryed samfirm's latest, i've tryed installing everything even stock firmware but of course the binary is 4, won't ttake anything less
can you give me links?!
i know how to use odin, flashing firmware etc
Click to expand...
Click to collapse
Here, try this version of odin. It may work, it may not, but let me know if it does let you downgrade or flash whatever revision your trying to flash.
Good Luck!!

scotteb said:
Here, try this version of odin. It may work, it may not, but let me know if it does let you downgrade or flash whatever revision your trying to flash.
Good Luck!!
Click to expand...
Click to collapse
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/007> Odin engine v(ID:3.1203)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> FAIL! Model dismatch fail
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1203)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Erase...
<ID:0/007> FAIL! Model dismatch fail
<OSM> All threads completed. (succeed 0 / failed 1)
CANT SOMEONE PUT SOMETHING TOGETHER TO ODIN ME BACK?

SOMEONE PLEASE HELP! IS THERE ANYWAY SOMEONE CAN CHOP AND PIECE TOGETHER AN ODIN WORKING FLASHFILE THAT LIKE INCLUDES THE 4th bootloader but rest regular files?

klip1 said:
SOMEONE PLEASE HELP! IS THERE ANYWAY SOMEONE CAN CHOP AND PIECE TOGETHER AN ODIN WORKING FLASHFILE THAT LIKE INCLUDES THE 4th bootloader but rest regular files?
Click to expand...
Click to collapse
Don't know if you are still bricked, but there is now a bootloader 4 ODIN file available here: https://forum.xda-developers.com/showpost.php?p=76819577&postcount=3603