I follow all the instructions for installing PACman on my HTC One V (GSM version), but when everything is finished and I restart my phone, it gets stuck on the HTC welcome screen. I figured it was because of a buggy kernel, so I used hellboy's, but when it does start up, it doesn't have any connectivity (no wifi, network, data transfer etc). I'm now running cyanogen without any problems what so ever, so I guess my phone's not broken. Any tips?
You have to do a full wipe from recovery,or it will give those bugs.
which pac man rom bro.... there is a 4.2.2 kernel u need to use that with the latest ROM
I did do a full wipe, like 5 times, and I'm using the bundled kernel.
Sent from my One V using xda app-developers app
Related
Hi,
For some reason in rommanager I can only see up to #13 for the cyanogenmod nightlies?
Does anyone else have this problem?
The reason I bought the paid version was to get access to all of them.
Thanks
Paul
Well you got ripped off because Rom Manager is ****. Seriously, you should NEVER flash anything with Rom Manager or have it installed at that. Just download it from CyanogenMod, put it on your SD and install it via recovery.
Rom manager does what it is supposed to do and does it well.
The reason you do not see anymore nightlies is because there are no more. The nightlies got reset after RC1 was released. There isn't a new njghtly every night because sometimes there is no successful build.
Rom Manager does everything really poorly, seriously. It is useless and causes so many problems.
Meaple said:
Rom Manager does everything really poorly, seriously. It is useless and causes so many problems.
Click to expand...
Click to collapse
Care to elaborate?
Sent from my HTC Desire using Tapatalk
The main issue(s) is when you reboot. Say you flash a rom, when you reboot it tends to just reboot and not flash the rom or anything. It does stuff like that. Rom Manager tries to be the recovery but whilst booted up but fails. Fair enough, it works for some people but so many other people have problems with it. Ok, it has been developed for "noobs" and yes, I did kind of use it at first but then I found out from my own experience it didn't work too well. I think that people should forget about Rom Manager and just boot up into recovery and just use that since the recovery actually works, and only takes a reboot (depending on your rom) to get into it.
Why, do you like it?
I've noticed same issue with the nightly. I've tried manually flashing the newer ones, but get an error on the device check. So rom manager is correct 13 or RC2 are the latest that will install
Sent from my HTC Desire using XDA Premium App
Am a bit of a newbie to the custom rom world. So far rom manager has worked fine.
Am currently on cyanogen rc2 and have flashed my radio without problems. As a Java developer and a phone geek people think I am mad for mucking about with my phone so much.
The question was because I thought I had read there was a nightly 15.
Sent from my Desire HD using XDA App
I have had the same issue with Rom Manager. I had to download directly from the Cyanogenmod site
Just flashed 17 and it seems to be really fast!
http://mirror.kanged.net/nightly/bravo/
or directly to 17
http://mirror.kanged.net/nightly/bravo/cm_bravo_full-17.zip
Cheers
Which desire do you have GSM or cdma?
Sent from my HTC Desire using XDA Premium App
Uk desire HD gsm
Sent from my Desire HD using XDA App
That version worked for me thanks
Sent from my HTC Desire using XDA Premium App
Just realised, that is the bravo version, cyanogen points xemacs desires to bravoc. Still seems to be working fine
Sent from my HTC Desire using XDA Premium App
I don't know if it's related, but I had trouble with CM7 RC2 when installed through ROM Manager, but manually flashing the CM7 Nightly #17 worked just fine. I wiped the caches etc. on both tries (or rather, ROM Manager did on the RC2).
As you know i can't ask this directly into dev's section right now, i want to ask after flashing various roms, i came through these 2 roms from suilmagic, 1 is insertcoin, and anotherone is desire s ported for g2 with sense/gingerbread, insertcoing doesn't have fm radio in his rom, but his desire s ported rom does have, but i have installed it correctly but it cannot load htc sense home screen, and it stucked on htc logo, i can access all apps through search button, just cant go to home screen, one more thing, when i open settings>personalize through search it says htc sense closed unexpectidly..force close, tell htc)...plz advice
Di dyou do a full wipe between insetcoin and the desire s roms?
Sent from my HTC Vision
cjward23 said:
Di dyou do a full wipe between insetcoin and the desire s roms?
Sent from my HTC Vision
Click to expand...
Click to collapse
yup bro i wiped data/cache, and also wiped dalvik cache, after that i installed rom, and through clockworkmod, not through rom manager
You might of just got a bad download, try downloading again.
Have you used superwipe. Might worth giving it a try and reflash the desire s rom. Get it from here http://db.tt/7xNYpFp
Sent from my HTC Vision
cjward23 said:
You might of just got a bad download, try downloading again.
Have you used superwipe. Might worth giving it a try and reflash the desire s rom. Get it from here http://db.tt/7xNYpFp
Sent from my HTC Vision
Click to expand...
Click to collapse
OK BRO..THANX FOR YOUR HELP...Right now device is at home...will re-download, and get back to you, my device is S-OFF, So using superwipe will not affect that? or i will have to re-root? give me the link of a guide for using superwipe if possible...once again thanks alot for your attempt to sort out my problem...
Superwipe won't remove s-off. Check out the origianl thread http://forum.xda-developers.com/showthread.php?t=1044992
It is a really good tool, I use everytime I switch roms and it does seem to make a difference.
Sent from my HTC Vision
ok, i will use it for wiping data this time...hope fully this time this rom will load properly..
I flashed the same desire s Rom and had the same problem as you. Restore your last working Rom but this time don't wipe dalvik and it will work
Sent from my T-Mobile G2 using XDA Premium App
bryyyan said:
I flashed the same desire s Rom and had the same problem as you. Restore your last working Rom but this time don't wipe dalvik and it will work
Sent from my T-Mobile G2 using XDA Premium App
Click to expand...
Click to collapse
i just flashed it again. i installed insertcoin sense again. and then i boot in cmw recovery, wipe data and did'nt wiped dalvik cache, and then installed desire s g2 port again, but still same, device booted and lock screen came up on first boot like every rom. but when i unloke screen, htc logo appeared and home screen did'nt loaded, now i am downloading again, but i am very unsure it will work, if zip file would have been damaged due to bad download, why its opening properly, anyhow 75mb downloaded so far,lets see
@cjward23: As per your instruction, i downloaded it again and also used your superwipe to wipe data/cache..and then installed desire s g2 port, but still having same issue, phone booted up properly with my network logo appeared as well, but when i unlock screen, it shown htc logo, actualy all roms show it, but within 5 minutes i see htc setup like time zone, google accounts etc, but this desire s didnt, it just stucked to that htc logo like its installing something, but no setup appears, this time i waited for 10 minutes, but no change...so far i get back to insertcoin sense/gingerbread 1.4, which is working properly as usual...actualy i just need fm radio...can you help me geting fm radio on insertcoin rom?
Hi all,
I have a routed DHD and have used the advanced ace hack kit, everything went well and the root was successful.
Now when I'm trying new roms from XDA the problem is that for 1 week the rom work absolutely fine and after that suddenly it is in bootloop and then I have to change the rom.
I have tried the following roms:
1) Core Droid v9.2
2) Lee latest rom v5.1.1
3) virtuoso affinity latest build
4) bindroid
n a lot more but still having the same issue.
Right now I'm on ARHD 6.3.1
Requesting a sincere help from the dev community....!!
Sent from my DHD using XDA App
Look at what mods you do or what you install..must be some kind of trigger maybe..have u updated Rom only not radios kernels etc etc?
Sent from my Desire HD using XDA Premium App
apart from installing the roms i haven't touched on anything....as i'm new to all this.
Try cyanogen for a while..have you flashed any roms without sense?
Sent from my Desire HD using XDA Premium App
Hmm, strange. What about ROM internal modifications or options?
As you tried LeeDrOiD 5.1.1 you seem to have that problem not always after 1 week (cause it's not that old *g*), so what about trying this:
of course make a backup of your data
full wipe your device (you can make sure to do it right by using a full wipe script
install a new rom and fully boot it
keep running it for a day without reinstalling your preferred apps
keep installing the apps step by step and watch the system's behaviour
When installing your new ROM and setting it up again, do you restore any data by using tools like Titanium Backup? If so, do you also restore system data or apps (+ data) only?
PS: maybe edit your topic's title to something better like "Problems with fresh installed custom ROM after a few days" or so.
unhallowedone said:
Hmm, strange. What about ROM internal modifications or options?
As you tried LeeDrOiD 5.1.1 you seem to have that problem not always after 1 week (cause it's not that old *g*), so what about trying this:
of course make a backup of your data
full wipe your device (you can make sure to do it right by using a full wipe script
install a new rom and fully boot it
keep running it for a day without reinstalling your preferred apps
keep installing the apps step by step and watch the system's behaviour
When installing your new ROM and setting it up again, do you restore any data by using tools like Titanium Backup? If so, do you also restore system data or apps (+ data) only?
Click to expand...
Click to collapse
Right now on ARHD 6.3.1...so far so good...!!
Neways...will try to do it ur way...and will check to see which app is creating this issue....!!
whereas read the LeeDroid forum and came across certain post regarding TB giving problem to certain users....!!
For now uninstalled the same... .
arknailed7754 said:
Try cyanogen for a while..have you flashed any roms without sense?
Sent from my Desire HD using XDA Premium App
Click to expand...
Click to collapse
Have used MIUI and worked well for at least 1 week...but got bored of it as was really missing sense...!!
But will try this option too...!!
Hi everybody,
last Thursday my phone had a boot loop, so I've decided to change the ROM.
I flashed my HTC Desire with Runny ROM 6.1.1 and since that time my camera doesn't work, flash either.
When I try to start camera app there is only black screen and phone restarts in 10 seconds.
I was trying with other ROM and official GB, but camera is simply dead.
Is there anything that I can do with it? Install some fix or update?
I have latest radio and cm7/r2 hboot.
Any ideas?
Do u test it by installing any camera app from play store?
with many apps but still the same effect
Try installing an AOSP build and check your result....what caused your phone boot loop?
Did you do a full wipe?
Sent from my HTC Desire using XDA
What is AOSP?
Yes, I did full wipe and build the partitions on sd-card from scratch.
Sent from my HTC Desire using XDA
AOSP is an original android rom, without HTC Sense or any other interface.(like sandvold's ics)
Sent from my HTC Desire using XDA
twisted_forever said:
Try installing an AOSP build and check your result....what caused your phone boot loop?
Click to expand...
Click to collapse
I don't know what caused boot loop, but I've tried cache and dalvik wipe, without success.
I will try later to flash some AOSP ROM and write here the results. Anyway I've tried already to flash RUU Gingerbread and camera was dead.
There's still no camera on AOSP Sandvolds ICS.
I think that I will disassemble my Desire and check the connections.
Wipe everything.
Boot, system, data, cache, dalvik. Then flash the ROM again. Wiping everything before flashing should be standard procedure for you.
I did it 3 or 4 times in a row. Nothing changed.
Sent from my HTC Desire using XDA
Hardware problem, try with connectors, but I think that you'll need a camera replacement.
Sent from my HTC Desire using XDA
ok, I disassembled my phone and checked all connections. Camera still doesn't work, but phone don't switch off when I try to execute camera app.
I will try one more time to do something with software.
Hi guys, ich disassembled my Desire one more time and guess what. There was one contanc loose. On the lower main board the left board-to-board connector. I put it into the socket and now everything works perfectly!
Anyway thank for your tipps guys!
Sent from my HTC Desire using XDA
This started happening a while ago (app crashing) on a different rom, and since then I've tried the following with no success;
New rom
New kernel
Full wipe
New gapps (not required on my current rom)
relocked and unlocked bootloader, upgraded from 0.95 to 1.28
Nothing seems to be working on any rom, and now I have just got out of a battery bootloader bootloop the past couple days my phone seems also unable to handle connections; I supposedly have signal however I receive no texts, data connection isn't working as my gmail account has not been synced (so I have no contacts etc) and wifi crashes when I turn it on.
I'm starting to worry this may be a hardware fault! However considering I have unlocked my bootloader I won't be able to return it under warranty! Can you suggest anything else to try? I haven't fully wiped my whole storage (sd card and all) is that an option to try?
Thanks for any help I can get
bump, really stuck here
If you you are using an AOSP Rom a special kernel is required for the new HBoot. Or has this happened on the old HBoot too? If so a hard reset might solve the problem.
Sent from my HTC One X using xda app-developers app
Marc199 said:
If you you are using an AOSP Rom a special kernel is required for the new HBoot. Or has this happened on the old HBoot too? If so a hard reset might solve the problem.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Yeah I am using an AOSP rom but it happened on HBOOT 0.95 and still on 1.28. Is that a factory reset from the bootloader? Also which kernel is it? I just used the boot.img included in the zip
You can do it from the bootloader. Essentially its just wiping everything including the sd storage. I dont have much time to look for it right now because im working. But if you use the search function you should find it have you tried to redownload the rom?
Sent from my HTC One X using xda app-developers app
Marc199 said:
You can do it from the bootloader. Essentially its just wiping everything including the sd storage. I dont have much time to look for it right now because im working. But if you use the search function you should find it have you tried to redownload the rom?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
This is the rom I'm using atm http://forum.xda-developers.com/showthread.php?t=1784185 (CM is based on AOSP right?)
and is this the kernel you're talking about? http://htcfanboys.com/download/seadersn/?action=view&file=14552 ? However don't I also
need the zip to flash in CWM?
Yes it is an AOSP Rom, but you dont need the the modified kernel because tripnraver solved the problem in his kernels and Rom. Since you have the problem on other ROMs too i would suggest to perform a hard reset and see if the problem still exists. Just backup everything and reflash Rom.
Sent from my HTC One X using xda app-developers app
I might try this AOKP rom that I used before, according to the OP there is a specific boot.img you must use for HBOOT 1.28, so I've downloaded that to and when I get home I'll give it a try. It says a full wipe is required, does that just mean cache/dalvik/wipe in CWM or do I need to run the SuperWipe.zip?
Marc199 said:
Yes it is an AOSP Rom, but you dont need the the modified kernel because tripnraver solved the problem in his kernels and Rom. Since you have the problem on other ROMs too i would suggest to perform a hard reset and see if the problem still exists. Just backup everything and reflash Rom.
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Sorry I just saw this reply, I'll try a factory reset before I try the other rom, cheers
I cant factory reset, everytime I do it just goes into CWM?
I just formatted each partition separately in CWM, re installed etc and pretty much everything seems to be back up and running However I am still having the SMS crash issue :S even though my whole SD card is wiped
At least the rest is working still weird though. Does that happen with any sms app?
Sent from my HTC One X using xda app-developers app