yashsingh1/xdaforums huggingface dataset:
[Verizon Motorola Droid Turbo General] sd_shadow:
I've used RSD Lite on my Windows 10 PC, many times, without issues, but several people have posted that it won't work for them
[Verizon Motorola Droid Turbo General] CCaseXX:
Jcase is the man. Got everything sorted, thanks!!!
[Verizon Motorola Droid Turbo General] dwh2o13:
Thanks. Awhile back right after i moved to Windows 10 I had an old Droid Razr Max that i wanted to return to stock firmware. To my surprise found out that rsdlitehad compatibility issues with Windows 10. RootJunky did a vid on this, and I ended up doing his Manuel scrub tutorial to get the job done.

Just didn't know if things had changed with compatibility? Was curious.. As a matter of fact you were a big help to me when i was first learning how use RSDLite. Much thanks!
[Verizon Motorola Droid Turbo General] dwh2o13:
[MENTION=4267571]sd_shadow[/MENTION] Sorry, forgot to quote you in my last post.
[Verizon Motorola Droid Turbo General] Sulphur21:
Step 2: Unable to break bootloop

I am in the same exact boat as OP.

"I unlocked my phone using sunshine and it worked, afterwards my phone booted and showed the "Warning Bootloader Unlocked" banner, so i was set... except... when I load in fast boot and upload the TWRP file, once i select recovery mode it returns to the bootloop and continues to just show the prompt "Warning Bootloader Unlocked" over and over."

As an additional background, I am using the verizon XT1254 with marshmallow and unlocked boot loader using Sunshine. That, was a success. Status on my phone is "Device is unlocked. Status code: 3". When I tried to flash the TWRP file, I get the following message.

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash recovery TWRP.img

(bootloader) slot-count: not found

(bootloader) slot-suffixes: not found

(bootloader) slot-suffixes: not found

(bootloader) has-slot:recovery: not found

target reported max download size of 536870912 bytes

sending 'recovery' (14108 KB)...

OKAY [ 0.468s]

writing 'recovery'...

OKAY [ 0.218s]

finished. total time: 0.702s

And I rebooted into recovery and the loop continues. I checked to see that the TWRP file is TWRP.img.

Am I missing something? Any suggestions on how to get out of this loop?

Thanks !
[Verizon Motorola Droid Turbo General] beaups:
You need to follow the last instruction in the temproot thread (remove the temproot with fastboot)
[Verizon Motorola Droid Turbo General] Sulphur21:
Bootloop problem solved!

In section 1, step 9 I entered the command to disable the temporary root exploit incorrectly. I didn't enter the quotes at the end of the command :eek:

fastboot oem config fsg-id "" .

Correcting that fixed my issue.

Thanks !
[Verizon Motorola Droid Turbo General] mspt_99:
done BUT

so I followed the instructions and it all worked perfect the first time form my turbo. I confirmed my phone what rooted with root checker. now I want mobile hotspot working. is there a different TWRP.img to install? I"m fairly noobish, just good enough to follow these instructions. I have used the MOFO in the past to root successfully and that came with the hotspot enabled.
[Verizon Motorola Droid Turbo General] mspt_99:
SWEET. After lots of reading and re-reading and following instructions all is well. I still have root, no black screen of death which I thought I had for a while and hotspot enabled so I can use my unlimited data plan that I still have grandfathered in. Thank you for your guidance.

1. one weird thing is that root checker basic state "root access is not properly installed" I cant see how that is since everything worked? Build number is Computerfreek274....1.0.8.

2. can I delete from downloads and uninstall sunshine, magisk that I used?

TY

dan
[Verizon Motorola Droid Turbo General] ChazzMatt:
Glad it's working for you.

You can uninstall Sunshine. That was only used to unlock your bootloader. You won't need it any more. (Please don't re-lock your bootloader!)

I don't use Magisk, so someone else will have to answer that question. I use SuperSu myself, as I don't really care about Android Pay and stuff that won't work with visible root. Magisk is usually used to hide root and bootloader unlock.

If you ever decide to use SuperSu, with Motorola Marshmallow you first have to root with a specific older version of SuperSu, then you can update to the newest -- or you will get bootloop. I don't want to confuse you with too many details, especially if you are not using SuperSu and are happy with Magisk root. I'm only mentioning this because if you installed that Computerfreek274 ROM, it's very possible you did use SuperSu (that older version is mentioned in the installation instructions, I believe) and that error message means it's conflicting with Magisk or something? Magisk has its own root functionality. But you would know better than me what you have installed.

Currently in this thread [MENTION=5901115]TheSt33v[/MENTION] only mentions Magisk as it does cloak bootloader unlock and does have root functionality, but I'm more old-school and like SuperSu.
[Verizon Motorola Droid Turbo General] TheSt33v:
If you want to uninstall magisk, flash the uninstaller package here: http://tiny.cc/latestuninstaller
[Verizon Motorola Droid Turbo General] lightcs4d:
No wifi or cell

I must admit, I haven't been rooting my phone since I purchased a Droid turbo in 2013. I am fairly technically adept, and haven't finished the messages in this thread. My current state is no cell or wifi signal. I also can't get into TWRP, as it just goes back to a message stating the bootloader is unlocked. Any simple fixes before I just swap out the phone?

Thanks,

Chris

Edit: Installed Lineage 14.1 and regained web. The Sim is not detected so I am working on that one. It looks like a common issue that needs a library file replaced. I'll work on getting it fixed or downgrade Lineage to version 13 and see how it goes.
[Verizon Motorola Droid Turbo General] ChazzMatt:
If TWRP was successfully installed, you can always get to it manually by turning off the phone, then pressing volume down and power button the same time. That will boot you up the bootloader screen. From there you can arrow up with the volume buttons to choose recovery, and select that with a brief tap of the volume key.

Did you install SuperSu? If so, installing the latest version first causes the bootloop you describe. There's

specific version of SuperSu you must install first, reboot to verify, then you can update to the latest.

Confirm to me you tried to install SuperSu and I'll tell you more, if you or go look at that link. This is just a guess on my part at this point.

By the way, Droid Turbo was released late 2014 (October/November). ;) Not 2013. Of course many other phones were labelled as "Droids".
[Verizon Motorola Droid Turbo General] lightcs4d:
Seems like forever ago. I had my old Droid rooted but never bothered with the Turbo. Life got too busy.

I was able to get into TWRP this morning. I should have put that in the update. I added Magisk version 14.0 and root explorer just now, and have root access. The sim is the only issue I am chasing down.

Thanks for the response.
[Verizon Motorola Droid Turbo General] ChazzMatt:
Glad you got part of it solved. And you have wi-fi now? It's only the cellular signal/data you are having issues with?

By the way you need to get rid of the bootloader unlock warning. ;) No need to see that every time you reboot the phone! Here's

two ways: ADB or TWRP.
[Verizon Motorola Droid Turbo General] lightcs4d:
I'll take care of the bootloader warning once the sim is working. Yes, that is the only issue to fix. The rom looks pretty good. It is fairly fast and it is nice to get rid of the pre-installed apps. Gapps has been installed as well.
[Verizon Motorola Droid Turbo General] ChazzMatt:
Oh, hold on! You installed a custom ROM? You didn't mention that! Check your APN, then.

Also check your settings to make sure cellular data is enabled (off/on toggle switch).

I assumed you were still on stock firmware.

The custom ROMs based on CM/LOS have a quirk where Straight Talk MVNO is the default APN instead of Verizon (S comes before V). IF you are a Verizon customer you need to change it to Verizon Internet. (Unless you are a Straight Talk customer, in which case I feel sorry for you.)

Before we assume anything else, to help you...

Are you a Verizon customer?

Which custom ROM did you install?

Which Gapps did you install?

We also might need to move the discussion to that ROM thread, as you have now successfully unlocked your bootloader, installed TWRP and rooted your phone.
[Verizon Motorola Droid Turbo General] lightcs4d:
Sorry, I should have made that known. Bootloader is definitely unlocked and custom rom installed. You are correct, this is not longer an issue of the bootloader, as that was resolved this morning. I'll check out the forums for Lineage issues and see what I can find. I really appreciate the help. I no longer see the boot loader warning message - decided to dump it before fixing the cell issue.

---------- Post added at 09:27 AM ---------- Previous post was at 09:16 AM ----------

Closing the loop on my questions. Bootloader was fully unlocked and fixed when I ran the final command with the quotes at the end (yes, I needed to fully read the instructions). I finally reflashed Lineage 14.1 again due to the SIM not being recognized, since I installed the wrong radio package and made it worse. This fixed my SIM issue and the phone is fully functional. A big thanks to ChazzMatt for helping out with this issue.
[Verizon Motorola Droid Turbo General] ChazzMatt:
You're very welcome! Glad it's all fixed. One suggestion. Boot into TWRP and make a backup of your current system, so if something goes wrong you have a point in time to restore. Takes like 5 minutes to make backup, but it's like having a magical time machine. Too many people don't do that, but it's helped me tremendously. Ooops! No problem, restore!

I try to make a recent backup every few days or so, and then delete the older one. You don't have to do it that frequently -- even just having one made right now is great. But when it restores, it will restore everything to the point in time you made the backup. I make one for my wife's phone every couple of weeks. It's a good habit to get into.
[Verizon Motorola Droid Turbo General] lightcs4d:
Great advice.i will do that now so I don't wait until I regret not doing it.
[Verizon Motorola Droid Turbo General] Faethor420:
First off, I'll be the first to admit - I'm an idiot!!

I was happily following the instructions, but Sunshine failed my first attempt. Some brainfart told me to check that Magisk installed properly. I ran the app and observed it was an older version, so like a moron I blindly chose to update Magisk and chose the "recommended" option, which began to patch the boot image!! Now when I boot, it goes straight to the fastboot mode. I've been able to get from there to recovery but no further.

Am I screwed or is there an RSD recovery option or something similar to recover stock?
[Verizon Motorola Droid Turbo General] sd_shadow:
Why are you installing Magisk before unlocking the bootloader?

Flash the firmware as described in post 1.
[Verizon Motorola Droid Turbo General] Faethor420:
Followed the instructions on the auto#initroot page. Either way, damage is done.

As for the flash, every time I try, almost every component fails. ADB on the laptop recognizes my phone, and simple fastboot commands run, so I've got no idea why the flash fails.
[Verizon Motorola Droid Turbo General] ChazzMatt:
What [MENTION=4267571]sd_shadow[/MENTION] is saying is do one step at a time. In this forum, the temp root is only to used to allow Sunshine to unlock the bootloader. Sunshine is then only used to unlock the bootloader. After that, you do not need the temp root (be sure to run the end commands), and after that you do not need Sunshine any more.

Magisk is something you should be concerned with only AFTER you have successfully completed the first and seconds steps.

Ah, I see the problem. After [MENTION=5901115]TheSt33v[/MENTION] revised this bootloader unlock guide to include the temp root (with a link to the temp root), the OP of the temp root guide changed those instructions -- to include Magisk from the very beginning, which may conflict with Sunshine -- so the link in this bootloader unlock guide goes to somewhat confusing instructions for temp root...

All you want to do at first is install the temp root. Do not install Magisk until much later.

Temp root mentioned in this guide is ONLY to allow Sunshine to run to unlock the bootloader.

You should probably uninstall Magisk for now just to make sure nothing is conflicting. In THIS guide, Magisk is clearly step 3 if you want it.

If you have paid for Sunshine [MENTION=2376614]jcase[/MENTION] and the Sunshine team will offer tech support to you. However, you should make sure you are fully updated on Verizon firmware. There's been times people strangely had mis-matched system elements, newer this, older that due to some kind of botched OTA installation. The answer was to ADB flash full latest Verizon firmware, then Sunshine could work properly. Section 0 (zero) of this guide tells you how to make sure your firmware is completely up to date.
[Verizon Motorola Droid Turbo General] TheSt33v:
Guide has been revised to advise the reader not to mess with Magisk during the unlock process.
[Verizon Motorola Droid Turbo General] Faethor420:
Thanks guys, but that doesn't help me out at this point. My phone no longer boots, just goes straight into fastboot mode. And my attempts to flash the firmware in step 0 constantly fail.

My thought: since the firmware file is for -5, is there a firmware available for -5-5? Haven't seen that one around.
[Verizon Motorola Droid Turbo General] TheSt33v:
Flashing -5 will fail if you're on -5-5. The link for -5-5 is here:

https://mega.nz/#!a1ZwTY6Z!2gLd7yVAu7vTrJ_cU_OjnxUCN7tWEYegIbelI-gSJWc
[Verizon Motorola Droid Turbo General] Faethor420:
Sweet! That restored my phone to operational once more!!

However, now that its working, the unlock isnt! In fact, Sunshine won't even get past the tests! Do I need to redo step 0 or skip past it completely? Here's what I did:

Ran the auto#initroot steps

Installed Sunshine

Ran Sunshine

it never even asked for root access.

Went back to PlayStore and installed SuperSU, which appeared to be functional

re-ran Sunshine, still sticking

I even went bak into settings, enabled Dev Mode, OEM Bootloader unlocking, ADB Debugging and tried again.

Ugh, I hate when things don't go smoothly, but at least I've go a way to recover if I screw it up badly again. Thanks a ton for that!

Update: GOT IT!!! Unlocked and running TWRP. Now on to check out ROMs. Any suggestions? Prefer something with over clocking and fun features.
[Verizon Motorola Droid Turbo General] nnjimmy59:
I've been running NepoRood's Nougat ROM. I think it's great. Very stable.
[Verizon Motorola Droid Turbo General] mspt_99:
need help please

so I successfully rooted my Droid Turbo, model XT1254 using this method but my wife's phone had the build MCG24.251-5-5 on hers so i had to do those extra steps.

i installed sunshine and did the extra step to gain temp root but then i got stuck in bootloop.

currently i am stuck in bootloop. i didn't panic and did the "fastboot oem config fsg-id" command and then restarted but it didn't work. i keep getting bootloop.

i thought I would flash the TWRP.imp thinking maybe i was good but that didn't work either.

i tried to factor reset since its early in the game and that didn't work either.

ugh.

---------- Post added at 12:25 AM ---------- Previous post was at 12:02 AM ----------

ok so i am replying to myself. I flashed the full firmware again from step one and i hit start but still in bootloop

---------- Post added at 12:45 AM ---------- Previous post was at 12:25 AM ----------

Wont let me into recovery mod either.

---------- Post added at 12:49 AM ---------- Previous post was at 12:45 AM ----------

wont identify my device in fastboot mode.

---------- Post added at 12:59 AM ---------- Previous post was at 12:49 AM ----------

no it recognizes my device and i can flash the firmware again but still stuck in bootload after that.
[Verizon Motorola Droid Turbo General] beaups:
The command to remove the temproot is

fastboot oem fsg-id " "

The quote space quote is there for a reason. You need to run the command with that part.
[Verizon Motorola Droid Turbo General] ChazzMatt:
and it's double quotation marks after the fsg-id, right? He only typed one set.
[Verizon Motorola Droid Turbo General] beaups:
I don't think he did any of them, he wrapped the entire command in quotes for the post, I believe
[Verizon Motorola Droid Turbo General] TheSt33v:
There should be no space in between the quotes. The way it is written is the way it should be done. Read carefully.
[Verizon Motorola Droid Turbo General] mspt_99:
so I see that error. I had already reformated phone to factory since I had been monkeying around and I simply started fresh.

NOW, so I am stuck in Sunshine Testing section 1:8.

I have WIFI on. I an not connnected but I do have the sim card in.

in looking at the phone, after section 0:11 should my build number change from the original MCG24.251-5-5?
[Verizon Motorola Droid Turbo General] 34Ford:
I killed my old turbo so I bought another one, however this one is 5.1 SU3TL-39.

How do I get to SU4TL-44 or SU4TL-49

I would like to do the same to this newer one like my old one. I used this.

https://xdaforums.com/droid-turbo/general/psa-droid-turbo-android-6-0-update-t3379894

Thanks
[Verizon Motorola Droid Turbo General] Nido221:
My mobile is Totally screwed.

I was running resurection remix 7.1.

Tried to restore the data backup in twrp after factory reset.After that mobile is in continuous boot loop mode.Reflashed the TWRP recovery with the help of Adb and unchecked the system partition read only.Flash many roms like Aokp,RR,cR droid but mobile still in boot loop.

Any help.

Note:one strange thing is tha boot logo remains unchanged after flashing any rom and do not change into default boot logo.

---------- Post added at 08:43 AM ---------- Previous post was at 08:39 AM ----------

Get guidance from first section of this thread stepswould be under .

Download and install minimal adb,fast boot and Su 4tl-49 and flash it via adb command...
[Verizon Motorola Droid Turbo General] 34Ford:
I finally did get back to a rooted Turbo on Lollipop like I wanted. I am good for now. Wished the Moto Z Force could be rooted.
[Verizon Motorola Droid Turbo General] TheSt33v:
Flash this using fastboot (not adb) to go back to the latest stock firmware: https://xdaforums.com/droid-turbo/development/fxz-official-stock-firmware-6-0-1-mcg24-t3569334

Let it boot once before you start flashing things again. Be patient when it is booting for the first time. It can take 5-10 minutes.

Also, it's not strange that the boot logo is not changed after flashing all the roms you flashed. The boot logo is determined by logo.bin, and no roms flash this file. If you're actually talking about the boot animation and not the boot logo, then that is strange.
[Verizon Motorola Droid Turbo General] wapda11:
Guys, I am facing an issue. I ran "auto#initroot.windows.bat" and rebooted my Droid Turbo. After reboot, when I run sunshine, the app launches but it shows an empty white screen. I waited 15 minutes but its still stuck on the white screen. Only the app gets stuck on the white screen, the phone itself keeps working as normal. Another thing I noticed is that while the app is stuck in white screen the phones becomes sluggish.

If I revert the temproot by running fastboot oem config fsg-id "", the sunshine app starts working again. No empty white screen problem.

Things I have tried so far

1. Reflashed "mcg24.251-5-5" rom using mfastboot tools.

2. Installed supersu 2.63 apk and re-ran Sunshine in hopes that it would not get stuck on white screen.

I ran the the temp root commands manually and I got permission denied error.

fastboot oem config fsg-id "a initrd=0x110BEE50,2483340"

fastboot flash initroot xt1254_quark_vzw_mcg24.251-5-5.initroot

fastboot continue

Output:

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash initroot xt1254_quark_vzw_mcg24.251-5-5.initroot

target max-download-size: 512MB

sending 'initroot' (4882 KB)...

OKAY [ 0.155s]

writing 'initroot'...

(bootloader) Permission denied

FAILED (remote failure)

finished. total time: 0.159s

Please help!!
[Verizon Motorola Droid Turbo General] beaups:
Uninstall supersu. Install magisk manger, but be sure to NOT update anything if magisk manager prompts you to.
[Verizon Motorola Droid Turbo General] wapda11:
Thanks, It worked
[Verizon Motorola Droid Turbo General] IllestminatiV2:
ive tried this too, but with no avail

C:\Users\Illestminati\Downloads\Minimal ADB and Fastboot>fastboot flash initroot xt1254_quark_vzw_mcg24.251-5-5.initroot

(bootloader) slot-count: not found

(bootloader) slot-suffixes: not found

(bootloader) slot-suffixes: not found

(bootloader) has-slot:initroot: not found

target reported max download size of 536870912 bytes

sending 'initroot' (4882 KB)...

OKAY [ 0.266s]

writing 'initroot'...

(bootloader) Permission denied

FAILED (remote failure)

finished. total time: 0.285s
[Verizon Motorola Droid Turbo General] FaizanMustafa:
I was using Samsung j7 and recently bought this Droid turbo and I want to install custom rom on this phone as I did before with my j7 the problem is to unlock bootloader on j7 I just unlocked oem and then used Odin to install twrp

Why can't I do the same thing with this phone ? i know Odin is for Samsung devices but there is still an option to unlock oem under develpors option on this phone as well so I'm confused as to follow these steps or not I want to install twrp please can anyone guide me ? Thanks

I'm running android 6.0.1 marshmallow

System version:24.91.5.quark_verison.verison.en.us

Build number. :mcg 24.251-5-5
[Verizon Motorola Droid Turbo General] beaups:
Where in the instructions are you seeing anything about "fastboot flash initroot"??
[Verizon Motorola Droid Turbo General] IllestminatiV2:
my bad, i should have said that i am running mcg24.251-5-5 and that is part of the temproot, which is linked for use before sunshine, i just wanted to know if anyone could help with the (bootloader) Permission denied

FAILED (remote failure) part, happens when flashing anything
[Verizon Motorola Droid Turbo General] beaups:
That error is normal.
[Verizon Motorola Droid Turbo General] am03b4:
it was done, yet ?

if haven't maybe this post will help :

also this error "(bootloader) Permission denied" is normal
[Verizon Motorola Droid Turbo General] TheSt33v:
Because your Samsung J7 did not come from Verizon, and Verizon does not allow bootloader unlock. All Droid Turbos come from Verizon.

You're absolutely right. Different devices can have different unlocking procedures, and it does get very confusing. If only there was an unlocking guide out there somewhere specifically for the Droid Turbo that could walk you through it! Someone should write one up someday...
[Verizon Motorola Droid Turbo General] beaups:
Lol, but too bad your sarcasm will get lost ;)
[Verizon Motorola Droid Turbo General] TheSt33v:
I've never developed a thing in my life. I'm just good at Googling. Check back in a few months after I finish these Kotlin courses that I'm taking though :cool:
[Verizon Motorola Droid Turbo General] TheSt33v:
Your current configuration is compatible. With a locked bootloader, there is nothing that you could have done to make it incompatible. I can't even think of a way to mess it up with an unlocked bootloader, for that matter. The link that I included is the full firmware package, not the OTA update. If you're interested in flashing the images in the firmware package manually for some reason, right click on the .bat file and select edit. Then you can read all of the commands that the .bat file is performing automatically and do them using Fastboot manually. I wouldn't recommend that though.
[Verizon Motorola Droid Turbo General] rlb81:
I'm just looking to get unlocked/twrp etc etc. so I'll follow the outline you have in the first post. Thanks again!