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.
Related
Hi All,
I have posted this on the GooManager thread but there hasn't been much activity there recently so asking here as well. Noob question on GooManager...I have the AOKP rom installed on my Sensation and GooManager notifies me of updates to my ROM every now and then. I just want to know if updating my ROM build with GooManager will reset all my custom ROM settings and preferences or will they all be preserved? I'd like to keep my ROM up to date but if it means spending all the time again to setup my preferences and icons/widgets/home screens etc. then I'd rather stick with what I have.
TIA!
I'd recommend to use GooManager only to download the newest ROM and flash it from recovery.
I asume you're using AOKP Swagger from frankenstine, the same I use.
I just download the update from GooManager, boot to recovery, flash ROM, gapps and 4.2 stuff and are ready to go.
All my settings are their after updating - only AdAway needs a reconfiguration and a reboot (and I need to set my alarm clock since I'm overwriting that). Basically you keep all your settings except those you made to the kernel.
Regards
lolmachine4 said:
I'd recommend to use GooManager only to download the newest ROM and flash it from recovery.
I asume you're using AOKP Swagger from frankenstine, the same I use.
I just download the update from GooManager, boot to recovery, flash ROM, gapps and 4.2 stuff and are ready to go.
All my settings are their after updating - only AdAway needs a reconfiguration and a reboot (and I need to set my alarm clock since I'm overwriting that). Basically you keep all your settings except those you made to the kernel.
Regards
Click to expand...
Click to collapse
Oh perfect, yes indeed I am using that exact ROM.
OK so when I boot to recovery, I shouldn't do any wiping? Just simply flash the new file? Will the updated gapps package be in the download I get from GooManager?
freddysensation said:
Oh perfect, yes indeed I am using that exact ROM.
OK so when I boot to recovery, I shouldn't do any wiping? Just simply flash the new file? Will the updated gapps package be in the download I get from GooManager?
Click to expand...
Click to collapse
I only wipe dalvik & cache after each update.
I can't say something about what GooManager downloads as "gapps", I use some I downloaded some weeks ago + some old version of 4.2 stuff. I might need to update my flash-setup too
lolmachine4 said:
I only wipe dalvik & cache after each update.
I can't say something about what GooManager downloads as "gapps", I use some I downloaded some weeks ago + some old version of 4.2 stuff. I might need to update my flash-setup too
Click to expand...
Click to collapse
Thanks lolmachine, for the benefit of anyone who might have the same question as me the following worked:
- Downloaded latest build of my AOKP Rom via GooManager
- Downloaded latest gapps package for my ROM via GooManager
- Boot to Recovery
- Flash new ROM file and then gapps package
- Restart.
My only question is, I didn't wipe davlik and cache so should I, and what difference does it make if I don't?
I used Goo the other day to flash, ummm, bugger, can't remember if it was an update or a new rom.
Oh now I remember, the latest one was an update to Bruce's Rom. I do believe when I tapped flash rom it booted to recovery (the one it installs) and I may have had to select "Install" from there, don't think so though. Either way, I used Goo to handle the install.
I didn't do a wipe. From what I've picked up, wiping is a good way to cover your butt. So if you're having issues and didn't wipe, you go back and do it all again with a wipe. Doing the wipe to start with means you can eliminate those types of issues from the start.
Someone can correct me if I'm wrong (which I probably am )
Hi there, I also received an update to my ROM via Goo Manager. It is CyanogenMod 10.1 by Albinoman887 for my HTC Sensation XE. I am using the EXT4 bootloader. I just installed it a few nights ago so I am completely new to rooting. My question is that there is no option to wipe dalvik cach. EXT4 just says wipe cache, wipe data and wipe system. Does wipe cache wipe dalvik cache as well. Also do I need to re-flash gapps as well after updating and will this wipe my gmail accounts etc?
Thanks,
Adam
thisisadamh said:
Hi there, I also received an update to my ROM via Goo Manager. It is CyanogenMod 10.1 by Albinoman887 for my HTC Sensation XE. I am using the EXT4 bootloader. I just installed it a few nights ago so I am completely new to rooting. My question is that there is no option to wipe dalvik cach. EXT4 just says wipe cache, wipe data and wipe system. Does wipe cache wipe dalvik cache as well. Also do I need to re-flash gapps as well after updating and will this wipe my gmail accounts etc?
Thanks,
Adam
Click to expand...
Click to collapse
You want to select "wipe dalvik+cache" option when you flash an update.
There's no need to flash gapps after a ROM update.
Sent from my Ouya
AndroidSupporter318 said:
You want to select "wipe dalvik+cache" option when you flash an update.
There's no need to flash gapps after a ROM update.
Sent from my Ouya
Click to expand...
Click to collapse
Thanks very much, downloading it now.
Help
im using albinoman's jelly bean rom
excuse me for noob doubts but
1) goo manager shows i have an update, so ive downloaded it. its a zip just like the rom n not just a small update. i have downloaded it now what should i do?
2) if i have to go to the recovery and flash the zip then i have to wipe only the cache right? Im using 4ext recovery.
3) will all my apps get uninstalled? what about the app data?
4) what about gapps? i have a gapps zip file, will i have to flash it again after the update?
Please reply thanks
I finally rooted phone after silly VMUNE7 thing on Verizon but after I get the install openrecoverscript and hit reboot recovery it does not go to teamwiz bootload instead I get something with a green driod on the bottom saying downloading but above it saying in red can't download Odin mode?? Please help I want to run cleanrom for better battery and less bloatware and keep my touchwiz. :crying:
all3rd said:
I finally rooted phone after silly VMUNE7 thing on Verizon but after I get the install openrecoverscript and hit reboot recovery it does not go to teamwiz bootload instead I get something with a green driod on the bottom saying downloading but above it saying in red can't download Odin mode?? Please help I want to run cleanrom for better battery and less bloatware and keep my touchwiz. :crying:
Click to expand...
Click to collapse
sorry man but i think you are talking for a samsung device am i right?
if yes then this is only for sensation/XE/4G devices
yasho170 said:
im using albinoman's jelly bean rom
excuse me for noob doubts but
1) goo manager shows i have an update, so ive downloaded it. its a zip just like the rom n not just a small update. i have downloaded it now what should i do?
2) if i have to go to the recovery and flash the zip then i have to wipe only the cache right? Im using 4ext recovery.
3) will all my apps get uninstalled? what about the app data?
4) what about gapps? i have a gapps zip file, will i have to flash it again after the update?
Please reply thanks
Click to expand...
Click to collapse
Simple.
Go to recovery.
For s-on you must enable smartflash.
Do a nandroid backup.
Dirty flash the update (meaning flash over the previous rom without wiping).
Dirty flash gapps (signed only).
Wipe cache + dalvik.
Reboot.
If it can't boot/run properly then you can just restore the backup or do a clean flash.
First off I'm not experienced in any way, got my Sensation unlocked, rootet and installed Sultanxda's 4.4.2 ROM for sensation. I'm on S-On, too, if anyone wonders.
Updating didnt affect my apps as far as I can tell. Everything seems to be the way as before and everything seems to be working.
What I did was download the ROM manually since the download with goomanager didn't work. I downloaded gapps as backup because I didnt have the zip on my SD, just in case anything would go wrong.
You only need to boot into recovery, with S-On make sure smartflashing or something like that is on, select the zip, flash it and then select wipe cache +dalvik.
It's pretty much what AndroidSupporter318 wrote, just wanted to give feedback and say what I did in detail in case anyone was still wondering.
LxMaD
I guaranted 4EXT Recovery for this type of problem. U don't need to boot into recovery and work with 4ext is very simple.
Look, I need some help.
This morning, my GFit (running CM10.1, latest stable build) went crazy, by FCing Play Store and Services, and as well Poweramp everytime I tried to open it. I used my process killer and killed everything that was running. But then Trebuchet (launcher) and other things started FCing and I had to remove the battery of it. Then I got bootloop when I turned it on. Removed the battery again, wiped cache, data, dalvik-cache, fixed permission and battery stats and tryed to boot. Again I got bootloop. Then I re-wiped everything (I didn't fix permission or battery stats) and tryed to re-flash CM10.1. Bootloop again.
I then decided to install a stock rom and unroot my GFit via Odin. Downloaded the brazilian stock rom from sammobile.com, put the BENI.ops file, choosed the one package file from the stock rom and started. It passed on Odin after 4:51 minutes. I rebooted in recovery, wiped data and rebooted it normally. I'm still getting bootloops. I just don't know what to do anymore. I'm considering in taking it to Samsung to try to fix it. Does anyone have any idea or could help me out?
By the way, I'm getting this error in stock recovery when I try to wipe data. (E:format_volume: rfs format failed on /dev/stl13) and I'm getting an error when rebooting my Fit (something like /dataReboot).
Don't flash official stock rom directly over cm10+... U should have flashed cm7(for instance) easily & it would b all fine...
So, two different ways u can try now...
Method 1:-
Flash cwm recovery by tjstyles (v5.0.2.7) via Odin...Then boot into recovery mode...wipe data/cache/dalvik-cache/system)...Then flash the latest official cm7...Then again wipe data/cache/dalvik-cache. & see if it boots...
Method 2:-The case where ur bootloader might b the problem:-
Now, first of all u *must* flash froyo(4 package) via Odin...wipe data/cache(factory reset) & see if it boots. If it does... then flash gingerbread as usual.
Hope this helps...!!!
Galaxy_Rohit said:
Don't flash official stock rom directly over cm10+... U should have flashed cm7(for instance) easily & it would b all fine...
So, two different ways u can try now...
Method 1:-
Flash cwm recovery by tjstyles (v5.0.2.7) via Odin...Then boot into recovery mode...wipe data/cache/dalvik-cache/system)...Then flash the latest official cm7...Then again wipe data/cache/dalvik-cache. & see if it boots...
Method 2:-The case where ur bootloader might b the problem:-
Now, first of all u *must* flash froyo(4 package) via Odin...wipe data/cache(factory reset) & see if it boots. If it does... then flash gingerbread as usual.
Hope this helps...!!!
Click to expand...
Click to collapse
I tried Method 1 and it didn't work, then I asked a friend with a bit more experience in Android to do Method 2 for me and my GFit is back to life.
So thanks man! Really appreciated!
ur most welcome...!!
Hi. I have tbe same problem, can u elaborate the method 2 with froyo links.
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!
Hi all...
I tried to upgrade by Tab 2 7" to KitKat today and failed. I installed Clockworkmod successfully, but then started getting error 7's. I discovered this was because it was outdated. I've tried to install updated clockwork mod which it says has been successful - but doesn't change the original.
I did a backup of my original rom, but this has failed to reinstall. I've tried to put an old version of cyanogen on it, which also has failed, and re-downloaded the stock rom from samsfirmware which passes through ODIN, resets but then the tab 2 hangs on the Samsung screen - flashing.
I can't seem to resolve it.
Has anyone got any ideas? I can't access anything other than clockworkmod - so if you think you know of a way I can successfully upgrade it I may stand half a chance.....
Thanks
Tim
sheltont said:
Hi all...
I tried to upgrade by Tab 2 7" to KitKat today and failed. I installed Clockworkmod successfully, but then started getting error 7's. I discovered this was because it was outdated. I've tried to install updated clockwork mod which it says has been successful - but doesn't change the original.
I did a backup of my original rom, but this has failed to reinstall. I've tried to put an old version of cyanogen on it, which also has failed, and re-downloaded the stock rom from samsfirmware which passes through ODIN, resets but then the tab 2 hangs on the Samsung screen - flashing.
I can't seem to resolve it.
Has anyone got any ideas? I can't access anything other than clockworkmod - so if you think you know of a way I can successfully upgrade it I may stand half a chance.....
Thanks
Tim
Click to expand...
Click to collapse
Use Odin to restore to the stock ROM. Download the stock rom from samfirmware.com and flash it in Odin as PDA. Then, use the latest recovery (either TWRP, CWM, OR PhilZ) from @Android-Andi's recovery thread in the Dev section. You should now be able to flash any ROM you want to. Make sure you do a backup and a wipe system, cache, Dalvik, data, and android secure (if it's an option.)
Sent from my SGH-T989
thanks and....
Thanks so much, does it matter that it won't boot with the stock Roma which I've installed from sams? Will the recovery program still work?
sheltont said:
Thanks so much, does it matter that it won't boot with the stock Roma which I've installed from sams? Will the recovery program still work?
Click to expand...
Click to collapse
What do you mean? Did you flash the stock ROM in Odin?
Sent from my SGH-T989
yep
jrc2 said:
What do you mean? Did you flash the stock ROM in Odin?
Sent from my SGH-T989
Click to expand...
Click to collapse
Yes, I did twice and it's still hung after apparent success installation according to Odin. I've tried it twice.
No success
Thanks
What I've done tonight is reflashed the original Rom - this time it blew away Clockworkmod. It still wouldn't boot. I then put a recovery solution on from your link, which has flashed well. However I've then tried three ROMS and each have hung after installation on the initial boot.
I'll try them again tomorrow night - but do you have any idea why three ROMS plus the stock keep failing?
Thanks
Tim
sheltont said:
Thanks
What I've done tonight is reflashed the original Rom - this time it blew away Clockworkmod. It still wouldn't boot. I then put a recovery solution on from your link, which has flashed well. However I've then tried three ROMS and each have hung after installation on the initial boot.
I'll try them again tomorrow night - but do you have any idea why three ROMS plus the stock keep failing?
Thanks
Tim
Click to expand...
Click to collapse
Did you wipe system, cache, Dalvik cache, and data before flashing and wipe cache and dalvik after flashing? And your tablet will bootloop after a reinstallation in Odin because Odin does not wipe before installation. After flashing in Odin, reboot recovery (make sure tablet is unplugged,) and wipe data, cache, and dalvik cache. Reboot and you should be good to go.
Sent from my SGH-T989
good idea but still no success....
jrc2 said:
Did you wipe system, cache, Dalvik cache, and data before flashing and wipe cache and dalvik after flashing? And your tablet will bootloop after a reinstallation in Odin because Odin does not wipe before installation. After flashing in Odin, reboot recovery (make sure tablet is unplugged,) and wipe data, cache, and dalvik cache. Reboot and you should be good to go.
Sent from my SGH-T989
Click to expand...
Click to collapse
Hi, I've retried all that this morning-i must admit that I didn't know about wiping cache after install, however it's not made any difference, and still hangs on first boot...
Any other ideas? Thanks for all your help.
Happy success
Hi all
Thanks for all your help,especially rcj! I have managed to recover my device using cynagodmod 9 - it wont run 10 or 11 but at least its up and working - even if it's a downgrade from the Android version I was on Really don't care as I can use it again with a lot more memory.
Thanks - without you I would never have found Phils ROM which enabled me to get this far.
Tim
sheltont said:
Hi all
Thanks for all your help,especially rcj! I have managed to recover my device using cynagodmod 9 - it wont run 10 or 11 but at least its up and working - even if it's a downgrade from the Android version I was on Really don't care as I can use it again with a lot more memory.
Thanks - without you I would never have found Phils ROM which enabled me to get this far.
Tim
Click to expand...
Click to collapse
Which version of PhilZ? And I have found that TWRP 2.7.1.0 works better than other versions for KK.
Sent from my SGH-T989
Use latest Philz touch recovery. And use the rom and gapps compatible to your tab. Don't forget to reset to factory setting, clear cache and wipe dalvic cache before flashing the rom and gapps ☺
Sent from my GT-P3100 using XDA Free mobile app
directly..
sm-n915s in sktelecom
i first rooting by cf root in nj5? nj6?... i remember
flash skyhigh kernel 1.0, 1.1,1.2, 1.3
and ota update nj9
i installed cydia substrator, xposed modules.
after ota update nk5..
base band is gone
then flash nk5 stock rom by odin
i think all is well
but that is wrong..
problem is
1. lag, sometimes app is stop...
freeze but status bar is ok
2. sms is dont work
app is fine but....i cant send anything
3. allow super su freeze
super su permission window pop dont shown
4. random rebooting
i cant english well
but xda is only one web site about n915s
i want to fix my device
plz help me
1. BACKUP ALL DATA OFF DEVICE
2. Boot into CWM recovery
3. Wipe : system, DATA, cache, dalvik-cache
4. Boot directly into Download Mode
5. Flash stock firmware with Odin
In future, suggest to forget OTA. Use Odin !
UpInTheAir said:
1. BACKUP ALL DATA OFF DEVICE
2. Boot into CWM recovery
3. Wipe : system, DATA, cache, dalvik-cache
4. Boot directly into Download Mode
5. Flash stock firmware with Odin
In future, suggest to forget OTA. Use Odin !
Click to expand...
Click to collapse
I think that i was .....
i try again... your suggest