yashsingh1/xdaforums huggingface dataset:
[Google Pixel 4a 5G ROMs, Kernels, Recoveries, & Ot] Schmye Bubbula:
Maybe this is something peculiar to this unofficial TWRP build, after all. (If not, after the following, just say so and I will cheerfully delete some of my preceding posts, for I am cognizant of the bad netiquette of crapping-up this thread with off-topic issues.)

I found my way to a workaround:

While TWRP was running on the USB-cable-connected target phone ("fastboot boot..." from Bugjaeger, not actually flashed as the phone's custom recovery — does it matter?), I entered into Bugjaeger's ADB shell :

push [path to my zip file on source phone] sdcard/

...and it appeared in my TWRP sdcard/

But my Install Zip went bad:

E:unable to find apex_payload.img in zip

Updating partition details...

...done

Unable to mount storage

Full SeLinux is present.

Unable to mount /data/media/TWRP/.twrps

Unable to mount /data/media/TWRP/.twrps

Installing zip file 'sdcard/Magisk_Delta.zip'

[ran installation script of Magisk Delta (Systemless Mode) by HuskyDG]

Updated process ended with ERROR: 2

Error installing zip file '/sdcard/Magisk_Delta.zip'

Updating partition details...

...done

Unable to mount storage

E:Error creating fstab

So what makes me think that this might have to do with this particular TWRP build is that it seems not to be able to mount storage. I could understand that if it were encrypted, but I was set to Swipe lockscreen, so it wouldn't be encrypted, right?

Also, the XDA thread I linked in my earlier reply suggested some things I also tried, such as checking System to mount (is that supposed to happen without further ado?; I got no feedback), or setting a phone password and letting TWRP try accepting it (it didn't), then go back to Swipe and try TWRP again — even several times in succession — to force something to get reconstructed that TWRP could then handle, but, alas, it was to no avail — storage was still listed as zero and things evidently still aren't getting mounted. Would this be a problem with this TWRP build, or am I just on my own at this point?
[Google Pixel 4a 5G ROMs, Kernels, Recoveries, & Ot] Yeedatoy:
The odd part is that as long as you install it on Android 12 and keep it installed, meaning when you update....make sure to reflash it so it doesn't get overridden by whatever ROMs recovery is being flashed....it continues to work even into Android 14. Sure it has some issues but they're all things that just take a little bit of tinkering to work around. However, as soon as you boot into the system without TWRP installed, there's no getting it back into a working state in a13 and newer.

Ps: Bugjagger is an incredible app. I install it on every device and never use a PC to flash anything unless Im forced to do so in fastbootd
[Google Pixel 4a 5G ROMs, Kernels, Recoveries, & Ot] Nazo:
There has been no update from TWRP in well over a year. It used to update every few months or so. My distinct impression is that TWRP is more or less officially dead for whatever reason. It sucks beyond words to see it go, but I think we have to let it go. I just wish there was something at least close to its capabilities, but for now I think we have to put up with the LineageOS recovery as probably the only thing fully capable of handling (almost) everything. Hopefully TWRP gets properly revived someday. Fingers crossed. I miss the ability to backup partitions and that sort of thing. I don't feel like it's worth sticking to a legacy system that's falling farther and farther behind. I've seen TWRP fail to support changes needed by OS installers many times in the past when not updated, so I'm betting that will happen again sooner if not later now that it's basically dead.

As for the booting thing, my bet here is that there is some major change to the bootup process (perhaps for better checking of signatures and stuff?) and it's using a legacy boot method until it sees it doesn't have to. It's usually a bad idea to do an "upgrade" install over a major version -- eg 12 to 13 or 13 to 14 -- so I'm not really sure it's worth it. It's pretty much the official advice from every single OS build. I've never had system breaking bugs from such a thing per se, but I can say that the rare few times I did an upgrade install of a major version it tended to run really badly with more sluggishness and worse battery life. It makes sense really. The old system leaves behind a lot of incompatible things I'm sure. I'm sure the installer tries to remove many but likely can't get all.

As for Magisk, the most sure-fire way to install it is to take the boot partition image (no need to extract it if you're using official LineageOS builds as it's separate on the downloads page) and patch it with the Magisk app, then flash that in fastboot. It won't matter whether you use TWRP or whatever in that regard, so if you're getting errors in TWRP you can basically just avoid the problem entirely by doing that anyway. Normally this is what TWRP does -- just automating the process for you more -- so I'm not really even sure what's going on with that error since it shouldn't even be using those. Since fastboot is from the device, it's independent of TWRP or the LineageOS recovery software and will work regardless of which you use. Just grab the boot image from the downloads page or extract from an installer image, patch with Magisk, download the patch to your PC (or other device if you use fastboot on something else,) reboot to fastboot, and flash the current boot partition.
[Google Pixel 4a 5G ROMs, Kernels, Recoveries, & Ot] hammered58:
Just a couple other options that have worked for me

1. If your rooting stock,, pixel flasher is pretty good alternative, slight learning curve but once learned it is a good tool.

2 if rooting custom ROM ,,by using the roms recovery you can sideload the magisk zip file

But as stated sure fire way is patched bootloader,, hth
[Google Pixel 4a 5G ROMs, Kernels, Recoveries, & Ot] Yeedatoy:
Side loading magisk is depreciated as it doesn't install correctly, making a reboot necessary and then refreshing again through the magisk app. The official way for pixels is click install, patch image, than click the entire ROM.zip and magisk will pull the correct image from payload and patch it. Than flash via fastboot. On many recoveries side loading still works but it's just a 3 step process instead of 1. Regarding TWRP, the release for the pixel 5 still works up to a13 and on the Pixel 3 as well which also uses the titan chip. The 4a5g branch just needs to be cloned from the pixel 5 branch and have some lines edited which I've slowly been doing....very slowly. Like I mentioned though, Joshua's latest release still works as long as you install it on a12 and than keep in installed as you update to 14, just remove your lock pin before rebooting into it
[Google Pixel 4a 5G ROMs, Kernels, Recoveries, & Ot] Schmye Bubbula:
Yeah, but I've never been able to solve the problem of Storage and Internal Storage as zero bytes.... I've googled around until I'm blue in the face, and it's not just a Pixel 4a (5G) problem — a lot of others face it — and it has to do with getting it to decrypt my phone, but I don't have any kind of lock, so how is it encrypted?, and I'm bewildered!
[Google Pixel 4a 5G ROMs, Kernels, Recoveries, & Ot] Nazo:
It's a basic security feature with modern Android versions where setting a password encrypts things. In many it encrypts the whole user partition. I think in the latest (13 and 14) it just encrypts databases or something. The only way to clear it is to remove the password, which of course means less security.

I've had one device where TWRP was able to ask for the password and decrypt the LineageOS encryption if I entered it correctly, but that may have been specific to that one specific TWRP+LineageOS build. Or maybe just they can't do it anymore. Or maybe it's just prohibitively hard to implement and most don't bother. Not sure. Either way I think you have to count on TWRP not being able to directly handle user partitions anymore in any forseeable future. Especially since there don't seem to be any official TWRP builds anymore.

I still say it's simplest just to grab the boot.img and patch that directly as opposed to patching an entire update file. The basic LineageOS image is 1GB large and that's almost as minimal as it gets (at least without specialist builds.) I think the stock system was closer to 1.5GB. If you're using LineageOS, the download page includes the boot.img as a separate file, so all you have to do is save that too. As you say though, it's depretiated and may stop working entirely, so it's probably a bad idea to rely on sideloading as it may start breaking things in the future.

I really do wish they would make some method for us to actually do the patch without having to run Magisk ON an Android device first though. There should be a PC program to do it or something. Or bring back sideloading as a thing. Actually, what would be cool is if they'd make a Python script or whatever that would take an input image, patch it, and then flash the patched boot ROM straight from your PC as one step.
[Google Pixel 4a 5G ROMs, Kernels, Recoveries, & Ot] Schmye Bubbula:
But I said that I don't have any kind of lock — meaning no password, just swipe (so how is it encrypted?) — and I still get the Storage and Internal Storage as zero bytes. I don't get it!

memo: I was doing only a:

fastboot boot [path to twrp-3.6.0_11-0.1-bramble.img]

...because V0latyle says that TWRP is only meant to be used on a temporary "live" basis on devices such as Pixel, because TWRP cannot be permanently installed on A/B devices like Pixels which do not have a recovery partition, so how are you guys doing it?
[Google Pixel 4a 5G ROMs, Kernels, Recoveries, & Ot] Nazo:
Well, partially I misread about the lock, but also, as I said, Android 13 and 14 do it a little bit differently. I'm just guessing, but it probably has a basic system-level encryption using a standard key or something in addition to the separate user level thing. That or TWRP just doesn't recognize the layout in the latest versions if they made some changes or something. (Maybe the filesystem has changed or something? Not sure.)

Bramble has a recovery. It uses vendor_boot instead so it will have an a/b recovery too. If you flash vendor_boot it flashes the currently selected one, but you can manually specify vendor_boot_a or vendor_boot_b if needed. I think this is so that when a recovery changes significantly (which may happen across major version changes such as 12 to 13) it can have a current one for the new system yet still have the old one if you have to boot back to the old one for maximum compatibility. When you start it up with the button combination it boots the currently selected vendor_boot.
[Google Pixel 4a 5G ROMs, Kernels, Recoveries, & Ot] Schmye Bubbula:
So just to make sure I grok — because I'm a noob and don't really know what I'm doing — my syntax would be?:

fastboot flash vendor_boot [path to twrp-3.6.0_11-0.1-bramble.img]

...Oh yeah, and by the way, when I recently bought my Pixel 4a (5G), it came with Android 14 on it (grrr!); does that mean I'm crap out of luck in the first place?
[Google Pixel 4a 5G ROMs, Kernels, Recoveries, & Ot] Nazo:
Yes. For reference, here are the official LineageOS instructions: https://wiki.lineageos.org/devices/bramble/install/#installing-a-custom-recovery-using-fastboot

Assuming it's still compatible enough to boot as a recovery, that is how you would do it.

EDIT: Misunderstood the question. First, to be clear, we're not talking about locked devices. If you can fastboot boot TWRP that already means the device is unlocked. What they were talking about was using the old patched boot image. If you have Android 12 you can use the old image if you install 14 and flash back the old image before it ever boots up. Probably this means it's forced to keep system encryption in a more backwards compatible level. Since it came with 14 you would have to downgrade and go through the process manually to re-upgrade. Bear in mind an upgrade rather than clean install can often come with worse performance and etc (and if it's forcing backwards compatibility stuff it's likely going to be even worse still.)
[Google Pixel 4a 5G ROMs, Kernels, Recoveries, & Ot] Schmye Bubbula:
I'm sorry if I'm being daft, but you're not saying that:

fastboot flash vendor_boot [path to twrp-3.6.0_11-0.1-bramble.img]

...is only for LineageOS, are you? I'm on stock Android 14.

(And I'm not forgetting earlier posts about probably having to flash recovery to earlier versions, then upgrade to current OS while making sure not to lose recovery, so in that case, you wouldn't have meant that vendor_boot is only good for earlier LineageOS's, did you?)
[Google Pixel 4a 5G ROMs, Kernels, Recoveries, & Ot] Nazo:
No, I'm saying that the wiki has convenient instructions that are handy to link to.

No.
[Google Pixel 4a 5G ROMs, Kernels, Recoveries, & Ot] mabra666:
need help with fastboot
[Windows 11] jenneh:
==============================================================

HOW TO MAKE A MODIFIED WINDOWS ISO

==============================================================​

Spoiler content hidden.

Mod Edit: Link to Tool removed.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

Spoiler content hidden.

This ISO will work just fine In virtual machines. However..

To install direct to disk you need to use usb method:

Spoiler content hidden.

<333333

This guide will teach you how to do this without MSMG:

Spoiler content hidden.
[Windows 11] jenneh:
My modded version of Windows 10, Lazily titled "JROM-Win10" has been uploaded to the cloud, and added to the thread. The ISO is 4.24 GB in size.

I am modifying Windows 11 now, running JROM on my Host PC as well as a Virtual Machine, and will do a video once I get my modded Windows 11 posting in VBOX and properly write out what all was removed and left in~!

This includes my toolset to root anything android, called "Phonetoolz" Which is a series of batch files to easily root most anything android that you have the bootloader unlocked on, but that will be explained later...
[Windows 11] jenneh:
JROM - Win 11 Iso link has been added to the thread. It is 4gb in file size. I am working on my "Rooted" version of the Win 11 iso, which will have WSA and more included on the ISO. When that is completed I will put all these iso's on their own thread and place that link here. Lol.

These ISO's were made for Virtual Machines, but will work with Rufus USB method too

TPM Requirements are off~!

Also, I took my Virtual Machine thread down Temporarily, when my root copy is complete I will post a VM image on that thread...

THESE ISOS ARE UNACTIVATED~!

This is intentional!

Good Day Sirs~!
[Windows 11] jenneh:
Windows 7 is slightly different~!

Here's the command \ steps for anyone interested.

Copy the Window's 7 ISO Contents to the DVD Folder,

Run the start command in the MSMGTK12 folder.

Select option 1 and then pick out the version of windows 7 you want to install.

Proceed as normal

"

Main Differences Between Windows 7 Professional and Ultimate

The Ultimate Edition can boot files directly from VHD without host interference while this is not possible in Professional."

INTERESTING~! LETS EXPERIMENT WITH THAT

Working on some things for y'all <3
[Windows 11] Almas001:
My modded variant of Windows 10, Lazily named "JROM-Win10" has been transferred to the cloud, and added to the string. The ISO is 4.24 GB in size.

I'm adjusting Windows 11 presently, codeprozone running JROM on my Host PC as well as a Virtual Machine, and will do a video once I get my modded Windows 11 posting in VBOX and appropriately work out what everything was eliminated and left in~!

This incorporates my toolset to root anything android, called "Phonetoolz" Which is a progression of cluster records to effortlessly root most anything android that you have the bootloader opened on, yet that will be clarified later...
[Windows 11] jenneh:
This is a little strange, haha. Rewording, that which I already wrote.

I like your style.

I do see you guys' interest in how the phonetoolz work, my only limitation right now, is the fact that, A. The fastboot drivers continue to break in windows 10.

I want to find out why, but the thought lingers, that these tools, adb, etc, have existed for years without ANY trouble on windows 7, as my toolkit comes from batch files that I made 6 years ago....

I tried to simply install windows 7 on my machine and it was rejected due to "nvme drivers missing" and I was like, what the heck is that>? found out modern systems with ssd only cannot natively run the iso.

Learned about DISM and DISKPART. Figured DISM to edit and inject the tools into the iso could potentially rectify this, but I am failing due to our friend "TIM" TrustedInstall manager....

I realize that everything would work as is right now, but I want to complicate it in a way that teaches myself, and others, bc there's like an infinite way you can do things in computing today, with all the Languages our Puters know...

I got off track, but my other limitation is my USB on my RAZER PHONE 2 went bunk :< I do not have another android phone to show these on yet. Maybe I can find a cheap burner to teach on~!

Long story short, lemme correct these complications and we absolutely will go over these batch files~!

I am trying to build a tiny windows 7 virtual machine with the drivers preinstalled correctly so you could in theory run a script and boom we have root... and windows 7 A for compatibility of ADB and FASTBOOT but B for the filesize of the entire system... you can get that crap down to 1.2 gb zipped...

AN ENTIRE OPERATING SYSTEM, PREINSTALLED, ZIPPED FOR 1.2 GB....

CASE AND POINT

Google Drive - Virus scan warning

drive.google.com

This was made using Experiences' Modded windows 7 called "Tiny 7"

It kinda still works to this day!@

This is evidence that virtual machines can preserve history~!

Let's also not forget the fact that Windows 7 could run 21 Virtual Androids at once.

Not as expected, but the music they made was.... One Of A Kind~!

Skip to 2:47 in the video to hear them Sing~!

Also I just ask that people give me time.

I'm just an ordinary girl and I work at an ordinary place. It makes me tired.

So I try my best to make good use of my few hours off before bed haha.
[Windows 11] erktheerk:
Just a heads up to users still learning, who rely on scripts and tools to learn the process of building your own environment/lab/station. We all start somewhere not knowing what to do next, or which direction to go. especially when it comes to the line between experimenting in isolation and using unknown tools that then are allowed to coexist with your production ready, day to day, IRL devices/servers/network. There is a reason the term edge is used when discussing the line between private and public networks.

Malicious/suspicious code should be treated like like what it is: a novel virus. Untrustworthy, suspect, potentially deadly, and not something you're going to expose your loved ones too if for little else than to save you time, money, effort, and stress when you inevitably have to go into triage mode. Zero wipe your entire setup down to the firmware and driver headers on every machine in your network; muttering to yourself at 2 in the morning, cursing how much there is left to do after you're finished tearing it all down, hoping that it wont show up again like last time 2 times you missed a spot.

Code doesn't care about your intentions, good or bad, innocent or nefarious. It's not concerned about who, why, if it's good or bad, if it's helpful, funny, or destructive. It just is, and it does what it was told to do by someone you'll never know. Zerotrust is the new term, I still prefer paranoid. Everyone else should embrace that as well, especially before running something that has 9 separate flags in a 31MB file on a forum. Even when the poster shows no other signs of mal-intent.

Never forget, it's not a fairytale.

This is the internet, and there be dragons.

MSMGTK12.zip:

VirusTotal

VirusTotal

www.virustotal.com

View attachment 5601613
[Windows 11] Er. Aditya:
hi thanks buddy but i am facing this error over and over again
[Windows 11] erktheerk:
Based on that, Something is trying to use logic(boolion) code where it's not allowed. Whatever flipit grid is (maybe tiles for start menu?). Windows is throwing the error because it was blocked from doing it's thing and whatever it is wasn't programed to recover from the halt in code at that point. Seeing as how windows covers those types of expectations, I stand by my earlier post and say anyone downloading this person's files should know what they are doing. It threw many flags on virus total. Regardless of their intentions OP should not be trusted. Guess I'll hit the report button since they obviously won't pull the content themselves.
[Windows 11] Er. Aditya:
thanks buddy il be aware
[Windows 11] TNSMANI:
MOD ACTION:

Thread closed temporarily.

@jenneh

Please check your PM inbox.
[G1 General] kolobok01:
Hi guys I'm truing to download apps from web via Android browser. but wan i click on any file zip or apk it's giving me an massage that

"Cannot download. The content being downloaded is not supported on the phone."

How can i make it download file?
[G1 General] Mikey:
Would you mind tell us the extension of the file you are trying to download?
[G1 General] kolobok01:
I did .zip and .apk
[Samsung Galaxy S9+ Questions & Answers] handy77:
S9 plus randomly shuts down. I am rooted anyway to reset and keep rooted. Only recently my phone started playing up
[Realme X2 Questions & Answers] MrZZZ123:
关于MSMDOWNLOADTOOL_FOR_REALME说明

1、目前工具已经能通过nginx代理跳过登陆验证，可以直接进入刷机界面，但是在签名验证那里会出问题

2、通过fd截取请求，我已经知道它需要的参数以及返回的字段，但尚不清楚需要返回什么样的数据

3、工具可以随意选择ofp进行刷入，但只支持高通设备的ofp

希望能有大佬一起来帮我研究一下这东西，可私聊我

About msmdownloadtool_ FOR_ Realme description

1. At present, the tool can skip login verification through nginx agent and directly enter the brush interface, but there will be problems in signature verification

2. By intercepting the request through FD, I already know the parameters it needs and the fields it returns, but I don't know what data it needs to return

3. The tool can select OFP to brush in at will, but it only supports the OFP of Qualcomm devices

I hope some big guys can help me study this thing, but talk about me privately

下载链接

链接：https://pan.baidu.com/s/1UfAbpqj8v_CyWvc9vOOvEA

提取码：cxyf

--来自百度网盘超级会员V1的分享

View attachment 5507987

View attachment 5507989
[Realme X2 Questions & Answers] MrZZZ123:
手机：realme x2，rmx1991，8+128，realmeui1.0，730g

问题：无imei，无法重新上锁与解锁，无法使用指纹，无法进fastboot

缘由：偷，渡realme ui2.0失败，寄，修过去所产生，找过当地售后当面线刷，也没法解决，初步推测是ofp问题

发生时间：2021年3月-2021年4月

Mobile phone: realm X2, rmx1991, 8 + 128, realmeui1 0，730g

Problem: no IMEI, unable to re lock and unlock, unable to use fingerprint, unable to enter FastBoot

Reason: upgrade realm ui2 0 failed. It was sent and repaired in the past. I found a local after-sales face-to-face brush and couldn't solve it. It is preliminarily speculated that it is an OFP problem

Occurrence time: March 2021 - April 2021
[Realme X2 Questions & Answers] MrZZZ123:
msmtool: MsmDownloadTool.2.0.51_rcsm

系统：Windows10 1909

ofp版本：RMX1991_11_A.09_190920_f9fe8ec3.ofp

是否需要权限运行： 是

msmtool: MsmDownloadTool. 2.0.51_ rcsm

System: windows10 1909

OFP version: rmx1991_ 11_ A.09_ 190920_ f9fe8ec3. ofp

Need permission to run: Yes
[Realme X2 Questions & Answers] MrZZZ123:
楼上是工具，里面有内容，我就不加密了，你们自己研究一下，自己型号的线刷包自己去外网找，我也就不提供了，链接：1UfAbpqj8v_CyWvc9vOOvEA

提取码：cxyf

--来自百度网盘超级会员V1的分享

Upstairs is a tool. I won't encrypt it if there is content in it. Study it yourself. Go to the Internet for your own model of wire brush bag, and I won't provide it. Link: https://pan.baidu.com/s/1UfAbpqj8v_CyWvc9vOOvEA

Extraction code: cxyf

--Share from Baidu online disk super member v1
[Realme X2 Questions & Answers] nian678:
无意中看到的：

OPPO MsmDownloadTool Cracked_哔哩哔哩_bilibili

OPPO MsmDownloadTool Cracked, 视频播放量 12125、弹幕量 0、点赞数 62、投硬币枚数 33、收藏人数 63、转发人数 37, 视频作者 mlgmxyysd, 作者简介 一！只！喵！｜可能会炸毛｜KaleidoscopeOS 创意设计总监｜MeowCat...

m.bilibili.com
[Realme X2 Questions & Answers] MrZZZ123:
这个视频作者都不发工具出来，一直装死。
[Realme X2 Questions & Answers] mlgmxyysd:
有没有可能，oddo不让我发:rolleyes: