Cyanogen 6.1.2 bootloop on rooted 2.2

killerocker

Member
Jan 18, 2011
8
0
0
I downloaded Cyanogen 6.1.2 from ROM Manager and it installs successfully every time that ive tried it. (12 times now) but it just stays stuck in the bootloop every time. Any suggestions for how to fix this situation?
 
Yes, make SURE you wipe data and cache. It should first ask you if you want Google apps then it should ask you if you want to wipe data and cache. But beware, you'll lose all your apps. You should get titanium backup and backup all your apps.

And please, please don't forget to do a nandroid backup. I don't wanna see you lose your phone. I'll be sad (lol). Good luck!

Sent from my HTC EVO 4G
 
I had lots of problems with CM6 but I think this was largely due to issues with the 3.x version of ClockWork that ROM Manager was using at the time. I have read about problems from other users with the 2.6 Clockwork recovery and they were attempting to go back to 2.5 clockwork to see if that fixed their issues. Since all of my issues with CM6, I am now running Amon_RA 2.2.1 recovery and have tried out several other ROMs (VaelPak 3.0 and Myn's 2.2 RLS5) without issue. Both were rock solid for over a week. I haven't been brave enough to go back to CM6 yet using Amon_RA recovery, so not completly sure my problems were totally due to Clockwork or not. This is just my guess. I like the Cyanogen ROMs the most out of all the ROMs I have used but the instability I experienced has kept me from going back.
 
definitely a noob on flashing, but have experience on the Palm Pre rooting past. The problem I'm getting is getting stuck with the red triangle. Have done a factory reset this morning and same problems, using Rom Manager. Trying to get Gingerbread and maybe some clocking settings changed, but there's just sooo much info out there.

I have gained root by z4root download to the SD card and used titanium backup so I should be good there, but what would be the best next step for me guys?

My problem also seems to not just be the Clockwork Recovery as when I power down and use the volume/power combo to boot to recovery, I get the red triangle. Any ideas based on this???
 
Last edited:
definitely a noob on flashing, but have experience on the Palm Pre rooting past. The problem I'm getting is getting stuck with the red triangle. Have done a factory reset this morning and same problems, using Rom Manager. Trying to get Gingerbread and maybe some clocking settings changed, but there's just sooo much info out there.

I have gained root by z4root download to the SD card and used titanium backup so I should be good there, but what would be the best next step for me guys?

My problem also seems to not just be the Clockwork Recovery as when I power down and use the volume/power combo to boot to recovery, I get the red triangle. Any ideas based on this???

I'm not sure what you're talking about with rooting the Palm Pre. Gaining developer access on the Palm Pre took about as long as it takes to open an option screen, and flip the switch, then reboot. Factory controls ALLOWED you to get developer mode access.

Rooting this phone is different in nature because of the factory controls that do not allow you superuser access by default.

Anyway, z4root is temporary. If you want to flash a ROM, I suggest following what's listed in this thread: http://forum.androidcentral.com/htc...-help-info-asking-help-updated-1-24-11-a.html

You'll want to check to see what your hboot and software version is. Then follow along that thread with rooting instructions.
 
  • Like
Reactions: 2CupsWithString
As I'm reading more into this, and thanks for the obvious comment about it being different to root Android than WebOS, it appears my problem does not have anything to do with how I have used Z4Root, but I cannot go into recovery mode at all without getting the triangle.

Anyone (that can be helpful) with an idea of what I can do to find out what is causing this boot issue?
 
As I'm reading more into this, and thanks for the obvious comment about it being different to root Android than WebOS, it appears my problem does not have anything to do with how I have used Z4Root, but I cannot go into recovery mode at all without getting the triangle.

Anyone (that can be helpful) with an idea of what I can do to find out what is causing this boot issue?

Wow, thanks for the sarcasm. At the time that I posted, it didn't seem like you knew the difference between webOS and Android, hence why I made my post.

Actually, you'll kinda have to provide some more information than you currently are. You mentioned that you used z4root, did you do anything else?

I don't see where you mentioned you flashed a recovery. Do you see the three androids load?

Code:
To find your hboot version: 
Power off your Evo, once it's off press and hold the 
volume down button and the power button at the 
same time. Release your fingers when the screen with 
3 androids loads, your hboot version will be displayed 
at the top of the screen. Select reboot to reboot your phone normally.

If you're not so sure what has happened so far, you can use the 3.70 RUU and return to a "factory" base software image. You'll find that in the "how to unroot" sticky. Then I suggest following the sticky I posted earlier with rooting.

Trust me, I'd like to be helpful, but so far you really haven't provided a lot of information on what you've done to your phone other than use z4root.
 
I did try to use the Rom Manager and downloaded Cyanogen Mod. I have done a titanium back up which was what required the z4root, but it appeared to be more than temporary as I still found the SU icon in my apps after rebooting.

Just performed another factory reset and am checking to see if I can boot into recovery mode now...hopefully that will narrow down where the issue's root (pun intended) cause is.

Is there something on the boot screen that will help determine what is causing the red triangle? Cuz even after the factory reset, it is still not going into recovery mode.
 
I did try to use the Rom Manager and downloaded Cyanogen Mod. I have done a titanium back up which was what required the z4root, but it appeared to be more than temporary as I still found the SU icon in my apps after rebooting.

I think this is where your problem comes from. z4root is a temporary root that is lost at reboot. It does install a SU program, but you are not rooted when you reboot (even though the icon is still there). The z4root also does not unlock the NAND.

I used z4root to try out a few things and finally decided to do a full root. I followed these instructions:
[ROOT][GUIDE] HBoot 2.02/2.10 SOFF - There Will Be Root - Upd. 01.22.11 - xda-developers

Once you follow those instructions, you will have the "Sprint Lovers" ROM installed and can play with that or you can install another ROM. This is easy at this point because you can just copy the zip for the ROM to your SD card, boot into recovery, wipe the caches, and then install from the zip using the Amon_Ra recovery.
 
So I don't have Z4Root anymore due to factory reset, but am still not able to boot recovery mode. Just has the red triangle. What else needs to be done?
 
So reading the guide, it appears the red triangle is now normal for the device when booting into recovery???? Is that what I have been missing all day in trying to figure this damn thing out? Ugh, too many freaking threads and too many OUT-DATED POSTS!
 
Well, kinda. I believe the red triangle occurs when the software fails a self-check. You have to go through the entire process in the thread I linked to in order to root your EVO. You can't just skip to the step where you think it applies.

I know it looks like a pain and a big hassle, but it isn't too bad if you just go step by step (and read through it a few times before attempting so that you are familiar with the process). I used that process about a week or two ago for my hardware version 004 EVO and it worked fine.
 
So root and rom flashing is command prompt driven now due to how locked down HTC and Sprint have made the device? Ugh...guess will give it a go again tomorrow...just too much info and too many old instructions out here to sift thru...hopefully by the weekend I'll b all set
 
So root and rom flashing is command prompt driven now due to how locked down HTC and Sprint have made the device? Ugh...guess will give it a go again tomorrow...just too much info and too many old instructions out here to sift thru...hopefully by the weekend I'll b all set

The device really isn't that locked down, not compared to some other Android phones out there. Don't get upset at all the old information either ... the phone has been out for a long time now, has gone through many updates, and has multiple software and hardware differences. You need to find what is relevant to your phone's hardware version, software version, HBOOT, etc.

There are "one-click" methods out there such as Unrevoked, which has worked for many users. However, with the issues that you have already had, I would really suggest you go the long route to root your phone so that you know what is going on, what to do if you have issues, how to manually push files to your phone, etc. Personally, I have not had much luck with ROM Manager - the only thing I really use it for is to switch between Clockworkmod and RA Recovery 2.2 (fyi, a lot of users are reporting Clockworkmod has not been properly wiping cache & Dalvik cache). As a previous poster asked - what recovery are you using?

Otherwise, you can give Unrevoked 3 a shot and fend for yourself later ...
 
Because I was using Rom Manager - widely promoted, I was using Clockworkmod. Even when I attempted to use the 'alternate recovery method' showing in RM, I still couldn't get to the data/cache wipe pop up w/o agreeing to Clockworkmod. It shuts the phone down as expected, and I get an HTC boot up screen, but then it always goes to the red triangle when I select 'Recovery' from the boot menu.
 
My take is that you do not have a recovery loaded b/c you are not rooted. If you did a complete wipe, you might as well load a stock RUU and start the root process over using Unrevoked or the manual method. Since you wiped, you won't be losing anything or much.
 
So my problem probably was that it was losing root at shut down cuz I was using z4root, duh...thanks for the take!
 
So my problem probably was that it was losing root at shut down cuz I was using z4root, duh...thanks for the take!

I'm glad you finally figured out the problem.

Strange, your assertion that you were relying on z4root and that you hadn't done anything else... sounds exactly what I posted much earlier.

Anyway, once you're rooted let us know how it goes. What are you looking to do after you root?
 
trying to get Gingerbread goodness, and a better kernel. Did quite a bit of over-clocking on my Pre and am ready to take the plunge on the Evo if only just to get better battery performance. Trying to get some files figured out now as I'm going the unrevoked route and Root was not successful. Device manager is not showing Android 1.0, so I think I'm going to have to take a couple steps back.
 

Trending Posts

Forum statistics

Threads
956,347
Messages
6,967,707
Members
3,163,516
Latest member
KidColoringPage