Hey all,
I successfully bootloader unlocked and rooted, and I installed TWRP. But as per the TWRP thread, touch is disabled on TWRP if you use ADB to reboot to recovery.
...so how the hell do I get into TWRP? LOL. The engineering bootloader is the only one that does fastboot, and since I patched my boot_a with TWRP, I can't exactly do that now. Otherwise there was no point to installing TWRP.
I'm so very close, I just need recovery to install custom roms!
Edit: Nevermind, figured it out. Like the V30+, you boot holding power up and power, immediately release power when the lg logo comes up, then keep pressing power. Then say yes to data erase.
But the TWRP guide had you install the Korean TWRP which is highly annoying. Found the USA version buried in another thread.
Related
Trying to install CyanogenMod for my razr maxx HD. Recently used RSDlite to install 183.46.10 after OTA KK update kept failing. Then used towelroot to root and motopocalype to unlock bootloader. Fastboot screen shows bootloader is unlocked with status code: 3.
I then followed the instructions on the CyanogenMod site to flash CWM 6.0.4.4 recovery using fastboot, and all appeared to work fine.
However, when I try to reboot into recovery, nothing happens. I get hung up on the motorola dual core flashscreen for about a minute or two, then the screen goes black, then the phone reboots normally.
I tried flashing a different copy of CWM, tried TRWP, and tried several third party apps from Google Play store to boot directly into recovery using software reboot instead of hardware keys - all with the same results. I even tried flashing custom CWM recovery using ROM Manager and Rashr, same result.
Do I have a corrupt recovery partition? Any suggestions for how to fix?
You need to install a recovery for that phone specifically.
http://androidhosting.org/Devs/Dhacker29/
Use the recovery files found here.
Edit: on the site I posted, browse to the msm8690 folder. There you will find the recovery files.
to make this even easier here
TWRP http://forum.xda-developers.com/showthread.php?t=2776515
CWM http://forum.xda-developers.com/showthread.php?t=2747535
next time be sure your flashing for this phone and bootloader
billycar11 said:
to make this even easier here
TWRP http://forum.xda-developers.com/showthread.php?t=2776515
CWM http://forum.xda-developers.com/showthread.php?t=2747535
next time be sure your flashing for this phone and bootloader
Click to expand...
Click to collapse
Thanks, guys, total noob mistake. I knew the recovery needed to be specific for the phone, but didn't realize it varied depending on the bootloader. Will try again with the right recovery!
billycar11 said:
to make this even easier here
TWRP http://forum.xda-developers.com/showthread.php?t=2776515
CWM http://forum.xda-developers.com/showthread.php?t=2747535
next time be sure your flashing for this phone and bootloader
Click to expand...
Click to collapse
Those recovery aren't sticking for me. Does anyone have a suggestion to fix that issue.
Pushing the buttons doesn't work.
The only thing that is working is place the phone in fastboot mode and flash the recovery to my device three time and then I will go straight in recovery and there it is.
Sent from my SM-N900V using Tapatalk
TheGman125 said:
Those recovery aren't sticking for me. Does anyone have a suggestion to fix that issue.
Pushing the buttons doesn't work.
The only thing that is working is place the phone in fastboot mode and flash the recovery to my device three time and then I will go straight in recovery and there it is.
Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
Your phone has been upgraded to Kit Kat and the bootloader unlocked, correct? The two recoveries linked to are for phones that already have already been upgraded to KK.
If so, power off your phone.
Then, hold down volume up and then press and hold power. After a few seconds, let go and the boot menu should come up.
Use Volume down to select "Recovery" and then hit "Volume Up". That should boot you into the custom recovery, depending on which one you flashed.
I prefer TWRP. CWM seemed buggy and it wouldn't always boot into it. A lot of times, I'd get a blank screen and would have to reflash it.
Another option is, when it's booted up, hooked up your phone to your pc and use adb to reboot it into recovery using "adb reboot recovery".
iBolski said:
Your phone has been upgraded to Kit Kat and the bootloader unlocked, correct? The two recoveries linked to are for phones that already have already been upgraded to KK.
If so, power off your phone.
Then, hold down volume up and then press and hold power. After a few seconds, let go and the boot menu should come up.
Use Volume down to select "Recovery" and then hit "Volume Up". That should boot you into the custom recovery, depending on which one you flashed.
I prefer TWRP. CWM seemed buggy and it wouldn't always boot into it. A lot of times, I'd get a blank screen and would have to reflash it.
Another option is, when it's booted up, hooked up your phone to your pc and use adb to reboot it into recovery using "adb reboot recovery".
Click to expand...
Click to collapse
Yep.. I had some issue with my devices. I tried the update well root and the devices didn't want to boot up anymore. So I had to RSD lite the devices back to health. So I do have the latest software for the devices. I guess. I am going to use Twrp since you say it boots fine from the boot menu.
TheGman125 said:
Yep.. I had some issue with my devices. I tried the update well root and the devices didn't want to boot up anymore. So I had to RSD lite the devices back to health. So I do have the latest software for the devices. I guess. I am going to use Twrp since you say it boots fine from the boot menu.
Click to expand...
Click to collapse
Is your bootloader unlocked? If not, that is your problem. You need to root, and then unlock the bootloader before you can flash TWRP and use CM.
iBolski said:
Is your bootloader unlocked? If not, that is your problem. You need to root, and then unlock the bootloader before you can flash TWRP and use CM.
Click to expand...
Click to collapse
Yes my bootloader is unlocked. Have code 3 on the devices.
try and unplug from USB when you reboot
I have been having this issue with flashing recovery on my Nex5 ever since I installed lollipop(factory image).
I have repeatedly tried to install TWRP (2.8.2.0) on my device but it just doesn't seem to stick no matter what I try.
Each time it gets installed but as soon the the system reboots, its gone. If I directly boot into the recovery from fastboot or bootup recoveryafter flash without restarting the bootloader, the TWRP logo shows up and then the device just restarts.
Please help me out here. Really want to go back to PA4
Thanks
You probably updated to LRX21O through OTA.
Go back to 4.4.4 through factory image. Boot system once. Reboot to bootloader. Flash twrp. Using vol keys, boot to recovery directly from bootloader. Flash PA.
agent47er said:
I have been having this issue with flashing recovery on my Nex5 ever since I installed lollipop(factory image).
I have repeatedly tried to install TWRP (2.8.2.0) on my device but it just doesn't seem to stick no matter what I try.
Each time it gets installed but as soon the the system reboots, its gone. If I directly boot into the recovery from fastboot or bootup recoveryafter flash without restarting the bootloader, the TWRP logo shows up and then the device just restarts.
Please help me out here. Really want to go back to PA4
Thanks
Click to expand...
Click to collapse
Read this.
I finally figured out how to unlock the bootloader after figuring out that I have to specify "-i 0x2e04" between "fastboot" and the fastboot command and I thought it was going well until after flashing TWRP custom recovery version 3.11 as per This thread's recommendation when attempting to boot into TWRP recovery simply takes me to, rather than the menu that's supposed to show up, a screen with the android mascot on it's back and a single line of text below it saying "No command".
I figured I might as well try reflashing, but the problem persisted. I then tried reflashing with a newer version of TWRP, version 3.2.3 as recommended by This guide. but instead of taking me to the "No command" screen, it just ends up in a boot loop as long as my finger is holding down the power + volume buttons. The boot loop ends, booting into the normal OS if I stop holding down the buttons.
How can I access the recovery to make a nandroid backup and install the magisk .zip file?
I've heard one or two guides make mention of a "no verity opt encrypt.zip" file but I haven't been able to find where I can download it. Could someone help me out?
root using magisk than install from official twrp app
tech2update said:
root using magisk than install from official twrp app
Click to expand...
Click to collapse
I can't access the apps on the phone because the phone is stuck in a bootloop
Hi all,
today I updated Magisk on my H830 (stock H83030c with TWRP) and now it's stuck in a boot loop.
Since the phone does not support flashing in fastboot, is there any way to fix this without re-flashing a stock kdz?
<edit>
The phone is showing the "bootloader unlocked warning", then flashes black and shows the warning again, over and over.
I can't enter TWRP, only fastboot and download mode.
Thanks,
schalli110
Never mind.
Mashing the power button like crazy finally got me into TWRP and I was able to reflash a stock boot.img and then an old version of Magisk.
Phew.
I'll leave this thread in the hopes it helps other poor souls.
I have the exact same problem (thanks Magisk team!). Can you expound on the power button technique that allowed you to access TWRP? By repeatedly pressing it?
Funny, I've seen multiple posts about this happening on G5 phones after the Magisk update, but nothing on the Magisk threads.
Hi there. I got trouble rooting my Blackview BV5500Pro with Android 9.0
Its not the first smartphone im rooting, so im not new to this. But im also not a professional or something, even english is not my native language so sorry for my bad grammar.
At first i tried the way i done this bevore to my smartphones:
1. Unlock OEM via Fastboot
2. Flash TWRP 3.3.0 (The only working twrp i found) to Recovery
3. Boot into TWRP.
To this point everything works fine.
But when i install Magisk 21.4. i get a bootloop.
also when i install SuperSu 2.8.2
So i tried to patch the boot image via Magiskmanager App 8.0.7.. Everything works fine. I can flash the patched boot image via fastboot, twrp or sp flash tool. But when i open Magisk after booting the patched image, there is no option to install Magisk or root the Phone. Only to patch the boot image. Even when i boot the patched image directly with fastboot.
Maybe somone here can help me.
Best regards, Jules.
Edit: I Also treid to install Liniage OS 17 and 18. Via fastboot, twrp and sp flash tool, but also get a bootloop.
Hi
I'm sorry, I cant't answer your question, but I have one to you: I'm trying to install LineageOS on a bv5500pro too (by the guide from here), but I'm stuck at the TWRP installation. Can you tell me how you managed to do it and do you have perhaps a link to the TWRP you used?
I did unlock the bootloader by toggling OEM Unlock in developer settings, then via fastboot: fastboot flashing unlock. Then reboot.
Then I pushed TWRP 3.2 (from this source here, from the tutorial here) by fastboot flash recovery recovery.img. When I tried then to boot directly after flashing into twrp recovery by holding vol up + power, then selecting recovery mode and confirming with vol down, it tries to boot normally instead of recovery. I think, my TWRP flashing didn't work properly. Booting into TWRP by fastboot boot recovery.img doesn't work either, there it reboots and tries to boot normally too. fastboot tells me that it loses connection (normal, since my phone reboots, I think?):
Code:
fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 1.017s]
booting...
FAILED (status read failed (No such device))
finished. total time: 23.457s
What I have to confess, is that I did wipe the system, data and cache partitions using fastboot erase <partition>, perhaps someone knows if I have problems with twrp because of that? (I know that I shouldn't have done this, sometimes curiosity is equal to stupidity...) I did this because I tried to install LineageOS without twrp. Was a bad idea, I know now...
I am on a HP proBook using Debian 10 with adb and fastboot installed. Not sure if MK65xx drivers are installed. Might this pose problems?
Thanks in advance to all here!
EDIT: Sorry, I forgot to mention a lot of things. I corrected some of them here. A more complete overview in another post can be found here.
hi, at least im not alone having trouble with the BV5500pro. I don't remember where i got the twrp exactly, but i uploaded it for you.
File-Upload.net - recovery-verified.rar
Datei: recovery-verified.rar. Die Datei wurde von einem User hochgeladen. Laden Sie auch kostenlos Dateien hoch mit File Upload.
www.file-upload.net
At first i flashed TWRP with fastboot. But then everytime i could boot in twrp only one time. After the next reboot the stock Recovery was reinstalled. So i used the Stock images
Blackview BV5500 Pro factory firmware (flash file)
This Blackview BV5500 Pro firmware flash file (stock ROM) can help you easily un-brick or restore your device to its default or factory state. If you have previously rooted or modified the system (or other) partition of the phone in any way, flashing this stock ROM will overwrite all existing...
www.leakite.com
and replaced the recovery-verified.img with the TWRB image and fashed everyting wit sp flashtool on my phone. After that TWRP was permanent.
Ok, great, thanks for your fast reply. I'll try it again with your image.
GiRonimoon said:
At first i flashed TWRP with fastboot. But then everytime i could boot in twrp only one time. After the next reboot the stock Recovery was reinstalled.
Click to expand...
Click to collapse
How did you boot into TWRP then? By Volume up + power, then selecting recovery mode and confirm with vol down? or by terminal/fastboot command?
edit: small grammar
By Volume up + power.
Thank you
Ok, quick update: Flashing worked, but reboot not, I think. I managed to boot into TWRP, but I managed too once with my image before (I forgot to mention), where the screen was then not responding. A complete description of my case can be found here on xda. Sorry for the late corrections that are made in this post, I'll correct them above...
Now after the flash with the image from GiRonimoon above, I can boot into TWRP and the TWRP start screen shows: TWRP Recovery Project 3.3.0-by *nemo-nemo* (4pda.ru), and when I'm in, the screen is not responding. It was like this with my first TWRP image too, so perhaps the flashing didn't work and I have still my old image which is not working?
GiRonimoon said:
By Volume up + power.
Click to expand...
Click to collapse
Ok. But when I boot into recovery, the exact things I do is:
1. phone powered off
2. Hold volume up + power until boot mode selection screen appears
3. Select recovery mode with volume up, then confirm with volume down
4. the phone reboots (screen goes black for about 1 sec), Blackview logo is shown (as well as a 'orange state' warning message), 5 sec delay because of orange state.
5. screen goes black for 1/2 sec
6. TWRP is open, screen not responding, asking for password for decryption
Exactly the same for booting into recovery via terminal/fastboot (just insert fastboot command at 1.). So since the phone reboots once in between, is it possible that my new TWRP is erased every time? Do your BV5500pro behaves also like this (except the orange state, I think)?
Thanks in advance
How long you are waiting? In my case TWRP needs a long time to start. At first i was thinking that it freezes at startup.
I just foubnd out that every boot into twrp causes a boot loop.. Even when i just boot twrp to see the versionnumber, and then reboot normaly.
GiRonimoon said:
How long you are waiting? In my case TWRP needs a long time to start. At first i was thinking that it freezes at startup.
I just foubnd out that every boot into twrp causes a boot loop.. Even when i just boot twrp to see the versionnumber, and then reboot normaly.
Click to expand...
Click to collapse
When I manage to boot into TWRP it's rather fast - I have to wait around 7 sec or so, maybe 10. But I only manage sometimes. Normally I have to do fastboot boot recovery.img, and after that do the normal steps to boot into recovery. If I try to boot into recovery, it just tries to boot normally (which ends in a bootloop)...
But I think I'll try to flash a stock rom and retry from there, as it was suggested here.