Database Info

[Q] Is Infuse(current version) installing or is Phone Bricked???

I am def a newB and have taken the plunge into custom roms. I followed the directions to installing Infuse with modded 3e recovery and cwm going to rom mgr and doing the download and now my phone is just displaying "SAMSUNG" across screen its been about 10 minutes. Question is, is the rom installing or is the phone bricked and what are the signs of a brick? How would long does a wiped Infuse download usally take?

It shouldn't take that long
infuse 4g "a lot a screen real estate"

So how would i know if the phone is bricked???

supadupadoug said:
So how would i know if the phone is bricked???
Click to expand...
Click to collapse
take battery out and try turning it on again after putting it back in. if it starts booting and you get the lady talking, your good, but if it just sits there, you most likely have a brick.
No worries though. Just follow these steps to get back to stock and your golden:
Ultimate Unbrick Thread:
http://forum.xda-developers.com/showthread.php?t=1116251
once your back to stock you can flash the community kernel via odin:
Community kernel:
http://forum.xda-developers.com/showthread.php?t=1119598
Once this is done, your rooted (just need to download superuser from market), and you have been lagfixed(with the lady talking on boot) and you have CWM to flash roms easily (accessible via: turning phone off, holding down volume buttons, press power till you see samsung logo, then keep holding volume buttons till red text comes up)
Then you should be back to the game

I really appreciated my heart is racing right now with uncertainty. I havent done what u mentioned but i did hold the power button and volume keys and now I do have access to a red menu that says ClockworkMod recovery v2.5.1.3 - Voodoo lagfix. does this mean anything???

supadupadoug said:
I really appreciated my heart is racing right now with uncertainty. I havent done what u mentioned but i did hold the power button and volume keys and now I do have access to a red menu that says ClockworkMod recovery v2.5.1.3 - Voodoo lagfix. does this mean anything???
Click to expand...
Click to collapse
try to reboot... and relax, your phone will be fine

If you want, stop into the #infuse4g channel on webchat.freenode.net
I'm in there and could probably help you out better

Im at work LOL so they have filters on video but I've tried to reboot and the screen displays SAMSUNG never heard a lady or anything like that, but I'll give it some time and if all else fails follow the procedure u suggested previously. S/N I while in the red screen i selected to apply the unzip package update.zip. the screen flashed and quickly and i guess it did its thing the went back to the menu and i chose reboot so I guess we will see what happens... I really do appreciate your time and effort in helping me resolve this problem

supadupadoug said:
Im at work LOL so they have filters on video but I've tried to reboot and the screen displays SAMSUNG never heard a lady or anything like that, but I'll give it some time and if all else fails follow the procedure u suggested previously. S/N I while in the red screen i selected to apply the unzip package update.zip. the screen flashed and quickly and i guess it did its thing the went back to the menu and i chose reboot so I guess we will see what happens... I really do appreciate your time and effort in helping me resolve this problem
Click to expand...
Click to collapse
the update.zip wont do anything. there's nothing to flash...
Another thing you can try is to flash the rom again, since you have access to red CWM... then if that doesnt work, follow the unbrick procedure

May be dumb question but how do i flash rom from red screen(link???) thanks

Assuming you have the zip for the ROM installed to your internal SD (CWM can't find stuff on the external SD unfortunately...)
Use VolUp/VolDown to navigate through CWM.
Wipe Data/Factory Reset should always be done when changing from one ROM to another. Usually not needed when updating a ROM from a previous version of the same one.
Then choose "Install zip from sdcard" then "Choose zip from sdcard" and navigate to the zip for the ROM.
However if Voodoo Lagfix is interacting strangely with your phone, other steps may be needed.
Good news is that if you can get into CWM, at least your kernel is in decent shape.
For whatever reason I never heard the lady speaking when I installed my ROM, although I may have gone into the other room and done something else.

Well for some reason I cant go to the page with the GTG unbrick download which sucks idk maybe u can email me the zip file [email protected] if not I guess i'll be back once I get home and try to figure this thing out. smh phone down

Thanks Entrophy512 I will give this a try and get back w the results

Entrophy512 followed your directions screen is displaying SAMSUNG you have any idea about how long the phone should be in this state???

Not long
5 minutes ish
is the lady talking??

well yea mine is stuck on that screen for well over 15 mins. guess i have to start at square 1. Does anybody know what this means???

supadupadoug said:
well yea mine is stuck on that screen for well over 15 mins. guess i have to start at square 1. Does anybody know what this means???
Click to expand...
Click to collapse
could be anything. something went screwey on the flash... so just try again and follow the instructions

OK finally after reading and digging deep into the INFUSE I found the correct zip file which was in the clockworks recovery folder which i accessed though the red menu. I am now running infused 1.5.3. Thank you all for the support. One last question how do I refress all my data from stock. I did a Titanium backup of everything how to i get all that stuff onto my phone???
And again many thanks

supadupadoug said:
OK finally after reading and digging deep into the INFUSE I found the correct zip file which was in the clockworks recovery folder which i accessed though the red menu. I am now running infused 1.5.3. Thank you all for the support. One last question how do I refress all my data from stock. I did a Titanium backup of everything how to i get all that stuff onto my phone???
And again many thanks
Click to expand...
Click to collapse
Install TiBu from the market.
Restore user apps + data - don't restore system data. You may in that case still need to put in the info for your Google account, etc and tweak some settings.

Ok im finally up and running. Question what is the proper way to turn the device completely off. I tried yesterday and I see I have an extended power off menu with various options. What do they mean? Yest I chose turn phone off and the phone went to the downloading screen with the big yellow android w the shovel. Again thanks to you all.

[Q] help dl mode not working anymore and won't go into CWM

Hi guys!
I'm a semi noob when it comes to all this, BUT I did thoroughly look over the forums for almost 8 hours now trying to figure all this out on my own, but now I think I may have taken a turn for the worse.
First of all I have a Samsung Galaxy S Vibrant 4g. I first rooted my phone successfully using the SuperOneClick, no problem. Then I wanted to use team whiskey's Bionix Frost rom (http://forum.xda-developers.com/showthread.php?t=1119986) which I LOVED on my other vibrant galaxy s (not 4g).
I then went to this thread to get CWM (http://forum.xda-developers.com/showthread.php?t=1099374) which was placed in all the right folders I believe, BUT here was when the problems started....
I did not run the update.zip file twice... I went in CWM mod (by pressing the volume buttons and power button) and then reinstalled packages and then selected the update.zip....THEN I thought I could go ahead and install the Bionix rom by selecting that zip file..
It unloaded and then went to reboot...but the screen never passed the GALAXY S 4g logo....
so back to the forums I went. I really couldn't find anything that would help except load the old firmware with odin, so I went to http://www.akaskriller.com/free/vibrantflashing1.php and followed his steps..but I think that was a bad move because these files aren't particularly for my 4g
so when I went to flash the original stock (which was 2.1) I think I really screwed it up because it said FAIL when I tried to run it through odin..
now here's the big probem:
I can't get into download mode any longer (by pressing JUST the volume buttons and then usb and then battery). I took the picture and attached it, so now what can I do?
the picture is a cellular mobile phone connected to a yellow triangle with an exclamation point connected by dots to a computer.
please please please help if you can and leave step by step instructions if possible. I would greatly appreciate it, and I know it's stressful reading these things, but I honestly have tried for 8 hours now trying to figure this out on my own, and now I'm asking the community. Thanks!

[Q] Kindle Fire and Kindle Water

So I found this app today and was thrilled at it's potential simplicity (read: Noob Heaven) but after following all of the steps three times I still find myself booting into the stock Fire OS.
Anyone else having this issue?

Yes, I have an issue. This does absolutely nothing. I took a whole day to weigh the pros and cons of rooting and what I would do if it all went wrong. Good joke. Absolutely nothing happened.

Just my luck...
It turned out that my hellish 12 hours trying to get things going with their programme exposed errors in their code so I was the sacrificial lamb. I wound up following another method that I found on this site.

Kindlewater is a root tool, not a new OS
feroxcvpiditas said:
So I found this app today and was thrilled at it's potential simplicity (read: Noob Heaven) but after following all of the steps three times I still find myself booting into the stock Fire OS.
Anyone else having this issue?
Click to expand...
Click to collapse
Hi, I've rooted with kindlewater on my mac. At first I thought nothing had happened because I didn't reboot once it was complete.
If you reboot, you will see the firefirefire logo come up, and it tells you to press the power button until it turns orange, whereby the CWM recovery program, which is the program you will use to install an Android SDK (the new OS you were expecting) or run backups or install other .zip files among many other tasks.
-> if you do not press the power button while the firefirefire logo is displayed, the kindlefire will boot into the regular stock OS.
The yellow triangle with a flame in the middle (like a road sign spelling "caution: ") is the firefirefire bootloader's logo. Wait a few seconds, the firefirefire logo goes away and is replaced by the animated words "Kindle Fire" and it then boots normally.​-> If you do, it will boot into CWM recovery and the screen will be all black with red text and a hierarchical, touch-navigable menu structure.
The kindlewater app is not intended (as far as I can see) to actually install alternate OS options for you. It is meant to "root" your device, or in other words, give you superuser permissions such that you are permitted to make permanent system changes to your device.
To summarize: The visible change to your kindlefire after running kindlewater doesnt become visible until you reboot, at which point you will be able to see the change in the bootloader program.
Hope that helps!

sisterdelirious said:
Hi, I've rooted with kindlewater on my mac. At first I thought nothing had happened because I didn't reboot once it was complete.
If you reboot, you will see the firefirefire logo come up, and it tells you to press the power button until it turns orange, whereby the CWM recovery program, which is the program you will use to install an Android SDK (the new OS you were expecting) or run backups or install other .zip files among many other tasks.
-> if you do not press the power button while the firefirefire logo is displayed, the kindlefire will boot into the regular stock OS.
The yellow triangle with a flame in the middle (like a road sign spelling "caution: ") is the firefirefire bootloader's logo. Wait a few seconds, the firefirefire logo goes away and is replaced by the animated words "Kindle Fire" and it then boots normally.​-> If you do, it will boot into CWM recovery and the screen will be all black with red text and a hierarchical, touch-navigable menu structure.
The kindlewater app is not intended (as far as I can see) to actually install alternate OS options for you. It is meant to "root" your device, or in other words, give you superuser permissions such that you are permitted to make permanent system changes to your device.
To summarize: The visible change to your kindlefire after running kindlewater doesnt become visible until you reboot, at which point you will be able to see the change in the bootloader program.
Hope that helps!
Click to expand...
Click to collapse
My issue was related to faulty code by the creators which we discovered during chats/emails which prompted them to correct and issue a new update. I opted for other methods that day as I didn't want to wait for their corrections.
Nonetheless, I'm sure others will appreciate your input and advice. Nice of you to take the time to detail it.

Hey guys... I just came across this thread... If you ever have questions email me! I'm willing to help! I see that it has been resolved but I would just like to add, PLEASE LET ME KNOW IF IT DOESN'T WORK! That is the only way I can get it working!

When I buy a Kindle Fire with its latest Firmware from Amazon i think. Can I compleetly decripple this device so that I have something similar to the Samsung Tablet?

Can't get into bootloader menu

EDIT: SOLVED! I did some additional googling and stumbled across the answer elsewhere on the internet. Once I was in the yellow triangle/exclamation mark screen, pressing Volume Up and Volume Down at the same time brought me into the boot menu. Whew! Back to flashing!
Original message:
I've been messing with my wife's phone and think I may have screwed something up pretty seriously.
I had a CM9 beta installed, and thinking I would update it to the latest version I first installed the D2G bootstrap, then tried to reboot into CWM. (I think this was a noob error...I have a Galaxy Nexus, which makes life so easy, and only mess with this D2G when my wife is really complaining about bugs or slow performance.) Anyway, obviously it wouldn't boot. So, I SBFed using the 4.5.608 SBF file. Upon attempting the first reboot, it got to the droid boot animation and I thought I was home free. It bootlooped. "No problem" I thought, I'll just wipe the user data. So I tried the "hold X" trick. I did get to the screen with the android and the ! in a triangle, but when I try the next step "press the physical search button to enter the bootloader menu", nothing happens. Literally nothing. I've tried many different combinations of many different keys, and I'm always looking at the android with the exclamation mark. Rebooting always results in a boot loop.
Anybody have any suggestions? Thanks in advance.

That's not bootloader, that's Recovery.
Just saying.

[OPO] [BRICK] Screen failure after solution

Hi all,
So my I decided to bring my old Oneplus One back to life by following some 'Unbrick Tutorials'. I've tried a couple but nothing seems to work.
So I followed this tutorial as last resort:
http://www.androidbrick.com/unbrick-oneplus-one-two-3-3t-qualcomm-hs-usb-qdloader-9008/
Everything went like it's supposed to happen I guess. My cmd window gave me positive info (Things like: flashing recovery.img - okay... Sending packages etc. etc.) So I wanted to perform the final step -> reboot to recovery and all of a sudden my phone vibrates! yay!
But then it showed some nasty vertical stripes and it didn't boot in recovery at all. I don't see anything exept those lines. But my PC seems the recognize my OPO. When I launch fastboot my pc can find it.
But what do I do now!? How do I boot it normally and get rid of those vertical lines!? PLEASE HELP!!
Thank you for your time and effort in helping me! I'll donate a beer for the guy that helps me fix this issue!
Thread on OnePlus Forums: here

Are you sure it's not hardware damaged? "Bring to life" from what? What happened to it in the first place?

use wugfresh tool kit and go back to stock and start again and see if it fixes the issue may just been a bad flash of the recovery