yashsingh1/xdaforums huggingface dataset:
[Touch Diamond, MDA Compact IV Themes and Apps] Wolfblood:
OIC, I'm useing SwiftBL WWE Diamond v6.5 Full w/(16Mb Pagepool) and have try the Original hTC 1.93 ROM is work fine.

I'll take a time to try Duttys V2.3a WWE in my holiday, Let's try :)
[Touch Diamond, MDA Compact IV Themes and Apps] tommm:
I never had a stock 1.93 ROM - you mean that on stock ROM it works without any probs??

btw: this Duttys ROM I got from yesterday n till now didn´t find any bugs;)
[Touch Diamond, MDA Compact IV Themes and Apps] Wolfblood:
Yes, hTC has release a ROM update for Diamond v1.93 on July. You can check with your country hTC web site. Sign Up as Member is MUST before you check with hTC.

Here is the ROM info on my country hTC web site:

=====================================

hTC Touch Diamond English ROM Code Update (2008/07/23)

ROM version: 1.93.831.1 WWE

ROM date: 07/18/08

Radio Version : 52.29.25.12H_1.00.25.05

* You can check device ROM version from Start -> Setting -> System -> Device Information -> Version.

Description:

1. Fixed sometimes no signal issue.

2. Fixed no action while touching navigator control in camera mode.

3. Fixed some files in internal storage which cannot be listed.

4. Fixed SMS sound alert notification delayed issue.

5. Improved audio quality after audio booster is enabled.

6. Improved TouchFLO 3D tab switching and movement speed.

7. Improved home page loading speed.

8. Turned off the 5-second auto screen off function when screen is turned back on by pressing power key during a voice call. Screen off timeout will follow system power setting.

9. Added random access bar to the right hand edge of the screen for selection of weather countries and cities.
[Touch Diamond, MDA Compact IV Themes and Apps] tommm:
OK stock ROM, but has anybody get it to work on cooked one??:confused:
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] CrushedMango:
Does anyone has serious screen bleeding, nearly 20% of the screen is lighter when the background is gray.

Is this a hardware or a software issue?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] arkadia_1969:
Most people who have such a problem say it is a screen-hardware defect
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] Dariusdd:
it is something inherent to AMOLED displays, it's fairly common even on OLED TVs, and yes, it is a hardware issue
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] CrushedMango:
Do you think I should return the phone?
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] blackhawk:
Design defect. It may be firmware, software or hardware.

I see none on my on my Note 10+ with ScreenTest or when using. The curved sides show some optically induced differences which is unavoidable. This particular model is known for its drop dead gorgeous display.

There is no backlighting on AMOLED displays, each pixel is the light source so no bleeding should be possible. If the drivers aren't properly matched or there's uneven current sinking uneven lighting levels can occur.

With large displays the cost of rejects increases exponentially so quality standards may be lowered. Likewise maintaining tolerances and even current sinking on large displays becomes more challenging.

If the manufacturer doesn't have their act together enough to avoid this especially on a phone, I would return it.

It may be a fluke but QC should have picked it off before it left the plant.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] panchovix:
Hardware issue, it doesn't happen in my F3 and it didn't happen either on my Galaxy S8+ (both AMOLED).

You could return your phone for warranty, or just return it for money and get phone another model.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] CrushedMango:
Is the warranty still valid after unlocking bootloader?

Because I thouhgt it was a miui problem, but its the same when I used arrow
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] pl1992aw:
You can flash official MIUI fastboot ROM of your phone back and relock bootloader for warranty.

Check Xiaomi/Redmi/Poco warranty policy just in case.
[Xiaomi Poco F3 / Xiaomi Mi 11X / Redmi K40] CrushedMango:
Oh ok. Thanks!
[Touch Cruise General] triolight:
I'm trying to find a way to keep the screen on when I'm in a call but it turns of automatically every time. Is there any tweak to stop that?
[Touch Cruise General] chris10230:
try searching i have seen this before in a different thread
[Touch Cruise General] JIESSEL:
Yes, you can do it

Make a search in Tweaks for Polaris for example, you'll find which Key register you'll have to modify. I think you could find very quickly on the Mahmoud website.

BR
[Touch Cruise General] triolight:
it didin't work

I did searched , and found a tweak from another thread, but it didin't work.

any ideas?

thanks in advance
[Touch Cruise General] triolight:
Nevermind, S2U2 was causing the problem

Thanks all for the help
[Touch Cruise General] igoivo:
See trick N38 in

http://xdaforums.com/showthread.php?t=355277&page=19

Namely:

HKLM\Drivers\BuiltIn\RIL\EnableFastDormantDisplayDuringCall

change the value from 1 to 0 then soft-reset

It works in Polaris. Regards.
[OPPO A52 Questions & Answers] Contraplan:
Hoi everyone, i have a question and looking for a solution. After cracking my glass and replacing a aftermarket display&digitizer, an issue accured. The screen goes black after a while and i cant start up using the On an Off switch. The phone is still working i can feel fibration using the volume and on and of button. Sometimes i can use the display and of the sudden it truns black. I have to disconnect the battery and start up again.

I tried solving any proximity issues as the phone seems to use the camera when unlocking the screen . You can see a blue ring around the camera when pressing the button but it stops there. Then i went to disable all sensors. No help there. Last i switch of the use of the lock screen. It did help the phone can can be used for a few hours but then goes black again.

any explanations to why this happens and any solutions?

thank you in advance

best regards Vincent
[Xiaomi Mi A2 Lite Questions & Answers] Abi1210775:
Dear experts, my a2 lite suddenly turns off and at first when I connected to the charger, the light just blinking, and after I flashed a rom using flash tool just EDL mode is possible and sometimes I can turn it on but it keeps restarting. sometimes also I am able to bring up the fastboot screen and the command: fastboot getvar all shows me:

(bootloader) version:0.5

(bootloader) token:VQEBHwEQCLu3tv9Mjs6/iXki+g3VUAMFZGFpc3kCBO+CzA8=

(bootloader) battery-soc-ok:yes

(bootloader) battery-voltage:0

(bootloader) variant:QRD eMMC

(bootloader) unlocked:yes

(bootloader) secure:yes

(bootloader) version-baseband:

(bootloader) version-bootloader:MSM8953_DAISY2.0_20210513184102

(bootloader) logical-block-size:0x200

(bootloader) erase-block-size:0x200

(bootloader) display-panel:

(bootloader) off-mode-charge:1

(bootloader) charger-screen-enabled:1

(bootloader) max-download-size: 0x1fe00000

(bootloader) slot-count:2

(bootloader) current-slot:b

(bootloader) slot-retry-count:b:7

(bootloader) slot-success:b:No

(bootloader) slot-active:b:Yes

(bootloader) slot-unbootable:b:No

(bootloader) slot-retry-count:a:7

(bootloader) slot-success:a:No

(bootloader) slot-active:a:No

(bootloader) slot-unbootable:a:No

(bootloader) has-slot:userdata: No

(bootloader) has-slot:vendor: Yes

(bootloader) has-slot:system: Yes

(bootloader) has-slot:modem: Yes

(bootloader) has-slot:logdump: No

(bootloader) has-slot:boot: Yes

(bootloader) has-slot:persistbak: No

(bootloader) has-slot:persist: No

(bootloader) has-slot:mdtp: Yes

(bootloader) has-slot:bk6: No

(bootloader) has-slot:dsp: Yes

(bootloader) has-slot:splash: No

(bootloader) has-slot:bk5: No

(bootloader) has-slot:modemst2: No

(bootloader) has-slot:modemst1: No

(bootloader) has-slot:fsg: No

(bootloader) has-slot:devinfo: No

(bootloader) has-slot:mcfg: No

(bootloader) has-slot:tz: Yes

(bootloader) has-slot:bk4: No

(bootloader) has-slot:dip: No

(bootloader) has-slot:aboot: Yes

(bootloader) has-slot:misc: No

(bootloader) has-slot:keymaster: Yes

(bootloader) has-slot:cmnlib64: Yes

(bootloader) has-slot:cmnlib: Yes

(bootloader) has-slot:syscfg: No

(bootloader) has-slot:keystore: No

(bootloader) has-slot:mota: No

(bootloader) has-slot:rpm: Yes

(bootloader) has-slot:sbl1: Yes

(bootloader) has-slot:msadp: No

(bootloader) has-slot:apdp: No

(bootloader) has-slot:devcfg: Yes

(bootloader) has-slot:lksecappbak: No

(bootloader) has-slot:lksecapp: No

(bootloader) has-slot:bk3: No

(bootloader) has-slot:config: No

(bootloader) has-slot:limits: No

(bootloader) has-slot:DDR: No

(bootloader) has-slot:bk2: No

(bootloader) has-slot:bk1: No

(bootloader) has-slot:sec: No

(bootloader) has-slot:dpo: No

(bootloader) has-slot:ssd: No

(bootloader) has-slot:fsc: No

(bootloader) partition-type:userdata:ext4

(bootloader) partition-size:userdata: 0x57bbfbe00

......

Please help
[Xiaomi Mi A2 Lite Questions & Answers] Abi1210775:
why this happened and how can I solve it?
[Galaxy Tab 2 Q&A, Help & Troubleshooting] SoIomon:
I accidentally installed espressowifi build on my Samsung Tab 2 P5100. It works although the audio,youtube videos, and camera won't work. Then, I tried flashing an espresso3g Lineage OS then error 7 popped out saying "This ROM is not built for your device" (something like that). I looked at the build info of my device and its written that it has changed to espressowifi build. Any way to fix this?
[Galaxy Tab 2 Q&A, Help & Troubleshooting] HippoInWindow:
Which version of LineageOS in particular are you trying to flash?
[Galaxy Tab 2 Q&A, Help & Troubleshooting] SoIomon:
Lineage OS 14 - Nougat Android 7.1.2.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] SoIomon:
IDK what I did but my Tab is 3G version. I downloaded the Wi-Fi version and flashed it in my Tablet. It booted up and it works. Then issues came up, no sounds, cant play videos, and camera is not accessible. I then looked at the build and it was changed to espressowifi so when I tried installing the other compatible ROM with my device, it does not work. Because when I installed the espressowifi ROM, it also did change the build info of my device. So what can I do to fix it?
[Galaxy Tab 2 Q&A, Help & Troubleshooting] SoIomon:
I did go there
[Galaxy Tab 2 Q&A, Help & Troubleshooting] drnightshadow:
Wipe all than in TWRP, than reboot in TWRP again, after that use SD-card to flash the right vesion
[Galaxy Tab 2 Q&A, Help & Troubleshooting] SoIomon:
i think the lineage os ROM is buggy not really because of what I did. I will change to a more stable ROM. XDA Devs here say that go with OMNI ROM.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] drnightshadow:
For stability use RessurectionRemixOS 5.7.4 and don't use gapps. Gapps are pure trouble on prehistoric tab 2.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] SoIomon:
Ah, it did not work. Prolly gonna go back to stock ROM and back up my Custom ROM
[Galaxy Tab 2 Q&A, Help & Troubleshooting] SoIomon:
I finally fixed it on July 10, 2021. Here is what I did:

Downloaded the official firmware of Samsung Galaxy Tab 2 P5100.

I go to Bootloader (Odin Mode) and installed the firmware through Odin in my Computer.

Go to Recovery Mode (not TWRP cause I installed the official firmware) and cleared data & cache.

Powered the Tablet on and waited for 10 mins for its booting.

After its done, I downloaded KingRoot to root the tablet.

Rooted and I go to Odin mode again to install TWRP Recovery.

Go to Recovery Mode and installed the right Custom ROM for my tablet.

Opened and successfully its working af. Audio, Video, all are working.

PROBLEM: INSTALLED THE WRONG CUSTOM ROM ON MY DEVICE (espressowifi) MUST HAVE INSTALLED (espresso3g).

This problem lasted for 3 days xD.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] drnightshadow:
Wtf kingroot malware you recommended. Shuuush.. DONT USE THAT CR@P KING ROOT..

Install official ROM from odin,

Boot once, than go back to download mode,

Connect tab to odin and flash TWRP.

Boot to TWRP and wipe all than install custom ROM + magisk.. reboot to system

And viola all done.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] SoIomon:
I used it but ok. if its a malware, then use an antivirus. idc what you say, this is what i did.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] SoIomon:
i mean, you dont need a rooted phone for twrp recovery but thats what i did so shush. lmao. why so mad.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] drnightshadow:
Lol antivirus lmao malware in system lool

Good luck! When a virus get as root in system, no antivirus cant delete it. And Antiviruses on android suc.ks as h3ll.

Be carefull what you'll install on your device.

Mad?? I'm not mad but confused by your method lol. So complicated for nothing lool.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] SoIomon:
u find it, when your phone is rooted, you can delete it.
[Galaxy Tab 2 Q&A, Help & Troubleshooting] SoIomon:
then sorry, this is what I did. its your freedom if you want to follow. theres no virus on my system so idk what are you saying but ok. then just tell them not to install kingroot. i just installed it cause i wanted to. wtf is ur problem. this is my choice lmao
[General Questions and Answers] Leminsc8:
Hello, my english is bad but i tray it :)

I need to root my "Samsung XCover 4" with the last update of Android Pi (9.0) any owen experience?

first question is, an i backup the OS befor goes to a brick by rooting?

witch root tool is the best one for XCover 4 with Andi 9?
[Touch Diamond, MDA Compact IV Themes and Apps] detroix:
just wondering

when smsing.. can i have some kinda typewriter sound effect? it will be cool.. the sound has to be responsive.. and the interval just nice

reason: cool and nostalgic + always miss a button.. with sound.. can better know when i did press on the keypad..
[Xiaomi Mi 10T / 10T Pro Questions & Answers] rachitanand:
It's showing error extract tarfork after restoring bootimg it stops
[Asus ZenFone Max Pro M1  Guides, News, & Discussio] Hihellodfg1:
Hello i am not the maker of this kernel.

This is my first kernel post,

This is the kernel which has better battery backup.

Here is the Link to kernel

XXXXXX

Mod Edit: Link removed

Code:Your warranty is now void or not.i am not responsible for broken sdcard,phone etc.

sorry for not posting any of its features

I am a big noooob.So who are interested can try.

the whole thanks and source goes to the BENKz29

sorry for my bad english....

SCREENSHOTS:

View attachment 5357865
[Asus ZenFone Max Pro M1  Guides, News, & Discussio] rony raj:
cool
[Asus ZenFone Max Pro M1  Guides, News, & Discussio] TNSMANI:
MOD ACTION:

Thread closed and link removed.

Links to PPC sites are not allowed. Rule 13:
[Touch Diamond, MDA Compact IV General] phr3n1c:
Hey Folks,

well I've experienced a very bad problem. When I started to change my ROM again, my whole device hang up, nothing happened any more. No chance to do a Hard or Soft Reset, the Led-Ring does not even light up anymore when I plug in the USB. Neither via Notebook nore via outlet. I don't know whatelse to do, hopefully it's not dead...

Thx for all the answers and sry for my bad english...^^:)
[Touch Diamond, MDA Compact IV General] ady_uaic:
can you enter in bootloader mode? if you can, it's everything ok.
[Touch Diamond, MDA Compact IV General] studz:
Remove the battery for 30 seconds then replace it and see if it will then respond to any of the following... on switch/usb cable/bootloader mode/hard reset.
[Touch Diamond, MDA Compact IV General] phr3n1c:
Well... the Diamond doesn't respond to anything... It isn't even recognised by Windows...
[Touch Diamond, MDA Compact IV General] ady_uaic:
phr3n1c can you enter in bootloader mode with it? pressing volume down (on the left side) and reset in the same time, and keep holding untill 3 colour screen appears.
[Touch Diamond, MDA Compact IV General] phr3n1c:
Nothing happens... OMG i could start crying...
[Touch Diamond, MDA Compact IV General] borce_razor:
WTF! If don't enter even in bootloader, I only can say that its totally bricked. Sorry
[Touch Diamond, MDA Compact IV General] phr3n1c:
How could this happen? I just tried to install juices RoM, then it said that this isn't the right ROM for my Device, turned off the screen and.... nothing...

So there's no way for me to get this Diamond working again... I just got it for 3 weeks... 469€... mmh...
[Touch Diamond, MDA Compact IV General] PJ6363:
Keep trying to get bootloader mode...its very fiddely....

also try and charge your battery...was it at full charge before?
[Touch Diamond, MDA Compact IV General] Black93300ZX:
Don't give up hope just yet, I've seen a few people on here that thought they bricked their Diamond but a few of the major contributors of the forum were able to work them out of it. Not saying it's a guarantee of course, but definitely a possibility.

2nd what the guy above me said, just hold volume down and the power button and try to get to bootloader mode... You should really be able to get to this, and once you can you'll be all set.
[Touch Diamond, MDA Compact IV General] phr3n1c:
So the best thing for me is to leave this Thread here and wait for some answers I can try out...

Well... I use to read in this board since February and I always found all the answers to my questions...

This is the fact y this is my first post as well^^...

so i think i'll leave my xda alone 4 a while...^^ thx for all answers, upcoming and read...
[Touch Diamond, MDA Compact IV General] phr3n1c:
mmh.. so there's nobody who's got any idea... thought more people could help me... mmh...
[Touch Diamond, MDA Compact IV General] borce_razor:
Do you flashed Diamond HARDSPL-OliNex first ?
[Touch Diamond, MDA Compact IV General] prank1:
That is NOT the way to get into bootloader mode, if you have been trying that then there is no way you will enter the tri-coloured screen,

You need to press the power button as well as the volume down button along with the reset button to get into bootloader mode.

1) Take of the back cover of your diamond

2) Take out the stylus, notice a red dot in the bottom left corner? thats the reset button

3) Get your stylus ready to press the red reset button, but don't press it yet

4) Press and hold the POWER button and the VOLUME DOWN button, as well as holding down and pressing the reset button

5) After 3 seconds, let go of the red reset button but KEEP holding down and pressing the POWER and VOLUME DOWN buttons

6) Once the tri-coloured screen (bootloader) comes up, you can let go of the buttons.

That is how to get into bootloader mode, in depth. If that is not working that you have damaged your device quite a fair bit.

Remember if you didn't try pressing the power button to get into bootloader mode before, then there would have been no way you could have gotten into bootloader - try this method now and you might (hopefully) be flashing a new ROM in a matter of minutes.

Good Luck!
[Touch Diamond, MDA Compact IV General] phr3n1c:
what can i say..? nothing happens... don't know whatelse to do now... but... can the ROM really damage the diamond that far that it doesn't even light the LED ring under the screen if i plug it into the USB...

damned... whatelse to do now...? sell it on ebay?
[Touch Diamond, MDA Compact IV General] Kueh:
Another reason why I stay away from eBay.

Did unplug the usb cable, then pull out the battery ?
[Touch Diamond, MDA Compact IV General] prank1:
Hhmm.. I wouldn't have thought a ROM could cause so much damage.

You could try this..

1) Leave the battery out for 30 minutes

2) Put it back in along with the charger

3) Try to turn on the device (hold the power button down for 15 seconds)

Selling the device on eBay should be your last resort. Try everything you can to get the device working for now.
[Touch Diamond, MDA Compact IV General] borce_razor:
DO YOU FLASHED HARDSPL FIRST ? AND DOES YOUR DIAMOND IS UNDER GUARANTEE ? IF NOT, YOU CAN THROW AWAY.
[Touch Diamond, MDA Compact IV General] falcolombardi:
Hold Volume down, the Enter Button and then press Reset... Hold the Volume down and the Enter button until the three colour screen appears... Try it....

Look here:

http://blog.jannewap.ws/2008/07/25/htc-diamond-reset-xda-diamond-hard-reset-anleitung/
[Touch Diamond, MDA Compact IV General] phr3n1c:
yes, i flashed hardspl first... i dont know if it is still under guarantee if i bricked... doesn't another rom make your guarantee end? so nothing else to do... :(

PS: if i would have sold it on ebay, i had declared it as broken... just by the way... not to have any people think wrong things about me...
[Touch Diamond, MDA Compact IV General] phr3n1c:
nobody else any idea?
[Touch Diamond, MDA Compact IV General] -Mr. X-:
Im not clear as to what you have tried.

Firstly, Juicy's rom is for North American CDMA Diamonds ONLY :)

Second. i dont think your going through the correct steps.

Enter boot loader mode:

To do this press and hold, Power, Vol Down and Reset button via stylus.

after doing this release the reset button and continue holding power and vol down. you device screen should show a series of colored bars, you're now in boot loader mode.

Flash the CORRECT GSM ROM to you device:

download the rom of choice. anything thats in your language and not labeled CDMA.

extract the rom and connect your phone to your computer and run the ROM Updater Utility to flash the GSM rom to you device.
[Touch Diamond, MDA Compact IV General] dariop:
You gave no information about what you did, and what you have.

What is your Diamond model: US 3G (110), EURO 3G (100), Telus, US CDMA (don't remember those numbers)?

What did you try before bricking it? All the ROMS you used...

and then, are you following the steps for bootloading? Did you try bootloading before bricking it and worked?
[Touch Diamond, MDA Compact IV General] Black93300ZX:
As bad as ICP is, you make a good point... Would trying to flash a CDMA ROM onto a GSM Diamond even go through? If it did, and that's where he's at, I don't think it's something I've seen before.
[Touch Diamond, MDA Compact IV General] -Mr. X-:
no it wont go through. device id is different

that is where he stands it rejected the update because of this and now he says it will not boot up. i dont think he has even tried boot loader mode and flashing a gsm rom yet.

PS: its just a nick name ;) im very much an oldies/rock guy
[Touch Diamond, MDA Compact IV General] drtwin:
maybe you should try reflashing it with htc's original rom? Another thing that interests me is behaviour of device when charging? Does LED blink?
[Touch Diamond, MDA Compact IV General] Black93300ZX:
How can he reflash the HTC ROM when his computer won't recognize it and he can't get to bootloader mode?
[Touch Diamond, MDA Compact IV General] phr3n1c:
Well, I think I'm able to press three buttons, and yes, I did... But it doesn't respond to anythinf... I can not even plug in usb or get it working in any way... not light appears anywhere in or on the device...
[Touch Diamond, MDA Compact IV General] phr3n1c:
Well, I tried to flash a lots of different roms in the past few days, can't remember all of them.

I have a European model from the htc, the xda diamond from o2. I didn't know there is a difference between american and european devices, so some roms are restricted...

mmh I don't know if everything about the hardspl worked fine because it said first that i tried the wrong hardspl for my device, then i lashed another one, and after this juices rom.

While flashing, once the lcd turned on, then off, and remained black...

all the time now, as i wrote not even the leds under the display, in the ring were lighting...

I don't know what to do now...
[Touch Diamond, MDA Compact IV General] -Mr. X-:
so is it dead doesn't even attempt to turn on to the radio info screen? Remove the battery for about 30 min then put it back in and try to force it into boot loader mode and flashing a GSM rom?

once in boot loader mode your pc will see it and you can run the rom updater utility for the gsm rom you want.

if your phone wont boot into windows mobile then bootloader is your only option to get it to detect.