Hi everyone,
This is my first thread here eventhough i m following these forums whenever I'm doing stuff with Android. I am also a programmer, not particularly an Android expert, but whenever I need to I use Android tools too. Anyways, today I realized my phone's touchscreen is broken somehow. And I have pattern lock. Normally my developer mode is enabled but darn when I connect my phone to PC I cant just tap to activate Usb connection. I searched through web, spent at least 6-7 hours looking for solutions. Here are what I got:
- I can't use Adb because my phone is not rooted and for most commands I got "closed" error.
- I tried various tools and methods, mostly from here but all end up not being able to confirm because of touchscreen malfunction.
- Tried to root it through Adb didnt work
- Can't seem to use fastboot, fastboot dont seem to see my device eventhough Adb can (I couldnt see any fastboot options in factory or recovery mode. Actually Factory Mode was only tests, and recovery mode has update from adb,update from sd card, update from cache, wipe, backup and restore options.)
Other than that I tried all I can except actually disassembly of my phone. So, at this point I wonder "If" there's a way of connecting my phone to my pc. Soon I ll buy a new display and replace it for sure. But I see this as a reason to dig into Android and dont want to miss the chance by being too lazy.
Thanks in advance.
Related
Ok I recieved the above device from a coworker. They had gotten the device for their kid for Christmas, non 3G version. Anyway their kid enabled airplane mode, and took the tablet to school. They had airplane mode on to save battery. They had a lock screen on the tablet. Well as luck would have it he left it on his desk, and the other students locked the tablet so the Gmail account had to be entered. Well with airplane mode enabled there was no way to authenticate with Gmail for recovery. Upon massive Google searches, I discovered this tablet had no hard key press recovery. Essentially it was a bricked device, even the company Sungale had no info on recovery. Well after working at it I discovered a fix. ADB is on by default for this device. Boot into ADB then issue the command
adb shell
wipe data
adb reboot
Now setup your tablet just as you did the first time you opened it.
Hope this helps guys!
Pntblltrc4
Root Access
One other tip, this device is rooted out of the box via the shell. So realistically it should be very simple to port clockwork to this tablet.
pntblltrc4
pntblltrc4 said:
One other tip, this device is rooted out of the box via the shell. So realistically it should be very simple to port clockwork to this tablet.
pntblltrc4
Click to expand...
Click to collapse
Out of curiosity, were you able to find out anything more about upgrading the device? I own an ID707WTA as well, and I've been searching for an unofficial ROM but nobody has seemed to have tried to make one yet.
device not found error
I keep getting a device not found error.... What do you think is the cause or how can you get around it?
After unrooting, by installing stock and then updating, from Samsung, to Android Jelly Bean 4.3, I am unable to get the computer to see my phone when in download mode. Further, when connected to the phone by adb, when I issue the command, to reboot in 'bootloader mode', it just does a normal restart. I need to unroot because the phone's IMEI is corrupted and I want to use the efs backup to get it reinstated. I don't know of any way to root that doesn't require 'Download Mode' to work.
So, in summary:
The phone is currently not rooted, it has stock Android 4.3.
I can access the phone via adb.
I also have Android SDK on my computer so have the availability of 'fastboot' in addition to adb.
I can switch to Download mode on the phone, in the normal way, but the computer can't see the phone when in that mode.
Please can anyone advise on how I should proceed in order to root the phone, given the above constraints, or regain the use of a working 'Download Mode' ?
Search for many similar posts on pc connections to download mode, there isn't one solution.
Sent from my GT-I9300 using Tapatalk
Thank you for your reply. Despite the quote, I had already searched and I had not come up with a solution that worked. That is why I posted a question. All the stuff about trying another socket and it could be the lead are basic. The lead is perfectly OK - I used it to flash the stock ROM. Then the phone failed to connect in Download mode. I've use both Linux and Windows in a Virtualbox to communicate in Download mode before. Both could see the phone in Download mode before I did the stock flash.
delete all samsung driver
rebbot windows
install driver
Thanks for the suggestion. The non-connection also applies to Linux, which is the host system, so it isn't just a Windows problem. Previously I could use either OS with no problem.
However, I did, by chance, find a solution, not a good one but it works. I have to disconnect the battery for a long time - minimum time not known. I tried 10 minutes and that didn't work so I tried waiting a much longer time. I am then able to use download mode for one instance. Then it becomes unusable again so next time I have to go through the battery removal process again.
By chance I found a similar post where a similar stock install had resulted in the same problem. So I posted my solution on there also.
Plz pardon my rant but I need major helpppppppppp lol, I've spent days scouring this site & google to try to fix this myself. I've built pc's but delayed learning droid because it's worse then mickersoft from what I've seen. I babysit for a lady raising her 3 granddaughters, they don't have net & were only able to access a few things. Sooo I volunteered to add some games, I was so flabbergasted at the bloat, shear greed and limitations of both versions of dis ui. I wanted to just disable it to use a different launcher but nooo to easy. no good deed goes unpunished lol. I updated the stock to the current as of two weeks ago ota kitkat and it went down hill fast, the dis ui worked for the most part but it wouldn't let me in the settings that's on the nabi mode for no apparent reason.
So not being able to find much current info for dis version, I made the huge mistake of using kingroots apk. it chocked but then work fine except I still had the above problem. no matter what I tried to clean or debloat. I got stupid tired and did a factory reset it now won't boot fully. I only get a pop up loop even in safe mode of nabiSetup has stopped. I can only turn off but can access recovery and the fastboot etc! I give it wins this round lol.
I have tried both win 10 32 & 64bit I only got it to connect once, it said I unlocked the bootloader but nothing can find the device to reboot-bootloader thru adb or NabiLab, 15 sec abd and etc. I'm to tired to think straight and to new to this so I must be missing something. there has to be away to get droid back on it! I can usually access the tablet and the sd card thru win explorer but no matter witch drivers I've tried it will not connect properly or the drivers won't install fully even with drive sig disabled. so it has to be because of the bitmap error I found in recovery or because it won't fully boot to access the usb on the tablet??
cliff-notes
1. the devise will not fully boot I get a nabiSetup has stopped popup loop in normal & safe mode I can only shut it off.
2a I can still get in recovery I tried to flash it but I assume I was using the wrong file nothing would load, but noticed E: missing bitmap stage_empty & stage_fill it seems to be a common droid problem but no info to be found for this devise version.
2b In the device manager fastboot comes and goes or I see a USB device descriptor failed or set address I think it was and pdanet stalls. I'm gonna fdisk laptop again it's had way to many driver attempts to be sure that's some of problem not operator error or usb in a mood again.
3. being brain-dead tired & a droid newbieish. I can't get to the usb to play nice so I can't install twrp. I assume because of the usb drivers ie google and etc not showing up right in device mangr. no usb on nabi which I just remembered the developer options vanished, that's why I decide to reset since what I think is the reset pinhole didn't work?
p.s I can access win explorer most of the time. the common droid/disney folders are showing but I'm unclear what all is missing.. can someone please give me a laymens clue how to get the os back on it. I deleted the cache and etc to no avail. I pieced together other peeps info here but so far I'm special no one has my exact errors lol. my gut says it's fixable from what I have read it seems to makes a difference its a disney version I don't care what's on it as long as it works at this point any ideas or help is deeply appreciated. I'm running win 10 ent 64bit at the moment and it was stock disney version of NABI2-NV7A-US-D with 4.4.1 before bad update of kitkat ota.
Twink225 said:
Plz pardon my rant but I need major helpppppppppp lol, I've spent days scouring this site & google to try to fix this myself. I've built pc's but delayed learning droid because it's worse then mickersoft from what I've seen. I babysit for a lady raising her 3 granddaughters, they don't have net & were only able to access a few things. Sooo I volunteered to add some games, I was so flabbergasted at the bloat, shear greed and limitations of both versions of dis ui. I wanted to just disable it to use a different launcher but nooo to easy. no good deed goes unpunished lol. I updated the stock to the current as of two weeks ago ota kitkat and it went down hill fast, the dis ui worked for the most part but it wouldn't let me in the settings that's on the nabi mode for no apparent reason.
So not being able to find much current info for dis version, I made the huge mistake of using kingroots apk. it chocked but then work fine except I still had the above problem. no matter what I tried to clean or debloat. I got stupid tired and did a factory reset it now won't boot fully. I only get a pop up loop even in safe mode of nabiSetup has stopped. I can only turn off but can access recovery and the fastboot etc! I give it wins this round lol.
I have tried both win 10 32 & 64bit I only got it to connect once, it said I unlocked the bootloader but nothing can find the device to reboot-bootloader thru adb or NabiLab, 15 sec abd and etc. I'm to tired to think straight and to new to this so I must be missing something. there has to be away to get droid back on it! I can usually access the tablet and the sd card thru win explorer but no matter witch drivers I've tried it will not connect properly or the drivers won't install fully even with drive sig disabled. so it has to be because of the bitmap error I found in recovery or because it won't fully boot to access the usb on the tablet??
cliff-notes
1. the devise will not fully boot I get a nabiSetup has stopped popup loop in normal & safe mode I can only shut it off.
2a I can still get in recovery I tried to flash it but I assume I was using the wrong file nothing would load, but noticed E: missing bitmap stage_empty & stage_fill it seems to be a common droid problem but no info to be found for this devise version.
2b In the device manager fastboot comes and goes or I see a USB device descriptor failed or set address I think it was and pdanet stalls. I'm gonna fdisk laptop again it's had way to many driver attempts to be sure that's some of problem not operator error or usb in a mood again.
3. being brain-dead tired & a droid newbieish. I can't get to the usb to play nice so I can't install twrp. I assume because of the usb drivers ie google and etc not showing up right in device mangr. no usb on nabi which I just remembered the developer options vanished, that's why I decide to reset since what I think is the reset pinhole didn't work?
p.s I can access win explorer most of the time. the common droid/disney folders are showing but I'm unclear what all is missing.. can someone please give me a laymens clue how to get the os back on it. I deleted the cache and etc to no avail. I pieced together other peeps info here but so far I'm special no one has my exact errors lol. my gut says it's fixable from what I have read it seems to makes a difference its a disney version I don't care what's on it as long as it works at this point any ideas or help is deeply appreciated. I'm running win 10 ent 64bit at the moment and it was stock disney version of NABI2-NV7A-US-D with 4.4.1 before bad update of kitkat ota.
Click to expand...
Click to collapse
It's hard to understand all of that but it sounds like perhaps you deleted some bloat that you should have, you sound like having driver issues, and possibly wrong TWRP version. Need to clear that up and then reinstall the stock Disney ROM.
I'd start here it has all the tools/TWRP/ROM's you need.
http://forum.xda-developers.com/nabi-2/general/nabi-information-t3229119
So sorry hun, toshiba is driving me nuts and I'm having a bad add moment or three lol. I read about you retiring. so I tried hard not to bother you. now I'm really confused. I've read your nabi2 general info post and even ran across your youtube vids. the problem is I'm not familiar with adb. & the included NabiLabGUI drivers, win10 either fails to finish saying it was interrupted. or it just won't install the 32 bit drivers, I thought I as suppose to use.
The 64bit driver 3 out of 4 install but, I can not get the Google Inc, driver to install properly even with the inf file. (ie the android_winusb.inf ) it says the system can't find the file, it can install the older versions from NabiLabGUI or naked drivers. but doesn't show in add/remove and it still won't detect the tablet most of the time lol.
Pda also has conflicts with adb, I got the nablab disney option to detect it but still failed to install twrp saying it can't find devise and I noticed in device manager 2 driver problems that will not let me update manually or they go missing if I try to force windows to reinstall. (device descriptor request & set address failed)
I must be missing something big, I also tried the 15sec and minimal adb. I assume because the tablet won't fully boot up, windows doesn't know what to do with it. when I tried different cables. windows 10 enterprise won't play nice at all now. so I will format again to be safe but lost what to try next.
I guess my questions should be is there a work around or a full inf version of the newer drivers for NabiLabGUI2015 that might work with this demonic disney nabi2.
&
Is NabiLabGUI compatible with .net framework 4.6 advanced services? (I may have to downgrade o/s. on the nabhacks site is says .net 4.5 is a prerequisites.) I don't know much about the app but saw 4.6 comes preinstalled, I can't install 4.5 yet, I saw there has been compatibility issues. and it won't let you revert versions easily if at all.
I'm to tired of this tab to think straight anymore and so grateful any help I'm in way over my head here.
Update
I lost the battle but I won the war, now google & supersu are messing with me as usual but it boots so I win lol :victory::silly:
Hi, I am trying to unlock a Galaxy J1 Ace SM-J111F/DS for my colleague. The phone belonged to his younger brother who had passed away in an accident, now that he's gone, we have no information as to now to unlock his phone.
I have tried researching and searching around for methods but to no avail. I was hoping maybe someone here could provide some assistance
A factory reset is out of the question as he needed to access information stored inside the phone
Some device details:
Device is locked by a pattern lock
Unable to unlock via Google account(No one in his family knows his account name/password)
Phone is not Rooted
Phone is FRP Locked
Things I have wanted to try and done so far:
Intended to flash a bypass to unlock the lock screen
Attempted to flash a custom recovery in order to flash the bypass, however FRP is locked and it does not allow a custom recovery to be flashed
Attempted various methods of "security exploits" to unlock, but appears to be patched on current firmware
Tried to search methods of unlocking FRP, however all the methods I've seen so far requires access to developers option, or requires a flash of stock firmware.
Tried accessing device via ADB, however it does not work as USB debugging is not enabled
I'm currently out of options trying to do this by myself, we would really appreciate it if someone could help us out in this
If powered on, and plugged in to PC, is it 'seen' at all?
robneymcplum said:
If powered on, and plugged in to PC, is it 'seen' at all?
Click to expand...
Click to collapse
Yes, it is "seen", but I can't do anything else to it
If it is seen, there is a chance you can get data off it.
You can install' minimal ADB and fastboot' and the USB drivers for the phone on your PC. If the phone is not encrypted you should be able to browse the phone storage in an adb shell and to copy files or directories with adb pull.
gl
Chilli
Chilli71 said:
You can install' minimal ADB and fastboot' and the USB drivers for the phone on your PC. If the phone is not encrypted you should be able to browse the phone storage in an adb shell and to copy files or directories with adb pull.
gl
Chilli
Click to expand...
Click to collapse
I have tried that as well, the only way I can get the phone to appear under "adb devices" is to select "apply update from adb" via recovery, even then it's only via sideloads, running shell returns an error
XenoJin said:
I have tried that as well, the only way I can get the phone to appear under "adb devices" is to select "apply update from adb" via recovery, even then it's only via sideloads, running shell returns an error
Click to expand...
Click to collapse
Ill jump in this one to. im in a similar situation. I have a lg g vista that no conventional method is working to bypass frp. Device is not encrypted. My prob is. I believe if i can downgrade back to stock kk which the phone was released with it didnt hve frp then so bam im in. But lgflash tool wont downgrade. Always errors. Loads of diffrent settings have been made. Also followed guides to a t.
But in ure case to if it is possible to dlmode and odin back to kk or earlier u should the be able to skil the google login totally. I dont know if ure device came with kk from factory or lolipop. Frp was implemented in loli so kk should be good. Maybe
Two comments:
1) I have a Huawei G8 in front of me. I worked all weekend with it with bootloader/fastboot. I wanted to test the lock screen/adb behavior, But to my surprise ADB does not find it w/ and w/o lockscreen. --> There are different possibilities why the phone does not show up (it worked in the past with this phone/notebook, but quit working). Before you flash make sure that your setup is working (best with an identical mobile). It seems that USB connection can behave different in Bootloader/Recover/Android OS mode.
2) I made a dirty flash (w/o erasing flash) of Lollipop over Marschmallow last weekend. The result was that many directories including SDCard0 where not accessible. Also user data was not accessible. And you have always the chance that you mess something up when flashing and you loose the content.
If the data is really important your friend could pay a data rescue company (if you don't loose your face). I'm pretty sure that programs exist that can be loaded into RAM with bootloader (fastboot boot) that provide an interface to the PC (in the easiest case, adb again).
Chilli
Hi,
I bricked my phone, a SHARP Aquos C10.
After unlocking the bootloader I was able to install several rom. The last one was LineageOS 18.
I bricked the phone when I tried to replace LineageOS Recovery with TWRP by dint of trying.
The phone is not completely blocked. It gets stuck for a long time on the "battery" logo which replaced the "Sharp" logo when the unlocked it. After several minutes, it vibrates and restarts.
I can restart it by long pressing the OFF button, I can't turn it off, I can't put it in recovery mode.
I can just put it in download mode but unfortunately it is no longer recognized by the PC.
So, bricked or not bricked.
Thank you for your help.
Nobody can help me ?
Hallo,
if you still can go to the download mode, maybe not all hope is lost. Your phone might not have
a hard brick, but only a soft brick. Everything should be fine as long the download mode isn't bricked too.
I had a similar problem once with a tablet after flashing it.
You need to install the USB-Drivers for your device on your PC and then reconnect it.
This might sound ridicolous if you already have installed them, but sometimes
a deinstallation of the USB-drivers and reinstallation of the drivers might help.
I found the following site for the drivers:
"https://gsmusbdriver.com/sharp-aquos-c10".
If you prefer an official source, you can use: "http://www.sharpusa.com/Home/CustomerSupport/SharpCareCenter/MobileSupport/ADBDriver.aspx"
However both sources seem to look reliable for me, even if I can't test it, without having a SHARP device.
If you are not sure, you might compare it with other tutorials and look for reviews.
Installing the drivers can't lead to harm to your device until you don't connect it.
Things can't really get worse if you install the drivers. The only thing that could happen is, that either the PC will say that it recognizes the device or that no device can be recognized, so it's worth a try. Please report me, if it worked for you and you are able to flash again. I hope this will help.
With kind regards
dontdropme
Hello,
Thank you very much for your help.
Yes, I installed the USB drivers. I unlocked the phone for you I installed another rom.
I reinstalled the drivers following your links. Unfortunately that does not change anything. The phone is not recognized. No sound comes out of the computer when I connect the USB cable.
I tried on 2 computers, 1 on Windows 10 and in Windows 10 / Xubuntu dualboot.
When the battery is empty and I try to turn it on, a red battery will light up and flash. As I charge it, the battery changes color to green.
I don't have download mode if the cable is not plugged into the computer or the charger.
:/
Hallo,
the download mode is supposed to be only able to get started if you connect the device to the computer or another device, this is not strange. You need to go to the download mode and try to flash the stock firmware for you device. Try it at first without a device recognition of your PC and find out, if you need to do a hard reset before, to regain factory settings. I have listed, in color, a short number of things you could do now. If this still doesn't work only the SHARP team or a specialized company might help.
What you could do, is to ask the SHARP support for a source for the USB drivers and how to do a hard reset to regain the factory settings. I don't know which flashing tool you use for you device.
Normally if your device is not recognized by plugging it in to the PC-USB-Port the flashing tool shouldn't recognize it either, but it might be just an error of Windows, and the flashing tool is not allways depentent to the USB-drivers, but relies only on the question if you can go to the download mode, so you could give it a try to flash even in this case. Start the flashing software and look what will happen.
You said, that you have successfully flashed until now, which means that the flashing tool supports you device. If you can't flash now anymore, you might also not make a backup, which would be important, because the only things you could try now, is to find the stock firmware and flashing it.
If you haven't installed any important data on your system after flashing LineageOS or if you already made backups of your applications in a cloud or another drive you need not to care. It is possible that you will need to do a hard reset before. You can find on hardreset.info, in the section "All devices", how to do it or ask the SHARP support. If you fear you have still important data on your phone a backup is normally recommended.
Because flashing a ROM not only wipes your data, but removes the guarantee, the result is: Restoring the phone to a usable device by any helping team of SHARP's customer care service in you city, even if you have any service buildings, might be expensive in this case. To go around high prices you would need too look around also for other data restoring companies or specialists, if nothing works.
But at first, if you are able to do it; I would recommend to do a hard reset of your device, which should restore it to factory setting, which should make the drivers work.
Even if they don't work, ask SHARP for actualized USB-drivers. Try flashing also with and without working USB drivers, and find SHARP's stock firmware for you device first, which is a "must do", if you want to have access to the original recovery mode again. Flash this stock firmware after you have done a hard reset. After flashing the stock firmware you should be able to go to the custom recovery mode again, if not, only a specialized company or a help team of SHARP's customer service might help.
Hello,
The adb and fastboot commands wait for the device to connect.
SHARP support is not responding.
Hello, did you try "https://getsupport.sharpusa.com/Contact-Us/Product-Support"?
Because of the actual situation with the Virus, they might need longer to answer, so you need to be patient. As I see you already tried to connect your device after the use of CMD.exe. Installing the drivers with CMD and checking the Windows Hardware Manager if the Installation worked correctly is one way to do a driver install. I am sorry if this didn't work for you. If it does not, only a specailized soft- and hardware team can help, which could get expansive, but maybe not as much as buying a new device, so I hope for you Sharp will answer and give a correct Installation guide and that it will fit to solve your problem. I wish you good luck and that you don't need any other company than Sharp to help. I know that nobody is amused if all help and waiting does not help, after bricking bis device, but unfortunately I can't do more for you. I wish you success and keep your device in a safe place just for the case.