Develop Bugs

Just wondering

With toast's new kernel with working camera, could we say flash darchdroid then flash the kernel ontop of that

I hope you like my totally ambiguous answer
In certain cases you can, because the dev of the rom has not modified the kernel.
In other cases, the dev has modified the kernel, so if you flashed toasts kernel, it would overwrite that and your phone would turn into a black hole. Or it would just cause issues, I cant remember

[Q] can not boot into recovery?

This is my first post and I was wondering if anyone can help.
I have an incredible, 2.2, rooted, with Rom Manager. I flashed the lastest recovery through Rom Manager but when I try to boot into recovery the screen stays black with a thin white line on both sides. I had some backups from another Dinc I had and took a chance at a restore from one of my older Roms. Although the screen stayed black it did load the backup so my recovery appears to be working fine only I can't see it.
Doing this before I am scared if I load a bad rom or something and get locked up I won't be able to see the recovery to restore my backups. I have tried older recoveries through Rom Manager with the same problem however when I flash RA_GNM Recovery v1.7.6 it works perfectly. Only problem is Rom Manager won't use that.
Any suggestions would be greatly appreciated.

Search for slcd recovery.
Sent from my ADR6300 using XDA App

ok now I am really confused. I research the slcd and not quite sure what I have or looking at. How do I know? My old Dinc was literally only about a month older than my previous one. Can you give me a brief "Dumbed Down" version of what exactly this is?
Sorry to be such a newbie.

mmjets said:
ok now I am really confused. I research the slcd and not quite sure what I have or looking at. How do I know? My old Dinc was literally only about a month older than my previous one. Can you give me a brief "Dumbed Down" version of what exactly this is?
Sorry to be such a newbie.
Click to expand...
Click to collapse
From what you're describing, your phone has a slcd screen, not amoled. As such, you're going to have a few issues here and there with recoveries as well as ROMS (due to your hardware not being supported by the included kernel). Search the forums for slcd and you'll see suitable workarounds for this.

To see what screen you have... Menu > Settings > About Phone > Hardware Version. If yours is 003, you have a SLCD screen.

Anyone who has the.new guy Rom ..is there a way to get the HTC pot penguin to as my boot image. That penguin is great lol
Sent from my ADR6300 using XDA App

Just incase anyone is having this problem I did find a site with a fix. Download the file, change the name and flash through hboot. It has worked for me and now I can get into recovery. Here is the link:
**Sorry the site wouldn't allow me to post the link***
Only problems I have now and I am hoping someone can help is that I can't seem to install any custom roms that don't have sense. When installing MIUI or CyanogenMod, etc I get locked up on the white HTC screen.
Anyone know a solution?

http://www.incredibleforum.com/foru...nly-see-black-screen-white-bars-recovery.html
That has the custom recovery you need for an slcd screen. I used that exact dl link to get the image. Then i used the unrevoked 3.21 tool to set it to flash a custom recovery then let the tool run. All went flawlessly
*Edit sorry i didn't see you fixed it. As far as cyanogen mod goes, I know it doesn't work with slcd screened incs because we have different display drivers. I believe that is true for all aosp roms. If you want a vanilla feel go with skyraider vanilla 3.0. It works perfectly for me

Thanks for posting that link and the help. I will keep checking to see if a solutions for slcd screens comes around so that I can install some other roms.
I just hate that I thought I upgraded my inc and as it turns out it was probably a downgrade.

To my understanding, I believe all roms work except aosp roms. I remember reading somewhere (but don't remember where) that they were working on a fix. So maybe it'll come before you know it

Koush's test #2 kernel works fine and will boot aosp on my Slcd.

Just wanted to let you know I found a way to make MIUI and cyanogen work on a slcd Dinc. I found the fix in one of the forums so I don't want to take any credit for it but it worked for me so I wanted to pass that info along to anyone else having the same issue.
I downloaded the Koush test kernel from Rom Manager, then I flashed the MIUI rom. Once flashed it gets stuck on the white HTC screen. I pull the battery, go to recovery, and then open zip from SD card. I find the Koush kernel, install, and reboot and it has worked for everything I have tried so far (MIUI and Cyanogen).
Hope that helps someone.

mmjets said:
Just wanted to let you know I found a way to make MIUI and cyanogen work on a slcd Dinc. I found the fix in one of the forums so I don't want to take any credit for it but it worked for me so I wanted to pass that info along to anyone else having the same issue.
I downloaded the Koush test kernel from Rom Manager, then I flashed the MIUI rom. Once flashed it gets stuck on the white HTC screen. I pull the battery, go to recovery, and then open zip from SD card. I find the Koush kernel, install, and reboot and it has worked for everything I have tried so far (MIUI and Cyanogen).
Hope that helps someone.
Click to expand...
Click to collapse
Really? My post above says that.

Your kidding right?? i didn't see your post as it was on page two so my apologies. I didn't mean to steal any of your credit!!! lol. I am just trying to help others out.

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] Z based ROMs - prerequisites?

So my launch day Incredible bit the dust out of nowhere the other day, following some quirky behavior leading up to it (random reboots, inability to power up after battery pulls).
I get my warranty RMA yesterday, and figure that before I restore my Titanium backup, I'll play with some ROMs. I'm assuming I was lucky enough to get another AMOLED replacement, since by any method I can tell it appears to be AMOLED and not SLCD (part number is ADR6300VW, hardware version 0002).
At any rate - I figured I'd try one of the Desire-Z ROMs or a Gingerbread ROM. After I fully rooted and turned NAND S-Off. After confirming those worked fine, I rebooted and flashed a Gingerbread ROM from Clockwork. Rebooted, never got past the HTC Incredible splas screen.
Couldn't get it to work at all - after all sorts of wipes, I finally gave up and flashed Virtuous, figuring it's close to stock. Got back up and running, no problem.
Turned to a Desire-Z ROM - and the same happened again. Splash screen, nothing further. After the same tries, went back to recovery, flashed Virtuous and then SkyRaider, and again, up and running fine.
I'm on HBoot 0.92 with the 7.28 radio. Is there something I'm missing on these Z ROMs? I read through the threads, saw a few people report the same but no real conclusion as to why it was happening.
Thoughts?

Judging by what you posted, you only used ROM Manager to flash roms after booting into recovery correct?
What happens when you manually go into recovery, wipe cache/data/dalvik, and flash the rom from your SD Card? I was running Nil's Business Sense (Desire Z) rom quite fine after flashing it. Some people have issues with ROM Manager and others don't and I'm one of the people who do use ROM Manager to flash roms so I can't help you in that respect.

Sounds like you're using CWM3.
Try any older version.

dpwhitty11 said:
Sounds like you're using CWM3.
Try any older version.
Click to expand...
Click to collapse
This is wat it sounds like
Sent from my ADR6300 using XDA App

If you are using ClockWorkMod v3 and tring to do a fresh install with a cwm3 capable ROM it could be a problem. Seems like cwm3 acts a little funny. Or you could be on cwm-v2 and trying to install a cwmv3 ROM and that does not work.
So the key is use cwm 2.5.1.2 and a cwm-v2 Z ROM

[Q] Flashing a new kernel on Liquidsmooth v 2.10 makes my screen unusable

Sorry if this isn't the correct place to post this. I would post it in the ROM's thread but since this is my first post on XDA I'm not allowed to. I'm trying out the Liquidsmoothhttp://forum.xda-developers.com/showthread.php?t=2347004 ROM and want to flash another kernel mainly for exfat support and longer battery life. I've tried KT-SGS4 and ChronicKernel so far (downloaded the AOSP 4.3 versions and wiped cache/dalvik cache and fixed permissions after flash) each time after rebooting the ROM's splash screen colors would appear inverted, the screen would turn off, and when I turned it back on the colors were still inverted and everything on the screen was double. I couldn't use the screen at all because I couldn't read anything and had no choice but to power off the phone and boot into recovery to flash the ROM again. I'm just wondering if the problem is my fault or if there's some kind of compatibility issue with the ROM and other kernels?

PotatoDrum said:
Sorry if this isn't the correct place to post this. I would post it in the ROM's thread but since this is my first post on XDA I'm not allowed to. I'm trying out the Liquidsmoothhttp://forum.xda-developers.com/showthread.php?t=2347004 ROM and want to flash another kernel mainly for exfat support and longer battery life. I've tried KT-SGS4 and ChronicKernel so far (downloaded the AOSP 4.3 versions and wiped cache/dalvik cache and fixed permissions after flash) each time after rebooting the ROM's splash screen colors would appear inverted, the screen would turn off, and when I turned it back on the colors were still inverted and everything on the screen was double. I couldn't use the screen at all because I couldn't read anything and had no choice but to power off the phone and boot into recovery to flash the ROM again. I'm just wondering if the problem is my fault or if there's some kind of compatibility issue with the ROM and other kernels?
Click to expand...
Click to collapse
First off....the enter key is your friend. Space the paragraphs out more. Giant blocks of text are a little hard to follow.
Second, the latest Chronic and KT kernels are tweaked to deal with a new way CyanogenMod processes the screen. If you use the newer kernel on a rom that doesn't have that update, you'll get what you see. The inverted colors. Same if you use an older Chronic or KT kernel on a new rom that's been updated. Either way they don't work together.
Try an older version of Chronic and it should work. Read Albino's changelog for Chronic Kernel to see when he fixed the color inversion issue, and check the date on that changelog. (It's been in like the last month, I just don't recall the date) Use the kernel version from just before that and it should boot up just fine.

Thanks for the advice. Sorry about the spacing issues, I was kind of in a panic. I flashed ChronicKernel v.2.2 and everything works properly now.