Hello all,
Here is my situation:
- I have my brother's Nexus 4.
- The screen no longer responds to touch, though it still displays correctly when it is turned on.
- It has PIN security
- It is running stock KitKat 4.4.4.
- It is not rooted.
- USB Debugging (ADB) is not enabled.
- Stock recovery is installed.
- The bootloader is locked.
I would like to be able to back up the contents of the phone, but the state it is in renders that difficult. Here are the different options I've considered and discarded:
- Connect the phone via USB to copy the contents of the SD Card
# Impossible since the phone will not mount USB storage (might be a security feature since it has PIN enabled?)
- USB OTG mouse to bypass using the touchscreen
# OTG support is not available on stock kernels for the N4
- Bluetooth mouse
# No way to enable Bluetooth
- Use Android Control to control the phone via my PC
# No ADB; no way to enable ADB; unlocking bootloader to install a recovery with ADB enabled would wipe the phone.
The only option that might work that I have yet to attempt is to replace the screen. However, based on research I did while trying to troubleshoot my own Nexus 4, this could be a costly waste of time. The Nexus 4 has a history of having faulty touchscreens. Case in point, both my phone and my brother's phone suffered from this same flaw. This might be because the touchscreen controller is bad on the N4's motherboard. I junked my N4 specifically for this reason.
I'm beginning to think that there is no way for me to recover the data on this phone. Does anyone know of a way I could get the data off of it? Any way to enable ADB via Fastboot or Recovery? Any way to flash an ADB-enabled kernel via ADB sideload? Any way to unlock the bootloader without wiping all the data? Any way to run a backup of the whole phone?
Please help! Thank you in advance!
You might try towelroot to root. Then bootunlocker from the play store to unlock but you'd have to be able to use the touch screen. Long and short, you're kind of screwed
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
You might try towelroot to root. Then bootunlocker from the play store to unlock but you'd have to be able to use the touch screen. Long and short, you're kind of screwed
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Yup, that's pretty much what I thought. I was hoping someone here could think of something I hadn't thought of yet. Basically, I think the only two avenues I have to send anything to the phone are via the Bootloader (Fastboot) or via ADB sideload in Recovery. I was hoping I could find something to save me there, but it is looking unlikely.
Related
Alright... I am having a bit of an issue... looking for interesting solutions.
Have a replacement MT4G with stock 2.3.4. I am trying to downgrade to Froyo so I can root it.
Unfortunately, my usb cable must not be working. It starts charging when I plug it into the PC, but Windows won't recognize it (I have tried different ports, and double checked drivers...). When I had my first Mt4G, if I needed to use ADB, I used a market app that allowed me to connect to ADB using Wifi. It has some limitations, but it is a good substitute if needed.
But those Wireless ADB apps only work with Root (at least the ones I found), and well, obviously that was the goal all along... so I am thinking temporary root... but didn't think there was a temp root...
Question: does anyone know of a way to access ADB wirelessly without root, or know of a way to gain temp root via terminal emulator so I could then connect via the wifi ADB app and be able to complete downgrade/permroot?.... or are there any suggestions for what I could do to get the USB working?.....anything would be appreciated.
I can use the SD card with my laptop.. so downloading/getting files on the phone's SD card is not a problem... just access to ADB is a problem.
PS: Since the USB cable still functions as a charger (if that is actually the problem), I am trying to avoid spend $40 for the replacement.... since I would really only need it once.
Did you try TrueBlue_Drew thread about adb/fastboot set up ?
Sent from my HTC Glacier using XDA App
If you need to gain root access, there are other methods than the regular ADB .
Refer this post to find way that suits you.
http://forum.xda-developers.com/showthread.php?t=834225
If you need Wireless ADB, refer to this post.
Thank you both.... question however...
2kwic25: I checked the trueblue thread, and this seems to be a method for rooting which does not require the full sdk. However, it still uses the usb cable to connect to the phone. I am trying to gain temp root either through the emulator alone, or using adb (which is already installed on my pc) via wifi, but without having any su or root permissions as I don't have them and that is what I am trying to achieve ultimately.
febycb I read/scanned the link on rooting.... I went through to the end of it, and it doesn't seem to apply to the gingerbread 2.3.4 stock. This is what is on my phone now. I have a brand new phone, everything is factory locked, no root, s=on, etc.. The one post I found originally which seems to be the route most are using is to gain temproot, then downgrade to Froyo.... THEN attempt rooting to get a real permroot with s=off. So, in order to downgrade, I need to connect via USB, and use adb initially. But my USB does not work, so I am left with trying to connect via wifi. However, the thread on using adb over wifi seems to say that while you may not need to use su when running the necessary commands in the emulator, your device must still be rooted. So I cannot seem to figure out how to do this trying to use adb over wifi to get root, yet you need root to use adb over wifi.
Lastly, while I did note that your first link says only updated devices, I believe they are talking about the update to Froyo.
I guess this is the one main question I have:
Does anyone know -- or has anyone heard or read about -- a method to get temporary root on a MT4G with stock Gingerbread 2.3.4 using only the emulator???
Thanks... I am going crazy without root, and as said, I really want to avoid (as I am on a tight budget) purchasing another usb cable for $40, just to get a temp root.
I will try to sort out the issue as simple as i can
1. There is no method right now to root the 2.3.4 upgrade (even temproot).
2. To enjoy root access, you need to downgrade to Froyo (stock 2.2.1)
3. Do Permroot and then upgrade to GingerBread 2.3.4 or 2.3.5
4. Every post related to rooting is based on the stock Froyo Rom.
To downgrade, follow this post. Select the option best suited to you.
Also don't spent $40 for an OEM data cable. A replacement cable is available at price tag as low as $0.99
Just go to ebay & search for "micro usb cable". Just go through this link.
Have you installed the "HTC_drivers" file that comes on the root of the sdcard?
Possibly the reason why windows doesn't see it.
Or Make sure "USB Debugging" is enabled..
Not saying you haven't done either. Just putting it out there.
Sent from my HTC Glacier using xda premium
Thanks mahato... But yes. I have loaded the htc drivers, htc sync, pdanet.... All of them. Plus, I know all about usb debugging and it is on.
I have had it with this problem. The other thing that drives me crazy about my issue (which is why my phone was replaced in the first place, is that wifi calling keeps dropping), is that in my comprehensive research, I read one person's post that said that they confirmed that their 911 address needed to be filled out. Will I have done this and have done it through tmo. But I don't know if this was the problem, because I STILL KEEP GETTING THE DIALOG BOX which instructs me to complete my 911 address.
One more thing, since I need a cable to root this (which I know I can order cheaply), I might try to get a free usb cable from tmo...
But, before, I acquiesce to these problems and accept a new phone and just deal with it...
Can someone tell me how to confirm whether I have the ”bad chip” or ” bad screen”? I put a new screen protector on the new phone, and I thought that might be it, but I don't think so. My usual wall paper is the beautiful widgets living wallpaper which shows the blowing grass, etc.
However, when I look at my phone at an angle, the screen turns lighter, with practically zero contrast. I had read somewhere that this is a symptom, although I may be paranoid considering everything....
So does anyone know how to confirm a ” bad screen” or a ”bad chip” (I didn't even know there was a bad chip). Is there something I can check in the bootloader screen or something like that to confirm a component part number?
Sent from my HTC Glacier using xda premium
Reposted to new thread.
Ok, there are a lot of wrong statements in this thread and I don't have any time to cover them all.
Temp-rooting 2.3.4 requires running fre3vo. That's the only currently existing method.
fre3vo runs by exploiting msm_rotator.
I believe it's not documented whether the exploit absolutely requires link through ADB.
So, you could just try and see for yourself. In the worst case you'll discover that the temp root shell is given only to ADB and not to emulator.
I cracked my screen and want to copy things to my computer but I cant get past the lock screen. How do I bypass it? btw I cant used adb because usb debugging isn't turned on and the phone isn't rooted.
Sorry man, you're screwed. There is no way to bypass lockscreen.apk and go to launcher.apk without actually unlocking (AFAIK, don't quote me on it). Most stuff gets backed up by the google servers by default.
Sent from my iPad using Tapatalk
There is a method to do it with ADB, but not without: http://forum.xda-developers.com/showthread.php?t=1800799
If your bootloader is unlocked then you can install custom recovery and use command lines to back it up. But if its not, if you try to unlock it will wipe your entire device in the process.
If the data is valuable enough, ie naked pics, you could buy a new screen replacement.
I'm in a bit of a hard place - I'd previously unlocked, loaded TWRP and rooted my Gen1 Nexus 7. I can no longer boot into recovery and get the " no command" message. This also gets in the way of the KitKat upgrade process. With all that said, the tablet works fine under 4.3 stock.
Here's the rub - one morning stumbling out of bed I stepped into a loop of USB cable that was charging the Nexus, yanked the cable and tablet violently enough to damage the USB port. Data communications or charging no longer work via USB. Fortunately I can still charge via dock and pogo pins.
Besides buying a new tablet or replacing the ports (about $60 on eBay) can anyone suggest another method to recover or load a bootloader?
Sent from my Nexus 7 using Tapatalk 4
Pretty sure you mean recovery, not bootloader.
The OS still works right? Just flash a recovery using an app like flashify and you're good to go.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Not sure what flashing a bootloader has to do with this.
If your bootloader is locked, you can't "flash an unlocked one"*, but even if you could, that wouldn't help as you still would not have use of fastboot via the USB to do a "fastboot flash of a recovery". And fastboot only speaks to the tablet when the bootloader is running, not when a kernel is loaded (recovery or regular boot).
To get a custom recovery re-installed, you can do that by using "dd" to overwrite the recovery partition from ANY root-privileged shell (either a custom recovery or a rooted ROM). So there's the rub: you need something running with root privilege.
If that is not the case (rooted ROM) you need to either find a "root exploit" for your current ROM, or get your USB plug repaired. You could run ADB over your WiFi network (instead of via the USB cable) or just use a terminal emulator app to run exploit codes.
I haven't been keeping up with things, but the "motochopper" exploit was exactly that - a method of rooting a stock ROM that avoids fooling with fastboot or the lock state of the bootloader. But that was a while ago, and I don't know whether it still works against newer stock ROMs. (Besides, you neglected to even mention what is currently on your tablet)
Good luck.
*actually you can, but only if you have a rooted ROM or custom recovery running AND you previously captured a raw dump of a certain partition while the bootloader was in an unlocked state (bootloader is encrypted on a per-tablet basis). I think osm0sis disclosed this method a long long time ago.
I apologize for my probable misuse of terms - in short (unless I can find a root exploit) a new Nexus 7 may be on my XMas list. I greatly appreciate your input.
Sent from my Nexus 7 using Tapatalk 4
My Nexus 7 (2012), with broken usb port, lost root while updating but the bootloader is still unlocked. Also, I have no recovery on it and have been unable to flash a new one so far.
Is there any way to salvage root via terminal or am I SOL? I've searched the forum but haven't been able to find anything that specifically applies to my situation. Help?
P.S. I'm charging it via the dock, thanks for asking
ndhusn said:
My Nexus 7 (2012), with broken usb port, lost root while updating but the bootloader is still unlocked. Also, I have no recovery on it and have been unable to flash a new one so far.
Is there any way to salvage root via terminal or am I SOL? I've searched the forum but haven't been able to find anything that specifically applies to my situation. Help?
P.S. I'm charging it via the dock, thanks for asking
Click to expand...
Click to collapse
I think you're SOL - Every which way I think about this... It always comes down to having a working USB connection.
Hi, ndhusn....
I've been thinking about your situation all day... and I can't think of anything that would work.
The "traditional" way of rooting the Nexus 7 is...
** fastboot flash a custom Recovery (CWM or TWRP)...
** Using that Custom Recovery, flash Chainfire's SuperSU root package.
But with a knackered USB port, you obviously can't fastboot flash anything.
Looking into alternative options... there is something called CF-autoroot...
http://autoroot.chainfire.eu
http://forum.xda-developers.com/showthread.php?t=2025272
I've never used this means of rooting myself... but it has been mentioned several times on this forum. It's chief advantage, it seems, is it doesn't require the fastboot flashing of a Custom Recovery first.... so I thought this might work for you. But upon closer examination, it appears you still have to hook up your Nexus 7 to a PC via USB in order to run it.
--------------------------------------
Without CWM or TWRP installed, I can't think of any way of rooting your Nexus 7.
The irony here is... that there IS A WAY of flashing a Custom Recovery without recourse to fastboot (and the need for a USB connection) using the Flashify app. But you need root to do it. You can even flash a Custom Recovery via a terminal shell, with...
Code:
$ su
# dd if=/sdcard/recovery-image-file.img of=/dev/block/platform/sdhci-tegra.3/by-name/SOS
...but as you can see from the initial su command, root already needs to be available.
You're stuck in a 'chicken and egg' situation! You can't root without a Custom Recovery... and you can't install a Custom Recovery without root.
--------------------------------------
Even a 'root exploit' requires a USB connection... like the old 'motochopper exploit' which would root the Nexus 7 even with a LOCKED bootloader. Anyway, that 'exploit' now no longer works, since Google 'blocked' such exploits as of Jellybean 4.3 onwards.
--------------------------------------
ndhusn said:
...I'm charging it via the dock, thanks for asking...
Click to expand...
Click to collapse
If the USB port is that damaged, such that you have to use the dock to charge, then presumably this precludes the possibility of trying another, different USB cable... with the intent of fastboot flashing TWRP or CWM.
Sometimes, it's just the USB cable at fault... and not the USB port itself. Anyway, just a thought.
--------------------------------------
I'm sorry to say, that without a working USB port on your Nexus 7, I don't think you'll be able to root it... or at least, I can't think of anyway of doing so.
Rgrds,
Ged.
*** Edit & addendum - WARNING ***
Whilst tinkering around with various methods in order to acquire root, will likely not hardbrick your Nexus 7... but they may cause softbrick/bootloop situations.
Normally, these are relatively trivial to resolve... but in your situation, they could be permanent.
Without a Nandroid backup created with a Custom Recovery, you won't be able to restore back to a previously known 'good' version of Android.
And without a working USB port, you won't be able to fastboot flash a Google factory image.
So... tread carefully.
Better a working Nexus 7 without root, then a Nexus 7 perpetually locked in a bootloop. It's unlikely, but be aware that you're recovery options are limited.
Needs be as needs must...
I have a broken port also! Low quality parts.
Cheapest replacement I have found is here....
http://www.asusparts.eu/Asus-08301-00522000
I know this doesn't answer your question but always good to have options.
Got a question that I am not sure has a proper answer (and yes I know this is a sus question to begin with).
I have an old s7 and I forgot the pattern to unlock it. Developer mode is enabled but since I can't get through the lock screen I can't whitelist my PC on the phone when I connect it. I need to access my google authenticator app because I want to export it to my new phone (use to have it on my new phone but for other reasons it got wiped). I've tried using the samsung service mode code to put it into service mode from the emergency call dialer but that doesn't work. Is there anything else I might be able to try?
use droidkit or drfone screen unlock? I think dr.fone has a free trial, maybe you can screen unlock with it. Or just look for any other 3rd party free screen unlocker. They usually don't need root, nor adb.
Ive tried both but both don't support the s7. At this point I would pay for one of these apps to get into this damned thing.
Is it's bootloader unlocked?
Yes you may try with - UFED4PC_7.49.0.2.tar
This is supported to remove or read screenshot without lock data For Android & specially working on many SAMSUNG devices
AzimBahar said:
Yes you may try with - UFED4PC_7.49.0.2.tar
This is supported to remove or read screenshot without lock data For Android & specially working on many SAMSUNG devices
Click to expand...
Click to collapse
Is that something you can flash via odin or?
Did some research, looks like a full mobile forensic device suite. I don't have 2000 dollars to drop on trying to open a phone.
NO.
This is a tool which can read your phone lock
I wonder if there is a way to use Odin to flash TWRP for a single boot. It might be enough to push the ADB keyfile to the directory or to delete the sqlite keys for the pattern.
AzimBahar said:
NO.
This is a tool which can cellebrite your phone lock
Click to expand...
Click to collapse
That doesn't mean anything Cellebrite is the name of the company that produces UFED.
metalblaster said:
I wonder if there is a way to use Odin to flash TWRP for a single boot. It might be enough to push the ADB keyfile to the directory or to delete the sqlite keys for the pattern.
Click to expand...
Click to collapse
you use fastboot to boot a twrp image on a device, without actually flashing it, but im not entirely sure if you can do it with a locked bootloader. Google it i guess?
PhotonIce said:
you use fastboot to boot a twrp image on a device, without actually flashing it, but im not entirely sure if you can do it with a locked bootloader. Google it i guess?
Click to expand...
Click to collapse
I wonder if I could mount the system partition that way or not bootloader aside. Unlocking the bootloader would kill all the data too which is a no-no.
It does seem possible to flash TWRP on some devices without unlocking the bootloader. How would I go about booting from it with fastboot without flashing it if I tried it? edit: nevermind I know how to do it.
I assume I would have to use the herolte img to try to get it to work since there isn't one specifically for the sprint variant.
Well I tried but I can't seem to read the phone with fastboot. I tried Odin and it predictably threw out the flash because it wasn't properly authenticated either.
Did you install the correct drivers? You need the samsung usb drivers for odin, and some adb and fastboot drivers for adb.
PhotonIce said:
Did you install the correct drivers? You need the samsung usb drivers for odin, and some adb and fastboot drivers for adb.
Click to expand...
Click to collapse
Yeah, of course. I have the Samsung drivers and I tried working with linux and had the same issue. Feels like my only recourse at this point is to setup a kali nethunter.
You also need to manually install adb and fastboot drivers for your device, which for me is pain, but maybe it'll be easy for you.
PhotonIce said:
You also need to manually install adb and fastboot drivers for your device, which for me is pain, but maybe it'll be easy for you.
Click to expand...
Click to collapse
Yeah I have them both. For some reason though Fastboot just doesn't see the device. I tried pinging it with the linux version and its vendor id but it didn't do any good. Kind of a real pain this is becoming. I may just convert my old nexus 11 into a kali nethunter and try to brute force it.
Still haven't found a solution and now I am feeling the consequences. My Nintendo 2FA is on this damned phone. Going to try to call support and get it removed tomorrow but its a real big pain.
Metablaster,
Is there an update to this?
My wife's S8 is pattern locked, she didn't set up a Samsung account prior, and the Google Find my Phone web tool PIN option has been changed/ deleted. Maybe there's an older html version of this somewhere?
ADB keeps coming back that the device access is "unauthorized" even after reboot, so although I thought I enabled USB Debugging before giving her the phone (it used to be mine), she may have restored to factory without enabling it again.
Kali will delete all of the data like a factory reset so that defeats the purpose except to just get use of the phone at all again.
Is there anyone on here that knows of a professional grade service that can do this?
So frustrating...! Why , upon proof of ownership, can't something be done?
Please pm me, I'd want to try the MD-Next option first.
If I run the risk of losing her data than anything more intrusive probably isn't worth it.
mat68046 said:
Please pm me, I'd want to try the MD-Next option first.
If I run the risk of losing her data than anything more intrusive probably isn't worth it.
Click to expand...
Click to collapse
MetalBlaster,
I did manage to get the S8 to boot into Recovery Mode, please PM me about trying the MD-Next step via USB bridge.
mat68046 said:
MetalBlaster,
I did manage to get the S8 to boot into Recovery Mode, please PM me about trying the MD-Next step via USB bridge.
Click to expand...
Click to collapse
Have you already tried to unlock the device with a locked SIM?