Hi,
I know these types of questions has been asked/answered before, but I have not even by combining the different threads information managed to get a clear picture of what to do in my situation
Background info:
I inherited a samsung galaxy tab 10.1 (p7510), i.e. p4wifi, with JB installed.
It's currently running cm-10-20120816-experimental-p4wifi and clockworkmode recovery 5.8.3.1 with ROM Manager v5.0.2.1
I have SOD while charging, but everything else works fine. This makes me believe that i don't have the proper boot loader!?
What i want to do:
flash the new cm-10-20121017-experimental-p4wifi
a boot loader is also provided US_LPL_4.0.4_bootloader.zip
from: droidbasement.com/galaxy/roms/cm10/p4wifi/
Question(s):
Do I need to to take any special steps to get the correct boot loader in place (now that i'm already on cm 10 with an incorrect bootloader)?
Could i just use ROM Manager to flash both the boot loader and new cm-10-20121017-experimental-p4wifi or must i use odin?
If I need odin, do I need another recovery as well?
So the basic question is, in my situation running an older build of cm10 on a p4wifi, running an unknown boot loader and clockworkmode recovery, how do i get back on track with a correct setup of every part?
If someone could help me out with a step-by-step it would be greatly appreciated, please include links to necessary files e.g. if i first must flash a stock boot loader,recovery etc..
BR
Peter
Peppelito said:
Hi,
I know these types of questions has been asked/answered before, but I have not even by combining the different threads information managed to get a clear picture of what to do in my situation
Background info:
I inherited a samsung galaxy tab 10.1 (p7510), i.e. p4wifi, with JB installed.
It's currently running cm-10-20120816-experimental-p4wifi and clockworkmode recovery 5.8.3.1 with ROM Manager v5.0.2.1
I have SOD while charging, but everything else works fine. This makes me believe that i don't have the proper boot loader!?
What i want to do:
flash the new cm-10-20121017-experimental-p4wifi
a boot loader is also provided US_LPL_4.0.4_bootloader.zip
from: droidbasement.com/galaxy/roms/cm10/p4wifi/
Question(s):
Do I need to to take any special steps to get the correct boot loader in place (now that i'm already on cm 10 with an incorrect bootloader)?
Could i just use ROM Manager to flash both the boot loader and new cm-10-20121017-experimental-p4wifi or must i use odin?
If I need odin, do I need another recovery as well?
So the basic question is, in my situation running an older build of cm10 on a p4wifi, running an unknown boot loader and clockworkmode recovery, how do i get back on track with a correct setup of every part?
If someone could help me out with a step-by-step it would be greatly appreciated, please include links to necessary files e.g. if i first must flash a stock boot loader,recovery etc..
BR
Peter
Click to expand...
Click to collapse
You should be fine just flashing the new CM 10 build from Pershoot. If you want to update your bootloader you can do that too but I don't remember reading about any change in requirements from the earlier CM 10 build as far as the bootloader is concerned. What makes you think you are using an "incorrect" bootloader to begin with?
Always a good idea to have the stock firmware from Samsung to flash in Odin in case anything breaks. Remember if that happens to flash the ROM with Odin but then also do a factory reset afterwards.
suleimankhan said:
You should be fine just flashing the new CM 10 build from Pershoot. If you want to update your bootloader you can do that too but I don't remember reading about any change in requirements from the earlier CM 10 build as far as the bootloader is concerned. What makes you think you are using an "incorrect" bootloader to begin with?
Always a good idea to have the stock firmware from Samsung to flash in Odin in case anything breaks. Remember if that happens to flash the ROM with Odin but then also do a factory reset afterwards.
Click to expand...
Click to collapse
I was looking at the post in
http://forum.xda-developers.com/showthread.php?t=1787399&page=188 to page 203
And there was a lot of talk about having the correct boot loader or else strange flickering could appear, and as i interpreted (or maybe misinterpreted) it, shutdown while charging or SOD while charging, indicated that you are using the wrong boot loader?
So you are saying; as long as the previous build is running okay, I should be fine using ROM Manager / "clockwork mode" to flash the files from Pershoot?
Is it also okay to flash the bootloader using the ROM Manager / clockwork as well? (flash order: bootloader->cm->gapps)
Sry, if everything is just confusion from my part, it was 2 years since i previously flashed a custom ROM..
All the talk about matching boot loader with a certain build made me uncertain. I have always just considered the boot loader to be just the "kick starter" for the actual ROM/CM/OS "binary". But comments in the thread-posts indicating flickering/charge-errors is caused by having the incorrect boot loader made me uncertain about if I was running the correct loader (as i have charging shutdown problems)...
Is there a way of checking my version of the boot loader and/or making sure I have an unlocked boot loader (or is it unlocked for sure as I'm already running a custom ROM?)
Why all the talk about using odin? Is it just that people tend to find odin better than ROM Manager / Clock work mode or do they actually do different things?
Any answers sorting out the thoughts of a somewhat Custom-ROM-noob, whom has just risen from the ashes after sleeping for two years, would be greatly appreciated!
Related
My end goal is to have CyanogenMod 7.1 stable or the RC of CM 7.2
I have AT&T Samsung Galaxy S II that is running Android 2.3.4 rooted via
http://forum.xda-developers.com/showpost.php?p=18859438&postcount=199
Current Version info is:
Model #: SAMSUNG-SGH-I777
Baseband version: I777UCKH7
kernel version: 2.6.35.7
Build# GINGERBREAD.UCKH7
I then installed Rom Manager Premium from the market and thru there installed the CWM Recovery 5.0.2.6
I downloaded the TeamHacksung CM7.2 RC I have also tried the CM7.1 stable and gets same results which are
The phone boots in CWM Recovery and when I choose ANY option I get the CWM logo and the device gets stuck there to get device back up. I have to force into into ODIN and flash the ROM I'm on which then enables me to boot back to where I was before booting into CWM Recovery.
I have searched the forums and can't find a solution to this with the ATT version of this device
Please help
Your issue probably stems from ROM manager. It does not play well with sgs2. Recommend removing that thing either way.
Secondly have you tried flashing cm then when it boots into cwm flashing it again without wiping.
Running ICScrewD ROM
jivy26 said:
Your issue probably stems from ROM manager. It does not play well with sgs2. Recommend removing that thing either way.
Secondly have you tried flashing cm then when it boots into cwm flashing it again without wiping.
Running ICScrewD ROM
Click to expand...
Click to collapse
How do I flash CM w/o using CWM Recovery ? I never get to the option of being able to flash CM inside CWM Recovery mode.
Is it possible to flash CM w/ Odin or Hemidall?
EDIT: I'm reading your FAQ now and found the reply where it was suggested to use HOME for item selection . will try that and more review of your FAQ - Thank you
update: I have root + installed cwm with adb
all from http://forum.xda-developers.com/showthread.php?t=1311081
but now no freaking key press combo seems to boot me into cwm recovery any ideas?
power off completely
hold volume up, down and power until SGH-i777 shows up, continue holding until it power cycles again
when that shows up for the second time, release all 3 buttons and wait. If the AT&T boot animation starts, you messed up, so try again
if successful, you will be in CWM
I do that but no love the only difference is mine shows i9100 not 777
under settings -> about phone
Model# SAMSUNG-SGH-I777
Android version 2.3.4
Baseband version I777UCKH7
kernel version
2.6.35.7
Build# GINGERBREAD.UCKH7
is this just a pebcak error on my part or something else? I do not release all 3 till the model # logo appears for 2nd time then i get att crap
Actually it should just say Samsung Galaxy SII at the initial boot up.
If it says something different, you may have an issue....
Make sure that you're keeping all three buttons pressed firmly until the SECOND TIME that the logo comes up, and when it comes up, let go of all 3 immediately.
I get
Samsung Galaxy SII
GT-I9100
and no cwm recovery love
does it / should it make any difference if usb cable is plugged in or not?
issue solved via
./adb reboot recovery
EDIT: okay good you got it solved. I still don't know WHY your boot image is different, but it's okay.
Anyways...I had the stuff below typed out already so I'll just leave it
Boot up, back up everything you would need, then do factory reset
Use that guide again
use the following steps: 2c, then 3c
Then try going into CWM. Also, your boot image should be changed back to the normal one. Might have to do with the fact that you tried to use ROM Manager initially, it causes problems on this phone
once i got into cwm recovery via adb i tried to do a backup and got
error when backing up /system
phone is now booted all the way up ..is flashing via the guide in 2c sufficient for the factory reset or do you have other method? phone currently has the 2c rom loaded plus the CWM kernel ( SGH-I777_ClockworkMod-Recovery_5.0.2.3.tar)
can't find link where I got the cwm kernel from
avidmovies said:
EDIT: okay good you got it solved. I still don't know WHY your boot image is different, but it's okay.
Click to expand...
Click to collapse
Flashing a custom kernel via Odin/Heimdall will trigger the custom kernel warning - a big yellow triangle and the boot screen saying GT-I9100.
To the OP - you say you have searched, but nearly everything you have asked is answered in the FAQ. What isn't in the FAQ is in the first post of codeworkx's CWM recovery thread. Seriously, it's NOT that hard to search, the Development forum has only four pages of threads, and the answer to some of your questions is right in the thread titles of the relevant threads.
Entropy512 said:
Flashing a custom kernel via Odin/Heimdall will trigger the custom kernel warning - a big yellow triangle and the boot screen saying GT-I9100.
To the OP - you say you have searched, but nearly everything you have asked is answered in the FAQ. What isn't in the FAQ is in the first post of codeworkx's CWM recovery thread. Seriously, it's NOT that hard to search, the Development forum has only four pages of threads, and the answer to some of your questions is right in the thread titles of the relevant threads.
Click to expand...
Click to collapse
point taken - I have looked at so many threads and comments that I guess I overlooked some of the very answers i was / am searching for just for the record I'm not getting the yellow triangle during boot - will go back to digging
was asking here as I saw so much info was trying to get consolidated answers from folks who know more than I do and might could tell where i may have messed up
IT WORKS!! I'm finally where I want to be CyanogenMod 7.1 running !!!!! Thanks to all who helped on this thread !!!!
i have a atrix and cannot for the life of me get the following rom to load. [ROM] CM7 Mod ICS FINAL I have followed several different installation instructions but after loading the main file, the google updates, and fixes, have i been able to reboot. It just hangs at the screen that says unlocked.
I have used rsd lite to reload the latest stock file and the phone returns to its normal unrooted self.
What could i be doing incorrectly.
If anyone knows or has a FOOLproof method for installing this rom any help would be appreciated.
I never used to have any trouble changing roms on my TILT phone.
I have tried for several days to get this to work. any expertise would be most appreciated.
So you unlocked your bootloader and you are using the latest cwm recovery?
questions
first off, thanks for replying.
I beleive i am using the current of both.
just in case i am not could you tell me the most current boot unlocker and where what and how on the cdm recovery. i must be doing something a little wrong in these 2 areas, everything else seems very straight forward.
mgoforth said:
first off, thanks for replying.
I beleive i am using the current of both.
just in case i am not could you tell me the most current boot unlocker and where what and how on the cdm recovery. i must be doing something a little wrong in these 2 areas, everything else seems very straight forward.
Click to expand...
Click to collapse
Well if you have "unlocked" when you start up your phone your bootloader is unlocked. If that's the case then go ahead and download "Rom manager" from the market and flash it from there.
I was an eager beaver and flashed my i777 with the new leak before it was released without a custom bootloader. After finding out it did indeed have one I flashed my kernel back to codeworkx's Kernel with the ClockworkMod Recovery 5.0.2.3 and loaded a backup image I made of cyanogenmod 7.
I flashed used Tasks image of the leak (without bootloader) and am currently running that.
My question is whether or not that custom bootloader was removed at any point during this process. If not, should flash back to stock to remove it and then repeat the steps to flash tasks firmware? Thanks for the patience.
custom bootloader?
avoid flashing bootloaders whenever possible. If your phone is working okay right now, leave it.
hottpockets said:
I was an eager beaver and flashed my i777 with the new leak before it was released without a custom bootloader. After finding out it did indeed have one I flashed my kernel back to codeworkx's Kernel with the ClockworkMod Recovery 5.0.2.3 and loaded a backup image I made of cyanogenmod 7.
I flashed used Tasks image of the leak (without bootloader) and am currently running that.
My question is whether or not that custom bootloader was removed at any point during this process. If not, should flash back to stock to remove it and then repeat the steps to flash tasks firmware? Thanks for the patience.
Click to expand...
Click to collapse
There are no custom bootloaders. Since you flashed the one click ics leak you now have the secondary bootloader that came with that package. codworxx kernel and tasks' ics leak have no bootloaders and will not change them in any way.
As long as the secondary bootloader does not suffer from any corruption during the flash process and your phone boots up normally after flashing it, it will not cause you any problems (other than resetting the custom binary counter if that ever becomes an issue for you).
The danger of flashing packages with bootloaders is if something happens during the flash process to corrupt the bootloader it will hard brick your phone, as in dead paper weight brick.
So don't ever flash any package with bootloaders unless you are absolutely sure want too flash them and are aware of the risk.
Sent from my SGH-I777 using XDA Premium HD app
Sorry I'm a noob at all of this. Successfully rooted my phone today thanks to Honsoon2000's excellent tutorial and toolkit. Then I went to install Android Revolution, which appeared to go successfully and then after I flashed the kernel the phone wouldn't load and just hangs at the quietly brilliant screen. I followed Honsoon's tutorial to the T (or so I thought) and everything went perfectly until right at the end when I flashed the kernel. I can make it back to the bootloader screen though it says "failed to load usb master mode". I can still make it into fastboot and recovery mode...tried recovery, and the process seemed to go sucessfully, but the phone still wouldn't load after...tried reinstalling ARHD-- it's still on the sd card and the install procedure still goes off without a hitch, but the phone still won't load. I've searched around and tried everything I can, to no avail. Any help would be muchly appreciated, and I apologize in advance for being a noob wasting people's time.
Edit: For example, when I follow the steps outlined in the FAQ it asks me to enter the command 'fastboot flash boot boot.img' , but when I do it says 'error: cannot load boot.img'.
Edit 2: So I put my boot.img file from Android Revolution into the data directory of the rooting toolkit and was able to complete the above flashboot command. I was also able to install the ROM off my SD card...however the phone still hangs on the Quietly Brilliant screen...I can't even power the phone down...whenever I try it just reboots...frustrating...really hoping someone can help me...cheers.
Before you begin, make sure that the drivers for the One X+ are installed.
Place the boot image being used on the computer's hard drive.
Boot in to recovery and flash the ROM.
When that is done, boot in to bootloader and connect the phone to the PC via a USB cable.
If the phone isn't in fastboot mode already, use the volume keys to highlight the word "fastboot", then press the power button.
Now, there should be text at the bootloader screen that says "Fastboot USB".
Finally, use the toolkit or command line and flash the kernel with the fastboot command.
This should successfully flash the ROM and the kernel. Make sure you full wipe before flashing a new ROM. If you can't seem to get the new ROM booting, the final choice is to relock the bootloader and run a RUU.
Which phone version you do own? International or AT&T / TELUS?
Did you flashed the correspondant boot.img? Did you cleared the cache? ( fastboot erase cache)
I'm trying to run an RUU but it keeps saying the battery isn't charged enough to flash anything...and this after it's been plugged in all day. Oh dear I think my phone might be done...really sucks :/
Also, it won't let me power the phone down-- every time i try it shuts the phone off briefly and then opens back up to the bootloader screen.
Fixed thanks to sarcasticphoenix. Cheers.
OK so I've tried 3 times to flash a new ROM onto my phone (Android Revolution twice and Eleganzia once) using Honsoon's toolkit...I've followed every instruction to the T as far as I can tell and all 3 times the process has gone perfectly right until the end when I flash the kernel...after that when I reboot the phone it just hangs at the Quietly Brilliant screen. I know how to relock the bootloader, flash the custom rom and get my phone back...but I really want to know what I'm doing wrong so I can install a custom ROM. I know I'm using the right ROM for my phone and am wondering what gives. Being driven crazy here...any ideas what's going wrong here would be helpful. BTW on the last attempt right after I finished and the phone hung I went into the boot loader and followed the instructions in the FAQ for fixing a bootloop...still nothing.
Edit: Solved my problem-- I managed to successfully load eleganzia...the only thing i did differently the last time was flash the kernel BEFORE installing the ROM off the SD card.
jrockwell said:
OK so I've tried 3 times to flash a new ROM onto my phone (Android Revolution twice and Eleganzia once) using Honsoon's toolkit...I've followed every instruction to the T as far as I can tell and all 3 times the process has gone perfectly right until the end when I flash the kernel...after that when I reboot the phone it just hangs at the Quietly Brilliant screen. I know how to relock the bootloader, flash the custom rom and get my phone back...but I really want to know what I'm doing wrong so I can install a custom ROM. I know I'm using the right ROM for my phone and am wondering what gives. Being driven crazy here...any ideas what's going wrong here would be helpful. BTW on the last attempt right after I finished and the phone hung I went into the boot loader and followed the instructions in the FAQ for fixing a bootloop...still nothing.
Edit: Solved my problem-- I managed to successfully load eleganzia...the only thing i did differently the last time was flash the kernel BEFORE installing the ROM off the SD card.
Click to expand...
Click to collapse
That's usually what I do first, flash the kernel and then install the zip via recovery
Sent from my HTC One X+ using xda premium
Which kernel are you referring too? Actually there is one or two kernels available but only for the International version, not the AT&T/TELUS which you seem to have.
I strongly suspect that your boot looping was because you didn't flash the boot.img file correctly or not at all. And you don't seem to install the good ROM version for your phone.
Elegancia has two ROM versions one for International and one for AT&T/TELUS users.
ARHD is for International users.
Please read Q12 of the FAQ.
Lucky Thirteen said:
ARHD is for International users.
Click to expand...
Click to collapse
Lol...yeah I don`t know how I missed that. I ended up getting elegancia successfully flashed and loaded so all is well. In retrospect this was a good experience because there`s nothing like having to get yourself unforked from a bad situation to gain an understanding of what`s going on. Cheers.
I have a couple questions and since I`m not allowed to post yet in the elegancia thread I'll try in this thread first:
1) An elegancia question: Is there a way (widget) to toggle data roaming on and off in this ROM?
2) Is there a way to tweak settings (transparent pull down, selection of launcher etc.) without wiping and reflashing the ROM?
3) What are people's favorite launcher for that ROM? I tried Atom but it was just a guess because I hadn't heard of any of them. I like it so far but am curious about the others.
Hi, this is my first post. I'm a total noob in customizing phones and since my phone is quite old, all the information I can find is years old, talking about file versions that don't exist anymore, or became outdated since there are so many different versions of android.
I have been trying to find a good guide to help me do the correct steps to follow to flash Cyanogenmod. I might try the latest 12.1, and then see if I like it.
This is what I have so far:
- international i9100, I live in panama if that's relevant to any help I need
- stock ICS 4.0.3 (with XWLP7 kernel)
- used superoneclick to root, it installed CMW PhilZ touch 6.0.1.7 (I think, can't remember the last digit.)
- used "galaxy s unlock" app to unlock the phone
I downloaded this: philz_touch_6.07.1-i9100 from d-h.st/hUX, sorry I can't post the links correctly for being a new user.
I just made a backup before i will attempt to load philz touch 6.07.1. I read that I need to have a kitkat compatible recovery, is this one compatible. Can I simply flash it or do I need to do anything specific before.
I am trying to follow the steps explained in wiki.cyanogenmod.org/w/Install_CM_for_i9100, but the warnings scare me a bit, can someone please explain the workarounds, thanks.
So, what I'd like to know is the specific steps for my version of android to make it migrate to CM12.1, and what to do about the warnings (should i find a custom kernel, do i need to backup anything else, I read also that the recovery I have doesn't backup efs, so how can I do that?)
Thanks a lot for taking your time to help me out.
@milen_506
So when you reboot into recovery, you have philz recovery?
If yes, all you need to do is install a newer recovery such as the one from this post. Once you flash it, reboot straight back to recovery(you will get a bootloop if you try to reboot into the system). This newer recovery is compatible with the latest versions of android and gapps, so just need to have the rom .zip and gapps(if you want play store/services) .zip ready to flash before you upgrade this recovery. Do a nandroid backup before you flash the new rom/gapps
There are several ways to backup efs, HERE is a link to one option
And as far as custom kernels, you are probably better off sticking to the kernel that comes with the rom unless you are comfortable adjusting kernel settings and you know what you are doing. It would be easy to mess things up if you didin't have a basic knowledge of the changes. Also with cm12/LP roms on the S2, custom kernels are only starting to be developed and are a little unstable for some users at this stage.