Related
I am planning on returning this phone because it cannot get to recovery/download mode using the combo keys. When I tried to swap it today, nothing from their stocks worked but the demo unit worked, but they wouldnt swap it with mine.
I understand that it might be a huge problem for me if i cannot get into download/recovery mode right?
Seems to me that te early batches can do this but the new batches cannot. Bell must have done something. But what exactly they have done? Is this software related that Bell did to disable this? Is there no chance at all to flash the device to re-enable it back?
Those who have theirs working, whats the first four five characters of your serial numbers?
Please delete this thread. Didnt realize theres one already
Hi all
I would like to thank everyone in advance and hopefully someone will be able to guide me to resolve my concern, Bell Samsung Vibrant will not go Pass the Galaxy S logo once powered on.
-Was the Phone ever rooted in the past? No, it's less than 2 weeks old, First ever Android, previous Windows mobile/ Iphone User.
-Did I encounter any error? Yes, Invalid or Damaged internal SD, I believe my main mistake was taking the battery off while the device was left powered on. The device was stuck on a loop cycle then after.
-Did I install any Apps on an External SD card? No, never got a chance to.
- Why not save the hassle and just return/ repair phone from your carrier? Unit bought online from craigslist and was not provided with a receipt, Paid a decent price and confirmed IMEI doesn't have any negative file from carrier at the time of purchase.
- Did I contact Samsung Canada at all? Yes and they won't take any accountability as the carrier must follow their own repair/ return process.
Just a Summary of what was done:
Charged and attached for atleast an hour.
- Tested by plugging it to the Wall charger (Device assumed OFF), the screen goes on a loop cycle from the Galaxy S Logo to a blank black Screen back to the Galaxy S logo and so on.
-Attached and tested ALL USB ports (Windows 7 64 bit) and the screen goes on a loop cycle however this time I get a drained battery logo and a stuck time capsule in the middle of the screen.
Downloaded Samsung softwares: Kies_1.5.1.10074_2_6, Kies_1.5.0.10024_74, Kies_1.5.1.10074_45.
-The device only goes on a loop cycle from a drained battery logo back to a black screen while connected to the USB port. It appears the device is not being detected. No visible partnership between Bell Vibrant device and the Kies drivers.
Desperate to attempt anything, I even tried rooting the device by attempting all possibilities to get it to Recovery mode or Download mode however my best efforts did not avail. Before anything was attempted, I confirmed the device was powered off first before taking the battery out.
-Held down the Up volume button and Power button and released the power button only
-Held down the Down volume button and Power button and released the power button only
-Pressed Up volume, Down volume button and Power button and released the power button only
-Held down the Down volume button, Home button and Power button and released the power button only
-Held down the Down Volume button, Home button and Power button and released the Home(middle) button only
-Held down the UP volume button, Home button and Power button and released the power button only
-Held down the UP volume button, Home button and Power button and released the Home(middle) button only
Also downloaded Update.zip and android-sdk_r06-windows.zip
-extracted and confirmed SDK was installed successfully however my device was not detected. Ran from CMD [unable to enable the USB debugging in Applications]
-confirmed the how to steps taken intended for Bell.
Im still optimistic that I can expect the best possible outcome from this situation or I have to hunt down the individual who sold the device
Please verify if I can attempt an alternative or if took a wrong turn with any of the steps mentioned above.
If you live locally in Toronto [GTA] and would like to take on this challenge, Please PM me..
Feel free to drop your comments as to how this issue can be resolved. Please!
Thanks in advance!
Kind Regards,
mamasboy
Update: 3:00am
Hours later and still no luck!
Any ideas how I can approach Samsung Canada directly and have them deal with the situation?
here is a post here on how you can access using something called ADB ? It can be used apparently where the three button recovery can not be entered. Try looking under three button recovery in the search on the forum. Hope this helps.
How i get into recovery mode is by restarting the phone by holding the power button and continuously tapping all 3 Home +power+ vol up at the same time
And if it works it will go into the recovery mode before the screen changes.
see if you can boot into recovery mode
wiki has instruction to get into recovery mode http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/Vibrant_GT-I9000M
once in recovery mode, try the data wipe option, also the cache wipe option
then reboot back to normal
Tehpriest said:
here is a post here on how you can access using something called ADB ? It can be used apparently where the three button recovery can not be entered. Try looking under three button recovery in the search on the forum. Hope this helps.
Click to expand...
Click to collapse
Hey,
The SDK was successfully updated. It downloaded all the new patches and required files, the sdk does work however when I get to the point of:
adb device (Hit enter)
list of devices attached (blank entry)
-even attempted other commands but getting error: device not found
NezumiYaro said:
How i get into recovery mode is by restarting the phone by holding the power button and continuously tapping all 3 Home +power+ vol up at the same time
And if it works it will go into the recovery mode before the screen changes.
Click to expand...
Click to collapse
Hey NezumiYaro,
Thanks for the tip but still no luck
AllGamer said:
see if you can boot into recovery mode
wiki has instruction to get into recovery mode http://forum.xda-developers.com/wiki/index.php?title=Samsung_Galaxy_S/Vibrant_GT-I9000M
once in recovery mode, try the data wipe option, also the cache wipe option
then reboot back to normal
Click to expand...
Click to collapse
Hey AllGamer,
Thanks for the help and I checked the link and reviewed and re-attempted but still to no avail..
I may have the disabled recovery/download mode Bell batch and it seems the only option out of this is to get the device replaced
I had the same problem...Currently Samsung is 'repairing' my phone. Instead of going through all this trouble, I would rather suggest you to go and exchange it.
If they dont replace the phone for you, just call samsung social hub help desk (1-888-751-4078). They will give you a ticket number and then you can send your phone to samsung via any Bell corporate store.
The samsung social hub guy told me that it would take 5 business day to repair but the person at Bell store told me that it can take 2-6 weeks.
I'm in the same boot as you, altough i'm in a different country.
nevertheless, same sh*t
I did however discovered today that when I start the phone, connected trough usb, I does detect what seems to be a part of the phone, have a look at this image (was done on a XP virtual machine, but my WIN7 does the same.
I get a G: and a H: in the device manager.
But I cannot access those, maybe or maybe not, this might be our only hope, before I send it back.
But I refuse to give up (yet)
Exact same problem you had. Phone would not load past Galaxy S logo. I did not hack or root my phone either. Seems this is becoming a larger issue. Recovery mode was disabled on my phone too. It is now with Bell being sent for repair. I would suggest you do the same, I wasted 3 days trying to get the phone into recovery mode to no avail. If Bell has any in stock they may swap for you. They did not when I took mine in unfortunately.
nalinbhatt said:
I had the same problem...Currently Samsung is 'repairing' my phone. Instead of going through all this trouble, I would rather suggest you to go and exchange it.
If they dont replace the phone for you, just call samsung social hub help desk (1-888-751-4078). They will give you a ticket number and then you can send your phone to samsung via any Bell corporate store.
The samsung social hub guy told me that it would take 5 business day to repair but the person at Bell store told me that it can take 2-6 weeks.
Click to expand...
Click to collapse
Wow thanks 5 business days is acceptable. I'm currently back on my Windows Mobile device as a back up phone for now. I will definitely give them a call first thing tomorrow morning!
This is what concerns me going down the road. Any of you recall the Samsung Instict? aka Iphone Killer.. "roll eyes" Could it be that Samsung didn't put enough research and development into the Operating System/ Hardware and deployed the Galaxy S series prematurely? One can only ponder...
To be continued...
nalinbhatt said:
I had the same problem...Currently Samsung is 'repairing' my phone. Instead of going through all this trouble, I would rather suggest you to go and exchange it.
If they dont replace the phone for you, just call samsung social hub help desk (1-888-751-4078). They will give you a ticket number and then you can send your phone to samsung via any Bell corporate store.
The samsung social hub guy told me that it would take 5 business day to repair but the person at Bell store told me that it can take 2-6 weeks.
Click to expand...
Click to collapse
patj3 said:
I'm in the same boot as you, altough i'm in a different country.
nevertheless, same sh*t
I did however discovered today that when I start the phone, connected trough usb, I does detect what seems to be a part of the phone, have a look at this image (was done on a XP virtual machine, but my WIN7 does the same.
I get a G: and a H: in the device manager.
But I cannot access those, maybe or maybe not, this might be our only hope, before I send it back.
But I refuse to give up (yet)
Click to expand...
Click to collapse
Hey patj3, it seems you have a better chance than the rest of us. Attempt to delete or uninstall what you highlighted in yellow, unplug device, reboot computer and before you plug the device, Install the latest kies software from Samsung and allow it to fully install. It's missing drivers and is unable to recognize the unit. search "[GUIDE] ADB, Fastboot, and Nandroid for Noobs" here in XDA.
Good luck, I may be throwing the towel as early as tomorrow
xZeDgEx said:
Exact same problem you had. Phone would not load past Galaxy S logo. I did not hack or root my phone either. Seems this is becoming a larger issue. Recovery mode was disabled on my phone too. It is now with Bell being sent for repair. I would suggest you do the same, I wasted 3 days trying to get the phone into recovery mode to no avail. If Bell has any in stock they may swap for you. They did not when I took mine in unfortunately.
Click to expand...
Click to collapse
Thanks for the feedback..
I know, my mind is about to explode!
Unfortunately, I'm pass the 14 days/ 30 minutes requirement for Bell's D.O.A policy and sending the device out for repair is my only option.
Post back and let us know your repair experience with Bell and their turn around time.
Cheers
Just an update..
I went through the regular repair process, it looks like I'm looking at 3-6 weeks.
Regards..
I had the exact same problem except I rooted it and it was after I applied a lag fix but luckily it wasn't even a week before I got the phone so I just brought it in and bell gave me a new one on the spot lol. Hope you can get it repaired.
The same problem here also. I did not root it or put anything aftermarket. Only unlocked it with a code. Bestbuy did not want to do anything because it is 4 days pass the 30 day mark, not talking about the 14 days 30 min. I spoke to Samsung support and they told me to go to Bell store and have it sent for repair. I did complain to Samsung that it is unacceptable to have a 34 day use of a device and 2 months for repair. Now I am waiting for the superviser of the tech suppoert to call me by the end of the day today, but no news from hem yet. Tomorrow first thing in the morning I am calling again Samsung to look for the superviser of the superviser.
P.S. Bell did not ask me for an account number of phone number with them. Only took $47.00 in case if there was a water or mechanical domage. It is refundable.
mamasboy32 said:
Thanks for the feedback..
I know, my mind is about to explode!
Unfortunately, I'm pass the 14 days/ 30 minutes requirement for Bell's D.O.A policy and sending the device out for repair is my only option.
Post back and let us know your repair experience with Bell and their turn around time.
Cheers
Click to expand...
Click to collapse
thats the refund policy. doa is 30 days on the spot replacement as long as it says i9000m on the logo before it gets stuck.
Idan73 said:
thats the refund policy. doa is 30 days on the spot replacement as long as it says i9000m on the logo before it gets stuck.
Click to expand...
Click to collapse
What if they dont have it in stock?
That was case with me,
so i went to another bell corporate store,
they send me away, claiming that only the place you got it from can replace it.
its been now 20 days with the phone, and the guy (bell corporate location) does not have it in stock,
he says he does not know when he can get it.
so i dont know if there is truly a shortage, but that is what they are telling me.
help.
if it makes you feel any better
I've had one on order through my corp plan at work for over a week, usually if quantities are low it will say so on the ordering site, or it will say on backorder, well it didn't, they don't have them, supposed to get a shipment this week, shipment hasn't arrived yet.
this will be my 2nd crack at a Vibrant, the first one was riddled with small yet important issues as well as the GPS didn't work. Hoping for a better one this time, if not I'll try and get a 'Desire Z' down the road.
Neil
I was playing around with the pattern lock and eventually got the 'Too many pattern attempts!' message, with it asking for my Google username and password to log in.
No matter what, it doesn't accept my username/password. I am 100% sure I've typed it in correctly.
This bug has been around for over a year with many people reporting 'bricked' phones without even doing anything particularly naughty with their phones.
This is the Google bug that has been posted on it: http://code.google.com/p/android/issues/detail?id=3006#makechanges
As you can see this has been around for over a year. The 'null'-in-password trick doesn't work, nor does the spamming-home-button trick.
My phone is rooted and with the Voodoo Lagfix-only custom kernel. Any suggestions?
Do a hard reset / wipe. That's my suggestion.
Try booting into recovery (Home Button, Vol Up + Power), and resetting your cache and wiping it. Then try logging in with your Google account. If all else fails, try changing your Google password on the PC then logging in on the phone. And then if it still fails, looks like you need to flash the phone again. Next time, don't enter the thing wrong! Stop rushing haha .
I wasn't rushing, I was playing with the lock. It takes about 30 times before it's permanently requiring the username/password. But really...you can't blame me for not expecting this. :/
I'm currently trying to flash a new ROM but I've run into another problem - I can't get it to boot into downloader/recovery. It's not the lack of the 3 button combo - I've managed to reach Recovery and Downloader ONCE each in the past, but never again since.
And now with all my efforts to boot into recovery/downloader, it now cannot boot into normal usability mode (or in my case, locked mode). Instead, the Galaxy S logo loops endlessly.
Sigh.
Have you read the thread for the fix for Galaxy S variants that are lacking the 3 Button Combos? It's in Android Development. Maybe try that? Or, can you still connect the phone and connect with Kies?
I can't turn on the phone anymore, meaning no changing to USB debugging etc. And I'm having problem accessing recovery/download, even though I definitely HAVE done each of them once before and therefore do not have the 3 button problem.
Without turning on my phone, Kies can't detect it
So what happens when you power on?
Now, it shows the first Galaxy S splash screen, then shows the boot logo, then nothing. The boot logo continues to glow endlessly.
Be patient, i waited up to five minutes. If you see the s logo glowing/shining youare ok
Sent from my GT-I9000 using XDA App
okpc said:
Be patient, i waited up to five minutes. If you see the s logo glowing/shining youare ok
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Yeah it's continuously shining. Haven't left it for up to five minutes though... And even then it probably won't help since I'm still locked out of the phone, and unable to access download/recovery mode to reflash it.
After waiting for a long time, the logo disappears, screen goes black. Menu and back buttons light up. Nothing else.
Looks like your going to have to reflash your phone again. Download the desired firmware, open up Odin and put your phone into download mode and start the flashing procedure. Be more careful next time.
PaulForde said:
Looks like your going to have to reflash your phone again. Download the desired firmware, open up Odin and put your phone into download mode and start the flashing procedure. Be more careful next time.
Click to expand...
Click to collapse
Good advice considering he said his 3 button combo stopped working =))
All I did when I got that black screen was adb reboot recovery and wiped and phone bootedup fine. But only if you have debuging enable and and sumsung drivers. Hopes this help.
Sent from my SGH-T959 using XDA App
Can't enable USB debugging when phone can't be turned on at all.
danamoult said:
I was playing around with the pattern lock and eventually got the 'Too many pattern attempts!' message, with it asking for my Google username and password to log in.
No matter what, it doesn't accept my username/password. I am 100% sure I've typed it in correctly.
This bug has been around for over a year with many people reporting 'bricked' phones without even doing anything particularly naughty with their phones.
As you can see this has been around for over a year. The 'null'-in-password trick doesn't work, nor does the spamming-home-button trick.
My phone is rooted and with the Voodoo Lagfix-only custom kernel. Any suggestions?
Click to expand...
Click to collapse
Ok i did the same thing, and spent hours googling.
Tried the key combinations to restore, but never worked.
Heres what worked for me, but, be warned all your contacts will be lost if stored on the phone.
From another phone, call your locked number.
Answer it on the locked phone, then hit the "back" button.
This gives you full access to the phones menus etc.
Hang up on the phone you called from.
Now, go into Applications / Settings / Privacy / Factory Data Reset.
This worked for me whereas all other methods did not.
Once your phone is up and running again, be sure to create your google account on your phone.
That way your protected again. If you didnt previously have the account set up from your phone, like i didnt, then you cannot log in of course.
This works...give it a try. Hope it helps.
danamoult said:
Can't enable USB debugging when phone can't be turned on at all.
Click to expand...
Click to collapse
you need to be able to enter recovery mode for you to solve this problem
danamoult said:
I was playing around with the pattern lock and eventually got the 'Too many pattern attempts!' message, with it asking for my Google username and password to log in.
No matter what, it doesn't accept my username/password. I am 100% sure I've typed it in correctly.
This bug has been around for over a year with many people reporting 'bricked' phones without even doing anything particularly naughty with their phones.
This is the Google bug that has been posted on it: http://code.google.com/p/android/issues/detail?id=3006#makechanges
As you can see this has been around for over a year. The 'null'-in-password trick doesn't work, nor does the spamming-home-button trick.
My phone is rooted and with the Voodoo Lagfix-only custom kernel. Any suggestions?
Click to expand...
Click to collapse
dear friend dont worry or panic... i'll tell you a trick , go to the samsung customer care and tell them that your phone gets heated up very often and today it just refuses to boot up normally...
since your device cannot get into recovery mode or download mode the company will never know that you had played with the system files in the device or not... (rooted )..
since the samsung people will also try to get your device in recovery mode.. but when it will not go to the recovery mode you will get a mother board replacement under warranty.....
this heating up of the device is a common problem in the galaxy here in india.. so use this excuse and i know it works 100% ... (just dont tell them that you had rooted and lagfixed your device )
What you describe sounds like a very large security hole if I am reading it correctly.
Are you saying that even if your phone has been locked out from too many lock screen failures, that just answering an incoming phone call gives you full access to the phone? Really?
I just checked on my phone and while I can answer an incoming call while the screen is locked, if I hit the back button or menu button, I just get the lock screen.
I'm missing something here...
OzzYGuY said:
Ok i did the same thing, and spent hours googling.
Tried the key combinations to restore, but never worked.
Heres what worked for me, but, be warned all your contacts will be lost if stored on the phone.
From another phone, call your locked number.
Answer it on the locked phone, then hit the "back" button.
This gives you full access to the phones menus etc.
Hang up on the phone you called from.
Now, go into Applications / Settings / Privacy / Factory Data Reset.
This worked for me whereas all other methods did not.
Once your phone is up and running again, be sure to create your google account on your phone.
That way your protected again. If you didnt previously have the account set up from your phone, like i didnt, then you cannot log in of course.
This works...give it a try. Hope it helps.
Click to expand...
Click to collapse
distortedloop said:
What you describe sounds like a very large security hole if I am reading it correctly.
Are you saying that even if your phone has been locked out from too many lock screen failures, that just answering an incoming phone call gives you full access to the phone? Really?
I just checked on my phone and while I can answer an incoming call while the screen is locked, if I hit the back button or menu button, I just get the lock screen.
I'm missing something here...
Click to expand...
Click to collapse
chill my dear friend.... it cant be true.... its just his 1st post.. and samsung cannot be so dumb to leave a password protected keypad that can be cracked so easily.. even i tried the back key on a call with a password lock.. i cannot get passed the lock screen....
Firstly, may I apologise, I know this has been covered, I've trawled the internet for hours but just can't seem to get an answer.
I recently updated my UK, unlocked Galaxy S to Froyo via the registry hack, all was fine (ish). Because Froyo had been delayed in the UK and wasn't as great when it was running on my phone I thought it would be safer to revert back to 2.1 and wait until the official UK release came out (I know some will ask me why I did this, I just felt that Froyo was held back for a reason and I couldnt get an answer as to if I could update to the UK version if I already had the Scandinavian one). So I did the reg hack again and was offered 2.1. Everything seemed to go smoothly until the phone rebooted after downloading from Kies. Now the phone's animation starts then the flashing S symbol displays for an extended time. After that, the screen goes black. If I touch the two touchscreen buttons they stay on but do not go off. If I hold the power button the phone turns itself off and when the phone is powered off and I plug it into my PC with a USB, the battery charging sign comes on.
The phone was rooted and I did have the OCLF on but uninstalled that and un-rooted before changing the firmware so it was back to stock.
Before I get 20 people telling me to put the phone in download/recovery mode I must tell you that I can't. My phone has never been able to do it. I've tried every single way and button order suggested. I'm not the only one who's phone won't do it either so it's not just me. The only way I ever saw recovery mode on my phone was when I used the one click root on the PC.
I'm at a total loss. Debugging was turned off because Kies won't let you do anything with it turned on and so ADB recovery is out also.
Please help if you can.
Many thanks,
Ryan
Boot to download mode, do a repartition with Odin and 512 pit flash, remove battery and boot again to download mode and then do a odin firmware flash to which ever firmware you want.
thanks intratech but I can't boot the phone into recovery or download mode (sorry should have stated that). Believe me, I have tried every combination. I did a lot of research and discovered that there are quite a few people for whom that feature was disabled.
if the 3 button combo is not working on your phone, you should not do these risky stuff actually
take a look at this thing
http :/ / forum.xda-developers.com/showthread.php?t=819551
remove spaces
thanks Noobproof. I remember coming across that thread last night. Although I consider myself ok with software, soldering and slicing just isn't my forte. I haven't got a clue about soldering, etc. I've just come back from the Carphone Warehouse (Samsung suggested I go there as they are the service centres listed on the Samsung UK website). The engineer had the phone for half hour and said that the "board was faulty". Haven't got a clue what he meant by that, unless he meant the internal SD which a few people have had go on them. Anywho, he told me to ring Samsung and send it in for a repair. I did that and need to send my phone special delivery to a company called regenersis in Scotland.
I knew rooting and flashing custom roms was a risk, that's why I never touched Odin,etc. I used Kies to upgrade to Froyo and Kies to downgrade back to Eclair. You would think that sticking to official Samsung software would be safe. I must admit, when it was going well I loved my Galaxy but more and more I'm starting to wish I'd opted for the Iphone.It just seems that there have been so many glitches and bugs, I mean, why should there ever be a need for lag fix in the first place? I often found myself keeping my fingers crossed when downloading simple apps as that was usually touch and go!
Feeling a bit deflated now. Was hoping some clever boffin had designed a software solution that would recognise the phone and force it into download/recovery mode.
Ah well, thanks for taking the time to respond anyway.
Best wishes,
Ryan
You know i was very happy when i for the phone for the first time and while i was doing a research (i live in turkey and there is no stock android market here) i came along this forum. And i have learned that i havent got the 3 button combo. I downloaded the 3 button fix abd took the phone to samsung centre.
They told me that they cannot flash it and i made a huge fight then they accepted and i have my 3 buttons. Never give up your phone. I dont think the internal sd is faulty it is just corruppted if you can access the recovery menu you could fix it. Any way you have to find a service centre that has an anyway jig box other a jtag box otherwise they will have to replace the motherboard. Good luck
Sent from my GT-I9000 using XDA App
I had the same problem all i did was use a different firmware .. didnt choose anything in pitfile and did not check on repartition but checked only F reset and Auto reboot and flashed my phone and voila it booted perfectly fine
Hope it helps others with black screen problem after booting
thanks
mike
I had the same problem too. This method really works.
Wysłano z GT-I9000 z użyciem Tapatalk
so, i've been using xda for a while now and i would like to start thanking all the contributors and the nice android community there is.
today i'm posting my 1st post and it's not for good reasons...
i got my sgs [i9000 international] on september and i have to say it has been nothing but problems.
it was working ok but then came along the 1st issue - unable to receive text messages. it would just stop to receive them and i would have to place the sim card on another phone receive the 50 sms or so i was supposed to have been receiving and then place the sim card back on the sgs and it would be fine for 5 days or so and the problem would begin again and i must say walking around with 2 mobile phones is just stupid when i only need 1...
in order to solve this and some other lags the phone had i decided to update to 2.2. in portugal there's no official update in kies (at least for me...) so i decided to go custom rom. i went with doc's rom BUJP8 V9.0.1 non-wipe and then voodoo's lag fix and i finally had the mobile phone i always wanted. then came along another issue - unable to receive phone calls (it doesn't receive sms and phone calls, what kind of a mobile phone is this?!). when someone is calling me, the phone lights up, it says there's no network available, it regains the signal and i don't even know who called!
now, i don't know what to do, i have a sgs that just doesn't work and i don't know what i'm supposed to do. this thing cost me a lot of money and i just don't want to waste it, all i really want is a proper mobile phone, i want the sgs!
i would appreciate any help, tell me if i've done something wrong, what i can do to have this working.
thanks in advance
~galaxydroids
ps: sorry for the english, as i've said i'm from lisbon, portugal
the attachment shows the sgs info after the custom rom flash
Sounds really weird indeed.
Have you tried hard-reseting your phone?
Does it still do the same after a hard-reset?
Maybe there is something wrong with the phones hardware it you keep loosing signal, where other phones works perfectly.
I would say, try putting in stock ROM (2.1 for Portugal?) and see it the problems still occur. If they do, maybe you should send it in for repair.
so i was kind of avoiding the hard reset but went for it.
now the phone is...well... isn't. it did everything, rebooted and now the two led buttons are lighted up and the phone randomly vibrates. that's it. it's been like this for quite some time now. is this supposed to happen?
Mine started to do that after a reboot also I just reinstalled the rom and its working for now.
Sent from my GT-P1000 using Tapatalk
how did you reinstall the rom? i can't even connect it to the computer...
Using download mode, I guess...
yeah well i can't get into download or recovery mode, neither one of them, i've tried all the combos with the keys...
if i'm unable to get into download mode how can i use odin?
my guess is that your problem might be due to your carrier... I don't know over there in portugal, but I've always heard vodafone isn't very good....
I have same phone, international version, bought on sept. mine came from handtec.co.uk...
if your phone is like mine, you should be able to enter download mode, just hold down the volume down key + home key + power key.. in that order, you should see your phone boot to download mode.
Hope it helps