Database Develop

Bricked HD?

I recently synced my HD after having flashed the EVO Grid 1.8 ROM.
Since it took over half an hour I disconnected the phone from the computer during the sync process. Now the screen freezes as soon as the smart mobility screen shows up. I soft reset' the phone as well as I tried hard resets. Still the phone doesn't go beyond the smart mobility screen and freezes.Is there another option to get the phone back apart from resetting it? Or is it completely bricked now. I've always successfully flashed the roms, so it can't be connected to a wrong ROM flash.Thank you for a feedback.

What you can try is place an ROM on your memory card (BLACIMG.nbn) and flash it. (shut down phone, hold vol down and power up).
Maybe this will do the trick. Good luck

Can you still get the phone into bootloader mode (tricolor screen)? It's likely you can - then just re-flash the rom (although to be safe I'd download it again).

Did you follow this guide to initally flash rom? If not, I'd suggest you do. As pointed out above, if you can still get into bootloader your device is not bricked. Just follow guide and reflash rom

just do like "jontelfer" said go to 'bootloader' for getting 'Tricolor' by pressing 'Volume Down' and 'Power' 1 time. Then u can see 'tricolor' and re-flash what ever rom you want.
I had try 'Xannytech ROM Grid Leo 2.5 (Internal Rel. 4.2.5.202)' and found the same as your problem 2 times already.
Now I'd change to test others.

I would be tempted to flash it back to original SPL and ROM and then start again from scratch. This happened to me a few months back, I couldnt flash any cooked ROMS at all until I reverted back to stock and started again.

Yeah and do not forget to hard reset after flashing. It can sound useless but it really helped me when I got some problems with some roms...
- Bya -

Thanks everyone. I flashed to a different ROM and it's working again now.
It's tougher than I thought to find an innovative, graphically sophisticated and most of all stable ROM.

good to hear had this ones before and gladly figured out how to go back and flashed it again with a stable rom!!

[Q] Stuck after boot animation. No Recovery/Download

Hi guys,
I think I finally managed to brick my phone. Everything was working perfectly fine, until today when decided to try GB's Steam kernel.
So a little background first, to make things quicker:
- I was able to open download and recovery mode before, even after doing a odin3 one click restore twice.
- I've tried a Cognition and moved to DarkyYtt3r. Went from 7.0.1 to 7.5 to 7.8 to 8.0.1, no issues.
- Changed the kernel and modem several times. The last one I tried was glitterball's uc/ov stable (no charging death).
- Current set up before this mess:
-- ROM: DarkyYtter v8.0.1 > http://forum.xda-developers.com/showthread.php?t=890429
-- Kernel: gb-reorient-fixed-ocuv-f-cwm.zip > http://forum.xda-developers.com/showthread.php?t=887315
-- Modem: TLJL3 I think.
Everything working beautifully.
Today I saw this thread: http://forum.xda-developers.com/showthread.php?t=903238 ... gb's steam kernel. since no one was having major issues, I made a backup of my current rom using CWNand decided to install the kernel using SGS Kernel flasher, according to instructions.
Cool. I've flashed kernels before a few times. No big deal. And I figured, I'm able to get into Recovery or worst case scenario into download mode. I flashed the kernel, reboot, got into Steam's recovery. Looked around. Activated a couple of tweaks although I don't remember which ones.
Rebooted and this is where the issues began. I got the "intro" window you get with i9000 roms (keyboard intro, syncing, etc). A lot of apps were force closing, including facebook, twitter, rom manager, ADW Launcher, etc.
Ok, so I rebooted to Steam recovery and deleted the cache. Went back and the same problem. At least I was able to boot the system.
I said, oh well, let's go back to our backup. Booted Steam's recovery, and tried to recover from the last backup.
It worked for one boot. Not sure what I did, I don't remember, but after trying to boot again, the phone displays the AT&T screen, the GT-I900 screen and then the Galaxy S screen. I then feel the force close vibration, and the screen goes black. I can touch the softkeys and they blink, but I feel the FC vibration every 10 or 15 seconds.
Somewhere along the line something bad happened.... but here is what's bothering me. I cannot get back into download or recovery mode anymore. Been there all day trying to make it work with no luck at all.
So, more importantly, somewhere along the line, between rom flashes, or something, I lost the ability to get into recovery or download mode. I've heard that I900 roms have different button combos, but nothing works
I'll buy a few resistor packs tomorrow, and some cables just in case. I'm afraid that I won't be able to boot into download mode this way either.
also, adb is not detecting the phone. tried both windows and linux. if I could only get it even for one second so I can send a adb reboot download... but no
Do you guys have any ideas?
Thanks!

cumanzor said:
Hi guys,
I think I finally managed to brick my phone. Everything was working perfectly fine, until today when decided to try GB's Steam kernel.
So a little background first, to make things quicker:
- I was able to open download and recovery mode before, even after doing a odin3 one click restore twice.
- I've tried a Cognition and moved to DarkyYtt3r. Went from 7.0.1 to 7.5 to 7.8 to 8.0.1, no issues.
- Changed the kernel and modem several times. The last one I tried was glitterball's uc/ov stable (no charging death).
- Current set up before this mess:
-- ROM: DarkyYtter v8.0.1 > http://forum.xda-developers.com/showthread.php?t=890429
-- Kernel: gb-reorient-fixed-ocuv-f-cwm.zip > http://forum.xda-developers.com/showthread.php?t=887315
-- Modem: TLJL3 I think.
Everything working beautifully.
Today I saw this thread: http://forum.xda-developers.com/showthread.php?t=903238 ... gb's steam kernel. since no one was having major issues, I made a backup of my current rom using CWNand decided to install the kernel using SGS Kernel flasher, according to instructions.
Cool. I've flashed kernels before a few times. No big deal. And I figured, I'm able to get into Recovery or worst case scenario into download mode. I flashed the kernel, reboot, got into Steam's recovery. Looked around. Activated a couple of tweaks although I don't remember which ones.
Rebooted and this is where the issues began. I got the "intro" window you get with i9000 roms (keyboard intro, syncing, etc). A lot of apps were force closing, including facebook, twitter, rom manager, ADW Launcher, etc.
Ok, so I rebooted to Steam recovery and deleted the cache. Went back and the same problem. At least I was able to boot the system.
I said, oh well, let's go back to our backup. Booted Steam's recovery, and tried to recover from the last backup.
It worked for one boot. Not sure what I did, I don't remember, but after trying to boot again, the phone displays the AT&T screen, the GT-I900 screen and then the Galaxy S screen. I then feel the force close vibration, and the screen goes black. I can touch the softkeys and they blink, but I feel the FC vibration every 10 or 15 seconds.
Somewhere along the line something bad happened.... but here is what's bothering me. I cannot get back into download or recovery mode anymore. Been there all day trying to make it work with no luck at all.
So, more importantly, somewhere along the line, between rom flashes, or something, I lost the ability to get into recovery or download mode. I've heard that I900 roms have different button combos, but nothing works
I'll buy a few resistor packs tomorrow, and some cables just in case. I'm afraid that I won't be able to boot into download mode this way either.
also, adb is not detecting the phone. tried both windows and linux. if I could only get it even for one second so I can send a adb reboot download... but no
Do you guys have any ideas?
Thanks!
Click to expand...
Click to collapse
Did you ever get this problem fixed? The reason I ask is because I'm in this same situation.

We seem to be having the same problem also... Nothing has worked for me so far
http://forum.xda-developers.com/showthread.php?t=960419

Pull your battery, pull your sd card, hold the volume button and plug in the usb cord, this will get you into download
Sent from my GT-I9000 using XDA App

Keep hope alive glaze!
Sent using XDA App

Im going to get a jig hopefully all goes well.

USB/Charger reboot the phone, download mode lost, vibrant rom on i9000

OK guys I really badly need some help. My phone is in a non-workable state and I am starting to run out of options.
I did some mistakes but I will try to take out the details to list mostly the fact, hoping someone will take the time to give me directions.
- I have a galaxy s I9000 (switzerland/orange)
- I had upgraded to 2.2 via Kies.
- I got tired of the phone becoming increasingly slow. I found out about voodoo lag fix. I read 3000 forum posts, documentation and stuff, and when everything seemd easy enough, I installed voodoo via Odin.
- Here problems started. After installing voodoo, the phone booted, but the robot voice said "convert data partition. Not enough space on partition". Then again. And again. It was stuck in a boot loop. This problem doesn't seem to be documented anywhere i could find. The only instructions I could find on how to disable voodoo were to create some files on the disk, not very helpful when you can't boot the phone.
- I found a couple of threads with people who had the same message, and the advice their were given was to flash another rom.
- So I went to samfirmware.com and downloaded 2.2.1 for I9000 (JS8). I installed it through Odin. The phone booted, showed me the Galaxy S screen, then went black. Then it would vibrate every 20 seconds or so. Once, then 3 times in a row. I waited 30 minutes because in some places it said that may take long, but the situation didn't change. I rebooted, tried again after taking about the battery, wiped data, reset factory settings etc. The phone state wouldn't change, and I started to get a little desperate, because this was a stock rom, and if that didn't work...
- I read 3000 more threads, and phone a guy who had been in this situation, and got out of it by first installing "Eugene's JK2 froyo that never bricks" and then after wards reinstalling the stock rom.
- So I installed Eugene's rom. I knew it was trouble that it was a vibrant's rom, but I figured, I had read everywhere that as long as your phone supported download mode you could still always re-flash a new rom, so I decided give it a try.
- And the phone booted. Asked my pin, loaded stock android and all. I was happy at first, but then new trouble came. Now, whenever I plug in the USB, the phone's screen goes black after 4-5 seconds. When I unplug it, phone reboots. No charging battery appears when I plug the turned off phone on the charger.
- And worst of all, the buttons got mixed up. Vol up is vol down now. But more of a problem, 3 button recovery and 3 button download mode don't work anymore. I couldn't find a way to get them back. So I can't flash a new rom with Odin :-/.
- My latest was to install rom manager since I can access the market. I downloaded the tedgy rom. Installed the "clockwork recovery mode" from Rom Manager. It asked me if I had I9000 or vibrant, wasn't sure what it expected since I have now a vibrant rom on an I9000, but I put in I9000. Then I reboot telling rom manager to install Tedgy. I get a recovery mode screen which offers to reboot/reinstall packages/wipe data, then does a couple of operations, and finally gets stuck on :
can't open /cache/update.zip
(bad)
installation aborted
So there I go, with a vibrant rom on my I9000 (rooted, at least), a phone that can boot a half-functionnal android, but with a useless cable plug, an unchargeable battery, and a download mode I couldn't find... And waiting for my wife to get back with her phone so I can charge my battery again...
Any help or lead to help me get another rom installed on this phone again would be *greatly* appreciated. What other ways do I have to access download mode ? Or is there a way to get to it despite my buttons being messed up ? Maybe the rom manager issue can be fixed ?

OK well I got out of it somehow.
In case someone else had this same issue, here's how I got out of it :
1) Install ADB.
2) launch Odin
3) go to adb folder in command line and type "adb reboot download" but no enter just yet.
4) plug the usb cable on the phone.
5) type enter in the adb shell in the small window of opportunity you have before the screen goes blank. This reboots the download mode and allows new flashing via odin.

Any answer for this thread?
Did you fix the problem?
I'm stuck with the same case...

[Debricking] Hang at samsung animated logo

Hi everyone, I spent all day trying figuring this out, even if probably the solution was really stupid, so I thought of doing a little post for future reference. If you have no time for my babbling, feel free to go to the short version (I wanted to put a link here, but I still have to learn how to do it and it's almost dinner-time...). If this post happens to be a duplicate feel free to remove it.
=== Whole story ===​A week ago I got a Galaxy SIII mini N (GT-I8190N) and just kept it that way because I didn't had a win pc to use Odin. Yesterday I finally came back to my parents, powered up the win machine and followed an awful lot of different guides to manage to install the Macław CM 10.1. So, for short: installed CWM touch trough Odin, installed the root zip trough CWM and finally installed CM 10.1 & Gapps trough CWM. Here I did my first mistake: the first thing I did after installing CM was formatting internal and external SDs. Where the Nandroid backups of the working Samsung firmware were.
After some experiments I decided to go back to Samsung stock (reason 1: no gtalk, only hangouts, reason 2: NFC support still in development, reason 3: trying to restore SMS from a SmsContactsBackup I (luckily) had I messed up the SMS DB so much the app couldn't start). NOTE: Macław's ROM is amazing, I'm surely going to try it again when NFC support comes up. Sadly, I am an idiot who thinks he knows better so I ignored all the warnings of doing a wipe of data/cache and restoring the Samsung original recovery. I just went to Kies for a "Firmware upgrade and initialization" instead.
The result was a disaster. The phone rebooted but hanged at the Samsung animated logo. After a lot of hanging I decided to redo a Kies firmware upgrade. Obviously I had no luck. So I switched to Odin, took the image Kies downloaded (since I didn't want to wait an hour and an half to the download from unofficial sites) and flashed. And flashed. And flashed. Always without success. After a little bit I decided to try changing Odin options (repartition, NAND erase etc). Still nothing. So I started trying all the guides out there (here?): repartitioned with a PIT file, reflashed a CWM, reflashed stock recovery, various combinations in different orders of all the "solutions" above... You guessed right: nothing worked.
Since I read somewhere that there are Galaxy have 25 partitions (what the ****???) and saw that Odin was flashing only 8 or so I decided that something some the other partitions was missing, so I switched to Heimdall. Since the Win version didn't want to start, I did a fresh Ubuntu 13.04 install (lucky for me I happened to have an empty HD waiting to be installed on the server that I could use for an afternoon ), installed Heimdall, started figuring out how it works, realized I needed a custom-made package (nowhere to be found, apparently), started looking into the partition scheme to understand where the problem could have been... Finally I realized my skills are a tiny little bit inadequate for that and found a reference somewhere to a "hard reset".
In all this it never occurred to me to try and enter Samsung recovery. The first thing I noticed was that it didn't start right away with VolUP + Home + Power, but I had to keep them pressed a lot longer than what it's needed to go in download mode. In practice the SIII mini logo went up two times before showing the android with the open belly. Then finally the recovery appeared, I navigated to wipe data and cache with the volume buttons, accepted with the power button and rebooted. Thus I finally had a Samsung animated logo that was followed shortly by an "installing applications" loading bar and the first start configuration tool.
So, what I learned today:
1) Samsung tools are not necessary evil
2) if you don't understand what you're doing and you're doing it anyway, be prepared to suffer
3) we probably need a unified guide/troubleshoot the whole community can edit (wiki-like). Threads are great, but it's really easy to miss the obvious (for the whole time I was sure it was a bootloader problem, never occurred to me that there could have been some data left... also because I did a NAND wipe through Odin and I thought that was supposed to wipe personal data...) and often propose a solution without explaining the rationale behind it. I'm sorry if there's something like that out there somewhere, I wasn't able to find it
Thanks to you that bore my babbling
And now it's time for:
=== The short version ===​
Problem: I messed up doing a Kies reset after installing a custom rom (CM10.1) without the dues precautions; the result was a phone caught in an endless loop at the Samsung logo. Installing firmware with Odin didn't solve a thing.
Solution: I booted in recovery (volume up + home + power) and wiped data and cache. After that I rebooted and waited a little bit, a progress bar appeared and everything was fine (well phone was at factory default but at least now it's working ).
I hope all of this could be useful to someone

[Q] Help.. AP mode only - after succssful root

I apologize first that I am completely confused after reading posts for hours trying to fix my problem. Second, I know enough to get myself into trouble & I've succeeded. I'd been running Icarus 183 on my previous Bionic for months, so after shutting the truck lid on it, I set out to install the same on my replacement. Not realizing that JB had been released is where my ^$&#& happened. Here's the order of what I did which has lead me to a phone that boots to AP mode when you turn it on, or to the menu when holding both volume keys and powering on. If I go thru the power keys and select normal boot, I get the red dot and the screen will stay backlit.... nothing else.
1] New replacement phone: I used the Virtual Machine program to root.... This worked perfectly.
2] Goomanager had reinstalled from my google account, but I don't think I had ever used it.
3] I had installed Icarus thru the safe strap (3.05, I think) on my old phone. I went ahead and installed this again (no problems so far)
4] I started to install Icarus thru safestrap again, but I didn't like partitioning, so I figured I would download and install a rom using GooMgr
5] I believe I chose a rom named "Carbon" from those roms GooMgr stated was compatible... When I ran GooMgr nothing appeared to happen, so I rebooted the phone thinking I would just go ahead and install Icarus using safestrap.
6] When I pressed the button to boot into safestrap, the Carbon rom I had started to load began to run.. (apparently GooMgr could not reboot due to having safestrap installed??)
7] Naturally, the installed failed, giving me the dead android symbol... I removed the battery to reboot, but only AP mode comes up.
8] I am still at this point, having tried RSD Lite 5.7, updated Motorola drivers, and have now tried as who knows how many fxz files to restore it..
9] RSD Lite continues to fail at step 5 , where the phone reports "FAIL"
All I want is the stock JB back, so I can be up an running again.

WOW! Sorry for the problems. I wish I can help but I'm not too familiar with returning your phone back to stock. I do have one piece of advice. Go to YouTube and look up Tomsgt123. His website is rootjunky.com. Really great guy. He responds very quickly. Good luck.
Sent from my XT875 using xda app-developers app

If fxz fails why not try recovery mode flash using sd card?
Just follow the directions for 'manual JB' flash.
http://www.android.gs/update-motorola-droid-bionic-official-android-4-1-2-jelly-bean/

[/COLOR]Use a more recent version of RSD Lite for the latest JB FXZ files. 6.1.5 is the current RSD Lite release version.
https://db.tt/Tya2balw
You don't need to install the MTK patch included with this release.

UPDATE.. Since I need this phone for my business, I couldn't take the extra time this week to sort it out... Ended up going into a Verizon store & told them what I did (honestly)... They were surprised I was telling the truth & made arrangements for a warranty exchange.. Got the new phone today and up & running on stock rom... I'll be more careful and thanks for the advice above.. I'll make sure I am using the correct software next time.
Thanks for the responses.