Bricked G2x trying to install Eaglesblood HELP! - T-Mobile LG G2x

Hi everyone, Im relatively new to the whole flashing and custom rom scene. I rooted my wind mobile (Canadian carrier) LG-P999 and ran CMR before trying to flash EGB. I used the instructions on the forum post to install EGB. In the installation process however, It looked like Gapps were already installed, I installed the Gapps I was told to download here http://forum.xda-developers.com/showthread.php?t=1575199 again anyways. My phone will now not start, all that happens when I press the power button is the LG logo flashes, and then the Eaglesblood logo flashes then the phone shuts down. I have the CWM recovery file saved on my computer. Can someone help me unbrick my phone? thanks in advance, and please excuse my horrible grammar, I'm quite terrified right now.
EDIT: I messed around with my phone, and I am able to get into the Android System Recovery. Should I wipe data/factory reset? Will that solve my issues?

First get the rom you want to install on a sd card boot into recovery and wipe and install. If you factory reset it still will try and load eaglesblood. If using a cm 7 rom like eb or hellfire flash gapps right after the rom. Hope this helps
Sent from my LG-P999 using xda premium

How I do it with no problems
monte666 said:
First get the rom you want to install on a sd card boot into recovery and wipe and install. If you factory reset it still will try and load eaglesblood. If using a cm 7 rom like eb or hellfire flash gapps right after the rom. Hope this helps
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Anytime you flash rom, I recommend these steps. (Some may argue that it's over kill)
Get a Copy of Titanium Backup Pro.apk
Batch back-up all your user apps if you so wish. (These first two are optional, but I highly recommend)
Copy ROM, Kernel, and Gapps to MicroSD card. (EXTERNAL)
Boot into CWM.
Do a Wipe data/factory reset
Wipe cache partition
select advanced-->wipe dalvik cache
mounts and storage-->format /system
Install zip from sdcard (not the apply update option!)
select your ROM, flash
select you kernel, flash,
<optional, if your on March BB and depending on ROM, you may need to flash new baseband.zip, forum search for it)
select gapps, flash
Reboot!
Sometimes upon booting you made need to wait 5-10min for phone to come up and be speedy. Be patient.
Hope some of this helps since your able to boot into CWM, which means your not bricked, yet. I;ve been there in a loop, called it soft bricked. Performed all of the above steps, never had the problem occur since. I jump between two GB 2.3.7 ROMS and two ICS ROMs with ease.

Related

Possible Bricked G2x No NV Flash Back Up

I was flashing CM 7 nightly 49 and now my phone is stuck on the LG logo, how do I fix?
After reading all the steps req'd to "Flash a Rom" and "recovery" process, what part isn't working?
N1user said:
After reading all the steps req'd to "Flash a Rom" and "recovery" process, what part isn't working?
Click to expand...
Click to collapse
After going through the NV flash process and getting to the last step that says
Keep holding them, as soon as you see "ANDROID" in Green with the new boot logo let go of the buttons.
From there it goes into boot recovery. I then choose from one of the roms I have on my SD card, it loads okay but then when I try to reboot it hangs up on the LG logo again
What am I doing wrong
we def need more info then that like what recovery how did u install the rom did u wipe data then cache then dalvik? then install rom and gapps? did u install any kernels previously? and this is probably going to get moved it should be in general
ok when u go into recovery do u wipe data factory reset, then cache, then go to advanced and wipe dalvik then install rom and gapps and it should boot up fine, did u make a backup of ur stock rom first?
sarni84 said:
ok when u go into recovery do u wipe data factory reset, then cache, then go to advanced and wipe dalvik then install rom and gapps and it should boot up fine, did u make a backup of ur stock rom first?
Click to expand...
Click to collapse
Damn. for one month on XDA you sure do have a lot of posts
On topic: I'm assuming you forgot to fully wipe before flashing the new rom.
If you can get into recovery, it's not bricked.
Read the install directions, you missed a step or got a bad download.. Or a bad build, as they are nightlys...
In recovery, do factory reset, then mounts and storage, select format system. Then install the rom.
Also, get the stock nandroid and put it on your card so you can drop to a known good setup.
I had back it up using rom manager but its on another computer. I took had gotten a SD card with more storage and never transferred it.
omarsalmin said:
Damn. for one month on XDA you sure do have a lot of posts
On topic: I'm assuming you forgot to fully wipe before flashing the new rom.
Click to expand...
Click to collapse
wow i do huh i cant stay away
Goldbatt said:
I had back it up using rom manager but its on another computer. I took had gotten a SD card with more storage and never transferred it.
Click to expand...
Click to collapse
You could copy the backup from your computer and make a folder called clockworkmod/backup/ on your new SD and put the backup file in that folder. When you go into recovery, backup and restore. restore - it should be visible. Select it and you should be OK - IF your backup is good.
If not, download a ROM and Gapps with your computer and put them in the root of your SD. Then after a full wipe, flash them.
If you have the latest Recovery, you can mount storage and then cut and past to your device while connected. If not, or if you have any problems moving them, just take it out and do it while it is plugged in your computer.
You have several options - so one of them will work.
Want to thank all you guys. I got it working again.
Sent from my LG-P999 using XDA App
Moved to proper forum.

All AOSP/CM ROMs bootlooping [FIXED]

All AOSP or CM ROMs are bootlooping. It gets to a certain stage in the boot animation, and then freezes for about 20-25 secs, then reboots and does the whole process again.
This only happens on AOSP or CM based ROMs. Doesn't happen on Sense based ROMs.
Anyone have any suggestions on how to solve this? I'm going to pull a logcat as soon as I can.
Thanks,
Phil
Probably wrong firmware.
Sent from my HTC Pyramid using xda premium
stonew5082 said:
Probably wrong firmware.
Sent from my HTC Pyramid using xda premium
Click to expand...
Click to collapse
So what firmware would I need for AOSP/CM based ROMs?
Steps to install rom properly after rooting and installing clockworkmod recovery.
For Gingerbread roms, 1.17 or 3.12, if you haven't touched the firmware, yours is 1.17.
For ICS roms, flash either 3.12 or 3.24. 3.12 is backwards compatible with GB roms, but 3.24 offers better performance.
Once you have the right firmware, put the rom onto your SD card and reboot into the recovery. There's an option to wipe data and factory reset, usually called "Wipe data/factory reset". Run that once, then install the rom from the zip that you copied earlier and that's about it. If you install anything cyanogen, make sure you flash Google Apps to get the market.
Roms should only take about 2 to 3 minutes to boot for the first time.
Possible issue you're having: Wrong firmware for the rom or you didn't wipe data before installing.
sshede said:
Steps to install rom properly after rooting and installing clockworkmod recovery.
For Gingerbread roms, 1.17 or 3.12, if you haven't touched the firmware, yours is 1.17.
For ICS roms, flash either 3.12 or 3.24. 3.12 is backwards compatible with GB roms, but 3.24 offers better performance.
Once you have the right firmware, put the rom onto your SD card and reboot into the recovery. There's an option to wipe data and factory reset, usually called "Wipe data/factory reset". Run that once, then install the rom from the zip that you copied earlier and that's about it. If you install anything cyanogen, make sure you flash Google Apps to get the market.
Roms should only take about 2 to 3 minutes to boot for the first time.
Possible issue you're having: Wrong firmware for the rom or you didn't wipe data before installing.
Click to expand...
Click to collapse
I do a superwipe and data wipe before installing, so it can't be that.
I'll try your solution now, thanks a lot!
I'm more of an app dev than firmware/ROM/kernels
redbullcat said:
I do a superwipe and data wipe before installing, so it can't be that.
I'll try your solution now, thanks a lot!
I'm more of an app dev than firmware/ROM/kernels
Click to expand...
Click to collapse
MAKE SURE MAKE SURE MAKE SURE your MD5s match. Flashing a firmware can brick your phone extremely easily so make sure your md5s match and that you have sufficient battery life left.
Also you will not be able to go back into bootloader without it asking if you want to flash the firmware if its still on your sd. If it asks you can say no but it will just reboot you into your system so if you have no system to boot into youll be stuck and will have to pull your sd card out and then reinsert it when in recovery.
It worked! Thanks guys, I owe you one

[Q] First time flashing NS i9023 (serious flasher from SGS,SGS2)

Hey!
First let me say that I know all about flashing SGS and SGS2. Im a proud owner of SGS1 from day 1.
Last week I decided to finally flash my brothers i9023 so I flashed stock 4.0.3 with stock recovery. Then we wanted to flash some XDA stuff and I don't understand these guides...
I found one guide where you get superuser access with one click and usb cable, I did that, then I flashed CWM through Rom manager and flashed 4.0.4 from evilisto (v1.1) and it worked. Now I'm trying to flash some others, like nuhetri reloaded or pixel rom and I'm always getting stuck at boot animation. It just keeps "working" and nothing happens for 5+ minutes.
What am I doing wrong? Please help!
Best Regards
Luka
(in general)in recovery wipe data factory reset, format cache, davlik cache, system, boot. then flash new rom.
with nuhetri i think there is a bug where your not supposed to wipe data coming from another rom only davlik cache and cache then flash nuhetri
sean1984 said:
(in general)in recovery wipe data factory reset, format cache, davlik cache, system, boot. then flash new rom.
with nuhetri i think there is a bug where your not supposed to wipe data coming from another rom only davlik cache and cache then flash nuhetri
Click to expand...
Click to collapse
Hey and thanks for such quick reply!
I did all these now, rebooted to recovery (from CWM) and flashed this Fully Touched:
http://forum.xda-developers.com/showthread.php?t=1411734
Its stuck at boot image for 5 minutes now.
What now?
your using updated version of cwm? http://forum.xda-developers.com/showpost.php?p=22044793&postcount=82
steps
put rom on sd card
reboot into cwm recovery
wipe data, cache, davlik cahe, and format system and boot
install zip from sd card
choose rom you put on sd card
should say install from sd complete or something like that
reboot system now
let it boot into new rom (should not take more than 3-5 min)
edit: just seen this post in the rom thread your trying to flash http://forum.xda-developers.com/showpost.php?p=23255456&postcount=389 try redownloading again
sean1984 said:
your using updated version of cwm? http://forum.xda-developers.com/showpost.php?p=22044793&postcount=82
steps
put rom on sd card
reboot into cwm recovery
wipe data, cache, davlik cahe, and format system and boot
install zip from sd card
choose rom you put on sd card
should say install from sd complete or something like that
reboot system now
let it boot into new rom (should not take more than 3-5 min)
edit: just seen this post in the rom thread your trying to flash http://forum.xda-developers.com/showpost.php?p=23255456&postcount=389 try redownloading again
Click to expand...
Click to collapse
I did all that before... Im going to redownload, maybe its corrupted but I doubt it. Is it maybe because I have locked bootloader or something? Beacause I didnt use that long guide with "android SDK" in General, but some other very quick guide. Just plug USB, enable debugging and run some script and thats it.
devianceluka said:
I did all that before... Im going to redownload, maybe its corrupted but I doubt it. Is it maybe because I have locked bootloader or something? Beacause I didnt use that long guide with "android SDK" in General, but some other very quick guide. Just plug USB, enable debugging and run some script and thats it.
Click to expand...
Click to collapse
do yourself a favor, do it the right way the first time and save yourself headaches in the future. its not hard. fastboot oem unlock(bootloader), flash a custom recovery, flash a custom rom(and gapps) via the recovery, then boot up. thats it.
If you are more of a visual type of guy I suggest going on YouTube and search "zedomax". He has some really simple videos on how to root your nexus s, he has a couple videos on how to root but make sure its for a GSM nexus.
Simms got all in a simply way.
Unlock boot loader
Install or flash cwm
install the new stuff from SD card
reboot
Can anyone tell me or please provide a link to what unlocking bootloader does please.
Best Regards
Excuse my ignorance, I'm pretty new to this and I might not be of any help at all... but is it even possible to flash a custom recovery without unlocking the bootloader on the Nexus S?
I followed the instructions found on the NexusShacks.com website (How to root Nexus S or Nexus S 4G on ICS or Gingerbread) without any issues at all (sorry, can't post links due to low postcount :/)
No problems for me, I had zero experience with this sort of stuff but I have flashed a new ROM a every few days now without any issues whatsoever.
devianceluka said:
Can anyone tell me or please provide a link to what unlocking bootloader does please.
Best Regards
Click to expand...
Click to collapse
use this link: http://nexusshacks.com/
its complete with the files, pictures, video and some ics roms that you can try. let me know if you have any other question

[Q] Updating ROM via GooManager

Hi All,
I have posted this on the GooManager thread but there hasn't been much activity there recently so asking here as well. Noob question on GooManager...I have the AOKP rom installed on my Sensation and GooManager notifies me of updates to my ROM every now and then. I just want to know if updating my ROM build with GooManager will reset all my custom ROM settings and preferences or will they all be preserved? I'd like to keep my ROM up to date but if it means spending all the time again to setup my preferences and icons/widgets/home screens etc. then I'd rather stick with what I have.
TIA!
I'd recommend to use GooManager only to download the newest ROM and flash it from recovery.
I asume you're using AOKP Swagger from frankenstine, the same I use.
I just download the update from GooManager, boot to recovery, flash ROM, gapps and 4.2 stuff and are ready to go.
All my settings are their after updating - only AdAway needs a reconfiguration and a reboot (and I need to set my alarm clock since I'm overwriting that). Basically you keep all your settings except those you made to the kernel.
Regards
lolmachine4 said:
I'd recommend to use GooManager only to download the newest ROM and flash it from recovery.
I asume you're using AOKP Swagger from frankenstine, the same I use.
I just download the update from GooManager, boot to recovery, flash ROM, gapps and 4.2 stuff and are ready to go.
All my settings are their after updating - only AdAway needs a reconfiguration and a reboot (and I need to set my alarm clock since I'm overwriting that). Basically you keep all your settings except those you made to the kernel.
Regards
Click to expand...
Click to collapse
Oh perfect, yes indeed I am using that exact ROM.
OK so when I boot to recovery, I shouldn't do any wiping? Just simply flash the new file? Will the updated gapps package be in the download I get from GooManager?
freddysensation said:
Oh perfect, yes indeed I am using that exact ROM.
OK so when I boot to recovery, I shouldn't do any wiping? Just simply flash the new file? Will the updated gapps package be in the download I get from GooManager?
Click to expand...
Click to collapse
I only wipe dalvik & cache after each update.
I can't say something about what GooManager downloads as "gapps", I use some I downloaded some weeks ago + some old version of 4.2 stuff. I might need to update my flash-setup too
lolmachine4 said:
I only wipe dalvik & cache after each update.
I can't say something about what GooManager downloads as "gapps", I use some I downloaded some weeks ago + some old version of 4.2 stuff. I might need to update my flash-setup too
Click to expand...
Click to collapse
Thanks lolmachine, for the benefit of anyone who might have the same question as me the following worked:
- Downloaded latest build of my AOKP Rom via GooManager
- Downloaded latest gapps package for my ROM via GooManager
- Boot to Recovery
- Flash new ROM file and then gapps package
- Restart.
My only question is, I didn't wipe davlik and cache so should I, and what difference does it make if I don't?
I used Goo the other day to flash, ummm, bugger, can't remember if it was an update or a new rom.
Oh now I remember, the latest one was an update to Bruce's Rom. I do believe when I tapped flash rom it booted to recovery (the one it installs) and I may have had to select "Install" from there, don't think so though. Either way, I used Goo to handle the install.
I didn't do a wipe. From what I've picked up, wiping is a good way to cover your butt. So if you're having issues and didn't wipe, you go back and do it all again with a wipe. Doing the wipe to start with means you can eliminate those types of issues from the start.
Someone can correct me if I'm wrong (which I probably am )
Hi there, I also received an update to my ROM via Goo Manager. It is CyanogenMod 10.1 by Albinoman887 for my HTC Sensation XE. I am using the EXT4 bootloader. I just installed it a few nights ago so I am completely new to rooting. My question is that there is no option to wipe dalvik cach. EXT4 just says wipe cache, wipe data and wipe system. Does wipe cache wipe dalvik cache as well. Also do I need to re-flash gapps as well after updating and will this wipe my gmail accounts etc?
Thanks,
Adam
thisisadamh said:
Hi there, I also received an update to my ROM via Goo Manager. It is CyanogenMod 10.1 by Albinoman887 for my HTC Sensation XE. I am using the EXT4 bootloader. I just installed it a few nights ago so I am completely new to rooting. My question is that there is no option to wipe dalvik cach. EXT4 just says wipe cache, wipe data and wipe system. Does wipe cache wipe dalvik cache as well. Also do I need to re-flash gapps as well after updating and will this wipe my gmail accounts etc?
Thanks,
Adam
Click to expand...
Click to collapse
You want to select "wipe dalvik+cache" option when you flash an update.
There's no need to flash gapps after a ROM update.
Sent from my Ouya
AndroidSupporter318 said:
You want to select "wipe dalvik+cache" option when you flash an update.
There's no need to flash gapps after a ROM update.
Sent from my Ouya
Click to expand...
Click to collapse
Thanks very much, downloading it now.
Help
im using albinoman's jelly bean rom
excuse me for noob doubts but
1) goo manager shows i have an update, so ive downloaded it. its a zip just like the rom n not just a small update. i have downloaded it now what should i do?
2) if i have to go to the recovery and flash the zip then i have to wipe only the cache right? Im using 4ext recovery.
3) will all my apps get uninstalled? what about the app data?
4) what about gapps? i have a gapps zip file, will i have to flash it again after the update?
Please reply thanks
I finally rooted phone after silly VMUNE7 thing on Verizon but after I get the install openrecoverscript and hit reboot recovery it does not go to teamwiz bootload instead I get something with a green driod on the bottom saying downloading but above it saying in red can't download Odin mode?? Please help I want to run cleanrom for better battery and less bloatware and keep my touchwiz. :crying:
all3rd said:
I finally rooted phone after silly VMUNE7 thing on Verizon but after I get the install openrecoverscript and hit reboot recovery it does not go to teamwiz bootload instead I get something with a green driod on the bottom saying downloading but above it saying in red can't download Odin mode?? Please help I want to run cleanrom for better battery and less bloatware and keep my touchwiz. :crying:
Click to expand...
Click to collapse
sorry man but i think you are talking for a samsung device am i right?
if yes then this is only for sensation/XE/4G devices
yasho170 said:
im using albinoman's jelly bean rom
excuse me for noob doubts but
1) goo manager shows i have an update, so ive downloaded it. its a zip just like the rom n not just a small update. i have downloaded it now what should i do?
2) if i have to go to the recovery and flash the zip then i have to wipe only the cache right? Im using 4ext recovery.
3) will all my apps get uninstalled? what about the app data?
4) what about gapps? i have a gapps zip file, will i have to flash it again after the update?
Please reply thanks
Click to expand...
Click to collapse
Simple.
Go to recovery.
For s-on you must enable smartflash.
Do a nandroid backup.
Dirty flash the update (meaning flash over the previous rom without wiping).
Dirty flash gapps (signed only).
Wipe cache + dalvik.
Reboot.
If it can't boot/run properly then you can just restore the backup or do a clean flash.
First off I'm not experienced in any way, got my Sensation unlocked, rootet and installed Sultanxda's 4.4.2 ROM for sensation. I'm on S-On, too, if anyone wonders.
Updating didnt affect my apps as far as I can tell. Everything seems to be the way as before and everything seems to be working.
What I did was download the ROM manually since the download with goomanager didn't work. I downloaded gapps as backup because I didnt have the zip on my SD, just in case anything would go wrong.
You only need to boot into recovery, with S-On make sure smartflashing or something like that is on, select the zip, flash it and then select wipe cache +dalvik.
It's pretty much what AndroidSupporter318 wrote, just wanted to give feedback and say what I did in detail in case anyone was still wondering.
LxMaD
I guaranted 4EXT Recovery for this type of problem. U don't need to boot into recovery and work with 4ext is very simple.

Help Please: Infuse steps to custom ROM

First i want to apologize if this has been answered, but i read so many things and maybe just confused myself. My infuse is on stock GB 2.3.6 (not rooted or any data to worry about), my goal is a stable custom ROM like CM10,slim Bean or any stable ROM you can recommend. Is there a step by step sort of a process i can follow to make this simple for a newbie? I am familiar with Heimdall and Odin but not sure where to start.
Thanks and i appreciate any help
First you need to be rooted and then get Clockworkmod cwm flashed! I suggest Enthropy cm9 , scott.hart.bti unofficial CM 10.1+ ROMs or Beanstalk( These are the most stable).
Remember different Gapps (Google apps) for different ROMs. If you already have CWM, then flash Enthropy's cm9 rom first. Then Scott's jellybeans and kitkat Hit thanks button! This is for att and unlocked infuse 4g.For Rogers, it's still the same except the mentioned back to stock tool.
Phase 1:
---------
To obtain CWM head over too Jscotts odin url.
1. download the file which includes root access.
"Stock UCLB3 with root
UCLB3_Unbrick_root_1.1.zip"
2. you will also need Samsung Kies, which will install
the usb driver for your Samsung galaxy. The link is on
the website.
3. Place your phone into Download mode
To do this, have your usb cable for your phone plugged
into the computer but disconnected from your phone.
shut off your phone. When the power is off press Volume
up and Volume down simultaneously, after the buttons
are pressed plug in the usb cable at the same time,
which should be connected to the computer.
This will place the phone in Download mode.
4. open the included Odin.exe, when you see the yellow
bar under ID:COM then everything is good.
Follow the rest of the instructions on jscotts website.
Finally when this procces is done, reboot into android.
Phase 2:
---------
1) Download SGS kernel flasher
2) Click on the link on jscotts website to download a
stock kernel which contains CWM. use "2013.04.30-
CWM-Synthesis-1.2Ghz.zip in the following link:
forum.xda-developers.com/showthread.php?p=25724638
You now have a working GB cwm and next is follow
Enthropy's CM9 guide for your first ROM
Fullmetal Jun said:
First you need to be rooted and then get Clockworkmod cwm flashed! I suggest Enthropy cm9 , scott.hart.bti unofficial CM 10.1+ ROMs or Beanstalk( These are the most stable).
Remember different Gapps (Google apps) for different ROMs. If you already have CWM, then flash Enthropy's cm9 rom first. Then Scott's jellybeans and kitkat Hit thanks button! This is for att and unlocked infuse 4g.For Rogers, it's still the same except the mentioned back to stock tool.
Phase 1:
---------
To obtain CWM head over too Jscotts odin url.
1. download the file which includes root access.
"Stock UCLB3 with root
UCLB3_Unbrick_root_1.1.zip"
2. you will also need Samsung Kies, which will install
the usb driver for your Samsung galaxy. The link is on
the website.
3. Place your phone into Download mode
To do this, have your usb cable for your phone plugged
into the computer but disconnected from your phone.
shut off your phone. When the power is off press Volume
up and Volume down simultaneously, after the buttons
are pressed plug in the usb cable at the same time,
which should be connected to the computer.
This will place the phone in Download mode.
4. open the included Odin.exe, when you see the yellow
bar under ID:COM then everything is good.
Follow the rest of the instructions on jscotts website.
Finally when this procces is done, reboot into android.
Phase 2:
---------
1) Download SGS kernel flasher
2) Click on the link on jscotts website to download a
stock kernel which contains CWM. use "2013.04.30-
CWM-Synthesis-1.2Ghz.zip in the following link:
forum.xda-developers.com/showthread.php?p=25724638
You now have a working GB cwm and next is follow
Enthropy's CM9 guide for your first ROM
Click to expand...
Click to collapse
Much appreciated, i'll try and follow the instructions. happy new year
skopedia said:
Much appreciated, i'll try and follow the instructions. happy new year
Click to expand...
Click to collapse
I made it !, i now have CM9 running without any issues(very proud of myself) but have a couple of questions
is this the kitkat i need to flash next? http://forum.xda-developers.com/showthread.php?t=2091900
also what about CM11, is that something i can try?
Thanks a bunch
For me, Beanstalk ROM has awesome features, but drains battery life heavily!
Unofficial CM11 has simple features, but very good battery life. I use unofficial CM11 from Scott(Infuse god)
http://forum.xda-developers.com/showthread.php?t=2517092
U first need to flash any Jellybean ROM to get a new CWM, then flash Kitkat. CM10.2
http://forum.xda-developers.com/showthread.php?t=1776129
When u flash Kitkat ROM after cm10.2, you'll be stuck at recovery, reboot to recovery once more then flash ROM again then gapps
Remember to hit thanks button for me and Scott and anyone every time they helped you
Glad I helped you update the old Infuse
Fullmetal Jun said:
For me, Beanstalk ROM has awesome features, but drains battery life heavily!
Unofficial CM11 has simple features, but very good battery life. I use unofficial CM11 from Scott(Infuse god)
http://forum.xda-developers.com/showthread.php?t=2517092
U first need to flash any Jellybean ROM to get a new CWM, then flash Kitkat. CM10.2
http://forum.xda-developers.com/showthread.php?t=1776129
When u flash Kitkat ROM after cm10.2, you'll be stuck at recovery, reboot to recovery once more then flash ROM again then gapps
Remember to hit thanks button for me and Scott and anyone every time they helped you
Glad I helped you update the old Infuse
Click to expand...
Click to collapse
something is wrong, twice after flashing CM9, i was not able to boot in to the rom, instead it boots to recovery no matter what i did..
and the only way i could get back was to reflash back to stock with ODIN and both times it messed up after i tried to use rom manager to backup the CM9 rom. any ideas?
thanks
NOTE:MAKE SURE U'RE FLASHING EACH ROM WITH THEIR RESPECTIVE GAPPS or you'll get errors!!!If you have a backup of apps and contacts and pics,don't make any further ones.Once u start flashing continue on flashing
If you're back to stock with jscott's back to stock with root tool, before flashing any ROM,u need to flash a CWM recovery first like in the above guide.Then wipe,flash cm9,stuck at reboot,reboot to recovery,format system,cache,data,flash cm9,flash cm9 gapps,wipe cache partition,wipe dalvik cache,back,back,reboot SYSTEM NOT reboot recovery. Now phone is on,just complete the default menus in cm9.Don't adjust any further settings!
Make sure battery life is beyond 40% every time or u're dead!
Reboot to recovery.Wipe cache/factory reset.Flash unofficial cm10.2 (if incompatible/error appears,ignore and flash again) ,reboot system,if stuck at reboot,reboot to recovery again format data and cache, flash cm10.2 (OR BEANSTALK 4.3 ROM), flash CM10.2 GAPPS wipe cache partition and wipe Dalvik,back,reboot SYSTEM. Complete default procedures at start.
Make sure battery life is beyond 40% every time or u're dead!
Reboot to recovery.Wipe cache/factory reset.Flash unofficial CM11 v01/04/14, if stuck at reboot system,reboot to recovery again,format data,cache,flash cm11 again and flash cm11 GAPPS , wipe cache partition,wipe Dalvik cache,reboot SYSTEM.
This should be all the needed detailed steps
Remember to hit thanks
Fullmetal Jun said:
For me, Beanstalk ROM has awesome features, but drains battery life heavily!
Unofficial CM11 has simple features, but very good battery life. I use unofficial CM11 from Scott(Infuse god)
http://forum.xda-developers.com/showthread.php?t=2517092
U first need to flash any Jellybean ROM to get a new CWM, then flash Kitkat. CM10.2
http://forum.xda-developers.com/showthread.php?t=1776129
When u flash Kitkat ROM after cm10.2, you'll be stuck at recovery, reboot to recovery once more then flash ROM again then gapps
Remember to hit thanks button for me and Scott and anyone every time they helped you
Glad I helped you update the old Infuse
Click to expand...
Click to collapse
Actually, I just flashed KitKat directly from Gingerbread.
1. Flash the ROM from GB recovery
2. It will boot into the ROM, pull the battery and boot into CWM again. Wipe data, cache, etc. And flash the ROM again, but this time flash gapps as well. Wipe again after flashing, then reboot. It worked for me.
reachmaster500 said:
Actually, I just flashed KitKat directly from Gingerbread.
1. Flash the ROM from GB recovery
2. It will boot into the ROM, pull the battery and boot into CWM again. Wipe data, cache, etc. And flash the ROM again, but this time flash gapps as well. Wipe again after flashing, then reboot. It worked for me.
Click to expand...
Click to collapse
Is this method still working for you? I mean any weird issues yet?
I'm not the type that will change thing often so i stayed with 2.3.6 after seeing what i had to go through everytime something went wrong.can the same be done with CM11 maybe?
i might just give it a try
Thanks
Hello, I hope it's okay for me to chime in. I did basically all the steps you mentioned. Using ODIN and pit file to go back to stock -> Flash kernel with CWM -> Install CM9 -> CM10.2 -> CM11.
My problem is the same, I can not boot into any single CM rom I installed even though the installation process completed successfully, even after installing the rom twice. I will keep retrying to ODIN back to stock and get into CM9.
mikeka said:
Is this method still working for you? I mean any weird issues yet?
I'm not the type that will change thing often so i stayed with 2.3.6 after seeing what i had to go through everytime something went wrong.can the same be done with CM11 maybe?
i might just give it a try
Thanks
Click to expand...
Click to collapse
Yeah. Actually, I did it yesterday. It worked fine for me. The last wipe isn't ABSOLUTELY required, but I do it every time (the ROM tends to be a bit buggy then). But yeah, it works. Make a backup of apps and whatnot, wipe data, cache (you don't have to wipe dalvik cache), install the ROM, reboot (if it doesn't automatically), install ROM, GApps, wipe again and reboot. And your done! Lemme know if it doesn't work.
I followed this instruction to get into CM rom. Apparently, after flashing the rom, I have to not do anything and immediately reboot and let it stuck at the kernel screen. My mistake was wiping or flashing before rebooting.
http://www.youtube.com/watch?v=I18O4JsUW7I
It definitely is slower than my N4, but I can't wait to load some FLAC to it and enjoy the Wolfson DAC. I was going to repurchase the Samsung Captivate again, but I saw this model with larger screen and 0.2ghz faster so I went with it.
reachmaster500 said:
Yeah. Actually, I did it yesterday. It worked fine for me. The last wipe isn't ABSOLUTELY required, but I do it every time (the ROM tends to be a bit buggy then). But yeah, it works. Make a backup of apps and whatnot, wipe data, cache (you don't have to wipe dalvik cache), install the ROM, reboot (if it doesn't automatically), install ROM, GApps, wipe again and reboot. And your done! Lemme know if it doesn't work.
Click to expand...
Click to collapse
I tried to install kitkat 4.4.215 from GB CWM and i got a warning saying that partitions are incompatible and that all data will be wiped etc, should i proceed? all data has been backed up but is the partition warning something to worry about?
Thanks
mikeka said:
I tried to install kitkat 4.4.215 from GB CWM and i got a warning saying that partitions are incompatible and that all data will be wiped etc, should i proceed? all data has been backed up but is the partition warning something to worry about?
Thanks
Click to expand...
Click to collapse
I strongly recommend to first go to CM9 to update the CWM. These are the instructions of the ROM developer who knows what he is talking. It takes less than 5 minutes to flash cm9 from stock GB with red CWM.After cm9, CWM will be blue, then flash again followed by cm9 gapps, wipe partition, reboot system(follow previous guide). Then flash CM11 with cm11 gapps(choose Paranoid Android mini modular gapps).
In all will take less than 10 minutes to flash cm9 and cm11. After flashing each ROM, do only default procedures and nothing else and flash again
Flash CM9 first!!!
The partition alert is normal. Just install ROM again with specific gapps
Fullmetal Jun said:
I strongly recommend to first go to CM9 to update the CWM. These are the instructions of the ROM developer who knows what he is talking. It takes less than 5 minutes to flash cm9 from stock GB with red CWM.After cm9, CWM will be blue, then flash again followed by cm9 gapps, wipe partition, reboot system(follow previous guide). Then flash CM11 with cm11 gapps(choose Paranoid Android mini modular gapps).
In all will take less than 10 minutes to flash cm9 and cm11. After flashing each ROM, do only default procedures and nothing else and flash again
Flash CM9 first!!!
The partition alert is normal. Just install ROM again with specific gapps
Click to expand...
Click to collapse
I made it to CM11, and don't want to have to do this again.. what do you recommend to back up the rom with the way it is now? i mean for me to be able to restore it the way it is now.. please tell me it's possible, lo
I appreciate all the help and patience you guys have with new users
Thanks:laugh:
mikeka said:
I made it to CM11, and don't want to have to do this again.. what do you recommend to back up the rom with the way it is now? i mean for me to be able to restore it the way it is now.. please tell me it's possible, lo
I appreciate all the help and patience you guys have with new users
Thanks:laugh:
Click to expand...
Click to collapse
U are on cm11. If you are not getting any errors, enjoy it. If any future problems,a reboot of phone is sufficient. Any big errors or heavy battery draining, then just flash cm11 ROM and gapps again followed by wipe cache partition and wipe Dalvik cache.
For backups, if you want to have game and apps data stored for easy restore, use titanium backup pro and if u can't afford it, I regret to say, but side download it
Fullmetal Jun said:
U are on cm11. If you are not getting any errors, enjoy it. If any future problems,a reboot of phone is sufficient. Any big errors or heavy battery draining, then just flash cm11 ROM and gapps again followed by wipe cache partition and wipe Dalvik cache.
For backups, if you want to have game and apps data stored for easy restore, use titanium backup pro and if u can't afford it, I regret to say, but side download it
Click to expand...
Click to collapse
There are alternatives like Helium and Super Backup. I don't really use Titanium Backup myself.
mikeka said:
I tried to install kitkat 4.4.215 from GB CWM and i got a warning saying that partitions are incompatible and that all data will be wiped etc, should i proceed? all data has been backed up but is the partition warning something to worry about?
Thanks
Click to expand...
Click to collapse
No. That is normal. When you try to flash the ROM again, it will reboot automatically. It will bring you back to an updated blue CWM. Then just flash the ROM and GApps and wipe. Then reboot. Hope that helps!

Categories

Resources