So I was able to successfully install CM7 on my new NC last week and got it just the way I want it. Now I would like to try Miui. I have never used Rom Manager (not working on the Epic), and would like to know how to go back and forth using that app.
Can someone break it down so I can follow along painlessly?
ROM manager is nice for doing incremental updates. What you want to know how to use is clockwork mod.
I'm in the car ATM, but I'll be at my computer in 15 or so. I'll write up what you need.
Sent from my Vortex using Tapatalk pro
OK, first turn on wifi. Then, from within Rom manager check and make sure you have the latest Clockworkmod flashed.
at the top it will say 'current recovery' if that's 3.2.0.1 then you're good, if not, select 'flash Clockworkmod'
if you get a selection between old and new, select new.
Now would be a good time to make a directory on your SD-card called 'ZIPS' and put the .zip files of whatever rom you want to flash.
CM7 nightlies
MIUI
And, you'll want to pickup the Gapps (google applications) zip from here
Clockworkmod is a recovery program. It is able to boot ahead of anything else and has access to every partition. From within clockwork mod you're able to do system level backing up, restoring, or just plan changing. I'll give you the run down on flashing different roms.
To boot Clockworkmod just turn off the nook, then hold the [pwr]+['n' button] until you see the text 'booting into recovery' release the buttons.
Now within clockworkmod [vol+] is up, [vol-] is down, ['n' button] is select, and [pwr] is back.
First we need to backup your current data. With this backup you will be able to restore to that EXACT time and setup. Make as many as you want, feel free to rename then to keep track.
->backup and restore->Backup
The backup is saved to the SD-card in the Clockworkmod folder
Then we need to wipe all that uncool old data from the emmc. Pick one, not both.
Scenario #1: upgrading versions of the SAME ROM
->mounts and storage->unmount /cache
->mounts and storage->format /cache
->advanced->wipe dalvik cache
Scenario #2: SWITCHING from one type of ROM to another
->mounts and storage->unmount /cache
->mounts and storage->format /cache
->mounts and storage->format /data
->mounts and storage->format /system
->advanced->wipe dalvik cache
->wipe data/factory reset (a little redundant, but it can't hurt)
Now to install the new ROM or ROM version
->install zip from sdcard->choose zip from sdcard->ZIPS/->ROM file
->install zip from sdcard->choose zip from sdcard->ZIPS/->Gapps file (should look something like this: gapps-gb-20110613-siged.zip)
After you've installed a new update of a ROM or a new ROM you'll have to fix the permissions.
->advanced->fix permissions
Reboot and you're done.
This should cover all of your flashing needs. If I missed something please point it out. If something doesn't work just post it, someone will know.
Awesome breakdown! Now to get apps back, do I need to use titanium or can I go to restore in CWM and do it that way?
Thanks again, that was very useful!
I seem to remember that titanium backup's app data restore does not work for CM7, only restoring the app itself works.
The restore in CWM will REVERT you back to when you backed up, undoing everything you've done since.
I can confirm that Titanium backup does work in CM7 I use it all the time to restore apps and data.
It also worked after I installed Miui. Batch restored all of my apps and data, no FC's.
Glad to hear it worked ok for you.
Related
As rooting has become so easy these days I am considering to try custom roms (as many hv done lately). I hv read alot since the root with unlocking the bootloader method came out. I am still on stock FRF91 and I'd like to keep my apps and data intact. CM6-RC3 has just released and I m so tempted to try!
Here is the proposed routine:
"Originally Posted by cicrockets"
0. Download the CM6-RC3 ROM with the gapps and put them on SD Card.
1. Plug in the power cable and root using the 1-click root.
2. Back up apps and data with Titanium Backup / MyBackupPro (which is better?)
3. Search for ROM Manager on Market and Install
4. Click the "Flash ClockworkMod Recovery" and wait until the progress bar is finished.
5. Reboot and do a Nandroid backup.
6. Open ROM Manager and "Install ROM from SD Card".
7. Add Zip:
i) update-cm-6.0.0-N1-RC3-signed.zip
ii) gapps-hdpi-20100814-signed.zip
8. When it prompts, choose to backup before flashing and give the backup a name like "Stock N1 Rooted". Also choose to clear data and dalvik-cache.
9. Wait. It'll reboot and go into the clockwork recovery and automatically queue and flash the two zips. Keep waiting until it reboots again.
At this point the phone should hv booted into CM6. Should I do the restore from the backup apps immediately? Or should I wait for 10-15min market sync?
My major concern will be the data. Is there any problem with the above routine? Please bear with me
Technically that is the way to do it. But some people say that they get issues when restoring titanium backups for certain apps and data. So keep that in mind.
Yeah I read about that too. They said it can be fixed by doing an advanced restore, right? Will u recommend MyBackUpPro instead?
Thanks!
I rooted my hero using the 1 click root from the market. I then used rom manager to make a back up image, then flashed cyanogenmod 7.0.2 on it. There was no Market, my home button didnt work, and a few other quirks so I decided to go back to my original os. I clicked on the manage and restore in rom manager. It went thru the process and said restore complete. when it boots up it has overlayed images, and says "the application Settings(process.com.android.settings)has stopped unexpectedly.FC. As i go thru the set up, many of they options are greyed out and not accessable, then when i get to "finish setup" it FC's and says" the application Setup(process.com.htc.android.htcsetupwizard)has stopped unexpectedly. Then i get a black screen. Just wondering if I can get a good Back up image from someone to put on my sd card, then do a restore? I am pretty noob at all this, so any help would be greatly appreciated!!!!!
Mmhmm...first, 1 click bad, second, rom manager...worse in the wrong hands...
Why don't you download the gapps and put it on the root of your sdcard and then flash it after the 7.0.2 and then you'll be ok I'm sure if you take a little time to figure out you may be the only person that can fix your issue. By that, what I mean is in the install steps I'd bet it mentions to install gapps and if it doesn't let me know and I'll get the op to add that step.
As for all your messed up permissions try running fix permissions in rom manager if you can get there.
~maybe I set it too high...
i tried that first but coulnt get it to work, so i downloaded the rom directly from rom manager. The only thing i can do on the phone now is thru clockworkMod recovery
You can do fix permission in cwm also, I think under advanced. Just whatever you do, do NOT format recovery or misc if those options are in your recovery.
If you're in recovery though you're in the right place to flash. It's just
Wipe data /factory reset
Advanced -> wipe dalvik cache
Back
Install zip from sdcard and choose the7.0.2 zip and then thesame thing with gapps.
Reboot system
Edit, you could also just try to restore again from cwm. I'm assuming it holds the backup.
~maybe I set it too high...
ok, im off to bed...i will try this in the morning and post my status, thanks for your help so far
Did you ever wipe between installations and flashes? I always play it safe and wipe boot, cache, data, system and dalvik cache when I am flashing different ROMs and when restoring. Try going back into recovery and wipe what I posted and then restore your backup.
Sent from my HERO200 using XDA Premium App
I couldnt wait, I had to try it....YOU ARE ABSOLUTELY AWESOME!!!!!!!!!!!! Thank you so very much. I already had Rocksteady and Gapps downloaded on my comp, so i put those on the sd, followed your steps and BAMM! Works great! I can not thank you enough!
Can anyone please help?
I just installed the Ultimate JB ROM XXLSA 4.1.2 v5 upgrade on top of v4.
All went perfectly well and I was able to enter all my setup and account details after the initial boot of the phone.
When I tried to re-install apps from Google Play, however, (Titanium Backup Pro, Quickboot) the phone hangs at the Samsung Splash screen and won't go any further. I re-tried the procedure 3 times but each time the result is the same.
Can anyone tell me what the problem could be? I followed all the instructions about wiping etc. correctly.
Trevor
v4 and v5 use completely different bases (LS7 and LSA).
I would save everything to my ext SD card.
Then goto Settings > Backup & Restore > Factory Reset (don't click on format external sd card).
Your phone will restart and do some crazy things. Then restart again.
When you get to the welcome page, or bootloop... take the battery out (its safe).
Then hold Vol Up, Home and Power (let go of Power after ~5-15sec) and goto recovery.
In recovery, wipe cache.
Then format data.
Then format system.
Then format cache.
Then wipe Dalvik cache.
Then install the v5 zip.
It shouldn't restart automatically, but it might, don't worry let it.
Now you should have a fully, fresh, clean install of v5.
Connect to your wifi, go through the start up.
Goto SuperSU and update binary.
Goto Play Store and install TiBu.
Open TiBu and grant it root access.
Close TiBu.
Connect phone to PC, then copy your TitaniumBackup folder into your sdcard directory.
Open TiBU and now, it will see your previous saves.
Restore your apps + data.
Presto! No bootlooping and no App FC !
Thanks for going to all the trouble to write all that out.
I followed the instructions to the letter but no, same result I'm afraid: it worked fine but as soon as I installed Titanium and granted root access, it asked me to choose to restore the original phone ID which I did. The phone rebooted but then wouldn't go past the "Samsung Galaxy Note Gt-N7000" screen.
I have no choice but to restore from my Nandroid backup. This is really p****ng me off but at least I can restore v4 easily.
Thanks again
Trevor
Kangal said:
v4 and v5 use completely different bases (LS7 and LSA).
I would save everything to my ext SD card.
Then goto Settings > Backup & Restore > Factory Reset (don't click on format external sd card).
Your phone will restart and do some crazy things. Then restart again.
When you get to the welcome page, or bootloop... take the battery out (its safe).
Then hold Vol Up, Home and Power (let go of Power after ~5-15sec) and goto recovery.
In recovery, wipe cache.
Then format data.
Then format system.
Then format cache.
Then wipe Dalvik cache.
Then install the v5 zip.
It shouldn't restart automatically, but it might, don't worry let it.
Now you should have a fully, fresh, clean install of v5.
Connect to your wifi, go through the start up.
Goto SuperSU and update binary.
Goto Play Store and install TiBu.
Open TiBu and grant it root access.
Close TiBu.
Connect phone to PC, then copy your TitaniumBackup folder into your sdcard directory.
Open TiBU and now, it will see your previous saves.
Restore your apps + data.
Presto! No bootlooping and no App FC !
Click to expand...
Click to collapse
Mystery solved - well partly. Turns out Titanium Backup Pro was causing it on my phone for some reason. This was naturally the first app I wanted to install so I could restore apps one by one from the Nandroid backup. I tried Quickboot too which also caused the same problem so because TB and then QB did the same thing I assumed every app was going to cause trouble. Shouldn't jump to conclusions, I know.
I have JB Ultimate XXSLA v5 installed and am restoring my apps one at a time from Google Play and making new Nandroid backups as I go along.
And now I just tried installing TB free version - the phone boots normally! Then I installed the TB Pro version and again the phone boots normally. When TB was the first app I installed after the ROM upgrade it hung up the phone every time on 6 attempts. I'll try re-installing Quickboot now and see what happens. Conclusion: I must have been doing something in the wrong sequence but can's see what.
Many thanks for your help.
Trevor
sacentre said:
Thanks for going to all the trouble to write all that out.
I followed the instructions to the letter but no, same result I'm afraid: it worked fine but as soon as I installed Titanium and granted root access, it asked me to choose to restore the original phone ID which I did. The phone rebooted but then wouldn't go past the "Samsung Galaxy Note Gt-N7000" screen.
I have no choice but to restore from my Nandroid backup. This is really p****ng me off but at least I can restore v4 easily.
Thanks again
Trevor
Click to expand...
Click to collapse
Tried ROM Manager backup of factory ROM.
Now, I power on and get CWM recovery. Choosing reboot always returns me
to CWM recov. I read every thread in this forum that refers to
loop, brick, etc. I have various backups, but I don't know what they
are worth, best way to use them. How to get out of the boot loop?
Best outcome would be to recover my last stable state. Factory reset
would be ok. Hardbrick would be a drag.
* Bought factory unlocked G-ST6500D (no vendor) in Spain.
* Have current non-root backups of contacts, sms, media, calendar, etc. on
laptop.
* Installed CWM v5.0.2.8 with Odin (three yellow boxes appeared in odin,
FWIW), and rooted. Froze bloatware listed by some people as safe, but
did not delete any factory installed software.
* Wanted to have a stock ROM backup before I did anything else. It's
not clear to me whether it is best/possible to download one or create
an image from my device. Started reading/trying backup apps, but I
don't really know what each one does.
* Did a full backup, apps + data, to extSD, and copy to laptop with Titanium
backup (free). This wrote >1000 files.
* Did most complete (as best I could tell) backup to extSD and laptop
with Online Nandroid app. This wrote boot.img, cache.ext4.tar,
data.ext4.tar, nandroid.md5, recovery.img, system.ext4.tar. Can these
be used to restore ?
* Tried to backup the ROM with ROM Manager app, but could not find an
option to backup to ext SD, only int SD. There was only 200MB free, so
I knew this would fail. I choose this anyway, hoping it would realize
there is not enough space and offer to change the path. The phone
rebooted into CWM and began a backup. After a few minutes, it printed
an error message and told me where a log was written, and rebooted
into CWM recovery. I tried rebooting, holding buttons, removing
battery, etc. Always returns to CWM recovery. Tried the 'backup and
restore' menu hoping it would give info on the backup. Instead, it
immediately started another backup, this time showing 1GB intSD
free. This backup reported success, then reboot into CWM recov.
* Since then, from CWM, I did 'wipe cache partition' and 'wipe davlik
cache'. Did not yet try factory reset.
* Show log ends with
"skipping exectuion of extendedcommand, file not found"
I read that sometimes it is possible to exit a boot loop without
flashing anything. If that is not possible, I guess I should do
factory reset. If that does not work, then I guess I should try
restoring something somehow: Use CWM recovery to recover nandroid
backup from extSD? Or install something via Odin ? For any solutions,
I am more comfortable doing things from linux than MSWin, but I think
that is not possible. Do I have to race to solve this before the
battery runs out?
Thank you for reading.
just install cwm 6.0.3.3 b2 from TheWhisps goo.im account and then should everything work fine.
midzan21 said:
just install cwm 6.0.3.3 b2 from TheWhisps goo.im account and then should everything work fine.
Click to expand...
Click to collapse
Thanks. I just figured that out after a several hours of reading. Finally saw stories on the thread
introducing CWM 6.0.3.3 of people who never flashed a ROM and still had boot loops.
I was on the wrong track because I assumed it was the filled up int. SD causing the
problem. I still have to fix that, but my phone is running. It would be nice if ROM Manager or CWM calculated the space
needed and refused to start if insufficient. But, I understand that there are few good devs and much to do.
So I rooted my phone and flashedTWRP. What's my next step to flashing TEKXodus?
I'm confused about steps on the guide on XDA.
Do I just go into recovery and install the whole .zip file? Or do I install individuals mods?
Thank you.
Make sure you download the correct version depending on if you have 910T or 910T3.
Follow the steps in this thread for rooting and installing TWRP:
910T:
http://forum.xda-developers.com/not...sy-steps-stock-odin-n910tuvu1anih-cf-t2903733
910T3:
http://forum.xda-developers.com/not...y-steps-n910t3-dofc-dog1-how-to-root-t3177225
MAKE A BACKUP OF YOUR CURRENT STOCK ROM WITH ROOT!!! Can not stress this enough. If you need to go back to stock, and you download an Odin file from a shady site, you have no idea what you're putting on your phone. It's sooo much easier to just backup your stock. Make sure ALL options are checked under backup. Save this file on your PC or external SD card just to be safe. I always keep a backup copy on my PC.
Put the ROM zip file on your phone, either internal or external SD card. Some recommend internal SD only, but I have had 0 issues flashing from an external SD card. I guess if you use a cheap card you may have issues, but if you have a name brand class 10 you should be fine.
Do a full wipe.... When you are in TWRP, choose wipe, then factory reset. Then goto advanced and check system and data and wipe again.
In TWRP choose install then navigate to the folder that has the ROM zip file... and install.
Do another factory reset wipe (do not wipe system this time, just goto the wipe screen, and default swipe is factory reset.
Boot your phone, and LEAVE IT ALONE. First boot will take a LONG time. 10 to 15 minutes sometimes. Once you get to the setup screen... LET IT SIT for another 5 or 1 0 minutes.
Complete your setup process as you normally would do. There will be a popup saying it needs to reboot to complete some actions. Go ahead and reboot.
Once everything is installed and working as it should you can continue on.
Keep in mind there are some mods that come pre-attached to the TEKXodus rom. To flash these, boot into recovery, goto Mount -> check SYSTEM. Goto Install, select "Up a folder" to get to the root folder, then goto System then Mods. There you can play around with different mods. The Note 5 screen off memo.apk will just need to be installed like you would a normal downloaded APK and is not flashed. You only flash the .zip files.
BEFORE YOU START MESSING WITH DPI settings (if that's your thing) make sure you do a backup first. Some DPI settings will cause force close on touchwiz, and you'll be stuck unless you use another launcher. Basically before you install Xposed, any Xposed module, or play around with the build.prop file make a backup first. Can NOT stress this enough. I'm constantly tweaking things, and will make a backup every 3 days just out of habit. Delete your previous backup after creating a new one as the files are quite large (5GB+ depending on what you have installed). ALWAYS keep your stock backup that you originally made.
I do not recommend using the TEKXodus Rom's Tweaks for changing DPI settings. This basically just edits the build.prop and makes a global DPI change. There are SEVERAL samsung apps that need to be changed back to 640 DPI (the stock setting) or they will force close. It is MUCH better to install the Xposed framework, and then install the "App Settings" module and change the DPI on a per app basis. Personally I changed "System UI" only (not android system) to 420DPI. This will give you a smaller notification bar but not mess with alot of the other apps. You can then change the DPI settings using App Settings on a per apk basis. Some I like at 420, some at 480, some even in the 300s. After changing a setting you will have to reboot to see the change. You used to be able to just kill the app and then re-open but that doesn't seem to work anymore.
If you DO decide to change the global DPI setting, MAKE SURE you install xposed and App Settings first, then read this thread to change all the nescessary apps back to 640 stock DPI or you will have issues.
http://forum.xda-developers.com/not...anging-note-4-dpi-settings-to-change-t2923408
If you need anything clarified let me know, typed this up in a bit of a rush at work.
Don't forget to hit that Thanks button if I helped
So I followed the instructions above, however, after the flash I just hit reboot instead of doing another factory reset wipe and the phone never booted after the reboot. So I went back into TWRP and restored.
What did I do wrong? Was it just the fact that I didn't do the factory reset after installing the new ROM?
More than likely yes that's what caused the error.
Do this just to be safe.
Boot into TWRP.
Do a FULL wipe (advanced wipe) and wipe System, Data, Cache, Dalvik, etc)
Re-Install TEKXodus
Do a "Factory Reset Wipe" BEFORE booting. Literally as soon as it gets done flashing, goto TWRP wipe, and just do the default factory reset (do not wipe system this time)
Then you can reboot.
The error I end up with was the kernal is not seandroid error. I'm guessing I picked the wrong ROM install?