yashsingh1/xdaforums huggingface dataset:
[Sony Xperia 5 II Questions & Answers] locoman103:
hi man.. plz can you help me i have sony xperia5ii sog02.. im in morroco my phone cant work with 4g until u restart the phone.. have you any idea how to modify the network.. or master codes.. or any thing to let the phone work normaly
[Sony Xperia 5 II Questions & Answers] khalilrehman17:
The normal process is to flash Modem Files from Global Rom. With this you will get proprer 4G and 4G+ signls and you can install Pixel IMS app for Volte and WOWIFI.

Its not a big issue anymore.
[Sony Xperia 5 II Questions & Answers] locoman103:
but it's possible flash modern from global version?.. can flash sony 5ii sog02 japan version?

and how to flash.?
[Samsung Galaxy S23] inklingtrex:
please help i need miui i have twrp and i rooted my samsung.
[Samsung Galaxy S23] corrifa:
Not possible. Sorry.
[Samsung Galaxy S23] dwensch:
Is this a joke?
[Samsung Galaxy S23] Bluetooth Tissue:
Afraid you're months, if not years too early for something like this
[Samsung Galaxy S23] wonsky21:
Not really.I remember I had a port of MIUI on my Samsung Galaxy S2 😁
[Samsung Galaxy S23] inklingtrex:
Thank you.
[Samsung Galaxy S23] inklingtrex:
No
[Samsung Galaxy S23] Bluetooth Tissue:
That's on the S2 though. We're talking about a phone that was released in Feb 2023. If I remember correctly, there's no MIUI port even from the S10 onwards.
[Samsung Galaxy S23] mino_ali:
WHY THE F*** DO YOU WANT MIUI??!

Its the worst firmware i ever seen
[Samsung Galaxy S23] corrifa:
I remember when I had my HTC HD2, that thing could run everything.....android (all kinds of skins), WP7, WM6.5.... sometimes its not about if you should but if you could

Haven't used MIUI in years but I remember it being smooth, and very bloated.
[Samsung Galaxy S23] mino_ali:
It was smooth and pretty but now things are deferent
[Samsung Galaxy S23] megumage:
Last time MIUI was semi-decent was 5+ years ago....you definetely don't want MIUI now
[Samsung Galaxy S23] chrisriveeraa:
MIUI is more beautiful and it's not that bad, I'm pretty sure you just say because of what people say, I came to S23 after using a Xiaomi 12 2 years and I miss it bad, nothing S23 can envy to that Xm12, and HK speaker was a lot better and one ui 5.1 is ugglier, the only good thing is the front facing camera bc back cameras are to saturated XD
[Android Head-Units] Hutch75:
am glad I found this site . I purchased an android head unit for my car and the main app I bought it to use in my car it says it won’t work in my device . I have tried to go the apk route but that won’t work and of course they won’t take it back . I know it’s running android 13 with armv7 cpu .
[Touch GSM General] ponde:
I dont know if this is only my "problem" but my screen is not so responsible when I am usin my fingers, I really have to PRESS like really hard, but when I am using my stylus or fingernails the screen is wery responsible.

sorry for my Englis and those writing foults
[Touch GSM General] Imyman:
Use the wiki. It's all there.

http://wiki.xda-developers.com/index.php?pagename=Touch_Sensitivity
[Touch GSM General] ponde:
thank you for fast response!
[Android Stick & Console AllWinner based Computers] itzthomas:
so are there any AOSP roms for Allwinner devices?
[Asus ROG Phone 7 / 7 Ultimate] williamtavares:
Could a good soul with A rooted phone extract the Asus launcher APK? 🥹

Reason: I want to install it in my rog 5. In this phone the icons are so small it hurts my eyes trying to look at them, there's no option to increase size, and I noticed they are much bigger in rog 7/Zenfone 10 series.

How it looks in my phone:

View attachment 6001155
[Asus ROG Phone 7 / 7 Ultimate] ericbajana:
Try using Nova launcher to have more options. Works well on my ROG7.
[Asus ROG Phone 7 / 7 Ultimate] williamtavares:
I don't want to. Make animations look laggy.
[Asus ROG Phone 7 / 7 Ultimate] williamtavares:
Got it and it works.

View attachment 6003973
[Xiaomi Redmi Note 4 Questions & Answers] Nhathere:
please someone do the xiaomi redmi note 4 nikel rom android 8 or 10 please i hate android 6,7 :(((
[Google Pixel 7a] jake.99x3:
Custom recovery has been built for Pixel 7a as a step towards decryption/custom recovery on Pixel 7 pro by member @Wishmasterflo It can be found here: https://github.com/Wishmasterflo/ofox_lynx The thread that lead to this being made can be found here : https://xdaforums.com/t/is-custom-recovery-possible-something-thats-being-worked-on.4532237/page-7 Unfortunately none of us have a 7a to test, just a 7 pro. This is a test build, at worst you will have to reset with web tool and lose data. Thanks!!
[Google Pixel 7a] BunkerBert:
after flashing this recovery device wont boot.

(Unlocked P7A / CalyxOs Rom)

if you have trouble after flashing this recovery please flash the stock vendor_boot.img
[Google Pixel 7a] Wishmasterflo:
OK got it. Thanks for checking. Then I know that this release is still not working. Will remove it again and check again some time in the future if there is more luck in getting that to work. Seems to be really a mess with the new Pixel devices to build that for. :cautious:
[Google Pixel 7a] BunkerBert:
Thx 4 your work
[Google Pixel 7a] Wishmasterflo:
OK I did a new build now, but I am not really sure if that will boot either now?

Perhaps not worth to upload and try now.

I guess I will give all that more time to perhaps get that booting some time in the future.

I think anyway the most difficult thing then will be to get decryption to work on our Pixel phones.
[Google Pixel 7a] Wishmasterflo:
I have a new Orangefox build from yesterday if someone wanna Test.
[Google Pixel 7a] binsentlangit6:
how to build?
[Google Pixel 7a] Wishmasterflo:
I have uploaded it here now if you wanna test and see if it boots.
[Google Pixel 7a] binsentlangit6:
is it for a13 or 14?
[Google Pixel 7a] Wishmasterflo:
A14
[Google Pixel 7a] gorm:
Still no boot.

Keep trying my friend.

Thank You for your efforts so far.
[Google Pixel 7a] Wishmasterflo:
Offff....ok.

I really thought I had found the issue, but then it seems to be something else.

Lets see if I can figure out that.
[Google Pixel 7a] binsentlangit6:
I hope you do! Thanks for your work!
[Google Pixel 7a] Wishmasterflo:
can you grab a dmesg log: adb shell dmesg > dmesg.log
[Google Pixel 7a] Wishmasterflo:
New Test build uploaded now.

download

Changed Kernel to BlueSpark Kernel (Android 14)

Added new build var to (hopefully) fix the Orangefox booting issue

Can someone test if this is booting up now. I really have hope that these changes have fixed that booting iussue now. :cowboy:
[Google Pixel 7a] binsentlangit6:
Still not booting. Stuck on google logo.

A telegram channel would help
[Google Pixel 7a] Sneeder:
@Wishmasterflo hey man did you gave up? Just asking, thanks for your effort in any case
[Google Pixel 7a] Wishmasterflo:
I am quite busy with other things the last weeks so have not done anything regarding Android stuff now. Also I just set up my Laptop with Arch linux and have to set up my build environment here again.
[Google Pixel 7a] Sneeder:
No problem, I was just curious 👌🏻
[Google Pixel 7a] macgealai:
We will all wait patiently, as this project is respected and necessary
[Google Pixel 7a] ianob:
I checked out the github and there's no releases, do I have to compile it myself or something?
[Google Pixel 7a] Wishmasterflo:
I removed them as they were not booting.
[Google Pixel 7a] d0udQu0i:
hi Wishmasterflo

on your GitHub https://github.com/Wishmasterflo/ofox_lynx

you tell you "OrangeFox-R11.1-Unofficial-lynx.zip" but i don't found it

or is it that...?

and after how i flash it?

thank's for your anwser

have a nice day
[Google Pixel 7a] Sneeder:
If I just boot from it like `fastboot boot yourrecovery.img` rather than `fastboot flash boot yourrecovery` is there still the risk to cause a bootloop once I try to do a full backup? Just for information
[Google Pixel 7a] Wishmasterflo:
Just booting it does not work on Pixel 7a. That works only on older phones which do not use vendor_boot as recovery etc.
[Google Pixel 7a] Wishmasterflo:
I had removed the build again as it is not booting.
[Google Pixel 7a] d0udQu0i:
hi @Wishmasterflo

is your project still in progress?

Commits · Wishmasterflo/ofox_lynx

Orangefox recovery for Google Pixel 7a (lynx). Contribute to Wishmasterflo/ofox_lynx development by creating an account on GitHub.

github.com

can i have a update on it?

thank's for your awnser

have a nice day
[Google Pixel 7a] Sneeder:
I think he moved on :( I hope I'm wrong tho
[Google Pixel 7a] Wishmasterflo:
I am quite busy with other things lately so have not checked further on that.
[Google Pixel 7a] T2100_BACK:
My friend has a Pixel 7a and really wants a custom recovery. It would be helpful if you could recompile. I'll ask him to make an XDA account to fix issues.
[Google Pixel 7a] Sneeder:
+1
[Google Pixel 7a] d0udQu0i:
hi @Wishmasterflo

do you have a clearer vision for the further development of “Orange fox custom recovery Pixel 7a”?

how can I help you?

if you agree, i'm willing to make a donation for a stable version, really !

thank's for your awnser

have a nice day
[Google Pixel 7a] Wishmasterflo:
Hi!

No not really right now.

Also have not checked so much further on that recently as I was busy with other things and updating my Orangefox Version for my Oneplus devices and building Orangfox for a Lenovo Tablet.

I can do another build of Orangefox recovery for Pixel 7a with all the latest changes, but since I have not changed anything huge in the device tree I have not big hope that it will boot now.

And even if I get a booting and running Version of Orangefox for the Pixel 7a, it will not be able to decrypt the Data partition (as I understand it, it is impossible to do that on the phones with the Google Tensor Chipset) so a running Orangefox without the ability to decrypt the data partition is a bit meaningless then and perhaps not really worth the effort in trying to get it to boot up.
[Google Pixel 7a] d0udQu0i:
hi @Wishmasterflo

OK i understand better now

i didn't know that the data partition was encrypted

thank you for details

good continuation

bye
[Google Pixel 7a] Wishmasterflo:
I have just updated the Kernel to the latest Version and added some more logging etc to my device tree.

Will do a new build now.

Lets see if we can get some more information from the log why it is not booting up.
[Google Pixel 7a] Wishmasterflo:
OK I did a new updated Test build for Google Pixel 7a. Download

If it just hangs at Google logo, try to get logs with the below commands:

adb shell dmesg > dmesg.log

adb shell logcat -d > logcat.log

Thanks!
[Google Pixel 7a] RAZINARES:
I installed it using the vendor_boot image, and it booted, but the screen touch is not working
[Google Pixel 7a] Wishmasterflo:
Ohh cool, that is good news at least.

Can you try to grab the recovery.log file from /tmp and send it to me.

On which OS/ROM and which Android security Patch is your phone?
[Google Pixel 7a] RAZINARES:
How can i access the logs?

I am using

cRdroid Android 14 May security update
[Google Pixel 7a] Wishmasterflo:
OK thanks.

If you connect the phone to your computer open cmd and do a adb pull /tmp/recovery.log
[Google Pixel 7a] RAZINARES:
Can't access adb from orangefox recovery
[Google Pixel 7a] Wishmasterflo:
Hmm oh ok. Let me check. I might have an idea how to get that all fixed and working.

Will check on that later.
[Google Pixel 7a] d0udQu0i:
hi @Wishmasterflo

thank you for resuming the development

good luck

(we're counting on you) 😜

for support you, where is the link to make a donation?

bye
[Google Pixel 7a] Wishmasterflo:
Yeah, thanks. :)

There is a Paypal donate link in my Signature here on XDA.

I am just building and uploading soon a new Version.

I guess I found the issue with touch not working.
[Google Pixel 7a] Wishmasterflo:
OK I have rebuilt Orangefox now and a new Version is uploaded.

Can you or someone else check how this Version works and if Touch screen is working now.
[Google Pixel 7a] RAZINARES:
Still not working
[Google Pixel 7a] Wishmasterflo:
Yes. i have added some more things which were missing for that but had not the time yet to build a new Test release.

Today I am not at home until late in the evening so a new build will hopefully come tomorrow.

Also now since we have at least a booting Version I am quite sure that I will fix a lot of the existing issues like touch and usb not working in the next days.

Then I will enable decryption again to see what Orangefox does do or try there but I am quite sure if that will work on the new Pixel devices with the Google Tensor chip.

And a big thanks to all for the Paypal donations.

Much appritiated. :)
[Google Pixel 7a] Wishmasterflo:
OK I have built and uploaded a new Orangefox Version now.

Can someone check if Touch screen is working now in Orangefox.

DOWNLOAD
[Google Pixel 7a] RAZINARES:
Tried this, and still same :/
[Google Pixel 7a] Wishmasterflo:
Ok hmm intressting.

I thought what I added should have solved the issue.

Have you flashed Orangefox to both alots or only one?

I guess when using the fastboot flash recovery method it will as standard only flash to the active slot.

If you sideload it from recovery the zip file it should flash to both slots.

Just to check if that makes any difference.

EDIT: OK I found something more what I missed, so will add that now to my device tree and do a new build...
[Google Pixel 7a] Wishmasterflo:
OK I have built and uploaded a new Version again now. Download
[Google Pixel 7a] blade1500:
the touchscreen isnt working
[Google Pixel 7a] Wishmasterflo:
OK thanks for checking.

I will have to figure out what more is missing there to get that working now.

EDIT: OK hope I got it now. Have added the Touch Firmware and drivers directly into the device.mk file now.
[Google Pixel 7a] blade1500:
Ok m8 keep up the good work 😀
[Google Pixel 7a] Wishmasterflo:
OK I have rebuilt and reuploaded a new Version again.

Can someone check if Touch screen is working now.
[Google Pixel 7a] blade1500:
nope not working for mw still no touch screen controls
[Google Pixel 7a] Wishmasterflo:
Ufff, hmm. Strange. Have to check, I have no clue why it des not work now.

And I guess USB connection is still broken as well or?

Otherwise can you try to grab the recovery.log file from /tmp and send it over?

EDIT: OK lets see. I have added some more things which will hopefully get USB to work so that I can get some log files. I guess that would help a lot in order to find the issue now. I will do a new build tomorrow.
[Google Pixel 7a] blade1500:
Yh ok I will get it for u tomorrow as got be up for work soon
[Google Pixel 7a] Wishmasterflo:
Yes thanks a lot.

Check if adb is working.

If you do adb devices from a cmd prompt you should get an output with the device id and mode like recovery.

Then it should be possible to do a adb pull /tmp/recovery.log
[Google Pixel 7a] blade1500:
Ok m8 I'll do it when I get in from work
[Google Pixel 7a] Wishmasterflo:
Yes thanks.

I will also build a new Version after work today.

I recognized that I had commented out a line in the device config file for Touch Firmware by mistake...
[Google Pixel 7a] blade1500:
Oh so if u fix that touch should work hopefully
[Google Pixel 7a] Wishmasterflo:
OK new Version is uploaded now.
[Google Pixel 7a] blade1500:
i will test this when my phone has a bit of charge on it
[Google Pixel 7a] blade1500:
Adb and touch screen doesnt work
[Google Pixel 7a] Wishmasterflo:
OK, now I might have an idea what I need to do to fix that, but that will take some time.

Will check further on this in the next days when I have a bit more time.
[Google Pixel 7a] blade1500:
Ok

Ok just let me no and if I need anything for me to test I will
[Google Pixel 7a] d0udQu0i:
hi @Wishmasterflo

thank's for all this build version

i'm not in the field but I'm thinking of a tip

is it possible to compare a version of OrangeFox Recovery in which touch and adb work and apply it to the version currently being developed?

or is it more complicated...

good luck with the next versions

bye
[Google Pixel 7a] Wishmasterflo:
The thing is that there is no custom recovery for the Google Pixel 7 series with which I can compare that with.

Now I have added the Touchscreen drivers etc directly into my device tree.

Lets see if that makes any difference now.

New Version is uploaded, please check if anything has changed now regarding Touch and USB.

Also I just wonder if it would be easier to communicate via Telegramm chat, its much more easy there instead of posting here for every new build. :cool:
[Google Pixel 7a] Wishmasterflo:
Hello!

Has someone tried how the new uploaded Version behavs now in regards of touch screen and adb ?

Thanks!
[Google Pixel 7a] dcarvil:
I installed it with "fastboot flash vendor_boot OrangeFox-R11.1-Unofficial-lynx.img", then did "fastboot reboot recovery".

The touch screen still does not respond to anything.

Thanks for your work on this.
[Google Pixel 7a] dcarvil:
adb seems to be working, though. Here is the recovery.log.
[Google Pixel 7a] Wishmasterflo:
Ah great. Thanks a lot. That helps a lot. I found some more hints to fix. Will do that tomorrow and provide a new Test build. Thanks for your testing. :)

(y)

Can you also send a dmesg log file: adb shell dmesg > dmesg.log

If you do adb shell and then type the below:

modprobe|goodix_brl_touch.ko
modprobe|focal_touch.ko

What is the output of that and does that perhaps enable the Touch screen??
[Google Pixel 7a] dcarvil:
More info:

Those two modules are in /vendor/lib64, but they aren't loaded, and I haven't figured out how to load them. I'm really off to bed this time.

1|lynx:/tmp # ls /vendor/lib64/*touch*

/vendor/lib64/focal_touch.ko /vendor/lib64/goodix_brl_touch.ko

1|lynx:/tmp # modprobe -d /vendor/lib64 goodix_brl_touch.ko

modprobe: LoadWithAliases was unable to load goodix_brl_touch.ko

modprobe: Failed to load module goodix_brl_touch.ko: No such file or directory

1|lynx:/tmp # ls /vendor/lib64/*touch*

/vendor/lib64/focal_touch.ko /vendor/lib64/goodix_brl_touch.ko

lynx:/tmp # modprobe /vendor/lib64/goodix_brl_touch.ko

modprobe: No module configuration directories given.

Usage:

modprobe [options] -d DIR [--all=FILE|MODULE]...

modprobe [options] -d DIR MODULE [symbol=value]...

Options:

--all=FILE: FILE to acquire module names from

-b, --use-blocklist: Apply blocklist to module names too

-d, --dirname=DIR: Load modules from DIR, option may be used multiple times

-D, --show-depends: Print dependencies for modules only, do not load

-h, --help: Print this help

-l, --list: List modules matching pattern

-r, --remove: Remove MODULE (multiple modules may be specified)

-s, --syslog: print to syslog also

-q, --quiet: disable messages

-v, --verbose: enable more messages, even more with a second -v
[Google Pixel 7a] Wishmasterflo:
OK great. Thanks a lot. I will try to figure out what more needs to be added to the device tree now and try to fix that.

Will do a new build when that is done.
[Google Pixel 7a] Wishmasterflo:
Hello!

OK I have set now the keymaster decryption so that it will try to decrypt data.

Just want to check if it still boots up and if it shows the pin/pattern to enter the decryption pattern/pin.

Download

So would be intressting to see how this behavs now.

Also please grab a dmseg.log and the recovery.log

Thanks!
[Google Pixel 7a] dcarvil:
The download site has only source code, no zip nor img.
[Google Pixel 7a] Wishmasterflo:
I just reuploaded a new build.

You can download it now.
[Google Pixel 7a] dcarvil:
There is no screen to enter a pin/pattern. It displays the logo, then a file management screen. The touchscreen is still not working, so I can't go any further.

I think the problem with modprobe is this error message.

"modprobe: No module configuration directories given."

xfx:~/oldhome/Phone/Pixel7a $ adb shell modprobe -l -v -v

mode is 2

mod_dirs is:

modules is:

module parameters is:

Usage:

modprobe [options] -d DIR [--all=FILE|MODULE]...

modprobe [options] -d DIR MODULE [symbol=value]...

Options:

--all=FILE: FILE to acquire module names from

-b, --use-blocklist: Apply blocklist to module names too

-d, --dirname=DIR: Load modules from DIR, option may be used multiple times

-D, --show-depends: Print dependencies for modules only, do not load

-h, --help: Print this help

-l, --list: List modules matching pattern

-r, --remove: Remove MODULE (multiple modules may be specified)

-s, --syslog: print to syslog also

-q, --quiet: disable messages

-v, --verbose: enable more messages, even more with a second -v

modprobe: No module configuration directories given.

xfx:~/oldhome/Phone/Pixel7a $

Logs attached.

Thanks again.
[Google Pixel 7a] Wishmasterflo:
OK great.

Guess I got it now. This log looks more promising.

Now I see that module files are getting loaded.

So I need to add the touch module files etc to the BoardConfig with TW_LOAD_VENDOR_MODULES.

Will do that now and upload a new build then.
[Google Pixel 7a] Wishmasterflo:
OK new Release is uploaded now.

Lets see if the Touch screen is working now. :)
[Google Pixel 7a] dcarvil:
Sorry, touch screen still not working, and no screen to enter pin/pattern.

I was able to get rid of the "modprobe: No module configuration directories given." by adding "-d /vendor/lib64" to the modprobe command.

xfx:~/oldhome/Phone/Pixel7a $ adb shell modprobe -l -v -v -d /vendor/lib64

mode is 2

mod_dirs is: /vendor/lib64

modules is:

module parameters is:

xfx:~/oldhome/Phone/Pixel7a $

I still can't list or load modules, though. At least I get a different error.

xfx:~/oldhome/Phone/Pixel7a $ adb shell modprobe -v -v -d /vendor/lib64 focal_touch

mode is 0

mod_dirs is: /vendor/lib64

modules is: focal_touch

module parameters is:

modprobe: LoadWithAliases was unable to load focal_touch

modprobe: Failed to load module focal_touch: No such file or directory

xfx:~/oldhome/Phone/Pixel7a $ adb shell modprobe -v -v -d /vendor/lib64 focal_touch.ko

mode is 0

mod_dirs is: /vendor/lib64

modules is: focal_touch.ko

module parameters is:

modprobe: LoadWithAliases was unable to load focal_touch.ko

modprobe: Failed to load module focal_touch.ko: No such file or directory

xfx:~/oldhome/Phone/Pixel7a $
[Google Pixel 7a] dcarvil:
Forgot the logs.
[Google Pixel 7a] Wishmasterflo:
Hmm ok thanks.

The module files are in /vendor/lib/modules now.
[Google Pixel 7a] dcarvil:
The goodix_brl_touch.ko and focal_touch.ko are still not being loaded.

xfx:~/oldhome/Phone/Pixel7a $ adb shell lsmod | grep touch

touch_bus_negotiator 20480 0

touch_offload 28672 0

xfx:~/oldhome/Phone/Pixel7a $

I'm still not able to load them using the /vendor/lib/modules directory.

xfx:~/oldhome/Phone/Pixel7a $ adb shell modprobe -v -v -d /vendor/lib/modules focal_touch.ko

mode is 0

mod_dirs is: /vendor/lib/modules

modules is: focal_touch.ko

module parameters is:

modprobe: LoadWithAliases was unable to load focal_touch.ko

modprobe: Failed to load module focal_touch.ko: No such file or directory

The files do exist, but modprobe cannot find them.

xfx:~/oldhome/Phone/Pixel7a $ adb shell ls -l /vendor/lib/modules/*touch*

-rw-r--r-- 1 root root 579433 1970-01-01 00:00 /vendor/lib/modules/focal_touch.ko

-rw-r--r-- 1 root root 531873 1970-01-01 00:00 /vendor/lib/modules/goodix_brl_touch.ko
[Google Pixel 7a] Wishmasterflo:
OK, I will do a new build tomorrow.

From another device tree with loading these touch drivers, I saw that they are there in a directory

/vendor/lib/modules/1.1

Will test that tomorrow and do a new build.

Otherwise I will try this and put that in the runatboot.sh file
[Google Pixel 7a] dcarvil:
Ok, thanks.

I find it interesting that "modprobe -l" does not produce any results, but lsmod does.

modprobe comes from toolbox, but lsmod comes from toybox. I am beginning to wonder if there is something wrong with the modprobe implementation in toolbox.
[Google Pixel 7a] Wishmasterflo:
OK. I took a look into the source code of the recovery where it loads the vendor modules.

As I see it there for vendor_boot devices (which the Pixel 7 series is) the modules needs to be in /lib/modules instead of /vendor/lib/modules.

Will check that out now.

Now I have also time and will unlock my Pixel 7a so that I can boot and test Orangefox recovery there.

That will all be much faster in testing etc. :)