Hi I had Xpower5 Rom. I wanted to try new Nougat. I had many issues with flash (error of processing system.sin and loader.sin). I dont know how now it work. After that I flashed AndroPlus 43 kernel and TWRP 3.0.2. Kernel works but No white led on startup and no recovery there (also adb reboot recovery not work) . I tried another img of twrp and nothing changed. Any idea how install recovery? Anybody has the same problem with flashing? Thanks
As this phone doesn't support universal recovery and only sports a ota partition that can be used for recovery but then requires a kernel that supports booting recovery from ota partition, it's a hustle to use non standard recovery systems.
Is there even a nougat compatible kernel with included TWRP ota boot support for this phone?
This should work
https://forum.xda-developers.com/showpost.php?p=70807294&postcount=132
Also patching the stock kernel with the rootkernel tool integrates working twrp.
Gewiz said:
This should work
https://forum.xda-developers.com/showpost.php?p=70807294&postcount=132
Also patching the stock kernel with the rootkernel tool integrates working twrp.
Click to expand...
Click to collapse
It works! Thanks. Problem was: no white LED flash there. I have to press vol down and power on.
But I have still have a problem with flashing. Error of processing file loader.sin or system.sin. I cant flash again anything
Make sure you use latest ver of flashtool 0.9.23.2
Gewiz said:
Make sure you use latest ver of flashtool 0.9.23.2
Click to expand...
Click to collapse
Yes I have latest version. I tried older version as well but nothing changed
hromanse said:
Yes I have latest version. I tried older version as well but nothing changed
Click to expand...
Click to collapse
Flash firmware 5.11 first and flash nougat firmware afterwards.
This should work
Not work as well
the 3.1 3.0.2 TWRP bundled in rootkernel 5.23 messess up the internal permissions, so it will appear to work until you try and recover, or - TWRP runs a wipe with mkext4fs
i was talking a bit about it in https://forum.xda-developers.com/showthread.php?t=3560135
---------- Post added at 18:16 ---------- Previous post was at 18:13 ----------
Gewiz said:
Flash firmware 5.11 first and flash nougat firmware afterwards.
This should work
Click to expand...
Click to collapse
Yeah, going back to Lollipop and going all the way up to Nougat works, this is what happened to me. I thought I had a psuedo-recovery-dual system boot .... where i could switch between Marshmallow and Nougat
But then I decided to factory reset, and that started all the problems.
NeoBeum said:
Yeah, going back to Lollipop and going all the way up to Nougat works, this is what happened to me...
Click to expand...
Click to collapse
Thanks! It works
hromanse said:
Thanks! It works
Click to expand...
Click to collapse
Just make sure Restore works, so you don't get burned thinking everything is ok and end up with 12GB of partition mismatched data backup after a month, like I did
Related
Hi,
seems that TWRP recovery isnt working with the just released .253-version of the firmware. Are there any alternative, working recoverys?
P
pickles76 said:
Hi,
seems that TWRP recovery isnt working with the just released .253-version of the firmware. Are there any alternative, working recoverys?
P
Click to expand...
Click to collapse
what twrp are you on? its more likely your kernel not your recovery.
pickles76 said:
Hi,
seems that TWRP recovery isnt working with the just released .253-version of the firmware. Are there any alternative, working recoverys?
P
Click to expand...
Click to collapse
TWRP is running with the last Rootkernel v5.0_rc1 and FW .253
http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
It just does not work when the phone is encrypted.
roadrunner00 said:
TWRP is running with the last Rootkernel v5.0_rc1 and FW .253
http://forum.xda-developers.com/xperia-z5/development/root-automatic-repack-stock-kernel-dm-t3301605
It just does not work when the phone is encrypted.
Click to expand...
Click to collapse
well,I can't get it work with encrypted phone,but it will work on non-encrypted phone .
I have TWRP 3.0.2 installed on FW .253 (non-encrypted) using Rootkernel v5.0_RC1. However, the method of accessing TWRP seems a bit different - I could no longer use apps like Quickboot. Only way is:
- Turn off device
- Turn device back on and wait for LED to turn amber
- Press volume UP button several times until phone enters TWRP
So, I've been trying to flash CyanogenMod 12.1, since I'm still stuck on EMUI 3.1, because I can't flash OTA updates (I've tried everything, dload method, and yes I have unrooted and used the stock recovery)
Every time I try to flash a ROM via TWRP it turns off for a second and then boots back to TWRP starting screen. Also, when I boot my phone the boot animation's Honor H is red for some reason.
Thanks in advance!
Fonku said:
So, I've been trying to flash CyanogenMod 12.1, since I'm still stuck on EMUI 3.1, because I can't flash OTA updates (I've tried everything, dload method, and yes I have unrooted and used the stock recovery)
Every time I try to flash a ROM via TWRP it turns off for a second and then boots back to TWRP starting screen. Also, when I boot my phone the boot animation's Honor H is red for some reason.
Thanks in advance!
Click to expand...
Click to collapse
Are you sure you have the right boot.img and recovery.img?
Usually that symptoms are due to messed partitions.
Did you flash current img files or did you got them from a different rom version?
zinko_pt said:
Are you sure you have the right boot.img and recovery.img?
Usually that symptoms are due to messed partitions.
Did you flash current img files or did you got them from a different rom version?
Click to expand...
Click to collapse
Well, actually I once bricked my phone and had to restore through a TWRP backup, that only had the System and Boot partitions and it was the B130 version when I had B140, but it worked. So, do I need to completely flash everything or can I just pick up some files from somewhere?
Fonku said:
Well, actually I once bricked my phone and had to restore through a TWRP backup, that only had the System and Boot partitions and it was the B130 version when I had B140, but it worked. So, do I need to completely flash everything or can I just pick up some files from somewhere?
Click to expand...
Click to collapse
No, you need to have all the files from the same version.
Flash boot, recovery, cust and system.
zinko_pt said:
No, you need to have all the files from the same version.
Flash boot, recovery, cust and system.
Click to expand...
Click to collapse
So, is there a FULL KIW-L21C432B140 restore packet somewhere?
Thanks for your help!
Fonku said:
So, is there a FULL KIW-L21C432B140 restore packet somewhere?
Thanks for your help!
Click to expand...
Click to collapse
http://forum.xda-developers.com/honor-5x/how-to/repository-honor-5x-file-depot-t3328288
You can use B130 as it is also Lollipop. But all the img from the same rom. You can update to B350 manually after, but first you need a stable rom working.
Let us know man if you fixed your phone. So if not, we can give firther recommendations.
Sent from my Galaxy Tab 3 using XDA Labs
Now supports among other things back up to pc. I've installed and tested and works.
https://dl.twrp.me/ailsa_ii/twrp-3.1.0-0-ailsa_ii.img
Edit: the original article https://www.xda-developers.com/twrp...-support-for-adb-backup-ab-ota-zips-and-more/
Edit: seems flashing via TWRP image flash is providing better success than via TWRP app. Recommend updating via TWRP flash.
thanks
Do not work.
Get a black screen if i try to Boot in to twrp.
Must go back to 3.0.4.1..
Eller1987 said:
Do not work.
Get a black screen if i try to Boot in to twrp.
Must go back to 3.0.4.1..
Click to expand...
Click to collapse
u sure ur bl is unlocked?
MaxRink said:
u sure ur bl is unlocked?
Click to expand...
Click to collapse
Yes.
I am in LOS 14.1 and twrp 3.0.4.1. works fine.
Flashed 3.1.0.0. whit Flashify.
Worked great for me! I always flash in TWRP, I guess that a I am old school. Thanks for pointing out the new version. I will have to try out the new ADB backup feature later. Although I am not sure if we are still having problems restoring backups like we used to on this phone. I haven't been able to keep up with the forum's lately.
Wrong thread, this needs to be in General
Mod please move.
I flashed the image file in recovery and I still ended up with a black screen.
borijess said:
I flashed the image file in recovery and I still ended up with a black screen.
Click to expand...
Click to collapse
Weird man i got it working flashing it feom twrp it self
borijess said:
I flashed the image file in recovery and I still ended up with a black screen.
Click to expand...
Click to collapse
Maybe you should also write from which TWRP version you come and which Axon 7 model(US/Chinese/European?) you own?
redandr said:
Maybe you should also write from which TWRP version you come and which Axon 7 model(US/Chinese/European?) you own?
Click to expand...
Click to collapse
i have a A2017G and come from twrp 3.0.4.1..
Which partion must i flash for the update to 3.1.0.0.?
I flashed this 3.1 on my chinese b13 with twrp 3.0.4-1 and everything is fine. Flashed it thru twrp btw.
---------- Post added at 11:26 AM ---------- Previous post was at 11:25 AM ----------
Eller1987 said:
i have a A2017G and come from twrp 3.0.4.1..
Which partion must i flash for the update to 3.1.0.0.?
Click to expand...
Click to collapse
Flash it in twrp install and choose img. Flash it for recovery partition.
redandr said:
maybe you should also write from which twrp version you come and which axon 7 model(us/chinese/european?) you own?
Click to expand...
Click to collapse
twrp 3.0.41 axon 7 us version.
Ok I flashed TWRP through fastboot and it worked. I think my first DL was bad. It was half the size of the second one I downloaded.
Success here too. Thank you.
Its all ok with Axon Zte A2017 Chinese.
The last TWRP I conscioulsy installed was 3.0.4.1 but it now shows 3.0.N1-1, what is that? Could it have been updated automatically from the TWRP app?
Also, before I noticed that my boot partition disappeared from TWRP, I can no longer make backups of it or restore the ones I had. Why could that happen? I get something like "unable to locate boot". Thanks
0Kajuna0 said:
The last TWRP I conscioulsy installed was 3.0.4.1 but it now shows 3.0.N1-1, what is that? Could it have been updated automatically from the TWRP app?
Also, before I noticed that my boot partition disappeared from TWRP, I can no longer make backups of it or restore the ones I had. Why could that happen? I get something like "unable to locate boot". Thanks
Click to expand...
Click to collapse
I am guessing you used EDL mode to install TWRP as that is the modified version, as I saw that too. I used TWRP to flash the 3.0.4-1 image and all is normal.
EDIT: TWRP 3.0.4-1 on A2017U Running modified Stock B15 (lots of APKs frozen). Flashing TWRP 3.1 both from TWRP and from "Official App" results with black screen for Recovery. TWRP 3.0.4-1 re-flashed OK from app.
N1-1 is from unjustified devs bootstack.
lafester said:
N1-1 is from unjustified devs bootstack.
Click to expand...
Click to collapse
N1-1 & 3.0.4-1 both work fine, but 3.1 boots to black screen. Why?
Twrp 3.1.0 worked fine on my Axon 7 US version A2017U
Flashed via fastboot over stock recovery.
Will edit this thread and report back if issue is discovered.
Here's Repack of the stock kernel
with dm-verity
SONY RIC off
SperSU EnableD
Working on Z4 Tablet (SGP771 - SGP712) 7.1.1 FW 32.4.A.0.160
DOWNLOAD:
SECOND POST
HOW TO INSTALL :
1. Extract zip file And Flash in Fastboot
2. Install TWRP 3.1.1.0 From Here
3. Then Flash SuperSU.zip From Here
4. Done You Get ROOT
Download section
Changelog :
SGP712 aded
dm-verity is Disabled
Sony RIC is Disabled
SR1-SuperSU-v2.82-SYSTEMMODE.zip Installed
busybox Installed
@IlariJ Now Done
Nimadroid said:
@IlariJ
Click to expand...
Click to collapse
THANKS!! :victory:
May i ask, ... would it be possible for you to make a kernel for the SGP712 - Wifi only version too?
Nimadroid said:
@IlariJ Now Done
Click to expand...
Click to collapse
The device boots fine (no longer infinite bootloop), but once it has powered up, the touchscreen doesn't work.
I have rebooted several times and no help.
In TWRP even the touch works.
Can You fix this? @Nimadroid
IlariJ said:
The device boots fine (no longer infinite bootloop), but once it has powered up, the touchscreen doesn't work.
I have rebooted several times and no help.
In TWRP even the touch works.
Can You fix this? @Nimadroid
Click to expand...
Click to collapse
Flash Stock ftf
Then Flash kernel
If don't change I make another one for you
Mr. Schnabel said:
May i ask, ... would it be possible for you to make a kernel for the SGP712 - Wifi only version too?
Click to expand...
Click to collapse
Provide me the kernel.sin from lastest FTF of your device
And i update this poet for you with your device kernel
@Nimadroid -> Send ya a PM
Nimadroid said:
Flash Stock ftf
Then Flash kernel
If don't change I make another one for you
Click to expand...
Click to collapse
Didn't help.:crying:
@ Mr. Schnabel : Goog idea
@ Nimadroid : Thanks in advance for the SGP772 version
ilarij said:
didn't help.:crying:
Click to expand...
Click to collapse
steevou said:
@ mr. Schnabel : Goog idea
@ nimadroid : Thanks in advance for the sgp772 version
Click to expand...
Click to collapse
post updated new device aded
Nimadroid said:
post updated new device aded
Click to expand...
Click to collapse
Kernel works, thanks
---------- Post added at 07:07 PM ---------- Previous post was at 07:02 PM ----------
SGP712 should use this recovery
https://www.androidfilehost.com/?fid=673368273298956222
Nimadroid said:
post updated new device aded
Click to expand...
Click to collapse
Works, thanks!! :victory:
Upgrade from 7.0
Hi,
quick question:
I am on 7.0 with root and DRM fix comming from here: "[Guide] Nougat with DRM fix, root and TWRP* (SGP771)".
Can I simply flash kernel and TWRP as you described on top of these or do I have to restart with any TFT's on 7.11?
Thanks a lot and best regards
Hi guys, i need your help!
Flashed new tft .160 via Flashtool - check
Flash boot via ADB - check
Flash Twrp via ADB - check
Reboot into recovery - nope nope nope ...
No matter what or how i flash i simply cannot boot into recovery
Tried older Twrp versions, in ADB shell everything is ok, no error, .....
simply don´t know what to do anymore hmmmmm ....
Mr. Schnabel said:
Hi guys, i need your help!
Flashed new tft .160 via Flashtool - check
Flash boot via ADB - check
Flash Twrp via ADB - check
Reboot into recovery - nope nope nope ...
No matter what or how i flash i simply cannot boot into recovery
Tried older Twrp versions, in ADB shell everything is ok, no error, .....
simply don´t know what to do anymore hmmmmm ....
Click to expand...
Click to collapse
If you're using SGP712 you need to flash the proper recovery for that device, the one in OP is for SGP771
This one is the correct one (also linked 3 posts above): https://www.androidfilehost.com/?fid=673368273298956222
Well .. actually OP and your´s in 3rd post and here are all 3 the same
Like said tried these here, from androPlus thread, etc etc ...
Flash via fastboot is working but cannot enter recovery after flashing
Tried to access via Power button, volume button, adb command, ... i dont even have a led signal at power on
Mr. Schnabel said:
Well .. actually OP and your´s in 3rd post and here are all 3 the same
Like said tried these here, from androPlus thread, etc etc ...
Flash via fastboot is working but cannot enter recovery after flashing
Tried to access via Power button, volume button, adb command, ... i dont even have a led signal at power on
Click to expand...
Click to collapse
oh, didn't notice, although I'm pretty sure the one in OP was different
It's booting on my device, but the first time I tried it didn't. I think it booted when I accidentally flashed it on the boot partition instead of the recovery one maybe you can try that.
but before, try hot booting it with:
Code:
fastboot boot ~/Downloads/TWRP-3.1.1-lineageos-karin_windy-20170520.img
Hotboot endet in an Bootloop but flashing recovery to Boot helped! Many many Thanks
€dit: Ok my bad didnt work ....
Hotboot didnt work
Flashing recovery to boot did boot up Twrp - Wiped cache/dalvik, flashed SU, Tablet constanty reboot into TWRP instead of system
Flashed Kernel/Boot to Boot - Tab boots into system but no root
Tried to reboot into recovery - no luck
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