Related
Hello
After searching the internet for good 30-40 minutes I found the Stock OnePlus 2 recovery image. I am returning my unit so needed it to be fully stock.
Download: https://www.dropbox.com/s/8np35kw71i222as/OPT Stock Recovery.7z?dl=0
Thank you!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! Been searching for this for past hour!!!!!!
Hi,
Thank you very much.
I'm also returning my phone to oneplus and i had unlocked and rooted the phone like you.
May i know how you restore the stock ROM and recovery?
thank you
Why do you need stock recovery for that? I just wiped everything on mine and when I rebooted from twrp I chose not to protect twrp. Rma was approved so I guess they were satisfied with that.
Sent from my A0001 using Tapatalk
granfot said:
Why do you need stock recovery for that? I just wiped everything on mine and when I rebooted from twrp I chose not to protect twrp. Rma was approved so I guess they were satisfied with that.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
What do you means by "wipe everything"? include internal storage?
And i heard that official twrp dont have the option of "not to protect twrp".
werthechamp said:
What do you means by "wipe everything"? include internal storage?
And i heard that official twrp dont have the option of "not to protect twrp".
Click to expand...
Click to collapse
Yes, including internal storage.
That I didn't know, but you don't void warranty by installing custom recovery or rooting so it shouldn't be an issue either way.
Sent from my A0001 using Tapatalk
granfot said:
Yes, including internal storage.
That I didn't know, but you don't void warranty by installing custom recovery or rooting so it shouldn't be an issue either way.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Is this the recovery of the international version or chinese?
thx
This is not the international version but chinese . Im looking for the english version, searched everywhere but unable to find it. wtf
1. Download the latest signed flashable zip from here.
2. Press thanks for Spannaa.
3. Extract recovery.img from the zip file with 7zip.
4. Flash it from fastboot using the "flash recovery recovery.img" command.
CafeKampuchia said:
1. Download the latest signed flashable zip from here.
2. Press thanks for Spannaa.
3. Extract recovery.img from the zip file with 7zip.
4. Flash it from fastboot using the "flash recovery recovery.img" command.
Click to expand...
Click to collapse
Problem: The signed flashable zips don't contain recovery.img
Spannaa said:
Problem: The signed flashable zips don't contain recovery.img
Click to expand...
Click to collapse
Hmmmm... that would be a problem. :/ Thanks for pointing that out.
CafeKampuchia said:
Hmmmm... that would be a problem. :/ Thanks for pointing that out.
Click to expand...
Click to collapse
I Installed the 2.0 manually...then update ota...now I have stock recovery.
zat0x said:
This is not the international version but chinese . Im looking for the english version, searched everywhere but unable to find it. wtf
Click to expand...
Click to collapse
Hey, I don't know if you ever found the stock recovery but another member had posted fastboot images in the OnePlus2 Android Development section.
I haven't tested out the recovery myself, but you can check to see if it's the English one.
All Fastboot images: https://www.androidfilehost.com/?w=files&flid=40701
Stock Recovery Image: https://www.androidfilehost.com/?fid=24052804347834210
Hope this helps.
Using these, how would I return my OP2 to completely stock recovery and kernel?
Thanks
keshavmot2 said:
Using these, how would I return my OP2 to completely stock recovery and kernel?
Thanks
Click to expand...
Click to collapse
Good question! Want to know that too...
keshavmot2 said:
Using these, how would I return my OP2 to completely stock recovery and kernel?
Thanks
Click to expand...
Click to collapse
1:
Flash the full stock rom from OxygenOS 2.1.1: http://forum.xda-developers.com/showthread.php?t=3209863
2: Flash the OxygenOS 2.1.2 zip from the same post
3: flash the stock recovery from tgis thread
Hope I helped you
Download OP2 Stock Recovery from Official Site: https://s3.amazonaws.com/oxygenos.oneplus.net/OP2_recovery.img
It seems OnePlus uses AWS to host all of their OTA's.
E.G. https://s3.amazonaws.com/oxygenos.oneplus.net/OnePlus2Oxygen_14_OTA_012_all_1602261837.zip ( This is for OxygenOS 2.2.1 releases in 2012 26th Feb - 970MB )
Recent ROM Downloads of OP2: http://downloads.oneplus.net/devices/oneplus-2/ ( Includes Marshmallow Beta OxygenOS 3.0 , however, seems the ROM has Battery issue, major )
matrixdefalco said:
I Installed the 2.0 manually...then update ota...now I have stock recovery.
Click to expand...
Click to collapse
I did the same thing and it worked for me If somebody is still facing this issue
anyone knows how the flash the stock recovery from mac???
krishp said:
anyone knows how the flash the stock recovery from mac???
Click to expand...
Click to collapse
One "?" is enough dude..
You have to install adb for Mac (http://stackoverflow.com/questions/31374085/installing-adb-on-mac-os-x), enable USB Debugging on your phone, reboot into bootloader mode :
Code:
adb reboot-bootloader
then go into:
Code:
su
and then
Code:
fastboot devices
fastboot flash <recovery_name>.img
This is a stock boot.img I use where I edited ramdisk and sepolicy for regular root. I also changed force encryption to encryptable and permissive Enforcing
I will continue to post new boot.img each update here.
Downloads
NBF26f big thanks for the update was done by @googy_anas
https://drive.google.com/file/d/0B4yuQy7Zn1WSdTFCMEtRbXpSREE/view?usp=drivesdk
NBD91K
https://www.androidfilehost.com/?fid=529152257862678470
NRD90U
https://drive.google.com/file/d/0B6DDdWOgUhVVMFpGTFlTQWVQOW8/view
@holla420 good looks on doing boot.img again.
NPD90G
https://www.androidfilehost.com/?fid=24591023225178833
big shout out to my homie @holla420 for knocking out this boot.img for everyone.
NPD56N
https://www.androidfilehost.com/?fid=24572369242686570
big shout out to my homie @holla420 for knocking out this boot.img for everyone
NPD35K
https://drive.google.com/file/d/0B4yuQy7Zn1WSQmdfZ3dNMW02Z3c/view?usp=drivesdk
Decrypted boot.IMG and no DM check for NPC91K
https://drive.google.com/file/d/0B4yuQy7Zn1WSVVJSbWpGaU1sTlU/view?usp=drivesdk
Decrypted boot.IMG for Android N build NPC56W
https://drive.google.com/file/d/0B4yuQy7Zn1WSZm11VE1KZmx3RG8/view?usp=sharing
Decrypted boot.IMG for Android N build inital release
https://drive.google.com/file/d/0B4VEhClrJEWpekpneFdUWkhBX1E/view
Big thanks to my good friend and co-dev @toknitup420 don't forget to thank him you see him around
works perfect. Good looks @Tigerstown.
Sent from my Nexus 6P using Tapatalk
Tigerstown said:
This is a stock boot.img I use where I edited ramdisk and sepolicy for regular root. I also changed force encryption to encryptable.
Download https://drive.google.com/file/d/0B4yuQy7Zn1WSTnE4bmxNZXRMdGs/view?usp=docslist_api
Click to expand...
Click to collapse
Eli5, What's the point of a normal root when you can just flash the systemless root and be done with it?
floepie said:
Eli5, What's the point of a normal root when you can just flash the systemless root and be done with it?
Click to expand...
Click to collapse
what's the point of systemless root is what you should be asking yourself
Tigerstown said:
what's the point of systemless root is what you should be asking yourself
Click to expand...
Click to collapse
Because you don't have to rely on the generosity of someone modifying the boot image to accommodate the older method, thereby requiring only 1 recovery flash?
floepie said:
Because you don't have to rely on the generosity of someone modifying the boot image to accommodate the older method, thereby requiring only 1 recovery flash?
Click to expand...
Click to collapse
Why are you even in this thread if you have no interest in using traditional root. Stop trolling and leave the thread. If you don't want it, then don't use it. It's been posted for users that want traditional root and don't know how to mod their own boot.img. Also you're incorrect about the amount of flashing in recovery. You still only need to flash one zip. The SuperSU zip. The boot image gets flashed in fastboot. Soooooooo when you're updating to newest software from Google, you simply use this modded boot.img instead of the one from Google. So technically there are absolutely no extra steps taken in order to use this boot.img.
Sent from my Nexus 6P using Tapatalk
Huh? No, really, I think I'm too old to be "trolling". Just curious to know if there are any potential advantages of the traditional method - not from a selfish perspective, but more out a, well, curiosity. Can we just keep this to the level of a civil "discussion"?
Is this still Enforcing? Is it possible to get a stock or close to stock kernel that is Permissive for a project I'm working on? I just need a boot.img. Thanks!
toknitup420 said:
Why are you even in this thread if you have no interest in using traditional root. Stop trolling and leave the thread. If you don't want it, then don't use it. It's been posted for users that want traditional root and don't know how to mod their own boot.img. Also you're incorrect about the amount of flashing in recovery. You still only need to flash one zip. The SuperSU zip. The boot image gets flashed in fastboot. Soooooooo when you're updating to newest software from Google, you simply use this modded boot.img instead of the one from Google. So technically there are absolutely no extra steps taken in order to use this boot.img.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I agree and thank you. as I am traditional root user. thank you for the boot img
Sent from my Nexus 9
floepie said:
Eli5, What's the point of a normal root when you can just flash the systemless root and be done with it?
Click to expand...
Click to collapse
Why do you guys attack the above person for asking "explain like I am 5, why does anyone want this?"
Tigerstown said:
what's the point of systemless root is what you should be asking yourself
Click to expand...
Click to collapse
toknitup420 said:
Why are you even in this thread if you have no interest in using traditional root. Stop trolling and leave the thread. If you don't want it, then don't use it. It's been posted for users that want traditional root and don't know how to mod their own boot.img. Also you're incorrect about the amount of flashing in recovery. You still only need to flash one zip. The SuperSU zip. The boot image gets flashed in fastboot. Soooooooo when you're updating to newest software from Google, you simply use this modded boot.img instead of the one from Google. So technically there are absolutely no extra steps taken in order to use this boot.img.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Would it have been better if the question were phrased: "Why do you need a separate modified boot.img, when you can force system root using any SuperSU above 2.65? It will still patch the boot.img and disable "forceencrypt"?
So, I'll ask....why do you need a modified boot.img and SuperSU, if SuperSU 2.6x will *automatically modify the boot.img for you and can be installed as system or system-less via terminal commands? Is it because you are using the stock rom and SuperSU will not install as system root due to lack of space in /system?
Edit: *automatically modify boot.img when installing as system-less, OR can be forced to install as system root via terminal commands?
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Why do you guys attack the above person for asking "explain like I am 5, why does anyone want this?"
Would it have been better if the question were phrased: "Why do you need a separate modified boot.img, when you can force system root using any SuperSU above 2.65? It will still patch the boot.img and disable "forceencrypt"?
So, I'll ask....why do you need a modified boot.img and SuperSU, if SuperSU 2.6x will *automatically modify the boot.img for you and can be installed as system or system-less via terminal commands? Is it because you are using the stock rom and SuperSU will not install as system root due to lack of space in /system?
Edit: *automatically modify boot.img when installing as system-less, OR can be forced to install as system root via terminal commands?
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Why use the terminal cmd? I make this for myself. I posted for people that want it. If you don't want it or need it that is cool. I flash this when flashing factory imgs and I can reboot still decrypted then I boot to twrp flash SuperSU zip and I'm done. I'm not a fan of systemless root. Do you know why it was even created??
guitardedhero said:
Is this still Enforcing? Is it possible to get a stock or close to stock kernel that is Permissive for a project I'm working on? I just need a boot.img. Thanks!
Click to expand...
Click to collapse
Yes it's still Enforcing
floepie said:
Because you don't have to rely on the generosity of someone modifying the boot image to accommodate the older method, thereby requiring only 1 recovery flash?
Click to expand...
Click to collapse
This boot.img isn't flashed in recovery so still one flash. This is fastboot when your updating factory imgs.
freddienuxx said:
I agree and thank you. as I am traditional root user. thank you for the boot img
Sent from my Nexus 9
Click to expand...
Click to collapse
no problem I do it for every update. I just decide to start posting them for people like yourself. ??
Hi,
Should I be using this file to update from MMB29P to MMB29Q and still maintain root?
I must flash the file through TWRP?
Touchmetallic said:
Hi,
Should I be using this file to update from MMB29P to MMB29Q and still maintain root?
I must flash the file through TWRP?
Click to expand...
Click to collapse
you can use this as boot.img to update yes. But keep root no. You just need to flash factory imgs with this boot.img then boot up and boot to twrp flash SuperSU 2.67 and you will be updated with regular root.
Flash this boot.img thru fastboot just like you do factory imgs not via recovery.
Tigerstown said:
you can use this as boot.img to update yes. But keep root no. You just need to flash factory imgs with this boot.img then boot up and boot to twrp flash SuperSU 2.67 and you will be updated with regular root.
Flash this boot.img thru fastboot just like you do factory imgs not via recovery.
Click to expand...
Click to collapse
Thanks for your reply.
Sorry if this is a redundant question as I'm not an expert, but is there an easy way to update without losing root?
Touchmetallic said:
Thanks for your reply.
Sorry if this is a redundant question as I'm not an expert, but is there an easy way to update without losing root?
Click to expand...
Click to collapse
No need to be sorry it's all good... Unfortunately no. You can just flash SuperSU zip in twrp after updating to new factory imgs with this modified boot.img and your 100% rooted again.
Touchmetallic said:
Thanks for your reply.
Sorry if this is a redundant question as I'm not an expert, but is there an easy way to update without losing root?
Click to expand...
Click to collapse
I recommend not flashing the userdata.img as that will wipe your internal storage sense it's still 6.0.+ FYI but that's up to you and don't flash the recovery.img either in factory imgs cause that will replace your twrp with stock recovery
Tigerstown said:
Why use the terminal cmd? I make this for myself. I posted for people that want it. If you don't want it or need it that is cool. I flash this when flashing factory imgs and I can reboot still decrypted then I boot to twrp flash SuperSU zip and I'm done. I'm not a fan of systemless root. Do you know why it was even created??
Click to expand...
Click to collapse
Ahh I see. That makes sense given that you are decrypted. Appreciate that.
Having followed SuperSU threads since late November, seems like it was created to make accepting OTAs easier. That, or to work around the limits of Marshmallow and /system rom space. If not that, then no I don't.
Sent from my Nexus 5X using Tapatalk
hi Guys!
I just wanted to share my work with you.
I created a working TWRP recovery for the Pixel on Android O developer preview 4, that can boot and decrypt the /data partition. I don't own a Pixel XL, so I can't test, but @Chainfire did a few quick tests and it seems to be working on his Pixel XL too. So I would say you can try and see if it works for you. Please keep in mind, that I didn't test it, and neither Chainfire, or myself or anyone else can be blamed if it doesn't work, or damages your phone (shouldn't actually, but who knows..).
If you are still not scared enough, please follow this link to the Pixel forums and check out my work:
https://forum.xda-developers.com/pixel/development/mod-twrp-recovery-pixel-android-o-dp4-t3651896
Good luck!
I test it on my pixel xl， working well.
Thank you very much.
But it seems to not be able to flash supersu
When I try to flash it via fastboot it says file is not signed. What am I doing wrong here? I wanted to be rooted and I am on Android op4 preview. Please guide me how to root. Thank you everyone.
sahilarora2003 said:
When I try to flash it via fastboot it says file is not signed. What am I doing wrong here? I wanted to be rooted and I am on Android op4 preview. Please guide me how to root. Thank you everyone.
Click to expand...
Click to collapse
Its in the instructions but here is the command and you shouldn't flash it but instead fastboot it.
fastboot boot trwp.img
flash the latest supersu 2.82 sr1
NVM. Mission accomplished. Thank you for help.
feimummy said:
I test it on my pixel xl， working well.
Thank you very much.
But it seems to not be able to flash supersu
Click to expand...
Click to collapse
To root, you don't even need recovery. Use @Chainfire's boot-to-root.img (fastboot boot it), and it will do the job for you. Easiest way to root...
And don't forget to thank him!
SR2 flash fine
gubacsek said:
To root, you don't even need recovery. Use @Chainfire's boot-to-root.img (fastboot boot it), and it will do the job for you. Easiest way to root...
And don't forget to thank him!
Click to expand...
Click to collapse
You can try SR2 flash fine.
gubacsek said:
To root, you don't even need recovery. Use @Chainfire's boot-to-root.img (fastboot boot it), and it will do the job for you. Easiest way to root...
And don't forget to thank him!
Click to expand...
Click to collapse
Thank you for your answer.
Thank Chainfire.
But my phone Pixel XL is at home now,I will try it later.
Is it this one?
https://download.chainfire.eu/1011/CF-Root1/root-marlin-pixelxl.zip
feimummy said:
Thank you for your answer.
Thank Chainfire.
But my phone Pixel XL is at home now,I will try it later.
Is it this one?
https://download.chainfire.eu/1011/CF-Root1/root-marlin-pixelxl.zip
Click to expand...
Click to collapse
Yes, that should be it!
Although Chainfire has released a new version in zip format, with a lot of pixel (XL) related fixes. You can also try to flash that one using my modded TWRP.
gubacsek said:
Yes, that should be it!
Although Chainfire has released a new version in zip format, with a lot of pixel (XL) related fixes. You can also try to flash that one using my modded TWRP.
Click to expand...
Click to collapse
I have used your modded TWRP to flash SuperSU zip,but there was nothing happened after rebooting the phone.
And I also try "fastboot boot boot-to-root.img" just now,there was still nothing happened...
View attachment 4236828
I mean,it was so strange that SuperSU can not be flashed into my Pixel XL with these two methods.
——————————The final outcome——————————
I have solved the problem with this SuperSU version:
https://forum.xda-developers.com/showpost.php?p=72686197&postcount=10481
Thanks a lot.
feimummy said:
I have used your modded TWRP to flash SuperSU zip,but there was nothing happened after rebooting the phone.
And I also try "fastboot boot boot-to-root.img" just now,there was still nothing happened...
View attachment 4236828
I mean,it was so strange that SuperSU can not be flashed into my Pixel XL with these two methods.
Click to expand...
Click to collapse
Try to flash the original boot.img first.
1. reboot to bootloader
2. fastboot flash boot.img from the factory image zip
3. fastboot boot recovery.img
4. in the recovery, flash supersu
Or you can skip points 3 and 4, and fastboot boot boot-to-root.img
gubacsek said:
Try to flash the original boot.img first.
1. reboot to bootloader
2. fastboot flash boot.img from the factory image zip
3. fastboot boot recovery.img
4. in the recovery, flash supersu
Or you can skip points 3 and 4, and fastboot boot boot-to-root.img
Click to expand...
Click to collapse
Sr2 flash fine!
caballon said:
Sr2 flash fine!
Click to expand...
Click to collapse
Great! Nice to see that everything is working I had this itching, you know, when something is not as it should be, because I wanted to have Android O, but there was no recovery to do what I want... Now this feeling is gone, and I'm relaxed again
The only thing missing is a flashable zip. Is my current "itch"
Very nice. I booted into TWRP with no issue. I had already used boot-to-root so I did not have to flash SR2 in TWRP but nice knowing we have it working for the XL.
Thank you for making this sir.
Work like a charm in Final Android O!!! Thanks man.
caballon said:
Work like a charm in Final Android O!!! Thanks man.
Click to expand...
Click to collapse
Same here!
People have successfully rooted O Final? I used the img but I can't flash zips or access any folders they all have weird names is that due to Encryption?
liam_davenport said:
People have successfully rooted O Final? I used the img but I can't flash zips or access any folders they all have weird names is that due to Encryption?
Click to expand...
Click to collapse
Had this already sometimes on 7.1.2 with twrp rc 1 and 2. Must be an encryption error. Only way for me to use the phone again was to start all over with flashing factory image with flash-all.bat.
liam_davenport said:
People have successfully rooted O Final?
Click to expand...
Click to collapse
Reboot until you get prompted for your PIN in recovery, then flash SuperSU v2.82 SR3 from here.
I have global Honor 9, updated to 8.0.0.379(C432), unlocked and rooted.
I read that Huawei rolled out an update which broke Magisk, does anyone know if the latest update is safe?
How can I tell if an update is safe to use?
I'm using it with the new 9.0.1 rom and it works just fine, the only problem is that it cannot exist on the phone at the same time with a TWRP recovery
mtvento said:
I'm using it with the new 9.0.1 rom and it works just fine, the only problem is that it cannot exist on the phone at the same time with a TWRP recovery
Click to expand...
Click to collapse
as opposed to version 8.0.0.379?
I currently have magisk and TWRP with no problem, is this problem you describe is new to the latest version?
Do you have a different custom ROM?
I have the latest official ROM, and yes it is a new problem with EMUI9, the boot.img partition doesn't exist any more and magisk has to be installed on the recovery_ramdisk.img
mtvento said:
I have the latest official ROM, and yes it is a new problem with EMUI9, the boot.img partition doesn't exist any more and magisk has to be installed on the recovery_ramdisk.img
Click to expand...
Click to collapse
So on EMUI9 there's no option of Root+Custom recovery?
So the options are either root or custom recovery?
Did I understand correctly?
Thank you
Yes, correct until new findings lead to better solution, and keep in mind that you have to boot to recovery each time to keep root working...
mtvento said:
Yes, correct until new findings lead to better solution, and keep in mind that you have to boot to recovery each time to keep root working...
Click to expand...
Click to collapse
That sucks big time.
What do you mean by "have to boot to recovery each time"? every time I restart the phone or turn it off and back on I must go through recovery?
I think I'll avoid EMUI9 and stick with EMUI8.
For some reason there are not much custom ROMs or honor 9
That is the last time I buy a non root friendly phone like Huawei/Xiaomi
Once you have magisk set up you can just get it to flash the boot image from within the manager you can boot as normal then
buchman said:
Once you have magisk set up you can just get it to flash the boot image from within the manager you can boot as normal then
Click to expand...
Click to collapse
I don't really know what that means.
Is it a one time thing?
how is it done exactly?
Clonimus said:
I don't really know what that means.
Is it a one time thing?
how is it done exactly?
Click to expand...
Click to collapse
From within magisk manager click on install magisk and the select the direct install method. It patches the right bit then and you can boot without going through recovery
buchman said:
From within magisk manager click on install magisk and the select the direct install method. It patches the right bit then and you can boot without going through recovery
Click to expand...
Click to collapse
When I do that it gives me 2 options, one is download a zip file (and then I need to install using TWRP, right?)
The other option is patch a boot image, and it lets me look for one. Is this option to patch a downloaded boot image and then I need to flash it? what do I do with this option?
Official TWRP is now available: https://twrp.me/asus/zenfone9.html
IMPORTANT NOTES:
CleanSlate custom kernel is not currently compatible with TWRP for this device (Kirisakura is compatible as of v2.0.6).
This device has a recovery partition (2, in fact), and fastboot boot is disabled in the bootloader. Flashing TWRP to the recovery partition is the only way to use it.
If you attempt to fastboot boot the TWRP image, your device may end up unbootable. YOU'VE BEEN WARNED.
Any questions, comments, feedback, or concerns should always be accompanied by logs (recovery log, logcat, dmesg)
TWRP Trees
Common: https://github.com/TeamWin/android_device_asus_sm84xx-common
Device: https://github.com/TeamWin/android_device_asus_AI2202
Thanks for your work!
Installed as on twrp.me described wont boot (https://twrp.me/asus/zenfone9.html)
Had to flash stock recovery again.
Rooted device on 32.2050.2050.29 with kirisakura-kernel.
Any idea what im doing wrong?
Hermann2306 said:
Thanks for your work!
Installed as on twrp.me described wont boot (https://twrp.me/asus/zenfone9.html)
Had to flash stock recovery again.
Rooted device on 32.2050.2050.29 with kirisakura-kernel.
Any idea what im doing wrong?
Click to expand...
Click to collapse
If you're not on stock kernel, then that's probably the problem. I know the custom kernel situation is different on this device than previous ones. This may be something that @Freak07 & I have to look into together. In the meantime, can you restore back to stock kernel and confirm that TWRP works, and then install Kirisakura and see if everything still works?
Restored stock kernel with kernelflasher but now it wont boot. Tried to change the slot to a but isnt allowed in fastboot.
Have to find out now how to change the slot or install stock kernel via fastboot...
Hermann2306 said:
Restored stock kernel with kernelflasher but now it wont boot. Tried to change the slot to a but isnt allowed in fastboot.
Have to find out now how to change the slot or install stock kernel via fastboot...
Click to expand...
Click to collapse
It doesn't sound like you followed the procedure in the Kirisakura thread FAQ to fully return to stock. Can you confirm exactly what you did?
just restored the backup i made with kernelflasher befor i installed the custom kernel and rebooted.
Hermann2306 said:
just restored the backup i made with kernelflasher befor i installed the custom kernel and rebooted.
Click to expand...
Click to collapse
I'm not familiar with that app, sorry. I just know that's not the process mentioned in his thread, so until you do that, I can't really confirm what the problem could be.
ok, im back on stock. flashing following files helped. i will test twrp again later and report. thanks for your replies.
fastboot flash boot boot.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash dtbo dtbo.img
fastboot reboot fastboot
fastboot flash vendor_dlkm vendor_dlkm.img
fastboot reboot
With stock kernel twrp works. Just installed as described on twrp.me. The official twrp app from playstore crashes after root allowing.
For everyone who comes from custom kernel flash the files from your actual firmware (payload-dumper) as described in the post above.
Are you working on custom kernel support?
Hermann2306 said:
With stock kernel twrp works. Just installed as described on twrp.me. The official twrp app from playstore crashes after root allowing.
For everyone who comes from custom kernel flash the files from your actual firmware (payload-dumper) as described in the post above.
Are you working on custom kernel support?
Click to expand...
Click to collapse
From stock, I just flashed the Kirisakura zip in TWRP and my device booted up fine.
EDIT: While the above is true, TWRP no longer functions after installing the kernel, and the device won't reboot again after installing it. So something is definitely wrong somewhere.
For now, I can only suggest not using it with a custom kernel until we figure this out.
Ok, flashing with EXKernelManager works also.
update
I can do reboots but twrp doesnt work anymore
Hermann2306 said:
Ok, flashing with EXKernelManager works also.
update
I can do reboots but twrp doesnt work anymore
Click to expand...
Click to collapse
Yes, there seems to be an issue in the kernel that's preventing TWRP from working. I'm not sure what the issue is, unfortunately.
So every time I restore a back up, do I have to delete all lock screen requirements ?
If that's the case, I would have to redo my fingerprints every time
c19932 said:
So every time I restore a back up, do I have to delete all lock screen requirements ?
If that's the case, I would have to redo my fingerprints every time
Click to expand...
Click to collapse
Yes.
Quick PSA for anyone using this TWRP that also wants to use a custom kernel:
As of Kirisakura 2.0.6, the custom kernel and TWRP can now co-exist. This is due to the changes that allowed a monolithic kernel build. Presently, CleanSlate has not adopted those changes, but if/when it does, I will remove that disclaimer from the OP.
Thanks to @arter97, @Freak07, & @tbalden for supporting this device!
Is the twrp compatible with android 13?
NisseGurra said:
Is the twrp compatible with android 13?
Click to expand...
Click to collapse
There's a really easy way to find out...
Captain_Throwback said:
There's a really easy way to find out...
Click to expand...
Click to collapse
I getting decrypt errors that why the q
NisseGurra said:
I getting decrypt errors that why the q
Click to expand...
Click to collapse
Then you should post some logs
Will do