While I was in cwm doing stuff (in a hurry), i choose something by accident. what I thought was partitioning the internal sd storage, turns out to be something else. I am able to get into android and both my sd partitions were unchanged.
Each time i boot I get this:
pwrReason: SW_AP_RESET
OS willl boot in 5 seconds
press a key to stop count down
available modes are:
1 RSD
2 Fastboot
3 NvFlash
4 BP HW bypass rsd
5 BP HW bypass QD DLOAD
6 BP HW Diag & boot AP
7 BP HW Bypass BP only
8 BP HW Bypass Bypass rsd
9 android recovery
10 boot android (no bp)
11 device UID
12 console=ttyS0,115200n8
13 early usb enumeration
14 BP tool
-----------------------------
volume up to select, volume down for next choice
current choice is mode:
----------------------------------
I am not able to select android recovery, well I can but it just reloads that screen again but can't get in cwm. How do I rid of this and get CWM back? I am fairly new to android. Please help.
Boot into the fastboot mode and reflash the recovery. that should solve the issue.
Okay I did that but not fixed entirely. I can now actually select recovery and get into it but that initial screen will still come up each boot.
If I did the vol- & power combo or not, that screen will appear. Doesn't seem to have broken anything but rather than doing the vol - & power combo then scrolling through each option, all the options are listed on screen.
Is there any way to revert back to the old way? I guess its just a comfort thing. I am fairly new to android and have not seen any examples of recovery looking like this.
That is not recovery. That is what it looks like under the M when you boot up. Volume down toggles the selection and power up selects it. If you do nothing then it should boot like normal. Mine has been that way for a while. All you are really missing is the M logo.
I think you have to SBF back to bone stock to fix it.
Sent from my MoPho. All typos are the phones fault.
I want this screen can you remember what you selected
Sent from my MB855 using XDA
jokersax11 said:
I want this screen can you remember what you selected
Sent from my MB855 using XDA
Click to expand...
Click to collapse
To do that (well at least on mine), you must disable the "Go back" button while on the advanced menu. Pressing the go back button, it will say data size as the header with 0M to 4096M as the selection. pressing it will format something. It screwed up my PDS partition but luckily I had a nandroid backup. I had to reflash CWM too. The SBF doesn't restore the partition.
it happened to me as well after accidentally doing something in recovery that I can't for the life of me remember. Dont know if it may or may not be caused by installing CWM from the CWM app or just because i accidentally partitioned my SD card. That being said, i kinda like it like this. Instead of that bland M logo you actually have something useful and informative.
Here is the thread on how to change that boot logo instead of having the red M. I also was getting this foreign boot screen, so you don't have to SBF back to stock to get that screen back. Just flash one of these, I personally love the Punisher one...it really looks awesome on the phone! http://forum.xda-developers.com/showthread.php?t=1248221
hoslayer13 said:
To do that (well at least on mine), you must disable the "Go back" button while on the advanced menu. Pressing the go back button, it will say data size as the header with 0M to 4096M as the selection. pressing it will format something. It screwed up my PDS partition but luckily I had a nandroid backup. I had to reflash CWM too. The SBF doesn't restore the partition.
Click to expand...
Click to collapse
This happened to me too the other day It was really late, was doing a clean install of the latest cm9, dozed off a few times but went through the motions anyway and ened up doing this by accident. Your description fits it perfectly, sadly I do not have an nandroid so I'm SOL, I can still flash roms and everything, but my profile and prl will not update which is kind of irritating.
I just eventually unrooted and went back to bone stock and it didn't help any, lol now I'm rerooted and unlocked, back on CM9. Anyone know of a fix for the partition?
benman715 said:
Anyone know of a fix for the partition?
Click to expand...
Click to collapse
Try pming Plancy, he had this issue on a different thread but I'm not sure if he resolved it.
hoslayer13 said:
To do that (well at least on mine), you must disable the "Go back" button while on the advanced menu. Pressing the go back button, it will say data size as the header with 0M to 4096M as the selection. pressing it will format something. It screwed up my PDS partition but luckily I had a nandroid backup. I had to reflash CWM too. The SBF doesn't restore the partition.
Click to expand...
Click to collapse
This! What you described here sounds exactly like what happened to me. By accident I went into something, I was given options 0m - 4096m with a bunch others in between. I choose 0m, because there was no way to go back (at which point I shouldve just pulled the batt), for me it was formatting or partitioning the internal SD, but it didn't wipe the data.
Being as un-knowledged as I am, since the data on my internal sd did not change, I can not tell if something is wrong or not. So this does something bad to the partition?
Doing that affects your boot.img (no boot logo) and formats your pds, which has device info necessary for updating your PRL and data profile. You should still have data and the contents of your internal SD. The only fix I know of is advance restoring your boot.img and pds.img with the same version of cwm. Plancy tried a universal fix of the pds from the atrix forum but it didn't work
I went into the partition menu and didn't have the option to go back. I partitioned pds i believe at 4096. Then I had the disappearance of the m logo.
I went on to install ice and all went well. Just missing the m at boot.
Sent from my MoPho. All typos are the phones fault.
Related
I have a Viewsonic GTablet. I have used it very little and know nothing about rooting or ROM's or anything. I picked it up one day and turned it on and it's in a loop while booting...it goes from "viewsonic" to "Gtablet" to "TapNTap" then sticks there for several minutes then turns off. I have tried holding down the power and Vol. + and It comes in the upper left hand corner saying "Detect Recovery Key Pressed" and then "Booting recovery Kernal Image". Then the "unpacking box" appears...nothing happens but when I press the "HOME" button it says "Formatting MISC" and then "Rebooting" then the loop again. Called Tech support they laughed and said send it in...not sure about all that but would rather figure something out before doing that...thanks in advance...remember I am a NOVICE...so simple instructions please LOL
You need a data wipe/factory reset. Can be done from stock recovery. I recommend method I from the following thread...
http://forum.xda-developers.com/showthread.php?t=1030915
K J Rad said:
You need a data wipe/factory reset. Can be done from stock recovery. I recommend method I from the following thread...
http://forum.xda-developers.com/showthread.php?t=1030915
Click to expand...
Click to collapse
Did that it came up with the first 2 "Detect Recovery Key Pressed" and "Booting Recovery Kernal Image" then to the "upacking box" for about 5 seconds then to the loop again. Still lost...thanks for trying to help any more suggestions?
http://forum.xda-developers.com/showthread.php?t=1008245
Look for the links about installing clockworkmod. Once installed you'll need to try the data wipe and possibly repartition your internal storage. That will cause any data stored there to be lost.
tried all of them and the tablet will not recognize the SD card or being connected to the computer
A little more than tried all of them would be helpful...
Did you get CWM installed?
Were you able to wipe data?
Did you partition?
What was the result of each of those actions?
Is the tablet still looping?
Can you still get into recovery?
If not, what exactly is it doing when you turn it on?
No..I put that on the SD card and put the SD card in the tablet. Booted up and it goes through the same cycle. It will not even boot from the SD card. It never brings up a menu to cycle through with the Vol + or -....if I connect it through the USB it never recognizes it because it never comes out of the boot loop.
Thanks for all your help...I am really a novice with this thing
Well... It doesn't boot from the SD Card. Recovery looks at the SD Card to see if there is anything for it to do. Back to basics...
Install ClockworkMod: http://forum.xda-developers.com/showthread.php?t=865245
The first part of that post describes how to do it. Use the MicroSD card version which you will find at the bottom of the first post. You'll need to download it, extract it and put the recovery folder and update.zip at the root of your MicroSD card using your computer. Then put the MicroSD card in your tablet. Turn the tablet on while holding down the Volume Up key. You should boot into recovery and see the little box, arrow and progress bar. When it finishes you want to reboot it while holding down the Volume Up key again. That will get you into ClockworkMod (CWM).
From CWM main menu you can wipe data. Try that and see if it helps. If not then reboot while holding the Volume Up and go into CWM again. Select "Advanced" menu and you'll find the partitioning command. Select it and answer the two questions with 2048 and 0. This will erase everything stored on your tablet in the user storage space but should fix the problem.
Tried it
Tried it and this time it worked like......clockwork LOL...thanks so much...any more advice to have an awesome butt kicking machine?
Glad to hear it. Hang out around here for a bit and read up on the custom ROMs and stuff. You can turn these tablets into some pretty kick butt machines without too much effort. Just take your time and make sure you understand the process before you get started.
This happened to me on the third day after I've got the ATRIX - so you could say I was still a bit of a newb on Moto Android stuff at that point.
I was using RomRacer's CWM recovery. When I went to school, I decided I'd wipe cache & dalvik & fix permissions until I put on the shoes. When I got out of the flat, it was all done. I could barely see anything on the screen, but I thought what the hell, I know how CWM looks like, I can navigate through it without too many problems.
I must have selected a line wrong, because I ended up formatting the external SD card. Well, I pressed on it, I selected an option (I didn't even realise what I was doing, ROFL), then... when I saw "formatting SD card", I was like "God, f*** me now". Battery pull, battery pull, BATTERY PULL.
After that, when I was booting the phone, instead of the M-logo with the DUAL CORE TECHNOLOGY text, I got #1 (see the first picture). After a few seconds, it would show #2 (see the second picture), and another few seconds after that, the boot animation of the ROM would appear.
As you can see, it shows "OS will boot in 5 seconds". In those 5 seconds, you can use the volume down key to navigate through those options (which are the options you get to choose when you normally boot the phone, say, to go to Recovery - only displayed in another way, since you have the M-logo boot screen, which I don't have, lol).
Option number 10 (Boot Android (No BP)) boots the OS, but without the baseband. Wi-Fi, Bluetooth work fine (didn't test GPS), but 2G/3G are offline; also, if I'd go in Settings -> About, under "Baseband version", it would show "Unknown" or "Unavailable".
Option number 15 (BP Tools), is enabled by default after 5 seconds, if you haven't selected another option. That turns on the BP (which I believe is the baseband), and the ROM boots after that.
If I wipe the partitions, it will show "No OS detected. RSD mode will activate in 5 seconds", or something like that.
Even though it says "Current choice is mode: RSD", after that, it is powering on the BP, and booting Linux... It isn't actually going into RSD mode. Unless I press a volume key, it doesn't change, and the phone boots normally.
-----
Notice the PwrReason: SW_AP_RESET text on the top side. It shows SW_AP_RESET because I used the Reboot function that my current ROM provides (Neutrino ROM). If I turn off the device and turn it back on (manual reboot, so-to-say, lol), PwrReason would be PWR_KEY_PRESS. If I turn off the phone and plug in the charger, it would show PwrReason: CHARGER.
If the OS freezes and the phone reboots, PwrReason is AP_KERNEL_PANIC.
-----
What do you think of this? What might have gone wrong?!
Anyways, this thing is awesome. Now it looks more like the way regular computers boot up (BIOS lines, etc.), which is more interesting to look at, instead of a shiny image which doesn't inform you of anything that your phone is doing RIGHT NOW.
-----
Some things I haven't stated. After I did that stupid thing in CWM, it was showing "No OS detected". I had to flash the ROM for it to properly boot up afterwards. Also, after that, the touchscreen was malfunctioning (the capacitive keys didn't work etc.), so I had to flash the PDS partition again, as well. But that's pretty much all I had to do.
I followed your link from the CM7 thread. It's just like turl said, you need a new logo.bin (boot logo). Here's a link to a thread in the Themes section that has it.
ghost_og said:
I followed your link from the CM7 thread. It's just like turl said, you need a new logo.bin (boot logo). Here's a link to a thread in the Themes section that has it.
Click to expand...
Click to collapse
I figured that was missing (a bit late, actually)... I just can't beleive how a simply "format external SD card" option from CWM can do such a thing... Format the PDS, boot animation and the ROM, without doing the purposed thing : FORMAT THE DANG SD. In a way, I'm happy it did that and not the thing it was supposed to do - I didn't had a backup of my SD, lol.
Well, thank you. Even though I kind of like the way my phone boots up now... I'd kind of like an image, too. It would be awesome to place some lines of that text in some corner of the animation, like PwrReason, for example... useful for when you wanna know why the phone was off when you thought it was on Anyway...
That is just smothered in awesome sauce. Is that an official how-to guide???
JdgM3NT4L said:
That is just smothered in awesome sauce. Is that an official how-to guide???
Click to expand...
Click to collapse
What are you talking about? That how to on making your own boot image?
lol, yep.
JdgM3NT4L said:
lol, yep.
Click to expand...
Click to collapse
Well, I don't know what you mean by "official", but that's a guide alright.
I'm just going to get straight to the problem here: my Atrix won't boot because something went wrong with a ROM I was trying to install. I was using the package from here Project kitchen sink, and selected aokp. I have Clockwork Recovery 5.8.1.8, so it boots into recovery.
The problem is that my volume rocker is broken, I *think* because of pds, so I cannot navigate the menu. I have tried using RSDLite and Fastboot, hoping that I could work through the recovery boot menu, but it's useless. And since my volume keys refuse to work, I can't set the phone to boot into RSD mode. I'm stuck in an endless loop of not-able-to-do-jack-****, and I don't think I'll be able to send it in to Moto for a replacement.
I don't know if the failure is due to a hardware issue (my Atrix was shipped to me from my family, since I live in Puerto Rico), the CM7 ROM I had before, or a recent crash (the battery was also giving me problems, and lately crashed the phone several times, not turning on unless I pulled it.)
Sparr159 said:
I'm just going to get straight to the problem here: my Atrix won't boot because something went wrong with a ROM I was trying to install. I was using the package from here Project kitchen sink, and selected aokp. I have Clockwork Recovery 5.8.1.8, so it boots into recovery.
The problem is that my volume rocker is broken, I *think* because of pds, so I cannot navigate the menu. I have tried using RSDLite and Fastboot, hoping that I could work through the recovery boot menu, but it's useless. And since my volume keys refuse to work, I can't set the phone to boot into RSD mode. I'm stuck in an endless loop of not-able-to-do-jack-****, and I don't think I'll be able to send it in to Moto for a replacement.
I don't know if the failure is due to a hardware issue (my Atrix was shipped to me from my family, since I live in Puerto Rico), the CM7 ROM I had before, or a recent crash (the battery was also giving me problems, and lately crashed the phone several times, not turning on unless I pulled it.)
Click to expand...
Click to collapse
PDS does not affect volume buttons.
And what happens when you boot? Boot loop is not very specific...
I read a post on here that said it did...
And what happens is that it boots once, stays on the Moto logo, then blacks out, boots again and goes into recovery. Since I have no way to do anything, I press the power button and it goes again.
What I need is either
1) A way to work with RSD through the recovery, or
2) A way to work with ADB through recovery, or
3) Someone to just tell it to me straight: I'm f*cked and I need to send it in to Moto (Which I doubt they would take it.)
Sparr159 said:
I read a post on here that said it did...
And what happens is that it boots once, stays on the Moto logo, then blacks out, boots again and goes into recovery. Since I have no way to do anything, I press the power button and it goes again.
What I need is either
1) A way to work with RSD through the recovery, or
2) A way to work with ADB through recovery, or
3) Someone to just tell it to me straight: I'm f*cked and I need to send it in to Moto (Which I doubt they would take it.)
Click to expand...
Click to collapse
I would tell you to flash touch recovery however I don't think you can and how it would help you recover from this situation.
Sent from my MB860 running Jokersax's CM9
The weird thing is that I had flashed touch recovery before I started with kitchen sink, and it fixed the touch problems I was having there, but now the touch doesn't work. I downloaded it from the clockwork website, because I don't want to pay for something that is available for free, and I flashed it in fastboot.
Now I have Clockwork Recovery 1.8, which should be touch, no?
Sparr159 said:
The weird thing is that I had flashed touch recovery before I started with kitchen sink, and it fixed the touch problems I was having there, but now the touch doesn't work. I downloaded it from the clockwork website, because I don't want to pay for something that is available for free, and I flashed it in fastboot.
Now I have Clockwork Recovery 1.8, which should be touch, no?
Click to expand...
Click to collapse
You mean 5.8.1.8? If so then yes. And if touch is not working in touch recovery then it does sorta confirm you need the PDS fix...
We are finally getting somewhere: yes, it is 5.8.1.8, touch doesn't work. I know I need the PDS fix, and I applied it. Twice. I patched in fastboot before I started with kitchen sink, and I thought it had worked, since the Aroma installer was touch-enabled after I patched. But now the recovery menu is not working. I tried pressing the search key, like with the Aroma installer, but I knew it wouldn't have any effect.
Sparr159 said:
We are finally getting somewhere: yes, it is 5.8.1.8, touch doesn't work. I know I need the PDS fix, and I applied it. Twice. I patched in fastboot before I started with kitchen sink, and I thought it had worked, since the Aroma installer was touch-enabled after I patched. But now the recovery menu is not working. I tried pressing the search key, like with the Aroma installer, but I knew it wouldn't have any effect.
Click to expand...
Click to collapse
Can you point me to the thread where it says volumer rocker is linked to pds because i searched and cant find it.
How are you booting...i mean with what key combination? Im assuming your booting normally(only power button) and end up going into recovery. Try booting with power button and volume down.
Sorry I'm not quoting anybody, first off.
Second, I can't find the link. I spent around an hour searching and found it through duckduckgo, but now I can't remember the search term I used. If I find it, I'll post it.
And yes, I'm booting only with power button, because the volume down key isn't working. That is where the pds problem comes in: I can't use the volume down or up key because the keys don't work.
My friend told me that I could use adb to manually boot it into fastboot mode. That works fine, but I don't know how to flash anything other than the recovery/pds partitions. I know fastboot has a "flashall" command, but I don't know how to use that or if it is even going to help. **Essentially** I can boot into fastboot mode, but I want to know if it is even possible to just flash a rom through that. Messy, of course, but if I can just get even a basic ROM working, I can go on from there.
I think you have 2 options:
1. if you can get to fastboot you can reflash everything using uncle cemka's method: http://forum.xda-developers.com/showthread.php?t=1501532
you basically take an .sbf unpack it and flash each part separately.
2. buy a atrix audio jack/camera flex cable from ebay and install it yourself, be especially careful when installing because the very small flex/ribbon that goes to your volume buttons stress fractures very easily if bent very much when installing, hence your volume buttons stop working.
I'm using cemka's method now. I'm waiting for the stock ROM to download, the one from his post. When I finish the whole process, I'll let you guys know how it worked out.
UPDATE: Thank you to whoever referred me to uncle cemka's method, I was able to use it to flash stock ROM. I have functionality back, can boot, and won't waste around $90 on a paperweight.
However, the first problem is still there: The volume keys still don't work. I still need to fix those before everything is %100 percent, so this issue is still open... Sorry guys
Hi,
Today I helped a friend flash a custom rom on a galaxy gio and I opened cmw on my phone to help him go to the right menu's in cmw.
I think I changed the ext4 partition to 0mb (don't realy know how :s) and now when I boot android Instead of the bootscreen with the red m I get some white text with some different options (like boot in adb (about 10 options)) it also tells me I can move change option with volume down and accept with volume up, but these don't do anything :s.
After I wait for a while android just starts booting like normal and everything seems fine, but when android has booted it seems like the touchscreen move up for like a centimeter (if I want to press a button I need to touch the screen under the button) and my soft keys don't work anymore (but I think this is because of the moved touchscreen)
What did I do and how can I make it normal again? I'm running the latest GB Mrom.
Edit:this is the screen I get when there normally is a red circle with the white M in:
Uploaded with ImageShack.us
Thnx if anyone can help me!
I've been trying somethings and if I don't have my usb cable plugged in I can choose some options on the menu, it seems now that I somehow removed my clockwordmod recovery and went back to old recovery? Is this even possible?
Should I just reflash cmw with fastboot again?
Plz help me
I would hold of on flashing another recovery until someone more knowledgeable than I comes along. There might be a chance where you can do permanent damage. Seems like it could have simply deleted their boot logo, and now instead of those options being normally hidden, are being shown. (like when you boot while holding volume down). What happens if you try booting with volume button held down?
Edit: If all else work as it should, just leave it. Makes it look like verbose mode. Forget Motorola and their stupid 'm'. =P
Sent from my MB860 using xda app-developers app
thesummoner101 said:
I would hold of on flashing another recovery until someone more knowledgeable than I comes along. There might be a chance where you can do permanent damage. Seems like it could have simply deleted their boot logo, and now instead of those options being normally hidden, are being shown. (like when you boot while holding volume down). What happens if you try booting with volume button held down?
Edit: If all else work as it should, just leave it. Makes it look like verbose mode. Forget Motorola and their stupid 'm'. =P
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
If I hold volume down + power while booting I get the same thing, and everything works normaly, BUT my touchscreen is messed up, the every touch gets detected to high (if I want to hit app drawer I need to push between the home and back soft button) and the soft buttons don't work.
Oh right, you did mention that, my bad. Well, I'd say hold off for someone that might know what happened as I've never read about or experienced something like this. Maybe try posting in the main XDA Q&A section not specific to Atrix as someone might have had a similar issue with another device (maybe even a Moro) Sorry can't be of much help. Good luck.
Sent from my MB860 using xda app-developers app
touchscreen problems are usually related to the pds partition. Did you by any chance make a backup before these problems started?
I don't know if the bootscreen is related to the PDS partition but it might be that this partition is corrupted.
jorno88 said:
touchscreen problems are usually related to the pds partition. Did you by any chance make a backup before these problems started?
I don't know if the bootscreen is related to the PDS partition but it might be that this partition is corrupted.
Click to expand...
Click to collapse
but could that also explain the weird boot message with the options? (or is it also called animantion, because the Mrom annimations works normal (the blue android guy))
I had mistakenly done something that resulted in your exact problems once. What I did to fix. First you'll need to fastboot a recovery again. Next you'll have to do the pds partition fix. Then lastly flash the proper boot logo back to get the m screen. The first step is dependent on you being able to get into fastboot so hopefully you can.
pre4speed said:
I had mistakenly done something that resulted in your exact problems once. What I did to fix. First you'll need to fastboot a recovery again. Next you'll have to do the pds partition fix. Then lastly flash the proper boot logo back to get the m screen. The first step is dependent on you being able to get into fastboot so hopefully you can.
Click to expand...
Click to collapse
thnx for the reply!
you mean the Fix in this thread?
http://forum.xda-developers.com/showthread.php?t=1131649
And I'm guessing i'll need the one for gingerbread?
M_K_ said:
thnx for the reply!
you mean the Fix in this thread?
http://forum.xda-developers.com/showthread.php?t=1131649
And I'm guessing i'll need the one for gingerbread?
Click to expand...
Click to collapse
Yes that is the right file and yes for gb.
Ok, I just reflashed the recovery with fastboot and then I flashed the PDS partition fix and the touchscreen works perfectly again. Only the red M is still gone.
Any Idea how to get it back?
And Thank You so much!
Now I can use my phone again
M_K_ said:
Ok, I just reflashed the recovery with fastboot and then I flashed the PDS partition fix and the touchscreen works perfectly again. Only the red M is still gone.
Any Idea how to get it back?
And Thank You so much!
Now I can use my phone again
Click to expand...
Click to collapse
Somewhere in the forum is the boot logo. I believe its in the apps section. Search for stock boot logo. Glad I was able to help.
Actually here you go. http://forum.xda-developers.com/showthread.php?t=1423763
After finishing a clean install of JB and restoring my apps, all was working perfectly on my Maxx. I have used TiBu Pro for a couple years, but I've never used its encryption feature. Now that I'm on JB, I thought it might be worth a try, so I enabled it, then rebooted into recovery, then ran a fresh nandroid backup. It completed correctly, but when it rebooted afterward I got an error message that the encryption failed and I needed to do another factory reset to be able to use my phone again.
While that's certainly a crap deal, I wasn't too upset since I'd (literally) just finished a new nandroid, so I figured I'd do the reset, restore the nandroid, then disable encryption again and be on my way. No dice.
When I hit the button to start the reset, it just reboots back to the same error every time. If I boot into the on-board recovery panel (the one with the white letters) and try to go into recovery mode from there, it only boots into the dead Android robot with the "!".
I looked at TiBu's website and tried contacting TiBu, but have found no useful information yet. Has anyone else experienced this? Got any ideas on how to recovery this thing or break out of the cycle I'm stuck in?
Thanks!
***UPDATE***
Here are some more details to see if anyone else can help me work through this. I can only get to two possible reboot states at the moment. The first (when attempting a normal startup) boots through the initial boot image, then the first part of the boot animation. I see the red eye for a few seconds, then I get:
Encryption Unsuccessful
Encryption was interrupted and can't complete. As a result, the data on your phone is no longer accessible.
To resume using your phone, you need to perform a factory reset. When you set up your phone after the reset, you'll have an opportunity to restore any data that was backed up to your Google Account.
Click to expand...
Click to collapse
Then there's a button that says "Reset phone" at the bottom (this is what makes me think the TiBu encryption is the culprit). If I hit that button, it just reboots to the same error every time.
The second reboot state is if I power down the phone completely, then boot into recovery by holding the Up/Down volume buttons and Power button for about 3 seconds. I get a black background with white text that says:
Boot Mode Selection Menu (0A.77)
Vol Up Selects, Vol down Scrolls
Available Boot Modes:
Normal Powerup
Recovery
AP Fastboot
BP SBF Flash
BP Only
BP HW Diag & Root AP
BP Tools
Click to expand...
Click to collapse
If I try "Normal Powerup" I circle back to the first reboot state. If I try "Recovery" then it goes to the picture of the Android robot keeled over with a red "!" in his chest and I have to manually reboot it again.
I'm thinking that I might need to go to the "BP SBF Flash" mode and try to SBF back to the .211 file that's still on my sdcard, but it's just a guess (and, admittedly, the only other option I can think of that's even available at this point).
Anyone have any thoughts?
***UPDATE #2***
By pressing both the volume up/down buttons at the dead Android robot, I've now accessed the recovery menu I'm used to seeing (when doing nandroid backups) that lets me perform the factory reset. Unfortunately, doing the factory reset doesn't change anything, and I still boot up to the encryption unsuccessful message.
Not Titanium's fault
This is a side effect of Android's encryption, not Titanium Backup's; Titanium's encryption should only be visible when restoring backups from Titanium itself.
Workaround guide thread here: http://forum.xda-developers.com/showthread.php?t=1447303
Android's page on phone encryption: http://support.google.com/android/bin/answer.py?hl=en&answer=1663755