Well i have been using the cm7 nightlies with no problem. Today i decided to flash the RC1 since im sick of having to flash everyday. So i flashed the rom with rom manager and my phone was stuck in a boot loop.
So i had to do a battery pull and then restore the rom i had just backed up. After restoring i reboot the phone and am stuck in a boot loop again. I did another battery pull did a full data wipe, wiped cache and dalvik cache. And reinstalled the nightly 41 and am no longer in a boot loop.
So i tried to install RC1 again and everything was fine after flashing rom and gapps. i thought everything was fine so i rebooted into recovery to flash the 1.2.2 BFS Netarchy kernel. Before flashing i wiped cache, and dalvik cache. And of course now im stuck into a boot loop again. Has anyone else experienced this problem? i believe i am doing everything right. This is the first time i have ever experienced this problem.
B2L said:
Well i have been using the cm7 nightlies with no problem. Today i decided to flash the RC1 since im sick of having to flash everyday. So i flashed the rom with rom manager and my phone was stuck in a boot loop.
So i had to do a battery pull and then restore the rom i had just backed up. After restoring i reboot the phone and am stuck in a boot loop again. I did another battery pull did a full data wipe, wiped cache and dalvik cache. And reinstalled the nightly 41 and am no longer in a boot loop.
So i tried to install RC1 again and everything was fine after flashing rom and gapps. i thought everything was fine so i rebooted into recovery to flash the 1.2.2 BFS Netarchy kernel. Before flashing i wiped cache, and dalvik cache. And of course now im stuck into a boot loop again. Has anyone else experienced this problem? i believe i am doing everything right. This is the first time i have ever experienced this problem.
Click to expand...
Click to collapse
try flashing the kernel without wiping the dalvik or cache.
personal, i dont use or recommend using rom manager, as it creates issues of its own. i download everything myself and flash in recovery without rom managers aid.
I'm trying that now. Thanks for the quick reply. I have even tried installing the rom without using rom manager and it still did the same thing to me. Hopefully this works.
This just started yesterday and i cant stop it. My phone reboots and says that memory is nearly full, then goes into a bootloop. I cant stop it long enough to back up texts, phone contacts and call log which is REALLY important; is there a way to back that up through recovery?
i'm really desperate here!
Edit: I can get the phone working through a format, but i need to be able to get contacts and sms backed up
Alternitavely, is there a way to run a clockword mod backup on an android emulator on my comp, so i can back up my important stuff?
what you should try doing is putting your sd card directly into your computer and delete stuff you don't need to get back so memory and then once you do that out it back into your phone
i cleared up the memory, internal and external. the stupid ROM is still broken
if its just the rom go to a different one and redownload mikrom later to make sure nothing happened in the initial download
If you haven't already, try removing some apps through adb, then reflash the ROM only wiping dalvik and cache. You shouldn't lose any of your text, call logs or contacts if you don't wipe data.
Sent from my PG06100 using Tapatalk
From The Hacker Manifesto:
I made a discovery today. I found a computer. Wait a second, this is cool. It does what I want it to. If it makes a mistake, it's because I screwed it up. Not because it doesn't like me... Or feels threatened by me.. Or thinks I'm a smart ass.. Or doesn't like teaching and shouldn't be here...
Click to expand...
Click to collapse
I love it sooooo the rom isnt stupid, the team of developers supporting it are amazing and you should setup adb and get a logcat, also you should nandroid before you flash so in case it goes wrong you can flash back, like insurance but you actually get something from this without paying..
if you did nandroid boot into bootloader and select recovery (hold volume down and power on use volume button to highlight recovery and power button to select)
I'm not sure if mikrom wipes or not but there's always that advanced restore option in cwm recovery flash rom, restore data and sd-ext if you have a ext partition with important data on it.
crump84 said:
If you haven't already, try removing some apps through adb, then reflash the ROM only wiping dalvik and cache. You shouldn't lose any of your text, call logs or contacts if you don't wipe data.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
I managed to get some apps removed, its no longer giving me the memory-full error, but its still bootlooping a minute or so after loading. going to try the cache and davlik wipes, then a another install....
JKILO said:
From The Hacker Manifesto:
Click to expand...
Click to collapse
thanks I always do a nandroid backup before doing a format; doesnt help. I can load the clean rom just fine, but when i restore, it goes into bootloop again....
sparksco said:
I'm not sure if mikrom wipes or not but there's always that advanced restore option in cwm recovery flash rom, restore data and sd-ext if you have a ext partition with important data on it.
Click to expand...
Click to collapse
ok, ill try this.
Also, how do i set up an sd-ext to automatically backup texts and call history etc to it?
crump84 said:
If you haven't already, try removing some apps through adb, then reflash the ROM only wiping dalvik and cache. You shouldn't lose any of your text, call logs or contacts if you don't wipe data.
Sent from my PG06100 using Tapatalk
Click to expand...
Click to collapse
did not work - goes back to bootloop. how do i install ADB?
Jedman67 said:
did not work - goes back to bootloop. how do i install ADB?
Click to expand...
Click to collapse
http://developer.android.com/sdk/index.html
Beginner's Guide to Installing the SDK and Getting Started with ADB
If nothing else, like Jkilo said, provide a logcat and maybe someone could take a look.
Did you ever get this fixed?
The usual way of fixing this is formatting /system, wiping dalvik, wiping cache, and reflashing the rom.
VICODAN said:
Did you ever get this fixed?
The usual way of fixing this is formatting /system, wiping dalvik, wiping cache, and reflashing the rom.
Click to expand...
Click to collapse
no. what i did was a backup, complete factory reset, wipe, dalvik wipe, etc - several times each, including a full on sd-card format, which took me hours to reload everything back on - and then reflashed MikShift. It worked fine for about a day, but then it started to go into bootloops again, so i again did a backup, full reset and all wipes, and restored data only to the new flash of mikshift. Once again its bootlooping.
LOG: ive been off the forums for several months, how do i get this log?
IMAGE: When i go into bootloader and enter recovery, it shows me a message in green text
"PG06diag.zip
No image!
PG06diag.nbh
No image or wrong image!
PG06img.zip
No image!
PG06img.nbh
No image or wrong image!"
At this point, im ready to RUU back to factory unrooted, so i can take it back to sprint and get it replaced.
I should not need to reflash the ROM every single day.
Jedman67 said:
no. what i did was a backup, complete factory reset, wipe, dalvik wipe, etc - several times each, including a full on sd-card format, which took me hours to reload everything back on - and then reflashed MikShift. It worked fine for about a day, but then it started to go into bootloops again, so i again did a backup, full reset and all wipes, and restored data only to the new flash of mikshift. Once again its bootlooping.
LOG: ive been off the forums for several months, how do i get this log?
IMAGE: When i go into bootloader and enter recovery, it shows me a message in green text
"PG06diag.zip
No image!
PG06diag.nbh
No image or wrong image!
PG06img.zip
No image!
PG06img.nbh
No image or wrong image!"
At this point, im ready to RUU back to factory unrooted, so i can take it back to sprint and get it replaced.
I should not need to reflash the ROM every single day.
Click to expand...
Click to collapse
OK
0) Run a backup with titanium backup.
1) First of all go to clockwork -> mounts storage -> FORMAT /SYSTEM.
2) Wipe /cache, wipe dalvik, wipe/data, factory reset, repartition sd card.
3) Redownload the rom or try a proven ROM like UKE or CM7-255. If AOSP MAKE SURE TO FLASH GAPPS.
NO NEED TO RUU.
4) DO NOT RESTORE YOUR BACK UP. See how stable the phone runs.
5) If the phone is still unstable try a different battery.
6) Do not flash a custom kernel.
i formatted my backup SD card, and copied the essential data to it, and i have it running in the phone now. it seems to be running fine so far, i suspect the other SD may have gotten corrupt or physically damaged
Vic: every single time this has happened, i first went to clear the data and dalvik caches and ran a factory reset, all through the CWM recovery interface. Then when i reinstall mikshift, i restore the data using advanced restore, wait 24-48 hours, bootloops start all over again.
after two days of running on the new sd card, i start getting bootloops again. it must be a problem with the phone or the OS, but at this point i dont care anymore.
Is there a guide to RUU back to stock unroot? this phone is going back to sprint by weeks end, period.
thanks for the help folks.
Jedman67 said:
Vic: every single time this has happened, i first went to clear the data and dalvik caches and ran a factory reset, all through the CWM recovery interface. Then when i reinstall mikshift, i restore the data using advanced restore, wait 24-48 hours, bootloops start all over again.
after two days of running on the new sd card, i start getting bootloops again. it must be a problem with the phone or the OS, but at this point i dont care anymore.
Is there a guide to RUU back to stock unroot? this phone is going back to sprint by weeks end, period.
thanks for the help folks.
Click to expand...
Click to collapse
Here's the 2.2 RUU zip http://forum.xda-developers.com/showthread.php?t=971550 Just put it on the root of sd, boot in hboot and let it do its thing.
Or you can run the RUU exe, just download and run from your pc. It's pretty self explanatory http://forum.xda-developers.com/showthread.php?t=1335068
Jedman67 said:
Vic: every single time this has happened, i first went to clear the data and dalvik caches and ran a factory reset, all through the CWM recovery interface. Then when i reinstall mikshift, i restore the data using advanced restore, wait 24-48 hours, bootloops start all over again.
after two days of running on the new sd card, i start getting bootloops again. it must be a problem with the phone or the OS, but at this point i dont care anymore.
Is there a guide to RUU back to stock unroot? this phone is going back to sprint by weeks end, period.
thanks for the help folks.
Click to expand...
Click to collapse
The problem is you didn't format /system.
Redownload the Rom. Then follow THIS GUIDE when you flash.
VICODAN said:
The problem is you didn't format /system.
Click to expand...
Click to collapse
Exactly 10 char
---------- Post added at 12:34 AM ---------- Previous post was at 12:31 AM ----------
prboy1969 said:
Redownload the Rom. Then follow THIS GUIDE when you flash.
Click to expand...
Click to collapse
Yeah that guide is great for flashing sense roms since "most" sense roms don't format/wipe the system partition correctly. Aosp roms you just do a data facotry wipe and everything installs just fine
I have this in development but though it shoudl be here.
Please help
I had issues loading AOKP| Build 4
These issues were caused I think by me. Before reloading I wiped Cache and Dalvic Cache, I then did a Format/Factory reset. While on this it stayed on formatting cache for about 20 mins. Since it locked up on formatting cache I held the power and vol down to get back in to CWM. I tried to install zip from ext sd Build-4. When it started it gave me a 4-5 lines saying E: Can't mount /cache/recovery/log and others relating to that. I proceeded anyway with loading build-4, sometime through the installation it rebooted itself. After that the unicorn would come up for a few secs then reboot, then keep doing it in a boot loop. I again went in to CWM and tried again with the cache, dalvic and factory reset, same thing happened where it got stuck at cache but it restarted by itself this time. I then downloaded the stock rom from http://forum.xda-developers.com/show....php?t=1722745. After loading stock from Odin I was able to get ride of the cache errors and cache lock up problems.
The issue now is reguardless of Build-4 or stock it is stuck at either the unicorn or the samsung logo. I have also tried CM10, so stuck at boot now on stock, CM10 and AOKP-Build-4 Any help would be GREAT. Thanks
Do a factory reset in the stock recovery.
You are my hero!!! Several days of doing all kinds of things and that was the one I would have never thought about. Yup and going. No problems now.
Sent from my SPH-D710 using xda premium
So i rooted my tablet about a week ago and went to install adaway today when i went to reboot it it got stuck in a loop and so i tried a factory reset but now its in a loop of starting, saying upgrading apps, then saying process com.android.phone has stopped working then restarting again and keeps going what can i do to fix it?
CarsonM135 said:
So i rooted my tablet about a week ago and went to install adaway today when i went to reboot it it got stuck in a loop and so i tried a factory reset but now its in a loop of starting, saying upgrading apps, then saying process com.android.phone has stopped working then restarting again and keeps going what can i do to fix it?
Click to expand...
Click to collapse
You Should flash the stock firmware through Odin . Your data will not be erased .
Don't forget to press the thanks button :good::good::good:
Really! Flash to stock just for a bootloop. Unnecessary I think. I would just go to recovery and wipe system, cache, and dalvik and reflash the ROM. If that doesn't fix, then do the same but wipe data as well. You'll have to reinstall apps of course with that last one. Also, If you have an external sd card and a card reader, you could download a different ROM to the card and flash that one in recovery.
Lol
wolfclan68 said:
Really! Flash to stock just for a bootloop. Unnecessary I think. I would just go to recovery and wipe system, cache, and dalvik and reflash the ROM. If that doesn't fix, then do the same but wipe data as well. You'll have to reinstall apps of course with that last one. Also, If you have an external sd card and a card reader, you could download a different ROM to the card and flash that one in recovery.
Click to expand...
Click to collapse
Flashing to stock always fix bugs that wiping can't solve
Because flashing to stock will restores the original firmware :good:
Sent from Gallifrey using TARDIS