Update from stock XOOM 4G to Tiamat ICS - Xoom Q&A, Help & Troubleshooting

Please help me guys.
I have 100 percent stock Xoom with the 4g update
I unlocked then did the fast boot recovery and did the root with the universal root
Then did the latest ICS nightly build #17.
Now my Xoom will go to the Dual Core screen and that is it.

The new Tiamat kernel takes a long time to boot.
Is it boot-looping, or displaying any errors?
If not, then let it try to do it's thing. It took my Xoom about 20 min to boot up the first time.
If it still doesn't boot after 25-30 minutes then follow these steps
-boot into recovery
-clear cache
-clear davlik cache
-wipe system
-re-install rom
Sent from my Xoom using xda premium

You don't need to root the stock rom. You're erasing it and flashing a new one.
Boot back into custom recovery.
Factory reset
Format system.
Flash rom
Flash gapps.
Reboot. It does not take 20 to 30 mins to boot ever.
Simply put. A proper full wipe. Flash rom and gapps. The end

Mine just hanged on the Motorola logo.
Also, are the Nightly updates a full ROM on each night?

you did not format system/ do a full wipe prior to flashing .......
Yes.

Help
is there any instructions for flashin this ROM. i have been looking and i am not able to find any help
I have a stock no root 4g xoom that i would like to have Tiamat ICS
Any help would be much appreciated.

Related

[Q] Bootloop - Downgrading from leaked 2.3.3 to official brazillian Froyo

Hey guys, can somebody help me here? I was using the leaked Orange Gingerbread, but decided that battery drain, non-720p and constant bugs were not worth it. Decided to downgrade it to Brazilian Vivo's Official Froyo, flashed full sbf (I also applied the leaked GB over Barebones using full sbf), but now all I get is a bootloop. IT shows splash screen, shows boot animation, than gets back to the begining of the boot animation, without showing the splash screen.
Is there any way for me to get an official firmware, or can I only use custom ones, now? I kinda like BLUR, so I'd like to have a firmware with it enabled.
Did you wiped with the stock recovery before flashing brazilian sbf?
vick33 said:
Did you wiped with the stock recovery before flashing brazilian sbf?
Click to expand...
Click to collapse
No, I didn't. Since I didn't need to wipe to upgrade, I didn't think it was needed for downgrade.
Then try to wipe now. it should work after it
I'm being able to access stock recovery (options: apply update.zip - as we all know, only motorola-signed files / wipe data/factory reset / wipe cache partition) and fastboot (or whatever we call the mode we use to flash the SBFs). Should I perform the wipes? Is there any firmware I can flash to solve the issue? Flashed Korean Eclair, the same bootloop issue.
vick33 said:
Then try to wipe now. it should work after it
Click to expand...
Click to collapse
Should I apply both wipes? Isn't it gonna brick my phone or anything like that?
enter into the stock recovery by pressing volume down.
then the droid guy appears press both volume up and down, then select wipe data cache.
Didn't have to wipe, it booted normally. I flashed the korean SBF, got bootloop too, than flashed brazilian SBF again and now everything's working
If you just wipe data and cache, there's no need to go to 2 or 3 SBF before.
if you want to go to another SBF,
it is really necessary to DO A WIPE DATA and WIPE CACHE from STOCK RECOVERY.
sometimes it works without wipe, but sometimes don't.
so it is safe to do a wipe before flashing sbf or restoring nandroid.
marhensa said:
if you want to go to another SBF,
it is really necessary to DO A WIPE DATA and WIPE CACHE from STOCK RECOVERY.
sometimes it works without wipe, but sometimes don't.
so it is safe to do a wipe before flashing sbf or restoring nandroid.
Click to expand...
Click to collapse
Above it Correct!!
I've not seen one SBF that wipes Data nor Cache which is needed anytime you make a change in the System Version, yes sometimes it will boot, but almost always will have issue later down the road.
~Eugene
I found same your problem.
After that.
- I wipe all data with stock recovery - I reboot to bootloader.
- flash 3.4.3-11 with sbf
everything ok!
Now,I rooted and update to CM7.
Sent from my MB525 using XDA App

[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

Bricked G2x trying to install Eaglesblood HELP!

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.

[Q] I can't get any 4.3 roms to work.

Every 4.3 rom I install after the first reboot it hangs at unlocked bootlaoder screen. I have tried every recovery out there but everytime I have to fastboot to be able to restore a 4.2.2 rom and get it to boot. Does anyone know how to fix this because it is very frustrating. I wipe everything when I install to. I follow the standard procedure and I am not new to rooting or flashing.
ajh305 said:
Every 4.3 rom I install after the first reboot it hangs at unlocked bootlaoder screen. I have tried every recovery out there but everytime I have to fastboot to be able to restore a 4.2.2 rom and get it to boot. Does anyone know how to fix this because it is very frustrating. I wipe everything when I install to. I follow the standard procedure and I am not new to rooting or flashing.
Click to expand...
Click to collapse
you tried 6.0.3.5 cwm also?
i had the same problem and this was the only one i could get to work.
bweN diorD said:
you tried 6.0.3.5 cwm also?
i had the same problem and this was the only one i could get to work.
Click to expand...
Click to collapse
Ya i tried every cwm including 6.0.3.6 and twrp 2.0.6.1
ajh305 said:
Ya i tried every cwm including 6.0.3.6 and twrp 2.0.6.1
Click to expand...
Click to collapse
not sure if it will help but this is the exact process i used:
-rts using matts utility found here http://batakang.com/dr_utility.php
-put stock recovery back on using the above utility
-root with the above utility and protect with voodoo
-take the ota to get the latest baseband back (will likely fail but still update the bb)
-restore root
-install cwm 6.0.3.5 from this utility http://www.mediafire.com/download/tt7cwwua49n24uv/Razr_HD_Recovery_Flasher_V7.rar
-flash your 4.3 rom of choice
-profit (hopefully lol)
ajh305 said:
Every 4.3 rom I install after the first reboot it hangs at unlocked bootlaoder screen. I have tried every recovery out there but everytime I have to fastboot to be able to restore a 4.2.2 rom and get it to boot. Does anyone know how to fix this because it is very frustrating. I wipe everything when I install to. I follow the standard procedure and I am not new to rooting or flashing.
Click to expand...
Click to collapse
keep in mind the second boot on 4.3 roms seems to take a while, how long is it hanging on the boot screen? I remember the first 4.3 I flashed hung for about 5-8 minutes before it booted up. it seems to be the second one that hangs consistently for me, but it does always boot. All following reboots after the 2nd are normal with no hangs.
bjoostema said:
keep in mind the second boot on 4.3 roms seems to take a while, how long is it hanging on the boot screen? I remember the first 4.3 I flashed hung for about 5-8 minutes before it booted up. it seems to be the second one that hangs consistently for me, but it does always boot. All following reboots after the 2nd are normal with no hangs.
Click to expand...
Click to collapse
I think I have waited for about 10 minutes before. I'll try again and see if it does actually boot. Does your hang on the bootloader unlocked screen or the boot animation screen?
EDIT: I tried another 4.3 rom and booted it up. Set some things up then updated su binaries and restarted and let it sit there at the unlocked bootloader warning for 15 minutes with no changes.
bweN diorD said:
not sure if it will help but this is the exact process i used:
-rts using matts utility found here http://batakang.com/dr_utility.php
-put stock recovery back on using the above utility
-root with the above utility and protect with voodoo
-take the ota to get the latest baseband back (will likely fail but still update the bb)
-restore root
-install cwm 6.0.3.5 from this utility http://www.mediafire.com/download/tt7cwwua49n24uv/Razr_HD_Recovery_Flasher_V7.rar
-flash your 4.3 rom of choice
-profit (hopefully lol)
Click to expand...
Click to collapse
I did actually restore it back to completely stock, recovery and everything. I downloaded the OTA after rooting and using voodoo. The update failed but I installed cwm 6.0.3.6 and then restored my backup. Then I flashed twrp 2.0.6.1 to try that and flashed a 4.3 rom and same issue came up.
ajh305 said:
I think I have waited for about 10 minutes before. I'll try again and see if it does actually boot. Does your hang on the bootloader unlocked screen or the boot animation screen?
Click to expand...
Click to collapse
Yeah, mine hangs at the bl unlocked screen on that second boot, though I flashed a different logo to get rid of that annoying message 10 minutes seems a bit excessive but not unheard of-longest I clocked was around 8. Does yours ever make it to the boot animation? If so, it should go into a full boot eventually. I think the hang has something to do with the rom building cache on that second boot Also, whichever 4.3 your using, I would make sure it's a more recent release as they have come a very far since the early releases which hung for longer periods of time. I'm currently running pa rc2 by cj and it went smoothly using cwm 6.0.3.2.
bjoostema said:
Yeah, mine hangs at the bl unlocked screen on that second boot, though I flashed a different logo to get rid of that annoying message 10 minutes seems a bit excessive but not unheard of-longest I clocked was around 8. Does yours ever make it to the boot animation? If so, it should go into a full boot eventually. I think the hang has something to do with the rom building cache on that second boot Also, whichever 4.3 your using, I would make sure it's a more recent release as they have come a very far since the early releases which hung for longer periods of time. I'm currently running pa rc2 by cj and it went smoothly using cwm 6.0.3.2.
Click to expand...
Click to collapse
It never reaches the boot animation just sits at that screen. I have tried several 4.3 roms within the last few days so they are the newest versions I can find. Could I clear the cache to get it to boot?
ajh305 said:
It never reaches the boot animation just sits at that screen. I have tried several 4.3 roms within the last few days so they are the newest versions I can find. Could I clear the cache to get it to boot?
Click to expand...
Click to collapse
http://www.droidrzr.com/index.php/topic/27682-having-issues-with-43-roms-is-it-me/ check out the last post on the page in that link. It seems to have worked for that guy. If you don't mind, try that and let me know if it works. In the meantime, I'm going to try and find some more solutions. I'm assuming his method worked, as he hasn't posted back.
bjoostema said:
http://www.droidrzr.com/index.php/topic/27682-having-issues-with-43-roms-is-it-me/ check out the last post on the page in that link. It seems to have worked for that guy. If you don't mind, try that and let me know if it works. In the meantime, I'm going to try and find some more solutions. I'm assuming his method worked, as he hasn't posted back.
Click to expand...
Click to collapse
By golly that worked! It booted up fast as well. It must lie with the formatting your internal storage before flashing the 4.3 rom. I tried something similiar to this but I was already on a 4.3 rom that wouldn't boot and I formatted the sd card then tried flashing it again and it booted again for the first time but wouldn't the second. So if your having trouble do this:
Restored stock 4.1.2 using Matt's utility
Rooted with Matt's utility
Put 4.3 rom and GAPPS on external SD
Fastboot flash CWM 6.0.3.5 (or install via Matt's utility if you like)
Wipe data/factory reset
Wipe Cache/Dalvik
Go to mounts/storage and format /data and /data/media (/sdcard) **Back up anything in your internal SD you want to keep before doing this!**
Flash 4.3 rom
Wipe Cache/dalvik
Flash GAPPS
Wipe Cache/dalvik
Boot up and setup rom
Reboot
ajh305 said:
By golly that worked! It booted up fast as well. It must lie with the formatting your internal storage before flashing the 4.3 rom. I tried something similiar to this but I was already on a 4.3 rom that wouldn't boot and I formatted the sd card then tried flashing it again and it booted again for the first time but wouldn't the second. So if your having trouble do this:
Restored stock 4.1.2 using Matt's utility
Rooted with Matt's utility
Put 4.3 rom and GAPPS on external SD
Fastboot flash CWM 6.0.3.5 (or install via Matt's utility if you like)
Wipe data/factory reset
Wipe Cache/Dalvik
Go to mounts/storage and format /data and /data/media (/sdcard) **Back up anything in your internal SD you want to keep before doing this!**
Flash 4.3 rom
Wipe Cache/dalvik
Flash GAPPS
Wipe Cache/dalvik
Boot up and setup rom
Reboot
Click to expand...
Click to collapse
Awesome man! I'm glad it booted up for you welcome to the 4.3 side!
ajh305 said:
I did actually restore it back to completely stock, recovery and everything. I downloaded the OTA after rooting and using voodoo. The update failed but I installed cwm 6.0.3.6 and then restored my backup. Then I flashed twrp 2.0.6.1 to try that and flashed a 4.3 rom and same issue came up.
Click to expand...
Click to collapse
glad you got it fixed but i have to ask, in the sequence above why are you restoring a backup? you should be going right from stock to 4.3. also, some people have issues with twrp and 4.3, thats why i suggested cwm.
I'm not sure why I restored the backup. I didn't think coming from stock would work for some reason.
Sent from my XT926 using xda app-developers app
I am having the same problem. I have followed the steps but still no joy . Any thoughts?
sgtslaughter64 said:
I am having the same problem. I have followed the steps but still no joy . Any thoughts?
Click to expand...
Click to collapse
This was the only thing that worked for me. You could maybe try updating to the most current recovery instead of the one listed.
the only 2 issues i have seen to cause this problem are covered in the post a few below, and fixed it every time. my only suggestion would be to install cwm after rooting, then reboot, then continue with the steps. just my preference, it may not matter.

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