Related
Hey guys, been awhile
Finally upgraded from my Stellar (Kaiser) to HTC Desire a couple of months ago but was resisting rooting it as i believed it spoilt my Kaiser (then decided it was just crap.)
Anyway, I hate branding + i wanted Froyo, so i've been playing with my Desire today & I've made a gold card, ive followed the guide via dev forum which was brilliant.
I was expecting a blank slate to install a selected Rom from but to my surprise, found it had a rom after the rooting process, So i figured this was a Stock rom (just what i wanted), tried to Update, downloaded, rebooted, progress bar, few seconds later a red question mark appears & it reboots again.
So i assumed maybe there was something limiting about rom installed, so i downloaded....
"RUU_Bravo_HTC_Europe_1.15.405.1_Radio_32.30.00.28U_4.05.00.11_release_121684"
and running the exe file i end up going through the standard RCC routine & getting an "Error wrong bootloader version use the correct version" message.
Any suggestions?
I've probably missed something obvious, but ive been searching & trying for a couple of hours now so if anyone can point me in the right direction from here would be great
Thanks
Edit: Just noticed posts saying about using the gold card to do updates, i shall try that & post back.
Edit 2: Tried using gold card + different rom (Stock WWE) seemed to do the trick, don't know if that was the right thing to do but it certainly worked, OTA Froyo downloaded & installed too.
This is my first post and I was wondering if anyone can help.
I have an incredible, 2.2, rooted, with Rom Manager. I flashed the lastest recovery through Rom Manager but when I try to boot into recovery the screen stays black with a thin white line on both sides. I had some backups from another Dinc I had and took a chance at a restore from one of my older Roms. Although the screen stayed black it did load the backup so my recovery appears to be working fine only I can't see it.
Doing this before I am scared if I load a bad rom or something and get locked up I won't be able to see the recovery to restore my backups. I have tried older recoveries through Rom Manager with the same problem however when I flash RA_GNM Recovery v1.7.6 it works perfectly. Only problem is Rom Manager won't use that.
Any suggestions would be greatly appreciated.
Search for slcd recovery.
Sent from my ADR6300 using XDA App
ok now I am really confused. I research the slcd and not quite sure what I have or looking at. How do I know? My old Dinc was literally only about a month older than my previous one. Can you give me a brief "Dumbed Down" version of what exactly this is?
Sorry to be such a newbie.
mmjets said:
ok now I am really confused. I research the slcd and not quite sure what I have or looking at. How do I know? My old Dinc was literally only about a month older than my previous one. Can you give me a brief "Dumbed Down" version of what exactly this is?
Sorry to be such a newbie.
Click to expand...
Click to collapse
From what you're describing, your phone has a slcd screen, not amoled. As such, you're going to have a few issues here and there with recoveries as well as ROMS (due to your hardware not being supported by the included kernel). Search the forums for slcd and you'll see suitable workarounds for this.
To see what screen you have... Menu > Settings > About Phone > Hardware Version. If yours is 003, you have a SLCD screen.
Anyone who has the.new guy Rom ..is there a way to get the HTC pot penguin to as my boot image. That penguin is great lol
Sent from my ADR6300 using XDA App
Just incase anyone is having this problem I did find a site with a fix. Download the file, change the name and flash through hboot. It has worked for me and now I can get into recovery. Here is the link:
**Sorry the site wouldn't allow me to post the link***
Only problems I have now and I am hoping someone can help is that I can't seem to install any custom roms that don't have sense. When installing MIUI or CyanogenMod, etc I get locked up on the white HTC screen.
Anyone know a solution?
http://www.incredibleforum.com/foru...nly-see-black-screen-white-bars-recovery.html
That has the custom recovery you need for an slcd screen. I used that exact dl link to get the image. Then i used the unrevoked 3.21 tool to set it to flash a custom recovery then let the tool run. All went flawlessly
*Edit sorry i didn't see you fixed it. As far as cyanogen mod goes, I know it doesn't work with slcd screened incs because we have different display drivers. I believe that is true for all aosp roms. If you want a vanilla feel go with skyraider vanilla 3.0. It works perfectly for me
Thanks for posting that link and the help. I will keep checking to see if a solutions for slcd screens comes around so that I can install some other roms.
I just hate that I thought I upgraded my inc and as it turns out it was probably a downgrade.
To my understanding, I believe all roms work except aosp roms. I remember reading somewhere (but don't remember where) that they were working on a fix. So maybe it'll come before you know it
Koush's test #2 kernel works fine and will boot aosp on my Slcd.
Just wanted to let you know I found a way to make MIUI and cyanogen work on a slcd Dinc. I found the fix in one of the forums so I don't want to take any credit for it but it worked for me so I wanted to pass that info along to anyone else having the same issue.
I downloaded the Koush test kernel from Rom Manager, then I flashed the MIUI rom. Once flashed it gets stuck on the white HTC screen. I pull the battery, go to recovery, and then open zip from SD card. I find the Koush kernel, install, and reboot and it has worked for everything I have tried so far (MIUI and Cyanogen).
Hope that helps someone.
mmjets said:
Just wanted to let you know I found a way to make MIUI and cyanogen work on a slcd Dinc. I found the fix in one of the forums so I don't want to take any credit for it but it worked for me so I wanted to pass that info along to anyone else having the same issue.
I downloaded the Koush test kernel from Rom Manager, then I flashed the MIUI rom. Once flashed it gets stuck on the white HTC screen. I pull the battery, go to recovery, and then open zip from SD card. I find the Koush kernel, install, and reboot and it has worked for everything I have tried so far (MIUI and Cyanogen).
Hope that helps someone.
Click to expand...
Click to collapse
Really? My post above says that.
Your kidding right?? i didn't see your post as it was on page two so my apologies. I didn't mean to steal any of your credit!!! lol. I am just trying to help others out.
Hi guys, I've had a Bell-branded Desire Z (on AT&T's network) for some time now, but I've never gotten around to rooting / flashing a different ROM on it. Since I have some free time this weekend, I figure I'll finally tackle it. Have a few general questions though:
1) Is the method listed in the guide: http://forum.xda-developers.com/showthread.php?t=928160 still the best method for rooting a desire Z? I've heard bad things about visionary, but every rooting method I've read seem to involve it in some way.
2) with S-OFF, am I free to flash any Desire Z / G2 ROM? or will only certain ROMs work with a Bell Desire Z? Any specific recommendation on ROMs? I'm planning on trying out CM7, then going from there
3) What is the best method for backing up my current image + a few other things (mostly contacts and SMS)? Titaniumbackup gets thrown around a lot, but I only have a handful of apps, and really would rather just redownload them then go through the trouble of backing them up
Thanks
http://wiki.cyanogenmod.com/index.php?title=TMobile_G2:_Rooting
that is going to be your safest way to root your vision. eventhough this is longer, there is a lot less chance of bricking your phone. the one you listed is very simple to do, but runs a high risk of turning your phone into a paper weight.
when you do have your phone completely s off, you now have every right to flash kernels, roms, and other things. you can find all of the things i just listed over in the development forum on the g2/desire z. download rom manager from the market. that allows you to back up your current rom, flash the latest recovery and so on. it just allows you to not have to manually install everything. it has the popular g2 roms under the "download rom section".
in terms of backing up everything, there are a few different options. every contact to save is linked to your gmail account, so whatever rom you flash and load youll always have those contacts coming with you. thats the beauty of google and gmail on a android device! but with rom manager, you can back up your current rom and image with that app and save it to your sd card. BEFORE YOU FLASH ANY ROM, OR BEGIN TO START TRYING OUT ROMS, BACK UP YOUR STOCK ROM. whenever i got my g2 when it first came out, i made a nandroid backup of my stock rom and i still have it. when i originally backed it up, i just named it "stock" and havent messed with it since. i just know that i have the stock image(it helps me sleep at night). jk, heh. for your text messages and stuff, download sms backup from the market and you can back everything up through that. all of the apps that you download, including the paid ones of course, travel with you between roms, etc.
i hope i helped ya out, and i wish you luck. if you have any other questions, just shoot me a private message!
Thanks for that;
I actually went ahead and used that method in the guide since upon further research, it seems that visonary was only causing issues when it was use for perm root; temp root, which is what that method uses visionary for seems to work fine.
So did that, reboot into the bootloader, confirmed that I had S-OFF on the first line.
Installed ROM manager from the market
Flashed Clockwork recovery
Booted into recovery and did a system backup to SD card
Rebooted and decided to download the Virtuous ROM from ROM manager
Told it to reboot into recovery and flash that image, wiping all data and settings
Got stuck on an bootup loop (HTC logo + start up sound -> black screen -> HTC logo + startup sound ad infinitum)
Rebooted into recovery, and did a restore from the backup (whew)
Phone seems to be working fine now
Now I'm trying to figure out what went wrong... any ideas?
K, I redownloaded virtuous from XDA, checked the MD5, and tried to flash it again.
Same problem, infinite loop on startup screen.
Do i need to flash the engineering hboot? I was under the impression that that wasn't necessary for using custom ROMs.
Still can't figure out what's wrong.
did you debrand? http://forum.xda-developers.com/showthread.php?t=835777
Have you tried flashing through CWM directly? I really don't like ROM Manager for flashing new ROMs and seems to oversimplify the process to allow green users to get on the flashing wagon.
I would boot into CWM (camera + power i think) and do a complete wipe + flash from in there. I have never had an issue with doing things directly from recovery and I have a Bell DZ as well. It's long since lost it's blue and white colours, but that was it's origin
Have fun!
Im new to this stuff here, and i DO want to learn about it as this stuff is very interesting to me! Technology is something i learn very quickly if im directed in the correct direction
The question i have here is about my Desire Z ( Bell Cannada ).
A few months ago we received a OTA update. So its currently running on Android 2.2.1 : Build - 1.84.666.2 CL322105, and its SUPER slow! Is it still possible to root this version?
I want to install the Gingerbread version on my phone, but i cant find instructions to root this OS version to be able to do so.
Or should i wait till the Official gingerbread Os to come out for our phones?
Ive been searching every where's for this info and everything i find is all back dated to last yr and nothing up-to-date after the OTA.
I hope this question is not TOO n00bish as i tried to search every where for it, and ether i could not find it or i did not enter the correct word search to get a result i needed.
Thanks in advance!
Andrew
Edit: NVM my question here.... i have finally found an update post within the wiki ( April 1 2011 )
Sorry for a useless post!
Thank you all for your efforts in posting in this forum! Very informative!
Athrun88 said:
Have you tried flashing through CWM directly? I really don't like ROM Manager for flashing new ROMs and seems to oversimplify the process to allow green users to get on the flashing wagon.
I would boot into CWM (camera + power i think) and do a complete wipe + flash from in there. I have never had an issue with doing things directly from recovery and I have a Bell DZ as well. It's long since lost it's blue and white colours, but that was it's origin
Have fun!
Click to expand...
Click to collapse
heh. that actually worked. Flashed directly from CWM recovery and it booted up with no issues.
Guess I know not to flash from ROM manager anymore
Thanks.
deaththeorist said:
did you debrand? http://forum.xda-developers.com/showthread.php?t=835777
Click to expand...
Click to collapse
You do not need to debrand to flash custom ROMs to the Bell Canada Desire Z.
makken85 said:
heh. that actually worked. Flashed directly from CWM recovery and it booted up with no issues.
Guess I know not to flash from ROM manager anymore
Thanks.
Click to expand...
Click to collapse
Interesting, I've flashed many ROMs from ROM Manager on my Bell Canada DZ, and never had an issue. That said, flashing from recovery is really not any harder, so if it works, it works.
redpoint73 said:
Interesting, I've flashed many ROMs from ROM Manager on my Bell Canada DZ, and never had an issue. That said, flashing from recovery is really not any harder, so if it works, it works.
Click to expand...
Click to collapse
Yeah, I assumed that flashing from ROM manager just meant that it rebooted to recovery and flashed it from there. I guess there is a difference.
Either way, been playing with Virtuous 1.0.2 for a few days now, really like this ROM, but I'm itching to try out something different now. Man, I can see this is going to develop into a time consuming hobby.
Plus, I'm going to need a bigger SD card to store all of these ROMs + backup =X
Oh, another noob question; I've come across a few zip files that included a system folder and an META-INF folder. How exactly do I install these?
G2 only works with at&t
alright here it is my t-mobile G2 won't connect to the t-mobile network at all, I've went through 3 SIM cards because this thing use to kill the SIM card from working on other t-mobile phones and it works perfectly fine on at&t network. so I've unlocked so it will work on at&t just to see if it would work. so i gave p and bought a MT 4G, but i still want to know if the G2 is fixable because I'm just about ready to throw in the towel this is what I've tried to resolve the problem called t-mobile they ended up saying just return the phone but i can't since i didn't buy it from them. Called them again got the unlock code. I've flashed the radio a few times. I've also just got the leaked 2.3.3 update and nothing has worked. It find t-mobile network but says your SIM card isn't allowed to connect to this network then after trying again it says unable to connect to network please try again later.
Just so frustrating i don't know what to do just about to say forget it. this thread is my last resort.
also i still have S-OFF
i used this method on my G2 just yesterday and put on CM7.0.3. the only issues i came across were because i restored everything (should have just done apps and app data) using Titanium, which put me in a boot loop. I'm dumb, so i did it twice before i figured out what was the problem. the thread has a comment about how Visionary is dangerous, but the OP responded that since it is only used to gain temp root, there should be no problems.
So I was trying to put the new 7.1 Cyanogen Mod on my Defy
where should i start lol....
so i had a type of clockwork mod, but i couldnt boot into (except from an app i had) and it didnt say clockwork mod when i did but it had ALL the same features as CWM... i used this method because i was having trouble putting CWM on my defy...
so anyways, that seemed like it would work fine, and all the steps did in fact work flawlessly, when it came to flashing Cyanogen, I noticed it only took like 5-6 seconds flat, seemed odd, and during reboot it just froze at the CM logo (said Google, the 1st O had a motorola symbol instead of a O, and the 2nd O had the little android skater guy in it)
keep in mind i cannot boot into clockwork, so basically i had a bootloop it seemed. So i found another tutorial for flashing the phone back to a regular firmware using RSD lite, (used RSD Lite 4.9 and tried ALL the 2.1 and 2.2 stock roms for US)
every time it seemed to work but upon reboot it would just stay black, and white light at top was on, could not boot phone at all (not into bootloader or recovery) and it only shows anything when i plug it into usb (the white light at top comes on)
ok so i read on that tutorial at the bottom a few people had the same brick issue, and a guy figured out that a specific version and the 5.3.1 RSD Lite (i tried using the US roms again, still didnt work even with 5.3.1) and it worked! but now i am stuck at a vodaphone version (i think it was vodaphone, it has a red motorola boot logo now)
ok i think i summed about everything up that happened
now for the questions!
I would like to get the new cyanogen but i do not want to end up with a non booting phone again, and I am not sure how to go about it with my new rom...
im somewhat new to this (have rooted and hacked tons of phones, but the flashing thing is new to me)
so can somebody help me out? i DO NOT want a brick, but i want the new Cyanogen (or at least the original US ROM!)
ANY HELP GREATLY APPRECIATED! THANK YOU! IF YOU NEED ANY MORE INFORMATION PLEASE LET ME KNOW AND I WILL PROVIDE IT!!!
as long as you didn't flash a full gingerbread sbf you can definitely go back to stock US rom or CM7.... ALWAYS WIPE FROM RECOVERY before you flash a sbf..
Next time install bootmenu and you can access custom recovery in the event of a bootloop! Only flashing sbf will remove bootmenu!
P.S. bootmenu includes custom recovery aka CWM
If I were you I would root the rom you are running, install bootmenu, enter custom recovery, WIPE DATA/CACHE, then flash CM7
If you want to go back to stock US rom: WIPE DATA/CACHE from stock recovery, pull battery, re insert battery holding volume UP to enter bootloader then flash sbf....voila
well like i said my computer is giving me problems (or perhaps its not even the computer), ive tried to get bootmenu to install, i dont understand why its having problems, as ive rooted phones on this computer, and adb executes perfectly find, but when i try to run ANY adb commands (after running the exe in CMD), it gives me the ADB IS not a recognized command or whatever....
so I have to tell you i am not sure where to go from here...
i followed the
/wiki/Motorola_Defy:_Full_Update_Guide (wouldnt let me post full name because i havent posted 8 times yet *sigh*)
guide for installing the bootmenu, and like i said adb doesnt function... i even let it fully update, instead of picking the 2 that it needs for adb, and it took a while, but worked perfectly, and even worked flawlessly during the test afterwards, it shut down and started adb shell or whatever it says, and had no problems, but when i run cmd and try to acctually use it (like the guide shows you specifically for the defy) it doesnt work...
SO IS THERE ANOTHER METHOD OF INSTALLING BOOTMENU AND CWM???
because i tried ROM manager and of course it says it cant install CWM to the defy, and has to be done manually, which is what brought me here... would love to try the new gingerbread, very sad my Dell Streak cant get it, so this is my next best thing... i even ordered a new earpiece to fix the notoriously defective one (mine is out, like everybody elses lol)
so again any help appreciated
if it helps here is my phone info
System version
Version.34.904.4.MB252VF360Blur.Vodafone.en.ES
Model number
MB525
Android version
2.2.2
Baseband version
EPU93_U_00.59.02
Kernal version
2.6.32.9-gb08c3c8
[email protected] #1
BPflex version
USAJRDNEMARAB1B8VFES03A.0R
APflex version
GAS_EMEA_USAJRDNFRYOVFES_P028
Build number
JOREM_U3_3.4.2_179-4.4
Well I used to install bootmenu using adb but lately I'm just lazy LOL. Now I just install it from market just search defy 2nd init or just search defy and you will find one called defy 2nd init. Install it and run it, then from within the app install bootmenu!
This is definitely the "easy" way to install bootmenu!
P.S. They recommend rebooting your phone twice before using bootmenu after it is installed. Then reboot again and when the blue LED flashes press volume DOWN to enter bootmenu..... GOOD LUCK post back with your success!!
P.P.S DON'T install any other version of CWM after installing bootmenu as this will screw it up. CWM is included with bootmenu
WELL LOOK AT THAT i may have figured something out by that message you posted
so i remember installing 2nd init already... lmfao... and i do recall a blue light blinking once when booting my phone, is this normal or only when bootmenu is on the phone? i may have just not been booting into CWM the right way hence i didnt think i had it
so is that true? is the blue light only when bootmenu is installed?
and how do you boot into bootmenu?
Untraumatized said:
so is that true? is the blue light only when bootmenu is installed?
and how do you boot into bootmenu?
Click to expand...
Click to collapse
Yes.
Press Vol- as soon as you see the blue led.
Sent from Android 2.3.7
ok im gonna try and do it all over and see what happens
kinda nervous haha
but anyway, im trying to root (superoneclick said it worked, busybox installed and i have superuser, but no root access... so i am running gingerbreak right now to see if it works)
and when im done....
i download 2in it or whatever its called xD and then get ROM manager and try to flash CM7 correct?? can you give me a little better detailed step by step
(and by the way gingerbreak still says rooting ... running exploit ... so im not sure if its just taking a while or is stuck... ill post in a few minutes and let you know what happened)
assuming it doesnt work, what should i do?
just like ryan8r said press volume DOWN when blue light flashes. Then select recovery by using the volume rocker to move selection up or down and pressing power button to make your selection. Next choose stable recovery and your in
---------- Post added at 12:30 AM ---------- Previous post was at 12:27 AM ----------
you need to reboot after rooting to get root access! and NO DO NOT USE ROM MANAGER. just download the cm7 .zip put it on your SD and go into bootmenu then recovery then stable recovery. Wipe data/cache. Then choose install zip from sd card, then choose select zip from sd card then select your cm7 .zip. Then flash gapps after it finishes
if you don't flash gapps you will not have market
sorry maybe i should have explained better, i did get a blue light, before i bricked and then finally got it to start back up with the vodafone flash, the blue light doesnt come on anymore...
and gingerbreak didnt work, so im stuck without a root, i need root to get 2nd in it so i can get CWM and then get CM7
so right now my only delay is getting this damn this rooted, i dont even remember what i rooted it with to begin with, been a while, im trying superoneclick 1.7 because i used to have problems with 2.1.1, and this time (instead of "working" and not showing any errors) it just crashed, so should i try it once with 2.1.1?
and if that doesnt work how should i root it?
like i said everything worked, i have busybox, superuser, i even set superuser to automatically ACCEPT any requests, and still not working... no root...
Reboot to get root access
hmm did you mean for superoneclick or gingerbreak?
i believe i tried rebooting after both but ill try just to make sure
I have always used SuperOneClick 1.6.5 with NO problems ever! Maybe the sbf you flashed gives you troubles. If all else fails try wiping and reflashing a different sbf like nordic or cee. I ALWAYS have to reboot after rooting to get root
tried to edit last post but it didnt work?...
anyways!
yes that worked reboot gave root access, so correct me if im wrong
now i download 2nd in it (and run right?) and then ROM manager after im down with 2nd in it (and should i try to boot into CWM to make sure 2nd in it is working?
read my previous post #8 DO NOT USE ROM MANAGER and DO NOT INSTALL ANY OTHER VERSION OF CWM after you install 2nd init
---------- Post added at 12:55 AM ---------- Previous post was at 12:53 AM ----------
Booting into CWM is done by entering bootmenu at boot by pressing vol- when blue light flashes and then selecting recovery
ok so no ROM manager, got it
i have 2nd in it installed now and i just tested it, opened into bootmenu beautifully
let me read what you posted to see where to go from here
edit:
ok can you please give me the link i need for the new CM7 (for defy of course) and a link for the Gapps ill need? thanks in advance for the help!!
edit AGAIN:
can you give me a step by step of the installation of CM7 and gapps install, sorry if im making you repeat yourself just want to make sure i dont mess this one up
almost done just need a little more help!
can somebody give me a link to the new cm7 (for defy of course) and a link to the Gapps? i found the link for the cm7 but cant find the Gapps, and i would rather go with links from people who have been there ^^
sorry for double post, just really need some help here!
edit:
found the links xD dont call me stupid! lmfao
zyxwvut said:
just download the cm7 .zip put it on your SD and go into bootmenu then recovery then stable recovery.
Click to expand...
Click to collapse
somebody please help me out, he said go to recovery > stable recovery
but my only options after recovery are custom recovery or stock recovery
which one should i do?
sorry I had to run somewhere!! Go into custom recovery then stable recovery!
Depending on which version of CM7 you want ie:Quarx's RC1.5 or official CM7 You will find both in the development section here. Both have links to gapps
Quarx's http://forum.xda-developers.com/showthread.php?t=1033654
Official http://forum.xda-developers.com/showthread.php?t=1297559
Have fun!
---------- Post added at 01:51 AM ---------- Previous post was at 01:47 AM ----------
Quarx is the original dev who brought us CM7 for our defy's
The official CM team just released theirs a couple days ago
Both are great ROM's try em out for yourself. I just switched from Quarx's RC 1.5 to Official just today and have had no problems so far. RC 1.5 has the option of 720p video recording if you have RED lens
haha thanks a ton, i acctually figured it out and got flashed before i saw your last post ^^ but thank you so much, wouldnt have figured it out without you guys lol!
everything seems to be running flawlessly, gapps and all
and it seems much quicker and everything is just nice looking, huge improvement from 2.1-2.2 for SURE, im already stoked, gonna have to let my girlfriend rock the Streak 5 for a while, so i can break in this new ROM ;]
just 2 more questions if i can!
1. i was wondering what i should use to overclock, i used Milestone Overclock on the stock ROM and it worked very well, but i am curious if there is anything better i can use (or if i should just use Milestone again)
2. i ordered a replacement earpiece speaker thing for the defy (im not too inexperienced with hardware fixes, i have replaced screens and such, nothing a simple DIY youtube video cant fix) but I am just curious how hard it is to fix? just figured you might now, considering its such a common issue with Defys
AGAIN THANK YOU SO MUCH! LOVING THIS CM7 (btw 1st time ive acctually flashed a custom rom!)
Well CM7 is already overclocked to 1000 Mhz. You can control this in bootmenu under CPU settings. I recommend adjusting the vsel settings to improve battery life. Although battery life is great right out of the box
I run vsel 1 at 20, vsel 2 at 32 and vsel 3 at 56 300,600,1000 respectively. Play around and see what works for you
hi
ive done a search and read the thread in the developer section, but it wont allow me to post on that as i havent contributed enough posts yet.
im trying to fix my wifes phone, and have asked on the androidforums about this and been pointed here. basically, theres a glitch on some One Xs where the picture is green when the flash is used. this is the thread ive been reading
HTML:
http://forum.xda-developers.com/showthread.php?t=2082782&page=5
for several hours last night i muddled my way through unlocking the bootloader and then rooting the phone, and installed viper rom and rebooted fine. i then installed the 'green tint fix' zip from sd card in recovery. once id done that tho, it prompts for reboot, but gets hung up with a system fault and wont finish booting. i then have to do a clean wipe and restore my backup (so no green tint fix is ever capable of being tried out)
could anyone help me get round this please?
thanks a lot
ive just found out my mate has an HTC One X too, but no camera problem. is there anything i can check or 'copy and paste' into my wifes phone from my mates? im thinking overwriting a file or something?
thanks