Cannot connect to adb Lineage OS 16 - LineageOS Questions & Answers

Hey guys,
So this weekend I decided to give lineage OS 16 a try on my Xiaomi 5, the process went smoothly I think, but the battery life is really bad, so I wish to try other ROM.
Now the thing is, I cannot connect to my computer (And I could with the previous MIUI), and if I run adb devices or fastboot devices (When on fastboot) nothing shows up. I have android debug enabled.
Any ideas on what this could be?

djramrques said:
Hey guys,
So this weekend I decided to give lineage OS 16 a try on my Xiaomi 5, the process went smoothly I think, but the battery life is really bad, so I wish to try other ROM.
Now the thing is, I cannot connect to my computer (And I could with the previous MIUI), and if I run adb devices or fastboot devices (When on fastboot) nothing shows up. I have android debug enabled.
Any ideas on what this could be?
Click to expand...
Click to collapse
You have twrp installed. So you don't need adb for next ROM. Try without GApps to save battery.

kurtn said:
You have twrp installed. So you don't need adb for next ROM. Try without GApps to save battery.
Click to expand...
Click to collapse
Hey. Thanks for the answer, I am still a bit noob on this so I am not sure I completely understand. Yes indeed I have used twrp , but I used the command fastboot boot twrp.img . Before that, I also did fastboot flash recovery <recovery_filename>.img. Does this mean that I have twrp installed or that I booted directly from it from my computer? I ask this because, when I go to recovery (Hold Power + Volume Up), I dont go to TRWP menu, but rather to the Mi-Recovery 3 menu.
Thank you!

Deleted

kurtn said:
You have twrp installed. So you don't need adb for next ROM. Try without GApps to save battery.
Click to expand...
Click to collapse
I am note sure what happened but did you mean to reply twice?

djramrques said:
I am note sure what happened but did you mean to reply twice?
Click to expand...
Click to collapse
Oops. Bad data connection.
---------- Post added at 04:14 PM ---------- Previous post was at 04:11 PM ----------
djramrques said:
Hey. Thanks for the answer, I am still a bit noob on this so I am not sure I completely understand. Yes indeed I have used twrp , but I used the command fastboot boot twrp.img . Before that, I also did fastboot flash recovery <recovery_filename>.img. Does this mean that I have twrp installed or that I booted directly from it from my computer? I ask this because, when I go to recovery (Hold Power + Volume Up), I dont go to TRWP menu, but rather to the Mi-Recovery 3 menu.
Thank you!
Click to expand...
Click to collapse
Oh, I have no experience with a/b devices like yours

kurtn said:
Oops. Bad data connection.
---------- Post added at 04:14 PM ---------- Previous post was at 04:11 PM ----------
Oh, I have no experience with a/b devices like yours
Click to expand...
Click to collapse
So turns out, if I use my old cable (Which is a bit ruined at on end), it works. But if I use a new cable, that I just bought, it does not work. That is super weird right?
Thank you anyway. I am flashing Pixel Experience at the moment. ANd now I am TWRP installed.

Related

[Q] Unrooting: now i can not log into the system!?

Fixed! thanks guys!
Drop the toolkit and do it manually. Boot into bootloader and lock it with fastboot.
The android with the red triangle is the stock recovery.
stop being lazy with the toolkit...
http://forum.xda-developers.com/showthread.php?t=1626895
But Debugging mode is still required, when installing Naked driver.
I already spend too much time on this ****.. maybe I should just throw my phone in trash?
hxgni said:
But Debugging mode is still required, when installing Naked driver.
I already spend too much time on this ****.. maybe I should just throw my phone in trash?
Click to expand...
Click to collapse
Debugging mode has nothing to do with fast boot or custom recovery. It only applies to a booted OS.
So, no its not required.
Do some reading and comprehend what you are doing to your device.
Sent from my Galaxy Nexus
Pirateghost said:
Debugging mode has nothing to do with fast boot or custom recovery. It only applies to a booted OS.
So, no its not required.
Do some reading and comprehend what you are doing to your device.
Sent from my Galaxy Nexus
Click to expand...
Click to collapse
reading? THATS UNHEARD OF AROUND HERE! YOU SPEAK BLASPHEMY
---------- Post added at 03:31 PM ---------- Previous post was at 03:31 PM ----------
hxgni said:
But Debugging mode is still required, when installing Naked driver.
I already spend too much time on this ****.. maybe I should just throw my phone in trash?
Click to expand...
Click to collapse
way to not follow the guide btw
ok thanks guys, i finally got it fixed

[Q] Bootloop

Hey,
i just got a bootloop...
I still can access the recovery menu but Windows wont allow me to reinstall the adb drivers... so my fire phone is just known as "SD4930UR" in the device management ...
adb wont recognize it as device -.-
Anyone got an idea how to get this thing back working?
Cheers,
Xerx
//Edit: OK got it... windows just had to be restarted... -.-
Xerx3sHipe said:
Hey,
i just got a bootloop...
I still can access the recovery menu but Windows wont allow me to reinstall the adb drivers... so my fire phone is just known as "SD4930UR" in the device management ...
adb wont recognize it as device -.-
Anyone got an idea how to get this thing back working?
Cheers,
Xerx
Click to expand...
Click to collapse
Hi,
i think you are using Windows 8 or newer?
When not:
Try go to Device Manager - choose SD4930UR -> Drivers -> Driver update -> Search on Computer -> Here you choose ADB Driver
When using new windows: Try to use this http://www.makeuseof.com/tag/how-can-i-install-hardware-with-unsigned-drivers-in-windows-8/
After boot you can choose the unsigned ADB Driver -> adb prompt is working again
gz
B1ackByte said:
Try go to Device Manager - choose SD4930UR -> Drivers -> Driver update -> Search on Computer -> Here you choose ADB Driver
Click to expand...
Click to collapse
yeah... i just needed a reboot after this ...
Cheers,
Xerx
But how did you come out of the loop? Or made you a clean install?
Clean install
le-grx said:
But how did you come out of the loop? Or made you a clean install?
Click to expand...
Click to collapse
yep like B1ackByte said, i had to do a clean install.
Cheers,
Xerx
How can i flash this device? Amazon Fire Phone (SD4930UR) i am getting a boot loop and cant get into the recovery.
Please help.
hi, i sideload the new update through ADB successfully but the firephone keeps restarting
---------- Post added at 09:41 AM ---------- Previous post was at 09:39 AM ----------
damienweithers said:
How can i flash this device? Amazon Fire Phone (SD4930UR) i am getting a boot loop and cant get into the recovery.
Please help.
Click to expand...
Click to collapse
make sure its connected to PC/mac while you hold volume up and power at the same time ,then it will enter recovery
Recovering from BootLoop
le-grx said:
But how did you come out of the loop? Or made you a clean install?
Click to expand...
Click to collapse
I did a sideload of ROM available from Amazon website in .bin and the phone restored to its previous state without loosing any data.:laugh:
---------- Post added at 03:29 PM ---------- Previous post was at 03:17 PM ----------
damienweithers said:
How can i flash this device? Amazon Fire Phone (SD4930UR) i am getting a boot loop and cant get into the recovery.
Please help.
Click to expand...
Click to collapse
You can do it with side-load, get the updated version of ROM in bin form, from Amazon's website and sideload to your phone. You won't lose any data with this process.
bakhtjs said:
I did a sideload of ROM available from Amazon website in .bin and the phone restored to its previous state without loosing any data.:laugh:
---------- Post added at 03:29 PM ---------- Previous post was at 03:17 PM ----------
You can do it with side-load, get the updated version of ROM in bin form, from Amazon's website and sideload to your phone. You won't lose any data with this process.
Click to expand...
Click to collapse
In my case, doing a sideloaded update with 4.6.6 bin file didn't resolve the reboot loop. Unfortunately.
I've also read elsewhere that a battery fault can cause this issue. So that's also something else for people with this issue t consider.
AndroidWelcome said:
In my case, doing a sideloaded update with 4.6.6 bin file didn't resolve the reboot loop. Unfortunately.
I've also read elsewhere that a battery fault can cause this issue. So that's also something else for people with this issue t consider.
Click to expand...
Click to collapse
If side loading doesn't help then it's a dead battery. Replacement is pretty straightforward and the costs are around $40.
AndroidWelcome said:
In my case, doing a sideloaded update with 4.6.6 bin file didn't resolve the reboot loop. Unfortunately.
I've also read elsewhere that a battery fault can cause this issue. So that's also something else for people with this issue t consider.
Click to expand...
Click to collapse
Well i have the same case as you, sideload update with 4.6.6 from Amazon's official website but nothing changed. And i even tried and replaced my phones battery but it didn't work either. Don't know exactly what is wrong and what to do
My phone is working with the power source only as I unplug it goes in bootloop .
should I just do adb or replace my battery??
do I need to install any driver's to do sideload adb ??
B1ackByte said:
Hi,
i think you are using Windows 8 or newer?
When not:
Try go to Device Manager - choose SD4930UR -> Drivers -> Driver update -> Search on Computer -> Here you choose ADB Driver
When using new windows: Try to use this http://www.makeuseof.com/tag/how-can-i-install-hardware-with-unsigned-drivers-in-windows-8/
After boot you can choose the unsigned ADB Driver -> adb prompt is working again
gz
Click to expand...
Click to collapse
I did that but my drivers were already updated .
my fire phone is stuck in a bootloop i tried doing adb but it doesn't complete while the updates are installing it restarts itself and goes into a bootloop again .what should i do plz help .
Xerx3sHipe said:
yep like B1ackByte said, i had to do a clean install.
Cheers,
Xerx
Click to expand...
Click to collapse
hey how did you do a clean install?? i did adb sideload but before i get a message that adb is successful my phone restarts and goes to a bootloop in between when updates are being installed.
when i update my phone as "apply update with adb" its work perfectly and turned to adb sideload mode. after sending update package on my device, my device going away to verifying package, opening package, but when its turn to installing updates, my device display was turn off or it reboot automatically and showing the company logo - "amazon". please help me for this problem. My handset name is - Amazon Fire SD4930UR
Replace your battery.. It worked for me.
filxy said:
My phone is working with the power source only as I unplug it goes in bootloop .
should I just do adb or replace my battery??
do I need to install any driver's to do sideload adb ??
Click to expand...
Click to collapse
Replace your battery.. It worked for me.

[Softbrick] Every ROM stuck in Bootloop

Hello,
I really dont know what to do anymore.
No matter which ROM I flash, I always get stuck in a bootloop. I always wait 20-25 for a boot, but it doesnt pass the bootanimation.
Here is what happened:
My PC didnt recognize my phone anymore even though I didnt change any driver settings or something like that. Same with other PCs, not even showing up in device manager at all. So I thought I messed up some settings in my phone, thats why I wiped data, system, cache, internal store, then pushed a new ROM to my phone via USB OTG, but it doesnt boot at all. Phone still doesnt get recognized by any pc, not even in TWRP or bootloader.
Here are the things I tried so far:
- Ressurrection Remix (latest 3 versions) with OpenGapps
- Lineage OS with DynamicGapps
- both of them without any gapps
- OMNI Rom with DynamicGapps
I also did a factory reset before every flash. After 20 minutes of bootloop I also tried a 2nd boot for 20 minutes...nothing.
Since I cant access my phone from PC I cant flash stock ROM (or is it possible to flash it via TWRP?). I guess I just wiped something that I shouldnt have wiped. Does anyone have an idea what else I could try?
I had something similar happen to my 5x a while back. After fiddling with drivers/device manager etc, I found this on net which actually worked for me:
Solution 5 – Uninstall Android drivers if PC not recognizing phone
Sometimes you might not have the latest drivers, or your drivers might not be properly installed, so in order to fix issues with Android devices and Windows 10, it’s advised that you uninstall your Android drivers. To do so, follow these steps:
Connect your Android device to your computer and open Device Manager.
In Device Manager locate your Android device. Usually it’s located in Other Devices or in Portable devices section, but the location might be different on your computer.
Right click the device and choose Uninstall.
uninstall-driver
After the drivers have been uninstalled, disconnect your Android device.
Reconnect it again, and wait for Windows 10 to install its drivers again.
Check if your Android device is now recognized.
---------- Post added at 06:09 PM ---------- Previous post was at 06:06 PM ----------
Above post fixed my driver/PC not recognizing phone issue. As far as your bootloop issue, I'm assuming your bootloader is still unlocked, right? If so, and if above fix works where PC recognizes phone, try flashing google factory images via fastboot commands.
jrotert said:
I had something similar happen to my 5x a while back. After fiddling with drivers/device manager etc, I found this on net which actually worked for me:
Solution 5 – Uninstall Android drivers if PC not recognizing phone
Sometimes you might not have the latest drivers, or your drivers might not be properly installed, so in order to fix issues with Android devices and Windows 10, it’s advised that you uninstall your Android drivers. To do so, follow these steps:
Connect your Android device to your computer and open Device Manager.
In Device Manager locate your Android device. Usually it’s located in Other Devices or in Portable devices section, but the location might be different on your computer.
Right click the device and choose Uninstall.
uninstall-driver
After the drivers have been uninstalled, disconnect your Android device.
Reconnect it again, and wait for Windows 10 to install its drivers again.
Check if your Android device is now recognized.
---------- Post added at 06:09 PM ---------- Previous post was at 06:06 PM ----------
Above post fixed my driver/PC not recognizing phone issue. As far as your bootloop issue, I'm assuming your bootloader is still unlocked, right? If so, and if above fix works where PC recognizes phone, try flashing google factory images via fastboot commands.
Click to expand...
Click to collapse
Since it doesnt show up in device manager, I cant uninstall the driver there.
I also tried it on a new PC that did never get in touch with an android phone - nothing. Not even a sound when I plug it in. The phone is just charging, thats it.
Have you tried using a different cable?
Keksdroid said:
Hello,
I really dont know what to do anymore.
No matter which ROM I flash, I always get stuck in a bootloop. I always wait 20-25 for a boot, but it doesnt pass the bootanimation.
Here is what happened:
My PC didnt recognize my phone anymore even though I didnt change any driver settings or something like that. Same with other PCs, not even showing up in device manager at all. So I thought I messed up some settings in my phone, thats why I wiped data, system, cache, internal store, then pushed a new ROM to my phone via USB OTG, but it doesnt boot at all. Phone still doesnt get recognized by any pc, not even in TWRP or bootloader.
Here are the things I tried so far:
- Ressurrection Remix (latest 3 versions) with OpenGapps
- Lineage OS with DynamicGapps
- both of them without any gapps
- OMNI Rom with DynamicGapps
I also did a factory reset before every flash. After 20 minutes of bootloop I also tried a 2nd boot for 20 minutes...nothing.
Since I cant access my phone from PC I cant flash stock ROM (or is it possible to flash it via TWRP?). I guess I just wiped something that I shouldnt have wiped. Does anyone have an idea what else I could try?
Click to expand...
Click to collapse
try Wug's Nexus Root Toolkit he is able to flash phone in bootloop
panicbear said:
Have you tried using a different cable?
Click to expand...
Click to collapse
I dont have any other cable, but maybe I should get a new one just to test. The cable I have is just 3 months old and was high quality....
pincher65 said:
try Wug's Nexus Root Toolkit he is able to flash phone in bootloop
Click to expand...
Click to collapse
Yeah I always used that tool in the past. But since my PC doesnt recognize the phone at all, not even in fastboot mode, that doesnt help me. I really need a solution that works just with TWRP...
Edit: Just an idea from my side. Would it work if someone, who just cleaned flashed, makes an nandroid backup, which I just restore with TWRP?
what radio at you installed? 7.1.1 02.2017 for TWRP
pincher65 said:
what radio at you installed? 7.1.1 02.2017 for TWRP
Click to expand...
Click to collapse
Radio is m8994f-2.6.36.2.20 - flashed it in December.
For TWRP?? Can I flash the stock zim through TWRP?
Keksdroid said:
For TWRP?? Can I flash the stock zim through TWRP?
Click to expand...
Click to collapse
yes. also PixelROM has full img
pincher65 said:
yes. also PixelROM has full img
Click to expand...
Click to collapse
Okay I will try that. I guess I will loose TWRP when I flash it?!
Keksdroid said:
Okay I will try that. I guess I will loose TWRP when I flash it?!
Click to expand...
Click to collapse
No.
pincher65 said:
No.
Click to expand...
Click to collapse
So I tried the stock rom and pixel rom, both when I try to flash them I get the Error message "Zip file is corrupt". There is no md5sum to check if its really corrupt...
Keksdroid said:
So I tried the stock rom and pixel rom, both when I try to flash them I get the Error message "Zip file is corrupt". There is no md5sum to check if its really corrupt...
Click to expand...
Click to collapse
disable check md5sum in setting TWRP.
pincher65 said:
disable check md5sum in setting TWRP.
Click to expand...
Click to collapse
Either way I'm blind, or I dont have that setting...
Keksdroid said:
Either way I'm blind, or I dont have that setting...
Click to expand...
Click to collapse
sorry, I have inattentively read the previous post. redownload zip if doesn't help, then your recovery is damaged and it is necessary to look for a way to connect him to PC
Problem solved. Got a new USB cable today, it worked now. Flashed stock image, it finally booted.
But wow, the old cable is already broken after 3 months...well it still charges very fast, but thats it.

Please confirm this is bricked

Hi guys,
I know there are plenty of posts about bricked phones and I've read most of them. Just want to do a sanity check here. If my phone has a LOCKED bootloader and USB debugging is NOT enabled, there is nothing I can do in terms of flashing an image right? I can enter bootloader and stock recovery, but when I boot to OS it bootloops.
Just want to confirm my only option is warranty claim with Google and there's no way to enable USB debugging other than from the OS?
Thanks in advance!
piotrus22 said:
Hi guys,
I know there are plenty of posts about bricked phones and I've read most of them. Just want to do a sanity check here. If my phone has a LOCKED bootloader and USB debugging is NOT enabled, there is nothing I can do in terms of flashing an image right? I can enter bootloader and stock recovery, but when I boot to OS it bootloops.
Just want to confirm my only option is warranty claim with Google and there's no way to enable USB debugging other than from the OS?
Thanks in advance!
Click to expand...
Click to collapse
Go into the bootloader and on a PC with adb run "fastboot flashing unlock" and see what happens. I don't think you need adb enabled to do it but I could be wrong so just try
---------- Post added at 11:14 PM ---------- Previous post was at 11:10 PM ----------
@piotrus22 another option would be to go into recovery and adb sideload the latest ota package from google.
Can you side load with debugging off?
Also have you factory reset from recovery?
DR3W5K1 said:
Can you side load with debugging off?
Also have you factory reset from recovery?
Click to expand...
Click to collapse
Not sure if you can but it wouldn't hurt to try. That night work too
Try to sideload the latest ota image.
Sent from my Pixel C using Tapatalk
piotrus22 said:
Hi guys,
I know there are plenty of posts about bricked phones and I've read most of them. Just want to do a sanity check here. If my phone has a LOCKED bootloader and USB debugging is NOT enabled, there is nothing I can do in terms of flashing an image right? I can enter bootloader and stock recovery, but when I boot to OS it bootloops.
Just want to confirm my only option is warranty claim with Google and there's no way to enable USB debugging other than from the OS?
Thanks in advance!
Click to expand...
Click to collapse
im having a similar issue. my phone just started to bootloop randomly yesterday, i tried to flash stock and once i get to the setup screen it shuts down and reboots...
thanks guys. i actually tried to sideload and was successful, but still no booting up. still get the boot loop. interestingly enough when i try to sideload again, i get an error message: device '(null)' not found
piotrus22 said:
thanks guys. i actually tried to sideload and was successful, but still no booting up. still get the boot loop. interestingly enough when i try to sideload again, i get an error message: device '(null)' not found
Click to expand...
Click to collapse
What were you trying to do to get it like that?
Veid71 said:
What were you trying to do to get it like that?
Click to expand...
Click to collapse
ok i was able to try to sideload it twice. side load finishes successfully but still doesn't boot to OS....
piotrus22 said:
ok i was able to try to sideload it twice. side load finishes successfully but still doesn't boot to OS....
Click to expand...
Click to collapse
Have you tried a factory reset?
DR3W5K1 said:
Have you tried a factory reset?
Click to expand...
Click to collapse
yes of course -
piotrus22 said:
yes of course -
Click to expand...
Click to collapse
Well unfortunately you're out of things to try.
If your phone happens to be a 128gb model this is actually quite common.
---------- Post added at 12:25 PM ---------- Previous post was at 12:11 PM ----------
Further confirmation of problems with some 128 units.
https://support.google.com/pixelphone/forum/AAAAb4-OgUsZ1zs71de3Io/?hl=by
I hope your phone is under warranty because Google won't do crap if it isn't. I'm a proud owner of a POS 128GB brick thanks to their junk they sell.
Sent from my [device_name] using XDA-Developers Legacy app

Hisense A5 (GSI on e-ink?)

Hi all,
I've just got a new e-ink device Hisense A5. I've checked via adb and it says it supports trebble.
I would love to flash GSI, but am afraid of the consequences: will it work on e-ink device?
There is no TWRP for it either.
Can anyone help to point me in the right direction? Has anyone tried GSI on an e-ink device?
Thanks
Since there is no global rom for this device AOSP GSI looks a likely solution.
I would take a chance on it if I could unlock the bootloader.
I tried all the usual methods but it looks like a determined effort has been made to keep it locked.
Anyone up to the challenge?
?
Hi!
I have this phone also!
I found this on GSI https://www.getdroidtips.com/android-10-hisense-a5/
But does this require us to have an unlocked bootloader?
I'd be interested in knowing as well. Was thinking to buy one, but a 100% chinese market phone is just a no go for me. Potentially too many "spyware" apps installed.
I have it right now and i tried it. To enter Fastboot Mode you have to press the volume up button for 10 sec while insert the charging cable to the PC (The phone needs to be powered off before doing it)
What can i do further?
It is possible at this point to get GSF ID to get it signed by google and try to install some apps?
There is a way to enter developer mode in the Phone?
lillo9546 said:
I have it right now and i tried it. To enter Fastboot Mode you have to press the volume up button for 10 sec while insert the charging cable to the PC (The phone needs to be powered off before doing it)
What can i do further?
It is possible at this point to get GSF ID to get it signed by google and try to install some apps?
There is a way to enter developer mode in the Phone?
Click to expand...
Click to collapse
One guy managed to enter dev more, maybe try to tap several time on the build number (in parameters, about phone) as usual?
Then it seems that there is a box to check allowing OEM unlock.
Third step, try "fastboot oem unlock" command.
Anghirrim said:
One guy managed to enter dev more, maybe try to tap several time on the build number (in parameters, about phone) as usual?
Then it seems that there is a box to check allowing OEM unlock.
Third step, try "fastboot oem unlock" command.
Click to expand...
Click to collapse
Tried
It says command not found
lillo9546 said:
Tried
It says command not found
Click to expand...
Click to collapse
Maybe you can have a look at this tutorial and evaluate if A5 can also be managed with Qpst.
https://forum.xda-developers.com/general/rooting-roms/flashing-rom-hisense-a2-qpst-t3673945
---------- Post added at 08:29 PM ---------- Previous post was at 08:18 PM ----------
Had a look on Internet... Seems you can flash Hisense products with qpst only... I see nothing nowhere about bootloader unlock
---------- Post added at 08:32 PM ---------- Previous post was at 08:29 PM ----------
Look here... Always the same.
https://www.needrom.com/category/hisense/other-sub-hisense-other-categories/
Any updates? This phone is fascinating.
solarkraft said:
Any updates? This phone is fascinating.
Click to expand...
Click to collapse
https://forum.xda-developers.com/android/help/to-root-hisense-a5-t4058081/page5
This post is more active
Proof that GSI can be done, pics in the attachment. Just unsparse the GSI image with simg2img and flash it to system with QFIL. As far as I've tested, only Android 9 ones boot.
The refresh rate and latency is terrible though - unoptimized AOSP is unsuited for use on e-ink display.

Categories

Resources