Hey!
I wanted to flash a custom rom because my stock rom was very very slow (after 3 years of permanent usage). I installed TWRP and wipe the phone. Then I wanted to use adb to push the desired rom to my Gnex. But my Gnex is not recognized by the computer. So there is no adb possible. Am I lost? Do I need to recycle my Gnex or is there any change to bring a rom onto the phone? TWRP is working but without usb connection it is worthless, is it?
I fear that the usb port of my Gnex is not working properly (maybe broken). It's charging but no computer recognize it (I tried 2 Windows machines and two Mac Books).
I'm happy for every tip or hint. Maybe you could help me find a way to get my Gnex working again. I'm not very optimistic but the android community amazed me before and so I hope you guys do again
Bye
Tschoartschi
Odin Mode??
is ur phone totally bricked?? can't u go to the odin mode ( by pressing power button and volume down button) ????
drivers?
Are the drivers installed so the phone and cpu can communicate?
Is the device recognized by the windows device manager when its plugged in? If not you could try to copy the rom zip on a usb flash drive and then connect it over usb otg (to see if it's mountable in the twrp mount section).
Related
All,
I have a big problem. When I try to start my phone I get the black screen with google and the unlocked padloack, after which the screen goes dark and nothing happens anymore.
What I did before this are two things. I had been mukking around with the screen resolution (I had it set at 240 and 280, as some apps did not show up in the market) also downloaded LCD density to solve the market issue.
I then rebooted the device and entered CWM to do a backup which as far as I knew succeeded. unfortunately after rebooting, see the above.
I have tried a couple of reboots, tried restoring the nandroid (the above was the only one I had). that didn't work, so tried to connect to the PC to load a new ICS rom (original 4.0.4 by google), unfortunately my device can not go into USB mode in CMW (it comes up with UMS lunfile missing....)
so I am woring in circles. can't start the device to download a rom, can't open USM to load a ROM to start the device again.....
any help would be appriciated
thanks
Patrick
hey
flash a new ROM via fastboot then, there are enough guides
-Syn
Edit: Alternatively, flash the stock Google ROM via GNex toolkit and go from scratch.
as mentioned, I can't get a rom on the phone so that I can flash it.
I can't start the phone to donwload one, and can't connect it to usb to get one on the storage....
sorry, you mentioned fastboot.... not USB.
so connect it to usb cable. I then entered fastboot devices, no number came up, as was also the case with ADB. thinkin I might not have the correct USB drivers for my windows machine. any idea where to get teh correct one?
pwvandeursen said:
as mentioned, I can't get a rom on the phone so that I can flash it.
I can't start the phone to donwload one, and can't connect it to usb to get one on the storage....
Click to expand...
Click to collapse
To flash stock images the files are on your PC, not the phone.
If you can get the phone to boot into fastboot (via vol up + vol dn + power) and get your PC to recognize it you're good to go.
thats the issue. pc cannot recognize the phone, so cannot get any files from the PC to the phone (ie. cannot get a rom file to the phone...)
pwvandeursen said:
as mentioned, I can't get a rom on the phone so that I can flash it.
I can't start the phone to donwload one, and can't connect it to usb to get one on the storage....
sorry, you mentioned fastboot.... not USB.
so connect it to usb cable. I then entered fastboot devices, no number came up, as was also the case with ADB. thinkin I might not have the correct USB drivers for my windows machine. any idea where to get teh correct one?
Click to expand...
Click to collapse
Either directly from Samsung or download the GNex Toolkit (You might want to use it anyways to flash the stock image), the drivers come with it.
After you installed the drivers and have you phone plugged in, go to the device manager to check if it is connected properly.
pwvandeursen said:
[snip]
thinkin I might not have the correct USB drivers for my windows machine. any idea where to get teh correct one?
Click to expand...
Click to collapse
For the drivers, I would recommend you remove all old drivers and install these. If you don't know how to install them, or are having issues, look here.
pwvandeursen said:
as mentioned, I can't get a rom on the phone so that I can flash it.
I can't start the phone to donwload one, and can't connect it to usb to get one on the storage....
sorry, you mentioned fastboot.... not USB.
so connect it to usb cable. I then entered fastboot devices, no number came up, as was also the case with ADB. thinkin I might not have the correct USB drivers for my windows machine. any idea where to get teh correct one?
Click to expand...
Click to collapse
I had a similar issue with regard to my PC recognizing the drivers. I googled around and found that people were having success with installing the PdaNet drivers, so maybe you can try that too. I had installed the Android SDK as well as the PdaNet drivers, and I eventually got mine to work.
I would probably follow Efrant's links first though - if that doesn't work for you, then maybe you can try PdaNet drivers and/or installing the SDK.
Good luck.
Why not just do a factory reset from within recovery?
¢ £®0π π€XU$ |||
the factory reset didn't help, the phone just wouldn't go past the black lockscreen. So in the end I used the galaxy nexus toolkit. installed the drivers for the PC, was able to go through fastboot and push files and flash a new rom.
Al is now solved, just need to do a lot of work to bring the phone back to where it was and make a backup asap.
thansk all for the help!
case closed.
pwvandeursen said:
the factory reset didn't help, the phone just wouldn't go past the black lockscreen. So in the end I used the galaxy nexus toolkit. installed the drivers for the PC, was able to go through fastboot and push files and flash a new rom.
Al is now solved, just need to do a lot of work to bring the phone back to where it was and make a backup asap.
thansk all for the help!
case closed.
Click to expand...
Click to collapse
Good to hear you got it.
Hey guys,
Now, my Galaxy Note 2 was rooted. When I connected it with the USB cable to my PC the PC didn't recognize it (it used too, but then suddenly it stopped connecting). It still charges but no new device is detected. No Kies, no MTP, no Odin.
I didn't worry too much, because being rooted I could still do everything using the external sd card.
However then the ROM for Android 4.3 was leaked I stupidly installed the stock version. So, no root, and no capability to mess around with the phone.. I also have no viewable option in Settings to set the device connection to MTP, or PTP mode as usual, but maybe that's because of Android 4.3
I have bought a new USB flex part, opened it and replaced it but it still didn't work.
I download a version of phoneutils.apk and installed (because the one on Android 4.3 didn't have Qualcomm USB settings option) and choose the correct options, but still nothing.
Do you have any idea what may have gone wrong? Or what I can try to do?
I desperately want to root the thing.
Thank you very much! I appreciate any suggestion and reply.
Hi!
This might sound stupid but... have you tried a different USB cable? Or USB port? Sometimes this can solve these kind of issues. Take a look in your computer's Device Manager and see if you have any problems with the USB hub driver. Also try to connect using a different PC and see if that works.
You can try and boot in Download mode (Vol down + Home + Power) and see if ODIN sees the phone. If so, you can flash another stock firmware and see if your USB works then.
Yea tried all that! No success. /:
Phone goes into download mode but Odin does not recognize it..
Ruwin said:
Hi!
This might sound stupid but... have you tried a different USB cable? Or USB port? Sometimes this can solve these kind of issues. Take a look in your computer's Device Manager and see if you have any problems with the USB hub driver. Also try to connect using a different PC and see if that works.
You can try and boot in Download mode (Vol down + Home + Power) and see if ODIN sees the phone. If so, you can flash another stock firmware and see if your USB works then.
Click to expand...
Click to collapse
Hello, I'm the new guy, kind of (I'm new to this forum but somewhat a technological handyman, so to speak).
I had recently obtained a Samsung Galaxy Ace II, everything was going good on the phone, hell, it's what? Two years old now? Anyway, I noticed the immense trouble I've been having trying to get several Windows PCs/laptops to detect anything from the phone, no driver updates, installations, not even from the trustworthy SAMSUNG Kies application. It is becoming a real problem as I really want to keep this phone, root it, installing several ROMs as I go along, but no, the computers won't even allow me to access the contents of my SD card through USB.
(Note: I have manually downloaded and installed SAMSUNG USB drivers and pooft, still nothing!)
I have tried quite a few methods to allow the PCs to establish a connection with the phone e.g. Dialing "*#7284#*, accessing "PhoneUtil", choosing "PDA" as the good mode, even switching to "MODEM" then back to "PDA"; Uninstalling/Reinstalling drivers; Attempting Kies.
I guess I am on the look out for a new-ish phone to replace this, which saddens me as I love being able to root, install various ROMs, Kernels etc, personally I like this phone too, more than my Spica running ICS (couldn't be too hard though, it wasn't stable whatsoever).
If anyone on this board could find a solution to this problem for me, I would be ever so grateful, I don't doubt it though, I love the work of XDA. Thank you.
Turn off the phone with no cable attached, press volume down, home and power at the same time and then volume up to put it in ODIN mode and connect it to the PC (use windows vista or newer so it auto installs the driver) It should install something like Samsung USB serial device. Tell if it works
Do I have to load it into ODIN mode whilst Odin is running on my PC?
[/COLOR]
RyanCM said:
Do I have to load it into ODIN mode whilst Odin is running on my PC?
Click to expand...
Click to collapse
For this test you dont need ODIN on the PC. Its only to see if the PC recognizes the phone
Porobu said:
[/COLOR]
For this test you dont need ODIN on the PC. Its only to see if the PC recognizes the phone
Click to expand...
Click to collapse
I just tested this and it appears not to be working, whatsoever. Is it necessary to have all SAMSUNG USB drivers installed on the PC?
Thank you for the idea, though. I just really want to root/mod my phone, ugh.
RyanCM said:
I just tested this and it appears not to be working, whatsoever. Is it necessary to have all SAMSUNG USB drivers installed on the PC?
Thank you for the idea, though. I just really want to root/mod my phone, ugh.
Click to expand...
Click to collapse
Windows should auto install the drivers. Connect the phone to the PC and see in device manager if there is something like an unknoen device or Samsung USB device
Porobu said:
Windows should auto install the drivers. Connect the phone to the PC and see in device manager if there is something like an unknoen device or Samsung USB device
Click to expand...
Click to collapse
Thank you for the help, although my problem is not dealt with still. I have completed the steps that you had suggested, thoroughly and repeatedly, yet there is no hope for a permanent, or even temporary fix for my mobile.
Windows isn't displaying any correlation between my PC and phone, no driver software auto-installs and no sign of the device being located in the Device Manager, not even under an "Unknown device".
Is this a problem for most Ace II devices? Or am I missing something that is too obvious to consider so seriously?
Porobu once told me something like:
1. Uninstall kies and sammy usb drivers
2. Install kies again, it should promt to install USB drivers.
3. Plug in phone to pc in DL mode.
I'm not sure what you mean in your 1st post so im assuming you have yet to try this. Works for me
When do I plug the USB into the phone and boot my phone into download mode? As soon as the drivers are installed via Kies?
RyanCM said:
When do I plug the USB into the phone and boot my phone into download mode? As soon as the drivers are installed via Kies?
Click to expand...
Click to collapse
After kies installation complete(dont have to open), boot phone to download mode, connect to cable and plug to pc
It sounds like a broken microusb port but try something first.
Download ubuntu or any other live cd linux distro
Boot it on your pc. You dont need to install anything.
Open a terminal
*Plug the phone while it is turned on to the PC
Write in the terminal 'lsusb' without the quotes and press enter
Something like Samsung android device or MTP device should appear.
If it doesnt appear power off the phone and go to odin mode and repeat from the * the steps
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
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.