So I know there's a lot of posts here with a similar situation and I tried to find a solution but I'm at my wit's end.
I recently tried updating my KF using the Cyanogenmod built in nightly update system. When it rebooted after downloading I got stuck in this boot loop for TWRP. It shows the "teamwin" logo, then the screen flashes and it's back to the logo again.
I can connect via adb but unfortunately my device is unauthorized. Obviously, since I'm stuck at this logo I can't authorize it manually on the KF.
I definitely have the latest version of adb as I just downloaded/installed it from the SDK manager seconds ago. I installed all the drivers and added the blurps of code to the Google USB driver and the adb_usb.ini. I tried deleting the adbkey files and restarting adb. I tried different USB cables and different USB ports on my computer. All this to no avail.
Anyone have any ideas besides buying a fastboot cable? That's the only thing left that I can think of to do.
bump
Guess I'll try getting that fastboot cable...
I had the same problem. The only solution that worked for me was buying a fastboot cable and then re-flashing the TWRP recovery img.
tawpa said:
I had the same problem. The only solution that worked for me was buying a fastboot cable and then re-flashing the TWRP recovery img.
Click to expand...
Click to collapse
Yep, I just received mine and did the same.
Dear Members,
I would like to ask some help.
I tried to build Ubuntu Touch (Phablet) onto my phone (LG p880). Seemingly the kernel is working, because the recovery image operates perfectly. But the boot image is not working. The booting process cannot step over the bootloader. Only the LG logo is seeming.
Have somebody ever met similar issue? What can the problem be? In my suspect, the ramdisk can be wrong, cannot it? How can the 2nd stage be debugged? (e.g. via USB)
Thank you for your help in advance.
Regards,
Csaba
secure boot is the problem
qualcomm chipset and lg lock the boot loader so no fastboot so no flash. "bump" boot.img and that should go away. suprised it didnt soft brick your device
Please download link file rom Ubuntu for p880
hello i have i mi note pro that has been bricked for a while and im trying to fix it.
i think it has 2 problems that has to be solved but im not sure.
first thing that i tried to fix was that the device only started up when i was charging it from an adapter. when i connected it to the computer it just flashed the red dot with second in interval. i searched for a solution in forums and found out that similar problems had been solved by pulling the battery out and putting it in again after some minutes, but it did not fix the problem. and thats when i get to the second problem.
2nd prob is that, when i get my device started ( by having it connected to the adapter) it only flashes the mi logo. And i realized that i could start fastboot, and then quickly while fastboot is on connect to my computer. when i write sudo command "fastboot devices" i can see that it recognizes the device. (fastboot is unlocked also if that is to any importance.)
When i last used the phone i had a twrp and an unofficial ROM installed and it got bricked because i tried to install a new twrp or ROM, i cant remember.
I have a feeling that i tried install either a twrp or rom that wasnt compatible with what i had. i had marshmallow 6.x on the device and i think i tried installing something older or probably newer like nougat 7.x
i was wondering if i could some how install a new clean TWRP and ROM on my device trough fastboot so i can continue using this device again.
i would be grateful for any response or help
Hi all,
I just got an X4 XT1900-01 from Google Fi, and was really looking forward to putting LineageOS on it. I followed the instructions to unlock the bootloader, then tried the instructions to install TWRP. Unfortunately, after I got fastboot unlocked, any boot or flash operation I try against it just hangs forever. I have let it run for up to an hour, and it appears to do nothing (rebooting works as though nothing happened).
I have the latest Android platform tools as of this post (28.0.1-4986621), and the bootloader shows
Code:
flashing_unlocked
on the screen. Fastboot responds properly to reboot commands, so I don't have much to go on here. I'm running Arch Linux at the moment, and have O$X and Window$ available if absolutely necessary.
Would anyone be so kind as to steer me in the right direction to get fastboot to actually move bits?
Hello, I have a Razer Phone 2, yesterday I uploaded a ROM on it, everything seems to have installed after whether the phone displayed a notification "Your device is corrupt. It can’t be trusted and may not work properly." then the notification disappeared and the phone will appear on the Razer powered android logo . after pressing vol - and the phone switch, the bootloader starts but I can not do anything in it, neither recovery mode nor wipe userdata, after clicking them, it returns to the razer logo and stands I looked and tried everything but I can't do anything about it, is this the end of the phone or is there any chance to get it back?
Thank you for your help and sorry for the spelling (translator)
lukkiii96 said:
Hello, I have a Razer Phone 2, yesterday I uploaded a ROM on it, everything seems to have installed after whether the phone displayed a notification "Your device is corrupt. It can’t be trusted and may not work properly." then the notification disappeared and the phone will appear on the Razer powered android logo . after pressing vol - and the phone switch, the bootloader starts but I can not do anything in it, neither recovery mode nor wipe userdata, after clicking them, it returns to the razer logo and stands I looked and tried everything but I can't do anything about it, is this the end of the phone or is there any chance to get it back?
Thank you for your help and sorry for the spelling (translator)
Click to expand...
Click to collapse
Flash stock following instructions on Razer Developer portal
jonchance_84 said:
Flash stock following instructions on Razer Developer portal
Click to expand...
Click to collapse
He follows the instruction and when entering the commands, <waiting for device> is shown . I have installed all the drivers
lukkiii96 said:
He follows the instruction and when entering the commands, <waiting for device> is shown . I have installed all the drivers
Click to expand...
Click to collapse
Installing drivers while phone is in fastboot mode too. Do checks while booted with adb devices and then boot into fastboot then run fastboot devices. If you get a device on each one, script should work. The pc sees a different device for each mode.
jonchance_84 said:
Installing drivers while phone is in fastboot mode too. Do checks while booted with adb devices and then boot into fastboot then run fastboot devices. If you get a device on each one, script should work. The pc sees a different device for each mode.
Click to expand...
Click to collapse
I think it's a hard brick, no command works, I guess I'll give up, is there any Razer service in Europe that could repair it for a fee?
lukkiii96 said:
I think it's a hard brick, no command works, I guess I'll give up, is there any Razer service in Europe that could repair it for a fee?
Click to expand...
Click to collapse
Could be a Win10 2004 build issue. Some have had luck either using an older win7 machine or loading up a linux vm in win10. U can let it take control of usb ports. It all stems from usb drivers in windows.
Don't know about service in europe. Im in Texas.
jonchance_84 said:
Could be a Win10 2004 build issue. Some have had luck either using an older win7 machine or loading up a linux vm in win10. U can let it take control of usb ports. It all stems from usb drivers in windows.
Don't know about service in europe. Im in Texas.
Click to expand...
Click to collapse
I followed your advice and used a computer with windows 7 everything flashed everywhere ok, only now when the phone turns on the message pops up "your device i corrupt. It can't be trusted and may not work properly" if something went wrong ?:crying:
Edit:It was enough to use the command fastboot flashing unlock_critical and everything works as it should, thanks a lot for your help, best regards