So basically, I got a new Mi Max helium 3 days ago, wanted root, and the most recent stock stable rom. Looked on the threads, guides are not up to date, or are for unlocked bootloaders, or are just plain unclear. SO HERE'S ONE THAT WORKS! (at least for me) I've essentially mashed together a few guides, and found really helpful posts. I'll go step by step for everyone to follow.
Your data will be wiped. proceed with backups (whatever you can do)
1. download MiFlash Beta
2. extract the installer from the downloaded zip
3. install MiFlash Beta (it should install drivers for you.)
I was met with a warning on unsigned drivers or similar. just make sure to select "install anyway"4. download and unzip this prepackaged zip for flashing in MiFlash TWRP 3.0.2.0 for helium.
5. download and unzip the fastboot version of MIUI v8.1.3.0 Global stable for Helium
6. download and unzip recovery flashable MIUI v8.2.1.0 from this thread.
7. download the newest TWRP .img from twrp's site .
I KNOW it says hydrogen, but this official post states it is for both. And if you try looking at the Helium link it doesn't have the latest TWRP. trust me on this one. it works fine. Only download the hydrogen 3.1.0 version.8. download "universal boot.img patcher.zip" from this thread.
9. download latest SuperSU recovery flashable zip.
we need to modify the ROM to be able to work with a locked bootloader as suggested by this post.
10. go to the folder you extracted the prepacked ROM you downloaded in step 6
11. zip up all the files except for the "firmware-update" folder
Now that you've got all the resources, we can go to a version of MIUI that does not have security patches and allows custom recoveries with a locked bootloader, then upgrade from there.
12. Run MiFlash Beta as administrator
13. Turn off your Mi Max Helium
14. hold down Vol + and Vol - on your phone then plug phone to computer via USB while holding the buttons down to enter EDL mode. you should feel a short vibration and then a black(blank) screen.
15. click on the "refresh" button in MiFlash
you should see a new entry for id: 1, device: COM**16. click on the "select" button and navigate to the folder which contains the extracted files of the fastboot MIUI v8.1.3 you downloaded in step 5.
17. click flash and wait for result to show "success"
now we need to re-enter EDL mode to refresh EDL18. hold down Vol + and Vol - and Power buttons on your phone with the USB cable still attached to the computer. again you should feel the vibration and then black screen.
19. refresh MiFlash
you should see a new entry for id: 1, device: COM** again20. click on the "select" button and navigate to the folder which contains the extracted files of TWRP 3.0.2.0 you downloaded in step 4.
21. click flash and wait for result to show "success"
additional info: if you have issues trying to flash, also perform the instructions from this forum post.
22. hold down Vol + and Power button to boot into TWRP recovery. you should feel a slightly longer vibration.
at this point you should see the MI logo and it will take a while before it changes to TWRP's logo. once you see the MI logo you can let go of buttons. if the MI logo only flashes quickly and disappears, then try flashing a older version of MIUI instead.23. when TWRP boots, it will ask, and you should keep system read-only at this point.
24. format the data partition. important
25. check if your preferred method of copying/pushing files can be done from the computer
26. copy/push the newest TWRP img you downloaded from step 7 to /sdcard
27. install the new recovery.img
28. reboot into recovery and keep system read-only
29. flash the prepackaged ROM you modified in step 11
30. flash the boot.img patcher you downloaded in step 8
31. flash latest SuperSU.
32. DO NOT REBOOT.
33. mount /system
34. delete /system/recovery-from-boot.p (or similar)
35. you may reboot now.
36. PROFIT!
Based on the fact that we used a boot.img patcher, theoretically I could use the official latest roms as long as we patch immediately after flashing the recovery version instead. I've not tried this, but you're welcome to.
If you get a softbrick (Mi logo flashes then black screen) just use MiFlash and flash any Fastboot version official rom. (or the v8.1.3 for convenience sake) that'll reset everything.
Thanks to these following guides and threads, and i implicitly hereby thank creators of the prepackages/tools they link to.
[GUIDE]ROOT/TWRP/MULTIROM/Cm13/RR on Locked Bootloader + Hardbrick Recovery by @DoomSlayer
source for boot.img patcher thanks to this post by @avi3230
[ROM] [HELIUM] MIUI 8 Global Rooted by @ajsmsg78
and @Chainfire for SuperSU
I confirm that this does work
Big Thanks
Many thanks for this guide. I followed just about every other guide written to the exact letter but no success at all. The Miflash tools written for the Max (1 click method) didn't work and showed "Specified cast not valid" despite the driver being okay the Mi logo would flash but TWRP would not load if I flashed myself with the newer flash tools beta . Xiaomi never sent me an unlock SMS either and even if they did I might have gotten stuck on 50% anyways
Your guide worked for me 100%. I followed it up to step 30 but then went for LineageOS https://forum.xda-developers.com/mi-max/development/rom-lineageos-14-1-t3529851/post70343167 ROM and Firmware instead of de-bloated MIUI (personal preference) and it worked for me great. A super thanks to all those credited in the OP but especially to shuckeru for making the instructions super clear!
Can i use this guide for my 3 / 32 GB Version ?
What about safety net pass?
Can I ask few noob questions.
1. From step 22 to 36 is the phone must connected to the computer?
2. From step 22 to 36 is it done in the phone and not in the computer?
3. If I restore my phone from MUIU account will this delete the whole process?
Thank you for anyone that answering and I really appreciate it if the answer is in simple language as I'm a noob in this. Thanks.
janmichaelis said:
Can i use this guide for my 3 / 32 GB Version ?
Click to expand...
Click to collapse
Unfortunately no, the resources I've linked are not compatible. If you can find the equivalent resources for your own model you can try it. Most you'll get is a soft brick which is easy to fix.
ankushkushal said:
What about safety net pass?
Click to expand...
Click to collapse
Never tried. Root is more important than safety net. There's no NFC for Android pay and only one dying game uses it, amongst the rest of the banking apps.
kornetbeef said:
Can I ask few noob questions.
1. From step 22 to 36 is the phone must connected to the computer?
2. From step 22 to 36 is it done in the phone and not in the computer?
3. If I restore my phone from MUIU account will this delete the whole process?
Thank you for anyone that answering and I really appreciate it if the answer is in simple language as I'm a noob in this. Thanks.
Click to expand...
Click to collapse
1. No, but you are required to connect the phone to the computer for step 26.
2. Yes, Recovery instructions are done in phone. Except step 26. That is done from your computer.
3. Yes
shuckeru said:
1. No, but you are required to connect the phone to the computer for step 26.
2. Yes, Recovery instructions are done in phone. Except step 26. That is done from your computer.
3. Yes
Click to expand...
Click to collapse
Thank you for answering. If u don't mind I still have a few question, sorry for being noob:
1. In step 16 did u mean fastboot version of MIUI v8.1.3.0? As u mention "download in step 5".
2. At step 26 the phone is still usable/detectable by the computer right? So I can transfer the file from computer to the phone.
3. Everything that I install from step 27 to 31 is it copied at step 26? Because all of the files is still in my computer not in my phone, or should i transfer it to my phone before?
4. So I should delete my back up in my MIUI account, if after twrp and root and then back up the phone in my MIUI account, will this new back up have twrp and root?
Sorry for asking so much and please pardon my English as its not my main language. And Thank You for answering.
kornetbeef said:
Thank you for answering. If u don't mind I still have a few question, sorry for being noob:
1. In step 16 did u mean fastboot version of MIUI v8.1.3.0? As u mention "download in step 5".
Click to expand...
Click to collapse
yes i did. i'll fix that typo
kornetbeef said:
2. At step 26 the phone is still usable/detectable by the computer right? So I can transfer the file from computer to the phone.
Click to expand...
Click to collapse
yes
kornetbeef said:
3. Everything that I install from step 27 to 31 is it copied at step 26? Because all of the files is still in my computer not in my phone, or should i transfer it to my phone before?
Click to expand...
Click to collapse
Yes
kornetbeef said:
4. So I should delete my back up in my MIUI account, if after twrp and root and then back up the phone in my MIUI account, will this new back up have twrp and root?
Click to expand...
Click to collapse
no. its not going to back up twrp and root. you should use nandroid backups.
@ shuckeru
After several hicup and error I finally succeed.
But I still want to ask several confirmation:
1. From step 27 until step 31, I never touch any check box. Is this OK/right?
2. To do step 34, I have to change the setting in recovery from "read only" into "allow modification" to delete the file. Is this right?
3. And in step 34 I delete it with file explorer function in the recovery, is this the right way?
4. When I'm rebooting, instead the normal MI start up loading animation, It was replaced by ring of light animation (like from horror movie). Is this OK.
Other than that everything is OK. Thanks a lot shuckeru. Hopefully will not find any problem.
Again Thank you.
kornetbeef said:
@ shuckeru
After several hicup and error I finally succeed.
But I still want to ask several confirmation:
1. From step 27 until step 31, I never touch any check box. Is this OK/right?
2. To do step 34, I have to change the setting in recovery from "read only" into "allow modification" to delete the file. Is this right?
3. And in step 34 I delete it with file explorer function in the recovery, is this the right way?
4. When I'm rebooting, instead the normal MI start up loading animation, It was replaced by ring of light animation (like from horror movie). Is this OK.
Other than that everything is OK. Thanks a lot shuckeru. Hopefully will not find any problem.
Again Thank you.
Click to expand...
Click to collapse
1. Have no idea what you are talking about.
2. Yes
3. Yes.
4. Yes
Glad I helped you enjoy!
Thank you man! :good:
shuckeru said:
1. Have no idea what you are talking about.
Click to expand...
Click to collapse
I was talking about TWRP interface menu. There is many checkbox and options that should be left alone or should be check when using TWRP menu. For example Don't touch anything else from step 27 until step 31. But in step 34 turn off "read only" checkbox. Maybe u can mention this in the guide to help more user so they can do it more easy than me.
shuckeru said:
Glad I helped you enjoy!
Click to expand...
Click to collapse
Yes Thank You!!!
If u don't mind I have two question:
1. What happen if in Step 7 I use the helium one? The one that is older? Will it give different result?
2. If there will be upgrade in the future like MIUI V8.2.2 do I have to do it from step 1 or from step 29 (that also need to be modify first)?
Again Thank you for making this guide.
jwa88 said:
Thank you man! :good:
Click to expand...
Click to collapse
no problem
kornetbeef said:
I was talking about TWRP interface menu. There is many checkbox and options that should be left alone or should be check when using TWRP menu. For example Don't touch anything else from step 27 until step 31. But in step 34 turn off "read only" checkbox. Maybe u can mention this in the guide to help more user so they can do it more easy than me.
Click to expand...
Click to collapse
really, if i didn't say do something in this guide, don't do it. its a step-by-step guide. if you managed then i've already got my message across. i'm not going to be using pictures for a 34 step guide unfortunately.
kornetbeef said:
If u don't mind I have two question:
1. What happen if in Step 7 I use the helium one? The one that is older? Will it give different result?
2. If there will be upgrade in the future like MIUI V8.2.2 do I have to do it from step 1 or from step 29 (that also need to be modify first)?
Again Thank you for making this guide.
Click to expand...
Click to collapse
1. yes it is older, I can't remember.
2. probably step 1.
i posted the steps that worked for me. i didn't go out of my and try every single combination. there is no need.
shuckeru said:
really, if i didn't say do something in this guide, don't do it. its a step-by-step guide. if you managed then i've already got my message across. i'm not going to be using pictures for a 34 step guide unfortunately.
Click to expand...
Click to collapse
Well its your guide.
shuckeru said:
2. probably step 1.
Click to expand...
Click to collapse
I actually have try once when I screw up the process to restart it from step 29 and its works. The crucial point of this process is the new ROM (and everything else) will need to be installed by TWRP, so in theory if u already have it (TWRP) u can just skip it to step 29. At least its work for me.
shuckeru said:
i posted the steps that worked for me. i didn't go out of my and try every single combination. there is no need.
Click to expand...
Click to collapse
Again is your guide.
Again thanks a LOT fro creating this guide.
I just get update notification for Miui v8.2.3.0. What should I do? If I automatic update it will I lost my ROOT and Twrp?
:good:
Hi,
I made the steps from 1 to 21 exactly as described, but my device won't enter TWRP, with Mi logo flashing and disapearing. I already flashing an older MIUI (8.0.3) as suggested, still with no success. My phone now not even boot in normal mode, only showing mi logo for one second and turning off (soft bricked). However, it still boots in fastboot and EDL modes. Any advices?
Some suggestions /improvements
Thank you friend for this great guide, great job!:good:
I could flash my device successfully after failing in the other ones i have tried.:victory:
I have some suggestions or improvements for your guide.
about the XiaoMiFlash:
1. The name of the flashed files and their path-names should be kept short; otherwise it wouldn't work. thus the names of the files should be renamed and shortened. that means the files "fastboot MIUI v8.1.3" and the " TWRP 3.0.2.0".
2. The flashing should be done quickly. " just seconds from entering EDL mode to hit flash"... that means that step #16 should be done before step #13 or 14. and step#20 should be done before step #18.
http://en.miui.com/thread-325513-1-1.html
3. 2 steps are missing:
to enable step #34. delete /system/recovery-from-boot.p, we first need to uncheck the box Mount> Mount system partition read-only
and after deletion to check it back.
Thanks a lot.....
mailm said:
Thank you friend for this great guide, great job!:good:
I could flash my device successfully after failing in the other ones i have tried.:victory:
I have some suggestions or improvements for your guide.
about the XiaoMiFlash:
1. The name of the flashed files and their path-names should be kept short; otherwise it wouldn't work. thus the names of the files should be renamed and shortened. that means the files "fastboot MIUI v8.1.3" and the " TWRP 3.0.2.0".
2. The flashing should be done quickly. " just seconds from entering EDL mode to hit flash"... that means that step #16 should be done before step #13 or 14. and step#20 should be done before step #18.
http://en.miui.com/thread-325513-1-1.html
3. 2 steps are missing:
to enable step #34. delete /system/recovery-from-boot.p, we first need to uncheck the box Mount> Mount system partition read-only
and after deletion to check it back.
Thanks a lot.....
Click to expand...
Click to collapse
Thanks for your feedback.
1. This isn't an issue unless your path is very very very long. In that case the onus is on you to clean up your environment. I've personally been guilty of that before.
2. I don't believe this is the case for everyone. I left my device in EDL mode for a very long time while I figured what I should flash before flashing and it is fine. I will make a reference to the link just in case. Thanks.
3. That's step 33. You also don't have to return it to read only. That's redundant
Related
Guys don't use this guide for now, don't use official unlocking method for now..
TO flash the CM12.1 in your Zf2 you must unlock the bootloader [WARNING: it will void the warranty]
I'm not responsible for bricked phone,try on your own risk
and official ASUS warning for unlocking bootloader ,its long so read it by clicking show content
Before you download, install, and use the Unlock Device App you acknowledge and assume complete risk to the quality and performance of this App, including but not limited to the following: once you activate the App you will not be able to recover your ASUS product (“Original Product”) back to original locked conditions; the Original Product with the activated App will not be deemed the Original Product; the Revised Product will no longer be covered under the warranty of the Original Product; the software of Revised Product will no longer be deemed the software of the Original Product and can no longer receive ASUS software updates; your purchased digital content may also be affected.
You also acknowledge ASUS does not guarantee service satisfaction to any Revised Product, including events involving paid service requested by you to be performed to the Revised Product.
Furthermore, such repaired Revised Product will not be covered under the warranty of the Original Product; the software of the repaired Revised Product will not be deemed the software of the Original Product and will not receive ASUS software updates.
It is strongly advised that you avoid activating this App unless you fully understand and accept the risks that may arise.
What this guide giving steps for:[just more like summary]
Files Needed and Required before Steps: - Just basic drivers to activate adb,fastboot system wide
Steps For Flashing CM12.1 : - unlocking bootloader, flashing twrp recovery and then flashing CM12.1,gapps and supersu.zip
Files Needed and Required before Steps:
Drivers for Asus Zenfone 2 installed on PC from here [mostly it will auto installed]
ADB installed on your PC (https://drive.google.com/file/d/0B0MKgCbUM0itVVFWRC02Q0VBQnc/view?pli=1),download and install this
And some more,which will be mentioned below
Steps For Flashing CM12.1 :
unlock bootloader instructions:
Update your software image to V2.20.40.59 or latest version
download app for ZE551ML[all 2gb,4gb] here and for ZE550Ml here
install, and use the Unlock Device App downloaded from above step
Download untethered twrp from here (zooa is for all ze551ml,z008 is for ze550ml),
if the .img you just downloaded doesnt have name as twrp.img [it may have version along it] then please rename that to twrp.img[remove those versions] and turn off ur phone, plug the usb cable in ur phone port,hold the VOL UP[no need to press the power] and connect the other end of cable to PC port,wait for few seconds till the green Android robot appears. You should see a blue line below saying "Waiting Fastboot command or Continue the fastboot process"
select the folder where you are having the twrp.img by pressing Shift + Right Click.. Then select "Open command here"...[in case you are wondering where and how see pics here or here]
Copy and paste the following command in the command prompt window
Code:
fastboot flash recovery twrp.img
after it finish the flashing[it will take less than 10sec only],u can unplug the phone, boot the phone.
download CM12.1 latest version or nightly from here [NOTE:see the date of the build to know the latest version]
get the gapps from here
get the supersu.zip from here
after downloading all zips,..place all in your micro SDCARD
now power off, Once it is off, hold down the volume up button and hold on to the power button until the phone vibrates. After the vibration stops, release the power button and continue pressing the volume up button until the green Android robot appears. You should see a blue line below saying "Waiting Fastboot command" ,Now here click vol down till you see Recovery mode in top big rectangle box,click power button
it will enter twrp,first take the backup of ur current OS[tick everything], choose sdcard for backup,so u can restore if u want to use stock at some point[even the apps will be there,but if you kept the obb,data in internal,it will be wiped,so better copy android folder to pc]
now click wipe,click advanced wipe,select everything except the microsd [be careful],if u want to keep the internal files,then untick internal storage also
Click the install,choose externalSD, search for those zip,and install CM.zip ,then install Gapps.zip,then supersu.zip,now reboot..
Enjoy the CM12.1 in ZF2
For bugs ,discussion please goto Main Thread: here
BUGS: here
Credits : there are lot of ppl who contributed to have CM12.1 in zf2 than those who i mentioned below,thanks for them also..
@sorg for new unlocked bootloader without root
@shakalaca for old unlocked bootloader with root
@ravian29 for unlocking guide
@TheSSJ for TWRP ,thread is here
@jrior001 , @crpalmer , @hharte for CM12.1
This ROM is only for the Z00A?
Sent from my ASUS_Z008D using Tapatalk
Added to index, thanks for your work!
GreatItami said:
This ROM is only for the Z00A?
Sent from my ASUS_Z008D using Tapatalk
Click to expand...
Click to collapse
551ml (z00A and z00ad)
For now not supported for 550ml..
Okay. Nice tutorial.
Sent from my ASUS_Z008D using Tapatalk
OK, so far I'm unlocked. But, I'm stuck on step 3 - select the folder where you are having the twrp.img by pressing Shift + Right Click.. Then select "Open command here"
EDIT:Got it! I had to open the actual folder first with TWRP in it (adb is where I put it) in my C drive then the right click + shift works as you said within the folder - thanks so much for this tutorial!
Is it neccessary to be on 2.19.40.22? There wasn't much of a difference between 2.19.40.20 and 2.19.40.22. Would I have to flash the OTA then flash CM? Also, do you recommend wiping cache/dalvik after flashing GAPPS just in case?
PS: Thank you Ansebovi! All your guides are easy to read and follow.
texla said:
OK, so far I'm unlocked. But, I'm stuck on step 3 - select the folder where you are having the twrp.img by pressing Shift + Right Click.. Then select "Open command here"
EDIT:Got it! I had to open the actual folder first with TWRP in it (adb is where I put it) in my C drive then the right click + shift works as you said within the folder - thanks so much for this tutorial!
Click to expand...
Click to collapse
I did it by downloading Terminal for Android and putting the image on the internal storage and then opening Terminal and did this
su
dd if=/sdcard/twrp.img of=/dev/block/by-name/recovery
reboot recovery
CM12 zip is downloading really slow...i know its only 350mb but is going at barely 45kb/s ..is this normal? i know its not my connection -.-
texla said:
OK, so far I'm unlocked. But, I'm stuck on step 3 - select the folder where you are having the twrp.img by pressing Shift + Right Click.. Then select "Open command here"
EDIT:Got it! I had to open the actual folder first with TWRP in it (adb is where I put it) in my C drive then the right click + shift works as you said within the folder - thanks so much for this tutorial!
Click to expand...
Click to collapse
http://forum.xda-developers.com/attachment.php?attachmentid=3419717&stc=1&d=1437962670
http://forum.xda-developers.com/attachment.php?attachmentid=3419716&stc=1&d=1437962670
both works
Ntrasme said:
Is it neccessary to be on 2.19.40.22? There wasn't much of a difference between 2.19.40.20 and 2.19.40.22. Would I have to flash the OTA then flash CM? Also, do you recommend wiping cache/dalvik after flashing GAPPS just in case?
PS: Thank you Ansebovi! All your guides are easy to read and follow.
Click to expand...
Click to collapse
i updated from .20 and i had the mtp bug which others didnt have,..so i think its better to have .22 , try with .20 and look for bugs..only problem,u cant report the bug to them,since they are seeing with .22
cjvzla said:
CM12 zip is downloading really slow...i know its only 350mb but is going at barely 45kb/s ..is this normal? i know its not my connection -.-
Click to expand...
Click to collapse
no i downloaded the zip with 700KBps-1MBps ,definitely no problem from their side
ansebovi said:
http://forum.xda-developers.com/attachment.php?attachmentid=3419717&stc=1&d=1437962670
http://forum.xda-developers.com/attachment.php?attachmentid=3419716&stc=1&d=1437962670
both works
i updated from .20 and i had the mtp bug which others didnt have,..so i think its better to have .22 , try with .20 and look for bugs..only problem,u cant report the bug to them,since they are seeing with .22
no i downloaded the zip with 700KBps-1MBps ,definitely no problem from their side
Click to expand...
Click to collapse
OK, thank you. BTW do you know if TWRP can sideload the ota zips? Is there a conflict if I use ProjectT kernel while sideloading OTA? You are more knowledged than me.
ansebovi said:
TO flash the CM12.1 in your Zf2.....
Click to expand...
Click to collapse
...wow this a great rom
excuse me for asking but is this already running in 64bit mode?
or it is still 32bit?
Thanks. Worked flawlessly.
berlyshells said:
...wow this a great rom
excuse me for asking but is this already running in 64bit mode?
or it is still 32bit?
Click to expand...
Click to collapse
they used asus stock .22 latest update as base,so it should be x86 till the asus release x64bit and Cm updated to that firmware ...
Ntrasme said:
OK, thank you. BTW do you know if TWRP can sideload the ota zips? Is there a conflict if I use ProjectT kernel while sideloading OTA? You are more knowledged than me.
Click to expand...
Click to collapse
ota have patch for boot and recovery,..not a gud idea to flash ota with twrp,custom kernel...it may end up in failure
hi, finished downloading needed files, unlocked bootloader succesfully (white splash screen) , rooted, and installed unthetered twrp just like in the steps, however, when i tried to enter recovery for the first time just showed android on the floor with ERROR and red triangle logo...nothing happens so just rebooted and wating for a tip...thanks.
EDIT: sorry i did not read the same problem being resolved on page 1... got twrp running now.
Bro is there any bugs ? Please post bug list
himesh1994 said:
Bro is there any bugs ? Please post bug list
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=62014498&postcount=2
btw dont quote the whole op anywhere in xda please..edit ur post and delete the quote
Ntrasme said:
Is it neccessary to be on 2.19.40.22? There wasn't much of a difference between 2.19.40.20 and 2.19.40.22. Would I have to flash the OTA then flash CM? Also, do you recommend wiping cache/dalvik after flashing GAPPS just in case?
PS: Thank you Ansebovi! All your guides are easy to read and follow.
Click to expand...
Click to collapse
sry i forgot to answer the other qn before...no need to wipe cache after installing gapps as we wiping before the installation of both
and thanks for compliment
ansebovi said:
http://forum.xda-developers.com/showpost.php?p=62014498&postcount=2
btw dont quote the whole op anywhere in xda please..edit ur post and delete the quote
sry i forgot to answer the other qn before...no need to wipe cache after installing gapps as we wiping before the installation of both
and thanks for compliment
Click to expand...
Click to collapse
OK, thanks. Now to go on the long process of resetting everything so I can apply OTA. Restore stock recovery, restore stock kernel, unfreeze apps, uninstall framework, uninstall busybox, unroot.
Ntrasme said:
OK, thanks. Now to go on the long process of resetting everything so I can apply OTA. Restore stock recovery, restore stock kernel, unfreeze apps, uninstall framework, uninstall busybox, unroot.
Click to expand...
Click to collapse
haha ,thats really headache ... btw use manual ota for safety
For 500CL ?
I can't wait for this rom for the 500cl Zenfone 2. The original rom is awful, with the huge amount of bloatware any so many bugs ! Any chance to have this rom for the zenfone 2 500cl ?
****** I DO NOT TAKE ANY RESPONSIBILITY FOR ANY BRICKS/BOOT LOOPS/Mi LOGO BRICK. I AM SHARING THE STEPS THAT I HAVE USED AND YOU USE THESE STEPS AT YOUR OWN RISK ******
Use Android Image Kitchen to decompress and Recompress.
Unzip the whole Kitchen and ROM files through 7 Zip * mode.
Copy the "boot.img" to the Android Kitchen Unzipped Folder.
Follow the following steps:
Step 1. Decompress the boot.img file through Android Image Kitchen (unpackimg.bat)
Step 2. Open the file "fstab.qcom" via notepad / notepad++.
Step 3. Remove the ".verify" from it and save the file. Do not change the file extension. (Though it should not ask/or do). (This unlocks bootloader over server).
Step 4. Open default.prop via notepad / notepad++.
Step 5. Change "ro.secureboot.devicelock=1" to "ro.secureboot.devicelock=0" (This unlocks the bootloader).
- Additional Amendments if you want, like enabling adb, debug, etc, then do Step 6, else go to Step 7. STep 6 somehow seems to have some error on WiFi access. In case you do not want that, do not perform Step 6. a. and 6.b.,.
Step 6. Change:
a. "ro.secure=1" to "ro.secure=0"
b. "ro.adb.secure=1" to "ro.adb.secure=0"
These enable OEM Unlock over Server and over Developer mode.
c. "ro.debuggable=0" to "ro.debuggable=1".
This turns on USB Debug.
d. "persist.sys.usb.config=none" to "persist.sys.usb.config=adb"
This turns on ADB mode.
e. "persist.sys.timezone=Asia/Shanghai" to "persist.sys.timezone=Asia/XXX".
One can set the default locale from here. (This does not seem to work on Beta ROM's, as the server denies setting locale). (Though it should not ask/or do).
- Save the file. Do not change the file extension.
Step 7. Recompress these files back through repackimg.bat."
A new file "image-new.img" will be created. Rename the file to "boot.img" and replace the same to the unzipped folder of the ROM.
You now have a cooked/modded boot.img within the ROM, and your device is bootloader unlocked. Now Flash the ROM through MIFlash.
Also note: Rename the TWRP/Custom Recovery image to "recovery.img" and replace it with the Stock Recovery within the ROM. Now you have Custom Recovery ROM.
These steps take no more then 5-6 minutes, and are pretty easy.
Happy Flashing.
N.B.: I have attached the Android Kitchen File here.
Is this equivalent to unofficial unlock or the official one?
BlueJeans said:
Is this equivalent to unofficial unlock or the official one?
Click to expand...
Click to collapse
Actually None. I mean not the official, nor the unofficial one.
I am on unlocked bootloader myself.
These are the steps I did to unlock my bootloader.
I have even rooted my RN3QC within 10 days from purchase.
I just wanted to unlock and have even custom TWRP 3.0.2-2.
can miflash just flash the boot.img?
meangreenie said:
can miflash just flash the boot.img?
Click to expand...
Click to collapse
Nope, I tried, and it went to bootloop once and second time to mi logo.
The easiest way to install the boot.img and the recovery.img are:
If you want TWRP to be your recovery and that too after flashing the ROM, I will ask you to replace the default recovery file within the unzipped ROM with the TWRP Recovery File. The default recovery path is within the images folder and called recovery.img.
Just rename the TWRP Recovery image file to recovery.img and replace it in images folder, and flash through MIFlash. Done.
And if you want to flash boot.img, then flash through TWRP. That is the easiest method.
Safe and no bricks.
N.B.: FYI: Few Stable ROM's have a verity check on even after official unlock. That just means that the server has not yet updated their unlock, and if it is not done manually, then it will remain locked on server.
Nice tutorial , this will be helpful to those people who are still stuck on 50% error ,Good work !
NVDX11 said:
Nice tutorial , this will be helpful to those people who are still stuck on 50% error ,Good work !
Click to expand...
Click to collapse
Hope that moderator is not here too.
vdbhb59 said:
Hope that moderator is not here too.
Click to expand...
Click to collapse
Haha , yep :laugh:
So this should work on redmi 3s too ? gonna give it a try now. thanks dude.
Btw are you the guy who got banned on miui forum ? i had bookmarked a post similar to this but when i actually got time to read it, it was deleted by mod.
Edit : does not work lol, was stuck on Qualcomm HS-USB Diagnostics 900E mode, and couldn't get it to fasboot/edl mode. tried many different key combinations and and now finally got it fixed. so i guess it works only on RN3. now gotta wait for them to fix their db.
kraatus90 said:
So this should work on redmi 3s too ? gonna give it a try now. thanks dude.
Btw are you the guy who got banned on miui forum ? i had bookmarked a post similar to this but when i actually got time to read it, it was deleted by mod.
Edit : does not work lol, was stuck on Qualcomm HS-USB Diagnostics 900E mode, and couldn't get it to fasboot/edl mode. tried many different key combinations and and now finally got it fixed. so i guess it works only on RN3. now gotta wait for them to fix their db.
Click to expand...
Click to collapse
R3S it should not work, and as you confirmed it does not work.
Yes I am thr guy whose post got deleted, and the Mod is still adamant on saying it does not unlock bootloader.
They have changed the method to unlock on MM, so this apparently is only for LP.
vdbhb59 said:
Step 6. Change:
a. "ro.secure=1" to "ro.secure=0"
b. "ro.adb.secure=1" to "ro.secure=0"
These enable OEM Unlock over Server and over Developer mode.
Click to expand...
Click to collapse
Noob question, due to I need to ensure something.
Point 6.b.
It is correct, change "ro.adb.secure=1" to "ro.secure=0"
Since this is different command.
Anyway, thanks for your share.
abihary said:
Noob question, due to I need to ensure something.
Point 6.b.
It is correct, change "ro.adb.secure=1" to "ro.secure=0"
Since this is different command.
Anyway, thanks for your share.
Click to expand...
Click to collapse
Thanks for pointing this out bro. My typing error.
It is ro.adb.secure
vdbhb59 said:
Thanks for pointing this out bro. My typing error.
It is ro.adb.secure
Click to expand...
Click to collapse
You're welcome. I need to share this simple way to my friend, thats why i read it carefully to avoid any problem. For myself, already unlocked few weeks ago.
Anyway, thanks for your feedback.
abihary said:
You're welcome. I need to share this simple way to my friend, thats why i read it carefully to avoid any problem. For myself, already unlocked few weeks ago.
Anyway, thanks for your feedback.
Click to expand...
Click to collapse
Any day welcome.
For kenzo or hennessy?
zenex01 said:
For kenzo or hennessy?
Click to expand...
Click to collapse
For kenzo
zenex01 said:
For kenzo or hennessy?
Click to expand...
Click to collapse
Kenzo and unfortunately currently limited to LP.
Searching for MM and N pattern to unlock.
What MIUI version you using? @vdbhb59
I tried with 7.3.2.0 after flashing then check bootloader but still locked. I skip step 6.
MiripRedmoon said:
What MIUI version you using? @vdbhb59
I tried with 7.3.2.0 after flashing then check bootloader but still locked. I skip step 6.
Click to expand...
Click to collapse
I am on 6.9.9 Global Beta. I had unlocked when I was on 6.8.18 Global Beta.
You need to check the steps properly, or if you want, attach your boot.img filehere, and I will change and reattach it here for you.
vdbhb59 said:
I am on 6.9.9 Global Beta. I had unlocked when I was on 6.8.18 Global Beta.
You need to check the steps properly, or if you want, attach your boot.img filehere, and I will change and reattach it here for you.
Click to expand...
Click to collapse
So you are back to a locked bootloader when you moved to 6.9.9?
And for doing that you just flashed the fastboot tgz file in edl mode?
Btw, overall comment -> u mean to say .. using this process there is no need to replace/ flash the modded emmc_appsboot.mbn file?
Hi to everybody
I'm doing this thread because I've seen that there's a lot of confussion about how to install all this things properly, and I think that concentrating the wide-spread information could help you to get rid of this. First of all I have to thanks @aaawqw and @Moyster for their great efforts.
This is going to be a recopilatory of several sources and personal tips to help you to do this the easiest way. I'm not responsible of bricked phones nor your personal problems.
Please, read the full tutorial before doing anything, to avoid bricks and those things.
PREPARE THE RECIPE
Download these files:
- Unlocking bootloader tool: HERE
- TWRP image from Moyster (creator of LOS14 for our device): here
- If you want to install a modified version of FlymeOS, use this one from Romul35 from 4PDA: here. Original post
- Last LineageOS 14 build: from this thread. PLEASE DON'T FORGET TO THANK THE DEVELOPERS
- GApps: here I recommend the nano option. Choose ARM64 and Android version 6.0.
Put those three last files into your internal memory. If you've got an microSD card, I recommend you to put them into it (it's safer and easier).
UNLOCKING THE BOOTLOADER
To unlock the bootloader go to:
- Kevin.MX @aaawqw) post: here
Finally we have a guide to unlock the bootloader of Meizu m2 note. We need Mediatek SP Flash Tool, MTK phone drivers and the images/bin files for unlocking. No modaco superboot, no fake tutorials any more
Now here's the guide:
1. Download the files I provide
Then unzip it. You'll get a folder with FlashTool, Phone drivers and unlock images.
2.Install drivers for Mediatek platform.
3.Flash the temp-unlock-secro.img via Flashtool. (secro row)
4.Flash secro.img, lk.bin, preloader_meizu6753_65c_l1.bin via Flashtool. (secro, lk and preloader rows respectively)
5.Disconnect USB data cable and power on the phone. If you see the "=>Normal boot" sign(it's quite small.......) in the left bottom cornor of the screen, then the unlock is done. You can now flash things in whatever way you like. The guide is over~~~
The full tutorial is here
The unlock tool is here
Thank you for testing&trying!
If you've seen this spoiler and didn't thank Kevin, please go to here and thank him. This motivates him and gives him the recognisement he deserves.
- Robot Hijau 97 Youtube video: here It isn't in English, but may help if you find any problem or get lost during the unlocking. Leave him a like if it helped you.
This unlocking guide only works for M571 model. If you try this with a M571C (China Telecom) model, you'll get a bricked phone (very useful if you like paperweights )
THIS METHOD DOES WORK FOR M571H MODEL. DON'T WORRY, THE ONLY ONE THAT GIVES SOME ISSUES IS THE M571C.
The great user @aaawqw states "And Meizu M571C should use the same method of meizu m2 (mini), a shell script for frp unlock. But no recovery images yet…Different hardware and partitions"
Tips to unlock the bootloader easily:
- If you're going to do it from a Windows 10 or 8 pc, have in mind that to install unsigned drivers you'll have to unlock the feature in your pc. A guide to do this: here
- Select the images to flash and hit the Download button before connecting your Meizu (pressing Vol Down button). This will help you if it turns on and off and makes the flashing impossible.
- Download the guide or see the video to correctly follow all the steps. You don't want to lose your phone, don't you? Don't try to mix guides, because you may skip a step and brick your phone. The video and Kevin.MX guide are the same procedure, they both are safe.
INSTALLING TWRP
Once done this part, we'll proceed with the installation of TWRP recovery image. There are two ways, choose the easier to you:
- Flash TWRP from SP Flashtool (original idea from @widagdag. The post: here)
+Turn off your device
+ By using your pc or laptop, extract the TWRP zip for meizu m2 note, there's a file "recovery.img"
+ You can flash it via SP flash tool (clicking the recovery, then select the file)... then click Download, wait until finished!! (Check symbol)
+ You can reboot ur device now, unlocked bootloader and installed twrp!
*The profit is u didn't need to root first and install any flash tool such as Rash, FlashFire, Flashify, etc. saving you some time
Click to expand...
Click to collapse
- Flash the recovery image from Flyme:
+ Get root access (if you do, skip this step). You can get it downloading Kingroot: here. Just install this apk and follow the steps
+ Unzip TWRP zip into a known folder
+ Download Flashify from the Playstore
+ Grant superuser access
+ (Optional) make a backup of your current recovery going to backup tab
+ Tap Recovery Image
+ Choose a file
+ Find TWRP img that you unzipped before and flash it
Click to expand...
Click to collapse
INSTALLING CM AND GAPPS
We're close to the end of this post. The final step: installing your desired ROM and GApps. I will flash CM from the thread whose link is at the download section.
I hope you've put it into your memory (internal/external) as we said
Ok so:
- Turn off your phone
- Go into the TWRP recovery (Vol up+power)
- (Optional but recommended) Make a backup of Flyme, just in case you don't like the new ROM and would like to go back to Flyme. If it takes up too much memory, move it to your pc after making the backup.
- Go to Wipe menu
- Go to advanced wipe
- Select these:
+ System
+ Cache
+ Dalvik Cache
+ Data
- Swipe to do the wipe
- Go to install.
- Select your zip image (in my case the cm13 I downloaded).
- Install also the GApps zip file you downloaded
- Restart to System, and check what you've done.
Some final tips:
- Make the backup, seriously, it takes 10 min and you'll have a Flyme backup if you don't like CM.
- If you want to transfer all your apps and their data from Flyme to your new ROM, use Titanium Backup.
- If you want to install Xposed Framework, it's the same procedure: enter into TWRP, tap install, select the zip and swipe.
- This won't delete your images or videos, but I would recommend to transfer them to a microSD card or your PC.
- Yes, you need to do all this to install a custom ROM. Yes, even unlocking the bootloader. Don't try to skip a step if you aren't sure about what you're doing.
I think that's all, I'll update this post if I lost anything.
I hope this helped you to move into CM world. If you have any doubt don't hesitate to ask.
I know this seems exhausting, but trust me, it worths it. Welcome to the custom ROMs world in your Meizu M2 Note. Let the magic begin.
ADDITIONAL GUIDES
RELOCKING THE BOOTLOADER
If you want to relock the bootloader just follow this simple steps:
Flash the original recovery image from Flashtool of from Flashify (the steps are the same as installing TWRP). You can find this image here
From there, install an update.zip (download them from the official flyme web: here and put it into the storage )
Now you have flyme again with a locked bootloader.
INSTALLING FLYME WITH TWRP
It's very important that you don't install an update.zip from the original Flyme page, because you will cause a bootloop. To get the flyme updates, you can follow one of these two methods:
METHOD 1: 4PDA
-Download the modified zips from 4PDA: here]. Translate it to English. It's on custom firmware>Flyme
-Flash them from TWRP
METHOD 2: DO IT YOURSELF
-Download the update.zip file from the Flyme page
-Open it and remove the preloader- files
-Flash it from TWRP. It will give you an error: IGNORE IT.
Reboot and done, you've got Flyme and TWRP.
UNBRICK A PAPERWEIGHT
BIG THANKS TO @numpea FOR THIS:
This just a firmware that has all the partitions and can be used to unbrick to device using SPFlashtool
Here is the link:
FIRMWARE
- Flash temp_unlock_secro.img with sp flashtool like you do when unlocking the bootloader.
- When done, disconnect the device and add the firmware to sp flashtool. You need to select "format all+download", click on "Download" and connect the device. The flashing process will start. After it finishes, the device will start again.
You wil notice that you lost your imei number you can add it back by:
Using MTK Engineering Mode (does not requires root)
Open engineering mode » Click on Engineer Mode (MTK) » Swipe left to Connectivity » click on CDS Information » Radio Information
Click on phone 1 if you want to change your sim 1 or choose Phone 2 to change sim 2 IMEI, follow this guide:
For Phone 1: “AT+ EGMR=1,7,â€YOUR NEW IMEI NO†(make sure you add a space in between AT+ & EGMR)
For Phone 2: “AT+ EGMR=1,10,â€YOUR NEW IMEI NO†(make sure you add a space in between AT+ & EGMR)
Using Chamelephon (requires root, but much more easier)
Just copy the IMEIS from the phone's box and put them into the app.
hope this is helpful
Click to expand...
Click to collapse
I'll keep updating the info!
Really complete, I could unlock my M2 Note and install CM-12.1 ! Thanks !
Moyster said:
Really complete, I could unlock my M2 Note and install CM-12.1 ! Thanks !
Click to expand...
Click to collapse
Moyster xDD :laugh::laugh: Thanks to you, without you this wouldn't have been possible
Pretty much covered all, just state the Armv7 Android level API 21 64bit, 5.1 Micro or Nano for gapps. They might get confused on what to choose.
Xtian Rey said:
Pretty much covered all, just state the Armv7 Android level API 21 64bit, 5.1 Micro or Nano for gapps. They might get confused on what to choose.
Click to expand...
Click to collapse
Very true, thanks a lot. I introduced the platform and the Android version of GApps
Thanks nice guide... Very useful for everyone who want play and modified the M2 note.
"This unlocking guide only works for M571 model. If you try this with a M571C (China Telecom) model, you'll get a bricked phone (very useful if you like paperweights*)"
I Am Using M571C, But Everything Fine.
Sent from my M2 Note using XDA Forums Pro.
Mr0oHo0 said:
"This unlocking guide only works for M571 model. If you try this with a M571C (China Telecom) model, you'll get a bricked phone (very useful if you like paperweights*)"
I Am Using M571C, But Everything Fine.
Sent from my M2 Note using XDA Forums Pro.
Click to expand...
Click to collapse
I include this on the guide. I read it bricked the phone in several cases, but I'm glad yours didn't.
Thanks for your guideline , it helps a lot !
Great work lol
Another thing is…ShevT's recovery has no problem in cache partition.Only my broken recovery did… So remove the cache fixing partAny problem just send me a private message. I'll check when i have time.
---------- Post added at 04:00 PM ---------- Previous post was at 03:58 PM ----------
And Meizu M571C should use the same method of meizu m2 (mini), a shell script for frp unlock. But no recovery images yet…Different hardware and partitions…
Another thing is, Kingroot is not suggested. It cannot be detected by Flashfire and some other tools. And cannot be replaced by SuperSU. So Kingo Root+SuperSU might be better.
aaawqw said:
Great work lol
Another thing is…ShevT's recovery has no problem in cache partition.Only my broken recovery did… So remove the cache fixing partAny problem just send me a private message. I'll check when i have time.
---------- Post added at 04:00 PM ---------- Previous post was at 03:58 PM ----------
And Meizu M571C shoukd use the same method of meizu m2 (mini), a shell script for frp unlock. But no recovery images yet…Different hardware and partitions…
Click to expand...
Click to collapse
https://github.com/Moyster/android_device_meizu_m2note/blob/cm-12.1/BoardConfig.mk#L10
Line 10 to 15 you have the partitions size
Code:
$ cat /proc/partinfo
example :
Name------------Start-------------Size
recovery 0x0000000004840000 0x0000000001400000
Take the Size value : "0x0000000001400000" => hexadecimal to decimal => 20971520 = recovery partition size
PS: I don't think the hardware is "that" different, at least, the kernel meizu released should contain both phone models/drivers
This unlocking guide only works for M571 model.
Click to expand...
Click to collapse
Mine is M571H, can I proceed?
Qeemi said:
This unlocking guide only works for M571 model.
Mine is M571H, can I proceed?
Click to expand...
Click to collapse
Mine too and it worked. I can't assure you anything, but I think that the problem are m571C which are different. Good luck if you're going to give it a try!
Moyster said:
https://github.com/Moyster/android_device_meizu_m2note/blob/cm-12.1/BoardConfig.mk#L10
Line 10 to 15 you have the partitions size
Code:
$ cat /proc/partinfo
example :
Name------------Start-------------Size
recovery 0x0000000004840000 0x0000000001400000
Take the Size value : "0x0000000001400000" => hexadecimal to decimal => 20971520 = recovery partition size
PS: I don't think the hardware is "that" different, at least, the kernel meizu released should contain both phone models/drivers
Click to expand...
Click to collapse
See it. I'll give a try on m2 note(M571C, China Telecom). At least try to build twrp But seems my pc's hdd is not enough No space for source code
little problems.
bootloader unlocking and twrp and roms works very well..
1. OTG is working for me.. :good:
2. unfortunately my phone is not detected by PC..
(show USB is not connected, USB debugging is not accessible..)
3. little bit lag here and there..
4. wifi works well :good:
Need more optimization.. Expecting lot more from you
thankyou very much for this :good:
DOUBT : so bootloader is unlocked, now it is possible to make good MM and N based CM roms ?
dinkan01 said:
bootloader unlocking and twrp and roms works very well..
1. OTG is working for me.. :good:
2. unfortunately my phone is not detected by PC..
(show USB is not connected, USB debugging is not accessible..)
3. little bit lag here and there..
4. wifi works well :good:
Need more optimization.. Expecting lot more from you
thankyou very much for this :good:
DOUBT : so bootloader is unlocked, now it is possible to make good MM and N based CM roms ?
Click to expand...
Click to collapse
hi,which build of cm 12 you put in phone?
M571U
I have the Meizu M571U Model. Can I do this or will it be bricked?
Thank you very much
venturaj said:
I have the Meizu M571U Model. Can I do this or will it be bricked?
Thank you very much
Click to expand...
Click to collapse
It won't, the only problematic model is the M571C, have fun
LBA97 said:
It won't, the only problematic model is the M571C, have fun
Click to expand...
Click to collapse
How can I check which model my m2 note is..?
[email protected] said:
How can I check which model my m2 note is..?
Click to expand...
Click to collapse
Check the store page you bought it from. If you bought it from China, then probably it's a M571C. Good luck
Ok here's what I did. To keep my data and twrp when upgrading from "P" to " Q".
1. I downloaded the OTA zip file.
2. Extracted it on your phone.
3. Edit the "Flash-all.bat" file
A. Delete "-w" from one of the last command lines.
B. Add "reboot-bootloader"
"fastboot boot twrp-3.2.3.1-marlin.img"
C. Hit "save"
C. Both the above command lines should be right
before the line "echo press any key to exit"
4. Add the twrp.img to the folder with the above extracted contents.
5. Edit "flash-all.sh" to read the same as you have just edited the "flash-all.bat" file. And then hit "save".
6. Compress the extracted file so as to create a .zip file again.
7. Move this .zip file to your PC.
8. Plug up your phone to your PC and make sure android debugging is active.
9. On your PC extract the .zip file you just created.
10. Make sure you have the twrp installer zip on your phone.
11. Go into the extracted .zip file and double click the "flash-all.bat" windows batch file and sit back and wait.
12. When it finishes it will boot up. 1 out 3 times I tried this it booted then immediately rebooted to the stock recovery with an error saying that my data may be corrupt and if I see this message again then perform a factory reset. And gave me to options "try again" and "factory reset". I clicked "try again". It then booted normally.
13. Power off your phone.
14. While holding vol down press and hold power button for a few seconds and then release the power button but NOT the vol down button. This will put you in bootloader mode.
15. Once in bootloader mode it will then boot twrp.
16. Once once twrp loads click install then navigate to the folder you put the twrp installer.zip and flash the installer. 17. Hit "reboot system"
18. Sit back and wait.
19. All your data will remain on the phone. All your settings stayed the same.
***********NOTICE ***********
1. YOUR BOOTLOADER MUST BE UNLOCKED. IF YOU DONT KNOW HOW TO DO THAT THEN YOU SHOULDNT BE ATTEMPTING THIS. ESPECIALLY IF YOU ASK ME HOW TO UNLOCK YOUR BOOTLOADER.
2. I TRIED THIS 3 DIFFERENT TIMES WITH THE SAME RESULTS. I will post pics of the step by step process later. Just wanted to go ahead and get this out there so those of you who know your way around an android could do it.
3. I AM NOT RESPONSIBLE FOR YOUR ACTIONS.
I AM NOT RESPONSIBLE FOR YOU F'ING THIS UP AND NOT FOLLOWING INSTRUCTIONS TO A "T".
4. THIS IS RISKY BUT IF YOU FOLLOW INSTRUCTIONS CAREFULLY YOU SHOULD HAVE NO ISSUES.
Im also posting a pic of my about phone to show I am indeed on "Q" and that this worked for me.
Hope you enjoy
Be patient I'll have step by step screen shots posted in a little bit of the process. To maybe make it easier to understand.
Could this work for official android 10
Very nicely explained, thank you.
Please excuse me if this is a stupid question, but why not just extract and edit on your PC instead of on the phone then transfer to PC?
Did you try flashing magisk?
Thanks for letting us know latest twrp works. But did you try to get root @mattwheat ? I am too afraid to lose data so didn't flash magisk yet.
All I did was manually flash bootloader, radio, system and vendor and it kept all my data with working twrp and root (coming from pie custom rom).
sinkoo1979 said:
All I did was manually flash bootloader, radio, system and vendor and it kept all my data with working twrp and root (coming from pie custom rom).
Click to expand...
Click to collapse
So you didn't even wipe anything? You just booted into TWRP and manually flashed the files? I'm also on a 9 custom ROM and would love to know the best/safest way to make the move to 10
johnblundon said:
So you didn't even wipe anything? You just booted into TWRP and manually flashed the files? I'm also on a 9 custom ROM and would love to know the best/safest way to make the move to 10
Click to expand...
Click to collapse
no wipes
Flashed through fastboot.
Steps:
flash bootloader
reboot to bootloader
flash radio
reboot to bootloader
flash system
flash vendor
reboot to system
I was missing OTA function in settings.....
it work for me but can't guarantee it will work for everybody. Best way is to try it.
flashed q beta and went back to pie customs roms by flashing bootloader, radio, and vendor (before official q was released). Have to download all apps but internal storage stayed intact.
salpsuc said:
Very nicely explained, thank you.
Please excuse me if this is a stupid question, but why not just extract and edit on your PC instead of on the phone then transfer to PC?
Click to expand...
Click to collapse
You're welcome. And sure you could do that I would imagine. May be easier but then I would be explaining a method I did not actually try. And that would suck if by chance some ones phone caused world's to collide. I would feel pretty bad about that. Unless the end result was Nancy pelosi shutting up and resigning.
rahil3108 said:
Thanks for letting us know latest twrp works. But did you try to get root @mattwheat ? I am too afraid to lose data so didn't flash magisk yet.
Click to expand...
Click to collapse
I did not have root after flashing twrp.... Seems like, looking back, that I tried and seems like it may have said "successful" but it didn't stick upon reboot. But I imagine it's neither here nor there cuz y'all prolly have root by now...
This guide is now obsolete. Please check my new guide. It has a custom recovery for this device as well as a rooting guide. Refer to this guide only for installing adb and unlocking bootloader.
This rooting guide is for the Lenovo Tab M10 X505X only.
I plan to work on a custom recovery for this tab as well and probably a custom rom in the future.
So please consider donating so that I can keep up the work.
Donations
Google Pay
This will work only on the version "TB-X505X_S001037_200718_ROW". Check it in the Settings > System > About Tablet > Build Number. If it is the newer "X505X_S001038_200819_ROW", do a factory reset and make sure it is the "TB-X505X_S001037_200718_ROW" before proceeding.
Once a custom recovery is made, OTA updates can be applied without losing root. So do not update the tablet until a custom recovery is developed for the device. I plan to develop a custom recovery for it as soon as possible, so please support me.
Anything that goes wrong in this tutorial is not my responsibilty. Proceed at your own risk.
Downloads
patched_boot.img
Step 1. ADB and Fastboot Installation [If adb and fastboot are already installed, skip to Step 2]1. Download the platform tools for your OS from this link.
2. Extract the zip file and place the contents in a folder "platform-tools".
3. To confirm if adb is working, open a command prompt "platform-tools" and run the following command.
Code:
adb version
If it returns the adb version, its done.
Step 2. Unlocking BootloaderWe have to unlock the bootloader inorder to root the device.
Warning: Unlocking bootloader wipes data on the device. It is recommended to backup your data. Proceed at your own risk.
1. Now in the tab, goto Settings > System > About Tablet. Multiple tap the "Build Number" till the developer options are enabled.
2. Goto the developer options and turn on the "OEM unlocking".3. Power off the device.
4. Turn it on by holding Power Button + Volume Down. Once the screen turns on. leave the power button but continue holding the Volume Down button until the fastboot mode is shown.
5. Now open a command prompt in "platform-tools" and now run the following command:
Code:
fastboot oem unlock-go
Your Bootloader is now succesfully unlocked.Step 3. RootingNow to root the tab, download the "patched_boot.img" from the top of this post. Copy the file to the "platform-tools" folder.
Make sure the tab is still in the fastboot mode. Otherwise go back into the fastboot mode as instructed before.
Now run the following command:
Code:
fastboot flash boot patched_boot.img
Congratulations, you have rooted your tab.:highfive:
To complete the process, run the following command.
Code:
fastboot reboot
Once the tab turns on, goto this link and download the latest version of Magisk apk and install it. It is required to control the root privileges for other apps.That's all. You now have a rooted tab.:victory:
If this helped you, hit the thanks button.
And keep tuned for new stuff that are to come for this device.
Thanks for this thread for the TB-X505X.
Shamil Niyas said:
I plan to work on a custom recovery for this tab as well...
I plan to develop a custom recovery for it as soon as possible...
Click to expand...
Click to collapse
Have a look at this post for a TWRP that works with the TB-X505F. It might work for the TB-X505X, provided the X505X uses the SDA429 soc. That version of TWRP is unofficial and does not decrypt the data partition.
If the X505F version of TWRP works for you, then you won't need to patch the boot image - you can just install the Magisk update.zip in TWRP. This saves you from having to release a new patched boot image every time there's an OTA.
Shamil Niyas said:
Once a custom recovery is made, OTA updates can be applied without losing root.
Click to expand...
Click to collapse
With the TB-X505F/L, TB-X605F/L and TB-X705F/L we've found that you need to uninstall Magisk to apply OTAs. This is because Lenovo's OTA updater scripts verify you have unmodified boot, system, vendor and firmware partitions. So make sure you backup these partitions as stock.
Yahoo Mike said:
Thanks for this thread for the TB-X505X.
Have a look at this post for a TWRP that works with the TB-X505F. It might work for the TB-X505X, provided the X505X uses the SDA429 soc. That version of TWRP is unofficial and does not decrypt the data partition.
If the X505F version of TWRP works for you, then you won't need to patch the boot image - you can just install the Magisk update.zip in TWRP. This saves you from having to release a new patched boot image every time there's an OTA.
With the TB-X505F/L, TB-X605F/L and TB-X705F/L we've found that you need to uninstall Magisk to apply OTAs. This is because Lenovo's OTA updater scripts verify you have unmodified boot, system, vendor and firmware partitions. So make sure you backup these partitions as stock.
Click to expand...
Click to collapse
I gave a look at the TWRP image. Unfortunately, X505X does not boot into the recovery image. It would have been great if it worked. I guess it is because of the different processor, as you mentioned.
It is the same for X505X as well. OTA cannot be applied without uninstalling Magisk. So I guess OTAs are a no-go until a custom recovery is developed. The latest update is also just a boot image patch. So there is no way to use magisk on that.
Thanks for the advice.
But i updated to android 10 S001122_200915
Sir, thanks for the thread.,
But unfortunately my version is S001122_200915 and u had posted patched boot_img for S001037 version. I dont want to downgrade. Please make a patched boot_img for this version.
Excuse me if this was asked before. Is there a rooting method for TB-X505F? It's the model that is sold in Europe. I'm thinking of buying this.
ShAd0W_z0nE said:
Excuse me if this was asked before. Is there a rooting method for TB-X505F? It's the model that is sold in Europe. I'm thinking of buying this.
Click to expand...
Click to collapse
This post has instructions for the X505F, under "How do I root my device?".
cYBER~VeTeRaN said:
Sir, thanks for the thread.,
But unfortunately my version is S001122_200915 and u had posted patched boot_img for S001037 version. I dont want to downgrade. Please make a patched boot_img for this version.
Click to expand...
Click to collapse
I'm currently working on the twrp for this device. Once it is finished it should be able to root without downgrading.
cYBER~VeTeRaN said:
Sir, thanks for the thread.,
But unfortunately my version is S001122_200915 and u had posted patched boot_img for S001037 version. I dont want to downgrade. Please make a patched boot_img for this version.
Click to expand...
Click to collapse
Hello cYBER-VeTeRaN,
I have compiled a TWRP for X505X. You can find it here. Install the magisk zip from TWRP and you should be able to root your tablet regardless of the verison.:victory:
Hit the thanks button.
Shamil Niyas said:
Hello cYBER-VeTeRaN,
I have compiled a TWRP for X505X. You can find it here. Install the magisk zip from TWRP and you should be able to root your tablet regardless of the verison.:victory:
Hit the thanks button.
Click to expand...
Click to collapse
Thanks sir. Great job and I'm also from kerala, nice to meet you
Good afternoon.
I have this version ( Build number TB-X505F_S001142_210804 ROW ) of Android on my Lenovo TB X505F.
Can you tell me if this method works with this version of Android?
jsvenancio said:
Good afternoon.
I have this version ( Build number TB-X505F_S001142_210804 ROW ) of Android on my Lenovo TB X505F.
Can you tell me if this method works with this version of Android?
Click to expand...
Click to collapse
[RECOVERY][TB-X505F][UNOFFICIAL] TWRP 3.6.x for Lenovo Tab M10 HD
This version of TWRP works on the Lenovo TB-X505F (wifi). For the TB-X505X, see this thread. For the TB-X605F/L, see this thread. For the TB-X606F/L, see this thread. The X606F/L is the second gen M10 and it uses a Mediatek SOC. #include...
forum.xda-developers.com
Twrp for x505f
Umm where it says to download my os there is no link provided. Same goes for fastbook it takes me tomyour old guide and then there is no link where a person would think they would find it. Am I stupid and missing something or all the links broke/missing ?
I'd prefer to be stupid.... Just saying..
tombaldwin6 said:
Umm where it says to download my os there is no link provided. Same goes for fastbook it takes me tomyour old guide and then there is no link where a person would think they would find it. Am I stupid and missing something or all the links broke/missing ?
I'd prefer to be stupid.... Just saying..
Click to expand...
Click to collapse
Check his new guide, just flash twrp and flash magisk from there
Guys, I am stuck in a Bootloop after i tried that with the patched boot img. Can someone help?
Tamiiiiiii812 said:
Guys, I am stuck in a Bootloop after i tried that with the patched boot img. Can someone help?
Click to expand...
Click to collapse
Download rom, extract boot.img from it and flash it. Makw sure you download the right version.
You can find the rom here:- https://mirrors.lolinet.com/firmware/lenovo/Tab_M10_HD/TB-X505X/
cYBER~VeTeRaN said:
Download rom, extract boot.img from it and flash it. Makw sure you download the right version.
You can find the rom here:- https://mirrors.lolinet.com/firmware/lenovo/Tab_M10_HD/TB-X505X/
Click to expand...
Click to collapse
OMG IT WORKED. Thank you.
Thanks bro. I found what I needed..
Shamil Niyas said:
1. Download the platform tools for your OS from this link.
Click to expand...
Click to collapse
yeah, where is the link?
Booe said:
yeah, where is the link?
Click to expand...
Click to collapse
Just search for platform tools and download it.
Guys, i tried the above mentioned method but my device is showing (can,t load android system. your data my be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device) after performing a factory data reset the device reboots and the welcome menu shows up after 15-30 seconds the device automatically shut down and again shows the same message (can,t load android system. your data my be corrupt. if you continue to get this message, you may need to perform a factory data reset and erase all user data stored onnn this device). this goes again and again......