I am running the previous version of the GeeWiz Media ROM (I'm not sure of the version number, I did not find that info under About>Phone).
The newest version is "GEEWIZ MEDIA 4.5 SCH-I500 JDQ39 JELLY BEAN 4.2.2 ROM/KERNEL", and the reason I want to update is that it "Fixes issue with low headphone/headset output volume", a problem that I experience.
Can I do a dirty flash over the old one? There are three files in the download section. One is clearly a full wipe, but I am not sure which of the others I need to use for updating:
ODIN Compatible Downloads
GeeWiz Media 4.5 ROM/Kernel/Modem/Recovery/Data Wipe Full Update (ODIN)
This will delete all user data from your device, replace your RECOVERY with GeeWiz Recovery as well as replace your modem with the EH03 revision. Your data volumes will be formatted with EXT4 on the first boot
GeeWiz Media 4.5 ROM/Kernel (ODIN)
GeeWiz 2.9 Recovery (ODIN)Thank you for any pointers on this. I've only flashed once before (the current ROM), and the searching I've done on my question is not giving me a direct answer.
beebelo said:
I am running the previous version of the GeeWiz Media ROM (I'm not sure of the version number, I did not find that info under About>Phone).
The newest version is "GEEWIZ MEDIA 4.5 SCH-I500 JDQ39 JELLY BEAN 4.2.2 ROM/KERNEL", and the reason I want to update is that it "Fixes issue with low headphone/headset output volume", a problem that I experience.
Can I do a dirty flash over the old one? There are three files in the download section. One is clearly a full wipe, but I am not sure which of the others I need to use for updating:
ODIN Compatible Downloads
GeeWiz Media 4.5 ROM/Kernel/Modem/Recovery/Data Wipe Full Update (ODIN)
This will delete all user data from your device, replace your RECOVERY with GeeWiz Recovery as well as replace your modem with the EH03 revision. Your data volumes will be formatted with EXT4 on the first boot
GeeWiz Media 4.5 ROM/Kernel (ODIN)
GeeWiz 2.9 Recovery (ODIN)Thank you for any pointers on this. I've only flashed once before (the current ROM), and the searching I've done on my question is not giving me a direct answer.
Click to expand...
Click to collapse
there's a ClockworkMod/Geewiz recovery section that you can find GW 4.5 in. Download that (and the 4.5.2 patch), copy those to your phone's SD card, and then wipe data and update using the GW recovery
skepticmisfit said:
there's a ClockworkMod/Geewiz recovery section that you can find GW 4.5 in. Download that (and the 4.5.2 patch), copy those to your phone's SD card, and then wipe data and update using the GW recovery
Click to expand...
Click to collapse
I was staying away from that section because I used Odin and don't have ClockworkMod, and also don't know what Edify is because I didn't use it the first time (sorry!). Do I need to install ClockworkMod first?
Thank you for your assistance!
beebelo said:
I was staying away from that section because I used Odin and don't have ClockworkMod, and also don't know what Edify is because I didn't use it the first time (sorry!). Do I need to install ClockworkMod first?
Thank you for your assistance!
Click to expand...
Click to collapse
If your comfortable with odin use that, but you will still need to use the zip install if the 4.5.2 patch regardless of which method you go with.
If i remember correctly the previous GW had the 2.9 recovery, so you would not need to install if that's correct.
All the cwm and edify talk is nothing to get confused over,,, again since you are on the prior version you are go to install by either flashing the zip files or using odin.
A full wipe is not necessary but the benefit of formatting to the ext4 would be worth any extra effort to have the speed boost it offers.
hhp_211 said:
If your comfortable with odin use that, but you will still need to use the zip install if the 4.5.2 patch regardless of which method you go with.
Click to expand...
Click to collapse
Ok, thanks for that info; i would not have known that.
hhp_211 said:
If i remember correctly the previous GW had the 2.9 recovery, so you would not need to install if that's correct.
Click to expand...
Click to collapse
Yes I believe it did; I mean I am sure it had recovery, because I installed the "ROM/Kernel/Modem/Recovery/Data Wipe Full Update" the first time.
hhp_211 said:
A full wipe is not necessary but the benefit of formatting to the ext4 would be worth any extra effort to have the speed boost it offers.
Click to expand...
Click to collapse
I allowed the ext4 formatting the first time I installed
Thank you & wish me luck!
I haven't done my update yet because time has been limited and I don't want to start something and have it go wrong at midnight, in which case I'll be up all night...
More questions, but first, here is the ROM info so you know exactly what is on my Fascinate:
Android version: 4.2.2
Kernel version: [email protected] #1, Sun Mar31 23:32:20 EDT 2013
Build number: full_atlas-userdebug 4.2.2 JDQ39 20130403.103839 test-keys
Based on the above, do I need to install the recovery? (I would ask this in djp952's developer thread, but can't since I don't have enough posts).
As for the sequence of this process, is this right:
In Odin, install the GeeWiz Media 4.5 ROM/Kernel (ODIN) file, "geewiz-media-4.5-syskernel-20130913.tar.md5", without having to clear anything or wipe anything?
Next install the GeeWiz 2.9 Recovery (ODIN) file, "geewiz-recovery-2.9-20130305.tar.md5" -- if that is necessary.
OR can I put both of these files into ODIN at the same time?
Next copy the GeeWiz Media 4.5.2 Patch (EDIFY Update-Zip) to my SD card root, and install it by the other method (booting into recovery mode or whatever you call it)... I hate being ignorant, sorry!
The howto's I've read--the ones that have noob-oriented specifics--are instructing from the CWM perspective, and that's why I get kinda stressed out about this, since I'm not really sure and don't want to find out I made a bad assumption in the middle of the process.
A teenie bit of hand-holding will be immensely appreciated!
Well I did it and all seems well... and it's only 1AM.
1. I had frozen some Gapps with Titanium Backup. Thought it might be a good idea to unfreeze everything first.
2. Used Odin to install the System/Kernel tarball
3. Unplugged and replugged Odin and installed the Recovery(Odin) tarball
4. Rebooted twice just to be sure, but it seemed ready-to-use after the first bootup
5. Uploaded the update.zip patch file to the SD card root
6. Followed general instructions for installing SD card update.zip, to get the 4.5.2 patch on there.
Luckily there were no issues and I can go to sleep listening to music!
Related
I have used ODIN before to install the JI6 2.1 update but that left my data intact on the internal SDcard. So my question is the following as I'm about to flash a new ROM and kernel using ROM manager for the very first time (and from my point of view, flashing with ODIN has been a child's play versus with ROM manager):
Question #1: How do you wipe and when? Do you wipe before you flash the new ROM/kernel or after? And HOW do you wipe? Do you manually delete files, do you format the card, or is there some other magic option that you select?
Question #2: If you plan to flash both a new kernel AND ROM, can you do them at the same time? If not, does it matter which one you do first?
Many thanks for all answers in advance from all the brave souls that have already been there and done that. I'm about to join you.... hopefully without bricking my phone... LOL
OK, I personally try to ODIN to stock (with repartition) before flashing any new Rom.
Now if you are flashing a new rom with kerne included, you obviously flash it at the same time because is only one package.
If you want to install a Rom with a different kernel, and you are unsure about the ROM including a kernel or not, flash the rom, and after that without restarting, flash the kernel.
If you want to flash a new radio different than the one included with the kernel, then do the same with the radio after you installed the kernel.
You can also do one, restart, do the next one. It is a matter of choice most of the time, evcept when you are switching from 2.1 to 2.2
There you have to be sure that kernel and rom are both match pairs. a 2.1 Rom with a 2.2 kernel can get ugly, as well as viceversa.
always try to flash from let's say top to bottom
ROM first (if it includes kernel, will overwrite the kernel you have)
Kernel second (will overwrite any kernel and modem installed)
and finally the modem (only overwrite modem)
Thanks gagb. I have never used the repartition option of ODIN. Does that format and repartition the internal SDcard exactly how it was from the factory? And why is it called repartition rather than reformat? I woud think the whole SDcard should all be one partition. Or are there different partitions so that the OS would use some of the internal memory and the other would be for the user? Sorry for the many questions and thanks in advance for the answers.
larryvand said:
Thanks gagb. I have never used the repartition option of ODIN. Does that format and repartition the internal SDcard exactly how it was from the factory? And why is it called repartition rather than reformat? I woud think the whole SDcard should all be one partition. Or are there different partitions so that the OS would use some of the internal memory and the other would be for the user? Sorry for the many questions and thanks in advance for the answers.
Click to expand...
Click to collapse
Yes it does delete the existing app partition in Internal SD & recreate one. There is some system reserved space to install APPS.
MAJOR UPDATE 2/22/12: While the process hasn't changed too much, the key files have all been replaced for greater flexibility, and they are NOT compatible with the old method using rookie1's prep-dualboot zip. See this post for an update path from the old method to the current one.
This guide details how to repartition your internal storage and install two operating systems, or ROMs, side by side. If you're looking for a SD install that leaves the Nook's main storage untouched, you're in the wrong place (see my sig).
This guide takes advantage of the multiboot functionality built-in to CM7.1 nightlies since about #140. As such, it is not compatible with CM7.0.x builds or with earlier boot menus.
What you'll get: Whatever two ROMs you install, each will have a nearly 2GB /data partition for apps and they will share a nearly 2GB /media partition for storage, and both will have access to the SD card for more storage. At startup you will see either a small green bar labeled "CyanogenMod," or the word "cyanoboot" in blue. Both boot menus work the same:
Do nothing, and your primary system will boot
Hold down both volume buttons, and your alternate system will boot
Hold down 'n' for a more detailed boot menu
Hold 'n'+power and recovery will boot (if you installed CWM internally).
All of these actions must be taken in the first couple seconds, before a "loading" message appears below the logo. Once you see a confirmation message, you can release all buttons.
DISCLAIMER: As usual, YOU are responsible for changes YOU make to YOUR device. This process is intermediate difficulty level. It probably shouldn't be the first thing you've ever done with ClockworkMod Recovery, and you probably shouldn't just follow the steps if you don't understand them. If you don't know how your NC is currently partitioned, turn back now. If you want to preserve your warranty, turn back now. Here be serpents; be so warned.
Following the guide as-is with all default options gets you a stock 1.4.1* install on secondary and a CM7 install on primary. I hope you can figure out what to substitute where for different results.
*I don't have access to a CWM-flashable 1.4.2 zip right now, but there are instructions for making one here.
The Guide
Prerequisites:
CWM on either SD or internal recovery (internal recommended)
Wi-Fi access
Materials:
repartitionDual2GBdata
BNpri2alt
reformatData
1.4.1-keep-CWM (IF you're not starting with an up-to-date stock install)
CM7.1+ OR MiRaGe's CM7.2 OR unofficial CM9 nightlies (w/ compatible gapps)
CM7 gapps(look near the bottom of the page)
Steps:
Put all materials in your SD card's root directory (DO NOT UNZIP).
Boot into CWM.
From CWM main menu, "backup and restore" and "backup."
From CWM main menu, "install zip from sdcard," and "choose zip from sdcard."
Choose the repartitionDual2GB file.
Reboot recovery. If you have internal CWM and no boot menu, you may need to use the rhythm method:
verygreen said:
hold nook N key and then press and hold power until the {first} message appears and then disappears with screen going blank. Release power button, then press it again and hold for ~5 seconds, the {first} message should be on the screen for three seconds or so before you release power button, keep holding N button until screen blanks again. If the screen went off while you were holding the power key, that means you were holding it for too long
Click to expand...
Click to collapse
Repeat step 4 and choose reformatData
If your backup in step 3 was stock, you can "backup and restore" then "restore" and skip to step 13.
Otherwise, repeat step 4 and choose 1.4.1-keep-CWM.
When it finishes, hold the power button to shut down, remove your CWM card (if applicable), and power back on.
Complete B&N registration process¹
Power off and boot back into CWM (may require rhythm method above).
Repeat step 4 and choose BNpri2alt.
From CWM main menu, in "mounts and storage," format system, data, and cache.
From CWM main menu, choose "Advanced" and "Wipe dalvik cache."
Repeat step 4 and choose CM7 update zip.²
Reboot into main partition and set up Wi-Fi.
Reboot into alt partition (hit both volume buttons at once on "CyanogenMod" loading screen) to make sure it's working.
optional: install gapps, keysmod, etc from CWM.
¹Any mods you want to make to stock, do it now: update to a newer version, root with Manual Nooter (if rooting 1.4.x firmware, follow the linked instructions but use MN 5.12.20), flash keysmod, overclock kernels, or anything else CWM-flashable.
²If you backed up an existing CM7/9 install in step 3, then after step 16 just install gapps, install keysmod if you want it, then from CWM's main menu, Backup & restore > Advanced Restore, and restore data only from your most recent backup. When you boot into CM7 (not tested with CM9), it will be just like you left it.³
³Steps 17 and 18 may look unnecessary, but several users experienced force closes in their CM7 installs when they didn't take these steps.
Other Resources:
CMpri2alt: Moves a CyanogenMod install from the primary partition set to the alternate partition set
BNalt2pri: Moves a stock install from the alternate partition set to the primary partition set
CMalt2pri: Moves a CyanogenMod install from the alternate partition set to the primary partition set
Revert dual boot: deletes the alternate partition set and alternate boot files. Does not restore stock partition sizes, but must be run prior to partitioning back to stock.
1.4.1 full restore: removes CWM from internal recovery, does not affect partitioning
1.4.1-to-alt-partition: updates any existing stock install on the dual boot partition (removes root, does not remove installed apps)
Steps to back up and/or update both partitions
Instructions to rename boot files created with j4mm3r's old multiboot
Possible fix for rooted stock boot-looping at 'n' screen on secondary
Credits:
repartitionDual2GB and reformatData provided by DeanGibson
1.4.1 zips provided by rajendra82
possible boot-loop fix provided by sryan1983
BNpri2alt, BNalt2pri, CMpri2alt and CMalt2pri are minor alterations of DeanGibson's files
revert-dualboot is a minor alteration of rookie1's remove-dualboot
Racks11479 provided key info for the above alterations
________________________________________________________
Old Resources (Do Not Use with Current Method):
prep-dualboot
froyo-to-dualboot
Remove dual boot: returns partitioning altered with prep-dualboot to stock (1GB/5GB, non-blue-dot)
1.2 full restore: removes CWM from internal recovery, does not affect partitioning
1.3-to-alt-partition: updates any existing stock install on the dual boot partition (removes root, does not remove installed apps)
Video documenting setup for a CM9 (Ice Cream Sandwich Alpha) dual boot with Nook Color stock 1.4.1
Old Credits:
1.2 full restore provided by nemith: thank here
prep dual boot and remove dual boot by rookie1: thank here
froyo-to-dualboot from jasoraso: thank here
1.4-to-alt from jasoraso: thank here
You can thank me with the button below, or if you feel real strongly about it, you can make a donation at my blog.
UPDATE 5/25/12: Removed the prerequisite for 1GB/5GB partitioning. A little bird named jicama confirmed that the newer partitioning script doesn't care if you start with a blue dot NC. Prep-dualboot would carve the alt partitions out of /media, which doesn't work if /media's not big enough. RepartitionDual just deletes the last three partitions (/system, /data and /media) and makes new partitions from the now-unallocated space, so as long as you have the right number of partitions, it doesn't matter how big they are.
Added to my Subscribed list !! ...Thank you
I'm getting more daring , so I went through this step-by-step this afternoon (thanks for the guide!).
This was a fresh install into a previously stock Nook (I was running CM7 through the SD).
Booting into stock 1.3 works fine - no difference at all.
In CM7, however, I'm having some problems. I installed nightly 201, which worked fine from the SD card. When I boot into CM7, I get a couple "android.process.media" errors at startup, and again when I try to start Market, which just hangs up after a couple of error message popups. I tried to reinstall 201 through CWM which didn't help.
Any ideas? Should I try a different nightly build?
EDIT: also tried 202 with the same results.
oppy said:
I'm getting more daring , so I went through this step-by-step this afternoon (thanks for the guide!).
This was a fresh install into a previously stock Nook (I was running CM7 through the SD).
Booting into stock 1.3 works fine - no difference at all.
In CM7, however, I'm having some problems. I installed nightly 201, which worked fine from the SD card. When I boot into CM7, I get a couple "android.process.media" errors at startup, and again when I try to start Market, which just hangs up after a couple of error message popups. I tried to reinstall 201 through CWM which didn't help.
Any ideas? Should I try a different nightly build?
EDIT: also tried 202 with the same results.
Click to expand...
Click to collapse
You wiped system, data, and cache after running froyo-to-dualboot and before installing CM7? Try wiping dalvik cache, too (under Advanced in CWM), and boot into both partitions after installing CM7 but before gapps or any other packages/restores.
Taosaur said:
You wiped system, data, and cache after running froyo-to-dualboot and before installing CM7?
Click to expand...
Click to collapse
Yes.
Try wiping dalvik cache, too (under Advanced in CWM), and boot into both partitions after installing CM7 but before gapps or any other packages/restores.
Click to expand...
Click to collapse
Okay, I'll do that and post results. Thanks.
EDIT: Looks like that did it. Seems to work fine, other than some app FCs, which, from what I've read, are fairly common. Thanks for the assist!
I worked that info into the OP. I've done this process twice now without taking those steps and without getting FCs, but you're not the first to report them.
I was a bit confused about the backup and restore part also. Seeing as my Nook was stock to start, I probably didn't need to do that step, and might have actually caused a problem or two by restoring data that didn't exist to start.
Still working great. The only FCs I've had so far were while trying to run Facebook.
Excellent guide! Thanks for all the work on this, it works great.
This is an awesome guide. Thanks for the help. I've been wanting to do this for a while.
Thanks man.
I appreciate you putting all the tools in one place, and I especially appreciate you posting that us blue dot people needed to repartition to 1gb data before doing this; I should've figured that, but I didn't for some reason.
Moving 1.3 to the dual boot partition as I type
Question though; after I move 1.3 to the dual boot, can I still install modifications to it via CWM?
SCrid2000 said:
Question though; after I move 1.3 to the dual boot, can I still install modifications to it via CWM?
Click to expand...
Click to collapse
Short answer: no. As-is, most zips tell CWM to install them to the primary partition. You can modify them to to install to the secondary, but it's a lot simpler if you want to root, install keysmod, or overclock, to do it before you shuffle stock to secondary.
There's a decent chance rajendra82 or someone else will provide dual boot compatible versions of any future B&N software upgrades.
Taosaur said:
Short answer: no. As-is, most zips tell CWM to install them to the primary partition. You can modify them to to install to the secondary, but it's a lot simpler if you want to root, install keysmod, or overclock, to do it before you shuffle stock to secondary.
There's a decent chance rajendra82 or someone else will provide dual boot compatible versions of any future B&N software upgrades.
Click to expand...
Click to collapse
Thanks man. That's what I figured.
Question: what if I want to stick with Phiremod 6.3 instead of going to 7? Can I do all the steps outlined but just substitute 7 for 6.3? Thanks!
This is the best thing EVER. I got sick of the nook app on my CM7 build, so this worked flawlessly.
I am running the CM7.1.0 RC1 build, and everything runs smooth as silk
ChaOConnor said:
Question: what if I want to stick with Phiremod 6.3 instead of going to 7? Can I do all the steps outlined but just substitute 7 for 6.3? Thanks!
Click to expand...
Click to collapse
Negative, that's built on CM 7.0.3. You would have to use j4mm3r's multiboot and the matching stock-to-secondary file found in this thread: http://forum.xda-developers.com/showthread.php?t=1156909
Nevermind, dumb question.
Updated with a link to CM7.1 stable
I kept a stock install of 1.2 and installed phiremod 6.3 because the 7.2 links weren't working and I couldn't find one anywhere. How do I boot into the alt-partition on boot? There is no CM7 boot screen (google gears, maybe?) and pressing volume buttons several times throughout the entire boot didn't do it.
can somebody please tell me what I am doing wrong. I followed the steps, CM7 boots ok but when I use the alt, the nook gets stuck on the "n" screen.
TomMelee said:
I kept a stock install of 1.2 and installed phiremod 6.3 because the 7.2 links weren't working and I couldn't find one anywhere. How do I boot into the alt-partition on boot? There is no CM7 boot screen (google gears, maybe?) and pressing volume buttons several times throughout the entire boot didn't do it.
Click to expand...
Click to collapse
I'll just leave these here:
Taosaur said:
this guide is not compatible with CM 7.0.x sta(b)le releases, nor branch ROMs based on those builds
Click to expand...
Click to collapse
Taosaur said:
Phiremod 7+
Click to expand...
Click to collapse
Taosaur said:
ChaOConnor said:
Question: what if I want to stick with Phiremod 6.3 instead of going to 7? Can I do all the steps outlined but just substitute 7 for 6.3? Thanks!
Click to expand...
Click to collapse
Negative, that's built on CM 7.0.3.
Click to expand...
Click to collapse
Try installing regular CM 7.1.
rabi347 said:
can somebody please tell me what I am doing wrong. I followed the steps, CM7 boots ok but when I use the alt, the nook gets stuck on the "n" screen.
Click to expand...
Click to collapse
Sounds like you got close. I would say start over at step 5.
Hi, I tried installing CM7 via the CWM/zip method, which appeared to succeed by actually resulted in a boot loop. Found a couple of messages from people with the same problems but no solution.
So. Does anyone have one of the CM7 ROMs in tar image format?
Timmmmmm said:
Hi, I tried installing CM7 via the CWM/zip method, which appeared to succeed by actually resulted in a boot loop. Found a couple of messages from people with the same problems but no solution.
So. Does anyone have one of the CM7 ROMs in tar image format?
Click to expand...
Click to collapse
You'll find it here:
http://forum.xda-developers.com/showthread.php?t=1151396
This is the direct link to the uploading site, but it's not connecting now.
http://www.multiupload.com/N8VH6IUWOP
That's for CWM recovery, not CM7.
Also, you have heard about megaupload ... haven't you?
Timmmmmm said:
That's for CWM recovery, not CM7.
Also, you have heard about megaupload ... haven't you?
Click to expand...
Click to collapse
Sorry, I'm tired and read it wrong.
But it's worth trying to reflash Clockworkmod. Make sure it's the EXT4 and not the RFS version. I made that mistake before which got my CM7 stuck in a bootloop.
CM7 doesn't come in .tar format. It only comes in .zip format, which can be downloaded here:
http://www.clockworkmod.com/rommana...t.js&name=psyke83&deviceName=Samsung Galaxy 5
Don't forget the Google Apps Package as well:
http://wiki.cyanogenmod.com/index.php?title=Latest_Version/Google_Apps
And the link I gave was multiupload, not megaupload.
Heh, I am also tired! Thanks for the hint...
Timmmmmm said:
Heh, I am also tired! Thanks for the hint...
Click to expand...
Click to collapse
my personal suggestion is to use Odin to flash the CWM recovery (use the 0.5 or 0.7 version, NOT the v0.6 tar files): once booted in the recovery, do the 4 wipes (if you have the phone fully charged; if not don't do the Battery Stats Wipe); usually I also use to format the partitions, you'll find that in the Mounts menu.
Now, always from the Mounts menu, mount the sdcard as USB mass storage and copy here all the files you need to flash: usually a upgrade-****** package, an hotfix and gapps (full or minimal package that's your choice). Unmount from PC and then unmount fro phone.
Now flash normally by Install zip from sdcard and do as always: first the update-***** archive, than the hotfix and finally the gapps ones.
Now reboot and enjoy!
That's my personal how-to, which never makes me falling into a bootloop!
brainvision said:
my personal suggestion is to use Odin to flash the CWM recovery (use the 0.5 or 0.7 version, NOT the v0.6 tar files): once booted in the recovery, do the 4 wipes (if you have the phone fully charged; if not don't do the Battery Stats Wipe); usually I also use to format the partitions, you'll find that in the Mounts menu.
Now, always from the Mounts menu, mount the sdcard as USB mass storage and copy here all the files you need to flash: usually a upgrade-****** package, an hotfix and gapps (full or minimal package that's your choice). Unmount from PC and then unmount fro phone.
Now flash normally by Install zip from sdcard and do as always: first the update-***** archive, than the hotfix and finally the gapps ones.
Now reboot and enjoy!
That's my personal how-to, which never makes me falling into a bootloop!
Click to expand...
Click to collapse
hi brainvision im new to the gti5500 forum but hav been flashing roms on my wildfire for ages, my wife asked me to sort her mob out coz it kept messin up. so i did the dutiful thing and followed status's thread in the dev section and got a bootloop like a few other peeps on that thread but it doesnt seem to be any answer to this problem. i hav also tried installing the official firmware from sammobile but that jst loads the 3 screen then flashes samsung at me foreva. do you hav any suggestions of how i can fix this, im not bothered wot rom goes on as long as the mob is opperational for my wife.
thank you for your time
Did you perform data and cache wipe before flashing CM7 files and gapps package?
The way to install is always the same, so provide me some details or I cannot tell you more than that..
{ brvsn ~ CM7 on GT-I5500 ~ Tapatalk }
Sorry but I need some help. When upgrading roms a few times, no problems ever occurred. CWM always worked smoothly. Now, I have the Resurrection Remix 1.0 Pro installed and was attempting to upgrade to Resurrection Remix 1.2 AOKP. I see that when running CWM I only had to choice to access the "download" folder on the scard. When attempting to install the Remix 1.2 rom, I always end up with an e signature fail. I tried several times but had the same results. I had to reboot and stay with Remix 1.0 until someone can help me get the upgraded rom installed. I wiped all the data and reset, and don't know what else to do.
Please help!!
OK, not sure the procedure you made... but might also be that some files you got were corrupted. Check to see they all are fine before going ahead with this way to install:
Do a full wipe(factory reset+cache+dalvik cache)
Install the Main ROM
Install Siyah-v3.0.1-CWM.zip
Reboot
Do the initial setup of things
Go back to CWM and install navigation button fix
Reboot
Then go back to CWM and install app themes (there are some bugs, but if you want the black themes, then install classic first, then black)
Reboot
Some people have other issues after, but see how this goes.
I would change the DPI settings to 184 or 210 for everything to work fine from market apps.
*if have more problems, just reply here.
Is the file on an external SD?
It's wherever you put it, though some files will only flash properly from external SD.
I think it's the internal sd
felixg123 said:
Is the file on an external SD?
Click to expand...
Click to collapse
At first I thought I had the files on the external sd card, but when rebooting in recovery with CWM it looked like it was only allowing me to access the download folder on the internal sd card.
Thanks for any suggestions.
cyberboob said:
It's wherever you put it, though some files will only flash properly from external SD.
Click to expand...
Click to collapse
The CWM that came with the remix 1.0 pro rom is that weird one that seems to have to boot from the other little app. Do you recall this is the CWM zip file that was added to the files to download for the remix 1.0 pro rom. It doesn't appear to have the same flexibility that the CWM had that came with my previously used rom...remix 9.4
Any comments??
With 1.0 its 3e (stock recovery) so you have to put cwm.zip in your external SD or your cache then flash it through 3e. Now you have cwm. If its the one from westcrip its touch so don't use the volume buttons.. actually touch the screen.
Hopefully that helps.
Sent from my GT-I9100 using XDA
Does the same thing... but it's a touch version.
There is a newer 1.3 version out now for Resurrection Remix with far simpler installing procedure... and people have reported most bugs fixed now (maybe a couple remain to be found).
cyberboob said:
Does the same thing... but it's a touch version.
There is a newer 1.3 version out now for Resurrection Remix with far simpler installing procedure... and people have reported most bugs fixed now (maybe a couple remain to be found).
Click to expand...
Click to collapse
Now, I'm really scratching my head. When I try installing the 1.3 rom it begins ....but returns this message and then aborts.
E: failed to verify whole-life signature
E: signature verification failed
I re downloaded the rom 1.3 to make sure it wasn't corrupt, and it did the same thing. Then I downloaded remix 1.2 just to see if this would install properly. I got the same result with the failed signature coming up in red and then it aborts. So something is not allowing me to change roms?? At present I have remix 1.0 installed.
Please I need some assistance figuring this out. I don't know what to do now?
Thanks in advance
Check if your current rom is having any beta releases of siyah 3.0, if so then it would be the cause, download cf root, or any latest version of custom kernel in tar format and flash it via Odin, now enter cwm and flash the new rom, you would be good to go
#*posted on the move *#
Works fine ....but is there a GPS problem?
I got the darn thing installed. Thanks. I was able to install the CWM......one that worked properly and the remix 1.3 got installed without a hitch. One problem I'm noticing the the GPS taking a whole bunch of time trying to locate sats. Is there is gps fix ??
Thanks
go to the Emergency FAQ for 1.3 (in my sig)
I did the ExynosAbuse-v1.40 exploit, install Mobile Odin Lite, SiyahKernel v2.6.14, ClockworkMod Recovery, and install CM 10.1.3.
My first root and rom install and everything works great! Battery life went from one day to three and operating quickly.
Do I keep the files on my sd card or can i delete them?
For future installs and upgrades, is CWM recovery my primary means of install?
Thanks guys for your hard work. I really appreciate all you do and plan on donating to the cause.
Dave
dave042 said:
I did the ExynosAbuse-v1.40 exploit, install Mobile Odin Lite, SiyahKernel v2.6.14, ClockworkMod Recovery, and install CM 10.1.3.
My first root and rom install and everything works great! Battery life went from one day to three and operating quickly.
Do I keep the files on my sd card or can i delete them?
For future installs and upgrades, is CWM recovery my primary means of install?
Thanks guys for your hard work. I really appreciate all you do and plan on donating to the cause.
Dave
Click to expand...
Click to collapse
"on my sd card"? You meant external uSD card or internal memory?
Either way, you can delete them if you won't ever need them again.
From this point on, any flashable zip file will be run using CwMR
Welcome @dave042,
-and congrats on a successful first root/ROM experience.
regarding the "files on the sd card", If we're ignoring the expansion slot, then there are files that apps use on the internal SD, so I wouldn't go deleting them at random. I'm sure that a google search will help you with which folders are needed, and which are not.
All future firmware installs should indeed happen from CWM recovery. Once you're rooted and kernel'd, there isn't any need for mobile ODIN. The options offered in CWM recovery are superior.
As you try new things, I do advise that you do some cleanup inbetween ROMS. Dirty flashes often lead to issues that people blame on the rom or kernel. factory resets only catch a portion of the critters. @mrcook has a few rom wipe scripts specifically for the i777 that have helped multiple people (myself included) out of weird phone issues that were the result of old-rom-junk not playing well with new-rom-junk.
Happy flashing
-Cyril
thanks votinh and Cyril for the quick response.
the SD card i was referring to was the external SD. i don't plan on installing too many roms but will make sure to do a complete wipe prior to any install.
was this process of installing ExynosAbuse-v1.40 exploit, install Mobile Odin Lite, SiyahKernel v2.6.14, ClockworkMod Recovery, to get me to root? and once to root, to install a rom?
another question, kernal and rom updates, are they independent of each other? can i update one without the other?
i understand roms are numerous and customized, what about the kernal? does changing the kernal make any significant changes to the operating system?
Gneerally on this device ROMS will come packaged with their own kernel. The kernel will be flashed when the rom is flashed. I do believe however that most install AJK after they flash their roms.
You can delete everything off your sd card. I do keep a known good rom as well as a copy of Siyah 4.3.3 kernel on my card at all times. You never know when something is going to mess with your phone, and you may have to re install a rom in order to make you phone function again. I would hate to be somewhere, my phone start a boot loop, and I am stuck without a phone. The Siyah 4.3.3 kernel comes in handy for me. Some roms will give you an error 7 when flashing. Rather than messing with editing the build prop I just flash Siyah, and try my rom again.
If you go flashing kernels make sure you have the proper kernel for your ROM.
@dave042: "was this process of installing ExynosAbuse-v1.40 exploit, install Mobile Odin Lite, SiyahKernel v2.6.14, ClockworkMod Recovery, to get me to root? and once to root, to install a rom?"
Click to expand...
Click to collapse
ExynosAbuse-v1.40 exploit <-- tool to establish root-access to the device (framaroot is another useful, easy rooting tool for the i777)
Mobile Odin Lite <-- tool that uses root-access to install...
SiyahKernel vX.X.X <-- a custom kernel (one of many) installed primarily to provide cwm recovery, but are also commonly used to:
-provide additional functionality to the existing ROM
-backup your ROM install
-install a different ROM
-install a different kernel
-flash cleanup scripts
-and many many other things
As Butchr stated, the ROMs are usually packaged with their own kernels, so the kernel used above only remains in place until another ROM is flashed, which will overwrite the existing recovery with one specifically designed for the ROM flashed.