Related
Hello, I recently decided to root my phone and place Cyanogenmod on it. When I did that I realized my radio was no longer working. In an attempt to just get back to a working phone for the time being I flashed a rom that I believe was just for the Nexus S and not Nexus S 4G. Due to my stupidity I am unable to communicate from the device to my computer using USB. When I attach the device to the computer nothing happens. The device does not even appear in the device manager. I have tried on multiple computers as well. On top of that the rom seems to have put me back into the stock recovery. If anyone could help me figure out just how to get USB working again I would be very appreciative.
I should note that I can still transfer files to the phone using the sd card or via ftp.
Thank you for your time and help.
Change the USB cable?
Yes, forgot to mention that. I have tried 2 cables both of which work on other devices.
What if you hold in the middle of the volume buttons (i.e. both up and down at the same time) and keep holding, then plug in to your usb port? It should come up as download mode. If it will do that you might try using Odin.
Or try a different machine perhaps?
are the drivers the same for the S as the 4g?
do you have clockwork on the phone or have you tried to run recover by holding volume up and power?
just throwing things out.
Hello, I appreciate any and all suggestions and help.
I have Odin downloaded and installed, but the computer can not find the device so Odin can not do what it needs to do. This is even the case in download mode.
In terms of recovery I am on the stock recovery. I was on clockwork but made a small mistake and now am back to stock.
I know if I can just get the computer to see the phone exists I can fix it.
If you can find the full OTA package for NS4G, you can try putting it on the SD card and flash it via stock recovery.
Also another thing worth trying is connecting the phone to an Ubuntu machine and see if it's detected or not.
I have tried looking for the original full OS. I will continue looking, but the different OS thing is a good idea I did not think of. I will attempt that now. Thank you.
I installed Ubuntu and the Android SDK and Ubuntu was unable to see the phone as well. I am going to keep searching for the original firmware to see if that will fix it. Thank you for your help so far, it is greatly appreciated.
I have found the only rom my phone will accept now is
Android 2.3.4/GRJ22/KRKC1 Radio/KA3 Bootloader
Which is for the M200 variant. This apparently the Korean version.
Problem: Cannot get my Samsung T959V to connect to the computer in order to flash/root. Always gives the same "USB Device Not Recognized" error when I plug it in to the computer.
My Progress: Before you guys throw this questions out, let me tell you what I have tried so far. I have been trying to get this damn thing connected to the computer for about 3 weeks now. I have sat down on my computer going through the xda forum in detail trying to find an answer. I know the process of flashing and the xda contributors have some great guides to help us along the way, a big thanks to all ur hard work, but no matter what, I cannot get the phone in download mode or get it connected to the computer.
* I have read the Download Mode post and tried all 5 ways without luck.
* Have read all things related to Keis Mini and how it sucks when it comes to the T959V and other ppl have had the same problem.
* Have tried connecting in Keis mode, usb debugging mode but still the same error.
If someone can help me get my phone connected to the computer, I am sure I can take of the rest since everything is available on the SGS4G Bible, thanks for that also.
Is there anything I have missed or not tried yet? Please help. Thanks in advance for anyone who reads this post as it is my first. Usually I don't have to post since all the documentation is always up-to-date and available but this problem is killing me
Additional Information: Bought the phone from a cell-phone store I use to work at. Has Android 2.3.6 on it. Have done the factory reset and tried to get it to connect, no luck. Not sure if it has been flashed before, pretty sure it hasnt but the flashed download mode method didnt work also. Have android-sdk installed and have tried pointing the .inf file to the google usb-drivers in the sdk, no luck. Download both 32-bit and 64-bit drivers for this phone from multiple locations, still no luck trying to connect. Have also tried multiple computers and multiple v9 cables, no luck.
Have you installed the Samsung drivers? You mention google drivers but samsung has it's own. You should be able to find them in the noobs guide to Odin thread. DL mode should work as well regardless of what drivers you have installed. Pull the battery, plug usb into computer, plug phone into usb, hold down BOTH vol + and -, insert battery. I've never not seen that method work.
hechoen said:
Have you installed the Samsung drivers? You mention google drivers but samsung has it's own. You should be able to find them in the noobs guide to Odin thread. DL mode should work as well regardless of what drivers you have installed. Pull the battery, plug usb into computer, plug phone into usb, hold down BOTH vol + and -, insert battery. I've never not seen that method work.
Click to expand...
Click to collapse
Yup tried both 32-bit and 64-bit drivers on multiple computers. Tried the download mode method u said also. Trust me have tried everything I have read about and know, but no luck.
But the phone charges fine? Could be a bad USB port. Or partially bad. Have you tried a jig? If that doesn't work I'd say your hardware is screwed up somewhere.
hechoen said:
But the phone charges fine? Could be a bad USB port. Or partially bad. Have you tried a jig? If that doesn't work I'd say your hardware is screwed up somewhere.
Click to expand...
Click to collapse
Yup it charges fine. Both when I plug it into the wall and the computer. What's a jig? Don't think I have tried that yet. If something can let me know for sure its a hardware problem, then I will stop obsessing over this, hahaha. Thanks for ur help btw.
A jig is a nifty little device that plugs in to your USB port on the phone and then gets you to DL mode. Their mostly used to recvover from bad flashes(like flashing the wrong phones kernel). Here's a link:
http://www.ebay.com/itm/Download-Mode-USB-Jig-Samsung-Omnia-7-Galaxy-S-4G-/250877662279
If your cheap like me or just wanna make it fast here's a guide to making your own.
http://forum.xda-developers.com/showthread.php?t=1604707
hechoen said:
A jig is a nifty little device that plugs in to your USB port on the phone and then gets you to DL mode. Their mostly used to recvover from bad flashes(like flashing the wrong phones kernel). Here's a link:
http://www.ebay.com/itm/Download-Mode-USB-Jig-Samsung-Omnia-7-Galaxy-S-4G-/250877662279
If your cheap like me or just wanna make it fast here's a guide to making your own.
http://forum.xda-developers.com/showthread.php?t=1604707
Click to expand...
Click to collapse
Awesome bro. I will see if I have time to make the jig, if not i will just order it.
Also, is there any way to flash/root without DL mode or USB debugging or using Keis? My recovery mode works but that's all. Was wondering if there was a way i could flash/root from the 'apply update from sdcard' option in the recovery mode?
Seems like a driver error have u tried one of the heimdall one clicks http://forum.xda-developers.com/showthread.php?t=1358498
They will put u back to stock with a modified rooted kernel .
If anything try and manually point to the drivers in device manager. Or download android sdk and use the google drivers ?
rangergiya said:
Also, is there any way to flash/root without DL mode or USB debugging or using Keis? My recovery mode works but that's all. Was wondering if there was a way i could flash/root from the 'apply update from sdcard' option in the recovery mode?
Click to expand...
Click to collapse
There was with Froyo but with GB it's all been put into the kernel. So not that I'm aware of. However one of the GB leaks changed the key mapping of the phone. I forget which one but that might be the issue. Go to settings>about phone>build number and let me know what that says. post the base band as well.
hechoen said:
There was with Froyo but with GB it's all been put into the kernel. So not that I'm aware of. However one of the GB leaks changed the key mapping of the phone. I forget which one but that might be the issue. Go to settings>about phone>build number and let me know what that says. post the base band as well.
Click to expand...
Click to collapse
As requested,
Build number: GINGERBREAD.VUVKJ6
Baseband version: T959VUVKJ6
Well that is the official GB release so now I officially have no idea why you can't get into DL mode. Get the jig and let me know if that works. Good luck.
hechoen said:
Well that is the official GB release so now I officially have no idea why you can't get into DL mode. Get the jig and let me know if that works. Good luck.
Click to expand...
Click to collapse
Will do. Thanks for ur help.
I downloaded the terminal emulator app and tried doing 'reboot download' but says 'operation not permitted,' any way to get around that? Or any other non-button or non-adb way to get into download mode? Other than the jig? Or is it possible to get su privileges on an unrooted device for the 'reboot' command to work in the terminal emulator app?
It's giving you "not permitted" because you don't have root. Have you tried Super One Click to root? If you can get SOC to root it you can use terminal to force DL mode.
If you haven't hears the link.
http://shortfuse.org/
DL 2.3.1. It should come with the android drivers as well. Worth a shot. If it doesn't work it doesn't damage the phone at all.
hechoen said:
It's giving you "not permitted" because you don't have root. Have you tried Super One Click to root? If you can get SOC to root it you can use terminal to force DL mode.
If you haven't hears the link.
http://shortfuse.org/
DL 2.3.1. It should come with the android drivers as well. Worth a shot. If it doesn't work it doesn't damage the phone at all.
Click to expand...
Click to collapse
Im trying it now but for SOC to work, i have to have the proper drivers to get my phone connected. Will see whether the drivers that come with SOC work for my phone.
No luck with the SOC 2.3.1 drivers. They r the same as the android-sdk drivers
Will try the jig. Hope it works.
Have you tried using this DRIVER SWEEPER to remove the drivers?
eollie said:
Have you tried using this DRIVER SWEEPER to remove the drivers?
Click to expand...
Click to collapse
And then what? I've tried to get the phone connected on multiple computers without any luck. Uninstall and reinstall didnt give me any results.
rangergiya said:
And then what? I've tried to get the phone connected on multiple computers without any luck. Uninstall and reinstall didnt give me any results.
Click to expand...
Click to collapse
Im sorry I am having mouse issues that deleted part of my response..
Sometimes a residual driver will not allow you to properly install the drivers. I had a LG driver from my old phone that was conflicting with Samsung driver.
Also this is a new root process. I do not know if it will work or not. But Hell its worth a try right?
http://forum.xda-developers.com/showthread.php?t=1652825&highlight=root
eollie said:
Im sorry I am having mouse issues that deleted part of my response..
Sometimes a residual driver will not allow you to properly install the drivers. I had a LG driver from my old phone that was conflicting with Samsung driver.
Also this is a new root process. I do not know if it will work or not. But Hell its worth a try right?
http://forum.xda-developers.com/showthread.php?t=1652825&highlight=root
Click to expand...
Click to collapse
Thanks for that link. I will try it out and give an update here.
rangergiya said:
No luck with the SOC 2.3.1 drivers. They r the same as the android-sdk drivers
Will try the jig. Hope it works.
Click to expand...
Click to collapse
Just to make sure you had usb debugging and allow non market apss both CHECKED right?
Hello everybody,
I am new to the forum and also new to Androids. After years of using iPhones and finally becoming fed up Apple, I've decided to try something new (please don't judge my prior smartphone selection and start posting opinions about the 2 operating systems, I do not want this thread to turn into one of the "battle of the phones" thread that I've experienced many times on iPhone forums). My friend recently got an S3 and had no use for his Galaxy S 4g, so he gave it to me so that I could try out an Android. There was one issue though, he said that the phone would not get past the Galaxy S screen and would keep re-booting itself (stuck in a boot loop). He said if I could figure out a way to fix it then it's mine.
That being said, here's my dilemma. I've tried many different methods to get the phone out of a boot loop. The first method I tried was putting the phone into restore mode and selecting the "reinstall packages" option. After this executes I get the message:
E:Can't mount /dev/block/mmcblk0p1
(no such file or directory)
E:Can't mount SDCARD:update.zip
Installation aborted.
After some further research I discovered a nice little program called Odin I read a lot about Odin and how to properly use it. After trying at least 5 different methods to get the phone into download mode with no success, I purchased a jig. The jig did the trick and instantly put me into download mode, I was ecstatic and hopeful that I could now fix the phone with Odin. I connected the phone to my PC in download mode, but Odin still didn't recognize the phone (I tried many versions of Odin, 1.85, 1.87, and the most recent 3.07). I do have the latest drivers for this phone, which I downloaded from Samsung's website. The phone will charge through the computer but the computer does not recognize it otherwise and will not allow me access its mass storage (I am running Windows 7 64 bit). I have tried using a different USB cable, and I have tried to use a different PC, the other PC I used popped up with a message saying that Windows could not successfully download the drivers (that was after I downloaded the drivers from Samsung's webpage and plugged the phone into the computer). I've even tried transferring stock firmware onto an external SD card and loading it onto the phone from restore mode (is that even possible to do?). I have also tried running Odin in compatibility mode, still didn't detect the phone. I should probably also mention that Kies Mini also does not recognize the phone. I asked my friend if he ever tried rooting this phone and he said no, so I'm assuming this issue has nothing to do with a failed attempt to root.
I really want to get this phone working, but I have run out of options to try. I am hoping that someone on here has a solution for me from a similar experience. After reading through the forum, I have noticed that people on here are very helpful and also very friendly; something that I can say is very different from some of iPhone forums I've used. I apologize if there is already a similar thread to mine, I've read through many threads and none of the solutions have worked for me. I also apologize for my first post being so lengthy, I just wanted to state all of the methods that I've tried to fix this phone. Thanks for your replies.
Hi hubbs134
You have come to the right place.
First,
I suggest you read a little bit about this phone and how to put it in Recovery (by holding Volume Up + Volume Down + Power until you see the SGS4G splash screen) and Download modes, it will help you in the future.
You can find it all in the Wiki.
Second, use this guide to One-Click Heimdall your way to Stock KJ6 2.3.6 Gingerbread ROM (latest official ROM for this phone).
If you use this file (instead) with that guide, you will also get phone rooted, or else you will need to make another flash of a rooted kernel (as the guide suggests).
Now, if you have the official latest stock, but still want some ICS/JB lovin', if you have CWM recovery v5 (you will see the recovery info once you're in that mode), you can flash CM9/AOKP/HebMIUI/UltraGen/RemICS/CM10/Slimbin/etc. etc. etc. ROMs.
Enjoy and welcome aboard!
P.S what the @#%#$ were you doing with an iphone ?
itzik2sh said:
Hi hubbs134
You have come to the right place.
First,
I suggest you read a little bit about this phone and how to put it in Recovery (by holding Volume Up + Volume Down + Power until you see the SGS4G splash screen) and Download modes, it will help you in the future.
You can find it all in the Wiki.
Second, use this guide to One-Click Heimdall your way to Stock KJ6 2.3.6 Gingerbread ROM (latest official ROM for this phone).
If you use this file (instead) with that guide, you will also get phone rooted, or else you will need to make another flash of a rooted kernel (as the guide suggests).
Now, if you have the official latest stock, but still want some ICS/JB lovin', if you have CWM recovery v5 (you will see the recovery info once you're in that mode), you can flash CM9/AOKP/HebMIUI/UltraGen/RemICS/CM10/Slimbin/etc. etc. etc. ROMs.
Enjoy and welcome aboard!
P.S what the @#%#$ were you doing with an iphone ?
Click to expand...
Click to collapse
Thanks for your reply, I have read a lot about this phone and know how to get into download and recovery mode. I tried the method you mention, however, when running the command window I get errors for both roms you suggested (i attatched a screen shot of the errors I'm getting). Do you know how I can fix these errors so that I can proceed with the rest of the tutorial? Thanks.
PS I only had an iPhone because I had yet to discover how bad a** Androids are
It sounds like you can't use Odin because of a windows issue. Try installing linux. I use ubuntu
Sent from my HTC One X+ using xda app-developers app
---------- Post added at 07:48 AM ---------- Previous post was at 07:47 AM ----------
You can also run as live CD or in a virtual machine
Sent from my HTC One X+ using xda app-developers app
hubbs134 said:
Thanks for your reply, I have read a lot about this phone and know how to get into download and recovery mode. I tried the method you mention, however, when running the command window I get errors for both roms you suggested (i attatched a screen shot of the errors I'm getting). Do you know how I can fix these errors so that I can proceed with the rest of the tutorial? Thanks.
PS I only had an iPhone because I had yet to discover how bad a** Androids are
Click to expand...
Click to collapse
No need to replace PC OS...
1. Uninstall all your Java versions and Samsung drivers and reboot.
2. Reinstall Java 1.7u..
3. Follow the guide, it should work.
When you reinstall the driver through Heimdall - it will appear as Gadget device.
Good luck !
itzik2sh said:
No need to replace PC OS...
1. Uninstall all your Java versions and Samsung drivers and reboot.
2. Reinstall Java 1.7u..
3. Follow the guide, it should work.
When you reinstall the driver through Heimdall - it will appear as Gadget device.
Good luck !
Click to expand...
Click to collapse
I second this... This should fix your driver issues.
Thanks for both of your replies. Odin detected my friends GS3 so I know it's not a Windows issue.
itzik2sh I did what you suggested and now got the command to function properly. I am going to try and finish the tutorial, I will be back soon with results. Thanks.
The phone is in download mode with Heimdall One-click 1.3.1 running and nothing is popping up in the command window. Neither is showing that the device is connected. Any suggestions? Thanks
Irish Enigma said:
I second this... This should fix your driver issues.
Click to expand...
Click to collapse
I forgot to mention that I can here the sound that a device was just connected to the computer via USB, and a message pops up saying USB device not recognized. When I click on the message it says "One of the USB devices connected to this computer has malfunctioned, and Windows does not recognize it."
Tried a different port? Tried second different port with a different USB cable?
itzik2sh said:
No need to replace PC OS...
1. Uninstall all your Java versions and Samsung drivers and reboot.
2. Reinstall Java 1.7u..
3. Follow the guide, it should work.
When you reinstall the driver through Heimdall - it will appear as Gadget device.
Good luck !
Click to expand...
Click to collapse
Theraze said:
Tried a different port? Tried second different port with a different USB cable?
Click to expand...
Click to collapse
Ok I got the device connected and I got Zadig running, however, there is no option for "Samsung USB Composite Driver" on the drop down list, on "gadget Serial", "Gadget Serial Control (interface 0), and "1.3 HD Webcam (Interface 0)'. What should I do?
On the one-clicks, you don't actually want to use zadig. Apparently it conflicts, which is awesome for something that gets released WITH the tool.
If you're doing manual Heimdall, make sure you've told zadig to list all devices in the menus. Your phone should show up after that.
If you're using a one-click, make sure you're using a USB port on your computer where you have NOT installed zadig, Kies, or Samsung official drivers. Follow the steps in the one-click religiously, and it should cooperate.
Follow the guide %100 then Odin should work
Sent from my HTC One X+ using xda app-developers app
Ok I ended up getting the phone to register in Odin. I flashed it with the stock rom in Odin and it said success. The phone booted and it seemed like it was going to work but then the recovery menu came up. I posted a screen shot of what it says, what action should I take from here? Thanks
I am also in a different boot loop now, before it would load to the first screen (black screen saying samsung galaxy 4g) then restart, now it boots to past the splash screen to where it says "Samsung" and then reboots back to the screen where the pink letters roll across the whole screen. I don't need to flash bootloaders do I?
Looks like recovery is broken or the updater script on the ROM you're trying to flash is messed up. Flash a new and the proper recovery via Odin then download a new Rom and either sideload it or mount usb from recovery and push it... Or you could just use Odin XD
EDIT: Samsung's are easy to brick and hard to debrick it may take a couple of trys
Sent from my HTC One X+ using xda app-developers app
Irish Enigma said:
Looks like recovery is broken or the updater script on the ROM you're trying to flash is messed up. Flash a new and the proper recovery via Odin then download a new Rom and either sideload it or mount usb from recovery and push it... Or you could just use Odin XD
Sent from my HTC One X+ using xda app-developers app
Click to expand...
Click to collapse
OK GREAT NEWS! After flashing with Odin and that screen popping up, I clicked update from SD card, which failed. I then click system reboot, which brought me into the new boot loop. I put back into download mode and re-flashed with One-Click. Same recovery menu came up as before but when I clicked reboot system it hung at the "Samsung" black screen (after the splash screen) for about 20-30 seconds and then booted up I'm afraid to turn the phone off and see if it reloads lol. Is it safe to say that it is fixed? Or should I still follow your advice and run the proper recovery in Odin and then sideload a new rom? Or take different action? Thanks for all your help guys! Everyone gets a thanks click for being so helpful and friendly on an unhappy/confused/pissed off/ now happy new Android user!
Ok I just put my Tmobile simcard in and the phone is not detecting the sim. Any suggestion?
The IMEI number and baseband both say "unknown", I'm assuming this has to do with the simcard not registering?
hubbs134 said:
The phone is in download mode with Heimdall One-click 1.3.1 running and nothing is popping up in the command window. Neither is showing that the device is connected. Any suggestions? Thanks
Click to expand...
Click to collapse
What Heimdall package are you applying ?
After JAR package runs you are ready to go.
As I wrote, according to guide you can reinstall "Gadget" driver.
EDIT :
Enigma, if you're not an owner of an SGS 4G please stop advising.
Odin is not the common way since we have MTD ROMs and it had its problems.
hubbs134,
blank IMEI is a serious problem. without a proper IMEI your device is everything but a phone.
Try this : take battery off, press the POWER button for 10 seconds, leave device untouched for 15 minutes and then put battery back and power up.
This could bring your IMEI back to life. If not... maybe another flash will help.
P.S
The 3e recovery image you put on post #14 is a snapshot of the the stock unrooted ROM recovery.
i made a extremely poor decision and was trying to change the boot animation loader when i actually changed the boot cmd and now it boots to samsung then to download everytime,. i can get into the onboard recovery yet i cant access safestrap and none of the many many drivers ive tried i cant get the phone to show to connect, its listed as unknown device in my device manager and ive hand picked the ones im supposed to have to other ones. ADB doesnt see it either and i was wondering if there is cmd for adb to find myu device, if you help me guys i promise ill only practice on hand me down smart phones. Ty:cyclops: [email protected] SM-G870A
This may be a dumb question, but have you tried Odin? I have had situations similar to this with my Samsung devices and always thought i bricked. But as long i could get into download mode, i could Odin back to stock and start over.
MrAwesome75 said:
This may be a dumb question, but have you tried Odin? I have had situations similar to this with my Samsung devices and always thought i bricked. But as long i could get into download mode, i could Odin back to stock and start over.
Click to expand...
Click to collapse
ya but i havent even tried loading a file into odin cause it wont see my device
and i have installed the samsung drivers but after this happened my pc wont see the phone
has to be a way to get a connection between the pc and phone
I'm not an expert so I'm not sure. Do you have the correct drivers installed on PC?
---------- Post added at 06:34 AM ---------- Previous post was at 06:30 AM ----------
Try different Odin versions. And make sure you have the proper drivers installed on the PC.
ya ive actually read that it probably doesnt have the function running to talk with the pc cause it cant boot. im all set up to reset the phoone. just need it to appear in my odin
..does kies still work?
[email protected] said:
i made a extremely poor decision and was trying to change the boot animation loader when i actually changed the boot cmd and now it boots to samsung then to download everytime,. i can get into the onboard recovery yet i cant access safestrap and none of the many many drivers ive tried i cant get the phone to show to connect, its listed as unknown device in my device manager and ive hand picked the ones im supposed to have to other ones. ADB doesnt see it either and i was wondering if there is cmd for adb to find myu device, if you help me guys i promise ill only practice on hand me down smart phones. Ty:cyclops: [email protected] SM-G870A
Click to expand...
Click to collapse
When you boot to system
It doesn't show anything right ??
but the touch is still functioning
Sent from my GT-i9300 running cm11 using tapatalk.
when i just boot it goes to download mode and says "could not do do normal boot"
i can access recovery mode and download mode but i cant get drivers to show it, and it used to show it until i did this, can i put a file on my micro SDcard from my pc via card reader then install it in recovery mode ? like firmware or a memory wipe reset?
If you can get into recovery, I believe that would be possible. Couldn't hurt to try. As long as you can get into recovery and all the recovery functions work, I don't see why you couldn't.
fixed it!
well after two nights of reading i got my pc to discover the device by changing ports three different times to find one that seamed to like it. and also installed kies and installed the drivers from them, (figured couldnt go wrong after as many as ive used from samsung and others). so win7 pro / altered boot command and only stock options afterwards sucks big time. ty all for helping me
never let up
Hi
TF300T JB 4.2.1
Bought new in the US in 2013 so has US SKU. Originally for my wife, but she now has an iPad Pro so I've got the hand-me-down!
Wiped it and unlocked the device successfully using the Asus V8 utility. Tried to flash TWRP from Win7 computer but something went wrong. The interface was still there, it would boot up okay but there was no sign of TWRP. Eventually, I went into fastboot and selected RCK. Nothing happened except the icon turned brown and just sat there. Then I tried a factory reset but it wouldn't have any, nor a cold boot. In desperation I turned the device off and tried to reboot. The initial "Asus" screen came up ("This device is unlocked" in top left-hand corner and the 'Nividia Tegra' logo in bottom right. No spinning circle of dots). It won't boot into fastboot, in fact the volume keys are totally unresponsive. On/off will turn off the device, but it immediately boots back to the same Asus screen. It's not recognised by the Win7 computer so I can't flash anything to it. I think I've tried everything this forum (and a few lesser ones!) could suggest, to no avail.
I believe I now have the proverbial 'bricked' tablet.
Nothing daunted, and not prepared to involve Asus support, I'm considering swapping the motherboard (I've done a couple on Windows computers) but will this bring my TF300T back to life, or is there more I need to do?
I'm no expert on the Android OS so any help from you experts would be much appreciated.
Thanks in advance.
Anyone?
I know the TF300 is a bit long in the tooth now, but all I want to know is whether a bricked one can be recovered by replacing the motherboard. There must be someone out there who has done the replacement and can advise me? Also, I apologise if this in in the wrong section, I guess it should have been in the 'Help' section, but I didn't realise until I'd posted it.
capelyddol said:
Hi
TF300T JB 4.2.1
I'm considering swapping the motherboard (I've done a couple on Windows computers) but will this bring my TF300T back to life, or is there more I need to do?
Click to expand...
Click to collapse
Of course, exchange the MB will bring back your device to life. But it is really the last option.
Firstly you have to check patiently if you can get access into your device. Therefore read mindfully this thread:
https://forum.xda-developers.com/showthread.php?t=2396072
"The solution by @Buster99 is for those who:
- flashed the wrong recovery, and wiped data
- are able to boot into recovery, but cannot flash anything
- no adb access (although, if you DO have adb access, this will still work for you...)"
Hopefully my advise will help you! Don't forget to thank @Buster99
ebonit said:
Of course, exchange the MB will bring back your device to life. But it is really the last option.
Firstly you have to check patiently if you can get access into your device. Therefore read mindfully this thread:
https://forum.xda-developers.com/showthread.php?t=2396072
"The solution by @Buster99 is for those who:
- flashed the wrong recovery, and wiped data
- are able to boot into recovery, but cannot flash anything
- no adb access (although, if you DO have adb access, this will still work for you...)"
Hopefully my advise will help you! Don't forget to thank @Buster99
Click to expand...
Click to collapse
ebonit ~ many thanks for your response. Unfortunately, I really don't think there's any way I can get access. The initial boot-up screen is all I get, in perpetual loop. The only way to shut it down is reset with vol-up., though it's possible it may be in some sort of variation of apx mode at this point as the screen is blank. I've no way of knowing as my win 7 computer only acknowledges an 'unknown device' at that point, and nothing when the initial boot screen is there. Vol-down doesn't seem to have any effect at all. Windows has already installed the drivers so won't re-install, or uninstall them as it's 'unknown'. I did once manage to get it recognised as an 'apx device' but with an '!' (not sure how I did it as I haven't been able to replicate it since!) but I don't think that helps me even if I could replicate it without the '!', Nvflash requires I have the necessary back-up files, which of course I don't. I don't know where to go from here except to replace the motherboard. Once I get the device apart I may try disconnecting the battery, vol-down, and reconnect, to try booting to recovery, but I'm not optimistic of that working.
I'll certainly be very happy to consider any other suggestions you, or anyone else, may have.
I tried Buster99's method, but as my TF300T isn't recognised by Windows that was a non-starter.
Once again, many thanks for your input.
capelyddol
(John)
capelyddol said:
ebonit ~ many thanks for your response. Unfortunately, I really don't think there's any way I can get access.
Click to expand...
Click to collapse
I'm sorry, but if you are really sure that you cannot boot into either fastboot or recovery the tablet is bricked for good!
In this case to replace the mainboard will be the last option to get the tablet back to life. There is a very good instruction with pictures by @huebinger that shows you what to do exactly: https://forum.xda-developers.com/showthread.php?t=2368372 (BTW, that's what I did many years ago!!!)
On ebay.com you may find a used one:
https://www.ebay.com/itm/GENUINE-AS...863174?hash=item54321ab206:g:lrcAAOSwjXRXcHSB
ebonit said:
I'm sorry, but if you are really sure that you cannot boot into either fastboot or recovery the tablet is bricked for good!
In this case to replace the mainboard will be the last option to get the tablet back to life. There is a very good instruction with pictures by @huebinger that shows you what to do exactly: https://forum.xda-developers.com/showthread.php?t=2368372 (BTW, that's what I did many years ago!!!)
On ebay.com you may find a used one:
https://www.ebay.com/itm/GENUINE-AS...863174?hash=item54321ab206:g:lrcAAOSwjXRXcHSB
Click to expand...
Click to collapse
ebonit ~ Thanks for the links. I checked out huebinger's and pulled my motherboard out, then bought the one you linked to on eBay. Hopefully, I didn't do any damage getting the MB out. I'm more used to the tough old internal wiring of desktop computers!
I'd already backed up the data and done a factory reset before I began my abortive attempts at rooting so hopefully I'll be starting with a clean slate once I get the new board installed. It's going to take a while to cross the pond to France, but I'll report on how it goes once it arrives.
Thanks again for your help, it's much appreciated.
John.
(capelyddol)
Hello,
My tf300t got bricked while upgrading twrp.
nothing helped, i put away the tablet, after a year i found her ... so i said to myself "why not" ?! so i ordered from ebay a motherboard, and it's work like a charm, but the tablet is old now ;0
now i want to setup a lite rom ....
mitomon said:
Hello, now i want to setup a lite rom ....
Click to expand...
Click to collapse
What do you mean?
What do you mean?
Click to expand...
Click to collapse
I was wondering that, too!
It's good to know the s/h motherboard cured his tablet's ills, though.
My replacement motherboard arrived yesterday and is installed, up, and running.
Android Ver: 4.2.1
Build No: US_epad - 10.6.1.27.5
I downloaded the v8 unlock device app and unlocked the tab.
I've downloaded:
1) djibe Transformer Pad TF300T pack v3
2)KatKiss -7.1_TF300T_029
3) open-gapps-arm-7.1-pico-20180517
I have a 32g microSD formated to FAT32 installed in the tablet.
All as per djibe89's tutorial here: https://forum.xda-developers.com/transformer-tf300t/general/guide-asus-transformer-pad-tf300t-stock-t3554744
My 'versions' are identical with djibe89's except for the BT version which is 11.38, not 10.38. Hopefully that'll not affect anything!
At this point I run into problems:
1) My USB link between the win 7 (32-bit) computer and the tablet is iffy. Sometimes it works for a while, but I frequently get the "USB device Not Recognized" with a useless MS message not worth clicking on. I'm wondering if there's a more reliable way to transfer files? Airdroid, possibly? Losing connection during file transference doesn't bear thinking about.
2)
Go to folder /Universal Naked Drivers 0.72 you unziped at start on your Desktop.
Select file android_apxusb.inf, then right click -> Install.
Force driver install and wait until a success message prompts.
Repeat operation with android_winusb.inf .
Click to expand...
Click to collapse
I tried installing these drivers by both right-click-> Install and also CMD. -to no avail. I get a Windows message saying the best drivers for the device are already installed, but the tab still isn't recognized. Oh, yes it is! Ooops, now it isn't! ad infinitum, I'm guessing.
Can anyone advise how to overcome this or I can see myself keeping the used motherboard salesmen in Mercedes for the next decade! :crying:
3) Assuming I can overcome the iffy USB problem: should I use TWRP Kang 2.8.7.2 or TWRP 3.2?
I guess that's enough problems for now. I hope ebonit or some other expert can assist with this as I really want to get this tab rooted.
Thanks
John.
(capelyddol)
capelyddol said:
My replacement motherboard arrived yesterday and is installed, up, and running.
Android Ver: 4.2.1
Build No: US_epad - 10.6.1.27.5
Click to expand...
Click to collapse
Congratulations! You did a good job. Thanks for your report.
First of all, to avoid any issues to get your device on N 7.1 Nougatella please follow exactly Tim's install instruction step by step in post #1. https://forum.xda-developers.com/transformer-tf300t/development/rom-t3453702
You need Kang TWRP as advised by Tim. Don't forget to format data through Kang TWRP before. It takes up to one hour. Then change file system to F2FS for data only no cache and system. Successfully done your device is now ready to install Rom, pico Gapps and SuperSU fresh downloaded via Tim's links there.
PS: About your USB issue take another USB port on your PC not via hub!
Good luck!
Three days with nothing from me, you'd be excused for thinking either I was dead, or my tab was! Thankfully, neither. In fact - SUCCESS!!! We're both alive and well, and for the tablet at least, performing better than ever.
TWRP installation took me two days. First, the computer (Win 7 32-bit) refused to recognize the TF300T and 'fastboot' could have been renamed 'nerverboot'. Strangely, the whole business seemed to evolve over time. Persistence was the name of the game - trying different USB ports, booting and rebooting (both tab and desktop). Eventually I found Snoop05's '15 seconds ADB Installer v1.4.3' https://forum.xda-developers.com/showthread.php?t=2588979 and with that I began to make progress...slowly!
Code:
fastboot devices
returned '???????????????' over and over again. By uplugging/plugging the cable into the tablet a few times I suddenly got a nice long string of letters and numbers. It came and went a few times but after a while seemed to stabilize till I felt ready for the big push of TWRP. I got so many error messages: 'can't find twrp.img' (I'd renamed it); 'can't open twrp.img'; 'insufficient memory', etc, etc.. Suddenly, it worked. It took just over eight seconds to download the 6.95MB. Booting into recovery was rather heart-stopping, but it came up a treat.
After that it was relatively simple to set up the TWRP (I found Djibe89's guide https://forum.xda-developers.com/transformer-tf300t/general/guide-asus-transformer-pad-tf300t-stock-t3554744 especially useful and there's a copy in the -djibe Transformer Pad TF300T pack v3' http://bit.ly/djibe-tf300t-v3.
Flashing KatKiss 7.1_TF300T_029, open_gapps-arm7.1-pico, and SuperSU-v2.82 from the microSD I'd copied them to went like a dream and before I knew it the old tab was humming with life once more. I'm a very happy chappy!
I have just two queries (so far ) 1. djibe89 mentions the file 'deviceID.apk' but Tim doesn't. Is it still necessary? I believe it's to keep Google happy, but I've no problems downloading from the Play Store, so I've not installed it as yet.
2) While installing the 'Battery Calibration' app it briefly stated that the tab wasn't rooted. I assume if I've achieved all the above, then it must be?
Now I'm going to play. No doubt I'll be back with a few more queries before too long!
Special thanks to ebonit for his help and support.
capelyddol said:
My replacement motherboard arrived yesterday and is installed, up, and running.
Android Ver: 4.2.1
Build No: US_epad - 10.6.1.27.5
I downloaded the v8 unlock device app and unlocked the tab.
I've downloaded:
1) djibe Transformer Pad TF300T pack v3
2)KatKiss -7.1_TF300T_029
3) open-gapps-arm-7.1-pico-20180517
I have a 32g microSD formated to FAT32 installed in the tablet.
All as per djibe89's tutorial here: https://forum.xda-developers.com/transformer-tf300t/general/guide-asus-transformer-pad-tf300t-stock-t3554744
My 'versions' are identical with djibe89's except for the BT version which is 11.38, not 10.38. Hopefully that'll not affect anything!
At this point I run into problems:
1) My USB link between the win 7 (32-bit) computer and the tablet is iffy. Sometimes it works for a while, but I frequently get the "USB device Not Recognized" with a useless MS message not worth clicking on. I'm wondering if there's a more reliable way to transfer files? Airdroid, possibly? Losing connection during file transference doesn't bear thinking about.
2)
I tried installing these drivers by both right-click-> Install and also CMD. -to no avail. I get a Windows message saying the best drivers for the device are already installed, but the tab still isn't recognized. Oh, yes it is! Ooops, now it isn't! ad infinitum, I'm guessing.
Can anyone advise how to overcome this or I can see myself keeping the used motherboard salesmen in Mercedes for the next decade! :crying:
3) Assuming I can overcome the iffy USB problem: should I use TWRP Kang 2.8.7.2 or TWRP 3.2?
I guess that's enough problems for now. I hope ebonit or some other expert can assist with this as I really want to get this tab rooted.
Thanks
John.
(capelyddol)
Click to expand...
Click to collapse
hi ,
you said that you succeeded to unlock the tablet ?
how ?!
i tried with unlocker v7 and 8 , i got the network error.
my tf330t is on 4.2.1.
i try hard reset, nothing helped.
i changed the mb, succeeded to root with motochopper.
please , i need help.
thanks
mitomon said:
I tried with unlocker v7 and 8 , i got the network error. My tf330t is on 4.2.1.
Click to expand...
Click to collapse
To avoid any issues please reinstall your system by doing a Buster99 https://forum.xda-developers.com/showpost.php?p=44244313&postcount=12. Be sure you have the latest firmware "WW_epad-user-10.6.1.27.5"
After that delete your Google account. Then you may unlock your device with V7.
capelyddol said:
TWRP installation took me two days. Eventually I found Snoop05's '15 seconds ADB Installer v1.4.3' https://forum.xda-developers.com/showthread.php?t=2588979 and with that I began to make progress...slowly!
Click to expand...
Click to collapse
Hope you have Kang TWRP now as required by Tim in post #1!
I'm sorry, but you never mentioned that you cannot access your Tablet via ADB. Therefore please note, the best ADB tool, every Android user may have on his PC, is "Minimal ADB & Fastboot" https://forum.xda-developers.com/showthread.php?t=2317790.
BTW, the answer to your first question is nope, you don't need it. The answer to your second one is yes the device is rooted. However check the update status of your SuperSU. Hope you did fresh download Rom, Apps and SuperSU via Tim's links in post #1 of the Nougatella thread?
I have installed Kang TWRP 2.8.7.2 as per Timduru's link. My tab was wiped before installation so all apps were fresh downloads. SuperSU was 'UPDATE-SuperSU-v2.82-20170528234214.zip' again, as per Timduru's link, as was the ROM ' KatKiss-7.1_TF300T_030.zip'. Many thanks for pointing me to 'Minimal ADB & Fastboot' which I've now installed for future use. And many thanks for all your other help. No doubt I'll be back for more!
capelyddol said:
My tab was wiped before installation so all apps were fresh downloads. Many thanks for pointing me to 'Minimal ADB & Fastboot' which I've now installed for future use. And many thanks for all your other help. No doubt I'll be back for more!
Click to expand...
Click to collapse
You are welcome! It's good to hear that you did such a good job. Using the thanks button is always greatly appreciated.
Please note, if you have any issues or you are changing the Android system, Format /data through Kang TWRP is always required. Format /data is more than wipe (you did wipe!) or factory reset. It takes up to 1 hour to be successfully. After that your system is really clean.
"Warning: formatting will remove what is stored in your internal storage, so store the rom /gapps/supersu zips onto an external storage (microSD, SD card..) or make sure you know how to push them back through adb." advised by Tim in post #1.