Database Users

I think my Dream is toasted... OR My experience with the "blue light"

Recently my phone started acting a little unusual. For instance, composed email weren't being sent out while syncing and a wipe and reflash seemed to fix it at first. This problem continued to get worse and at the same time, I started getting SD card ejected notifications seemingly without reason. Now it's to the point that my phone is completely unusable/useless. IF it boots all the way up, it will lock and then just go black. I have to remove the battery for some time to get it to turn on again. This includes loading the SPL and the Recovery interface. The ONLY way my fone will act semi-normal is if I remove the SIM card and boot it. Then eventually it will again just shut-off. I have reverted back to an older SPL with no luck (was using Haykuro's latest one until now). I have loaded multiple radio's with no luck (after reverting the SPL of course). I have tried multiple ROM builds, JF's, Cyanogens and Haykuro with no luck. This really sux. 4 month old fone and seems the radio might be fried. VERY disappointed in the quality. I hope I can get some help and warranty the phone. I am thankful I unlocked my old Blackjack and am able to use it for now. Just though I would share my tale of woe. I am not sure exactly what caused this. Maybe too much flashing? Not sure, but be aware; I feel like maybe I played too much with my phone. That last part REALLY sux cause I love my fone. I LOVE that I can play with it and install all of the great ROMs and themes. Anyway, best of luck to all you Dream owners. I hope I dont have to buy another one (cant afford it )
My fone is not bricked it just seems unstable in every way. Sad day 4 me
[UPDATE]
Before I made this post, I turned on the blue LED (holding trackball and power) and just let my phone sit there. Didn't really have a good reason to do so other than 'why not?'. Anyway, shortly after making this post, I couldn't just leave it alone so I picked up my phone again (I really do love it that much lol). While holding it and just thinking about my less and desirable situation, I noticed the back of the fone was warm like it is when you've been using it for some time. I couldn't help but think that the blue light was indicating that "something" was going on in the background so I just began pushing the buttons on the front and no specific way just randomly and all the sudden my fone rebooted. Sorry I can't say how long it was in "blue light" mode.
Now everything I had experienced and read concerning the "blue light" indicated the only way to get it out of this mode is to 1) remove the battery or 2) let the battery just die on its own. So you can imagine my surprise when the fone just rebooted. It booted up (no SIM inserted) and seem to be fine, but as I mentioned before, this had happened only to lock up and reboot itself. I just began using it as much as I could to see if it would fail again and it seemed to keep going fine so I thought "why not insert the sim again?" So...
With SIM inserted, the fone booted up fine. Again I began to put it through its paces and everything is good so far. Makes call (too late to have someone test call me), browses, downloads market, basically everything with no lockups and no reboots leaving all keys unresponsive. Damn I was happy! But not too much just yet. I'll let it keep going for sometime to make sure it's good, but I can't help but to think that putting my fone into "blue light" mode somehow "fixed" my fone fo lack of a better word. I am perplexed but pleased. Will update later after some decent testing time has gone by. I remain hopeful and regret my earlier comments regarding the fone's quality. I hope I remain regretful of this lol.

Interesting. Can you tell what EXACTLY was on the SDCARD when this happened?

lbcoder:
When this problem first happened on my phone I had folders containing my AppManager backups, ringtones, NES ROMS, camera pix and video files. It's the SD card I always have in there. I don't use apps2sd. I thought maybe there some problem with this card so I tried 2 other SDs I have with the same results; instability. I even tried a clean build with no SD card (as well as with and without SIM); all with the same results. I tried every possibly combination as a form of troubleshooting.
When I put it into blue light mode, the SD card that was installed contained DCIM (pix), appmanager, mp3s, video files, 2 different radios in .zip form (radio 1.22 and the sappire radio; neither with the name update.zip), .footprints folder, ime folder and that's about it. Did u have something in mind?
BTW, I wish I could edit the name of my thread to show there's an update...

The Blue LED has some other purpose and is simply not a "lock". That just seems silly and useless, especially since you'll find if you put it into this 'mode' it will drain your battery fairly quickly for a 'lock' mode (like 12 hours).
There's more than a 'lock' going on here...

I agree. It's doing something in the background other than just being a type of "lock". I'm don't want to claim that it fixed my phone because I have no idea what it's doing when that little blue lights is on. I am saying that it seems a little more than coincidental that my fubared fone (my feeling at the time) began to "magically" work after putting it into this mode and its subsequent reboot. I am really glad I did.
No amount of: fastboot erase "partition name", data wipes, radio/spl/rom flashing helped my fone. I was going to try and get warranty today, but now I don't need to. Back running ION and happy as h3ll! Maybe this will help someone else with a fone that refuses to function correct. Maybe it won't, but I definitely wanted to share my experience with it.

BTW, I was running Cyanogens 3.4 JF mod at the time this began. I understand some other people have had some similar issues as seen here:
http://forum.xda-developers.com/showthread.php?t=525306
These problems are very similar to what I was having, but mine seem irrecoverable even after flashing EVERYTHING. Just food for thought...

I wonder if it found one of those radios and did something with it?

For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.

hamshu said:
For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.
Click to expand...
Click to collapse
This is why I stay on Google Ion. It's clean, stable and fast. All these "optimized" builds seem plauged by bugs and quirks.

lbcoder said:
I wonder if it found one of those radios and did something with it?
Click to expand...
Click to collapse
Interesting thought. But it would have to have parsed the file and made a determination on its own as to whether or not it was a valid radio. Neither were named update.zip at the time. Also, I had already downgraded the radio to one of the versions that existed in file name radio_1.22.zip that was on the SD. That allowed me to downgrade the SPL without bricking because at the time I was running Haykuro's newest SPL (which I have since reflashed to my now functioning fone).
For that thread, Cyanogen has stated that the main issue is in the kernel. The memory killer kicks in and kills essential processes thus result in a crash. He stated that he's looking into it and the fix will likely be in 3.4.1 or one of the iterations after that. I'm not sure if your suffering from the same thing though. None of them seem to have the same symptoms as you do.
Click to expand...
Click to collapse
Actually I described pretty much the problem quoted below that is in the thread that I referenced earlier:
tearsphere said:
Can someone please help me..
I installed Cyanogen 3.4 when it got released a few days ago and it was running smoothly.. I think he is a genious. Just today my phone shut off on its own and I had to take the battery out and put it back in to get it to come back on.
Click to expand...
Click to collapse
So I guess it could be open to interpretation. I think Cyanogen does amazing work. I have great respect for him and all his efforts that have given us more functionality with our Dream fones. As I said, it's food for thought. I'm not drawing any conclusions as they would be based on conjecture.
I am intrigued by the blue light mode. I really wish we knew exactly what purpose it serves.

Stock+root&clockwork and OTA update. My experience.

First let me say thank you to everyone who makes this place such an awesome resource. I'm sure I'm not the only lurker who feels a ton of gratitude and appreciation for all the time and effort shared here!
Because of that gratitude I just wanted to register and post this in the hope that it'd help someone else in the same position.
I was hesitant to root my vibrant because I'm really not in a position to replace it if I managed to destroy it in the process, but finally 2 days ago I gave in and did the one click root plus clockwork recovery process so that I could use barnacle wifi tether. Of course 2 days later this official over the air update gets pushed through, immediately filling me with dread.
I assumed it was froyo finally but did some reading first, mostly here; and while it was not the much anticipated 2.2 it still sounded like something I'd want to have. Plus there seems to be no simple way to get rid of the update nag in the notification bar unless you update.
So I went ahead and risked it. And I'm happy to say that despite a horrifyingly long pause at the galaxy s screen, the update went thru perfectly using just the official push delivery method, not Odin or anything but the stock delivery method.
Now I have media hub, the gps fix, my signal bars seem to finally be working right and maybe I'm fantasizing but the whole phone feels faster; and I didn't even lose root.
Anyway, I hope this helps someone who like me only rooted and clockworked for wifi tether.

I wasn't so luckly. I undid my lag fix and un rooted and still soft bricked mine and had to use odin to get it back

how long
HumanTarget said:
First let me say thank you to everyone who makes this place such an awesome resource. I'm sure I'm not the only lurker who feels a ton of gratitude and appreciation for all the time and effort shared here!
Because of that gratitude I just wanted to register and post this in the hope that it'd help someone else in the same position.
I was hesitant to root my vibrant because I'm really not in a position to replace it if I managed to destroy it in the process, but finally 2 days ago I gave in and did the one click root plus clockwork recovery process so that I could use barnacle wifi tether. Of course 2 days later this official over the air update gets pushed through, immediately filling me with dread.
I assumed it was froyo finally but did some reading first, mostly here; and while it was not the much anticipated 2.2 it still sounded like something I'd want to have. Plus there seems to be no simple way to get rid of the update nag in the notification bar unless you update.
So I went ahead and risked it. And I'm happy to say that despite a horrifyingly long pause at the galaxy s screen, the update went thru perfectly using just the official push delivery method, not Odin or anything but the stock delivery method.
Now I have media hub, the gps fix, my signal bars seem to finally be working right and maybe I'm fantasizing but the whole phone feels faster; and I didn't even lose root.
Anyway, I hope this helps someone who like me only rooted and clockworked for wifi tether.
Click to expand...
Click to collapse
thats great to hear since I'm rooted and i just installed ROM Manager/Clockwork in order to make a nandroid backup. Now Im wondering whether i should wait for the OTA to hit my phone or if I should use Kies Mini to do it manually over USB. In either case, could you please answer one question...how long did it stay at the galaxy s screen?
Becuase some people are saying it stayed on it for an hour and assuming they're soft bricked but if it really takes 1 hour and 2 minutes than that extra bit of patience is needed...

jblade1000 said:
thats great to hear since I'm rooted and i just installed ROM Manager/Clockwork in order to make a nandroid backup. Now Im wondering whether i should wait for the OTA to hit my phone or if I should use Kies Mini to do it manually over USB. In either case, could you please answer one question...how long did it stay at the galaxy s screen?
Becuase some people are saying it stayed on it for an hour and assuming they're soft bricked but if it really takes 1 hour and 2 minutes than that extra bit of patience is needed...
Click to expand...
Click to collapse
took about 3-6 minutes for me.
I got very worried... but was patient.
Stock ROM
Rooted
All bloatware removed.

wasted mine with no lag fix rooted on stock kernel, stock build..had to odin back and update via odin...****ty

well damn, im kinda at a loss then about whether to go through with this. I want the update but I dont have the time to be messing with flashing and odin right now...

Weirdddddddd

I to bricked my phone with the ota. I was rooted, stock rom, lagfix with clockwork. I undid the lagfix but still bricked. My boy's running the same without clockwork (never had time to put it on). Unrooted, delaged and removed the update.zip that was on the phone from root and cleared the cache. Ota worked without a problem. Some believe it is the result of an update.zip left on the sd which causes the problem.

My journey to the unconscious brick of the Flipout.

Here's how I bricked my phone, for the ones who're interested:
I think it's a pretty funny story, so keep reading if you're searching for some entertaining story.
So I Bought a flipout because I wanted a small phone. I was pretty satisfied by the phone and it's performance, althought it's kinda an effeminate phone. Anyways, before I knew it (When I booted up the phone for the first time) I was disgusted by Orange's laggy intro: it was supposed to be an explosion followed by an implosion which created the Orange logo (sort of XBOX style). The reality was less: a very laggy 2 or 3 fps intro. Bravo Orange if you were actually aiming for this rate.
When I boot up the phone it shows the menu just like any other phone, but it came with another disgusting fact: MotoBlur. Lag, lag and lag. There it was, in all it's glory:
- It's laggy (not as much as Orange's intro...)
- Uses default services (calendar, gallery) with some unfinished 3D features (that caused needless lag)
- "Happenings" which connects your twitter, facebook and other things.
Although I have to say, I did like the lil tab that shows above and tells you on which screen you were. It looks kinda like the following (excuse me my drawing skills):
.: : . |^| . : :.
resp. -3 -2 -1 0 +1 +2 +3
Anyways, I had to get rid of this "MotoBlur" and the first thing I had to do was to root my device. I remember the days with the G1 which were a hassle to just root your phone, so I was hesitating if I really wanted to go through all this again...
But after a lil search, I found that nowadays we have superoneclick, androot, z4root, etc... etc... So I tried one of these "new" apk's which gave me a small error, so then I tried z4root which was quite easy, fast and simple. I was in. Things were going my way, hell, I even found a brand-new-looking 4GB microSD on my work. Just out of nowhere there it was, very small, laying down on the ground waiting for me to get picked up.
What goes up, must go down...
So there I was with my first steps trying to remove MotoBlur, and although I knew there were tut's about how to remove Orange and Blur, I just couldnt wait. I made backups of my system apk's with Titanium which was quite easy, and it was that precise moment when I was like "GET!", i'm sick of this MotoBlur, let's remove these "things". They are right in front of me, just get rid of them... And while continuously hitting the "remove" button I was daydreaming of a simple usefull handy phone. Bam, bam, bam, I deleted one app after the other, even Google Talk didn't had a chance. Everything was going smooth, bye Blur.Calendar.apk, bye odex, bye Blur.gallery.apk, bye Blur.happenings.apk,... ... ... about 20 apk's later, I was quite satisfied.
But you know how it goes when you just delete stuff without greater knowledge. You BRICK your phone. But people, this was just the start. I had some force close after this one man operation, but my phone was smoother. I have to admit, things were comming unexpected. First I couldnt find my gallery (removed). Then I found out I couldnt download anymore from the Android Market because I deleted Blur.calendar.apk which is connected with Calendar.apk which syncs my G-Mail account which is needed before you can download anything from the Market. Hah! Owned.
Backups.
So there I was having these problems, but the phone still works great. I have to admit I silently thought: luckely I made a backup, and was kinda proud I wasn't one of those noobs who just goes forward without a save game, right? Right? Guys...? Anyone...? . ... ...Wrong! The reality was I couldn't even "restore" with Titanium. The backups weren't real backups, but just data-backups which were stored on my sdcard in .tar format. Aaarrgh!
No problem, no problem. There has to be a way to fix this, someone did this stupidity before me. Obviously. Ofcourse. No?
When I was searching about why I couldn't fix my Titanium backups, someone answered to someone else that's because he couldn't sideload the apps. He needs to root his phone in a way so sideloading is enabled. Great! Sideloading it will be then.
Sideloading is def a great way to install .apk's without the market, because I tried a factory reset (hoping that would solve everything) and I couldn't download anymore from the market. I had to sideload ASTRO which was successful with the right ADB drivers - even though I didn't knew what ADB meant I did register on MotoDev's website (so I can download the little bastard).
Easy peasy. Now I'm back on track with ASTRO and an easy install of Flan Gallery (fixed camera) replaced my gallery. We're off to set!
Despite this minor victory I was aware I'm still not were I wanted to be. Factory reset doesn't get me were I want to be and I'm still having issues. But no problem no problem. This time I'll turn my questions to the community, not google. That's eventually why there is a community? That's why we are open source? Yes. Score. Win.
So maybe some knowledgeable people will reply because they can help the ones who are trying to learn. I think I'll start with how to fix the calendar-issue and then I'll try to make a ROM-backup, so I can install a new ROM or whatever. That's probably a better idea then before. Cool, I even got a quick reply by someone who told me to go to this-and-this site, which is better for noobs. Allrighty then...
Trying my own way.
Since things weren't going were I wanted to, I thought now it's time to give it a real last try by searching about this mystery "ADB" and eventually to push some apps into system/app/ so I could fix all this misery. I found what I was searching for, however the tut about how to push apps sounded like someone was holding a gun against the writer's head. It really sounded like he wrote it against his will.
Desperate attempts.
I started today (15 april) around 5pm local time with this whole pushing-thing because I thought I had the knowledge that I needed and even surprised myself by actually successfuly pushing some apk's using a quick and nice XDA how-to, but then things went from worse to worser. I pushed Blur.calendar.apk, Blur.service.apk, Blur.email.apk, Blur, Blur, Blur... Ironically thát what I wanted to remove at the start came voluntary back in my system/app/ of my phone.
That's quite funny especially when I rebooted my phone and I kept getting force close com.motorola.blur.service.main and I couldn't get around this except by using voice-commands (double tap home button). "Find ASTRO" I said. Finding ASTRO... Opening ASTRO... Ingenious! It was quite amazing that this feature actually works without any bugs or misunderstandings. So I started root manager, rebooted the system with r/w settings so I can try a final attempt by trying to remove blur-service.apk from the system/app/ which actually didn't had any impact. Nothing really happened.
The end.
And there I was having these problems, and the phone doesn't work. A friend of me adviced me on Steam-chat to hard-reset the phone. I could care less, but we had a little discussion about what has more effect hard-reset or factory-reset? Btw... Holding down the power button and the camera button...?! The phone doesn't even has a camera button! Hilarious.
I eventually did the hard-reset with another tut and now the phone is... ehm... kinda... pretty... bricked. It just boots up and then gives 1 continously looping force close of the blur service (which I allready had), and another force close when I finish setting up the blur account wizard. At the end of the wizard it just force close and shows the wizard again,... and again... and again...
Mathematical summon:
+1 noob
+1 bricked phone
- $$$
- (a lot of) time
+ frustrations/stress
+1 story
Equals a possitive outcome?

i've not rooted my Flipout as it seems there's not much you can do with a rooted one anyway
but I've done bad flashes before...many times
and i've always been able to rescue those phones by flashing the original rom. just wondering if this might be an option for you..

See if you can flash that device using RSDLite, I can see some tuts in this board that features this, likely that debranding guide. Hold up+power when it's off and boot into flash mode, not camera+power

A brick = a dead phone, no boot, no flicker, nothing. If it acts like a brick it's a brick, otherwise it's just a messed up phone. I'm sure you'll be able to recover yours...
Sent from my HTC HD2 using XDA Premium App

Moto phone + rsdlite + flipout sbf= fixed phone. Just find those two things and you can restore your phone back to fresh out of the box state again. Promise.
Sent from my SGH-I897 using Tapatalk

Yeap i just did it first try hold "up" button on the keyboard + power for 4 sec then plug usb. in flex options i checked everything and it all went god then

Ginger Break broke 3G

Ok I fear I have a very isolated problem since I have not found any other posts over multiple sites on the same issue.
I bought my VM optimus V 3 days ago and wanted to root it. I had used gingerbreak to root my optimus M just 1-2 weeks ago without problem. Well unfortunately I did not see that it basically doesnt work anymore (I did PLENTY of research but you guys have the only post), and installed and attempted a root.
It failed after a few restarts and tries, so I moved on, but soon I noticed 3G and GPS (I guess data as a whole) was not working.
Since then (2 days) I have rooted using <yuck> windows-superoneclick and flashed multiple ROMS including stock with success. BUT no matter what I do the data is still not working.
VM couldnt figure anything out, and has escalated the issue internally, and I could go down to BEST BUY and exchange it as broken, but I'd rather figure it out, and I hope its something stupid easy.
Can any serious developers, or even funny ones help me out here? Thanks in advance!

Update
Wow, no one up for a challenge?
Latest: Its been escalated again to like lvl3 VM support now, since 3G shows up and up and down arrows flash but it doesnt actually work. Also the virgin activate app completes but identified my phone as a Nexus S!!???
Any takers?

Same thing happened to me I freaked out.
I saw this thread and used Gingerbreak to unroot my phone in hopes the problem would go away. It didn't seem to. Then I tried to turn on some sync things like gmail and google reader. Googled for a bit and the 3g came back on I received the email notice for signing up to xda and just thought I would let you know it wasn't permanent. If you backed up your original rom with the gingerbreak try flashing to it and unrooting. Then wait a while for the 3g to come back.

(Request) PDS Back Up for AT&T Unlocked GingerBread Atrix

Does anybody have a working PDS for a AT&T unlocked Atrix for Gingerbread they can upload please ?
Having irritating touch screen issues.

I think pds is unique for each device so other pds won't work on your phone. Correct me if I'm wrong.
Sent from my MB860 using XDA Premium App

Andy_Thatcher said:
Does anybody have a working PDS for a AT&T unlocked Atrix for Gingerbread they can upload please ?
Having irritating touch screen issues.
Click to expand...
Click to collapse
pds are for their individual phone but there is a generic one on the forums for touchscreen fix. you are going to have to search for it.
did you do nandroid restore? which recovery? tenfer?

Really unsure to be honest.
Kinda hoping that isn't the case but if it is it is.
Have seem a couple of PDS's here but apart from one once they haven't made a difference so am trying for a definite match to find out.
My screen behaves normally until the phone starts to get warm then...well if I didn't know better I would think it was hacked with random key presses left and right.
Take out the battery for 10 minutes and get another 15 minutes or so and off it goes again.
Edit -
Managed to get some form of stability with the Aura ROM with Faux's Kernel and SetCpu under clocked....have managed to lose Wi-Fi in the mix somehow.
Could be time just to bite the bullet and buy a new one as I am due an upgrade. NOOOO enough of that defeatist talk !

Regrettably I do not have a back up of the original PDS, managed to miss that as being a requirement pre-boot unlock.
I have 2 PDS's from here I have found on here but neither seem to be a permanent fix. One is khoulk's (sp?) but I think that is from a non standard phone and another one that worked....briefly. I also have 2 from my phone but alas they were after the issues started so have doubts about them.
Just changed the CWM from tenfer's to the new one.
At present just playing around trying to get wifi back on the phone, then I will go back to the pds hunt.
Oh just for kicks it seems that I can't download from the market either at the moment. It starts but then after a few seconds stop.

I managed to get the phone to behave normally by going back to 1.2.6.
Then used OTA's to get to 1.8.3.
All stable at that point then SBF'd 4.5.1 with pudding and pre root and then....
Everything went to pot again.
Currently heading back to Froyo and will OTA again up to 1.8.3 and stay there for a while and consider my next move. Trouble is that I really need a working stable phone. so will do the smart thing next time and get a nandroid back up of the 1.8.3 and a copy of the PDS.

Try using the method described in this thread:
http://forum.xda-developers.com/showthread.php?t=1131649
It will fix both touchscreen issues, as well as the problem described in the thread. It worked for me...

Thankyou.
I had already tried that and first time it worked a treat alas not attempt 2,3,4,5,6....