Related
my phone which i bought today is updated to the latest and greatest. its a zenfone 2 WW_2.20.40.97
you would think this would be a simple click here click that with the 1-click tool "WinDroid Universal Android Toolkit v2.5".
I tried to play along even though I hate these "virus filled" utilties.
I clicked on Step 1. unlock bootloader and followed on my phone screen.
it gave me the message unlock success.
so i said ok great maybe it works.
i then clicked on the next step, flash twrp.
ha ha. thats where things went south.
it rebooted into bootloader and said some lines i couldnt keep up with.
i then moved onto step 3 which is Flash supersu.
now with this step its supposed to boot into what it had done in step 2 which is TWRP.
guess what? it doesnt.
it boots me into an android logo with an "error" message.
can anyone assist, please ?
Okay, first did you get the white splash screen when you booted up? This will tell you if the bootloader is indeed unlocked?
Second I don't know anything about the windroid tool but it may do some things and others not so much, there is a one click bootloader unlock we know works on 97 I would start there, also keep in mind there is a new update from last night and I would only unlock then update, then root and install twrp. Latest update is 134
Sent from my ASUS_Z00AD using Tapatalk
jimchee said:
Okay, first did you get the white splash screen when you booted up? This will tell you if the bootloader is indeed unlocked?
Second I don't know anything about the windroid tool but it may do some things and others not so much, there is a one click bootloader unlock we know works on 97 I would start there, also keep in mind there is a new update from last night and I would only unlock then update, then root and install twrp. Latest update is 134
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
i took a long route but i believe i got it done. i am still not sure if the bootloader is unlocked properly or not.
in any case heres what i did.
windroid:
Unlock bootloader --> success? i am not sure cause to unlock you'd need root?
and with that as i stated above twrp never installed.
i downloaded CWM_Zenfone_2_Intel and used that. it got me rooted.
after which i got the corrupted screen. but it finished and rebooted into CWM. woohoo!
i then installed SuperSU via CWM and that put the supersu icon and all was well..... almost.
i decided to do "reboot recovery". guess what? yellow triangle with error.
obviously this means no custom recovery was installed.
i headed over to the TWRP website and downloaded the custom TWRP recovery image. twrp-2.8.7.2-Z00A.img
back to Windroid: clicked on the commands tab; then "Flash recovery". it asked me for the file i downloaded, gave it twrp-2.8.7.2-Z00A.img and it flashed it.
did a reboot to recovery this time and voila. i got TWRP.
i am hoping this is now permanent?
i am still not sure. is my bootloader unlocked? how do i verify ? cause i was literally skipping steps back and forth.
Okay 2 things if your bootloader is unlock you will get white splash screen on boot up not black and 2nd of twrp has successfully replaced your stock then your bl is unlocked and you can boot into it whenever you go to recovery
Sent from my ASUS_Z00AD using Tapatalk
jimchee said:
Okay, first did you get the white splash screen when you booted up? This will tell you if the bootloader is indeed unlocked?
Second I don't know anything about the windroid tool but it may do some things and others not so much, there is a one click bootloader unlock we know works on 97 I would start there, also keep in mind there is a new update from last night and I would only unlock then update, then root and install twrp. Latest update is 134
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
jimchee said:
Okay 2 things if your bootloader is unlock you will get white splash screen on boot up not black and 2nd of twrp has successfully replaced your stock then your bl is unlocked and you can boot into it whenever you go to recovery
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
ok ya now everytime i click reboot recovery it goes to twrp.
what white screen are you referring to ? the one with the asus logo?
... and in reference to the 134 update. i never got that. i dont care about cause the whole idea behind twrp is to install custom roms from the roms section. i could care less about asus's crap rom. lol
Then your unlocked, and yes the one with the Asus logo,
Sent from my ASUS_Z00AD using Tapatalk
---------- Post added at 07:14 PM ---------- Previous post was at 07:10 PM ----------
Good luck then.... And on a personal note you should keep the c... Comments to yourself no place for that here.
Sent from my ASUS_Z00AD using Tapatalk
Here is the easy way to ROOT your Galaxy S6 edge plus with Marshmallow:
Download TWRP for S6 edge plus: (I mean Compatible)
https://dl.twrp.me/zenlte/
Download SuperSU V2.68 BETA or latest (2.78 Stable its OK)
http://forum.xda-developers.com/apps/supersu
Copy SuperSU to your phone
Remember to enable debugging mode and unlock device
Now flash TWRP via Odin (AP), remeber to unmark "auto reboot" in option tab
Restart to Recovery (Vol Up + Home + Pwr)
Flash SuperSu from TWRP (latest version, 2.68 was latest at the time of the post not now)
If You have tried other options could be posible that You have to re flash Marshmallow again and repeat the procedure.
I can conffirm It works
ROOT - 100%
SELINUX - intact
Battery - Testing but looking good. (Depends of your ROM and Kernel if You go beyond Stock )
I flashed TWRP but i have bootlop,. But TWRP from note 5 dr.ketan thread is fine..
Sent from my SM-G928K using Tapatalk
You can't flash the S6 Edge Plus recovery with the marshmallow bootloader. I think you need to flash a old bootloader first.
---------- Post added at 10:47 AM ---------- Previous post was at 10:45 AM ----------
Or I think you can flash Note 5 TWRP. (Tested Working)
UPDATE: PHONE GET "Unfortunately, the process com.android.phone has stopped." WITH NOTE 5 RECOVERY. DON'T TRY THIS WITH NOTE 5 RECOVERY.
AK1149 said:
You can't flash the S6 Edge Plus recovery with the marshmallow bootloader. I think you need to flash a old bootloader first.
---------- Post added at 10:47 AM ---------- Previous post was at 10:45 AM ----------
Or I think you can flash Note 5 TWRP. (Tested Working)
UPDATE: PHONE GET "Unfortunately, the process com.android.phone has stopped." WITH NOTE 5 RECOVERY. DON'T TRY THIS WITH NOTE 5 RECOVERY.
Click to expand...
Click to collapse
I flash note 5 recovery(nobleltezt) and working perfect with my s6 edge+ and no need to old booloader..
Sent from my SM-G928K using Tapatalk
Recovery works. You sure the root works? I just tried it, all sorts of errors started popping up when tried booting in the device.
AK1149 said:
Recovery works. You sure the root works? I just tried it, all sorts of errors started popping up when tried booting in the device.
Click to expand...
Click to collapse
Yup..root works perfect mate .. strange [emoji1] .maybe a different way,first i flash Cf-autoroot for my Sm-G928k and then flash note 5 TWRP revovery,
Sent from my SM-G928K using Tapatalk
I still recommend Auto-Root by CF.
uninstall supersu apk from your device
All the problems supersu 2.65 app in the markets
install beta super su with twrp
good root
no lag
there is no supersu apk icon, but no problem
Auto Root includes 2.68 apk.
No need for old BootLoader
ariefabuzaky said:
Yup..root works perfect mate .. strange [emoji1] .maybe a different way,first i flash Cf-autoroot for my Sm-G928k and then flash note 5 TWRP revovery,
Sent from my SM-G928K using Tapatalk
Click to expand...
Click to collapse
yes I can confirm. You don't need to flash the old boot loader. I also flashed CF-Autoroot first, boot it up once and then straight to flashing TWRP (via Odin).
Phone rooted and appears smooth. Battery life yet to be determined but at least my phone isn't overheating as it was with SuperSu v2.65.
rbt001 said:
yes I can confirm. You don't need to flash the old boot loader. I also flashed CF-Autoroot first, boot it up once and then straight to flashing TWRP (via Odin).
Phone rooted and appears smooth. Battery life yet to be determined but at least my phone isn't overheating as it was with SuperSu v2.65.
Click to expand...
Click to collapse
Good to hear that
Sent from my SM-G928K using Tapatalk
wich version of twrp do you use? (if possible with a link i try zenlte-zenlte and twrp-3.0.0-0-nobleltezt-nobleltezt)
le_pere_noel said:
wich version of twrp do you use? (if possible with a link i try zenlte-zenlte and twrp-3.0.0-0-nobleltezt-nobleltezt)
Click to expand...
Click to collapse
The last one working great
My phone cooks when I installed super user. Tried this and Dr ketans and cf autoroute. As soon as I uninstall, phone cools and all is good in the world.
Sent from my SM-G928C using Tapatalk
---------- Post added at 11:47 PM ---------- Previous post was at 11:47 PM ----------
Minus root
Sent from my SM-G928C using Tapatalk
---------- Post added 1st March 2016 at 12:00 AM ---------- Previous post was 29th February 2016 at 11:47 PM ----------
Edit: I still have full root access with superuser uninstalled. That's new...
Sent from my SM-G928C using Tapatalk
If you do it correclty you will have full functional SuperSu, phone isnt getting hot and battery is ok (Still cycling to see, and I think that a custom kernel will help but is ok)
If you dont have a SuperSu icon or is showing a old version maybe You had tried other solutions, in that case could be possible that You need to reflash MM to stock re try my way
I confirm full root access, other method gave me root access to apps but could not moddify system files; This way give You full root.
le_pere_noel said:
wich version of twrp do you use? (if possible with a link i try zenlte-zenlte and twrp-3.0.0-0-nobleltezt-nobleltezt)
Click to expand...
Click to collapse
I use the twrp-3.0.0-0-nobleltezt-nobleltezt.img.tar and it works like a charm.
Where and how can i get mm on edge+ G928T? Thanks
Sent from my SM-N920I using Tapatalk
This method of rooting triggering knox or not?
Yanardag said:
This method of rooting triggering knox or not?
Click to expand...
Click to collapse
Just got my S6E+ rooted as easily as I expected.
Cheers.
Yanardag said:
This method of rooting triggering knox or not?
Click to expand...
Click to collapse
I think custom recovery will.
Hey guys.
I have installed 6.10.13 MIUI 8.1. When i bought my mi5s phone they installed me that rom and told me that my bootloader is unlocked.
So my question is for someone to write me steps of installing lastest version of european rom. And i didnt find any rooting guide so I would be grateful if someone write me that.
Thanks in advance.
Rooting
You don't have to root the phone to flash custom ROM but be sure that bootloader is unlocked. Boot to fastboot and check: fastboot oem device-info. I have never used Roms from Xiaomi.eu because in general their rooms are Chinese weekly -chinese AP's + more system languages. English is fine for me.
There is a installation guide on site: https://xiaomi.eu/community/threads/6-11-10.36056/
zmajdk said:
You don't have to root the phone to flash custom ROM but be sure that bootloader is unlocked. Boot to fastboot and check: fastboot oem device-info. I have never used Roms from Xiaomi.eu because in general their rooms are Chinese weekly -chinese AP's + more system languages. English is fine for me.
There is a installation guide on site: https://xiaomi.eu/community/threads/6-11-10.36056/
Click to expand...
Click to collapse
Thanks for advice. What rom are you using then?
Tomislav995 said:
Thanks for advice. What rom are you using then?
Click to expand...
Click to collapse
Well, it is a ROM from reseller a modified Chinese I guess. Version 8.0.10.0.0. As everything works fine I will keep it as long as some better alternative comes. I have been reading about the others who switched to original Chinese but afterwards regretted they did it. If I were you, before you try some other ROM, I would flash custom recovery TWRP and save/backup current ROM you have now, just in case.
The other option is to flash original Chinese developer ROM and then root the phone and finally get rid of Chinese thrash.
Best luck!
zmajdk said:
Well, it is a ROM from reseller a modified Chinese I guess. Version 8.0.10.0.0. As everything works fine I will keep it as long as some better alternative comes. I have been reading about the others who switched to original Chinese but afterwards regretted they did it. If I were you, before you try some other ROM, I would flash custom recovery TWRP and save/backup current ROM you have now, just in case.
The other option is to flash original Chinese developer ROM and then root the phone and finally get rid of Chinese thrash.
Best luck!
Click to expand...
Click to collapse
OK. Thanks.
I just realized that they installed me twrp recovery 3.0.2 . Also checked that I have unlocked bootloader .
If I install that weekly rom, what will happen with my data?(will i lose data or it just wipe system and put newer version)
So my last question is how to root mi5s.
I saw in twrp that there is SuperSu option, is this one of ways to root phone?
I prefer eu rom have more optimization just download rom on your phone boot in twrp volume up and power install rom and after that wipe cash data is untouched. Reboot system phone will need some time to boot because it build cash and after that it start to optimize installed applications. It's really simple.
Sent from my MI 5s using Tapatalk
---------- Post added at 09:25 PM ---------- Previous post was at 09:24 PM ----------
For root install latest super su in twrp...
Sent from my MI 5s using Tapatalk
Thanks for answer.
But I want to be sure, Should i install su from twrp or I need to download and put zip in phone and then install?
Sry for being annoying and asking probably stupid question but I dont want to brick my device already hahah.
One more stupid question, I install SU after rom install?
Ok
Always make back up in twrp in case something happen..
I didn't root my phone but i root all phones that i have before.
So install rom first in twrp than flash super su in twrp all zips need to be on phone. I download everything that i need on phone directly...
Sent from my MI 5s using Tapatalk
People are panicking about TWRP not working on the latest Nougat firmware.
As an advanced user like me, I cannot live with a device with no root, so here is my solution.
Oh, and of course, your device need to be either bootloader unlocked, S-OFFed, or both.
What Is Magisk
Maybe.... you live under a rock?
Magisk Subforum on XDA
What This Will Do
Following the instructions here will install Magisk v9.1 (nearly same as official v9 with some fixes for cache support) and phh's SuperUser to your device.
You DON'T need any custom recovery, and your system partition is NOT touched at all.
Files and binaries are stored in the cache image, Magisk will move them to /data in the next reboot.
You can upgrade Magisk, phh root, and install other Magisk Modules within the Magisk Manager app!
Instructions
If a prebuilt boot image is available:
Download "magisk+phh_arm64_cache.zip", your prebuilt boot image, and unzip both
You should get "patched_boot.img" and "magisk_cache.img"
Install Magisk Manager and phh's SuperUser app
Reboot your device to download mode (adb reboot download)
Manually flash the images:
Code:
fastboot flash boot patched_boot.img
fastboot flash cache magisk_cache.img
Reboot and you're done!
If you are using other bases, then grab your boot image from your OTA package, and follow the instructions:
Download "magisk+phh_arm64_cache.zip", "magisk_boot_patcher.zip", and unzip both
You should get "magisk_cache.img", and a folder with scripts and tools
Grab ANY rooted device >Android 5.0 to do the patching. Running the scripts on an unrooted device will create an unbootable boot image!
Follow the instructions in the README.txt of the tool, it shall guide you to patch your own boot image
Downloads:
Prebuilt Cache Images:
ARM64(HTC 10): magisk-v9.1+phh-r266-2_arm64_cache.zip Prebuilt Boot Images:
US Unlocked: US_Unlocked_2.28.617.8_boot.zipMagisk Manager:
Latest Magisk Managerphh's SuperUser app:
phh's SuperUser (PunchUp Beta 9)
Reserved
Reserved
Just installed on US Unlocked HTC 10 running Stock Android N. Works great. I now have root back. Thanks for doing this.
Also, @topjohnwu correct me if I'm wrong, but if you install a Magisk Module that prevents your phone from booting, you can just re-flash the cache image. That would remove all modules you may have added and start back with just root.
And as an added bonus, I am also passing SafetyNet which I was not before do to the unlocked bootloader. Great work.
Sorry if it's already been answered in a different form it has been a while since I've been on here butt Am I able to just pull the boot image file out of the roms zip I am using or could I use the backed up boot image from the nand backup I have. Or do I have to do the Adb method. Thanks in advance.
Works great! Thanks for your work and share! @ topjohnwu
---------- Post added at 05:02 PM ---------- Previous post was at 05:02 PM ----------
This works well thank you. Has anyone been able to get xposed to work within it? I've tried to download all 3 and it will not install them - says Can't load the content at the
moment
EDIT - didn't know Xposed need SDK 24 for N... So disregard last bit
Will this work with Viper10 rom based on 2.28.401.6?
sardroid said:
Will this work with Viper10 rom based on 2.28.401.6?
Click to expand...
Click to collapse
it already has magisk/phh superuser. so there is no need to try this.
Excellent, device rooted..
Question : Now, can i delete Magisk Manager ??
Followed instructions using prebuilt 2.28.617.8. I'm getting a bootloop at green HTC logo.
Sent from my Nexus 9 using Tapatalk
I don't understand how to proceed if not US version :/
..
---------- Post added at 12:40 AM ---------- Previous post was at 12:37 AM ----------
GhastlyTT said:
Followed instructions using prebuilt 2.28.617.8. I'm getting a bootloop at green HTC logo.
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
Do you have any MicroSD inserted ? If yes, remove it.
psicobelico said:
..
---------- Post added at 12:40 AM ---------- Previous post was at 12:37 AM ----------
Do you have any MicroSD inserted ? If yes, remove it.
Click to expand...
Click to collapse
Thanks for the reply. I had thought of that and removed it-still boot looping.
@topjohnwu Any idea how to fix? I am also getting stuck on the green htc logo and it is just bootlooping.
serophia said:
@topjohnwu Any idea how to fix? I am also getting stuck on the green htc logo and it is just bootlooping.
Click to expand...
Click to collapse
I have to ask, what Rom are you using? Did you update to N OTA? Are you on Viper or one of the beta ICE or LeeDroid versions?
jsaxon2 said:
I have to ask, what Rom are you using? Did you update to N OTA? Are you on Viper or one of the beta ICE or LeeDroid versions?
Click to expand...
Click to collapse
I fixed the bootloop by extracting the stock OTA boot.img and flashing that. I did update OTA from M using TWRP then SD card flashing the firmware.zip. Really want your stock dialer module back lol.
jsaxon2 said:
I have to ask, what Rom are you using? Did you update to N OTA? Are you on Viper or one of the beta ICE or LeeDroid versions?
Click to expand...
Click to collapse
I OTA to Android N and wanted to try this out. Just flashed a stock boot.img and will see if that fixes the bootloop.
GhastlyTT said:
I fixed the bootloop by extracting the stock OTA boot.img and flashing that. I did update OTA from M using TWRP then SD card flashing the firmware.zip. Really want your stock dialer module back lol.
Click to expand...
Click to collapse
serophia said:
I OTA to Android N and wanted to try this out. Just flashed a stock boot.img and will see if that fixes the bootloop.
Click to expand...
Click to collapse
We're either of you using Magisk prior to OTA? I'm wondering if the magisk.img file was still in /data after you updated.
I RUU'd prior to taking the OTA so I was coming from a clean phone and did not have any problems installing this.
GhastlyTT said:
I fixed the bootloop by extracting the stock OTA boot.img and flashing that. I did update OTA from M using TWRP then SD card flashing the firmware.zip. Really want your stock dialer module back lol.
Click to expand...
Click to collapse
jsaxon2 said:
We're either of you using Magisk prior to OTA? I'm wondering if the magisk.img file was still in /data after you updated.
I RUU'd prior to taking the OTA so I was coming from a clean phone and did not have any problems installing this.
Click to expand...
Click to collapse
I was in fact using Magisk. I took the OTA with Magisk and Root installed. In fact, i have the AOSP lockscreen still lol.
jsaxon2 said:
We're either of you using Magisk prior to OTA? I'm wondering if the magisk.img file was still in /data after you updated.
I RUU'd prior to taking the OTA so I was coming from a clean phone and did not have any problems installing this.
Click to expand...
Click to collapse
Yes I was but i thought flashing stock boot.img will remove magisk seeing as how it allowed me to ota onto Android N perfectly fine.
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.