Database Info

Desire s stuck after 2.3.5 update

i tried to update via phone (after the notification), but after green bar was full, my phone rebooted and stuck in white screen with htc logo... if i try to enter in recovery i see this
h*tp://i39.tinypic.com/xdxnc5.jpg
it seems to be s-off (i bought it used) ...what have i to do for make it work again??
tnx.. and sorry for my bad english

same problem here, help is needed!

A golden rule: never update OTA on a modified device (custom ROM even modified Stock one, custom Recovery, Revolutionary hboot!, etc.)
How to fix:
do not pull battery!
flash a custom recovery (e.g. 4EXT) with the fastboot command (search for a how-to)
reboot to recovery, wipe all partitions and install custom ROM

Ok, to late with the battery, have already pulled that one out!
I also have S-Off on my phone, really dont understand the how to fix a recovery??
And is it really neccessary to flash a new ROM for this?
An official release that screwes the phones up?

I think the general issue is that an 'Official' OTA upgrade should not screw up your phone - enough testing by HTC should make sure of that.
Hoever, if you have modified your phone (e.g. by rooting it, installing custom recovery etc) then you can not expect to blame HTC when their upgrade doesn't work as expected. They can't be held responsible for problems caused by modifications you make to the phone.

But all I have done is S-Off, I have not installed another ROM or anything else?
So the update should work I really think!
Can I install a custom recovery without have to be able to start the phone?

Akerhage said:
But all I have done is S-Off, I have not installed another ROM or anything else?
So the update should work I really think!
Can I install a custom recovery without have to be able to start the phone?
Click to expand...
Click to collapse
The OTA flashes a new hboot also.
If you S-OFFed with Revolutionary your hboot has to be version 6.98.000x. This hboot has a protection and cannot be overwritten. This is the point where the update process is interrupted. The result is a bootloop, because the new system is incomplete.
If you can boot to bootloader (hboot) you should be able to flash a custom recovery with the fastboot command (in the 4EXT Recovery thread there is an attachement - a zip file that contains recovery.img). Extract the archive and flash it with this command from cmd (there is a guide how to make fastboot working in my signature):
Code:
fastboot flash recovery {path to file on your PC}/recovery.img
If this works reboot to recovery, wipe all partitions and flash a custom ROM. Then your phone should be working again.
Then if you want the OTA flash a 0.98.2000 hboot, then use the 1.47.401.4 RUU (if you are using European unbranded) or the corresponding for your brand/region to return back to complete Stock and S-ON. Then you will be prompted to update and you will have the latest OTA on your device

Okay, I have now fixed the 4EXT Recovery and it is working!
Do I have to put a new ROM on the SD-card or is there another way to install a ROM (from cmd with the ROM on the computer etc?)
I dont have an adapter to the SD-card, but maybe I can put the ROM on the sdcard with a command in cmd aswell?
What ROM do you recommend to use? (sense, no sense doesnt matter)
Edit: I did a backup as well, thinking that I should do that...

Can you link to zip file you used for recovery i have exactly same issue and same software versions as you have.

@ Mooler. First of follow the guide that was posted here regarding the adb-drivers.
After that download this: http://forum.xda-developers.com/attachment.php?attachmentid=631186&d=1308596026
Then install that one as described with the cmd-command.
After that just put a custom ROM or a shipped ROM on the SD-card, wipe data/cache and install the ROM you want. That solved the problem for me!
Good Luck and thanks for the help I got here! Xda always delivers

Damn this phone! After hours of fixing with this problem!
I managed great, installed new kernels, radios, ROMs etc. And the first thing I did was to drop it on the floor so the whole damn display cracked!

Thanks for both of you.
I managed to restore the phone quickly after i got the correct recovery file. 30 mins and custom ROM was up and running. Good bye official update.
Akerhage: sad to here, it really was hours of reading and trying before you get it right.

[I9020A] Nexus S, Master Clear?

Hi everyone... I've tried searching and seen references to this kind of thing, but no download links or guides...
So I've got my Nexus S (bootloader unlocked, rooted, stock 2.3.4 until attempting the following, I have no Sim card in this phone), and I tried to flash 2.3.6, and while the update appeared to run just fine, the wifi won't turn on, just gives "error". So I attempted several things, reflashing the update, flashing the 4.04 update (which was the original point), etc, but they all give the following; installation aborted, assert failed, error in xxx.zip, "status 7".
Anyways... I'm a bit at a loss, I've never had this problem, or any problems flashing ROMs on other phones or updates. It seems no update.zip, or any .zip, will install. Back in my captivate days, there was a very handy program called Odin, and it had a master clear functionality that brought you back to the stockest of stock. Ideally... is there a tool like this for the Nexus S? I don't care about whether or not it re-locks the bootloader, I can unlock it again in just a couple minutes... but I need help.
I've read guides about "return to stock" but they all involve flashing a .zip. I need a way to push past that, and get back to 2.3.4, or alternatively, a way to completely reinstall 2.3.6.
I know an Odin exists for the Nexus S, but is there a way to use that to reset to stock?
Thank you so much anyone who can help...

Do you see an android and exclamation mark as you enter recovery? This means you have stock recovery and you cannot flash anything that hasn't been signed by google here. Stock is flashed on each boot on a stock ROM, you need to rename/delete /system/etc/install-recovery.sh to stop this.
If you don't have stock recovery, update to the latest CWM (touch or not is irrelevant) and try again. It's recommended to do a full wipe (data/factory reset, format /system and optionally format /boot) when doing a major ROM change (ie, CM to non-CM, GB to ICS, etc), and failure to do so could leave you with some interesting problems like that wifi issue.
And as always, make sure you backup properly before flashing -anything-.
edit to answer more questions: Odin is available for the Nexus S but near-useless. Fastboot can do just as much, and there are official fastboot images released by google to bring you back to a pure stock state. You'll just need an unlocked bootloader to do that, though you can relock straight afterward with no repercussions.

Harbb said:
Do you see an android and exclamation mark as you enter recovery? This means you have stock recovery and you cannot flash anything that hasn't been signed by google here. Stock is flashed on each boot on a stock ROM, you need to rename/delete /system/etc/install-recovery.sh to stop this.
If you don't have stock recovery, update to the latest CWM (touch or not is irrelevant) and try again. It's recommended to do a full wipe (data/factory reset, format /system and optionally format /boot) when doing a major ROM change (ie, CM to non-CM, GB to ICS, etc), and failure to do so could leave you with some interesting problems like that wifi issue.
Click to expand...
Click to collapse
Heh, yeah I guess I should have wiped previous to running this upgrade. I guess I was hoping data would preserve, because theoretically it should have been just like the Google OTA.
And I have CWM... I'm not sure if it is the latest version, but the phone can't get any data connectivity so I can't update it.
Harbb said:
edit to answer more questions: Odin is available for the Nexus S but near-useless. Fastboot can do just as much, and there are official fastboot images released by google to bring you back to a pure stock state. You'll just need an unlocked bootloader to do that, though you can relock straight afterward with no repercussions.
Click to expand...
Click to collapse
Ok, so fastboot is my solution. I've used that to unlock my bootloader, but little else (on a Mac, because terminal is super easy to use, but I've got PC access too). I've found the Google fastboot images, do you (or anyone reading this) know of a good fastboot image flashing guide?

Dareoth said:
Heh, yeah I guess I should have wiped previous to running this upgrade. I guess I was hoping data would preserve, because theoretically it should have been just like the Google OTA.
Click to expand...
Click to collapse
Some people supposedly had troubles with the ICS update and keeping all data as-is, though i've not experienced it myself, but it is definitely possible and with such a big update, if it's in your power to start fresh it is always the best option. It was more of a general statement, not directed at your situation - something to keep in mind
Dareoth said:
And I have CWM... I'm not sure if it is the latest version, but the phone can't get any data connectivity so I can't update it.
Click to expand...
Click to collapse
You can flash the latest CWM through fastboot from your PC or Mac, you can grab the latest file from here. Name it whatever you like and put it in a known folder (preferrably current folder) and : fastboot flash recovery recovery.img
Dareoth said:
Ok, so fastboot is my solution. I've used that to unlock my bootloader, but little else (on a Mac, because terminal is super easy to use, but I've got PC access too). I've found the Google fastboot images, do you (or anyone reading this) know of a good fastboot image flashing guide?
Click to expand...
Click to collapse
Of course i do

Great, I'm all set now. Thanks so much.
(Also for linking to that ref guide again, I had read it three times, but I didn't get how to use it until I went in going, I just need the fastboot commands, which is all that guide gives.)

Your welcome mate. All you need for that is setting up the android SDK or essentially downloading platform-tools seperately. There are guides all over the place describing how to do this for Windows, Mac and Linux as it is no different from getting oem unlock to work, they're just mostly disguised as rooting guides.
Once you do it the first time it's quite simple, but it can definitely be confusing before that

[Q] upgarde snaufu...

was running viperXL 3.2.5 and wiped and went to cm10.1 now i used goo manager to download xhata (sorry i butchered it) now i can only boot into spash screen and bootloader. i used fastboot to reflash twrp and still only boots to the custom spash... hboot 1.09 s-off..... im kinda lost here. should have syuck with viper, why screw with perfection.

What is xhata? Is it a rom?
I'm not sure we can install roms with Goo Manager on this phone.
If you installed a rom for the quad-core Tegra One X, your phone will not boot and you're lucky you didn't get a brick. You need to do a full wipe and reflash.

first off not a noob. it was the evita rom. i still have bootloader access and can get half way into recovery( spash screen then twrp spash...) then reboot into custom splash. it was the rom... http://forum.xda-developers.com/showthread.php?t=2075783 so if anyone has any ideas please help, just dont start with the usual u screwed up flashing roms i know better. and the odd part is after reflashing the recovery via fastboot i get Twrp spash before going back to the phone main splash and boot looping.... and yes im s-off

No need to be so defensive. If we don't know exactly what you flashed, all we can do is ask. Its not meant as an insult. But its always better to ask the seemingly "obvious" questions first, get them out of the way.
If there is a "usual thing" that gets mentioned, its because the mistake of flashing ROMs for the ENDEAVORU in fact happens so often. Downloading from GooManager is not a great idea either, and often a red flag that someone installed a ROM for the wrong version of the phone.
Did the phone operate properly when you were on CM10.1?
What version of TWRP, and what fastboot command did you use to flash it?

I asked the "usual" questions because:
-You have less than 100 posts. That's often a sign of someone who is new to this.
-You used a rom name I've never heard of, and suggested you weren't sure of the name yourself. That's usually a big red flag for someone who flashed some random rom they found via Google.
-You mentioned using Goo Manager. That's a non-standard method for this phone, and an awful lot of people have bricked their phones trying to flash roms through apps that aren't well-supported. CWM Touch was notorious for this when the One X first came out.
If you don't want people to assume things, you need to state them up front.
On topic: There appears to be a bug in the latest TWRP that causes issues for some people. Try rolling back to an earlier version.

iElvis said:
On topic: There appears to be a bug in the latest TWRP that causes issues for some people. Try rolling back to an earlier version.
Click to expand...
Click to collapse
Yeah, I saw that too, and why I asked the OP what version of TWRP.

i had problems with that rom on version 4.0.1 and 4.1.0 had alot of errors and trouble. i haven't tried 4.2.0 though, i have been having better luck with rom after clearing out recovery cache running "fastboot erase cache" and running only twrp 2.3.3.1.

i flashed the second to last release of twrp (latest gave mount issues), viper was running great, cm 10.1 avatar was running fine just didnt like how plain it was so i used goo manager to download hatkaXL and when the download finished i picked select and flash.. then the usual warning about flashing and it rebooted, hit spash screen where it still is hours later. i then tried manually boot into recovery, it hit the bootloader i selected recovery and it seemed to try and load. next step was back to fast boot and to reflash twrp (fastboot flash recovery recovery.img ) flashed 100% success and still wont boot into recovery just the bootloader, and i wasnt trying to get all defensive, i sent first post using the wifes phone and posted quick, had a guy hooking up my satellite at same time as phone crashed. has anyone tried the new version of cwm for the evita? maybe flashing that may get me back, i have roms and backups on the pc that i can seem to side load but never boot as well.

well after repeated flashing of recovery and (fastboot erase cache) it finally booted to recovery, now to see if my backup will load.

XT925 Updating to KK fail + Bootloader mess

Hey there fellas,
Being a part time/spare time "mod wanna be", I've successfully modded different cell phones every now and then.
Lately I bought, 2nd hand, a XT925 running as it was in the attached screen shot + unlocked BL, rooted and CWMR touch 6.0.4.4.
Since the phone was rebooting itself kinda often, since I've been told that Epinters builds was JBBL based and also based on the phone info 3.0.x Kernel, I thought it was ok to flash a stock ROM and after that, upgrade to KK via OTA.
I've flashed the JB 4.1.2 BR Retail via fastboot and everything went ok. I let it boot, ran through configurations and just made myself sure that basic options were working ok. The OTA pops up, I downloaded it and proceed to install...an error pops up while it was somewhere around 25-30% of the flashing process.
I talked to the previous owner and he said that he went to CM because the cell never was able to install OTAs, there was always errors on the installation process.
With that in mind, I proceed to research some tutorials about alternative methods on how to install KK OTA.
I've found one here and another one on other forum, which was more suited to my needs since I'm at Brazil. Both are suggesting the same method:
Requirements:
1.Stock/unmodified JB4.1.2
2.Stock recovery
3.Unrooted
4.Bootloader unlocked
Since I met all the requirements, I proceeded to give it a try.
The next steps was:
1.Download a JB custom recovery and flash it via fastboot
2.Correct OTA installed on the external SD card
3.Install the OTA via custom recovery
4.install KK custom recovery
5.Root
Steps 1 and 2 were ok but again, while attempting to flash the OTA there was errors. Since Ive tried the whole process several times with different files, doing MD5 checksums, with different custom recoveries, I may divide the errors in 2 separate categories:
Error category 1:
While verifying current system, different .apks has unexpected contents. Status 7 as the final status error.
Since I was battling with this for 36 hours non stop, just before going to have some sleep, I decided to format internal SD since I thought maybe there was some leftovers from previous installations.
Apparently everything went ok and i proceed to flash the another SBF this time (I was trying the JB4.1.2 BR Retail). Since I've heard one of the latest KK kernel was the DE I decided to give it a try. Downloaded it from the official motorola page and flahed it via fastboot. This time I didn't stayed on front of PC because I needed some coffee! When I cam back, everything seemed to be ok since there was a message at the end saying so.
Phone rebooted and JB4.1.2 was installed, basic configurations done and OTA downloaded through the cell phone. Installation failed again! With this OTA fail already in mind, I previously downloaded the DE OTA from a post here and had it downloaded already to the external SD card. Installed JB custom recovery and proceed to flash the OTA...it failed again!
There was almost 40 hours without sleeping so my brain didn't allowed me to keep going.
After 10 hours of rest, I was back to keep fighting....and there comes the next type of errors:
Error category 1 +2 +3+4
1+2+3 because after several attempts on the whole process, the error 1 popped up some times, there was, as well, a new error (error 2) while flashing the OTA via custom recovery (please see the attached screen shot).
Finally, the errors 3+4 (actually the error number 3 is the one I'm concerned the most about). Its sort of a bootloader menu error message and the error number 4 shows up while trying to flash SBF and or Custom recoveries and they are as follow
Bootloader menu error message:
10.98(*) (sha-5b608bc, 2012-11-23 19:48:44)
eMMC Info: Size16GB
Device is UNLOCKED. status code: 3
Fastboot reason: Boot menu selected
USB Connected
downgraded security version
Update gpt_main version failed
Pre flash validation failed for gpt
Fastboot error messages while trying to flash SBFs and or custom recoveries
<bootloader> Variable not supported!
target max-download-size: 30MB
FAILURED (remote failure)
My conclusions/doubts are as follows:
1.Does that internal SD format has something to do with the bootloader menu errors message? I feel it has started to show up after I did it...maybe it's just coincidence though!
2.The .xml editing part still making me feel something suspicious about the Fastboot error messages.
3.Does that Epinters CM11 KK 4.4.4 Kernel 3.0.101-11512-g9511901 has something to do with that scaring Bootloader error message about downgrading?
...or is it just me being a noob?!?
However, If you came this far, congrats! I really truly respect your commitment to help people and your passion for computer/programming/Android related things!
People like this are the real responsible for bringing men out of caves all the way through the days we live in and as far as to reach the moon!
Now if you help me to get out of this and reach my goal of having KK4.4.4 official DE(or any newest other one which works where I live), rooted, unlocked BL, I'll be more than happy to ask for your permission to invite you to some beers!
Cheers!

RMarques said:
Hey there fellas,
Being a part time/spare time "mod wanna be", I've successfully modded different cell phones every now and then.
Lately I bought, 2nd hand, a XT925 running as it was in the attached screen shot + unlocked BL, rooted and CWMR touch 6.0.4.4.
Since the phone was rebooting itself kinda often, since I've been told that Epinters builds was JBBL based and also based on the phone info 3.0.x Kernel, I thought it was ok to flash a stock ROM and after that, upgrade to KK via OTA.
I've flashed the JB 4.1.2 BR Retail via fastboot and everything went ok. I let it boot, ran through configurations and just made myself sure that basic options were working ok. The OTA pops up, I downloaded it and proceed to install...an error pops up while it was somewhere around 25-30% of the flashing process.
I talked to the previous owner and he said that he went to CM because the cell never was able to install OTAs, there was always errors on the installation process.
With that in mind, I proceed to research some tutorials about alternative methods on how to install KK OTA.
I've found one here and another one on other forum, which was more suited to my needs since I'm at Brazil. Both are suggesting the same method:
Requirements:
1.Stock/unmodified JB4.1.2
2.Stock recovery
3.Unrooted
4.Bootloader unlocked
Since I met all the requirements, I proceeded to give it a try.
The next steps was:
1.Download a JB custom recovery and flash it via fastboot
2.Correct OTA installed on the external SD card
3.Install the OTA via custom recovery
4.install KK custom recovery
5.Root
Steps 1 and 2 were ok but again, while attempting to flash the OTA there was errors. Since Ive tried the whole process several times with different files, doing MD5 checksums, with different custom recoveries, I may divide the errors in 2 separate categories:
Error category 1:
While verifying current system, different .apks has unexpected contents. Status 7 as the final status error.
Since I was battling with this for 36 hours non stop, just before going to have some sleep, I decided to format internal SD since I thought maybe there was some leftovers from previous installations.
Apparently everything went ok and i proceed to flash the another SBF this time (I was trying the JB4.1.2 BR Retail). Since I've heard one of the latest KK kernel was the DE I decided to give it a try. Downloaded it from the official motorola page and flahed it via fastboot. This time I didn't stayed on front of PC because I needed some coffee! When I cam back, everything seemed to be ok since there was a message at the end saying so.
Phone rebooted and JB4.1.2 was installed, basic configurations done and OTA downloaded through the cell phone. Installation failed again! With this OTA fail already in mind, I previously downloaded the DE OTA from a post here and had it downloaded already to the external SD card. Installed JB custom recovery and proceed to flash the OTA...it failed again!
There was almost 40 hours without sleeping so my brain didn't allowed me to keep going.
After 10 hours of rest, I was back to keep fighting....and there comes the next type of errors:
Error category 1 +2 +3+4
1+2+3 because after several attempts on the whole process, the error 1 popped up some times, there was, as well, a new error (error 2) while flashing the OTA via custom recovery (please see the attached screen shot).
Finally, the errors 3+4 (actually the error number 3 is the one I'm concerned the most about). Its sort of a bootloader menu error message and the error number 4 shows up while trying to flash SBF and or Custom recoveries and they are as follow
Bootloader menu error message:
10.98(*) (sha-5b608bc, 2012-11-23 19:48:44)
eMMC Info: Size16GB
Device is UNLOCKED. status code: 3
Fastboot reason: Boot menu selected
USB Connected
downgraded security version
Update gpt_main version failed
Pre flash validation failed for gpt
Fastboot error messages while trying to flash SBFs and or custom recoveries
<bootloader> Variable not supported!
target max-download-size: 30MB
FAILURED (remote failure)
My conclusions/doubts are as follows:
1.Does that internal SD format has something to do with the bootloader menu errors message? I feel it has started to show up after I did it...maybe it's just coincidence though!
2.The .xml editing part still making me feel something suspicious about the Fastboot error messages.
3.Does that Epinters CM11 KK 4.4.4 Kernel 3.0.101-11512-g9511901 has something to do with that scaring Bootloader error message about downgrading?
...or is it just me being a noob?!?
However, If you came this far, congrats! I really truly respect your commitment to help people and your passion for computer/programming/Android related things!
People like this are the real responsible for bringing men out of caves all the way through the days we live in and as far as to reach the moon!
Now if you help me to get out of this and reach my goal of having KK4.4.4 official DE(or any newest other one which works where I live), rooted, unlocked BL, I'll be more than happy to ask for your permission to invite you to some beers!
Cheers!
Click to expand...
Click to collapse
thats a lot to process lol
i have a 926 not a 925 and know nothing about the specifics of updating.
however, you have and may have made some universal errors.
- when flashing with rsd a couple partitions can not be flashed equal or downgraded. these are tz/trustzone and gpt/partitioning file. therefore these lines need to be edited out of the xml unless you are upgrading. thats why you have the fastboot error, from trying to downgrade the partition table. any correct flash, updating or removing the partition and tz lines, should make this go away.
- as far as the update files. if they are true update pulls and not modified files made to flash in custom recovery, they need to be flashed in stock recovery, not cwm. without seeing the post the files came from, i cant say which you have, but the poster should have identified which they are.
there isnt much else i can comment on, but hope that helps get you on the right path.

Thanks for stopping by, reading and replying!
I'll try to touch it point by point, saying so:
1. I have flashed several times attempting to succeed on this, all of them I've used Fastboot.
2. I didn't knew, nor read nothing anywhere about the partitions that can not be flashed equal or downgraded anywhere I researched before I decided to proceed.
3. I've got what you said and I pretty much agree with that, in fact, i was pretty sure about that there was some mistake(s) in the .xml.
4. "Fastboot error, from trying to downgrade the partition table. Any correct flash, updating or removing the partition and tz lines, should make this go away." Are you talking about the following error?
"downgraded security version
Update gpt_main version failed
Pre flash validation failed for gpt"
...if so, thank God, it scared me to dead!
- As for the update files, I followed the tutorials and it was clearly stated that they was meant to be flashed using a JBBL custom recovery. http://forum.xda-developers.com/showthread.php?t=2760840&page=60 (Post #599)
Thanks again and from where I'm at atm, any kind of input helps a lot!

RMarques said:
Thanks for stopping by, reading and replying!
I'll try to touch it point by point, saying so:
1. I have flashed several times attempting to succeed on this, all of them I've used Fastboot.
2. I didn't knew, nor read nothing anywhere about the partitions that can not be flashed equal or downgraded anywhere I researched before I decided to proceed.
3. I've got what you said and I pretty much agree with that, in fact, i was pretty sure about that there was some mistake(s) in the .xml.
4. "Fastboot error, from trying to downgrade the partition table. Any correct flash, updating or removing the partition and tz lines, should make this go away." Are you talking about the following error?
"downgraded security version
Update gpt_main version failed
Pre flash validation failed for gpt"
...if so, thank God, it scared me to dead!
- As for the update files, I followed the tutorials and it was clearly stated that they was meant to be flashed using a JBBL custom recovery. http://forum.xda-developers.com/showthread.php?t=2760840&page=60 (Post #599)
Thanks again and from where I'm at atm, any kind of input helps a lot!
Click to expand...
Click to collapse
yes, that error should be fixed by any good flash.
if for some reason its not, get "mfastboot" and flash the most current version you have ever had on the phone and *** flash the partition file first, followed by the rest of the files. mfastboot can write equal partition files. if the partition file flash fails, you dont have the newest one.
hopefully re-flashing without the partition file works, then you wont need to mess with mfastboot.
looks like that is a modified ota file as you stated, sorry but i cant help with whatever the issue is with that part.

Solved!
http://forum.xda-developers.com/showthread.php?p=56598858
Sent from my Razr HD/Unlocked KKBL/TWRP2.8.1.0/Latest CM11 M11 Nightly/ART Runtime

Problem flashing Kernel for 6633

Somewhat new to this, but I successfully rooted my 6633 which has stock 4.4.4 (Which I re-installed the stock firmware fresh). Afterward I Installed TWRP and attempted to create a custom recovery (I could never boot into recovery and tried many times and many ways), and assume I must at least create a custom recovery. Anyway, in attempting to create the recovery I tried to flash the img file. However, I could not find an image for the 6633 and (stupidly) flashed the image for the z3c. But other than freezing the phone the first time I shut it down, everything on the phone works fine. But a recovery was never created. I then found an img for the 6633 and tried to flash it but simply got an error message saying that "Failed remote: image is not a boot image". Apparently either the original mistakenly loaded (z3c) image won't let me flash another over it (unlikely, since it may have never even loaded) or (more likely) the new correct image is bad or corrupted. It is called "bootZ3dualmonxtest01.img" and was downloaded from another site. Searching this site I did find a kernel for the Z3 6653 but there is not any kernel for the 6633.
Again the phone works fine and I can do some file management things in the root, but the whole reason for doing this rooting process is so I can flash a mod to fix the crappy ringtone volume, that I located in another thread on this forum. It's been a journey & I had a lot of fun learning, but I'm not even sure that, in the end, the mod will even fix the ringtone volume (although posters on that thread claim it works). But that's a whole other issue. (lol). Sorry for the wordiness. I read the forums a lot and tried to be thorough. I know there are a lot of really smart people helping newbies like me. Any help is appreciated.

First of all, you can't flash custom kernels on Locked bootloader (I guess you've never unlocked it)
Second, if you wan't just to flash a zip file with sound mod then after rooting and installing TWRP, boot in TWRP and Install the zip. Thats it. You don't need custom kernel or any other recovery. TWRP is fine enough.

G-FACE said:
First of all, you can't flash custom kernels on Locked bootloader (I guess you've never unlocked it)
Second, if you wan't just to flash a zip file with sound mod then after rooting and installing TWRP, boot in TWRP and Install the zip. Thats it. You don't need custom kernel or any other recovery. TWRP is fine enough.
Click to expand...
Click to collapse
Thanks so much for your reply. However, the Bootloader was unlocked the whole time. In fact, the process did seem to correctly flash the wrong kernel (xperia Z3c). The reason I was trying to create a custom recovery is that I am apparently unable to boot to TWRP. I had read in another forum that the Z3 Dual does not come with a stock recovery and that a custom one has to be installed.
In any case, I followed the instructions to boot to TWRP (which gave a couple of methods), and it continues to just either just boot normally, or it I get an error "Damaged SD Card" and I lose some minor functionality. In that case, the phone won't shut down and I have to hold the power button and up volume to kill it. But then if I power it on, everything is normal. This error sequence only occurs when I try to boot into recovery.
Is it possible that when I flashed the wrong kernel (using the Xperia Z3c kernel) that I created this issue? I assumed that the reason for the error was that there was no stock recovery and one could be created by flashing the kernel image.

There is no stock recovery on Z3.
Here is a custom kernel for D6633, but you need to be on stock 23.0.F.1.74 firmware: http://forum.xda-developers.com/z3/development/root-stock-kernel-twrp-v01-test-28-09-t2889794
You can ask the dev there to prepare for you a custom kernel for another firmware version if you want.