Database Develop

[TOOLKIT] Shield Root and More! [Shield RAM V1.1]

Shield RAM V1.1
<<< Shield Root and More >>>
I'm happy to present my first release.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
FEATURES:
◄Unlock Bootloader►
◄Flash ClockWorkMod Recovery/Stock Recovery►
◄Root►
◄Debloat System►
◄After all it's a gaming console, who needs calendar's and books and crap ►
◄Restore to Factory Stock (erases all user data in the process)►
◄More to Come!!!►
NEWB INSTRUCTIONS:​Make sure you have the naked driver installed from this THREAD first. There is an install guide in the thread describing how to get the driver's configured properly. However I'll try to sum it up. Once you have USB Debugging enabled windows will try finding the driver's but won't be able to, go into device manager and right click the device you need to install the driver for. For the ADB driver right click it and go to Update Driver Software >>> Browse my computer for driver software >>> Click the browse button and find the folder where you have extracted the naked drivers. Hit next, it should scan the folder, find the driver and then install it. For the fastboot driver you need to power your shield off, boot into the bootloader, and then plug your USB Cable in. Windows should look for the driver software and once again, it won't be able to find it. Do the same thing, go to device manager and right click Fastboot and select Update Driver Software. Select Browse my computer for driver software again but this time select Let me pick from a list of device drivers on my computer. Highlight Show All Devices and select Next. Select Have Disk at the bottom, and then Browse. Find the Naked Driver folder once again and then select android_winusb.inf and hit Open. Select ok, scroll to the bottom, highlight Nvidia Shield Fastboot, hit Next and accept the warning dialog. The Fastboot driver should now be installed. Extract Shield RAM.zip, open the folder, and all you have to do at this point is double click Shield RAM.exe to start the process. I made this about as simple as it get so someone with no rooting experience should have no problem. Happy Modding!!!
ADVANCED INSTRUCTIONS:
Make sure to have your adb and fastboot driver's installed, start Shield RAM
DISCLAIMER:​If you do not know what root is, or have no need to use root, then you probably shouldn't be rooting your shield. I have tested this multiple times, and on multiple different shield units. This tool should be 100% safe however when it comes to flashing/rooting, modifying android device's in general there are certain inherent risks involved. I take no liability towards your device and the harm you could potentially cause to it. By now we should all know the risk involved with rooting, flashing, etc.
▲▲▲!!!AVAST AND POSSIBLY OTHER ANTIVIRUS PROGRAMS WARNING!!!▲▲▲
Avast wanted to run this in sandbox mode, if yours does the same let it sit for about 20 seconds and then hit continue execution.
Not really sure why it's doing it, I dont think Kwongger's tool tripped my avast.​
Credits/Thanks:
Minimal ADB and Fastboot - Shimp208
CWM Recovery - Clockworkmod and Agrabren for porting it to the shield
Kwongger - Using his toolkit is what made me want to make my own​
<<< DOWNLOAD >>>​
Feel free to ask any question's, post any comment's or concern's, or make suggestion's for thing's you might like to see
Donation's are never expected,
and always appreciated. Please
leave your XDA username in the
field box so that I can say thank
you here for it.
THANK YOU FOR DOWNLOADING!!!​

Changelog for 1.1:
With all the people not wanting to update to 77 I left 68
Changed some of the messages that are echoed
Added Koush's superuser App
Added a failsafe so if a wrong key is entered the program exits
Example:Requires a Y/N input if you hit 6 or M it will exit​
Donation List
Budokaiboy
THANK YOU VERY MUCH!!!

Hey, are you planing on add an option to "ota ready" the device? You need to create a script that flash system, boot and recovery from stock, without a factory reset or userdata flashing, so, you can full unroot and full disable all system level changes in order to update I personally do this on my GF nexus 7 and my shield and everything work great

Antara33 said:
Hey, are you planing on add an option to "ota ready" the device? You need to create a script that flash system, boot and recovery from stock, without a factory reset or userdata flashing, so, you can full unroot and full disable all system level changes in order to update I personally do this on my GF nexus 7 and my shield and everything work great
Click to expand...
Click to collapse
There's an option to flash it back to the newest ota, but ya changing that will be easy. And you just gave me a good idea too.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.

Very nicely done always glad to see people developing tools for the community, and intergrating Minimal ADB and Fastboot into their projects!

shimp208 said:
Very nicely done always glad to see people developing tools for the community, and intergrating Minimal ADB and Fastboot into their projects!
Click to expand...
Click to collapse
Thanks alot. Your tool made it much easier to get everything up and running

Just finished adding Wipe and No Wipe System Restore options for the next release.

Thanks for your work , but one question the CWM recovery that will be flashed with your script is the recovery with the OTA installation allowed ?, another think the stock recovery is the 4.3 recovery ?, the last time i flashed a custom recovery to my shield i had to return out of the box to get all the new otas

Thank You so much OP! I just got my SHield about 2 weeks ago and thought all Dev was dead for it. Glad to see someone stilling messing around with stuff.:good:

Both of you, are most welcome. I enjoyed putting together, and I enjoy it even more when I hear people are using it.
psycho1200 said:
Thanks for your work , but one question the CWM recovery that will be flashed with your script is the recovery with the OTA installation allowed ?, another think the stock recovery is the 4.3 recovery ?, the last time i flashed a custom recovery to my shield i had to return out of the box to get all the new otas
Click to expand...
Click to collapse
Im misunderstanding your first question but ya the stock recovery you can flash is 4.3 i think i mentioned it somewhere but i need to go back and make sure i do have it mentioned in the thread and in the RAM file. Maybe I'll go back and add an option for the 4.2 recovery since there are probably still a few shields using it. In my next release There is a no wipe option for system recovery so it wont touch any of your apps or data and it will flash your device back to stock, remove root and the supersu app, making it OTA ready.
synplex said:
Thank You so much OP! I just got my SHield about 2 weeks ago and thought all Dev was dead for it. Glad to see someone stilling messing around with stuff.:good:
Click to expand...
Click to collapse
Oh yeah, there's a little bit of life left in the shield. I use to have the model of galaxy s4 that had the exploitable bootloader, but the speaker went out and warrantied it, so lost the aforementioned and all I really have on it now is root. Since the shield is easily mod-able I decided to start doing some stuff up for it. I do have a couple of other things planned for it :thumbup:

Attention K-Mart Staff! Massive clean up in Aisle 6!!
Ok, all cleaning done from the very first mention of the dispute. Sorry if some good arguments got caught up in the cleaning process, but in reality, they had absolutely "0" to do with the tool's functionality (issues, features, bugs, etc)
If you do not like a tool, for whatever reason, kindly move along to something that more suites your needs, Without.. posting things that have nothing to do with the tool itself. And this includes "all" parties who participated.
Keep it On Topic folks.
Cheers
MD

Thanks.
Nvidia Shield Root and More
Doing a little bit of reading goes a long way.

Do I need to unlock the Bootloader first before flashing Recovery and Super SU? also does unlocking the bootloader remove all installed apps? I just want root access. Thanks in advance

rylen said:
Do I need to unlock the Bootloader first before flashing Recovery and Super SU? also does unlocking the bootloader remove all installed apps? I just want root access. Thanks in advance
Click to expand...
Click to collapse
Yes you have to unlock the bootloader before doing root. It states right in the menu i believe the order theyre presented in is also the flashing order. Unlocking bootloader does basically do a factory data reset so yes youll lose everything in the process as well. Hope i answeres all your questions
Nvidia Shield Root and More
Doing a little bit of reading goes a long way.

hexitnow said:
Yes you have to unlock the bootloader before doing root. It states right in the menu i believe the order theyre presented in is also the flashing order. Unlocking bootloader does basically do a factory data reset so yes youll lose everything in the process as well. Hope i answeres all your questions
Nvidia Shield Root and More
Doing a little bit of reading goes a long way.
Click to expand...
Click to collapse
Thanks :good: I'm just making sure because I've already put a lot of apps and don't want to reinstall everything, but I went ahead and did all the steps because I really want to have root access. I'm currently reinstalling my apps now. Thanks again for making a simple program for noobs like me my Shield finally have root access (also debloated ).
I apologize for my bad grammar, English is not my native language.

rylen said:
Thanks :good: I'm just making sure because I've already put a lot of apps and don't want to reinstall everything, but I went ahead and did all the steps because I really want to have root access. I'm currently reinstalling my apps now. Thanks again for making a simple program for noobs like me my Shield finally have root access (also debloated ).
I apologize for my bad grammar, English is not my native language.
Click to expand...
Click to collapse
Your English isnt bad I couldn't tell it was your second language. Thanks though I appreciate it
Nvidia Shield Root and More
Doing a little bit of reading goes a long way.

Worked just fine once I got the windows 8.1 driver funstuff squared away. Great work hexitnow! And shout out to 1wayjohnny and wwjoshdew for the driver work around! The Shield is an awesome toy!!!

mta1981 said:
Worked just fine once I got the windows 8.1 driver funstuff squared away. Great work hexitnow! And shout out to 1wayjohnny and wwjoshdew for the driver work around! The Shield is an awesome toy!!!
Click to expand...
Click to collapse
Thanks alot man i appreciate it. The naked driver and fastboot/adb minimal setup made it easy to get up and running in a matter of minutes
:thumbup:
Nvidia Shield Root and More
Doing a little bit of reading goes a long way.

Hey, huge thanks for this. Wouldn't have rooted my shield without it!

f3tf said:
Hey, huge thanks for this. Wouldn't have rooted my shield without it!
Click to expand...
Click to collapse
No problem glad you liked it

[Q] Verizon G2 acting crazy after FDR

Hello, and thank you in advance for any support on my issues. I have done some extensive searching regarding my issues but am coming up empty. I consider myself a relative noob and am now facing multiple questions and issues with my phone.
Device Info:
Verizon LG G2
Rooted, stock
Android Version 4.2.2
Software Version VS98011A
I did not personally root my phone - I paid to have it done for me remotely.
I have been using Titanium Backup to freeze or remove applications and bloat.
I also have used the paid version of ROM Manager for when/if I need it - I have never personally flashed a custom ROM or Kernel, etc.
I did personally side load the HotSpotProvision apk to use the Verizon Hotspot feature with my unlimited data and it worked great.
I also have the Verizon versions of the Galaxy S5 and LG G3. I recently did a 4G LTE speed test with all 3 devices and got insane speeds (attached) with the S5 and G5 but not the G2. I tried researching whether KitKat was the reason for being able to access XLTE speeds or not but couldn't find anything definitive there either. So I decided to attempt the Verizon OTA KitKat update for the G2. Here is where my nightmare begins...
To my knowledge, no backup had ever been done to my phone unless it was done when it was rooted. Regardless, I wanted to do one before making any changes to the phone but I have a feeling I was unsuccessful. After more searches on how to perform a backup and trying 6 times with ROM Manager (unsuccessfully), I decided to try the physical key option to launch into Recovery Mode. Based on what I did find online, this method would take you to the FDR screen but not to worry and to continue because it would actually take you to the TWRP home screen. Well, it did not. My phone reset and I lost everything in my gallery, etc. On reboot, I did see that I was still rooted but not able to do the OTA (because I am still rooted, I assume?). I have done 2 more FDRs and now my phone is acting out of it's mind.
Issues:
Touch screen unresponsive or turning off/on all by itself
Contact info not syncing to native messaging app
Previously installed free or purchased apps not reinstalling (although they did after the first FDR)
Can't receive OTA
At this point, I might as well do whatever I need to do to get things working correctly since I'm already reset.
My questions are:
How can I check if I do in fact have, or don't have a backup that I can access?
How do I create a backup so this doesn't happen again?
What do I need to do to get the OTA and will KK allow me to access the XLTE band?
Can I still do a Factory Data Reset and get back to the true "out of the box" version of the phone? If so, how?
I think that's it for now!! Thanks for any help that can be offered. Cheers.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Sounds like whoever you paid to root the phone didn't install a recovery or you lost it from applying the KK OTA.
You can install TWRP using Autorec if you're on KK (4.4.2) now.
http://forum.xda-developers.com/showthread.php?t=2715496
Personally I'd start clean to see if it clears up your issues, the touch screen thing sounds more like a hardware problem. If all is well after returning it to stock, re-root it yourself using ioroot/towelroot and install a recovery again and make a back up to save somewhere once you get it set up the way you want it.
http://forum.xda-developers.com/showthread.php?t=2448960

Thank you very much, Matt.
KK never did get installed...I am still on 4.2.2 and every time I try to go back to stock through various methods on this site I get the attached image. I would definitely like to start with the out-of-box device again, OTA KK and re-root but I'm not even having any luck with that either. This whole project began with the thinking that I needed KK to access the XLTE network since I was getting incredible speeds with the G3 and S5...do you know if that is accurate?
mjones73 said:
Sounds like whoever you paid to root the phone didn't install a recovery or you lost it from applying the KK OTA.
You can install TWRP using Autorec if you're on KK (4.4.2) now.
http://forum.xda-developers.com/showthread.php?t=2715496
Personally I'd start clean to see if it clears up your issues, the touch screen thing sounds more like a hardware problem. If all is well after returning it to stock, re-root it yourself using ioroot/towelroot and install a recovery again and make a back up to save somewhere once you get it set up the way you want it.
http://forum.xda-developers.com/showthread.php?t=2448960
Click to expand...
Click to collapse

lantzman said:
Thank you very much, Matt.
KK never did get installed...I am still on 4.2.2 and every time I try to go back to stock through various methods on this site I get the attached image. I would definitely like to start with the out-of-box device again, OTA KK and re-root but I'm not even having any luck with that either. This whole project began with the thinking that I needed KK to access the XLTE network since I was getting incredible speeds with the G3 and S5...do you know if that is accurate?
Click to expand...
Click to collapse
Follow the directions in the return to stock guide provided, see if you can get the phone in download mode...
Install the LG Flash Tool and drivers then try this.
1) Go ahead and put phone in Download mode by VolUp + plug in USB to PC. At this time your computer should install the device, if it hadnt already. Open device manager to check if un der "Ports (Com and LPT)" it shows up as LGE AndroidNet for VZW USB Serial Port (COM##) IF the COM number is anything other than 41, which it probably will be. Right click it in device manager and choose peroperties, then go to port settings tab and click advanced. On the bottom choose COM41 and hit OK. (if you get an error about it being in use I'll write more about that later)
hit ok and all that and close out the properties.
Click to expand...
Click to collapse

OK, I'm on download mode, the computer installed drivers and I changed to COM41. Phone still shows "Firmware Update" screen and 0% on progress. Where do I go from here?
mjones73 said:
Follow the directions in the return to stock guide provided, see if you can get the phone in download mode...
Install the LG Flash Tool and drivers then try this.
Click to expand...
Click to collapse

lantzman said:
OK, I'm on download mode, the computer installed drivers and I changed to COM41. Phone still shows "Firmware Update" screen and 0% on progress. Where do I go from here?
Click to expand...
Click to collapse
Did you unplug and replug in the phone?

I think I got it done. Phone is downloading KK now. This is where I would get the error on the install because I was rooted. Did the process I just go through unroot me?
mjones73 said:
Did you unplug and replug in the phone?
Click to expand...
Click to collapse

OK, it's doing the OTA!
lantzman said:
I think I got it done. Phone is downloading KK now. This is where I would get the error on the install because I was rooted. Did the process I just go through unroot me?
Click to expand...
Click to collapse

lantzman said:
I think I got it done. Phone is downloading KK now. This is where I would get the error on the install because I was rooted. Did the process I just go through unroot me?
Click to expand...
Click to collapse
Yes, returns the phone to out of the box stock basically. Now if you want to re-root, you can use ioroot25 or towelroot.
ioroot25 - http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
Once rooted, use autorec to install a recovery (kitkat requires some additional steps besides just flashing a recovery and it does them for you)
http://forum.xda-developers.com/showthread.php?t=2715496
Make sure you grab the vs980 version of autorec.

So I can't create a stock recovery prior to root, correct...so that I can go back to stock from root?
mjones73 said:
Yes, returns the phone to out of the box stock basically. Now if you want to re-root, you can use ioroot25 or towelroot.
ioroot25 - http://forum.xda-developers.com/showpost.php?p=48709232&postcount=869
Once rooted, use autorec to install a recovery (kitkat requires some additional steps besides just flashing a recovery and it does them for you)
http://forum.xda-developers.com/showthread.php?t=2715496
Make sure you grab the vs980 version of autorec.
Click to expand...
Click to collapse

lantzman said:
So I can't create a stock recovery prior to root, correct...so that I can go back to stock from root?
Click to expand...
Click to collapse
No, you need to root it first if you want to back it up.

OK, so I can root with the Towelroot app and use Autorec for backup. Does it give me TWRP?
mjones73 said:
No, you need to root it first if you want to back it up.
Click to expand...
Click to collapse

and where do I find the process for installing Autorec?
lantzman said:
OK, so I can root with the Towelroot app and use Autorec for backup. Does it give me TWRP?
Click to expand...
Click to collapse

sorry, I was making this way too difficult. I ran Towelroot and Autorec and I believe we are good to go. Now, when would I use Autorec...when I have an issue flashing other ROMs, kernels, etc?
How do you prefer to receive donations? I really appreciate your help...you've been great!

lantzman said:
sorry, I was making this way too difficult. I ran Towelroot and Autorec and I believe we are good to go. Now, when would I use Autorec...when I have an issue flashing other ROMs, kernels, etc?
How do you prefer to receive donations? I really appreciate your help...you've been great!
Click to expand...
Click to collapse
Autorec is a one and done, you can remove it now, it installs TWRP, that's all you need it for. You should now be able to get into recovery using the same sequence you used before if it installed clean for you. Any flashing of rom, kernels, etc would be via TWRP.
One last note, don't install any OTA's while you're rooted.
You don't have to donate anything but if you really want to, just hit the Donate to Me button under my name.

OK, thank you. One last question: it seems the touch screen may be starting to fail. If I needed to unroot or at least show unrooted to turn it in for a warranty replacement, can that be done and if so, how?

lantzman said:
OK, thank you. One last question: it seems the touch screen may be starting to fail. If I needed to unroot or at least show unrooted to turn it in for a warranty replacement, can that be done and if so, how?
Click to expand...
Click to collapse
This will get you back to stock. Make sure you read the first page before you do this...if needed. FYI: Device needs to be off to get into download mode and you should be in download mode before installing the drivers. http://forum.xda-developers.com/showthread.php?t=2448960
Sent from my XDABBEB VS98025A v2.0.0 using XDA free mobile app

Perfect, that's the process I just did from root so I could get the KK OTA. Just wasn't sure if there was an easier way to just show "unrooted" in "about phone" before having them look at it. Love your call sign/avatar. Huge Huge Huge Zeppelin fan here! Ever since hearing "Stairway" in 7th grade! Mght need to see if "LantZeppelin" is available! Thanks again.

[Q] OTA Update without losing Unencryption......Possible???

I am on my second OTA and my phone gets encrypted during the process. Is there a to update without forced encryption being reactivated on my device? I want to disable encryption so that my N6 runs faster but I don't want to have to wipe my device every time there's a new OTA.

marsdiamond said:
I am on my second OTA and my phone gets encrypted during the process. Is there a to update without forced encryption being reactivated on my device? I want to disable encryption so that my N6 runs faster but I don't want to have to wipe my device every time there's a new OTA.
Click to expand...
Click to collapse
How are you OTA-ing? OTA checks for modified kernel and should fail... You need edited kernel to have forced encryption disabled.
The best way to update would be to fastboot flash the system.img and then flash a matching boot.img wit forced encryption disabled.

I am using the Wug Fresh Toolkit...
But when I flash an image with encryption disabled, won't that wipe my device?

marsdiamond said:
I am using the Wug Fresh Toolkit...
But when I flash an image with encryption disabled, won't that wipe my device?
Click to expand...
Click to collapse
No idea. I suggested using fastboot. If you're using s toolkit, you're on your own. At least from me.
Here is my generic toolkit statement
There's nothing wrong with toolkits themselves.* They can be great, useful tools.* We're not even saying they cause bricks either - though users not understanding things *could* cause one...Toolkits are necessary on many devices, but on Nexuses, the manual steps are very easy.
Ultimately it's fine to use a toolkit but *only* if you already know how to do all these steps manually.* If you do not know how to do that then you should do it manually so that you do know. * The reason for this is if something goes wrong further down the line, we don't want to have to teach you the basics AND tell you what you need to do to fix whatever issue you have.* We just want to do the latter - because teaching someone the basics that they should already know when they are frustrated and panicking is not a good set of circumstances to be teaching under and it is frustrating to us more than you and putting us in that situation is a little bit selfish

rootSU said:
No idea. I suggested using fastboot. If you're using s toolkit, you're on your own. At least from me.
Here is my generic toolkit statement
There's nothing wrong with toolkits themselves.* They can be great, useful tools.* We're not even saying they cause bricks either - though users not understanding things *could* cause one...Toolkits are necessary on many devices, but on Nexuses, the manual steps are very easy.
Ultimately it's fine to use a toolkit but *only* if you already know how to do all these steps manually.* If you do not know how to do that then you should do it manually so that you do know. * The reason for this is if something goes wrong further down the line, we don't want to have to teach you the basics AND tell you what you need to do to fix whatever issue you have.* We just want to do the latter - because teaching someone the basics that they should already know when they are frustrated and panicking is not a good set of circumstances to be teaching under and it is frustrating to us more than you and putting us in that situation is a little bit selfish
Click to expand...
Click to collapse
Do you keep this statement somewhere so you can copy and paste or do you type it out every time?

Evolution_Freak said:
Do you keep this statement somewhere so you can copy and paste or do you type it out every time?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

rootSU said:
Click to expand...
Click to collapse
Touché.

rootSU said:
No idea. I suggested using fastboot. If you're using s toolkit, you're on your own. At least from me.
Here is my generic toolkit statement
There's nothing wrong with toolkits themselves.* They can be great, useful tools.* We're not even saying they cause bricks either - though users not understanding things *could* cause one...Toolkits are necessary on many devices, but on Nexuses, the manual steps are very easy.
Ultimately it's fine to use a toolkit but *only* if you already know how to do all these steps manually.* If you do not know how to do that then you should do it manually so that you do know. * The reason for this is if something goes wrong further down the line, we don't want to have to teach you the basics AND tell you what you need to do to fix whatever issue you have.* We just want to do the latter - because teaching someone the basics that they should already know when they are frustrated and panicking is not a good set of circumstances to be teaching under and it is frustrating to us more than you and putting us in that situation is a little bit selfish
Click to expand...
Click to collapse
rootSU...Thank you for you candid response. I do agree with you. I should know how to manually control my device. I bricked (no OS found) my N6 with my first lollipop OTA update using the toolkit. I looked up some manual instructions to flash the OS back to my device. I would have, but my third attempt/configuration with the toolkit I got it back. I plan on learning how to manually maintain my N6. Do you have a link to a thread that you suggest to get me started?
Also, if I manually flash OTA updates, is there a way that I can keep my encryption disabled? That is currently my biggest problem. Each time I update with the toolkit it re-encrypts my phone during the process.

marsdiamond said:
rootSU...Thank you for you candid response. I do agree with you. I should know how to manually control my device. I bricked (no OS found) my N6 with my first lollipop OTA update using the toolkit. I looked up some manual instructions to flash the OS back to my device. I would have, but my third attempt/configuration with the toolkit I got it back. I plan on learning how to manually maintain my N6. Do you have a link to a thread that you suggest to get me started?
Click to expand...
Click to collapse
Just go to General > Sticky Roll-up thread.
All "important" threads are there.
marsdiamond said:
Also, if I manually flash OTA updates, is there a way that I can keep my encryption disabled? That is currently my biggest problem. Each time I update with the toolkit it re-encrypts my phone during the process.
Click to expand...
Click to collapse
You cannot flash OTA if you have any customisations in the ROM or kernel and if you're unencrypted, you have a custom kernel.
If you're wishing to stay rooted or unencypted, you should either install a rom.zip, custom kernel and SuperSU from custom recovery or download the factory image and fastboot flash the system.img, a custom kernel (recovery or fastboot) and SuperSU (recovery)

Ridiculously easy upgrade to 5.1 and keep root/TWRP/no-wipe

All I know is that the wugfresh nexus root toolkit is the way to go. I discovered that windows application early on in my Nexus 5 ownership and haven't looked back. Sure, back in the day I would SDK and ADB and root and rom when it was cool and almost mandatory to bring in the cutting edge features on my incredible and galaxy nexus but there's just no need for it anymore with Lollipop having all the must-haves. And with the toolkit all I did was fire it up and the app put my N5 to sleep, poured it some warm milk, and rubbed its belly until it purred. 5 minutes later I'm up from 5.01 to 5.1 and I still have root, TWRP, and didn't even have to lose my ex-girlfriends phone number with a wipe. It even pre-downloaded 5.1 for me and checked md5. I really can't say enough good things about how painfree it is. Essentially 1 click.
If no-wipe turns out to be crap, I'll just click the OTHER button and be good to go. Thanks WUG!! You ROCK!

So far so good on the dirty flash...

What are you looking for? Validation? An argument? Validation through argument? Help me out here.

Wakamatsu said:
What are you looking for? Validation? An argument? Validation through argument? Help me out here.
Click to expand...
Click to collapse
Hahah, you're right. I was just sharing the solution. When the last update came out everyone who had root/custom recovery was freaking out and having issues with upgrading and they had all these how-to threads, etc. Wug's application is just so easy. And I wanted to poll to see how many people are using a toolkit vs. ADB.

rabaker07 said:
Hahah, you're right. I was just sharing the solution. When the last update came out everyone who had root/custom recovery was freaking out and having issues with upgrading and they had all these how-to threads, etc. Wug's application is just so easy. And I wanted to poll to see how many people are using a toolkit vs. ADB.
Click to expand...
Click to collapse
Probably some people are like me and prefer doing it the tough way by flashing files manually, instead of using a tool kit.

Wugfreshes toolkit is the best. As you probably know most of the senior pple discuss and ridicule toolkits. I've never had trouble with his.
ADB is hassle if you are new. We all know driver issues. Thats a nightmare b4 you even start. I've since learnt ADB commands but still would only use it as a last stop. It was the toolkit that found and loaded the driver allowing ADB.
To be honest I think, subconsciously, ADB users see them selves as superior to the rest of us.
I'm happy with the years Rug fresh has been there for me. The tool updates automatically.
Sent from a Toolbox rooted and flashed phone
Sent from my Nexus 5

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
But seriously:
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash radio radio.img
fastboot flash bootloader bootloader.img
boot into custom recovery
flash SuperSU/other stuff if desired
isn't that hard.
Driver issues? If you had driver issues your toolkit wouldn't work either. All it does is literally the above—if that is so hard, then maybe you shouldn't modify your device.
Also, ADB ≠ fastboot, they are separate binaries and have a completely different purpose.

@Elluel
Agreed. Just to notice you - Wug's Toolkit recognize ADB or fastboot by itself.
@rabaker07
Was using Wug's Toolkit for a long time. But I don't prefere anymore that app itself take so much space and not necessary files on my PC. So this is much better solution: @rootSU http://forum.xda-developers.com/google-nexus-5/general/noob-read-adb-fastboot-how-hep-t2807273
@zerosum0
To be honest. Yes, there are people that feel superior at XDA. But hey, they have reasons.
Problem is, that if you got a bootloop or something like that, its very hard to help people, because they actually don't know what they were doing with their phones before that happened. And if they are also yellers then we got to much threads here like "OMG, please help. :crying:"

I got the drivers on my computer with the kit,after trying everything. That did it in seconds. I do take notice and have written all the commands needed should something go wrong and no toolkit.
A lot of people just are not computer literate.
If push comes to shove I could do it that way but say I want to flash a factory image. The toolkit fetches it, after sorting out the connection between phone and computer. It then flashes it, with a step by step account. Quick and simple. I've never had trouble with it. Toolkits have come along way and I guess there are bad ones out there. Horses for courses. And if someone screws up with a toolkit OR ADB. They should eat humble pie before asking for help.
Sent from my Nexus 5

rabaker07 said:
All I know is that the wugfresh nexus root toolkit is the way to go. I discovered that windows application early on in my Nexus 5 ownership and haven't looked back. Sure, back in the day I would SDK and ADB and root and rom when it was cool and almost mandatory to bring in the cutting edge features on my incredible and galaxy nexus but there's just no need for it anymore with Lollipop having all the must-haves. And with the toolkit all I did was fire it up and the app put my N5 to sleep, poured it some warm milk, and rubbed its belly until it purred. 5 minutes later I'm up from 5.01 to 5.1 and I still have root, TWRP, and didn't even have to lose my ex-girlfriends phone number with a wipe. It even pre-downloaded 5.1 for me and checked md5. I really can't say enough good things about how painfree it is. Essentially 1 click.
If no-wipe turns out to be crap, I'll just click the OTHER button and be good to go. Thanks WUG!! You ROCK!
Click to expand...
Click to collapse
Thank you for sharing your experiences
Glad it worked for you
Thread closed

Droid Turbo (XT1254) autoiniroot problem

Hey.
I have a Droid Turbo XT1254 with bootloader locked (I am planning to unlock soon).
Recently, I stumbled across the thread and saw that someone had made rooting MCG25.251-5-5 possible and it made me want to try it out.
Anyways, I downloaded all the files (magisk and autoinitroot) and was able to root my phone just fine.
I tried giving Super user permission to some apps, and it worked flawlessly. I then tried to install Magisk module but oddly enough it failed.
It gave me an error that magisk was not properly installed. Also the SafetyNet check failed.
I decided to uninstall root, factory reset my device and root the device again.
Now the thing is that when I booted back into fastboot and ran the command that was meant to uninstall the root, it failed.
Obviously, I made sure that I was typing the correct command, I didn't even miss the "" marks. But it still didn't work.
It only gave me an error that the command 'confirm' doesn't exist.
I tried running the autoinit script and I booted just fine.
But the problem is that magisk isn't working properly and I'm unable to uninstall the autoinit root.
Any help will be greatly appreciated.
Also, Im using minimal adb and fast boot setup. Not sure if that's what causing the uninstall to fail or not.
TL; DR: Magisk doesn't work properly after doing the autoinitroot and I'm unable to uninstall the root by using the command that was mentioned in the original post.
Thanks for taking the time to read it

DuringSummer said:
Hey.
I have a Droid Turbo XT1254 with bootloader locked (I am planning to unlock soon).
Recently, I stumbled across the thread and saw that someone had made rooting MCG25.251-5-5 possible and it made me want to try it out.
Anyways, I downloaded all the files (magisk and autoinitroot) and was able to root my phone just fine.
I tried giving Super user permission to some apps, and it worked flawlessly. I then tried to install Magisk module but oddly enough it failed.
It gave me an error that magisk was not properly installed. Also the SafetyNet check failed.
I decided to uninstall root, factory reset my device and root the device again.
Now the thing is that when I booted back into fastboot and ran the command that was meant to uninstall the root, it failed.
Obviously, I made sure that I was typing the correct command, I didn't even miss the "" marks. But it still didn't work.
It only gave me an error that the command 'confirm' doesn't exist.
I tried running the autoinit script and I booted just fine.
But the problem is that magisk isn't working properly and I'm unable to uninstall the autoinit root.
Any help will be greatly appreciated.
Also, Im using minimal adb and fast boot setup. Not sure if that's what causing the uninstall to fail or not.
TL; DR: Magisk doesn't work properly after doing the autoinitroot and I'm unable to uninstall the root by using the command that was mentioned in the original post.
Thanks for taking the time to read it
Click to expand...
Click to collapse
1) why are you waiting to unlock your bootloader? Temp root is unstable and won't give you what you want.
2) of course Magisk won't work until you unlock your bootloader. Why would you think otherwise? On Motorola phones you have to unlock the bootloader to make changes like permanent root, install custom recovery, etc. Magisk just hides that.
3) you SAY you typed the correct command but after having a back-and-forth for two days over three pages with someone else who claimed the same thing and was WRONG, I'm skeptical.
Type exactly what you think is the correct command. Don't copy and paste anything. Actually type it out.
Better yet, post screenshot. That's how we proved to the other guy he was not reading what we had written.
"Oh, I didn't know."
Yes he did. It was in post #2, the very FIRST reply in the thread, which I wrote. And I told him over and over to go re-read that post!

Thanks for replying.
The answer to the first question is that I don't have $$$ right now. Will do it next month or so.
#2: Hahah. I did read that thread, and I'm pretty sure I'm not making that mistake, In any case I'll attach screenshots.

This is the screenshot. This time I tried specifying the directory to the fastboot.exe that came with autoinitroot, still no luck. Same error comes up regardless of whether I specify the directory or just use normal fastboot the came with minimal ADB.
And yes. I did it while I was in fastboot mode.
For some reason the app won't let me upload screenshot. Here is the link instead
http://i.imgur.com/Y5L5kvw.png

ChazzMatt said:
1) why are you waiting to unlock your bootloader? Temp root is unstable and won't give you what you want.
2) of course Magisk won't work until you unlock your bootloader. Why would you think otherwise? On Motorola phones you have to unlock the bootloader to make changes like permanent root, install custom recovery, etc. Magisk just hides that.
3) you SAY you typed the correct command but after having a back-and-forth for two days over three pages with someone else who claimed the same thing and was WRONG, I'm skeptical.
Type exactly what you think is the correct command. Don't copy and paste anything. Actually type it out.
Better yet, post screenshot. That's how we proved to the other guy he was not reading what we had written.
"Oh, I didn't know."
Yes he did. It was in post #2, the very FIRST reply in the thread, which I wrote. And I told him over and over to go re-read that post!
Click to expand...
Click to collapse
Yeah but in the original thread by autoprime, users have posted that they managed to install modules like "xposed systemless" etc. No reason it shouldn't work on mine.
Edit: Furthermore, autoptime himself mentioned that we can use custom magisk script to avoid boot loop, as far as I understand that's only possible when magisk recognizes modules.
Thing is that I have root, I can even use apps like titanium backup and whatnot. I can't use the script he mentioned unless magisk allows me to install something.

DuringSummer said:
This is the screenshot. This time I tried specifying the directory to the fastboot.exe that came with autoinitroot, still no luck. Same error comes up regardless of whether I specify the directory or just use normal fastboot the came with minimal ADB.
And yes. I did it while I was in fastboot mode.
For some reason the app won't let me upload screenshot. Here is the link instead
http://i.imgur.com/Y5L5kvw.png
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Your screenshot shows you typed "confirm". That's not the right command. It's "config".
fastboot oem config fsg-id ""

ChazzMatt said:
Your screenshot shows you typed "confirm". That's not the right command. It's "config".
fastboot oem config fsg-id ""
Click to expand...
Click to collapse
Oh. Hell. I feel stupid. I kinda copied from one the comments in OP. Will update brb.

Still doesn't work. This time it gave me error (bootloader) something-suffixes: false.
Etc etc. Will post screenshot.
EDIT: It WORKED. I placed the autoinitroot to desktop and changed the directory along with folder names. Ran the command, seems to have worked. Thanks anyways.
Probably had something to do with really long directory name. Idk.

DuringSummer said:
Yeah but in the original thread by autoprime, users have posted that they managed to install modules like "xposed systemless" etc. No reason it shouldn't work on mine.
Click to expand...
Click to collapse
Show me examples of that with Motorola phones.
I also have extensive experience with LG phones, and many of those (like LG G2 and LG G3) do not need bootloader unlock to root and install custom recovery. Whereas, Motorola phones require unlocked bootloader.
---------- Post added at 03:27 PM ---------- Previous post was at 03:21 PM ----------
DuringSummer said:
Still doesn't work. This time it gave me error (bootloader) something-suffixes: false.
Etc etc. Will post screenshot.
EDIT: It WORKED. I placed the autoinitroot to desktop and changed the directory along with folder names. Ran the command, seems to have worked. Thanks anyways.
Probably had something to do with really long directory name. Idk.
Click to expand...
Click to collapse
Yes, the suffixes errors are normal. Only by rebooting do you see if it worked.

ChazzMatt said:
Show me examples of that with Motorola phones.
I also have extensive experience with LG phones, and many of those (like LG G2 and LG G3) do not need bootloader unlock to root and install custom recovery. Whereas, Motorola phones require unlocked bootloader.
Click to expand...
Click to collapse
http://i.imgur.com/u06AaAV.png
http://i.imgur.com/7AHc5Bk.png
He explicitly mentioned that about bootloader locked Moto. Also the tool only works on Moto so.

DuringSummer said:
http://i.imgur.com/u06AaAV.png
http://i.imgur.com/7AHc5Bk.png
He explicitly mentioned that about bootloader locked Moto. Also the tool only works on Moto so.
Click to expand...
Click to collapse
Well, I know he was wrong about one thing. When the phone reboots it doesn't just boot into a stock system. Instead it bootloops and gets hung on the Moto logo. It never finishes booting until you run that end temp root command in fastboot.
Go to the thread and ask him how to do what he describes.... He is an expert and knows a lot more than me.
But also remember if your phone reboots in any way while you are away from your computer with fastboot installation, your phone will be totally useless until you get back to your computer and temp re-root or run that end temp root command.

ChazzMatt said:
Well, I know he was wrong about one thing. When the phone reboots it doesn't just boot into a stock system. Instead it bootloops and gets hung on the Moto logo. It never finishes booting until you run that end temp root command.
Click to expand...
Click to collapse
Oh that. What he meant was that if you place the custom magisk script in the right folder it will avoid boot loop and will boot into stock system, from there you'll have to use autoinitroot tool from pc again to re-root it, the script is handy if you're going somewhere and won't have access to pc. In which case, even if your phone gets turned off or reboots, it won't bootloop like crazy and you get access to stock system. Though you won't have root until you run autoroot script again from PC.
Also, it does provides full root. The only downside is that it isn't permanent. So as long as you're careful and don't mess with system and only use systemless modifications using magisk, you're safe. In worst case scenarios you'll only have to run the unroot command and factory reset to go back to 100% stock.
It's useful for those who can't get their bootloader unlocked.
Sadly, In my case magisk isn't working properly. That's why I'll factory reset and try again. Hopefully it'll work then.
Also do you by any chance know how and where to place custom scripts of magisk? Will be doing that after factory reset.
Also you helped a lot. Thanks, mate

DuringSummer said:
Oh that. What he meant was that if you place the custom magisk script in the right folder it will avoid boot loop and will boot into stock system, from there you'll have to use autoinitroot tool from pc again to re-root it, the script is handy if you're going somewhere and won't have access to pc. In which case, even if your phone gets turned off or reboots, it won't bootloop like crazy and you get access to stock system. Though you won't have root until you run autoroot script again from PC.
Also, it does provides full root. The only downside is that it isn't permanent. So as long as you're careful and don't mess with system and only use systemless modifications using magisk, you're safe. In worst case scenarios you'll only have to run the unroot command and factory reset to go back to 100% stock.
It's useful for those who can't get their bootloader unlocked.
Sadly, In my case magisk isn't working properly. That's why I'll factory reset and try again. Hopefully it'll work then.
Also do you by any chance know how and where to place custom scripts of magisk? Will be doing that after factory reset.
Also you helped a lot. Thanks, mate
Click to expand...
Click to collapse
His post #2 seems to talk about folders.

ChazzMatt said:
His post #2 seems to talk about folders.
Click to expand...
Click to collapse
Yeah. Saw that. Couldn't find those folders. Checked both root and normal storage.
Thanks anyway.

The whole temp root thing is really just a way to proceed with the bootloader unlock. to use temp root on any daily driver just seems like more trouble than its worth. Hurry up and find 25 bucks!!!
My opinion is that for the work that these guys do its a small price to pay and was money well spent

bigmatt503 said:
The whole temp root thing is really just a way to proceed with the bootloader unlock. to use temp root on any daily driver just seems like more trouble than its worth. Hurry up and find 25 bucks!!!
My opinion is that for the work that these guys do its a small price to pay and was money well spent
Click to expand...
Click to collapse
Actually, I don't have any problem paying 25 bucks. The thing is that I'm planning to buy a new phone. Seems really pointless spending 25$ on something that I'll replace in a few months. At first I thought that I should get it unlocked, however, this phone is 3 years old. I decided that I should upgrade to current technology.

ChazzMatt said:
Show me examples of that with Motorola phones.
I also have extensive experience with LG phones, and many of those (like LG G2 and LG G3) do not need bootloader unlock to root and install custom recovery. Whereas, Motorola phones require unlocked bootloader.
---------- Post added at 03:27 PM ---------- Previous post was at 03:21 PM ----------
Yes, the suffixes errors are normal. Only by rebooting do you see if it worked.
Click to expand...
Click to collapse
Caution thread jacking...... since you are very familiar with LG phones. What are the chances of the verizon g6 ever getting root?
Sent from my VS988 using XDA-Developers Legacy app