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 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.
I've faced this problem several times, many people don't like to lose their data, in most of the cases, I use tools such as miraclebox, but besides of this one, what other options do I have to, for example, remove the password/pin of a non rooted phone without usb debbuging enabled?
All I want to do is get in the phone without losing data.
go to setting then about then software touch on build 10 times or so. go back to settings developer options should now be visible. usb debugging should be seen here just tick it on. edit sorry didnt realize it was locked nor read fully
toolhas4degrees said:
go to setting then about then software touch on build 10 times or so. go back to settings developer options should now be visible. usb debugging should be seen here just tick it on. edit sorry didnt realize it was locked nor read fully
Click to expand...
Click to collapse
Having no access to the phone, because it is locked by password.. In some cases, I can get into fastboot mode, but i dont know if theres a way to activate usb debugging through fastboot :/
WilliamWash said:
Having no access to the phone, because it is locked by password.. In some cases, I can get into fastboot mode, but i dont know if theres a way to activate usb debugging through fastboot :/
Click to expand...
Click to collapse
found this, its old but temp bootloader maybe https://forum.xda-developers.com/showpost.php?p=38900978&postcount=5
I have a Verizon SCH-I435 gx4 mini and I forgot my pin. Android device manager can't help me put it into lost mode and over ride screen lock. The interesting part is when I boot into recovery and go to factory data restore as a last option it says it's in display mode (MTM). The phone boots into Odin mode just fine. On all my phone I always turn on USB debugging which I believe if you have a pc you need to enable to use Odin correct me if I'm wrong. So if there's a way to keep my files safe and use my phone again it would be appreciated.
pk198 said:
I have a Verizon SCH-I435 gx4 mini and I forgot my pin. Android device manager can't help me put it into lost mode and over ride screen lock. The interesting part is when I boot into recovery and go to factory data restore as a last option it says it's in display mode (MTM). The phone boots into Odin mode just fine. On all my phone I always turn on USB debugging which I believe if you have a pc you need to enable to use Odin correct me if I'm wrong. So if there's a way to keep my files safe and use my phone again it would be appreciated.
Click to expand...
Click to collapse
Let's make Points
1-Odin Doesn't require any USB-Authentication such as Debugging Enabled
2-Only adb Requires Debugging
3-Great Thing you enabled it.
Now you can Apply two ways.
One you can boot into recovery and go into adb.Now on PC install adb and connect it to your phone(Go read a Tuto or watch a Video on how to do it)Now remove the locksettings.db file from /data partition(Use google to find the exact location)
Or you can pull the locksetting.db copy to your PC and crack the code using hashcat.But I recommend the first one.Next Time be cautious and if you don't know how to delete files using adb go read how to.
Sent from my Pixel 3 XL using Tapatalk
Hi,
i broke the Display of my ZTE Axon 7 mini on stock ROM and without USB debugging enabled. No custom recovery or anything done to the device. The touch interface of the screen is at least partially functioning, i'm able to boot it, unlock it by guessing where to draw the pattern (i know bc the fingerprint sensor is working afterwards) and power off as well by clicking on the spot where the button should be. I've read some threats about tools to access your phone with broken screens, but nothing worked. Thing is, i think i set the usb-setting to "charge only" when connected to my pc. So the device won't be recognizedwith adb fastboot. Which means i cannot use the method described here for instance.
So does anybody know how i could change the settings or get at the data generally? I'd be really glad if someone could help.
cheerio