Hello,
I have a Pixel 2XL that I had rooted and was working fine. I went to do an update to Android. Apparently it went through and did an update, and than somehow it became locked again, even though I had unlocked the bootloader fine. Now it is showing locked, even though I never locked it. Thoughts?
Update: I was unable to unlock it again, but it's not responding via USB despite showing up on Flashboot Devices.
Can you boot TWRP? If so put a factory ota or lineage on a thumb drive and flash it
Hello,
I have tried but the phone keeps rebooting when I try it. I've read that using non powered USB ports can cause that behavior, so I bought a powered USB 2.0 Hub and I am going to try that, even though I did the initial root using my desktop with non powered ports.
Related
Please take a look at the Software Information screen shot of my phone. I tried many methods of upgrading to MM or LP by flashing roms but almost all failed. I tried installing TWRP but on boot phone said "Fastboot mode started" on black dos-like screen. But phone was not bricked and I was able to start normally again into Android 4.4.2 by ejecting and reinserting battery. I am not even sure to which country this phone belongs, since its D855 I think its European, so I tried install those stock roms but failed, in a different way for each method.
When I try to update from LG PC Suite, it says that theres an update available for my phone but while trying to install it the software gives error saying phone cable disconnected.
Please help me guys.
try TOT method.
I did try that, didn't work. At the stage where you are supposed to eject USB cable and put it back in for the flashing to start, when I reinsert the cable nothing happens, a fail message shows up.
Try different USB cables, ports, maybe even PC, have you manually installed all PC drivers? What about resetting the phone? Is the phone rooted?
I have tried two different computers, and two different USB cables, however non of the cable were original from LG, one was from Nokia and other from Asus. Drivers are working fine as far as I know since I can see LG Mobile modem option in Device Manager. I think while trying to install TWRP I deleted the recovery so when I try to reset phone, after restarting it goes to a dos-like mode that says "Fastboot mode started". Yes, phone is rooted.
Hello
Are you sure do you have properly installed root? try this guide
http://forum.xda-developers.com/lg-g3/general/guide-root-method-lg-devices-t3129197
Then install the TWRP official app and install recovery from the twrp app.
I had successfully rooted the device, a root checker app from store confirmed that device is rooted.
Friends, now my device is completely bricked. I had given it to a friend after I had corrupted its recovery, he tried different stuff and said that partitions are corrupt. Now he said the device is fully bricked, not even turning on. Any chances of making it functional again?
Hi all,
I'm turning to forums now because I'm desperately in need of help.
I have an Oppo Find 7a which I bought about 9 months ago. When I first got it I tried flashing Cyanogenmod to it (unsuccessfully), and then tried rooting the phone. I have since unrooted the phone, and am running Color OS v 1.2.5i and really really need to update. Problem is, I cannot seem to update the operating system. Here's what happens:
Phone fails to boot to recovery
In my attempts to install Cyanogenmod, I installed a custom recovery. However I couldn't get Cyanogenmod to flash properly, so I tried reverting to the stock recovery. Did that, which seemed to work fine. However, since rooting and unrooting my phone, I cannot boot into reocovery at all. When turning off the phone and then pressing power+volume down to try and boot in, the "OPPO" logo comes up as if trying to boot into recovery, then the phone just turns off and boots into normal OS. Have tried many things but can't seem to get into recovery at all. This means that when an OS update is detected (which it is), the phone tries to reboot into recovery to install the update and cannot. So I'm stuck on a very buggy OS and can't do anything to update. Before you suggest adb+fastboot solutions, please read below:
Phone not recognised in PC at all
When plugging the phone into a PC via usb cable literally nothing happens (aside from the phone detecting it is charging). The phone does not mount as a volume in Windows, the phone is not detected as a device in device manager, as far as the computer is concerned, the phone is not even there. I have tried having the phone plugged in and installing all the proper adb drivers, but this has still yielded no results. And yes USB debugging is definitely enabled on the phone. I don't know why, but for some reason I literally cannot plug my phone into a PC anymore which limits me a LOT in terms of fixing the problem above.
Basically I really need to update the OS on this phone and am compeltely stuck: nothing seems to work. Can anyone help me out here. What do I need to do?? Any help is greatly appreciated.
seem adb device in windows device manager when the phone plug USB at bootloader?
if yes, you can use adb+fastboot solution
Hi all, learning fast, not there yet, so forgive me if I ask something less than brilliant here
I can't connect my Tab S 8.4 wifi to any pc anymore (tried 4 different PCs and 4 different cables) after upgrading bootloader with Odin last year.
I keep getting "device descriptor failed" in Device Manager (both win7 and win10).
My son did drop and break the usb/power port which I replaced myself. Could be a hardware error, but everything worked before and after my repair, just not after bootloader upgrade. Forgive me, I don't know which bootloader is currently installed, in any case one which works with android 5.1 and not with 7.1, which I unsuccessfully tried to flash.
COderbear was so kind as to direct me towards the bootloader, which I thought TWRP was.
Since I cannot connect to a PC, I cannot update the bootloader....catch 22...
Thx for ur input.
Ps Hardware failure is a possibility, but not conclusive guys. Tablet is working fine.
In what way have you been flashing stuff have you been doing anything on trwp or oden......
stinka318 said:
In what way have you been flashing stuff have you been doing anything on trwp or oden......
Click to expand...
Click to collapse
I used ODIN to update bootloader 1-2 years ago to flash an original Samsung ROM which was already rooted. After the bootloader flash I cannot connect to a PC anymore.
I n the mean time I have learned about TWRP and used it to flash a custom ROM, all via SD card, as I cannot connect to a PC.
The only one which did not get me stuck at the black Galaxy TAB S screen is the cm12.1 custom ROM with android 5.1.
All others (see above) with android 7.1 have gotten stuck.
I thought TWRP was the bootloader, but it isn't, kindly pointed out by COderbear in another thread. :good:
As I understand it, the only way to update the bootloader to a current version to successfully upgrade to a custom 7.1 ROM.
Since I cannot connect to any PC => "device descriptor failed", I cannot update the bootloader with ODIN.
So I cannot upgrade to an android version above 5.1. That's the problem.
Mace73 said:
I used ODIN to update bootloader 1-2 years ago to flash an original Samsung ROM which was already rooted. After the bootloader flash I cannot connect to a PC anymore.
I n the mean time I have learned about TWRP and used it to flash a custom ROM, all via SD card, as I cannot connect to a PC.
The only one which did not get me stuck at the black Galaxy TAB S screen is the cm12.1 custom ROM with android 5.1.
All others (see above) with android 7.1 have gotten stuck.
I thought TWRP was the bootloader, but it isn't, kindly pointed out by COderbear in another thread. :good:
As I understand it, the only way to update the bootloader to a current version to successfully upgrade to a custom 7.1 ROM.
Since I cannot connect to any PC => "device descriptor failed", I cannot update the bootloader with ODIN.
So I cannot upgrade to an android version above 5.1. That's the problem.
Click to expand...
Click to collapse
I have had a lot of Samsung device and this is a first i have heard of this i have flashed the wrong stuff and soft bricked things but never heard of having issues with the bootloader up date........
stinka318 said:
I have had a lot of Samsung device and this is a first i have heard of this i have flashed the wrong stuff and soft bricked things but never heard of having issues with the bootloader up date........
Click to expand...
Click to collapse
Yeah, but ur not me
I have a sneaky suspicion that it's the usb port which I've swapped.
I've found two threads somewhere on Google relating to using another cable, must be a hardware failure or substandard part.
Can't explain it otherwise.
There is no way to update a bootloader via SD, right?
Logical, the bootloader's the first thing it reads to start up.....
Anyway, thought it was worth a try to post a thread, u never know what crazy solutions come to pass in android world.... (iOS too for that matter)
Mace73 said:
I have a sneaky suspicion that it's the usb port which I've swapped.
I've found two threads somewhere on Google relating to using another cable, must be a hardware failure or substandard part.
Can't explain it otherwise.
There is no way to update a bootloader via SD, right?
Logical, the bootloader's the first thing it reads to start up.....
Anyway, thought it was worth a try to post a thread, u never know what crazy solutions come to pass in android world.... (iOS too for that matter)
Click to expand...
Click to collapse
Bootloader can only be updated with oden only any thing else won't work.......
It is not issue of fleshed software. I have this issue during last 2 months. Official service center didn't find any clue during 2 weeks so i get back my Tab. All story starts, i suspect, after 1 month using magnet cable. Then suddenly charging current start to be lower then usual (Galaxy Charging Current App) and i decide to check different chargers and PC. I found that tablet cannot connect to any PC - "device descriptor failed". During playing with "USB debug" on/off and USB modes i connected tablet to PC once. But during Odin flash it stuck in "Getting PIT file..." and i still didn't update anything.
I suspect that it is some hardware issue in part that responsible for USB communication.
Issue solved. Tried on different ports with combination USB-hub. On some ports it completely invisible, on some "usb device not recognized". But after two weeks once i get connected and Tab was detected - then immediately flash stock CQB1 with TWRP 3.1.0. Now it still detected by PC.
I suspect micro-crack in motherboard or some HW issue on some SW combination (modem SW).
Hello, I tried to install the rom Google PixelROM v7.3 for LG Nexus 5X[7.1.2] by argraurand, and now my phone will no longer boot into TWRP or the OS. I am running TWR 3.0.2-0, I didn't see anything about having to have that updated to the most recent for using this rom. I was able to install the rom fine from this TWRP, but now my phone seems to be bricked like. Sitting with the phone in the bootloader, I can't get windows/fastboot/adb to recognize my device connected to my computer, the google drivers are definitely installed as earlier it was being recognized fine by windows/fastboot/adb. My bootloader changed with this ROM being installed, but now the TWRP won't load either, and neither will the Android OS (it looks like it's about to load then just defaults into the TWRP loading screen, which just sits forever). I can get also into the download mode "firmware update" tool of the phone by pressing the volume up when booting, but even in this mode the phone isn't being recognized in windows anymore. Do I have any chance of restoring my phone, or should I start shopping? I've fixed other phones many times, but without being able to load/restore via fastboot I feel totally lost.
myselfalex said:
Hello, I tried to install the rom Google PixelROM v7.3 for LG Nexus 5X[7.1.2] by argraurand, and now my phone will no longer boot into TWRP or the OS. I am running TWR 3.0.2-0, I didn't see anything about having to have that updated to the most recent for using this rom. I was able to install the rom fine from this TWRP, but now my phone seems to be bricked like. Sitting with the phone in the bootloader, I can't get windows/fastboot/adb to recognize my device connected to my computer, the google drivers are definitely installed as earlier it was being recognized fine by windows/fastboot/adb. My bootloader changed with this ROM being installed, but now the TWRP won't load either, and neither will the Android OS (it looks like it's about to load then just defaults into the TWRP loading screen, which just sits forever). I can get also into the download mode "firmware update" tool of the phone by pressing the volume up when booting, but even in this mode the phone isn't being recognized in windows anymore. Do I have any chance of restoring my phone, or should I start shopping? I've fixed other phones many times, but without being able to load/restore via fastboot I feel totally lost.
Click to expand...
Click to collapse
Try a different USB port. Maybe even a different pc. Fastboot tools was just updated. Make sure you have the latest one.
Maybe you can get a fastboot connection in Linux. Try this:
https://forum.xda-developers.com/showthread.php?t=3526755
Sent from my Nexus 5X using Tapatalk
Thank you both, I tried both another computer, and running this linux version with the fastboot built in, nada! Guess I'm shopping for a new phone. Pixel here I come. Thanks for the help agian.
hey, I've rooted my device on android 11 and unrooted it again, but for some stupid reason kept the bootloader unlocked.
the new Android 12 came out and i installed it, but now i wanted to lock the bootloader and I've noticed a few things:
1- can't access the bootloader, tried everything, the - and + vol combo with the USB cable hooked to the pc.
2- can't get Odin to recognize my phone, I have the latest Samsung drivers, still nothing.
help me plz? I only need my old phone that used to run bank and Samsung apps back.
help? i'm a human bean.