So I just flashed the radio update and i rebooted then it went back to the reboot screen it says its formatting cache at the bottom. Should i wait till thats done or just reboot now. For what its worth I just flashed the new evovled rom R3charged.... its been sitting on this screen for like 40 min now. I can go up/down on the recovery menu thats why i asked should i just try to reboot.
Yeah, you can reboot now. The first time I flashed radios, I did the same thing, stared at that screen for like 20 minutes, wondering....
sha4000 said:
So I just flashed the radio update and i rebooted then it went back to the reboot screen it says its formatting cache at the bottom. Should i wait till thats done or just reboot now. For what its worth I just flashed the new evovled rom R3charged.... its been sitting on this screen for like 40 min now. I can go up/down on the recovery menu thats why i asked should i just try to reboot.
Click to expand...
Click to collapse
HipKat said:
Yeah, you can reboot now. The first time I flashed radios, I did the same thing, stared at that screen for like 20 minutes, wondering....
Click to expand...
Click to collapse
Funny you mention this. AR 2.3 always sits there saying "formatting cache" even though its done when you do a radio flash. I too waited longer than normal and finally just rebooted via AR. All was well. I'm not sure why it does this.
SO, about this radio update, I came into this late, not realizing there were new radios, sorry if I missed a few things.
1, are you guys not rolling PRI back to 1.77 anymore?
2, what's with the Profile update people have reported?? is this across the board, a problem or just random? And I never heard of a Data Profile, Reset. WTH is that?
HipKat said:
Yeah, you can reboot now. The first time I flashed radios, I did the same thing, stared at that screen for like 20 minutes, wondering....
Click to expand...
Click to collapse
thx i got tired of waiting after about an hour and took a chance and rebooted so everything worked out. I was nervous for a lil while watching the formatting cache screen lol
Yeah, when you know that it could brick your phone, it's nerve wracking
Swyped From The Hippest Phone Using XDA Premium
Installed via clockworkmod . . .
I just installed the combo file via clockworkmod recovery. Everything went well, so I thought I'd document my experience to keep anyone from having a heart attack while waiting to find out whether or not they just bricked their phone.
The initial flash took about 2 seconds to complete.
After rebooting, I got the icon of the open box with a yellow arrow coming out and pointing at the Android robot. That lasted for about 60 seconds, then the standard htc EVO 4G splash screen popped up.
That was then followed by a similar box-arrow-Android screen with a progress bar along the bottom, which lasted for about 30 seconds.
Finally, the standard splash screen appeared again, which held for about 60 seconds, then my ROM loaded just fine, although it took about 2 minutes to do so.
Not exactly scientific, but I also documented a speed increase after updating. A speed test from 3 weeks ago had me at 1131/82kbps. Just now, I got 1567/115kbps. I probably should have done the test _before_ updating to have a better comparison, but this is what I've got.
Last time there was a radio update, there was pc36img version, with all 4 updates in it. You could see it loading all three in Hboot. This time, I can only fined the radio itself, so I guess I need to do it in recovery, which freaks me out.
BTW, how is everything? Any noticeable differences?
HipKat said:
Last time there was a radio update, there was pc36img version, with all 4 updates in it. You could see it loading all three in Hboot. This time, I can only fined the radio itself, so I guess I need to do it in recovery, which freaks me out.
BTW, how is everything? Any noticeable differences?
Click to expand...
Click to collapse
Flashed all of the new updates, even though I had the only thing that was needed updating was the radio. Reprovisioned data, and I have to say: the previous radio, I got very little cell standby drain. This new radio, even lower drain.
Signal seems to hold better too. Speeds seem equivalent, have not run a speed test yet.
Related
I want to know if anyone knows what the problem/solution of this is. I have a 0003 Evo, the panel that only supports 3 pt touch, ROM doesnt matter, on the ENG HBOOT for CM, AMON RA 2.3
That sums up my phone, the problem is I'm always stuck at the splash screen for 3-4 minutes when booting up. If im booting to Bootloader or Recovery it's quick, hot reboot never reaches the splash screen so thats whatever, but reboot, or powering down then turning on my evo gets me stuck at the splash screen for quite some time. This is my second evo, and continues to do this despite the ROM I use and despite the splash screen image I use. Whats the problem/fix because so far it's only this specific evo.. I've tried google, everyone is complaining about erasing boot, that isnt my problem since everything else of the phone works just fine.
the panel that only supports 3 pt touch
Click to expand...
Click to collapse
huh?
Anyway, are you wiping data/cache/dalvik everytime you flash a new rom?
fatapia said:
I want to know if anyone knows what the problem/solution of this is. I have a 0003 Evo, the panel that only supports 3 pt touch, ROM doesnt matter, on the ENG HBOOT for CM, AMON RA 2.3
That sums up my phone, the problem is I'm always stuck at the splash screen for 3-4 minutes when booting up. If im booting to Bootloader or Recovery it's quick, hot reboot never reaches the splash screen so thats whatever, but reboot, or powering down then turning on my evo gets me stuck at the splash screen for quite some time. This is my second evo, and continues to do this despite the ROM I use and despite the splash screen image I use. Whats the problem/fix because so far it's only this specific evo.. I've tried google, everyone is complaining about erasing boot, that isnt my problem since everything else of the phone works just fine.
Click to expand...
Click to collapse
What exactly is the problem? It takes a long time to boot? You said it boots up eventually, or I assumed that since you said everything else on the phone works fine.
sitlet said:
huh?
Anyway, are you wiping data/cache/dalvik everytime you flash a new rom?
Click to expand...
Click to collapse
yes, using options built into the recovery and using the format all zip
and i mean the amtel panel, i cant remember the exact name, im currently switching to Salvage GB so im in recovery at the moment but ill tell you the panel. idk if it has anything to do with the problem so i included the info
Heaterz16 said:
What exactly is the problem? It takes a long time to boot? You said it boots up eventually, or I assumed that since you said everything else on the phone works fine.
Click to expand...
Click to collapse
when i boot up, it is stuck on the splash screen for 3-4 minutes, and then boots up normally. I'm wondering if all that time on the splash screen is normal or if i screwed something up since it takes so long to get to the boot animation
mine takes that long
fatapia said:
when i boot up, it is stuck on the splash screen for 3-4 minutes, and then boots up normally. I'm wondering if all that time on the splash screen is normal or if i screwed something up since it takes so long to get to the boot animation
Click to expand...
Click to collapse
That's not abnormal. My phone takes anywhere between 30 seconds and 4 minutes to get past the splash screen. This is especially apparent if you've just flashed something. Don't worry, it's just your phone loading
NewZJ said:
mine takes that long
Click to expand...
Click to collapse
really? I was messing with my friends evo and his screen was there for only 10 seconds, he was unrooted. Is this a side effect of being rooted?
Greenfieldan said:
That's not abnormal. My phone takes anywhere between 30 seconds and 4 minutes to get past the splash screen. This is especially apparent if you've just flashed something. Don't worry, it's just your phone loading
Click to expand...
Click to collapse
really? i've flashed alot of roms on this phone, like daily..
ok was just wondering if i could shorten this time some how, thank you
fatapia said:
really? i've flashed alot of roms on this phone, like daily..
ok was just wondering if i could shorten this time some how, thank you
Click to expand...
Click to collapse
You can by staying on a rom (Of course only to a certain point)
I don't know if I'd say mine stays at the white htc screen for 3-4 min, but close to a good min for sure. Have you actually timed it at 3-4 min?
Once it reaches the boot animation, it's typically ~30 seconds before the UI comes up.
gpz1100 said:
I don't know if I'd say mine stays at the white htc screen for 3-4 min, but close to a good min for sure. Have you actually timed it at 3-4 min?
Once it reaches the boot animation, it's typically ~30 seconds before the UI comes up.
Click to expand...
Click to collapse
yeah I have timed it, came out to 230 on avg with peaks at 3 minutes but generally around 230. I unrooted, then re-rooted my phone to get the latest hboot 2.1 and see if i screwed something up when rooting and after i unrooted i got past the splash screen quickly, and after rooting it still got past quickly. could it have been my hboot? i was on 0.76, gonna flash 0.93 if i cant keep the current hboot and have Salvage GB at the same time
fatapia said:
yeah I have timed it, came out to 230 on avg with peaks at 3 minutes but generally around 230. I unrooted, then re-rooted my phone to get the latest hboot 2.1 and see if i screwed something up when rooting and after i unrooted i got past the splash screen quickly, and after rooting it still got past quickly. could it have been my hboot? i was on 0.76, gonna flash 0.93 if i cant keep the current hboot and have Salvage GB at the same time
Click to expand...
Click to collapse
I suppose it could be the hboot ver, but am not familiar enough with it to say for sure. It's been over a month since I had hboot 2.10, and I don't reboot the phone THAT often to pay much attention to it. FWIW, I've compared mine (hw ver 0003) to a launch day 100% stock evo. Both go through the splash and animation in roughly equal time.
Yours might be delayed because you're running GB?
Now im not sure what the hell is wrong with it that may be causing it but i think the modem may have triggered it because it was running fine all the way up in-till today when i turned on my phone, but however i flashed the modem yesterday around 7 and it was still running fine. I turned off the phone around 11 PM, and turned it on around 7 AM. and it started down from there.
Heres the link http://www.youtube.com/watch?v=cQYZPxsBV1Q
to the Visual Aid so you guys can see whats worng and show you all the FC's it has in begining when phone is turned on.
But mind you after the phone is on and running ill be sitting there and not doing anything and the phone will keep popping up the Google Framework services has stopped working Constantly it happened to me today atleast 30 times if not more.
XxLostSoulxX said:
Now im not sure what the hell is wrong with it that may be causing it but i think the modem may have triggered it because it was running fine all the way up in-till today when i turned on my phone, but however i flashed the modem yesterday around 7 and it was still running fine. I turned off the phone around 11 PM, and turned it on around 7 AM. and it started down from there.
Heres the link http://www.youtube.com/watch?v=cQYZPxsBV1Q
to the Visual Aid so you guys can see whats worng and show you all the FC's it has in begining when phone is turned on.
But mind you after the phone is on and running ill be sitting there and not doing anything and the phone will keep popping up the Google Framework services has stopped working Constantly it happened to me today atleast 30 times if not more.
Click to expand...
Click to collapse
You have corrupted data... Going to have to wipe data and start over... also did u happen to pull the battery out while the phone was on or did u reboot using three button method or 4 finger boot into clockwork?
davidrules7778 said:
You have corrupted data... Going to have to wipe data and start over... also did u happen to pull the battery out while the phone was on or did u reboot using three button method or 4 finger boot into clockwork?
Click to expand...
Click to collapse
I had wiped the data after this happened. i pulled the battery after this thought a hard reboot may have been needed, apparently not. I dont know what 3 or 4 finger boot into clock work is i just hold down the Vol. Down + Camera + Power which im taking is the 3 finger boot?
XxLostSoulxX said:
I had wiped the data after this happened. i pulled the battery after this thought a hard reboot may have been needed, apparently not. I dont know what 3 or 4 finger boot into clock work is i just hold down the Vol. Down + Camera + Power
Click to expand...
Click to collapse
The pulling of the battery is a no-no as it causes corrupt data cause journaling is not on and its like playing russian roulette as you may get lucky and it may not be doing a write
if you pull the battery while its doing a write this is the outcome,
the only time you should have to pull the battery is if an app freezes, or odin hangs or fail...
davidrules7778 said:
The pulling of the battery is a no-no as it causes corrupt data cause journaling is not on and its like playing russian roulette as you may get lucky and it may not be doing a write
if you pull the battery while its doing a write this is the outcome,
the only time you should have to pull the battery is if an app freezes, or odin hangs or fail...
Click to expand...
Click to collapse
Gotch'a So what do i have to do to get back to normal?
Odin.. to stock or whatever or wipe data 3 times also cache 3 time in clockwork then teflash the Tom sometimes that works
Sent from my Epic 4.0.0g bonsai plant
EVO 4G, works for ~4 minutes, then the screen shuts off, it vibrates five times, and a green light flashes. Only way to fix it to remove battery.
Last night I was flashing Deck's Alpha1 and a camera mod via TWRP 2.0. Flashed Decks, flashed GAPPS, flashed camera fix from MongooseHelix. Delected reboot system and the phone rebooted into recovery. Odd.
Reboot system again it then went to a black screen / green light flashing (it probably shoot 5 times also, but I did not notice)
Boot, run ICS setup, after a bit it starts crashing and I notice all my old stuff was there even though I did a factory reset/clear caches/data. Odd.
Reboot, works for a minute then acts really strange, I decide I've got a bad flash and go to reboot into recovery. Recovery doesn't load, phone shuts off...
Try again, reboot into bootloader and notice that I am suddenly S-ON (rooted via unrevoked back in 2010). Rut roh.
Slapped a froyo PC36IMG.zip I found on it, booted, no good.
Found a Gingerbread PC36IMG, seemed to work, worked for 5 minutes and then black screen/5 shakes, green light.
Grabbed a RUU from therootofallevo, it said I needed to get the proper version when it was working on the phone.
Have tried getting it up and running long enough to apply unrevoked, but it doesn't seem to recognize the USB for ADB, only as QualComm something or other.
I sort of think the phone is dead. Had some electrical issues my APC UPS did not protect me from and ended up with the 4G being funky. But not sure if there is any step I could possibly do to revive the thing.
As a note, the EVO is not in service, not protected by TEP, so I can do pretty much anything to it and won't cry... I used it for a lot of other things (ip phone, HDMI, etc) and would lie to get it working but will accept it's dead Jim
your problem maybe due to twrp. check out the thread http://forum.xda-developers.com/showthread.php?t=1400645
dzee206 said:
your problem maybe due to twrp. check out the thread http://forum.xda-developers.com/showthread.php?t=1400645
Click to expand...
Click to collapse
oh frak me....
that is it
I am EVOless now
It crashed?
Sent from my PC36100 using xda premium
Sounds like the twrp 2 death flash s-on that's hit a few ppl now
Sent from my iCS'd out EViL4G, soaking in a bowl of Ramen Noodles
Hey, this is my first post so let me first say sorry if I'm doing something wrong here and thanks a ton to anyone who can help me out in some way...
So long story short - I just looked down at my phone and it was on the white "Evo 4G" screen, so I thought it must have just restarted for some reason (which has never happened, but I usually try to remain optimistic) and I went about my business...about 10/15 minutes later it was still on the white screen, so I pulled the battery and left it out for a minute and then tried turning it on again. No luck-right back being stuck at the white screen. So I pulled the battery again and waited about a half hour before trying with my other battery, which is definitely fully charged and cool, and it is still sticking at the white screen. I don't know what the heck is going on. Anyway, I have an Evo 4G running Warm 2.2 with some netarchy kernel of some sort (one that is suggested on his thread) if that even matters. I can get into recovery, but that's actually another set of issues in itself so if this can be solved without doing a restore I'd prefer that. Okay, sorry to give too many details. Thanks again to anyone who has any thoughts!
this is why you make nandroid backups
If you do happen to have a recent nandroid backup you might wanna restore to that, otherwise the only other other option I can suggest which may still not work but it's worth a try...
recovery > wipe cache > wipe dalvich cache > flash the same warm 2.2 zip you are running and do not flash the custom kernel just yet, see it that gets you to boot
colindelong said:
Hey, this is my first post so let me first say sorry if I'm doing something wrong here and thanks a ton to anyone who can help me out in some way...
So long story short - I just looked down at my phone and it was on the white "Evo 4G" screen, so I thought it must have just restarted for some reason (which has never happened, but I usually try to remain optimistic) and I went about my business...about 10/15 minutes later it was still on the white screen, so I pulled the battery and left it out for a minute and then tried turning it on again. No luck-right back being stuck at the white screen. So I pulled the battery again and waited about a half hour before trying with my other battery, which is definitely fully charged and cool, and it is still sticking at the white screen. I don't know what the heck is going on. Anyway, I have an Evo 4G running Warm 2.2 with some netarchy kernel of some sort (one that is suggested on his thread) if that even matters. I can get into recovery, but that's actually another set of issues in itself so if this can be solved without doing a restore I'd prefer that. Okay, sorry to give too many details. Thanks again to anyone who has any thoughts!
Click to expand...
Click to collapse
I would suggest wiping cache and dalvik cache and trying to boot up the phone again. I have ran into this a few times using the fastboot option, otherwise never had the problem.
Hey guys, I've been having a really weird issue for a couple of days now. For your better understanding I'll list the things that I did with my d855 (Including some stupid ones)
1. I was on a cm 13 nightly rom, I was getting pretty bored so I decided to try out the fulmics 4.2 . So, I did. I flashed it without any hiccups. Everything seemed to be going fairly well. (I did make a TWRP backup and i also checked md5 of the zip file. It matched out)
2. I installed all of my apps that i use, Set up my wallpapers, nova, etc. I used it for a whole day and i noticed that the sot improved quite a bit from cm 13.
3. I'm in my bed, obviously not sleeping, you know how we do. And an incredibly stupid idea came to my mind. I thought "Hey! It's 4'o clock in the morning and i have school tomorrow, BUT WHO GIVES TWO ****S?! why not try out the lg g4 camera app ?!? Now, I had tried it before a long time ago, The camera didn't work, But the phone definitely did. So I wasn't paying too much attention on what the thread said about which version of android it was for. And just like a complete moron i downloaded the thing and proceeded to place the apk and 'libs' folder on my phone. I did give them proper permissions.
4. After that I went ahead and rebooted my phone. It booted just fine. I tapped on the camera app and it gave me an error. So i rebooted again, same as last time it booted up just fine but the camera didnt seem to work. Then suddenly it just shut down and then the lg logo flashed. It booted to the homescreen just fine. Then it turned off again and rebooted again. This loop started to go on and on forever.
5. So I decided to boot into twrp and wipe my art/dalvik cache and normal cache. Then i pressed on reboot. This time the phone didnt turn off, it optimized all of my apps. It took a while but i was on my homescreen and it didnt turn off. So I went ahead and opened up root explorer, located to where i pasted the camera, deleted the libs folder and the apk and also renamed my original camera app from .bak to .apk . Then I rebooted again, and it started the weird looping thing once again.
6. I realized that it boots up just fine if it's plugged in. But it seemed to turn off after 5 mins or so even when plugged in. I thought I messed up my rom or something so i decided to check by entering into recovery. But the result was the same. It just turns off. So since it was turning off even when i was in recovery i thought it was a faulty battery.
7. So i busted out my ZTE pocket wifi router and proceeded to take its battery and hold it up against my d855's battery pins with my finger. (Probably not safe) And the phone seemed to work just fine. I could use it for days without any issues. So at that point im like 110 percent sure its a faulty battery. Fair enough.
8. But, just to be certain i thought lets try doing a factory reset and flash the fullmics again. Result = Wank.
Then I wiped the cache again. Result = Wank. Then i decided to restore to the backup i made earlier that day. Result = An oreo to be given to the one with the correct guess.
9. At this point i wasn't 110 percent sure that it was a faulty battery. I KNEW it was a faulty battery. I was feeling it in my left testicle. So I decide to finally sleep cuz you know, gotta get some sleep, got a big day ahead of me tomorrow. Cuz I dont have my phone. So, I prepare myself and go to sleep.
10. The next day I decide to give it one last shot. I was thinking about wiping it clean and restoring to the backup again.
11. This is where the interesting thing happens. Bear in mind, I am NOT plugged in. Im on my G3's battery. I hold down the volume down and power button. The lg logo shows up. I let go of the buttons. I press them again. The white factory reset screen shows up. Now, I left my phone on that screen for legit 20 mins ladies and gentlemen and it didnt turn off once. But as soon as i click yes for twrp to launch the phone turns off before the twrp logo can show up. I tried the same thing with the ZTE battery as well, and it worked just fine. Only this time it actually booted to twrp. And it booted into the system as well.
Now, wtf is this? Wouldn't the phone turn off in the factory reset screen if it was faulty? And if the battery isn't faulty, then why does it work with a different battery but not with the lg one?
Now, My question to you guys, WHAT SORCERY IS THIS?
Help me out people. Expert help needed. TIA
*sigh*
It's a faulty battery mate. The phone stayed in the factory reset screen because the battery usage was basically insignificant. When you tried to go to recovery mode, the phone used more battery and boom, dead phone Happened to me too, new battery solved it.