Fellow XDAers,
I'm in dire straits for some assistance.
I've been a member for some time now, lurking here and there, contributing when I have something of value. I've been through several phones, with an EVO 4G being my latest acquisition. Once I left Sprint as my carrier (Monthly rates were just too high for my blood), I was left with a phone that I couldn't flash to another carrier worth my valuable dollars (yes I know I could flash to Cricket or Metro PCS but I've never been a fan of their service). So, I started reading this forum and may others in regards to rooting and flashing.
After accomplishing this and having a case of ORD, I finally settled on FreshROM.
It worked well and outside of the occasional lag, I was pretty happy with my setup. Then a friend of mine finally converted from the TP2 to the EVO 3D. After answering several of his questions about rooting and flashing, he made the leap and flashed InfectedROM w/ beats audio baked in.
Being an audiophile and music blogger, I was of course interested to see if there was a ROM available w/ beats in it for my device. I found this one HERE called BlazingROM and installed the file from the first D/L link using the normal SD card method and Clockwork.
I of course cleared the Dalvik and the other cache. I didn't make a backup of my FreshROM as I already had one on my SD Card and in Dropbox for safekeeping as well as a Stock Odexed backup just in case.
The ROM installed just fine and I was enjoying the different elements of it while re-installing my apps with Titanium Backup when, the ROM started giving me messages that I was running low on internal storage space. I stopped TB and started using Apps2SD to move what I'd installed so far to the card. I then went back to TB to finish but with every installation, I'd get the "Internal Memory Low" message again.
By this time, I was scratching my head. I mean, yes I do have 20 must have apps but with FreshROM and Apps2SD, I was able to have almost all of those apps on the SD card without any issue. Now with this BlazingROM, why would I be encountering this issue? I then noticed that this new ROM had some sort of baked in Task Manager, which was the process giving me the error messages. So I attempted to use it instead of A2SD to move anything I could to the card. After doing so, I once again went back to TB to finish but upon the first install, I got the error message again. By now, I'm getting a little pissed and I still haven't even tried out the beats audio part of the ROM yet.
So, I decided to go back to basics. I opened Clockwork and did a Dalvik wipe and a re-flash of the ROM. Once that finished, I re-booted the phone. It was to no avail, as the Task Manager happily told me my Internal Memory was still too low.
I kind of panicked, not really…but a little…but I kept my wits about me and quickly went back to the post I got the ROM from in search of answers. I scoured any and all related replies which the consensus of brought me to the conclusion that my SD card should be formatted and then partitioned to accommodate the BlazingROM’s internal memory quirk.
Having no need to ever do so before, I then asked Mr. Google how it is properly done. Of course searching there brought back many links and after reading the majority of them, I settled on the method that involved ditching Clockwork Mod for Amon Ra’s recovery as it had more necessary options to partition than CW. That accomplished, I then found a guide for the different sizes of partitions as well as a discussion on the difference between EXT2 and EXT3 as well as the pros and cons of upgrading from one to the other.
I opted to leave the swap size at 0 (zero) and go for a 512MB partition. Once that was done, I then once again went through the steps to get BlazingROM flashed and running and once again, the evil “Internal Memory Low” message laughed at my efforts.
Fine I thought, I'll just go back to my good old trusty FreshROM until I come across another one w/ beats audio and none of these memory issues. I turned off the device, went to the Bootloader, chose Recovery and from CW Recovery, wiped the Dalvik again and chose to install FreshROM from zip on SD card.
Everything was going fine. It installed and I chose to re-boot the phone. That's when tragedy struck.
When my phone attempted to start up, the normal Boot Screen I'd come to love, where if you have the volume up, you see a hybrid of Tux and Andy while being greeted with a stylized "FRESHHHHHHHH!!" became stuck in the dreaded Boot Loop.
Back I went to Mr. Google to get some answers. This time he directed me to posts from here at PPCG to XDA to Android Central and various others. Almost every post I read instructed me that a Boot Loop could easily be fixed by placing the PC36IMG on the roots of my card and allowing the Recovery to find it in the Bootloader. I did so but it didn’t seem to make any difference. The phone continued to loop.
I did a battery pull but this time when I went to the Bootloader, ensured that it was indeed finding the PC36IMG and re-booted, I ended up with the Black HTC screen with four exclamation marks in the corners.
I’d never seen this screen before…so now I’m really panicking.
Off I went again in search for a solution. This time, I came across posts at all of the sites mentioned before but with a different solution involving the use of an RUU to take the phone back to it’s out of the box stock ROM state. Fine I thought. The phone will still be S-Off and I’ve got everything backed up on TB and Dropbox, it won’t be hard to get it back to where it was.
After checking the posting dates to ensure I was getting fresh info and links, I ended up at Shipped-ROMS. I D/Led what appeared to be the latest one and most recommended (RUU_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2.15.00.11.19_NV_1.90_release_161482_signed.exe) to remedy my issue along with some instructions in a Word Doc regarding it as well that I found on another site. I even followed another post that added that I should install HTC Sync in order to have the right drivers on my PC for the RUU to work properly.
Long story short, after trying 10 different RUU’s as well as installing HTC Sync, uninstalling Sync and installing different HBoot drivers (2.10, 2.02, etc.) in all possible combinations, the only thing I’ve managed to do is end up with my phone still showing a Black HTC four exclamation mark screen. The only time the screen is different is when the RUU fails (either due to Error 152, Error 238 or Error 330) and I unplug the USB cable. The screen then shows an RUU Bootloader with these results:
SUPERSONIC EVT1 ENG S-OFF
HBOOT-2.10.0001 (PC36****)
MICROP-041f
TOUCH PANEL-ATMELC03_16ac
RADIO-2.15.00.0808
Mar 30 2010, 11:24:04
RUU
Parsing ….[downloading ZIP]
[1] RADIO_V2 -OK
[2] SPLASH -Fail-PU
[3] RECOVERY -Fail-PU
[4] WIMAX -Fail-PU
[5] USERDATA -Fail-PU
[6] BOOTLOADER -Fail-PU
[7] SYSTEM -Fail-PU
[8] BOOT -Fail-PU
Partition update fail!
Update Fail!
For some reason, each and every RUU gets up to around 32% to 40% and begins to show signs of failing while Updating User Data.
I’m reluctantly conceding defeat on this, as I have no clue as to what to do now. I’ve even gone as far as downloading Android SDK to try and figure out how to push the RUU or some kind of fix through ABD Shell.
If anyone has anything constructive that could help, I’d appreciate it greatly.
Wow. sorry my friend. I feel your pain as something similar happened to me with a HD2 once..my nand had gone bad. it seems you have pretty much tried everything. only recommendation I have is if you are still able to flash stuff try older version radios (downgrade radios first) before you try to RUU and don't neccesarily go for latest RUU you find. also leave out your SD card while trying the RUU. - fully format your SD card is also another thing I did not see in your long list of things you already tried? if you can't flash thru recovery (or maybe even your recovery somehow is messed up!?) try this new tool called Android Flasher I just saw someone has released on XDA. looks very good but I have personally not tested it yet. http://forum.xda-developers.com/showthread.php?p=18279765#post18279765
good luck maybe one of these combinations might work.
Gonna try and see what this can do to help later this evening. I appreciate the help and will report back what happens.
Related
I'm having a little trouble and I'm sincerely hoping you'll help. I've tried flashing my Eris using the file, "Evil_Tazz_3.zip" and my Eris is now bricked and stuck in a bootloop. All it will do is show an animation of the sketchy letters ANDROID falling down the screen and then a smoky light following close behind it reveling the Droid itself. And it'll repeat this animation rapidly about 100 times before freezing and then restarting the whole process all over. To be frank it pisses me off because it always seems that I'm the only one who has trouble with this stuff.
My Eris is rooted and it does allow me to access the recovery screen. What am I supposed to do?
Anyways, thanks for your time.
Best Regards -Joseph Bergen
jbergen said:
I'm having a little trouble and I'm sincerely hoping you'll help. I've tried flashing my Eris using the file, "Evil_Tazz_3.zip" and my Eris is now bricked and stuck in a bootloop. All it will do is show an animation of the sketchy letters ANDROID falling down the screen and then a smoky light following close behind it reveling the Droid itself. And it'll repeat this animation rapidly about 100 times before freezing and then restarting the whole process all over. To be frank it pisses me off because it always seems that I'm the only one who has trouble with this stuff.
My Eris is rooted and it does allow me to access the recovery screen. What am I supposed to do?
Anyways, thanks for your time.
Best Regards -Joseph Bergen
Click to expand...
Click to collapse
Whatever you do, DO NOT DO ANYTHING ELSE UNTIL BTFB0 responds to your plea for help.
Do not just start trying different solutions, DO NOT FLASH ANY RUU, if you know what that is. BTFB0 is the guy who can get your phone unbricked if anyone can. He is the expert, I won't pretend to be able to duplicate his knowledge in this area.
Be patient until he has a chance to see this. You don't have to PM him, I'm sure he'll respond when he has a chance here in public. He will ask specific questions about what version of bootloader you have, 1.47 or 1.49, and you might as well find out if it's S=OFF or S=ON.
Also, do you have Amon RA recovery on your phone and can you get to it?
Have you tried flashing anything else since your phone has gotten stuck in this boot loop? If not and you can get into recovery still, then simply wipe data, wipe dalvik, and try flashing again. Don't worry you're phone doesn't sound bricked, just like you got a bad download or an error when flashing the rom. I would probably try a different rom or at least re-download the one you want to use.
It may still be wise to wait for BTFB0 to get here and offer some more advice as I am sure he has more knowledge in this area than me. But I do feel confident that he will say the same thing as I have.
Well, the OP merely said that he is having trouble with a specific ROM; he didn't mention failures during flashing; so, his problem could be as simple as having failed to "wipe" before flashing his ROM.
jbergen:
If you can boot into a custom recovery, your phone is not "bricked". It's not even soft-bricked; it's just not booting into the main OS correctly.
Providing as much detail as you can is helpful to people that are offering help to you; in particular, the following pieces of information:
- What recovery is on your phone? (Amon_RA, Clockwork? What version #?)
- When you are flashing the ROM file with your recovery, do you notice any "E:" messages?
An "E:" at the beginning of a line on the screen means that an error occurred!
- Are you having this same trouble on more than one ROM, or is this the only ROM you have tried since you rooted?
- What method did you use to root the phone?
- Did you use the "Wipe data/factory reset" menu item before you flashed the ROM file?
- Did you make any Nandroid backups that you still have on your SD card? If yes, did you attempt to restore one? What was the result? (BTW, every rooted phone user should be making Nandroid backups before they flash ROMs - no exceptions.)
- Do you have a media card slot or USB card reader device that will allow you to copy a different ROM file onto your SD card? -OR-
- Do you know how to "mount" the SD card onto the PC when your recovery is booted? (On Amon_RA, it is called "Toggle MS-USB" or something like that; it's also in the Clockwork menu somewhere too)
Given the information you have provided, there are any number of things that could be going on. I would suggest downloading a different ROM to your PC (let's say the stock HTC Eris March 2011 ROM), and then transferring it to your SD card. Then,
- Verify the exact size of the file and/or MD5 signatures of the file (if the developer provided it).
- make sure your phone is well charged
- perform a "Wipe data/factory reset" from the recovery menu
- Flash the ROM file from the recovery menu - and pay attention to the screen to see if there are any `E:' errors
- If there are errors, there is no point in attempting to boot the phone
- If there are no errors, boot the phone.
- Report your results here - and answer the questions that I asked.
So this time I'm going to be a little preemptive. I ordered a GTab like a week ago, spent the time waiting for it to get here doing a ton of reading so I could go ahead and get it flashed right away. It got here and I immediately ran into problems. I got CWM on there no problem and first flashed [ROM-AOSP]G-Harmony Gingerbread 2.3.3 with Honeycomb elements(UPDATED 4/17) with no problem. Didn't like it so tried to flash the CM7 nightly (which I have running on my evo and hero) and it kept getting stuck on the black screen with that just had "android" written on it really small. Since I hadn't anticipated running into something like that, I did even more reading. Decided to try some more roms and see if I had similar problems. Ran into similar problems with the vegan GB except it would hang on the powered by the "gtabdevs" screen or whatever it said. Vegan 5.1 or whatever the other Vegan one is I could get booted up fine though. So I read some mroe since I really wanted CM7. Discovered that I might need to re-partition, so went into CWM and repatitioned to what everyone was saying was the correct settings. Still a no go and got stuck on android screen. So after even more reading I kept seeing everyone saying NVFlash. So I found it, downloaded everything, read the sticky post on how to do it like 4 times before trying it, then gave it a shot. Put the tab into APX mode (vol- and power) and flashed everything and then when it was done, it was stuck in the APX mode. Very irritating considering I had only had it for about 6 hours. Anyways, sent it back and am getting a new one. It will be here tomorrow morning.
Sooooo, after that long winded explanation of everything, here is my question... How the **** can I get CM7 on my tab without wrecking it again? I did a ton of reading, and nothing I had seen helped at all. Everyone says wipe this and wipe that, or mount these then wipe those, or nvflash then do it and so basically I'm just not sure what to do. I WILL NOT use the nvflsh again and risk getting the APX loop, so any good advice would be most appreciated.
Thanks in advance
I just email walked my sister through installing CM7 on her new gtablet.
Have CM7harmony7.02.zip (or whatever.....7.02 is latest stable release....there is a newer nightly though if you prefer that), the gapps.zip on your computer.
install Clockworkmod recovery on your tablet like you did before.
Boot into CWM and partition sd card, 2048 for first partition and 0 for the second one.
attache via USB to your computer, mount usb option in CWM and copy the ROM.zip and the Gapps.zip to your tablet. Eject tablet from computer (USB eject) and unmount in CWM.
- wipe data/cache (factory reset)
- advanced, - wipe davlik cache
install .zip from sd card
(install the ROM, then choose to install .zip from sd card again and install gapps).
Reboot.
Make sure your tablet is NOT running OS 3991 (very unlikely) or 4349 (possible though unlikely) before doing any of this. (ie...boot tablet out of box and check it's OS version in settings).
Thanks for the walk through. Hopefully it will go smoothly this time around. I'll post back tomorrow after it gets here on if it worked out or not.
If it does have one of those 2 versions on it, I assume I just use the down grader from the thread taking about those 2 versions?
Sent from my PC36100 using XDA App
ix3u said:
Thanks for the walk through. Hopefully it will go smoothly this time around. I'll post back tomorrow after it gets here on if it worked out or not.
If it does have one of those 2 versions on it, I assume I just use the down grader from the thread taking about those 2 versions?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Correct, downgrade and then proceed.
Even though I'm 100% sure that at some point of me trying last time that I did in fact do all of those steps, it was a no go.....But this time, I'm sitting here watching the CM7 boot screen
Thanks a ton
First let me affirm that a little knowledge is dangerous and I am proof to that.
I unlocked, rooted, originally had Amon Ra, but was used to CWM on my Droid, so loaded it. Tried Scott's Ice Cream Sand, only to find myself staring at the 4G screen. Went into CWM recovery, recovered from several days earlier, but froze at the "htc" screen.
Still had access to CWM so wiped data/cache, tried again w/ no result. After several battery pulls w/ frozen screen, when booted, I got the FASTBOOT screen w/ the other choices, but before I could make any selections, it scrolled through several items saying "no image", then droped me at HBOOT.
Now I'm looking for the umteenth time at a screen saying:
****UNLOCKED****
VIGOR PUT SHIP S-ON RL
HBOOT-2.11.0000
eMMc-boot
Oct 6 2011.15.43.22
Parsihng...[SD ZIP]
[1] BOOT
Do you want to start update?
<VOL UP> Yes
<VOL DOWN> No
I have tried the "update" and it processes, I reboot, but am left in the same loop. The drivers in my Win 7/64 are up to date. The phone is recognized as a device, but I have no USB access to try flashing from the PC.m to be back w/ Amon Ra and no access to CWM. I have pulled the SD and deleted PH98IMG, but suspect another is on the phone's memory. I have pulled the SD and the SIM, but still can't get into the phone to reset, flast, or whatever.
I suspect I am "bricked"... don't want to hear confirmation, but better than another 36hrs of repetitious nonsense.
Did you flash the boot.img that goes with the rom you restored? Restoring doesn't restore the boot.img, so you gotta do that manually. It won't boot otherwise. And I'm assuming the PHxxx.zip you have in there already is the boot.img for Scott's rom.
Sent from my bad**s mofo HTC Rezound
Using the PC, I removed the SD and copied the PH98IMG file from CleanFLASH 1.0 to the SD card. When I got into FASTBOOT it looped, but took me back to the standard AmonRa menu w/ Recovery. I selected Recovery, then toggled the USB setting. That allowed me to get the PC linked. Then I flashed the PH98IMG again, it worked, and then flashed the "Stock Rooted ROM-Vigor-WWE2.01.605". It went, but FAILED at the reboot/bootloader command.
Again, I took out the SD card, removed the PH98IMG from it, replaced it, got into Recovery and flashed the ROM from the SD. I now am back in business.
I thought I was pretty handy with PC's, but like troubleshooting them, I found that often it boils down to persistence, trial and error, and luck. I DO SO UNDERSTAND THE PANICKED MESSAGES THAT SO OFTEN FREQUENT THESE FORUMS, and also understand the way they must tax the patience of the more proficient. Even so, please be patient and forgive me for adding to the mess. Maybe this will assist someone else.
Thank you for your help
wfpabst said:
Using the PC, I removed the SD and copied the PH98IMG file from CleanFLASH 1.0 to the SD card. When I got into FASTBOOT it looped, but took me back to the standard AmonRa menu w/ Recovery. I selected Recovery, then toggled the USB setting. That allowed me to get the PC linked. Then I flashed the PH98IMG again, it worked, and then flashed the "Stock Rooted ROM-Vigor-WWE2.01.605". It went, but FAILED at the reboot/bootloader command.
Again, I took out the SD card, removed the PH98IMG from it, replaced it, got into Recovery and flashed the ROM from the SD. I now am back in business.
I thought I was pretty handy with PC's, but like troubleshooting them, I found that often it boils down to persistence, trial and error, and luck. I DO SO UNDERSTAND THE PANICKED MESSAGES THAT SO OFTEN FREQUENT THESE FORUMS, and also understand the way they must tax the patience of the more proficient. Even so, please be patient and forgive me for adding to the mess. Maybe this will assist someone else.
Thank you for your help
Click to expand...
Click to collapse
It isn't that it taxes our patience it is the fact that there are about a dozen threads on this already. A little time spent searching and you would have had your answer.
Sent from my ADR6425LVW using XDA
these threads make me want to never come here again!!
how hard is it to use google. I mean cmon!!
andybones said:
these threads make me want to never come here again!!
how hard is it to use google. I mean cmon!!
Click to expand...
Click to collapse
No kidding.
Just run the RUU if you are that messed up.
I do understand the use of the search function to not clutter the forums but at least he posted in the right section.
Sent from my ADR6425LVW using XDA App
This question has been answered...search
Again I do appreciate the response, but rest assured, I spent nearly two days searching through forums for answers, and none seemed to specifically answer my problem... although I'm sure I missed some. The searching did provide me with alternatives, when combined, appeared to deal with the problem...
wfpabst said:
Again I do appreciate the response, but rest assured, I spent nearly two days searching through forums for answers, and none seemed to specifically answer my problem... although I'm sure I missed some. The searching did provide me with alternatives, when combined, appeared to deal with the problem...
Click to expand...
Click to collapse
So you're up and running again?
Sent from my ADR6425LVW using Tapatalk
Thanks
Boots fine into the 2.01.605 system. The only thing I am trying to deal with is that if I go into fastboot, it still runs through a script and I get the "no image"... however everything works. I did a fastboot recovery of the boot img file that was with the CleanFlash Stock-Rooted Rom, but it doesn't seem to make any difference.
Tried copying the same PH98IMG file to the SD and when asked if I want to update, I did that too... but still get the "no image" when I reboot into FASTBOOT. I am going to rest now... and allow the phone to be a phone for a few days, then retackle the issue.
But, thank you so much for your
If you have the PH98IMG.zip on your sd card when you are in hboot, then you will have to make a choice to do the update or not. That is the only option you will ever have, thus the reason for deleting it as part of the first things that you do on an install.
If you do not have the PH98IMG.zip on your sd card and boot into hboot, it will run that script that you see and say "no image" That is just the way it is. It is checking for the .zip file. Its nothing to worry about.
Ran Automatic Unlock V4.2 , phone was previously unlocked but a ATT Motorola update removed Root and Unlock, was hoping for the official ICS but since we were left high n dry read and read and chose CM-10-20121023-UNOFFICIAL-olympus.zip and gapps-jb-20121011-signed.zip for my installation files.
Performed back-up, formatted data/cache, factory reset and flashed files under advanced since was getting the Status 7 error and it was found in forums as the work around when this occurred.
Phone will only get to splash screen with Motorola Icon and the unlocked message, I can enter recovery, tried another factory reset, still hanging, phone seems warmer than usual in this hanging event.
Will try another round of steps mentioned above, but since cannot post in developer thread yet, posted here.
Any suggestions, will mark resolved if this passes, but thought some might be more verse in this process playing with dailies and whatnot...
thanks all for any useful suggestions...
Found my own solution below...:laugh:
Went into mounts and chose to format system-data-cache, reinstalled the 2 files, still hangs on boot...
Thought this would be painless, work will be rough up all night resolving this, any suggestions, load a different rom?
Tried to use the back-up, it failed....
Perhaps I need to keep updating and reach 10 posts so can actually ask in dev thread, only phone and have work in morning, should have done this on the weekend, will have to take a day off if can't get this bad boy back up, or take a hit and buy phone on craigslist or facebook, lol,, fun fun..
I ran a custom Rom on my other Atrix no issues, but onboard speaker was doa and had to use Bluetooth all the time and was hassle sleeping, replacement phone had 2.3.6 so was just being patient for the ICS so hadn't played with this one until tonight...
Solution
placed v5 of CW recovery into auto unlock folder, renaming the v4 to old and just changing the name of the v5 to the name of the v4 so I didn't have to edit the bat file, re-ran script, chose the option 6 I think it was for flashing recovery, it flashed the one I substituted into the folder, loaded the zip files fron SD card again and then joy, phone booted, loading apps, back to testing and hoping to love this JellyBean on my Atrix...
Hello, all. First, I'd like to say thank you for taking the time to read this and potentially try and help me out. Any assistance with this matter would be greatly appreciated!
I added the (Non-standard) to the title, as I've been flashing and modding this phone for over two years, and I've never experienced this issue. I'm not the type to ask for assistance, as my research skills are well above par, but after digging through literally countless forums and topics, I have yet to find anything quite like my situation...
ISSUE: Performed recent flash attempt to epinter's CM10.1. Now loads to Moto splash, sits there the usual few seconds, but when it comes time to load the rom, it reboots and starts the process again... (I swear I think I see it trying to load the rom splash for like a micro second, but then it could just be the delirium of long hours researching and fighting this problem.) Now, you might be thinking, "Eh, pretty common...", right? Yeah, me too, until I couldn't fix it like I've done a million times before... I can boot into recovery. I have performed ALL standard actions regarding flashing a new rom, yet the problem persists. The problem persists now no matter what rom I attempt to flash. Now you might be thinking, "Just flash your nandroid recovery...", but I wish, oh how I wish I could... I am currently using CWM-based Recovery 5.0.2.7, although I've tried more than a few different recoveries since this issue, all provide the same results... Which is nothing. I'm at the end of my rope here.
I've even tried flashing TWRP (two different versions) so I could at least get some charge to the battery so I could continue this debacle, but it hangs at the TeamWin splash screen...
Fastboot loads fine. Wipes performed to system, caches, partitions, etc, to no avail... Battery pull, already tried...
I've covered all the basic fixes, but my issue seems to be bigger than my knowledge base (at the moment).
Okay, here's the exact details of what led up to this...
My Atrix WAS unlocked, rooted, and using RR's CWM for recovery at the time. I had flashed everything coming and going as the scene grew, but eventually went back to CM7.2 and had been running it for ages. Well, I decided to try something new, and settled on trying BeanStalk. Flashed Aroma Prep, no problem. Flashed ROM and Gapps, no problem. Booted up fine. Decent start on the rom, but a little too buggy yet for me. So on this note I wiped and restored my CM7 nandroid backup, no problem. All was well, until I came across epinter's CM10.1 and thought, "Eh, why not?" (...and now look at the mess I'm in!) Performed a new nandroid backup of my CM7, and began the process that ended me... Everything went along just fine. Performed all my wipes, flashed my zips, rebooted, and BAM... boot loop! Little did I know what kind of headache I was in for, until I couldn't restore my backup. Now, I'm just praying I find a solution before my battery drains out completely...
SIDE NOTE: While attempting to restore fails and just resets recovery back to the main screen, there are no visible errors reported. Attempting to flash ANY of my other roms results in the same behavior. Flashes "appear" to go smoothly, but the end result is the same... I did notice upon attempting to flash BeanStalk again that there is an error reported in the aroma installer. It performs all wipes correctly, but when it comes time to actually install, it reports a broken symlink error, or something to that effect... (I would reproduce the install error message, but at the moment I'm trying to hang onto as much battery life as possible. My apologies for the inaccuracy of any statement.)
PLEASE, LADIES AND GENTLEMEN, I BEG OF YOU... If anybody has been unfortunate enough to have found themselves in my shoes, then hopefully you were lucky enough to get it figured out by now and would be willing to pass along the info. Although not my primary phone anymore, it still gets more than it's share of use. I'd hate to see it go out this way...
Any help to guide me in the right direction would be most appreciated! Thank you all in advance!