NOTE: I'M STILL ON 4.2.2
So I've already rooted my device using motochopper and had no issues, but now I'm trying to install a custom recovery to no luck. I prefer TWRP but every time I try to install via Odin it fails with this message:
<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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've installed the latest drivers and ran ODIN as admin. I tried an older version of TWRP and even ODIN but end with the same result.
When I try via GooManager, it finds the correct version and takes me to the download page, but after the countdown it never downloads and eventually times out.
So then I decided to go CWM via RomManager. It found the correct CWM recovery image and said the install was successful, but when I try to boot into recovery I get the standard Android recover screen with "reboot system" etc.. with the little Android robot with a red triangle coming out of him.
Every method I've tried is failing and I can't figure out why
h_smith said:
NOTE: I'M STILL ON 4.2.2
So I've already rooted my device using motochopper and had no issues, but now I'm trying to install a custom recovery to no luck. I prefer TWRP but every time I try to install via Odin it fails with this message:
<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> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I've installed the latest drivers and ran ODIN as admin. I tried an older version of TWRP and even ODIN but end with the same result.
When I try via GooManager, it finds the correct version and takes me to the download page, but after the countdown it never downloads and eventually times out.
So then I decided to go CWM via RomManager. It found the correct CWM recovery image and said the install was successful, but when I try to boot into recovery I get the standard Android recover screen with "reboot system" etc.. with the little Android robot with a red triangle coming out of him.
Every method I've tried is failing and I can't figure out why
Click to expand...
Click to collapse
I'm assuming you are AT&T SGH-i337?
If so, are you using the LOKI'd versions?
If you don't know what that means, I suggest you do a search and some reading.
If you know what it means and have used the correct version, may be someone else can help.
Sounds like nothing is able to write to the recovery partition. You might consider flashing the stock firmware with odin and starting over.
jd1639 said:
Sounds like nothing is able to write to the recovery partition. You might consider flashing the stock firmware with odin and starting over.
Click to expand...
Click to collapse
so is there something wrong I may have done to cause this? I wish GooManager would just download and install as I've had luck using it in the past but it won't for some reason.
scott14719 said:
I'm assuming you are AT&T SGH-i337?
If so, are you using the LOKI'd versions?
If you don't know what that means, I suggest you do a search and some reading.
If you know what it means and have used the correct version, may be someone else can help.
Click to expand...
Click to collapse
Yes I'm on the AT&T version. I got the LOKI files from here
What baseband?
Sent from my i337 MF3 using tapatalk.
I'm not sure how much damage you have already done to your recovery partition so you made need to ODIN AMDL stock onto your phone before anything will work. However, here is the TWRP page for this device that also gives instructions on how to install via ADB or Terminal Emulator. Make sure you read EVERYTHING!
http://www.teamw.in/project/twrp2/174
Once you get TWRP working, you can flash a compatible version of CWM if you want to.
For future reference NEVER do anything to your phone that you don't read about here on XDA or at least see that people on XDA have tried it and verified it to work. Most sites (I'm not positive about the one you linked) just copy the information from XDA and claim it is there own. Usually, screwing it up some how. So never trust anything outside of XDA or that isn't directly linked to XDA. An example of something to trust is with the TWRP site. You can trust it as long as you make sure you have the correct information and version for your phone. That is your responsibility.
Also, make sure you search and read before asking questions or advice. Most information is already posted and you need to read about everything you are trying to do to your phone. If you follow these guidelines, you should do OK. If you try to cut corners or not search and read, you will end up in a mess. Good luck.
Related
Hey Everyone! So long story short, I ended up picking up a 8.9 tab and now we have a 100% confirmed working ClockworkMod Recovery!
So, quick and dirty instructions for users WITHOUT any form of CWM recovery on their device:
1) Download the attached ClockworkMod_Recovery_v5.5.0.4.tar
2) Reboot the tab into download mode
3) Fire up Odin 1.85 and put the ClockworkMod_Recovery_v5.5.0.4.tar in the PDA field.
4) Flash!
5) Reboot into ClockworkMod Recovery
Quick and dirty instructions for users WITH some form of CWM recovery on their device:
1) Download the attached ClockworkMod_Recovery_v5.5.0.4.zip to your device
2) Reboot the tab into recovery
3) Install the zip
5) Reboot
If, for any reason, you want to return to the stock recovery, simply download the P73xx_Stock_Recovery.tar and follow the instructions above (with odin)!
DISCLAIMER: THIS WILL NOT WORK WITH LTE TABS!
I kinda "bricked" my tab yesterday trying to create a recovery.
Now it just continually boots to the splash screen then restarts.
I can not get into recovery.
I can get into download.
I tried the ClockworkMod Recovery v5.0.2.6 but odin just hangs after setup connection.
Trying to download the stock recovery:
<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>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Any ideas?
Thanks,
-dana
Thankfully Samsung devices are notoriously hard to brick
So is the tab still booting into the OS? Or are you ONLY able to get to download mode?
Also, what did you do to try and create a recovery and what did you flash? If I can understand what has been done I can help you get up and running again
As for Odin hanging at "Setup Connection" when you tried to flash my recovery, it is likely just coincidence more than anything. Odin isn't the most dependable application...well, it is and it isn't...but getting stuck at Setup Connection is a common issue.
First tell me what you did yesterday so we can figure out how to proceed. Then we'll go from there!
I kinda want to volunteer as I am familiar with ODIN coming from a Vibrant but what's stopping me is 3 questions with all due respect. What's the related thread you were talking about at the OP? Are you sure that is the right 8.9 Stock Recovery? How did you find it as there is (at least) no American ODIN image as of today (checked Samfirmware as of this post)?
nirogu325 said:
I kinda want to volunteer as I am familiar with ODIN coming from a Vibrant but what's stopping me is 3 questions with all due respect. What's the related thread you were talking about at the OP? Are you sure that is the right 8.9 Stock Recovery? How did you find it as there is (at least) no American ODIN image as of today (checked Samfirmware as of this post)?
Click to expand...
Click to collapse
Excellent -
This is the thread I was talking about in 10.1 section:
http://forum.xda-developers.com/showthread.php?t=1307242
The recovery is standard, regardless of region. In fact, with the exception of precompiled binary modules, the recovery is even identical to that of the 10.1 tab
What I have done here is repacked the recovery image with a vanilla build of clockworkmod. This should work on both the P7300 and the P7310.
Give it a shot and let me know how it goes!
Neither got flashed via ODIN, but I too tried to install CWM yesterday via the market app so my recovery is messed up to start with.
After trying to flash the two the tab wouldn't boot and I got an error about a failed update.
Flashed the bootloader file below with ODIN to get it to boot.
Code:
ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> recovery.img
<ID:0/010> NAND Write Start!!
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Hmm ok...
So yesterday you tried the market CWM, which caused the tab not to boot at all? Then, you had to flash the bootloader to make it boot again?
I'm assuming you had a booting tab prior to trying to flash these files, but still had the borked recovery yes?
That is correct, but the recovery was fine when i got the device, I used it to root.
I know I should do a full flash but I don't want to lose all my stuff.
Also flahing the bootloader somehow removed the cwm ?script? That was forcing the tab to try and boot into the borked recovery on each boot.
Damn that app does a number on the poor tab...unfortunately the best course of action is really to completely restock the thing - flash an entire rom through Odin with a repartition.
Since you are able to boot, you can back up all your data with Titanium backup, then move the data off your internal storage and onto your computer in case it gets wiped by the Odin flash.
Now i really wish I had an 8.9 because I'm curious if someone who hasn't got the messed up recovery tries to flash my file if it will go through or fail like yours and the Geologist.
Any takers?
alterbridge86 said:
Now i really wish I had an 8.9 because I'm curious if someone who hasn't got the messed up recovery tries to flash my file if it will go through or fail like yours and the Geologist.
Any takers?
Click to expand...
Click to collapse
That'd be me. Once I backup my apps, I will (give me some minutes and I will post the result as an EDIT post). If it fails, worst case scenario would be flashing the Asian ODIN image since it is the only one available. That one displays everything in Chinese but I can change the language. Sidenote: Damn I wonder what is taking so long to bring an American ODIN image of the 7310 live???
nirogu325 said:
That'd be me. Once I backup my apps, I will (give me some minutes and I will post the result as an EDIT post). If it fails, worst case scenario would be flashing the Asian ODIN image since it is the only one available. That one displays everything in Chinese but I can change the language. Sidenote: Damn I wonder what is taking so long to bring an American ODIN image of the 7310 live???
Click to expand...
Click to collapse
Excellent! Let me know how it goes!
alterbridge86 said:
Excellent! Let me know how it goes!
Click to expand...
Click to collapse
It does not flash. This is what ODIN shows after following instructions:
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
<ID:0/010> Initialzation..
<ID:0/010> Get PIT for mapping..
<ID:0/010> Firmware update start..
<ID:0/010> recovery.img
<ID:0/010> NAND Write Start!!
<ID:0/010>
<ID:0/010> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
EDIT: Oh well...it's been a while since I last saw a "device-!-PC" screen.
EDIT 2: The "device-!-PC" screen vanished after one or two restarts as if nothing ever happened.
That's really weird, because I can even flash the p73xx stock recovery on my 10.1 tab and it at least goes through...it won't boot into recovery, as expected, but it at least FLASHES...
Maybe next question - are you guys using Odin 1.85? Also, are you using the driver from Kies or did you install a standalone driver? Try installing this driver:
http://www.multiupload.com/ISBTL9TADO
And then flashing after. It also may be worthwhile to switch USB ports after installing the new driver. Don't mind the p7510 in the file name, it works with multiple devices.
alterbridge86 said:
That's really weird, because I can even flash the p73xx stock recovery on my 10.1 tab and it at least goes through...it won't boot into recovery, as expected, but it at least FLASHES...
Maybe next question - are you guys using Odin 1.85? Also, are you using the driver from Kies or did you install a standalone driver? Try installing this driver:
http://www.multiupload.com/ISBTL9TADO
And then flashing after. It also may be worthwhile to switch USB ports after installing the new driver. Don't mind the p7510 in the file name, it works with multiple devices.
Click to expand...
Click to collapse
Yes, ODIN 1.85. Will install that driver and see how it goes.
EDIT: Same result as pointed earlier, even after installing the quoted driver and changing USB ports.
EDIT 2: Wait a second. I think I might have figured it out. This does not work on an encrypted system, right? I think I'll unencrypt and then try doing this.
EDIT 3: Nope, unencrypted or not, it does not flash. Same result.
Sent from my GT-P7310
Well, I have good news and bad news...lol
I was strolling through best buy this evening after dinner and made an impulse purchase...i'm now the new owner of a Galaxy Tab 8.9
EDIT (10/22/11): We're back open! Confirmed working STOCK recovery is in first post...confirmed working CWM recovery coming momentarily
EDIT 2 (10/22/11): And we're official. ClockworkMod is 100% working Enjoy guys!
Now on to my next project...making this thing FASTER
Confirmed working CWM-Recovery . Doing a NANDROID backup as of this post.
Working great, thanks.
Sent from my GT-P7310 using Tapatalk
Works perfectly on my gtab P7300 and ki1 rom.
Thanks for your job !
Now, wait noTW rom !
work perfectly on my gtab P7300 asia
AWeSOME
Thanks, working perfectly on my gtab 7300 as well. So glad you are one of us now, looking forward for your overcome roms
Hey guys, I'm having a little trouble getting custom roms installed on my Galaxy S4. Here is a little information about the phone
Carrier: ATT
Model: Galaxy SGH - 1337
Android version 4.2.2
After spending a few hours here on XDA both searching the site and posting on the help thread, I've come to no solution.
So yesterday due to a level of frustration with the amount of bloat that comes pre-installed on the Samsung devices, I decided I would try to set up a custom rom. I've used the Towelroot site to root the device (enable superuser access and disable Knox,) But wasn't able to install CWM. I've downloaded and installed the CWM Rom Manager and inside that app is an option to install CWM manually. Of course it isn't that easy, because although it says it's installed the recovery, when I boot into recover mode, it is still the stock android recovery mode.
So I turned to Odin. Specifically Odin 3.09. This is where the problems start. I start my phone and enable download mode. The phone is recognized by Odin and I choose the CWM file I have (recover-clockwork-touch-6.0.4.4-jflteatt.tar.) I press start and the process begins, but before long I see FAIL! in red at the top
The message box reads as follows:
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<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)
<ID:0/003> Removed!!
I've tried using three different usb cables (including the stock s4 cable included in the packaging) and several different ports of course to no avail.
What exactly does FAIL! (Auth) mean? That seems to be the point where it goes south. I've tried other Odin versions and gotten more or less the same result.
Could I be flashing a bad file? Is the CWM.tar not the correct file to flash?
Anyways if anyone has a fix to this particular solution then let me know. Otherwise I'll take really any other viable solution to enabling custom roms on the Galaxy S4 for ATT. I'd like this to be a thread that people see when they google search it, so I won't give up and I'll be sure to post with the best process that I can find!
I think u maybe flashing a bad file or maybe ur choosing wrong option in Odin to flash the recovery, what option did u choose? and also check in the att s4 section as this is not the right forum for ur phone model
Sent from my GT-I9505 using XDA Premium 4 mobile app
dorian2kx said:
I think u maybe flashing a bad file or maybe ur choosing wrong option in Odin to flash the recovery, what option did u choose? and also check in the att s4 section as this is not the right forum for ur phone model
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Odin PDA loader and then start. Very simple it seems. I didn't see any particular ATT s4 section but maybe a mod could move me over?
Alright stop what you are doing. Want to kill your phone? Keep going like this.
The stuff you try to flash is NOT for you phone. You don't have an i9505 or an i9500. You have an at&t phone. That's a completely different section on xda.
You need to be in this section.
http://forum.xda-developers.com/galaxy-s4-att/general
You probably need to look for unlocking your bootloader. But I would suggest reading and understanding everything before you do anything like this again. If you want to kill your phone this is the way to do it.
I'm pretty new to this, and managed to root my AT&T galaxy s4 i337 recently, using a guide I found here (it won't let me post the link).
From what I can tell, it didn't give me a custom recovery. Booting into recovery mode gives me the stock recovery. Now, I'd like to try paranoid android or cyanogenmod, but so far I've tried several guides and apps/tools and none has worked.
I've tried installing the clockwork mod app, and although it told me it's successfully installed, when I reboot into the clockwork recovery, it instead takes me to the stock recovery.
I've tried flashing the new AP with Philz touch using Odin3, but each time it fails on auth:
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> SingleDownload.
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I tried copying the paranoid android rom to my SD card, and installing it via the stock recovery but all it seems to have done is reset my phone to stock. All the samsung bloatware is back.
If anyone could tell me what I'm doing wrong, or how to get around this I'd really appreciate it. Ideally I'd like to end up with a custom recovery, and either PA or CM on there. I believe the phone is still rooted.
thanks very much for any help.
http://forum.xda-developers.com/galaxy-s4-att is where you want to go, as there are far more people on that forum that can help you with your issue than we can. This is the international S4 forum. Your device has a locked bootloader, meaning you cannot install a custom recovery or a custom ROM to the device's system areas. To get a custom ROM on your device requires a different process, which the link provided can assist you with.
Ah, thank you very much for pointing me in the right direction.
I pulled out my old Verizon Galaxy S4 with the intention of getting a ROM on it that had XPosed. After some Googling, saw KingRoot supported it, so I used that app to root it. Then I tried to get TWRP installed. Their website said you could do it from their TWRP Manager app, so I tried that. It *said* it succeeded, but after that, my phone couldn't even boot at all.
So then I read up on using Odin to fix it. I tried to flash TWRP recovery from Odin (even finding a .tar version was a PITA), but I got this:
Code:
<ID:0/006> Removed!!
<ID:0/006> Added!!
<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> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
Now, it boots normally, but I can't get into Recovery any more.
All I really want to do is get some custom recovery on there. Or even back to normal at this point. But I don't know how. I also tried flashing Clockwork Mod, but that didn't improve anything. What should I be doing now? Go back to stock and start over? Or am I installing the wrong recoveries from Odin (the TWRP one wasn't on their official download page, they only have .img files there, not tars). Or what?
Your first mistake was that you used Kingoroot. CF-Autoroot should be supported on your S4. As to the recovery, you want the latest version of TWRP, here. Download the 3.0.2-0 tarball (.tar), open Odin, select the PDA slot and point Odin to the tarball, then flash. That should resolve your recovery woes.
Make sure your TWRP is for that phone model. Verizon phones have locked bootloaders which make modifications harder.
Since the OP installed Clockworkmod, I have to assume his bootloader is one of the ones that can be exploited. But a good point, and I edited the link in my last post accordingly.
Strephon Alkhalikoi said:
Your first mistake was that you used Kingoroot. CF-Autoroot should be supported on your S4. As to the recovery, you want the latest version of TWRP, here. Download the 3.0.2-0 tarball (.tar), open Odin, select the PDA slot and point Odin to the tarball, then flash. That should resolve your recovery woes.
Click to expand...
Click to collapse
That link doesn't have any tarballs. Only image files. I couldn't find the tars on their site at all, and the only one I could find was one someone had as an attachment in a thread. No clue if it's the right one, though.
Strephon Alkhalikoi said:
Since the OP installed Clockworkmod, I have to assume his bootloader is one of the ones that can be exploited. But a good point, and I edited the link in my last post accordingly.
Click to expand...
Click to collapse
I tried to install Clockwork Mod, but it didn't work. I got the fail message above when trying to install the tar via Odin, and when I tried to use their app, it did the same thing the TWRP Management app did - it said it succeeded, but now I can't boot into recovery.
Do not install Clockworkmod. It's no longer maintained and has problems with more current ROMs. Install TWRP using that tarball you found on the forums. I believe TWRP on Verizon has no tarballs as it's expected to be installed using the TWRP Manager or a similar app in the Play Store.
If this does not work, you may have to start from scratch. Hopefully you kept a copy of the ROM with the exploitable bootloader so you can reinstall if necessary.
Hey everyone,
This guide should make it very easy for anyone to root and install a custom recovery (TWRP) on basically almost any S6 variant. You've got all the download links in the video description as well.
It works on all Android 7.0 stock versions, including the latest ones (with the most recent security patches).
Everything is very clearly explained, with step-by-step instructions in the video below. Just make sure you download the correct TWRP tar file for your S6 variant.
https://youtu.be/BV1ELmu8T0I
Enjoy!
Here is just the same but in really short (because that isn't so complicated) And here are also useful links to get latest drivers, stock firmware, ROOT, TWRP etc.
rifek4 said:
http://cdn.droidviews.com/wp-content/uploads/2015/03/Odin3_v3.12.7.zip Odin 3.12.7 (latest)
https://forum.xda-developers.com/galaxy-tab-s/general/tool-samfirm-samsung-firmware-t2988647 SamFirm 0.3.6 (latest)
http://samsung-usb-driver-for-mobile-phones.en.lo4d.com/download Samsung USB Drivers 1.5.63 (latest)
Install latest USB drivers, unpack lastest Odin3 and SamFirm. Use SamFirm to download latest firmware for your model, so put "SM-G920F" in "model" check "Auto" under that, put CSC code for your country in "Region", download it and then just flash it in Odin
Here you got full CSC codes list and also short guide how to use SamFirm
https://www.androidsage.com/2017/07...specific-product-code-csc-and-country-region/
How to root then? > CF-Auto-Root
How to get TWRP then? > latest TWRP
Customize? > Look my signature
Click to expand...
Click to collapse
rifek4 said:
Here is just the same but in really short (because that isn't so complicated) And here are also useful links to get latest drivers, stock firmware, ROOT, TWRP etc.
Click to expand...
Click to collapse
Thank you so much for responding, but unfortunately l it does not have my version which is the (SM-S906L/TFN) variant it works but straight talk but when I booted it up it said Tracfone so the region I put TFN and the model number (SM-S906L) and I can't find it. I have the firmware for my phone so as this is much not a problem. What is a problem is when I do flash the stock firmware in odin is that i run into sboot.fail and cm.bin fail, and the only way is to delete them from the .tar file and rezipping them into another .tar without the sboot/cm.bin, and NO matter what I flash either if is a successful rom flash in twrp or what I just said in odin I ALWAYS come back to a boot loop. I'm starting to think my phone is dead idk what to do.
Error: <ID:0/004> Odin engine v(ID:3.1101)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/004> Odin engine v(ID:3.1101)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> sboot.bin
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL!
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Halp
I hate to ask, but i've been going over every post i can find in the forums, including this one, and i think i am scared to ask this but.......Does this not work for the G920V Verizon variant? i keep looking everywhere online but it seems like none of these methods work for that Variant, but no one has said that it wont work on that one specifically, was hoping maybe you can confirm or deny if it works on the Verizon variant? thank you in advance.
KNOX
How about KNOX? Will it flip the flag?
rifek4 said:
Use search option or Google is your friend.
Click to expand...
Click to collapse
Looks like you're the one who can't read. He clearly stated that he read everything he could find and all he got was conflicting information. If you don't have the answer, don't post anything. If you have the answer and can set the record straight, then please do. Thanks.
rifek4 said:
I answered on same question for few times before, and I won't do it any more because I don't like to repeating my self. Answer on he's question is in thousends places on that forum, if he only would to like use "Search Option" here little bit above on right corner, and type there "ROOT S6 Verizon" or just "ROOT G920V" he will have answer for him question even confirmed not once! My first shoot in search engine, that thread : https://forum.xda-developers.com/ga...-auto-root-t3056630/post73993971#post73993971
For example here on few last pages is many posts with answer to him.
P.S.
Please don't let me starting next time.
Click to expand...
Click to collapse
Is this what you call an answer?
---------------------------
Quote:
Originally Posted by NizzoFoShizzo
I thought SM-G925V verizon model doesn't allow this method because it doesn't have the oem unlocking option in the developer options.
Just flash CF-Auto-Root for your model (is avaiable), then you can easy flash also TWRP without problems with OEM Unlocking. After that do all what you want
---------------------------
Because I'm quite sure you're wrong. Just because there's a CF-Auto-Root image for the device for a particular build number, it doesn't mean it's gonna get past the locked bootloader. I got CF-Auto-Root from here https://desktop.firmware.mobi/device:841/firmware:2970 for my G920V 6.0.1 build CPK2. Tried to flash with Odin, and it failed right away. On the device, on the downloading screen, it says "Secure Download : Enabled", and once I try to flash, it says "SECURE CHECK FAIL: (RECOVERY)".
Also, the CF-Auto-Root README.txt clearly says: "Your device must have: - An unlocked bootloader, - OEM unlock enabled (if present) in developer options, - Factory reset protection (if present) disabled".
I was going to write a long post about all the things I tried on the Verizon phone that din't work, including mihaixp and rifek4's suggestions (things that worked fine on G920F), so I'll just say: "No, there is no root for Verizon phones", and leave you with this: https://forum.xda-developers.com/verizon-galaxy-s6/help/current-root-method-verizon-s6-t3647371
rifek4 said:
Here is just the same but in really short (because that isn't so complicated) And here are also useful links to get latest drivers, stock firmware, ROOT, TWRP etc.
Click to expand...
Click to collapse
Plz Guyz Help!
I just installed twrp in my SM-G925l & directly boot into recovery , after that i did factory reset, advanced wipe(dalvik/ART cache, system, data, internal storage, cache) and than i was going copy the Rom Files via MTP but it says "can't copy files, the Device either disconnected or stopped responding" .
I don't have a external usb drive so can't try that.
Plz guyz, help. What to do now.
rifek4 said:
Yes... So true... For G920V with 6.0/7.0 I think isn't any avaiable way to ROOT. I never had Verizon and never looking for any post with informations about it, but from that what I know possible was S6 Verizon (G920V) ROOT but on Lollipop (5.1.1) ROM's only.
Click to expand...
Click to collapse
and yet here you just answered the simple question i asked in the first post you replied to, so thank you , but even though you say this, other posts seem to make me believe it is possible.
But just in case, here is what i have tried so far, maybe some other option i am not seeing in my searching has come up that you might know?
First i was trying to root via the method mentioned here....http://rootmygalaxy.net/root-samsung-galaxy-devices-using-cf-auto-root-odin-tool/
This method kept failing me however on the first box, not the green pass as is expected. I also in my searching found this thread about locked bootloaders... (crap my window crashed with the link and now i can't seem to find it, grr) anyways, there was talk of unlocking the bootloader to solve the problem....which lead me to this thread...https://forum.xda-developers.com/verizon-galaxy-s6/general/root-nougat-s6-verizon-t3710864
And i used that method, and everything went and worked as expected however i did not achieve the SuperSU that i expected to see int he app drawer in the end, so something didn;t work.
which lead me to this thread...https://forum.xda-developers.com/ve...20vvrs4dqd1-odin-nougat-7-0-firmware-t3597007 to get myself the firmware needed for this method here...https://forum.xda-developers.com/ga...-auto-root-t3056630/post73993971#post73993971 and this post ...https://androidmtk.com/root-samsung-galaxy-s6-sm-g920v which was again just the CF Auto Root that failed the first time around.
So i feel like a giant game of round robin here.
I really don't want to drop to a lower version of Android to root the unit (and i also feel it really wouldn't matter what version at this point) but if that is my only option i might just try it, but so i kindly ask again, after clearly using the search function on the forum to look for methods, has anyone had luck with the Verizon variant S6 920V on Nougat getting root to stick and if so, can you please point me to the method you used on the forums, because all the methods i keep finding circle back to the CF Auto method that keeps failing time and time again. Thank you in advance.
So will this be triggering KNOX or not?
Could anyone please tell me whether Knox will be triggered or not
Hello, I tried this method, everything was OK, i got pass in ODIN app, then tried to reboot and now nothing is happening, i think device is bricked, but I made everything as you have described in video. Now when I try to hold volume UP + home + lock buttons, galaxy s6 logo pops up, the side buttons just flash and nothing happens. Could you please, help me?
Edit: I can enter download mode
Edit2: false alarm, I just installed wrong TWRP