I updated the EMUI version on my ALE-L02 from 3.1 to 4.1 using TWRP recovery. The disadvantage of this is that I lost TWRP afterwards as it was replaced by the stock recovery.
I tried to flash TWRP to the phone again using ADB, which said that the flash was successful. However, when rebooting into recovery mode, it boots into the stock recovery. Why is it doing this/how do I fix it?
You need to follow the instructions to get TWRP to boot after install. https://forum.xda-developers.com/showpost.php?p=71429023&postcount=73
JpegXguy said:
You need to follow the instructions to get TWRP to boot after install. https://forum.xda-developers.com/showpost.php?p=71429023&postcount=73
Click to expand...
Click to collapse
Thanks! Will try later on
mackelbot said:
I updated the EMUI version on my ALE-L02 from 3.1 to 4.1 using TWRP recovery. The disadvantage of this is that I lost TWRP afterwards as it was replaced by the stock recovery.
I tried to flash TWRP to the phone again using ADB, which said that the flash was successful. However, when rebooting into recovery mode, it boots into the stock recovery. Why is it doing this/how do I fix it?
Click to expand...
Click to collapse
Try just pressing vol. up+ power, that happened to me sometimes. Also, as a tip, when flashing EMUI from TWRP first backup recovery than flash it. After that, don't reboot, go back and restore the recovery. Much easier for me.
Related
Going to need some help on this one. Got root on stock through ioRoot22. Flashed twrp 2.6.3.3 through FreeGee. Backed up stock rom in twrp then reboot to stock rom to confirm boot
Went back into TWRP then Wiped device then attempted flashing Vanir.
Flashed Vanir zip
Flashed gapps zip
Attempted flashing kernel from here http://forum.xda-developers.com/showthread.php?t=2638091
Came back with flash failed with an assert issue with loki, knowing I probably shouldnt have rebooted and restored my stock backup. I didnt think anything of it. Now Im stuck in fastboot and can gain access to download mode.Currently downloading the 11A tot/kdz and reading over this guide
http://forum.xda-developers.com/showthread.php?t=2448960
Would I need a stock recovery for the VS980 to complete download mode restoral? if so would anyone have it?
Ok so in the end through some patience, I was able to restore my stock rom by gaining access to TWRP through the normal "factory reset with stock recovery" method of booting. Was tricky because it wouldnt power off and bootlooping to fastboot. While in fastboot I held Vol - and Power so I can gain access again to TWRP. Restored the stock rom and all is well.
Snuzzo said:
Ok so in the end through some patience, I was able to restore my stock rom by gaining access to TWRP through the normal "factory reset with stock recovery" method of booting. Was tricky because it wouldnt power off and bootlooping to fastboot. While in fastboot I held Vol - and Power so I can gain access again to TWRP. Restored the stock rom and all is well.
Click to expand...
Click to collapse
Thanks for sharing.
Sent from my LG-D802 using Tapatalk
Ok so apparently there are some kernels/roms who have not updated their loki_patch file yet. From what I've been reading up which needs to be done for the roms to correspond to the updates. Am I correct?
I decided today to try and root my phone and followed the steps on this tutorial: http://forum.xda-developers.com/nexus-4/general/nexus-4-guide-unlock-bootloader-root-t2266654
I had unlocked my phone and installed the latest version of TWRP. Now I can only boot into TWRP and bootloader. My phone is not being picked up by my PC. I tried a factory reset and format of data on TWRP but my phone still only boots into TWRP.
Is my phone permanently bricked?
Any help will be greatly appreciated
I actually have just made some progress now. I've managed to get the phone connected to the computer by going into ADB sideload and installing the ADB drivers again on my computer.
Typing ADB devices in CMD now shows my device as connected.
Any advice on what I should do now?
What happens when you try to boot it normally? Is it stuck at the boot animation or does it go directly to the bootloader or recovery? Since you already had to wipe everything you could try flashing a factory image via fastboot.
theminikiller said:
What happens when you try to boot it normally? Is it stuck at the boot animation or does it go directly to the bootloader or recovery? Since you already had to wipe everything you could try flashing a factory image via fastboot.
Click to expand...
Click to collapse
Booting the phone normally loads it into TWRP. Booting the phone with the volume key pressed down loads the bootloader. I think I may have just wiped the OS present on the Phone.
I want my phone to be rooted running CyanogenMOD (phone is currently unrooted). Should I first install a stock rom then root by installing SuperSU and CyanogenMOD or can I just skip installing a stock rom and install SuperSU and CyanogenMOD?
Thanks for the help
You could try flashing a cyanogenmod zip from TWRP, and if that doesn't work I would suggest flashing I factory image.
theminikiller said:
You could try flashing a cyanogenmod zip from TWRP, and if that doesn't work I would suggest flashing I factory image.
Click to expand...
Click to collapse
But my phone is not rooted yet. Can I install SuperSU by copying onto my phone and installing it through TWRP?
umair_ said:
But my phone is not rooted yet. Can I install SuperSU by copying onto my phone and installing it through TWRP?
Click to expand...
Click to collapse
Yes, if it is a zip file. But I'm pretty sure installing cyanogenmod will automatically root it for you.
theminikiller said:
Yes, if it is a zip file. But I'm pretty sure installing cyanogenmod will automatically root it for you.
Click to expand...
Click to collapse
I installed SuperSU then CyanogenMOD and lastly GApps. It still only boots into TWRP and it doesn't look like there has been any files added to the phone's storage. Should I first flash a stock rom and then try to install CyanogenMOD?
umair_ said:
I installed SuperSU then CyanogenMOD and lastly GApps. It still only boots into TWRP and it doesn't look like there has been any files added to the phone's storage. Should I first flash a stock rom and then try to install CyanogenMOD?
Click to expand...
Click to collapse
Yes, try flashing a factory image. If it boots then you could try flashing cyanogenmod.
EDIT: here is a guide on how to flash a factory image: http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
theminikiller said:
Yes, try flashing a factory image. If it boots then you could try flashing cyanogenmod.
EDIT: here is a guide on how to flash a factory image: http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
Click to expand...
Click to collapse
I've managed to get it all working by first flashing the stock ROM and starting all over again.
Thanks for your help.
Is there a workaround to this other than flashing factory images...?
hwweiler said:
Is there a workaround to this other than flashing factory images...?
Click to expand...
Click to collapse
@hwweiler, No friend there is no other way.Please before do this as is one direction way take the pain to look on my post #180 on zaclmon's thread http://forum.xda-developers.com/nexus-4/orig-development/wip-aosp-7-0-nougat-t3448444/page18 and keep in mind that is impossible to return back on any nandroid backup u kept e.g to 5.1.1 or M furthermore its also impossible to flash any rom zip if u use this N (WIP) rom,the only way to have a workable phone again is to flash the stock rom from scratch.Exceperienced with and never again untill we have the appropriate solution..The twrp used and i still use on M is TWRP 3.0.2.0.The possibility to return on LP ffrom M and reverse still exists but not when u flash this rom.
Regards,Christos
Hey guys, I'm a longtime XDA browser but hardly ever post. I have the MXPE rooted with the newest TWRP build and has been running great since I got it. last night flashed the Deodexed 6.0 build from AICPs 5.1.1. I had some issues with the SD card being mounted as internal storage and erasing something so I tried to flash back to stock as my nandroids weren't seen as usable.
Long story short when I flashed back to stock, the recovery would never take. I've flashed the stock recovery and twrp to no avail. For some reason it wont actually stick. Everything else is back to stock but that. When I used the win toolkit and tried to flash twrp again it said something about the folder locations so I'm wondering if I messed something in the partitions.
Question is, have you guys ran into this issue or have any insight on where to go from here? I've looked around but I couldn't find a post that the same as this issue. As a side note, I can get into the bootloader just fine.
I appreciate any info that someone can provide.
Flash twrp. Reboot back to recovery from recovery. Reboot system.
Hopefully it's that easy. Stock os flashes stock recovery on boot. Rebooting recovery from recovery prevents that from happening.
From TWRP:
"Note many devices will replace your custom recovery automatically during first boot.... Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
mxpe 6.0
Thanks for the info ffejy462. What happens when I try to flash TWRP and it doesnt stick? I know for a fact that I can boot into it temporarily with fastboot boot and the recovery file. Should I just flash it from there?
THEFILLTER said:
Thanks for the info ffejy462. What happens when I try to flash TWRP and it doesnt stick? I know for a fact that I can boot into it temporarily with fastboot boot and the recovery file. Should I just flash it from there?
Click to expand...
Click to collapse
I'm sorry I didn't see this sooner. Flash recovery with fastboot. Boot into recovery. From reboot menu in recovery, select reboot recovery. Twrp will patch so recovery isn't lost again.
mxpe 6.0
That did it. thanks alot ffejy462!
Hello everyone.
I've recently got the notification from the updater saying that oxygen OS 3.1.0 was out and awaiting to be downloaded (was on 3.0.2).
Since I unlocked bootloader/installed twrp/installed supersu when I was on 2.1.0 I wanted to update using the same method that I had used to update it before: install full zip of 3.0.2, install zip 3.0.2->3.1.0, install supersu
Problem is after I've done this the phone was stuck into booting animation when booting into system.
And since I'm dumb and nervous I thought that wiping /system before the installation was the solution.
So once again, this time with also system wipe, full 3.0.2->ota update->install supersu
Now you already probably understood that not only the phone is booting forever, but also I lost access to twrp and only have fastboot showing up when trying to boot through power+vol up
What can I do? What did I do wrong?
Thanks for the attention
Edit: I can access recovery, had the wrong combo of buttons going (i was pressing power+vol up but it's power+vol down)
I repeat, TWRP is fully accessible
Edit 2: Since TWRP was fully accessible I reinstalled both full zip and 3.0.2->3.1.0 zip without supersu and it booted... What did I do wrong with supersu?
Depends on the SuperSU zip y supposed you need the one specific for oos3 beta or h2os
Sent from my ONE A2005 using Tapatalk
I fresh installed 3.1.0 but after booting up and flashing supersu v2.78 i get bootloop. Before it always worked so i think we need to wait for an updated version of supersu.
I boot in fastboot modes by volume up + power and then connect with pc en boot in recovery with fastboot command. 'fastboot boot recovery.img'
Burn2Hell said:
I fresh installed 3.1.0 but after booting up and flashing supersu v2.78 i get bootloop. Before it always worked so i think we need to wait for an updated version of supersu.
I boot in fastboot modes by volume up + power and then connect with pc en boot in recovery with fastboot command. 'fastboot boot recovery.img'
Click to expand...
Click to collapse
Did you try flashing the modified SuperSu 2.78 zip?
I had the same problem until I flashed the SuperSu mentioned from Spannaa the post before.
It happened to me too and the fix is to flash the modified supersu.
Nimwe said:
Hello everyone.
I've recently got the notification from the updater saying that oxygen OS 3.1.0 was out and awaiting to be downloaded (was on 3.0.2).
Since I unlocked bootloader/installed twrp/installed supersu when I was on 2.1.0 I wanted to update using the same method that I had used to update it before: install full zip of 3.0.2, install zip 3.0.2->3.1.0, install supersu
Problem is after I've done this the phone was stuck into booting animation when booting into system.
And since I'm dumb and nervous I thought that wiping /system before the installation was the solution.
So once again, this time with also system wipe, full 3.0.2->ota update->install supersu
Now you already probably understood that not only the phone is booting forever, but also I lost access to twrp and only have fastboot showing up when trying to boot through power+vol up
What can I do? What did I do wrong?
Thanks for the attention
Edit: I can access recovery, had the wrong combo of buttons going (i was pressing power+vol up but it's power+vol down)
I repeat, TWRP is fully accessible
Edit 2: Since TWRP was fully accessible I reinstalled both full zip and 3.0.2->3.1.0 zip without supersu and it booted... What did I do wrong with supersu?
Click to expand...
Click to collapse
Can you please specify the brief step by step procedure of flashing 3.1.0 on 3.0.2 (Clean flash)!Please!
Sent from my ONE A2003 using Tapatalk
nitishgupta said:
Can you please specify the brief step by step procedure of flashing 3.1.0 on 3.0.2 (Clean flash)!Please!
Click to expand...
Click to collapse
Download the full OOS 3.1.0 zip from post #1 in the Oxygen mirrors thread and flash it via recovery.
If you want root, flash a SuperSU zip from the same post.
I installed the twrp 3.0.2.2 and after installed a kernel which made the phone stuck on zte logo.
I tried to flash to the stock files using this guide:
https://forum.xda-developers.com/axon-7/how-to/a2017g-nougat-b08-twrp-bootstack-t3696479v
but when i try to install the superSu the twrp stuck after extracing files, then the phone just shuts down.
what can I do?
Shakedbuk said:
I installed the twrp 3.0.2.2 and after installed a kernel which made the phone stuck on zte logo.
I tried to flash to the stock files using this guide:
https://forum.xda-developers.com/axon-7/how-to/a2017g-nougat-b08-twrp-bootstack-t3696479v
but when i try to install the superSu the twrp stuck after extracing files, then the phone just shuts down.
what can I do?
Click to expand...
Click to collapse
Update your twrp, there's no need to use that old version... my phone reboots when it wants when it has opd twrp versions
Download twrp 3.1.1-0
Put it on your phone, maybe via adb or through mtp if you have it
Go to Install -> hit the button on the right that says 'Install image'
Find the TWRP.img and install it, it will prompt you where to install it, put 'recovery'
Followed you instructions, but now i cant get into TWRP or the OS ):
Tried to flash it with axon7tool on pc, but got the same result, but when I tried to flash the 3.0.2. again, it worked.
Shakedbuk said:
Followed you instructions, but now i cant get into TWRP or the OS ):
Tried to flash it with axon7tool on pc, but got the same result, but when I tried to flash the 3.0.2. again, it worked.
Click to expand...
Click to collapse
Don't use axon7tool for this... you already have TWRP, the only thing you have to use axon7tool for is to install twrp when you have the stock recovery. after you have twrp on the phone just try not to use the PC except for maybe miflash
I tried both of this options.
Flashing new version of twrp through the old twrp resulted in black screen when i try to get to recovery.
So I flashed the old twrp from the pc, tried to flash the new one using the same method but it the same as i flashed it through the old twrp. (which mean that when i get to the recovery i get black screen)
ATM the situation is the same, system wont boot stuck on zte logo, twrp is 3.0.2.2 (there is another method to flash newer twrp?)
There is another option?
After wiping system in twrp i was able to install supersu, which means i completed this guide
https://forum.xda-developers.com/axon-7/how-to/a2017g-nougat-b08-twrp-bootstack-t3696479v
but still stuck on zte logo after i reboot , any help?
Shakedbuk said:
After wiping system in twrp i was able to install supersu, which means i completed this guide
https://forum.xda-developers.com/axon-7/how-to/a2017g-nougat-b08-twrp-bootstack-t3696479v
but still stuck on zte logo after i reboot , any help?
Click to expand...
Click to collapse
Wait, what did you do? Did you install everything again after wiping system?
Ya, afte i wiped the system it allowed me to install the supersu without interrupts, but it did not helped.
Anyway i manged to install purefusion os, system booted up, after that the new twrp updated successfully.
Shakedbuk said:
Ya, afte i wiped the system it allowed me to install the supersu without interrupts, but it did not helped.
Anyway i manged to install purefusion os, system booted up, after that the new twrp updated successfully.
Click to expand...
Click to collapse
You installed SuperSU without a system, and the phone did not boot up? Amirite?
what i did was wipe system dalvik cache, cache, after that install bootstack and the system files, and after that the supersu.
before i wiped the system, when i tried to install the supersu the twrp collapsed, after that it installed it but did not helped to make the system boot.