Last time I flashed my phone I used ODIN and a modded AT&T ICS stock rom. This time I used directions from the following site and when I boot to CM after flashing it goes through a process that says optimizing applications then reboots and hangs on the CM logo spiining which I'm assuming means it locking up during boot.
I changed recovery from odin to CWM before flashing which appears to work fine. I restored my backup I made with CWM after installing and my phone is working again. Any ideas what I'm doing wrong here or should I try a different ROM? Thanks.
AT&T Samsung I777
http://tech.gamotech.com/how-to-install-android-4-3-jelly-bean-on-att-samsung-galaxy-s2-i777/
@keeperofthecode,
The ROM is fine, it's the method that i question.
Once you're comfotably back to stock, this is the easiest way to get from stock to custom recovery on the i777:
Framaroot <-- tool to establish root-access to the device
Mobile Odin Lite(or pro) <-- tool that uses root-access to install...
Custom Kernel <-- a custom kernel (there are many available) installed primarily to provide cwm recovery, but are also commonly used to:
-install a different ROM
-provide additional functionality to the existing ROM
-backup your ROM install
-install a different kernel
-flash cleanup scripts
-and many many other things
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.
This guide will walk you through the steps, but read through the thread carefully to be sure that you understand everything before leaping.
-happy flashing
edit - it seems you already had root and cwm, so I'm not sure what went wrong. Before flashing the ROM, try a ROM cleaning script, or at least:
-factory reset
-format /system
Thanks. Reset and wiped then installed perfectly. UDMAN
Related
hi..
I've rooted my device with superoneclick and installed Erygit Custom-rom 3.0 using Odin.
Should I still do the CMW recovery, will it have any affects? I want to install some boot animation that I've found on this site. Will it help?
Also, if someone can kindly check if the method as mentioned on this site is accurate.
http://www.android.gs/root-install-cwm-recovery-samsung-galaxy-player-5-0/
Thanks
If I recall correctly, the Erygit rom includes the CWM recovery kernel.
If it doesn't, I'd strongly recommend installing it. It won't make any difference to normal usage, but it does allow you to create a complete backup of your device at any given time, which is very handy if you do more than minor tweaks.
Also, you'll need it to wipe your system data if you switch to another rom.
Hey guys
I'm trying to flash my S II I9100G with cMIUI, which doesn't work. The phone gets stuck during booting right after the installation. I've been messing around with this problem for a couple of hours by now, been googling a lot and yet I have not found a solution.
What I did in order to flash the ROM:
1) I installed the latest German stock ROM (ICS) using Odin.
2) I followed this tutorial (root using SU-BB-Installer.zip and flash CWM recovery kernel 6.0.1.2 via kTool): http://forum.xda-developers.com/showthread.php?t=2065581 So far everything works fine. I have root access now.
3) Downloaded the cMIUI 2.10.19 zip from http://forum.xda-developers.com/showthread.php?t=1804619
4) When I tried to flash cMIUI from Recovery and toogle signature verification "on", it told me "signature verification failed". I ignored that message and installed it anyway.
5) Installation ran smoothly. After finishing it, the phone wanted to reboot. It now got stuck in the booting screen. I can not get the ROM booted.
I don't think it's cMIUI-caused, because I tried to flash a clean CM10 and still had the same problem (even though it didn't fail signature verification). Here are some more things I tried:
- installed clean stock ROM via Odin, again. Then followed all above steps exactly as described above, except for using Odin for flashing CWM Recovery instead of kTool
- again, clean stock ROM. After rooting, I then tried to install cMIUI via ROM Manager v5.5.2.3. Unfortunately, ROM Manager doesn't identify CWM recovery and keeps asking me to install the Recovery-System with ROM Manager. When I try that, there apparently "is no official CWM Recovery available" for my model. So, ROM Manager is no option
As described in the following thread, I can not use the ClockworkMod Recovery 6.0.1.2 kernel on aosp based ROMs like cMIUI and CM: http://forum.xda-developers.com/showthread.php?t=1631934 So that probably is the cause of my problem. Can you tell me what kernel I can use, instead? Or is there another way to flash that ROM? Via Odin, for example...
Thanks for your help in advance. Very much appreciated!!
Regards,
Daniel
What Codeworkx is saying in that thread is, that you cannot use that kernel when you are already on a aosp based rom. So you can use that recovery.
Something you didn't mention, did you do a full wipe from within the recovery? If you didn't do that, then thats probably the source of your problems.
1. Flash a stock rom true Odin.
2. Flash the recovery (you don't need to root your rom after)
3. Wipe system/factory reset
4. Wipe cache.
5. Download the rom again to make sure you the download went well.
6. Toggle signature verification off.
7. Flash Miui
8. Reboot and wait.
Lennyz1988 said:
What Codeworkx is saying in that thread is, that you cannot use that kernel when you are already on a aosp based rom. So you can use that recovery.
Something you didn't mention, did you do a full wipe from within the recovery? If you didn't do that, then thats probably the source of your problems.
1. Flash a stock rom true Odin.
2. Flash the recovery (you don't need to root your rom after)
3. Wipe system/factory reset
4. Wipe cache.
5. Download the rom again to make sure you the download went well.
6. Toggle signature verification off.
7. Flash Miui
8. Reboot and wait.
Click to expand...
Click to collapse
Thank you so much! Wiping helped. :good: Why didn't I try that before :silly:
Awesome, now I can finally enjoy cMIUI. It's really great! (except for crashing galery/camera app when starting cam from lock screen. but who cares )
Thanks dude! :highfive:
I tried following this:
http://forum.xda-developers.com/showthread.php?t=1580070
"INSTRUCTIONS" part:
* 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
Click to expand...
Click to collapse
did all the above, never forgot any of the 3 wipes/resets that were necessary.
used this rom file:
http://goo.im/devs/paranoidandroid/roms/i9100g
(latest one)
for my Galaxy Samsung S II GT-i9100g.
I had CWM and also had a rooted android 2.3.
first boot it showed me the normal samsung boot screen, for 45 minutes....
so I restarted and the phone gave me the same behaviour..
so I removed the battery to turn off the phone, and attempted to reinstall the whole thing, going through this process again from scratch
not forgetting any of the wipes etc...
now every time I boot it, it leads me to CWM instead of the normal boot screen and the expected paranoid rom eventually...
I followed this path because CM 10 failed me because upgrading from 2.3 to 4.x requires going through something that is called "stock" or as I think it actually is - google's /manufacturer's original firmware/rom production line thingy
and after that it needs me to re-enable root on that stock rom all over again. And only then I may attempt to install CM10...
so I picked paranoid instead, because in it's instructions is showed me no such constraint. heck it can't give me that constraint because there is no "stock" of android 3.x for smartphones
but then this issue happened... so I need your help.
I found similar search results but couldn't figure out their solutions or how whatever triggered that same problem (which isn't mentioned in those threads) is related to what I did to my phone... (so that I will not repeat the same mistake)
your help is much appreciated as I need it so so much!
Huh?
Just flash a stock ROM, get back on your feet and go CM or paranoid.
Sent from the little guy
gastonw said:
Huh?
Just flash a stock ROM, get back on your feet and go CM or paranoid.
Sent from the little guy
Click to expand...
Click to collapse
by "flash"ing you mean the option "install from a zip file" in CWM in recovery mod?
if I have some rom, the only way for me to install another would always be by going through that middle step of also installing a 'stock' rom as well?
there is no way around it?
installing a 'stock' rom, wouldn't it make me loose my root I have on the phone and force me to root it all over again before I can continue install anything at all?
thats the reason I wanted to try out the paranoid way of doing this instead of the CM10, because I have no interest in rooting my already rooted phone and I hoped that paranoid does not need me to go to stock first....
Couple of things:
Stock: why, when in trouble, we suggest stock?
Stock is the original state of the phone.
Samsung write it for our device to work flawless, so, by flashing stock we can check if our device is fully functional.
Imagine you flash a custom ROM and you lose IMEI, you go "wtf?" right?
In order to check if your EFS folder is f&#cked up, you flash stock and check if your IMEI is still there.
We can always use stock to take a long breath "phew, we're fine" after a f*&k up.
You can flash stock via CWM (zip file), Odin (tar file, md5) and mobile Odin (tar, zip and md5).
CWM: custom recovery, you can get it by flashing a custom kernel or by flashing it via stock Recovery (generally comes with BusyBox and SuperUser app, which gives you Root).
Odin: Just download any version and follow directions.
Mobile Odin: Well, this is a hell of an app, you need Root to run it.
It does all that Odin does, plus it roots your ROM (only stock ROMs) while it's flashing it, all by itself. Costs 5 bucks, but it's damned worthwhile.
Wanna know the best scenario?
You get M.O Pro, you get a nandroid back up online app, you get CWM zip files (sitting on your SD).
With that line up, you can flash whatecer the hell you want and you will ALWAYS have root.
Sent from the little guy
some questions
ONE QUICK IMPORTANT QUESTION BEFORE THE REST:
If I use mobile odin, will I be able to use it to install stock rom and also root it at the same time?
SECOND IMPORTANT QUESTION:
you said I could flash whatever I want and still have root, but my problem was not 'not having root', it was not having the flash process complete successfully... how do I attack that?
THIRD IMPORTANT... info... :
My "BUILD" version is "GINGERBREAD.XXKL5", isn't that a 'stock' one?
If you don't have a lot of time,
then the rest of this post is not as important as the 2 questions above...
gastonw said:
Couple of things:
Stock: why, when in trouble, we suggest stock?
Stock is the original state of the phone.
Samsung write it for our device to work flawless, so, by flashing stock we can check if our device is fully functional.
Imagine you flash a custom ROM and you lose IMEI, you go "wtf?" right?
In order to check if your EFS folder is f&#cked up, you flash stock and check if your IMEI is still there.
We can always use stock to take a long breath "phew, we're fine" after a f*&k up.
You can flash stock via CWM (zip file), Odin (tar file, md5) and mobile Odin (tar, zip and md5).
CWM: custom recovery, you can get it by flashing a custom kernel or by flashing it via stock Recovery (generally comes with BusyBox and SuperUser app, which gives you Root).
Odin: Just download any version and follow directions.
Mobile Odin: Well, this is a hell of an app, you need Root to run it.
It does all that Odin does, plus it roots your ROM (only stock ROMs) while it's flashing it, all by itself. Costs 5 bucks, but it's damned worthwhile.
Wanna know the best scenario?
You get M.O Pro, you get a nandroid back up online app, you get CWM zip files (sitting on your SD).
With that line up, you can flash whatecer the hell you want and you will ALWAYS have root.
Sent from the little guy
Click to expand...
Click to collapse
the saddest part is that I couldn't figure out most of what you just said
what is 'nandroid'? 'flashing'? do you mean like dd in linux? copying to the entire flash storage device?
'IMEI'? huh..? O_O
at the moment I was able to 'get back on my feet', I restored everything back to normal with manual copying of important parts of the CWM corrupted backup from this week, and old stuff for a CWM backup made few months ago.
now that I am at a 'normal' state.. I want to install paranoid or CM10 on my GT-I9100g.
which one of those 2 does not force me going through installing stock?
I have this fear of installing stock that it will take away my root and that I will have to use adb from command line to re-enable root afterwards, which I have bad experience with.
I need to know a few things before I attempt to install stock via CWM,
will installing stock disable my root? will installing stock disable my ability to load recovery boot menu CWM?
is 'root' an attribute or state that belongs to the running rom itself after boot has been completed and to that only?
or does it also belong to the state the device is at while in the recovery boot menu CWM ?
I tried messing around with ADB in the past to see if I could root devices via that way but it wasn't very successful so thats why I'm afraid of having to attempt it again.
bumpitybump
even though a year later, I would still love some replies
resurrecting my motivation to do this once again.
copy paste from my other post;
before flashing, you will need these;
-stock rom (get it from Sammobile, sign in and select your country and phone model)
-blazing kernel for recovery (search in XDA)
-custom rom (CM, PA, Supernexus...your choice)
-backup your data
-GApps (get the latest one)
-you must know what are you doing and dont flame/blame other member if something wrong
how to flash;
-make sure you are on latest stock rom (mine is JellyBean 4.1.2), if not like the OP, flash the latest stock rom using Odin;
*reboot your phone in Download Mode
*open Odin and in PDA option select your stock rom and then Start
*if done it will display Done and disconnect your phone, it will boot up
*if bootloop, reboot into Recovery Mode, and then wipe data and cache, and then reboot normally
-after updating your phone to latest stock rom, copy your custom rom, GApps, and Blazing kernel into external SD card, then reboot into Recovery Mode
-choose "apply update from external storage" and choose Blazing kernel, wait for it to finish update
-reboot normally, and then reboot back to Recovery Mode. this time you will notice that your recovery is different from the previous one
-select install zip > choose from external storage/sdcard 1 > and then choose your custom rom. then wait for it to finish update
-repeat the above step to install GApps, and after that reboot normally
-if bootloop, reboot back to Recovery Mode and then wipe data, cache and dalvik and then reboot
-done, now you are running on custom rom
Click to expand...
Click to collapse
and about the root, i believe that almost all custom rom rooted
Any ideas why this could happen?
What I do everytime:
Flash XXLPB with ODIN 1.85, root with CF-Root v5.2 CWM, reboot, all fine.
Then I flash for ex. Carbon ROM Nighlty, GAPPS, reboot and it's stuck at triangle screen. Can't go to recovery, only download mode works.
I also tried "old" Carbon 1.8, and even other ROMS that worked like a charm some time ago.
All started when I tried yesterday to flash 4.3 Carbon nightly over 4.2.2 (1.8) Carbon w/o wiping...
Please help as for now I'm stuck with my 3310 xD
Back to stock via Odin/download mode (you don't really have another option), make sure you do a wipe/factory reset, try flashing the rom again.
I tried 4-5 times, and always the same is coming out! Is there any minimum requirement for flashing let's say 4.2.2? Shouldn't matter, right?
It shouldn't matter but we see cases on here all the time where for whatever reason, Odin flashes don't take on the first/second.....eighth (as an example), and for whatever reason, the ninth flash works. In other words, you need to persevere. Try different stock roms for your carrier (different Android versions, not just the recent ones - but don't use 4.0.4 in case you forget when you re-root your phone & do a wipe which will brick your phone). And keep trying. There's no easy fix for these situations unfortunately (search for Hopper8's 'Odin won't flash' thread, there's stuff in that thread you can try).
Actually the ODIN flash of the stock rom always works. But then I flash a rom through CWM and it bricks...
Is there a way to flash those roms with ODIN?
No. Almost all custom roms are CWM flashable.
OK...What I suggest you do is this...
*Clean install of stock with wipe/factory reset.
*Root your phone by flashing a custom kernel like PhilZ or Siyah (or Dorimanx).
*Do not flash a separate CWM or any other mod after you've rooted the phone.
*Read the first page of the thread devoted to the rom you want to flash very carefully. Flash the rom with CWM/follow the instructions to the letter (do not use Rom Manager or the CWM app from your homescreen; boot the phone into recovery & flash that way).
If you're seeing specific errors in CWM having done those steps (And do them again now even if you've done them previously), you need to tell us exactly what's going wrong in CWM. We're not mindreaders.
Edit - Your phone isn't bricked. Bricked phones don't boot. At all.
Thanks for the detailed answer.
Actually that's what I'm doing every time!
I'm trying to install 4.3 nightly build of carbon
I tried also stable build which was working well before...
There are no specific instructions, but I think it's pretty much standard:
1. Wipe Data/Factory Reset
2. Flash zip
3. Flash GAPPS
4. Wipe Dalvik Cache
5. Reboot
Thanks!
EDIT: After flashing the custom rom the phone doesn't boot, it gets stuck at kernel panic upload mode. Once I managed to get into CWM but there I couldn't perform any action, it was freezed.
Hi Again,
it looks like everything worked fine. Maybe I had a strange version, or the CWM was to old (5).
Now I could flash what I wanted and it's not stuck at boot anymore!
Thanks for the help!
Perseverance is a beautiful thing.
Hey Guys,
I'm having a bit of an issue. Currently I was running STOCK Android 4.3 JB, have been for a while, it started to get a bit slow & I was wanting to fresh install, but also try out a 5.0 lollipop ROM. I've rooted my phone in the past and installed custom ROMs before without a problem (Revolution Remix + Cyanogenmod 11), however, I decided to try Liquidsmooth 5.0 lollipop. i followed this video,
https://www.youtube.com/watch?v=QquFDFEEKlI
http://forum.xda-developers.com/galaxy-s3/development/rom-liquidsmooth-lollipop-4-0-b1-t2980477
I downloaded both files and copied them onto my MicroSD card.
I backed up my data (contacts, images, files etc..)
Booted into "Recovery Mode", wiping Cache & factory Reset
When to install from SD, located file and it started reading/installing (sorry can't remember exactly what it did), but during process it failed. I went back into Android (had to setup again), Went and made sure Developer Mode and USB Debugging was on, still didn't work.
Went to make sure CWM was installed/update, which it said it was (possibly from previous custom installs?), tried updating, failed. It said
Went and installed 'SuperSU' from Play store, but got this error.
Decided to try re-install STOCk 4.3 JB, I
made sure USB Debugging was on
loaded Odin 3.07 (or was it 3.09) and loaded 4.3 Firmware under PDA (left everything else as is)
Started and let it do its thing. It finished/PASSED and phone restarted.
i went back into the phone, installed ROM manager & SuperSU again to give it another shot... but same problem again, getting the error above.
I'm not sure what's happened and I'm not sure what "solutions" to search for... anyone have any suggestions?
At this stage I'm thinking of just going back to STOCK 4.3, then maybe try again (either with Liquidsmooth lollipop, or, Slimkat 4.4)
Thanks guys, any help would be super appreciated,
Regards,
~ Dave
Le Widget said:
Hey Guys,
I'm having a bit of an issue. Currently I was running STOCK Android 4.3 JB, have been for a while, it started to get a bit slow & I was wanting to fresh install, but also try out a 5.0 lollipop ROM. I've rooted my phone in the past and installed custom ROMs before without a problem (Revolution Remix + Cyanogenmod 11), however, I decided to try Liquidsmooth 5.0 lollipop. i followed this video,
https://www.youtube.com/watch?v=QquFDFEEKlI
http://forum.xda-developers.com/galaxy-s3/development/rom-liquidsmooth-lollipop-4-0-b1-t2980477
I downloaded both files and copied them onto my MicroSD card.
I backed up my data (contacts, images, files etc..)
Booted into "Recovery Mode", wiping Cache & factory Reset
When to install from SD, located file and it started reading/installing (sorry can't remember exactly what it did), but during process it failed. I went back into Android (had to setup again), Went and made sure Developer Mode and USB Debugging was on, still didn't work.
Went to make sure CWM was installed/update, which it said it was (possibly from previous custom installs?), tried updating, failed. It said
Went and installed 'SuperSU' from Play store, but got this error.
Decided to try re-install STOCk 4.3 JB, I
made sure USB Debugging was on
loaded Odin 3.07 (or was it 3.09) and loaded 4.3 Firmware under PDA (left everything else as is)
Started and let it do its thing. It finished/PASSED and phone restarted.
i went back into the phone, installed ROM manager & SuperSU again to give it another shot... but same problem again, getting the error above.
I'm not sure what's happened and I'm not sure what "solutions" to search for... anyone have any suggestions?
At this stage I'm thinking of just going back to STOCK 4.3, then maybe try again (either with Liquidsmooth lollipop, or, Slimkat 4.4)
Thanks guys, any help would be super appreciated,
Regards,
~ Dave
Click to expand...
Click to collapse
First of all and most important don't use rom manager! it causes more problems than anything else.The best way to install custom roms is to use Cwm,PhilZ or Twrp to install anything!
Flash superSU zip in recovery from here >> http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1 << SuperSU forum here >> http://forum.xda-developers.com/showthread.php?t=1538053 << Technically you should not need to flash SuperSU because nearly all custom roms come with root built in so you could flash a custom recovery then wipe and flash your rom (but I can see you have been having problems doing that)
What you should do is
(1) Flash a custom recovery with Odin (Recommend PhilZ)
(2) Reboot to custom recovery
(3) Wipe phone
(4) Install custom rom (which is already rooted) from Ext SD card
(5) Reboot (If you get bootloop factory reset/ wipe cache
Also to note PhilZ recovery (which I think is better as more options and is based on Cwm) as a option to fix root in settings.
tallman43 said:
First of all and most important don't use rom manager! it causes more problems than anything else.The best way to install custom roms is to use Cwm,PhilZ or Twrp to install anything!
Flash superSU zip in recovery from here >> http://download.chainfire.eu/696/SuperSU/UPDATE-SuperSU-v2.46.zip?retrieve_file=1 << SuperSU forum here >> http://forum.xda-developers.com/showthread.php?t=1538053 << Technically you should not need to flash SuperSU because nearly all custom roms come with root built in so you could flash a custom recovery then wipe and flash your rom (but I can see you have been having problems doing that)
What you should do is
(1) Flash a custom recovery with Odin (Recommend PhilZ)
(2) Reboot to custom recovery
(3) Wipe phone
(4) Install custom rom (which is already rooted) from Ext SD card
(5) Reboot (If you get bootloop factory reset/ wipe cache
Also to note PhilZ recovery (which I think is better as more options and is based on Cwm) as a option to fix root in settings.
Click to expand...
Click to collapse
hi tallman, much appreciated for the reply
For some reason I couldnt get Philz Custom Recovery to work with odin, kept getting an error :/ . So I ended up trying TWRP, which worked, I booted into it then installed Liquidsmooth + gapps, all installed ok, but all up it was the same process you mentioned, which I greatly appreciate.
So running Liquidsmooth 5 now with TWRP recovery, though will likely give Philz recovery a shot down the track
Le Widget said:
hi tallman, much appreciated for the reply
For some reason I couldnt get Philz Custom Recovery to work with odin, kept getting an error :/ . So I ended up trying TWRP, which worked, I booted into it then installed Liquidsmooth + gapps, all installed ok, but all up it was the same process you mentioned, which I greatly appreciate.
So running Liquidsmooth 5 now with TWRP recovery, though will likely give Philz recovery a shot down the track
Click to expand...
Click to collapse
Good to hear it's working Yes it's worth persevering with PhilZ it's a good recovery although Twrp is not bad either:good: