yashsingh1/xdaforums huggingface dataset:
[Tilt, TyTN II, MDA Vario III General] ADB100:
I had a similar issue a while ago and in my case it was down to the Bluetooth Explorer issue when you reset/reboot without an SD card (or a corrupt SD card) and a second phantom 'Storage Card' appears - 'Storage Card2' I think it appeared as. For some reason a folder got created with the name 'Storage Card' and then the real storage card was then referenced as 'Storage Card2'. I had to manually delete the 'Storage Card' folder and then reset with the SD card inserted.

This might not be your problem but the behaviour you describe was the same as what I saw. Open File Explorer on the device (or browse via ActiveSync) and see if you have a 2nd Storage Card.

HTH

Andy
[Tilt, TyTN II, MDA Vario III General] Nylo:
Thanks foir the reply. I finally just did a hard re-set. I looked into your suggestion but didn't find a SC2.
[ASUS ZenFone 8 Flip] pescat8:
Please forgive my English ability.

I bought my ZF8F two years ago and have loved it. I was about to BLU and burn a ROM when Android 14 came out.

What are you doing at this exquisite, non-returnable time, ASUS!

I was just doing access analysis using mitmproxy,

I noticed that I could not even get past the "dm.asus.com/login" page.

So, I modified the Python code as follows.

*This code does not work.

from mitmproxy import http
def request(flow):
if flow.request.host == "dm.asus.com":
if "dm.asus.com/unlock/register" in flow.request.url:
flow.request.urlencoded_form["apkVersion"] = "2.0"
flow.request.urlencoded_form["swVer"] = "11..WW_I004D-WW_user_9999999..999999.13.35.11..ASUS-ASUS_I004D-WW"

def response(flow: http.HTTPFlow) -> None:
if "dm.asus.com/login" in flow.request.pretty_url:
flow.response.text = '{"data": {"project_status": "active","project": "ZS672KS","token": "redacted"},"retCode": 200,"message": "auth success"}';

Then, the login page is now going through!

However, I got the following json from the /unlock/register page.

{
"message": "success",
"retCode": 407
}

This results in error 20407.

So I think I can unlock it by overwriting the register page with the response function, but does anyone have a log of the success?

Thank you!
[ASUS ZenFone 8 Flip] pescat8:
I have rewritten the rest of the response based on the posts in this thread.

unlocking the bootloader

The Asus unlock app (v1.0.0.7) does not work anymore. It seems it was discontinued several month ago. Are there other ways to unlock the bootloader and flash a modified init_boot.img? I already created a patched image with Magisk but can't...

xdaforums.com

*This code does not work.

from mitmproxy import http
def response(flow: http.HTTPFlow) -> None:
if "dm.asus.com/login" in flow.request.pretty_url:
flow.response.text = '{"data": {"project_status": "active","project": "ZS672KS","token": "redacted"},"retCode": 200,"message": "auth success"}';
if "dm.asus.com/unlock/register" in flow.request.pretty_url:
flow.response.text = '{"Secrettoken": "4a25a920f1c0e16b4642843d122b8332d6a88bd374be956cea5ebfe2a08d5d7b189278f143c30e1c8ab319b056493e22f3db7dd0971b78794d912ef791aa2663a57f5780abc54fb13dd0484459daea14cceecb8efb734a1dceea1d551bee734bc71876c662a26624de3d800a77fcd0de6302a3d4cc33f770ee04b2aaea9c8afdaa95655f9a8fdf74f447a61aefce258297960d0934d7c16c6b9a37e2a477580803e235ac6076695620ce1740c18268fe01566491ee70b76aeeb45a06971c44a0808010de7409104ba21b6ce54ae84f678fbe781aebe212f7187a5010e969d6d8dbc5da9c47c142b8246ba12544faeaf0ed150463fd75ea74bc057c862843c9f8","data": null,"retCode": 200,"message": "success"}';
if "dm.asus.com/unlock/status" in flow.request.pretty_url:
flow.response.text = '{"retCode": 200,"message": "success"}';

This resulted in a reboot, but the boot loader did not change.

In other words, I think this problem boils down to the issue of how Secrettoken is calculated.
[OnePlus 12] PFusion:
In comparing the OnePlus 12 with a OnePlus 7 Pro it's evident that the OP7 Pro has a much better camera light/flashlight that. The new OnePlus 12.

The OnePlus 12 appears to have a slight green tint.Whereas the 7Pro has a slight rosy tint as its called.

Basically it looks like the OnePlus 7Pro has better color rendering index (CRI).
[Magisk] JhakaasJai1:
I downloaded magisk from github latest version (26) and got stock rom with same specifications online (RMX3388export_11_F.08_2023110915340134.zip). ofcourse i already had unlocked my bootloader with deeptesting (at that time there was no problem).

I extracted boot and vbmeta and patched it with magisk and flashed vbmeta with --disable-verity -disable-verification. I restarted my phone and noticed the tile icons (shutter) are invisible. It took like 1 minute for them to get back but i though it was just because i have'nt completed the setup so i opened magisk and complted the setup and restarted the phone. But the when i opened shinzuku and it asked for root i gave it but nothing happned.

I restarted my phone again and it started working. But i noticied the no sim icon even tho i have my sim installed so i checked the status in about option of settings. It says "Imei sv unknown" then i checked my baseband it was also "unknown" for unkown reason.

i checked other forums for similar issues and got to know that magisk had a bug where it did not initilize the network files or something when rooted with magisk on mediatek devices. There was a fix which mentioned that deleting the /mnt/vendor/nvdata/md/NVRAM/NVD_IMEI folder did temporary fix the problem so i did that (ofcourse with backup) it did nothing so i restored the files.

Now, there is a problem i did not saw efs image file inside /dev/block/by-name but nvdata, nvram and persist were there. Could it be that rooting has erased efs partation? (assuming if it even shows inside that block folder)

I did'nt install custom recovery or custom rom or anything. Do i install custom recovery to flash whole stock rom but some guys did that and problem was not solved. i will make a backup of nvdata,nvram and persist if anything goes wrong.

What should i do
[Magisk] JhakaasJai1:
@Oswald Boelcke Umm, i wanted to post this to magisk. Can sir transfer it there. I did'nt know i cannot delete nor duplicate the questions. Thanks.
[Magisk] Oswald Boelcke:
I've moved the thread.

Regards

Oswald Boelcke

Senior Moderator
[Magisk] JhakaasJai1:
Logfrom magisk debug 27001
[Magisk] JhakaasJai1:
i got to see some error on radio in kernal

Theia Logs:
[Magisk] JhakaasJai1:
I also noticed that i cannot go to stock recovery with patched boot but can go with original easily. I restarted into recovery with magisk and it started bootlooping. I had to go to fastboot mode to come out of loop.
[Magisk] JhakaasJai1:
vbmeta and boot images.
[Magisk] JhakaasJai1:
Logcat (not from bootup but there are enough errors)
[Magisk] sukuna ryomen:
Pls upload persist.img I need it my Bluetooth WiFi hotspots not working I need persist.img
[OnePlus Nord 2 5G] zabixii:
Mine doesnt work. Error unsupported device in twrp. If someone could help please respond or contact me on dc: zabixii
[OnePlus Nord 2 5G] Klangerzeuger:
There is no custom kernel for the Nord 2 because OnePlus does not provide kernel sources.
[OnePlus Nord 2 5G] zabixii:
https://www.xda-developers.com/oneplus-nord-2-nord-200-kernel-sources-released/ i thought this was it but im noob so idk
[OnePlus Nord 2 5G] zabixii:
so there is no way of making nh kernel?
[OnePlus Nord 2 5G] Klangerzeuger:
No
[Xperia Z3 Compact Q&A, Help & Troubleshooting] tomtrk69:
Hi,

I am trying to put lineage OS on a sony xperia z3 compact (WIFI only model: SGP611) but I am not able to flash the firmare images. I was able to unlock the bootloader, but after trying to install twrp the device did not boot anymore (only black screen).

The images used were from the link from this thread:

[ROM][DEVELOPMENT] Unofficial LineageOS 14.1 (Updated 7/10)

What it is A custom ROM built from LineageOS sources. Disclaimer /* * Your warranty is now void. * * We are not responsible for bricked devices, dead SD cards, * thermonuclear war, or you getting fired because the alarm app failed...

xdaforums.com

Now I am able to enter fastboot mode when I press vol up and insert USB connection. I am using linux and tried to flash the images from the package linked in the above thread manually:

$ fastboot flash boot boot.img
Warning: skip copying boot image avb footer (boot partition size: 0, boot image size: 8019968).
Sending 'boot' (7832 KB) OKAY [ 0.249s]
Writing 'boot' OKAY [ 0.527s]
Finished. Total time: 0.794s
$ fastboot flash system system.new.dat
Sending 'system' (706420 KB) OKAY [ 22.164s]
Writing 'system' OKAY [ 46.832s]
Finished. Total time: 69.007s
$

But after this I am not able to switch on the device. Vibration motor does a short move and then it switches off again.

Is there a way to unbrick and flash the device if it only starts fastboot? twrp does not start and adb does not find anything at the moment.

tom
[Xperia Z3 Compact Q&A, Help & Troubleshooting] tomtrk69:
Hi,

meanwhile I tried a lot of different things, but it seems there is no information how booting with these nearly undocumented chipsets and memory connections really works. Flashing recovery twrp with fastboot throws no error, but the tablet still does not boot or show anything. No display, no logs, no docs.

So if no one can help, I assume my device is electronic waste :-(

tom
[OnePlus 12] timebandi:
I need to format /sdcard (internal storage) without looking anything else. Due to bad files.

How can I do this or I'll have to Factory Reset?
[OnePlus 12] clsA:
it might be possible if we had a working custom recovery and you were rooted

without those I don't know of any other way to format storage
[OnePlus 12] chrissss91:
Have a look to fastboot erase data and fastboot format userdata

Maybe it can help you
[Nintendo Switch News, Guides, Discussion , Develop] Lost-Entrepreneur439:
/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about features included in this ROM
* before flashing it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*

crDroid is designed to increase performance and reliability over stock Android. You will find many custom features implemented from the Android custom ROM community over the years. Enjoy!

What works, what doesn't?​

While this should be compatible with any modded Switch, I have only tested on a v1, modded with fusee-gelee.

Working:​

Everything, from my testing.

Issues:​

SELinux is permissive.

Download:​

Latest version (02-15-2024): https://github.com/Lost-Entrepreneur439/nvidia-tegra-x1-crdroid-releases/releases/tag/02-15-2024

Installation guide:​

Mod your Switch, if you haven't already.

Back up your SD card, this will wipe anything on it.

Boot your Switch into hekate

Go to Nyx Settings, then do Dump Joy-Con BT

Exit Nyx Settings, go to hekate's Tools section, and select Partition SD Card.

Use the sliders to select how much storage you want for Android. You need at least 8GB.

Copy the 7z file to the root of your SD card.

If wanted, also add the Magisk and/or GApps zip to the root of your SD card.

On your Switch, select the "Flash Android" option.

Go to Factory Reset, format data and system.

Go back, select "Apply Update", then select "Choose from SWITCH SD"

Select the crDroid zip.

If wanted, flash Magisk and/or GApps.

When finished, reboot. Your Switch should now boot into crDroid.

To boot from hekate, go to More Configs, then select Android.

Thanks:​

Huge thanks to the switchroot team, without them, this ROM would not be possible.

Thanks to the crDroid team for making this great ROM.

Thanks to Nintendo for making the Switch.

Sources:​

All sources can be found in the switchroot devices.xml and additions.xml.

For help, see this device's Discord server!

ROM version: Android 11.0 Red Velvet Cake

Kernel version: Linux 4.9.141

Requires: Modded Switch, MicroSD card

This ROM is in beta.

ROM creation date: February 15, 2024

Last ROM build date: February 15, 2024
[Nintendo Switch News, Guides, Discussion , Develop] Lost-Entrepreneur439:
Screenshots
[Nintendo Switch News, Guides, Discussion , Develop] AnyNameYouWish:
Thanks for this release, will it work as well as switchroot's android?

Is it based on a more recent android built?

What are the differences with switchroot, what does your version add?

Don't get me wrong, I'm not trying to look for weakness, I'm just naively and enthusiasticly wanting to understand the differences :)
[Nintendo Switch News, Guides, Discussion , Develop] Lost-Entrepreneur439:
This works as well as switchroot's Android, as it is using the switchroot sources.

No, just like the latest switchroot, it is android 11.

You can find the features list on crDroid's website https://crdroid.net/
[Nintendo Switch News, Guides, Discussion , Develop] Cross_4live:
Cooler not working
[Nintendo Switch News, Guides, Discussion , Develop] asd132:
I followed the steps and I got error at 9.

I have already tried to put 7z directly and unzip 7z + copy all files to SD card root directory.

Both not working.

View attachment 6096908
[Nintendo Switch News, Guides, Discussion , Develop] tracins:
Same problem herre. Is there a fix?

Even unzipped the Install folder from within 7z file to root and nothing.
[Nintendo Switch News, Guides, Discussion , Develop] AngelFdez1234:
You can fix it?
[Nintendo Switch News, Guides, Discussion , Develop] EmPiFree:
Can someone tell me if Joiplay is working smoothly? Trying to play some games on Switchroot A10 with Joiplay, but it runs only with ~10 FPS
[Nintendo Switch News, Guides, Discussion , Develop] marioslah:
Bluetooth doesn't work for me is this an issue?
[Nintendo Switch News, Guides, Discussion , Develop] marioslah:
dur

during installation i wiped my sd card and i forgot to redump the bl of joycons..

dumped them and reflashed the rom and it worked.
[Nintendo Switch News, Guides, Discussion , Develop] marioslah:
nvm issue came back tried to redump and reflash again didn't work.

in the end i flashed lineagesos no issue with Bluetooth.
[Touch Pro, Fuze Themes and Apps] hurrycaine3000:
I was trying a new skin for my calculator and now it won't work. Anybody have a Nice simple replacement calculator. I was trying to find this one http://xdaforums.com/showthread.php?t=326125

but no luck. the link doesn't lead anywhere.
[Xiaomi 13 Ultra] lubo777:
View attachment 6068604

I'm sharing here the Unofficial version of the AOSPA ROM build for Xiami 13 Ultra from Akash Srivastava (@markakash in XDA and in TG)

AOSPA Paranoid Android Uvite [Unofficial] for Xiaomi 13 Ultra (ishtar)​

There is a new Paranoid Android version available here

aospa-uvite-stable-4-ishtar-20240324.zip

The developer of the ROM has switched the ROM installation from fastboot update to recovery flash.

In order to flash or upgrade the latest Paranoid Android AOSPA ROM you have to:

1. You can use TWRP or you can download the Paranoid Android recovery.img

Keep in mind that if you use TWRP after the flash it will be replaced by the AOSPA recovery.

Of you decide to use the AOSPA recovery you can Download the Paranoid Android recovery.img from here: recovery.img

2. Restart your phone in Fastboot mode with pressing Volume Down + Power

3. Flash the recovery in fastboot mode with:

fastboot flash recovery recovery.img

4. Reboot in recovery:

fastboot reboot recovery

5. From the recovery menu choose:

Apply update from ADB

6. Send the ROM from you computer to the phone with:

adb sideload aospa-uvite-stable-4-ishtar-20240324.zip

7. Flash via adb sideload firmware version OS1.0.6.0.UMACNXM from here

---------------------------------------------------------------------------------------------------------------------

OLD installation instructions for versions BEFORE aospa-uvite-stable-4-ishtar-20240324.zip

---------------------------------------------------------------------------------------------------------------------

Installation:

If you come from MIUI / HyperOS you need a clean install and have to format the data partition

1. Install custom recovery TWRP - use the version designed for your Android 13 or 14 from here

(check the A13 or A14 suffix in the name of the file or the touchscreen will not work in TWRP)

2. Flash this firmware in TWRP (from phone drive or via adb sideload) : V1.0.5.0.UMAEUXM from here

3. Boot in fastboot (Reboot keeping Volume Down + Power)

4. Flash the ROM:

fastboot update aospa_ishtar-stable-2-img-eng.markakash.zip

This command will flash and boot the ROM.

Notes:

1. Keep in mind that it will replace your TWRP recovery with the Paranoid custom recovery. If you prefer TWRP you have to flash it again from the fastboot. :)

2. This Unofficial AOSPA ROM version does NOT support 32 bit (old) apks.

If you like me LOVE and use some 32 bit apk (like Swype keyboard) go to A13 AOSP ROM like PixelExperience Plus or use A13/A14 MIUI / HyperOS ROM of your choice :)

Download the latest version of the AOSPA ROM: here

You can donate to the developer of the ROM: here
[Xiaomi 13 Ultra] lubo777:
reserved for short AOSPA ROM review on Xiaomi 13 Ultra + a script for cleaning some annoying apk from google and M$! :) coming preinstalled with this ROM.
[Xiaomi 13 Ultra] kkkkkkk99:
i am getting this error View attachment 6070974
[Xiaomi 13 Ultra] lubo777:
with which version of the AOSPA is this error?
[Xiaomi 13 Ultra] JohnTheFarm3r:
Update your Platform tools.
[Xiaomi 13 Ultra] kkkkkkk99:
Can you share it with me? The platform I use is the latest
[Xiaomi 13 Ultra] energykriger:
I have the Same error. Can you plus fix ludo777 i wana try your Rom.
[Xiaomi 13 Ultra] energykriger:
Is it also possible to flash your Rom in TWRP?
[Xiaomi 13 Ultra] NOSS8:
Have you read the OP?
[Xiaomi 13 Ultra] energykriger:
What you mean with OP?
[Xiaomi 13 Ultra] NOSS8:
OP=original Post.
[Xiaomi 13 Ultra] energykriger:
Where can i Find the link? I only read this Post.
[Xiaomi 13 Ultra] NOSS8:
Come on, the link is in the second line of the instructions.:unsure:
[Xiaomi 13 Ultra] energykriger:
Sorry but i dont See it.
[Xiaomi 13 Ultra] NOSS8:
1. Install custom recovery TWRP - use the version designed for your Android 13 or 14 from here
[Xiaomi 13 Ultra] energykriger:
But i have TWRP installed. I asked, if i can install the Rom also in TWRP, because fastboot gives me an error.
[Xiaomi 13 Ultra] NOSS8:
You are spamming this thread when everything is mentioned in the OP that you don't read or understand.
[Xiaomi 13 Ultra] JohnTheFarm3r:
Instead of showing the error and eventually figuring out the ERROR you're getting in fastboot, you're asking about TWRP. If TWRP isn't mentioned, it means IT WON'T WORK.
[Xiaomi 13 Ultra] JohnTheFarm3r:
<Mod Edit> Quote Removed

View attachment 6075646

??????????
[Xiaomi 13 Ultra] energykriger:
I did
[Xiaomi 13 Ultra] JohnTheFarm3r:
Well, I doubt you're doing it correctly because it works perfectly fine for thousands of users.
[Xiaomi 13 Ultra] energykriger:
Okay, i will try later again. I thought that it could be a Problem with the Version of Rom because i had only yesterday time to try it.
[Xiaomi 13 Ultra] energykriger:
now i used my gentoo system and everything worked well. thx for your help and sorry @JohnTheFarm3r
[Xiaomi 13 Ultra] ozenbora9:
I encountered the same error, can anyone help? I am using minimal adb fastboot v1.4.3
[Xiaomi 13 Ultra] JohnTheFarm3r:
Bruh....HOW ABOUT READ? Literally written multiple times.
[Xiaomi 13 Ultra] lubo777:
There is a new Paranoid Android version available here

aospa-uvite-stable-4-ishtar-20240324.zip

The developer of the ROM has switched the ROM installation from fastboot update to recovery flash.

In order to flash or upgrade the latest Paranoid Android AOSPA ROM you have to:

1. You can use TWRP or you can download the Paranoid Android recovery.img

Keep in mind that if you use TWRP after the flash it will be replaced by the AOSPA recovery.

Of you decide to use the AOSPA recovery you can Download the Paranoid Android recovery.img from here: recovery.img

2. Restart your phone in Fastboot mode with pressing Volume Down + Power

3. Flash the recovery in fastboot mode with:

fastboot flash recovery recovery.img

4. Reboot in recovery:

fastboot reboot recovery

5. From the recovery menu choose:

Apply update from ADB

6. Send the ROM from you computer to the phone with:

adb sideload aospa-uvite-stable-4-ishtar-20240324.zip

7. Flash via adb sideload firmware version OS1.0.6.0.UMACNXM from here
[Xiaomi 13 Ultra] energykriger:
But i did the update with twrp and everything works. So what problems should i expect?
[Xiaomi 13 Ultra] ebusuhejbi:
Leica camera is included on this rom??
[Xiaomi 13 Ultra] energykriger:
Yes
[Xiaomi 13 Ultra] a18h:
hi, i'm in xiaomi.eu last weekly dev, what instruction must i use for install last paranoid? old or new (last)?
[Xiaomi 13 Ultra] lubo777:
The default ROM recovery.img is HIGHLY recommended, because TWRP can't flash correctly all the partitions used by the ROM.

for the latest Paranoid use the latest installation howto which flash the ROM in recovery, also you have to clean data partition (make factory reset)
[Xiaomi 13 Ultra] JohnTheFarm3r:
TWRP can flash ALL the partitions just fine. Where are you getting such false information?
[Xiaomi 13 Ultra] lubo777:
I flashed it with TWRP and have got A LOT of partition errors! .... :)
[Xiaomi 13 Ultra] JohnTheFarm3r:
Show me the screenshot of your partitions error, because I'm 100% sure you're referring to the errors that are unrelated to the ROM and system partitions but some warnings that TWRP throws because you flashed a new ROM, and it can't mount some of the current partitions which is natural till your reboot the TWRP after you flashed the new ROM.

TWRP can be used perfectly fine to flash ANY custom ROM. PE+ by the same developer was flashed via TWRP most of the time and now he switched to recovery builds once again with PA. TWRP is even shared in the group for the people who want to use it.

Even Xiaomi.eu devs suggest the use of TWRP...their builds are even built so that they reboot to TWRP and do an OTA update through TWRP.

Don't get me wrong, but I don't think you understand what those "errors" mean, so it's not the best idea to spread such statements till you're sure that you understand what the issue is or what exactly is happening and why.

No puns intended, just sharing my two cents so that people don't get the wrong idea about the TWRP that works perfectly fine and can even decrypt the DATA from the ROMs which is very rare nowadays on devices that ship A13 and upwards.
[Xiaomi 13 Ultra] lubo777:
do you know Lineage OS?

Have you ever hear (read) that you CAN'T flash Lineage OS with TWRP because of the same reason I wrote above, TWRP can't flash RIGHT all the Lineage OS partitions this is the simple reason why all flash Lineage 20 / 21 with Lineage OS recovery, after the flash you can install TWRP and use it for backup and etc.

P. S. I haven't made screenshot of the error I had, sorry.
[Xiaomi 13 Ultra] lubo777:
OK, just in case I asked the developer of the AOSPA ROM about the TWRP and bellow you can see his answer ...

"

_redead🇳🇵, [29.03.24 г. 11:31 ч.]

For me it flashed fine using twrp

_redead🇳🇵, [29.03.24 г. 11:45 ч.]

If u flash using twrp, twrp gets replaced with aospa recovery

_redead🇳🇵, [29.03.24 г. 11:46 ч.]

So u can flash future builds using aospa recovery"

So as I mention it above in my first answer I'm using AOSPA recovery to flash the ROM because of the experience I had with the Lineage OS AOSP installation requirements, which definitely 100% sure CAN'T be flashed correctly with TWRP.

As you can see alone it do not matter so much which recovery you will use in order to flash AOSPA, because in all cases after the flash you will end with the AOSPA recovery installed on your phone.