[RECOVERY][UNOFFICIAL] TWRP 3.4.0.0

[tendiez01]

touch screen is broken, XT2034-4 MetroPCS

 

[tendiez01]

touch screen is broken, XT2034-4 MetroPCS

*43-4, typo

 

[racenrich]

Success!!

with diligence and consistent tries, finally rooted my Moto-G...wahoo, no more ads!
the adb push was the only route i found successful, as touch within TWRP is unusable for this phone.
Still running stock...holding on on ROM for now.

thanks to the DEVS and support from others making this possible.
Rich K.

 

[KRaZy WaKa]

Has anybody tried this on a US retail unlocked moto g stylus? Sounds like most of the people commenting with issues are using the MetroPCS version.

I bought mine universal unlocked from Best Buy. Just looking to see if anybody else has used one of the factory unlocked moto g stylus with this TWRP build and if they're experiencing touch screen issues and whatnot

 

[racenrich]

Has anybody tried this on a US retail unlocked moto g stylus? Sounds like most of the people commenting with issues are using the MetroPCS version.

I bought mine universal unlocked from Best Buy. Just looking to see if anybody else has used one of the factory unlocked moto g stylus with this TWRP build and if they're experiencing touch screen issues and whatnot

Hey there....Yes I'm running the US version on T-Mobile

Thru the fastboot approach; I was successful in rooting stock rom.
All have been working as should.
(With Adaway...no more ads!)

TWRP gave me constant touch issues and don't own a OTG cable...yet...
Good luck

 

[KRaZy WaKa]

Hey there....Yes I'm running the US version on T-Mobile

Thru the fastboot approach; I was successful in rooting stock rom.
All have been working as should.
(With Adaway...no more ads!)

TWRP gave me constant touch issues and don't own a OTG cable...yet...
Good luck

Yeah I was specifically interested in TWRP functionality on a universal unlocked phone. I'm thinking Metro or possibly any T-Mobile version may have some slight variances. They seem to do that sometimes.

 

[Rev.X]

I have the US unlocked and I can confirm that the TWRP issues are present. with some diligence you can figure out where you need to press on the screen for which keys but I couldn't successfully get the bar to swipe to initiate the flash.

I was able to root and flash a different rom without TWRP but if you're really nifty if there was a working version

 

[griz.droidx]

Success!!

with diligence and consistent tries, finally rooted my Moto-G...wahoo, no more ads!
the adb push was the only route i found successful, as touch within TWRP is unusable for this phone.
Still running stock...holding on on ROM for now.

thanks to the DEVS and support from others making this possible.
Rich K.

Congratulations! If you've rooted a custom ROM isn't hard at all. Just read the OP of this and even other threads we especially the one about installing treble images (forgot the acronym) there's a bunch of useful info in the first few posts by the OP of that thread

Edit: I forgot that I too am on the US universal carrier/unlocked model purchased at Walmart.

Sent from my Moto G Stylus using XDA Labs

 

[sonyericsucks39]

No Issues with TWRP

I brought the Moto G Stylus directly from Motorola, and I have no issues with TWRP. Touchscreen fully works, and I made a complete backup before flashing Magisk. My build number is: QPRS30.80-58-7.

 

[tendiez01]

everyone that complained abt touch, this img was posted in the g stylus telegram. unzip and try it. works for me (XT2043-4 MetroPCS)

 

[freddyhank]

everyone that complained abt touch, this img was posted in the g stylus telegram. unzip and try it. works for me (XT2043-4 MetroPCS)

So far so good! Touch works (tendiez01 "Telegram group" version above, not the one linked by the thread originator)! I was able to wipe dalvik cache, and reboot into all modes without the OTG and mouse. I haven't gotten the chance to flash anything yet. BTW, what is the Telegram group link?

 

[SomeDooD123]

everyone that complained abt touch, this img was posted in the g stylus telegram. unzip and try it. works for me (XT2043-4 MetroPCS)

Could I get a link to the Telegram group please?

 

[tendiez01]

Could I get a link to the Telegram group please?

Yessir, here u go https://t.me/MotoGStylus

 

[bobbyp1086]

For those with touch screen issues. Using the twrp here works just fine, the point of entry is where the error lies.
Do not flash when you can see all the info and different things, that's the bootloader. Instead adb reboot fastboot from pc. It says fastbootd up top and like 3 or 4 options. This is the actual place you want to flash.
adb fastboot flash recovery recovery.img
That's The way the next command should look. From there reboot straight to recovery, or as I did and do, using volume to select reboot bootloader and then to recovery from there, once in twrp there is a password screen, use your screen lock if you set it up, if not just hit cancel it will still mount everything. The issue with the storage is because it's not decrypted, hence the password doesn't do anything.
Flashing anything fails due to this problems and that's where I'm stuck. Flashing the verity disabled and img is what I'm looking at but first.
1. Does it have to be a fresh flash of everything. Example: System, bl, vendor.... Or can I flash that img after setup and be ok.
2. ... That's it actually just need that answered. Not familiar with gsi. But very familiar with Android and the tricks they pull to keep us out

 

[ctschrodinger88]

Touchscreen Issues: I used the twrp here to fix things (notice: factory reset) :
like @bobbyp1086 mentions above.

adb reboot bootloader
fastboot boot twrp-3.4.0-0-sofia-test9.img

See also: https://support.motorola.com/us/en/solution/MS92002

Once it booted into TWRP. I went into TWRP and switched which slot it was set to use. (I had patched slot_b, so I switched to slot_a)
Then I rebooted.
It wasn't happy with me, and came to a built in recovery mode after failing to load the OS twice.
In the "recovery" mode I told it to factory reset the device. Which I was okay with because I had literally only worked on getting bootloader unlocked and then rooting.
After about 3/4 minutes it booted up right into the vanilla Welcome page with touch screen enabled.
Bootloader is still unlocked, and I plan on using the mechanism listed here https://forum.xda-developers.com/t/guide-to-root-motorola-g-stylus.4122713/post-83681901 to pull my boot.img and go again.

I would post much more robust steps, but my wife wants her phone back and I want to go to sleep


PS: As a note, it appears this will work once. And still leaves your device in an odd state.

 

[zfk110]

​

why touchscreen isn't working? how we can help you to fix this issue??

 

[zfk110]

So far so good! Touch works (tendiez01 "Telegram group" version above, not the one linked by the thread originator)! I was able to wipe dalvik cache, and reboot into all modes without the OTG and mouse. I haven't gotten the chance to flash anything yet. BTW, what is the Telegram group link?

It didn't work for me.

 

[zfk110]

For those with touch screen issues. Using the twrp here works just fine, the point of entry is where the error lies.
Do not flash when you can see all the info and different things, that's the bootloader. Instead adb reboot fastboot from pc. It says fastbootd up top and like 3 or 4 options. This is the actual place you want to flash.
adb fastboot flash recovery recovery.img
That's The way the next command should look. From there reboot straight to recovery, or as I did and do, using volume to select reboot bootloader and then to recovery from there, once in twrp there is a password screen, use your screen lock if you set it up, if not just hit cancel it will still mount everything. The issue with the storage is because it's not decrypted, hence the password doesn't do anything.
Flashing anything fails due to this problems and that's where I'm stuck. Flashing the verity disabled and img is what I'm looking at but first.
1. Does it have to be a fresh flash of everything. Example: System, bl, vendor.... Or can I flash that img after setup and be ok.
2. ... That's it actually just need that answered. Not familiar with gsi. But very familiar with Android and the tricks they pull to keep us out

still It didn't work for me. no tocuh screen

 

[flroots]

everyone that complained abt touch, this img was posted in the g stylus telegram. unzip and try it. works for me (XT2043-4 MetroPCS)

This also solved the touch issue for me. I just did the following:
1. extracted img from zip file: twrp_sofiap_auo_test2.zip
2. copied img file to my adb/fastboot folder
3. open command prompt at adb/fastboot folder
2. executed: fastboot flash recovery twrp_sofiap_auo_test2.img

I do have a question. Can someone recommend which partitions should generally be backed up? Thanks

 

[flroots]

I continue to investigate which partitions to backup in TWRP. One reason for my concern is that the backup size is almost 18GB whereas my G4 Plus backups were only 5GB even though I had the same apps installed. Of course one difference is Android 8 on the G4 Plus vs Android 10 on the G Stylus. I have attached photos showing the partition choices. There are two Super partitions listed with the same size. Are they the same? I'd love to hear what partition choices others have used and why. Thanks