Hi all! I build LineageOS 13 for LG K10 MTK. But I can not check on my phone . Who will be able to test? Need wipe data and install LineageOS with TWRP. MOD EDIT
Keep it up!
If I install this rom on my phone and it will not work Can I install firmware rom with lg up, but I need dll file(from .kdz file) to replace in lg up folder. I don't want to have bricked device. (Sorry for bad english)
Singular777 said:
Hi all! I build LineageOS 13 for LG K10 MTK. But I can not check on my phone . Who will be able to test? Need wipe data and install LineageOS with TWRP.
Click to expand...
Click to collapse
I'm glad to see there is development on K10 but why the heck would you make this when on mtk devices can't be flashed anything not even recovery because of "check function" on Qualcomm it was on aboot partition on Mediatek it's probably on lk. Please announce that before someone screw their phone for no reason.
Also if you make a rom thread make it to look like something like pvineth Lineage thread, add some info and device tree and such things with this info it could be tampered bomb inside..
Why u can't?
---------- Post added at 03:43 AM ---------- Previous post was at 03:42 AM ----------
Singular777 said:
Hi all! I build LineageOS 13 for LG K10 MTK. But I can not check on my phone . Who will be able to test? Need wipe data and install LineageOS with TWRP. Download
Click to expand...
Click to collapse
Why u can't test?
it's not working :/
i booted in TWRP then wiped data, installed LineageOS and Gapps and rebooted.
and phone booted to lg logo and showed message device is corrupt and powered off
Singular777 said:
Hi all! I build LineageOS 13 for LG K10 MTK. But I can not check on my phone . Who will be able to test? Need wipe data and install LineageOS with TWRP. MOD EDIT
Click to expand...
Click to collapse
Hello,
Kindly check, confirm if this is useful and safe for other users. Please mention what are the RISKS AND REPERCUSSIONS if the flash is not successful.
It is most important
Thanks
Singular777 said:
Hi all! I build LineageOS 13 for LG K10 MTK. But I can not check on my phone . Who will be able to test? Need wipe data and install LineageOS with TWRP. MOD EDIT
Click to expand...
Click to collapse
I believe that lg's security system from the 2017 febr. update prevents flashing/loading any modified boot image. So you need your stock firmware to be older than 2017 febr. to flash this OS (if i'm not mistaken it only flashes the boot, the recovery and the system partition). On the other hand you cannot modify the recovery partition at all, no matter the security patch date so before flashing this mod you need to backup your recovery partition and restore it after installing this zip - otherwise you will naturaly get shut off after the device corrupt message.
If you could build it for the k8 (k350n) i could give it a try. Please confirm that it only flashes the boot, recovery and system partition and it's not messing with lk, laf and preloader - so we can recover with lg up if anything goes wrong.
Thanks anyways!
PS. do you think its enough if i just exchange the "boot.img-kernel" file in the boot image in you're zip to mine from k8? all other necessery files looks the same (like fstab and init files). I'm also not sure if i should change the .m253. files to .mm1v. files (like ueventd.m253.rc -> ueventd.mm1v.rc and init.m253.rc -> init.mm1v.rc, etc... all files that are m253 in your boot image are mm1v in my boot image but their contents are the same). So should i exchange them or leave them untouched?
So to test it i must downgrade ROM to earlier version than 2017 feb?
a_lewicki said:
So to test it i must downgrade ROM to earlier version than 2017 feb?
Click to expand...
Click to collapse
Exactly. Also i believe that it has to be ported (not built) for each type (or some) of the k10 variants (https://forum.xda-developers.com/lg-k10/development/stock-versions-model-lg-k10-t3457319) since there might be some difference in the hardware.
Another thing is the recovery partition. The zip itself does not contain any recovery related parts. However the OS might check the recovery during boot up and it might change the recovery partition which means it will fail to boot up again. But i didn't find anything in the zip that would change the most important partitions like lk, bootloader and laf so i'm 99% sure that we can use lg up or lg brigde to recover if we get soft bricked.
Singular777 said:
Hi all! I build LineageOS 13 for LG K10 MTK. But I can not check on my phone . Who will be able to test? Need wipe data and install LineageOS with TWRP. MOD EDIT
Click to expand...
Click to collapse
I can confirm that it's not hard bricking the device so the stock firmware can be easily reflashed by lg up (i tested three times). However i tried to port it to my k8 but i didn't succeed (never booted up).
So would you be so kind as building one for the k8? More specifically k8 - k350n. I believe you need the source (i guess it's LGK350N):
http://opensource.lge.com/osSch/list?types=ALL&search=k350n
and maybe device tree (if it is really the device tree):
https://forum.xda-developers.com/lg-k8/development/device-tree-device-tree-lg-k350xxx-t3549783
the firmwares you can find here: https://lg-firmwares.com/lg-k350n-firmwares/
Let me know if you need anything else and thanks in advance.
Naturally i don't expect you to make it, i understand if you don't. It would be just nice if you did and you'd probably make many k8 users happy...
gottlasz said:
I can confirm that it's not hard bricking the device so the stock firmware can be easily reflashed by lg up (i tested three times). However i tried to port it to my k8 but i didn't succeed (never booted up).
So would you be so kind as building one for the k8? More specifically k8 - k350n. I believe you need the source (i guess it's LGK350N):
http://opensource.lge.com/osSch/list?types=ALL&search=k350n
and maybe device tree (if it is really the device tree):
https://forum.xda-developers.com/lg-k8/development/device-tree-device-tree-lg-k350xxx-t3549783
the firmwares you can find here: https://lg-firmwares.com/lg-k350n-firmwares/
Let me know if you need anything else and thanks in advance.
Naturally i don't expect you to make it, i understand if you don't. It would be just nice if you did and you'd probably make many k8 users happy...
Click to expand...
Click to collapse
Hi, I'll try to collect the firmware for K8
Singular777 said:
Hi, I'll try to collect the firmware for K8
Click to expand...
Click to collapse
Thank you for your time and efforts! Let me know if i can help!
This'll not work as long as bootloader acts as if it's not unlocked even though we applied the steps to unlock it.
a_lewicki said:
it's not working :/
i booted in TWRP then wiped data, installed LineageOS and Gapps and rebooted.
and phone booted to lg logo and showed message device is corrupt and powered off
Click to expand...
Click to collapse
And it's this what'll happen.
gottlasz said:
I believe that lg's security system from the 2017 febr. update prevents flashing/loading any modified boot image. So you need your stock firmware to be older than 2017 febr. to flash this OS (if i'm not mistaken it only flashes the boot, the recovery and the system partition). On the other hand you cannot modify the recovery partition at all, no matter the security patch date so before flashing this mod you need to backup your recovery partition and restore it after installing this zip - otherwise you will naturaly get shut off after the device corrupt message.
If you could build it for the k8 (k350n) i could give it a try. Please confirm that it only flashes the boot, recovery and system partition and it's not messing with lk, laf and preloader - so we can recover with lg up if anything goes wrong.
Thanks anyways!
PS. do you think its enough if i just exchange the "boot.img-kernel" file in the boot image in you're zip to mine from k8? all other necessery files looks the same (like fstab and init files). I'm also not sure if i should change the .m253. files to .mm1v. files (like ueventd.m253.rc -> ueventd.mm1v.rc and init.m253.rc -> init.mm1v.rc, etc... all files that are m253 in your boot image are mm1v in my boot image but their contents are the same). So should i exchange them or leave them untouched?
Click to expand...
Click to collapse
@berkantkz
Hey what do you think, is it possible that mtk versions of K10/K8 are using this ?
To your "p.s." It's not enough to replace kernel image and it's files if the rom is built from source it is built for different chipset (still mediatek tho but different) so it probably won't work at all.
Professor Woland said:
@berkantkz
Hey what do you think, is it possible that mtk versions of K10/K8 are using this ?
To your "p.s." It's not enough to replace kernel image and it's files if the rom is built from source it is built for different chipset (still mediatek tho but different) so it probably won't work at all.
Click to expand...
Click to collapse
I didn't understand what you've asked for on that link. It's only a guide.
Chipset model doesn't matter. If the configurations are OK to work on our model, there will be no problem or very little which aren't major.
We need to achieve unlocked bootloader. It can be unlocked by oem unlock command but it isn't actually. We have to manage to fix this. Then everything will be fine that our devices are MTK and easy to port rom stuff.
Sent from my LG K10 using XDA Labs
berkantkz said:
I didn't understand what you've asked for on that link. It's only a guide.
Chipset model doesn't matter. If the configurations are OK to work on our model, there will be no problem or very little which aren't major.
We need to achieve unlocked bootloader. It can be unlocked by oem unlock command but it isn't actually. We have to manage to fix this. Then everything will be fine that our devices are MTK and easy to port rom stuff.
Sent from my LG K10 using XDA Labs
Click to expand...
Click to collapse
Sorry for badly explained question. The link I posted talk about "verified boot" it's used to verify system, kernel and other images, so I thought maybe our phones use this too. But errors are different a little bit here take a look on this too
Professor Woland said:
Sorry for badly explained question. The link I posted talk about "verified boot" it's used to verify system, kernel and other images, so I thought maybe our phones use this too. But errors are different a little bit here take a look on this too
Click to expand...
Click to collapse
Both links regard to the same thing.
You're right, it's used on our devices that's why we can't flash anything over the stocks.
As usual, this warn should gone after bootloader unlock but as I told before, it doesn't act like unlocked, still thinks locked so the warn doesn't go away.
Sent from my LG K10 using XDA Labs
berkantkz said:
Both links regard to the same thing.
You're right, it's used on our devices that's why we can't flash anything over the stocks.
As usual, this warn should gone after bootloader unlock but as I told before, it doesn't act like unlocked, still thinks locked so the warn doesn't go away.
Sent from my LG K10 using XDA Labs
Click to expand...
Click to collapse
It's not the same link, but it doesn't matter, however if this is same thing as on our phones this should be able to help us https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
I don't think that bootloader stay locked but that there is some verification and if it fails device won't boot.
Professor Woland said:
It's not the same link, but it doesn't matter, however if this is same thing as on our phones this should be able to help us https://forum.xda-developers.com/an...signing-boot-images-android-verified-t3600606
I don't think that bootloader stay locked but that there is some verification and if it fails device won't boot.
Click to expand...
Click to collapse
Well, actually, I didn't mention links as the same. They're different links. I meant talks about the same thing. Well, this is not matter.
That thread you linked seems useful. I'll look on it. And your p.s. seems sensible.
Sent from my LG K10 using XDA Labs
Related
The stock ROM has a feature called verity, which ensures that the system partition is not modified. It uses a cryptographic signature to verify each sector on the partition. If any sector is modified, it is treated as corrupt.
In other words, any changes to the system partition will render it unbootable. This includes mounting /system read-write in recovery, even once.
In order to modify your system partition or recover from accidentally mounting your system partition read-write, you must download and flash the correct boot image using tuliptool.
You can find stock boot images with verity removed here:
US model, version 7.1.1 b12
md5=71428e4957763858f47bc9540e848d5e
US model, version 7.1.1 b14
md5=c6a67411e81f27d798eea035ddf4261e
EU model, version 7.1.1 b09
md5=ba210d332d3527b81f652dd0d2ce962e
i tried to see what would happen if i adb sideload supersu and my results came out that the went to zte screen and went into a bootloop didnt boot up but i have root priv in twrp....hmm. so i re-edl boot to after that i was able to boot back in to my android without root or supersu and twrp went back to normal aswell i was in the mood to test thankfully i was able to fix what ever had any issues
What would we need to provide for you to make one for v1.0.0B06?
I can make one for any firmware version. I just need the following:
* any relevant regional or model info.
* firmware version (including android version).
* the backup boot image, eg. from tuliptool.
parawizard said:
What would we need to provide for you to make one for v1.0.0B06?
Click to expand...
Click to collapse
So if I were to want to stay on the current ZTE rom (for now) would I need to flash this in order to root or currently root is only supported on the incomplete rom you are working on?
Depends how you root. I don't run stock so someone else should answer with details.
fallen00sniper said:
So if I were to want to stay on the current ZTE rom (for now) would I need to flash this in order to root or currently root is only supported on the incomplete rom you are working on?
Click to expand...
Click to collapse
tdm said:
Depends how you root. I don't run stock so someone else should answer with details.
Click to expand...
Click to collapse
i'm not a fan of the stock image, i do like to keep features which the stock seems devoid other than atmos which used to be hit or miss lol
i am sure someone out there likes the stock look, i used nova launcher and made things smaller, neater and tried to make it look a little better.
Done some experiments with SuperSU 2.82 (unsuccessfully, got bootloop).
In other words, any changes to the system partition will render it unbootable. This includes mounting /system read-write in recovery, even once.
Click to expand...
Click to collapse
And was able restore phone to work only with this EU boot.
Thanks, for making and publishing it!
Hi tdm, my 7 mini is USA hardware version but with European 6.0.1 firmware (build number ZTE B2017G V1.0.0B12). I tried to go back to USA Nougat firmware but unsuccessfully. Basically my phone was turned into P852A11 from P852A12. Do I need a new boot image with verity removed so that I can flash USA firmware? If I have to use Tuliptool, can you build a Windows32 version? Thanks in advance.
Sure thing, I'll make a firmware package. Please get me your partition checksums as in this post:
https://forum.xda-developers.com/showpost.php?p=74134639&postcount=52
I'll look into a win32 version of tuliptool.
bao_gg said:
Hi tdm, my 7 mini is USA hardware version but with European 6.0.1 firmware (build number ZTE B2017G V1.0.0B12). I tried to go back to USA Nougat firmware but unsuccessfully. Basically my phone was turned into P852A11 from P852A12. Do I need a new boot image with verity removed so that I can flash USA firmware? If I have to use Tuliptool, can you build a Windows32 version? Thanks in advance.
Click to expand...
Click to collapse
tdm said:
Sure thing, I'll make a firmware package. Please get me your partition checksums as in this post:
https://forum.xda-developers.com/showpost.php?p=74134639&postcount=52
I'll look into a win32 version of tuliptool.
Click to expand...
Click to collapse
Thank you tdm. You are awsome. I will provide you the checksums tomorrow.
Hey @tdm
Wanted to ask if you just removed the "verify" option in the fstab file to strip the dm verity checks? I might have read something like this before
Yes that's exactly it.
TheSSJ said:
Hey @tdm
Wanted to ask if you just removed the "verify" option in the fstab file to strip the dm verity checks? I might have read something like this before
Click to expand...
Click to collapse
I had finally gotten around to unlocking the bootloader and flashing TWRP.
Would flashing one of your custom ROMs without flashing the verity-free boot images affect anything?
I would suggest flashing the no verity boot just to avoid the headache
The stock boot images are only for running stock. Custom ROMs all include their own boot images.
JoeGatto said:
I had finally gotten around to unlocking the bootloader and flashing TWRP.
Would flashing one of your custom ROMs without flashing the verity-free boot images affect anything?
Click to expand...
Click to collapse
tdm said:
The stock boot images are only for running stock. Custom ROMs all include their own boot images.
Click to expand...
Click to collapse
Great. Looks like I'll be trying AOKP soon.
JoeGatto said:
Great. Looks like I'll be trying AOKP soon.
Click to expand...
Click to collapse
I've been running it for a couple of days and so far its great. No issues here
MrWhite0429 said:
I've been running it for a couple of days and so far its great. No issues here
Click to expand...
Click to collapse
You weren't kidding. Feels much faster than ZTE's ROM, and so refreshing as long as I've been looking at that MiFavor UI.
EDIT: Battery drain during standby.
tdm said:
Sure thing, I'll make a firmware package. Please get me your partition checksums as in this post:
https://forum.xda-developers.com/showpost.php?p=74134639&postcount=52
I'll look into a win32 version of tuliptool.
Click to expand...
Click to collapse
Hi tdm, my adb can not recognize the mini. And in order to get the partition info, I need to "boot into twrp" as the instruction says. But my recovery is STOCK not TWRP.
Anyway, if you can make a win32 Tuliptool, I can unlock the bootloader and flash the TWRP in. After that, I can flash any firmware that I want. Is it correct?
This is mainly a temporary repost of @rakomancha's TWRP announcement in a new thread. He is the maintainer of this TWRP but has not signed into XDA for a while. There is an updated TWRP that I wanted to share. When he comes back and creates his own thread, I will replace this post with a link to his.
-------------------------------------------------------------------------------------------------------------------------------------------------------
[TWRP][RECOVERY] Asus ZenPad 3S 10 Z500M
The next big step forward for Z500M development is here!
This is the first working custom TWRP recovery for the Asus ZenPad 3S 10 Z500M [P027], based from TWRP v3.2.1.
diplomatic and I had both been working on a port separately, and I offered to test his version. In a few hours we worked out a functional and install-friendly version.
Please NOTE that this is NOT an official TWRP. After this post, I'll be working on making the port official and update here.
ACKNOWLEDGEMENTS
This project, and my own motivation, would not have been possible without the incredible work and input of:
diplomatic, who has been instrumental in propelling Z500M development forward. He worked on the issue of perm root and discovered and revealed important intricacies of the Z500M restrictive bootloader. By the end of Dec 2017, he developed a method to unlock the Z500M bootloader based on his amazing work with the Z380M. With amartolos as his testing assistant, the Z500M bootloader unlocking tool was quickly developed and released Jan 5th 2018.
overkillZ, who in Sept 2017 introduced us all to rooting the Z500M
toineh, who did legwork of establishing temp root by manipulating system permissions & redirecting files through adb. Then he took the boot.img posted by LGiki, explained how to patch it through Magisk and posted the first patched boot image. He also served as a guiding voice on this front.
amartolos, who first attempted perm flashing the patched boot image of toineh's method and worked with diplomatic on the developments afterward, which led us to today. Also has served as a guiding voice.
LGiki, who was the first to post an extracted WW_27 boot image that got things rolling forward
DISCLAIMER
This image has only been successfully tested by me at this point.
Please exercise caution and care when attempting to flash anything to your device.
You are completely responsible for any possible issues or damages resultant from undertaking the following procedures.
That being said, this image and method should be safe.
REQUIREMENTS
ZenPad Z500M tablet, upgraded to Android N
Bootloader Unlocked, using Diplomatic's tool. Tablet should be showing Orange State during initial bootup.
Root with Magisk installed, Permanent Root preferable
BACK UP YOUR INTERNAL USER DATA, in case you need to factory reset
TWRP for Z500M recovery image file [twrp-3.2.1-0-z500m.img]
Knowledge of adb/fastboot and basic Linux shell
INSTRUCTIONS
Ensure REQUIREMENTS are all met
Ensure to RE-READ all instructions and understand them before starting
Reboot into fastboot mode
do fastboot boot twrp-3.2.1-0-z500m.img, TWRP should boot up in a few seconds. The theme should be blue.
In TWRP, go to BACKUP and back up Boot, Recovery, Data, System and SystemImage. Full backup took me about 10GB of space.
Copy the created TWRP Backup to your PC or an external location for safekeeping
Copy the TWRP twrp-3.2.1-0-z500m.img to tablet storage if not done already.
In TWRP, go to INSTALL, select Install Image and choose the twrp-3.2.1-0-z500m.img. Installation should only take a few seconds.
Unplug from USB and Reboot back into Recovery through the REBOOT menu
If installation went well, TWRP should boot up in a YELLOW theme. From my testing, I'm confident it is functionally the same.
RESOURCES
In this shared folder are
TWRP for Z500M recovery image file [twrp-3.2.1-0-z500m.img]
version 0.5 of Diplomatic's Unlock Tool
diplomatic's Z500M device source
hxxps://mega.nz/#F!SQlyDapC!XbbW0fftZWFfVx2lmL_JUQ [down, get the file below]
GOING FORWARD
I successfully tested replacement of Magisk with SuperSU. My steps taken were:
"Completely Uninstall" Magisk through the Magisk Manager
reboot directly into Recovery
INSTALL a previously downloaded official SuperSU zip file & REBOOT
I very much enjoyed this process of developing for uncharted regions of Android technologies and I owe all of that to the existence of this forum and the people in it. Next, I am reading up on porting a custom ROM, LineageOS looked very nice. I'll update here with significant progress until I get capability to start new forum threads. Thank you all and enjoy delicious functional TWRP custom recovery on your Z500M for the first time in history. Here's to looking forward to development exploding on this device.
-------------------------------------------------------------------------------------------------------------------------------------------------------
NEW DOWNLOAD
Updated February, 2018
Fixes the yellow color rendering in installed mode
twrp-3.2.1-0-z500m.zip
ADDITIONAL WARNING: At first boot of TWRP, it will ask you if you want to keep system read-only. Touch the Keep Read Only button at this screen and only mount system in read-only mode if you need (rarely needed). This is necessary because of dm-verity and is no different than most Android 6+ devices. Unless you have unlocked your bootloader and installed permanent root with dm-verity disabled, mounting the system partition in r/w mode will make changes to it and your tablet will instantly become unbootable.
This is great. Tempted to try this. thanks for the effort!
Thank you very much, I did this and also switched to SuperSU with no problems!
Hi guys,
I have followed all the steps until 8 but I'm stuck at the install : TWRP ask me what partition to flash
boot, recovery or system image
Which one to choose ? I think it's boot but I don't want to make any mistake
Thanks
ratus69 said:
Hi guys,
I have followed all the steps until 8 but I'm stuck at the install : TWRP ask me what partition to flash
boot, recovery or system image
Which one to choose ? I think it's boot but I don't want to make any mistake
Thanks
Click to expand...
Click to collapse
Well, recovery of course. ...because it's a custom recovery.
Hey guys I hope you can help me I had my Z500m partially rooted using the patched Magisk boot method and accidentally erased some stuff before I could permanently root it. Everything snowballed and all I have now is my firmware stored on pc I can get to fastboot mode but I have stock recovery still. can i flash my firmware through fastboot? I’ve been researching and it seems with Mediatek it’s different or at least not as simple. All searches keep coming up for Zenfone and I’m lost. Apologies if Im in wrong area.
diplomatic said:
Well, recovery of course. ...because it's a custom recovery.
Click to expand...
Click to collapse
Well I'm glad having nothing done until I get a reply from the Master himself
Thanks a lot diplomatic !
Sorry for stupid query. I have my Asus in Fastboot mode and connot reboot it. Have tried to hold power longer than 1 minute but nothing happen.
What I have to do
mirek54 said:
Sorry for stupid query. I have my Asus in Fastboot mode and connot reboot it. Have tried to hold power longer than 1 minute but nothing happen.
What I have to do
Click to expand...
Click to collapse
hold volume + and - together for 10s
There was a time that it was unthinkable development. I appreciate the time that cames after. Nice tutorial!
Nice work! I've got the Z500KL version of this tablet, so I'm hoping to port twrp to it at some point as well; if you have any tips or advice that might help it would be much appreciated! Although I'm fairly experienced with Linux this would be my first time working with Android, so I'm not sure if I'll succeed, but I thought I'd give it a shot anyway.
Hi, soleera,
To install TWRP, you must have some way to flash it and a bootloader that's either unlocked or doesn't care about unofficial images. I'm not sure that's possible in Z500KL. Look into that first. The Z500KL is about as much a version of this tablet as a Lenovo Tab4 is a version of this tablet. They are completely different platforms, just with a similar model name.
I've already managed to unlock the bootloader of my Z500KL and I've got fastboot working with it too, what I'm stuck on now is actually compiling twrp - I've already had a look at the guide here, but it's not very useful considering there are no .mk files for this model yet. If I had some idea about where to start I'd at least be able to start experimenting with the kernel / twrp source files and see where that leads me.
soleera said:
I've already managed to unlock the bootloader of my Z500KL and I've got fastboot working with it too, what I'm stuck on now is actually compiling twrp - I've already had a look at the guide here, but it's not very useful considering there are no .mk files for this model yet. If I had some idea about where to start I'd at least be able to start experimenting with the kernel / twrp source files and see where that leads me.
Click to expand...
Click to collapse
Oh, cool. How did you unlock it, btw? I know Asus makes you jump through hoops or doesn't allow unlocking altogether...
In case there is no device tree source (almost always), you start with an existing source tree for a phone with a similar platform. Then you adapt it for your device. Usually it's just a few changes, like the model numbers and importing your kernel. A quick search showed that the Xiaomi Redmi Note 3 might fit the bill. Check out this thread for a TWRP build that someone has made for it...
diplomatic said:
Oh, cool. How did you unlock it, btw? I know Asus makes you jump through hoops or doesn't allow unlocking altogether...
In case there is no device tree source (almost always), you start with an existing source tree for a phone with a similar platform. Then you adapt it for your device. Usually it's just a few changes, like the model numbers and importing your kernel. A quick search showed that the Xiaomi Redmi Note 3 might fit the bill. Check out this thread for a TWRP build that someone has made for it...
Click to expand...
Click to collapse
Sounds good, I'll see what I can do when I get the time.
For some reason one of the official unlock tools for a different model worked on my tablet - I believe it was for the ZE552KL, although I could be wrong since I can't seem to install it any more ("the package conflicts with an existing package by the same name"). I'm definitely unlocked though since I can flash using fastboot without any errors...
Since we now have official unlock. Any chance at custom roms for this device? I would love to see it get some oreo love.
soleera said:
Nice work! I've got the Z500KL version of this tablet, so I'm hoping to port twrp to it at some point as well; if you have any tips or advice that might help it would be much appreciated! Although I'm fairly experienced with Linux this would be my first time working with Android, so I'm not sure if I'll succeed, but I thought I'd give it a shot anyway.
Click to expand...
Click to collapse
Hello soleera
Have you succeeded to port twrp to Z500KL?
Do you know of any custom recovery for Z500KL?
Do you know how to root it?
Dr.Ghobar said:
Do you know how to root it?
Click to expand...
Click to collapse
Since it seems to be possible to unlock the bootloader, you can always try the offline patching method of Magisk Manager. Just get your boot.img from the stock firmware and run it through MM to make a rooted patched boot img. Then using this patched image from your PC, do either 'fastboot flash boot' or 'fastboot boot' (for tethered boot) to obtain root. Done.
diplomatic said:
Since it seems to be possible to unlock the bootloader, you can always try the offline patching method of Magisk Manager. Just get your boot.img from the stock firmware and run it through MM to make a rooted patched boot img. Then using this patched image from your PC, do either 'fastboot flash boot' or 'fastboot boot' (for tethered boot) to obtain root. Done.
Click to expand...
Click to collapse
Thank you for your answer.
But I am not familiar with what you said and with the expressions you used. Can you explain in plain language or point me to a tutorial?
Dr.Ghobar said:
Thank you for your answer.
But I am not familiar with what you said and with the expressions you used. Can you explain in plain language or point me to a tutorial?
Click to expand...
Click to collapse
Basically, just do the procedure in this post. It's not that complicated. Reading through that thread may also help. Oh, and you have to unlock your bootloader first with an Asus unlock tool, as soleera has mentioned. I think the tool for the Z500M may work. It's essentially the same app for every device.
Hi guys!
I've bought Moto E5 XT1944-2 just few days ago, I was looking for some info to root the device but I couldn't find any tutorial, and after a couple of hours I found a way to root the device, so I'm going to explain how to root this device.
Disclaimer
I'm not responsible for any dead phones, even if they explode or cause a war
If you didn't follow the steps one by one
VERY IMPORTANT!!
There's no way to backup using TWRP (cos is not available yet)
Also it seems that it doesn't works with XT1944-1 (try by your own risk)
REQUIREMENTS:
1. Unlocked Bootloader
2. Magisk Manager apk https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
3. Boot Image from stock rom (you need to choose your current variant to avoid some possible problems) https://forum.xda-developers.com/moto-e5/how-to/firmware-moto-e5-xt1944-4-dual-sim-t3820901
4. Motorola Drivers and ADB/Fastboot Drivers also
5. PC
6. A good brain and some patience LOL
Well, considering that already have all what I've mentioned lest begin.
FIRST STEP
Download and install Magisk Manager, It will show and advertisement asking if you want to install Magisk v16 (the screenshot says v16.7 but it's because I've got root already).
https://www.dropbox.com/s/a8mj0w0mk7uho7x/Screenshot_20180803-232248%5B1%5D.png?dl=0
Press no thanks, then open the app and in settings change the Update Channel into Beta , it's very important to know that because only Magisk v16.7 works, previous versions wont work!!
https://www.dropbox.com/s/vk404a1d0oou0ji/Screenshot_20180803-225740%5B1%5D.png?dl=0
https://www.dropbox.com/s/fyi6b3c1tgtfj5u/Screenshot_20180803-225745%5B1%5D.png?dl=0
SECOND STEP
After you have already downloaded the zip from your variant, use Winrar/7 Zip or any program to extract boot.img and then copy boot.img to you internal/external storage
THIRD STEP
Open again Magisk Manager, it will show if you want to install Magisk v16.7, press install, and select Patch Boot Image File
https://www.dropbox.com/s/9xyqgu8p4mm2ddy/Screenshot_20180803-232254%5B1%5D.png?dl=0
Then you need to look for the boot.img previously unzipped and moved onto your storage
https://www.dropbox.com/s/xlik3p9cau4952f/Screenshot_20180803-232720%5B1%5D.png?dl=0
After that the process began and it will save a new file called "patched_boot" that will be located on storage/MagiskManager
FOURTH STEP
Reboot your phone to bootloader mode and move to your computer the patched_boot.img, then flash that boot image via CMD with this command:
fastboot flash boot patched_boot.img
https://www.dropbox.com/s/xlik3p9cau4952f/Screenshot_20180803-232720%5B1%5D.png?dl=0
https://www.dropbox.com/s/h0r03mio06jezzz/XDA2.png?dl=0
It might delay less than a minute.
Finally run the command:
fastboot reboot
In my case shows a black screen saying, invalid key with white letters, if that is your case wait a minute, it will boot, if says N/A maybe something is wrong but first wait until the phone starts, if not, you have chosen the incorrect boot.img, to fix that just flash the original boot.img you've extracted with the command:
fastboot flash boot boot.img
And your phone will start normally, you don't need to wipe, and you wont loose your data
If you have some questions, let me know, oh, forget to mention, I'm not a dev so I don't know if it will be any rom available soon...
P.D I've tested only Substratum and it doesn't works, Xposed not tested yet because it turn the phone slower (in my experience) also some modules are not compatible and it will brick your device, Viper4Android works fine, you only need to install it via Magisk but keep in mind to use version 6.1 designed for Masigk v15 and upper...
I've created a telegram channel to help each others =)
https://t.me/joinchat/AAAAAEkiNbz-qY1tlKVgGQ
Woooow the scene grow up!. This guide is compatible with the Moto E5 xt1944-1?.
intherior said:
Woooow the scene grow up!. This guide is compatible with the Moto E5 xt1944-1?.
Click to expand...
Click to collapse
If it is nova_row I guess so, but well you need to try, remember that you need the stock ROM to extract boot and then in case of something wrong, also bootloader unlocked sir
Nice work @Fersho. Thank you for your contribution and your time.
Good descriptive guide.
I try to follow the guide using the Xt1944-1 stock rom image and after do it everything my Moto E5 get stucks on the Moto logo and reboots everytime. Only restoration guide of pal MotoJunkie01 revives.
intherior said:
I try to follow the guide using the Xt1944-1 stock rom image and after do it everything my Moto E5 get stucks on the Moto logo and reboots everytime. Only restoration guide of pal MotoJunkie01 revives.
Click to expand...
Click to collapse
Glad you got it back to life.
MotoJunkie01 said:
Nice work @Fersho. Thank you for your contribution and your time.
Click to expand...
Click to collapse
Thank you, all in the name of development and to help each others
intherior said:
I try to follow the guide using the Xt1944-1 stock rom image and after do it everything my Moto E5 get stucks on the Moto logo and reboots everytime. Only restoration guide of pal MotoJunkie01 revives.
Click to expand...
Click to collapse
You've tried flashing only boot? beause I mentioned that it wasn't necessary to flash the whole time, just flashing the stock boot the phone will start normally, but well that means that the XT1944-1 is unable to root, did you follow the correct steps? I mean you tried with Magisk v16.7?
Fersho said:
You've tried flashing only boot? beause I mentioned that it wasn't necessary to flash the whole time, just flashing the stock boot the phone will start normally, but well that means that the XT1944-1 is unable to root, did you follow the correct steps? I mean you tried with Magisk v16.7?
Click to expand...
Click to collapse
I think that i follow well. And i put my boot.img from stock rom with Magisk to make the patched_boot.img. Then i connect to the Pc to copy that file to the adb directory, reboot on bootloader mode and flash with the command that you post. Everything well, buy when i reboot after flash that appears the N/A letters and stucks rebooting everytime. When i reflash the smartphone with the stock rom then the Bad Key letters appears and make the boot well.
I dont know if isn't compatible yet
intherior said:
I think that i follow well. And i put my boot.img from stock rom with Magisk to make the patched_boot.img. Then i connect to the Pc to copy that file to the adb directory, reboot on bootloader mode and flash with the command that you post. Everything well, buy when i reboot after flash that appears the N/A letters and stucks rebooting everytime. When i reflash the smartphone with the stock rom then the Bad Key letters appears and make the boot well.
I dont know if isn't compatible yet
Click to expand...
Click to collapse
Well at least you've restored your phone, I think the same, that is not compatible, but well we won't know if something works til' we try, but thanks to share your experience I've edited the thread telling that issue, that happened to me but it boots while shows N/A
Does not work on xt1944-4
Hi, the ROM link for the stock rom is for the Moto E5 Play (James). Is this also the right one for Moto E5 (nora_row), because both phones have different specifications (according to GSM arena).
Otherwise, thanks for your help @Fersho.
artemis1102 said:
Hi, the ROM link for the stock rom is for the Moto E5 Play (James). Is this also the right one for Moto E5 (nora_row), because both phones have different specifications (according to GSM arena).
Otherwise, thanks for your help @Fersho.
Click to expand...
Click to collapse
My mistake, I didn't notice that I put the link for E5 Play Stock ROM, now is updated with the right one
Fersho said:
My mistake, I didn't notice that I put the link for E5 Play Stock ROM, now is updated with the right one
Click to expand...
Click to collapse
Seems like the right one now, thanks for your help. I'll give it a try.
Edit: I checked the page and there is no mention of the OPP27.91-72 build. Do you think the OPP27.91-25 will work or should I get the firmware from stock rom .net, which seems to have the correct one.
Thanks for updating the link anyways @Fersho
artemis1102 said:
Seems like the right one now, thanks for your help. I'll give it a try.
Edit: I checked the page and there is no mention of the OPP27.91-72 build. Do you think the OPP27.91-25 will work or should I get the firmware from stock rom .net, which seems to have the correct one.
Thanks for updating the link anyways @Fersho
Click to expand...
Click to collapse
The thread is not updated yet, so It will work because you only need the stock rom for your specific device, if it is updated or not, doesn't matter, I guesss that nora and hannah have got a security patch, but is not necessary, I mean still outdated, so don't take care about it
Hi
Have someone this firmware "XT1944-4 NORA_ROW_OPP27.91-146_cid50_subsidy-DEFAULT" for share ?
I would like to verify once magisk is I stalled and the manager is running and root works if we update will it still work. There are supposed exports who have said that if you update the magiks manager to the latest version 18+ or magiks 18+ versions that magics won't work anymore for the Moto e5 play can any one vetify
daktras said:
I would like to verify once magisk is I stalled and the manager is running and root works if we update will it still work. There are supposed exports who have said that if you update the magiks manager to the latest version 18+ or magiks 18+ versions that magics won't work anymore for the Moto e5 play can any one vetify
Click to expand...
Click to collapse
running 18 on e5+ perfectly
It worked on my XT1944-2 but only with Stock-ROM. Until nowI have no solution to Root with Lineage 17.1 OS on it.
Unbrick tool by One-Team - EypCnn
First: This tool seems to be from EypCnn, One-Team. All credits to them!
EDIT2: I no longer own this device, so i will leave this thread here for people to use. But don't expect any direct support from me .
What can this tool do?:
Restore phone to Stock(International) Firmware (S048) Marshmallow (Locked & Unlocked bootloader)
Fix Lost or bad Signal / IMEI any software Problem
For who does this work?
Pretty much any Lenovo P2 Variant (Chinese and International)
Phones which can access bootloader(you have to boot into it)
Works on Locked & Unlocked Bootloader
Installation aka. Flashing-Steps
Put your phone into bootloader (which is also fastboot) mode.
Download the folder and unzip it.
Connect your phone to your pc.
Go into the unzipped folder and open "flashall - stock reco.bat"
Wait, for the process to end, your phone will reboot on its own.! A stock lenovo bootlogo will show up !
You can disconnect your phone cable from pc and plug into a wall charger, just to be safe. Once the lockscreen is showing up, you're done.
If you want to flash Custom Roms:
look below:
WHEN MOVING TO CUSTOM ROMS NOW:
1. Boot to twrp. (Make sure it is pietwrp from telegram or the official 3.2.3 or later version)
2. Select WIPE menu option
3. Select data partition
4. Change file format to f2fs or anyother.
5. Go back to Start Menu of TWRP, choose Reboot Menu Option
6.Reboot to Recovery
7. Repeat Steps 2 and 3
8. This time select EXT4 when changing file format
9. Do Step 5 and 6
10. Wipe System,Cache and Dalvik-Cache partitions
( for older twrp versions: 10.1 If you're on official twrp 3.2.3 or lower, you have to flash pietwrp or latest twrp now !)
11. Flash your Custom Rom, Gapps (optional) and latest Magisk(optional)
12. Wipe Cache and Dalvik-Cache
13. Reboot. First Boot might take a few minutes but never longer than 7minutes.
If it takes longer, you're encounter a so called bootloop.
Comment hear if that happens, containing information on your twrp-version, rom, gapps, magisk and mods(if present) you're using.
When you corrupt your internal Storage or geht TWRP Error 1001, Error 7:
1. Repeat steps 2-6
2. Repeat steps 7-8
Download(Official Link)
2nd Link(reuploaded because some couldn't download it from androidfilehost): https://drive.google.com/open?id=1wUOZiTwW8mo0IheAGONyj9-QnjimnY2M
I will help if questions arise.
Credits to One-Team & EypCnn.
Thanks a lot. You literally saved my life!
Works like Magic
Thanks a lot for saving my ass . simplest way to downgrade to mm too. Thanks again
Wait.... downgrade to MM? Does this mean you can regain your signal or did @krishnakoonala get it wrong?
I have a spare P2 lying around that I never used because the IMEI got corrupted and I couldn't flash the bootloader files since I was unlocked.
I assume this wouldn't solve my issue?
eried1 said:
Wait.... downgrade to MM? Does this mean you can regain your signal or did @krishnakoonala get it wrong?
I have a spare P2 lying around that I never used because the IMEI got corrupted and I couldn't flash the bootloader files since I was unlocked.
I assume this wouldn't solve my issue?
Click to expand...
Click to collapse
My p2 was bricked and , stuck in boot loop. I followed the above instructions, 10 mins into it , it booted with mm version, the same version when i bought and booted for 1st time. It was like a new phone to me.
So i assume if one has upgraded to noughat and want to downgrade but is worried he might brick his device, one can take a back up and try this tool. It works flawless.
No harm in trying this one if ur p2 can boot up mate. Give it a shot. Good luck
Cheers
This tool has saved my device from multiple over a span of two years soft bricks. Can confirm it to do wonders.
eried1 said:
Wait.... downgrade to MM? Does this mean you can regain your signal or did @krishnakoonala get it wrong?
I have a spare P2 lying around that I never used because the IMEI got corrupted and I couldn't flash the bootloader files since I was unlocked.
I assume this wouldn't solve my issue?
Click to expand...
Click to collapse
THis will solve your problem , Cheers.
I tried but cannot download it - do you where to find it?
can i flash this without pc?? if yes please tell how
@sm00th4f3 bro, i wanna know, does this tool flashes full ROM including modem files etc, even on unlocked bootloader?
What is the state of bootloader after using this tool?
amansehdav said:
@sm00th4f3 bro, i wanna know, does this tool flashes full ROM including modem files etc, even on unlocked bootloader?
What is the state of bootloader after using this tool?
Click to expand...
Click to collapse
It flashed everything you have when you buy a new phone. And no, it doesn't lock your bootloader.
So you can either :
- keep using MM Stock Rom S048
- Update via ota in System like you normally would do.
- Update till latest Firmware, then flash twrp- and then Custom Rom of your Choice.
Bootloader is in the same state it was before you used this tool.
sm00th4f3 said:
It flashed everything you have when you buy a new phone. And no, it doesn't lock your bootloader.
So you can either :
- keep using MM Stock Rom S048
- Update via ota in System like you normally would do.
- Update till latest Firmware, then flash twrp- and then Custom Rom of your Choice.
Bootloader is in the same state it was before you used this tool.
Click to expand...
Click to collapse
So how does it fixes corrupted modems? it cannot be flashed on unlocked P2 right?
amansehdav said:
So how does it fixes corrupted modems? it cannot be flashed on unlocked P2 right?
Click to expand...
Click to collapse
I literally just answered it above somewhere.
(Literally in thread description)
You can flash it on unlocked bootloader or locked as well.
So many thanks for bringing up tis tool for us!
This thread should be stick as the "New user" thread is, they definitely belong together.
Download source
Thanks guys, if this works I can now revive my phone. But can someone please upload the tool to another place like google drive. From android filehost it will take an eternity to download!
HkQc said:
So many thanks for bringing up tis tool for us!
This thread should be stick as the "New user" thread is, they definitely belong together.
Click to expand...
Click to collapse
I didn't bring it up, i just linked it . All Credits belong to ONE TEAM and EypCnn.
ryd3r89 said:
Thanks guys, if this works I can now revive my phone. But can someone please upload the tool to another place like google drive. From android filehost it will take an eternity to download!
Click to expand...
Click to collapse
Link updated, Cheers
Lavesh05 said:
can i flash this without pc?? if yes please tell how
Click to expand...
Click to collapse
Nah you need a Computer for this.
no signal after using "flashall - stock reco.bat", it finished successfully, but after rom setup still no signal
GPSSlovakia said:
no signal after using "flashall - stock reco.bat", it finished successfully, but after rom setup still no signal
Click to expand...
Click to collapse
If you used some other tool for imei. You are pretty much done for.
Using this tool i can go to MM version and can upgrade to S251. However after installing twrp and flashing custom rom, it goes to bootloader
I rooted following Maxwell's tutorial (OnePlus 7 Pro - How to Unlock the Bootloader, Install TWRP, and Root with Magisk
).
Now that all is said and done, and my phone is rooted, I noticed that:
1) The wifi does not work. It will not let me enable wifi. Just keeps switching back to off.
2) The speakers don't work.
I need to know how to fix it. What do I do?
I am new to android so I am not sure the steps needed to fix this botched install/operating system/root whatever
U prob flashed the wrong boot.img, make sure to flash the correct model and OS version.
What model and OS version do you have?
download
Bradl79 said:
U prob flashed the wrong boot.img, make sure to flash the correct model and OS version.
What model and OS version do you have?
Click to expand...
Click to collapse
This is probably an error on my end then. I chose "Global 1917 1911" but my about phone page says "1913", however, my phone also says 9.5.1 and there is no 9.5.1 (under 1913) in the link you provided. Do I need to upgrade my OS first before retrying?
jfny100 said:
This is probably an error on my end then. I chose "Global 1917 1911" but my about phone page says "1913", however, my phone also says 9.5.1 and there is no 9.5.1 (under 1913) in the link you provided. Do I need to upgrade my OS first before retrying?
Click to expand...
Click to collapse
yes you will need to upgrade, there was no 9.5.1 full zip released for us to have patched the boot.img. So update and then patch the correct OS and Model version you update to. Let us know if you have any other issues.
I swear nobody reads the threads before starting. Your wifi is disabled because your rooted boot image does not match the version you should have.
Just flash one of the kernels in the roms section, I'm using ElementalX 1.10, wifi will come back up.
Bradl79 said:
yes you will need to upgrade, there was no 9.5.1 full zip released for us to have patched the boot.img. So update and then patch the correct OS and Model version you update to. Let us know if you have any other issues.
Click to expand...
Click to collapse
Okay. That was it (flashing the wrong boot.img) It's working now - I upgraded to latest OS. Downloaded correct boot.img. Redid the root process with correct files this time, and it worked. Wifi is good. Speakers are good. Everything is good. Thanks for the help. Also, I removed any criticism of the tutorial creators in my post since it turns out I was the idiot. I'm brand new to android though so go easy on me.
djsubterrain said:
I swear nobody reads the threads before starting. Your wifi is disabled because your rooted boot image does not match the version you should have.
Just flash one of the kernels in the roms section, I'm using ElementalX 1.10, wifi will come back up.
Click to expand...
Click to collapse
I didn't read the post until after I encountered errors. I was going off of the video. One problem I had was that the video assumed I had a basic knowledge of some steps, so they didn't mention them. I did not have this knowledge since I am brand new to android. Anyways. I was able to fix these errors via the steps discussed in earlier comments. Everything is working now. I removed any criticism of the tutorial creators from this post since it turns out I'm the idiot.
Glad you got it working
Why are people even flashing boot images? Just unlock bootloader, boot twrp from fastboot, flash twrp, flash magisk, all done.
JedixJarf said:
Why are people even flashing boot images? Just unlock bootloader, boot twrp from fastboot, flash twrp, flash magisk, all done.
Click to expand...
Click to collapse
BC that is just an extra step not really needed, I haven't even flashed twrp on my device yet, if I need it I will just boot to it, it's so much easier doing this.
I always thought the same thing u did, until I just flashed the patched boot and updating is so much easier too.
JedixJarf said:
Why are people even flashing boot images? Just unlock bootloader, boot twrp from fastboot, flash twrp, flash magisk, all done.
Click to expand...
Click to collapse
Because I'm just following along with the tutorial xda put on YouTube and that's what they say to do