Related
[UPDATE] Fixed using method 2 in the link in post #4. Thanks a lot!!
Hi everyone, new to the forum and in need of some help please
I have a new Desire from T-Mobile UK. Branded and I assume locked, not rooted.
I attempted to debrand my phone by doing the following.
1. I already had Android SDK and HTC Sync.
2. I made a GoldCard following the unlockr instructions "how-to-create-a-goldcard" (not allowed to post link as am new forum user).
3. I ran an RRU from the pinned ROMS topic in this forum, which was RUU_Bravo_HTC_WWE_1.21.405.2_Radio_32.36.00.28U_4.06.00.02_2_release_126984_signed.exe
The flash completed with no errors.
Afterwards, the phone appears to boot up but the screen remains completely black at all times. I have tried everything I can think of, and have seen absolutely nothing on the screen at all since flashing. Pure black not even backlight.
What I have observed is:
1. On power-up, the vibration and welcome sound.
2. The hardware buttons illuminate. They time out and go off, and they illuminate again when pressed.
3. On inserting a freshly formatted SD card and turning on, waiting ages, turning off (remove battery), removing card, then viewing in a card reader, Android has added some folders to the card (.footprints, LOST.DIR, rssreader) so obviously it is booting up to some degree.
4. On attempting to flash another ROM, the tool reports the "From image version" to be 1.21.405.2 which is the one I flashed earlier, not the phone's original version.
5. Phone no longer shows up in "adb devices" when connected, although this may be simply because USB debugging isn't enabled, or because the phone will be at its start-up introduction screens.
6. There is network activity after a while, indicated by the interference on my PC's speakers.
What I have tried to do to fix:
1. Numerous reboots removing battery, SD, SIM etc.
2. Flashed the WWE 1.21 ROM again, which succeeded, but didn't fix the problem.
3. Attempted to flash the WWE 1.15 ROM RUU_Bravo_HTC_WWE_1.15.405.4_Radio_32.30.00.28U_4.05.00.11_release_122704.exe which failed with "ERROR [140]: BOOTLOADER VERSION ERROR. The ROM Update Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again."
4. Attempted to flash the T-Mobile 1.5 ROM RUU_Bravo_TMO_UK_1.15.110.11_Radio_32.30.00.28U_4.05.00.11_release_122755.exe which failed with the same error.
5. Flashed the T-mobile 1.21 ROM, which succeeded, but didn't fix the problem, and has made it slightly worse in that I don't get the welcome sound at power-on any more. I still get the vibration, the lights, the network activity, and the black screen.
6. Tried with another SD card, no difference.
Before I started debranding at all, I took a photo of the software versions screen as supplied by t-mobile, which showed as follows.
Firmware version: 2.1-update1
Baseband version: 32.41.00.32U_4.08.00.09
Kernel version
2.6.29-3cb3dfbf
htc-kernel{at}and18-2 #1
Build number 1.15.110.11 CL155070 release-keys
Software number: 1.15.110.11
Browser version: WebKit 3.1
(replace {at} with the email at symbol, new forum members aren't allowed to post these)
So in summary, I probably have the WWE 1.21 ROM working on my phone, but the screen doesn't work so I can't see it, and re-flashing doesn't work so I can't try a different ROM.
I'm a noob to debranding but am a programmer and Android app developer so feel free to get a little bit technical
Any help you can give is greatly appreciated! Hopefully I won't have to explain this to the T-Mobile support people!
Thanks!
Hi. Sorry to hear you having trouble, I'm not too sure. But sounds to me like its a display issue? You may have a Desire with the new cheaper display, not a amoled.screen? Think I remember reading in the forums blank screens and issues with roms. (please check other treads)
The good news is I think its recoverable. Sorry. I can't be of mote help.
Sent from my HTC Desire using XDA App
Thanks for the reply,
I had a better search around and found showthread.php?t=747393 which describes apparently the same problem, although I haven't messed with bootloaders. It was fixed by installing the OTA update blind by pressing buttons in the right order.
It is indeed possible I have a different screen type, or perhaps a different model of AMOLED, does anyone know how to tell the difference? I do notice the screen is more reflective than my G1, which I think is associated with AMOLEDs, but that might just be down to 2 yrs of wear and tear.
Anyway, I will try it now let you know how I get on!
Thanks!
As above you have a Desire with an SLCD screen.
You will have a HBOOT of 0.83 or 0.92 - You need a rooting and/or debranding guide for those HBOOTs. The current guides only work for HBOOT 0.80 and lower.
Here is your fix for your current problem: http://forum.xda-developers.com/showthread.php?t=748498&highlight=brick+fix+SLCD
I couldn't get the pressing buttons blindly method to work, but method 2 from dickenz's link worked a treat.
It gave me WWE Android 2.1, and I immediately got the OTA update to Froyo, WOOHOO!
Can I suggest we create a section in the pinned ROM topic listing RRUs and OTAs compatible with the new screens? That'll make it more obvious to new visitors.
Thanks for your help both of you, I'll stay around the forums!
Desire HD - Orange Branded (GSM)
Recently rooted, downgraded ROM to stock 1.35 and since doing so the SIM is no longer detected.
Installed multiple ROMS (including official) which has not resolved the problem - completed a Radio update to 26.04.02.17, still not cured.
Any suggestions/solutions I'd be grateful to hear...
Additionally if anyone believes this could have been caused by an IMEI corruption - any way to fix without returning the phone?
Just to note also the following settings are enabled and I've not yet tried a reversal: Radio S-OFF, SuperCID & SimUnlock
SIM works ok in Galaxy Tab
You may want to try putting a different SIM in your phone to see if it is detected. If it is, then maybe there's something with your current one that causes incompatibility.
Also, have you tried removing the battery to do a "cold" boot?
Loggsie said:
Desire HD - Orange Branded (GSM)
Recently rooted, downgraded ROM to stock 1.35 and since doing so the SIM is no longer detected.
Installed multiple ROMS (including official) which has not resolved the problem - completed a Radio update to 26.04.02.17, still not cured.
Any suggestions/solutions I'd be grateful to hear...
Additionally if anyone believes this could have been caused by an IMEI corruption - any way to fix without returning the phone?
Just to note also the following settings are enabled and I've not yet tried a reversal: Radio S-OFF, SuperCID & SimUnlock
SIM works ok in Galaxy Tab
Click to expand...
Click to collapse
Hi, sometimes SIM does not sit properly in the SIM holder in DHD itself. So make sure that your SIM is properly inserted and see if that helps.
Did you flash RADIO properly? I mean were there any errors?
MonsieurD - thank you for your reply.
A cold boot - would this be booting the phone whilst USB is connected with the battery removed?
Loggsie
sphuyal - thank you also for your prompt reply.
I did not receive any errors whilst flashing the radio, would you suggest trying a previous radio to the current one in use? If so can you point me in the right direction to a website.
Furthermore - what I have noted from reading other forums etc. is that perhaps I should flash the radio first prior to flashing ROM to ensure compatability any views on this would be great.
Regards
Loggsie
Loggsie said:
sphuyal - thank you also for your prompt reply.
I did not receive any errors whilst flashing the radio, would you suggest trying a previous radio to the current one in use? If so can you point me in the right direction to a website.
Furthermore - what I have noted from reading other forums etc. is that perhaps I should flash the radio first prior to flashing ROM to ensure compatability any views on this would be great.
Regards
Loggsie
Click to expand...
Click to collapse
Well flashing radio after installing custom roms would not be a problem. Which ROM you are using and what is the version of the radio? (if you flashed the one the dev mentioned in his thread then it is ok).
This is a brilliant guide on flashing radio: http://forum.xda-developers.com/showthread.php?t=896597
Did you try taking out your sim and putting it back in? Sometimes reboot helps...
I've followed the information provided here:
wiki.cyanogenmod.com/index.php?title=HTC_Desire_HD:_Full_Update_Guide
Radio Version: 26.04.02.17
1.32.405.6 Firmware
Tried taking out the SIM and reinserting with no joy.
I'm going to try your previous link tonight and will keep you updated along the way.
I followed your guide. Radio flash initially failed, after disabling Eng-OFF it was successful with no errors.
The SIM however is still not being detected - if this was to be a problem due to rooting do you believe its reversible and furthermore me using Z4Root could this be the problem?
Loggsie
I've since established inserting the SIM the correct way around helps drastically!
Hi there,
I'm been having recurring Screen of Death issues with my HTC Desire.
This is where the screen is off, but the phone still works, i.e. touch, vibration, sounds, incoming calls etc, but the screen remains off.
The phone is rooted and S-Off and using the latest stable CM7.
I have tried reinstalling the ROM after a full wipe (data, cache and Dalvik)
Tried latest CM7 nightly with the same problem.
I even tried the MIUI and Oxygen ROMs and the problem is still there.
Also, I tried installing the Load Monitor app (to prevent the device from sleeping) but that did not help. Others reported that this has helped them.
I now have a device which appears to be unusable so any help is much appreciated.
To be clear: the phone works fine but once the screen goes off it will not come back on.
Many thanks
No Expert said:
Hi there,
I'm been having recurring Screen of Death issues with my HTC Desire.
This is where the screen is off, but the phone still works, i.e. touch, vibration, sounds, incoming calls etc, but the screen remains off.
The phone is rooted and S-Off and using the latest stable CM7.
I have tried reinstalling the ROM after a full wipe (data, cache and Dalvik)
Tried latest CM7 nightly with the same problem.
I even tried the MIUI and Oxygen ROMs and the problem is still there.
Also, I tried installing the Load Monitor app (to prevent the device from sleeping) but that did not help. Others reported that this has helped them.
I now have a device which appears to be unusable so any help is much appreciated.
To be clear: the phone works fine but once the screen goes off it will not come back on.
Many thanks
Click to expand...
Click to collapse
You obviously haven't tried everything. Check my guide.
Hi and thanks for taking time to reply.
I've just tried Option 9 in your thread, i.e.:
Fixing Deep Sleep
[STEP1]- Enter dialpad
[STEP2]- type *#*#4636#*#*
[STEP3]- Go to "phone information
[STEP4]- Change "preferred network type" to GSM only, or CDMA only
But unfortunately the problem persists (I didn't try any of the other options because they are not relevant at least to this issue).
Is there anything else I can try, perhaps something more aggressive in terms of "wiping"?
Thanks again.
No Expert said:
Hi and thanks for taking time to reply.
I've just tried Option 9 in your thread, i.e.:
Fixing Deep Sleep
[STEP1]- Enter dialpad
[STEP2]- type *#*#4636#*#*
[STEP3]- Go to "phone information
[STEP4]- Change "preferred network type" to GSM only, or CDMA only
But unfortunately the problem persists (I didn't try any of the other options because they are not relevant at least to this issue).
Is there anything else I can try, perhaps something more aggressive in terms of "wiping"?
Thanks again.
Click to expand...
Click to collapse
Try different radio
Hi,
I tried to flash another radio through ClockworkMod but I get the error:
"Amend scripting (update-script) is no longer supported.
Amend scripting was deprecated by Google in Android 1.5.
It was necessary to remove it when upgrading to the ClockworkMod 3.0 Gingerbread
based recovery."
This is the same as described here:
http://forum.xda-developers.com/showpost.php?p=17311987&postcount=2163
So I then tried the fastboot method but once I issue the command adb reboot bootloader, the screen goes black and then there is no response.
I tried this twice and it's the same both times.
Any ideas appreciated as the phone is unusable at the moment.
Thanks
EDIT: I issued the command to flash the radio anyway (fastboot flash radio) even though the screen was completely dark and the radio did indeed flash sucesfully.
I checked in "about phone" and I can see the updated radio.
The radio is version 5.11.05.27 which was the last one sent with the last official HTC update.
So I rebooted the phone and...the same thing.
Once the phone sleeps I cannot turn the screen on, even though the phone itself is on.
PS: I even tried an early Ice Cream Sandwich alpha ROM and the problem persists....
Thanks.
No Expert said:
Hi,
I tried to flash another radio through ClockworkMod but I get the error:
"Amend scripting (update-script) is no longer supported.
Amend scripting was deprecated by Google in Android 1.5.
It was necessary to remove it when upgrading to the ClockworkMod 3.0 Gingerbread
based recovery."
This is the same as described here:
http://forum.xda-developers.com/showpost.php?p=17311987&postcount=2163
So I then tried the fastboot method but once I issue the command adb reboot bootloader, the screen goes black and then there is no response.
I tried this twice and it's the same both times.
Any ideas appreciated as the phone is unusable at the moment.
Thanks
EDIT: I issued the command to flash the radio anyway (fastboot flash radio) even though the screen was completely dark and the radio did indeed flash sucesfully.
I checked in "about phone" and I can see the updated radio.
The radio is version 5.11.05.27 which was the last one sent with the last official HTC update.
So I rebooted the phone and...the same thing.
Once the phone sleeps I cannot turn the screen on, even though the phone itself is on.
PS: I even tried an early Ice Cream Sandwich alpha ROM and the problem persists....
Thanks.
Click to expand...
Click to collapse
Try the latest one http://download.oxygen.im/radios/bravo.5.17.05.23.zip
Also if you can't boot fastboot with commands then just poweroff, then hold BACK and POWER
Hi Bortak,
that's the one (5.17.05.23) I already had before I downgraded.
Thanks
Bortak,
HTC have actually agreed to have a look at the handset as part of the warranty (I was unaware at the time I posted my question that the warranty is 24 months), so I will be sending it to them.
Do you know if I can use HTC's own RUU from their site on my rooted and S-off handset to return it to stock, or do I risk any damage?
(see question here: http://forum.xda-developers.com/showthread.php?p=20288444#post20288444)
[Moderators, I will close / delete one or the other thread once answered. Thanks]
No Expert said:
Bortak,
(I was unaware at the time I posted my question that the warranty is 24 months), so I will be sending it to them.
Click to expand...
Click to collapse
Really? Which country?
Do you know if I can use HTC's own RUU from their site on my rooted and S-off handset to return it to stock, or do I risk any damage?
Click to expand...
Click to collapse
If you have a goldcard/you have the RUU meant for your region, there is no risk if you follow instructions
Hi,
I'm in the UK (I believe under EU rules all electronic manufacturers need to provide 24 months though Apple I think only provide 12 I thikn).
In any case, they said OK.
If you have a goldcard/you have the RUU meant for your region, there is no risk if you follow instructions
Click to expand...
Click to collapse
I do not have a goldcard but it's definitely the RUU for my region (i.e. GB / UK).
Just one more question: can I just run the RUU directly or do I need to downgrade HBOOT etc first?
Thanks.
No Expert said:
Hi,
I'm in the UK (I believe under EU rules all electronic manufacturers need to provide 24 months though Apple I think only provide 12 I thikn).
In any case, they said OK.
I do not have a goldcard but it's definitely the RUU for my region (i.e. GB / UK).
Just one more question: can I just run the RUU directly or do I need to downgrade HBOOT etc first?
Thanks.
Click to expand...
Click to collapse
1. Is the phone on contract?
- if yes, you need to correct RUU for your network provider (NOT region - unless you bought the phone yourself), otherwise your warranty will be void
2. Since you are S-OFF, you need to flash the stock hboot first, then the downgrader, then the RUU
3. If you don't know which RUU is for you, use the 2.3.3 one
Hi and thanks,
1. Is the phone on contract?
Click to expand...
Click to collapse
No, it's an unbranded one.
2. Since you are S-OFF, you need to flash the stock hboot first, then the downgrader, then the RUU
Click to expand...
Click to collapse
Can I confirm these steps are right?
(i) Flash Stock Hboot
Verify the MD5SUM of the file
Flash HBOOT with phone in fastboot mode (Back+POWER) -> 'fastboot flash hboot bravo_alphaspl.img'
'fastboot reboot-bootloader'
'fastboot erase cache'
Do I need to reboot after this?
(ii) Downgrader
As above but using the bravo_downgrade.img file.
So I do (i), then immediately (ii), then the official RUU.
Correct?
Many thanks
EDIT: the reason I'm asking about the correct order is because this post:
http://forum.xda-developers.com/showpost.php?p=16686095&postcount=9
says that the Downgrader needs to be run first and then the stock flash, which is why I'm a bit confused.
No Expert said:
Hi and thanks,
No, it's an unbranded one.
Can I confirm these steps are right?
(i) Flash Stock Hboot
Verify the MD5SUM of the file
Flash HBOOT with phone in fastboot mode (Back+POWER) -> 'fastboot flash hboot bravo_alphaspl.img'
'fastboot reboot-bootloader'
'fastboot erase cache'
Do I need to reboot after this?
(ii) Downgrader
As above but using the bravo_downgrade.img file.
So I do (i), then immediately (ii), then the official RUU.
Correct?
Many thanks
EDIT: the reason I'm asking about the correct order is because this post:
http://forum.xda-developers.com/showpost.php?p=16686095&postcount=9
says that the Downgrader needs to be run first and then the stock flash, which is why I'm a bit confused.
Click to expand...
Click to collapse
Yup, that sounds correct.
bortak, worked perfectly and was able to return device to stock for repair by HTC under warranty.
It turns out the Sleep of Death was a faulty screen.
Thanks.
Hi,
Having gone into hboot for the first time i notice that both radio and OpenDSP have "INVALID-VER-INFO" beside them.
Is this correct on an unmodified phone.
I've done a quick search but couldnt find anything.
I have hboot version 3.16.0.000
I have this also,
I'm using a stock htc one m8 from Vodafone.
The os is: os-1.54.161.5. Boot dated Mar 22 2014,00:08:55.0
EtA
Ethel the Aardvark said:
I have this also,
I'm using a stock htc one m8 from Vodafone.
The os is: os-1.54.161.5. Boot dated Mar 22 2014,00:08:55.0
EtA
Click to expand...
Click to collapse
also have this gonna try rolling back roms thru twrp backup to see if anything related to latest rom flashed will report back
Any updates on this topic? I just bought this phone and been using it for about 2 weeks. I went into the HBOOT to see what differences there were from my previous phone and noticed the invalid version on the radio and opendsp. Again, completely stock unmodified phone.
That is the TWRP recovery bug..are u all install the twrp recovery or not?
Edit: I read it again,so u all using stock rom,Idk what caused it now
Sent from my HTC One_M8 using Tapatalk
hdorius said:
That is the TWRP recovery bug..are u all install the twrp recovery or not?
Edit: I read it again,so u all using stock rom,Idk what caused it now
Sent from my HTC One_M8 using Tapatalk
Click to expand...
Click to collapse
I just went into recovery for the first time on my new m8 stock and unmodified. I see the same thing. I'm in T-Mobile
Same thing here. Happened after 4.4.3 update. Stock international M8. I wonder if it has anything to do with the battery drain introduced with the update - I barely get 12 hours of usage hence, instead of 18.
shirreer said:
Same thing here. Happened after 4.4.3 update. Stock international M8. I wonder if it has anything to do with the battery drain introduced with the update - I barely get 12 hours of usage hence, instead of 18.
Click to expand...
Click to collapse
same for me here
I noticed this on my phone today too. My phone is a completely stock verizon one m8.
My phone is not yet a week old.
Hi Guys,
which firmwares do you have. I'm running 2.22.401.4 in bottloader the hboot entries are the following:
CID-HTC__102
HBoot-3.18.0.0000
Radio-1.19.21331147A1.09G
OpenDSP-v38.2.2-00542-M8974.0311
Even after performing s-off they didn't change
________________________________________________________________________________________________________
HTCOne M8 Gunmetal: Sunshine S-Off, firmware stock 2.22.401.4, rooted with Chainfire SuperSu, CID HTC__102
HTCOne M8 Silver: HTCDev Unlock, S-On, ARHD/ViperOne (M8) (ever switchin'), firmware 1.54.401.10, CID HTC__102
Same here i am rooted and using TWRP recovery also have the invalid message like the OP so is this normal or something gone wrong somewhere ?
wakers said:
Same here i am rooted and using TWRP recovery also have the invalid message like the OP so is this normal or something gone wrong somewhere ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=54669689&postcount=11
tonnytech said:
http://forum.xda-developers.com/showpost.php?p=54669689&postcount=11
Click to expand...
Click to collapse
Thanks i also went S-Off over the weekend (sunshine) but hadn't noticed the radio and stuff had changed
hi guys,
first off, thanks to everyone contributing to this forum, I've been able to find some truly useful help in here
Has anyone found a solution to this thread? My m8 has just changed for no apparent reason to "invalid-ver-info". I don't know how important the RADIO AND OpenDSP info is when it comes to un/re-rooting.
As it happens, I did take a photo of this info the day before it happened with my M7 ..will that be of any use to me?
Also, what information from the boot or software info, should NOT be shown on the internet E.G due to privacy/security reasons.
Thanks
TW
tw10 said:
hi guys,
first off, thanks to everyone contributing to this forum, I've been able to find some truly useful help in here
Has anyone found a solution to this thread? My m8 has just changed for no apparent reason to "invalid-ver-info". I don't know how important the RADIO AND OpenDSP info is when it comes to un/re-rooting.
As it happens, I did take a photo of this info the day before it happened with my M7 ..will that be of any use to me?
Also, what information from the boot or software info, should NOT be shown on the internet E.G due to privacy/security reasons.
Thanks
TW
Click to expand...
Click to collapse
you can post fastboot getvar all (minus your Serial no. and IMEI)
nothing on the bootloader is secret
as said above. You need to provide more information to solve your issue.
ok, well here's what I have for you..if you need anything else, please tell me(see attached).
I was thinking about setting this back to stock rom, but I can't seem to find in here...do I have any possibilities?
thanks
tw10 said:
ok, well here's what I have for you..if you need anything else, please tell me(see attached).
I was thinking about setting this back to stock rom, but I can't seem to find in here...do I have any possibilities?
thanks
Click to expand...
Click to collapse
Does the phone work ? do you have stock recovery ? Have you do a normal factory reset ?
yes the phone works but not the top speaker(for what ever reason) Hence I want to send it in for repair(if possible, still 18 months guaranty).
I don't believe I have a stock recovery(I'm too new to this game to really know), there is a twrp backup, but whether it's the original or not(I doubt it) because nothing changed as far as the boot or software/firmware version is concerned when I executed the recovery(only the basic content) and the date of the backup is just one week prior to when I purchased it!?!? which makes me believe that the original was overwritten.
no I haven't, the reset was apparently done by the seller.
tw10 said:
yes the phone works but not the top speaker(for what ever reason) Hence I want to send it in for repair(if possible, still 18 months guaranty).
I don't believe I have a stock recovery(I'm too new to this game to really know), there is a twrp backup, but whether it's the original or not(I doubt it) because nothing changed as far as the boot or software/firmware version is concerned when I executed the recovery(only the basic content) and the date of the backup is just one week prior to when I purchased it!?!? which makes me believe that the original was overwritten.
no I haven't, the reset was apparently done by the seller.
Click to expand...
Click to collapse
Well if you have TWRP you can try a format data, But this will completely wipe the phone all your data and the system will be gone.
you would then flash a stock Rom back to the phone from the ext_sd card
To find the correct stock rom you need your phones basic info from fastboot getvar all
you can post the results here but exclude your serial no. and IMEI
Hello,
I have just got my HTC One X, and unfortunately it seems that it's some kind of chinese phone, and I'm now trying to make it work the right way. In fact i have found out that it isn't even One X, but One XT (chinese version).
First Problem(screen):
I have problem with my screen. It just acting weird sometimes. This shows exactly my problem: youtube[dot]com/watch?v=T4GUnlMKTds (sorry that i'm overriding spam prevention, but i cant explain this problem better). I have contacted HTC support but they told me that my IMEI isn't even in their database(probably it had motherboard replacement), and they can't help me. It looks to me like problem with a badly connected wires from display. Do you think that disassembling phone, and checking these wires could help?
Second Problem(hboot):
This phone have some weird ROM (version 2.10.1403.7) and i found out that to flash CyanogenMod i need at least hboot 1.28. But... I have 1.12, and because my CID is HTCCN704, I'm not sure i can change hboot to newer version. I have read that i need proper CID to flash hboot, but what will happen if I just flash any hboot i find? Will changing CID to SuperCID allow me to change hboot?
Third Problem(SIM):
Sometimes my HOX thinks that my SIM is removed. I have to remove it, and put it back in to make him recognize my SIM card. Is it possible that it's just software issue, and changing ROM will fix that?
And the last problem(3g):
My phone can't connect to 3G, It just uses EDGE(I even tried to use *#*#4636#*#* menu to change it manually to use WCDMA, no luck). Is it fault of phone's origin or is it possible to fix that?
Give me a picture of your bootloader please !
Mr Hofs said:
Give me a picture of your bootloader please !
Click to expand...
Click to collapse
Here it is. imgur[dot]com/uVJcYAH
Hmm not sure if our firmwares supports the Chinese version ? Can you install ics based roms from this forum ? I mean are those working ?
If so you can try to flash the 3.14.401 standalone firmware to upgrade the hboot to 1.39 and install any rom you like.
Read up in here
http://forum.xda-developers.com/showthread.php?t=1957376
It's all explained there how to do it.
Mr Hofs said:
Hmm not sure if our firmwares supports the Chinese version ? Can you install ics based roms from this forum ? I mean are those working ?
If so you can try to flash the 3.14.401 standalone firmware to upgrade the hboot to 1.39 and install any rom you like.
Read up in here
http://forum.xda-developers.com/showthread.php?t=1957376
It's all explained there how to do it.
Click to expand...
Click to collapse
Thank you. I'll try it.