I recently attempted flash a ROM onto my Tab3 SM-110 using TWRP, flashing that on using a .tar.md5 file which was compatible with the device. For some reason I've encountered a screen which informs me that "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again," When I attempted to flash the .zip using TWRP. I don't know if this was because the ROM was incompatible, or if it simply ran out of power before it finished, as I wasn't there to watch it. So, following the helpful instructions that the device gave me, I installed Kies. It told me that my device wasn't supported, and Emergency Firmware Recovery doesn't find the device either.
I then moved to Odin, finding the firmware for the device on Sammobile. It was the correct software for the device, and I attempted to flash it on using Odin v3.12. The program gets stuck as File Analysis, and doesn't do anything until the battery of the tablet runs out and then the screen constantly turns on and off and continuously connects and reconnects. I searched the internet for this issues, and I've tired things such as waiting to plug in the device until Odin loads the .tar.md5 file completely, checking Re-Partition in the options, and attempting to reinstall the driver. I've tried putting the file in the AL, BP, CP, and CSC sections all at the same time, and individually; Nothing seems to help. The file from Sammobile was the Canadian T110UEUAOD1_T110XACAOD1_T110UEUAOD1_HOME.tar.md5, as I bought the device in Canada.
I've even tried setting up ADB and attempting to reboot the tablet into Download mode as another forum instructed. ADB couldn't find the device, and I was stuck there too. I did everything required for the setup, including downloading the entire thing from SDK and setting the environment variables on Windows. ADB does work on my Samsung S5 phone, so it isn't an issue with ADB itself, but with the tablet.
This is a relatively new buy, and thus I really don't want to loose it. I've been trying this for about a week now, and I'm open to almost any suggestions. I've also tried changing computers, changing ports, using official Samsung chargers, etc. If anyone knows anything, even if you regret to inform me that I cannot save the device, it would save me the stress of staying up well into the night searching desperately to fix it. The device cannot boot out of this message, which means no recovery, download, or any other type of actual booting; I've tried removing the battery to prevent the screen from popping up. I'm also given limited time with Odin, as the device doesn't want to charge when plugged into anything but an official Samsung Adapter, and thus I can't spend hours with the tablet connected to the computer.
If this helps, although I'm not exactly sure if it would, here are some specific numbers and information that is listed around the device and on the screen:
Product Name: SM-T110
Current Binary: Samsung Official
System Status: Custom
H/W Version: 0.2
IC: 649E-SMT110
FCC ID: A3JLSMT110
Related
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.
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.
Here you go:
https://1drv.ms/u/s!AshkuG2cY1T0xPZArSsy6iO1e_UnPw
This is a zip file with all the tools and files you need and instructions on how to use them.
What it covers:
Restoring bricked device (as long as download mode still works)
Unlocking bootloader (firmware dependent)
Rooting (any firmware)
Installing a custom recovery (any firmware)
Installing a custom ROM (any firmware)
I made this because all the guides for this phone were seemingly outdated, and some required tools and files were incredibly hard to find. Didn't want anyone else going through the pain I went through to break this phone open.
Thank you so much for uploading this. The charging port on my Nexus died and I have to use my old Note 2 as a backup, but I forget how this old piece of junk works. This should be very helpful.
I rooted and flashed twrp to boot to a triangle saying system software not authorized. Tried 3 firmwares and wont boot correctly. I got error about firmware update failed use kies... Kies won't do anything and kies 3 says unsupported device. On the 3rd firmware (root66 rooted stock ) firmware file I now am back to the original triangle system software not authorized by Verizon ..
How do I fix this?!?
robles4242 said:
I rooted and flashed twrp to boot to a triangle saying system software not authorized. Tried 3 firmwares and wont boot correctly. I got error about firmware update failed use kies... Kies won't do anything and kies 3 says unsupported device. On the 3rd firmware (root66 rooted stock ) firmware file I now am back to the original triangle system software not authorized by Verizon ..
How do I fix this?!?
Click to expand...
Click to collapse
Did you read my guide? You can't flash TWRP unless you successfully unlocked your bootloader with Casual, otherwise you are limited to SafeStrap. Also you can't restore with Kies, you have to use Odin and the files I've included to restore.
yambag said:
Thank you so much for uploading this. The charging port on my Nexus died and I have to use my old Note 2 as a backup, but I forget how this old piece of junk works. This should be very helpful.
Click to expand...
Click to collapse
Nice to see people still looking for something like this, so my guide wasn't for nothing!
I was geeked to see this!! but then i got "This item might not exist or is no longer available"
I take it back.. i let it sit on the "failed" page for like 2 min, and randomly it popped up with a download!
Well the auto bootloader didn't work, so now i'm at the root section. However i'm getting an error where ADB isn't detecting my phone. USB debug is on, and i'm definitely in media mode and not installer. The phone shows up in windows and looks good, but adb doesnt detect. I opened command prompt and ran adb /? and found adb devices -l, and it reports "list of devices" and theres nothing in the list. I can't imagine why it's not seeing it. I tried turning on and off debug mode, switching from camera mode to media, changing usb ports. still nothing comes up, but windows sees it fine. grrrr
*edit, well since we can't delete posts i'll leave this here, because i have to. But what i did was re-open the "no you verizon" and it showed DISCONNECTED also. I changed usb ports like 3 times, turned usb debug on and off, changed from installer mode, to camera, to media mode, restarted the phone and the computer multiple times.. and then it just all of a sudden was detected again. So i went with it and it seems to have worked.
-it took 3 times to actually work, you noted it may take multiples, and it sure did. I ran it through the command prompt so i could read the text, and it took 5 times longer and reported much more stuff when it actually worked.
-final edit: if you can't unlock your bootloader, you're still stuck with ditto or alliance from 2014, and lots of apps won't update on android that old. So if you thought this guide was some holy grail, it is not. But still useful if you need the assist, so thanks to the author.
Hi, total noob here, I just bought Verizon note 2 at a yard sale but there is a pin I don't know. When I went to do a factory reset it booted into TWRP, so I am assuming is rooted. Do I need to be able to get into the phone to use your tools? I know nothing about TWRP. I would like to install a newer Android version and unlock it so I can use TMobile. Thanks
Something wrong...
when i try to load this file from the packages folder i get an error message:
"md5 error! Binary is invalid"
none of the other three works for me. they all come back ailed.
any suggestions?
awesome! thanks for posting this, just found my old note 2 and want to get it up and running again for the kids.
Kudos!
Used this to get my Note 2 up and going again temporarily until the Pixel 4a release...
NOTE: I had strange issues with Odin on my modern X570 board (USB 3.2 Gen 2) where I did not receive any errors, yet the process would randomly seem to time out. Sometimes I'd get stuck at flashing boot.img, sometimes it would hang up at the start, once I got to flashing system.img and it seemed to hang....
Used an older PC circa 2013, no issues! Not the first time I've had issues with this newer motherboard and older USB flashing interfaces; had the same issue on my Note 8 (RIP) as well.
excited to try this.
I'm on some rooted 4.4.2 stock-looking rom. Recovery doesn't look custom.
Hoping to be able to install a working Oreo or Pie ROM
great post, bought a couple of these for almost nothing and am having fun playing with them. sadly they are both 4.4.2 but its great fun anyway.
SilentNightx said:
I made this because all the guides for this phone were seemingly outdated, and some required tools and files were incredibly hard to find. Didn't want anyone else going through the pain I went through to break this phone open.
Click to expand...
Click to collapse
Thank you for sharing. Always difficult to find those tools after a few years!!!
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.
Hi everyone. As I said on a former post, I have an Alcatel 1t 7 tablet; I need its stock recovery image, but even stock firmware is getting impossible to find. I mean, apparently there are firmware for that reference of tablet, but what happens, is that there are several models that share the same physical appearance, but have different hardware, so, they have different firmware, and by that reason, their firmware don't work for my tablet. Anyway...
The fact is, looking that its original firmware is not available on the internet, at least publicly; I'm trying to reflash my tablet by using alcatel's tool called "Alcatel Mobile Upgrade", a tool that I don't guess, would be unknown for many of you. So as I said, I'm trying to reflash it with it (and in the process, restore stock recovery, I hope). So I installed MTK drivers, installed the version recommended for this tablet, followed program's instructions, but when I reach step 2 of 4, the program warns me saying this: "Read terminal information failed. Unplug device, remove the device battery and plug it again - Repeat step 2 and try again".
The issue is, that its battery is internal, not removable; even, is soldered to the board. And I must add, that at first, when I bought this tablet and began to "experiment" with it, I was using SP flash tool, and it was giving me almost the same warning that Alcatel mobile upgrade, but later I discovered what that was a fail of the used sp flash tool version. On a webpage, someone recommended a specific version of sp flash tool to fix that issue; I mean, that I could download firmware to the device without having to "unplug battery"; and It worked.
So first ¿How can upgrade my tablet by using that program?¿What am I doing wrong?¿ Which device must appear under device manager, to it can work?¿mtk usb port, Mediatek DA usb VCOM, Android preloader, or which one? And second, ¿Could be this problem, due to alcatel's mobile upgrade version?
let battery drain to make sure device is powered off. you only have preloader mode for a second - within this time pick up in device manager and install preloader drivers.
if drivers installed correctly, first start flashing, then connect phone. flash tool will keep device in preloader mode for the flashing time period
aIecxs said:
let battery drain to make sure device is powered off. you only have preloader mode for a second - within this time pick up in device manager and install preloader drivers.
if drivers installed correctly, first start flashing, then connect phone. flash tool will keep device in preloader mode for the flashing time period
Click to expand...
Click to collapse
Thank you for replying. Definitely using Alcatel mobile upgrade is not an option, at least to me. I mean, I couldn't make it work in any way. "Fortunately", after an exhaustive search, I could find a post on internet, that recommended for a similar issue, to use Sugar MTK; the publisher shared this program and its credentials, for can use it . So I downloaded and used it, and I could restore my original stock. Now my issue is to port it to TWRP, but now I'm gonna to write a new post about it.
link me to the sugarmtk