Related
I read as much as I can about installation of a custom ROM. I think I'm confident enough to do it now, but I just want someone to review these steps before I start.
I have a Rogers I896 currently running the stock froyo that I upgraded via Kies with a build 10.10.
Because this is on a build 10.10 I can't follow the steps vertabim with the guide in the android development forum.
1. Root with SuperOneClick
2. Titanium Backup
3. Use Odin3 v1.7 or later to restore to stock with this http://forum.xda-developers.com/showthread.php?t=905042 and the 512 pit file. (I understand this is unnecessary as I'm already stock, but in case I need to revert back to stock from a custom ROM, this is what I'll do)
4. Reroot with SuperOneClick
5. Get the ROM and put it in the root of the phone
6. Download ROM Manager and install Clockwork Recovery
7. Boot into recovery and install zip from SD card and choose the zip file that I downloaded.
8. Titanium Backup to restore
Please let me know if I'm missing something. I think I read something about Nandroid backup somewhere in the forums. I'm not exactly sure what that is and it didn't really say that in the guide. Should I do that and how do I perform that?
I'm thinking about installing either Paragon, Serendipity, or di11i. Perhaps someone can also maybe list some differences, issues, pros and cons about these ROMs.
Thanks in advance!
your steps are good enough for you to flash to a new rom.
You may have trouble with installing Clockwork. If you do, follow this link.
Also, once you reboot into clockwork, remember to do a backup of your current ROM and move it and your TiBu backups to your HD. Clearing your cache before you install your new ROM isn't a bad idea either
Goodluck!
Is clearing cache done in the clockwork recovery? I notice an option for "clear download cache" from Rom manager. Is that the same thing?
integrasaurus said:
You may have trouble with installing Clockwork. If you do, follow this link.
Also, once you reboot into clockwork, remember to do a backup of your current ROM and move it and your TiBu backups to your HD. Clearing your cache before you install your new ROM isn't a bad idea either
Goodluck!
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I896 using XDA App
likiud said:
Is clearing cache done in the clockwork recovery? I notice an option for "clear download cache" from Rom manager. Is that the same thing?
I do not think "clear cache" is necessary when you install a new rom, since most of rom will format the related partitions first. You can clear the dalvik cache in the cwm.
A master clear is recommended since it will reset your phone to factory default and delete all the data in your built-in sdcard.
Click to expand...
Click to collapse
mengbo said:
likiud said:
Is clearing cache done in the clockwork recovery? I notice an option for "clear download cache" from Rom manager. Is that the same thing?
I do not think "clear cache" is necessary when you install a new rom, since most of rom will format the related partitions first. You can clear the dalvik cache in the cwm.
A master clear is recommended since it will reset your phone to factory default and delete all the data in your built-in sdcard.
Click to expand...
Click to collapse
It doesn't hurt AFAIK. I do notice after restoring apps with TiBu some apps require you to clear their cache in order to work properly, so I do it as a preventative measure.
Another tip: do NOT restore all system data with TiBu after you flash!
Click to expand...
Click to collapse
I started on Rogers stock 2.2.
Used superoneclick to root. Installed rom manager. Used a script to modify my recovery 3e file. Rebooted into recovery. Flashed cwm. Installed my custom rom.
Pretty awesome.
Sent from my SGH-i896
Hey I don’t mean to hijack/bump the thread but I’ve got an I896 which I’m attempting to flash a custom ROM onto, but I’m a complete phone newbie and could use some assistance when it comes to clarifying some instructions. This thread seemed to be the most “laid out” instruction guide for the I896 which I could find.
Currently my phone is running 2.2 Froyo / I896UXJL1 / Kernel 2.6.32.9 which I got via Kies early January when the update was released by Rogers.
I downloaded SuperOneClick 1.7 and rooted it without problems, but that’s as far as I’m clear/comfortable.
1. Do I need to use Odin (http://forum.xda-developers.com/showthread.php?t=905042) to restore to stock? Since I’m on the default Rogers technically that is already stock, no? Can I simply continue on from where I am?
a. If I don’t need to use Odin, do I need to make a backup with titanium?
2. Does step 6 of the OP’s list simply involve hitting the “Flash ClockworkMod Recovery” option in ROM Manager v3.0.1.0?
3. After that is it simply a matter of downloading my ROM of choice (Serendipity 5.12) and putting the .zip into my root folder, booting into recovery via the “Reboot into Recovery” option in ROM Manager, and then selecting to install the ROM .zip file?
4. Is my above three points everything I need to know or is there anything else I should know/be considered?
Also, when rooting I simply turned USB debugging on, ran the two .exe’s in order and then hit root after plugging in my phone. Was I supposed to go into download mode or anything or is that only for other modes of rooting (I have superuser installed and titanium backup was able to get root access so I assume my phone rooted properly).
That being said, I’ve read a ton of threads and a ton of stickies but things tend to seem either old/outdated or focusing on the AT&T i897, with there being limited information on a newbie friendly “explain all” way from A to B for the i896, unless I missed it. Some mention rooting with X, and using path ABC to root/flash a custom rom, and others mention rooting with Z and using patch DEF to do the same; all of which have left me feeling uneasy about flashing. ><
I'd be more then happy to provide any information in which I may have left out, and would appreciate any help I can get as I'm more then enthusiastic about flashing my first custom ROM but would like have the knowledge to do it right instead of being left with a brick. Yes, I know it seems almost all "bricked" captivates are unbrickable, though I would prefer to avoid that road at all costs either way haha.
mengbo said:
Another tip: do NOT restore all system data with TiBu after you flash!
Click to expand...
Click to collapse
I'm curious to know why not to restore system data?
Is "missing apps with data" ok to restore?
Restoring system data messes things up. Restore "missing apps with data" only. no system data.
If you restore system+data your home screen will fill up with force closes faster than you can clear them out, I know this Because I did it...twice, this is where my aww.W.T.F? sig came from. Don't panic if this noobish brain fart happens to you, just re-flash the rom and only restore missing apps+data as studacris said and enjoy.
I deleted my Rom Manager in an attempt to refresh and install the pro version. I did this by using the force uninstall from TB, which actually did not remove it, but then I did remove it normaly via the TB remove app feature (not force uninstal). Now when I try install the rom, it will not load. I do not get any errors when I try to install it. It is just is not there / cant be seen by any app or in a directory. Any suggestions on how to fix this??? Are there any alternative apps???
Just fyi - I am also unable to install the latest CM7 version. It gets to the CM7 boot screen, but hangs on it ofr more than an hour with no progress. Just fro clarification, I have since reloaded the latest CM6 version, to see if Rom Manager would install, but it still wouldn't.
Current phone is a Sprint Hero, running the latest CM6 Version.
when you reloaded CM6, did you restore a backup or did you wipe everything and reload a fresh image?
I had a problem using ROM Mgr when I tried to flash the recovery. Ended up it wouldn't boot into recovery and after that it wouldn't flash the recovery anymore. I was able to flash the alternate ra recovery, wipe factory data/cache & davlik cache, reload clean CM6.1 with latest gapps. Still the ROM Mgr was goofy. I used the fix permissions tool in ROM Mgr and it finally allowed me to flash the CWM recovery (2.5.0.7) successfully and reboot into recovery mode. Maybe the fix permissions or making sure everything (besides your SD card) is wiped would help? Or, try using the ra recovery to load your CM7 image (not sure if that is supported).
diva64 said:
I deleted my Rom Manager in an attempt to refresh and install the pro version. I did this by using the force uninstall from TB, which actually did not remove it, but then I did remove it normaly via the TB remove app feature (not force uninstal). Now when I try install the rom, it will not load. I do not get any errors when I try to install it. It is just is not there / cant be seen by any app or in a directory. Any suggestions on how to fix this??? Are there any alternative apps???
Just fyi - I am also unable to install the latest CM7 version. It gets to the CM7 boot screen, but hangs on it ofr more than an hour with no progress. Just fro clarification, I have since reloaded the latest CM6 version, to see if Rom Manager would install, but it still wouldn't.
Current phone is a Sprint Hero, running the latest CM6 Version.
Click to expand...
Click to collapse
You need to do a full wipe of absolutely everything and then update your recovery image. Do a fresh download(try from a mirror) of the latest CM7 version. Make sure that everything is fully wiped and you wipe your system, cache, data and davlik-cache. Do the wipe TWICE.
Once you are flashing CM7, make sure you only flash the rom first and then boot up and see if it goes through.
Thanks for the info, Waffle_.. So to just clarify... I need to:
1. wipe everything twice
2. get a fresh download of cm7
3. then install cm7
What do you mean by "Once you are flashing CM7, make sure you only flash the rom first" -- Like make sure it boots up before installing anything else????
Thanks!
diva64 said:
Thanks for the info, Waffle_.. So to just clarify... I need to:
1. wipe everything twice
2. get a fresh download of cm7
3. then install cm7
What do you mean by "Once you are flashing CM7, make sure you only flash the rom first" -- Like make sure it boots up before installing anything else????
Thanks!
Click to expand...
Click to collapse
Yes.
Meaning, when you flash the rom, don't flash gapps or anything else. Flash the rom only, then reboot and make sure it runs. And then you can go back and flash gapps, etc.
Last night I was lurking in market and I realized there was some updates pending to apply including Superuser but I don't remember the other 3... there was a little bit strange because wasn't in another color like normal pending updates, so I enter in tne app page, push "update" button and the push "ok" button, this for every one...
Updates was downloaded but when was applying suddenly the nook reboot... well, try to reboot, but something goes wrong... boot starts ok, but when came to the outlined white "nook" and outlined raindow "color" stops drawing the "l", and reboot again and again.
Well, today I make a 2GB SD with ClockWorkMod 3.2.0.1, manualnooter-4-5-18.zip and manualnooter-4-6-16.zip like last time... first I apply MN4.5.18, but when reboot happens the same thing... then I apply MN4.6.16 and the same thing happens...
So, anybody figured has idea what is going wrong and what I have to do to fixit???
Thanks a lot
Try this
Had the same problem this morning and found this thread. It worked for me but now need to reinstall Flash. http://forum.xda-developers.com/showthread.php?t=1208896
Same issue - flash zip fix didn't work for me
fealuin, did the flash zip work for you?
I got the flash update today, rebooted and hit the same problem where it's looping on the colo... Before I read this thread I tried reapplying the copies of manualnooter 4.5.18 & 4.6.16 I had with no luck.
I've tried the flash zip, reapplying the manualnooters, clearing cache & davlik cache, but apart from taking longer on the initial boot before looping, it keeps doing the same thing.
I had just installed and run nsr (nook screen recalibrate), which automatically rebooted, but I don't know if that could be an additional cause.
At this rate I'm close to wiping and starting from scratch, but I'd welcome any suggestions. About to go on vacation, and I was in the middle of a book...
Thanks.
Same thing happened to me when I uninstalled ad free and tried a new app of the same likeness. Had to flash to a backup
dadmarshall said:
Had the same problem this morning and found this thread. It worked for me but now need to reinstall Flash. http://forum.xda-developers.com/showthread.php?t=1208896
Click to expand...
Click to collapse
Worked for me. Thanks to GMPOWR's solution
deadermeat said:
fealuin, did the flash zip work for you?
Click to expand...
Click to collapse
Nope.
My nook color is underpower... I just put it to charge but the original cable is damaged, so I use a standard cable to charging and is pretty much slow than original cable...
I hope in about 1 hour have enough charge... I will be reporting
Well... it works... market return to an old version so I reapply mn 4.6.18... all looks like work fine
Sent from my NOOKcolor using XDA App
this is exactly what just happened to me. flash update didn't work either.
Today by mistake i updated adobe flash player to version 11, since then it stuck in boot looping, i tried to flash the zip file many a times but no success. it still in boot loop. please let us know is there other way to delete the flash player except adb as it dose not work for me.
Flash shouldn't have anything to do with booting up. How exactly did you update it, the market, adb?
+1 here. Tried flash fix zip, and recovery fix zip,...nada. I had the updates hit last night, borked my nook, and today I'm attempting a cure. Just about ready to revert to stock and start again.
Anybody found anything yet?
I have no problem with updating or using Flash 11.
Maybe I'm lucky.
sym1 said:
+1 here. Tried flash fix zip, and recovery fix zip,...nada. I had the updates hit last night, borked my nook, and today I'm attempting a cure. Just about ready to revert to stock and start again.
Anybody found anything yet?
Click to expand...
Click to collapse
Not sure if you can fix it if its already doing the boot loop, but I was able to prevent it from happening by using the instructions posted. Uninstall flash and air with titanium backup and then load the flash.zip with cwm and you should be able to then update flash through the market without boot looping. To get the market working, I did a data wipe of the market app using titanium backup.
votinh said:
I have no problem with updating or using Flash 11.
Maybe I'm lucky.
Click to expand...
Click to collapse
I don't have any issues with it either......
I have the same problem. Stock rooted. Updated superuser, noticed I had an update to abobe air installed. When I rebooted I got stuck in this loop.
I tried flash fix, but it did nothing.
so is the only fix to wipe and re-install everything?
bullfrog527 said:
so is the only fix to wipe and re-install everything?
Click to expand...
Click to collapse
That's what I had to do the first time it auto updated flash as I couldn't figure it out (and the flash fix wasn't out). I made sure to turn off auto updated for flash after that and I installed Titanium Backup so I wouldn't have to remember all the apps I wanted. I managed to get the new market working by data wiping the market app, but this turned on auto updating again. Luckily, now there is a way to avoid the bootloop if it auto installs flash. You just have to make sure to remove the updated flash and air using titanium BEFORE you reboot, or you'll get stuck in the bootloop again. I know, that doesn't help you now, but once you run the fix, you should be able to safely update flash. If it happens again, you'll have titanium backup so it'll be easy to restore. As I have all of the root and flash fix files loaded on my SD card along with CWM, I could restore my nook to it's current state in about 10 minutes if it were to get stuck again, but hopefully that won't happen.
I had the same problem. I even flash with stock 1.1 and it did not work. Somehow I think I get rid of ROM manager after that and I can restore to stock 1.2 after 8 un-successful reboot.
repair path?
so in order to fix this issue I must
1. in CWM wipe all and re-flash stock 1.2
2. update to 1.3,
3. run MN 4.5.18 and then 4.6.16a
4. download TB from market
5. uninstall Adobe Flash and Adobe AIR
6. Flash "Adobe Fix"
7. RE-install Adobe Flash and AIR
Is this the way to go?
bullfrog527 said:
so in order to fix this issue I must
1. in CWM wipe all and re-flash stock 1.2
2. update to 1.3,
3. run MN 4.5.18 and then 4.6.16a
4. download TB from market
5. uninstall Adobe Flash and Adobe AIR
6. Flash "Adobe Fix"
7. RE-install Adobe Flash and AIR
Is this the way to go?
Click to expand...
Click to collapse
Thats what worked for me, though my sequence may have been a little different (I updated to 1.3 with an already rooted 1.2).
Hi
I'm experiencing these issues during last days:
-Market doesn't download or actualize nothing (Error 492)
-Phone shuts off randomly
-I cannot load CWM recovery
These are my phone specifications:
-V20o Official Leaked Rom
-Horsepower extreme 24BPP RC11 Kernel
-Hp v20o tweaks
-Fast Dormancy Logging fix
-Scrolling Cache Disabler for smoother scrolling
-CWM Touch Custom Recovery installed flashing a zip encountered on xda
I'm experiencing these problems after I installed CM9 beta-rom (and the proper google apps) and then I went back to the V20o doing three wipes and restoring a previous Nandroid Backup
Any suggestion?
Thanks
The problem is I think touch recovery. It contains a bug when your wiping cache. The problem is that after wiping it, it won't rebuild, so this will crash your market and may also cause the other problems.
What you could do is change your recovery.
Thank you very much
So I should not wipe cache when i run a Nandroid restore?
I ask you this 'cause when, after installing CM9 (doing three wipes procedure), i rebooted into recovery to restore Nandroid backup and it seemed to work well. I began to experience problems when I loaded Rom after it.
Anyway is there any chance to reinstall old version CWM without reinstalling the Rom?
scompiani said:
Thank you very much
So I should not wipe cache when i run a Nandroid restore?
I ask you this 'cause when, after installing CM9 (doing three wipes procedure), i rebooted into recovery to restore Nandroid backup and it seemed to work well. I began to experience problems when I loaded Rom after it.
Anyway is there any chance to reinstall old version CWM without reinstalling the Rom?
Click to expand...
Click to collapse
The problem occurs after every cache wipe, because it should rebuild after every wipe and that's the problem.
The easiest way to reinstall a CWM version is using ROM Manager and restore to CWM version 5.0.2.0. I know it's kinda old, but it'll do good enough.
EDIT: If you for some reason really don't like CWM 5.0.2.0, look at this thread: http://forum.xda-developers.com/showthread.php?t=1478995
You can find a flashable zip somewhere of CWM 5.0.2.7
Touch Recovery i had was flashed from that .zip file you're telling me! Anyway i tried to install old CWM version in Rom Manager but it didn't resolve the problem.
I will manage to reinstall everything.
So I created a backup using the PhilZ bootloader. Then I restored the original firmware using odin because I needed to get the original gallery app. Now I'm trying to restore the backup, but I'm having problems. The first time I tried I got an error asking me to select a backup account or something. I did it again, this time doing a full wipe (with preload and everything) and then wiping cache and dalvik cache. I am still having problems however. Gmail doesn't stay open, trying to open the settings force closes touchwiz, and the phone and messaging apps have disappeared. Any ideas what's going on or how I can fix this? Anything I can do to give you guys more detail?
Philz is philz and odin is odin
Sent from my GT-N7000 using xda premium
So that's it then? Back to square one? If so, ok, but I'd rather not.