Somewhere in the odd universe of Turl's latest cm9 rom my bootloader got f'ed up. It gives me the full menu and serial number and stuff, magicvalue mismatches and other stuffs. Loads into different roms just fine, have tried a couple roms including jokers cm9, the stock rom and alien, what I used before cm9. Anyway, phone turns off very often. Sometimes it'll stay on for only a few minutes before turning off. Had to do a PDS fix because somehow in that flash of turls rom my touch screen also blotched and it got stretched out and unusable. Had pds backed up but it got blotched somewhere too, its been a while.
Anyway... I have a feeling I'll have to RSD a full unlocked sbf. The ones in the pudding thread are multiupload/megaupload stuff... which is blotched... Can I get an opinion on what to do? I can't go around with an unreliable phone lol.
bump? >>
phone still restarting. Loaded stock sbf and it kept restarting randomly.
Related
ANY HELP WILL DO.
I work for T-Mobile and have plent of time to learn how to do things the right way. I became familiar with ADB, Flashing roms with CWM, and bricks and freezes do not scare me.
One day i was reverting to stock. Oden completed with a bright green pass! My phone rebooted, finalized the recovery, rebooted again, the screen went place and never came back on. I attempted to hold the power, change the battery-NOTHING-The phone remains powerless never to reboot again. I had not not done anything crazy before-JUST TESTING OUT ROMS. I currently have a working vibrant that i flash and recover everyday. I now purposly do not disable lagfixes and try random combintions of kernals and roms. Although i have had some crazy outcomes, nothing like that has happened again.
Does any one know for SURE what this means or does any one have any direction on how i can remedy a vibrant that no longer turns on or shows any signs of life. IF SO, AND YOU CAN BE RESPONSABLE FOR THE FIX, YOU MAY HAVE IT AT AN -UN-GODLY-CHEAP PRICE
After playing with a few other devices I returned to the Atrix pretty much the day after the Gingerbread OTA was released by AT&T.
Before I realised that had happened I completely refreshed the software by SBF'ing back to 1.2.6 and then up to 1.8.3.
By the time I got to visit here the bootloader SBF had been released so I just unlocked the bootloader and having read about the dangers of hard bricks with the OTA went for Kenn's Gingerbread version and all was good with the world for 3 days.
The new ROM's started to appear so dove into a few of those via CWM.
After a couple of days I started to get screen freezes.
I found the suggestion of reloading the PDS partition in this thread and that seemed to fix the issue.
Only for a couple of days though and then I went back to lock ups so I reloaded the PDS fix and that made no change.
Drastic measures time.
Now remember I have never loaded the OTA which from all I have read is the main cause of hard bricks so I again went back to the beginning and SBF'd 1.2.6 and back through again to 1.8.3, then Pudding. Not a hint of an issue.
I then reloaded Gingerbread using moto-fastboot and rooted using the fantastic Auto-Bootloader/Root tool, found here
I am still getting intermittent screen freezes. I can't help but think if it was a hard ware issue that the screen would just stay dead but it doesn't. It works for a few hours and then just dies on me. I took the phone apart just to check that all the connectors were properly in situ and they were.
Any ideas out there please ?
I found a backup that worked and flashed it via CWM and had a few hours of relative stability.
Unfortunately tinkering got the better of me and I flashed the D3 camera. Within a few minutes I was back to screen weirdness. This time it was as though the phone had been hacked and I could see random key presses all over the screen.
I did take a copy of the pds file prior to flashing the D3 camera so tried that and...no change.
Going back to the previously stable back up.
Interestingly I found a thread on the Developer form about the contents of the pds file and on Gingerbread the camera file seems to be in there.
I was running Bionix 1.31 on my Vibrant, everything was wonderful! Smooth speed, GPS working great and everything, so I decided to flash DoW14 kernel v1.1.1 HD so I could have voodoo color, sound and BLN. First few weeks phone was working great! Then started to act strangely… sometimes it rebooted or turned off by itself and no matter what earphones I plugged to listen to some music, randomly stopped playing just as if I unplugged the headphones. Then two weeks ago I was using my phone and I put it in my pocket… when I pulled it out to use it again, it was off. Turned it on and it was stuck on the booting screen, after like 10 minutes I realized it was soft-bricked. I can get to download mode, though, so I used AIO Toolbox and flashed back to stock with Odin, flash was successful but when I turned my phone on shortly after the Vibrant screen it rebooted and did the same over and over again. Tried to flash back to stock a few times now and I get the same.
I ended up hard-bricking the phone, so I took it to a guy with a Riffbox and even after restoring the bootloader and all, he's getting the exact same problem.
Your help is very much appreciated!
Sounds like either the battery is dying or the phone.
Update for the OP: After having the bootloader restored and flashing stock with Odin, I get the (data wipe failed) error and after the Vibrant Screen shows up, the phone turns off.
Already tried flashing Eugene's FTDB and it boots me into recovery, I use adb reboot and after the Galaxy S screen the screen turns off and the soft-buttons stay lit but doesn't boot. Flashed back to stock and I get the same data wipe error.
There is a video on youtube of a guy with the same problem, I wanted to share it here but xda wouldn't let me since I don't post much around here.
Your help is much appreciated.
So I upgraded my Dell Streak to StreakDroid some time ago and had been updating along the way as new versions came out. At around 1.9.0 my streak started crashing every which way. So I reverted back to the old version - no luck. Then I reflashed 1.9 still no go. My streak now crashes basically whenever I try do anything useful with it. Whenever I open Maps, Market, browse a page with any pictures, watch a video, or even think about using flash my streak freezes up and then capacitive buttons flash a few times and the Streak reboots. Often times it hangs at it the Dell Logo and reboots a few times before being able to get back into android. Sometimes it never even makes it back to android and I have to pull the battery.
I recently tried Farad's Ginger Streak, it was stable for a while but now has the exact same problem! (Yes I did the amss, dsp, gps flash)
I have run all of the Engineering tests in the Fastboot mode ( I was convinced it was the internal SD card for a while) but they all turn out fine.
Something interesting: Whenever I boot into fastboot mode it says TE Failed and something else in red then it looks like it tries again and finally gets to the "Wait for SD Detect" until finally booting to fastboot mode.
I am at end of my nerves at this point! I can only use my phone as a phone! Everything else crashes it! Please Help.
Thank You.
Please use the Q&A Forum for questions Thanks
Moving to Q&A
adrian.galindo said:
So I upgraded my Dell Streak to StreakDroid some time ago and had been updating along the way as new versions came out. At around 1.9.0 my streak started crashing every which way. So I reverted back to the old version - no luck. Then I reflashed 1.9 still no go. My streak now crashes basically whenever I try do anything useful with it. Whenever I open Maps, Market, browse a page with any pictures, watch a video, or even think about using flash my streak freezes up and then capacitive buttons flash a few times and the Streak reboots. Often times it hangs at it the Dell Logo and reboots a few times before being able to get back into android. Sometimes it never even makes it back to android and I have to pull the battery.
I recently tried Farad's Ginger Streak, it was stable for a while but now has the exact same problem! (Yes I did the amss, dsp, gps flash)
I have run all of the Engineering tests in the Fastboot mode ( I was convinced it was the internal SD card for a while) but they all turn out fine.
Something interesting: Whenever I boot into fastboot mode it says TE Failed and something else in red then it looks like it tries again and finally gets to the "Wait for SD Detect" until finally booting to fastboot mode.
I am at end of my nerves at this point! I can only use my phone as a phone! Everything else crashes it! Please Help.
Thank You.
Click to expand...
Click to collapse
Did you try the 2.3.3 Gingerbread ROM?
If nothing works then the internal SD card (2GB one) maybe faulty.
He mentioned testing the internal SD and that it reported no problems.
To the OP, has this occurred on stock ROMs as well?
I am currently running farad's 2.3.3 ginger rom.
As for the stock ROM I don't remember having the problem back in the day of stock 1.6 from dell but that was a looong time ago...
I was trying to go back to complete stock..but any instructions I find seem to be a bit shaky I tried just flashing the stock rom through streakmod recovery but it never booted(didn't really expect it to since I had to flash a new amss and dsp to get 2.3.3). I was thinking about going QDL but that doesn't flash the 1.6 if I remember correctly. I kind've want to send it in for warranty but I need to get it back to stock for that.
Thanks for taking intrest and helping.
Install the current version of your carrier's ROM on the Streak and try that rather than going all the way back to 1.6. This will allow for the following:
1. The recovery image, the baseband, and the software are all the same version.
2. Eliminates hardware as the source of your difficulties.
If the Streak functions properly under the carrier firmware you install, then you can safely eliminate hardware as the source of your problem, which means the software is the culprit. In that case, install Fards' ROM again and test it. It is possible that your Streak had a bad flash when putting GingerStreak on it.
I believe the directions given on the Dell Streak Flashing Guide on the Wiki might be helpful.
Did he factory reset at any time inbetween all those flashes?
Flashing rom after rom wont fix anything if it's the data that's the issue, custom roms dont wipe data as a general rule (they can, it's simply not scripted to on install as it's usually not required for updating the same rom but to a new version).
I didn't even think to ask that of him. Putting a stock ROM on the device does wipe everything though, so wouldn't he be at the same end point that a factory reset would be at?
A stock update will, but reading his posts i'm unsure he actually managed to get any stock update to complete as he was likely doing it wrong
If I had a penny for every time I factory reset my phone....
I can't tell you how many times I factory reset my phone between rom flashes but it didn't help any. I tried both the factory reset from the "black and white" and from within StreakMod. I have cleared the Dalvik Cache and the batter stats and the entire cache partition. I have run fix permissions out the wazoo. And it never really helped any.
Anyway I just installed the latest stock AT&T Rom (unfortunately they are only at 2.2.2) as suggested by Strephon (thanks for the wiki link by the way that place is amazing! How is it I never ran across it in all my time with the streak...)
The phone seems ok...but so did all the other ROMs when I first installed them. Any ideas on how to "stress test" the device short of installing stuff from market and trying to do everything?
Thanks for all this help by the way you guys are being awesome.
Well nevermind...that didn't take long at all. It is giving me the same problems as before. It is freezing, flashing LEDs and rebooting a few times. It made it into android for a sec while it said "checking SD card for integrity" in the status bar then rebooted again and finally booted into android.
If you're having this problem even with a stock ROM, I believe you have a hardware related problem, and that it was simply coincidence that it happened shortly after upgrading to custom ROMs.
adrian.galindo said:
Well nevermind...that didn't take long at all. It is giving me the same problems as before. It is freezing, flashing LEDs and rebooting a few times. It made it into android for a sec while it said "checking SD card for integrity" in the status bar then rebooted again and finally booted into android.
Click to expand...
Click to collapse
If its not under warranty, I would look on these forums for a disassembly guide and replace the internal sd card. I replaced mine with a 4 gig just for the heck of it.
Alright I guess I will I call Dell tomorrow and see if I can't get it fixed/replaced.
According to the warranty site I should still be under warranty.
I'll post back once I contact dell. Thanks for helping out so much!
Success
Called Dell and they next-dayed me a new streak. Runs just fine. I guess it was a hardware problem after all.
Now Last time I upgraded my streak from stock I had to go through a whole bunch of hoops (QDL, then some intermediate stock roms then streakmod and finally DJ_Steve)
Is this still the recommended path to 2.3.3 or has a better way come around since?
I can laugh about it now, but...
First let me say that I am new to rooting, but not to toys Here's my train wreck comedy of errors, maybe someone can tell me how all of this was even possible?
I started by rooting using Doomlord's rooting script. That went super-easy. Then I decided I wanted to do a nand backup, so following the instructions here I went and installed ROM manager and used it to flash Clockwork Recovery Mod. CWR wouldn't load when I tried to get to recovery mode to do my backup so I asked around and I discovered that my Atrix was not unlocked. It all goes downhill from there.
Following all the unlocking instructions in the Pudding sticky, I used RSDLite, and the IHOP sbf (since I'm on Bell Canada). Well that looked like it was working, but when RSD showed me at 100% reboot after it was all done, the program stopped showing any further status to say it was complete. I've seen this happen a lot before doing other smartphone activities, and I knew it wasn't going to proceed further. So after giving it another 10 minutes just in case, I unplugged from my PC. And yes, of course, now RSD protests that it wasn't done. Typical. I shut down my phone and rebooted. Time for the Fastboot stage.
(at this point I want to point out that BriefMobile's guide is wrong. you do NOT skip to instruction #13 if you are on gingerbread because that does not work. I ran into a couple of other people who reported the same problem with his guide)
(also at this point, I want to clarify that all my USB drivers needed for this to work were installed, and many of the links provided by Pudding sticky are out of date and don't work. or both so I had to get software from other sources and cross my fingers)
So, now onto the fast boot. But wait! Briefmobile guide (linked as the guide to use in Pudding sticky) never informed me I need to put my sim card back in now. or not. I decided since NO instruction is being given either way, I left it out. Fastboot works fine until I enter the "fastboot oem unlock ###" part. Then the cmd window showed zero progress. Once again I wait 20 minutes this time. Nothing. Finally I sigh "here we go again" and unplug, knowing I am now going to be soft bricked, and I was right. I am now showing "unlocked" at bootup, but I am also now stuck in the logo boot-loop. Tried to reflash, that didn't work. Tried to fastboot boot again, that didn't work.
Finally I caved in and did a factory reset/wipe. My phone is now restored to 2.3.6 but I am now also rooted and unlocked like I wanted to be when I started all of this.
The problem is that none of this went anything nearly as smooth as others claimed it would be. Every step of the way caused errors. RSD didnt work properly in the end, and neither did the fastboot. The instructions for Bell Atrix 2.3.6 are all extremely outdated and/or irrelevant in some cases. Before all this happened I was considering flashing custom ROMS. Now I am absolutely terrified to do so, and would rather just use TiBU to freeze some bloatware and leave it at that. How did this all go so terribly wrong? Are days like this normal in the custom ROM scene?
no ideas anyone? I'm still baffled how my phone went through the train wreck that happened in the above post but still manages to be unlocked and rooted after the factory reset and 2.3.6 re-installed OTA. I still have root, and the phone is still unlocked.
omnius1 said:
Fastboot works fine until I enter the "fastboot oem unlock ###" part. Then the cmd window showed zero progress. Once again I wait 20 minutes this time. Nothing. Finally I sigh "here we go again" and unplug, knowing I am now going to be soft bricked, and I was right. I am now showing "unlocked" at bootup, but I am also now stuck in the logo boot-loop. Tried to reflash, that didn't work. Tried to fastboot boot again, that didn't work.
Finally I caved in and did a factory reset/wipe. My phone is now restored to 2.3.6 but I am now also rooted and unlocked like I wanted to be when I started all of this.
The problem is that none of this went anything nearly as smooth as others claimed it would be. Every step of the way caused errors. RSD didnt work properly in the end, and neither did the fastboot.
Click to expand...
Click to collapse
Yep, sounds a little like the night I had when I unlocked the bootloader. If it helps, I've done a little bit of rom flashing since and have had exactly zero problems there. (I'm not a new-rom-every-week kind of gal, just wanted something more functional than stock.)
So that SBF was known to cause a soft-brick; RSD Lite would predictably choke on itself and your phone would display "failed to boot" with a bunch of options. You enter the fastboot oem unlock command and keep going. My fastboot procedure went as advertised, but upon reboot it did stick for ~15 minutes on the startup screen and I had to do a battery pull. After that, up it came and everything was peachy.
Did you pull the battery and attempt another reboot before doing the factory reset? Just curious.
Yeah, second battery pull was because both the phone and the PC cmd window became non responsive after I executed the final stage of the OEM unlock procedure.
The phone went into bootloop. Wouldn't reboot. Had to hard factory reset with the 3 finger salute
Huh. Well, unlocking the bootloader also causes a factory reset, so in this case your end outcome was the same. Sorry it was such a pain in the meantime.
Seriously, though, that's the hardest part. Installing CWM recovery and other roms is a piece of cake, just do plenty of reading before changing anything.
well looks like I got all the final kinks worked out. I froze all of my bloatware with TiBU including Motoblur Launcher and I'm now running my phone using Launcher 7. Everything's pretty zippy now and I think I may have just extended my phone as a keeper for the rest of this year