• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Frequent Reboots

clonellw

Lurker
Every ICS and JB ROM I have installed on my OV produces frequent reboots. I have not yet tried previous ROM versions. I am new to rooting so I may be making a simple mistake in the installation process. The general procedure I have been using is as follows.

  1. Download ROM and gapps (if required)
  2. Check MD5 sums
  3. Backup using Titanium Backup
  4. Boot into recovery (Bobzhome CWM)
  5. Backup
  6. Wipe data/factory reset
  7. Format /boot and /system
  8. Wipe Dalvik Cache
  9. Install ROM ZIP and gapps ZIP
  10. Reboot system
The reboots begin in initial phone setup and occur randomly thereafter in all areas of the system (apps, settings, contacts, camera, browser, you name it). I have tried Fix Permissions, re-wiping the Dalvik cache, re-flashing the ROM, multiple manual reboots.


Any suggestions?
 
Do you check md5 after it is on the SD card?

I wipe, then individually format everything EXCEPT the SD card. Then flash ROM and gapps and reboot. You also may want to not restore your Ti backup. Problems can be had restoring apps from a different system.
 
1. ROM installation instructions: Now you need to do all these things(this must be done when installing a new ROM) from the recovery.
A. wipe data/factory reset
B. wipe cache partition.
C. wipe dalvik cache(advanced section)
Now that your rooted, YOU MUST NEVER USE THE FACTORY RESET IN THE PRIVACY MENU ON THE PHONE . This will mess up your phone and require a PC and much gnashing of your teeth, and possible loss of some system functionality.
D. go to mounts and storage. Select format boot,system,data,and cache
E. go to install zip from sd card
F. go to select zip from sd card, select the Gingerbread ROM.zip that you put on the root of the sd card. When done go back and select the gapps if needed. When done hit the back button once.
G.,When all this is done select reboot system now.
( for Froyo ROM's just install the ROM, thats all. You don't need the Gapps)

9. It will take 5-10min.for the initial reboot. If you installed a Gingerbread ROM you will be asked to sign in,skip all this.

Now you can go to the market app and click on it and sign in to your google account (you must have your e-mail address and log in code). Reboot the phone twice then go back to the market and download the app you used to backup your apps. Restore your apps. Set up your apps. Once you get everything set up just the way you like it and all your apps are just where you want them,go back into your recovery and make a backup of that ROM. You can now delete the first backup if you need to (you might keep it if you ever need to revert back to stock to sell the phone).

WARNING: Do not restore system data from a backup. Do not restore apps from your backups that are already included in the new ROM (you can restore app data). This will cause force closure issues and can corrupt the ROM.

NOTE: ROM's that are in the Alpha and Beta stage will have some problems, this can be lessened with
a thorough wipe and format so there will be no residual data left behind to corrupt the ROM. You can also download and put on the sd card obijohn's update_wiper_1.3.zip. When flashed before the ROM & Gaps it will wipe a little deeper. It can be found in the All Things Root Guide sticky (Tools & Utilities sections).
Also before installing a theme or anything else, reboot the phone several times (give it 5 min. powered up in between reboots). This will help tighten the ROM up.

ICS and Jellybean ROM's don't like to be overclocked, if your overclocking them this will cause them to auto reboot or freeze.

The best ICS ROM that I know of is: Paranoid Android, which will allow you to overclock a little.
 
AndyOpie, thank you for taking time to give me a detailed response. I re-installed BobZhome's CM10 09152012 Build yesterday and changed the I/O Scheduler to DEADLINE. I also changed the Minimum CPU Frequency to 480 MHz. It has run extremely well without random reboots. I don't think changing the Minimum CPU Frequency has anything to do with the stable run I've seen. What are your thoughts?

D. go to mounts and storage. Select format boot,system,data,and cache
The wipe data/factory reset option indicates that it formats /data and /cache. Is that less thorough than the format in the mounts and storage menu?

Also before installing a theme or anything else, reboot the phone several times (give it 5 min. powered up in between reboots). This will help tighten the ROM up.
I have not read any source code or white papers yet - just checking out ROMs so far. Why wait? Does the Android system software perform "auto tuning" or does it take a few minutes for all the configuration settings to be fully applied?

One more question: Do you recommend multiple reboots (with the waits in between) after all flashes or just system flashes?

Thanks again!
 
The wipe data/factory reset option just wipes all user data from the ROM.

The cache partition, boot partition, system partition, and data partition's of the phone still need to be wiped (this is what formatting them does).

The Dalvik cache is part of the ROM, which theoretically shouldn't need to be wiped after formatting the system partiton, but I do it anyway (kind of an OCD thing I guess).

Recovery's for android phones aren't perfect when it comes to completely wiping all data (something to do with how they are scripted to operate I guess), so we need to give them all the help we can get. This is why I also mentioned obijohn's wiper zip which I use before every ROM install.

As an example: If you used the Xionia recovery on a Froyo ROM it works fine because the Froyo ROM's are not as sensitive to residual data. You use the same recovery on an ICS ROM like the one you installed and you would have to wipe and format every option three times to keep from getting any residual data left behind that might corrupt the ROM.

Residual data is the killer of all the CM7, CM9, and CM10 ROM's. If you adopt a clean freak attitude before a ROM install you will experience a lot less problems with the ROM's you install.

The min CPU setting is where the CPU idles at. If you only have the ROM set for 600MHz max then you don't need the min to be so high.

With all CM7 ROM's the best settings for performance/battery off charge times is: 480MHz min (if set any higher the CPU will get hot and the battery will drain faster), 768MHz max, using the Interactive (interactive X if available) governor (this tells the CPU when and how to apply your CPU settings).
The CM9 and CM10 ROM's don't like to have the CPU settings messed with except maybe to change the governor. The exception to this seems to be the Paranoid Android ROM.

This is where your phone should be at as a default. When you need to do other tasks then you can change the settings, remembering to change them back when done.

The reboots I mentioned are for new ROM's, updates to ROM's, kernels, and themes.

My LG Optimus V is 1 and 1/2 years old because of my following these basic principals. It has not showed any signs of giving up, even after having to use it as my only source of internet browsing (helping out in the forums mostly) with the screen on for more than 6 hours at a time for several months at a time.

NOTE: I also never turn the power off unless I need to go into the recovery (I always turn the screen off when not using it). I used to work on 14 different Avionics systems on a Jet Aircraft while in the Marine Corps, so I learned that turning things on and off a lot can hasten there demise (something to do with the power surge/spike produced from turning them on and off).
 
Thank you, AndyOpie150! I have been a programmer for 28 years and hope to have time to contribute to the great efforts being made in ROM development. I really like the openness and cooperation in the dev community; I have seen nothing but patience and willingness to share.
 
Last year I didn't know squat about Android Phones and just barely knew enough to be able to surf the web on a computer (first computer was purchased the year before).

Everything I learned was from trial and error and the big three in Android Forums.
1. Android Forums
2. Android Central
3. XDA-Developers

Now I have a killer ROM (three other members and I took apart two ROMs and made one that is pretty cool) and Ubuntu 12.04 sharing half my hard drive with Windows XP service pack 3.

You can teach and old dog new tricks (50 next year).
 
GoCrew, I just saw your post!

Thanks for the tip on Titanium. I have been wondering if cross-version restores are safe. I remember reading something about a migration feature in Titanium Backup, but I cannot find it in Preferences. I have restored SMS messages and Call Logs without incident, but it was in the same ROM version. I have seen different opinions on restoring system data (data only) across versions. What is your take?

I have been checking MD5 sums, when available.
 
I have not restored apps or app data. Nothing is critical on my phone. I don't even back up SMS. I just start fresh every time by downloads via play store.

I don't see why SMS restore would be an issue if using the stock app. I've never seen the need to back up call log. If a number is important, it gets written down.

I would only advise app backup/restore if you were doing nightly flashes. I also would run a ROM "clean" for a few days before I would restore app data, and only app data. That will eliminate a potential source of your restart issue.

Have you played with speeds? Too high will make the system unstable. If you have, try a stress test to dial in your phones sweet spot.
 
When using titanium backup, only backup user apps and data. System apps/data is not to be transferred between ROMs. Your nandroid backup via custom recovery will backup everything. Also make sure you verify your nandroids.
 
When using titanium backup, only backup user apps and data. System apps/data is not to be transferred between ROMs. Your nandroid backup via custom recovery will backup everything. Also make sure you verify your nandroids.
Are you talking about MD5 checksums? If so, aren't those automatically verified as part of the restore process?
 
I have not restored apps or app data. Nothing is critical on my phone. I don't even back up SMS. I just start fresh every time by downloads via play store.
I agree with you there. When you think about it, all your important stuff (emails, contacts, calendars, etc.) are synced to your Google account. If you do have a bunch of important text messages, they could be backed up and restored with Titanium.
Have you played with speeds? Too high will make the system unstable. If you have, try a stress test to dial in your phones sweet spot.
I have tried a conservative, but larger than incremental, increase in CPU speed. It caused reboots and I had to restore my original settings, navigating with slow touchscreen movements to keep the CPU running low.
 
What screen do you have? The processor with Novatek screens apparently takes better to overclocking than the new ones do. I run mine at 806/420mhz on interactiveX and it is very stable. I was thinking of a new phone, but root/ROM/overclock makes me feel like I've got a new phone. When trying new settings just don't use 'set on boot' and you will be fine if you go a little overboard on your speed. A reboot will put you back to normal speeds.

After I create a nandroid backup via custom recovery, I always run the backup through Android File Verifier (in play store) to ensure that my backup is a-ok. I am unsure if your recovery would automatically verify said files.


Have you had any reboot problems since you followed the advice in this thread? What is your status on the original topic of the thread? AndyOpie150's advice is spot on. I learned to flash by following his instructions and I haven't had one bad experience (knock on wood). If you weren't insane on the overclock, I am guessing residual data from incomplete wipes was causing your issues.
 
What screen do you have?
I have the Hitachi screen.

After I create a nandroid backup via custom recovery, I always run the backup through Android File Verifier (in play store) to ensure that my backup is a-ok. I am unsure if your recovery would automatically verify said files.
Oh, I see. A message is displayed during restore that says "Checking MD5 checksums". I assumed the restore would terminate if the checksums were wrong, but it makes a lot more sense to verify the nandroid backup before you blow away what you backed up! I'll start doing that.

Have you had any reboot problems since you followed the advice in this thread?
My phone has been pretty stable since I made the suggested changes to my procedure and settings.

What is your status on the original topic of the thread?
The problem is definitely solved.

If you weren't insane on the overclock, I am guessing residual data from incomplete wipes was causing your issues.
I haven't tried any other ROMs since I got BobzHome's CM10 running stably. It doesn't have MMS, voice search, or reliable data, but it has been otherwise solid enough for daily use. I'm getting ready to give Paranoid Android a try on your recommendation. It sounds awesome. I'll let you know how it works out for me.

Thanks for checking up on my progress and giving me more solid info! :thumb:

Edit (10/2/2012):
I'm getting ready to give Paranoid Android a try on your recommendation. It sounds awesome. I'll let you know how it works out for me.
I was mistaken. It was AndyOpie150 who suggested I try Paranoid Android. I came in late and responded from memory of an earlier reading.
 
Back
Top Bottom