My little brother have a Rockchip based Tablet which is more than 3 years old. It named Symphony and device name on about the device have a different name of K11+. running JB 4.2.2. I never found it's origin and all other details on the internet. But I pulled its firmware with some tool and I have a backup of it. And successfully managed to perform its firmware updation many times. But, Yesterday I stuck on an error. That when I performed a wipe using the tool (I always makes it before the firmware installation) where it called "Erase NAND (IDB). Then my Laptop got error that USB device not recogonized. I tried many ways to overcome this error, even tried to re-install ADB, Driver etc... But nothing happened... So, Is there any hope of getting back ? All others even my smart phones were also works on same port and USB cable. Hope that someone can help me out...
Related
sorry if i posted this the wrong place but nevertheless here is what i need help with.
i was looking for a stable 4.4.2 rom to flash on my at&t note 2 and i found this http://forum.xda-developers.com/gala...-odex-t2802189
so i followed the instructions and flashed with odin and flashed the new bootloader since i was running lower than mj5
after flashing everything went well the rom was great until i wanted to take some photos from my laptop and send them to the phone.
the laptop recognizes a usb device but no prompt for folders or anything is being given, ive tried multiple usb cables and even multiple pcs to no avail.
so i tried reverting back to my old firmware 4.1.2 and the problem is still there
after digging around the computer in the device manager, the phone is being listed as SAMSUNG_ANDROID and is unknown followed by an error when i click properties which says:
This device is not configured correctly. (Code 1)
i also have kies and the official samsung drivers installed
To find a driver for this device, click Update Driver.
so i tried updating the driver which failed and said an error occured data invalid
i really need some help on this because my phone isnt being picked up by odin or download mode
please help asap
You might consider downloading a wifi or bluetooth file transfer utility. I used one of these to great effectiveness on my old phone.
I realize this isn't the ideal solution you're looking for, but sometimes you have to take what you can get.
warriorpanda said:
sorry if i posted this the wrong place but nevertheless here is what i need help with.
i was looking for a stable 4.4.2 rom to flash on my at&t note 2 and i found this http://forum.xda-developers.com/gala...-odex-t2802189
so i followed the instructions and flashed with odin and flashed the new bootloader since i was running lower than mj5
after flashing everything went well the rom was great until i wanted to take some photos from my laptop and send them to the phone.
the laptop recognizes a usb device but no prompt for folders or anything is being given, ive tried multiple usb cables and even multiple pcs to no avail.
so i tried reverting back to my old firmware 4.1.2 and the problem is still there
after digging around the computer in the device manager, the phone is being listed as SAMSUNG_ANDROID and is unknown followed by an error when i click properties which says:
This device is not configured correctly. (Code 1)
i also have kies and the official samsung drivers installed
To find a driver for this device, click Update Driver.
so i tried updating the driver which failed and said an error occured data invalid
i really need some help on this because my phone isnt being picked up by odin or download mode
please help asap
Click to expand...
Click to collapse
So you want to take photo's from your laptop and put them on your phone right?
Well why don't you get a micro SD card , put it on your computer transfer the photos then put the SD card in your phone.
pstuart82 said:
You might consider downloading a wifi or bluetooth file transfer utility. I used one of these to great effectiveness on my old phone.
I realize this isn't the ideal solution you're looking for, but sometimes you have to take what you can get.
Click to expand...
Click to collapse
using one doesnt make sense because now especially odin wont recoginize the phone so i cant flash or do anything
I'm hoping someone can help. I have an LG G3 D855 phone and is factory unlocked and running Lollipop 5.0. When I first got the phone (second hand), I was able to connect the phone via USB to my PC and was able to transfer files back and fore no problem. Until about 3 weeks ago, I am now unable to do this. The PC won't recognise the phone at all, all the USB connection does is charge the phone and I can see no option to get the phone to change to file transfer mode.
I had a look at Storage in the settings menu and I don't have the three dots that some people have spoke about. I have factory reset the phone and this hasn't fixed it.
I have tried using a different USB cable, this was the same. The drivers are installed (phone was recognized before). I have also tried the LG Suite, again same result. I also had a look in Device Manager for ACER something or other and this wasn't there.
I am currently having to use Bluetooth to transfer files back and fore to my PC and this is a bit slow. I'm assuming that an update LG have done has somehow broke the USB settings. I am also unable to root the phone (tried this before the USB stopped working and nothing worked) and possibly go back to KitKat 4.4.2 to even try that.
My phone has software version V20u-EUR-XX, Kernel Version 3.4.0 and build number LRX21R.A1439960697. There is no update available for my phone in the Software Update center.
After quite a bit of searching, it seems that this is a common issue but I have not found a solution to this. Can anyone help? Is there any firmware or software that I can try?
Thanks.
Assuming the OS is Win8/8.1 or Win10, have you already tried this?...
[How to fix] Windows 8/8.1/10 is not detecting my LG G3 device
http://forum.xda-developers.com/lg-g3/help/answer-windows-8-8-1-detecting-lollipop-t2967574/post57373374#post57373374
... or tried the suggestions in this thread?: http://forum.xda-developers.com/lg-g3/help/lost-usb-connection-mode-t2847857
Thanks for the reply. I am using Windows 7 Home Edition 64 Bit and had had a look for the ACER Composite ADB Interface in Device Manager and it wasn't there. Post #18 in the thread you linked to, I have no idea what kdz file I would need. Does this method need the USB to working?
Thanks for the reply and help.
I have D85520T_00.kdz and D85520U_00.kdz files. Can someone tell me if these are OK for my phone (and latest) and what the differences between the two are (apart from the file names?) Thanks again.
I couldn't tell you what the differences are between software revisions, only that 20u is newer. And I believe 20w is the latest available. I would probably try reinstalling the latest drivers from LG...
http://www.lg.com/us/support/software-firmware
... then again check to see if your PC recognizes the phone. If the "Charge phone--> Tap for more USB options" notification doesn't appear after installing the latest driverset, I'm not sure what else you could try. The LG Flash Tool needs to be able to communicate w/ the device when it's in Download Mode. You might be able to find something in the [Guide] LG G3 Stock Firmware (Go Back to Stock) KDZ & TOT Method thread related to the same problem you're having.
http://forum.xda-developers.com/showthread.php?t=2785089
Just a quick update, can't even get the phone into download mode. I press volume up, insert the USB cable in to the PC and all I get is the battery charging icon. I'll have a further look this weekend - not good so far!
Thanks again for the replies and help.
Firmware W seems to be flashable only via TWRP or ClockWorkMod just now?
I have been able to get the phone into Download Mode a few times (not all of the time) and when I run LG Flash Tool, it just tells me that the phone isn't connected. I'm going to assume that the USB port is in someway defective. Can't think of anything else.
Have you tried w/ a different PC and/or OS? Have you tried connecting the phone via different USB ports (USB 2.0 compared to USB 3.0 or vice-versa)? And I assume you've already installed the latest driverset from LG?...
http://www.lg.com/us/support/software-firmware
Yes, I got into Download Mode once or twice on the laptop. I'm using LGMobileDriver_WHQL_Ver_4.0.3. I have tried USB 2 ports on both my Laptop & PC. I've tried driver 3.81 as well.
OK, got a new USB Charger port fitted just in case it was the port that was wrong and it's still exactly the same! I did a factory reset and have setup the phone for now. During the factory reset, it does pop up with Updating Android and has 169 updates. If anyone here has the LG G3 and has it working file transfer wise, can you tell me what version of the LG USB drivers you are using? Is it possible an LG update has caused this?
Thanks.
It's fixed!!! I think there was an update yesterday for Android Devices or Services, can't remember which was made available yesterday, installed that, reconnected the phone to the computer just a few minutes ago and it has finally been recognised! I can finally transfer files between the phone and the PC.
It was an LG update that has fixed this.
At last.
I'd like to say thank you for all the replies and help.
Hi all,
I got given this Tab3 because the smd power socket connection guts were physically broken inside socket.
Fitted new power socket (I'm an electronics repair engineer by trade) and checked all pcb (printed circuit board) tracks leading from new fitted socket to ensure there were no hidden breaks ...... new socket refit was 100% successful .....with no solder shorts / bridges and no broken tracks leading to mainboard.
I left Tab3 on charge overnight and next day switched Tab3 on only to be greeted with dreaded .PBL and .PIT failed issue.
After extensive (days!) research I gathered together all necessary firmware and tools and decided that its an easy firmware fix if flashed to an original Samsung SM-T210 UK firmware.
(Please note I dont know past history of this Tab3 .... I dont know if it was rooted / upgraded firmware etc ..... I doubt it though as it belonged to a 7 year old)
Big issue ..... Odin flash tool won't show coms port connection on PC via USB (have tried 3 different laptops one with XP, one with Win7 32bit and another with Win7 64 bit. I've installed / uninstalled / reinstalled multiple Samsung usb drivers that were verified to work with my Tab3 SM-T210 model on each PC .... no joy. Even installed / uninstalled / reinstalled Kies from Samsung .... still wont connect when Tab3 is in download mode. Have kept PC device manager open and nothing appears in device manager. Also have tried 6 different makes of Usb A to micro Usb cables. Have disabled all antivirus, UAC, firewall and Win defender etc ... still no go!
When I go into download mode (power + Vol- +Home buttons) a warning screen does appear BUT it only shows right hand side of graphic warning ..... left hand side is totally grey from top to bottom. (LCD screen is not faulty as it displays full screen info on failed .pbl / .pit flash memory checks) When I then select Vol+ this vertical half graphic info and half grey screen disappears just leaving the backlight on .... which I assume means Tab3 is in proper download mode?
I can go to all recovery modes which allows me to factory reset and delete user cache etc .... it seems to go through the proper routines of reset but upon restart .pbl and .pit failed error in red memory check list is still there.
I can also try and flash firmware file from external sd micro card .... Tab 3 recognises firmware OK and shows Install ..../SD, but then after approx 5 minutes it restarts to failed .pbl /.pit error list again.
Apologies for long post, but from reading above issues can anyone please confirm ....
1) Is half graphic normal when going into download mode? .... or does this point to a previous incorrect or unfinished flash issue?
2) I have downloaded proper .pit flash (LT02) file and original firmware flash for my Tab3 ..... can I flash this any other way other than using Odin ....eg is there any bdm flash method (direct hard wired) flash method to motherboard from external programmer ....like they use for car ecu flash recovery?
3) As I dont know exactly whether Tab3 was rooted / flashed with wrong firmware / incomplete flash upgrade, is there a software tool that can attempt to list what firmware is on my Tab3 at present?
4) I can get into ADB recovery within recovery mode but havent a clue how to use this method .... is this a possible recovery method to use, as I can see SMT210 ADB device in PC device manager when going into recovery mode?
many thanks in advance for help, :good:
Tab3SMD
OK all, here's more info .......AND another additional issue!
I got stuck back in again tonight because not knowing anything about Tab3 ADB recovery mode was bugging me, so here's what extra I've done so far
While "poking my nose" into tonnes more Xda forum troubleshooting guides I discovered I might need PitMagic tool to try and sort my .Pit partition error via ADB recovery mode.
I tried to find Pitmagic but discovered this is now part of EFS Professional, so downloaded EFS Pro and found this got me nowhere as I needed to also install Android SDK .... which also requires Java Development kit, so I downloaded the full Android Studio and Java JDK 8u91 and installed all (about 1.2Gb and requires ~ 4.2Gb hard drive space!)
Anyway, I now ran Android Studio and then ran EFS Professional, opened my Tab3 into ADB recovery mode and connected Tab3 and PC via usb .....
All looking good EFS reported
Initialising ADB server ..... Okay.
ADB server is running!
Searching for device..... OK
Connecting to device .....OK
Checking device status .....
THEN BAMMMM ....popup from EFS
Connected device is currently UNKNOWN
Please ensure ADB server has been authorised by the connected device by confirming your PC's RSA fingerprint, then press OK to continue
like, wtf! .... one step forward and 6 back!
Can anyone please tell me what this means or better still how to proceed from here?
Anyone?
Anyone??? .....Tab3 is still soft-bricked
I did figure out how to use ADB flash recovery mode using PC.
Unfortunately this also did not allow me to flash any firmware (original or custom) due to admin permissions
(I think this is due to USB debugging not activated within Developer options).
I'm sorta banging my head off the wall with this one .... a bit like what came first? egg or chicken?, because since Odin isn't being recognised by the PC, I cannot flash rom and even though the PC fully communicates with Tab 3 in ADB mode, it won't allow me permission to sideload any flash files because I reckon I need root based permissions, and since the darn thing isn't booting fully, I cannot manually change anything!
I then started thinking about trying to sneak around this permissions issue by flashing CWM or TWRP, but again flash fails due to no permission.
All in all, for me this has been a great learning experience tackling the multiple Android recovery modes, and since I feel so close to cracking this non boot issue, I hate to give up and bin it.
Perhaps someone with much more experience can please help me here?
Is there any way of forcing superuser status on this Tab 3 SM-T210, so as to allow me to flash stock rom via ADB recovery mode?
many thanks in advance for your help,
Tab3SMD
Tl;dr: DM-VERITY error after upgrading, SIM card not recognized. Can't get fastboot to work to try out a solution. Everything is going to ****.
So... this one's a doozy.
I tried to install the update by dropping it onto my phone and using TWRP to install it, which I ended up having to update. After I updated, I get a brief second popup screen when I reboot telling me that there is an invalid DM-VERITY (it only pops up for a second). When the phone loads, it doesn't recognize SIMs.
I did some research and it looks like the issue can be fixed by flashing the stock recovery. So I go to flash the stock recovery, which requires the usage of fastboot. Which I always have problems with.
Sure enough, adb recognizes my device but fastboot doesn't. I have all the drivers downloaded, so I go check on my device in device manager. For some reason, it's always listed under "Portable Devices" no matter what I do... no matter whether I enable/disable USB debugging, MTP/PTP/Charging, etc. I was under the impression that a device not being recognized by fastboot meant that you had to go find it under "other devices" and manually update the drivers. However, the only options here are ADB drivers, not bootloader ones.
So I did more research. Turns out that Windows 10 is ****ty and you have to disable secure boot to install unsigned drivers. So I went into my BIOS, disabled it, booted into safe mode, reinstalled the drivers, and... nothing.
So I'm basically where I started and for the first time in a while, I have no clue what to do. Nothing's working. I even tried to load an older version of OxygenOS and install it with TWRP (sideloading didn't work), which didn't work. I'm totally stuck and I have no idea what to do.
If you don't care about your data, just use the unbrick guide method 2. Don't know about the first one, I have never used that. That will get you to a like new phone. You could even get 4.0.3 version, using the newer unbrick toolkit.
Windows 10 x64 isn't that sh**y. I've never had issues with the drivers, and they all install automatically (fastboot, adb, unbrick tool). They all work with 4 phones without any issues: OP3, Nexus 5X, Nexus 5, Nexus 4.
True, I had just unbrick my op3 2 days back by method 2 .
Well this was wild
So I did try to unbrick and got the Sahara communication error.
But I ended up fixing my problem! Someone on Reddit correctly pointed out that the dm-verity screen often exists simply as a result of unlocking the bootloader. I was assuming that one symptom caused the other. They suggested just reflashing OnePlus's 4.1.3 full ROM. I did it exactly the same way as I had when I got the error (with TWRP) and... it worked!
I'm astounded. My phone wouldn't work with fastboot, wasn't recognized by the unbrick toolkit, and had a host of other issues. I did 7 hours of work on it and the solution ended up being that I just needed to reinstall the OS (again). My hypothesis is that there was some hidden issue that resulted in part of the firmware being incorrectly updated, and when I wiped my device as part of my troubleshooting process it was ready to be reflashed with the OS.
Thank you guys so much anyway!
Hi All, sorry this is a fairly long post.
i recently "Upgraded" my SM-P605 to Android 9 and it has been working fine.
i have, however, been experiencing connectivity issue with file transfer via USB.
i have tried several cables (3 Genuine) including a brand new "Generic" cable and keep getting the "device descriptor request failed" error.
i have also tried multiple PC's, loaded all recommended Samsung drivers and finally relented and replaced the USB port in the tablet itself, which still did not fix the problem.
Convinced after all of this it must be software related, i then decided to re-install and earlier version of Android which i copied over to the Tablets internal memory.
i logged into TWRP and wiped the tablet ready to reinstall Android 7. and when i tried it says the zip file is corrupted.
i now have a tablet that wont load the zip file i have, wont read from an SD card in the tablet or OTG (via TWRP) and is unable to connect to a PC via a usb cable..
if anyone could offer any suggestions i would be extremely grateful as i dont want to "Dump" this tablet as i use it daily for work..
Why it does not read the SD card? I would expect that should work and should be the safest bet here...
-Maybe the zip file really is corrupt, which can be easily told by unpacking via pc.
-If the tablet can still charge the battery usb is most likely okay.
-Sdcards can fail by becoming read-only. Most easy to tell by unsuccessfully trying to format them in the tablet or pc , but e. g. under Windows you seemingly can successfully delete and copy stuff, everything as it should even after forced refresh via F5. But after reinserting the card or rebooting the previous state is back.
-ADB has been enabled in developer settings? Then you normally get a notification where you can modify usb mode. Charge-only won't work, but most of the rest should do (Dcim/mtp/msp...) .
-And all the time Windows has to recognize the device via PnP and auto-install drivers for the current usb mode. Besides the aforementioned storage drivers for flashing and communication a modem driver and virtual COM ports must be auto-installed.
In this department i had lots of trouble with a phone based on an old TI OMAP SoC under any Windows newer than seven. Only Download mode invoked on the phone itself was still working and only zseful to restore stock rom, while in the more flexible Fastboot mode the phone wasn't recognized by Windows.
Samsung devices seem to support Fastboot only, but call it Download mode.
To come to an end, if everything fails i'd recommend to install stock rom in "download recovery" (Fastboot?) mode via Kies. If this also fails try to put the P605 manually into Download mode (Power and Volume minus or plus), no need to press home button, as often advised. After this, work your way back to Twrp, custom rom and root.
@crwzar80
Try connecting the tablet to a Windows 7 PC/laptop, making sure it's on an Administrator account (so it can autoload/download needed stuff). Not Windows 10 or even 8.1, but Windows 7.
I had the same problem a while back ago; if your attempt with this method succeeds then report back; I had an unconfirmed hypothesis about this issue.