I have a stock N5 that has a broken screen. You can see some parts of it but doesn't respond to touch at all. I saw there was an app on here that let's you see and remotely control the screen using your PC with adb. It looks like I might have the usb debugging turn on, however my adb shell is not authorized but does see the device. I have tried booting into stock recovery, but adb is not running at that time to allow me to push access keys.
What options do I have to be able to remotely use this phone. I want to use it as a camera for tinycam pro
Sent from my Pixel using Tapatalk
If your bootloader is unlocked, you can boot TWRP without flashing anything. From TWRP you'll get adb access.
If your bootloader is locked, you're doomed. :-/
Bootloader is locked. Is there anything I can flash to get it to work.
Sent from my Pixel using Tapatalk
I was able to use fastboot and unlock the bootloader. The phone restarted and went to a welcome screen. I was then able to flash twrp in recovery and load that up. I got into adb shell and ran some echo commands to put things into the default.props file in an attempt to enable us debugging when it rebooted. Well I guess the commands we're not correct or something but it didn't work. So then I went back into the bootloader and I thought I had to reflash twrp again, so I ran the same fastboot command I did before to load twrp. Says it wrote fine but now when I select recovery the phone just reboots back to the welcome screen. Since most of the screen is messed up o can't make out why that happens. Any help would be appreciated
Sent from my Pixel using Tapatalk
In case anyone else has the similar problem, once back into TWRP by using 'fastboot boot <img>', i used this post to mount the file system under system2 folder - https://forum.xda-developers.com/showpost.php?p=63829295&postcount=27
I then pushed my adb key onto the device so when the OS boots back up, it would allow adb to connect
Code:
adb push C:\Users\<username>\.android\adbkey.pub /data/misc/adb/adb_keys
Related
I'm kind of screwed and It's not even my mistake, I guess.
I clean flashed the Mahdi Update 25/04 yesterday earlier I had 03/03. In the morning I experienced 2 -3 random reboots and later only one random reboot after which my phone won't boot (bootloop). When i enter bootloader, it automatically selects "start" and boots into system and then reboots.
Once i got the chance and my phone booted fully. But then when I selected reboot into recovery so that i can restore a NAND. IT reboots, the team win logo shows up and then the cycle repeats.
Basically, i don't have access to recovery, my bootloader isn't stable (i.e. it automatically boots without selecting) so I'm unable to flash a stock img as of now. If and when my Nexus fully boots into system it stays the same for about 1 hr if i have any luck. PLz help.
From India. Unlocked Bootloader and custom Rom "Mahdi".
Have you tried using add to boot into recovery? If not also try to getting a logcat when it reboots, those will give us a little more of a general idea of what is actually happening.
First thing don't panic. You can't brick a nexus. You should be able to get into bootloader (volume down + power button) use Wugs Nexus Root toolkit from XDA forum. reload stock ROM in fastboot mode. I have done this lots of time. It's a draw back to being a tinkerer just can't leave well enough alone.
It sounds like your power bottom might be stuck to be honest.
Sent from my Nexus 5 using Tapatalk
nyterage said:
Have you tried using add to boot into recovery? If not also try to getting a logcat when it reboots, those will give us a little more of a general idea of what is actually happening.
Click to expand...
Click to collapse
I managed to somehow get into my bootloader and flashed the following
1. bootloader.img
2. radio.img
3. system.img
4. stock kernel (boot.img)
5. twrp recovery.img
I skipped userdata,img as i need to save my data.
I then went into recovery and did a factory wipe (not including internal storage)
My stock rom booted BUT the setup screen showed up and during the setup process it rebooted again and I couldn't mount my storage to backup.
MY MAIN PRIORITY IS TO COPY THE CONTENTS OF MY SD CARD Before flashing the whole stock image (including userdata)
Now when I type "adb version" in cmd I get Android Debug Bridge Version 1.0.31 but when I type "adb devices" whilst my phone is in fastboot mode, it doesn't list my phone. So i'm unable to "adb pull /mnt/sdcard"
I'm in the same situation with rare access to B/L (based on luck) and Recovery.
Plz tell me what to do when I am able to connect in bootloader mode (fastboot)
IF required I can upload a video showing that what problem I am facing.
scuccria said:
I managed to somehow get into my bootloader and flashed the following
1. bootloader.img
2. radio.img
3. system.img
4. stock kernel (boot.img)
5. twrp recovery.img
I skipped userdata,img as i need to save my data.
I then went into recovery and did a factory wipe (not including internal storage)
My stock rom booted BUT the setup screen showed up and during the setup process it rebooted again and I couldn't mount my storage to backup.
MY MAIN PRIORITY IS TO COPY THE CONTENTS OF MY SD CARD Before flashing the whole stock image (including userdata)
Now when I type "adb version" in cmd I get Android Debug Bridge Version 1.0.31 but when I type "adb devices" whilst my phone is in fastboot mode, it doesn't list my phone. So i'm unable to "adb pull /mnt/sdcard"
I'm in the same situation with rare access to B/L (based on luck) and Recovery.
Plz tell me what to do when I am able to connect in bootloader mode (fastboot)
IF required I can upload a video showing that what problem I am facing.
Click to expand...
Click to collapse
To use adb pull you have to enter the recovery. You need universal naked usb driver 0.73 to make adb work in recovery. If you are on windows 8 or 8.1 you have to turn off the driver signiture enforcement befote installing the universal naked usb driver 0.73
Tapatalk-kal küldve az én Nexus 5-el
El Daddy said:
It sounds like your power bottom might be stuck to be honest.
Click to expand...
Click to collapse
I agree. It's a malfunctioning power button due to several reasons (moisture, drops, etc.). I had this on my Nexus S.
Purchased an Lg Gpad 7 Wifi tablet (v400) 2 weeks ago. Came with preinstalled Lollipop android so i couldnt install a recovery rom to flash any other custom roms. Downgraded to Kitkat version following the instructions on Xda forums and succesfully installed Twrp. When i installed Cyanogenmod 12.1 through Twrp i got stuck in fastboot screen.
Any suggestions and / or solutions would be greatly appreciated.
I had a similar problem.. Only mine was stuck at the bootloader. Go in TWRP and repair /data and other partitions. My data partition gave me an error since F2FS is a little flaky and some ROMs corrupted it (claimed they supported it). I would recommend erasing the system, cache and data partition if you can't get into TWRP.
The problem is i cant get out of fastboot whatever i try. It says start on bootloader but the tablet just restarts on an empty screen doing nothing.
Hakalai said:
The problem is i cant get out of fastboot whatever i try. It says start on bootloader but the tablet just restarts on an empty screen doing nothing.
Click to expand...
Click to collapse
if you have an sd card, try removing that, then reboot.
if that doesnt work, try entering fastboot command, fastboot continue
Tried without sdcard and i get the same fastboot screen.
How can i give any commands? The only options i have are Restart Bootloader / Restart / Power off. Tried restarting bootloader but i get nothing in return tablet just stays on with nothing on screen.
Hakalai said:
Tried without sdcard and i get the same fastboot screen.
How can i give any commands? The only options i have are Restart Bootloader / Restart / Power off. Tried restarting bootloader but i get nothing in return tablet just stays on with nothing on screen.
Click to expand...
Click to collapse
you said it was stuck on fastboot, if thats the case, install any needed drivers on your pc, connect device to it, open a terminal in the fastboot dir (after you go get fastboot), then try those commands i gave. you could also try, fastboot reboot dont think i mentioned that before.
bweN diorD said:
you said it was stuck on fastboot, if thats the case, install any needed drivers on your pc, connect device to it, open a terminal in the fastboot dir (after you go get fastboot), then try those commands i gave. you could also try, fastboot reboot dont think i mentioned that before.
Click to expand...
Click to collapse
Did as you said but every command i gave gives me an error message in adb terminal. There are new lines in fastboot menu in tablet now. Bottom two are SECURE BOOT - enabled & LOCK STATE - locked.
Hakalai said:
Did as you said but every command i gave gives me an error message in adb terminal. There are new lines in fastboot menu in tablet now. Bottom two are SECURE BOOT - enabled & LOCK STATE - locked.
Click to expand...
Click to collapse
hmm, ok, im guessing it would have said that normally, when not broken. all the command does is try to release it past where its stuck. it doesnt actually flash, lock, unlock, or change anything.
imo, this seems good, because now we know fastboot is working.
i own lg devices, but not your specific device. i would hate to give you some bad advice and make your tablet broken more, but if it were me in this situation, i would try to flash the factory KK firmware you used to downgrade with odin or however you did it. hopefully, that will clean everything up and let it boot properly.
if for whatever reason you cant do that, we could try extracting the factory file, and just flashing recovery and system, those should be the only things that got changed putting on twrp and cm normally.
Sorry, I have the serious proplem wtih my LG pad V400, I rooted it and using <LG Flash Tool 2014> with <V40010c_00.kdz> to downgrate the firmware but their is error then my LG pad stuck in fastboot menu as with just turn off, restart and restart bootloader. if i seclect one one them the tablet just logged again the fastboot menu
it stuck on the fastboot menu and i cannot do nay think with it. I can restart with factory restore mode but when select yes to restore, it will restart and log in fastboot menu again.
I downloaded adb and fastboot program and put in one folder <Minimal ADB and Fastboot> in C:\Program Files (x86)\Minimal ADB and Fastboot
I dont have recovery image so i download file <cm-13.0-20160421-NIGHTLY-v400-recovery.img> form your link to download TWRP file
move it to folder of fastboot programe and changed its name to <recovery.img>
I turn on the tablet and it waited at fastboot menu
when i run the command <fasboot flash recovery recovery.img> and they said some thing wrong like in picture
please help me
Hi,'
I think I disabled google app on my nexus 5 (stock android) and since then my phone is stuck in boot loop. (My phone does not go past logo of marshmallow rolls or message saying starting apps 10 of 10). I have very important data that is not yet backed up and I need them to be recovered.
From various threads, I did following in recovery mode
1. Wipe cache option under recovery menu - as it was mentioned, that it would not delete any user data on my sdcard. (No help, still stuck with boot loop)
2. In recovery mode - there was an option to mount phone memory and I did that. My phone shows a message at the bottom of the screen that it is successfully mounted. But I am not familiar how to proceed further or to recover data from my phone.
My phone is running stock android and I think I have not disabled USB debugging. I am not familiar about ADB, but can follow your guidelines and execute them. When I connect my phone to windows laptop, I see my laptop trying to install the MTP device driver, but fails saying unable to find the driver.
I need to recover my data and Any help is greatly appreciated.
Is your bootloader unlocked? I'm guessing not.
Sent from my Nexus 5X using XDA Free mobile app
If the bootloader is unlocked, you could flash twrp and then mount the data partition from twrp. If the bootloader is not unlocked, you could try pulling the data from the phone using adb commands. Was debugging enabled in the rom?
I have not unlocked my boot loader. Is there a guide to use adb with stock android?
Only if you enabled debugging in developer options.
Today, I installed 15sec ADB installer and booted my device in to recovery mode by pressing power and volume keys.
Then under recovery menu there was an option called - Mount / System. I selected it by pressing power key and from ADB ran adb devices.
No devices was listed, when I ran ADB devices.
But I saw another option in my phone recovery screen - Apply update from ADB.
I got a message in phone - "Now send the pacakge you want to apply to the device with adb sideload filename".
Now, when I execute ADB devices in my PC cmd prompt, I see my device with its serial number.
then I tried to use ADB Pull /sdcard/ to recover files from PC command prompt. But I got a message - saying error closed.
Am I doing the right things? Can you guys guide me to recover files from this point.
My bootloader version is HHZ20h. Product - Hammerhead.
I noticed from below link a user has had luck with sideloading a launcher. Has anyone here tried it ? will it affect my data on phone?
https://code.google.com/p/android/issues/detail?id=64773#c22
Any guide to sideload google search app in recovery mode?
Have you considered side loading the OTA from Google? https://developers.google.com/android/nexus/ota Directions are on the site.
When you get to this point
(But I saw another option in my phone recovery screen - Apply update from ADB.
I got a message in phone - "Now send the package you want to apply to the device with adb sideload filename".), you send the ota zip. (Adb sideload <name of zip> ). You have to make sure the zip file is in the folder with adb files.
Sent from my Nexus 9 using Tapatalk
I tried to install OTA update and did the reboot. But it did not help.
Can anyone provide me a launcher that I can sideload in recovery mode? Reading from various threads, I think my phone is in this state because I disabled the google app, which is also the launcher.
Thank you
Try to flash system image without userdata wipe and wiping only cache
Sent from my fx-82MS CAF using Tapatalk
santi1993 said:
Try to flash system image without userdata wipe and wiping only cache
Sent from my fx-82MS CAF using Tapatalk
Click to expand...
Click to collapse
How to perform this flash without wiping my user data? Any guide for it?
Download the stock image from Google that matches the rom currently installed on the phone, extract system.img, boot phone into fastboot mode, and type fastboot flash system system.img at the command prompt, and reboot.
audit13 said:
Download the stock image from Google that matches the rom currently installed on the phone, extract system.img, boot phone into fastboot mode, and type fastboot flash system system.img at the command prompt, and reboot.
Click to expand...
Click to collapse
Let me try it. so far I have been able to execute only adb sideload commands, after choosing Apply update from ADB.
Let me try this - fastboot flash system system.img.
smartey said:
Let me try it. so far I have been able to execute only adb sideload commands, after choosing Apply update from ADB.
Let me try this - fastboot flash system system.img.
Click to expand...
Click to collapse
Boot ur phone in fastboot mode (From power off to vol down + power), then connect it to the pc and install latest_google_drivers for nexus devices, ull need to manually install them, after that ur fastboot will recognize ur device.
From that type fastboot devices, if u see ur device connected u simply need to get into the commands that the other user gave to you, i u are lucky ur device will boot.
if u had unlocked bootloader the thing was easy as installing twrp 3.0.2.0 and backup all ur data via MTP
I just tried rooting my phone. The phone is cycling back and forth between the bootloader is unlocked screen and the Motorola splash screen.
To repeat some steps from a prior post.
My phone had QPR30.80-58-3 .
I downloaded that ROM and extracted the boot.img file.
I downloaded the latest Magisk Manager and installed it on my phone.
I ran through the patching process for boot.img.
I requested an unlock code from Motorola and unlocked the bootloader.
I flashed the patched boot image which patched partition b.
I flashed the patched boot image to partition a.
I rebooted which began the cycle.
I tried holding down the power button but it returns to the cycle.
I can get back to the bootloader with the Volume Down and Power buttons.
Any suggestions on what could get me back to a functioning phone, rooted or not rooted?
I would confirm the version of the boot image you flashed matches the version of the installed rom. You could also try to flash the unpatched / original boot.img to see if that gets you booting again.
dafunk60 said:
I would confirm the version of the boot image you flashed matches the version of the installed rom. You could also try to flash the unpatched / original boot.img to see if that gets you booting again.
Click to expand...
Click to collapse
I checked that the image I patched was from the QPR30.80-58-3 ROM which matched the level after the phone was updated.
I flashed that original boot image which flashed partition a and then rebooted. I did not flash partition b.
It first came up with the unlock warning screen. It sat on the Motorola splash screen for a noticeable amount of time followed by a yellow screen with a circle around the Motorola symbol. Finally it ended up on a blue Hello there screen with a yellow start button.
This screen was unresponsive. Eventually through various cyclings through all this I ended up on a screen that said Android could not boot and gave me an option of a factory reset. I did that but it did not help getting past the Hi there screen.
I went back and flashed the QPR30.80_58 image on both partitions a and b. This got me back to setting up the phone again. The phone is at QPR30.80_58. I am considering just rooting at this level.
So I tried patching the original QPR30.80_58 boot image. I did notice that it appeared the phone had automatically staged the QPRS30.80_58_3 update. I proceeded in (false) hopes that I could stop that.
It flashed the b partition. Ended up stuck in the bootloader unlock loop. I flashed the a partition but no change.
Previously I had ended up on a recovery screen automatically after some time. I could not force this to happen.
I tried flashing the original unpatched boot image but would end up on a non-functioning Hello there screen.
I tried adb recovery and adb shell but came back with device unauthorized.
I tried following some instructions on using fastboot erase userdata and fastboot erase cache. No change.
I finally found out that the Recovery menu was option off the bootloader screen. However, that came up with No command.
Lenovo Rescue did not want to recognize my XT2043-4 device.
I flashed the unpatched retail QPRS30.80_58_3 boot image to both a and b partitions. That got me back to a functioning phone. After getting through the login and setup steps I did find that it was at QPRS30.80_58_3.
Out of curiosity, I tried Lenovo Rescue again. I received a "Failed to match connected device. Reconnect device, then try again." which did not work.
Now I am at a loss.
DougPeterson said:
So I tried patching the original QPR30.80_58 boot image. I did notice that it appeared the phone had automatically staged the QPRS30.80_58_3 update. I proceeded in (false) hopes that I could stop that.
It flashed the b partition. Ended up stuck in the bootloader unlock loop. I flashed the a partition but no change.
Previously I had ended up on a recovery screen automatically after some time. I could not force this to happen.
I tried flashing the original unpatched boot image but would end up on a non-functioning Hello there screen.
I tried adb recovery and adb shell but came back with device unauthorized.
I tried following some instructions on using fastboot erase userdata and fastboot erase cache. No change.
I finally found out that the Recovery menu was option off the bootloader screen. However, that came up with No command.
Lenovo Rescue did not want to recognize my XT2043-4 device.
I flashed the unpatched retail QPRS30.80_58_3 boot image to both a and b partitions. That got me back to a functioning phone. After getting through the login and setup steps I did find that it was at QPRS30.80_58_3.
Out of curiosity, I tried Lenovo Rescue again. I received a "Failed to match connected device. Reconnect device, then try again." which did not work.
Now I am at a loss.
Click to expand...
Click to collapse
Happy to hear you have a working phone again! The lack of touchscreen response & the stuck at the hello screen issues are what others have reported when they used a boot image from a different version than on the phone. I suspect that something got confused between the version & slot somewhere along the way. As far as the Lenovo Rescue software not seeing the phone, it's communicating via ADB. If I recall correctly I needed to reauthorize the PC to connect via ADB after updating from 30.80-58 to 30.80-58-3. When I connect the phone via USB there's a popup on the phone asking to authorize the PC. Can you connect via ADB in the command line? If yes, you may want to reinstall the Lenovo software. If no, I would troubleshoot the ADB connection.
I originally rooted the 30.80-58 version. When 30.80-58-3 was released all I did was flash the unpatched boot.img, took the update OTA, let it reboot, then flash a patched boot.img from 30.80-58-3. All worked as expected, user data was intact.
dafunk60 said:
Happy to hear you have a working phone again! The lack of touchscreen response & the stuck at the hello screen issues are what others have reported when they used a boot image from a different version than on the phone. I suspect that something got confused between the version & slot somewhere along the way. As far as the Lenovo Rescue software not seeing the phone, it's communicating via ADB. If I recall correctly I needed to reauthorize the PC to connect via ADB after updating from 30.80-58 to 30.80-58-3. When I connect the phone via USB there's a popup on the phone asking to authorize the PC. Can you connect via ADB in the command line? If yes, you may want to reinstall the Lenovo software. If no, I would troubleshoot the ADB connection.
I originally rooted the 30.80-58 version. When 30.80-58-3 was released all I did was flash the unpatched boot.img, took the update OTA, let it reboot, then flash a patched boot.img from 30.80-58-3. All worked as expected, user data was intact.
Click to expand...
Click to collapse
I double checked that I had USB debugging set, given I have reset a couple of times. I revoked all USB access and reinstalled the Rescue app. I still get the Failed to match connected devices error.
fastboot device will list the phone.
adb devices or adb devices -l does not list anything and adb shell says no devices/emulators found.
If I try to get into recovery mode I get a No command screen. I have been trying to take notes on what I did but there have been gaps in all the fiddling. I may have only flashed one partition the last time I tried putting back a stock boot image.
For USB drivers I downloaded the latest from Motorola. Was that sufficient for this?
DougPeterson said:
I double checked that I had USB debugging set, given I have reset a couple of times. I revoked all USB access and reinstalled the Rescue app. I still get the Failed to match connected devices error.
fastboot device will list the phone.
adb devices or adb devices -l does not list anything and adb shell says no devices/emulators found.
If I try to get into recovery mode I get a No command screen. I have been trying to take notes on what I did but there have been gaps in all the fiddling. I may have only flashed one partition the last time I tried putting back a stock boot image.
For USB drivers I downloaded the latest from Motorola. Was that sufficient for this?
Click to expand...
Click to collapse
If you want to get into recovery, boot into the bootloader than do
Code:
fastboot reboot fastboot
That'll boot you into fastbootd which has an option to go to the real recovery
DougPeterson said:
I double checked that I had USB debugging set, given I have reset a couple of times. I revoked all USB access and reinstalled the Rescue app. I still get the Failed to match connected devices error.
fastboot device will list the phone.
adb devices or adb devices -l does not list anything and adb shell says no devices/emulators found.
If I try to get into recovery mode I get a No command screen. I have been trying to take notes on what I did but there have been gaps in all the fiddling. I may have only flashed one partition the last time I tried putting back a stock boot image.
For USB drivers I downloaded the latest from Motorola. Was that sufficient for this?
Click to expand...
Click to collapse
If adb isn't showing any devices connected that would explain why the rescue software cannot find your phone. Perhaps you don't have the correct driver installed. Windows Device Manager shows the phone as a Motorola ADB Device on my PC.
View attachment 5061327
Another possibility is that you have multiple versions of adb on your PC. Older versions won't work but the adb.exe in "C:\Program Files (x86)\Rescue and Smart Assistant" works for sure. With your phone booted into android & unlocked, plug it into your PC. Do you see the "USB debugging connected" on the phone? If you don't I would re-check that USB debugging is enabled. If you do see the debugging notification, on your PC, open a command prompt and navigate to "C:\Program Files (x86)\Rescue and Smart Assistant". Run
Code:
adb devices
Does adb find your phone?
For some reason, when I go to my fastboot mode, it shows blank screen. Any idea how i can get back to the default fastboot mode screen which usually shows device state, etc. My phone boots up fine , its OEM unlocked but without fastboot im unable to flash custom recovery or rom or do anything to be honest. One plust 6T. Please help
crmemaster said:
For some reason, when I go to my fastboot mode, it shows blank screen. Any idea how i can get back to the default fastboot mode screen which usually shows device state, etc. My phone boots up fine , its OEM unlocked but without fastboot im unable to flash custom recovery or rom or do anything to be honest. One plust 6T. Please help
Click to expand...
Click to collapse
with normal boot, i can access adb commands, its just that fastboot mode is blank and hence unable to access commands. Ive installed all possible drivers, i think the kernel is broken. Any possible way to fix this?
crmemaster said:
with normal boot, i can access adb commands, its just that fastboot mode is blank and hence unable to access commands. Ive installed all possible drivers, i think the kernel is broken. Any possible way to fix this?
Click to expand...
Click to collapse
Is developer options and usb debugging enabled in your phones settings? Also no screen lock set? If so if you have another Android device that's also rooted with magisk you can use Osm0sis and Surge's fastboot/adb magisk module, (a quick search in magisk will pull it up) Install it on your other device and use an otg cable ($5 online or make one yourself) and using termux app from "other phone" with connected otg & magisk root type: su (hit enter) grant root once it pops up then type: adb reboot bootloader then tick the pop up on phone you are trying to boot recovery on when it pops up. Then type: fastboot boot twrp_3.4.0-9-11.img (hit enter) Just make sure you put your TWRP recovery.img in correct directory on phone you you're using termux app on with otg and fastboot/adb module to boot the phone you are trying to boot to recovery.
Using root explorer directory in termux is: /data/data/com.termux/files/home/
place your TWRP_3.4.0-9-11.img ,, which ever TWRP image you are trying to boot in that directory...
Hope this makes sense. I don't use Windows and haven't for many years now. I've unlocked bootloader's and rooted many devices using another Android device this way now for years. Super easy! Not sure why you would be getting a black screen. Have you searched for solution to this? I would definitely search , a lot about the black screen situation.. Make sure you have a charged battery too. Sounds stupid I know but it's possible you are at 0%.. Hope this helps...
(Edit)