Develop Bugs

EVO hung up on reboot loop!

ok, guys... something is totally effed up with my evo. i was trying to reroot after doing a factory reset, but now all it does is reboot from the "htc evo 4g" screen constantly. it won't even bring up sprint's 4g boot screen...
please help!

nothing?? =/

trying to do a factory reset through the android os? I dont think that takes away root. But in any case, can you still manage to get into recovery? If so you could do a nandroid restore, or flash a new rom

elegantai said:
trying to do a factory reset through the android os? I dont think that takes away root. But in any case, can you still manage to get into recovery? If so you could do a nandroid restore, or flash a new rom
Click to expand...
Click to collapse
it's weird. i tried that. it's still loops. i tried to do a nandroid restore as well, no success. i flashed dc 3.2.3 (what i was on previously) with no success.
it just loops with the htc evo 4g logo screen and then powers off and then repeats. i even tried a different microsd card, but again, no success.

Have you tried wiping cache, or even full data/cache/dalvik and then flashing a rom?

elegantai said:
Have you tried wiping cache, or even full data/cache/dalvik and then flashing a rom?
Click to expand...
Click to collapse
i'm on my 5th attempt right now...
aaaand... nope, no success.

So all you did is do a factory reset from the settings and it started boot looping? Is your recovery method up to date (if clockwork)

elegantai said:
So all you did is do a factory reset from the settings and it started boot looping? Is your recovery method up to date (if clockwork)
Click to expand...
Click to collapse
yea, i wanted to reroot it and apply a new rom. i use amon ra recovery. it was up-to-date, from what i understand.

Well crap! The only thing I can recommend is to use the starting over guide, possibly trying to use a ruu to return it to stock and the try rerooting and flashing a new Rom
Just so I can sleep comfortably tonight, you were just rerooting for fun? Because you know you don't have to reroot to flash a new Rom correct?

elegantai said:
Well crap! The only thing I can recommend is to use the starting over guide, possibly trying to use a ruu to return it to stock and the try rerooting and flashing a new Rom
Just so I can sleep comfortably tonight, you were just rerooting for fun? Because you know you don't have to reroot to flash a new Rom correct?
Click to expand...
Click to collapse
trying to use a ruu would work, if i could only boot up, which i can't =/
and yea, i wanted to get a better feel for rooting. i know i don't have to reroot, i just wanted to wipe everything and start fresh, you know, wipe the slate clean. i'm trying the recovery-windows.bat batch file now. worst scenario, i'll go to sprint tomorrow and try to get a replacement.
still, thanks for the help man!

Hmm, do you think there is a possibility you could have used the wrong image when you were trying to reroot? Or if you didn't get that far, starting at toast part 2 might get you out of the loop.
I'm sure you'll get it though!

elegantai said:
Hmm, do you think there is a possibility you could have used the wrong image when you were trying to reroot? Or if you didn't get that far, starting at toast part 2 might get you out of the loop.
I'm sure you'll get it though!
Click to expand...
Click to collapse
it's entirely possible i may have used the wrong image. i'm trying to see what this batch file will do, though it's been hung for quite some time. i tried doing toast's part 2, i got the error that the sdcard folder doesn't exist... when it was already mounted lol.. something funky is going on.
thanks i hope so...

having the same problem tried to go back to stock so i could exchange the phone. now i am stuck with the reboot loop also. if anyone figures out what to do would really love the help.

i let the recover-windows.bat batch file run overnight and it seems to be stuck at this spot:
C:\Android SDK\android-sdk-windows\tools\evo-recovery>adb-windows.exe shell nohu
p /sbin/recovery
nohup: appending output to nohup.out
i ran it while i was in recovery, and the recovery menu is weird, switching between the main menu and sub menus if i use the volume rocker to move up and down the selections... i think i'm going to go to the sprint store, act stupid, and try to get a replacement.

i bought mine at bestbuy so sprint wont look at it. until my 30 days is up with bestbuy. and cant get a replacement at bestbuy since they are out of stock. hopefully someone can fix this problem. because right now iam sol.

I have absolutely no idea what would cause this, I will try searching around to see if a similar problem was resolved. I just can't believe that it won't let you do anything from recovery. Have you guys tried a different Rom, maybe stock Rom before root? Clueless, I am hoping someone will chime in with something else to try.
Can you still remount the system as rw? Using the command: adb remount rw?
If so maybe try flashing the recovery, wiping, and then flash a stock rom?

elegantai said:
I have absolutely no idea what would cause this, I will try searching around to see if a similar problem was resolved. I just can't believe that it won't let you do anything from recovery. Have you guys tried a different Rom, maybe stock Rom before root? Clueless, I am hoping someone will chime in with something else to try.
Click to expand...
Click to collapse
it's really weird. i can't get past initial boot. i went to the sprint store and they're out of stock, so i have to wait a few days
in the meantime, i'm going to try and continue to force my will onto my evo lol. this is heartbreaking...
do you know where i can find a stock rom unroot? like a zip file? maybe that'll work? i doubt it, but worth a shot.

Yea let me get the link. Will edit...
Here is a cache of the wiki, it has links for Stock rooted roms which I would give one of those a shot. I can only find the unrooted in an exe form. I am not sure but in the boot screen you could try fast boot usb and see if the exe would run that way but I am entirely unsure about that
http://webcache.googleusercontent.c...iki&cd=1&hl=en&ct=clnk&gl=us&client=firefox-a
Also, did you see if your nand was still unlocked? And did you try reflashing recovery? Not sure, just throwing ideas out there!

elegantai said:
Yea let me get the link. Will edit...
Here is a cache of the wiki, it has links for Stock rooted roms which I would give one of those a shot. I can only find the unrooted in an exe form. I am not sure but in the boot screen you could try fast boot usb and see if the exe would run that way but I am entirely unsure about that
http://webcache.googleusercontent.c...iki&cd=1&hl=en&ct=clnk&gl=us&client=firefox-a
Click to expand...
Click to collapse
awesome! thanks!..
at this point, i'm willing to try any and all voodoo tricks as well to get my baby up and running. i'll update with what happens.
edit. no success still... i'm trying all versions of exe files.

Since you can boot into recovery, amon ra will let you mount your sdcard as a drive into windows where you can download the stock 1.47 RUU and copy it into the root of your sdcard. Once you do that, unmount via the recovery menu and wipe data/dalvik and then flash the ruu to try and get it to boot. You shouldn't need to boot fully to flash the ruu. Find the starting over post by whitslack to get the ruu.
Sent from my PC36100 using XDA App

Unsure what i did. Please help me

I was trying to install a splash screen and it would not process, so i installed the http ://forum.x da-developers.com/s howthread.php?t =752832 from here in order to gain the fastboot commands, it went thru but it complete became stuck in bootloader, making me think it replaced instead of installing on top. I read in a post that they installed .76 something. So i reflashed a pc36image i had, but it was the 2.1, didnt realize, so i followed all the step including the unrevoked steps, and installed the clockwork mod instead of the amons_ra, all i wanted to do was return to original so i can do a nandroid back up, it wouldnt let me before , because it failed, and now i realized i installed the wrong one so what shall i do, can i simply just flash amron and it will work or shall i just stay with this and suck it up. Also since im here should i just install cm6 or do i have to do more. please help asap, please i have to leave work in about 1 hour and have school next i really need my phone, thanks alot.

Alright, calm down. There's no need to panic I can barely understand what you were trying to convey. If I understood you correctly, yes you can flash amon ra and restore your nand backup. The hboot version shouldn't matter right now, you can fix that when you are less pressed for time.

i actually ended up flashing to the cm6 after 6 tries, but now my market place doesnt work, it that normal, I also added the google apps so it should work. Thanks again for you help.

nevermind, finnally started working after 5th try, I guess ill have to reflash later to anov_ because i need 4g, unless there is any custom rom that has 4g and no sense. do you know of any? thanks again sorry for panic attack.

[Q] installed new rom cant use cwm recovery now..

I installed gbtweaked0 on my r800x cdma. My wifu doesn't work and I have to use cwm to install the wifi files but every time I click install for cwm it doesn't install.. I need help thanks in advance.

I don't want to come off as mean, but please go back to the developers thread and read through it...
You have to re-install CWM, and from there flash DoomLord's WiFi .zip. EVERYTHING is in that board... You should read through it before you start installing ROMs/Software for possible bugs and issues.

I know that. But the problem is CWM Doesnt stay installed. Everytime I install it and then try to boot into recovery it doesnt work. And then I open cwm recovery and click install again try it and it uninstalls after every reboot..

I had the same problems with cwm, which is one reason I went right back to cola. There's a thread in the development forum that has a one-click install of cwm, if you use that, it should work.

I am having the same problem too. I re-installed CWM twice but it still will not let me boot into recovery mode. I am also getting a force close error with Titanium Backup even after I reassign user permissions.
The ROM works great other than that! Does anybody have a solution?

Spoke to dev he told me to reroot I havent gotten around to it busy day Im gonna try tomorrow hopefully that fixes the problems. But I have to admit I love the rom. But Im using a droid incredible right now so Ill try it tomorrow. Good to know I'm not the only one with this problem.

Ok well I tried unrooting and rooting again and Im still having the same problem. Did you try to reroot? Just wondering if maybe you got a different result?

same i tried unroot and reroot absolutely nothing changed. my home button doesnt work either now..

wyckedsyko said:
same i tried unroot and reroot absolutely nothing changed. my home button doesnt work either now..
Click to expand...
Click to collapse
Yea my home button stops working every now and then but after I turn my phone off and back on it works again.

I had the same problems, installed cwm with a computer, app, etc. I did it about 20 times in a row of install, reboot, etc etc and then one time in randomly worked and never stopped workin since

Having same issue.
Understand that the quick install of CWM only works on stock so that's why it's not working now. But even the quick instructions say to go back into CWM to flash the wifi modules which now I can't do.

I havent really been trying to fix it... But I'm gonna try more with my phone now. Im enjoying my mom's old droid incredible too much..

Sorry for the double post but here is the solution http://forum.xda-developers.com/showthread.php?t=1390771 <-- use this instead of app thank you ligthningdude

[Q] Moar 2.4

i installed the new moar. clean install. now it runs fine. battery life is great. but i have a big issue. for some reason it sometimes just goes to the bootloader and freezes up. have to gett back into recovery and reflash to get passed the bootloader again. done this mutiiple times so far. not running anything crazy either just some texts and phone calls. please if there a way to fix or something im not doing. please let me know. thanks.

yotaking said:
i installed the new moar. clean install. now it runs fine. battery life is great. but i have a big issue. for some reason it sometimes just goes to the bootloader and freezes up. have to gett back into recovery and reflash to get passed the bootloader again. done this mutiiple times so far. not running anything crazy either just some texts and phone calls. please if there a way to fix or something im not doing. please let me know. thanks.
Click to expand...
Click to collapse
What do you mean it goes into the bootloader. Need some specifics of precisely what you mean. And what do you mean by bootloader, are you talking about recovery or download mode?
Sent from my SPH-L710 using Tapatalk 2

GiantJay said:
What do you mean it goes into the bootloader. Need some specifics of precisely what you mean. And what do you mean by bootloader, are you talking about recovery or download mode?
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
I believe they means the boot animation. Unless I'm mistaken, they're getting stuck in a bootloop. I'm really interested in which Kernel option they chose when installing it. I'd say that choosing a different one would fix the bootloop issues (I tried the optimized stock one recently and that seemed to work well).
I'd suggest that the next time it happens go into recovery and clear cache and dalvik cache. Reboot phone and see if that fixes the problem (give the phone time to boot up after clearing cache). If that doesn't work, you can try fixing permissions in Recovery (I doubt that'd fix a bootloop, but it might be worth trying).
Finally if none of the above work, I'd try downloading the MOAR rom again, but double-check md5 sums to make sure it's a good download. When installing it, start with the stock kernel and see if it occurs again.

[Q] Help! Softbrick while going to CM10 or Lifeless

Hey all,
I'm trying to install either CM10 or the Lifeless ROM (links here and here: http://forum.xda-developers.com/showthread.php?t=2189788 and http://forum.xda-developers.com/showthread.php?t=2083320). I had tried CM10 in the past but it didn't work that well. Thought I'd give it a second go, and, failing that, I'd try out this "lifeless". Sounded like a cool idea.
Background: phone was already rooted, and as I mentioned, i did actually get this CM10 rom to load sucessfully in the past, though I wasn't fully satisfied with the results. i figured this time I'd give it more time to sort out any issues I found. Failing that, I was going to go with the Lifeless ROM (which, I have decided I'm going to do over an unoffical CM10, I love that installer, if I can ever get it to work!). Anyway, here's what happened: I formatted Cache, Data, Davlik, and System just to be safe (same as I did last time). I tried flashing the CM10 ROM along with GApps. I got a hang on boot... just a black screen after the LG screen disappeared (yes, i forgot to do the TeenyBin flashes at the end... more on that later). So, I took this as a sign to try Lifeless, and I installed it successfully. Still a hang on boot... just the LG screen, and I let it go for a good half hour or more. Decided to do a restore of my backup (always do backups!), and... same thing. Even with the stock backup it would hang on boot.
So, I did some digging and I remembered about the TeenyBins! So I flashed the original one, just as I had last time I got CM10 to work. No dice, and even worse, TWRP was changed somehow (I am not sure if it changed versions, or what, but the menus were different), and now for some reason it couldn't even see my backup, even though the file browser in TWRP shows it clearly in the TWRP folder. So, I tried to install CM10, and flashed every one of the three TeenyBins offered on that page. The first one, of course, did nothing. The second, gave me a Google logo instead of LG, and I can actually see the choices on the bootloader screen now (I assume becuase it's based on the Nexus?), but again, nothing. The third (ZVBin) gave me a stuck LG logo for 5 minutes, then a few screen flashes and a kernel panic! Now I'm utterly confused.
EDIT: After the kernel panic, I restarted into recovery, and after the ZVBin flash, i have TWRP 2.4.4.0. It now sees my backup! I'm attempting to run the backup to see if I can at least get my phone back! If this doesn't work, I'll re-flash the Original TeenyBin... and then go from there. I thought about flashing the modems as the link from the CM10 page says, but before I get into changing even MORE, I'll defer to a professional's suggestions, haha.
I've exhausted just about every single option I can think of, I hope someone out there can help me! I would love to just get my phone to boot in some way so I can flash my backup file right back on. Any ideas on what might be causing this?
Thanks!

Sucess! Kinda. With the ZVBin, I was able to restore my phone, and get it to boot. And for some reason, the restore took my /sdcard folder and moved it into sdcard/sdcard0... don't know what that's about.
Any suggestions on what might have happened, and why Lifeless didn't want to work? Does it have soemthing to do with the TeenyBins I had to flash to make CM10 work? What do the TeenyBins replace? Sounds like the boot partition. Is there a way to get a plain one, with just TWRP 2.5 and the LS970 stuff it needs?

Ok, last post for the night, I think... tried to install Lifeless again, and it just fails, right off the bat. it says "Error flashing zip" with no explanation.

VDub2625 said:
Ok, last post for the night, I think... tried to install Lifeless again, and it just fails, right off the bat. it says "Error flashing zip" with no explanation.
Click to expand...
Click to collapse
If it reads error or fail something in that nature it still flashes fine for lifeless ROM, he posted something bout on the first page so go ahead and enjoy

RubbleTea said:
If it reads error or fail something in that nature it still flashes fine for lifeless ROM, he posted something bout on the first page so go ahead and enjoy
Click to expand...
Click to collapse
No, it didn't even get to the flash stage, just when I swipe to flash, it instantly failed.
But, i got it working! Not sure why or how, but I re-downloaded the Lifeless ROM and it worked with a fresh file. The file I had on there originally worked at first, but something must have happened to make it not work afterwards.
However, I do still have the Google boot-up screen and the Bootloader screen shows me menu choices, unlike every other Optimus G. I'm also still on TWRP 2.4.4.0. I hope it's not a problem. And maybe my expirences could help enlighten others,or maybe someone can help explain why exactly I went down this road, haha. I'd love to understand how the bootloader works on this particular phone, because it seems different from my old HTC.
Sorry to seem a little skittish with this post... but I was figuring it out as I was going along, and understood about half of it, haha. Just typing it out I think helped me to figure out what I was doing.

VDub2625 said:
Ok, last post for the night, I think... tried to install Lifeless again, and it just fails, right off the bat. it says "Error flashing zip" with no explanation.
Click to expand...
Click to collapse
I just quoted you here cause your last entry was long anyways here's a flash able twrp 2.5,http://androidforums.com/boost-mobi...ry-twrp-2-5-touch-recovery-cwm-flashable.html just flash in your recovery!

VDub2625 said:
No, it didn't even get to the flash stage, just when I swipe to flash, it instantly failed.
But, i got it working! Not sure why or how, but I re-downloaded the Lifeless ROM and it worked with a fresh file. The file I had on there originally worked at first, but something must have happened to make it not work afterwards.
However, I do still have the Google boot-up screen and the Bootloader screen shows me menu choices, unlike every other Optimus G. I'm also still on TWRP 2.4.4.0. I hope it's not a problem. And maybe my expirences could help enlighten others,or maybe someone can help explain why exactly I went down this road, haha. I'd love to understand how the bootloader works on this particular phone, because it seems different from my old HTC.
Sorry to seem a little skittish with this post... but I was figuring it out as I was going along, and understood about half of it, haha. Just typing it out I think helped me to figure out what I was doing.
Click to expand...
Click to collapse
Well now I know I need to try that second teenybin... I miss having that Google bootloader screen and the menu options I wonder if that is the only way to get it?
Sent from my Lifeless Optimus G