Database Develop

[Q] Properly upgrading from 2.2 to 2.3 or ICS?

So, I've been using Firefly, a 2.2 rom for a while now, and I think I'm ready to join the world of 2.3 or even an ICS rom when they're ready. Just to confirm - could I just install the rom over my current one, while wiping internal memory? Also, just to be safe: will the Wipe Data/Factory Reset format my internal SD card as well, meaning I'd lose my pictures/music/etc.? I think the answer is no, but it has been a while!

GB bootloaders first
If you are truly on a froyo rom, in order to make the jump to 2.3 you have to install the Gingerbread bootloaders. I would recommend checking out the dev section and looking at one of the one-clicks they have to get you over to GB. PM me if you have any questions

Thanks, I knew there was something I should probably do in between! Probably best to go to stock GB, then go to the custom rom of my choice, I'm guessing?

or just read the sticky on how to flash any rom including gingerbread.... that i wrote..... and is in my sig

But that sounds way too easy
Sent from my SAMSUNG-SGH-I897 using XDA App

I want to install gb bootloader on my i9010 Armani, but i dont know what bootloader works for me.The i9000 or the captivate?Maybe the i9010 closer to the captivate, but i have to know first 100% wich one work because i dont wanna brick my phone.

Well...the I9000 bootloaders work on a captivate, that is how we had gingerbread here before the leaks of the captivate bootloaders. I'm using them now on mine.
Either should work, barring any connection issues you may have between your pc and your phone. But that's the risk you take flashing bootloaders in the first place.

[Q] Upgrading from 2.2.1 to Onecosmics RC3.1

Hello,
I have Galaxy S 2.2.1 rooted (CF-root) with woring CWM, a Nandroid backup, and Onecosmics ICS goodys locked and loaded on my internal SD card. But still I can't find the b...courage to do a full wipe and flash ICS as if something goes wrong I will be without a descent smartphone for about 2-3 months.
My question is if I can flash straight from 2.2.1 or I should go through CM7 first.
One flash is simpler than 2 in my head..
I reckon that as the days go by I will do it and I want to make sure I do it the right way.
Thank you in advance.

Hi,
I, personally, went through a CM7 flash before going to OneCosmic's ICS, leaving Froyo. It took me about 10 minutes to do it, and in doing it this way, you stay close to OneCosmic's installation instructions.
1. Flash CM7
2. Reboot and test your phone (without installing apps & widgets)
3. Flash OneCosmic's ICS
Hope it might help!

Tilk94 said:
Hi,
I, personally, went through a CM7 flash before going to OneCosmic's ICS, leaving Froyo. It took me about 10 minutes to do it, and in doing it this way, you stay close to OneCosmic's installation instructions.
1. Flash CM7
2. Reboot and test your phone (without installing apps & widgets)
3. Flash OneCosmic's ICS
Hope it might help!
Click to expand...
Click to collapse
I would recommend flashing JVU (using Odin) before cm7 as it contains the latest bootloaders, just to make sure everything works as it should
Sent from my sgs

thanks!!!!

Yeah,
First I think you should install JVS with CF-Root and recovery.
Just register to samfirmware, where you can easily download the required files, also you'll find some tutorial. For CF-root, just google it, and you'll also find some tutorials, than just put the zip in your internal sd, and install it from recovery. Don't forget to remove your microSD before flashing, cause it can be damaged after.
If you did something wrong, you can still go back to stock JVS ( happened to me ) and start it over.
Regards

mformarcee said:
I would recommend flashing JVU (using Odin) before cm7 as it contains the latest bootloaders, just to make sure everything works as it should
Sent from my sgs
Click to expand...
Click to collapse
Works perfect! Thanks

aristomenis said:
Hello,
I have Galaxy S 2.2.1 rooted (CF-root) with woring CWM, a Nandroid backup, and Onecosmics ICS goodys locked and loaded on my internal SD card. But still I can't find the b...courage to do a full wipe and flash ICS as if something goes wrong I will be without a descent smartphone for about 2-3 months.
My question is if I can flash straight from 2.2.1 or I should go through CM7 first.
One flash is simpler than 2 in my head..
I reckon that as the days go by I will do it and I want to make sure I do it the right way.
Thank you in advance.
Click to expand...
Click to collapse
Dont worry, you can always Odin back to 2.x
Download mode through 3-button-combo > Odin (re-partition checked!)

Thank you for your insights, I will probably go to CM7 and then to ICS and if i get any issues I ll go back to 2.2.1 and then start from JVU.
I will let you know, soon I hope..

Going via CM7 should be the safest way. CM ROMS are the easiest and quickest ROMS to flash imo and you shouldn't have any problem. Once you do that without any problems, flashing ICS should be as easy.
Gluck!

So I tried to get CM7 over 2.2.1 with no success so I took the long road and upgraded to stock 2.3.4 via Odin, then flashed rooted CF root kernet, then upgraded to CM7 and finally (and after a lot of sweating) I got to Onecosmic's ICS which is great and really a major upgrade!
I think I have some donating to do........

aristomenis said:
So I tried to get CM7 over 2.2.1 with no success so I took the long road and upgraded to stock 2.3.4 via Odin, then flashed rooted CF root kernet, then upgraded to CM7 and finally (and after a lot of sweating) I got to Onecosmic's ICS which is great and really a major upgrade!
I think I have some donating to do........
Click to expand...
Click to collapse
wow.. ur phone went thru a marathon of flashing and booting !

You don't need courage its like an adventure learn and do it without fear
Flash gingerbread jvs or anything than cm7 or miui and than the onecosmic or teamhacksung
Sent from my GT-I9000 using xda premium

I have a 2.3.4 darky rom JVQ, with darkcore 2.9.2, can i flash directly to cm 7.1 and then to onecosmics rc3.1? Are there anychances to brick my phone in the process?
Sent from my GT-I9000 using Tapatalk

[Q] Upgrading from Milky's kernel 2.3.4 JVR to ICS

Hi all
I'm currently on 2.3.4 JVR with MilkyS Mod 1.3 and think it's time to take the plunge to ICS. I really like the speed and stability of my current set up, so was just wondering if you could help answer a few questions:
1. What's the best ICS ROM for me considering I like MilkyS? Battery life is important as is stability.
2. I have CWM already on my phone. To upgrade, is it just a case of doing a CWM back-up of my current set up, and then clearing cache's etc, downloading the new ROM to SD card and running the zip file in CWM? Or are there additional steps?
3. If I screw it up, or an unhappy, can I reload my current backed up set-up via CWM without risk?
Thanks in advance
Sach

I used dark knight v3 , it is good. just flash from cwm. but if you want to go back to GB. you will need to flash from odin , can NOT just restore a ndriod backup ....I tried it and my phone is now bricked...
Sent from my Dell Streak using XDA

ICS, want to go back to GB

i'm using the new Germany open ICS 4.0.3, N7000XXLPT. it consumes battery soooo fast. so, i wanted to go back to GB or to switch to ICS STUNNER ROM.
1st, can i go from the official German ICS to ICS STUNNER ROM directly?
if not...
2nd, how to go back to stock GB ROM?
thank

engaz said:
i'm using the new Germany open ICS 4.0.3, N7000XXLPT. it consumes battery soooo fast. so, i wanted to go back to GB or to switch to ICS STUNNER ROM.
1st, can i go from the official German ICS to ICS STUNNER ROM directly?
if not...
2nd, how to go back to stock GB ROM?
thank
Click to expand...
Click to collapse
Well the safest way used to be PC Odin....but see here.....some instance of PC odin getting stuck and then giving you super brick http://forum.xda-developers.com/showthread.php?t=1653582
You can even use Mobile Odin. No one reported bricking through that...but all risks on your own !!

I used Mobile Odin to flash LC2 and the CF kernel together. No problems and I'm glad to be back to a stable rom!

engaz said:
2nd, how to go back to stock GB ROM?
thank
Click to expand...
Click to collapse
1-Download a kernel fx franco is what you need and copy it to your sd
2-Go to recovery
3-Flash a zip
4-Choose franco kernel
5-In advance restart revovery/if you cant just turn off the phone and reboot to revovery
6-Wipe every thing
7- Flash a gb rom you have downloaded

Can I use mobile odin lite
hi all got the same issue app crashing ram almost full use (thk go power) phone very slow so i want to go back to gb but I just have mobile odin lite version and a pre rooted rom stock of gb.
can i use this to go back safely to gb if yes how if no how can i do
best regards,

Worked with Odin Lite
Just flash back to GB and everything wipe clean (unfortunately) as a new phone
I feel happy and also unhappy

Easiest way of going back is to flash darkys Odin resurrection 3.4. Then via cwm flash whatever u wanna
Sent from my GT-N7000 using xda premium

I'd say do a soft reset first to see is some rogue program is consuming the battery too fast. If not do a factory reset (in the settings of ICS) and use your device without any program to see if it's the OS that's causing the battery drain.
If I were you i'd go back to GB only when absolutely necessary!! There are a lot of advises (already 5 different workarounds in this thread!!!) on this site who can brick your device because you have to know exactly what is currently on your device before choosing the method of returning to GB otherwise it will become a brick. Unfortunately I know what I'm talking about, just bricked my device two days ago (btw I'm not blaming anyone!!). New mainboard is appr. 300 euro, all included.

AIe
Sorry for you
I have successfuly downgrade to GB through Odin Mobile Lite.
I have flash stock rom through PC Odin and it seems that it work (for me)
Now looking how to get back my root
Got my root now waiting again for ics
Best regards

[Q] Galaxy Note GT N7000 eMMC Bug/Kernel Related Question

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.