Can i flash direct android 7.0 zip files in unlocked bootlaoder using sunshine.Does this cause some problems directly?
Unless I am misunderstanding the question, you unlock your bootloader with Sunshine. You flash zipped files with TWRP recovery.
TWRP is free, very useful custom recovery. You can make backups, flash zipped files, etc. With an unlocked bootloader, there's no reason to keep stock recovery. We have official TWRP recovery for Quark from @bhb27.
[RECOVERY][OFFICIAL TWRP 3.0.2-0][For all Quark][Moto Maxx/Turbo and Droid Turbo]
http://forum.xda-developers.com/mot...recovery-twrp-2-8-7-0-touch-recovery-t3180308
Related
Ok so i unlocked the bootloader, installed twrp 2.7.1.1, and when i flashed SuperSU.zip file it is stuck on the "warning bootloader unlocked screen." I can get back to the trwp bootloader and clear cache and data, but every time i try to boot to system it stays on the warning bootloader unlocked screen. please help..
running marshmallow 6.0
KyleSaki714 said:
Ok so i unlocked the bootloader, installed twrp 2.7.1.1, and when i flashed SuperSU.zip file it is stuck on the "warning bootloader unlocked screen." I can get back to the trwp bootloader and clear cache and data, but every time i try to boot to system it stays on the warning bootloader unlocked screen. please help..
running marshmallow 6.0
Click to expand...
Click to collapse
You should read the threads about installing custom recoveries and rooting in the general section.
TWRP 2.7.1.1 is wayyy to old, you should use TWRP 3.0.0.0 when you're flashing things in marshmallow.
And you should give more info, which version of superSU did you flash?
There is only one beta version which is able to root marshmallow without a modified Boot.img, it's BETA-SuperSU-v2.62-3-20151211162651.
http://download.chainfire.eu/751/SuperSU/BETA-SuperSU-v2.62-3-20151211162651.zip
Read the thread about "[Simplified] [Root Method] [Titan] [Marshmallow 6.0] Without Modifying boot.img" : http://forum.xda-developers.com/moto-g-2014/general/simplified-modifying-boot-img-t3317605
and "[GUIDE] [Titan] [MM, LP, KK] [Unlock + Root + Backup + Restore + Downgrade" : http://forum.xda-developers.com/moto-g-2014/general/xt1063-t3018818 .
Flash twrp 3.0.0.0 ( https://dl.twrp.me/titan/ )and then the BETA-SuperSU-v2.62-3-20151211162651, you can try to flash the beta superSU above with your old recovery but it's not recommended. Your choice but then change recovery afterwards.
Sent with somewhat
Wolfcity said:
You should read the threads about installing custom recoveries and rooting in the general section.
TWRP 2.7.1.1 is wayyy to old, you should use TWRP 3.0.0.0 when you're flashing things in marshmallow.
And you should give more info, which version of superSU did you flash?
There is only one beta version which is able to root marshmallow without a modified Boot.img, it's BETA-SuperSU-v2.62-3-20151211162651.
http://download.chainfire.eu/751/SuperSU/BETA-SuperSU-v2.62-3-20151211162651.zip
Read the thread about "[Simplified] [Root Method] [Titan] [Marshmallow 6.0] Without Modifying boot.img" : http://forum.xda-developers.com/moto-g-2014/general/simplified-modifying-boot-img-t3317605
and "[GUIDE] [Titan] [MM, LP, KK] [Unlock + Root + Backup + Restore + Downgrade" : http://forum.xda-developers.com/moto-g-2014/general/xt1063-t3018818 .
Flash twrp 3.0.0.0 ( https://dl.twrp.me/titan/ )and then the BETA-SuperSU-v2.62-3-20151211162651, you can try to flash the beta superSU above with your old recovery but it's not recommended. Your choice but then change recovery afterwards.
Sent with somewhat
Click to expand...
Click to collapse
Ok thanks, I did actually find out twrp was an old version so I flashed a lollipop 5.0.2 Titan rom to escape the bootloop, then rooted with Kingroot(I was lazy to install SuperSU) then installed the latest version of twrp.
It's actually my first time attempting rooting and unlocking the bootloader, so yea at least I learned something from this. :good:
KyleSaki714 said:
Ok thanks, I did actually find out twrp was an old version so I flashed a lollipop 5.0.2 Titan rom to escape the bootloop, then rooted with Kingroot(I was lazy to install SuperSU) then installed the latest version of twrp.
It's actually my first time attempting rooting and unlocking the bootloader, so yea at least I learned something from this. :good:
Click to expand...
Click to collapse
Good to hear that you fixed your problem. One thing: Don't use Kingroot.
It's a very unstable way to root your device and a suspicious app.
Just flash superSU, it's stable and easy to do and it doesn't send data to unknown sources. Just an advice.
Sent with somewhat
I have managed to root, install a custom recovery and unlock the bootloader.
I'm currently trying to install cyanogenmod 13.0 6.0.1 but whenever I flash the boot.img I extracted from the rom I get a bootloop?
What are the procedure from updating from KK to MM?
It's been a while since I owned a Sony Xperia help a brother out :good:
Don't flash boot img.Just Do wipes and flash the rom.
4.3 is jellybean(jb)
If you're using stock firmware 4.3 jellybean.. Then you need first to unlock your bootloader then root your phone using towel root or any other root app. after that you can fastboot boot.img or twrp.img to boot to recovery and flash cm13.
Sent from my Xperia SP using Tapatalk
You should flash TWRP 3.0.2 with Flashtool (via Fastboot option on Flashtool).
After flashing, power up your phone and boot to twrp.(if the flash was successfull, it boots to the twrp automatically).
Then Wipe system+data+dalvik cache+cache from TWRP.
Flash the CM13, flash Gapps.
Enjoy!
I've xt1068. It is unrooted. So it has unlocked bootloader. It has twrp and I've marshmallow update for my phone in zip format. My phone is not connecting to pc. I've tried so many ways to connect it. So can I directly flash through twrp without rooting? If so how? And if not, can I flash it after rooting? I'm planning to root it using SuperSU zip.
Do you have stock firmware in zip format if you have such file then I think you can't flash it through twrp, you can only flash custom roms and twrp backup via twrp not stock image files
Is it OK to switch between Android 6 and Android 7 in TWRP 3.0.2.0 backups?
I would like to use both Androids on my phone until Xposed will be ready for Nougat, but I'm afraid of file structure, partitions and so on.
Both Androids are rooted and no encryption.
Restore backup of Android M won't mess with Nougat will it?
belek1979 said:
Is it OK to switch between Android 6 and Android 7 in TWRP 3.0.2.0 backups?
I would like to use both Androids on my phone until Xposed will be ready for Nougat, but I'm afraid of file structure, partitions and so on.
Both Androids are rooted and no encryption.
Restore backup of Android M won't mess with Nougat will it?
Click to expand...
Click to collapse
No problem provided u have N bootloader to use N ROMs. N bootloader is backward compatible. Nutty Nexus thread has link to latest N bootloader and radio combined in one zip to be flashed in TWRP 3.0.2.0 before flashing N roms
HueyT said:
No problem provided u have N bootloader to use N ROMs. N bootloader is backward compatible. Nutty Nexus thread has link to latest N bootloader and radio combined in one zip to be flashed in TWRP 3.0.2.0 before flashing N roms
Click to expand...
Click to collapse
Thank you for your answer.
I'm going to update from ADB (factory image):
1 fastboot flash bootloader
2 fastboot flash radio
3 fastboot restart-bootloader
4 fastboot flash boot
5 fastboot flash system
6 entering twrp recovery from bootloader
7 flash SuperSU (root and no encryption)
TWRP doesn't backup BL or radio?
Why not use MultiROM so you can actually switch between them and not wipe/restore all your partitions each time you want to switch back and forth? I think it should work between MM and N so long as the kernels in each ROM are kexec patched.
belek1979 said:
Thank you for your answer.
I'm going to update from ADB (factory image):
1 fastboot flash bootloader
2 fastboot flash radio
3 fastboot restart-bootloader
4 fastboot flash boot
5 fastboot flash system
6 entering twrp recovery from bootloader
7 flash SuperSU (root and no encryption)
TWRP doesn't backup BL or radio?
Click to expand...
Click to collapse
TWRP only backs up \system, \data, \boot, \recovery, \EFS (\cache also but who cares)
You could flash like that but you could also just flash debloated N rom from tupac4u or DanvH straight from TWRP (after flashing N bootloader and radio zip).
Multi-rom can be tricky for Noobs
EDIT: Here are the useful links: N radio and bootloader in 1 flashable zip in TWRP by RatchetPanda: https://www.androidfilehost.com/?fid=312978532265362066
Here is tupac4u latest debloated N rom:
https://mega.nz/#!e9JDyRRY!mJl2CJeWTmlhELPbHdHdzT1GHE15awdlqd3Q4sIED70
(needs MEGA app to download or use "desktop" emulator on mobile browser to download)
When getting a custom ROM and wanting to root it with Magisk, should I patch and flash the boot.img of the specific ROM or the boot.img of the factory FW
hazoky01 said:
When getting a custom ROM and wanting to root it with Magisk, should I patch and flash the boot.img of the specific ROM or the boot.img of the factory FW
Click to expand...
Click to collapse
Flash TWRP or orange fox and then Magisk zip in the recovery
That's it
But of course the bootloader has to be unlocked
The boot img of the current ROM you're using like example boot img of Pixel Experience if you're using that. Usually the boot img is inside the ROM zip when you installed it. But this method is for devices without custom recovery. Of course it will work but I suggest to follow what Laptapper suggested to flash a custom recovery (orange fox r12.1_2 or twrp 3.7.0) and just flash magisk.zip.