I read the lineage documentation for installation, but I got pretty lost.
In the parts of Booting a custom recovery using fastboot and Ensuring all firmware partitions are consistent.
These parts I read and did not understand, and if possible I would like help.
I've already managed to unlock the bootloader and install root on the device via magisk.
If anyone who has already managed to install can help me, thank you.
Related
I am unsure whether my phone (which is being delivered from Gearbest) will have google play store and google sync etc all installed and working. If I don't have all of that installed + working I am going to try and flash a ROM (probably unofficial CM14.1) from here.
Now, when I went to see how to unlock the bootloader, the guide had a lot of chinese writing, so I couldn't understand what I was supposed to do... Can someone explain in english how I am supposed to unlock the bootloader?
The following is a snippet that I did not understand from the guide. Link : https://forum.xda-developers.com/zuk-z2-pro/development/how-bootloader-zuk-z2-pro-t3415392
"Unlocking the phone...
With the email now received it's time to do some dev stuff...
尊敬的ZUK用户，您好
 您已经在ZUK开发者平台申请了解锁您的ZUK智能设备的bootloader。
 附件是适用于您的设备的解锁文件，请妥善保管。
 请访问这里了解如何进行解锁操作。
 如果不是您本人操作或者您改变主意，请忽略这封邮件，您的设备将不会受到任何影响。
ZUK开发者平台
Download the unlock_bootloader.img from the email and place it somewhere easy to find for flashing."
CarpeDiemJay said:
I am unsure whether my phone (which is being delivered from Gearbest) will have google play store and google sync etc all installed and working. If I don't have all of that installed + working I am going to try and flash a ROM (probably unofficial CM14.1) from here.
Now, when I went to see how to unlock the bootloader, the guide had a lot of chinese writing, so I couldn't understand what I was supposed to do... Can someone explain in english how I am supposed to unlock the bootloader?
The following is a snippet that I did not understand from the guide. Link : https://forum.xda-developers.com/zuk-z2-pro/development/how-bootloader-zuk-z2-pro-t3415392
"Unlocking the phone...
With the email now received it's time to do some dev stuff...
尊敬的ZUK用户，您好
 您已经在ZUK开发者平台申请了解锁您的ZUK智能设备的bootloader。
 附件是适用于您的设备的解锁文件，请妥善保管。
 请访问这里了解如何进行解锁操作。
 如果不是您本人操作或者您改变主意，请忽略这封邮件，您的设备将不会受到任何影响。
ZUK开发者平台
Download the unlock_bootloader.img from the email and place it somewhere easy to find for flashing."
Click to expand...
Click to collapse
Not sure how far you've gotten following that guide. It's very good in pointing you where you need to look but it assumes that you do have a bit of knowledge to follow the basic steps without given a full explanation of every step you need to take.
With that in mind, I loaded a custom ROM in my phone just last week and here's the steps and the pitfalls you need to avoid:
This is the guide I used: http://zukfans.eu/community/threads/zuk-z2-bootloader-unlock.62/
So grab your phone S/N, install ADB and Fastboot on your PC, and install the Google and ZUK drivers.
Things to note:
If you're on Windows 8/10, you might have issues with driver signing enforcement. Bizzarely the drivers from Lenovo for the ZUK are unsigned and Windows does not like that. So you might need to disable this function. Thankfully, it's rather painless. http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
Now to unlock the bootloader. You'll need to go to http://developer.zuk.com/bootloader but first you'll need to register to the site. I'm assuming that you're not in China or have a chinese SIM lying around so you'll need to register using email, which can be done here: https://passport.zuk.com/wauthen3/w...lenovoid.thirdname=null&lenovoid.qrstate=null
Once you register, fill in the bootloader unlock form and you'll get an email with some Chinese writing, this is unimportant. Look at the attachment to that email and you'll find a unlock_bootloader.img file. Download it and you're in business.
Now I ran into trouble sending fastboot commands to my phone, just wouldn't be detected for some reason, no clue why. But I found this tool by mauronofrio: https://forum.xda-developers.com/zu...ol-tool-one-driversunlocktwrpfactory-t3432782 - works like a charm, you can use it to unlock the bootloader and then install TWRP on your phone.
Once you have TWRP then you can install whatever ROM that tickles your fancy, no problem. Personally I'm running Resurrection Remix by fedor917. I tried CM14.1 but it's not stable enough for me and I much prefer RR. Plus it's Marshmallow so xposed works fine on it and plenty other stuff that hasn't reached Nougat yet. I really want Nougat-based Resurrection Remix on this phone and I've been working at porting it, but it's the first time I do this so it's quite a steep learning curve.
Uivalf39 said:
Not sure how far you've gotten following that guide. It's very good in pointing you where you need to look but it assumes that you do have a bit of knowledge to follow the basic steps without given a full explanation of every step you need to take.
With that in mind, I loaded a custom ROM in my phone just last week and here's the steps and the pitfalls you need to avoid:
This is the guide I used: http://zukfans.eu/community/threads/zuk-z2-bootloader-unlock.62/
So grab your phone S/N, install ADB and Fastboot on your PC, and install the Google and ZUK drivers.
Things to note:
If you're on Windows 8/10, you might have issues with driver signing enforcement. Bizzarely the drivers from Lenovo for the ZUK are unsigned and Windows does not like that. So you might need to disable this function. Thankfully, it's rather painless. http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
Now to unlock the bootloader. You'll need to go to http://developer.zuk.com/bootloader but first you'll need to register to the site. I'm assuming that you're not in China or have a chinese SIM lying around so you'll need to register using email, which can be done here: https://passport.zuk.com/wauthen3/w...lenovoid.thirdname=null&lenovoid.qrstate=null
Once you register, fill in the bootloader unlock form and you'll get an email with some Chinese writing, this is unimportant. Look at the attachment to that email and you'll find a unlock_bootloader.img file. Download it and you're in business.
Now I ran into trouble sending fastboot commands to my phone, just wouldn't be detected for some reason, no clue why. But I found this tool by mauronofrio: https://forum.xda-developers.com/zu...ol-tool-one-driversunlocktwrpfactory-t3432782 - works like a charm, you can use it to unlock the bootloader and then install TWRP on your phone.
Once you have TWRP then you can install whatever ROM that tickles your fancy, no problem. Personally I'm running Resurrection Remix by fedor917. I tried CM14.1 but it's not stable enough for me and I much prefer RR. Plus it's Marshmallow so xposed works fine on it and plenty other stuff that hasn't reached Nougat yet. I really want Nougat-based Resurrection Remix on this phone and I've been working at porting it, but it's the first time I do this so it's quite a steep learning curve.
Click to expand...
Click to collapse
Thank you for replying.
I have found a simpler guide I believe...
https://www.youtube.com/watch?v=iinsQCuZr9Q or the written version... : http://www.gizbeat.com/11283/hs-usb...r-zuk-z2-and-any-qualcomm-phone-with-miflash/
There is no mention of unlocking the bootloader.
Do i not have to unlock the bootloader then?
CarpeDiemJay said:
Thank you for replying.
I have found a simpler guide I believe...
https://www.youtube.com/watch?v=iinsQCuZr9Q or the written version... : http://www.gizbeat.com/11283/hs-usb...r-zuk-z2-and-any-qualcomm-phone-with-miflash/
There is no mention of unlocking the bootloader.
Do i not have to unlock the bootloader then?
Click to expand...
Click to collapse
That is just for installing the stock ROM (ZUI) so for that you don't need to unlock your bootloader, but if you want to install a custom ROM (Cyanogenmod, MIUI, Resurrection Remix, etc.) you do need to unlock the bootloader and the install process is much simpler (unlock bootloader -> install TWRP -> wipe & install whatever ROM .zip file you want).
Uivalf39 said:
That is just for installing the stock ROM (ZUI) so for that you don't need to unlock your bootloader, but if you want to install a custom ROM (Cyanogenmod, MIUI, Resurrection Remix, etc.) you do need to unlock the bootloader and the install process is much simpler (unlock bootloader -> install TWRP -> wipe & install whatever ROM .zip file you want).
Click to expand...
Click to collapse
Ah okay, thanks.
I've found a good tutorial I think. It seems more simple compared to using the qfil qualcom software stuff. What do you reckon? I've seen other people (can't remember what thread exactly) suggesting miflash to be used as well.
http://www.gizbeat.com/11283/hs-usb...r-zuk-z2-and-any-qualcomm-phone-with-miflash/
Hi,
I am very new to this android world so my queries might feel stupid. Actually i m here after 3 years and that is very long period in this world. I know about rooting(super Su), bootloader and recovery (stock,CM and TWRP) . Recently read about Magisk and got some queries. Hope you will help me out. These are not device specific but need to learn.
What i read/study i found these readings...
1. Magisk roots device systemlessly (does not touch system partition) so one can get OTA updates easily.
2.To install and run Magisk one needs to unlock the bootloader .
3.(Device Specific) My redmi MI Flash tool says,If you unlock the bootloader , you wont get OTA updates.
4.I have previously rooted my galaxy Y and uninstalled system apps. If i delete sys apps from magisk,still can we say that we are not touching system.
So all statements are true? or some? or none ?
Here my device is redmi 3s (6.0.1- MIUI 9.6.1.0 Global Stable).All these queries are just in relation to OTA system updates. Nothing related to warranty.
Thanking You
Yes.
Yes.
Don't know about Xiaomi, but I've never had issues with OTA on a device with an unlocked bootloader (I've mainly used different Google and Oneplus devices). Someone with a Xiaomi is gonna have to chime in on this one.
As long as you use Magisk's debloating feature of replacing files or directories with empty ones, you're good. The actual /system partition won't be touched. Use a module like the Debloater module by @veez21, or make a debloater module yourself.
Didgeridoohan said:
Don't know about Xiaomi, but I've never had issues with OTA on a device with an unlocked bootloader (I've mainly used different Google and Oneplus devices). Someone with a Xiaomi is gonna have to chime in on this one.
Click to expand...
Click to collapse
Ahh, Thank You.
You get OTA system updates for your STOCK ROM ?
inwell said:
Ahh, Thank You.
You get OTA system updates for your STOCK ROM ?
Click to expand...
Click to collapse
Yes. But, having both Magisk and a custom recovery (an OTA won't install with a modified boot image and a custom recovery installed) I always find it easier to download the update and flash it manually. But, like I said, I have no idea if this is true for Xiaomi.
1. Ok. i also heared that when you update your device,you lose root...not true ? Or you need to root again ?
2.In normal stock device,we get update notification and we downlaod then restart (as per convenience)device to update.
If i remove some system apps from my rooted device and unroot the device,manage to get stock recovery back ,will the OTA update system treat my device as Stock-untouched? And install updates just as stock device will do ?
3. Is boot.img and bootloader are same things? Coz i read that for re locking boot loader you need to flash boot.img from stock software. (But Some procedures just use fastboot and relock oem command-they wont use boot.img,dont know why )
I read that unrooting,restoring stock recovery and locking bootloader again is more difficult/complicated than the rooting procedure
Some one should come up with solution just like Windows Restore .If you want to go back to everything STOCK,just use that feature same as done to Restore Windows in its previous state.
Any update that also updates the boot image (which means pretty much all) will remove root. But, that's just a simple case of reflashing Magisk right after applying the update.
If you've touched /system in any way, removing system apps or even just mounting the /system partition read-write, an OTA will fail. To be able update with an OTA your /system and /vendor partitions need to be untouched and you need to have the stock boot image and stock recovery installed. If your device doesn't conform to this the OTA will fail.
Boot image and bootloader are not the same thing. That you can read up on all over the internet, so I won't go into details. If you have done any kind of modifications on your device, I suggest you leave your bootloader unlocked. It's to easy to mess things up otherwise.
Going back to full stock is usually just a matter of flashing a full factory image/firmware package/stock ROM. Quite easy... Of course, some manufacturers make it harder than others.
Didgeridoohan said:
Boot image and bootloader are not the same thing. That you can read up on all over the internet, so I won't go into details. If you have done any kind of modifications on your device, I suggest you leave your bootloader unlocked. It's to easy to mess things up otherwise.
Click to expand...
Click to collapse
Ok. As you say the two are different , but can you explain in simple words (terms) that how they both are related/linked/connected? Coz as i read some forums/posts i get to read
1. To relock/lock bootloader you need to flash boot.img which suggests these (terms) are linked/connected.
2. but same time some forums/post suggest no img file flashing but just a fastboot command(s) to relock bootloader. In this case it seems they are not linked/connected.
And if the above 2 statements are true and device specific then how the bootloader and boot image are linked and not linked in diff devices? what changes are made so that in some cases these are linked and in some not
Sorry for asking too much. But you were really very kind to help me out.Thank you once again
I'm not 100% accurate (and someone will hopefully come I'm and correct me if needed), but basically the bootloader checks that everything is alright and then starts up your device. After that the boot image (ramdisk and kernel) takes over. Ramdisk basically makes sure all the partitions are mounted, and the kernel is exactly what it sounds like. The core of the OS, making sure that everything is working as it should.
This is of course a huge over-simplification, so if you want more you'll have to search around (and there are tons of resources around the web).
The main reason I can think of right at the moment for wanting to flash a boot image before locking the bootloader is that it's generally a good idea to have your device fully stock and functional before doing so. After you've locked the bootloader there might not be any going back if things start acting up and you could end up with a nice paperweight.
Questions are good. That's how you learn. I do believe that you'd be much better of searching around the internet for your answers. They've been put out there many, many times.
Ok.Thank you very much.I will learn more ...
I rooted the e5 plus using this method: https://forum.xda-developers.com/mo...o-e5-plus-rhannah-backup-magisk-root-t3822702
This was different from what I'm used to as normally TWRP replaces the stock recovery and then root is applied. Here, TWRP is only used in fastboot and not applied permanently.
A couple of questions:
Since recovery is not replaced, can this device receive OTA updates with no issues?
Can a normal factory reset be done without soft bricking the device?
If I want to install zip files for mods etc, can I use the fastboot temp TWRP to do this and it will still work?
Are there any actions/caveats that should be done or avoided with this TWRP method?
Excuse my ignorance but I'm sure someone else may have the same question and I'd rather not brick my device.
Thank you.
shezzy83 said:
I rooted the e5 plus using this method: https://forum.xda-developers.com/mo...o-e5-plus-rhannah-backup-magisk-root-t3822702
This was different from what I'm used to as normally TWRP replaces the stock recovery and then root is applied. Here, TWRP is only used in fastboot and not applied permanently.
A couple of questions:
Since recovery is not replaced, can this device receive OTA updates with no issues?
Can a normal factory reset be done without soft bricking the device?
If I want to install zip files for mods etc, can I use the fastboot temp TWRP to do this and it will still work?
Are there any actions/caveats that should be done or avoided with this TWRP method?
Excuse my ignorance but I'm sure someone else may have the same question and I'd rather not brick my device.
Thank you.
Click to expand...
Click to collapse
OTA won't work if rooted, you'll have to flash stock boot or flash full stock ROM.
Flashing twrp causes issues because of avb and dm-verity
TWRP won't have access to data because of encryption and won't be able to write to system.
Basically you're only booting twrp to make a backup and then use Magisk to patch your boot.img for root. From there you can install magisk modules and Xposed as well as any apps you use that need root.
You might use the TWRP installer within Android to install TWRP but it didn't boot for me on my E5 Plus.
reaper-death said:
Basically you're only booting twrp to make a backup and then using Magisk to patch your boot.img for root.
.
Click to expand...
Click to collapse
Ok so that's the answer I was looking for. TWRP is ONLY for backing up in our case since it doesn't have access. Therefore, none of what I asked about will work.
shezzy83 said:
Ok so that's the answer I was looking for. TWRP is ONLY for backing up in our case since it doesn't have access. Therefore, none of what I asked about will work.
Click to expand...
Click to collapse
These Moto e5 + posts have become pointless.
No method works and if root does work it will have issues. The original poster can't fix the issue because they don't know what they are talking about half the time.
We need better people on here who can make a video or explain how to do this without ****ing with our heads ?
Like a person who knows what they are doing with that exact phone model and are not just saying **** for a post ?
Contact me if you need real help fixing these people's mistakes [not root] "fix a bricked phone"!
Hello all,
I bought recently a used mi8 for replacing my oldie mi5.
I have reading several posts that are related with flashing the roms, and several talk about the encryption storage.
I know that xiaomi encrypts the storage and that I need to format, but I get confused with the necessity of having to flash or not the dm-verity pack.
So what I know so far and please correct me if I'm wrong:
First boot loader unlock no problem
Second install Twrp, can I use the latest official or search for a specific package????
Third in the Twrp format everything
Fourth after format I remember something about keeping system read only or not, what do I need to do???
Fifth grab an asop rom and flash it
Sixth if I want root, use the Magisk, normally or do I need to pay attention to anything else.
Sorry, for so many things, but I read plenty, before asking
robrodrigues said:
Hello all,
I bought recently a used mi8 for replacing my oldie mi5.
I have reading several posts that are related with flashing the roms, and several talk about the encryption storage.
I know that xiaomi encrypts the storage and that I need to format, but I get confused with the necessity of having to flash or not the dm-verity pack.
So what I know so far and please correct me if I'm wrong:
First boot loader unlock no problem
Second install Twrp, can I use the latest official or search for a specific package????
Third in the Twrp format everything
Fourth after format I remember something about keeping system read only or not, what do I need to do???
Fifth grab an asop rom and flash it
Sixth if I want root, use the Magisk, normally or do I need to pay attention to anything else.
Sorry, for so many things, but I read plenty, before asking
Click to expand...
Click to collapse
Well come to Mi8 mate.
1. You need to unlock bootloader
2. Install official or IMO use Orangefox recovery which is based on latest twrp with some themes and extras.
3. You are right
4. After installing twrp or similar you need to slide on first run if you want to enable flashing etc.
5. Choose any rom you want
6. Yes Magisk is your only option, if you need root.
However if your device is unencrypted than you don't need to install dmverity. I am also used many AOSP roms on my unencrypted device and faced zero issues.
[emoji3590] from [emoji1191]
ammaralidj said:
Well come to Mi8 mate.
1. You need to unlock bootloader
2. Install official or IMO use Orangefox recovery which is based on latest twrp with some themes and extras.
3. You are right
4. After installing twrp or similar you need to slide on first run if you want to enable flashing etc.
5. Choose any rom you want
6. Yes Magisk is your only option, if you need root.
However if your device is unencrypted than you don't need to install dmverity. I am also used many AOSP roms on my unencrypted device and faced zero issues.
[emoji3590] from [emoji1191]
Click to expand...
Click to collapse
Hello all
Well I repeated the same steps once again and voila it worked.
Bootloader unlocked successfully and my Mi8 is with Asop pixel experience.
Thanks once again
Hello, I'm new to this world and I've never done anything like this. I'm thinking of installing a custom rom, could you help me? where do i find twrp for my device? what precautions should i take?
Hi. If your device is the Edge 20, i think there is no TWRP available.
From what i understand, you have to use the own recovery build for the rom you plan to use. LineageOS has his recovery. PixelExperience has his recovery as well.
Start with the lineageos and follow the guide to understand how that work