Related
I have a Bell SGS, GT-I9000m. I'm considering installing hardcore kernel only, i.e. no custom ROM. If later I want to revert to the stock kernel, how would I do that?
Thanks for your help.
Sent from my GT-I9000M using XDA App
I'm not quite sure if it is possible with the stock-kernel but if you can make a full backup (like with CWM) you could restore it later. But why do you want to get back to stock-kernel?
If the backup-possibility does not work you have to find the stock-kernel for downloading and flash it via Odin or you have to flash the whole stock-ROM with Odin.
Thanks for your answer. I can't make a Nandroid backup while I'm on stock (because I can't install CWM recovery because I'm on 3e stock recovery, not 2e)
I'm not sure why I would want to go back to stock... Maybe something goes terribly wrong? I guess I just wanted to know if it was possible.
Last question: when you say I would have to find the stock kernel, is that just Google, or are there sites/repositories out there for this sort of thing?
Sent from my GT-I9000M using XDA App
I should add, the site/repo question is for kernels and stock ROMs...
Thanks.
Sent from my GT-I9000M using XDA App
site1ca said:
I'm not sure why I would want to go back to stock... Maybe something goes terribly wrong?
Click to expand...
Click to collapse
Well, then just flash the whole stock-ROM and flash it (look at samnfirmware.com for firmwares).
site1ca said:
Last question: when you say I would have to find the stock kernel, is that just Google, or are there sites/repositories out there for this sort of thing?
Click to expand...
Click to collapse
Don't know if you'll find it anywhere cause nobody needs it.
Possible scenario
Alright, thanks for your help. I guess the one scenario that is bothering me is as follows:
1) Bell - FINALLY - releases their official Gingerbread update.
2) I've installed Hardcore kernel, which according to - http://forum.xda-developers.com/showthread.php?t=822756 - "works on all 2.2 and 2.2.1 ROMs".
3) Would I be able to install the Bell Gingerbread update with Hardcore kernel?
This is why I keep asking how I would revert from Hardcore because I obviously don't want to lock myself out of Bell updates forever.
It doesn't matter which kernel you are using when you are flashing with Odin. And Bell releases the updates later than Samsung, so you'd have the advantage of getting updates earlier with a 'free' firmware.
One solution to flash back the stock kernel is to extract the zImage (the kernel) from the stock rom and flash that with Odin or Heimdall.
But as far as I know having a custom kernel would not cause problems with installing a stock upgrade.
Done
I've installed Hardcore's kernel. Everything seems to be working fine, phone started up and picked up service.
I booted into recovery, enabled lagfix, turned on all of the recommended tweaks and then ran the Quadrant Standard. Things seem a bit faster, so I guess it's all good.
Next step, Darky's 10.1.
Thanks for your help, everyone.
One more question:
I did a Nandroid backup of everything (so data, dbdata, cache AND system). The restore option says "Be careful!". What's up with that? I mean, what's the caveat?
Thanks.
I've already made some NANDROID-backups, but never seen 'Be careful!'.
If the backup was succesful I wouldn't care about that.
*sigh*, I hate to keep adding questions on to this thread, but I must.
After installing the hardcore kernel and enabling tweaks and lagfix, I'm running into exactly this problem: http://forum.xda-developers.com/showthread.php?t=851970
My phone was extremely hot for a while, then I got a warning indicating that my internal phone storage was running low, etc.
Eventually, I found this file (/data/local/tsprsp) to be the culprit. I deleted it and rebooted and now my phone is fine. However, vibration just doesn't work at all!
Any ideas? Has anyone else run into this problem?
I was told that if you do a 'full' backup, in some cases restoration will fail with some error. But it depends on the version of the ROM you are using.
That is the reason why it is recommended to backup only data and if you want to restore, then first reflash your rom, then restore the data.
Thanks, zsori. That explains the "Be careful!".
Sent from my GT-I9000M using XDA App
After trying MIUI, a stock ROM will never touch my SGS again.
meresis said:
After trying MIUI, a stock ROM will never touch my SGS again.
Click to expand...
Click to collapse
you will have to flash back a stock rom via odin if anything wrong happen during the flashing of custom roms, although chances are low if you follow the instructions carefully.
good luck and have fun flashing custom roms!
Which Gingerbread?
So I'm continuing my quest to learn more about all of this custom ROM flashing stuff. And I wanted to get gingerbread on my phone... So I figured I'd just get an image from samfirmware.com and flash it. But then, I went here (because I was also interested in Darky's 10.1 so I was reading their guide): http://www.darkyrom.com/community/i...-darkyrom-gingerbread-jvh-noob-friendly.3080/
It says that flashing "Ficeto_JVH_I9000_Odin" will get me a stock Gingerbread. My question: what's the difference between flashing an image from samfirmware.com or flashing "Ficeto_JVH_I9000_Odin"? How do I know which to pick?
In all my browsing/reading, I realize that there are 3 "separate" parts: kernel, modem and then the "ROM". Ideally, I want to keep my modem as is... What does that correspond to in Odin? I've tried to find what "PIT", "PDA", "PHONE" and "CSC" represent in Odin, but I'm not sure I got it right. PIT = Kernel? PHONE = modem?
And finally, how do I know if a particular kernel is compatible with a particular ROM?
Sorry, I know there are lots of questions there. But please help clearing up a n00b's confusion. Thanks.
site1ca said:
So I'm continuing my quest to learn more about all of this custom ROM flashing stuff. And I wanted to get gingerbread on my phone... So I figured I'd just get an image from samfirmware.com and flash it. But then, I went here (because I was also interested in Darky's 10.1 so I was reading their guide): http://www.darkyrom.com/community/i...-darkyrom-gingerbread-jvh-noob-friendly.3080/
It says that flashing "Ficeto_JVH_I9000_Odin" will get me a stock Gingerbread. My question: what's the difference between flashing an image from samfirmware.com or flashing "Ficeto_JVH_I9000_Odin"? How do I know which to pick?
In all my browsing/reading, I realize that there are 3 "separate" parts: kernel, modem and then the "ROM". Ideally, I want to keep my modem as is... What does that correspond to in Odin? I've tried to find what "PIT", "PDA", "PHONE" and "CSC" represent in Odin, but I'm not sure I got it right. PIT = Kernel? PHONE = modem?
And finally, how do I know if a particular kernel is compatible with a particular ROM?
Sorry, I know there are lots of questions there. But please help clearing up a n00b's confusion. Thanks.
Click to expand...
Click to collapse
you got it wrong.
PIT is for mapping the partitioning of the phone. In most cases you should only use 512 pit file. and only use it when you want to wipe the phone.
the three parts is "pda" (which is the rom), "phone" (which is the modem), and "csc" (which is the carrier customization and apns)
the kernel is in the part of pda (the rom)
check the thread in xda of the kernel to see if its a gingerbread kernel or froyo kernel.
hope this clear things up
Yes, that helps. That's really good to know. So now, in Darky's guide to flashing Flash Ficeto_JVH_Odin, I see that only PIT and PDA are specified. This is reassuring, knowing that the modem and carrier stuff isn't touched.
Many thanks.
There are firmwares with three parts (Phone, PDA, CSC, including bootloader) and with only one part (PDA, no bootloader(?)). The one-part-FW is just an 'update', the one with three parts an 'upgrade'.
Hello,
first a brief intro...i am not an android developer but I am a user and I love the OS.
However i have had a little trouble with the small issue of backing up stock ROM so that i can have the freedom to tinker with any custom ROM possible knowing that i can always fall back to my stock ROM if I don't like anything or something doesn't work.
I have the original ROM so i can flash it back whenever but not everyone has access to their stock ROM. so you must make a choice that once you flash a custom ROM, you cant go back.
So i am calling out to all the nice developers in the house...
1. Is this possible. is there a way one can do a backup of the stock ROM in the galaxy mini?
2. If its not possible at the moment, is there anyone willing to work towards ensuring its possible?
Like I said, I am not a developer but i could help in any little way i can to work with any willing developer towards achieving this.
Thanks.
yess is possible to backup your rom juste install ROM MANAGER and clic on backup is simple you can find it on android marcket ^^
I would not personally suggest Rom Manager since there are a lot of cases here that it bricked the phone. It is possible to backup your stock rom with cwm recovery. The problem is it can't be restored via the same recovery. This is a limitation of cwm. So Odin is still the best option to restore stock roms.. I do hope that restoring stock roms can be made possible thru cwm..
Sent from my GT-S5570 using XDA App
spawk said:
yess is possible to backup your rom juste install ROM MANAGER and clic on backup is simple you can find it on android marcket ^^
Click to expand...
Click to collapse
I have tried ROM manager and it doesnt even recognize the cmw recovery already installed. it requests to install a custom recovery and the SGM isnt listed among the supported devises so that wount work.
kitrax59 said:
I would not personally suggest Rom Manager since there are a lot of cases here that it bricked the phone. It is possible to backup your stock rom with cwm recovery. The problem is it can't be restored via the same recovery. This is a limitation of cwm. So Odin is still the best option to restore stock roms.. I do hope that restoring stock roms can be made possible thru cwm..
Sent from my GT-S5570 using XDA App
Click to expand...
Click to collapse
Have you actually backed up your stock rom using cwm?I have tried and each time i get an error that it couldnt mount the /system. And am seeking assistance to develop a means to back up and restore Stock ROMs in SGM.
with custom kernel with suport ext4 and convert rfs partition to ext4 partition you can backup your stock rom.
only need flash custom kernel. after that you can backup the rom.
galaxy S user have CF-root kernel for each rom. CF-root do this and root your phone and install CWR.
but for mini no any CF-root kernel
.i have changed my CWM by another one find here with godell thread I use "CWM5028.zip"
Dude, don't you try Rom Manager, it may brick your phone. CWM can't make stock rom backups as far as I know.
Enviado desde mi GT-S5570 usando Tapatalk
spawk said:
.i have changed my CWM by another one find here with godell thread I use "CWM5028.zip"
Click to expand...
Click to collapse
Yea...tried that still wont back up stock rom...
to make the backup of stock rom recovery is needed to be modded for work on bml partition layout it should also be compatible with rfs partitions
dhlalit11 said:
to make the backup of stock rom recovery is needed to be modded for work on bml partition layout it should also be compatible with rfs partitions
Click to expand...
Click to collapse
Has this been done by any one? or can you do it and then avail a working solution?
no am a member like you but squad can do this
dhlalit11 said:
no am a member like you but squad can do this
Click to expand...
Click to collapse
well squad gets alot of request and am sure he would hav done it by now because he has made several recoveries...but i will def ask him. it would b nice to have smeone else tho workin on it to take the pressure off the main developers.am doin a bit of research myself but havent made much headway:-(
Sent from my GT-S5570 using xda premium
Hi, I have an international varient of the Galaxy Note GT N7000 which using Chainfire's Got Brick App v1.1 says:
eMMC Chip
Type: VYL00M
Revision: 0x19
Verdict: Danger! This eMMC chip is "Known" to have the brick bug!
I once had installed a custom Kingdroid ROM v3 and wiped it but it had resulted in a Hardbrick/Superbrick so i had to take it Samsung Service Center to get it fixed. They have repaired it and given me back the handset with the Stock ICS ROM. Here are the details:
Model Number: GT-N7000
Android Version: 4.0.3
Baseband Version: N7000XXLPT
Kernel Version: 3.0.15-N7000JPLPD-CL643396
[email protected]#3
SMP PREEMPT Thu May 31...
Build Number: IM74K.JPLPD
Now i have done some researched and found that this bug is only triggered with kernels (ICS stock & leaked) which have the eMMC_Erase function/command. GB kernels are not known to have this erase function so they are safe.. Also the two safe kernels are franco r3 and speedmod k3 (Correct me if im wrong). Can anyone please guide me on the following:
1) Should I flash Stock Gingerbread OR ICS Kernel(franco/speedmod)?
2) Should I use Recover or ODIN?
3) Plz Provide the links for the Kernels - Franco R3 & Speedmod K3 which are safe?
4) Will the above Kernels provide root access?
5) Is abyss kernel safe (because it supports GPU overclock)?
6) Can i flash an ICS kernel over a Gingerbread ROM?
For answering please answer in a similar numbered way so that it is easy to read and understand for me as well as future audience! Thanking everyone who takes time to read and answer!
I use Speedmod kernel and i confirm that it is safe (for me at least anyway) Im using CleaNote ICS ROM, So I would suggest you also use speedmod kernel,
You Flash it in Odin, It will give you CWM and Root too !
Ive attached the kernel to the post for you.
Abyss kernel is safe, But its for GB ROMs only, You are on ICS so it wont work.
I dont know if you can flash ICS kernel over GB ROM, However, Your are on ICS so you shouldnt need to worry about that.
don't really want to hijack your thread an i dont really want to make a whole new thread for a simple question.
as a noob, im just wanting to know, if i update my stock gb to stock ics via software update, are there still chances of this emmc bug/brick thats going on?
and the battery drain issues, do they only exist in custom roms or does it exist in stock roms too?
cheers.
azzledazzle said:
I use Speedmod kernel and i confirm that it is safe (for me at least anyway) Im using CleaNote ICS ROM, So I would suggest you also use speedmod kernel,
Click to expand...
Click to collapse
Thanks for the confirmation mate, one more thing to ask you: Is the speedmod kernel faster than the stock ICS kernel? Is there any flaws such as battery drain/WIFI problem with it? Also does it support GPU OC? Thanks once again for your help!
little-vince said:
don't really want to hijack your thread an i dont really want to make a whole new thread for a simple question.
as a noob, im just wanting to know, if i update my stock gb to stock ics via software update, are there still chances of this emmc bug/brick thats going on?
and the battery drain issues, do they only exist in custom roms or does it exist in stock roms too?
cheers.
Click to expand...
Click to collapse
Firstly get your Galaxy Note checked using Chainfires App (Gotbrick v1.1). If the verdict says "Danger" only then does your device have this problem. My Galaxy Note (Rev 0x19) had this problem and came with GB out of the box and i upgraded it to ICS through Samsung Kies and it worked fine. So i do not think that while updating to ICS via Kies will cause this problem. As of what i know it is triggered when a command eMMC errase is triggered when either doing a factory reset or wipe through recovery. The update as such did not brick my device, however this does not mean it cannot brick yours. I am no expert on this so be a little cautious while updating. I would suggest stick to GB until Samsung Releases a safe stock ICS ROM with a safe Kernel. Cheers!
really easy
1: (optional ) in GB do factory reset (after you have made a backup with TB)
2: put phone in Download mode.
3: use PC odin flash STOCK ICS rom
4: reboot device let it load
5: put device back into download mode
6: use PC ODIN flash Speedmod k3-3
7: reboot
8: launch CWM and tell it to reboot in cwm recovery
9: load your custom rom of your choice
i HIGHLY recommend doing ONLY THE FACTORY RESET WIPE data and cache in GB before you start anything.
ONCE you are in ICS and have successfully loaded speedmod or franco's kernel then it is safe to do a factory wipe if you want. but ONLY after one of those 2 Kernels are on your device.
EMMC BUG. is affected in all N7000 Devices only . only the devices sent to the USA have the revision the non 0x19 bug .
rp4k said:
EMMC BUG. is affected in all N7000 Devices only . only the devices sent to the USA have the revision the non 0x19 bug .
Click to expand...
Click to collapse
okay...
truth is i haven't actually bought the note yet.
just doing substantial amounts of research beforehand.
im pretty sure only the n7000 model is out in australia.
but it's all okay if i dont factory reset/wipe/anything-risky-in-general right?
little-vince said:
okay...
truth is i haven't actually bought the note yet.
just doing substantial amounts of research beforehand.
im pretty sure only the n7000 model is out in australia.
but it's all okay if i dont factory reset/wipe/anything-risky-in-general right?
Click to expand...
Click to collapse
Yes, this bug is known to trigger usually when you do a wipe using the recovery. However there have been some cases when doing a factory reset via the settings has also resulted in a brick. However if you stay away from recovery and do not intend to doing flashing/wipes then i guess you should be ok. And it is a matter of time before Samsung Comes up with a solution. They are said to be working on this bug already. I have the N7000 which i bricked once while flashing and then wiping but i got it repaired since i had warranty. Since then i have stayed away from wiping or installing any custom roms so the device has not given any problems. Hope this info helps! Cheers!
Rom doesnt load during boot
Dear Developers
I rooted my galaxy note and soon as that i got gained super user access for chain fire app, then i flashed CWM and installed crisello rom with abbysys kernel , it installed all the files correctly and soon after that the phone rebooted .After reboot the phone went inside the boot menu ( the world of galaxy UI boot menu ) and it frozen since then
i tired flashing various custom or stock roms and still the same problem i face
If someone could help me out on what the problem is and how i could get a fix to it
cuteglen said:
Dear Developers
I rooted my galaxy note and soon as that i got gained super user access for chain fire app, then i flashed CWM and installed crisello rom with abbysys kernel , it installed all the files correctly and soon after that the phone rebooted .After reboot the phone went inside the boot menu ( the world of galaxy UI boot menu ) and it frozen since then
i tired flashing various custom or stock roms and still the same problem i face
If someone could help me out on what the problem is and how i could get a fix to it
Click to expand...
Click to collapse
What rom are you on? Have you performed any wipes or factory resets?
Sent from my GT-N7000 using xda premium
Hi everybody
I have three questions if You can help me
1- Are speedmode and franco Kernels the only safe kernels for stock ICS?
2- Can I flash CM9 from stock ICS or it is safer to do it from GB rom?
3- Can I flash CM9 kernel for stock rom?
Thanx in advance
iraqi4ever80 said:
Hi everybody
I have three questions if You can help me
1- Are speedmode and franco Kernels the only safe kernels for stock ICS?
2- Can I flash CM9 from stock ICS or it is safer to do it from GB rom?
3- Can I flash CM9 kernel for stock rom?
Thanx in advance
Click to expand...
Click to collapse
1. Afaik yes
2. NO, you'll brick, flash from GB kernel, I know some have done from abyss.
3. No. CM based not compatible with Touchwiz framework.
Sent from my GT-N7000 using xda premium
I have a quick ( hopefully) question about the brick bug. I already asked but I think a mod must have deleted the whole thread, even though the thread was about the brick bug and I think I might have been bringing a new way ( well for some anyway) to flash safely to new ROMs.
So anyway, I have a 'safe' kernel ( speedmod), and I want to try out 4.0.4 stock ROM. I have extracted the stock ROM zip and the tar file inside. In there is the Zimage.
Do I just delete the Zimage then re-zip and flash from CWM?
OR Do I have to replace the Zimage with another, 'safe', Zimage ( for example just put the zimage in there from speedmod because I want to keep that for now). Does there NEED to be A Zimage there, or will it work fine without one. I don't want to start flashing the ROM and it get stuck half way through.
If it will work this way then this might be a fairly easy way for anybody to flash any new ROM they want. They'll just need to get a safe kernel on there in the first place.
SpyderTracks said:
1. Afaik yes
2. NO, you'll brick, flash from GB kernel, I know some have done from abyss.
3. No. CM based not compatible with Touchwiz framework.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
thank you for your response
just to be sure you said that it is unsafe to flash CM9 from stock ICS?
can we flash CM9 from stock ICS rom with safe kernel such as franco or speedmod
sorry for bothering you and thank you again
iraqi4ever80 said:
thank you for your response
just to be sure you said that it is unsafe to flash CM9 from stock ICS?
can we flash CM9 from stock ICS rom with safe kernel such as franco or speedmod
sorry for bothering you and thank you again
Click to expand...
Click to collapse
Only from GB kernel such as abyss. If you flash from ics kernel you WILL brick. This goes for all cm based roms.
Sent from my GT-N7000 using xda premium
kyllerbuzcut said:
I have a quick ( hopefully) question about the brick bug. I already asked but I think a mod must have deleted the whole thread, even though the thread was about the brick bug and I think I might have been bringing a new way ( well for some anyway) to flash safely to new ROMs.
So anyway, I have a 'safe' kernel ( speedmod), and I want to try out 4.0.4 stock ROM. I have extracted the stock ROM zip and the tar file inside. In there is the Zimage.
Do I just delete the Zimage then re-zip and flash from CWM?
OR Do I have to replace the Zimage with another, 'safe', Zimage ( for example just put the zimage in there from speedmod because I want to keep that for now). Does there NEED to be A Zimage there, or will it work fine without one. I don't want to start flashing the ROM and it get stuck half way through.
If it will work this way then this might be a fairly easy way for anybody to flash any new ROM they want. They'll just need to get a safe kernel on there in the first place.
Click to expand...
Click to collapse
Hiya, yep, you can just delete the zimage file, no need to replace, it will just skip writing that partition.
Sent from my GT-N7000 using xda premium
Gave that a go last night and I must not be doing something right. Either I need to re-zip it differently or I need to use something other than CWM (mobile odin?) because it's just aborting before it actually starts flashing anything.
Suppose I could always flash the separate elements on pc odin?
kyllerbuzcut said:
Gave that a go last night and I must not be doing something right. Either I need to re-zip it differently or I need to use something other than CWM (mobile odin?) because it's just aborting before it actually starts flashing anything.
Suppose I could always flash the separate elements on pc odin?
Click to expand...
Click to collapse
Try mobile odin. If you point to the tar, it should load all the components. You can then review which components are being flashed.
Sent from my GT-N7000 using xda premium
iraqi4ever80 said:
Hi everybody
I have three questions if You can help me
1- Are speedmode and franco Kernels the only safe kernels for stock ICS?
2- Can I flash CM9 from stock ICS or it is safer to do it from GB rom?
3- Can I flash CM9 kernel for stock rom?
Thanx in advance
Click to expand...
Click to collapse
1. Add goku, dafuq, gl-notecore and abyss42 (GB) to your list.
2. Only do it from a GB firmware or at least a GB kernel like abyss42. SPECIFIC instructions per firmware is listed for a reason. Follow those instructions to the letter.
3. No.
Sent from my GT-N7000 using xda app-developers app
kyllerbuzcut said:
Gave that a go last night and I must not be doing something right. Either I need to re-zip it differently or I need to use something other than CWM (mobile odin?) because it's just aborting before it actually starts flashing anything.
Suppose I could always flash the separate elements on pc odin?
Click to expand...
Click to collapse
Stock rom in a zip? Are you sure you are nit flashing a custom rom? Point us to the file/thread please.
If it is a custom rom, the it is meant to be via CWM.
1. Flash abyss42
2. Reboot recovery
3. Do your wipes
4. Flash.
Im sure there is a specific instruction on where you got that file. Or better yet, go to dr. Ketans thread and get your stock rom from there.
Sent from my GT-N7000 using xda app-developers app
It's just the standard rom file from sammobile.It does come as a zip you know. If you unzip it, then use rar on it you can see all the bits. I thought if I just put a different zimage in there it would just go ahead and use that, but didn't seem to like it after I zipped it all back up again.
Tonight I've ended up getting chainfires excellent CF-Root kernel.Flashed that through odin, over my speedmod kernel.
Put just the factoryfs part of the stock rom zip onto the SD card and flashed that using the cwm app that CF-Root installs for you.. Now have CF-Root kernel and 4.0.4 firmware.
If you don't already have a "safe" kernel then I dunno what the brick chances would be, but since I had a safe one already I thought it couldn't hurt to try it out.
The reason I haven't flashed the hidden, cache, model and sbl parts of the zip is that simply they wouldn't fit on my SD card If it behaves funny or I can make space then I'll try the rest too. And the reason I didn't flash the zimage from the zip should be fairly obvious. Because I don't want a brick
EDIT: I managed to clear some space on the SD and flashed the rest of it. Seems to be working ok, so far anyway. I'm hoping the battery issues from 4.0.3 will be a little better. This is a really good way of doing it all as you can just swap out a potentially bad kernel for one that has been 'protected' by having te emmc cap erase turned off.
I'd like to start playing around with ROM's for my SGN but I'd like to know if there is a way to make a backup of my current Gingerbread 2.3.6 Stock ROM.
Maybe with PC Odin? Can I dump my current ROM to a flashable file to be able to go back to stock Gingerbread whenever I want?
I'd really appreciate your help. Thank you.
Its called a nandroid
get yourself CWM recovery and then boot into it, Go to back up and job done, It will create a nandroid.
Now all you have to do is boot back into recovery and restore it when you want !
Thank you azzledazzle. I'm very familiar with CWM and Nandroid backups I was thinking that maybe there was another way. Does the Nandroid backups also backup the kernel? or would I have to downgrade to stock GB kernel first if I want to downgrade from ICS?
I do believe it backs up the kernel too, However i wouldnt recommend restoring a GB nandroid from a ICS ROM, I would suggest to flash GB in ODIN, then restore nandroid.
Flashing with odin only takes 5 mins
It might work, restoring from ICS to GB via nandroid, But i havent seen any confirmation on this, and what with the bricking risks and all that, Its better to be safe than sorry !
Thank you again. That makes sense.
One last question... maybe if you don't know someone else might:
Are all Gingerbread kernels the same, I mean are all 2.3.6 kernels the same for all Galaxy Note Stock ROM's regardless of CSC? Or is there a possibility that my current GB 2.3.6 ROM is not "compatible" with one of the existing GB 2.3.6 kernels (in case there is more than one)?
For instance if I go back to my firmware with CSC TTT and install a kernel for say CSC XME, will that work? and which CSC will my phone end up with, TTT or XME?
Thanks again for your help. Much appreciated.
Hi Guys,
I wondered if any of you (more experienced, long serving) users are aware of any Gingerbread ROMs? Preferably a CM or any 2.3.7 based, but if they don't exist, any build will do... It needs to be a safe build, a non eMMC bug version, or DeOxed (is that the term)?
Sure, you're gonna say, why bother.. There's JB and KK now, but I like GB and wanted to see what it's like on the N7000?
All help gratefully welcomed..
Thanks, Lister
all GB kernels are safe to wipe data (only stock ICS kernel is unsafe)
i advise you to try Checkrom HD v6, still my favorite GB rom
Sent from my GT-N7000 using xda premium
Hi @ASMI1,
Thanks for such a fast reply.. I've been to the main website where I can download it.. One thing I'm worried about, I've seen in this ROM and mentioned in another GB based ROM for our phones is: CSC?
the CheckRom v6 features "Multi CSC" what does this mean, and is it dangerous?
Do I flash Philz Kernel, and install with that? Do I need to flash another kernel afterwards? Does this room raise the counter or anything?
I'm OK flashing JB or KK, but not done a GB ROM and worried in case summit not aware of, don't want to brick this...?
Thanks, Lister
ASMI1 said:
all GB kernels are safe to wipe data (only stock ICS kernel is unsafe)
i advise you to try Checkrom HD v6, still my favorite GB rom
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
CSC means customer service code. Multi csc means that this rom is not locked to any country or carrier.
Yes you can flag it under philz kernel.
Sent from my LG-E410
Hi @kaborayyan / @ASMI1 / Guys,
I've flashed Philz original Recovery/Kernel first, and then do all the usual wipes... Factory Reset, System, Davlik Cache (and even tried Pre-Load? after first failed) and same result each time.
During the flashing process it seems to backup the EFS (even though that was the first thing I did when I got this phone, so hope it hasnt over written my original EFS backup) but then gets stuck. It seems to stay on Flashing Modem for ages, and progress bar doesnt move... And then the phone goes black, and it reboots... But then gets stuck on the white Samsung splash screen "Samsung Galaxy Note - GT-N7000" and stays like that, unless I reboot....
I reboot, but notice CWM 5.0.2.7 is installed (not sure if thats a safe one?) so I flash Philz from within that, reboot recovery and then do all the wipes again... and the phone seems like normal again. However I dont know if I've done anything wrong, or if the phone is still safe or if I've killed it any way??? lol
Cheers for any help/support.
Thanks, Lister
Lister Of Smeg said:
Hi @kaborayyan / @ASMI1 / Guys,
I've flashed Philz original Recovery/Kernel first, and then do all the usual wipes... Factory Reset, System, Davlik Cache (and even tried Pre-Load? after first failed) and same result each time.
During the flashing process it seems to backup the EFS (even though that was the first thing I did when I got this phone, so hope it hasnt over written my original EFS backup) but then gets stuck. It seems to stay on Flashing Modem for ages, and progress bar doesnt move... And then the phone goes black, and it reboots... But then gets stuck on the white Samsung splash screen "Samsung Galaxy Note - GT-N7000" and stays like that, unless I reboot....
I reboot, but notice CWM 5.0.2.7 is installed (not sure if thats a safe one?) so I flash Philz from within that, reboot recovery and then do all the wipes again... and the phone seems like normal again. However I dont know if I've done anything wrong, or if the phone is still safe or if I've killed it any way??? lol
Cheers for any help/support.
Thanks, Lister
Click to expand...
Click to collapse
Reboot into recovery again if you found the touch colored recovery then you're on philz kernel. If not be sure that you selected the suitable philz kernel.
If I helped hit the thanks button.
Hi @kaborayyan,
Yep, I'm certainly on Philz Kernel.... when it's loaded, its kind of a pink/purple-ish colour.... (not sure what version, but something like 5.1.1.1) It's the first one I downloaded when I got this phone a couple of months back, that I used to root/and then flash custom roms with... (namely, JB).
However, I fancy seeing what GB is like on it, but get stuck... it seems to hang on Flashing Modem, sits there, and then reboots without finishing by the looks of things...?
Its a UK Vodafone, N7000
Thanks, Lister
Did you try to flash a stock GB ROM through Odin? May be you get better results. Then root it and flash whatever you want of custom GB based Roms.
Sent from my GT-N7000
yeah like kaborayyan said, try to flash any stock GB rom using odin3 v1.85 only (you can find instructions and download links in the sticky thread in the orginal development section, you should look for mirrors because hotfile is down or just download chainfire prerooted stock rom)
After you get a stock rooted GB rom installed on your phone, install checkrom using the recovery after wiping data, cache and dalvik.
as i said stock ICS roms are unsafe, other roms are safe... just keep a backup of your efs
and be careful when using odin3.
btw, hitting the "thanks" button is easier than writing it
cheers
Sent from my GT-N7000 using xda premium
Lister Of Smeg said:
However, I fancy seeing what GB is like on it, but get stuck... it seems to hang on Flashing Modem, sits there, and then reboots without finishing by the looks of things...?
Click to expand...
Click to collapse
Go to www.samsung-updates.com firmware section. There are a few 2.3.6 roms available. Stock though. These roms might be non root able. Not really sure as there are not many methods of rooting GB (check Dr ketans thread for more info) . It could also be possible that for rooting again you will need to flash an ICS or JB rom again using Odin.
If you just want to taste the ginger then stock GB rom is quite fast.
Lister Of Smeg said:
Hi Guys,
I wondered if any of you (more experienced, long serving) users are aware of any Gingerbread ROMs? Preferably a CM or any 2.3.7 based, but if they don't exist, any build will do... It needs to be a safe build, a non eMMC bug version, or DeOxed (is that the term)?
Sure, you're gonna say, why bother.. There's JB and KK now, but I like GB and wanted to see what it's like on the N7000?
All help gratefully welcomed..
Thanks, Lister
Click to expand...
Click to collapse
Pristine LC1 is a good option. Its in the OP of the pristine thread. All GB kernels are safe, as above mentioned.
There is no 2.3.7 or CM based N7000 rom
Sent from Nexus 5 on Slimkat
Hi @ASMI1, @kaborayyan, @nokiamodeln91, @AndroidSlave,
Thanks guys, with you're help.... I've finally made it !!! It appears CheckROM HD v6 does not want to flash under Philz (or some other recovery, cant think what now??) However I did manage to get it to Flash under Abyss Recovery Kernel (which is based on GB kernel, apparently).
So it has flashed now, not had chance to play around with it yet as am at work... But just by looking at it, it's bringing back the GB love....
Yes I know it's sad, why go back to GB?? lol. But sometimes it's just nice to go over, for old times sake... Used to do it on my ZTE Blade many a times...
So, (quick questions).
1) With this stock-ish rom, can I remove/tweak/clean up, and then package it (in CWM) as a flashable rom?? or do I have to backup/restore only in that version of CWM??
2) It safe to flash any version of CM9, without using flashing a seperate recovery afterwards... and still avoid the eMMC. It's only official STOCK firmware that killed them....
Thanks once again guys for all your support, I know its not normal (and frowned upon) to use older firmware... But just wanted to see what GB was like again...
Cheers, Lister
Lister Of Smeg said:
Hi @ASMI1, @kaborayyan, @nokiamodeln91, @AndroidSlave,
Thanks guys, with you're help.... I've finally made it !!! It appears CheckROM HD v6 does not want to flash under Philz (or some other recovery, cant think what now??) However I did manage to get it to Flash under Abyss Recovery Kernel (which is based on GB kernel, apparently).
So it has flashed now, not had chance to play around with it yet as am at work... But just by looking at it, it's bringing back the GB love....
Yes I know it's sad, why go back to GB?? lol. But sometimes it's just nice to go over, for old times sake... Used to do it on my ZTE Blade many a times...
So, (quick questions).
1) With this stock-ish rom, can I remove/tweak/clean up, and then package it (in CWM) as a flashable rom?? or do I have to backup/restore only in that version of CWM??
2) It safe to flash any version of CM9, without using flashing a seperate recovery afterwards... and still avoid the eMMC. It's only official STOCK firmware that killed them....
Thanks once again guys for all your support, I know its not normal (and frowned upon) to use older firmware... But just wanted to see what GB was like again...
Cheers, Lister
Click to expand...
Click to collapse
1) not really unless you use a new version of philz touch recovery, which wouldn't happen because on the n7000 the recovery sits on the kernel, thus you are stuck with an old kernel and old recovery. As such your best bet is to do a nandroid backup. Further - when you restore such a backup, I recommend flashing abyss again first so you are in the Ame recovery it was made in
2) yes. Just be concerned of Stock ICS (4.0.4) with a custom recovery. Never flash temporary cwm.zip. matter of fact, just avoid stock ICS at all costs. Newer versions of cm9 are safe. Avoid very old cm9 versions. My personal recommendation to you would be Paranoid Android cm9 ( I think it stopped at around .4a) that one was amazing.
Sent from Nexus 5 on Slimkat