I have searched for a topic, but they didn't give me any answers. I have tried EVERYTHING, buying a new cable, turning off USB Debugging, hell I even did a hard reset on the tablet.
When I connect the two devices, "MTP initialisation" comes up on the Tab sometimes, and when I say that I have to keep unplugging and pugging in the damn thing. SO, it says connected on the Tab, but my PC will not recognize it at all. There is nothing under Device Manager, and nothing under Computer.
And Yes, all my drivers have been installed. I really wanted that ICS rom and this is making me frustrated. If I can;t get this resolved, I'm getting an iPad 3 lol. Please help!
galaxytabevo said:
I have searched for a topic, but they didn't give me any answers. I have tried EVERYTHING, buying a new cable, turning off USB Debugging, hell I even did a hard reset on the tablet.
When I connect the two devices, "MTP initialisation" comes up on the Tab sometimes, and when I say that I have to keep unplugging and pugging in the damn thing. SO, it says connected on the Tab, but my PC will not recognize it at all. There is nothing under Device Manager, and nothing under Computer.
And Yes, all my drivers have been installed. I really wanted that ICS rom and this is making me frustrated. If I can;t get this resolved, I'm getting an iPad 3 lol. Please help!
Click to expand...
Click to collapse
Had a similar problem myself and it ended up being the PC usb drivers. Used a program on the PC to remove all the drivers for the tab off the PC and reinstalling them and everything went great from there.
I thought the program was called Dev view or something, but can't find it right now, but anyway google how to remove drivers from your win version and you should be able to manually remove the usb drivers pretty easily. I ended up removing every usb driver except my mouse and keyboard from Windows 7, installing the drivers for the tab downloaded from Samsung directly and haven't any problems since.
This may be a bit of overkill so you might want to wait for other fixes to be suggested too.
Good luck.
Edit: just noticed this in two other recent threads "MTP selected under settings/storage/USB computer connection" don't know if it's only related to ics, cause I don't have this option on my tab running Task 14 slim. So may be of no help what so ever.
Sent from my GT-P7510 using XDA Premium HD app
Benzoman said:
Had a similar problem myself and it ended up being the PC usb drivers. Used a program on the PC to remove all the drivers for the tab off the PC and reinstalling them and everything went great from there.
I thought the program was called Dev view or something, but can't find it right now, but anyway google how to remove drivers from your win version and you should be able to manually remove the usb drivers pretty easily. I ended up removing every usb driver except my mouse and keyboard from Windows 7, installing the drivers for the tab downloaded from Samsung directly and haven't any problems since.
This may be a bit of overkill so you might want to wait for other fixes to be suggested to.
Good luck.
Sent from my GT-P7510 using XDA Premium HD app
Click to expand...
Click to collapse
How can you tell which driver is which though? I can't seem to find the Dev view thing, even though you're not sure about it lol
galaxytabevo said:
How can you tell which driver is which though? I can't seem to find the Dev view thing, even though you're not sure about it lol
Click to expand...
Click to collapse
I don't remember, sorry I'm old and can't get to my PC right now. Hopefully someone will jump in here soon or I can get to my PC to figure out what I did exactly.
Sent from my GT-P7510 using XDA Premium HD app
Benzoman said:
I don't remember, sorry I'm old and can't get to my PC right now. Hopefully someone will jump in here soon or I can get to my PC to figure out what I did exactly.
Sent from my GT-P7510 using XDA Premium HD app
Click to expand...
Click to collapse
Yeah, it would be a favor whenever you use your PC again to remember to check back lol, hopefully someone will remember
I just checked again, and the tablet is charging through the USB, which I'm not sure why. Every once in a while when plug it in to the USB, the battery gets a small red x on it, and it says MTP initialisation, but nothing on the computer
galaxytabevo said:
I just checked again, and the tablet is charging through the USB, which I'm not sure why. Every once in a while when plug it in to the USB, the battery gets a small red x on it, and it says MTP initialisation, but nothing on the computer
Click to expand...
Click to collapse
I think Misledz just dealt with a tab with the red x on it. Please pm him if you would and tell him I sent you to point out this thread. I'm dealing with a lot of other things and may not be much help with my mind going a hundred different directions. I'm sure he can help get you on the right track quickly. one of his posts should be easy to find in general or q&a sections.
Don't tell him I said this but he's a great help.
Sent from my GT-P7510 using XDA Premium HD app
Benzoman said:
I think Misledz just dealt with a tab with the red x on it. Please pm him if you would and tell him I sent you to point out this thread. I'm dealing with a lot of other things and may not be much help with my mind going a hundred different directions. I'm sure he can help get you on the right track quickly. one of his posts should be easy to find in general or q&a sections.
Don't tell him I said this but he's a great help.
Sent from my GT-P7510 using XDA Premium HD app
Click to expand...
Click to collapse
lol, I will do that thanks.
Well, yeah sorry that I didn't reply via the PM as it tends to get flooded at times and I lose track of where and who sent the original Do forgive me for that.
The problem is the red X appears when you had the USB charge from the Overcome series, I'm pretty sure it's a lib file that conflicts with other ROM's and such, and they said there was a way to remove it, but it's dug somewhere underneath their thread, the best bet would be to attempt a factory reset, I do hope that your data is backed up via Titanium or something before you attempt this, because doing a factory reset via device *Not CWM* tends to reset all sorts of mods applied to the phone, and the user applications.
If you do attempt a factory reset do let me know You'd be surprised what a clean swipe can do (Problem is there isn't an external sd slot) so things tend to get left behind from other ROM's (The ones that aren't replaced anyway during installation)
Misledz said:
Well, yeah sorry that I didn't reply via the PM as it tends to get flooded at times and I lose track of where and who sent the original Do forgive me for that.
The problem is the red X appears when you had the USB charge from the Overcome series, I'm pretty sure it's a lib file that conflicts with other ROM's and such, and they said there was a way to remove it, but it's dug somewhere underneath their thread, the best bet would be to attempt a factory reset, I do hope that your data is backed up via Titanium or something before you attempt this, because doing a factory reset via device *Not CWM* tends to reset all sorts of mods applied to the phone, and the user applications.
If you do attempt a factory reset do let me know You'd be surprised what a clean swipe can do (Problem is there isn't an external sd slot) so things tend to get left behind from other ROM's (The ones that aren't replaced anyway during installation)
Click to expand...
Click to collapse
Thanks for your reply but the problem is that I'm not rooted and I have done a factory reset. The problem still persists.
Sent from my SPH-D710 using XDA
Have you tried manually mounting the internal drive via CWM? CWM->Mount? It's different from MTP
Misledz said:
Have you tried manually mounting the internal drive via CWM? CWM->Mount? It's different from MTP
Click to expand...
Click to collapse
How do you do that? Is that Clockwork, because I thought you needed to be rooted for that
Basically CFRoot is CWM+Root, CWM is just a custom recovery module made for flashing mods.
You need to select these options as shown, Ignore the pink walls
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Misledz said:
Basically CFRoot is CWM+Root, CWM is just a custom recovery module made for flashing mods.
You need to select these options as shown, Ignore the pink walls
Click to expand...
Click to collapse
I appreciate your pictures and help, but I have no idea of getting to this point. Everywhere I read it says that I need to be rooted to have CWM, I am completely stock, no root.
Good sir, you don't need root to get to this point. Just flash CWM from the Overcome thread or anywhere, It's all over the Development section, Just flash it via Odin, I assume by this point you know how to use Odin? If you don't it's all good, I'm willing to help you with that too
I took the liberty of uploading CWM recovery for you,
http://www.mediafire.com/?6c5tdmds927npdv
Cheers,
Fitz
Edit: Oh good lord, I just realized since you don't have CWM you can't get the PC to recognize the tab itself, silly me. Have you tried putting it into download mode and seeing if the tablet is detected in Odin?
PS: Do you know what Odin is?
Misledz said:
Good sir, you don't need root to get to this point. Just flash CWM from the Overcome thread or anywhere, It's all over the Development section, Just flash it via Odin, I assume by this point you know how to use Odin? If you don't it's all good, I'm willing to help you with that too
I took the liberty of uploading CWM recovery for you,
http://www.mediafire.com/?6c5tdmds927npdv
Cheers,
Fitz
Edit: Oh good lord, I just realized since you don't have CWM you can't get the PC to recognize the tab itself, silly me. Have you tried putting it into download mode and seeing if the tablet is detected in Odin?
PS: Do you know what Odin is?
Click to expand...
Click to collapse
I will definitely try this when I get home, I really appreciate your help on this issue. Last time I tried using Odin in download mode, the PC would not connect but I will retry it later with these directions.
Sent from my SPH-D710 using XDA
Ah no worries mate, it's all good I gain user knowledge like this Experience being the wisest mans weapon, they say
I think a combo of sdk/ADB and samsung drivers are enough to see odin. (if i remember right) Connected to odin without cwm many times before development. Uninstall any samsung applications and drivers(if applicable and separate from apps) Reinstall samsung drivers via installing "Kies", then install SDK... this combo should allow Odin to see your device. Odin is a samsung program licensed to samsung and therefor should not require root access or CWM.
If i remember correctly... sorry been quite a while
http://www.addictivetips.com/mobile/what-is-adb-and-how-to-install-it-android/
Yeah guys it didn't work. Even when in download mode and the SDK thing, nothing is recognized.
I chatted with a Samsung service rep for like an hour, I swear this guy must have been a robot. He told me to do what everyone else on this forum told me to do and it didn't work. He just told me to file a service request....yeah no.
I called this guy a magnificent bastard and my homeboy, and he didn't even give back the slightest emotion
Well, unless someone else can help me, I'm getting an iPad 3....I'll stick to Androids for my phone but going all Apple for my tablets. Getting sick of the sluggishness of Honeycomb, didn't even get to try ICS because of this issue.
Related
UPDATED. This will put you to STOCK 2.2! Using ODIN thanks to eugene373.
If you want stock and are able to get in to recovery and want a flashable rom. click here
This started as a thread asking for help, with the little help I got... and a little searching NOW this thread is to help other people who are having the same problem
ALSO its to show that a little searching on this forum, you will pry find the answers you are looking for.
EVERYTHING in here I found in the Bible, that is located in the development section.
This guide is for non hardware locked vibrants... if you are hardware locked check out this threadhere
First off you will need to get odin and the correct files.
I have packaged eugenes 2.2 pit and tar(md5) files in a zip along with odin. these are all the files you will need and you can download them here
(remember this is for unofficial 2.2 if you want Official 2.1 files click here )
s15274n (thread here) has everything you will need in his [Tips & Tricks] thread AND MORE!
so make sure to check that out and read the "EASY WAY TO GET THE JI6 UPDATE" before you go any further with my thread.
Georgegreco86(thread here) made this awesome image (below) and it works perfectly....
HOWEVER some times there are some complications that happen that i cover below.
TO GET IN TO DOWNLOAD MODE
I have found the EASIEST WAY to do this is:
1.pull the battery out of the phone.
2.plug usb into computer
3.put the battery back in the phone
4.hold in the volume up and down
5.plug usb in to phone
it should bring you to the download mode in seconds.
now you should unplug the usb From the phone..
make sure the battery stays in, and open odin.
now follow the instructions below.
1. Open Odin3_v1.0
2. Load .512 into the PIT placeholder
(In this case s1_odin_20100512)
3. Load *FILE.tar* into PDA placeholder
(In this case Eugene_2E_JK2_Froyo.tar.md5)
4. Make sure COM port has a number in it
This means your phone is connected, if your phone is not connected make sure you have the correct drivers)
5. Press Start!
6. If you it all works your done... if not keep reading!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
IF YOU RUN IN TO PROBLEMS!
If your phone is not connecting to odin.It might be because you need the correct drivers, thanks to TGA_Gunnman they are located here http://forum.xda-developers.com/showthread.php?t=728929.
I was able to just let the computer search for them and with a few clicks, had the drivers installed.
To install the Android USB driver on Windows Vista for the first time:
1. Connect your Android-powered device to your computer's USB port. Windows will detect the device and launch the Found New Hardware wizard.
2. Select "Locate and install driver software."
3. Click "Next." Vista may prompt you to confirm the privilege elevation required for driver installation. Confirm it.
Freezing on "cache.rfs"
searching on google i found a website called fractionalphones.com, the post was about this and it said what i had to do was reboot my computer and hit F8 (just keep touching it) and when it gets to the "safemode screen" arrow down to "Disable Digital Signature Verification"
Also a problem Some people had was the usb port used...
So if it does not work try a new port!
Use oclf. Remove the lag fix first, then ant other optimizations you may have clicked, then ext 2 and finally root. I had to do this to send back my phone. Now the ext2 takes awhile so be patient.
Sent from my SGH-T959 using XDA App
ipeench said:
So if I have rooted the phone and have installed the OCLF from the market. But I wasn't the phone back as if I just took it ot the box.. What's the best way to do that.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
The easiest and cleanest way to do it is to Odin the phone back to stock.
Odin Visual Guide
Stock Firmware
tjhart85 said:
The easiest and cleanest way to do it is to Odin the phone back to stock.
Click to expand...
Click to collapse
Sweet, you even put in links to reading material! In a day of being flamed for asking questions like this..words can not express the kindness you have shown, thank you.
Sent from my SGH-T959 using XDA App
creglenn said:
Use oclf. Remove the lag fix first, then ant other optimizations you may have clicked, then ext 2 and finally root. I had to do this to send back my phone. Now the ext2 takes awhile so be patient.
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
It wont let me remove the lag fix, v2 says i dont have the lag fix installed
and v1 says "you only have 346MB free on RFS, but 364MB used on EXT2. You must free up some space"
and then it tells me i dont have enough to install either v1 or v2 of the lag fix
BUT my quadrant is 2000+ so i know its installed.
i saw the other tread about this but it didnt really tell me much.
ipeench said:
It wont let me remove the lag fix, v2 says i dont have the lag fix installed
and v1 says "you only have 346MB free on RFS, but 364MB used on EXT2. You must free up some space"
and then it tells me i dont have enough to install either v1 or v2 of the lag fix
BUT my quadrant is 2000+ so i know its installed.
i saw the other tread about this but it didnt really tell me much.
Click to expand...
Click to collapse
LOL, One of the reasons I suggested Odin. It'll "just work" even if you have the lagfix (at least it did for me). Make sure you backup everything on the SD card that you want & tell it to repartition. If all goes well, everything down to the internal SD card has been put back to stock.
I know when I did the lagfix, I had a PC app that just ran ADB commands in a batch file (basically). After a week or so it got unbearably slow and even the remove lag fix that came with it wouldn't work, so I used Odin to go back to stock.
--------
But, I think what it's complaining about is you need to free up ~20MB of space in order to remove the lag fix. Since it needs to move the files that it put on the ext2 partition back to the RFS partition, it needs at least that much space before it can move the files & then delete the ext2 partition.
bumping because I figured out what I was doing and I think this can help a lot of other people.
I'm trying to do the "Odin back to stock" process but I'm having a little trouble. I've got all the files and opened Odin etc. I entered the .pit file and the .tar file. Auto-reboot and f. reset time are checked. I click start and I get "<OSM> All threads completed. (succeed 0 / failed 0)"
What am I doing wrong?
trunkstar1 said:
I'm trying to do the "Odin back to stock" process but I'm having a little trouble. I've got all the files and opened Odin etc. I entered the .pit file and the .tar file. Auto-reboot and f. reset time are checked. I click start and I get " All threads completed. (succeed 0 / failed 0)"
What am I doing wrong?
Click to expand...
Click to collapse
Odin isn't recognizing your phone. You should double check that the drivers are properly installed. Then, make sure Odin is on and click Reset if need be. Put phone into Download Mode and then plug it into computer.. A yellow box should appear at top of Odin, which let's you know you're successfully connected.
Hope that helps!
.:|Sent from my Super AWESOME Vibrant using XDA App|:.
That did help, thanks. And, with some help from other XDA forumers I got the right drivers installed and I'm in motion now. Thanks again.
trunkstar1 said:
That did help, thanks. And, with some help from other XDA forumers I got the right drivers installed and I'm in motion now. Thanks again.
Click to expand...
Click to collapse
With all that i have taken from this forum..I'm glad i can finally give back!
ipeench said:
This started as a thread asking for help, I got a little help(thank you for pointing me in the right direction tjhart85)
NOW this thread is to help other people who are having the same problem
ALSO to show that a little searching on this forum, you will pry find the answers you are looking for.
pretty much everything in here i found in the Bible, that is located in the development section.
This is for non hardware locked vibrants... i dunno what to tell you if yours is hardware locked because honestly i have no clue what that even means :-/ I'm just as new to this as you are!
First off you will need to get odin and the correct files.
and rhcp0112345(thread here) found the "true stock 2.1 firmware for vibrant" and all the files you will need,including odin are bundled in a nice little zip file for you.
http://tinyurl.com/2bc5b6r
Georgegreco86(thread here) made this awesome image (below) and it works perfectly.... but some times there are some complications that happen that i cover below.
TO GET IN TO DOWNLOAD MODE
I have found the EASIEST WAY to do this (IMO) is
1.pull the battery out of the phone.
2.plug usb into computer
3.put the battery back in the phone
4.hold in the volume up and down
5.plug usb in to phone
it should bring you to the download mode in seconds.
now you should unplug the usb.. make sure the battery stays in, and open odin.
now follow georgegrecos instructions.
Some people have said to load the files (PIT and TAR) before reconnecting the phone to the computer so that is how I did it and it worked perfect.
IF YOU RUN IN TO PROBLEMS!
If your phone is not connecting to odin.It might be because you need the correct drivers, thanks to TGA_Gunnman they are located here http://forum.xda-developers.com/showthread.php?t=728929.
I was able to just let the computer search for them and with a few clicks, had the drivers installed.
To install the Android USB driver on Windows Vista for the first time:
1. Connect your Android-powered device to your computer's USB port. Windows will detect the device and launch the Found New Hardware wizard.
2. Select "Locate and install driver software."
3. Click "Next." Vista may prompt you to confirm the privilege elevation required for driver installation. Confirm it.
Freezing on "cache.rfs"
searching on google i found a website called fractionalphones.com, the post was about this and it said what i had to do was reboot my computer and hit F8 (just keep touching it) and when it gets to the "safemode screen" arrow down to "Disable Digital Signature Verification"
Also a problem i had was the usb port i was using... so if it does not work try a new port!
Click to expand...
Click to collapse
Perfect,thanks.Previous to the J16 OTA update,I just held volume down/power.
I flashed back to stock to make sure I'd get the update without a hitch,which I did.
trunkstar1 said:
That did help, thanks. And, with some help from other XDA forumers I got the right drivers installed and I'm in motion now. Thanks again.
Click to expand...
Click to collapse
Coolness! Pass on the knowledge!
This is the same method I tried last night. Mine wont get past the bootup sequence. any help?
wicked1lbc said:
This is the same method I tried last night. Mine wont get past the bootup sequence. any help?
Click to expand...
Click to collapse
Try re-downloading the files and doing it again, maybe you got a bad file or something? This should work and if it does not... like I said I'm brand new to this, I had a problem figured out how to fix it and figured share the info, if it does not work for you, hopefully someone with more knowledge will chime in.
The tinyurl link you posted is bad. Looks like too many people have downloaded and the account is suspended :/ can someone upload them to somewhere else? I really need them
hiddengopher said:
The tinyurl link you posted is bad. Looks like too many people have downloaded and the account is suspended :/ can someone upload them to somewhere else? I really need them
Click to expand...
Click to collapse
this is correct, i do not need this right now but it would be nice to have
Hey guys, I am new at this My status stays at file analysis. My phone is in download mode as well.
SORRY! i have been away from the computer for a few days :-/
go to this thread
http://forum.xda-developers.com/showthread.php?t=732458
it has all the info you will need AND THEN SOME! it has the proper files and a little instruction spot with it... plus that one gives your the update.
if you still have trouble come back and i will try to help!
rcanela1 said:
Hey guys, I am new at this My status stays at file analysis. My phone is in download mode as well.
Click to expand...
Click to collapse
try switching usb ports.. i remember that happening to me.. i dont remember what i did tho haha.
im sure a google search will help with that one thats what i did
Installed cm via directions. No problems. Decided to try installing a new Android kernel. Flashed via recovery.
Moboot, but couldn't get into any os, not even recovery. Eventually got into Android. Was able after many attempts to get to webos. Decided to try and reinstall cm9 and such. Plugged into computer while in webos to move files over and got a need to format window. Hit yes (i know, I know).
Now can't even get moboot. Decide to Dr it. Gets to 12% and doesn't move. Google it and follow some novaterm/cmd directions.
Now Dr gets to 8% and says unable to reset device. Have a hard time getting into HP recovery (usb symbol). Mostly get an exclamation point in a triangle and the url for Dr.
What r my options, HP warranty? Thx
Sent from my PG86100 using XDA App
The cm team can help you on IRC here's info I copied from the cm thread go here and they should get you right http://webchat.freenode.net?channels=cyanogenmod-touchpad
The reason the doctor is failing is because Android messes with your partitions and at 12% the webOS doctor is verifying partitions. Have you attempted ACMEUninstaller? When at the webOS screen go ahead and run ACMEUinstaller. Then if uoi can boot into webOS do the complete wipe to wipe the entire SD section. Then doctor it and then reflash Android with ACMEinstaller2
Sent from T the Touchpad
Eat it iPhone said:
Installed cm via directions. No problems. Decided to try installing a new Android kernel. Flashed via recovery.
Moboot, but couldn't get into any os, not even recovery. Eventually got into Android. Was able after many attempts to get to webos. Decided to try and reinstall cm9 and such. Plugged into computer while in webos to move files over and got a need to format window. Hit yes (i know, I know).
Now can't even get moboot. Decide to Dr it. Gets to 12% and doesn't move. Google it and follow some novaterm/cmd directions.
Now Dr gets to 8% and says unable to reset device. Have a hard time getting into HP recovery (usb symbol). Mostly get an exclamation point in a triangle and the url for Dr.
What r my options, HP warranty? Thx
Sent from my PG86100 using XDA App
Click to expand...
Click to collapse
lucky for us, the TP can never be bricked unless you start to manually edit partition tables (and even then, its fixable with much hair pulling, ive personally troubleshooted this with a friend before )
maybe these threads can help you out:
http://forum.xda-developers.com/showthread.php?t=1236727&page=2.
http://forum.xda-developers.com/showthread.php?t=1379579
it really helps to have a grasp on how novaterm works, and ALWAYS ALWAYS re read your commmands to ensure you typed it correctly (upper/lower case espicially ;P)
Thx guys ill look into it, but I'ma be busy so ill have to chk this out tomorrow
Sent from my PG86100 using XDA App
http://forum.xda-developers.com/showthread.php?t=1426244
Try it. It may just work.
rr5678 said:
http://forum.xda-developers.com/showthread.php?t=1426244
Try it. It may just work.
Click to expand...
Click to collapse
oh god, that brings back terrible memories of "unbricking" my buddies TP from scratch using mine as a reference
and yes, Eat it iPhone, this is the best last alternative for repair, you will be restored to 100% BNIB (or LNIB as the case would be )
Solidus_n313 said:
oh god, that brings back terrible memories of "unbricking" my buddies TP from scratch using mine as a reference
and yes, Eat it iPhone, this is the best last alternative for repair, you will be restored to 100% BNIB (or LNIB as the case would be )
Click to expand...
Click to collapse
It may be horrible but in the end it's worth it
P.S.: I read that link in your signature (The TRUTH: XDA: Then and Now), and all I have to say is.....
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
im still wating for a complete recovery without bootie... which doesnt evn turn on the screen.heh
as said before more likely than not its a currupted partition that its stoping on...
darkassain said:
im still wating for a complete recovery without bootie... which doesnt evn turn on the screen.heh
as said before more likely than not its a currupted partition that its stoping on...
Click to expand...
Click to collapse
There is no recovery from a missing bootie (not that I know of). A missing bootie is like a missing hboot.
rr5678 said:
There is no recovery from a missing bootie (not that I know of). A missing bootie is like a missing hboot.
Click to expand...
Click to collapse
yep there is a way, you just havent heard of it (the pre has a way to boot from a corrupted bootie too)...
you can boot directly from the usb into the cpu bypasing bootie (instead of power + vol-up to enter bootie try it with vol-down while connected to a pc , and you will get what i mean..)
work has been done on this but a working product hasnt...
also is the hboot in nand or rom (im gueasing the nand /boot partiton just as with the few android devices i have worked on)
darkassain said:
yep there is a way, you just havent heard of it (the pre has a way to boot from a corrupted bootie too)...
you can boot directly from the usb into the cpu bypasing bootie (instead of power + vol-up to enter bootie try it with vol-down while connected to a pc , and you will get what i mean..)
work has been done on this but a working product hasnt...
also is the hboot in nand or rom (im gueasing the nand /boot partiton just as with the few android devices i have worked on)
Click to expand...
Click to collapse
No, the Pre is a completely different device. The Pre has an OMAP3430, while the TouchPad has your typical (non-USB bootable) Qualcomm processor.
And hboot is in the nand. (but still erasable)
rr5678 said:
No, the Pre is a completely different device. The Pre has an OMAP3430, while the TouchPad has your typical (non-USB bootable) Qualcomm processor.
And hboot is in the nand. (but still erasable)
Click to expand...
Click to collapse
doesnt matter boot with power+voldown and you enter qualcomm recovery which can boot from usb....
ps should have said that this only works on the TP
pps should mention that other qualcomm devices can boot from usb too...
darkassain said:
doesnt matter boot with power+voldown and you enter qualcomm recovery which can boot from usb....
ps should have said that this only works on the TP
pps should mention that other qualcomm devices can boot from usb too...
Click to expand...
Click to collapse
If you're talking about QHSUSB_DLOAD, there is no known way to use that. No image files, nothing.
rr5678 said:
If you're talking about QHSUSB_DLOAD, there is no known way to use that. No image files, nothing.
Click to expand...
Click to collapse
which is why i mentioned in two different posts that that its "not working" and why "im waiting" for something like this...
it works on some phones though which means it will communicate
darkassain said:
which is why i mentioned in two different posts that that its "not working" and why "im waiting" for something like this...
it works on some phones though which means it will communicate
Click to expand...
Click to collapse
I wish it was known what to do though. That's a super low level function.
I will try to make a long story short. A couple of weeks ago I connected my I9300 international (bought in France) to a Macbook Air using Kies. Kies froze and I closed it, and disconnected the phone. I soon found out that the phone was not working, apparently because Kies had started an upgrade that never finished.
I reconnected the phone to the Macbook+Kies, but this did not recgonize the phone any more. After reading a lot from the internet, I realized
1. When I turn on the phone, I get a striped blank screen
2. I could not put the phone in recovery mode
3. I still can get to the download screen
Note that this phone was NOT rooted, and had the original firmware, Android 4.1.1.
Since then, I tried everything I could find on the net. In summary,
1. tried to flash a stock ROM using Odin, but I get a message saying that "there is no PIT partition"
2. I then tried to flash a PIT file. But Odin stops at "get PIT for mapping..." and nothing else happens
3. Also tried the S3 Toolkit, but it will not list the serial and apparently does not recognize the phone
I have read all I could find, and ran short of ideas. Could anyone help me please??? :crying:
maybe this will help.
Still no joy
chrismast said:
maybe this will help.
Click to expand...
Click to collapse
Thanks for the relevant link. I read it all, almost like a dramatic soap opera, every chapter rising in tension. Well, this is what I did.
1. Changed to another computer, now a laptop, virgin of Samsung drivers
2. Installed the drivers from link provided in the indicated thread
3. Downloaded Odin 3.07 again
4. Dowloaded the 3-part firmware as indicated by SirKunon
5. Loaded Odin with mx.pit, code, csc and modem files
6. Connected the phone in dowload mode, drivers were installed, got the "Added" msg and blue ID:COM square
7. Clicked start and got stuck again at "Get PIT for mapping" - see image below
I repeated from 5, now using another USB port. Drivers loaded again, and now I said I did not want Windows to look for drivers on the web. It installed local drivers. I crossed fingers, hit start, got stuck.
Any furter ideas???
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
One of the two , You probably damaged your nand or your phone has the sudden death (Since you are on 4.1.1) Take it to the service center and play dumb
Sent from my GT-I9300 using xda app-developers app
try this http://forum.xda-developers.com/showthread.php?p=15330252
vsop.wiki said:
Thanks for the relevant link. I read it all, almost like a dramatic soap opera, every chapter rising in tension. Well, this is what I did.
1. Changed to another computer, now a laptop, virgin of Samsung drivers
2. Installed the drivers from link provided in the indicated thread
3. Downloaded Odin 3.07 again
4. Dowloaded the 3-part firmware as indicated by SirKunon
5. Loaded Odin with mx.pit, code, csc and modem files
6. Connected the phone in dowload mode, drivers were installed, got the "Added" msg and blue ID:COM square
7. Clicked start and got stuck again at "Get PIT for mapping" - see image below
I repeated from 5, now using another USB port. Drivers loaded again, and now I said I did not want Windows to look for drivers on the web. It installed local drivers. I crossed fingers, hit start, got stuck.
Any furter ideas???
Click to expand...
Click to collapse
never checked re-partition while flashing via odin! try unchecking it!
^ he was flashing a pit file. . It needs to be on.
Damaged nand probably.. go to a service center and explain the kies situation , never ever mention odin.
Sent from my GT-I9300 using xda app-developers app
1. Go to service center.
2. Play as if you were a normal person (we on XDA are special )
3. NEVER MENTION ANYHING ABOUT ROOTING, XDA OR ANDROID DEVELOPING, REMEMBER YOU ARE TRYING TO BE LIKE A NORMAL PERSON.
4. Mention KIES accident if asked what happened.
5. Get free repair and have fun, not your fault anyway
Additional steps for future:
6. Don't buy a Samsung phone again if you ever thing (buy a Sony/Sony Ericsson or Nexus)
Sent from my GT-I9300 using xda app-developers app
bennycop said:
try this http://forum.xda-developers.com/showthread.php?p=15330252
Click to expand...
Click to collapse
Thanks, bennycop. Tried your unbrick, but did not work. Even after installing drivers it did not help. Next step, Samsung service.
And thanks a lot to all that made suggestions, including never buying Samsung phone again. But I did notice that you have an S3!
That would be stupid, if they didn't fix it for free. I see your point. But if they do, why would you never buy a Samsung phone again ? I loved the LG suggestion though. You will certainly .. love.. the ... Experience xD
Sent from my GT-I9300 using xda app-developers app
vsop.wiki said:
Thanks, bennycop. Tried your unbrick, but did not work. Even after installing drivers it did not help. Next step, Samsung service.
And thanks a lot to all that made suggestions, including never buying Samsung phone again. But I did notice that you have an S3!
Click to expand...
Click to collapse
My other phone is an R800i Xperia Play.
It never had any problems at all at any point. No firmware bugs. No errors. Completely open source (good for devs) Sony Ericsson gives devs support as well (remember when they sent FreeXperiaProject 11 Xperia phones in 2011 for FREE just for them to develop Cyanogenmod)
The only problem EVER on the xPlay is the flex cable, because it is between the sliders if one hits the floor with the phone too violently (literally throws it as hard as possibly) or if you keep sliding it out as hard and quick as you can. If the flex cable disconnects then you would have problem (you would not see screen, touchscreen would not work or it would only work under charger)
And for the play it has such a nice and beautiful community in XDA where everyone literally helps each other and has respect for others and they are just nice.
For example:
Developer Sdojoin made music controls on lock screen for multiple ROMs and which can be easily ported into any other ROM as well. (Vokal 1992 adapted it)
I shared a rom with my custom AC!D Sound MOD v5 for Gingerbread (this was before AC!D Gingerbread official which came 4 months later)
Anyway enough Xperia Banter, we're in Samsung area.
BTW. One developer here that had an Xperia 2011 phone here is themer ThilinaC, I'm sure he still likes it A LOT.
Sent from my GT-I9300 using xda app-developers app
Hi xda. I have a atrix 4g which is a at&t model and while flashing a rom it bricked. when i try to open it says failed to boot then it says entering ...... recovery so quickly that i hardly caught what it says. and then screen goes black, nothing.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(this is from google, the problem is same)
the phone doesnt enter recovery or anything else. i know usb jig method but i failed to do it. if you may help me i will really appreciate that
mike4peace said:
Hi xda. I have a atrix 4g which is a at&t model and while flashing a rom it bricked. when i try to open it says failed to boot then it says entering ...... recovery so quickly that i hardly caught what it says. and then screen goes black, nothing.
(this is from google, the problem is same)
the phone doesnt enter recovery or anything else. i know usb jig method but i failed to do it. if you may help me i will really appreciate that
Click to expand...
Click to collapse
So if the message on the screen matches your problem, that must mean that you are like other members of recent. it means you don't know how to use this wonderful creation called a search and need to create pointless threads.
took me all of 5 seconds to do what you didn't do. I mean even if you had typed what you think the screen showed, the auto fill feature would have pointed you in the right direction too
http://forum.xda-developers.com/showthread.php?t=1490903
palmbeach05 said:
So if the message on the screen matches your problem, that must mean that you are like other members of recent. it means you don't know how to use this wonderful creation called a search and need to create pointless threads.
took me all of 5 seconds to do what you didn't do. I mean even if you had typed what you think the screen showed, the auto fill feature would have pointed you in the right direction too
http://forum.xda-developers.com/showthread.php?t=1490903
Click to expand...
Click to collapse
thank you for responding, but i have been searching for days but i hadnt found this thread thanks a lot. and here is another problem: i have a folder named fastbood in c:/ which contains fastboot.exe, adbwinapi and adbwinusbapi.dll but in the cmd screen i failed to do what im supposed to do.
2: Located in the folder where the files are.
i dont know what that means
i guess i did it but it says waiting for device, so the computer doesnt recognize my device
You also need drivers.
All of that has been covered already. Did you search?
ravilov said:
You also need drivers.
All of that has been covered already. Did you search?
Click to expand...
Click to collapse
yes mate i have motorola device manager, as far as i know this the same thing right? just like samsung's kies
i really did tons of search but im almost hopeless. guys who have the same problem did solved it by just taking device to fastboot but mine is not going in that mode. when i plug the device its charger it says same problem and also says battery too low to flash. so im just gonna go and buy a new battery
mike4peace said:
thank you for responding, but i have been searching for days but i hadnt found this thread thanks a lot. and here is another problem: i have a folder named fastbood in c:/ which contains fastboot.exe, adbwinapi and adbwinusbapi.dll but in the cmd screen i failed to do what im supposed to do.
2: Located in the folder where the files are.
i dont know what that means
i guess i did it but it says waiting for device, so the computer doesnt recognize my device
Click to expand...
Click to collapse
yes you do. you just told us where you have the files. navigate via cmd to the folder that has fastboot in it
palmbeach05 said:
yes you do. you just told us where you have the files. navigate via cmd to the folder that has fastboot in it
Click to expand...
Click to collapse
now even if i have the necessary drivers (which come with motorola device manager) pc doesnt recognize my phone
also now my phone now says svf.... failed to boot... entering nflash recovery.... battery too low to flash and screen stays like this and phone gets heat (so we can say it's alive?)
The phone has been alive this whole time. I don't know why you said "hard brick" in the title, this has nothing to do with a hard brick. (Do you even know what a hardbrick is?)
You will need to charge the battery using another phone or an external charger. If you feel confident enough, you could try the trick where you strip a USB cable and connect the wires directly to the battery. (No idea what I'm talking about? Time to use search again.)
mike4peace said:
now even if i have the necessary drivers (which come with motorola device manager) pc doesnt recognize my phone
also now my phone now says svf.... failed to boot... entering nflash recovery.... battery too low to flash and screen stays like this and phone gets heat (so we can say it's alive?)
Click to expand...
Click to collapse
That's rsd mode, I think. From there you can flash an full sbf and start over
Enviado desde mi MB860
ravilov said:
The phone has been alive this whole time. I don't know why you said "hard brick" in the title, this has nothing to do with a hard brick. (Do you even know what a hardbrick is?)
You will need to charge the battery using another phone or an external charger. If you feel confident enough, you could try the trick where you strip a USB cable and connect the wires directly to the battery. (No idea what I'm talking about? Time to use search again.)
Click to expand...
Click to collapse
not hard brick? oh thank god, i said so because the phone does nothing
yeah i searched it before and its calldd factory cable, i havent done it yet but i tried usb jig which was a failure. no one owns an atrix around me, so i just need a external charger and right now im onto it
guys, i really appreciate your helps, im very glad to have you here thanks a lot. i will post here the results
man i told you, it's hard brick i guess.. because i charged the battery a bit then i opened the phone and the problem is the same again, it says entering nvflash recovery in about half a second screen goes black
mike4peace said:
man i told you, it's hard brick i guess.. because i charged the battery a bit then i opened the phone and the problem is the same again, it says entering nvflash recovery in about half a second screen goes black
Click to expand...
Click to collapse
What version of Ginerbread were you on and what did you flash via rsd? exact version and exact file please.
mike4peace said:
man i told you, it's hard brick i guess.. because i charged the battery a bit then i opened the phone and the problem is the same again, it says entering nvflash recovery in about half a second screen goes black
Click to expand...
Click to collapse
Here is short explanation what hard brick is:
Hard bricks are more or likely that you won’t be able to fix it. If you get a hard brick, your phone will not be repaired, there will be absolutely no way to without sending it to the manufacturer. This could be from wiping the entire system without flashing a rom, no way into recovery and no way to get it back. This could be also caused from bad installation files, or turning off/removing the battery from your device during the first installation or boot up sequence. Sometimes you can fix a hard brick, but more often than not your device is going to be broken. This is a fix that is required by the manufacturer of the device. Honestly if you get this, it may just be simpler to go get the device replaced instead of even trying to fix it. HOWEVER make sure you go out and read about it, typing in the exact problem and doing lots of research for your specific device as there may be some hope for the device somewhere.
Click to expand...
Click to collapse
Source: "Soft Brick Vs Hard Brick vs Broken" from Techychat.com by Anthony Burkett
Your phone doesn't get recognized by the p c? On linux you can check dmesg after you plug it to see anything, not sure about windows
Enviado desde mi MB860
palmbeach05 said:
What version of Ginerbread were you on and what did you flash via rsd? exact version and exact file please.
Click to expand...
Click to collapse
im not quite sure cause i bought this phone intentionally via ebay-like web site
yanick76 said:
Here is short explanation what hard brick is:
Source: "Soft Brick Vs Hard Brick vs Broken" from Techychat.com by Anthony Burkett
Click to expand...
Click to collapse
okay soft brick it is, but my phone doesnt do anything but show an error screen (and goes)
andresrivas said:
Your phone doesn't get recognized by the p c? On linux you can check dmesg after you plug it to see anything, not sure about windows
Enviado desde mi MB860
Click to expand...
Click to collapse
oh that is a good news, can you please tell this with a bit more detail? but here's what i understood: on linux ( i have ubuntu ) open terminal, after you plug your phone to usb port type "dmesg" and see something
i really appreciate all of your efforts thank you millions times
mike4peace said:
[...]
oh that is a good news, can you please tell this with a bit more detail? but here's what i understood: on linux ( i have ubuntu ) open terminal, after you plug your phone to usb port type "dmesg" and see something
i really appreciate all of your efforts thank you millions times
Click to expand...
Click to collapse
Exactly. try it with sudo, just in case (sudo is for run the command as root, with full privileges).
From there, you can go several ways
andresrivas said:
Exactly. try it with sudo, just in case (sudo is for run the command as root, with full privileges).
From there, you can go several ways
Click to expand...
Click to collapse
i typed just dmesg and there were several lines with words but nothing about the phone. lets say i found a jtag machine or whatever, can it recover my phone?
mike4peace said:
i typed just dmesg and there were several lines with words but nothing about the phone. lets say i found a jtag machine or whatever, can it recover my phone?
Click to expand...
Click to collapse
JTAG depends heavily on your ability to solder tiny surface mount components. Good luck.
I woke up this morning to my phone stuck on the boot screen. I have tried pulling the battery and turning the phone back on and it still gets stuck at the same screen. I am running alliance build 26. have also tried booting in to recovery but it just gets stuck at the teamwin blue screen. any suggestions would be greatly appreciated.
Thanks
bluedevils0000 said:
I woke up this morning to my phone stuck on the boot screen. I have tried pulling the battery and turning the phone back on and it still gets stuck at the same screen. I am running alliance build 26. have also tried booting in to recovery but it just gets stuck at the teamwin blue screen. any suggestions would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
I'm assuming that you were on 4.1.2 with unlocked bootloader since you have TWRP on the phone.
You might have something that's become corrupted in data/cache. You can try to ODIN flash the stock recovery back to the phone (see this thread: http://forum.xda-developers.com/showthread.php?t=2792511), then try wiping the cache, doing factory reset, and see if it will boot up again. (This will wipe all your data on the ROM, so hopefully you have a nandroid backup). If that seems to fix things, you can ODIN flash TWRP back to the phone and then restore a previous backup. (If you were on 4.3 with safestrap... then don't try to ODIN flash the stock recovery because the bootloader is locked).
If that doesn't fix things, sounds like you may have to use ODIN to restore to stock 4.1.2, then run CASUAL again, etc... Section 1b on Droidstyle's guide will help you restore to stock if needed: http://forum.xda-developers.com/showthread.php?t=2024207
mattnmag said:
I'm assuming that you were on 4.1.2 with unlocked bootloader since you have TWRP on the phone.
You might have something that's become corrupted in data/cache. You can try to ODIN flash the stock recovery back to the phone (see this thread: http://forum.xda-developers.com/showthread.php?t=2792511), then try wiping the cache, doing factory reset, and see if it will boot up again. (This will wipe all your data on the ROM, so hopefully you have a nandroid backup). If that seems to fix things, you can ODIN flash TWRP back to the phone and then restore a previous backup. (If you were on 4.3 with safestrap... then don't try to ODIN flash the stock recovery because the bootloader is locked).
If that doesn't fix things, sounds like you may have to use ODIN to restore to stock 4.1.2, then run CASUAL again, etc... Section 1b on Droidstyle's guide will help you restore to stock if needed: http://forum.xda-developers.com/showthread.php?t=2024207
Click to expand...
Click to collapse
yes i was running alliance build 26 so last firmware i was on was 4.1.2 with unlocked bootloader. so here is whats going on so far. i tried downloading and installing stock firmware and it failed half way through. now when i run odin and plug my phone in it doesnt show. i have tried reinstalling drivers and still nothing. any help or suggestions would be greatly appreciated.
bluedevils0000 said:
yes i was running alliance build 26 so last firmware i was on was 4.1.2 with unlocked bootloader. so here is whats going on so far. i tried downloading and installing stock firmware and it failed half way through. now when i run odin and plug my phone in it doesnt show. i have tried reinstalling drivers and still nothing. any help or suggestions would be greatly appreciated.
Click to expand...
Click to collapse
Does your phone still boot into Download (Odin) mode?
If you could post the log from Odin, it should list the error that happened when it failed and this would assist others to help you troubleshoot.
Edit : This YouTube video shows one idea to try to get Odin to recognize the phone again: https://www.youtube.com/watch?v=YO7TVY2UXEY&feature=youtube_gdata_player
I s isn't look to see what the error code was when it happened. I have tried the battery pull while plugged in and it still doesn't show when I plug my phone in. I'm starting to get worried the phone is shot but willing to do whatever I have to to get it back up and running again.
bluedevils0000 said:
I s isn't look to see what the error code was when it happened. I have tried the battery pull while plugged in and it still doesn't show when I plug my phone in. I'm starting to get worried the phone is shot but willing to do whatever I have to to get it back up and running again.
Click to expand...
Click to collapse
Can you confirm if the phone still boots into Download mode (what does it do when you press Volume down+Home+Power Button)?
mattnmag said:
Can you confirm if the phone still boots into Download mode (what does it do when you press Volume down+Home+Power Button)?
Click to expand...
Click to collapse
yes it still boots in to download mode. at first my computer would read it when plugged in but after the failed firmware install on odin it will now not even read my phone when plugged in.
bluedevils0000 said:
yes it still boots in to download mode. at first my computer would read it when plugged in but after the failed firmware install on odin it will now not even read my phone when plugged in.
Click to expand...
Click to collapse
That's good that you can still get into download mode and means you will likely be able to fix it. I suspect that something happened with the computer when your attempt to ODIN flash failed...and even though you uninstalled/reinstalled the Samsung drivers , something is probably still messed up with the computer. If you have another computer available to try it on, you may give that a go.
Another solution might be to use the "System Restore" feature on the computer to restore to a previous point and see if that will fix things. If it does and ODIN can recognize the phone again, then you might try some of the tips that I've read on various posts....
Here's some of those tips for ODIN flashing:
-Always verify the md5 on your downloads to make sure they aren't corrupted. Here's a good program (WinMd5) for Windows to verify MD5's if needed. I noticed that the link for the stock 4.1.2 firmware on Droidstyle's guide doesn't have a md5. The md5 for stock 4.1.2 VRAMC3 firmware should be MD5: d04cc7e7717f60b06ce82ffdf85703cd. If that doesn't match with what you've got... then you may try to download the stock firmware again from this link (KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.tar.md5 ) and then verify the md5 again.
-Verify the md5 on your pit file -- it should be a md5 of: 6e874ba443d59ea114e48c1a57f3dfaa
-Make sure that your phone has at least 50%+ charge on the battery
-Disable Firewall / Antivirus software on the computer before running ODIN
-Make sure you are running ODIN as Administrator
-Try a different USB port on the computer (I've read where you should use a USB 2.0 port, not 3.0-- and also using the port on the back of desktop PC's seems to be recommended/ or the one closest to the power source --you'll have to experiment).
-Try a different USB cable (preferably the cable that came with the phone if you have it and it is still in good shape).
I know this can get frustrating, but I'm hoping that as long as you can still get the phone into download mode, that you can restore it back to 4.1.2. Maybe others will also read this thread and chime in with some additional tips or ideas if none of this works. Doing some more searching in the XDA threads and Google will also probably give you some more ideas.
:fingers-crossed: Good luck.
mattnmag said:
That's good that you can still get into download mode and means you will likely be able to fix it. I suspect that something happened with the computer when your attempt to ODIN flash failed...and even though you uninstalled/reinstalled the Samsung drivers , something is probably still messed up with the computer. If you have another computer available to try it on, you may give that a go.
Another solution might be to use the "System Restore" feature on the computer to restore to a previous point and see if that will fix things. If it does and ODIN can recognize the phone again, then you might try some of the tips that I've read on various posts....
Here's some of those tips for ODIN flashing:
-Always verify the md5 on your downloads to make sure they aren't corrupted. Here's a good program (WinMd5) for Windows to verify MD5's if needed. I noticed that the link for the stock 4.1.2 firmware on Droidstyle's guide doesn't have a md5. The md5 for stock 4.1.2 VRAMC3 firmware should be MD5: d04cc7e7717f60b06ce82ffdf85703cd. If that doesn't match with what you've got... then you may try to download the stock firmware again from this link (KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_user_low_ship.tar.md5 ) and then verify the md5 again.
-Verify the md5 on your pit file -- it should be a md5 of: 6e874ba443d59ea114e48c1a57f3dfaa
-Make sure that your phone has at least 50%+ charge on the battery
-Disable Firewall / Antivirus software on the computer before running ODIN
-Make sure you are running ODIN as Administrator
-Try a different USB port on the computer (I've read where you should use a USB 2.0 port, not 3.0-- and also using the port on the back of desktop PC's seems to be recommended/ or the one closest to the power source --you'll have to experiment).
-Try a different USB cable (preferably the cable that came with the phone if you have it and it is still in good shape).
I know this can get frustrating, but I'm hoping that as long as you can still get the phone into download mode, that you can restore it back to 4.1.2. Maybe others will also read this thread and chime in with some additional tips or ideas if none of this works. Doing some more searching in the XDA threads and Google will also probably give you some more ideas.
:fingers-crossed: Good luck.
Click to expand...
Click to collapse
okay so did a system restore as i dont have another computer available right now. was really hoping that would work but i still got nothing. plug my phone in and it does absolutely nothing. dont know where else to go from here. appreciate all your help but it is really starting to seem like a lost cause.
bluedevils0000 said:
okay so did a system restore as i dont have another computer available right now. was really hoping that would work but i still got nothing. plug my phone in and it does absolutely nothing. dont know where else to go from here. appreciate all your help but it is really starting to seem like a lost cause.
Click to expand...
Click to collapse
If the phone boots into download mode, I wouldn't give up on it until trying everything. What have you tried other than the Windows system restore? Trying different USB ports/ different cables seem to be 2 of the most common fixes I've read about for this issue.
Does your computer indicate anything at all when you plug in the phone? (You can check to see if the computer shows if any devices are connected by looking in the computer's device manager when the phone is plugged in. This link should help you: ( http://www.tech-recipes.com/rx/504/how-to-uninstall-hidden-devices-drivers-and-services/ ). You can try uninstalling any drivers that might be related to Samsung/Android. Then reboot the computer and try reinstalling the Samsung drivers again. Here are some links for the Samsung drivers if needed: Official Download link for Samsung Drivers - -- (or these... Alternate link for Samsung Drivers, which are what I've been using).
Hopefully, you can get the computer to recognize the device and then try ODIN again. Are you using ODIN 3.07 from this link? If not, that's the one that is suggested for our phones.
If the computer can recognize the phone, but ODIN isn't working, you might try to restore the device with Samsung Kies 2.6, which you can find here - http://www.samsung.com/us/kies/.
Verizon also has a Repair Assistant which might be worth a try. You can learn more about it here: http://www.verizonwireless.com/support/devices/knowledge_base.html/80201/.
I hope that I'm not overwhelming you with information... but I thought it would be good to point out that there may still be options to try before giving up.
I've got to take care of some errands and do yard work this afternoon, so I won't be available to check back for quite a while. There are TONS of people on XDA with much more knowledge than me... so I'm hoping that if you can't get it fixed with what I've provided, that some others will provide some suggestions.
okay so i have tried almost everything that has been suggested to get my computer to recognize my phone. i even plugged it in to another computer last night and even that computer did not do a thing once plugged. have tried different cables and different ports and so far nothing. very very frustrating i frickin love my gn2 and was hoping to get a few more months out of it until i could afford a note 4. thanks for all your help if you can think of anything else just let me know im willing to try anything to get it back up and running.
bluedevils0000 said:
okay so i have tried almost everything that has been suggested to get my computer to recognize my phone. i even plugged it in to another computer last night and even that computer did not do a thing once plugged. have tried different cables and different ports and so far nothing. very very frustrating i frickin love my gn2 and was hoping to get a few more months out of it until i could afford a note 4. thanks for all your help if you can think of anything else just let me know im willing to try anything to get it back up and running.
Click to expand...
Click to collapse
Hi bluedevils0000,
Unfortunately, without a that error report from ODIN, we're really just guessing on why the ODIN flash didn't work. Did that other computer that you tried have the Samsung Drivers installed on it... and were there any other mobile device drivers on it that might have caused conflicts? Do you also have Samsung Kies installed on your computer? .... if so, it might be causing conflicts.
Do you know what percentage your battery was at when you tried to restore with ODIN... and is it currently charged to at least to 50%? I've read a couple posts where the battery needs to be charged for the flash to work properly... so if your battery is old, I'm wondering if it's went bad and if charging it fully could make a difference.
If you haven't plugged the phone in to the computer yet and looked at the Windows Device manager to see if the phone is showing any sort of connection at all, then that would be my next step. Look to see if there are any yellow exclamation points on any of the devices--like the picture here:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Maybe try the battery pull trick as well when looking at device manager with the phone plugged in. There's an option in Device Manager to see hidden devices, so make sure to enable that. Let's hope that your computer will show something in Device Manger when you try these things. You can try uninstalling the Samsung Drivers again, then try manually uninstall the devices in Device Manager that look to be related to Android, adb, mass storage, portable devices, etc... and see if that makes any sort of difference. Unplug your phone and reboot the computer afterwards... then reinstall the Samsung drivers (the ones linked in my previous post). If you don't know how to manually uninstall devices, you can get this info through a Google search.
I'm running out of ideas... but I would say that as long as the phone goes into download mode and something hasn't happened that damaged your phones micro usb port, then there should still be hope to restore the device with ODIN, Samsung KIES, or Verizon's Repair Utility.
so once again i sat down last night and retried everything that i had been doing to get my computer to recognize my phone. i opened device manager and plugged my phone in and it shows absolutely nothing. even tried the battery pull while still plugged in and it still shows nothing. i had kies downloaded on my computer so i uninstalled it also unistalled all drivers again then restarted and reinstalled drivers still to no avail. im lost and running out of ideas.
If you went to Device Manager and chose to show hidden devices /rescanned for hardware changes, manually uninstalled devices in Device Manager that look to be related to Android, adb, mass storage, portable devices, etc..., rebooted the computer & reinstalled Samsung Drivers... If you have tried all these things, then I'm not sure why it won't show any sort of connection. It could be that your phone's micro usb port is bad.
Here's another web link that offers possible solutions to fix usb connection issues: ( http://www.wintips.org/how-to-fix-usb-device-not-recognized-not-installed/). Maybe one of these solutions will help.
Sorry.... but I'm out of ideas too and can't think of any other solutions if you can't get the phone to communicate with the computer.
Let's hope there are some other XDA members who can offer other ideas.
Did you delete the file that needs to be deleted in Device Manger? I ran into that before, I would run odin, then my phone would no longer be recognized until you deleted the correct file/port in Device Manager? I know it was mentioned above, just checking you deleted the correct port under device manager.
https://www.youtube.com/watch?v=zzghcV8HVVk&feature=youtube_gdata_player
mattnmag said:
If you went to Device Manager and chose to show hidden devices /rescanned for hardware changes, manually uninstalled devices in Device Manager that look to be related to Android, adb, mass storage, portable devices, etc..., rebooted the computer & reinstalled Samsung Drivers... If you have tried all these things, then I'm not sure why it won't show any sort of connection. It could be that your phone's micro usb port is bad.
Here's another web link that offers possible solutions to fix usb connection issues: ( http://www.wintips.org/how-to-fix-usb-device-not-recognized-not-installed/). Maybe one of these solutions will help.
Sorry.... but I'm out of ideas too and can't think of any other solutions if you can't get the phone to communicate with the computer.
Let's hope there are some other XDA members who can offer other ideas.
Click to expand...
Click to collapse
i have also noticed that when i plug the phone in to its stock charger i get the battery on the screen but it does not ever show the green portion at the bottom of the battery like it usually does when it is charging. it just shows the battery that normally shows up with the little circle in the middle and never goes any further. i attached a picture to show you exactly what it looks like when i plug it in to charge.
bli
bluedevils0000,
Can you post the name of the file that you were ODIN flashing over to your phone when ODIN failed? That might help others help you.
The file I was attempting to flash was KIES_HOME_I605VRAMC3_I605VZWAMC3_1098177_REV04_use r_low_ship.tar.md5 it started fine and stopped half way through and would no longer do anything when I plugged my phone in to my computer.
That was definitely the correct file to flash to restore the phone to 4.1.2. I'm assuming you followed Section 1B of Droidstyle's GUIDE in development section and placed the file in the PDA slot in ODIN.
I wish I knew more ideas to try to help you to get the computer to recognize the phone again when you put it in download mode. It could be that your phone is having a hardware problem. I've provided all the links and ideas I can think of for now. You can bump this thread periodically to keep it alive to see if others will respond with additional ideas.
well thank you for all the time you have put in trying to help me resolve my problem. i truly do appreciate it and this right here is why i love the android community and could never stray from android. i will keep you updated but at this point i would have to agree that it is most likely a hardware issue. the phone wont charge and my computer wont recognize it so as much as it sucks now im stuck with a broken phone until the day comes when i can afford a note 4. once again thank you.