Related
Hey guys!!!
Today I got a new Update for my OnePlus 3T. But you can't install it with your custom recovery, becouse oneplus doesn't support third party recoverys. (Without lose any data)
So today I would like to explain to you how you can install the update anyway.
Edit: If you don't have the update avarible to download, here is the current Version ONLY for the OnePlus 3T and not for 3!
Link : https://mega.nz/#!RwxjAaSa!csp25h49dQZmZZ4Yehq1ZfXWJHRoDgS-3RnBA-MgXyA
Step 1: Go to your Softwareupdates and click on download Softwareupdate.
Step 2: If the download is completed, don't click on reboot and install!
Step 3: Go in your (for e.g.) ES File Manager and search for "ota". You'll find the .zip file. Copy that to your main Storage (sdcard) directory.
Step 4: After that, reboot into your recovery (at my point, twrp)
IF YOU WANT DO NOW A BACKUP -> SYSTEM, DATA AND BOOT
Step 5: Click on Wipe and select only dalvic and cache. (It'll not delete your data if you select only dalvic and cache!)
Step 6: Now go on install and select the Oxygen OS Version, that you copied to your storage. (Swipe to install)
Step 7: The installation takes a while. If it finished, click on back and wipe dalvic and cache again.
Step 8: After it, you can go back and reboot into your system. It should update now your apps.
Step 9: Finally you got successfully the newest oxygen OS version!
-> If your device was rooted, root access will no longer be available.
Edit: If you want to get root access after updating your phone, download SuperSu.zip (download : https://mega.nz/#!gsBCACAQ!L5t_0Ca6-Lyf-_xRpF9Bw2jzo-xj3W5Dr5X1Y8EsVoY )
Step 1: Boot into your recovery, click on Advanced -> Adbsideload and Swipe to activate it)
Step 2: Connect you device with your computer and check, if your device is successfully conntected to adb devices.
Step 3: Type "adb sideload SuperSU.zip, after the installation, reboot your system.
Step 4: Finished installing root. Have fun
If you have any questions, don't be shy.
Best regards and have fun,
LloydSmallwood
(Don't forget to thank )
Nice tutorial
Sent from my MI 5s Plus using Tapatalk
What TWRP version did you use?
Freyelis said:
What TWRP version did you use?
Click to expand...
Click to collapse
I used 3.0.2
LloydSmallwood said:
I used 3.0.2
Click to expand...
Click to collapse
so the latest, 3.0.3.0, should be also okay?!
hAMMERlized said:
so the latest, 3.0.3.0, should be also okay?!
Click to expand...
Click to collapse
Yeah sure!
LloydSmallwood said:
Yeah sure!
Click to expand...
Click to collapse
okay, i'll give it a try. had to go back to 3.5.4 as supersu (2.79) gave me a bootloop with the latest 4.0 update :/
Updater process ended with error 7
Hello,
Thank you very much for the detailed steps. However, I am getting stuck at installing the OTA and get error 7 on TWRP.
I tried to fix it by following the below link but it did not work:
https://forum.xda-developers.com/showthread.php?t=2522762
Any help or suggestions?
P.S: I am trying to update from 3.5.4 to 4.0 OOS.
I updated my TWRP to 3.0.3 and now can't get TWRP to decrypt, it did not ask me for any pin / password on 3.0.2 TWRP.... Is it safe to revert back to 3.0.2 and flash the 4.1 OTA with it?
SourPower said:
I updated my TWRP to 3.0.3 and now can't get TWRP to decrypt, it did not ask me for any pin / password on 3.0.2 TWRP.... Is it safe to revert back to 3.0.2 and flash the 4.1 OTA with it?
Click to expand...
Click to collapse
Yesterday I got my 3T and upgraded OTA latest OxygenOS 4.0.1. I was able to unlock bootloader and install TWRP 3.0.3 but when I access bootloader the first screen ask me to provide "Decrypt password" to mount, and if I ignore and slide to start modification I don't have access to internal card (assume its READ-ONLY), just folders are visible but unable to find or install SU package.
I check all the forums but didn't find any relevant information how to get out of TWRP "Decrypt password" issue. I don't want my phone to be encrypted, so I would appreciate if anyone can please help me.
SourPower said:
I updated my TWRP to 3.0.3 and now can't get TWRP to decrypt, it did not ask me for any pin / password on 3.0.2 TWRP.... Is it safe to revert back to 3.0.2 and flash the 4.1 OTA with it?
Click to expand...
Click to collapse
I think go back
Removing security (pin/pass/fingerprint) before booting to TWRP on 3.0.3 official worked for me to update to 4.0.1 but miss xposed
SourPower said:
Removing security (pin/pass/fingerprint) before booting to TWRP on 3.0.3 official worked for me to update to 4.0.1 but miss xposed
Click to expand...
Click to collapse
Oke
Hai,
Zip verification of Full 4.01 .zip failed both in 3.0.3.0 and 3.0.3.0.beta 1 TWRP version . If installed ignoring the zip verification , got message " No OS installed " on booting
Pl guide me.
LloydSmallwood said:
Hey guys!!!
Today I got a new Update for my OnePlus 3T. But you can't install it with your custom recovery, becouse oneplus doesn't support third party recoverys. (Without lose any data)
So today I would like to explain to you how you can install the update anyway.
Edit: If you don't have the update avarible to download, here is the current Version ONLY for the OnePlus 3T and not for 3!
Link : https://mega.nz/#!RwxjAaSa!csp25h49dQZmZZ4Yehq1ZfXWJHRoDgS-3RnBA-MgXyA
Step 1: Go to your Softwareupdates and click on download Softwareupdate.
Step 2: If the download is completed, don't click on reboot and install!
Step 3: Go in your (for e.g.) ES File Manager and search for "ota". You'll find the .zip file. Copy that to your main Storage (sdcard) directory.
Step 4: After that, reboot into your recovery (at my point, twrp)
IF YOU WANT DO NOW A BACKUP -> SYSTEM, DATA AND BOOT
Step 5: Click on Wipe and select only dalvic and cache. (It'll not delete your data if you select only dalvic and cache!)
Step 6: Now go on install and select the Oxygen OS Version, that you copied to your storage. (Swipe to install)
Step 7: The installation takes a while. If it finished, click on back and wipe dalvic and cache again.
Step 8: After it, you can go back and reboot into your system. It should update now your apps.
Step 9: Finally you got successfully the newest oxygen OS version!
-> If your device was rooted, root access will no longer be available.
Edit: If you want to get root access after updating your phone, download SuperSu.zip (download : https://mega.nz/#!gsBCACAQ!L5t_0Ca6-Lyf-_xRpF9Bw2jzo-xj3W5Dr5X1Y8EsVoY )
Step 1: Boot into your recovery, click on Advanced -> Adbsideload and Swipe to activate it)
Step 2: Connect you device with your computer and check, if your device is successfully conntected to adb devices.
Step 3: Type "adb sideload SuperSU.zip, after the installation, reboot your system.
Step 4: Finished installing root. Have fun
If you have any questions, don't be shy.
Best regards and have fun,
LloydSmallwood
(Don't forget to thank )
Click to expand...
Click to collapse
Um u can flash the updates with twrp if it's zip format. Says so on oneplus as well
samoechen said:
Hai,
Zip verification of Full 4.01 .zip failed both in 3.0.3.0 and 3.0.3.0.beta 1 TWRP version . If installed ignoring the zip verification , got message " No OS installed " on booting
Pl guide me.
Click to expand...
Click to collapse
Can you send a picture?
hAMMERlized said:
okay, i'll give it a try. had to go back to 3.5.4 as supersu (2.79) gave me a bootloop with the latest 4.0 update :/
Click to expand...
Click to collapse
got me too, f***** update.. haha.. ill post the tutorial for root and current os version in future.
Edited Dec 22 -2017 <-- I may not always change this, but this is a work in progress!
[GUIDE][OSPREY] Moto G3 2015 - BEGIN: How to Unlock bootloader, flash TWRP, flash ROM, flash Root, Flash boot logo.
I started this because while trying to explain it to a user I kept running in to old info.
Code:
/*
* Your warranty is now void.
*
* This may destroy your phone. As with any modification to a phone,
* you must be prepared/willing to THROW IT AWAY without thinking twice.
* If you need it or it is your daily driver, don't mess with it.
* I am not responsible for bricked devices, dead SD cards,
* thermonuclear war, or you getting fired because the alarm app failed. Please
* do some research if you have any concerns about the suggestions in this guide
* before following it! YOU are choosing to make these modifications, and if
* you point the finger at me for messing up your device, I will laugh at you.
*/
This may well work on Merlin but I don't have one to test.
--> NOTE: I no longer use LineageOS so can't help there. Using AOSP 8. Should be no difference.
1a) Prep - before you do anything, in stock, go to settings/Development Options (which is turned on by tapping /settings/about phone/Build Number about 10 times.)
turn "OEM unlocking" ON
turn Debugging - "USB debugging" ON.
1b) Now! - To do anything, you must unlock your bootloader: This is done by going to the Motorola site and following their instructions completely.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
They want you to "Install the Android SDK.". You only need adb and fastboot on your PC (windows or Linux).
Try this guide to get ADB and FASTBOOT onto your computer: https://forum.xda-developers.com/showthread.php?t=2588979
For Ubuntu Linux simply type fastboot on the terminal and if it's missing a command will pop up as to how to add it - simple. same with adb.
ADDITIONAL THOUGHTS: a very helpful user suggested the following additional for unlock bootloader and getting adb and fastboot: @Dave here - see post 34ff.
Dave here said:
Glad it was helpful! Happy to be able to give something back. Here are some links I used...
LineageOS Osprey install guide:
wiki.lineageos.org/devices/osprey/install
LineageOS Using ADB and fastboot guide:
wiki.lineageos.org/adb_fastboot_guide.html
adb & fastboot: I used this link, which was in the LineageOS ADB guide and I think also the Motorola bootloader unlocking instructions:
Mac: dl.google.com/android/repository/platform-tools-latest-darwin.zip
Windows: dl.google.com/android/repository/platform-tools-latest-windows.zip
Linux: dl.google.com/android/repository/platform-tools-latest-linux.zip
Lenovo forum: "THERE IS AN ERROR WITH YOUR REQUEST! MOTO G ROOTING PROBLEM!" (it's actually about bootloader unlocking, not rooting):
forums.lenovo.com/t5/MOTO-G-MOTO-G-...EST-MOTO-G-ROOTING-PROBLEM/m-p/3458979#M27009
European Motorola unlocking URLs:
motorola-global-en-uk.custhelp.com/app/standalone/bootloader/unlock-your-device-a
motorola-global-portal-de.custhelp.com/app/standalone/bootloader/unlock-your-device-a
Click to expand...
Click to collapse
2) Now that your phone is "bootloader unlocked" you will get an ugly screen on every bootup - we'll get to that in step 4.
- Now you must set up a custom recovery so you can back things up and change things. To do that you need to flash a recovery from your PC.
-> Follow squid2's guide: https://forum.xda-developers.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537
Hint - to get into fastboot mode on your Osprey, power off, THEN, hold power and vol-down for maybe 8 seconds until the fastboot screen pops up, Then connect USB cable phone to PC.
I recommend flashing his latest.
I also recommend doing it twice in a row, simply because once in a while that is needed.
3) okay, now you can boot into TWRP: power off, hold power and vol-down for a few secs until fastboot screen pops up. use vol-down to step through the options. Choose Recovery and press power to select. 10 secs later, you're in TWRP. If you get the dead android it means you still have the stock recovery - boot to fastboot and flash TWRP again.
IMMEDIATELY tap Backup and select to put backup on external storage - your SDcard. NOTE - if your SDcard has been converted to "internal storage" you will have to choose "internal storage" (em0). I did it twice. This is your stock ROM. YOU WILL NEED THIS LATER.
-- > For TWRP BACKUP I use the default settings of "system,data, and boot". Here is a nice article that explains the differences: https://twrp.me/faq/whattobackup.html .
At this point I recommend you boot back into stock and connect your phone to your PC via USB (slide down) and copy that backup in the TWRP folder to your PC. at least once, maybe twice, for safe keeping. You will need this if you wish to test if a problem exists only on a custom ROM but not on the stock ROM. You will also need this if you simply choose to run stock, instead of a custom ROM. Remember, you are now testing ROMs - nothing is certain!
4. Getting rid of the nasty boot message:
This has some nice ones: https://forum.xda-developers.com/2015-moto-g/themes-apps/bootlogo-beautiful-logos-t3229167
Grab the one(s) you like and download - they're in .zip format. Put it on SDcard. Boot to TWRP, tap install, choose the one you want to flash. Voila.
Be aware there are some sites out there with logos that don't work on Moto G3.
5. To flash a custom ROM: Download to PC and put it on your SD card. Do same for gapps. (gapps - g-apps - google apps allow you to log in to your google account, use play store, etc. example http://opengapps.org/ (use arm, 7.1, whatever size you wish)(if you're new use full, mini, or micro until you know what you need. If you're on a 1GB phone, consider nano or pico.) )
https://download.lineageos.org/osprey or whatever ROM you want.
http://opengapps.org/ or whatever gapps you want.
Boot to TWRP.
Clean flash:
tap WIPE,
tap advanced, carefully checkmark:
Dalvic/ARTCache,
System,
Data,
Cache,
and then swipe the bottom swipe button. Takes a few sec. This is what makes a "clean flash".
Generally: Don't wipe "internal storage" or SDcard as this is where TWRP stores its backups/nandroids. - I always copy my TWRP backups to PC for safety.
Then back to menu screen and tap Install, select the rom, and swipe and let it do its thing.
Then back and tap Install, select the gapps and swipe to flash it.
THEN, and only then: tap Reboot (if you're at the main menu you also have to tap System to boot from system.)
The install takes 3 min or so before it starts asking questions.
Be sure to choose "Set up as New" or else you get whatever junk is in your google drive. This has cost errors and much time. <-----
6. Root: If you want to use bank apps, PokemonGo, etc, follow these instructions for Magisk:
https://forum.xda-developers.com/2015-moto-g/general/guide-pass-safetynet-custom-roms-t3603609
read the whole thread.
- Else go to https://download.chainfire.eu/1019
and download the zip form of Chainfire's SuperSU 2.79 and boot to TWRP and flash (install) it.
Many thanks to @acejavelin for inspiration and information(which I probably shamelessly stole from him), to @squid2 for his installation guide and his version of TWRP, to @Chainfire for the tons of work that continue to go into superSU, to @coolguy_16 for the safetynet/CTS work, and all the many Devs and helpers who make these ROMs possible, and as clean as they are! And to users like you who find bugs and file bug reports! Thank you!
Remember you are working with a Development ROM - a work in progress! (Even stock isn't perfect!!!)
Enjoy!
KrisM22 said:
I started this because while trying to explain it to a user I kept running in to old info.
As with any modification to a phone, you must be prepared/willing to throw it away without thinking twice. If you need it or it is your daily driver. don't mess with it. It is YOUR responsibility alone. If you break your phone, I will laugh.
1) To do anything, you must unlock your bootloader: This is done by going to a Motorola site and following their instructions completely.
https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
2) Now that your phone is "bootloader unlocked" you will get an ugly screen on every bootup - we'll get to that later.
- Now you must set up a custom recovery so you can back things up and change things. To do that you need to flash a recovery from your PC.
a) you need to have fastboot support on your PC
Try this guide: https://forum.xda-developers.com/showthread.php?t=2588979
You do not need to put the whole SDK on as s9ome guides would have you do.
Follow squid2's guide: https://forum.xda-developers.com/2015-moto-g/orig-development/twrp-twrp-moto-g-2015-t3170537
Hint - to get into fastboot mode, power off, THEN, hold power and vol-down for maybe 8 seconds until the fastboot screen pops up, Then connect USB cable phone to PC.
I recommend flashing his latest - twrp-osprey-3.1.0-r1.img
I also recommend doing it twice in a row, simply because once in a while that is needed.
3) okay, now you can boot into TWRP: power off, hold power and vol-down for a few secs until fastboot screen pops up. use vol-down to step through the options. Choose Recovery and press power to select. 10 secs later, you're in TWRP.
IMMEDIATELY tap Backup and select to put backup in internal (em0) storage. I did it twice. This is your stock ROM. YOU WILL NEED THIS LATER.
4. Getting rid of the nasty boot message:
This has some nice ones: https://forum.xda-developers.com/2015-moto-g/themes-apps/bootlogo-beautiful-logos-t3229167
Grab the one(s) you like and download - they're in .zip format. Put it on SDcard. Boot to TWRP, tap install, choose the one you want to flash. Voila.
5. To flash a custom ROM: Put it on your SD card. Boot to TWRP.
Clean flash: tap WIPE, tap advanced, carefully select Dalvic, Data, System, Cache, and then swip the bottom swipe thing. Takes a few sec. This is what makess a "clean flash".
Then back to menu screen and install, select the rom, and swipe and let it do its thing.
Then back and select gapps and flash it.
Then do supersu and flash that (optional)
Then "reboot".
6. Root:
Click to expand...
Click to collapse
nice information... hope this will help many friends..
Sent from my MotoG3 using Tapatalk
save1
save2
Subins Mani(Tintumonn) said:
nice information... hope this will help many friends..
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Thanks - hopefully it will help.
A factory reset is recommended. It wipes /data, /cache, ART cache as well as any remnant files in the internal and external storages, which are missed when manually wiping these partitions.
Wiping of /system is not always needed as the updater script of a ROM automatically wipes it before copying files. It is usually needed in case of updating ROMs where some persistent mods are needed to be removed such as gapps.
More on this here at TWRP FAQ.
Broadcasted from Zeta Reticuli
Gravemind2015 said:
A factory reset is recommended. It wipes /data, /cache, ART cache as well as any remnant files in the internal and external storages, which are missed when manually wiping these partitions.
Wiping of /system is not always needed as the updater script of a ROM automatically wipes it before copying files. It is usually needed in case of updating ROMs where some persistent mods are needed to be removed such as gapps.
More on this here at TWRP FAQ.
Broadcasted from Zeta Reticuli
Click to expand...
Click to collapse
I thought this was true but found my gapps was remaining residual in system - had to clear system to get rid of gapps.
KrisM22 said:
I thought this was true but found my gapps was remaining residual in system - had to clear system to get rid of gapps.
Click to expand...
Click to collapse
Yes you are correct, gapps won't get removed for new builds of the same ROM due to a persistent ROM script. However flashing a ROM different than the one currently installed usually ignores such scripts and does a clean wipe. Doing a manual wipe just to be sure is fine, even needed sometimes.
I just wanted to point out that not performing a factory reset (twrp>wipe>swipe to factory reset) can leave potential conflicting files in aforementioned places which can cause unexpected behaviours ranging from FCs to bootloop. The potential issues are rare but I think you know how much trouble it can bring to folks trying to capture real bugs (thanks for hard work at Linage ); it was all about removing the potential factors .
Broadcasted from Zeta Reticuli
The TWRP wipe-swipe does Data, Cache, and Dalvic. That's what I used to do. After messing up some tests this past week and wasting a lot of time, I now recommend adding system to that:
In advanced, checking data, cache, and dalvic/ARTcache, and, now, system. as far as i can see, I am leaving nothing other than internal storage and sd card (and of course whatever is in OTG if there's one attached). TBPro puts its backups on "internal storage". By the way I do appreciate your taking the time to look so closely at this!
KrisM22 said:
[GUIDE]
6. Root: Go to http://www.theandroidsoul.com/supersu-2-79-zip-apk-download/
and download the zip form of Chainfire's SuperSU 2.79 . Use it in step5 above.
NOTES: this has nothing to do with rooting your stock ROM which afaik can't be done.
Click to expand...
Click to collapse
To root stock ROM with SuperSU, you need to open a terminal in TWRP and type
Code:
echo "SYSTEMLESS=true" > /data/.supersu
This forces a systemless installation.
Edit: Not necessary anymore, just flash SuperSU zip and you're done
MagiskSU is an alternative to SuperSU and similar apps that hides root (to SafetyNet), so it's better to use that with stock ROM. It is also pre-installed on some ROMs like AICP.
If you're using LineageOS, it's best to use the official root package: https://download.lineageos.org/extras (direct link).
xMotoDA said:
To root stock ROM with SuperSU, you need to open a terminal in TWRP and type
Code:
echo "SYSTEMLESS=true" > /data/.supersu
This forces a systemless installation.
MagiskSU is an alternative to SuperSU and similar apps that hides root (to SafetyNet), so it's better to use that with stock ROM. It is also pre-installed on some ROMs like AICP.
If you're using LineageOS, it's best to use the official root package: https://download.lineageos.org/extras (direct link).
Click to expand...
Click to collapse
a) I have seen that but not tried it. I did add a note so you're now the authority!
b) not since SuperSU 2.79 - Those were invented because earlier SuperSUs had probs. I've been flashing 2.79 for a while now with no problems on Lineage.
Thanks for looking in!
KrisM22 said:
a) I have seen that but not tried it. I did add a note so you're now the authority!
b) not after SuperSU 2.78 (or 2.70 or something) - Those were invented because earlier SuperSUs had probs. I've been flashing 2.79 for a while now with no problems on Lineage.
Thanks for looking in!
Click to expand...
Click to collapse
SuperSU 2.79 "General Release" was the version of the change, anything prior needed the forced systemless command, all 2.79 or later versions include the correct check to flash on most Moto devices without the command. Using the echo command to create the file has no detrimental effects on later versions though. Note that using https://download.chainfire.eu/supersu/ as your download link will always get you the most current stable version of SuperSU available directly from the official source.
Magisk is the way to go to root most stock devices though, I would definitely agree with that.
acejavelin said:
SuperSU 2.79 "General Release" was the version of the change, anything prior needed the forced systemless command, all 2.79 or later versions include the correct check to flash on most Moto devices without the command. Using the echo command to create the file has no detrimental effects on later versions though. Note that using https://download.chainfire.eu/supersu/ as your download link will always get you the most current stable version of SuperSU available directly from the official source.
Magisk is the way to go to root most stock devices though, I would definitely agree with that.
Click to expand...
Click to collapse
Huge thanks for that!!! Changed above post.
Never played with Magisk - others (you!) are the authority on that. I think some were saying that was a way to get a custom rom to pass safteynet... Thanks!
Huge thanks for looking in!!!
edited/updated 5-4-17
Problem!
Resurreccion no me va bien en mi movil, se sobre calienta demaciado, por lo demas bien!
GermanRodriguez said:
Resurreccion no me va bien en mi movil, se sobre calienta demaciado, por lo demas bien!
Click to expand...
Click to collapse
This is possibly a problem with that rom - ask at that thread.
https://forum.xda-developers.com/2015-moto-g/development/rom-resurrection-remix-n-5-8-2-t3587204
or
https://forum.xda-developers.com/2015-moto-g/development/rom-resurrection-remix-t3478845
edited...
edited
update
changed.
DISCLAIMER
I am not responsible for anything that happens to your device on following these steps. These are untested steps that worked for me and might work for you.
PREREQUISITES
1. PC with adb
2. Unlocked Bootloader
3. TWRP
4. MIUI 9 [Might work with other ROMs, not tested]
5. Lazyflasher zip
NOTES
1. If you are on a custom ROM, chances are that camera2 api is already enabled. Use Manual Camera Compatibility to verify.
2. If you are on MIUI, updating using ota might reset build.prop file. This might help, not tested. Update: I successfully updated to MIUI 9 Global 7.10.19 | Beta, see below for steps,
3. I am using Google Camera v4.4.020.163412804 on MIUI 9 Global 7.9.7 | Beta, and it is a HUGE improvement over the stock camera.
STEPS
1. Boot into TWRP. (Guide if you don't have TWRP)
2. Mount System.
3. Take NANDroid backup. (Optional but HIGHLY RECOMMENDED)
4. Connect to PC and execute the following command in terminal:
Code:
[SIZE="3"]adb pull /system/build.prop[/SIZE]
5. This copies build.prop to the current directory. (C:\Users\[USERNAME] by default on windows)
6. Copy it to another directory for backup.
7. Open in editor and add the following line at end:
Code:
[SIZE="3"]persist.camera.HAL3.enabled=1[/SIZE]
8. Save and exit.
9. Execute following commands:
Code:
[SIZE="3"]adb push build.prop /system/
adb shell
cd system
chmod 644 build.prop
[/SIZE]
10. Copy lazyflasher to internal storage.
11. Flash using TWRP.
12. Reboot to system.
13. Use Manual Camera Compatibility Checker to verify.
14. PROFIT!
15. Install the latest Google Camera HDR+ Port. (Optional but HIGHLY RECOMMENDED ;P)
UPDATING MIUI
1. Download the official recovery zip from here.
2. Download latest TWRP from here
2. Reboot into TWRP.
3. Take NANDroid. (Optional, just in case . . .)
4. Transfer ROM zip, TWRP img and Lazyflasher zip to internal storage.
5. Flash ROM zip. (Took about 10 minutes)
6. Flash TWRP img. (Go to flash -> select flash image -> select twrp-[v].img)
7. Flash Lazyflasher zip.
8. Follow steps 4 through 9 of above instructions. (Yes, build.prop also gets replaced on update)
9. Reboot to system.
10. Wait patiently.
11. VOILA !!
LINKS
1. Manual Camera Compatibility Checker
2. Lazyflasher Zip
3. Google Camera HDR+ Port
4. Latest MIUI Recovery Image
5. Official TWRP for mido
6. Sources: (1) (2) (3)
Hope this helps. Try and comment if this works for you in other ROMs. Also let me know if anything is unclear.
TWRP Tweaks (MIUI 9 Beta)
The method in this thread basically allows you to edit build.prop without rooting, which opens up a lot of possibilities. Here are some other useful tweaks to build.prop that I use.
(Note: If a line is already present in the file, edit the line otherwise add at end.)
1. Enable MIUI's full screen gestures
Code:
[SIZE="3"]
qemu.hw.mainkeys=0
[/SIZE]
2. Add EIS and disable noise cancellation
Code:
[SIZE="3"]
persist.camera.eis.enable=1
persist.camera.HAL3.enabled=1
ro.qc.sdk.audio.fluencetype=fluencepro
[/SIZE]
3. Turn off noise cancellation for audio recordings
Code:
[SIZE="3"]
persist.audio.fluence.voicerec=false
[/SIZE]
4. Fix Google Assistant talkback
Code:
[SIZE="3"]
mm.enable.qcom_parser=245389
[/SIZE]
Sources: (1)
Do reply if you are using some build.prop tweak and I'll add it here!
is it possible to make the flash-able zip work with stock recovery?
What does the lazyflasher zip actually do? A quick search on google shows a custom kernel installer.
joefso said:
is it possible to make the flash-able zip work with stock recovery?
Click to expand...
Click to collapse
I am not sure if it is safe to flash zips from stock recovery. Even if you could, you would not be able to take NANDroid, so you are doomed if things go south. Still, if you want, you could try and then we'll know
mato_d007 said:
What does the lazyflasher zip actually do? A quick search on google shows a custom kernel installer.
Click to expand...
Click to collapse
The source of the lazyflasher zip (2 in sources) says:
This device uses dm-verity
This means that swiping to allow system modifications will prevent you from being able to boot if you are using the stock kernel. In order to bypass dm-verity's boot prevention, you will have to install a kernel that has dm-verity disabled in the fstab.
Click to expand...
Click to collapse
When I was trying the adb method, I was getting a bootloop, because (I think) the system partition had been modified (new build.prop replaced old one). Flashing this zip solved this, so I guess it essentially allows modifications to the system partition.
A_K_S_H_ said:
I am not sure if it is safe to flash zips from stock recovery. Even if you could, you would not be able to take NANDroid, so you are doomed if things go south. Still, if you want, you could try and then we'll know
Click to expand...
Click to collapse
I am willing to try because it would be great if this could work withouth using twrp, root or a unlocked bootloader.
Are the scripts compatible?
joefso said:
I am willing to try because it would be great if this could work withouth using twrp, root or a unlocked bootloader.
Are the scripts compatible?
Click to expand...
Click to collapse
They should be, as I used them with stock MIUI, stock kernel. However, are you going to flash a zip on locked bootloader? Is that even possible? Why would modifications to the system partition be allowed with locked bootloader? What would be the point of locking if that is the case?
A_K_S_H_ said:
They should be, as I used them with stock MIUI, stock kernel. However, are you going to flash a zip on locked bootloader? Is that even possible? Why would modifications to the system partition be allowed with locked bootloader? What would be the point of locking if that is the case?
Click to expand...
Click to collapse
I assumed that if OTA updates can be flashed through bootloader then by that logic /system could be modified too, right? hmmm
In Android devices, Recovery is an Android-based, lightweight runtime environment separate from and parallel to the main Android operating system. Recovery's original purpose was:
to apply software updates to the device, e.g. OTA updates, and
to erase user data and cache, e.g. for troubleshooting or preparing the device for resale (factory reset) and
to run (another) external tool from microSD flash memory
https://forum.xda-developers.com/wiki/Recovery
Click to expand...
Click to collapse
Thanks... BTW..
You can simply add that line using any file manager with root permissions and after rebooting device it works..
amit.tiger12 said:
Thanks... BTW..
You can simply add that line using any file manager with root permissions and after rebooting device it works..
Click to expand...
Click to collapse
Read the title : WITHOUT ROOT
A_K_S_H_ said:
Read the title : WITHOUT ROOT
Click to expand...
Click to collapse
yep I found..
do you have any solution for locked bootloader or everything stock??
amit.tiger12 said:
yep I found..
do you have any solution for locked bootloader or everything stock??
Click to expand...
Click to collapse
Unfortunately I don't have access to a stock mido right now, and I don't want to lock my bootloader.
If you're willing to risk it, you could try these steps:
1. Go to developer settings and enable adb.
2. Follow steps 4 to 9 of main post (with device switched on)
3. Reboot.
You might get a bootloop on rebooting, in which case you'd have to get into stock recovery and factory reset, because afaik, stock recovery doesn't give you adb.
Do tell what happens if you try this, good luck!
When I replace the build.prop the phone goes bootloop. It does not matter I use adb or root explorer or something... Why is that? BTW only this method worked: I used an app called build prop editor and worked like a charm! Thank you. If you did not tell that it was possible to enable camera 2 api on miui 9, all my hopes would be lost. So I suggest everyone to use another methods in case this does not work.
Does this work for MIUI 8? I dont want to root my phone but would like camera2
qun said:
Does this work for MIUI 8? I dont want to root my phone but would like camera2
Click to expand...
Click to collapse
It should, provided you have unlocked bootloader, but I haven't tested yet. Take a backup and try! Also, don't forget to reply what happens if you do try.
Can someone tell me what is this?it was set to no hdr+ on default.im on miui 9 global beta 7.12.8
In the end of the TWRP guide it says to flash lazyflasher.zip . In the end of this guide it also says you have to install lazyflasher.zip .
Do you have to install it both times or is once enough ? What would happen if you follow both guides to the letter and install it twice ?
Ghavio1516 said:
Can someone tell me what is this?it was set to no hdr+ on default.im on miui 9 global beta 7.12.8
Click to expand...
Click to collapse
These are configs, check and see which one works best for you.
foxhunt said:
In the end of the TWRP guide it says to flash lazyflasher.zip . In the end of this guide it also says you have to install lazyflasher.zip .
Do you have to install it both times or is once enough ? What would happen if you follow both guides to the letter and install it twice ?
Click to expand...
Click to collapse
No, once should be enough, but flashing twice won't cause any trouble either.
We have the first port and root for this highly unpopular BLU phone.
BLU DASH M 2 - Carliv Touch Recovery 6.6.1 aka CTRI have managed to replace the stock recovery and still keep the stock system since there are no customs roms at the moment. The recovery doesn't require you to be rooted but rooting is possible after flashing or booting this rom. Don't fall for the fake Dash files on youtube, I have downloaded them all and they are copies of similar phones and don't work.. This one is ported over from the D070Q by Carliv.
It will not flash a full custom rom but will flash ZIPs so you can root, recover, flash partitions and hopefully pave the way for a TWRP . I do have a TWRP ported over to the BLU Dash M 2 but the touch doesn't work so you can't pass the first swipe screen.
DOWNLOAD from uploadfiles.io @ https://ufile.io/8oc6k
Instructions
- Make sure to backup any important files, this will wipe your data pics, vids, etc..
- Enable OEM unlock under developer options and power down phone
- Boot to stock recovery by holding PWR + VOL UP
- In recovery choose "Reboot to Bootloader" ( aka fastboot )
- You should now be at a blank screen with Fastboot mode: at the bottom
Open your terminal and type the following code, obviously replacing your paths with the correct ones.
fasboot devices < --- will return a serial number or something to indicate connection is OK
fastboot oem unlock <--- will prompt your phone screen to accept unlock request, chose VOL Up to accept and make sure it says "Unlock pass" at the bottom
For testing only
fastboot -c "lge.kcal=0|0|0|x" boot CTR_6.6.1_BLU_DASH_M2_D090U.img
For permanent flash
fastboot flash recovery CTR_6.6.1_BLU_DASH_M2_D090U.img
Don't power down, instead boot in the same recovery
fastboot -c "lge.kcal=0|0|0|x" boot CTR_6.6.1_BLU_DASH_M2_D090U.img
Inside CTR select Wipe cache, Dalvik cache, Userdata / Data.
Select Reboot Phone from CTR menu and when asked to patch , Select " NO "
On first reboot it will reboot twice, then boot the stock system as if it was a factory reset.
This now paves the way for root with Magisk. See my post after this for rooting Blu Dash M2.
Enjoy !
RESERVED
Hey Thank you, got it working. Had to alter it a bit though. Had to select "Yes" for the fix as mine was restoring the old recovery.
Also when I followed your method, the system was not mounting the internal storage.
So I didn't wipe the data and used "Yes" when rebooting and the recovery is good.
I'll be looking out for the root constructions.
Great tutorial though.
73Hn said:
Hey Thank you, got it working. Had to alter it a bit though. Had to select "Yes" for the fix as mine was restoring the old recovery.
Also when I followed your method, the system was not mounting the internal storage.
So I didn't wipe the data and used "Yes" when rebooting and the recovery is good.
I'll be looking out for the root constructions.
Great tutorial though.
Click to expand...
Click to collapse
That will not work for root because Magisk needs the original boot rom. I'm sure it worked for you and that's a good start but wiping the partitions in order does work as well, I probably just left something out or got the order wrong. It's important we don't use CTR to patch because then Magisk complains about boot img being aleady patched and doesn't work.
Anyway you get the idea, it took me a few tries as well but in the end I managed to keep all 3 features intact, the stock rom + CTR + root. If you need to start again you don't need the full rom or sp flash, just flashing system.img to sytem partition works to restore everything.
I'm hoping to find the source code to the kernel and make a TWRP with touch working but the CTR is the only thing we have so far. It does flash zips just not full operating systems. It also flashes boot and recovery partitions.
Thanks, I can restore and try again. Do you have the tutorial for the magisk to root?
73Hn said:
Thanks, I can restore and try again. Do you have the tutorial for the magisk to root?
Click to expand...
Click to collapse
I think most can figure out Magisk from here, the real hurdle was the lack of a recovery because the stock rom doesn't allow Magisk to be flashed.
Thanks, I already started checking in on it... I'll update here once I get through.
How to Root Blu Dash M 2 with Magisk
I have managed to root the stock system using Magisk. The stock recovery will not let you do this, as usual ignore the garbage on youtube and personal blogs, they're giving false info and fake files. This method works and I'm the first user who ported CTR 6.6 to allow for this.
DOWNLOAD Magisk from developer https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
FOLLOW THE ABOVE POST to replace stock recovery with CTR 6.6
Instructions
- Follow first post to install CTR 6.6 recovery and reboot a couple of times to make sure it stuck.
- Enable OEM unlock under developer options and power down phone
- Boot to new CT 6.6 recovery by pressing PWR + VOL UP
- In recovery choose "Install Zip" and choose the "Magisk.zip" from your /SDCARD
Magisk installer will launch and if you did everything right, complete without errors.
- Select Reboot Phone from CTR menu and when asked to patch , Select " NO "
Phone should now reboot twice and have Magisk installed. I have verified root by deleting protected files like default.prop and gave Root Explorer permanent root access. If something doesn't work just find the right sequence. I believe it was flash system, flash recovery. wipe partitions. flash magisk
Enjoy !
The only thing left do now is find the Blu kernel source code for the M2 so a working TWRP can be compiled from scratch, then any MT6580 rom should be flashable.
Perfectly... Got it working using your same method after reinstalling the firmware... only difference was.
After installing recovery and booting into it, I then installed Magisk via adb sideload.
Confirmed root works.
Thank you very much for your patience and assistance
graciaaas
romish said:
How to Root Blu Dash M 2 with Magisk
I have managed to root the stock system using Magisk. The stock recovery will not let you do this, as usual ignore the garbage on youtube and personal blogs, they're giving false info and fake files. This method works and I'm the first user who ported CTR 6.6 to allow for this.
DOWNLOAD Magisk from developer https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
FOLLOW THE ABOVE POST to replace stock recovery with CTR 6.6
Instructions
- Follow first post to install CTR 6.6 recovery and reboot a couple of times to make sure it stuck.
- Enable OEM unlock under developer options and power down phone
- Boot to new CT 6.6 recovery by pressing PWR + VOL UP
- In recovery choose "Install Zip" and choose the "Magisk.zip" from your /SDCARD
Magisk installer will launch and if you did everything right, complete without errors.
- Select Reboot Phone from CTR menu and when asked to patch , Select " NO "
Phone should now reboot twice and have Magisk installed. I have verified root by deleting protected files like default.prop and gave Root Explorer permanent root access. If something doesn't work just find the right sequence. I believe it was flash system, flash recovery. wipe partitions. flash magisk
Enjoy !
Click to expand...
Click to collapse
Thank you very much! You do not know how much I needed to be root! I thought that this device was impossible to root. I really am very grateful. Friend was asking me if you could adapt the custom Slimrom rom for this device? because all the storage of this one takes the system, it would be of great help for all the users of this phone, I do not know if you can or are interested, but I thank you in advance
romish said:
We have the first port and root for this highly unpopular BLU phone.
DOWNLOAD from uploadfiles.io @ https://ufile.io/bj9kk
Enjoy !
Click to expand...
Click to collapse
Hi, can you provide a download link that doesn't require you to get a premium account to access the file. It's against XDA rules.
kirito9 said:
Hi, can you provide a download link that doesn't require you to get a premium account to access the file. It's against XDA rules.
Click to expand...
Click to collapse
It is not premium, the file just expired so the site will keep it on line for a fee. I'll upload it again.
romish said:
It is not premium, the file just expired so the site will keep it on line for a fee. I'll upload it again.
Click to expand...
Click to collapse
Try this one.. if the host tries to replace it with the original let us know and one of the others who have the file will re upload it to another host. I don't feel like signing up anywhere so that is why I use this host.
https://ufile.io/8oc6k
https://ufile.io/8oc6k
https://ufile.io/8oc6k
kevoncrush said:
Thank you very much! You do not know how much I needed to be root! I thought that this device was impossible to root. I really am very grateful. Friend was asking me if you could adapt the custom Slimrom rom for this device? because all the storage of this one takes the system, it would be of great help for all the users of this phone, I do not know if you can or are interested, but I thank you in advance
Click to expand...
Click to collapse
All 'ya 'all are welcome . Unfortunately I can't go any further because there is no source for the kernel so TWRP won't work because there is no touch to get past the first screen. Otherwise if it. did slim rom would flash without any problems, its just these older recoveries don't support a few things that TWRP has to make flashing full roms successful. If someone has source files for the BLU Dash M2 let me know.
I'll just let you guys know, I managed to make a pretty good custom rom with root only by deleteing everything but the core OS. I don't recommend this for everyone but I did get rid of just about everything and made this 6.0 more like 4.4 .. I got it to the point where even the phone and SMS didn't work and the google framework was deleted, then slowly began adding my approved versions of apps. Now its totally de googled but again I realize this isn't for everyone. I just wanted a small rom with camera ad GPS and those are working fine for me.
Custom recovery link taken down again
Could someone please upload the custom recovery again?
[Port] [Recovery] BLU DASH M 2
I tried to fast boot as peryour instructions but I get the error: cannot load ' ctr_6.6.1 etc. :crying:
Please try this link, if you have a better locarion to store it please do so and reshare as this link is only valid for 2 days.
ctr_6.6.1_blu_dash_m2_d090u.img
---------- Post added at 05:08 AM ---------- Previous post was at 05:01 AM ----------
If that recovery does not work, try this one. I have two of different sizes and can't remember which one i used.
recovery.img
Download link
Please repost the download link
Hey hey hey !!! I'm back for a new method, for flash Magisk without patched_boot.img or select current-slot etc, just by do 2 things. And it works for all phone version, Sable, Beta.... ( We use TWRP temporarily, so after the process, TWRP is gone)
Credits :
Me for the idea.
@Frustrated Indian the tester.
@TingyiChen for this nice TWRP.
Code:
Your warranty is now void.
We are not responsible for bricked devices, bootloop... Please
do some research if you have any concerns about features
included in this GUIDE before using it! YOU are choosing to
make these modifications.
Of course first you must have the drivers installed on your pc. And an unlocked bootloader + unlock critical partition, if it is not, follow this procedure :
1. Installing drivers & Preparing PC
- Download this and extract it
- Open and install "adb-setup-1.4.3.exe"
- When it is done, go to "Drivers" folder and start "miflash_unlock.exe"
- Click on the gear icon top right corner and click on "Check" next to "Click the button to install the drive"
- Do as the installer says
- Hopefully the drivers has been installed so we're done with it, let's head on the next step.
2. Preparing phone for unlocking
- On your phone navigate to Settings->System->About phone and tap the build number until you see "You are developer"
- Go back once and you'll see a new menu called "Developer options"
- Tap on it and search an option called "OEM Unlocking", enable it
- We're done here. Let's keep going
3. Entering fastboot and unlocking bootloader (MAKE A BACKUP of your data!)
- Hold your power button down, tap on restart and hold your volume DOWN button while it resets until you see the Mi bunny doing its thing
- Now we're in Fastboot mode, hooray
- Download this zip and extract it on your PC
- Open it and type "cmd" (without the quotations) in the file manager header where you see (This computer>somethingsomething>Mi A2 fastboot), don't be afraid just type it in, and hit enter and you'll enter into command prompt
- Now we are ready for action
- Type these commands one by one:
fastboot flashing unlock
fastboot flashing unlock_critical
- And follow phone on screen steps to validate unlock bootloader...
After this, you will see a warning message that your bootloader is unlocked and your data is not safe, blah blah... Just ignore it everytime you power on your phone.
Downloads :
- TWRP here
- Magisk Latest Beta / Stable (if you prefer) zip
- Magisk Uninstaller zip
Steps :
- Download TWRP
- Copy it to your pc adb folder
- Rename it to twrp.img
- Download Magisk Installer
- Download Magisk Uninstall
- Place these 2 folders on your phone storage
- Reboot phone to fastboot
- Open fastboot command prompt on your pc
- Type "fastboot boot twrp.img" without quotes
- Your phone will boot twrp
- Decrypt data with your pin if needed
- Click install and select the Magisk Installer zip, swipe to confirm
- Wait for the process
- Reboot
That's it !! You now have root on your phone, and TWRP is gone.
If you have issues you can uninstall Magisk with the Uninstaller zip.
For OTA just uninstall Magisk using Magisk Manager, by flash the stock boot.img to your current-slot, or using the zip and flash it like the Magisk Installer.
Check my other thread, Part 3 : OTA for more informations.
-reserved-
I always thought this method was all we needed to do even with the A/B thing... Is this a custom magisk zip?
After installing the October ota: installing magisk caused a boot loop. Switch to this kernel and install magisk again and everything should work.
https://forum.xda-developers.com/mi-a2/development/kernel-hex-t3855773
Magisk link not work.
kishd said:
After installing the October ota: installing magisk caused a boot loop. Switch to this kernel and install magisk again and everything should work.
https://forum.xda-developers.com/mi-a2/development/kernel-hex-t3855773
Click to expand...
Click to collapse
is that what happened to you, or is that what you heard? the testers did not encounter any problem without hex. Plz don't do pub for other thread.
SpectraFun said:
Magisk link not work.
Click to expand...
Click to collapse
Fixed. sorry it was an issue when we click links using XDA phone app. Have a nice day.
Matteo
Adairo said:
I always thought this method was all we needed to do even with the A/B thing... Is this a custom magisk zip?
Click to expand...
Click to collapse
nope, this is just the latest Zip. i can explain you how my method work. when you fastboot boot TWRP.img , the TWRP will automatically boot on your current slot. and when you flash the magisk zip it will automatically flash the zip on your current slot, ( for exemple if your current slot is b, in the past you should flash magisk_b, but no TWRP will automatically temp boot on slot b, so mgisk will automatically be installed on b. and that's it. ).
Atlas/ML said:
is that what happened to you, or is that what you heard? the testers did not encounter any problem without hex. Plz don't do pub for other thread.
Click to expand...
Click to collapse
This happened to me. Even with flashing back the original kernel I could not boot. Flashing the alternate kernel solved my issue and it's much smoother than stock. Not advertising but it seems that the dtb is changed in some way by patching with magisk and an alternate kernel bypasses that issue to allow booting. In my opinion.
kishd said:
This happened to me. Even with flashing back the original kernel I could not boot. Flashing the alternate kernel solved my issue and it's much smoother than stock. Not advertising but it seems that the dtb is changed in some way by patching with magisk and an alternate kernel bypasses that issue to allow booting. In my opinion.
Click to expand...
Click to collapse
flash stock kernel has no sense. that's why it doesn't work. if you have issue you should just flash boot.img or flash magisk uninstaller in twrp like magisk zip. sometime hex kernel cause some issues . for me with all version tested, with help of the maintainer @draco I'm not able to boot fine. I have a green glitchy screen etc, and after some boot my device screen stuck on black screen.
works fine, thank you!
bavmouse said:
works fine, thank you!
Click to expand...
Click to collapse
I'm glad to hear it, enjoy
Atlas/ML said:
nope, this is just the latest Zip. i can explain you how my method work. when you fastboot boot TWRP.img , the TWRP will automatically boot on your current slot. and when you flash the magisk zip it will automatically flash the zip on your current slot, ( for exemple if your current slot is b, in the past you should flash magisk_b, but no TWRP will automatically temp boot on slot b, so mgisk will automatically be installed on b. and that's it. ).
Click to expand...
Click to collapse
I'm gonna try to get Xposed working with this method, if it fails I'll try another one used on pixel 2
Adairo said:
I'm gonna try to get Xposed working with this method, if it fails I'll try another one used on pixel 2
Click to expand...
Click to collapse
I recommend you to use magisk and install systemless xposed.
Atlas/ML said:
I recommend you to use magisk and install systemless xposed.
Click to expand...
Click to collapse
I've heard about Xposed from magisk brings a bootloop... I already installed Hex kernel so I don't mind to modify system partition
Adairo said:
I've heard about Xposed from magisk brings a bootloop... I already installed Hex kernel so I don't mind to modify system partition
Click to expand...
Click to collapse
okay, give me results if it works. good luck
Atlas/ML said:
okay, give me results if it works. good luck
Click to expand...
Click to collapse
*Xposed from magisk = bootlop
*flashed Xposed.zip from twrp = bootlop
*install xposed from Pixl 2 method: https://www.themefoxx.com/2018/01/xposed-for-pixel-2-xl.html = bootlop
I guess we'll have to wait a bit longer to get xposed working on our A/B partition device
Adairo said:
*Xposed from magisk = bootlop
*flashed Xposed.zip from twrp = bootlop
*install xposed from Pixl 2 method: https://www.themefoxx.com/2018/01/xposed-for-pixel-2-xl.html = bootlop
I guess we'll have to wait a bit longer to get xposed working on our A/B partition device
Click to expand...
Click to collapse
hum, interesting
I'm on September update and want to update to the October one, I've tried doing everything in Part 3 but no success. Any solution that let me keep my data?
Adairo said:
*Xposed from magisk = bootlop
*flashed Xposed.zip from twrp = bootlop
*install xposed from Pixl 2 method: https://www.themefoxx.com/2018/01/xposed-for-pixel-2-xl.html = bootlop
I guess we'll have to wait a bit longer to get xposed working on our A/B partition device
Click to expand...
Click to collapse
Xposed will not work untill we get a deodexed stock rom or custom rom