Related
I'm having problems because I don't think the ROM is flashing correctly. Some apps are missing that say are include with the ROM. Should I Odin back to 2.1 and do the process all over again starting fresh?
Also checked the build number on my phone and it reads "MIUI-unknown" HELP!!
Are you flashing the "Original" MIUI first and then going to the "ReVaMpEd LITE"? If not then ODIN to 2.1 and Flash that first. I could be wrong, but I'm pretty sure the only install directions in the OP are "If you are coming from a MIUI ROM". The "Original" MIUI download link is in the OP of the "ReVaMpEd LITE" thread. Good luck!
Flash the latest MIUI following the cm7 install instructions.
Then flash revamped following the revamped instructions.
FOLLOW THEM EXACTLY.
"Format system" is not factory wipe.
It is located in mounts and storage.
Vibrant+MIUI
Well see I'm already on MIUI Revamped and what I'm having problems with is that every week that a new release comes out I flash following the instructions in the OP but the ROM doesn't flash correctly I guess.
Thanks again guys/gals for your help.
Once you're on it the updates should be pretty easy. Just flash like any other ROM. Good luck!
s13epy said:
Well see I'm already on MIUI Revamped and what I'm having problems with is that every week that a new release comes out I flash following the instructions in the OP but the ROM doesn't flash correctly I guess.
Thanks again guys/gals for your help.
Click to expand...
Click to collapse
feel free to PM me with any questions.
Ive been on revamped for weeks now Ive got it down pretty good.
Odin back to stock.
Root your phone again.
Redownload the rom and delete the old one because it may just be a bad download.
Wipe data/factory reset
Go into recovery and go to mounts and storage.
Format system, data, and cache.
Go back to the main recovery screen and go to "advanced".
Wipe Dalvik cache then go back to the main recovery screen.
Go to install zip from sdcard and reflash the rom.
Flash the kernel of your choice that is compatible with the rom.
Go to advanced and "fix permissions".
Reboot and let it sit for 5 minutes if you have the patience.
Enjoy
Thanks peeps!
Update:
Just re-flashed and everything works now :b
Hey guys!!!
New galaxy S2 owner. I have done some searching in these forums and the threads answered many of my questions. However, I still have some newbie questions that I found unanswered. Please excuse me if my questions have been answered before but I got tired of searching
Here is the deal:
Yesterday, I flashed a CF Root with Odin3. Then used CWM to flash a wanamlite firmware. The firmware was great but I didn't like that it still had TW. So I dl'ed another firmware to the internal SD card and flashed again using CWM. I then flashed a couple of other ROMS and I noticed that after the first wanamlite flash, the new ROMs were unstable with many error messages that some OS processes have stopped etc.
I got back home, flashed to stock with Odin3 and the phone got stuck at the second samsung logo. I followed some community steps (thanks XDA) like disabling all kies processes from TM, wiping data/cache, then boot in DL mode and flash the stock ROM using Odin3 which worked.
I then Flashed a CF Root again and used CWM to flash a Spike Pure ICS ROM v5 which was great but I get occasional error messages like 'gallery stopped' or some other error message when I try to set contact photos. It just lags, blackscreen then comes back with the 'Unfortunately, the process had stopped'.
My questions: is this because of the previously flashed firmware that this is happening or is it that those ICS ROMs have these issues commonly? Did anyone have this experience before? What do you advice before flashing to a new ROM going back to stock or going straight from the current? Doesn't Odin3 technically wipe everything back to stock?
WIPE WIPE WIPE.
Go into recovery. Data/factory reset.
Advanced, Wipe dalvic cache. Mounts and storage, format system. Its a standard procedure going from one OS to another OS. You can then either flash a firmware zip from recovery or an .tar file from Odin.
Then to be on the safe side factory reset once again.
Sent from my GT-I9100 using Tapatalk 2
Wich fw do you have?
Make a deep clean with odin an flash on the latest ics version (lp9 is a good one)..then flash (if you want) a custom rom..
My experience with custom roms: one of the best rom samsung based (ics 4.0.3) is the foxhound greyfox v2..if you want a pure ics rom flash the omega aokp rom (ics 4.0.4)..
Try then to change kernel..siyah is the best for both roms..
P.s. sorry for my bad english
Sent from my GT-I9100 using Tapatalk 2
After LP7 should be staple enough for daily use .However you are using custom roms and you should read carefully each roms thread before flashing .
You are probably suffering from flashing multiple roms and leaving bits behind as well = clean wipe .
jje.
Can someone give me a clear full wipe procedure? I always wiped data/factory rest/wiuped chaceh and dalvik... but what else? a step by step procedure would be helpful!!
I currently have Spike Pure ICS v 5.
What do you mean by Odin3 'deep clean'?
OJ77 said:
Can someone give me a clear full wipe procedure? I always wiped data/factory rest/wiuped chaceh and dalvik... but what else? a step by step procedure would be helpful!!
Click to expand...
Click to collapse
Read my last post..
Sent from my GT-I9100 using Tapatalk 2
so:
1. Recovery mode > format user data > wipe cache > clear dalvik > format system (from moutns and storage)
2. Download mode > flash stock ROM using odin 3
Did I get it right? Was there something i didn't wipe?
Before you flash a new rom, make sure you answer the requirements.Some ICS roms need to be flashed in specific way.
The way of doing a full wipe is you go in Clockwork mode, wipe data/factory reset, you wipe cache partition, then go to advanced wipe Dalvik and Battery stats, then go in mounts and storage ( i think ) and you wipe the cache from there, but nothing else in mounts and storage.If you wipe anything else there's a high percent of bricking your phone.If this doesnt help you, I doubt that anyone could give you any clearer instructions.
Good luck.
DONT FORMAT SYSTEM.
....................................
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card .
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware .
Followed by root and custom rom if you so wish .
jje
OK im confused now... do I format system directory in mounts and storage or no?
OJ77 said:
OK im confused now... do I format system directory in mounts and storage or no?
Click to expand...
Click to collapse
i always do personally.
I got tempted and formatted system/cache/data but now i cannot flash from my internal sd card.. I get errors and 'installation aborted' if i try to do it from CWM... does that mean formatting those 3 means Odin3 is the only way? Cus I'm not home and I don't have odin3 on me.... LOL!
OJ77 said:
I got tempted and formatted system/cache/data but now i cannot flash from my internal sd card..
Did you format sd card and totally wipe the lot = nothing on the phone .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card .
At this point you have no OS on the phone nor kernel rooted nor CWM .
Hence
Remove battery
Boot to download mode
Open Odin
Install correct stock firmware .
Click to expand...
Click to collapse
JJ, you really need to learn how to quote you know, makes your posts so confusing to read sometimes
skimminstones said:
JJ, you really need to learn how to quote you know, makes your posts so confusing to read sometimes
Click to expand...
Click to collapse
Agree must try better .
Habit from replying to emails i guess .
jje
Thanks...
I did a 'full wipe' by doing t his:
1. Boot into CWM: wipe data, wipe cache, wipe dalvik, wipe battery stats, wipe system/data/cache from mounts.
2. Reboot into DL mode, flash stock ROM using Odin3.
3. Repeat step 1
4. flashed spike ICS v 7.3 using CWM. Stable so far.
Thank you!
imho: the most stable ics release is the stock official, but with some.battery issues, my suggestion: stay on gingerbread, find a custom kernel to suits your need,
GT-I9100, official 2.3.6, hardcore's Speedmod
budi.hermawan said:
imho: the most stable ics release is the stock official, but with some.battery issues, my suggestion: stay on gingerbread, find a custom kernel to suits your need,
GT-I9100, official 2.3.6, hardcore's Speedmod
Click to expand...
Click to collapse
I agree! I don't like ICS because is still unstable! My battery lasts very short with ICS and the phone overheats.
Moreover I hate the browser! I mean, The Galax S2 with GB still has the smoother browser of all the smartphones out there, and Samsung with ICS update messed it up! Now is laggy with micro stutters! Don't understand why!
OJ77 said:
The firmware was great but I didn't like that it still had TW.
Click to expand...
Click to collapse
You didn't need to go through all that trouble just because you didn't want TW (which I also hate, btw).
You could simply have installed another launcher (such as Go Launcher EX, ADW, etc) from Play Store and, since you were already rooted, uninstalled TW using Titanium Backup afterwards. It has to be in that sequence (install new then uninstall old).
this way you can have whatever ROM + kernel combination you like, and still use whatever launcher you prefer.
Hello XDA,
I own a SGS II GT-I9100.
It has been running on CM7.1.0 , Android version 2.3.7 since I got my phone and I'd like to update it.
I have PARANOIDANDROID 2.54 in mind to update into.
I am wondering what steps do I have to take as I do not understand the instructions stated in the rom's thread.
The instructions state:
RECOVERY: FACTORY RESET IF YOU WERE USING ANOTHER ROM!
RECOVERY: Install Rom: Download
RECOVERY: Install Gapps, ALWAYS-EVEN FOR UPDATES: Download (find the latest one that carries the "jb" tag)
RECOVERY: Wipe Cache Partition
RECOVERY: Wipe Dalvik Cache
Reboot and enjoy.
Specifically at the part after doing a factory reset. How do I install rom/gapps after I do a factory reset?
Do I use "ROM Manager v4.5.0.1"? And also, will it still stay after doing a factory reset?
JustGotAnSGSII said:
Hello XDA,
I own a SGS II GT-I9100.
It has been running on CM7.1.0 , Android version 2.3.7 since I got my phone and I'd like to update it.
I have PARANOIDANDROID 2.54 in mind to update into.
I am wondering what steps do I have to take as I do not understand the instructions stated in the rom's thread.
The instructions state:
RECOVERY: FACTORY RESET IF YOU WERE USING ANOTHER ROM!
RECOVERY: Install Rom: Download
RECOVERY: Install Gapps, ALWAYS-EVEN FOR UPDATES: Download (find the latest one that carries the "jb" tag)
RECOVERY: Wipe Cache Partition
RECOVERY: Wipe Dalvik Cache
Reboot and enjoy.
Specifically at the part after doing a factory reset. How do I install rom/gapps after I do a factory reset?
Do I use "ROM Manager v4.5.0.1"? And also, will it still stay after doing a factory reset?
Click to expand...
Click to collapse
after doing a factory reset copy the rom and gapps zip files to your internal or external sdcard.
Paranoidandroid does not come with google apps (gapps) as part of the rom it is a seperate zip file.
reboot in to recovery.
scroll down to install a zip from sdcard. install rom. reboot.
reboot into recovery again install gapps.
reboot.
No rom manger will not stay but paranoid does not use it. It is only recommend for use with cm roms only.
avoid using ROM manager on this particular device, it is known for beign the cause of lots of problems and malfunctions
Thanks for the reply guys.
Let me confirm the steps I have to take:
1) Factory reset my phone.
2) Copy the rom+gapps into internal/external sd.
3) Reboot phone into recovery.
4) Scroll down to install zip from sd card -> install rom -> reboot.
5) reboot into recovery and install gapps
6) Reboot.
Is that correct?
Also, I read this thread, http://forum.xda-developers.com/showthread.php?t=1990102 about dong a factory reset on a custom rom.
Is there a chance that I would encounter the same problem as I'm running on CM7?
I apologise for having so many questions. It is my only phone and I'm afraid that I'd brick it.
Thanks again for the help, really appreciate it.
Got another question.
For kernels, is there anything I have to take note of?
Like will my current one affect anything like it not being compatitble with paranoidandroid?
Read the ParanoidAndroid thread (first page in particular; but as much of it as you need to in order to get an answer), normally compatible kernels in those threads.
Learning is fun.
MistahBungle said:
Read the ParanoidAndroid thread (first page in particular; but as much of it as you need to in order to get an answer), normally compatible kernels in those threads.
Learning is fun.
Click to expand...
Click to collapse
Thank you for your reply.
If my kernel is not compatible (kernel automatically changed when I flashed CM7.1.0), what do I have to do?
I have read the first page of the thread and also ran a search on my kernel (2.6.35.7-g1e46077 [email protected] #1) in that thread.
Sadly, there were no answers as to whether my kernel was compatible.
Hmm, just wondering, if cm7.1 came with a compatible kernel, would flashing into ParanoidAndroid actually come with a compatible kernel as well?
Find the ParanoidAndroid discussion thread (not the development thread; You'll quite rightly get baked if you post a question like this there), and post asking if the kernel you want to use is compatible with the rom.
Or you could always read the thread. XDA search is complete/utter poorly coded rubbish (and I'm being very kind in saying this), I'm not surprised you didn't get meaningful results from a search.
Edit - Yes, I think you'll find the rom will come with its own kernel which is (obviously) compatible. But lots of people change kernels for all kinds of reasons. Up to you.
I tried finding their SGS II discussion thread but was unable to find it. (Only managed to find one for LG Optimus One)
From what I understand so far after reading around, is it true that my current Android version (2.3.7), Kernel and Mod version will not affect the process of flashing into a new rom?
Like will everything change after flashing into a new rom? In this case would be the Android, Kernel and Mod versions will change according to what the ParanoidAndroid rom is of?
If my understanding is correct, can I proceed with these steps:
RECOVERY: FACTORY RESET IF YOU WERE USING ANOTHER ROM!
RECOVERY: Install Rom: Download
RECOVERY: Install Gapps, ALWAYS-EVEN FOR UPDATES: Download (find the latest one that carries the "jb" tag)
RECOVERY: Wipe Cache Partition
RECOVERY: Wipe Dalvik Cache
Reboot and enjoy.
I have a sch-i500 that is rooted with cwm working.
I am very interested in running liquid smooth v 2.9 found here: http://forum.xda-developers.com/showthread.php?t=2245120
so I did a format, wiped the cache and davlik. when I installed the zip from external sd card the phone immediately gave me a screen for CWM v 6.0.3.3.
I can still navigate and restore old back ups but the phone does not go past the Samsung logo on the boot screen. Any advice is appreciated.
I was previously running stock 2.3.5 E09 if that helps
http://forum.xda-developers.com/showthread.php?t=1026746
seems to be the best way for me to recover from this (looks like I flashed a non voodoo rom without removing voodoo) but I am unable to get the phone into download mode with or without the battery in the phone.
please help......(update) Alright, I am a moron. needed to have a powered usb port. on my way to recovery. thanks for having all this great info in one place.
aircooledbusses said:
so I did a format, wiped the cache and davlik. when I installed the zip from external sd card the phone immediately gave me a screen for CWM v 6.0.3.3.
I can still navigate and restore old back ups but the phone does not go past the Samsung logo on the boot screen. Any advice is appreciated.
I was previously running stock 2.3.5 E09 if that helps
Click to expand...
Click to collapse
Oh so close.
When coming from 2.3.x ROM you will need to flash the rom (liquid: or other 4.2.x) you will need to flash 2 more times...
The 1st flash get you into the new recovery only,,, as you found out.
2nd flash will pop up with an error message about incompatible partition and telling you to re-flash again,,,
So 3rd flash actually installs your new ROM
Then install a current/compatible Google gapps
.
Enjoy
.
Thank you, I am getting closer.
still on the second and third flash of the rom I get a satus 7 error which I think is a bootloader issue.
I have flashed the GBbootloader.tar through odid to no avail and am following Section:4 How to flash any ICS 4.0.x & 4.x.x JellyBean based rom
http://forum.xda-developers.com/showthread.php?t=1238070
anythoughts?
aircooledbusses said:
Thank you, I am getting closer.
still on the second and third flash of the rom I get a satus 7 error which I think is a bootloader issue.
I have flashed the GBbootloader.tar through odid to no avail and am following Section:4 How to flash any ICS 4.0.x & 4.x.x JellyBean based rom
http://forum.xda-developers.com/showthread.php?t=1238070
anythoughts?
Click to expand...
Click to collapse
what does the error say besides status 7?
did you odin the CWM4 fixed for cm7 then install the ROM 3 times?
can you get a pic up for us to see?
just to be sure......using odin, I repartitioned with the pit, and flashed a E03 rom. rebooted the phone fine.
flashed the CWM4 fix for 7 and redid the GB bootloaders as well.
went into recovery and factory reset, wiped cache, and dalvik.
installed liquid-JB-v2.7-Official-fascinatemtd.zip this time first time took me directly to clockwork where I flashed again. prompted with install from sdcard complete. repeated and got same message.
factory reset, wipe, wipe and flashed gapps. Everything seems to have worked this time with the v2.7Official instead of 2.9. I will play with this for just a bit and probably try it again tonight with a fresh downloaded copy of v2.9. I really do appreciate your assistance and help and I would not have gotten this far without the forum.
update:
flawless installation of v2.9 since 2.7 was already installed. (installed via cloclwork mod recovery)
It was most likely an operator error that prevented me from installing 2.9 after E03. But I don't see the benefit of going back to recreate why it didn't work. Thanks again all is good and right.
Clarifying here, it's a simple question.
I saw several people in the blu_spark custom kernel thread saying that you don't need to do a full wipe and flash stock OOS to flash the kernel. If I'm coming from stock rooted with TWRP, am I able to just flash the kernel itself without wiping anything? New to flashing custom things in general.
Dont know for sure, but what I'd suggest is to Flash the Kernel & Wipe Dalvik before reboot, thats what i do, no problems so far, same for updates too.
You don't need to wipe Cache/Dalvik because Kernel has nothing to do with them. Only thing you have to check for is if the Kernel you want to flash grabs the ramdisk from the Kernel that is installed or comes with its own.
Im using despair kernel
Scherzengel said:
You don't need to wipe Cache/Dalvik because Kernel has nothing to do with them. Only thing you have to check for is if the Kernel you want to flash grabs the ramdisk from the Kernel that is installed or comes with its own.
Click to expand...
Click to collapse
How would I be able to check this?
Ask the Dev of the Kernel you want to install. But first read the description of the Kernel and the Devs advice for Installation.
Most kernels do not require a whole system wipe like that. As long as the kernel is compatible with the ROM you should have no problems in just plain flashing it. You can find out if it is compatible by looking on the Original Posting by the developer. Another thing to note: if a kernel developer does not specify a ROM compatibility and yet a kernel installs and the ROM even boots up that does not mean you are completely bug free. An example of this would be using blu_spark's OOS kernel on CM 13. It will flash, boot, but your phone will lag, randomly reboot, apps will force close, etc.
He actually has a beta kernel for CM 13 so that you can use his customization and without above issues.