Q: boot loop after F.D.R. on custom rom - myTouch 4G Q&A, Help & Troubleshooting

okay so yes...im a noob, or atleast i consider myself one. heres my problem, i jumped into rooting and flashing head first, without researching EVERYTHING, ENTIRELY, so im at fault, i know this guys.
so heres the just of it, i have the mt4g aka htc glacier. i wanted to root, and flash a custom rom. i have a thing for sense 3.0 so i flashed virtuous fusion, now i never checked or learned how to figure out if i have a bad emmc? i through caution to the wind and here i am with no phone.
okay so its installed everythings good no glitches running smooth. my girl downloads mad bull**** into the phone and it starts running SLOW, real slow. i think hmm, factory data reset? earse everything yes i know this is unrevesable. phone goes black. remove battery reinstall, turn on, myotuch 4g then htc sense boot screen, then boot loop, then boot loop, then blakc screen unresponsive until battery pull.
cleared cached partition, wiped dalvik cache tried reinstalling viruous fusion from zip, same problem, not sure where i saved my nadroid backup unable to find it
so basicly guys, without gettin chewed out, am i a total ****ing moron? and is there hope....
also i saw a simalr thread unanswered there was a suggerstion to instal some file with a random jumble of letters and numbers as the name, however idk how to do so without being able to access my sd card with the phone i dont have a spare phone or way to put sd card in laptop please help me someone

SOLVED, not sure how i fixed it but i think its because, i first deleted everything i could form clockwork, then went to advanced deleted cache system and something else reflashed now its working...no complaints, however i read on another forum that virtuous fusion is known for brick devices upon factory data resets

Virtuous Fusion is a very outdated ROM.
Use Virtuous Unity.

joeyydaprofitt said:
okay so yes...im a noob, or atleast i consider myself one. heres my problem, i jumped into rooting and flashing head first, without researching EVERYTHING, ENTIRELY, so im at fault, i know this guys.
so heres the just of it, i have the mt4g aka htc glacier. i wanted to root, and flash a custom rom. i have a thing for sense 3.0 so i flashed virtuous fusion, now i never checked or learned how to figure out if i have a bad emmc? i through caution to the wind and here i am with no phone.
okay so its installed everythings good no glitches running smooth. my girl downloads mad bull**** into the phone and it starts running SLOW, real slow. i think hmm, factory data reset? earse everything yes i know this is unrevesable. phone goes black. remove battery reinstall, turn on, myotuch 4g then htc sense boot screen, then boot loop, then boot loop, then blakc screen unresponsive until battery pull.
cleared cached partition, wiped dalvik cache tried reinstalling viruous fusion from zip, same problem, not sure where i saved my nadroid backup unable to find it
so basicly guys, without gettin chewed out, am i a total ****ing moron? and is there hope....
also i saw a simalr thread unanswered there was a suggerstion to instal some file with a random jumble of letters and numbers as the name, however idk how to do so without being able to access my sd card with the phone i dont have a spare phone or way to put sd card in laptop please help me someone
Click to expand...
Click to collapse
well there's a lesson learned...
never EVER do a factory reset within a ROM... lol
btw, when you went to recovery, did it show any errors?
like "E:/ Can't find ..."?

Related

Boot infinite loop

I tried to install expresso on DC 2.07 and the zip file flashed, then when I rebooted it just keeps looping without getting to the OS. I suppose I screwed something up, so I was going to nandroid back, but now the phone won't let me get back into the recovery console. Anybody have any tips on how to get the recovery console back up?
schnoz said:
I tried to install expresso on DC 2.07 and the zip file flashed, then when I rebooted it just keeps looping without getting to the OS. I suppose I screwed something up, so I was going to nandroid back, but now the phone won't let me get back into the recovery console. Anybody have any tips on how to get the recovery console back up?
Click to expand...
Click to collapse
You pulled the battery and put it back in, then held just the home button and the power key?
if the above doesnt do it
Pull the battery put it back in power on hold down home and back. clear the data.
I am currently running the newest version of DC, hours after the update I look down the phone is continuously restarting never making it past the sprint screen.
I go into recovery it says it cant mount to the SD card. so as of right now my phone is dead in the water.
I purchased a new SD card and im loading DC onto it to do a flash. Ill let you know If I get the same thing, mine didnt do it right away but it was fine before the update this morning... oh and Damage whats up with no Wireless Tether??
Mine is doing the infinite loop also. I had everything working and did a nandroid backup. After I rebooted, it started to loop, the nandroid loops also, I wiped the ext on sd, and still get the loop.
RPerry435 said:
I am currently running the newest version of DC, hours after the update I look down the phone is continuously restarting never making it past the sprint screen.
I go into recovery it says it cant mount to the SD card. so as of right now my phone is dead in the water.
I purchased a new SD card and im loading DC onto it to do a flash. Ill let you know If I get the same thing, mine didnt do it right away but it was fine before the update this morning... oh and Damage whats up with no Wireless Tether??
Click to expand...
Click to collapse
dwertz said:
Mine is doing the infinite loop also. I had everything working and did a nandroid backup. After I rebooted, it started to loop, the nandroid loops also, I wiped the ext on sd, and still get the loop.
Click to expand...
Click to collapse
So you guys can get into Nandoird, you wipe data, dalvik and ext partition, reinstalled ROM and you still get a boot loop?
Yes exactly..
I ruled my phone bricked earlier for no reason at all. phone was fine, i did the update to 2.7.2 and hour or two later it keeps looping..
I tried New SD card,erase data, davlik, re partitioned, downloaded a fresh version off the net just incase my copy was corrupt and still looped
I took it to the sprint store before they closed and got a new phone.
I Would seriously look into this obviously I wasnt the only one
danknee said:
So you guys can get into Nandoird, you wipe data, dalvik and ext partition, reinstalled ROM and you still get a boot loop?
Click to expand...
Click to collapse
Yes TrevE says it may have something to do with /data/private-app/
http://forum.xda-developers.com/showpost.php?p=6174954&postcount=1951
All I know, it boots like normal, I install exchange, hotmail. some market apps. titanium apps, paid and free, then when I went to reboot I backed up in nandroid, then when it actually booted, it was stuck in the HTC quietly brilliant and the start up of the sprint logo and keep looping. TreVe suggested adb logcat but I can not get that far to log the error. He said he logged it as the private-app
Oh I also tried to delete sd ext, davik, remove sdcard, run from the nandroid back up and everyway made the loop. I think TrevE is onto something though. I have one app that I install that is a private app that is from Titanium that may cause this.
Oh and btw, if I wipe the rom and reboot it boots up normally so i think it has something to do with something that is installed. Is anyone else using titanium backup to restore a paid app? Installing a paid app from the sdcard??
RPerry435 said:
Yes exactly..
I ruled my phone bricked earlier for no reason at all. phone was fine, i did the update to 2.7.2 and hour or two later it keeps looping..
I tried New SD card,erase data, davlik, re partitioned, downloaded a fresh version off the net just incase my copy was corrupt and still looped
I took it to the sprint store before they closed and got a new phone.
I Would seriously look into this obviously I wasnt the only one
Click to expand...
Click to collapse
Not much left to look into since the phone is gone. I would have restored to the unrooted 1.56 ruu to test, but I guess a new phone is good too.
Try flashing a different ROM as in different frameworks. Sometimes going back to a 1.5 ROM can fix weird issues like that.
I went with fresh's Rom this time instead of dc. Everything has been good so far.
I had a problem with a loop with both DC and Fresh. It all began after I set up my Exchange email. I am using Touchdown and I haven't had any issues.
Keep on mind I never added or used any private apps. This happened after the update through the loader. I changed nothing and have been using the same apps for months.
I kept having these issues after 2.07.2 even after a full wipe and reset still no dice. So I just went to Fresh.

On a subject totally unrelated to anything else going on:

Damn near burst a vessel earlier, doods. I had downloaded the newest darchdroid, and was looking forward to some oc'd, jit-enabled, vanilla goodness. I booted into recovery, wiped everything, and tried to install. Ut oh! Got a bad download. No es bueno. But, imma careful sob, so I have like 4 nandroids sitting on my SD....2 from flipz' latest betas, 1 from the original fresh toast, and one from dc 2.0.8. And it was a damned good thing, too! The backups off the newest would NOT boot. They kept looping. I tried rewiping, nothing. No good. Finally, I tried one of the other nandroids, and It worked first try. Because I'm a curious person, I then immediately booted to recovery and tried my most recent nandroid (the first one that bootlooped). This time it worked like a charm. Consider this evidence that having more than one nandroid in storage is never a bad idea. Anyone with a clue about what might have happened, and why the nandroid wouldn't work...until suddenly it did?
dood, Nandroids are for pansies.
Maybe it has a bad temper, too.
-------------------------------------
Sent from your mom!
@Kcarpenter- Well, paint me pink and stick me in a pot! (i was gonna make a joke about your wife and my root, but in this current climate, it prolly would have gotten me banned for being off topic in my own thread)
@jerry- you're prolly right. I know it has my sense of humor, cause it keeps effing with me when I'm drunk....
Same experience
I tried to make a nand of darch and when it failed I tried to restore my last nand of my last rom and almost "oops_I_crapped_my_pants" when it failed too
Fortunately an older nand worked
So I just had to try darchdroid again and its nanding just fine . I probably wont stick with it fo eva but it is fast as crap after eating liquid dish soap.
btw, did you happen to see the very last stock wallpaper in darchdroid?? HOMINA HOMINA HOMINA. So hot, want to touch the hiney.. awwooooooo
phenicks said:
Same experience
I tried to make a nand of darch and when it failed I tried to restore my last nand of my last rom and almost "oops_I_crapped_my_pants" when it failed too
Fortunately an older nand worked
So I just had to try darchdroid again and its nanding just fine . I probably wont stick with it fo eva but it is fast as crap after eating liquid dish soap.
btw, did you happen to see the very last stock wallpaper in darchdroid?? HOMINA HOMINA HOMINA. So hot, want to touch the hiney.. awwooooooo
Click to expand...
Click to collapse
Na. I had a totally bad download. It never even finished installing. I'll try it again this afternoon, when I'm near a computer.
I am not sure if this will help, but I had a loop problem and I noticed it started when I installed an app. This was in my nandroid back up. If you boot, it will go into loop.
Through adb start removing programs in the /system/app/. I ended up removing the program (apk and/or odex) and it stopped the loop without rebooting. Not sure why it did this.
Once you find the program that may cause this, restore your nandroid and only remove that apk or odex.
Just try it and see if this works.
you should wipe and clear data before nandroiding back. probably why you had a boot loop. With recovery theres no reason why you cant take 5 seconds and wipe everything before nandroid. If you did do a wipe and clear data before hand then my sincere apologies.
Yeah, I rewiped MULTIPLE times (each time I tried to nandroid recover, so, like, 6 times or so). Thanks, though.

Endless Rebooting, about to smash phone to bits

Alright, this issue has seriously driven me insane over the last few days, and today it's gotten to the point where I'm going to do something I'll regret if somebody can't help me out. As you can tell, I'm pretty desperate.
Using Fresh 3.5.0.1, I've encountered more reboots than I can count. Whether it's checking an email or playing Asphalt, the phone frequently decides it doesn't want to cooperate and restarts itself. I decided to try to get rid of the reboots for good today with a complete wipe and new rom.
First, I made a nandroid backup, followed by a data/system wipe and cache/dalvik cache wipe. Afterward, I flashed the ZenDroid 1.1.0 kernel in case that was the issue. I then proceeded to flash CyanogenMod 7 RC1 with gapps.
That worked for all of three minutes, and then it got even worse. The phone started restarted itself when I wasn't even doing anything, up to the point where it would restart on the CM7 boot animation. I took my rage out on a nearby pillow and decided to try something else.
I downloaded the final release MIUI rom and used Calkulin's format all to wipe my phone as instructed. This time around I flashed Savage-Kernel 1.6 along with MIUI. Lo and behold, after rebooting I was finally able to swipe through the home screens again.
And then I wasn't. It started rebooting on the boot animation again. At the moment it's even worse, rebooting three seconds into the damned splash screen. I've tried keeping the battery pulled for half an hour with the HTC battery and two after market batteries. I wiped the ext partition on the micro sd card. I even physically removed the card itself. This effing phone is still rebooting on the splash screen.
I'm at the end of my wits. All I want is for my Evo to WORK, without any constant reboots or force closes that make it utterly unusable outside. If anyone could help me out with this issue, I'd be extraordinarily grateful.
Mecha2142 said:
Alright, this issue has seriously driven me insane over the last few days, and today it's gotten to the point where I'm going to do something I'll regret if somebody can't help me out. As you can tell, I'm pretty desperate.
Using Fresh 3.5.0.1, I've encountered more reboots than I can count. Whether it's checking an email or playing Asphalt, the phone frequently decides it doesn't want to cooperate and restarts itself. I decided to try to get rid of the reboots for good today with a complete wipe and new rom.
First, I made a nandroid backup, followed by a data/system wipe and cache/dalvik cache wipe. Afterward, I flashed the ZenDroid 1.1.0 kernel in case that was the issue. I then proceeded to flash CyanogenMod 7 RC1 with gapps.
That worked for all of three minutes, and then it got even worse. The phone started restarted itself when I wasn't even doing anything, up to the point where it would restart on the CM7 boot animation. I took my rage out on a nearby pillow and decided to try something else.
I downloaded the final release MIUI rom and used Calkulin's format all to wipe my phone as instructed. This time around I flashed Savage-Kernel 1.6 along with MIUI. Lo and behold, after rebooting I was finally able to swipe through the home screens again.
And then I wasn't. It started rebooting on the boot animation again. At the moment it's even worse, rebooting three seconds into the damned splash screen. I've tried keeping the battery pulled for half an hour with the HTC battery and two after market batteries. I wiped the ext partition on the micro sd card. I even physically removed the card itself. This effing phone is still rebooting on the splash screen.
I'm at the end of my wits. All I want is for my Evo to WORK, without any constant reboots or force closes that make it utterly unusable outside. If anyone could help me out with this issue, I'd be extraordinarily grateful.
Click to expand...
Click to collapse
hmm...
i don't know what kernel fresh comes with, but both of the other kernels are more aggressive ones, and i would guess your phone doesn't like them. i would try this:
Wipe twice using calk, wipe again using recovery, flash mikfroyo or stock rooted (stock kernel). If you still get reboots... unroot and take your phone back in because its a hardware problem.
I had this problem. Drove me insane. Ultimately just unrooted and got a new one from sprint. Not one reboot since I got the new one.
Sent from my PC36100 using XDA App
Well I'm still super new to the whole flashing of the ROM's. But from what you have explained the only thing I can think of is that you missed a step when you rooted your phone. Because of this that is why your phone keeps brick. You should go and check out HTC EVO Hacks (go Google it) and the guy who runs the site made a sweet video & write-up on how to root your phone. Just re-do everything and follow directions, then when your done just flash Kings Unleashed. And when you check out the HTC EVO hacks root page look for the link to the XDA root forum which has more info on how to root your HTC the proper way.
Sent from my PC36100 using XDA App
aimbdd said:
hmm...
Wipe twice using calk, wipe again using recovery, flash mikfroyo or stock rooted (stock kernel). If you still get reboots... unroot and take your phone back in because its a hardware problem.
Click to expand...
Click to collapse
Yeah, I guess I should try the stock rooted rom. If I'm only able to use that instead of any other custom rom, though, I'm going to lose it. There's something inherently frustrating about a device refusing to work for no apparent reason.
chickut123 said:
I had this problem. Drove me insane. Ultimately just unrooted and got a new one from sprint. Not one reboot since I got the new one.
Click to expand...
Click to collapse
I'm sort of hoping I won't have to do that, considering I'll likely get a refurbished unit.
Fredrow425 said:
But from what you have explained the only thing I can think of is that you missed a step when you rooted your phone. Because of this that is why your phone keeps brick. You should go and check out HTC EVO Hacks (go Google it) and the guy who runs the site made a sweet video & write-up on how to root your phone. Just re-do everything and follow directions, then when your done just flash Kings Unleashed. And when you check out the HTC EVO hacks root page look for the link to the XDA root forum which has more info on how to root your HTC the proper way.
Click to expand...
Click to collapse
I'm pretty sure that isn't the case at all. If there was an issue with the way I rooted my phone, it would have been present eight months ago when I bought it. This rebooting issue is relatively new, and it isn't bricked. I appreciate the advice, though.
It could be just a defective phone - memory isn't immortal or impervious to defects.
I'd downgrade to a Sprint ROM, and keep it stock and see how that works. You have to rule out bad hardware first, and that's the only way to do it.
I agree on all of your guys suggestions but one thing i noticed was that he said he wiped data then dalvic cache then he said he flashed the kernel then the rom. Maybe he should try and rewipe everything with calk format all then flash the rom and reboot. Then go back into recovery and flash your new kernel then reboot again and see whats up from there.
Have you tried repartitioning your SD card and formatting? I was getting random reboots on every single rom I tried, and every single kernel. Turns out my partitions somehow got messed up on my SD card and that was causing it randomly. Now I have no reboots.
akrod2as said:
Have you tried repartitioning your SD card and formatting? I was getting random reboots on every single rom I tried, and every single kernel. Turns out my partitions somehow got messed up on my SD card and that was causing it randomly. Now I have no reboots.
Click to expand...
Click to collapse
Yes, I first formatted the sd card in Windows and then partitioning it on the phone's recovery. Still no luck.
Yeah... Sprint rom or if you go through with the unrooting process (I forgot how...) then you can figure out if it is hardware.
But yeah, endless reboots are frustrating.
If Sprint rom is giving you troubles, then just return it and get a new one. It's gotta be hardware then.
Also you could try running stock rooted without any downloaded market apps. Just run what came with the phone.
You can also try stock rooted eclair 2.1
Mine started the reboot bs after the december update. Mine seems to reboot when I use it heavily even though I'm not overclocked (heats up). Before the 2.2 update, it was very fussy being outside during the summer. I would like to exchange mine for another, even though I don't use it anymore. It would be nice to have a fully functioning backup. My gf's daughter wants the evo very much. Even if I would do that, which I wouldn't, I wouldn't let someone use a possibly unstable phone. If an emergency happened, and the phone started it's rebooting bs, it would be very bad to not be able to use the phone when you need it the most.
I am guessing I would have to reactivate the evo, run it for a month or so, unroot and lock it, then take it to a service center and see if I can make it start rebooting like crazy. Maybe I will get lucky and they would give me another one. I don't care too much if it is a refurb as long as it is in good shape and works good.
Try removing the SD card and booting.
Sent from my PC36100 using XDA App
rebooting
I had this same problem with my evo. Sometimes it would be ok, but then others it wouldnt stop doing it, didnt matter what I did. It could be sitting by itself and I would hear it rebooting. Drove me mad!!!
My first evo was awesome, it was a hardware ver 3. My camera lens cracked and the gave me a refurb, hardware version 2. This is when my reboots started happening.
After 3 batteries from Sprint and two more refurbs I finally blew in front of a store full of customers telling them that either give me a NEW evo, hardware version 3 like I originally had with no problems or it was going against their wall.
I havent had one problem since.
I wasnt rooted yet so cant comment along those lines but if you take it back to stock and it still does it I recommend throwing it at one of Sprints walls. No need to do any drywall patching at your place LOL.
I hope you get it resolved as I can feel your pain!
It may not be hardware. Did you restore any apps using any back up app (Titanium Backup) after flashing the AOSP roms? If so, make sure you did NOT restore any system apps or data. This is especially important when you go from Sense to AOSP.
The test is what everyone is suggesting. Flash back to Sprint rom and see what happens.
Also, you need to flash the kernel after flashing the rom, otherwise you'll just get the kernel packaged with the rom. I usually reboot and art least try the default kernel unless I know that my phone hates it.
bigmoogle said:
It may not be hardware. Did you restore any apps using any back up app (Titanium Backup) after flashing the AOSP roms? If so, make sure you did NOT restore any system apps or data. This is especially important when you go from Sense to AOSP.
The test is what everyone is suggesting. Flash back to Sprint rom and see what happens.
Also, you need to flash the kernel after flashing the rom, otherwise you'll just get the kernel packaged with the rom. I usually reboot and art least try the default kernel unless I know that my phone hates it.
Click to expand...
Click to collapse
No, I haven't even been able to get to the stage of installing any apps before the rebooting cycle starts again. I tried installing the stock Sprint rom this morning with the stock radios and kernel and it was stable for about five minutes. It's back to rebooting again, though.
Do you guys think it's time to unroot and go to the Sprint store for an exchange?
Mecha2142 said:
No, I haven't even been able to get to the stage of installing any apps before the rebooting cycle starts again. I tried installing the stock Sprint rom this morning with the stock radios and kernel and it was stable for about five minutes. It's back to rebooting again, though.
Do you guys think it's time to unroot and go to the Sprint store for an exchange?
Click to expand...
Click to collapse
If it was me, I would take it back. I just downloaded the newest ruu and will flash it later tonight. The only thing I'm worrying about is they won't be able to reproduce the problem. I really have to be multitasking a lot and pushing the phone hard. Actually the last time it had rebooting fits was with wireless tether running. The back of the phone was warm. I put it in front of the ac vent in the car for a minute or two and that seemed to help it stop rebooting.
herbthehammer said:
If it was me, I would take it back. I just downloaded the newest ruu and will flash it later tonight. The only thing I'm worrying about is they won't be able to reproduce the problem. I really have to be multitasking a lot and pushing the phone hard. Actually the last time it had rebooting fits was with wireless tether running. The back of the phone was warm. I put it in front of the ac vent in the car for a minute or two and that seemed to help it stop rebooting.
Click to expand...
Click to collapse
Well, it looks like I'll be taking it to the store after all. I just finished unrooting my phone with the RUU, so it's as if I had never touched the software. Lo and behold, the damned thing still rebooted a minute into using the phone.
I guess that in some sick way, I can consider myself more 'fortunate' than you, seeing as how my phone doesn't even need to be used in order to begin rebooting. It's ridiculous that I have to part with my Evo because of this bs.
Mecha2142 said:
Well, it looks like I'll be taking it to the store after all. I just finished unrooting my phone with the RUU, so it's as if I had never touched the software. Lo and behold, the damned thing still rebooted a minute into using the phone.
I guess that in some sick way, I can consider myself more 'fortunate' than you, seeing as how my phone doesn't even need to be used in order to begin rebooting. It's ridiculous that I have to part with my Evo because of this bs.
Click to expand...
Click to collapse
Did you even try removing the sd card and booting the phone?
Same thing happend with my old evo it started after i install one of the first cm safe roms not nightlies not saying tyat was the cause, i tried evverything wiping unrooting botting without sd, ive been on android sice g1 and i tried everything nothing worked, ended up going to sprint and getting another refurnished it was prolly hardware issue maybe cpu overheating or something, anyways not sure why ppl are so scared of refurnished phones i believe they do a lot more tests on those phone than retail ones lol
akrod2as said:
Did you even try removing the sd card and booting the phone?
Click to expand...
Click to collapse
Yes. I've already said I tried booting the phone without the sd card several times now without success.

[Q] MyTouch 4g: Multiple problems... PLEASE help.

Okay, I've searched and searched and no one seems to have the specific problem that I'm having with my phone, so I'm taking to the forums myself. I've been rooting since the G1, I know how to adb push things, I have used google and multiple forums to try to fix this problem. So here goes, anyone that can help I thank you in advance.
1-My phone, like some other MT4G users, reboots itself each time it's plugged in. Initially I thought this was because I was using a Kindle cord to plug it into the pc, so I bought an MT4G usb cable from tmobile, and still it boot loops (just the first white screen for maybe 4 seconds, then black then again and again). The only way to charge it is to let it start boot looping, take the battery out, turn it on, and if I'm lucky enough that it begins to boot up correctly I plug it in mid boot. If I wait til it's fulled loaded it just starts rebooting again.
2-It will not at all from any angle go into Recovery mode. If I try to go to recovery from Rom Manager, or from the screen you get when holding power and lower volume key or by flashing a rom through Rom Manager, it just boot loops just like mentioned above, until I pull the battery for a while (it is currently sitting next to me with the battery out) and then put it back in.
3-If by chance it's on, and plugged into the computer, it is not at all recognized. Ever. While it's booting up my computer finds something, but doesn't know what it is, and doesn't allow me to view any folders on the SD card. Yes I've installed the HTC drivers file. I've adb'ed things to this phone before, now it says device not found. I don't know when it stopped being recognized...
4-I've even tried to fastboot something over to it, but to no avail, still not found.
If I try to do a factory reset, it boot loops. If I sneeze it boot loops.... I don't know what to do, and if I trade it in under warranty, I have to reset it to stock rom, or they're going to charge me for a new phone. Any ideas!?
I have Cyanogen mod 7 on here.
have you tried a fastboot wipe? or have you tried to reboot to recovery from adb?
First, I don't trust using the actual ROM Manager app to do the flashing/installing.
Since you've been flashing since the G1 days why not use Clockwork Recovery? Just go into recovery and do the necessary wipes.
So I suggest to do a complete full wipe in Clockwork, meaning wipe data, cache, and dalvik cache. Install the newest CM nightly (Which is working wonderfully BTW) and see if your problems still persists.
Edit: I didn't realize you tried to enter recovery, oops. But yeah try what the buy above me said. Try re-installing the latest CWM recovery, if that still fails then try heading into there via ADB.
mackster248 said:
First, I don't trust using the actual ROM Manager app to do the flashing/installing.
Since you've been flashing since the G1 days why not use Clockwork Recovery? Just go into recovery and do the necessary wipes.
So I suggest to do a complete full wipe in Clockwork, meaning wipe data, cache, and dalvik cache. Install the newest CM nightly (Which is working wonderfully BTW) and see if your problems still persists.
Click to expand...
Click to collapse
I second that, flashing ROMs from ROM Manager a terrible idea.
Well...if all else fails and if you are really thinking about returning it and still under warranty...few seconds in the microwave method should work just fine. They wont be able to see that its rooted if the phone wouldn't turn on, would they???
glimmer of hope...
So by the grace of god I did get it flashed back to unrooted, stock 2.2 by putting it as pd15img.zip on my sd card and going into bootloader. Once that was done I thought I would be out of the woods... I even plugged it in last night and no boot loop!! but this morning I unpllugged it (and I'm using a tmobile cable for the phone attached to my pc) and here it sits, next to me again with the battery out of it because everytime I try to turn it on (for over 40 minutes now) it boot loops to that stupid white screen (that is honestly driving me insane at this point). I know that it isn't rooted (because I dl'ed rom manager and it won't let me do anything without being rooted) so do we think that I'm safe to go to the store today to request a new one be sent? Thoughts? And thanks for the help thus far!
yeah I would send that back
Bad emmc chip? I'm sorry man, that's a terrible story.
Sent from my HTC Glacier using XDA App

[Q] Stuck at Samsung Screen

Can someone please help me? I have a Samsung focus that was recently acting up.. Games wouldn't open etc.. so I decided to reset it.. After I reset it.. Its now stuck at the Samsung logo after resetting.. I am guessing that I need to reflash it.. If so, I need to make sure my battery isn't dead. Does the Phone charge while showing the Samsung boot logo?? Help Please..
I dont have a focus but with a Google search looks bout the same as I wud do on my epic ..found this if it helps http://forums.androidcentral.com/dr...ks/130642-help-stuck-samsung-boot-screen.html
Alright, heres what I did.1. Rebooted in*CWM2. Wiped data/factory reset3. Wiped cache partition4. Wiped dalvik cacheAt this point I couldn't reflash because I forgot I couldn't access my SD card, I kept getting the "e:can't mount /sdcard" message whenver I went to install zip from sd card.5. Took off the back and pooped out the SD card and put it right back in. Seemed to work6. Flashed 2.07. Flashed kejar's sd card fix8. Rebooted through*CWMPhone starts up, do all the set up stuff, but still can't access my sd card or anything. Booted back into*CWM*just to see and was getting the "e:can't mount /sdcard" error again and couldnt reflash anything, so back to step 1.Here's a list of other things I have done since the original crap out a few days ago that might be affecting this.*1. Yesterday I tried reflashing 2.0 and it seemed to be boot looping again. So I just wiped data and cache partition and flashed 1.9.1 that I had on my SD card. Was having the same problems so that was the only time I tried it. Not sure if built in kernels might affect anything or whatever.2. After it seemed like I had a stable 2.0 again last night. I flashed blue*CWM*because I've had yellow this whole time. I also flashed EP1 radios through ODIN because I was planning on going to GG 2.1 (I was following your video dave! its awesome btw*).I'm not sure at what point I lost access to my SD card. Ive read a lot this morning about voodoo lag fix affecting things. Could this be a problem with what I've done?
Sent from my SPH-D710 using Tapatalk 2
jpeclf said:
I dont have a focus but with a Google search looks bout the same as I wud do on my epic ..found this if it helps http://forums.androidcentral.com/dr...ks/130642-help-stuck-samsung-boot-screen.html
Alright, heres what I did.1. Rebooted in*CWM2. Wiped data/factory reset3. Wiped cache partition4. Wiped dalvik cacheAt this point I couldn't reflash because I forgot I couldn't access my SD card, I kept getting the "e:can't mount /sdcard" message whenver I went to install zip from sd card.5. Took off the back and pooped out the SD card and put it right back in. Seemed to work6. Flashed 2.07. Flashed kejar's sd card fix8. Rebooted through*CWMPhone starts up, do all the set up stuff, but still can't access my sd card or anything. Booted back into*CWM*just to see and was getting the "e:can't mount /sdcard" error again and couldnt reflash anything, so back to step 1.Here's a list of other things I have done since the original crap out a few days ago that might be affecting this.*1. Yesterday I tried reflashing 2.0 and it seemed to be boot looping again. So I just wiped data and cache partition and flashed 1.9.1 that I had on my SD card. Was having the same problems so that was the only time I tried it. Not sure if built in kernels might affect anything or whatever.2. After it seemed like I had a stable 2.0 again last night. I flashed blue*CWM*because I've had yellow this whole time. I also flashed EP1 radios through ODIN because I was planning on going to GG 2.1 (I was following your video dave! its awesome btw*).I'm not sure at what point I lost access to my SD card. Ive read a lot this morning about voodoo lag fix affecting things. Could this be a problem with what I've done?
Sent from my SPH-D710 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for your help but seeing as your phone is an Android phone, I don't think the same process applies. But thanks for the effort, I have this baby up and running now.. I just had to reflash the ROM.. Thanks again :good:
FocusHelp said:
Can someone please help me? I have a Samsung focus that was recently acting up.. Games wouldn't open etc.. so I decided to reset it.. After I reset it.. Its now stuck at the Samsung logo after resetting.. I am guessing that I need to reflash it.. If so, I need to make sure my battery isn't dead. Does the Phone charge while showing the Samsung boot logo?? Help Please..
Click to expand...
Click to collapse
If you have decided to reflash then use ROM provided by 'voluptuary' (3.10a). And moreover, to flash, it would not matter if your battery is getting charged. Just plug the device to your PC using the USB cable and flash the device.
Be VERY sure you flash the correct ROM for your phone. If you have a version 1.3, then ONLY flash 1.3 ROMs to it. If you have a version 1.4, then ONLY flash 1.4 ROMs to it. You can find the version number under the battery on the sticker. If you flash the wrong version of ROM to it, you will end up with a brick.
When having problems like this, I would recommend flashing the Stock ROM to it first to set everything back to normal. Then, if that works fine, go to custom ROMs if desired. Stock flashing will replace everything back to new settings, including spl, radio, etc... Some of the custom ROMs are truly worth flashing, FASTER, stable, nice features.
Unokashi01 said:
If you have decided to reflash then use ROM provided by 'voluptuary' (3.10a). And moreover, to flash, it would not matter if your battery is getting charged. Just plug the device to your PC using the USB cable and flash the device.
Click to expand...
Click to collapse
I know I had 3.05a and reflashed 3.10a Clean Rom.. It works great now... I remember I use to have problems with the 3g but not after reflashing it works great

Categories

Resources