Related
Sorry to start a new thread. I have read the rules about posting and have searched for the last couple of days for an answer but can't find one.
I am unable to install ANY apps whatsoever and it is driving me crazy. I have an HTC Desire (obviously) and am using Pays ROM Froyo Sense v2.2 A2SD+ (updated just the other day). (And yes, I wiped everything like you are supposed to do, before and after the update.) I don't think the problem is with the ROM itself because the problems started before the update.
I am able to download apps from the market but it seems to get hung up on the installation itself. It never stops installing and I am not even getting a failed installation message.
I have gone to Settings>Applications>Manage applications and cleared the data and cache for all of the normal suggested apps and have even force closed a few. Nothing is working, even when I try to install .apk files which are located in the download folder of my SD card.
One strange thing I have noticed is that when I go to Settings>Applications>Manage applications, the amount of space being used never displays anything other than 'computing....' I know sometimes it can take a while for the size to be displayed but surely not an hour!
I have even restored the default/factory settings to see if that helped but nothing!!! grrrrr.....
I am reaching the end of my rope and would appreciate any advice offered. I am keeping my fingers crossed that this isn't a newbie mistake and thanks in advance for any help!
have you tried another rom see if the problem persists? it usuall only takes a minute for manage applications to find all my apps and i have looooooads also no problem with market, do a nandroid, and try another rom, if its still the same you can always restore your nandroid, i suggest maybe leedroid
Thanks so much for your reply! Was really hoping to avoid trying another ROM but I am going to give LeeDroid a try and hopefully that will sort out my app problem. Just finished downloading it, will flash and post back soon. Thanks again!
missbizzylizzy said:
Thanks so much for your reply! Was really hoping to avoid trying another ROM but I am going to give LeeDroid a try and hopefully that will sort out my app problem. Just finished downloading it, will flash and post back soon. Thanks again!
Click to expand...
Click to collapse
like i said do a nandroid, if leedroid dosent work then, you can just restore your backup and your rom will be exactly the same as it was b4 you flash leedroid
FIXED!!! Thank you so much!! Am happily running LeeDroid.
Just FYI: Usually, I have such a problem installing but I leave it (it shows nothing downloading). Upon restarting the phone (whenever), the apps automatically install.
-----------------------------------
- HTC Desire via XDA App -
So, I don't really post on forums because I'm pretty tech-savvy, but I have a big problem that I can't fix, and I can usually fix everything (thanks to you guys!)
This morning, my incredible acted up as I was checking an e-mail and it froze, so I decided to battery pull because restarting my phone didn't work. (Note, my incredible has been running VERY solidly on a CM7.1 nightly). As I tried to boot up the phone again, it would stay on the white HTC Incredible screen. When I rebooted into recovery thru HBOOT, i realized that there was an error mounting something, like recovery_log, or something like that (i didn't mind this because I thought I knew what I was doing), but I tried restoring my old nandroid backup that was working well, but it didn't work. It said it couldn't format /data or something... It ended up staying on the white HTC incredible screen. So, I wiped data/cache like 10 times, and dalvik cache as well and tried re-flashing a clean install of cm7.1 stable, but didn't work again - led me straight to the white Incredible screen. So, installing a fresh rom AND restoring a solid backup didn't work... so...
I found the RUU 2.3 stock rom on the development forums, and tried to install that like I do with the radios (PB31IMG.zip) through HBOOT, but no cigar. It did go PASSED the white screen, but boot loops at the Droid eye.
So, I thought I'd find a different stock img, and found the 2.2 official OTA .zip and installed it the same way, but got the exact same result (boot loops, forever).
Any suggestions? I can't think of anything else.... I feel like my phone is bricked, but I didn't do anything to make that happen.
I feel like something happened that made me not able to format the /data, and stuff. I even formatted my SDcard in case it was the problem.
Any help is appreciated. Thanks!
Load the RUU onto a different fat32 sd card and see if you are able to boot.
Sent from my ADR6300 using XDA Premium App
i'll try that and give an update. thanks for the reply!
*update* no luck. same thing happens. i tried on three different sdcards formatted fat32...
Can you factory reset and flash a ROM from a different sd than the one you were using? Description sounds like bad sd, and AOSP roms interact with the sd on boot. If original (CM 7) sd is toast, it'll never boot, hence different sd card and prefably RUU
Sent from my ADR6300 using XDA Premium App
I had this happen once where no matter what rom i flashed all i got was bootloops. I had to get the stock froyo ruu.exe that you run from your pc and install it that way. Then once installed boot up and go to settings/sd & phone storage and do a factory reset from there. This factory reset is a true reset as it wipes out vzw programing also. After reset folow on screen steps to reactivate your phone, you can skip the rest of the setup. Once thats done your good to go just flash clockwork or amon ra recovery and then flash what ever rom you want. No guarantees but it worked for me.
NOTE: This assumes you are s-off, if your not after flashing the ruu you will have to use unrevoked to regain root and s-off again.
You can also try wiping /system and /boot.
*token post to get my post count high enough to ask for help in the hacking section, dumb rule btw. FAIL*
Mine is now stuck in a continuous boot as well. It's not rooted and have no idea how to fix it.
I see instructions in this thread but they mean nothing to someone who doesn't know what the abbreviations stand for or how to go about the commands required.
sl4m said:
*token post to get my post count high enough to ask for help in the hacking section, dumb rule btw. FAIL*
Mine is now stuck in a continuous boot as well. It's not rooted and have no idea how to fix it.
I see instructions in this thread but they mean nothing to someone who doesn't know what the abbreviations stand for or how to go about the commands required.
Click to expand...
Click to collapse
if you are non root. you will need to download the RUU.exe for 2.2 and install if from you pc.
http://androidforums.com/htc-droid-...mplest-instructions-ever-windows-xp-only.html
follow that and your phone will be back to the day you got it out of the box.
All the recommendations prior to Synisterwolf's post require root.
Some of the "abbreviations" are detailed in the Droid Incredible Development section. If you head over there you can read up on a beginners guide to root terms and helpful links in one of the top four threads namely:
If You're New to Modding/Rooting, Read This First! (Updated 08/05/10)
I will say though:
CM7.1 = CyanogenMod 7.1 (this is a rom)
OTA = Over The Air
2.2 = Froyo (Android software version 2.2)
RUU = basically refers to a file that people use to revert back to the Droid Incredible's pre-root status. Although there are additional steps as well.
SlimSnoopOS said:
All the recommendations prior to Synisterwolf's post require root.
Some of the "abbreviations" are detailed in the Droid Incredible Development section. If you head over there you can read up on a beginners guide to root terms and helpful links in one of the top four threads namely:
If You're New to Modding/Rooting, Read This First! (Updated 08/05/10)
I will say though:
CM7.1 = CyanogenMod 7.1 (this is a rom)
OTA = Over The Air
2.2 = Froyo (Android software version 2.2)
RUU = basically refers to a file that people use to revert back to the Droid Incredible's pre-root status. Although there are additional steps as well.
Click to expand...
Click to collapse
RUU = ROM Update Utility
no luck, I installed the program on my XP machine, but the app can't connect to the phone.
The phone literally keeps rebooting over and over.
sl4m said:
no luck, I installed the program on my XP machine, but the app can't connect to the phone.
The phone literally keeps rebooting over and over.
Click to expand...
Click to collapse
Then its gotta be a hardware failure.
Sent from my sexy assistant. (AMOLED HTC Incredible)
wow... what a bummer. thanks for the help anyway, it's much appreciated.
sl4m said:
no luck, I installed the program on my XP machine, but the app can't connect to the phone.
The phone literally keeps rebooting over and over.
Click to expand...
Click to collapse
Does it give any specific error code when it says it can't connect to the phone?
Someone correct me if I'm wrong but don't you have to have HTC sync installed on your pc to use an ruu.exe? Do you have that installed?
Sent from my ADR6300 using xda premium
I'll try it again to verify the code, I'm pretty sure it was "170"
sl4m said:
*token post to get my post count high enough to ask for help in the hacking section, dumb rule btw. FAIL*
Mine is now stuck in a continuous boot as well. It's not rooted and have no idea how to fix it.
I see instructions in this thread but they mean nothing to someone who doesn't know what the abbreviations stand for or how to go about the commands required.
Click to expand...
Click to collapse
I had this issue the first time i rooted my phone and attempted to put on a ROM, and i resolved it when i found this post to get back to stock. I also used this to fix a problem where my phone had a black screen with a line through it on booting to recovery or attempting to do a nandroid back up:
droidforums.net/forum/droid-incredible-hacks/95406-how-correctly-unroot-incredible.html
All i did was basically use the PB31IMG Method without turning s=on, ( i had stock radio and still have 7.28 )
1) download that PB31IMG.zip and drop it on the root of your sd card ( it has to be named ( PB31IMG.zip ) so make use you have file extensions showing on your PC.
2) boot to hboot and and let see the file and install it
3) used unrevoked ( remove sd card ) to aquire root again.
idk if this helps, but this seems to get me out of the few weird situations i had
sl4m said:
I'll try it again to verify the code, I'm pretty sure it was "170"
Click to expand...
Click to collapse
Check this out to fix your 170 error.
http://androidforums.com/incredible...170-171-solution-windows-7-a.html#post1472468
This low key happened to me and I booted in to HBOOT and went to clear storage and it did its thing and booted up, from there I had to activate it then I was set!
Sent from my ADR6300 using XDA App
=D
Sent from sweet snacks off tapatalk.
Hi,
I am currently running Android Revolution HD 5.1.7 on my DHD
I was just wondering with the new 6.1.1 version out, to upgrade to it,
do I simply download the file and just flash that to the device or must I first wipe my device? Or some other way?
Thanks for any help!
P.s Really sorry if this has already been asked but I had a quick search and couldn't see anything to this specific situation!
Back up all your data then flash the superwipe script, then flash the ROM, restore data
Sent from my HTC Desire HD using Tapatalk
Thanks alot,
Also once I have flashed the rom to the phone,
Can I remove the file from my SD Card to free up some space?
Its something I have been unsure about from the first time I flashed my phone,
But I should imagine you can??
**UPDATE**
I have succesfully installed Android Revolution HD 6.1.1
But I am getting an awful lot of Force Closes now,
1 in particularly when i try to go on "People" (contacts) it instantly force closes!
Another is SuperUser, and there are a few more than insantly FC as soon as I try to Open them!
Razza12003 said:
Can I remove the file from my SD Card to free up some space?
**UPDATE**
I have succesfully installed Android Revolution HD 6.1.1
But I am getting an awful lot of Force Closes now,
1 in particularly when i try to go on "People" (contacts) it instantly force closes!
Another is SuperUser, and there are a few more than insantly FC as soon as I try to Open them!
Click to expand...
Click to collapse
1. You can but I would recommend that you keep a copy of a stable ROM on your sd card just in case you have to reinstall for some reason.
2. It seems like the ROM is corrupted.
Did you superwipe before you installed the ROM?
If you have:Check the md5 checksum of the rom you downloaded. It should be the same as the one posted under the ROM download link in the ARHD thread. If its the same you can try superwiping and reinstalling the rom.
If you havent: Download the superwipe script from the first page in the ARHD thread, superwipe and reinstall the ROM.
Also make sure to backup your phone data before superwiping because everything will be lost. Also don't install any mods untill your device has completed the first boot after installing the ROM.
to be honest i had issues with arhd 6.1.1 when i flashed it too. not the same as yours but constant. not everybody seems to have them though and others say it has something to do with the overclock daemon. i believe there´s a patch for it though on the 6.1.1 developers thread.
i didnt bother though i just moved on to virtuous unity 2.39 and have had no problems, really smooth sense 3.0 rom. i´ve been planning to try out a non sense rom next but i really like this rom so i´ve been putting it off for a while now. i even put the beats audio patch on it a few days ago and i gotta say its pretty good even on stock htc headphones
planing to update to arhd6.1.1 too, but have ardh3.3 and clockwork 3.0.0.6. which clockwork is ok (mean which of the newest)?
I did use superwipe and i checked the md5 and it was all good!
I re-flashed the rom and now its ok
I have found out what was causing it!
It starts happening again every time I install google+ 2.0
The new version of the app that has recently been leaked on androidpolice
(Would include a link but im not allowed yet)
And the reason it did it straight from the start the first time is because, before
doing anything else, I restored all my app via Titanium Backup!
If anyone else has this issue or could try to install the app and see if it happens
to them or could figure out how to fix it, it would be great!
(Don't worry about installing it, uninstalling it stop the force closes straight away)
did you try just restoring just the app, but clean without the user data. i did that first time i flashed a rom and it caused all sorts of problems. so i reflashed and restored the apps one by one but just the app, no user data, and stopped having problems
Lewelynn said:
Also make sure to backup your phone data before superwiping because everything will be lost.
Click to expand...
Click to collapse
Hi,
My first post
Any idea does this superwiper clean the radio as well? Does the order matter - first wipe, then rom and finally radio?
ponk2k said:
did you try just restoring just the app, but clean without the user data. i did that first time i flashed a rom and it caused all sorts of problems. so i reflashed and restored the apps one by one but just the app, no user data, and stopped having problems
Click to expand...
Click to collapse
Yes i tried restoring just the app, that caused fc's too!
As did re-downloading the app!
jms-xda said:
Hi,
My first post
Any idea does this superwiper clean the radio as well? Does the order matter - first wipe, then rom and finally radio?
Click to expand...
Click to collapse
Superwipe doesn't effect the radio, and yeah that order you said is the way I went about it, but I also think you can do radio before rom too!
Update from 5.1 to 6.1
Maybe I haven't looked hard enough or maybe I am simply too tired...
Are there any specific steps from updating ARHD from 5.1 to 6.1? I can't seem to find any info about it.
Also, flashing the 6.1 over the 5.1 will it reset the way my screens/widgets are set while on 5.1?
Thanks.
All right this problem has now been solved! Thank goes to khamsakamal48 for posting the solution for the problem. The problem is solved by replacing the updater-script with the one that is used in the GSM version the of Rom. Then Using the latest 4ext recovery, wipe everything and install. Thank you to everyone that have participated in trying to get this solved. This might also work with other recoveries, but has not yet been confirmed.
Updater-Script: http://db.tt/sUfk5p8E
Latest 4ext recovery: http://db.tt/sP5o7HhJ
only thing i could think of is try a different recovery .I haven't had any trouble at all booting miui an i use cwm touch version.
Alright I'll have to give it a try. Was trying to avoid that but oh well. Thanks!
Sent from my Incredible 2
so I tried 4ext and clockwork recovery. Both have caused my phone to just boot right back into recovery. Wiped data and all.
kylesag21 said:
so I tried 4ext and clockwork recovery. Both have caused my phone to just boot right back into recovery. Wiped data and all.
Click to expand...
Click to collapse
Can you give us a little more background on your phone setup? Have you flashed roms successfully before or is this a first time? Are you s-off?
Sorry bout that. I am S-off and I am able to flash all of the other roms available. But when it comes to this one it just won't flash.
Sent from my Incredible 2 using Tapatalk 2
I have been having this same problem. I am going to try to go through everything I have done to see if I can get more info.
I had MIUI V4 (2.9.29 CDMA) running shortly after rooting this phone (maybe 1 week ago). I installed it from the latest TWRP, so that isn't our problem. I loved it and everything was great. I am unsure what radio I was on at the time, and I think that may be where my problems came in.
I successfully installed ViperINC 1.0.0 after doing a factory reset, wiping cache, dalvik from my WORKING MIUI V4. It booted and I played with it for a few hours, but wanted to go back to MIUI. At this point I was on the firmware from nitsuj17's thread. When I tried to factory reset and install MIUI clean again I started having the same trouble as OP. Since then I have tried every radio I could get my hands on, and may have even been a bit sloppy about what firmware I flashed (the only one I'm unsure of is CondemnedSoul's Return to stock as I am unsure what all it included other than radio and stock rom). After a lot of different attempts, I used CondemnedSoul's PG32IMG and went back to stock where I had everything working fine (for stock). I got an OTA update, but wasn't satisfied so I kept trying different radios from the pinned post on the Development thread (really only .0312 and .0320 as well as the first leaked firmware I linked from nitsuj17). So far nothing has worked to get me any further than the OP unless I just use a different rom. Had this rom never worked I would just talk to the developer, but as I had it working before and no idea what changed I'm at a loss.
I don't have enough posts to get something on the Development forum, but if anyone here can help, I'd really appreciate it.
I've been scouring these forums looking for someone who has made progress on this issue. I'm going to make a list here of posts by people having similar problems, if not the exact same. I have yet to see anyone successfully address them.
One of a few people on the MIUI V4 thread who have had the same issue. I had this rom running at one point, though, so I'm not sure what change caused it to stop. I definitely get further with the TWRP recovery (freezes on "android" splash screen) than the 4ext recovery (reboots to recovery).
I don't believe the JB issues are directly related, but similar problems.
Similar to the Jellybean issue above. More similar to my own situation since I also only started having trouble after flashing ViperINC, but I have formatted, wiped and reverted (even to S-ON and unroot Froyo) so much that I can't see how it would have changed anything that I have not removed. This thread has 3+ people with the same sort of issues. Last report one of them installed ViperINC with all defaults and let it run for a few minutes then wiped and re-installed CM10 with success. I may try this, only with MIUI. I have no idea what settings would be slipping through.
And the cdma miui is one of the only roms that boots for me. Running it now. I think Zelmo is right, there's something sticking around with that Aroma script. I've flashed aosp roms over sense roms and vice versa without even wiping and never had issues like these. I've basically wiped this thing with steel wool and always the same thing. It's gone atleast 15 mins with it's bootloop/freezing max cpu process. It ain't gonna boot! I was up until 2am last night ****ing with it. I'm done.
I'm nearly there. Had I never been able to run MIUI, I would probably have dumped it by now, but it's like an itch I can't reach at this point. There is just something there that I can't see or imagine that is hanging in through every wipe I can find. I just formatted my SD card and did a bunch of wipes (I know that has been tried) and I'm going to try VenomINC with all defaults like Zelmo88 had some success with. If I don't have any luck getting to MIUI from there I'll probably go back to my dinc or buy a new phone soon. This one was really an experiment anyway.
Will follow up if I can figure out anything else.
khamsakamal48 posted pretty detailed instructions here. I have confirmed that my install is going pretty fast, so I am betting that could be our issue. I am not sure what causes this or how to prevent it. I'm going to try and flash it a bunch of times here to see if I can get it to complete.
Edit: I tried 3-4 times with CDMA file and had no success making it take longer than 1-2 minutes. I then flashed the GSM file which I had been having the same trouble with and it succeeded! I am going to check my MD5s again on the CDMA file and give it another go.
Edit: I have tried now around 10 times with the file found here linked from khamsakamal48's thread on the development forum. MD5 matches, but I cannot find any method of flashing>wiping>reflashing>rewiping>crying>flashing>snoring which will make it take more than about a minute with the "install". I'm going to type out my log from 4ext so that I have something to do.
>format all partitions (except sdcard)
>wipe dalvik cache ;multiply the repetetive redundancy
>install from sdcard
>MIUI.us_vivow_v4_2.9.29.zip ;MD5 9f36b433635e50e0daf23768280c050f
;begin log
Finding update package...
Opening update package...
Installing update...
Formatting system...
do not formate system ;???
Installing system files... ;this bit may take 1minute
Creating system links...
Set permission...
Update Boot image...
Install from sdcard complete. ;and done in less than 2 minutes every time.
If someone could post a link to this on the Dev forum or something I would appreciate it. I don't feel like spamming 4 more posts just so I have that privilege.
stoicwood said:
khamsakamal48 posted pretty detailed instructions here. I have confirmed that my install is going pretty fast, so I am betting that could be our issue. I am not sure what causes this or how to prevent it. I'm going to try and flash it a bunch of times here to see if I can get it to complete.
Edit: I tried 3-4 times with CDMA file and had no success making it take longer than 1-2 minutes. I then flashed the GSM file which I had been having the same trouble with and it succeeded! I am going to check my MD5s again on the CDMA file and give it another go.
Edit: I have tried now around 10 times with the file found here linked from khamsakamal48's thread on the development forum. MD5 matches, but I cannot find any method of flashing>wiping>reflashing>rewiping>crying>flashing>snoring which will make it take more than about a minute with the "install". I'm going to type out my log from 4ext so that I have something to do.
>format all partitions (except sdcard)
>wipe dalvik cache ;multiply the repetetive redundancy
>install from sdcard
>MIUI.us_vivow_v4_2.9.29.zip ;MD5 9f36b433635e50e0daf23768280c050f
;begin log
Finding update package...
Opening update package...
Installing update...
Formatting system...
do not formate system ;???
Installing system files... ;this bit may take 1minute
Creating system links...
Set permission...
Update Boot image...
Install from sdcard complete. ;and done in less than 2 minutes every time.
If someone could post a link to this on the Dev forum or something I would appreciate it. I don't feel like spamming 4 more posts just so I have that privilege.
Click to expand...
Click to collapse
Your post is an exact match to what I've done. Even tried reverting to ext3 ( no luck, obviously). Well I've got the bug so now I'm not stopping until I figure this out. I'm running viper 1.0.1 so there might be a common element.
grunt9800 said:
Your post is an exact match to what I've done. Even tried reverting to ext3 ( no luck, obviously). Well I've got the bug so now I'm not stopping until I figure this out. I'm running viper 1.0.1 so there might be a common element.
Click to expand...
Click to collapse
I think most of us first noticed these problems around the time we flashed Viper, but I have nuked this thing so hard from so many different directions since the last time I ran Viper that I can't imagine anything surviving. Still, a little too coincidental.
Running the GSM version didn't last long, either. I played around with trying to get it to use my sim, but as soon as I changed some of my network settings it went into a bootloop tailspin and somewhere along the way corrupted my /system. That took a little work to get around, so now I'm back to aeroevan's CM10 which runs OK... other than what doesn't.
Try replacing the updater-script under meta-inf with one from my GSM version!!
Hope that helps!!
Edit: Replace the updater-script with this one- http://db.tt/sUfk5p8E & use this recovery which I downloaded just now- http://db.tt/sP5o7HhJ
All the best!!
Sent from my HTC Incredible 2 using xda app-developers app
[SOLVED]
khamsakamal48 said:
Try replacing the updater-script under meta-inf with one from my GSM version!!
Hope that helps!!
Edit: Replace the updater-script with this one- http://db.tt/sUfk5p8E & use this recovery which I downloaded just now- http://db.tt/sP5o7HhJ
All the best!!
Sent from my HTC Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
Worked perfectly first try! Now running CDMA version without problem. I don't know why it works, but it works. Everyone thank khamsakamal48!
I'm not seeing a meta-inf folder. Is there another place it could be?
Sent from my vivow using xda premium
I believe it is in meta-inf>com>google>android
Updater-script should be located there.
Sent from my HTC Incredible 2 using Tapatalk 2
Nope, no meta-inf. Back to Google
Sent from my vivow using xda premium
Are you using 7zip to open up the zip file?
Sent from my HTC Incredible 2 using Tapatalk 2
I'm too embarrassed to tell you what I was trying got it now, thanks again
Sent from my vivow using xda premium
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