Hey,
For more than a week I couldn't remount the SDcard, caused by a bad flash. :crying:
I tried awfull many times on all different ways with Nand erase, bootloader, pit, PDA and all possible data and variations between them. All flashing occured from my laptop and PC several times
In many threads also they repeatedly mention that error while flashing can be caused by drivers and installation and solved using a different USB ports whether to restart, and flash with a new clean installation. So I tried also those manners.
What could be the problem
Until I thought ..... on the differences in transmission speed ... between Compuer and smartphone :silly:
The laptop I use has an Intel i7 core processor and 16GB of memory. Moreover, there are USB3 ports wich tranfer data 10x faster than regular USB2 ports. My PC has the same configuration, and has in addition a SSD on wich the whole transmission between the disk and processing also increas the acceleration. Both are very fast computers, as you can see, and flashing occured on both in no time.
And so after a week error and trial and most of all reading on XDADeveloppers, I thought this transmission speed also could be the cause of the problem ....
So I installed the stockroms, data and Odin on my old laptop, I2 core and memory 2GH and USB2 ports and ..... yes yes yes ... in only one flash everything went well and result perfect.
- Check Auto-reboot, F. Reset Time and Nand Erase
- Stockrom on PDA
- Start and fash
- When rebooting pull ou the battery
- enter recovery-mode with Audio Up / Menu / PWR.
- wipe data / factory reset
- Reboot and .... everything is smooth and OK.
I hope this thread about the experience of transmission speed difference may be helpfull for other Samsung smartphone lovers
:silly:
El
Related
Hi, I have reflashed my ROM I dont know how many times. Yesterday I tried to connect via activesync on a new ROM and it wouldnt connect. These are some of the things that happened:
Device orange charging light flashes a few times then goes off [never seen THAT before]
Activesyc menu comes up on device but activesync doesnt connect
Get 'this device can perform faster' message on desktop
Sometimes get USB devce not recognized on desktop
SOmetimes device orange charging light it stays on if I plug direct into PC but still doesnt activesync
I have tried to connect as DISK DRIVE but I dont see the device on my PC.
Have tried different ROMS, 6.5, 6.51, sense 2.1 and 2.5 but all have same issue. Have also tried connecting to other computers. same issue.
Have played around with USB to PC menu options (enable / diable faster data sync etc) but doesnt make a difference.
Anyone had this problems? Thoughts?
Have you tried diselecting "ask me 1st about usb connection type when I connect the device to the pc" under USB to PC settings
It worked for me
This is the exact problem I am facing!
I tried everything - as diskdrive, activesync (with/without speedup), etc.
On many ROMs, even the original one (WM6.1)
Can't connect - every PC gives an 'unknown device' and on some ROMs I cannot charge via USB, only via mains...
I also tried without the question on connection.
Just some thoughts:
Do you have corruptions on screen sometimes? (Some graphical glitches)
Any .CAB files you cannot install?
Did you try to reflash the same ROM more than once?
tried to connect without card in the device and in flight mode? (Uses less power)
With me it started after a ROM flash from Miri... (I don't blame him!!)
The Hard SPL did not give me any problem, the radio was not flashed, just the OS. But reverting did not help.
I certainly hope you will find a solution, since I have the exact same problem!!
Do you stil know what ROM you flashed when this problem occured?
I reverted to original ROM 6.1 AND 6.5 which included everything - boot, radio, os, stardup image. But it did not change!
I figured it out after trying everything i could: i think its a hardware problem. I have dropped my devicetoo many times, or plugged it in too many times. Who knows.
ekerbuddyeker said:
I figured it out after trying everything i could: i think its a hardware problem. I have dropped my devicetoo many times, or plugged it in too many times. Who knows.
Click to expand...
Click to collapse
And how did you figured it out? Did you return the device to the shop?
I have this exact same issue except I am on AthineOS... I thought it was my PC until I read these posts. No OS updates or any other machine updates were performed except on my device. Any clues as to a fix?
Somehow I don't think this is just hardware.
I did drop my device once, but that was even before first flash. After that it still worked.
So, some weeks later I HSPLed without any problem. After that the device still worked.
Then, after investigating which ROM to use I flashed the ROM a few days later.
Right after the first flash it all still worked. So, had to flash another and from that moment on the device cannot be reckognised by any PC.
I still think it has something to do with the flashing. I think the device does not give correct feedback when it receives some commands from PC (eg. the command to reply the device type/number)
Does anyone know a program which can check the USB port for the HTC Touch Pro 2? Just to test wheather the connector pins are ok?
download activesync 4.5 and run the setup. it will perform a repair. that usually solves the problem. if not, try a different usb cable and try plugging into different ports on your pc.
crazythunder said:
download activesync 4.5 and run the setup. it will perform a repair. that usually solves the problem. if not, try a different usb cable and try plugging into different ports on your pc.
Click to expand...
Click to collapse
These are the first things done. And this was already written in here.
It happens with many PCs, including some on which the device never connected to.
Also tried different cables, ports, etc.
Also disabled the fast transfer etc. etc.
Even tried several other ROMs, inclusding original Dutch 6.1 and Dutch 6.5
I'm having the same issue. I can connect via bluetooth, but not usb. And I'm stuck with 6.1. I was tole my phone was brand new, but now I'm starting to think otherwise.
waynehead05 said:
I'm having the same issue. I can connect via bluetooth, but not usb. And I'm stuck with 6.1. I was tole my phone was brand new, but now I'm starting to think otherwise.
Click to expand...
Click to collapse
Some questions, to verify this is due to flashing or is a fault in the design of the device...
- Where did you get the device?
- Have you flashed the device?
- Did you accidentally drop the device?
hi just to say had a completely orignal o2 xda orbit 1 flashed with new rom everything worked perfect before now active sync plays up i can sometimes connect but get usb device not reconigsed then click cross then pull out usb then reinsert then active sync connects works fully functional then after 5 min it disconects this is driving me mad as use active sync for a fast internet connection on my pda as my wifi is crap
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
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...
Hey,
I have a problem. Since a few days I could observe that the battery drain are highly increased, up to 40% over night.
I decided to wipe my phone and flash the newest firmware MIUI10. I put a USB cable in my phone and connected it to my PC.
No response.. huh? Ok, just save my personal files via WLAN, no problem. Done.
I goes to TWRP and wiped all datas. Then I rebooted into Fastboot Mode (volume - and power), done.
I started MI flashing tool (in advance I've downloaded the firmware from officall MI website), connected my phone... nothing happenend. Tried several computers, I also tried to connect a USB device via OTG cabel in TWRP. Nothing works.
Whats going on? Any ideas? I'm really frustrated. The phone is just 6 month old, I flashed firmwares many times before. I think the problem is defective USB port.. but maybe I have just a simple logical error?
Thank you very much in advance.. and sorry for my english, I tried my best.
Best regards
René
I had a problem to transfer files, too. But it worked to adb sideload.
Is it recognized by adb?
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.