Develop Bugs

My Letv X800 us version. have malware. it's install the app automatic.

Help. My Letv X800 us version. have malware. it's install the app automatic without my permission.
It's auto download the app in the background and install the application automatic.
and run it , how to solve this problem.
I'm really in pain.

US/international Le1 pro that is sold worldwide on many web-shops comes with very unpleasant malware package. Several malware/trojans are included in rom. Many users suffered automatic installation of unwanted software, and there will be many more in next days.

Root, flash TWRP and install any RECENT custom ROM. Cuoco 14S for stock experience or latest CM12.1 for good experience. Good luck, you can find all infos in the threads!

I had the same problem and my phone bricked trying to install TWRP. Hope to have a chance this weekend to attempt to unbrick the phone this weekend. Let me know if you find a way to install TWRP, because none of the instructions here worked. For the record, this isn't my first rodeo...I've rooted every smart phone I've ever owned.

ProppaT said:
I had the same problem and my phone bricked trying to install TWRP. Hope to have a chance this weekend to attempt to unbrick the phone this weekend. Let me know if you find a way to install TWRP, because none of the instructions here worked. For the record, this isn't my first rodeo...I've rooted every smart phone I've ever owned.
Click to expand...
Click to collapse
I had the same issue. I couldn't get my phone to boot into any of the ROMS (CM, CUOCO92) with TWRP as my recovery. After a few attempts and a few soft bricks later, I stumbled across this sequence.
1- Flash TWRP 3.0.2. At this point, my phone could only boot into recovery.
2- From TWRP, wipe phone, root, flash custom rom, then reboot into TWRP (recovery).
3- Use Fastboot to flash Stockrecovery.img. Reboot. Your phone will be able to start the CM/CUOCO ROM.

YES..... I can confirm too. this phone is installing stupid apps by itself! I just found today morning that i had a new lock screen! wtf????? I'd flash the phone right away! get your self a new TWRP and a different rom.

You can download US rom by Cuoco92 for the US version + TWRP (version 5.5.014S) here:
LETV LeEco Le1 Pro X800
by Cuoco92 *Official Release*
https://www.facebook.com/cuoco92/info/?entry_point=page_nav_about_item&tab=page_info
Developer's thread (in German):
LeEco (Le1Pro_CN/US) X800+ MULTILANGUAGE ROM CUOCO92

I have also bought X800 -but from Gearbest, my friend that already got his phone told my about the same problem like OP, I wonder if we can simplly just install the official FW from here:
http://bbs.le.com//zt/eui/le_pro1.html
will it work or this FW not competible with our X800?

Darth_h said:
I had the same issue. I couldn't get my phone to boot into any of the ROMS (CM, CUOCO92) with TWRP as my recovery. After a few attempts and a few soft bricks later, I stumbled across this sequence.
1- Flash TWRP 3.0.2. At this point, my phone could only boot into recovery.
2- From TWRP, wipe phone, root, flash custom rom, then reboot into TWRP (recovery).
3- Use Fastboot to flash Stockrecovery.img. Reboot. Your phone will be able to start the CM/CUOCO ROM.
Click to expand...
Click to collapse
can you explain little more : wipe what? , root with su? , step 3 flash Stockrecovery.img . i want to instal cuoco92 5.5.014s and i am new in that .thank you

mastika100cc said:
can you explain little more : wipe what? , root with su? , step 3 flash Stockrecovery.img . i want to instal cuoco92 5.5.014s and i am new in that .thank you
Click to expand...
Click to collapse
Go to this site,it's in Italian but everything you need is here.
http://www.androidiani.com/forum/mo...rsione-usa-ovvero-le1pro_us-marchiato-ce.html

tc0566 said:
Go to this site,it's in Italian but everything you need is here.
my question is : did anyone succeed to install cuoco92 (5.5.012s or 5.5.014s) on phone with malware without bricking it and if answer is yes - to explain how he did this step by step , because it s very important . my phone is us version and eui 5.5.011s , youtube app and browser not working.
Click to expand...
Click to collapse

http://showtop.info/letv-leeco-malware-removal-fixing-boot-loop-problems/
https://sites.google.com/site/l1prousx800/
This might be of assistance.

finally i did it : flashed twrp3.0.2 , root with su 2.76 and malware killed. thanks to all of you for your help !!!

mastika100cc said:
finally i did it : flashed twrp3.0.2 , root with su 2.76 and malware killed. thanks to all of you for your help !!!
Click to expand...
Click to collapse
Masti a can you explain the steps u followed?. As I am facing the same problem my data pack gets exhausted in a day or two due to all mallware installation.

kamaljit.lote said:
Masti a can you explain the steps u followed?. As I am facing the same problem my data pack gets exhausted in a day or two due to all mallware installation.
Click to expand...
Click to collapse
first of all what win you use ?

I am using Win10 on my PC.

kamaljit.lote said:
I am using Win10 on my PC.
Click to expand...
Click to collapse
i use win 8.1 and i am not sure about install of drivers on win 10 .
so look at this post: http://showtop.info/letv-leeco-malware-removal-fixing-boot-loop-problems/
and this : http://showtop.info/download-flash-...-version-fix-missing-software-update-youtube/
i do it as hi did but install drivers different way .
try and if you have any trouble write again

anyone who have this problem follow this => work great
1) download file update.zip as is into the root directory of the phone storage (root directory means not in any folders) from here : https://sites.google.com/site/l1prousx800/
2) power off phone
3) hold power and volume+up button at the same time to boot into recovery
4) select update
5) the update should take about a minute and the phone will reboot, and you're done.

I just got a US version today. How do I know if I have malware? I haven't seen anything untoward happening yet

chr0m said:
I just got a US version today. How do I know if I have malware? I haven't seen anything untoward happening yet
Click to expand...
Click to collapse
You almost certainly have malware, install the update mentioned above
anyone who have this problem follow this => work great
1) download file update.zip as is into the root directory of the phone storage (root directory means not in any folders) from here : https://sites.google.com/site/l1prousx800/
2) power off phone
3) hold power and volume+up button at the same time to boot into recovery
4) select update
5) the update should take about a minute and the phone will reboot, and you're done.

Root + twrp + bootloader unlock + twrp flashable stock rom - marhsmallow

If you are on Lollipop, this guide is NOT for you!
Almost none of this is my work, I just collect it and put it together in one place and I'm writing a small how-to get things done.
PLEASE ONLY PROCEED AT YOUR OWN RISK!!!!!!!!!
ONLY FOR ZX551ML
Bootloader unlock:
Currently the only way I was able to get ROOT on the phone was by installing it from TWRP which required an unlocked bootloader, so the first step is to get the bootloader unlocked, to do this please follow this steps:
1) Enable USB debugging - If you do not know what is that and how to do it, you should probably STOP right here.
2) Download and extract: Unlock 6_ZX551ML.ZIP
3) From the extracted folder run unlock.bat (This will restart your phone into fastboot mode, downgrade the bootloader and unlock it)
4) When step 3 is completed, you need to run restore.bat
If everything went on correctly your boot screen should be inverted (white background, black Asus text). This was the most risky part. I only have my phone and it worked, but if something goes wrong here you might end up bricking your phone, so please take extreme care, always read the messages on the screen!!!!!
Custom Recovery:
1) Now to get a custom recovery, please download TWRP-3.0.2-M1-Z00A.img.
2) Put your phone into bootloader mode, if your phone is currently in use, just use the following commands:
Code:
adb reboot bootloader
Alternatively you can power off the phone, remove the USB cable. Power it back on while holding the volume up button.
3) once your phone if in bootloader mode please use the following command:
Code:
fastboot flash recovery TWRP-3.0.2-M1-Z00A.img
4) Use the vol up & down to select "RECOVERY"
5) Use the power button (short press) to reboot to TWRP
ROOTING
1) Download BETA-SuperSU-v2.74-2-20160519174328-patch-by-shakalaca-for-zenfone2-6.0_(1).zip
2) In recovery select Advanced -> Sideload
3) From your computer use the following commands:
Code:
adb sideload "BETA-SuperSU-v2.74-2-20160519174328-patch-by-shakalaca-for-zenfone2-6.0_(1).zip"
4) Once it's completed installing, restart the phone to system
FLASHABLE STOCK ROM
If you have TWRP installed and you want to flash the latest stock ROM, you will need to, make sure you un-root your phone from the supersu app, reboot to recovery and sideload the zip. You can also copy the zip to your phone and install it from twrp. When installing the stock rom, your bootloader will be locked again, so you will need to unlock it (if you wish), also you will need to root again, because the root is lost. However the modified stock rom will NOT remove the custom recovery giving you freedom to flash whatever you like in the future...
XPOSED
Xposed on our device won't work if we have SuperSu installed. If you want to use Xposed modules you will need to use PHH's SuperUser instead. All files required for Xposed/Magisk/Phh's SuperUser are available in the Xposed folder.
Available modified stock rom versions:
UL-Z00A-WW-4.21.40.141-user-TWRP.zip - Updated: 2016-Oct-07
UL-Z00A-WW-4.21.40.197-user-TWRP.zip - Updated: 2016-Dec-16
Files can be downloaded from: here
Again, please proceed on your own risk.
Special tanks and credits to all the guys who made this possible, namely:
@sorg @social-design-concepts @shakalaca - For bootloader unlock
@jrior001 for the TWRP
@shakalaca - For the modified SuperSU package.

Magisk / systemless should also work?
any way to get back the noninverted Bootscreen?

Tr4sHCr4fT said:
Magisk / systemless should also work?
any way to get back the noninverted Bootscreen?
Click to expand...
Click to collapse
Yes I'm using Magisk, but even with it I wasn't able to use Google Pay. To get back to non inverted, you will need to flash the locked bootloader.

Emil Borconi said:
Yes I'm using Magisk, but even with it I wasn't able to use Google Pay. To get back to non inverted, you will need to flash the locked bootloader.
Click to expand...
Click to collapse
While essentially true the user can always use a different boot animation by flashing one via twrp. There might even be one somewhere of the unmodified asus screen.
Can anyone confirm the flashable Rom mentioned in Post #1 is MM 6.0.1? I ask because my phone upgraded itself right after I booted it up and I wondered if it was on a newer version than the downloadable one. Pretty sure the update was only security updates given it was only around 80mb.
The actuall boot screen is only a couple of seconds long while the boot animation shown
---------- Post added at 10:00 PM ---------- Previous post was at 09:02 PM ----------
Well as usual the linux users drew the short straw. The shell script is for mac users. I decided to see about running the lines manually but never even reached the "danger zone". As soon as I did an "adb reboot bootloader" I followed up with "sudo fastboot devices" (some linux distro's need sudo..some don't)....and nothing shows up although I can clearly see the device is hooked up and in fastboot mode as well as the fact the adb reboot bootloader worked. I swap out one of my other devices and check things...they show up fine in fastboot....ok...so what's missing from this picture?
*update* solved by updating the ubuntu adb and fastboot binaries from here: https://github.com/simmac/minimal_adb_fastboot/tree/master/linux
*update2* bootloader unlocked, supersu flashed and verified. Much appreciated.

I ran the bootloader unlock and it appeared to work. Now it keeps booting back into the bootloader. I can't seem to get it to boot normal. Suggestions?
Nevermind, I didn't realize that I needed to run restore.bat while still in the bootloader. It is booting now! I was able to follow your guide and it is now rooted.
Regarding the marshmallow zip you include. I have a couple questions.
- For the modified stock version that will keep the recovery do I just need to flash it from recovery?
- Do I need to unroot before flashing this modified stock marshmallow?
Thanks!

slgooding said:
I ran the bootloader unlock and it appeared to work. Now it keeps booting back into the bootloader. I can't seem to get it to boot normal. Suggestions?
Nevermind, I didn't realize that I needed to run restore.bat while still in the bootloader. It is booting now! I was able to follow your guide and it is now rooted.
Regarding the marshmallow zip you include. I have a couple questions.
- For the modified stock version that will keep the recovery do I just need to flash it from recovery?
- Do I need to unroot before flashing this modified stock marshmallow?
Thanks!
Click to expand...
Click to collapse
Happy to read you got it booting, by the time I got to answer you seemed to git it figured out.
Regarding the zip, yes flash from recovery and you don't need to unroot before, but you will need to root after flashing.
However I do suggest you make a backup before flashing jsut in case....

Emil Borconi said:
Happy to read you got it booting, by the time I got to answer you seemed to git it figured out.
Regarding the zip, yes flash from recovery and you don't need to unroot before, but you will need to root after flashing.
However I do suggest you make a backup before flashing jsut in case....
Click to expand...
Click to collapse
I'm assuming the file is just for folks who are on lollipop who want to upgrade? Didn't see any need to flash it since already on 6.0.1 and have it rooted...unless I'm missing something again.

I read this after I went to 6.0.1 from Asus's manual download and update process. I can't get ADB to connect in the OS (developer mode never displays, even though it tells me I'm a developer after doing kernel ver. button process). I tried to get adb devices -l in fastboot and recovery, and it wont discover it. I've tried multiple windows drivers (including the one that worked when I flashed the firmware the first time) to no avail. Any ideas?

Irishman2020 said:
I read this after I went to 6.0.1 from Asus's manual download and update process. I can't get ADB to connect in the OS (developer mode never displays, even though it tells me I'm a developer after doing kernel ver. button process). I tried to get adb devices -l in fastboot and recovery, and it wont discover it. I've tried multiple windows drivers (including the one that worked when I flashed the firmware the first time) to no avail. Any ideas?
Click to expand...
Click to collapse
If windows doesn't see the phone when in recovery there is something wrong, this can be:
1) Wrong driver
2) Damaged USB cable
3) Damaged USB port.
When you are in recovery you should see the phone with adbm if you are in fastboot you should see the phone with:
Code:
fastboot devices
If nothing works you have the nuclear option.
Manually download the original firmware from Asus website: https://www.asus.com/support/Download/39/1/0/26/BXbNqJplzZiLmk6G/32/
copy the zip to an Sd card.
1) Now Turn Off your phone and boot into recovery mode by pressing Power+Volume UP.
2) Now in recovery mode choose to apply update from sdcard.
3) Now select the zip file.
4) Now wait until the process complete and then Reboot the phone.
5) Done!

famewolf said:
I'm assuming the file is just for folks who are on lollipop who want to upgrade? Didn't see any need to flash it since already on 6.0.1 and have it rooted...unless I'm missing something again.
Click to expand...
Click to collapse
More or less true, but somehow I was on a 6.0.1 version which is now gone from the firmware list of Zenfone, meaning I have updated from 6.0.1 to 6.0.1
Again now I see there is a new firmware released yesterday if I have the time I will patch that system image as well so it can be upgraded with TWRP.

famewolf said:
I'm assuming the file is just for folks who are on lollipop who want to upgrade? Didn't see any need to flash it since already on 6.0.1 and have it rooted...unless I'm missing something again.
Click to expand...
Click to collapse
Just for you I've just uploaded the 4.21.40.197 release as well... so now there is a point of the TWRP rom's

Emil Borconi said:
Just for you I've just uploaded the 4.21.40.197 release as well... so now there is a point of the TWRP rom's
Click to expand...
Click to collapse
Typical....now you've given me work I need to do on the phone. ;P
Appreciate your work!
Out of curiosity have you tried xposed?

famewolf said:
Typical....now you've given me work I need to do on the phone. ;P
Appreciate your work!
Out of curiosity have you tried xposed?
Click to expand...
Click to collapse
Yes and it works. I tried a few modules, but generally speaking I'm not a big xposed user myself. Nify doesn't work to well because of all the asus software on it and I wasn't able to get google assistant either. Android audo mod worked perfectly, so yeah generally speaking xposed work's

Emil Borconi said:
Yes and it works. I tried a few modules, but generally speaking I'm not a big xposed user myself. Nify doesn't work to well because of all the asus software on it and I wasn't able to get google assistant either. Android audo mod worked perfectly, so yeah generally speaking xposed work's
Click to expand...
Click to collapse
Thanks...that answers all my questions except for figuring out what's safe to disable. I put a post in q&a but no replies..the zoom appears to have a very small group on xda. I'll figure it out eventually.

famewolf said:
Thanks...that answers all my questions except for figuring out what's safe to disable. I put a post in q&a but no replies..the zoom appears to have a very small group on xda. I'll figure it out eventually.
Click to expand...
Click to collapse
Actually most if them can be. Here is a print screen of the ones I have disabled on my phone hover I have a zenpad z380c which I use as my car dashboard and on that one o have disabled almost of all of the apps, except zenhome, audio manager and the file manager.
Yes I was surprised to find out that there is almost no zoom community.

Emil Borconi said:
Actually most if them can be. Here is a print screen of the ones I have disabled on my phone hover I have a zenpad z380c which I use as my car dashboard and on that one o have disabled almost of all of the apps, except zenhome, audio manager and the file manager.
Yes I was surprised to find out that there is almost no zoom community.
Click to expand...
Click to collapse
I'm actually enjoying mobile managers auto startup managing...it's done a good job of keeping 10000 things from running at startup that don't need to although "Startup Manager" would do a similar job for free. I'm liking the zenui launcher and calling screen so don't want to break anything related to that...the phone's been performing exceptionally well for days on end with no required reboots. Been very impressed. Previously been fighting with a T-mobile V10 and an Alcatel Idol 3...the v10 had spontaneous reboots...the idol had a stock rom with a bunch of lag in it....tiny to nothing development on both of those.
What about Zentalk, ZenChoice, PhotoCollage, MyAsus Service center, Clean Master, Audiowizard and Bug Reporter?

famewolf said:
I'm actually enjoying mobile managers auto startup managing...it's done a good job of keeping 10000 things from running at startup that don't need to although "Startup Manager" would do a similar job for free. I'm liking the zenui launcher and calling screen so don't want to break anything related to that...the phone's been performing exceptionally well for days on end with no required reboots. Been very impressed. Previously been fighting with a T-mobile V10 and an Alcatel Idol 3...the v10 had spontaneous reboots...the idol had a stock rom with a bunch of lag in it....tiny to nothing development on both of those.
Click to expand...
Click to collapse
I use tasker for that, but yes I agree as a whole is not bad, this is my 4rd Asus product (Zenfone 4, Zenfone 2, Zoom and Zenpad) and overall I'm quite impressed with how they perform, just the support from Asus isn't really the top of the cream... they released MM when other were releasing N... so yeah a bit of sour taste, otherwise happy. And the camera, I think it's brilliant, not the best on the market, but the optical zoom is cool, as well as the camera app which allows you to do some nice manual shooting.

Emil Borconi said:
I use tasker for that, but yes I agree as a whole is not bad, this is my 4rd Asus product (Zenfone 4, Zenfone 2, Zoom and Zenpad) and overall I'm quite impressed with how they perform, just the support from Asus isn't really the top of the cream... they released MM when other were releasing N... so yeah a bit of sour taste, otherwise happy. And the camera, I think it's brilliant, not the best on the market, but the optical zoom is cool, as well as the camera app which allows you to do some nice manual shooting.
Click to expand...
Click to collapse
I listed a few apps in my previous post I wondered if you had looked at..it was a last minute addition so you may have missed it. I own tasker...I'm unaware of using it to stop tasks from running at bootup although I have used it to MAKE some apps run after "Boot Completed".

famewolf said:
I listed a few apps in my previous post I wondered if you had looked at..it was a last minute addition so you may have missed it. I own tasker...I'm unaware of using it to stop tasks from running at bootup although I have used it to MAKE some apps run after "Boot Completed".
Click to expand...
Click to collapse
Generally tasker can be used for almost anything.... but I'm doing most of the thing with root+shell scripts, but yes nothing wrong with the app provided by Asus. I think everybody uses the setup/software he/she is most comfortable using... and there is no right or wrong.... that's until you are NOT and iCrap user, because that is the ultimate WRONG! )

Emil Borconi said:
Generally tasker can be used for almost anything.... but I'm doing most of the thing with root+shell scripts, but yes nothing wrong with the app provided by Asus. I think everybody uses the setup/software he/she is most comfortable using... and there is no right or wrong.... that's until you are NOT and iCrap user, because that is the ultimate WRONG! )
Click to expand...
Click to collapse
Well from the lack of posts it appears you and I ARE the zenfone zoom community. Any idea where the system updates get stored after downloading? I thought in /cache based on regular zenfone posts but was unable to see it. I've got one available but it has to be modified for twrp compatibility as well as unrooting temporarily.

[ROM] [STOCK] Official manual updates on the M2 tablet M2-A01L

Official manual updates for
the M2 tablet M2-A01L​
- Disclaimer
Well, whatever you do with this guide is all up to you and in your own responsibility. You
should have basic knowledge about Android. Remember, I have only one M2-A01L and this
guide worked this way on my device. There is no guarantee, it will work on your M2-A01L,
too.
- Issue
Well, some guys just do not get an automated update in their EMUI apps, still hanging dry
on B006 or B007.
- Solution
So, you can manually update the tablet with one of the original update files, which I saved at
my two automatic updates.
- Guide
1. First, it is important to know, if you have installed a different recovery and/or any root stuff.
If no, go to 3.!
2. So, with a different recovery like TWRP and not the official Huawei one, you cannot get the
official updates. Also, I absolutely do not recommend Kingroot. You may rather use Magisk for
systemless root rights - way less problems. For a guide I recommend my other thread, but you
can do it your own way:
https://forum.xda-developers.com/mediapad-m2/how-to/guide-official-updates-m2-tablet-root-t3589363
Basically, you cannot update with a non-original recovery like TWRP.
3. If you are on B006, you should first update to B007 and afterwards to B010. I did it that way.
I would not recommend going directly to B010. If you are on B007 you can update to B010.
You might update to B010, if you are on B009, but I never tested this with this file.
4. So, we have two ways to go - you have to decide one:
a) You have to download the file (see below), rename it to "update.zip" and place it into the
directory "HwOUC" on your tablet. That is the very official way, just like it usually goes.
OR
b) You have to download the file (see below), unpack the included "update.app" and place it
into the directory "dload" on your tablet. That should be working, too, BUT I never checked this
and I only read somewhere on the internet about this method. I definitely do NOT recommend
it. The first method is the easier one.
5. Well, now you have to reboot your tablet and it will reboot directly into the recovery, because
it "sees" the update in the update directory ... et voila, you are getting your awaited update.
6. After the update is done and your device has rebooted, you can go back to your own recovery
like I did with this guide:
https://forum.xda-developers.com/mediapad-m2/how-to/guide-unlock-bootlader-twrp-root-huawei-t3322340
- Root:
If you want to have root rights, I strongly recommend flashing Magisk within TWRP, because it is
just a nice and more modern approach to having root. It works very fine on my M2 10 tablet. The
link for the files and guide is here:
https://goo.gl/UXYk4d
It is very easy. You just flash Magisk 12 in TWRP and then install the Magisk Manager app from the
Play store.
- Files for M2-A01L:
File-Upload:
B007 (from B006): M2-A01LV100R001C100B007.zip (European version)
B010 (from B007): OTA-M2-A01LV100R001C100B010.zip (European version)
DepositFiles:
B007 (from B006): M2-A01LV100R001C100B007.zip (European version)
B010 (from B007): OTA-M2-A01LV100R001C100B010.zip (European version)
Have fun with your updated tablet. ... and I am happy, if I could help you - any coffee/juice appreciated.
https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&hosted_button_id=ESYCULGT8ZU3A
...
..
.

*** save ***

Hi xsycox, I'm not able to update mine with your technique Mine is a M2-A01L with 006.
I load the file M2-A01LV100R001C100B007.zip in HwOUC and rename it to update.zip but restarting the tablet it is not installed automatically.
So the only way I've is to go in "manual update" of the tablet, select the file and it will reboot. But after 2% I got error.
I also tried the "dload" unpack method without results..
Help please..

Shocker580 said:
Hi xsycox, I'm not able to update mine with your technique Mine is a M2-A01L with 006.
I load the file M2-A01LV100R001C100B007.zip in HwOUC and rename it to update.zip but restarting the tablet it is not installed automatically.
So the only way I've is to go in "manual update" of the tablet, select the file and it will reboot. But after 2% I got error.
I also tried the "dload" unpack method without results..
Help please..
Click to expand...
Click to collapse
Same issue here. I'm on 007.

vahtmestar said:
Same issue here. I'm on 007.
Click to expand...
Click to collapse
Shocker580 said:
Hi xsycox, I'm not able to update mine with your technique Mine is a M2-A01L with 006.
I load the file M2-A01LV100R001C100B007.zip in HwOUC and rename it to update.zip but restarting the tablet it is not installed automatically.
So the only way I've is to go in "manual update" of the tablet, select the file and it will reboot. But after 2% I got error.
I also tried the "dload" unpack method without results..
Help please..
Click to expand...
Click to collapse
Had the same issue as well. Luckily I've been able to find a full Stock ROM of the latest version B010. It is designed for the 10.0 LTE Premium Edition of the M2 A01L. Shared it in a separate threat over here. Maybe it'll be of any help to you. Only problem when using it, is a full factory reset happening by doing so.

Hi,
just curious to know. I have Media pad M2-A01W (not A01L) which I bought in China (using in EU). I have currently M2-A01WV100R001C233B020 build number, which was an update from September 1, 2016. Is this A01L (EU/Western version) is different than A01W update? Is it possible to manually replace A01W to A01L ? I tried once but wasn't succeed.
Thanks in advance for your reply.
-KK

5m4r7ph0n36uru said:
Had the same issue as well. Luckily I've been able to find a full Stock ROM of the latest version B010. It is designed for the 10.0 LTE Premium Edition of the M2 A01L. Shared it in a separate threat over here. Maybe it'll be of any help to you. Only problem when using it, is a full factory reset happening by doing so.
Click to expand...
Click to collapse
You just saved my tablet. Thanks.

Hi, is it work for Dtab D-01H (Docomo), I dont find any rom for it

More custom roms for Mediapad M2 10 !
Hi,
I don't understand why we don't have more custom roms for the Mediapad M2 10....

[Guide]Rooting Wifi Version of Galaxy Tab s4 (T830)

So this is all thanks to @tomiga and developer of Magisk and Odin. I’m not even tryin to take any credit for any of this.
Also, it's a rough draft, let me know if things need to be changed or clarified, though I'm not intending to keep this updated in the future.
1. Booted up, checked for firmware updates, got none, stuck on Jun security patch with firmware version T830XXU1ARGH/T830OXM1ARGH/
2. Settings>about tablet>tap on build number to get into developer settings.
3. Check OEM unlock, tablet resets and erases everything
4. Installed Samsung Windows USB Drivers from here: https://www.samsung.com/us/support/downloads/ on Windows 10 pc
5. Booted up, installed Magisk Manager v 5.9.1 from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
6. Downloaded boot image modified with Magisk 16.7 from here: https://forum.xda-developers.com/showpost.php?p=77439510&postcount=35
7. Installed Odin 3 from here: https://forum.xda-developers.com/galaxy-tab-s4/how-to/sm-t830-t830xxu1arh1-t3831918
8. Started Odin, checked AP and selected location of the BootImage from above as location of AP
9. Connected tab to PC, opened command prompt, adb reboot bootloader
10. Loading screen comes up on TAB, Odin says “Added!” to mean it recognizes the Tab
11. Hit “start” in Odin
12. After it’s done, Tab says something about a problem booting, Click “reset” on, tablet gets erased again
13. Booted up finally, on boot it says something about warranty and kernel and a bit being triggered
14. Connect tab to PC, command prompt, adb shell, “pm uninstall -k --user 0 com.samsung.android.securitylogagent”
15. Open Magisk Manager, it says tablet isn’t rooted.
16. ADB reboot bootloader, Repeat the flashing in Odin. Just don’t close Odin so it’s all ready to go, hit start
17. Tab rebooted fine
18. Open Magisk, Magisk says it’s rooted but want’s to install 17.1 which is the current stable version of Magisk.
19. Agree to install the Stable Magisk (17.1), choose direct install as it is “recommended”.
20. Reboot.
21. ???
22. Profit?

mistermojorizin said:
So this is all thanks to @tomiga and developer of Magisk and Odin. I’m not even tryin to take any credit for any of this.
Also, it's a rough draft, let me know if things need to be changed or clarified, though I'm not intending to keep this updated in the future.
1. Booted up, checked for firmware updates, got none, stuck on Jun security patch with firmware version T830XXU1ARGH/T830OXM1ARGH/
2. Settings>about tablet>tap on build number to get into developer settings.
3. Check OEM unlock, tablet resets and erases everything
4. Installed Samsung Windows USB Drivers from here: https://www.samsung.com/us/support/downloads/ on Windows 10 pc
5. Booted up, installed Magisk Manager v 5.9.1 from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
6. Downloaded boot image modified with Magisk 16.7 from here: https://forum.xda-developers.com/showpost.php?p=77439510&postcount=35
7. Installed Odin 3 from here: https://forum.xda-developers.com/galaxy-tab-s4/how-to/sm-t830-t830xxu1arh1-t3831918
8. Started Odin, checked AP and selected location of the BootImage from above as location of AP
9. Connected tab to PC, opened command prompt, adb reboot bootloader
10. Loading screen comes up on TAB, Odin says “Added!” to mean it recognizes the Tab
11. Hit “start” in Odin
12. After it’s done, Tab says something about a problem booting, Click “reset” on, tablet gets erased again
13. Booted up finally, on boot it says something about warranty and kernel and a bit being triggered
14. Connect tab to PC, command prompt, adb shell, “pm uninstall -k --user 0 com.samsung.android.securitylogagent”
15. Open Magisk Manager, it says tablet isn’t rooted.
16. ADB reboot bootloader, Repeat the flashing in Odin. Just don’t close Odin so it’s all ready to go, hit start
17. Tab rebooted fine
18. Open Magisk, Magisk says it’s rooted but want’s to install 17.1 which is the current stable version of Magisk.
19. Agree to install the Stable Magisk (17.1), choose direct install as it is “recommended”.
20. Reboot.
21. ???
22. Profit?
Click to expand...
Click to collapse
What directory is fastboot and ADB in????

ScottBroker said:
What directory is fastboot and ADB in????
Click to expand...
Click to collapse
Honestly, I don't think the directory should matter as long as adb and fastboot are in your environmental variables. And if they aren't, then just open a terminal in the directory you DO have adb and fastboot in....and run the commands from there.
https://www.xda-developers.com/15-s...ng-fast-adb-fastboot-and-driver-installation/

ScottBroker said:
What directory is fastboot and ADB in????
Click to expand...
Click to collapse
I already had adb/fastboot setup on my PC for my other phones, but didn't have the Samsung drivers. I installed the android SDK at some point to get the adb and fastboot drivers. Note, that unlike all of my other android devices, the tab S4 didn't respond to fastboot commands (for example, "fastboot devices" command in bootloader/download mode didn't return anything, which was unexpected). But Odin recognized it in that mode. So this doesn't rely on using any fastboot commands, just ADB.

Thanks for making a more user-friendly guide. I was considering doing so myself but got caught up with a lot of other stuff, so much appreciated.

mistermojorizin said:
1. Booted up, checked for firmware updates, got none, stuck on Jun security patch with firmware version T830XXU1ARGH/T830OXM1ARGH/
2. Settings>about tablet>tap on build number to get into developer settings.
3. Check OEM unlock, tablet resets and erases everything
4. Installed Samsung Windows USB Drivers from here: https://www.samsung.com/us/support/downloads/ on Windows 10 pc
5. Booted up, installed Magisk Manager v 5.9.1 from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
6. Downloaded boot image modified with Magisk 16.7 from here: https://forum.xda-developers.com/showpost.php?p=77439510&postcount=35
7. Installed Odin 3 from here: https://forum.xda-developers.com/galaxy-tab-s4/how-to/sm-t830-t830xxu1arh1-t3831918
8. Started Odin, checked AP and selected location of the BootImage from above as location of AP
9. Connected tab to PC, opened command prompt, adb reboot bootloader
10. Loading screen comes up on TAB, Odin says “Added!” to mean it recognizes the Tab
11. Hit “start” in Odin
12. After it’s done, Tab says something about a problem booting, Click “reset” on, tablet gets erased again
13. Booted up finally, on boot it says something about warranty and kernel and a bit being triggered
14. Connect tab to PC, command prompt, adb shell, “pm uninstall -k --user 0 com.samsung.android.securitylogagent”
15. Open Magisk Manager, it says tablet isn’t rooted.
16. ADB reboot bootloader, Repeat the flashing in Odin. Just don’t close Odin so it’s all ready to go, hit start
17. Tab rebooted fine
18. Open Magisk, Magisk says it’s rooted but want’s to install 17.1 which is the current stable version of Magisk.
19. Agree to install the Stable Magisk (17.1), choose direct install as it is “recommended”.
20. Reboot.
21. ???
22. Profit?
Click to expand...
Click to collapse
It should be possible to avoid the second system reset in step 12 by flashing a modified system.img with the offending package(s) removed.

tomiga said:
Thanks for making a more user-friendly guide. I was considering doing so myself but got caught up with a lot of other stuff, so much appreciated.
Click to expand...
Click to collapse
I was able to root my Tab S4, but now my camera does not work. I tried installin xposed, and it didnt work, so I did a factory data reset and now when I set it up it was still rooted, but the camera does not work. Any suggestions before I flash the stock firmware back to it?????

ScottBroker said:
I was able to root my Tab S4, but now my camera does not work. I tried installin xposed, and it didnt work, so I did a factory data reset and now when I set it up it was still rooted, but the camera does not work. Any suggestions before I flash the stock firmware back to it?????
Click to expand...
Click to collapse
It sounds as if the kernel you flashed isn't compatible with the vendor.img of the firmware that you're on.
The rooting procedure described here uses a modified boot.img that may now be too old for the updated firmware that a lot of us have since received on our devices.
If that's the issue, you will either need to downgrade your firmware to match the one your kernel was built against (flashing vendor.img from that version is probably sufficient), or upgrade your kernel to match the firmware you're running now. That will entail modifying the new boot image for root in the same way as the one you downloaded as part of the rooting process.
This is why, in spite of feeling tempted, I'm personally holding off on rooting this device until I or someone else gets TWRP working on it.

ianmacd said:
It sounds as if the kernel you flashed isn't compatible with the vendor.img of the firmware that you're on.
The rooting procedure described here uses a modified boot.img that may now be too old for the updated firmware that a lot of us have since received on our devices.
If that's the issue, you will either need to downgrade your firmware to match the one your kernel was built against (flashing vendor.img from that version is probably sufficient), or upgrade your kernel to match the firmware you're running now. That will entail modifying the new boot image for root in the same way as the one you downloaded as part of the rooting process.
This is why, in spite of feeling tempted, I'm personally holding off on rooting this device until I or someone else gets TWRP working on it.
Click to expand...
Click to collapse
I just reflashed the stock image and I am back to normal

ScottBroker said:
I just reflashed the stock image and I am back to normal
Click to expand...
Click to collapse
Which will also align your camera firmware with your kernel again, but now you don't have root, right?

ianmacd said:
Which will also align your camera firmware with your kernel again, but now you don't have root, right?
Click to expand...
Click to collapse
No, and I have the wifi version

ScottBroker said:
No, and I have the wifi version
Click to expand...
Click to collapse
I have both root and camera working fine. Only difference I can tell from your software version is under Build Number mine has t830XXU1ARGH. Have you disabled any apps by chance? On one of my phones camera would crash if i disabled NFC service.

mistermojorizin said:
I have both root and camera working fine. Only difference I can tell from your software version is under Build Number mine has t830XXU1ARGH. Have you disabled any apps by chance? On one of my phones camera would crash if i disabled NFC service.
Click to expand...
Click to collapse
His problem was almost certainly due to his having ARH5 firmware on the device (specifically the vendor.img component) but an ARH1 kernel. Such mismatches usually present themselves in the form of a non-functional camera.
After upgrading the firmware past ARH5, the new boot image should be rooted, rather than flashing the older one given in the rooting instructions of this thread.
Please also note that @ashyx has started work on TWRP and even released an initial test build for the T820. I intend to give that a try this afternoon when I get home.
Sent from my SM-G965F using XDA Labs

ianmacd said:
His problem was almost certainly due to his having ARH5 firmware on the device (specifically the vendor.img component) but an ARH1 kernel. Such mismatches usually present themselves in the form of a non-functional camera.
After upgrading the firmware past ARH5, the new boot image should be rooted, rather than flashing the older one given in the rooting instructions of this thread.
Please also note that @ashyx has started work on TWRP and even released an initial test build for the T820. I intend to give that a try this afternoon when I get home.
Sent from my SM-G965F using XDA Labs
Click to expand...
Click to collapse
Do you have a rooted image??? It was nice to be rooted for a while. I'm pretty sure flashfire would work until twrp is available.....

ScottBroker said:
Do you have a rooted image??? It was nice to be rooted for a while. I'm pretty sure flashfire would work until twrp is available.....
Click to expand...
Click to collapse
flashfire won't open. i went through something like this on my fire hd 10, had to install an xposed module to trick flashfire into thinking we're back in an older time and install a really old version of flashfire. Otherwise, the newer version of flashfire would just close/won't open.

hope this all settles down to a working version soon

ScottBroker said:
Do you have a rooted image??? It was nice to be rooted for a while. I'm pretty sure flashfire would work until twrp is available.....
Click to expand...
Click to collapse
TWRP is on the way. @ashyx is working on it. This thread is tracking the progress.

ianmacd said:
TWRP is on the way. @ashyx is working on it. This thread is tracking the progress.
Click to expand...
Click to collapse
Exciting stuff ?

Will this work for LTE? I don't see the option to oem unlock on my Verizon version. Does that mean locked bootloader?

machx1111 said:
Will this work for LTE? I don't see the option to oem unlock on my Verizon version. Does that mean locked bootloader?
Click to expand...
Click to collapse
Most likely. Verizon normally make them unlockable

Bootloader auto locks, can install TWRP but asks for password.

Hello,
New to the forums, I've come across a Nexus 5X that has got me stumped. I haven't had to create and post on xda-developers before because I could always find a solution. But this phone...I've even got the book (xda-developers Android Hackers Toolkit)
So I needed a Nexus 5 for a project. I went to ebay and ordered one from China/Hong Kong.
I've got TWRP installed but the device asks for a password. I've tried different versions of twrp. in the more recent version TWRP asks for a password. In earlier versions it just runs a script and reboots.
I cannot yet post links to images, being a new member.
I'm not sure what I'm doing wrong. I can run fastboot oem unlock and unlock the device. Then, if I try and flash a stock good android Nexus ROM the bootloader locks itself and reboots.
Is there something obvious I am missing? I just want to wipe the phone and install a stock nexus ROM. It's like the people who sold it have it loaded with something the prevents the phone from being wiped/modified.
I've never come across an Nexus phone that I couldn't wipe. I don't care about the data on the phone. I cannot securely use a phone if I cannot wipe it first. I can get to the bootloader and TWRP recovery. But there is no
point with TWRP because when it prompts for a password and I click cancel it runs a script, reboots and then locks the bootloader again.
Thanks

internetdenizen said:
Hello,
New to the forums, I've come across a Nexus 5X that has got me stumped. I haven't had to create and post on xda-developers before because I could always find a solution. But this phone...I've even got the book (xda-developers Android Hackers Toolkit)
So I needed a Nexus 5 for a project. I went to ebay and ordered one from China/Hong Kong.
I've got TWRP installed but the device asks for a password. I've tried different versions of twrp. in the more recent version TWRP asks for a password. In earlier versions it just runs a script and reboots.
I cannot yet post links to images, being a new member.
I'm not sure what I'm doing wrong. I can run fastboot oem unlock and unlock the device. Then, if I try and flash a stock good android Nexus ROM the bootloader locks itself and reboots.
Is there something obvious I am missing? I just want to wipe the phone and install a stock nexus ROM. It's like the people who sold it have it loaded with something the prevents the phone from being wiped/modified.
I've never come across an Nexus phone that I couldn't wipe. I don't care about the data on the phone. I cannot securely use a phone if I cannot wipe it first. I can get to the bootloader and TWRP recovery. But there is no
point with TWRP because when it prompts for a password and I click cancel it runs a script, reboots and then locks the bootloader again.
Thanks
Click to expand...
Click to collapse
"bootloop_after_lg_replaced_mainboard_bootloader reddit"
google it

https://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
This is the droids guide you are looking for...
Hope this helps anyone else who lands here with the same issue.

First sorry my bad english. I guess you took wrong way.
I suggested safety and easy solution. TWRP needs password due to encrypted data partition.
If you can format userdata,TWRP require no password and you can flash any Rom.
I wish you success with your way.

Thank you for your reply.
I am following the instructions here; https://forum.xda-developers.com/nexus-5x/help/req-help-to-unbrick-t3251740
I am stuck at the google logo. The bootloader is locked and I cannot unlock it because I cannot get the system up to enable developer tools and allow unlocking.
I don't really know what else to do.

The last resort
h ttps://ja.aliexpress.com/item/32846103543.html?spm=a2g0o.cart.0.0.74743c004Bny1g&mp=1
There is no longer anything that I can do for that.

I've managed to recover the phone using a combination for LGUP + tot files and sideloading an OTA from google.
I want to turn off encryption though... not sure how to do that..

Can you manage bootloader unlock?
O.K. following the tut of reddit thread and use fastboot tool this ver.
h ttps://www.reddit.com/r/nexus5x/comments/5hj0r0/bootloop_after_lg_replaced_mainboard_bootloader/
h ttps://androiddatahost.com/265a2

Hiroki.S said:
Can you manage bootloader unlock?
O.K. following the tut of reddit thread and use fastboot tool this ver.
h ttps://www.reddit.com/r/nexus5x/comments/5hj0r0/bootloop_after_lg_replaced_mainboard_bootloader/
h ttps://androiddatahost.com/265a2
Click to expand...
Click to collapse
I've tried to follow the reddit instructions. There are some missing files in the instructions where he links to xda-developers https://forum.xda-developers.com/nexus-5x/general/modified-boot-imgs-android-n-t3495169
The files are not available. Same goes with Magisk Compatible phh's SuperUser not being available
Thank you though for taking the time to try and help me

h ttps://forum.xda-developers.com/nexus-5x/general/modified-boot-imgs-android-n-t3495169/page17

Hiroki.S said:
h ttps://forum.xda-developers.com/nexus-5x/general/modified-boot-imgs-android-n-t3495169/page17
Click to expand...
Click to collapse
I have that boot img and tried to flash it but nothing happens.. The phh-superuser-magisk is marked as obsolete here -> https://forum.xda-developers.com/apps/magisk/magisk-phh-s-superuser-android-pay-t3435921
thanks mate

Majisk latest
Probably no problem

Hi mate,
I managed to flash TWRP. I booted into TWRP and selected to keep the system read only. I then used 'adb push' to push Magisk to the SDCARD and successfully flashed Magisk. I can boot back into the system and I have root access. Where do I go from here? I would like to install a custom ROM
thanks mate.

OK.
So. I installed Magisk successfully. I setup the phone and rebooted into recovery. It no longer asks for a password. I was able to push a custom ROM to the SDCARD and flash using TWRP.. I have learned alot about android and the 5X in just a couple of days.
Thanks

internetdenizen said:
OK.
So. I installed Magisk successfully. I setup the phone and rebooted into recovery. It no longer asks for a password. I was able to push a custom ROM to the SDCARD and flash using TWRP.. I have learned alot about android and the 5X in just a couple of days.
Thanks
Click to expand...
Click to collapse
Everyone goes through the same thing.
Cheers.