Hi, my brother-in-law tried to root his phone but probably didn't know what he was doing with Odin and Kies. I tried to restore the phone with Kies3 but the phone is not recognized and I can't get a recovery code. I've tried the default option of booting into recovery mode and flashing with Odin as Administrator. I'm flashing following a guide on this forum using [Auto Reboot] [F. Reset Time] checked in the options and loading [AP] [CP] [CSC] first. Others have commented not to use the [BL] file. The problem is when I try to flash it fails and I get this message:
<ID:0/007> Odin engine v(ID:3.1100)..
<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> boot.img
<ID:0/007> NAND Write Start!!
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> FAIL! (Auth)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
On the screen of the phone it says:
UDC START
SYS REV CHECK FAIL : Refer 3 > Binary 1
SECURE CHECK FAIL : system
Click to expand...
Click to collapse
I've tried everything I could flashing each one by one [BL] [AP] [CP] and [CSC]. Apparently the only one that successfully flashed through was [CP]. The phone can boot into recovery mode fine, when I start the phone normally it just hangs on the Samsung Galaxy S5 screen. Any help in the right direction would be appreciated. I have pretty much GoogledFu'd all the information I can and am using the stock Samsung Galaxy S5 SM-G900A firmware. I have tried different USB ports, the stock Samsung USB cable, and an LG USB cable and that didn't help either.
To flash the firmware using Odin you need to put the phone in Download mode (Power + home + volume down) and not recovery mode. Select PDA/AP in Odin, select the firmware and then click start.
DigitalBeating said:
Hi, my brother-in-law tried to root his phone but probably didn't know what he was doing with Odin and Kies. I tried to restore the phone with Kies3 but the phone is not recognized and I can't get a recovery code. I've tried the default option of booting into recovery mode and flashing with Odin as Administrator. I'm flashing following a guide on this forum using [Auto Reboot] [F. Reset Time] checked in the options and loading [AP] [CP] [CSC] first. Others have commented not to use the [BL] file. The problem is when I try to flash it fails and I get this message:
On the screen of the phone it says:
I've tried everything I could flashing each one by one [BL] [AP] [CP] and [CSC]. Apparently the only one that successfully flashed through was [CP]. The phone can boot into recovery mode fine, when I start the phone normally it just hangs on the Samsung Galaxy S5 screen. Any help in the right direction would be appreciated. I have pretty much GoogledFu'd all the information I can and am using the stock Samsung Galaxy S5 SM-G900A firmware. I have tried different USB ports, the stock Samsung USB cable, and an LG USB cable and that didn't help either.
Click to expand...
Click to collapse
Yes, I already have done that and the only thing that writes successfully is the [CP] file. It fails to write to the NAND and does a FAIL! (Auth). Not sure what else I can do.
Alright I think I figured exactly what he did to the phone. Apparently AT&T locked the bootloader on Lollipop and his phone got upgraded to Lollipop while he was sleeping. So he tried to use Odin to flash the AP for the older KitKat back onto the S5 and this softbricked the phone. As far as I have read there is no way to downgrade back currently to KitKat to get root access. I'm trying to look for stock firmware for Lollipop but I can't find anything for this model. I assume if I flash it back to the latest Lollipop version functionality will be restored. Someone said something about flashing a kernel but I don't know. Not really sure what to do now since I can't find official Samsung S5 SM-G900A firmware to flash back either through the recovery or through Odin.
DigitalBeating said:
Alright I think I figured exactly what he did to the phone. Apparently AT&T locked the bootloader on Lollipop and his phone got upgraded to Lollipop while he was sleeping. So he tried to use Odin to flash the AP for the older KitKat back onto the S5 and this softbricked the phone. As far as I have read there is no way to downgrade back currently to KitKat to get root access. I'm trying to look for stock firmware for Lollipop but I can't find anything for this model. I assume if I flash it back to the latest Lollipop version functionality will be restored. Someone said something about flashing a kernel but I don't know. Not really sure what to do now since I can't find official Samsung S5 SM-G900A firmware to flash back either through the recovery or through Odin.
Click to expand...
Click to collapse
I am currently in the same boat. Please tell me you found a fix for this and if so, what was it? Any help is greatly appreciated.
@DigitalBeating and @Theamazingcorey
Here is an AT&T lollipop firmware.....
https://www.androidfilehost.com/?fid=24591000424940454
G900AUCU4COI5_ATT4COI5_v5.1.1_Repair_Firmware
I found it (by chance) on a Russian hosting site. They say it's a 'repair' firmware which means it is more than likely going to be more than one file (it'll probably be bootloader, modem and OS) So you'll have to load each file into it's respective Odin 'slot'.
If I understand how repair firmwares work, it should wipe and format the data partitions (instead of simply overwriting them) as it flashes. This will give the best chance of a successful flash.....
http://i.imgur.com/rVnFwJM.jpg
I cannot thank you enough, that seems to have fixed my problem. I though I was going to be stuck with a paperweight, lol.
Would you happen to know if there is a way to root the the AT&T S5 with 5.1.1?
Glad it worked fella.....
With regards to rooting, everything I've read on XDA indicates AT&T Lollipop can't be rooted....and the possibility of downgrading to achieve root is non existent.......
But there's a LOT if information on XDA, and I'll be the first to admit that I haven't read it all........
http://i.imgur.com/rVnFwJM.jpg
@Theamazingcorey just out of interest, can you confirm what files were inside the zip?
http://i.imgur.com/rVnFwJM.jpg
Thanks for the info. Sorry I was not able to get back to you sooner, I've been slammed these last couple of days. Have family coming into town this evening and between work and getting ready for their visit, I haven't had time to think straight, lol.
Related
i have been trying to install stock Lollipop on my device. i have followed both http://www.androidpit.com/how-to-get-android-5-0-lollipop-on-the-galaxy-note-3 and http://techbeasts.com/2015/02/14/update-galaxy-note-4-n910f-android-501-lollipop-official/ to the letter. This is also my fourth or fifth time using Odin. Every attempt has failed. i have tried Odin 3.10, 3.09, and 3.07 and got the same results:
Code:
<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> sbl1.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
My phone's download screen gave thisd message:
Code:
Secure Check Fail : sbl1
until i switched from "N9005XXUGBOB6_N9005XEOGBOA4_XEO" to "N9005XXUGBOA5_N9005XEOGBOA4_XEO" and also freezing any anti-theft app that may be locking my device somehow. Now the screen says:
Code:
Secure Check Fail : aboot
i am rooted (running Omega 24) and to be sure, i re-flashed auto-root
i have tried 4 different USB cables
No USB hubs, i am connected directly to my PC
Firewall, AntiVirus, and Anti Malware software are all off.
i have run Odin as admin
Reactivation Lock is not ticked
Some other things me screen says that may be of some help are:
Code:
QUALCOMM SECUREBOOT: ENABLE
followed by some coupling of letters and numbers and:
Code:
Write Protection: Enable
i am hoping that a factory reset can be my very last resort. i am contemplating reflashing my current Omega ROM and then retrying this.
Any ideas?
EDIT: Factory Reset did not change anything
Is your device unlocked or branded?
Joku1981 said:
Is your device branded or unlocked?
Click to expand...
Click to collapse
It should be unlocked. i unlocked it a while ago when i flashed my first ROM. i have been flashing Omega roms ever since. i cannot imagine my phone would lock itself back up...
billybag said:
It should be unlocked. i unlocked it a while ago when i flashed my first ROM. i have been flashing Omega roms ever since. i cannot imagine my phone would lock itself back up...
Click to expand...
Click to collapse
Odin gave you fail in the NAND. This mean that you have lost plenty of files in EFS. Try to restore your OMEGA backup.
Joku1981 said:
How you unlocked it? By IMEI or other method?
Click to expand...
Click to collapse
Damn, i don't remember. It seemed so long ago. i don;t suppose there is a way to check...
EDIT: while attempting a restore of a nandroid backup, i noticed something. The following backup files were missing:
.android_secure.vfat.tar and
.android_secure.vfat.tar.a
i REALLY appreciate your time and help, by the way. This is so frustrating. One person told me that they repartitioned and selected bootloader when they flashed, but was not advising me to do so.
billybag said:
i REALLY appreciate your time and help, by the way. This is so frustrating. One person told me that they repartitioned and selected bootloader when they flashed, but was not advising me to do so.
Click to expand...
Click to collapse
Do you have any EFS backup?
billybag said:
i REALLY appreciate your time and help, by the way. This is so frustrating. One person told me that they repartitioned and selected bootloader when they flashed, but was not advising me to do so.
Click to expand...
Click to collapse
If you want to flash stock LP, I would just bite the bullet and do it and first get a working system. Then install Recovery and re-root - I use TWRP.tar file so I can flash it in Odin and the SuperSU zip file that I then flash in Recovery.
You don't say which N3 you have but are you sure you have the right ROM for it?
Did you turn off the phone and remove the battery for a bit THEN go into download mode?
Are you using v3.09 of ODin PC?
I've done mine twice for other reasons since LP came out - I untick the auto-reboot so after I flash the stock firmware I can flash TWRP - then it's boot into Recovery and install my custom ROM (I use Temasek's CM12) PA GApps and the SuperSU.zip, then set up the phone - usually I then Restore only Data from my latest TWRP backup but on occasion I've DL'd Titanium from Ply and used that to Restore my apps from extSD.
Journyman16 said:
If you want to flash stock LP, I would just bite the bullet and do it and first get a working system. Then install Recovery and re-root - I use TWRP.tar file so I can flash it in Odin and the SuperSU zip file that I then flash in Recovery.
You don't say which N3 you have but are you sure you have the right ROM for it?
Did you turn off the phone and remove the battery for a bit THEN go into download mode?
Are you using v3.09 of ODin PC?
I've done mine twice for other reasons since LP came out - I untick the auto-reboot so after I flash the stock firmware I can flash TWRP - then it's boot into Recovery and install my custom ROM (I use Temasek's CM12) PA GApps and the SuperSU.zip, then set up the phone - usually I then Restore only Data from my latest TWRP backup but on occasion I've DL'd Titanium from Ply and used that to Restore my apps from extSD.
Click to expand...
Click to collapse
That is what i am having problems with. i know how to flash custom roms. i was also able to flash stock KK when it came out. It is stock lollipop that i cannot get to flash. i am using an SM-n9005 (tmobile). i am going to try different firmware downloads (CSCs) and see what that does.
Also, i have tried Odin versions 3.07, 3.09, and 3.10
billybag said:
That is what i am having problems with. i know how to flash custom roms. i was also able to flash stock KK when it came out. It is stock lollipop that i cannot get to flash. i am using an SM-n9005 (tmobile). i am going to try different firmware downloads (CSCs) and see what that does.
Also, i have tried Odin versions 3.07, 3.09, and 3.10
Click to expand...
Click to collapse
Do you know your original firmware? I'm wondering because some versions have different sized partitions and flashing another type causes fails. i.e. I had a HK S3 and had to flash a PIT file before I could use European firmware. Might it be something along those lines?
Have practically the same situation...
The furthest I've got is the following
Code:
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> sbl1.mbn
<ID:0/003> aboot.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)
But again, with any version of odin and any firmware (lollipop or kitkat) i'm trying to flash, it stucks with
Code:
<ID:0/003> Complete(Write) operation failed.
PS I also have
Code:
QUALCOMM SECUREBOOT: ENABLE
Write Protection: Enable
and my phone was originally locked to spanish vodafone.
Sorry for the delay. i just got around to giving it another shot and it worked. i found an official, made for TMOBILE, version of the firmaware.
Code:
N900TUVUFOB6_N900TTMBFOB6_TMB
for anyone else that may be having trouble. You can find it here: http://www.sammobile.com/firmwares/download/43850/N900TUVUFOB6_N900TTMBFOB6_TMB/
i was using n9005 firmwares, which is usually fine except int his case i needed a tmo one.
Thanks again for everyone's input. Hopefully this post can help someone else out now.
Hello people,
I have tried a lot of things since two hours, but I just cannot go past it. I installed the stock firmware on my i9505 from CM12. And it worked fine. However it got unrooted by itself. Now I want to root it back and install a custom rom.
Firstly, odin never turned yellow. Now when it did, it says There is no PIT partition. I am trying to install a recovery, so that the phone gets rooted first.
I am putting the phone in download mode, connecting the USB cable, and then adding the recovery file in the PDA section. And the same result keeps coming. I have tried switching F.Reset time on and off just to check if that is working, but both don't.
I've read the suggestions on xda, and I have changed USB ports, restarted phone, laptop, changed the laptop and tried again. It also says Write protection: enable.
Here's the log as well.
<ID:0/007> Added!!
<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> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/007> Removed!!
<ID:0/007> Added!!
<ID:0/007> Removed!!
<ID:0/007> Added!!
<ID:0/007> Removed!!
<ID:0/007> Added!!
Please help me out on this. Thanks!
And now the phone is bricked! It says firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.
thehtmldev said:
And now the phone is bricked! It says firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.
Click to expand...
Click to collapse
Use a different usb port / different usb cable.
thehtmldev said:
And now the phone is bricked! It says firmware upgrade encountered an issue. Please select recovery mode in Kies and try again.
Click to expand...
Click to collapse
If you can't flash anymore, then install kies and select recovery mode. The recovery mode will work only if you have an active internet connection, required for downloading the system files.
Rooting is not required to install a custom rom.
Looks for a pit file for your phone and flash it together with twrp. Once you have twrp working, you can wipe the system, cache, data, etc. and flash a custom rom.
audit13 said:
Rooting is not required to install a custom rom.
Looks for a pit file for your phone and flash it together with twrp. Once you have twrp working, you can wipe the system, cache, data, etc. and flash a custom rom.
Click to expand...
Click to collapse
You can't flash pit file via twrp. He needs to reflash all, to back to the stock rom. But, odin gets error. I suggest to him to use kies to recover his phone.
Giovix92 said:
You can't flash pit file via twrp. He needs to reflash all, to back to the stock rom. But, odin gets error. I suggest to him to use kies to recover his phone.
Click to expand...
Click to collapse
You are correct in the part that Odin can't flash a .pit file. But that's not what Audit13 is saying. He is saying that when flashing TWRP through Odin he also uses the .pit file.
The .pit error in 99% of the cases is solved by using a different usb port and different cable.
Lennyz1988 said:
You are correct in the part that Odin can't flash a .pit file. But that's not what Audit13 is saying. He is saying that when flashing TWRP through Odin he also uses the .pit file.
The .pit error in 99% of the cases is solved by using a different usb port and different cable.
Click to expand...
Click to collapse
In 1% of case the .pit file is damaged. Yes, you're right about TWRP, but he can't flash the stock firmware by TWRP.
Deleted, posted message in wrong forum. Sorry.
Obtain a pit file and flash it together with your desired firmware via ODIN. I'm afraid that your pit is damaged. (Like others said if any)
Sent from my GT-I9500
Try flashing the last official firmware you used on Sammobile and let it do a full boot and then try flashing again the custom recovery...
The Samsung Galaxy S5 (SM-G900F) is stuck at the boot screen and keeps restarting. I cant go into recovery mode. I can only go into the download mode. I tried to flash it with odin and update it with kies. But none of it works.
At the download mode screen it says:
ODIN : flash read failure
Error: There is no pit binary
Odin screen:
<ID:0/013> Odin engine v(ID:3.1101)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013>
<ID:0/013> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
Any help will be appreciated
Got your back.
Hey man just make sure you closed odin completely.
1. Start Kies
2.Click Tools-> Firmware upgrade and initilazation
3.Type in model of your phone for example sm-g900i which is my Australian S5 then it will ask you for your SN which is a 16 digit code serial number located on the back of your phone when you remove the battery.
Then just follow steps until it asks YOUR phone to be connected... DONT connect it yet...first put it in download mode; phone turned off; press home but, power but, and vol down bot at same time then press vol up key to enter download mode.
Connect phone; then just wait 1 hour and voila you got your phome with latest stock firmware.
Please reply to us if this worked for you as this can help new users to determine what to do.
Cheers
Sorry but English is not my first language, hope i made myself clear.
If there is anything else i can do to assist please let me know.:laugh:
Which Kies works with the S5? Because neither seem to be working
I'm having pretty much the same problem, had a bad flash and can't boot into recovery or get it detected in Kies
And I can't flash stock Marshmallow or Lollipop till I finish downloading them
Going through firmware upgrade and installation option and putting in the model just causes Kies to freeze using either version
WalkableBuffalo said:
Which Kies works with the S5? Because neither seem to be working
I'm having pretty much the same problem, had a bad flash and can't boot into recovery or get it detected in Kies
And I can't flash stock Marshmallow or Lollipop till I finish downloading them
Going through firmware upgrade and installation option and putting in the model just causes Kies to freeze using either version
Click to expand...
Click to collapse
Kies will automaticlly download the correct atock fw.....just use Kies lite versiom which is the one i used a couple of days ago and had exactly the same problem as you i actually had a corrupter pit file so there was no partition being found...again install and use lite kies for samsung then just dlow the steps ut should automatically download the firmware and install it into samsung at the same time you shpuld not remove the cable whatsoever during download and installation and actually make sure yu have the drivers for samsung installed and that the usb cable you are using is original....hope it works if you need a detailed guide with instalation steps let me know or heck i cpuld even help out with a video just let me know.
Hope you get it sorted and if you do please let us all know so in the furute people can see the answer.
Cheers.
It's alright I fixed it now, still couldn't get Kies to work
I flashed the latest version of Lollipop (no carrier) to the phone, which initially sent it into a bootloop. But that enabled recovery again so I did a data and cache wipe, flashed the same ROM from ODIN again and it worked
Hi, when trying to flash my Verizon S7 back to stock (with the correct verizon files) I got this odin log
<ID:0/003> Odin engine v(ID:3.1203)..
<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> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
When trying to exit I got the "Software Update Failed" and when trying to flash again it's just a stuck bar on my screen. Not sure what to do and I'm kinda of new to this but I'd appreciate any help. Since then my phone has been stuck on the green screen since and whenever I press anything it just returns to the screen.
Any fast help would really be appreciated, it's been like this for hours and I'm not sure what to do ):
I'm gonna take a quick stab at this and say use the other CSC file, whichever one you haven't tried (either csc_vzw or home_csc_vzw).
Do not use the HOME_CSC file. Use the CSC and be sure that all of the images are in the correct spots in ODIN.
Was the device rooted? If so, you may not have gotten rid of all the root files, so it detects modified and won't flash.
Which firmware are you trying to flash? Were you on Nougat? We need more information.
Are you going from U firmware? I had to check repartition when I did.
ironbesterer said:
Do not use the HOME_CSC file. Use the CSC and be sure that all of the images are in the correct spots in ODIN.
Was the device rooted? If so, you may not have gotten rid of all the root files, so it detects modified and won't flash.
Which firmware are you trying to flash? Were you on Nougat? We need more information.
Click to expand...
Click to collapse
I was rooted through the steps found here
https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
I tried to flash back to stock and got the error after that. My phone's battery died and it's just sitting on my desk now );
Sayunoi said:
I was rooted through the steps found here
https://forum.xda-developers.com/ve...-to-notes-root-install-xposed-unroot-t3411039
I tried to flash back to stock and got the error after that. My phone's battery died and it's just sitting on my desk now );
Click to expand...
Click to collapse
Same thing here. I can only get into stock recovery with the error "dm-verity verification failed" (most options are disabled), and into bootloader, but unable to flash stock ROM; it just fails every time.
I'd be glad for a solution!
Don't forget the bootloader file too. I believe the root thread doesn't include the BL file in the instructions, but the error disappeared when I included the Bootloader.
azoller1 said:
Don't forget the bootloader file too. I believe the root thread doesn't include the BL file in the instructions, but the error disappeared when I included the Bootloader.
Click to expand...
Click to collapse
Mine still has the error when I included the bootloader file.
Another thing I should mention is in the top right it says "SW REV CHECK FAIL : [system] Fused 3 > Binary 1
I tried changing the wire, using the boot loader file, and changing usb ports. Lost here );
Sayunoi said:
When trying to exit I got the "Software Update Failed"
Click to expand...
Click to collapse
I tried going back to stock as well and am stuck on this screen. It says to use the Verizon Software Repair Assistant on a computer to repair it. I've only ever rooted a kindle fire so I don't know too much. Any way I can just get my phone back to normal?
JaffXsMan said:
I tried going back to stock as well and am stuck on this screen. It says to use the Verizon Software Repair Assistant on a computer to repair it. I've only ever rooted a kindle fire so I don't know too much. Any way I can just get my phone back to normal?
Click to expand...
Click to collapse
Really wondering the same thing =/
I think maybe I'm trying to flash back to an older version. Does anyone have a link for the latest Galaxy S7 stock rom?
Sayunoi said:
I think maybe I'm trying to flash back to an older version. Does anyone have a link for the latest Galaxy S7 stock rom?
Click to expand...
Click to collapse
You cannot flash a stock rom with an older bootloader than what ever you currently have on your phone. You can only Odin flash a stock rom with same or newer bootloader. So usually you cannot go to an older rom only newer.
Can I try flashing stock rom while in the Software update failed screen, or do I need to be in download mode?
Sayunoi said:
I tried changing the wire, using the boot loader file, and changing usb ports. Lost here );
Click to expand...
Click to collapse
Try re-downloading the firmware. Are you sure you had the right firmware downloaded? The error seems to be caused by some kind of mismatch between the software trying to be flashed and what software you currently have on your phone
Also, make sure you are using the non princecosmy Odin 3.12
When ever I try to flash stock onto my phone, i'm getting the error "SW REV CHECK FAILED : [aboot] fused 4 > binary 2" I don't know what any of this means. Could someone explain this? Also when trying to flash stock i'm in "System Update Failed" screen and a little bar appears at the bottom. Does this mean it is still able to download the stock rom at all? One last thing, if I were to try and flash G935U instead of G935V could that help? Any help would be nice
go to samfirm and download the latest firmware for the S7 that you have, try flashing with that. I had to put everything in it's place in odin and select reformat to unroot my phone. I ran into the dm_verification failed and the only option was to download the latest firmware and flash that.
JerseyDubbin said:
go to samfirm and download the latest firmware for the S7 that you have, try flashing with that. I had to put everything in it's place in odin and select reformat to unroot my phone.
Click to expand...
Click to collapse
Do you mean sammobile? https://www.sammobile.com/firmwares/database/SM-G935F/
That or http://samfirm.net/I believe.
Hi, I hope I can get an answer on this. Purchased the Note 4, just went outside of warranty a few weeks ago, and I'm trying to root it.
I set my phone in debug mode, and tried on both ODIN 3.9 and the last RV to no avail and tried to flash CF-Auto-Root-trltecan-trltecan-smn910w8.tar.md5
I don't understand what it is I'm doing wrong. Installed all drivers with Samsung USB Driver, and KIES
Uninstalled KIES as I heard it was not recommended.
It hangs during the download stage at <ID:0/003> recovery.img
Getting real frustrated as documentation doesn't really cover anything for the latest Android version released for this phone.
Any help would be greatly appreciated.
Thank you in advance!
WarDerp said:
Hi, I hope I can get an answer on this. Purchased the Note 4, just went outside of warranty a few weeks ago, and I'm trying to root it.
I set my phone in debug mode, and tried on both ODIN 3.9 and the last RV to no avail and tried to flash CF-Auto-Root-trltecan-trltecan-smn910w8.tar.md5
I don't understand what it is I'm doing wrong. Installed all drivers with Samsung USB Driver, and KIES
Uninstalled KIES as I heard it was not recommended.
It hangs during the download stage at <ID:0/003> recovery.img
Getting real frustrated as documentation doesn't really cover anything for the latest Android version released for this phone.
Any help would be greatly appreciated.
Thank you in advance!
Click to expand...
Click to collapse
DISCLAIMER-_-Try on your own risk.
This is a universal method if you follow all steps correctly you will have permanent root and also custom recovery for flashing roms,zip files,backup roms etc.
1, download TWRP recovery img.tar.
2,download supersu.zip
3,open odin go to options and "uncheck" autoreboot.
4,choose AP tab in odin and upload TWRP recovery.
5,go to device download mode and connect to pc via usb cable.
6,HIT START in odin once odin shows pass remove battery from device.(DO NOT REBOOT YOUR DEVICE)
7,insert battery again and boot into TWRP recovery by pressing (volume up+home+power button)
8,go to install and flash supersu.zip and reboot.
Your device may reboot twice so dont worry its normal
Enjoy root.
TWRP RECOVERY LINK
https://dl.twrp.me/trltecan/twrp-3.0.2-0-trltecan.img.tar.html
SUPERSU.ZIP LATEST
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
Thanks for the help! I tried that though and now it's just hanging at the Downloading screen again. Going to give it another five minutes but I really hope I'm not ruining it.
<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> recovery.img
Click to expand...
Click to collapse
EDIT: Nothing's happened. Trying with latest RV of ODIN
Tried with the latest version of ODIN. Nothing
can the w8 be rooted?
Reviving an old thread? Yes, W8 can be rooted. I did had similar problem with rooting my W8, but I fixed it using similar steps as Trex outlined above.
If you're still having problems, check and make "lock re-activation" is off. "usb debugging" is on.
HappyPlato said:
Reviving an old thread? Yes, W8 can be rooted. I did had similar problem with rooting my W8, but I fixed it using similar steps as Trex outlined above.
If you're still having problems, check and make "lock re-activation" is off. "usb debugging" is on.
Click to expand...
Click to collapse
Know any way to revive via sd card? I hear it's possible.
Sent from my Samsung SM-N900T using XDA Labs