God do I hate technology sometimes.
Phone was working perfectly, ages ago, I had updated it to JF 1.5, with apps2SD, and everything is working perfectly until today, I restart my phone (not the first time I have done this since last updating my phone), and for some reason it cant go beyond the android flashing screen. Just keeps going.
WTF do I do? I do not want to have to reflash my phone causing me to have to reinstall all my apps, etc. Just too much hassle, I hope it doesnt come to that.
Does anyone have any ideas?
I have tried removing the battery and putting it back, no difference. Maybe I didnt do it for long enough.
Any advice or help would be much appreciated.
wel I thought I may as well reflash with JF 1.5, and have done so, but the phone STILL won't go past the flashing android screen.
Dunno what to do now, I had thought this would definately do the trick.
Any help would be much appreciated.
Use the search bttom.... and WIPE the phone, Wipe the phone and problem solve...
i have almost same problem
except mine goes past android screen then screen goes blank but stays lit up
Don't wipe your phone. Try this first.
Krazyone said:
Figured i would update this with the knowledge i have gained. Erase the EXT2 / 3 partition then wipe. Load the ROM again and reboot. This should let it pass the boot loop. I had the problem this morning with Drizzy's Hero build and now with JAC's I am running tests with.
Click to expand...
Click to collapse
I had the same problem so I did what Krazyone suggested in one of the post. And it solved my problem. It's something to do with your EXT partition be corrupted or something.
EDIT: You will have to either reload your apps or restore them from your backup.
Same problem here & tried as you suggested...
BeenAndroidized said:
Don't wipe your phone. Try this first.
I had the same problem so I did what Krazyone suggested in one of the post. And it solved my problem. It's something to do with your EXT partition be corrupted or something.
EDIT: You will have to either reload your apps or restore them from your backup.
Click to expand...
Click to collapse
I tried that, but phone still wouldn't boot past the android screen. So, will wipe & start anew.
Related
Hey guys. Lately it seems that any rom I try to flash, it get's stuck at the boot screen. Not really "stuck," more like looping. I first noticed it going from Aloysius to Damage Control 2.08.1. Now I'm not at all blaming any rom, as I'm sure it's something I'm not doing.
I'm no stranger to flashing roms. I know to nan-back, wipe, then flash. But oddly enough, i'm stuck with restoring to Aloysius' rom because that seems to be the only one that DOESN'T get stuck in the loop.
Can anyone help me on what I may be doing wrong?
derynhaze said:
Hey guys. Lately it seems that any rom I try to flash, it get's stuck at the boot screen. Not really "stuck," more like looping. I first noticed it going from Aloysius to Damage Control 2.08.1. Now I'm not at all blaming any rom, as I'm sure it's something I'm not doing.
I'm no stranger to flashing roms. I know to nan-back, wipe, then flash. But oddly enough, i'm stuck with restoring to Aloysius' rom because that seems to be the only one that DOESN'T get stuck in the loop.
Can anyone help me on what I may be doing wrong?
Click to expand...
Click to collapse
Have you tried wiping your SD PARTITION? That is the main reason people get bootloops going from one ROM to the next.
Konikub said:
Have you tried wiping your SD PARTITION? That is the main reason people get bootloops going from one ROM to the next.
Click to expand...
Click to collapse
I've never had to do that before, I'll be sure to try it. What does it do? Hearing the words "SD" and "Wipe" together is kinda scary
derynhaze said:
I've never had to do that before, I'll be sure to try it. What does it do? Hearing the words "SD" and "Wipe" together is kinda scary
Click to expand...
Click to collapse
You'll be fine...lol. Wipeing the SD partition does not wipe your card completely....everything will remain, it will just make your Phone boot other ROMS properly I have had many people come to Aloysius with the same issue, and wiping the SD partition did the trick every time!
Wiping it didn't solve the problem but what did was repair and wipe. Thanks for the info! Much appreciated!
I'm serious. It's slow everything force closes and I figured now that cyanogen had his new build of Froyo....I could give the kang o rama a try. but everything is still force closing and I have no idea how to fix it and I'm about ready to just give up :/
What do I do?
Are you completely wiping everything before you install a rom?
Give yourself a wipe, or at least a cache partition wipe
Sent from my Nexus One using XDA App
if its slow then something is using a large amount of cpu power.
I just caught Flickie doing it (thanks to CPUStatusLED)....but it stopped before i got to uninstalling it.
Backup your apps, wipe everything data, ext, cache..then install a ROM.
My phone was freezing/rebooting 3-10 times a day before I did the above and now its quite stable.
EVERYTHING has been wiped. Dalvik, cache, Factory reset, everything I could do without doing anything to the SD card.
I'm seriously at a loss for words.
Currently on kang o rama's 2.2 cyanogen build A2 btw is what I'm trying to work with. Though it has been no different for other roms. I Mean it's so unresponsive and always force closes everything
2.1 works ok ?
2.2 doesn't you say? after all wipes and a clean install of Cyanogen and other ROMs? How about stock Froyo FRF91?
It may be a hardware error if the stock one doesn't work. So even if you got an unlocked phone, Google/HTC should replace it because it's hardware. If you're installing it wrong SOMEhow.. then that's another story.
EDIT: NVM believe I found it
I just went through this.
Just download the PASSIMG.ZIP from the latest Eclair build and put it on the root of your SD card. Go into bootloader and it will automatically pick it up.
In a minute you'll be at stock Eclair. By the time you can get into the Settings menu, you'll have the majority of FRF91 downloaded. Let it do its thing and probably within 5 minutes you'll be sitting pretty on a stock FRF91 Froyo build.
http://lmgtfy.com/?q=passimg+eclair
First link
If you've used the Froyo App2SD function, then you might need to delete your .AndroidSecure folder on your SD card after a flash.
I never touched that folder and the last few times I flashed a ROM I was getting weird problems where I couldn't install things, it would hang, I would get FCs, etc. I deleted that folder, rebooted, and everything was cleared up for me.
...Of course you'll have to install those apps again.
mudrock1000 said:
I'm serious. It's slow everything force closes and I figured now that cyanogen had his new build of Froyo....I could give the kang o rama a try. but everything is still force closing and I have no idea how to fix it and I'm about ready to just give up :/
What do I do?
Click to expand...
Click to collapse
Have you installed the latest radio image? Even if you have give it another flash. I had the same problem on my Hero
mindfrost82 said:
If you've used the Froyo App2SD function, then you might need to delete your .AndroidSecure folder on your SD card after a flash.
I never touched that folder and the last few times I flashed a ROM I was getting weird problems where I couldn't install things, it would hang, I would get FCs, etc. I deleted that folder, rebooted, and everything was cleared up for me.
...Of course you'll have to install those apps again.
Click to expand...
Click to collapse
Yea thats a good idea. The short time I've been on Android, it seems like A LOT of CRAP gets brought into new builds. Everytime I flash a new rom, the Market downloads all the crap from before. lol.
While I can see it as being a nice feature, it can get troublesome. When my replacement Nexus comes tomorrow, I'm going to backup my APK files and format my SD card. Start completely from scratch on Froyo 2.2
Usually I have NO problem hunting for things myself...but I DO NOT AT ALL...see this "Passimg" in that thread.
ANYWAYS I'm gonna try reflashing the radio to see if that helps
This is why I just use stock stuff, I want my phone to just work
khaytsus said:
This is why I just use stock stuff, I want my phone to just work
Click to expand...
Click to collapse
Foo Stock dun work .
Anyways good news...I've gone more then a few minutes without it crashing. . I think the radio think might actually have worked.
Wait market crashed. I'm hoping it's just a thing and I'm gonna reboot and try again.
Nope just more Force Closes
Tell me about this passimg.
mudrock1000 said:
Foo Stock dun work .
Anyways good news...I've gone more then a few minutes without it crashing. . I think the radio think might actually have worked.
Wait market crashed. I'm hoping it's just a thing and I'm gonna reboot and try again.
Click to expand...
Click to collapse
And you're sure your N1 isn't defective?
Other then the occasional data connection failure...yea Eclair worked perfectly.
And sriously...guys I need the effing stock rom image I wanna try something else BUT I don't have it.
Oh yea. AND NOW I'm trying to reinstall the apps but it says out of space...and I can clearly see I have 111 mbs of internal storage. I think it's installing it on the SD card. IDK HOW TO MAKE IT STOP and I'm so frustrated I'm about ready to dump my n1. I've been screwing with this forever and I was excited. The first build of Cyanogen and nothing works...
mudrock1000 said:
Other then the occasional data connection failure...yea Eclair worked perfectly.
And sriously...guys I need the effing stock rom image I wanna try something else BUT I don't have it.
Oh yea. AND NOW I'm trying to reinstall the apps but it says out of space...and I can clearly see I have 111 mbs of internal storage. I think it's installing it on the SD card. IDK HOW TO MAKE IT STOP and I'm so frustrated I'm about ready to dump my n1. I've been screwing with this forever and I was excited. The first build of Cyanogen and nothing works...
Click to expand...
Click to collapse
Wipe, install rom, reboot and hold volume down to load the bootloader, power off in bootloade, pull battery, remove microsd, replace battery, boot and set it up. See what happens.
you might just have a faulty hardware (bad ram or something)
norazi said:
you might just have a faulty hardware (bad ram or something)
Click to expand...
Click to collapse
I'm betting it has something to do with data saved on the sd. . .
Afternoon all!
I would REALLY like to completely wipe my phone and SD and start all over from scratch. I'm rooted, and I've tried WAY too many codes/flashes/apps that I'm sure embedded code in my system that causes some of the errors I get now. I've been told that if I wipe the SD, it'll properly reset, but I've also read of problems after wipe. I'm wondering if anyone knows of a fool proof way to start all the way over for a brand new phone feel. I'll un/re-root if necessary.
Any ideas?
Thanks in advance!
IP IHI II IL
I remember last time having this idea on a random day feeling that my phone was too much, I decided to go to my sd card on my phone from my PC and deleted every folder there WHICH IS NOT GOOD AT ALL, so I'd suggest you wait for someone who knows or can tell you how to properly start over fresh on your new phone.
impatient, but not stoopid!
yeah, I was thinking of goin' rogue and just randomly deleting crap, but my better side made me hold off... I DID get impatient, though and try a suggestion from the Virus forums. I ran the format SD from the phone, then replaced all my ROM zips, and rebooted to recovery first wiping everything 2-3 times, then re flashing Virus ROM 4.X, and my favorite functions/kernel/radios/font... So far so good, though I still would REALLY like to start all the way from scratch. There were some settings embedded into the phone it seems, as I still have my custom splash, even before flashing again... For now, I guess I'm ok with a semi-clean slate, but would still like to know whether or not I can completely start from scratch...
Thanks for the reply, alekosy!
IP IHI II IL said:
yeah, I was thinking of goin' rogue and just randomly deleting crap, but my better side made me hold off... I DID get impatient, though and try a suggestion from the Virus forums. I ran the format SD from the phone, then replaced all my ROM zips, and rebooted to recovery first wiping everything 2-3 times, then re flashing Virus ROM 4.X, and my favorite functions/kernel/radios/font... So far so good, though I still would REALLY like to start all the way from scratch. There were some settings embedded into the phone it seems, as I still have my custom splash, even before flashing again... For now, I guess I'm ok with a semi-clean slate, but would still like to know whether or not I can completely start from scratch...
Thanks for the reply, alekosy!
Click to expand...
Click to collapse
Maybe this'll help, I tested myself and it works fine.
http://forum.xda-developers.com/showthread.php?t=855424
alekosy said:
Maybe this'll help, I tested myself and it works fine.
http://forum.xda-developers.com/showthread.php?t=855424
Click to expand...
Click to collapse
GET OUTTA' MY HEAD!
I used that as well, and yeah, it works great! Thanks!
IP IHI II IL said:
GET OUTTA' MY HEAD!
I used that as well, and yeah, it works great! Thanks!
Click to expand...
Click to collapse
Glad I helped you there, It's really useful for me too xD
I tried to go from my AOKP device to a stock rooted rom I downloaded from the Development Section here, but it seemed to go horribly wrong.
I got force closes all over the shop, so I did a Factory Reset and tried again, still got Force Closes.
I tried to restore my Backup, but it seems that 4.2 puts my SDCARD data in a folder called /0/, so TWRP couldn't find them.
I have ended up downloading the Factory Image for 4.2 from Google and have decided to start from scratch. (And deleted ALL MY DATA in the process!!)
So, is there anyway I can root this stock ROM? I have just re-installed TWRP, so I am set with a custom recovery!
http://forum.xda-developers.com/showthread.php?t=1750835
This worked for me.
It might cause a boot loop.. Don't worry about it, let it sit a few..then power off
And restart.(see the last page in the thread.)
taqulic said:
http://forum.xda-developers.com/showthread.php?t=1750835
This worked for me.
It might cause a boot loop.. Don't worry about it, let it sit a few..then power off
And restart.(see the last page in the thread.)
Click to expand...
Click to collapse
Yeah, just done it! Seems to work well!
All I need now is an Extended Power Menu!!
Hi, my phone acted weird today, been running custom room for over couple months without any problem, but then when i resart my phone today it got to the bootload screen and stuck there ever seen. I can able to go into custom recover and did a full wipe but nothing change, could anyone help me out? I have loki also. Using S4 ATT version.
Try wiping cache in your recovery
i did that, always do that after install a new rom, don't know why my phone is soft bricked now...
akahimaro said:
i did that, always do that after install a new rom, don't know why my phone is soft bricked now...
Click to expand...
Click to collapse
if you've done a full wipe and tried either re-flashing your rom or restoring a nandroid and neither was successful, you may need to consider going back to stock via odin and starting over.
i've never seen a phone run on the same rom and kernel settings for months and then just shut down and softbrick without something having been changed recently.
xBeerdroiDx said:
if you've done a full wipe and tried either re-flashing your rom or restoring a nandroid and neither was successful, you may need to consider going back to stock via odin and starting over.
i've never seen a phone run on the same rom and kernel settings for months and then just shut down and softbrick without something having been changed recently.
Click to expand...
Click to collapse
yes, i'm doing that right now, thanks for the tips, i had that happen to my s2 before. Really weird...
Before ODIN'ing back to MDL/MDB...
akahimaro said:
yes, i'm doing that right now, thanks for the tips, i had that happen to my s2 before. Really weird...
Click to expand...
Click to collapse
What recovery image are you running? You are not the only one that had this problem. I am trying to piece this together.