Related
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 was running Freedom OS CE 2.5 and I dirty flashed official OOS 4.1.0 and got into a bootloop.
I restarted the phone into twrp and it told me that it was read only so I wasn't seeing any zip files. I tried to use repair in the Wipe section by changing file format. I think I chose FAT...I honestly can't remember. But when I swipe to repair and I got stock on updating partition. So I restarted the device into twrp again but this time I'm stock on just the splash screen....won't start.
All I'm getting into is bootloader mode.
Help please
Use fastboot to wipe recovery and flash TWRP again. Alternatively, directly sideload your ROM.
Anova's Origin said:
Use fastboot to wipe recovery and flash TWRP again. Alternatively, directly sideload your ROM.
Click to expand...
Click to collapse
Thank you so much. But what about how I tried changing the format from what it was originally? Should I be worried or that's a minor issue?
ddaharu said:
Thank you so much. But what about how I tried changing the format from what it was originally? Should I be worried or that's a minor issue?
Click to expand...
Click to collapse
You should reformat those partitions that you've changed. Ext4 or f2fs for /data and ext4 for all other partitions. This can be done through either fastboot or TWRP.
Anova's Origin said:
You should reformat those partitions that you've changed. Ext4 or f2fs for /data and ext4 for all other partitions. This can be done through either fastboot or TWRP.
Click to expand...
Click to collapse
Are these the commands I should use?
c:\adb>fastboot erase recovery
c:\adb>fastboot flash recovery twrp
Well as you said, after this I can reenter recovery and reformat the partitions and I should be fine right?
Thanks for all your help man...
ddaharu said:
Are these the commands I should use?
c:\adb>fastboot erase recovery
c:\adb>fastboot flash recovery twrp
Well as you said, after this I can reenter recovery and reformat the partitions and I should be fine right?
Thanks for all your help man...
Click to expand...
Click to collapse
Dont forget the ".img" when referring to images"
c:\adb>fastboot flash recovery twrp.img
Anova's Origin said:
Dont forget the ".img" when referring to images"
c:\adb>fastboot flash recovery twrp.img
Click to expand...
Click to collapse
One last question. Is there any twrp version you'll recommend? Or anyone is good?
ddaharu said:
One last question. Is there any twrp version you'll recommend? Or anyone is good?
Click to expand...
Click to collapse
3.0.4-1 has proven to be the most stable so far.
I've also been using 3.1.0-1 for a while and haven't noticed any issues.
Avoid 3.1.0.0 though, as there has been many reports of issues with it.
Anova's Origin said:
3.0.4-1 has proven to be the most stable so far.
I've also been using 3.1.0-1 for a while and haven't noticed any issues.
Avoid 3.1.0.0 though, as there has been many reports of issues with it.
Click to expand...
Click to collapse
MY PHONE IS RUNNING AGAIN! thanks for your help man.
Btw! Seeing that the positions were somewhat corrupted, I actually had to use stock recovery to sideload the stock ROM then flash TWRP and finally on freedom is 2.6.1
Thanks again, mate. :highfive:
ddaharu said:
I was running Freedom OS CE 2.5 and I dirty flashed official OOS 4.1.0 and got into a bootloop.
I restarted the phone into twrp and it told me that it was read only so I wasn't seeing any zip files. I tried to use repair in the Wipe section by changing file format. I think I chose FAT...I honestly can't remember. But when I swipe to repair and I got stock on updating partition. So I restarted the device into twrp again but this time I'm stock on just the splash screen....won't start.
All I'm getting into is bootloader mode.
Help please
Click to expand...
Click to collapse
I faced a similar issue with twrp , just try to flash twrp again using fastboot mode , in case it does not work again then try to flash it a few more times , it would surely work , I have already tried it , but before that try to factory reset ur phone using twrp and reboot to twrp and only use the first method if the problem exists after that
9891ishu said:
I faced a similar issue with twrp , just try to flash twrp again using fastboot mode , in case it does not work again then try to flash it a few more times , it would surely work , I have already tried it , but before that try to factory reset ur phone using twrp and reboot to twrp and only use the first method if the problem exists after that
Click to expand...
Click to collapse
Thanks. I got through.
I flashed latest TWRP with fastboot command on CMD.
TWRP works but after I reset the TWRP was deleted and I can get STOCK recovery.
I can boot up TWRP only if I connect my device to computer and use command FASTBOOT BOOT RECOVERY.IMG
Why?
If u flashed a rom,.then before booting you must flash the root file or a custom kernel in order to keep the TWRP.
Unleashed by my rooted OP3T on 8.0
I do not flashing another rom, only new open beta versions and flash files.
saarxee said:
I do not flashing another rom, only new open beta versions and flash files.
Click to expand...
Click to collapse
New open beta is another Rom buddy.
Unleashed by my rooted OP3T on 8.0
But I dont need custom kernel and root.
saarxee said:
But I dont need custom kernel and root.
Click to expand...
Click to collapse
You have to flash at least Magisk/SuperSU or custom kernel in order to keep TWRP intact after each reboot. Not sure about modified stock kernels with dm-verity and forceencrypt disabled, they may work too.
This is the nature of stock ROM.
saarxee said:
But I dont need custom kernel and root.
Click to expand...
Click to collapse
OOS enforces encryption and restores the stock recovery when you reboot your phone.
Custom ROMs, custom kernels, and Magisk all prevent that from happening.
If you want plain OOS (stable or Open Beta) and keep TWRP, then use Xennet's patched boot image. See https://forum.xda-developers.com/on...y-force-encryption-op3t-t3688748/post74155053
Sent from my OnePlus3T using XDA Labs
I flashed magisk on TWRP and TWRP deleted again after restart.
What can I do?
Reflash your current ROM via TWRP and flash Magisk right after ROM without restarting
Today I flashed open beta 24 and after that Magisk and wipe dalvik and restart recovery and I got stock recovery and dont TWRP.
saarxee said:
Today I flashed open beta 24 and after that Magisk and wipe dalvik and restart recovery and I got stock recovery and dont TWRP.
Click to expand...
Click to collapse
Like I said, use Xennet's patched boot image.
Sent from my OnePlus3T using XDA Labs
What to do about this file? flash it and install TWRP again? or only flash it and restart to recovery?
Why I need to change my boot file? If my device dont booting up after the flash?
saarxee said:
Why I need to change my boot file? If my device dont booting up after the flash?
Click to expand...
Click to collapse
Because stock will always revert to stock recovery.
If the device doesn't boot, then you're using an incompatible boot image
(it seems that Magisk/SuperSU isn't enough)
I flashed this boot patched image and choose restart to recovery and stock recovery again...
I have the same problem - twrp gets erased after booting in OS Since beta 24
I don't know guys what's wrong with your devices, I'm using Open Beta 24 with custom kernel and TWRP boots everytime.
I use stock kernel, maybe that is the clue.
Viktorrr said:
I use stock kernel, maybe that is the clue.
Click to expand...
Click to collapse
Then maybe you should flash the modified kernel that is especially modified to not restore the stock recovery.....
gizahNL said:
Then maybe you should flash the modified kernel that is especially modified to not restore the stock recovery.....
Click to expand...
Click to collapse
Correct, as I pointed out in this post https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867/post76049932
Sent from my OnePlus3T using XDA Labs
gizahNL said:
Then maybe you should flash the modified kernel that is especially modified to not restore the stock recovery.....
Click to expand...
Click to collapse
BillGoss said:
Correct, as I pointed out in this post https://forum.xda-developers.com/oneplus-3t/help/twrp-deleted-booting-t3769867/post76049932
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
OP said that it didn't work:
I flashed this boot patched image and choose restart to recovery and stock recovery again...
Click to expand...
Click to collapse
So, just got the OTA update to Android Pie for my Mi 8 Global, and want to try flashing TWRP again. Every single version of TWRP I have flashed before has always either fail to boot, or always reboots into recovery and the ROM never loads. Anyone can suggest a real working TWRP file to flash? Do I need to wipe data? Etc. Since TWRP hasn't worked for me at all, I have to root with a roundabout way. Install Magisk Manager, extract and recompile boot.img into patched_boot.img and flash that in fastboot. This gives me roo but no TWRP so I can't flash any custom kernels or ROMs.
Rommco05 said:
Hi, I can't help you with twrp because I still waiting for countdown for unlocked it. From your post I understand u have a stock recovery.img, where u find stock recovery?
Click to expand...
Click to collapse
I just flash the stock boot.img and it reverts everything
Rommco05 said:
Where I can find stock .imgs?
Click to expand...
Click to collapse
Download a stock ROM and grab the boot.img from inside it.
I'm trying to install Hex Kernel on my Mi A2 with Pie, but I'm unable to use TWRP in it. TWRP doesn't boot, and doing the "fastboot boot twrp.img" makes the phone start booting and just shut down. I need another method to flash the kernel.
Can anybody help me, please?
Cuesta4 said:
I'm trying to install Hex Kernel on my Mi A2 with Pie, but I'm unable to use TWRP in it. TWRP doesn't boot, and doing the "fastboot boot twrp.img" makes the phone start booting and just shut down. I need another method to flash the kernel.
Can anybody help me, please?
Click to expand...
Click to collapse
Your bootloader is unlocked?
Aziziamran said:
Your bootloader is unlocked?
Click to expand...
Click to collapse
Yes. Both for normal and critical flashing.
Sent from my Mi A2 using XDA Labs
Cuesta4 said:
Yes. Both for normal and critical flashing.
Click to expand...
Click to collapse
Maybe you should try another recovery such as PBRP or unofficial TWRP..
Aziziamran said:
Maybe you should try another recovery such as PBRP or unofficial TWRP..
Click to expand...
Click to collapse
Tried both already, neither worked. I went back to Oreo and now it's all ok. Better wait for a decent Pie version.
Sent from my Mi A2 using XDA Labs
@Cuesta4 How came back to Oreo since Pie?
Yeah/%# said:
@Cuesta4 How came back to Oreo since Pie?
Click to expand...
Click to collapse
Your phone is Mi A2 or Mi 6X?
If it's the first, just unlock the bootloader and critical flashing then download any stock Oreo ROM and flash it through EDL. You'll then be able to boot custom TWRP and flash a Custom ROM. I'm using CRDroid Pie with Hex Kernel. It's not my favorite, but it's the most stable.
Cuesta4 said:
I'm trying to install Hex Kernel on my Mi A2 with Pie, but I'm unable to use TWRP in it. TWRP doesn't boot, and doing the "fastboot boot twrp.img" makes the phone start booting and just shut down. I need another method to flash the kernel.
Can anybody help me, please?
Click to expand...
Click to collapse
Try installing Hex in the active (on which your is is installed) partition.
Like I have Havoc installed on b, twrp and Magisk installed on a. Installing Hex on b would be my best shot. You can toggle active partitions from reboot menu in twrp.
New TWRP available now for PIE
My friend TWRP 3.3 Supporting Android Pie (version 3.3) is available now.
So all you gotta do is Ublock bootloader . normal and critically.
boot twrp 3.3 using "fastboot boot twrp.img"
copy the hex kernal you want to flash in your phones internal storage and flash it.
this works fine i have done it successfully.