So I just put Clockwork Recovery on an new SLCD Droid Incredible. I was about to flash the IncDoes new Sense Rom which I'm also running on an Amoled Incredible (and enjoying on that device) and decided to pause for a second before doing it wondering if anyone had done it already. Are the roms compatible between the SLCD and Amoled Incredibles? Any one know? Or am I treading in uncharted waters?
codyt01 said:
So I just put Clockwork Recovery on an new SLCD Droid Incredible. I was about to flash the IncDoes new Sense Rom which I'm also running on an Amoled Incredible (and enjoying on that device) and decided to pause for a second before doing it wondering if anyone had done it already. Are the roms compatible between the SLCD and Amoled Incredibles? Any one know? Or am I treading in uncharted waters?
Click to expand...
Click to collapse
I have a SLCD Incredible and all roms run just fine. I don't notice anything different beside missing my vibrant AMOLED colors
You want to sell me your AMOLED Droid Incredible? I'm desperately looking for another INC to dev on...
ID
Well my company owns both of these, so I can't sell the other one.
So my SLCD DINC will not show Clockworks screens. I just get a black screen with two white lines down either side. phone boots fine and i can get to the bootloader screen but when i try to go into clockwork I only get the black screen with the white outside lines.
Are you using Clockwork? Did you use UnRevolked to load it or Fastboot?
How are you using fastboot, I take it you flashed the mfg hboot?
codyt01 said:
Well my company owns both of these, so I can't sell the other one.
So my SLCD DINC will not show Clockworks screens. I just get a black screen with two white lines down either side. phone boots fine and i can get to the bootloader screen but when i try to go into clockwork I only get the black screen with the white outside lines.
Are you using Clockwork? Did you use UnRevolked to load it or Fastboot?
Click to expand...
Click to collapse
Actually I'm not, I used Unrevolked3 to install Clockworkrecovery and supposedly root. But when I run ADB with the SDK it finds the device but it doesn't seem that I really have root.
I had remembered Fastboot-Windows from my previous work with the Nexus and original Droid. I cheated with Unrevolked3 this time, and it worked flawlessly on the Amoled Dinc, but not this SLCD Dinc
the real issue is that I can't see Clockwork's screens at all. Just a black screen with white lines down the side. I can clearly get to the phone through ADB cause it's listed and I can run commands like SU, although it tells me permission denied when I run SU. So it sounds like something didn't quite go right?
I'm not a developer, I'm just a guy that plays with ROMs on a lot of different phones.
Yeah I ran unrevoked on mine as well (just got an SLCD version today). I can backup ROMs and everything with full root access, but when booting into clockwork all it shows is black screen with white on the sides, so I can't actually tell what it's doing until it reboots.
bloodiedwraith said:
Yeah I ran unrevoked on mine as well (just got an SLCD version today). I can backup ROMs and everything with full root access, but when booting into clockwork all it shows is black screen with white on the sides, so I can't actually tell what it's doing until it reboots.
Click to expand...
Click to collapse
how can you tell you can back up roms with it? Do you know that the controls work? + - for up and down and the power for select? and are you just memorizing the locations?
I just opened up Rom Manager on my phone and when I choose make backup it goes to that black screen and when it finishes it reboots. When I go into ROM Manager it shows that there was a backup made.
I would definitely like a version that could be useable when going through manually into recovery though.
bloodiedwraith said:
I just opened up Rom Manager on my phone and when I choose make backup it goes to that black screen and when it finishes it reboots. When I go into ROM Manager it shows that there was a backup made.
I would definitely like a version that could be useable when going through manually into recovery though.
Click to expand...
Click to collapse
Wow, I've gotta get with the program. I haven't browsed this forum enough. I had no idea a tool like ROM manager was out there. found it downloaded it loading .7 now on the SLCD Dinc. Black screen with white now as it's loading the rom, no messages on whether it's working or not. Kind of scary, but I'll let it run.
Looks like a very cool tool.
side question, but any one know how much better the slcd version does with battery? and if they fixed the charging issue (bump charge)?
gummehbear said:
side question, but any one know how much better the slcd version does with battery? and if they fixed the charging issue (bump charge)?
Click to expand...
Click to collapse
i would also like to know this well atleast the bump charge part
the battery is Dependant literally on what colors u have displaying the most
for a
AMOLED screens if you display dark/black more you waste less battery
SLCD screens if you display white/bright colors more you waste less battery
great thing i have a amoled and i love dark colored themes
superchilpil said:
i would also like to know this well atleast the bump charge part
the battery is Dependant literally on what colors u have displaying the most
for a
AMOLED screens if you display dark/black more you waste less battery
SLCD screens if you display white/bright colors more you waste less battery
great thing i have a amoled and i love dark colored themes
Click to expand...
Click to collapse
interesting. how can one tell which screen their Dinc has?
mcgoo99 said:
interesting. how can one tell which screen their Dinc has?
Click to expand...
Click to collapse
Up to recently, they've had AMOLED. They are being made with SLCD now though.
Sent from my Droid Incredible
Div033 said:
Up to recently, they've had AMOLED. They are being made with SLCD now though.
Sent from my Droid Incredible
Click to expand...
Click to collapse
i know; i got my Dinc roughly two months ago, but don't know if it was before or after the switchover
mcgoo99 said:
interesting. how can one tell which screen their Dinc
has?
Click to expand...
Click to collapse
I found the answer here yesterday:
http://forum.xda-developers.com/showthread.php?t=799499
look on your box at the model number or on your phone
if it ends with w2 then it's amoled
if it ends with w3 is slcd
I checked my box last night but I sent the UPC back for a rebate so ???
julesism said:
I checked my box last night but I sent the UPC back for a rebate so ???
Click to expand...
Click to collapse
The rebate form stated to make and save a copy of everything If you have a receipt with the UPC google it. You could try calling big red, that might work
ToyTank said:
The rebate form stated to make and save a copy of everything If you have a receipt with the UPC google it. You could try calling big red, that might work
Click to expand...
Click to collapse
I have receipt copies somewhere. Hopefully the model number is on it. I do not have a copy of the box.
I had this same issue a few nights ago... you have to upgrade your bootloader to. 92
Sent from my Incredible using XDA App
Jaxon2319 said:
I had this same issue a few nights ago... you have to upgrade your bootloader to. 92
Sent from my Incredible using XDA App
Click to expand...
Click to collapse
They should already have the .92 bootloader if brand new and stock 2.2.
codyt01 said:
Well my company owns both of these, so I can't sell the other one.
So my SLCD DINC will not show Clockworks screens. I just get a black screen with two white lines down either side. phone boots fine and i can get to the bootloader screen but when i try to go into clockwork I only get the black screen with the white outside lines.
Click to expand...
Click to collapse
Hopefully this helps you...
I do believe that IncredibleDoes uses Amon_Ra recovery, so if he is using a slcd like he says with no problem, then I would try that instead of clockworkmod.
Sent from my ADR6300 using XDA App
Related
So i just got my second android powered phone which is a htc droid incredible, brand new completely stock. so i want to root, unlock bootloader, da da da, etc.
a few guides i followed here on xda which is really helpful, but before i get started and follow some guides, which ones?
which should i follow?
http://forum.xda-developers.com/showthread.php?t=709220
http://unrevoked.com/rootwiki/doku.php/public/forever
unRevoked or the old way?
Use unrevoked3. It is very easy and will take you less than 5 minutes.
BEFORE you root the new Incredible, make sure you know whether you have the AMOLED or the other type display - it will make a difference in whether/how your rooted device displays your recovery screen (or not) after rooting.
Said another way, I think the non-AMOLED screens don't let you see anything in recovery after rooting. Recommend you thoroughly research whether the type screen you have (if not AMOLED) has a recovery that lets you see what's on the screen.
smtom said:
BEFORE you root the new Incredible, make sure you know whether you have the AMOLED or the other type display - it will make a difference in whether/how your rooted device displays your recovery screen (or not) after rooting.
Said another way, I think the AMOLED screens don't let you see anything in recovery after rooting. Recommend you thoroughly research whether the type screen you have (if not AMOLED) has a recovery that lets you see what's on the screen.
Click to expand...
Click to collapse
wow i did not know that. so how do i go about finding out if my screen is amoled or not?
merbiyatch said:
wow i did not know that. so how do i go about finding out if my screen is amoled or not?
Click to expand...
Click to collapse
AMOLED is ok, SLCD gives issues.
http://forum.xda-developers.com/showthread.php?t=818052
merbiyatch said:
wow i did not know that. so how do i go about finding out if my screen is amoled or not?
Click to expand...
Click to collapse
look of your proof of purchase on the box and if it say w1 r w2 it is an amoled. If it says w3 you have a slcd. Hope this helps.
merbiyatch said:
wow i did not know that. so how do i go about finding out if my screen is amoled or not?
Click to expand...
Click to collapse
Easiest way to check: menu>settings>about phone>hardware information> hardware version. 0002 = amoled = good to go, 0003 = slcd = search forums for the right recovery.
yeah definitely go with unrevoked3, I just got my new incredible yesterday and had it rooted and flashed the slcd recovery image in less than 5 minutes. Really this was the easiest flash I've ever done on any phone.
When I first got my desire back in July, I was over the moon with all these jam packed features and functions and that AMOLED screen not to mention my very first smart phone. That didn't last, ever since I moved to the HTC Desire it gives me nothing but grief, I can hardly use it due to its faults, either be it hardware or software based; Boot Loops, Boot Freeze, Inconsistency, On-board Low Memory, Overheating, Buggy that's just a few problems with it.
Trying to fix it by debranding to the HTC Stock ROM didn't solve any problems.
I think the time has come now to move on from my desire and chose another device other than HTC, preferably iPhone?
Please share your experiences regarding this device and what would you recommend as my next device.
-Deeco
Did you try rooting, S-OFF and installing a non-stock ROM? I know 3-4 people with a Desire and they are all stock and they all work immaculately.
I am not interested in using a Non-Stock ROM and I don't think that would make any difference. I was talking generally about the phone and the amount of flaws disadvantages it's self from reliability.
I am absolutely satisfied with HTC after using 3 different phones made by them in the past 3 years. iOS and Apple are great for dumb people.
Why didn't you bring it in for warranty? Freezes and reboots are not normal on an unrooted desire.
Sent from my HTC Desire using XDA App
Deeco7 said:
I am not interested in using a Non-Stock ROM and I don't think that would make any difference. I was talking generally about the phone and the amount of flaws disadvantages it's self from reliability.
Click to expand...
Click to collapse
Maybe it's just a dodgy phone? A new ROM would amost certainly fix your issues providing they aren't hardware related. Have you tried to get it repaired using your warranty?
I came from an iPhone. iPhone get hotter than this phone.. you probably got a defective phone, mine works flawlessly...
And believe me, use this rom and you'll love it:
http://forum.xda-developers.com/showthread.php?t=741663
If you want to move to another phone look around go in shops there are many try an iPhone, Blackberry, or another phone. It's your choice no one can make that decision for you.
Ik Desire said:
Why didn't you bring it in for warranty? Freezes and reboots are not normal on an unrooted desire.
Sent from my HTC Desire using XDA App
Click to expand...
Click to collapse
That would be the obvious thing to do, but I am unwilling to have my AMOLED screen replaced with a SLCD one, that's just me.
The phone is defective you guys are right but as explained I don't want the above scenario to occur.
TBH, the only reason one I metioned iPhone is because it has all the features I want 'Front face camera' etc besides the Signal Problem, I can jailbreak/mod the phone to my desire and needs.
Deeco7 said:
That would be the obvious thing to do, but I am unwilling to have my AMOLED screen replaced with a SLCD one, that's just me.
The phone is defective you guys are right but as explained I don't want the above scenario to occur.
TBH, the only reason one I metioned iPhone is because it has all the features I want 'Front face camera' etc besides the Signal Problem, I can jailbreak/mod the phone to my desire and needs.
Click to expand...
Click to collapse
??
But you're not willing to root your Desire and flash a custom ROM?
brummer101 said:
??
But you're not willing to root your Desire and flash a custom ROM?
Click to expand...
Click to collapse
Like I mentioned above, I had rooted it but I consider flashing to a Custom ROM will make no difference whatsoever as my device is fault and unwilling to deliver to HTC under warranty due to screen replacement.
Deeco7 said:
Like I mentioned above, I had rooted it but I consider flashing to a Custom ROM will make no difference whatsoever as my device is fault and unwilling to deliver to HTC under warranty due to screen replacement.
Click to expand...
Click to collapse
so, you're looking for an excuse to buy an iPhone, or you are making yourself a martir? You dont want to try a custom ROM, but dont want to change the phone neither... so what's the point of this thread?
brummer101 said:
??
But you're not willing to root your Desire and flash a custom ROM?
Click to expand...
Click to collapse
Good point. I'd rather be with an Android OS than iOS, but with that said I'm not going to go over the rigmarole of an Android Vs iOS Vs WP7 'discussion'.
If it was my phone I'd take the time to atleast root it and get Clockwork recovery installed and try a light Sense-based ROM to see if it is defective hardware or not.
What's even more simple than that is resetting the phone to factory defaults to see if the problems persist, have you given that a go?
netomx said:
so, you're looking for an excuse to buy an iPhone, or you are making yourself a martir? You dont want to try a custom ROM, but dont want to change the phone neither... so what's the point of this thread?
Click to expand...
Click to collapse
Look, I'm not sure if I have phrased it wrong or something, but using a custom rom hadn't made any difference.
Deeco7 said:
Look, I'm not sure if I have phrased it wrong or something, but using a custom rom hadn't made any difference.
Click to expand...
Click to collapse
Aye you did, if it still persists you've got a duff phone. Warranty is the best bet, get them to replace it, then stick with it or try another phone. As it's pointless using a defective device, it'd drive me up the wall.
netomx said:
... so what's the point of this thread?
Click to expand...
Click to collapse
Exactly, so you've got a defective phone but won't RMA it, purely on the basis you'll get an LCD screen instead? Madness... Those early AMOLEDS are nothing to write home about too.
Deeco7 said:
Look, I'm not sure if I have phrased it wrong or something, but using a custom rom hadn't made any difference.
Click to expand...
Click to collapse
I thought you didnt tried a custom ROM, my bad. Well, send it to repair, and then sell it in ebay and get an AMOLED one. If you're insterested, and if you live in USA, I got the A8181 version, and I want the A8183 (WCDMA 850), and I dont care to get a SLCD screen.
The SLCD's are actually more vibrant in colour, although I'd say the AMOLEDs are more efficient.
Kalavere said:
The SLCD's are actually more vibrant in colour, although I'd say the AMOLEDs are more efficient.
Click to expand...
Click to collapse
Yet again, I have mentioned that I don't want to sacrifice my AMOLED screen for SLCD as I the AMOLED is what I payed for and is better in comparison. The Desire battery is bad as it is and adding SLCD will not do anygood.
I don't want to drift into that, a back to my first post.
Deeco7 said:
Yet again, I have mentioned that I don't want to sacrifice my AMOLED screen for SLCD as I the AMOLED is what I payed for and is better in comparison. The Desire battery is bad as it is and adding SLCD will not do anygood.
I don't want to drift into that, a back to my first post.
Click to expand...
Click to collapse
Considering you are asking people for help, you are being very short and sharp with people and really aren't being too polite. That was a statement, I was retorting generally to sarge78's post about screens.
I just lost my phone and unfortunately need to get a $100 replacement from Asurion two weeks (approx, whenever they release it.) before I upgrade to the Galaxy Nexus...Can I use a Nandroid backup of my old phone on my new replacement incredible when I get it? Or do the hardware differences matter and will cause it to be unreliable and crash?
Unfortunately, the differences between the two and other more granular stuff like device id stored in the backup would cause many many issues, were it even bootable.
Sent from my ADR6300 using XDA Premium App
EvanVanVan said:
I just lost my phone and unfortunately need to get a $100 replacement from Asurion two weeks (approx, whenever they release it.) before I upgrade to the Galaxy Nexus...Can I use a Nandroid backup of my old phone on my new replacement incredible when I get it? Or do the hardware differences matter and will cause it to be unreliable and crash?
Click to expand...
Click to collapse
as long as the phones are the same ie. if you used an AMOLED to AMOLED or SLCD to SLCD device it should work. the worst it is going to do is not boot. i would recommend having a rom on your phone sd card and try it. If anything happens you can always RUU with the .exe to get it back to working order.
Thanks guys, yeah I guess its worth a shot, I'm not sure what the new screen is or even what my old screen was...but as you said the worst that'll happen is it wont boot. I really only need it till I can get the Galaxy Nexus, even if it is a little unreliable for the time being..
EvanVanVan said:
Thanks guys, yeah I guess its worth a shot, I'm not sure what the new screen is or even what my old screen was...but as you said the worst that'll happen is it wont boot. I really only need it till I can get the Galaxy Nexus, even if it is a little unreliable for the time being..
Click to expand...
Click to collapse
New screen will be slcd. Its really hard to get an amoled. When did you buy the other incredible?
Sent from my sexy assistant. (AMOLED HTC Incredible)
1st gen preorder...the phone almost made it..
You more than likely had a AMOLED then.
EvanVanVan said:
1st gen preorder...the phone almost made it..
Click to expand...
Click to collapse
yeah then the nandroid might not work unless you get another AMOLED because thats what the OG incredible was. if you try to restore it your touch screen will not work.
i mean if you really want to try it better say a little prayer first.
yeah, had a feeling that was the answer thanks...oh well at least all the important stuff was on the sd card and the contacts were on google
smtom said:
Unfortunately, the differences between the two and other more granular stuff like device id stored in the backup would cause many many issues, were it even bootable.
Sent from my ADR6300 using XDA Premium App
Click to expand...
Click to collapse
I think so ha ha..
Hey I was just wondering if this was just me..but when i boot up the phone on the boot up animation as the colors are doing they're thing, it looks like the screen is a bit pixelated or as if it has oily blotches on the screen. I was wondering if that's normal with the phone or if like i should get it replaced. and than also with that..this is my second phone already..i exchanged my first one cause the usb connector wasnt working, would verizon exchange this one with no problem also?
Only in the boot animation? Are you sure it isn't supposed to look that way?
Yes, the boot animation is a bit rough-looking normally.
Sent from my Galaxy Nexus using XDA App
ah alright i wasnt sure if it was supposed to look that way or not..thanks for that merry christmas all!
it's normal, to made the boot animation smoother.
Hated to bump an old thread, but it seemed to be the closest hit.
Just got my GNex from Google Play today. When I turned on the phone for the first time, the animation discussed here appeared to be absolutely vivid and stunning - HD quality. It was quite impressive indeed.
However, after accepting the system update nag it appears grainy and closer to SD quality following the update. It's now feeding my paranoia about everything else I look at.
Other than that, I don't see any other screen issues other than the blue tinge when viewing from indirect angles.
Not sure what all the update did. Looks like I am running Android Version 4.04 and kernel version 3.0.8-gda6252b
Sound normal?
Rooted?
http://www.mediafire.com/?kfn1e6nvys663ar
Flash that.
If not...
You can open that .zip...find the bootanimation.zip
and adb push it to /data/local/bootanimation.zip
Jubakuba said:
Rooted?
Click to expand...
Click to collapse
Not rooted, but possibly heading in that direction. Just getting acquainted for now and making sure I don't need to send it back before I get too intimate with it.
Need to do some more forum searching and start sequencing out a plan. Thanks for your file link, I'll put it with my arsenal.
Hi all, I was wondering if anyone has Chad's "testing" version of Clockwork mod, and it was version 2.5.1.8. The first recovery to be able to get more than 2 touchpoints at a time?
could anyone help? searched high and low but all links are either dead or to websites that don't exist anymore,
many thanks,
Brian
-xipher- said:
Hi all, I was wondering if anyone has Chad's "testing" version of Clockwork mod, and it was version 2.5.1.8. The first recovery to be able to get more than 2 touchpoints at a time?
could anyone help? searched high and low but all links are either dead or to websites that don't exist anymore,
many thanks,
Brian
Click to expand...
Click to collapse
Try pming Chad. Also slcd or amoled screen?
Also some touch controllers seem to only work with 2 even though they are detected by the multi touch kernel as supporting more.
Sent from my Galaxy Nexus using Tapatalk
I will try to pm him and see if he will respond,
I'm unaware of how to determine my screen type, i've read many threads about it but it's hard to make clear what screen I have? if you have any information on this it would help greatly. Even if it's a slcd, some people have reported 3 working but even 3 I would be happy for the apps I use requires more than 2 sometimes like music apps, emulator and such but thank you for replying
many thanks, Brian
If you pull your battery, hardware version ADR6300 VW & ADR6300 VW2 are AMOLED, ADR6300 VW3 is SLCD.
Following your advice, it's a SLCD (I think as it was both VW beside the FCC and VW3 above it) and reading about this screen means at most 3 touch points. Even at that it's pushing it =[ but thanks all for your help though i'm sure someone else could use the information
-xipher- said:
Following your advice, it's a SLCD (I think as it was both VW beside the FCC and VW3 above it) and reading about this screen means at most 3 touch points. Even at that it's pushing it =[ but thanks all for your help though i'm sure someone else could use the information
Click to expand...
Click to collapse
I probably have the same model as you. As far as the selecting number of touch points in the kernel, mine should support more than 2 but it doesn't. I've never heard of anyone with an SLCD model get more than 2 points.
tiny4579 said:
I probably have the same model as you. As far as the selecting number of touch points in the kernel, mine should support more than 2 but it doesn't. I've never heard of anyone with an SLCD model get more than 2 points.
Click to expand...
Click to collapse
hmmm that's true though, people have been trying to get more than two on SLCD but wonder if it's got to due to the board, digitizer or screen? so lets say mine is a SLCD, if I purchase a AMOLED screen would multitouch work? as I replaced the digitizer recently due to a nasty drop?
in this thread http://forum.xda-developers.com/showthread.php?t=906721
i've seen this post? so it could be possible to get 3? http://forum.xda-developers.com/showpost.php?p=10805042&postcount=101