Develop Bugs

so i tried to root my g2...

So... as the title says I tried to root my phone. I'm following the CM 7 wiki guide and i got up until step 6 but I did not install cyogenmod 7 I just rebooted (i thought you just reboot and hey it installs but i guess not). So it rebooted to the original rom and then I just downloaded ROM manager again to install it. It goes through clockwork and then it reboots again so... i thought it successfully installed but it didn't because my phone was stuck on the HTC boot up screen unresponsive. So, I've been googling and so I pulled the battery and did the whole power on + volume down. It took me to the screen with fastboot,recover,and stuff but then it changed screens to the could not find PC10img.zip and wanted me to update. So i updated it again and it rebooted to the HTC screen and stayed there. Pulled the battery again, took out the SDcard, and then did the whole power up + volume button. Now I can choose the options in this screen (fastboot,recover,factory reset,simlock, system info, image crc).
Now I don't know what to do.... I want to continue to root to cyogenmod but I'm soo confused how to get back to installing it properly. Thanks for the help in advance!
edit
perhaps, i might just have to delete the PC10img.zip file? i have an mircoSDcard reader at home and if I delete it then loading into hboot should be fine..... right?
update: nevermind! i fixed it!

[Q] stuck in white boot screen after trying to restore from backup

i just rooted my incredible today and flashed MIUI. everything worked fine but i didnt like how it looked so i tryed to restore from a backup i made earlier. My phone is now stuck in the white boot screen. i did a battery pull and still get the white screen. I can get into hboot and recovery but when im in recovery none of the menu options work. when i go to one like the install zip from sd it goes to a black screen with just the cwm logo on it. same goes with every other menu option it try. What do i do? please help i searched all over the threads and google and cant find anything

Just how aee you selecting a menu option, and then what happens?

i was trying to select it with the power button and not the track pad.. im new to this lol my bad. everything is fine now got it up an running

[Q] Please help! Stuck and can't use phone.

This morning I was using font installer to change my system font . I guess somewhere along the way something got messed up because when I went to reboot it gets to the boot animation and turns off. Not exactly a boot loop but useless anyway. I could just go into recovery and reflash. The problem is I can't get the phone into recovery. I use TWRP. I hold volume up and down and power, the TEAM Win blue screen and logo comes up but then what do I do? If I keep holding it down then it just goes into that mode where it vibrates every second and nothing happens.if I let go then the blue logo screen goes away and it tries to boot up normally again. What am I missing here? Why can't I get into recovery so I can reflash... Thanks for all Your help guys!

have you tried using adb commands? Also if you have not gotten into recovery as of now you just have to keep trying with the vol and power key buttons you will get it.
ADB choices
Plug phone into pc and type adb reboot recovery and hope for the best

I think you might be able to reflash/reinstall the recovery using adb commands and that might work too. Worst comes to worst, you could try using ODIN to restore your recovery or whole phone, but you'll probably lose anything not on SD.
And I haven't used font installer in ages, but I had issues with it on my SGSII because I think it flashes system files; I know it doesn't help now, but I'd stick to using font apks, since our phones support that.
Russian smashed across the interwebz from my Galaxy S2.

Sometimes this happens with fonts that are not designed for whichever version of android you are running. Its not all of them believe me, as well as this is honestly an easy fix. This is why I believe in knowing everything about your phone prior to doing stuff to it and knowing how to escape 90% of the issues that may come your way.

Thanks alot. the annoying part is that TWRP blue screen comes up but nothing happens. It just kinda flashes like a crt tv off and then goes into the vibrate every second thing. I typically do alot of reading and research prior to doing anything and I used to use the font app before on the HD2 so I was suprised this happened. I guess you live and learn. I just thought that was one of the benefits of having a recovery so you Could fix stuff like this. it doesn't help if you Can't even get into recovery. I never had this problem with Cwm Recovery.

I got it to work! I guess it's all about the timing for when to release the buttons to get into recovery. I flashed the rom back and all is well. Or at least getting there. Thanks everyone for the help. Hopefully this thread will help someone else in the future. Lesson Learned: Don't give up on trying to boot into recovery. It will work. You just have to release the power and volume button at just the right time to get everything going. Lesson 2: Don't use the font installer app....

[Q] Phone stuck on boot collective rom

First off a little background I downloaded and installed the collective rom from the dev section earlier today and was absolutely loving it. I went into the over the air settings, and downloaded the avengers theme bc I thought it would make a cool edition to show my nephew ( loves the avengers) upon rebooting after successfully flashing I get the avengers A boot logo but it just sits there flashing, and the phone never boots. After waiting a solid 15 minutes for it to boot I held down the power button to power down the phone, and now I can not get it into recovery to reinstall the rom, or install a backup that I made. Clockwork will not come up for some reason, and whenever I try to boot the phone again it gets stuck on the avengers A??? What should I do? What did I do wrong? Thanks in advance
P.S. whenever I plug the phone in it does bring up the battery icon that shows that it is charging, and it will also allow me into download mode.
-Garrett

hino8229 said:
First off a little background I downloaded and installed the collective rom from the dev section earlier today and was absolutely loving it. I went into the over the air settings, and downloaded the avengers theme bc I thought it would make a cool edition to show my nephew ( loves the avengers) upon rebooting after successfully flashing I get the avengers A boot logo but it just sits there flashing, and the phone never boots. After waiting a solid 15 minutes for it to boot I held down the power button to power down the phone, and now I can not get it into recovery to reinstall the rom, or install a backup that I made. Clockwork will not come up for some reason, and whenever I try to boot the phone again it gets stuck on the avengers A??? What should I do? What did I do wrong? Thanks in advance
P.S. whenever I plug the phone in it does bring up the battery icon that shows that it is charging, and it will also allow me into download mode.
-Garrett[/QUOTEf
that is rather wierd. i also use the collective rom its great! but was the avengers theme a flashable theme? or one from theme choooser... if it was flashabble are you sure you did it to the right device.. honestly if i were you and there were no way going into recovery i would unroot and reroot and install ur custom recovery again and restore ur collective rom before this problem happened...
Click to expand...
Click to collapse

Thank you for the quick response. Yes I am sure it was a flashable theme, if you are running the collective rom and go to the over the air settings there are themes you can download, and the instructions just say to reboot into recovery, flash the theme, then reboot. after doing that I am now experiencing these problems.
A little more info. Sorry bear with me I'm a noob. whenever I try to reboot (not recovery) it says samsung first then it say samsung galaxy s3 like normal then the next screen is the avengers A and this is where it gets stuck. When I try to reboot into recovery all i get is the first black screen with samsung and then after that the phone turns off and the battery icon comes back up. I don't get the second samsung galaxy s3 screen where you are supposed to release the power button, it just dies and goes to the battery logo.

hino8229 said:
Thank you for the quick response. Yes I am sure it was a flashable theme, if you are running the collective rom and go to the over the air settings there are themes you can download, and the instructions just say to reboot into recovery, flash the theme, then reboot. after doing that I am now experiencing these problems.
A little more info. Sorry bear with me I'm a noob. whenever I try to reboot (not recovery) it says samsung first then it say samsung galaxy s3 like normal then the next screen is the avengers A and this is where it gets stuck. When I try to reboot into recovery all i get is the first black screen with samsung and then after that the phone turns off and the battery icon comes back up. I don't get the second samsung galaxy s3 screen where you are supposed to release the power button, it just dies and goes to the battery logo.
Click to expand...
Click to collapse
Since you can go to download mode i assume odin should still recognize your device. If I were you I'd odin unroot...reroot....restore your old collective rom...cuz u wanna stay orange

How could Bootanimation flash break rom like this?

I had 4 min till work and I decided to compile bootanimation zip really quickly.... 19 Frames... done with bootanimation factory. Used Rom toolbox pro to install it... rebooted...
Then this happened:
* Bootloop pre- bootani
--- Pulled battery
*Bootloop stopped, phone booted into rom (screen black)
I wasnt sure but the buttons turned on. on the bottom.... so I pulled battery out
After work-
* While waiting for ride I pulled battery decided to leave it with battery on and blank screen. I tapped vol up and sound went up... I actually kept getting my text message notifications and I received a call! Which I was able to answer with swiping....
After that, I dirtyflashed to get rom working once i was home which worked...but menu was a little laggy so I did nandroid and then did full wipe, reflash and restored. because usb doesn't mount until your in OS (if you have pin/pass) I had to guess location of digits on the screen which gladly worked in 1 shot to even put the zips on the external card to fix the phone)
EVERYTHING WORKED, Except the screen once it passed Samsung Boot sequence....its freaky
Its just really a mystery to me how bootanimation could muck things up like that.

nxneko said:
I had 4 min till work and I decided to compile bootanimation zip really quickly.... 19 Frames... done with bootanimation factory. Used Rom toolbox pro to install it... rebooted...
Then this happened:
* Bootloop pre- bootani
--- Pulled battery
*Bootloop stopped, phone booted into rom (screen black)
I wasnt sure but the buttons turned on. on the bottom.... so I pulled battery out
After work-
* While waiting for ride I pulled battery decided to leave it with battery on and blank screen. I tapped vol up and sound went up... I actually kept getting my text message notifications and I received a call! Which I was able to answer with swiping....
After that, I dirtyflashed to get rom working once i was home which worked...but menu was a little laggy so I did nandroid and then did full wipe, reflash and restored. because usb doesn't mount until your in OS (if you have pin/pass) I had to guess location of digits on the screen which gladly worked in 1 shot to even put the zips on the external card to fix the phone)
EVERYTHING WORKED, Except the screen once it passed Samsung Boot sequence....its freaky
Its just really a mystery to me how bootanimation could muck things up like that.
Click to expand...
Click to collapse
Odd. It's entirely possible that it's a coincidence, and unrelated to the boot animation. It might have done that on reboot even if you didn't change anything (to my knowledge, the boot animation can't do that.) It's kind of like a lot of the people I see who are saying rebooting and wiping cache/dalivk fixed so and so issue, when the reboot alone would've done it. I've had that happen to me on a few aosp roms, usually requiring a restore or new install, and didn't touch the boot animation.