yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy Note 9 Questions & Answers] gruuvin:
Sounds like the limit is a protection. Overcome the limit and you may destroy your device.
[Samsung Galaxy Note 9 Questions & Answers] angvil:
How come? Many phones can record 4k with no limits
[Samsung Galaxy Note 9 Questions & Answers] gruuvin:
Maybe nand/sdcard write speed is not fast enough to keep up with 4K, and so while recording it's written only to RAM, and then written to nand/sdcard after recording is finished. If this is the case, you can only use up so much RAM before recording must stop.
[Huawei P20 Pro Questions & Answers] TheDevGuy9497:
My P20 pro CLT-L29 432 is stuck on 9.0.0.47 and has been for months USB, Hi Suite methods do not work neither has OTG so far bootloader is locked and FRP is locked even after removing google account and resetting the phone

Any Ideas?
[Huawei P20 Pro Questions & Answers] Grazeholder:
I am also stuck on 9.0.0.286 and it doesnt tell me to update from OTA or HISuite..

Also for some reason the update information are missing. It says "no information" instead of " security patch etc"

I also did a factory reset but it didnt help...

Maybe some could give an advice.
[Huawei P20 Pro Questions & Answers] dejandoggy1:
same here no info and 9.0.0.286 version in austria

Iv asked huawei service yesterday they say that is no problem and update will be made by imei number and I have to wait so I don't know what to believe
[Huawei P20 Pro Questions & Answers] dejandoggy1:
no info

patch no information provided
[Huawei P20 Pro Questions & Answers] andrei80:
From my observations, if phone is updated through a method other than OTA(Hisuite PC included), there will be no info about update in phone updater. Also, OTA might not work (my phone was stuck on 191 when I bought it second hand, no OTA, but imediately updated to 286 when connected to Hisuite PC. Didn't have update info with 191 and still no info with 286. Never received an OTA this whole time)

Didn't receive OTA for 9.1 and force updated using Firmware finder and modded Hisuite(to 311). Still no info after that.
[Huawei P20 Pro Questions & Answers] dejandoggy1:
Today Iv contacted huawei and they've said my serial number is ok and they will push send me the update. Iv tried all methods FF patched hisuit to instal no success.
[Huawei P20 Pro Questions & Answers] Grazeholder:
Let us know if that will work so i can try do the same and contact them
[Huawei P20 Pro Questions & Answers] TheDevGuy9497:
any luck?
[Huawei P20 Pro Questions & Answers] fatgit:
How did you contact Huawei? I used the website a few weeks ago but never got a reply.
[Huawei P20 Pro Questions & Answers] dejandoggy1:
Iv contacted Huawei from Hicare app tells you in which huawei centar can you call and you can also chat online with them. Try from hicare app quick services
[Huawei P20 Pro Questions & Answers] TheDevGuy9497:
did they push a update?
[Huawei P20 Pro Questions & Answers] dejandoggy1:
Tonight received by regular OTA in Austria
[Huawei P20 Pro Questions & Answers] sPEADy:
I contacted Huawei support via Hicare app (Chat) and told them that I didn't received any OTA update since April security patch this year, the last update I did was via Hisuit from 9.0.0.270 to 9.0.0.286 (which was my/Hisuit mistake because the update was not planned for my device) CLT-L09C432, and I didn't get any OTA since then.

I was told through phone call, after receiving information via Remote Smart Diagnostic, that they have informed the Huawei software development department about the problem, and I should get my update during this week.

I waited till Wednesday but nothing happened, then I backed up all my data via Hisuit, downgraded to 9.0.0270 via Firmware Finder Hisuit (Hacked version :p) did a factory reset.

After logging in got notification for 9.0.0.293 did the update successfully, after the update got notification for update to 9.1.0.311, again did updated successfully, and last after the update got notification for update to 9.1.0.328 (August security patch) also installed successfully, and phone is running smoothly.

So who else is stuck on the 9.0.0.286 or older version this might do some trick with updating the phone via OTA eventually.

Have a nice day.

Just my 2 Cents.
[Huawei P20 Pro Questions & Answers] TheDevGuy9497:
How did u do the hisuite method
[Huawei P20 Pro Questions & Answers] sPEADy:
https://xdaforums.com/tools/general/huawei-firmware-finder-team-mt-t3469146/page144 have a look at that, it's very clear and self explanatory, good luck.
[Huawei P20 Pro Questions & Answers] TheDevGuy9497:
i just get "failed to update"
[Huawei P20 Pro Questions & Answers] jerico9:
I'm stuck on 311. Asks me to update everyday also at the end it says patched 01. I'm on 9.1 now but I've not noticed any changes from emui 8. Nothing sticks out, nothing has improved. I'm thinking it's not installed the firmware which was around 400mb because it takes less than 1 minute to download then less than a minute to install. Once it's installed, it asks to download and install again, every day for 2 months. I don't have access to a pc anyone help with this? Or how can I install beta 10 emui in the UK
[Essential Phone Questions & Answers] neXussT:
Hi,

I have not yet done so, but I plan on installing e.foundation's OS to my Essential Phone. Before I start, I would like to ensure that I can reinstall or switch back to Android, in case I muck it up. Is there a way to backup the installed Android or switch back?

I've heard of Nandroid (https://xdaforums.com/showthread.php?t=459830), but I'm not sure if it will do what I need (A full backup and restore over another ROM). For example, if on Linux, I could use "dd" to copy an entire partition, and write it back later.

Also, as I understand it from (https://mata.readthedocs.io/en/latest/), the phone contains two sets of partitions (slots). If I install the custom ROM to one slot, can I switch back to Android by executing the adb command to change the active slot?

Thanks in advance for help on this. I would very much like to avoid bricking my phone.

Cheers.
[Essential Phone Questions & Answers] rignfool:
I would HIGHLY recommend not installing /e/

It is old... And unsupported.. and unless your tinfoil hat is itchy...

It's just LineageOS and MicroG...
[Essential Phone Questions & Answers] marcdw:
It is not unsupported. It is not old (though it is Nougat). Constantly updated. Is more than just LineageOS and microG.

Do not spread FUD. Seriously.

[MENTION=10090842]neXussT[/MENTION], I would suggest downloading the latest various stock ROMs, Pie, Oreo, Nougat, whichever or all. Have them at the ready on your PC/laptop. You could always fastboot flash the originals if things don't work out.

https://xdaforums.com/showthread.php?t=3701681

[STOCK][DUMPS][FIRMWARE] Essential stock firmware and rom dumps

You'll have to downgrade to Nougat firmware first before trying /e/OS anyway so I doubt you can have Pie or Oreo on one slot and /e/OS on the other.

I have /e/OS on the Essential and Axon 7 (multiboot with other ROMs). Last update was about a day ago.

Essential PH-1, /e/OS 0.7-n ROM, microG (NoGapps), XDA Legacy
[Essential Phone Questions & Answers] neXussT:
Thanks marcdw. Those are good tips. I would never have thought of a version difference causing issues. Cheers.
[Essential Phone Questions & Answers] rignfool:
I see your definition of old (3 versions behind) is different than mine...

Also... Merging 2 year old security patches and updating that which even CAF has moved on from... Is what I would call unsupported...
[Essential Phone Questions & Answers] marcdw:
Alrighty then.

I personally don't adhere to the notion that folks must run the latest and (not so) greatest because it's there. Let folks run what they want to run, be it old or new. Discouraging folks doesn't seem too cool. IMNSHO of course.

Moto G5s Plus XT1806, OmniROM 8.1.0, NanoDroid, MultiROM, XDA Legacy
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] crossover01:
Hi guys is anyone there can help me , bec everytime i wipe my DATA (Typing Yes) it erase also my Internal storage , so how can i flash ROM if its wiping my Internal storage ?
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] Zeyar Moe Lwin:
All you have to do is plug your phone in to your pc and just drag them (your rom files) to your storage. That's all
[Redmi K20 / Xiaomi Mi 9T Questions & Answers] Schnedi:
Or if you want, you can use an USB OTG.
[iPAQ rw6828, XDA Atom General] dragunov:
Hello ppl,

Can anyone tell me what is the average free RAM on an MWg Atom Life? After a soft reset, my free RAM is just 19MB decreasing hour by hour. With just 1 day without reset, it may reach 14-13MB with all (visible) applications closed from memory manager, isn't it EXTREMELY LOW?

Is there any way to manage free ram from registry?

Help would be highly appreciated.

Best Regards,

Konstantinos
[Samsung Galaxy S10+ Questions & Answers] jay876:
Hey guys,

I have the SD S10+. As the topic says, I do not see the ring light effect whenever I unlock/lock my phone. I have edge lighting etc all enabled but I have no idea why I have seen some phones edge and camera ring light up when the phone is unlocked but not mine.

Shouldn't the camera ring light up by default when you unlock or wake the phone without the use of any third-party apps?

Any assistance?
[Samsung Galaxy S10+ Questions & Answers] Gogolakis:
The camera ring light effect occurs when you unlock your phone with face unlock.
[Samsung Galaxy S10+ Questions & Answers] jay876:
Thank you for your response. I had no idea it only did that for face unlock
[Xiaomi Redmi Note 5 Pro Questions & Answers] Niko7u7r:
I had a problem trying to install the TWRP on my Xiaomi Redmi Note 5 Pro, is that when placing all the commands in the CMD to start in the recovery mode the cell phone appears as if it was turning on and stays like this, it does nothing more. Help please.

I would appreciate if you pass the ADBs and all the necessary things to install the updated TWRP.
[AT&T Samsung Galaxy S7 Questions & Answers] OooTanjaooO:
Hello everyone...I have recently rooted my phone everything seems okay but I noticed a major issue after rooting when I went to a day of school. The battery life has gotten SO BAD, my phone died 2x within the day and it was not a entire 24hrs. I would like to know what my options are because I can not find anything on my model. Also before the root my phone was also stuck on Android 6.0.1 and I have no idea why. Thanks everyone for your future replies....hopefully...
[Samsung Galaxy A50 Questions & Answers] jjh76:
For those interested in enabling this function that seems missing:

Downloaded SetEdit from Play Store (tip: blue gear on red background icon), scrolled down to "haptic_feedback_enabled" (was 0) and changed it to 1.

Afterwards I deleted the app, restarted the phone and the haptic feedback was still there.
[Samsung Galaxy A50 Questions & Answers] simonhcai:
Its not working,is there a setting somewhere?
[Samsung Galaxy A50 Questions & Answers] gakis1976:
It works great ...thank you very much.
[Samsung Galaxy A50 Questions & Answers] therealroyston2:
Wow you are awesome
[Samsung Galaxy A50 Questions & Answers] abhijeet1331:
Thanks man.. It works..
[Samsung Galaxy A50 Questions & Answers] svetlio359:
Ok i check this app

It look like have option for call recording

does some one try it yet

Or it is not up to thees settings
[Samsung Galaxy A50 Questions & Answers] jjh76:
I tried it but didn't see any change in the Phone menu
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
First, let me apologize for the rough guide I'm going to deliver I'll clean this up in due time.

1.) Let's get some files downloaded. So here is a guide by [MENTION=4222965]deadman96385[/MENTION] that details Qfil and the actual process of flashing.

2.) Let's incorporate that into my guide

* You'll choose the programmer from my TWRP folder

* You'll choose the rawprogram0.xml from my TWRP folder

3.) Time to flash....just press Download there's nothing else to do.

4.) Boot into recovery...do I need to explain how?

* Warning* Do not flash Magisk requires a separate boot.img I haven't made it just yet.
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] FF7CloudsNobody:
So with all this, what is the next step in the process for custom rom installs? Waiting on mine in the mail so I can begin looking into everything as well, sadly I picked the att variant so it looks like things will be more difficult for me.
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] GuestK00251:
good work [MENTION=4911249]Unjustified Dev[/MENTION] And [MENTION=4222965]deadman96385[/MENTION]
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Roms won't be ready any time soon this was just a preliminary step. And what do you mean by more difficult? I have the att version.
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] FF7CloudsNobody:
From what I've been reading up on, it had looked like the AT&T variant was more difficult to get through than the others. I could be wrong though. But thanks for this breakthrough!
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
I don't know about the other variants. Each firmware is signed so I can't test their Roms, but I used their updated 8.1 proprietary files to build Lineage.View attachment 4811467View attachment 4811468
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] FF7CloudsNobody:
Does going the old "data wipe then flash boot img without encryption" not work anymore? If so then my bad, been a while since I've worked with a phone that is locked down with signed firmware. Was looking into doing that right now.

Edit: And I don't mean via flashboot because first boot should cause it to resign
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] Drakosha:
AT&T

Hello!

Thank you for the first ray of light :) Please, can you answer some questions?

1) As far as I know, AT&T version of Z999 has locked bootloader. Have you tried this TWRP with AT&T Z999 (not T-mob, China or Russian)?

2) As far as I know, AT&T version of Z999 has non-standard EDL mode and until now there was only one tool capable of flashing it, "Uni-Android Tool" for $49. The usual QFIL doesn't see 9008 COM-port on this phone. So, how does your TWRP gets flashed? Or is the included "firehose" an already patched one for AT&T Z999?

3) If all of these works, can root be (some day) obtained with locked bootloader?

I live in a country with GSM 900\1800, UMTS 2100 & LTE B3 & B20, so right now my Z999 is useless as a mobile device & works only as a small tablet. The root is totally necessary for me to unlock additional bands & I have faith in You :)

Thanks once again,

WBR - Draco.
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
1.) I have the att variant

2.) The all have edl mode I sniffed the firehose from uniandroid and had a friend reconstruct it to get it working. And the usual qfil does see the phone. You're more than likely in dfu mode and not edl. Uniandroid can send the phone from dfu to edl. You can adb reboot to edl to get in 9008. The issue was the programmer was incorrect.

3.) Root can probably be obtained I just had no interest. I'll look into it later if I have time. Also I'm not sure if you can unlock more bands never looked into that before.
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] Drakosha:
Great!

Thanks for the answers! Wonderful news, the ability to flash AT&T phone with QFill changes everything. As for the bands, I've seen a lot of articles on how to unlock Qualcomm phones with NV editor, and had success with several Nexus-es & LG's. Let's hope that after (if...) root is obtained, one of the methods works. It will literally breath the new life into this phone & will make it useful everywhere in the world.

WBR, Draco.
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] FF7CloudsNobody:
Just an FYI, only running this didn't work for me, I changed the img to recovery.img and used the firehose with the stock files, I edited the boot though to remove secure boot.
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] Drakosha:
Root

Hello!

Any news on root or, perhaps, some ROM like Lineage? :)

WBR, Draco.
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] ehsan96696:
Any News?

So I tried flashing my bricked Axon M with the provided firehose file, and using provided B37 firmware, but I keep getting an error associated with "userdata.img is 0 bytes!" and if I delete the file, I then get an error stating "userdata.img could not be found!" any ideas?
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Edit rawprogram0.xml where it says userdata.img edit it to be "" basically telling qfil don't flash it. Alternatively use miflash
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] ehsan96696:
Thanks, I did get past that error, but now it is stuck at https://imgur.com/YzyzPNP
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Use miflash
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] ehsan96696:
How? Whenever I pick the folder with the firmware it just sais "couldn't find flash script"
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] Drakosha:
rawprogram0.xml

Here, just use the attached rawprogram0.xml (AT&T B37) with QFil
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] ehsan96696:
Tried as specified and it gets stuck here: https://imgur.com/xMynQ3h
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] Drakosha:
Do you have spaces in your username? Put firehose programmer file inside the firmware folder, and put the whole folder in C:\Z999 (without any spaces or long filenames). Run Qfil as admin. And never flash phones from DESKTOP...
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] ehsan96696:
Did as you requested, still using your provided rawprogram0 file and B37: https://imgur.com/Bioy98t
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] Drakosha:
Check "Configuration" in your QFIL. See attached image. If all is correct, then perhaps you should reinstall qualcomm drivers \ try other QPST version, or (better) try different PC. And of course DO NOT USE USB 3.0 (blue) ports!
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
For miflash the programmer has to be in the root of the firmware folder. I never got qfil to work on full firmware it won't flash system it'll hang. But it will flash anything else.
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Also let's stay on topic if you create another thread I'll help if you can't get it working. I'll be fixing this thread up when I get home
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] ehsan96696:
Got it, my apologies. I made a new thread here: https://xdaforums.com/axon-m/development/attempt-to-unbrick-axon-m-provided-t3965300
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] GJSmith3rd:
Flashing recovery is not working for me either. Can you provide a few quick details or references about removing secure boot? I'm not sure this is needed in my case but I willing to look further into it.

I was able to flash B37 but somehow my TWRP flash is not taking even though the log shows all is well. This seems odd as I successfully flashed stock ROM from (ZTE/Z999/fujisan 7.1.2/N2G47H/20180822.110344 user/release-keys) to (ZTE/Z999/fujisan 7.1.2/N2G47H/20181015.010030/user/release-keys).

Any advice is welcome.
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] FF7CloudsNobody:
I am currently working on getting my flashing setup back after replacing my motherboard in my laptop and having to (unfortunately) switch from uefi to bios on it (effectively wiping everything) so once I discover the setup that worked for me, I will make a zip that has the program along with my modded files. I may just end up editing an edl tool such as the axon7 one made by [MENTION=4911249]Unjustified Dev[/MENTION] however that method requires me to properly unsparse the system.img for this device and I was working on a Windows computer at home over the weekend. I need to figure it out anyways because I soft bricked my phone while working on a ROM

Edit: got the setup back but I gotta mess with it a little prior to sharing

Edit 2: so I can either share the current setup that has the twrp and a semi-modified boot (just changed a few settings) or we can wait for me to rebuild the files to enable the fastboot (currently in the process of doing)

Sidenote: I will be making my own post soon for testing some setups I've made, just need to clear out some issues first.
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] sev7en:
Good morning,

any update about?
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] Jemini024:
you are awesome sir...if i can help in anyway just let me know
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] ZeroTheSavior:
Flashing recovery is not working for me even though the logs say it transferred. And yes my memory is marked as EMMC.
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
There's a typo in the rawprogram XML file
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:


<program start_sector="1181696" start_byte_hex="0x24100000" sparse="false" size_in_KB="65536.0" readbackverify="false" physical_partition_number="0" partofsingleimage="false" num_partition_sectors="131072" label="recovery" filename="recovery.img" file_sector_offset="0" SECTOR_SIZE_IN_BYTES="512"/>
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] ZeroTheSavior:
I see.

I was able to flash and boot TWRP by copying the recovery line from rawprogram0.xml of an official firmware.

Now I'm getting "your device is corrupt" messages and it won't boot. Is that intentional? It's because of verified boot, right?

edit: tried flashing stock firmware again. It hangs at 3.10% when sending system.img. I probably hard bricked it. Oh well. I guess I shouldn't touch things when I don't know if I can unbrick them.

edit 2: unbricked by flashing everything except system.img. But I don't know where I would go from here. Phone still says it's corrupt. Guessing at this point it doesn't really matter what I flash, it's going to keep saying it's corrupt. Even tried flashing system.img from TWRP, no change.

Programmer gives this message: 01:48:38: DEBUG: Only 361472 bytes written of 1048576 requested, attempt 1 of 100

edit 3: Somehow managed to brick it even worse and now I can only access stock recovery, I can't boot into FTM and EDL won't accept the programmer. The only thing I can do is DFU, jumping from DFU to EDL just makes the phone not accept the programmer.
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] Unjustified Dev:
Sounds like data couldn't decrypt successfully. I'll pm you my email and I'll help you get it back working.
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] ZeroTheSavior:
I was able to unbrick it using an EDL cable and following the instructions in this thread.

Somehow the second time flashing twrp caused no issues.

Oh well. At least it worked and now I know how to resurrect my device when I screw it up again.

It still shows the corrupt boot screen, but I prefer being able to choose to reboot into recovery anyway.
[ZTE Axon M ROMs, Kernels, Recoveries, & Other Deve] loopdeer:
If you ever want to get rid of the corrupt boot screen, just use the following command: adb reboot "dm-verity enforcing"