yashsingh1/xdaforums huggingface dataset:
[Asus ROG Phone Guides, News, & Discussion] MichaelCaditz:
Another similar story:

https://xdaforums.com/rog-phone/help/defective-screen-idea-cost-to-repair-t3878297/amp/

---------- Post added at 10:52 PM ---------- Previous post was at 10:49 PM ----------

And another:

https://www.asus.com/zentalk/in/thread-270274-1-1.html

This scheme by ASUS to blame a ROG Phone screen defect on customers is rampant. Do we have a lawyer who is willing to take on a class action lawsuit?
[Asus ROG Phone Guides, News, & Discussion] Tesla74:
Not a lawyer, but I found these two websites that might help:

https://www.usa.gov/consumer-complaints

https://www.consumer.ftc.gov/articles/0252-warranties
[Asus ROG Phone Guides, News, & Discussion] MichaelCaditz:
My invoices are coming from Fremont, CA, so it looks like I'll also be filing a complaint with the California Attorney General.

https://oag.ca.gov/consumers

There are also consumer advocate shows on radio and television. Those could be quite embarrassing to ASUS.

https://www.nbclosangeles.com/consumer-form/

https://abc7news.com/7onyourside/
[Asus ROG Phone Guides, News, & Discussion] MichaelCaditz:
I just received an email from ASUS "CEO's office" saying that my phone will be repaired free of charge. Now I will wait to see when and what I receive back from ASUS service center.
[Asus ROG Phone Guides, News, & Discussion] samshak01@gmail.comr:
Asus Inner display broken without physical damage

Hi have brought the Asus ROG Phone on 14 Jan 2019. while i was playing PUBG , Suddenly my phone was blackout and i have checked that inner display cracked without physical damage. I couldn't see single scractch on the outer glass.

But when I was check with service centre and they are saying this will not be comes under warranty and they were also saying silly answer like inner display might be get damaged because of finger impression and placing the phone inside pant pocket.

RMA NUMBER: INUIK40199

I was shocked about the answers from technician. so ASUS company has manufacturing cheap, weak display for the permium phone.

my friend has advised me that don't go for ASUS ROG phone , it has cheap and week LED display but i didn't listen that.

Can you please help to escalate team.

Please see the below link as many of the buyers has been facing the inner display broken issues, now tell me that is ur Asus ROG PHONE has weak and poor quality display
[Asus ROG Phone Guides, News, & Discussion] MichaelCaditz:
samshak01:

As you have noted this is a common problem with ROG phone. So far ASUS has not acknowledged this problem and it is attempting to collect fees of approximately half the cost of the phone for repairs. Until such time as ASUS decides to fix this defect under warranty, each user is on his or her own to argue for warranty service.
[Asus ROG Phone Guides, News, & Discussion] Tesla74:
If you haven't already, I highly recommend posting on the ASUS support forum. Reference this thread. If you do send your phone in, take a lot of pictures of it first and back up your data.

Please post your ASUS support forum thread here and I'll add it to the OP. The more we document that this is a problem the better it is for us.
[Asus ROG Phone Guides, News, & Discussion] MichaelCaditz:
ASUS will be releasing ROG Phone 2 soon.

https://www.digitaltrends.com/mobile/asus-rog-phone-2-news/
[Asus ROG Phone Guides, News, & Discussion] Tesla74:
I've updated the OP with more information. :good:
[Asus ROG Phone Guides, News, & Discussion] rodfranklin0311:
They got me, too

I'll just post what I posted on Zentalk. But here is the link to my Zentalk post that has the ridiculous pictures added to it:

https://www.asus.com/zentalk/ww/thread-272455-1-1.html

What follows is what I posted in the thread minus photos:

This is happening to me right now. This is the second time my screen has done this. This first time ASUS fixed it no problem. This time ASUS sent two pictures back from their service department stating the screen was cracked from 'impact damage'. Note that the screen is not cracked, the glass is fine. The LCD UNDER the glass is somehow cracked.

When I sent the phone in the screen was completely dead with a very short crack on the right side of the LCD under the glass. I'm talking maybe a quarter inch. They sent a picture back with TWO cracks going all the way across the screen! That was not how I sent the phone in to them! Further, I babied that phone. I NEVER dropped it and never abused it. I was watching TV, looked at my phone, then put it in my pocket. About a half hour later I looked again and there was a spot the size of the pad of my pinky finger that had gone dark and rainbow colored around the edges of the dark spot. As the hour progressed the screen progressively died as I just sat and helplessly watched, not even touching it. It's the EXACT way it died the first time.

The picture of the 'impact damage' is a joke. I had to look extremely hard to see any irregularity in the picture, and I don't see how that would have caused the crack, or how it would have even happened IN MY POCKET. Further, I had the case on it from day one THAT I BOUGHT FROM ASUS. I have never taken it off. I followed all their directions for shipping, bought their shipping label, I did everything I was supposed to do and now somehow my phone is MORE damaged than last time I saw it, and they are trying to say I somehow damaged it via 'impact'?? No! I had my wife look at the picture and she seriously doubts that's even my phone! She doesn't think the crack is even in the same place! I never even thought about taking pictures of my own phone, who thinks about doing that? But my 'dispute' just ended in an e-mail stating physical damage isn't covered by warranty. The guy on the phone asked if I had any pictures of my phone from BEFORE it was damaged. My phone is my camera, how am I supposed to take a photo of my camera with my camera, and why would I do that to begin with?

There is no way this was done by physical damage!! And now they want me to dish out 400 dollars? I can't afford that! Anybody have any ideas? If I can't get it fixed under the warranty like it should be, especially since it would be IT'S THIRD SCREEN, then I'll just have to dish out the extra cash and buy a new Razer Phone 2. I don't see another option here. If I pay the 400, this will more than likely happen again and then I'll have to go through this whole mess all over again. And to think this whole time I was braggin up ASUS to everyone, showing off the phone. All my PC parts are ASUS. I guess if this doesn't get fixed, I'll have learned my lesson there, too.
[Asus ROG Phone Guides, News, & Discussion] rodfranklin0311:
I've yet to hear anything from ASUS and they still have my phone. Just to update you all. I'll update the other sites I've posted on as well.
[Asus ROG Phone Guides, News, & Discussion] rodfranklin0311:
Just heard back from Customer Loyalty and they won't fix it without the 400 dollars. This, they said, was after they lowered the cost of fixing it. So i told them if they are refusing to fix their faulty product to just send it back to me so I can use it as a paperweight, and I'll notify all the appropriate forums, websites, and reviews on Amazon, Newegg, XDA, Zentalk, and warn family and my entire department about using ASUS for anything. I'll be looking elsewhere for all my PC hardware now, also. Apparently my favorite company is now being run by people that have no care for product quality and customer loyalty. Sorry, everyone. I was hoping ASUS would come clean and fix their problem. Clearly I was wrong. I'll be sending everyone over to Razer from now on for gaming phones.
[Asus ROG Phone Guides, News, & Discussion] Tesla74:
Thanks for the update. Too bad this is happening. I'll add a link to your thread in the OP.
[Asus ROG Phone Guides, News, & Discussion] ImpressiveNewtype:
Bad Services By Asus

Ohh Asus is such a bad company.. i wanna go for iphone but, apple os system is so crap full with limitations and also customer service always ask alot money.. me too havin bad day with the 1st day i bought that Rog phone.. Luckily after 1week i got my phone back from asus service center.. I don't know what they do to my phone, at least my phone not auto reboot again when i plug in that aero active cooler fan.
[Asus ROG Phone Guides, News, & Discussion] MichaelCaditz:
There is a defect in the ASUS ROG phone screen and ASUS policy it to blame it on the customer and demand about half the cost of the phone to repair. In my case, I did not give in and after seven weeks I won.

WARNING! Before sending the phone in for repair, take detailed pictures of the phone as it goes into the shipping box. ASUS will send you pictures of a damaged phone WHICH IS NOT YOURS to try and prove you damaged your phone.

See my thread:

https://xdaforums.com/rog-phone/help/zs600kl-screen-dead-t3915901
[Asus ROG Phone Guides, News, & Discussion] MichaelCaditz:
Read this story:

https://piunikaweb.com/2019/05/02/a...orm-inside-for-many-rma-denied-in-most-cases/
[Asus ROG Phone Guides, News, & Discussion] Biedronczak:
Asus don't care

Well they dont care about their ROG Phone cuz they soon release ROG Phone 2. So Asus try to grab as much money as they can cuz selling point was not achieved. But thats what i think. When Xiaomi release their Rrd Magic 3 with Android 9.0 integrated fan and half of their price ROG Phone is just overpriced piece of tech with expensive accesories.
[Asus ROG Phone Guides, News, & Discussion] omgdracula:
https://www.asus.com/zentalk/thread-275797-1-1.html You can add this to the list. My phone just did this yesterday
[Asus ROG Phone Guides, News, & Discussion] vb0108:
Well I haven't caught in the situation like this but thanks for sharing .

If I want solve this kind of problem I surely will go through the Asus return policy
[OnePlus 6T  Questions & Answers] kccoNCSU:
Need a little help here guys. I unrooted my OP6T, and locked the bootloader. Now I have no data connection on either SIM. Thoughts?
[OnePlus 6T  Questions & Answers] Jager:
With the lack of details on your problem I can only grasp at straws here....

Check the APN settings for each SIM.
[Android Q&A, Help & Troubleshooting] gintama_me:
Hello and sorry my English.

Please help to avoid brick of my smartphone.

There is a smartphone Meizu MX4Pro. The bootloader is locked bc of greedy Meizu. I don't know what it means but osm0sis said here it's U-boot device.

So. As far as i know if the bootloader is locked Ican use flash images (*.img files) if they are signed by Meizu. Correct ?

I want dump ramdisk partition with dd command, patch it to be able to install Magisk and flash it back to mobile. As far as I know, android boot image and recovery have different ramdisks so modifying android's boot image ramdisk it shouldn't corrupt recovery work? but If patching will be unsuccessful will be I able to boot recovery and flash firmware ?

And if recovery will be broken can I flash with fastboot recovery-uboot.img (file from firmware) and flash firmware ?

Firmware has next files.

custom\

META-INF\

system\

android-info.txt

boot.img

dtb

ramdisk-uboot.img

recovery-uboot.img

system.new.dat

system.patch.dat

system.transfer.list

zImage

Thanks.
[Android Q&A, Help & Troubleshooting] osm0sis:
You likely can't do anything if it's locked because nobody has Meizu's signature to re-sign a zip or image to be flashed.

I quite easily patched the Meizu ramdisk partition dump [MENTION=8953766]HemanthJabalpuri[/MENTION] gave me, by taking the split ramdisk, putting it in an AOSP image, patching that with Magisk Manager then putting the patched ramdisk back into the unpacked U-Boot image and repacking with it.

Presumably it would work if you could get it flashed to your ramdisk partition, but without a root exploit or an unlocked bootloader there's probably nothing you can do with it.

And yes, by the sounds of it recovery ramdisk is in its own separate partition and should continue to work fine

[ Attachment removed ]
[Android Q&A, Help & Troubleshooting] HemanthJabalpuri:
Great idea....

I have patched manually by replacing init with magisk one and placing original init in .backup...

Without knowing this simple trick...
[Android Q&A, Help & Troubleshooting] osm0sis:
I thought about that but realized it would be a pain to manually go through all of it, plus I think you forgot the sepolicy binary also needs patching by magiskpolicy.

The only thing missing are the kernel binary patches which shouldn't be necessary with an in-ramdisk monolithic sepolicy binary and no system-as-root on this device.

So mine should have everything necessary for working root here, but again, sounds like no way to flash it. ¯\_(ツ)_/¯

Edit: Oh wait, I see from that firmware list above there's also a dtb partition. That might need manual patching from magiskboot as well to have working root.
[Android Q&A, Help & Troubleshooting] HemanthJabalpuri:
Magisk searches for dtbo right?

but dtb from above firmware updater-script flashes to by-name/dtb....

So we dont need to patch it?

May be I am wrong?

I dont have experience with dtb dm-verity etc since I am using KitKat...:(
[Android Q&A, Help & Troubleshooting] gintama_me:
So files that are inside of firmware zip files don't have their own sign but the whole firmware zip file has only ? Should I try flash recovery-uboot.img via fastboot ?

that was dump I made from my smartphone and sent to [MENTION=8953766]HemanthJabalpuri[/MENTION].

I have supersu on my smartphone and mod of TWRP recovery that lay above native recovery and can install ROMs.

So can we flash pathed ramdisk ?
[Android Q&A, Help & Troubleshooting] osm0sis:
Since they've split up what would normally be in an AOSP boot.img into separate partitions, presumably the dtb is the equivalent to the old Samsung dtb section appended to the end of a boot.img, or the (more standard) dtb part of Image.gz-dtb.

I'm not sure if a device from 2014 would need to have it patched, but Magisk should only patch it if needed when run though the highlighted script (rename the dump to dtb first): https://github.com/topjohnwu/Magisk/blob/master/scripts/boot_patch.sh#L158-L160

Oh, so you've got root with SuperSU, you just don't have Magisk? I see now. How did you get SuperSU on it?

Yes most likely the firmware zip is signed and their recovery will check it and only allow their signature. But if you've got TWRP any flashable zip should work fine.

I doubt fastboot will let you do anything if your bootloader is locked, but since you have root already that doesn't matter, just dd the patched file to the ramdisk partition in TWRP or from a root # prompt while booted.

You shouldn't need to flash recovery-ramdisk.img from what you're telling me. Just leave it alone.
[Android Q&A, Help & Troubleshooting] gintama_me:
Flyme OS (meizu OS) has built in root if you has a flymeos account (phone number as login and password). So all I need is enable root from meizu, install SuperSU and give it permission from meizu-root. All another program get root from SuperSU.

Yes. If I make replacing boot.img recovery says firmware is corrupted.

Magisk can't patch system while installing through TWRP.

I can't use ADB from TWRP. When I go to shell (adb shell) I just can't get root user. Perhaps I need mount /system manually in TWRP.

So can I try flash patched ramdisk via dd and don't worry get brick? Or should I try

fastboot flash recovery-uboot.img

first ?

And can you please give me my ramdisk you patched with Magisk Manager.

Thanks.
[Android Q&A, Help & Troubleshooting] osm0sis:
Your setup still isn't making a lot of sense the way you explain it. Does fastboot work at all for your device? You say your bootloader is locked, so fastboot shouldn't work for you at all, but you keep bringing up fastboot commands. If you have root anywhere (TWRP or booted, via SuperSU) then you should be able to use dd or cat to dump/flash partitions.

You also say you have TWRP over your stock recovery (sounds like the way people used to temp flash ClockworkMod recovery), but then you keep talking about reflashing recovery and potentially bricking your device. If you have a working TWRP or recovery then there shouldn't be any brick you can't recover from.

In TWRP go to Advanced, there's a Terminal option which should give you a root prompt without an adb connection.

The Magisk-patched ramdisk is for your ramdisk partition, NOT your recovery partition, and NOT your boot partition.

I already posted it for you in my first reply to your, scroll back and read.

You should upload a dump of your dtb partition for me too, and I'll run it though magiskboot to make sure it is patched as needed. Once you've got my patched dtb and ramdisk.img you should cd to the same directly as the patched files and flash them from a root # prompt like this:

`cat dtb_patched.img /dev/zero > /dev/block/platform/15540000.dwmmc0/by-name/dtb`

`cat ramdisk-uboot-magisk_patched.img /dev/zero > /dev/block/platform/15540000.dwmmc0/by-name/ramdisk`
[Android Q&A, Help & Troubleshooting] gintama_me:
you are right . It's a risk.

Can you pls tell me how to do it ?
[Android Q&A, Help & Troubleshooting] XRed_CubeX:
I think if you use Supersu to install magisk it's not a bad idea. Forgive me if I'm wrong but my last Meizu was a m3 note and since then I've never used SuperSu so I don't remember how it works.
[Android Q&A, Help & Troubleshooting] gintama_me:
It's not possible.
[Android Q&A, Help & Troubleshooting] osm0sis:
Your answer "it's a risk" did not make sense with what I was saying. Unfortunately I feel we are not understanding each other due to a language barrier. You not being able to follow my instructions because you do not fully understand them will be the biggest risk I think.

Dump dtb the same way you dumped ramdisk and kernel for [MENTION=8953766]HemanthJabalpuri[/MENTION]... While booted, open Terminal Emulator app. Type `su` so you are at a root # prompt. Then `dd if=/dev/block/whatever/by-name/dtb of=/sdcard/dtb.img` and upload dtb.img here.

You will need to figure out what "whatever" needs to be, because I do not have your device. I can tell you the full command for sure if you give me `ls -alR /dev/block` from a root # prompt on pastebin.com.
[Android Q&A, Help & Troubleshooting] osm0sis:
Good to hear you can do it, because, again, that's contrary to you asking me how to do it your post before..

/data/adb/magisk/magiskboot dtb-test dd_dtb.img
Loading dtbs from [dd_dtb.img]
1|:/storage/emulated/0/Download #
/data/adb/magisk/magiskboot dtb-patch dd_dtb.img
Loading dtbs from [dd_dtb.img]
1|:/storage/emulated/0/Download #

An error code of 1 from dtb-test is supposed to mean verity flags were found and would need to be patched out. I'm not sure what error code of 1 from dtb-patch indicates.. maybe that it didn't need it after all?

Anyway you should be good to try my patched ramdisk.img.

Then the command to flash it from a root # prompt would be:

`cat ramdisk-uboot-magisk_patched.img /dev/zero > /dev/block/platform/15540000.dwmmc0/by-name/ramdisk`
[Android Q&A, Help & Troubleshooting] gintama_me:
I have tried this command and tried

cat ramdisk-uboot-magisk_patched.img /dev/zero > /dev/block/mmcblk0p23

Got error

root@mx4pro:/ # cd /sdcard/leo/
atched.img /dev/zero > /dev/block/platform/15540000.dwmmc0/by-name/ramdisk
tmp-mksh: cat: <stdout>: Operation not permitted
cat ramdisk-uboot-magisk_patched.img /dev/zero > /dev/block/mmcblk0p23
tmp-mksh: cat: <stdout>: Operation not permitted

..... if=ramdisk-uboot-magisk_patched.img of=/dev/block/mmcblk0p23
dd: /dev/block/mmcblk0p23: Operation not permitted
[Android Q&A, Help & Troubleshooting] osm0sis:
Interesting. Seems like you don't have true root? My next step would be to run those commands then immediately `dmesg | grep denied` since it's probably selinux related.

Then maybe SuperSU can change it with supolicy or something.
[Android Q&A, Help & Troubleshooting] osm0sis:
That all looks good! You don't need system mounted for any of this so that shouldn't matter. So, will it boot now? Any difference? You'll have root via system AND ramdisk now so a root app might be confused. You might need to clean something up so there's only one root.

The ramdisk is rooted with the latest Magisk Canary so you should install the Manager from here: https://github.com/topjohnwu/magisk_files/blob/master/canary_builds/app-debug.apk

Only other thought I had was I've seen certain partitions locked before until you issue a command like this: `echo 0 > /sys/block/mmcblk0p23/force_ro`
[Android Q&A, Help & Troubleshooting] gintama_me:
what about trying to get true root with kingroot ?

log file attached

Doesn't SuperSU have supolicy ?
[Android Q&A, Help & Troubleshooting] osm0sis:
There's nothing wrong in that log, just a lot of SuperSU stuff. SuperSU should have supolicy normally, but if it's not a normal SuperSU root then maybe not.

You didn't answer my other questions. What happened when you boot after flashing the ramdisk from recovery? It looked like it worked from recovery. You could also try dd from recovery terminal.

From a root # prompt when booted `ls -al /sbin` and `tail /init.rc`
[Android Q&A, Help & Troubleshooting] gintama_me:
I have a problem I had before now.

Installing Magisk-v18.1.zip ends up with error

Installing '/data/media/0/1/Magisk-v18.1.zip'...

Checking for MD5 file...

Skipping MD5 check: no MD5 file found

I:Zip does not contain SELinux file_contexts file in its root.

I:Legacy property environment initialized.

1038+1 records in

1038+1 records out

1063528 bytes (1.0MB) copied, 0.018904 seconds, 53.7MB/s

Archive: /data/media/0/1/Magisk-v18.1.zip

inflating: META-INF/com/google/android/update-binary

inflating: META-INF/com/google/android/updater-script

inflating: arm/magiskboot

inflating: arm/magiskinit

inflating: chromeos/futility

inflating: chromeos/kernel.keyblock

inflating: chromeos/kernel_data_key.vbprivk

inflating: common/addon.d.sh

inflating: common/boot_patch.sh

inflating: common/magisk.apk

inflating: common/util_functions.sh

inflating: x86/magiskboot

inflating: x86/magiskinit

inflating: META-INF/MANIFEST.MF

inflating: META-INF/CERT.SF

inflating: META-INF/CERT.RSA

************************

* Magisk v18.1 Installer

************************

- Mounting /system, /vendor

- Target image: /dev/block/mmcblk0p23

- Device platform: arm

- Removing system installed root

- Constructing environment

Invalid image: not signed

- Unpacking boot image

MagiskBoot v18.1(18100) (by topjohnwu) - Boot Image Modification Tool

Parsing boot image: [/dev/block/mmcblk0p23]

No boot image magic found!

! Unable to unpack boot image

- Unmounting partitions

I:Legacy property environment disabled.

E:Error executing updater binary in zip '/data/media/0/1/Magisk-v18.1.zip'

Error flashing zip '/data/media/0/1/Magisk-v18.1.zip'

Updating partition details...

I:Data backup size is 1694MB, free: 2503MB.

...done

Magisk-v18.1.zip deleted my superSU and install it's own superSU installer which can't install SuperSU(I tap on SuperSU on Meizu uppstore and nothing is happen). So I have installed supersu as I did before - by APK via ADB and adb-supersu have replaced supersu installer wich was installed by Magisk-v18.1.zip under TWRP .

What I have noticed now :

1. supersu works , I have created a folder in /system by root explorer, rebooted and deleted it

2. meizu root can't see super su. So super su with patched ramdisk no need meizu root as before

3. Magisk manager cant update and can't install Magisk

What next ?
[Android Q&A, Help & Troubleshooting] gintama_me:
Nothing unusual except replacing supersu and I gave an answer above already

I think ramdisk is patched but why I can't install Magisk from TWRP ?

root@mx4pro:/ # ls -al /sbin
-rwxr-x--- root root 309812 1970-01-01 03:00 adbd
-rwxr-x--- root root 328840 1970-01-01 03:00 healthd
lrwxrwxrwx root root 1970-01-01 03:00 ueventd -> ../init
lrwxrwxrwx root root 1970-01-01 03:00 watchdogd -> ../init
root@mx4pro:/ #

shell@mx4pro:/ $ su
root@mx4pro:/ # tail /init.rc
mkdir /data/misc/vbus 0750 system system
mkdir /data/misc/vbus/sockets 0750 system system

service netdiagn /system/bin/netdiagn -p/data/misc/vbus -ibus0
class main
socket netdiagn dgram 0660 system system
disabled
oneshot
# @}

root@mx4pro:/ #