Hi--
I've done some searching to see about this, but honestly I'm a little out of my league here.
I have an att gs6 that I haven't used in a while. It is currently on 5.1.1 and firmware version 3.10.61xxxx. Before I totally tried using it, I tried updating to marshmallow but was an idiot and let my computer go to sleep, so flashing the update failed and now dm-verity verification fails. Since this has happened, it wouldn't OTA update or allow anything at all. Now, I'm no longer on att and not currently using this device, but it would be great if I could revive it.
Basically, I'd love to root, install twrp, flash custom roms, etc. but I'm just not sure what I can do, and my situation is so out of date that I'm hesitant to try anything without some guidance.
I'd really appreciate any help you all can offer, and I hope that I'm posting this in the right place, etc. Thanks in advance!
dcrow0 said:
Hi--
I've done some searching to see about this, but honestly I'm a little out of my league here.
I have an att gs6 that I haven't used in a while. It is currently on 5.1.1 and firmware version 3.10.61xxxx. Before I totally tried using it, I tried updating to marshmallow but was an idiot and let my computer go to sleep, so flashing the update failed and now dm-verity verification fails. Since this has happened, it wouldn't OTA update or allow anything at all. Now, I'm no longer on att and not currently using this device, but it would be great if I could revive it.
Basically, I'd love to root, install twrp, flash custom roms, etc. but I'm just not sure what I can do, and my situation is so out of date that I'm hesitant to try anything without some guidance.
I'd really appreciate any help you all can offer, and I hope that I'm posting this in the right place, etc. Thanks in advance!
Click to expand...
Click to collapse
Depending on which 5.1.1 build you are on, you may be able to do either ping pong or the tethered root. Ping pong only worked on the first couple official builds after the phone launched. Think the ping pong thread is in development, and tethered root thread is in general.
There is no way to unlock the bootloader for the ATT model, so no custom recovery or custom ROMs.
dandrumheller said:
Depending on which 5.1.1 build you are on, you may be able to do either ping pong or the tethered root. Ping pong only worked on the first couple official builds after the phone launched. Think the ping pong thread is in development, and tethered root thread is in general.
There is no way to unlock the bootloader for the ATT model, so no custom recovery or custom ROMs.
Click to expand...
Click to collapse
Awesome, thanks for your reply. I figured the custom rom thing would be the case, but it never hurts to ask.
If I do tethered root, will I be able to bypass the dm-verity check and upgrade to latest android version?
dcrow0 said:
Awesome, thanks for your reply. I figured the custom rom thing would be the case, but it never hurts to ask.
If I do tethered root, will I be able to bypass the dm-verity check and upgrade to latest android version?
Click to expand...
Click to collapse
I don't know about your DM verity issue. I never did the tethered root - couldn't risk being stuck in a boot loop with my daily driver.
dandrumheller said:
Depending on which 5.1.1 build you are on, you may be able to do either ping pong or the tethered root. Ping pong only worked on the first couple official builds after the phone launched. Think the ping pong thread is in development, and tethered root thread is in general.
There is no way to unlock the bootloader for the ATT model, so no custom recovery or custom ROMs.
Click to expand...
Click to collapse
Well, if you have temproot, there actually may be a way to unlock the bootloader if you found an XDA developer with the unlocked Samsung willing to cooperate, you could have them extract Samsungs bootloader unlcoking tool, called CROM service, and the necessary libs and framework. It's risky, but may work.
Related
On the G900A shipped from AT&T we have a locked bootloader, and there is no known existing workaround to unlock it correct?
So given that, root was achieved , then safestrap was developed so we can currently flash roms that use the stock bootloader and kernel image, however we can customize the OS as long as the kernel and loader are untouched.
If the bootloader stays locked, what is known regarding safestrap and lollipop?
Can we still rollback the stock kernel to achieve root, then roll forward and keep it?
If that is the case, then when the stock AT&T lollipop is released, some level of ROM development can occur?
I am confused somewhat by all the discussions surrounding this, and didn't see any threads to discuss it specifically.
wmunn said:
On the G900A shipped from AT&T we have a locked bootloader, and there is no known existing workaround to unlock it correct?
So given that, root was achieved , then safestrap was developed so we can currently flash roms that use the stock bootloader and kernel image, however we can customize the OS as long as the kernel and loader are untouched.
If the bootloader stays locked, what is known regarding safestrap and lollipop?
Can we still rollback the stock kernel to achieve root, then roll forward and keep it?
If that is the case, then when the stock AT&T lollipop is released, some level of ROM development can occur?
I am confused somewhat by all the discussions surrounding this, and didn't see any threads to discuss it specifically.
Click to expand...
Click to collapse
No, if you update to lollipop then your ability to have a rooted phone will be lost. The bootloader hasnt changed since the phone was released which is the reason we have been able to rollback the rom. This was a loophole in the original firmware of the s5. When lollipop comes out then it will be a completely different bootloader and will be locked and you will not be able to roll back to kk bootloader. The loophole for this has been patched and there probably wont be another way to root the phone after lollipop considering the guy that found the loophole is now working for googles security team. Bottom line is if you want root then you cant have lollipop.
Sent from my SM-G900A using XDA Free mobile app
miller1821 said:
No, if you update to lollipop then your ability to have a rooted phone will be lost. The bootloader hasnt changed since the phone was released which is the reason we have been able to rollback the rom. This was a loophole in the original firmware of the s5. When lollipop comes out then it will be a completely different bootloader and will be locked and you will not be able to roll back to kk bootloader. The loophole for this has been patched and there probably wont be another way to root the phone after lollipop considering the guy that found the loophole is now working for googles security team. Bottom line is if you want root then you cant have lollipop.
Sent from my SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
How does this affect our device when it gets the lollipop update?
http://www.xda-developers.com/android/supersu-beta-lollipop-root-stock-kernel/
wmunn said:
On the G900A shipped from AT&T we have a locked bootloader, and there is no known existing workaround to unlock it correct?
So given that, root was achieved , then safestrap was developed so we can currently flash roms that use the stock bootloader and kernel image, however we can customize the OS as long as the kernel and loader are untouched.
If the bootloader stays locked, what is known regarding safestrap and lollipop?
Can we still rollback the stock kernel to achieve root, then roll forward and keep it?
If that is the case, then when the stock AT&T lollipop is released, some level of ROM development can occur?
I am confused somewhat by all the discussions surrounding this, and didn't see any threads to discuss it specifically.
Click to expand...
Click to collapse
Thanks to chainfire the chances of updating to 5.0 while keeping root seems more doable at this point.
However, based on recent samsung updates for other devices, safestrap may stop functioning after the update as it continues its slow death.
Once again, if having root access is important to you, do no not take the 5.0 update when released until some of us have a chance to evaluate it.
Since I am running dynamic Kat on stock slot right now, I should be safe from updates for now right?
Waiting to see what happens with all this. I did back up my stock rom to an SD card, so I can restore and unroot etc... to get an update if I choose to later.
muniz_ri said:
Thanks to chainfire the chances of updating to 5.0 while keeping root seems more doable at this point.
However, based on recent samsung updates for other devices, safestrap may stop functioning after the update as it continues its slow death.
Once again, if having root access is important to you, do no not take the 5.0 update when released until some of us have a chance to evaluate it.
Click to expand...
Click to collapse
was looking for a post like this. well maybe we might get 5.1 in the next few weeks or sooner so i am sure you will give it a try and a good look and hopefully you will have success in attaining root and a good SS. seems like u da man for this...:good::good:
as for 5.1 or a custom rom...well whose to say what that will bring...
will be waiting to see what happens. will check back here when it comes out. i watch for it everyday and as usual, thank you for all your great work!
miller1821 said:
No, if you update to lollipop then your ability to have a rooted phone will be lost. The bootloader hasnt changed since the phone was released which is the reason we have been able to rollback the rom. This was a loophole in the original firmware of the s5. When lollipop comes out then it will be a completely different bootloader and will be locked and you will not be able to roll back to kk bootloader. The loophole for this has been patched and there probably wont be another way to root the phone after lollipop considering the guy that found the loophole is now working for googles security team. Bottom line is if you want root then you cant have lollipop.
Sent from my SM-G900A using XDA Free mobile app
Click to expand...
Click to collapse
Not necessarily, just because (if) the S5 gets 5.0 does not mean the ability to root will be lost just go check out the Verizon S5 forums you'll see they have a method for rooting with 5.0 that in theory should work for us as well. again it is recomended to remain on a 4.4.x rom until this has been fully evaluated.
wmunn said:
On the G900A shipped from AT&T we have a locked bootloader, and there is no known existing workaround to unlock it correct?
So given that, root was achieved , then safestrap was developed so we can currently flash roms that use the stock bootloader and kernel image, however we can customize the OS as long as the kernel and loader are untouched.
If the bootloader stays locked, what is known regarding safestrap and lollipop?
Can we still rollback the stock kernel to achieve root, then roll forward and keep it?
If that is the case, then when the stock AT&T lollipop is released, some level of ROM development can occur?
I am confused somewhat by all the discussions surrounding this, and didn't see any threads to discuss it specifically.
Click to expand...
Click to collapse
My suggestion would be not to take any updates until the root capabilities have been evaluated.
As always, research goes a long way towards alleviating fears and stopping panic attacks before they happen. be patient there are great devs here give them time to work
Well, I stopped using the S5 and switched to a oneplus one, happily running CM12 nightlies now
the att gs5 doesn't seem like it's getting any updates..
wmunn said:
Well, I stopped using the S5 and switched to a oneplus one, happily running CM12 nightlies now
Click to expand...
Click to collapse
How are you liking it? I'm seriously thinking about doing the same thing.
I have a coworker that just got the Lollipop update for his Note 3 so that means it will be coming to the S5 very soon!
There is a pre-rooted lollipop update on droid views "http://www.droidviews.com/install-rooted-lollipop-on-att-galaxy-s5-sm-g900a/" . I have updated already and it runs smoothly. The only thing is after you run the update it can take anywhere from 5 to 20 minutes to reboot so just hang tight.
silentscreamz said:
There is a pre-rooted lollipop update on droid views "http://www.droidviews.com/install-rooted-lollipop-on-att-galaxy-s5-sm-g900a/" . I have updated already and it runs smoothly. The only thing is after you run the update it can take anywhere from 5 to 20 minutes to reboot so just hang tight.
Click to expand...
Click to collapse
I used that method as well. Sure, it worked for me, but I came from Dynamic Kat, a well debloated stock rom. Due to this, after installing the update using this method, the built-in apps restore function could not complete due to having all of the useless bloatware back, taking up the extra space I was free to use in Dynamic Kat. Even removing the apps that are safe to remove via Titanium Backup doesn't help because the space is reserved for them. I've also already moved every app that it will allow to move to SD card. I've removed unneeded apps. I've gone through my internal storage to remove any unneeded files.
I've removed most of the apps listed here
This doesn't give me the Bluetooth tether that I used to us for my Gear 1(Running Null Rom). I'd look for an app to cover this but... I can't install anything because I've got no space to do so... I hope a good debloat method comes along soon. I still have root, so I'm hopeful.
Yea, bloatware is ridiculous for this phone. Have you tried the Alliance rom, that is what I run and it's not to bad for bloatware but I have only managed to get 5.6 running. Going to try version 8 today sometime. If you like to customize that is an awesome rom.
Hi folks, new to the S5 forums on here as I just upgraded from my trusty S3 on AT&T. I'm still on the stock 4.4.2 firmware, NG3 build, and I'm wondering if I should just root from here using TowelRoot method or take the 4.4.4 OTA and root from there.
Root your 4.4.2, then use the update while saving root to lollipop and skip 4.4.4 all together.
SoCalHTCFuze said:
Root your 4.4.2, then use the update while saving root to lollipop and skip 4.4.4 all together.
Click to expand...
Click to collapse
I tried to root using TowelRoot but it said device not supported. I'll do some research though. Havent even had the phone 5 hours yet.
MetalHead66 said:
I tried to root using TowelRoot but it said device not supported. I'll do some research though. Havent even had the phone 5 hours yet.
Click to expand...
Click to collapse
You gotta downgrade theres a post on here just type it in the search bar. Pretty easy process
Yes. Follow the 4.4.2 how to root thread, it says that bit still works.
OK thanks a bunch. Getting ready to do that now.
---------- Post added at 03:27 AM ---------- Previous post was at 02:53 AM ----------
Well that was quite easy and I'm a happy camper now! Just had to flash nd3 kernel with odin in order for TR to work then flash my ng3 kernel. So nice to be able to use TiBu. Helium wouldnt install all my apps. Now I can start freezing and uninstalling all the bloatware!
So I actually don't have the S5, or any Samsung device for that matter, but a friend of mine does, and really wants to root their phone. I had no idea the AT&T S5 was so secure, but it's pretty interesting too. I've been researching for over 15 hours. I may not have been able to root his phone, but I think I have learned a couple things and maybe some possible root methods.
1.) Since using ODIN to downgrade would soft brick the phone, would it be possible to download the stock Lollipop update onto a computer, give the update super user access, replace the recovery with a custom one, or unlock the bootloader from the computer, then flash it through ODIN?
2.) Intercept any sort of OTA update, then alter it to flash a custom recovery or unlock bootloader? I don't know how you would go around this though.
3.) If someone hasn't taken the OTA update that patched the Stagefright exploit, could someone purposely use the exploit to allow installation of a custom recovery or even to unlock the bootloader since the Stagefright bug has super user access (or so I've heard).
Also, I'm sorry if these are stupid ideas. I know close to nothing about Samsung so everything I'm basing this off of is what I've read in the past 15 hours.
jsmithfms said:
So I actually don't have the S5, or any Samsung device for that matter, but a friend of mine does, and really wants to root their phone. I had no idea the AT&T S5 was so secure, but it's pretty interesting too. I've been researching for over 15 hours. I may not have been able to root his phone, but I think I have learned a couple things and maybe some possible root methods.
1.) Since using ODIN to downgrade would soft brick the phone, would it be possible to download the stock Lollipop update onto a computer, give the update super user access, replace the recovery with a custom one, or unlock the bootloader from the computer, then flash it through ODIN?
2.) Intercept any sort of OTA update, then alter it to flash a custom recovery or unlock bootloader? I don't know how you would go around this though.
3.) If someone hasn't taken the OTA update that patched the Stagefright exploit, could someone purposely use the exploit to allow installation of a custom recovery or even to unlock the bootloader since the Stagefright bug has super user access (or so I've heard).
Also, I'm sorry if these are stupid ideas. I know close to nothing about Samsung so everything I'm basing this off of is what I've read in the past 15 hours.
Click to expand...
Click to collapse
The issue is that AT&T (and Verizon) use an encrypted signature key to verify they are the correct unaltered files as well as the means to unlock the bootloader to allow the OTA. Without that key, the tasks you mention are near impossible. They are not stupid ideas at all..just very difficult with all the security checks included.
KennyG123 said:
The issue is that AT&T (and Verizon) use an encrypted signature key to verify they are the correct unaltered files as well as the means to unlock the bootloader to allow the OTA. Without that key, the tasks you mention are near impossible. They are not stupid ideas at all..just very difficult with all the security checks included.
Click to expand...
Click to collapse
Crap... well does anyone know how that encyption key is generated? Like, could I theoretically get an algorithm from a ROM?
Honestly for the time being I wouldn't bother with ROMS for that Device and carrier at the moment. Especially being that its someone elses device. Towelroot should be a good start. If Im not mistaken I don't think its supposed to trip knox.
Sent from my HTCEVODesign4G using XDA Free mobile app
jsmithfms said:
Crap... well does anyone know how that encyption key is generated? Like, could I theoretically get an algorithm from a ROM?
Click to expand...
Click to collapse
This is the riddle of the Sphinx my friend. I am sure the super devs have tried their best so far to crack it. It has been an ongoing effort to make phones more and more secure, not against the amateur developers and rooters, but against the hackers. These smartphones are now our personal computers, diaries, personal assistants, financial operator, and more. They basically are a person's (and business's) life. AT&T and Verizon have taken the big steps to appeal to the Exchange clients, corporate, government and military contracts. Even the general public want to know their phone is secure. This is what keeps me stuck on the Sprint network.
Have you tried Kingroot?
I successfully rooted my wife's AT&T S4 on OC3 lollipop (supposedly unrootable) with the desktop version. Mobile version didn't work but desktop did without a hiccup. Maybe it'll work on the S5.
http://forum.xda-developers.com/android/apps-games/one-click-root-tool-android-2-x-5-0-t3107461
Rockin' a l337 with Goldeneye v49.1 + Wanam Xposed and loving life on AT&T's 4G LTE network
S5 on lollipop has a new nasty boot loader.... it was a miracle on its own that they ever came up with safestrap to duck the boot loader on earlier versions of android
Wondering if I should update downloaded ota then root or will the update screw things up like locking my boot loader and installing things I don't want or that will make customizing more difficult or impossible? Have had real bad luck with Verizon ota's in the past when it comes to rooting, unlocking, jailbreaking etc... And from what I've been reading on other threads this and other nexus ota updates have been really buggy especially with WiFi and BT. Mine works perfect right now and all I really want is to root it and remove the update file and turn off the update app. Thanks in advance for any advice.
paulsmcin said:
Wondering if I should update downloaded ota then root or will the update screw things up like locking my boot loader and installing things I don't want or that will make customizing more difficult or impossible? Have had real bad luck with Verizon ota's in the past when it comes to rooting, unlocking, jailbreaking etc... And from what I've been reading on other threads this and other nexus ota updates have been really buggy especially with WiFi and BT. Mine works perfect right now and all I really want is to root it and remove the update file and turn off the update app. Thanks in advance for any advice.
Click to expand...
Click to collapse
If you want root, first thing you should do is unlock the bootloader. Second thing you should do is read all the threads regarding root in the SuperSU subforum. Third thing is you want marshmallow because battery life, in my experience, is far better.
I haven't experienced any buggy WiFi or BT with either of my N6s. Just because you had bad luck in the past doesn't mean you'll have the same experience with this phone. The only bad luck you'll encounter would come from your own inexperience.
paulsmcin said:
Wondering if I should update downloaded ota then root or will the update screw things up like locking my boot loader and installing things I don't want or that will make customizing more difficult or impossible? Have had real bad luck with Verizon ota's in the past when it comes to rooting, unlocking, jailbreaking etc... And from what I've been reading on other threads this and other nexus ota updates have been really buggy especially with WiFi and BT. Mine works perfect right now and all I really want is to root it and remove the update file and turn off the update app. Thanks in advance for any advice.
Click to expand...
Click to collapse
Its a Nexus. Even Verizon ota's won't lock it. Update it, unlock the boot loader before or after. Flash back, flash forward, flash sideways. It is all up to you. The entire os/image is downloadable from Google, it is a fully ipen phone.
There are no widespread problems with Marshmallow. It is great. You get that impression because only the people with problems post.
So I would stop reading threads about problems and just read the threads about flashing and customizing.
Take the ota's up to the current version.
Unlock the bootloader.
Flash TWRP.
Flash systemless root version 2.65 from chainfire.
That will get you started.
Thanks for the advice all, did the updates, unlocked the boot loader & rooted. Easiest phone ever to mod !
Hi guys. I somehow messed things up really bad.
I was running a modded ROM, but decided I wanted to go back to unrooted stock. I followed this instructions in this video: https://www.youtube.com/watch?v=6avEPGWB8E0
Unfortunately, things didn't work out. When I tried flashing the files it kept saying "system not found". Now I'm stuck in recovery forever. If I try to press start, nothing happens. If I scroll up to factory, nothing happens either. If I look at the Bootloader logs, all it says is "failed to validate system image. Boot up failed".
The one good thing is that the phone recognizes being plugged into my computer (Windows 10), so maybe there's a small chance I can get my phone back. If you guys have a solution, please let me know, as I'm pretty distraught right now. Also hoping there's a chance I can get my photos back that are on the device, though that seems unlikely now.
Unrooted stock? I can possibly see going back to rooted stock, or at least a CF (rooted) stock-based ROM, but not unrooted stock. "Please make me a slave again. Please, I don't like owning my phone."
Do you still have TWRP custom recovery or do you only have stock recovery? If you have TWRP, use the File Manager and drag over a custom ROM from your PC, and flash it.
ChazzMatt said:
Unrooted stock? I can possibly see going back to rooted stock, or at least a CF (rooted) stock-based ROM, but not unrooted stock. "Please make me a slave again. Please, I don't like owning my phone."
Do you still have TWRP custom recovery or do you only have stock recovery? If you have TWRP, use the File Manager and drag over a custom ROM from your PC, and flash it.
Click to expand...
Click to collapse
Long story short, I'm a slave to Pokemon Go. I used to be super passionate about having my phone rooted and everything, but I found I wasn't really using the rooted features at all. I can completely understand the appeal of having it rooted, it's just not something I need right now.
Unfortunately I have the stock recovery, and nothing seems to be loading on it.
Xpwnage123 said:
Long story short, I'm a slave to Pokemon Go. I used to be super passionate about having my phone rooted and everything, but I found I wasn't really using the rooted features at all. I can completely understand the appeal of having it rooted, it's just not something I need right now.
Unfortunately I have the stock recovery, and nothing seems to be loading on it.
Click to expand...
Click to collapse
Is your bootloader still unlocked? Can you connect your phone via ADB and re-flash TWRP? Forget about Pokemon Go for now and just get your phone back to working.
Also with custom ROMs you can still run the ROM and UNroot your phone. (I know you can with CM.) No need to go back to stock, unless parent company of Pokemon is clueless and demands stock.
Well, seems they are clueless and doing what Android Pay does:
http://www.xda-developers.com/lates...blocks-rooted-devices-from-entering-the-game/
What Niantic has managed to do with the update is kill off the enthusiasm in users who had root but were not cheating. Root is used for many more things outside of cheating in a game, and to assume that all rooted users are cheaters is just silly.
_____
After some more reading around, it seems Niantic is actually using the SafetyNet checks to check for root. XDA Senior Member MaaarZ found the SafetyNetService being called in the game code. Niantic is really making users jump through the whole nine yards, as this is the same method employed by Android Pay. This means that if you do need to run Pokémon GO on a rooted device, you need to go through the whole Magisk and systemless root way. Or stop playing completely, because that is what Niantic wants you to do.
Click to expand...
Click to collapse
ChazzMatt said:
Is your bootloader still unlocked? Can you connect your phone via ADB and re-flash TWRP? Forget about Pokemon Go for now and just get your phone back to working.
Click to expand...
Click to collapse
First of all thanks for your prompt responses. I really appreciate it.
I've always sort of had trouble getting ADB to work. I'm pretty sure the only version ADB I have installed on my laptop is the Fastboot version I downloaded from the video I linked. As I'm typing this, I'm currently downloading Android SDK and RSDLite, though the process is taking a while.
I think my bootloader is unlocked, but I'm not entirely sure. I think when I installed the custom rom, root first came out on the turbo. The method I used was the Mofo method. If I need to install a more elaborate version of ADB I will do so, I just might need clarification on what particular version is most optimal to use.
Xpwnage123 said:
I think my bootloader is unlocked, but I'm not entirely sure. I think when I installed the custom rom, root first came out on the turbo. The method I used was the Mofo method. If I need to install a more elaborate version of ADB I will do so, I just might need clarification on what particular version is most optimal to use.
Click to expand...
Click to collapse
The MoFo method was not bootloader unlock, and it only worked on KitKat. Wow, you were still using MoFo?
Real bootloader unlock came via Sunshine ($25) last November 2015, and you needed at least stock Lollipop 5.1 with Verizon firmware SUTL-44. It also now works with Verizon SUTL-49.
If you never paid for Sunshine, then your bootloader was never unlocked.
However, using ADB you can re-flash stock firmware even with a locked bootloader.
Some Droid Turbo owners like @TheSt33v will be more help than me as to what version you should flash. I own three Quarks but not the Droid Turbo. But as long as you are flashing, might was well update to SUTL-49.
IF you can't find a good download of SUTL-49, here's at least SUTL-44. Thank @bhb27.
https://www.androidfilehost.com/?fid=24052804347843637
_______
Also, go read this.
How to Manually Official Firmware on any Motorola Device
http://forum.xda-developers.com/dro...force-how-to-manually-flash-official-t3282077
Even though written for the Kinzie, the concept and method is the same.
Xpwnage123 said:
First of all thanks for your prompt responses. I really appreciate it.
I've always sort of had trouble getting ADB to work. I'm pretty sure the only version ADB I have installed on my laptop is the Fastboot version I downloaded from the video I linked. As I'm typing this, I'm currently downloading Android SDK and RSDLite, though the process is taking a while.
I think my bootloader is unlocked, but I'm not entirely sure. I think when I installed the custom rom, root first came out on the turbo. The method I used was the Mofo method. If I need to install a more elaborate version of ADB I will do so, I just might need clarification on what particular version is most optimal to use.
Click to expand...
Click to collapse
You need neither the SDK nor RSDLite. If you're interested in unlocking your bootloader (and returning to pokemon go-ready stock in the process), follow my guide here: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684. If you don't want to unlock your bootloader, and you want to return to stock kitkat so that you can continue using mofo, let me know what build you're on (see "about phone" in your settings) and I can send you a link to the firmware package that you'll need. If you want to update to the latest firmware and you don't care about unlocking your bootloader (maybe ever), only follow section 0 of my guide and take whatever OTA updates you are given with the understanding that you'll probably never be able to unlock your bootloader again after taking them.
ChazzMatt said:
The MoFo method was not bootloader unlock, and it only worked on KitKat. Wow, you were still using MoFo?
Real bootloader unlock came via Sunshine ($25) last November 2015, and you needed at least stock Lollipop 5.1 with Verizon firmware SUTL-44. It also now works with Verizon SUTL-49.
If you never paid for Sunshine, then your bootloader was never unlocked.
However, using ADB you can re-flash stock firmware even with a locked bootloader.
Some Droid Turbo owners like @TheSt33v will be more help than me as to what version you should flash. I own three Quarks but not the Droid Turbo. But as long as you are flashing, might was well update to SUTL-49.
IF you can't find a good download of SUTL-49, here's at least SUTL-44. Thank @bhb27.
https://www.androidfilehost.com/?fid=24052804347843637
_______
Also, go read this.
How to Manually Official Firmware on any Motorola Device
http://forum.xda-developers.com/dro...force-how-to-manually-flash-official-t3282077
Even though written for the Kinzie, the concept and method is the same.
Click to expand...
Click to collapse
TheSt33v said:
You need neither the SDK nor RSDLite. If you're interested in unlocking your bootloader (and returning to pokemon go-ready stock in the process), follow my guide here: http://forum.xda-developers.com/droid-turbo/general/guide-how-to-unlock-bootloader-install-t3292684. If you don't want to unlock your bootloader, and you want to return to stock kitkat so that you can continue using mofo, let me know what build you're on (see "about phone" in your settings) and I can send you a link to the firmware package that you'll need. If you want to update to the latest firmware and you don't care about unlocking your bootloader (maybe ever), only follow section 0 of my guide and take whatever OTA updates you are given with the understanding that you'll probably never be able to unlock your bootloader again after taking them.
Click to expand...
Click to collapse
Thank you guys. I was able to revive my phone from the dead using your advice. Unfortunately, I lost all of the photos from my trip to Europe, but overall I'm happy my phone is back and running. That will be a lesson to me to be less lazy about backing up my data.
Once again, thank you very much.
Someone over in Resurrection Remix thread got Pokemon Go to work with Root Cloak:
Nitefire77 said:
Pokemon go works on my phone with rootcloak. Wasn't too difficult to get it working
Click to expand...
Click to collapse
You can ask him for details. So, you can still run a custom ROM if you wish...
Hello, I'm wondering if they've made any advancement on the Samfail root method for the Note 8 AT&T version. I'm finding that I'm running into circumstances where I need to be able to flash a zip. This is still not possible, correct?
2Tone23 said:
Hello, I'm wondering if they've made any advancement on the Samfail root method for the Note 8 AT&T version. I'm finding that I'm running into circumstances where I need to be able to flash a zip. This is still not possible, correct?
Click to expand...
Click to collapse
Just check the Samfail thread. It's up to v3 for the latest 7.1.1 software we have. It does not root Oreo, but it will downgrade you from it back to 7.1.1 to be able to root.
Jammol said:
Just check the Samfail thread. It's up to v3 for the latest 7.1.1 software we have. It does not root Oreo, but it will downgrade you from it back to 7.1.1 to be able to root.
Click to expand...
Click to collapse
Thank you, Jammol. I'm actually rooted, but I was out of the loop due awhile and I was wondering if full root had been managed. They finally achieved it on the Note 5 AT&T version, only after I got rid of it. Hoping lightning will strike twice, you know?
2Tone23 said:
Thank you, Jammol. I'm actually rooted, but I was out of the loop due awhile and I was wondering if full root had been managed. They finally achieved it on the Note 5 AT&T version, only after I got rid of it. Hoping lightning will strike twice, you know?
Click to expand...
Click to collapse
Full root as in TWRP and such? We have full root but with a locked bootloader. Flashfire can be used to flash stock roms for the Snapdragon variant. Safestrap was just released for it as well but currently only the "Stock" slot can be used. And yes the 80% battery limit is very much still there.
So I can actually flash custom roms with this lock bootloader on this variant? Also, safestrap will allow me to flash custom roms as well?
Jammol said:
Full root as in TWRP and such? We have full root but with a locked bootloader. Flashfire can be used to flash stock roms for the Snapdragon variant. Safestrap was just released for it as well but currently only the "Stock" slot can be used. And yes the 80% battery limit is very much still there.
Click to expand...
Click to collapse
So I can actually flash custom roms with this locked bootloader on this variant?. Also, safestrap will allow me to flash custom roms as well? I hope I understand you right, Jammol. To be able to finally do that would make me a happy man. Also, is there any advantage to using Safestrap over Samfail? I used Safestrap with my S5.
2Tone23 said:
So I can actually flash custom roms with this locked bootloader on this variant?. Also, safestrap will allow me to flash custom roms as well? I hope I understand you right, Jammol. To be able to finally do that would make me a happy man. Also, is there any advantage to using Safestrap over Samfail? I used Safestrap with my S5.
Click to expand...
Click to collapse
Correct, but you can't get to Safestrap without being rooted first, which requires Samfail.
Jammol said:
Correct, but you can't get to Safestrap without being rooted first, which requires Samfail.
Click to expand...
Click to collapse
Thanx. I'm Samfail rooted already. Going to install safestrap. Can you direct toward some custom stock roms that might flash? I've had no luck thus far.... And thank you for all the info. If not for you I wouldn't even know Safestrap and flashing was even available.
2Tone23 said:
Thanx. I'm Samfail rooted already. Going to install safestrap. Can you direct toward some custom stock roms that might flash? I've had no luck thus far.... And thank you for all the info. If not for you I wouldn't even know Safestrap and flashing was even available.
Click to expand...
Click to collapse
Currently there are only 2 roms we can flash. FENNEC and Culpeo.
FENNEC is based on the U1 (unlocked firmware), so there's no carrier bloatware.
Culpeo is based on U or carrier firmware. The bloat will come with the CSC you flash for your particular firmware. There are CSC edits in there for things such as VoLTE, Wi-Fi Calling, etc.
These are both based on the latest 7.1.1 version respectively. I have personally ran both but I was partial to FENNEC because I hate carrier bloat.
Both are located on the Development section. There are more roms coming so don't be deterred.
Jammol said:
Currently there are only 2 roms we can flash. FENNEC and Culpeo.
FENNEC is based on the U1 (unlocked firmware), so there's no carrier bloatware.
Culpeo is based on U or carrier firmware. The bloat will come with the CSC you flash for your particular firmware. There are CSC edits in there for things such as VoLTE, Wi-Fi Calling, etc.
These are both based on the latest 7.1.1 version respectively. I have personally ran both but I was partial to FENNEC because I hate carrier bloat.
Both are located on the Development section. There are more roms coming so don't be deterred.
Click to expand...
Click to collapse
Jammol, I really appreciate your responsiveness and all of the knowledge you've provided. Thanks you!
Jammol, trying to figure out why Safestrap won't take. Busybox up and running. After hitting install it goes thru its paces and says I install successfully, or something similar, but above that where it says State it still reads not installed. I see it with granted access in Su. But when rebooting I do not get the splash screen. Any ideas?
2Tone23 said:
Jammol, trying to figure out why Safestrap won't take. Busybox up and running. After hitting install it goes thru its paces and says I install successfully, or something similar, but above that where it says State it still reads not installed. I see it with granted access in Su. But when rebooting I do not get the splash screen. Any ideas?
Click to expand...
Click to collapse
I have the free version of Busy Box installed. Tried installing the pro version in case that would somehow facilitate the installation of Safestrap and the pro version won't install either. The notice suggests I try installing in another location. Not sure how to do that. Can anyone advise me on this and /or how I can get Safestrap to install?
2Tone23 said:
Jammol, trying to figure out why Safestrap won't take. Busybox up and running. After hitting install it goes thru its paces and says I install successfully, or something similar, but above that where it says State it still reads not installed. I see it with granted access in Su. But when rebooting I do not get the splash screen. Any ideas?
Click to expand...
Click to collapse
In the Safestrap thread there were a few users that had that issue occur. I don't know what the Fix was for them, if it was fixed, as I haven't followed that development for a few days now. I suggest giving the OP of that thread a full read through again and read through the comments/replies of what others have done so far to solve their issues.
Thanx Jammol. Actually perused that before my last post. Will look again. Hope I missed something, but I dont think so.
Jammol said:
In the Safestrap thread there were a few users that had that issue occur. I don't know what the Fix was for them, if it was fixed, as I haven't followed that development for a few days now. I suggest giving the OP of that thread a full read through again and read through the comments/replies of what others have done so far to solve their issues.
Click to expand...
Click to collapse
Thanx Jammol. Actually perused that before my last post. Will look again. Hope I missed something, but I dont think so.
2Tone23 said:
Thanx Jammol. Actually perused that before my last post. Will look again. Hope I missed something, but I dont think so.
Click to expand...
Click to collapse
No problem. Let me know. There are some bugs with it though so posting Safestrap related questions there would be the best thing to do. I merely fiddled with it for about a day at most and had to return to stock(work reasons).
Thanks, J. Really appreciate your feedback. Will let you know if something gives.
Jammol said:
No problem. Let me know. There are some bugs with it though so posting Safestrap related questions there would be the best thing to do. I merely fiddled with it for about a day at most and had to return to stock(work reasons).
Click to expand...
Click to collapse
Thanks, J. Really appreciate your feedback. Will let you know if something gives.
(Eventually, I'm going to get this reply thing right. ?)
2Tone23 said:
Thanks, J. Really appreciate your feedback. Will let you know if something gives.
(Eventually, I'm going to get this reply thing right. ?)
Click to expand...
Click to collapse
Lol, no problem.