did a search and didn't find a specific answer.
My charging port pretty much went to crap on my evo so I need to bring it in for repairs in the morning (replacement)
Now, I know how to unROOT my phone, but What I don't know is...
Will It remove/replace all stock boot images/animations, or do I need to do this before I unroot?
If I need to do it manually, could anyone help me out with a how to?
Thanks guys.
and just so im clear, When my phone boots up, there is an image and then an animation.
If you just unroot, everything will be the same as it is now, except you wont have SU access. If you flash the stock rom back on, like you should if you are taking it in, then that will replace everything, including boot animations and the recovery. It will literally be like you first got it out of the box.
And again, you ABSOLUTELY SHOULD return to the stock rom so you dont void your warranty.
http://theunlockr.com/2010/06/14/how-to-unroot-the-htc-evo/
That might be what you're looking for.
EVERYTHING whould return to stock, boot animations, splash, and what not. But the files from rooting and root apps will still be on the SD card, so if you're feeling savvy, I'd swap out one of my old cards while it is in for service. Or just be honest with the repair guys. Most of them are rooted anyways...
I used to work at the store I'm taking it to for repairs, and the bossman and me never did get along, if i just had to deal with the rep's it would be easy haha.
Thanks.
Related
He ran the original OTA update the day before yesterday, he didn't run it twice like everyone else that had issues.. He's not bricked in the "won't power on or boot" sense of the term, it WILL boot up. But it's pretty much completely unusable, it keeps trying to remove and install widgets on its own, the touch screen does the opposite of whatever he touches, swiping between screens hangs and sits in between each screen, it keeps opening the htc weather widget and won't let you back out of it.. voice search keeps popping up randomly. It tries to install the htc coin flip widget, a lot. It basically takes 5 to 10 tries to get anything to work right, and when something does work right it's only for a minute.
He wasn't rooted in any way, and he tried doing a factory restore through the settings menu, as well as formatting the sd card.
Radio shack has no eta on a replacement and sprint says to just return the phone and get a different kind of phone if they are out of evo's (seriously..? wtf).
You guys are smart, is there anything he can do to try and troubleshoot this?
there currently isnt a way to root after the ota update, so the suggestion to try some cooked roms is out the window.
i dont want to be the bearer of bad news, but it doesnt look good.
I think he can try restoring to factory.
Download this:
http://www.joeyconway.me/evo/stock/...Radio_1.39.00.05.31_release_171253_signed.zip
Rename it PC36IMG.zip and put it on the root of the SD card.
Turn off the phone, hold volume down and turn it on, it should boot into hboot, sort of a factory recovery
It will automatically detect the zip file and ask if you want to apply it. Select yes, and it should restore to factory.
If you continue to have problems, then there is probably something wrong with the phone and it'll need to be returned.
Hope this helps!
Could this in anyway void my warrenty or make sprint un-willing to give me a new phone/ repair my phone if this fix does not work?
if that is stock, they would not be able to find out even if it further messed up the phone by attempting that method
...err taking a look, if he has the newest ota, then I am not sure if that link will work because it is a lower version. you would need to find the one that is for 1.47...
I am not even sure if that would work, but hey it is worth a shot if the phone doesnt work already
Use this ruu
It'll bring you back to stock with the latest OTA included.
Hello,
Last night I rooted my device using this (http://forum.xda-developers.com/showthread.php?t=1265429) method and file from zedomax and everything worked great except when I booted my device there was a yellow triangle with a black “!” in it. I figured that just indicated the device was rooted or running a 3rd party kernel so I didn’t worry about it.
Today I launched my camera app and it failed to load the interface but showed the image from the camera momentary then crashed back to the home screen. I restarted my device and when the device restarted it was very slow and unresponsive and after unlocking it my live wallpaper was gone replaced with the last background I used before selecting a live background a couple weeks back. No icons or widgets loaded and I am unable to open the settings tray. The only things I am able to do with the phone is pull down the notification bar, respond to text messages, adjust the volume and hold power to restart the phone. All of which are very slow and delayed.
When I connect the device to my computer windows is no longer able to load the drivers and Kies is unable to connect with the device. I am not sure what caused this or how to resolve this issue so any advice or known fixes would be fantastic! I am unable to get to clockwork mod to restore my backup and I am unable to get to Kies or the phone settings to do a factory reset so I really don’t know what to do they were supposed to be a last resort and now I don’t even think I can do them. I am an experienced techie but I am new to android and this is the first device I have rooted so any advice would be great no matter how basic it may be.
UPDATE: I just connected the phone via USB to my laptop at work and it was able to discover and install everything it needed to connect with the phone. I am installing Kies now so at least there is hope of a factory restore, although I really hope it doesn't come to that!
Boot into download mode and flash the stock eg30 tar file from crawrj.
Sent From My Evo Killer!!!
Thanks Already started doing that waiting for it to download now
Still no touchwiz... great!
Try flashing a stock rom via clockworkmod.
efarley said:
Still no touchwiz... great!
Click to expand...
Click to collapse
You can root again and restore your backup, or go to this website www.lostandtired.com (midnight roms blog) click on android development and download and flash the sprint bloat and TW restore zip. Hope that helps.
I flashed the stock rom which didn't change anything so then I used clockworkMod to do a factory reset which ended up trapping me into a boot loop. I could use Odin to flash new roms but the device would never go past the 4G logo
I ended up taking the device back to Best Buy and since the loading screen showed the stock rom and they couldn't get past the 4G logo I just had to say it wasn't rooted and they gave me a new one.
I would love to know if anyone has any idea of what went wrong here so that I can feel comfortable rooting again. Also if anyone has some basic articles handy that teach basics of rooting that would be great, I didn't even know about clockwork mod until after I had this problem so knowing things like that earlier would have helped a lot I think. I'll be spending the weekend looking up everything I can find on the subject so any reading you guys can suggest would be fantastic.
efarley said:
I flashed the stock rom which didn't change anything so then I used clockworkMod to do a factory reset which ended up trapping me into a boot loop. I could use Odin to flash new roms but the device would never go past the 4G logo
I ended up taking the device back to Best Buy and since the loading screen showed the stock rom and they couldn't get past the 4G logo I just had to say it wasn't rooted and they gave me a new one.
I would love to know if anyone has any idea of what went wrong here so that I can feel comfortable rooting again. Also if anyone has some basic articles handy that teach basics of rooting that would be great, I didn't even know about clockwork mod until after I had this problem so knowing things like that earlier would have helped a lot I think. I'll be spending the weekend looking up everything I can find on the subject so any reading you guys can suggest would be fantastic.
Click to expand...
Click to collapse
If you a clockwork and "stock rom" you were still rooted...Doing a factory reset will send you into bootloop when rooted. Trying to flash other roms on a bootloop is not going to work. You need to have grabbed a backup such as Zedo has on his post and put the backup in clockwork folder on your phone. Then flash that in CWM. Would of brought you out of bootloop to a stock rom with his kernal. Now you can flash Roms and kernals or could of flashed crawf or anyone else FULL stock rom and been back to stock kernel and rom and not rooted.
dallastx said:
If you a clockwork and "stock rom" you were still rooted...Doing a factory reset will send you into bootloop when rooted. Trying to flash other roms on a bootloop is not going to work. You need to have grabbed a backup such as Zedo has on his post and put the backup in clockwork folder on your phone. Then flash that in CWM. Would of brought you out of bootloop to a stock rom with his kernal. Now you can flash Roms and kernals or could of flashed crawf or anyone else FULL stock rom and been back to stock kernel and rom and not rooted.
Click to expand...
Click to collapse
Ohhhh that's what happened! Awesome thanks. I will be much better prepared with backups out the wazoo this time haha.
Now if only I could figure out why Touchwiz died in the first place hmmm....
I hope you can figure it out, just postin here to say that when I saw this thread, it reminded me of the thread over in the EVO forums about the guy who claimed that sprint removed his Sense from his phone.
Khilbron said:
I hope you can figure it out, just postin here to say that when I saw this thread, it reminded me of the thread over in the EVO forums about the guy who claimed that sprint removed his Sense from his phone.
Click to expand...
Click to collapse
haha SPRINT removed it?! So that person thinks sprint monitors every device and has a team of techies on staff to hack your phone and brick it if you break their rules?... yeah that totally makes more sense than a file got corrupted when you were messing with the kernel.. some people maybe shouldn't be rooting their devices in the first place haha
I had cyanogenmod 7 installed on my EVO and one day my phone just turned itself off. This time it will only boot up to the white HTC EVO screen then power itself back off and continue to cycle. I loaded into bootloader and tried to go into recovery. As soon as I select recovery it goes right back to the white screen and continues to loop. I tried to clear storage and recieved the same results. I searched a tone online and tried to find a resolution. As far as I can get is install the boot interface driver and HBOOT USB the phone. All root programs get stuck at the "waiting for device". Any help would be much appreciated.
Drake13 said:
I had cyanogenmod 7 installed on my EVO and one day my phone just turned itself off. This time it will only boot up to the white HTC EVO screen then power itself back off and continue to cycle. I loaded into bootloader and tried to go into recovery. As soon as I select recovery it goes right back to the white screen and continues to loop. I tried to clear storage and recieved the same results. I searched a tone online and tried to find a resolution. As far as I can get is install the boot interface driver and HBOOT USB the phone. All root programs get stuck at the "waiting for device". Any help would be much appreciated.
Click to expand...
Click to collapse
sorry but you're pretty much S O L on this, has something to do with a bad boot.img and you can't get it to take another one might as well file a lost phone claim and pay the $100 and get a new one thats what i had to do and they just happened to have sent me the 3d instead so i guess i got a bit lucky.
i still have my evo 4g and still working on it but its been about a month and i haven't had any luck with it.
Sounds like you have no recovery or not completely rooted. You could try to put a recovery CWM or Amon-Ra file renamed PC36IMG.zip onto your sd card from your computer, put card back into phone then go in to hboot see if it will flash you a recovery then try to go into it
If that doesn't work search for a stock ruu file for the Evo, rename PC36IMG.zip, place on your card, put card back in phone, flash through hboot. This will return your phone to stock unrooted, then you try the process again
Sent from my PC36100 using XDA Premium App
That's what happened to my phone also..It just happened out of nowhere..
I tried everything and in the end I had to file an insurance claim.
And once again, a phone running CM7 goes into this mysterious unfixable bootloop.
What is up with that?
What is up with that, I'm about to remove this rom its not really all that. Its already messed up my keyboard, sometimes I have to take the battery out just to restart it.
I Loved CM7 when I had it, but then i started seeing all these bootloop issues start up in the early part of Summer, and I refuse to put it back on. Sorry to those that dev and support it, but seriously, out of all the cases on here, and there have been a bunch, only one was on a phone that didn't have CM7 on it.
HipKat said:
I Loved CM7 when I had it, but then i started seeing all these bootloop issues start up in the early part of Summer, and I refuse to put it back on. Sorry to those that dev and support it, but seriously, out of all the cases on here, and there have been a bunch, only one was on a phone that didn't have CM7 on it.
Click to expand...
Click to collapse
Most of those phones from the 'CM Scare" had bad nand blocks, and it had to be replaced. They had them frothe very beginning, but just decided to act up then. It also happen to some users using MIUI.
Okay my speaker got distorted so I decided to unrooted to take it in for service. Now the phone is unrooted but theres only one problem! Now the phone will boot up to the normal home screen but within 2 to five minutes, it shuts itself down and boot back up to home screen again and the cycle starts again. I have reset few times but same ting' happens. Now sprint is ordering a new phone for me hope its not the 3D i don't think I like it. So now I have my evo still but will give it to sprint once my new phone is in at the sprint store tuesday! Oh by the way, beside the speaker problem the phone was working fine as normal before the unrooting. thx
teh roxxorz said:
t also happen to some users using MIUI.
Click to expand...
Click to collapse
No! Don't say that!!
tony_2018 said:
What is up with that, I'm about to remove this rom its not really all that. Its already messed up my keyboard, sometimes I have to take the battery out just to restart it.
Click to expand...
Click to collapse
I've been using CM for about a year and NEVER had either of those two problems. There has to be an issue with something else you've loaded onto the phone that isn't playing nice.
Concordium said:
I've been using CM for about a year and NEVER had either of those two problems. There has to be an issue with something else you've loaded onto the phone that isn't playing nice.
Click to expand...
Click to collapse
No one ever said every install of CM7 will lead to this bootloop, but almost every case of this bootloop, the user was running CM7
HipKat said:
No! Don't say that!!
Click to expand...
Click to collapse
Miui is based of cm's fixes and what not right?
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702
No, MIUI is not based on CM. It's a completely different ROM
Yeah but I'm pretty sure they use their fixes since its a port
Having trouble with AOSP? http://forum.xda-developers.com/showthread.php?t=1295702
It's true that most of the cases happened on CM7, but from what I understand it can happen on any rom... and has happened on Sense and AOSP.
There's no known fix. You can try to RUU, but even if the RUU flashes properly, the phone will never boot. You're eternally stuck with hboot/fastboot. File an insurance claim, that's about all you can do. I had a similar problem with a stock, never-been-rooted Evo. I got a replacement through insurance without paying the deductible, but I was s-on.
Hopefully I don't get slammed for suggesting this, but if you don't want to pay the deductible for a "lost" phone, you can flash a radio through hboot and pull the battery. If you do it at the right time, the phone will completely brick and never turn on again. It may take a few tries. Then you can take it in and you shouldn't have to pay the deductible, as long as you play dumb of course.
I think this happens due to bad nand blocks on your boot partition, so the main cause is hardware. Something in the rom triggers the never-ending splashscreen bootloop (I'm assuming something related to the boot.img). I could be entirely wrong about this though.
You can't live in fear, if it happens it happens. It's one of the risks you take when rooting and flashing. The number of cases is small compared to the number of people with rooted Evos, especially considering only a portion of people are active on this site, and a lot of the reports come from members that wouldn't post or even be a member if they didn't have the problem. I wouldn't let the possibility deter you from running whatever rom you want.
Sent from my Evo + MIUI using Tapatalk!
I myself am stuck with same issue. Nothing takes. So where does hboot reside when loaded? I also have looked in vain for diagnostic flashes....
Now one thing I noticed is that I installed PDAnet and it shows it installed an app to the phone, however I cant connect. I think cause I cant boot the phone and enable what it telling me to...so how is it this software can load an apk and I cant?
Overall, I am now however learning and it has become a hobby.
Theres an answer somewhere I would think. Thinking maybe its time to tear apart and look for jtag points....
I have had this happen to me a few times, I leave the RUU on the sd card and when this happens and do what bimmerman7 wrote on the first page. This has always worked for me when I get stuck in a bootloop when trying to access recovery.
Just got this phone and I love it but the seller on ebay had it rooted and had one of the roms from here on it. They said they would put it all back to stock for me. I like to start with a clean slate if you know what I mean. Well, it is back on gingerbread but root is still there and a whole bunch of other stuff (apps, roms, titanium backup) etc etc in folders on the internal storage. My question is can I safely get this phone back to being stock just like it was from the factory, without the risk of bricking it? I know how to use Odin for the Epic 4G and all. I knew there were some problems with the touch and some phones getting bricked. I have no clue what they may have done to the phone so I am a bit concerned to do anything to it till I hear from someone who has done this (gone completely back to stock) Also, is there a tutorial somewhere?? Thanks guys for your help with this.
Oh here is some more info if it helps looks like I am on Android version 2.3.6, EL29, kernel 2.6.35.7 there is some other info if you need it please let me know I do see a Caulklin's folder in there in the internal storage so most likely they did have that rom on there at one time. There is also a ACS folder in there but when I try to open any of the folders in there I get an error that there is no program that can perform this action. Grrrrrr
Hi.
When messing with Gingerbread, especially stock, bricks are pretty hard to come by nowadays.
Here is what I suggest:
http://forum.xda-developers.com/showthread.php?t=1433101
(from what you said, you probably understand this already)
Just run the EL29 OC. You'll be good to go.
In terms of the internal storage, just delete it all or run a format. You won't get yourself in trouble that way, it's just the internal storage.
If you're concerned about the data wipe brick, that is only on ICS. So since you're on GB, it is not a problem (and totally unrelated to clearing internal storage.)
Post back if you have any questions or anythin'.
If you are on gingerbread then there is no danger of the EEMC superbug(As far as I've heard/read). As for reseting I don't have a link to a tutorial off the top of my head, however the process is pretty simple. Start searching through the development forums for the stock odin files and then flash them. I can try to find you a tutorial/links tonight but I don't really have time right now...besides the search function works the same way for you as it would for me! Feel free to ask if you need anything else!
Hahaha MochaCharok beat me to it!
Thanks guys. The phone at one time was on an ICS rom and yes I can search for it. I just wanted to make sure before I did, that this could be done. So, I will see about finding the tutorial and how to go about getting the phone all back to factory like. I know I am so anal this way, but I really do like to start with a clean slate before I do anything to any phone. thanks again guys I will holler if I run into any problems. LOVE this phone though.
thewadegeek said:
If you are on gingerbread then there is no danger of the EEMC superbug(As far as I've heard/read). As for reseting I don't have a link to a tutorial off the top of my head, however the process is pretty simple. Start searching through the development forums for the stock odin files and then flash them. I can try to find you a tutorial/links tonight but I don't really have time right now...besides the search function works the same way for you as it would for me! Feel free to ask if you need anything else!
Hahaha MochaCharok beat me to it!
Click to expand...
Click to collapse
When you activated the phone on your account it should've wiped everything they had on the phone prior and reset it to stock. At least that's what happened when I activated a phone I'd bought from an XDA member. So I started with a clean slate automatically.
It didn't for whatever reason. I had to go in and edit the MIN and MDN manually to get it to activate so maybe that is why. That thing was a HUGE pain to do too. It would not take and kept resetting. Had to try it like 5 times.
Esoteric68 said:
When you activated the phone on your account it should've wiped everything they had on the phone prior and reset it to stock. At least that's what happened when I activated a phone I'd bought from an XDA member. So I started with a clean slate automatically.
Click to expand...
Click to collapse
If you are stuck with what to do next then take it to a Sprint store and let them wipe it for you.
Good info
As I'm going to try this and hopefully get the missus off her Opt S and onto an E4GT this week this was good timing to cover the process.
Here's what I am planning to do:
1) Flash EL29 + Root
2) Factory Reset from Recovery (which should clear NVRAM if I understand correctly)
3) Call MVNO and have them set up phone
4) Allow hands-free activation to hopefully fill in the blanks
If this works as I hope then I shouldn't have to tinker manually with the NVRAM data.... if not then I have my phone to base most of that off of. And of course it depends if the carrier will let me set the phone up - in the past they haven't been warm to using a different phone unless you purchased it directly from them.
All this just to sit tight until we can get the GS3 probably next year.. yeesh.
I've searched and found lots of evidence that this issue should be fixable (which is great!)
What I'd like to know is: if a Gnex successfully boots to the Google splash but does not go any further, is there any way that it WOULDN'T be salvageable? If so, how, and is there any easy way to determine this with phone in hand?
It might be obvious by the nature of this question, but I'm looking at buying a Gnex as described. I have 2 already so I'm well familiar with the Gnex tool suite here, just wanted to see how likely the chance of truly getting a brick is.
Thanks!
Hate to "bump" this but might be buying this device tonight. Anyone?
it all depends of why its not booting. it can be as simple as flashing another kernel or rom(if its not booting) or it could be a brick(the real kind, a paperweight).
try to go to recovery or CWM, wipe date n cache. restart. before that, stock rom or custom rom? me too face this kind of problem after it drop to the floor but after wipe data in recovery(im using stock JB) restart the device and everything back to normal. the worst part is all the data is gone.
t3mp3st said:
I've searched and found lots of evidence that this issue should be fixable (which is great!)
What I'd like to know is: if a Gnex successfully boots to the Google splash but does not go any further, is there any way that it WOULDN'T be salvageable? If so, how, and is there any easy way to determine this with phone in hand?
It might be obvious by the nature of this question, but I'm looking at buying a Gnex as described. I have 2 already so I'm well familiar with the Gnex tool suite here, just wanted to see how likely the chance of truly getting a brick is.
Thanks!
Click to expand...
Click to collapse
I guess you'll never know for sure until you have the device to test.
http://forum.xda-developers.com/showthread.php?t=1812959
Best thing, if you're just buying it, is to try and get to fastboot. If you can do that then try and flash the factory image. If that boots then at least you know phone is working and you can then go about flashing a new ROM if that's the route you wanna take