Database Info

Test and possible solution to the reboots (GB related)

Well first off I do believe there are 2 different reboot problems. One related to radio/sig and a new one. Im very crazy about wiping everything before flashing roms. I would boot into cwr and wip data/factory reset, cache, dalvik, then go into mounts and storage and format /system and /sdcard. now i would have basically nothing on my phone or sd card.... i would then mount as usb storage from cwr and add the rom i wanted to flash. I would flash it and have 0 probs until the GB roms. Ive found that after wiping the SD card it would boot and after the setup process it would get non stop reboots every time it would get a data or voice sig. to fix it i had to wipe just data cache and dalvik and then reflash the rom and then everything was cool (besides maybe a reboot during setup but thats semi normal) ive gone a day now with 0 reboots on my phone. before that i tested and i can replicate this every time ive even tested it on my co workers phone. I dont know why this happens and im hoping some1 can test it by doing what i did in cwr and confirm that they also get reboots after this.
again the steps are:
Boot into CWR
Wipe data/factory reset
Wipe cache
Wipe dalvik
go into mounts and storage and format /system /sdcard
mount as usb and add in GB bamf beta 4 (since thats what i did my tests with)
reboot do the setup and see if you get reboots
report back here
p.s. please dont flame or ask silly questions kinda wana just keep it to people who have tested and have feed back
p.s.s. to fix the reboots just re wipe data cache dalvik and reflash rom

please some1 test it if you can confirm then im gong to test it on stock froyo roms etc

how to do a correct full wipe?

Hey guys, this might be a really noob question. I looked it up on google, but still wanted to make sure because of the verizon locked bootloader etc( i know we can unlock it now). How do i do a full wipe on my device? I am asking because there are a few more options in the wipe settings of the custom recovery i have.
This are the steps i always do before flashing a rom. Are they the correct steps or do i need to do something else?
Wipe Cache
Wipe Dalvik-Cache
Wipe Data/factory reset

dimeloklk said:
Hey guys, this might be a really noob question. I looked it up on google, but still wanted to make sure because of the verizon locked bootloader etc( i know we can unlock it now). How do i do a full wipe on my device? I am asking because there are a few more options in the wipe settings of the custom recovery i have.
This are the steps i always do before flashing a rom. Are they the correct steps or do i need to do something else?
Wipe Cache
Wipe Dalvik-Cache
Wipe Data/factory reset
Click to expand...
Click to collapse
Wipe Cache and wipe dalvik cache should both be done when flashing modifications or tweaks as they reduce the chance of encountering data issues/glitches and neither of them wipe your data as they are merely caches. Wipe data/factory reset should be done before flashing a rom. Wipe data/factory reset automatically wipes the cache and as the name implies will wipe any data you have on the phone, though any files you have saved to your internal "sd card" will be left intact. Before flashing a rom I always do a factory reset, and a dalvik cache wipe. Additionally I have found it helpful to also go into mounts and format system. There have been times for me that switching between two different roms has led to choppy performance, and this step seems to fix that as it thoroughly removes any traces of the previous rom.

Thanks for the detail reply. Is useful to know this since i always flash roms

OneNutShort said:
Wipe Cache and wipe dalvik cache should both be done when flashing modifications or tweaks as they reduce the chance of encountering data issues/glitches and neither of them wipe your data as they are merely caches. Wipe data/factory reset should be done before flashing a rom. Wipe data/factory reset automatically wipes the cache and as the name implies will wipe any data you have on the phone, though any files you have saved to your internal "sd card" will be left intact. Before flashing a rom I always do a factory reset, and a dalvik cache wipe. Additionally I have found it helpful to also go into mounts and format system. There have been times for me that switching between two different roms has led to choppy performance, and this step seems to fix that as it thoroughly removes any traces of the previous rom.
Click to expand...
Click to collapse
this is what I've always been taught to do as well.
sent from my unlocked bootloader Verizon Samsung galaxy s III

maybe you can get a dev to make a wipe zip

CM9 boot animation loop

I have clockworkmod recovery installed and rooted. It's been a few months since I rooted, and can't remember exactly what I did, but OTA updates stopped working. Hence, I am still on gingerbread.
Trying to flash a custom rom now, CM9. I tried the rom manager method several times, found out that wasn't recommended, and then tried the recovery method.
The same thing happens either way: it boots into CM9, but the boot animation keeps playing.
With the rom manager method, I tried wiping nothing, then tried wiping dalvik only, then tried... whatever the other option was, wipe cache and data?
With CMW recovery I downloaded CM9 zip and the appropriate GAPPS, moved onto the internal SD card, booted into recovery mode Wipe data/factory reset, then Wipe cache partition, then install both.
I'm able to restore from backup each time, but this is annoying.
Thank you

1. Install ICS Radio (UCLF6)
2. Wipe Data/Factory Reset
3. Format /System
4. Install CM9.zip
5. Install Gapps.zip
6. Wipe Cache/Dalvik
7. Reboot
:good:

UZ7 said:
1. Install ICS Radio (UCLF6)
2. Wipe Data/Factory Reset
3. Format /System
4. Install CM9.zip
5. Install Gapps.zip
6. Wipe Cache/Dalvik
7. Reboot
:good:
Click to expand...
Click to collapse
So "UCLF6" appears to be rom that is similar to stock, I'm guessing the idea here is that I'm resetting the phone but retaining root, the idea being that something on my phone is messed up and preventing CM9 from booting but doesn't prevent the current rom from booting?
Two other questions
1. Won't format/system wipe out all my backups in addition to my data?
2. Have you had or seen this problem before? I'm hesitant to commit myself to something, especially with no backups, if it's just a theoretical fix. I do appreciate it either way.

UCLF6 is an ICS modem/radio you need if you're coming from gb.
If you back up though CWM you can restore again later if you want.
Formatting /system will delete the operating system.
Formatting /data will delete your apps/settings/wallpaper etc...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2

I had a similar boot animation loop when I went from stock GB to stock ICS. What seemed to fix it was updating my CWM from 5.0.2.6 (non-touch) to 5.5.0.4 (touch). (BTW, I couldn't find an advantage of stock ICS over stock GB. I have since put on CM9 which I'm liking).

UZ7 said:
UCLF6 is an ICS modem/radio you need if you're coming from gb.
If you back up though CWM you can restore again later if you want.
Formatting /system will delete the operating system.
Formatting /data will delete your apps/settings/wallpaper etc...
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Still got the boot loop.
When I did the "Wipe data/factory reset" I did get an error message during one of the processes"
"Error mounting sdcard/.android_secure!
Skipping format"

I had a boot loop problem when I first tried to flash JB. I went from GB to ICS with a custom rom a few months back, but I couldn't get any of the new JB roms to work. I ended up having to upgrade my CWM to the touch version in order to get JB flash to work. Also, a tip-- the boot animation will take a minute or two even when it is working. Don't assume it is still a problem if you see it more than once.

Wiping Cache Partition

I accidentally installed a cyanogenmod zip without wiping the cache partition first, right now I am still on cwm recovery. I HAVE already wiped the data.
Should I wipe it now? Should I wipe data and then restart the process?
Any help would be appreciated.

You should be alright, the /cache partition on this phone doesn't hold too much important stuff. Just to be safe, reflash the CM zip, and wipe the cache and data. You will lose all of your apps and settings, but not wiping data usually causes problems when flashing different ROMs.

Problems after updating firmware for my samsung galaxy note 8 gt-n5110

I installed cm12.1 rom for my samsung galaxy note 8 gt-n5110 and after i turned it on this was what happened. It constantly showed text boxes like "unfortunately, google app has stopped" and after i closed it another one showed up and now i cant control it anymore! I cant even finish the setup! What can i do?
Im new to these firmware stuff btw.

sunglassesman said:
I installed cm12.1 rom for my samsung galaxy note 8 gt-n5110 and after i turned it on this was what happened. It constantly showed text boxes like "unfortunately, google app has stopped" and after i closed it another one showed up and now i cant control it anymore! I cant even finish the setup! What can i do?
Im new to these firmware stuff btw.
Click to expand...
Click to collapse
Try a smaller Gapps package than the one that you flashed with the ROM. The package you used is probably too large to fit in the system partition along with the ROM.
Or, you didn't factory reset, wipe cache and wipe dalvik cache when you flashed the ROM. Failing to do those wipes will cause bugs due to the new system conflicting with the saved system data/settings from the previous system. In other words, data left over from the old ROM is causing problems with the new ROM.
Sent from my SM-S767VL using Tapatalk

Droidriven said:
Try a smaller Gapps package than the one that you flashed with the ROM. The package you used is probably too large to fit in the system partition along with the ROM.
Or, you didn't factory reset, wipe cache and wipe dalvik cache when you flashed the ROM. Failing to do those wipes will cause bugs due to the new system conflicting with the saved system data/settings from the previous system. In other words, data left over from the old ROM is causing problems with the new ROM.
Sent from my SM-S767VL using Tapatalk
Click to expand...
Click to collapse
Hey thanks for replying but it seems like i cant even finish the setup. Therefore i cant load any files into my device. Any suggestions?

sunglassesman said:
Hey thanks for replying but it seems like i cant even finish the setup. Therefore i cant load any files into my device. Any suggestions?
Click to expand...
Click to collapse
Boot back into recovery, then factory reset, wipe cache and wipe dalvik cache, then reboot.
If that doesn't work, try booting back into recovery then flash the ROM then the Gapps then factory reset, wipe cache and wipe dalvik cache then reboot.
If that doesn't work, try booting back into recovery, then select the "Wipe" option, then choose the "advanced wipes" option, then choose the system partition, then swipe the slider at the bottom to run the wipe, then try flashing just the ROM but don't flash the Gapps, factory reset, wipe cache and wipe dalvik cache then reboot. After you get the device booted, you can delete the Gapps file then download a smaller package and put it in your phone's internal storage then boot back into recovery and select the "Install" option, at this point, you already have the ROM installed so no need to flash it again, but you do need to flash the new Gapps file, then factory reset, wipe cache and wipe dalvik cache.
Do you see how important it is to factory reset, wipe cache and wipe dalvik cache every time you flash? It is a vital step.
Sent from my SM-S767VL using Tapatalk

Hey thanks for all these but my device is using cwm right now so can you pls rewrite the instructions for me?
Also i cant finish the setup with all these popups so theres no way i can load files into it.
And yeah i guess i didnt wipe data or caches away after i finished flashing the files.
Thank you so much.