Develop Bugs

Anyone afraid of NAND flashing is a wuss. Check this out, its so easy..

These Instructions are out of date, and may not work anymore.
-CarComp
EDIT POST ON 5-5-2010
INSTRUCTIONS ARE IN BOLD!!!!!!!
EDITS AND MY OPINIONS ARE IN ITALICS
Want google and not winmo but can't wade through all of the confusion offered up by the supergeeks of android linux? Well just do these steps. It took me an evening to figure out these steps, and could whip it up instantly now.
BTW - it REALLY helps to have a computer with an SDcard slot adapter that handles the micro-sd cards. I don't really recommend trying all this with a USB cable, b/c once you get to linux only, you will kinda be screwed cause it doesn't quite work the same like windows CE. Also that and you can't format through the phone, so just get an adapter ok? Stop right here if you don't have one and just order one or go to walmart and spend 10 bucks and get one. BTW, your micro sd card should have come with one when you bought it, so go look for it.
Ok how to get the super Eclair android into NAND and live a happy life....
1, CHARGE YOUR PHONE UP ALL THE WAY BEFORE ANYTHING. When done charging, unplug whatever is in your USB port for the rest of this procedure. Having phone plugged in while flashing = BAD
2, get hard spl on your phone.
3, Install Hyperdragon IOlite on your phone to get the radio(1.65.24.36) that I recommend, which will improve battery life and possibly other things that I don't know about. Get it here -> http://sakajati.com/blogs/2009/02/hyperdragon-iv-iolite-based-on-htc-iolite/
4, format your 1+ GB sdcard using fat32 only.
5, download polyrhythmics dark / light build for nand and sdcard.
put that SINGLE FILE (androidinstall.tgz) into a folder in the root of the SD-CARD called "andboot" - Get it here -> http://forum.xda-developers.com/showthread.php?t=600154
6, go to http://sourceforge.net/projects/androidhtc/files/ and download KAISIMG-PANEL2-320-TILT.NBH if you have an ATT tilt. If you have something else, download that NBH.
7, Rename that NBH file to "KAISimg.nbh". Put it in the root of your storage card.
8. Now you are ready to install to nand. Get out your stylus, hold down the camera and power button and press the reset button with the stylus. It should go to an updating screen. If you don't get a white screen with a progress bar, but instead it still shows tri color and says "serial" then you did something wrong. Start over from step 1. Once you get to 100%, wait 20 seconds or something (just for shihtz and giggles) and then pull out the battery.
9. Now, put it back in, press power and wait for android to start booting. You will know cause all this random looking text will go by. You have to be quick to do it, but press the middle button on the d-pad when it says 'press the middle button to enter setup' or soemthing like that. (EDIT: I've been told that you have to just hold the d-pad center button down. Either way, just get that button pushed when it says to push it).
You will be presented with some options. Make sure the little asterisk is on the "NAND" option.
10. Go to the install (first option) and tell it to overwrite everything. It may ask you twice.
Now it should go into a fix of text and waiting and hanging, but be patient. You should eventually see a colorful "X" for about 10 minutes. Go to eat, have a beer, leave the house for awhile. Go mow the yard. Just don't use the phone. When you come back, go through the inital setup (touch the android, and skip everything else. Don't set up anything.) Now go mow the yard again. After about 5-10 minutes goes by, come back and pull out the battery. Put it back in and push power.
Crap your pants at the speed NAND offers. Install some live desktops (I like the starfield warp drive one from the google market.)
BTW: If you mess up your phone doing this, blah blah its not my fault blah blah you probably shouldn't be on these forums etc. Just make sure you have HardSPL and you will be fine. I've flashed hundreds of roms hundreds of times. Just that one little step will make your life easier.
EDIT:
RADIO DETAILS:
I've heard a LOT about using the latest radio or whatever version 1.71 or soemthing. I run radio 1.65 just fine. I never upgraded it through out all of the android builds. I operate like this.. If you weren't having cell quality issues, GPS lock issues, or any other radio issues in WINMO, then android will be fine too. I've added a step to the process to install a specific winMO rom that has the radio that I use. If you don't like the fact that I'm telling people to use an older radio, so be it. I'm just spreading the word for what works REALLY well for me.
EDIT: (My thoughts on the panel 1 2 3 and the 320 or 428 or whatever...) Picking the right panel is like playing the 'cups and ball' game. if you know which one the ball is under, you will win. Well for you TILT users, the ball is under #2. I don't know why, but it is. If 2 doesn't work, use 1. Doesn't get simpler than that. As for the resolutions, just use the 320. Ya, some apps fit better on the higher res, but our screens don't support them really well, and its all blurry. Think of it like this..... using 4xx instead of 320 is like asking 3 pixels to display as 1, vs. one pixel displaying as one pixel very clearly. Polyrhymic has done a great job supporting our screen's native 320 size, so just use it.
EDIT: (An issue i've noticed with booting and having your phone plugged in). Android just won't do it on nand. You can charge your phone from a dead point for say 20 mins, unplug it, then turn it on, boot android then plug it back in. You can't plug it in, and turn it on. It gets stuck in some sort of USB status loop.
EDIT: (When your phone just sits there on the A N D R O I D text and won't boot). Seems like this has been happening a lot, for me too. I've found there are two ways to stop this, one is preventative... Don't let your phone go totally dead. The second, when you reboot your phone, press and hold dpad center, then just count to 10 and go to the QUIT option. 9 times out of 10 it will boot right up.
IF YOU HAVE ANY PROBLEMS, JUST REPEAT THE PROCESS.. Don't skip the full charge and installation of Hyperdragon first.

for may people on here, the fear of flashing isn't the problem. it's the missing features such as bluetooth, speakerphone and in some builds even camera.
I would LOVE to go nand. I hate not knowing if the problem is with the build or with the sucky sdcard.
but I need to revert back to winmo for bluetooth headset. once that or speakerphone works I am ON IT.

Nice, couldn't have said it better myself, a few small points, press and HOLD the centre button on Dpad, a quick press will not do it, I'd mention the radio version too, but those are not major issues, and can be sorted easily enough
Good advice about the card reader and adaptor, those two saved my ass a few times in the early days of Nand flashing, I keep a good stock winmo kaisimg.nbh on a spare SD card, you only need a 128Mb one for a stock rom.
Yes there are install instructions on the build posts, but a lot of the info is now spread though some 2000+ posts, so having it all in easy terms helps a load.

I have a question. What is the different those PANEL1, PANEL2 and PANEL3? And the following number 320 - 428 - 480?
And one more silly question, is Tilt the one without 3G camera?
Thx for the instruction, it is easy to understand and so helpful!

added info about panel stuff to the instructions

It is not a fear of flashing in NAND It is just the issue that not all the features works...CAMERA,Bluetooth, voicesearch, so when the features will work than probably everybody will change I know i will ))

my problem is, that i cant get to boot the android for the second time. it just hangs in first screen after booting and thats it...
tried to pull out the battery for 10minutes and still nothing...

Disturbed21 said:
It is not a fear of flashing in NAND It is just the issue that not all the features works...CAMERA,Bluetooth, voicesearch, so when the features will work than probably everybody will change I know i will ))
Click to expand...
Click to collapse
agreed, currently no gps working map that can be rely such as garmin that can work on winmo.. 1 disadvantage of android.. need to be online to get route..

Kurt Cobain said:
I have a question. What is the different those PANEL1, PANEL2 and PANEL3? And the following number 320 - 428 - 480?
And one more silly question, is Tilt the one without 3G camera?
Thx for the instruction, it is easy to understand and so helpful!
Click to expand...
Click to collapse
320-428-480 là chỉ độ phân giải đó bạn.
320 is a resolution of 240X320 and the 480 is a resolution of 320X480
Mình biết được chừng đó thôi

Created another edit to the 1st post.
I'm not saying that android doesn't have its shortcomings, I'm just offering a quick means to get to NAND without trying to comprehend the whole thing in the traditional sense of reading 200 threads.
BTW my radio is 1.65.24.36
Maranevin, try flashing Hyperdragon IOlite first. Maybe a radio switch will prod your phone into the correct direction.

Errr, for newbs who don't know how to properly unlock their device isn't this dangerous? There IS a possibility of bricking your phone if you don't know what you're doing -- right?
Anyway, I would also mention that if you or your phone can't do 3G don't flash to NAND yet. The radio can't be instructed to use GSM only with the current poly build (and any other I have tried so far)

I totally agree with mnjm9b, the problem is not flash the phone, the problem is that there are many things that do not. In particular I am very happy with the performance of 2.1g polymod to date is the best I've worked.
carcomp thanks for the help, very good summary.

aikeru, if someone is flashing a phone, they probably know the risks. Its not my fault if they do something stupid. Is it autozone's fault if I buy specialty tools and ruin my engine changing a timing chain?
Anyways, I don't get the 3g thing. We have hardly any 2g or whatever is below 3g here in Mulberry Indiana and my android works fine.
Like I said, maybe i've found that magic mix of things that works really darn good.
BTW: major argument for using android.....
First of all, i'm not borg. I have yet to really get into bluetooth. I own two earpieces and the only good thing i've found is you can talk on the phone in freezing weather with you hands in your pockets. Bluetooth to mute car radios is cool, but I have a 20 year old car. I don't need bluetooth for file transfer cause i've got wifi, and SD CARD.
Second, as for the speakerphone, it never really was that loud anyways. I came from a hermes, which has a speaker like the voice of god, so i've never been impressed with the kaiser speakerphone.
Third, the camera... I have a nikon D60 with a speedlight for taking stills and lowlights, and a Kodak Z612 in my wife's purse most all the time for the past 3 years for video and spot shooting. All this data easily goes onto the micro sd card and into the phone.....

carcomp said:
10. Go to the install (first option) and tell it to overwrite everything. It may ask you twice.
Now it should go into a fix of text and waiting and hanging, but be patient. You should eventually see a colorful "X" for about 10 minutes. Go to eat, have a beer, leave the house for awhile. Go mow the yard. Just don't use the phone. When you come back, go through the inital setup (touch the android, and skip everything else. Don't set up anything.) Now go mow the yard again. After about 5-10 minutes goes by, come back and pull out the battery. Put it back in and push power.[/B]
Click to expand...
Click to collapse
I've done all step above, just when i did this After about 5-10 minutes goes by, come back and pull out the battery. Put it back in and push power. it started back to Step 9 when i had to 'press the middle button to enter setup'.
So, i skipped that step, and then later everytime i tried to press reset button, the phone is freeze, then i had to started over again...
In some cases, my OK button became to POWER button...
And at first time, WIFI was OK, then it showed Unable to start Wi-Fi
Any suggestion for my troubles?
Thank you!!

Great!!
Hi all, Great!! I am now running Android on my kaiser and I love it!!!
Just a couple of questions for people who can answer them:
- How to change phisycal keyboard layout? I mean, some keys that I have in blue aren't the same I have on my keyboard...
- Is there any means to connect to a pc to transfer contacts and files?
Thank you all!!
Gnatto

Maranevim said:
my problem is, that i cant get to boot the android for the second time. it just hangs in first screen after booting and thats it...
tried to pull out the battery for 10minutes and still nothing...
Click to expand...
Click to collapse
Same problem here. Someone please help. My device is now a worthless brick!!!!

Ok when this happens (its happened to me), first of all don't panick. If you've installed hardspl you are protected, and besides, just cause your phone won't boot android doesn't mean its bricked, it just means its not booting android.
There can be a multitude of things causing this, but the #1 reason I think is "Just because thats how it is"
First of all, don't boot your phone with it plugged in. Ever. Charge it first, then boot it, or charge it enough to make it through boot then plug it in when it reaches android.
Second, sometimes during boot, it just hangs where it says A N D R O I D, or some other text. You can get around this by resetting with stylus, then pressing the center dpad button, then just counting to 10 or 20 or some random number that makes you happy, then select quit. It should boot.

Thanks. Fortunately I unbricked it by putting the KAISDIAG.NBH file onto the SD card, then booted it. This unbricked it. I also put the the KAISIMG.NBH for the Android on here and it booted into the installer. My problem now is that when I click install to NAND, it says it has an error extracting from the SD card for the android installer. It then quits back to the main install screen. I think it is a permissions error since it says on the screen something about being read only. If anyone could help me, I would greatly appreciate it. Thanks.
Oh and btw, I never had usb plugged in since mine is broken.

Ok well you are on the right track. Before you do anything else though, flash a copy of windows Mobile. Either take your pick, or use hyperdragon. Its very complete ... radio / ext rom etc. Next, try reformatting your SD card using windows. Do a complete format, not a quick one. That might help. Now reflash using the link to kaisnbh that i posted.
Remember, installing windows mobile is your NAND reset. Its lot like an sdcard where you can just erase everything. You have to put something else there that is radically different. I may be wrong about this, but it seems to be the case more often than not.
You may be one of the special case people who have a weird phone that takes one of the other KAISimg.nbh files too, so don't discount that. Also since you have hardspl, and you are flashing from the sdcard, you phone is probably NOT going to brick, and even if it does screw up royally, if you can still get to tri color, you can fix it.

Ok. That's great to know. I'll try what you stated. Do I need to partition my SD card? Thanks again. I really appreciate the help.

How I (accidentally) got into download mode on my Bell i9000m

This is not the kind of recipe you'd want to follow to get download mode on a phone with 3 button recovery disabled, but this might clue someone in as to how to make it accessible under simpler circumstances.
This worked for me, dont assume anything:
- Got brand new Bell Samsung Galaxy S from store this morning.
- Tested general funcs, installed nothing.
- Tested every possible way of getting into Recovery or Download mode. None worked.
- Loaded up Kies
- Plugged in phone
- Clicked upgrade firmware
- Started the firwmare update process
- At around 20% progress, unplugged the phone (dont ask)
- Phone was now Purple screen bricked.
- Popped and re-inserted battery.
- Came back with "disconnted" graphic (phone-warning-pc)
- Held HOME, then VOLUME-DOWN, then power (with usb plugged in)
- Held till it came back in download mode.
- Voila!
I then used Odin to flash JH2 onto my phone. Phone works fine now. Impossible to get into recovery or download mode again.
Conclusions:
- If you are completely mad, you could try this technique to get into download mode.
- The blocking of the mechanism is clearly software, not hardware.
- Erasing or damaging the firmware erases the block.
- You may not be able to get into download mode voluntarily, but when you need it most (ie phone bricked) it's there for you.
I hope this somehow ever so slightly advances us toward a hack or fix for this problem. Good luck all.

davidke said:
- At around 20% progress, unplugged the phone (dont ask)
- Phone was now Purple screen bricked.
Click to expand...
Click to collapse
Glad you got it working. I'm able to boot into recovery/download mode when my phone is warmish. Try explaining that!

risky stuff good job

mInes saying device cannot be updated

taurean376 said:
mInes saying device cannot be updated
Click to expand...
Click to collapse
Because you already have the latest....
Smart to test that method when brand new. In an emergency that isn't a bad thing to try. But they need to fix that, we bought the phone in good faith that it was complete and it might kill warranty but we should be able to get into download mode as designed. If we do then there isn't an issue with people wanting to exchange them cause we can fix our mistakes. Isn't that the better less evil way?...

taurean376 said:
mInes saying device cannot be updated
Click to expand...
Click to collapse
God I hate that angry face emoticon. It's like QQ more red face dude!
Anyway, mine says that too. Who cares. Just use odin.

my phone will only go into download mode if the back is warm. i flashed it 4 or 5 times yesterday and each time it would not go into download mode until i left it plugged in long enough for the back to become a little warm, then i could enter download mode at will

I have to sacrifice the lives of 1000 virgins to get mine into recovery/download mode Pain in the ass...
[/sarcasm]
Actually mine works fine. Mind you, I've had a locked out one. It Bricked

it's not true, i got mine into the ultimate bricked mode
and no matter what trick you tried
it will not go into download mode holding the 3 combo keys
on the NEW phone i got after that, it will easily go into download mode at my will, EVEN WHEN THE PHONE IS ON
so, it really just comes down to, if it works, it will work regardless
if it doesn't work... better return it before it is too late, and when you really really need it and it's not there for you

AllGamer said:
it's not true, i got mine into the ultimate bricked mode
and no matter what trick you tried
it will not go into download mode holding the 3 combo keys
on the NEW phone i got after that, it will easily go into download mode at my will, EVEN WHEN THE PHONE IS ON
so, it really just comes down to, if it works, it will work regardless
if it doesn't work... better return it before it is too late, and when you really really need it and it's not there for you
Click to expand...
Click to collapse
I had that picture on my screen yesterday and I almost swallowed my tongue! I was able to get it into download mode and flash with odin. Pretty scary as I mentioned earlier that my phone needs to be warm for it to have any chance of entering download mode.

from what i can gather, people that are able to to get into download mode, it was because it was working fine to begin with, just not hittings the buttons in the correct time or sequence
because if the heat mode worked, or the usb plugged mode worked, then it should have worked as well on the one i sent back for repair, but it didn't work because i tried those methods already

I definately cannot get back into download mode. I tried 100 times. Yet, yesterday, when I had the black screen of death, I could do it at will easily.
So there are circumstances that will let you in and others that wont.
For some it's "warmth", for me it's when it's bricked. Or maybe I killed a virgin that day... not sure.

i like the new term "Black Screen of Death"
lets keep using it more often, so it becomes the norm
it's much easier than say i got bricked at the phone -- ! -- pc screen as most people have been trying to describe

I can't get mine into d/l mode for the life of me.
question: I've had my phone for about a month now. Is it too late? I'm not even sure if I have the receipt (although my buddy is a manager at the bell store)
Should I replace mine? and if so, how do I go about doing it ?
Is it really necessary?
Can't you get into download mode via ADB ?????????????

i'll say wait for froyo to be out
then see if Samsung includes a fix for the 3 button issue.
if they don't or if the froyo upgrade dies half way
then you can comment it all here
http://www.facebook.com/samsungmobilecanada

AllGamer said:
i like the new term "Black Screen of Death
lets keep using it more often, so it becomes the norm
it's much easier than say i got bricked at the phone -- ! -- pc screen as most people have been trying to describe
Click to expand...
Click to collapse
plz help to bass this problem

I dont think you can "brick" an android device. I've had customers come in with all sorts of failed atemps of rooting and hacking and have fixed them all.
Device list:
Samsung Galaxy s
Samsung Galaxy
Samsung Apollo
HTC Wildfire
HTC Desire
Sony X10
Sony X10 Mini Pro
LG Intouch Max
T-Mobile G2
T-Mobile G1
There are a few things like when people dont make back ups of there efs folder etc but that is just user "school boy" errors by people who would play Russian roulette with a fully loaded gun and go first.
Why do people jump into things without thinking and expect others to fix it when they f**k it up. My advice is that if you cant afford to buy a new one when you brake it then leave it alone.

Flashing the software shouldn't "brake" it. It shouldn't break it either. Point is, the phones have a method of recovering from a bad flash, and that isn't working for some of us. We shouldn't have to be ready to buy a whole new phone, just to try different software.
Sent from my GT-I9000M using XDA App

ATT Tilt 2 went to red, green, blue, white screen; how can I flash a cooked Rom to it

Hi,
Right in the middle of use, my ATT Tilt 2 went to a basic, dead screen with red, green, blue, and white bars that says Rhod300 32m SS-BC, etc.
The operating system seems have gone down--it won't respond to anything. Hard reset produces the same results.
Can I flash a cooked or official Rom back onto this? I think activesynch is needed for a normal flash and of course I can't use active synch with the phone in this condition.
I think probably what I need is an original ROM install. Is this possible with a normal Windows 7 PC and a dead phone?
I have so many Windows Mobile programs and peripherals that I am trying to avoid going to Windows Phone at all costs--at least until they have basic stuff like file systems, a way to port over notes, etc. Also need a hard keyboard.
Right now using an older Fuze, which works, but is slower, worse screen, smaller, and lacks some of the features I like.
Thanks for your help.

You sound like you're in the bootloader mode. Tri-color screen.
You can flash from USB or from SD at that screen. I'd recommend trying to flash a stock ROM - as it flashes everything. Assuming that works, hopefully you can flash back whatever ROM you were on.
The phone isn't dead if you're at the tri-color screen. It should say 'serial' at the bottom - when you plug in your USB cable, it should say 'USB' and install some drivers. Then with the RUU software that comes with every ROM, you should be able to flash it.

Phone won't reboot--stuck on tricolored boot screen
Hi,
Thanks so much for replying. I appreciate you pros helping us novices.
Just after I posted the first note, I pulled the battery and hit the power button, it rebooted, and everything was still there in the OS--working fine. But whenever the device had to be rebooted, I would have the same problem of it getting stuck in the boot screen. After that, for the last several days once in awhile, randomly, it would finally reboot from the boot screen after I pulled the battery and hit the power button. The rest of the time (about 5/1) it would just sit there in the boot screen no matter what I did. The "Serial"/"USB" thing would change when I plugged it in, but that's all.
Thought it was the OS, so at a lucky moment where the "pull battery, hit power button" strategy actually worked, I installed the latest official HTC/ATT Rom--it's the next to last one issued that ends in .4.
It was gorgeous and I got all excited--started installing stuff thinking my problem was solved.
Had to reboot to install some programs--now it is stuck again on the boot screen. Tried 30x again--no luck with the "pull battery/hit power button"
strategy. Sometime it would flash a white screen really quickly saying something like "Can't read image!" before going into permanent boot screen. The boot screen will switch from "Serial" to "USB" if you connect it to the computer. So, the problem doesn't seem to be in the OS--rather, in the ability of the device to "read" the OS from the boot screen.
I would be grateful if you or anyone else may know what's going on here, and any ideas on how to fix it. Is there any manual way to get it to read the OS from the boot screen when that's not happening?
I have two guesses (both of which may be wrong):
1. It may be something in the hardware is just worn out and is less and less able to read the Rom--any ROM. I got the phone new off Amazon for a profit of $50 ($.01 cost plus a refund for an older phone) in the summer of 2010 when it was already outdated. and WP was replacing WM. I've certainly gotten my money's worth after 18 months!
Of course we now know that a brand new ROM has the same problem as the older one--which suggests to me it's in the hardware. I'm sure the new OS and the stuff I installed is still there on the phone, but something it appears is not reading something in order to allow the boot up.
2. I have a squirrely free program called Rax Reset (from Windows Mobile Marketplace) that does a software-based hard or soft reboot from inside the OS. The very last time the device went down and didn't come back up, I had used that program to soft reset it. Might have been a big mistake. Could this program be causing the problem? If so, just one reboot would allow me to get rid of it or even hard reset to remove everything but the new OS--but can't get it to boot.
If it turns out the phone is just worn out, I've certainly gotten my money's worth.
I still love WM even with all its problems--and especially the newer Sense version. If this one is shot, I'm thinking about just buying a new Touch Pro2 on Ebay to avoid all of the sacrifices and backwards steps involved with Windows Phone.
Thanks for any help anyone can provide.
Phil Butin

Why are you crossposting? I read this EXACT same post in a thread just below this, in the same section. That's pretty low.. Crossposting across forums isn't welcome, crossposting within forums IN THE SAME SECTION is definitely not welcome.
Don't do it again.

Sorry, just trying to get help
Sorry, just trying to get help, not that familiar with the rules.
I searched on "bootloader" and found a thread (wrote a comment there too), but it's old....
Here is the thread. It doesn't really provide any solution.
HomeArrow
Legacy & Low Activity DevicesArrow
HTC Rhodium: Touch Pro2, Tilt 2Arrow
Touch Pro2, Tilt 2 GeneralArrow
issues with bootloader.

Either way, whether you know the rules or not - why would you think copying and pasting the exact same words in the exact same forum help you any more...
Anyhoo, have you tried the usual? Flash stock? Sometimes I've heard you have to flash several times, I never really understood that logic tho.

I'll try to reinstall the HTC/ATT Sense OS again. I guess you're saying active synch doesn't need to be working in order to do that. I'm at work now--have to wait until i get home. Nothing to lose at this point.
But I'm seriously wondering whether the problem is the OS install or whether there is something in the device that is supposed to read the ROM and start the bootup that is just wearing out.
Thanks.

"No Image File"
The quick little flash of white screen has "No image file" in blue letters--goes by so fast you can hardly see it.

[email protected] said:
The quick little flash of white screen has "No image file" in blue letters--goes by so fast you can hardly see it.
Click to expand...
Click to collapse
That error message is 'normal'. Basically the phone checks the SD card for a file labeled "RHODIMG.nbh". If said file exists, it will flash from it. If no file exists, or no SD present - it continues loading bootloader and should say "Serial" at the bottom. This indicates that it's ready to be flashed. If you plug in your USB cable, it will install some drivers and then it should change to "USB" at the bottom instead of "Serial".
Now you should be ready to flash from a normal RUU. I would recommend flashing STOCK, because this flashes everything.
It might also be good to note a lot of people have experienced something similar - the phone getting "stuck" in bootloader mode, and only occasionally making it to WinMo. I'd guess it's failing hardware in some way shape or form, as none of my RHOD's or RAPH's have ever done this.

Good News--at least for now
Good news--I hooked it up to the computer with the USB cable for awhile and the Windows 7 computer did set up some drivers. For some reason after I disconnected it I reset it, and the reboot worked. Then I immediately uninstalled the squirrely reset program and removed it.
Everything I installed yesterday is working fine--I have soft reset it about 5 times now and each time it has rebooted. So I think maybe I'm back in business. Too soon to tell--but we will pray and keep our fingers crossed.
Thanks so much for your time and help. I don't know how to use the thanks meter but I would have if I could have.

[email protected] said:
Thanks so much for your time and help. I don't know how to use the thanks meter but I would have if I could have.
Click to expand...
Click to collapse
You're welcome. Basically if I or someone else posts something helpful, click the "Thanks" button under that post.

15 hours later, Tilt 2 is still working fine on the newly installed Sense OS. I have rebooted freely (using the stylus button on the side) since removing the program "Rax Reset," and everything seems to be going well. I'm keeping my fingers crossed, and will end my contributions to this thread with a warning about using "Rax Reset."
Thanks to all.

[Q] Screen's gone fuzzy and weird - Solved

My Captivate Glide's screen does this whenever I turn it on:
I didn't drop it or get it wet, it just started doing this randomly.
I live in the UK and ordered the phone unlocked over eBay so I can't take it into an AT&T store, sadly.
Do you guys know if there's anything I could do myself or anything someone more experienced in repairing mobile phones could do to fix the screen?
This is bearing in mind that not many people over here have seen one of these phones though.
Any help would be massively appreciated. Thanks guys.

you was using still GB right? just flash ics via odin, with one click or with a tar file
This is UCLH2 without one click
http://androidromupdate.com/2012/09/...ota-stock-rom/
And here is the latest version with bug fixes (like keyboard light)
http://androidromupdate.com/2012/11/...ptivate-glide/
and there is for one click
http://www.androidauthority.com/captivate-glide-sgh-i927-att-android-4-0-4-ics-uclg9-leak-110365/
i think that only one click wipe your internal storage. but is the bes (in my opinion). try it, dont have anything to lose

No, I already updated it to ICS. Should I reinstall it? Will that fix the screen? How will I manage to do it with the screen all messed up?

if you can put in download mode, then you can. Its weird because i only see that problem with GB. Put in download mode and then reinstall

I just tried putting it into download mode but I get the exact same thing.

Thats weird, the problem is weird because it never happen to me in download mode, maybe you can try it without battery, or let the phone without battery a couple of hours, etc.
Dont Know what you cand o, because if you cant enter in download mode, you will be no able to flash ICS

Hrm... that purple splotch in the bottom left of the screen doesn't look so good... Almost appears as if it had been dropped on that corner at some point in the phone's history. I am tempted to say that is a hardware issue, though. Reminds me of when the flex cable for my laptop's display started shorting out many years ago. Might be repairable, but, might be a costly repair depending on what all needs to be replaced. I can't imagine replacing the software on it will do much, though, sorry to say. You could give it a shot, you can verify if your phone made it into download mode without the display by loading up odin and seeing if it detects under that, and then running the one click install (or any other since you'd have odin running anyway) but I wouldn't expect much.

If you're not getting the Samsung/Rogers logo screen, you're done. Either the screen is physically damaged, or the bootloader is corrupt. There's no saving that one, sadly.

yes, try what Artemis-kun say. put in download mode and connect, and see if odin detected. Or maybe just turn on the phone and wait a little, then try to call to your phone, if the phone ring or appears to be on, then is a hardware problem.
But try what Artemis-kun, maybe you have luck
PD: now i see better the image and it seems little different from what it happens to me. if you turn on, inmediatly happen that? or screen banish slowly?

AW: [Q] Screen's gone fuzzy and weird - need help please
There should be a cable, connecting the hardware to the display. Maybe it loosened, you should check out the video of a guy tearing his glide apart, hopefully youll find something to repair there.
Sent from my SAMSUNG-SGH-I927 using xda app-developers app

Hey guys, you'll be glad to hear I finally fixed my Glide by installing a new screen assembly from Repairs Universe.

[Q] Samsung Ace II will not turn on

Hello, new here and I know nothing about rooting nor have I rooted my phone but after looking all over the net I have come here in hopes of finding some tech wizards that can help me.
The Problem:
Turned phone off and a few hours later I tried turning it back on but it only shows the screen with model number and Samsung under it. It shows for a few seconds then the screen goes black and keeps looping like this. I have not rooted or anything. Not dropped in water ( water square is pink though). Phone shows no water damage or corrosion after opening.
What have I done?
I tried booting in recovery and download mode but i have never done it before and I was not successful at getting any other screen besides the model number Samsung screen.
I have tried a different battery after spending some time at the mall (no on carries it any more as it is no longer made) different battery did nothing. Repair guys suggested it may be the button sticking and said hey could clean it for $25. Instead I went home searched the web and disassembled my phone. I cleaned the button areas on the inside of the case and the contact on the inside attached to the circuit board. I have reassembled and it still does the same thing.
After more research I found a video saying to actually remove the internal button from the circuit board to stop the loop (which will leave me with no power button) I have not tried this as I am not that bold (yet).
I am wondering if it is a software problem that can be fixed by using Odin and installing the stock firmware but I just have not found a proper guide that makes enough sense for me to actually try. I don't want to waste my time with something I have never done and make things worse.
I have downloaded Odin and firmware from sammobile but that is about as far as I can go without some hand holding....
Thanks for reading my story any help would be much appreciated.

Fishheadman said:
Hello, new here and I know nothing about rooting nor have I rooted my phone but after looking all over the net I have come here in hopes of finding some tech wizards that can help me.
The Problem:
Turned phone off and a few hours later I tried turning it back on but it only shows the screen with model number and Samsung under it. It shows for a few seconds then the screen goes black and keeps looping like this. I have not rooted or anything. Not dropped in water ( water square is pink though). Phone shows no water damage or corrosion after opening.
What have I done?
I tried booting in recovery and download mode but i have never done it before and I was not successful at getting any other screen besides the model number Samsung screen.
I have tried a different battery after spending some time at the mall (no on carries it any more as it is no longer made) different battery did nothing. Repair guys suggested it may be the button sticking and said hey could clean it for $25. Instead I went home searched the web and disassembled my phone. I cleaned the button areas on the inside of the case and the contact on the inside attached to the circuit board. I have reassembled and it still does the same thing.
After more research I found a video saying to actually remove the internal button from the circuit board to stop the loop (which will leave me with no power button) I have not tried this as I am not that bold (yet).
I am wondering if it is a software problem that can be fixed by using Odin and installing the stock firmware but I just have not found a proper guide that makes enough sense for me to actually try. I don't want to waste my time with something I have never done and make things worse.
I have downloaded Odin and firmware from sammobile but that is about as far as I can go without some hand holding....
Thanks for reading my story any help would be much appreciated.
Click to expand...
Click to collapse
Try this - Press and hold Volume up + Home + Power buttons together a few seconds, you should get recovery mode. And then find factory reset.

garak elim said:
Try this - Press and hold Volume up + Home + Power buttons together a few seconds, you should get recovery mode. And then find factory reset.
Click to expand...
Click to collapse
Thanks for the reply. I have tried this many times and tried again after reading your reply. This should work fairly fast from what I understand right?
My phone is a virgin mobile phone (Canada) is it possible they have locked out recovery / download modes?
When I try to start in recovery nothing happens at all. Screen does not light, phone does not vibrate. Again I have never tried this until now so I don't know if the phone ever booted into these special modes when it was working.

Fishheadman said:
Thanks for the reply. I have tried this many times and tried again after reading your reply. This should work fairly fast from what I understand right?
My phone is a virgin mobile phone (Canada) is it possible they have locked out recovery / download modes?
When I try to start in recovery nothing happens at all. Screen does not light, phone does not vibrate. Again I have never tried this until now so I don't know if the phone ever booted into these special modes when it was working.
Click to expand...
Click to collapse
It's weird. I found something on page hard-reset.com. I cannot post link here now. I put "samsung ace2 recovery" into google and it was on first page. It's hard reset key combination. Try it.

When you plug the phone into the charger, do you get the battery charging status screen?

garak elim said:
It's weird. I found something on page hard-reset.com. I cannot post link here now. I put "samsung ace2 recovery" into google and it was on first page. It's hard reset key combination. Try it.
Click to expand...
Click to collapse
Forget my previous post. I was wrong. I try find another solutions.
Is your battery fully charged?