Hey guys/gals,
Unfortunately I recently dropped my Nexus 4 (Stock), the screen is cracked and the touchscreen is unresponsive. I have read a few of the threads here on how to salvage the data but they are not working for me or honestly I may not be understanding them right?
I wanted to use this ( http://forum.xda-developers.com/showthread.php?t=2786395 ) guys method as this is exactly what I need to get my stuff out of the phone. I didn't have USB Debugging enabled and as I said my phone was/is stock so no root or anything fancy like that. From my understanding this:
http://forum.xda-developers.com/sho...tmctr=(not provided)&__utmv=-&__utmk=25906750
link will help me unlock the USB Debugging but I get nowhere after running the program.
My question and apologies for the annoyance beforehand, can anyone give me a step by step laymens process of how I can go about getting "The Ultimate Touch Screen Control for Android" to work on my PC/phone so I can salvage my pictures/text files/other data?
This would be greatly appreciated. I thank anyone who responds in advance!
-Celloh
Can anyone help me out? I have been trying to figure this out since last night and have gotten nowhere. Maybe even link me to a thread I haven't seen?
Catch-22
Celloh said:
Can anyone help me out? I have been trying to figure this out since last night and have gotten nowhere. Maybe even link me to a thread I haven't seen?
Click to expand...
Click to collapse
Is your Bootloader unlocked?
If USB debugging is not enabled in Android and you can not enable it in android due to an unreadable screen,
Your only option is to ADB shell from custom recovery such as TWRP using the method in the first link you posted..
You can only boot into custom recovery if your bootloader is already UNLOCKED.
Unlocking the bootloader wipes all your data from the phone. Catch-22
Related
Tab boots to "welcome" screen but does not register touches, leaving me unable to move forward. Ready for the long story?
I am helping a friend who bought this tab from a third party. When he received it, the previous owner stated that they did a factory reset back to Honeycomb but he noticed that it did in fact still have ICS on it. Probably OTA'd when the previous owner did the reset. Tab worked fine for about two weeks until one day he came home and the lockscreen would not register touches. That's where I come in.
I did the "erase, wipe" (booting while switching the screen rotation back and forth.) Tab wiped and brought me to the "Welcome" screen where you select country and language and still does not register touches. I have tried blackthund3r's flash and manager tools, as well as multiple guides to recover from what I have seen referred to as "flu." The main problem I have is that I cannot get a valid UID. Using USBDeview gives me an 11 digit serial but it returns as invalid when plugged into DotNetDetector and I am unable to use SDB because the non working touchscreen has left me unable to enable USB debugging.
Any suggestions, help, advice, on things I can try? I am really stumped and would like to help my friend/conquer this problem. Thanks for anyone who has taken the time to read this/offer help.
generalagony said:
Any suggestions, help, advice, on things I can try? I am really stumped and would like to help my friend/conquer this problem. Thanks for anyone who has taken the time to read this/offer help.
Click to expand...
Click to collapse
Get ready for some Ubuntu... Here is the guide that will get you a valid sbk. My nephew just brought his tab to me after forgetting his password. So I was in the same boat as far as UID/SBK. This is gonna take a while so put some time aside.
JdgM3NT4L said:
Get ready for some Ubuntu... Here is the guide that will get you a valid sbk. My nephew just brought his tab to me after forgetting his password. So I was in the same boat as far as UID/SBK. This is gonna take a while so put some time aside.
Click to expand...
Click to collapse
As sure as I am reading yoru reply the damn thing just started working. I was able to get to USB debugging and via ADB I was able to pull the UID; which was the same as the one I got from USBDeview btw. Still an 11 digit code. The only thing I can guess is that it has a faulty touchscreen, or maybe the battery was just too low to register touches? Thanks for your reply though. Always nice to be able to rely on the folks at XDA.
That is too cool. The other way is a learning experience to be sure. Enjoy.
JdgM3NT4L said:
That is too cool. The other way is a learning experience to be sure. Enjoy.
Click to expand...
Click to collapse
I have now realized that the touchscreen does work but is very glitchy and have found that lots of people have had problems with the OTA ICS update. Any suggestions on a good custom ROM for this tab? It isn't mine so I have not been following this section. Would like something close to stock ICS but with fixes that resolve the problems associated with OTA.
generalagony said:
...I was able to get to USB debugging and via ADB I was able to pull the UID; which was the same as the one I got from USBDeview btw. Still an 11 digit code...
Click to expand...
Click to collapse
generalagony said:
I have now realized that the touchscreen does work but is very glitchy and have found that lots of people have had problems with the OTA ICS update. Any suggestions on a good custom ROM for this tab? It isn't mine so I have not been following this section. Would like something close to stock ICS but with fixes that resolve the problems associated with OTA.
Click to expand...
Click to collapse
First check in Settings>About Tablet>Build Version - this will tell you what rom you are currently running -
Then, if you can, download and install Acer Recovery Installer
This tells you what bootloader and recovery is installed.
The glitches you speak of and the 11 digit uid point to an ICS Rom and unpatched HC bootloader - updating to the new BL often fixes these weird glitches BUT if you flash a custom rom as well, you'll be running sweet!!!
If you wanna stay close to Stock then I'd recommend ezterrys one here comes pre-rooted and busy box installed - and if you want to you can install his Over clocked kernel too.... plus its well maintained and supported
there are many tools and guides around to help you...the ones in my sig for instance the cpuid one has a lot of general info in it too re bootloaders, sbk and flash tools.
If you have any q just ask, there's always someone round willing to help...good luck!!
Hey guys, my first post here. I signed up for this forum a little while ago and I've just been a lurker since today. Lots of great stuff on this forum!
I finally got my Nexus 4 phone when they went back on sale in late January, I came from an iPhone 3GS and I've been loving the switch every day since!
But now I have a problem that I hope you guys can help me with.
When I first got my phone the first thing I did was unlock the bootloader and root the device, I had 4.2.1 on my phone and forced the 4.2.2 update by clearing the cache/data of a few apps when it was mentioned on this forum (Bad mistake I think). I went to download titanium with root the other day to start to backup my apps/phone before I started messing with kernels and audio upgrades in case I messed something up and needed to reinstall. Unfortunately since this is my first Android phone I didn't know that upgrading would also remove my root access. Not a problem I though, I'll just go ahead and re-root the device, well that's where I started to see various problems.
I installed the SUser 1.0.4 zip on my phone (After I tried .98), booted up into the clockwork recovery option, extracted the zip from within clockwork to root my device again and nothing. I tried a couple of times, even tried the Nexus 4 toolkit but that didn't seem to work either. Rootchecker won't recognize that my phone is rooted.
In fastboot mode it shows my phone is
Secure boot - enabled (Green)
Lock State - unlocked (red)
When I was in the Nexus 4 toolkit I also noticed that it wouldn't recognize my phone's serial USB debugging mode even when I turned it on (Pressing the build number 7 times and checking the usb debugging box in developer options). When in fastboot mode my computer recognized my phone without a problem. I am still able to move stuff on and off of the phone through windows explorer, but only when it's NOT in debugging mode, my computer beeps like something is connected when in USB debugging mode but nothing shows up anywhere except in device manager. I tried installing the drivers that were posted for 4.2.2 and also tried installing the drivers through the toolkit but neither would fix that problem. Another thing I noticed was that I never got a prompt on my phone to allow my computer access to debugging mode like people mentioned that I should get.
Now either I messed something up somewhere along the lines, (good chance)
or I'm an idiot and i'm missing something really obvious (better chance)
Anyone have any suggestions as to what I can do or how I can get my root access back?
Thanks a bunch in advance for any help you guys can give me, and if I left some info out of here that you need let me know.
kelmino said:
Now either I messed something up somewhere along the lines, (good chance)
or I'm an idiot and i'm missing something really obvious (better chance)
Click to expand...
Click to collapse
Oh wow... yup I'm an idiot and missed something really obvious....
I just installed the SuperSU app from the playstore and I do have root access again and apps request access.
ugh I'm a moron, I spent hours on this yesterday and as soon as I post this I fix the issue
Sorry guys
Now my only problem is I can't see my phone from the playstore on my computer but I'm not worried about that, I think I can fix that as I see another post up here for that same issue.
perhabs this helps
http://forum.xda-developers.com/showthread.php?t=2159744
u dont need to extraxt su zip file....download drivers..use tool kit to unlock bootloader..then flash temporary clockwork recovery...flash su in recovery....download goo manager from playstore to flash permanent recovery
Sent from my Nexus 4 using xda app-developers app
dont use toolkit. do it the long way so you know what you're doing otherwise you're walking in a room blindedly hoping you'd get through the maze.
in the long run, it'll be worth it. very simple & easy to do.
Hey Guys,
Hoping someone can help here, I have followed various tutorials I have found on the internet to try and restore my Nexus 7 back to its factory state after it one day decided to never get past the white Google logo.
Inevitably I ended up on this tutorial as the only one where I seemed to get any kind of a link and response with the tablet: blog.laptopmagDOTCOM/how-to-hard-reset-a-bricked-nexus-7-with-your-pc
basically it got as far as trying to Unlock the Bootloader, but it fails to do so. I do get the popup on the tablet asking if I want to unlock it but nothing happens, it remains locked after I click Yes. My command line saying that it Failed.
All other tutorials seem to assume you can access the OS and enable debug mode but of course I cannot. I cannot even do a Factory Reset, every options eventually leading me to a white Google logo.
I also cannot get into recovery mode, im just stuck on the screen with the green android and the option to Start, Recovery mode etc all just lead to the Google logo.
The impression I have gotten from not being able to unlock the bootloader is that there must be a hardware failure? could anyone suggest some black magic I might be able to do to fix it? I realise at some point I should cut my losses. I had also wondered if it was worth buying a new motherboard/logic board?
Would appreciate any help.
Cheers,
Matt.
Have you tried this tools:
http://forum.xda-developers.com/showthread.php?t=1766475
or
http://forum.xda-developers.com/showthread.php?t=1809195
Both are magic tools for nexus 7, please read any explanation carefully!
It may help you :good:
ju1da said:
Have you tried this tools:
http://forum.xda-developers.com/showthread.php?t=1766475
or
http://forum.xda-developers.com/showthread.php?t=1809195
Both are magic tools for nexus 7, please read any explanation carefully!
It may help you :good:
Click to expand...
Click to collapse
Wow.....
Please stop spamming the toolkits.
The op has indicated that there is a hardware issue because the bootloader unlock isn't working.. A stupid toolkit isn't going to fix that. You should are promoting people to use their damn brains and doing it the right way, but laziness prevails, eh?
To the op, sorry but it sounds like you have a corrupt emmc. If the unlock process fails to commit, that's a bad sign.
Sent from my Nexus 5
Also to the op, USB debugging has nothing to do with the bootloader or recovery, only a booted os. Can you boot to recovery from the bootloader?
Sent from my Nexus 5
Hi all, I've messed up with my nexus 7 2013 and i think its soft bricking.
I was using multirom and accidentally installed the wrong kernel. Every time I boot into android (4.4) it loads slow and then instead of displaying the screen it shows two duplicated top left hand corners and remains unresponsive.
Unfortunately i never got the chance to enable usb debugging and my bootloader is locked.
I tried a few things suggested online but they didn't work and multiform appears to have been wiped.
Recovery still works (TWRP) but I'm really in a bind.
Any help on getting back to stock android 4.4 would be amazing, but please bear in mind I'm new to android, so please provide detailed instructions.
Probably your best way would be using fastboot, can't give you details but I have seen it on here. Google fastboot nexus 7.
Sent from my Nexus 10 using XDA Free mobile app
gandy92 said:
Hi all, I've messed up with my nexus 7 2013 and i think its soft bricking.
I was using multirom and accidentally installed the wrong kernel. Every time I boot into android (4.4) it loads slow and then instead of displaying the screen it shows two duplicated top left hand corners and remains unresponsive.
Unfortunately i never got the chance to enable usb debugging and my bootloader is locked.
I tried a few things suggested online but they didn't work and multiform appears to have been wiped.
Recovery still works (TWRP) but I'm really in a bind.
Any help on getting back to stock android 4.4 would be amazing, but please bear in mind I'm new to android, so please provide detailed instructions.
Click to expand...
Click to collapse
Wugfresh toolkit should also work, especially if you are not familiar with or interested in learning fastboot & adb.
wtherrell said:
Wugfresh toolkit should also work, especially if you are not familiar with or interested in learning fastboot & adb.
Click to expand...
Click to collapse
I used the Wugfresh tookkit and it worked like a charm!
Thank you both for getting back to me and helping me fix this. I really appreciate it!
So, as this is my first ever thread to this website and the reason why i have created this account, I am somewhat new to the XDA forums...
Nevertheless, i will state my problem here:
Right now, my phone and my limited knowledge about it have come to an dead end. with the help of online tutorials and so on, (I have downloaded almost 40 gigabytes worth of space to do stuff to my phone), i was able to only get the fastboot mode to work again.
It started with me uninstalling a system app from google (I don't know which one exactly, but i had the resurrection remix 5.69 or something like it, and in that ones system app remover it was one of the lowest google apps). I don't know if this is important, but at the time i did that i was in plane mode.
After some time i ran into some loading issues with games and restarted my phone. the first time i got in, i booted up normally and could do my pattern normally, but then there was only a black screen and i could pull that info bar thing down. as soon as i wanted to open the settings, everything froze and i decided to restart the phone. Once it was shut down i then got greeted by a bootloop which i aborted by shutting down after about 3 minutes. then nothing was working anymore, so i wanted to see if the fastboot mode was still available. it was, but after shutting down from that and trying again ( just to be sure) even that was gone.
so i went online and downloaded basically everything you can find online to recover a harbricked op2.
turns out, after i got my fastboot working again, the OEM and the device were locked (still not sure if those are different things or the same) and because i couldnt get in the android system, i could not enable it.
the ADB commands do not work at all because there is no device detected for it, though it is detected for fastboot. the command fastboot OEM unlock does not work because OEM unlocking is disabled...
so far i have been able to connect my phone in 3 modes and names for those, them being:
Android Bootloader interface (Fastboot)
Qualcomm HS-USB Diagnostics 900E (Connected while holding VolUp)
RELINK HS-USB QDLoader 9008 (Connected while holding VolUp + VolDown)
I am also unable to flash anything on the phone because the OEM is locked
I will not be able to answer for some time (probably 2-3 weeks) but i wanted to start this thread so I could already have an answer when i come back home again (traveling with fam, and its somewhat hard to take a PC tower with you on trips)
Thanks for helping me! :fingers-crossed:
I'm having the exact same issue as OP.
I'm not sure exactly what I did, but I can only boot to fastboot. Typing fastboot continue does not work, I can't flash ANYTHING or use any of the recovery tools, because my device is locked, and there's no system to boot to so I can run fastboot oem unlock (have to turn on debugging, which I can't do). I have read just about every guide there is, and also downloaded a boatload of purported "fix" tools/drivers/packages. My phone remains able to boot only into fastboot, and I can't get anything working.
Installing the device drivers did work for me, so I'm about half a step ahead of some other people with this issue, but none of the tools or scripts I've found, or manual methods, have brought my OP2 back to life.
I'm really, really hoping someone here is able to help with this.
Only way is restore with Qualcomm tool
Sent from my SM-N920C using Tapatalk
Coolmfarshard said:
Only way is restore with Qualcomm tool
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
Sorry, but could you link us that?
Also,does this really work with a locked device and locked OEM? Please do not tell us things if you don't know if they work.
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
Lonemaster said:
Sorry, but could you link us that?
Also,does this really work with a locked device and locked OEM? Please do not tell us things if you don't know if they work.
Click to expand...
Click to collapse
Its working bro tried several phones with this tool
You cant know its working or not without trying
Coolmfarshard said:
Its working bro tried several phones with this tool
You cant know its working or not without trying
Click to expand...
Click to collapse
Ok, Thanks. Don't know what i was thinking back then.
I will reply again when i am Home and tried it. (Currently i am just using Internet cafes.)
MickyFoley said:
http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
Click to expand...
Click to collapse
Oh, it is that one. I had already tried this one, in all listed modes posted above. The problem with that one is that everytime I hit the start button, the green progress bar does not show up and it does not a single thing... because I am staying at a place with a internet café for 3 days, I can download some stuff and try it again.
EDIT: I don't know if that was the reason It didn't work, but I may or may not have forgotten to install the driver because it was deleted off the onedrive page and I just forgot about it afterwards. if I can find a replacement for it, I will ink it here for future users with the same problem. otherwise, I would be GLaD if someone would do that for me...
Have you tried flashing a stock ROM with the qcom download tool
abdur10567 said:
Have you tried flashing a stock ROM with the qcom download tool
Click to expand...
Click to collapse
I am not sure if it is that one (it gets pretty messy wehen you have downloaded 50 gigs), but i think it wouldn't let Me because of the locked OEM.
Lonemaster said:
So, as this is my first ever thread to this website and the reason why i have created this account, I am somewhat new to the XDA forums...
etc. etc.
Thanks for helping me! :fingers-crossed:
Click to expand...
Click to collapse
For some reason, after doing it for the what felt like the billionth time whith the restore tool it finally worked (I have NO ****ING IDEA why tho.)
Thanks for everybody who helped me.