Database Info

[Q] Bricked?

I've been in the samsung family for so long that I didn't realize how different flashing can be. I broke my phone so I bought a Moto G. Rooted it right away with only a little trouble. I installed a Lollipop ROM afterward and couldn't get my phone to boot. Guess who forgot to do a backup of the stock ROM? Yay me... but anyway, I found a stock file and went through all the steps in the screenshot. Each time, I got the okay to move on and I assumed I had the stock file flashed. Upon rebooting, I stay at the "warning, bootloader is unlocked" and phone doesn't go any further. I'm not booting up at all and custom recovery is gone now.
Can anyone help? I'm at my wit's end.
Thanks in advance.

http://forum.xda-developers.com/showthread.php?t=2542219
Follow this step by step. I did it twice. If your phone boots, it is more than likely recoverable. Once you get everything sorted out and are ready to flash a custom ROM, I recommend Carbon ROM (personal preference).
The lollipop ones are still shaky. I would try em out but they truly aren't daily drivers yet
---------- Post added at 11:19 AM ---------- Previous post was at 11:01 AM ----------
Another thought. You have your bootloader unlocked. You can flash the TWRP image through fastboot. Then you can flash the "flashable zip" stock firmware

BBobby said:
http://forum.xda-developers.com/showthread.php?t=2542219
Follow this step by step. I did it twice. If your phone boots, it is more than likely recoverable. Once you get everything sorted out and are ready to flash a custom ROM, I recommend Carbon ROM (personal preference).
The lollipop ones are still shaky. I would try em out but they truly aren't daily drivers yet
---------- Post added at 11:19 AM ---------- Previous post was at 11:01 AM ----------
Another thought. You have your bootloader unlocked. You can flash the TWRP image through fastboot. Then you can flash the "flashable zip" stock firmware
Click to expand...
Click to collapse
That's actually the instructions I used to try to flash back to stock. But when it reboots, it never gets past the warning about bootloader. I can get the TWRP recovery back but from there is there another way to flash the "flashable zip"? With Samsung I could always use ODIN but I don't think it works with Moto G. I can't get the zip to internal storage to flash it.
Thanks for the reply by the way I'm going to try it one more time I think....

http://forum.xda-developers.com/showthread.php?t=2854688
Flashable stock zips. I don't have a PC to do a full reset. But with TWRP and the flashable stock zip I have had absolutely no problem.
If all else fails I would give it a shot
I have the xt 1032 cricket/aio. I am using stock "us retail" and it works just fine. If you have radio issues etc there is also a repository of flashable radio images

BBobby said:
http://forum.xda-developers.com/showthread.php?t=2854688
Flashable stock zips. I don't have a PC to do a full reset. But with TWRP and the flashable stock zip I have had absolutely no problem.
If all else fails I would give it a shot
I have the xt 1032 cricket/aio. I am using stock "us retail" and it works just fine. If you have radio issues etc there is also a repository of flashable radio images
Click to expand...
Click to collapse
I hate sounding dumb... but how will I flash the zip if I can't get it on my phone?

Get back TWRP custom recovery by booting your phone into bootloader and flash via fastboot. You can get the .IMG file for the falcon from their website latest version is 2.8.5.0
http://teamw.in/project/twrp2/233
Then simply install the corresponding stock flashable zip

BBobby said:
Get back TWRP custom recovery by booting your phone into bootloader and flash via fastboot. You can get the .IMG file for the falcon from their website latest version is 2.8.5.0
http://teamw.in/project/twrp2/233
Then simply install the corresponding stock flashable zip
Click to expand...
Click to collapse
Thank you for all your help. I'll give that a shot.

BBobby said:
Get back TWRP custom recovery by booting your phone into bootloader and flash via fastboot. You can get the .IMG file for the falcon from their website latest version is 2.8.5.0
http://teamw.in/project/twrp2/233
Then simply install the corresponding stock flashable zip
Click to expand...
Click to collapse
Quick question. When I go into recovery to flash the zip, do I go to 'advanced' and then ' terminal command'? and go from there? I feel like a noob and I've flashed dozens of roms...

To flash a zip, choose the install option, find the name of the zip, select it, swipe to install it.

audit13 said:
To flash a zip, choose the install option, find the name of the zip, select it, swipe to install it.
Click to expand...
Click to collapse
The problem is that I didn't make a backup. When I tried flashing back to stock using fastboot everything was wiped. I don't even have the original custom ROM that started the whole mess. The stock file flashed but phone won't boot. I never get passed the boot loader warning screen. I did everything to the tee (following the directions that BBobby posted above. Actually did it twice. Isn't there an ODIN type deal for this phone. Brand new and I've broke it dangit.
Oh and I can't get into the phone to enable us debugging.

There is rsd lite but it may not help. Odin doesn't help if you can't enter download mode too. Usb debugging isn't require to flash a rom or install recovery.
It sounds like your phone is not booting because of the bootloade or the data partition is messed up.

I can get into bootloader and I have TWRP installed and can boot into it. I'm starting to think it's a lost cause. Thanks though y'all.

stacalicious said:
I can get into bootloader and I have TWRP installed and can boot into it. I'm starting to think it's a lost cause. Thanks though y'all.
Click to expand...
Click to collapse
I also got similar problem as yours. I have xt1033 dual sim phone and i had flashed lollipop 5.0.2 soak version. When official update was released for xt1033 i got back to kitkat 4.4.4 to download ota. But when i flashed kitkat through fastboot it got stuck on unlocked bootloader screen. Only solution i got still is converting to gpe. Only Gpe firmware boots. Im still finding solution for bootloop

You can get into TWRP? What happens when you use it to flash a custom ROM?

BBobby said:
http://forum.xda-developers.com/showthread.php?t=2542219
Follow this step by step. I did it twice. If your phone boots, it is more than likely recoverable. Once you get everything sorted out and are ready to flash a custom ROM, I recommend Carbon ROM (personal preference).
The lollipop ones are still shaky. I would try em out but they truly aren't daily drivers yet
---------- Post added at 11:19 AM ---------- Previous post was at 11:01 AM ----------
Another thought. You have your bootloader unlocked. You can flash the TWRP image through fastboot. Then you can flash the "flashable zip" stock firmware
Click to expand...
Click to collapse
audit13 said:
You can get into TWRP? What happens when you use it to flash a custom ROM?
Click to expand...
Click to collapse
I originally flashed a custom ROM but it never would get past the loading screen. I went through all the steps to flash back to stock and now all my data is gone. The ROM I had in my download folder is gone as is all my other info. So I get into TWRP but there's nothing in my phone I can flash.

audit13 said:
You can get into TWRP? What happens when you use it to flash a custom ROM?
Click to expand...
Click to collapse
I've flashed dozens, probably hundreds of ROMs in the past and never ran into such an issue. Custom ROM seemed to take, but got stuck. So I used fastboot and followed the directions to the tee in this link http://forum.xda-developers.com/showthread.php?t=2542219
When the ROM is finished flashing (stock that is) it never gets past the bootloader warning screen. If I could just get a zip onto the phone, I could flash through TWRP but I have no idea how to or if it's even possible.

Cwm have a option "sdcard mount" via usb. I dont remember the specific option but you can mount your device and connect it to a computer.

esd316 said:
Cwm have a option "sdcard mount" via usb. I dont remember the specific option but you can mount your device and connect it to a computer.
Click to expand...
Click to collapse
So I got into cwm. I can't mount usb storage, but I have an option to use adb sideload? Can I flash stock from there?

http://teamw.in/project/twrp2/233
Instructions on how to flash via fastboot are there in the same download page
---------- Post added at 02:47 AM ---------- Previous post was at 02:43 AM ----------
stacalicious said:
Quick question. When I go into recovery to flash the zip, do I go to 'advanced' and then ' terminal command'? and go from there? I feel like a noob and I've flashed dozens of roms...
Click to expand...
Click to collapse
The moto g just needs to do a wipe. Advanced wipe is not necessary. Then install the zip from the folder. By the way you can flash from USB otg (USB storage device such as a flash drive)

I fixed it!!!
stacalicious said:
I originally flashed a custom ROM but it never would get past the loading screen. I went through all the steps to flash back to stock and now all my data is gone. The ROM I had in my download folder is gone as is all my other info. So I get into TWRP but there's nothing in my phone I can flash.
Click to expand...
Click to collapse
esd316 said:
Cwm have a option "sdcard mount" via usb. I dont remember the specific option but you can mount your device and connect it to a computer.
Click to expand...
Click to collapse
I'd hug your neck right now if I could get to you!!! I flashed cwm, went to adb sideload and installed a stock rom. My phone is back up and money isn't going to be pissed into the wind because I made a mistake. Thanks to everyone for your help.

Anyone willing to try OG5 Root?

I was looking into the S5 OG5 root a while ago and I sold the device I had because there didn't seem to be a way to root it. I do have a rooted S4 and there was recently a new root method found for the 5.0.1 S4 rom that was released after the OG5 rom for the S5. The MobileGo website says it also supports the S5 so if anyone with OG5 unrooted wants to give this a try and let others know whether it works or not, I'm sure everyone would appreciate it. You guys are probably going to want to flash an older S5 kernel just like the S4 users flashed an older kernel before running the MobileGo program. Link: http://forum.xda-developers.com/showthread.php?t=3254434

Where do I find kernels to flash? I am willing to try this.

MySonsDad said:
Where do I find kernels to flash? I am willing to try this.
Click to expand...
Click to collapse
What you can do for now is try running MobileGo using the kernel you have now. If you're lucky, it'll root. If not, you can read on:
So what I would do first is download the latest version of Odin: http://odindownloadxda.com/Odin3_v3.10.7.zip
Then you'd want to go to this thread for the Odin flashable stock kernels for older versions:
http://forum.xda-developers.com/ver...t/safestrap-odin-safestrap-flashable-t3161043
BEFORE YOU TRY THESE NEXT STEPS: I was unable to find the stock OG5 Odin flashable kernel in these forums. If someone could kindly extract it from the stock OG5 rom and post on here you can begin the next steps. Don't try this before you have the stock OG5 kernel on hand because the older kernels may not let your phone boot up into the rom and the only way to fix it is to either reflash the entire OG5 rom in Odin or to flash the OG5 kernel in Odin. I think you can make the kernel yourself if you have the stock OG5 Odin tar, just extract the boot.img and pack it into a tar.md5 using http://forum.xda-developers.com/showthread.php?t=2446269 Here is a stock OG5 odin flashable kernel I was able to create for you: https://mega.nz/#!SEhzyKaL!ymd4vJ2Jd6ytbZoBIPp4fYh6fCRz0tELRMNAYVmIrqU
Once you have the OG5 kernel as a backup, try flashing VZW_BOD5_RETAIL_KERNEL_ONLY.tar.md5 and run MobileGo, if that doesn't work move on to VZW_BOC4_RETAIL_KERNEL_ONLY.tar.md5 then trying the MobileGo and then if that fails try NI2_stock_kernel.tar.md5 since that's the 4.4 kernel that was rootable. However, there's a strong chance that your phone will refuse to boot into the Lollipop rom using a KitKat kernel. All you have to do is flash back the OG5 kernel in Odin 3.10. Once you go through the different kernels from OG5 -> OE1 -> OC4 -> NI2 and the MobileGo program fails to root on any of them, you'll know that this is not a viable root method for the S5.

I couldn't get MobileGo to connect to my phone on OG5. I flashed the OE1 kernel, connected to MobileGo, then used Mobilego's backup feature. After that I noticed that there's a notification reading SECURITY NOTICE Unauthorized actions have been detected. Restart the device to correct them. I tried the MobileGo root and after about 5 minutes it gave me a failure message. Then I tried to proceed to BOC4 but I kept getting failures from Odin. I cannot get back to OG5 kernel either. After a few tries, I now cannot even get into download mode.
The good news is my phone is working. What do I do now? Is this "tripping Knox?"

Pull the battery. Press the buttons for download mode. There should be no case in such you can't access download mode unless you hard bricked your phone which you didn't since the phone is working. Mobilego doesn't specify if their root method trips Knox. Probably should assume it does but if the root failed then it should've left Knox alone. After a clean battery pull try flashing the OG5 kernel back to your phone.

aznjosh said:
I was looking into the S5 OG5 root a while ago and I sold the device I had because there didn't seem to be a way to root it. I do have a rooted S4 and there was recently a new root method found for the 5.0.1 S4 rom that was released after the OG5 rom for the S5. The MobileGo website says it also supports the S5 so if anyone with OG5 unrooted wants to give this a try and let others know whether it works or not, I'm sure everyone would appreciate it. You guys are probably going to want to flash an older S5 kernel just like the S4 users flashed an older kernel before running the MobileGo program. Link: http://forum.xda-developers.com/showthread.php?t=3254434
Click to expand...
Click to collapse
Where on the mobilego website does it say it supports the s5? I will try this when I get home tonight and post results.

fates13 said:
Pull the battery. Press the buttons for download mode. There should be no case in such you can't access download mode unless you hard bricked your phone which you didn't since the phone is working. Mobilego doesn't specify if their root method trips Knox. Probably should assume it does but if the root failed then it should've left Knox alone. After a clean battery pull try flashing the OG5 kernel back to your phone.
Click to expand...
Click to collapse
I can now get into download mode. If I try the older kernels I get a status bar that goes about 1cm then stops. If I try the kernel you gave me for OG5 ODIN says the binary is corrupt before even letting me flash it.

MySonsDad said:
I can now get into download mode. If I try the older kernels I get a status bar that goes about 1cm then stops. If I try the kernel you gave me for OG5 ODIN says the binary is corrupt before even letting me flash it.
Click to expand...
Click to collapse
I fixed it. I flashed the entire stock image from this thread:
http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527
I am gonna try again, skipping OE1
---------- Post added at 09:36 PM ---------- Previous post was at 09:27 PM ----------
MySonsDad said:
I fixed it. I flashed the entire stock image from this thread:
http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527
I am gonna try again, skipping OE1
Click to expand...
Click to collapse
Wait a second. I can't try again until we get a working OG5 kernel
How do I extract that?

MySonsDad said:
I fixed it. I flashed the entire stock image from this thread:
http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527
I am gonna try again, skipping OE1
---------- Post added at 09:36 PM ---------- Previous post was at 09:27 PM ----------
Wait a second. I can't try again until we get a working OG5 kernel
How do I extract that?
Click to expand...
Click to collapse
Hey, I might have created the flashable kernel incorrectly. Sorry, this is my first time creating flashable odin images. Try this one: https://mega.nz/#!SEhzyKaL!ymd4vJ2Jd6ytbZoBIPp4fYh6fCRz0tELRMNAYVmIrqU
You can try flashing that over your OG5 rom right now since it's the OG5 kernel and it won't change anything on your phone even if it does flash.
---------- Post added at 10:03 PM ---------- Previous post was at 09:56 PM ----------
Hariiiii said:
Where on the mobilego website does it say it supports the s5? I will try this when I get home tonight and post results.
Click to expand...
Click to collapse
wondershare(dot)(com)/mobile-phone/root-samsung-galaxy-s5(dot)(html)
That guide is from before the OG5 update though. However, my basis for trying this is because it was able to root an S4 5.0.1 rom that was released well after the S5 OG5 rom was released. I was thinking that they would've implemented the same root-fixes into the S4 as the S5 so if the mobilego method worked on the patched S4 rom then it should have a good chance of working on the S5. I would test all this myself but I sold my brother's S5 a couple days ago.

I dont know if odin will let you flash an older kernel other that OE1 if it does just ignore this post if not you can try this , I put together a Heimdall package that may flash the kernel and let this method work.
Instructions:
1. Download and install Heimdall For S5
2. Put phone into download mode (power+volume down+home)
3. Navigate to extracted Heimdall folder and run heimdall-frontend.exe
4. Click on utilities tab and click detect
5. Click on Flash tab in the Under Options PIT click browse and choose s5.pit
6. Under Partion Files click add
7. Change the Partion Name to BOOT
8. Click Browse and choose boot.img
9. Click Start.
If you get driver errors follow below
10. In the Heimdall folder open the Drivers folder and click on zadig.exe
11. Under options click on List All Devices
12. Choose MSM8960
13. Choose Install or Reinstall Driver
14 Go Back to Step 4
15. If devices does reboot and start with older kernel ignore any security warnings and try the root method

jrkruse said:
I dont know if odin will let you flash an older kernel other that OE1 if it does just ignore this post if not you can try this , I put together a Heimdall package that may flash the kernel and let this method work.
Instructions:
1. Download and install Heimdall For S5
2. Put phone into download mode (power+volume down+home)
3. Navigate to extracted Heimdall folder and run heimdall-frontend.exe
4. Click on utilities tab and click detect
5. Click on Flash tab in the Under Options PIT click browse and choose s5.pit
6. Under Partion Files click add
7. Change the Partion Name to BOOT
8. Click Browse and choose boot.img
9. Click Start.
If you get driver errors follow below
10. In the Heimdall folder open the Drivers folder and click on zadig.exe
11. Under options click on List All Devices
12. Choose MSM8960
13. Choose Install or Reinstall Driver
14 Go Back to Step 4
15. If devices does reboot and start with older kernel ignore any security warnings and try the root method
Click to expand...
Click to collapse
Thanks for your input jrkruse! I read here http://mobile.tumblrvip.com/2015/09/23/successfully-downgrade-from-bog5-kernel-to-any-kernel-solved/ that Odin 3.10 should allow S5 users to downgrade OG5 to any older kernel supposedly.

jrkruse said:
I dont know if odin will let you flash an older kernel other that OE1 if it does just ignore this post if not you can try this , I put together a Heimdall package that may flash the kernel and let this method work.
Instructions:
1. Download and install
2. Put phone into download mode (power+volume down+home)
3. Navigate to extracted Heimdall folder and run heimdall-frontend.exe
4. Click on utilities tab and click detect
5. Click on Flash tab in the Under Options PIT click browse and choose s5.pit
6. Under Partion Files click add
7. Change the Partion Name to BOOT
8. Click Browse and choose boot.img
9. Click Start.
If you get driver errors follow below
10. In the Heimdall folder open the Drivers folder and click on zadig.exe
11. Under options click on List All Devices
12. Choose MSM8960
13. Choose Install or Reinstall Driver
14 Go Back to Step 4
15. If devices does reboot and start with older kernel ignore any security warnings and try the root method
Click to expand...
Click to collapse
Thanks for the detailed instructions. Somebody may want to keep trying this. I got an error on step 9 relating to libusb, is that the drivers?
---------- Post added at 06:11 AM ---------- Previous post was at 06:01 AM ----------
MySonsDad said:
I fixed it. I flashed the entire stock image from this thread:
http://forum.xda-developers.com/verizon-galaxy-s5/general/g900vvru2bog5-factoryodintarimage-t3179527
I am gonna try again, skipping OE1
---------- Post added at 09:36 PM ---------- Previous post was at 09:27 PM ----------
Wait a second. I can't try again until we get a working OG5 kernel
How do I extract that?
Click to expand...
Click to collapse
Okay. Here's my assessment of the ODIN method.
OG5 on OG5 Kernel - MobileGo Cannot Root this
OG5 on OE1 Kernel - MobileGo Cannot Root This
OG5 on OC4 Kernel - MobileGo Cannot Root This
OG5 on NI2 Kernel - Bad idea. I was stuck in a boot loop for like an hour before I got back to Download mode to reflash the whole stock image.
You can flash any of these kernels from ODIN, and you can flash everything back to rescue yourself. If you leave one of the older kernels on your phone too long, it will soft brick. If somebody figures out a root method that works, ODIN will be able to help use move between Kernels. This has been a fun first foray into Android Hacking. I still hate my phone.
Thank you fates13 and jrkruse, you guys rock.

MySonsDad said:
Thanks for the detailed instructions. Somebody may want to keep trying this. I got an error on step 9 relating to libusb, is that the drivers?
---------- Post added at 06:11 AM ---------- Previous post was at 06:01 AM ----------
Okay. Here's my assessment of the ODIN method.
OG5 on OG5 Kernel - MobileGo Cannot Root this
OG5 on OE1 Kernel - MobileGo Cannot Root This
OG5 on OC4 Kernel - MobileGo Cannot Root This
OG5 on NI2 Kernel - Bad idea. I was stuck in a boot loop for like an hour before I got back to Download mode to reflash the whole stock image.
You can flash any of these kernels from ODIN, and you can flash everything back to rescue yourself. If you leave one of the older kernels on your phone too long, it will soft brick. If somebody figures out a root method that works, ODIN will be able to help use move between Kernels. This has been a fun first foray into Android Hacking. I still hate my phone.
Thank you fates13 and jrkruse, you guys rock.
Click to expand...
Click to collapse
Thanks for testing!

All those people complaining that their updated device can't be rooted, not willing to try this out?

Can confirm that the root does not work and that the NI2 kernel will not successfully boot lollipop. Root might be theoretically possible if NI2 could boot....any thoughts on how to get into lollipop with the NI2 kernel in place?

ldeveraux said:
All those people complaining that their updated device can't be rooted, not willing to try this out?
Click to expand...
Click to collapse
I have an unrooted VZW S5 with OG5 and would like to give it a shot, but download mode hasn't worked for me since OE1. Holding power+vol down+home just boots the device normally. I've tried holding them all the way through the boot, which causes the phone to repeatedly reboot. Am I missing something?
Edit: Nevermind, guess I was pressing power first. I've got download mode now. Will report back if I make any progress...

Verizon
This is unfortunate.
So we are back to square one?
But if I understand, MySonsDad confirmed we have no reason to not update to OK3 since we can jump between the locked kernels?

So no root for 5.0? I've got to start researching these things before I buy a phone.

brd912 said:
So no root for 5.0? I've got to start researching these things before I buy a phone.
Click to expand...
Click to collapse
Same here, I figured it would be a similar process as rooting my Nexus 5 when I was on AT&T. The Verizon and Samsung bloatware is painful when it can't be removed.

Is there no update on this? I'm willing to anything at this point.

Trouble rooting my Pixel

I have tried TWRP (twrp.me/devices/googlepixel.html) and the Unified Android Toolkit (skipsoft.net/download/uat-v156/) to root the Pixel I bought directly from Google. With TWRP, I cannot see the .zip I downloaded (the phone is encrypted and /sdcard/* are all gibberish names; I'm never prompted for a decrypting password when booting for recovery) and with the Toolkit I end up in a reboot loop (I've tried twice with the same results).
I'm surprised that the Toolkit thinks my build is "Verizon" (NDE63X). I'm not sure if that matters.
Thoughts? Pointers? Diagnostics? TIA.

go get the new alpah2 of twrp.
---------- Post added at 01:51 PM ---------- Previous post was at 01:48 PM ----------
Save v4 root on sd. Save alpha 2 img on desktop, and .zip on sd on phone. fastboot img, enter pin or pattern, then flash alpha2 zip. restart in recovery, flash v4 root. Done.

computercarl said:
go get the new alpah2 of twrp.
---------- Post added at 01:51 PM ---------- Previous post was at 01:48 PM ----------
Save v4 root on sd. Save alpha 2 img on desktop, and .zip on sd on phone. fastboot img, enter pin or pattern, then flash alpha2 zip. restart in recovery, flash v4 root. Done.
Click to expand...
Click to collapse
Thanks. That gets me further. I put twrp-pixel-installer-sailfish-3.0.2-0-alpha2.zip and SR3-SuperSU-v2.78-SR3-20161103171345.zip on the SD card. I booted with twrp-3.0.2-0-alpha2-fastboot-sailfish.img and I could see the zips. I installed alpha2.zip, reboooted, installed SuperSU, rebooted. I don't see SuperSU in my app list. I'm missing something. I'm not sure what you mean by "v4 root".

ChrisNelsonPE said:
Thanks. That gets me further. I put twrp-pixel-installer-sailfish-3.0.2-0-alpha2.zip and SR3-SuperSU-v2.78-SR3-20161103171345.zip on the SD card. I booted with twrp-3.0.2-0-alpha2-fastboot-sailfish.img and I could see the zips. I installed alpha2.zip, reboooted, installed SuperSU, rebooted. I don't see SuperSU in my app list. I'm missing something. I'm not sure what you mean by "v4 root".
Click to expand...
Click to collapse
Since you have to temp boot twrp, I just use adb sideload to flash the twrp and SuperSU zips.
I reflash stock boot img
Boot into twrp from fast boot
Sideload twrp zip
Reboot recovery
Sideload supersu sr4 zip

GeekMcLeod said:
Since you have to temp boot twrp, I just use adb sideload to flash the twrp and SuperSU zips.
...
Sideload supersu sr4 zip
Click to expand...
Click to collapse
I found download.chainfire.eu/1013/SuperSU/SR4-SuperSU-v2.78-SR4-20161115184928.zip. Trying that shortly.

ChrisNelsonPE said:
I found download.chainfire.eu/1013/SuperSU/SR4-SuperSU-v2.78-SR4-20161115184928.zip. Trying that shortly.
Click to expand...
Click to collapse
Just let me know if you need any help. I'd happily help you get your phone rooted.

GeekMcLeod said:
Just let me know if you need any help. I'd happily help you get your phone rooted.
Click to expand...
Click to collapse
SU4 did it for me.
And a shout out to the Helium app for moving my data, even without root. Best $5 I spent this year!

ChrisNelsonPE said:
SU4 did it for me.
And a shout out to the Helium app for moving my data, even without root. Best $5 I spent this year!
Click to expand...
Click to collapse
I'm curious, I think I have ADB set up correctly but I have never had any luck I. Using it before ( mainly because of ADB language and commands to do what I want to do). Is there a guide that tells people like myself what to type and where to put files? Man that would be nice .

quinejh said:
I'm curious, I think I have ADB set up correctly but I have never had any luck I. Using it before ( mainly because of ADB language and commands to do what I want to do). Is there a guide that tells people like myself what to type and where to put files? Man that would be nice .
Click to expand...
Click to collapse
I highly recommend that if you're going to be doing stuff like this to your phone you get familiar with ADB and fastboot otherwise you're just asking for trouble. Each of the threads on custom recovery and root have the links and instructions including commands, read everything twice since you're new to this and I mean everything.

[G930F][Nougat] Installing TWRP or rooting resulting in eternal flashing Samsung logo

Hey,
So yesterday I decided to flash the BTU Nougat 7.0 firmware to my EE S7 and all went well and the device booted normally, after this I tried to install TWRP onto my device which also went well, I installed the no-verify zip (or whatever it's called) and tried to boot the phone and I was just greeted with the flashing Samsung logo for an hour, after this I used Odin to flash my phone back my phone to the BTU nougat ROM and everything was fine, later I tried to use CF-Auto-Root which once again resulted in the flashing Samsung logo, I also tried wiping my data with TWRP and booting but to no use, same error occurred. Can anyone help, really I only need TWRP as I just want Google assistant (Yes I know, probably not worth tripping the KNOX for but I want it) and for this I just need to install a zip file.
Thanks!
EDIT: Fully resolved, just installed the Superman ROM and all is well. Thanks for the help!

Using the latest version of ODIN?
Any older than 3.12.3 cause problems

*Detection* said:
Using the latest version of ODIN?
Any older than 3.12.3 cause problems
Click to expand...
Click to collapse
Yeah I'm using 3.12.3

tbh to make things less hassle download any custom roms avail and used it. i gave up when i had the same issues as yours or maybe slightly worse losing my IMEI and baseband too. did install twrp to the cm14.1 rom and now using superman rom's everything was fine root is there too.
---------- Post added at 06:12 AM ---------- Previous post was at 06:05 AM ----------
but if you still insist on using the stock rom with just root what i can suggest u to do is turn off that oem lock in the settings and enable usb debugging. 1) Odin flash your twrp.zip files 2) Download supersu.zip or any rootable zip files 3) and extra modifications/tweaks you wanna add in such as the no-verify thingy 4) Always download your stock original firmware in case you messed it up.

MxFadzil92 said:
tbh to make things less hassle download any custom roms avail and used it. i gave up when i had the same issues as yours or maybe slightly worse losing my IMEI and baseband too. did install twrp to the cm14.1 rom and now using superman rom's everything was fine root is there too.
---------- Post added at 06:12 AM ---------- Previous post was at 06:05 AM ----------
but if you still insist on using the stock rom with just root what i can suggest u to do is turn off that oem lock in the settings and enable usb debugging. 1) Odin flash your twrp.zip files 2) Download supersu.zip or any rootable zip files 3) and extra modifications/tweaks you wanna add in such as the no-verify thingy 4) Always download your stock original firmware in case you messed it up.
Click to expand...
Click to collapse
Thanks for the tip mate, I'll have a look at some custom ROMs for my phone tomorrow, I used to use CM14 on my s5 so CM shall be my first choice I think

did you try formating data in twrp?
you will loose your data but that should fix it.

munchy_cool said:
did you try formating data in twrp?
you will loose your data but that should fix it.
Click to expand...
Click to collapse
Yeah I've already tired that

Sumsung j7 duo sm-j720F recovery and root ??

Hi all
I can't find the recovery and how to root my Sumsung j7 duo sm-j720F with oreo android
Any help plz
And thanx in advance .

No one answer seems like no root and twrp at thise time

Unfortunately the reason you can't find it is the same reason, why nobody can find it: it simply does not exist...

Try Magisk. (I've personally tried and succeeded).
1. Extract "boot.img" from J720F's latest stock firmware and copy it to your sd-card.
2. Install latest Magisk Manager apk.
3. Through Magisk patch the stock "boot.img" in Odin flashable ".img.tar" format.
4. Copy the "patched-boot.img.tar" to your pc and load it in Odin's "AP".
5. Make sure your phone is OEM unlocked.
6. Go to recovery mode and make factory reset/wipe data for best result (I've not tested whether it works without factory reset)
7. Go to download mode (Newer models like J720F doesn't support previous download mode access method by pressing and holding volume down+home+power buttons. New method is pressing and holding "volume down+home" button and attaching the usb cable).
8. Flash the "patched-boot.img.tar"
9. After restart finish additional setups in Magisk app.
10. Enjoy!

mastergg said:
Try Magisk. (I've personally tried and succeeded).
1. Extract "boot.img" from J720F's latest stock firmware and copy it to your sd-card.
2. Install latest Magisk Manager apk.
3. Through Magisk patch the stock "boot.img" in Odin flashable ".img.tar" format.
4. Copy the "patched-boot.img.tar" to your pc and load it in Odin's "AP".
5. Make sure your phone is OEM unlocked.
6. Go to recovery mode and make factory reset/wipe data for best result (I've not tested whether it works without factory reset)
7. Go to download mode (Newer models like J720F doesn't support previous download mode access method by pressing and holding volume down+home+power buttons. New method is pressing and holding "volume down+home" button and attaching the usb cable).
8. Flash the "patched-boot.img.tar"
9. After restart finish additional setups in Magisk app.
10. Enjoy!
Click to expand...
Click to collapse
Thank i ll try
The only thing that i not found is OEM unlocked i have not thise option in my j720f ?

You will find OEM unlock option under "Developer Options" menu. You need to enable the menu first by continuously tapping your "Build Number" for 7 times in a row. Remember that enabling OEM unlock will automatically factory reset your phone. So don't forget to take a backup first.
I suggest you to first install magisk, find the stock boot image and patch it through your phone, then copy it to your pc. Backup everything else you need. Then enable OEM unlock. This way you need to reset your phone only once.

Sir i m try alot to patch boot.img but installing failed error. Can u provide patched boot.img.tar file i really need it
Thank yo

mastergg said:
You will find OEM unlock option under "Developer Options" menu. You need to enable the menu first by continuously tapping your "Build Number" for 7 times in a row. Remember that enabling OEM unlock will automatically factory reset your phone. So don't forget to take a backup first.
I suggest you to first install magisk, find the stock boot image and patch it through your phone, then copy it to your pc. Backup everything else you need. Then enable OEM unlock. This way you need to reset your phone only once.
Click to expand...
Click to collapse
Thank you but i still can't find OEM unlock
In the pict is all what i have in Developer Options option

Samy6699 said:
Thank you but i still can't find OEM unlock
In the pict is all what i have in Developer Options option
Click to expand...
Click to collapse
Strange indeed! You should have the option! In my case it's between "Bluetooth HCI snoop log" and "Running services".
What's your firmware version? Is it the latest one? My build number is "R16NW.J720FDDU3ARI4".
---------- Post added at 12:35 PM ---------- Previous post was at 12:26 PM ----------
prvnktl said:
Sir i m try alot to patch boot.img but installing failed error. Can u provide patched boot.img.tar file i really need it
Thank yo
Click to expand...
Click to collapse
I will try to provide it and will post the link.
But why can't you patch? Is there any problem with Magisk? Or you cannot install the patch through Odin?

mastergg said:
Strange indeed! You should have the option! In my case it's between "Bluetooth HCI snoop log" and "Running services".
What's your firmware version? Is it the latest one? My build number is "R16NW.J720FDDU3ARI4".
Click to expand...
Click to collapse
Yes its the last updat august 1 2018
As the pict show
I do some shearch and many have the same probleme i try to fix it

Samy6699 said:
Yes its the last updat august 1 2018
As the pict show
I do some shearch and many have the same probleme i try to fix it
Click to expand...
Click to collapse
Seems like you have been locked by your bootloader. You can refer to this guide if it helps.
https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/

mastergg said:
Strange indeed! You should have the option! In my case it's between "Bluetooth HCI snoop log" and "Running services".
What's your firmware version? Is it the latest one? My build number is "R16NW.J720FDDU3ARI4".
---------- Post added at 12:35 PM ---------- Previous post was at 12:26 PM ----------
I will try to provide it and will post the link.
But why can't you patch? Is there any problem with Magisk? Or you cannot install the patch through Odin?
Click to expand...
Click to collapse
Yes problem with Magisk

prvnktl said:
Yes problem with Magisk
Click to expand...
Click to collapse
Install latest Magisk manager.
However for your convenience I am providing the patched boot image.
https://drive.google.com/file/d/1Qx3_wol2dN_RcPXhfvBv7vgVSDnEdi-E/view?usp=sharing
This is extracted from the latest stock firmware having build number J720FDDU3ARI4 so please confirm yourself that you are using the same firmware.
Download and flash it through Odin and let me know about what happens.

mastergg said:
Seems like you have been locked by your bootloader. You can refer to this guide if it helps.
https://www.xda-developers.com/fix-...y-s9-samsung-galaxy-s8-samsung-galaxy-note-8/
Click to expand...
Click to collapse
i try it and i try many other tutorial without success
i flash the same firm as you and no way no oem unlock :crying:
i can't get these oem unlock :crying::crying::crying::crying:

Samy6699 said:
i try it and i try many other tutorial without success
i flash the same firm as you and no way no oem unlock :crying:
i can't get these oem unlock :crying::crying::crying::crying:
Click to expand...
Click to collapse
Sorry to hear that. Did you tried a factory reset? And still there is no OEM unlock? If yes then wait till the next firmware release. Or continue searching for any other method. If I come across something then will definitely post here.

mastergg said:
Sorry to hear that. Did you tried a factory reset? And still there is no OEM unlock? If yes then wait till the next firmware release. Or continue searching for any other method. If I come across something then will definitely post here.
Click to expand...
Click to collapse
Yes i did with factory reset and i try flashing some other firmware with all tutorial talking about changing date
Desabling the auto update and many other
I still searching other trick my be ...
Any way thank you for your great help regards:good:

mastergg said:
Strange indeed! You should have the option! In my case it's between "Bluetooth HCI snoop log" and "Running services".
What's your firmware version? Is it the latest one? My build number is "R16NW.J720FDDU3ARI4".
---------- Post added at 12:35 PM ---------- Previous post was at 12:26 PM ----------
I will try to provide it and will post the link.
But why can't you patch? Is there any problem with Magisk? Or you cannot install the patch through Odin?
Click to expand...
Click to collapse
yes problem with magisk hlp me out please

mastergg said:
Sorry to hear that. Did you tried a factory reset? And still there is no OEM unlock? If yes then wait till the next firmware release. Or continue searching for any other method. If I come across something then will definitely post here.
Click to expand...
Click to collapse
I get new updat of the system
How to do now to enable oem plz help

Samy6699 said:
I get new updat of the system
How to do now to enable oem plz help
Click to expand...
Click to collapse
Is the OEM unlock toggle still unavailable? Then wait for 7 days since update and check again.
---------- Post added at 08:59 PM ---------- Previous post was at 08:58 PM ----------
prvnktl said:
yes problem with magisk hlp me out please
Click to expand...
Click to collapse
Flash the patched boot image first

mastergg said:
Is the OEM unlock toggle still unavailable? Then wait for 7 days since update and check again.
Click to expand...
Click to collapse
I don't think the trick of 7 day ll work it was fixed in last updat of august