[TUT][CDMA]ROM randomly rebooting? Here are some fixes! (BACK IN BUSINESS!!! :D)

NOTE: This one's a big one if you can't tell! Everyone give a round of applause to simonsimons34 for tracking down the issue. What does this mean? Well, there may not be a need to ever downgrade using the RUU. If you go here (you really can't miss that big, bolded "here"), you will see that he determined the issue is caused by:

a bad battery driver function in the kernel

Click to expand...

Click to collapse

He also took the liberty of building a kernel compatible with 4.2 and putting in a commit for fixing the kernel to work with the newer radio at GitHub. Any ROM builders who see this, please do check it out. As far as everything goes, I haven't personally tested it but I do always encourage people to try it out. Simon has been a great supporter and kernel builder for our device so I have faith that he hath found the Holy Grail. 'Course my thread will have no more existential purpose, BUT it is a great resource so as it is, I will leave it up for the general perusal of the community. Have a great week everybody and I look forward to a new flood of development.

Exciting news y'all! This thread has been stickied! [Hopefully] this will allow continued support and growth of the thread. My personal philosophy is that anything I post shouldn't be locked down to what I know or believe in, so I encourage any reader to put forth their input. What does that mean? It means that if you have a suggestion, by all means inbox me your thoughts. I'm open to continual development of this tutorial through community teamwork. Have a good day everyone!
-------------------------------------------------------------------------------------------------------
Here are some common reasons why your phone will randomly reboot (bootloop). You should only use an RUU (the methods below the "=" signs) if NOTHING ELSE WORKS (because the RUU does a factory wipe of the phone).

Common Problems:
I switched from another ROM and now my phone keeps rebooting...
There are several factors in play here. The commonly accepted fix is backing up your data and doing a full wipe (cache, dalvik cache, system, data) followed by reflashing your ROM.

I upgraded my ROM from blah blah version to blah blah version (ex. 4.0.x to 4.1.x)...
This is because your old Ice Cream Sandwich system stuff may not be compatible with JellyBean (in the case of the example). Wipe system and the caches (dalvik & cache) followed by reflashing your ROM.

I upgraded my ROM (within the same version) and it keeps rebooting...
Every time I upgrade my ROM, I wipe cache. If something funky happens, just wipe system and reflash your ROM.

I flashed a ROM and it won't boot at all...
Either you flashed a ROM for a different device, you flashed a kernel for another device, OR you didn't flash a kernel at all. Make sure everything is for your phone (the HTC One V on Virgin Mobile is the CDMA version known as "PrimoC" whereas the GSM version is the "PrimoU").
=============================

NOTE: This guide is for the One V!

I know the feeling! You're all excited because you just unlocked your One V's bootloader, flashed a recovery, and flashed a steamin' hot new ROM. You boot up for the first time and get ecstatic, the tension building as you put in your Gmail info. You finish the start up but OH NO!!! Your phone reboots! You blame yourself... you blame your cat... you blame your wife... you blame the war in the Middle East. You think, I must've done something wrong! Stupid, stupid, stupid! Don't fret! Take my experience with this quite seriously (despite the jokes). For 2 weeks, I retraced my steps and tried EVERYTHING! I thought it was just the ROM's problem, so I flashed one after another to the same end. Finally, I decided to post a new thread asking for help. Nothing became of the first thread, so I posted a second one. To my great relief, along trotted Curiousn00b. After shoving me in the correct direction, I figured out the rest. A big thanks by the way, Curiousn00b! The following is the method that I used to get my phone to finally run a ROM. Also, a thanks to CafeKampuchia for the quoted directions below.

A few things to make sure you have:
Windows (with Administrator's priveleges)
Fastboot installed and working
Your phone (duh!)
A USB cable
Time and patience

The following quote is from CafeKampuchia's thread over here.

NOTE ABOUT THE FOLLOWING PARAGRAPH: jmztaylor's site is now legally able to host the RUUs again so the download link is right here*
In support of jmztaylor and all of his work for this device, I have decided to also include his website in this thread... *here is the download directory for the HTC One (Primo) device RUUs. I'm not sure if this bug effects other Primo devices, so this especially pertains to the PrimoC (HTC One V CDMA). Thanks jmz for the tip!

Solution #1

CafeKampuchia said:

Here we go:

1. Download the correct RUU for your device from Football's Primo Shipped ROM Collection.

2. Charge the battery above 50% or for at least one hour. If the battery dies during the flashing process, you could hard brick the phone!

3. Run the RUU until the wizard comes up. While the RUU wizard is open, find the temporary folder it created. (Open Explorer in Windows and type %temp% in the navigation bar.) There will be two folders with long encrypted names. In one of them you will find ROM.zip. Open it with 7zip and extract recovery.img or recovery_signed.img. Put it in the location were you've installed Android SDK tools. This is the stock HTC Recovery and it is needed to run the RUU.

4. Boot the phone into bootloader (power off, hold down volume and press power) and highlight FASTBOOT using the volume rocker and pressing power. Then connect the USB cable. You should see FASTBOOT USB.

5. Open a command prompt in Windows and navigate to the folder where you installed Android SDK tools. Flash the stock recovery extracted in step 3 above using the following command:

Code:

fastboot flash recovery recovery.img

or

Code:

fastboot flash recovery recovery_signed.img

6. Relock the bootloader using the following command:

Code:

fastboot oem lock

Click to expand...

Click to collapse

Thus far you should have the stock recovery back and be bootlocked again. Now, back in fastboot mode, you should already be connected to your computer via USB (if you disconnected, just reconnect it and wait for "FASTBOOT" to change to "FASTBOOT USB")

Run this command:

Next, start up the RUU program again and let it run through without interruption. After this process is done, the phone should boot up to the stock ROM. Let it do its thing, but this time don't do the OTA update. From here, just unlock the bootloader again, install your recovery of choice, and install your ROM of choice or reroot the stock ROM (I know some want to keep it stock).

As also pointed out by RoyalYeo, you can let HBOOT take care of the problem:

Solution #2

My hunch was correct, the .0928 Radio was causing the bootloop... I managed to flash the 521_2 radio, and now the Sick kernel is working and AOKP JB runs great.

Steps (on windoze):

1) Download the RUU
2) Run the .exe, wait for it to open the first wizard screen.
3) Open a file explorer in c:\users\yourname\AppData\Local\Temp\New_Directory _With_Some_Hexadecimal_name
4) Locate `rom.zip`, copy to the root directory of your sd card, and rename it to PK76IMG.zip
5) Reboot to bootloader, connect usb, and `fastboot oem lock` in cmd shell, at which point it'll reboot
6) Get back to HBOOT, wait for it to notice PK76IMG, confirm, make a pot of coffee, check back in 5-10 minutes.
7) After reboot, phone should now show a 1.00.00.521_2 radio... re-unlock the bootloader in fastboot, re-flash TWRP or whatever, and you should be good to go.

Lemme know if you get it working...

Click to expand...

Click to collapse

My personal solution (Solution #1) is the more technical side of things and also exposes you to the nitty-gritty. Having said this, #1 is quite touchy because if you do something wrong, there is a good chance that you could... well uh, brick your phone to be quite honest. On the other hand, #1 requires no SD card (given the event that your SD card won't mount, your SD reader is broken, or you just plain don't have an SD card). Ultimately, the choice is up to you.

robaho said:

Won't work if the ota is already applied from the factory.

Click to expand...

Click to collapse

Or if you applied the OTA via the popup window saying, "Blah, blah, blah, new update available."

mastertr said:

EDIT#2: I still wasn't able to escape the rebooting, even after doing this. I installed AOKP 10 and it stayed on the Initiating Swagger screen while rebooting every minute or so...

Click to expand...

Click to collapse

Did you relock the bootloader before or after flashing PK76IMG.zip? This does make a difference. My suggestion is just to go back through and try again following everything to a tee. Doesn't always work the first time.