yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] sachinu7f:
Hello!

I flashed the ROM

AospExtended-v9.0-beryllium-UNOFFICIAL-20211009-1953.zip

only with magisk 23.0 with Orangefox.

However when I booted to check the ROM was working with Magisk. But now I'm unable to boot into the Recovery again to flash it completely. The OrangeFox or TWRP just gets stuck on their logo screen. I tried to flash stock rom but either the tool gives me an error or just says success with 0 seconds time for flashing and not having done anything.

I tried to HotBoot to TWRP or OrangeFox but they also get stuck on the logo. Flashing either recovery does not help as it also gets stuck in the same place.

When left the phone at just the logo, after a while it boots to the system automatically.

I do not know what has to be done at this point. I am stuck with only rom and Magisk and nothing else. Unable to boot to recovery or anything. Please help! I really need help.

I would be very grateful for any help.
[General Questions and Answers] DiamondJohn:
Sorry, but I did not read every word, as you appear to be confusing the version of GApps you need to download and install. You talk about KitKat Gapps with possibly a more recent LOS build.

oFor clarity, the version fo GApps should match the ROM you are flashing, not the version of ROM your phone was released with or is runningbefore you update the OS. So if you flash a Nougat ROM onto a phone that has KitKat, then you need a Nougat GApps; not a KitKat Gapps.
[General Questions and Answers] sachinu7f:
Thank you for the help guys.

Got the issue resolved.

You first have to

1. flash the stock recovery

2. Do a complete wipe.

3. Boot to your custom recovery using PC and command ( fastboot boot <RecoveryName>.img )

4. Flash the proper recovery zip

5. reboot to recovery to check if it's working.

6. Flash proper rom
[General Questions and Answers] Duraze:
Hello XDA peeps.

I posted this question on the wrong XDA lineage forum and someone helpfully sent me here.

I recently received a Rhino T8 and am looking to flash lineage or similar onto it.

So far I've installed magisk (I'm not sure it's the right version of that to be honest) and haven't been able to get much further. Can't find a boot.bin or extract one (tried using payload_dumper_go) to use magisk to root and can't find correct twrp to change the recovery.

Is anyone able to help me?

Thanks 😊
[General Questions and Answers] Cheizasaur:
So I am downloading the package for the platform that Legacy uses? How do I find out which platform the phone is using, assuming I have to look through the phone info instead of Google?
[General Questions and Answers] SubwayChamp:
I guess you're saying you installed the Magisk app on your device, and you're trying to get the boot image to can patch it through it.

What format did you get from your OTA dumped? And which files -if you were able to open it- there are inside? Could you get a stock ROM for your device to get the boot image from it?
[General Questions and Answers] DiamondJohn:
Is it a custom ROM zip? If so, the name of the zip file will usually have a version number, from which you can look on the web to find which version of android it is, thus telling you which version of GApps you need. So you should not need to look through the phone or "Google", but you may need to read spomemore froma web search; which could be duckduckgo.

"Legacy" can mean many many things depending on its context, which I am not understanding from what you are typing.
[General Questions and Answers] Duraze:
I haven't been able to get the ota. I found a security file from their official site bit it's probably not right
[General Questions and Answers] SubwayChamp:
Ok, if there is no official ROM available then you should try with mtkclient it might work or not for your specific processor.

With it, you can pull the boot image, patch it and flash it back to your device, included the ability to unlock bootloader (mandatory before trying anything else).
[General Questions and Answers] xAxB:
I have read about anti-rollback protection here and I would like to know if this is something that generally applies to all phones / manufacturers using Oreo and later versions of Android.

I have my own reasons for wanting a phone that *comes* with an older version of Android (6 or 7) that can be subsequently be updated to a newer version of Android. A Pixel would fit the bill perfectly, but if I was to buy a second hand phone, there is a very high chance that it will come with Android 10 pre-installed.

Would there be any way to go down from Android 10 to 7 or will the anti-rollback protection make it impossible?

(I know it is a weird thing to ask, but anyway, I have my reasons)
[General Questions and Answers] Cheizasaur:
I had actually meant Lineage OS. I apologize for remembering wrong.

I appreciate the responses! You were very helpful. I wanted to find a way to identify the platform for future phone repairs other than a google search. For anyone who wants to find out the platform of their phone in the forum search (I'd like to contribute a bit if I can, I don't know who knows what) :

I actually found the answer to my question via app search. I looked for an app that functions like Speccy on the PC for android devices. Turns out there is one called CPU-Z that provides full specs of your device, including the Kernal architecture, for anyone else with similar questions. Which is apparently armv71. Strangely enough because DROID ULTRA is advertised as x86 Platform in a release article I found.
[General Questions and Answers] DiamondJohn:
To find technical details of your phones, a good spec list is normally available at www.gsmarena.com for many devices. It provides the model number, by region, which is very useful.

Also, if you are rooted or are flashing a custom ROM, there are many details regarding the platform of the ROM and hence pretty much your device, in your /system/build.prop file, which is also commonly found in the install ZIP file for your ROM.
[General Questions and Answers] xAxB:
I would like to ask two questions:

1. Can you upgrade more than one major versions in one go? For example, going from Android 7 straight to Android 9?

2. Am I less likely to run into problems if update in one go, or step by step (e.g. Android 7 to Android 8, to Android 9)?
[General Questions and Answers] SubwayChamp:
It depends on the ROM and OEM you want to update, some custom 9 ROM needs Oreo as based, so you wouldn't in this case, and in some OEMs like i.e. Samsung you can't jump more than a specific number of updates being in some specific build number.
[General Questions and Answers] xAxB:
I have one more nooby question.

I would like to remove encryption on a Pixel XL using Universal DM-Verity, ForceEncrypt, Disk Quota Disabler:

- As I understand, step one format the device via TWRP to remove all encryption.

- Step 2 is to reboot back in recovery

- Step 3 is to flash the ROM. And this is where I have a question. Are there any TWRP flashable ROM for Pixel XL?

- If there isn't, then what are my options? When I flash the factory ROM using flash-all.bat it restarts the device thereby encrypting it and if I am not mistaken, TWRP also get removed?

- So I need a way to install the stock ROM and Universal DM-Verity, ForceEncrypt, Disk Quota Disabler without the first booting into the system (and thereby enabling encryption).
[General Questions and Answers] tchl:
In a bit of a pickle...

Found a Coolpad Legacy SR, model cp3648AT. I cannot find firmware for this device, anywhere. I tried flashing AOSP 10.0 v201 but was met with a Invalid spars file format at header. I then downloaded TalAloni/SparseConverter but I can't get it to function. Every guide that I have found for Sparse Converter says to execute using SparseConverter.exe but I don't even see the file in the zip folder that I extracted.

Any guidance is appreciated. Bootloader is unlocked and the end goal is too root the phone.
[General Questions and Answers] Droidriven:
Your Windows Defender/firewall or antivirus may have blocked the converter.exe when you extracted the downloaded file. Try turning off Windows Defender and firewall and disable your antivirus then extract your file again and see if you can find the .exe file. Turn Defender/firewall and antivirus back on after you extract the file.

Make sure that what you are trying to flash is specifically for the Coolpad Legacy SR and not for the other Coolpad Legacy models. Coolpad Legacy and Coolpad Legacy S are not the same as Coolpad Legacy SR.

The GSI ROM that you are trying to use may be compatible with another Coolpad Legacy variant but may not be compatible with the Coolpad Legacy SR that you have.
[General Questions and Answers] tchl:
Nailed it! Thanks for that tip.

I just ran the converter command and all I got back was this message...

C:\android\platform-tools>SparseConverter.exe /compress/C:\android\platform-tools\system-quack-arm64-aonly-vanilla.img C:/256MB

SparseConverter v1.0.1.0

Author: Tal Aloni (tal.aloni.il@gmail.com)

About:

This software is designed to create / decompress compressed ext4 file system

sparse image format, which is defined by AOSP.

Usage:

SparseConverter /compress <image-path> <output-folder> <max-sparse-size>

SparseConverter /decompress <first-sparse-path> <output-image-path>

SparseConverter /stats <sparse-path>

What am I doing wrong?

re-checked my typing

:)
[General Questions and Answers] SubwayChamp:
There are some ROMs here https://xdaforums.com/c/google-pixel-xl.5916/ that could bring you natively or at least you can disable the verity over them.

On a stock ROM you can't do it, so flashing back a stock ROM all returns to the original state.
[General Questions and Answers] SubwayChamp:
What do you want to gain with that? Is it the firmware from other model? Do you want to flash a GSI?
[General Questions and Answers] tchl:
Before I go any further, how do I find an appropriate firmware to flash on this device?
[General Questions and Answers] tchl:
Supposed to be a generic ROM that can work on this device. End goal is to root the phone.
[General Questions and Answers] marina1511:
Hello, I'm trying to be a new user, and not a noob!

I'm looking for an advice here as the forum of my device is pretty much dead. I checked the forums of the similar devices, but that's what got me into trouble, I thought my device would be okay with LineageOS as similar devices have their LineageOS ROMs, but apparently not.

I managed to softbrick my Oneplus Nord CE 5G. I tried to root it with magisk - I patched the LineageOS boot.img intended for other Nord, and flashed that patched boot.img. On reboot I get qualcomm crashdump.

I can boot to fastboot so I tried to boot all boot.images from post containing official OxygenOS for my device ( https://xdaforums.com/t/oneplus-nor...epo-of-oxygen-os-builds.4326661/post-85557697 ) but none did the trick, I'm always stuck at watching the OOS circles loading screen and then black screen, which when I use power button asks do i want to lockdown, reboot or power off.

I'm not sure what version of os I had. I tried to find the other versions of boot.img i can flash, but there's no full oos files on oneplus page (I tried DE, UK, HR, AT sites as I have EU version as in https://www.oneplus.com/de/support/softwareupgrade and nord ce 5g is nowhere listed so I can't get other versions of os).

I'm a bit scared of flashing all other oos image files as I'm a noob new user, and I'm scared of hardbrick since atleast atm I can go to fastboot and try to fix it. I'm not managing to boot into EDL mode so that would be my last resort. Fastboot enhance tool doesn't work for me, I can't go into fastbootd. I tried atleast 5 different platform tools so idk what's the problem there.

Anyways, my questions are...

1) Should I try to find correct boot.img or should I just use any full os I downloaded from that post containing OxygenOS zip and flash all that's inside? I asked in the forums: "Is there anyone who's in Europe and bought the phone lately and can upload his boot.img somewhere for me to try to use it?" My question for you here : Could that do the trick? Maybe I should just request the same thing from Oneplus since they didn't post the official oos on their site for my device as seen in upper onepluscom link?

2) Is flashing boot, system, vendor and recovery from the zip enough? I can't find flash-all.bat for this phone so I'm not sure if I'm missing anything. I looked at flash-all.bat for some other Oneplus device and it flashes images i don't see in extracted OOS for my device, and there are some more .imgs in my OOS not listed in that bat, so what gives? I only flashed (incorrect) boot.img, nothing else so I have a hunch correct boot.img would be enough. Am I correct about this?

TLDR: I'm softbricked. Which images to flash from unpacked OxygenOS if I can only fastboot and I only flashed incorrect boot.img? I tried several and none booted the os. Can some European who bought the Nord CE 5g lately and didn't update the os upload his boot.img somewhere for me to try it out? Any guidance would be greatly appreciated

Thanks for your help.
[General Questions and Answers] SubwayChamp:
First, you need a device that allows to have bootloader unlocked.

A GSI doesn't need to convert or sparse the image or anything like I suppose you are trying to.
[General Questions and Answers] tchl:
I unlocked the bootloader.
[General Questions and Answers] tchl:
I looked up the device info and it says ARM64 A only Vanilla and so that's what I downloaded but when I attempt to flash it I get the Sparse header error message as mentioned above.
[General Questions and Answers] SubwayChamp:
Which method you are using? And What version is it? Did you check your device has a system or a super partition? I guess this is a MediaTek device?
[General Questions and Answers] tchl:
Trying to flash with fastboot. How do I look up the partition information? i'm using an app called CPU X.
[General Questions and Answers] tchl:
It's an A only system partition.
[General Questions and Answers] SubwayChamp:
To know which partition you have use an app like this https://play.google.com/store/apps/details?id=me.kuder.diskinfo&hl=en&gl=US check if you have system or super partition instead.

And check if you have a MediaTek or Qualcomm (I doubt it).

Android Version?
[General Questions and Answers] tchl:
I'm guessing Media Tek because the chipset says MT676V/CABView attachment 5461505

Does this help at all? :/
[General Questions and Answers] SubwayChamp:
Your device is MediaTek 6761.

The last "sparse error" you had, last there?, and never got it flash it? Did you target to the system partition? For that it is important to know if you even have system partition as I said you previously have to check it with that app.

You also could try to load the image through the DSU feature in Developer option if you're in Android 10.
[General Questions and Answers] tchl:
So, I flashed with this command...

C:\android\platform-tools>SparseConverter /compress C:\android\platform-tools\system-quack-arm64-aonly-vanilla.img C:\android 512MB

response was this....

Image size is not a multiple of 4096 bytes

So it looks like I'm on the right track? How do I calculate the image size?
[General Questions and Answers] Droidriven:
You were supposed to patch the boot.mg from your stock firmware, not the LineageOS boot.img.

The simple answer to help you find what you need is to do a Google search for:

"Return to stock (your specific model number)"

That should find the necessary software, firmware file, tools and instructions to restore your device to stock standard.

You could also do a search for:

"How to unbrick (your specific model number)"

Once you have the device restored, then you need to make sure the bootloader is unlocked. Then use Magisk to patch the boot.img from your stock firmware file, then flash the patched boot.img that Magisk produces. When you boot into the new system that you just flashed, install the Magisk Manager app to gain control of your root functions, modules and management features.
[General Questions and Answers] SubwayChamp:
You are not saying which command you used and which partition you targeted, so I only have to guess, in case this is what you're trying to use https://xdaforums.com/t/tool-sparseconverter-v1-0-1.2749797/ you don't need it.

You have to identify which partition and which Android version you have, in order to know how to flash a GSI.
[General Questions and Answers] tchl:
Okay, still working on identifying the partition breakdown. Will fastboot getvar all show me what I need? I can't find the partition information on any apps. Most seem to need root permissions.
[General Questions and Answers] zapsi92:
hello, will there be any update for the radio to android 10:

mcu version, T3L.3.19-296-10-A49311-210105(MM030),

system version V.8.1.1_20210430.162039_THEME1l

Android version 9
[General Questions and Answers] Orion_6:
What exactly is the difference between pixel experience plus and pixel plus UI bcz when i was searching for extended, PE+ and PE there was only a few vid on extended and it was implied that extended is pixel plus UI, is it true?
[General Questions and Answers] marina1511:
Thank you for your help and guidance with search strings. Yes, now I see my mistake with patching the wrong boot.img.

In the meantime I managed to get to fastbootd mode (with ./fastboot.exe reboot fastboot - it seems my environmental variable had some older platform-tools in a path, but changing PATH variable didn't help so I just use ./fastboot.exe instead of fastboot in folder of newest platform-tools). So that meant I could proceed with flashing the rom since part of it needs to be done in fastbootd.

I found few different scripts/instructions for flashing the stock rom, and i flashed all the files from the stock with rebooting to fastbootd when instructed. Now I don't have qualcomm crashdump error anymore, but the phone is stuck on loading the OxygenOS (the spinning circles animation just keeps spinning for minutes). I tried to wipe data, cache and system settings through recovery but still stuck on endless booting of the os.

Should I try some other version of stock rom, or does anyone have some other advice for me what should I try next? Could it be that I had older android (10) and flashing the 11 is making it stuck? Any help would be greatly appreciated!

EDIT: everything resolved after wiping user data (pics,music,etc) - third option in recovery! Wiping data, cache and system settings didn't help. Will make a post about it in nord ce forum. Thanks for your help once again
[General Questions and Answers] SubwayChamp:
Yes, also there are other ways to know which partitions you have: adb shell ls /dev/block/by-name, (following the path may help).

Anyway If you are decided to flash a GSI on your device, first be sure that you have some backup or a firmware available to restore things, second; you should need to flash at least/like minimum a system image and a vbmeta that can bypass the verification integrity so do the next:

Download an A/B GSI image (recommendable), target it to your system partition (this way you know if you have it) with fastboot flash system nameofyourimage.img if it returns something like "system partition doesnt exist" then you should have to do it in other ways, then follow with the vbmeta using fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
[General Questions and Answers] tchl:
I ran fastboot getvar all. Which partition am I looking for?

Also, thanks for answering all of my questions. I find this stuff fascinating and trying to learn. I bought a box of old phones from someone on Craig's List for $25 so I'm not that worried if I screw this phone up. More interested in getting it rooted.
[General Questions and Answers] tchl:
View attachment 5462335
[General Questions and Answers] SubwayChamp:
Then go straight to the fastboot command, the goal is to know if you have a system partition, this way you can flash directly a GSI on your system partition.
[General Questions and Answers] tchl:
View attachment 5462339View attachment 5462341

What am I looking for?
[General Questions and Answers] SubwayChamp:
Read above.

If your last (or solely) goal is to root it, you also have to read about this amazing tool https://github.com/bkerler/mtkclient with it, you should pull your boot image, then patch through Magisk and then flash it back using fastboot.
[General Questions and Answers] tchl:
I'll check that out.

I received this error message when trying to flash the system file...

C:\android\platform-tools>fastboot flash system C:\android\platform-tools\system-arm64-ab.img

Sending sparse 'system' 1/10 (131068 KB) OKAY [ 3.450s]

Writing sparse 'system' 1/10 FAILED (remote: unknown command)

Finished. Total time: 5.681s
[General Questions and Answers] SubwayChamp:
Be sure that USB debugging and OEM unlock options remain enabled on every reboot and also use the latest SDK platform https://developer.android.com/studio/releases/platform-tools#downloads
[General Questions and Answers] tchl:
OEM unlock is in the already unlocked position. USB debugging is enabled and still getting that command error. Stuck as to what to try next.
[General Questions and Answers] Droidriven:
Put the file in your fastboot folder, then your command should be:

fastboot flash system system-arm64-ab.img

If your file is placed in your fastboot folder, you won't have to use a path in the command, you only have to input the na.e of the file in your command instead of a path to a location, it will flash from fastboot folder by default if no path name is included in the command.

As a side note, the file name you posted this time is ab.img but weren't you previously trying to use a file that is aonly.img?
[General Questions and Answers] tchl:
Yes, someone suggested I use the A/B earlier in this thread.
[General Questions and Answers] tchl:
Received the same error message.

C:\android\platform-tools\fastboot>fastboot flash system C:\android\platform-tools\fastboot\system-arm64-ab.img

Sending sparse 'system' 1/10 (131068 KB) OKAY [ 3.391s]

Writing sparse 'system' 1/10 FAILED (remote: unknown command)

Finished. Total time: 6.642s
[General Questions and Answers] tchl:
For the life of me, I cannot figure out which partition system this phone uses. When I run an app called CPU X it says; Instruction set arm64-v8a armeabi-v7a armeabi
[General Questions and Answers] SubwayChamp:
This doesn't make reference to the partition structure, but to the architecture type your device is.

As your getvar all command did throw, it seems your device has system partition, but something is wrong with your fastboot binaries, or I'm doubting you are entering to fastboot or bootloader mode;

How did you send your device to?

Android version?

What about the SDK platform version, is the latest?
[General Questions and Answers] tchl:
I'm using platform tools and the SDK is the latest. I flashed a Pixel 3a without any issues. This crazy phone doesn't seem to have any firmware on the internet and has been a pain.

The device is in fastboot mode with a gray Android character icon. The device drivers are up to date and the fastboot devices command shows the device. Other commands work as well but when I go to flash I get error messages.
[General Questions and Answers] tchl:
View attachment 5462711
[General Questions and Answers] SubwayChamp:
(Crazy=Unpredictable) Try with fastboot reboot fastboot or fastboot reboot-fastboot in case you are in Android 10.

I asked that, cause there is a difference if you sent it to fastboot (new user space) or bootloader mode.

You can back up all the partitions with the tool that I linked, to have a backup of the firmware, as I mentioned previously.

And again, what about the DSU option in developer section?
[General Questions and Answers] tchl:
Sorry, missed that. It’s Android 9. I’ll check the developer section for DSU first thing in the morning at my office.

I appreciate you being patient and walking me through this.