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)
Related
Okay guys, never let me down before, lets see if you can keep a perfect score
This is not my first time rooting, i've rooted at least 3 phones thus far, and I am trying to root my Samsung Fascinate. I've tried z4root, Superoneclick and adb. None of them took. I believe it may be something with my drivers, but before I get into specifics, let me give you my information:
~~~~PHONE~~~~
Hardware version: I500.04
Model SCH-I500
Firmware: 2.2.2
Kernel version: 2.6.32.9
Build Number: SCH-I500.ED05
~~~~COMPUTER~~~~
Microsoft Windows XP Media Center Edition Version 2002 Service Pack 3.
Ok so now that's out there, what am I doing wrong? when I tried z4root 1.3.0, it got the point where it said "acquiring root shell, then the phone vibrated 3 times and the app closed. Super one click, the prompt got stuck on "waiting for phone" ADB, the device won't even show up in the list of devices. I can't seem to find the right drivers anywhere.
It may be important to note that I am using my data cable from my optimus v, and when I plug it in, the micro-usb dongle doesn't go all the way into the port on the fascinate. However, the fascinate gives me the notification that usb mode can be activate and that debugging is on, etc.
I made sure that mock locations, and usb debugging were both on.
Any help?
Follow these steps in link:
http://www.galaxyforums.net/forum/fascinate-rs-guides/1967-how-root-froyo-gingerbread-your-fascinate.html
Ive always used ADB and pushed over the files and such.
However are you going to flash another rom? If so just Odin recovery, flash the rom and be done with it.
I have to have root for that right? My drivers aren't working, is there a way to flash it with out a computer
OhioYJ said:
Ive always used ADB and pushed over the files and such.
However are you going to flash another rom? If so just Odin recovery, flash the rom and be done with it.
Click to expand...
Click to collapse
Sent from my LG Optimus V running Sense 3.0
You need a REAL cable... If computer doesn't see the phone via the drivers, nothing is going to work.
OhioYJ said:
However are you going to flash another rom? If so just Odin recovery, flash the rom and be done with it.
Click to expand...
Click to collapse
agreed! If you want a different rom, alot of the steps in that link I posted a not needed. Just odin the proper recovery for the rom you intend on flashing. boot into recovery and wipe data,cache,dalvik, then install rom.zip from sd card. reboot and the phone should be rooted.
droidstyle said:
Follow these steps in link:
http://www.galaxyforums.net/forum/fascinate-rs-guides/1967-how-root-froyo-gingerbread-your-fascinate.html
Click to expand...
Click to collapse
Downloaded everything in the link, installed drivers, I'm on my friends laptop now, still xp. I got to the step where I have to find CWM3 Voodoo in Odin, and the instructions say that one of the boxes should have turned yellow, but it didn't. I went on ahead and clicked the pda button, but it just said success 0/failure 0. What do I do? Do I have to have vista?
That means odin is not recognizing the phone. Im not sure if odin works with xp or vista... I only use 7 these days. Actually if my memory serves right, odin dont work with xp, don't quote me tho. You could try heimdall but I have no experience with it.
Still can't squire root.I've factory rest 3 times now and still nothing. Can no one help?
Sent from my LG Optimus V running Sense 3.0
If u can't get odin or heimdall to work, you won't be able to root. Do you not have windows 7
droidstyle said:
If u can't get odin or heimdall to work, you won't be able to root. Do you not have windows 7
Click to expand...
Click to collapse
as stated in the op, I explicitly said I am using windows xp, media center 2002, service pack 3 to be specific. So your telling me I'm S.O.L.?
first, get a real cable
then, go to official samsung website and install the correct fascinate drivers
download and open odin v3 1.30 (I have xp and it works)
plug in phone in download mode, wait for odin box to turn yellow
pick file in pda
and press start
then just go into cwm via 3 fingers and flash rom
dragon1357 said:
first, get a real cable
then, go to official samsung website and install the correct fascinate drivers
download and open odin v3 1.30 (I have xp and it works)
plug in phone in download mode, wait for odin box to turn yellow
pick file in pda
and press start
then just go into cwm via 3 fingers and flash rom
Click to expand...
Click to collapse
I have my cable from my samsung intercept, would that work? By the way thanks for being so informative. Could you pm the drivers you used, if you have them?
Sent from my LG Optimus V running Sense 3.0
I'm not saying that you shouldn't be doing this but I think you need to slow down and read some more before trying. While this phone is pretty dang hard to brick without physical damage, lacking basic knowledge can put you down got a while if something goes wrong.
A good place to start is the qa stickies. Again I'm not saying don't, just maybe give it another day or two. Really sucks rushing in soft bricking and having to learn after with no phone in the mean time.
XDA Prem app Running UKB w PBJ
MattRussNC said:
I'm not saying that you shouldn't be doing this but I think you need to slow down and read some more before trying. While this phone is pretty dang hard to brick without physical damage, lacking basic knowledge can put you down got a while if something goes wrong.
A good place to start is the qa stickies. Again I'm not saying don't, just maybe give it another day or two. Really sucks rushing in soft bricking and having to learn after with no phone in the mean time.
XDA Prem app Running UKB w PBJ
Click to expand...
Click to collapse
Not trying too be an ass or anything but 1.) This is my 5th or 6th time rooting. I have more than basic knowledge. 2.) This is a spare phone I picked up dirt cheap for development. 3.) I checked every place possible trying to find out why my drivers weren't working including q&a.
That aside, I'm trying it on my friends laptop with vista. Wish me luck.
Sent from my SCH-I500 using XDA App
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.
I am using the UCKH7 one click w/root tool.
I start download mode by holding volume up and down while plugging in USB. I click the start button but the program hangs at 'factoryfs.img'
Please help. Thanks.
AT&T galaxy s2
Deenybird said:
I am using the UCKH7 one click w/root tool.
I start download mode by holding volume up and down while plugging in USB. I click the start button but the program hangs at 'factoryfs.img'
Please help. Thanks.
AT&T galaxy s2
Click to expand...
Click to collapse
I use heimdall personally. Never had any problems with it. Do you have all the sgs2 drivers installed?
Also check md5 sums to make sure your download is ok.
Sent from my SGH-I777
I'll try heimdall. Drivers should be fine as kies is installed. Rom should be good as I've tried 2 different download sources
Make sure you install the libusb drivers for heimdall before flashing. The instructions are in the heimdall readme. Good luck
Sent from my SGH-I777
Just wanted to post that my problem is solved.
Summary: My AT&T Galaxy SII showed an error on boot (software upgrade failed. connect to kies...). Kies wouldn't even recognize the device so that route was a no go. So as everyone's recommended method of last resort, I decided to flash the device back to stock via odin. I entered download mode (volume up + volume down and plug in usb) and Odin would recognize the device, I would load the stock rom in the PDA slot and hit start and it would begin normally, but it would always fail after a few seconds on 'NAND write start', or 'factoryfs.img'. So I got a 1 click download solution using odin for reverting my phone back to stock. Same thing, it would recognize the phone, but stall out and fail. I also tried flashing clockworkmod via odin but and same problem. People recommended I try heimdall. It would recognize my device, and then fail after 'kernel 100%'.
I tried both programs on 3 different computers, and must have tried 12 different USB slots amongst all of them. I'm fairly handy with this stuff and I worked for hours on it.
xtra info: I had successfully used odin on my computer to flash a kernel just a week ago so I know my stock usb cable was working etc...
Resolution: So I hung my head and drove to the ATT store. After pressing a few buttons on the device and not getting anywhere they sent me to a nearby Device Support Center. I told the girl at the counter that my phone booted to this error screen and that connecting it to Kies did nothing. She asked if it was ok that in the case that she couldn't fix it she would offer me a replacement. I said that was fine and after 10 minutes in the back room she came out with a replacement (free of charge).
Well that was the good news. For the bad news, unfortunately I still don't know how to fix the problem I had, and don't really know how to avoid it in the future. I thought phone's could only get truly bricked if you messed with PIT files and such. There didn't seem to be anything more I could do than flash with odin or heimdall as those were already last resorts. I know I had the right files, the right drivers, and working usb. No matter how crazy I got with my iphone, a full restore was only a click away by plugging in to iTunes. Somehow I messed up my phone so bad that even the device support center couldn't fix it....? Shouldn't have had to be like that.
Thank yous: Thanks to ATT for having a walk-in store and for so easily offering up a replacement. Thanks to the many people on the web who offered remedies.
tl;dr - phone broke, att replaced, still a mystery
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???
Ok
Trying to Unroot.
But today I have this giantic issue.
My recovery mode just doesnt appear anything like before.
I have tried unrooting using a Root_Remover.zip file. But I can't find at all the "install zip" menu in recovery mode I had when I had to root it first ! Now it just wont appear at all. I only have :
Reboot system Now
Apply update from external Storage
Wipe Data/Factory REset
Wipe Cache Partition
and nothing more. I even tried the second menu (apply update from ext.stor.) but im not using any external storage.
I thought "all right, Ill get through it with ODIN >>> WRONG !!!!!! No download mode ...
So right now I'm completely screwed since theres no way I can perform an unroot under such conditions.
Please someone help me out with this, sorry for being a bit too straightfoward but after 72h spent on that @#%? I find it pretty unrelevant that this ****ing menu wont show the hell up. Even though I guess Im just doing something wrong, I need help.
EDIT : All right. So I figured out most tutorials are written by incompetent people whom mostly release pseudo tutorials that are just here to show the world that they can perform this or that, but in fact, can't take a single second to make a point where you don't get access to DOWNLOAD MODE the same way on a Tab2 than with a S2 -_-. We don't enter DOWNLOAD mode the same way ... geez ... so I figured out that using the Up volume button instead of the down volume button would eventually get me there. Which it did. Come on ... how is it possible that after 15 tutorials, not ONE did mention that ?
Also, ODIN doesn't want to do @#%? right now. I browsed the right firmware, plugged my tab to my laptop ... hit START and it ends in 5 seconds after "all thread completed (0 succeed/0 failed)
I've tried multiple stock firmwares (all the same but form different locations or mirrors) and ... nothing. So ...
First, please clarify these couple of questions. What device do you have? What version of recovery do you have? And one more out of curiosity. Where did you get that root remover zip?
Sent from my GT-P7500 using Tapatalk 4
Most of the tutorials are written for the GT-P75xx. Being that it's also the device for the section you posted this rant in, I can see why the tutorials were not what you needed. Just my two cents but condemning the authors of the tutorials will most likely get you very little help. Not to mention this section isn't for your device.
Sent from my GT-P7510 using XDA Premium HD app
Benzoman said:
Most of the tutorials are written for the GT-P75xx. Being that it's also the device for the section you posted this rant in, I can see why the tutorials were not what you needed. Just my two cents but condemning the authors of the tutorials will most likely get you very little help. Not to mention this section isn't for your device.
Sent from my GT-P7510 using XDA Premium HD app
Click to expand...
Click to collapse
Don't know what happened to my last reply but anyway :
All the threads I read were for Tab2 p51xx or SII.
As explained in first reply (which disappeared), I had and have my damn good reason to condemn people who spam the net with their useless blogs. Won't waste time explaining again a reason which won't certainly arent interested in. But it was costy in term of $.
That said I then realized XDA still exists so I launched a quick google search and fell on this subboard. Reading "Samsung Tab 10.1", unfortunatly didn't mean to me it is a seperated sub forum from the Samsung tab2 10.1. My bad ... do I have to get this thread transfered to the right place or admins will find it useless ?
_____________
My ROM is none. I unrooted but didn't install any ROM. After that I simply figured out I don't need one. But today I need to upgrade to anything above 4.0.4 after the very bad experience I had late friday eve which is quite costy.
I have one more minor trouble I didn't speak of in my first post :
I bought my tablet in September 2012 in the Netherlands GT P5110, ICS 4.0.4. So after checking on the XDA page where all of the stock firmwares are listed, I realized there is no "perfect" match. The only firmware for the Netherlands and for P5110 is from April 2012 and ICS 4.0.3, not 4.0.4 ; yet it is the one I downloaded. Should I get another one ?
About the Root remover, I uploaded to my tab one I downloaded from a website which I can't recall or find on google right now because I downloaded two from two different websites and only remember this one : www techbloggerzone com/2012/09/how-to-unroot-galaxy-tab-2-101-gt html [dots for WWW | COM and HTML were removed since I'm not allowed to post external links yet]
I think there's nothing else missing, but tell me if there is.
IMPORTANT EDIT : I just realized the factory usb plug I have for the Samsung must be damaged. It charges on sector, but isn't identified properly on my laptop and thus won't let me connect it by wire. Didn't figure this out earlier as I did all transfers by Kies wifi. Damn ... but it only explains why Odin can't upload anything to my tab, not why I can't use find the zip install option in Recovery mode for the root_remover.zip
As already stated you're in the wrong place but we all try to help each other here...but no more rants or you might find a stoney silence will be your only reply....
Problem with Odin is more likely laptop drivers and/or windows version and not your cable...
Samfirmware has many 4.0.4 roms for your "area", they have a 4.1.2 version for Netherlands and 4.0.4 for Belgium, Luxembourg etc. As long as you find an XX version it will have Dutch language option.
The recovery you described when you eventually got into it sounded like stock recovery so you wouldn't be able to choose and flash zip from there
Calm down, take a deep breath, get your laptop and drivers sorted first or you'll not get anywhere... Did you have a yellow indication with com port number in the Odin window, if not it is surely drivers. Does windows in any way recognise the tab when connected? (warning tone, does device manager show anything?)
sent from my still superb Google I/O 7510 (xda hd)
stinky73 said:
As already stated you're in the wrong place but we all try to help each other here...but no more rants or you might find a stoney silence will be your only reply....
Problem with Odin is more likely laptop drivers and/or windows version and not your cable...
Samfirmware has many 4.0.4 roms for your "area", they have a 4.1.2 version for Netherlands and 4.0.4 for Belgium, Luxembourg etc. As long as you find an XX version it will have Dutch language option.
The recovery you described when you eventually got into it sounded like stock recovery so you wouldn't be able to choose and flash zip from there
Calm down, take a deep breath, get your laptop and drivers sorted first or you'll not get anywhere... Did you have a yellow indication with com port number in the Odin window, if not it is surely drivers. Does windows in any way recognise the tab when connected? (warning tone, does device manager show anything?)
sent from my still superb Google I/O 7510 (xda hd)
Click to expand...
Click to collapse
I thought I had all my drivers updated (for the samsung tab, installed like two or three weeks ago), so if it's about drivers, then I don't get it . I checked that in the first place. The cable sometimes fails the connection to my laptop, but today it just won't work. :/. Windows recognizes the device as an external object which can't properly install and such connect (yellow pop up message in right corner, over the task bar). I do not exactly undersatnd what you mean by a yellow indication with "com port" number in the Odin window, but I don't think I had that ... in fact I'm pretty sure about it.
If it's just about drivers, where can I go to find the latest ?
Try looking in Samsung site for drivers here http://www.samsung.com/us/support/
What version of odin are you using? Would recommend 1.3 for the tab 2.
The indication of com port in odin is as in attached image, if you haven't got that then the computer is not recognising your tab, either because of drivers, or cable, but as we've said, you should start with the drivers, probably by downloading the latest from Samsung, deleting all drivers you have at the moment then re-installing.
If the tab is not recognized by the computer then programs like odin cannot do anything as they use the computers' usb bus...
stinky73 said:
Try looking in Samsung site for drivers here
What version of odin are you using? Would recommend 1.3 for the tab 2.
The indication of com port in odin is as in attached image, if you haven't got that then the computer is not recognising your tab, either because of drivers, or cable, but as we've said, you should start with the drivers, probably by downloading the latest from Samsung, deleting all drivers you have at the moment then re-installing.
If the tab is not recognized by the computer then programs like odin cannot do anything as they use the computers' usb bus...
Click to expand...
Click to collapse
Thank you very much !! I was using Odin 1.85 and Odin 3.7 (used 1.85 for rooting), I'll try a downgraded version.
Keep you in touch if problems are resolved or not after that. Thank you again.