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.
Related
Hello All!
Relative noob here...but more seasoned all the time. Firstly my viewpad device info from FTM:
SWVer=3.410
Model: FM6-001
HWVer: 107
In a nutshell: My bluetooth wasn't turning on (would turn on..then off). So tried to fix by:
1) Rooting and install CWM 5.0.2.6 (awesome tool BTW) and various ROMs, all done with success.
2) No good, oh well now want to give up. Contacted Viewsonic got RMA to return unit..however now concerned they'll not honor warranty if I rooted the device (sigh). So thought I'd return to stock. I did backup..but was already rooted when I thought of it.
3) Trying to return to stock using many versions Sutl3 and Sutlr...and on different PCs none work..once it boots to CWM menu...just stalls with error eventually.
4) Tried to install Napster's CWM with Recovery Menu to be able to return to original state with stock recovery. My version of CWM won't install it...errors out (another great tool though by the sounds of it).
5) Can't use fastboot..never sees device...although ADB works OK. Believe that the Bluetooth issue may be a hardware problem and may be effecting devices ability to work in "download mode". Note that HS-USB device is never present in device manager in Windows even though driver is installed.
So...my question...how can I return my device to stock with one of the below .nb0 files without stock recovery, sutlr or sutl3?
Files I have:
FM6-3310-0-5029-A02.nb0
FM6-3350-0-1008-A01.nb0
Can I somehow use CMW? Can I somehow use adb and "flash_image"?
Will super appreciate any thoughts!
Many thanks in advance!
Johnster25
If I remember correctly, you use SUTL3 from Viewsonic on your PC with the *.nb0 file in the same sub/directory - and just run it to flash the stock ROM or return it to factory condition, you do NOT use CWM to flash or re-install the *.nb0 file ... Part of this process involved overwriting the CWM installed on your rooted device & reversing it to become unrooted, look under the Development subforum here in this section as there's a link/discussion about how to restore, please double check on the details written up.
Also, make sure you have a mSD card in the slot - and that the USB drivers are loaded & running (they should be installed already back then) - might want to power down & restart the PC and do the same to the Vpad7.
Let us know how it go & good luck !
Many thanks for your response.
Well, what has happened when I've used SUTL3 so far is that I select the .nbo image I wish to flash, then the program restarts teh VPAD7 into recovery mode.
From what I've read, after a few moments the phone is then supposed to enter some sort of "download mode" whereby the new image is pushed across the USB cable.
It's at this point with SUTL3 seems to error out, and the phone simply remains in CWM.
I've read a few posts that suggest that not using the correct image could produce a response like this, so I'll retry again this PM having tried re-downloaded the two .nbo files I've tried, and one I've not tried.
Will let you know how it goes!
J.
Hi Again,
OK I've retried it with a fresh copy of SUTL3, and new .nb0 files. Still no good.
Take a look at the enclosed pictures. The first time I try to run SUTL3 the device not configure error shows up. By this point CWM is showing on the VPAD7. I try to run SUTL3 again in this state and now the device not detect error shows up.
So all in all it seems to me that the device when in CWM mode is not exposing an interface to the computer...or the computer lacks the driver needed to utilize the interface.
I've also enclosed a picture of my windows devices when the VPAD7 is connected, as well a copy of the drives that show up when it's connected. The only time the drives change is when the VPAD7 is in CWM mode, at which time the H: drive (where the adb program are) is not present.
So am I missing a driver?
BTW: Have tried to copy down the synchronization program that is on the H: Drive and ran it while running SUTL3...thinking somehow it acted like a bridge to the VPAD7 (I've seen some posts that suggest this). Still no good.
J.
OK..one more piece to the puzzle...or maybe off the trail...but when trying on two differnt PCs when the VPAD7 is first plugged in I get one set of driver installs...and note that the HS-USB has an error.
Later when trying to run SUTL on it...another set of driver installs...again HS-USB error.
See enclosed.
try run sutl with viewpad in FTM mode that worked for me good luck
I have same problem before..n my solution is change back CWM with old ..mine to CWM 2.5.1..found that CWM 5.0.2.6 got problem with SUT L3..and everythind done successfully..as long u can still access ur Viewpad to change CWM its ok..
Wow! Thanks so much for your reply! This would be a huge help. Any idea where I might be able to find that older version of CWM?
Alleycatzero you're a genius! Running SUTL in FTM mode has done it!
THANK YOU!!!!!!!!!!!!!!!!!!!!!!
Johnster25 said:
Wow! Thanks so much for your reply! This would be a huge help. Any idea where I might be able to find that older version of CWM?
Click to expand...
Click to collapse
This is under the Development section - just d/l and unpack the zip file, copy to mSD card & follow the instructions. This verison should be the earlier one and I personally find it worked best together with ext3 and/or ext4 partitioning as needed.
http://forum.xda-developers.com/showthread.php?t=1015005
The issues with SUTL3 and other apps not working/running has to do with the usb drivers not auto-installing & running as they should, try to uninstall Vpad7 drivers, reboot the PC - turn off any firewall and anti-virus software, connect the Vpad7 and let it finish installing/rebooting both devices again. Then, turn back on antivirus & firewall so that you will have easier time flashing rom, connecting mSD card & copying/moving files, etc.
Hey guys,
a friend's Galaxy S2 (GT-i9100) hangs in a boot loop after updating Android (she says). She asked my if i could rescue her photo's, contacts, etc...
Booting Phone to Download-Mode works, connecting then via USB Windows 8 device manager prints USB\DEVICE_DESCRIPTOR_FAILURE as Hardware-ID.
There's no custom ROM installed, the device is not rooted and there's no CWM installed.
In Download mode, there's no option to "apply update from external sd card".
Tried "wipe cache partition", still boot loop.
Any ideas?!
EDIT:
I've tried to use/install various drivers. But IMHO if there's no Hardware ID / Vendor ID in the Windows Device Manager, Windows can't decide which driver matches for this device. So, if there's no device driver loaded, there's no chance for Odin or adb?! Correct me if I'm wrong.
Same as everyone else who's trying to do an Odin flash & having problems; Hopper8's 'Odin troubleshooting' thread stickied in General - go through the troubleshooting steps methodically (pay particular attention to the ones that relate to connectivity as that's the problem you're obviously having). Don't be surprised if your only option is to use another PC though given previous instances like yours I've seen.
Also, why would there be an option to 'update from external sd card in download mode ? You seem to be confused between it & recovery.
Download mode is very 'low level'; the only option you have is to get a stock rom from Samfirmware & flash it with Odin. This may/may not fix the problem. If it does, no data will be lost. But it's quite possible you may need to do a factory reset after the flash to fix, or even in some cases, flash the 3 part firmware linked in the thread I mentioned - in both cases this will wipe the phone.
Yes, you're right, i've mixed up Download & Recovery Mode. But i hope you know what my problem is.
Tried these steps (although another laptop using Windows 7), but no success.
I have another GT-i9100 which is successfully recognized by Windows 7 & 8 using Odin v1.85.
Is here any chance to extract / backup the user data from the device?
Btw:
If I boot it in Reocvery Mode, and choose "apply update from sdcard", it's possible to browse through /storage/sdcard0. It's soo depressing to see the user data and have no chance to backup them :silly:
Unless you either get a stock rom on the phone or get the phone & PC to connect to each other so you can maybe use ADB to pull the data, you have no other way to access that data.
If after trying everything in that thread for a day or two & you still have no joy, I'd be looking at replacing the USB board in the phone (you mentioning another I9100 can connect to the same machine just fine makes me suspect this might be the cause). This is a more & more common fault with the I9100 as the period since it was released increases, and this will absolutely cause the connectivity issues you're seeing. Unfortunately, you don't really have a way to test for this definitively, best you can do is replace it & see if if works.
However, fortunately, this is easy & cheap (~US$10) to do yourself. If you decide to go down this path, search for KeithRoss39's guide in General (search for 'replacing USB charger board'/similar). This guide has all the info you need to get it done painlessly.
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 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.
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.