Early yesterday I launched Kies and hit the update firmware option from the tools menu to see if the alleged ICS update was available for my phone. It appeared it was with, a message promoting that it would clear all personal data from the phone, which I then selected cancel so I could do a backup of pictures/videos on the phones internal SD.
Without doing any sort of backup yet I shutdown the phone, only for it to freeze on the shutting down screen. After 20 mins I pulled the battery and let the phone cool down since it had gotten warm trying to shut itself down. After replacing the battery and turning on it was stuck in a bootloop with only the SGS2 logo, never reaching the ATT logo.
At that point I came to XDA, which I frequently browse but have yet to root, and began reading and searching everything I could find.
Hours later I decided to attempt to flash the stock firmware from sammobile.com using Odin. The flash took a long time and I assume never completed. I left it overnight since I didnt want to unplug it mid-flash. Checking back in the morning the phone is black, Odin says failed/disconnected, and I find the battery completely drained. I charged it for a while then tried turning it back on and got the yellow triangle "firmware upgrade encountered an issue..." screen.
Now i'm attempting once more to flash the firmware but again it has been 30 mins on Sbl.bin. I've had a hard time finding stock firmware in different varieties with working links, so to not increase the flash counter in the event I ultimately have to send it in for repair.
Any suggestions on where to go from here? I've followed every direction I can find for flashing stock firmware and nothing has been successful.
Glad to help if I can. Please tell me exactly what package you flashed from sammobile, with a link if possible.
You should change the title of the thread.... I killed my phone. LOL!
http://forum.xda-developers.com/showthread.php?t=1313659
I attempted to flash I777UCKH7, 2011 August, USA (AT&T)
w.sammobile.com/firmware/?page=3&t=1&o=1&m=SGH-I777&r=-1#modelsa
BROKKANIC:
I've tried the steps in that thread, the One-click Oden does not have the phone showing up in any boxes, yet it still shows up in the non-One click Oden.
nett3 said:
I attempted to flash I777UCKH7, 2011 August, USA (AT&T)
w.sammobile.com/firmware/?page=3&t=1&o=1&m=SGH-I777&r=-1#modelsa
BROKKANIC:
I've tried the steps in that thread, the One-click Oden does not have the phone showing up in any boxes, yet it still shows up in the non-One click Oden.
Click to expand...
Click to collapse
Try this.....
2c.) How to root by flashing Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package with Modem using Odin3 One-Click Downloader (Windows)
Download the "Odin3 One-Click Downloader Stock I-777 UCKH7 with Root no BL" package from Hotfile. Extract the contents of the zip file to a directory on your hard disk drive. This is a One-Click version of Entropy512's Return/Unbrick to Stock, Kernel + Rooted System Package plus stock modem from the development forum. (Contains stock zImage, factoryfs.img with root, and modem.bin.)
Start the Odin3 One-Click Downloader program by double clicking on "I777UCKH7 OCD With Root.exe".
Now Enter Download Mode:
With the phone powered off, plug in the usb cable while holding the vol up + vol down buttons (but not the power button).
When the warning screen appears, press Volume up to continue into download mode.
In Odin, the small edit box in the upper left corner will turn yellow, and say something like [0:COM8]. The number could be different.
Click Start. Watch the progress bar advance in green while the message box in the lower area describes the steps. When the flash is finished, the top left larger edit box will turn green and say PASS! and your phone will automatically reboot.
Unplug the usb cable from you phone after it boots up. Success. You're Rooted.
SOURCE: http://forum.xda-developers.com/showthread.php?t=1311081
creepyncrawly would know better. It's his thread.
Download the file from below post to go back to stock I777UCKH7. Follow the instruction written in the post. I just had the same a while ago using the mobile odin to go back to stock. Got stuck on Samsung Galaxy SII screen. Pulled the battery and then followed the instructions from this post. I selected the one that says no BL 'I777UCKH7 OCD No BL'.
http://forum.xda-developers.com/showpost.php?p=18859438&postcount=199
Once you are done with the stock restore. To upgrade to ICS LE5 follow the instructions from below post. Make sure you read and follow the instructions as mentioned in the post.
http://forum.xda-developers.com/showpost.php?p=27707563&postcount=83
nett3 said:
I attempted to flash I777UCKH7, 2011 August, USA (AT&T)
w.sammobile.com/firmware/?page=3&t=1&o=1&m=SGH-I777&r=-1#modelsa
BROKKANIC:
I've tried the steps in that thread, the One-click Oden does not have the phone showing up in any boxes, yet it still shows up in the non-One click Oden.
Click to expand...
Click to collapse
You downloaded I777UCKH7_I777ATTKH7_ATT and extracted I777UCKH7-rev02-home-low-cl503881.tar.md5?
Flashed the .tar.md5 in the pda slot?
What version of Odin are you using?
Edit: You're getting lots of advice here. Let me know if you need me to help troubleshoot your issues.
BROKKANIC/krips2003: Thanks for helping so far, but no luck. Those both link to the same Odin One click. This and another one click I tried do not show the phone connected to any COM#. But, in the non-one click Oden the phone shows up. I have pulled the battery and changed USB ports and it still will not show up in the one click.
In the mean time I'll see if there's a solution for that, but I'd like to hear any other suggestions.
Edit: I get the feeling Odin is not starting the write process, since neither the progress bar or words show up in the box above COM# until AFTER I unplug the phone, at which time it flashing quickly then displays Failed.
nett3 said:
BROKKANIC/krips2003: Thanks for helping so far, but no luck. Those both link to the same Odin One click. This and another one click I tried do not show the phone connected to any COM#. But, in the non-one click Oden the phone shows up. I have pulled the battery and changed USB ports and it still will not show up in the one click.
In the mean time I'll see if there's a solution for that, but I'd like to hear any other suggestions.
Edit: I get the feeling Odin is not starting the write process, since neither the progress bar or words show up in the box above COM# until AFTER I unplug the phone, at which time it flashing quickly then displays Failed.
Click to expand...
Click to collapse
Try using another micro usb wire if you have one. If not then get one from radioshack or bestbuy. I had the almost similar issue on my captivate with the original USB cable. Then I got a Rocketfish one from bestbuy and it worked like a charm.
I'm sure you might have already done this. Make sure you first run the ODIN and then put your phone in download mode.
krips your a genius!
The one click is now working thanks to the suggestion to pay attention to order of operations. I must have never plugged the phone in AFTER starting the one click. This was easily overlooked when I've been switching the phone between 2 PCs and 3 micro usb cables.
I now have a progress bar and have had made more progress than in the last 24 hours. Even after searching I did not find this solution, even though it's stated in the directions and it seems trivial, maybe it should be emphasized the one click needs to phone plugged in after it's running.
Thanks again. I'll update this post when it's back to being a phone again.
PS. BROKKANIC: you were right, if I didn't kill my phone then I sure was the impeding factor in its recovery.
Good news/bad news. Still stuck in bootloop, but now have SGS2 logo instead of yellow triangle. Trying to enter recovery mode crashes the phone soon after it appears.
Is this a bootloader problem, kernel problem, or something else?
LOL!. Glad you got it working.
nett3 said:
Good news/bad news. Still stuck in bootloop, but now have SGS2 logo instead of yellow triangle. Trying to enter recovery mode crashes the phone soon after it appears.
Click to expand...
Click to collapse
Flash back to stock first.
BROKKANIC said:
LOL!. Glad you got it working.
Flash back to stock first.
Click to expand...
Click to collapse
I believe that what I have been doing. I ran I777UCKH7 OCD With Root.exe, which resulted in bootloop, then ran I777UCKH7-CL503881-No-BL.exe, which also resulted in bootloop. Both completed successfully, but resulted in the same bootloop.
Odin appears unable to flash anything without it being a one click. I'm trying to flash Siyah-v2.6.14-att.tar. But Odin hangs at zImage with no progress bar.
What operating system you using: if windows 7 are you running as administrator ?
hd779 said:
What operating system you using: if windows 7 are you running as administrator ?
Click to expand...
Click to collapse
I've resorted to my WinXP laptop which has been more successful than my Win7 desktop. On the Win7 attempts everything is run as admin, but has many time bluescreened and hard reset the whole PC when attempting to flash anything with Odin. Maybe a separate issue, maybe not. But the XP machine is atleast successfully flashing the Odin one clicks.
Update: Odin standalone (non-one click) appears to be unable to flash anything, it will only hang when trying to write. One click Oden packages seem to work. Is there a one click with full stock sbl, param, kernel, etc?
I think your problem is you flash to stock with packet include bootloader, so that is the reason why your phone is brick.
I'm using this: http://forum.xda-developers.com/showthread.php?t=1691659 for stock UCKH7. This is non-root version and work very well for me. It include sbl, kernel and param, ...
gefox4vn said:
I think your problem is you flash to stock with packet include bootloader, so that is the reason why your phone is brick.
I'm using this: http://forum.xda-developers.com/showthread.php?t=1691659 for stock UCKH7. This is non-root version and work very well for me. It include sbl, kernel and param, ...
Click to expand...
Click to collapse
I haven't flashed a package with a bootloader yet. The only ones that work for me are Odin one click packages, and the two I've tried do not have bootloaders. I've been looking for one WITH a bootloader but no such luck yet, since maybe that would solve the problem.
The guide/link you've suggested will not work for me at this time. I do not have the ability to boot into any andriod OS. The only capability my phone has is executing Odin one click packages for some reason, even Oden standalone firmware flashes do not work.
I had a similar issue...I eventually got mine stuck at the ATT droplets....
Finally I flashed back to 2.3.4 stock....did the ota...then upgraded to ICS.
Its all on my work laptop so I wont be able to post any specific files or their names until monday...
Good luck!
Once your phone gets to the boot screen try to get into stock 3e (both volume buttons + power till 2nd SGSII splash screen) recovery and do a factory reset. Should boot after that. Good luck.
Sent from my SAMSUNG-SGH-I777 using xda premium
Why not try a custom ics rom? What else do you have to lose? Staying stock is overrated anyways. You may also have an antivirus stopping Odin but I doubt it. Just turn off your antivirus and try.
Sent from my SGH-I777 using xda premium
Related
I odin to KA6 from KA5, including the sbl.bin. When I odin from KA6 to KA7 using the stock ROM, odin hanged at transfering sbl.bin. After waiting for 10 minutes or so, I have to disonncect, remove/reinsert the battery and reboot. The dreaded phone-dotted line-computer with an exclamation point appeared. I tried all the manuvers I can find on the forums but failed to get to the download mode screen. I was desperate and called T-mobile. The tech rep instructed me how to "master reset" the phone, without success. The rep transfered me to Samsung tech support. I was instructed to to the "master reset" a few time without success. I was transfered again to a second level Samsung tech support. I waited for nearly 30 minutes without reaching a human being. I hanged up and called T-mobile again. I was finally offered a replacement. After than, I tried again all the button/battery/usb adapter combinations without being able to get past the phone-computer-exclamation point screen. As the last resort, I tried flashing KA6 with Odin 1.3 in this "brick" mode. Surprisingly, Odin recognised the phone and added a modem port. I was successful in flashing KA6 without seeing the downlaod mode screen. I then flash KA7, again successfully. I just wish to report this for the reference of anybody encountering a similar situation. The new sbl.bin in KA6 may have altered the behavior of the bootloader so that the phone will be automatically be put in download mode if anything goes wrong. That essentially makes the vibrant unbrickable. Just my guess...
chtse53 said:
I odin to KA6 from KA5, including the sbl.bin. When I odin from KA6 to KA7 using the stock ROM, odin hanged at transfering sbl.bin. After waiting for 10 minutes or so, I have to disonncect, remove the battery and reboot. The dread phone dotted line computer with an exclamation point appeared. I tried all the manuvers I can find on the forums but failed to get to the download mode screen. I was desperate and called T-mobile. The tech rep instructed me how to "master reset" the phone, without success. The rep transfered me to Samsung tech support. I was instructed to to the "master reset" a few time without success. I was transfered again to a second level Samsung tech support. I waited for nearly 30 minutes without reaching a human being. I hanged up and called T-mobile again. I was finally offered a replacement. I tried all the button/battery/usb adapter combinations without success getting anything beyond the phone-computer-exclamation point screen. As the last resort, I tried flashing KA6 with Odin 1.3 in this "brick" mode. Surprisingly, Odin recognised the phone and added a modem port. I was successfully in flashing KA6 without seeing the downlaod mode screen. I then flash KA7, again successfully. I just wish to report this for the reference of anybody in a similar situation. The new sbl.bin may have altered the behavior of bootloader so that the phone will be automatically be put in download mode if anything wrong happens. That essentially makes the vibrant unbrickable. Just my guess...
Click to expand...
Click to collapse
wrong section for posting this
@birgertime....this sounds like what happened to you lol
Someone on the General thread had this happen also.. instead of anything working for the soft brick, when he plugged his phone in with ODIN open it brought up a COM port and he finally said "well, I'll try to flash it anyway" and it went.
Good "Need to Know" Info
I had a similar experience. I flashed KA7 and needed to flash another rom, so I went about flashing voodoo via ODIN and it failed and I was stuck at that screen.
I was freaking out a little because I couldn't get into download mode (even tried my jig).
Throughout the whole process I did notice ODIN recognized my phone as if it was in DL mode, which I thought was a little strange.
Anywho after trying everything I decided to try again. So I flashed the kernel again (in the phone ! pc screen) and it worked...
Sooooo...maybe the secondary bootloader allows you a way out if you screw up a flash............
jmcghee1973 said:
Sooooo...maybe the secondary bootloader allows you a way out if you screw up a flash............
Click to expand...
Click to collapse
or maybe it sucks worse than before and is easier to brick
I'd prefer your way though
i had the same thing hapopen to me today . odin hanged ,pulled battary out and dload mode shows phone dot computer icon , plugged in cable and started odin and it showed com port and reflashed it ..worked.
maybe that's the new download mode? lol
Sent from my SGH-T959 using XDA App
iynfynity said:
maybe that's the new download mode? lol
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
It's not. I had a similar experience as some of the others in this thread, but it seems that it is some sort of extra failsafe mode. Because I could NOT get into download mode when this happened.
Is there any special reason you were using ODIN? ClockworkMod seems a far more reliable flashing method than Kies (Mini) or ODIN IMO. I only use ODIN when I can't use ClockworkMod. I like to think I have avoided many (soft)bricks this way. A co-worker of mine bricked his phone by using ODIN with a intermittently connecting USB cable, had he used ClockworkMod instead he likely would have been fine since there's no cable involved. This is an attempt to prevent future bricks, nothing more. Thankfully, I was able to fix it for him.
Moved of: Samsung Vibrant > Vibrant Android Development
To: Samsung Vibrant > Vibrant Q&A
Please put your questions to: Vibrant Q&A
I had the same issue. My phone would not boot or get into download mode so it wouldn't get recognized by Odin or ADB. All I could do it get the phone, exclamation point, computer graphic. After a ridiculous combination of things tried, I was able to get it to download mode by unplugging USB and battery out. Then while holding down volume buttons, plug in the USB cable. This [finally] allowed me to get back to download mode. Hope it helps.
Wellp, I tried to install Cyanogenmod and it bricked the crap out of my phone. I followed their guide at http://wiki.cyanogenmod.com/wiki/Samsung_Vibrant:_Full_Update_Guide and got to the "The Samsung Vibrant now has ClockworkMod Recovery installed. Continue to the next section." step and upon my phone's startup (with the added Clockworkmod flash screen) was greeted with nothing but a black screen. All I see is the samsung "S," glowing for ten or so seconds, like the Windows logo, then it goes black. I tried One Click Unbrick (http://forum.xda-developers.com/showthread.php?t=1153310), which restarts my phone, and brings me back to the same screen. Next, I tried doing the three button (sound-up, sound-down, and power) boot into the Android System Recovery program. There, I deleted the cache data, all user data, and attempted to reinstall packages, but I got a "failed to verify whole-file signature" error, as well as a "signature verification failed" error. I also, tried to re-flash via ODIN, but the only way to get it to see the phone is to boot it to the S logo screen (and the darkness beyond). There is the no-man's-land that Odin detects. Unfortunately, Odin gets stuck at the connecting step, and goes no further (unless that takes more than a few minutes). Fun stuff.
I'm sure you get people asking for help all the time, so I am very sorry to be yet another person asking, but this is quite the frustrating brick.
I am able to boot into download mode, as well as the android recovery menu (the aforementioned area with clear cache, user data, etc.) so I have found a bit of solace in those facts.
Thank you so much for your time.
rushmix said:
Wellp, I tried to install Cyanogenmod and it bricked the crap out of my phone. I followed their guide at http://wiki.cyanogenmod.com/wiki/Samsung_Vibrant:_Full_Update_Guide and got to the "The Samsung Vibrant now has ClockworkMod Recovery installed. Continue to the next section." step and upon my phone's startup (with the added Clockworkmod flash screen) was greeted with nothing but a black screen. All I see is the samsung "S," glowing for ten or so seconds, like the Windows logo, then it goes black. I tried One Click Unbrick (http://forum.xda-developers.com/showthread.php?t=1153310), which restarts my phone, and brings me back to the same screen. Next, I tried doing the three button (sound-up, sound-down, and power) boot into the Android System Recovery program. There, I deleted the cache data, all user data, and attempted to reinstall packages, but I got a "failed to verify whole-file signature" error, as well as a "signature verification failed" error. I also, tried to re-flash via ODIN, but the only way to get it to see the phone is to boot it to the S logo screen (and the darkness beyond). There is the no-man's-land that Odin detects. Unfortunately, Odin gets stuck at the connecting step, and goes no further (unless that takes more than a few minutes). Fun stuff.
I'm sure you get people asking for help all the time, so I am very sorry to be yet another person asking, but this is quite the frustrating brick.
I am able to boot into download mode, as well as the android recovery menu (the aforementioned area with clear cache, user data, etc.) so I have found a bit of solace in those facts.
Thank you so much for your time.
Click to expand...
Click to collapse
which rom did u come from?
Froyo. I followed the guide to a 't' and got this black screen. I have no idea what I did wrong.
Well, I need to run off to work now, but I'd really appreciate any responses.
It seems like my phone isn't being detected by odin or windows when it is in download mode, though windows does recognize that a Samsung USB device is being connected. This is recognized in the windows tray (under the name "Samsung_Android"), and in Heimdall's Zadig driver tool ("Samsung_Android").
Hmm first tthings first, your reinstall package error seems pretty simple, yu dont have the right update.zip and recovery combination... if u wanna solve that problem, find the recovery 3e to 2e tool (google it) and run it (follow directions).. then you can run reinstall packages (might havr tto do it twice). If that doesnt cut it, find the CWM update.zip and put iit into the root of your internal sd card (the 12gb one), then run reinstall packages again. You may have to reinstall packages more than once.
Your odin problem might be caused by a lack of drivers on your comp... go on the android dev section and look for a thread talking aboout ms64 and 86 drivers samsung something...
If you can get into download mode, you can unbrick your phone so dont panic
Now odin is a very dangerous tool imo so if you really are sorry about askint, do us a favir and read the sticky oon how to odin before you use it so you dont have to come back and ask us about how to Really unbrick your phone
Also, your brick is referred to as a soft brick and the android recovery program is referred to as recovery mode.
And if you really **** up, we now have the unbrickable mod in the vibrant android dev section which will unbrick your phone no matter wat (it takes somr hardware modifying though)
Sent from a cell tower to the XDA server to you.
And if i were you, id redownload the cm7 package again to make sure that it wasnt a bad download and id read some general vibrant info before diving into cm7... if youre running stock recov and have never odined before etc, youre prob not the best candidate for flashing.. just my opinion
Sent from a cell tower to the XDA server to you.
Thank you very much for your reply. I couldn't find a related tool with the Google search string "3e to 2e recovery tool vibrant," but I did find a modified 3e tool at dkszone(*)net/bypass-e-signature-verification-fail-issue-on-samsung-vibrant-android-2.2 . However, this gets stuck at "checking for temporary root."
As for installing drivers, I have installed the Samsung galaxy 64 bit drivers several times now, but I'll give the 32 bit drivers a whirl as well.
I am unable to access the SD card, and don't have a mini SD card reader, so that compounds the problem (damn my lack of cash!).
*Edit* Upon my attempted installation of the 32 bit drivers I get the following (word for word) "Swallowtail has being used. You need to eject device and reboot your computer. Rerun (Japanese or Chinese characters) after reboot your computer." Google returns zero results when I search for this error. I tried rebooting my computer and running it again, but got the same error (even with the phone unplugged from the computer).
*Double Edit* I've been trying to use the AIO Vibrant Toolbox to restore my phone to factory defaults, but I've been having no luck, as it claims my phone is not in USB debugging mode (and obviously I can't change this, as I have no access to the Android OS).
Try this, mate and hopefully you will be up and running soon...
http://forum.xda-developers.com/showthread.php?t=1278683
When I run this the program handshakes, downloads the pit file, then restarts and "...Local and device PIT files don't match and repartition wasn't specified!
Ending session...
Rebooting device...
Device not connected.."
It reboots to the black screen of death and stays there. Perhaps I could select "Flash Bootloader," but the warning of possible permanent damage scares me.
According to the thread...
"REPARTITIONING ISSUE WITH HEIMDALL 1.3.0
Heimdall currently has an issue with repartitioning. 99% of the time you will not need to repartition. Failure to follow these directions can possibly lead to bricking:
Do not flash bootloaders if you see this message:
Code:
Local and device PIT files don't match and repartition wasn't specified!
This message means your partition tables do not match the firmware."
So I guess one of the roots of my problem is that my partition tables do not match the firmware. I have no idea what to do about that.
In this case try another computer if you can, install the right drivers and see odin recognizes your phone. I'm sure it will, for some people sometimes it takes fair few tries for no reason.
Another suggestion, take out sim card and external sd while connecting in download mode. Sometimes that helps.
---------- Post added 29th September 2011 at 12:01 AM ---------- Previous post was 28th September 2011 at 11:43 PM ----------
Here is a recent thread where someone had issue with odin connection.
http://forum.xda-developers.com/showthread.php?t=1225197#16797271
Well, I ran Heim one click on another computer and had the same boot-to-blackscreen process happen.
I was, however, successful at getting Odin to recognize the phone with AIO vibrant toolbox. Odin kept getting stuck at "set pit file" though.
Baby steps...
This is so frustrating. I feel like I'm so close.
How do I get the right PIT file on my phone if ODIN is getting stuck at that step?
Now, after installing the drivers provided with Heimdall-one-click's Zadig, ODIN doesn't recognize the phone.
One step forward, two steps back.
*Edit* Nevermind, got ODIN to recognize it again by uninstalling/reinstalling all related drivers.
Then odin to stock with tthe stock jfd files.. follow the manual, report results
Sent from a cell tower to the XDA server to you.
http://forum.xda-developers.com/showthread.php?t=734475
Use those files and the procedure for ODIN.
As for what caused your problem. You flashed a clockwork recovery for a different phone, possibly the Vibrant (non-MTD) mode? Usually installing Clockwork on the Vibrant only works from ROM Manager app when its running stock JFD. At least for me anyway. Any other ROM it ****s it somehow and I end up in a situation like yours. Not to worry though. Here's a quick install guide after you ODIN the phone to stock.
Put latest nightly of CM7 on the phone memory (not external microSD)
Install clockwork (Easiest way to do this is put the update.zip file I've attached onto the root of your phone memory, not the external microsd card, then reboot into recovery (hold both volume buttons and turn it on) and select Reinstall packages twice. It will then boot you into Clockwork).
Wipe data and cache in clockwork
Install zip from SD card--> pick the latest CM7 nightly.
DONE.
I'd like to use those files, but every single link is broken...
*Edit* Never mind. Found another source. I'll post upon success/failure.
*Edit again* Actually, it doesn't seem like the new link on mediafire has all the files required by the process (OP: http://forum.xda-developers.com/showthread.php?t=734475), and I can't post in that thread (because I'm a new user).
This is the post that uploaded the files: http://forum.xda-developers.com/showpost.php?p=17512889&postcount=615
So I haven't changed a damn thing yet, and all that happens when I try to put the phone in download mode is | Phone----Warning (!) Sign----Computer | screen comes up.
Even when I only plug it into a power outlet...
Flashing the IPhone was easier and more stable than this, years ago. I honestly expected better from Google.
*Edit*
OH MY GOD. Odin is going somewhere! Go, AIO Vibrant Toolbox, Go!
*Edit again*
And it stopped at about 90% with "<ID:0/003> dbdata.rfs
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
"
Well, I tried again and everything finished uploading, and got the green "pass!" for the first time in Odin.
Now my poor little 959v is stuck in a booting loop. The Samsung Vibrant screen comes up, disappears, comes up again, disappears, ad infinitum.
rushmix said:
Well, I tried again and everything finished uploading, and got the green "pass!" for the first time in Odin.
Now my poor little 959v is stuck in a booting loop. The Samsung Vibrant screen comes up, disappears, comes up again, disappears, ad infinitum.
Click to expand...
Click to collapse
959v is the not the vibrant, tis the galaxy s4g, if you odined vibrant files on your 4g then that's why you are in a bootloop
Dear god do I feel stupid. I googled it a while ago just to be sure, and it seemed to say that the V stood for "Vibrant." I guess that would be why I've been having this sneaking suspicion...
Well it's good news for you, mate. Head over to galaxy s 4g
forums and hopefully you will be able to get your phone back.
a while back (about 3 weeks) i bought me a galaxy player us version 4.0. great player.
love it honestly.
but of course i wasnt satisfied.
so i rooted.
that was two weeks ago.
and tonight. i found myself trying to flash a custom kernel. called
"steves kernel" or something like that. and to my surprise using odin, it worked. rebooted. looked around. and the only thing different was the boot logo. booted to home screen. and worked naturally. wanted to boot into te CWM recovery that came with the custom rom to backup. "obviously was too late". and i backed up and rebooted. and of course. it was stuck in a bootloop. witht he fireworks looking thing. i looked for hours on end. for a stock rom of the 4.0 US version. i found what claimed to be 4.0 but either didnt match the md5 or were intl versions or WTF EVER.
(pretty damn steamed over here)
i unplugged my galaxy from my computer. and it instantly shut off. and now what seems to be a (from my experience with a psp; correct me otherwise) in a full brick. because it wont power on. it wont flash. it wont be recognized in windows. or any OS for that matter. nothing. tried battery pulll. nothing. someone.
please.
anyone.
help.
(also think i could get my money back from bestbuy if all else fails??)
When posting things like this, post EXACT links to what you actually flashed.
Flashing something without bootloaders in Odin shouldn't have done this.
try this - forum.xda-developers.com/showthread.php?t=1386669
the unbrickable recovery should be able to get your device back into download mode. when I bricked my player to the point that it wouldn't turn on it was able to save it.
I think it works under windows, download the unbrickable resurrector and the
Samsung bootloaders from the link. you need to have Java runtime installed for it to work too.
open the unbrickable resurrector ".jar" file, and select "galxay player" from the dropdown in the bottom left. plug your player in ane above the text box it should say "device detected." or something to that effect.
now hold the "volume down" button on your player and hit the download mode button in the program. keep holding the download mode button until your device comes on in download mode. if after 5-10 seconds the screen is still black, unplug your player, restart the program and try it again. it took me 4-5 tries sometimes but it always managed to bring it back.
when you do get it into download mode, fire up Odin and flash the player bootloader from the "galaxyplayer-bootloader.zip". make sure to check the flash bootloader box on the left side or Odin. if just the bootloader was screwed up, your device might boot now.. if it gets stuck at the Samsung logo you need to put it back in download mode (power + volume down) and reflash a good rom or recovery rom (not just a kernel). if it doesn't want to go back into download mode you can use the unbrickable process again.
good luck.
i am going to try this method. do you think it will help with my 4.0 though? the tut is for the 5.0.....
this isnt the EXACT link. however this is the exact software i used. (odin was 1.83 i do believe)
http // www anythingbutipod com/forum/ showthread php?t=66820
(fill all spaces with .)
That's why in the notes section for each of Steve's kernels it says not to use CWM
Try following logo20heli's work on it here http://forum.xda-developers.com/showpost.php?p=21302504&postcount=41 since he did the same thing and got stuck in a boot loop
woer said:
That's why in the notes section for each of Steve's kernels it says not to use CWM
Try following logo20heli's work on it here http://forum.xda-developers.com/showpost.php?p=21302504&postcount=41 since he did the same thing and got stuck in a boot loop
Click to expand...
Click to collapse
i looked there. however, i couldnt find any proper download links for anything.
macdomerocker said:
i am going to try this method. do you think it will help with my 4.0 though? the tut is for the 5.0.....
this isnt the EXACT link. however this is the exact software i used. (odin was 1.83 i do believe)
http // www anythingbutipod com/forum/ showthread php?t=66820
(fill all spaces with .)
Click to expand...
Click to collapse
I'm not sure if it'll work with the 4, I doubt trying it would hurt anything though.. just wouldn't work.
exodus454 said:
I'm not sure if it'll work with the 4, I doubt trying it would hurt anything though.. just wouldn't work.
Click to expand...
Click to collapse
well if anyone can help me out. this would be tremendous. i will post the results to that in a wee bit. gotta try it first
Read my thread in development.
Hyperrunner said:
Read my thread in development.
Click to expand...
Click to collapse
yes. however if you have read my problem it is FULLY BRICKED. so i have NO clue on how to get it unbricked. meaning that i couldnt get it to go into download mode if you were here in person. now if you know a way to unbrick me. please say so. THEN i can follow your tutorial.
lol just got back from bestbuy. they swapped me out because i bought it within the last 30 days.. so im good
Alright, so here's my problem:
I just upgraded to the Galaxy S III yesterday, and today decided to try to 'root' the device. So I found the Toolkit here on XDA (from here), and went through the initial steps without any issues (driver installation, device recognition, etc..).
I then went to the 'rooting option' menu, where I selected the first--and most basic --option, which was to only install Super User, and the push the permissions.
I was following the automated guide, opened Odin, selected the correct file, 'boot-insecure-i9300xxale8-gsm.tar', and made sure only 'auto-restart' and F.reset time' were checked, and clicked 'start'. The flash appeared to have gone well, but when it tried to restart, the phone never rebooted. I attempted to reboot into download mode (Vol. Down + Home + Power), but the device was unresponsive. I then browsed around the forums a bit looking for other methods, including taking the battery out for several minutes, then putting it back in whilst holding down the 'download mode' button combination, and other various variations of that method; yet again, none prevailed.
The device gives no indicator lights when plugged in, no light up when the power button is held down, and is overall seemingly unresponsive. However, when I hold down the 'home' button alone - after about 30 seconds - a green vertical battery appears on the screen, with a little white loading indicator on it, but vanishes after about 5 seconds or so, and the device becomes unresponsive once more.
The device is not being recognized by my computer whatsoever, no beeps or anything when plugged in.
Any ideas as to what I can do?
EDIT: I have been able to get into 'Download mode' somehow, but after trying to reflash the stock rom, it went back to the 'Unresponsive' mode. I have it in Download mode again currently, so what do I do from here?
I assume it is still under warranty, since it is less than a few days old. Return it to the store claiming hardware malfunctioning.
Forget about the toolkit. In my opinion, it's quite useless (as you know by now), and it tends to automate tasks that are simple by nature.
Even although I appreciate the effort the developers of the toolkit put into it, I would never do it, since I want to have control of the entire process: I want to know exactly what is being done and why, and that is something the Toolkit won't give me.
If you want to root your phone and keep it stock, do this:
- Install the drivers for the device.
- Install SiyahKernel for S3 version 1.3 using ODIN.
- Install superSU (from market) and let it update it's binary su
- Install MobileOdin (free version)
- download the latest Samsung ROM (such as DBT [Germany] or ITV [Italy]) using CheckFus downloader
- copy the downloaded and unzipped ROM to your phone's external SD card (just the .md5 file)
- using MobileODIN, flash the ROM and select the "EverRoot" feature
- after reboot the ROM will be updated, stock, but with root
- Install TriangleAway to get rid of any annoying triangles and to reset the binary counter
Done. supposing the ROM is already downloaded, the entire process takes exactly 4 minutes.
Simonetti2011 said:
I assume it is still under warranty, since it is less than a few days old. Return it to the store claiming hardware malfunctioning.
Forget about the toolkit. In my opinion, it's quite useless (as you know by now), and it tends to automate tasks that are simple by nature.
Even although I appreciate the effort the developers of the toolkit put into it, I would never do it, since I want to have control of the entire process: I want to know exactly what is being done and why, and that is something the Toolkit won't give me.
If you want to root your phone and keep it stock, do this:
- Install the drivers for the device.
- Install SiyahKernel for S3 version 1.3 using ODIN.
- Install superSU (from market) and let it update it's binary su
- Install MobileOdin (free version)
- download the latest Samsung ROM (such as DBT [Germany] or ITV [Italy]) using CheckFus downloader
- copy the downloaded and unzipped ROM to your phone's external SD card (just the .md5 file)
- using MobileODIN, flash the ROM and select the "EverRoot" feature
- after reboot the ROM will be updated, stock, but with root
- Install TriangleAway to get rid of any annoying triangles and to reset the binary counter
Done. supposing the ROM is already downloaded, the entire process takes exactly 4 minutes.
Click to expand...
Click to collapse
Thank you so much for responding!
I have the phone in download mode right now though, as I've been able to get that far. Is there anything I can do from here to fix the issue? I really don't want to take it back up, and face the chance of confrontation if they decided to call me out on the issue.
I tried flashing the Sinyah Kernel via Odin just now, using the PDA mode, but once again, just flashes the Samsung logo for a brief second, and disappears, leaving me with a black screen.
Samsung don't seem to really care if you have rooted or not, so far about 4 people in 2 days on this and other for mums have returned phones because they have possibly bricked them, all got them exchanged with out a problem.
To unroot and return your galaxy S3 to stock for warranty watch this. http://www.youtube.com/watch?v=_8Tga_yKywc&feature=youtube_gdata_player
Zenno said:
Thank you so much for responding!
I have the phone in download mode right now though, as I've been able to get that far. Is there anything I can do from here to fix the issue? I really don't want to take it back up, and face the chance of confrontation if they decided to call me out on the issue.
I tried flashing the Sinyah Kernel via Odin just now, using the PDA mode, but once again, just flashes the Samsung logo for a brief second, and disappears, leaving me with a black screen.
Click to expand...
Click to collapse
Flash a stock rom for your phone and location or if it was a branded phone flash that .
Even if it does not boot you stand a better chance under warranty .
Say you where doing a Kies update and it just failed to reboot .
jje
JJEgan said:
Flash a stock rom for your phone and location or if it was a branded phone flash that .
Even if it does not boot you stand a better chance under warranty .
Say you where doing a Kies update and it just failed to reboot .
jje
Click to expand...
Click to collapse
I tried to reboot the stock firmware 'boot-stock-i9300xxale8-gsm.tar', but when Odin failed to reboot the phone, and I manually put it back into download mode, it still said my binary was 'Custom'.
Should I be trying to flash that under 'Bootloader' in Odin or something? Because I've been doing 'PDA' and it hasn't been working.
Download an original, stock ROM from samsung-updates.com or use checkFus downloader.
That is what you'll flash.
This is the one I use: http://samsung-updates.com/get/1932/Samsung_Firmware_GT-I9300_DBT_I9300XXALF6_Android_4_0_4.html
After some further browsing, I was able to fix it thanks to this post here, posted by 'mskip'.
Whew! That was stressing. Thanks guys for helping out though!
How to get out of hard brick to download mode
Zenno said:
After some further browsing, I was able to fix it thanks to this post here, posted by 'mskip'.
Whew! That was stressing. Thanks guys for helping out though!
Click to expand...
Click to collapse
After hardware brick, how did you get it back to download mode agian?
i cnat do anything , no turn on no charging, nothing, how you do it?
i think if i can get it back to dowload mode, i can flash out the stock rom again.
any advise will help
Pull the Batteery
jiafu790617 said:
After hardware brick, how did you get it back to download mode agian?
i cnat do anything , no turn on no charging, nothing, how you do it?
i think if i can get it back to dowload mode, i can flash out the stock rom again.
any advise will help
Click to expand...
Click to collapse
Remove the battery for about 2 minutes, replace it and immediately try to go into download mode. This worked for me
same problem
Hard bricked it too, flashed a wrong rom made for international model, i have the att model are you sure taking out the battery works?
Zenno said:
EDIT: I have been able to get into 'Download mode' somehow, but after trying to reflash the stock rom, it went back to the 'Unresponsive' mode. I have it in Download mode again currently, so what do I do from here?
Click to expand...
Click to collapse
I have the same problem! Do you know how you got into download mode?
Surge411 said:
I have the same problem! Do you know how you got into download mode?
Click to expand...
Click to collapse
Just keep trying,I must have removed the battery and pressed the buttons over six times to get into download mode. Hope you get there.
I've searched for hours for different solutions and have tried them all. I'm on my last leg, and I can't wrap my head around what is going on.
I'm running an S2 with ShoStock3 rom. It's been rooted for over a year now without any major hiccups at all. Last night, it froze on me. Usually when it does this, I just force-restart by holding the power button down until it cycles. Phone usually boots right back up, and I'm all set. This time it just stayed on the boot screen. For eternity. I let it sit like that for more than 45 min, and it never budged. Turn it off from the booth screen, it'll boot right back up. I can go into download mode, but not recovery, and every little trick I've tried works.
I've tried flashing new kernels with ODIN. Tried various recoveries, like Philz and even went as far as the one touch factory ROM and using the regular method for getting the stock ROM. Nothing. Maybe I'm doing something wrong. Most people who have this problem only recently added a new ROM or modified something. I haven't touched the ROM, kernel, etc. for over a year before this happened.
ODIN never makes it far when trying to flash anything. It depends on what is being flashed. It never gets past nand read/write. It never gets past boot.bin. It never gets past factory.img. Etc. Etc. I don't know if maybe something isn't going through between computer and phone, and that's why I'm not having success or what in the world is going on. Every tutorial or help I found confidently stated that all you have to do is flash this kernel, go to recovery, clear cache, and you're all set. But I feel like I'm the odd man out.
I'm afraid that this won't see much attentions, as the S2 is far from new, but like I said I am on my last leg. I just don't understand how it stops working from cycling power. I also don't understand how every attempt doesn't even scratch the surface. Any and all help will be greatly appreciated
The most basic step is to verify you're using the correct button combo to get into recovery: power+both volume keys, then release after the second Samsung logo.
SteveMurphy said:
The most basic step is to verify you're using the correct button combo to get into recovery: power+both volume keys, then release after the second Samsung logo.
Click to expand...
Click to collapse
^^ while the device is NOT USB connected to a computer.
Actually, you're lucky. This device is so popular, even though is it getting old, that there are still a handful of knowledgeable people hanging around.
You need to get into recovery. As Steve and Cyril have said, try the correct button combination, and post back here to verify that you are using the correct combo and that it will not go into recovery.
If you do get into recovery, perform a wipe data/factory reset and see if that gets your phone to boot into the system.
If you are unable to get into the recovery with the correct combo, then you may have one of several possible issues. The first possibility to troubleshoot is nand read/write corruption. Do the following:
Instructions to clear nand read/write corruption. Instructions are specific; do them in order, and don't skip.
Odin3 v1.85 is recommended.
1) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning. (Please observe normal bootloader flashing caution.)
2) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning
3) Flash the Tar.md5 of the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
I have done the correct button combination for recovery, I promise you that. It brings up Samsung logo first, cuts off, and brings it up a second time, but releasing does nothing. I've tried it several times with different delays as well.
creepyncrawly said:
Instructions to clear nand read/write corruption. Instructions are specific; do them in order, and don't skip.
Odin3 v1.85 is recommended.
1) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning. (Please observe normal bootloader flashing caution.)
2) Download the Tar version of Siyah 2.6.14 Kernel. Flash it in PDA. Without ticking Re-Partitioning
3) Flash the Tar.md5 of the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
Click to expand...
Click to collapse
I've actually tried this. On step one, it hangs up on "NAND Write Start!!", just like everything else that tries to get flashed.
To clarify, I should be flashing the I777 UCKH7 sbl.tar file, correct?
Luckily for me I qualified for a free upgrade from ATT for an S4, but I don't want to give up on this phone just yet. Especially with all of the data I have yet to recover from it.
XxArxAngelxX said:
I have done the correct button combination for recovery, I promise you that. It brings up Samsung logo first, cuts off, and brings it up a second time, but releasing does nothing. I've tried it several times with different delays as well.
I've actually tried this. On step one, it hangs up on "NAND Write Start!!", just like everything else that tries to get flashed.
To clarify, I should be flashing the I777 UCKH7 sbl.tar file, correct?
Luckily for me I qualified for a free upgrade from ATT for an S4, but I don't want to give up on this phone just yet. Especially with all of the data I have yet to recover from it.
Click to expand...
Click to collapse
Yes, that is the correct secondary boot loader.
Next, you must assume that there is a connection problem between the phone and the computer. The micro usb port, the cable, the usb port on the computer and the computer itself are all possible weak links in the connection. So try different cables, different ports on the computer, escpecially one directly connected to the mother board, even try a different computer. You can not proceed until you can get the phone to receive a flash and pass. A few people have even reported that they finally were able to complete a flash just by trying repeatedly over and over until it finally passed.
creepyncrawly said:
Yes, that is the correct secondary boot loader.
Next, you must assume that there is a connection problem between the phone and the computer. The micro usb port, the cable, the usb port on the computer and the computer itself are all possible weak links in the connection. So try different cables, different ports on the computer, escpecially one directly connected to the mother board, even try a different computer. You can not proceed until you can get the phone to receive a flash and pass. A few people have even reported that they finally were able to complete a flash just by trying repeatedly over and over until it finally passed.
Click to expand...
Click to collapse
Tried using different computer. Brand new cord. Multiple times tried. Different ports. I dunno, it's doing the same thing. It stops whenever it gets to NAND Write Start.
EDIT: Tried something I saw in another thread. Used stock binary with pit file. Never finished, so aborted it. Now phone doesn't come on at all for any reason whatsoever. -.- Pretty sure I fried it