Hi,
I was trying to root and install a custom rom on a friends phone. She has T-Mobile Galaxy S 4G. I was rushing through the whole project cause I had work and accidentally installed T-Mobile Vibrant Stock 2.1 using Heimdall. It was my fault. I did a google search for SGH-T959, but failed to realize that SGH-t959U is Vibrant and SGH-T959V is Samsung Galaxy S 4G...
After flashing the wrong ROM, I could not get it back into Download mode. I removed the SIM, SD card, Battery, and then tried putting it back into download mode (without the SIM or SD card) and that worked. I was able to get it into download mode at that point, but it would still not turn on or boot into recovery.
After realizing it was the wrong Flash, I searched online and found this http://forum.xda-developers.com/showthread.php?t=1358498 , after searching for users who bricked their phone previously and this was listed as a solution... the phone doesn't boot now however. It loads into Samsung Recovery (3e) and gives the error:
--Applying Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/TMB/system/'
Successfully applied multi-CSC
Each time i try to 'reboot system now' it just loops back to recovery with the same error. On that link i listed above, it says to install bootloaders if that CSC issue exists. Problem is, each time i try, it says PIT failed and then it just disconnects and wont reboot, requiring me to reflash the package all-together.
This phone was originally on 2.3.6 and the problem is I tried rooting using Vibrant instructions which was to go back to 2.1, then flash root, then CWM, then custom ROM.
How do i get this phone working again. I can pick up where i left off as far as rooting and installing a custom ROM. I have experience with it... But I have no idea how to get this phone out of this soft-brick. Can anyone please assist me. I feel terrible for messing up my friends phone.
Thanks a bunch!
TL;DR - Soft bricked SGS4G by flashing Vibrant ROM, tried to correct using SuperOneClick heimdall, doesnt work. please help. Originally was completely stock.
Read the second link in my signature and see if it helps you with Heimdal.
lumin30 said:
Read the second link in my signature and see if it helps you with Heimdal.
Click to expand...
Click to collapse
Yeah, I've read that when I was searching for a fix on my lunch break. My laptop is a MAC however. Which is why I didn't ODIN. I lost my Windows partition a while ago, along with my Windows CD.... Is there anyway I can get some MAC instructions?
JGonzo1299 said:
Yeah, I've read that when I was searching for a fix on my lunch break. My laptop is a MAC however. Which is why I didn't ODIN. I lost my Windows partition a while ago, along with my Windows CD.... Is there anyway I can get some MAC instructions?
Click to expand...
Click to collapse
Get heimdall 1.3.1 for mac os x here. There is 1.3.2 and 1.4.0-rc1, but don't use them, just use 1.3.1 for now!
Read the install instructions here.
After that, you should be able to do the oneclick on your mac.
Just replying to the OP... Still follow the instructions in my previous post.
JGonzo1299 said:
the phone doesn't boot now however. It loads into Samsung Recovery (3e) and gives the error:
--Applying Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/TMB/system/'
Successfully applied multi-CSC
Each time i try to 'reboot system now' it just loops back to recovery with the same error. On that link i listed above, it says to install bootloaders if that CSC issue exists. Problem is, each time i try, it says PIT failed and then it just disconnects and wont reboot, requiring me to reflash the package all-together.
Click to expand...
Click to collapse
The CSC error is just a red herring. Don't worry about that error. The one to worry about is not being able to flash the PIT!
JGonzo1299 said:
This phone was originally on 2.3.6 and the problem is I tried rooting using Vibrant instructions which was to go back to 2.1, then flash root, then CWM, then custom ROM.
Click to expand...
Click to collapse
Yea... Don't do that. Follow only instructions for the SGH-T959V, Galaxy S 4G. Do not ever, EVER, follow instructions for any other phone, unless you know exactly what you are doing.
JGonzo1299 said:
How do i get this phone working again. I can pick up where i left off as far as rooting and installing a custom ROM. I have experience with it... But I have no idea how to get this phone out of this soft-brick. Can anyone please assist me. I feel terrible for messing up my friends phone.
Thanks a bunch!
TL;DR - Soft bricked SGS4G by flashing Vibrant ROM, tried to correct using SuperOneClick heimdall, doesnt work. please help. Originally was completely stock.
Click to expand...
Click to collapse
Make sure you only follow instructions for the SGH-T959V, Galaxy S 4G! As I said above.
Either follow the instructions in my oneclick sticky thread, or follow lumin30's guide.
Make sure you try different usb cables. Make sure the ports on the computer and phone are clear of obstructions. Check in the cable connectors too. If all that still doesn't work, try a different computer. You could have bad usb ports. This has happened to me before, but it was a double whammy. I had bad usb ports on my computer and a bad usb cable.
bhundven said:
Get heimdall 1.3.1 for mac os x here. There is 1.3.2 and 1.4.0-rc1, but don't use them, just use 1.3.1 for now!
Read the install instructions here.
After that, you should be able to do the oneclick on your mac.
Click to expand...
Click to collapse
With that in mind, does anyone have a link to the most up to date Stock ROM not rooted. The Sticky Page has a dead link and the workaround link takes me to the OneClick ROM install that gave me the problem to begin with. I'd rather use the instructions to flash it myself and choose the file instead of doing the OneClick option. Does that make sense?
bhundven said:
Just replying to the OP... Still follow the instructions in my previous post.
The CSC error is just a red herring. Don't worry about that error. The one to worry about is not being able to flash the PIT!
Yea... Don't do that. Follow only instructions for the SGH-T959V, Galaxy S 4G. Do not ever, EVER, follow instructions for any other phone, unless you know exactly what you are doing.
Make sure you only follow instructions for the SGH-T959V, Galaxy S 4G! As I said above.
Either follow the instructions in my oneclick sticky thread, or follow lumin30's guide.
Make sure you try different usb cables. Make sure the ports on the computer and phone are clear of obstructions. Check in the cable connectors too. If all that still doesn't work, try a different computer. You could have bad usb ports. This has happened to me before, but it was a double whammy. I had bad usb ports on my computer and a bad usb cable.
Click to expand...
Click to collapse
Yeah i followed Vibrant instructions on accident. It was a careless mistake. Ill ignore the CSC error then and Ill try using a different USB port. My usb cable is brand new from my SIII. I don't think its a problem. But my mac USB ports are pretty old.
JGonzo1299 said:
With that in mind, does anyone have a link to the most up to date Stock ROM not rooted. The Sticky Page has a dead link and the workaround link takes me to the OneClick ROM install that gave me the problem to begin with. I'd rather use the instructions to flash it myself and choose the file instead of doing the OneClick option. Does that make sense?
Click to expand...
Click to collapse
Uhm, In the very first post of this thread, is this link. This is the totally back to stock oneclick.
I just downloaded it. Link works fine.
Yes, I realize you'd like to just run "heimdall" to flash everything, but it is so error prone.
The oneclick works for me on mac, linux, and windows. Again, if you have problems, list out each step you made and the results and we'll help
Just open a terminal, type:
Code:
java -jar T959VUVKJ6_STOCK-UVKJ6-One-Click.jar
and go...
bhundven said:
Uhm, In the very first post of this thread, is this link. This is the totally back to stock oneclick.
I just downloaded it. Link works fine.
Yes, I realize you'd like to just run "heimdall" to flash everything, but it is so error prone.
The oneclick works for me on mac, linux, and windows. Again, if you have problems, list out each step you made and the results and we'll help
Just open a terminal, type:
Code:
java -jar T959VUVKJ6_STOCK-UVKJ6-One-Click.jar
and go...
Click to expand...
Click to collapse
OK. I followed this. It DIDNT work. Ill list the steps i did.:
1) Redownloaded the one click listed above to ensure its not a corrupted download and verified
2)Placed file in my user folder (MAC Terminal defaults to this folder which is why i chose it)
3) Checked my Java version using Software update on MAC. Java was already up to date.
4)Opened Terminal
5) typed ls to confirm i was in the correct directory.
6) typed 'java -jar T959VUVKJ6_STOCK-UVKJ6-One-Click.jar'
7) Terminal began doing its thing.
8) I already have the Samsung Drivers. I've had Samsung Facinate and i currently have SIII so thats all up to date. Once i verified, i skipped the samsung drivers step.
9)I skipped the x86 step cause i know MAC has its own version of it already installed. My MAC version is 10.6.8
10) Connected phone to USB port, put in download mode.
11) Waited til phone was recognized with OneClick AND my MAC,
12) Ready to Flash
13) Clicked Flash
14) Flash successful, phone automatically powers down, reboots
15) Phone automatically loads into Android Recovery (3e) and gives error CSC mumbo jumbo i quoted in my first post
16) I needed bootloaders since I accidentally put Vibrant ROM. (per instructions from http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2 )
17) Removed Battery, Reconnected to MAC and placed in Download Mode
18) Clicked Flash Bootloaders, bypassed the warning, clicked Flash.
19) Uploading PIT, PIT upload failed!, Ending Session..., Rebooting Device...
20) Phone shuts off and never reboots, stays as a black screen, cant turn it on, load into recovery. I can ONLY load it into Download mode.
I followed these instructions as directed http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2 . Tried different USB cables and also tried BOTH USB ports. Please help. Thanks in advance.
JGonzo1299 said:
OK. I followed this. It DIDNT work. Ill list the steps i did.:
1) Redownloaded the one click listed above to ensure its not a corrupted download and verified
2)Placed file in my user folder (MAC Terminal defaults to this folder which is why i chose it)
3) Checked my Java version using Software update on MAC. Java was already up to date.
4)Opened Terminal
5) typed ls to confirm i was in the correct directory.
6) typed 'java -jar T959VUVKJ6_STOCK-UVKJ6-One-Click.jar'
7) Terminal began doing its thing.
8) I already have the Samsung Drivers. I've had Samsung Facinate and i currently have SIII so thats all up to date. Once i verified, i skipped the samsung drivers step.
9)I skipped the x86 step cause i know MAC has its own version of it already installed. My MAC version is 10.6.8
10) Connected phone to USB port, put in download mode.
11) Waited til phone was recognized with OneClick AND my MAC,
12) Ready to Flash
13) Clicked Flash
14) Flash successful, phone automatically powers down, reboots
15) Phone automatically loads into Android Recovery (3e) and gives error CSC mumbo jumbo i quoted in my first post
16) I needed bootloaders since I accidentally put Vibrant ROM. (per instructions from http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2 )
17) Removed Battery, Reconnected to MAC and placed in Download Mode
18) Clicked Flash Bootloaders, bypassed the warning, clicked Flash.
19) Uploading PIT, PIT upload failed!, Ending Session..., Rebooting Device...
20) Phone shuts off and never reboots, stays as a black screen, cant turn it on, load into recovery. I can ONLY load it into Download mode.
I followed these instructions as directed http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2 . Tried different USB cables and also tried BOTH USB ports. Please help. Thanks in advance.
Click to expand...
Click to collapse
Just double checking, This is t959v, not t959w... right? T959W has some issues with heimdall and odin that are still being worked out.
When i originally encountered the problem. I downloaded the 'back to Factory stock rom' for vibrant. It was an ODIN file so it was .tar, I downloaded its associated PIT file.
I loaded the PIT file into heimdall under the 'flash' tab
i extracted the .tar file and found 6 files. i took each file and loaded them individually to heimdall 1.3.1 under the 'flash' tab.
I had 6 files in there: cache, dbdata, factoryfs, modem, param, zImage.
Once I flashed those it wouldnt boot and was just black. could only go into download mode.
Then I realized i messed up and used the wrong ROM.
Came into this thread for SGS4G
Found the right files.
Phones been broken since and ive been following the instructions listed above. hope that makes sense. im at my work desk. sorry. Ill try to find the link of the go back to factory stock file i found on the vibrant forums but it was whatever vibrant came with out of the box. and it was a verified stock ROM. I just followed the instructions to the T until I encountered problems.....
bhundven said:
Just double checking, This is t959v, not t959w... right? T959W has some issues with heimdall and odin that are still being worked out.
Click to expand...
Click to collapse
Yes. I popped the battery out and im looking at the label in the back of the phone and it says SGH-959V.
JGonzo1299 said:
Yes. I popped the battery out and im looking at the label in the back of the phone and it says SGH-959V.
Click to expand...
Click to collapse
Ok, so it sounds like you need to try a different computer.
I know this is a pita, and I'm not trying to make things more difficult then they are, but as I said before. I've had this issue and had to buy a new computer. :crying:
Just thinking aloud, could try the kc1/kd1(froyo) firmware? Then move to gingerbread.
bhundven said:
Ok, so it sounds like you need to try a different computer.
I know this is a pita, and I'm not trying to make things more difficult then they are, but as I said before. I've had this issue and had to buy a new computer. :crying:
Click to expand...
Click to collapse
I'm going to try my friends PC. I'll try ODIN if I can find ODIN files, if not ill try heimdall instructions on a PC.
champ1919 said:
Just thinking aloud, could try the kc1/kd1(froyo) firmware? Then move to gingerbread.
Click to expand...
Click to collapse
Where do I find these? Can you post the link? I can probably try to flash this while im still at work for the next 2 hours lol
JGonzo1299 said:
I'm going to try my friends PC. I'll try ODIN if I can find ODIN files, if not ill try heimdall instructions on a PC.
Where do I find these? Can you post the link? I can probably try to flash this while im still at work for the next 2 hours lol
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=27374477
I think it's still a good link in that thread... I'm on my phone, I did try and something started.
JGonzo1299 said:
I had 6 files in there: cache, dbdata, factoryfs, modem, param, zImage.
Click to expand...
Click to collapse
So out of curiosity I just unpacked this Ravers KJ6 for Odin which was harder to find than I thought because Raver likes to spell offical instead of official. But I digress. The kicker here is that there are only 5 files.
cache.rfs
factoryfs.rfs
modem.bin
Sbl.bin
zImage
If I where the OP I'd DL that then unpack it. Reverse engineer what you did the first time by using the proper .tar through heimdall. If it worked once to totally hose you it just might work again to save you. Or it might not. Either way it's worth a shot. Good luck man.
hechoen said:
So out of curiosity I just unpacked this Ravers KJ6 for Odin which was harder to find than I thought because Raver likes to spell offical instead of official. But I digress. The kicker here is that there are only 5 files.
cache.rfs
factoryfs.rfs
modem.bin
Sbl.bin
zImage
If I where the OP I'd DL that then unpack it. Reverse engineer what you did the first time by using the proper .tar through heimdall. If it worked once to totally hose you it just might work again to save you. Or it might not. Either way it's worth a shot. Good luck man.
Click to expand...
Click to collapse
So you mean Download this and do exactly what I did that bricked the phone in the first place. but use these files instead. Cause these are for SGS4G. Correct?
I'll try that now. But dbdata is missing. Is that an issue? What is dbdata for anyway?
champ1919 said:
http://forum.xda-developers.com/showthread.php?p=27374477
I think it's still a good link in that thread... I'm on my phone, I did try and something started.
Click to expand...
Click to collapse
Thank you. I'm going to try this after I try what i just posted above first. Will post results later tonight around 11 EST. Work computer wont let me download any links.
JGonzo1299 said:
So you mean Download this and do exactly what I did that bricked the phone in the first place. but use these files instead. Cause these are for SGS4G. Correct?
I'll try that now. But dbdata is missing. Is that an issue? What is dbdata for anyway?
Click to expand...
Click to collapse
Yes that is what I mean.
I don't own a vibrant so I have know idea what dbdata is for. Maybe someone will chime in with a better answer. Doing it this way you should be able to get the phone back to where it was. Again this is my best guess at how to try to fix it. Plus it's really hard to brick a brick(bad joke I know but i had too).
Related
Here was my situation, and how I got out of it:
I was running the Perception build 7 ROM. It was great, no issues except that I needed to get some kernel modules for it, and was unable to get the info I needed to re-create the kernel build environment. I decided to return to stock. There were lots of threads, all going in different directions with inconsistent advice. The wiki I was looking at has what appeared to be a ClockworkMod (CWM) backup.
I had already tried to restore my own CWM backup, but (after disabling lagfix) would restore, but then seemed to loop trying to start the lock screen. Same thing with the version on the wiki. I didn't want to restore to the ATT version and I didn't have windows to run Odin...
So this should work from Windows, Linux and Mac.
get param.lfs from http://forum.xda-developers.com/showpost.php?p=9663090&postcount=58
get FIRMWARE from http://forum.xda-developers.com/showpost.php?p=9109370&postcount=697
Get Odin.rar from http://forum.xda-developers.com/showpost.php?p=8802897&postcount=1
Get Heimdall from http://www.glassechidna.com.au/products/heimdall/
Install Heimdall and any drivers it requires.
Extract the .pit file from Odin.rar. I have heard other people say don't use the pit file…I did…
Unzip the firmware
start Heimdall
FactoryFS
- factory.rfs
Kernel
- zImage
Param.lfs
- param.lfs - though I didn't use this
Primary Bootloader
- I left this blank
Secondary Bootloader
- I left this blank
Cache
- cache.rfs
Modem
- modem.bin
FactoryFS
- factory.rfs
Click Start
Phone will do it's thing. I did receive an error at the very end but all went well. I'd welcome some additional info on the Primary/Secondary Bootloader.
Curious if this restored the bootloader from at&t back to the rogers one?
Excellent! Another successful restore of Rogers stock with Heimdall. Thank you for the write up, gin032.
@Gin Which driver did you install ? WinUSB or libusb ?
Does your Start button starts greyed out ?
I tried both drivers and the only time the Start button is active is when i put a file in primary bootloader. I tried opening heimdall prior and after the phone is in download mode but the Start button always stay inactive. Odin on the other hand always detect my phone in download mode.
Just trying to figure out both apps
I had the same troubles is well.
silvertag said:
@Gin Which driver did you install ? WinUSB or libusb ?
Does your Start button starts greyed out ?
I tried both drivers and the only time the Start button is active is when i put a file in primary bootloader. I tried opening heimdall prior and after the phone is in download mode but the Start button always stay inactive. Odin on the other hand always detect my phone in download mode.
Just trying to figure out both apps
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I896 using XDA App
I'm running on the Mac and Linux so I haven't tried the Windows version yet. I'll try to take a look over the next few days.
silvertag said:
@Gin Which driver did you install ? WinUSB or libusb ?
Does your Start button starts greyed out ?
I tried both drivers and the only time the Start button is active is when i put a file in primary bootloader. I tried opening heimdall prior and after the phone is in download mode but the Start button always stay inactive. Odin on the other hand always detect my phone in download mode.
Just trying to figure out both apps
Click to expand...
Click to collapse
gin032 said:
I'm running on the Mac and Linux so I haven't tried the Windows version yet. I'll try to take a look over the next few days.
Click to expand...
Click to collapse
Heimdall might not work for you on Mac, that requires an official Froyo update with fixed secondary bootloader. Should work fine on Linux if you followed readme file instructions.
Sent from my SAMSUNG-SGH-I896 using XDA App
This seems to be correct. I tried Heimdall on both Windows 7 32-bit and Mac OS X Leopard and neither worked for me.
I could never select the "Start" button on either, and it seems your assertion that a secondary boot loader is required for Mac OS X is bang on.
I instead used Odin with the Pit file from this thread and the stock Rogers firmware and it seems to have worked.
Only the AT&T World Phone boot screen still shows up as a remnant of my previous flashing to Cognition.
I think I would have stayed with Cog if not for the reduced battery life, GPS lock-on slowness and static with BlueTooth head sets, as otherwise it is a fabulous ROM.
Either way, thanks to the OP for at least giving us the tips we needed to restore our older, but better than AT&T firmware!
sshvetsov said:
Heimdall might not work for you on Mac, that requires an official Froyo update with fixed secondary bootloader. Should work fine on Linux if you followed readme file instructions.
Sent from my SAMSUNG-SGH-I896 using XDA App
Click to expand...
Click to collapse
soooo why is the "start" button grayed out???
soooo why is the "start" button grayed out???
Probably because you didn't read instructions and to prevent you from unknowingly bricking your phone. You most likely didn't uncheck the repartition option.
Sent from my SAMSUNG-SGH-I896 using XDA App
SteveCheeseman said:
soooo why is the "start" button grayed out???
Click to expand...
Click to collapse
10ee said:
This seems to be correct. I tried Heimdall on both Windows 7 32-bit and Mac OS X Leopard and neither worked for me.
I could never select the "Start" button on either, and it seems your assertion that a secondary boot loader is required for Mac OS X is bang on.
I instead used Odin with the Pit file from this thread and the stock Rogers firmware and it seems to have worked.
Only the AT&T World Phone boot screen still shows up as a remnant of my previous flashing to Cognition.
I think I would have stayed with Cog if not for the reduced battery life, GPS lock-on slowness and static with BlueTooth head sets, as otherwise it is a fabulous ROM.
Either way, thanks to the OP for at least giving us the tips we needed to restore our older, but better than AT&T firmware!
Click to expand...
Click to collapse
sshvetsov said:
Probably because you didn't read instructions and to prevent you from unknowingly bricking your phone. You most likely didn't uncheck the repartition option.
Sent from my SAMSUNG-SGH-I896 using XDA App
Click to expand...
Click to collapse
sshvetsov is 100% correct. If it wasn't for the fact I put in functionality to grey out the start button you'd now have a bricked device. You can not repartition your device unless you provide all the necessary files.
It doesn't help that for a long time the samfirmware website was spreading misinformation about requiring you specify a PIT file in Odin without repartition checked. There's no need to select a PIT file when you're not repartitioning, in fact Odin will just ignore the fact that you have done so.
The start button isn't greyed out when you don't have a working secondary bootloader. Instead, after you press Start, you will receive a message saying your device couldn't be detected.
Benjamin Dobell said:
sshvetsov is 100% correct. If it wasn't for the fact I put in functionality to grey out the start button you'd now have a bricked device. You can not repartition your device unless you provide all the necessary files.
It doesn't help that for a long time the samfirmware website was spreading misinformation about requiring you specify a PIT file in Odin without repartition checked. There's no need to select a PIT file when you're not repartitioning, in fact Odin will just ignore the fact that you have done so.
The start button isn't greyed out when you don't have a working secondary bootloader. Instead, after you press Start, you will receive a message saying your device couldn't be detected.
Click to expand...
Click to collapse
In my case, I did re-partition....but in the interest of fullness, where can one find such a secondary bootloader?
Bricked my rogers i896 while trying to mash up different kernels for a rom, odin didnt work so i tried heimdall with the procedures thanks to OP.
The only difference was I did not use the pit file. Everything worked flawlessly and I still managed to maintain my data on root sd although i lost root access. The ATT splash screen also was removed (thank goodness) and model number changed back to i896 in the "About". It is now back to pretty much stock, though I did lose the APN settings (can easily reenter it). Last step now is just to re-root and restore via Titanium Backup.
Thanks for the helpful information everyone!
Now that 2.2 is out on Kies, it should become a lot simpler to restore to stock Rogers.
All we need is an ODIN image from the 2.2 release.
loonieryan said:
Now that 2.2 is out on Kies, it should become a lot simpler to restore to stock Rogers.
All we need is an ODIN image from the 2.2 release.
Click to expand...
Click to collapse
This please!
I've tried this, but use zadig.exe my phone shows up as Gadget Serial. So I installed anyways, it says successful, but nothing happens in the frontend that shows the phone and it doesn't allow me to start anything.
ootz0rz said:
Curious if this restored the bootloader from at&t back to the rogers one?
Click to expand...
Click to collapse
+1 this is important!
Tried doing this and my phone is now a brick. It's stuck at the following image:
Phone...Yellow exclamation...PC
Edit: Just got download mode back but still not working for me
Edit: Got Odin3 to work finally. Flashing JL1. Hoping it works.
ok, I have a real challenge.
I made the derp of giving my phone temp root using Z4root, then I ran OneClickLagFix on the phone. The phone rebooted & now just goes to a black screen after the rogers logo. it is on but does not respond to anything (capacitive butons light up when pressed).
I tried the steps listed here to revert to factory but it didn't help. Any ideas?
Hey Guys.
So i am having this problem for about 2 weeks now. You won't believe how many threads i read, to find a solution to my problem.
So it seems like i soft bricked my sgs4g. It is in a mode, where i can't do anything.
There is a phone on the left, a warning triangle in the middle, and a computer on the right side. Under that it says "firmware upgrade fail! Try using recovery mode".
So, i really don't know much about flashing, rooting, cwm etc.. So i got some help by a friend of mine to install some rom i can't quite remember the name. It had a lag-fix in it, cwm, root and also a overclocked processor. It worked perfectly except that it didnt' recognize my Sim. So i tried to flash it to a coupel other roms, but everywhere the same problem. Eventually, odin had an error, and now i am in this freaking mode where i can't get out of. Volume up + volume down and plugging in usb cord won't work. since my phone doesnt work, i can't really install adb, to fix the download mode, and even a usb jig won't bring me to the download mode. I really have no idea how i can get out of here. I would really appreciate any kind of help, and i hope that i can get this thing fixed.
If you need any further information about my phone, just ask.
Thanks for everybody who can or wants to help!!
max aka de4dw0lf
de4dw0lf said:
There is a phone on the left, a warning triangle in the middle, and a computer on the right side.
Click to expand...
Click to collapse
Does it look like the attached pic? Or similar?
it looked like that before. than i tried to falsh it a couple times and now it looks different. It looks more modern now. and there is an actual text below it!
de4dw0lf said:
Hey Guys.
So i am having this problem for about 2 weeks now. You won't believe how many threads i read, to find a solution to my problem.
So it seems like i soft bricked my sgs4g. It is in a mode, where i can't do anything.
There is a phone on the left, a warning triangle in the middle, and a computer on the right side. Under that it says "firmware upgrade fail! Try using recovery mode".
So, i really don't know much about flashing, rooting, cwm etc.. So i got some help by a friend of mine to install some rom i can't quite remember the name. It had a lag-fix in it, cwm, root and also a overclocked processor. It worked perfectly except that it didnt' recognize my Sim. So i tried to flash it to a coupel other roms, but everywhere the same problem. Eventually, odin had an error, and now i am in this freaking mode where i can't get out of. Volume up + volume down and plugging in usb cord won't work. since my phone doesnt work, i can't really install adb, to fix the download mode, and even a usb jig won't bring me to the download mode. I really have no idea how i can get out of here. I would really appreciate any kind of help, and i hope that i can get this thing fixed.
If you need any further information about my phone, just ask.
Thanks for everybody who can or wants to help!!
max aka de4dw0lf
Click to expand...
Click to collapse
First off, you are in an alternate download mode. Just flash Odin as normal with a stock ROM and all will be good again.
Second off, what ROM did you flash that has an overclocked processor? We don't have a kernel that supports overclocking yet, at least for gb.
As for the SIM card, I've had that problem before. It's from not wiping /data /system /cache before flashing. Once you Odin back to stock, it should work. If not, you will have to contact your service provider to get a new one.
de4dw0lf said:
it looked like that before. than i tried to falsh it a couple times and now it looks different. It looks more modern now. and there is an actual text below it!
Click to expand...
Click to collapse
That is still download mode. Use Heimdall One Click.
i already tried to flash back to stock a couple times. but it just won't work, because odin always gets an error. Could you send me a link to the right stock version for my sgs4g? maybe i am just using the wrong one..
also, i want to avoid sending it back to t-mobile, because my phone is a refurbished one, and i am not quite sure about the warranty..
de4dw0lf said:
i already tried to flash back to stock a couple times. but it just won't work, because odin always gets an error. Could you send me a link to the right stock version for my sgs4g?
Click to expand...
Click to collapse
Use Heimdall One Click. The one with bootloaders. It will work. Read the OP to a T.
de4dw0lf said:
i already tried to flash back to stock a couple times. but it just won't work, because odin always gets an error. Could you send me a link to the right stock version for my sgs4g? maybe i am just using the wrong one..
also, i want to avoid sending it back to t-mobile, because my phone is a refurbished one, and i am not quite sure about the warranty..
Click to expand...
Click to collapse
Click on the Lightning Zap link in my signature... Then click on the link called Removing the Gremlins in the OP
Read the whole post. The link will give you KG4 and Odin and the necessary drivers...
If you already have odin setup use this http://forum.xda-developers.com/showthread.php?t=1353176 It's the official update to Gingerbread.
alright
Alright. i will try the things you guys sent me, and i will tell you later if it worked.
Thanks a lot!!! i hope it works^^
I'm going through the exact same problem right now! But this happened to me using Heimdall. My phone is still recognized by Heimdall but when I try to reflash it I get this in the command prompt:
[C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB 3DC9DDF\heimdall-win32\heimda
ll.exe, flash, --pit, C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB 3DC9DDF\
Sgs4g.pit, --6, C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB 3DC9DDF\zImage
, --7, C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB 3DC9DDF\zImage-1, --22,
C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB 3DC9DDF\factoryfs.rfs, --23,
C:\DOCUME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB 3DC9DDF\data.rfs, --24, C:\DOC
UME~1\Dar\LOCALS~1\Temp\DarHeimdallOneClickB3DC9DD F\cache.rfs, --11, C:\DOCUME~1
\Dar\LOCALS~1\Temp\DarHeimdallOneClickB3DC9DDF\mod em.bin]
and this in the Heimdall window:
Initialising connection...
Detecting device...
Claiming interface...
Setting up interface...
Checking if protocol is initialised...
Protocol is not initialised.
Initialising protocol...
Handshaking with Loke...
Beginning session...
Session begun with device of type: 0
Downloading device's PIT file...
PIT file download sucessful
Uploading KERNEL
KERNEL upload failed!
Ending session...
i am too stupid
Ok, i am probably just way too stupid, but i can't find the download for heimdall one-click.
ohh. i get it now. but when i hit enter after typing in:
"java -jar T959V-UVKJ6-One-Click.jar"
the following message comes up:
Unable to access karfoöe T959V-UVKJ6-One-Click
Any ideas?
de4dw0lf said:
ohh. i get it now. but when i hit enter after typing in:
"java -jar T959V-UVKJ6-One-Click.jar"
the following message comes up:
Unable to access karfoöe T959V-UVKJ6-One-Click
Any ideas?
Click to expand...
Click to collapse
Did you download java?
---------- Post added at 11:18 PM ---------- Previous post was at 11:16 PM ----------
DarsOnMars said:
I'm going through the exact same problem right now! But this happened to me using Heimdall.
Click to expand...
Click to collapse
You may have a bad download. You might try redownloading the file.
java is installed, i might have fixed that problem though. i think my download wasn't quite finished, because when i updated java, it wanted me to close firefox..
so, because my phone is not in the actual download mode, it won't find any drivers to install.. can't i just install them manually?
de4dw0lf said:
so, because my phone is not in the actual download mode, it won't find any drivers to install.. can't i just install them manually?
Click to expand...
Click to collapse
Here is my recommendation...
First used the attached .zip (assuming you are on a 64 bit machine) and uninstall all samsung and android drivers.
Then start over with Heimdall One Click. It will tell you whether you have the drivers you need or not, and if you do not, it will put up directions, send you to zadig and tell you what you need to do.
And you are in download mode.
Heimdall uses different drivers then ODIN.
Go here then and download 32 bit USBDeView.
I recommend restarting your machine after uninstalling drivers.
im on 32 bit
de4dw0lf said:
im on 32 bit
Click to expand...
Click to collapse
By the way... I recommended downloading the bootloader one click in case whatever you previously flashed was not for our device and changed your bootloaders.
"java -jar T959V-UVKJ6-One-Click.jar" --> is not the bootloader download.
SMS-KJ6-beta2d_Stock-Rom_with_Bootloaders-One-Click.jar = bootloader download.
hmm.. so it tells me to select Samsung USB Composite device, but it's not there.. :/
i am downloading the one "Download SMS KJ6 (beta2d) Kernel Stock Rom with Bootloaders" right now.
And after i am done im gonna restart my computer.
So I believe I goofed here and could use some help. The tablet still works and boots into honeycomb, but things are not the same. ADW is crashing, home button is not working. I can still open apps and go to settings and get onto the net.
I rooted the device, installed Clockwork Mod and the SDCard permissions fix, but this all happened after applying the SDCard fix.
Now I went into recovery and tried restoring to factory default and used the factory reset through the Privacy tab under settings. Both options do not work. When I say it doesn't work, I mean that it doesn't ask me to create or sign in to my google account, it just goes back to the home screen with the same problems.
I read that Kies can reflash the device, but Kies is not recognizing the device on my mac. I haven't tried it using VMWare with Windows 7. I can give that a try I guess, but I can use some help here.
**edit**
So I logged into bootcamp using Windows 7, Kies shows it's trying to connect but it doesn't go past that point. I have found the odin instructions, but I don't have the proper stock rom to use with it. What now? The multiupload sites don't work, it keeps leading to google can't find the page.
Thanks!
***edit 2***
I need the official GT-P6210 US Firmware so I can recover my tablet using Odin (I can't boot into recovery, so I need to use Odin). I saw the thread with the download links, but they are all broken.
I can really use the help, I've googled all night and day, searched this forum and I'm running to brick walls. I'm at the screen where it says there was a problem updating the os (or something like that) and to use the kies recovery mode?
Thank you.
Have you tried searching for your stock firmware on www.sammobile.com ?
P_
I didn't know that existed, I will give it a try. I'm assuming I use those stock Rome with the oden app?(forgive me if I'm not spelling that right
Sent from my PC36100 using xda premium
Hmm, it doeantlook like my Tom is on that site. Other suggestions?
Sent from my PC36100 using xda premium
helps on its way bro......
now follow my steps....
step1. download your required firmware package from the development section.
step2. download the odinv1.8 and then unzip and install to desktop
step3. open odin and select PDA and load the unzipped firmware file. (do not touch anything else at all)
step4. power on the device with volume button down and power on (download mode)
step5. plug in to pc via USB 2.0 as this has less chance of failing then press start on odin it will push the firmware on to the device and them reboot
step6. sit back and enjoy lol.
thank me if it helps.
jmar8124 said:
now follow my steps....
step1. download your required firmware package from the development section.
step2. download the odinv1.8 and then unzip and install to desktop
step3. open odin and select PDA and load the unzipped firmware file. (do not touch anything else at all)
step4. power on the device with volume button down and power on (download mode)
step5. plug in to pc via USB 2.0 as this has less chance of failing then press start on odin it will push the firmware on to the device and them reboot
step6. sit back and enjoy lol.
thank me if it helps.
Click to expand...
Click to collapse
Yes, I did all this, but when I get to step 5 it says that the rom I used was invalid. Maybe I downloaded the wrong one, I'm not sure. But all the rome on here using multi upload, the links are not working. I just need to find the rom for my US Galaxy tab 7 plus wifi... can you point me to a working link?
At this point, I've been trying to reflash a firmware and it's not worked, it has now kept me at the Galaxy Tab 7.0 Plus boot screen. It doesn't even play the Samsung animation.
And while I'm in CWM i tried reformatting again and I noticed one error:
"Error mounting /sdcard/.android_secure! <new line> Skipping format..."
This is the what I get when I format:
Formatting /data...
Error mounting /data!
Skipping format
Formatting /cache...
Formatting /sd-ext...
Formatting /sdcard/.android_secure!
Skipping format...
Data wipe complete.
Suggestions would be great.
BTW: The multiupload.com url's in the development section is totally not working. I could use a mirror site for looking on the net is not working.
have you tried going to mounts and mounting data?
bdds13 said:
have you tried going to mounts and mounting data?
Click to expand...
Click to collapse
Ya, doing that says it's error.
According to my research, I need to get the official us firmware, but the links are broken... I'm trying very hard to find it elsewher
Sent from my PC36100 using xda premium
Well, I'm one step closer to solving this issue. I found a european rom and tried flashing it on my device using odin. It was going all well until at the end it failed when completing the writing part of the flash. When I tried booting the device, I get a graphic and an exclamation point saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & Try again." Sooo, I think what i need is to get my hands on a firmware version for us or something that works.
it may be dangerous, but I thought there was a p6200 firmware and .PIT file floating around. You want to load that in ODIN ( or heimdall ) and choose repartition.
just my advice.
Ya I found a European firmware but it story!!ed at like 98%.
Sent from my PC36100 using xda premium
chrisrotolo said:
it may be dangerous, but I thought there was a p6200 firmware and .PIT file floating around. You want to load that in ODIN ( or heimdall ) and choose repartition.
just my advice.
Click to expand...
Click to collapse
No need for pit, flashed european GT-P6210 firmware once and just some minor system app difference.
And yes, it seems there is no working link of official US GT-P6210 firmware here.
well good news!! Amazon has agreed to replace my tablet, so a new one is being shipped as I speek and should be here in about 3 days. I didn't think they would replace it with what has happened, but I got lucky.
All I can think of is the sdcard permissions hack screwing up everything. I'm just going to accept defeat and go the route samsung wants me to take to load files. Unfortunate, but it's the price to pay for this device. I really like the GT+, light weight, thin and looks great.
hmmm i've being flashing my GT+ many times as i always play with it framework and such... and have use the hack each time i reflash... never got the error
For future reference the 6210 US retail firmware is located in the Dev section under 'official Firmwares' Post #82 (I am a noob so I can't post a link)
I have used it. Once you have it loaded via ODIN then you can upgrade to the latest firmware via Keis.
wes.harris said:
For future reference the 6210 US retail firmware is located in the Dev section under 'official Firmwares' Post #82 (I am a noob so I can't post a link)
I have used it. Once you have it loaded via ODIN then you can upgrade to the latest firmware via Keis.
Click to expand...
Click to collapse
I seriously don't know how I missed that post. I'm looking it up now.
Hey all. Unfortunately, I can't post in the development forum because this is my seventh post. :crying: Anyways, I had a comment about the verizon root and hopefully somebody can either move this to that sticky or answer... Anyways...
I wanted to see what was done to the modified image to make sure nothing strange was put in it. I downloaded the 'orig' from fus, extracted the image, and ran a md5 check on all the files. I then downloaded your system.img file and ran a md5check on all the files. I found two files were added...
#
330a331
> 65bd72996c68f289c5fa0b81f0874127 app/Superuser.apk
2007a2009
> d1a9de9724c662a50a9a128e48b1fb37 xbin/su
#
When I tried to find the versions of those files and the md5 hashes, they don't match. Here's your version...
65bd72996c68f289c5fa0b81f0874127 app/Superuser.apk
d1a9de9724c662a50a9a128e48b1fb37 xbin/su
I then downloaded 'superuser' from http://androidsu.com/superuser/, which I'm assuming is the source. For the 3.1.3 version, I get this...
MD5 (system/app/Superuser.apk) = e0bc7b7284b68c9539b6ec6b306310e0
MD5 (system/bin/su) = 054c9a22d8900d50ce6172fd56bbf414
For the 3.2-RC2 version, I get this...
MD5 (system/app/Superuser.apk) = d0abb9413f712f2f7dd43ed47df6c2d8
MD5 (system/bin/su) = 96c672c1339da363232f42dd87b4a3cf
As you can see, the md5's are different which make me a little uneasy about it. I was wondering if anybody knew of the source for these. I think I just email'ed invisiblek the same thing, but don't know if it would get to him or not. Maybe somebody else knows the answer.
Thanks!
WTF?
Im confused, I see active topics saying the S3 hasn't got root yet due to the locked boot loader, I also see active topics saying it has been unlocked + rooted..
answer
OK, I still haven't got my s3, so I haven't tried it. But from what I read, you can flash a custom system.img and put su and supervisor.apk on it. This allows you to get 'root' on the device. Here's a reference...
http://forum.xda-developers.com/showthread.php?t=1756885
Verizon Failed on on Odin now stuck at SIII boot screen
wiz561 said:
OK, I still haven't got my s3, so I haven't tried it. But from what I read, you can flash a custom system.img and put su and supervisor.apk on it. This allows you to get 'root' on the device. Here's a reference...
http://forum.xda-developers.com/showthread.php?t=1756885
Click to expand...
Click to collapse
Verizon Failed on on Odin now stuck at SIII boot screen
I tried the procedure with rooted.system.img and Odin 3.07 and it threw root Xmit Write fail. Then it just hung.
I pulled the battery and now it won't boot. I tried doing Vol Up + Home to do a hard reset to no avail.
I also tried Samsung-Updates.com-SCH-I535_VZW_1_20120705143513_fti2qg2lmf file through Odin with no success.
I've rooted phones in the past but never through this method.
I'm hoping I haven't bricked it.
I have a spare 16 GB card if I can recover something that way.
I can't reactivate my old Rezound because now the SIM card is invalid and they are two different sizes so I can't use the new one in the old phone.
1. Bootloader is [still] locked
2. Root has been achieved
Solved the problem. I tried a better micro usb cable and a different usb port.
Everything went great after that. I'm now rooted fully.
daffy113 said:
Verizon Failed on on Odin now stuck at SIII boot screen
I tried the procedure with rooted.system.img and Odin 3.07 and it threw root Xmit Write fail. Then it just hung.
I pulled the battery and now it won't boot. I tried doing Vol Up + Home to do a hard reset to no avail.
I also tried Samsung-Updates.com-SCH-I535_VZW_1_20120705143513_fti2qg2lmf file through Odin with no success.
I've rooted phones in the past but never through this method.
I'm hoping I haven't bricked it.
I have a spare 16 GB card if I can recover something that way.
I can't reactivate my old Rezound because now the SIM card is invalid and they are two different sizes so I can't use the new one in the old phone.
Click to expand...
Click to collapse
..
The answer is that this type of question doesn't belong in the dev threads, but in the S3 Q&A forum. If MD5 doesn't match, then you have a bad download or bad copy, or the posted MD5 is incorrect.
Unable to Root VZW SG3
I have been unable to download the Samsung ADB interface driver for my phone. So I can't root using Debugs ADB root method. Is there something I need to do in order to get ADB installed for my device so it can recognize my phone?
luisdr007 said:
I have been unable to download the Samsung ADB interface driver for my phone. So I can't root using Debugs ADB root method. Is there something I need to do in order to get ADB installed for my device so it can recognize my phone?
Click to expand...
Click to collapse
Download works in Droidstyles guide.
http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
prdog1 said:
Download works in Droidstyles guide.
http://forum.xda-developers.com/showpost.php?p=28530394&postcount=1
Click to expand...
Click to collapse
thanks, but not sure what you mean. i've clicked on the link but not sure where to go. I see the section for windows OS, but not sure what to download.
luisdr007 said:
thanks, but not sure what you mean. i've clicked on the link but not sure where to go. I see the section for windows OS, but not sure what to download.
Click to expand...
Click to collapse
Here is direct link from Samsung.
http://www.samsung.com/us/support/owners/product/SCH-I535MBBVZW
Click see all downloads>software
prdog1 said:
Here is direct link from Samsung.
Click see all downloads>software
Click to expand...
Click to collapse
thank you. i will uninstall the current drivers, reboot, and install these and see what happens.
prdog1 said:
Here is direct link from Samsung.
Click see all downloads>software
Click to expand...
Click to collapse
I tried installing drivers again, but no avail. i keep getting "There was a problem installing this hardware, SAMSUNG Android ADB Interface. This device is not configured correctly. (code 1)" Not sure what else to do.
Did you reboot the PC
prdog1 said:
Did you reboot the PC
Click to expand...
Click to collapse
I uninstalled, rebooted, and then installed new drivers, and still getting that error. I can't seem to figure out what the problem is. I also installed Kies, and SDK, and still can't get to work.
luisdr007 said:
I uninstalled, rebooted, and then installed new drivers, and still getting that error. I can't seem to figure out what the problem is. I also installed Kies, and SDK, and still can't get to work.
Click to expand...
Click to collapse
Need to reboot PC after drivers are installed and make sure usb debug is turned on in phone settings.
prdog1 said:
Need to reboot PC after drivers are installed and make sure usb debug is turned on in phone settings.
Click to expand...
Click to collapse
ok, I did not reboot after I installed drivers. USB debugging is checked on the phone. Let me reboot PC and I will keep you posted. thank you very much for you help with this. I'm not new to rooting, but I am new to the Samsung phones. I've had the DX for the last 2 years, and never had issues rooting or flashing ROMS.
prdog1 said:
Need to reboot PC after drivers are installed and make sure usb debug is turned on in phone settings.
Click to expand...
Click to collapse
So I rebooted and I'm not getting the error. But adb is still not recognizing my device.
luisdr007 said:
So I rebooted and I'm not getting the error. But adb is still not recognizing my device.
Click to expand...
Click to collapse
ADB shows mine as offline emulator.
hey guys i am new to the forums..i have t mobile galaxy s t959v. and its stuck on bootloop. i have tried ODIN to flash it back to stock firmware but it keeps reeboting on vibrant screen over nad over...help me guys...m going out of my mind. also i tried eugene froyo with no avail cnt get past a boot screen. But i can get into download mode. any help would be appreciated.....:good:
The Guide
Read Learn Profit.
Then thank the guy who spent hours(maybe even days) putting that together.
hechoen said:
The Guide
Read Learn Profit.
Then thank the guy who spent hours(maybe even days) putting that together.
Click to expand...
Click to collapse
i saw the guide earlier and it ddint work for me since i cant boot up the phone and update it with kies mini or anything else. any other solution? m going crazy.
What do you mean you can't boot up? You need to be on download mode, or are you telling me that you can't get into download mode?
If you can't get into download mode then you're out of luck.
nemeancestus said:
i saw the guide earlier and it ddint work for me since i cant boot up the phone and update it with kies mini or anything else. any other solution? m going crazy.
Click to expand...
Click to collapse
OK you said in your OP that you can get into DL mode. Follow the second post of that guide for getting Heimdall One-Click up and running. Then flash heimdall per the directions of the guide. You'll want to flash WITH bootloaders. Just relax and read through it. It will fix your problems.
Before you do anything, uninstall Kies Mini and use usbdeview to uninstall android and samsung drivers. Then proceed with Lumins guide. If you DO NOT UNINSTALL DRIVERS I can assure you there is no way to get out of hard brick unless you have a jig.
Tip: Uninstall drivers that has the name Samsung or Android.
th3controller said:
If you DO NOT UNINSTALL DRIVERS I can assure you there is no way to get out of hard brick unless you have a jig.
Click to expand...
Click to collapse
Actually not true. If you use a different USB port then the one the Kies drivers are linked to Heimdall Drivers will install just fine. I've got Odin, Heimdall, and ADB running for two different phones on my laptop. And this guy is soft bricked not hard bricked.
hechoen said:
Actually not true. If you use a different USB port then the one the Kies drivers are linked to Heimdall Drivers will install just fine. I've got Odin, Heimdall, and ADB running for two different phones on my laptop. And this guy is soft bricked not hard bricked.
Click to expand...
Click to collapse
i followed the second guide and got everything right..but when i click flash i get this error/message? ''Local and device PIT dont match and repartition wasnt specified!
Ending session....
Rebooting device....
what should i do???
nemeancestus said:
i followed the second guide and got everything right..but when i click flash i get this error/message? ''Local and device PIT dont match and repartition wasnt specified!
Ending session....
Rebooting device....
what should i do???
Click to expand...
Click to collapse
You sure you have a t959v? Try a different one click from the collection? New to me.
In his op it says it is bootlooping on the vibrant screen. Quite possibly he actually has a vibrant .
eollie said:
In his op it says it is bootlooping on the vibrant screen. Quite possibly he actually has a vibrant .
Click to expand...
Click to collapse
That's what I'm thinking. Or when he flashed with Odin he flashed vibrant firmware to it? Have you ever seen that error before?
Cant say that I have. It could be I havent ever flashed a rom not for this phone.
AdamOutler says one clicks have a safety that keeps you from flashing the wrong software. That might be what is happening. Maybe the op needs to use heimdall-frontend to flash a tar.gz. /shrug.
nemeancestus are you comfortable using regular heimdall? You can flash the files used in the one click with heimdall-frontend. I will link the tar.gz, download it. In heimdall-frontend the first tab will give you the ability to load a package. Browse to the folder you downloaded it in. It will decompress the tar.gz once that is done in the package files pane it will list the files. Once it does that select load it will take you to the flash tab and load the files for you. Now put your phone in download mode and it should show as connected in heimdall. Dont change any of the options set. Just hit flash. After that it should reboot and you will be on stock plus blastoff kernel. You will need to flash a different rom tho wifi does not work and it doesnt have busy box or su preinstalled. Just reboot to recovery and flash a new rom.
The link might not be active yet give it some time I just put it on drop box.
https://dl.dropbox.com/u/10373328/Stock KJ6 + root.tar.gz
hechoen said:
That's what I'm thinking. Or when he flashed with Odin he flashed vibrant firmware to it? Have you ever seen that error before?
Click to expand...
Click to collapse
I think you are right. He probably has the phone but flashed a vibrant rom. He refers to "Eugene's Froyo Rom"
Check the link and forum name.
--------------------------------------------------------------------------------
http://forum.xda-developers.com/showthread.php?t=819047