Related
I'll give my question first, then the history. I tried to search the EVO 4G subforums and couldn't seem to find it. If there's a post on this please kindly point me in the right direction.
Regardless of which ROM I install on my EVO except for what I understand is the engineering ROM or possibly the stock ROM, I go into a boot loop.
History:
- Did not install any updates or use unrevoked after receiving my EVO
- Did the root method known as "part 1" before NAND unlocking was available, never did any system updates. It seemed I had root because I was able to use the sudo "allow" or "deny" and use Wifi Tether in AP mode successfully (the open source APK)
- Was having some random reboot issues so I decided I needed to finally get an updated, custom ROM on my phone
- Yesterday spent many hours trying to get SimpleRoot to root my phone. However, ROM Manager keeps complaining it can't do privileged commands
- I was able to get Clockwork Recovery onto my phone finally using Unrevoked 3 just to get it on there (with what I know as the engineering ROM)
- Used clockwork to try and install Fresh 1.0.1, DamageControl v3.1.2 or seemingly anything other than that same engineering ROM (that has the HTC logo and sound) puts it into a boot loop. Also Clockwork (the APK) complains it still can't run privileged commands on that ROM from SimpleRoot.
I've been flashing a Kaiser/Tilt since forever but still pretty newb on Android but trying to learn fast. Love my EVO!
If there is any more information I can provide to help someone help me please let me know and hopefully this can help others not go astray as I have...
EDIT: Oh, yes and I read some of the troubleshooting information for different ROMs and one said to reformat sd-ext but my SD card is just formatted how it comes from the factory. I would really like to keep it that way unless it is a must for installing custom ROMs on the EVO. Clockwork did not seem to be able to do the partitioning for me.
EDIT: Now resolved after following thoroughly the directions listed here:
http://forum.xda-developers.com/showthread.php?t=721055
Thanks for helping me out!
aikeru said:
I'll give my question first, then the history. I tried to search the EVO 4G subforums and couldn't seem to find it. If there's a post on this please kindly point me in the right direction.
Regardless of which ROM I install on my EVO except for what I understand is the engineering ROM or possibly the stock ROM, I go into a boot loop.
History:
- Did not install any updates or use unrevoked after receiving my EVO
- Did the root method known as "part 1" before NAND unlocking was available, never did any system updates. It seemed I had root because I was able to use the sudo "allow" or "deny" and use Wifi Tether in AP mode successfully (the open source APK)
- Was having some random reboot issues so I decided I needed to finally get an updated, custom ROM on my phone
- Yesterday spent many hours trying to get SimpleRoot to root my phone. However, ROM Manager keeps complaining it can't do privileged commands
- I was able to get Clockwork Recovery onto my phone finally using Unrevoked 3 just to get it on there (with what I know as the engineering ROM)
- Used clockwork to try and install Fresh 1.0.1, DamageControl v3.1.2 or seemingly anything other than that same engineering ROM (that has the HTC logo and sound) puts it into a boot loop. Also Clockwork (the APK) complains it still can't run privileged commands on that ROM from SimpleRoot.
I've been flashing a Kaiser/Tilt since forever but still pretty newb on Android but trying to learn fast. Love my EVO!
If there is any more information I can provide to help someone help me please let me know and hopefully this can help others not go astray as I have...
EDIT: Oh, yes and I read some of the troubleshooting information for different ROMs and one said to reformat sd-ext but my SD card is just formatted how it comes from the factory. I would really like to keep it that way unless it is a must for installing custom ROMs on the EVO. Clockwork did not seem to be able to do the partitioning for me.
Click to expand...
Click to collapse
i had a similar issue, and so did a few people. i wrote out a post some time ago, i don't know if you read it...
http://forum.xda-developers.com/showpost.php?p=7204861&postcount=4
try that out. let me know how it goes.
EDIT: it also sounds like you don't have nand unlocked.
Thank you for your quick reply! I will try it and report back what I did, what works/didn't.
As a side note...
Since I have Clockwork on the recovery (I can boot to recovery all day long just using volume up and clockwork is there) doesn't that mean NAND is unlocked? Anyway, thank you again.
aikeru said:
Thank you for your quick reply! I will try it and report back what I did, what works/didn't.
As a side note...
Since I have Clockwork on the recovery (I can boot to recovery all day long just using volume up and clockwork is there) doesn't that mean NAND is unlocked? Anyway, thank you again.
Click to expand...
Click to collapse
having a boot recovery program doesn't necessarily mean you have nand unlocked. the ability to flash custom roms does though. good luck! i know it's frustrating, but keep at it.
silly question but are you wiping correctly ?
I had to ask...
elegantai said:
silly question but are you wiping correctly ?
I had to ask...
Click to expand...
Click to collapse
i almost spilled my drink LOL
elegantai said:
silly question but are you wiping correctly ?
I had to ask...
Click to expand...
Click to collapse
lol XD nice ... any comeback I can think of just goes way too far
Well, I've downloaded the files so sometime this evening/tonight I should have results. That post links to what appears to be a very, very thorough set of instructions
http://forum.xda-developers.com/showthread.php?t=721055
So I'll go through the whole thing there and of course report back
aikeru said:
lol XD nice ... any comeback I can think of just goes way too far
Well, I've downloaded the files so sometime this evening/tonight I should have results. That post links to what appears to be a very, very thorough set of instructions
http://forum.xda-developers.com/showthread.php?t=721055
So I'll go through the whole thing there and of course report back
Click to expand...
Click to collapse
lol good luck buddy. it's a relatively easy walkthrough if you follow it closely. post up any questions you have.
Hi,
I have a HTC Desire and just after I got it I managed to muddle through unbranding it to get rid of the Vodafone addons. At the same time I managed to root it.
I recently decided to take the jump and try some of the non stock ROMs as that's one of the reasons I went for Android.
I have to say there are some great tools out there and my sincere thanks to the developers, namely:
o AlphaRev
o ClockworkMod
o ROM Manager
o unrevoked
Wow nandroid is a real bare metal restore that works ))
When I decided to take the plunge I went through the recommended approach detailed elsewhere in this forum.
I've so far tried LeeDroid, Oxygen & Defrost.
I now have a slight problem that seems (perception) to be getting worse.
In summary, if I reboot into recovery (either power/back or ROM Manager) it sometimes works and more often now doesn't work. When it fails it just hangs at the AlphaRev screen, just a boot screen I guess. When it hangs it never recovers, battery out and try again, again, again .... then it'll work.
Does anyone have any thoughts on this boot into recovery issue ?
Colin
~~~~~~~~~~~~~~~~~~~
HTC Desire
AlphaRev S-OFF
Radio 32.49.00.32U_5.11.05.27
ROM currently Defrost (still trying the various flavours)
This is the issue, people get a brand new shiny phone and the first thing they do - as opposed to actually USING the thing - is find as many ways to bodge it as possible...
People need to actually read everything, take some time to absorb it and then read it again. Then use the phone as chances are unless they're a real app whore they'll never need to worry about internal space...
I've no idea why you're having issues but I assume you don't have a copy of the RUU your Desire originally came with so should you need to return to stock you can?? this is the first thing anyone should do before undertaking any type of customising and would save a lot of headaches
Hmm,
Not quite valid. I've had the phone for a few months now. I originally wanted to get rid of the Vodafone crap as that's caused me issues in the past with other phones, albeit not Android based. At the same time I wanted to go to Froyo which was on the never/never from Vodafone at the time. Again upgrading phones in the past has caused more issues when it's been used for a while.
I work in the IT sector and have dual boot on my laptop (XP & Ubuntu) as they do different things in different environments, so I'm used different look/feel/behaviour. I wanted to try some of the non HTC Sense ROMs, a couple of things bugged me a bit and after all you can try in the Android environment. That after all is the beauty of an Open System as opposed to a closed environment, e.g. Nokia Symbian, M$ Windows.
My only issue I have at the moment seems to be the tempremental behaviour of getting into recovery.
BTW I have a copy of the stock ROM but have no intention of ever going back to a Vodafone branded pre-froyo Android environment.
When I rooted, installed S-OFF, ClockworkMd, ..... I fully accepted the risks and knew that if I bricked the phone, it'd be my fault.
Regards
Colin
how bout reflashing recovery?
gol_n_dal said:
Hmm,
Not quite valid. I've had the phone for a few months now. I originally wanted to get rid of the Vodafone crap as that's caused me issues in the past with other phones, albeit not Android based. At the same time I wanted to go to Froyo which was on the never/never from Vodafone at the time. Again upgrading phones in the past has caused more issues when it's been used for a while.
I work in the IT sector and have dual boot on my laptop (XP & Ubuntu) as they do different things in different environments, so I'm used different look/feel/behaviour. I wanted to try some of the non HTC Sense ROMs, a couple of things bugged me a bit and after all you can try in the Android environment. That after all is the beauty of an Open System as opposed to a closed environment, e.g. Nokia Symbian, M$ Windows.
My only issue I have at the moment seems to be the tempremental behaviour of getting into recovery.
BTW I have a copy of the stock ROM but have no intention of ever going back to a Vodafone branded pre-froyo Android environment.
When I rooted, installed S-OFF, ClockworkMd, ..... I fully accepted the risks and knew that if I bricked the phone, it'd be my fault.
Regards
Colin
Click to expand...
Click to collapse
I didn't mean it as a flame btw, just that so many people come on here and blindly follow everyone else without actually realising what they're doing
>> I didn't mean it as a flame btw, just that so many people come on here and blindly follow everyone else without actually realising what they're doing
NP,
I get it all the time having to "help" people who tried things on their Home PCs or TVs, BluRay, HDMI inerconnect, ..... Shops offer bloody useless help to them. ;-)))
>> how bout reflashing recovery?
Yes, I've tried reflashing ClockworkMod through ROM Manager, it's currently 2.5.0.7 confirm by ROM manager and when it finally gets into recovery.
It just seems an intemittent issue that only arises when I want to do a Nandroid backup or "play" with the ROMs / Radio etc. The only solution I have is to remove the battery, count to 3 and re-insert it. Then try again.
It's not a show stopper just a real pain, especially when installing a new ROM/Radio when it's supposed to reboot. It's a case of how long do I leave it and hope it recovers to sod it, battery out and pray it's not bricked as a result.
Regards
Colin
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.
Not sure how to start this...
first off, i'm pretty sure my phone now has a fried eMMC chip, but in reality, i don't really know...
the reason i say i think it's fried is because no matter what method i try to flash anything to my phone with...it simply won't do it...most fastboot commands will not work anymore, my computer won't load the devise anymore so no adb commands, bootloader fails everything when trying to flash a stock rom and gets hung up updating the radio_v2....i've tried running official RUU's but it keeps telling me my phone has less then 30% battery life, wich is simply false. and i can't get into my recovery without it crashing the phone and not letting me turn it back on (till battery pull).
i went onto the #g2root and #xda-devs channels on the freenode server in mIRC, and had talked to a couple people there who also think i probably fried the eMMC chip (making it impossible to write or read anything from the phone), but again...i'm really going on word of mouth rather then first hand knowledge here.
but again today, i ran into yet another possible solution and i just want to know if i should bother trying or if i have a chance.
http://forum.xda-developers.com/showthread.php?t=1314629 is the thread, but i think this is for a desire s, so i suppose my question would be...would this method still work if i just used the right files or, again, am i screwed?
i have an HTC Desire Z that i got from Bell in Canada. it has gotten an OTA firmware update, and does not have root or s-off
if i remember right, everything is still stock, completely. minus the now possibly fried eMMC chip lol
thank you in advance and i will try to edit this post as neccessary so as to update any needed info.
please ask me questions as to what i have done and i will try my best to let you know. i know i had followed probably too many guides for rooting with too many methods lol next time, xda-dev's wiki guide, and that's it!
[edit:] i just found this too...lemme know if this helps..... http://forum.xda-developers.com/showthread.php?t=1284196
[edit:] i do know that when i go into my recovery, it does say those things (e: can't mount cache, blah blah) but it crash's out and doesn't actually get me into the recovery console. if so i would be able to envoke some adb commands and just finish this, but that's adding to the issue really...not being able to get into my recovery.
i feel with you.
it happend for me just today morning.
got my desire z on thursday, installed usual apps.
it started to freeze in random app installations. the last softreset threw it into a boot loop with the same problems you stated above.
you can get pre formated desire z emmc's for around 30 - 40 euro i think. but soldering them on your own requires some skill and tools since their contacs are below and not on the side.
this accident threw me back to my old htc touch diamond (with windows mobile 6.1 D: )
Q&A for [ROM] [04/10/14] [Unofficial] CM 10 for HTC Desire 300 [Public Beta]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM] [04/10/14] [Unofficial] CM 10 for HTC Desire 300 [Public Beta]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Hello,
I had a problem with my HTC desire 300 and I took it to a servis, there they put the cwm on my phone but my wifi isn't working, or its working a little bit and then it says that I can't connect.
So, I'm new here and I don't understand all the words here and I'm confused, so can you please explain me how to restore my htc to stock rom?
Interesting, I didn't even know my thread had a Q&A section
May I ask what was wrong with the phone before you had it serviced?
So the service center unlocked your bootloader and flashed a custom recovery?
They deliberatly voided your waranty? This sounds wrong on so many levels, please tell me you gave them permission to do so.
cwm is clockworkmod recovery btw and you are asking in the cm10 thread, does that imply that they also flashed this rom?
I don't know what to say to this except get your money back and/or sue them unless you actually asked them to do so.
Flashing a userdebug build on an enduser phone in a service center without being asked to do so is criminaly negligant imho.
The wifi in this rom is working fine (at least in the latest available build) so it might also be a hardware problem.
Could you tell me the version number of the rom you have on your device? (Settings->About Phone->CyanogenMod version)
To return to stock you would need the backup of your original rom and use cwm to restore the device.
That's why the OP includes a reminder that you should always make a backup before flashing a different rom.
There are no official htc RUUs available for this device, so without that backup you are out of luck.
I couldn't turn on my phone, it was stuck with the HTC logo, so I took it to the service and they told me it was a software problem and that they can fix it. After fixing it wifi worked 3-4 days and then stopped, all passwords are forgotten and its says '' Failed to connect network''. I know that its the clockworkmod when I press volume down and power.
When I go to recovery it says cwm advanced edition 5 cwm base version v6.0.3.7 philZ
I'm sorry If I asked in the wrong field but I'm so frustrated and just want my wifi to work somehow..
I don't mind you asking. I was just surprised to get a pm from a bot saying that my thread now has a Q&A.
I'm glad to see that it's still the stock rom you are on. But I don't know why it would bootloop or suddenly loose wifi.
Just out of curiosity, is the bootloader still locked? And is it the broken philz recovery with the graphical glitches that crashes on exit?
I don't understand why they would need to change the recovery. If the device is not repairable via factory reset or original recovery.
They should've just sent it in to htc for a replacement unit.
There are 2 things you can try now:
Try the factory reset option in the bootloader and if it doesn't work get in contact with htc customer support.
or
Replace the recovery, backup your system, check if wifi works in the cm10 rom and if it doesn't work
then reflash your backup before asking the htc customer support for assistance.
But be aware that the more you mess around with the device the less inclined htc will be willing to help you without charging you for the repair.
I tried the factory reset and nothing happens, still no wifi.
How can I replace the recovery?
Thank you!
First you need to set up your pc so it can communicate with the device via the android debug bridge.
There should be many tutorials on how to do that on this site. Just find one that explains how to get adb and fastboot working.
Since your radio and build version are different then mine I'd like to be on the safe side since I don't know what the service center did.
So activate the usb debug in the stock rom, and open a terminal.
Type: "adb shell" to connect to your phone and then type "cat /proc/emmc" and post the output here.
It should look something like:
Code:
dev: size erasesize name
mmcblk0p17: 000ffa00 00000200 "misc"
mmcblk0p34: 00fffe00 00000200 "recovery"
[...]
thank youuu so much I will try it..
I'll take it to the service again, and I'll let you know what he told me about the new recovery, and the wifi and everything that he made on my phone :crying:
Don't forget to ask them why they think it would be better to void a customers warenty by unlocking the bootloader,
instead of using it to get the manufacturer to replace the device if it's broken.
just to let you know that I took my htc to the service again, and they told me that the wifi is broken and they need to change the wifi chip or card I think...
Google Play has stopped working
Hi guys.
I have problem with Google play. I have instaled gapps for CM 10 (downloaded from cyanogen wiki). Everything works (youtube, gmail, google music, google sync,...) except Google play store...
Gapps was instal via recovery.
I tried to donwload only Google play app, but it get : Android App Not Install. An existing package by the same name with a conflicting signature is already installed.
Did anybody has same problem?
Thanks
Hi,
Just flashed the ROM on my girlfriend's phone and I gotta say its pretty nice she's quite happy with it and I gotta say it made her phone a lot faster so thanks for that from her ill keep an eye on it to see if she experiences any problems and let you know.
jaboos said:
Did anybody has same problem?
Click to expand...
Click to collapse
So far you are the first with such a problem. I can only assume that you grabbed the wrong gapps version.
In order to start fresh you'll have to do a full wipe (format system & data) because gapps will persist if you simply reflash the rom.
hello,
can you please upload the source of your rom to github?
thank you
Progress?
2 problems
day 2 of testing. nice work, thank you for providing this custom rom. signal strength is an issue. but battery usage is normal. I have two problems:
1. the weather does not display on lock screen.
2. google or other location based services cannot identify my location.
3. When I try to install Facebook app, it says this version of android is not supported.
can you please help me on this?
I have been using this ROM for a while, I have to say it was a horrible thing to install (not because of the ROM though, my phone doesnt read the internal SDCard in recovery.) and I have not had any issues apart from one which I will get to later, than you OP for making this, now what we need is a custom kernal to overclock this sadly weak phone.
CyanogenMod runs so much better than Stock sense 5, but I have a issue when exiting or entering apps, it will get a certain area of the frame and make a grid, this also sometimes happens while changing rotation, however it is alright to live with.
We need a cyanogenmod 11/12 port now
TheGamingBarrel said:
I have been using this ROM for a while, I have to say it was a horrible thing to install (not because of the ROM though, my phone doesnt read the internal SDCard in recovery.) and I have not had any issues apart from one which I will get to later, than you OP for making this, now what we need is a custom kernal to overclock this sadly weak phone.
CyanogenMod runs so much better than Stock sense 5, but I have a issue when exiting or entering apps, it will get a certain area of the frame and make a grid, this also sometimes happens while changing rotation, however it is alright to live with.
We need a cyanogenmod 11/12 port now
Click to expand...
Click to collapse
i'm willing to make cm 12 for this device as i own it, but HTC hasn't released the kernal source as of yet and i don't think they will at all.
if they do, send me a message and i'll start to port cm 11 or 12 and an overclocked kernel
app2sd
hi
i installed and used this rom for about a month and it was really OK. thanks
but the only thing that needed is Move2sd option in app settings and i dont know how to enable it, the 2 gig internal memory really bothers!
thanks again for your attention
Its a great rom just a pity that libaudio is not working as normal