yashsingh1/xdaforums huggingface dataset:
[Touch CDMA General] No1ustad:
take a picture while covering the lens, then set it to be ur wallpaper man.
[Touch CDMA General] ghettofreeryder:
hahahahahahaha
[Nokia 7.2 ROMs, Kernels, Recoveries, & Other Devel] Raghu varma:
* initial build

* R33

* April security patch

* Added ota program

* Enforcing

* Clean flash recommended

* Signed with private keys for the sake of security

* Flashing process changed request to click on installation procedure for further steps

* No need to flash gapps
[Nokia 7.2 ROMs, Kernels, Recoveries, & Other Devel] vitalikmp:
I tried to flash the ROM following the manual by the link from the first post, but there are a few steps missing:

> 8. Tap on reboot and tap on bootloader ( this will reboots your phone to bootloder mode )

> 9. Now open cmd in pc flash vbmeta using this command

>for slot-a > fastboot flash vbmeta_a --disable-verity --disable-verification vbmeta.img

>for slot-b> fastboot flash vbmeta_b --disable-verity --disable-verification vbmeta.img

>( thanks to [MENTION=4947821]singhnsk[/MENTION] for this step )

>10. now type fastboot reboot and wait for 3 min rom will boot up

← xdaforums.com/nokia-7-2/development/rom-lineageos-17-0-t4001281

⇐ sourceforge.net/projects/ddv-sprout/files/vbmeta/TEN

After these steps, the system started up.
[Nokia 7.2 ROMs, Kernels, Recoveries, & Other Devel] Lordxhelmchen:
FIRST !

Many thanks for your work Raghu !

Really good!

I didn't have to do that, came from Lineage 16

and wanted to do a clean flash

My timetable was:

* Boot in to twrp ( https://sourceforge.net/projects/ddv-sprout/files/TWRP/TEN/2020-04-05/ )

* Click on wipe

* Click on format data

* type yes

* Reboot to bootloader

* Boot in to twrp

* Wipe all partitions

* flash ROM zip

* flash vendor zip

* Change slot - when A go to B, when B go to A ( Without new boot in twrp )

* Wipe all again except system vendor

* Reboot system

Everything works fine.

Greetings and good luck

LH

***
[Nokia 7.2 ROMs, Kernels, Recoveries, & Other Devel] Lordxhelmchen:
After today's OTA update of DerpFest 10 I had massive problems.

At first everything went well.

Only the ROOT was gone.

I tried to reinstall Magisk and

got caught in the recovery loop.

That sucks.

Isn't it possible to download the ROM DerpFest via

OTA Updater to update?

Or have I done something wrong?

Who knows what?

Greetings.

LH

***
[Nokia 7.2 ROMs, Kernels, Recoveries, & Other Devel] Lordxhelmchen:
I've been on the Derpfest ROM for two weeks now.

Everything's going smoothly.

Magisk and TWRP are also working great with it.

The Accu lasts longer than with Lineage 16.

Bluetooth audio, WLAN and GPS reception are good.

I have the Nova Launcher and use the Derpfest design to Android.

I'm happy with it.

Greetings

LH

***
[Nokia 7.2 ROMs, Kernels, Recoveries, & Other Devel] keturidu:
Thanks, ROM works just perfectly. Any possibility to run Nokiacamera app?
[Nokia 7.2 ROMs, Kernels, Recoveries, & Other Devel] k-ninja:
Question about the kernel in this ROM - is it custom compiled or a nokia kernel?
[Nokia 7.2 ROMs, Kernels, Recoveries, & Other Devel] Lordxhelmchen:
Sorry, see Raghus Post below

At my 7.2:

Kernel 4.4.194-perf+

#1 Thu Mar 12

Regards

LH

***
[Nokia 7.2 ROMs, Kernels, Recoveries, & Other Devel] Raghu varma:
Hello there

Nope rom comes with stock prebuilt kernel. :)

Reason - Nokia officially never released kernel sources for the phones which released from 2019 due to software comes from longcheer instead of FIH ( Foxconn )
[Nokia 7.2 ROMs, Kernels, Recoveries, & Other Devel] Lordxhelmchen:
Ahoi Nokia fans.

I just realized that I can't connect to VoWifi.

Only VoLTE works. fine.

I am at the Telekom, German Provider.

Is this a Nokia problem?

Have any of you on the 7.2 VoWifi / Wlan Call?

Thnks

LH
[Xiaomi Mi 9 Questions & Answers] jfodra:
Hi everyone, I'm thinking about using the latest ParanoidAndroid or HavocOS but I'm curious for everyone who has used both xiaomi.eu or stock rom and those custom roms I mentioned above. What do you guys think is the difference? Pros and cons of each roms? What do you suggest? im currently on xiaomi.eu
[Xiaomi Mi 9 Questions & Answers] baggino:
The desire to try is great, but both paranoid and havoc have some flaws .... The best is: Xiaomi. eu 11.0.9. stable QFACNXM
[Xiaomi Mi 9 Questions & Answers] jfodra:
That's what I feel man. Haha. I really want to try custom roms but from experience with my oneplus 3, custom roms like havoc is faster but the photo and video quality is bad compared to stock and also the battery life is also shorter. :/
[Xiaomi Mi 9 Questions & Answers] buck123:
Hi. I have always preferred android stock, miui I do not like too much. I have tried many roms (pixel experience, paranoid android, extended ui, lineage, havoc ...). The devs do a great job, and the roms are very stable, very few bugs. However, unfortunately, the truth is that none is as stable as miui. They are less smooth, the camera and the sound are worse, and I have always noticed something strange in the scrolling of apps such as the browser, Telegram, etc. I suppose it has to do with the proprietary drivers of Xiaomi, but in the end in miui everything ends up working better. It is my opinion
[Xiaomi Mi 9 Questions & Answers] jfodra:
Thank you so much. Yeah, it's really the performance from the custom roms that makes you want to install them but the stability, it really is more stable with miui. I guess I'll just stick with the stock rom for now. Thanks again.
[Xiaomi Mi 9 Questions & Answers] invisiblewave:
Honestly, the performance and battery life on the eu rom is also better than the AOSP roms, because it includes so much of the proprietary customization and the proprietary drivers.
[Xiaomi Mi 9 Questions & Answers] Shojimeguro:
xiaomi.eu should be default ROM for all xiaomi phones
[Xiaomi Mi CC9 / Mi 9 Lite Questions & Answers] apna.suresh0305:
I am not able to download MIUIPro rom from below source link due to the access issue, If anyone have the recovery ROM, can you please share to my google drive? My ID: apna.suresh0305@gmail.com

https://miuipro.info/rommgr/device/608
[Android Q&A, Help & Troubleshooting] Asif3718:
Here is the full description with recovery logs files that how my RMX1825 lost IMEI :-

1. I flashed TWRP recovery after unlock bootloader.

2. After that I am trying to get full backup through TWRP but the error was occurred every time, So I flashed OrangeFox Recovery and take the full backup through it, But it not include all partitions. So I backup only of these partitions:- System, Vendor, Vendor Image, Boot, Data(Excel. etc) and recovery.

3. After that I flashed "Disable_Dm-Verity_ForceEncrypt_03.04.2020.zip" and also flashed magisk. And reboot my phone, But due to this DM- Verity zip file I am unable to access my any type of lock, like fingerprint lock, Password, pin or face lock. And also I am unable to access app drawer.

4. So I flashed stock rom of RMX1821 .ozip file through official recovery, and everything will be fine, Then I decided to enable DM-Verity disable option of Orangefox recovery and when I reboot my phone then IMEI goes to "Null" and also network goes.

5. Then I search the solution of this problem on XDA, And one Junior member said that to Run two commands through Fastboot mode, I execute these commands - "fastboot erase nvram" and "fastboot erase nvdata". But my problem is not solved.

After this process I tried lots of methods to recover nvram and nvdata partitions but all are failed.

6. I have .ofp file of RMX1825 but I need it to extract for flash this ROM through SP Flash tool.

Please help me to fix my phone.

Drive Link of Recovery Logs:-

https://drive.google.com/open?id=13RL4FreFQ7uye7Kcow_X78InPED6Q8Gi
[Mogul, XV6800 ROM Development] gc14:
Hello all,

Spoke with a few people today from UTStarcom and Verizon and got quite a bit of information about this long awaited update. Figured I'd share with you.

Called UTStarcom and spoke with Orlando, an engineer with them. He forwarded an internal memo to me (I can't post it on here, don't bother asking). I can tell you what was in it though.

The update is complete and was received by Verizon mid June.

Rom version number is 3.36.605.0. I know a lot of you are going to say "but we already have 3.56 blah blah", but those are Sprint updates and just because the version number is different, doesn't mean it's not newer.

The update addresses the following (straight from the memo):

-Update to Windows Mobile 6.1

-Update to EVDO Rev. A

-Update location based services (GPS)

-Update bluetooth profiles

Update is complete on their end, waiting on Verizon to give the go ahead. He said he would speak to his superiors and find more info and for me to call back Thursday (he gave me his extension).

I called Verizon and spoke to Wes, a WDTS Tier 3 Tech.

He confirmed what Orlando told me. The completed update was received by Verizon and has been in final testing. The last update he had was July 3, been in testing for a while with no problems. Projected release set for end of the month/early August.

He also told me it's been so long due to the fact that they decided to add WM 6.1 (previously it was only expected to address EVDO Rev A / GPS)
[Mogul, XV6800 ROM Development] serfboreds:
Fugg yes!

Now, does this potentially include aGPS? Will we get the lock times of Sprint? Any other potential goodies that could be included? Lastly, what will DCD be looking to extract to improve in his ROMs?
[Mogul, XV6800 ROM Development] a_lazy_dude:
Dude, you rule.
[Mogul, XV6800 ROM Development] thundaar2000:
Can't wait...

Now I have to check the vzw or utstar sites every day!
[Mogul, XV6800 ROM Development] serfboreds:
Where would you look on Utstarcom if it were there? I know it is not yet but I can't even find anything close except this and it is a dead link here.

Link please...
[Mogul, XV6800 ROM Development] scrawnyb:
Perhaps... here???

http://handsets.utstar.com/view_phone_details.aspx?mcode=XV6800

Idk though, they didn't update the sprint one yet
[Mogul, XV6800 ROM Development] kashabrown:
Excellent news GC - hopefully it might add some more functionality to the GPS, although with your fix, it seems to work really well now!

Thanks for the info!
[Mogul, XV6800 ROM Development] serfboreds:
Thanks, this is great. I am sure GC or DCD will have this dissected well before it hits Slorizon's website (or the UTStarcom one you posted), but it is exciting none the less.
[Mogul, XV6800 ROM Development] lllboredlll:
I'll be sure NOT to hold my breath waiting on their release :cool:
[Mogul, XV6800 ROM Development] calash:
So...did you happen to ask him about what it would take for an "Accidental" leak of the beta? Because I am sure a few of us would drop some money into an unknown Paypal account if such a thing were to happon.

:)
[Mogul, XV6800 ROM Development] elisherer:
OK... so I'm not trying to be a bad news guy, but I pretty much got the exact same story from UTStarcom back in April, but the release date was May.

When I called in May they said it was release to VZW and was up to them to do something with it. I never was able to get anyone at VZW to admit they had the update (in fact some really bad Help guy yesterday told me that a) any updates would come from the mantufacturer and not VZW, and b) anything, and I mean ANY application you add to the PPC is bad for it and will cause it to slow down. (He was a real piece of work, and when I asked what about things like Microsoft's Live Search which was MADE by MS for this type of phone, he said ANYTHING would basically bog it down and if it stopped VZW would not replace it... schmuck).

Anyway... the UTSarcom site is a good one... but where might we search for Verizon updates???
[Mogul, XV6800 ROM Development] serfboreds:
I am surprised anyone told you anything except "let me check another system....no, I don't see anything here....you may want to keep checking the website if they ever have updates for the phone," schmucks for real. Speaking to higher tier techs is probably more realistic information as they will be seeing memos that other people will not.

Anyways, here is the XV6800 page on vzw:

http://support.vzw.com/phones/index.html?p=3411
[Mogul, XV6800 ROM Development] gc14:
If you read my post you'd see that I asked about what you're referring to. The "release date" for May was for EVDO Rev A & GPS. They decided to add WM 6.1 at the last minute, which prolonged it. The difference is, you never got anyone from Verizon to admit to it, while I have spoken to several people since May who all have confirmed it.

You guys have to trust that I know what I'm doing....this hasn't been my first time calling and I know what to ask. They pretty much know me by name now when I call lol. In fact, I don't hang up until I speak with someone who knows what they're talking about.

As far as the update itself goes, it will be on HTC's site when it's available, not UTStarcom's or Verizon's.
[Mogul, XV6800 ROM Development] elisherer:
OK thanks... I had been to that page many times before, but didn't know that they might post anything like a ROM update there.

We'll see....

And yes, senior techs are probably better... just didn't have the time to wait yesterday.
[Mogul, XV6800 ROM Development] serfboreds:
Do you have a link for where you would look for this upgrade on HTC.com? I know you and DCD will be releasing ROMs before I find it but curiosity reigns supreme.

This is what I found but I don't think this is anything more than a marketing page:

http://tytnseries.htc.com/htctytn.html
[Mogul, XV6800 ROM Development] 760hacker:
http://www.htcamerica.net/support/support-product.html

It will be posted on this site under the appropriate phone. Since there have not been any updates for VZW you won't find the xv6800. Correct me if I am wrong GC.
[Mogul, XV6800 ROM Development] gc14:
First, that link is for the TyTN, not the Titan. 2 Different phones. The TyTN is actually the HTC Hermes, as the TyTN II is the HTC Kaiser.

Second, when it's available you'll be able to find it here:

http://www.htc.com/us/FAQ_Detail.aspx?p_id=82&act=faq&cat=268

except when it's released, there'll be an icon next to "Tips & Tricks" called "Software Download" similar to the Sprint Mogul page located here http://www.htc.com/us/FAQ_Detail.aspx?p_id=75&act=faq&cat=268
[Mogul, XV6800 ROM Development] serfboreds:
Thanks, thats the link I was looking for. You are one resourceful dude GC.

Do you work in the phone industry?
[Mogul, XV6800 ROM Development] gc14:
Nope. Computer Engineer specialized in Embedded Systems Design :D
[Mogul, XV6800 ROM Development] scotcha12345:
Sweet

Maybe this seems a bit off subject, but why would a company with proprietary information share there potential release dates and internal memos with a guy that calls in a lot for tech support?

Hope that doesnt sound rude, its more me just being inquisitive. Essentially, how do you manage to be seen as someone worth sharing that information with?
[Wear OS Q&A, Help & Troubleshooting] InfernvlPlvgue:
Can anyone post the Google Clock app version 5.4.0? I have no update to this version in the play market.
[Huawei P40 Pro Questions & Answers] benchallenger:
So weird issue with my new p40 pro. It’s on version 10.1.0.114, and all HMS apps latest update.

However when i open the selfie camera to take a portrait mode pic, it doesn’t do any background blur - UNLESS I go to effects and click on one of the other effects, such as lights or hearts etc.

Anyone else having the same? Have tried a factory reset but still same issue. Wasn’t doing this on Software 10.1.0.109 i think.
[Huawei P40 Pro Questions & Answers] xnostra:
wanted to help you but my software is still at 10.1.0.109
[Huawei P40 Pro Questions & Answers] matik3789:
I was reading somewhere about portait from front camera is without bokeh. Bokeh is only on rear. I did myself selfie and i dont have bokeh too from front camera. But im not sure on 100%
[Huawei P40 Pro Questions & Answers] MajestyZ:
I've seen lots of reviews that post front camera pictures with bokeh effect. The ToF sensor makes this possible. So: bokeh is not only for the rear camera. Try the portrait mode option on the front camera.
[Huawei P40 Pro Questions & Answers] matik3789:
Youre right. Tested it and bokeh is visible but really low

https://www.dxomark.com/huawei-p40-front-camera-review/

Check here. They said bokeh is visible but really low in front camera
[Huawei P40 Pro Questions & Answers] benchallenger:
I don't think so. No difference at all between portrait mode or photo mode without the effect filter turned on for selfie. Looking at the reviews there is noticeable bokeh on further objects. I'm not seeing that unless I turn on circles in effects for example.
[Huawei P40 Pro Questions & Answers] snipeerz:
try hotspot or change country location for other countries I'm in France and I get it 114 so try
[Huawei P40 Pro Questions & Answers] SammyVDA:
I noticed the same on my device after updating.
[Huawei P40 Pro Questions & Answers] xnostra:
thanks it worked the moment i used a vpn, but thats weird why are they doing that.
[Huawei P40 Pro Questions & Answers] snipeerz:
can I ask you if it works to press thanks button :) thanks
[Huawei P40 Pro Questions & Answers] jericho246:
This also happens on my Mate 20 Pro. I always have to choose an effect, otherwise, the background isn't blurred.
[Huawei P40 Pro Questions & Answers] flystarjay:
question, does those effect have a special purpose cause i do not notice it, i only notice blurs
[Xiaomi Mi A2 / 6X Questions & Answers] kxnzxmori:
Hi all. I have a problem updating to april update. I only have an unlocked bootloader. No twrp, root whatsoever. Pls advise. Thank you.

**or maybe xiaomi want to pull the update maybe bcos of unfixed bugs making the update useless? Idk...
[Xiaomi Mi A2 / 6X Questions & Answers] Baron60:
It's a patch.. it's not useless...
[Xiaomi Mi A2 / 6X Questions & Answers] kxnzxmori:
Yes patch as in security patch with some fixes. I understand that. Prolly i stick with mar update since i can't update to april patch. Thanks.
[Xiaomi Mi A2 / 6X Questions & Answers] kxnzxmori:
I've tried updating/installing using a vpn. Still no success. Don't know what's wrong...
[Xiaomi Mi A2 / 6X Questions & Answers] K9998:
One possible guess is that you accidentally modified the system, vendor or boot partition since OTA need 'untouched original' partitions.

For example, change system font, modify hosts(not systemless method) in order to disable AD, etc.

In order to find out what the cause was, you need enable developer option, and type the following command:

Then you can analysis the log
[Xiaomi Mi A2 / 6X Questions & Answers] kxnzxmori:
Thanks. I will give it a try.
[Xiaomi Mi A2 / 6X Questions & Answers] K9998:
No worries,

The typical message you will get if any of three partitions has been modified:

The hash of the source data on disk for this operation doesn't match the expected value. This could mean that the delta update payload was targeted for another version, or that the source partition was modified after it was installed, for example, by mounting a filesystem.
[Xiaomi Mi A2 / 6X Questions & Answers] Sanukanu:
I have a Locked bootloader & I'm having the same problem. Please advise something.
[Xiaomi Mi A2 / 6X Questions & Answers] tnt-4-:
I have the same problem. . i unlocked bootloader to flash persist.img beacause i have had problem with my camera. now it came april(2020) ota update but it fail. why? what can i do? I didn't root the phone. Only unlock bootloader and criticals
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] s3axel:
While waiting for a working TWRP for all those needful of the possibility to access their file system from recovery, e.g. for removing an offensive magisk extension preventing boot I repackaged the Stock OOS recovery but with ADB enabled.

Prerequisites:

Oneplus 8 Pro :)

unlocked bootloader

access to fastboot on the phone

adb and fastboot

Installation:

Reboot the phone to fastboot, then flash the recovery from fastboot with the command

fastboot flash recovery <filename>

(with <filename> being the name of the recovery in the format of "recovery.img" you wish to flash)

Uninstall:

Same as installation, but flash the original stock recovery instead.

Usage:

Boot up recovery, enter encryption key if file system is encrypted. Then connect the phone to PC and you are ready to go with adb. E.g. by using

adb shell

to open a shell and access the file system. Magisk modules are located in /data/adb/modules, deleting the corresponding directory there will remove the module in question.

Step-by-step this would be:

cd /data/adb/modules

to change to the Magisk modules directory

ls

to list the content of this directory, each module has its own directory, usually with a well-recognizable name :)

rm -r <directory>

to delete the directory in question. Tip: in console TAB-autocomplete works

Downloads:

10.5.4 BA Recovery

Modified 10.5.4 BA recovery from GDrive

Original 10.5.4 BA recovery from Gdrive

10.5.5 BA Recovery

Modified 10.5.5 BA recovery from GDrive

Original 10.5.5 BA recovery from Gdrive

10.5.6 BA Recovery

Modified 10.5.6 BA recovery from GDrive

Original 10.5.6 BA recovery from Gdrive

Notes of caution:

ADB security is disabled as I could not get the recovery to allow for authorizing a connected computer. As a consequence any computer connected is automatically authorized in ADB, although with encrypted filesystem at least no data is accessible without the key.

with direct ADB access to your file system you can easily wreck you phone requiring a factory reset or even reinstallation of the OS from fastboot - please be careful on what you are doing ;)

Credits: Thanks to osm0sis for Android kitchen and all great developers for the Oneplus devices, specifically mauronofrio for his TWRP efforts.
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] s3axel:
Description of method to modify recovery by yourself:

Prerequisites:

Android Image Kitchen (credit to osm0sis for providing this tool)

the original recovery image file (henceforth called "recovery.img"). You can extract this yourself from an update zip file by unpacking "payload.bin" and then use a tool like payload_dumper (credit to vm03 for providing this) to extract the recovery.img file

Now do the following:

unpack image with Image Kitchen --> this will create a "ramdisk" and a "Split_img" directory with the unpacked content within

navigate into the "ramdisk" folder and use a text editor (on windows preferably Notepad++) to edit the file "prop.default"

look for entry "ro.adb.secure" and change entry value from "1" to "0". Note this entry can occur multiple times (I noticed twice), change each --> this will prevent adb from asking for authorization (the recovery does not provide such a dialogue)

look for entry "ro.debuggable" and change this from "0" to "1" --> this actually enables adb

look for entry "ro.secure" and change this from "1" to "0" --> may be unnecessary but I wanted to avoid brick in case a modified recovery would result in such a behaviour :)

save textfile

repack the image with Android Image Kitchen and voila:

you have a new modified recovery image you can flash
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] cultofluna:
Thanks for this...

On fastboot we have to flash the modified recovery img?

EDIT : Nevermind haven't read the whole OP
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] HottieLinus:
I have a noob question: this won't affect data or magisk right?
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] cultofluna:
To remove a module , command should not be :

( rm -rf < directory> ) ?...
[OnePlus 8 Pro  ROMs, Kernels, Recoveries, & Other ] s3axel:
Thanks for your comment, but technically no :)

The - f flag is used to omit prompts before each removal, which may or may not be helpful - depending in how sure the user is on what he does :D

I chose the safer variety in my example, confident that users with more knowledge can always look at the "rm" man page to decide what command they want to use...

But again thanks, I do appreciate your help!