yashsingh1/xdaforums huggingface dataset:
[Verizon Galaxy Note 4 Q&A, Help & Troubleshooting] Tim2460:
I have tried many, many things. I have determined that the problem is a faulty cpu temperature sensor. Is there any way I can disable it on android 6?

Anyways, here's a list of the stuff I have tried:

1. Downgrading the Rom (Didn't work)

2. Upgrading to a custom Rom and just using the "Disable sensors" quicktile (Rom Refused to boot)

3. Finding whatever app is doing this and disabling it (Scoured the internet for about 3 days, couldn't find anything)

It looks like there's 2 solutions that will work:

1. Disabling the app that's doing this

2. Disabling the faulty sensor

Do you think you know a way to do either?

Thank you for your time!
[Sony Xperia 1 V] andyman1222:
Someone previously was able to enable wifi 6E on the Xperia 1 IV by editing the build.props (https://xdaforums.com/t/wifi-6e-on-xq-ct72-tw-version.4550613/). Turns out, the same sort of instructions work for the 1 V as well. Like in the post, I extracted the image of the US firmware to get the properties needed to turn on 6e. I then used MagiskHide props config to create new properties with the values shown below. For some reason manually creating the script didn't work but using the magisk module did.

This is specific to the 1 V only, more specifically this config is for US regulations. For European or other regulations, I suggest doing what I did but with your appropriate firmware (steps below).

#!/system/bin/sh
resetprop -n ro.vendor.product.rf.id=pdx234-A2US
resetprop -n ro.vendor.sony.wlan.6e_cc_list=US
resetprop -n ro.oem_ant_switch_index_table=10,10,12,12,10,10,12,12,12,12,12,12,12,12,12,12,10,10,12,12,10,10,12,12,12,12,12,12,12,12,12,12,10,10,12,12,10,10,12,12,12,12,12,12,12,12,12,12,10,10,12,12,10,10,12,12,12,12,12,12,12,12,12,12
resetprop -n ro.oem_sar_back_off_index_table=1,1,8,1,6,3,8,1,5,2,8,1,5,2,8,1,1,1,8,1,6,3,8,1,5,2,8,1,5,2,8,1
resetprop -n ro.boot.wificountrycode US

Extracting the properties:

First, take a look at this guide to rooting and changing US modem. Follow the instructions in it which extract init_boot_[].sin however instead extract oem_X-FLASH-ALL-[].sin.

This should generate a .ext4 file in the output of the dump tool, extract or open it (I used 7zip).

In /etc/customization, open config.prop. Once there, look for the specific property values to use in place of the ones used above, probably all bundled at the bottom of the file.
[Sony Xperia 1 V] nos1609:
What about just flashing the whole OEM partition?
[Sony Xperia 1 V] andyman1222:
That would work but modifying build.prop doesn't require re-flashing anything
[Sony Xperia 1 V] Flava0ne:
Do I replace the line below with?: resetprop -n ro.boot.wificountrycode US

ro.trackingId.booking=2112101

Or just replace all the lines just above that with what you provided?
[Sony Xperia 1 V] andyman1222:
If you're doing it for a different model or firmware, replace all the lines with those found in whatever config.prop you're looking in. Look for the ro. properties specifically. (at least I think)
[Sony Xperia 1 V] Flava0ne:
I've attached the modified config.prop. Did I correctly change the required lines in it? My device is the XQ-DQ72 like yours I believe.
[Sony Xperia 1 V] kingjames007:
Hi, does it work ? I have DQ72 too, I wanna be sure before making mistakes... Do you see any difference on the network following this guide ?
[Sony Xperia 1 V] Flava0ne:
I haven't flashed the config.prop file yet since the OP still hasn't replied back to confirm if whether or not I changed the correct lines in it.
[Realme X3 Questions & Answers] Polv3rine:
Hello,

I recently locked my bootloader after locking it don't know if I did something wrong it wiped my IMEI now I can't get network. Any one have any idea of fixing this?
[LG V50 ThinQ ROMs, Kernels, Recoveries, & Other De] shenlongforum:
<Moderator Edit>:

Thread closed and content removed! - @roirraW "edor" ehT
[LG V50 ThinQ ROMs, Kernels, Recoveries, & Other De] shenlongforum:
Battery review: very good, 7h56m on-screen from 100%

View attachment 6071956View attachment 6071957View attachment 6071958
[Device Repair] HyperDimensional:
I have a quest 2 where the backlight on the right side is blackened. I know it's the backlight, because I can still see the screen from the residual light bleed over if I close my left eye. This confuses me greatly, because it looks like the right and left side are just masked out part of the same display. But if one is broken and the other is not, well. I have no idea what that means. This is a placeholder thread for it's repair. If I don't repair it by March 2024, I'll delete it, if I forget to to do that and you're reading this and April 2024 has passed, please DM my calendar unaware ass to delete this thing.
[Device Repair] HyperDimensional:
So I let my LG G5 die from having a low battery. This battery is COLD and OLD. It didn't just run to 1% and shut off, no it died. This happens all the time though. Also the day before it would only accept charge from a cheap Chinese charger and rejected a USB 3.0 charger (no charge notification or red led). Anyway, I tried doing the power button down for 30 seconds trick, and it still wouldn't turn on or accept charge (no red led). Then I swapped out the battery with my other LG G5, charged it to 50, and swapped it back, and it still wouldn't turn on or accept charge (no red led).

What do you guys think? Bricked?
[Device Repair] user0u:
Try turning it on with the charger plugged in and the battery removed. If it responds then there's your answer.
[Device Repair] HyperDimensional:
Brick.
[Samsung Galaxy S24 Ultra] dinesh6908:
I'm using S24 Ultra and tried to install 3rd party games onto the device but while installation every game gives same error - App not Installed as app is not compatible with your device whereas i'm able to install all 3rd party apps but GAMES.

Please help.
[Samsung Galaxy S24 Ultra] SupFlynn:
Probably they are developed for x86 architecture rather than arm (which most of the qualcomm chip's based on) This is the main reason that i can think of other than they aren't being compatible with android 14.
[Samsung Galaxy S24 Ultra] dinesh6908:
All same game was working earlier on my S23 Ultra wheather x86 or arm. Apps are getting installed properly of x86 and working.
[Samsung Galaxy S24 Ultra] SupFlynn:
S23 ultra uses snapdragon so it is arm based too. It is something software related after few updates it'll get fixed for sure. Wait for february update. In february update most of the problems we're having today should get fixed.
[Samsung Galaxy S24 Ultra] dinesh6908:
OK, Thanks
[Samsung Galaxy S24 Ultra] cabagekiller:
its related to no 32 bit support on the newer snapdragon processors, the apps are most likely 32 bit not 64 bit
[Samsung Galaxy S24 Ultra] dinesh6908:
Can you give some game names released for 32bit which i check on S24 Ultra
[ASUS ROG Phone 5 / 5s] sakamaki123x:
I'm looking for the full firmware version of .175. If anyone has it, please give it to me. thank you.
[Galaxy Ace S5830i General] lactarius:
I tried several custom ROMs. Wifi ok, internet working - still can't sign in to Google account. Username and password are fine, I still use that account. I tried setting the correct date and time.
[Galaxy Ace S5830i General] ze7zez:
Try manually upgrading the Google Account Manager for your android version.
[Galaxy Ace S5830i General] lactarius:
This is it! (y)

Thank You very much.
[Non-Touchscreen Windows Mobile Other] vodafones:
THANKS TO Mr. RAMJAN

HAPPY NEW YEAR 2009

all in one HARD RESET CODE collections, please download here :

DOWNLOAD HERE

​
[Non-Touchscreen Windows Mobile Other] cicciocant:
from virus total (see attachment)
[General Questions and Answers] mimixd:
I got a showcase (live demo) s22+ where the SIM doesn't work and the IMEI is 000000000...

I did a quick search and saw that it's possible to make the SIM work by downloading a firmware. I'm a user with no experience on the subject and I'd like to know if it's really possible. If so, could you give me some tips to keep in mind when doing it? Like what type of ROM do I use, where can I find it and some valuable tips for carrying out this installation, thank you in advance!
[General Questions and Answers] xXx yYy:
One possibility why the chip in your phone might not be working is that it was damaged during manufacturing or shipping. Another possibility is that it has been tampered with or replaced with a counterfeit chip. If the chip is damaged, it may need to be replaced. If it has been tampered with or replaced with a counterfeit chip, the phone may be blacklisted by the carrier and will not be able to be used on any network.
[General Questions and Answers] mimixd:
I apologize, I ended up expressing myself wrong. The CHIP I'm referring to is the SIM, cell phone number. As it is a storefront cell phone, this option does not work, so I cannot enter a cell phone number and use 5G on the streets. I even forgot to mention that it is a live demo cell phone.
[Samsung Galaxy S21+] icavp:
My Device is showing "Emergency calls only" I tried to change the network but its saying " Error while changing the network ".

The update don't work also its saying " Registration Failed."

I bought this phone 2nd hand from a person and isn't refundable. So I need a solution now. It was working fine when I purchased it but after coming back to home I flashed my phone to BD region. Now it showing emergency calls only. But it detects my phone number.

The Device is G996B/DS. Carrier Provider is XSP/MM1.So is there anything I can do to unlock this network?

Should I have to be in the same rom as my provider? Currently I am on SIN rom.
[Android Q&A, Help & Troubleshooting] iceblue007:
Hi, To be honestly I'm a totally newbie about root or flash, so the bad news is that my [PDA] got bricked now. If you are an expert in this area, just look my questions below and Please help me, and the latest situation is at 4 floor. Thx a lot sincerely!

Here are some key information.

SoC: MT6765

(maybe)preloader code: full_k65v1_64_bsp

OS: Android 9

Can not usb debugger or trigger the developer option.

BTW, It's an un-famous vendor so that the compatible twrp-recovery I didn't found, even the stock rom.

Steps 🚩

Here are some steps I‘ve done before when I follow the tutorial.

https://github.com/bkerler/mtkclient

#S1

python3 mtk r boot,vbmeta boot.img,vbmeta.img

#S2

python3 mtk reset

#S3

do some patched work with customized app - Magisk

#S4

python3 mtk w boot,vbmeta boot.patched,vbmeta.img.empty

#S5

python3 mtk e metadata,userdata

#S6

python3 mtk da seccfg unlock

After doing this, I restart my PDA and I found that it said unlocked and the system root succeed. Thx a lot again!

#S7

🔪Then I delete just one folder which is inside of path: /system/priv_app/XXFolder/XX.apk

Reboot to the recovery mode, I want to flash 3rd recovery like TWRP or CWM.

BTW, I never into the fastboot mode succeed no matter how I press the Physical buttons, I tried much much time, it‘s always failed.

So I type the command

#S8

python3 mtk payload --metamode FASTBOOT

I see the fastboot in the screen bottom left side, and I continue type

#S9

fastboot flash recovery --disable-verity --disable-verification twrp-3.2.1-0-geminipda.img

fastboot boot twrpxxx

Result ⬇️

I never into the system succeed as usual even the recovery or fastboot, except preloader.

I didn't know the reason then I start to learn Sth. about that, so now I backup the entire partition using MTKClient2.0-beta-gui. I don't flash the 3rd rom actually, I just want to root the PDA from the very beginning.

So I hope some one can help me solve this urgent problem, Thx a lot!!!

Questions❓

#Q1: If I unpack the system.img file and restore the XXFolder/XX.apk, repack and flash it, can everything restore as usual?

#Q2: I can't enter the recovery mode now, so anyone can give me a common&light recovery?

#Q3: Step-By-Step above, I missed the recovery and metadata partition backup, is that necessary?

#Q4: I want to know if I did S7 wrong lead to that bricked or Sth. else?

#Q5: Why I could't into the twrp and cwm even any other 3rd recovery. Didn't I have any chance for that?

I tried by best as I can for my need, like XDA forums searching, MTK flash tools, MTK recovery tools, ext-typed img-unpack/repack tools, but still not work for my own. So I really really hope any one can help me, or just give me some advice.

Thx for all your precious time.
[Android Q&A, Help & Troubleshooting] Chickenkillla81:
Have you tried to flash the ORIGINAL boot_dump that you took when you pulled your backup? It sounds to me that the problem is when you tried to flash the TWRP recovery. If the recovery is not SPECIFICALLY for your device it will not work. Even if it is from the same company every device is different and it will cause the device to not boot properly. That would be the first thing to try. Go back to mtkckient and run the command to flash your boot dump that you made. Should be

python3 mtk w boot boot_dump_from_mtkclient.img

Or if you can get into fastboot

fastboot flash boot boot_dump_from_mtkclient.img

That should get you back to being able to work again. Some devices don't have any custom recoveries to use so you will always have to use fastboot or mtk. I hope that helps😁. Good luck

Also, don't worry. If you can access the preloader you always have a chance to fix it. Sometimes it is hard to find the firmware for not popular devices though. I have a tablet for 3 months and cannot find. I messed it up trying to root with mtk and deleted my backup boot.img on accident so I cannot fix it🤬
[Android Q&A, Help & Troubleshooting] iceblue007:
Thx bro.

Sorry for that I'm too late to reply.

For roll back:

Actually I tried roll back with mtk as soon as I can, but still not working. My ubuntu terminal showed me I've typed history bash command is 'python3 mtk w boot,vbmeta boot_normal.img,vbmeta.img.empty' and the command combination, even roll back to the bootloader locked state, but still not working. I was trying to learn Sth for that stuff, I really noticed that the dumped xx.bin or xx.img using MTK is not formatted, it is just raw data as binary.

Besides, for Q1,

now I unpacked the system and vendor, then I unpacked the boot.img backuped before bootloop. Obviously system and vendor showed everything to me, but for boot.img, I just got the kernel file, why that ramdisk is empty? I really really don't know. Is that boot.img corrupted? But I guaranteed that I use command `python3 mtk r boot boot_normal.img` to backup.

Based Q1, I tried Q2 manually, still bootloop.

Finally, I just try to format all partitions(except boot loader) thru SP Flash Tool and flash another vendor-stock rom cause of no stock rom for it self as I said before.

In fact, I got many errors untill I change the scatter file about partition of preloader, just change its name to my preloader_k65v4.bin, and I change the path of preloader in this tool.

But not my expectation, things goes worst, I got totally bricked cause of it never into recovery or fastboot or os even the logo screen.

Should I try to overwrite the preloader partion thru mtkclient? I heard it's a very dangerous action.

But I really don't know if a stock-preloader.bin combined with a third rom(except the rom's preloader) could work in any MTK device?

Recent, I learn Sth about Scatter file and partition layout. I considered that if I could try this below?

a)Parse the backuped gpt_main.bin/gpt_backup.bin

b)Create or Fix the scatter file based the 3rd stock rom to be compatible with device it self.

Is there some one can tell me if the solution worth to try?

If it's worth, give me some guide or tool links about that.

Any tips would be appreciate.
[Android Q&A, Help & Troubleshooting] iceblue007:
I got bricked long time.

No recovery!🤢

No fastboot!🤮

Even no logo screen!😱

Always black screen!

Charger light always on by USB cable(I really don't sure whether it is in charge).

Dumped(or backuped) some known partitions but some are exceptional.

Had gpt_main.bin and gpt_backup.bin(I don't know that stuff much)

Here are some key information.

Device: customed phone or tablet(I don't know) with not popular vendor

SoC: MT6765

(maybe)preloader code: full_k65v1_64_bsp

OS: Android 9

Now I just could use some tool to do Sth, just like mtkclient, SP Flash Tool, or else which just need USB COM/VCOM cable on that bricked device.

So I've tried Sth by myself.

a)Backuped the partitions before the brick, but recovery.img, userdata.img.

Worth noting:

first, the boot.img I unpacked has no ramdisk totally.(I don't know why, or it is just ordinary?)

b)With no stock rom cause, I must have to flash the 3rd rom compatible as much as possible. I choose OPPO A8 finally. I flash the whole rom partitions by SP Flash Tool except the rom's inside preloader_oppo_6765.bin otherwise it always lead to some wrong tips.

What I need is just enter the os as usual, so help me Pls.

Any tips will be appreciated.
[Android Q&A, Help & Troubleshooting] Renate:
The gpt and its backup are the partitioning. You probably shouldn't be rewriting them.

If the partitioning and the preloader are ok you should be able to hit the preloader on USB at 0e8d/2000

If not you're stuck with the less versatile BRom at 0e8d/0003

Does this thing boot up now with any action on the USB?

You really can't flash this with firmware from some other model, even with the same SoC. there are too many variables.

I don't how the Mediatek secure boot works.

Most (many?) boot images don't have a ramdisk.
[Android Q&A, Help & Troubleshooting] Chickenkillla81:
@iceblue007 @Renate knows what's going on. Try anything that is suggested. But I agree 1,000% do not try to flash a ROM from a different device. I don't know too much but that would be really bad and not work at all. And would probably leave you with a device that is not fixable.

An idea I have is if you can find a new device at the store that is the exact same model. But it and use it to get everything you need of of it. Then relock the device back to stock and return it. It is kind of shady to do that but if your device is not popular it might be your only choice. I know how it is. I have a tablet I cannot find any information on. It is also a cheap tablet like yours and there is nothing online where I can download firmware. It sucks. That's why I haven't tried to do anything with it because if I break it I can't fix it. 😂 good luck
[Android Q&A, Help & Troubleshooting] mvikrant97:
That's a lot of stuff.

Answer these questions below.

1. Which device are you trying to flash?

2. How did you bricked it?
[Android Q&A, Help & Troubleshooting] Chickenkillla81:
From what he says I am 80% sure it was step9 in his post that did it. He attempted to flash a TWRP for a different device.

To fix that he should just have to flash back his original boot.img he backed up right?

BUT, I think he had been doing other stuff since that point. IE repartitioning. And last post talks about flashing a ROM for different device. Obviously that would have been bad if he did do that.
[Android Q&A, Help & Troubleshooting] iceblue007:
Yeah, you hit it. I was always been BRom mode no matter when I try to flash TWRP before or this bricked time.

Cause the first tool I met and tried to do that thing is indeed MTKClient from github. And when it start working normally, stdout showed that I was detected in BRom mode. Indeed I was not trying use preloader mode do Sth. Never.

For boot.img unpacked issue, now I knew that, Thx a lot. If some solution you thought I could try, let me know pls.
[Android Q&A, Help & Troubleshooting] Chickenkillla81:
Did you get it working again with different ROM using so flash tool and scatter?
[Android Q&A, Help & Troubleshooting] iceblue007:
1. The device is not popular, just more like a customed PDA or tablet. Last, the key info is at 4 floor.

2. Long story, in a word, just as this thred title described. Of course, before that I might did some thing wrong lead to that but I'm still not sure which step I did wrong.

Now, I just want to fix the issue.

Any tips will be appreciated, Truly Thx.
[Android Q&A, Help & Troubleshooting] mvikrant97:
Please provide the model number so that I can find stock rom somewhere.
[Android Q&A, Help & Troubleshooting] iceblue007:
@Renate @Chickenkillla81 @mvikrant97

Actually, I use ubuntu22.0.4 vm in windows10 and do everything there. But when I use magisk to patch the backuped boot.img, and unblock the bootloader from MTKClient tool, after that, I try to reboot , I just have a bootloop. I also remember the screen showed that 'dm-verity error\n device has unlocked xxxx' message.

For trying to fix that issue by myself, the first choice I use fastboot to flash the TWRP(even I know there is no compatible for my vendor version), even with option --disable-verity --disable-verification, but not work, still bootloop.

That time, I don't know any stuff even a little about patch boot or kernel. I just try to find some solutions.

Finally is bad situation just described as I said at 4 floor.

This issue drive me crazy almost.

During that period, I've learned ext fs, scatter layout, partition knowledges, Android boot mechanism, some tools working theory roughly, even reading some patched boot or kernel technic post blog deeply.

Sometimes for a newbie just like me, I learn some, know some, but also don't know some. E.g. I could use SP Flash Tool to flash the 3rd rom, and I knew it need a scatter file, so I thought whether I can try flash other rom first then I just need restore the scatter from backuped gpt_main.bin from MTKClient tool, I will got everything worked fine, even I knew it is a bad choice but did I have another one?
[Android Q&A, Help & Troubleshooting] Chickenkillla81:
Honestly I have no ideas. I'm a noob too. 😂 I know some basic stuff but nothing in the area you are into. Sorry
[Android Q&A, Help & Troubleshooting] iceblue007:
Maybe there is no accurate model, I just capture some key info when I viewed the recovery logs as follow:

SoC: MT6765

vendor preloader: full_k65v1_64_bsp-user

vendor brand: IWRIST

vendor model: DPK3AP

vendor fingerprint: IWRIST/full_k65v1_64_bsp/k65v1_64_bsp:9/PPR1.180610.011/server04221802:user/test-keys

If you need more, I could upload all captured info images later.
[Android Q&A, Help & Troubleshooting] mvikrant97:
GitHub - fw-dumps/vivo_k65v1_64_bsp_dump: full_k65v1_64_bsp-user 10 QP1A.190711.020 compiler01122029 release-keys

full_k65v1_64_bsp-user 10 QP1A.190711.020 compiler01122029 release-keys - fw-dumps/vivo_k65v1_64_bsp_dump

github.com
[Android Q&A, Help & Troubleshooting] iceblue007:
It's okay, my best Fd. Sometimes maybe we can offer some useful msg, even a little inspiration. I have much confident and patient to met the challenge even sometimes it drive me crazy. Let's look forward to the final solution of this or these discusting problems.🍺
[Android Q&A, Help & Troubleshooting] Chickenkillla81:
Check out that firmware. That was awesome he found that!
[Android Q&A, Help & Troubleshooting] Chickenkillla81:
How did you find that? I won't if I could find something for my Sky Devices Sky pad 8 pro. I have never been good with finding things on GitHub
[Android Q&A, Help & Troubleshooting] iceblue007:
Thank u. Actually I read about that from git topic named MT6765, but as I said before, not work for me.

Not only that designated dumped rom, I've seached almost every matched maybe compatible ROM of SoC MT6765 as possible as I can. In fact I chose oppo realme first because I saw the twrp has compatible version, but then I found its Android 10, which is supported dynamic partitions, so I gave up. After that, I tried oppoA8 which is more closer to my vendor info such as MT6765, Android9, 4G+64G, etc. But the bad news is that still not valid.

Thank u again!
[Galaxy S 4 Q&A, Help & Troubleshooting] Wenze76:
Mod Translation:

I have a samsung galaxy s4, it is possible to install ROM from S6.

Mam samsung galaxy s 4,jde do nej nainstalovat ROM z S6.
[Galaxy S 4 Q&A, Help & Troubleshooting] V0latyle:
@Wenze76 Please make sure you post your question in the appropriate section of the forum. You originally posted this in the Galaxy S3 section; as a courtesy, I moved this thread to the S4 section.

Additionally, please be aware that English is required on XDA:

Thank you.