i search a Root for the Samsung Galaxy Tab S5e SM-T725 , for install a Mod PlayStore .....
Are you asking if there is root for the Tab 5se yet?
yes ... is there a root for the tab S5e?
Yes, there is root for the S5e, it is complicated atm...
https://forum.xda-developers.com/galaxy-s10/development/magisk-root-galaxy-s10-series-t3918699
DerZero said:
yes ... is there a root for the tab S5e?
Click to expand...
Click to collapse
I do not understand. how can I ROOT the Galaxy Tab S5e (SM-T725)?
DerZero said:
I do not understand. how can I ROOT the Galaxy Tab S5e (SM-T725)?
Click to expand...
Click to collapse
I have not tried it yet...don't have a lot of time atm. Basically you will need to enable developer mode first to unlock the bootloader your device, the OEM unlock may not appear for 24 hours or more. Once you do that, follow the instructions from this website:
https://topjohnwu.github.io/Magisk/samsung
More or less it is the same, except we don't have a Bixby button. You'll need to hold Volume Up and Volume Down together to boot into download mode. Make sure you practice booting into the various modes first.
nsx2brz said:
I have not tried it yet...don't have a lot of time atm. Basically you will need to enable developer mode first to unlock the bootloader your device, the OEM unlock may not appear for 24 hours or more. Once you do that, follow the instructions from this website:
https://topjohnwu.github.io/Magisk/samsung
More or less it is the same, except we don't have a Bixby button. You'll need to hold Volume Up and Volume Down together to boot into download mode. Make sure you practice booting into the various modes first.
Click to expand...
Click to collapse
I'm going to attempt this within the next 24 hours. My CSC value is XAA (and I can't locate XAA firmware as of yet) but the latest available is KOO (Korean) with a build date of Thu, 25 Apr 2019. I'm actually quite happy with the device's overall performance but, you know, curiosity.
AHE_XDA said:
I'm going to attempt this within the next 24 hours. My CSC value is XAA (and I can't locate XAA firmware as of yet) but the latest available is KOO (Korean) with a build date of Thu, 25 Apr 2019. I'm actually quite happy with the device's overall performance but, you know, curiosity.
Click to expand...
Click to collapse
A few caveats with XAA:
For 'OEM Unlock' to show, you must be connected to WiFi to unlock the Bootloader.
And if you 'Factory Reset' after unlocking it, it disappears completely.
If you change the date, time or year, it doesn't return until you reconnect to WiFi.
Interesting, just got mine today tempted to try this.
---------- Post added at 12:56 AM ---------- Previous post was at 12:52 AM ----------
AHE_XDA said:
I'm going to attempt this within the next 24 hours. My CSC value is XAA (and I can't locate XAA firmware as of yet) but the latest available is KOO (Korean) with a build date of Thu, 25 Apr 2019. I'm actually quite happy with the device's overall performance but, you know, curiosity.
Click to expand...
Click to collapse
Please let us know how it went!
I've managed to unlock the bootloader.
I'll post a few pictures in a moment.
Note: This is for the SM-T720.
AHE_XDA said:
I've managed to unlock the bootloader.
I'll post a few pictures in a moment.
Note: This is for the SM-T720.
Click to expand...
Click to collapse
-----
I've patched the AP file but keeps failing when Odin attempts to write 'Modem':
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 5505 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> system.img.ext4
<ID:0/003> dtbo.img
<ID:0/003> vendor.img.ext4
<ID:0/003> persist.img.ext4
<ID:0/003> userdata.img.ext4
<ID:0/003> vbmeta.img
<ID:0/003> modem.bin
<ID:0/003> FAIL! (Auth)
For those curious; I'm on the latest version of Odin and running stock XAC firmware.
That said, I'm finished trying for now. Perhaps when there are more active participants, we can collaborate.
But I have the 6GB/128GB combination and, for what I use it for, root isn't that essential (just merely a curiosity). The device, with its eMMC storage and mid-range CPU, does really impress me. I've been able to use it as a very competent laptop replacement with DEX and One UI, once you use the Android Studio to uninstall some unnecessary bloat, is night and day from what Samsung use to offer just a couple years back.
Try removing every file from the tar except for boot.img, recovery.img, and vbmeta. That is what worked for PewPewK when he rooted his in another thread. I built my magisk_patched.tar with these 3 files, haven't tried flashing them yet...
AHE_XDA said:
-----
I've patched the AP file but keeps failing when Odin attempts to write 'Modem':
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1301)..
<ID:0/003> File analysis..
<ID:0/003> Total Binary size: 5505 M
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> NAND Write Start!!
<ID:0/003> SingleDownload.
<ID:0/003> system.img.ext4
<ID:0/003> dtbo.img
<ID:0/003> vendor.img.ext4
<ID:0/003> persist.img.ext4
<ID:0/003> userdata.img.ext4
<ID:0/003> vbmeta.img
<ID:0/003> modem.bin
<ID:0/003> FAIL! (Auth)
For those curious; I'm on the latest version of Odin and running stock XAC firmware.
That said, I'm finished trying for now. Perhaps when there are more active participants, we can collaborate.
But I have the 6GB/128GB combination and, for what I use it for, root isn't that essential (just merely a curiosity). The device, with its eMMC storage and mid-range CPU, does really impress me. I've been able to use it as a very competent laptop replacement with DEX and One UI, once you use the Android Studio to uninstall some unnecessary bloat, is night and day from what Samsung use to offer just a couple years back.
Click to expand...
Click to collapse
nsx2brz said:
Try removing every file from the tar except for boot.img, recovery.img, and vbmeta. That is what worked for PewPewK when he rooted his in another thread. I built my magisk_patched.tar with these 3 files, haven't tried flashing them yet...
Click to expand...
Click to collapse
Do you happen to have the URL for the thread?
I'm apt to try this again in a week or two.
best would be a root of CF-AUTOROOT or a TWR and a ROOT.ZIP -.-
https://forum.xda-developers.com/ga...ragon-root-waiting-discussion-t3919024/page24
Post #235 is where is says what worked. Good luck! I probably won't have time to try mine until next month.
AHE_XDA said:
Do you happen to have the URL for the thread?
I'm apt to try this again in a week or two.
Click to expand...
Click to collapse
I have Magisk working on my Tab S5e (have had it working since the day after it launched). I was going to post instructions, but we still don't have a Tab S5e forum to post em in.
PewPewK said:
I have Magisk working on my Tab S5e (have had it working since the day after it launched). I was going to post instructions, but we still don't have a Tab S5e forum to post em in.
Click to expand...
Click to collapse
Any chance you can post it here? Or share via pm? I'd be really interested in root so I can do some debloat.
btonetbone said:
Any chance you can post it here? Or share via pm? I'd be really interested in root so I can do some debloat.
Click to expand...
Click to collapse
Yeah, sure. I wrote this in an e-mail to someone who messaged me regarding rooting the Tab S5e, but it's a tad bit old. Regardless, I'll paste it verbatim here:
Because my installation process was hardly linear (I ran into many problems along the way), I can't guarantee that these are exclusively the exact steps you would need to take to get it working. But I think this should be a compilation of all the final (working-ish) steps I took.
(1) Setup tablet for first time, go to settings, enable developer mode, and flick the OEM Unlocking switch.
(2) Turn off the Tab S5e and boot into Download Mode by holding Power and Vol Up + Vol Down. Then hold up on the Vol Up button (not just a quick press) as it says to enter Bootloader Unlocking Mode. Follow the instructions there to fully unlock the bootloader.
(3) The tablet will be formatted at this step. After the bootloader is fully unlocked, make sure you boot back into the Tab S5e and perform the set up again. Enable developer options and make sure that the OEM Unlocking switch is turned on. Yes, again. This step is necessary apparently due to some changes Samsung made with their new VaultKeeper service? If you don't you may soft brick the device.
(4) Install @ianmacd's Magisk Manager application on your Tab S5e. Download is here. [Update: TopJonWu's official Magisk build should now work fine.]
(5) Download the latest Tab S5e firmware build. I found my copy here. Extract from it the AP file. Transfer this file to your Tab S5e.
(6) Back in Magisk Manager, go to settings and look for "Update Channel." Here's where I'm a little uncertain of what I did that finally got it to work, so I'll recommend two steps...
(7a) Select the ianmacd update channel and return to the home screen of Magisk. [Update: This shouldn't be necessary anymore, especially if you installed the official Magisk Manager earlier.] Click install, then choose the patch file option. Locate the AP file you transferred earlier and wait for it to finish creating a "magisk_patched.tar" file. Transfer this file to your computer and rename it "magisk_patched_ianmacd.tar," then delete the old magisk_patched on your device.
(7b) Do the same for the Canary (debug) update channel. Patch the AP again, and locate the patched file, copy it to your computer, and rename it to something clear.
(8) This is an odd step I had to follow to avoid errors flashing. It turns out of the several times I tried making the patched images, I almost always inevitably had some file in the archives getting corrupted. So open up both magisk_patched.tar's and test them for errors. I did this in 7-Zip, but there's probably ways to do it in WinRAR, too. If it gives you any error, take a note of which file it failed on because that guarantees your flashing will fail in later steps. In fact, the reason I recommended doing two different methods for patching magisk above was because the first ianmacd patch I tried had a corrupt recovery.img. What I ended up doing to fix it was extracting a working (non-error checking) recovery.img, vbmeta.img, and boot.img from the two different patched Magisks and then recombined them myself into my own Magisk tar. I also kept the meta-inf folder in there for good measure, though I don't think it's necessary? So in the end, I had what I called a "magisk_patched_lite.tar" that contained exactly three images: recovery.img, vbmeta.img, and boot.img, along with the meta-inf folder and ensured 7-Zip did not return any errors on the archive.
(9) Reboot the tablet to Download Mode. Press Vol Up to start. Attach the Tab S5e to your computer, and start Odin (I used v3.13.1_3B_PatcheD).
(10) Put some working archive of the patched magisk in the AP slot and uncheck "Auto Reboot." I don't know if the 'lite' version is sufficient for your first flash, but I suspect that it is (it would not be sufficient if you're pre-patching an updated firmware for the Tab S5e). Let Odin rip and see if you get any errors.
(11) Assuming Odin was successful, hold Power and Vol Down to exit Download Mode, then immediately switch to Power and Vol Up once the screen shuts off. Continue holding these until you are greeted with Recovery mode.
(12) Use the volume keys to select Factory Reset/Wipe Data. Execute that to make sure the tablet is properly formatted.
(13) Use the reboot into system option at the top of recovery. Hold Power and Vol Up until the "Bootloader is Unlocked" warning screen shows up, then release.
(14) If you're lucky, you should eventually see a red warning message about not having Samsung software installed. That's a good sign. My tablet fumbled around these steps and looked like it was gonna bootloop for a while? But eventually, it ran its course and booted.
(15) You hopefully have root installed now. Set up the tablet one last time, install the ianmacd Magisk Manager again and open it up. If it says Magisk is installed, great job, otherwise... I don't know where the issue is because this rooting sequence is way more complicated than for other devices! At some point, I think after a reboot, Magisk Manager asked if it could do some additional setup stuff. Obviously let it do that.
Click to expand...
Click to collapse
I updated a few steps that have changed since writing that up originally. Since the Tab S5e hasn't seen a software update yet, I'll also upload my (hopefully) working copy of the flashable patched_magisk_boot.tar that you can flash in the AP slot in Odin. No guarantees it works, but I can't imagine why it wouldn't. In theory, you should be able to skip several steps above and simply OEM (bootloader) unlock the device, then flash this in Odin.
Also important! Fundmentally, this version of root works very differently from what you may be used to. See here for detailed information. Normally root is installed onto the boot partition, but Samsung did some ****y stuff this generation to be "compliant" with Google's new rules, but still do things in their own special way, so now to achieve root Magisk has to live on the recovery partition.
Magisk living on the recovery partition means that in order to boot with Magisk enabled, you have to boot into recovery. So to boot with root, hold power and vol up until you see the "bootloader is unlocked" warning screen, then release. If you hold Vol Up, you will be taken to recovery, which will boot the system partition with root enabled. Otherwise, your tablet will boot the system partition without root. So if you do not do this step, root will not work (i.e. you'll boot into system without Magisk).
Hope this helps you achieve root.
Great Instructions.
The only other trick to keep in mind, is you have to hold up and power EVERY TIME you boot. If you don't, it'll come up in not root mode.
PewPewK said:
Yeah, sure. I wrote this in an e-mail to someone who messaged me regarding rooting the Tab S5e, but it's a tad bit old. Regardless, I'll paste it verbatim here:
I updated a few steps that have changed since writing that up originally. Since the Tab S5e hasn't seen a software update yet, I'll also upload my (hopefully) working copy of the flashable patched_magisk_boot.tar that you can flash in the AP slot in Odin. No guarantees it works, but I can't imagine why it wouldn't. In theory, you should be able to skip several steps above and simply OEM (bootloader) unlock the device, then flash this in Odin.
Hope this helps you achieve root.
Click to expand...
Click to collapse
btonetbone said:
Any chance you can post it here? Or share via pm? I'd be really interested in root so I can do some debloat.
Click to expand...
Click to collapse
netjetman said:
The only other trick to keep in mind, is you have to hold up and power EVERY TIME you boot. If you don't, it'll come up in not root mode.
Click to expand...
Click to collapse
Yep, good point. I forgot to include that because in the original e-mail thread, it was already known and implied. But I'll add it to the post here so folks will catch that. Annoying for sure, but at least it works.
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
Model number
GT-I9505
Android version
4.3
Baseband version
I9505XXUEMJ7
Kernel version
3.4.0-1765174
[email protected] #1
Tue Oct 15 16:14:54 KST 2013
Build number
JSS15J.I9505XXUEMJ7
SELinux status
Enforcing
SEPF_GT-I9505_4.3_0010
Secure boot status
Type: Samsung
So, i just bought this device from a friends friend who hasn't used it for a few months and even when i got it, it was 4.2 and WiFi was not working. But the problem is that i can't switch it on. When i try and press to switch it on, it doesn't do anything. Even in the notification bar, i can't turn it on.
So, what is the safest thing for me to do and fix this and is it even fixable?
The device is not rooted or flashed in any way. It's plain stock.
If somebody could reply with a step by step procedure to fix this, i would be really greatfull.
re: no wifi
nikolanicic said:
Model number
GT-I9505
Android version
4.3
Baseband version
I9505XXUEMJ7
Kernel version
3.4.0-1765174
[email protected] #1
Tue Oct 15 16:14:54 KST 2013
Build number
JSS15J.I9505XXUEMJ7
SELinux status
Enforcing
SEPF_GT-I9505_4.3_0010
Secure boot status
Type: Samsung
So, i just bought this device from a friends friend who hasn't used it for a few months and even when i got it, it was 4.2 and WiFi was not working. But the problem is that i can't switch it on. When i try and press to switch it on, it doesn't do anything. Even in the notification bar, i can't turn it on.
So, what is the safest thing for me to do and fix this and is it even fixable?
The device is not rooted or flashed in any way. It's plain stock.
If somebody could reply with a step by step procedure to fix this, i would be really greatfull.
Click to expand...
Click to collapse
If that was my phone and I did not want to root it this is what I would do.
Download Ktoonsez International 4.3 kernel:
http://ktoonsez.jonathanjsimon.com/sgs4/TW/KT-SGS4-JB4.3-TW-INTL-12.22.2013.zip
Then rename the file to "update.zip" and copy it from computer to the phone's
internal sdcard.
Before anything else, use the file manager which is in your app drawer just
to be sure that the filename is "update.zip".
(it cannot be anything else unless you root the phone)
Once you are sure of the filename, reboot the phone into the stock recovery mode
and select the option "flash update.zip" or the wording might be "install update.zip".
If you cannot find update.zip it means that you have re-named it wrongly
or you have not copied it to /sdcard.
It cannot be in some folder, it must be in the root of your sdcard.
If worst came to worst and it was my phone and the above did not work
I would simply root the phone and flash a custom recovery after that it
would be a very easy fix.
Good luck!
Misterjunky said:
If that was my phone and I did not want to root it this is what I would do.
Download Ktoonsez International 4.3 kernel:
Then rename the file to "update.zip" and copy it from computer to the phone's
internal sdcard.
Before anything else, use the file manager which is in your app drawer just
to be sure that the filename is "update.zip".
(it cannot be anything else unless you root the phone)
Once you are sure of the filename, reboot the phone into the stock recovery mode
and select the option "flash update.zip" or the wording might be "install update.zip".
If you cannot find update.zip it means that you have re-named it wrongly
or you have not copied it to /sdcard.
It cannot be in some folder, it must be in the root of your sdcard.
If worst came to worst and it was my phone and the above did not work
I would simply root the phone and flash a custom recovery after that it
would be a very easy fix.
Good luck!
Click to expand...
Click to collapse
I've tried doing that, i've placed the "update.zip" on both my external sdcard and internal phones memory.
When i click to go update it displays no package is anywhere to be found.
God damn it.
Any other options ? :/
nikolanicic said:
Model number
GT-I9505
Android version
4.3
Baseband version
I9505XXUEMJ7
Kernel version
3.4.0-1765174
[email protected] #1
Tue Oct 15 16:14:54 KST 2013
Build number
JSS15J.I9505XXUEMJ7
SELinux status
Enforcing
SEPF_GT-I9505_4.3_0010
Secure boot status
Type: Samsung
So, i just bought this device from a friends friend who hasn't used it for a few months and even when i got it, it was 4.2 and WiFi was not working. But the problem is that i can't switch it on. When i try and press to switch it on, it doesn't do anything. Even in the notification bar, i can't turn it on.
So, what is the safest thing for me to do and fix this and is it even fixable?
The device is not rooted or flashed in any way. It's plain stock.
If somebody could reply with a step by step procedure to fix this, i would be really greatfull.
Click to expand...
Click to collapse
Do a Internal Memory Card Backup and then:
Wake your Samsung Galaxy S4
Navigate to and tap on Settings.
Go to Accounts
Tap Backup & reset.
Select Factory data reset.
You will see a warning – read it and tap Reset phone.
Now tap Erase everything.
Let the phone finish the process (will reboot too)
Try if u have WIFI now
Joku1981 said:
Do a Internal Memory Card Backup and then:
Wake your Samsung Galaxy S4
Navigate to and tap on Settings.
Go to Accounts
Tap Backup & reset.
Select Factory data reset.
You will see a warning – read it and tap Reset phone.
Now tap Erase everything.
Let the phone finish the process (will reboot too)
Try if u have WIFI now
Click to expand...
Click to collapse
Nope, still not working.
nikolanicic said:
Nope, still not working.
Click to expand...
Click to collapse
Try this WIFI FIX:
Use it with care!!!
1. Go to Download Mode
2. Open Odin
3. Select this FILE as PHONE/CP and click START
4. Ur phone will reboot automatically when the process finish
5. I think this will work
Joku1981 said:
Try this WIFI FIX:
Use it with care!!!
1. Go to Download Mode
2. Open Odin
3. Select this as PHONE/CP and click START
4. Ur phone will reboot automatically when the process finish
5. I think this will work
Click to expand...
Click to collapse
Is this going to work even without rooting my device ?
I've tried what you suggested but i can't get ODIN to see my device unless it's powered on.
PS. This is what i have:
"Android system recovery <3e>
Volume up/down to move highlight;
power button to select
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache"
nikolanicic said:
Is this going to work even without rooting my device ?
I've tried what you suggested but i can't get ODIN to see my device unless it's powered on.
PS. This is what i have:
"Android system recovery <3e>
Volume up/down to move highlight;
power button to select
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache"
Click to expand...
Click to collapse
U are in STOCK RECOVERY Mode. U have to go DOWNLOAD MODE: HERE
Joku1981 said:
U are in STOCK RECOVERY Mode. U have to go DOWNLOAD MODE: HERE
Click to expand...
Click to collapse
I have done everything you've said in the tutorial...
Output from ODIN:
"<ID:0/016> Added!!
<ID:0/016> Removed!!
<ID:0/017> Added!!
<ID:0/017> Odin v.3 engine (ID:17)..
<ID:0/017> File analysis..
<ID:0/017> SetupConnection..
<ID:0/017> Initialzation..
<ID:0/017> Get PIT for mapping..
<ID:0/017> Firmware update start..
<ID:0/017> NON-HLOS.bin
<ID:0/017> NAND Write Start!!
<ID:0/017> Transmission Complete..
<ID:0/017> Now Writing.. Please wait about 2 minutes
<ID:0/017> Receive Response from boot-loader
<ID:0/017> RQT_CLOSE !!
<ID:0/017> RES OK !!
<ID:0/017> Removed!!
<ID:0/017> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
"
The phone started but i'm still unable to switch the WiFi on.
Damn it.
nikolanicic said:
I have done everything you've said in the tutorial...
Output from ODIN:
"<ID:0/016> Added!!
<ID:0/016> Removed!!
<ID:0/017> Added!!
<ID:0/017> Odin v.3 engine (ID:17)..
<ID:0/017> File analysis..
<ID:0/017> SetupConnection..
<ID:0/017> Initialzation..
<ID:0/017> Get PIT for mapping..
<ID:0/017> Firmware update start..
<ID:0/017> NON-HLOS.bin
<ID:0/017> NAND Write Start!!
<ID:0/017> Transmission Complete..
<ID:0/017> Now Writing.. Please wait about 2 minutes
<ID:0/017> Receive Response from boot-loader
<ID:0/017> RQT_CLOSE !!
<ID:0/017> RES OK !!
<ID:0/017> Removed!!
<ID:0/017> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
"
The phone started but i'm still unable to switch the WiFi on.
Damn it.
Click to expand...
Click to collapse
im having the same problem
Misterjunky said:
I would simply root the phone and flash a custom recovery after that it
would be a very easy fix.
Click to expand...
Click to collapse
Any custom recovery you'd suggest ?
One fun night
Well, this has been a fun night for me... It's 5:40AM at the moment while i'm writing this post. Take into consideration that i've had 0 experience in android phones before i've started flashing my Galaxy S4 a few hours ago.
So, first off, i've tried installing just the WiFi fix, had no luck. After that i've had trouble while instaling a custom rom (I9505XXUEMJ7-PRE-ROOTED-KNOX-FREE-ODEX-FULL.tar.md5) and i soft-bricked my phone. After that i've read that changing the USB port might solve the problem with ODIN so i've done that and it really fixed later. Had trouble with partitioning so i've had to find out what a PIT file was and where to download it. I flashed "I9505XXUEMJ7-PRE-ROOTED-KNOX-FREE-ODEX-FULL.tar.md5" (found it on the forums) and flashed the "WiFi fix", no luck. I've then came back to this thread and seen that Misterjunky told me to install a custom kernel and custom recovery mode. I've installed the kernel he suggested and i've installed Phillz recovery mode.
Now, what really bothers me and is SERIOUSLY getting on my nerves is THE WIFI IS STILL NOT WORKING AND I STILL CAN'T TURN IT ON!
I'm seriously bothered by this and i'm seriously going to trash it if i continue messing with it.
Someone please help me or i'll go insane.
try :download Samsung Kies3(for drivers) and Odin 1.85, port must indicate yellow box on odin when you connect your device in download mode,next try again wifi fix files on PHONE box and wait on pass green box,try even fiev times . On mine S4 work . Good luck
The problem might be cuz u are using the new bootloader (knox)... if u ar eusing that, follow the steps:
You need to install Triangle away (from google play, or just search it on google/xda) to wipe the BINARY counter. After this you will need to reflash the official samsung ROM via Odin and wipe data after installing.
Crossed fingers for you.
flashed everything tried everything wifi won't turn on
I flashed most stock firmwares out there then flashed the modem twice, then reflashed wifi fix twice. Wifi doesn't turn on. A few days ago I managed to fix it so I don't think it's hardware, or maybe now it is. Even tried custom roms and kernels. Anyone anywhere has any idea? Please
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.
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
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