[Q] SGP 5.0 U.S. Ver. HARD BRICKED! HELP!!! - Samsung Galaxy Player 4.0, 5.0

Hi, I'm pretty new to Android and stuff, but I bricked my SGP 5.0 with a mod.. At first I was able to go into download mode but then I think I flashed the wrong firmware and now the device is completely unresponsive. Any advice on what to do would be great. I also already checked out all the forums on here but none have been able to work for me. Thanks in advance!

Yup. I was in the same boat as you. Exact same one actually. However i managed to get best buy to to switch mine out because i said it was "defective". I tried the linux tutorial with resurrector and nothing as well. And i also tried.... Well everything. From my thread i posted I gathered that no one (at leasr on xda) knows how to unbrick these damn things. So until these get more popular. Your sunk. Sorry pal:/

try the resurrector.. it's worked for me on a few occasions. it brought mine back from not even being able to turn on.
one thing that's not incredibly obvious with it though is you have to hold "vol up" for download mode while the program is doing its thing. if you don't hold the button it wont work.

Tried it.
I tried that already though and it wouldn't let me unbrick it, but I'll give it another try with what you said about the Vol.+Up keys! Thanks!

I don't have a 4.0 player but my 5.0 player was bricked initially the first time I tried to root... To get it into Download mode you need to hold Vol-(Vol down) button and Power button as the unit is powering up. Hold both for a few seconds until you see the yellow download mode picture.
Good luck

Are you able to get to the download mode? If so I have a simple solution. If not, start a download of Ubuntu to have the proper stuff to fix your problem.

I'm running Ubuntu with the Unbrickable Mod and I have it in download mode and I have virtualmachine installed with windows and sammy drivers but my player wont show up in odin3. Any ideas to get it shwoing?

Either, shutdown VM and see if usb device shows up in windows. If it still does not then unplug usb from pc and then plug it back in, or transfer usb back to host in VM.

I tried that already.. It still doesn't show up in Odin3.

Check device manager for vm drivers for usb and remove them?
Sent from my YP-G70 using XDA App

Hmmm.... I don't really understand what you mean.. Sorry!

When you attach a usb device to a VM the vm software replaces the drivers of the USB device on the host with virtual drivers that redirects IO from the USB device to guest If the original driver does not get put back in during a detach then IO never goes back to the host.
I know that sounds complicated but I do not know how else to explain it...
Sent from my YP-G70 using XDA App

Okay, i fixed that. I have it in download mode, i uploaded the bootloaders that adamoutler has. I uploaded the stock rom you have. Odin3 said pass. But its still in download mode, autoreboot was checked. when i try turning it on, the download screen appears but the icon for download goes all over the screen then stops. Its still recognizeable in odin3 too. Any ways to get this thing going?

My stock rom does not include bootloaders and adam outler's bootloaders are only a temporary solution. What you need to do is flash a full international rom that has bootloaders. Then flash my stock rom to fix the capacitive buttons.
Sent from my YP-G70 using XDA App

Alright I see what you mean!! Where can I get a full stock rom though?

Well, I'm not exactly sure. I used to get mine from samfirmware.com but they have recently changed their site. You might try rumirands stock recovery in the dev section. You'll want to open it up and look for files like: boot.bin and Sbl.bin . These are the bootloader files. This will verify that you have a rom with bootloaders in it.
Sent from my YP-G70 using XDA App

Alright thanks a lot! Ill try rumirands stock and if that doesnt work ill go to samfirmware.com. Ill be back with the results in a few hours!!

Well Rumirands ROM did not. work. samfirmware.com only has the French and Chinese Rom versions so that doesnt help either. I downloaded a .tar.md5 from here : http://www.4shared.com/file/zhZjh0EY/package_us235tar.html..... Should I flash this by itself or do I need a pit file too?

The language of the ROM does not matter. What matters is that is has the boot loaders. Flashing my Stock ROM over it will fix language and capacitive buttons.
Make sure you have followed AdamOutler's intructions precisely. I don't recall having to use a pit file other than the one in his intructions but if comes to it, it is another troubleshooting point.

Realyy? Hm alright so what your saying is that when I have it in download mode, and with, lets the the chinese firmware, I flash that, turn on my sgp to see if it loads and then put it in download mode again and flash your stock rom, that it might work fine again???

Related

[Q] Plz Help me.....Plz..........

I have a vibrant and I was rooted my cell phone when the phone's version was 2.1 eclair
I tried to upgrade to 2.2 froyo by official updating
After updating my phone did not show any screen so i tried to return original rom by odin.........
However, odin did not work for the phone... Always stopped when odin tried to install modem.bin.............
And now my phone does not work and even I cannot turn downloading mode or recovery mode........ It is just not work like when the phone's battery is done....
Plz if someone know how to fix it, explain me...........
Not sure what's going on here, but a few more pieces of information might help others figure it out:
First, what ROM were you running? Given the fact that you officially updated, I'm guessing rooted stock? Not sure if this is relevant to your problem, but were you running a lagfix of any kind?
Second, how did you enter Download Mode? Did you select it from a Shutdown menu? Or did you use the Volume buttons while plugging in the phone? EDIT: Forgive my stupidity. You obviously used the buttons, as you entered Download Mode after bricking.
Third, what version of Odin are you using? Did or didn't you select repartition?
Finally, which stock file did you use when restoring?
Take out battery , plug usb into comp. Then while holdin vol up and down plug in usb.
Sent from my SGH-T959 using XDA App
hi
I rooted the phone before I tried to upgrade official update.
And I did not use any custom rom, I just used legfix
And I tried to use T959UVJFD this rom to restore my phone....
and I used odin v1.7
i tried to click or non click repartition both but when I did first trying
I did not check repatition and I used volume down button to join dowloarding mode.
try to Odin with Eugene's froyo that doesn't brick THEN Odin back to stock. Link should be in the Bible thread at the top.
This method has helped me in a brick before.
lol i swear im explainin this second time this issue already today , go hook up your phone to wall cahrger for 5 min , unplug cabole from chsrger and unplug phone from cable hook up cable to computer remove battery from your phone hold vol up vol down hook up usb cable that is already hooked up to computer connect it to phone while still holding vol up vol down bam u got it there if it didnt work hook up phone to wall charger to 10 min instead of 5 trust me i went thru same storry .
i went with every imaginable story of brickin my vibrant lol
i thinkk chance of you brickin that phone to the point that wont ever turn back on is like one in 1000 if not more unles u fried the phone and i dont know id thats possible P
First, make sure you have at least Odin3 v1.3 when attempting this. This version includes a Samsung specific .dll that is required to get a successful load with Odin. Then follow these instructions to flash back to stock.
http://martint.net/2010/how-to-use-odin-to-go-back-to-stock-jfd-2/
from there, just root, install Clockwork Mod Recovery, flash and enjoy.
I used 5 different roms to restore my phone..... but it still stop when odin try to install modem.bin............ I do not understand and very bad.... how can i fix it...
and I tried to find eugene's froyo rom... but I cannot find download link........
plz help me.... I will appreciate every guys......
ss10823 said:
I used 5 different roms to restore my phone..... but it still stop when odin try to install modem.bin............ I do not understand and very bad.... how can i fix it...
and I tried to find eugene's froyo rom... but I cannot find download link........
plz help me.... I will appreciate every guys......
Click to expand...
Click to collapse
Then its odin. Try to find an older version. Yep I said that. I run 1.3 still because it works every single time.
Sent from my SGH-T959 using XDA App
I'm just grasping at straws here, but you might try using every version of Odin (as has already been suggested by several posters above). Also, make sure you remove your SIM and sd card. Lastly, run Odin as an administrator. I don't think the admin part is related, but it can't hurt to try.
Look for Eugene's froyo on Android Spin. I DLed it a few days ago.
Sent from my SGH-T959 using XDA App

[Q] Read all the posts I can find and I still can't flash with odin! Please help!

Hi everyone,
I brought a new galaxy s2 phone about 4 weeks ago and it has spent most of that time soft bricked since I tried to update it to the newest firmware, K14....
I am using windows 7 starter, 32bit. I have installed kies, uninstalled and re-installed kies, tried uninstalling kies and just using the drivers.
Recently I did a clean install of windows, installed kies, as more drivers seem to be recognized and downloaded odin v1.85. I restart the computer, start task manager end all processes that say kies, run odin as a administrator, put the tar file in pda, only auto reboot is selected. I then plug in the phone, in download mode, wait for yellow box and press start and the process only goes as far as boot.bin.
I have tried all of my usb ports and the only difference is the number of the modem installed driver and how far along odin gets. With two ports it only goes as far as setup connection which was as far as anything went before I re-installed windows. I have replaced the usb cable and made sure the phone battery is fully charged. The phone was put into usb debugging mode before it was bricked. I have attached a picture of what drivers get installed when I plug in the phone. The firmware I am attempting to flash is the uk 3 version off the firmware page of this website.
Please can somebody give me the solution it is driving me nuts!
Sorry for waffling but I figure you need to know what I've tried so that I don't waste anybodies time.
Thanks guys
Did you try a different stock rom? Did you try a different pc? Or if you want to, flash a CF-root kernel. Then boot in recovery and flash a rom of your choice.
The flashcounter will start and stock roms can't be flashed this way (at least as far as I know).
Is your phone a I9100 model?
I ask this to make sure you are trying to flash the correct firmware for your device.
Sent from my GT-I9100 using XDA App
Cookoospite said:
Hi everyone,
I brought a new galaxy s2 phone about 4 weeks ago and it has spent most of that time soft bricked since I tried to update it to the newest firmware, K14....
I am using windows 7 starter, 32bit. I have installed kies, uninstalled and re-installed kies, tried uninstalling kies and just using the drivers.
Recently I did a clean install of windows, installed kies, as more drivers seem to be recognized and downloaded odin v1.85. I restart the computer, start task manager end all processes that say kies, run odin as a administrator, put the tar file in pda, only auto reboot is selected. I then plug in the phone, in download mode, wait for yellow box and press start and the process only goes as far as boot.bin.
Possibility one bad firmware file or wrong file ,
Or not using Samsung USB cable .
jje
Click to expand...
Click to collapse
Hi Lenny,
Yh, i have tried it on my desktop which runs 7 home premium. Clean install with same results. Tried the K14 firmware a few times but that never got any further than setup connection. Don't understand the rest of your post sorry. Can you do a flash for dummies thing? And is there a firmware you would recommend trying?
@ aceofclubs -the box says i9100 and so does the sticker in the back.
@ JJEgan - the first cable I used was the one in the box and while the one I have replaced by ebay, they had good feedback. The K14 firmware was given to be by a user of the galaxy s2 that he had successfully flashed with.
Does the phone look to have installed correctly, the guy who gave me the firmware said he had abd appear in device manager, which I haven't got. Also after the phone is finished installing drivers if I click in the system tray, the green icon that shows devices that are present is not there and neither is the phone but if I go into device manager samsung composite device is.
Cookoospite said:
Hi Lenny,
The K14 firmware was given to be by a user of the galaxy s2 that he had successfully flashed with.
Does the phone look to have installed correctly, the guy who gave me the firmware said he had abd appear in device manager,
Better of following the instructions than second hand stuff .
Download firmware from stock rom thread no excuses of bad firmware then .
Stock Roms .and csc
http://forum.xda-developers.com/showthread.php?t=1075278
jje
Click to expand...
Click to collapse
Thanks for the suggestion JJegan but I just tried another firmware from the link you provided above with no success, stopped at setup connection. What is abd and do I need it? Think I must be missing some drivers!
Cookoospite said:
Thanks for the suggestion JJegan but I just tried another firmware from the link you provided above with no success, stopped at setup connection. What is abd and do I need it? Think I must be missing some drivers!
Click to expand...
Click to collapse
No you dont need a ADB neccesarily for flashing. ADB (Android Debug Bridge) is a tool that comes with the Android SDK that allows you to control and interface with your Android device. Well do u have the phone specifications before bricking it, like Model No, Built, CSC, Kernal Etc.
First try to uninstall Kies and Install the latest version, so that you have the latest drivers.
Check the Intratech thread on Stock ROM ( http://forum.xda-developers.com/showthread.php?t=1075278) and download the correct rom.( I presume you have I9100 Intenational Version of S2). Open Odin 1.85, do not change any options, brownse and put the stock rom u downloaded into the PDA section and click on start button, you should be good.PM me if you have any issues.
The above didn't work. Here's what I got:
Cookoospite said:
Thanks for the suggestion JJegan but I just tried another firmware from the link you provided above with no success, stopped at setup connection. What is abd and do I need it? Think I must be missing some drivers!
Click to expand...
Click to collapse
AS you have the yellow box in Odin you have the drivers all the firmware in that link works .
run odin as a administrator, put the tar file in pda, only auto reboot is selected. I then plug in the phone, in download mode, wait for yellow box and press start
Lets do this the right way just to be sure . Open Odin put the tar file in PDA
go to download mode at first screen download mode on phone follow instruction ( vol up from memory ) after next screen connect Samsung USB cable to phone and PC .
jje
Thanks, think I've done that anyway but, just to check, what do you mean by next screen?
The screen when you are in download mode and press volume up.
Yh that is what I'm doing, thanks tho. Can someone please give me a reliable link to an older version of Odin to try? At the mo I am using v1.85, this the latest version?
Sent from my GT-I9100 using XDA App
Odin 1.3 here
Cookoospite said:
Yh that is what I'm doing, thanks tho. Can someone please give me a reliable link to an older version of Odin to try? At the mo I am using v1.85, this the latest version?
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
So close! I plugged the phone in and got as far as cache with the green progress bar showing just the tiniest bit. Left it for over an hour but the bar didn't move at all! Encouraged I restarted the computer to try again only to find that now the computer and odin won't recognize the phone until I uninstall and reinstall kies and always hangs on cache. I restarted in the first place as the phone never shows in the system tray. Sorry to be a bore but have you any idea why everyone else can plug in and flash and my machines refuse to! I welcome any ideas you have. Thank you.
Instead of Odin, you could try Heimdall. Maybe that will work for you.
http://forum.xda-developers.com/showthread.php?t=1104826
Thanks Lenny. Don't know how to use it tho no boxes like on the tutorials I have watched in the latest version. Can you clue me in please?
Sent from my GT-I9100 using XDA App
Here is a guide, it should work the same for our phone.
http://forum.xda-developers.com/showthread.php?t=878686
Thanks. Have to wait a couple of days to try it now. Happy Christmas
Sent from my GT-I9100 using XDA App
hey hope everyone had a good christmas and new year. Still no joy, where do I get PIT files to flash with the newest version of heimdall to go with our firmware? The newest version won't let me add files until I enter a PIT. I tried version 1.1 but I couldn't get it to recognise a compatible device.
On the odin front: I thought I'd cracked it. It started flashing, took hours but I had half a green progress bar and then it just seem to freeze. Also this seems replicable a few times and then I get stuck at setup connection again. I then have to do a system restore to get it to flash to the furthest point again. Does this give anyone any clues? Or does anyone know of any heimdell packages I could try? And the long shot, any way of getting firmware on to an sd card and flashing that way when a phone is soft bricked?
Sorry if I'm annoying you but there has to a way round this. I brought a rooted one to use while this is sorted, love the phone but need to know I can update and be able to sort it out if things go wrong.
Thanks again for your help and suggestions.

More Help!

If someone could provide me/direct me to a ROM with bootloaders, I'd be very thankful. Or if someone could tell me how to save my bricked player, that would be nice too. Thanks!
EcHoFiiVe said:
If someone could provide me/direct me to a ROM with bootloaders, I'd be very thankful. Or if someone could tell me how to save my bricked player, that would be nice too. Thanks!
Click to expand...
Click to collapse
I used the guide http://forum.xda-developers.com/showthread.php?t=1386669 to resurrect a player I bought fully bricked. No sign of life but now it's running normally. Go to the end of the thread and read my post.
I had to do a few attempts with diffent bootloaders and roms but at the end, I was able to get it back.
I am sure you have read most of the thread I pointed out to you already, but retry the steps since that is how I was able get mine to reboot normally.
Use the resurrector in Linux to get the player into Download mode (it went from black screen to showing Phone(!)PC icon). Trick is to keep it plugged in, since unplugging it shuts the player down and can't get Download mode with the button combos. So you will either need to have a Linux box with Virtual session of Windows to run Odin or, as my case, a dual boot. If you use the dual boot, when you switch from Linux to Windows, do not power down. Instead, reboot. It keeps the USB port powered and the player stays in Download mode (Phone(!)PC). In Windows run Odin to load bootloaders. You will need to flash a couple different bootloaders.
I flashed the Download mode only bootloader along with the pit file (included in the OP of the thread ^) to get the player into Download mode. It was stuck there until I flashed the SamsungPlayer bootloader (all found in the thread above) and got it to go into Recovery mode. Once there, I flashed a rom with CWM, factory reset and reboot... worked for me.
EcHoFiiVe said:
If someone could provide me/direct me to a ROM with bootloaders, I'd be very thankful. Or if someone could tell me how to save my bricked player, that would be nice too. Thanks!
Click to expand...
Click to collapse
As per the PM that I sent you, I'm also putting the link to the russian froyo firmware that I found, here. This firmware does have bootloaders in the firmware.
http://www.4shared.com/zip/VtAB8dCU/G70JKKE3_STOK_222RU_.html
Good luck and let me know how it goes.
Both of you guys helped me out, thank you so much!!
Sent from my Galaxy Nexus S using XDA

[Q] Stuck in Odin mode "Could not do normal boot."

I recently got my new Verizon Galaxy S4 and decided to play around with it. I got it rooted fine and got a few apps on there (like Titanium backup) and decided that, since I would eventually want to play around with ROMs, I would want to unlock the phone.
I looked around and found there were some options for me, the one I chose being the "all in one" option that roots, unlocks and installs a custom recovery mode for you. I went through this process and now get nothing but the Downloader Mode (could not do normal boot). Even if I pop out the battery and try to reboot it, I get this screen.
I later found that apparently the ME7 model currently will not accept attempts to unlock the phone and install a custom ROM or recovery menu. How do I fix this? I tried using Odin, but it doesn't recognize the phone as being connected. I am currently trying other methods like Kies, to see if there is any way to at least to an emergency recovery and get it back to normal.
EDIT: Ran into the same issue with Kies as I did with Odin, it does not see anything connected to the computer.
Do you have the correct drivers installed? Does adb recognize the device? You're in Odin mode when you try to use Odin to push something? I believe with ME7 you can Odin back to the official stuff.
Sent from my SCH-I545 using Tapatalk 4
TheColdOne said:
I recently got my new Verizon Galaxy S4 and decided to play around with it. I got it rooted fine and got a few apps on there (like Titanium backup) and decided that, since I would eventually want to play around with ROMs, I would want to unlock the phone.
I looked around and found there were some options for me, the one I chose being the "all in one" option that roots, unlocks and installs a custom recovery mode for you. I went through this process and now get nothing but the Downloader Mode (could not do normal boot). Even if I pop out the battery and try to reboot it, I get this screen.
I later found that apparently the ME7 model currently will not accept attempts to unlock the phone and install a custom ROM or recovery menu. How do I fix this? I tried using Odin, but it doesn't recognize the phone as being connected. I am currently trying other methods like Kies, to see if there is any way to at least to an emergency recovery and get it back to normal.
EDIT: Ran into the same issue with Kies as I did with Odin, it does not see anything connected to the computer.
Click to expand...
Click to collapse
You need to make sure you have the drivers for the phone and have a solid USB connection (I prefer the rear of a tower)
sent from my GE gs4
I ended up getting it to work. I had to go here:
http://www.intel.com/support/chipsets/inf/sb/CS-013541.htm
and get files to get the computer to recognize the device. Even afterwards, Keis had no idea what was going on, and Odin saw it and was able to install a stock firmware I downloaded earlier, saving the phone.
For now I will be satisfied with just root access and will wait for ROM capabilities.
I hate to hijack a thread but I'm stuck here. My GS 4 (Vzw) was supposedly successfully rooted using TWRP, but now I have no way to enter any sort of recovery. The package I downloaded for the root does not have an Odin version to run. I've been getting the endless prompts to install the 4.3 update but there is no way to do this on my phone. I get the same "Could not do normal boot. Odin mode. Write protection enabled" message with the downloading screen. I try to boot into recovery via CWM or Goomanager but it always goes to the same screen. I can't make any backups or restore now either or I would just do a factory reset. Any ideas? I'm on VRUAME7.
Um.... there's no recovery available with ME7.... are you on the MDK bootloader?
Sent from your mom's smartphone
I don't think so but how would I confirm? I'm just trying to get the 4.3 update installed but at every attempt it goes into Odin Mode and gets stuck.
BoltsRUs said:
I don't think so but how would I confirm? I'm just trying to get the 4.3 update installed but at every attempt it goes into Odin Mode and gets stuck.
Click to expand...
Click to collapse
You're said that you're on ME7 - what you need to do is to flash the "No wipe" ME7 ROM onto your phone. It's in the Development forum.
http://forum.xda-developers.com/showthread.php?t=2301259
You've got to update to MI1 before you can install the 4.3 update (MJ7).
ONLY flash files intended for whatever release you're running. You can't mix and match, can't go backwards, and can't skip updates.
Theres also an ml1 factory image in the dev section.
Hit thanks if I helped you out. Doing a little bit of reading goes a long way. Sent via tapatalk.
TheColdOne said:
I ended up getting it to work. I had to go here:
and get files to get the computer to recognize the device. Even afterwards, Keis had no idea what was going on, and Odin saw it and was able to install a stock firmware I downloaded earlier, saving the phone.
For now I will be satisfied with just root access and will wait for ROM capabilities.
Click to expand...
Click to collapse
Hi! Sorry to kind of "butt in" on your thread, but I'm somewhat of a noob and have the same exact problem as you. If you don't mind, can you explain what you downloaded from Intel and what you did afterwards that fixed your problem? I'd really appreciate it, since my phone's been dead to me for more than a week now....
nyankat said:
Hi! Sorry to kind of "butt in" on your thread, but I'm somewhat of a noob and have the same exact problem as you. If you don't mind, can you explain what you downloaded from Intel and what you did afterwards that fixed your problem? I'd really appreciate it, since my phone's been dead to me for more than a week now....
Click to expand...
Click to collapse
On that page I linked to, look for this:
Solution:
Download and run the IntelĀ® Chipset Software Installation Utility so Windows* properly recognizes the SMBus controller.
Get the proper driver download according to your OS, then install it. This should allow Odin to see the phone for you to install a clean copy of the stock ROM onto the phone.
If you want more details I am sorry to say I cannot provide them. When things involve me fixing my own technology, it is a lot of rapid-fire troubleshooting and I just go with what sticks without really memorizing what I did (so if I run into this issue again, I have to re-research).
TheColdOne said:
On that page I linked to, look for this:
Solution:
Download and run the IntelĀ® Chipset Software Installation Utility so Windows* properly recognizes the SMBus controller.
Get the proper driver download according to your OS, then install it. This should allow Odin to see the phone for you to install a clean copy of the stock ROM onto the phone.
If you want more details I am sorry to say I cannot provide them. When things involve me fixing my own technology, it is a lot of rapid-fire troubleshooting and I just go with what sticks without really memorizing what I did (so if I run into this issue again, I have to re-research).
Click to expand...
Click to collapse
Thanks! Finally Oden recognizes my phone
my amazing method
the same problem was with me 3-4 weeks ago...
follow the url-
dbloo dbloo dbloo dot autoroot dot chainfire dot eu
(i cant post the URL because the website is not allowing me.....understand and use the code)
1) choose your samsung model and download the recovery file
2) download and open odin on a dekstop
3) connect your device to the dekstop
4) press the volume down, home button and power button together till the screen changes
5) press the volume down button again
6) odin will show the message "attatched or connected"
7) click pda
8) attatch the file you downloaded
9) your device will be fixed and will be restarted
ur welcome
hai i am stuck at download mode with message as could not normal boot how to fix it

[Q] Bricked GT-P7510 not recognized by various PC's

Hey all.... Long time lurker and reader here. I usually find all my answers through previous posts but I'm a little stuck here and cannot find the appropriate guide to help me out.
I have a GT-P7510 which has always been rooted and has had a few ROM lifes, so I'm no stranger to CWM and download mode, Odin Etc... (But I'm certainly no expert by any means)
Last week I tried a flash and ended up bricked. (Soft brick) I tried several times to flash back to stock with the current as well as last known good firmware from SamFiles, but ODIN would fail partially through the flash. I got the message "Can't open the specified file. (Line: 1876)", so I checked here: http://forum.xda-developers.com/showthread.php?t=1370433 But that didn't help me.... And now, my tab is not recognized in any of the laptops or desktops I plug it into. (WinXP, WinVista, Win7 -- Kies drivers all fresh from Samsung)
I can get into Download mode. I can get into recovery, (I have done a wipe/re-format Factory reset in recovery a few times now) but nothing seems to help. I'd be willing to learn how to probe around with ADB, but haven't tried for lack of a driver being recognized. I have a few Linux boxes here at the house and haven't tried them. I wouldn't know where to start if the device was recognized by them.
Any suggestions on how to get the device recognized? Or, maybe what I can do from CWM (Sideload?). or even if I get an ADB connection from one of my linux boxes, would I be able to re-flash the firmware?
Thanks in advance.
first thing is to check your cable, then your pc drivers, if u can get in to cwm, try a new cable and mount the usb from there, put in a new rom, and flash it.
hope this helps, dude. Good luck.
If you foobarred the tab by a failed flash using Odin as you described logic would dictate that it has absolutely nothing too do with pc drivers suddenly not being good if they worked before, same for pc and cable.
You need to reinstall using Odin as you say you can get into download, using a .pit file, ticking repartition, and a stock firmware file. If that works you can go on to play another day....
If you're not sue about stuff you're using, good version of Odin (not all versions flash the 7510 properly) for 7510 and drivers are here http://forum.xda-developers.com/showthread.php?t=1518895
I'll put a .pit file up here when I get to a computer and get yourself a STOCK rom from samfirmware to flash thro Odin and you should be good to go
Sent from my GT-P7510 using XDA Premium HD app
stinky73 said:
If you foobarred the tab by a failed flash using Odin as you described logic would dictate that it has absolutely nothing too do with pc drivers suddenly not being good if they worked before, same for pc and cable.
You need to reinstall using Odin as you say you can get into download, using a .pit file, ticking repartition, and a stock firmware file. If that works you can go on to play another day....
If you're not sue about stuff you're using, good version of Odin (not all versions flash the 7510 properly) for 7510 and drivers are here http://forum.xda-developers.com/showthread.php?t=1518895
I'll put a .pit file up here when I get to a computer and get yourself a STOCK rom from samfirmware to flash thro Odin and you should be good to go
Sent from my GT-P7510 using XDA Premium HD app
Click to expand...
Click to collapse
That sounds great man.... THANKS! I do have the correct Odin, and I have a clean firmware from SamFiles. But I have tried looking for a pit for the 7510 and haven't had much luck. If you could post one, I'd be forever in your debt.
Here y'are
stinky73 said:
Here y'are
Click to expand...
Click to collapse
Thank you brother! I'll report back in a day or so.
Good luck!
sent from my still superb Google I/O 7510
stinky73 said:
Good luck!
Click to expand...
Click to collapse
Back to the drawing board I guess... I have a new cable on-order. However I was able to get the driver loaded by utilizing the dreaded "Plug - Unplug" routine several times until I just got lucky.
Odin can see it as COM5, and I used your pit (Again, TY!) I tried using the "P7510XABLPL_P7510UELPL" file I got from Samsung, but Odin is locked up at this point. (See screen cap)
I'll keep beating my head against this wall
:silly:
Odin 1.85 is just about the most random version of the prog when it comes to the 7510...
Try the one I have posted below (v1.3) it has never let me down (whereas 1.85 often has done to me what it is doing to you)
Worth a try
stinky73 said:
Odin 1.85 is just about the most random version of the prog when it comes to the 7510...
Try the one I have posted below (v1.3) it has never let me down (whereas 1.85 often has done to me what it is doing to you)
Worth a try
Click to expand...
Click to collapse
Yes. Sorry I forgot to mention that.
I saw your other post and did grab that 1.3 version. However, When I get the drivers loaded (When windows "sees" the tablet after plugging and unplugging numerous times) It will show up as COM3 or COM5 in any version of odin Except 1.3.
I tried various versions of Odin and when they all see the com port, 1.3 does not. Truly bizarre to me.... With 1.85 and or 1.7 I was successful in just loading the pit file, but if I try to load a PDA, it just freezes.
I installed Android SDK and started playing with ADB yesterday. I haven't had much success in addressing the Tablet. Also, I cannot get into recovery any more. It appears that the tablet is stuck in download mode, as if it's in a loop. ('the device states that it's downloading even after a reboot with no cable attached.)
My new cables will be here in a couple of days. Until then, I'm letting the battery die completely and will try again with the new cables.
P-tek said:
Yes. Sorry I forgot to mention that.
I saw your other post and did grab that 1.3 version. However, When I get the drivers loaded (When windows "sees" the tablet after plugging and unplugging numerous times) It will show up as COM3 or COM5 in any version of odin Except 1.3.
I tried various versions of Odin and when they all see the com port, 1.3 does not. Truly bizarre to me.... With 1.85 and or 1.7 I was successful in just loading the pit file, but if I try to load a PDA, it just freezes.
I installed Android SDK and started playing with ADB yesterday. I haven't had much success in addressing the Tablet. Also, I cannot get into recovery any more. It appears that the tablet is stuck in download mode, as if it's in a loop. ('the device states that it's downloading even after a reboot with no cable attached.)
My new cables will be here in a couple of days. Until then, I'm letting the battery die completely and will try again with the new cables.
Click to expand...
Click to collapse
That's an odd one for the download reboot.... As normally you should get choice of recovery or download as first step... Would tend to signal a failed download
I've often seen people say here "have you tried a different computer?" and scoffed a bit at that but maybe in your case...
However to be scientific you should only change one variable at a time so as to know where the result comes from, so start with the cable and we can see where you go from there
sent from my still superb Google I/O 7510 (xda hd)
Victorious
stinky73 said:
That's an odd one for the download reboot.... As normally you should get choice of recovery or download as first step... Would tend to signal a failed download
I've often seen people say here "have you tried a different computer?" and scoffed a bit at that but maybe in your case...
However to be scientific you should only change one variable at a time so as to know where the result comes from, so start with the cable and we can see where you go from there
sent from my still superb Google I/O 7510 (xda hd)
Click to expand...
Click to collapse
Thank you again for all your help!
My new cables arrived and appeared to be at the center of the issue. Once plugged in, the drivers properly loaded and I was successful with Odin. I used the pit you gave me for a re-partition, and the UELPL PDA from Samfiles.
It was initially stuck in a boot loop after the successful flash, but I was able to reboot to recovery, F/R, wipe and clean it up and now it's ALIVE! :victory:
Yeeee. Haaaaah!!!!
sent from my still superb Google I/O 7510 (xda hd)

Categories

Resources