Database Develop

[SCRIPT] GladRoot v4.3 (Bell 0.37.4, AT&T 1.26/1.52/1.57/1.83 Supported)

Note to all users: This thread is now closed. I will no longer be updating GladRoot as there are more reliable and simpler methods for obtaining root on the newer firmwares. Support can still be found through PM for the older firmware versions.​Note to all users on non-AT&T/Bell devicesThis is currently untested on anything but AT&T and Bell phones. You can run this on any phone, and at the very worst, it just won't work. There's almost 0 chance you will harm your phone by running this, so feel free to try. Please report back what firmware version you tried it on, and if it worked or not and I'll update the first post here to reflect. I don't have any device but an AT&T Atrix so I can't test any of the other versions myself, I need your help!​GladRoot v4.3 (AT&T 1.83 Update Supported - READ DIRECTIONS)
In the interest of cleaning things up and putting all the current information into one place, with links to everything you'll need to get this working.
Basically, there's a ton of misinformation floating around about current root methods. This is your one stop shop for all your root needs. To explain, the SuperOneClick method installs busybox a second time. The Atrix already has busybox installed, so there's no need to install a duplicate. This can cause issues with other mods. GladRoot will take care of everything SuperOneClick did. I've contacted the developer to see if there's a way around this.
Start Here
If you have an AT&T Atrix and want to update to 1.57/1.83 with root, follow the first set of instructions.
If you have a Bell Atrix or an AT&T Atrix on 1.26 or 1.52 and just want to root, go to the second set of instructions.
Please, please, PLEASE, read the whole first post before asking questions. Chances are your question is already covered in the directions.
If you have any features requests or notice any bugs, please PM me, I might miss them in this thread.
To unroot, just run unroot.bat
Note to users seeing "Unable to detect device" error: Disable USB debugging, and turn it back on. Make sure your connection type is set to None. If you need the drivers, they are available here: 32-bit Drivers and 64-bit Drivers
Little bit of additional info here:
This will root your phone. There is no need to run aRoot before this, and you should NOT be running SuperOneClick anymore.
This has options to enable sideloading and the tethering APN. Enabling sideloading will not add an Unknown Sources checkbox, it will just enable it. I don't see any reason for the need to disable this, so unless someone can make a case for the checkbox (that makes sense for users), it will remain this way.
Unlike v1, the scripts are fully automated. You need only click "allow" to superuser when prompted for certain steps.
If you are already on 1.57/1.83 and do not have root, you MUST flash back to 1.26 for this to work. NO EXCEPTIONS.​
Installation instructions: 1.26 to 1.57/1.83
Read the directions.
Read the directions again.
Read the directions a third time. If you do not understand a step, ASK before starting.
Download the script
Extract the GladRoot folder and files to C:\. Do not install anywhere else. Having it inside a folder with a space will cause the script to FAIL.
Make sure your device is 1.2.6 and is not running any mods, I recommend a fresh SBF flash of 1.2.6. Download links and installation instructions here
Enable USB debugging (Settings -> Applications -> Development).
Connect your phone (I recommend setting USB Connection to 'None').
Run gladroot.bat and follow the on-screen directions (If you're using Windows 7, run as admin by holding down control and double-clicking).
Verify that there are no errors before updating.
Go to Settings -> About phone -> System updates
Follow the on-screen instructions. First download the update (you will need a Wi-Fi connection for this), then it will prompt you to install.
The update will reboot the device and install itself. If this part fails it's because you are not on stock 1.2.6 firmware. Start over and read the directions.
When it boots back up, verify USB debugging is still on. Some users report that disabling and re-enabling USB debugging solves a few issues with the script detecting your device (Settings -> Applications -> Development).
Run afterupdate.bat (If you're using Windows 7, run as admin by holding down control and double-clicking).
Make sure you allow the superuser request on your phone or it WILL fail.
All done! Enjoy your rooted Atrix on 1.57/1.83!
​Screenshots**REMOVED FOR NOW UNTIL I GET A CHANCE TO UPDATE**​Installation instructions: 1.26, 1.52 and Bell Atrix
Read the directions.
Read the directions again.
Read the directions a third time. If you do not understand a step, ASK before starting.
Download the script
Extract the GladRoot folder and files to C:\. Do not install anywhere else. Having it inside a folder with a space will cause the script to FAIL.
Make sure your device is the correct version. Go to Settings -> About phone -> Build number and make sure it matches one of the following:
OLYFR_U4_1.2.6
OLYFR_U4_1.5.2
OLYLA_U4_0.37.4
If you need to flash an SBF first, Download links and installation instructions here.
Enable USB debugging (Settings -> Applications -> Development).
Connect your phone (I recommend setting USB Connection to 'None').
Run gladroot.bat and follow the on-screen directions.(If you're using Windows 7, run as admin by holding down control and double-clicking).
When you get to the step that asks if you're updating to 1.57, just say no.
Verify that there are no errors.
All done! Enjoy your rooted Atrix!
​DISCLAIMER
I am not responsible if this bricks your phone or if it doesn't work properly for you. I've done everything I can to ensure smooth execution.
If you have any issues, feel free to PM me, reply to this thread, or come find me on IRC (I'm Fenrir or fen|works on IRC)​Special Thanks
Sogarth for adb wizardry, shawnbuck for the concept and getting the ball moving, designgears for the initial aRoot script method, and everyone on XDA and IRC who helped contribute and test.​Changelog
Version 4.3
Cleaned up script a tiny bit
Added textual support for 1.83 (the method hasn't changed, it's always worked)
Version 4.2
Added Uknown Sources checkbox to sideloading, as well as enabling it.
Added unroot script.
Version 4.1
Fixed a few minor aesthetic errors in the script
Version 4
Added a pause after the superuser request so if it fails, users can read the output.
Started mapping out log process for error catching.
Removed abd kill-server from the beginning of the file as I think it might be causing problems on slower machines.
Version 3
Removed option to root, it just roots. This will not harm your phone if you're already rooted.
Added support to root all devices, including Bell Atrix.
Cleaned up and improved script.
Changed name from Root v2 to GladRoot (Which is Root v3)
Version 2
Massive improvements to deployment script
Removed need to manually enter commands
Version 1
Initial Release
​

I love you guys lol!
So will this method (or the idea behind it) work for future updates (like the supposed ones for HSUPA, voice quality and one day eventually maybe gingerbread?)
Or do we have no idea about those?

Vigneshd said:
I love you guys lol!
So will this method (or the idea behind it) work for future updates (like the supposed ones for HSUPA, voice quality and one day eventually maybe gingerbread?)
Or do we have no idea about those?
Click to expand...
Click to collapse
I would assume so, unless Moto closes this hole? Not sure if this is a root exploit like psneuter or not.
Also flashing my phone 1.2.6 and will attempt this, will post back my results

So do this version allow sideloading?

awww yeahhh

PixoNova said:
I would assume so, unless Moto closes this hole? Not sure if this is a root exploit like psneuter or not.
Also flashing my phone 1.2.6 and will attempt this, will post back my results
Click to expand...
Click to collapse
Unfortunately, it is possible to close this hole, but I don't think moto is going to get it for a little while.

plmiller0905 said:
So do this version allow sideloading?
Click to expand...
Click to collapse
i assume so. i'm able to sideload

After failing with the previous version, I failed again with this version. I get the screen shot below every time.
I installed JDK and SDK. I did aroot. I rebooted Atrix and my PC. I tried in None and Mass Storage. The Atrix is recognized by my PC as it is listed under Computer and connects with Media Sync. I put the new retainroot folder in C:\.
Nothing works.
Have I missed something?
Any ideas?

drjim said:
After failing with the previous version, I failed again with this version. I get the screen shot below every time.
I installed JDK and SDK. I did aroot. I rebooted Atrix and my PC. I tried in None and Mass Storage. The Atrix is recognized by my PC as it is listed under Computer and connects with Media Sync.
Nothing works.
Have I missed something?
Any ideas?
Click to expand...
Click to collapse
open command prompt and type:
Code:
adb devices
What does it return?

drjim said:
After failing with the previous version, I failed again with this version. I get the screen shot below every time.
I installed JDK and SDK. I did aroot. I rebooted Atrix and my PC. I tried in None and Mass Storage. The Atrix is recognized by my PC as it is listed under Computer and connects with Media Sync.
Nothing works.
Have I missed something?
Any ideas?
Click to expand...
Click to collapse
USB debugging on?
USB mode set as None?

Ririal said:
open command prompt and type:
Code:
adb devices
What does it return?
Click to expand...
Click to collapse
I'm in C:\Users\My Name>
Is that the directory I should be in? If not, which and how to get there (I'm not great with cmd)?

shawnbuck said:
Unfortunately, it is possible to close this hole, but I don't think moto is going to get it for a little while.
Click to expand...
Click to collapse
So is this a hole that allows us to exploit another hole?

s0dhi said:
USB debugging on?
USB mode set as None?
Click to expand...
Click to collapse
Yes to both.

drjim said:
I'm in C:\Users\My Name>
Is that the directory I should be in? If not, which and how to get there (I'm not great with cmd)?
Click to expand...
Click to collapse
I changed directory to C:\ in cmd and typed in adb devices. Its response: List of devices attached.

Only thing I haven't done is flash SBF (whatever that is). But I'm dling it now...along with RSDlite (whatever that is).

Any ideas why I got all the way to the second command prompt with permission denied? I never got the super user prompt on my phone. Can I still put the phone in debug mode and rerun afterupdate.bat to re-root?

PixoNova said:
So is this a hole that allows us to exploit another hole?
Click to expand...
Click to collapse
This isn't quite a hole, just a little magic-show type trickery really.

tdamocles said:
Any ideas why I got all the way to the second command prompt with permission denied? I never got the super user prompt on my phone. Can I still put the phone in debug mode and rerun afterupdate.bat to re-root?
Click to expand...
Click to collapse
What do you mean second command prompt?

Failed backup?
OK, I'm on stock 1.2.6, said yes to already rooted and yes to side load and no to tether. It starts and says pushing backupsu.sh... then retval = and backup failed to execute properly. What am I doing wrong? I have developer on and usb = none. Can't seem to get it to work...

when i run beforeupdate i get backup failed to execute properly
am i missing something?

[Q] Dazed and Confused

So I'm trying to get a better understanding of the things I am reading here and on other Android websites. I keep reading about ADB - which I've gathered stands for Android Development Bridge. I did a search on this site and found the "easy ABD tutorial" that actually confused me even more. So my question is, could someone please explain to me in laymans terms what exactly is ABD? I've successfully rooted my D3 and created a nandroid and would l iike to try the Steel Droid Rom however, it talks about using ADB to push the BlurEmail.apk to system/app/.
I think I've successfully installed the Android SDK but I have no clue as to how to install the ABD "drivers" that are referenced in the the following post: http://www.xda-developers.com/android/adb-easy-tutorial/
Is there a difference between the SDK application and ADB or are they part of the same thing?
Is there a way to verify if I have the ADB drivers/application/whatever that I need so that I can push the BlurEmail.apk to the system/app/ file location?
As always, thanks to those that provide a response to this thread.

[Q] DPI change gone wrong

I made a mistake when changing the DPI on my LG Flex using Texdroider DPI, this happened to me before when i set a too lower value. Now my phone boots and i immediately get a UI crash error which i have to press ok and it appears again, in the time between errors the phone is not responsive.
First my phone came with 4.0.2 which i rooted using ioroot then i modified the DPI, crashed bad one time as it was not booting anymore but i was able to use adb to restore the backup files (build.prop) that the program (Texdroider DPI) made. I had to use the same PC from which i performed the rooting process but it worked eventually.
I then updated to 4.4.2 and my phone was unrooted, after that i used towelroot to root it again and it installed the SuperUser app. Now i am stuck with my problem:
Tried using ADB shell to restore the backup files but i need root permission to do so.
1. When trying adb root i get "adbd cannot run as root in production builds" (Error which didn't appear in the past)
2. When i try adb shell then su nothing happens in the command window, but on the phone i get a popup for granting access to "adb" and i cannot press the Grant button as my phone is not responsive.
What can i do in this situation? Are there any solutions for one of these two methods? Like granting privileges to adb trough the command window?
Please Help, Thank you.

unless you have custom recovery or can grany adb root access i think your only option since it still is restock
---------- Post added at 06:25 PM ---------- Previous post was at 06:21 PM ----------
this http://forum.xda-developers.com/showthread.php?t=2644083 should get u back up an flexin just follow carfully if u don't understand something read read an read again i would suggest reading whole thread but if you read an understand an are confident pull the trigger

[Q&A] Android M Developer Preview / Images & Flashables

Q&A for Android M Developer Preview / Images & Flashables
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Android M Developer Preview / Images & Flashables. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!

Anyone try it with project fi
Sent from my Nexus 6 using XDA Free mobile app

I am currently downloading.... I am on verizon. i wonder how much is going to break.

We need non encryptable boot.img so the boot.img should be modified right ?

Anyone else microphone broken in M? Doesn't work at all throughout the OS for me
It seems to be when you set up hotword detection. That doesn't work, once you try it borks the mic until you restart.

Are Android M Dev Preview Updates OTA?
So I've installed the Android M Developer Preview on my Nexus 5 and I wanted to know whether the updates Google rolls out for it (not official M but incremental bug fixes e.t.c) will these small updates be OTA or will I have to manually flash them? Was it the same with L developer preview.

im trying to flash it, but when i run the flash all bat i get missing boot.sig and so on. everything is extracted... i guess i jumped the gun a little

boot animation?
Flashed few mins ago. Still hanging google logo. Is it normal? Where is boot animation?
---------- Post added at 09:30 PM ---------- Previous post was at 09:22 PM ----------
Flashed few mins ago. Still hanging google logo. Is it normal? Where is boot animation?

Change DPI on Android M
To change DPI and not bugs like stretch contacts photos and google play big icons (by method wm density) try this:
1. boot to recovery
2. mount /system
3. go to command line
HTML:
adb pull /system/build.prop
4. change line ro.sf.lcd_density=xxx (xxx means dpi, on N5 i like 400)
5. save this file
6. go to command line
HTML:
adb push build.prop /system/
adb shell
cd system
chmod 644 build.prop

Use Wug's to Flash....
You can use Wug's Nexus Toolkit for this... do the following:
1. Download and Install Wug's
http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
2. Unlock BootLoader if you haven't using the toolkit
3. Once Unlocked, Use the toolkit to FLASH STOCK with Normal Conditions....
4. Dialogue Box should come up that will allow to browse to an image file on your computer... make sure to download the Android M Preview directly from Google...
https://developer.android.com/preview/download.html
Don't leave the download page for the preview as you'll need to cut and paste the MD5 Check Hash from the preview page into Wug's
5. Using Browse.... select the download .tgz on your computer
6. Copy & Paste MD5 Hash
7. Wug's will pretty much do the rest for you with zero issues.... I like to put it into ADB bootloader mode myself before I begin the flash since its really simple to do......
Keep in mind that unlocking the bootloader and / or flashing the preview will completely wipe your phone... so make sure to backup anything important..... :good:
Hope this helps those having booting and loading problems....
FOR DPI..... and / or screen re-sizing
It is much simpler and less evasive (won't cause bootlooping) by just doing the following ADB command:
adb shell wm size hhhh x vvvv
where hhhh is your horizontal resolution and vvvv is your vertical.... takes some trial and error to get something that works.... but it does not manipulate dpi which may cause bootlooping
Hope this helps too :laugh:

Interesting, I never flashed the stock boot.img, but I get the verification error on boot up. I was curious why everyone was concerned about it though cause it doesn't really impact anything does it? (flashed the noencryption-boot.img).
FYI for Verizon Users, there was a tip in here about enabling Multi-window, well I didn't know you can ADB in TWRP, so while changing the build.prop you can also enable the hotspot tether. Works.
*My posts still get sent to q&a threads. As well as my post count never seems to go up. Love it.

daledenton said:
Anyone else microphone broken in M? Doesn't work at all throughout the OS for me
It seems to be when you set up hotword detection. That doesn't work, once you try it borks the mic until you restart.
Click to expand...
Click to collapse
Yes, I'm having the same problem.

mahst68 said:
You can use Wug's Nexus Toolkit for this... do the following:
1. Download and Install Wug's
http://forum.xda-developers.com/nexus-6/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2947452
2. Unlock BootLoader if you haven't using the toolkit
3. Once Unlocked, Use the toolkit to FLASH STOCK with Normal Conditions....
4. Dialogue Box should come up that will allow to browse to an image file on your computer... make sure to download the Android M Preview directly from Google...
https://developer.android.com/preview/download.html
Don't leave the download page for the preview as you'll need to cut and paste the MD5 Check Hash from the preview page into Wug's
5. Using Browse.... select the download .tgz on your computer
6. Copy & Paste MD5 Hash
7. Wug's will pretty much do the rest for you with zero issues.... I like to put it into ADB bootloader mode myself before I begin the flash since its really simple to do......
Keep in mind that unlocking the bootloader and / or flashing the preview will completely wipe your phone... so make sure to backup anything important..... :good:
Hope this helps those having booting and loading problems....
FOR DPI..... and / or screen re-sizing
It is much simpler and less evasive (won't cause bootlooping) by just doing the following ADB command:
adb shell wm size hhhh x vvvv
where hhhh is your horizontal resolution and vvvv is your vertical.... takes some trial and error to get something that works.... but it does not manipulate dpi which may cause bootlooping
Hope this helps too :laugh:
Click to expand...
Click to collapse
adb shell wm method break some images thumbnials and icons (for example hangouts, contacts and play store). Better method i wrote up to your post...

Android M on other devices than Nexus
Hey Guys, i wondered if I can install Android M on my OPO (using Multirom) or if this is not possible because it's only for Nexus 5,6,9 & Player? Thanks for the answer

Dragobourd said:
Hey Guys, i wondered if I can install Android M on my OPO (using Multirom) or if this is not possible because it's only for Nexus 5,6,9 & Player? Thanks for the answer
Click to expand...
Click to collapse
No you cannot.

Rooting Android M
I realized that the device verification message pops up if we flash the perm_recovery_signed.zip file. Is there anyway to get around this?

sakacjakub said:
To change DPI and not bugs like stretch contacts photos and google play big icons (by method wm density) try this:
1. boot to recovery
2. mount /system
3. go to command line
HTML:
adb pull /system/build.prop
4. change line ro.sf.lcd_density=xxx (xxx means dpi, on N5 i like 400)
5. save this file
6. go to command line
HTML:
adb push build.prop /system/
adb shell
cd system
chmod 644 build.prop
Click to expand...
Click to collapse
Is there any benefit using this instead of:
Code:
adb wm density 480
adb reboot
?

Gingerbread1611 said:
Is there any benefit using this instead of:
Code:
adb wm density 480
adb reboot
?
Click to expand...
Click to collapse
Yes... I had graphical glitches with adb wm density method (400 dpi). Contact picture thumbnails are messed up, also in WhatsApp, Hangouts has very big profile photo and Play Store has very big icons (best developer)...

sakacjakub said:
Yes... I had graphical glitches with adb wm density method (400 dpi). Contact picture thumbnails are messed up, also in WhatsApp, Hangouts has very big profile photo and Play Store has very big icons (best developer)...
Click to expand...
Click to collapse
Damn, just checked the playstore and i also have those big icons. I'll try your method now, thank you.
/edit: I just saw you actually answered it in the post i quoted... Im sorry, didn't see that.

Don't know if anyone already answered but at the I/O announcement and on the website they've said they plan to roll out OTAs as new M Previews are made available. On the graphic there seems to be at least 2, 3 more.

Moto e5 James

Hello everyone I'm having a hard time pushing fstab.qcom it keep saying argument required that is my only issue is there a way around it but without my phone will not root help please

Fstab.qcom issue
Jrknock said:
Hello everyone I'm having a hard time pushing fstab.qcom it keep saying argument required that is my only issue is there a way around it but without my phone will not root help please
Click to expand...
Click to collapse
Make sure that if your using the zip file that you extract it to your adb/fastboot tools location. It should work then. Double check and make sure your using the proper command to adb push the file as well. https://forum.xda-developers.com/moto-e5/how-to/guide-root-twrp-moto-e5-play-explained-t3856182 this is a great link for help with rooting the device. Just follow the steps and you should have no plroblem getting root. Hope this helps.