Related
Hi everyone,
I own a captivate-i896 (rogers)
I have run into a very serious trouble
I tried to odin back to stock and now I am experiencing this problem. I get the following message:
update media. please wait
E:Can't mount /dev/block/st110
(Invalid argument)
E:copy_dbdata:media:Can't mount DBDATA:
copy default media content failed.
PLEASE HELP.
I tried delete all user data. reinstall packages. delete cache. EVERYTHING.
I even trying flashing again 3 times. No luck.
Can someone please help?
First thing is your phone isn't bricked if it still has power and you can see things on it. Second, what were you doing with Odin when it was flashing? Was it the full Odin or a one click version? Are you making sure you flash the proper firmware? What did you have on your phone before you tried going back to stock? Lots more detail is helpful because your phone works...just not like it should. Again its no brick and searching the forums will help with your issue.
This is my Captivate. There are many like it but this one is mine.
haroonazeem638 said:
Hi everyone,
I own a captivate-i896 (rogers)
I have run into a very serious trouble
I tried to odin back to stock and now I am experiencing this problem. I get the following message:
update media. please wait
E:Can't mount /dev/block/st110
(Invalid argument)
E:copy_dbdata:media:Can't mount DBDATA:
copy default media content failed.
PLEASE HELP.
I tried delete all user data. reinstall packages. delete cache. EVERYTHING.
I even trying flashing again 3 times. No luck.
Can someone please help?
Click to expand...
Click to collapse
You had a lagfix installed that you did not disable before you reflashed. Your internal partition is still on ext4 but the data is on efs. This is not a problem. You need the one-click version of odin. Search the threads for it and instructions on flashing. You will have the att boot logo but there are ways to work around it, but first do the one click.
Sent from my SAMSUNG-SGH-I896 using XDA App
clemmie said:
You had a lagfix installed that you did not disable before you reflashed. Your internal partition is still on ext4 but the data is on efs. This is not a problem. You need the one-click version of odin. Search the threads for it and instructions on flashing. You will have the att boot logo but there are ways to work around it, but first do the one click.
Sent from my SAMSUNG-SGH-I896 using XDA App
Click to expand...
Click to collapse
I thought Lagfix didn't need to be disabled if you were flashing to stock, just going from ROM to ROM. Besides that, I don't feel comfortable running 1-click for any reason as it bricked my first phone, just trying to flash.
What ROM were you running when you encountered this problem?
Stock, with a SpeedMod kernel. I wanted to go back to a stock kernel with voodoo. Trust me on this one, one-click will restore you to 2.1 if you follow the instructions.
See this thread:
http://forum.xda-developers.com/showthread.php?t=964749
Sent from my SAMSUNG-SGH-I896 using XDA App
The reason you have to disable the lagfix is because with a new ROM you are likely flashing an integrated kernel with a lagfix. Some are Captivate-based, some are i9000-based. Additionally, some use Supercurio's Voodoo Lagfix, some use Hardcore's SpeedMod. One or more of these elements might be incompatible going from one configuration to the new flash config. Without knowing more about what you had before and what you wanted to flash, this is the best explanation I can give.
If you are irked by the AT&T boot screen, I am also partial the this fellow's package, which I have used and works well. Read and make sure you have the Rogers version.
http://forum.xda-developers.com/showthread.php?t=944418
clemmie said:
Stock, with a SpeedMod kernel. I wanted to go back to a stock kernel with voodoo. Trust me on this one, one-click will restore you to 2.1 if you follow the instructions.
Click to expand...
Click to collapse
It has nothing to do with following the instructions - It has to do with the Batch version of the phone - 1010 and 1012 batch numbers do NOT play well with 1-click.
Dante04SRT said:
It has nothing to do with following the instructions - It has to do with the Batch version of the phone - 1010 and 1012 batch numbers do NOT play well with 1-click.
Click to expand...
Click to collapse
I'm well aware of that:
http://forum.xda-developers.com/showpost.php?p=11649620&postcount=5
What you might not be aware of is that Rogers Captivates are not prone to these failures as they are different build numbers. This is a fellow Rogers customer. I'd bet dollars to doughnuts that his build is 10.11.
Thanks everyone for all the responses.
Actually I had doc's rom installed on my phone and I believe I had the hardcore speedmod kernel OR the glitterball's kernel on my fone and also had the lagfix.
I was actually in process of flashing the cyanogen 7 gingerbread when this happened. I forgot to copy the actual flash file(that i was supposed to instal from speedmod kernel recovery) and so i just decided to odin back to stock and start the process all over again. But after doing that my phone never went past the rogers splash screen.
I use the ODIN 1 click software where u just load the PDA and PIT files and flash the fone. I have tried Odin back to stock for Rogers eclair 2.1 and froyo 2.2 without any luck. I also tried the at&t 1 click odin flash back to stock without any luck.
The best I was able to do was to reach the rogers splash screen and then the screen turned black and thats it.
I flashed many different kernels but nothing happened.
I even downloaded the giorgio armani firmware for the captivate and flashed that which got rid of the mounting error in the 2e recovery screen but after the splash screen, the phone just kept vibrating and nothing happened.
I have tried everything you guys asked me too.
Also, after flashing the I9010 rom(giorgio armani), my download mode 3 button combo changed. First, I used vol up and down plus USB to get into download mode but now its changed to vol down + power. This one is not a big deal as i can still get into download mode. But I am telling you all just to help.
I also read somewhere that we cannot repartition and flash using odin 1 click if we have a lagfix kernel installed. I might have done that too that might have caused the problem.
Someone here mentioned that the file system is changed from ext4 to efs or something like that. I don't know what the real problem is.
Please help
clemmie said:
I'm well aware of that:
http://forum.xda-developers.com/showpost.php?p=11649620&postcount=5
What you might not be aware of is that Rogers Captivates are not prone to these failures as they are different build numbers. This is a fellow Rogers customer. I'd bet dollars to doughnuts that his build is 10.11.
Click to expand...
Click to collapse
My build is 10.10
but I never had a problem with flashing with 1-click ODIN to stock before.
I have tried both AT&T and rogers versions through 1-click odin.
Hope that helps.
clemmie said:
Stock, with a SpeedMod kernel. I wanted to go back to a stock kernel with voodoo. Trust me on this one, one-click will restore you to 2.1 if you follow the instructions.
See this thread:
http://forum.xda-developers.com/showthread.php?t=964749
Sent from my SAMSUNG-SGH-I896 using XDA App
Click to expand...
Click to collapse
I am just going to try your method. I am downloading from here:
http://forum.xda-developers.com/showthread.php?t=731989
However, I cant do master clear because im stuck in recovery. Does it matter?
im going to try and see.
will update soon
clemmie said:
Stock, with a SpeedMod kernel. I wanted to go back to a stock kernel with voodoo. Trust me on this one, one-click will restore you to 2.1 if you follow the instructions.
See this thread:
http://forum.xda-developers.com/showthread.php?t=964749
Sent from my SAMSUNG-SGH-I896 using XDA App
Click to expand...
Click to collapse
I got it working. THANKS A LOT TO YOU.
YOU ARE THE MAN clemmie.
I didn't know that what I was using before wasn't a 1-click odin lol
it's fixed now. just have to install the rogers eclair or froyo now. Thanks a LOT!
haroonazeem638 said:
I got it working. THANKS A LOT TO YOU.
YOU ARE THE MAN clemmie.
I didn't know that what I was using before wasn't a 1-click odin lol
it's fixed now. just have to install the rogers eclair or froyo now. Thanks a LOT!
Click to expand...
Click to collapse
It can be pretty harrowing when you are in limbo like that, glad to be of assistance.
Clemmie, YOU rock!!! I haven't had this problem, but... your instructions were stated in a way that I could visualize the whole process! If I ever have issues, I'm looking for YOU!
Hi guys, I'm new here and have been scouring the forums on how to do things but I keep getting caught with uncertainties.
I have an i896 Samsung Galaxy S Captivate with a Rogers 2.3.3 Gingerbread installed.
I have rooted it with no issues and its also unlocked.
What I want to do:
1. CyanogenMod 7
2. Overclock the CPU
But what I don't know is...
1. Since i'm running a Rogers ROM, do I have to flash to an AT&T ROM then to any custom ROM?
2. I read the instructions on how to update to the CM7 ROM but every instruction I read says I must have Froyo/Eclair to goto CM7. So do I downgrade and if so, how can I do that? I tried and what ends up happening is the phone's reception bars have an X and data doesn't work either. In the phone About properties, states that the baseband is "unknown". I suspect I need something more than a stock Rogers ROM without bootloaders. I couldn't find a 2.1 or 2.2 stock Rogers ROM with bootloders.
3. For overclocking, I installed Voltage Control and Control Freak and neither let me overclock, the max CPU is 1000Mhz. I assume I need a custom Kernal to do this but haven't been able to find how to do this during the CM7 upgrade.
I just need someone to point me in the right direction on what order to do all this and whether me having a Rogers stock 2.3.3 ROM causes an issue. I've done a lot of reading on these forums so its not like I just signed up and wanted to know the easy way out. I simply want the proper way to do things so I don't repeat the same mistakes many people may have done in the past.
I have used Odin, Heimdall, Odin One Click, Super One Click for rooting.
Hopefully someone can guide me in the right direction and help me achieve these goals!
You dont need to go back to Froyo, as GB bootloader is compatible. but you need CWM to flash CM7. you can use Rom Manager app to flash the CWM.
Just download CM7 zip file, wipe data, system and cache and install it using CWM. It comes with custom kernel so you can overclock it using those apps you mentioned. You can also flash Glitch kernel....
See that's what i've been trying to do but when it comes to installing the nightly rom in zip format, it tells me the signature failed.
Do I need to buy the premium version of rom manager or can I get away with the free version? I don't want to use my credit card, i rather wait until paypal is implemented with android market.
This is so frustrating...
BadBoiSinZ said:
See that's what i've been trying to do but when it comes to installing the nightly rom in zip format, it tells me the signature failed.
Do I need to buy the premium version of rom manager or can I get away with the free version? I don't want to use my credit card, i rather wait until paypal is implemented with android market.
This is so frustrating...
Click to expand...
Click to collapse
You need to Odin flash a custom kernel that has CWM in it and then install the zip from CWM. I don't know if all kernels for the i897 are compatable with i896 just have to read. I
Currently Fusionized
Wdustin1 said:
You need to Odin flash a custom kernel that has CWM in it and then install the zip from CWM. I don't know if all kernels for the i897 are compatable with i896 just have to read. I
Currently Fusionized
Click to expand...
Click to collapse
Ya that's what I don't know either...I read tons of threads where people with i896 Rogers roms tried to flash with AT&T based roms or i897 roms and either bricked their phones or made a mess that took much more to get them back to stock...problem is the people that have i896 roms here I can't contact until I hit 10 posts...so I'm here stuck until then...
Just flash a custom I897 kernel with cwm, once complete, yank battery, replace and button combo boot into recovery and flash the ROM. Whichever kernel you choose doesn't really matter as zip will flash a compatible kernel, the I896 and I897 are identical other than cosmetic branding.
I was on stock rogers 2.3.3.
Installed Sumari kernel. Booted into the sumari recovery, installed CM7 zip, the phone rebooted into cwm recovery, and continued installing.
It worked pretty smoothly.
okay so i flashed my phone with a stock 2.3.5 rom with CWM, but how do I update to CM7? When i boot into recovery the only option I have is reinstall package. Do i rename the CM7 zip file to update.zip and that should work? I'm so lost...
In CWM recovery you need to choose install zip from sdcard, make sure you are in fact in cwm recovery
Before you do that....you need to flash a kernel with Odin that has cwm in it...
Woo! that worked like a charm haha yea baby yea!! Thank you soo much!! i was so scared to flash my cappy going from Rogers to AT&T that it would brick the phone. Got CM7 with Glitch Kernel and overclocked to 1.4 sawweeeeet!!
Now time to fiddle around and customize!
Thanks everyone!!
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.
Firmware : 2.3.6
Build Number : GINGERBREAD.XXJW4
Galaxy S I9000
I've rooted my phone...
And I've been looking for a way to lagfix my phone...
But I keep failing; won't work..
Can someone please help me with it?
I'm a beginner...
Please help...
Just install ( Flash ) any custom rom because it's already have lagfix !
you can try this one :
http://forum.xda-developers.com/showthread.php?t=1829256
or choose anyone as you like ^_^ >>>>>> http://forum.xda-developers.com/forumdisplay.php?f=665
thanks
Hi there, try XWJW6. Its much better and lag-free already.
Then, you may flash CF Root kernel and convert the filesystem from RFS to EXT4.
GINGERBREAD.XWJW8 - Lag?
lifehijack said:
Hi there, try XWJW6. Its much better and lag-free already.
Then, you may flash CF Root kernel and convert the filesystem from RFS to EXT4.
Click to expand...
Click to collapse
Hi - forgive the noob question....it's 2013 and I've got Gingerbread.XWJW8 and find it a bit laggy. I wanted to reflash a custom kernel to address occasional lag. But from above the lagfix is standard. Does this kernel include these anti-lag features? Should I reflash or let it lie.
OBTW, tried to root it using developer mode from a couple of techniques on youtube and it failed. Is this because Samsung blocks it?
nope, flash custom kernel, semaphore or cf root n ur fone will be rooted
Sent from my GT-I9000 using xda premium
Squishy61 said:
Hi - forgive the noob question....it's 2013 and I've got Gingerbread.XWJW8 and find it a bit laggy. I wanted to reflash a custom kernel to address occasional lag. But from above the lagfix is standard. Does this kernel include these anti-lag features? Should I reflash or let it lie.
OBTW, tried to root it using developer mode from a couple of techniques on youtube and it failed. Is this because Samsung blocks it?
Click to expand...
Click to collapse
Yes the above mentioned kernel includes lagfix.
Samsung doesn't block anything. You are not following the correct method.
lifehijack said:
Yes the above mentioned kernel includes lagfix.
Samsung doesn't block anything. You are not following the correct method.
Click to expand...
Click to collapse
Thanks - but may need more help as my phone is in a rebooting cycle now
Downloaded and installed standard Firmware from Sammobile - all good
Followed directions on http://forum.xda-developers.com/showthread.php?t=1044519 and downloaded SpeedMod kernel K16 series which works on older Samsung 2.3.x roms. (mine is 2.3.6 GB). Started Odin3 and installed the .tar and it appeared to flash fine, then rebooted inot a continuous cycle. I followed directions to the letter - what could I have done wrong?
I'll try another older speedmod kernel and see what happens, otherwise it's back to the standard one again.
There shouldn't of been just one .tar, it looks like you may of flashed an update instead of a whole rom.
If there was 3 .tars then you probably put them in the wrong place. Try use a guide off android souls website. They really simple and I used them when I first started.
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