yashsingh1/xdaforums huggingface dataset:
[ASUS ZenFone 8] silv3rfox:
Funny enough, I was looking into alternative to Mi 12 (and Mi 12X), and was more interested in the Zenfone 8. But after reading this, I am more skeptical.

For me currently the Z8 has more ROM support (Mi 12 and 12X are non-existent), and better chip then 12X (possible supported longer), and better camera. But this issue of sudden death is absolutely a deterrent. I don't want to go with what OP went through. Maybe I should wait until the Mi 12X gets some dev ROMs and reconsider (I hate MIUI with all its botnets and bloats).
[ASUS ZenFone 8] Blumi511:
You'll be well off. The cases of ramdump vanished and I suppose if you have the refined model, it is not going to happen to you
[ASUS ZenFone 8] HyperCriSiS:
My new phone is also now in RAM dump mode right after flashing the modified Magisk boot image :mad:

Did I just have bad luck or what could I have done wrong? After several tries to boot it shows "Your device is corrupt. It can't be trusted and will not boot."

Does anybody know whats going on here?

When I reflash the patched boot image, it still stucks in boot loop, but without the corrupt message.
[ASUS ZenFone 8] Adaoh:
If its due to a bad flash, don't worry, just hold the power button and the volume buttons so you can go into the bootloader and use the reset script to re-write every partition to a default state and start again. Maybe your magisk image is corrupt. I would check the cheksum to verify that its good. Also, maybe that image just does not behave well with the zenfone 8, it happens sometimes

I have encountered a ramdump screen several times because of bad manipulations and was always able to recover, don't worry, there's a 95% chance it's not a ramdump screen of death if its due to a bad flash :)
[ASUS ZenFone 8] Voodoojonny:
Yeah, I've installed stock fastboot rom, relocked my bootloader, sold my zf8 and bought th 12x...I'm happy TWRP and oxygen already there...
[ASUS ZenFone 8] Muaddib69:
Which MFD are the bad&ugly guys?
[ASUS ZenFone 8] dron39:
I don't think it's known. We saw some stats here and on zentalk that there were 04.2021 and 05.2021 who got ramdump. There were 06 or 07 month too, but only a few devices.

And by the after some SW update ramdump cases decreased drastically.
[ASUS ZenFone 8] Muaddib69:
BINGO!

Mine is 2021.06

(ouch)
[ASUS ZenFone 8] FastJack2:
great, i got a 04.2021 shipped in december 21 -.-

... maybe i should relock that bootloader soon and always keep a backup?

are there reports of the age of the devices getting ramdump? to go like "if your device survives 6 months, it should last forever"?
[ASUS ZenFone 8] Blumi511:
You should always keep a backup of any important data.

After around 4 to 6 month most ramdump cases were experienced from my knowledge. But the amount of people was limited. We had around 40 tracked cases at asus.zentalk. my device was also manufactured in April 21 and is still alive (working like a charm).

Where are you living?
[ASUS ZenFone 8] FastJack2:
in Germany, so i'm at least covered by extended customer rights ;) I always keep backups of the really important data but in this case i think i'll be keeping a backup of the "not-sooo-important" data also ;)
[ASUS ZenFone 8] Blumi511:
Ah se dschörmens, Grüße aus Frankfurt!

Well, then you are good to go in my opinion. Just keep backups and your receipt.

In the past, phones with heating issues and other stuff, which looked hardware related tended to receive the ramdump feature.
[ASUS ZenFone 8] FastJack2:
Grüße zurück aus dem Norden ;)

Okay, well, mine is not heating, sometimes gets a bit warm but not as warm as my old OPT under load, so i think i'm good to go, wanted to try some custom roms and like to be on the safe side ;)
[ASUS ZenFone 8] eVen123:
I don't know if it's relevant - I got a RAMdump a couple a week and a half ago.

The phone just out of the blue went into the ramdump screen. I was terrified. In the end, I just rebooted it and it was fine. It happened once again, but a reboot worked.

After that, I got an update to LOS and now, I've received no more ramdumps. It seems to just have been one ROM update where this was an issue. I can't confirm/vouch that it was ROM related, but it seemed that way, since it's now gone.
[ASUS ZenFone 8] Adaoh:
Yeah LineageOS sometimes crashed on me while charging with the stock charger. Weird behaviour as it does not happen on stock for me. Happy to know that it is now fixed though!
[ASUS ZenFone 8] Boneface Johnson:
I have now my second ZF8, because i like it a lot. The first died suddenly in the first 6 months or so, luckely i got refund from the seller after a long email discussion. My secod Zenfone is still working. Its rooted like the first one.

Today the phone of my girlfriend died, seams like "sudden death" too. She bought it used so no chance of refund, but despite so little chances of help I will try to somehow get in touch with Asus for an explanation and a solution.
[ASUS ZenFone 8] mihalru:
I have very similar problem. My Zenfone 8 died at around 19% battery. No response now. Did you manage to recoer your files without breaking the warranty?
[ASUS ZenFone 8] Boneface Johnson:
edit:

Good News!!

Short version: after one month emailing back and foth and arguing with Asus:

I got refund a free new/repaired ZF8 in exchange to my defect and BOOTLOADER UNLOCKED phone.

long version:

first of all: I bought the phone for my GF. It was used with a unlocked bootloader and rooted, but younger than 2 years, so theoretical in warranty.

First I fullfilled RMA formular and send device to Asus.

In the beginning they declined the phone because "the device is not covered by warranty, because the given issue is a softwareproblem and thus not covered by warranty.

Then the send my a cost estimate over 528,48€ for repair. Thats hillarious, almost the price of a new phone.

I send an email and explained the issue while claiming it's a hardware issue. In this email I linked these forums:

Zenfone 8 died while in use - did this happen to anyone else?

While i was scrolling around on the phone in suddenly died on me. From scrolling the web to absolute dead in my hands. It does not charge, it is not recognized by a PC, it does not go in boot mode or anything like that - absolutely dead. I had it for 1 year and will not fix it as fixing cost...

zentalk.asus.com

https://xdaforums.com/t/zenfone-8-s...ause-of-an-unlocked-bootloader.4335101/page-2

https://www.reddit.com/r/ASUS/comments/pshs89

https://www.reddit.com/r/zenfone8/comments/pd2ga2

and told them to read carefully.

Answer: No warranty, because of unlocked bootloader.

Me: Unlocked bootloader has nothing to do with hardware issues. Have you read in forums?

(Meanwhile ignoring emails refering to processing fees and the cost estimate.)

Asus: Unlocked bootloader, means no warranty. Try to contact your seller and ask him for refund.

Me: First I don't know how the reseller could help, becaus it's Asus fault. Second I don't care about warranty, fact: the device was faulty immediately after it left the production. I payed for the device, so Asus has to deliver. Maybe you didn't get the issue correctly so please explain it to me:

Why has my phone died?

Asus: We will check your issue and we get in touch again.

Asus: Dear customer, we will offer you a free repair.

Now the repaired or maybe new phone is on the way to me.

Guys stay strong!! Take the time, It's worth it!!

Greetings
[ASUS ZenFone 8] Boneface Johnson:
Good news, read here!!!

https://xdaforums.com/t/zenfone-8-s...-an-unlocked-bootloader.4335101/post-87095541
[ASUS ZenFone 8] blackhawk:
Yay! Maybe Asus has seen this issue on the ones running stock... more then a few times🤣

Only persistent is omnipotent.

Misconfigured firmware can blow out hardware so Asus is well within their rights to deny a claim, especially if it's stated in writing.

Sometimes Samsung will warranty the display on a rooted device but charge the owner for a new mobo to "fix" the user caused damage🤣

Outcomes in these situations can be varied and at times bizarrely counterproductive.
[ASUS ZenFone 8] vexebaj:
Hi. On what email is possible to contact this bastards ?? Asus i mean .
[ASUS ZenFone 8] duduhayo:
My asus also died suddenly. I hope someone will find a way to exit edl mode without fastboot. I will never buy asus again, this is the first phone that died in my life. I even have 6 years phone which fell the toilet lol.
[ASUS ZenFone 8] lulu1975:
I unlocked my new Zenfone8. then I had flashed the new E-OS system. and somehow I put it in my pocket wrong, and now the phone doesn't tell me it's unlocked! and it only goes to the green START screen Can someone help me?
[ASUS ZenFone 8] sazrul:
Damn, I also have the same issue. My Zenfone 8 suddenly died with no sign of LED when I wanted to charge the phone and the battery health is still at 25%. My first Asus phone and really disappointed with Asus.
[ASUS ZenFone 8] blackbile:
What is the MFD of you phone on the original box?
[ASUS ZenFone 8] Jurigag:
I guess I am writing this too late - use EU law and return it to seller, not to ASUS. They have to fix it or return you your money, if it's 2 years or less.
[ASUS ZenFone 8] LineOFire:
My zenfone 8 died suddenly, still under warranty but I was not recognized because according to them I had unlocked the bootloader. The assistance service for Italy where I live if he kept it a month, I shot a quote for the replacement of the motherboard of € 494

Obviously I did not accept and I had him sent back. Taken to a service center in my area and they confirmed that it hadn't even been opened. Sleeve of bastards. A new phone to throw in the toilet. No more Asus!
[ASUS ZenFone 8] blackhawk:
Sweet.

Does rooting the warranty in EU?
[Nokia 5.4] 1447047:
Hi. I bought a few days ago a Nokia 5.4 and the box seems to have a weird pattern. I am now lurking the forums and unboxing videos to check if maybe I was sold a fake.

I attached a picture with the problem. One the sides, one of the flaps is completely glued to the side walls, and one is completely not glued and flips freely.

Is this normal? do others have the same boxes? i cant afford to buy a new one to check it out.View attachment 5412215
[Redmi Note 9 Questions & Answers] Ch Tech:
sorry if I ask so many questions but I have so many doubts to remove. it is possible to have twrp, Orange fox or a custom rom wuthout bootloader unlock?
[Redmi Note 9 Questions & Answers] VD171:
No.
[Redmi Note 8 Pro Questions & Answers] Laminesls:
Ineed kernel suppert kcal for asop rom rn8pro
[Xiaomi Mi 9 Guides, News, & Discussion] Gokh:
Anyone else installed it?

Uploading the update package...

miui_CEPHEUSEEAGlobal_V12.5.1.0.RFAEUXM_64d22ba46c_11.0.zip

drive.google.com

View attachment 5412223
[Xiaomi Mi 9 Guides, News, & Discussion] Gokh:
Nothing to report so far, it's all good.
[Xiaomi Mi 9 Guides, News, & Discussion] bogdan_gy:
it is a good build,no bugs so far.the only problem I have,it's with the battery,I replaced it with original one and one day,I noticed something strange.My phone was charged 84%,it took about 2-3 hours to discharge to 83% ,the screen on time was about 7 hours and 25 minutes,and when the battery was at 66%,sot was 6 hours and 33 minutes 😳
[Touch CDMA Windows Mobile ROM Development] prometheus9000:
All you great cooks out there is the any way you guys can get togather, and make a tutorial to teach us newer guys the method on creating our own custom work to share.
[Touch CDMA Windows Mobile ROM Development] boggsie:
SYS:

http://forum.ppcgeeks.com/showpost.php?p=320656&postcount=6

XIP:

http://forum.ppcgeeks.com/showpost.php?p=378506&postcount=10

Best regards,

-boggsie
[Touch CDMA Windows Mobile ROM Development] rstoyguy:
Sorta like these??? Start with the bottom one, and work your way up...
[Touch CDMA Windows Mobile ROM Development] prometheus9000:
Thanks

Thanks for the help guys.

I will read all your guys tutorials.
[Android Software/Hacking General [Developers Only]] vk rathi:
​

>> Standard Disclaimer <<
* I am not responsible for bricked devices, dead SD cards, thermonuclear war, or you getting fired because the alarm app failed.
* Please do some research if you have any concerns about features included in this ROM before flashing it!
* YOU are choosing to make these modifications, and if you blame me in any way for what happens to your device, I will laugh at you.
* BOOM! And Turn to Ashes...!!!

What's ColtOS

Needless to say, ColtOS Project is custom ROM based on AOSP by a team of learners with all the necessary customizations, without compromising the stability and security of the device.

We have cherry-picked the features from many other open-source roms/projects and we are very thankful to all of them!

We try to keep ColtOS as stable as possible, on an off chance you faced any issues with official builds, please let us know via our official telegram group or XDA thread.

Team ColtOS

We, The ColtOS Team, are a bunch of Android enthusiast coming from a wide variety of industries (some of them don't even belong to anything related to programming or coding). But we like what we do.

We are young and growing team of learners. We are still learning and helping each other learn as well. Thanks to entire ColtOS team for giving their precious time to this Project.

​

@Rakesh Batra - Lead Developer and Founder of ColtOS

@nitin.chobhe - Core Developer

@mg712702 - Core Developer

@SaurabhCharde - Community Manager

@SuperDroidBond - Project Contributor

@Roger.T - Graphics Designer

@mukesh22584 - Project Contributor

Checkout the features here

ColtOS Builds (gapps included)

kernel source

join rom group

join device group

​

First time installation:

Download Rom,

(If you want ROOT Download Magisk)

Reboot to recovery

Format data (If Encrypted)

Wipe system, vendor, cache, dalvik, data

Flash Rom,

Flash Magisk (optional)

Reboot

Update installation:

Wipe system, vendor, cache, dalvik

Flash Rom & Magisk (optional)

Reboot

NOTE: If you fail to follow these instructions, please don't bother reporting any bugs. Also we do not

support any Xposed or Magisk modules or any custom kernel so please keep in mind before reporting.

We would like to give thanks to everyone that contributes to the Android community, big or small because every bit counts. Although we can't list each and every contributor within the Android community, we would like to highlight some of the teams and individuals that have made it possible NOT only with just this version of COLT but throughout the years because we don't ever want to forget where we came from nor those that have helped us!

That said, ColtOS team would like to thank to....
​

* LineageOS / Cyanogenmod

* Project-Xtended

* EvolutionX

* OmniROM

* Nitrogen OS

* AICP

* crDroid

* DirtyUnicorns

* Bliss Roms

* BootLeggers

* AOSP Extended ROM

* DerpFest

* Project-404

* DotOS

* CorvusOS

**If we have left someone or some team, we apologize and please PM us. We would be very happy to include your name as well.**

​

casting is broken will fix in next update
[Android Q&A, Help & Troubleshooting] river8394:
Hi,

is there a widget that shows if the smartphones compass is calibrated? i used to check in google maps but now only live view is available which is not possible to use inside my apartment. i have to use the sensor menu of the phone (S21). dialing *#0*# -> Sensor -> magnetic sensor (red bad, green better, blue is calibrated.

a widget that would show these colors would suffice.

a tool that checks regularly and sends a notification would also work.

i sometimes go on hikes and forget to calibrate before.
[OnePlus 8T Questions & Answers] behel1t:
Hi everyone, I could really use some help. My KB2005 is stuck in what looks like a boot loop. I took an OTA update after going into magisk and restoring images. After the update finished installing and before rebooting, I installed magisk to the inactive slot. Now when my phone boots up, it is stuck on the spinning circle boot up logo. It stays there, screen goes black, then maybe 30 seconds later I see the boot logo again.

I used MSM download to restore my phone to stock. Re rooted + safetynetfix, attempted to take the OTA update using the procedure above, and the same result happened (boot loop).

I then used the fastboot method to unbrick. Re rooted + safetynet fix, attempted to take OTA update using the procedure above, and again the same thing happened.

My phone will successfully take an OTA and not boot loop if I'm not rooted.

I could root + safetynet fix after taking the OTA, but the next time an update comes along, I'd like to be confident that using the magisk method to install the OTA will work.

Any help would be greatly appreciated. If there is any other information I can provide that can help please let me know. Cheers

EDIT - I did some digging - according to getvar all, my slot b is not 'successful'. To confirm, I force booted slot b and get a qualcomm crush dump screen.
[OnePlus 8T Questions & Answers] azoller1:
After you used magisk to flash to the inactive slot, did you disable all of the modules before rebooting? That might help. And you are not using twrp correct?
[OnePlus 8T Questions & Answers] behel1t:
Hi, correct I am not using twrp. I tried unlocking the boot loader and not rooting. Receiving an OTA works and I can reboot. But oddly enough if I do a --set-active=otherslot, i get a qualcomm crashdump.

It appears that whenever I or magisk force change the active slot, I get a crash dump.

EDIT - Still unsuccessful. I've tried numerous times using MSM Download and the fastboot unbrick method by coomac. I haven't been able to --set-active=b a single time, it always ends up in a qualcomm crash dump. I suspect slot is B is corrupt.
[OnePlus 8T Questions & Answers] kjslabber:
Try to restore both slots with an older version of rom using local update. Then take ota and try.
[OnePlus 8T Questions & Answers] behel1t:
I'd like to give this a shot but I have a couple of follow up questions: does an older version of the rom restore both slots vs newer versions just containing one slot? Or if I have that wrong, how do I flash both slots from local upgrade?
[OnePlus 8T Questions & Answers] kjslabber:
Install rom to first slot, boot system and do local update again and reboot. That will put same version on both slots. Then take the regular update to current new version. You do know how to do local updates don't you?
[OnePlus 8T Questions & Answers] behel1t:
Thanks for the reply. I do yes. I'll give this method a shot. Cheers

UPDATE - Just finished using msm download to restore OOS 11.0.5.6 and then used local upgrade to flash OnePlus8TOxygen_15.O.20_GLO_0200_2011132216 (both 11.0.5.6). I can now successfully boot both slots!

Now I am going to root. install riru and safetynet fix in magisk.

When I am ready to take an OTA, the correct process would be to uninstall the safetynet fix and riru. Then uninstall magisk using restore images, download and install OTA but do not reboot. Go into magisk and install to other slot. Then providing a successfully boot, reinstall safetynet and riru. Is this correct?

UPDATE 2 - Qualcomm crashdump happened after taking an OTA using the method I outlined above. So I reverted back to the previous slot and am in the process of doing a local upgrade again using 11.0.5.6 to hopefully restore that slot to working.
[OnePlus 8T Questions & Answers] behel1t:
Something about magisk installing to the other slot and forcing a slot change is causing this crash dump.

I had 11.0.5.6 on both slots. I rooted. I then completely unrooted (not restore images). Took an update. That booted. I booted that. Rooted it. Then for testing, completely unrooted again. Then I received the latest OTA. That installed and booted. So I'm rooting now on the latest getting ready for daily use.

I have no idea why using magisk to install root to the other slot and forcing a slot change is not working. I'm grateful that, with extra steps, i can at least reliably receive OTAs and continue on living rooted life.
[OnePlus 8T Questions & Answers] azoller1:
So, right after the ota is finished installing, before rebooting, you go to magisk and install to inactive slot, then you reboot immediately correct?
[OnePlus 8T Questions & Answers] behel1t:
Yup. Doing exactly that results in a Qualcomm crash dump every single time.

Only way for me to bypass the crash dump is to completely uninstall magisk. I take the OTA and reboot losing root. I use twrp to dump updated boot partition, and reinstall magisk to patch the boot dump. Then fastboot flash the new rooted boot dump.
[OnePlus 8T Questions & Answers] azoller1:
Well, that's really weird. Have you tried magisk-canary? Or are you using the stable v23?
[OnePlus 8T Questions & Answers] behel1t:
I'm on v23, I haven't tried Canary.

This used to work on v23, the Qualcomm crash dump just started four days ago. What happened? In early September, I started failing safetynet out of the blue. Safetynetfix was not working so I followed the steps that are now crossed out (they were not then) at the following link. About a week after following those steps, I revisited the site to find that a new safetynetfix was released that worked. It didn't need LSposed or Xprivacylua. I went into Xprivacylua and reversed the changes i made, and uninstalled it and Lsposed. Then I applied the new safetynetfix. Immediately upon reboot, my finger print sensor started say 'finger print hardware failure' on the lock screen, and I was unable to enroll any new fingerprints; I would get a popup error saying enrollment failed.

At this point I decided to restore my phone using an unbrick method for a couple of reasons: 1) I wanted my finger print scanner to work, 2) I wanted to start fresh on my phone for a few months, and 3) I used to unbrick my phone to restore to factory all the time when I messed around with my OP5T. This is when the Qualcomm crash dumps started happening every time when Magisk installs to the other slot. I've used the MSM download linked on this forum and the fastboot unbrick method. I Qualcomm crash every time magisk installs to the other slot and switches slots.
[OnePlus 8T Questions & Answers] azoller1:
Sorry, at this point I don't know why it isn't working. You seem to be doing everything correctly so I am not sure why it's not working properly. The only thing I could think of that might be the issue is, as far as I know, that Oneplus hasn't pushed a september update yet to merge the september security patch which could be the culprit, but I cant say for certain. I know for me, I use Sakura ROM, SafetyNet was failing early september when android had pushed the september patch, but Sakura ROM hadnt merged it yet, but when they did merge it everything was working fine. Anyways, hopefully someone else may be able to give you a better answer.

EDIT: It seems the latest OOS incremental update is breaking when trying to upgrade while rooted. You need to use the full ota zip and do local manual upgrade. See the last couple of posts in here: https://xdaforums.com/t/oneplus-8t-rom-ota-oxygen-os-repo-of-oxygen-os-builds.4193183/
[OnePlus 8T Questions & Answers] behel1t:
Thanks for bringing this to my attention. This is definitely what is happening. You just just saved me from spending any more time on this mess. Cheers!
[OnePlus 8T Questions & Answers] rcbjr2:
I just wanted to add that I had same problem with my OP8T and couldn't reflash the ROM and had to send my phone to OP to get the ROM put back on. Slot B still doesn't work. You at least were able to get the phone back working with MSN.
[Samsung Galaxy S21 Ultra] ledvedder:
Is anyone else not able to open links in their corresponding apps? All my links open in the browser. Any way to fix this?
[Samsung Galaxy S21 Ultra] shaharofir:
I'm using this
[Samsung Galaxy S21 Ultra] Has_anDroid:
xda app to link Twitter not open beta 2 problem
[Upgrading, Modifying and Unlocking] modd1uk:
Ive found my old O2 XDA Orbit, its locked to O2 network, is there anyway to unlock it ?

Cheers
[Upgrading, Modifying and Unlocking] orb3000:
Please READ the Wiki, and you´ll find a way to unlock