I'm trying to factory reset in Acer c720p Chromebook but it's been register or whatever Enterprise so all the things have been disabled like developer mode so I did what you said and I took out the screw and disconnect the battery and all that s*** put on I figured now it says use this device requisition when enrolling the device for Enterprise management and then it's got a spot where I can type something and it says restart or cancel ....what do I do?
Related
Hi guys!
Like my brother said: if they don't know it at XDA, there is simply not a solution yet. And having tried a lot of options myself, your expertise is wanted!
How it all began:
I wanted to update my Lumia, so used CAB sender. Fine so far, but there was a bug (no keyboard) so I wanted to repair with Zune. Didn't work, it said it was impossible to repair to the previous version (code 80180083). And since it didn't started up now anymore, it bricked.
Looking for a solution, my laptop OS (Windows Vista 32-bit) didn't recognized my phone anymore as Nokia Lumia 800, but simply as 800. And now, it only recognises my phone as Unkown Device (Qualcomm CDMA Technologies MSM). And Windows does not detects a proper driver for this thing. Tried Nokia USB Connectivity, WindowsUSB and the drivers belonging to Nokia Care Suite but nothing gets it done.
View attachment 1231319
I thought I found the solution with NSS, but I dont get the option below which says Nokia Connection Cable, because yet again: no phone can be found!
View attachment 1231326
Or course I tried also with Nokia Care Suite, but yet again: the laptop can't recognise the brick! Although Windows does notices I put something in the USB port and it sees the Qualcomm device.
Hard reset
Not possible, since I will get a 3 second vibration followed by 3 seconds nothing and then half-a-second vibration.
Putting phone on
If I try, it will give the 3 second start-up vibration which connects to Windows Vista (using the typical sound) shortly followed by the half-a-second vibration (and a triple-short disconnect sound on Windows).
As you guys can understand, I am in quite a bad situation now. Since the phone is bought in my home country The Netherlands and I currently live in Melbourne Australia, I hope to prevent sending it back home at any costs.
So what do you think: is this one permanently bricked, or is it still possible with a specific driver to fix this? Seems to me it's purely a communication/connection problem between my laptop and my phone, but I run out of options to try..
You could try downloading Windows Phone Support Tool from Microsoft.
Turn on your phone by pressing on and the Camera button at the same time, it should then enter flash mode (release power on buzz but keep holding the camera button). When it's in flash mode you can try and get Windows Phone Support Tool to repair the phone for you.
Thank you for your reply!
I tried it before, and this is the message I got:
Communicating with device. Please wait for Recover button to be enabled.
Support Tool version 4.8.2345.0
The tool had difficulty communicating with your device. Please check your device connection and make sure you followed the instructions above. Try recovery again and if the problem persists please contact technical support.
No devices were found.
Click to expand...
Click to collapse
The problem seems to be that there is absolutely nothing is installed on my phone. Therefore, the connection with my phone fails over-and-over. Doesn't matters which program I use. I am almost sure that there is a connection fail between the computer and my phone. I tried it at some other laptops but at every laptop it says 'Qualcomm CDMA Technologies MDM'. But not a single program (NSS/NCS/Phoenix/Windows Phone Support Tool) can make an actual connection with the phone, so it must be driver related.
When I try to turn it on, it starts up but then puts itself off, like if its out of energy. It doesn't charges though. What do you think: driver related or battery related?
------------------
Extra added info: when I try to flash Rainbow os-new with NSS, I get this message:
Checking file selection...Done.
Looking for NAND disk...Not found.
Are you sure you have development Qcom loader ?
Click to expand...
Click to collapse
What does that means?
Some more info about using NSS in an attempt to try flashing my phone
(Command: Flashing > WP7 Tools > Write OS)
Checking file selection...Done.
Looking for NAND disk...Not found.
Are you sure you have development Qcom loader ?
----------------------------------------------------
(Command: Flashing > WP7 Tools > P**** FS)
Looking for NAND disk...Not found.
Things to check:
1. Is the phone connected?(Plug to the USB)
2. Is it in the correct mode?(Try to switch to OSBL mode)
3. Have you installed the Qcom loader ?(Use the Install button)
Preparing update...Done.
------------------------------------------
(Command: Flashing > WP7 Tools > Install)
Init connection...Phone not found!
Does this shows a battery problem? I have had battery problems before with my phone, but I guess that when I try to flash (even with the extra add to NSS) it should ignore any battery level. Or should I screw it open, try it again and see if it will work then?
If it's finding it as an 800 that means it's finding it (it finds mine as an 800 when I've played with it too much).
When you enter flashing mode via camera button, do you not get the image of the phone connected to a PC on the phone?
I had that in the beginning, but those days are long gone.. I don't know how it happened that I don't get that back anymore. Perhaps because my phone doesn't boots itself completely, but falls out of its boot program. Nothing visible on screen
I know this question was asked over, and over, and yet over again.
However, the discussions over the topic go over many, many pages, are not noob-friendly (the noob in question is me).
My device:
LG Optimus G (E975); stock; no root; no USB debugging; locked bootloader (I think)
The screen is working, the digitizer is not.
I can get into recovery.
I can copy the files from DCIM.
I have found this soft: http://forum.xda-developers.com/showthread.php?t=2786395
I was able to make it work with another device. Maybe that's a good way to go? If I can get the USB debugging to turn on I could get all my data this way.
Also, when I get the broken phone into recovery mode, connect it to computer and use 'adb devices' it shows up as ' LG<some number of the phone> recovery>' - I don't know if it is a good sign or just 'meh, they all do that'.
What I want from the old phone:
Contacts. Unfortunately, when the phone broke it has not been synchronized with Google for some time, and some of the crucial contacts are lost.
All other data would be a nice bonus.
Since I can get the above software to work I think that what I need to do is 'just' enable USB debugging through ADB.
HOWEVER, to do this I think I need to get a custom rom? And that means rooting? WHICH would lead to data lost. I hope I'm wrong.
Any advice? Besides the 'get a new digitalizer and put it on'?
Please, help the noob!
zabcia said:
Since I can get the above software to work I think that what I need to do is 'just' enable USB debugging through ADB.
HOWEVER, to do this I think I need to get a custom rom? And that means rooting? WHICH would lead to data lost. I hope I'm wrong.
Any advice? Besides the 'get a new digitalizer and put it on'?
Please, help the noob!
Click to expand...
Click to collapse
To enable usb debugging you don't need root or anything. just go to settings > about phone > tap "build number" 7 times > back to settings > new menu "developer options" should appear > turn USB debugging on. When you connect your phone to the PC with ADB opened your phone will ask for authorisation - authorise connection and you're good to go.
zabcia said:
Also, when I get the broken phone into recovery mode, connect it to computer and use 'adb devices' it shows up as ' LG<some number of the phone> recovery>' - I don't know if it is a good sign or just 'meh, they all do that'.
Click to expand...
Click to collapse
This is a good sign, because it means ADB recognizes the phone and you can use it.
Thanks for the reply.
The thing is - the touch is not responding. So I can't turn it on through the menu.
Hi I’m trying to root my viewsonic iR7Q tablet, I’ve tried kingoroot on both versions and neither seem to work.
On the pc version, the tablet won’t show the notification telling me that the pc has tried to connect, and the app will just tell me to enable usb debugging, which is already active since the tablet warns me about it and asks me to turn it off.
Also on a side note I can't access the developer options from the configuration menu, I had to enter through the malware bytes app.
And the .apk isn't much help either, it will reach 90% then freeze the device, I waited for 10 whole minutes and no progress at all, it was still frozen (I read somewhere that I shouldn't take longer than 5 minutes) had to reset it.
It was connected to wi-fi so I don't think it was that, anyone know any way to root it?
So i got my friends old Lumia 920 with Windows 8/8.1 installed on it but obviously it's not really used anymore and a lot of apps are already unsupported now. So i thought i'd try and install Android over the Windows OS.
Using WPInternals i flashed the phone with a .ffu file (RM-820 - i think!) that was listed under my phones specifications, used the program to flash the phone but just before it completes i get an error message saying the boot-loader wasn't unlocked properly and now the phone won't switch on, hold a charge or do anything at all. I have tried all button combinations for a soft & hard reset but the phone doesn't respond at all. I managed to get the phone connected to my desktop temporarily in Mass-Storage mode, but then the connection disappears and i can't access it.
I've seen so many posts about this problem and being able to 'flash' it back to normal or repair the issue..
can anybody recommend or explain a technique that would work?
Many thanks!
Hi,
is there any sign of reaction in the device manager, e.g. a Qualcomm_USB device or a Qualcom_COMx port?
Joachim
Good Morning Ladies and Gents;
I am working with an LG G4 H811 (T-Mobile) on 20v (MM 6.0), which I would like to root. I have unlocked the bootloader, which is confirmed every time I start the phone. I then tried to root using LGUP, but the phone wasn't recognized, so I did an error recovery reinstall in LG Bridge, thinking a fresh software install would re-align things.
Now, whenever I connect the phone to the computer, I get a pop-up window on the phone saying "USB Connection - Allow this computer to access your phone data?" CANCEL/ALLOW and the phone does not show up on the PC screen or in Device Drivers until I tap "ALLOW". Therefore, it is not recognized by any software without tapping ALLOW.
More than an inconvenience, this effectively prevents me from any mods on the phone, because I need to shut off the phone and disconnect from the USB port, then reconnect with Volume UP pressed to get to download, and in download mode I have no access to ALLOW the USB connection, so neither ADB nor FastBoot recognize any devices, and the phone is not included in Device Manager.
Of course, the bootloader is unlocked, Developer Options enabled, OEM Unlock on, USB Debugging on. I am using an original LG USB cable. I have tried 4 different computers and three different sets of drivers. I've tried older drivers on older and newer computers, and vice-versa, for every combination available. Each time, I plug in the phone after a fresh computer install and let it install it's own drivers. Two of the computers are Windows 7, two are Windows 10. I've tried connecting in MTP mode and PTP mode, with no difference. I've removed the SD card in case it was affecting things, and done a factory reset on the phone. Auto Play options have been set on the PC to "Do Nothing". I've searched the internet and this forum without results.
Basically, I've spent two days on this before asking for help. Has anyone else had this experience and solved it with something other than drivers? I think I've just about run out of ideas! Thanks.
I don't root however it's probably Developer options>usb default settings>usb tethering
Try connecting directly from Disk Management on the PC. Use the scan for new drives option if it's not visible.
Thanks buddy, appreciate you trying to help out.
Tethering is a way to allow a device connected to your phone to use the phone's data connections. In the tethering instructions:
"You may not be able to access the data files stored in the phone's memory, such as pictures, music etc, or transfer such files between your phone and your PC when USB tethering is on"
However, its worth a try - so I set up tethering, unplugged the phone and plugged it in again - the same Cancel/Allow screen came up, and no device in DM until I tapped Allow.
I then opened Disk Management and plugged in the phone. I still get the Cancel/Allow screen, and rescanning devices didn't show anything new, because the phone is not in the Device Manager until I tap Allow.
The key here is finding out why the phone or computer do not store the "Allow" command. Normally, the phone will show this screen the first time you plug it into a computer, and when you tap Allow, it will store that someplace such that the phone and computer are recognized as safe devices. You should never have to see the permission screen again. My challenge is that I don't know where that permission is stored - is it on the phone, the computer, attached to the driver? Don't know. And I don't know why it's not being saved. If I had those answers, I could probably edit the registry (or whatever) to make this a permanent attachment.
Thanks!
You're welcome.
Maybe debug mode?
Try turning off Developer options.
Obviously there is a way, sorry but I never had to use that function.
Try some Google searches which is how I usually find answers and/or by just playing with it
Well, I wouldn't be able to communicate via ADB with Developer Options off. And I spent two days searching the internet before coming here, and all I found was people updating their drivers, which is why I tried so many combinations of Windows versions and drivers versions.
I'm actually kind of surprised that this seems to be such a unique problem, I was hoping someone would notice the post who had actually had a similar problem and fixed it. But I do appreciate you trying to help!
Sorry I can't help, but I never choose to root.
It's time sucking black holes like this that I deliberately want to avoid.
At least you didn't brick it...
ha ha... you got that exactly right! Every time I do this I end up spending DAYS trying to get up to date on everything that has changed since my last phone!
Well, I appreciate you taking time to try to help.