Related
So today i finally get the gusto mod my phone Android Dev 1. After downloading all the files and following the instructions here i can't get past the black g1 screen (#8). note i can also get the the rgb screen. thats it, but with so many different posts with similar issues, my brain is pounding. At this point if i can get beack to factory, ill live. what i'll hate is the fact that bricked my phone. i'll most likely get screamed on for not searching, but i think i may be searched out. any help would be appreciated.
thanks.
docfu.
first of all dont freak out lol. Download the dreaming.nbh or w/e file from the rooting instructions and place it at the root of the sdcard. Then get into the rgb screen (Camera + Power) and flash it. That should get you back to factory settings. If not, download the update.zip for w/e region you are in place it on your sd card. Enter recovery (Home + Power) and flash the update.
ok...so i tried the DREAMING file and it kept turning up no image found, alternatively i'm not sure what you mean by w/e region update. i ihavent come across that in my searches.
ok dreaming file did infact work. i feel better knowing that the phone isnt bricked. however after running the update when it prompts for action, i hit the trackball and i'm right back at the rgb screen..AGGGHHHH! sorry. i've been at this since 3pm this afternoon.
Chill. Don't freak. You can't just jump in and do something as soon as your read it. Read the whole thing and if you don't have the patients for this work on that before you work on this. bbreath.
I must say start by saying thanks guys. i stepped back, and actually took my [email protected]@ to bed. Rest does wonders. That said. I've accomplished the factory reset. so i back to a stock g1, and boy does it suck. As stated my phone WAS a dev 1. i've already started the upgrade process, my question at this point is where do you recommend i go from here. back to dev 1 or try one of the other roms. i've already installed the spl, and right now im stuck at the telnetd part of the root process. and this too may have me screaming by the end of the day...
any thoughts would be appreciated.
After the recovery image is installed you need to update the radio if you want to install a cupcake 1.5 ROM. You can get it here, rename 'update.zip', place on the SD card and boot in to recovery and flash. Then flash a ROM of your choice. You should be able to do that on RC 30, but I'm not sure if you need to install a rooted image first, so I'd wait for someone else's input before trying that.
I played it extra safe and used the rc29. as far as i know the proper radio is installed. i'll wait around before i do something stupid. thanks for the input tho. i'm trying to learn everything.
ok...so i went back to the original method for obtaining root. i was so frustrated last nite that i ended up trying to combine 2 slightly diff methods. at this point i call them the telnetd method and root.apk method. correct me if im wrong but niether one mentions the other. so i make it to the bootloader running the root.apk it runs thru the list and the fails at radio_v2. now im on the white screen wuth the skateboarders, the radio #says 1.22.12.29. so i run it again i
now im on the rgb screen at proceeds to attept the update again. this time the dreaimg.nbh fails. i'm not freaking out. im good. because i know im almost there. feedback appreciated. thanks in advance.
y'know i never thought about this..but if i reverted a dev phone to factory settings...did i relock everything? and for the record, i only have a mac. if that matters at all.
Future reference ^-^
In case you encounter this problem in the future, cause it can happen with flashing new roms if you skip a step:
You're only bricked if you are stuck at the G1 boot screen but can't get into recovery or fastboot, adb or anything. In cases where you can still get to other phone options to start over, rest assured your phone does still work, just need to step back and figure it out, which you did in this case with a little help ^-^ First few times doing anything to my phone, I went into panic mode a couple of times thinking I bricked until I read around and found out otherwise.
Just in case you didn't know these things, if you did, well, hope it was a nice read? ^-^
doctorfugazi said:
ok...so i went back to the original method for obtaining root. i was so frustrated last nite that i ended up trying to combine 2 slightly diff methods. at this point i call them the telnetd method and root.apk method. correct me if im wrong but niether one mentions the other. so i make it to the bootloader running the root.apk it runs thru the list and the fails at radio_v2. now im on the white screen wuth the skateboarders, the radio #says 1.22.12.29. so i run it again i
now im on the rgb screen at proceeds to attept the update again. this time the dreaimg.nbh fails. i'm not freaking out. im good. because i know im almost there. feedback appreciated. thanks in advance.
y'know i never thought about this..but if i reverted a dev phone to factory settings...did i relock everything? and for the record, i only have a mac. if that matters at all.
Click to expand...
Click to collapse
Well... if you actually purchased a dev phone it should not be sim locked.
Technically... after the rooting process, we all have dev phones with the exception of the sim lock.
So... what SPL are you using?
What ROM are you trying to install? Some roms you should consider partitioning your sdcard.
What radio do you have?
First thing is first.
Get the 1.4 recovery if you haven't done so already. 1.4 Recovery
Because this allows you to select any .zip file without having to rename it to update.zip. This saves on confusion so you don't try flashing a spl (like danger spl )before a radio (could brick your phone).
Second
You need the 1.5 radio to use cupcake. 2.22.19.26I
Third
Consider an spl. You have 4 choices. HARDSPL (Recommended), Eng SPL (what the dev phone defaults with.. skateboarding androids), the standard spl (nondev) and Danger SPL (risk bricking but worth it because you have more memory for your ROMs and can try HERO builds).
Fouth
Find your rom. NOTE: Read each post carefully! If it says you need a specific spl then get it! Otherwise it won't work. Some require the Danger SPL. If you chose a JF rom then you should be alright and don't even need to partition your card and it will work just like the OTA release. Some (such as Cyanogens 3.9.7) are experiemental and are not recommended for noobs.
Fifth (and probably the most important)
ALWAYS BACKUP WITH NANDROID!!!
In the event that you think that you've bricked your phone. I would say that there is a 90% chance that you didn't. As long as you have a nandroid backup and can get to the bootloader then you still have a phone. Just make sure the fastboot.exe file is in your sytem32 directory of your computer. Open CMD and cd to your fastboot backups saved on your computer. Simply
fastboot flash boot boot.img <enter>,
fastboot flash system system.img <enter>,
fastboot flash userdata data.img <enter>
fastboot reboot <enter>
and you should be back to where you were immediately after the point you backed up. Think of it as a system restore for Windows. It couldn't hurt to have a few backups stored.
If you have any questions or problems include information for us to read in a single post and edit as necessary.
Example:
AT&T
Cyanogen 3.9.7 Rom
Recovery 1.4
HARD SPL
Radio 2.22.19.26l
8GB class 4 sd card (7gb fat32/900mb ext3/100mb swap)
Theme version if any.
That way we know what we are working with.
Happy flashing.
rest assured i was in panic mode yesterday. but honestly the only thing i could really do was just step back for a while, meaning get some rest tackle it with a clean head. its frustrating for sure. this one guy tho who posted in the brick think tank thread...just cuz he couldnt figure things out in an hour he got pissed and started screaming waste of time this that and the other. total BI$CH! I was like whoa. I was at that point too. but Im not tryna be that guy.
Now, if could just figure out if i have to start from scratch, i just might be able to get my phone working again in time fro me to go to work tmrw morning.
So... what SPL are you using?
the hard SPL found here
What ROM are you trying to install?
Well i was trying to follow suggestion on something simple, like one of the early jesusfreke's. if i can step it up sure why not. but i'll pass on the partitioned sdcard setup for now.
actually I'll run with JesusFreke JFv1.51 US CRB43
What radio do you have?
radio number listed in my previous post.
Hey thanks by the way for taking the time out of your day to respond to this. i know u guys get your fair share of spazmiesters, so i appreciate it totally.
after doing research it seems that all the current roms require partitioning. or is that optional just for running apps to sd?
partitioning is optional of apps2sd for preformance. some like myself have three partitions, the third being for a linux swap
Ok ive final decided on the dudes cupcake 101. the ? i have now is do i start from scratch. im kind of in limbo as i'm stuck on the bootloader. if remember correctly i got half way thru the root process and it went down hill from there.
TMobile
RC29 / previously Dev 1
Recovery 1.4
HARD SPL
Radio currently 1.22.12.29 / trying to get to 2.22.19.26l
4gb card
(hope i did that right)
doctorfugazi said:
Ok ive final decided on the dudes cupcake 101. the ? i have now is do i start from scratch. im kind of in limbo as i'm stuck on the bootloader. if remember correctly i got half way thru the root process and it went down hill from there.
TMobile
RC29 / previously Dev 1
Recovery 1.4
HARD SPL
Radio currently 1.22.12.29 / trying to get to 2.22.19.26l
4gb card
(hope i did that right)
Click to expand...
Click to collapse
Okay... you have the recommended recovery and spl.
So all you need to do is get your rom and radio and store the zip files to the root of your sdcard. You don't need to rename them.
Just boot in recovery (power+home) and scroll down to:
[Alt+A] apply any zip from sd
And then you should see the zip files.
Upgrade your radio first.
Then your rom.
Another note... make sure you have a data plan once you've installed your rom. Depending on your rom version, you may not be able to sign in without one. If you can't sign in, you can't use your phone which is why most would recommend a custom rom or an adp rom.
Now... if I'm not mistaken... you do NOT have to partition your sdcard to install a rom (unless it's a HERO rom).
You may want to consider doing so however.
The advantages are that you can have virtually unlimited storage for apps and it's much easier to restore them after a wipe because they are still on your sdcard. Some apps will recognize the partitioned sdcard and automatically do all the apps2sd work for you by default. It is also recommended that you use at least a 2gb class4 card at MINIMUM. Any slower then a class 4 may result in system crashes and errors. Any less then a 2gb card is almost not worth all the effort since you'll likely be using at least a quarter of it for the apps2sd. I would suggest buying at least a 8gb class 6 card for less then $50 online. It's both fast and plenty of storage. With apps to sd, if you do need to wipe you still have all of your apps installed. A great advantage of having apps2sd.
Also... try different roms! There are DOZENS out there! Some have the htc music installed, some have myfaves, some have special cameras, etc. Don't be afraid to experiment. As long as you have a backup and can get to the bootloader (skateboarding androids) and a pc, you can't go wrong! If fact... with the 1.4 recovery you can store several different roms on your sdcard, backup your current rom, wipe, flash a new rom to try it, wipe, flash a different rom to try that one, etc. If you decide that you didn't like any of those... just restore back to your previous backup. Simple as that. No pc needed. However having a pc is handy to get logcat information if it's not booting for some reason.
Speaking of roms not booting... while your experimenting with various roms... you MUST have patience. Sometimes (based on my personal experience with about 10+ different roms) they can take up to 15 minutes to boot up. You can literally be staring at the ANDROID or HTC logo this entire time. Unless you are using ddms.bat or adb shell logcat, you will be clueless of whats going on. DO NOT do anything unless you get the infamous "boot loop". This will be obvious. It will stick at the ANDROID or HTC screen for a while and then blink and go back to the logo. If you see it blink and go back to the logo then try pressing power + talk + menu to restart it and then immediately press the home button to bo back to recovery. Wipe... try again. This time it should work. If it doesn't then restore your backup while you research on that partitcular rom. You may have skipped a step or not have the proper requirements (partitioned card, spl, etc).
With all of that said... good luck and you'll be posting help to other users like yourself before you know it.
Hey Doc, if I'm not mistaken (other guys correct me if I'm wrong), if all, and I mean ALL you have is a boot loader (AKA SPL. ie// skating androids or colored bars) you need to reflash dreaimg.nbh to get a system back.
This ALSO flashes your SPL and RADIO back to default so reflash your radio and SPL afterward. (IN THAT ORDER I HOPE)
Binary100100 is a gentleman and a scholar
nicely written response binary.
I can't stress enough how helpful it is to have the sdk working on a computer when flashing new roms. Get ADB working, it'll save you a ton of headaches.
innerspace said:
nicely written response binary.
I can't stress enough how helpful it is to have the sdk working on a computer when flashing new roms. Get ADB working, it'll save you a ton of headaches.
Click to expand...
Click to collapse
Thank you! I do what I can.
Okay, I'm really on the fence here. I've got ADB working, I've read the warnings, I've flashed my previous WinMo phones about a hundred times. I am also getting annoyed at the missing market apps and the incredibly awful 3G uplink speed of the 2.2 test build in my area. My phone looks in no way shape or form likely to crap out, needing the warranty. So the round is in the chamber, hammer is cocked, finger is on the trigger.
Only thing holding me back is the idea of the official 2.2 update coming out tomorrow (or really any point in the first half of the week), and having to reverse everything I did (unlocking aside, I get that it's permanent, for now at least). Which all revolves around extra work. I'm not looking to flash other ROM's at the moment, just get access to tweak a few things.
So...3 questions
1) Since I'm just going to root the stock ROM, and edit a few things in build.prop, do I need to disable the online app and info backup? I'm 99% sure I read somewhere that unlocking the bootloader wipes the phone, but that's not a concern as I could just let the thing boot after unlocking it and pull my info from the cloud. This is for AFTER I root (though if you're responding, you probably already know that).
2) Any way to backup a complete system image, so that I can revert to that when the official 2.2 comes out?
3) Which SU/Rooting method do you, the knowledgable and expert [insert additional groveling] reader, suggest for FRF50? I've seen Cyanogen's and the one on Modaco ( http://android.modaco.com/content/g...-erd79-frf50-superboot-rooting-the-nexus-one/ ) I'm guessing this is a "doesn't matter," but I figure why not ask.
Was this the wrong section for this kind of thing?
I'm no expert, just have had my n1 for a couple of weeks but:
1. Can't help you there, no idea, sorry.
2. nandroid backup.
3. I've read a lot about this and I'd go with Cyan's method and amon_ra's recovery. It seems like they do the job well. Plus if you search around, you'll see instructions on going back to stock recovery from amon_ra's, but I'm not sure about the other recovery image (or whether it would be the exact same procedure)
1. I really don't understand the struggle here. Why you would want to disable app backup in the first place? It's not like Google is persecuting people who unlock bootloaders that they might cut you off if they see you're rooted. Just leave it running so you don't have to install everything manually. Unlocking does wipe everything, so it'll be convenient.
2. Well yeah... Make a nandroid the way your phone is now and go back to it whenever you like. And if you like, you can restore just the system.img from fastboot.
3. I prefer the cyan method with .34 kernel. There were some people complaining that Froyo was really slow for them, but I haven't noticed that at all.
^
1) Was because of things I've read, that if you do X, you should turn off backup syncing to keep from screwing things up. I certainly have no desire to turn it off. I love it.
2)Thanks.
3) Thanks
EDIT: Done. That was stupid-fast. From installing the fastboot drivers to installing SU was 90 seconds. Add 20 more for AmonRa's recovery.
Titanium backup installed.
build.prop edited to allow protected apps and fixes to the missing ril info.
Glad it turned out okay!
I'm so glad to be rid of Twitter!
Thanks you for your input.
Ok so this is my first post here, and I'm sort of a noob so I'm sorry if these questions are too noobish...
First, I rooted my HTC hero last night, but I tried to install the rom (fresh 2.3.3) before wiping so I got stuck in this perpetual loop of the startup screen, had to wait until the phone ran out of battery and then did a wipe of data/ext and rebooted. Everything worked fine from there, and it seems to be working normally, BUT I'm wondering if this means everything installed correctly, or if I should just go through the process again.
Second, when I connect my phone to the computer I notice that I have the .zip of the image still in my phone's root. Can I delete this or is it necessary for the phone's function?
Third, are there any other roms people would suggest? I like vanilla android (not a sense fan), and I heard of a rom called Darchdroid. I was wondering how this stacks up to fresh 2.3.3...I'm looking for the smoothest experience possible (not a fan of the minor lag that happens in fresh)
And fourth, if I decide I want to get rid of Fresh and try a new rom, what is the procedure for wiping my phone clean and installing the new rom? (sorta noobish I know...)
Dr. Falken said:
Ok so this is my first post here, and I'm sort of a noob so I'm sorry if these questions are too noobish...
First, I rooted my HTC hero last night, but I tried to install the rom (fresh 2.3.3) before wiping so I got stuck in this perpetual loop of the startup screen, had to wait until the phone ran out of battery and then did a wipe of data/ext and rebooted. Everything worked fine from there, and it seems to be working normally, BUT I'm wondering if this means everything installed correctly, or if I should just go through the process again.
Second, when I connect my phone to the computer I notice that I have the .zip of the image still in my phone's root. Can I delete this or is it necessary for the phone's function?
Third, are there any other roms people would suggest? I like vanilla android (not a sense fan), and I heard of a rom called Darchdroid. I was wondering how this stacks up to fresh 2.3.3...I'm looking for the smoothest experience possible (not a fan of the minor lag that happens in fresh)
And fourth, if I decide I want to get rid of Fresh and try a new rom, what is the procedure for wiping my phone clean and installing the new rom? (sorta noobish I know...)
Click to expand...
Click to collapse
a bit noobish myself, but I think I can answer a bit regardless, anyone feel free to correct me...
1: if everything is working, great! if you dont feel comfortable, and dont mind resetting everything up, go ahead, do it again, cant hurt. whenever reflashing/new flashing, Dont Forget to make a nandroid and wipe! (and you can rename the backups in USB disk mode so you know which ones are what, otherwise go by the embedded date in the autogen'd title. in the nandroid folder on your SD card btw)
2: as far as I know, leave it?
3: HUGE fan of Darchs work, cant go wrong... keep in mind it does not have VisVoicemail in it, fix flash needed.
4: reboot into recovery, make a nadroid backup, WIPE!, flash the new one according to cookers intructions! done! (if ya dont like it, buggy, nandroid restore back to your last good one you did like!)
well I reinstalled the rom and wiped first...and everything is running way smoother than last time. I don't know what in the world happened or what was going on but I'll take it as it is
Okay so, I used the Odin JI6 Froyo flash and everything went peachy. Also installed the OCLF and the Voodoo one from off the market.
Problem is that the root wasn't total/complete and the update.zip was replaced but could not be used in full rooting or something along those lines (I'm not certain).
Anyhow, the phone worked great for the last three days, then this evening the browser wasn't refreshing facebook so I restarted the phone. After the AT&T logo it went blank and it vibrated like a beating heart constantly before restarting again after about 5 minutes, which then made it beat like a heart again etc.
I tried going to the boot screen/safe mode and reinstalling the update.zip (which didn't work because of the failed root), tried clearing my data cache, and then also i formatted the sd card. Nothing.
After that I tried putting it into download mode and flashing Odin, which didn't work. It said it was sending the PIT files but stalled there and never changed. I tried a master clear and it didn't go anywhere either.
Any advice?
You should've read the forums more before flashing and saved yourself this headache. You will need this to flash back to stock.
use thishttp://forum.xda-developers.com/showthread.php?t=731989
Dowload Odin and the drivers on the first page of the thread. Install the drivers. Run Odin as Administrator. You need to then remove your SIM, battery and external sd card if you have one. Hopefully your button combo will work to get you into download mode. Next, put battery back in, hold the vol + & - buttons and plug in your USB from pc to phone and do not let go of the volume buttons, do not touch power and you should then enter download mode. Yellow screen with android shovelling. Odin should see your phone, push start on Odin and let Odin do it's thing. When Odin finished and your phone reboots you will be back on stock JF6. While your phone is powered on and on your homescreen master clear with Odin.
You need to read a bit before flashing anything again. One Click Root doesn't work with Froyo, neither does Voodoo. Had you taken some time and read you would know this.
Good Luck, I hope this helps.
ApplCobbler said:
Okay so, I used the Odin JI6 Froyo flash and everything went peachy. Also installed the OCLF and the Voodoo one from off the market.
Problem is that the root wasn't total/complete and the update.zip was replaced but could not be used in full rooting or something along those lines (I'm not certain).
Anyhow, the phone worked great for the last three days, then this evening the browser wasn't refreshing facebook so I restarted the phone. After the AT&T logo it went blank and it vibrated like a beating heart constantly before restarting again after about 5 minutes, which then made it beat like a heart again etc.
I tried going to the boot screen/safe mode and reinstalling the update.zip (which didn't work because of the failed root), tried clearing my data cache, and then also i formatted the sd card. Nothing.
After that I tried putting it into download mode and flashing Odin, which didn't work. It said it was sending the PIT files but stalled there and never changed. I tried a master clear and it didn't go anywhere either.
Any advice?
Click to expand...
Click to collapse
I feel your pain. Been there, done that. Although your process of bricking reminds me of a more sophisticated approach....lol....mine was out of total complete noobness.
Question:
1) Can you manually boot into download/ recovery manually using 3-button combo? If so you have hope (meaning your phone is basically "un-brickable").
-Bet that made you feel better huh?
-If you can't use 3-button to go into either modes, then you are in the same boat as i was. Hope you are still within your 30 days, or at least warranty. One way to tell if you can/ can't go into either modes is to check your "Batch #."
a) remove battery
b) look below your Serial Number
c) if your Batch # = 1007 = You are safe
d) Batch # = 1008 = good luck
2) When you say Brick, do you have the unfortunate "Phone (!) PC" screen? If yes, then its a "soft brick." If No, then its a "hard brick." I would start to worry.
3) According to your post, it sounds like you have the Regular Odin and NOT the One click version, correct? If you have regular Odin, i would at least try the One click. Regardless, both versions should be able to get you back to stock (JF6), but we already know how well your current version Odin has gotten you.
If you need help, there are TONS more knowledgeable people here in the Captivate forum than I. They should be able to help.
Good Luck!
1. Yes I can go into download and recovery mode. I've attempted to reinstall the 2.2 off odin but it doesn't take. It is the One Click Odin Froyo, it does not work. The Comm screen is yellow, and the logs just say it's loading the PIT and doesnt ever change from there.
2. I have seen that phone ! computer screen, but I'm not stuck at it. When that came on I held the vilume buttons and the power button and it went back to regular boot up (which obviously still doesn't work).
3. It is the one click. I'm not smart enough to use something that involves more than one click.
Stop trying to flash Froyo. Flash back to stock then master clear. Then go read the threads in the development section of the forum before flashing anything. The fact that you tried to apply Voodoo to Froyo and you tried to use one click lagfix on Froyo shows you haven't read and don't know what your doing. You corrupted something by flashing incompatable stuff, flash back to stock and master clear for now. Read a bit and then flash Froyo.
ApplCobbler said:
1. Yes I can go into download and recovery mode. I've attempted to reinstall the 2.2 off odin but it doesn't take. It is the One Click Odin Froyo, it does not work. The Comm screen is yellow, and the logs just say it's loading the PIT and doesnt ever change from there.
2. I have seen that phone ! computer screen, but I'm not stuck at it. When that came on I held the vilume buttons and the power button and it went back to regular boot up (which obviously still doesn't work).
3. It is the one click. I'm not smart enough to use something that involves more than one click.
Click to expand...
Click to collapse
LOL . I as well. I know enough to be dangerous.
Now, on to business. If you actually read what Rhiannon has posted for you, and click on the actual link itself, you will realize that the version of Odin you are using (yes the one click) is NOT the correct version for flashing back to stock (JF6/ Eclair.....NOT froyo). Remember, if all else fails....."The One must return to the Source...." <-----Plus 9,000 to whoever can guess where thats from.
Obviously your phone falls within the 1007 since you have the Luxury/ Advantage of manually entering Download/ Recovery mode....i wish i did.
Rhiannon224 said:
You should've read the forums more before flashing and saved yourself this headache. You will need this to flash back to stock.
use thishttp://forum.xda-developers.com/showthread.php?t=731989
Dowload Odin and the drivers on the first page of the thread. Install the drivers. Run Odin as Administrator. You need to then remove your SIM, battery and external sd card if you have one. Hopefully your button combo will work to get you into download mode. Next, put battery back in, hold the vol + & - buttons and plug in your USB from pc to phone and do not let go of the volume buttons, do not touch power and you should then enter download mode. Yellow screen with android shovelling. Odin should see your phone, push start on Odin and let Odin do it's thing. When Odin finished and your phone reboots you will be back on stock JF6. While your phone is powered on and on your homescreen master clear with Odin.
You need to read a bit before flashing anything again. One Click Root doesn't work with Froyo, neither does Voodoo. Had you taken some time and read you would know this.
Good Luck, I hope this helps.
Click to expand...
Click to collapse
Well Said!
Thanks Spartan, I'm guesing too much skimming and not enough reading.
OP when someone says flash back to stock they don't mean Froyo. I don't mean to sound harsh, really I want to help you, but you have to read and follow instructions when you ask for help or it becomes frustrating to all that try to help you. If you want to get out of the mess you are in read my original post and use the Odin thread I linked for you please.
Rhiannon224 said:
Thanks Spartan, I'm guesing too much skimming and not enough reading.
OP when someone says flash back to stock they don't mean Froyo. I don't mean to sound harsh, really I want to help you, but you have to read and follow instructions when you ask for help or it becomes frustrating to all that try to help you. If you want to get out of the mess you are in read my original post and use the Odin thread I linked for you please.
Click to expand...
Click to collapse
I see you are still on Cog 2.2 B5......dont care for 8 or any of the new ones? Or Sheps? What's your story?
Mine is simple....Patience. lol
I am on Cog beta 5.5 with 2e recovery kernel, I swapped the kernel myself before DG updated. It has working GPS and it is pretty zippy, I am not noticing lag. I was going to flash beta 8 last night but there were some modem issues and people losing 3g. Then 8.1 came out and I read the changelog and it isn't much different from my setup. I didn't go to beta 7 because Tw Launcher was removed and you need that for Kies to see your phone so that's a no go. Shep is using an I9000 kernel and I don't want to mess with I9000. I liike to flash my phone but I need to use it as a phone. I have tried some ROMS that I didn't think worked as well so I stick with what has worked best for me. I have all the mods on it, stock lock screen, battery circle mod, and gps works. I may try AOSP this weekend but I work all week not at a computer and I can't just flash all day. I find that things can go wrong and it takes time to reconfigure apps and contacts and if anything goes wrong it sould take a while to fix and I haven't had time to mess with it this week. I see you are still on 2.1, that is patience. I tried out Froyo and when gps worked for the first time ever since having the phone I'm sticking with Froyo. I am waiting for Voodoo to make ot to 2.2 then it will be perfect.
Also, I forget to edit my signature if i only try something for a day or two. I was on Froyo for a few before i remembered to change my sig.
Rhiannon224 said:
Thanks Spartan, I'm guesing too much skimming and not enough reading.
Click to expand...
Click to collapse
Alright, Jesus I get it, I didn't do my homework; repeating it over and over isn't going to help any more. Thank you for the info, I'm downloading the right Odin right now and I'll do the fixes you said.
Rhiannon224 said:
I am on Cog beta 5.5 with 2e recovery kernel, I swapped the kernel myself before DG updated. It has working GPS and it is pretty zippy, I am not noticing lag. I was going to flash beta 8 last night but there were some modem issues and people losing 3g. Then 8.1 came out and I read the changelog and it isn't much different from my setup. I didn't go to beta 7 because Tw Launcher was removed and you need that for Kies to see your phone so that's a no go. Shep is using an I9000 kernel and I don't want to mess with I9000. I liike to flash my phone but I need to use it as a phone. I have tried some ROMS that I didn't think worked as well so I stick with what has worked best for me. I have all the mods on it, stock lock screen, battery circle mod, and gps works. I may try AOSP this weekend but I work all week not at a computer and I can't just flash all day. I find that things can go wrong and it takes time to reconfigure apps and contacts and if anything goes wrong it sould take a while to fix and I haven't had time to mess with it this week. I see you are still on 2.1, that is patience. I tried out Froyo and when gps worked for the first time ever since having the phone I'm sticking with Froyo. I am waiting for Voodoo to make ot to 2.2 then it will be perfect.
Also, I forget to edit my signature if i only try something for a day or two. I was on Froyo for a few before i remembered to change my sig.
Click to expand...
Click to collapse
It's all good. I was just curious, that's all. As far as the 19000, that makes two of us. I tried it, hoping that the voodoo + OCLF combo would work.......WRONG! lol
When 7 came out and i too noticed the TW removed, i thought Everyone would take a plunge into that, since many have complained that TW i/o was just unbearable. Oh well. As far as everything else you mentioned, i feel the same way.
Edit: "I9000"
spartan062984 said:
It's all good. I was just curious, that's all. As far as the 19000, that makes two of us. I tried it, hoping that the voodoo + OCLF combo would work.......WRONG! lol
When 7 came out and i too noticed the TW removed, i thought Everyone would take a plunge into that, since many have complained that TW i/o was just unbearable. Oh well. As far as everything else you mentioned, i feel the same way.
Edit: "I9000"
Click to expand...
Click to collapse
I know you were curious, I figured I would just tell you my story. I froze Tw Launcher with TIBU for now, I've used Launcher Pro for months and didn't wanmt a second running in the backround, i will unfreeze it when I need it. Yeah, I try stuff anf when it doesn't work the way I need i go back to what works. I've been using DG's stuff since SRE and I update when it is a better package for my needs, so far his stuff works for my needs. I want Voodoo though, lol. Sory to hijack the thread, lol.
ApplCobbler said:
Alright, Jesus I get it, I didn't do my homework; repeating it over and over isn't going to help any more. Thank you for the info, I'm downloading the right Odin right now and I'll do the fixes you said.
Click to expand...
Click to collapse
Again, sorry if I sounded harsh, i am just trying to help you get out of the mess you're in. You can flash Froyo in the future you just need to learn about these ROMS and fixes so you don't have these kinds of headaches. I will stop repeating now. i really hope this works. I know your stressed and wasn't trying to give you a hard time, I just thought you were missing something and I am from NY and we are pushy Let us no if you get it working.
I have made some mistakes along the way too and it was because I didn't read the instructions clearly so I do understand how you felt.
Rhiannon224 said:
I know you were curious, I figured I would just tell you my story. I froze Tw Launcher with TIBU for now, I've used Launcher Pro for months and didn't wanmt a second running in the backround, i will unfreeze it when I need it. Yeah, I try stuff anf when it doesn't work the way I need i go back to what works. I've been using DG's stuff since SRE and I update when it is a better package for my needs, so far his stuff works for my needs. I want Voodoo though, lol. Sory to hijack the thread, lol.
Click to expand...
Click to collapse
""Sory to hijack the thread""
I started it. No worries. I too would love to have voodoo. So far, with stock OS, ext2 + OCLF seems to work for me....for now. Keep in mind that i too would like to have the functionality of a Phone. That was my intention in the first place...lol.
ok so the other day i went and downloaded cognition v2.3b3 and it went off without a problem. i then wanted to download the v2.3b3 update and the stock lock and circle battery indicators. so i read that i needed to remove voodoo or disable it so i created the disable lag-fix folder, then i read that i needed to use odin and return to stock firmware...i tried that and it didnt work, so then i remembered that i needed to enter download mode...i couldnt get it into download mode...i used oclf thinking i needed to do that to then use odin but it didnt work...i did all this because the update supposedly had the android 2.1 keyboard with that haptic feedback...please help i want to return to stock and i can take it from there...and yes i did search the forums but cog is so big that there are tons of things associated with it and i didnt see my answer..my phone still works ...btw cog is great i love it
If you are trying to flash stock you need to read more about Odin. Cog has nothing to do with it. If you want to move up with cognition you do not have to go back to stock. You can flash the update through Rom manager. Just make sure lag fix is disabled. I see you made the folder make sure you reboot.
Captivate
Cog 2.2
i dont think i conveyed that right...i know they are different...i tried to upgrade using rom manager but when i did i kept getting an error stating basically it couldnt find the sd card or something to that affect....i think at this point i need to return to stock since i un-rooted the device...any recommendations since im using cog? what i mean is...do i need to do anything special....thanks for any and all replies
the first thing you need to do is learn how to read the cognition FAQs....its all explained in there and in the massive thread....why do you need to create a new topic on it?
i got it figured out..and i did read the FAQs but there were somethings i wasnt sure of im not a genius on this stuff like many of you are...
After you disable lagfix, make sure your phone is set to usb development mode (settings->applications).
Before you start, I recommend copying everything from the internal sdcard to your computer for backup.
1. Start the Odin one click to stock and connect your phone. Do a master clear. I've had some trouble with master clear after cog 2.3, but it's the first thing to try
2. turn phone off. Make sure usb is disconnected, SIM is out, and the odin program open on PC. Hold both volume keys and insert USB cable. You have to wait a couple of seconds until you see the digging robot. If you got that, you're in download mode. Click on the start and wait until the rebooting cycles are over.
3. If you couldn't do a master reset before, try it again. I would also recommend reformating the internal sdcard and copying back only what you need (assuming you backed it up).