Hi,
Something strange happened with my phone yesterday and I think it is worth sharing.
The Problem: I have an old USB JIG I made by myself about one year ago for using it with the Samsung Galaxy S (GT-I9000), it works like a charm for entering into download mode. But when I bought the SGS2 (GT-I9100) I noticed it didn't work, so I searched the forum and read that the new bootloader prevents it from working and erasing flash count or removing the infamous yellow triangle.
I know this have been addressed by other means. But yesterday my phone started acting weird and it turned out to be a problem in the phone's USB port making some sort of short circuit (Explanation in this thread, I'm not the only one: http://forum.xda-developers.com/showthread.php?t=1216163).
The funny part is that, when the phone was not working well, I had to remove the battery because it was unusable. And when I put the battery back, withouth touching any button, the phone started on download mode with a legend saying that the flash count has been erased, I rebooted the phone and the yellow triangle was gone also!
The point of my post is that something in the USB port made the phone think it had some kind of JIG connected which told it to erase the flash count and start the download mode. So I've come to think that there has to be another version of the USB JIG that works with out phone in the latest bootloader version!
I'm not very good with electronics, so I cannot investigate any further, but I leave my doubt in the community just in case someone wants to do some more research.
Hint: When this happened, the phone kept showing the car home icon in the status bar as if it was connected to some kind of dock
I hope this helps!
What rom were you and and did you flash the old bootloader at any time since you were using your phone?
yeah the old jig only took my phone to down mode thts it,but yes defo the fun i had is sparking the pins like wires + an _....lolyes i think ur right ,thers gota b an otha verson
bpivk said:
What rom were you and and did you flash the old bootloader at any time since you were using your phone?
Click to expand...
Click to collapse
I9100UHK1 - Latest 2.3.4 unbranded for my country, the old JIG we all know doesn't work and no, I've never flashed the old bootloader, I was staring to become friends with the yellow triangle until it faded away
Flash the old bootloader, use the jig, flash the new bootloader again if you need to. Simple.
However, I recall seeing posts on here in November/December about a new USB jig that worked with the new bootloader. Don't know how that ended up or whether anyone had gotten hold of one of these (if they exist).
Edit to add - I've just sent the person I was discussing this 'new jig' with a couple of months ago a message to see if these things exist or not. I'll post here when I know either way.
MistahBungle said:
Flash the old bootloader, use the jig, flash the new bootloader again if you need to. Simple.
However, I recall seeing posts on here in November/December about a new USB jig that worked with the new bootloader. Don't know how that ended up or whether anyone had gotten hold of one of these (if they exist).
Edit to add - I've just sent the person I was discussing this 'new jig' with a couple of months ago a message to see if these things exist or not. I'll post here when I know either way.
Click to expand...
Click to collapse
I know that flashing the old bootloader works, but the point of the thread is precisely that there must be another version of the JIG because the phone reseted the flash counter by itself because of the USB port problem, even though it has the new bootloader
using same firmware some time ago when i bought my phone, i try to use usb jig with the new bootloader, but never happened what you said to me, i have to flash the oldbootloader, but if you're not the only one, that,s strange
I think noone understands. He managed to see the factory mode screen and erase the counter while having the new bootloaders (without a JIG, maybe shortcircuit). Can we suppose that a different JIG can activate this with the new bootloaders?
Edit: Sorry, MistahBungle seems to get it
tsinc said:
I think noone understands. He managed to see the factory mode screen and erase the counter while having the new bootloaders (without a JIG, maybe shortcircuit). Can we suppose that a different JIG can activate this with the new bootloaders?
Edit: Sorry, MistahBungle seems to get it
Click to expand...
Click to collapse
Exactly! maybe I didn't manage to give a good explanation.
By the way, I've seen that screen three different times while the problem on the phone existed, so It's not just a concidence, there HAS to be a new JIG version, we just need to figure out. I'm guessing that we need to short circuit some cable with resistors like the original JIG, maybe a different resistance is needed?
New JIG
I remember over-reading a conversation between Odia ( I think) and someone regarding a resistance-switching JIG that can erase it, but I never caught what exactly was required.
If we can find out I'd like to make one, I might have a play with some rheostats later and see if I can figure it out.
May also have something to do with the order things are done as well. The OP inserted the battery at the time the reset occurred. Maybe switching off alone is not enough but a new jig needs installing with the battery out, then the battery replaced.
Sent from my GT-I9100 using Tapatalk
alias_neo said:
I remember over-reading a conversation between Odia ( I think) and someone regarding a resistance-switching JIG that can erase it, but I never caught what exactly was required.
If we can find out I'd like to make one, I might have a play with some rheostats later and see if I can figure it out.
Click to expand...
Click to collapse
That conversation will help you.
pulser_g2 said:
That conversation will help you.
Click to expand...
Click to collapse
Basically this is what I remember when a firmware is being flashed the USB cable should have the same resistance on the same pin as the jig now.
Sent from my GT-I9100
OK. Allegedly (and I can't emphasise this enough), this works with the 'new' bootloader on the SGS2. Yes, I realise the description/title says I9000, I'm just relaying what I was told by someone else (who hasn't bought/tried one of these BTW).
I guess it's a case of who in this thread can't be arsed flashing the old bootloader or using Triangle Away & wants to fork out 2.5 quid to test it out.
pulser_g2 said:
That conversation will help you.
Click to expand...
Click to collapse
It was Chainfire and Odia in CF's TriangleAway thread, but neither of them actually mentioned what it was, just at hint at it.
Anyone care to share?
MistahBungle said:
OK. Allegedly (and I can't emphasise this enough), this works with the 'new' bootloader on the SGS2. Yes, I realise the description/title says I9000, I'm just relaying what I was told by someone else (who hasn't bought/tried one of these BTW).
I guess it's a case of who in this thread can't be arsed flashing the old bootloader or using Triangle Away & wants to fork out 2.5 quid to test it out.
Click to expand...
Click to collapse
I have one of those cables and can confirm, it does NOT work on the new boot loader.
Thanks That rules that bit of kit out then.
mrm1 said:
I have one of those cables and can confirm, it does NOT work on the new boot loader.
Click to expand...
Click to collapse
I suppose by using mobile odin to flash we'll never need a jig again?
Sent from my GT-I9100 using xda premium
rwc3b said:
I suppose by using mobile odin to flash we'll never need a jig again?
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I guess with chainfires hot fix you would not need mobile odin or jig ... if sammy keeps as they are in there future releases of ICS
Just to clear things up
The original JIG does not work on the latest bootloader. My state is that there may be a new version of the JIG which may work based on what I've found.
I know there are many methods like flashing the old bootloader, using Triangle Away, or flashing by mobile odin, I just opened this thread in order to share something I have found by mistake on my phone and maybe useful for others.
When I first made the JIG for the original SGS was because the device had download mode disabled and the only way to access it was by calling 'adb reboot download'. But then a flashing procedure failed and all that could save the brick was the JIG. I know this is not the case with the SGS2 but I thought it may be interesting to share and investigate
Related
I know there are various threads like this one but my situation is a bit different. I tried using odin to clean install 2.2 to then use the custom rom epic experience. I attempted to install 2.2 using odin but it would get stuck in "setup connection" and I would have to quit and try again. Last time I tried my phone got the "phone connection caution computer" icon and to get into recovery I would have to hold the power and camera button, not the volume down button. When I go to try and install things straight from my SD card I would get an error like "status 7" cus I didn't have the sprint apps to install 2.2. I believe I get these errors installing straight from the card cus I rooted my phone, modifying the kernal cus I read somewhere because when trying to update, it tries to verify but can't cus things are missing or edited cus of the root. I can't try to use odin again because my computer can't recognize the phone anymore regardless reinstalling the samsung drivers. SOOOO, I'm basically ****ing stuck for sure I think. The way I access the SD card is by using an adapter. The only way I see this working is if I find a fix using the SD card, but it's looking slim cus of the stupid root.
I don't know much about this yet, as I'm still learning myself. Did you try using another usb port and are you putting the phone in download mode?. Restart the computer and the phone. Make sure odin is running before you plug in the phone as well. And try another usb port. Are you using the cable that came with the phone? That one trends to have problems for some people.
Edit: I don't believe your phone is bricked either, people tend to throw the word around to much because that arnt quite sure about the definition. Just hang in there and the community will help you get back up and running. Good luck
Sent from my shoe, I mean....Epic shoe... I mean Samsung Epic!
mxcoldhit said:
I don't know much about this yet, as I'm still learning myself. Did you try using another usb port and are you putting the phone in download mode?. Restart the computer and the phone. Make sure odin is running before you plug in the phone as well. And try another usb port. Are you using the cable that came with the phone? That one trends to have problems for some people.
Edit: I don't believe your phone is bricked either, people tend to throw the word around to much because that arnt quite sure about the definition. Just hang in there and the community will help you get back up and running. Good luck
Sent from my shoe, I mean....Epic shoe... I mean Samsung Epic!
Click to expand...
Click to collapse
You see, I'm out of options. Last thing I thought of was installing a custom rom 2.1 rom cus 2.2 roms need odin, but I try to install and I get a signature error or whatever. I'm about to throw the phone against the wall, crack the screen, and use my warranty and get a new phone cus I literally tried EVERYTHING. I spent my ****ing 8 hours of my saturday trying to fix this.
Try a different computer my new Dell XPS 9100 will never reconize my Epic, however, my wifes laptop will always reconize it. I know that sounds weird, I always thought I had a poblem with my phone but it ended up being my computer.
Sent from my SPH-D700 using XDA App
cbpagent72 said:
Try a different computer my new Dell XPS 9100 will never reconize my Epic, however, my wifes laptop will always reconize it. I know that sounds weird, I always thought I had a poblem with my phone but it ended up being my computer.
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
omfg, I used my mom's lappy and the drivers worked. Meaning I can try and use an odin fix.
Odin can be tricky to use because of a few factors other than itself. 1) if you can, use a deskto pc and attach to a usb port literally on the motherboard, no front or pci, this may work, but this I what I found (reading countless threads) to be the most failsafe for everyone. 2) your sammy usb cable is for charging or non critical data transfer ONLY, as it is garbage... repeatedly proven in the threads. 3) reboot pc and phone, boot phone into download mode, (hold down 1. On physical keyboard and press power... DO NOT CONNECT YET! Start up odin, place files where needed (.pit, etc...) uncheck all but what you're told in the flashing instructions with the file you're flashing, most have awesome detals, but sometimes your little issue is resolved on page 50 of the thread... not in the OP. Ok so now plug in the usb connection, odin should find it. If it doesn't, search for drivers, uninstall, reinstall start over, OR you have a bad connection, refer back to usb port and cable. I have 1 out of 4 mobo usb ports that the drivers will maintain a connection to, so try another. Then, once odin has a connection, make sure you're following the guides to the T (and read all the posts)... after that, odin is your best friend. The problem lies elsewhere... odin is the goods. If you have run into problems maintaining connection, and plan to re-root, read all the one click posts and if it drops connection a lot, enter the commands in one by one, repeat if one fails till it sticks. There are way better guides, but you seem to have run into the same issues I did, and after hours and hours, I got that scary ass reconnect me now screen. Just read the whole threads, and if your problem hasn't already been resolved, post in the appropriate thread, so others may learn from your discoveries!
Don't give up, once you figure out the quirks of the relationship between your pc and phone, and of course meticulously follow instructions, your elation when successful will make you forget that pesky 'bricked' screen... trust me I got it too, and no matter how much everyone says you can't brick these following instructions on here... its still scary till it all works. If things are wonky, wipe, go back to DI18 and start over... or just sit tight for froyo roms... good luck!
Oh, and sorry for no links, but it would seem you've probly already read em all... not sure I can do links...
Maybe its just my eeepc that doesn't like the drivers, good luck! Sounds like you're on the way... oh don't forget with the drivers to let em install on connect, leave it plugged in for like 10 mins, unplug, it will then complain it wasn't done, reconnect, then after that finishes, reboot. Crazy drivers...
At least I got a computer recognizing my phone, so I can try and use odin. I've been trying to use this fix
http://forum.xda-developers.com/showthread.php?p=9755894#post9755894
and so far odin has been stuck at this one step "file analysis..."
Yeah I used that method to no avail, but it was about 3 pasts old at the time, so I figured id try
something more stable. Tried a couple dk17 roms, then went back to 2.1 and am now using syndicate xtreme. Id suggest going back to DI18, then go from there. Let me check for another post of mine, theres a dialer code I had to do too at one point...
Ok when doing one click root, someone suggested ##8778# in the dialer, then keyboard enter, then set UART to pda not modem. This and removing comodo firewall, all the sudden my intermittent connection was solid. Not responsible for what this does, but it worked for me. Never found out what it does..... still curious. So this may help you even in odin, try to flash di18 after doing this, then the all in one rom you're looking at...
Oddly enough, I managed to semi-brick my phone several hours ago - my wireless adapter was on the same USB header, and both the wireless adapter and the phone crapped out while trying to flash with Odin.
Thankfully I was still able to get into download mode, and plugging the phone into a different USB port worked fine.
After some more research, about 10 hours of it, odin finally cooperated with me after I downloaded about every kind of file that could make my phone work and finally got it into 2.1
I first flashed the stock kernal to get it working, then flashed stock 2.1
Now I'm that my phone isn't rooted anymore I tried installing 2.2 through the recovery menu and I still get error status 7. Any ideas?
Probly best to post in the thread for the package/rom you are trying to install... others using it should be able to help... or you can do a 2.1 rom and wait for a final froyo based rom... glad to hear you're not bricked... the only way I've heard you can absolutely do that with these is installing a GSM rom or something crazy like that... but non-functional phone is scary regardless...
ungovernable1977 said:
Probly best to post in the thread for the package/rom you are trying to install... others using it should be able to help... or you can do a 2.1 rom and wait for a final froyo based rom... glad to hear you're not bricked... the only way I've heard you can absolutely do that with these is installing a GSM rom or something crazy like that... but non-functional phone is scary regardless...
Click to expand...
Click to collapse
Alright I completely fixed my phone. After I rooted my phone on 2.1, I then used odin v1.6 to install the froyo .tar file into pda and it worked. I then rooted it again so now I'm back to normal. Honestly, I did so many things I forgot what I did but I now have my phone functional. Thanks for help everyone, I greatly appreciate it!
Okay so - recently my I9000m went into a boot loop (during normal use - though I did have voodoo installed) and I can not access recovery mode. I could however access download mode.
I attempted to install stock firmware from samfirmware - no luck.
I attempted to install stock firmware from the forums - no luck.
I attempted to install EZBase - no luck.
I even attempted to use Virniks 'stock everything' tutorial - no luck.
After all these attempt and various other attempts involving 3 button fixes I was still having boot-loops.
So I got desperate - and I installed the Odin One Click for captivate - I know...bad idea but like I said.. I was desperate.
Now my i9000m (bell canada) starts up with the AT&T Logo and then boot loops!
The worst part is I can't even access download mode anymore! I understand that this is probably due to the fact that the buttons are remapped - keeping that in mind I tried as many key combos as I could but still get nothing but the AT&T Logo looping over and over.
So to the point.. does anyone have a surefire way to get to captivate download mode on a I9000M?
I've read about the JIG solution but I'll use that as a last resort as I would have to order the pieces (I'm not much of a solderer).
So are there any non-JIG solutions to get back to download mode/restore my phone?
All input is appreciated and I'd like to thank everyone that has tried to help me these last couple of days!
Sounds like your internal SD card is dead.
I was having similar issues where the phone would just bootloop. I re-flashed 4-5 different stock roms which all did the same thing. One of the stock roms allowed me into recovery mode, which yielded no success only a no sd card message.
I have gone ahead and sent my phone out to Bell for repair.
Viper717 said:
Sounds like your internal SD card is dead.
I was having similar issues where the phone would just bootloop. I re-flashed 4-5 different stock roms which all did the same thing. One of the stock roms allowed me into recovery mode, which yielded no success only a no sd card message.
I have gone ahead and sent my phone out to Bell for repair.
Click to expand...
Click to collapse
I'm thinking of doing the same (bringing it to bell) though I'm not sure they'll honor the warranty with it booting up with the AT&T logo, hah :<
Yeah i dont think they would service that, i was fortunate enough to get back a stock i9000m rom so it still boot up with that.
You can try contacting samsung directly to see if they will be able to repair for you, or try the jig and re-flash to stock bell rom
Viper717 said:
Yeah i dont think they would service that, i was fortunate enough to get back a stock i9000m rom so it still boot up with that.
You can try contacting samsung directly to see if they will be able to repair for you, or try the jig and re-flash to stock bell rom
Click to expand...
Click to collapse
Called samsung last night - they said I have to bring it to bell first.
Worst case scenario I'll pay sammy to fix it =/
Update: Just got off the phone with Bell, described my problem, said that I messed with the software real hard and they said that as long as I didn't remove any warranty stickers I'll still be able to get it fixed by samsung foh freeee.
Viper717 said:
Sounds like your internal SD card is dead.
I was having similar issues where the phone would just bootloop. I re-flashed 4-5 different stock roms which all did the same thing. One of the stock roms allowed me into recovery mode, which yielded no success only a no sd card message.
I have gone ahead and sent my phone out to Bell for repair.
Click to expand...
Click to collapse
I have urgued him to flash any SGS firmware with recovery image, but he didn't listen.
And yes, I think that his internal storage bus is dead.
If so, he should write down IMEI of his phone, and send email to the Samsung Korea with the info, that his internal SD card is dead. They will send him brand new phone.
But in the case he would rather use warranty service of his provider, he will need to:
a) try reboot with adb, and fastest as he can, try to issue "reboot download" command with it
OR
b) make JIG, and reboot to download mode, and reflash stock ROM
Asking Samsung Korea for new phone with IMEI sent to them do not require any of above...
EDIT: I have missed your last reply. Good to know, that Bell will fix it for you. But I do not think that they will be able to fix it. They will more likely give you new phone.
Virnik0 said:
I have urgued him to flash any SGS firmware with recovery image, but he didn't listen.
And yes, I think that his internal storage bus is dead.
If so, he should write down IMEI of his phone, and send email to the Samsung Korea with the info, that his internal SD card is dead. They will send him brand new phone.
Click to expand...
Click to collapse
I did listen - no matter how many times I tried to flash the sgs firmware w/ recovery image it would just keep booting and wouldn't enable the functionality.
As i detailed above I tried several recommended methods to re-enable the recovery mode and none of them worked.
Thanks for your help - hopefully Bell honors what they said on the phone.
Sozage said:
I did listen - no matter how many times I tried to flash the sgs firmware w/ recovery image it would just keep booting and wouldn't enable the functionality.
As i detailed above I tried several recommended methods to re-enable the recovery mode and none of them worked.
Thanks for your help - hopefully Bell honors what they said on the phone.
Click to expand...
Click to collapse
OK. Just do not panic :-D
You will get your phone back, more likely new one.
And on other hand, this result is not your fault. Some "first-line" SGS phone models has been faulty. You are not the first one with such problem.
Virnik0 said:
OK. Just do not panic :-D
You will get your phone back, more likely new one.
And on other hand, this result is not your fault. Some "first-line" SGS phone models has been faulty. You are not the first one with such problem.
Click to expand...
Click to collapse
They said they would send it to Samsung and give me a loaner until mine is back.
Not sure if they'll still honor it when I show up in person...but I'm hoping for the best.
So to give a final update:
After a couple commutes back and forth to the Bell store and a couple phone calls to Samsung it looks like I voided the warranty and I'm SOL on getting this phone repaired.
The (semi)bright side of the story is that I have an insurance policy with Bell and I'm getting a brand new SGS for $150.
Sozage said:
So to give a final update:
After a couple commutes back and forth to the Bell store and a couple phone calls to Samsung it looks like I voided the warranty and I'm SOL on getting this phone repaired.
The (semi)bright side of the story is that I have an insurance policy with Bell and I'm getting a brand new SGS for $150.
Click to expand...
Click to collapse
Little too much for a few hours of your time. If you'd reflashed stock ROM and ignored vibrant fw, as I've suggested, they would have no chance to find out what happened, and you've been given new phone for free. But you were in a hurry. Besides, your second, but in the circumstances of your haste not important misstake was, that you've told them what you have done.
Sent from my GT-I9000 using XDA Premium App
Virnik0 said:
Little too much for a few hours of your time. If you'd reflashed stock ROM and ignored vibrant fw, as I've suggested, they would have no chance to find out what happened, and you've been given new phone for free. But you were in a hurry. Besides, your second, but in the circumstances of your haste not important misstake was, that you've told them what you have done.
Sent from my GT-I9000 using XDA Premium App
Click to expand...
Click to collapse
Exactly what I thought...you gave them extremely obvious reasons to put you at fault when you could have easily gotten a free replacement out of this. Don't answer questions that aren't asked
My father's I9000M had a failed SD and I got it replaced for free. Ironically his had a single ROM flashed on it and mine has had over 100 and been 100% fine.
chambo622 said:
Exactly what I thought...you gave them extremely obvious reasons to put you at fault when you could have easily gotten a free replacement out of this. Don't answer questions that aren't asked
My father's I9000M had a failed SD and I got it replaced for free. Ironically his had a single ROM flashed on it and mine has had over 100 and been 100% fine.
Click to expand...
Click to collapse
Btw, it does not matter how many times you'll reflash, this sd bus failure is pretty common in some first series of GT-9000 and GT-9000M
Sent from my GT-I9000 using XDA Premium App
chambo622 said:
Exactly what I thought...you gave them extremely obvious reasons to put you at fault when you could have easily gotten a free replacement out of this. Don't answer questions that aren't asked
My father's I9000M had a failed SD and I got it replaced for free. Ironically his had a single ROM flashed on it and mine has had over 100 and been 100% fine.
Click to expand...
Click to collapse
My BELL phone started up with an AT&T logo... even if I didn't volunteer the information they would have figured it out and sent me the bill.
As soon as they determine it is off warranty Samsung charges $35 dollars just to evaluate the problem and then charges you to fix it.
Yes I should have just brought it back when it first messed up but I figured my warranty was already voided due to the voodoo installation that I could not reverse (due to the boot loops).
Lesson learned.. probably won't tweak my phone too much in the future...especially if (like my last phone) I can't get into recovery mode - though I'm hoping this is fixed in the new phone I get.
Sozage said:
My BELL phone started up with an AT&T logo... even if I didn't volunteer the information they would have figured it out and sent me the bill.
As soon as they determine it is off warranty Samsung charges $35 dollars just to evaluate the problem and then charges you to fix it.
Yes I should have just brought it back when it first messed up but I figured my warranty was already voided due to the voodoo installation that I could not reverse (due to the boot loops).
Lesson learned.. probably won't tweak my phone too much in the future...especially if (like my last phone) I can't get into recovery mode - though I'm hoping this is fixed in the new phone I get.
Click to expand...
Click to collapse
$5 jig could have saved you $150
But at least you're having your phone repaired...
Kops said:
$5 jig could have saved you $150
But at least you're having your phone repaired...
Click to expand...
Click to collapse
Not repaired! New phone! Maybe even one without a faulty SD card!
Sozage said:
My BELL phone started up with an AT&T logo... even if I didn't volunteer the information they would have figured it out and sent me the bill.
As soon as they determine it is off warranty Samsung charges $35 dollars just to evaluate the problem and then charges you to fix it.
Yes I should have just brought it back when it first messed up but I figured my warranty was already voided due to the voodoo installation that I could not reverse (due to the boot loops).
Lesson learned.. probably won't tweak my phone too much in the future...especially if (like my last phone) I can't get into recovery mode - though I'm hoping this is fixed in the new phone I get.
Click to expand...
Click to collapse
The lesson you should've learn is to READ before you attempt anything.
I've flashed about anything to this phone and it's pretty hard to really brick the thing... Flashing the rom from a captivate is realy not in the line of "tweaking" rather than no-sens what so ever...
t1mman said:
The lesson you should've learn is to READ before you attempt anything.
I've flashed about anything to this phone and it's pretty hard to really brick the thing... Flashing the rom from a captivate is realy not in the line of "tweaking" rather than no-sens what so ever...
Click to expand...
Click to collapse
Right, it should be enought to use common sense, and think a little before any further action. I have tried almost anything, starting with dualboot to xubuntu linux, or editing apk's, modding and themming apps (not always successful), erasing all data partitions, created new ones, installed (or at least tried) to install gentoo linux with simple routing capability, and so on. And I'm still here.
Truth is, that some first lines of SGS were affected with faulty sd bus. But there is no need for paying warranty service, and no need to be few days without my phone. If common sense is used, then User would not:
1) install captivate firmware
2) flash anything before cwm is working
if both above fails, he'll reboot to the download mode, flashed canadian or any other fw containing Sbl.bin, alias recovery.
After that, he would flash standard stock firmware which is used by his operator. As a last thing, he would wipe sdcard from recovery.
Phone will look, behave and WILL BE same as he'd bought it.
So they will look on it, and will see standard, untouched phone, which is unknowingly rebooting itself.
Voila! They'll have no other chance then give you brand new phone right on the spot.
So for the next time, keep your mouth shut at least, when you deal with operator ;-)
Sent from my GT-I9000 using XDA Premium App
t1mman said:
The lesson you should've learn is to READ before you attempt anything.
I've flashed about anything to this phone and it's pretty hard to really brick the thing... Flashing the rom from a captivate is realy not in the line of "tweaking" rather than no-sens what so ever...
Click to expand...
Click to collapse
I wish people would read the entire thread before posting more bs like this.
Trying to put the captivate software on my phone via Odin One Click was the 10th or so thing I tried to do to restore my phone. Nothing would work - recovery mode did not work on my phone nor was I able to restore it.
Flashing the captivate software was an attempt to get recovery working (a desperate attempt) and had nothing to do with my comment about tweaking.
diaf.
I know there is nothing you can do but out is bs that you' voided' warranty. they make you pay $150 for THEIR hardware failure.
I know this is possible depending on the phone, but on the Vibrant I have not found a way to install clockwork mod without using USB. I saw that mobile odin was an option for some samsung phones but not the Vibrant.
My usb port is dead, no warranty etc. I bought it for 70 in like new condition with knowledge that the port was bad. I figured that the port needed to be soldered back down. But after taking the phone apart, I don't see anything wrong with it. Its not loose on the board, but the socket itself is loose inside.
The baseband is KA2 Eclair. I got it rooted with the oneclickroot tool.
On a side note, the phone also came with pictures of the seller and all his girlfriends naked . Not pretty
So let me review what you want to do, you want to install CWR without having a USB port. Seems easy enough.
Firstly, find a app that will let you connect to your phone to your computer, apps like Dropbox, Box, and this app i put up on these forums a bit ago will do more than just the job HERE
install one of those, which ever you like. I'll use the MIUI File Manager as a example throughout this post because its the easiest.
Open the app, go to the FTP and start service, go to your computer open MY COMPUTER and type in ftp://all your #'s
Put this file in your ROOT meaning just in sdcard/ no folders just drag and drop it in there. DO NOT RENAME,EXTRACT OR ANYTHING TO THE .ZIP just put it in the sdcard/
*Thanks for the CWR file from Woodrube and S15*
Now go into Recovery mode on your phone
Power + Volume up and down ( i think )
Press REINSTALL PACKAGES
It SHOULD say something like booting into clockwork recovery.
it will reboot, if it goes to clock work recovery, GREAT. If not, press Reinstall Packages AGAIN and it should directly go there.
Just reply if i'm explaining something wrong or if you need more help.
Or you could just download and install rom manager and flash clockworkmod through there. No offense xriderx, just seems like a lot of work to just install cwr that a single app can do as well.
djquick said:
Or you could just download and install rom manager and flash clockworkmod through there. No offense xriderx, just seems like a lot of work to just install cwr that a single app can do as well.
Click to expand...
Click to collapse
To each his own, Rom Manager never has worked great on my phone. Even bricked it completely once and I don't believe it was user error.
Relevant guide, +1 cookie. One suggestion though, organize the steps a bit further so there is a clear distinction between steps.
ie:
• Now go into Recovery mode on your phone, Power + Volume up and down ( i think )
• Press REINSTALL PACKAGES. It SHOULD say something like booting into clockwork recovery. it will reboot, if it goes to clock work recovery, GREAT. If not, press Reinstall Packages AGAIN and it should directly go there."
Anywho, to the OP: Since it's rooted, why aren't you simply downloading ROM Manager from the market and installing CWR from there?
edit/ beaten
Don't get me wrong, your tutorial is spot on, I just never had any problems with ROM manager before so I threw it out as a suggestion.
Sent from my Nexus S using xda premium
working on it now, big thanks!
TheEnternal said:
working on it now, big thanks!
Click to expand...
Click to collapse
As far as the port goes, Eugene, Krylon360 and myself all fried ours when we were porting the V4G - so you may not visibly see anything wrong with it at all.
Thanks guys, I ended up semi bricking the phone . Even though it was my 6th droid device. Not sure what I did, I was in recovery and everything was working, then went to reboot and it was stuck on the Galaxy screen, could no longer get into recovery. Too bad that USB port was out . I ended up just reselling it to a guy for parts and still made some profit off it. Shame though, that AMOLED display was beautiful. Ended up getting a G2X yesterday for 195, just missed one at 150 on craigslist. Already got it up with CM 7.2 with a minor OC. Hopefully towards then end of this year I might be able to get a Galaxy 2 for cheap.
hi.
pls need help.
have the same phone. my usb is not working too.
t-mobile vibrant t959.
its CM7.2 skang-kang flashed.
have issue with mute-unmute.
and need to get it back to froyo.
how to do it without usb?
card slot is working fine.
zukko said:
hi.
pls need help.
have the same phone. my usb is not working too.
t-mobile vibrant t959.
its CM7.2 skang-kang flashed.
have issue with mute-unmute.
and need to get it back to froyo.
how to do it without usb?
card slot is working fine.
Click to expand...
Click to collapse
Download the files you need to your phone and flash them
Sent from my HTC Sensation 4G using XDA
johnson8cyl said:
Download the files you need to your phone and flash them
Sent from my HTC Sensation 4G using XDA
Click to expand...
Click to collapse
i have tried this.
but gingerbread loader and froyo loader are different.
it gave an error at flashing and stopped flashing.
Hmmm. That would require fastboot huh. Don't know of a wireless way to use that. Is there an unroot procedure you could do from your sdcard without a cord and then re-root to gb perhaps?
Sent from my HTC Sensation 4G using XDA
and i'm asking for something like this.
but i ask for froyo not unroot.
to flash from sd card.
it gives an error
Amend scripting (update-script) is no longer supported.
Amend scripting was deprecated by Google in Android 1.5
it was necessary to remove it when upgrading to the clockworkMod 3.0 Gingerbread based recovery.
Please switch to Edify scripting (updater-script and updare-binary) to create working update zip packages.
installation aborted.
I don't think it is possible to downgrade to froyo from CM7 without ODIN. I might be wrong but that is how i remember it.
Though i did find this thread..
http://forum.xda-developers.com/showthread.php?t=1149158
But i don't know how that worked for people. You might wanna research a little bit more. IMO you are better off going to ICS.
Br1cK'd said:
Just use Odin, don't shortcut it. The OP here has a very very basic idea of the reason and necessity to change these files, and has not provided a complete set of steps in two different "guides" he has posted here, and nobody has been successful as per the reports.
Bottom line, save both yourself and dev in the future a headache, and just use Odin.
Click to expand...
Click to collapse
its very sad ((((
Just a reminder to some who have USB port problems. I'm not trying to insult anyone's intelligence here but remember Samsung phones are picky about USB cables.
I know because my phone was Semi bricked while doing Odin. Turned out my original Samsung cable went bad halfway through Odin'ing a new bootloader. After two months of playing with it I tried literally 5 different data cables that all fully worked for other phones and a few cheap off the street cables. Some would not even charge my vibrant but would work fine for data and charge on my wife's LG Quantum. Hard to find good micro-USB cables here in Peru. Finally I ended up modifying my original cable with another cable's micro-usb connector and wrapping a separate ground wire around the shield to get it to work. Samsung phones must require really good shielding to communicate and possibly not all cables have the shield connected on both sides or are properly shielded.
zukko said:
hi.
pls need help.
have the same phone. my usb is not working too.
t-mobile vibrant t959.
its CM7.2 skang-kang flashed.
have issue with mute-unmute.
and need to get it back to froyo.
how to do it without usb?
card slot is working fine.
Click to expand...
Click to collapse
Check out 'mobileODIN' on the market.
I have the att s4 with the mf3 build which I received via an ota update. I recently did the root for this build which worked perfectly, afterwards I read through 47 pages of forums and was trying to do the work around djrbliss put out, around page 40 someone says if your phone is rooted just download goomanager and installscriptrecovery. then reboot recovery. I downloaded goomanager then installed script, after this I hit the reboot recovery and the phone went into download mode. and it will stay there. If i restart it returns to download mode. Any Ideas?
Im not 100% but u may hve read wrong. This has happened to everyone who has tryed to flash a recovery on mf3. You can only have root there is no custom recovery for this build. Ok now this is wat you do take your phone to bestbuy tell them kies f'd ur phone up nd they can reflash mf3.at this moment mf3 isnt available to general public
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Yeah, read the forums. I mean seriously, almost every other post, including the one you read, tells you that drjbliss's exploit was patched in mf3, and can brick your device if you attempt to install a custom recovery. It is, quite literally, the biggest topic in the S4 forums. Also, there is no odin flashable image for mf3, so you cannot return to stock without taking it to bestbuy. Read more in the q&a section, as this same mistake has been made and asked about at least a hundred times. Literally.
In conclusion, you have a paperweight till you take it to get it flashed back to normal.
ok thanks for the help
cooljg said:
ok thanks for the help
Click to expand...
Click to collapse
Read this thread. Best buy can flash the stock mf3 firmware and get your recovery back. http://forum.xda-developers.com/showthread.php?p=45457012
Either that or J-Tag.
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
Hey guys thanks for chiming in. I want to give a thank you to those who have gave me a serious answer. I will go back to best buy and try again, but I sent my wife up there and she said the cell phone department told her they do not flash firmware there. She said she asked them if the service section did and the lady told her no again. I am fairly familiar with flashing the firmware on an s3 I just haven't messed with the s4 that much,and obviously I didn't read as well as I thought I did or it wouldn't be bricked. I do have one other question tho if Best Buy can flash it back to stock firmware, is it safe to assume at some point I should be able to flash it back via odin when the mf3 build is released by sammobile? Either way if best buy doesn't flash it back i'm screwed on this one and i'll just have to pick up another s4 tomorrow. I just want to know if this one can be fixed i'd really hate to waste a perfectly good phone.
If and when mf3 firmware is available you should be able to flash with odin. Best buy seems to be using a new software package other than Odin so who knows if an odin package will be available.
I believe at best buy they have to have a "Samsung Experience" booth or area to do the flashing. The normal best buy service counter can't do it.
~wolverine~ said:
I believe at best buy they have to have a "Samsung Experience" booth or area to do the flashing. The normal best buy service counter can't do it.
Click to expand...
Click to collapse
Correct
Question on brick fix
Hey guys thanks for the helpful info. I took it to the samsung experience part of best buy and the guy fixed it. He didn't have to flash the firmware tho, he took the back off and replaced the battery then I don't know what combination of buttons he hit or what but he held something and it was able to reset the phone and came up normally. Does anyone know what he could of hit? The phone was stuck in download mode no matter what you hit it would only reset to it. I had tried booting and holding volume up and home and releasing home for the recovery boot. As a recap of what happened I had rooted the phone and then downloaded goomanager and ran the installed script option under settings then I reset and was stuck in download mode. I just found it crazy that he never had to hook it to his computer to fix it.
cooljg said:
Hey guys thanks for the helpful info. I took it to the samsung experience part of best buy and the guy fixed it. He didn't have to flash the firmware tho, he took the back off and replaced the battery then I don't know what combination of buttons he hit or what but he held something and it was able to reset the phone and came up normally. Does anyone know what he could of hit? The phone was stuck in download mode no matter what you hit it would only reset to it. I had tried booting and holding volume up and home and releasing home for the recovery boot. As a recap of what happened I had rooted the phone and then downloaded goomanager and ran the installed script option under settings then I reset and was stuck in download mode. I just found it crazy that he never had to hook it to his computer to fix it.
Click to expand...
Click to collapse
Hmm, that is interesting. Did he replace the battery temporarily while 'resetting the phone with combination of buttons'?
Or did he place the battery inside and let you have it?
Sounds like a simple factory reset...
Sent from my SAMSUNG-SGH-I337 using XDA Premium 4 mobile app
haremmon said:
Hmm, that is interesting. Did he replace the battery temporarily while 'resetting the phone with combination of buttons'?
Or did he place the battery inside and let you have it?
Click to expand...
Click to collapse
He originally plugged my phone up when I gave it to him but it wouldn't come on so he unplugged it and replaced the battery. The battery I had was completely dead. After he replaced the battery he turned it on and it went to the download screen with the little green alien. After that he held some buttons and kept looking at the back and then the front of the phone. I couldn't really see what he hit but shortly afterwards it came up with my lock screen picture. After that he said it doesn't need flashing but he would flash the firmware if I wanted so I said ok and he did. I have the phone now working great but it doesn't show rooted anymore.
Omg how do people not know this already. I have had my S4 for 2 days even i know better and I cant believe people dont read
Hi everybody, I enjoyed my stock N4 for almost a year and today several apps started to crash suddenly, after that the device rebooted itself and never got out of the bootloop. I immediatly booted into recovery and tried to wipe the cache memory and perform a factory reset but I cannot do either of the two, the error I get is something like "can't mount cache partition".
What should I do? How did this happen?!? I really need my phone back asap.
Thanks everybody!
Flash the stock images.
Chromium_ said:
Flash the stock images.
Click to expand...
Click to collapse
Ok I will but...How can this happen? A fully stock phone who never had a problem suddenly corrupts it's partitions?! (This is my understanding of the situation, correct me if I am wrong)
Thanks again for the link
Update: unlocking the bootloader works but when I reboot it appears to be locked again.
flashing the bootloader img file fails.
chikosneff said:
Update: unlocking the bootloader works but when I reboot it appears to be locked again.
flashing the bootloader img file fails.
Click to expand...
Click to collapse
sounds like your storage itself fails. thats the same issue that happens when the storage goes bad.
simms22 said:
sounds like your storage itself fails. thats the same issue that happens when the storage goes bad.
Click to expand...
Click to collapse
Thanks for helping, yes it looks like..so I can throw away my phone or there's something more I can try?
It feels so weird because it's one of the few phones I always kept stock, never fell, never had a single problem. Damn.
chikosneff said:
Thanks for helping, yes it looks like..so I can throw away my phone or there's something more I can try?
It feels so weird because it's one of the few phones I always kept stock, never fell, never had a single problem. Damn.
Click to expand...
Click to collapse
You could give this a try, but I really doubt it'll do much. I guess its worth a shot though.
chikosneff said:
Ok I will but...How can this happen? A fully stock phone who never had a problem suddenly corrupts it's partitions?! (This is my understanding of the situation, correct me if I am wrong)
Thanks again for the link
Click to expand...
Click to collapse
chikosneff said:
Update: unlocking the bootloader works but when I reboot it appears to be locked again.
flashing the bootloader img file fails.
Click to expand...
Click to collapse
Tried to Toolkit yet ? http://forum.xda-developers.com/showthread.php?t=1766475
Why did it happen? A phone is basically a mini computer, same as when you have to reload a computer OS sometimes,(failing hardware, bad app???)
Timboe73 said:
Tried to Toolkit yet ? http://forum.xda-developers.com/showthread.php?t=1766475
Why did it happen? A phone is basically a mini computer, same as when you have to reload a computer OS sometimes,(failing hardware, bad app???)
Click to expand...
Click to collapse
I'll give it a shot thanks, but I am afraid that the fastboot flash error is pretty clear :crying:
I get the phone being a computer, and I am totally ready to reload an OS...but I am not so ready to see the storage fails so suddenly leaving me with no phone, especially because this phone has received more care than any other phone I ever had..
Timboe73 said:
Tried to Toolkit yet ? http://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
If its failing when he does it manually via fastboot commands, its very unlikely that using a toolkit will change anything. A toolkit simply runs the same fastboot commands behind a GUI.
Switched to windows to give the toolkit a try, then I will follow the unbrick procedure...I still cannot believe that this phone is lost without even having experienced the fun to mess it up with my own hands
chikosneff said:
Switched to windows to give the toolkit a try, then I will follow the unbrick procedure...I still cannot believe that this phone is lost without even having experienced the fun to mess it up with my own hands
Click to expand...
Click to collapse
As expected: toolkit not working. Since the bootloader " relocks" itself after rebooting the toolkit is unable to flash it afterwards.
Will try to contact google support but I am currently living in Europe I don't think it will be easy to get help.
Any other help is greatly appreciated. Thanks everybody.
1. if its within the warrenty period, this is something that would be covered.
2. its fixable. it can be professionally repaired, or you can try to do it yourself with the right parts.
but you will lose whatever you had in your storage, if you havent already.
another case reported :/
i think some batches of nexus 4 contains emmc brick bugs
just see this thread, more then 5 or 6 have been reported here.
http://forum.xda-developers.com/showthread.php?t=2259334
so after reading that thread i **** my self, because if this occured to my nexus i will have no warranty no google claims no nothing because i live in Pakistan.
So i ran emmc check app on my phone to check what it shows.
my emmc check shows i have "NO, Sane chip"
this means i am safe? if it give me "Yes, Insane chip" then i,m not safe according the my theory.
EMMC check app also shows the chip type, my chip type is "016g92"
googling this chip type i came across no specific results, one from S3 sudden death thread discussion. one person reports he have the 016g92 type and it is a safe chip according to other folks.
and one person having a galaxy s3 bricked his emmcs chip and claim the warranty. after the phone returns his chip type change to 016g92
http://smartphone.usofttech.com/t85915.html
so they change the emmc chip to 016g92.
can i surely assume that my nexus is safe from this serious hardware defect?
also any one here run the emmc chip and do give there chips type here, as i want to confirm if i,m safe or not. if not i,m going to sale my phone here. because the lose will be unbearable for me if the brick did occured
---------- Post added at 11:48 AM ---------- Previous post was at 11:37 AM ----------
simms22 said:
1. if its within the warrenty period, this is something that would be covered.
2. its fixable. it can be professionally repaired, or you can try to do it yourself with the right parts.
but you will lose whatever you had in your storage, if you havent already.
Click to expand...
Click to collapse
Dear Sir do advice me
simms22 said:
1. if its within the warrenty period, this is something that would be covered.
2. its fixable. it can be professionally repaired, or you can try to do it yourself with the right parts.
but you will lose whatever you had in your storage, if you havent already.
Click to expand...
Click to collapse
I still have 2 weeks of warranty left but I'll be in Europe till next year..I will try to ask the warranty service if I can send it in at my own expense.
Damn a worldwide warranty service doesn't look so useless now as it looked when I bought it :laugh:
PHONE BACK FROM THE DEAD!!!
So I got in touch with google's customer care to arrange the RMA and just to show them that my phone was impossible to recover I jumped ahead and told 'em: ok let's do a factory reset together so that I can show you what's the problem....
Fastboot>recovery>>data wipe....COMPLETED!
I cannot understand why did it work, I tried to wipe it at least ten times yesterday.
So now I have my N4 back working. What's your opinion on what happened? Do you feel like the problem is going to show up again soon? Is there anything I should do now that it's working? I just did a factory reset, not the cache wipe.
Just FYI: RMA from oversea is a pain in the ass, you have to ship the phone back to somebody in the U.S. and THEN ask for the RMA.
I wish I had your luck, mine did the same thing about 2 weeks ago. Couldn't get it to factory reset either. Mounting issue. My RMA came in yesterday. I'm enjoying the new phone though. It's even got the little nubs on the back. Mine original was a creaky 1st or 2nd batch one, I think. I will miss all the memories, pics, and data on my old one though.
SefEXE said:
I wish I had your luck, mine did the same thing about 2 weeks ago. Couldn't get it to factory reset either. Mounting issue. My RMA came in yesterday. I'm enjoying the new phone though. It's even got the little nubs on the back. Mine original was a creaky 1st or 2nd batch one, I think. I will miss all the memories, pics, and data on my old one though.
Click to expand...
Click to collapse
Since I feel this problem is hardware related I do not feel completely safe and I believe you were the lucky one getting the RMA
I had no choice, I should have sent the phone back to the US and then ask for the RMA...big pain in the ass
:fingers-crossed: let's hope this thing holds