I came from cm13 and i suddenly think of returning back to stock lollipop. After a few days, I realize cm13 is a lot better. I downgraded back to kitkat and unlocked the bootloader the way I did before. Before, it was successful. But now, when I flash TWRP and reboot to recovery using flashify, it shows security boot error. I upgraded to stock lollipop and tried it unlocking bootloader there. I flashed TWRP but when I entered TWRP, I cannot reboot back to system. I cannot get out of recovery!! Pleasee help... I want to get cm13 back
ShadowBlade_20 said:
I came from cm13 and i suddenly think of returning back to stock lollipop. After a few days, I realize cm13 is a lot better. I downgraded back to kitkat and unlocked the bootloader the way I did before. Before, it was successful. But now, when I flash TWRP and reboot to recovery using flashify, it shows security boot error. I upgraded to stock lollipop and tried it unlocking bootloader there. I flashed TWRP but when I entered TWRP, I cannot reboot back to system. I cannot get out of recovery!! Pleasee help... I want to get cm13 back
Click to expand...
Click to collapse
you should write this in other section but i want to help you.
maybe try to flash stock kdz again if you still can then check if bootloader method you use is correct but if was not you will brick your phone.
I came from cm13 and i suddenly think of returning back to stock lollipop. After a few days, I realize cm13 is a lot better. I downgraded back to kitkat and unlocked the bootloader the way I did before. Before, it was successful. But now, when I flash TWRP and reboot to recovery using flashify, it shows security boot error. I upgraded to stock lollipop and tried it unlocking bootloader there. I flashed TWRP but when I entered TWRP, I cannot reboot back to system. I cannot get out of recovery!! Pleasee help... I want to get cm13 back
ShadowBlade_20 said:
I came from cm13 and i suddenly think of returning back to stock lollipop. After a few days, I realize cm13 is a lot better. I downgraded back to kitkat and unlocked the bootloader the way I did before. Before, it was successful. But now, when I flash TWRP and reboot to recovery using flashify, it shows security boot error. I upgraded to stock lollipop and tried it unlocking bootloader there. I flashed TWRP but when I entered TWRP, I cannot reboot back to system. I cannot get out of recovery!! Pleasee help... I want to get cm13 back
Click to expand...
Click to collapse
actually i gave a answer for you http://forum.xda-developers.com/showpost.php?p=64674426&postcount=2
u even can flash kdz ? if yes, try it and check if your bootloader unclocking method, file, is correct.
You could brick your phone.
Hi xda!
I have a Z5C and i was tired of sonys laggy version of Android so I decided to install zombie kernel with twrp as backup.
The kernel works brilliant but I can only boot to recovery with help from fastboot. I would like to be able to boot to recovery directly from my phone without the use of fastboot/PC..
I also have a z4 tablet with Androplus kernel with twrp recovery.. And I am able to boot directly from the tablet to recovery.
So I decided to install Androplus and twrp for my z5c. I tried to install twrp through twrp and it looked like it was installed... However still not able to boot to recovery without fastboot. Then I tried to install with fastboot and I got an error - picture attached.
When I look under "about phone" the phone tells me that I'm still using the old zombiekernel??
How do I get Androplus kernel and working twrp installed on my z5c?
Thanks in advance
asl0501 said:
Hi xda!
I have a Z5C and i was tired of sonys laggy version of Android so I decided to install zombie kernel with twrp as backup.
The kernel works brilliant but I can only boot to recovery with help from fastboot. I would like to be able to boot to recovery directly from my phone without the use of fastboot/PC..
I also have a z4 tablet with Androplus kernel with twrp recovery.. And I am able to boot directly from the tablet to recovery.
So I decided to install Androplus and twrp for my z5c. I tried to install twrp through twrp and it looked like it was installed... However still not able to boot to recovery without fastboot. Then I tried to install with fastboot and I got an error - picture attached.
When I look under "about phone" the phone tells me that I'm still using the old zombiekernel??
How do I get Androplus kernel and working twrp installed on my z5c?
Thanks in advance
Click to expand...
Click to collapse
To boot to recovery in the z5c you gotta pudg the volume up while booting over and over until you see the notification LED go red-yellow-orange
Once you're in recovery you could restore your old kernal if you made s bsckup
I know... But that is not working. The only way i can get it to boot is with fastboot. What to do?
asl0501 said:
I know... But that is not working. The only way i can get it to boot is with fastboot. What to do?
Click to expand...
Click to collapse
Try flash tool to push anew kernel maybe.I've never done it but from what j have read, download your firmware from xperia firmware and use flash tool to only flash kernel.
You need to use fastboot to flash the boot.img to the phone and then do the same for recovery.img. It will then work with androplus kernel and twrp.
Thats my setup currently.
spikeyhair said:
You need to use fastboot to flash the boot.img to the phone and then do the same for recovery.img. It will then work with androplus kernel and twrp.
Thats my setup currently.
Click to expand...
Click to collapse
Sorry to resurect this old thread. Can you or anyone provide a boot.img or how to go about creating one? I am in same situation (stuck at boot screen) and only have access to fastboot. Thanks.
For which version of rom? I can give you 32.0.A.200 boot.img and twrp recovery.
Are you sure you're clicking volume up when booting? It doesn't work when you hold the volume up button down.
If y'all go to the twrp thread there is a modified boot.IMG that allows booting to recovery now.
Hi friends,
So here's a thing:
I was trying to update my Nexus 9 to the latest Slimrom build , and I used Chainfire's flashfire app. It didn't work and sent the tablet in a boot loop. But it also wiped my recovery so I couldn't even select my recovery.
So no issues, I used the Wugfresh nexus toolkit to flash it back to stock and unroot. Bootloader is still unlocked, so I just root it again and go ahead and try to install the update using Wugfresh. It works, but says the vendor.img is wrong. So I downloaded the correct vendor.img and tried to flash it, but of course because the tablet is encrypted TWRP asked for a password. I hit cancel and tried to continue, but Wugfresh just hung at that step.
So I tried to manually flash the ROM, but now it gives me a vendor.img error and will not flash anything. Trying to flash anything sends the device in a bootloop.
TLDR; I can restore to stock and root, and also access the bootloader and recovery (TWRP) but can't flash anything without sending the device in a bootloop.
I've currently restored the tablet to stock via wugfresh's tool and rooted. So I'm back at the beginning, except with this vendor.img issue when I'm trying to flash a ROM.
Anyone have any ideas?
I was running stock MIUI with root and TWRP recovery. After flashing the Pixel Experience Android 11 ROM, I didn't flash TWRP again. I tried many attempts (I haven't mentioned everything here to keep the post shorter) to install TWRP again, and I managed to do it successfully once. However, now when I boot into TWRP and select the A partition, it can't decrypt with my password and reboots the system, always opening the bootloader. When selecting the B partition, if I format the data and flash Magisk, it opens up the system (it opens the bootloader without flashing Magisk). But after booting into the system, if I boot TWRP again and reboot into the system without doing anything, my settings app and Bluetooth stop working. Then I have to boot into TWRP again, format the data, and flash Magisk again to boot the system normally. I can't install any Magisk modules either. However, the root is working.
Do you have any suggestions on what I can do?"
AhmedRadowan25 said:
Do you have any suggestions on what I can do?
Click to expand...
Click to collapse
flash stock miui according to your region with mi flash (don't lock the bootloader!)
this generally solves any problem and you can go back to custom roms after booting into miui.
Anyway , i recommend you to use the recovery provided with the rom itself as twrp can give issues sometimes.
AhmedRadowan25 said:
I was running stock MIUI with root and TWRP recovery. After flashing the Pixel Experience Android 11 ROM, I didn't flash TWRP again. I tried many attempts (I haven't mentioned everything here to keep the post shorter) to install TWRP again, and I managed to do it successfully once. However, now when I boot into TWRP and select the A partition, it can't decrypt with my password and reboots the system, always opening the bootloader. When selecting the B partition, if I format the data and flash Magisk, it opens up the system (it opens the bootloader without flashing Magisk). But after booting into the system, if I boot TWRP again and reboot into the system without doing anything, my settings app and Bluetooth stop working. Then I have to boot into TWRP again, format the data, and flash Magisk again to boot the system normally. I can't install any Magisk modules either. However, the root is working.
Do you have any suggestions on what I can do?"
Click to expand...
Click to collapse
Here's a complete explanation what I have done:
Initially, I was running stock MIUI with root access and TWRP recovery. However, I decided to switch to the Pixel Experience ROM. I downloaded the Pixel Experience Android 11 version and flashed it directly from TWRP since I didn't have access to a PC at that time. I only flashed the ROM file and didn't install the Pixel Experience recovery image, assuming that my TWRP would remain intact. But when I rebooted into recovery after the ROM installation, it booted into the Pixel Experience recovery instead. I couldn't find an option to flash the recovery image, only an option to apply an update through ADB sideload.
Fortunately, I managed to use a friend's computer and installed all the necessary ADB and Fastboot drivers. The computer could detect my phone in ADB sideload mode, but when I tried to boot into the bootloader, the PC couldn't detect my phone. Despite multiple attempts of booting into the Pixel Experience recovery and enabling ADB sideload, the PC couldn't recognize the fastboot mode. Strangely, every time I booted into the bootloader, my phone automatically powered off after displaying the Redmi logo. Holding the power button didn't help as it consistently powered off after showing the logo, without accessing the bootloader or recovery mode. I was afraid my phone had become completely unresponsive.
After numerous attempts, my phone unexpectedly booted into the bootloader again. This time, I connected my phone to another device using BugJagger, which successfully detected my phone. I used the command "fastboot flash recovery twrp.img" followed by "fastboot boot twrp.img" to open TWRP. However, I couldn't decrypt it using my password. I then flashed TWRP again and tried to boot into the system, but it always reverted back to the bootloader. I went back into recovery, selected partitions A to B, and flashed Magisk ZIP, DM variety ZIP, and LazyFlasher ZIP (without fully understanding their purpose).
Finally, my phone successfully booted into the system. However, upon rebooting into TWRP and then rebooting the system without any changes, my settings app and bluetooth stoped working. To resolve this, I had to boot into TWRP once again, format the data, and flash Magisk to restore normal operation.
alonsoj636MW said:
flash stock miui according to your region with mi flash (don't lock the bootloader!)
this generally solves any problem and you can go back to custom roms after booting into miui.
Anyway , i recommend you to use the recovery provided with the rom itself as twrp can give issues sometimes.
Click to expand...
Click to collapse
yes i am also thinking that it is the only solution.But I have tampered almost everything of my phone.Will flash stock miui rom can solve all problem?I have writen everything what i have done details in reply.you can read it if you want.
AhmedRadowan25 said:
yes i am also thinking that it is the only solution.But I have tampered almost everything of my phone.Will flash stock miui rom can solve all problem?I have writen everything what i have done details in reply.you can read it if you want.
Click to expand...
Click to collapse
yes i think you messed up with your phone for real. there was a lot of things that was incorrect.
don't mess with the slots and don't flash things you don't know about... you can ask here if you have doubts...
follow my advice and reflash stock miui with miflash to start from 0
and don't do all those things again... once you are done with miui... just tell what do you want to do and we'll guide you properly
alonsoj636MW said:
yes i think you messed up with your phone for real. there was a lot of things that was incorrect.
don't mess with the slots and don't flash things you don't know about... you can ask here if you have doubts...
follow my advice and reflash stock miui with miflash to start from 0
and don't do all those things again... once you are done with miui... just tell what do you want to do and we'll guide you properly
Click to expand...
Click to collapse
alonsoj636MW said:
yes i think you messed up with your phone for real. there was a lot of things that was incorrect.
don't mess with the slots and don't flash things you don't know about... you can ask here if you have doubts...
follow my advice and reflash stock miui with to start from 0
and don't do all those things again... once you are done with miui... just tell what do you want to do and we'll guide you properly
Click to expand...
Click to collapse
Thank you very much.Flashing miui will solve all probem?what do you think?
AhmedRadowan25 said:
what do you think?
Click to expand...
Click to collapse
it should
at least when i mess up with my phone flashing stock fixes all problems
Hi mate! Did you resoved the problem? What about the rom? All good?
gabsvm1 said:
Hi mate! Did you resoved the problem? What about the rom? All good?
Click to expand...
Click to collapse
No.I am running pixel experience 11 rom with these problems.No problem will appear untill i boot into recovery.Sorry i can't check and tell you that if 13 rom's recovery can flash 11 rom.
AhmedRadowan25 said:
No.I am running pixel experience 11 rom with these problems.No problem will appear untill i boot into recovery.Sorry i can't check and tell you that if 13 rom's recovery can flash 11 rom.
Click to expand...
Click to collapse
No problem mate, besides that everything is working good? You have tried a13 roms before?
gabsvm1 said:
No problem mate, besides that everything is working good? You have tried a13 roms before?
Click to expand...
Click to collapse
No
Who told you to flash DM Verity and Lazy Flasher
We don't need these things in our device
Don't mess up with Active Slot
If you try to change your Active slot into Inactive slot, once you Reboot to system, you will go straight to fastboot
You need Android Bootloader Interface to detect your phone in bootloader and ADB Composite to detect your phone in ADB, such as : Google USB Driver r13
Why you don't ask before doing anything, we have global community chat in telegram, for sure, we will help you in possible way
I assume you need back to stock rom to fix this issue
hit me on tele t.me/super_img