Any resolution to this problem? This has been reported in several threads (link 1, link 2, link 3, need I give more?)
I'm also experiencing the same problem. I installed Paranoid Android (per instructions here) and am now experiencing the same problem. After flashing, the phone continuously reboots. I am using an HTC One V (CDMA) from the US. I also flashed the JB 4.1.2 gapps with the ROM flash process.
When it boots, I receive two errors: "Unfortunately, android.process.acore has stopped working" and "Unfortunately, Contacts has stopped working". When I lock the screen, it reboots. When I try using it, it reboots after 30 seconds. If I just leave it alone, it reboots.
I have also tried several kernels with this same ROM (kernel that comes with the ROM, SuperSick [found here], and stock CM10) and they all just produced the same behavior.
I've looked all around. Some possibilities are: bad kernel, memory (RAM or otherwise) running out, bad install of ROM, or something no one has yet to define. I don't think its a bad kernel because this happens in 3 different ones. I don't think it's a memory issue because I lowered the CPU clockspeed and the phone has plenty of storage memory, and I've also flashed AOKP with the same results which rules out a bad ROM install.
I've wiped cache, system, data, and dalvik and followed all instructions as given to get a completely fresh installation. No avail. I realize that the One V isn't very popular, and there is only a limited amount of support for it but could anyone shed some light as to what the problem could be?? Perhaps some of the original devs who made the ROMs can help out us lowly fools who can't get it to work? I thank anyone in advance for being awesome and at least trying to help.
You may have to flash the old RUU. Look in the General subforum for a thread about phone rebooting after one minute.
sounds like you did the OTA update and have the new radio version, you need to RUU back to stock and dont get the OTA.
I'll try.
Thanks both of you! I will try flashing the RUU and I'll make sure to not install the OTA update. I'll post later with my results.
...
So... I flashed the RUU on the phone again. I again carefully followed instructions on how to flash ROMs (AOKP and Paranoid) and it simply doesn't boot. AOKP's ROM only starts up to a black screen. Paranoid boots to the boot screen animation and just hangs... I've used stock kernels, and tried the SuperSick kernel with both. No progress. Any other ideas?
Try the latest version of cm10 with the latest version super sick kennel. That's what I'm running. AOKP has a few versions that boot to a black screen. If you want AOKP use the latest stable version.
Awesome!
riggerman0421 said:
Try the latest version of cm10 with the latest version super sick kennel. That's what I'm running. AOKP has a few versions that boot to a black screen. If you want AOKP use the latest stable version.
Click to expand...
Click to collapse
Riggerman0421, thanks a ton for the suggestion!! It worked! Despite not being able to use the other roms, I think I can settle with using CM10.
htc one v
filoxo said:
Riggerman0421, thanks a ton for the suggestion!! It worked! Despite not being able to use the other roms, I think I can settle with using CM10.
Click to expand...
Click to collapse
Hey I am having the same problem as you with my htc one v. What did you do exactly to fix this?
lytesson said:
Hey I am having the same problem as you with my htc one v. What did you do exactly to fix this?
Click to expand...
Click to collapse
You have to RUU your device back to the original radio version; it was changed when you accepted the OTA update. That means that you're going to have to flash it to complete stock (no recovery, HTC Sense, booloader relocked, etc.) using the RUU. The forum I found that had all of the different RUUs was deleted unfortunately. You'll have to do careful research for the RUU for your specific device. I only know that Virgin Mobile in the U.S. uses the Sprint towers, so the RUU I used was titled "RUU_PRIMO_C_ICS_40A_Sprint_WWE_VM_1.08.652.6_Radio_1.00.00.0521_2_NV_VM_3.46_0503_PRL61008_release_262414_signed". Just a quick search on XDA and found this forum that has a download link to the RUU you would need for VM [CDMA] phone (read the comments); you can also look around yourself to make sure you have the right one.
You can find specific instructions on how to RUU your device at this awesome forum. It should only take, literally, 15-20 minutes.
After that is done, you will need to unlock your bootloader again and then you're ready to move on to bigger and better ROMs.
filoxo said:
You have to RUU your device back to the original radio version; it was changed when you accepted the OTA update. That means that you're going to have to flash it to complete stock (no recovery, HTC Sense, booloader relocked, etc.) using the RUU. The forum I found that had all of the different RUUs was deleted unfortunately. You'll have to do careful research for the RUU for your specific device. I only know that Virgin Mobile in the U.S. uses the Sprint towers, so the RUU I used was titled "RUU_PRIMO_C_ICS_40A_Sprint_WWE_VM_1.08.652.6_Radio_1.00.00.0521_2_NV_VM_3.46_0503_PRL61008_release_262414_signed". Just a quick search on XDA and found this forum that has a download link to the RUU you would need for VM [CDMA] phone (read the comments); you can also look around yourself to make sure you have the right one.
You can find specific instructions on how to RUU your device at this awesome forum. It should only take, literally, 15-20 minutes.
After that is done, you will need to unlock your bootloader again and then you're ready to move on to bigger and better ROMs.
Click to expand...
Click to collapse
So, this happend to my htc and I ruu'ed back to stock, after continunously trying to install roms with constant bootloops. I did the ota update again. So if I want to install a custom rom your saying DONT do the ota after ruu'ing then install one after rooting?
I've got a similar issue (virgin mobile HTC One V)
I currently have TWRP recovery installed, and I attempted to flash the jellybean CM10 as well as the AOKP rom, and I got as far as the unicorn and I actually manged to get the phone to boot to the main screen with all the icons, but it would constantly reboot after being on for maybe a minute
I tried flashing everything back to stock including restoring a backup I had previously taken with TWRP, but no luck
I also tried flashing the stock rom downloaded somewhere here on XDA and I even flashed the stock recovery, but all I got was constant rebooting.
it would get as far as the startup animation and then reboot indefinitely
I'm at a total loss here. I've seen a few links with some resources that look like they might have been helpful (like on this thread) but the links are dead, and I also read somewhere that HTC was putting the kibosh on a site that had some stock roms.
I'd prefer to get jellybean working on my phone, but ultimately, I just want a working phone.
I've followed the process of installing the rom - some instructions said to flash the boot img before flashing the rom, some say after
I've tried both methods
I went into recovery, mounted the usbmsd and copied the rom, and used recovery to install the rom after having cleared the cache, davlik cache and wiping the data (factory reset)
I also installed the gapps package after the rom, but I don't think that's critical to getting it to just boot.
The OTA update reboots were fixed in the latest 4.2 SickleKernels.
Sent from my One V using Tapatalk 2
bheadrick said:
I currently have TWRP recovery installed, and I attempted to flash the jellybean CM10 as well as the AOKP rom, and I got as far as the unicorn and I actually manged to get the phone to boot to the main screen with all the icons, but it would constantly reboot after being on for maybe a minute
I tried flashing everything back to stock including restoring a backup I had previously taken with TWRP, but no luck
I also tried flashing the stock rom downloaded somewhere here on XDA and I even flashed the stock recovery, but all I got was constant rebooting.
it would get as far as the startup animation and then reboot indefinitely
I'm at a total loss here. I've seen a few links with some resources that look like they might have been helpful (like on this thread) but the links are dead, and I also read somewhere that HTC was putting the kibosh on a site that had some stock roms.
I'd prefer to get jellybean working on my phone, but ultimately, I just want a working phone.
I've followed the process of installing the rom - some instructions said to flash the boot img before flashing the rom, some say after
I've tried both methods
I went into recovery, mounted the usbmsd and copied the rom, and used recovery to install the rom after having cleared the cache, davlik cache and wiping the data (factory reset)
I also installed the gapps package after the rom, but I don't think that's critical to getting it to just boot.
Click to expand...
Click to collapse
I think I'm having the same problem. The phone boots, gets as far as the "this build is for development purposes..." and then hangs for a few minutes and restarts, over and over. The flash with fastboot seemed to work fine and reported no errors.
EpicLordPhone said:
So, this happend to my htc and I ruu'ed back to stock, after continunously trying to install roms with constant bootloops. I did the ota update again. So if I want to install a custom rom your saying DONT do the ota after ruu'ing then install one after rooting?
Click to expand...
Click to collapse
Yes. Do NOT install the update if you want to flash another ROM onto your device. Use the RUU to get the device back to factory; this will restore the original radio version. Then go through the steps to unlock the bootloader, root, and flash your ROM as desired. There are other forums which explain the mentioned processes better.
BeyondExistence says that this is fixed with a "4.2 SickleKernel", but as far as I'm aware there are no JB 4.2 ROMs for the HTC One V. Maybe a little more information would be in order?
Bheadrick:
I'm not quite sure what you mean when you say you flashed the stock recovery. The One V doesn't have a recovery when everything is stock.
You will have to RUU your device back (have you read any of the posts in this and other forums??). The process will reinstall the stock rom, relock your bootloader, remove the recovery, etc.
I recommend that you use Paranoid android's rom with the latest SuperSick kernel. Its been my favorite and most stable build I've used.
Sent from my Nexus 7 using xda app-developers app
So I found what BeyondExistence might have been talking about (for those of you who care/are currently having the bootloop problem and would rather go with this route). Its called RhythmicRom. This is a 4.2.2 ROM and it has some cool things for users switching from Sense to a more-pure Android [Link here]. Its based off of CM10.1 for the One V and it includes the BeatsAudio app (which most ROMs don't, as far as I know).
The reason I think that this is worth mentioning is because whoever runs into this bootlooping problem can simply SKIP the RUU process and just move onto this ROM. Hit thanks if this helped!
Newest OTA update.
As some of you may have seen, there's an even newer OTA Update available through the stock ROM. As always, this will cause problems when you try to flash a different kernel, resulting in bootlooping (can anyone who has done the newest update confirm?). Anyway, I've also read that this update also updates your hboot (which, since I haven't and will not apply the update, don't know why it would impede you from flashing any other ROM/kernel but it does) and radio version.
I've looked for additional ROMs who try and make their builds compatible, but so far only RhythmicRom has done anything worthwhile (in my opinion). His latest v 1.3 build will be out soon, and I highly recommend it.
If you flashed both OTA updates, then please be sure to include that when making any post.
filoxo said:
As some of you may have seen, there's an even newer OTA Update available through the stock ROM. As always, this will cause problems when you try to flash a different kernel, resulting in bootlooping (can anyone who has done the newest update confirm?). Anyway, I've also read that this update also updates your hboot (which, since I haven't and will not apply the update, don't know why it would impede you from flashing any other ROM/kernel but it does) and radio version.
I've looked for additional ROMs who try and make their builds compatible, but so far only RhythmicRom has done anything worthwhile (in my opinion). His latest v 1.3 build will be out soon, and I highly recommend it.
If you flashed both OTA updates, then please be sure to include that when making any post.
Click to expand...
Click to collapse
I got my One V at the end of December and did the OTA update at the beginning of April. Last week, I decided to try messing with loading some different ROMs and have encountered all of the problems you've mentioned (e.g., boot-looping, inability to RUU back to stock). I have successfully gotten RhythmicRom to load using this OTA_support.zip (which has been incorporated into the regular release since I flashed it). I have also gotten the most recent version of PACman v22.1 to run (using the same kernel as RhythmicRom) without boot-looping, but the performance hasn't been great (browser crashes frequently and it seems like the launcher has to restart a lot). User demi_fiend has said that the PACman ROM will work using the CodefireX kernel from user BeyondExistence.
I had also tried to revert back to my stock CWM recovery, but it had the boot-loop problem too. However, demi_fiend has also informed me that you can revert to a stock backup by using the boot.img file that is located in the backup folder. I haven't had the chance to verify this, but I wouldn't be surprised if it were true.
It's a bit of a pickle being unable to revert back to previous radio versions, but there is hope that some of the devs will incorporate this issue into their new builds.
tallnproud said:
I got my One V at the end of December and did the OTA update at the beginning of April. Last week, I decided to try messing with loading some different ROMs and have encountered all of the problems you've mentioned (e.g., boot-looping, inability to RUU back to stock). I have successfully gotten RhythmicRom to load using this OTA_support.zip (which has been incorporated into the regular release since I flashed it). I have also gotten the most recent version of PACman v22.1 to run (using the same kernel as RhythmicRom) without boot-looping, but the performance hasn't been great (browser crashes frequently and it seems like the launcher has to restart a lot). User demi_fiend has said that the PACman ROM will work using the CodefireX kernel from user BeyondExistence.
I had also tried to revert back to my stock CWM recovery, but it had the boot-loop problem too. However, demi_fiend has also informed me that you can revert to a stock backup by using the boot.img file that is located in the backup folder. I haven't had the chance to verify this, but I wouldn't be surprised if it were true.
It's a bit of a pickle being unable to revert back to previous radio versions, but there is hope that some of the devs will incorporate this issue into their new builds.
Click to expand...
Click to collapse
Did you flash stock recovery and lock bootloader before running RUU?
Lsesp said:
Did you flash stock recovery and lock bootloader before running RUU?
Click to expand...
Click to collapse
I had flashed my stock recovery (although it was still boot-looping), and I did re-lock the bootloader before running the RUU.
I used the instructions found here.
Hey guys i have a samsung i747 from rogers and i'm trying to install custom roms. I've obviously rooted it and installed CM recovery and downloaded roms and gapps. So far i've tried liquidsmooth 2.8. Avatar Rom. Cyanogen. but nothing seems to be working. Every single one of the them keeps telling me that my setup wizard had crashed and my gapps weren't working. I earlier had a Status 7 error installing cyano and avatar so i flashed d2att's 07.05.13 kernel, but that didn't seem to help. I tried running a different version of the clockworkmod recovery too. I've hardly ever "dirty" flashed. Someone help me out here i hate custom roms!!!
Wipe
Data
Cache
Delvik Cache
and Factory Reset.
Make sure you're flashing the correct GApps for android 4.2.x
Flashing a kernel has nothing to do with a status 7 error.
A status 7 error points to a outdated recovery or bootloader.
You should get ANY errors.
If you hate flashing why do it??
I honestly don't get that...
If you're here to make your phone to look "cool" you're in the wrong place.
Galaxy S3 / AoCP / V4A / Turbocharged
duoblade said:
Hey guys i have a samsung i747 from rogers and i'm trying to install custom roms. I've obviously rooted it and installed CM recovery and downloaded roms and gapps. So far i've tried liquidsmooth 2.8. Avatar Rom. Cyanogen. but nothing seems to be working. Every single one of the them keeps telling me that my setup wizard had crashed and my gapps weren't working. I earlier had a Status 7 error installing cyano and avatar so i flashed d2att's 07.05.13 kernel, but that didn't seem to help. I tried running a different version of the clockworkmod recovery too. I've hardly ever "dirty" flashed. Someone help me out here i hate custom roms!!!
Click to expand...
Click to collapse
I would get TWRP recovery.. wipe dalvik / factory reset. and re-flash your rom.. I'm on Rogers as well and the status 7 error means that your recovery / bootloader is outdated.
So start by getting the most recent TWRP. I got it from goo.
btw: if you don't like custom rom, i suggest going to the sammobile site and getting your factory firmware. Use Odin to reflash back to stock. That should solve your hiatus towards custom roms...
correction
thanks guys but idk i just tried flashing a custom rom at 4.1.2 and then went up from the there and it was fine... for the status 7 i just adjusted the coding for it so it didn`t have to check the model and this was typed up like at like 2 in the morning where i`m from i meant to say i hate stock roms LMAO:silly:
duoblade said:
thanks guys but idk i just tried flashing a custom rom at 4.1.2 and then went up from the there and it was fine... for the status 7 i just adjusted the coding for it so it didn`t have to check the model and this was typed up like at like 2 in the morning where i`m from i meant to say i hate stock roms LMAO:silly:
Click to expand...
Click to collapse
sure but its fine custom Roms can be a Pain in the A$$ thats why am running stock rooted stable, great battery life, fast like custom roms, everything is perfect give a try with stock rooted no issues or problems like custom roms
Synergy Rom 4.1.2 w/ Ziggy Kernel using ATT Galaxy S3
HAPPY ROOTIN :cyclops:
this is just weird, as i have been installing custom ROM like crazy...
but for some time i was on CM 10.1.2 and didnt install any custom ROM, but i felt like coming back to TW based ROMs, so tried installing DeTmobilized 1.5, but phone stuck at boot screen, i tried to restart by pulling battery out but phone displayed "encryption failed" and kept on showing phone.apk stopped working (something similar). so i decided to ODIN to stock and start fresh, this time i tried installed Dandroid 3.8.1 and it worked, so i thought of giving DeTmobilized one more try, but again it got stuck at samsung letters at the boot.
so i decided to stick with Dandroid for a while, but now i cannot install that too. it gets stuck while booting. but if i ODIN to stock everything works fine on stock firmware, its only the custom ROMs that are not working.
i also tried repartitioning using PIT file along with stock md5 hoping that would solve this issue, but it hasnt.
i need help, i cannot stay on stock ROM.
thank you.
chirantan.f said:
this is just weird, as i have been installing custom ROM like crazy...
but for some time i was on CM 10.1.2 and didnt install any custom ROM, but i felt like coming back to TW based ROMs, so tried installing DeTmobilized 1.5, but phone stuck at boot screen, i tried to restart by pulling battery out but phone displayed "encryption failed" and kept on showing phone.apk stopped working (something similar). so i decided to ODIN to stock and start fresh, this time i tried installed Dandroid 3.8.1 and it worked, so i thought of giving DeTmobilized one more try, but again it got stuck at samsung letters at the boot.
so i decided to stick with Dandroid for a while, but now i cannot install that too. it gets stuck while booting. but if i ODIN to stock everything works fine on stock firmware, its only the custom ROMs that are not working.
i also tried repartitioning using PIT file along with stock md5 hoping that would solve this issue, but it hasnt.
i need help, i cannot stay on stock ROM.
thank you.
Click to expand...
Click to collapse
boot into recovery and wipe cache partition along with davik, that should fix the stuck
also do remember first boot will always take a while
also make sure you're using the latest custom recovery (either twrp or cwm)
i would also like to note here that i tried installing AOSP based ROMs also, and AOKP didnt work, got stuck at nexus like boot animation forever, but when i tried installing CM10.1.2 (which is what i was running when i tried to get back to TW based ROM) it worked perfectly, so for now i am back to CM, but i would really get back to flashing different ROMs and trying them out. just makes me wonder if CM is the reason i am not able to install anything else, just a thought...
has anybody else tried going to any other ROMs from CM 10.1.2?
your help is appreciated!
pcshano said:
boot into recovery and wipe cache partition along with davik, that should fix the stuck
also do remember first boot will always take a while
Click to expand...
Click to collapse
thanks for your reply, but i have tried doing that, i also wipe data and system along with cache and dalvik before installing any new ROM.
pcshano said:
boot into recovery and wipe cache partition along with davik, that should fix the stuck
also do remember first boot will always take a while
also make sure you're using the latest custom recovery (either twrp or cwm)
Click to expand...
Click to collapse
i have latest recovery , TWRP 2.6.0.0 and i have given more than an hour to boot up and still nothing. i have been flashing ROMs like an addict since i got this phone last year, but when CM 10.1 stable was released i stayed on it till today, but now i cannot install any other ROM, i can odin to stock 4.1.1 ROM or install cm 10.1.2 which i did just now, but no other ROM, either TW based on AOSP based is working...which is very weird for me.
Were you able to fix this issue at all? I am facing the same issue, in my case, the phone was encrypted on stock TW. I roooted and put in CM 10.1.2 and now when I try installing Dandroid, the install itself would work but I am struck at the "type password to unlock the screen". If I reflash CM10.1.2, I can login fine. Any pointers?