Hi Guys,
I have been give a Zenfone 2 which cannot reboot into stock recovery or any recovery, basically at the bootloader menu when you select recovery it reboots and goes back to the bootloader menu.
I've installed Rom Manager and it says both TWRP and CWM are installed.
So I believe this has multiple Recoverys and it basically cant use any, I have attempted to flash it back to stock but it wont again even let me into recovery that way.
I was rooted but I fully unrooted it to see if this would make a difference but it made no difference.
The bootloader says unknown and the screen is black on start with the Asus logo so would that suggest it has not got an unlocked bootloader either if so I believe the person who owns the phone tried to flash the untethered version of TWRP without having this unlocked ?
Any ideas how to get this back to stock and a recovery working ?
Thanks
Have you ever tried flashing stock fastboot?
I think the guide of "changing phone's SKU to WW version" can do the trick. Doing this can have official fastboot and recovery flashed on your phone.
Hello,
As the title pretty much explains, I want to know how to prevent stock recovery replacing twrp when we flash the nougat oos zip? Even when I flash twrp image in recovery after oos nougat installation, the damn thing still overwrites twrp and I need to use a laptop to flash twrp again.
abhibnl said:
Hello,
As the title pretty much explains, I want to know how to prevent stock recovery replacing twrp when we flash the nougat oos zip? Even when I flash twrp image in recovery after oos nougat installation, the damn thing still overwrites twrp and I need to use a laptop to flash twrp again.
Click to expand...
Click to collapse
To keep twrp
1.flash stock oos
2.flash twrp
3.reboot to recovery - most imp step
4.reboot to system
JumboMan said:
To keep twrp
1.flash stock oos
2.flash twrp
3.reboot to recovery - most imp step
4.reboot to system
Click to expand...
Click to collapse
Did the same but unfortunatley, it booted straight into the rom rather than recovery.
abhibnl said:
Did the same but unfortunatley, it booted straight into the rom rather than recovery.
Click to expand...
Click to collapse
That "bootloader unlocked" warning is pretty useful. When it shows up, press a volume buttton (any) and you'll get a list of options. Choose recovery there to make sure it doesn't try to go directly into system.
Sent from my OnePlus 3 using Tapatalk
Explorer23 said:
That "bootloader unlocked" warning is pretty useful. When it shows up, press a volume buttton (any) and you'll get a list of options. Choose recovery there to make sure it doesn't try to go directly into system.
Sent from my OnePlus 3 using Tapatalk
Click to expand...
Click to collapse
I can vouch for the usefulness of the warning screen. Quite accidentally I found that option while trying to install 4.0.2 and TWRP and in the process trying to avoid dm_verity. It is really useful because sometimes, despite your choosing to boot into recovery, the phone stubbornly boots into system.
i know its a old threat but i have the same problem, and tested all the steps above and still is my OP3T booting into stock recovery after i installed TWRP. do you guys maybe have a new solution for the problem ?
PIPT said:
i know its a old threat but i have the same problem, and tested all the steps above and still is my OP3T booting into stock recovery after i installed TWRP. do you guys maybe have a new solution for the problem ?
Click to expand...
Click to collapse
Another method is to flash Magisk immediately after TWRP before booting into system. Then boot into system.
Hi,
My Nexus 5X died some days ago, and Google shiped me another one. But this new device have the unbelievable "NO RPMB" message that locks the bootloader (this is a known issue where the bootloader is automatically re-locked after each reboot, making flashing factory images an harassing journey).
I installed TWRP to flash a custom rom but after each reboot on the system,TWRP was replaced by stock recovery !
Do anyone knows how resolve this problem ? I suppose if I can flash a custom rom it will solve a great part of the problem... I'm actually thinking of sell this new phone and get another device like oneplus.
Any help will be appreciated ! ?
Atok_fr said:
Hi,
My Nexus 5X died some days ago, and Google shiped me another one. But this new device have the unbelievable "NO RPMB" message that locks the bootloader (this is a known issue where the bootloader is automatically re-locked after each reboot, making flashing factory images an harassing journey).
I installed TWRP to flash a custom rom but after each reboot on the system,TWRP was replaced by stock recovery !
Do anyone knows how resolve this problem ? I suppose if I can flash a custom rom it will solve a great part of the problem... I'm actually thinking of sell this new phone and get another device like oneplus.
Any help will be appreciated !
Click to expand...
Click to collapse
Unlock bootloader, flash TWRP and boot straight to recovery without rebooting, perform a factory reset and root. That should make TWRP stick. If it doesn't, you can then use the TWRP manager to install TWRP again.
CazeW said:
Unlock bootloader, flash TWRP and boot straight to recovery without rebooting, perform a factory reset and root. That should make TWRP stick. If it doesn't, you can then use the TWRP manager to install TWRP again.
Click to expand...
Click to collapse
Thanks mate, it worked !
CazeW said:
Unlock bootloader, flash TWRP and boot straight to recovery without rebooting, perform a factory reset and root. That should make TWRP stick. If it doesn't, you can then use the TWRP manager to install TWRP again.
Click to expand...
Click to collapse
Quick question. As I just picked up a refurb N5X on the cheap and I plan to use it (fingers crossed it does have RPMB, not holding my breath though)- how viable are custom ROMs on this thing? The reddit thread that started this all states to leave /system unmodified but other comments say that they've flashed custom kernels.
So- if this is the case, would the order be unlock bootloader>flash stock images/noencrypt>flash TWRP>boot into TWRP> factory reset> boot into Oreo> unlock bootloader and boot into TWRP when modifications need to be made?
Thanks.
negusp said:
Quick question. As I just picked up a refurb N5X on the cheap and I plan to use it (fingers crossed it does have RPMB, not holding my breath though)- how viable are custom ROMs on this thing? The reddit thread that started this all states to leave /system unmodified but other comments say that they've flashed custom kernels.
So- if this is the case, would the order be unlock bootloader>flash stock images/noencrypt>flash TWRP>boot into TWRP> factory reset> boot into Oreo> unlock bootloader and boot into TWRP when modifications need to be made?
Thanks.
Click to expand...
Click to collapse
I use a custom kernel so that works just fine, haven't tried a custom ROM though. You don't have to unlock the bootloader every time to make changes as long as you have TWRP. I'm not entirely sure but I think rooting made the TWRP stick. If not, you can still install it from the TWRP app as you have root.
After you've installed the stock images, it should be enough to boot into TWRP, do a factory reset and flash the custom ROM.
CazeW said:
I use a custom kernel so that works just fine, haven't tried a custom ROM though. You don't have to unlock the bootloader every time to make changes as long as you have TWRP. I'm not entirely sure but I think rooting made the TWRP stick. If not, you can still install it from the TWRP app as you have root.
After you've installed the stock images, it should be enough to boot into TWRP, do a factory reset and flash the custom ROM.
Click to expand...
Click to collapse
So once TWRP is installed and "stuck", it can make modifications to traditionally "root" partitions (system, data, etc.?).
Also, did you flash the noforce encrypt boot image (and then wiping userdata)? Or does the stock image work?
negusp said:
So once TWRP is installed and "stuck", it can make modifications to traditionally "root" partitions (system, data, etc.?).
Also, did you flash the noforce encrypt boot image (and then wiping userdata)? Or does the stock image work?
Click to expand...
Click to collapse
Yes. I've for example installed all the OTAs from TWRP (except Oreo).
Stock image works.
CazeW said:
Yes. I've for example installed all the OTAs from TWRP (except Oreo).
Stock image works.
Click to expand...
Click to collapse
Thanks. Does DRM content work? I've also read conflicting reports as to apps like Netflix working on Oreo.
negusp said:
Thanks. Does DRM content work? I've also read conflicting reports as to apps like Netflix working on Oreo.
Click to expand...
Click to collapse
I don't use Netflix so can't say if that works but Play Movies worked on Nougat.
CazeW said:
Unlock bootloader, flash TWRP and boot straight to recovery without rebooting, perform a factory reset and root. That should make TWRP stick. If it doesn't, you can then use the TWRP manager to install TWRP again.
Click to expand...
Click to collapse
Hello, i have the same NO RPMB problem Im using latest stock rom 8.1 (December patch), radio, bootloader and vendor.
How can i boot straight into recovery without rebooting? Do i need to flash vendor.img too? (i would like flash latest AEX rom).
If im not wrong i should do this procedure as suggested right?
- unlock bootloader from fastboot
- flash latest twrp recovery from fastboot without rebooting (this will work? Because in the N5X root thread it's written to reboot first)
- get into twrp without rebooting (how do that?)
- install root (i will use latest Magisk)
- perform factory reset
- wipe system, data, cache, and dalvik cache
- install custom rom, gapps...
- wipe cache and dalvik, and reboot
Finally i will have a rooted device with custom rom and bootloader locked again right?
Or is preferred this solution of Reddit user?
https://www.reddit.com/r/nexus5x/comments/5hj0r0/bootloop_after_lg_replaced_mainboard_bootloader
sigibian said:
Hello, i have the same NO RPMB problem Im using latest stock rom 8.1 (December patch), radio, bootloader and vendor.
How can i boot straight into recovery without rebooting? Do i need to flash vendor.img too? (i would like flash latest AEX rom).
If im not wrong i should do this procedure as suggested right?
- unlock bootloader from fastboot
- flash latest twrp recovery from fastboot without rebooting (this will work? Because in the N5X root thread it's written to reboot first)
- get into twrp without rebooting (how do that?)
- install root (i will use latest Magisk)
- perform factory reset
- wipe system, data, cache, and dalvik cache
- install custom rom, gapps...
- wipe cache and dalvik, and reboot
Finally i will have a rooted device with custom rom and bootloader locked again right?
Or is preferred this solution of Reddit user?
https://www.reddit.com/r/nexus5x/comments/5hj0r0/bootloop_after_lg_replaced_mainboard_bootloader
Click to expand...
Click to collapse
I haven't tried this with a custom ROM but I would try it like this.
- Unlock bootloader from fastboot
- Flash TWRP from fastboot
- Select boot to recovery from the fastboot menu
- Do a factory reset
- Wipe system, cache, and dalvik cache
- Flash ROM, flash Gapps
- Flash Magisk
- Reboot
Hey all,
I'm trying to better understand what I'm doing with my phone here. Currently I have my OP3 rooted (aka unlocked bootloader, correct?) and on 8.0.0.
1. If I wanted to keep it rooted and reinstall the OS, is this as simple as downloading whichever ROM I want, copying it to my phone's internal storage, and flashing it in recovery using TWRP?
2. Is stock recovery (recovery_OP3.img on the oneplus.net website) the same part of the software as TWRP? As in the stock recovery is locked bootloader and TWRP is unlocked bootloader?
3. I've been searching for the most recent root guide, can I get a recommendation? I've read that SuperSU is not the thing to use any longer, but rather Magisk. Correct?
4. What is boot.img?
Thanks all
Shoruk3n said:
Hey all,
I'm trying to better understand what I'm doing with my phone here. Currently I have my OP3 rooted (aka unlocked bootloader, correct?) and on 8.0.0.
1. If I wanted to keep it rooted and reinstall the OS, is this as simple as downloading whichever ROM I want, copying it to my phone's internal storage, and flashing it in recovery using TWRP?
2. Is stock recovery (recovery_OP3.img on the oneplus.net website) the same part of the software as TWRP? As in the stock recovery is locked bootloader and TWRP is unlocked bootloader?
3. I've been searching for the most recent root guide, can I get a recommendation? I've read that SuperSU is not the thing to use any longer, but rather Magisk. Correct?
4. What is boot.img?
Thanks all
Click to expand...
Click to collapse
1. If you switch roms, always do a clean install (wipe all partitions) . If you want to get rid off all the mods wipe system and flash the same rom + gapps + root. You won't loose data since you are only modifying the system partition.
2. Stock recovery by Oneplus is as if says stock, you littery can't do anything with it apart from upgrading your OOS, wiping cache partitions and doing a factory reset. I do recommend the TWRP provided by Bluspark since that seems to be the only one I tried without any issues whatsoever.
3. Magisk is the new root method in my opinion, it supports Magisk modules which simply are mods that can be installed and removed with a single click (reboot required tho). You can compare it to xposed but very limited when compared.
4. Boot.img is your kernel, never flash standalone img files apart from TWRP since the kernel modifies more the only the boot img. Always flash the full zip.
Hello, I was just trying to install a custom ROM (Resurrection Remix) on my phone, but now I can't get out of the bootloader.
The steps I took were:
Install TWRP
Root with Magisk (for Titanium Backup)
Factory Reset in TWRP
Flash the RR rom zip file
and now when I turn my phone on, it goes through the bootloader unlock notice and the Google screen, but then it just goes into the bootloader.
I tried going into LineageOS recovery and doing an OEM sideload, but when I go into Apply Update --> Apply from ADB, on my computer, adb devices shows nothing.
Someone please help me.
SuperModder123 said:
Hello, I was just trying to install a custom ROM (Resurrection Remix) on my phone, but now I can't get out of the bootloader.
Click to expand...
Click to collapse
So fastboot should work. You can always flash the stock ROM first and continue from there.
Instructions: https://developers.google.com/android/images
Try the following,
Go back to stock
Boot twrp
Swipe to factory reset in twrp
Flash RR ROM zip
Flash TWRP zip
Boot to system (it should go to OS)
reboot back to TWRP
Flash custom kernel (optional)
Flash Magisk for root
Boot back to system