I tried to upgrade my brothers samsung galaxy gio with a leaked version of it's 2.3.4 upgrade via "Odin".It kinda got stuck in the process and following the guide for it I removed the battery (it said to remove the battery if it stuck at a process for more than 10 minutes). After that when I tried to power it up it got stuck with an image of a phone and a pc connected with dots and a caution mark in between. For extra info recovery mode doesn't open but the download mode does. And I have tried to upgrade it a few times but gets stuck at the process named "ididb download"or something like that.
Is the phone bricked?????? Plz reply quick.
Hi,
Don't worry: as long as you can turn the phone on you should be OK, it's only a soft brick . Have you tried going in download mode again, and reflashed another ROM or even the one you attempted? Got evering right? OPS? Evering you must tick? Re-read the whole tutorial cause generally people mess up because they don't pay enough attention ^^
P.S. At least a million threads exist for this, you obviously haven't looked far before posting..
Related
hello all, I am having a bit of an issue. So as you know, there is a new 2.2 version of froyo, so i and my noob self wanted to download it, so i searched on Google on how to do it using Odin, and i did, then next thing i knew i was stuck at the recovery menu because there wasn't a "select" key on the vibrant, so my phone was semi-bricked kinda. but i fixed it by going to the download mode and downgrading my firmware back using Odin, but there was a problem, every time i booted my phone, the "Samsung GT-i9000" logo would show up, then 3 seconds later the "Vibrant" logo would show up, so 2 logos at once, that seems weird and i don't want that. but i really want my phone to be normal again! (and also my phone got unrooted for some reason after i "downgraded") and whenever i wanted my phone to go to recovery mode, you would have to use the i9000 method to get that to work, but obviously i cant use that method because i don't have a middle button on my Vibrant, and i don't want that, so my question is:
How do i make my phone normal again? do i have to use Odin to do that and what files do i have to use to bring it "back"?
plz Help!
I wanted to share my knowledge and experience from the past 2 days. Most of the help came from guides and posts on this forum so I wanted to give that back.
We were trying to root the SGS4G and because we're noobs we made the mistake of thinking it was a Vibrant. Got a Vibrant ROM and tried to flash it though Odin WITH re-partition checked. Everything we read said if you do either one of these things, you will brick your phone.
Sure enough we bricked the phone. It was trying to boot into the Vibrant ROM but was getting stuck on the word 'Vibrant' and then showing a whole lot of weird colored pixels. We then learned we'd made a massive mistake and that the phone wasn't a Vibrant after all.
We got a stock ROM for SGS4G and started trying to push them through Odin. Faced countless FAILS and freezes and finally it took us to the Recovery Mode and we tried the Restore option. It booted into a crippled SGS4G ROM. When it booted, it vibrated every 10 seconds or so and it had a null IMEI and unknown baseband.
We tried following a guide that wanted to change some text in the nv_data.bin but the numbers we were meant to be editing (0018810?) didn't exist in our nv_data.bin. So that didn't work for us.
In the meantime we tried to flash the stock ROM in Odin but kept getting FAILs and Freezes. With this step we lost even the crippled operating system and couldn't reach anything except the 'phone --!-- computer' screen. Luckily, this acts the same as download mode, so not bricked. We kept trying to push the stock SGS4G stock ROM (Froyo 2.2) several times and failing.
At one point we got a completely black screen, wouldn't turn on. Bricked again. We found this post on RootzWiki and it worked for us that time and brought it back from the black screen to download mode http://rootzwiki.com/topic/1820-how-to-unbrick-your-sgs4g/
Somehow we ended up at this guide here on XDA for fixing the "null/null" IMEI http://forum.xda-developers.com/showthread.php?t=1142829
We followed that guide. When you add the PIT file it automatically checks 'Re-Partition' in Odin, we didn't uncheck it. Bricked again. It was stuck on the Samsung logo and when we tried to get to download mode it got stuck on a black screen with the loading circle/lines and 2 computers were giving 'The USB device has malfunctioned' when we plugged it in. The unbrick guide above (RootzWiki) didn't help this time. We tried restarting the computer, let the phone rest without battery for half an hour, held power button for a minute without battery, still nothing.
Finally I accidentally pressed the power button (rather than the volume buttons to get into download mode) and it went to the samsung logo (as expected) and after that I was able to get into download mode. The key to this I think is to keep on trying powering on normally then try download mode over and over and eventually it should get unstuck and the computer should recognize it again.
Once I had it back in download mode, I followed this guide again BUT!!! I made sure to un-check re-partition and I did not check "Phone EFS Clear" (because I had tried that already before it was bricked and wanted to see if a straight ROM would work first). Everything worked perfectly, I got my IMEI and Baseband back, without modifying anything.
I don't know if this was a miracle, or if any of it will work for anyone else, but the moral of the story is don't give up even if you've done the absolute worst possible thing. I don't even think hardbrick exists on this phone after everything we were able to save it from.
Cheers
Hardbricks do exist on this phone but you have to try really hard to do it. A few people have managed it. Way to stick with it and recover your phone. I've done that more times than I can count.
hechoen said:
Hardbricks do exist on this phone but you have to try really hard to do it. A few people have managed it. Way to stick with it and recover your phone. I've done that more times than I can count.
Click to expand...
Click to collapse
I didn't feel like i really hard bricked it until i saw the USB computer connection error "device pluged in malfunctioned" in more than one PC.
Then i really felt like its a hardware BIOS chipset level problem now but man...
That story cracked me up. That is exactly why I spend days reading before I even root my phone. I made the mistake one time on my old G1 and it could not be revived.
Congrats on getting it working. (especially without flooding the q&a with redundant questions that have been described in detail several places )
hani1400 said:
I wanted to share my knowledge and experience from the past 2 days. Most of the help came from guides and posts on this forum so I wanted to give that back.
We were trying to root the SGS4G and because we're noobs we made the mistake of thinking it was a Vibrant. Got a Vibrant ROM and tried to flash it though Odin WITH re-partition checked. Everything we read said if you do either one of these things, you will brick your phone.
Sure enough we bricked the phone. It was trying to boot into the Vibrant ROM but was getting stuck on the word 'Vibrant' and then showing a whole lot of weird colored pixels. We then learned we'd made a massive mistake and that the phone wasn't a Vibrant after all.
We got a stock ROM for SGS4G and started trying to push them through Odin. Faced countless FAILS and freezes and finally it took us to the Recovery Mode and we tried the Restore option. It booted into a crippled SGS4G ROM. When it booted, it vibrated every 10 seconds or so and it had a null IMEI and unknown baseband.
We tried following a guide that wanted to change some text in the nv_data.bin but the numbers we were meant to be editing (0018810?) didn't exist in our nv_data.bin. So that didn't work for us.
In the meantime we tried to flash the stock ROM in Odin but kept getting FAILs and Freezes. With this step we lost even the crippled operating system and couldn't reach anything except the 'phone --!-- computer' screen. Luckily, this acts the same as download mode, so not bricked. We kept trying to push the stock SGS4G stock ROM (Froyo 2.2) several times and failing.
At one point we got a completely black screen, wouldn't turn on. Bricked again. We found this post on RootzWiki and it worked for us that time and brought it back from the black screen to download mode http://rootzwiki.com/topic/1820-how-to-unbrick-your-sgs4g/
Somehow we ended up at this guide here on XDA for fixing the "null/null" IMEI http://forum.xda-developers.com/showthread.php?t=1142829
We followed that guide. When you add the PIT file it automatically checks 'Re-Partition' in Odin, we didn't uncheck it. Bricked again. It was stuck on the Samsung logo and when we tried to get to download mode it got stuck on a black screen with the loading circle/lines and 2 computers were giving 'The USB device has malfunctioned' when we plugged it in. The unbrick guide above (RootzWiki) didn't help this time. We tried restarting the computer, let the phone rest without battery for half an hour, held power button for a minute without battery, still nothing.
Finally I accidentally pressed the power button (rather than the volume buttons to get into download mode) and it went to the samsung logo (as expected) and after that I was able to get into download mode. The key to this I think is to keep on trying powering on normally then try download mode over and over and eventually it should get unstuck and the computer should recognize it again.
Once I had it back in download mode, I followed this guide again BUT!!! I made sure to un-check re-partition and I did not check "Phone EFS Clear" (because I had tried that already before it was bricked and wanted to see if a straight ROM would work first). Everything worked perfectly, I got my IMEI and Baseband back, without modifying anything.
I don't know if this was a miracle, or if any of it will work for anyone else, but the moral of the story is don't give up even if you've done the absolute worst possible thing. I don't even think hardbrick exists on this phone after everything we were able to save it from.
Cheers
Click to expand...
Click to collapse
Wheooooooooowwww,..you just UNBRICKED mine, I know of the Battery pull etc...but the post you referenced
is MAGIC
This was not my first Rom nor Root on this phone, it weirdly happened while doing the GB starter....via ODIN, which i also used before..no clue what went wrong, oh well...
Thank you, thank you "i did"....Yohoooo
Yup i agree i like to read, reread then read as i do. This way i got a pretty good understanding of what I'm doing. Btw i have just started using one click and it is sooooo simple. I love it.
Sent from my SGH-T959V using XDA App
The link for fixing null/null IMEI is not working.
http://forum.xda-developers.com/showthread.php?t=1142829
diavel said:
The link for fixing null/null IMEI is not working.
http://forum.xda-developers.com/showthread.php?t=1142829
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=881162
Im still carrying this phone, stupid baseband unlock for iphone won't come out now I am carrying 2 phones, one as an ipod touch and the galaxy s! Good story, hope it can help others, but I am prepared to jump off of this bandwagon anytime now!
Hello XDA forum,
My name is Brandon. I have used this forum for the last couple years and have found invaluable information, and for that, I thankyou guys!
I have searched everywhere I can think of to find someone that has been able to solve my problem. Hopefully you all can help.
I have a TMOBILE GS2 T989. I have had my phone randomly go into boot loop a few times before (even though I have never had anything besides stock ROM on this phone), and have always been able to fix it with Odin. This time, my phone decided to get stuck into the boot loop cycle, and I tried to use Odin like usual to fix it, and I get to the download section and it only stays in the' download mode for 2-3 seconds and boot loops again. The computer only recognizes the phone for a couple seconds and odin says "removed" and "failed" when i push start in odin. Im not sure why this is happening or how to fix it. All the research I have done has said that if I can get into download mode, the phone is only soft bricked, not hard bricked. But I cant get odin to work for me this time.
Any help is appreciated in advance!
Thanks,
Brandon
bump
Im not a big computer guy but for the most part can figure stuff out, i have rooted several phones before and flashed new roms. I just got the verizon g2 and rooted it, then attempted to do twrp recovery, Nothing even came close to working until i read that flashify worked, so i did that and it said it worked, took 2 seconds, when it restarted it showed my ddroid dead with a warning symbol comin outta his belly. I held down volume down and power keys and it came back on. It will not go into download mode or restore mode.
I had hoped that it worked so tried to flash malladus but once again, nothing!
I have been going at this for close to 12 hrs now and i am about to just break this thing.
Please, i need step by step instructions of what to do that for sure will work.
the forums about twrp do NOT work no matter what i do. and im not missing anything, debugging mode on, connected with ethernet, all info entered correctly, files in the correct folders, yet nothing works!!! PLEASE HELP.
I just want to get that rom! lol
Hello all,
I have flashed ROMs via recovery and Odin plenty of times. I would say I generally know what I am doing and I flash ROMs on the regular. This is my third Samsung device and have been rooting/flashing for almost 3 years, so not a noob. And this is the first time I encounter problem with my phone while flashing ROM.
I was stuck in a bootloop on my Note and it wouldn't even let me boot into recovery, so I decided to Odin and back to stock and try again... I got the one-click, phone recognized, yellow COM box popped up, hit start, walked away for 10-15 minutes. Come back and there has barely been any progress at all... I could barely see the green progress bar. I figured something is wrong because I've done this before and it only takes a minute at most. What I did next is what I think messed me up...I pulled my phone and closed the Odin dialogue box and tried to redo it. Problem is, nothing I could do would get me the Yellow COM box. The phone goes into download mode but Odin doesn't seem to want to recognize it. I've tried EVERYTHING. When I boot the phone normally, I get the Samsung error screen saying there was an issue with a firmware upgrade and I should try Kies. I download Kies and attempt to upgrade firmware but my phone still not recognized. I already tried it to other PC still the same result.
I can't post the pic of my phone.
Is there nothing I can do to restore it?:crying::crying:
ton8_22 said:
Hello all,
I have flashed ROMs via recovery and Odin plenty of times. I would say I generally know what I am doing and I flash ROMs on the regular. This is my third Samsung device and have been rooting/flashing for almost 3 years, so not a noob. And this is the first time I encounter problem with my phone while flashing ROM.
I was stuck in a bootloop on my Note and it wouldn't even let me boot into recovery, so I decided to Odin and back to stock and try again... I got the one-click, phone recognized, yellow COM box popped up, hit start, walked away for 10-15 minutes. Come back and there has barely been any progress at all... I could barely see the green progress bar. I figured something is wrong because I've done this before and it only takes a minute at most. What I did next is what I think messed me up...I pulled my phone and closed the Odin dialogue box and tried to redo it. Problem is, nothing I could do would get me the Yellow COM box. The phone goes into download mode but Odin doesn't seem to want to recognize it. I've tried EVERYTHING. When I boot the phone normally, I get the Samsung error screen saying there was an issue with a firmware upgrade and I should try Kies. I download Kies and attempt to upgrade firmware but my phone still not recognized. I already tried it to other PC still the same result.
I can't post the pic of my phone.
Is there nothing I can do to restore it?:crying::crying:
Click to expand...
Click to collapse
You sound like you have a problem similar to what I had.
I was downloading 6.01 to install using KIES 3 and got no recognition from my Windows 7 based computer when I connected up and ran KIES.
I had the Sammy 1.55.5 USB drivers installed.
What I did it was use KIES,not KIES 3.
Samsung says KIES 3 but that turned out to be wrong in my case,although I'm not sure why?
I'm now running M/M and happily gutting the bloat out of it.
It feels better than new now!
Solved
Anyway, I already solved it!
ton8_22 said:
Anyway, I already solved it!
Click to expand...
Click to collapse
i have the same problem....
how did you solve it?