yashsingh1/xdaforums huggingface dataset:
[Asus Zenfone 9] rootlessabroad:
Anyone know where to get these without a mark-up? Asus doesn't seem to have the 16GB/256GB. The $800 + tax is already blowing my budget, so I can't afford the mark-up to buy from an Amazon reseller.

If there is only Asus, does anyone have a line on when the only model worth getting (since there is no sd card slot) might be available again?

Thank you.
[Asus Zenfone 9] Veiranx:
https://smile.amazon.com/dp/B0BBPJ6TNC?ref=ppx_yo2ov_dt_b_product_details&th=1

Try this one. It's the same page I bought my launch one from. Still seems solid, IMO.

EDIT: This is the USA version (version C)
[Asus Zenfone 9] softshape:
There is 11.11 sale on Aliexpress, 3 days left, and it's about $760 for 8/256 model.
[Asus Zenfone 9] craznazn:
Make sure if you buy on Amazon, the seller is mobile advanced. Other sellers are using the listing to push non us models
[Asus Zenfone 9] rootlessabroad:
Mobile Advance has the 8/256GB available for $709 + tax: https://smile.amazon.com/ASUS-ZenFo...G-BK/dp/B0BBQ9MYR6?ref_=ast_sto_dp&th=1&psc=1 (which is a better price than Asus' website.)

Spending that much, it isn't too much more to just get the additional 8GB (16GB). While Android 12 & 13 don't 'need' 16GB, every version needs better hardware.

The only 16/256 version is NGP and they want $100 bonus. At that price you are in the same territory as the ROG phones (which are just beasts, albeit impressive beasts).

Hopefully they will get some more of them out of China soon. Hard with all of the Covid closures there.
[OnePlus 9 Pro] harriii:
How to update OnePlus 9 pro dual sim non PTA Patched without removal of patch? Please help
[OnePlus 9 Pro] AndyC76:
Hi,

1)

What phone model (hardware)? LExxx, If you're not sure, it will be on the box

2)

Which ROM do you have installed? Which exact A13 version? Stable/ Beta etc.

3)

What do you mean by PTA patch?

Once you answer the above, someone will be able to help you
[OnePlus 9 Pro] samwhiteUK:
Not everyone will have the box, but it's on the back of the phone as well ;)
[OnePlus 9 Pro] Mr Hassan:
1st this forum not provide support imei repair patched services

U can try update coz i updated without any issue
[OnePlus 9 Pro] Oswald Boelcke:
@Mr Hassan I don't recognise any request for support to change of IMEI in any of the above posts. And just to be precise, XDA doesn't allow discussions of or support regarding change of IMEI's but we do allow support for the repair or recovery of the original IMEI.

Please refarin from any attempts to moderate this forum. Thanks for your cooperation.

Regards

Oswald Boelcke

Senior Moderator
[OnePlus 9 Pro] Appreciative:
It's very fair of you to allow the thread to continue, in my view.

I believe it was brought up because a "PTA patch" is, from my limited understanding, an imei change required in Pakistan for many devices to get on the network there. PTA = Pakistan Telecom Authority. I read in another thread that certain (it was described as many) devices are blocked from PTA networks without a "patch". Many users buy these phones knowing them only as a "pta patch" where it's an imei that has been changed from the original. I don't think it's from blacklisted imeis of stolen/missing/unpaid devices, more of a network politics thing but I may be wrong.

His concern seems to be losing that patch upon update. Which I think doesn't go into supporting imei changing, just how to keep his phone in the current state it's in, but update.

It's worded a little difficult "non pta patch...without removal of patch"

Hopefully he gets it sorted out
[OnePlus 9 Pro] djsubterrain:
Would the Indian build cover Pakistan too?
[OnePlus 9 Pro] Mr Hassan:
What u mean by cover? Cover pta? No never its not about build then
[Touch Pro, Fuze ROM Development] trinode:
Ok, can anyone tell me what I did wrong?

I extracted a htc rom, put a new opera wwe and opera _409 folder from another rom in (in the oem folder)

and I did "follow the on screen instructions"

But at a number of times, it just ran a utility and told me nothing about what to do with it.

I then flashed it, and sh*t myself when i noticed during the flash that the rom was only 70MB.

Thank god for HardSPL.

What did i likely do that resulted in the bad rom?

I've looked for a tutorial, but cannot find one that covers the tools / windows in the raphael kitchen build process.

Any help would be appreciated.

Edit: I used the new buildOS+package tool, not the old BuildOS as that one had a problem with duplicate provxml files I think.
[Touch Pro, Fuze ROM Development] trinode:
Nevermind, worked it out...

Thanks anyhoo
[Motorola Moto G100 / Edge S] michaelpartono181992:
Please help me. Please share installer,I need ready for Assistant 1.6.59 or 1.6.60 ..... 🙏🙏🙏...

Because new ready for assistant very many bug and can't connection cable to pc.
[Motorola Moto G100 / Edge S] michaelpartono181992:
Please help me I need installer PC Motorola ready for old version 1.6.59 or 1.6.60...

Because new version Motorola ready for can't support wired...
[Motorola Moto G100 / Edge S] Danielthomas0308:
Which device you are using???
[Motorola Moto G100 / Edge S] michaelpartono181992:
Motorola g100
[Redmi Note 11 (spes/spesn)] Nihan Khan:
When i factory reset my redmi note 11 then my Portable Hotspot option move to Connection and Sharing option.

View attachment 5755231

View attachment 5755233
[Redmi Note 11 (spes/spesn)] Lister Of Smeg:
Hi there,

I wonder if the option change is because you've gone from A11 to A12.....

I can't verify that, as I am still waiting to get the big update....

..... although I can see you have a few System Apps to update, DO NOT UPDATE SYSTEM APPS.... it will break your phone !!!

Cheers, Lister
[Redmi Note 11 (spes/spesn)] Nihan Khan:
Please explain me properly. No i am still A11.
[Samsung Galaxy A32 4G] Frank10cantillo:
The bug seems to be related with 4g, just disable it.

Go to settings-connections-mobile networks- and select 3g/2g mode.

Thats it bug fixed.

At least while samsung fix the problem, you can also downgrade to first android 12 version, or 11 the problem isn't at there.
[Touch Diamond, MDA Compact IV General] SimonW500:
Can someone please clarify the difference between HSDPA and HSUPA?? I know HSDPA is the next one up from 3G in terms of speed, but am unsure of what the D and U stand for (guessing variants of similar?).

From what I can see HSUPA was not enabled by default on most older ROMS, but could be in the registry or using something like AdvancedConfig. However I notice that it is enabled by default on the latest Vodafone ROM (v1.97.x.4, a horrible looking branded ROM that I had to get rid of, but with some interesting 'latest and greatest' components hidden in there).

Lastly to sum this one up in my own context - a UK user on Vodafone - do I gain any benefit from having it enabled?

Thanks!
[Touch Diamond, MDA Compact IV General] DaveShaw:
Wikipedia has a lot of info on HSDPA and HSUPA and the differences.

As for enabling it on the Diamond, someone else will have to help you :eek:

Dave
[Touch Diamond, MDA Compact IV General] SimonW500:
Thanks for the prompt reply. Indeed you're probably right - I could've used Google a bit more prior to posting.

To answer my own question / for the benefit of others:

They are both HSPA protocol implementations although achieve it using slightly differing methods, therefore while similar are distinctly different and not directly compatible.

It seems Vodafone in the UK has both HSDPA and HSUPA networks, therefore I guess it *IS* of benefit to have it enabled (potentially more chance of picking up a network signal faster than 3G).

:)
[Touch Diamond, MDA Compact IV General] peterc10:
The D stands for download and the U for upload. They are all part of the same service, just used for different directions of data travel. Some networks have one and not the other some have both.

Not absolutely sure but judging from the maximum upload speeds quoted by HTC for the Touch Diamond it does not support HSUPA anyway
[Introductions] danilo65535:
I'm only a curious guy from Brazil, trying to help other people.
[Redmi Note 10S] jjsan:
yesterday my fingerpring sensor (power button) became really hot.

without installing any app or doing some changes.

going to try wipe after backup

has someone same experience?
[Redmi Note 10S] tutibreaker:
only the power buttom or the device?
[Redmi Note 10S] jjsan:
yes. nothing else
[Redmi Note 10S] tutibreaker:
quite odd, did you do something before get hot?
[Redmi Note 10S] jjsan:
nothig. just using my phone
[Redmi Note 10S] orangpelupa:
When My redmi note 8 pro finger print scanner became hot, turns out it was a short circuit. Cleaned the sensor and socked and then it work fine.

Maybe the same issue with what occurred to your 10s?
[Redmi Note 10S] jjsan:
which sensor? powerbutton?
[Redmi Note 10S] orangpelupa:
Yes. As the finger print sensor is in the power button, for redmi note 10s
[Redmi Note 10S] :
Bro it may be some issue with the power button, maybe some components of sensor or button have weared out, suggest you to visit service center for better assistance.
[Google Pixel 7 Pro] Pritster5:
I followed this guide exactly: https://topjohnwu.github.io/Magisk/ota.html

Before starting the guide, I had a pretty new Pixel 7 Pro with the latest version of Magisk successfully installed (with bootloader UNLOCKED) and some small Magisk modules to tweak things (iOS emojis). I made sure to restore boot images and got the "restoration complete" toast message.

I saw the notification for the November update, downloaded and installed it. I did NOT reboot after that. I then went into the Magisk app and tapped "install to inactive slot (after OTA)" and rebooted from within the Magisk app.

My device rebooted, and showed me the bootloader unlocked screen, then showed me the "your device is corrupt" warning and said "press power button to continue". I pressed the power button and my device is now stuck on the Google logo.

Has this happened to anyone else? And is there any way to fix this (preferably without data loss)?
[Google Pixel 7 Pro] Freak07:
That´s a bug within AVB. Unfortunately it can happen on Pixel 6 and 7 devices.

There´s one thing that can clear it:

I know this sounds a bit counter intuitive, but download october factory image, extract init_boot.img, flash it via fastboot on your device with nov firmware.

fastboot flash init_boot init_boot.img

Try to let it boot, if it fails or crashes go back to bootloader via long press power and volume down. (can take up to 30 seconds on p7pro)

If it boots already don´t forgot to flash init_boot from november firmware still.

Then download november factory image, extract init_boot.img, flash it via fastboot as well. This might get you out of the loop.

If you want you can use a magisk_patched init_boot.img as well so you´re rooted.

That last step should get you out of the corruption loop, as flashing outdated init_boot and then correct init_boot will somehow clear avb.

I´ll attach patched init_boot.img from november firmware TD1A.221105.001, Nov 2022 for you.
[Google Pixel 7 Pro] Pritster5:
I see. Thank you so much for this info. I will try and report back my results. Has this bug been fixed in newer versions of Magisk or Android? I feel like it's a high priority bug given that it soft-bricks peoples devices.

EDIT: And does this process result in data loss?
[Google Pixel 7 Pro] Pain-N-Panic:
Glad you're on our forum Freak!
[Google Pixel 7 Pro] Pain-N-Panic:
Remove "-w" from the flashall.bat, I believe that ensures you keep data.
[Google Pixel 7 Pro] Pritster5:
I'm also a bit confused by this step: "flash it via fastboot on your device with nov firmware." Are you saying that I should flash october init_boot.img onto my phone, which already has the Nov firmware installed? Or do I have to merge the Oct init_boot.img into the Nov firmware (full factory image TD1A.221105.001)
[Google Pixel 7 Pro] Freak07:
yes, you flash the old outdated init_boot via fastboot on november firmware.

afterwards you flash back the correct one for november. that will hopefully clear the avb bug you´re experiencing.

You flash only this img, not anything else. do precisely the steps I described. you don´t have to flash the full firmware, as you already updated to november if I read your initial post correctly and OTA to november was successful.

no it has not been fixed.

no, with the steps detailed there´s no data loss.

I wouldn´t recommend updating your phone with the magisk flash to inactive slot method. That´s not working for most people on p6 and p7 devices.

the method I described doesn´t involve using that script. no data will be lost.
[Google Pixel 7 Pro] devsk:
How do you expect this to work for p7p? The Magisk code has not been updated yet to flash init_boot partition instead of boot partition on p7p. Of course, it will corrupt your boot partition.

Update Magisk using the method outlined in the main thread for OTA and Magisk: https://xdaforums.com/t/november-20...-safetynet-all-relevant-links.4502805/page-61
[Google Pixel 7 Pro] Freak07:
If what @devsk states is true, you also need to flash back stock boot.img from november firmware via fastboot @Pritster5.

fastboot flash boot boot.img

Since magisk can patch init_boot.img´s, I assumed it would account for pixel 7 pro, having ramdisk inside init_boot instead of boot.img. It´s a bad design choice by magisk app to show this option to users on Pixel 7 pro in that case. :/ but even on pixel 6, the forums are full of people running into issues with that method.
[Google Pixel 7 Pro] Pritster5:
Where can I see what devices are supported for that method? I assumed that the guide worked for anyone with A/B partitioning. It would be helpful if there was a notice of this somewhere on the guide or any other obvious place.
[Google Pixel 7 Pro] devsk:
The easiest way to recover is to follow that guide and flash the whole ROM (it will fix both the boot and init_boot partitions). *Make sure* to remove -w from the flash-all.bat or flash-all.sh, whichever one you are using. This part is important. "-w" command line argument wipes your data and you don't want that.

I just updated my p7p using this method this afternoon and it worked fine.
[Google Pixel 7 Pro] devsk:
That link is specifically for p7p
[Google Pixel 7 Pro] Pritster5:
Oh I meant where can I see what devices support the Magisk "Install to inactive slot" guide.

You said "The Magisk code has not been updated yet to flash init_boot partition instead of boot partition on p7p. Of course, it will corrupt your boot partition."

How are you aware of this? Did you find this out by reading the code itself or was there a notice of this somewhere?
[Google Pixel 7 Pro] devsk:
Actually, this got me thinking and I looked at the code. Looks like the magisk code (the bash function find_boot_image) seems to be doing the right thing by treating init_boot ahead of boot partition.

Do you have the logs from that run of "Install to inactive slot"?
[Google Pixel 7 Pro] Pritster5:
I don't believe so, as I can only connect to my phone via PC over fastboot mode right now, so I'll have to check for logs after fixing my device.

One other question though, the guide you linked mentioned disabling magisk modules before flashing the factory image. I was never able to do that because I used the inactive slot guide which made no mention of it. Will the enabled magisk modules prevent me from using the guide you linked?

I am also unable to do this step as I can't transfer files from my pc to my p7p when I cant access the phone aside from fastboot mode: "Copy the init_boot.img from the PC to the phone's internal storage." Can I skip this step?

EDIT: Should I just use the Android flash tool instead if I don't have access to ADB? Or should I instead just follow Freak07's steps since his steps don't require adb access?
[Google Pixel 7 Pro] devsk:
Just restore your device by flashing the whole ROM. This will get rid of magisk and you should have no problem booting back into the system. You will have lost the root at that point. Once inside, transfer the init_boot.img into /sdcard and run magisk and ask it to patch that. Bring the patched file to your PC, and flash it to init_boot partition like the guide says. At that point, you should be able to boot back into the system and root should be good.

I did not disable Magisk modules and it worked fine. I have magiskhide props, shmiko, systemless hosts, zygisk - lsposed, universal safety net fix.

If you have trouble with Magisk modules, you can recover by booting into Safe Mode (restart and press down volume and keep it pressed). Magisk detects the Safe Mode and disables the modules. Done that many times.
[Google Pixel 7 Pro] Freak07:
in the end it doesn´t matter how you do it.

Flashing the complete firmware with -w removed or using the web flasher might be easier as it´s kind of a one click solution.

However simply flashing entire november firmware, might not get you out of the avb corruption loop. It might but, but it might not depending on what went wrong. If it´s the bug that I think it is, avb gets cleared when flashing an older outdated init_boot.img.

You can try to just flash the entire nov firmware with any of the methods suggested. If it doesn´t clear the avb corruption bug, flash back older init_boot from oct firmware, followed by current init boot as I originally suggested.
[Google Pixel 7 Pro] Pritster5:
Ok so I did this part:

"I know this sounds a bit counter intuitive, but download october factory image, extract init_boot.img, flash it via fastboot on your device with nov firmware.

fastboot flash init_boot init_boot.img

Try to let it boot, if it fails or crashes go back to bootloader via long press power and volume down. (can take up to 30 seconds on p7pro)

If it boots already don´t forgot to flash init_boot from november firmware still."

And it works, however when I go to "About Phone" the build number is still the October version. Is this expected, given that I flashed the october init_boot.img onto a phone with November firmware? Or did my phone perhaps reboot into the older partition which the phone ran before switching to the inactive slot?

EDIT: Even after flashing the november init_boot.img after temporarily reverting to the october init_boot.img, it's still showing that I have build TD1A.220804.031 installed.
[Google Pixel 7 Pro] Pritster5:
"followed by current init boot as I originally suggested."

Should I reboot back into fastboot mode again to do this?

Thank you guys so much for the help so far btw, I'm already back up and running and just need to finish the steps you mentioned.
[Google Pixel 7 Pro] Pritster5:
@devsk Here are the logs you wanted:
[Google Pixel 7 Pro] Lughnasadh:
There are a couple of issues open regarding Magisk, devices shipping with A13, restoring/patching the init_boot.img, and installing to inactive slot.

Magisk wants to patch boot part instead of init_boot on devices that ship A13 · Issue #6380 · topjohnwu/Magisk

Device: Pixel 7 Global Android version: 13 (comes with A13 and therefore used init_boot) Magisk version name: latest debug Magisk version code: 25205 On devices that ship with A13 (pixel 7 for now)...

github.com

Magisk won't backup init_boot.img · Issue #6378 · topjohnwu/Magisk

Device: Pixel 7 Android version: 13 Magisk version name: cf9957c Magisk version code: 25205 I'm using the latest version of Magisk on my pixel 7 and everything works fine. However, there is a small...

github.com
[Google Pixel 7 Pro] viper8u2:
wish I would have saw this yesterday, I got the corrupt message also by doing the manual download method (editing flash-bat to remove -w, adding disable verity and disable verification settings.

I put phone in recovery (volume down and power) and did the android flash and it appeared to work but same corrupt message

I ended up doing the reset and spent all night redoing phone..... I had this happen on my P6P also and went back to only doing android flash and never had an issue after that
[Google Pixel 7 Pro] Bofahad:
Your mobile is dead , you have to replace the motherboard.
[Google Pixel 7 Pro] Pritster5:
Hmm interesting. I was able to get back to a fully functional state by flashing an older (October) version of init_boot.img
[Google Pixel 7 Pro] Bofahad:
Sorry i thought your Bootloader is locked 🔒 , with unlocked bootloader you can do alot of things 🔓
[Google Pixel 7 Pro] devsk:
I don't see the logs attached. Did you forget to attach?
[Google Pixel 7 Pro] Freak07:
init_boot doesn´t contain the props that set the security patch state iirc. so flashing it won´t change the security patch date you see in settings.

Maybe the OTA wasn´t successful, silently failed in the background and you´re still on October. Or your device switched slots.

I´d just flash november firmware via either web tool or factory image. :) Check the guides in this forum, you´ll find it :)
[Google Pixel 7 Pro] Lughnasadh:
I also wonder if this didn't happen. As far as I know, when you "Restore images" in Magisk, it isn't restoring the stock init_boot.img, therefore you remain rooted and subsequently the OTA should fail. I've seen a few users who had the OTA fail after using the "Restore images" function, but afterwards flashed the stock init_boot.img manually and then took the OTA with success.
[Google Pixel 7 Pro] Pritster5:
Hmm I flashed the stock November init_boot.img and I'm failing to take the OTA (and I no longer have root)
[Google Pixel 7 Pro] simplepinoi177:
November or October?

Because if you're on November, then what OTA would it be updating? Unless you're attempting to update more than just the init_boot.img OTA and you're just trying to dirty flash over any glitches the unorthodox OTA updating you've been implementing thus far....

Also, if you're attempting to do the OTA using the System Update, and you're already on November, then of course it'd fail; but I assume you mean sideloading the OTA....

Is it still possible to sideload & apply OTA's in Recovery?

If so, maybe OP should consider doing that...
[Google Pixel 7 Pro] Pritster5:
I was following Freak07's steps which recommended first flashing the October one, which fixed the bootloop, and then flashing the November one anyway. I'm currently on the November init_boot.img
[Google Pixel 7 Pro] Pritster5:
Weird, it shows the file as attached in preview but wont show it when I actually reply. Trying again:
[Google Pixel 7 Pro] Pritster5:
Well I lost root so idk what boot image I have now. Since I can access adb, I'm just going to do a full factory image flash/dirty flash without wiping.
[Google Pixel 7 Pro] Lughnasadh:
Sometimes .txt files don't show up so try zipping it up and posting that.
[Google Pixel 7 Pro] Pritster5:
Trying one last time:
[Google Pixel 7 Pro] K1nsey6:
Using Magisk 'install to inactive slot' patches then restores the BOOT image. Pixel needs a patched init_boot image, that must be done from bootloader
[Google Pixel 7 Pro] Pritster5:
Ok, I got it working via the following steps:

1. Flash Stock October build init_boot.img via PC over fastboot mode. (When OTA + Magisk Inactive Slot method for November update failed)

2. This fixed the bootloop but put me back on the Octoberbuild version. It also allowed me to use ADB and the Android Flash Tool.

3. Followed the guide here (I used the Android Flash Tool instead of the FAB script but everything else is the same): https://xdaforums.com/t/november-20...-pro-cheetah-safetynet.4502805/#post-87540339