Looking for some input on clean ROM on the TF300T,
This is my second time trying to install it and both times it was successful, however as soon as the boot image loads up it stays stuck loading... I did download the file again thinking it may have been corrupted.
It has been sitting there loading for 20 minutes now.
I am using cwm the latest version and I did not install a kernel still running stock
Any ideas on what could cause this?
chibra said:
Looking for some input on clean ROM on the TF300T,
This is my second time trying to install it and both times it was successful, however as soon as the boot image loads up it stays stuck loading... I did download the file again thinking it may have been corrupted.
It has been sitting there loading for 20 minutes now.
I am using cwm the latest version and I did not install a kernel still running stock
Any ideas on what could cause this?
Click to expand...
Click to collapse
CWM has issues on this unit. Many, many complaints. I use twrp. If you decide to use twrp be sure to choose JB and tf300t version.
Clean ROM is freaking amazing! Seriously just do it I love the mods I can make for it too! Can't wait till I get my volume long press seek mod done! Love this device!
Sent from my SGH-T999
"So I put my phone into airplane mode and threw it... worst transformer ever. -.-" -My friend
tobdaryl said:
CWM has issues on this unit. Many, many complaints. I use twrp. If you decide to use twrp be sure to choose JB and tf300t version.
Click to expand...
Click to collapse
I initially when i first rooted intalled Twrp however i was not able to flash anything at all with it, it would give me errors.... that is the only reason i went to cwm.... I was able to make backups and restores with but ROMs flashing would just fail
chibra said:
I initially when i first rooted intalled Twrp however i was not able to flash anything at all with it, it would give me errors.... that is the only reason i went to cwm.... I was able to make backups and restores with but ROMs flashing would just fail
Click to expand...
Click to collapse
OK. It was just a suggestion since the problem you are experiencing is usually cleared by using twrp.
oryhight sullivan
tobdaryl said:
OK. It was just a suggestion since the problem you are experiencing is usually cleared by using twrp.
Click to expand...
Click to collapse
i m going to give twrp another shot...
i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop
chibra said:
i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop
Click to expand...
Click to collapse
I'm sorry it is hard to tell since you have chosen an older twrp to install. The current is five versions later and was updated as the kernels were updated to account for changes. The rom you are flashing is based on 10.4.4.25.
chibra said:
i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop
Click to expand...
Click to collapse
Use TWRP 2.4.1.0
You are using a very old version of TWRP that has bugs with AROMA installer. So that is most likely where your issues are.
What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!
sbdags said:
What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!
Click to expand...
Click to collapse
Wise words. Nobody likes to listen to me so im glad someone else suggested it!
elesbb said:
Use TWRP 2.4.1.0
You are using a very old version of TWRP that has bugs with AROMA installer. So that is most likely where your issues are.
Click to expand...
Click to collapse
Updated the TWRP to the version you mentioned still stuck in boot loop.
sbdags said:
What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!
Click to expand...
Click to collapse
The only ROM i was able to flash that was fully functioning is cm10.1,
i have also flashed PA 2.9 but had some bugs i couldn't stand (screen rotation not working, extended desktop with no pie)
as for boot loader it says 1.00e by "US _Epad-10.4.2.20-20121228" A03
I just updated the TWRP as recommended on the other post (v2.4.1.0)
on every flash i wipe dalvik / Cache / Factory reset.
Before attempting to boot into Clean Rom i also followed the steps on screen saying to wipe cache and dalvik.
I m hoping PA releases a 3.0 for this device and/or i m able to get Clean rom running
chibra said:
The only ROM i was able to flash that was fully functioning is cm10.1,
i have also flashed PA 2.9 but had some bugs i couldn't stand (screen rotation not working, extended desktop with no pie)
as for boot loader it says 1.00e by "US _Epad-10.4.2.20-20121228" A03
I just updated the TWRP as recommended on the other post (v2.4.1.0)
on every flash i wipe dalvik / Cache / Factory reset.
Before attempting to boot into Clean Rom i also followed the steps on screen saying to wipe cache and dalvik.
I m hoping PA releases a 3.0 for this device and/or i m able to get Clean rom running
Click to expand...
Click to collapse
If you are coming from cm10.1 you will definitely need to do a full wipe as it is non stock. It does say this in the first post. You only do a dalvik and cache wipe when upgrading from the same ROM or in CROMI's case from stock.
Do a data wipe in recovery, make sure you have a titanium backup or equivalent if you want to restore apps.
Success!!!
It worked perfectly fine after i install the back up i did before i flashed my 1st costume rom,
I rooted made a back up at stock/rooted... It just would not install from a full wipe,
it install fine once i flashed that specific backup and dirty flashed then wiped dalvik and cache before booting.
Hey guys, since my post count is too low to post my problems with this OTA update in the development section of this rom, ill do it here. Sorry for that.
I think im having no problems with flashing the 2.1. ROM yet but i have my concerns if i did that right.
First problem with flashing it, is the question if im having a custom kernel. I flashed ViperOneS a several times but made a fullwipe before.
So am i having a custom kernel or not?
Next issue is that im only able to flash this ROM with CWM. TWRP 2.5 doesnt work and even 2.3.3.0, which should work, but does not for me...
Well with CWM i ll do it that way:
1. Doing Fullwipe in CWM (Factory reset, Wipe Cache, Wipe Dalvik and System).
2. Flashing the ROM and choosing HTC Theme > Custom Kernel? > not sure sometimes "yes" sometimes "no".
3. Flash finished? > asks me if i want to reboot (into system) or save the logs. Since the instruction tells me to flash the boot.img first before rebooting...
4. ... im going into bootloader via adb which works
5. flash the boot.img
6. fastboot erase cache
7. reboot system
8. before doing the first setup i go into recovery and wipe cache.
I think 2.1 works but i want to be sure if i did everything right, especially with the custom kernel question and that i reboot into bootloader right after aroma says that the flash is finished.
Now i want to flash the 2.2.0 OTA because the update function through the ROM didnt work for me last time (it downloads the OTA but wasnt able to flash)
Im not sure how to flash the OTA right via recovery. Everytime i did that the ROM was kinda messed up, like when im turning the screen off and on Sense keeps loading and it takes some sec to unlock. And the venom tweaks app is totally laggy, even with the "trick" to go into app settings and wipe the cache and data which found on any other site (not xda...).
The problem is that they dont keep their instructions up-to-date (+ how to flash the OTA... right)
It looks to my like there are 100 different ways to flash 2.1.0 and 2.2.0 and only 1 is the right way which lets the ROM being amazing...
Hope you can help me. Thanks in advance!
turnschuh said:
Now i want to flash the 2.2.0 OTA because the update function through the ROM didnt work for me last time (it downloads the OTA but wasnt able to flash)
Im not sure how to flash the OTA right via recovery. Everytime i did that the ROM was kinda messed up, like when im turning the screen off and on Sense keeps loading and it takes some sec to unlock. And the venom tweaks app is totally laggy, even with the "trick" to go into app settings and wipe the cache and data which found on any other site (not xda...).
Click to expand...
Click to collapse
All you have to do ist to flash the OTA with your custom recovery like any other flashable zip if this isn't done automatically. You can simply copy it to your device from your pc or flash it from your mobiles download folder, it doesn't matter which way.
The 'trick' is very well known here at xda, but simply nobody wants to repeat it a hundred times... Here at xda there is even included the fact, that after rebooting you should change your skin once to get things going besides wiping cache and data in venom tweaks and hub.
What EXACTLY doesn't work with TWRP 2.3.3.0?
All you have to do ist to flash the OTA with your custom recovery like any other flashable zip if this isn't done automatically. You can simply copy it to your device from your pc or flash it from your mobiles download folder, it doesn't matter which way.
Click to expand...
Click to collapse
yea i did it like that. i just flashed it in the recovery, but im not sure if i have to wipe caches after or before doing that.
The 'trick' is very well known here at xda, but simply nobody wants to repeat it a hundred times... Here at xda there is even included the fact, that after rebooting you should change your skin once to get things going besides wiping cache and data in venom tweaks and hub.
Click to expand...
Click to collapse
about finding such "tricks": the problem is that those ROM release threads have tons of post (500+ sites of them) and it seems like 90% are from people who didnt even flash the ROM... i think you ll excuse me if i say i got tired of searching for my problems there^^
well can u tell me which skin i have to change? on venom tweaks or the htc skin on personalization? and app settings > venom tweaks > wipe cache and data right?
What EXACTLY doesn't work with TWRP 2.3.3.0?
Click to expand...
Click to collapse
when i flash it with 2.3.3.0 (or 2.5... its the same), the flash process doesnt even take up to 2 seconds and it says its finished and that causes a bootloop but doesnt make me wonder.
dont you have problems with TWRP flashing sense roms either?
ah and another one: did i flash the version 2.1 right and what about the custom kernel question?
well thanks for ur time.
edit: well this time flashing with twrp 2.3.3.0 worked somehow, but i choosed flashing without wipe (made it in recovery) and not to delete apps with aroma installer (which i did before)... just strange.
new problem. dont know whats wrong with my phone but:
wanted to make a backup of my ViperOneS 2.1 with TWRP 2.3.3.0 after lets say 70% of progress it starts turning off my phone and restarts into system. i flashed 2.5.0.0 but its the same issue (edit#1: with CWM too...). strange is that TWRP turned out my phone before when i wiped something there.
i think somethings really messed up atm...
edit#2: had to run a ruu over the system again, flashed twrp and backups seem work again..strange ****
I had rooted my phone, and did use Jelly Blast for a while worked perfect. After a few days I tried installing mods through cwm which led to boot loops. I used odin and got stock ROM for my phone . Now when I tried installing Nemesis ROM, I followed all steps right but though it shows Nemesis boot picture, it still boots into the stock OS.
Update ur cwm version
Flash ur rom again
It will ask u to disable stock recovery say yes
This should fix ur problem:thumbup:
Hit thanks if i helped
Sent from my GT-S7500
[email protected] said:
Update ur cwm version
Flash ur rom again
It will ask u to disable stock recovery say yes
This should fix ur problem:thumbup:
Hit thanks if i helped
Sent from my GT-S7500
Click to expand...
Click to collapse
Hey I'm a noob. By flash your rom, do you suggest to flash the same nemesis rom again? And what will ask me to disable stock recovery? I have cwm version 5.0.2.6 right now.
try this
wipe data
wipe cache
wife dalvik cache
install stock rom via odin
then install your desired rom via cwm
Sent from my GT-S5302 using xda premium
DJDSB said:
try this
wipe data
wipe cache
wife dalvik cache
install stock rom via odin
then install your desired rom via cwm
Sent from my GT-S5302 using xda premium
Click to expand...
Click to collapse
I have tried the following steps:
1. Odin stock rom: I just have pda,csc and modem. I do not have bootloader and pit.
2. Then went to Recovery and installed CWM
3. Installed custom rom JELLY Blast which previously had no issues. (Before this I wiped data,cache & dalvik)
4. Result - > Stuck on Samsung screen.
After which I cannot get back to any recovery mode anymore, it is stuck on samsung screen. All I have to do is go back to download mode and odin it again. But I really want to be back on custom roms
pavitar said:
Hey I'm a noob. By flash your rom, do you suggest to flash the same nemesis rom again? And what will ask me to disable stock recovery? I have cwm version 5.0.2.6 right now.
Click to expand...
Click to collapse
Yes u have to install rom by normal way
Updare your cwm to V6
Cwm will ask u to disable it
This may help u:thumbup:
Hit thanks if i helped
Sent from my GT-S7500
Generic Rom Flashing Issues
pavitar said:
I had rooted my phone, and did use Jelly Blast for a while worked perfect. After a few days I tried installing mods through cwm which led to boot loops. I used odin and got stock ROM for my phone . Now when I tried installing Nemesis ROM, I followed all steps right but though it shows Nemesis boot picture, it still boots into the stock OS.
Click to expand...
Click to collapse
Hi,
This is not your phone issue alone but any phone can face this. To reproduce this issue, it takes more than what you have mentioned. But the solution comes through if you follow these steps just as listed by me here:
1. Get an older version of official Samsung Firmware (preferably 1 or 2 versions older than the latest one)
2. Flash this using ODIN (if flashing fails at any point via ODIN user an even older Stock Firmware version)
3. If you can boot into the Rom fine, reboot to its Stock Recovery
4. From Stock recover, start the CWM.zip that you have (version 5 or 6 whichever lets you load fine, does not matter at this point)
5. When inside CWM, go into Advanced and select "Fix Permissions"
6. Only after you have fixed permissions, go ahead and do the Wipes in the order below
7. Wipe Dalvik Cache, Wipe Cache, Wipe Data
8. Once this is done, load the custom ROM you want to install from this CWM session
9. After install, when you go for reboot, see if you get any option that says something like "prevent from flashing stock recovery" or so, say yes to it.
This should fix any permission issue that may be preventing you to get to your favorite ROM from stock ROM.
Let me know if this helps or if I can help you further.
Glad if this helped you in any way !
NOTE: THIS IS GENERIC AND NOT SPECIFIC TO ANY ONE PHONE MODEL.
keeploving said:
Hi,
This is not your phone issue alone but any phone can face this. To reproduce this issue, it takes more than what you have mentioned. But the solution comes through if you follow these steps just as listed by me here:
1. Get an older version of official Samsung Firmware (preferably 1 or 2 versions older than the latest one)
2. Flash this using ODIN (if flashing fails at any point via ODIN user an even older Stock Firmware version)
3. If you can boot into the Rom fine, reboot to its Stock Recovery
4. From Stock recover, start the CWM.zip that you have (version 5 or 6 whichever lets you load fine, does not matter at this point)
5. When inside CWM, go into Advanced and select "Fix Permissions"
6. Only after you have fixed permissions, go ahead and do the Wipes in the order below
7. Wipe Dalvik Cache, Wipe Cache, Wipe Data
8. Once this is done, load the custom ROM you want to install from this CWM session
9. After install, when you go for reboot, see if you get any option that says something like "prevent from flashing stock recovery" or so, say yes to it.
This should fix any permission issue that may be preventing you to get to your favorite ROM from stock ROM.
Let me know if this helps or if I can help you further.
Glad if this helped you in any way !
NOTE: THIS IS GENERIC AND NOT SPECIFIC TO ANY ONE PHONE MODEL.
Click to expand...
Click to collapse
Thanks a Ton, this helped me. The only step I did not perform earlier is Fix Permissions.
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!