Related
Hi all.
I had recently flashed cm6 rc2 without the radio via rom manager comming straight from froyo. While using the ROM today, I noticed a lot of processes crashed all at once including acore.
When I rebooted, I was stuck in a boot loop. I wiped stuff and did a nandroid restore to get back to my stock froyo, just fine.
Was it the radio that caused it (edit: seems like rom manager may have snuck it in). Since I flashed cm6 from ROM manager, I thought it would prompt me if I needed the radio. What went wrong?
The radio on the first post of the CM6 RC2 thread is the required radio and must be flashed separately if you are not already using that radio. If you are on stock froyo you most likely are.
Radio Firmware: 4.0.6.00.12_7 (FROYO RADIO, REQUIRED!)
Check this by going to: Settings - About Phone - Baseband version
If you are not on the correct radio you can flash by downloading the zip on the first page of the CM thread.
http://forum.xda-developers.com/showthread.php?t=722798
If you update again try wiping and a reboot into the mod before your nand restore. Some common issues/fixes are in the link below.
http://forum.xda-developers.com/showpost.php?p=7418214&postcount=2055
Good luck to you.
Please read the instructions next time instead of posting a new topic.
Edit: Actually, after reading your other post, I'd say, stop what you're doing, reflash to stock, and please don't do anything more. I can see you'll be a headache for all the other users in the future as you refuse to read first then ask questions. Everything you need to know is in the first post of the CM6 RC2 thread and the wiki that is linked within that post. If you can't handle that much, please do us all a favor and don't flash custom roms.
I'm waiting for the "My phone iz bricked now" thread to arise...In the right forum next time I hope!
It's lame topics like this that get budding roms pushed to the back of the list.
chesh is right though, you need to learn by reading first. The search button is your friend.
chesh420 said:
Please read the instructions next time instead of posting a new topic.
Edit: Actually, after reading your other post, I'd say, stop what you're doing, reflash to stock, and please don't do anything more. I can see you'll be a headache for all the other users in the future as you refuse to read first then ask questions. Everything you need to know is in the first post of the CM6 RC2 thread and the wiki that is linked within that post. If you can't handle that much, please do us all a favor and don't flash custom roms.
Click to expand...
Click to collapse
Mind you. I read those instructions 1 million times. I chose not to flash it because a website said you only need it if you are comming from froyo. I had also seen a video of someone running cm6 without the radio. So I thought I was fine
jrmurph said:
The radio on the first post of the CM6 RC2 thread is the required radio and must be flashed separately if you are not already using that radio. If you are on stock froyo you most likely are.
Radio Firmware: 4.0.6.00.12_7 (FROYO RADIO, REQUIRED!)
Check this by going to: Settings - About Phone - Baseband version
If you are not on the correct radio you can flash by downloading the zip on the first page of the
If you update again try wiping and a reboot into the mod before your nand restore. Some common issues/fixes are in the link below.
Good luck to you.
Click to expand...
Click to collapse
So are you saying that the 4.0.6.00.12_7 is the radio needed to use cm6 or does it mean I need to flash the radio
GlobaL_TroTTer said:
So are you saying that the 4.0.6.00.12_7 is the radio needed to use cm6 or does it mean I need to flash the radio
Click to expand...
Click to collapse
4.0.6.00.12_7 is the Froyo radio that is required for using CM6 or Froyo roms. Froyo will work with the earlier radio, but you'll have issues with camera, video camera, MMS, SMS, and a whole slew of other things. There is another radio floating about that's from the Korean version of the Nexus Ones, and has a higher version then the initial Froyo radio, but at this time, doesn't seem to change anything. So, the way you check which radio you already have (as most Froyo roms don't come with the radio, you're required to flash it on your own) is to go into Settings -> About Phone and check what version of the radio you have listed in there. If it is anything other then the above version, then flash the above version.
Follow this guide to the "T" and you won't have any issues. And, BTW: this guide is linked in Cyanogen's original post in the CM6 RC2 thread. (Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.) http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_Nexus_One
Strangely enough, i have that radio even though i didn't flash it. is it possible it came from rom manager when i installed cm6 or could it have been there when i got froyo
chesh420 said:
4.0.6.00.12_7 is the Froyo radio that is required for using CM6 or Froyo roms. Froyo will work with the earlier radio, but you'll have issues with camera, video camera, MMS, SMS, and a whole slew of other things. There is another radio floating about that's from the Korean version of the Nexus Ones, and has a higher version then the initial Froyo radio, but at this time, doesn't seem to change anything. So, the way you check which radio you already have (as most Froyo roms don't come with the radio, you're required to flash it on your own) is to go into Settings -> About Phone and check what version of the radio you have listed in there. If it is anything other then the above version, then flash the above version.
Follow this guide to the "T" and you won't have any issues. And, BTW: this guide is linked in Cyanogen's original post in the CM6 RC2 thread. (Please visit the CyanogenMod Wiki for step-by-step installation walkthroughs and tons of other useful information.) http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_Nexus_One
Click to expand...
Click to collapse
turns out i have the radio, even though i didnt flash it (unless its not the baseband you mean) i think rom manager snuck it in- could this be possible
if you flashed froyo previously then the radio got updated with that full ROM.
one more thing, for some reason the clockwork recovery keeps dissapearing. it changes to an exclamation mark in a white triangle with a mini green android. it just dosent like me!
Once again, see my previous post where I linked you to the Cyanogen Wiki with complete, step-by-step instructions of how to install all of this manually. I would suggest the manual route, as it seems you need the practice with the commands.
chesh420 said:
Once again, see my previous post where I linked you to the Cyanogen Wiki with complete, step-by-step instructions of how to install all of this manually. I would suggest the manual route, as it seems you need the practice with the commands.
Click to expand...
Click to collapse
what im saying is that every recovery image i use disappears after i have been in the recovery image more than once Even Amon ra's recovery!
Which means you haven't done some part of the process right. I remember hearing about this once before. Just start from the very beginning of those instructions (including unlocking bootloader). Not going to harm anything if it's already been done.
chesh420 said:
Which means you haven't done some part of the process right. I remember hearing about this once before. Just start from the very beginning of those instructions (including unlocking bootloader). Not going to harm anything if it's already been done.
Click to expand...
Click to collapse
Are you sure. I searched slot and I didn't find anything about recovery images reseting. I am in need of help.
One thing about the rooting process, all I did was unlock the bootloader and install su permissions. It's hard to find detailed and I mean detailed instructions on rooting a nexus one and installing a recovery image.
do a wipe
i did everything again except unlock the bootloader again because i am not sure of the result of that if you have already done it. do you think a factory restore would do the trick in setting or do i need to http://forums.t-mobile.com/t5/Opera...-Nexus-One-to-shipping-Rom/m-p/292051#U292051
Did you do all the steps in the Cyanogen wiki that I linked you, exactly as they were? Because, if you did, you wouldn't still be having a problem. See, this is what I'm saying, you keep on posting, but you don't want to follow any instructions. Why don't you follow that t-mobile guide, and give up on installing custom roms.
And, are you saying this isn't detailed enough?? http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_Nexus_One
Or how about some video's in the sticky at the top of this forum? http://forum.xda-developers.com/showthread.php?t=705460
Or, how about these: http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_&_Tutorials
I mean, I found all of those in the last 45 seconds. Come on man. You obviously just can't follow instructions. What you need is the 5yr old from down the block that keeps beating your a$$ at MW2 to do it for you.
why dont you post a video showing exactly what happens. show it booting into recovery, then trying again and recovery disappearing.
Would just let everyone know I fixed it. I've been reading alot and now allmost fully understand the rooting and flashing side of android. Sorry for this noobish post. Will never happen again
Sent from my Nexus One using XDA App
chesh420 said:
Did you do all the steps in the Cyanogen wiki that I linked you, exactly as they were? Because, if you did, you wouldn't still be having a problem. See, this is what I'm saying, you keep on posting, but you don't want to follow any instructions. Why don't you follow that t-mobile guide, and give up on installing custom roms.
And, are you saying this isn't detailed enough?? http://wiki.cyanogenmod.com/index.php?title=Full_Update_Guide_-_Nexus_One
Or how about some video's in the sticky at the top of this forum? http://forum.xda-developers.com/showthread.php?t=705460
Or, how about these: http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_&_Tutorials
I mean, I found all of those in the last 45 seconds. Come on man. You obviously just can't follow instructions. What you need is the 5yr old from down the block that keeps beating your a$$ at MW2 to do it for you.
Click to expand...
Click to collapse
I fixed it differently from how you said I should do it even though I tried to do what you said.
Also. I OWN at WW2... you have no idea. Being cocky doesn't fix anything.
Also I know how it feels when there is a new generation of android hackers joining the community. I was with the iphone hacking community from the start. I miss the days when hacking was harder. Don't start saying I can't follow instructions on the rooting process because it was a nandroid restore that stuffed everything up. I rerooted twice just to make sure.
I hate being taken as a noob. Everyone starts somewhere.
Sent from my Nexus One using XDA App
Strange we have many FAQ's WIKI's, Great topics on <x> subject - but not one place for the suffering new user to go to. After even myself duplicating topics that have been posted multiple times it is my hope to create this topic to help guide the newly wayward Captivate user to the correct topic and keep the repeated topics down a bit.
I AM IN NO WAY RESPONSIBLE IF SOMETHING HAPPENS TO YOUR DEVICE - YOU THE OWNER OF YOUR CAPTIVATE TAKE 100% RESPONSIBILITY.
This is going to be a long long post - so make sure you use your CTRL-F in your Browser
Special Credits go to the following for putting together the information. I'm just the one gathering it up. So if something you read here helps - make sure to DONATE to them. Also if I have forgot to list you and you wish to be credited? PM me and I'll be happy to add you.
Mikey1022
CLShortFuse
Design Gears
bobbylx
nbs11
BEFORE EVEN READING THIS POST IT WOULD BE WISE TO READ THE WIKI FIRST!
Also some tips before Posting your Question!
Use the SEARCH FEATURE on the Forum and keep your search simple. (ex. GPS, Bricked, Shutdown etc..) Odds are your issue has been posted and answered a few times.
Follow the Rules: Failure to do so could get you banned or worse ridiculed!
Be Courteous and Patient! - If your posted is filled with expletives and I hate this phone, and you come off as being overall rude? Don't expect an answer and expect your post to get removed and you possibly banned.
1) What USB Drivers should I get for my computer to recognize my Captivate? These are the drivers I have used on both a Windows XP 32-bit and Windows 7 64-bit machines - so I know they work.
For Windows 64bit Click here.
For Windows 32-bit Click here.
2) How do I Root my Captivate?
By far the easiest method that I've been able to use is CLShortFuse's One-Click Root and Allow Non-Market Apps. It is a VERY SIMPLE application to use.: Click HERE to go to the post to read about it and download the application.
There is a new tool out there that is a "do-it-all-in-one" called AIO - I would check out the post here and check out the youtube video. This tool appears to do it all.
And users have asked what do I lose if I root my phone. The short answer is nothing! You will not lose any settings, pictures, media, application data etc. But you do gain a lot! I would suggest reading about rooting your device here to learn more about the benefits to rooting your phone.
3) Oh crap I have "bricked" my device!
Um no you didn't. Unless you are unable to get the phone to power on, or it will not be recognized by your computer it is not bricked. "Most" (as in 99.99999%) of the time you can get the phone back into download mode and then ODIN 1-Click back to stock. I would highly recommend going to the links posted before reading the methods I have below them.
Go to DesignGears Odin3 One-Click back to Stock thread and do what it says there.
You should also go to bobbylx's READ ME BEFORE FLASHING!!!! Thread as well by clicking here.
If your phone is still able to get to CWM You can download the stock OTA JH7 from this thread here! I would still recommend the Odin 1-Click method as it will definitely wipe all the gremlins from your phone.
You can watch this tutorial on youtube here if you wish. Credit to BlinkPhaseVideos for the tutorial.
If for some strange reason you absolutely cannot get the phone into download mode you can try one of two things:
The first method - It will take a few tries to get the timing just right so be patient:
Unplug your Device
Pull out the SIM, External SD Card, and Battery
Plug in the mini-USB Cable back into your phone.
While holding down BOTH Up/Down Volume Buttons re-insert the battery.
If you get the "grey battery charging" screen. Then you will need to try and re-attempt it as it didn't work. You should get the download screen and be ready to go back to stock.
Build a Jig to force the phone to go into download mode by reading this thread here.
Mind you this is not for the feint at heart and AT&T warranty centers might be a better option then completely frying your phone.
4) My Phone is Randomly Rebooting or Shutting down after I do <insert whatever action it was doing when it did it here.>
I was informed of two separate posts here and here and now here.
If you have a build 1008 phone and the IMEI # matches what is in this thread here then you might get a replacement device.
Feel free to try what they are posting on there and who knows? You might get lucky. But the overall consensus from what I've read is that if your phone is shutting down and it's not related to some errant application, a custom ROM, or you dipped it in water then it is hardware related and you will want to do a warranty replacement. (No warranty - OUCH! That $4.99 a mo seems pretty trivial now eh?)
5) My GPS is not working because of <insert your random thought/idea here>?
There are two awesome posts on the developer forums on thought, ideas, potential fixes that will at least help if not completely fix your GPS. Keep in mind a lot of this is speculation, personal user experiences, and some folks just madly mashing buttons and getting lucky and having no clue as to how they fixed it.
If your not having GPS issues GREAT! You don't need this then!
My personal favorite thread as it has a lot of information about how GPS works is the [GPS/AGPS] REAL solution analysis thread (Jupiter Tweaks) thread. ***Note: This is most likely only for Froyo 2.2 ROM's.
Another one that has a lot of information and might possibly work for your is:
GPS Flawless/I am requesting XDA Community and Developers to please read!!
6) So.. You think your ready to Install that Awesome <insert Name of ROM here> ROM that will CHANGE YOUR LIFE?
Uh-uh... not until you have read here first. This is that sticky topic that says "Read BEFORE flashing!!". This is probably THE MOST IMPORTANT reading you can do before you start flashing as it shows you how to backup and restore your device.
Then you need to read up on nbs11's guide on his [GUIDE] How to Install a Custom ROM by going here. This guide is VERY easy to read and can apply to most of the custom ROMs that utilize a *.zip to install. ***edit - now includes a video(s) on youtube on how to install that custom ROM.
And failing to follow the developer/cooker's instructions to the "T" could cause catastrophic issues with your phone and yes... possibly bricking your device. Make sure when you go to the ROM you wish to install that you read their install instructions as it could slightly differ from other ROMs out there.
7) So your Battery is Going Down to 0% faster than your USB can Charge Your Phone?
This - by far is probably the best thread I have read about the subject. Although some of it might be speculation - it does seem to be pretty solid work. I would suggest reading this post:How to isolate and fix battery drain (and maybe lag, too) and then see if your battery performance improves.
I hope this guide helps you out. I wish I had known this information before I started flashing ROMs.
Important Links with Additional Information about your Captivate
I have found all of these quite helpful. If you think your post should be added please PM me!
Wiki's and How-TO Basics!
The XDA Samsung Captivate Wiki
XDA and Android Terms and Acronyms Thanks to jmtheiss for creating this. Basic guide to XDA and your Captivate
AIO Captivate Toolbox: This is the all in one tool that allows you to do everything from install drivers, root your phone, and install custom ROM's. If your new this might be the tool for you to use.
Samsung HOW-TO Wiki (3rd Party Link)
The Main XDA Wiki: Lists all the phones that XDA has in their forums. Also has additional information there.
ADB for Dummies! - ADB is probably one of my best tools for tweaking my phone (and restoring stuff I break). If your going to be changing your phone around at all - READ THIS THREAD
Theming Your Phone
Captivate Theme Sticky: Go here to see all of the different themes/tweaks/mods for your Captivate phone.
MetaMorph Home Page on XDA - This is a 3rd party application that will modify the look of your phone without you having to modify any type of *.apk files yourself.
Circle Battery Mods - How to change your default Battery Icon on your status bar.
Transparent Widgets - Just what it says. But please be careful and understand what you are doing before attempting these mods.
Common Sense Before Posting Your Question - PLEASE PLEASE PLEASE READ
Before you post a question on XDA - Please make sure you have utilized the SEARCH Feature - as your issue has probably been answered at least once.
If your going to post a question, make sure it makes sense! i.e. a bad example is ZOMFGBBQSAUCE WTF DO I DO!!!1111!!!!111!!!!!! vs. Phone is Soft Bricked After Attempting to Odin 1 Click. Which one do you think people are going to know how to answer by looking at the topic? Just saying..
In the body of your text it will be very helpful if you do the following:
State clearly the issue - bricked my phone etc.
What ROM are you currently using?
What is the EXACT ERROR of the issue you are reporting?
Is your phone rooted?
Did you have USB Debugging turned on?
If you fail to put pertinent information such as the above - there is no way for anyone to answer your question.
And.. this shouldn't need to be said but I'm adding it anyways...
Be patient. Be polite. Just because you cannot understand something does not mean u can show your frustration at folks here.
Of course this does not encompass all questions - mainly this is useful for when something goes wrong with your phone.
Good resource to put everything together.
w00t Sitckied! Thanks!
JF6 to JF7 Kies Mini Update. Is it necessarily?
Question guys. After using Odin to obtain JF6, do I need to use Kies mini to get to JF7 to be able to use another ROM or I can just master clear everything and from JF6 install a new ROM? Asking because I bricked my phone trying to do OTA to JF7. Got a replacement phone. The boot loader is shot probably so its safe to say my Captivate is bricked. It won't power on at all. I think upgrading to JF7 is pointless but need your expert advice. Thanks.
I have never upgraded from jf6 to jf7 before I flashed another rom, never had any issues. Think it would be an unnecessary step if you are planning to flash over out anyway.
Sent from my SAMSUNG-SGH-I897 using XDA App
Mr.Pirate said:
Question guys. After using Odin to obtain JF6, do I need to use Kies mini to get to JF7 to be able to use another ROM or I can just master clear everything and from JF6 install a new ROM? Asking because I bricked my phone trying to do OTA to JF7. Got a replacement phone. The boot loader is shot probably so its safe to say my Captivate is bricked. It won't power on at all. I think upgrading to JF7 is pointless but need your expert advice. Thanks.
Click to expand...
Click to collapse
After you use ODIN back to JF6 - you can then upgrade back up to any ROM the Dev Forums have available.
The only caveat to this - is READ THEIR INSTRUCTIONS! Some are highly experimental and require you to install them different from the standard CWM install method. (i.e. Cyanogen and the Gingerbread port going around).
i wish this thread was around when i first started out a while back. good job on this one guys.
Can someone post something that shows how to install a theme? I have flashed a custom rom and see a theme I wanna install on it. (Already downloaded the .zip file for it, not sure what to do next)
Thanks.
nice stuff
I find that installing PDAnet as my drivers for my Captivate works well for rooting.
Nice thread. I wish I had seen this before I started flashing.
I think the OP needs to be updated with the line "Be patient. Be polite. Just because u cannot understand something does not mean u can show ur frustration at folks here."
A couple of questions. I've rooted my phone installed a custom rom (serendipity 5.5) and installed that steam. What does jpy and all those others mean? and where would I find out what mine is?
Deadclown said:
A couple of questions. I've rooted my phone installed a custom rom (serendipity 5.5) and installed that steam. What does jpy and all those others mean? and where would I find out what mine is?
Click to expand...
Click to collapse
I think all of that is listed in the WIKI with definitions.
When you see JPY - it is the last 3 letters of the Baseband Version typically - but could be the Modem or Kernel being utilized in the ROM your running. You can see what baseband you are currently running by going under Settings -> About Phone and you will see under Baseband Settings something like: "I9000UGJK4"
But... you would be better off going to the Dev's forum and looking at their release notes. 99% of the time tell you what build the kernel is based off of and the modem they are using.
LOL and yes being patient and courteous is kind of a given. If you guys have any updates, ideas, etc.... to add to the post please let me know.
diablo009 said:
I think the OP needs to be updated with the line "Be patient. Be polite. Just because u cannot understand something does not mean u can show ur frustration at folks here."
Click to expand...
Click to collapse
lol Added it!
Thanks This is helpful
thanks for posting this.
How do you upgrade a ROM?
I just flashed Super Nova 2.0.2 last night. It was updated to 2.0.6 since I flashed. How do I update? Do I have flash back to factory?
Hi there.
First off, please forgive my posting this thread into the general, but I'm still restricted to posting replies in the dev subsection where the Darky thread is at.
I'm a Bell vibrant user, and I'm having big issues with Darky's 9.0.2; my first custom ROM.
I updated from ugjl2, so I have the sbl.bin that [hopefully] avoids the corrupt SD issue.
I downloaded darky and speedmod kernel to get a CWM. I flashed the speedmod with ODIN fine. I then added the ROM to my internal SD and used CWM to apply it. All went well. I used the full wipe ROM.
Now that I'm running Darky's though, it's wonderfully smooth and responsive except that every once in a while, when I press the BACK button, it just hangs.... for like, 45-120 seconds or more. I get impatient and hit HOME and it snaps a screenshot; as if I were pressing both buttons simultaneously. Locking the screen with the power button then unlocking seems to help most, but not all of the time.
Is this because I'm using the VooDoo kernel (default option) without applying the VooDoo lagfixes? Darky states that this ROM automatically uses the ext4 filesystem, which should negate the need for the voodoo lagfix. Would I be better off to just apply the default lagfixes in CWM or reflash with the speedmod kernel selected in darky's configurator?
What are other culprits that could cause he otherwise fast system to hang on pressing back.... there doesn't seem to any pattern to when it happens that I can find... but it does happen quite a bit.
I searched the forums for this, but found no hits, any help is appreciated and TYIA.
You can grab the "android Terminal emulater " from market .. Type in "mount " and See your partitions and filesystems.. i dont think the default is ext4, its rfs..
Sent from my Galaxy S using XDA App
You're absolutely right.
All of my partitions seem to be RFS.
Odd though because in the features section of darky's thread it says explicitly that it converts all partitions to ext4. Oh well.
What's the recommendation then? Shouldn't RFS also not require lagfixing? I thought it was the samsung ext2 partitions that caused the lag.
In any case, this doesn't feel like regular lags, the system straight up hangs on pressing the back button sometimes.
ieatrocks,
I would check that the lagfix is installed.
I upgraded to Darky's v8.1 on Sunday just before v9.0 came out. v8.1. did not have lagfix installed by default so I manually ran through CWM which is there is an option to run. This made things smoother.
I then flashed to v9.02 this morning and it feels faster and smoother. My understanding is that you do not need to uninstall lagfixes and not that it is automatically installed but please check in CWM. I think the only option to convert is ext4. RFS is the laggy one which is why it converts to ext4. I also enabled all of the recommended tweaks.
Hopefully, this will give you what you expect as the experience is great for me.
Ok, trying both voodoo default options now. Will report back in a few. Thanks.
Sent from my GT-I9000 using XDA App
Not 100% gone but a *whole* lot better.
Thanks
I noticed the very odd stutter but not as bad as you mentioned. Have you checked the recommended tweaks? Other option is a wipe if possible. For me, this is a whole lot better than I've ever had
I'm surprised, running Darky's new rom and don't have any lags. I'm not running any lagfixes since android 2.2.1 therefore still on the RFS.
I'm using speedmod kernel though, I had some reboot problem with voodoo on Darky 8.0 . Maybe you should try to fully wipe it clean and reinstall after backing up your data, that's what i usually do, it's better to start fresh!
Demeryus
does any know how to change the color of text from green to default , in the messaging app?
i think your back button gets stuck, because you have mentioned that if you press the home key, it takes a screenshot.
i think somebody else had this problem too. he solved it by some way but i cant remember where it was right now.
just use the search option for 'back button stuck'.
hope it helps.
edit: i think he updated his touchkey firmware by a secret code but i am not sure.
mate....
your post should be deleted...
The Rom doesn't apply by him self any lag fixer.
Use the configurator with option WIPE, reapply Darky Rom and them post issues...
There is a reason why you are not allowed in developer section...
Read the post and use the F******ING SEARCH FUNCTION
keno_ro said:
mate....
your post should be deleted...
The Rom doesn't apply by him self any lag fixer.
Use the configurator with option WIPE, reapply Darky Rom and them post issues...
There is a reason why you are not allowed in developer section...
Read the post and use the F******ING SEARCH FUNCTION
Click to expand...
Click to collapse
I used the search function. Do you have any idea how many false hits about generic lags I got? I spent a couple of hours looking before posting my detailed situation here.
Darky's by default uses the full wipe option if you're on any rom other than a previous version of Darky's; so my install was a full WIPE. I stated that pretty obviously in my first post. Why you would fly off the handle and start cursing out new users without having the common courtesy or sense to actually read what they wrote before presenting yourself as some sort of rageaholic on a forum is just bizarre.
Thanks to the guy who suggested I look into the firmware update; I can run with that.
NoobProof said:
i think your back button gets stuck, because you have mentioned that if you press the home key, it takes a screenshot.
i think somebody else had this problem too. he solved it by some way but i cant remember where it was right now.
just use the search option for 'back button stuck'.
hope it helps.
edit: i think he updated his touchkey firmware by a secret code but i am not sure.
Click to expand...
Click to collapse
Found that thread and everything is fixed now!
http://forum.xda-developers.com/showthread.php?t=869492
Updated my firmware in Darky's and lost both buttons, Turned off the lagfixes, flashed back to ugjl2, updated the touchkey firmware, reflashed speedmod for CWM, and finally re-applied Darky's with a full wipe.
Perfect!
No lagfixes applied on this fresh install yet and everything is working great.
Gave you thanks on the post for the tip.
fllipper said:
does any know how to change the color of text from green to default , in the messaging app?
Click to expand...
Click to collapse
nobody ? please maybe an ideea?
Thanks for the nice thread title
Seriously, I never said I support the i9000M.
Darkyy said:
Thanks for the nice thread title
Seriously, I never said I support the i9000M.
Click to expand...
Click to collapse
Hahahaha oh man, I wasn't trying to cast gloom on your awesome ROM Darkyy.
The touchkey firmware hang/lag and fix weren't related to your ROM at all. It looks like it would have happened anyways no matter which ROM I used, I just happened to pick yours.
...which I am enjoying a lot btw. Thanks for all the hard work
EDIT: I found out how to change my thread title, so no more false bad advertising for Darkyy.
keno_ro said:
mate....
There is a reason why you are not allowed in developer section...
Read the post and use the F******ING SEARCH FUNCTION
Click to expand...
Click to collapse
Dude... chill out.. what you getting so upset about.. he's asking a question so he's in the right place, we all started off newbies needing some guidance, Its not the end of the world no body forced u to read / reply to this thread.. jeeez.. go take yourself for a long walk.. of a short pier...
soo... :-" has any of you guys come up with an ideea to change the green text from the messaging app back to normal ? pls?
fllipper that should be handled by the theme. AFAIK any deodexed rom can be updated with themes that alter the look including the color and text schemes of the default apps that you normally can't change.
The right place to ask this is in the themes and apps subforum. I may be completely wrong with the theme advice, but I'm reasonably sure there is an entire subforum dedicated to questions like yours.
UPDATE: this thread is closed as Entropy512 has already updated his post and confimed the problem
**moderators, pls remove this post if you want to, since it has been added in the sticky post
thx for those who chose to read this and decided on thier own what to do next
thx for those who kept silent, either like or dislike this post
thx for those claimed they have reformatted the device so many times but still running, but pls report if it failed one day. i am not hoping that ur phone will be bricked, instead, just to inform us what caused it
thx for those against this post with spams, even with possible personal attacks. i learnt a lot of english words
lastly, after the experience this time, it further urges me that this is not the place for me
good luck to u all
FROM THE MODERATOR : This news is not new, and YES you should all take great care when flashing. DO YOUR RESEARCH......... do not flash custom roms without the proper knowledge to do it safely (duh)......
Very few people have had any issue with bricking (I only know of 2)......
BUT do Your Homework........ Oka1 Moderator
FWD: by chainfire:
WARNING: I have just been informed that LPY *does* suffer from the I/O bug. Do *not* use any CWM functions ! They are dangerous and may hardbrick your flash memory !
Deleting large files while fully booted may also cause problems with your flash memory.
Also see: http://forum.xda-developers.com/showthread.php?t=1633943
Say tuned for further information.
original post by chainfire: http://forum.xda-developers.com/showpost.php?p=19030788&postcount=6 --- This is 6 months old hardly current information....... food for thought- oka1
incorrect link used above. the correct one should be
http://forum.xda-developers.com/showthread.php?p=25966147#post25966147
EDIT: some ppl in the general thread talked about even OTA upgrade is affected. can someone pls confirm this to other ppls here?
EDIT2: for the sake of safety, i suggest NOT upgrading to LPY until the problem is solved and confirmed
EDIT3: so???
what does it mean?
- you risk bricking your phone if u use the LPY rom
- at this time, the exact problem areas are to be determined
- no evidence so far if this is due to cwm or cfroot's, or it could be the stock rom
- if you r still using gb (android 2.3.6), it is suggested to stick with it at the moment
- it is "assumed" that it was due to formatting the partitions in the recovery
- wipe is NOT safe as well. i checked the source and found that a wipe will call the format_volume function, ie to do a format
is it safe to go back to gb?
- all i can say is, gb should be safe. but the problem is, how to get back to gb safely
can i flash a gb via pc odin?
- yes, you can. but again, no guarantee
is it safe to upgrade via pc odin or OTA?
- no one can assure u it is safe
- some ppl reported the phone bricked via OTA upgrade. maybe he was using a leaked one before but yet to confirm
it's only 5-10% failures so why should we concern about this?
- it's simple. u will only realize u r a victum after your phone bricked
- what we know is the number of ppl suffered. what we will know is the number of ppl who suffered avoidable issues after reading this post. but what we dono is how many lives we saved
my phone is working fine with LPY now. i cant see any problem
- as i said, u wont know what's next. perhaps u r lucky and i am lucky too, for now
what to do then?
- sorry, i want to know too. just wait and see what happen
so r u bxllshxting?
- i dont and wont mind if you think so. this is JUST A WARNING. you certainly have the final say whether to be alerted or simply ignore this post
* to moderators
even i will be banned, i will still post this to let ppl be aware about this
but its ok to use on its own....LPY
Will we ever get rid of this hardbricking issues, well how unlucky we are with this, this is getting ridiculous...
vinokirk said:
but its ok to use on its own....LPY
Click to expand...
Click to collapse
ppl in the gerenal section mentioned even OTA has this problem, although i cant proof it
ICS for Note seems to be star-crossed....
I just went back from Stock ICS by flashing Abyss first, though I wiped from with-in CF-LPY kernel no issues, restored a nandroid of Stunner. Everything seems to be working fine.
Also this shouldn't be in Development. IMHO.
OK then I "say tuned for further information"
This is a officiele kernel so no bugs, problem is ower cwm and the things that we do with the phone that a normale person not do with a phone. Xda devs are not fully understanding ics and they tread it like a gb. See all ics threads that post this rom have problems.
Ok so now im.on alba ics with lpy kernel. How do i get back to gb. Use pc odin and flash the gb firmware that doesnt cause triangle and increase cojnter??
Sent from my GT-N7000 using Tapatalk 2
robertberma said:
This is a officiele kernel so no bugs, problem is ower cwm and the things that we do with the phone that a normale person not do with a phone. Xda devs are not fully understanding ics and they tread it like a gb. See all ics threads that post this rom have problems.
Click to expand...
Click to collapse
ppl claimed OTA is affected
also, official rom doesnt mean bugs free
huzz said:
Also this shouldn't be in Development. IMHO.
Click to expand...
Click to collapse
9 out of 10 ppl came here just for download roms. i don care if it's not for development
if we don inform ppl about this, we are not a responsible developer
****in ****, was waiting so long for official ics and now it seems to cause bricks, damn. But thnx for the info, wont be using cwm recovery
so if i flash stock rom via pc odin and dont root it will all be good?
i dont need root just want ics
DNK13 said:
so if i flash stock rom via pc odin and dont root it will all be good?
i dont need root just want ics
Click to expand...
Click to collapse
I think so, yes.
I am using the official ICS and I have flashed CWM. No issues. I used CWM for full backup nandroid. Nothing is strange.
Sent via Galaxy Note
EdgaBimbam said:
****in ****, was waiting so long for official ics and now it seems to cause bricks, damn. But thnx for the info, wont be using cwm recovery
Click to expand...
Click to collapse
Feel the same too...waited so long!! Yeah it seems its not a problem with the ICS kernel per se, but an incompatability with CWM. So we could technically still use the roms as long as we don't use CWM functions/recovery at all. Anyone confirm?
Yesterday, I was afraid to brick my GNote after installing ALBA LPY directly from Kingdroid V7.
First boot and Blocked in Home without any choice to remove battery.
Second boot, same... I installed it without fullwipe.
So Fullwipe from CWM and format /system partition... hanged... and hard reboot
Formatting /system was impossible...
Restore my nandroid backup... Hanged on /system... ouch...
Boot with CWM (franco.Kernel now)... Restore OK...
iT iS Me said:
I am using the official ICS and I have flashed CWM. No issues. I used CWM for full backup nandroid. Nothing is strange.
Sent via Galaxy Note
Click to expand...
Click to collapse
i have no problems too, but i was a victum before and hard bricked my note
Maybe the main reason of bricks LPY is flashing from leaked ics roms? I cant believe about what is happening :O
ykk_five said:
ppl claimed OTA is affected
also, official rom doesnt mean bugs free
9 out of 10 ppl came here just for download roms. i don care if it's not for development
if we don inform ppl about this, we are not a responsible developer
Click to expand...
Click to collapse
you don't need to justify yourself - you did the right thing to open this thread imho!
ykk_five said:
FWD: by chainfire:
WARNING: I have just been informed that LPY *does* suffer from the I/O bug. Do *not* use any CWM functions ! They are dangerous and may hardbrick your flash memory !
Deleting large files while fully booted may also cause problems with your flash memory.
Also see: http://forum.xda-developers.com/showthread.php?t=1633943
Say tuned for further information.
original post by chainfire: http://forum.xda-developers.com/showpost.php?p=19030788&postcount=6
EDIT: some ppl in the general thread talked about even OTA upgrade is affected. can someone pls confirm this to other ppls here?
EDIT2: for the sake of safety, i suggest NOT upgrading to LPY until the problem is solved and confirmed
* to moderators
even i will be banned, i will still post this to let ppl be aware about this
Click to expand...
Click to collapse
so do you mean that flashing the whole CUSTOM rom with no root and cwm from xda or sammobile is not dangerous? is this what u mean pls reply so that all can know
Hi,
I was quite happily running ICS4.0.4 (rooted) when I decided to try a different ROM (and/or JB - can't even remember any more).
After I did a wipe (I know, I know!!!) it got stuck on the boot logo screen.
I had the phone fixed by a 3rd-party repair shop, who installed ICS4.0.3 on it and, while at the shop, I used the phone a bit to make sure it was ok.
It kept crashing intermittently, so they had another go at it and now they tell me they could only install GB on it.
So, keeping in mind that the phone had the emmc bug and I tripped over it:
Is there anyway I can install ICS again on it?
I could use some of the tools floating around to detect damaged partition blocks and work around them.
What procedure should I use to go from a stock GB (non-root) to ICS?
Specifically,
- is there a safe way to root GB (given the emmc damage already), so that I can flash the other ROM/kernels (below)
- what kernel should I use
- what ROM should I use
I would greatly appreciate any help on this. I have been eating humble pie for a week now, so I hope there is no more 'why didn't you pay attention' coming my way
Cheers
You could use hydracore kernel which works with all GB and ICS ROMs and JB none Tw ROMs I be leave you can flash with PC odin to gain root and is a safe kernel
Sent from my GT-N7000 using XDA Premium HD app
ttibbetts83 said:
You could use hydracore kernel which works with all GB and ICS ROMs and JB none Tw ROMs I be leave you can flash with PC odin to gain root and is a safe kernel
Sent from my GT-N7000 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks ttibbetts83, I will try that and see how i go
Thanks Arobase40.
I'll get a strong coffee and read your reply from top to bottom and then plan my next move.
The repair was done by people unrelated to Samsung.
I currently have GB v2.3.5, (SGN_XX_OXA_KJ1_FACTORYFS) which works well, it would seem.
I'd love to get ICS back on it but need to gather info (such as that from yourself) before I do anything.
A bit more info on the state of the emmc storage: Using 'adb shell' and executing the command DD did in fact find bad blocks in partitions 9-11 (can't recall right now exactly which ones), so there are issues there.
The partition that is in place now, __appears__ to have successfully skipped those bad blocks.
And on something slightly tangential to the current topic, I know that doing a 'WIPE DATA' from the recovery menu zaps emmc, but does that also happen when you do a factory reset from within Android? From memory, when doing so, it seems to go into recovery mode and do it, so I'd expect that it'd also damage emmc.
Cheers
arobase said:
As opposed to all alarmist and contradictory posts about eMMC bug on stock Samsung ROM : GB or ICS, I never got any issues with this so called eMMC bug and never got bricked G-Note as long as I kept at using the stock kernel, nevertheless I made various and numerous wipe whichever the ways (from recovery or the settings)...
For rooting, I always used the temporary Touch CWM to flash (which has been may be removed from XDA, I guess as it was supposed to cause bricked devices) anything : superuser, busybox, and other custom ROM... ^^
BUT when I flash a custom ROM, I always removed the custom kernel (so called "safe"), and replace it for a stock kernel and never got issues with it.
The first and last time I flashed a custom with custom kernel I got my G-Note bricked (just forgot the replace the custom kernel for a stock one... ^^) !!!
So, if you want to flash an ICS version, get one from Sammobile, and flash it with PC Odin !
You shouldn't have any problem with them !!!
Get all root and busybox files from dr Ketan, and if you can find it again use the temporary Touch CWM which has NO kernel inside : it WORKS quite fine !!!
Click to expand...
Click to collapse
Unfortunately there are no high trees on XDA beause you should look for one before typing this utter personal nonsense that could brick anybody's Gnote.
Taking your own convictions for thruth is one thing, sending innocent ppl into the jungle is another...
What you are saying is: If there is a lightning storm, just go into an open field en enjoy. I cannot say it is 100% safe, but I never got struck....I think they removed the tree i used to seek shelter from the rain, but if you search real hard you might find it anyway.
---------- Post added at 10:33 AM ---------- Previous post was at 10:17 AM ----------
amanmasgaman said:
Hi,
I was quite happily running ICS4.0.4 (rooted) when I decided to try a different ROM (and/or JB - can't even remember any more).
After I did a wipe (I know, I know!!!) it got stuck on the boot logo screen.
I had the phone fixed by a 3rd-party repair shop, who installed ICS4.0.3 on it and, while at the shop, I used the phone a bit to make sure it was ok.
It kept crashing intermittently, so they had another go at it and now they tell me they could only install GB on it.
So, keeping in mind that the phone had the emmc bug and I tripped over it:
Is there anyway I can install ICS again on it?
I could use some of the tools floating around to detect damaged partition blocks and work around them.
What procedure should I use to go from a stock GB (non-root) to ICS?
Specifically,
- is there a safe way to root GB (given the emmc damage already), so that I can flash the other ROM/kernels (below)
- what kernel should I use
- what ROM should I use
I would greatly appreciate any help on this. I have been eating humble pie for a week now, so I hope there is no more 'why didn't you pay attention' coming my way
Cheers
Click to expand...
Click to collapse
Actually you should be happy that they revived your Note after brick even if it's only running GB for now.
However if you are a brave person you can do the same trick on ICS.
Just read and understand the thread that is a guide on doing so.
You can root your GB without a problem, but there is no obligation for it to install ICS with odin.
However what you do need is the following (besides a lot of patience and courage) :
1. get the ICS files you want to flash including the pit file.
2. get a program called PIT MAGIC to recreate a suitable pit file
3. determine where your bad blocks are located
4. Load the pit file into the magic program and alter the stock pit file
with the values needed to ommit your bad emmc area
5. save it and then flash your note in odin with your newly created pit file and repartition ticked.
@OP: could you please check your internal storage capacity? Is it aroung 8GB?
Arobase we are not going to rediscuss this matter for another 556643 pages.
Just ask yourself : if there was no problem then why did samsung patch their JB kernels for it. http://forum.xda-developers.com/showpost.php?p=34933643&postcount=683
Also nobody asks you to reconsider your own experience and beliefs, but the day someone follows your instructions and bricks his phone, are you going to pay for a new motherboard ?
I'll stop this discussion here, and just hope nobody will get struck under the tree.