Related
Hello guys.
Official Gingerbread is finally available on Portugal.
I have currently Stock Froyo + Speedmod installed on my Galaxy S, so how can i update to Gingerbread?
Can i just update and Speedmod will still work?
Or should i install a stock kernel, then update, then install the Speedmod (Gingerbread version)?
Or i shouldn't update at all?
i'm interested in this too,i'm in the same situation (froyo+speedmod) and i'm quite a noob
is there someone who can patiently give us an hint about that? also about a good battery life gingerbread rom?
This is what I did.
1. Disable any lagfix - convert back to rfs (very important).
2. Back up all apps, contacts, data, photos etc from internal memory. Use something like Titanium backup or Mybackup pro.
3. Update through Kies for an official update.
4. Install latest Speedmod kernel for gingerbread (not Froyo version). Use odin.
5. Install superuser from clockwork mod recovery.
6. From recovery, do a factory data reset (make sure you have everything backed up first!)
7. Restore previously backed up apps, data etc, sync with google calendar.
8. Redo lagfix from recovery (convert to ext4).
Battery life at first seemed all over the place but has now settled down and is similar to Froyo/speedmod.
The phone is smoother and faster to use.
Thank you a lot!
That's exactly what i'm going to do!
thanks colin! 1 thing: i read somewhere that if you deleted some bloat app from operator (e.g. o2) you wont be able to update from kies anymore. is that true?
my phone it's not a locked one but anyway i think i always got o2 apps on it (which i unfortunately uninstalled instead of freezing it) and carrier-related updates.
am i going to have any kind of prob in the process?
skeletonboy said:
thanks colin! 1 thing: i read somewhere that if you deleted some bloat app from operator (e.g. o2) you wont be able to update from kies anymore. is that true?
my phone it's not a locked one but anyway i think i always got o2 apps on it (which i unfortunately uninstalled instead of freezing it) and carrier-related updates.
am i going to have any kind of prob in the process?
Click to expand...
Click to collapse
If Kies is showing that there is an update available then I think you should be ok.
If not then it is a case of flashing the whole firmware with odin. Open phone dialer and enter *#1234# and you will see the firmware details you are on now. It is worth making a note of these so you can reflash your current firmware if there is a problem.
okidoki i'll try that!
update:
PDA:I9000AOJP5
PHONE:I9000AOJP3
CSC:I9000VIAJP3
pretty old looks like o2 release. being my phone unlocked i never understood why i got o2 releases on it
so when i am not able to upgrade by kies i should reflash stock thru odin.
what parameter (pda/phone/csc) i have to look at to get the right firmware?
Everything is working better than ever, except for one little thing: The GPS.
Today i turned on GPS and tried to use my navigation software (CoPilot) and the GPS signal just didn't fix at all!
I ended by not using it, but i don't know why it doesn't work. It always worked wonderfully well before this update...
skeletonboy said:
okidoki i'll try that!
update:
PDA:I9000AOJP5
PHONE:I9000AOJP3
CSC:I9000VIAJP3
pretty old looks like o2 release. being my phone unlocked i never understood why i got o2 releases on it
so when i am not able to upgrade by kies i should reflash stock thru odin.
what parameter (pda/phone/csc) i have to look at to get the right firmware?
Click to expand...
Click to collapse
Still try kies first. If no luck there is a lot of info in this thread.
http://forum.xda-developers.com/showthread.php?t=723596
Make sure you can get into recovery mode first. Power button, volume up and home pressed all at once. Let go home button when Samsung logo appears.
ok thanks for the infos! i'll do it all when i can have a bit of relax,i am relocating so i need a working phone during these days
so i did it then!
flashed darky's resurrection 10.2 and then updated to doctorz rom jvt leaving ext4 enabled with no probs: another phone
just needs a good theme now..
Hi Seniors,
This became like a mystery for me..please help me to solve it.
Issue is like this if I install any custom or stock Gingerbread ROMS by phone works like a butter, no issue at all I can say.
But when I install any ICS or JellyBean ROM's it starts creating pain in my neck.
If I am using my phone it never restarts itself but when I lock my phone screen and keep it my pocket M finding that my phone is restarting into recovery mode itself.
Now here comes the strange part...If I play music using any music player and lock my screen it works fine,its not restarting itself ...but once I stop that music player and lock my handset screen in idle mode it goes to recovery in few secs
This only happens if I upgrade to ICS or JellyBean ROM's
One more issue...my wifi works fine If am having GingerBread install on my phone but when I install ICS/JB I cant even start it.
Have tried a lot to get it fixed....but
.....Even I want to taste ICS/JB Rom's like u guys...Please Help Your Rookie.
Thanks & Regards
D.J XactiX
Proud owner of Samsung Galaxy S i9000
----------------------------------------------------------------------------------------ANDROID ROCKS---------------------------------------------------------------------------------------------
Which ICS Rom did you try, and what guide did you use to follow?
The more detail you give the better we all can help you
EwOkie said:
Which ICS Rom did you try, and what guide did you use to follow?
The more detail you give the better we all can help you
Click to expand...
Click to collapse
Hey EwOkie,
Thanks for your courtesy mate...really appreciate it,
So here we go,
I had stock GB 2.3.6 ROM installed on my phone ;ie GT-I9000_XEU_I9000XXJW4_I9000OXAJW4_I9000XXJW4.zip,
after that I rooted my phone using CF-Root-XX_OXA_JW4-v4.4-CWM3RFS,
then I did factory reset,wipe cache and dalvik cashe and installed GamerzRom v11.0 which is a GB ROM,
so far no issue...wifi is working fine,phone is not at all giving me any auto restart issue...its was working like a charm,
then I found ICS_F4k_MOD_v4.0.4_I9000_r3.zip which is an ICS ROM,
I did factory reset,wipe cache and dalvik cache,the I installed ICS_F4k_MOD_v4.0.4_I9000_r3.zip using CWM Recovery console,
it was booted fine to home screen...later on I tried connecting my phone using my wifi router I found that WiFi was not switching on at all,
I locked my phone using lock button then after few secs I am finding my phone is restarting itself in recovery mode,
restarted my back to normal and again the same issue,
I ignored it,
Then I downloaded C-RoM Mix v7 Latest 4.2.1.zip in which had a wifi bug fix,
I did factory reset,wipe cache and dalvik cache,
I flashed it using clockworkmod recovery and had eactly that same issue which I had on ICS ROM,
for WIFI issue I tried flashing wififix.zip and found no resolution,
my phone went into boot loop of Samsung Logo,
then I flashed it back to original stock rom GB 2.3.6 and my phone started working like the way it should be.
This is the whole story
I moved from GB to ICS and then to JB.
Seriously brother I have no idea why its causing this weird issue...this is why I am looking for help from AndroidXperts on XDA site
Kindly help me to sort it out.
Thanks & Regards
D.J XactiX
Ok first up thanks for the info....
When doing a complete wipe before installing another rom make sure you wipe all 4 :
Data / Factory Reset
Cache Partition
Dalvik Cache
Battery Stats
Unless the Developer for the Rom States otherwise.
I know that there are a few ICS Roms that have a lot of bugs please check Info on them before Downloading
Should tell you whats working and whats notto save hassle
As I really only use GB Roms (my own preference)
Might help to try different Modems for your Romas this can help signal/network strength, where do you stay?
Yeah flashing back to 2.3.6 will work all the time as its basically stock.
No matter what Custom Rom I try I always flash JVU 2.3.6 then Root it > then the Custom Rom I want
I never just overwrite it with another Rom...
Hopefully someone with the same Rom as yourself may help as I dont want to give wrong info ....
Or Ask on the Rom site the issue your having with it
If you do need my help ... just ask
EwOkie said:
Ok first up thanks for the info....
When doing a complete wipe before installing another rom make sure you wipe all 4 :
Data / Factory Reset
Cache Partition
Dalvik Cache
Battery Stats
Unless the Developer for the Rom States otherwise.
I know that there are a few ICS Roms that have a lot of bugs please check Info on them before Downloading
Should tell you whats working and whats notto save hassle
As I really only use GB Roms (my own preference)
Might help to try different Modems for your Romas this can help signal/network strength, where do you stay?
Yeah flashing back to 2.3.6 will work all the time as its basically stock.
No matter what Custom Rom I try I always flash JVU 2.3.6 then Root it > then the Custom Rom I want
I never just overwrite it with another Rom...
Hopefully someone with the same Rom as yourself may help as I dont want to give wrong info ....
Or Ask on the Rom site the issue your having with it
If you do need my help ... just ask
Click to expand...
Click to collapse
Hi EwOkie,
Thanks for sharing your experience.
I am followed everything what u just mentioned in ur reply allready...but no go
Me & my GF we both have i9000 and I have followed same installation process on both the phones...her phones works like a charm but mine is like an incomplete soul.
One more thing mate,I really dont understand this ......can you tell me what difference it makes to have JVU 2.3.6 or some other version...how exactly its works....u know what I mean to say.
No idea why we use 2.3.6 JVU with CF Root (Kernel for Recovery) we just do ,, suppose its the best to start with before flashing a Custom Rom
So your partners phone works ok and yours doesnt.. did you try using the PIT File and re-partition?
Check my signature at bottom its a HOW TO Guide incase you get lost
As I says I dont have a lot of experience with ICS or JB Roms as the ones i flashed in the past werent as stable and had some bugs in them
Thats why i stuck with GB Roms
plz help me
today i install a custom rom lollipop in sony xperia c3 dual
but now my phone refused to start even same issue recovery mode... now my phone completely death.. when i try to start it red +green blink but fast mode work easily .. & when i connect my phone to charger it restart it self again & again ... its show only sony logo and its restart again ..plz help me
Hi to all,
I don't post here often, but this time I think that I really need your help and because of that, it will be an long post.
I read all treads before I do anything, but seems that I still don't get it good especially because it's a second time in a row that I got an software brick.
I own an international N7000 (volt group B) and it was more then 30 (thirty) times flashed in last seven months with a lot of custom kernels (mostly overclocked) and also with lot of different stock and custom ROM's, and there was no any major problem till I came back to stock TWR JB ROM.
I live in the Netherlands and I couldn't wait relaese of the Netherlands original stock JB ROM (but it also shouldn't matter, correct me if I'm wrong) and I flashed the first for Europe available JB ROM and that was an German stock JB ROM. Before of that I tested also Hong Kong JB ROM but I have removed it after a few days of testing.
This time I came from a CM 10.0 and NirvanaCore N6 and before everything, I wanted to get all right (even it wasn't necessary). I flashed back a rooted GB ROM from the tread of Dr. Ketan to be for shore that I have all good done. Then I have wiped from CWM cache partiton, than factory reset and then in advanced I wiped a dalvik cache.
Than I went to Mount and Storage and there I have formated: preload, system, data and cache. After that I cleand once again dalvik cache and then flashed with PC Odin 3.07 a stock JB German ROM.
And of course it was all perfect as always.
Then I have used a XXLSZ-OXA (fixed for bootloop)<< 07.03.2013 - PhilZ-cwm6 v4.87.6 with CWM 6.0.2.8 based recovery >> to obtain a root and that was it.
I restored all my 550 apps with Titanium BackUp too. Of course I used it for a few days to "settle it down" but I was dissapointed with it's performance.
I tried to flash a few scripts because I've read that there is no problem at all to flash "V6 supercharger" on N7000. I installed Busy Box Pro 1.20.02 and free script manager and applied "V6 supercharger" script from Script Manager to ROM but it didn't succsed 100% but 50% so there was something that I missed how to manage but the most of tweaks really already worked well and the performance and smoothnes of stock JB ROM came near to overclocked N6 with CM 10.0.
I flashed then also "Air View fix scripts" to preload and to system from CWM and I got it to work also in galery and by video preview. So I had relatively fully working TWR JB ROM with no lags and airview as it should be.
Than my baterry went low and I left it on Samsung AC charger to charge it.
I checked it few times in few hours if it charge, and the last time I checked it was after it reached about 92%. I went out and came back in two hours and I thought it schould be fully charged now.
But when I looked at it I saw that both touch buttons (home button and back button) were lited on, constantly, what it wasn't a good sign .
Of course a Note was stuck and with no response, dus the only way was to remove the battery to restart it.
Actually, it was a first time that my Note went fully off without any current and completely swiched off. Before that it was only few times restarted but not fully swiched off.
Next time when I put battery back Note could not start up any more. That was a first soft-brick in my life. :cyclops:
I didn't ordered a USB JIG but I send it to Samsung Repair Centar and they just reflashed it in meanwhile with a new Netherlads LSZ JB ROM and they send it back to me, even all my files was still there on the main phone memory togheter with philz rooted kernel and all other rooted kernels and scripts.
But again it wasn't much better and with the same poor performaces, so again I decided to root it, but now it was already new XXLSZ-OXA (fixed for bootloop) << 13.03.2013 - PhilZ-cwm6 v4.88.2 with CWM 6.0.2.9 based recovery >> kernel and I just flashed it when I saw that the new kernel was already up there (<< 17.03.2013 - PhilZ-cwm6 v4.89.4 with CWM 6.0.2.9 based recovery >>) I have download it but I didn't have time to flash it.
I made a nandroid back up (and a holo backup too) and again decided to try to speed it up a little bit, but now with a few other scripts.
This time I didn't flash "Air View fix" scripts and I choose also not to flash "V6 Supercharger" but for "4cyl_Turbo_engine_150_shot_v0.2.3" and " CrossBreeder -3.15.13-Entropy Lag Reduce/DNS Speedup/Tether boost/Clean Adblock" script and again it gain in speed. Also I restored about 550 apps on my 64Gb microSd with Titanium BackUp.
Everything was fine untill the battery went down.
Before it reached 1% I ordered to android to swich off the device and it went fully good.
When I tried to charge it with a USB cable via USB 3.0 port it didn't started. Then I tried to charge it with an original Note AC charger but the result was the same. So it seems to be again soft-bricked.
Last friday I took a phone to a local Samsung Repair center and I said to them that I have faild with Software update. They said that I don't have to worry about it, because there is newest software update on the Samsung server which is just released, but I have to wait for about an hour to be downloaded and it's an update which is still not available via KIES but only for Samsung stuff.
So I beleved him and I sat down to wait and the guy came after a 45 minuts to tell me that he doesn't know what is going on, because the phone can't be recognised and asked me if I want to send it immediatly to main Samsung Service, but because I already ordered a USB JIG I wanted to try it before I send it to them to reflash it again.
The battery was complitely empty so I found a place where I can fully charge it and when I came at home I tried the USB JIG revival methode to get it in Download mode but it also faild.
Someone offered to me for 25 euros to reflash it with RIFF JTAG Box but I'll send it first to Samsung to see what they will do.
Now I ask all wise and experienced users and developers to tell me where it went wrong ?
1) Is that Philz kernel and which kernel should I precisaly choose next time for the Netherlands LSZ JB ROM or should I try SpeedMod N7000 Jelly Bean [K5-2 CWM CIFS ROOT / NO-ROOT] kernel ?
2) Are the scripts responsable for bricks, which maybe interfere with wrong partitions or somthing like that ?
3) Or is it AirView Fix script (In the first brick) ?
It's also remarkable that after powering phone down it won't boot anymore, in both cases.
Edit: I just reed this tread here: http://forum.xda-developers.com/showthread.php?p=39683593#post39683593 , from the user EvaWorld about application called "Swapper2" which i forgot to mention, but I had installed with both LSZ stock ROMS.
Now I'm even more confused...
What do you guys think about "V6 Supercharger" and about the newest " 4cyl Turbo engine v0.2.9_r1 w/ 200 shot NOS | Stable" mods, and what about " CrossBreeder -3.15.13-Entropy Lag Reduce/DNS Speedup/Tether boost/Clean Adblock" mod?
It's all about TWR and I ask all this because there are people which want to stick with a stock TWR JB ROM and maybe it can help to them too...
If you still read this, thanks for your patience and I hope to see your reactions and to read your answers soon...
Thanks in advance.
Edit: The phone is back and repaired. The mainboard is changed and there is no more EMMC chip in there.
Still there is a question what caused the brick ? Was that Swapper2 or een van the scripts which I have used ?
Is there someone who has any idea about it ?
I use now Rocket ROM reloaded and is quite fast and stable.
Greetings to all !
Solved
Solved by Samsung
I don't read it untill the end.
Sent from my GT-N7000 using Tapatalk HD
O.K.
zai89 said:
I don't read it untill the end.
Sent from my GT-N7000 using Tapatalk HD
Click to expand...
Click to collapse
Who did it, what do you think ? Neither do I, but at least there hes been some movements... :good:
Cheers !
Hi,
I own a Galaxy Note GT-N7000.
I never rooted it, just used two official updates provided by Samsung and then flashed the original 4.1.2 using Odin.
I have rooted my older Android phones (San Francisco) and used to try all kinds of ROM's on many Windows Mobile phones - I am not a exactly a noob, I just did not mess with my Note, because I am happy with it just like it is and because it is my work phone, which needs to be 100% working.
However, battery life is getting shorter (so I just ordered a new original Samsung battery) and, worse, the phone is getting more and more unresponsive.
This is the real problem: whenever I want to do something, it takes like 1-2 seconds, if not longer, before the phone reacts. This is very annoying. I don't have that many apps installed (I just stick with my preferred ones, instead of betting on sheer quantity). Still, the other day, the phone complained that there is no free space to install upgrades of some apps.
To make it short: how can I install a clean original 4.1.2 as if my phone was just purchased, i.e. with a clean flash?
Before you flame me and tell me I should spend the next month reading the forum: I already did!
I am afraid of the brick bug, so I guess that doing a wipe of the flash is not an option, as i guess that the bug has not been fixed by Samsung on 4.1.2. On the other hand, I do not want to root my phone, to install some custom kernel, to then wipe the flash and revert to the official ROM, risking to activate the counter, etc. Not that I don't know my way around flashing, soldering, building the flash dongle or even JTAG - I just don't have the time and nerve.
So my simple question: How do I securely wipe the flash and install a clean official 4.1.2 ROM on my phone, getting rind of 2 years of garbage files and God knows what else is slowing down my phone.
Many thanks for those guiding my way - I don't want to believe that there is a planned obsolescence in course, like Samsung building a timer that makes the phone get slower and slower...
Cheers,
vma
If you really want to enjoy the speed of your phone, IMO, you should go ahead and try CM /AOSP roms. They will give you some time out of the "slowness".
Just saying. On the other had if you want to be on the stock TW 4.1.2 rom, then doing a factory reset from the recovery will do the job. JB kernels for 4.1.2 seems to be safe to do a reset as there has not been cases of bricking on stock JB kernel.
But what my method would be to...
1. Install Philz kernel for JB using recovery and boot into recovery again... to get CWM recovery this time
2. Choose wipe data/factory reset ----> Clean for new rom install. (this will delete the current rom, data and cache)
3. Mounts and Storage -> Format Internal storage.
4. Mount USB storage and connect to PC... delete all files
5. Go to advanced menu and choose reboot download.
6. connect to PC and flash stock rom JB using odin,
Thanks for your reply.
However, you say:
nokiamodeln91 said:
On the other had if you want to be on the stock TW 4.1.2 rom, then doing a factory reset from the recovery will do the job. JB kernels for 4.1.2 seems to be safe to do a reset as there has not been cases of bricking on stock JB kernel.
Click to expand...
Click to collapse
While in another post it says:
"Warning :
Don't wipe anything from stock ICS recovery
Don't factory reset/Hard reset on stock ICS.
Don't flash any Wipe version of ICS ROM"
(http://forum.xda-developers.com/showthread.php?t=1424997)
This is what I don't get... Is it safe or not? Does this warning only apply to ICS, while JB is safe?
Cheers,
vma
Its applies only to ICS stock kernels. There is no evidence to prove that JB is safe. but Samsung seems to have suppressed the bug on JB kernels.
nokiamodeln91 said:
Its applies only to ICS stock kernels. There is no evidence to prove that JB is safe. but Samsung seems to have suppressed the bug on JB kernels.
Click to expand...
Click to collapse
Thank you for your kind help!
I will probably work on my Note this weekend.
Cheers,
vma
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