Hi everyone
EDIT: Well, I managed to install Cardinal AOSP ROM. However I am having the same issue I was having with every other custom ROM: USB has gotten very flaky. I can connect USB with debug modus on. ADB will list the device, but the moment I switch to MTP, the device vanishes from Windows.
I tried the P2 root tool but it too shows the device as not connected the moment I click on "Root".
I have tried removing drivers and using Google drivers instead but it keeps happening...
Previous Text:
I'm having trouble with my Lenovo P2. I was trying to flash a custom rom, Viper in this case, but it keeps crashing and rebooting. The problem is I can't get to TWRP. I can get to the boot menu but there is no option to go to recovery. And it doesn't seem to be loading USB either as adb doesn't find the device.
All I can do is display barcodes, start or power off.
Any ideas?
Regards,
Marco
Holding Volume Up + Volume Down + Power did it.
However I still have no USB in the boot menu.
So flashing a new recovery with fastboot is not possible at the moment. Does anybody have a guide on how to flash the boot environment?
Regards,
Marco
Related
Phone with official rom , never isntalled CWM or any unofficial stuff. It boots ok to standard mode but not any other mode. I have tried in two different pcs with Windows XP and Windows 8. Phone doesn't even seem to try to boot in those modes, is not like the PC isn't detecting it.
I'm totally lost on how to recover the flashmode functionality to be able to unlck bootloader and install CM, any help will be welcome.
madmalkav said:
Phone with official rom , never isntalled CWM or any unofficial stuff. It boots ok to standard mode but not any other mode. I have tried in two different pcs with Windows XP and Windows 8. Phone doesn't even seem to try to boot in those modes, is not like the PC isn't detecting it.
I'm totally lost on how to recover the flashmode functionality to be able to unlck bootloader and install CM, any help will be welcome.
Click to expand...
Click to collapse
You must be doing something wrong.
Flashmode - turn the phone off, connect USB cable to PC, hold down Back button, connect USB cable to the phone. Green LED should light up, then phone is in flashmode.
Fastboot mode - turn the phone off, connect USB cable to PC, hold down Menu/Option button, connect USB cable to the phone. Blue LED should light up, then phone is in fastboot mode.
Nah, it didn't worked. I got it to still a recovery with X-parts app. Booted to the recovery, wiped everything, did a factory restore, since that moment it won't boot at all, Sony logo and it won't power off without taking off the battery. Of course, still won't enter flashmode or flashboot.
madmalkav said:
Nah, it didn't worked. I got it to still a recovery with X-parts app. Booted to the recovery, wiped everything, did a factory restore, since that moment it won't boot at all, Sony logo and it won't power off without taking off the battery. Of course, still won't enter flashmode or flashboot.
Click to expand...
Click to collapse
Did you install the drivers for it? If you want to use either flashtool or fastboot you need to install these programs along with the drivers. Also, ignore the prompt by Sony PC Companion when prompted. If you can boot into ROM, check that USB debugging is enabled.
僕のLT18iから送られてきた
popthosegaskets said:
Did you install the drivers for it? If you want to use either flashtool or fastboot you need to install these programs along with the drivers. Also, ignore the prompt by Sony PC Companion when prompted. If you can boot into ROM, check that USB debugging is enabled.
僕のLT18iから送られてきた
Click to expand...
Click to collapse
Drivers installed, USB debugging enabled, tried on two diferent computers.
I have some experience not only in flashing roms but also in rom cooking, kernel compilation, etc... and after all day I couldn't get it to go to flashmode. My girlfriend -she is the owner of the phone- remembered me we already have problems being unabled to access flasmode when she bought the phone and wanted to update it with sony software, so I finally took it to the shop so they can send it to repair service.
Thanks guys for your prompt replies.
I'm working with a friend's LG K10. OEM unlock isn't turned on in settings, neither is USB debug, as far as I can tell. The phone shuts down before booting fully, so there's no chance I can get into settings to change those. Everything on the phone is stock - recovery, bootloader, Android version, etc.
I can get it into fastboot mode and download mode. In fastboot, it talks to my computer, but refuses to run any command I send it. I can't get it to connect to my computer in download mode. This might be a driver issue on my computer - I'm still working on fixing this.
We're not concerned with saving his data (although it would be nice, if possible). We care a lot more about getting the phone functional again.
What are the options from here? I haven't been able to find any root exploits for this phone that work without at least having adb. I'm happy to root the phone if that's the only way to get it working again.
Thanks in advance.
yes, i do this:
- phone without batery
- press up button ( all moment)
- connect usb cable
- put the battery
-wait
- and this all, firmware update mode you need, "Lg UP "
I've managed to get myself an LG K9 LM-X210YMW (body has CV1 0415 on it), but rooting this device is turning out to be VERY hard. Has anyone else had success? Its running Android 7.1.2 with Kernel 3.10.49+
I've got ole developer options set:
Enable OEM lock is ON
USB debugging is ON
Automatic updates are OFF
It's easy enough to get adb to recognize it:
Code:
evryd4y$ ./adb devices
List of devices attached
LMX210cXXXXXXX device
But rebooting with adb reboot bootloader just reboots it to lock screen.
Methods tried include:
connect then reboot with adb reboot bootloader - this just reboots to lock screen
Power on holding volume DOWN button until LG logo appears - this boots into safe mode
Power on holding volume down and power button - this reboots to safe mode
King o root (YES I know but desperate times call for depserate measures) give error 0x1c8bb4
Tried platform tools (Adb, fastboot) on Linux, Windows, Mac... same results... nothing
BUT I can get it into firmware mode by powering on and holding volume UP. This mode then hangs until I rip the battery out and throw it into space.
Has LG managed to make an un-rootable phone? Are you having the same problems?
I literally have the same problem...
evryd4y said:
Has LG managed to make an un-rootable phone? Are you having the same problems?
Click to expand...
Click to collapse
Same problem here with an LM-X210EM, have you had any luck since then?
Only thing I'd like to add is if I "adb reboot recovery" then it reboots to a sick android screen.
[SOLVED see post below]
Hi all,
Just bricked my Phone and can't access MSM. Hope you can help me. I will try to be very clear on the steps I took to get to this point.
Device: EU OnePlus 9 Pro
What is was trying to do: Go from rooted C.47 to Pixel Entended ROM
What I did:
Code:
Unrooted using Magisk uninstall option
Updated to c.48 through OTA
Go to lineageOS page on how to ensure all firmware partitions are consistent
very stupidly did not flash dtbo and vendor boot partition
did adb reboot fastboot in stead of abd reboot bootloader
Download the "lineage-19.1-20220701-recovery-lemonadep.img" and tried to temporaryly flash it by
fastboot flash boot <recovery_filename>.img
This resulted in the device getting stuck on the 1+ boot logo.
I can still force turn it off by holding Volume Up + Power.
When I try to access EDL by turned off and Vol UP + Vol Down + Plug and release, My PC makes a connection sound and the screen stay black for a while. After +- 10 seconds, the PC makes a disconnection sound and the phone boots up and gets stuck again on the 1+ bootup icon.
Also my phone won't stay turned off when plugged in the charger or pc
Yes, but what is it presenting as (i.e. EDL, fastboot, ADB, UMS...) when it connects?
If this is Windows, UsbLog.exe is handy to identify things popping up (as long as they have drivers installed).
For a list of devices that have ever tried to connect, try "enumusb.exe /l".
Both available here: https://www.temblast.com/windows.htm
Renate said:
Yes, but what is it presenting as (i.e. EDL, fastboot, ADB, UMS...) when it connects?
If this is Windows, UsbLog.exe is handy to identify things popping up (as long as they have drivers installed).
For a list of devices that have ever tried to connect, try "enumusb.exe /l".
Both available here: https://www.temblast.com/windows.htm
Click to expand...
Click to collapse
I will try this
I found the issue:
> EDL exits after 10 seconds if it is not captured by the MSM tool.
> The MSM tool only monitored 4 of my 10 USB ports
> So it was not captured because I was plugged in to an unmonitored USB port and rebooted after 10 seconds
> I have successfully used the MSM tool now
Oh! A bit off-topic, but I have never understood why EDL is commonly used over a "serial" port.
The interface that EDL presents is a generic USB bulk interface with two endpoints. You can use it just like that.
But no. They have to use a Qualcomm driver that makes it look like a "serial" port and then you can connect to that.
Me? I use a generic "WinUSB" Zadig driver. I have an EDL client that just connects to that fine.
So does the Python client implementation.
Also, I've never run into that 10 second timeout.
TraktorHenk said:
[SOLVED see post below]
Hi all,
Just bricked my Phone and can't access MSM. Hope you can help me. I will try to be very clear on the steps I took to get to this point.
Device: EU OnePlus 9 Pro
What is was trying to do: Go from rooted C.47 to Pixel Entended ROM
What I did:
Code:
Unrooted using Magisk uninstall option
Updated to c.48 through OTA
Go to lineageOS page on how to ensure all firmware partitions are consistent
very stupidly did not flash dtbo and vendor boot partition
did adb reboot fastboot in stead of abd reboot bootloader
Download the "lineage-19.1-20220701-recovery-lemonadep.img" and tried to temporaryly flash it by
fastboot flash boot <recovery_filename>.img
This resulted in the device getting stuck on the 1+ boot logo.
I can still force turn it off by holding Volume Up + Power.
When I try to access EDL by turned off and Vol UP + Vol Down + Plug and release, My PC makes a connection sound and the screen stay black for a while. After +- 10 seconds, the PC makes a disconnection sound and the phone boots up and gets stuck again on the 1+ bootup icon.
Also my phone won't stay turned off when plugged in the charger or pc
Click to expand...
Click to collapse
Your phone needs to be in OFF state mode when you're using EDL.
So, very simple:
Enter bootloader mode by holding both volume buttons with the power button together till your phone restarts and enters the bootloader.
From the bootloader screen you can use the volume buttons to navigate through the choices and you can select "Switch off".
When you complete this, you need to hold both volume buttons, and while holding them connect the cable (PC).
If you don't have or you don't have the correct Qualcomm EDL drivers installed, your phone will reboot or start to boot, it won't stay in EDL mode for longer than 10 seconds.
I also got the correct drivers for you, but you need to install the drivers manually while your device is in "EDL" mode, so, you need to be a bit "fast".
I have even a video for you, but need to upload it to YouTube so you can watch it.
I'll share you here the drivers just in case if you're familiar with a manual installation of the drivers.
ekin_strops said:
Your phone needs to be in OFF state mode when you're using EDL.
So, very simple:
Enter bootloader mode by holding both volume buttons with the power button together till your phone restarts and enters the bootloader.
From the bootloader screen you can use the volume buttons to navigate through the choices and you can select "Switch off".
When you complete this, you need to hold both volume buttons, and while holding them connect the cable (PC).
If you don't have or you don't have the correct Qualcomm EDL drivers installed, your phone will reboot or start to boot, it won't stay in EDL mode for longer than 10 seconds.
I also got the correct drivers for you, but you need to install the drivers manually while your device is in "EDL" mode, so, you need to be a bit "fast".
I have even a video for you, but need to upload it to YouTube so you can watch it.
I'll share you here the drivers just in case if you're familiar with a manual installation of the drivers.
Click to expand...
Click to collapse
Thanks for the help. The problem ended up to be a bit different than this for me, but this is a good post for anyone to find in the future!
So, I flashed Derpfest A12 ROM, It boots fine but gets stuck on "getting your Android 12 Ready" screen with the animation. I can access wifi and visiblity options but not settings. I flashed TWRP from the official website to install the recovery. But now when I reboot and press Volume Down, TWRP is stuck on boot animation. So I thought just reset using fastboot and start again and pressed volume up and power button but it does NOT work. I tried the volume buttons again in the rom [i can change volume in the starting screen] and they are working. I can press volume down and power button to reboot into recovery and it works fine but gets stuck. So, I just want to have access to adb or fastboot to reset this phone but neither seems possible. I Cant enable advanced reboot in the starting screen. Fastboot doesnt work. ADB not recognizing as it is a new rom and havent enabled it [i enabled in the previous rom]. Thanks for you Help in Advance!
P.S. I have tinkered POCO F1 fairly so I am not totally new to this scene!
EDIT: Thanks for all the replies! But I solved the problem, Idk how but i got access to fastboot mode after some tries and reflashed everything and now it works, also I use linux and the adb drivers and fastboot were in repos so it was easy.
hello,
I am a novice and use a translation tool to write to you (sorry if there are errors...).
Ok I already installed roms (but a long time ago on a OnePlus One...
I have an OP5T, I want to install lineage Os 19.1 on it.
I followed the tutorial on the lineage wiki.
I installed ADB and fastboot well, as well as universal adb driver.
I'm on windows 11, it works.
I enabled debug mode
The adb reboot bootloader command works, so the tel is well seen by the pc and the tel restarts in fastboot mode.
Then nothing, no command (oem unlock) works, the computer does not seem to see such after restarting in fastboot mode.
I read some topic on the net that say that the phone must be in "battery charging" mode and not "file transfer". Me to be visible by adb I have to put it in file transfer mode, otherwise it is not seen.
If I put in recharge mode, same thing to do.
Do you have a tip or should I give up?
ezivoco_163 said:
The adb reboot bootloader command works, so the tel is well seen by the pc and the tel restarts in fastboot mode.
Then nothing, no command (oem unlock) works, the computer does not seem to see such after restarting in fastboot mode.
I read some topic on the net that say that the phone must be in "battery charging" mode and not "file transfer". Me to be visible by adb I have to put it in file transfer mode, otherwise it is not seen.
If I put in recharge mode, same thing to do.
Do you have a tip or should I give up?
Click to expand...
Click to collapse
You need to install not just the adb drivers, but the fastboot ones as well, see this guide for example. This driver is the one needed for fastboot.
My devices have always been in file transfer mode btw, I've never heard of it needing to be in charging mode only.
No, you don't have to be in "charging only" vs "data transfer".
Still, those of us who distain to be plebian keep our devices in "charging only" (with ADB on) as MTP is beneath our contempt.
(Actually, the problem is that the USB VID/PID sometimes changes with each mode and that you may not have a driver loaded for ADB only.)
Nimueh said:
You need to install not just the adb drivers, but the fastboot ones as well, see this guide for example. This driver is the one needed for fastboot.
My devices have always been in file transfer mode btw, I've never heard of it needing to be in charging mode only.
Click to expand...
Click to collapse
Renate said:
No, you don't have to be in "charging only" vs "data transfer".
Still, those of us who distain to be plebian keep our devices in "charging only" (with ADB on) as MTP is beneath our contempt.
(Actually, the problem is that the USB VID/PID sometimes changes with each mode and that you may not have a driver loaded for ADB only.)
Click to expand...
Click to collapse
ok thanks, i a going to try this