i posted about this before, but they were kind of muttled. So ill state my problem as cleanly as i can and see if i can get some help on what to do.
I tried out TW's Gingerbread Tech demo. I tried to ODIN back, but my computer doesnt recognize my phone when its in download mode. I tried Nexus s drivers, and vibant drivers. The nexus s drivers install fine when the phone is NOT in download mode, but my comp doesnt recognize it when in download mode. My computer reads my phone in DL mode as "Gadget Serial". I also tried plugging my phone into my comp while in DL mode and installing the same drivers, but it doesnt work. Honestly i am not really a "noob" at this, and i have tried everything i can think of, so this is why i am posting this.
Try using a Windows XP computer or at least 32 bit Windows 7
anthonys2r said:
Try using a Windows XP computer or at least 32 bit Windows 7
Click to expand...
Click to collapse
This might work........ worth a try, but read up on doing this through ADB...... that will probably expose what is corrupted in the software and it may be the SBL........ not sure but either way you need to be able to see line by line what is happening
I can't remember but I think it was untermensch, Whitehawxx or Jellette one of those I thought had some post on ADB and how to help in reloading a rom......
I am really not sure if i understand the total problem ..........
hope that helps
Wasn't the TECH Demo made to run in memory and all you had to do was flash back to the kernel you were using previously and your phone would be back to the way it was.... lemme look at that again..
Yeah thats what you do...even a list of 2.2 kernels to flash
jmcghee1973 said:
Wasn't the TECH Demo made to run in memory and all you had to do was flash back to the kernel you were using previously and your phone would be back to the way it was.... lemme look at that again..
Yeah thats what you do...even a list of 2.2 kernels to flash
Click to expand...
Click to collapse
oka1 said:
This might work........ worth a try, but read up on doing this through ADB...... that will probably expose what is corrupted in the software and it may be the SBL........ not sure but either way you need to be able to see line by line what is happening
I can't remember but I think it was untermensch, Whitehawxx or Jellette one of those I thought had some post on ADB and how to help in reloading a rom......
I am really not sure if i understand the total problem ..........
hope that helps
Click to expand...
Click to collapse
The problem is odin doesnt recognize my phone in download mode. So thats why just flashing a kernel back wont work. And CWR doesnt work if thats what you were talking about. Ill look up the ADB post though, thank you
f**k this is so aggravating, my phone is basically f**ked....
Might sound wierd but my phone used to do the same thing. Which version of odin r u using. I have 2 versions of it the v1 and whatever the new one is, but anyway one recognizes my phone the other doesnt. Try using a diggerent version on odin. Worth a try hope it helps
Currently running ______________! (<----Insert Rom name here)
have you tried Heimdall ? It's like Odin
Had the Same problem
What you need to do is go over to the Nexus S forums and download the drivers for that and install them on your computer. Then once they are installed ODIN will then recognize your phone. I know that the OP for the Tech Demo state that all your info is still on the phone because it dual boots but to get back to the ROM you had before you are going to need those drivers then in ODIN just download a kernel and place it in the PDA section. This will allow the phone to revert back
vibrant2010 said:
What you need to do is go over to the Nexus S forums and download the drivers for that and install them on your computer. Then once they are installed ODIN will then recognize your phone. I know that the OP for the Tech Demo state that all your info is still on the phone because it dual boots but to get back to the ROM you had before you are going to need those drivers then in ODIN just download a kernel and place it in the PDA section. This will allow the phone to revert back
Click to expand...
Click to collapse
ive done all this before, problem is my computer doesnt recognize my phone when in download mode. I installed the drivers and my comp recognizes my phone when its on, but NOT when its in download mode.
oka1 said:
have you tried Heimdall ? It's like Odin
Click to expand...
Click to collapse
+1
odin wouldn't recognize my phone, but heimdall worked great.
Related
I flashed back to Stock Sprint from the RUU and then let the phone update to the MR update. I rooted and then did the pushed the recovery-RA-heroc-v1.2.3.img to the SD card and flashed it (at least I think so, it happened really fast). When I did "reboot recovery" it just powered down the phone and no reboot. In fact, I had to pull the battery to get it to boot normally. If I try to boot to recovery by holding the home key I just get stuck at the HTC splash screen.
Any help is appreciated.
I went through this SAME THING for 3 days when I first rooted my hero and it was driving me nuts! You may have a corrupt recovery img or just a bad root. I would download the recovery img again, and flash the Sprint RUU AGAIN and then root again. Basically start from scratch again . That is what worked for me. Every time I tried rebooting and getting to that screen where u can do a nandroid backup and flash from sd I could not for the life of me get to that screen, It would just power off and reboot and stay on the HTC screen. So try starting ALL OVER again I bet that it will work.
Thanks for the advice. I'm going to redownload everything and reflash with the RUU, reroot, and try the recovery image stuff again.
It's been a frustrating day.
I feel your pain man, I went through it for 3 days before someone told me to flash the Stock Sprint RUU. And at the time I didnt even know there was a stock sprint ruu,lol.
OK, redid RUU, rerooted, and reflashed recovery and now it's working.
Now I can go to bed!
BTW, thanks aaron130 for your moral support.
No problem. Glad you got it working!
i'm having a bit of trouble with this as well i cant flash back to the stock sprint firmware with the RUU exe file. it times out on waiting for bootloader and the phone will never reset. has anyone encountered this? i downloaded the RUU file three times and and tried two different computers. i'm just trying to get back to the stock ROM. someone help please?
Yes, Spunkzz. Download and install HTC Sync.
Spunkzz said:
i'm having a bit of trouble with this as well i cant flash back to the stock sprint firmware with the RUU exe file. it times out on waiting for bootloader and the phone will never reset. has anyone encountered this? i downloaded the RUU file three times and and tried two different computers. i'm just trying to get back to the stock ROM. someone help please?
Click to expand...
Click to collapse
Try doing it from fastboot. (Off the top of my head) With the phone powered off: hold volume down and then hit the power button. It should say if you want fastboot to hit volume up... press volume up. See if it will flash RUU that way. If not then check your device manager and see if it shows you are missing a driver for your phone.
Spunkzz said:
i'm having a bit of trouble with this as well i cant flash back to the stock sprint firmware with the RUU exe file. it times out on waiting for bootloader and the phone will never reset. has anyone encountered this? i downloaded the RUU file three times and and tried two different computers. i'm just trying to get back to the stock ROM. someone help please?
Click to expand...
Click to collapse
I saw a thread about this somewhere. I think it was the Sprint Community forums. Are you on Windows 7? If you are, you'll have to manually download and install the Vista drivers for the phone.
I'll find you a link to them if this is your problem.
arashed31 said:
I saw a thread about this somewhere. I think it was the Sprint Community forums. Are you on Windows 7? If you are, you'll have to manually download and install the Vista drivers for the phone.
I'll find you a link to them if this is your problem.
Click to expand...
Click to collapse
I'm using Win7 and all I had to do was install HTC Sync.
jonnythan said:
I'm using Win7 and all I had to do was install HTC Sync.
Click to expand...
Click to collapse
Really? I have Win7 x64 and it wouldn't install any drivers. The program installed but it would never recognize my phone and neither did the RUU. I had to download the Vista x64 drivers from somewhere and then the HTC Sync program and the RUU would work.
http://www.mydigitallife.info/2009/08/24/workaround-for-htc-hero-sync-problem-in-windows-7/
Here's what I did:
I got the 2.0.8 version off the site.
Installed in normally and let it error with a long dialoge that said something about not installing drivers.
Downloaded the drivers from the site and put them in the HTC Driver folder
Used device manager to manually install the drivers for "Android Device"
And it worked!!
as an update. i figured it out. i was using Fresh Rom 0.5d and for some reason that wasnt letting me run RUU exe file to get it back to the stock rom. i flashed modacos rom and then used the RUU and it worked fine. i'm now back to the stock rom. for some reason after a day something keeps my phone awake. i've been tryign to figure it out but cant seem to narrow it down.
arashed31 said:
Really? I have Win7 x64 and it wouldn't install any drivers. The program installed but it would never recognize my phone and neither did the RUU. I had to download the Vista x64 drivers from somewhere and then the HTC Sync program and the RUU would work.
http://www.mydigitallife.info/2009/08/24/workaround-for-htc-hero-sync-problem-in-windows-7/
Here's what I did:
I got the 2.0.8 version off the site.
Installed in normally and let it error with a long dialoge that said something about not installing drivers.
Downloaded the drivers from the site and put them in the HTC Driver folder
Used device manager to manually install the drivers for "Android Device"
And it worked!!
Click to expand...
Click to collapse
Ah, Win7 x64 and x32 are going to be different beasts when it comes to drivers. Great info for those running x64 though, thanks.
Sooooo, I may have bricked it. Any help would be appreciated.
So I got my new sd card and figured i would go ahead and partition for future use, if needed for apps2sd, or any other reason. Instead of going through adb I thought I would save myself some time and just do it from Rom Manager.
Now most of you probably already know what happened. Being as the storage on our devices is called "sdcard" I am humbly assuming that it thought I wanted to partition THAT.
Phone wont boot. Tried factory reset, but no surprise there, it did not work. Can get into download mode and reset menu.
Do I need to flash the factory pda, phone and boot files? Will that work? Where can I get it (preferably without the bloatware and root?????)? Do I need a specific version of odin or will the same one i used for my behold 2 be ok?
Sorry if any of this is stupid, I read these forums cause I want to learn as much as possible about my phone, but have limited experience messing with it. Might try Eugene's froyo just for kicks before I go back to factory. But is this the correct route, or should i just get a replacement?
**** update to issue in post 5
Here look at this: http://forum.xda-developers.com/showthread.php?t=743875
ElahC said:
Here look at this: http://forum.xda-developers.com/showthread.php?t=743875
Click to expand...
Click to collapse
Thanks, makes sense. Download mode does not appear to be working now though, think i got into on accident trying to get to recovery mode.
Is it vol down plus power?
How do you know if you are in download mode? Once when i was in what i thought was download mode it said please wait downloading or something, big yellow characters, and when i hit menu in recovery mode it sent me to a screen with a little mailbox and an arrow coming out of it pointing to a little green android.
Which is dl mode?
ok, i got it into dl mode and when i flashed back to stock it still had a blank screen, like the post above says. But then when I tried to flash Eugene's froyo rom it froze on cach.rfs in odin and the screen on the phone went black. So after about an hour i pulled the plug and tried again, same thing, now when i go to flash back to stock, like previously, it does the same thing, freezing when odin gets to cache.rfs
Also the cell phone goes to a screen that has a cell phone and a computer and the link is broken by an exclamation point. cannot get into recovery mode from there but can get back to download mode.
Any help with all of this?
People have been saying that it could be a problem with your Operating System. Mines is Windows 7 64 - bit and when I use Odin it worked but I have experienced what you have; Odin getting stuck on cache.rfs. You can try on a Windows XP based computer to see if you have any success in that. Also you can possibly be using the wrong Odin. Try the Odin from either : http://forum.xda-developers.com/showthread.php?t=734475 , or : http://forum.xda-developers.com/showthread.php?t=740558 . When I was using Odin it would get stuck on cache.rfs but I tried a different Odin and it worked fine again. Really hope this helps and sorry for the late response.
cache.fs problem in odin
ElahC said:
People have been saying that it could be a problem with your Operating System. Mines is Windows 7 64 - bit and when I use Odin it worked but I have experienced what you have; Odin getting stuck on cache.rfs. You can try on a Windows XP based computer to see if you have any success in that. Also you can possibly be using the wrong Odin. Try the Odin from either : http://forum.xda-developers.com/showthread.php?t=734475 , or : http://forum.xda-developers.com/showthread.php?t=740558 . When I was using Odin it would get stuck on cache.rfs but I tried a different Odin and it worked fine again. Really hope this helps and sorry for the late response.
Click to expand...
Click to collapse
I FOUND A SOLUTION TO THE CACHE.RFS PROBLEM!!
http://www.fractionalphones.com/?p=121
So, yes before anyone tells me to read, Ive read the instructions on how to use Odin again and again. I downloaded Odin and the 64 bit usb drivers, i have a laptop running on windows 7. I put my phone in downloading mode and connected it to my laptop, but nothing seems to happen in Odin, no COM number, just nothing, I uninstalled the drivers and Odin and installed them once again, and i tried a different port...still nothing. I'm running on the leaked android 2.2.1, the phone is not rooted, just flashed with the update.
Any suggestions??....
Try a different USB cable/port... The one that is included with the Epic is a peice of crap as far as I am concerned.
Another idea... Try right clicking on Odin and running as administrator (not sure if this will effect anything, just throwing ideas out there).
Koadic said:
Try a different USB cable/port... The one that is included with the Epic is a peice of crap as far as I am concerned.
Click to expand...
Click to collapse
Yeah I bought another cable i know the one that comes with the phone is useless.
Will give a shot to the administrator idea and see what happens o.0,
thanks
The other thing is that you must put your phone in download mode, open ODIN and THEN plug in your phone. Aside from that, the USB thing is your best bet.
Well...i tried running Odin as administrator, launched it before plugging the USB into the phone and the laptop...and once again...nothing...I'm using a Gigaware USB cable, this is just driving me insane >.>
My last bit of advice would be to check in IRC at #samsung-epic the people there are very versed in using ODIN and are very helpful
monnie27 said:
Well...i tried running Odin as administrator, launched it before plugging the USB into the phone and the laptop...and once again...nothing...I'm using a Gigaware USB cable, this is just driving me insane >.>
Click to expand...
Click to collapse
I've had this issue before myself. I have two Windows 7 machines, both 64 bit. One would recognize my phone in download mode, and the other would not. I installed the correct drivers on both machines.
Make sure you are connected to one of the USB ports on the rear of the machine. Some people have had issues using the front USB ports.
ok thanks, I managed to get it to work somehow, i repeated the process od uninstalling and installing the drivers, Odin and somehow it worked this time. However i had Kies installed on the laptop, so i decided to uninstall it just for the heck of it ....and well after that, Odin recognized the phone o.0.
But thanks to all of you for the support ^_^
i would love to know the source of the x64 driver...as i found it to be a load of horsecrap
the driver found on the samsung website installs on both x86 and x64 machines in my experience
i was running windows server 2008 x64 at the time and only got the phone working with the driver directly from the samsung website
peoples long winded history of drivers and windows makes for a bad situation...at least be willing to try THE MANUFACTURERS option first
i bought my phone used...but it did come in the original box...
i just wasn't sure enough, then, to say that it is BS for a company like samsung not to distribute some kind of media/drivers with, or preloaded on, the device.
http://www.samsung.com/us/support/downloads/SPH-D700ZKASPR
well..i got the drivers from this page:
http://forum.xda-developers.com/showthread.php?t=798067
and used BitZipper to extract them, it worked this time.
good news
enjoy dk28
it saved me from believing android was a suckers solution to windows mobile
my phone instantly locks gps now and the easy access to enabling 3g via the power button menu was nice
i am a believer...adb is my new god...reborn in code...blahblah...
actually i'm just glad something like a cellphone can simply work simply as it should
finally after billions of ages of fail
Well im actually having some problems with the gps navigation and lock. The location is not accurate, it was extremely accurate when i was running on 2.1 and i had no probs with neither of them. I saw a thread related to this issue before and ill see what can be done..
Sent from my SPH-D700 using XDA App
the only method that worked for me:
odin back to dI18 (.md5 extention removed/renamed to .tar extension)
get gps lock
odin dk28 modem (modem only) with victory_8G_100528.pit
gps lock again
odin dk28 (.md5 extention removed/renamed to .tar extension)
i actually didn't even try to get a gps lock after flashing the dk28 modem...
the key here seems to be performing the modem flash separately/first as there are multiple bootloaders working
I flashed my Nexus S with CM7 RC 4. Accidentally my original nandroid backup got deleted. I want to flash my device with the factory android 2.3.3 image. Please let me know the link to download the Android 2.3.3 for SNS 9023 GRI54.
You find it on:
http://forum.xda-developers.com/showthread.php?t=973534
I have already downloaded the rom files and the odin but the odin don't recognise my NS.
Can you tell me how to do a fastboot flash ?
If you want odin to recognize your nexus you have to install the samsung usb drivers .. You can find them here: http://forum.xda-developers.com/showthread.php?t=728929
I have already installed the google drivers but the phone recovery is the clockwork image. I am not able to put the phone to the download mode. I have downloaded the GRI54 image from samfirmware.com. Now I am not able to use it. Is there any other fully cooked image to flash the Nexus S.
I do not have a fastboot image for you ..btw the google drivers are not the same as the samsung drivers ..for odin you will need the samsung ones ...
To go into downloadmode :
turn on you phone, plug your phone into a sb port ( as if you wanted to put something on the phone) then while your phone is still connected to your pc , switch you phone off and keep holding vol up + vol down ..you will see that if you keep holding them phone will go into download mode after you phone is switched off
jaivinder said:
I have already installed the google drivers but the phone recovery is the clockwork image. I am not able to put the phone to the download mode. I have downloaded the GRI54 image from samfirmware.com. Now I am not able to use it. Is there any other fully cooked image to flash the Nexus S.
Click to expand...
Click to collapse
You installed the samsung drivers, make sure that your phone is power on,disable the usb debugging, ceheck that microsoft.net framework is installed on your pc. When you connect your phone (on your device manager) you must have "android phone" and below that "nexus s" with out any question symbols.If so then select to update your driver and give the path you installed the samsung drivers (eg c:\program files\samsung ....).
Power off you phone, open Odin and follow the pdf file from samfirmware to load the files (bootloader,pda,modem,csc). Hold your phone from the middle of volume buttons(between vol up and vol down) and immediately connect your phone to your pc with the usb cable .you are going to see the yellow triangle with the android.
Try it
Thanks afilopou, I've managed to enter download mode.
However I've never used Odin before so I'm not sure how to use it.
When I use 'PDA_SOJU_GRI54_TMO_EUR_MR1_SIGNED.tar.md5' for PDA, I get an error and the process stops.
If I start the process without selecting PDA, everything goes smoothly but when I reboot nothing's changed of course...
BTW, my i9023 is from Vodafone Australia (I hope that's got nothing to do with the error). Currently running CM RC4.
Please help.
hamajiro said:
Thanks afilopou, I've managed to enter download mode.
However I've never used Odin before so I'm not sure how to use it.
When I use 'PDA_SOJU_GRI54_TMO_EUR_MR1_SIGNED.tar.md5' for PDA, I get an error and the process stops.
If I start the process without selecting PDA, everything goes smoothly but when I reboot nothing's changed of course...
BTW, my i9023 is from Vodafone Australia (I hope that's got nothing to do with the error). Currently running CM RC4.
Please help.
Click to expand...
Click to collapse
What kind of error?on Odin or on your phone?
afilopou said:
What kind of error?on Odin or on your phone?
Click to expand...
Click to collapse
On Odin. The error message is in Korean so I don't know what it says, but it says something about the PDA tar. Please see the attached image.
Thanks
If I do it without PDA, I don't get an error...
hamajiro said:
If I do it without PDA, I don't get an error...
Click to expand...
Click to collapse
I see you are using a virtual machine and the host is mac .correct?do you have any pc with windows (not on a virtual machine)?Also please check that you have microsoft.net framework installed
Also i did an md5 check sum for the file from samfirmware and the result is 0557b037f56195497718e1dc575b20c9
Can you pls check the I9023_EUR_GRI54_XXKB3?
And the md5 check sum just for the PDA_SOJU_GRI54_TMO_EUR_MR1_SIGNED.tar.md5 is b594e50fd160428826a66f58a15ad522
afilopou said:
I see you are using a virtual machine and the host is mac .correct?do you have any pc with windows (not on a virtual machine)?Also please check that you have microsoft.net framework installed
Also i did an md5 check sum for the file from samfirmware and the result is 0557b037f56195497718e1dc575b20c9
Can you pls check the I9023_EUR_GRI54_XXKB3?
And the md5 check sum just for the PDA_SOJU_GRI54_TMO_EUR_MR1_SIGNED.tar.md5 is b594e50fd160428826a66f58a15ad522
Click to expand...
Click to collapse
Thank you so much for your help.
I don't have a windows PC, but I'll install Windows 7 to my MBP using bootcamp and see how that goes.
I'll check the md5 check sum as well.
Sent from my Nexus S using XDA Premium App
Forgot to mention. I tried Odin using Win7 (64 bit) on VMware Fusion, and I no longer got the error for PDA. Everything seemed to work but now Windows can't recognise the NS when I connect with USB! I tried to install range of Samsung USB drivers but installation failed.
Hopefully Win7 on bootcamp will work...
Sent from my Nexus S using XDA Premium App
hamajiro said:
Forgot to mention. I tried Odin using Win7 (64 bit) on VMware Fusion, and I no longer got the error for PDA. Everything seemed to work but now Windows can't recognise the NS when I connect with USB! I tried to install range of Samsung USB drivers but installation failed.
Hopefully Win7 on bootcamp will work...
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
Looks like that the virtual machine (vm fusion) on macosx generates problems.As far as i remember only parallels worked ok.I have imac as well but i have bootcamp win7 in order to avoid all these problems. Hope to help
Sent from my Desire HD using Tapatalk
Odin on Win7 Bootcamp worked! Even though I got an error when I was installing the Samsung USB Drivers, Windows started recognising the NS after that.
After using Odin, the only change I can tell from the bootloader is that the 'CARRIER INFO' has changed to 'EUR' from 'XSE'. The bootloader version and baseband version are unchanged. They are still 'I9020XXXKA3' and 'I9020XXXB3'. I thought they were going to change to I9023XXX... but apparently not. Is this normal? I'm confused.
Obviously this rom is for Europe, so my i9023 from Australia probably had a different factory rom. I need to go into a Vodafone store and check but if it's different, it's going to be difficult to find the original rom for Australian i9023...
hamajiro said:
Odin on Win7 Bootcamp worked! Even though I got an error when I was installing the Samsung USB Drivers, Windows started recognising the NS after that.
After using Odin, the only change I can tell from the bootloader is that the 'CARRIER INFO' has changed to 'EUR' from 'XSE'. The bootloader version and baseband version are unchanged. They are still 'I9020XXXKA3' and 'I9020XXXB3'. I thought they were going to change to I9023XXX... but apparently not. Is this normal? I'm confused.
Obviously this rom is for Europe, so my i9023 from Australia probably had a different factory rom. I need to go into a Vodafone store and check but if it's different, it's going to be difficult to find the original rom for Australian i9023...
Click to expand...
Click to collapse
Do you remember the initial values?i mean when your phone was with stock rom?
Sent from my Desire HD using Tapatalk
thanks, really needed this link
afilopou said:
Do you remember the initial values?i mean when your phone was with stock rom?
Sent from my Desire HD using Tapatalk
Click to expand...
Click to collapse
No, I don't remember the initial values...
I'll check them at a Vodafone store when I get a chance.
Sent from my Nexus S using XDA Premium App
OK, so I had a chance to go into a local Vodafone Australia store.
The Baseband version under 'About phone' from the settings was I9023XXXKB1.
Under fastbootmode, the bootloader and baseband versions were I9020XXXKA3 and I9020XXXKB1.
However, CARRIER INFO is 'XSE' for Vodafone Australia, where as the CARRIER INFO from the Samfirmware.com ROM is 'EUR'.
Almost back to factory stock condition! Is it possible to change the carrier info? Does anyone know where I can get the stock Australian ROM for Nexus S?
Hi guys,
I am trying to re-root as Tab needs to go in to be fixed. I copied across my nandroid backup and then tried to restore it but the MD5 checksum failed :-( I had already done a factory reset and format of system and am now stuck at the Samsung Logo. I can't mount the USB storage to copy over a different ROM to get it back up and running again. I have tried to mount USB storage in CWM 4.0.4 and 5.0.2.3 but keep getting "E:Unable to open ums lunfile (No such file or directory)".
Is the Tablet bricked? Is there a way out of this?
Help appreciated as am getting worried....
M
I was able to access my SDcard from recovery using Droid Explorer (google it):
1. do not connect Tab to PC
2. start Droid Explorer on PC
3. On your Tab in CWM: mounts and storage > mount system, data, efs (I don't know if all this is necessary, but It's what I did), mount USB storage
4. Connect Tab to PC, hit refresh icon in Droid Explorer
Now you should be able to access SDcard in Droid Explorer. You can only transfer individual files though, so any folder structures must be done manually.
Failing that, if you can get into download mode:
If you can get into download mode (which you should be able to), you can just use Odin to flash a new ROM: http://forum.xda-developers.com/showthread.php?t=1167250
The ASIAN ROM (Sept.) is the most recent (don't worry it defaults to English). Also, this will wipe your SDcard, but will get everything back to working order.
Thanks SO much for getting in touch, much appreciated! Well Droid Explorer is not working......I can connect via Odin though (thank God!). How exactly do I flash a ROM with it mate? Only ever done recoveries before....
Cheers,
M
mark.m.moran said:
Thanks SO much for getting in touch, much appreciated! Well Droid Explorer is not working......I can connect via Odin though (thank God!). How exactly do I flash a ROM with it mate? Only ever done recoveries before....
Cheers,
M
Click to expand...
Click to collapse
Watch the first 2-3 mins of this video to see how to operate ODIN. In the video the guy is trying to root his tab, whereas you are trying to go back to stock rom. So the bit where he chooses the pda from his zip file, you just substitute that with the pda and csc from the asian rom file using the link in the post above me.
http://www.youtube.com/watch?v=krQDP7xYlWg
mark.m.moran said:
Thanks SO much for getting in touch, much appreciated! Well Droid Explorer is not working......I can connect via Odin though (thank God!). How exactly do I flash a ROM with it mate? Only ever done recoveries before....
Cheers,
M
Click to expand...
Click to collapse
You need to use a ROM that is specifically flash-able in Odin. Pretty much just follow the directions in the link and you should be good to go.
After that, you'll need to re-install CWM, but once you're done that, you can flash whatever ROM you want just like you're used to.
dpakrr said:
Watch the first 2-3 mins of this video to see how to operate ODIN. In the video the guy is trying to root his tab, whereas you are trying to go back to stock rom. So the bit where he chooses the pda from his zip file, you just substitute that with the pda and csc from the asian rom file using the link in the post above me.
http://www.youtube.com/watch?v=krQDP7xYlWg
Click to expand...
Click to collapse
dpakrr, you are a LEGEND! I was able to get back to stock thanks to you after I thought I was screwed! I had to send the Tab back today for repair to Samsung as it is not being recognised at all by any PC I hook it up too. Not being recognised by Kies either.....you think it's a hardware fault?? I have tried three different PC's with three different OS's on them!
I flashed the stock ROM using Odin back onto it before sending it, will they be able to tell it was rooted? I noticed a flash counter on the Odin screen so wonder will that now be + 1?? I checked and Clockworkmod Recovery was gone, all that was there was the stock recovery.....
Cheers,
M
mark.m.moran said:
dpakrr, you are a LEGEND! I was able to get back to stock thanks to you after I thought I was screwed! I had to send the Tab back today for repair to Samsung as it is not being recognised at all by any PC I hook it up too. Not being recognised by Kies either.....you think it's a hardware fault?? I have tried three different PC's with three different OS's on them!
I flashed the stock ROM using Odin back onto it before sending it, will they be able to tell it was rooted? I noticed a flash counter on the Odin screen so wonder will that now be + 1?? I checked and Clockworkmod Recovery was gone, all that was there was the stock recovery.....
Cheers,
M
Click to expand...
Click to collapse
your welcome mate. im going to limerick for 3.5 months this friday and i love guinness beer so consider that a thank you to the irish lol.
hm well if you have followed the basic guidelines like turning usb debugging off, installing kies and reinstalling samsung mobile drivers and the samsung customer service has no idea whats going on then there is definitely something wrong. so yes could be a hardware fault but just seems strange.
nah the stock rom is not rooted and as you said recovery is back to stock as well, thats all the samsung guys should be worried about. dont think they'll care too much about odin flash counter etc. they will just have a look at the os on your tab and its now stock, so should be fine.
dpakrr said:
your welcome mate. im going to limerick for 3.5 months this friday and i love guinness beer so consider that a thank you to the irish lol.
hm well if you have followed the basic guidelines like turning usb debugging off, installing kies and reinstalling samsung mobile drivers and the samsung customer service has no idea whats going on then there is definitely something wrong. so yes could be a hardware fault but just seems strange.
nah the stock rom is not rooted and as you said recovery is back to stock as well, thats all the samsung guys should be worried about. dont think they'll care too much about odin flash counter etc. they will just have a look at the os on your tab and its now stock, so should be fine.
Click to expand...
Click to collapse
Phew Thanks for all the help man, so many good people here on XDA! I was just thinking that the machine sees the Tab when in ODIN mode but why not in Windows mode? What is the difference? Are low low level hardware drivers used for ODIN that Windows does not have access too?
By the way have a GREAT time in Limerick, it's a cool town and you will not find nicer people!
All the best,
M
mark.m.moran said:
Phew Thanks for all the help man, so many good people here on XDA! I was just thinking that the machine sees the Tab when in ODIN mode but why not in Windows mode? What is the difference? Are low low level hardware drivers used for ODIN that Windows does not have access too?
By the way have a GREAT time in Limerick, it's a cool town and you will not find nicer people!
All the best,
M
Click to expand...
Click to collapse
yes that is it mate. thats what i think it is, odin's got low level drivers which the OS doesnt. thats why I thought the samsung mobile drivers might help the OS identify the tab as well but that didnt work for u either did it. so the tab is probably faulty.
cheers mate, yeh look forward to having a great time in limerick
dpakrr said:
yes that is it mate. thats what i think it is, odin's got low level drivers which the OS doesnt. thats why I thought the samsung mobile drivers might help the OS identify the tab as well but that didnt work for u either did it. so the tab is probably faulty.
cheers mate, yeh look forward to having a great time in limerick
Click to expand...
Click to collapse
And a fault like that, is it easily fixable or would I need a new unit? If I get a repair I don't want issues with it again a few months down the line!!
Cheers,
M
mark.m.moran said:
And a fault like that, is it easily fixable or would I need a new unit? If I get a repair I don't want issues with it again a few months down the line!!
Cheers,
M
Click to expand...
Click to collapse
I'm not sure what causes it. Could be an internal rom missing a flashed image. You were just really unlucky . This is very rare so I wouldn't worry too much
dpakrr said:
I'm not sure what causes it. Could be an internal rom missing a flashed image. You were just really unlucky . This is very rare so I wouldn't worry too much
Click to expand...
Click to collapse
Phew, that good to know
Edit: Latest from the repair shop here in Dublin is that they could not fix it and it's been sent to Samsung! I had a feeling this would happen.....now have to wait at least another week :-(