Develop Bugs

Did I brick my Dinc SLCD??? Help please!

Ok, so I did unrevoked and have an unrooted phone. Started to get bored with the stock 2.2 and wanted better battery life.
My Dinc has an SLCD screen. So, when I go into the standard clockwork recovery, it goes to a black screen with white bars on the side. I had to do a custom flash recovery for my phone through unrevoked/flash. I then did a nand backup.
Tonight, I downloaded MIUI and attempted to install through the recovery flash. I ended up getting errors. So, I then thought that I needed to go through the ROM Manager app.... when I tried to flash the ROM, it automatically switched my recovery back to the Clockworks recovery..... then tried to go into the recovery portion of the ROM flash. Needless to say, I had to do a battery pull. Now when I try to do a normal boot, the phone freezes at the white screen that reads "HTC Incredible". If I boot into recovery... I can get to the hboot screen with the three droids at the bottom, but a script comes up on the screen and I think that it says something about no image... from there I can navigate around the recovery menue, but nothing works for me getting past this. If I go to recovery, it just keeps going to the black screen with the two white bars.
Is there anything that I can do. I am wondering if it is trying to flash the ROM everytime it comes on.... but this recovery method is not working on my phone.
Any help would be greatly appreaciated!

I believe you need a special clockwork recovery for SCLD screens. Not exactly sure where to find it on here, but it should be hanging around somewhere. I hope I helped ya out a bit, good luck.
Sent from my Droid Incredible running SkyRaider 3.3.2 with King Kernel BFS #5.

OK, so I was working a 24 hour shift yesterday when I posted this... unable to download any zip or exe file (damn firewalls)... This morning I was able to remove the miui zip from the root of the sd card via card reader. I then copied the PPB31IMG.zip to the root of my sd card. Then booted into recovery. I asked if I wanted to flash this file, I said yes and then it gave me the correct recovery menue. from there I was able to choose the recovery image that I had created yesterday. It seemed as though it was going to work, booted up to a stock rom that required manual setup (like on a new phone). Then I started to get FC's all over the place. I was able to find on my sd card two other nandroids that were saved in a different place than the only one that recovery allowed me to choose from. I moved the newly found recovery folders to the same location as the first and now I had those recovery options listed. I chose one from last week and thankfully my phone is restored and working.
I am not sure if this information will help anyone with an SLCD Dinc. There seems to be a huge difference in how these phones react to roms and tweaks. I am very hesitant to attempt any other ROMs at this time. On my eris, I flashed about 30 different ROMs and about 5 differnet radios. I am not new to this, but this SLCD Dinc has been a headache.

Any Aosp rom on an Slcd takes a different kernel. Get yourself the koush test#2 kernel and just keep it on your sd card. Flash it everytime you do a AOSP rom.
Sense based roms all seem to be ok as the kernel was built with Slcd in mind.

Well I'm glad you got it back up and running. I've heard about them not working well with some roms, I didn't know it was with all asop roms.
Sent from my Droid Incredible running SkyRaider 3.3.2 with King Kernel BFS #5.

doug piston said:
Any Aosp rom on an Slcd takes a different kernel. Get yourself the koush test#2 kernel and just keep it on your sd card. Flash it everytime you do a AOSP rom.
Sense based roms all seem to be ok as the kernel was built with Slcd in mind.
Click to expand...
Click to collapse
Thanks for the info on the AOSP roms. I did not know either. I wonder if there is a way to make the AOSP roms to support it by providing the new kernal in the flash or at least making a note on the AOSP ROM forum page that states the issues with SLCD Dinc's and what needs to be done to avoid problems. I would venture to say that anyone new to this stuff and was feeling brave would not be able to figure out how to restore there phone when it was acting the way mine was. Just my 2 cents.
Thanks again for the info.

[Q] Looping Boot Image

Heres the main question at hand before you read my large summary.
1) Why is my ROM's boot image looping constantly?
2) Do I have to NAND again if I revert to a nandroid backup that was made before I nand'ed my phone?
Time for the long, and mostly pointless, summary:
I'm pretty desperate to get things running on a Gingerbread ROM, if you didn't notice in my last topic 2 hours ago.
Anyways, I'm trying to get cyanogenmod7, Stock Gingerbread 2.3.1, or heck, even eVOKINGS-gingerbread ROM to work.
So far, i've tried Cyanogenmod7 and Stock Gingerbread 2.3.1 on my evo; none of which have worked past the boot screen.
Lets take stock gingerbread for example:
I downloaded the new cyanclockwork recovery rom off of rom manager and flashed it after a *long* process of nand'ing and rooting again.
Then, I powered down, booted up, and went straight into recovery in the bootloader. I went to install ROM from SD->chose the .zip .
after waiting for awhile, it said the upgrade was complete (upgrade?)
*notice: the installation bar didn't move at all durring the installation process, if that makes a difference
I rebooted, and was greeted by the HTC screen while it spelt out q-u-i-e-t-l-y-b-e-a-u-t-f-u-l
Nothing happens after that.
It just shows the HTC screen again, getting stuck at the B in beautiful. Pretty much just looping over-and-over again.
Same thing happened for Cyanogenmod7, I was constantly being looped through the skateboarding-droid figure.
I'm doing something wrong here obviously, because all these ROM's have screen captures from a EVO 4G.
Does it make a difference if I use Clockwork recovery 3.0.0.7/6/5? or 2.6.7?
Please help.
I know all my questions are rather long and complicated, but im sick of being ignored at every forum (ubuntu forums, black ops, etc.)
Or I'm impatent and overestimated your forums activenes. No disrespect to the forums or devs (I thought your forum was really active)
Edit: If I for some reason can't get a 2.3.1 ROM to work, would someone kindly point me to a stable Froyo ROM they think is the best?

Have you use amo-ra?
Sent from my evil evo!!

rsjc741 said:
Heres the main question at hand before you read my large summary.
1) Why is my ROM's boot image looping constantly?
2) Do I have to NAND again if I revert to a nandroid backup that was made before I nand'ed my phone?
Time for the long, and mostly pointless, summary:
I'm pretty desperate to get things running on a Gingerbread ROM, if you didn't notice in my last topic 2 hours ago.
Anyways, I'm trying to get cyanogenmod7, Stock Gingerbread 2.3.1, or heck, even eVOKINGS-gingerbread ROM to work.
So far, i've tried Cyanogenmod7 and Stock Gingerbread 2.3.1 on my evo; none of which have worked past the boot screen.
Lets take stock gingerbread for example:
I downloaded the new cyanclockwork recovery rom off of rom manager and flashed it after a *long* process of nand'ing and rooting again.
Then, I powered down, booted up, and went straight into recovery in the bootloader. I went to install ROM from SD->chose the .zip .
after waiting for awhile, it said the upgrade was complete (upgrade?)
*notice: the installation bar didn't move at all durring the installation process, if that makes a difference
I rebooted, and was greeted by the HTC screen while it spelt out q-u-i-e-t-l-y-b-e-a-u-t-f-u-l
Nothing happens after that.
It just shows the HTC screen again, getting stuck at the B in beautiful. Pretty much just looping over-and-over again.
Same thing happened for Cyanogenmod7, I was constantly being looped through the skateboarding-droid figure.
I'm doing something wrong here obviously, because all these ROM's have screen captures from a EVO 4G.
Does it make a difference if I use Clockwork recovery 3.0.0.7/6/5? or 2.6.7?
Please help.
I know all my questions are rather long and complicated, but im sick of being ignored at every forum (ubuntu forums, black ops, etc.)
Or I'm impatent and overestimated your forums activenes. No disrespect to the forums or devs (I thought your forum was really active)
Edit: If I for some reason can't get a 2.3.1 ROM to work, would someone kindly point me to a stable Froyo ROM they think is the best?
Click to expand...
Click to collapse
I'm pretty sure you will still have nand unlocked. The only way you wouldn't is if you unroot.
Sent using my EVO running AZRAL X V 3.1

klquicksall said:
I'm pretty sure you will still have nand unlocked. The only way you wouldn't is if you unroot.
Sent using my EVO running AZRAL X V 3.1
Click to expand...
Click to collapse
Thanks
I should face-palm myself. I just read the sticked post and I'm going to try some of his suggestions. He pointed out why cyanogenmod wouldn't work.
My whole consept of the framework went out of the window, and now I think of it more like a standard linux distro, in terms of kernel->ROM relationship.
I don't think I need to have a custom kernel for the Gingerbread beta-4, but i'll look it up just in case... Though I don't have a clear idea on how to flash that.
And to the person 2 above, im using Cyanclockwork. For whatever reason, I like its design verse RA recovery. I might try RA recovery just to see if it works better, as everyone has said it does.
I think i needed to clear all my caches and then load the ROM.

So I did a wipe of everything (data, darvik, cache) and trying to install the GB ROM. My boot screen is *still* looping. Do I need to get another kernel? Is it like flashing a ROM? Where are they at? I didn't see any in the software section...

3 Incredible's dead - up to 5 now

So I've had two incredible's now fall in to a boot loop
(wiped, pulled battery, RUU'd, went back to s-on - nothing worked)
first one I had for about 8 months with no issues until now. they did
send me a replacement XD and it did the same thing!
Now my wifes phone is doing it :\
I'm just verifying - if I RUU/S-on/remove sd card - then it HAS to be a hardware issue right? nothing that I could have done?
[Further info if needed]
All had CWR 3.0.0.5 and were rooted via unrevoked

h0x90 said:
So I've had two incredible's now fall in to a boot loop
(wiped, pulled battery, RUU'd, went back to s-on - nothing worked)
first one I had for about 8 months with no issues until now. they did
send me a replacement XD and it did the same thing!
Now my wifes phone is doing it :\
I'm just verifying - if I RUU/S-on/remove sd card - then it HAS to be a hardware issue right? nothing that I could have done?
[Further info if needed]
All had CWR 3.0.0.5 and were rooted via unrevoked
Click to expand...
Click to collapse
Were you using the same ROM or kernal each time?

It's the new cwm. It uses a different gscript setup. To a restore or flash incredible reengineered 2.3.1
If not that then I don't know. Did it happen after a Rom flash?
Sent from my Incredible using XDA App

well the first one was running Evervolv and had been for about 3 weeks.
it crashed during a phone call and never booted all the way again. (boot loop)
The second (This ones replacement) was running cm7 (Flashed it right as I got it) and worked fine the first day I had it (but I wasn't using it much that day) then it died while using the browser and fell victim to boot loopage.
The third one (my wifes phone) died about an hour later while using the browser but would still boot - but not stay on for very long. Especially if any sort of data was going on (like syncing with gmail). I figured since it was kind of working maybe it was the rom so I flashed s-on went back to stock 2.2 (ruu) where it now dies upon lock screen.
(or before sometimes)
[Ninja edit] Wifes phone had been running evervolv the amount same time as my first phone
all three were running latest CWM and had the default kernel for the rom they had. Also all 3 were flashed ruu and s-on including a clear storage for good measure (Verizon also had me do a factory reset come to think of it - before they would ship replacements)
Ianxcom said:
It's the new cwm. It uses a different gscript setup. To a restore or flash incredible reengineered 2.3.1
If not that then I don't know. Did it happen after a Rom flash?
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
could cwm leave something behind that would continue the boot loop after ruu?
That would suck because I've already sent in one phone would hate for them
to find something like that ><

have you tryed downgrading? i know i was having alot of issues with the new cwm. im running chingys rom and after the downgrade everything is running smooth again. cwm 2.5.1.2 seems to be working better...

HandsomeRob2310 said:
have you tryed downgrading? i know i was having alot of issues with the new cwm. im running chingys rom and after the downgrade everything is running smooth again. cwm 2.5.1.2 seems to be working better...
Click to expand...
Click to collapse
I've went complete stock everything (including recovery) and it didn't fix anything.
Have an update on the situation as well.
Verizon shipped me another 2 phones - both broken out of the box.
The first one just reboots over and over again and can't even enter recovery.
On the second device the speaker is blown -.-

Are you using the same or different SD card(s) amongst these failing devices?
The one you had running for 8 months, was that SD card at end of life?
Asking, as AOSP ROMs interact quite a bit more w/ the SD card than do Sense ROMs, so if your issues are all with AOSP ROMs, I suspect wonky SD card(s).

smtom said:
Are you using the same or different SD card(s) amongst these failing devices?
The one you had running for 8 months, was that SD card at end of life?
Asking, as AOSP ROMs interact quite a bit more w/ the SD card than do Sense ROMs, so if your issues are all with AOSP ROMs, I suspect wonky SD card(s).
Click to expand...
Click to collapse
I got that SD back when I got the phone so I hope its not
at the end of its life span.
I've actually didn't bother putting the SD cards in this last batch
because they were showing issues immediately (without any modding)
Thanks for the info on AOSP roms that could help diagnose future problems

That would explain a lot, actually, as AOSP ROMs call the sd during boot.
Sent from my ADR6300 using XDA App

[Q] I stuffed up. What do I do?

Hi, first time posting here.
I have a bit of a unique problem or so I've heard. So I was an idiot and decided to flash a Virtuous ROM over the WiFi via ROM Manager on my Desire Z. Previous to this it was rooted and was running CM 7.1 RC1 and was all fine. When I flashed the Virtuous Sense Rom (Not unity, the one before it in ROM Manager), it flashed, what I thought was fine. However, when I actually got into the phone, it said everything was crashing and would go into a boot cycle. Then for some stupid reason I just reflashed the 1.3.4 or whatever ROM back onto (The one you're meant to downgrade to). At this moment in time, I can't do anything. When I'm in the bootloader of the phone itself, I can't scroll up or down to the recovery option, so I can't flash through that. I've tried re-rooting the phone (Or that process), hoping that it would work. At this point in time, it keeps popping up errors at /data/local/tmp/psneuter
Note: I was following the CM7 rooting guide thing.
Anyway, I hope someone'll be able to help me out of this stupid stupid thing that I've done.
THanks!
EDIT: Okay, well, going through the CM7 rooting guide a fourth time seems to have fixed it. It's all fine now. On another note, how do you change the Virtuous Unity lock screen to something else? I'm not really a fan of the Sense 3.0 lockscreen.

You should not need to re-root after flashing any custom ROMs.
Also, I would not do any more ROM flashing if clockworkmod is not properly installed, or you don't know how to use it.

Did you bother to wipe data and cache? You didn't mention it. If you didn't that's your problem
Sent from my HTC Vision using XDA Premium App

Can't flash custom roms

Hi all, I have a problem with my Desire Z. A few days ago I made root following instruction on wiki.cyanogenmod.com. Everything went fine until when I tried to flash custom rom. After each flash the phone will not boot and hangs at the boot screen. I tried MIUI, Virtuous Quattro RC1, RC2 and RC3, and even clean original rom from HTC. The only two roms I managed to install are ILWT CM7 and Virtuous Quattro Beta 9. Of course, I did full wipe before each flash. Can anyone help?

Flozik said:
Hi all, I have a problem with my Desire Z. A few days ago I made root following instruction on wiki.cyanogenmod.com. Everything went fine until when I tried to flash custom rom. After each flash the phone will not boot and hangs at the boot screen. I tried MIUI, Virtuous Quattro RC1, RC2 and RC3, and even clean original rom from HTC. The only two roms I managed to install are ILWT CM7 and Virtuous Quattro Beta 9. Of course, I did full wipe before each flash. Can anyone help?
Click to expand...
Click to collapse
I've got the same problem with the Virtuous Quattro roms, you can try JIBwitch, Andromadus or CyanogenMod 9 for ICS. Those roms worked on my Vision. Sadly I can't help you to get those other roms, I'm still trying to figure out why this happens, if I figure it out I'll post it here.

Thanks fo reply. I tried JIBwitch and Virtuous Unity and same result. Freeze during booting...

At loading a new rom, the first boot can take up to 10 minutes. But if do you an ADB logcat while booting you should see a constant flow of messages, if this isn't the case something is wrong indeed. I am now on CyanogenMod 9 pre-Alpha 2.5 and it works like a charm. Can you try that one, and look if your device is doing something upon boot, with logcat?

Thanks for reply again. I tried again flash JIBwitch with adb logcat and its working Anyway Virtuous roms (Unity and Quattro) still not working...

No problem, glad you can use your device with ICS.
Now to figure out why the Virtuous roms won't work, I tried so many things I can't remember what I've done anymore. The best I can think of right now is that it is an download error somehow. I'll try tonight if I can flash quattro rc3 with a copy downloaded at work, and a copy downloaded at home. I'll post my results here again.

As I thought it seems to be an download error, the file I downloaded at home wont boot, while the file I downloaded at work works fine. Can you try to download the Quattro rc3 over another network??

When you rooted you may have flashed the g2 engineering hboot. So, even though you have a desire z you have the bootloader from a g2. You need the desire z bootloader to run the virtuous stuff and almost all other sense roms. Anything 3.0 and above.
Sent from my HTC Vision using xda premium

There is information from my hboot screen:
Vision Pvt Eng S-off
Hboot-0.84.2000 (PC1011000)
Microp-0425
Radio-26.03.02.18M3
eMMC-boot
So I think, I have not hboot for G2 but for Desire Z. Or I am wrong?
I am going to try download Virtuous Quattro by another network and flash again. Anyway I tried check mdl5 sum for files that I used to download and its matched.

First off, hello!
That's actually a Desire Z Engineering HBOOT you have, and not the G2 one. Applying the G2 hboot on our phone can potentially brick the phone.
Now you are saying you're wiping before flashing, but do you use Superwipe? If not, it's strongly advised that you do. This tool erases the OS partitions and format them using the ext4 filesystem. In addition to that, it also cleans the "EFS Data". EFS data is temporary radio config data, and it is advised to wipe them every time you flash a new ROM, so the radio can reconfigure itself, which has proven to fix a lot of issues, mainly with GPS but not limited to that.
Anyways, I decided to upload a version of Superwipe I had found and used numerous times for easy access. Here is the link: http://www.mediafire.com/?iygmwd1a7zrfe9p (Don't be distracted by the "G2", it works the same for both phones!) Also, the MD5 is E0B0AF31F22EE06BDE7748195F8AE651
What recovery do you have? ClockworkMod or 4EXT? I presume you have Clockwork Mod 3, since you mentioned you used the cyanogenmod wiki, It is a good idea to switch over to 4EXT Touch which has a lot of bugs fixed over from CWM and is faster as well as safer in general. The 4EXT site is here:http://www.4ext.net/
All credit goes to madmaxx82 for his hard work!
With all that said, there have been several users who couldn't get VQ RC releases to boot on their devices, would always hang them on the white HTC screen. The reason is still unclear though, we'll have to wait for an update from the Virtuous DEV's. You, also might have the same issues, hence be uncapable of booting it considering that in your reply you mention you can successfully boot Beta 9 but none of the RC versions, which was the case for the people with the issue in question.
As far as MIUI is concerned...which MIUI distribution are you using? MIUIAndroid or MIUI.us? Or did you flash an ICS MIUI release found here, particularly cjward's one...it uses the Virtuous Quattro kernel, hence the reason it didn't boot on your device. If that's the case, anyway.

Thanks for all advices!
I used CWM Recovery v. 3.x.x.x and also 5.x.x.x (not exactly sure which versions...)
Today I was trying 4EXT and SuperWipe for flashing VQ RC3 downloaded over another than my home network. But with same results as past. Everytime booting pass over HTC screen and freeze on Virtuous logo. It's mystery....
About MIUI - I was trying to flash MIUI_Au 4.0.3. I think that uses Andromadus kernel or not?
Anyway I am really satisfied with Ice Cream JIBwitch rom!