So when are we going to get us some custom ROMS, already? - Moto G Stylus (Moto G Pro) Guides, News, & Discuss

Just picked up this bodacious device and I AM FIENDING FOR SOME CUSTOM WAREZ.

Just got my phone and haven't found the firmware yet to even root the device. Give it some time. Might be more difficult on Android 10 as well. At the least we should have root and some basic mods soon. I gotta do a bit of research though before I start devolping and feel comfortable releasing anything. Been over 5 years since I've don't anything with a phone so I'm excited to get into it too man! Just gotta be patient so we don't end up with $300 bricks

I Rooted my Moto G Stylus today with Magisk using the Patched Boot Image method!
It won't let me post the link's here cause I'm a new member but just search on Google for Stock Firmware for Moto G Stylus and it will come up the website you want is getdroidtips. Also for information on how to Root using Magisk and using the Patched Boot Image method search in Google for Magisk Patched Boot Image you want to go to the website that says Installation Magisk GitHub Pages.

JoshPhillySportsFan1 said:
It won't let me post the link's here cause I'm a new member but just search on Google for Stock Firmware for Moto G Stylus and it will come up the website you want is getdroidtips. Also for information on how to Root using Magisk and using the Patched Boot Image method search in Google for Magisk Patched Boot Image you want to go to the website that says Installation Magisk GitHub Pages.
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/sofiap/official/RETAIL/
The frmware matches the phone I bought at Best Buy.

mrbubs3 said:
Just picked up this bodacious device and I AM FIENDING FOR SOME CUSTOM WAREZ.
Click to expand...
Click to collapse
Doubt any ROMs will appear.at least there is a way to root. But as far as ROMs. As long as any new device ships with Android 10 twrp recovery is not supported with it.

Yeah it's sad I really hope someone comes up with another Custom Recovery or I hope someone updates TWRP to work with Android 10 cause TWRP hasn't been updated for a lot of device's in awhile.
---------- Post added at 01:29 AM ---------- Previous post was at 01:16 AM ----------
I'm just happy to have Root for this phone! I'll never buy a Carrier Locked phone again cause you can't Unlock the BootLoader on Carrier phone's so you basically can't Root them if you find a way to Root them your lucky but it's much harder if the BootLoader is locked. Thankfully Magisk make's it much easier to Root unlike in the past when we had to use the SuperSU App plus Magisk is Systemless Root unlike the old SuperSU App so it also make's it much easier to UnRoot and return to Stock.

JoshPhillySportsFan1 said:
Yeah it's sad I really hope someone comes up with another Custom Recovery or I hope someone updates TWRP to work with Android 10 cause TWRP hasn't been updated for a lot of device's in awhile.
---------- Post added at 01:29 AM ---------- Previous post was at 01:16 AM ----------
I'm just happy to have Root for this phone! I'll never buy a Carrier Locked phone again cause you can't Unlock the BootLoader on Carrier phone's so you basically can't Root them if you find a way to Root them your lucky but it's much harder if the BootLoader is locked. Thankfully Magisk make's it much easier to Root unlike in the past when we had to use the SuperSU App plus Magisk is Systemless Root unlike the old SuperSU App so it also make's it much easier to UnRoot and return to Stock.
Click to expand...
Click to collapse
Is flashify or whatever it was still a thing? I remember we couldn't use twrp on the att Galaxy S5 because the bootloader was locked but we had a way around it and could flash zips and roms using an app. It was a pain developing for because testing for it was even more risky since you didn't have twrp and nandroid backups
Sent from my [device_name] using XDA-Developers Legacy app

talkingmonkeys said:
Is flashify or whatever it was still a thing? I remember we couldn't use twrp on the att Galaxy S5 because the bootloader was locked but we had a way around it and could flash zips and roms using an app. It was a pain developing for because testing for it was even more risky since you didn't have twrp and nandroid backups
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
I'm not sure, but I thought the same thing. I also remember an app called Safestrap that I used on my Droid Bionic because of the same thing. It was kinda like have a dual boot machine.

talkingmonkeys said:
Is flashify or whatever it was still a thing? I remember we couldn't use twrp on the att Galaxy S5 because the bootloader was locked but we had a way around it and could flash zips and roms using an app. It was a pain developing for because testing for it was even more risky since you didn't have twrp and nandroid backups
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
The bootloader is unlockable, though.

One thing I think would be of value is a kernel with Kcal. Total control over RGB colors and Saturation. My last phone was LCD and with Kcal baked into the kernel and using Color Calibration app or Kernel Adiutor, cranking up the saturation really made a difference. Bland orange color went to vibrant red. I don't care about all the other tweeks to use AKT rpofiles etc. I just want more control over the screen. Keep it simple for less hassle.
Since we can't install a custom recovery, we have whatever magisc modules work, whatever exposed works, and a custom kernel. I think the stock ROM is ok as is. Just wish I could control the color more.
And of course we have to hope the custom launchers can catch up with gestures.
---------- Post added at 05:46 PM ---------- Previous post was at 05:29 PM ----------
Flashify is still in the Play store. It hasn't been updated since 2015. It looks to me like it is an onboard ADB solution. No PC needed. It appears to be using Fastboot, so it may still be compatible. But first you have to be rooted using ADB. Without TWRP, you can only flash .img file. No .zip files. So you can use it to flash a new kernel, but you can do that with ADB.
---------- Post added at 06:01 PM ---------- Previous post was at 05:46 PM ----------
We may not need a custom kernel to get kcal. Found this where someone with a G3 and root added a few files and a script and got color control with the stock kernel. Once I root, I'll give it a try.
https://forum.xda-developers.com/lg-g3/general/color-control-display-stock-kernel-t3309677

bencozzy said:
Best we can do is magisk modules to systemlessly modify the rom for debloating and theming etc.
Luckily we will still be able to use fastboot to change kernels. So we should be able to push this hardware a bit that way.
Click to expand...
Click to collapse
yes but then when the debloat script bricks your phone, how do you recover?

bencozzy said:
Fastboot the factory image of the firmware.
Click to expand...
Click to collapse
I tried running the script to do that from my old moto g6 and failed. Read somewhere that on the moto g stylus you had to adb sideload the stock rom from recovery, but I dont seem to have a stock recovery, and of course TWRP is not available for this phone. Are you saying that you have actually succeeded in fastboot flashing the factory image? If so, could you post exact instructions? Thanks!

You might want to look at this.
https://www.getdroidtips.com/moto-g-stylus-stock-firmware/

androiddiego said:
You might want to look at this.
https://www.getdroidtips.com/moto-g-stylus-stock-firmware/
Click to expand...
Click to collapse
Thanks but I tried that the other day and no go because that method (ADB sideload) requires stock recovery, and my stylus does not seem to have stock recovery. I just get the dead android / NO COMMAND icon after selecting recovery mode. Is my new stylus defective?

fronto said:
Thanks but I tried that the other day and no go because that method (ADB sideload) requires stock recovery, and my stylus does not seem to have stock recovery. I just get the dead android / NO COMMAND icon after selecting recovery mode. Is my new stylus defective?
Click to expand...
Click to collapse
When you get the NO COMMAND icon, press and hold power, then hit volume up quickly and release. (Don't hold the volume up hardly at all)
You then get into recovery. Stock recovery. The stock firmware has a stock recovery img in it, so you do have a stock recovery.

I got the stock rom
Sent from my moto g stylus using Tapatalk

It was bootstrap

fronto said:
Thanks but I tried that the other day and no go because that method (ADB sideload) requires stock recovery, and my stylus does not seem to have stock recovery. I just get the dead android / NO COMMAND icon after selecting recovery mode. Is my new stylus defective?
Click to expand...
Click to collapse
androiddiego said:
You might want to look at this.
https://www.getdroidtips.com/moto-g-stylus-stock-firmware/
Click to expand...
Click to collapse
how do you go about installing the rom/img? using adb and getting error 21 codes with signature verification failed.
is there a custom recovery that you're suppose to use?

androiddiego said:
When you get the NO COMMAND icon, press and hold power, then hit volume up quickly and release. (Don't hold the volume up hardly at all)
You then get into recovery. Stock recovery. The stock firmware has a stock recovery img in it, so you do have a stock recovery.
Click to expand...
Click to collapse
Thank you! This worked!!! Never had a phone before that I had to do that to get to recovery. Android 10 thing? Kinda a pain but it works. Now I feel more secure about going ahead and debloating this phone knowing if I mess it up, I can always re-flash.
Thanks!
EDIT: I am back to thinking this phone is bogus. Stock recovery does not seem very useful. Cannot connect with ADB despite latest ADB and latest Moto USB drivers. Cannot install from SD card either. It wont mount the SD card seemingly no matter what. So, although we do have a stock recovery, there does not seem to be a way to flash the stock rom back it it.

fronto said:
Thank you! This worked!!! Never had a phone before that I had to do that to get to recovery. Android 10 thing? Kinda a pain but it works. Now I feel more secure about going ahead and debloating this phone knowing if I mess it up, I can always re-flash.
Thanks!
EDIT: I am back to thinking this phone is bogus. Stock recovery does not seem very useful. Cannot connect with ADB despite latest ADB and latest Moto USB drivers. Cannot install from SD card either. It wont mount the SD card seemingly no matter what. So, although we do have a stock recovery, there does not seem to be a way to flash the stock rom back it it.
Click to expand...
Click to collapse
What about fastboot? I am curious, because I am leaning on buying this phone.

Related

Help for a somewhat new person.

I am new with rooting my phone. I have used Rooted phones before, I followed http://forum.xda-developers.com/showthread.php?t=2258633 Motochopper how to. I ran into a problem. I click the superuser app that was installed onto my phone, and it tells me that "The Superuser binary (su) must be updated. Please choose an installation method. Recovery mode installation is recommended for HTC devices." I click install and it tells me there was an error. I would like to root my phone along with potentially installing CWM so that I can easily install Cyanogenmod when they release a stable verison for the S4. Also would love to install titanium backup along with some Adfree apps.
Any help would be very much appreciated.
OK, so it looks like you already have it rooted.
When super SU asks that question, dont install via CWM, tell it to just install normally.
Once you have SuperSU working, Download Rom Manager from the play store and install CWM Recovery right from within the ROM Manager app.
It will give you the option to pick between two types of CWM(ClockWorkMod). The Touch version, like its name gives you the ability to use the touch screen and not only the volume up/down + Power button.
Telling it to install normally causes it to just tell me there was an error, it also tells me it is out of date as well. Titanium Backup tells me that it cant get root access and I was never asked about it.
OK, so your phone is not rooted then.
Your going to have to try rooting it again or flashing an already rooted rom with Odin.
I just tried it again, this time it said failure after the install of the superuser.apk. I just read that one of the later updates by samsung can make it harder to root. I just got my phone and i was fully updated. What Roms, are already rooted for the S4. I am actually enjoying some of the default apps that came with the phone.
Wicked (and most ROMs that don't include the [STOCK] tag) are pre-rooted...but you'll need to ODIN a custom recovery first then flash the ROM.
If you want to stay on rooted stock, follow the steps in the "root May 7 MDL" thread to ODIN a rooted kernel, and you'll be good to go.
(You don't need root access to get a custom recovery flashed)
Basically, any of your options are pretty straightforward, but they're going to involve Odin-ing stuff.
So there isn't really a way to just root my phone without installing a custom rom?
There was before the second update, with the second update rooting got just a little bit more steps
Sent from my SGH-M919 using xda premium
movieaddict said:
There was before the second update, with the second update rooting got just a little bit more steps
Sent from my SGH-M919 using xda premium
Click to expand...
Click to collapse
So is there a way to keep it stock but root it? What are the other steps I would have to take. Why does Samsung not like people rooting their phones, I thought carriers were the ones that hated people rooting their phones
Spud37 said:
So is there a way to keep it stock but root it? What are the other steps I would have to take. Why does Samsung not like people rooting their phones, I thought carriers were the ones that hated people rooting their phones
Click to expand...
Click to collapse
Are you still on the MDB firmware or have you done any over the air updates? Specifically the May 7 update which is MDL. Motochopper is specifically for then older firmware (MDB) and it won't work if you are already on the updated. MDL firmware. In which case you would have to follow these instructions to acquire root.
http://forum.xda-developers.com/showthread.php?p=41162041
I usually use a market app called root checker to quickly check if I do have root.
And yes you can be rooted on stock.
Sent from my SGH-M919
lazaro17 said:
Are you still on the MDB firmware or have you done any over the air updates? Specifically the May 7 update which is MDL. Motochopper is specifically for then older firmware (MDB) and it won't work if you are already on the updated. MDL firmware. In which case you would have to follow these instructions to acquire root.
http://forum.xda-developers.com/showthread.php?p=41162041
I usually use a market app called root checker to quickly check if I do have root.
And yes you can be rooted on stock.
Sent from my SGH-M919
Click to expand...
Click to collapse
Root checker says no root. I believe it does have that over the air update installed. T Mobile updated it when they gave me the phone, because they thought I didn't really know anything about phones. I assume this means I have to follow another method to root my phone?
If you have the MDL update you have to root using the steps listed here:
http://forum.xda-developers.com/showthread.php?t=2268880
Easily done, just a few more steps.
ronin4740 said:
If you have the MDL update you have to root using the steps listed here:
http://forum.xda-developers.com/showthread.php?t=2268880
Easily done, just a few more steps.
Click to expand...
Click to collapse
This is going to sound like a dumb question but from reading all of that I need to use ODIN to install the ROOT_M919?UVUAMDL onto the phone? that should root the phone and allow me to install ROM Manager and install CWM from there right?
Also would doing this delete everything I have on my phone right now?
Spud37 said:
This is going to sound like a dumb question but from reading all of that I need to use ODIN to install the ROOT_M919?UVUAMDL onto the phone? that should root the phone and allow me to install ROM Manager and install CWM from there right?
Also would doing this delete everything I have on my phone right now?
Click to expand...
Click to collapse
No, you use Odin to install one of the recoveries. You use the recovery to install the zip ROOT_M919?UVUAMD. Personally I didn't use that file. I installed the kernel in recovery and SuperSU in recovery. And no, it won't delete things on your phone.
Atmazzz said:
No, you use Odin to install one of the recoveries. You use the recovery to install the zip ROOT_M919?UVUAMD. Personally I didn't use that file. I installed the kernel in recovery and SuperSU in recovery. And no, it won't delete things on your phone.
Click to expand...
Click to collapse
Thank you so much, I am about to go and do this. I will use the kernel you suggested since that looks like a better option, after flashing the kernal should i reboot and just use it normally for a bit and then go to recovery and flash SuperSU?
EDIT: The steps on the thread for ODIN are for installing a rooted ROM, I am assuming its still the same steps for installing a recovery instead of a rooted ROM
Spud37 said:
after flashing the kernal should i reboot and just use it normally for a bit and then go to recovery and flash SuperSU?
Click to expand...
Click to collapse
If I remember right I just flashed them both at the same time. Just make sure you do the kernel first.
---------- Post added at 02:01 PM ---------- Previous post was at 01:59 PM ----------
Spud37 said:
EDIT: The steps on the thread for ODIN are for installing a rooted ROM, I am assuming its still the same steps for installing a recovery instead of a rooted ROM
Click to expand...
Click to collapse
The steps for Odin are for the stock rom, but yes, you use it the same way for a recovery.
Atmazzz said:
If I remember right I just flashed them both at the same time. Just make sure you do the kernel first.
---------- Post added at 02:01 PM ---------- Previous post was at 01:59 PM ----------
The steps for Odin are for the stock rom, but yes, you use it the same way for a recovery.
Click to expand...
Click to collapse
Okay I didn't get any error using ODIN, however when I try and boot into CWM using Volume Up + Power it just goes to android recovery. Which doesn't have any of the options I need. Am I just booting up the wrong way, or did I do something wrong. I tried both the touch version and the non-touch version
Spud37 said:
Okay I didn't get any error using ODIN, however when I try and boot into CWM using Volume Up + Power it just goes to android recovery. Which doesn't have any of the options I need. Am I just booting up the wrong way, or did I do something wrong. I tried both the touch version and the non-touch version
Click to expand...
Click to collapse
2 options. uncheck auto reboot in Odin. When Odin is done, unplug your phone, pull your battery, then boot into recovery. Or .. when Odin is done and it reboots your phone, keep holding volume up to get to recovery.
Atmazzz said:
2 options. uncheck auto reboot in Odin. When Odin is done, unplug your phone, pull your battery, then boot into recovery. Or .. when Odin is done and it reboots your phone, keep holding volume up to get to recovery.
Click to expand...
Click to collapse
Thank You so much. However it now seems like I have both Super User and SuperSU installed.
How did you root? Did you install the ROOT_M919?UVUAMDL zip and install SuperSU?

If I root?

Will I lose the ability to get the 4.4 ota update when available?
If you just root, then no. What would prevent it from installing is if you have a custom recovery. Then it would fail to install. If your just rooted and take the OTA though you may loose root.
Are you sure? lol.
Well if you lose root, you can always re-root?
Are you rooted and have a custom recovery?
REDFOCZ said:
If you just root, then no. What would prevent it from installing is if you have a custom recovery. Then it would fail to install. If your just rooted and take the OTA though you may loose root.
Click to expand...
Click to collapse
Custom recovery is fine (from the standpoint of the OTA verification check). Custom kernel will cause OTA to fail, as would any changes/modifications/removals to/from /system (ie the ROM)
To root I need an unlocked bootloader?
SysAdmNj said:
To root I need an unlocked bootloader?
Click to expand...
Click to collapse
Yes. Unlocking bootloader just sets a flag so signature checks aren't performed. For security reasons it also clears your user data so someone can't just bypass your login.
Until I see the next version of Android and a few weeks of user comments on its abilities, I'm not sure whether I'll ever want to upgrade...
sfhub said:
Yes. Unlocking bootloader just sets a flag so signature checks aren't performed. For security reasons it also clears your user data so someone can't just bypass your login.
Click to expand...
Click to collapse
Wish I knew this before I installed all my apps lol. Its easy to unroot and lock back up in case?
alpine101 said:
Until I see the next version of Android and a few weeks of user comments on its abilities, I'm not sure whether I'll ever want to upgrade...
Click to expand...
Click to collapse
You mean 4.3 is fine with you? Battery life and performance?
Or just wait until your current Custom ROM gets updated to the 4.4, and then flash with that newly created ROM. Boom. 4.4.
I just got this yesterday and I like it so far, reading on it isnt bad. Even at night, some apps have night mode etc. I dont feel like rooting/unlocking just yet, let alone custom rom'ming, until I'm sure I'm keeping it. Would like to hear the nexus 10 announcement but honestly the size of the nexus 7 is comfortable to carry around. The weight is good, and it kind of fits it in my old nexus 7 rubber case. If I do keep it, definitely looking forward to 4.4 custom roms and a better fitting case.
REDFOCZ said:
If you just root, then no. What would prevent it from installing is if you have a custom recovery. Then it would fail to install. If your just rooted and take the OTA though you may loose root.
Click to expand...
Click to collapse
The problem is that to have root you have to install a custom recovery first, since the root file (supersu) is installed from a custom recovery.
So how can we root without a custom recovery?
I haven't rooted my N7, just going off my experience with other devices.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Sensamic said:
The problem is that to have root you have to install a custom recovery first, since the root file (supersu) is installed from a custom recovery.
So how can we root without a custom recovery?
Click to expand...
Click to collapse
Does this method not work?
http://forum.xda-developers.com/showthread.php?t=2467014
It involves unlocking your device by putting your device in bootloader/fastboot mode, but I dont see anything about installing a custom recovery.
REDFOCZ said:
I haven't rooted my N7, just going off my experience with other devices.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Whats your primary use for your n7?
Web browsing, video watching, and reading magazine's.
Sensamic said:
The problem is that to have root you have to install a custom recovery first, since the root file (supersu) is installed from a custom recovery.
So how can we root without a custom recovery?
Click to expand...
Click to collapse
You don't need to "install" custom recovery. Booting custom recovery (leaving stock recovery on the tablet) is good enough.
The key to everything is you need to unlock the bootloader. Once you do that, any number of methods of installing root are possible.
If you don't want to unlock bootloader, then you need to wait for an exploit to be found which could arrive anytime between now and never.
---------- Post added at 10:52 AM ---------- Previous post was at 10:48 AM ----------
SysAdmNj said:
Does this method not work?
http://forum.xda-developers.com/showthread.php?t=2467014
It involves unlocking your device by putting your device in bootloader/fastboot mode, but I dont see anything about installing a custom recovery.
Click to expand...
Click to collapse
It works.
From a technique standpoint, it is equivalent to booting custom recovery and installing root, except everything is automated for you.
The key is you need to unlock.
In the most published method, after unlocking, you boot (or install) custom recovery and manually select the SuperSU or Superuser install update.zip
In CF-AutoRoot, there is a custom kernel that you boot whose job is to install root (essentialy taking care of the manual selection of the SuperSU/Superuser install update.zip), then after a subsequent reboot, you are back to using your original kernel, except root is installed.
sfhub said:
You don't need to "install" custom recovery. Booting custom recovery (leaving stock recovery on the tablet) is good enough.
The key to everything is you need to unlock the bootloader. Once you do that, any number of methods of installing root are possible.
If you don't want to unlock bootloader, then you need to wait for an exploit to be found which could arrive anytime between now and never.
---------- Post added at 10:52 AM ---------- Previous post was at 10:48 AM ----------
It works.
From a technique standpoint, it is equivalent to booting custom recovery and installing root, except everything is automated for you.
The key is you need to unlock.
In the most published method, after unlocking, you boot (or install) custom recovery and manually select the SuperSU or Superuser install update.zip
In CF-AutoRoot, there is a custom kernel that you boot whose job is to install root (essentialy taking care of the manual selection of the SuperSU/Superuser install update.zip), then after a subsequent reboot, you are back to using your original kernel, except root is installed.
Click to expand...
Click to collapse
Thanks for the explanation. I think I'm just going for it as I didnt see any announcements of the nexus 5 or kit kat, let alone nexus 10 I'll just keep my nexus 7 2013. I did more reading on this device the past two days then I've done on my previous nexus 7 and nexus 10 tabs. In other words I like it, good enough to keep. Comfy size, weight etc. Now to find the best rom for battery life with a kernel that would let me double tap to wake

installing recovery

Hello everyone I just had a question about recover, a little while back I had cwm on my phone but then I did a full restore and am on stock rooted kit Kat. The first time I installed the cwm recovery I used freegee, but I've seen people say that it doesn't work on the software I am on which is E98020H, can anyone confirm that it doesn't work and is there another way? Thank you.
nsh121193 said:
Hello everyone I just had a question about recover, a little while back I had cwm on my phone but then I did a full restore and am on stock rooted kit Kat. The first time I installed the cwm recovery I used freegee, but I've seen people say that it doesn't work on the software I am on which is E98020H, can anyone confirm that it doesn't work and is there another way? Thank you.
Click to expand...
Click to collapse
have you got anywhere?
nsh121193 said:
Hello everyone I just had a question about recover, a little while back I had cwm on my phone but then I did a full restore and am on stock rooted kit Kat. The first time I installed the cwm recovery I used freegee, but I've seen people say that it doesn't work on the software I am on which is E98020H, can anyone confirm that it doesn't work and is there another way? Thank you.
Click to expand...
Click to collapse
Unless I am doing something completely wrong... it is not working for me either. I'm on E98020h and I was not even able to root with kitkat root tool. I wound up using Root Genius to root, and was able to get root access for apps like FreeGee, titanium backup, etc.. However Freegee is littered with errors. Upon opening I get an error message saying there is an "exception thrown waiting for command to finish" and then the next error window says that "your aboot is not supported by loki on software version: E98020h." After that the app seems fine, everything is there, but when I go to flash CWM-6.0.4.7 I get another error message, this time saying "There was an error running action "loki_recovery."
No clue, might just be me, but I have tried some other methods as well (including rooting, using voodoo root protector, update to e98020h, and then try freegee) but still nothing.
frankp124 said:
Unless I am doing something completely wrong... it is not working for me either. I'm on E98020h and I was not even able to root with kitkat root tool. I wound up using Root Genius to root, and was able to get root access for apps like FreeGee, titanium backup, etc.. However Freegee is littered with errors. Upon opening I get an error message saying there is an "exception thrown waiting for command to finish" and then the next error window says that "your aboot is not supported by loki on software version: E98020h." After that the app seems fine, everything is there, but when I go to flash CWM-6.0.4.7 I get another error message, this time saying "There was an error running action "loki_recovery."
No clue, might just be me, but I have tried some other methods as well (including rooting, using voodoo root protector, update to e98020h, and then try freegee) but still nothing.
Click to expand...
Click to collapse
Loki hasn't been updated in months. I think we just have to hold tight until they update it to include the new aboot that comes with e98020h. I'm stuck at the same place. No big deal since I have root, but would be nice to get into CWM (safely) and back the phone up.
---------- Post added at 04:08 PM ---------- Previous post was at 03:54 PM ----------
frankp124 said:
Unless I am doing something completely wrong... it is not working for me either. I'm on E98020h and I was not even able to root with kitkat root tool. I wound up using Root Genius to root, and was able to get root access for apps like FreeGee, titanium backup, etc.. However Freegee is littered with errors. Upon opening I get an error message saying there is an "exception thrown waiting for command to finish" and then the next error window says that "your aboot is not supported by loki on software version: E98020h." After that the app seems fine, everything is there, but when I go to flash CWM-6.0.4.7 I get another error message, this time saying "There was an error running action "loki_recovery."
No clue, might just be me, but I have tried some other methods as well (including rooting, using voodoo root protector, update to e98020h, and then try freegee) but still nothing.
Click to expand...
Click to collapse
Found a temporary solution.
http://forum.xda-developers.com/showthread.php?t=2371927&page=43
flash the CWM from this thread. At least allows you the ability to get into CWM and do backups, etc...
nsh121193 said:
Hello everyone I just had a question about recover, a little while back I had cwm on my phone but then I did a full restore and am on stock rooted kit Kat. The first time I installed the cwm recovery I used freegee, but I've seen people say that it doesn't work on the software I am on which is E98020H, can anyone confirm that it doesn't work and is there another way? Thank you.
Click to expand...
Click to collapse
Here's what you do to be able to install freegee cwm recovery successfully and also obtain root.
1.) Download towelrrot app from www.towelroot.com (much appreciation to Geohot). One click and you are rooted.
2.) Download busybox from playstore. Install.
3.) Download GPRO cwm 6.0.4.4 recovery apk (look for it on the attached files area of G3 rom v 4.7 on the android section of our phone). Run app and install recovery but don't reboot afterwards.
4.)Run Freegee. It should install freegee cwm or twrp by then.
i tried this sadly freegee still getting hung on a boot error...
Couldn't you just flashtool back to stock jb then root and install recovery........
2SHAYNEZ
---------- Post added at 09:46 PM ---------- Previous post was at 09:45 PM ----------
Then flash easykat and boom you have stock kk and recovery
2SHAYNEZ
shayneflashindaily said:
Couldn't you just flashtool back to stock jb then root and install recovery........
2SHAYNEZ
---------- Post added at 09:46 PM ---------- Previous post was at 09:45 PM ----------
Then flash easykat and boom you have stock kk and recovery
2SHAYNEZ
Click to expand...
Click to collapse
this work for me thanks
rcorvo1 said:
this work for me thanks
Click to expand...
Click to collapse
No problem hit that thanks button for people who help you out and have a great day sir :thumbup:
2SHAYNEZ
im so stuck on this with e98020h.
new to optimus g pro so super lost. Any help would be awesome. Used towelroot. Could not install twrp or else it did install and i cant boot into recovery for some reason. Installed SuperSU with no problems.
briandresstoyota said:
im so stuck on this with e98020h.
new to optimus g pro so super lost. Any help would be awesome. Used towelroot. Could not install twrp or else it did install and i cant boot into recovery for some reason. Installed SuperSU with no problems.
Click to expand...
Click to collapse
You're on stock Kitkat. Use GPRO_recovery.apk, after that update recovery to something newer (TWRP prefered) and voila, you're ready to go.
Or start from stock Jellybean, unlock via Freegee and update recovery. You'll get a better flashing base (smaller chances for hardware wakelocks).
Yeah I finally worked through it last night. Towel root. Gpro recovery. Then installed busy box and flashed latest twrp with flashify and got to flashing my ROMs. Hey BTW which ROM/kernel do you get the best battery life with?
Sent from my LG-E980 using XDA Free mobile app
briandresstoyota said:
Yeah I finally worked through it last night. Towel root. Gpro recovery. Then installed busy box and flashed latest twrp with flashify and got to flashing my ROMs. Hey BTW which ROM/kernel do you get the best battery life with?
Sent from my LG-E980 using XDA Free mobile app
Click to expand...
Click to collapse
I'm still on KitKat (custom build of PAC-ROM 4.4.4, with my own kernel) and I get pretty good SOT (~5h) and maybe a day-day and a half of one charge. Haven't used Lollipop ROMs much, they are too unstable for my needs (mostly problems with overheating and phone not sleeping properly) and I'm too lazy to sync repos and do a custom build, but CM12.1 with Emmanuel's kernel was OK for me for a long time. Please note, I was using older CM build (01.06.2015) because of the SIM bug which is not patched yet.
blitzkriegger said:
Here's what you do to be able to install freegee cwm recovery successfully and also obtain root.
1.) Download towelrrot app from www.towelroot.com (much appreciation to Geohot). One click and you are rooted.
2.) Download busybox from playstore. Install.
3.) Download GPRO cwm 6.0.4.4 recovery apk (look for it on the attached files area of G3 rom v 4.7 on the android section of our phone). Run app and install recovery but don't reboot afterwards.
4.)Run Freegee. It should install freegee cwm or twrp by then.
Click to expand...
Click to collapse
Friend gave me his e980, and was stuck trying to install recovery. This worked (step 2-4). I was rooted but couldnt get recoveries to install. Thanks!!!! :good::good:
ThoR294 said:
Friend gave me his e980, and was stuck trying to install recovery. This worked (step 2-4). I was rooted but couldnt get recoveries to install. Thanks!!!! :good::good:
Click to expand...
Click to collapse
to run freegee you need stuck 4.1.2 android.

HTC One M8: Root/Bootloader Unlocking failed? "No SU binary"

Root/Bootloader unlocking failed? "No SU binary"
A few months ago I got a M8 (international model i believe, it says 'M8x' on the back) and tried to root and unlock the bootloader but failed so I just stored it away .
I followed these videos. Can't paste links...new xda account:
youtube:
HTC One M8 : How to Unlock Bootloader & Root - Easiest Method
HTC One M8 : How to Root & Install TWRP Recovery - Easiest Method
I believe the first video, unlocking the bootloader, was successful(says "Software status: Modified""**Unlocked**" in bootloader mode).
In the second I believe TWRP was installed successfully (It opens up via Recovery) but the SuperSU app was not successful . I don't remember exactly what happened (it was months ago) but when I hit the SuperSU app I think it failed to update as seen in the second video at 2;29. As of today, when I try to open SuperSU, I'm presented with a message that says: "There is no SU binary installed, and superSU cannot install it. This is a problem! If you just upgraded to Android 5.0, you need to manually re-root" hit ok and SuperSU closes.
I found various fixes and such but I'm not sure which is the safest.
Sorry I'm new to android and I just don't want to ruin my device.
SOLVED
I grew some balls and just went for it. Flashed a supersu.zip in TWRP and it worked.
Delete this thread I guess.
If you used the toolkit as shown in the Youtube video, that was your main problem.
The toolkit uses obsolete (and by obsolete, I mean over a year) versions of both:
SuperSU (current version is 2.46)
TWRP (current version is 2.8.7)
Using outdated versions of either/both of these with a stock Lollipop M8 will cause some major issues. Before doing any mods, its best to read and research to make sure you are using the most up-to-date procedures and files. Youtube should not be your only modding resource. Also, keep in mind that the "easiest" way, is not necessarily the "best" way.
huura said:
I grew some balls and just went for it. Flashed a supersu.zip in TWRP and it worked.
Click to expand...
Click to collapse
Making a TWRP backup before flashing anything would have minimized any risk.
---------- Post added at 01:20 PM ---------- Previous post was at 01:20 PM ----------
huura said:
A few months ago I got a M8 (international model i believe, it says 'M8x' on the back)
Click to expand...
Click to collapse
M8x is the Taiwanese, higher CPU clocked variant.
That makes sense. Thanks for all the info. woo slightly higher clock speed variant!
Just successfully updated TWRP with Flashify, TWRP Manager didn't want to work. All good.
Also should I use the superSU 2.52 beta or is it too troublesome? Any benefits?
huura said:
T woo slightly higher clock speed variant!
Click to expand...
Click to collapse
On a side note. Only thing to be aware of, the M8x can't have other versions' radios flashed to it, even with s-off; as confirmed by a few users here (including one very knowledgeable one).
By extension, this probably also means that you can't "convert" to another version by running that version's RUU.
Probably not a major issue, as all other common mods (TWRP, root, flashing custom ROMs) should work fine on the M8x. Just something to keep in mind.
huura said:
Just successfully updated TWRP with Flashify, TWRP Manager didn't want to work. All good.
Click to expand...
Click to collapse
My advice would be to learn how to use fastboot to install TWRP, and skip the pointless middle man apps. Doing it by fastboot is easy, and much more reliable.
huura said:
Also should I use the superSU 2.52 beta or is it too troublesome? Any benefits?
Click to expand...
Click to collapse
No benefits that I know of. 2.46 roots the phone (on Lollipop) just fine, no need to have any "benefits" beyond that.
Marshmallow is a different story.
Ah ok. I'll keep note of that quirk, thanks.
The fastboot method doesn't look too complicated. I'll definitely look into it if it's more reliable/less of a hassle.
One more thing, I wanted to install Xposed for ARHD's sense toolbox. How do I install it? Just install the .apk file on my device and I'm good to go or is there more to it?
huura said:
The fastboot method doesn't look too complicated. I'll definitely look into it if it's more reliable/less of a hassle.
Click to expand...
Click to collapse
Its a good trick to know (as well as other fastboot commands) as it allows you to flash recovery without a working OS (not an unheard of situation, if you mess with flashing ROMs and other things enough times).
The process is pretty simple, as you most likely already have fastboot setup on your computer if you unlocked the bootloader. So flashing a recovery is simply a matter of:
1) Download the desired recovery .img to your fastboot folder (where fastboot.exe is located)
2) Connect your phone to the computer, and boot into bootloader-fastboot mode
3) Open a command prompt on the computer
4) Issue the proper fastboot command
5) Drink beer
huura said:
One more thing, I wanted to install Xposed for ARHD's sense toolbox. How do I install it? Just install the .apk file on my device and I'm good to go or is there more to it?
Click to expand...
Click to collapse
I haven't messed with Xposed for a while, but I think you just need to:
1) Make a nandroid of your current working setup
2) Install the Xposed apk
3) Open the Xposed app and install the desired frameworks
Figured it out, was straight forward

[TWRP][v3.1.1][xt907][KKBL][EXPERIMENTAL]TWRP for xt907 KKBL EXPERIMENTAL build

TEAMWIN TWRP v3.1.1 for the RAZR M KKBL (xt907 KKBL)
Built from source: http://github.com/minimal-manifest-twrp/platform_manifest_twrp_lineageos.git
All the usual prefaces to using this project. ie/eg I am not responsible for anything if you flash this zip in regards to your device or data etc etc etc
I have built this blindly (ie NO testing whatsoever) as I only have a JBBL device. It was easy for me to build since I have built a JBBL version, and I thought someone may find it useful IF it worked.
Please let me know if it works for you?
DiamondJohn said:
Please let me know if it works for you?
Click to expand...
Click to collapse
No-one has tried it?
Works like a charm for me
Worked like a charm here.
Shmaks said:
Works like a charm for me
Click to expand...
Click to collapse
trivialPotato said:
Worked like a charm here.
Click to expand...
Click to collapse
Now you just have to find a KKBL ROM to use it against :fingers-crossed: but maybe this will be a case of now that a way to flash it has been made, "build it and they will come"
Works great so far, just about to try a lineage rom.
DiamondJohn said:
TEAMWIN TWRP v3.1.1 for the RAZR M KKBL (xt907 KKBL)
Built from source: http://github.com/minimal-manifest-twrp/platform_manifest_twrp_lineageos.git
All the usual prefaces to using this project. ie/eg I am not responsible for anything if you flash this zip in regards to your device or data etc etc etc
I have built this blindly (ie NO testing whatsoever) as I only have a JBBL device. It was easy for me to build since I have built a JBBL version, and I thought someone may find it useful IF it worked.
Please let me know if it works for you?
Click to expand...
Click to collapse
Will keep you posted.
For anyone wanting to try this just a pointer. This isn't a TWRP flashable zip so you will need to use your computer to extract the IMG file and sideload using fastboot. Working great so far.
Does this require an unlocked bootloader? I am rooted.
---------- Post added at 01:36 AM ---------- Previous post was at 01:35 AM ----------
DiamondJohn said:
Now you just have to find a KKBL ROM to use it against :fingers-crossed: but maybe this will be a case of now that a way to flash it has been made, "build it and they will come"
Click to expand...
Click to collapse
I have XT907 KitKat 4.4. ready to try. Just need to know if I need an unlocked bootloader. That said, I am rooted.
DragonFire1024 said:
Does this require an unlocked bootloader? I am rooted.
I have XT907 KitKat 4.4. ready to try. Just need to know if I need an unlocked bootloader. That said, I am rooted.
Click to expand...
Click to collapse
you MUST have an unblocked bootloader to flash a custom recovery. ie this.
DiamondJohn said:
you MUST have an unblocked bootloader to flash a custom recovery. ie this.
Click to expand...
Click to collapse
I only asked because 1) wasn't mentioned in this thread specifically. 2) Not all devices require the bootloader be unlocked. 3) Why does it need to be a custom recovery? I still get confused about that from time to time because it just amazes me that it seems that's where things seem to always end up and sometimes seems to be a bit too convenient. I'm not vastly familiar with bootloader technology so that's where I scratch my head. I can install TWRP, get to all the settings and options, so why can't I just back up the proper files/imgs and flash the zip?
Looks like I'm going to have to rely on Sunshine then. I wish they accepted Bitcoin. It's that, or lose the phone to old age as it's components and functions fail slowly, one by one. I know I can reflash the stock firmware, it's been done a...few...times.
EDIT: Well s**t. Sunshine DOES accept Bitcoin. If I had known that ages ago...ugh
Just wanted to pass on this TWRP build for KKBL worked great. I ended up "downgrading" to JBBL in order to load a current LineageOS build.
It appears it was just me
I re-flashed my bootloader upgrade CAREFULLY via fastboot, and the error on wiping cache disappeared. however, I still haven't been able to flash a bootable KKBL ROM. It was suggest via PM that I also wipe my internal SDCard, which I have yet to try.
Shmaks said:
Works like a charm for me
Click to expand...
Click to collapse
trivialPotato said:
Worked like a charm here.
Click to expand...
Click to collapse
mr3p said:
Just wanted to pass on this TWRP build for KKBL worked great. I ended up "downgrading" to JBBL in order to load a current LineageOS build.
Click to expand...
Click to collapse
I see the posts saying it works, but has anyone actually successfully flashed and booted (ie past the bootanimation ) any ROM Zip file using this recovery?
Or performed a backup and restore?
I ask this as I finally got around to creating an upgrade (from JBBL to KKBL) for my phone (an xt905 not an xt907) and the two ROMs I tried both boot looped on the bootanimation. Also, I get errors when i try to wipe my cache.
Is it just me?
-----edit-----
I got a PM saying that someone has managed to flash an LP ROM for KKBL using this recovery. So obviously I need to go back to the drawing board on my upgrade to KKBL...
I am considering adding PDS (ie FSD) backup to my TWRP builds see https://forum.xda-developers.com/showpost.php?p=74136332&postcount=9 it also applies to KKBL.
DragonFire1024 said:
I only asked because 1) wasn't mentioned in this thread specifically. 2) Not all devices require the bootloader be unlocked. 3) Why does it need to be a custom recovery? I still get confused about that from time to time because it just amazes me that it seems that's where things seem to always end up and sometimes seems to be a bit too convenient. I'm not vastly familiar with bootloader technology so that's where I scratch my head. I can install TWRP, get to all the settings and options, so why can't I just back up the proper files/imgs and flash the zip?
Looks like I'm going to have to rely on Sunshine then. I wish they accepted Bitcoin. It's that, or lose the phone to old age as it's components and functions fail slowly, one by one. I know I can reflash the stock firmware, it's been done a...few...times.
EDIT: Well s**t. Sunshine DOES accept Bitcoin. If I had known that ages ago...ugh
Click to expand...
Click to collapse
The boot loader has to be unlocked because of the nature of the boot loader itself. I ain't no expert, but based on my understanding and what I personally know, here is what a boot loader does:
A boot loader checks the various images (recovery, boot, radio, etc.) and if any of these are incorrect/unsigned (like a custom recovery), your device won't boot. This makes sense, because most users aren't flashing their devices, so when an image is unsigned something is VERY WRONG. Unlocking a boot loader basically turns off the signature check that the boot loader does. If the boot loader isn't checking each image than it will boot up fine whether you have a custom recovery or not.
Recently reacquired an xt907 after "losing" mine. Anyways I rooted with Kingroot and used the mrw root.sh script to switch to supersu. I had to use an older version if kingroot, 4.9.6 for it to work. I then used the Sunshine app to unlock bootloader for $25 and used terminal emulator to 'dd' TWRP to recovery. Everything is perfect and am glad all still works as such.
Now my point: is there an easy guide or something that I can use to port an updated TWRP image? May thanks to everything.
DragonFire1024 said:
Recently reacquired an xt907 after "losing" mine. Anyways I rooted with Kingroot and used the mrw root.sh script to switch to supersu. I had to use an older version if kingroot, 4.9.6 for it to work. I then used the Sunshine app to unlock bootloader for $25 and used terminal emulator to 'dd' TWRP to recovery. Everything is perfect and am glad all still works as such.
Now my point: is there an easy guide or something that I can use to port an updated TWRP image? May thanks to everything.
Click to expand...
Click to collapse
Easy is a relative scale to the person asking the question. Read and answer it for yourself. TWRP builds are muuuuuch simpler than ROM builds.
The following two may mean you do not have to build. I have never used them, as I built mine from source.
https://forum.xda-developers.com/android/general/unofficial-twrps-devices-source-code-t3833338
https://forum.xda-developers.com/android/apps-games/twrpbuilder-t3744253
https://forum.xda-developers.com/showthread.php?t=1943625
The question may also be better asked, after reading, in the thread above

Categories

Resources