Related
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
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.
Ok guys let me start by saying thank you in advance. I thought I bricked my last incredible when trying to unroot it and return to stock by flashing the wrong p31.... file. I realized I had the newer slcd screen to late and had no picture when trying to turn the phone back on. All I got was the vibrate but no picture. Anyway I tried the recommendation on the forum and tried to flash it blind...... then I dropped in water! As I was doing it.
I have read and read but can't tell if I have amoled or slcd. Looking the screen with magnifier, etc. Is there a sure fire way to tell so I don't screw up an unroot if I try? I read that hardware version 0002 usually meant amoled... need more than usually! Lol.
My stats, stock: of course this is a replacement phone and the under the battery sticker that would have been on stock is not there a refurbished in the Philippine took its spot...
Dinc 2.2
2.15.00.07.28 radio
Stock kernel 26.32.17.... build 149 #1
Hardware version 0002
Hboot .92
Sent from my ADR6300 using XDA App
eraste said:
Ok guys let me start by saying thank you in advance. I thought I bricked my last incredible when trying to unroot it and return to stock by flashing the wrong p31.... file. I realized I had the newer slcd screen to late and had no picture when trying to turn the phone back on. All I got was the vibrate but no picture. Anyway I tried the recommendation on the forum and tried to flash it blind...... then I dropped in water! As I was doing it.
I have read and read but can't tell if I have amoled or slcd. Looking the screen with magnifier, etc. Is there a sure fire way to tell so I don't screw up an unroot if I try? I read that hardware version 0002 usually meant amoled... need more than usually! Lol.
My stats, stock: of course this is a replacement phone and the under the battery sticker that would have been on stock is not there a refurbished in the Philippine took its spot...
Dinc 2.2
2.15.00.07.28 radio
Stock kernel 26.32.17.... build 149 #1
Hardware version 0002
Hboot .92
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
Assuming the screen works, yes, you can tell with a magnifying glass or a SMALL drop of water on the screen. An LCD will show colored squares. The AMOLED the dInc uses will show what's called a RBGB pattern (red, blue, green, blue pattern) when viewing a white screen. Also, the backlight will be seen through a black screen on an LCD, which will be very obvious in a dark room. Again, this is assuming the device works correctly.
Easy way to tell: Hardware version 002=AMOLED, 003=SLCD.
Sent from my Droid Incredible running a random CM7 nightly.
Thanks guys so hardware =0002 for me take that to mean I have the older incredible amoled screen which is easier to return to stock right?
Sent from my ADR6300 using XDA App
take out your battery. ADR6300VW = amoled = ADR6300VW2
ADR6300VW3 = SLCD
vassskk said:
take out your battery. ADR6300VW = amoled = ADR6300VW2
ADR6300VW3 = SLCD
Click to expand...
Click to collapse
i didn't know this. thank you.
Just a note on most refurbished phones that information is not there, they placed a refurbished in " " sticker for me it says Philippines and the only information on the sticker is MEID number and couple barcode numbers.
However if you have one that hasn't been refurbished Ie: you never took your old one to verizon for a replacement or through an insurance company claim then you should have factory sticker(info) under battery.
Sent from my ADR6300 using XDA App
eraste said:
Just a note on most refurbished phones that information is not there, they placed a refurbished in " " sticker for me it says Philippines and the only information on the sticker is MEID number and couple barcode numbers.
However if you have one that hasn't been refurbished Ie: you never took your old one to verizon for a replacement or through an insurance company claim then you should have factory sticker(info) under battery.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
^ i wonder why they do that...
NP wolf!
No clue, I knew that trick by the time I got the phone in the mail that was the first thing I looked for lol. When I saw that refurbished sticker I was like da**! Lol
Sent from my ADR6300 using XDA App
SteveG12543 said:
Easy way to tell: Hardware version 002=AMOLED, 003=SLCD.
Sent from my Droid Incredible running a random CM7 nightly.
Click to expand...
Click to collapse
This doesn't seem to be true anymore if you flash the new 2.3.4 leak... I've had my inc since the day it came out and it always used to say 002 for the hardware version, but since I've flashed the new 2.3.4 leak, it now says hardware version 003... can anyone else confirm this?? FYI I flashed the one JoelZ posted
I would imagine that's because the GB leak has a sprint build.prop. Unless you changed it yourself or whoever put the rom out changed it, it will show some incorrect information.
taihard said:
This doesn't seem to be true anymore if you flash the new 2.3.4 leak... I've had my inc since the day it came out and it always used to say 002 for the hardware version, but since I've flashed the new 2.3.4 leak, it now says hardware version 003... can anyone else confirm this?? FYI I flashed the one JoelZ posted
Click to expand...
Click to collapse
Huh... That's shady lol. Weird.
Sent from my Droid Incredible running a random CM7 nightly.
msg deleted
I know I have an AMOLED screen.
But I've been seeing hardware = 0003 under MIUI ROMs and Nils' Gingerbread too, so I doubt it has anything to do with Sprint-related origins.
Hardware version 2 is Amoled and version 3 is SLCD
eraste said:
Ok guys let me start by saying thank you in advance. I thought I bricked my last incredible when trying to unroot it and return to stock by flashing the wrong p31.... file. I realized I had the newer slcd screen to late and had no picture when trying to turn the phone back on. All I got was the vibrate but no picture. Anyway I tried the recommendation on the forum and tried to flash it blind...... then I dropped in water! As I was doing it.
I have read and read but can't tell if I have amoled or slcd. Looking the screen with magnifier, etc. Is there a sure fire way to tell so I don't screw up an unroot if I try? I read that hardware version 0002 usually meant amoled... need more than usually! Lol.
My stats, stock: of course this is a replacement phone and the under the battery sticker that would have been on stock is not there a refurbished in the Philippine took its spot...
Dinc 2.2
2.15.00.07.28 radio
Stock kernel 26.32.17.... build 149 #1
Hardware version 0002
Hboot .92
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
jpradley said:
I know I have an AMOLED screen.
But I've been seeing hardware = 0003 under MIUI ROMs and Nils' Gingerbread too, so I doubt it has anything to do with Sprint-related origins.
Click to expand...
Click to collapse
On MIUI, the settings menu doesn't even show hardware version. Only place I've seen it is in one of setCPU's "about" menus, and it was reported 002 which is correct. As for nil's rom, I thought it was based off a sprint rom but that could be incorrect.
You have to look at your stats when your phone is bone stock....
0002 is AMOLED and 0003 is SLCD. However when you flash a new rom, etc whatever that rom was built on is what will show up under hardware version. So if you looked and wrote down your stats when your phone was stock and it is hardware version 0002 its AMOLED and 0003 is SLCD.
I am using Nils gingersense 3.0 ver 1.6 and under the hardware version it says 0003 but I know mine is the older AMOLED 0002, And when I flash my " stock with root" backup my hardware version shows me 0002 like when I first powered it on from verizon.
Screen size is another thing I noticed will be wrong when flashing custom roms etc. Flashed one that had my screen size at 4.3" lol I got an incredible so I know thats false... My advice to anyone would be to record all your information on a lil notepad before changing anything incase you forget.
Hi all,
I'm hoping I'm posting this in the right place and with the right format.
I have a rooted T-Mobile Samsung Galaxy S2 device, and after trying to install Villainrom 3.0.0 (VillainROM-3.0.0-signed.zip) through the Clockworkmod recovery console, it is completely bricked. Installation said it finished successfully, I then chose 'Reboot' through the CWR console, and the device went dead.
It won't turn on, or boot into recovery or download modes. I removed the battery and SIM for 10 minutes, and same results. When connecting the device to the computer, I hear the "Device failed to connect" sound. If I try to press the power button, I hear the "device connected" sound followed immediately by the "device failed to connect" sound. The fact that it is responding at all to the USB cable being connected, is the only hope I have left that I can do something about it. Odin does not show it connected though (I saw in another thread that someone was able to use it despite the device not turning on).
I would appreciate any advice before I try ordering a USB jig and / or visiting a support center and hoping they somehow replace it within warranty by making another story.
Next time you should really be careful when installing ROMs................. Make sure they are supported by your phone............... That's all the advice I can give.
Your only options now is to try a USB jig or sending it to a support center so...
Yup, you need to make sure the ROM you want is supported.. other than our dev section, everything else you will find is for the i9100.
Completely different phone.
I think your only options are jig or warranty
Sent from my SGH-T989 using XDA App
Yeah - this happens when you flash a ROM for a totally different device.
You could try flashing a T989 kernel and see if that helps - but the International SGS2 has a Exynos processor - yours is a Snapdragon - along with some other differences.
You can also try using ODIN to flash a stock tar and ROM back - it's not really bricked - but you'll need to do some reading to hopefully avoid such disastrous results again
I had a previous generic Galaxy S2 and installed roms without a problem. How come the T-mobile is a completely different device? aside from some carrier bloatware, it's basically the same hardware, no? at least everything I read led me to believe that.
How could I use ODIN when the device doesn't respond to any kind of button combo and doesn't go into download or recovery modes? is there a way to force ODIN to recognize a bricked device?
erangalp said:
I had a previous generic Galaxy S2 and installed roms without a problem. How come the T-mobile is a completely different device? aside from some carrier bloatware, it's basically the same hardware, no? at least everything I read led me to believe that.
Click to expand...
Click to collapse
The answer to your question is common knowledge and in fact has already been answered in this thread even. Le sigh.
Sent from my SGH-T989 using XDA App
TJBunch1228 said:
The answer to your question is common knowledge and in fact has already been answered in this thread even. Le sigh.
Click to expand...
Click to collapse
I appreciate everyone trying to help, but this is not very helpful. Obviously it wasn't common knowledge for me, otherwise this wouldn't have happened - and I did read up a lot about this. And where in this thread does it answer about the difference in hardware?
Please bear in mind that I'm not an android developer, so what seem like common knowledge to you about internal difference in devices is not that obvious.
How many times in these forums does it say don't flash if you don't know what you are doing. If you don't know what you are doing ask questions. Maybe bricking your phone will teach you a lesson.
are you able to go into Download mode with a USB Jig?
(you can always make your own if you can add up enough spare resistor to amount 301k)
if you can then you can try flashing the stock Odin ROMs
erangalp said:
Hi all,
I'm hoping I'm posting this in the right place and with the right format.
I have a rooted T-Mobile Samsung Galaxy S2 device, and after trying to install Villainrom 3.0.0 (VillainROM-3.0.0-signed.zip) through the Clockworkmod recovery console, it is completely bricked. Installation said it finished successfully, I then chose 'Reboot' through the CWR console, and the device went dead.
It won't turn on, or boot into recovery or download modes. I removed the battery and SIM for 10 minutes, and same results. When connecting the device to the computer, I hear the "Device failed to connect" sound. If I try to press the power button, I hear the "device connected" sound followed immediately by the "device failed to connect" sound. The fact that it is responding at all to the USB cable being connected, is the only hope I have left that I can do something about it. Odin does not show it connected though (I saw in another thread that someone was able to use it despite the device not turning on).
I would appreciate any advice before I try ordering a USB jig and / or visiting a support center and hoping they somehow replace it within warranty by making another story.
Click to expand...
Click to collapse
erangalp said:
I had a previous generic Galaxy S2 and installed roms without a problem. How come the T-mobile is a completely different device? aside from some carrier bloatware, it's basically the same hardware, no? at least everything I read led me to believe that.
How could I use ODIN when the device doesn't respond to any kind of button combo and doesn't go into download or recovery modes? is there a way to force ODIN to recognize a bricked device?
Click to expand...
Click to collapse
Hmm - well let's see... a simple Google search to compare the phones would tell you that it's definitely not the same device. A little more reading might be in order though...
1. different screen sizes
2. different SoC (system-on-chip, i.e. processor)
3. different basebands/radios
4. etc.
All of those combine to a different device.
Now as relating to ODIN - I honestly don't see why you couldn't get into ODIN. A jig might help but I doubt it.
erangalp said:
I had a previous generic Galaxy S2 and installed roms without a problem. How come the T-mobile is a completely different device? aside from some carrier bloatware, it's basically the same hardware, no? at least everything I read led me to believe that.
How could I use ODIN when the device doesn't respond to any kind of button combo and doesn't go into download or recovery modes? is there a way to force ODIN to recognize a bricked device?
Click to expand...
Click to collapse
With very little research....
Galaxy S2 (International) - i9100
Dual-core 1.2GHz ARM Cortex-A9 processor, Mali-400MP GPU, Exynos chipset
T-Mobile/Telus Galaxy S2 - T989/D
1.5 GHz Scorpion dual-core processor, Adreno 220 GPU, Qualcomm APQ8060 Snapdragon chipset
This difference in specification should be the FIRST thing keeping you away from flashing a i9100 ROM on a T989...
erangalp said:
I appreciate everyone trying to help, but this is not very helpful. Obviously it wasn't common knowledge for me, otherwise this wouldn't have happened - and I did read up a lot about this. And where in this thread does it answer about the difference in hardware?
Please bear in mind that I'm not an android developer, so what seem like common knowledge to you about internal difference in devices is not that obvious.
Click to expand...
Click to collapse
Well - how about this answer given above which does in fact provide the answer for you:
jerdog said:
You could try flashing a T989 kernel and see if that helps - but the International SGS2 has a Exynos processor - yours is a Snapdragon - along with some other differences.
Click to expand...
Click to collapse
How can you know what you don't know? I have previously rooted my galaxy S2 and installed various ROMs without a problem. I now have this new T-mobile device since I switched carriers. I could I know that what worked for my previous Galaxy S2 won't work for this one? why should I "be taught a lesson"?
I would really appreciate if someone could give me a helpful answer - I can't use ODIN to flash since I can't boot up the device in any mode. Is there any way to make ODIN recognize a bricked device? the computer does make the USB connected sound for a sec there. Please guys, anything helpful instead of telling me how "should've known", because really, if I could I would. Nobody here ever had a faulty ROM installation?
erangalp said:
I appreciate everyone trying to help, but this is not very helpful. Obviously it wasn't common knowledge for me, otherwise this wouldn't have happened - and I did read up a lot about this. And where in this thread does it answer about the difference in hardware?
Please bear in mind that I'm not an android developer, so what seem like common knowledge to you about internal difference in devices is not that obvious.
Click to expand...
Click to collapse
Jerdog covered the differences in hardware for you. In fact it was exactly above your post explaining that you were unaware of the differences in hardware. 95% of us here are not devs... All you gotta do is read. There are dozens of threads already from folks who have already made your mistake. Read read read. And if you think you've read enough, read more. The difference in processor is one of the most commonly known and discussed things about this phone. Good luck with your phone.
Edit: regarding an actual solution, just try to do a warranty exchange. Play dumb.
Sent from my SGH-T989 using XDA App
This thread happens 30 times a day, very annoying. People will never learn
Sent from my SGH-T989 using xda premium
TJBunch1228 said:
Edit: regarding an actual solution, just try to do a warranty exchange. Play dumb.
Click to expand...
Click to collapse
Thanks, will do that.
Sorry guys, it was an honest mistake. I didn't bother googling it, because I assumed it was the same hardware. Obviously, a sorry mistake, but we're all human. Thanks again to all who tried to help, sorry if annoyed anyone with my problem (and I did search the forum before posting, none of the other threads offered any solutions to my case).
Cheers
If you just assumes it was the same, that basically means you are.clueless and don't even know anything about the phone, in other words, you should not be flashing if you don't know what you are doing
Sent from my SGH-T989 using xda premium
Yup, it's unfortunate - people try to flash VR onto their device, then find it's not compatible...
If there's something I can do to the zip to prevent it flashing on these devices, I will gladly do it, but since they bear the SGS2 name, the standard check for "galaxys2" likely won't help us...
If you try the jig, it SHOULD in theory work, if the hardware is fine. But I have no experience of this, it's a case of stabbing blind in the dark
erangalp said:
Thanks, will do that.
Sorry guys, it was an honest mistake. I didn't bother googling it, because I assumed it was the same hardware. Obviously, a sorry mistake, but we're all human. Thanks again to all who tried to help, sorry if annoyed anyone with my problem (and I did search the forum before posting, none of the other threads offered any solutions to my case).
Cheers
Click to expand...
Click to collapse
Hey - we all make mistakes - and you own up to it - that's a good thing.
I wouldn't personally recommend taking it back for a warranty exchange and playing dumb. If you can go without your device for a few days go on eBay and get a jig. Try that and then flash with ODIN back to stock. It's better than driving up the overall costs for others (trickle-down) for something you did yourself.
My $0.02.
allright guys. After reading the whole thread i see this is truely crazy how much people have this probem. Yesterday i got my second one. And with my second one i have the same issues...I am pretty sure it is a software related issue:
OR
The phone's kernel is ****ed up (battery issues, bad voltage on screen)
OR
there is something wrong with the G-sensor:
Go to your screen settings, and on the bottom of the you can calibrate your G-sensor. When you do this, you see both of the green dots go insane like the screen do!
What do you think guys?
The green dots don't go insane on mine, just slightly up and down. I was waiting for something a little more interesting hehehe
twistedh said:
The green dots don't go insane on mine, just slightly up and down. I was waiting for something a little more interesting hehehe
Click to expand...
Click to collapse
Why? I'm just trying to make a statement on this problem. And try to solve this. Monday i get my third HTC One X. The first X, suffer from screen flickering, mostly on greyish fields the second one, has it too. Both HT23 devices. Both problems.
Personally i'm studying IT, so i only try to get a possible statement with the knowledge i have, and with the custom ROM flash knowledge i have during very very much flashings with my Galaxy S.
I'm just trying to get a possible solution. Is this software or hardware? I dont' know for sure. Maybe Paul O Brien can say something about this problem. I'm out of thoughts.
We don't know, some phones have it some don't. Nothing indicating any differences between phones that have it and phones that don't.
Difficult to tell at this stage. We need a brave soul to check for loose connections but I bet no one will tear their HOX apart to find out.
Knock on wood my second one has no screen strobing as of yet 1 day old so far.
Keep replacing until you get one that doesn't flicker is the only solution for the time being.
Sent from my GT-I9000 using Tapatalk 2
nikzDHD said:
We don't know, some phones have it some don't. Nothing indicating any differences between phones that have it and phones that don't.
Difficult to tell at this stage. We need a brave soul to check for loose connections but I bet no one will tear their HOX apart to find out.
Knock on wood my second one has no screen strobing as of yet 1 day old so far.
Keep replacing until you get one that doesn't flicker is the only solution for the time being.
Sent from my GT-I9000 using Tapatalk 2
Click to expand...
Click to collapse
What we need is HTC to pull their finger out of their arse, and rip one apart that was sent back doa, and then tell us what it is, tbh they probably are doing this, but need more samples of the problem to be 100% sure of it
Sent from my HTC One X using XDA