-
After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.
Root no power !!!!!!!!
- Thread starter patsfann
- Start date
-
- Tags
- htc evo design
braxton355
Android Enthusiast
I've heard of it happening before on his rom.
grad061980
Newbie
It's not the rom
The problem was caused by the cwm recovery. If I remember right, it was the .7 version & was fixed in .8. I don't think there's a solution besides grabbing another phone to charge your dead battery or buy another fully charged battery. I would suggest to make sure you are running the .8 revision of cwm if & when you are able to boot back up. Your phone will remain dead until a charged battery is put into it.
patsfann
Well-Known Member
the battery was fully charged !! & not sure what recovery i have , so i'm trying the battery charging right now ..........will let you know if that works !!!!! i'm keeping my fingers/toes,legs & anything else i can cross ............................thank you all 4 the info , did'nt think it was the rom but was'nt sure what the cause is !!!!!
braxton355
Android Enthusiast
We understand, but try if you can to charge it up some how.
grad061980
Newbie
Good luck. You might try a different sd card. Sometimes a corrupt sd card can cause trouble. Just wondering, did you before your phone died perform any mod or install any new apps? Maybe something along those lines.
braxton355
Android Enthusiast
I mean its worth trying. I sent in a rooted lg optimus and they sent me a brand new one without any trouble within 5 days. But that's LG /:
2fast4u88
Android Enthusiast
Actually I believe this is the first time this happened with my rom. The other issues were partition errors if I recall correctly. If I had to take a few guess, it would be as follows. First is the plugging in and nothing happens. It could likely be you installed one of the old recovery's with the charging issue that is floating around. I still believe they are even on here after numerous times saying not to use them because of the issue.
The other is if not the above it is likely a hardware fault or something else done that isn't mentioned. I know playing with the hboot partition will cause exactly as you said. Where I know of a aosp rom I would never flash on a phone because that person had no clue what he was doing. Where it would wipe partitions not even close to right of what was needed. Any way back to the hardware fault, it may have just been that. It may have also been due to the overclock based on my kernel. Where at the set boot speed nothing bad should happen.
So you may have raised that above that. Which if true sorry to say you took the risk pushing it that high.
The other is if not the above it is likely a hardware fault or something else done that isn't mentioned. I know playing with the hboot partition will cause exactly as you said. Where I know of a aosp rom I would never flash on a phone because that person had no clue what he was doing. Where it would wipe partitions not even close to right of what was needed. Any way back to the hardware fault, it may have just been that. It may have also been due to the overclock based on my kernel. Where at the set boot speed nothing bad should happen.
So you may have raised that above that. Which if true sorry to say you took the risk pushing it that high.
patsfann
Well-Known Member
i know its not a charging prob. , i was able 2 use another phone 2 charge my batt. & my kernel was set at 1920/368 ,,,,, so I don't think it had anything 2 do with your rom or kernel , but i am a noob so i'm can't be 1hundred % sure , but i did not do anything other than try 2 open FB .... i'm thinking its hardware (atleast i'm hoping) , that is why i did not give you a shout out (2fast) , like i have said b4 your stuff rocks (i will b reinstalling your rom & kernel again ) so if & when you can please hook me up with the new recovery & whatever updating you have done 2 xfuziion 4.3.2 / daily use of cm10 (stable)..........thank you every1 who has responded 2 this thread ....
I wouldnt say 1920mhz is really that safe, My phone does run stable at that but any higher and it will jam (maybe if i add more i can get more speed but truthfully i would rather run 1.2ghz and be-able to use it all i want all day.) The phone stock is at 1.2ghz, to run at 700mhz over stock(about 59%) isnt really that small amount... I have had other phones that wouldn't run anything over stock speed. I really think your Phone had a hardware failor is my guess but I dont know for sure. (could have been somewhat becuse of overclocking but cant say for sure).
grad061980
Newbie
I never could run at 1.9 on my old hero s. It would lock up & reboot. 2fast & I tested all the way up past 2.03. His phone would handle a little faster clock than mine. 1.8 was the top for me.
2fast4u88
Android Enthusiast
Actually it was probably the running 1920mhz, which I hope you didn't have it set to performance. I generally run 1.6 to 1.8 on smartass v2, where I believe I recall someone in here saying to use my kernel on different governors or use the old version of the kernel. It may have not been here but if it was the person mentioned something about not using smartass.
How ever the people didn't build the kernel nor do they know much about the hardware specs of this line of phone. The cpu is actually the same as what is in the shift 4g and merge. How ever we got the cpu's out of production that is factory overclocked to 1.2 from the 800mhz. Being we got the better batch most of our phones will run higher clocks then the 800mhz clock ones. Now back to smartass the reason I run it as I have got reboots from heat while doing the kernels. The ondemand governor is either the lowest clock or the highest clock with generally none in between speeds. The performance governor nets smoother speed but is running the max clock you have set.
Smartass v2 will only scale up based on work load from I believe I have it set at 806mhz. It may not be the fastest governor but will save battery life, produce less heat, less hard on the cpu and use the max clock when needed. This is why I recommend it over the other to noobs and use it myself. If using the other governors above 1.6ghz I would recommend to keep it out of the heat, set a profile for when charging, then set a profile if battery temp gets to high while using gps or similar. Smartass you will better off in the long run.
Also for reference any overclock will help, the apps to test it mainly suck. Anyone remember back in the day overclocking pc's for a little 100mhz clock? I do and was something you could notice. The problem with a phone versus a pc is the cooling. So you have to be more careful what you are doing with it.
How ever the people didn't build the kernel nor do they know much about the hardware specs of this line of phone. The cpu is actually the same as what is in the shift 4g and merge. How ever we got the cpu's out of production that is factory overclocked to 1.2 from the 800mhz. Being we got the better batch most of our phones will run higher clocks then the 800mhz clock ones. Now back to smartass the reason I run it as I have got reboots from heat while doing the kernels. The ondemand governor is either the lowest clock or the highest clock with generally none in between speeds. The performance governor nets smoother speed but is running the max clock you have set.
Smartass v2 will only scale up based on work load from I believe I have it set at 806mhz. It may not be the fastest governor but will save battery life, produce less heat, less hard on the cpu and use the max clock when needed. This is why I recommend it over the other to noobs and use it myself. If using the other governors above 1.6ghz I would recommend to keep it out of the heat, set a profile for when charging, then set a profile if battery temp gets to high while using gps or similar. Smartass you will better off in the long run.
Also for reference any overclock will help, the apps to test it mainly suck. Anyone remember back in the day overclocking pc's for a little 100mhz clock? I do and was something you could notice. The problem with a phone versus a pc is the cooling. So you have to be more careful what you are doing with it.
patsfann
Well-Known Member
im sorry i forgot 2 put , min. 368, max. 1920 , set @ smartassv2 ...., deadline, i ran it @ that from dy 1 & about 3 months later this , thats why i'm (hoping) hardware !!! & keeped it in my window (cold) , but did have a couple of times of it getting hot & freezing up , (hence the window ) ....still thinking might be hardware ! do you think HTC will say anything about being unlocked/rooted ?