Hey guys,
I recently rooted my z2 the easiest way using a thread I found and TWRP 2. I have some basic experience flashing roms but it has always involved carefully following instructions.
I recently downloaded Cyanogenmod for Sirius but when I try and use TRWP to flash the zip it tells me I have the wrong rom, presumably because TWRP is designed for the Z3 and it thinks I'm trying to do something silly.
I have Rom Manager and have tried to install Clockworkmod bit it has trouble recognising my device and always boots into TWRP instead. I've had problems using ADB software in the past so would like to find a "phone-based" fix if possible.
Any help would be much appreciated xox
1. Root and backup TA (optional)
2. Unlock your bootloader
3. Flash kernel and recovery
4. Through recovery flash CM12.1 (or any older versions of choice)
Need i explain in more detail.
Read the part about flashing boot.img using fastboot: http://forum.xda-developers.com/xperia-z2/help/twrp-phone-t3178773/post62332549#post62332549
Then you should be able to flash your CM.
I want to root my htc desire x and I more or less followed this - https://www.youtube.com/watch?v=0zdhyDky2MI and have so fare unlocked the bootloader.
At this moment I got twrp-2.6.0.0-protou.img installed.
https://twrp.me/devices/htcdesirex.html
I installed the latest version of supersu through twrp recovery. I did also give the install instructions on the twrp webpage a go but to no avail.
http://forum.xda-developers.com/showthread.php?t=1538053
When i open supersu on the phone I get this error message (loosely translated from danish).
"no binary su program file installed and supersu cannot install one this is a problem"
http://forums.androidcentral.com/ht...uper-su-installation-failed-how-do-i-fix.html
http://forums.androidcentral.com/an...-binary-installed-supersu-cannot-install.html
I do not have root. When I install supersu with twrp recovery mode it delivers a successful message at the end of install however I see no text in the twrp terminal/console during the install of supersu.
I have android-tools installed on my distribution which delivers fastboot as well as ADB. I have not setup SDK and am wondering if that is coursing issues. Though I get no such error messages.
No need to mess yourself with SuperSU as it is included in the ROM. Pick a ROM of your choice (i.e. Vimiro) and install. I assume you are S-ON (look at the bootloader in top). If so, you need to pick the kernel out of the ROM (open the package with Winrar) and take out boot.img. Flash manually as you flashed TWRP: fastboot flash boot boot.img. Then install ROM-package.
I don't particularly want to install a custom ROM. Do I have to?
What I want to achieve is to be able to move or remove some of the bundled apps, e.g. chrome - in an effort to free up storage, to an ext formatted partition on the sd-card.
techgage.com/article/moving_your_non-movable_android_apps_to_an_sd_card
It is not especially needed but handy You discovered already the SuperSu thread, maybo the solution is over there? Sorry, can't help you on SU problems. If nothing helps give another ROM a try (after backup). Most of the ROM's have nice features (also with custom kernel) and a installer on which you can select apps to install or not.
do it on your own risk ..................
you need
1. unlocked bootloader
2. twrp recovery installed
3. official stock firmware installed.
4. gapps 7.0 arm version stock package
for moto g4 only
please backup you current stock rom using twrp
1. unlock bootloader that void your warranty so do that on your own will.
2. install twrp recovery after unlocking the booloader
3. download gapps from open gapps website and select
arm ->7.0->stock
4. install gapps without factory reset and after that reboot, it takes some to boot than go to settings apps search dialer app then give it all the permissions and make pixel launcher default.
this method is annoying because you have to backup your current rom before flash gapps. if any problem occured then go to twrp and factory reset and then restore the rom.
but this method take your moto g4 to very stable pixel ui and also every app is genuine as pixel device. i trust on open gapps.
i did it very short because old users know how to unlock bootloader and install twrp so use that if you want some pixel feel on moto g4.
for new users of moto g4 guys do not update the rom in future if you unlocked the bootloader.
*** use this method if you have current version of stock rom that is installed when you unlock the bootloader, for example: if you have npj25.93-4 version installed at present time then you must have that version of stock rom, for relocking the moto g4, for the future update. if you update the software by auto update feature that prompt on the whole screen whenever new updates come, then you will be in trouble untill you have latest updated stock firmware package. understand the matter, because it will hard brick your phone so unlock the bootloader if you have full stock rom package for relock the device and during unlocked bootloader do not auto update to the newer version of os. its simple do not update to latest untill you relock the device.
good luck and do it carefully ....... otherwise used methods describe on youtube for unrooted devices
nice..
will it work on g4 plus?
Had QFJEUXM v11.0.5.0,
OrangeFox v10.1.2,
Hasty kernel,
Magisk Canary v20416
Today received OTA notification for QFJEUXM v11.0.6.0 (frankly, expected v12 but ok for now).
Did not accept OTA (System update, Automatic download disabled) but proceeded as following:
1) Downloaded full Recovery/zip firmware
https://bigota.d.miui.com/V11.0.6.0...AGlobal_V11.0.6.0.QFJEUXM_79a4386920_10.0.zip
2) Opened (in MiXPorer), copied out boot.img, patched boot.img from Magisk Manager (Preserve DM-Verity and Preserve Encryption On, Recovery Mode Off)
3) Rebooted to OrangeFox, flashed firmware zip from (1)
4) Rebooted again to OrangeFox (otherwise stock Recovery will overwrite), flashed patched_boot.img from (2)
5) Rebooted to system:
- all apps, settings and data preserved
- Magisk, modules, root grants all preserved
By (4), OrangeFox was also preserved.
Instead of OrangeFox, you can also use Official TWRP (probably Unofficial as well and likely other custom Recoveries)
Btw, Official TWRP v3.4.0 just released:
https://dl.twrp.me/davinci/
finally supporting back-up of Data if using dual apps:
https://forum.xda-developers.com/showpost.php?p=82910629&postcount=316
Updated mine today also. dowload zip, patched boot with magisk, installed zip and boot image with TWRP, looks like all is fine.
Great, thanks for the advice as I usually follow your recommendations.
Proceeded with Hasty kernel, it works fawlessly with QFJEUXM v11.0.6:
Download Hasty-davinci-Intoxicated-insider.zip from:
https://forum.xda-developers.com/showpost.php?p=82564409&postcount=119
1) Reboot to OrangeFox/TWRP and
flash the just downloaded Hasty
2) Reboot to system - Magisk Manager will show that Magisk is not installed, never mind
3) Reboot to OrangeFox/TWRP and make a Backup of Boot
4) Reboot to system and patch the just backed up boot.emmc.win
5) Reboot to OrangeFox/TWRP and flash the just patched patched_boot.img
Reboot to system and enjoy Hasty kernel (longer lasting battery) with Magisk
Step (2) could probably be skipped and therefore steps (1) and (3) merged to a single step:
Reboot to OrangeFox/TWRP and
flash Hasty, then backup Boot
This maybe a stupid question (probably is) I normally use TWRP and not that I have needed to do it yet but what are the steps for restoring a backup with OF and from reading the guide it doesn't actually explain it? I currently backup to a OTG USB stick.
thanks
brachios said:
This maybe a stupid question (probably is) I normally use TWRP and not that I have needed to do it yet but what are the steps for restoring a backup with OF and from reading the guide it doesn't actually explain it? I currently backup to a OTG USB stick.
thanks
Click to expand...
Click to collapse
With the latest official TWRP 3.4.0 I was finally able to successfully back-up Data partition (I'm using dual WhatsApp and it was failing both with TWRP and OrangeFox)
Hence you can use TWRP 3.4.0 (instead of OrangeFox as explained in post #1) and backup everything (except Cache and TWRP recovery itself) in advance - but I didn't need to restore anything (ie, didn't need to restore Data upon upgrading MIUI): all my apps, data and settings were preserved
Otherwise, I also (partially) backup things over Google and Mi account
What I was trying to say is I'm now using Orangefox and just looking how to do a restore if needed as I was using TWRP for years.
brachios said:
What I was trying to say is I'm now using Orangefox and just looking how to do a restore if needed as I was using TWRP for years.
Click to expand...
Click to collapse
There is also Backup/Restore option in OrangeFox
AFAIK, Fox uses the TWRP engine (Fox has different UI and few more options) hence it's backup (files indeed look the same) should be restorable through TWRP
I liked Fox but for now I switched to TWRP since finally being able to make full nandroid backup by TWRP 3.4.0 - hoping that Fox will be updated to the latest TWRP engine
Thanks, being comfortable with TWRP I might switch back at least I know what I'm doing.
Is there are anybody here who did upgrade to QFJEUXM v11.0.6, but who has NO Magisk (and ideally, has locked Bootloader) to check SafetyNet with the attached app, or alternatively with:
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
zgfg said:
Is there are anybody here who did upgrade to QFJEUXM v11.0.6, but who has NO Magisk (and ideally, has locked Bootloader) to check SafetyNet with the attached app, or alternatively with:
https://play.google.com/store/apps/details?id=com.scottyab.safetynet.sample
Click to expand...
Click to collapse
No matter if on v11.0.6 or older, if Bootloader is unlocked, CTS Profile will fail (since the last day or two) and Magisk with Magisk Hide Props Config cannot help
Seems that custom ROMs are excluded from the problem (from Google's ongoing testing)
Google is testing SafetyNet, they will hopefully turn off again that hardware backed CTS Profile attestation later:
https://groups.google.com/forum/m/#!msg/safetynet-api-clients/lpDXBNeV7Fg/Ov2H6ZvhBQAJ
But nobody knows when they can enforce for real and forever, affecting Google Play Device certification and Google Pay
zgfg said:
No matter if on v11.0.6 or older, if Bootloader is unlocked, CTS Profile will fail (since the last day or two) and Magisk with Magisk Hide Props Config cannot help
Click to expand...
Click to collapse
Use e.g. Magisk Hide Props Config module for Magisk and chose the option to delete a prop ro.product.model - reboot and CTS Profile will be using Basic attestation mode, so CTS Profile and SafetyNet will pass
If Playstore shows Device is not certified,, go to Settings, Apps, enable System services, search for Google and delete Cache and Data for Google Playstore, Google Services Play and Google Services Framework
Did anyone had a successful backup>restore with TWRP v3.4.0/11.0.6?
i tried to get my backup to phone but i get the famous "extractTarFork() process ended with ERROR: 255"
EDIT: was able to get the backup back. wiped all partitions, reflashed with miflash, put the same version of miui after, then the backup worked fine, phew!
Hello
I am using MIUI global 11.0.8 stock rom. Recently just unlocked the bootloader and trying to figure out how to flash LineageOS in it.
Tried to followed this guide https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-unlock-bootloader-custom-t3839405
But it seems like it is pretty old and not updated. Should i follow this thread or there is something updated? Also feels like i'm missing various things like disabling encryption(!), needs to be on old stock rom for proper installation, customized TWRP recovery and specific Xiaomi programs to do it properly. Could someone identify the missing info/issues i'm having trouble with? TIA.
61zone said:
Hello
I am using MIUI global 11.0.8 stock rom. Recently just unlocked the bootloader and trying to figure out how to flash LineageOS in it.
Tried to followed this guide https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-unlock-bootloader-custom-t3839405
But it seems like it is pretty old and not updated. Should i follow this thread or there is something updated? Also feels like i'm missing various things like disabling encryption(!), needs to be on old stock rom for proper installation, customized TWRP recovery and specific Xiaomi programs to do it properly. Could someone identify the missing info/issues i'm having trouble with? TIA.
Click to expand...
Click to collapse
FIRST OF ALL BACKUP YOUR DATA. Go to fastboot mode and flash latest twrp recovery. Boot to recovery and wipe cache, system and data. Since this is the first time you are installing a custom rom you should format data in twrp. After formatting data reboot to twrp then transfer latest Lineage OS flashable zip in you phone's storage and flash it. Then flash gapps if you want. Then magisk if you want root and DFE if you don't want encryption. That's it. Now reboot to system.
And remember google is your friend.
callmebutcher101 said:
FIRST OF ALL BACKUP YOUR DATA. Go to fastboot mode and flash latest twrp recovery. Boot to recovery and wipe cache, system and data. Since this is the first time you are installing a custom rom you should format data in twrp. After formatting data reboot to twrp then transfer latest Lineage OS flashable zip in you phone's storage and flash it. Then flash gapps if you want. Then magisk if you want root and DFE if you don't want encryption. That's it. Now reboot to system.
And remember google is your friend.
Click to expand...
Click to collapse
Actually there is too much information to handle at once that's why i got confused lol. Thanks for the infos :good:
I'll try to do according to your info.