So, I dropped my G3 and unfortunately the screen entirely shattered. I have zero response from the screen at all. I need to at least get a full backup, but ideally I'd like to get a backup and then revert back to stock, all with only adb commands or other usb access... anyone know how to do this?
Quantumrabbit said:
So, I dropped my G3 and unfortunately the screen entirely shattered. I have zero response from the screen at all. I need to at least get a full backup, but ideally I'd like to get a backup and then revert back to stock, all with only adb commands or other usb access... anyone know how to do this?
Click to expand...
Click to collapse
I know the backup and restore commands i.e
"adb backup" &
"adb restore C:
\[restorefile].zip"
Anyone know how to do a restore to factory or anything like that only from USB connection?
\Trying the adb backup, having issues getting it to run at this point.
Quantumrabbit said:
Anyone know how to do a restore to factory or anything like that only from USB connection?
\Trying the adb backup, having issues getting it to run at this point.
Click to expand...
Click to collapse
Power off the phone, and boot into the recovery using the back buttons, assuming they still work, if not, "adb reboot recovery" should boot into recovery
I can confirm that TWRP v2.8.0.0 has support for mouse using an OTG cable, if you do not have one they're $0.05 on amazon:
http://www.amazon.com/s/ref=nb_sb_noss_1?url=search-alias=aps&field-keywords=usb+otg
(The power dongle one is helpful but not necessary)
Use the mouse as you would touchscreen to make a NAND backup.
Then go to the "mount" screen, make sure the button on the bottom right says "Disable MTP" and unplug the OTG cable.
Plug in normal cable to PC, you should have access to the device's internal storage
Pull contents to PC
Pictures are attached showing the mouse on screen for TWRP
2kool4u526 said:
Power off the phone, and boot into the recovery using the back buttons, assuming they still work, if not, "adb reboot recovery" should boot into recovery
I can confirm that TWRP v2.8.0.0 has support for mouse using an OTG cable, if you do not have one they're $0.05 on amazon:
http://www.amazon.com/s/ref=nb_sb_noss_1?url=search-alias=aps&field-keywords=usb+otg
(The power dongle one is helpful but not necessary)
Use the mouse as you would touchscreen to make a NAND backup.
Then go to the "mount" screen, make sure the button on the bottom right says "Disable MTP" and unplug the OTG cable.
Plug in normal cable to PC, you should have access to the device's internal storage
Pull contents to PC
Pictures are attached showing the mouse on screen for TWRP
Click to expand...
Click to collapse
Nice.
Thanks I'll give this a shot
No problem, let us know how that turns out for you!
Related
I've seen an increase in people who have gotten themselves stuck in a bootloop or can't seem to get the combo right to get into download or recovery mode.
Assumptions:
You have the proper drivers installed
Samsung Driver
Your phone is recognized by your PC
Instructions:
Power Phone off
Extract this folder to your computer
Run batch file for Download or Recovery Mode (it waits to see your phone)
Plug phone into computer
Power phone on
Phone should be detected and go into the proper mode
Thx Red_81, again. Glad to see u put this here for the i777. Appreciate u sharing this. It should provide some good help for many users. :thumbup:
Sent from my SAMSUNG-SGH-I777 using xda premium
So much easier than trying to explain how to install the sdk and then what commands to run. The only problem is you need to have working drivers.
Sent from my SGH-I777 using xda premium
Red_81 said:
I've seen an increase in people who have gotten themselves stuck in a bootloop or can't seem to get the combo right to get into download or recovery mode.
Assumptions:
You have the proper drivers installed
Samsung Driver
Your phone is recognized by your PC
Instructions:
Power Phone off
Extract this folder to your computer
Run batch file for Download or Recovery Mode (it waits to see your phone)
Plug phone into computer
Power phone on
Phone should be detected and go into the proper mode
Click to expand...
Click to collapse
My phone is stuck in boot logo. Computer is detecting phone as "SAMSUNG Android ADB Interface" but adb is not recognizing my phone.
Any ideas?
---------- Post added at 10:29 AM ---------- Previous post was at 10:23 AM ----------
lambition said:
My phone is stuck in boot logo. Computer is detecting phone as "SAMSUNG Android ADB Interface" but adb is not recognizing my phone.
Any ideas?
Click to expand...
Click to collapse
Never mind. I just got it working.
Had to just enter adb command directly. wait-for-device is not working for my phone for some reason.
If you get stuck there again, unplug and plug in the device again.
Sent from my SGH-I777 using xda premium
Adb kill server, adb start server.
Sent from my GT-I9100 using Tapatalk 2
Phalanx7621 said:
Adb kill server, adb start server.
Sent from my GT-I9100 using Tapatalk 2
Click to expand...
Click to collapse
Script already does that
Sent from my SGH-I777 using xda premium
Thanks
Thanks i was tinkering with a noria 7" tablet, which hasn't worked right since i got it but for 65 bucks its to be expected, but i used sdk manager to get it to register on my computer as an android adb device and for some reason i tried to turn the wifi on and it crashed and got stuck in a boot loop idk why. like i said hasn't worked right since i bought it. But i did use adb portable like you said to get into recovery mode and it worked great thanks! For other noria users when i figure out how to flash a rom to it i'll start a section here on xda as soon as i figure it out. Thanks again
Any suggestions if ADB doesn't see it?
- Phone was working fine in the morning and at lunch I noticed it was off.
- Try to turn phone back on and it is stuck at the samsung menu like everyone else.
- Soft and hard reset change nothing.
- Neither recovery nor download mode works using every key combo that I've seen suggested.
- Computer detects a device but "USB Device not recognized" and ADB can't see any devices (and I know it is set up correctly as I have the full SDK installed and known to be working).
- Charging still works fine and the battery is now at 100%
- Phone is NOT rooted and has no special apps or any recent changes to change the situation (not even app updates since a few weeks)
I'm not sure what else to do. I will probably let it sit for a few days without a battery, but otherwise I would open it up and see if there is some mechanical/electrical issue like a short or something somewhere. Pretty sure this is a software issue though. Any ideas?
BrockSamsonFW said:
Any suggestions if ADB doesn't see it?
- Phone was working fine in the morning and at lunch I noticed it was off.
- Try to turn phone back on and it is stuck at the samsung menu like everyone else.
- Soft and hard reset change nothing.
- Neither recovery nor download mode works using every key combo that I've seen suggested.
- Computer detects a device but "USB Device not recognized" and ADB can't see any devices (and I know it is set up correctly as I have the full SDK installed and known to be working).
- Charging still works fine and the battery is now at 100%
- Phone is NOT rooted and has no special apps or any recent changes to change the situation (not even app updates since a few weeks)
I'm not sure what else to do. I will probably let it sit for a few days without a battery, but otherwise I would open it up and see if there is some mechanical/electrical issue like a short or something somewhere. Pretty sure this is a software issue though. Any ideas?
Click to expand...
Click to collapse
To use ADB you must have USB debugging enabled in settings under Developer Options. If you don't keep this enabled all the time, and it wasn't set when the phone stopped working, then ADB is not an option.
Hopefully, you can get into download mode. For reference, here are the ways I know of, in case you haven't tried something here:
If you can get into download mode, you should flash the stock firmware and then perform a wipe data/factory reset from within stock recovery.
There are several ways to put the phone into download mode. You should try all of them that you can before you give up.
Recovery mode:
With the phone off (and not connected to the computer), and battery installed, hold all three buttons, vol- vol+ pwr continuously until the initial boot screen appears the second time.
Download mode:
1. With the phone off and connected to the computer via USB cable, and battery installed, hold all three buttons, vol- vol+ pwr.
2. With the phone off and battery installed, hold vol- and vol+ (but not pwr) while plugging in the USB cable.
3. With the phone off and battery installed, hold vol- (but not vol+ or pwr) while plugging in the USB cable.
4. Attempt each of the above three options with the battery removed from the phone. The computer will supply the power to the phone.
5. Use Android Debug Bridge (adb) which will only work if USB debugging has been already turned on in Developer Options, since you can't boot into the system to turn it on. With the battery installed and the phone connected to the pc via USB cable, use the command "adb reboot download".
6. Use a USB jig. With the battery installed insert the USB jig into the USB connector of the phone. Some have reported that this method works when no other method would work.
creepyncrawly said:
To use ADB you must have USB debugging enabled in settings under Developer Options. If you don't keep this enabled all the time, and it wasn't set when the phone stopped working, then ADB is not an option.
Hopefully, you can get into download mode. For reference, here are the ways I know of, in case you haven't tried something here:
If you can get into download mode, you should flash the stock firmware and then perform a wipe data/factory reset from within stock recovery.
There are several ways to put the phone into download mode. You should try all of them that you can before you give up.
Recovery mode:
With the phone off (and not connected to the computer), and battery installed, hold all three buttons, vol- vol+ pwr continuously until the initial boot screen appears the second time.
Download mode:
1. With the phone off and connected to the computer via USB cable, and battery installed, hold all three buttons, vol- vol+ pwr.
2. With the phone off and battery installed, hold vol- and vol+ (but not pwr) while plugging in the USB cable.
3. With the phone off and battery installed, hold vol- (but not vol+ or pwr) while plugging in the USB cable.
4. Attempt each of the above three options with the battery removed from the phone. The computer will supply the power to the phone.
5. Use Android Debug Bridge (adb) which will only work if USB debugging has been already turned on in Developer Options, since you can't boot into the system to turn it on. With the battery installed and the phone connected to the pc via USB cable, use the command "adb reboot download".
6. Use a USB jig. With the battery installed insert the USB jig into the USB connector of the phone. Some have reported that this method works when no other method would work.
Click to expand...
Click to collapse
Thanks a ton for the reply. Recovery mode does not work but using your methods I AM able to get it to boot to download mode. If it matters, USB debugging was and should still be enabled.
Now the question is... is there any way to backup the phone from this state or get into a state where I could back it up? I don't really care about my pictures or anything else as those were recently backed up but some app settings would be nice to save (Clash of Clans village without Google+, ugh). I'm going to do more research on the next step myself but if you have any suggestions or information to point me in the right direction I would of course appreciate that as well. Thanks for getting me this far though!
BrockSamsonFW said:
Thanks a ton for the reply. Recovery mode does not work but using your methods I AM able to get it to boot to download mode. If it matters, USB debugging was and should still be enabled.
Now the question is... is there any way to backup the phone from this state or get into a state where I could back it up? I don't really care about my pictures or anything else as those were recently backed up but some app settings would be nice to save (Clash of Clans village without Google+, ugh). I'm going to do more research on the next step myself but if you have any suggestions or information to point me in the right direction I would of course appreciate that as well. Thanks for getting me this far though!
Click to expand...
Click to collapse
It's pretty difficult to recover information from the data partition when the phone is in a state such as you describe. Maybe the developers and technogeeks can do it. I can't. However, depending on where the game saves it's game data, you may be fine. If the game data is saved to the USB memory (internal sd card) then it will still be there once you flash new firmware. Your pictures should also be fine, since they are on the sdcard.
Well a friend of mine has flashed the Jellybean ROM onto his prime and now it wont boot into the OS. It can boot into CWM and bootloader. However when connecting to a computer it shows up as unknown (I've tried intstalling both ASUS and Universal naked drivers with the same result) no matter what mode it is in (fastboot, APX or recovery). So I can't use adb and it's an old CWM version that doesn't support an external SD. I have tried different computers and a different cable without success, also for it to be recognized by a computer the cable connecting to the primes port needs to be bent to a certain position, though I am not sure if this matters. So is this prime bricked or is there still hope?
JJ2197 said:
Well a friend of mine has flashed the Jellybean ROM onto his prime and now it wont boot into the OS. It can boot into CWM and bootloader. However when connecting to a computer it shows up as unknown (I've tried intstalling both ASUS and Universal naked drivers with the same result) no matter what mode it is in (fastboot, APX or recovery). So I can't use adb and it's an old CWM version that doesn't support an external SD. I have tried different computers and a different cable without success, also for it to be recognized by a computer the cable connecting to the primes port needs to be bent to a certain position, though I am not sure if this matters. So is this prime bricked or is there still hope?
Click to expand...
Click to collapse
It is not bricked. I'm still not convinced you are on jellybean bootloader as there is not a version of Cwm that works with it and you still have cwm.
First thing you need to do is confirm what bootloader you are on before you really brick it.
Switch the machine on and look where the tegra logo is. If it is bottom center you are still on ICS bootloader and if it is bottom right it is jellybean bootloader.
We need to know this to point you to the correct version of twrp to flash to start.
Yeah, the logo is still bottom center. But can I flash TWRP on with it saying Unknown Device when connecting to a computer as I know I can't use such things as adb and fastboot commands until it is recognized?
JJ2197 said:
Yeah, the logo is still bottom center. But can I flash TWRP on with it saying Unknown Device when connecting to a computer as I know I can't use such things as adb and fastboot commands until it is recognized?
Click to expand...
Click to collapse
Really you are going to need to get into fastboot and get the drivers installed.
I'm guessing you know how to get into fastboot but if you don't then hold down volume down and power button for 10 seconds when off. When the icons appear press volume down to go over to the USB icon and then press volume up. It will freeze on the prime screen at this point and that is fastboot mode.
Now go into device manager and try to install naked drivers. If this does not work then try in on another pc. If this still does not work then you have a faulty cable. A faulty cable can still charge the tablet but will not work in pc.
At this moment my money is on your cable being faulty over something you said earlier about having to play with it. You can buy a replacement cheaply on eBay.
Well at first I couldn't get the prime to be recognized by any PC so I got a replacement and that cable didn't work either. However the cable was stuck, so I had tried pulling it in different directions and then all of a sudden the PC had recognized it. This also worked for the other cable, figuring me to believe there is something wrong with the pins on the primes port. Anyways I've tried installing drivers, ASUS did nothing and the naked drivers would tell me the drivers were either not for the device or not 64 bit compatible. I've tried in fastboot, recovery and APX with the same result.
JJ2197 said:
Well at first I couldn't get the prime to be recognized by any PC so I got a replacement and that cable didn't work either. However the cable was stuck, so I had tried pulling it in different directions and then all of a sudden the PC had recognized it. This also worked for the other cable, figuring me to believe there is something wrong with the pins on the primes port. Anyways I've tried installing drivers, ASUS did nothing and the naked drivers would tell me the drivers were either not for the device or not 64 bit compatible. I've tried in fastboot, recovery and APX with the same result.
Click to expand...
Click to collapse
Without getting any drivers installed at all there is not much we can do.
Cwm doesn't support external cards and even tho I could make you a flashable zip to install twrp you couldn't get it on there.
If you can get back into the machine at all then we could use wireless adb and send the files over that way or use es file explorer to access network shares and take them over.
So it is pretty much as I had feared even though I can turn it on and boot into Recovery, fastboot and APX without being able to use adb commands it is as good as bricked. I'm still wondering as to why I can't seem to install the drivers, does the device think it is something else?
JJ2197 said:
So it is pretty much as I had feared even though I can turn it on and boot into Recovery, fastboot and APX without being able to use adb commands it is as good as bricked. I'm still wondering as to why I can't seem to install the drivers, does the device think it is something else?
Click to expand...
Click to collapse
This normally happens with a faulty cable and as you said you think the pins are faulty so it could be that instead.
You could try going to the wipe icon where the fastboot icon is and try running that. If there is a rom still on there it will try to factory reset but I can't guarantee that will work but at this point you have nothing to lose.
I've done a factory reset clear delvic and regular cache, wipe user data etc in CWM already.
JJ2197 said:
I've done a factory reset clear delvic and regular cache, wipe user data etc in CWM already.
Click to expand...
Click to collapse
I'm not talking about in CWM. I'm talking about the wipe icon where the fastboot icon is also.
Isn't the factory reset the same in both CWM and bootloader?
JJ2197 said:
Isn't the factory reset the same in both CWM and bootloader?
Click to expand...
Click to collapse
No
Hmm, really. What does bootloader change the CWM doesn't or do you just know it's not the same?
JJ2197 said:
Hmm, really. What does bootloader change the CWM doesn't or do you just know it's not the same?
Click to expand...
Click to collapse
It reformats the partitions back to stock except the system partition.
I'm not saying this is going to work for you. Just as you are your only other option if the pins are broke is to get it sent back to asus and they will swap out the whole mobo so you might as well have a go.
Hi,
My Z Ultra's screen is cracked and i would like to use it for my TV as a Android-Box replacement, because it's actually still usable i think. Now my Problem isn't finding a suitable Rom(i think) or general knowsledge about rooting.
I think i got all the needed tools like a microsoft bluetooth keyboard with touchpad(regular usb mouse and keyboard too if needed), a MHL/USB(all-in-one) OTG adapter, HDMI cable and the universal USB micro to usb adaptercable.
SO my questions are:
1) Can i root without actived USB Debugging? (i can't activate it due to the cracked screen) ...Most important!
2) Is Towelroot still good? Or are there other easy root methods for newbs?
Thanks for reading any maybe helping
Talentfree said:
Hi,
My Z Ultra's screen is cracked and i would like to use it for my TV as a Andriod-Box replacement, because it's actually still usable i think. Now my Problem isn't finding a suitable Rom(i think), general knowsledge about rooting.
I think i got all the needed tools like a microsoft bluetooth keyboard with touchpad(regular usb mouse and keyboard too if needed), a MHL/USB(all-in-one) OTG adapter, HDMI cable and the universal USB micro to usb adaptercable.
SO my questions are:
1) Can i root without actived USB Debugging? (i can't activate it due to the cracked screen) ...Most important!
2) Is Towelroot still good? Or are there other easy root methods for newbs?
3) anything else i might have forgotten?
4) i think that a Sony Companion free system is usefull for Flashtool or am i wrong?
Thanks for reading any maybe helping
Click to expand...
Click to collapse
Have you tried using the USB mouse with the OTG adapter?
I.assume you have seen this guide. http://forum.xda-developers.com/xpe...de-cracked-screen-beast-life-tv-xbmc-t2907921
i just tried, didn't work
...and yes i tried some of it, but usb debuggin not being ebabled seems to be my problem. I will try that script asap
Talentfree said:
i just tried, didn't work
...and yes i tried some of it, but usb debuggin not being ebabled seems to be my problem. I will try that script asap
Click to expand...
Click to collapse
I am testing now and mouse works fine with developer options and USB debugging turned off.
Does your phones screen display? I also reread your first post ", a MHL/USB(all-in-one) OTG adapter," the OTG cord I have is just a male micro and female full size USB.
Yes the screen seems to display. i tried it with the z ultra and oneplus one, both didn't respond to a mouse(two different tested with two different otg cables). I still got the S4, will try that on it too later.
Basically you plug it in and you see a mouse cursor or what? i clicked around, but nothing...
Also on my Z Ultra the widget on the screen seems to jump around, just like the stars that move when you touch the screen usually if you get what i mean.
Talentfree said:
Yes the screen seems to display. i tried it with the z ultra and oneplus one, both didn't respond to a mouse(two different tested with two different otg cables). I still got the S4, will try that on it too later.
Basically you plug it in and you see a mouse cursor or what? i clicked around, but nothing...
Also on my Z Ultra the widget on the screen seems to jump around, just like the stars that move when you touch the screen usually if you get what i mean.
Click to expand...
Click to collapse
Yes I see a cursor (even on the lockscreen) and it does give the shooting stars effect when swiped. Needed to hold down left mouse button when swiping and then release.
my shooting stars "cursor" seems to either jump around or not appear at all, but nothing happens.
Does anything pop up on the top down menu or does it play sound when connected?
Would this from this thread work on the XZU too, due to it being android based?
Reset Nexus into recovery mode (power & volume down)
2. Connect to PC via USB. Install the USB driver from the SDK so that it appears as an ADB device
3. Fire up the updated toolkit. You should see the nexus as a fast boot device
4. Unlock bootloader
5. Using option 10 on the toolkit load up CWM on the phone. This gives you ADB access so can you pull files off the device via ADB although I could access the SD card through programs like Droid explorer.
6. If you want to carry on further and get into Android properly, you'll need to wipe the cache from within CWM
7. Reboot and hold down the volume key to get back into recovery
8. In the toolkit select root options (option 4) and load temporary image (6) If it hangs on the google or nexus logo you've not wiped the cache.
9. With this second phone I couldn't access it through droid explorer as it was popping up as an MTP device but I could pull the files via command prompt or through the toolkit
10. If you have any use of the touchscreen at all you can run the following command which will then mean that any touch will unlock the device
adb shell rm /data/system/gesture.key
11. You can activate bluetooth via adb if you have a mouse or keyboard available but you will need to be able to press okay on the screen
12. Any changes you make in the unstable android image such as lockscreen, bluetooth, enabling debugging, etc will remain in place when you restart the device.
13. You can relock the bootloader if you wish via the toolkit. You just need to be in recovery mode first.
Talentfree said:
Would this from this thread work on the XZU too, due to it being android based?
Reset Nexus into recovery mode (power & volume down)
2. Connect to PC via USB. Install the USB driver from the SDK so that it appears as an ADB device
3. Fire up the updated toolkit. You should see the nexus as a fast boot device
4. Unlock bootloader
5. Using option 10 on the toolkit load up CWM on the phone. This gives you ADB access so can you pull files off the device via ADB although I could access the SD card through programs like Droid explorer.
6. If you want to carry on further and get into Android properly, you'll need to wipe the cache from within CWM
7. Reboot and hold down the volume key to get back into recovery
8. In the toolkit select root options (option 4) and load temporary image (6) If it hangs on the google or nexus logo you've not wiped the cache.
9. With this second phone I couldn't access it through droid explorer as it was popping up as an MTP device but I could pull the files via command prompt or through the toolkit
10. If you have any use of the touchscreen at all you can run the following command which will then mean that any touch will unlock the device
adb shell rm /data/system/gesture.key
11. You can activate bluetooth via adb if you have a mouse or keyboard available but you will need to be able to press okay on the screen
12. Any changes you make in the unstable android image such as lockscreen, bluetooth, enabling debugging, etc will remain in place when you restart the device.
13. You can relock the bootloader if you wish via the toolkit. You just need to be in recovery mode first.
Click to expand...
Click to collapse
I have no idea if any of that would work, to me it sound like a lot of it would only apply to Nexus. I checked and the only indication I have that mouse is connected is the scroll wheel lights up. I had three apps that I thought may remotely effect mouse so I uninstalled and rebooted and it still works. I also looked through all the settings menus and can't see anything there.
Is there an app mybe, that would set USB Debugging automatically to enabled just by installing it? I can load apps from playstore to the device
Or do fastboot or recovery mode provide USB debugging enabled?
Talentfree said:
Is there an app mybe, that would set USB Debugging automatically to enabled just by installing it? I can load apps from playstore to the device
Or do fastboot or recovery mode provide USB debugging enabled?
Click to expand...
Click to collapse
I found this......
https://play.google.com/store/apps/details?id=com.vmlite.vncserver
adfurgerson said:
I found this......
https://play.google.com/store/apps/details?id=com.vmlite.vncserver
Click to expand...
Click to collapse
oh man 9eur for trial and error -_- guess i have too :/
Talentfree said:
oh man 9eur for trial and error -_- guess i have too :/
Click to expand...
Click to collapse
Or try another mouse, or something because I was able to control via mouse. Here in the states we have a two hour window for refunds, but it is already late here and I should be sleeping or I would offer to test. Here is a YouTube video that shows it working the way it works for me.
http://youtu.be/W8HVEHNOy7I
bought it, but it still needs usb debugging enabled in order to function -_-
thx at least now i know how it SHOULD work :laugh:
it seems i can't use adb driver because this once again needs some android setting enabled.
weird thing is right now that i somehow got into some menu beyond the lockscreen, but still cant do anything :crying:
so close, but so far at the same time
I'm about to buy a fire tv or some other android box and throw the XZU away as it seems its useless in this state without zsb debugging
Talentfree said:
thx at least now i know how it SHOULD work :laugh:
it seems i can't use adb driver because this once again needs some android setting enabled.
weird thing is right now that i somehow got into some menu beyond the lockscreen, but still cant do anything :crying:
so close, but so far at the same time
Click to expand...
Click to collapse
Talentfree said:
I'm about to buy a fire tv or some other android box and throw the XZU away as it seems its useless in this state without zsb debugging
Click to expand...
Click to collapse
I am 99% sure that OTG mouse should work without USB debugging enabled.
adfurgerson said:
I am 99% sure that OTG mouse should work without USB debugging enabled.
Click to expand...
Click to collapse
I'll tell you more, it works without any problem at all. I am using it
i bought another otg cable, gonna try it later. hopefully it finally works
Talentfree said:
i bought another otg cable, gonna try it later. hopefully it finally works
Click to expand...
Click to collapse
How old is your Z Ultra? The reason I ask is people have reported very mixed results as to getting screens replaced under warranty. I think I even recall someone who wasn't the original purchaser getting a screen replaced for no charge.
Hi,
on my P9000 the glass is broken (display working but no touch).
So i want to sell it as it is and do a factory reset - the problem is i can not boot in recovery. When i boot with volume up + power the white elephone logo appears then nothing happens for a while (much much longer than with a normal boot) and then it continues with the normal boot.
The recovery is TWRP.
The volume up button does work as i can see when it is booted, the power button obviously works too.
Can i trigger the reset via USB or do you have any idea how to boot the recovery?
sundawn said:
Can i trigger the reset via USB or do you have any idea how to boot the recovery?
Click to expand...
Click to collapse
I think you can. But you need "Developer Options" to be turned on for this.
Connect your phone via usb
open a command line
type in
Code:
adb reboot recovery
You should boot into recovery.
...My phone has also a broken display, so I ordered a USB-C otg adapter. I hope I can connect my mouse to the phone and so save my most important data and activate usb mounting.
I think dev options shoulb be on.
But i only get this message: (deleting .android folder does not help and as it is broken i cant check for that confirmation)
C:\>adb reboot recovery
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device unauthorized.
This adbd's $ADB_VENDOR_KEYS is not set; try 'adb kill-server' if that seems wrong.
Otherwise check for a confirmation dialog on your device.
Kooperativ said:
...My phone has also a broken display, so I ordered a USB-C otg adapter. I hope I can connect my mouse to the phone and so save my most important data and activate usb mounting.
Click to expand...
Click to collapse
Did this work? As i can not confirm the adb access without Touch this might be a solution for me too.
I am just wondering if a OTG connection would require a confirmation via touch too...
sundawn said:
Did this work? As i can not confirm the adb access without Touch this might be a solution for me too.
I am just wondering if a OTG connection would require a confirmation via touch too...
Click to expand...
Click to collapse
Sorry, I was so happy with my result that I forgot to write this post ^^.
So yes, connecting a mouse with otg works great! (I took this one, but every other should work fine too)
If your phone does not mount the mouse restart your phone and you should be fine.
I was able to run my backup tasks and transfer them to my new phone!
I already ordered extactly the same one
Thank you - the idea with a mouse never crossed my mind...
Hi all,
I wonder if somebody could help me.
At the moment I have a Z5 compact with a broken screen (totally black) and touch. I know it still can boot, because it responds to my fingerprint when booted up. However, it does respond to my finger, but still needs a patern on first boot, which I cannot do on account of the broken touch screen. Also, my computer detects the phone.
I want to access my data, but for that I would have to use the onscreen menu which pops up when I connect the phone with usb. That's impossible.
I looked around on the internet and it is possible to remotely control the screen or access via adb. However, for that I either need to install some app on the phone, enable usb-debugging or authorise access via adb. All of those are impossible.
My phone has un unlocked bootloader and is rooted, so as a last resort I've tried to flash a modified kernel to enable usb debugging by default. This fails. Probably because I make some mistake in modifying the kernel, but I don't know. There's not a lot of response from my phone, as you understand ... Besides, I've absolutely no experience modding myself.
Anybody any idea, please?
So I just fixed the same issue you're having this week. It required opening up the phone.
Basically the ribbon cable that connects the screen to the motherboard had become unseated and needed to be plugged back in for me.
The Z5C isn't the easiest phone to take apart but it's not that difficult either. Just requires some basic tools (Hair dryer, tweezers and some precision screw drivers). There's a bunch of videos showing you how on ifixit or youtube. You just have to go all the way to the part where they flip over the motherboard and unplug the two ribbon cables, one of those two will be the culprit.
This is the first and only phone I've taken apart so any amateur can do this.
Boot to recovery and connect your phone to PC
Nutchos said:
So I just fixed the same issue you're having this week. It required opening up the phone.
Basically the ribbon cable that connects the screen to the motherboard had become unseated and needed to be plugged back in for me.
Click to expand...
Click to collapse
Yes, actually I've had problems with a broken backlight before and opening the phone and re-adjusting the cable solved that. Not in this case however. Thanks for your suggestion, anyways.
mlleemiles said:
Boot to recovery and connect your phone to PC
Click to expand...
Click to collapse
Would recovery provide me with some way to enter my pattern via a PC, e.g. with ADB?
Actually, I'm not sure I had any recovery installed at all. I've tried this before and just tried it again. I press the on/off-button while holding volume down. After that no response whatsoever. My computer does not see any device when connected. I suppose my recovery does not work properly, but without screen I can't be certain.
mlleemiles, you are a _hero_!
After reading your post I decided to try flashing another recovery to try if that might work. Now I can access my files without ever having entered any pattern .
Nevermind that it turns out my files weren't encrypted and I thought they were.
If anyone has a similar problem in the future, this is what worked for me:
My exact situation:
- My phone runs a stock rom (downloaded from XperiCheck) with version 32.4.A.1.54. When my phone was still running ok I had the bootloader unlocked and my device rooted with Rootkernel.
Working solution:
- I downloaded Twrp, version 3.2.1, from this page:
https://forum.xda-developers.com/z5-compact/development/twrp-twrp-3-2-1-z5-compact-t3748952
- Shut down my phone by disconnecting the battery and reconnecting it again
- Started my phone in fastboot mode and flashed recovery to my phone with:
Code:
fastboot flash recovery recovery_suzuran_220218_2.img
- Booted my phone in recovery with volume down + on/off-button.
- Connected my phone to my PC, et voila.
Turns out I can also access my phone with ADB as root, so after backing up the entire internal memory, I might try to get some remote screen tool working.
So thanks for the help and if I find something interesting and new, I'll post that too.
Small update:
After successfully flashing Twrp I backed up the internal memory, so must of the important stuff was safe by then.
However, it turned out that my phone now wouldn't boot into anything other then Twrp. I decided to flash my rom again. First I installed my apb keys using Twrp:
Code:
adb push adbkey.pub /data/misc/adb/adb_keys
It turned out I already had usb debugging enabled.
I then flashed my original firmware again, and connected with adb. This time it connected correctly, without me having to click any dialogue on my phone. I fiddled with several remote control Android tools most of which didn't work. Finally, it turned out Vysor does exactly what I want to do. It is a bit unstable, but workable.
Anyways, I've finally managed to copy all the stuff I wanted from my phone.