Hello...
So I was going to test out a couple different kernels this morning. I was running Elemental X and it was performing quite well, but I wanted to test out arter97 since it was new to OP7. Flashed via TWRP and had absolutely no issues at all. After reviewing the features I noticed it didn't have wakelock blocking and decided I'd like to try something else that allows it. I decided to try out Kirisakura instead so I followed the instruction on the thread to flash it via EXKM. I installed the companion module via Magisk first, then flashed the kernel + rebooted. After rebooting however.... I can't boot up at all. The only thing I can do is hold volume up + power to get the device to get to the bootloader unlocked screen and then it goes black.
https://forum.xda-developers.com/on.../kernel-kirisakura-1-0-0-op7-pro-aka-t3933916
I figured out the hardware buttons for fastboot mode was actually Vol up + down + power. Got into fastboot, adb TWRP.img. Once in TWRP, flashed arter79's kernel (what I was on before going to this one). After that I noticed Magisk wasn't installed for some reason so I reinstalled that as well. Had to fix some stuff afterward but I'm basically back to normal it seems.
Related
A couple of months back, I had unlocked the bootloader (I had stock 4.2.1) and rooted this tablet in order to put Cyanogenmod on it. The current version was CM10.2 (nightlies). I was able to update to different nightly versions and then to the stable 10.2 version. Recently, I saw CM11 nightly versions beginning to appear, so I thought I'd install it.
Using TWRP 2.6.1.0, I had been able to do all of my CM10.2 updating. However, with CM11, the initial flash didn't work (I did clear cache and Dalvik), and so I thought I had to update TWRP. I downloaded TWRP 2.6.3.0 for the TF300T (both .img and .blob) and tried to fastboot them to my device. .img did not work, but then the blob fastboot was able to install TWRP, however, there was a password lock. Reading about this online, I thought I just had to reflash TWRP 2.6.3.0. I tried that and got the same password issue.
Then, I thought that CWM would be a better option (although I thought I may have seen things about it not playing well with the 4.2.1 bootloader...). I flashed a version of that (not exactly sure what version... (which may be the source of my problem) but it was for the TF300T...). Then, upon rebooting, it got stuck on the ASUS loading screen (with "The Device is UnLocked." in the corner). So then I tried rebooting into the recovery, but then I couldn't access the recovery menu from power + vol. down buttons anymore.
Basically, what I can do now is restart the tablet (via holding the power button or pressing the reset slot), but it always gets stuck on the ASUS screen, or I can enter APX mode, but don't think that'll do much good since I don't have nvFlash installed...
Is my tablet bricked?
Thanks in advance!
PS - I saw some solutions that required opening up the tablet. I would be okay with doing that, but only as a last resort!
Quevvy said:
A couple of months back, I had unlocked the bootloader (I had stock 4.2.1) and rooted this tablet in order to put Cyanogenmod on it. The current version was CM10.2 (nightlies). I was able to update to different nightly versions and then to the stable 10.2 version. Recently, I saw CM11 nightly versions beginning to appear, so I thought I'd install it.
Using TWRP 2.6.1.0, I had been able to do all of my CM10.2 updating. However, with CM11, the initial flash didn't work (I did clear cache and Dalvik), and so I thought I had to update TWRP. I downloaded TWRP 2.6.3.0 for the TF300T (both .img and .blob) and tried to fastboot them to my device. .img did not work, but then the blob fastboot was able to install TWRP, however, there was a password lock. Reading about this online, I thought I just had to reflash TWRP 2.6.3.0. I tried that and got the same password issue.
Then, I thought that CWM would be a better option (although I thought I may have seen things about it not playing well with the 4.2.1 bootloader...). I flashed a version of that (not exactly sure what version... (which may be the source of my problem) but it was for the TF300T...). Then, upon rebooting, it got stuck on the ASUS loading screen (with "The Device is UnLocked." in the corner). So then I tried rebooting into the recovery, but then I couldn't access the recovery menu from power + vol. down buttons anymore.
Basically, what I can do now is restart the tablet (via holding the power button or pressing the reset slot), but it always gets stuck on the ASUS screen, or I can enter APX mode, but don't think that'll do much good since I don't have nvFlash installed...
Is my tablet bricked?
Thanks in advance!
PS - I saw some solutions that required opening up the tablet. I would be okay with doing that, but only as a last resort!
Click to expand...
Click to collapse
Try using fastboot to install this version of TWRP: http://forum.xda-developers.com/showpost.php?p=48512729&postcount=16
It will only work if you were on 10.6.1.15 or above. It allows flashing CM11.
cmendonc2 said:
Try using fastboot to install this version of TWRP: http://forum.xda-developers.com/showpost.php?p=48512729&postcount=16
It will only work if you were on 10.6.1.15 or above. It allows flashing CM11.
Click to expand...
Click to collapse
The thing is, I can't get into fastboot the typical way; pressing power and volume down does not go into the fastboot mode like it did before. I can get into APX mode, though. Can I use that to flash a recovery? I haven't been able to find a way of doing that yet…
Quevvy said:
The thing is, I can't get into fastboot the typical way; pressing power and volume down does not go into the fastboot mode like it did before. I can get into APX mode, though. Can I use that to flash a recovery? I haven't been able to find a way of doing that yet…
Click to expand...
Click to collapse
No, you need nvflash backups to use APX mode. Since you can't get to the recovery menu, I can't think of any other solutions....?
Same here
I'm in the same state after trying to update from 10.2 to 11. Just sits at the ASUS logo screen. No fastboot or recovery. I can get it to turn off by holding the up volume and inserting a paper clip into the reset switch hole. Otherwise I have been totally unsuccessful in getting it to do anything else. At this point I'm not adverse to opening it up. Do you have the link to the solution you found that required opening the tablet? Maybe I'll give it a try.
boggessb said:
I'm in the same state after trying to update from 10.2 to 11. Just sits at the ASUS logo screen. No fastboot or recovery. I can get it to turn off by holding the up volume and inserting a paper clip into the reset switch hole. Otherwise I have been totally unsuccessful in getting it to do anything else. At this point I'm not adverse to opening it up. Do you have the link to the solution you found that required opening the tablet? Maybe I'll give it a try.
Click to expand...
Click to collapse
You would have to open it and replace the motherboard with a new one like this:
http://forum.xda-developers.com/showthread.php?t=2368372
With a new part like this:
http://www.ebay.com/itm/like/390706401658?lpid=82
Hi everyone, I just bought a N5 yesterday (i was using a N4 for almost 2 years) and I unlocked my device using the Nexus Root Toolkit, flashed the latest TWRP, installed ParanoidAndroid as my main OS and everything was fine untill the next step...
I was an avid user of MultiRom on my N4, so I flashed MultiRom on my N5 and everything was fine, I even tried to flash the official MiUI as a secondary OS but i got some errors and I just deleted that listed rom, no biggies... after that I booted into PA and flashed a custom kernel.
First, I flashed Franco's using his tool, and everything went smooth. I even restarted the device like 2 or 3 times while i was installing the usual apps (xposed, changed the font etc), the problem started when I downloaded the HellsCore kernel app from the playstore and flashed the kernel, after that, every time I try to boot my device it gets stuck on a black screen, it doesnt even show the Google logo with the unlocked icon at the beginning, it just gets stuck at that point.
My guess was that the Hellscore kernel had some issues with Multirom, and I started the fastboot recovery via ADB and flashed Franco's Kernel again... nothing happened, I still got a black screen.
I tried flashing the entire rom again (PA) and the same, black screen.
I also tried installing the original TWRP (not the MultiRom modded TWRP) and guess what??? I stilll got the same black screen.
The only way to get past thu it is to disconnect my device from USB, press power for 10 secs and after that i have to press power+volup+voldown.
That gets me to the fastboot. If I try to boot to the OS from there, i get a black screen. If I try to boot into the recovery, it boots ok.
The only way to boot into ParanoidAndroid is using the Nexus Root Toolkit and using the Franco's Kernel (r57) to boot TEMPORARY into the OS.
I dont know what else can I try, can someone please give me some advice??? Please. D=
Thanks in advance!!!
Return to stock. Links via signature.
Sent from my Nexus 5 using Tapatalk
Hey everyone, I have a potentially silly question, but searching here and google hasn't helped me.
I decided to try out two custom roms for the z3, Carbon and Lineage, but once I installed them using a recovery (TWRP specifically), I was unable to get back into it. When I started the phone, I'd see the purple led, doing nothing booted into the rom, pressing either vol+ or vol- would change it to orange and a few seconds later, the phone would reboot again and show the purple led again. If I flashed the recovery again, the rom would no longer boot.
I feel like there is something super simple I'm missing with the flashing, but possibly can't describe it well enough to search effectively.
P.S. The reason I'm trying to get into recovery again (otherwise it wouldn't be a problem) is to do things like flash gapps, superuser, etc.
First up I would always recommend flashing the rom, gapps and your superuser in one go.
Sometimes it get's really messy when doing it after booting the rom without anything.
So now I guess you didn't upgrade your bootloader, did you?
Because the older bootloader didn't have a partition for the recovery that would survive a new rom flash (sometimes), but the new one does. But if you lost your recovery, you can easily just boot into fastboot mode and fastboot flash your recovery and instantly boot into it.
It also could be a problem of the wrong recovery you're using. Which one did you use up until now?
You were correct. Because I had a pre-rooted stock firmware, I thought I was on the latest. Turns out I was one version behind, the one version that did as you described. Once I flashed that first, it was working again. Thanks
I flashed cwm recovery over TWRP from this link below . now phone is not power on?
http://androidhost.org/hUhuh
Any suggestion. :crying:
sanrajbhar said:
I flashed cwm recovery over TWRP from this link below . now phone is not power on?
http://androidhost.org/hUhuh
Any suggestion. :crying:
Click to expand...
Click to collapse
Press volume down while powering on. Does the bootloader appear? If it does, use
Code:
fastboot flash recovery NAMEOFTWRPIMAGE.img
Code:
fastboot boot NAMEOFTWRPIMAGE.img
Backup your data, reboot to bootloader and flash stock ROM before proceeding to flash a custom ROM (or try flashing the custom one directly).
xMotoDA said:
Press volume down while powering on. Does the bootloader appear? If it does, use
Code:
fastboot flash recovery NAMEOFTWRPIMAGE.img
Code:
fastboot boot NAMEOFTWRPIMAGE.img
Backup your data, reboot to bootloader and flash stock ROM before proceeding to flash a custom ROM (or try flashing the custom one directly).
Click to expand...
Click to collapse
I tried volume down with power button but it does not working, no bootloader or sceen on. can I assume now nothing can be done.
My phone was rooted and installed with AOSP rom .
sanrajbhar said:
I tried volume down with power button but it does not working, no bootloader or sceen on. can I assume now nothing can be done.
My phone was rooted and installed with AOSP rom .
Click to expand...
Click to collapse
I have a similar issue, as my phone also cannot turn on and I have TWRP recovery.
I had rooted my phone with SuperSU and unlocked the bootloader via motorola's tool. But then due to SafetyNet, apps such as Snapchat wouldn't work (cant log in), and I couldn't download Netflix (totally a huge issue).
So I decided to try switching to Magisk instead, as I heard that uses systemless root that doesnt trip Safety Net. While uninstalling SuperSU (using the built in feature for full removal), I was able to uninstall SuperSU and unroot my phone, but was not able to restore the stock boot image in the process. It was at this point I made a NANdroid backup in case I stuffed anything up.
Because of this, I was unable to flash Magisk via the TWRP recovery, so I downloaded a previous version of the firmware from January to flash back to from here. After flashing this and also wiping the user data, my phone booted up fine and worked, and appeared to be in normal condition.
However, then I elected to download and install the firmware update. This all went well, and was installing, until just at the end of the process, when the phone turned off. It had over 60% battery at the time.
At this point in time I'm still unable to get it to boot up, even into recovery or fastboot mode, so I cant really do anything, or restore my NANdroid backup.
If I plug it into my laptop, and hold the power + volume button down for a period of time, I can hear the USB connected tone (Windows 10), which then switches to a disconnected tone and a "USB device malfunctioned" error message pops up.
I tried leaving it unplugged all of last night just in case it was stuck in a boot loop or something so the screen couldn't display anything, in order to flatten the battery, but obviously I couldn't tell any difference. I'm currently now trying to have it plugged into power for an extended period of time just in case it is actually just flat. The current condition is just a black screen as if there was no power at all, with no lights or anything, regardless of a charger being connected, with the buttons not doing anything (I've attempted holding down the power and volume down buttons together for at least 2 minutes to no effect)
Any help would be greatly appreciated.
My specs: Moto G Turbo (2015), model XT1557, running Android 6.0.1. Can't remember exactly, but it previously had the latest firmware available before I tried flashing the January firmware.
I have BLN-L22 device. I installed TWRP recovery 3.1.1- berlin and it installed correctly. Then I found the latest version 3.2.1-berlin on official TWRP app. So I flashed that one and rebooted to recovery. Since then the phone is stuck at the bootscreen which shows 'Phone is unlocked, booting' message.
I can't connect to PC and how can I recover to original?
Official TWRP app (and relative site obviously) leads to a non working build of TWRP, i stumbled upon the same scene too while flashing official 3.1.0 version took by their site... Don't know why. Modded versions of TWRP made by OpenKirin team and HassanMirza01 works correctly instead. Here https://forum.xda-developers.com/honor-6x/development/twrp-honor-6x-hassanmirza01-t3733201 you'll find a working 3.2.1-0 version, i tested it by myself.
Now, to get rid of this and flash a working TWRP, you have to boot to fastboot mode with manual method, so begin with completely shut off the phone by keeping held power button for 10+ seconds.
Then, connect the phone to PC with the USB cable, and boot it up by keeping pressed power button and held down volume - immediately as you hear the vibration. From fastboot, you'll be able to flash back the working TWRP.
Problem Solved
RedSkull23 said:
Official TWRP app (and relative site obviously) leads to a non working build of TWRP, i stumbled upon the same scene too while flashing official 3.1.0 version took by their site... Don't know why. Modded versions of TWRP made by OpenKirin team and HassanMirza01 works correctly instead. Here https://forum.xda-developers.com/honor-6x/development/twrp-honor-6x-hassanmirza01-t3733201 you'll find a working 3.2.1-0 version, i tested it by myself.
Now, to get rid of this and flash a working TWRP, you have to boot to fastboot mode with manual method, so begin with completely shut off the phone by keeping held power button for 10+ seconds.
Then, connect the phone to PC with the USB cable, and boot it up by keeping pressed power button and held down volume - immediately as you hear the vibration. From fastboot, you'll be able to flash back the working TWRP.
Click to expand...
Click to collapse
Hi Thank you so much. The phone was restarting continuously after holding the power button. So I tried by pressing the power and volume down button which took me to fastboot.
Then I could install the compatible version of TWRP successfully.:good:
kpk1307 said:
Hi Thank you so much. The phone was restarting continuously after holding the power button. So I tried by pressing the power and volume down button which took me to fastboot.
Then I could install the compatible version of TWRP successfully.:good:
Click to expand...
Click to collapse
Good job!
RedSkull23 said:
Good job!
Click to expand...
Click to collapse
Hello there!!! help me. i too installed the 3.1 berlin and got stuck.even i have tried installing 3.2 and still i am stuck.no error while installing in both the images though.the screen just got stuck your device is booting..plz help
Venom0425 said:
Hello there!!! help me. i too installed the 3.1 berlin and got stuck.even i have tried installing 3.2 and still i am stuck.no error while installing in both the images though.the screen just got stuck your device is booting..plz help
Click to expand...
Click to collapse
Did you solve your issue.....I am also having same issue now. ..whatever recovery I flash....its get success but still it gets stuck on you are booting now
nokiasatyam said:
Did you solve your issue.....I am also having same issue now. ..whatever recovery I flash....its get success but still it gets stuck on you are booting now
Click to expand...
Click to collapse
You can successfully flash even non compatible images. the problem only arises when you boot them. Simply, they won't be able to boot because they're incompatible.
first, get into fastboot, flash compatible recovery(they are different for emui 5 and 8, so check before you flash). Then boot to recovery by pressing and holding power and volume up button at once from the fastboot mode itself.
Update me with the result. I'll tell you what to do next based on whether the flash works or not.