My Streak just stopped working, was working fine then while trying to fix the Wikipedia crashing browser problem, it stopped being able to boot past the white/black Dell logo.
Events leading up to this.
- Browser crashes on wikipedia
- Googling around, found some threads on how might be related to libskiagl.so not named properly as libskiaGL.so
- Went into local console, su, mv libskiagl.so to libskiaGL.so.
- Browser still crashes, figured a reboot might be needed
- Reboot... stuck at white Dell logo
Tried to undo the problem, managed to get fastboot_mode working, tried a few recovery images which doesn't seem to do anything different (I still get the same 4 options recovery).
StreakMod recovery seemed to work, tried to do a nandroid backup but it got stuck at /firstboot like others have mentioned
But in this state, I was able to get adb working and pushed libskiagl.so and libskia.so hoping that will fix the problem. Doesn't.
Found some threads that mentioned possible hardware failure. The #301# code doesn't work, I dial it in on the bootloader/fastboot screen but nothing happens. Pressing the MMI-BB button seemed to initiate the hardware test.
Every seems to work until the G-Sensor test because of the ALS Value = 0.00
But googling this seems to be "Alternate Line Service" which I don't think I have, so in order to proceed, I just tapped Fail.
Apart from this, everything seemed to pass, including the internal SD which showed the size, the permanent non-protection status.
Factory reset didn't help.
I wanted to try downloading a stock Dell image but the links to mobileupdate.dell.com appears dead.
So I'm at my wits' end about how to revive my Streak.
What else can I do?
Thanks in advance for any help.
boonadx said:
My Streak just stopped working, was working fine then while trying to fix the Wikipedia crashing browser problem, it stopped being able to boot past the white/black Dell logo.
Events leading up to this.
- Browser crashes on wikipedia
- Googling around, found some threads on how might be related to libskiagl.so not named properly as libskiaGL.so
- Went into local console, su, mv libskiagl.so to libskiaGL.so.
- Browser still crashes, figured a reboot might be needed
- Reboot... stuck at white Dell logo
Tried to undo the problem, managed to get fastboot_mode working, tried a few recovery images which doesn't seem to do anything different (I still get the same 4 options recovery).
StreakMod recovery seemed to work, tried to do a nandroid backup but it got stuck at /firstboot like others have mentioned
But in this state, I was able to get adb working and pushed libskiagl.so and libskia.so hoping that will fix the problem. Doesn't.
Found some threads that mentioned possible hardware failure. The #301# code doesn't work, I dial it in on the bootloader/fastboot screen but nothing happens. Pressing the MMI-BB button seemed to initiate the hardware test.
Every seems to work until the G-Sensor test because of the ALS Value = 0.00
But googling this seems to be "Alternate Line Service" which I don't think I have, so in order to proceed, I just tapped Fail.
Apart from this, everything seemed to pass, including the internal SD which showed the size, the permanent non-protection status.
Factory reset didn't help.
I wanted to try downloading a stock Dell image but the links to mobileupdate.dell.com appears dead.
So I'm at my wits' end about how to revive my Streak.
What else can I do?
Thanks in advance for any help.
Click to expand...
Click to collapse
QDL tool to push 2.2 305 is my fallback whenever I really Bork my phone.
Sent from my Dell Streak using XDA App
BigBopper said:
QDL tool to push 2.2 305 is my fallback whenever I really Bork my phone.
Click to expand...
Click to collapse
Thanks for pointing out this tool. Still downloading it although I've fixed my phone within like 5 minutes of waking up. Just in case I bork my phone again
Reading back what I did, I feel totally stupid since it should had been blindingly obvious that I couldn't possibly change the character case on a *nix system and not expect things to break, or that if I could adb push, then I could had just done adb shell too to mv the file back to the correct name.
Note to self and others: Do not attempt to mess with phone while on flu medication.
Related
Running AT&T Dell Streak, 1.6 6601. Being slightly irritated with the lack of updates by ATT, i downloaded QDL and went through the walk-through. Everything seemed to go smoothly. However, on reboot after the QDL tool was complete I've frozen on swirling dell screen. Anyone hit this snag? Possible bad img? Currently running QDL tool 2.7.4.8; anyone had success on a previous version? I've ran the QDL tool more times than i care to admit. I apologize if this has already been addressed but I've read so many threads on so many boards I need to walk away from the computer for a while.
I have also tried a factory reset (via volume key boot and and clockworkmod) neither of which worked (another problem for another thread). Any help or guidance would be very much appreciated.
Cheers,
Zac
keenercoug said:
Running AT&T Dell Streak, 1.6 6601. Being slightly irritated with the lack of updates by ATT, i downloaded QDL and went through the walk-through. Everything seemed to go smoothly. However, on reboot after the QDL tool was complete I've frozen on swirling dell screen. Anyone hit this snag? Possible bad img? Currently running QDL tool 2.7.4.8; anyone had success on a previous version? I've ran the QDL tool more times than i care to admit. I apologize if this has already been addressed but I've read so many threads on so many boards I need to walk away from the computer for a while.
I have also tried a factory reset (via volume key boot and and clockworkmod) neither of which worked (another problem for another thread). Any help or guidance would be very much appreciated.
Cheers,
Zac
Click to expand...
Click to collapse
My first thought is a bad download of QDL Tool.. I would delete the version and folder you have, re-download and attempt once again. Make sure you leave the battery out of your streak one min. prior to plugging it into the computer. Then once it it recognized by QDL, run, once finished unplug the phone and allow it to reboot. If still no go, please let me/us know. Good Luck
ARHMogul said:
My first thought is a bad download of QDL Tool.. I would delete the version and folder you have, re-download and attempt once again. Make sure you leave the battery out of your streak one min. prior to plugging it into the computer. Then once it it recognized by QDL, run, once finished unplug the phone and allow it to reboot. If still no go, please let me/us know. Good Luck
Click to expand...
Click to collapse
Thanks for the response. Gave it a shot and still frozen. A quick question, for any programmer who knows this system, what is it trying to load at the spinning dell screen? Is it loading the boot.img? I thought about trying to just flash that via fastboot after running the QDL tool. Bad idea? Second question, anyone know where to find an older version of the QDL tool? Basic forum and web searches have lead me nowhere.
Last question, if for some reason the streak is fubar, would returning this to best buy with some jacked up version of 2.2 and clockworkmod on the phone void its warranty?
I really appreciate any response. Cheers.
try a factory reset in the 1st menu in recovery (don't go in clockwork). The factory reset within clockwork is broken - doen't work correctly. This will hopefully fix it.
Kohawk09 said:
try a factory reset in the 1st menu in recovery (don't go in clockwork). The factory reset within clockwork is broken - doen't work correctly. This will hopefully fix it.
Click to expand...
Click to collapse
That was my first reaction. I tried the factory reset via volume key reboot. it flashes to the white screen stating the factory reset but it reboots to the frozen loop... i think shes s.o.l... I believe something has to be corrupt. Its an odd issue. Is there a way to factory reset via fastboot?
Thanks again
i'd go to webchat.freenode.net channel: #dellstreak to see if you can snag a copy of the lower level version of the QDLTool. If fixes corrupt firmware, which you may have if the factory reset is giving you issues. Just explain your issue and someone is usually in there and can help.
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?
Had my Prime 2 days, got it rooted.
After ICS install and camera update it worked for a while. Then it rebooted and it's stuck in a bootloop. I can't even power it off.
Yes, I've used the reset pinhole.
I've rebooted into Asus recovery but all I get is the "dead droid" screen. I'm assuming it's because I don't have my SD card in.
Any suggestions?
I'm thinking that if I can get my hands on the stock ICS zip direct from Asus I might be able to run that.
I suspect, from this thread that the issue might be that the Launcher has gotten corrupted.
Update:
Ran the battery till the unit shut off and didn't reboot.
Charged the battery for 4+ hours, unplugged it and tried to boot up. Same story, bootloop.
ADB sees my Prime and can issue commands.
Any suggestions? I'm getting desperate here.
Edit again: I can pull a logcat, any suggestions what I'm looking for? I'm not sure what subset of Linux commands are in Android, can I do a kill -9 if I identify a rogue process?
I'm pretty sure top won't work, and a lot of my Linux knowledge is pretty rusty.
Same here
I'm stuck in boot. I rooted it from zedo's instructions (that guy is a whoot!). Afterwards I installed "VM Heap Tool"(by martino), restarted the tab from the VM app and it got stuck in the boot screen.
I'm stuck and don't know what to do. I don't really know codes, so I'm pretty much up a creek without a paddle.
Any help would be MUCH appreciated!
Bumble-Bee has solved this issue for you on IRC but I figured we should post the solution to *your* specific problem here for others. Hopefully it helps them if they run into a simular issue.
With a boot loop try shutting down the tablet by holding power for 30 seconds. If it doesn't shut down then hold power for 30 seconds and after it vibrates hold power and volume down. This should get you into the recovery process.
The first thing to do in trying to resolve this issue (and what solved it for Col_kernel) was to do a data wipe using the recovery menu. Directions on how to perform this can be found here . this will solve the majority of bootloop issues.
The second thing to try to do is to perform a recovery using a signed zip from Asus. the ICS 9.4.2.11.1 is the latest one as of this thread and can be downloaded at the link provided there. Download that and place it on a microsd card. Load the card into your prime and boot into recovery and perform a recovery.
after that, start asking for help
I tried both solutions suggested and they didn't work for me, however I modified the services.jar in systems\framework. Looks like it tries to recover and then goes to an android on his back with an exclamation mark. I can't get adb to recognize my device either. I'm assuming my only options are to send it back to Asus or wait til I can flash at this point?
I should have said that I have already done the reset. Also, I cannot install anything on the tablet, since I cannot even access it. My PC won't even recognize it.
Update: I just spoke with Asus support. They said that if all these options are exhausted, I should return the tablet. That's what I'm going to do today. [good thing I have all my apps backed up. #TiBu!]
I had a dreaded boot loop issue a week or two ago..
I attempted to root the prime using Max Lee's one click using my MBP..
ADB failed to push SU up properly but the script kept running.
After waiting an eternity I bounced the tab to find it in eternal bounce mode and complaining of a corrupted launcher.
Luckily enough I was able to still detect the device and run ADB commands, so I was able to run the same root method (under windows this time) which worked a treat.
Had me really worried for a while, but got the device working again and rooted it (win win)
Anyway, it's interesting that a rogue file or an incomplete binary in the /system/bin folder (which shouldn't have been called by anything) was causing the boot loop!
wells79 said:
I had a dreaded boot loop issue a week or two ago..
I attempted to root the prime using Max Lee's one click using my MBP..
ADB failed to push SU up properly but the script kept running.
After waiting an eternity I bounced the tab to find it in eternal bounce mode and complaining of a corrupted launcher.
Luckily enough I was able to still detect the device and run ADB commands, so I was able to run the same root method (under windows this time) which worked a treat.
Had me really worried for a while, but got the device working again and rooted it (win win)
Anyway, it's interesting that a rogue file or an incomplete binary in the /system/bin folder (which shouldn't have been called by anything) was causing the boot loop!
Click to expand...
Click to collapse
Odd. I had the same issues. I started rooting mine on my mac, then finally moved to my pc. It rooted flawlessly on my pc.
So, I don't know if it was the root with a corrupted file, or the VM Heap Tool that I activated in it that caused it to get stuck in bootloop. But... I didn't restart the tablet until after the VM Heap Tool. In other words, it could have done the same thing without the VM Heap, I just wouldn't have known it, because I didn't restart it right after the root.
Make sense?
Hello, after playing with a tablet I got boot loop so below is solution for this.
This is what I wrote first:
I purchased Chinese tablet called CyberNav, there is link to the website with specs http://www.dracotek.com/cybernav-7-...ps-navigator-ultra-slim-wifi-8gb-gps70yw.html It works great and is worth the money. I received- on request- firmware for it, but it is with .img extension and I have no idea how to get to the files. Attached application PhoenixCard should install it on sd card but it does nothing. So there is my question- can anyone help me with it? Possibly root it? Or update to newer firmware version? I'll post a link to, just need to upload it to my dropbox on my next break at work.
Sek
im pretty sure you need a 3rd party application to flash that firmware, i think you load the .img file into the software on your pc, connect tablet in flash/recovery mode then flash it that way, dont know which software you would need to use though , sorry i cant help further
There is link to rar package http://db.tt/jm7eHfbq
If there is someone who wants to spend some time... Please help.
Bump
Some new infos:
As far I found out tablet is detectable during boot in adb, but it stays in boot loop. I think I've got right usb drivers.
I tried unyaffs the .img file using C:/unyaffs/unyaffs pw08.img but it shows file corrupted (might be wrong method?).
Logcat attached.
Maybe there is someone who will find what it's missing...
I see there is nobody who can help me, so... If some of u have similar problem with chinese tablet- bootloop, can't flash it with LiveSuit our update from sdcard, I found solution which worked for me. Using adb, pulled catalog /dev/data/ to hard disk, then deleted all dalvik cache, installed by me apps and almost every other file from /data on my hard disk. Then typed adb remount, then adb shell rm -r /dev/data/* to delete all data catalog on tablet. Then pushed /data catalog from my hard disk to tablet, and finally adb reboot. And it WORKS! Booting without problems. I wasted 4 days on research how to turn it in flash mode etc. But it was very simple.
Cheers
Sek
Hi, sek111
It was necessary to use the LiveSuite to flash through usb.
Thank you very much, from your post, I found the firmware for my tablet.
An experience with another low cost tablet with Bootloop
I happen to got my tab (Wammy from WickedLeak.org) stuck in BootLoop and was struggling to get a way out for the past 3 days, checking almost all of the posts for this issue!
The tab would stuck on the android loading animation despite running for 2-3 hours and after several hard reboots, it throw-ed following error-
Encryption Unsuccessful
encrytion was interupted and cant complete. as a result the data on your tablet is no longer accessible
to resume using your tablet, you must perform a factory reset. when you set up your tab after the reset, u'll hav an opportunity to restore any data that was backed up to ur google account
Click to expand...
Click to collapse
Despite going for the factory reset, it still didn't workout as the reset activity never completed or proceeded. I happen to be a beginner/noob and was trying my luck with possible solution but was comfortable with ADB stuff and workaround. Well i checked the solution which sek111 offered in this post and it was most closely helped me out. So i would like to Thank him a ton for sharing his solution.
Another method for few others if you don't get through the technical stuff and handling all the flashing tools, i was successful in bringing up the setting window of my tab and chose to do Reset via GUI which worked. Actually my battery got drained out to 7% and a popup message for same displayed while i was on the above error page. I selected the "check battery" option from that pop up and got my way out via factory "Backup and Reset" option under settings.
I hope this might help few people if not all! But the XDA forum is great and everyone will find a solution here. Cheers!!!
So I got this wm8850 chinese generic tablet. The camera is in the front in the middle (wide). It was shipped to me with 4.0.3 in boot loop. I soon found out that it boots into safe mode when I usb to pc. This is the furthest I've gotten with it so far. I can adb into it and have already tried to wipe data. It seems like since its from factory screwed up that a may need to reload the firmware or the os or something. Im kind of a noob because I only have my droid x. I've gotten it out of a boot loop before but I also knew what I had done to cause it so I fixed it. I tried to follow seks adb commands but im too noob to do it I guess. I was able to wipe data and dalvik-cache. Issue still occurs . If anybody can give me some adb commands than can help I would greatly appreciate it. Im fairly sure that I found the firmware elsewhere on xda. I thank you guys for any help at all you can give. I don't wanna send it back without trying everything software related as I can, but ill send it back if I can't fix it or if I brick it
Sent from my DROIDX using xda app-developers app
i have same problem in my china mobile.. dupad k1 ... after in installed new boot screen, device stuck in boot... please help to recover my device in step by step....
Hey all, this is my first post on this forum. I registered just to let my voice be heard.
Let me just say that I have done extensive research into these problems but I don't want to brick my phone so I want to know the direct steps for me.
OK my problems are:
Upon turning on the phone the original Motorola logo is gone and is instead replaced by:
"Unlocked. PwrReason: PWR_KEY_PRESS. OS will boot in 5 seconds. Press a key to stop countdown. Avaliable Modes are: " and lists 14 different modes I can choose
This happened after I accidentally deleted my pds folder or something of the sort. I must've partitioned something accidentally and as a result my phone did not boot the next time around. It booted after I did a battery pull but gave me the next problem.
Upon booting into CM10.1 I noticed that the soft keys would not work. The entire screen was recognized as one big touch surface.
I deduced that some file was deleted which makes the screen recognize the soft keys, so I proceeded to do some research into it. The methods I saw to do were doing some sort of pdsfix which is not recommended unless necessary, which in my case is very necessary. I can boot into Romracer's recovery (5.0.2.7 I believe it is) as well as my OS. Everything is working except for those problems I listed. I am not sure if my phone can boot into fastboot but I can try. Please post your answers because I really need to get my phone working perfectly again. At this point, it is only useful for texting and a little music (and settings). I can't go into much else without restarting the phone each time (you must know why).
EDIT 15/04/13
-----------------------------------------------------------
I just flashed pdsfix(gingerbread).zip and I am now able to use my phone at normal speeds and even overclock if necessary. I was running epinter's CM10.1 Rom
Fixed half the problem!
Okay so after many hours of trying, I managed to install the drivers for fastboot on my computer and did the fix for the pds file.
First I downloaded moto-fastboot.zip and extracted to my C:/ drive.
Then I tested if my device was recognized. It didn't recognize it at all, so I went into device manager.
In device manager there was my problem. I saw fastboot with a yellow exclamation sign. I right-clicked it and directed it to where I had previously downloaded fastboot drivers. (Found them here: FASTBOOT DRIVERS
It installed nicely and when I tried the commands listed in Method 2 on this page PDS Partition Fix it worked perfectly!
So I proceeded to restart the phone, no issues. But the Motorola logo at the very beginning is still not there. It says unlocked at the top left and displays the same options as before. The phone is still fully functional without it, but I want to get it back. I will be doing more to fix this though.
But the best part is that, my soft-keys are working perfectly! :laugh: I do notice a little lag in the system but that will be fixed soon. Hope this helped anyone who didn't know what to do.
P.S. If you find a way to restore the Motorola logo on boot, please tell me!
http://forum.xda-developers.com/showthread.php?t=1423763
Logo and animation
Mojar7070 said:
http://forum.xda-developers.com/showthread.php?t=1423763
Logo and animation
Click to expand...
Click to collapse
Perfect! Thanks much for finding that for me. I now have the problems fixed except that my cpu won't clock above 608 mhz even when I put the min clock slider higher than that value.
I suspect that perhaps I flashed the froyo pdsfix instead of gingerbread. Maybe that is causing the problem. I'll try and post my results soon.
My Atrix 4g is fixed!!
Wow I can't believe I finally fixed it! It was as I suspected. After downloading the pdsfix(gingerbread).zip I rebooted my phone into fastboot and proceeded to flash the zip. And who would've guessed it? I am now able to clock at usual speeds including the 1000MHz of old ^_^. I am sooo glad I found this forum. If anyone had similar problems you can try the steps I did.
P.S. For the record I was running epinter's CM10.1 Rom for the Atrix 4g. I may go to Neutrino's in the near future, but I am just glad to have my phone back in working order :laugh::laugh: