I have a Virgin Mobile HTC One V and had been using the pacman 19.3 ROM. Except for a few minor issues, I haven't upgraded to subsequent builds as they have all had major issues that would affect my use of the phone. However, pacman 22.1 was just released and it seems that everything is working. I downloaded the ROM and every time it sticks on the HTC unlock boot screen when booting into the ROM. At first I simply wiped dalvik/cache, and that did not work. Then I reverted back to pacman 19.3. I've tried many combinations of installing this ROM, but all have the same result, including wiping everything prior to install. I get the same HTC boot screen every time. Can anyone help me get past this?
Wrong forum, this is for the htc one, not the one v.
Related
I did a few searches and couldn't find any help with this.
Basically I downloaded the latest mods and tried a few, but all had the same problem. I was using safestrap on a rooted droid 4. downloaded the latest cyanogenmod for droid 4 from here http://rombot.droidhive.com/ROMs/maserati/
These roms were linked to by the thread below.
I tried the 6/9/2012 version of cm9 and the 6/9/2012 version of AOKP.
I followed the instructions here: http://forum.xda-developers.com/showthread.php?t=1533161
followed the instructions. wiped data, wiped cache, wiped dalvik cache. Then installed the rom from the SD card, and installed google apps.
I then reboot. The screen is very dim. It is responsive for a few seconds and I sometimes flashes into functionality allowing me to click the "start" icon button. The furthest I got was with the AOKP rom and was allowed to type one letter of my username before it went non-responsive and dim screen. Keyboard doesn't work. The menu/home/back/search buttons are giving tactile feedback/vibration for the AOKP rom, but not for the cm9.
Both of these roms gave me similar problems. I don't know what I could have done wrong. Any help would be much appreciated.
-davestrrr
fixed with earlier version
I thought I should post here for posterity, it seems the 6/9/12 version for the Droid 4 is borked. I went back to an older version of cm9 from 5/29/12 kind of chose randomly from the archives, and everything worked. So stay away from those later builds until things get worked out.
OK, one last post for posterity in case someone searches the web and finds this error. I found that the 5/29 version of the cm9 mod for droid 4 had data connectivity issues, and I couldn't get 4G or 3G connection. After looking around some forums I found that the 5/19 version of this mod works for data, so I switched to this version, and it was able to get 4G. So the bottom line, for anyone looking to install ICS on a droid 4, go with the 5/19 version of the cm9 mod and avoid these problems. Thanks.
I saw the dim screen issue on mine with some early June build. Currently running 6/15 and it works fine, but I'm just using it to test apps (no sim card in phone, can't verify voice/text/mobile data working properly, though I imagine it's fine).
I did format /system and then wiped data/cache.
I've been experiencing random reboots since I bought my Developer Edition but today I think it hit me real hard with the random reboots in short intervals.
this kind of reboots happened to me both on completely stock and custom rom but today heavy reboots occurred when I was on Insert Coin 2.0.3 (S-Off).
According to someone's advice, I installed catlog and try to record the events until the phone reboots. So I post my logs here and hope some one could save me from this misery.
the first file was recorded with "write to disk every 200 lines" so it may miss some very last event when phone rebooted. The next ones were recorded with "write to disk every 100, 20 and 10 lines". I hope some devs could have a clue on what is happening with my phone.
I also save the log file AFTER phone reboot but they were too big to attach. If you think those might helo, I'll post them somewhere else.
Might be something to do with Xposed
BenPope said:
Might be something to do with Xposed
Click to expand...
Click to collapse
Yeah, I've noticed that some custom ROMs got issues with Xposed on S-Off device. However, as I mentioned earlier, this happened to me while I was on completely stock rom, too.
I've made a few observations and found out that I haven't got a single reboot on AOSP for a whole day but AOKP still gave me random reboots (not as frequent as on InsertCoin but still).
Any help would be very appreciated
might be worth trying to install sense rom again stock or custom and do full wipe, cache and dalvik. strange that an aosp rom works fine. must be something caused by a sense rom, drivers or framework. was this problem introduced when you started using 4.2.2 roms? have you updated to the new firmware.zip?
well, my habit of installing new roms is always do a full wipe so I think the cause of reboot should not be related to that.
After getting no reboot on AOSP roms (carbon, cm 10.1), I decided to go back on custom sense roms but no luck. reboots just came back no matter what roms I was on (renovate rev 45, insertcoin rev36, rayglobe 4.3).
I went to stock again with RUU dev edition (.16 one). Phone gave me a reboot right after I finished setting up (as new phone). However, it has been running stable up to now (3 hours).
Should the reboot have any thing to do with Sense, i'm wondering. I would be very thankful if any devs can help me on this issue. I'm willing to make as many logs as required or install any custom, stock roms if neccessary.
Sincere
hello, i have locked moto and wonder do i need 4.2.2 root to install this rom or 4.4 cause i get bootloop after installing the rom.
Are you currently running jellybean? Sounds like you are not running the KitKat kernel.
Sent from my XT1060 using Tapatalk
Same Bootloop
Hey Nitro,
Moto X VZW Dev.Ed.
Unlocked BL
TWRP 2.6.3.1
Stock rom 4.4.2
SuperSU
Rom Toolbox Pro for my needs
Had Eclipse installed and was running great. Screen started to flash between operations and loading apps. Thought it was just a misbehaving app, deleted everything I installed and it kept happening. Reinstalled the Eclipse ROM, no-joy. So I brought the phone back to complete stock. I was running on stock for about a week, the OTA came for 4.4.2 and I took it.
Flashed TWRP and installed SU again. When I go to install Eclipse 3.3.2 it shows that everything is loading correctly (love the "mounting your system like a horse"). When it restarts itself it gets stuck in a bootloop with just the Eclipse image. I've left the phone alone for a half hour at a time and it never completes (at 45 minutes on the latest install attempt). Downloaded from the primary and mirror and tried those, same issue, tried it dirty at first, then wiped the dalvik/cache. I've read the main ROM thread - nothing that I could find where someone got stuck in a bootloop like this. Just wanted to pick your brain and see what you thought.
^^^It's long, my bad. I just wanted to make sure you had every detail possible.
Really appreciate it, it's a great ROM when I don't jack things up.
d33pblue said:
Hey Nitro,
Moto X VZW Dev.Ed.
Unlocked BL
TWRP 2.6.3.1
Stock rom 4.4.2
SuperSU
Rom Toolbox Pro for my needs
Had Eclipse installed and was running great. Screen started to flash between operations and loading apps. Thought it was just a misbehaving app, deleted everything I installed and it kept happening. Reinstalled the Eclipse ROM, no-joy. So I brought the phone back to complete stock. I was running on stock for about a week, the OTA came for 4.4.2 and I took it.
Flashed TWRP and installed SU again. When I go to install Eclipse 3.3.2 it shows that everything is loading correctly (love the "mounting your system like a horse"). When it restarts itself it gets stuck in a bootloop with just the Eclipse image. I've left the phone alone for a half hour at a time and it never completes (at 45 minutes on the latest install attempt). Downloaded from the primary and mirror and tried those, same issue, tried it dirty at first, then wiped the dalvik/cache. I've read the main ROM thread - nothing that I could find where someone got stuck in a bootloop like this. Just wanted to pick your brain and see what you thought.
^^^It's long, my bad. I just wanted to make sure you had every detail possible.
Really appreciate it, it's a great ROM when I don't jack things up.
Click to expand...
Click to collapse
Did you do a factory reset wipe? Also, are you running the 4.4.2 kernel?
Sent from my HTC6525LVW using Tapatalk
Info
nitroglycerine33 said:
Did you do a factory reset wipe? Also, are you running the 4.4.2 kernel?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
I did not do a factory reset wipe the first time. I did the second time. Same situation.
The kernel I'm using is:
3.4.42-g3385454
- Jan 23 17:09
System Version:
164.55.2.ghost_verizon.Verizon.en.US
Build #:
KXA20.16-1.25.2
I appreciate you taking the time out to look at this, thank you.
Hi, I recently bought a Droid Turbo, and had the bootloader unlocked by Sunshine. The phone works wonderfully, but I'm having a few issues. Most notably, it takes ages(over 15 minutes) to boot when I'm using a custom rom. I'm specifically trying to use AOKP Android version 7.X. I've tried clearing cache, clearing ART cache, clearing modem, factory resetting, reflashing system, and nothing seems to be fixing it. At first I thought it was the ROM's fault, like maybe it was a common issue with the ROM, but I flashed Bliss to it, and had the same issue. One thing I should note is that it doesn't take very long to boot into the stock Verizon rom. Another issue I'm having is sometimes the orientation sensor doesn't work, It's not that big of a deal, but I thought it would be a good idea to include it. I remember my LG G2 having a similar issue because I had the wrong bootstack flashed, but I'm not sure if a similar context applies to the Droid Turbo.
Are you using the very latest modded TWRP from @bhb27? Not the crap from the official TWRP website, but from our official TWRP maintainer? 3.1.1_mod2 is the latest right now.
He knows what's best for our Quarks (he's a recognized XDA dev) and although he got us official status with TWRP over two years ago, for some reason they won't post TWRP with his tweaks that work best with custom ROMs. Some people using official TWRP can only boot to recovery, their phone won't even boot to their ROM directly. I helped someone with that just this week.
So, we ignore the official TWRP website and download his modded TWRP. This is the one you should be using:
twrp-3.1.1-mod_2-quark.img
https://androidfilehost.com/?w=files&flid=39562
If you are using that, then I don't know. You could also try other ROMs just to see. AOKP is in the top three, in my opinion, but wouldn't hurt to test with something else.
[ROMs][Quarks][List for Moto Maxx and Droid Turbo]
Hey Guy's
So for my 626g I was experimenting with some custom roms. And I've came across this rom Viper OS V2.1 - 7.1.2 - PYTHON by Arkanium.
At first it was taking for ever to start at the first stept of setup... it asked for a backup or as a fresh start... and it doesn't matter if fresh or backup... continuous loop.
That's if you flash zip in recovery for gapps. If without gapps than all goes fast and without interruptions. But it's still in yearly stage and camera app not working... also phone service also the data... still lot's of bugs. If only someone could look at this build and maybe get all together. Thanks a lot for your support and work put in fixing lot's of builds and giving hope to our phones.
The link from where I found it .... getdroidtips.com/viperos-htc-desire-626g