yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7a] MasonJames1988:
Hi @Wishmasterflo

I used your orangefox recovery on my old OnePlus 8 Pro, not sure if you remember me from the OnePlus test group on TG.. I'm just wondering if you could do one for the Pixel 8 Pro? Sorry for jumping on the 7a thread, thought I'd ask in case
[Google Pixel 7a] Wishmasterflo:
Hello!

First I want to get everything working on the Pixel 7a before I build it for any other Pixel devices.

I was a bit busy with other things here the last days so have not checked further on fixing the current issues.
[Google Pixel 7a] MasonJames1988:
No worries at all and thank you for your response. Fingers crossed you get everything working for the 7a. Looking forward to using your work again
[Google Pixel 7a] Wishmasterflo:
Yea, I will check further on that soon again.

Right now I have reflashed and relocked my Pixel 7a again with a custom ROM and custom avb-keys and wrote a small script to handle OTA updates and flash it to the phone as well as unroot the OTA again and flash it.

I also did a option to replace the vendor_boot directly with Orangefox recovery as the avbroot tool has an option to replace whole partition images but have not test out if that really works now.

Otherwise I need to unblock my bootloader again to flash and test new Orangefox releases but will check further on that.
[Google Pixel 7a] blade1500:
If you need any testers let me know and I will help as my bootloader is unlocked
[Google Pixel 7a] MasonJames1988:
And this is why you are a legend! That's absolutely awesome stuff right there. Reminds me of the dualboot mod you did
[Google Pixel 7a] Wishmasterflo:
Like this...

EDIT: OK now as I have my OTA Patcher almost working and done I can continue with Orangefox recovery things for Pixel 7a. :)
[Google Pixel 7a] d0udQu0i:
ho @Wishmasterflo

any news on the state of progress?

thank's

good luck
[Google Pixel 7a] Wishmasterflo:
No. Still trying to get touch screen working now.

Was also a bit busy with other things the last days so have not done so much more investigation regarding that recently.
[Google Pixel 7a] MilanKK:
what file stands for this recovery? cuz i wanna flash it on my pixel 7a.
[Google Pixel 7a] Wishmasterflo:
I have removed the downloads again and just doing a new build because touch screen is still not working in recovery now and the color pixel format is not correct so trying to get that fixed now.

EDIT: OK still no luck with that now. I will continue to check on that the next days!
[Google Pixel 7a] Wishmasterflo:
Just wonder, was it for you as well that the colors of the Orangefox logo and GUI are blue instead of Orange by default?
[Google Pixel 7a] dcarvil:
I'm pretty sure they were blue. I didn't keep the .img file, so can't reinstall to verify that.
[Google Pixel 7a] Wishmasterflo:
Yes no problem.

OK now at least I made some progress in the loading modules thing. Had to att the loading of modules into a runatboot script and add some more copying of files to the device tree.
[Google Pixel 7a] Wishmasterflo:
@dcarvil OK might be that I have fixed the issie with module loading now.

Now I just get an error when loading the module file regarding key was rejected and I assume it is due to the fact that tried that on a custom rom with self signed avb keys on locked bootloader.

So if I upload a new build later today can you try it out?
[Google Pixel 7a] dcarvil:
Yes, I can try it. I am on the stock Google ROM. Thanks.
[Google Pixel 7a] Wishmasterflo:
OK will do a rebuilt now.
[Google Pixel 7a] Wishmasterflo:
OK thanks.

I have uploaded a new build now.

I will do another change now but would be intressting to know if touch works in this build for you now.
[Google Pixel 7a] dcarvil:
Sorry, touch is still not working. The touch modules are not being loaded.

xfx:~/oldhome/Phone/Pixel7a $ adb shell

lynx:/tmp # lsmod | grep touch

touch_bus_negotiator 20480 0

touch_offload 28672 0

lynx:/tmp # ^D

The logo color is blue, and there is no screen to enter a PIN.

Logs attached.

Anything else I can try?

Thanks for the effort.
[Google Pixel 7a] Wishmasterflo:
Hmmm ok.

What is the output of this:

modprobe -d /vendor/lib/modules/1.1 focal_touch
[Google Pixel 7a] dcarvil:
xfx:~/oldhome/Phone/Pixel7a $ adb shell

lynx:/tmp # modprobe -d /vendor/lib/modules/1.1 focal_touch

Loading module /vendor/lib/modules/1.1/focal_touch.ko with args ''

modprobe: Failed to insmod '/vendor/lib/modules/1.1/focal_touch.ko' with args '': Exec format error

modprobe: LoadWithAliases was unable to load focal_touch

modprobe: Failed to load module focal_touch: Exec format error

1|lynx:/tmp #
[Google Pixel 7a] Wishmasterflo:
Hmm intressting. You getting another error than I get now.

I get an error like failed to load module focal_touch: Key was rejected by service

EDIT: OK I guess I know what the issue is now. Seems to be that the Kernel Version with which the modules got build does not match the Kernel Version of the Kernel I use when building.
[Google Pixel 7a] dcarvil:
A google search of my error message turned up this, among other things:

What is "Exec format error"?

I'm running Ubuntu Budgie 20.10 on a MacBook Pro 12.1 and while trying to get the built-in camera working (using this and this) I got this error message: modprobe: ERROR: could not insert 'facetime...

askubuntu.com

Here are the logs after running that modprobe. Looks like selinux is denying the module install.
[Google Pixel 7a] Wishmasterflo:
I guess the issue might have been that the kernel modules in my device tree were not exactly from the same Kernel build as the ones in the Kernel I build from.

So now I copied over them so that I am sure they are the same.

Will do a new build now.
[Google Pixel 7a] Wishmasterflo:
OK I have uploaded a new build now.

Can you check if it is any difference in that now regarding touch screen.
[Google Pixel 7a] dcarvil:
That loads additional modules, but touch screen still does not work.

xfx:~/oldhome/Phone/Pixel7a $ adb shell

lynx:/tmp # lsmod | grep touch

focal_touch 282624 0

touch_bus_negotiator 20480 1 focal_touch

touch_offload 28672 1 focal_touch

heatmap 20480 1 focal_touch

lynx:/tmp # ^D
[Google Pixel 7a] dcarvil:
FYI, I'll be going offline for the day in about an hour. I can delay a bit if you expect to have a new build soon.

Thanks for your continued effort on this.
[Google Pixel 7a] Wishmasterflo:
Ok no problem.

I guess I will try this another way now.

So instead of using the prebuilt Stock Kernel I will build a kernel from source and include the touchscreen drivers directly there instead of trying to load them via modules.

I think that might be a more promising solution.
[Google Pixel 7a] macgealai:
A golden God, ladies and gentlemen.... Thank you for your service, Sir. I don't have two dimes to rub together for warmth, but the necessity for this group to recompense this man is true and high. Wishmasterflo, you fukkin rock!
[Google Pixel 7a] Wishmasterflo:
Yeah thanks.

From next week on I will have 3 weeks vacation so I will have more time for all this.

Also got a bit of help regarding Orangefox building and another person is doing the same things for Pixel 7 Pro now.

Hope to have some more success in the next days.
[Google Pixel 7a] MilanKK:
ok thanks
[Google Pixel 7a] Wishmasterflo:
OK that was not working as I thought to build with a custom Kernel.

I changed back to the prebuilt Kernel now and have updated the prebuild Kernel and Kernel Modules to July 2024 ones.

New Test Version is uploaded here.

If Touch is still not working now please sent the output of:

modprobe -d /vendor/lib/modules/1.1 focal_touch
[Google Pixel 7a] dcarvil:
Touch still not working.

xfx:~/oldhome/Phone/Pixel7a $ adb shell

lynx:/tmp # modprobe -d /vendor/lib/modules/1.1 focal_touch

Loading module /vendor/lib/modules/1.1/focal_touch.ko with args ''

modprobe: Failed to insmod '/vendor/lib/modules/1.1/focal_touch.ko' with args '': Exec format error

modprobe: LoadWithAliases was unable to load focal_touch

modprobe: Failed to load module focal_touch: Exec format error

1|lynx:/tmp #

I'll be going offline in a few minutes. Will be back tomorrow.
[Google Pixel 7a] Wishmasterflo:
OK thanks.

Just wonder do you have the issue as well when you have flashed Orangefox recovery that the phone will not boot to the ROM anymore? (on my device it just reboots again after a while when on the ROM boot logo)

Lets see, I hope I found the issue now, and then all that extra script and load stuff for the modules is not needed anymore.

Seems that it did search for the modules load file in another directory than I thought so it never used my adjusted module_load file with the touch screen modules in it.

I have adjusted that now.

Let me check if that works now here. :)
[Google Pixel 7a] dcarvil:
Yes, it will not boot to the ROM until I flash the stock vendor_boot image.
[Google Pixel 7a] Wishmasterflo:
OK.

Hmmm ok all the things that I thought would be the root cause of this did not work now.

I tried like 6 different things now and rebuilt Orangefox but no luck in getting the touch modules to load.

Now I need some break to think further what to do next.

Will continue with that later tonight or tomorrow.
[Google Pixel 7a] LeeGarChat:
Dude, are you sure everything is fine with the ramdisk setup?
[Google Pixel 7a] Wishmasterflo:
Hi

Hmm ok. No I am not sure as this is the first device with vendor_boot_as_recovery I have build Orangefox recovery for.

Also the Pixel devices seem to be a bit more special.

What exactly are your thoughts? That there are things missing in the first_stage_ramdisk or??
[Google Pixel 7a] LeeGarChat:
that ramdisk can't be opened correctly in MT manager. for example the first video is unpacked ramdisk.cpio in compressed original lz4, and r.cpio is its decompression. as you can see the file structure is displayed incorrectly, besides for some reason it was possible to open compressed ramdisk.cpio. in the second case it is my ramdisk.cpio and r2.cpio (decompressed) from vendor_boot pixel 8. I didn't download the original from pixel 7a because there is no point, I had many different devices and I unpacked many different ramdisks. pixel 8 is just an example, your ramdisk.cpio is assembled somehow incorrectly not in terms of file structure, but in terms of correctness of packing
[Google Pixel 7a] LeeGarChat:
here for example the same actions in ubuntu
[Google Pixel 7a] Wishmasterflo:
Hmm. I dont know. I mean its packed from the Orangefox build process so I dont think that there is anything wrong with it.

Alsi its booting up etc its just that some modules dont get loaded and I dont think that has anything to do with the packeging .
[Google Pixel 7a] LeeGarChat:
This may be related to Android booting, since some files are loaded from vendor_boot when the kernel starts, the same first_stage
[Google Pixel 7a] Sneeder:
@Wishmasterflo aside from the touchscreen issue did you have the chance to test if the actual backup/restore part works properly? Like using an usb otg mouse or whatever to temporarily bypass the touch bug.
[Google Pixel 7a] Wishmasterflo:
No that does not work as data decryption is not working!

Also I guess getting that to work is much more complicated.
[Google Pixel 7a] Sneeder:
Doesn't the encryption get bypassed by disabling the lock screen?
[Google Pixel 7a] Wishmasterflo:
But then you cant acces the /data partition. Its needs to get encrypted.
[Google Pixel 7a] Sneeder:
I don't know if that's still the case but I remember Android 12 having already the encryption thing on and by disabling the lock screen you could make a full backup, /data included
[Google Pixel 7a] Wishmasterflo:
OK wow, finally at least I made some progress here after adding this to the Boardconfig.mk file:

TW_LOAD_VENDOR_MODULES := "focal_touch.ko goodix_brl_touch.ko goog_touch_interface.ko"

and then via a runatboot script copy over the touch module files from /tmp/vendor/lib/modules to /lib/modules I can see now in the log that Orangefox is loading the touch module files.

Just for one of them there is in error, I guess due to some selinux stuff.

Trying to fix that now. :)

07-14 13:03:41.970 312 312 I recovery: Loaded kernel module /vendor/lib/modules/goodix_brl_touch.ko

07-14 13:03:41.971 312 312 I recovery: Loading module /vendor/lib/modules/focal_touch.ko with args ''

07-14 13:03:42.004 312 312 I gtd : GTP: Debug tools miscdev register success

07-14 13:03:42.005 312 312 I gtd : GTP: goodix_ts_probe: goodix_ts_core probe success

07-14 13:03:42.005 222 222 I alsa : aoc_snd_card_probe

07-14 13:03:42.005 222 222 I alsa : aoc_snd_card_probe: wait for aoc output ctrl

07-14 13:03:42.007 341 341 I gtd : GTP: rom_pid:BERLIN

07-14 13:03:42.007 341 341 I gtd : GTP: rom_vid:02 00 04

07-14 13:03:42.007 341 341 I gtd : GTP: pid:9895

07-14 13:03:42.007 341 341 I gtd : GTP: vid:1f 00 00 21

07-14 13:03:42.007 341 341 I gtd : GTP: sensor_id:255

07-14 13:03:42.007 341 341 I gtd : GTP: cfg_bin_name:goodix_cfg_group.bin

07-14 13:03:42.009 341 341 I SELinux : Context u:eek:bject_r:vendor_fw_file:s0 is not valid (left unmapped).

...

07-14 15:23:41.129 339 339 I gti.0 : goog_touch_interface_probe: device create "gti.0".

07-14 15:23:41.129 339 339 I gti.0 : offload.caps: data_types 0x1b, scan_types 0xc0, context_channel_types 0x0.

07-14 15:23:41.129 339 339 I touch_offload_init: touch_offload.

07-14 15:23:41.129 339 339 I gti.0 : offload.caps: display W/H: 1080 * 2400 (Tx/Rx: 16 * 34).

07-14 15:23:41.129 339 339 I gti.0 : offload ID: "l100" / 0x3030316C, offload_enabled=1.
[Google Pixel 7a] Wishmasterflo:
Hello!

OK I have uploaded a new Test Version here.

From the log I can see that it is loading the touch drivers now, but I see some selinux denial in the logcat.

Also it seems that the whole recovery is just hanging then, I can not even turn off the screen when pushing the power button, but still adb etc is working. Hmmm

I just want to have someone else checked if the issues are the same or if it is working for someone?

Perhaps I just have those issues due to my locked down ROM and Kernel I use?

I see this selinux error in the log which seems to be related to Touch screen firmware:

SELinux: Context u:eek:bject_r:vendor_fw_file:s0 is not valid (left unmapped)

I guess we can try with selinux denials resolver to fix this issue perhaps.
[Google Pixel 7a] kodycdrews:
I can definitely help test! And just to confirm, I can just flash the stock vendor_boot once I'm done testing, correct?
[Google Pixel 7a] Wishmasterflo:
Yes correct. Thanks!
[Google Pixel 7a] dcarvil:
Touch screen still not working. These modules are loaded.

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

focal_touch 282624 0

goodix_brl_touch 258048 0

goog_touch_interface 106496 1 goodix_brl_touch

touch_bus_negotiator 20480 2 focal_touch,goog_touch_interface

touch_offload 28672 2 focal_touch,goog_touch_interface

heatmap 20480 2 focal_touch,goog_touch_interface

systrace 16384 7 goodix_brl_touch,goog_touch_interface,exynos_acme,pixel_metrics,exynos_devfreq,exynos_dm,gs_acpm

Logs attached.

Thanks for continuing work on this.
[Google Pixel 7a] kodycdrews:
My apologies, but what's the best way to take a log that will help you? I tried copying a couple lines that you shared a few posts ago, and here's what I got:

modprobe: LoadWithAliases was unable to load focal_touch

modprobe: Failed to load module focal_touch: No such file or directory
[Google Pixel 7a] Wishmasterflo:
adb pull /tmp/logcat.log
[Google Pixel 7a] Wishmasterflo:
OK thanks. I think the solution is to get this selinux thing solved:

SELinux: Context u:eek:bject_r:vendor_fw_file:s0 is not valid (left unmapped)

EDIT:

OK I have run the log through the selinux denials resolver now and got an output with resolved denials.

Will try to implement those in my recovery and do a new Orangefox build.
[Google Pixel 7a] LeeGarChat:
any progress in the development of the project. have you thought about making a twrp build instead of ofox? as far as i know there are more problems with ofox than with twrp, including loading drivers
[Google Pixel 7a] Wishmasterflo:
No progress here, with TWRP it was the same issue as with Orangefox.

I just tried with a fresh TWRP build, its the same as in Orangefox that the touch screen is not working.
[Google Pixel 7a] d0udQu0i:
hi @Wishmasterflo

OK i understand

but the project is not stopped?

can't you get help from other people working on a recovery with google pixel?

thank you for your work
[Google Pixel 7a] Wishmasterflo:
I already did and there is almost no one working on that, so it seems a bit hopeless. Perhaps I have to give up on that.
[Google Pixel 7a] Sneeder:
I know that this will sound stupid but trust me it isn't, so please bear with me without prejudice: have you tried using ChatGPT as a coding companion? Not that it will save the day with a solution by itself but working in tandem with that can put you on the right track for a fix by filling the gaps with some obscure pieces of informations that only good knows how they ended up in its training dataset, lol. If you didn't, please consider giving that a try, there's nothing to lose either way no?
[Google Pixel 7a] Wishmasterflo:
Hello!

Someone on LinageOS who can send me the logcat.log file after booting to lineageOS recovery from /tmp/logcat.log ??

Thanks!
[Google Pixel 7a] roirraW "edor" ehT:
<Moderator Note>:

@Wishmasterflo,

I deleted the duplicate you had made of your post in the "Is custom recovery possible/something that's being worked on?" Pixel 7 Pro thread.

Thanks,

@roirraW "edor" ehT
[Google Pixel 7a] Wishmasterflo:
Yea, OK thanks.
[Google Pixel 7a] dcarvil:
Would a log from a Pixel 3 be of any help? My 7a is on the stock Google ROM.
[Google Pixel 7a] Wishmasterflo:
No, I would need one from a Pixel 7 series.
[XPERIA X1 General] Nick_74:
Hi to you all!

I new to this forum and have a question about the panels interface.

Is there a possiblity to increase the amount of panels in the Xperia to more then nine? So it resembles the Iphone interface to some extent.

Could it be a memory issue that they restricted the number of panels to nine?

Thanks for a great forum by the way!

Cheers!

Nick.
[Nokia 4.2 Questions & Answers] tnt-lop:
I have a Nokia 4.2 Model TA-1157

Which just turns on, comes out as shown in the image and the other is by pressing the power and volume button -

View attachment 6001165

View attachment 6001167

How to unlock the bootloader of nokia
[Nokia 4.2 Questions & Answers] PhoneRepairHUB:
fastboot --set-active=a

or

fastboot --set-active=b
[Google Pixel 7 Pro] krepsz:
I still didn't receive September update on my Pixel 7 pro.Any idea?
[Google Pixel 7 Pro] schmeggy929:
Yes, it hasn't been released yet.
[Google Pixel 7 Pro] simplepinoi177:
At this point, do you guys think it will be full on A14 stable release update or just another monthly that's been considerably delayed?
[Google Pixel 7 Pro] JakeDHS07:
At this point I assume they launch it with 14. That late beta might be why there was a delay. I don't remember the last time just a regular monthly was this late.
[Google Pixel 7 Pro] MrBelter:
Don't forget in April Google dropped the first Monday of the month schedule.
[Google Pixel 7 Pro] simplepinoi177:
This was the instance I had in mind....that one was one that went pretty far into the month before releasing...

I believe that was the one that had the T-Mobile issues and took such a long time to reach T-Mo customers that it delayed it pretty far even for the global version of the update...I could be mixing up the 2 instances though...
[OnePlus 9 Pro] Mahbubur Rahman Siam:
Oneplus's software quality has gone down with each OS upgrade. One of the worst parts about oxygen os is it's refresh rate and thermal throttling . This guide is about saying f*ck you to that .

Refresh rate throttling remove -

1.Download 4a Setedit application from play store .

2.Get the 4a setedit feature pack app .

3. Give unrestricted battery access to both applications .

4. Now you need to give permission to write to secure tables using adb ( You don't need root for this ).

5. To give permission you must have proper drivers installed in your computer and you need the latest android platform tools .You also need to enable usb debugging on your phone from devloper options .

6. In platform tools folder open cmd window and type -

adb shell pm grant by4a.setedit22 android.permission.WRITE_SECURE_SETTINGS

7. Now you need to open set edit apps and edit the tables attached in picture the same way . At the same time you should add those settings to foreground guardian in jobs option in setedit app

8. That's it you have disables all software throttling.

Disabling Thermal Throttling -

1. You just need to flash the attached zip in magisk app . ( Root is must duh )View attachment 6001179View attachment 6001185
[OnePlus 9 Pro] Evon88:
I'm ready to be the second person to say

"OnePlus It will become the biggest rubbish of phone communities, and it will go to the phone dustbin, and this will be my last phone from this backward company.​

🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮🤮
[OnePlus 9 Pro] Badger50:
Greetings. I have edited the thread title and first reply.

While it's ok to gripe about OEM's, please also remember that you must also abide by the forum rules for member conduct when posting.

Case in point, XDA Rule 2.1:

Spoiler content hidden.

Please keep your posts polite and respectful so as not to incur any disciplinary actions for Rules violations.

Your cooperation is appreciated. Thank you.

-Regards: Badger50
[OnePlus 9 Pro] TheGhost1951:
Talking about limitations. Samsungs unlockable bootloader is the worst ever. That is why i have moved to OnePlus.
[OnePlus 9 Pro] MJPollard:
That's why Samsung phones are (and will continue to be) a non-starter for me, no matter how whiz-bang they are. I'm certainly no fan of OxygenOS/ColorOS, but as long as I can unlock the bootloader and install a custom ROM, I'll be sticking with OnePlus; in fact, my 9 Pro is a peach on my LineageOS fork. 😁 (OnePlus made a major misstep with the 10 series by withholding the MSM tool, but someone managed to hack and release the MSM tool for the 11, and custom ROM development is proceeding apace. As such, a used 11 will definitely be in the running when it's time to retire my 9 Pro.)
[OnePlus 9 Pro] netgar:
Im waiting for pixel 8pro. Im done with op9 pro. Done with this company. 👎
[OnePlus 9 Pro] TheGhost1951:
Sorry to see you go......

Think about it......

Google's been using its own chips for the past couple of Pixel generations, so we're anticipating a Tensor G3 will power the Pixel 8 Pro. This chip is thought to be based on Samsung's Exynos 2300 platform, which could mean that Google lags behind in raw power compared to rival phones once again.
[OnePlus 9 Pro] MJPollard:
That, and it seems like virtually every Pixel phone that's been released has some sort of design flaw and/or quirk that people either need to live with or have to find some way of working around. An under-powered phone with design "quirks" isn't something that I'm in any big hurry to deal with, personally. If the day ever comes that OnePlus is no longer a viable option for me, then I'll look at Google, but as Aragorn once said, "This is not that day!" :LOL:
[HTC Tornado] tobbbie:
Hi all,

...after a long wait I found a suitable rechargable battery to replace the worn out one in my Tornado. It has the size (and mounting) of the Typhoon but still can be fit into the Tornado or Hurricane as well.

Have a look to here: http://picasaweb.google.com/tobbbie...upBattery?authkey=wadwcFTm3no&feat=directlink

I still have 6 batteries left, send me PM if you are interested - first come first serve. Of course you can order yourself at the distributor as well.

[Edit 20100326]

Batteries are all used up now, but see this post for at least something helpful.

enjoy,

tobbbie

:-)
[HTC Tornado] markanthonypr:
So is the problem about loosing time settings when removing battery gone by replacing this internal one? Mine always shows as the internal battery is fully charged. But it does loose the time settings.