yashsingh1/xdaforums huggingface dataset:
[POCO M3 Pro / Redmi Note 10 / 10T 5G] Phuocl Loi Le:
Has your phone been repaired yet? How much would you pay? My phone is broken like your phone.
[POCO M3 Pro / Redmi Note 10 / 10T 5G] Free Software X:
1. power on phone insert usb cable mobile show dm-verity corruption option then quick click 3 time volume up and down

your mobile skip restarting

2. after phone on. go setting developer option oem on and mobile go to update option and update your phone .
[POCO M3 Pro / Redmi Note 10 / 10T 5G] Free Software X:
Free Solution in this video
[POCO M3 Pro / Redmi Note 10 / 10T 5G] wetito:
nice tip!
[POCO M3 Pro / Redmi Note 10 / 10T 5G] heyika26:
how to do this pls?
[POCO M3 Pro / Redmi Note 10 / 10T 5G] dimension_z:
You must have Minimal ADB and Fastboot installed in your PC.

After installing it, open it.

Write exactly the command line above.

Connect you phone via USB while is in FastBoot Mode*, with your PC.

* For FastBoot Mode on your phone, Turn OFF your phone.

Press VOL Down & Power Button for some secs together.

** Not sure if this is necessary ,but before doing all these, you have turned ON Developer Options on your phone. (search google how to enable Developer Options)

OEM Unlocking Checked & USB Debugging Checked.

Press Enter and you're done.

For me it worked!
[POCO M3 Pro / Redmi Note 10 / 10T 5G] surpriserose:
it worked on me after getting that persistent corrupt error message during booting.
[POCO M3 Pro / Redmi Note 10 / 10T 5G] dimension_z:
So you fixed the corrupt error message? Or still exists?
[POCO M3 Pro / Redmi Note 10 / 10T 5G] surpriserose:
It was fixed but I was using SuperiorOS back then.
[Huawei P10 Lite Guides, News, & Discussion] meechyy:
1. Root with your gsi's recommended method and type of magisk

2. Download an app called 'Performance Tweaker (Root)'

3. Open it and grant it root permission

4. Change CPU Governer to 'Powersave' with the app

5. Enjoy!
[Tilt, TyTN II, MDA Vario III General] swiftgs:
Titel says enough, I put my kaiser in the washing machine, and offcourse it was dead... After drying it for 3 weeks I decided to put the power back on. It seems its alive, vibrate when poweron and charling light is orange. But no display at all... :S

Yesterday after 2 months (got a new diamond from the insurance and was travelling) I hooked it up to my laptop. And strange enough, activesync found it instantly, also is the tytn registred in the wifi network and i find him with my diamond on bluetooth as well.... its also possible to explore the device and copy paste etc. etc.

So know a question to a expert, can I roughly take the conclusion that the mainboard is still intact, and that the LCD is dead, or can it also be because of a damaged/lifted flex cable etc. Is there any way to check if its because of flex cables/mainboards issues or caused by a broken LCD?

If its not to expensive Ive got a new project :P:P:P

edit: LCD screen has been replaced and is fully working now :D All functions are still up and running, GPS, cameras, wifi etc. etc. The only part that isnt working is the keyboard. Some keys react, but most of them are dead. Does anybody know a shop on the internet that sells a complete keyboard unit incl. cable? Searched ebay but i didnt fine one so fast!

thanks in advance!
[Tilt, TyTN II, MDA Vario III General] swiftgs:
ok,

I opened the kaiser completely, and after cleaning assambled him once more. After power on, I now see things on the lcd, touchscreen is working, but there is no backlight. So it isnt usable at all. For one second the backlight jumped on as well, but its now dead (flicker sometimes). Is this the LCD of is this another problem?

pls advice

cheers
[Tilt, TyTN II, MDA Vario III General] joihan777:
There may still be soap residue inside

There may still be soap residue inside, which conducts electricity.

You may want to find a way to safely rinse what you can, then dry by surrounding components with silica gel to absorb any moisture.

I did that to a camera a while back and it worked.
[Tilt, TyTN II, MDA Vario III General] swiftgs:
cleaned the whole phone with gel, but the lcd screen stays on at about 50 procent brightness, whatever i changed it wont go to full (after cleaning it was at 100% for about 5 minutes)

so i guess a new lcd will do the job...

tnx for the tip!
[Tilt, TyTN II, MDA Vario III General] luanda:
try to imerse the phone on a bowl of RICE! yes rice for 48 hours.

my daughter droped a blackberry on the toilett and after the rice treatment

is working fine!!!!

:cool:good luck
[Tilt, TyTN II, MDA Vario III General] swiftgs:
Will try that as well... however its a long time ago already!! :(

But the conclusion now is that its fully functional besides 2 things:

-LCD (flickers and is not at full brightness)

-Keyboard (some letters work, some dont...)

Does anyone know a site who ship these parts to norway?

The good thing is... dismantling a kaiser and rebuild it takes only 20 minutes :D
[Tilt, TyTN II, MDA Vario III General] branko.savic:
It figures you are from Norway! ;) (Sweden here!)

Why did you put your kaiser in the washing machine anyway? LOL :p
[Tilt, TyTN II, MDA Vario III General] swiftgs:
haha, its a malfunction in the brain... when you drink to much beer, and decide to wash your clothes, then it goes wrong!

skål :)
[Tilt, TyTN II, MDA Vario III General] fizzie:
My daughter wears a hearing aid takes it off at night and puts it in a box type device called DryStore by Global I think. It removes ALL and ANY moisture from within.

Well one day, same thing, she washed her cell phone in the washing machine. I took her phone, took the battery out, opened it up as much as I could and put it in the DryStore for 24hrs.

After that put the battery back in, turned it on and it worked perfectly. It was not a Kaiser but the idea is the same. That thing litterally gets all the moisture out. It is an AC powered device and not a toy. I think it is cheaper than a new LCD and Keyboard. If your device is salvagable this will do it.

If you do not want to buy one then find a hearing aid store and see if they will do that for you instead

Best of luck to you!
[Tilt, TyTN II, MDA Vario III General] branko.savic:
Okey that teaches you to "dont drink and wash!" lol :D
[Tilt, TyTN II, MDA Vario III General] swiftgs:
Updated first post, can someone help me out with this part, it seems unable to find! :mad:
[Tilt, TyTN II, MDA Vario III General] fone_fanatic:
cnn.cn has this keyboard Dont think it includes the ribon cable and its out of stock.

I'd suggest keep on ebay and search for a damaged kaiser..
[Tilt, TyTN II, MDA Vario III General] swiftgs:
Nope, it doesnt include the ribbon, and i think i need that one as well :D anyway i will check ebay every day, but if someone has a good idea Im in for it.

I see that broken kaisers change owner for about 150 dollars, I have to admit, thats to expensive in my situation! Because everything is working ok (use it on daily base, seems ive got a fat touch cruise without the keyboard)!

cheers!!!
[Tilt, TyTN II, MDA Vario III General] burtcom:
this?

http://www.ppctechs.com/HTC-Kaiser_971/repairs/Main-Keyboard-Assy_1091-372.htm
[Tilt, TyTN II, MDA Vario III General] swiftgs:
This is excactly the part i need! but I need it in qwerty, not qwertz. And 69 dollars is actually quite expensive haha :D
[Realme 7 ROMs, Kernels, Recoveries, & Other Develo] Vadd99:
ColtOs 7.4 Tipsy unofficial Realme 7/ Realme Narzo 20 pro

••••••••••••••••••••••••••••••••••••••

Version : 7.4 | Tipsy

Build date : 23/10/2021

Build type : Vanilla

Device : RMX2151

Maintainer : vadd999

Source :

Device : https://github.com/vadd99/device_realme_RMX2151-1

Kernel : https://github.com/vadd99/kernel_realme_RMX2151

Vendor : https://github.com/vadd99/vendor_realme_RMX2151

Changelog :

Note :

Download : here

Screenshots :

View attachment 5440065

View attachment 5440067

View attachment 5440065View attachment 5440067

View attachment 5440069

View attachment 5440073

View attachment 5440069View attachment 5440073
[Realme 7 ROMs, Kernels, Recoveries, & Other Develo] jerryhou85:
Hi @Vadd99 , thanks for posting this. Coud you please check your inbox? I just sent you a message. Thanks.
[Realme 7 ROMs, Kernels, Recoveries, & Other Develo] Vadd99:
Source :

Device : https://github.com/vadd99/device_realme_RMX2151-1

Kernel : https://github.com/vadd99/kernel_realme_RMX2151

Vendor : https://github.com/vadd99/vendor_realme_RMX2151
[OPPO Find X3 Pro] ecomaki:
Still excited after the ColorOS 12 global launch, already tried most available features. How about you? Whats your favorite so far?
[Moto G5S Plus Questions & Answers] ALIENATOR200:
Help me!! PLEASE!!
[Realme 8 Pro] StratOS_HTC:
Europe Realme8 Pro (RMX3081GDPR_11_A.41) still doesn't have a unlock bootloader option.

That is the answer from EU Realme service.

C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash boot magisk_patched.img
Sending 'boot' (65536 KB)
FAILED (remote: 'Download is not allowed on locked devices')
fastboot: error: Command failed

From the debug of the flashing procedure done in the "Download" fastbootd mode.

Since the *.opf contains the blocks and binaries (elf) to be extended in the download mode guess the flashing of the single block cannot be done. Bootloader cannot be unlocked since the HAL is not included in fastbootd.

Weird thing is that the whole package of the zip included the files inside ofp and flashing ELF binaries inside has to be "flashed". Guess only the checksum values are not being verified during the procedure.

Extraction procedures of opf files are available, compress version are not available.

Since dev/block partition are not accessible (Permission denied) in normal state we cannot change particular block/partition.

Bootloader cannot be unlocked.

It's hard to create the root from this state.

Hope for the best .... to be solved ....
[Realme 8 Pro] StratOS_HTC:
After engaging "EDL" mode in witch the QC things are not implemented ?? (or need some extra approach) or this SAHARA MODE use some other drivers ...

Been able to partialy info and state from QC QDL mode :

View attachment 5449575

So we are on a good position to go forward from here ...

For unlocking SBL guess we need the SN, HASH1 and HASH2 to unlock and load from OEM Secondbootloader.

For flashing via MSM the HWID number is also important to been able to flash correctly.

Need some extra USB debugger in this mode or while flash via MSM.

Help appritiated.
[Realme 8 Pro] StratOS_HTC:
- MSM HW ID - The Hardware ID of the MSM chipset. Burned in a QFPROM fuse.

- Serial Number - The serial number of the device. Burned in a QFPROM fuse.

- OEM_PK_HASH - The hash of the entire root certificate which is blown into the QFPROM fuses of the device. the root certificate is included in the X509 certificate store of the SBL1 image. (Thanks Tal Aloni)

- Log buffer - Get a raw log buffer of the failed boot process (?assumed? corred me here)

- SBL SW Version - Returns the SBL version.

GitHub - openpst/libopenpst: A multi-platform C++ library for working with Qualcomm MSM devices

A multi-platform C++ library for working with Qualcomm MSM devices - openpst/libopenpst

github.com
[Realme 8 Pro] StratOS_HTC:
EU (GDPR) versions of Realme 8 Pro won't have a option to unlock bootloader. So only official flashing or use the EXPORT Flash to get the unlock bootloader.

Also no other option won't be available if bootloader locked.

That means root, custom roms ... :(
[Realme 8 Pro] StratOS_HTC:
Got a feedback with emmcdl program in EDL :

emmcdl -p COM3 -info -verbose

Version 2.15
SerialNumber: 0xnot shown
MSM_HW_ID: 0x001490e1
OEM_PK_HASH: 0xd9a31a8af5966a594e587c615a96f9defd4cf18f86e84d966876706ada8b3669
SBL SW Version: 0xb5119f8f
Status: 0 The operation completed successfully.

emmcdl -p COM3 -gpt

Version 2.15
Finding all devices in emergency download mode...
Qualcomm HS-USB QDLoader 9008 (COM3)

Finding all disks on computer ...
0. \\.\PhysicalDrive0 Size: 953869MB, (1953525168 sectors), size: 512 Mount:D:, Name:[Data]
1. \\.\PhysicalDrive1 Size: 244198MB, (500118192 sectors), size: 512 Mount:C:, Name:[]
\\.\PhysicalDrive3
No valid GPT found
Status: 13 The data is invalid

emmcdl -t - p COM3

Version 2.15
Running performance tests disk -1
Finding all devices in emergency download mode...
Qualcomm HS-USB QDLoader 9008 (COM3)

Finding all disks on computer ...
0. \\.\PhysicalDrive0 Size: 953869MB, (1953525168 sectors), size: 512 Mount:D:, Name:[Data]
1. \\.\PhysicalDrive1 Size: 244198MB, (500118192 sectors), size: 512 Mount:C:, Name:[]
\\.\PhysicalDrive-1Successfully opened volume
Testing this stuff out
Sequential write test 4MB buffer 19922944
status 6 bWriteDone 0 bytesOut 0

This is the last thing to do. Don't want to mess with certs and hashes.

Guess I'll have to flash the EXPORT IN version to be able to do more.

To be able to operate in EDL first a "info" handshake should be initialized and then you can send other.

If needed the file operation I get the same error like in Qfil.

Version 2.15
Downloading flash programmer: prog_firehose_ddr.elf
Successfully open flash programmer to write: prog_firehose_ddr.elf
Waiting for flash programmer to boot
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: Binary build date: Dec 19 2019 @ 20:53:50" /></data><?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: Binary build date: Dec 19 2019 @ 20:53:50
" /></data><?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="INFO: Chip serial num: not shown (0xnotshown)" /></data>
Programming device using SECTOR_SIZE=512

<?xml version = "1.0" ?><data><configure MemoryName="emmc" ZLPAwareHost="1" SkipStorageInit="1" SkipWrite="1" MaxPayloadSizeToTargetInBytes="1048576"/></data>
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Verifying signature failed with 3" /></data>
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Authentication of signed hash failed 0" /></data>
<?xml version="1.0" encoding="UTF-8" ?>
<data>
<response value="NAK" rawmode="false" /></data>

---Target returned NAK---

<?xml version="1.0" encoding="UTF-8" ?>
<data>
<log value="ERROR: Failed to read XML command -1" /></data>
ERROR: No response to configure packet

Status: 21 The device is not ready.
[Realme 8 Pro] StratOS_HTC:
Loaders for Oppo/Realme/Oneplus

OEM:Oppo/Oneplus MODEL:0000 HWID:0000000000510000 SWID:0000000000000003 SWSIZE: PK_HASH:401e4aff39a09344153e776879cac4b407b811b62229fb6ac0d2a578662ef528877e89263d856bc9fdd0140498568836 0000000000510000_401e4aff39a09344_fhprg.bin 695676
OEM:Oppo/Oneplus MODEL:0000 HWID:0000000000510000 SWID:0000000000000003 SWSIZE: PK_HASH:d9a31a8af5966a594e587c615a96f9defd4cf18f86e84d966876706ada8b366947637bf3b443e3012580db52e0edf216 0000000000510000_d9a31a8af5966a59_fhprg.bin 665884
OEM:Oppo/Oneplus MODEL:4D6D HWID:0000000000514D6D SWID:0000000000000003 SWSIZE: PK_HASH:7c15a98db4e70963715f51c8da39c1e66fc1c3334e95f4c6a5627da6a49c842f06b43e8de1f589fc36ce1135c7fa5aa2 0000000000514d6d_7c15a98db4e70963_fhprg.bin 701440
OEM:Oppo/Oneplus MODEL:0000 HWID:000520E100510000 SWID:0000000000000003 SWSIZE:00000148 PK_HASH:c8b4fe1cd7221f8816f3f097277e9d7eeed74717761ff773a4267d70041b35d1 000520e100510000_c8b4fe1cd7221f88_fhprg_peek.bin 341244 OEMVER:ubuntu-96-22 QCVER:BOOT.BF.3.1.5-00035 VAR:WAADANAZA
OEM:Oppo/Oneplus MODEL:0000 HWID:3006000000510000 SWID:0000000100000003 SWSIZE:000001C8 PK_HASH:0cf6c9ce73e7368aff1f442f67f9bc35372162c68561716c0ee2e43c5177553b 3006000000510000_0cf6c9ce73e7368a_fhprg.bin 669808 OEMVER:ubuntu-122-95 QCVER:BOOT.XF.1.4-00258-S660LZB-1 VAR:Sdm660LA
[Realme 8 Pro] StratOS_HTC:
Scatter file with extracted config and other needed info for GDPR version .44 of the rom.

Send a <CONFIG> :)
[Realme 8 Pro] StratOS_HTC:
Have prepared the QFIL xml to flash and patch ... Tested via Qfil ...

but since firehose is using signed validation it's useless to do anything else more ...

Even some FS/system oppo and flashed QC ELF files are digitally signed so no RE.
[Realme 8 Pro] StratOS_HTC:
program,configure,sig,nop,firmwarewrite,patch,setbootablestoragedrive,ufs,emmc,power,benchmark,read, getstorageinfo,getsha256digest,erase,peek,poke are the commands to communicate with firehose via XML.

Emmcdl don't have a full verbose info or log, like current Qfil, we get the sign request from the firehose after the initial handshake and info it sents the <configure>.

From the Qfil log or emmcdl we don't get the sign request for further authentication.

We get the Signature Request we have to Authenticate, since logs in current clients are not implemented for this we have to write a prog 4 it and break the encryption request.

After it we get the non requested error :

INFO: TARGET SAID: 'ERROR: Verifying signature failed with 3'

INFO: TARGET SAID: 'ERROR: Authentication of signed hash failed 0'

Also with the ETS HQXA emmc prog I get the MD5 via software version verification for only production used - Avtomatic verification mode.

Really weird is that it can do it in the phone DIAG mode not in the EDL ?

View attachment 5497519

We'll have to wait 4 it ... or capture the MSM tool communication on the desired port to see what is happening further.

Just for info I'll post the initial program for flashing via Qfil and port trace and initial xml.

QFIL Sorting TAGS to ensure order is <configure>,<erase>, others, <patch>,<power>

via others there can also be sig as signature.

4 now this is it ...

The problem will be setting the (new) correct NV also I guess.

IF first 5 numbers of PCB (Project ID) is different.
[8525, TyTN, MDA Vario II, JasJam ROM Development] austinsmartie:
Hi - I continually receive this error when trying to download applications: "An unexpected error has occurred in CRCinAU.exe" When I choose Details on the error, I get a list of errors starting with "CRCinAU.exe NotSupportedException at System.Net.WebRequest.Create....."

I have tried to use the updater with a couple of different CRC ROM versions, including 13 and 14.1 and I get the same results. I have also tried selecting different applications from the list singly and in combination with the same result.

I am running a Hermes100 (Cingular 8525) with HardSPL.

I get the error regardless of whether I am trying to access Device Update via WiFi or ActiveSync.

Any thoughts or suggestions?

Thanks,

austinsmartie
[8525, TyTN, MDA Vario II, JasJam ROM Development] joshkoss:
post it in his thread man!

http://xdaforums.com/showthread.php?t=364216
[8525, TyTN, MDA Vario II, JasJam ROM Development] austinsmartie:
Done. Thx.
[Huawei Mate 20 X Guides, News, & Discussion] avreen:
Is there a way to get harmony os2 on global. Version mate 20 x EVR L29?
[Introductions] hiwauk47:
bonjour ,je m appelle sebastien 47 ans lot et garonne . j ai trouver votre forum par hasard sur google afin de donner une nouvelle jeunesse a ma tablette samsung tab 4 10.1 SM-T530 mais etant novice c est un peu compliquer pour moi de m y retrouver . vous faites vraiment du super boulot,donc j espere trouver mon bonheur ici . merci d avance .
[Introductions] orb3000:
Welcome to XDA, English is the preferred language in here, you can always use google translate!
[General Questions and Answers] monsiu:
Hey.....so i have twrp and after installing my lineage of choice i go to flash gapps

it flashes successfully (i install immediately after lineage)

But upon setup and boot up....i cant download even a single app from the PLAY STORE as it displays an error.

Its quite random as i find that the error disappears when i flash again but also it might not and so am confused on what to do and what am doing right to skip that error

Summary: I have just done a clean install of lineage and gapps but when i want to download an app it shows an insufficient storage error....when i still have like the whole phone storage to use. (no restore from backup was done so phone is empty)

Help....

Thanks :)

Edit: i made it clear its an issue in playstore not in twrp...as i can handle up until stock gapps.
[General Questions and Answers] Deleted member 1890170:
The error gets triggered if not enough free storage space in partition /system and/or /vendor. Just try with micro version of GApps.
[General Questions and Answers] Droidriven:
Or use pico gapps
[General Questions and Answers] monsiu:
i use gapps
[General Questions and Answers] monsiu:
i use pico and i can even use stock if i want, device is quite capable :) ...im saying that i cant download an app in play store as it shows an insufficient storage error hence am confused as i have storage cause i just finished a clean install of lineage
[General Questions and Answers] Deleted member 1890170:
Then storage space in /data and/or /cache partition isn't sufficient. Take note that when downloading an app from Google Play Store in addition to APK's download-size extra ~500MB are needed.
[General Questions and Answers] Droidriven:
Have you tried going to system settings>applications then finding and selecting the Playstore on the list of apps then tap "storage" then wiping cache and storage for the Playstore app, then reboot the device?

Or

Have you tried booting into recovery and wiping cache and dalvik cache then reboot the device?
[General Questions and Answers] monsiu:
i have my whole phone storage as i just flashed lineage and gapps successfully....granted its not a lot of storage 😂(its 16gb) i should at least be able to download a 6.1 mb app in playstore....right?
[General Questions and Answers] monsiu:
ye i tried the second one and the first one( i didnt restart though) but its not a playstore issue as even in the device file explorer it does not show the internal storage hence the files are not even accessible but the storage size is still seen in settings but i just cant access them....its weird
[General Questions and Answers] Deleted member 1890170:
When in Android's Settings menu tap Storage, tap Advanced, wait for seconds the internal storage gets loaded, tap on internal storage: you'll be shown all the categories in your phone's internal storage. From this you can attain which storage folder or category is taking up huge amount of space in your phone internal storage.
[General Questions and Answers] Droidriven:
Try another clean install of your ROM and a different gapps package, there may be something wrong with your gapps file, it has been known to happen.

Or, try a clean install of your ROM but do not install gapps, then, reboot into system but do not sign in yet, then power off and boot back into recovery and flash your gapps then reboot. This has been known to fix many issues with flashing ROMs and gapps.
[General Questions and Answers] jays note 2:
Simplest way to fix your problem is too head back into Twrp recovery and perform a Factory Reset.
[General Questions and Answers] monsiu:
your solution seems as the most likely to work so i have marked it as the solution but what i did was just flash stock rom and mounted system in the stock recovery and cleared cache and did a factory reset and boot into the stock rom then i reflashed twrp and flashed the lineage and gapps

that worked

On second thought... im marking this as the solution cause i feel its assured to work cause you are going back to the stock rom and its default system partition and i never had issues flashing when i came from the stock rom.

i even flashed the aroma gapps

Thanks for the help guys...i appreciate it 😁
[General Questions and Answers] monsiu:
this did not work....i cleared everything and even formatted data
[General Questions and Answers] THE-TECH-GUY:
I don’t know if you found the solution but if didn’t format data clean your phone

Download the version you want make sure both the lineage and gaps are the same in my case I got lineage-18.1 and mindTheGapps 11

Because lineage 18.1 is 11 I tried other gapps but most didn’t work

Then after copy the both files directly in phone internal storage or if your phone supports SDcard put them in there

1st install the gapps.zip then the lineage.zip then reboot system and vwala 🤲🏽 Insufficient storage gone everything should work including all google apps if chrome or Gmail is missing download in playstore or use browser to download The apk