Hello,
Phone: Redmi K20 Pro / Xiaomi Mi 9T Pro
ROM: LineageOS 17.0
I installed LineageOS on my phone yesterday.
I used ADB and Fastboot on Windows with TWRP.
Now, I want to install ANXCamera in order to get back full capacity of my camera.
From my understanding, I can also do it using TWRP.
Problem:
When I enter adb devices in the terminal while the phone is on, the device is recognised.
After I enter adb reboot bootloader, and try again adb devices, the phone is not found.
Things done:
In the settings, I allowed USB debugging.
On Windows, I checked for updated of the drivers for the phone.
I follow the same process than yesterday, when I installed LineageOS, but somehow this time it doesn't work.
Do you know where the problem can come from?
-----
Additional question:
Can you confirm if then, I will have to use adb sideload to flash the zip of this program on TWRP please?
-----
Thanks a lot
I also encountered this. I then tried it on another laptop and all went well. You may try this, use other USB port, use system restore in Windows to roll-back to the point it still worked etc (yesterday)..
XedosMD said:
I also encountered this. I then tried it on another laptop and all went well. You may try this, use other USB port, use system restore in Windows to roll-back to the point it still worked etc (yesterday)..
Click to expand...
Click to collapse
Thanks a lot, will try that.
Do you remember that is the command I should use to transfer the file in TWRP?
I don't know how it works to upload a file that is due to be an additional program and not a full ROM.
Please explain, don't know what you mean exactly.. Just copy the zip to your phone and flash within TWRP.
https://camera.aeonax.com/ is where you can download your camera app.
XedosMD said:
Please explain, don't know what you mean exactly.. Just copy the zip to your phone and flash within TWRP.
https://camera.aeonax.com/ is where you can download your camera app.
Click to expand...
Click to collapse
Really sorry, I totally forgot to get back to you...
Yes, the procedure to follow is pretty easy in fact.
I was afraid it would need the use of an external device.
Thanks a lot for your help!
Related
So I got carried away with trying to get rid of that three dot menu button at the bottom of the screen and I've slowly managed to work myself into a really bad problem. I'm not necessarily new to this, I've rooted my Droid 2, Droid 3, and GS3, but this has been more complicated for me.
Anyways, my problem is, I was trying to wipe my phone so that I could flash a ROM. This is because I couldn't access my settings (I overwrote the original in an attempt to get rid of the multitask button). But while I was in CWM I factory reset it but I also accidentally deleted the system. My bootloader is unlocked, but now my phone is on and I can't get into recovery, and I'm assuming it's because the whole system is gone so there's nothing to boot.
Another problem I had (while my phone was able to boot up completely), Android File Transfer wouldn't work, I downloaded a rom for the settings.apk but it wouldn't let me transfer files between my computer and phone. I emailed the .apk to myself but since I couldn't access settings I wasn't able to pick my usual email (although now I'm thinking I should have just used the email I first signed in with). Not as much of a concern but input is still welcome.
I've looked up RUU but it looks like it's not available yet for Verizon. Any possible solutions would be MUCH appreciated.
Don't worry, your device is not bricked.
If your bootloader works well, you must select fastboot and flash the recovery via fastboot.exe in the command line. Now you should be able to get into recovery.
If you wiped your partitions, you can have a trouble with mounting /sdcard. Then you should get an OTG Micro USB cable and put ROM on your USB stick, but I'm not sure if TWRP recovery for HTC One supports mounting flash memory from USB host.
Gudio142 said:
Don't worry, your device is not bricked.
If your bootloader works well, you must select fastboot and flash the recovery via fastboot.exe in the command line. Now you should be able to get into recovery.
If you wiped your partitions, you can have a trouble with mounting /sdcard. Then you should get an OTG Micro USB cable and put ROM on your USB stick, but I'm not sure if TWRP recovery for HTC One supports mounting flash memory from USB host.
Click to expand...
Click to collapse
I'm stuck on the green HTC logo screen and the red warning about the bootloader. I can't boot into recovery anymore. By the way I'm using a Mac but I do have a PC running Windows 8 if there's solutions I could try
Gudio142 said:
Don't worry, your device is not bricked.
If your bootloader works well, you must select fastboot and flash the recovery via fastboot.exe in the command line. Now you should be able to get into recovery.
If you wiped your partitions, you can have a trouble with mounting /sdcard. Then you should get an OTG Micro USB cable and put ROM on your USB stick, but I'm not sure if TWRP recovery for HTC One supports mounting flash memory from USB host.
Click to expand...
Click to collapse
I tried flashing into recovery via fastboot but my computer doesn't recognize my device. And I'm pretty sure I had drivers installed since that's how I unlocked the bootloader in the first place..
xerhoffx said:
I tried flashing into recovery via fastboot but my computer doesn't recognize my device. And I'm pretty sure I had drivers installed since that's how I unlocked the bootloader in the first place..
Click to expand...
Click to collapse
Install the latest drivers and try from a windows 7 pc (or windows 8, win 8.1 doesn't work well)
Reinstall drivers if you haven't already and try the correct file for your 'Modelid' here. It's the only way I got mine to work again after i did the same thing.
Note: The file i used had a different software version but it still flashed ok.
After that, if you can find the right Nandroid you now have the ability to flash that
n1234d said:
Install the latest drivers and try from a windows 7 pc (or windows 8, win 8.1 doesn't work well)
Click to expand...
Click to collapse
I only have Windows 8 I believe...
xerhoffx said:
I only have Windows 8 I believe...
Click to expand...
Click to collapse
Try a different PC, worked for another guy whose pc wouldn't detect his phone. See if a pc with XP works..
ndulian increase
jingles98 said:
Reinstall drivers if you haven't already and try the correct file for your 'Modelid' here. It's the only way I got mine to work again after i did the same thing.
Note: The file i used had a different software version but it still flashed ok.
After that, if you can find the right Nandroid you now have the ability to flash that
Click to expand...
Click to collapse
Where could I find a nandroid for Verizon? I feel like Verizon is the most difficult to find.
FIXED
I was finally able to boot into recovery and thank goodness had a CWM backup. Thanks for your input guys.
So I went to flash the newest version of TWRP and once I got it flashed from fastboot, it's telling me I have no OS installed. ADB Sideload doen't appear to be working for me either, keeps telling me device not found.
I need some help really fast!! Is there a way to flash a ROM from Fastboot? Or is there any other way to move a ROM file onto my damn phone? I have no idea why it's telling me there is no OS installed....
UPDATE: Got it to actually try to sideload, but got an error "* failed to write data 'protocol fault (no status)'. Ughhh, I just want my phone to work again.
Look around for adb drivers, also use a different port or USB cable
SaHiLzZ said:
Look around for adb drivers, also use a different port or USB cable
Click to expand...
Click to collapse
The drivers eventually worked, my phone seems to have been broken even worse than before now....
If you want help you will have to explain more
sent from my mobile device
SaHiLzZ said:
If you want help you will have to explain more
sent from my mobile device
Click to expand...
Click to collapse
I made a separate thread relating all of the information and what I have done to get to this point here: http://forum.xda-developers.com/showthread.php?t=2651187
Figured my current issue isn't related to ADB Sideloading anymore.
Hello,
So I have officially had my first screw up. Rather than getting into what happened and explaining what a retard I am, I will make a long story short.
I can not boot into my OS to activate USB debugging. So when I am in bootloader, no fastboot devices are showing. I have no backup. I can however get into TWRP! What do I do? Can I flash system.img in TWRP? If not I think I am screwed... Any help would be greatly appreciated right now! I am kind of freaking out.
I am newer to Android. My Nexus 6 is my first Android Phone. Why am I flashing stuff and not having a backup? Because I am stupid and did not put it on a flash drive when I clean installed Windows 10 on my computers new SSD.
EDIT: Problem solved and I apologize for wasting all of your time. Apparently I did know what I was doing. (Kinda... lol) I did a clean install of Windows 10 on my laptop today because I got a new Samsung 850 Pro SSD. Apparently when I installed the Android SDK Platform tools and google drivers the drivers did not "take". So here I am freaking out, wondering why my Nexus 6 was not being recognized as a fastboot device, and the damn driver wasn't even installed. I had to go into device manager and hold my laptops hand / point it directly to the google drivers folder. My laptop still made the sound when I plugged it in so I didn't think the drivers were the issue. But oh well...
I can't believe how fast I had a few different people willing to help! I really appreciate it and it is good to know that help is here when needed!
Rektifying said:
Hello,
So I have officially had my first screw up. Rather than getting into what happened and explaining what a retard I am, I will make a long story short.
I can not boot into my OS to activate USB debugging. So when I am in bootloader, no fastboot devices are showing. I have no backup. I can however get into TWRP! What do I do? Can I flash system.img in TWRP? If not I think I am screwed... Any help would be greatly appreciated right now! I am kind of freaking out.
I am newer to Android. My Nexus 6 is my first Android Phone. Why am I flashing stuff and not having a backup? Because I am stupid and did not put it on a flash drive when I clean installed Windows 10 on my computers new SSD.
Click to expand...
Click to collapse
you can sidelod any rom(and gapps) via adb or with twrp, then flash it in twrp.
simms22 said:
you can sidelod any rom(and gapps) via adb or with twrp, then flash it in twrp.
Click to expand...
Click to collapse
Can I flash system.img in twrp ? I decided to wipe dalvik, system, data, internal storage, and cache before flashing MRA58N. I guess I wasn't thinking obviously. Being now when in bootloader mode my device isn't recognized.
I really don't know how or what to do. I have all of the images for MRA58N and I have access to twrp. I have no idea what to do now. I am noob with TWRP. Do I have to use the mount feature or ?
I'm really freaking out here. I have my Nexus 6 in TWRP right now, hooked to my computer. I am to scared to do anything! My phone is literally wiped, so I don't even get how TWRP is on it to be honest. lol
If no devices are showing in fastboot then you should check your drivers on your computer. And TWRP only allows you to flash .img files on recovery and boot partitions.
Even though this thread doesn't have the newest update you might be able to replace the .img files in the zip with the ones you have, OR you can just use the 58K build to get you bootable.
I have to system.img on my phone in the TWRP folder. When I click install, then images, It only gives me Boot and Recovery for "Select Partition to flash image"
With the phone in bootloader mode and connected to pc you can use fastboot not adb. That's how you flash the factory images.
With the phone in twrp and connected to pc you should see your phone and its internal storage from the pc. Drag and drop a rom zip to your internal storage and flash a rom.. Can also go to 'advanced' in twrp and adb sideload rom-name.zip.
If the phone doesn't show up on your PC in either mode you need the latest USB drivers, or check device manager.
Sent from my Nexus 6 using Tapatalk
yes because twrp will only allow you to flash your boot and recovery partitions if you're using .img files,
Go to that thread I listed above and grab the zip file for the MRA58K the one labeled as "Base."
Transfer it to your phone though a usb cable while in twrp. Then flash it and when it gets done reboot to system.
Your phone should be on Marshmallow and you can give your factory .img files another shot.
Thank you all for the advice. Especially StykerB for being more specific. I wasn't sure if I needed more than one zip or just the base. I should be good now. Right now I am uninstalling the google usb drivers and re-installing them. I just installed them today.... So I do not get it. My Nexus 6 shows up on my computer while in twrp but not for fastboot in bootloader. makes no sense. Or maybe it does?
I wonder wtf is going on. I have the google usb drivers installed, but my computer is not recognizing my Nexus 6. That is why I am having problems. I was going to say, I have flashed .img's to my Nexus 6 many times now. That is why I started freaking out when no matter what I did I could not get fastboot to see my Nexus 6. I am going to look into this USB driver issue first. If I can fix that I can flash the images the normal way and be done with it.
I wan't to thank you all and apologize for wasting your time. I thought I knew what I was doing, and I actually did. I installed a new Samsung 850 Pro SSD in my laptop today. I did a clean install for obvious reasons. Well when I installed the Android SDK platform tools and Google USB drivers, for some reason the USB drivers didn't "take". Even when I re-installed them they didn't. I had to go in device manager with my N6 plugged in, and hold my computers hand and point it directly to the google folder. Once I did that the driver installed and I was good to go.
It is good to know that help is definitely here if needed. You all responded very fast! Before I knew it I had a few different people helping / ready to help. Thank you all again!
Alright guys, I'll get right to the point with this one. So I was flashing a stock image to get back to Marshmallow from N preview 3, and for whatever reason, I couldn't get my system partition to flash! It would begin, and then just finish early. When I tried again, it kept telling me that the file was in use in another program. I made a new copy of my platform tools and the stock image I needed, and it did the same thing! My first thought was a corrupted system partition, and I was really hoping it wasn't that. I got it to work using my sister's really really slow Windows Vista laptop (not kidding, took an HOUR to flash) and that worked. Since then I reinstalled windows on my main laptop, but was wondering just what could have caused that? It kept partially flashing the image, and then saying it was in use right after when I tried to do it again. Sorry this isn't too much to go on, I don't have screens or logs or anything to help the case, but suggestions? Thanks all!
H4X0R46 said:
.... I got it to work using my sister's really really slow Windows Vista laptop (not kidding, took an HOUR to flash) and that worked.
Click to expand...
Click to collapse
Hardware issue or wrong drivers. Your PC - USB port - USB cable - drivers or drivers not correct/installed wrong drivers.
Before fastboot check PC in device manager if your phone is recognized.
Download toolkit of wugfresh. After installing there is a sub folder with drivers and also as a sub folder with fastboot and adb.
Install the drivers and use the fastboot/adb and check/try again.
NLBeev said:
Hardware issue or wrong drivers. Your PC - USB port - USB cable - drivers or drivers not correct/installed wrong drivers.
Before fastboot check PC in device manager if your phone is recognized.
Download toolkit of wugfresh. After installing there is a sub folder with drivers and also as a sub folder with fastboot and adb.
Install the drivers and use the fastboot/adb and check/try again.
Click to expand...
Click to collapse
Sure hope it wasn't hardware. That would be bad. My sister's did it without problem despite the amount of time it took lol. I always use my laptop to flash images, it just chose today to do that. It's really weird at that, never seen that happen before. Fastboot devices command showed that it was connect and seen, so that's even more strange.
Also, does anyone know a sure fire way to check if my system partition is actually getting corrupted? Or is that much more extensive?
H4X0R46 said:
Also, does anyone know a sure fire way to check if my system partition is actually getting corrupted? Or is that much more extensive?
Click to expand...
Click to collapse
In case the system partition is corrupted the phone will not boot. And the partition will not mount in TWRP recovery.
NLBeev said:
In case the system partition is corrupted the phone will not boot. And the partition will not mount in TWRP recovery.
Click to expand...
Click to collapse
Well, my device boots and I as able to flash xposed with out and issues so that's not the case. Might have just been my computer acting up. Thanks for your input! It helps a lot!
[EDIT: It's all good now... A stupid mistake of mine]
Ok, everything was fine... I was on PE and everything was normal. Then I wanted to try something out and cleared everything in TWRP and rebooted to fastboot, because I needed a different version of TWRP...
But once in fastboot and connected to my PC adb couldn't detect my device (list of devices attached is empty), so I can't flash twrp -> I can't do anything! I'm simply stuck in fastboot...
After a bit of googling i found out that I somehow had the wrong drivers installed, so I went into device manager and it showed some kind of "kedacom usb drivers". I tried every tutorial that is on the internet, but nothing worked. In the end I somehow got it changed to the regular "Android device -> Android ADB Interface"(how it used to- and should be?) from those "kedacom usb drivers" and I thought I found the solution, but it still doesn't recognize my device in adb I also tried the MiFlash tool - same thing
Is it possible that my mistake was not enabling usb-debugging beforehand and can I somehow get out of fastboot?
I would be so grateful if anyone was able to help me
Moischen said:
Ok, everything was fine... I was on PE and everything was normal. Then I wanted to try something out and cleared everything in TWRP and rebooted to fastboot, because I needed a different version of TWRP...
But once in fastboot and connected to my PC adb couldn't detect my device (list of devices attached is empty), so I can't flash twrp -> I can't do anything! I'm simply stuck in fastboot...
After a bit of googling i found out that I somehow had the wrong drivers installed, so I went into device manager and it showed some kind of "kedacom usb drivers". I tried every tutorial that is on the internet, but nothing worked. In the end I somehow got it changed to the regular "Android device -> Android ADB Interface"(how it used to- and should be?) from those "kedacom usb drivers" and I thought I found the solution, but it still doesn't recognize my device in adb I also tried the MiFlash tool - same thing
Is it possible that my mistake was not enabling usb-debugging beforehand and can I somehow get out of fastboot?
I would be so grateful if anyone was able to help me
Click to expand...
Click to collapse
what the
why dint u just save the new twrp to internal, boot to twrp, flash the new twrp image as recovery m thats it reboot to twrp and it will be the new one you flashed.
you dint have to wipe anything or use pc
Mooatreides said:
what the
why dint u just save the new twrp to internal, boot to twrp, flash the new twrp image as recovery m thats it reboot to twrp and it will be the new one you flashed.
you dint have to wipe anything or use pc
Click to expand...
Click to collapse
Yeah, good question... But it's too late for that now
Try another pc
emprazol said:
Try another pc
Click to expand...
Click to collapse
same thing
Manually install adb driver
Moischen said:
same thing
Click to expand...
Click to collapse
One time, I had such an issue with drivers, what I did is use a free VM machine software on Windows to install a Linux distro (or you could dual boot it), and from Linux it worked to detect my device.
On the other hand, there are really probably easier ways to fix your issue, but who knows, it may help and does not take too long.