[Q] Switching Rooted DInc AMOLED to SLCD - Droid Incredible Q&A, Help & Troubleshooting

Hello all
I have a Rooted DInc with the original AMOLED. Cracked my LCD so now I have to replace it with a SLCD. My question is will the rooted Dinc freak out when I install the SLCD since it's not a AMOLED? It was rooted using unrevoked 3 but unfortunately I can't remeber what ROM and kernal i used last.
Thanks in advance
-g

you're replacing just the screen? does it not need different drivers (which was the big issue with unrEVOked3 in the first place)?
if i were to hazzard a guess, i would say HECK YES.

i cant say i know what will happen replacing the screen but unrevoked works with SLCD as does the latest clockwork recovery. i have SLCD myself and had no problems rooting and flashing CWM. also want to make sure whatever ROM youre on supports it...

yeah just the screen, touchpad digitizer still works. I remember reading that about unrevoked awhile back before i rooted but was hoping I read it wrong! daymn!

gohamstergo said:
i cant say i know what will happen replacing the screen but unrevoked works with SLCD as does the latest clockwork recovery. i have SLCD myself and had no problems rooting and flashing CWM. also want to make sure whatever ROM youre on supports it...
Click to expand...
Click to collapse
All i remember was it was a Sense ROM. Just remember the Dev finished it but wasn't going to support it anymore.

Related

Question about custom ROM on slcd Desire

Hi All,
I've gotten as far as rooting my Telus slcd Desire (.83 boot) using the clockwork slcd image for unrevoked...
Just wondering what to do next? I am concerned about how the process for flashing a Froyo rom might differ from an amoled unit?
I'm a total newb with Android and I really don't want to kill my screen or anything, so a little nudge in the right direction would really be appreciated.
Thanks guys
It won't make any difference. If you install a ROM that doesn't support SLCD (all the active ones do) then just go back to recovery and restore your backup.

[Q] SLCD Rooting and Clockwork Recovery

On Monday my replacement Incredible is supposed to arrive because my old one had an issue with the GPS but after doing a little research I see that there have been issues with ClockWork Recovery and the SLCD models. Have these issues since been fixed? I don't want to go rooting the replacement phone (which I'm assuming will be SLCD) and ruin it. I was able to root my AMOLED one fine and return to stock for the return. Thanks for any help
I have an SLCD DInc as well. I know a few people have said they found a CWM Recovery that works with SLCD, but I can't seem to find it yet. With Unrevoked still working on a fix for the Nov OTA, I'm hoping they offer a package with CWM for SLCD.
One that works well is this one:
http://forum.xda-developers.com/showthread.php?t=845451
This is the one I use (adrynalyne's mod of clockwork recovery): http://forum.xda-developers.com/showthread.php?t=788306

[Q] Questions about rooting (HBOOT & Build)

So I'm looking into this unrEVOked thing, and it seems as though I could root my EVO just fine with it. However my HBOOT is 2.02 and my build number is 3.30.651.3 (this is the part that worried me, since my friend said that a EVO with the hardware version of 0004 and that build number won't be able to be rooted).
My question is basically is there any method of rooting that I could do with no worries? Somebody mentioned to me this method right here but I want to be certain I would be alright with that before I get started. The steps aren't the issue, I'm just trying to do my homework beforehand and be sure I'm ok.
the method you linked will work. unrevoked will not. pm me or gtalk [email protected] for help. i sitll havent gotten a hboot 2.02 person to give me enough time to let me help them root.
I have a 0004 hboot 2.02 device, and used that method. I had many issues during the middle of the process, but made it through using a microSD memory card reader to rename those pc36img.zip files...
Worked great!
dkdude36 said:
the method you linked will work. unrevoked will not. pm me or gtalk [email protected] for help. i sitll havent gotten a hboot 2.02 person to give me enough time to let me help them root.
Click to expand...
Click to collapse
Hey Dkdude36, I have questions along the same lines. For hboot 2.02, what other rooting options exist that DO NOT involve the use of Unrevoked's components. Looking through the download files, you'll notice both referenced methods (this and this ) use the file unrevoked-forever. So, what gives?
I am personally on the lookout for a rooting process (for hboot 2.02) that doesnt use that method. The reason being that it's a bit tedious to unroot.
unrevoked forever is different than unrevoked. the methods are completely valid. unrevoked-forever seems to be the key ingredient in rooting 2.02
dkdude36 said:
unrevoked forever is different than unrevoked. the methods are completely valid. unrevoked-forever seems to be the key ingredient in rooting 2.02
Click to expand...
Click to collapse
So, if I currently have hboot 2.02, and I want to 'downgrade' to the eng build .76.2000, what are the steps? Root with whatever flavor of unrevoked-forever that works with my EVO (hardware 003), then flash the hboot .76.2000 downgrade zip? I don't even understand why I need hboot 2.02 versus the earlier builds. Besides it also appears the earlier root methods (1 or 2 clicks, Simple Root 1.47.651.1,etc detailed here will not work on 2.02.).
Got around to rooting the phone just fine using the method I linked. However I can't installed CM 6.1 RC at all. It gets stuck at the white EVO 4G splash screen. I'm assuming it's an issue with 0004 EVO's?
Darknight630 said:
Got around to rooting the phone just fine using the method I linked. However I can't installed CM 6.1 RC at all. It gets stuck at the white EVO 4G splash screen. I'm assuming it's an issue with 0004 EVO's?
Click to expand...
Click to collapse
I've been trying to figure this out for a few days now... Apparently it's the kernel. A guy in the official forum said he used the toast test kernel 2.6.35 and everything works, including the camera! I'm just having a hard time finding it!
ImmortalLuD said:
I've been trying to figure this out for a few days now... Apparently it's the kernel. A guy in the official forum said he used the toast test kernel 2.6.35 and everything works, including the camera! I'm just having a hard time finding it!
Click to expand...
Click to collapse
Just saw the post about it, I rather just wait till they get a fix out for CM. I'll stick with Fresh, as much as I dislike sense I can deal.
Darknight630 said:
Just saw the post about it, I rather just wait till they get a fix out for CM. I'll stick with Fresh, as much as I dislike sense I can deal.
Click to expand...
Click to collapse
I don't know if that's going to happen anytime soon. I just installed the lastest nightly with snap's 7.6 cfs kernel. Everything works, and I'm super happy! Still use Frost, Fresh, MIUI, Myn's Warm, and everything else too...
tho this may seem like a dumb question i just got my evo over the weekend and i havent stumbled upon the answer yet....how do you know what hboot you have? i see that i have hardware 004 and i see that i have the newest build number i just not sure where or how to tell the Hboot version. Any ideas? Thanks.
Just boot into hboot. Power off, and then hold power and volume down. You are now in hboot.

[Q] New to Verizon and the Beauty that is the Inc.

So, after finding some amazing Black Friday deals (Inc and Fascinate for free, no activation fee!) I finally decided to get off my 6 month expired t-mobile contract.
Already rooted my girlfriends Galaxy S Fascinate (wow easiest root i've done... also what a beautiful screen.)
Than came all of my confusion regarding my inc.
I upgraded to the latest November update (I know, bad Embrace!) than realized I could not easily root it. It is the SLCD version
After hunting around all of my favorite phone forums I have found a few downgrade guides, and a lot of warning about a screen brick on the SLCD inc.
I have also read that you can downgrade an SLCD with certain rom and recovery packages(amon_ra). But I can not seem to find any clear instructions or any confirmation of what roms work and what do not.
I'm slightly OCD and the VZ bloatware is murder.
I am aware that Unrevoked is working on a fix but I would love to root this thing asap.
Thanks XDA... Second post after many years of lurking.
TL;DR: SLCD Inc, Nov OTA, Need Root.
I would suggest trying to reflash an older 2.1 or 2.2 RUU then root that.
From what I understand using the downgrade methods out there will brick an SLCD screen.
Am I wrong? I would like to think that as long as I am flashing a stock rom it won't brick anything, but If I flash the wrong recovery I will brick it.
Does anyone have any experience downgrading the latest ota with an slcd inc?
I've never had a problem rooting a phone and I rooted at least 20, but for some reason this one scares me D:
I don't have an SLCD so you'll have to wait for somebody else to chime in. As far as I know, the RUU should be fine and flashable in even an unrooted stock HBOOT since it is signed.
I would just make sure that the RUU you are using came from an SLCD phone. An older 2.2 RUU should be fine. Perhaps there are no 2.1 RUUs for the SLCD? I don't really know. But flashing a stock ROM is not going to brick a phone if it came from that phone.
So I cheated.went to Verizon told them I was having random reboots after the latest update... replaces it
Now I'm rooted
Sent from my ADR6300 using XDA App
Embrace said:
So I cheated.went to Verizon told them I was having random reboots after the latest update... replaces it
Now I'm rooted
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Whatever works works, but in case anybody else is wondering, it has been confirmed that it does indeed work if you have the latest OTA to simply flash an older RUU through HBOOT, root it and turn S-OFF, and then you can flash whatever you want on it.

Incredible Issues - Back To Stock?

Hi Everyone,
Been lurking here a long time... first on my Moto Droid and now the Incredible. Ran into my first unsolvable (by me) issue. I've had the Incredibly since beginning of December (SLCD). I rooted it via unrevoked, ran SkyRaider for a while changed roms, back to SkyRaider. I've had no issues. Last week I started getting random reboots... phone would reboot, then reboot multiple times from Incredible logo... then finally start up and my icons and wall paper would all be screwed up. Needless to say I've searched a ton and the only answer I've found is this points to a defective phone. So now I'm trying to get it back to stock - which I haven't been able to find a how-to or any info for anything as new as the current Roms. I was able to install a stock rooted rom, get s-on but then I can't figure out how to un-root it and get the stock recovery on as the only stock rom I found was rooted and that doesn't help me on the stock recovery.
Any suggestions?
Thanks,
Jon
There should be pb img you load up in hboot. I've used it worked like a charm. I'll see if I can find it and put the link up. Since you have an slcd screen also don't use any ruu's that downgrade to 2.1 it was made for oled screens it will brick the slcd screen incredibles.
just found it
http://www.incredibleforum.com/foru...s/5723-how-get-back-complete-stock-s-off.html
check that out.
shawn328 said:
There should be pb img you load up in hboot. I've used it worked like a charm. I'll see if I can find it and put the link up. Since you have an slcd screen also don't use any ruu's that downgrade to 2.1 it was made for oled screens it will brick the slcd screen incredibles.
just found it
http://www.incredibleforum.com/foru...s/5723-how-get-back-complete-stock-s-off.html
check that out.
Click to expand...
Click to collapse
Thats the version I edited from this original post found on this forum
http://forum.xda-developers.com/showthread.php?t=786436
Has all the files that are that are in the first link. Both threads unroot you to the 3.26 build and thats a good thing.
Thanks, that's the one I had followed originally and it wasn't working for me (but I had an unstable rom on there). Once I got something stable enough to boot I did the RUU method and it did the trick. Off to the verizon store today!
Thanks,
Jon

Categories

Resources