Boot looping on normal boot, but no boot looping on fast boot. RUU install didn't fix

[kwilson7770]

Ok, so I have a boot looping problem going on with my HTC Incredible (1). I originally had much more problems that I managed to solve before having to post this thread. So if you don’t want to be in my shoes and potentially brick your phone, don't do this:

I installed ClockworkMod so I could have root access on my phone and enjoy having full control of something that I purchased. Well I went through quite the mess to "fix" my phone (history below) but eventually, I had a S-ON phone, with a radio of 2.15.10.XX.XX (I don't remember the last two numbers), and ClockworkMod installed for the recovery. To my disappointment I discovered that even though the SuperUser app was installed from the ClockworkMod and programs still requested root access from the app, I didn't actually have root access to my phone. Verizon must have patched the vulnerability which is highly annoying. So I decided to restore a backup I made of my rooted phone before I accepted any of the Verizon updates. Well the restored failed on the SD card (which was kind of weird, but without root access I can kind of understand). So I was hoping that it wasn't a big deal, but it probably was.

The first issue I noticed right away was my phone was boot looping. It would vibrate when turning on, show the 'HTC Incredible™' screen wait about 5 seconds, and reboot. It never got to the HTC Quietly Brilliant screen. The second issue I noticed is when I ran ClockworkMod to use their option to delete the SD card, it would fail. So I tried to mount my SD card and that also failed. I eventually fixed my SD card issue by following the directions here (http://forum.xda-developers.com/show....php?t=1772312).

So after fixing my SD card the first then I was going to do was install a factory image using a RUU or zip file. My hope was that it would fix everything and I could try the new HTC Unlock Bootloader method (http://htcdev.com/bootloader). So I put the latest Verizon image (4.06.605.2) zip file on my SD card and installed it (it seemed to be successfully... it said it finished and it asked if I wanted to reboot my phone. So I did and the phone then booted into the HTC recovery, did something for a second or two, and rebooted. After that it went into boot looping. So I am not sure if the HTC recovery was able to install whatever it was trying to install). Now I am left with the boot looping problem. Now the boot looping problem is somewhat by-passable if I have my phone plugged into my computer. It will attempt to install drivers twice, failing both times, and then boot up. However, with fast boot enabled, the phone does not have any boot looping issues that I have experienced (so far). So there is an issue between what the normal boot does and what the fast boot does that is causing my boot looping. I have no idea how to fix this since the latest factory image did not fix it (installed it twice with same symptoms as above).

OK this is a history of everything I did to lead up to my current problem. This is long so you can skip to the bottom for phone specs. This is just something I wish I would of read before I put myself in the situation I am in now.

HISTORY

I rooted my phone about a year ago (using radio 2.15.00.07.28) it was super easy since it was automated by unrevoked 3. I eventually received an annoying notification that my phone had an update. It was also conveniently the same time my phone starting glitching. I personally believe that Verizon is installing hot fixes to break people's phones that have ClockworkMod on it or aren't running the latest update. Whenever I placed a call or received a call, my phone would lock up the screen. When my screen was locked up I was able to still talk and hear the conversation, but I could not access the dialer to press 1 for English or to hang out. There was no way to unlock the screen (trust me I tried everything) so when the phone call ended I had to pull the battery to be able to use my phone again. Since I was S-OFF at the time I figured that installing CyanogenMod 7 would fix this glitch I was having. Well it didn't. So I then tried using different dialer apps, but nothing fixed my problem. After a while I gave up researching the Internet to see if someone else had the same issue that I had, and they actually fixed it. So I decided to restore my phone to the Verizon factory image that was using the 2.15.00.07.28 radio with S-ON. Oddly enough installing it fixed my calling issue. Not much longer after installing the outdated image, my phone started prompting me, telling me to install a new update. And you probably guessed it, but shortly thereafter my phone had the same calling glitch again. So I deiced to install the update to see what would happen (Yes, I realize now how stupid that was... I was S-ON and I installed an official update that made my radio too new to be rooted. I learned this the hard way). This may not surprise you, but the update fixed my phone calling glitch. Hmmm, this makes me wonder, is Verizon INTENTIALLY breaking phones so you will install their update to a non-rootable image? Well one day my DSL Internet went out and I wanted to use my phone Internet for my laptop. Well this is when I discovered that I really don't have root access even though the SuperUser app is there. On top of that there was a new update that came out that I kept on ignoring. So as you would expected, a new glitched arrived on my phone. While in any type of text field (text messages, web browser, notes, etcetera) the cursor would scroll to the left about once every 3-5 seconds. When I wasn't in a text editor, it would auto-select things starting from where I selected something last and start going to the left. Probably another intentional problem caused by Verizon (this problem was also fixed by updating to the newest software version Verizon had to offer, although I wasn't at this update yet, I just wanted to let you know). So I figured I would restore a backup I made with ClockworkMod. I made this backup before accepting any Verizon updates (factory image with ClockworkMod installed). This is when everything fell apart. This leads up to what I explained above. Below are the phone specs

HISTORY

Phone Information:

HTC Incredible (The first one)
Model Number - ADR6300
Android Version - 2.3.4
Baseband Version (radio) - 2.15.10.07.07
Software Number - 4.06.605.2
Stock Recovery - I do not have ClockworkMod installed right now

Let me know if you need any more information for the issue I am having.

New Problem:

Update

My SD card wouldn't mount, but now the SD card is fixed

[Ads]

[Nyobie]

What size (capacity) SD card?

Sent from my unrooted HTC Incredible 4G on Verizon's 4G LTE Network (waiting for S-OFF to become available)

[kwilson7770]

What size (capacity) SD card?

Sent from my unrooted HTC Incredible 4G on Verizon's 4G LTE Network (waiting for S-OFF to become available)

My Micro SD card is 2GB

[Nyobie]

Ok. I'm glad it's fixed!

Sent from my unrooted HTC Incredible 4G on Verizon's 4G LTE Network (waiting for S-OFF to become available)

[kwilson7770]

My SD card is fixed, but not the boot looping