Recent content by rcboosted

so I got through most of this thread, let me see if I got this right. If I currently have rooted 10p, I can dirty flash to 20g after updating to TWRP 3.2.3-1 or later. What about 20h? Can I go 10p -> 20h directly?

I will give that a try. Thank you for all your work supporting this thread. *edit* skipping step2 and installing TWRP and Magisk manually worked!

Is this thread still supported? I hope so. I ran into the encryption unsuccessful issue. I unlocked the bootloader, now every time I start up, it says it's unlocked, as well as verified via fastboot getvar unlocked, it showed unlocked: yes. I flashed to a fresh 10p using uppercut, booted up...

I'm in the wrong thread.

post seems to be showing up late after posting.

I don't know if you got it or not, in case you didn't I'll just write up some quick steps for anyone else having similar issues. 1. unzip RSD_Lite_Motorola_XML_To_Batch_Script.zip to a folder 2. unzip the image from one of the depots 3. move all of the files (go into the folders until there are...

I was able to restore to stock via RSD_Lite_Motorola_XML_To_Batch_Script.zip, apparently the flashall utility might not flash all the files I needed. Or perhaps it was because I flashed Oreo on top of Nougat.

I have an ATT version of Z2 Force edition, it came with Nougat 7.x something. Tried to do the Oreo update by following this guide to update via Lenovo Moto Smart Assist: https://forum.xda-developers.com/z2-force/help/how-to-manually-update-att-motorola-z2-t3879143 During the Lenovo update...

I have a stock t-mo g pad x. I don't know what version OS it was on, but it has sat unused for some time. I took it out recently to run tinycam pro. It ran for a few days, and last week it just started rebooting itself and goes into a boot loop. I let it be a few times, and suddenly it won't...

I have this issue with many phones. the easiest way I found was sticking those cheap plastic screen protector on the screen. it unpolarizes the screen. the glass ones might do the same too, but I haven't tried.

That's unfortunate. Since you don't have the definition of these uncommon error code, is there anything that can be done to get the code and possible get a profile to work?

I turned on developer options and changed the log buffer size to 16M as you have then ran the report. The size is still very small, not sure if that's an indication of anything. Ran it twice.

I'm not sure what I'm doing wrong. I open mx player, open the video, it starts to play in sw, i switch to hw, it immediately gave me the error message, I click away(I have to) I open the menu to create the bug report. is there any step that I missed? what else can I do to get you an usable...

Just wondering if the new logs I pulled are sufficient.

Ok I did it again, I guess I didn't do it right. I opened the file, clicked on HW+, clicked off the prompt, ran the report. I did it both for HW and HW+