yashsingh1/xdaforums huggingface dataset:
[Samsung Galaxy S10 Questions & Answers] schwinn8:
Thanks for reporting back and letting us all know, and I'm glad it worked out well!

Yeah, the carriers pull this nonsense all the time... it's BS. The phones are all the same, only the ROM changes. If we can change ROMs (which we can) then there should be no reason to force users to specific IMEIs. But we know why they do this - follow the money. I encourage people to write to the FTC and FCC about this (I have).
[POCO M3 Pro / Redmi Note 10 / 10T 5G] jorrit47:
Hey i spend today a lot of time to tried to fix my bricked Redmi Note 10 5G.

I just wanted to unroot my phone but i did something wrong.

First problem i have is the dm-verity corrupt.

So i read and tried this

https://xdaforums.com/t/help-with-redmi-note-10-5g-bricked-but-has-access-to-fastboot.4366655/

Without succes i flashed the right firmware for my device many times but the dm-verity corrupt is still there and then i keeps hanging in the redmi boot logo.

But i dont know how but now i also got my bootloader locked so now i cant flash any thing.

And the dm-verity corrupt and keeps hanging on the redmi bootlogo.

So i hope some one have an solution for me and can help me and fix my phone.
[POCO M3 Pro / Redmi Note 10 / 10T 5G] wetito:
u have made a common mistake. u have flashed firmware with miglash, without change default option to flash all. you have select flash all and lock. so yout phone is hard bricked. i think theres a guide to solve this. search on this forum
[POCO M3 Pro / Redmi Note 10 / 10T 5G] jorrit47:
Hey thanks for the reply

i know i made a mistake and i search and tried anything what i thougt it is maybe a solution on this forum.

Bun without any succes and because my bootloader is locked now i cant do anything in the fastboot.

i dont know how to unlocked now.

Because the bootloader is locked now i think i have the Guarantee now but if the i boot the phone the dm-verity corrupt message is still there and then it keeps hangin on the redmi logo.

So if there is no way to fix it i think go trie it to bring it to the store where i bought it 2 months ago.
[POCO M3 Pro / Redmi Note 10 / 10T 5G] wetito:
i think you can solve using mtk spflash tool

look here, u can find the solution

https://xdaforums.com/t/soft-bricked-phone.4403573/
[POCO M3 Pro / Redmi Note 10 / 10T 5G] jorrit47:
Hey thanks for the

Hey thnks gor this guide but i cant get it found it in the sp flash tool.

I dont get my phone in the BRom mode to find it so im stuck there tried servel of times when it power of to get my phone BRom mode how dos the screen look if its in BRom mode ?

By pressing the vol + vol - and pwr button when its off id ont get it in the BRom Mode.

Also i googled the sp flash tool to download it so maybe i dont have tight one do you have mabe some links for me?

Or is there maybe a other way to fix my phone?
[POCO M3 Pro / Redmi Note 10 / 10T 5G] wetito:
try this tool. seems very good. but i didn't never used. so you had to try by yourself. it have many interesting and usefull function

Home - Tool All In One

TOOL ALL IN ONE This tool support 67 different devices of some different OEMs. DOWNLOAD CHANGELOG XDA THREAD OTHERS PROJECTS

toolaio.tk
[POCO M3 Pro / Redmi Note 10 / 10T 5G] jorrit47:
That also didn't work do i go to reseller today and hope i hot a new one of the gonna fix it.

Becuase the bootloader is locked again warrenty only the dm-verification message is there.

Do gonna say i updated my phone and now its not booting anymore.

Or do you or maybe some one do have an tutorial program or tool to fix it.
[POCO M3 Pro / Redmi Note 10 / 10T 5G] passion8059:
Download ROM for your phone and extract to desktop. Reboot to fastboot and open flashall.bat. it should run firmware through and reflash phone completely. Boot phone and on boot screen keep pressing power so phone can boot and bypass DM Verity error. Once booted reboot into fastboot again and enter fastboot oem cdms. Reboot phone and DM Verity should be gone.
[POCO M3 Pro / Redmi Note 10 / 10T 5G] wetito:
we repeats same anawers continuosly.i dont understand why some users decide to mod their devices, if they dont know how to use Google, and don't understand how to follow the flashing guides step by step. and finally after flashing custom rom, they ask how back to stock 🤣
[POCO M3 Pro / Redmi Note 10 / 10T 5G] passion8059:
Get what you are saying, think there is at least 8 threads on same topic.
[POCO M3 Pro / Redmi Note 10 / 10T 5G] jorrit47:
Hey thanks for the answers and the things i could tried to fix my phone.

im not a noob with rooting and flashing android phones before i do flasshong or rooting and the other stuff i always read and check the xda forum before i do.

With other android phones that i had before i made some misstakes before but like a bootloop or something else that the phone not was booting but always i can fix the phone.

So the problem what i had with my Redmi note 10 5G and not one solution that i found on xda or something that maube could fix the problem nothing could fix it.

So i a couple of week ago i went to the reseller and they send it to a repair center.

I think the coudnt also fix it because the did a boardswap.

I think if they cam fix it with a tool or software and reflashing the phone they did.

Now i wait some time before i go rooting or flashing stuff on my phone i hope there will be good twrp so thning go musch easier in the future to fix stuuf like (DM-VERITY Corruption.
[POCO M3 Pro / Redmi Note 10 / 10T 5G] wetito:
twrp is not necessary. fix dm-verity is easy. the are MANY MANY MANY post where is explained how to do. root new phones is dofferent but not complicated. magisk works fine if installed following the latest guides. it's impossible damage mainbord after a root procedure. sure you didnt follow the guides with attention. i have rooted my global phone many times without problems. simply you have made a bad flash of vbmeta or product partition. you made a big mistake, cause this devices can be rooted without brick
[Samsung Galaxy S21 FE] grayson73:
Is it safe to leave the phone plugged in 24/7 with "protect battery" on, which limits max charge to 85%?
[Samsung Galaxy S21 FE] blackhawk:
Not a good idea. A power surge or near lightning strike could fry it. Rather pointless to leave it perpetually plugged in.
[Samsung Galaxy S21 FE] grayson73:
I see. What about leaving it charging overnight while I sleep? Does it hurt the battery to have it plugged in while it is at 85% with "protected battery" on in the same way that it hurts to have it plugged in when it is at 100%?
[Samsung Galaxy S21 FE] blackhawk:
A 40-72% charge is better; Li's love frequent midrange power cycling. 85% is ok but 80% or lower be better. Do what best suites your needs.

Batteries aren't a big deal to replace. I now replace my heavily used N10+ battery about every year now as a matter of routine maintenance.

However a battery failure is a big deal and seriously damage the phone. Any battery swelling (rear cover) is a battery failure, replace immediately.
[Samsung Galaxy S21 FE] grayson73:
I see. Too bad Samsung didn't choose 80% or make it selectable.
[Samsung Galaxy S21 FE] blackhawk:
Like I said it's not a big deal. I just fast charge for 10-20 minutes when convenient.

You could put on a timer switch if it really bugs and slow charge it.
[Samsung Galaxy S21 FE] Ing.King:
Why such concern ? Been charging all my phones since 2012 all day long on, during daytime, none of them was affected. Battery still same, last like new. Many of them still in use by my family members.

Example, I behaved like this to phones for around 1,5 - 2 years, then I got new one. So not just tiny short period of time.
[Samsung Galaxy S21 FE] grayson73:
Oh really? That's good to know. I thought fast charging, charging to 100%, or leaving it plugged in at 100% would degrade the battery.
[Samsung Galaxy S21 FE] Ing.King:
Never actually carried about this, lucky me maybe, wait for other oppinions or exp.
[Samsung Galaxy S21 FE] Perioisis:
make sure that it doesn't heat up. rest of it not affect too much.
[Samsung Galaxy S21 FE] sunyakram:
I always charged my smart phones whole night.

Never faced any problem.
[Samsung Galaxy S21 FE] blackhawk:
Higher cell voltage degrades the Li faster.

They are rated by full charge cycles; discharge until shutdown to 100% charged is a cycle.

Most have a rated life of 200 or so cycles.

High storage/use temperatures also can effect it's service life greatly as can rapid discharge cycles.

In any event when a Li reaches 80% of its original capacity it is degraded and should be replaced before it fails (which could destroy the phone).

On my heavily used N10+ I get about a year to 1.5 years of usable service life per battery.

Just replace the battery once it's degraded and otherwise don't worry about it if so inclined. Don't expect a 3 year service life though if it's charge cycle is fully or near fully cycled daily.
[Samsung Galaxy S21 FE] Sailand:
Leaving the charger H24 is less unsafe with the 85% limit enabled but it is not totally safe.

After the first charge starting the discharge and automatically the recharge. The result is the use of more number of recharging and the batteries doesn’t support an infinite number of this.

This worse if you use fast recharge, when I have to leave in charge all the night I use an old 5V 500mA charger.
[Samsung Galaxy S21 FE] blackhawk:
Lightning strike... poof.
[Samsung Galaxy S21 FE] Ing.King:
My S21FE half ended life yesterday, finished call and then died. Always on charger while in office. Startup possible but after Samsung logo always restart then loop. After 7 loops stays off. Sent to provider for claim. Maybe it is not related to battery, but you never know. Charging not working, no reaction after plug of the charger, even while turned off.
[Samsung Galaxy S21 FE] blackhawk:
That sucks.

Hardware failure of some type. Bootup requires a lot of current so it maybe the battery.

Sounds more like a mobo failure...
[Touch Dual, MDA Touch Plus ROM Development] xttt2005:
i just brick my NIKI, it hung at the WM61 green screen, so far I can enter the rainbow screen, but I can't upgrade the device by Custom_RUU tools.

I get to know flash elf by SD was rename NBH file to ELF0IMG.nbh, is there anybody know how to rename the nbh file for NIKI? what is the file name for NIKI?

Thanks in advance!!!
[Touch Dual, MDA Touch Plus ROM Development] Midget_1990:
why cant you upgrade from the bootloader (rainbow). did you security unlock or use hardspl? have you tried a hard reset?

if you are not unlocked/hardspl and hardreset doesnt work then you must flash an origional carrier ROM meant for your device.
[Touch Dual, MDA Touch Plus ROM Development] vsavichev:
You jast need to rename your .nbh file to nikeimg.nbh, and then push the camera button while turning on device. Then follow the onscreen instructions.
[Touch Dual, MDA Touch Plus ROM Development] kenshin-J:
if i do that, i see a white screen with "loading" on it. after a 30 minutes still the same?

What is the problem?
[Touch Dual, MDA Touch Plus ROM Development] bubittu:
you must rename in "NIKEIMG" ....see that

http://xdaforums.com/showthread.php?t=437392
[Touch Dual, MDA Touch Plus ROM Development] bubittu:
when i flash from mcrosd,the update,start immediately after loading....i think that in your case,something is wrong....are you sure that you rename in caps letters?...is "NIKEIMG.nbh" and not "nikeimg.nbh",for example...
[Touch Dual, MDA Touch Plus ROM Development] animelover:
But what is meant with "two files"? One file must be the NBH Image but what's the other file? CustomRUU.exe? :confused:
[Touch Dual, MDA Touch Plus ROM Development] bubittu:
yes it is!...NIKEIMG.nbh & CustomRUU.exe....exactly!
[Touch Dual, MDA Touch Plus ROM Development] 0pod0:
then NIKI can't flash by SD in the end?

i got a same probrom,it hung at "loading"

card from is fat32

name is nikeimg.nbh
[Touch Dual, MDA Touch Plus ROM Development] animelover:
The filename must be NIKEIMG.nbh! Try it with big letters instead of normal letters!
[Touch Dual, MDA Touch Plus ROM Development] 0pod0:
i've already use NIKEIMG.nbh but it still hung at "loading"

and i tried to flash hspl by SD,

i run sspl-1.16-niki.exe,it still hung at 'loading"as well.

is the sspl-1.16-niki.exe cant flash anyrom by SD,or only cant work by USB?
[Touch Dual, MDA Touch Plus ROM Development] NetrunnerAT:
if you havent hardspl ... it only work via USB!!!

SD-Card works too ... if you dont need load Software SPLs first.
[Touch Dual, MDA Touch Plus ROM Development] 0pod0:
you mean that i have to unlock/hspl first,than it will done?

but i cant unlock/hspl with usb
[Touch Dual, MDA Touch Plus ROM Development] NetrunnerAT:
no USB = no chance!
[Sony Xperia XZ1  ROMs, Kernels, Recoveries, & Othe] Tux111:
View attachment 5577049

Evolution X for the Sony Xperia XZ1 (Poplar)

DON'T FORGET TO JOIN OUR AWESOME TELEGRAM XZ1 GROUP! ;D (Extra modules, help, laughts)

View attachment 5643027​

*
* Your warranty is void. Or valid, probably?
*
* I am not responsible for bricked devices, dead SD cards, Ebolation X,
* thermonuclear war, or the current economic crisis caused by you following
* these directions. YOU are choosing to make these modifications, and if
* you point your finger at me for messing up your device, I will LMAO at you.
*/

Reach us on Twitter! @EvolutionXROM

Just flash and check "The Evolver". We have tons of features combined together from different ROMs.​

* You tell me

DO NOT FLASH GAPPS, ALREADY INCLUDED​

CLEAN FLASH :

Download the latest build

Reboot to recovery

Wipe System, Data, Cache, Dalvik

Format Data

Reboot to recovery again

Flash the latest build

Done!

DIRTY FLASH :

Download the latest build

Reboot to recovery

Flash the latest build

Wipe Cache/Dalvik Cache

Done!

View attachment 5577051​

Android OS version: 12.1

Security patch level: September 2022

Build author: Tux111

Source code: https://github.com/Evolution-X

Kernel Source code: https://github.com/whatawurst/android_kernel_sony_msm8998

XDA: DevDB Information

Evolution X, ROM for the Sony Xperia XZ1 (Poplar)

Contributors

derf elot, modpunk, Rooted_Ansh, javiwz

Thanks to hsheemi for testing!

ROM OS Version: Android 12.1

Based On: AOSP

Version Information

Status: Stable
[Sony Xperia XZ1  ROMs, Kernels, Recoveries, & Othe] Toni Mahmud:
What is that bug after every start a phone.

There is an internal problem in your device. Please contact your manufacturer.​
[Sony Xperia XZ1  ROMs, Kernels, Recoveries, & Othe] Lovando:
yes, me too
[Sony Xperia XZ1  ROMs, Kernels, Recoveries, & Othe] raffyei8ht:
I had this error, what i did to fix this is when i flash the rom, after wiping, i format data or format phone. I forgot what the exact words in twrp.
[Sony Xperia XZ1  ROMs, Kernels, Recoveries, & Othe] Lovando:
Thank you for the information
[Sony Xperia XZ1  ROMs, Kernels, Recoveries, & Othe] Tux111:
Common bug, only shows at boot. You can ignore it.
[Sony Xperia XZ1  ROMs, Kernels, Recoveries, & Othe] Toni Mahmud:
ok thanks
[Sony Xperia XZ1  ROMs, Kernels, Recoveries, & Othe] nhojeric214:
Do i need to flash stock rom before flashing this one if im from DoTOS rom?
[Sony Xperia XZ1  ROMs, Kernels, Recoveries, & Othe] Tux111:
? No, not needed. Just clean flash.
[Sony Xperia XZ1  ROMs, Kernels, Recoveries, & Othe] nhojeric214:
Not rom related question but, i seem to cant boot to recovery on every android 10 or 11 custom roms ive tried i always need to fastboot twrp if i decide to change rom. Is it just me or its really the way it is?
[Sony Xperia XZ1  ROMs, Kernels, Recoveries, & Othe] Tux111:
Just you, at least on 10 11. On 12 i've always booted manually with Power+Volume Down.
[Sony Xperia XZ1  ROMs, Kernels, Recoveries, & Othe] nhojeric214:
from phone off?
[Sony Xperia XZ1  ROMs, Kernels, Recoveries, & Othe] Tux111:
Yes.
[Sony Xperia XZ1  ROMs, Kernels, Recoveries, & Othe] nhojeric214:
Do you have a recommended recovery for this or is the one from twrp side just as good?
[Sony Xperia XZ1  ROMs, Kernels, Recoveries, & Othe] Tux111:
The one included in the ROM is good. Moreoever, there aren't other compatible kernels with a12 afaik right now.
[Sony Xperia XZ1  ROMs, Kernels, Recoveries, & Othe] FelyCZ:
Hi, I have two questions:

1.) Does Google Pay work on this ROM?

2.) Would it be possible to use Sony Stock Camera (if I have TA partition backed up)?

Thank you for answers and work on this ROM!
[Sony Xperia XZ1  ROMs, Kernels, Recoveries, & Othe] Tux111:
1) Yes

2) Yes/no. Sony Stock camera doesn't work on A12 roms. And TA cant be restored on non-stock roms. But you can use this magisk module for stock camera: https://gitlab.com/xperiance/camera/-/releases its a bit limited but it works.
[Sony Xperia XZ1  ROMs, Kernels, Recoveries, & Othe] Tux111:
New update is up boyz ;)
[Sony Xperia XZ1  ROMs, Kernels, Recoveries, & Othe] caspian_swan:
Hi, thanks for your great ROM

İs there any way to;

1- remove name of app and show only app icon at home screen?

2-set default home screen. Currently i have two home screens, but like older Android versions i can not find any way to set the default one.
[General Questions and Answers] Lusty Rugnuts:
Hi, all.

So I bought a Murena Teracube 2e running Android 11. This phone originally comes from Teracube, but the /e/ foundation buys the phone, flashes /e/ OS to it, and resells it. It's a de-Google'd phone.

I somehow messed it up in trying to push build.prop in recovery mode and it went into a boot-loop so bad it wouldn't even give the options to boot into fastboot or recovery mode. I hadn't actually made any changes to the phone at the time (except to completely disable aGPS and change the launcher from Bliss launcher to OpenLauncher), because adb push failed (the phone's got the super partition setup, so pushing build.prop doesn't work as before because /system is read-only), the boot-loop happened when I rebooted the phone out of recovery mode.

So, I attempted to flash the OS to the phone via SP Flash... the flash completed successfully, but it continued to boot-loop. Something somehow got corrupted.

The only way I could get it to come out of boot-loop was to completely erase everything on the phone via SP Flash, flash the Teracube OS, then flash the /e/ OS after that.

The problem: in erasing everything on the phone, it erased the IMEI numbers.

How does one get the IMEI numbers put back into the phone?

This phone is not rooted (I'm actually unsure how to proceed on rooting it, given the super partition setup), but does have root ADB, if that'll help at all.
[General Questions and Answers] DragonPitbull:
You need IMEI numbers from box or other local.

You can use the tool for Mediatek phones with or without root.

Modem Meta download.
[General Questions and Answers] DragonPitbull:
With stock recovery installed?

Errors is because u not have MTK Drivers installed like VCOM and cdc-acm files/drivers.

You need install correct in your PC. After the phone conect ModemMeta and you can modify anything about IMEI and others things.
[General Questions and Answers] Lusty Rugnuts:
Yes, stock recovery is installed... it's the /e/ OS recovery.

Just to be sure I had the latest drivers, I uninstalled all Android-related drivers in Device Manager, and installed the latest. Then I cycled through Normal Mode, Recovery Mode, Fastboot Mode and Fastbootd Mode to ensure all the drivers had been enabled in Device Manager.

No change, still times out.
[General Questions and Answers] DragonPitbull:
You need connect phone off for Meta Modem work.

If connection close again is because drivers not installed. U need change VCOM to CDC-acm driver. How to install Mediatek CDC serial driver

How to use Modem Meta tool

imei repair any mtk device with MODEM META

We have writing about Mediatek drivers and not only adb driver! See the How to install Mediatek CDC serial driver link and test.

Very phones have something blocked. In that situation you need using mtk client for unblock (not unlock!) phone so look and read the mtkclient github if you need.
[General Questions and Answers] Lusty Rugnuts:
♫♪ So close... so close and yet so far. ♫♪

I set Maui META v10.1816.0.1 to Platform Type: Dummy AP, and checked the 'Switch Modem Mode: Normal mode -> META mode' checkbox, and it went all the way through to 'Connect MD' (the final step), then timed out at 99%.

It does the same with the 'Switch Modem Mode: Normal mode -> META mode' checkbox unchecked.

So it can get past 'Get SW Info', just have to figure out how to get it to connect.
[General Questions and Answers] Lusty Rugnuts:
Ok, let me record this here before I change anything in Maui META v10.1816.0.0...

IT CONNECTED!

Settings:

Platform Type: 'Dummy AP'

COM Port: 'USB Comm'

Baud Rate: '921600'

'Switch Modem Mode: Normal Mode -> META Mode': checked or unchecked

Active Modem: '1'

Service Type: '3: ETS'

Channel Type: '2: Tunneling'

It also connects with:

'Switch Modem Mode: Normal Mode -> META Mode': checked or unchecked

Channel Type: '3: TUNNELING NO CKSM'

It also connects with:

'Switch Modem Mode: Normal Mode -> META Mode': checked or unchecked

Channel Type: '4: ETS'

OK, now to see if I can actually change anything in the phone.
[General Questions and Answers] Lusty Rugnuts:
Mheh... this phone doesn't have a stand-alone nvram.img file, it's wrapped into super.img due to the super partition setup.

So how to proceed from here?
[General Questions and Answers] DragonPitbull:
No!

NVRAM, NVCFG, NVDATA is partitions of very MTK phones.

The Super partition have only System, Product, Vendor partitions.

Maybe your phone is 32 bits? If yes so that's more problem than 64 bits phones.
[General Questions and Answers] Lusty Rugnuts:
Neither the Teracube_2e_A11_05_20211102 ROM nor the IMG-e-0.22-r-20220307169166-stable-emerald ROM have an nvram.img file in them.

The Teracube_2e_A11 ROM is the original ROM from Teracube, the IMG-e-0.22-r ROM is what /e/ Foundation flashes to the phone to de-Google it.

Architecture: arm64
[General Questions and Answers] DragonPitbull:
IMG-e-0.22-r-20220307169166-stable-emerald

That's a LOS firmware?? If yes so nor custom firmware have acess to META Mode! Only stock firmware.

If is a stock firmware so thats a not problem and NVRAM is not problem if you not make FORMAT+options in the SPFT.

You made FORMAT+option in the SPFT?? If yes so, yeah; its a problem! You need nvram.img from other Teracube_2e_A11 same model or Meta Mode never connecting the phone vs software.

PS. Attached my phone testing with Modem Meta to you see.
[General Questions and Answers] Lusty Rugnuts:
Yes, the Teracube OS is based upon Lineage OS.

I've updated to Modem META v 10.2036.0.4, let's see how well it goes.

{ 20 minutes later }

Nope, same issues.

Where is the nvram.img file? I can't find it in either downloaded ROM, so it's got to be wrapped into another .img file, I think.

Yes, this phone got stuck in a boot loop. I attempted to flash the latest /e/ OS, but it was still stuck in a boot loop... something was corrupted.

The only way I could get it out of the boot loop was to erase everything on the phone, flash the Teracube OS (I was running the original Android as the phone comes from Teracube at that point), then flash /e/ OS over that (I was running the de-Google'd /e/ OS at that point). In erasing everything, though, it wiped the IMEI numbers.

How do they flash the IMEI numbers to the phone 'from the factory'?
[General Questions and Answers] DragonPitbull:
Look: NVRAM, NVCFG, NVDATA is partitions for each MTK phone. So that's have IMEI numbers and cannot share with others!

But if anyone with same Teracube 2e A11 phone can make the Read Back process with SPFT (you and other user need search - learning How to do) or if have TWRP, so that user can share (if's decision of him) with you and you can flash with SPFT.

When you made FORMAT+option in the SPFT so the NVRAM, NVCFG, NVDATA erased too. Because that very very experienced users always writed about not choose FORMAT option!

Now you need nvram.img - after flashed with SPFT you can see the IMEI in your phone from other phone - use the Modem Meta to write yours IMEIs.

Without that so the phone never have IMEI, network connection.

Good Luck.