Related
Hi XDA
My device before the procedure : HTC Desire S, unbranded, Bootloader locked,
HBoot 2.00.0002, S-ON, ICS stock rom via HTC RUU tool
I unlocked the bootloader via htcdev.com.
After hours of reading and testing "everything" I found here on xda (great stuff!!),
I finally managed to have a running CM10-alpha.
(http://forum.xda-developers.com/showthread.php?t=1776256 / Version 2012-09-17)
As I am new to this flashing stuff, I first tried to follow the flashing guide
on the CM-website. Was not workable because "Revolutionary" can not be used on hboot 2...
So I continued with flashing CWM-recovery and after a wipe (factory/reset/cache/dalvik),
I flashed CM10.zip and gapps.zip.
It went through without any errors, unfortunately, the device did not boot afterwards.
I found this guide :
http://forum.xda-developers.com/showthread.php?t=1525100 (CustomROM with 4EXT-recovery)
It indicates flashing "boot.img" (from the CM10 zip-file) as a last step.
Probably the most important step for this HTC device ?!
The Desire S booted CM10 without any further problems and is running since.
(I did not flash GApps.zip, just downloaded Maps and Youtube.)
I have 3 questions :
1. Is it possible to update to a newer version of 4EXT-recovery without losing
the CM10-installation ?
(e.g. 4EXT-Touch : http://forum.xda-developers.com/showthread.php?t=1377745)
2. Is it possible to switch from 4EXT to CWM-recovery without losing
the CM10-installation ? I would like to have CWM because I could then use the ROMManager App.
(e.g. http://forum.xda-developers.com/showthread.php?t=1484753)
3. If I would stick with the current 4EXT-recovery,
do I always have to flash "boot.img" as the last step before booting up the device ?
(e.g. after the next CM10-alpha release)
"fastboot flash boot boot.img"
Click to expand...
Click to collapse
Thanks so much !
CM10 is great, so much faster than HTC-stock rom ICS (with Sense 3.6) !!
CU
1) yes
2)yep
3)si
Edit: you only have to flash the boot.img when the kernel changes from cm10 to fallout yes.
Updating cm10 no, if the dev didn't change the kernel.
After a full wipe (in 4ext format everything exept SD-card) you also have to use fastboot. Because that wipes the boot.img
Thanks !
Just to recap, I can flash CWM-recovery and then do a normal bootup (with my existing CM10 installation). No further actions required !?
As the kernel will probably remain at v2.xx with the next CM10-alpha-release of nik111, I only wipe reset/factory/cache/dalvik
and then flash the new cm10.zip.
I do not think that I will format anything. But if I would, I would have to replace boot.img again.
FrolicFrog said:
Thanks !
Just to recap, I can flash CWM-recovery and then do a normal bootup (with my existing CM10 installation). No further actions required !?
As the kernel will probably remain at v2.xx with the next CM10-alpha-release of nik111, I only wipe reset/factory/cache/dalvik
and then flash the new cm10.zip.
I do not think that I will format anything. But if I would, I would have to replace boot.img again.
Click to expand...
Click to collapse
Changing recovery will not touch anything else on your device. But there were some issues reported with CWM on some ROMs.
I think one of them is a lack of /system/lib partition support, which is important if you go from a ROM that has such to a ROM without one (it will end with two conflicting /system/lib directories and the device will not boot.
Also I am not sure that CWM wipes the .android-secure directory on the SDcard which can cause issues if going from AOSP to Sense ROM
For some reason I never changed from cwm to 4ext whilst I owned a ds but I can confirm it does wipe .android-secure on the sd card
pughie said:
For some reason I never changed from cwm to 4ext whilst I owned a ds but I can confirm it does wipe .android-secure on the sd card
Click to expand...
Click to collapse
I have used it about an year ago so it is definitely improved. But there was an user with Bluetooth issues after flashing my kernel and changing the recovery solved it. Also 4EXT has a lot of minor but very useful settings over CWM. Anyway the OP can try both and stick with the one he likes more
Btw Rom Manager can be used to check for updates and ROM downloads with 4EXT if you choose "manual flash override" from the menu
Sent from my HTC Desire S
amidabuddha said:
Btw Rom Manager can be used to check for updates and ROM downloads with 4EXT if you choose "manual flash override" from the menu
Click to expand...
Click to collapse
Ah, will check on this one. Thanks !
FrolicFrog said:
As the kernel will probably remain at v2.xx with the next CM10-alpha-release of nik111, I only wipe reset/factory/cache/dalvik
and then flash the new cm10.zip.
I do not think that I will format anything. But if I would, I would have to replace boot.img again.
Click to expand...
Click to collapse
Nk111 uploaded a screenshot today, that shows kernel v3.0.16
When upgrading cm10 wiping cache & dalvic cache should be enough. If you get any problems, apps fc or something like that, do a full wipe(I use format all partitions except SD card in 4ext, after that don't forget to flash the kernel with fastboot).
Btw wipe and format is the same.
Bug in CM10 Alpha by nk11
Hello XDA,
Sorry if this question is in the wrong thread.
It is regarding the cm10 alpha port by nk111.
I got it working, save one major bug, the speaker does not produce any sound output whatsoever:
This applies to ringtones, alarm tones and music.
The sound is perfectly audible through a pair of earphones.
I followed the steps in the official thread to delete the file /system/lib/hw/audio_policy.msm7x30.so and reboot
but this only aggravates the issue by disabling all audio outputs!!!
I am running clockwork mod v5 with HTC bootlocker unlocked, S-ON.
Any help would be greatly appreciated.
c.m.b said:
Nk111 uploaded a screenshot today, that shows kernel v3.0.16
When upgrading cm10 wiping cache & dalvic cache should be enough. If you get any problems, apps fc or something like that, do a full wipe(I use format all partitions except SD card in 4ext, after that don't forget to flash the kernel with fastboot).
Btw wipe and format is the same.
Click to expand...
Click to collapse
I saw the screenshot of kernel version 3, too. And was quite excited
Thanks for the hint with wiping only cache&dalvik.
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!
Is deep sleep issue solved on flasing phatom kernel ? What about WIFI? Is it working in AOSP after flashing kernel? Someone, please confirm that so that I can flash the ROM
sladeslayer said:
Is deep sleep issue solved on flasing phatom kernel ? What about WIFI? Is it working in AOSP after flashing kernel? Someone, please confirm that so that I can flash the ROM
Click to expand...
Click to collapse
yes everything is fine and working
follow the steps
1. flash fresh 4.2.2 (.26 is better but i dont know this step is required or not but i follow this).
2. Flash Phantom Kernel V5 (Kitkat).
3. Flash system.img through Flashtool.
4. Dont Flash userdate.img file (ignore userdata.img)
5. boot into CMW recovery Wipe Data,Wipe Cache,Wipe Dalvik Cache
6. install g-apps
7. reboot.... and DONE !
RazZzeR said:
yes everything is fine and working
follow the steps
1. flash fresh 4.2.2 (.26 is better but i dont know this step is required or not but i follow this).
2. Flash Phantom Kernel V5 (Kitkat).
3. Flash system.img through Flashtool.
4. Dont Flash userdate.img file (ignore userdata.img)
5. boot into CMW recovery Wipe Data,Wipe Cache,Wipe Dalvik Cache
6. install g-apps
7. reboot.... and DONE !
Click to expand...
Click to collapse
Thank u! I'll do it:good:
RazZzeR said:
yes everything is fine and working
follow the steps
1. flash fresh 4.2.2 (.26 is better but i dont know this step is required or not but i follow this).
2. Flash Phantom Kernel V5 (Kitkat).
3. Flash system.img through Flashtool.
4. Dont Flash userdate.img file (ignore userdata.img)
5. boot into CMW recovery Wipe Data,Wipe Cache,Wipe Dalvik Cache
6. install g-apps
7. reboot.... and DONE !
Click to expand...
Click to collapse
I flashed boot.img of phantom.. Phone stuck after sony logo. what to do?
sladeslayer said:
I flashed boot.img of phantom.. Phone stuck after sony logo. what to do?
Click to expand...
Click to collapse
You need to flash the AOSP boot.img file
4.4 can't run on the 4.2 boot.img file
Joery360 said:
You need to flash the AOSP boot.img file
4.4 can't run on the 4.2 boot.img file
Click to expand...
Click to collapse
Finally, i got 4.4.. Thanks for the help.
Bugs..
Wifi works fine. There are these other bugs you see
1. Bluetooth doesn't work.
2. GPS doesn't work.
3. Device memory is the only internal memory available, which means, internal memory is just 2 GB (1.57 GB to be precise) :angel:
sladeslayer said:
Finally, i got 4.4.. Thanks for the help.
Click to expand...
Click to collapse
I was on CM12 stock 5.0.2 (version 12.0-YNG1TAS2I3) and i wanted to root my phone , so I unlocked bootloader and rooted the phone but now I want to flash a new Rom but I ve read in a couple of rom threads that we have to flash another 5.1nightly before flashing a ROM and I am not sure I understand this part.
I would be grateful if someone could help me with the process of flashing a 5.1 rom and gaaps for the first time on a freshly rooted phone
P.S : ( I also want to use calaukin's gaaps modified by mohit (http://forum.xda-developers.com/oneplus-one/themes-apps/gapps-modified-slim-gapps-calkulin-t3082242).
Flashing the CM12.1 nightly first ensures that your firmware is up to date. The process goes like this:
1. Download the latest CM12.1 nightly and install it with your custom recovery (no need to flash gapps, but make sure you perform a full wipe (system, data, cache, dalvik cache) first).
2. Boot the phone up once.
3. Boot back into your custom recovery and perform a full wipe.
4. Install your chosen ROM + gapps.
5. Boot phone.
6. Enjoy.
Heisenberg said:
Flashing the CM12.1 nightly first ensures that your firmware is up to date. The process goes like this:
1. Download the latest CM12.1 nightly and install it with your custom recovery (no need to flash gapps, but make sure you perform a full wipe (system, data, cache, dalvik cache) first).
2. Boot the phone up once.
3. Boot back into your custom recovery and perform a full wipe.
4. Install your chosen ROM + gapps.
5. Boot phone.
6. Enjoy.
Click to expand...
Click to collapse
Thank you so much . I followed your guide too so thank you for the support .
It is not necessary to flash nightly first, most ROM threads provide a separate firmware flashable .zip (just make sure it is flashed correctly, cause people reported issues with newer TWRP than 2.8.6.0)
davebugyi said:
It is not necessary to flash nightly first, most ROM threads provide a separate firmware flashable .zip (just make sure it is flashed correctly, cause people reported issues with newer TWRP than 2.8.6.0)
Click to expand...
Click to collapse
I used to share your opinion. But, while a lot of ROM threads do provide a firmware zip, they aren't maintained, it's usually uploaded and forgotten about. Flashing the nightly ensures that you're on the very latest firmware available.