yashsingh1/xdaforums huggingface dataset:
[Miscellaneous Android Development] mrmazak:
I was able to add superuser apk, and the app opens. I also added the su binary files to xbin. And an init file to /ect. Problem with it, seemed to be not having selinix permissions to exicute........

Maybe now with the debug-boot( which injects its own se-policy, that I can add to) can try this route again.
[Miscellaneous Android Development] aryanhington:
were these vbmeta img files already on the device and you just reflashed them with --disable-verity --disable-verification?
[Miscellaneous Android Development] mrmazak:
Yes. They are part of stock rom
[Miscellaneous Android Development] aryanhington:
why are you using the kernel source code you obtained to port twrp for your device?
[Miscellaneous Android Development] mrmazak:
I do not understand your question.
[Miscellaneous Android Development] aryanhington:
can you port twrp just by pulling the proprietary binaries from your device rather than using the kernel source code released by blu?
[Miscellaneous Android Development] mrmazak:
Yes. That was done already.

TWRP built, not ported.

I just built the kernel on the omni source tree, it is easier that way.

.
[Miscellaneous Android Development] aryanhington:
how is building twrp for your device different to porting it to your device?
[Miscellaneous Android Development] mrmazak:
Porting implies taking a built image, unpacking it and changing files in the ramdisk. Then repacking.

Building , compiles the files from the device tree into the image.

Certain features are built into the recovery binary that cannot be modified by swapping ramdisk *.rc files
[Miscellaneous Android Development] aryanhington:
If porting requires changing files in the ramdisk, and you have already built twrp for your device using your proprietary binaries which you pulled from the device, why do you need the kernel source code from Blu?
[Miscellaneous Android Development] mrmazak:
?????

You do know the kernel is for other reasons, not just recovery, right.

Ram management, battery optimization, are controlled by kernel, and if you want to modify these Android behaviors you need to be able to modify kernel.
[Miscellaneous Android Development] aryanhington:
yes i know the kernel is not just for recovery but im asking why do you need the kernel source code when preparing twrp for your device?
[Miscellaneous Android Development] mrmazak:
Today, Sept, 8 Blu released fixed kernel source. And I just built stock kernel, tested it in TWRP.

Now the hard work can begin. ......

We should be close, maybe soon after team win fixes dynamic partitions for 10, we will have TWRP fully working here.
[Miscellaneous Android Development] herowilmington:
which device for omnirom did you take the kernel from?
[Miscellaneous Android Development] mrmazak:
You must have not understand what I say.

G90 kernel source is what I used.

But in the quoted comment I say I built it in the "minimum manifest" for TWRP. On omni branch 9.0

Bit the kernel is for G90, not from some other official device
[Miscellaneous Android Development] lennoxswindon:
what do you mean by Use 64 bit AB GSI?
[Miscellaneous Android Development] mrmazak:
Like here. This is a screenshot of the current gsi images from phh aosp. I highlighted the 64 bit ab images.
[Miscellaneous Android Development] mrmazak:
I put the "wip" TWRP in the Android file host folder I shared in the OP.

I did not mention or post about it yet, because it is not very useful. But I see there are already few downloads of it. So I just wanted to be clear. That TWRP is NOT tested, and is not very useful.
[Miscellaneous Android Development] herowilmington:
why did you not include the pgpt file and sgpt files in the firmware, are they not needed?
[Miscellaneous Android Development] mrmazak:
They were not included in the OTA, so I didn't put them.

There is now also a signed, official you can say, firmware. I don't recall if it is on there or not.
[Miscellaneous Android Development] lennoxswindon:
which button combinations are you using to boot to the recovery menu as you mentioned on the magisk github issue tracker you were unable to boot to recovery, instead you were booting to the boot menu?
[Miscellaneous Android Development] mrmazak:
Volume up.

And recovery will boot, just not when magisk-pathced.

Did it work for you?
[Miscellaneous Android Development] herowilmington:
on the magisk issue tracker you mentioned you have the factory rom but you are not sure if it is a leaked or released version. Why would the manufacturer leak it as opposed to releasing the firmware?
[Miscellaneous Android Development] mrmazak:
I cannot answer as to why.

The company "Blu" has always answered requests for stock rom downloads with "we do not supply firmware"
[Miscellaneous Android Development] lennoxswindon:
what do you mean you used rom tools option?
[Miscellaneous Android Development] mrmazak:
In the super script, then is an selection called "rom tools"

You are asking the wrong questions. It seems you do not know what super tool is, else you would have seen or known what "rom tools" was.
[Miscellaneous Android Development] mrmazak:
New build of TWRP has booted, without needing to be repacked first.

But it is bootlooping on TWRP logo. So it is not completely good news, but is closer
[Miscellaneous Android Development] Shananiganeer:
Just wanted to chime in and say that I'm watching with interest. Don't want you to think you're the only one using this device.
[Miscellaneous Android Development] mrmazak:
More progress on TWRP.

Was able to get a build to complete, and it boots. But when /data is encrypted TWRP is hang on logo screen.

During testing , I was able to boot TWRP and even flashed different TWRP.img with it, after wipeing /data with "fastboot - w"

This new TWRP can mount /system and /vendor

Did not try to backup since it was only booted with a wiped and empty /data

Usb otg storage was working, did not try sdcard

Adb connects, but logcat is "failed read". So bugs at this time

Published in file host folder.

As this has grown to 6 pages now, and no longer matches thread title, will be splitting to new thread soon

in case you missed it, you can find threads by "tags" since this device has no page of its own. Here is the tag page i used for G90

https://xdaforums.com/tags.php?tag=g90
[Miscellaneous Android Development] florianwinston:
which superuser apk did you use?
[Miscellaneous Android Development] mrmazak:
Whichever one phh is using in his gsi aosp
[Miscellaneous Android Development] Shananiganeer:
Not sure if you can help me, but I think I bricked my device. Flashed a magisk patched boot.img and ended up stuck at the boot logo. Flashed the stock boot.img back, but no change. Tried the boot-debug.img you provided, but still stuck at boot logo. Used your stock scatter file with sp flash, but it just got stuck at 0% on the preloader so I stopped it. Unchecked the preloader and the rest flashed without issue, but now the device won't power on at all. I'm hoping I'm missing something obvious, but if not then so be it.

EDIT: Aaaand now Windows won't recognize the VCOM device and I can't get sp flash to do anything.

EDIT2: Ok holding Pwr+Vol Up got sp flash to recognize it again, but now it says ERROR: STATUS_SEC_PL_VFY_FAIL (0xC0020006) if I try to flash the preloader. Still can't get the device to power on.

EDIT3: Tried again using your older stock firmware and the preloader actually flashed! A bunch of the other imgs failed saying they weren't verified. Still won't power on.
[Miscellaneous Android Development] aryanhington:
did you take a dump of your device before trying magisk?
[Miscellaneous Android Development] Shananiganeer:
Foolishly no. I had been using mrmazak's imgs without issue and assumed I'd be ok just by rolling back to the stock boot.img.
[Miscellaneous Android Development] aryanhington:
how did you flash the img files?
[Miscellaneous Android Development] Shananiganeer:
Initially I was using fastboot, when trying to go back to stock I've been using sp flash.
[Miscellaneous Android Development] aryanhington:
if your device doesnt turn on it may still be stuck in download mode where you have to remove the battery in order for sp flash tool to recognize it. is sp flash tool recognizing the device?
[Miscellaneous Android Development] Shananiganeer:
I can't remove the battery, it's fully off not in download mode, sp flash can recognize it and flash most partitions, but there are a handful that it complains about needing a signed img. Right now I can't get any response out of the device other than sp flash.
[Miscellaneous Android Development] aryanhington:
have you asked blu for stock firmware?
[Miscellaneous Android Development] Shananiganeer:
I just tried to through their website, but got a strange response page after hitting submit and I'm not sure it actually went through. No e-mail confirmation of the request so I'm thinking it bugged... Let me try again.
[Miscellaneous Android Development] mrmazak:
I have a link to "verified" images. I thought it was already posted, but looking back it was not.

https://www.mediafire.com/folder/ocmvgrcd73bqy/G90 G0310WW

https://www.mediafire.com/folder/ocmvgrcd73bqy/G90

Try to flash this.

When you get messages in spflash tool that say needs verified image. I am pretty sure this is a sign that bootloader has been relocked.

Just remember

DO NOT

format device
[Miscellaneous Android Development] Shananiganeer:
You're a damn legend man :good::good::good: Flashed that package and it came alive straight away.

Now I all I need to do is awkwardly re-contact their support and cancel the warranty claim. The website didn't work to contact them, so I called and they said all they could do was have one of their techs flash the stock firmware if I sent it in. Went through the process for that and before I could ship it out you saved the day.
[Miscellaneous Android Development] aryanhington:
So how did you resolve it?
[Miscellaneous Android Development] Shananiganeer:
Flashing the verified images from mrmazak through sp flash.
[Miscellaneous Android Development] aryanhington:
Was your bootloader unlocked ?
[Miscellaneous Android Development] Shananiganeer:
No it wasn't. Had to re-unlock it once it booted back into the stock ROM.

That being said, when I try to re-flash the GSI I was using prior to this fiasco, I end up stuck at the screen:

Orange State

Your device has been unlocked and can't be trusted

Your device will boot in 5 seconds

EDIT: Nevermind, I was using the boot-debug.img, but when I swapped to the normal boot.img it booted without issue. Camera doesn't seem to work though, which it did when I had the ROM installed before.

EDIT2: Flashed the super.img from the OP instead of the verified image and went through the process to flash the ROM and camera is working again...
[Miscellaneous Android Development] aryanhington:
you were trying to flash images on fastboot while the bootloader was unlocked?
[Miscellaneous Android Development] Shananiganeer:
Yes, the re-locking happened somewhere in the process of me using sp flash.
[Miscellaneous Android Development] aryanhington:
is it possible to use fastboot on your device while the bootloader is locked?
[Miscellaneous Android Development] Shananiganeer:
No
[Miscellaneous Android Development] aryanhington:
if the issue with your device is that it requires only signed images, why not just disable dm-verity and verified boot to resolve the issue?
[Miscellaneous Android Development] Shananiganeer:
I think you may have missed something, let me recap what went down.

Fastboot:

I initially flashed a custom ROM and did all the prep for that (unlock bootloader, disable dm-verity, delete logical product partition). I attempted to flash a Magisk patched boot.img and ended up stuck in a boot loop. I reverted back to the stock boot.img, but was still stuck in a boot loop.

SP Flash:

I turned the device off and tried flashing the June package mrmazak listed in the OP. I was able to flash everything except the preloader, and ended up not being able to turn the device on at all. I tried to flash the March package listed in the OP, preloader flashed, but then the bootloader seemed to be re-locked and I started getting messages that I needed verified images. Mrmazak provided a package of stock "verified" images and I was able to flash that entire package with no problems and the device was able to boot into the stock ROM.

Fastboot:

I re-flashed the custom ROM I was using, again including the prep (unlock bootloader, disable dm-verity, delete logical product partition), but was experiencing some bugs that I had not previously. I flashed the super.img from the June package, re-deleted the logical product partition, and re-flashed the custom ROM and then all bugs were gone and the device is happy again.
[Miscellaneous Android Development] aryanhington:
were you trying to flash the preloader or change the preloader img file?
[Miscellaneous Android Development] Shananiganeer:
I don't understand your question. Partial quote with hightlights:
[Miscellaneous Android Development] aryanhington:
what benefit is gained by flashing the preloader partition?
[Miscellaneous Android Development] Shananiganeer:
Was reverting to stock to resurrect the device.
[Miscellaneous Android Development] aryanhington:
As the Mediatek preloader is closed source I don't see why you flashed that partition, did your custom ROM contain a custom preloader?
[Miscellaneous Android Development] Shananiganeer:
Initially, I flashed everything except the preloader, but the device was still borked. Seeing as selective flashing through both fastboot and sp flash had not yielded results, I went for the 'nuclear' option of just flashing the entire stock package to guarantee there were no version mismatches. This was the correct idea, but I needed the "verified" images that mrmazak provided. I don't have the slightest clue how flashing a custom boot.img and then back to stock led to this situation which is why I went for the safer plan of just getting everything back to the same version of stock and then going from there.
[Miscellaneous Android Development] Ivisibl3:
just curious how were you able to and the su binary files to xbin
[Miscellaneous Android Development] mrmazak:
By unpacking the system image and adding the files, then repack and reflash the img.

It did not work to give root though, I had stopped trying for some time now.

I went into little more detail on how I edited the system.img in my thread posts for ulefone note 9 pro.
[Miscellaneous Android Development] aryanhington:
why did it not work in giving you root?
[Miscellaneous Android Development] mrmazak:
Not trying to sound like an ass or anything. But if I knew the answer to that I would not have stopped trying to get it to root.
[Miscellaneous Android Development] aryanhington:
Did you check if its an SELinux related issue?
[Miscellaneous Android Development] Tigrouzen:
Hi i'm dev i all ready make it rooted if you need help ask 😊

Pleas Share here an original boot.img and other boot.img patched with Magisk too of Blu G90 then i make it rooted
[Miscellaneous Android Development] Ivisibl3:
HERE ARE BOTH THAT I HAVE. STILL NOT SUCESSFULL AT INSTALLING AFTER REBOOT
[Miscellaneous Android Development] Tigrouzen:
Thanks you brb when ready
[Miscellaneous Android Development] Tigrouzen:
Just flash with fastboot and install Magisk Manager
[Miscellaneous Android Development] Ivisibl3:
i believe i may have found a way to get root through magisk. using the canary build of magisk manager.. changed the update channel to custom channel. and used the following custom channel address

credit to the onces at https://github.com/topjohnwu/Magisk/issues/3042

https://raw.githubusercontent.com/vvb2060/magisk_files/master/mtk.json

downloaded magisk zip from the manager and installed through twrp. cleared cache and rebooted. magisk shows installed.

as a side note i am currently using the boot-debug.img that mrmazak provided in the op
[Miscellaneous Android Development] mrmazak:
I also used this modified update chanel.amd got rooted. Don't know what was modified to allow it to work.
[Miscellaneous Android Development] Ivisibl3:
Works with the original boot.img as well. As a side note was able to mount system as rw in twrp and could delete unwanted apps through the file manager in twrp.
[Miscellaneous Android Development] mrmazak:
Not sure what it will affect, but this root is not passing safety net. It gives attestation failed.

Will try a magisk hide and props, to see if helps
[Miscellaneous Android Development] mrmazak:
The root with a modified magisk, seems to have an issue with safety-net.
[Miscellaneous Android Development] florianwinston:
if you're unable to root the stock ROM or via Magisk why not use a pre-rooted GSI seeing as you were flashing a GSI?
[Miscellaneous Android Development] Ayoub$#:
Hi, I did not find twrp umidigi a3s do you have please
[Miscellaneous Android Development] scarlion:
I tried to flash this but it's stuck in a bootloop...

it's not possible to root this device yet then?
[Miscellaneous Android Development] mrmazak:
i hav enot followed this thread in some time now. But yes root is posible, since magisk 20.3 i believe when full support was finished.

fastboot flash dissable verification vbmeta ....

fashboot flash magisk_patched_boot.

if you need full steps and commands you can respond and ask. But the directions are same as for all other reported working magisk patched root devices.
[Miscellaneous Android Development] kirichen:
China fake tablet BLU/G90/G0310WW

BDF Tab G10 Android11 Tablet Pad 10.1 Inch Octa Core 3GB 64GB MTK Helio P22​

ro.system.build.date=Wed Dec 13 08:54:02 UTC 2023
ro.system.build.fingerprint=BLU/G90/G0310WW:10/QP1A.190711.020
ro.build.version.sdk=30

unlock the bootloader

[stock Rom] Blu G-90 G0310WW

Blu G90 device shipped from factory with Android 10 as with other devices from blu they do not have a public download of there roms. So here is the stock rom pulled from the device with SP-Flash tool. Both the shipped rom build fingerprint...

xdaforums.com

fastboot devices
fastboot flash boot patched-boot.img
fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta_a.img
fastboot reboot
[Touch Diamond, MDA Compact IV Accessories] uniqueboy:
Can anyone recommend a suitable waterproof/dustproof case, maybe something generic for an mp3 player or a "normal" phone, just something that is a snug fit that preferably I can hang around my neck. I work in a very dusty environment, I wear a mask all day and ear defenders, so if the ringing is obscured it is not a problem, I just check my notifications when I get the chance. I had one for my old Artemis which I found at a car boot sale but it has developed a hole and my pristine Diamond rattles about in it horribly. I am also about to go on a beach holiday and would like to have my Diamond hermetically sealed around my neck in the sea. Any suggestions would be welcome.
[Touch Diamond, MDA Compact IV Accessories] derinahon:
Check this out:

http://www.sailgb.com/c/waterproof__mobile_phone_cases/?gclid=CJSbyLCt9ZQCFQyD1QoduChUqQ

or you could have it surgically implanted into your arm.
[Touch Diamond, MDA Compact IV Accessories] MrDerrickC:
Keep it in a sealable sandwich bag?
[Touch Diamond, MDA Compact IV Accessories] uniqueboy:
That is the kind of thing I'm after , but where can I get the surgery, I have tried implanting it in various other parts of my body already, another reason why I need that case!

And MrDerrickC won't it make my sandwiches taste funny after that?
[Touch Diamond, MDA Compact IV Accessories] beermonster65:
i remember seeing some phone condom type cases, not sure how durable they were but totally water proof
[Touch Diamond, MDA Compact IV Accessories] uniqueboy:
My phone is on the pill!
[Touch Diamond, MDA Compact IV Accessories] sdc77:
condoms

Those phone condoms are called Skinz .. http://www.skins-mobile.com/

They do exactly what you want.. and they are a talking point..

I have used them loads.. They allow you to use the phone normally and are completely waterproof.

Possibly a bit expensive for everyday use as they are supposed to be 'disposable' ..
[Touch Diamond, MDA Compact IV Accessories] Vivasvan:
i have the invisible shield.. took me 1 hour to perfect it... but you cant tell my phone is covered with it.. its truly great.

but not waterproof.. but then why would i want my moby waterproof? over 10 years of mobile use.. never once had a water issue with any of them. I just dont takethem near the water...:p

im covered for accidental damage anyway.. its just scratches i hate to get on my diamond... and the invisi shield is superb to stopthat.
[Touch Diamond, MDA Compact IV Accessories] uniqueboy:
you mean you've never dropped a phone down the toilet? How hard wearing is your invisible shield please? It does sound interesting. It is more dust contamination than flood damage that is essential for me, unless I get a new job, which at the moment really does sound like a good option!
[Touch Diamond, MDA Compact IV Accessories] StylusPilot:
so can you still use the touch screen when you have one of those "skins" on it?
[Touch Diamond, MDA Compact IV Accessories] bugeyes:
http://www.mymemory.co.uk/iPod-Classic-Cases/Design-Go/Design-Go-Dry-Sounds-MP3-Player-Waterproof-Case

these are really cheap !!

also if you get a mini usb to 3.5 mm headset socket adaptor your well away!

:)

i got one from a service station on the M11 near bishops stortford for about £5.

the case is semi transparent but you can make out the screen quite well, great for reading ebooks in the bath!!! LOL

its water proof to 3 meters IPx8

and fits tightly with about 20mm space to one side if you jam your diamond to other side of the case and there's about the same to the top too so you can store you cash in it and go swimming on the beach
[Touch Diamond, MDA Compact IV Accessories] futuresbright:
just ordered the invisible shield for my t-mob compact iv however it is only listed on website for diamond, do you think it will fit compact with flat battery cover or only diamond??

thanks.
[Touch Diamond, MDA Compact IV Accessories] bugeyes:
sorry to say the invisible shield you ordererd is specifically for the diamond !!!

its designed to fit around all the different planes of the diamonds corners etc so it will not fit your compact! try and get a refund!;)
[Touch Diamond, MDA Compact IV Accessories] MaRyNoFear:
Real Waterproof

Take a look here.

http://golden-shellback.com/

Thats real waterproof no ugly bags or anything else. :eek:

Remember to look at the video's.

I sa the review on engadget. This **** is for real. When it will be public avaliable I dont know, but for sure it will come.

Just waterproof
[Android Q&A, Help & Troubleshooting] Darius_bd:
.

Hi forum!

So I own a Project Tango Development Kit Tablet (device name: Yellowstone) which appears to be a Tango-purposed Nvidia Shield K1 tablet. There's just a few threads about the yellowstone in the Shield forum and it's an old device now, that's why I'm posting the question here, in the hopes that the question is not device-related but something more general.

So, I wanted to use this tablet and the stock ROM just made it bootloop ad infinitum. Nothing I did could make it boot. So I went to the Shield forum and I found a TWRP image that would work on it. I rooted it, installed TWRP and I installed a ROM that I found around an old thread. So far so good, the tablet now boots but the audio, microphone and camera doesn't work. I want to use it as an intercom system so, that's the stuff I really want it to be in a working state.

By chance I found a LineageOS 16 ROM for the yellowstone (https://updater.oddsolutions.us/yellowstone) but it's description says "PSCI Repartition ONLY". The author hasn't replied to me to what it means. Googling doesn't give useful results regrettably. So I wonder if anyone around this parts could enlighten me about what is it, and how can it be performed?

Many thanks!