Related
This thread is for the support of CM9 ICS release by CyanogenMod
This is NOT an official CyanogenMod thread, and isn't officially supported by CyanogenMod or Teamhacksung.
This thread is designed to help keep the dev thread clean and clear for the dev's to do their magic. So please feel free to ask any questions about the ROM, but flaming will not give great results and will be reported
The main CyanogenMod CM9 ROM thread is HERE
The Nightlies can be found here
GAAPS can be found here
Look for 'gaaps-ics-********-signed.zip'
Modems for ICS:
http://soggycashew.weebly.com/cm7miui--ics-modems.html
Modem Coverage Map:
http://soggycashew.weebly.com/modem-location-map.html
ONLY USE THE MODEMS MADE FOR CM7/Miui/ICS.
Give the ROM thread and this one a good read before you post, you may find the answer is already available. Keep in mind that each device may behave slightly different, so YMMV
People have found different ways to successfully install, and it works for them, but their method may not work for everyone. So it is highly suggested to follow the method recommended by the developers.
This is copied directly from the dev OP:
"-First time flashing ICS to your Captivate (or coming from another ROM)?
1. Root your device and install ClockworkMod Recovery.
2. Reboot into Recovery using 3-button-combo
3. Do a Nandroid backup!
4. WIPE (wipe data/factory reset + wipe cache partition)
5. Install the ROM from internal sdcard using ClockworkMod Recovery
6. Optionally install the Google Addon
7. WIPE again or Calendar Sync will not work
-Upgrading from CM7?
1. Do a Nandroid Backup!
2. WIPE (wipe data/factory reset + wipe cache partition)
3. Install the ROM from internal sdcard using ClockworkMod Recovery
4. Optionally install the Google Addon
-Upgrading from another CM9 (or teamhacksung) Build?
1. Do a Nandroid Backup!
2. Install the ROM from internal sdcard using ClockworkMod Recovery
3. Optionally install the Google Addon
Note: The upgrade process from CM7 to ICS is automatic, but downgrading from ICS to CM7 (or restoring Nandroid) requires flashing twice. Once from ICS and again from CM7's recovery."
FAQ
The FAQ is available on Teamhacksung's Wiki. Please read before asking any questions and please feel free to edit it.
http://teamhacksung.org/wiki/index.php/Experimental:GT-I9000:Frequently_Asked_Questions
Known Issues
Please check the list of known issues before reporting bugs.
http://teamhacksung.org/wiki/index.php/Experimental:GT-I9000:Known_issues
Reporting Bugs
You are allowed to report bugs ONLY in the Development thread. Before reporting a bug, please make sure you are running as stock as possible. This means no custom kernel, no custom framework modification, etc. If you are using any of the above modifications, please flash the rom again to get rid of the modifications before reporting.
Grab a logcat right after the problem has occurred.
If it is a random reboot, grab /proc/last_kmsg. (Do not bother getting a logcat unless you can get it just before the reboot. A logcat after a reboot is useless)
Remember to provide as much info as possible. The more info you provide, the more likely that the bug will be solved. The following is a useful format to follow.
Thanks to the entire CyanogenMod Team for creating their magic for our aging Captivates!
I just registered so I can't post in the development thread... I hope this is the next best place...
I flashed build 3 of the ICS ROM and the DNS, at least for wifi, seems hardcoded to 8.8.8.8. I changed it to my local DNS ('su', 'setprop net.dns1 192.168.1.1'), checked that I could ping a local name, turned wifi off and on again, and it had gone back to 8.8.8.8. I'm new to Android so I don't know whether there's a way to set it harder, but I had expected that it would get the DNS servers from DHCP... that is definitely what stock Gingerbread and CM7 both did.
Hopefully some kind person will pass this message on to the developers... I am not sure whether this is the wifi DNS update issue listed in the Known Issues on the dev thread but if so maybe that should be marked confirmed
What should i do before flashing this rom? I'm currently with gal net miui. I assume that's cm7? So should i just flash after wipe? Or go back to stock first?
Sent from my I897 using XDA App
it states to wipe data and cache, then install from miui or CM7, no need to return to stock. Some run it better than others, mines running just fine with their release 3
Facebook Widget
Anyone having issues with the facebook widget?
Can't get it to work. Any suggestions?
anjosautomotive said:
Anyone having issues with the facebook widget?
Can't get it to work. Any suggestions?
Click to expand...
Click to collapse
Uninstall the app and reinstall from the market.
Glitch kernel let me OC to 1.4!
Thanks flashman that worked.
Dunno if anyone else has this issue but both mornings since flashing, I've woken up to an unresponsive touchscreen. clicking the hard button brings up the lock screen and everything looks right but it's just unresponsive to touch. I've had to fiddle with the hard buttons to be able to use the touchscreen again.
When finding things wrong with this build, you do have to realize that it's not even a beta yet, and things are gonna be slow/broken/or not integrated yet. I'm sure the devs will add all this stuff once the basic framework is solid. And like someone else stated, the best way is to go from CM7. It's very easy. I can even flash back and forth no hassle
Camera
Is there a zoom on this camera?
flashman2002 said:
Glitch kernel let me OC to 1.4!
Click to expand...
Click to collapse
Are you saying we can use Glitch on the the ICS Rom?
---------- Post added at 10:39 PM ---------- Previous post was at 10:09 PM ----------
Never Mind
http://forum.xda-developers.com/showpost.php?p=19915350&postcount=5292
after updating (after clearing the phone again) to build 5, i get more errors than with build 3. Gonna go back and try it again.
Two issues in build 5, calendar issues, no sync. Tried custom apk's, no luck with that. Reflashed gappsv5 still no good. Was working on build3 with gapps v4.1. Also anyone able to get their facebook account to sync. Try adding facebook account and just nothing...
uzbeque said:
I don't know if it is right to begin new thread, but it seems it is better to ask questions here?
my question is, how can I manage desktops? there are only 5 desktops, I want more.
thanks
Click to expand...
Click to collapse
ICS only allows 5 homescreens
Sent from my SAMSUNG-SGH-I897 using xda premium
Having market download issues, even with free apps it just hangs on the downloading line. Wipe cache and reflashed GAPPS v.5 and it still is having issues. I was able to download World of Goo last night but nothing good this AM. Any other suggestions that may work?
I am also was having market issues. What helped me was making them download to phone from the market website. It helped a bit. And yes, the Facebook sync seems broken
Sent from my ICS Captivate
doctor_r said:
Two issues in build 5, calendar issues, no sync. Tried custom apk's, no luck with that. Reflashed gappsv5 still no good. Was working on build3 with gapps v4.1. Also anyone able to get their facebook account to sync. Try adding facebook account and just nothing...
Click to expand...
Click to collapse
I had the same calendar sync problem. Did a wipe, flashed build 5, immediately flashed Gapps v5.1 before rebooting, and that fixed it for me.
any specific kernel? where do I pick up just the kernal? just moved from cm7 nightly b181
doctor_r said:
Two issues in build 5, calendar issues, no sync. Tried custom apk's, no luck with that. Reflashed gappsv5 still no good. Was working on build3 with gapps v4.1. Also anyone able to get their facebook account to sync. Try adding facebook account and just nothing...
Click to expand...
Click to collapse
FB sync doesn't work on ICS at all so I wouldn't expect a quick fix. I downloaded the friendcaster app and used that to sync with my contacts.
wasimalam said:
any specific kernel? where do I pick up just the kernal? just moved from cm7 nightly b181
Click to expand...
Click to collapse
You don't need to flash a kernel for this. At least it's a very bad idea in this stage of development. But if you need it for some other purpose, it's in the OP of the ICS thread
Okay so i messed up and geting fc issue with my text messaging app and am not able to install it from titianium backup no matter what i do (i have pro). Found /system image here and just need help installing it.
I want to keep it stock but remove bloat. Can i just copy the zip file to sd and install? or use RSD Lite?
I also read that if you replace the build.prop to and older say 2.3.4 and then try to do the ota upgrade it will work. Can anyone confirm this works and has older build.prop?
Using XT860 on Bell canada
**Backup whatever you can before using RSDlite as this will wipe your phone (except /sdcard /sdcard-ext)**
It's probably possible to fix your SMS issues but I don't know how.. maybe start by taking a look at the logs..
adb logcat .. or some logcat app from the market. You should probably start by this, unless you feel ready to jump into custom ROMs..
If all else fails you can always get a fresh system image..
But unlike the XT862.. we XT860 users on Bell don't have a leaked official SBF file to flash back to stock Bell with RSDlite/fastboot.
But we can flash a few leaked Latin America SBF files and change the language back to English/French.
http://sbf.droid-developers.org/umts_solana/list.php
The only way that I know of so far.. to get back to stock Bell is to use Willis111 file and flash it from recovery like a ROM:
http://forum.xda-developers.com/showthread.php?t=1465153
Either way, I suggest you then install hashcode's safestrap so you have working custom recovery with backups and everything.. and try out the latest CM9. Safestrap will allow you to easily switch between stock and custom ROM and backup/restore your future setups in case something goes wrong in the future..
http://blog.hash-of-codes.com/
~Sent from my unbricked XT860 running CM9 installed in hashcode's safestrap over the LatAm 2.3.6 SBF.
i used http://forum.xda-developers.com/showthread.php?t=1340492 and got all my bloat back.
But as soon as i removed any app again using TB it breaks messaging, think i'm uninstalling something that the messaging app needs but don't seem like i'm touching anything that has to do with it.
don't really want to go into custom roms this phone is for my mom and already wasted a day on it. Just need stock with bloat removed so its a bit quicker. My HTC is all decked out on the other hand
Be careful what you uninstall in TB..
I remember having issues after deleting some yahoo thing on mine when I was stuck on stock. (Contacts would FC)
EDIT: I did freeze and/or uninstall those without any issues citrix, kobo, GPS Nav., a few games, and zoompass when I was stock.
it seems to be alright, i striped out everything such as media connect, dlna, portal etc. Just to make the phone a simple phone.
It seems when i removed the email app it was causing the messaging app to fc. The phone seems stable after a complete wipe and don't see any fc'ing.
What i don't get is if i use TB to uninstall any app i cannot get TB to restore it and the only way is to flash the system image again.
I may just flash system again and just freeze everything i don't want.
Glad to see someone using my system dumps!
Did you do the OTA to 2.3.6 yet? That fixes A LOT of bugs, improves battery life and camera as well.
Yesterday I just loaded my first custom ROM on my phone, using the safestrap method and threw on CM9... so far I think it's really sweet. I really hope we get Official ICS but if we don't I'm going to stick with a custom ICS rom.
I can confirm you shouldn't uninstall or freeze the Email app (universal inbox thing) as it will indeed FC a few other things..
What I do in TB for stuff I want to completely uninstall is this:
-convert to user app (as opposed to system app)
-back it up
-uninstall as if it was any other app (from TB or not..)
If I want to restore.. I restore it from TB.. which reinstalls it as a user app.. then change it back to system app from TB.
Alternative: manually backup and rename or move the apk in /system..
And put it back in to restore.
In any case.. a reboot might be a good idea after restoring..
PS: CM9 has been my daily driver for a while now.. I had to go back to stock for a few minutes the other day (needed the HDMI mirror..) and I really wouldn't go back to stock as my daily..(Safestrap works wonders for switching between the two though..)
danifunker said:
Glad to see someone using my system dumps!
Did you do the OTA to 2.3.6 yet? That fixes A LOT of bugs, improves battery life and camera as well.
Yesterday I just loaded my first custom ROM on my phone, using the safestrap method and threw on CM9... so far I think it's really sweet. I really hope we get Official ICS but if we don't I'm going to stick with a custom ICS rom.
Click to expand...
Click to collapse
phone came with 2.3.6 so no OTA, you dump works wonders. I may flash it again and uninstall thinks like kobo, citrix etc and freeze others like universal inbox.
What does freezing do anyways, does it stop it from loading in RAM?
I've been using my phone for months already and have not experienced this...my messaging app always closes upon hitting the back button on my phone (GT-N7000)...a week ago I rooted my phone using the cwm.zip method and all was ok. I check for brick bugs (negative) and all the stuff are working fine...read the thread here saying cwm.zip can brick my phone I immediately looked for a solution...but before I installed a new kernel I tried installing busybox using the app called BusyBox Pro from google play...I noticed that when I open my messaging app and hitting the back button...it won't close, I'd have to go inside task manager and manually close it from there...I've also read some people saying that this was normal...does that mean that when I got my phone brand new that it wasn't normal because it was closing the app previously???
Anyways I tried flashing a new rom (stock ICS rom) (did not wipe I just flashed the stock rom from Mobile Odin) and did a factory reset afterwards...still the same...i did this twice with the same result...messaging app is still not closing properly. Now I have rooted my phone again using the safe method provided in this forum flashed the superSU and the busybox afterwards and flashed the Philz kernel using Mobile Odin as my final step.
I did find a way to fix this by ticking on the developer options "do not keep activities" and it does close the application when I hit back (I don't think checking the "do not keep activities" is also a proper fix anyways) but now this will leave me with another problem of the new message notification (1 inside the red circle) not going away even if all messages are already checked. Both situations are quite annoying so if anyone out there has any solution to this would be of really great help to us who has this problem...
I saw a few threads saying to replace the mms.apk file with a new one and they did say it fixed their problem...i dunno if this is a good idea but if it is where can I get the apk for the stock messaging app for ICS 4.0.4? would any expert recommend this? It does not have any CPU usage...only takes up RAM and I know this is not much of an issue but it is really annoying as hell and is weird.
as you already have flashed ics again, I am not sure of replacing the mms.apk will resolve the issue. anyhow the mms.apk can be found in rom you downloaded. open up the rom using 7z and the factoryfs.img file. now using sgs2ext4.jar and linux reader you can extract the mms.apk.
Other option is to install a wipe gb rom and the upgrade to ics again
Message App
nokiamodeln91 said:
as you already have flashed ics again, I am not sure of replacing the mms.apk will resolve the issue. anyhow the mms.apk can be found in rom you downloaded. open up the rom using 7z and the factoryfs.img file. now using sgs2ext4.jar and linux reader you can extract the mms.apk.
Other option is to install a wipe gb rom and the upgrade to ics again
Click to expand...
Click to collapse
I thought factory resetting would do the trick but done it twice and it did not...it was not like this before...wish there is a solution other than flashinig a new rom. By using a 3rd party app...will it disable my stock messaging app? maybe that will work what do you think?
like go sms or something?
nokiamodeln91 said:
like go sms or something?
Click to expand...
Click to collapse
yes i think...will that overwrite my messaging app or disable it or will I be having 2 messaging apps? sorry noob question.
What does wiping do? Maybe that's what I didn't do reason my message app stayed this way...
3 wipes
wipe cache
wipe data - same as factory reset
wipe dalvik
the wipe I mentioned was to format the system as we do on Windows and then install the new os again like fresh.
I don't know. May be you will have 2. but if the go sms is able to read your text messages as well the you can go in to application - all and disable the messaging
nokiamodeln91 said:
3 wipes
wipe cache
wipe data - same as factory reset
wipe dalvik
the wipe I mentioned was to format the system as we do on Windows and then install the new os again like fresh.
I don't know. May be you will have 2. but if the go sms is able to read your text messages as well the you can go in to application - all and disable the messaging
Click to expand...
Click to collapse
So factory resetting = wipe data right? and the cache and dalvik is not wiped in this process? hmmmm...I'm really wondering what the ^&(& happened to my messaging app and why this issue won't go away...really weird.
Anyways still trying to replace my stock mms.apk with something else...but none seems to work...i have set the permissions correctly but still I only get a black screen and then force closes after. Trying this method before resorting to a 3rd party app which I really am not into...I like my phone stock and clean and this abnormality in its performance is making me crazy. Sorry it's like an obsessive compulsive behaviour LOL.
I guess instead of trying so many things, it's better that if you install a wipe gb rom and then test the message app. If all ok and then upgrade to ics back
nokiamodeln91 said:
I guess instead of trying so many things, it's better that if you install a wipe gb rom and then test the message app. If all ok and then upgrade to ics back
Click to expand...
Click to collapse
I tried replacing the modified mms.apk from rocketrom v8 LRK build and still unsuccessful. Hmmm still trying to burn all possibilities before I flash a new rom again. Thanks!
I have tried installing a 3rd party SMS application and disabled the stock message application and still the problem persists. Will try one last idea afterwards I'll be off to flash a new GB rom and upgrade back to ICS.
Hey guys,
Sorry if this seems really noobish, but I seem be to kinda lost in all of this ROM'ing goodness.
I have read up on installing custom roms and plan on doing so but I have a couple of questions first before I take that last step (already unlocked and rooted on my One) - note: I have read through the guides but I still seem a little confused as to what exactly changes.
I notice that all tuts mention that you will lose all data on your phone. Does this include installed apps or are we just talking system files needed for the new rom? I have my phone setup already and have my apps backing up with Helium (Carbon) but this is something I seem to be a little confused with
Secondly, using something like CWM (Premium), can I update my ROM quickly and easily without losing any data?
I know that unlocking my bootloader will not get me OTA's so I am looking forward to using many of the awesome ROMs here on the site!
1) When you flash a rom, you need to do a full wipe in aroma.
Full wipe will erase all but not the sd, so your app in home, your background, your account will be erased.
2) You can upgrade your rom with CWM if is the same rom and the base isn't different.
If the base is different you have to do a full wipe.
One more
How likely is base to change for a ROM package? And if I have to flash that new ROM package instead of doing the update through CWM, am I back at square one again with my apps and data or is it just updating what it needs to?
Thanks again for the help!
Then:
Now, all the rom is based on 1.29.401.13.
When it will change (it depens from htc) and you will flash the latest update of rom, you have to do a full wipe, and you will lose all file, settings and other.
Instead, if you have to flash an update like: you're on 2.5 to 2.6, you can flash the rom with only dalvik cache and cache wipe.
But it depens, you always have to read in thread rom
I guess its not so big of a deal considering I can backup most of my apps using Helium and the rest of the apps can just be redownloaded if I keep a list. Configurations should be backed up anyways.
Thanks for the help!
If you're rooted and you will restore your app after a full wipe, i advise you titanium backup.
With this you can do a flashable zip with all your apps and data
Thanks!
I will take a look at Titanium backup and see what it can do! It would only make sense that someone would invent a way to backup all your apps and data (no matter what) to be able to restore them after a ROM update that wipes the phone completely!
Titanium backup can do this
However, only data app, not system app.
If you backupping system app too, you can have issue with new update of rom
Hey all. Had this phone for a while. All of a sudden after a routine poweroff (cuz I was flying), it refuses to boot up and is stuck on the flashing samsung text. Running the official ICS rom. No flashes/hacks/anything exciting ever done with this phone.
After a few browses at the topics here, I found out that I can access recovery mode (vol up + home + power). It shows the following message:
#MANUAL MODE#
-- Appling Multi-CSC...
Applied the CSC-code : INV
Successfully applied multi- CSC
Can anyone help me out here?
First and foremost before you do anything flash a custom kernel which will stop the brick bug from happening:
http://forum.xda-developers.com/showthread.php?t=1901191
Once that is done, do a data wipe in recovery mode. If it doesn't boot then you will have to reflash (a custom ROM or using download mode to flash an official ROM).
XxPixX said:
First and foremost before you do anything flash a custom kernel which will stop the brick bug from happening:
http://forum.xda-developers.com/showthread.php?t=1901191
Once that is done, do a data wipe in recovery mode. If it doesn't boot then you will have to reflash (a custom ROM or using download mode to flash an official ROM).
Click to expand...
Click to collapse
Many thanks for the reply. Just a few questions before I jump into it though...does the custom kernel do anything else besides safeguard from bricking? (I'm referring to not being able to access google services and the like)
Next - if I do a data wipe, doesnt that mean that all the data (pics, contacts, sms) will go? Would there be a way to preserve these?
Sorry I do realize these are really green questions...never had a problem with this phone before and never tried experiementing
vipster said:
Many thanks for the reply. Just a few questions before I jump into it though...does the custom kernel do anything else besides safeguard from bricking? (I'm referring to not being able to access google services and the like)
Click to expand...
Click to collapse
The custom kernel will stop the brick bug from happening and it will give you a custom recovery, If you have a custom recovery then you can flash other custom ROMs. You won't be limited in any way whatsoever.
vipster said:
Next - if I do a data wipe, doesnt that mean that all the data (pics, contacts, sms) will go? Would there be a way to preserve these?
Click to expand...
Click to collapse
I think that if you do it on the stock recovery (the one you have now) then it will remove everything: 3rd party apps, pictures, contacts, smses, settings etc. If however you do it on philz then it will remove your installed apps, settings, smses, contacs, call logs etc. BUT it will not remove all the files on your sd card (pictures and other files).
vipster said:
Sorry I do realize these are really green questions...never had a problem with this phone before and never tried experiementing
Click to expand...
Click to collapse
No problem, better to be safe and sure than having a bricked phone
Also, I read where the smses and call logs are stored (but not the contacts):
mmssms.db (messages and mms data bases)
telephony.db (this one contains call logs)
They are located in:
/data/data/com.android.providers.telephony/databases/
You could use ADB or something simpler (if you have that custom recovery I linked earlier) - aroma file manager:
http://forum.xda-developers.com/showthread.php?t=1646108
Then you can copy those files to your sd card.
Also, chances are your contacts are on google: https://www.google.com/contacts/
And also if you reflash and sign into your google account at startup then you may be able to restore your apps (but without the settings to them).
Let me know if you're unsure about anything.
The Custom kernel have a lot of useful tools besides safeguarding from bricking.. It wont interfere with accessing google services and all that..
If you do a factory reset, it will wipe you user account data ( i.e only contacts, sms and installed apps ) and it wont wipe your pics, songs etc.. When i first installed a custom Rom i imported all my contacts from sd card and when it asked me for a location to save contacts, i selected my google account. That way all my contacts are always synced and saved in google.. So whenever you flash a Rom and enter you phone, it will ask you google account to begin with and the contacts will be automatically synced to your phone!
If you are a starter and interested in Rooting and Flashing Custom Roms i would recommend reading Dr.Ketan's guide.
Dr.ketan's Rooting guide :- http://forum.xda-developers.com/showthread.php?t=1329360. Try the ercommended method 1A.. It will install custom kernel and as well as root your phone!
Enjoy and Happy Flashing
CustomRomAddicts said:
If you are a starter and interested in Rooting and Flashing Custom Roms i would recommend reading Dr.Ketan's guide.
Click to expand...
Click to collapse
On it...many thanks! The rooting though seems to have the effect of removing google play and other services (SNote for example). I read that its possible to get play/youtube/gmail back, but what about the other 3rd party apps?
XxPixX said:
No problem, better to be safe and sure than having a bricked phone
Let me know if you're unsure about anything.
Click to expand...
Click to collapse
That clarified a bit indeed! Unfortunately, my google contacts are filled with miscellaneous emails and no phone numbers...I should really get on top of making better backups.
Question #3: [EDIT] looks like the original ROM was DDLSC...trying for the same here.
Question #4: It seems one can run a backup directly from PhilZ. Shall I try that out before wiping everything into oblivion?
vipster said:
On it...many thanks! The rooting though seems to have the effect of removing google play and other services (SNote for example). I read that its possible to get play/youtube/gmail back, but what about the other 3rd party apps?
Click to expand...
Click to collapse
First of all, rotting doesn't remove or effect of removing google play.. S-Note, S planner and other samsung apps will work only if you are flashing a Touchwiz based Rom.. Those apps wont work in CM, PA and AOKP Roms cuz they need TW framework to work with!
If you are thinking of flashing of TW based Roms, i would recommend 2 Roms to take a look at..
X-Rom ( http://forum.xda-developers.com/showthread.php?t=2320871&nocache=1 ) This is the Rom, i am currently using.. It will give your phone a tablet UI, thus taking advantage of your Note's large real estate screen! .. Multi window, floating window and buttery smooth and lots of features!
You can also check out the Note 8 Apps ported to our galaxy note N7000, if you are interested.. ( http://forum.xda-developers.com/showthread.php?t=2217662 )
Arya Mod ( http://forum.xda-developers.com/showthread.php?t=2575767 ) This is also a great Rom and cool icons and themes!
vipster said:
Question #3: the link asks me to choose a kernel. Can this be random choice or does it mean much?
Click to expand...
Click to collapse
First go to that rooting guide and root using the 1A method. It will give you philz kernel.. Then install one of the Rom Above! ( If you want a TW Roms that is )..
Then if after flashing a TW based Roms, flash this kernel to get a amazing and battery life ! It makes the ROM buttery smooth too ( http://forum.xda-developers.com/showthread.php?t=2638337 )
Note that this rom only works with 4.1.2 JB Roms and Most TW Roms are 4.1.2 JB anyways!
vipster said:
Question #4: It seems one can run a backup directly from PhilZ. Shall I try that out before wiping everything into oblivion?
Click to expand...
Click to collapse
Install this app to take nandroid backup without having to go into Recovery ( https://play.google.com/store/apps/details?id=com.h3r3t1c.onnandbup&hl=en )
Note that this requires root, which means it will only work after you have finished rooting!
Enjoy and Happy Flashing
CustomRomAddicts said:
Install this app to take nandroid backup without having to go into Recovery
Note that this requires root, which means it will only work after you have finished rooting!
Enjoy and Happy Flashing
Click to expand...
Click to collapse
X-Rom it is then. Although my primary problem is that the phone wont start at all...so can't download any app till I get it up and running
vipster said:
X-Rom it is then. Although my primary problem is that the phone wont start at all...so can't download any app till I get it up and running
Click to expand...
Click to collapse
If you still can't get past the Samsung logo, check my thread ( http://forum.xda-developers.com/showthread.php?t=2654194 )
I had the same prob a few days ago! and i solved it!
---------- Post added at 04:19 PM ---------- Previous post was at 04:16 PM ----------
CustomRomAddicts said:
If you still can't get past the Samsung logo, check my thread ( http://forum.xda-developers.com/showthread.php?t=2654194 )
I had the same prob a few days ago! and i solved it!
Click to expand...
Click to collapse
To install stock Roms check this guide by Dr.ketan ( http://forum.xda-developers.com/showthread.php?t=1424997 )
NOTE:- Just make sure you select Normal method, when you open the Supersu and its asks you to update Supersu binaries..
So finally solved! Thanks heaps to CustomRomAddicts and XxPixX for the help!
Just for anyone else stuck in the same boat:
Problem: Phone won't boot, stuck at the flashing samsung logo.
Tried and didn't work: remove sim, remove memory card, different battery, on charge, off charge.
Solution:1) Installed Philz kernel (found the kernel I require by looking at the stock rom code...mine was DDLSC) on my external SD. You can find this out by looking at the stock roms downloads on Dr. Ketan's page and finding out where you got your phone from in the first place (assuming it wasn't parallel imported).
2) Put the external SD back in, go into recovery mode (vol up+home+power), backup whatever I require (which in my case was a full backup).
3) Factory reset. (Mine did not delete the pictures, songs etc. It did delete all contacts, sms, call logs, applications, settings and updates).
vipster said:
So finally solved! Thanks heaps to CustomRomAddicts and XxPixX for the help!
Just for anyone else stuck in the same boat:
Problem: Phone won't boot, stuck at the flashing samsung logo.
Tried and didn't work: remove sim, remove memory card, different battery, on charge, off charge.
Solution:1) Installed Philz kernel (found the kernel I require by looking at the stock rom code...mine was DDLSC) on my external SD. You can find this out by looking at the stock roms downloads on Dr. Ketan's page and finding out where you got your phone from in the first place (assuming it wasn't parallel imported).
2) Put the external SD back in, go into recovery mode (vol up+home+power), backup whatever I require (which in my case was a full backup).
3) Factory reset. (Mine did not delete the pictures, songs etc. It did delete all contacts, sms, call logs, applications, settings and updates).
Click to expand...
Click to collapse
Awesome man.. Glad to hear that