Database Info

[Q] Loop problem

Hello all. I'm pretty new and I hope this is the right place to open this thread. I did many searches, tried a lot of ways but i can't fix my problem.
Well the problem is that Everytime that i flash a new rom (in the Restoreway (Found on youtube) And in the .zip way) after installing the rom, and rebooting from xRecovery it start an endless loop and i don't really know how to fix it.
I tried many methods. Like wiping cache, factory reset and aaaall the other wipes.
so, ill ask you guys, please help me cause i can't find a way to flash this thing. :\
thank you so much.

hey dude i suggest you flash back your phone to stock rom
That fixes all the problems in the system and after that you just root it again
and install everything you want but be carefull in what you uninstall!

Try this...
I would suggest GSB ROM 3.6. Been using this rom since since version 2.2 and had very little problems. It is important that you follow Sheds instructions to the letter. It is very fast and basically trouble free. You can get it here. http://forum.xda-developers.com/showthread.php?t=944430

install ruu ?

do a factory rest ..else try stockroms

what i'll do is try to wipe cache partition and wipe dalvik cache before i flash a new ROM... if it still fails then i will do wipe cache partition and wipe dalvik cache and factory reset before i flash new ROM...
my last resort will be to flash stock ROM then flash custom ROM again...

CM7 Nightly Question

Hi all. I recently got my Inspire and have flashed a few ROMS, finally settled on CM7.1 RC. I want to try out the nightly route, but not entirely sure what order to do it all in. This is what I think I need to do:
Go into recovery, format /cache, wipe dalvik cache. Flash nightly 144 over my current 7.1, flash the bbmod165bBFS.zip, then juwe11 script (does this get flashed each nightly?), then reboot. Is this correct, or am I forgetting anything? Do I need to flash gapps again? I already made a NANDroid. Thanks.

RampageRR said:
Hi all. I recently got my Inspire and have flashed a few ROMS, finally settled on CM7.1 RC. I want to try out the nightly route, but not entirely sure what order to do it all in. This is what I think I need to do:
Go into recovery, format /cache, wipe dalvik cache. Flash nightly 144 over my current 7.1, flash the bbmod165bBFS.zip, then juwe11 script (does this get flashed each nightly?), then reboot. Is this correct, or am I forgetting anything? Do I need to flash gapps again? I already made a NANDroid. Thanks.
Click to expand...
Click to collapse
you got it. i dont think you have to flash the script everytime and you will not have to flash gapps everytime. btw you dont have to wipe between nightlys just simply flash over

Thanks, I appreciate the quick reply. So I shouldn't bother to wipe cache and dalvik cache? I thought that was pretty much recommended before flashing the majority of stuff. Ok, so I'm off to flash this nightly.

I never wipe between nightlys. But if you ever do encounter problems, then wipe cache, dalvik cache then reflash
Sent from my Desire HD using XDA Premium App

I've always wiped cache and dalvic between nightlies. I don't know if it's needed but I've never had any problems with installs. It only takes a few seconds and it's never hurts to be safe.
Sent through the power of Cthulhu!

I flashed 144, no issues so far. Thanks to all of you for the replies. I ended up wiping cache and dalvik cache just to be safe. I know there's a change log, but has there been any changes of consequence over 7.1 RC that are noticeable?

I know the most easily noticeable is if you put a lock screen on you can disable the lockscreen. Plus from 143 on is now on 2.3.5 if I'm not mistaken which does have some slight tweaks.
Sent through the power of Cthulhu!

[Q] about wiping

how much wiping is necessary on the nexus s when flashing roms and kernels? i've had a habit of wiping data/cache/dalvik 3 times each from my epic days when it only had a broken clockwork recovery to work with. is that a recommended procedure?
i also see that when you select wipe data/factory data reset in clockwork, it wipes cache. does this make the wiping cache step unnecessary when installing a new rom?
one last thing. . . every time i wipe dalvik cache the prompt delivers an error. is this normal? is anything actually being wiped?
thanks in advance for your help

v3rk said:
how much wiping is necessary on the nexus s when flashing roms and kernels? i've had a habit of wiping data/cache/dalvik 3 times each from my epic days when it only had a broken clockwork recovery to work with. is that a recommended procedure?
i also see that when you select wipe data/factory data reset in clockwork, it wipes cache. does this make the wiping cache step unnecessary when installing a new rom?
one last thing. . . every time i wipe dalvik cache the prompt delivers an error. is this normal? is anything actually being wiped?
thanks in advance for your help
Click to expand...
Click to collapse
Use dalvik-wiper.zip from morfic to wipe the dalvik on your Nexus S.
Steps to flash a rom, kernel:
wipe cache
wipe dalvik using dalvik-wiper.zip
flash rom/kernel
fix permissions
If you're having any issue, boot loops, wipe data.

wow i can't believe i went this whole time without ever actually wiping the dalvik. . . heh
thank you! armed with this info i couldn't resist the itch to do a clean install of my favorite rom/kernel

[Q] Problem on boot

Hello everyone, I have a problem with my i9023 nexus s.
When going on, every time freezes, then restarts and turns on, normally.
I don't now what happened.
I start by saying that i have root, the stock ics rom and kernel Matr1x 15.5, and I already have ( downloaded on my pc ) the stock gingerbread rom with no root.
Help me.
p.s. : my nexus s is fully functional

have you changed voltages up or down??
did you flash that rom with a clean install??
did you wipe dalvik cache before you flashed that kernel?
did you have this problem on any other kernel?

nodstuff said:
have you changed voltages up or down??
did you flash that rom with a clean install??
did you wipe dalvik cache before you flashed that kernel?
did you have this problem on any other kernel?
Click to expand...
Click to collapse
Yes, i wipe the dalvik cache, but i don't install other kernel, and i install the ics stock from gingerbread with the update.zip

hi mate, i had same problem with "cybergr v.5 ics rom", lots of reboots,
durning using camera app all screen covered in green "flickering" lines, lots of fcs, freezing boot ...
yes i did full clean install, wiping system, data, cache, cache partition, boot, dalvik and whatever else is out there to clean,
few times each, prior to my two attempts to make this room work properly on my phone.
im not OC.
it didnt work for me at all.each time the same bugs.
i have to admit, that CyberGR v.5 is freaking fast ...
i returned to my bugless rom " AndroidMe 1.1.0"
That rom has no modification, isnt the fastest around [ although still pretty fast ]
, but hey man if u looking for some really stable ics rom, try this room " AndroidMe 1.1.0"
I dont know man, i might be very well far from true, but i start thinking, that my ns [9020t] simply does not like matrix kernel, cuz that unlucky for me CyberGR was runnig matrix kernel and i had very similar problems before, when i was running NSCollab, which did include matrix kernel.
BTW find some thread/s regarding clean install , u need to do a CLEAN INSTALL;
-boot in to recovery,
-wipe data/factory reset and cache partition and Dalvik cache,
-from mounts and storage select:
-format system,
-format data,
-format cache,
-format boot.
u can repeat those step if u want, although im not sure is usefull.

Is clean flash really clean?

I have been using custom roms for guite a long time now. I have flashed several different roms and several flashable apps and mods without any major problems.
Until today. I flashed one camera app on top of another. The result was "com.android.phone has stopped".
1. So I first tried to uninstall that app with Rom Toolbox. Didn't help.
2. Then I cleared data and cache from Phone services. Didn't help.
3. Then I booted to recovery and wiped cache. No help.
4. Then I made factory reset, i.e. clean flash of my current rom. That did not help either! Still com.android.phone FC.
Seems that clean flash had still left something somewhere that caused the FC.
5. So I had to wipe EVERYTHING and flash and install and copy and restore all apps and data back to phone. Several hours of a job.

Yep, wiping everything is clean flash, or wipe everything but internal storage (if still problems, delete . Android folder beforehand).
Sent from my Pixel using XDA-Developers Legacy app

simeoni said:
I have been using custom roms for guite a long time now. I have flashed several different roms and several flashable apps and mods without any major problems.
Until today. I flashed one camera app on top of another. The result was "com.android.phone has stopped".
So I first tried to uninstall that app with Rom Toolbox. Didn't help.
Then I cleared data and cache from Phone services. Didn't help.
Then I booted to recovery and wiped cache. No help.
Then I made factory reset, i.e. clean flash of my current rom. That did not help either! Still com.android.phone FC.
Seems that clean flash had still left something somewhere that caused the FC.
So I had to wipe EVERYTHING and flash and install and copy and restore all apps and data back to phone. Several hours of a job.
Click to expand...
Click to collapse
for mw to be clean i would flash stock firmware then do the following procedure here
https://forum.xda-developers.com/tmobile-g4/development/turbo-cleaning-proceure-h811-t3417606

simeoni said:
I have been using custom roms for guite a long time now. I have flashed several different roms and several flashable apps and mods without any major problems.
Until today. I flashed one camera app on top of another. The result was "com.android.phone has stopped".
So I first tried to uninstall that app with Rom Toolbox. Didn't help.
Then I cleared data and cache from Phone services. Didn't help.
Then I booted to recovery and wiped cache. No help.
Then I made factory reset, i.e. clean flash of my current rom. That did not help either! Still com.android.phone FC.
Seems that clean flash had still left something somewhere that caused the FC.
So I had to wipe EVERYTHING and flash and install and copy and restore all apps and data back to phone. Several hours of a job.
Click to expand...
Click to collapse
A factory reset isn't a clean flash. A clean flash is wipe system, data, dalvik/art cache. You have flashed the camera app to your system partition, so you have to wipe /system in twrp too (together with /data and /cache if you want to make a clean flash). But in your case it should be enough to wipe system and then reflash your Rom to get rid of your issue

rob rich said:
A factory reset isn't a clean flash. A clean flash is wipe system, data, dalvik/art cache. You have flashed the camera app to your system partition, so you have to wipe /system in twrp too (together with /data and /cache if you want to make a clean flash). But in your case it should be enough to wipe system and then reflash your Rom to get rid of your issue
Click to expand...
Click to collapse
OK, thanks. Maybe in my step 4 above I thought that factory reset was enough but I didn't notice that it does not wipe system. So I went too far and wiped all my data, too.
But earlier when I have flashed different roms and they always tell that you must do clean flash, I didn't wipe system. So I thought clean flash was just factory reset. Still those different roms were working ok. Next time I try to remember wipe system also.