Related
Hey, after rooting my phone and installing a few different custom roms, my USB connection has stopped working. whenever I connect the phone to a PC via USB, the device is unrecognised, and mass-storage doesn't work. It's definitely a hardware error, since trying a variety of different roms on a variety of computers, hasn't solved the problem, and even the recovery image doesn't allow mounting the SD card.
Research has suggested that it's affected other people in the past, with the only fix being to replace the motherboard. Hence, I'm looking for advice on un-rooting, rather than advice on fixing (but thank's for your good intentions!).
So I need to un-root my phone (and set it back to factory defaults), so that I can return it to T-mobile and have them fix it under warranty. Of course, because USB isn't working, I can't un-root the "traditional" way, by just installing the RUU update.
So I'm trying to figure out how to set the phone back to its original software, and I thought I'd ask for some advice before I make a mess of things...
As far as I know, there are 2 things that need to be done:
Flash the stock rom back on
- This bit is pretty straightforward; I just use the stock update.zip files found on the Modaco Forums (can't share a link here due to new account), and use the recovery image to update. The lack of a USB connection isn't a major issue for this bit, as I can transfer the zip files using the WebSharing Lite app (which allows me to upload to the phone over wi-fi)
Remove the Amon_Ra recovery image
- This is where I'm having issues. How do I go about clearing the recovery image, without a working USB connection? I'm not really sure how I put the recovery image on in the first place!
If someone could give me advice on how to remove the recovery image (or reset it to the stock one... I'm not sure if there was one initially), I'd really appreciate it. Also, please let me know if I'm missing out anything important.
Assuming everything works, later I'll write out a proper guide for anyone else who's ever in the same position.
Thanks in advance
Maybe this thread could help you?.... Read the last post on the 1st page, something about re-enabling USB.
Worth a shot?
EDIT,..... The link would help wouldn't it,.... Nandroid restore left other stuff around? (No ADB, No SD) [SOLVED]
thanks for your suggestion, but it didn't seem to work. apparently the issue has cropped up for other users, and the only long-term fix is to replace the motherboard under warranty, which is why I'm asking about un-rooting.
k28 said:
thanks for your suggestion, but it didn't seem to work. apparently the issue has cropped up for other users, and the only long-term fix is to replace the motherboard under warranty, which is why I'm asking about un-rooting.
Click to expand...
Click to collapse
You sure?... Have you started your phone in fastboot (hold vol- and power)? Try that to make sure if you haven't already. Once it comes up with the white screen and skateboarding androoids it'l say to press back or vol- (not sure which one so read it) to put into fastboot.
But if you have done that already,... Unfortunately I dont know how you can run an RUU .exe without USB.
yep, tried the whole fastboot thing, didn't work. I can connect to fastboot, but using the command "fastboot oem boot" , everything is normal - usb/sdcard are not disabled
(i didn't copy the exact output, and I don't have sdk on this laptop.. but yeh, that person's advice didn't match my situation).
hopefully someone else will have some ideas/comments?
k28 said:
yep, tried the whole fastboot thing, didn't work. I can connect to fastboot, but using the command "fastboot oem boot" , everything is normal - usb/sdcard are not disabled
(i didn't copy the exact output, and I don't have sdk on this laptop.. but yeh, that person's advice didn't match my situation).
hopefully someone else will have some ideas/comments?
Click to expand...
Click to collapse
What?.... It DOES connect in fastboot?... Says fastbootUSB (or something similar) on the screen?
I had same kind of problems with my usb. Try cleaning the "usb-hole"
lol, tried cleaning it but no luck.
from the research I've done, I've sorted out how to put the main ROM in place.
now I just need to find a copy of the recovery image of a T-mobile G2 Touch, and flash it using flashrec
can anyone help with that?
1. recovery - put regular hero recovery od sdcard and try to flash it using flashrec
2. root apk - delete it using root explorer
Hello,
Complete Noob here. I'm hopeful that I can get some assistance restoring my phone to a semi-useful function. I've searched these forums, and while I've found some solutions, none of them seem to work when you can get your phone past the initial boot screen when turning on the phone. Here's the story, appreciate it if you can help.
Yesterday I saw that there was an update from Samsung for the vibrant, so I installed Kies Mini on my computer and followed the instructions. It would have been nice if the program would have detected that I was running the 64 bit version of Windows 7 as a Samsung Tech person told me afterward that it wasn't compatible with that version of W7.
When Samsung heard that the screen on my phone showed a picture of a cell phone, with a orange triangle connected to a computer they said I'd need to mail them the phone and wait over a week to get a working phone. I figured I have nothing to lose at this point, and searched for a "do it yourself" solution. I found one click unbrick or something like that, and it went to work, but my phone now is stuck in the initial boot screen for the Vibrant. So all you see is "Vibrant" and "Samsung" on the phone.
I've read several posts about putting the phone into developer or restore mode, pushing combinations of the up/down vol button with the power button, etc., perhaps I'm doing this incorrectly, but nothing seems to get my computer to recognize the phone. I downloaded Odin, and the pit and pda files to start back at Eclair, but odin doesn't detect the device, nor does it have anything listed in the id-com section. I also tried the heimdall one click for the vibrant, but again it can find the device.
Couple of questions -
Can the phone be returned to a working status or should I just return it to Samsung and wait a week for the phone?
Is there any chance that I will be able to recover anything that was on the phone? I expect not, but wonder if so. I backed up my important files, but it would be nice not to have to start from scratch.
sounds like you are able to get your phone into download mode, but odin is not recognizing, which means we have a driver issue. Put your phone into download mode, and then uninstall kies on your computer, then re-install it, this will uninstall and then reinstall the drivers, I have to do this nearly every time I use odin.
Thanks for the quick response. I assume I'll need to do this on an XP machine, and not a 64 bit W7 machine? Plugged the phone into a XP machine, and now the phone is able to get to the downloading... yellow icons. I hope this means I'm making progress
Try the drivers here:
http://forum.xda-developers.com/showthread.php?p=11633550#post11633550
And stay away from Kies. It will murder you're phone.
Sent from my ZenDroid using XDA Premium App
Okay, thanks for the link. I see what I can do with that. Prior to your post, I got into download mode, download the pit file s1_odin_20100512.pit and the pda file T959UVJI6.tar. Tried to reload things on the phone. The phone now boots to a screen where it says
Android system recover (2e)
Samsung Recovery Utils
Vol up
Vol down
Power - select items
etc, given the option to reboot, reinstall packages, clear user data, or delete cache
below it says...
Movi_check Start
checksum confirmation need_checksum[0]
Not need checksum confirmation
Movi_check already executed...
movi_checking done!
update media, please wait
E:Can't mount /dev/block/st110
(Invalid argument)
E:copy_dbdate_media: Can't mount DBDATA:
copy default media content failed
The ji6 Odin file is known for doing that. Pull the battery, get back into download mode, and use these two files in Odin.
http://www.justanotherdev.slackdev.com/T959UVJFD.tar
http://www.justanotherdev.slackdev.com/s1_odin_20100512.rar
Sent from my ZenDroid using XDA Premium App
Same thing here, but I got it finally by using an ancient version of odin to flash to stock jfd. Kies picked it up right away after that.
That said, now that I have no fear of odin there are no traces of kies left on my pc...
Do you know if those file are located some place else, the link doesn't appear to have either file?
Sorry about that. Didn't realize the links were dead.
http://www.multiupload.com/NP507B6P8A
This should have both the pit and tar files in it.
Sent from my ZenDroid using XDA Premium App
SUCCESS!!!!!
Thanks so much. It worked. Now to replace my backup files. No more Kies for me.
OK first, my rooted u.s. 4.0 running cm7 suddenly had a read on file system. Couldn't download anything, delete anything, or modify anything on /mnt/sdcard. So I thought I would go into Odin and restore from an old backup. In the middle of the process, Odin crashes and my device gives me a weird screen that I can't get rid of unless I remove the battery. I can't even go into cwm. The screen shows a phone and a computer with a yellow caution symbol between the them. I think it means there is an error with connection to the PC or something. I've tried to fix it with Odin but it won't recognize the device. What do I do???
Mine did this aswell. I found that although I could not get it into download mode to try and flash again, the symbol you spoke of lets it occur anyway. The issue with it not being recognised may be due driver problems so try uninstalling them compleyely then reinstalling.
Then basically, just try to reflash through odin whilst that symbol is there.
Hope I helped
Sent from my YP-G70
I've tried but it just says SetupConnection..... and stays there.
Sent from my A500 using XDA
the symbol described is a sort of default download mode that comes up when the OS i corrupted.
As others said... you are not totally out of luck yet.
Make sure you have the right drivers on you PC.
Start Odin and connect your player via USB.
Your device should now be recognized by PC if you have the correct drivers (since you were already trying to flash in the first place, you might be ok here).
Flash one of the stock roms you may find in the dev section for your player (make sure it's the right one, US or INT) and hit start. If you are not sure how to use Odin, there are some good guides you can search for also.
Your player should reboot once it's completed and you can start the rooting and flashing process again.
Good luck.
Yay fixed it. After many attempts with odin (it kept failing) it finally booted up. Thanks for the help guys
Sent from my YP-G1 using xda premium
This question has already been posted multiple times
Greetings,
My son has a Galaxy s2 running stock 2.3 which he bought in Singapore over a year ago, I think. He states that it has not been rooted. Over the last several weeks he has been getting the 'kernal panic upload mode' screen when the battery was getting low. Last week it became permenant regardless of the battery level. Yesterday I was able to talk him through entering recovery mode. He wiped the partition cache and rebooted with no apparent effect. A picture of the recovery mode screen idicates that the system was unable to mount /data (unknown error: 0). But it did show media files were copied succesfully. ... I've attached a picture of the screen. The phone is no longer recognized in Win7.
My basic question. How might we rescue the pictures and some text from the phone before redoing the os?
TIA,
Kim
Kim, flash siyah v5 and try cwm.
Also drill your son on what is that he did exactly, cause he must have done something.
Sent from the little guy
I had thought that if all else failed I would have him use Odin to re-apply his existing os. My thinking was that the file and partition structure would be close enough to what's there to allow normal usb connection and to d/l his pics and what not. Then I'd get him to install something with a little more support for recovery and snooping about. Decent enhancements!!
I don't know what he did other than I think he might have overloaded the little beast with too many apps constantly calling home on an older os. But, that's just a guess. Thanks for the upgrade suggestions. I'm only starting to research that aspect. I suspect that going direct to the better burns will be the way we'll end up going.
Be well,
Kim
Siyah is a custom kernel, no danger regarding existing data.
By flashing it you'll be able to access a temp recovery called clockwork mode.
Sent from the little guy
Greetings gastonw,
My son's getting the usb drivers from the Samsung site for the i9100. I found the tar Siyah-s2-v5.0.1.tar for Odin.
Odin3 version is 3.04. Don't know what else I need.
I'm going to be doing this long distance and I've not handled a smart phone personally so ...
1. Start the phone in download mode.
2. Connect phone to computer
3. Start Odin (making sure that Kies is not running), Odin should recognize the phone.
4. Load the tar in the pda section
5. check automatic reboot, and start.
6. I presume that I will know when it's done because odin will report success or finished, and the phone will boot.
To grab the data off this phone do we use the recovery mode or will it now be called clockwork mode?
At which point I presume we shut the phone down and do a normal start/boot.
Any thoughts would be appreciated. Thanks for your help. Reading the specs on the Siya work I'm almost tempted
to go get a phone for myself.
Be well,
Kim
Lol, that's awesome, your playing by the book
Custom recovery will become CWM instead of stock recovery.
And go ahead and get yourself a new phone, you're in for a hell of a ride.
Sent from the little guy
Thank!! My son called and said the usb still doesn't work. Hum .... I hope not, but I may be back to see if there's a way to transfer something from an sd card in order to save the data. On the flip side ...
Kim
Odin doesn't see his device or the pc calls it "unknown device"?
Can he get it to boot, he can use airdroid app or dropbox to transfer over wifi.
The custom kernel is just to get rid of that pabic message.
Sent from the little guy
Mornin' gastonw,
Well, as of a couple of minutes ago, win7 did not recognize the phone. Hopefully with a reinstallation of the Samsung specific usb drivers win7 and/or Odin will recognize the phone.
Interesting. When he booted into download mode the top of the screen said something like, 'Odin download mode'. Does this indicate that it might be rooted? To the best of my knowledge he was unaware of the three button boot loader mode and hence would not have changed the phone from the basic generic non-branded phone that he bought. Just wondering. If it is rooted is there a way to manually do, via the recovery mode, what Odin will be doing? It seems to me that if recovery allows to d/l from the sd card there must be a destination to be designated. I have no idea what the drive and directory layout is, and I'm a tad rusty on linix shell commands, don't even know what shell android uses. But, if I knew where the package had to go ... .
I'll write again when I know more.
Thanks again,
Kim
Well the last I heard is that no USB *and* it's probably a win7 problem!!!! Good golly miss molly!
Anyway, snooping about I found a thread [howto] which indicated that putting a clock work mod zip on an sd and d/ling it thru the recovery mode would install the clock work mod recovery boot.
http://forum.xda-developers.com/showthread.php?t=1814801
Now I can not find a further reference to a zip with the name format used in this post. However at the modclockwork site I do find two
http://clockworkmod.com/rommanager. One is for 'touch'. I don't know the difference between the two. But, am I understanding correctly that I can put the appropriate zip on an sd from which I can d/l thru the standard recovery mode which on restart I presume will give me access to cmw recovery mode? Seems to easy. LOL!!!
Any help would be appreciated.
Kim
This is how you root & flash cwm via recovery: http://m.youtube.com/#/watch?v=7psIQU69h3M&desktop_uri=/watch?v=7psIQU69h3M&gl=MX
Tell him to try another PC to see if it sees the device.
Genuine s2 usb I assume?
Sent from the little guy
Greetings all,
I am a real noob and have recently taken to playing with my android devices.
Unfortunately I am in a predicament with my old S3 I9300.
I really screwed up and failed to make a Nandroid back up when using TWRP to flash Cynagenmod 13, after following the correct procedure on my other I9300 and successfully flashing it I became cocky and made the fatal error of not having a back up. A bit of back story but perhaps unrelated it was also suffering the old "Failed to Mount EFS" message which I have recently learnt to fix on my Old Old I9100 S2 using ADB.
After flasing It was in a Cynagenmod boot loop and was not able to be recognized by my pc via download mode or recovery, so was unable to use Odin, Kies or even ADB.
After experiencing USB issues with Cynagenmod 13 on my other I9300 when the flash was successful, I decided that perhaps it would be better to flash Android Revolution as the USB connections just seem to work better. After the flash seemed to be successful and the Samsung Logo just hung around and never booted.
I played with it all day, trying to get Kies, ADB and Odin to recognize it to no avail, (I tried every little trick on Google, reinstall drivers, restart pc , restart device, plug unplug, play with the buttons and the battery etc.....) the thing is, is that Odin would recognize it in bootloop.
After growing tired of this not working, for some stupid reason I decided to flash CWM over TWRP via MicroSD, i just thought maybe I could get ADB to work or something. Anyway the flash worked and I continued to try ADB, KIES and ODIN but nothing.
To make matters worse currently when I try to go to Recovery CWM is now looping (I'm hoping its a passing phase), so with recovery gone my phone is restricted to Download mode. I really think my last chance is to get download mode communicating with Kies to get the Firmware.
Feeling frustrated and about throw my phone on the recycling heap after googling and reading so many XDA threads I decided to reach out and ask for any help or suggestions in finding a way to get my phone recognized in Download Mode.
I thank you for your time in reading this post and look forward to hearing any advice.
Cheers.
muddled said:
Greetings all,
I am a real noob and have recently taken to playing with my android devices.
Unfortunately I am in a predicament with my old S3 I9300.
I really screwed up and failed to make a Nandroid back up when using TWRP to flash Cynagenmod 13, after following the correct procedure on my other I9300 and successfully flashing it I became cocky and made the fatal error of not having a back up. A bit of back story but perhaps unrelated it was also suffering the old "Failed to Mount EFS" message which I have recently learnt to fix on my Old Old I9100 S2 using ADB.
After flasing It was in a Cynagenmod boot loop and was not able to be recognized by my pc via download mode or recovery, so was unable to use Odin, Kies or even ADB.
After experiencing USB issues with Cynagenmod 13 on my other I9300 when the flash was successful, I decided that perhaps it would be better to flash Android Revolution as the USB connections just seem to work better. After the flash seemed to be successful and the Samsung Logo just hung around and never booted.
I played with it all day, trying to get Kies, ADB and Odin to recognize it to no avail, (I tried every little trick on Google, reinstall drivers, restart pc , restart device, plug unplug, play with the buttons and the battery etc.....) the thing is, is that Odin would recognize it in bootloop.
After growing tired of this not working, for some stupid reason I decided to flash CWM over TWRP via MicroSD, i just thought maybe I could get ADB to work or something. Anyway the flash worked and I continued to try ADB, KIES and ODIN but nothing.
To make matters worse currently when I try to go to Recovery CWM is now looping (I'm hoping its a passing phase), so with recovery gone my phone is restricted to Download mode. I really think my last chance is to get download mode communicating with Kies to get the Firmware.
Feeling frustrated and about throw my phone on the recycling heap after googling and reading so many XDA threads I decided to reach out and ask for any help or suggestions in finding a way to get my phone recognized in Download Mode.
I thank you for your time in reading this post and look forward to hearing any advice.
Cheers.
Click to expand...
Click to collapse
Hey Mate,
Firstly we all are noobs here helping each other, secondly from my experience of S3, it is such a device that under any condition, if your hardware is intact, you can recover your phone from almost anything, so yeah you might have a solution to your problem.
Coming to the problem at hand, i had the same thing happen to my S3, (only twrp logo showed, couldn't access recovery, no ROM, only download mode available) the way i fixed it was using odin, now i know you say that odin is not recognizing your device, the thing is firstly Kies is useless in this situation acc. to me, it only works stock ROM and that too with difficulty, what i would say is go here - http://developer.samsung.com/technical-doc/view.do?v=T000000117
and then install the drivers to your PC, next up download the official firmware from sammobile or any other site (careful of the version you are using), now put the phone in download mod, start odin and then connect your phone. Now, hopefully odin will recognize your phone and you can flash the official firmware, also i would recommend to stay on the official firmware for like a week before returning to flashing again as i have noticed that constant flashing and wiping leads to not only errors like "unable to mount EFS" but also serious errors like "Unable to mount /system" or "Unable to mount /Data" ,which clearly sucks
Please try the method and tell me if it worked , if not we'l try something else but we sure as hell will get your device working again
If still not recognized then here is a suggestion :
Exit/uninstall from nokia/ovi suit.
Exit/uninstall bluestack. (if u r using it)
Update your drivers(phone specific)
Use correct odin version acc to ur phone
Sent from my Micromax E352 using XDA-Developers mobile app
I'm just gonna throw my 2 cents in too. I didn't read your whole thread as I'm in a slight rush right now.
But basically -
Can your PC recognise your phone when it's plugged into USB in Download Mode? If so, use ODIN to flash any stock firmware and you're back to square one (working, but stock) phone. Then go from there. Obviously try to flash the right firmware or you'll end up no further forward.
If it can't recognise it, try reinstalling the drivers, uninstalling the programs mentioned above and using another USB cable. My experience with my own S3 has shown potential wear with the USB port on the bottom of the phone presumably due to it's age and as a result it doesn't recognise many USB cables.
Regards