Database Users

BATTERY

Ok, so I am running the newest ENERGY ROM, VBN RELOADED, and CORE CELL v4.1 and Im for android Im using hd 3.7, and when I first install the android I can get it to run 5-10mA or when I flash a new ROM, but once I restart android I can only get 50-60mA, i have pushed the back button when haret is running, it is so frustrating becuase I want to switch between android and winmo, and Im already using hastarin custom kernels and cant seem to get it to go less than 50-60mA unless I reflash or reformat and install over. Someone please tell me why the f8Ck this is happening, SO irritating. Ive tried to do some searching but all I have heard is that its from not lighting up my buttons. is there a certain time im supposed to light them up? Also, does having my charger plugged in help? Someone please help! Dont make a grown man cry.
Thanks in advance.
Matt

Just use Excellors' Multi boot app and set it to auto boot/3 secs when you want to boot Android and you should be good. If you run WM for a while reset your phone before going to Android and let it auto boot into Android. The battery drain in Android seems to be related to WM/Sense. By using the auto boot feature, WM/Sense is not allowed to fully boot. You should see significant improvement in battery performance in Android if you follow these simple steps. Cheers.

thanks mate
reocej said:
Just use Excellors' Multi boot app and set it to auto boot/3 secs when you want to boot Android and you should be good. If you run WM for a while reset your phone before going to Android and let it auto boot into Android. The battery drain in Android seems to be related to WM/Sense. By using the auto boot feature, WM/Sense is not allowed to fully boot. You should see significant improvement in battery performance in Android if you follow these simple steps. Cheers.
Click to expand...
Click to collapse
Thanks brodie, Imma give it a shot! let you know shortly

I solved this problem by renaming lights.htcleo.so included in the kernel

?
sykodelyk said:
I solved this problem by renaming lights.htcleo.so included in the kernel
Click to expand...
Click to collapse
Whaqt did you rename it to?

TheGeorgiaSwagger said:
Whaqt did you rename it to?
Click to expand...
Click to collapse
Im assuming hes talking about renaming it to lights.qsd8k.so?

Overclocking - Hard/Easy?

I recently bought Wildfire, and I realy enjoy it. The biggest upset of this phone for me is that Skype isn't working properly. The sound quality is horrible, scratchy and I can barely understand what others are saying to me.
So last week I wrote an email to skype developers and they told me that the main couse of my issue is slow processor.
I started looking how can I improve my phone speed and found this awesome forum.
I'm pretty experianced if it comes to overclocking PCs which can confirm my PC - watercooled Q6600 4.1Ghz, but if it comes to the smartphones my experiance is less then none. On the PC everything is simple - you run bios and make some magic. Ofc. you can flash ur bios ect. but everything comes just so naturally for a user.
Here everything seems soo complicated. I've read tones of postes and I still 've no idea how 2 safely overclock my processor. I know I need some new kernel and newer ver. of Android. On the other hand, newer ver. of Android is bugged and GPS is not working as it should 've. (I didn't tested this, just heared about it).
Okay question time
1)Is there anyway to overclock my Wildfire without changing Android ver.? I don't need any more functions, 2.1 is enought for me.
2)Did you test skype on your OC'ed wildfire? If you did, how did it work?
3)Don't you've any simple guide how to make a safe overclocking? During the search time I found this - I can't paste link but the tutorial was very complex.
Sry for my mistakes, I know my English isn't in a perfect shape.
Cheers!

Its easy, Im a relative noob and I managed it no problems at all. You dont even need to be running a custom rom to do it.
Youll need to first root your phone by following this guide http://forum.xda-developers.com/showthread.php?t=788776
Then download Jacobs kernel from here http://forum.xda-developers.com/showthread.php?t=798471 Rename it "update" and put it in the root of your sd card. Reboot your phone into recovery by holding volume down and power and choosing recovery. Do a nandroid backup incase things go pear shaped. Select "apply sdcard:update" from the recovery menu and it should flash the kernel. Reboot your phone and install setCPU. Enjoy.

Do you have to pay for setCPU ?
Sent from my HTC Wildfire using XDA App

Frakke said:
Do you have to pay for setCPU ?
Sent from my HTC Wildfire using XDA App
Click to expand...
Click to collapse
You can either buy it on the market, or download it from this thread (don't worry, it's not warez, the thread is maintained by the dev).

Michealtbh said:
Its easy, Im a relative noob and I managed it no problems at all. You dont even need to be running a custom rom to do it.
Youll need to first root your phone by following this guide http://forum.xda-developers.com/showthread.php?t=788776
Then download Jacobs kernel from here http://forum.xda-developers.com/showthread.php?t=798471 Rename it "update" and put it in the root of your sd card. Reboot your phone into recovery by holding volume down and power and choosing recovery. Do a nandroid backup incase things go pear shaped. Select "apply sdcard:update" from the recovery menu and it should flash the kernel. Reboot your phone and install setCPU. Enjoy.
Click to expand...
Click to collapse
hey there. i've follow ur way. but then nothing happened? the setCPU comes after flashed the kernal or we have to find it? nothing happened but an app called "Superuser permission" came out. I've tried to open it but nothing happened, just a black screen.
i tried to search for setCPU and then i got a CPU tuner. Everytime i try to pull the max frequency bar and it will force closed =(. why??

1. root your phone
2. download hcdr jacob's kernel, put it on your sd card and flash it, you dont need to rename it to 'update.zip', boot into recovery, just select install zip from sd card and choose the kernel and flash it.
3. download setcpu from xda, or find it on the market
4. run it, allow su permissions, and then change your settings bla bla.

kevin2516 said:
1. root your phone
2. download hcdr jacob's kernel, put it on your sd card and flash it, you dont need to rename it to 'update.zip', boot into recovery, just select install zip from sd card and choose the kernel and flash it.
3. download setcpu from xda, or find it on the market
4. run it, allow su permissions, and then change your settings bla bla.
Click to expand...
Click to collapse
i've done all the steps u mentioned, but still... it forced close =(

halaue said:
hey there. i've follow ur way. but then nothing happened? the setCPU comes after flashed the kernal or we have to find it? nothing happened but an app called "Superuser permission" came out. I've tried to open it but nothing happened, just a black screen.
i tried to search for setCPU and then i got a CPU tuner. Everytime i try to pull the max frequency bar and it will force closed =(. why??
Click to expand...
Click to collapse
As U are getting the superuser app u have successfully rooted your phone.
Now download the latest Kernal nd update from it by booting into recovery mode.(HBOOT then Recover). In recovery menu select your file nd hit update.A couple of min. later ur done.Check in about hone to see weather it was a success.
Download setcpu app and select max min frequency nd profiles if u want.Any problem these threads have TONS of info.GL

assassinator said:
As U are getting the superuser app u have successfully rooted your phone.
Now download the latest Kernal nd update from it by booting into recovery mode.(HBOOT then Recover). In recovery menu select your file nd hit update.A couple of min. later ur done.Check in about hone to see weater it was a success.
Download superuser app and select max min frequency nd profiles if u want.Any problem these threads have TONS of info.GL
Click to expand...
Click to collapse
thank you for your clear guide.
since u say i got the superuser app means i have successfully rooted my phone, then i got the setCPU ( CPU Tuner ) from the market, but i just cant understand why it will forced close everytime i try to drag the max and min frequency bar =(. i did not change any values also..

halaue said:
thank you for your clear guide.
since u say i got the superuser app means i have successfully rooted my phone, then i got the setCPU ( CPU Tuner ) from the market, but i just cant understand why it will forced close everytime i try to drag the max and min frequency bar =(. i did not change any values also..
Click to expand...
Click to collapse
Setcpu will only work once u have flashed the overclockable kernal.Have u flashed that?

assassinator said:
Setcpu will only work once u have flashed the overclockable kernal.Have u flashed that?
Click to expand...
Click to collapse
yes.
HCDRJacob-htc-kernel-wildfire-2.6.32-a91e73b.zip
this is what i downloaded.
i put into sd root and then boot in recovery, then installed. problem with that kernel? i got it from the link given by Michealtbh, the first person replied this thread..

halaue said:
yes.
HCDRJacob-htc-kernel-wildfire-2.6.32-a91e73b.zip
this is what i downloaded.
i put into sd root and then boot in recovery, then installed. problem with that kernel? i got it from the link given by Michealtbh, the first person replied this thread..
Click to expand...
Click to collapse
Download this one.
http://forum.xda-developers.com/attachment.php?attachmentid=429951&d=1288436771
Then reinstall setcpu.

Or maybe you are using the wrong app, i am pretty sure it's setCPU, not CPU tuner.
Try getting it from the thread ?

i'm try to download that one, hope that will help. thanks assassinator =)
@argeoff
i got it from market leh.. it's wrong? do u have the link?

Download the setCpu from the thread. One guy mentioned it earlier.
http://forum.xda-developers.com/showthread.php?t=505419
leh? Singlish, you from Singapore ?

argeoff said:
Download the setCpu from the thread. One guy mentioned it earlier.
http://forum.xda-developers.com/showthread.php?t=505419
leh? Singlish, you from Singapore ?
Click to expand...
Click to collapse
lol. no i am not. i am from malaysia

Wow thank you guys for all this help. Michealtbh you gave me answear I was hoping for. Today I'm gonna try all of this, I just hoping my HTC Sync won't ruin my rooting. Thanks again!

i get it solved also =D. now my cpu f is 710mhz wow. but i cant see any difference right now, any way can test this limit? haa.
thanks all =)

Sucess! New kernel installed, Overclocking done! Aweeesome! TY!
EDITED: Okay guys, Skype isn't work properly so I'm pretty sure it's some kind of skype software bug. One last question, is there a way to check temperature of the processor?

Easiest way to test the new speed is to play games.
Something like angry birds ..
Sent from my HTC Wildfire using Tapatalk

[Help] phone stuck at google screen

Every time i try to boot into clockwork my phone it gets stuck at the google screen it even does this when trying to flash a rom using rom manager can someone help

This happened to me. Solution for me was to go to rom manager and scroll to flash previous version of clockwork and select 3.0.0. Hope this helps
Sent from my Nexus S using XDA App

mrnexus said:
Every time i try to boot into clockwork my phone it gets stuck at the google screen it even does this when trying to flash a rom using rom manager can someone help
Click to expand...
Click to collapse
youre going to have to reflash clockwork recovery. either fastboot it, adb, or through the terminal emulator on your phone(if it still boots). btw, wrong section to post in(i think), this is a development section

fosdos4790 said:
This happened to me. Solution for me was to go to rom manager and scroll to flash previous version of clockwork and select 3.0.0. Hope this helps
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
did it work

simms22 said:
youre going to have to reflash clockwork recovery. either fastboot it, adb, or through the terminal emulator on your phone(if it still boots). btw, wrong section to post in(i think), this is a development section
Click to expand...
Click to collapse
i thought you could do that thru rom manager

mrnexus said:
i thought you could do that thru rom manager
Click to expand...
Click to collapse
i dont use rom manager. i do it the easy way

how do you use the terminal emulator

mrnexus said:
how do you use the terminal emulator
Click to expand...
Click to collapse
download and put the file on the main part of the sd card(the root of the sd card), rename it to whatever you want, ill use rec.img. open your terminal emulator then type...
su(press enter)
flash_image recovery /sdcard/rec.img(press enter)
reboot recovery(press enter)
Click to expand...
Click to collapse
notice that there is a space between recovery and /sdcard/

Can I ask which ROM (and kernel if relevant) you were running? This has happened to me for the first time tonight (after the phone locked up earlier). I am running CM7 Nightly #25 and the NetArchy 1.2.1 (CM7) kernel - I'm wondering if this is related in some manner?
Incidentally, the dropping back to 3.0.0 trick worked a treat.

you might've left "Erase recovery before flash" on accident in Rom Manager.

I've just had the WiFi tell me that there was "an error" when trying to start it. I'm re-rolling to just CM7#25 on it's own (with a full wipe) to see if that resolves it for me.

visor said:
I've just had the WiFi tell me that there was "an error" when trying to start it. I'm re-rolling to just CM7#25 on it's own (with a full wipe) to see if that resolves it for me.
Click to expand...
Click to collapse
did you try just rebooting?

visor said:
Can I ask which ROM (and kernel if relevant) you were running? This has happened to me for the first time tonight (after the phone locked up earlier). I am running CM7 Nightly #25 and the NetArchy 1.2.1 (CM7) kernel - I'm wondering if this is related in some manner?
Incidentally, the dropping back to 3.0.0 trick worked a treat.
Click to expand...
Click to collapse
bionix ns1

andyandrwew said:
you might've left "Erase recovery before flash" on accident in Rom Manager.
Click to expand...
Click to collapse
what do you mean

simms22 said:
did you try just rebooting?
Click to expand...
Click to collapse
Yes - several times.
I've just rebuilt the phone. Everything is now working dandy with just CM7#25, gapps and I've not restored any data. I'll see how it goes.

[26.Mar][Fix] ★★★MARKET INCOMPATIBLE ISSUES, Bootloops, Random reboots -AND MORE- ★★★

[26.Mar][Fix] ★★★MARKET INCOMPATIBLE ISSUES, Bootloops, Random reboots -AND MORE- ★★★
MOST ASKED QUESTION ARE ANSWERED IN THE LINK BELOW :
http://forum.xda-developers.com/showthread.php?t=945427
--------------------------------------------------------------------------------------------------------------------------------------
This thread was opened as a question, but now I have some solutions, so I thought I should change it to a fix. Hope this helps!
Introduction:
"Your device is not compatible with this item"/market incompatible issues
Possible solutions to fix the random reboots
Possible solutions to fix bootloops
1. "Your device is not compatible with this item"/market incompatible issues​​I will list the solutions that I know about, hope this helps. (if you have other solutions, please reply in the thread)
1. Clear market cache.
2. Edit this in system/build.prop to make market recognize your phone as sgs2
Code:
ro.product.model=[B]GT-I9100[/B]
ro.product.brand=[B]samsung[/B]
ro.product.name=[B]GT-I9100[/B]
ro.product.device=[B]GT-I9100[/B]
ro.product.board=[B]GT-I9100[/B]
ro.build.product=[B]GT-I9100[/B]
3. Change DPI to 240.
4. Download Market Enabler.
Go to the settings list and long-press Verizon [us] and then fake this provider now.
5. Currently working for me:
LCD Density Modder Pro
What the app does, is to download a vending.apk to your phone based your preferred dpi. The vending.apk has a "hack" inside, which will trick market to think that your phone is on 240 dpi.
It's a paid app, but it's worth it.
2. Possible solutions to fix the random reboots​​
- Turn off automatically detect time
- Turn off automatically back light.
- Do not overclock
- Turn off Background data and Auto-sync: Menu > accounts & sync > uncheck "Auto-sync" and "Background data"
The options above "may" fix your rebooting issue, but the one that helped me (no reboots for over 4 months) and few other people was:
Go to Settings - Wireless & networks - Mobile networks - Network operators
Now choose your network operator manually.
I think this fixed my random rebooting issue because sometimes my phone would disconnect from my network and that's when the reboots occurred.
Another "proof" is that the random rebooting was reduced while using magldr. As we know, magldr is more stable when it comes to data, as it uses RMNET. So the disconnecting may be the issue.
Anyways, it worked for me, I hope it works for you too.
3. Possible solutions to fix bootloops​
Update 15.FEB.2012:
(Thanks to Seadersn for the idea)
Increasing the partition that contains the bad blocks will not always help.
To fix this, try increasing the first partition (which is recovery, in cLK)
Code:
fastboot oem part-resize recovery:50
Code:
fastboot oem part-commit
If your phone won't pass the android screen after a reboot, try decreasing the recovery partition. I ended up at 10.
--------------------------------------------------------------------------------------------------------------------------------------
- Make sure you have performed a task 29 (clean install) before complaining about anything
- If you flashed or edited something in your system, then rebooted and your phone was stuck, then try to go back to how your phone was.
For example:
If you were using kernel 1, but then flashed kernel 2, which caused the bootloops, re flash kernel 1, and it should be fixed
The solution for most of the people:
The Htc Hd2 came out in 2009, and if you are one of the people that have been using it since, then your phone is pretty old. We flash our nands very often, as new rom/kernel updates are released. This is causing bad blocks on the nand. Bad blocks are mostly causing bootloops, but it can even cause small issues like app2sd not working (funny, but it happened to me).
Solution:
Connect your phone to your pc and open the folder where the adb tools are located. Open terminal and type in:
Code:
adb shell dmesg
You will see a lot of text... Scroll down and you should see something like:
Code:
###BAD BLOCK 1234 56789###
###BAD BLOCK 1234 56789###
OR (recommended) (CLK ONLY):
Enter cLK bootloader. Connect your phone to your pc. Open cmd inside a folder containing fastboot files and type in this: (similar to task29)
Code:
fastboot oem format-all
If you do not see any bad blocks, you are lucky if you do, then do this:
- CLK USERS ONLY:
- THIS WILL DELETE YOUR CURRENT ROM AND CWM!
- You need fastboot drivers working on your computer
1. Install clk 1.5 link
2. Turn off phone. Click on power button once, and hold back button. Connect your phone.
3. Download fastboot.zip (scroll down)
4. Locate to the folder where the .zip is located and extract it. Hold shift while right clicking (inside the folder), open terminal.
5. This part depends on where your bad blocks are located. For example, lets say it is located in "system" then type this in the terminal:
Code:
fastboot oem part-resize system:160
The "160" is just an example. You will need to experiment with the partition size.
My bad blocks are located in "misc". After some minutes with experimenting, I ended up with increasing it to 25.
IMPORTANT:
When you are done re sizing your partition, type this in your terminal:
Code:
fastboot oem part-commit
Your phone should now reboot. Re flash cwm, then install your rom and check if it boots now.
ADVANCED ADVANCED USERS ONLY!​If you have bad blocks, and task 29 is not erasing it, you can try something called task2a using mtty. It is not guaranteed that this will erase your bad blocks, but there is a possibility.
You will need some drivers and mtty installed.
link
-----------------------------------------------------------------------------------------
My Bad blocks: http://forum.xda-developers.com/showpost.php?p=22994536&postcount=968
If you have tried everything in my guide, but your phone won't run android anymore.. The time is in to get a new phone
I hope this helped you
Please thank the devs for their work
I would appreciate a thank myself
PLEASE PM IF I MADE SOMETHING WRONG/MISSED SOMETHING

yz.hd said:
My phone keeps rebooting 2 - 6 times a day (randomly) I have turned off data connection and automatically time settings, but it doesn't help. I am not using setcpu.
Rom: Hypderdroid cm7 2.1.0
clk: 1.4.0.1
CWM: 4.0
Radio:2.15
HSPL: 2.08
Click to expand...
Click to collapse
when did this start happening ie after you installed clk or cwm
after you updated some apps .....

yz.hd said:
My phone keeps rebooting 2 - 6 times a day (randomly) I have turned off data connection and automatically time settings, but it doesn't help. I am not using setcpu.
Rom: Hypderdroid cm7 2.1.0
clk: 1.4.0.1
CWM: 4.0
Radio:2.15
HSPL: 2.08
Click to expand...
Click to collapse
VERY VERY VERY common problem in 80% of hd2s.
If some di**head comes along and says the usual CRAP...."do a task 29" just tell them where to go, coz it DOES NOT HELP.

Kameirus said:
when did this start happening ie after you installed clk or cwm
after you updated some apps .....
Click to expand...
Click to collapse
I have to install clk and cwm to install the rom.. So they were both installed

matthew33 said:
VERY VERY VERY common problem in 80% of hd2s.
If some di**head comes along and says the usual CRAP...."do a task 29" just tell them where to go, coz it DOES NOT HELP.
Click to expand...
Click to collapse
haha
I have talked to some other guys that have a hd2, some of them gets randomly reboots everyday, while on some of them, it has never happened..

yz.hd said:
I have to install clk and cwm to install the rom.. So they were both installed
Click to expand...
Click to collapse
ok how about this
1..try an older version of clk ie 3025
2.have you tried the magldr version of your rom to see if its rebooting also

matthew33 said:
VERY VERY VERY common problem in 80% of hd2s.
If some di**head comes along and says the usual CRAP...."do a task 29" just tell them where to go, coz it DOES NOT HELP.
Click to expand...
Click to collapse
this is why we need a useless post button

Kameirus said:
ok how about this
1..try an older version of clk ie 3025
2.have you tried the magldr version of your rom to see if its rebooting also
Click to expand...
Click to collapse
Still rebooting on 3.0.2.5
And yes, I switched to magldr for 2 days to check.. still rebooting 2 times a day :/

yz.hd said:
Still rebooting on 3.0.2.5
And yes, I switched to magldr for 2 days to check.. still rebooting 2 times a day :/
Click to expand...
Click to collapse
ok another dumb question
have you tried a different rom

Kameirus said:
ok another dumb question
have you tried a different rom
Click to expand...
Click to collapse
yeah lol

yz.hd said:
yeah lol
Click to expand...
Click to collapse
lol i know
im trying to help ya figure it out
ive never had the reboot problem
the only one i know who did was having it but he was useing
setcpu and your not using it

This is a longshot, but maybe its hardware related, like its been dropped to many times. Does it randomly freeze up or just reboot? I've had a few customers come in with similar issues, and one thing that seemed to work was scaling the CPU back to 800mhz in the cm7 performance settings. I'm not sure why, but its worked most of the time in my shop.
Sent from my HD2 Pocket laptop using XDA Premium App

z3nful said:
This is a longshot, but maybe its hardware related, like its been dropped to many times. Does it randomly freeze up or just reboot? I've had a few customers come in with similar issues, and one thing that seemed to work was scaling the CPU back to 800mhz in the cm7 performance settings. I'm not sure why, but its worked most of the time in my shop.
Sent from my HD2 Pocket laptop using XDA Premium App
Click to expand...
Click to collapse
it does not freeze at all :/ only rebooting.. It doesn't happen when I'm using it, only when it is in standby mode.

I've exactly the same problem. Device is rebooting only in idle/standby mode. Time between reboots seems to be ~2 hours.
-Radio Rom 2.15.50.14
Already tried to:
-Turn off automatically detect time
-Turn off automatically back light.
-Turn off mobile network (only turn on when needed)
-change maximum and minimum cpu to 460-800 Mhz
-with TyphooN_CM7_v3.7.0-cLK and 35-AmeriCanAndroid+122011(magldr)
-Tried with Magldr (1.13) or CLK (1.4.0.1)
-remove SD Card in case of incompatibility
does anybody has solved his problem? Another thing I can try?

I had forgotten this thread haha
The solution that helped me.. ever since june 2011 was to select my operator manually. No reboots since

Thanks! Helped!

goddamn, if that fixes it im gonna be SO happy lol

I had that problem a few days ago. I think its actually rom related .. on the new ics builds its been common for my phone to reboot but then other more stable roms it shouldn't be rebooting.. when I first noticed the reboots was a few days ago I converted an official miui rom to clk (not on xda) and randomly when I checked my phone it would be turned off or rebooting, this occurred several times.. today I updated to the newest miui 2.1.6 and converted it to clk but I haven't noticed any random reboots yet.. so maybe (hopefully) rom related.
Sent from my HD2 using xda premium

yz.hd said:
I had forgotten this thread haha
The solution that helped me.. ever since june 2011 was to select my operator manually. No reboots since
Click to expand...
Click to collapse
i am SO glad you did not entirely forgotten this thread, because your solution solved it for me to. and i was literally tearing my hear out.
This thread, or at least the solution to this problem needs to be stickied or wikified or some such thing.

updated the first post

Motorola bravo help

I have rooted my phone and flashed custom firmware b4... when i installed 2int to flash again.... it won't boot up the OS instead it keeps booting 2int... how do i boot into my os again... thx in advance
I am running android 4.1.1 jellybean

hotshot545 said:
I have rooted my phone and flashed custom firmware b4... when i installed 2int to flash again.... it won't boot up the OS instead it keeps booting 2int... how do i boot into my os again... thx in advance
I am running android 4.1.1 jellybean
Click to expand...
Click to collapse
Unfortunately, you cannot flash 2ndinit if you've already installed cyanogenmod, since it already has a bootloader. Goes for all versions of CM. I made the same mistake and had to flash the sbf.
I'm assuming that when you reboot normally you get stuck at the "red M" screen and your capacitive touch buttons might flicker. If that's the case, you will have to flash the sbf, because your bravo is boot looping. Go to this post here and follow the tutorial to the letter.
http://forum.xda-developers.com/showthread.php?t=1559109
If you are having further trouble, post it there.
And don't forget to say thank you to josuearisty

dr. Orange said:
unfortunately, you cannot flash 2ndinit if you've already installed cyanogenmod, since it already has a bootloader. Goes for all versions of cm. I made the same mistake and had to flash the sbf.
I'm assuming that when you reboot normally you get stuck at the "red m" screen and your capacitive touch buttons might flicker. If that's the case, you will have to flash the sbf, because your bravo is boot looping. Go to this post here and follow the tutorial to the letter.
http://forum.xda-developers.com/showthread.php?t=1559109
if you are having further trouble, post it there.
And don't forget to say thank you to josuearisty
Click to expand...
Click to collapse
thank u sooo much

hotshot545 said:
thank u sooo much
Click to expand...
Click to collapse
ok i just wanted to know is there a way to charge phone b4 doing this

hotshot545 said:
ok so if i flash it using sbf lite... will it run stock android 2.2 or will it's still run 4.1.1 and also will it still be rooted or will i have to restore root. and btw b4 i do this can i charge my phone in this "boot loop mode"... srry i am not the best at this kind of stuff... so I would greatly appriciate if you assisted me step by step if you could... thx in advance again..
**don't wanna brick my bravo xD
Click to expand...
Click to collapse
It will run stock 2.2.1 yes. If you follow the instructions from the tutorial, and you have at least a little battery left you should be fine, since you will have your phone plugged into your computer. You will have to re-root as well. When you sbf, you have to start all over, including rooting. Just make sure you follow the tutorial step by step. It does a much better job explaining how to fix everything.

Dr. Orange said:
It will run stock 2.2.1 yes. If you follow the instructions from the tutorial, and you have at least a little battery left you should be fine, since you will have your phone plugged into your computer. You will have to re-root as well. When you sbf, you have to start all over, including rooting. Just make sure you follow the tutorial step by step. It does a much better job explaining how to fix everything.
Click to expand...
Click to collapse
ok thx sooooo much.. approximatly how long will this take

hotshot545 said:
ok thx sooooo much.. approximatly how long will this take
Click to expand...
Click to collapse
Maybe an hour to get you back to jelly bean. It's worth it to take your time before each step so you don't mess anything up.

Dr. Orange said:
Maybe an hour to get you back to jelly bean. It's worth it to take your time before each step so you don't mess anything up.
Click to expand...
Click to collapse
Dude thx a bunch... i'm up and running jelly bean again using 2nd init btw next time i flash how would i do it without 2nd init

hotshot545 said:
Dude thx a bunch... i'm up and running jelly bean again using 2nd init btw next time i flash how would i do it without 2nd init
Click to expand...
Click to collapse
To reboot into recovery, hold the power/hold button down til that menu pops up, then select reboot, then select recovery. It was my pleasure helping. If you have any other questions just ask in the bravo general section and eventuality someone will help. Everyone with bravo is very supportive.
Edit: in recovery you will have options like reboot, wipe cache, wipe data, flash zip, backup/restore, that sort of thing. Usually I backup first just as a precaution, before wiping data and cache and then flashing a new rom. For other zips like gapps, cpu governors, or anything else you can just flash the zip without wiping.

Dr. Orange said:
To reboot into recovery, hold the power/hold button down til that menu pops up, then select reboot, then select recovery. It was my pleasure helping. If you have any other questions just ask in the bravo general section and eventuality someone will help. Everyone with bravo is very supportive.
Edit: in recovery you will have options like reboot, wipe cache, wipe data, flash zip, backup/restore, that sort of thing. Usually I backup first just as a precaution, before wiping data and cache and then flashing a new rom. For other zips like gapps, cpu governors, or anything else you can just flash the zip without wiping.
Click to expand...
Click to collapse
I'm gonna add, since the recovery option in the power button menu doesn't always access 2nd-init recovery (depends on the rom), nor is that option available in all roms, you just need to push the volume up button when the led light turns green when booting up to access the bootmenu. I've had cases where reboot menu recovery went to stock recovery instead of 2nd-init.
Its also a good idea to wipe cache\dalvik cache when flashing things like lockring mods, framework themes, and most theme related mods in general.

skeevy420 said:
I'm gonna add, since the recovery option in the power button menu doesn't always access 2nd-init recovery (depends on the rom), nor is that option available in all roms, you just need to push the volume up button when the led light turns green when booting up to access the bootmenu. I've had cases where reboot menu recovery went to stock recovery instead of 2nd-init.
Its also a good idea to wipe cache\dalvik cache when flashing things like lockring mods, framework themes, and most theme related mods in general.
Click to expand...
Click to collapse
When i start the phone up the led turns blue a few seconds before the boot animation appears... its that when i want to press the volume up key

hotshot545 said:
When i start the phone up the led turns blue a few seconds before the boot animation appears... its that when i want to press the volume up key
Click to expand...
Click to collapse
My fault, its Volume Down, and yes, the green blink before the blue is when you push it.
I got it confused with Stock Recovery, which is Power Button+Volume Up while turning on the phone.