I have a Xperia Z, and installed CM 10 on it, using the following method
Unlocked the bootloader from Sony's site
Downloaded the SDK
Flashboot flash boot boot.IMG
And installed cm.zip from the sdcard.
It worked, in fact, I am typing this from my newly ROM'ed xperia.
So, the question is , if I want to install another ROM now, say CM11 or even a complete different one from xda , what is the process?
Do I just copy the new zip, boot into recovery, and wipe wipe install?
Or do I need to reflash the new boot.IMG from the new ROM every time?
Thanks
endlesslyonline said:
I have a Xperia Z, and installed CM 10 on it, using the following method
Unlocked the bootloader from Sony's site
Downloaded the SDK
Flashboot flash boot boot.IMG
And installed cm.zip from the sdcard.
It worked, in fact, I am typing this from my newly ROM'ed xperia.
So, the question is , if I want to install another ROM now, say CM11 or even a complete different one from xda , what is the process?
Do I just copy the new zip, boot into recovery, and wipe wipe install?
Or do I need to reflash the new boot.IMG from the new ROM every time?
Thanks
Click to expand...
Click to collapse
For flashing CM11
Copy the rom to device
Reboot to recovery
Clear dalvik cache
Flash the rom.
For other rom
Copy rom to device
Copy Gapps to device
Reboot to recovery
Format system
Format cache
Format dalvik cache
Format data(not internal sd)
Flash the rom
Flash Gapps
OK, thanks
So I was correct in thinking the boot.IMG (which is the recovery, right?) Won't have to be flashed again.
endlesslyonline said:
OK, thanks
So I was correct in thinking the boot.IMG (which is the recovery, right?) Won't have to be flashed again.
Click to expand...
Click to collapse
You dont have to flash recovery again.
Hitting thanks would have been easier than writing it!
endlesslyonline said:
OK, thanks
So I was correct in thinking the boot.IMG (which is the recovery, right?) Won't have to be flashed again.
Click to expand...
Click to collapse
well not exactly, the boot.img is the kernel
Pablosch23 said:
well not exactly, the boot.img is the kernel
Click to expand...
Click to collapse
That's my understanding as well. So why is flashing boot.img necessary for installing custom recovery?
Pablosch23 said:
well not exactly, the boot.img is the kernel
Click to expand...
Click to collapse
Ah OK. But am I correct in saying that the (for example) clockworkMOD, or any other custom recovery resides in the boot.IMG
In lamens terms, can we say that the boot.IMG is almost like the bios on a PC?
Sorry for the dumb questions, I just wanna learn some mpre
endlesslyonline said:
Ah OK. But am I correct in saying that the (for example) clockworkMOD, or any other custom recovery resides in the boot.IMG
In lamens terms, can we say that the boot.IMG is almost like the bios on a PC?
Sorry for the dumb questions, I just wanna learn some mpre
Click to expand...
Click to collapse
I think you are right, I'm a also a newbie though..the boot.img contains the kernel (and the ramdisk) where the recovery resides.
Khaiyan said:
That's my understanding as well. So why is flashing boot.img necessary for installing custom recovery?
Click to expand...
Click to collapse
The boot.IMG is the kernel itself
If you flashed wrong one on wrong device so say goodbye to the device
Tapatalk'ed from my Xperiaâ„¢ Z (C6602) running Dirty Unicorns ROM!
endlesslyonline said:
Ah OK. But am I correct in saying that the (for example) clockworkMOD, or any other custom recovery resides in the boot.IMG
In lamens terms, can we say that the boot.IMG is almost like the bios on a PC?
Sorry for the dumb questions, I just wanna learn some mpre
Click to expand...
Click to collapse
Most custom roms include recovery so I dont think you will have to flash boot.img separately again and again
Related
Dear all,
I have tried to flash the pacman rom on my rooted Z, but i had over looked the part on wiping out the data and had restarted my phone. Right now my Z has be stuck on the Pac is loading for a good half of the day. Any assistance would be greatly appreciated. Thank you in advance.
Boot into recovery then wipe and reinstall or restore your backup
Michealtbh said:
Boot into recovery then wipe and reinstall or restore your backup
Click to expand...
Click to collapse
I managed to reboot it, thank you so much!!
remember, flashing CM roms require you to fastboot the boot.img
spazzy1912 said:
remember, flashing CM roms require you to fastboot the boot.img
Click to expand...
Click to collapse
No it doesn't, the boot.img is flashed with the zip in recovery. You only need to use fastboot if you don't already have a custom recovery
Michealtbh said:
No it doesn't, the boot.img is flashed with the zip in recovery. You only need to use fastboot if you don't already have a custom recovery
Click to expand...
Click to collapse
Since when?
From me to you.
XperienceD said:
Since when?
From me to you.
Click to expand...
Click to collapse
That's been the case since I got my XZ ~4 weeks ago
Michealtbh said:
That's been the case since I got my XZ ~4 weeks ago
Click to expand...
Click to collapse
If you have a stock, but bootloader unlocked Phone, you need to flash the kernel first for CWM, so if I flash another ROM that needs a different kernel, just flashing the zip now also flashes the kernel?, which it's never done on Xperia Phones before.
From me to you.
XperienceD said:
If you have a stock, but bootloader unlocked Phone, you need to flash the kernel first for CWM, so if I flash another ROM that needs a different kernel, just flashing the zip now also flashes the kernel?, which it's never done on Xperia Phones before.
From me to you.
Click to expand...
Click to collapse
Correct. Boot partition can be flashed through recovery with the XZ.
Hello XDA,
Since I update to CM12.1 from CM11 (I didn't realised when I applied update, I would croos to CM12.1, so I did it the dirty way ^^)
So since I upadte to CM12.1, my phone started to freeze for anything I'm doing, even unlock it... I decided to clean all the mess I had in the phone, and do a clean installation of CM12.1.
My problem is simple : since I didn't formatted /system, I can't reinstall Gapps.
The recovery installed is now the cyanogen recovery and I don't know how to format /system with this recovery.
Have you any advice to do this ?
Thanks, see you on the thread !
Flash other kernel like tangerine kernel or kernel that already has custom TWRP or CWM recovery or use this kernel to wipe system and flash the kernel (Format -> Advanced format -> check cache, dalvik, system and what you want more). twrp_2.8.6.0-huashan.img
OK ! Thanks ! I'm trying it right after I right it.
I was reading about fastboot to do this. Could this command work too ?
Code:
fastboot flash system system.img
I tried to find a compatible recovery, but this is not simple since I don't know enough things about recoveries.
xdadogs said:
OK ! Thanks ! I'm trying it right after I right it.
I was reading about fastboot to do this. Could this command work too ?
Code:
fastboot flash system system.img
I tried to find a compatible recovery, but this is not simple since I don't know enough things about recoveries.
Click to expand...
Click to collapse
no need to ...install rashr app on your phone and then from it flash the twrp.img that the user above gave it to you
RASHR !!!
Thank you ! This app should be in every "Swiss army knife folder" of android user !
It ask me to flash Philz recovery. What is the best to do ? Philz recovery from Rashr, or the linked TWRP above ?
I really don't know the difference :-/
Hi !
I tried a lot of time to flash the recovery using rashr. I can't get rid of cyanogen recovery.
I installed clockworkmod's ROM manager and it tells me I have two recoveries installed. Cyanogen and TWRP. It was before I try to flash. But now it is the same.
Any advice ?
Sent from my Xperia SP using XDA Free mobile app
The finish touch
I started a new thread to terminate with rashr issues !
You can check it here : I can't flash any recovery on my phone
Phoenix854 told me to use an older version of rashr, and everything worked fine !
Good bye guys, and thank you for the help...
Nexus Root problem. Marshmallow android 6.0 mmra58n
I just have tried everything.
I have a Nexus 6 with marshmallow, and I follow this thread guide http://forum.xda-developers.com/nex...mallow-6-0-t3241976/post64008696#post64008696 to root my phone, but everything goes wrong.
I flash the boot.img and there's no problem at the boot time, then I flash the recovery, and the same, when i reboot it works like a charm.
But everything goes wrong when i flash with twrp the supersu beta v2.52 or v2.56, when i reboot, it doesn't boot...
My phone continue on the first bootanimation (before flash this file it boot then says android, request my pincode and start booting, but no this time, just still doing the [email protected] bootanimation. I am kind of desperate, can somebody help me plz?
DONE, I re-flash system and do it again, thanks for everyone
dont use supersu 2.52, use supersu 2.51 instead http://www.apkmirror.com/apk/chainfire/supersu/supersu-2-51-android-apk-download/
I just flash then the 2.51 with twrp?
Fabiano91 said:
I just flash then the 2.51 with twrp?
Click to expand...
Click to collapse
yes. but you will need that boot.img or any other custom marshmallow kernel as well for root. btw, a boot.img is a kernel. also, you can flash boot.imgs with twrp now too, you just have to select the ability to flash it in twrp.
simms22 said:
yes. but you will need that boot.img or any other custom marshmallow kernel as well for root. btw, a boot.img is a kernel. also, you can flash boot.imgs with twrp now too, you just have to select the ability to flash it in twrp.
Click to expand...
Click to collapse
Ok dude, I will do it now, five minutes more and i write the update here. thanks!!!
It didn't work! I'm stuck!
I've been trying to find how to install a kernel for a few days but i couldn't find any good and updated source. I'm thinking of installing latest helium to my device. Can anyone help me?
ExclusiveBFS said:
I've been trying to find how to install a kernel for a few days but i couldn't find any good and updated source. I'm thinking of installing latest helium to my device. Can anyone help me?
Click to expand...
Click to collapse
Through any recovery is the most easy way, but you have to unlock bootloader first.
Do you even know what it does?
Bigrrd225 said:
Do you even know what it does?
Click to expand...
Click to collapse
Yeah, I do. I just didn't want to flash it and take risk. I must have learned details
HUEguy said:
Through any recovery is the most easy way, but you have to unlock bootloader first.
Click to expand...
Click to collapse
My bootloader is unlocked. And I have the twrp. Thanks!
ExclusiveBFS said:
Yeah, I do. I just didn't want to flash it and take risk. I must have learned details
My bootloader is unlocked. And I have the twrp. Thanks!
Click to expand...
Click to collapse
Then just flash the .zip file via TWRP. Simple. Of course you'll need a ROM compatible with helium otherwise you'll be stuck in a bootloop.
Also goes without saying that you should take a nandroid backup via TWRP first in case something goes wrong.
Edit : When you say you have TWRP, is it part of your current kernel or you flashed it in your FOTA kernel partition via Rashr or something? If its the former then flashing Helium would overwrite TWRP and you could wind up without a working recovery cause I don't think Helium comes with any. Might want to flash TWRP in your FOTA partition with Rashr before you proceed.
XenolithicYardZone said:
Then just flash the .zip file via TWRP. Simple. Of course you'll need a ROM compatible with helium otherwise you'll be stuck in a bootloop.
Also goes without saying that you should take a nandroid backup via TWRP first in case something goes wrong.
Edit : When you say you have TWRP, is it part of your current kernel or you flashed it in your FOTA kernel partition via Rashr or something? If its the former then flashing Helium would overwrite TWRP and you could wind up without a working recovery cause I don't think Helium comes with any. Might want to flash TWRP in your FOTA partition with Rashr before you proceed.
Click to expand...
Click to collapse
I was on latest candy5, i flashed adrian dc's twrp from recovery but now I'm installing the stock ftf, I will try carbon lp rom. When the installation completed, I will flash adrian dc's twrp again. Then I will flash the helium kernel with twrp. Is there a problem with that? Should I install twrp with rashr?
ExclusiveBFS said:
I was on latest candy5, i flashed adrian dc's twrp from recovery but now I'm installing the stock ftf, I will try carbon lp rom. When the installation completed, I will flash adrian dc's twrp again. Then I will flash the helium kernel with twrp. Is there a problem with that? Should I install twrp with rashr?
Click to expand...
Click to collapse
If you're gonna flash stock firmware via Flashtool then your FOTA recovery will be wiped out. How are you gonna flash TWRP & Carbon LP rom when you don't have a recovery in the first place?
http://forum.xda-developers.com/xperia-sp/development/recovery-twrp-3-0-0-touch-recovery-t3309938
The recovery from the above thread is flashable but you still need an working recovery on your device to be able to do it right? What you can do it use the fastboot bootable image and install whatever you want if you're gonna go stock.
Actually you only need Rashr if you wanna stay stock but still want a working recovery.
XenolithicYardZone said:
If you're gonna flash stock firmware via Flashtool then your FOTA recovery will be wiped out. How are you gonna flash TWRP & Carbon LP rom when you don't have a recovery in the first place?
http://forum.xda-developers.com/xperia-sp/development/recovery-twrp-3-0-0-touch-recovery-t3309938
The recovery from the above thread is flashable but you still need an working recovery on your device to be able to do it right? What you can do it use the fastboot bootable image and install whatever you want if you're gonna go stock.
Actually you only need Rashr if you wanna stay stock but still want a working recovery.
Click to expand...
Click to collapse
I guess I couldn't explained my situation well. I installed carbon rom just now, and flashed gapps. I didn't check if carbon comes with a recovery but if it comes, I'm going to flash adrian dc's twrp through stock recovery. That's what I'm asking, is there a difference between using rashr to install twrp or flashing through recovery.
ExclusiveBFS said:
I guess I couldn't explained my situation well. I installed carbon rom just now, and flashed gapps. I didn't check if carbon comes with a recovery but if it comes, I'm going to flash adrian dc's twrp through stock recovery. That's what I'm asking, is there a difference between using rashr to install twrp or flashing through recovery.
Click to expand...
Click to collapse
Carbon provides CM recovery. Flash TWRP only through recovery, don't use Rashr.
ExclusiveBFS said:
I guess I couldn't explained my situation well. I installed carbon rom just now, and flashed gapps. I didn't check if carbon comes with a recovery but if it comes, I'm going to flash adrian dc's twrp through stock recovery. That's what I'm asking, is there a difference between using rashr to install twrp or flashing through recovery.
Click to expand...
Click to collapse
The recovery that comes with Carbon is most probably Cyanogen recovery which will not let you flash unsigned zip files like custom kernels & roms, SuperSU, Xposed, etc.
Its the reason why people install a recovery in their FOTA partitions because installing new kernels or roms (which include their own kernel) wipes out the previous recovery since Xperia phones esp older one's like ours don't have a separate recovery partition - the recovery is part of the kernel so it gets replaced by whatever came (or didn't) with the new kernel or rom. Atleast that's how it works to the best of my knowledge.
With fastboot, you could boot the device into TWRP recovery using the twrp-3.0.0-rX-boot-huashan.img file and the command "fastboot boot *filename*.img". This way its just temporary and doesn't permanently flash anything. Once in the recovery, flash the rom, kernel, recovery and you are done. That's how I did it on my Mi4i though you might want to confirm but since the description next to it says fastboot bootable, I guessing it works on the same principal.
Edit : If the kernel creator says no Rashr then its no Rashr.
XenolithicYardZone said:
The recovery that comes with Carbon is most probably Cyanogen recovery which will not let you flash unsigned zip files like custom kernels & roms, SuperSU, Xposed, etc.
Its the reason why people install a recovery in their FOTA partitions because installing new kernels or roms (which include their own kernel) wipes out the previous recovery since Xperia phones esp older one's like ours don't have a separate recovery partition - the recovery is part of the kernel so it gets replaced by whatever came (or didn't) with the new kernel or rom. Atleast that's how it works to the best of my knowledge.
With fastboot, you could boot the device into TWRP recovery using the twrp-3.0.0-rX-boot-huashan.img file and the command "fastboot boot *filename*.img". This way its just temporary and doesn't permanently flash anything. Once in the recovery, flash the rom, kernel, recovery and you are done. That's how I did it on my Mi4i though you might want to confirm but since the description next to it says fastboot bootable, I guessing it works on the same principal.
Edit : If the kernel creator says no Rashr then its no Rashr.
Click to expand...
Click to collapse
I find that flashing TWRP from CM recovery and then Helium from TWRP is much simpler than flashing TWRP as a kernel in the boot partition, then flashing the rom again and the kernel.
Tomoms said:
Carbon provides CM recovery. Flash TWRP only through recovery, don't use Rashr.
Click to expand...
Click to collapse
I flashed helium v5 for lollipop through twrp 3.0.0 and rebooted. It's not booted yet, i'm waiting for 2 minutes and the screen is black. Is it normal?
Tomoms said:
I find that flashing TWRP from CM recovery and then Helium from TWRP is much simpler than flashing TWRP as a kernel in the boot partition, then flashing the rom again and the kernel.
Click to expand...
Click to collapse
Wait hang on, CM recovery lets you flash custom zip files now without moaning about file verification? Since when?
Yes that's why I asked him to temporarily boot up with the TWRP img and then flash whatever he liked from it but hey if you can flash stuff via CM recovery now then that's one less step to worry about.
Also why no Rashr? I haven't used it in a while that's why I am asking.
---------- Post added at 05:10 PM ---------- Previous post was at 05:07 PM ----------
ExclusiveBFS said:
I flashed helium v5 for lollipop through twrp 3.0.0 and rebooted. It's not booted yet, i'm waiting for 2 minutes and the screen is black. Is it normal?
Click to expand...
Click to collapse
You mean black screen after the Sony splash screen? Is that rom compatible with Helium?
XenolithicYardZone said:
Wait hang on, CM recovery lets you flash custom zip files now without moaning about file verification? Since when?
Yes that's why I asked him to temporarily boot up with the TWRP img and then flash whatever he liked from it but hey if you can flash stuff via CM recovery now then that's one less step to worry about.
Also why no Rashr? I haven't used it in a while that's why I am asking.
---------- Post added at 05:10 PM ---------- Previous post was at 05:07 PM ----------
You mean black screen after the Sony splash screen? Is that rom compatible with Helium?
Click to expand...
Click to collapse
First, yes it lets you flash custom zip files, that's what I was trying to tell I always used cm recovery to install twrp
And I haven't used rashr before, I didn't know how to use it. So I flashed it with cm recovery and perfectly installed.
About helium, my phone finally booted after 9 minutes, how I scared
ExclusiveBFS said:
First, yes it lets you flash custom zip files, that's what I was trying to tell I always used cm recovery to install twrp
And I haven't used rashr before, I didn't know how to use it. So I flashed it with cm recovery and perfectly installed.
About helium, my phone finally booted after 9 minutes, how I scared
Click to expand...
Click to collapse
Sorry man didn't know that CM recovery lets you do that now. Been out of the loop for a while.
Lol yeah I can relate but as long as you can see a splash screen, you're good and when you don't, Flashtool is your light in the darkness :victory:
ExclusiveBFS said:
I flashed helium v5 for lollipop through twrp 3.0.0 and rebooted. It's not booted yet, i'm waiting for 2 minutes and the screen is black. Is it normal?
Click to expand...
Click to collapse
The reboot button is broken on TWRP. Causes black screen for a long time. You must always use the Power off option instead.
XenolithicYardZone said:
Sorry man didn't know that CM recovery lets you do that now. Been out of the loop for a while.
Lol yeah I can relate but as long as you can see a splash screen, you're good and when you don't, Flashtool is your light in the darkness :victory:
Click to expand...
Click to collapse
CM recovery lets you flash signed zip, and TWRP is provided in a signed zip, while even though Helium is provided in a signed zip, it can't be flashed.
Tomoms said:
The reboot button is broken on TWRP. Causes black screen for a long time. You must always use the Power off option instead.
CM recovery lets you flash signed zip, and TWRP is provided in a signed zip, while even though Helium is provided in a signed zip, it can't be flashed.
Click to expand...
Click to collapse
@Tomoms, @XenolithicYardZone Thanks for all your help, I used more than 10 roms so far but never used a custom kernel before. You two helped me a lot
Tomoms said:
The reboot button is broken on TWRP. Causes black screen for a long time. You must always use the Power off option instead.
CM recovery lets you flash signed zip, and TWRP is provided in a signed zip, while even though Helium is provided in a signed zip, it can't be flashed.
Click to expand...
Click to collapse
Yeah kinda guessed it was signed cause in all my time flashing roms, I have never known CM recovery to allow the flashing of unsigned zips. So why doesn't it work with Helium if its signed?
ExclusiveBFS said:
@Tomoms, @XenolithicYardZone Thanks for all your help, I used more than 10 roms so far but never used a custom kernel before. You two helped me a lot
Click to expand...
Click to collapse
Your welcome man. As a famous author once said, "Help will always be given at XDA to those who ask for it. "
XenolithicYardZone said:
Yeah kinda guessed it was signed cause in all my time flashing roms, I have never known CM recovery to allow the flashing of unsigned zips. So why doesn't it work with Helium if its signed?
Click to expand...
Click to collapse
Because CM recovery sucks
Tomoms said:
Because CM recovery sucks
Click to expand...
Click to collapse
True that!
I would like to know if someone has managed to root with magisk from CMD without twrp?
You can root with magisk on any miui 14 without using twrp.Just get the boot image from the rom,install magisk apk and patch the boot.img, reboot to fastboot mode ,open cmd and write "fastboot flash boot_ab boot.img" just replace boot.img with the name of your generated magisk boot. The boot image is located in different location according to the rom you are using .Normal miui recovery rom contain file that called payload.bin.You need to download this tool https://github.com/tobyxdd/android-ota-payload-extractor. Follow the instructions in the link and you will get the boot.img .If you using miui.eu rom ,you just need to extract the zip and you will see the boot.img. Also if you want to use Miui 14 global or EEA, you can use the fastboot rom that I created and the zip file contain the boot.img .You can get download link on this thread link https://forum.xda-developers.com/t/fastboot-version-of-miui-14-eea-global-and-older-miui-13.4381953/ .
or965 said:
You can root with magisk on any miui 14 without using twrp.Just get the boot image from the rom,install magisk apk and patch the boot.img, reboot to fastboot mode ,open cmd and write "fastboot flash boot_ab boot.img" just replace boot.img with the name of your generated magisk boot. The boot image is located in different location according to the rom you are using .Normal miui recovery rom contain file that called payload.bin.You need to download this tool https://github.com/tobyxdd/android-ota-payload-extractor. Follow the instructions in the link and you will get the boot.img .If you using miui.eu rom ,you just need to extract the zip and you will see the boot.img. Also if you want to use Miui 14 global or EEA, you can use the fastboot rom that I created and the zip file contain the boot.img .You can get download link on this thread link https://forum.xda-developers.com/t/fastboot-version-of-miui-14-eea-global-and-older-miui-13.4381953/ .
Click to expand...
Click to collapse
ive use your method but my phone still gone to bootloop. im using eu rom currently.
martin132014 said:
ive use your method but my phone still gone to bootloop. im using eu rom currently.
Click to expand...
Click to collapse
What did you do? I wrote several options.
Hey Guys!!!
4 Android 13 we not use Magisk!!! We use Lygisk its a Version direct 4 Android 13 and works great!!!
you can choose witch File you would Patch Boot.img/Recovery.img!! So you can Boot with boot.img normaly into Rooted System!!! And when you Patch the Recovery.img and Flash this, you must start with the Button-Combo that starts Recovery-Mode, so its start the Rooted System, when you start it normaly not over Recovery-Mode the System is Not Rooted!!! Thats the Difference between the 2 Methods,and a Patched Recovery dont set you in Bootloop!!!
Lygisk APK ZIP
System23 said:
Hey Guys!!!
4 Android 13 we not use Magisk!!! We use Lygisk its a Version direct 4 Android 13 and works great!!!
you can choose witch File you would Patch Boot.img/Recovery.img!! So you can Boot with boot.img normaly into Rooted System!!! And when you Patch the Recovery.img and Flash this, you must start with the Button-Combo that starts Recovery-Mode, so its start the Rooted System, when you start it normaly not over Recovery-Mode the System is Not Rooted!!! Thats the Difference between the 2 Methods,and a Patched Recovery dont set you in Bootloop!!!
Lygisk APK ZIP
Click to expand...
Click to collapse
Hi, sorry, but i bit confused about the method here. You mean to just patch either or both. This method is for fastboot or twrp. Sorry if im asking noob question.
or965 said:
What did you do? I wrote several options.
Click to expand...
Click to collapse
I use the method for eu that you posted. First i install magisk 25.2 and then i patch the rom boot.img. I boot to fastboot and flash the patch boot.img using the command. It flash successful then i reboot. But it still bootloop.
And for context, im using Eu weekly rom, not stable and twrp-3.7.0_12-v7.2_A13-venus-skkk.img for recovery. The recovery im using in eu rom forum method for installation.
martin132014 said:
Hi, sorry, but i bit confused about the method here. You mean to just patch either or both. This method is for fastboot or twrp. Sorry if im asking noob question.
Click to expand...
Click to collapse
All good say what you think!! not booth one of them boot.img or recovery.img!! you can flash zip via TWRP than you dont need other steps!!! you can install the Apk and Patch the Boot.img or recovery.img!!! than you can flash it in fastboot, twrp Image or twrp terminal!! choose your method
martin132014 said:
And for context, im using Eu weekly rom, not stable and twrp-3.7.0_12-v7.2_A13-venus-skkk.img for recovery. The recovery im using in eu rom forum method for installation.
Click to expand...
Click to collapse
and what your experience with that!!! Tell me why you like this!!!
System23 said:
All good say what you think!! not booth one of them boot.img or recovery.img!! you can flash zip via TWRP than you dont need other steps!!! you can install the Apk and Patch the Boot.img or recovery.img!!! than you can flash it in fastboot, twrp Image or twrp terminal!! choose your method
Click to expand...
Click to collapse
I guess i should post how I'm doing with the root situation. I guess i miss the part that you need to format the rom after installing new rom. And then do flash the boot.img steps. Now magisk is installed and no bootloop.
I on the other hand do format and flash rom. And continue the boot.img process. I guess that's why it doesn't work.
I'm in the process on restoring my data.
martin132014 said:
I guess i should post how I'm doing with the root situation. I guess i miss the part that you need to format the rom after installing new rom. And then do flash the boot.img steps. Now magisk is installed and no bootloop.
I on the other hand do format and flash rom. And continue the boot.img process. I guess that's why it doesn't work.
I'm in the process on restoring my data.
Click to expand...
Click to collapse
ok a Tip to you!!! when you only Backup Data Partition you can restore it and all Contacts,SMS,Accounts,Apps are availibile again on new ROM!!!
Why you dont use the Magisk.zip and flash it via TWRP after Flash ROM!!! you can rename Magisk.apk to Magisk.zip and flash it!! than you dont need other steps to Root!!! when it dosnt work use the recovery.img to Patch it and try this Method for Rooting, but dont forgett when ya do so you need to try the Buttons-Combo to start in Recovery to boot the System in Root and you have no Recovery-Mode at this Method!!! Also to use Recovery again you must Flash it again via Fastboot!!
And in TWRP use the WIPE Option to make a Factory Reset or WIPE a Single Partition, after some Flashing CROMS its needed to be WIPE the Data Partition!!!
martin132014 said:
I guess i should post how I'm doing with the root situation. I guess i miss the part that you need to format the rom after installing new rom. And then do flash the boot.img steps. Now magisk is installed and no bootloop.
I on the other hand do format and flash rom. And continue the boot.img process. I guess that's why it doesn't work.
I'm in the process on restoring my data.
Click to expand...
Click to collapse
you can ask me what you would i share my Informations with ya!!! when iam not knowing iam googleing it out to find a solution!! the talk we have start are hope helpfully!! when ya have intresst we can stay in kontakt and make what we can, even its public 4 all or PM!!! PS i must not hide my Knowledge, but PM its OK too!!!