yashsingh1/xdaforums huggingface dataset:
[Moto G8 Plus Questions & Answers] Xvaro:
Hi macgd016

Sorry to revive this.

I have seen the same behavior you described but i don't have a moto g phone... I don't use the web version and I haven't touch App optimisations yet.

Did you found a fix ?
[Xiaomi Mi Max 2  Questions & Answers] shroomy_dude:
Hello!

https://xdaforums.com/t/rom-13-0-official-oxygen-crdroid-v9-1-24-01-2023.4545371/post-88631249

bug: Auto Rotate does not work · Issue #200 · crdroidandroid/issue_tracker

Issue type User interface Device Xiaomi MI MAX 2 (oxygen) build.board: MSM8953 build.bootloader: unknown build.brand: Xiaomi build.cpu_abi: arm64-v8a build.cpu_abi2: build.device: oxygen build.disp...

github.com

I've explained my issue in these two places, you can check for information in detail. Short, I had auto-rotate issues, the only thing that is not working. On github I was told it is due the wrong firmware and I need to bassicly wipe all and start over after flashing the correct firmware..

I'd like to avoid that, but I will do it if I must. but if not I am confused as to how to proceed. Should I flash firmware in twrp and that's it? Or do I need to backup my data, wipe all, flash firmware and then reinstall rom from 0?

Some guidance would be much appreciated, as detailed as possible, I am not that young or good with tech stuff.

I also have question, why is it only gyroscope/auto-rotate? All other things work as expected, including fingerprint etc

EDIT:

I have flashed stock ROM, verified that Auto-Rotate works (as well as does the light sensors, wwhich also did not work) and then flashed crDroid again as per instructions and again auto-rotation does not work.

Please help, anyone

EDIT2:

OK, for anyone finding this with same/similar problem, here is how I fixed it after searching far and wide and struggle to understand it all:

-I downloaded latest stock **fastboot** ROM

-I opened and looker for a file named "persist.img" and extracted it

-I copied the file to my phone

-Booted into recovery

-Mounted "Persist" partition

-Then selected "Install" and checked "img" option

-Selected my "persist.img" file and flashed to "Persist" partition

Rebooted and now all sensors work.

I do not know why I needed to do this when other do not.
[Tilt, TyTN II, MDA Vario III General] dizzy33:
Hello,

I have a problem when coming back from vibration mode :

when I put my phone in vibration mode using the Comm Manager, if I re-enable the sound (disabling the vibration mode) using the Comm Manager, it does only enable the sound for Windows but not for the phone ring. So every time I need to use my stylus to press the top left sound icon and then re-enable the phone ring too ...

Does anyone know where does this problem come from ?

Is there a workaround ?

Thanks !

Note : I'm using the official HTC 6.1 ROM.
[Tilt, TyTN II, MDA Vario III General] dizzy33:
No one else has got this problem ? :(
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] testask123:
does updating the phone prevent me from doing this or is it fine?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] cmfCyangenModteam:
Fine,
[Samsung Galaxy J3 (2017) Questions & Answers] catjj:
Greetings people of XDA! I hope you all are doing well!

I would like to ask you all help with rooting a Samsung SM-J330FN (with Ramdisk) through Magisk 26.1 . I have retrieved a "boot.img.lz4" image file from the official Sammobile stock rom (more precisely in the "AP" tar.md5 file) I successfully flashed the device with. However, when loading it in Magisk, I immediately get this error message stating that the boot image can't be unpacked. I've tried shortening the file's name to "boot.img" but that did not do it. I've tried using different versions of Magisk, still nothing, I've also checked if the other tar.md5 files ("BL"; "CP"; "CSC" and "Home_CSC") did not have a boot image...in vain.

well...any help would be much appreciated!

But, in any case, thanks for reading my request! May everyone have a magnificent day!

EDIIIIIIIT!:

I just loaded the "AP" tar.md5 file and it worked! (preferable to rename the file's extention to simply ".tar" before loading it in magisk)
[General Questions and Answers] hackeryy:
I am trying to root a Nord Plus N30, but there is no compatible TWRP download, or custom firmware. I've unlocked the bootloader and downloaded the Magisk app. But I can't install it because I need to flash the boot image to my device.
[General Questions and Answers] cmfCyangenModteam:
Man, theres just no TWRP for that,

People say when you even flash with TWRP that phone, it would not turn on.
[General Questions and Answers] hackeryy:
There isn't a download available for the OnePlus Nord N30
[General Questions and Answers] cmfCyangenModteam:
View attachment 5946649

No TWRP, it would brick your phone.
[General Questions and Answers] hackeryy:
Okay thanks. Also there isn't custom firmware available for the N30. How do I root it then?
[General Questions and Answers] cmfCyangenModteam:
Let me find!

No, even someone didnt make a ROM for that phone!
[General Questions and Answers] hackeryy:
Appreciate you. I have bootloader unlocked and the magisk manager/zip file downloaded, but I need to flash the zip file so I can select the raw .img or .tar file and install the boot image.
[General Questions and Answers] cmfCyangenModteam:
No problems, have a nice day.
[General Questions and Answers] hackeryy:
Is there another way to root the phone then? Could I flash the zip file some other way, without TWRP?
[General Questions and Answers] cmfCyangenModteam:
Trough PC,
[General Questions and Answers] dlads:
Why is this being asked here? Wrong forum mate..

Mods need t move this over to the nord forum
[General Questions and Answers] cmfCyangenModteam:
I Only noticed it now lol :)
[General Questions and Answers] hackeryy:
How do I do it through the PC if there isn't a ROM/firmware for Nord OnePlus N30?
[General Questions and Answers] cmfCyangenModteam:
Then just stay on your stock.
[General Questions and Answers] mingkee:
There's NO N30/CE 3 Lite forum
[General Questions and Answers] dlads:
Is there a Nord 1 or 2 forum? Think they'd be closer than the OnePlus 10 pro?

I'd speak with a mod... Sometimes devices are combined into one forum..
[General Questions and Answers] mingkee:
It's about time to have one because both have been released (N30 for America and CE 3 Lite for ROW).

Yes, I asked similar question on CE 2 forum
[General Questions and Answers] dlads:
Have contacted a mod, hopefully they can shed some light and put your post in the correct location
[General Questions and Answers] hackeryy:
Thanks all.
[General Questions and Answers] Quadraphalange:
I soft-bricked a Nord N30 trying this very thing. You’ll end up in a fast-boot loop or a screen stating that the recovery or boot img “have been destroyed.” I’m still casually trying to resurrect it, will report back with any success.
[General Questions and Answers] thisisapoorusernamechoice:
I found the repos they use to build PixelOS for the Nord CE2 Lite (Oscar) which has the same board (sm6375) as our device and indeed is in the same repo in the OnePlusOSS github repos. I forked everything and I'm converting all the Oscar specific stuff to our device but I haven't been this optimistic in a while. Trying to port the sm4350 to our sm6375 was slow going for me but they already have a kernel for the sm6375
[General Questions and Answers] thisisapoorusernamechoice:
The PixelOS sm6375 kernel repo builds without failing. I'm going to try for a full build tonight. I fully assume things will be broken in the build. The kernel is building for oscar, which is the Nord CE2 Lite. I'm pretty sure Larry is the Nord CE3 lite, and I know Dre is the Nord N200. Can someone please go here: https://github.com/OnePlusOSS/andro...ord_n30_5g/vendor/qcom/proprietary/devicetree

and help me figure out which name is the Nord N30?

I still need to do work on the sm6375-common repos I forked and I need to redo the vendor repos (which I always knew was an inevitability). Bad news: I broke the screen on my CPH2515. Good news: tomorrow is payday and I'm intending to get the CPH2513 this time. Once the dust settles hopefully exciting advances in the next several days.
[General Questions and Answers] dumdedumda:
Per @Yeedatoy:

CE3 Lite = International version

N30 = US version

Both correspond to Larry.

Also, not sure if the following resources are helpful for you, but I've attached them anyway:

GitHub - IamAzmathullaShaikh/android_device_oneplus_larry: Unified device tree for OnePlus Nord N30

Unified device tree for OnePlus Nord N30. Contribute to IamAzmathullaShaikh/android_device_oneplus_larry development by creating an account on GitHub.

github.com

GitHub - IamAzmathullaShaikh/kernel_oneplus_larry: {WIP} OnePlus Nord CE 3 Lite Kernel

{WIP} OnePlus Nord CE 3 Lite Kernel. Contribute to IamAzmathullaShaikh/kernel_oneplus_larry development by creating an account on GitHub.

github.com
[General Questions and Answers] thisisapoorusernamechoice:
The kernel repo you linked is an untouched fork of the OnePlus (stock) repos, it won't build for LineageOS. The device tree you linked was most useful, thank you.

The CE2 Lite (Oscar) is still based on the sm6375 we have and it uses a common sm6375 repo along with the device specific one. A lot of the files are 1:1 duplicates with what we have from our own stock dump and cobbled together AOSP trees. An encouraging number of the vendor blobs (also split into sm6375 common and device specific) are also identical to ours.

Finally, I added the larry dts (kernel) devicetree to the sm6375 kernel I forked and again, an encouraging number of the important kernel files in other locations are 1:1 duplicates. I've got builds of both LineageOS and crDroid going now, fingers crossed.
[General Questions and Answers] thisisapoorusernamechoice:
So the full builds failed, but I'm highly confident the only build error was a slight discrepancy in how the original larry DTS directory was structured vs how the current LineageOS one is laid out. After correcting this in a couple files, I successfully built a larry boot.img. New builds of both ROMs are started.

I don't know when I'll be able to push my latest commits unfortunately. I have duplicated them on both build machines for now.
[General Questions and Answers] thisisapoorusernamechoice:
Builds for both ROMs successfully completed. I would like to temper everyone's expectations with my strongly held assumption that things WILL be broken. I will be working on uploading to sourceforge next.

Unfortunately, I will not be able to test this at this time. My CPH2515 is broken and my new CPH2513 is scheduled to be delivered on Monday.
[General Questions and Answers] thisisapoorusernamechoice:
Mis send
[General Questions and Answers] sajattack:
@thisisapoorusernamechoice I built your latest source tree and it didn't boot the kernel at all for me. Just dumped back to fastboot. Possible I did something wrong but I don't think so. CPH2513. I'm guessing you need dts for ossi still.
[General Questions and Answers] thisisapoorusernamechoice:
Could be any number of things. Just making sure, did you use all the repos that I forked from PixelOS? Those are what I built off of. I still have to better name and organize the various branches. Check the attached manifest, that's what I used to build LineageOS.

I just remembered I haven't been able to push my latest commits yet and won't be able to before tomorrow.

Ultimately we will need to figure out a way to get logs to see what is wrong at this point.
[General Questions and Answers] sajattack:
Here is my manifest
[General Questions and Answers] thisisapoorusernamechoice:
device_oneplus_sm6375-common 14.0 branch is for crDroid, try the lineage-21 branch just to make sure.

I also remembered we still need to run ./extract-files on rooted stock to get all our vendor blobs, that's how the vendor repo is generated. We can't just blindly trust the CE2 Lite or even CE3 lite repos are compatible with this device as is.
[General Questions and Answers] thisisapoorusernamechoice:
I just took a second look, you definitely need to use the lineage-21 branch of the kernel repo, that's the most up to date
[General Questions and Answers] thisisapoorusernamechoice:
Ugh I apologize my repos as is won't build correctly because it's the latest commits that I can't push until tomorrow that correctly point the kernel to build for larry as opposed to Oscar

@sajattack if you want I can try to instruct you the file edits you need to do try to get it to build correctly. That or I can private message you links to my (Larry based) builds.
[General Questions and Answers] sajattack:
Congratulations 🥳
[General Questions and Answers] thisisapoorusernamechoice:
Hell yeah! Newest manifest with latest branch names attached and commits pushed
[General Questions and Answers] OdinVex:
Awesome progress, tip of the hat. :]

Edit: @thisisapoorusernamechoice, your `rosand25/android_device_oneplus_ossi` repo states 8+4 for memory but it's 8GB built-in + up-to 8GB "RAM expansion". Eg 8+8.
[General Questions and Answers] thisisapoorusernamechoice:
@OdinVex thank you for the correction I'll update that ASAP.

My CPH2513 arrived today. More than anything else I want to try to be on the latest stock ROM, rooted, so I can pull OUR specific vendor blobs into my (forked) vendor repos. I know this branch of this dump is the January or February Android 14 update for the CPH2513, and also that there's since been a May update.

My question is can I use the boot.img provided in the (January) dump to root the May stock ROM or is the mismatching boot.img gonna throw my phone into a bootloop?
[General Questions and Answers] dumdedumda:
If I recall correctly, each boot.img contains a different hash for each update. For safety, I'd just take 15 mins to pull the boot.img for your May stock rom and root it via Magisk.

Two ways of achieving this:

1) (Easiest and most convenient way, though I have not tested this myself.) Use Oxygen Updater, download the FULL update (NOT incremental) and use Magisk to patch the boot.img contained in the archive. Pull the patched boot.img via ADB and flash it via Fastboot.

2) (Safest, though, slower method). Sideload LineageOS 21 GSI rom via Project Treble, pull boot.img through ADB to PC, reboot to stock rom, patch boot.img with Magisk on Stock, pull patched room via ADB to PC, and flash via Fastboot.

https://xdaforums.com/t/extract-boo...ideloader-method-and-other-tutorials.4585449/ contains the full instructions for #2, but make sure you read @gobertel 's note and sideload LineageOS 21 for Android 14 (rather than LineageOS 20):

"I'd like to add that this also works for the 2023 version BUT you must use another ROM which I will link below, follow the exact same steps but just use this ROM. Worked for me and I was able to root my device"

My device is rooted but not on the May update. Else, I'd upload my boot.img for you to use.
[General Questions and Answers] thisisapoorusernamechoice:
I remembered about oxygen updater right after I posted, thank you. I've got it downloading the full (not incremental) May update which I'm already on through the normal update process, bootloader already unlocked.
[General Questions and Answers] sajattack:
I've got some OTAs backed up here https://nextcloud.paulsajna.com/index.php/s/zBpoe8g6WkxgZ4B . I had trouble getting the 14.0.0.302 full to boot and couldn't find a 14.0.0.700 full, but 14.0.0.201 has been pretty reliable for me.
[General Questions and Answers] thisisapoorusernamechoice:
Method 1 has me stuck in a bootloop unfortunately.
[General Questions and Answers] dumdedumda:
Sorry to hear. I used method 2 myself.

Do you have a backup of your stock boot.img?
[General Questions and Answers] logiccircuit:
I got stuck with this same bootloop. The update to the latest rom worked fine, then after rooting the phone it started bootlooping. Even restoring the non-rooted boot.img didn't fix it.

The last two system updates refused to work with a rooted phone, and that was definitely a deliberate decision on OnePlus' part. I think this bootloop is a result of their new strictness about this, but accidental or deliberate I have no idea.

I'm very happy to see your Lineage build, and I think it's arrived just in time.
[General Questions and Answers] Yeedatoy:
What device? I've never seen 8+8. Actually I should ask what OOS version. Maybe it was changed in 14. Honestly I would remove that in general. A 4gb zram file is more than enough, and these ram expansion things cause more harm than good. It ends up creating a swap file that acts as a cache for actual zram and interferes with zram working correctly

Did you click on uninstall in magisk than restore image? That should have allowed the update to proceed. Or just download the full build from oxygen updater and download the local installer from a OnePlus 12 and click local install. I haven't had any issues keeping root and updating except for the latest 700 release but it was failing because I was trying to install a build from a different region. Did you happen to have any Dolby module installed? It screws up SEpolicy and tends to still create issues even after unrooting

The CE 3 lite shouldn't have any differences. The pixelos build is for the CE 3 lite. I actually flashed it over 14 before being informed that the dev and other initial tester flashed from oos13 and still, on the 2nd build I have no issues
[General Questions and Answers] OdinVex:
Same device they're now using, the 2513 non-TMO version. This feature was present on 13 and no, I wouldn't remove it because it's up to the end user. 4GB may be enough for you, not enough for others. I agree RAM should be RAM and storage should be storage, but some have scenarios justifying it. As for the backend, I don't know if this a swap or zram.
[General Questions and Answers] thisisapoorusernamechoice:
How do you install the (full) 201? Did you use FastbootEnhance or just payload-dumper the payload.bin and flash each img manually?
[General Questions and Answers] sajattack:
I used payload dumper and flashed all the images with a simple bash script (using fastboot), then flashed the lineageos recovery and flashed more from fastbootd, (it seems like some things are only accessible to one or the other)
[General Questions and Answers] sajattack:
Don't forget to disable vbmeta too. It was very fiddly and took me several hours to get the whole setup working. I also experimented with flashing some super.img's I had backed up.
[General Questions and Answers] xe500linux:
From where? The CE Lite?
[General Questions and Answers] sajattack:
I have one I compiled from the extracted kernel of stock. And I also have one compiled from thisisapoorusernamechoice's git repo. I guess I can upload those if you need them.
[General Questions and Answers] sajattack:
recovery

Nextcloud - a safe home for all your data

nextcloud.paulsajna.com
[General Questions and Answers] xe500linux:
Thanks!
[General Questions and Answers] sajattack:
I found the official link for 622 again. My previous copy was corrupted as I mentioned. I had the best luck going from 601 or 622 to the may update (700). 14.0.0.201 prevents you from flashing 14.0.0.302 or 14.0.0.700 if you have verity disabled. I'm gonna try going back to 622 then to 700 and report back for @thisisapoorusernamechoice

https://android.googleapis.com/packages/ota-api/package/78d56df9d819faedfbb13cd3c57c12939ec9c14e.zip
[General Questions and Answers] sajattack:
Once again it took a few tries but now I got rooted 14.0.0.700 to share with y'all.

cph2513 14.0.0.700 unbrick/root guide

1. extract 13.1.0.622 ota using payload-dumper

references:

https://android.googleapis.com/packages/ota-api/package/78d56df9d819faedfbb13cd3c57c12939ec9c14e.zip

GitHub - ssut/payload-dumper-go: an android OTA payload dumper written in Go

an android OTA payload dumper written in Go. Contribute to ssut/payload-dumper-go development by creating an account on GitHub.

github.com

2. flash from fastboot with flash.sh

references:

fastboot flash script

fastboot flash script. GitHub Gist: instantly share code, notes, and snippets.

gist.github.com

3. flash vbmeta again with --disable-verity

4. flash lineageos recovery

references:

boot.img

Nextcloud - a safe home for all your data

nextcloud.paulsajna.com

5. enter fastbootd from lineageos recovery

6. flash again with flash.sh

7. flash vbmeta again with --disable-verity

8. reboot

9. It will boot into stock recovery, hit format data (THIS WILL WIPE THE PHONE)

10. It will reboot to stock 622

11. update to 14.0.0.302 using the stock updater

12. update to 14.0.0.700 using the stock updater

13. flash magisk boot.img (from fastboot) (adb reboot bootloader)

references:

magisk_patched-27000_4rsZA_cph2513_14.0.0.700.img

Nextcloud - a safe home for all your data

nextcloud.paulsajna.com
[General Questions and Answers] bdmajora:
I was able to get to the first screen and got it to install and boot. But without the touch screen working, I am unable to get any farther with the lineage os build.

Edit #1

As an update I also tried cRDroid from the sourceforge. It also lacks the ability to interact with the touch screen. However the volume buttons both work.
[General Questions and Answers] dumdedumda:
Probably lacking the vendor blobs, or drivers, needed for the rom to fully function, which @thisisapoorusernamechoice last mentioned he or she is in the process of working on.
[General Questions and Answers] bdmajora:
That makes a lot of sense. Thank you.
[General Questions and Answers] logiccircuit:
I am so hyped for Lineage on this phone. I've been using custom roms since the Cyanogenmod days - usually pure Lineage or CrDroid, depending on the phone. It's what I know and love, and I'm excited that it's on the way.

Much respect to @thisisapoorusernamechoice for doing the work to make this happen.
[General Questions and Answers] thisisapoorusernamechoice:
I appreciate what you did here but I couldn't get it to work for me. I have spent however long since my posts indicated without use of my CPH2513. I must've seriously messed things up trying to fix them since I was stuck in a bootloader bootloop (I couldn't boot to anything else no matter what I tried). This is entirely my fault, I am stupid, I will tell anyone who asks I know only enough to seriously mess with things. I am thrilled to announce that literally moments ago I was finally able to boot my CPH2513 again. I would like to share what worked for me.

Also I would like to share that unfortunately, MSM tool is dead for this phone but there is a potential replacement which I have found in my research. I am unable to test it because the 2513 file is locked by GSMafia, but there is an unlocked 2515 edl firmware file and a youtube video that does work for our device in getting what has replaced MSM tool up and running; this new tool DOES detect our device correctly which is very intriguing and promising. I digress.

To get my stuck in bootloader mode CPH2513 booted again all I had to do was download from this OnePlus community thread the "OxygenOS 13 OnePlus Nord N30 Rollback file" you just have to scroll down a little for the link. It will download an officially signed full OTA file. I used FastbootEnhance to flash the extracted payload.bin in fastbootd mode. The linked to OTA file made all the difference, and I know exactly why: THIS SIGNED OTA FILE, UNLIKE EVERY OTHER ONE WE'VE ALL BEEN SHARING, INCLUDED THE FOLLOWING TWO PARTITION IMAGES (WHICH EVERY OTHER OTA FILE DID NOT HAVE):

my_company.img

my_preload.img

I knew these were present on our device but without them all I could do was try creating them as empty partitions, which was clearly insufficient. My longwinded point is I think I've found our best way back from whatever you want to call the kind of brick that leaves you stuck bootlooping to bootloader. I am very relieved and very excited what I can accomplish with a newly resurrected device.
[General Questions and Answers] dumdedumda:
That is good news indeed. I recall coming across an XDA post in which the OP managed to crack the MSM tool, but it seems like that post has not been updated since its release.

Have you had any success rooting your revived CPH2513?