Related
I just got my incredible last Saturday cause I thought the Droid X was too laggy. Im a little bit familiar with rooting as I had my old g1 rooted and flashed a bunch of custom roms to that.
I've been researching the Droid incredible rooting process and think I wanna do it. But I have some questions first.
1. I'm currently on the latest OTA update. If I root, is there an easy way to go back to stock if I wanna claim warranty or download the gingerbread OTA when it comes out? If so how?
2. Is this stable for a rookie programmer to do? What are the odds i'll brick it?
Thanks for all your help in advance!
-TAF-
Sent from my Droid Incredible using the XDA app.
Unrevoked is simple. Couldn't be any easier really. Cake walk compared to rooting my D1.
Haven't gone back to stock on the incredible, but did it for a friend on the D1, and it was simple. I have seen people say that going back to stock on the Incredible is simple also.
As far as Gingerbread goes, we (rooted Incredibles) will most likely have it first, because of leaks. We already have several ROM's with the Gingerbread keyboard, and the ROM is sure to follow shortly.
I would suggest you Root. You wont regret it. The Dev's for the Incredible are fantastic. They are all making quality ROM's and you will love them. Guaranteed!
The only thing tricky in rooting the Incredible is the SLCD screen causes issues and you have to have a zip file on your SD card. The tutorial will link to it.
Lsdozer said:
Unrevoked is simple. Couldn't be any easier really. Cake walk compared to rooting my D1.
Haven't gone back to stock on the incredible, but did it for a friend on the D1, and it was simple. I have seen people say that going back to stock on the Incredible is simple also.
As far as Gingerbread goes, we (rooted Incredibles) will most likely have it first, because of leaks. We already have several ROM's with the Gingerbread keyboard, and the ROM is sure to follow shortly.
I would suggest you Root. You wont regret it. The Dev's for the Incredible are fantastic. They are all making quality ROM's and you will love them. Guaranteed!
The only thing tricky in rooting the Incredible is the SLCD screen causes issues and you have to have a zip file on your SD card. The tutorial will link to it.
Click to expand...
Click to collapse
The only thing I'm worried about is if I have an SLCD or not and unrooting instructions. Every search I do only comes up with an unroot back to stock method for 2.1 eclair that doesn't work on froyo.
Sent from my Droid Incredible using the XDA app.
Here are easy rooting/ unrooting tutorials:
http://www.incredibleforum.com/foru...rooting-stock-2-2-using-unrevoked-3-22-a.html
http://www.incredibleforum.com/foru...s/5723-how-get-back-complete-stock-s-off.html
Well, the rooting Part is extremely easy. But, when using unrevoked make sure you select a custom recovery image, that works with sLCD incredibles (i have one), or else you can't see anything going on with it. (black screen white lines, driver issue). If you want ill post a link up. But I rooted mine the second day I had it, and this is my first smartphone period. And I took java 1 and 2 last year in highschool, so i am no programmer. Its incredibly easy.
Now, I havent come across anything, anything for unrooting. So, if you can wait, dont root.
And..pretty sure, when you get the Gingerbread OTA, it will unroot your phone, and bring it back to stock.
techobsessive said:
Well, the rooting Part is extremely easy. But, when using unrevoked make sure you select a custom recovery image, that works with sLCD incredibles (i have one), or else you can't see anything going on with it. (black screen white lines, driver issue). If you want ill post a link up. But I rooted mine the second day I had it, and this is my first smartphone period. And I took java 1 and 2 last year in highschool, so i am no programmer. Its incredibly easy.
Now, I havent come across anything, anything for unrooting. So, if you can wait, dont root.
And..pretty sure, when you get the Gingerbread OTA, it will unroot your phone, and bring it back to stock.
Click to expand...
Click to collapse
Yeah dude if you could post a link to that custom recovery so I could check it out id be awesome!
Sent from my Droid Incredible using the XDA app.
Just go for it and root it. I was worrying about it for months and then I did it and was rooted in 10 minutes and had a custom ROM installed within 2 hours WITH all my data restored.
Incidentally, I can easily recommend Myn's Warm TwoPointTwo RLS4 ROM for Incredible http://forum.xda-developers.com/showthread.php?t=809985
It's insanely fast and stable, and the overclocked kernel gets surprisingly good battery life. And, go through some of the extras for it in that thread if you take a look, some are quite handy like Hulu and the Supercircle battery.
Also, the flipclock actually flips
enlightened79 said:
Here are easy rooting/ unrooting tutorials:
]
Click to expand...
Click to collapse
Will I be able to re SOn my device so I can claim warranty if it ever breaks after that unroot tutorial?
Sent from my Droid Incredible using the XDA app.
Should be a way on here, but if you treat your Incredible well/decently, it's not gonna break/a better phone will be out by then anyway. The benefits of root greatly outweigh the voided warranty. (My personal thoughts on "Manufacturer's Limited Warranties", however, could be an entire thread by themselves)
PGleo86 said:
Just go for it and root it. I was worrying about it for months and then I did it and was rooted in 10 minutes and had a custom ROM installed within 2 hours all my data restored.
It's insanely fast and stable, and the overclocked kernel gets surprisingly good battery life. And, go through some of the extras for it in that thread if you take a look, some are quite handy like Hulu and the Supercircle battery.
Also, the flipclock actually flips
Click to expand...
Click to collapse
The only thing I'm really worried about is my warranty and being able to unroot back to stock if I need to send it in(i have a knack of bad luck of phones breaking for no reason and me breaking phones)
I treat my electronics well. I just don't have the money for a new 500 buck incredible . I'm a struggling 18 year old paying for college and a car as well.
Sent from my Droid Incredible using the XDA app.
Yes- first step in the tutorial is actually how to turn s-on if you so choose.
As far as the custom recovery image goes, here is the basic instructions from the first link posted regarding the recovery.
Step 3A- For those with SLCD screens (Sku ends in 3) start here:
NOTE- You'll see a black screen with white bars if you go into recovery. DO NOT PANIC- we're going to fix that right now by doing the following:
Unplug your phone and close the unrEVOked window.
Download the following file and extract it somewhere you will remember: http://dougpiston.com/files/Recovery...MG_cwm_mod.zip
Start the unrEVOked tool again and go to file -->custom recovery.
Select the recovery.img that you extracted.
Plug in phone (charge only), enable usb debugging and let the tool run.
Note: If tool hangs at waiting for reboot (safe to unplug), that's normal. Unplug the phone and plug it back it. The tool should now saw "complete".
Turn phone off and reboot into HBoot by pressing the power and volume - (down) buttons at the same time
Continue with instructions in Step 3B
Click to expand...
Click to collapse
taffy333 said:
(i have a knack of bad luck of phones breaking for no reason and me breaking phones)
Click to expand...
Click to collapse
http://ohioloco.ubuntuforums.org/showthread.php?t=1382833
OP there was me. If you can boot AT ALL, you can restore.
taffy333 said:
The only thing I'm really worried about is my warranty and being able to unroot back to stock if I need to send it in(i have a knack of bad luck of phones breaking for no reason and me breaking phones)
I treat my electronics well. I just don't have the money for a new 500 buck incredible . I'm a struggling 18 year old paying for college and a car as well.
Sent from my Droid Incredible using the XDA app.
Click to expand...
Click to collapse
Heh I bet I have less money..... 15 yr. old highschooler with no job and $25 every 2 months from my grandma
I've broken my fair share of electronics, and have had faulty ones; from what I've seen Incredibles are insanely reliable (though most modern smartphones are).
However, rooting isn't for everyone. Like it says in the root tutorial thread, don't root to be cool. Do it if you actually want/would use features of root, esp. custom ROMs.
I came from a sprint hero. and ended up with a Slcd DINC. After reading up rooting took all of like 5 mins. But I bet I have less money.. 3 girls in school. and a wife in RN school. Im the only one working,lol But then again. my cars and such are paid for. no bill outside the norm. and my cells..
Just ordered the seidio rugged case etc.. to protect my DINC... cant wait. cause I sure cant afford to buy a new one if it breaks.lol
PGleo86 said:
Heh I bet I have less money..... 15 yr. old highschooler with no job and $25 every 2 months from my grandma
I've broken my fair share of electronics, and have had faulty ones; from what I've seen Incredibles are insanely reliable (though most modern smartphones are).
However, rooting isn't for everyone. Like it says in the root tutorial thread, don't root to be cool. Do it if you actually want/would use features of root, esp. custom ROMs.
Click to expand...
Click to collapse
Thanks guys. I eventually rooted. I did it wrong the first time and almost lost my phone (slcd issue). But the unroot guide helped bring me back. I re rooted and all went well. Haven't found the right custom Rom yet. Ill keep looking though.
Sent from my Droid Incredible using the XDA app.
Glad you did it and got it right
Sent from my ADR6300 using XDA App
I seem to be having an issue with my phone overheating and rebooting. It seems to happen consistently when using navigation or when playing games (I'm hooked on Gem Miner). Always at an inopportune time. To me this seems like a result of bad hardware or something but is it possible that rooting and installing ROMs like CM7 or Kingdom Stock Sense?
I bought my phone at Best Buy and ended up getting the warranty, so assuming I can revert the phone back to stock, I should be able to get this covered under warranty. Right?
My phone gets hot when under stress, but that's totally normal. But for it rebooting, that could mean bad hardware. What rom are you on? Some roms will run hotter than others.
Sent from my HTC Incredible
Well how it is it getting before it reboots? I think at 119F it will reboot/shut off and flash the LED. Seems like kernels can also impact heat, as well as custom undervolting mods.
TheWhiteBandito said:
My phone gets hot when under stress, but that's totally normal. But for it rebooting, that could mean bad hardware. What rom are you on? Some roms will run hotter than others.
Sent from my HTC Incredible
Click to expand...
Click to collapse
I was using CM7 for a while (pre-7 and up to 7.0.3) and recently tried Kingdom Sense. Under both of those I could only get a few moments of navigation before it would just completely shut down.
I actually just restored the stock ROM (though I'm still running S-OFF) and it doesn't seem to be overheating anymore. I guess I'll have to see what happens. It would totally suck if I am forced to stay on the stock experience after having been rooted/ROM'd for so long...
k_nivesout said:
Well how it is it getting before it reboots? I think at 119F it will reboot/shut off and flash the LED. Seems like kernels can also impact heat, as well as custom undervolting mods.
Click to expand...
Click to collapse
Hot enough that it's shutting down. I couldn't tell ya specifically.
k_nivesout said:
Well how it is it getting before it reboots? I think at 119F it will reboot/shut off and flash the LED. Seems like kernels can also impact heat, as well as custom undervolting mods.
Click to expand...
Click to collapse
Its higher than 119F. Mine hit 122F the other day and didn't reboot, unless the safety shut off didn't kick in on mine. Don't think it is much higher than that though before it does.
I had heard it shuts down at 119 but my phone hasn't ever gotten that hot. I've only managed to get it up to about 114, that was multitasking and charging, overclocked to 1113.
When it reboots, do you get 5 vibrations and then the indicator flashes green until you pull the battery? If so, you are starting to have serious problems.
This thread helped me recover my Incredible..
http://forum.xda-developers.com/showthread.php?t=982454
I had mine at 120F the other day loading a new rom and no shut off
Sent from my Incredible using XDA Premium App
Mine gets hot when using wireless tether.
jetsaredim said:
I was using CM7 for a while (pre-7 and up to 7.0.3) and recently tried Kingdom Sense. Under both of those I could only get a few moments of navigation before it would just completely shut down.
I actually just restored the stock ROM (though I'm still running S-OFF) and it doesn't seem to be overheating anymore. I guess I'll have to see what happens. It would totally suck if I am forced to stay on the stock experience after having been rooted/ROM'd for so long...
Click to expand...
Click to collapse
I'm leaning toward a hardware issue. The reason I say that is because I'm using CM7.0.3 and Chad's Incredikernal and when I use navigation I also connect my car charger and have never had a heat issue nor any reboots. I drove from SC to FL back in Feb and had navigation running the whole time.
Yea, I'm thinking its a hardware issue. I just downloaded Cut the Rope and can consistently get it to reboot/overheat after about 10-15 min of play. Only problem is that I'm not sure if the geniuses at the Best Buy warranty center will notice the S-OFF or not and if so how do I revert that when I don't have CWM on my phone anymore...?
jetsaredim said:
Yea, I'm thinking its a hardware issue. I just downloaded Cut the Rope and can consistently get it to reboot/overheat after about 10-15 min of play. Only problem is that I'm not sure if the geniuses at the Best Buy warranty center will notice the S-OFF or not and if so how do I revert that when I don't have CWM on my phone anymore...?
Click to expand...
Click to collapse
You can get S-On by using the "S-On" tools by unrevoked, Don't think I can post links just yet but you can copy/paste the URL below, it should help guide you.
unrevoked.com/rootwiki/doku.php/public/forever
Scroll down to the bottom of the page and you should see a FAQ section.
How can this be removed or undone if I need to take my phone in for service?
Download the latest ''S-ON'' tool to a temporary location and follow the installation instructions above to run it. Once your phone is S-ON, you may lose root permanently if you install an official update
The link to the S-On tool can be found at the URL above, I copied/pasted so you would know what to look for.
fLaWx said:
You can get S-On by using the "S-On" tools by unrevoked, Don't think I can post links just yet but you can copy/paste the URL below, it should help guide you.
unrevoked.com/rootwiki/doku.php/public/forever
Scroll down to the bottom of the page and you should see a FAQ section.
How can this be removed or undone if I need to take my phone in for service?
Download the latest ''S-ON'' tool to a temporary location and follow the installation instructions above to run it. Once your phone is S-ON, you may lose root permanently if you install an official update
The link to the S-On tool can be found at the URL above, I copied/pasted so you would know what to look for.
Click to expand...
Click to collapse
I assume you're not completely an expert in this matter, but let me see if I get this right... I have to go back to having CWM on my phone so I can apply the S-ON zip and then re-run the stock recovery to get back to complete 100% stock. Sound right? I wouldn't even consider it if I didn't think there was a slight chance that I'd get flagged on the warranty review for having S-OFF set. I don't want them to have any reason to deny my getting a new phone.
Hi - long time lurker, barely ever post, but I'm gonna chime in here.
My DInc also reboots, and it is warm to the touch when it does happen. Don't know how hot though sry. I've been rooted since November, but haven't installed a Custom Rom, just removed bloat, and added some other useful tools. The biggest change I've made was changing the fonts. I don't over/under clock either (it runs just fine for me). My reboots seem to be increasing in number. At first it would be once a month, then a few times a week, and now a couple times a day.
Sometimes, my phone will reboot just once, and then continue to work. Sometimes 2-3x in a row, and then continue to work or not. Sometimes, it just vibrates 5x quickly, and then is locked (LED flashes), and the only way to recover is to pull the battery and start over.
Seems to happen MOSTLY around certain times of day - 4:30-6pm when I'm on my way home from work (no, not using my phone, but it happens anyway), and around lunchtime (again, not using it, or if I am it's barely). Other times it happens too - but really randomly. I'm ruling out different apps that might be triggering it, but don't think that's the issue.
QUESTION - if it is heat related, and the phone is supposed to go into shut-down mode at 119*, but seems to be different temps for everybody, could it be the thermostat? Could it be registering a false temp reading and think it needs to shut down? Has anyone explored this?
I'm not an engineer, or even a programmer, but I like to play one on TV. Thx
Oh - I forgot to add this:
There have been times when it would reboot, and I've placed my phone and battery (removed from phone) on the vents of an airconditioner, or even sitting on a frozen ice pack (the kind for a cooler) and it would still happen afterwards. To the touch, my phone would be cold, not freezing, but cold. Seriously lower temp than what it was when it was very warm to the touch...
I'm definitely with you on the first scenario. I just brought it to my local Best Buy where I bought it (with warranty) and they sent it off and gave me a loaner DInc to use till mine's repaired. They said, if they can't repair it, they'll give me a DInc2 as a replacement since the Dinc1 is "backordered" (aka not being carried).
jetsaredim - I was able to get a replacement DInc sent to me overnight (free!). My first replacement had a faulty USB port, so I couldn't charge my phone. I have 'another' DInc being sent to me now. Other than the faulty USB port, I haven't had any overheating issues so far (knock on wood).
First phone manufactured in June 2010
First replacement phone, manufactured in April 2010, and remanufactured June 2011 (via ##7764726)
I just got my replacement Incredible today. I just tested my original phone again by watching 15 minutes of video on youtube and BANG!!!!!!!!!! It rebooted as usual. Screen and battery get very warm. The reboots seem to happen when watching videos online or offline, playing games for 10 to 15 minutes, browsing the web for 15 to 20 minutes, using Google Maps with or without charging at the same time, and charging and talking on the phone at the same time. Well, I'm sending back the original and hoping that the replacement doesn't fail me. Glad that I swapped it just before the manufacturer warranty was up.
Have had the Dinc since week one. 100% stock - have not rooted (yet) and stock battery - in the past month it has 'overheated" and rebooted twice. Never happened before. Both times while using navigation and charging. Could it simply be the battery? It's not holding a charge like it used to too which also makes me wonder about the battery.
its rooted. s-off supersonic....i cant tell ya all the specifics of the phone but i wanted to change to 4g start up screen with the blocks and the start up sound. I think it was called a splash screen? Anyways. The phone doesn't hold a battery charge as it is. it went dead in my pocket and when i charged it back up and tried to start it up it just sticks on the splash screen i think its called? its a pic of my daughter and i. then usually it would then go to htc 4g evo quietly brilliant screen. it does not. the only thing it will do at this point is go to the screen of my pic i put in of me and my daughter. it does a lil vibrate for a sec as well. where do i go from here? lol lol im already invested in this phone for about two weeks of time. i get through everyother prob thanks to you guys but im stumped on this one.... please help...plus my screen is cracked. anyway to get a new screen cheaper than trying to use insurance to get a new one? thank you.....DuBBzILLa
Try to power off the phone. Then hold volume down + power buttons at the same time until the bootloader appears. Use the volume down button until RECOVERY IS HIGHLIGHTED, followed by the power button. You should see an option on the list to wipe. If you can, try to find and wipe only the Cache and then Dalvik cache. The reboot the phone.
got into clockworkmod
thanks a ton.....NOW...hehe. Can ya help me out with gettin my wifi back on and let me know two other things? can you get the alpha.apk or blackmarketalpha app american link. i downloaded it so i can grab apps for free but its in islamic writing. i can see some american writing but the site usaually crashes. and the other thing was how can i get the free hot spot wifi tethering? can some one line me up with what a rom is and which one is best for this htc evo 4g. i think i have a clue but im trying to get something where you can store up to 5 different roms on the sd card? also. i would like to get some links to some cool kernels. i have no idea what a kernel is either but some of these guru are blowing my phone out the water and i have the same phone. if poss. list the direct sites to guides and lead me to the up to date software outthere. is there anything i should be staying away from and i have cracked screen as well. is that easily replaceable because dubbzilla.weber is broke and has no insurance on this rooted device thanks short doggs. that was way cool of you because i almost chucked it into the mississippi. whew. amen to you guru's. what are you using and can ya teach me the way?
[email protected] said:
thanks a ton.....NOW...hehe. Can ya help me out with gettin my wifi back on and let me know two other things? can you get the alpha.apk or blackmarketalpha app american link. i downloaded it so i can grab apps for free but its in islamic writing. i can see some american writing but the site usaually crashes. and the other thing was how can i get the free hot spot wifi tethering? can some one line me up with what a rom is and which one is best for this htc evo 4g. i think i have a clue but im trying to get something where you can store up to 5 different roms on the sd card? also. i would like to get some links to some cool kernels. i have no idea what a kernel is either but some of these guru are blowing my phone out the water and i have the same phone. if poss. list the direct sites to guides and lead me to the up to date software outthere. is there anything i should be staying away from and i have cracked screen as well. is that easily replaceable because dubbzilla.weber is broke and has no insurance on this rooted device thanks short doggs. that was way cool of you because i almost chucked it into the mississippi. whew. amen to you guru's. what are you using and can ya teach me the way?
Click to expand...
Click to collapse
My friend it sounds like you need to take a ride over to development section ahd just read. There are tons of options for your Evo and the best bet would be to do some research on everything Sense, AOSP and MIUI roms. All have there pros and cons. Now for wifi tethering you can get that in the market. For up to date software just google latest software for your Evo. Not trying to discourage you but I think the more you learn on your own the better you feel at the end.
Cracked screen once again not sure where you live but check craigslist for people who fix them or once again check google. Take your time man and just read up on things it will be well worth it in the end to understand why you are doing what you are doing and not because a thread said you could....
Goog luck
ok long story short. never flashed a kernal before but i decided to try cm10 and went with the gingerbread build and so i flashed the kernal and cm10 compatible rom. it wasnt running very well so i flashed back to the froyo kernal and the compatible cm10 rom.
all was ok but i wanted to go back to cm7 because the phone was considerably faster and so...
today tried to restore one of my cm7 kang back ups from recovery and the phone died. i think what happened is i got mixed up with the back ups and i must have restored the gingerbread cm10 first and without realiszing it flashed the cm7 with a froyo kernal and bang we have a dead phone. it simply wouldnt boot past the google lettering and so when i got home i decided to flash a full sbf and start from scratch however when i tired i got the dreaded battery low error so i followed this
http://forum.xda-developers.com/showthread.php?t=892026
and it worked but rsd lite didnt show my phone. there was simply nothing there when i started it. all very annoying so i uninstalled everything and by the time i started again i got the message battery low.
so my question is can mcgyver work if the battery is actually really low say 10-20 per cent or less?
is it worth buying a new fully charged battery and using that?
why wouldnt rsd lite recognize my phone?
is there anyway to charge the battery when it is like this?
nb. i am running windows 7 sp1 and have installed the latest drivers and rsd lite am my phone is a moto defy m525 red lense.
all very annoying and in five years of rooting and flashing i have never been in a situation where i couldnt recover it. too be honest i have been here before with the defy but i had a spare battery and a proper wall charger and so that was problem solved but i dont own them anymore and i am now not sure/ cant remember if a simple full battery will help hence the questions.
In theory it should work. You are supplying the terminals with the intended 5V and a ground.
However it is recommended to charge your battery, use an external battery charger and then flash the SBF. Its hell of a risk trying to flash SBF with low battery. The phone may actually brick with no way to restore it.
it is strange but using the mcgyver method i can get the bootloader ready to program i simply cant get rsd lite to see my phone and neither does windows. there are loads of posts and threads on this but not many (none actually when the situation i am is mentioned) offer a solution.
so i have ordered a new battery which will hopefully arrive tomorrow and i will see how we get on from there.
rockmonkey1973 said:
it is strange but using the mcgyver method i can get the bootloader ready to program i simply cant get rsd lite to see my phone and neither does windows. there are loads of posts and threads on this but not many (none actually when the situation i am is mentioned) offer a solution.
so i have ordered a new battery which will hopefully arrive tomorrow and i will see how we get on from there.
Click to expand...
Click to collapse
do u have blank flash mode enabled in rsd?
does defy show up in device manager?
try switching usb ports
Sent from my MB526 using xda premium
nogoodusername said:
d
try switching usb ports
Sent from my MB526 using xda premium
Click to expand...
Click to collapse
doh!
amazing i simply used another cable and usb port and then i had to unplug it and plug it again and drivers started to be installed. (i had already installed motos drivers but hey windows wanted more!).
i also went back to the older 4.9 version of rsd lite. it has been a long long time since i have had to do this. installing nordic and will try and install one of my other back ups. all should be well very soon fingers crossed.
looks like the spare battery i bought will be going back then. oh well.
cheers mate your post prompted me to try again and just tinker and it worked so appreciate that.
edit: seems a bit stuck and i am now a little unsure what to do. the android bootscreen is stuck and rsd lite is saying maually power up this phone. i am a little concerned because it is still saying in process even though it has flashed the sbf. i have tried turning it off and nothing happens. it looks like i am actually going to have to unplug the cables remove the mgyver wires and take out the battery and boot it.
bollox. it is dead again so i have to start again. trying a different sbf this time. not sure what happened there. maybe i was too impatient?
honestly not sure what is happening here. i have tried a standard blurred sbf 2.2 and the phone is now stuck on the m animation and rsd lite iks omce again saying manually start this phone. what in the world do i do next?
ah god i will have to do some more reading because it is ****ed. i now have a white light and black screen. rsd lite just remained stuck at 100 per cent in process and manually boot your phone. have tried it three times and that is all i get. not sure if it is because i am flashing froyo sbfs when i have had a 2.3 kernal on the device? it is why i have avoided flashing them in the first place and the first time i ever do bang i get a bricked phone when i try to restore it back to cm7. the phone came with 2.1 so should i be flashing them?
very boring and very very annoying.
getting quite tired of this little game and am on the brink of buying another phone.
ok i have a red lense defy and after much reading i have realised that i must be flashing the wrong sbfs now call me stupid but i actually am very confused about which one i need to flash.
i started on 2.1 originally then i flashed 2.2 and then stuck cm7 on the phone with a froyo kernal. however when i upgraded to cm10 i tried the 2.3 kernal.
so with this background in mind will this work???
http://forum.xda-developers.com/showthread.php?t=1595013
can i follow this to flash the sbf and get root?
or is there another sbf i need to flash. all i need to be able to do is root the phone and install cwm and then i can flash one of my back ups (properly this time).
rockmonkey1973 said:
ok i have a red lense defy and after much reading i have realised that i must be flashing the wrong sbfs now call me stupid but i actually am very confused about which one i need to flash.
i started on 2.1 originally then i flashed 2.2 and then stuck cm7 on the phone with a froyo kernal. however when i upgraded to cm10 i tried the 2.3 kernal.
so with this background in mind will this work???
http://forum.xda-developers.com/showthread.php?t=1595013
can i follow this to flash the sbf and get root?
or is there another sbf i need to flash. all i need to be able to do is root the phone and install cwm and then i can flash one of my back ups (properly this time).
Click to expand...
Click to collapse
Thats for BL7.. Some Defy+ with 2.3.6 were BL7. You definitely don't need to flash it..
Just flash the last SBF that worked for you..
neo.ank said:
Thats for BL7.. Some Defy+ with 2.3.6 were BL7. You definitely don't need to flash it..
Just flash the last SBF that worked for you..
Click to expand...
Click to collapse
yes mate i did the last sbf i flashed over a year ago was nordic and i got the error as listed above. have no idea what i am doing wrong but i must be doing something. trouble is the new battery has arrived and i have already tried a new sbf and still getting the same problem... manually need to reboot the phone.
bit worrying because obviously i will only have a certain number of tries before this new battery dies on me.
edit: absolutely annoying. part of the problem with the guides on here are that they are mostly incomplete. they dont actually tell you everything you need to do. take for instance this the guide for unbricking
http://forum.xda-developers.com/showthread.php?t=1828639
it is totally useless because what he fails to mention is that
to boot into stock recovery you need to hold down the volume button when you power on the phone and you will get a droid with an exclamation mark and then you need to hold down both the volume up and down buttons which after a few seconds will take you to stock recovery. then you can wipe cache etc and the phone will boot. i found this out here (notice how people are telling the guy to simply flash a new sbf!)
http://forum.xda-developers.com/showthread.php?t=1608812
the mad thing is if i had found that simple post just above and knew about the up and down volume buttons i would have fixed the defy on the very first try. that is what is so annoying about this situation.
ok
red lense defy.
long story short i flashed one of the bl7 defy plus gingerbread sbfs.
so i have gone through the root procedure by installing the rooted sbf in rsd lite and then i can install 2nd init 2.0.3 and can get a custom recovery installed.
but every time i try to install cm7.2 euro skank it reverts back to the bootloader. here is what i have done twice in recovery with the exact same result.
wipe cache, data, dalvik and battery stats/ flash cm7 froyo kernal/ then flash the rom/ then flash gapps and then wipe again and then reboot.
when the phone starts again i am once again back to the bootloader and i have to start all over again.
so a very simple question from the position i am in what exactly do i need to do to get cm7 running on the phone.
double post but there are worse crimes!
ok so i have realised that i am stuck on the gingerbread kernal and that any froyo based rom is not gonna work.
wow how did i end up here! bloody hell that is what happens when you start getting ****ed off with the phone not doing what you think it should. anyways it is done now and i have cm7 all up and running and have even been able to make a back up so that if anything happens in the future when i am experimenting then i have a decent base from which to start. everything is working including the camera data wifi calls and well everything except...
i have one all rather serious problem that i really need to get sorted (this is it if i can fix this then i can leave the phone alone).
my battery is not recognized. now the phone runs on the battery which is a big step up from before where i was literally having to leave it plugged in just to keep it on. but the battery icon at the top is displaying a question markn and i dont know if it is charging or not. i also have no idea how much battery is left.
i have flashed both the defy red lense ics battery zip and the defy plus battery fix and i wiped cache dalvik and battery stats before i flashed them and the cache after but neither of these worked.
anyone actually care to help out here. what do i need to do to get my battery recognized? seriously if you know then please share because i have wasted a day and a half on this and through sheer frustration dug myself into a huge hole and it took ages to climb out.
all i am asking for is a bit of guidance from someone who actually knows what they are talking about. if that sounds like you do me a favour and simply tell me what i should do because i am now totally and utterly stumped.
cheers.
rockmonkey1973 said:
yes mate i did the last sbf i flashed over a year ago was nordic and i got the error as listed above. have no idea what i am doing wrong but i must be doing something. trouble is the new battery has arrived and i have already tried a new sbf and still getting the same problem... manually need to reboot the phone.
bit worrying because obviously i will only have a certain number of tries before this new battery dies on me.
edit: absolutely annoying. part of the problem with the guides on here are that they are mostly incomplete. they dont actually tell you everything you need to do. take for instance this the guide for unbricking
http://forum.xda-developers.com/showthread.php?t=1828639
it is totally useless because what he fails to mention is that
to boot into stock recovery you need to hold down the volume button when you power on the phone and you will get a droid with an exclamation mark and then you need to hold down both the volume up and down buttons which after a few seconds will take you to stock recovery. then you can wipe cache etc and the phone will boot. i found this out here (notice how people are telling the guy to simply flash a new sbf!)
http://forum.xda-developers.com/showthread.php?t=1608812
the mad thing is if i had found that simple post just above and knew about the up and down volume buttons i would have fixed the defy on the very first try. that is what is so annoying about this situation.
Click to expand...
Click to collapse
rockmonkey1973 said:
double post but there are worse crimes!
ok so i have realised that i am stuck on the gingerbread kernal and that any froyo based rom is not gonna work.
wow how did i end up here! bloody hell that is what happens when you start getting ****ed off with the phone not doing what you think it should. anyways it is done now and i have cm7 all up and running and have even been able to make a back up so that if anything happens in the future when i am experimenting then i have a decent base from which to start. everything is working including the camera data wifi calls and well everything except...
i have one all rather serious problem that i really need to get sorted (this is it if i can fix this then i can leave the phone alone).
my battery is not recognized. now the phone runs on the battery which is a big step up from before where i was literally having to leave it plugged in just to keep it on. but the battery icon at the top is displaying a question markn and i dont know if it is charging or not. i also have no idea how much battery is left.
i have flashed both the defy red lense ics battery zip and the defy plus battery fix and i wiped cache dalvik and battery stats before i flashed them and the cache after but neither of these worked.
anyone actually care to help out here. what do i need to do to get my battery recognized? seriously if you know then please share because i have wasted a day and a half on this and through sheer frustration dug myself into a huge hole and it took ages to climb out.
all i am asking for is a bit of guidance from someone who actually knows what they are talking about. if that sounds like you do me a favour and simply tell me what i should do because i am now totally and utterly stumped.
cheers.
Click to expand...
Click to collapse
First of all Stop whining about the guides being incomplete. They have helped a lot of people before you and are still helping.. If you mean every post should mention trivial stuff like booting into recovery and wiping data then just imagine the redundancy of the stuff.
If only you were patient enough to read before reacting. Defy Beginner's guide clearly mention 'bout booting into recovery & bootloader so its your folly for not collecting the info before processing..
anyone actually care to help out here. what do i need to do to get my battery recognized? seriously if you know then please share because i have wasted a day and a half on this and through sheer frustration dug myself into a huge hole and it took ages to climb out.
all i am asking for is a bit of guidance from someone who actually knows what they are talking about. if that sounds like you do me a favour and simply tell me what i should do because i am now totally and utterly stumped.
Click to expand...
Click to collapse
Don't know what you've wasted your day on, but all I can suggest is flash the battery fix for Defy+. Search for it. not difficult to find.
neo.ank said:
First of all Stop whining about the guides being incomplete. They have helped a lot of people before you and are still helping.. If you mean every post should mention trivial stuff like booting into recovery and wiping data then just imagine the redundancy of the stuff.
If only you were patient enough to read before reacting. Defy Beginner's guide clearly mention 'bout booting into recovery & bootloader so its your folly for not collecting the info before processing..
Click to expand...
Click to collapse
whining! i didnt think i was whining although i can get annoyed and sometimes my frustration is vented without thinking. i accept that the phone being where it is is indeed my fault. in fact if i had just left it alone then it would have been running as well as it ever did. i am also a great advocate of the developers who spend there time providing us roms and tools for us to use and i can say hand on heart i appreciate the fine work they do often for free. i am also an avid reader of the guides being a simple bod with very little knowledge of flashing hacking and what not and they have saved my bacon more times than i care to remember over the last four or five years. and so you are spot on the guides help a lot... not just me but many before me and most likely many after and give us mere mortals the chance to stay current with firmware long after the manufacturer has abandoned the phone. so while i may have been complaining rather angrily i was not whining.
the fact is that guide is incomplete. not only is it incomplete but it is the one that is linked to on the wiki as the guide to follow on how to unbrick your phone.
if you are like me a tinkerer who every once in a while likes to try out a new rom and who doesnt know the every inner workings of the procedures and who needs to follow instructions then i think the least you can expect is for the definitive guide to be correct! i mean that isnt too much to ask for is it.
so yes i do expect them to list every basic important step one must follow to fix the phone because that is what instructions do they guide people who dont know what they are doing. that is there sole purpose and if they dont do that job then they should either be edited so they do or deleted.
and yes yesterday i was very annoyed at the fact that the guide i was following does not actually tell you exactly what one should do and i can promise you if it had of done then i would not be in the position i am in it is as simple as that. i mean you cant seriously expect people to think oh right these are the instructions for unbricking the phone but i bet you they aint right so i had better read some more instructions for the same thing... and hey they might not be complete as well so i had better read yet another set just in case. leave it out will you.
at the end of the day it doesnt matter and at the risk of repeating myself i know that if i had left well alone the phone would be fine so ultimately i have no one else to blame but myself. if i had been a little more patient and less stressed wondering why the phone wouldnt boot after what appeared to be a successful flash then i would have got there in the end without being stuck on a gingerbread kernal.
neo.ank said:
Don't know what you've wasted your day on, but all I can suggest is flash the battery fix for Defy+. Search for it. not difficult to find.
Click to expand...
Click to collapse
well if you had read through this thread then you may have seen i have wasted a day and a half on quite a lot of reading as it goes. you may have also seen that i have flashed 2 battery fixes and that they havent helped. so i am wondering if you know what else i could do to fix the problem? if you do and you dont mind telling me then i would be grateful. if you dont then no big deal... i will read through a few more threads and see if i cant get to the bottom of it.
EDIT: I have reread what i wrote and i take that back the guide is far from useless in fact it is excellent and i mean that. in every other way it is spot on and is the de facto guide to sorting yourself out of a hole. but it does miss out some vital information that (i think at least) really should be there. still water under the bridge and all that. we are were we are and one must move on. bottom line it is only a phone and if it comes to it i will buy another. the only reason i havent actually bought another so far is the buld quality and form factor of the defy is still yet to be bettered. but maybe it is a sign a message from above telling me to move on to pastures new.... although i would still like to fix the battery issue.
ok it is fixed. as i was writing this reply i installed the white rabbit rom (which i read included red lense battery fixes). true to its word there are five downloadable files. i got four (one woudnt download) and rebooted the system and hey presto.
well what a difference a day and a decent nights kip make. and colour me impressed. this rom is a work of genius. i see it is based on euro kangs cm7 effort with a few nice (well actually loads) extras thrown in for good measure. have to say i am really liking it. calls data wifi camera and battery all work and it looks and feels swift and very polished.
so all is well that ends well. and what a journey. man all i wanted to do was restore cm7 from my back ups. flashing the gingerbread based cm10 before i did it i reckon screwed me and i didnt realise what i had done until after when it wouldnt boot. however xda saved the day as it always does (even if it did take me quite a lot time to get there this time round). i may even write a mini guide but then either no one would bother reading it or i would get loads of people whining at me telling me how it aint right so i think i will avoid that little task and leave it to people more brave and knowledgeable than i.
cheers all for the help in this thread, the time taken by others to write stuff down and the people who provide us with some great software for our ageing but still great phone.
me to
pls help
jalal-jap said:
me to
pls help
Click to expand...
Click to collapse
if you need help mate then a little bit more info is gonna be required.
i will say this that i havent quite fixed it completely. i have the rom running sweet as a pie and the phone will work away from a power source but the battery percent/ icon remains locked at 100 per cent so i have no way of knowing if the phone is charging. when i plug it in to my laptop it says usb connected but again it doesnt list it as charging. so i have no way of knowing if the battery is actually getting charged or how much is really left.
i am also far from an expert more a bumbling old timer who rarely posts here unless desperate.
bear all that in mind and i will do all i can to help (provided you specifically say what you want help with)
edit: lmao... i couldnt have picked a worse sbf to flash. amazing. i have been so so careful in all the time i have owned this phone (over a year i reckon now) and i may have finally actually broken it.
i aint even certain i can charge the battery and once it runs down it will simply die. obviously there is hope that someone will come up with a downgrade method at some point in the future but for the time being i think the phone is ****ed.
i will try ics tomorrow and see if i can get any joy there but i think the only way i can now use the phone is to buy an external battery charger. funny really i used to own both a spare battery and a charger for this very reason and yet i sold them when i got rid of the old defy. so i am gonna have to buy one off ebay tomorrow and use it that way. at least then i will be able to use the phone.
rockmonkey1973 said:
if you need help mate then a little bit more info is gonna be required.
i will say this that i havent quite fixed it completely. i have the rom running sweet as a pie and the phone will work away from a power source but the battery percent/ icon remains locked at 100 per cent so i have no way of knowing if the phone is charging. when i plug it in to my laptop it says usb connected but again it doesnt list it as charging. so i have no way of knowing if the battery is actually getting charged or how much is really left.
i am also far from an expert more a bumbling old timer who rarely posts here unless desperate.
bear all that in mind and i will do all i can to help (provided you specifically say what you want help with)
edit: lmao... i couldnt have picked a worse sbf to flash. amazing. i have been so so careful in all the time i have owned this phone (over a year i reckon now) and i may have finally actually broken it.
i aint even certain i can charge the battery and once it runs down it will simply die. obviously there is hope that someone will come up with a downgrade method at some point in the future but for the time being i think the phone is ****ed.
i will try ics tomorrow and see if i can get any joy there but i think the only way i can now use the phone is to buy an external battery charger. funny really i used to own both a spare battery and a charger for this very reason and yet i sold them when i got rid of the old defy. so i am gonna have to buy one off ebay tomorrow and use it that way. at least then i will be able to use the phone.
Click to expand...
Click to collapse
You're on BL7 now and there's a reason people advise to avoid it. Most of the fixes and scripts doesn't work with BL7 including the battery fixes.
I'd suggest you to go for Quarx's build for GB kernel (along with the battery fix), Randomly flashing ROMs and fixes won't help.
Moreover, I strongly recommend you to search and read carefully. You're not the first one to face the problem, and there's a solution. Even if you waste(?) a couple of days reading 'bout it, it won't kill your phone, but if you do something out of desperation it might.
neo.ank said:
Moreover, I strongly recommend you to search and read carefully. You're not the first one to face the problem, and there's a solution. Even if you waste(?) a couple of days reading 'bout it, it won't kill your phone, but if you do something out of desperation it might.
Click to expand...
Click to collapse
i take it you mean this like in retrospect? of course you are right a deep breath and a walk does wonders for a fuddled head and is far better than simply rushing into the next desperate attempt to repair. however it is easy to say this after the event yes!
the battery wont charge and if i flash another rom it gives me the big battery icon with question mark so i am once again stuck in a corner with no where to go. basically it is ****ed because none of the battery fixes work. the battery works when there is power in it but it just wont charge when in the phone. because the battery ran down last night the only way i can use my phone at the moment is tethered to the mcgyver trick.
so the plan is to buy a separate charger and use that to charge the battery. then i reckon i should be at least able use the phone (although this yet to be tested).
amazing seriously amazing. a year of owning this phone a year of flashing and hacking and being ultra conservative and then all it takes is a few minutes of madness and it is royally screwed. the crying shame about it is that i have installed the best rom i have ever seen in the white rabbit and if the external charger doesnt work i wont get to play with it! still live and learn.
edit: by the way do you know if the mcgyver trick actually charges the battery?
.
rockmonkey1973 said:
i take it you mean this like in retrospect? of course you are right a deep breath and a walk does wonders for a fuddled head and is far better than simply rushing into the next desperate attempt to repair. however it is easy to say this after the event yes!
the battery wont charge and if i flash another rom it gives me the big battery icon with question mark so i am once again stuck in a corner with no where to go. basically it is ****ed because none of the battery fixes work. the battery works when there is power in it but it just wont charge when in the phone. because the battery ran down last night the only way i can use my phone at the moment is tethered to the mcgyver trick.
so the plan is to buy a separate charger and use that to charge the battery. then i reckon i should be at least able use the phone (although this yet to be tested).
amazing seriously amazing. a year of owning this phone a year of flashing and hacking and being ultra conservative and then all it takes is a few minutes of madness and it is royally screwed. the crying shame about it is that i have installed the best rom i have ever seen in the white rabbit and if the external charger doesnt work i wont get to play with it! still live and learn.
edit: by the way do you know if the mcgyver trick actually charges the battery?
.
Click to expand...
Click to collapse
The battery fixes replace your battd.bin binary file which stores the info about the battery. Surprisingly there isn't a single binary that work with each phone, it acts weirdly and not sure what fix will work for a particular phone.. I again suggest you, every battery fix you find. You're not the first one to face the problem and its been sorted for many..
Mcgyver just supply the device with intended charge as the battery does. It doesn't charge the battery.
Don't know if you tried this one.
Defy Red Lens Battery Fix
neo.ank said:
The battery fixes replace your battd.bin binary file which stores the info about the battery. Surprisingly there isn't a single binary that work with each phone, it acts weirdly and not sure what fix will work for a particular phone.. I again suggest you, every battery fix you find. You're not the first one to face the problem and its been sorted for many..
Mcgyver just supply the device with intended charge as the battery does. It doesn't charge the battery.
Don't know if you tried this one.
Defy Red Lens Battery Fix
Click to expand...
Click to collapse
i have tried it mate. i have also tired the ics defy red lense and the white rabbit rom had four of them available to download. none of them have worked. basically as it is now the phone will not stay on without the mcgyver leads and the battery wont charge. i have flashed 6 different battery fixes.
edit: it is strange once i have given it a blast on mcgyver for an hour or so i can then use the phone normally. however the battery is locked at 100 per cent and there is no indication it is charging when a usb lead is plugged in. seriously i have tried 6 of the fixes and none have actually worked.
if you are saying there is a fix for this then i would love to know what it is because i havent found one yet.
edit again!!!: ok this is strange because now when i plug it in to a usb lead the green light appears as if it was charging. very very strange this. i mean like really ****ing weird.
final edit: ok i am officially giving up. it has beaten me and for the first time ever i have got myself into a situation that i cant get out of. who would have thought a simple battery would be the cause of so much ****ing grief. anyway. for total clarity.
i am now running white rabbit rom runs great highly recommended and way quicker than the cm10 efforts that are being worked on at the moment. i have tried 6 battery fixes. none work. i am sometimes able to use the phone without being connected to the mcgyver leads but the battery remains locked at 100 per cent. other times the phone dies and the only way to boot it again is the mcgyver leads. if i do that then battery may change to say 25 per cent or even 75 per cent. basically it is all over the shot. i have tried to install another rom and this leads to the exact same thing. if i turn it on without the mcgyver leads i get the battery error. sometimes when connected to the usb port the phone has the led green light like it is charging then other times it doesnt. it is basically well and truly ****ed up.
so i am giving up. i have wasted quite enough time on a phone i have been thinking of changing as it is. i am gonna buy a sensation as a short term replacement. not as nice as the defy form wise but far faster and with a decent modding community so it will do for now. i will return here every now and then to see if someone comes up with a way to downgrade the bl7 but until that happens the phone is gonna gather dust in my drawer.
i think this thread serves as decent guide as to what shouldnt be done if you want to unbrick your phone (and also includes a few little things that may be missing elsewhere) so hopefully someone can learn from it. cheers all and see you later.
ok well this is the end of this thread (unless i find a proper working solution).
i was unable to charge the phone unless i used the mcyver trick. basically the only way it would accept a charge was if the mcgyver leads were connected. however the battery would charge once the mcgyver leads were in place but stays locked at 100 per cent no matter what i do. it may be the rom i am using but every time i tried another i got the battery error.
i have now bought an external battery charger and spare battery. it works a treat. i simply use the charger to charge one battery and use the other battery to power the phone. when the battery dies i simply switch them around and use the phone as normal.
this way i am no longer having to boot the phone using mcgyver and the only thing i am missing is the ability to charge the battery internally or tell how much battery life is actually left.
so all told all is well that sort of ends well. at least i can carry on using the defy. i was looking at buying another phone but they are all either too big or too slippy/ fragile in the hand. the only one i would like to buy is the orange san diego but there is no root and even worse there is no sim unlock. so for the time being i will stick with the nearly indestructible defy and hope that moto see sense and release a four inch, 8mp onboard camera and better screen carbon copy. fingers crossed.
First off the evo was officially released in june 2010. Only a few months till we are wishing our evo happy third birthday. Oh I have heard a rumor floating around that the Og Evo is one of the most active devices on XDA.
I have been a member here for a few years. I started with the cricket zio. Then the Og Evo, a 3vo for my girlfriend at the time, and then I fell victim to a boot loop of death. So back to my old a$$ Samsung Messenger II (I had already given the zio to my son as a music/media/911 device) till I could pick up another evo. Found a bad esn hybrid black front/white back og with no battery and seller stated vibration did not work. For $40 shipping paid. Thankfully I didn't sell my 3500 mA extended battery or mid-grade otter box case when I sold my first evo on ebay for $80. Remember it had bootloop of death and also a bad esn.
With some of our phones actually being three years old there are bound to be cataclysmic failures showing up. Over the past few weeks I have noticed a common problem spread out over the massive selection of roms we have. There was nothing really that the roms shared except for the fact that just this one person, never the same one that I can remember, would have this STATUS 7 ERROR during the flash causing the installer to abort. The first couple of times it came up I just passed it over as some wierd error due to something completely different than the real problem.
The following is from a the cm7 unchained thread.
Well with these problems popping up I have been thinking about implementing an old trick. You know about changing partion sizes. We can enlarge the boot and system partions and reduce the data size. We then use a2sd to make up for what we used on the other two. Now all I need to do is add the adjustment to the installer-script.
Although there is a side effect of this. When a different kernel is flashed it will not know how to read the partions. So then the user has to flash another script to change the partion parameters in the new kernel.
Now to shine a light on what the issue is that is causing what seems to be a random problem. The evo has been around since June 2010 and is getting old. The more recovery logs I see the more bad blocks I see. The memory only has so many write cycles before it burns out.
Now with all rom flashing we do just takes another write cycle from the evos life. If we start digging further into the lives of our users we will notice two groups with issues. The older phones (from '10 or '11) and the addicted flashers/developers. Both of which have used up some of their lives testing and flashing.
True be told we can bandaid the evos memory with symlinks to the sdext till we only have the files needed to symlink everything else to the sdext. Only problem will be the transfer rate of sdcard.
Hope this was enlightening and informative. Also if you have not noticed I am working on the TNN Rom toolbox which will help everyone in finding a solving the problems as they pop up.
The thread is in general discussion but only gives highlights of what will be coming. I still have to write the install script to copy logcat automatically to the TNN folder and create a md5sum of the rom flashed. Now I will have to add in the partion adjustments and make a kernel fix script so different kernels can be flashed.
Peace,
Love, and
Happiness
Extra power for my development
Well I have recently lost my job which is why I have been able to get all the roms out so quickly and with very few if any bugs.
Then on a few days ago PlatinumPenguin tells me that he has a 3vo sitting unused in his desk drawer. He states that the Og Evo just sounds so much better than the 3vo on his headphones. Long story short he is packing up the 3vo and giving it to me. Talk about a nice guy. So I will move to the 3vo as my phone with service and have the Og completely free for developing purposes.
Then yesterday my buddy tells me that he has an Inspire that his wife wants to put back on att. The problem is that he dropped it and shattered the screen. Then got upset about it and threw it at the wall damaging the power button and volume keys. No power button no phone right. Well it just so happens that I know a trick or two. He hands me the phone and started to walk away. I quickly do my trick and power up the phone before he gets a few feet away. I tell him to watch this phone boot up. Trick is you take the battery out, connect the charger to phone and wall, and then reinsert the battery. B.I.N.G.O. Houston we have lift off.
Now he offers me his bad esn evo with shattered screen if I can replace the screen and get the buttons working on the Inspire. For those unfamiliar with the Inspire it is part of the evo family. It was an att phone almost exactly like the Thunderbolt except it has no ffc.
Now I have two Og Evo's to use for development purposes. Now I can flash two roms at the same time First I have to root the two new to me evos and an Inspire.
Then maybe I can get the TNN Toolbox written up on post 1. With a collection of other tips and tricks for our evo on post two.
Umm time to hit the rooting section of all three phone. It has been awhile since I have done the Og (hw003 latest update from sprint installed Nov '11) the second evo came rooted. I did the 3vo back around august of last year. It took me some time to figure out exactly how to do it. I didn't use the wire trick which had just come out for the 3vo.
Anyways stay tuned for more innovations from Team No Name. They will be coming to a server near you soon. Long live the Evo. Even if we end up running 90% of our roms from a symlinked sdext. Heck who needs internal storage anyways.
Peace,
Love, and
Happiness
Re: The State of the elderly Evo Hopefully help will be on the way.
Two
Look forward to this. Count me in to assist where I can. Still noobish as far as development but pretty savvy in regards to understanding how this works and a quick learner.
Sent from my Galaxy Nexus using xda premium
Re: The State of the elderly Evo Hopefully help will be on the way.
Oh wow I just powered up this bone stock evo 4.67.651.3. I am going to do a timed boot comparison but it sure looks like the stock one takes twice as long to boot.
It is kind of mind blowing to think that there really is that much difference between a stock and modded phone. They are both hw004 so I can use all my nands on both phones. Oh just so you know I had already booted my newly acquired evo a few time before I started both at the same time. No cheating since both already had a dc made.
Re: The State of the elderly Evo Hopefully help will be on the way.
This is almost like finding out my old EVO has cancer and the more I flash it the more the cancer spreads.
I've had my OG Evo since December 2010 (still stock and unrooted). I recently BOYD'd it over to Ting and bought my wife a used OG Evo off of Glyde. Hers I rooted (my first root ever) without issue and am running MBQsniper's Triple S. I am planning to root my device once I get all the bugs worked out of hers, get SMS copied over, etc.
So, needless to say, I've recommitted to the OG Evo at least until Sprint (and therefore Ting) kills wimax and maybe longer. I'm glad there are people around that are much more knowledgable than I that are still paying attention to this device. It's also funny how everyone seems to be from Texas...
jlmancuso said:
The evo has been around since June 2010 and is getting old. The more recovery logs I see the more bad blocks I see. The memory only has so many write cycles before it burns out.
Click to expand...
Click to collapse
If this is the point you are making the thread title camouflages it somewhat. But it's a very good point.
Can I add another important point regarding the advanced age of our "elderly" Evos?
Batteries also decline with age.
There was a recent discussion around here about buying a replacement battery, which size, which brand, blah blah.
If you are replacing an original launch day stock battery that has been through hundreds of charge/discharge cycles, I can guarantee the details of your replacement battery do not matter as long as it is new.
I had been using a replacement battery for a while and just for the hell of it put in my original battery a week ago. After calibrating and letting it go through a few cycles, I was completely blown away by how bad the battery life was. Same ROM, same usage pattern, just went back to the old battery. I just ended a 13 minute call and watched my battery go from 50 to 15. What is that, 40 minutes of talk time on a full charge? No one would sell a mobile phone like that (not today, not three years ago, 1986 or ever).
So all you people inheriting old Evos (or trying to find new life for your own vintage Evos), please, before you clutter up ROM development threads with comments on battery life, REPLACE YOUR FREAKIN BATTERY FIRST.
Now if they could just "recondition" the non-replaceable flash memory to get rid of those bad blocks..
NxNW said:
If this is the point you are making the thread title camouflages it somewhat. But it's a very good point.
Can I add another important point regarding the advanced age of our "elderly" Evos?
Batteries also decline with age.
There was a recent discussion around here about buying a replacement battery, which size, which brand, blah blah.
If you are replacing an original launch day stock battery that has been through hundreds of charge/discharge cycles, I can guarantee the details of your replacement battery do not matter as long as it is new.
I had been using a replacement battery for a while and just for the hell of it put in my original battery a week ago. After calibrating and letting it go through a few cycles, I was completely blown away by how bad the battery life was. Same ROM, same usage pattern, just went back to the old battery. I just ended a 13 minute call and watched my battery go from 50 to 15. What is that, 40 minutes of talk time on a full charge? No one would sell a mobile phone like that (not today, not three years ago, 1986 or ever).
So all you people inheriting old Evos (or trying to find new life for your own vintage Evos), please, before you clutter up ROM development threads with comments on battery life, REPLACE YOUR FREAKIN BATTERY FIRST.
Now if they could just "recondition" the non-replaceable flash memory to get rid of those bad blocks..
Click to expand...
Click to collapse
True that. I had to go back to my original battery and it's stupid how bad battery life is.
As for the bad blocks, funny how 2 years ago, we believed you could write/re-write millions of times with no ill effects
Looks like you've been doing your homework brother,this looks to be promising.
Well actually most of the partition adjusting is old stuff. I just have to find a way to change the boot size. They were doing this back in the hero days.
Sent from my PC36100 using xda app-developers app
I am getting a status 7 error. Sucks, I loved my OG Evo
Sent from stock rooted Galaxy SIII
Status 7 error is a fail on installing boot image. I suggest removing the lines in the installer script for the boot.img and flashing a kernel separate. The use of a smaller kernel may solve the issue.
Sent from my PC36100 using xda app-developers app
Write cycles for NAND chips are in the order of 10k. Do we have fruity modders surpassing this number?!?
Wild!
0_o
Well lets look at it this way. 10,000 writes over 3 years (oldest evo) over 365 days and we have 9.13 writes a day. So while a 10k life sounds long it is over quicker than you think.
Hope this helped shine some light on the subject.
Sent from my PC36100 using xda app-developers app