Related
So... believe me, I know I'm an idiot for doing this. When trying to install Voodoo for official 2.2.1 I accidentally flashed the 5.5 for GT-I9000 that I forgot to delete when I was first starting to mess around with attempting to install voodoo, before doing much research.
When I tried to reboot it just sat at the I9000 boot screen forever and started to get hot so I pulled the battery.
I rebooted and came to a screen with lots of error messages from CWM on the bottom of the screen and the stock recovery options at the top.
When I try to reboot it just sits at the I9000 boot screen forever.
I tried reflashing 2.2.1 with ODIN as described in this thread http://forum.xda-developers.com/showthread.php?t=881064 That doesn't seem to get very far.
<ID:0/007> Added!!
<ID:0/007> Odin v.3 engine (ID:7)..
<ID:0/007> File analysis..
<ID:0/007> All threads complete. (succeed 0 / failed 1)
Did I completely brick my phone or is there some way to get it working again? really desperate here... I don't want to have to go back to my RAZR2 for another year until I can get an upgrade.
Thanks in advance to any golden saint that can help me out!
Never mind, I got ODIN to work (I hastily left out the step loading the tar file) and all seems to be working fine now. Albeit minus a hundred apps or so...
I apologize to anybody who spent time reading this thread.
Fidelis83 said:
Never mind, I got ODIN to work (I hastily left out the step loading the tar file) and all seems to be working fine now. Albeit minus a hundred apps or so...
I apologize to anybody who spent time reading this thread.
Click to expand...
Click to collapse
haha glad you got it working. Hope you had titanium for your apps! If not lesson learned! I thought I trashed my phone a few times thank the Devs for Odin! And boot camp for my mac...haha
droidzach said:
haha glad you got it working. Hope you had titanium for your apps! If not lesson learned! I thought I trashed my phone a few times thank the Devs for Odin! And boot camp for my mac...haha
Click to expand...
Click to collapse
Yep, got Titanium first thing after I rooted.
A million thanks to phidelt82 for the ODIN writeup!
I also flashed Voodoo5.5 to my Epic! Please Help!
I obviously didn't do my homework and flashed the latest voodoo kernel to my epic. I'm running a Rooted Epic w/ Fyoyo and have clockwork mod. So here's how it went: The kernel flashed (said it installed )and phone returtned to clockwork mod. I rebooted and phone stuck in a boot loop just as yours was. I have to pull the battery to shut the phone off. I can get into clockwork mod....where do I go from here? I have the phone backed up with titanium, which is great if I can get it to boot up. Please Help. Thanks.
Cbisk said:
I obviously didn't do my homework and flashed the latest voodoo kernel to my epic. I'm running a Rooted Epic w/ Fyoyo and have clockwork mod. So here's how it went: The kernel flashed (said it installed )and phone returtned to clockwork mod. I rebooted and phone stuck in a boot loop just as yours was. I have to pull the battery to shut the phone off. I can get into clockwork mod....where do I go from here? I have the phone backed up with titanium, which is great if I can get it to boot up. Please Help. Thanks.
Click to expand...
Click to collapse
Flash the correct kernel for your phone, that will fix you up. If you need any more help with that, you should post in the epic forum - since this is the mesmerize forum .
Fidelis83 said:
So... believe me, I know I'm an idiot for doing this. When trying to install Voodoo for official 2.2.1 I accidentally flashed the 5.5 for GT-I9000 that I forgot to delete when I was first starting to mess around with attempting to install voodoo, before doing much research.
When I tried to reboot it just sat at the I9000 boot screen forever and started to get hot so I pulled the battery.
Click to expand...
Click to collapse
You were even then a step ahead of me. Until I read this thread, I didn't even know that was the wrong Voodoo, in spite of it saying GT-I9000, I just figured that was the default behavior of Voodoo. XD I would have gone home tonight, maybe tomorrow, and kept beating my head against it, wondering why it wasn't working. XD
The Newbie Guide from bdemartino doesn't seem to specify---which version of Voodoo did you go with, and where did you get it from? The only Froyo Voodoo kernels I can find on the Project-Voodoo site are the 5.5 ones for the GT-I9000.
If you are on an i500 (fascinate, mesmerize, or showcase) you can flash any of the EC10 based kernels in the fascinate forum here on xda. Just remember that if you are on a touchwiz based rom (stock, PnP, etc) you need to make sure you use a touchwiz compatible kernel. Off you are running AOSP you must use an AOSP compatible kernel.
Sent from my voodoo froyo Mesmerize
Like the OP, I too flashed the wrong Voodoo kernel, the one for the GT-I9000. When I flashed it, I got the robot voice, and then it wouldn't complete the boot process.
So I panicked. I followed the instructions in the post titled "Files to get your Mesmerize back to stock 2.1 and 2.2.1", with the exception of disabling lagfix.
Everything seems to be working okay now, with one exception. I can't get the correct Voodoo lagfix working. I can get the kernel installed, but I never get the robot voice for the conversion.
I have BLN working so it seems like voodoo is installed, but my quadrant scores seem to indicate that it is not.
Help?
If that were me, and I'm certainly no expert, I'd start by taking a Titanium backup of all your apps. Next I'd boot into recovery and disable lagfix if you still can; even if the actual lagfix itself isn't working, just turn the setting off. Then I'd try to flash the stock 2.1 (or 2.2.1 as you prefer) with stock kernel and stock recovery, to treat it like a brand new phone (not sure if you did that or grabbed the stock + custom recovery). Then, just start the customization process over from scratch. Finally, once you've got it tweaked, load up Titanium again and bring over all your apps.
That is IF I understand it all correctly; if I'm telling him wrong, someone please chime in and correct, or confirm. XD (jrusch, I might wait till someone can confirm or deny my instructions, but I figured I'd least give you some food for thought)
I just can't get it to work. I disabled lagfix (even though it didn't seem to be running), and then I used Odin to flash the stock 2.2.1.
I tried a few Voodoo kernels (EC10_ulv_voodoo.zip, TW_kernel-0327-2.zip, and ec10_voodoo.zip) all with the same results. They install, I get the goofy startup screen with the flashing "android" in the middle, but no robot voice announcing the conversion process. After installing the Voodoo kernel I verify it creates the Voodoo folder in the root of the phone's memory and on the sdcard and no disable_lagfix folder exists.
jrusch said:
I just can't get it to work. I disabled lagfix (even though it didn't seem to be running), and then I used Odin to flash the stock 2.2.1.
I tried a few Voodoo kernels (EC10_ulv_voodoo.zip, TW_kernel-0327-2.zip, and ec10_voodoo.zip) all with the same results. They install, I get the goofy startup screen with the flashing "android" in the middle, but no robot voice announcing the conversion process. After installing the Voodoo kernel I verify it creates the Voodoo folder in the root of the phone's memory and on the sdcard and no disable_lagfix folder exists.
Click to expand...
Click to collapse
I'm pretty sure your system is either still in EXT4 or it thinks it is, and that's why disabling voodoo through CWM isn't doing anything for you - what has worked for me in the past is injecting the empty file named "disable-lagfix" into the clockwork folder on your SD Card, then rebooting. It should then disable it, then I would do a clean odin flash to make sure everything is working properly, then you should be able to pick up where you left off (adding voodoo, custom ROM etc.)
This has happened to me in the past when I've forgotten to disable lagfix and tried using odin to go to stock (this returns your kernel to stock and gives you issues because the internal file system is still formatted in EXT4 but the odin flash tries with the stock RFS format, and that's where the problem occurs.)
I used Root Explorer to create a new file named "disable-lagfix" in the clockework folder and rebooted. I then did a clean odin flash, etc.
I still can't get voodoo lagfix to work. When I boot to recovery (CwM Voodoo Lagfix Recovery v2.5.1.x) the voodoo menu shows:
Voodoo lagfix is actually: disabled
next boot: enabled
But at the next boot it doesn't do the conversion.
jrusch said:
I used Root Explorer to create a new file named "disable-lagfix" in the clockework folder and rebooted. I then did a clean odin flash, etc.
I still can't get voodoo lagfix to work. When I boot to recovery (CwM Voodoo Lagfix Recovery v2.5.1.x) the voodoo menu shows:
Voodoo lagfix is actually: disabled
next boot: enabled
But at the next boot it doesn't do the conversion.
Click to expand...
Click to collapse
I don't know if creating the file with root explorer will work, I had to create an empty file in my linux box and renamed to "disable-lagfix" (no quotes) once that file is in the clockwork folder and you reboot you should hear the sound of it being disabled - if you don't hear the voice then something is wrong with the file or where you put it.
right now you're stuck with it enabled, if you have the voodoo control app you can check to see if using the toggle in that app will work, but I'm guessing you're going to have to do it the manual way as stated above.
I still can't get it to work. I created the "disable-lagfix" file on a linux box and then copied the file to the sd card into the clockwork folder. I still can't get lagfix to disable/enable.
When I boot a voodoo_log.txt file is created, does this give any clues:
2011-04-12 13:03:18 model not detected
2011-04-12 13:03:18 manage fat.format in /sbin
2011-04-12 13:03:18 fat.format wrapper installed in /sbin
2011-04-12 13:03:18 fat.format renamed to fat.format.real & symlink created to fat.format_wrapper.sh
2011-04-12 13:03:18 running init !
I was trying to install the Voodoo kernel. I had the stock+froyo one installed just fine using Odin3. Then I went to their main page, and saw the 5.5 version. Titled Voodoo lagfix for Froyo stable. I used Odin to install it from the Download Mode. everything went fine till the voice said something about not enough space on the partition.
Then the T-Mobile pink screen appears, then the Samsung Vibrant S screen, then it goes black. Nothing happens after that except the bottom lights come on if I touch them. Odin3 still sees my phone as plugged in. I have a really hard time trying to get into the Recovery screen, but when I do, I have no idea what to do once I'm there.
I've tried using Odin3+Download Mode to reinstall the stock+voodoo-froyo-t959-UVKA6.tar which worked fine the first time, but I can never get back to the main home screen.
Any advice would be much appreciated, I'll be online for the next few hours refreshing this page, so my responses should be fairly quick. Thank you in advance.
Update: I tried searching for solutions, came across a post in the samsungvibrant.c o m forums with a youtube video.
I followed the instructions, everything worked as intended, until after the S screen, I just got a black screen. Never went to the home screen. This where I am currently at.
rtekbillabong said:
I was trying to install the Voodoo kernel. I had the stock+froyo one installed just fine using Odin3. Then I went to their main page, and saw the 5.5 version. Titled Voodoo lagfix for Froyo stable. I used Odin to install it from the Download Mode. everything went fine till the voice said something about not enough space on the partition.
Then the T-Mobile pink screen appears, then the Samsung Vibrant S screen, then it goes black. Nothing happens after that except the bottom lights come on if I touch them. Odin3 still sees my phone as plugged in. I have a really hard time trying to get into the Recovery screen, but when I do, I have no idea what to do once I'm there.
I've tried using Odin3+Download Mode to reinstall the stock+voodoo-froyo-t959-UVKA6.tar which worked fine the first time, but I can never get back to the main home screen.
Any advice would be much appreciated, I'll be online for the next few hours refreshing this page, so my responses should be fairly quick. Thank you in advance.
Update: I tried searching for solutions, came across a post in the samsungvibrant.c o m forums with a youtube video.
I followed the instructions, everything worked as intended, until after the S screen, I just got a black screen. Never went to the home screen. This where I am currently at.
Click to expand...
Click to collapse
WTF? Do you even have a Mes/Showcase?
Sounds like someone didn't check which forum they were in after they Googled.
You probably need to look around in this forum instead.
To all i500 users.... don't go to the project voodoo site looking for voodoo kernels. Those are generic or made just for OTHER phones. Any and all voodoo kernels you flash should be found either in this forum or the fascinate forum. This goes back to the old DO NOT FLASH PACKAGES FROM OTHER PHONES…
just trying to be helpful.
Sent from my SCH-I500 using XDA App
I have a question regarding Voodoo flashing methods, specifically relating to Odin & CWM. The Voodoo website (which contains the INCORRECT kernels for our I500s, I DID gather that already ) recommends placing the file directly onto the SD card, renaming it "update.zip" and using stock recovery to flash it. I have noticed that this sentiment is not reflected here are all - everyone seems to recommend using CWM Recovery and/or flashing everything with Odin. What gives?
If someone with a stock EC10 ROM just wanted the benefits of the Voodoo conversion, and isn't really interested in flashing a new ROM, is it really necessary to install CWM and Odin, or will the stock stuff work? From what I've gathered, this is all the OP was really trying to do from the start.
BTW, yeah, it's my first post, and yes I've been reading a lot, but definitely not nearly enough. I'm very impressed with the level of assistance forum members are willing to provide, but I, like many others, want to make sure I have it 100% correct before I turn my phone into a very fancy, very worthless piece of silicon, glass and plastic. Thanks, everybody!
I said I would flash cyanogenmod on a friends G1 because he was fed up with 1.6. I've flashed many custom ROM's on several different devices before but I've made a mess of things with this G1 and I can hardly hand back an unusable phone so I would really appreciate your help.
I rooted the phone using Androot, backed up the apps and settings using titanium backup and then the texts using a text backup app. I then downloaded Rom manager and flashed the latest clockworkmod recovery. Next I downloaded the latest official cyanogenmod rom for the dream/g1 and placed it on the phones SD card using my computer. I then re-opened rom manager and used it to select the zip file from the sd (to flash it) on prompt I checked two boxes one to wipe data and one to wipe the dalvik cache and pressed ok.
The phone rebooted into the recovery wiped the stuff, supposedly flashed the rom and rebooted. However it got stuck on the t-mobile g1 boot screen(it never showed anything else first or anything after) I left it for ages with no joy. I then tried wiping from the recovery and flashing again - same thing so i put cm5 on and tried flashing that. Same problem. Then i realised that it probably would not work because I would need to use DangerSPL as the /system partition is too small on the dream/g1. To be honest at this point I can't be bothered with to do that and this guy will be happy with anything above 1.6 to be honest so I thought I would try and flash CM4 because that's based on Eclair I believe (and so it not require I use DangerSPL or any other method to repartition the NAND). However, I tried it twice and still no luck.
At this point I'm somewhat panicking as I cannot seem to make the phone boot and it isn't even mine! Is anyone able to help?
Anyone? Please?
Look, at this stage I will forget custom roms etc. If anyone can tell me the easiest way to get this phone booting android again i would be very grateful.
Even if you could just tell me exactly how to restore it to stock 1.6 from here?
I have flashed roms on phones before - never had a problem but this is driving me crazy - please help!
wollac11 said:
Hi I said I would flash cyanogenmod on a friends G1 coz he was pissed off with 1.6 but im having trouble and I can hardly hand back an unusable phone so i really need your help.
I rooted the phone using Androot, backed up the apps and settings using titanium backup and then the texts using a text backup app. I then downloaded Rom manager and flashed the latest clockworkmod recovery. Next I downloaded the latest official cyanogenmod rom for the dream/g1 and placed it on the phones SD card using my computer. I then re-opened rom manager and used it to select the zip file from the sd (to flash it) on prompt I checked two boxes one to wipe data and one to wipe the dalvik cache and pressed ok.
The phone rebooted into the recovery wiped the stuff, supposedly flashed the rom and rebooted. However it got stuck on the t-mobile g1 boot screen(it never showed anything else first or anything after) I left it for ages with no joy. I then tried wiping from the recovery and flashing again - same thing so i put cm5 on and tried flashing that. Same problem. Then i realised that it probably would not work coz i would need to use DangerSPL coz the /system partition is too small on the dream/g1. Tbh i'm tired so I cba to do that and this guy is not that technical so he will be happy with anything above 1.6 so I thought I do CM4 coz thats 2.0 or 2.1 i seem to remember (and it not require I use DangerSPL) - tried it twice and still not luck.
HOW THE HELL CAN A GET THIS STUPID THING TO WORK AGAIN!??
MAJOR PANIC AS THIS IS NOT MY PHONE - PLEASE HELP!!!
Click to expand...
Click to collapse
Try this thread: http://forum.xda-developers.com/showthread.php?t=803482. I hope it helps.
It's been way too long since I rooted mine to be of any real help but I shall try nonetheless.
Firstly, there is a guide in the G1 forum to unroot and get back to stock firmware: Here (but note that I've never done this).
I must stress though (admittedly from memory) that if you have flashed an SPL or radio image at all, be VERY careful about the order in which you revert back to stock (or go to get a custom ROM depending on which way you decide to go). The G1 is very picky, and flashing things (mostly SPL and radio IIRC) in the wrong order will brick the device. That said, if you follow the instructions you find to the letter you should be OK. But yeah, read twice, flash once.
There is a lot of information in the stickies in the G1 forum. It could take a while to wade through but it should all be there. Failing that, post in the Q&A or General G1 subforums and I'm sure a current user will help you out.
I apologise if I've just posted a bunch of stuff you already know/have read - like I said, I've not used the phone in a while - just trying to offer what I can.
Thanks
No worries now guys i've done it! It was quite complicated but its all sorted now. If anyone is trying this and has the same (or similar) issue then pm me and I will tell you how I sorted it.
Otherwise thanks guys and you can conciser this thread:
---------------------closed--------------------------
Hi,
I have a Telus Fascinate (T959D) that I've flashed with Darky's 10.0 "Final".
I've read countless threads that tell me NOT to flash bootloaders to this phone, but we were adventurous (I don't own the device, a friend does) and wanted to try the latest Darky on it since it was working beautifully on my GT-I9000M.
Sadly, Darky's ROM requires a different bootloader, and it comes from an I9000.
After following the guide to install Darky, it effectively puts an I9000 bootloader, kernel, and ROM on the phone. (Shame on me, I know).
OK, so the problems are:
1.) No way to get into download mode or recovery mode without booting completely and issuing a 'reboot download' or 'reboot recovery' from a su terminal (or adb)
2.) The home and search softkeys act like left and right instead
There are other Darky related bugs, but not important to this discussion.
My question is: What is the safest/most reliable way to go back to stock Fascinate, bootloader and all? At this point since we don't have access to download mode without the phone booting properly, we don't want to flash anything else unless it's going to give us download mode back.
I've read the guides on going back to stock, but they all say you needed to have flashed a certain Telus ROM before going custom, and I don't know what exactly this phone had on it for sure. My friend says it was whatever was the latest update from Telus, but he hasn't plugged it into Kies in a while so I couldn't confirm for sure.
The idea here is to go back to stock then flash a custom kernel and possible a different modem to help with battery life and signal problems, and possibly some custom roms that don't require changing the bootloader.
Any insight would be greatly appreciated. If any additional info is needed, I'll provide it.
Hey just curious if you ever solved this problem as i currently have the exact same problem with a different Rom it won't allow me to boot into recovery and cwm won't recover my nandroid
I was having a hell of a time figuring some of this stuff out, so I decided to try to put some information in a solid place to find it again. Hope this helps some others out. Anyone please correct me if I am wrong about anything. I am simply putting what I understand to this point.
Terms:
Voodoo - A different recovery similar to clockwork (see post below)
CWM - ClockWork Mod (refers to being able to flash with clockwork recovery)
Lagfix - ?????? No idea what this is or what it does. Just see people saying to disable it. (see post below)
Odin - Sofware that can flash your phone. It can be found here http://forum.xda-developers.com/showpost.php?p=11872936&postcount=2
Download mode - Mode Used to flash phone using ODIN. Open Odin, remove battery, plug phone into USB port, hold down volume down key until screen comes up on phone and you see a com port active in the first block of odin.
Recovery Mode - This works for both STOCK and Voodoo. Hold down the volume up key + Home Button + Power button. Samsung will appear then disappear, and reappear again, this is when you let go of the buttons.
ED1 - Stock rom that came with phone
ED2 - Stock Rom - First update available
EE4 - Stock Rom - Second update available.
From what I learned so far, root is easily aquired by flashing down to ED1 using this file http://forum.xda-developers.com/showthread.php?t=1085190 and Odin
When using Odin you only need to insert the file, by clicking the PDA button. All other settings can be left alone.
The Droid Charge comes stock with Android 2.2.1 AKA "Froyo" which allows for flash and other improved functions.
Gingerbread is hopefully the next version 2.3 which should be a great treat for our Charge's. I was getting better performance, better battery life, and the ability to run some programs such as netflix that I cannot get to work on my froyo build right now (maybe I'm doing something wrong?) http://forum.xda-developers.com/showthread.php?t=1076150
That's all for now. Would be happy to add more if anyone else has suggestions.
I'm not a noob myself, but this just caught me off guard. I've been flashing roms since windows mobile 2003. I even made a few myself. I've owned other Samsung Android devices, but recently been using Motorola's so I have that down, but this one caught me off guard a bit.
Thanks to everyone that's been working to make this phone the best it can be.
Good idea. Let me help ya with a correction or two, and maybe a clarification.
Voodoo isn't a recovery, it's the lagfix. Techinically, Voodoo refers to Project Voodoo, an attempt at improving the Galaxy S phones:
http://project-voodoo.org/
But, for the Charge (which isn't a Galaxy S phone), when you see Voodoo referenced, they're only talking about the lagfix:
http://project-voodoo.org/lagfix
When you see people talking about disabling it, it's because they are going back to stock ROM, which doesn't support it.
Root can also be acquired by simply flashing directly to any ROM that has it built in, you don't have to be at ED1 any more. You could be at ED2 already, and flash Altered Beast using Odin, and you will be rooted. Soon we should see pre-rooted ROMs with EE4.
CWM is an alternate recovery, which, as you said, is generally used when you go in to recovery mode. A custom Android recovery basically replaces the stock recovery with one that lets you do all you can do with the stock recovery, plus a plethora of more options to give you a lot more control on your device. With a custom recovery, you can install official and unofficial ROMs as well as other updates including apps, themes, kernels etc. using zip files, wipe not just user data but pretty much every partition on your device, mount the storage card for USB mass storage access without leaving recovery, partition your SD card, wipe Dalvik cache and battery stats, fix permissions, perform, manage and restore backups and so on.
For those coming from CWM on other systems, you should know you cannot currently do backups and restores with it - that's being worked on.
Hope this helps!
The lagfix is done through Voodoo. It converts the Samsung system files from rfs to ext4. Which basically makes it run faster with no lag. Hence the Lagfix term. Depending on the kernel you're running, that would make you enable/disable Lagfix. Some kernels only run with rfs system files. Others run with the ext4 files. I'm a noob when it comes to the Samsung way of life, but I've learned a TON here and over on androidcentral. I'm coming from a rooted and ROM'd D1 myself. So I'm quite familiar with the way things are done on Motorola's.
Awesome input. Thanks so much for clearing these things up!
I just got my EE4 update but hungry for root. I wanted to try altered beast but I'd rather have a bone dry system to work up to. I'm also waiting for Gingerbread so I can do netflix. I had it on my droid 2. Also want to see overclocking.
YES
Ty, I'm a total noob, and I have spent hours and hours reading threads just trying to find out how to boot to recovery mode. This is most definately, exactly what i have been searching for! This noob thread is GENIOUS!
I am very grateful to all the members, devs, and everone for all their hard work (including the noobs that ask dumb questions so i dont have to) for making Kick @$$ programs and info for our phones.
I was really unhappy with my phone until I found this site, and learned how to modify my Charge. Y'all ROCK. (i know about the ty buttons, and i'm going to go back and hit it up for everyone thats helped!)
A voodoo kernel can also have sound and color enhancement which need to be enabled by the kernel. An app called voodoo control from the market helps to tweak the sound.
More info at http://project-voodoo.org/
Hi everyone,
I'm sorry I'm quite new to this, and I'm afraid I've gotten myself somewhat stuck with my Nexus S. Yesterday I managed to root it, install superuser, as well as clockwork mod. Today I wanted to try a new rom and after some attempts, it seems I no longer have any working roms on my phone. After much searching with no luck, I turn to you guys for your expertise.
So I am able to see fast boot upon pressing the volume up and power buttons, and am certainly able to choose recovery and get into clockwork mod. Within clockwork mod I can mount USB storage, so I can transfer roms to the internal SD card. I've tried 3 or 4 roms, some say they install correctly, others not, and after trying to boot after any installation I simply get stuck at the google screen with the lock image at the bottom. The only things I have "deleted" is wiped the data and cache. I have no idea, but I think I may have erased the bootloader image or something else that I should not have that is required.
I have a i9020a model (non-4g model I believe), can you pleeeeeeeeeeeeeaaaassee help me!! I just want to get back to gingerbread 2.3.6, and my phone back up and running the way it was. I've become quite nervous after some searching with some saying a resistor mod is needed on the hardware!!
Your okay cause you can get into fastboot and recovery so don't worry. Maybe the rom you downloaded is not for your phone. Did you make a nandroid backup before flashing the rom? If yes then go into backup and restore from clockwork recovery to go back to stock.
Sent from my A500 using Tapatalk
If you can get to recovery, just flash the stock image FOR YOUR PHONE. Then you can go through and reroot..don't worry, you'll get the hang of it.
Sent from my Nexus S using Tapatalk
So my phone is not "bricked" as they say?? I'm not in big trouble?
I did not make a nandroid backup What kind of image am I looking for and how do I install it on the phone? I know my phone is of the variant i9020a, but how am unsure of how much more specific I should be looking for.
Looking at the following post: http://forum.xda-developers.com/showthread.php?t=1063664.
Should I try installing the Android 2.3.6/GRK39F/UCKF1 Radio/KA3 Bootloader option?
Choose the latest 9020a version of the FULL ROM, which is what you have already have eyes on.
I've tried installing the file I mentioned above, but I get a status 7 error when trying to install, and the install is aborted.
Could I get some more assistance please? Can anyone point me to a correct, full rom? Or perhaps I'm installing it incorrectly, could someone be so kind to outline the correct steps to a proper install?
Edit: I think the above mentioned file is for a GSM model, I'm sure I have the CDMA version.
Also, somewhat good news. I managed to install the oxygen rom, but for the 4g version and installed fine with no errors, but I have no service. What does this indicate, as I still want to restore back to a factory version (non-4g) of gingerbread 2.3.6.
What CWM version do you have? Is it 3.0.0.0?
Also, if you have no service, it's likely that you downloaded a ROM with an incorrect radio.
Edit:
If you have CWM 3.0.0.0, make sure to download the latest version, found in this thread: http://forum.xda-developers.com/showthread.php?t=988686 (use 5023-cyan.img). You flash this the same way you did CWM previously, though in the terminal make sure you type out the 5023-cyan.img file name.
Next, download the stock ROM from this thread: http://forum.xda-developers.com/showthread.php?t=1063664. Simply look for your phone version, and you'll find the correct software variant.
Maybe you've fixed your phone already; if not, I hope this helps!
I wish you the best of luck. Oh, and through problems like these, you come to learn a lot more about your phone. That's what I've found, at least.
At the thread you mentioned above there is a version with a different radio, you might want to give that one a try.
You also said that you only wiped data and cache, so maybe you should do a full wipe before. Not doing that can sometimes lead to problems.
Sent from my Nexus S using XDA App
To be brief, the phone is up and running as brand new! Thank you so very much everyone. It seems the error was with CWM, as I was able to install and boot a 4g oxygen rom on my phone, I went into rom manager, and at the bottom of the list was an option to upgrade to 5.x. Installed the CWM update, wiped everything and was able to install the factory rom, no issues, and everything works just as I remember
I have most certainly learned more about my phone, and I am going to look at it as a rather stressful learning experience rather than a mistake on my part.
But a sincere thanks to everyone once again, I posted this at like 4am here and had a response within a few minutes, I was pulling my hair out haha!
Flashing to stock rom will help you out. You can get stock roms from Internet simply by searching in Google...
Sent from my Nexus S using XDA App