Database Info

[GUIDE][MOD] Splash Image

Ever since I got S-OFF on my G1, I set up a custom splash image. Here's how to do this on the Doubleshot (MyTouch 4G Slide).
Info:
The Doubleshot stores the splash image on the /dev/block/mmcblk0p14 partition, even though it only uses the first 768k of the 6MB partition. By default, this is a white image with green letters spelling the 'myTouch 4G slide' logo in the center of the screen and the '-T---Mobile-' gray and magenta logo above it.
Prerequisite:
Install and get familiar with the Android SDK see Android SDK | Android Developers also [HOW-TO] ADB for Dummies(How-To Learner's Guide) G1 Android Development
Unlock your T-Mobile MyTouch 4G Slide / HTC Doubleshot see How To Turn S-Off, Install MoDaCo Clockworkmod Recovery, and Install a Rom For Dummie
Install FFmpeg
Windows:
Extract the ffmpeg.exe file from the bin folder in ffmpeg-r25512.7z
- or Shortcut - get the getsplash.zip from gariak
Install the adb (Android Composite ADB Interface) and fastboot (Android Bootloader Interface) drivers from the android-sdk-windows\extras\google\usb_driver folder
Mac:
Might find this ffmpeg guide helpful - An easy install of the ffmpeg command line tool - Mac OS X Hints
Backup: (Optional)
To get the current image from the phone, execute this from a root shell:
Code:
dd if=/dev/block/mmcblk0p14 of=/sdcard/splash.img
On your computer, you can turn this into a PNG using ffmpeg from the command line:
Code:
ffmpeg -f rawvideo -pix_fmt rgb565 -s 480x800 -i splash.img -f image2 splash.png
Flash:
You can set the splash by converting an image you want to a 480x800 resolution PNG file, then use ffmpeg to convert it to raw565 format using the command line:
Code:
ffmpeg -i new_splash.png -f rawvideo -pix_fmt rgb565 new_splash.img
Then with an unlocked (S-OFF) bootloader, flash the new_splash.img file to your phone:
Code:
adb reboot bootloader
fastboot flash splash1 new_splash.img
fastboot reboot
OR you can flash from a terminal window on your phone. Be very careful with this method and triple check that you typed everything correctly so you do not accidentally brick your phone:
Code:
dd if=/sdcard/splash.img of=/dev/block/mmcblk0p14
References:
[GUIDE][MOD] Splash Image
[Request] MyTouch splash screen?
[TOOL] [Linux / OSX] Splash Screen creator / flasher
gravis86
gariak
An easy install of the ffmpeg command line tool - Mac OS X Hints
wilnotdie

Absolutely fantastic write up!
This is just the kind of information that belongs here in the dev section.
I like how you explained a lot of information that wasn't exactly necessary, but is very helpful to continue developing this topic in new directions.
Before anyone comes in and says there are threads on how to do this in the "themes and apps" section of the MT4GS forums, let me point out that they do not go into the detail and depth that this guide has done, and this write-up shows how to do it all manually.
Thank you for taking the time to lay this all out so people can see the process, and do it on their own.
MT4GS "themes and apps" links:
Replace your splash screen
Charlieb's gallery of pre-made boot splash images that you can flash with the new method listed here in dev:
Gallery Of Custom BootSplash Screens To Choose From

Great write up, much appreciated.

This was already posted back in September...

Already posted. Also wrong section.
Sent from my mt4gs

Madblaster6 said:
Already posted. Also wrong section.
Sent from my mt4gs
Click to expand...
Click to collapse
No, it hasn't, and no, it's not.
This is very helpful Dev material, which I have already been referencing to try to solve a splash flashing issue.
Please post a link to where it was already posted if you think that was the case, but there are no other dev postings to my knowledge that contain this very useful information.

Blue6IX said:
No, it hasn't, and no, it's not.
This is very helpful Dev material, which I have already been referencing to try to solve a splash flashing issue.
Please post a link to where it was already posted if you think that was the case, but there are no other dev postings to my knowledge that contain this very useful information.
Click to expand...
Click to collapse
Androidautobot referenced this writeup back in September on the MT4GS part of the site....
http://forum.xda-developers.com/showthread.php?t=1258873
@reukiodo - I used your method back in my G2 days so I thank you for that.
Not meaning to steal some else's spotlight but in case anyone seriously needs a noob proof method as posted by others as well and the way I did it back when I still had a MT4G is to go with TrueBlue_Drew's method....You'd have to be a true square headed moron to screw up...
http://forum.xda-developers.com/showthread.php?t=956434

Thanks, jsyi84.
I know about those links in the themes & apps section - and for users that's great.
Neither of the two threads in themes & apps contain the developers info that is included in the OP of this thread.
That's okay, it's not their purpose, which is why they are over in themes & apps.
This thread is a reference for people working on creating things like the utilities linked to in the other threads, and not really targeted at end users.

jsyi84 said:
This was already posted back in September...
Click to expand...
Click to collapse
Madblaster6 said:
Already posted. Also wrong section.
Click to expand...
Click to collapse
I apologize if you think this is a duplicate post or in the wrong section. In my search I was looking for which partition the splash image was stored on, and was unable to find that information.
Now with the reference provided, I see that information was already available, however difficult to find.
In response, I hope you agree that this post has all the information related to the splash image in one location, including a copy of the original splash image.

reukiodo said:
I apologize if you think this is a duplicate post or in the wrong section. In my search I was looking for which partition the splash image was stored on, and was unable to find that information.
Now with the reference provided, I see that information was already available, however difficult to find.
In response, I hope you agree that this post has all the information related to the splash image in one location, including a copy of the original splash image.
Click to expand...
Click to collapse
It's a very valuable piece of information I figured you'd be happy to know someone else already posted a topic referencing your topic lol. I agree it's easier for others to find posted here than having to hunt around in another phones forum lol.....sort of like how some people had to go in the g2 forums to downgrade to 2.2 in order to root their phones in the mt4g forums which only adds to confusion to some as for most people it's a red flag having to do stuff to their $400+ device from information posted for an entirely different phone lol.

+1
10char

I used this tool ages ago when I first got my Doubleshot. It is by far the easiest way to change the splash screen, and is great for noobs. Just follow the prompts, and presto change-o you have a new splash screen!
http://forum.xda-developers.com/showthread.php?t=956434
Here is my splash screen, I love it, but I have had it for so long I may change it to something else now.

Fastboot + Recoveries (My Gift To You)

You can get it from here:
Fastboot + Recoveries.7z
I decided because it get's a little tad difficult to find what you might want or need for Recoveries and Fastboot, (I had a B**** of a time myself )
I'd thought it would be nice to offer my assitance, (because I haven't done a d**n thing to contribute since I bought the Q )
So here's a list of nice things I elegantly made for you (Don't ban me mods :angel: :fingers-crossed: )
*What To Do*
For A Little Assistance:
Linux: go to folder and "Right Click" Click on "Terminal/Konsole"
Type "su" (without quotes)
Then copy/paste any of the following (not anything in parentheses)
fastboot flash recovery open_recovery.img (Open Recovery's Mod) (Skrilax_CZ)
or
fastboot flash recovery cwm.img (Clockwork's Mod) (Shabby Penguin)
or
fastboot flash recovery twrp.img (Team Win Recovery Pro) (arrrghhh)
or
fastboot flash recovery recovery.img (Stock Recovery Image) (dunno)
Windows: Go to folder and press "SHIFT and Right Click" run command window (or something close to it)
Then any of the upper ones
Mac: I don't know how to use it, but hey it's here.
Oh yeah thanks to falln Saint, I have my favorite boot logo
It's an android popping it's head out on the Moto with the phone name underneath
fastboot flash logo moto.img
Hope I helped, Have fun :good:
SYKKNYZZ
P.S. I only made it easier to find the files, I didn't create them.
Real credit goes to the members on XDA who work their a** off to help us out. :highfive:
P.P.S. I don't come here often, but if there is any problems, I will answer them as fast as i can.

Why not just link to the thread, where you got the recovery? Including them all in one big .7z file doesn't make a lot of sense - if TWRP or OpenRecovery are updated, that .7z file you have is now outdated...
Just a thought - interesting to see the stock recovery tho!

True
arrrghhh said:
Why not just link to the thread, where you got the recovery? Including them all in one big .7z file doesn't make a lot of sense - if TWRP or OpenRecovery are updated, that .7z file you have is now outdated...
Just a thought - interesting to see the stock recovery tho!
Click to expand...
Click to collapse
Thanks arrrghhh, I just thought to make this simple as possible.
But I do like what is going on with the new roms, I have AOKP because Carbon kept glitching on me and deleting my savedata and setting it under a folder called 0

SykkNyzz said:
Thanks arrrghhh, I just thought to make this simple as possible.
But I do like what is going on with the new roms, I have AOKP because Carbon kept glitching on me and deleting my savedata and setting it under a folder called 0
Click to expand...
Click to collapse
This isn't a glitch, it's a "feature" with 4.2.2.... Unfortunately the more 4.2.2 ROM's you flash, the more this feature will become apparent.

arrrghhh said:
This isn't a glitch, it's a "feature" with 4.2.2.... Unfortunately the more 4.2.2 ROM's you flash, the more this feature will become apparent.
Click to expand...
Click to collapse
Yeah I realized that, but Unicorns are for Gangsters.
And I might go back to carbon, if it didn't delete my info even when I reboot normally after flashing. But thanks for your hard work.
Any way I can be a beta tester for any upcoming products?
I am staying a Q Fan until next upgrade on my contract thru sprint
Sent from my Asanti C using xda app-developers app

I had about 7 "0" folders when I browsing my phone's files looking for a cache'd boot logo...it was like one of those russian dolls with a smaller and smaller doll inside and could not figure out what the heck was going on, lol. Ended up deleting all but the first parent and didn't seem to cause any issues....free'd up a good gig or two of internal storage space! Good to know now what the cause of this was as I was experimenting with a lot of different recoveries around the time this happened. Thanks^^

Argh! I came to this thread hoping for a nice, organized place to find all the links/downloads I needed to fix my girlfriends phone.
Now I have to read, AND continue my search for the files. (mild sarcasm)

Moto x BootLogo [With instructions N00B Friendly]

Okay.... I know its late but still here are some boot logos for the moto x .
NOTE: This is not a flashable zip... u have to extract the desired logo.bin to the folder in which fastboot and adb are present...
Currently There are 2 logos....
NOTE: Your device must have a unlocked bootloader for this to work.
1. Connect Your Device To Your PC
2. Make sure you have android sdk or the minisdk installed
3. Extract the desired logo.bin to the platform-tools folder
4.(a) Hold shift and right click anywhere in the platform tools folder and select open command window here
OR
(b) Open command prompt and navigate to the platform-tools folder
5. Reboot to bootloader using this command:
Code:
adb reboot bootloader
6. After the device boots into the bootloader execute this command to flash the bootlogo
Code:
fastboot flash logo logo.bin
Done..... Any problems Ask Below..

They look good. Gonna install the joker when I get a chance tonight.
Sent from my XT1053 using XDA Premium 4 mobile app

Thanks

UPDATE 1
Okay... i will be making more logos and also im taking requests... Here is Mortal Combat.....
The instructions to install are the same
Enjoy...:good::good:

UPDATE 2
Update 2
Abstract moto x bootlogo
Note: All the updates will be included in the bootlogo.zip

How bout the joker face from dark knight, plain and simple similar to this possibly with the "why so serious" text
Sent from my XT1060 using XDA Free mobile app

Sure I'll upload it soon
Sent from my XT1052 using XDA Free mobile app

Not to burst your bubble... but there were already a few threads about changing your bootlogo... including instructions on how to make your own.
For LOCKED bootloader there is -> http://forum.xda-developers.com/moto-x/general/changing-moto-x-bootlogo-root-t2445150
For UNLOCKED bootloader there are...
http://forum.xda-developers.com/moto-x/themes-apps/moto-x-boot-logos-t2417961
http://forum.xda-developers.com/moto-x/general/4-4-3-remove-unlocked-bootloader-message-t2548566

KidJoe said:
Not to burst your bubble... but there were already a few threads about changing your bootlogo...
Click to expand...
Click to collapse
But... How do you know he doesn't already know and just posting the info with his in case someone else doesn't know? Lol
Sent from my XT1053 using XDA Premium 4 mobile app

Nemosfate said:
But... How do you know he doesn't already know and just posting the info with his in case someone else doesn't know? Lol
Sent from my XT1053 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Exactly. Im just making and posting bootlogos... If i wouldnt include instructions people wuld have to findd another guide which frm my experience is a pain in the ass ...

Done.
Jexx11 said:
How bout the joker face from dark knight, plain and simple similar to this possibly with the "why so serious" text
Sent from my XT1060 using XDA Free mobile app
Click to expand...
Click to collapse
Sorry it took this much time but i had some problems... Here it is... Joker Bootlogo... The classic joker Enjoy!:laugh:

Here is a little demo I stumbled upon in the X
Also found these folx in the same directory.......

nipunx1999 said:
Exactly. Im just making and posting bootlogos... If i wouldnt include instructions people wuld have to findd another guide which frm my experience is a pain in the ass ...
Click to expand...
Click to collapse
This thread -> http://forum.xda-developers.com/moto-x/themes-apps/moto-x-boot-logos-t2417961 , started a long time ago, was a repository of replacement LOGO.BIN files, and has instructions to make your own logo.bin and flash...
But either way is fine.

KidJoe said:
This thread -> http://forum.xda-developers.com/moto-x/themes-apps/moto-x-boot-logos-t2417961 , started a long time ago, was a repository of replacement LOGO.BIN files, and has instructions to make your own logo.bin and flash...
But either way is fine.
Click to expand...
Click to collapse
Ur telling me that there r other forums n u make a new one today. Just WOW. *applauds*
http://forum.xda-developers.com/moto-x/themes-apps/collection-moto-boot-services-t2885395

nipunx1999 said:
Ur telling me that there r other forums n u make a new one today. Just WOW. *applauds*
Click to expand...
Click to collapse
No, actually, I'm telling you there was already another thread with replacement LOGO.BIN files, with instructions on how to make. And if you used the link I posted to view that thread, you would have seen it was started originally In Aug 2013, and we added new info in June 2014 for the 4.4.x updates.
nipunx1999 said:
http://forum.xda-developers.com/moto-x/themes-apps/collection-moto-boot-services-t2885395
Click to expand...
Click to collapse
I think you need to look more closely at what thread your are quoting. ^^^ This thread of mine that I just made today, is repository of all the Boot Animations from the Moto Boot Services App (in flashable format), and since it may also be asked for, the LOGO.BIN's too (since moto boot services doesn't change the LOGO.BIN on unlocked bootloaders)
Its not the same any any other threads to date. It is not a repeat.
While yes, I've created LOGO.BIN's from the CLOGOs that Moto Boot Services pushed down, and included them in a ZIP a while ago. As noted in the thread, when I get time, I will change it and put just those from Moto Boot Services there.
HOWEVER, not all of the Boot Animations from the Moto Boot Service app have been posted before, even when you look at the separate threads that had been created when the boot animations had changed. And that is the point of that thread. The Boot Animations from Moto Boot Services.
In contrast this thread is a duplicate of at least two other threads (which I've provided links to) instructing users how to flash a custom logo.bin, containing ready made logo.bin's, but unlike the other two, this thread doesn't say how to make them.
Either way.,... carry on.. and have fun. C'ya

Sorry, this is going to come off bad after what I've already posted but after downloading the sample logo.bin's you've posted I have some questions about them.
1. How were they made?
2. Do they contain just the single graphic? Or do they contain the "M" graphic, 0-3% battery graphic, and this new graphic?
I ask because the MLOGO tool (See -> http://forum.xda-developers.com/moto-x/themes-apps/app-moto-x-g-boot-logo-command-line-tool-t2819494 which is another thread about creating and flashing custom LOGO.BIN files), errors on each of these when trying to list the included elements. And opening with a hex editor they don't have the normal header which would mean they are a single image graphic.
While not a big problem, having just a single image means that if the battery level is below 3%, and the phone is off and charging, the user will not see anything on the screen, making it seem like the phone is dead, until the battery reaches 4% or above.

I made them using the original logo.bin file and edited it using Photoshop and gimp....
Sent from my unknown using XDA Premium 4 mobile app

V20 unHARD-brick experiment [Looking for Eng/Debug H918]

Hey all
I have bricked my t-mobile V20 trying to network unlock it.
Anyway, I have been investigating solutions to this problem, and well, let's say there is no easy solution for most people.
The problem as I see it, is that this chipset (msm8996), while not exactly super new, is for all intents and purposes VERY new indeed. Because of the widespread use of UFS NAND introduced with this cpu. Almost all phones based on these newer qualcomm chips use this modern storage, which works as a multi-LUN device. Meaning it will show as several independent logical storage devices depending on configuration. V20 has 7, or at least the H918 does.
In short, it means the storage device is no longer mounted in mmcblk0, but on /dev/sda sdb sdc... etc depending on how many LUN's.
So the community has not catched up yet to this new development. (Well I guess hard-brick has always been a pain for many phones, but this makes it worse)
Now there are, I think, 5 ways to approach the 9008 mode in this instance.
*JTAG: Bypass all this QC hodge-podge and program the darn NAND directly.
*USB with Box: Some type of box with the capability to program your specific phone. Proprietary, closed source, have to pay.
*USB with firehose: Program yourself with programs like QFIL. Need device specific "prog_ufs_firehose_8996*.elf" file. LG has not released this. Can probably only be leaked, which happens on occasion.
*Enter DL or 9006 mode: It may be possible to short certain test points on the motherboard, which will put the phone into 9006 or Download Mode. Would require instructions, or the Service Manual.
*SD-Card Rescue: Make an sdcard with the required partitions. Some say this can't be done on newer QC chips with UFS because of the aforementioned multi-LUN situation.
I have been looking into this SDCARD method, and I found some info on the DragonBoard 820C (which uses msm8996, with UFS). This board has 6 LUN's, so it's multi-lun just like V20.
If you see here: DragonBoard, there is listed a method of SD CARD rescue. The tools can be found here: db-boot-tools
Unfortunately I don't have a full dump of my partitions, so I only have the ones included in the TOT, or KDZ files. I tried making a image using those files, it didn't work, but something interesting happened. With this sd card inserted the phone does not show the qdloader 9008 port on my pc, actually nothing shows. I did double check using a normal card inserted, and yes with normal storage card qdloader 9008 mode appears.
So this is interesting and makes me think I should try some more with this, but I need someone with a T-Mobile H918 to dump their partitions. EFS is not needed (where the imei is).
Update: I currently don't need a dump (Except for engineering firmware).
Update2: I could not make the SD-Card boot work, see here (with normal firmware).

List partitions
Command: ls -l /dev/block/platform/soc/624000.ufshc/by-name/
Or this: ls -al /dev/block/bootdevice/by-name/
Then dd the relevant partitions not listed above: dd if=/dev/sd*1/2/3/4... etc of=/sdcard/"filename".img
As an example, maybe you can do it other ways, perhaps with an app.
You can also use the patched LGUP to dump partitions. Should be the simpler method.
In any case I will be grateful for your assistance, as I'm sure many others will if this pans out.
Engineering Rom: I got an idea, if I can't get this to work then maybe it's because the support isn't compiled in the bootloader. If I could get the eng-firmware (for H918) to test that it would be great. So please if you have an eng device or a dump of that, I would be thrilled try it out.
Update: Below I've attached a zip with a limited partition layout, and the commands to dump from adb. Use the patched LGUP for Engineering firmware. (actually, with engineering formware I need all, or most of the partitions. PM me if you have such a device)

Support your work. Lg
China user

I would certainly go the QPST/QFIL/Firehose method & my strategy would be to restore Download mode.
I'm sure once that has happened you can restore full firmware with the patched LGUP method here

Prowler_gr said:
I would certainly go the QPST/QFIL/Firehose method & my strategy would be to restore Download mode.
I'm sure once that has happened you can restore full firmware with the patched LGUP method here
Click to expand...
Click to collapse
Yes, but how would you go about doing that without the required firehose file? LG apparently uses certificate or some signing, so you can't use just any file.
Although that patched LGup is nice. If I had known about that tool before I messed up, I probably would not have messed up. Because then I wouldn't be afraid of loosing root, and just flashed H910pr with LGup, then flash back with the patched one later.
Edit: As I have later found out ^^this would not be a good idea. The result would be the same - BRICK Hard. Just as a precaution for anyone contemplating doing so. The H918 can not be flashed with any other V20 firmware, neither can you flash H918 firmware on any other V20.

askermk2000 said:
Yes, but how would you go about doing that without the required firehose file? LG apparently uses certificate or some signing, so you can't use just any file.
Although that patched LGup is nice. If I had known about that tool before I messed up, I probably would not have messed up. Because then I wouldn't be afraid of loosing root, and just flashed H910pr with LGup, then flash back with the patched one later.
Click to expand...
Click to collapse
I don't pretend to know the answer, but I believe that the firehose file is not any type of signed LG file, but just a partition layout (mbn or elf) file that can be generated from a .kdz file...
Make sure you use QPST_2.7.460 or later which supports MSM8996...
Google is your friend but you can start reading from here & here

Prowler_gr said:
I don't pretend to know the answer, but I believe that the firehose file is not any type of signed LG file, but just a partition layout (mbn or elf) file that can be generated from a .kdz file...
Make sure you use QPST_2.7.460 or later which supports MSM8996...
Google is your friend but you can start reading from here & here
Click to expand...
Click to collapse
Well, there is a difference between an MPRG and MSIMAGE/Singleimage. I believe you are thinking about the latter here. Those can be generated, but are of little use without a programmer file (mprg/firehose).

askermk2000 said:
Well, there is a difference between an MPRG and MSIMAGE/Singleimage. I believe you are thinking about the latter here. Those can be generated, but are of little use without a programmer file (mprg/firehose).
Click to expand...
Click to collapse
Remember we only aim to get bootloader mode, not the full layout...
Btw I probably wouldn't mind wasting $5 on this

Prowler_gr said:
Remember we only aim to get bootloader mode, not the full layout...
Click to expand...
Click to collapse
Yes I know. But Qualcomm and LG has made that very difficult for us. All the common info on the web so far is outdated, or doesn't work because of missing firehose file.
Except for possibly SDcard method.

Having read your OP again, of how you SD card affects how windows detects your phone, I believe this may be a good step to our solution. of getting the phone recognised in download mode

Prowler_gr said:
Having read your OP again, of how you SD card affects how windows detects your phone, I believe this may be a good step to our solution. of getting the phone recognised in download mode
Click to expand...
Click to collapse
Do you have brick as well?
I looked at that page, and pretty sure I've looked at it before. There is nothing there that can be of use.

askermk2000 said:
Do you have brick as well?
I looked at that page, and pretty sure I've looked at it before. There is nothing there that can be of use.
Also I'm very suspicious of that Aryk site. They don't seem to know what their talking about many times, their downloads dubious with viruses and the like. On the page you linked they claim QHSUSB_BULK is the same as 9008, while it is actually 9006.
It almost seems like that site was set up solely for the purpose of spreading malware or something. Just cobble up something random and presenting it like information, like with algorithms and bots or whatever.
I think there a lot of that stuff going on in the "gms" business. Like for example, on gsmarena I found a sticky thread which supposedly had files to repair a LG V20 which has been stuck in bootloop because of "use of cheap chinese usb-c cable". Anyway, that archive had some files, including a *prog_ufs_firehose_8996_lite.elf*. That file did not work, and there was an instructions file there also, in XLS format which contained virus.
Come to think about it. This whole crap with qualcomm "security" stuff seems like just a way to create the sub-market of gsm repair boxes. Well, who knows, just a guess on my part. But there's something fishy about the whole thing.
Click to expand...
Click to collapse
I was, I'm now unbricked (I worked out the method with the LGUP patch).
What I'm suggesting (as the website describes) is to write the v20 boot image to an SD card using Win32DiskImager/, & see if your device will boot with it, & then upgrade with LGUP.
I've got the H990DS variant (I can send you my boot image to try)

Prowler_gr said:
I was, I'm now unbricked (I worked out the method with the LGUP patch).
What I'm suggesting (as the website describes) is to write the v20 boot image to an SD card using Win32DiskImager/, & see if your device will boot with it, & then upgrade with LGUP.
I've got the H990DS variant (I can send you my boot image to try)
Click to expand...
Click to collapse
I would welcome a boot image, or images of partitions. That's why I started this thread mostly.

askermk2000 said:
I would welcome a boot image, or images of partitions. That's why I started this thread mostly.
Click to expand...
Click to collapse
link removed

Prowler_gr said:
...removed
Click to expand...
Click to collapse
Ok, I got it. Thx
Will try with this. Did you get it with LGUP ?

I extracted it from my phone

Prowler_gr said:
I extracted it from my phone
Click to expand...
Click to collapse
Im in this to but i have a lg g5 msm8996 board
me and him have been trying to work very closely to get a fix for msm8996 in gen of coarse he is worried about v20 me g5 but common interests.
i dont wanna knock any v20 discussions off track so im here but im sitting in the corner most quietly
he is def on the right track i have dealt with many hardbricks in the past
and the no reconition on pc is most def a good step
my problem is being a new moderator plus my job plus after hours work i dont have time to test a lot of stuff any more he has bought a lot of info to my eyes and am trying to work on what i can.
look and 8994 g4 it took 2 years for a hardbrick fix to come about only from people doing the same as we are

TheMadScientist420 said:
Im in this to but i have a lg g5 msm8996 board
me and him have been trying to work very closely to get a fix for msm8996 in gen of coarse he is worried about v20 me g5 but common interests.
i dont wanna knock any v20 discussions off track so im here but im sitting in the corner most quietly
he is def on the right track i have dealt with many hardbricks in the past
and the no reconition on pc is most def a good step
my problem is being a new moderator plus my job plus after hours work i dont have time to test a lot of stuff any more he has bought a lot of info to my eyes and am trying to work on what i can.
look and 8994 g4 it took 2 years for a hardbrick fix to come about only from people doing the same as we are
Click to expand...
Click to collapse
We agree he's on the right path (about SD method), that's why I sent him my boot image & suggested he burns it into an sd card. I'm hoping he only needs to boot with it & everything else would be straight forward

I burned the *.img file directly onto a 64gb uSDXC card. It creates a single 63gb fat mbr partition on the card. So it seems you managed to make a single complete image of your entire UFS chip. Have no idea how though, but I've not exactly had the chance to look into that myself because of brick.
The image, burned this way did not work, it's not even recognized by the phone as a boot image. I will see if I can perhaps extract the file from within the img-file and split that somehow.
Because windows can't edit/remove partitions on external devices, I used linux, since ubuntu's standard tools there can simply burn the image directly onto the device, automatically removing any partition scheme in the process.
That win32diskimager program is strange because it can not target device directly, but only mountpoint, and because my card was already formatted with numerous partitions from before, I could not use that program.

Prowler_gr said:
We agree he's on the right path (about SD method), that's why I sent him my boot image & suggested he burns it into an sd card. I'm hoping he only needs to boot with it & everything else would be straight forward
Click to expand...
Click to collapse
That has always been the rite track just to get to download mode.
I thank you for providing the files. Its always stressful when dealing with owns hardbrick. ive spent hours of burning images to mine lol even fried a couple sd cards
but most def seems as if you are knowledgeable also in this area so id love to keep you in this loop
If we all can pull this off. We will be the next heros of the day lol also if u are interested in reading some suposedly the s8+ also has same boards so even may be able to piece stuff from there
and i know sammys have been booted of sd in the past.
the more people we can get the better

Development TWRP for Moto G Stylus 2021 xt2115-1 (otg mouse necessary)

OTG adapter and mouse necessary
I am wondering if anyone can fix this recovery or possible port a new one with the files I have included. I am willing to test if you don't have a device to test on. My original post is here
Post in thread 'TWRP coming?'
TWRP coming?
Just saw the following article from XDA regarding TWRP v3.5 being released. I'm hopeful that this means that for devices that ship with Android 10 that TWRP will be able to decrypt the data partition in order to facilitate a complete backup...
forum.xda-developers.com
Here are the files and recovery backups.
Resolution is 1080x2400
Board is SM6150
Aarch64
Stock android 10
Please help anybody with the know how. Thanks. I'll buy anybody a pizza for doing this! Get it working right and I will definitely support.
External_sdcard says unknown filesystem but still functions to backup all partitions except /vendor, /system and /product individually. Allows /super backup.
/vendor and /system_root (permission denied)
touch screen not functioning in recovery
Flashing causes black screen after boot logo splash
I used AIK on windows 10 with notepad++
*EDIT*
added driver to /sbin in /ramdisk. updated recovery below.

Hey, do u have telegram? If so hit me up on there @rcc2002 username "Ritmo".. Im working on getting you help on this subject as soon as possible because I am so happy that you were able to create this. It does temporary boot. I didn't try flashing it but the problems that create the black screen I believe are Android security during boot, usually something to do with dmverity i think, the no touch screen working is usually a driver issue that just needs a proper driver being installed in the build. Or even pushed with a terminal cmd poss I've seen.. And the two errors coming up permission denied for system root is one I've seen before and is I believe very common. All mostly has to do with Android security and all the little annoying issues in building a permissive recovery I suppose. But anyway the dude I'm going to ask will basically tell you probably exactly what to do the second he sees or hears the errors and sees ur files.. what do the two zip files contain? And how did you build this exactly? Curious.. from common trees from scratch or a device tree builder? if you don't have telegram, just text me 856-896-7600..... ~RAY..

They contain most of kernel files and recovery and boot stock backup. Build.prop fstab and ueventd.rc. Also the device tree all pulled from the device root using root explorer. I ported this over from a different device that had the exact same specs. I used AIK for windows and modified the files to correlate with the moto g stylus 2021.

ID like to work on this also do you have someway to communicate? I may have found one of the kernel source codes you can try building with.

In all honesty I just need somebody to help me learn how to install touch drivers into the recovery. Then I will use avbtools to resize the file to its proper size. Just need the info. The rest of the recovery works. I've tested almost all of it. Haven't tested adb yet but I'm sure that won't be a problem if faulty.

Here is the block partitions I used to partly configure the recovery. It's a bit messy but I think it's OK. Not trying to type all this out. Pulled from device last night.

sosthenisRR said:
OTG adapter and mouse necessary
I am wondering if anyone can fix this recovery or possible port a new one with the files I have included. I am willing to test if you don't have a device to test on. My original post is here
Post in thread 'TWRP coming?'
TWRP coming?
Just saw the following article from XDA regarding TWRP v3.5 being released. I'm hopeful that this means that for devices that ship with Android 10 that TWRP will be able to decrypt the data partition in order to facilitate a complete backup...
forum.xda-developers.com
Here are the files and recovery backups.
Resolution is 1080x2400
Board is SM6150
Aarch64
Stock android 10
Please help anybody with the know how. Thanks. I'll buy anybody a pizza for doing this! Get it working right and I will definitely support.
External_sdcard says unknown filesystem but still functions to backup all partitions except /vendor, /system and /product individually. Allows /super backup.
/vendor and /system_root (permission denied)
touch screen not functioning in recovery
Flashing causes black screen after boot logo splash
I used AIK on windows 10 with notepad++
*EDIT*
added driver to /sbin in /ramdisk. updated recovery below.
Click to expand...
Click to collapse
Contact me on telegram, I could possibly help. @Electimon

is anyone working on twrp for the xt2131-1?

aaronj1993 said:
is anyone working on twrp for the xt2131-1?
Click to expand...
Click to collapse
No, also that's the 5G https://forum.xda-developers.com/f/moto-g-stylus-5g.12373/

ShayBox said:
No, also that's the 5G https://forum.xda-developers.com/f/moto-g-stylus-5g.12373/
Click to expand...
Click to collapse
yes I know but that's the next closest device.

I'm mid-level to flashing but new(ish) to XDA here. Since this device is so similar "can" you flash the 5G ROMS to the 2021 ? And it boot/work somewhat ? Referring to Lineage OS for the most part since these devices are still somewhat "new" .. Trying to find the best place to ask and this seems to be it so far. No posts much yet in 2022 ..

roiikka said:
I'm mid-level to flashing but new(ish) to XDA here. Since this device is so similar "can" you flash the 5G ROMS to the 2021 ? And it boot/work somewhat ? Referring to Lineage OS for the most part since these devices are still somewhat "new" .. Trying to find the best place to ask and this seems to be it so far. No posts much yet in 2022 ..
Click to expand...
Click to collapse
The Moto G Stylus 5G has a different SoC, so this most likely would not work.

I just upgraded to android 11 on my moto g stylus 2021 XT2115-1 but now I cannot figure out how to root it I can install magisk and patch the boot but it does not stick and keep root but it does show ramdisk as yes, so not sure what the deal is, it has been awhile but it looks like to achieve it we will have to get rid of dmverity and vbmeta at least. to be able to keep a root or roll back to droid 10.

Well I cannot help with twrp but I was able to upgrade to android 11 and get root with magisk rather easily check this post all credit goes to the poster. https://forum.xda-developers.com/t/root-question-for-moto-g-stylus-xt2115-1-2021.4259413/

toxinburn said:
Well I cannot help with twrp but I was able to upgrade to android 11 and get root with magisk rather easily check this post all credit goes to the poster. https://forum.xda-developers.com/t/root-question-for-moto-g-stylus-xt2115-1-2021.4259413/
Click to expand...
Click to collapse
However if someone can get twrp working I got orange fox but meh not my fav i prefer touch twrp please let me know or if i can find it someplace ill post it worst case I just reflash stock recovery and try again.

I can help with this if it hasn't been fixed already ?? Just did twrp for XT2215-4 and XT2211-2

so is this stable? // who knows which ROMs are safe to flash to this xt2115 -1

Terrible this isn't working, you guys throw the stylus in the trash and get new devices?

What's the new member thing about. I've been on xda for 10 years

sosthenisRR said:
OTG adapter and mouse necessary
I am wondering if anyone can fix this recovery or possible port a new one with the files I have included. I am willing to test if you don't have a device to test on. My original post is here
Post in thread 'TWRP coming?'
TWRP coming?
Just saw the following article from XDA regarding TWRP v3.5 being released. I'm hopeful that this means that for devices that ship with Android 10 that TWRP will be able to decrypt the data partition in order to facilitate a complete backup...
forum.xda-developers.com
Here are the files and recovery backups.
Resolution is 1080x2400
Board is SM6150
Aarch64
Stock android 10
Please help anybody with the know how. Thanks. I'll buy anybody a pizza for doing this! Get it working right and I will definitely support.
External_sdcard says unknown filesystem but still functions to backup all partitions except /vendor, /system and /product individually. Allows /super backup.
/vendor and /system_root (permission denied)
touch screen not functioning in recovery
Flashing causes black screen after boot logo splash
I used AIK on windows 10 with notepad++
*EDIT*
added driver to /sbin in /ramdisk. updated recovery below.
Click to expand...
Click to collapse
I have the xt2115-1 and am curious to know what ever came of this. Was a working TWRP ever accomplished? I am trying to install a custom rom on my phone, but I can't seem to move past a permission denied issue in fastboot and can't seem to locate a working TWRP. Any suggestions?