Hi I'm a new member,
I rooted my fascinate easily enough. Then searching and learning about ROMs and Kernels I decided to do use ODIN CWM Recovery to 'backup' or whatever most forums tell you to before installing a new ROM. Point is my phone is stuck in manual boot mode and I cannot undo it.
I have tried multiple times using ODIN plus the four stock files
Stock-i500-VZW-Kernel.tar.md5
Stock-i500-VZW-pit.pit
Stock-i500-VZW-Recovery.tar.md5
Stock-i500-VZW-System.tar.md5
(I always would try to implement them in order pit/system, pit/kernel, pit/recovery)
Unfortunately after the first one (pit/system) ODIN says the process fails, I go ahead with the other two and they both amount to nothing happening. My phone does not reset or do anything for this matter and I am forced to shut down ODIN and unplug my phone (upon which it dies with no battery).
Then I put back in the battery and Im back to before in manual boot mode with
Reboot system Now
Apply sdcard:update.zip
wipe data/factory rset
wipe cache partition
Btw wiped data and wiped cache and it didn't help me =(.
Please someone help me, I really don't want this new phone to be dead... Thanks in advance
Oh and when I press "apply sdcard:update.zip" I receive
E:Can't mount \dev\block\vold\179:9
(No such file or directory)
E:Can't mount SDCARD:update.zip
Installation aborted.
I really don't care at all about keeping the phone rooted or not or whatever. I just want to be able to make calls again!
So it looks like you're stuck in blue recovery ... sounds like something that Odining a stock package should fix.
Here is a nice thread for getting back to stock (it's a sticky in the general section). The packages include system, recovery, kernel, and radio in a single file (I've actually never odin'd four separate files to get back to stock, or even ever flashed a system-only file), though no pit file.
So open up odin with your phone in download mode (with the battery out, otherwise there's a small chance of odin stalling at the end), and use:
- either the DI01 all-in-one, EB01 all-in-one, or this DL09 package in PDA
- the pit file in PIT (the link says DI01/EB01 but it also works with DL09)
- check "re-partition" if it isn't already checked
- run odin and hopefully in five minutes your phone will work again If for some reason it doesn't, that thread has instructions for using heimdall, although I've never had to resort to it.
So try this and see if it works! (For which package to use, I'd suggest trying DL09 first (since you'll need it to get to the official froyo build) and DI01 if that fails. If you're wondering whether DL09+pit actually works, I've used it to get out of a "stuck in blue recovery after odining stuff" situation myself so yes, it works.)
Thank you for the response! It's encouraging to hear any support and I think yours is promising.
So unfortunately I tried D101 and no go. Turns out this was before I realized this was for 2.1 and I'd prefer 2.2 for the upgrades. Although would you suggest 2.1 for the purpose of rooting/ROMing/Kerneling in the future? I ask because I'm slowly gaining confidence that after fixing this I might be willing to try this again...
Odin (1.7 -> I decided at your poster friend's advice to upgrade from 1.3) worked well said 'pass' and everything. Unfortunately when booting my phone it went straight to the boot screen as always.
Meanwhile I'm downloading the EB01 and your suggested DL09 to test those two.
Hopefully one of those will work but if not, I guess I'll try that heimdall technique the poster suggested in the other forum. Hopefully not tho b/c it looks a bit more complicated.
I'll let ya know if one of these others works.
Yes it worked!! Thank you so much! I would buy you a round at the ale house if I could!
After running EB01 it worked (with the pit file going all the way back to factory settings). So I'm not sure what this means - maybe since it was after upgrading to 2.2 that my phone bugged out, it could only be restored to the 2.2 state which is EB01?? Idk, thanks anways.
Oh ya for the future if I try do this again - would you suggest I stay away from ROM Manager for backing up, which I believe is what started this problem in the first place? It seemed like ODIN did a fine job of managing my OS. Any thoughts? Thankss!!
mattjac1 said:
Yes it worked!! Thank you so much! I would buy you a round at the ale house if I could!
After running EB01 it worked (with the pit file going all the way back to factory settings). So I'm not sure what this means - maybe since it was after upgrading to 2.2 that my phone bugged out, it could only be restored to the 2.2 state which is EB01?? Idk, thanks anways.
Oh ya for the future if I try do this again - would you suggest I stay away from ROM Manager for backing up, which I believe is what started this problem in the first place? It seemed like ODIN did a fine job of managing my OS. Any thoughts? Thankss!!
Click to expand...
Click to collapse
Definately stay away from rom manager cwm if you have the voodoo lagfix enabled, but since all the new fascinate roms are edify scripted, flashing through cwm in rom manager would be ok.
Sent from my Froyo'd Evil Fascinate full of PB&J
Related
So i'm going to consolidate and give everyone a brief recap on how I fixed my phone since it required the use of SEVERAL posts. I figured someone will eventually get caught in the same situation I was.
This is by no means the best way, or the correct way to fix any phone, do this at your own pace and liability. I am, and no one mentioned in this thread is liable for your phone.
Please excuse any of my grammar mistakes, this is spewing out as I type.
History: Stock DI01 update w/ JT's Voodoo .2 OC Kernel.
Flashed JT's Super Clean ROM V.4 & Remix Incognito Theme.
** Market would no longer work. I had this issue before updating to the 2.2 market after the DI01 update, so I uninstalled and worked again, however, that option wasn't available with the ROM Flash.
I couldn't find a single fix that would work to get the market to work, even ADB pushing older market apk's to the system wouldn't fix it. I decided to do a flash of JT's Super Clean ROM V.2, that didn't fix the issue either.
**I was clearing data and wiping dalvik after each flash**
With nothing seeming to work, I decided to try Deodexe's Zinc ROM, and this is where **** hit the fan. After doing this, I sent my phone into FC boot loop hell. I was getting the process.acore FC everytime I pressed a key. I rebooted back into Clockwork, tried to recover from an old ROM I had backed up the previous day, notta. Damage was done. I was getting FC bootloop hell with a very crappy performance.
I decided it was time to Odin restore and start over. These aren't the exact steps I took, but if I had to do it over again, this is how I would do it. If at any point you're getting a process.media FC, remove your SD Card, and leave it out until you need it for CWM.
STEP ONE:
If you installed Voodoo (at any point, removed or not, do this step)
Thanks to adrynalyne
http://forum.xda-developers.com/showthread.php?t=804784
This was the main culprit behind my phone not working correctly after a complete restore. I moved this to the top of the list, because after that, it's downhill.
STEP TWO:
Completely Restore with Odin Restore Files
Thanks to fallingup
http://forum.xda-developers.com/showthread.php?t=782204
The instructions are a little un-clear, but do this. First, Only use the PDA option, and flash each backup one at a time along with the PIT file. You're not out of the clear yet. Read on.
STEP THREE:
Flash CWM Recovery (read my notes below)
Thanks to fallingup
http://forum.xda-developers.com/showthread.php?t=788099
After you've flashed CWM. Boot into CWM Recovery, Boot back in Stock Recovery and wipe data and cache. Boot back to CWM (select sd:update.zip) and do the exact same thing there. Reboot phone.
STEP FOUR:
Do a data factory reset
Even though you have just restored the **** out of your phone, you're still not there. Get through all the account setup fields and go to Settings > Privacy > Factory Data Reset.
After a reboot, you should be on your way to a completely 100% stock fixed phone. At this point, I would suggest making a ROM back up of this point before moving ahead with flashing again.
LAST STEP (for me anyway):
Restore apps via Titanium Backup
This restored most my apps and settings that I had already saved, including LauncherPro and the backups I had for that. If you haven't used Ti, then use whatever app backup app you do have, if you do indeed have one.
I decided to re-flash JT's Super Clean ROM V.4 found here. Thanks to JT
http://forum.xda-developers.com/showthread.php?t=796171
I am also running the Remix Incognito Theme here: Thanks to frostman89
http://forum.xda-developers.com/showthread.php?t=801867
Right now I'm mixed on updating a new Voodoo Kernel, I haven't decided if I want to do that again or wait for something else.
Thanks again for all the DEV support, hopefully someone searching will find this thread useful.
Pretty much my standard routine when trying new kernels.
I have a nandroid with my basic rooted setup (apps and data intact), so this doesn't set me back by a huge amount.
Just a few differences...
I use:
Odin (System, then kernel) (step only needed if things are *really* messed up...won't boot)
Boot into Recovery
flash update.zip to get into CWM
Wipe Data/Cache/Davlik
Reboot into recovery
run jt's voodoo_uninstall (flashes stock.zip and replaces mbr with stock mbr)
reboot into recovery
restore nandroid image.
This has yet to fail me and usually takes under 10 minutes. The nandroid image is key. Most of the time, I can skip the Odin step completely if I am not seeing anything truly, staggeringly horrific going on.
Again, jt's voodoo-uninstall seems to solve a lot more than just voodoo issues. This thing should get it's own topic/forum/entry in ROM Manager/zip code/nobel award...you get the picture.
PhoenixPath said:
Again, jt's voodoo-uninstall seems to solve a lot more than just voodoo issues. This thing should get it's own topic/forum/entry in ROM Manager/zip code/nobel award...you get the picture.
Click to expand...
Click to collapse
+1 I agree
Nice write up! I'm sure this will help many people.
Thanks
This along with several other threads allowed me to recover from my own mental retardation.
Gotta remember to remove voodoo before doing stuff. I should know better.
Thanks again.
This is not working for me. I removed voodoo (using the uninstaller). I then did odin and my phone boots but I cant do anything past the unlock bc of all the fcs I get. I wiped the cache and data. CWM is not working, when I try to do the update.zip I get a "failed to verify whole-file signiture". - I deleted the voodoo folder from the sd-card after uninstalling voodoo, dont know if that contributed to the problem. Any ideas?
Ke1evraTi said:
This is not working for me. I removed voodoo (using the uninstaller). I then did odin and my phone boots but I cant do anything past the unlock bc of all the fcs I get. I wiped the cache and data. CWM is not working, when I try to do the update.zip I get a "failed to verify whole-file signiture". - I deleted the voodoo folder from the sd-card after uninstalling voodoo, dont know if that contributed to the problem. Any ideas?
Click to expand...
Click to collapse
Sounds like you need to re-flash ClockworkMod through Odin. I'm guessing it got wiped out when you went back to stock.
I've saved a couple i9000 Odin flashed Fascinates with this method so it should work.
First, grab my DI01 All in One. You need an all inclusive package.
http://adrynalyne.us/files/kernels/DI01package3.tar.md5
You will need odin3 v 1.30. Google for it.
You also need Heimdall.
Heimdall – Glass Echidna There is a readme in the windows version zip if you get stuck. Drivers must be installed for it as well.
You also need a copy of the samsung galaxy s usb drivers, because Heimdall will remove them when you use it.
[Drivers] MS Windows x86 and x64 USB Drivers for Samsung Galaxy S - xda-developers
You will also need a PIT file from me:
http://dl.dropbox.com/u/2056318/atlas_v2.2.pit
Steps:
1. Install Heimdall and drivers.
2. Put phone in download mode and plug it in to usb cable.
3. Unzip the Odin file. 7zip can do this, but will give an EOF error. Ignore the error.
4. Choose each section in Heimdall and add the appropriate file, including PIT. Check repartition. Primary boot loader is boot.bin and secondary boot loader is sbl.bin.
5. Start. Boot once, check for problems. If problems persist, continue.
6. Reinstall Samsung USB drivers for Odin. This may require a PC reboot.
7. Put phone back in download Mode and start Odin, making sure its detected.
8. Load the entire Odin package, not extracted into the pda section of Odin. Include the PIT file. CHECK repartition.
9. Run the process.
If all goes well, you should be back to stock, crappy Eclair 2.1 without force close errors.
On a whim last night I flashed cm7 from kaoscinate. It wasnt what I wanted (nothing worked except calls data and sms), so I tried to go nack to sc 2.4. And of course I was bricked. But I just odined the eb01 radio and voila, I was ok.
Not sure if that helps.
Sent from my SCH-I500 using XDA App
i went to cm7 from sc 2.4 aswell, and to get back to sc 2.4 i just flashed cwmfroyo edition through cwm, rebooted the recovery then wiped data, re-installed sc 2.4 and bam! i was back.
upsidedownaaron said:
On a whim last night I flashed cm7 from kaoscinate. It wasnt what I wanted (nothing worked except calls data and sms), so I tried to go nack to sc 2.4. And of course I was bricked. But I just odined the eb01 radio and voila, I was ok.
Not sure if that helps.
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
I wouldn't say you were bricked. Bricked means the phone no longer functions period, no matter what you do to it. But I'm glad this helped you. I'll probably use the DL09 All in One and then flash SuperClean back over that.
When you flash an All In One, you are taking your kernel and your radio (modem) back to that version as well. When you want to go back to Froyo or whatever, make sure you flash the radio along with whatever else your flashing.
Boot looped. Wouldn't get past Samsung logo. Not an uncommon problem for me. I have become very comfortable with Odin.
Sent from my SCH-I500 using XDA App
upsidedownaaron said:
I have become very comfortable with Odin.
Click to expand...
Click to collapse
haha yeah. It's saved me but a couple times mostly anytime voodoo is involved. Tried restoring a nandroid backup of EB01 after flashing CM7 and got force closes from hell. Odin'd back using the EB01 unbloated/deodexed.tar and everything booted fine. Tried to restore the nandroid and couldn't do anything because of the force closes. Think I have corrupt data somewhere though. I also made a backup of the apps and data in MyBackupPro and ended up in the same force close situation upon reboot after restoring all. Selectively restoring a couple apps worked fine. Oh well.
Basically, I can't sustain a data connection for longer than about a minute before my fascinate disconnects. It takes about a minute to reconnect, then it disconnects again. Over and over and over. It never affects phone calls because it's not losing signal, it's just dropping the data connection.
I've been poking around my phone a bit, and in the past week, but I can't pinpoint what I did that made this start happening. I was hoping this thread would save me, but it didn't. I went back to DI01 using heimdall, booted up, still had the same problem. Reflashed with Odin, same thing. Went back to SCv2.4 with EB01 modem, same thing.
I ask this in this thread because I'm wondering what part of the phone remains untouched even with the full DI01 flash? Like some kind of low-level device mode that I triggered?
If there is nothing then it must be hardware related, and I will get a replacement.
@gizmo, maybe its time to start all over again with adryn's full di01 odin restore. i have had to do that twice now. and it has saved my butt.
i have become pretty familiar now with rebuilding my entire phone. it only takes about an hour now to go from a rom i like, to soft bricking it and then back to the rom i liked before i soft bricked with another alpha i just couldn't seem to wait to try.
Why does the movinand.bin fail when using Odin?
upsidedownaaron said:
@gizmo, maybe its time to start all over again with adryn's full di01 odin restore. i have had to do that twice now. and it has saved my butt.
i have become pretty familiar now with rebuilding my entire phone. it only takes about an hour now to go from a rom i like, to soft bricking it and then back to the rom i liked before i soft bricked with another alpha i just couldn't seem to wait to try.
Click to expand...
Click to collapse
Sounds pretty familiar . I always have to be breaking my stuff to be happy.
I've done the full heimdall DI01, followed by full Odin, to no avail. I think I messed up something with the service programming on the phone, but reactivating it doesn't help. None of the factory reset options I've tried have cleared the activation settings back to stock. Anyone know how to accomplish this?
I suppose I should move to my own thread now.
Problem: Whenever I boot my phone after the galaxy S logo dissapears the screen stays black, while the backlight on the touch sensitive buttons still come on.
So here is my background on what I have done with the phone
- It is on 2.1 Eclair
- Everything was fine. I had it rooted and running Bionix.
- When the problem started was when I was trying to install a matrix boot image, and a theme for Bionix.
- First symptons would it wouldnt get past the Vibrant (text) startup screen.
- In response I Restored to the Clockwork mod Restore which would have brang my phone back to normal.
- It did bring my phone back to normal except for one thing, there was a bug that said my cards were full and couldnt install any apps.
- So I went back into clockwork mod recovery and figured out quickly it didnt recognize my sd ext. But when my phone was on it did.
I understand that this problem is very out of now where and probably isnt very solveable with just a one click program. But I would be very thankful if anyone could give me any kind of information on this. Even if it is just saying "Its a problem with your Kernel". AlthoughI hope to see downloads and full instructions.
Thank for reading this.
CWM recovery is not supposed to be able to see your external sd, you are only supposed to be able to flash files from the internal sd.
Thanks given.
Do you know of any method I can do to fix this
You could Odin back to stock 2.1, but first turn off lag fix if there is one via voodoo app.
You want to ODIN using stock firmware and the 512 pit file. This will repartition your internal SD. You will (should) not lose personal data such as pictures, music, files.... You ended up trying to flash a theme or bootanimation that was not compatiable and when you restored traces of it have been left behind.
ODIN is the best method in these situations. Note that in rare cases it may be neccessary to do a full SD reformat.
The first thing you want to do is back everything up to your computer. All those pictures, music anything you want saved and then and only then try the odin with 512 pit.
If you need the files for odin you can check my sig for the odin exe pit file and tar file, if instead you need instructions on how to use odin i'd check here: http://forum.xda-developers.com/showthread.php?p=13132341#post13132341
shreddintyres said:
If you need the files for odin you can check my sig for the odin exe pit file and tar file, if instead you need instructions on how to use odin i'd check here: http://forum.xda-developers.com/showthread.php?p=13132341#post13132341
Click to expand...
Click to collapse
Thanks for referring, I've also included the files in the guide just in case.
I certainly hope you aren't in a partitioning brick situation. I've seen this now twice and both were running Bionix 1.3.1 w/ Voodoo enabled and both somehow got certain bml partitions in an recognizable format by CWM and the Android OS. So far it hasn't been fixable with conventional flashing and PIT repartitioning. I will be trying a full JTAG re-write on one of the customer's phones tonight. I'll report back to this thread whether a JTAG session in which I fully re-write all addresses in the NAND block was able to fix this.
This marks the 3rd instance of what I'm referring to as partitioning bricking that was involved on a Vibrant that was running Bionix 1.3.1 at the time of the brick. I'm not blaming the ROM or the developer as I have used it with no issues and it's a great piece of work but perhaps the CWM packaged with it is allowing users to do things they don't intend to do causing this issue.
Thank you everyone very much for all the information and I was able to restore my phone back to stock 2.1 Eclair and then I flashed the rom bionix onto it.
I have given thanks to everyone that has posted from here on up ^^
Also if anyone is stuck in this situation also and Is reading this thing saying "what the heck I have no idea what to do". Just message me and I could full througho instructions.
Once again thank everyone and I have solved my problem. I am pretty sure it was the boot logo that made it happen.
okay i'll preface this by saying i read all the way through the Vibrick thread and any others i could find on this subject.
i was running NeroV3, decided to try CM7. made a dumb move (apparently?) by restoring back to my stock 2.2 backup via CWM, then flashing to CM7 and THEN trying to flash the Overstock kernel (these steps should be reversed?). i wiped the cache and dalvik cache, but then the kernel flash failed ("installation aborted"), so i rebooted, which went fine. i used ROM Manager to get back to recovery, tried flashing the kernel again, failed again, hit reboot, and then my phone got stuck on the Vibrant screen.
I tried every 3-button combo (also with battery pulls) to get to Download mode but nothing works. when i plug in the USB the spinny-working-hourglass thing pops up but freezes, the green charging bar does not come up, and it does not go to download mode.
when not plugged in, it just keeps returning to the Vibrant screen. i can't even get it to turn off without pulling the battery. i'm definitely not comfortable trying the solder method.
any help is appreciated - i'm not giving it long til i take it to t-mobile and play dumb, worst comes to worst i'll just get a cheapo replacement from the store and find another vibrant (or similar) used on craigslist.
thanks!
UPDATE:::
got the phone into download mode thanks to a thread by Dolphinwigs. had to do have odin open when replacing the battery/holding volume up/down.
waiting on the stock rom download now (internet is slow). hopefully all goes well from here...
The biggest issue I find is that people give up on ODIN to easily. Getting into download mode is not that hard but also not that easy eiither. This is why everyone should purchase a jig, never give up on ODIN try it a thousand times and then once more. Always have ODIN up and ready with the proper files on hand, and as soon as it connects to ODIN be ready to make shyt happen.
In your case an ODIN flash should get you where you need to be and after you root again flashing to CM7 should not be an issue. Keep in mind if you use the .tar in ODIN as well as the .pit you will lose everything on both internal/exteral SD. At this point unless you made a backup prior to your issue its really a lost cost.
Good luck!
i am now back up and running, i just didn't realize i needed Odin running when i tried to go to download mode. so simple, but so frustrating.
one thing though, the ROM i got is Eclair. do i need to update to FroYo before flashing CM7?
and also, so i do it right this time, do i flash the Overstock kernel BEFORE i flash CM7? or does it matter?
Hello all,
I have a question that has not been answered after many hours of searching. Hopefully I'm just dumb, and my buddy's stock firmware and data isn't hosed. I'm trying to get his stock firmware running again so I can back it up safely.
What I've done:
Tried to flash CWM's update.zip via stock recovery (signature verification failed on the three different zip's I could find in the forums and various links)
Used Heimdall to push "cmenard-T959-CWM" zImage (this worked, and I get a different screen at boot)
The phone boots to the point of the T-Mobile splash screen with the annoying shriek sound, but goes to a black screen after. If i touch any of the soft buttons, they light up and remain lit. It'll stay like that for at least 20 minutes.
Is it possible to re-flash the system partition and not the data partitions using ODIN? Is that even feasible? Like I mentioned above, I'd like to get the stock firmware running such that I can make a good backup of it with all the user data intact. I haven't been able to because the CWM+root wouldn't flash.
Any suggestions or insight would be greatly appreciated.
thanks in advance!
Well as long as you don't format the internal SD, any pictures and videos and things should remain intact.
Here is a similar thread. See if it resembles your issue.
http://forum.xda-developers.com/archive/index.php/t-794869.html
Toast6977 said:
Well as long as you don't format the internal SD, any pictures and videos and things should remain intact.
Here is a similar thread. See if it resembles your issue.
http://forum.xda-developers.com/archive/index.php/t-794869.html
Click to expand...
Click to collapse
Thanks for the suggestion, Toast. I don't believe the internal SD has been messed with, and I don't plan to mess with it either. The thread you linked is not quite related to my issue, as far as I can tell.
I am able to get into Download Mode, and the Stock Recovery mode as well. However every time I try to flash an 'update.zip' with the Stock Recovery, I get an error about Signature Verification Failure.
After stepping back from it for a day, I think I've gained some clarity. Since all I've done is flash a different Kernel with Heimdall, I'm going to try to flash a stock kernel then see what happens.
Is this phone on stock Froyo or have you got it back to JFD (eclair)?
If Froyo, that's the problem. Using Odin back to Eclair and run update.zip. It won't work from stock Froyo.
*-*- I made some assumptions in my previous post. The shrieking sound. Black screen. Lights stay lit. Sounded like a poltergeist.
Glad you can get in download mode and recovery.
The old 2E vs 3E problem. Nice catch Toast
Give this a whirl: recovery 3e modified to work like recovery 2e
Might have to ABD push it to your internal SD card though.
Toast6977 said:
Is this phone on stock Froyo or have you got it back to JFD (eclair)?
If Froyo, that's the problem. Using Odin back to Eclair and run update.zip. It won't work from stock Froyo.
*-*- I made some assumptions in my previous post. The shrieking sound. Black screen. Lights stay lit. Sounded like a poltergeist.
Glad you can get in download mode and recovery.
Click to expand...
Click to collapse
Woodrube said:
The old 2E vs 3E problem. Nice catch Toast
Give this a whirl: recovery 3e modified to work like recovery 2e
Might have to ABD push it to your internal SD card though.
Click to expand...
Click to collapse
hahaha poltergeist!
Wow, so I'm glad I asked. I wouldn't have known about this issue, as I do not have any history with this device.
I know that the ROM is currently 2.2, and the Android System Recovery is showing "3e".
If I understand correctly, once I'm ready to flash up to ICS, I'll need to ODIN back to 2.1 to get Android System Recovery "2e", which will let me flash 'update.zip' packages freely. Then I flash an 'update.zip' to get CWM, then flash CM7, then CM9 (and CM9 is my intended destination).
The things mentioned in the thread you linked do appear to apply to my situation.
However I still want to get the stock OS booted and working, then do a Nandroid backup of it. (it's the computer tech/security pro in me. Since I'm new to this device, I -tried- to read up on everything first, and didn't want to make a change without being sure it would work.)
Does anyone happen to know if flashing a stock kernel over the 'cmenard' kernel will harm anything, and hopefully get a successful boot? Again, I'm trying to get the stock ROM booting again in order to verify I have everything I need off of it, then do a nandroid backup. Flashing to CM9 will come afterwards.
Ok, here are some things for you.
Here is a kernel pack that you can use. Read the OP because there are Froyo AND Gingerbread kernels in there.
[KERNELS] Moped_Ryder SGS Kernel Pack v2 [20+ Froyo/GB Kernels]
I really suggest using something like BaliX 1.2 or BaliUV kernels to make your back up. They are smooth, fast and OC/UV-able. To flash just Wipe /cache, /dalvik -> flash kernel -> Wipe /cache, /dalvik (I also fix permissions too bc that is the way that I learned and I just do it that way all the time). Reboot and Bam!! you should be able to get to the point that you can make a backup.
Look in my signature, there are downloads and flashables that are direct download linked. There is also an ICS install guide that can help your journey. Once you have your backup, then use Odin from the Toolbox in my signature and flash back to stock JFD. From there you will be able to follow my guide.
If you need any files, just let me know and I will upload them when I get home (won't be until late though, i have plans right after work).
Using HB, can I choose any theme? I am not so acquainted with the Theme chooser and boot animation of my phone. I flashed a boot animation zip yesterday and it was stuck in "ANDROID" screen. So I have to flash again. I never used any boot animation and themes in my phone yet. I want to know about them.
Sent from my SGH-T959 using xda app-developers app
Wrong thread. Put that question in the Jelly Bean Banter thread. No need to hijack this thread until we get OP up and running.
Ugh, so I've been on vacation for a while, and since being back I've been super freaking busy =(
Finally spent some time with the phone tonight. Took some fiddling to get the right drivers working for the phone on my Win7x64 laptop.
In any case, I checked out that Kernel thread, and extracted the Bali kernel. Since I had flashed successfully(?) with Heimdall at first, and I'm becoming more familiar with it, I used it to flash the Bali_1.8.8-zImage. That appeared to work, as I get a new boot screen/animation with the Bali logo.
However, after the Bali logo disappears, the T-Mobile animation+sound plays, and then gives me a black screen. The screen is on (backlight is on) but all black. Also, if I touch a soft-button, they'll light up and the phone will remain in that state for as long as I can stand to wait. (one episode of Archer)
So, it's doing the same thing as before, but with a new boot logo/animation.
I wonder if something else in the ROM has been messed up? Should I forget trying to save it, and just use ODIN to flash a whole new rom/kernel package? I'll talk to the owner tomorrow and see if he's now willing to do that.
I also wonder if I was wrong to use Heimdall again, instead of using the CWM method. Please correct me if I'm wrong, but I think those two methods end up doing the exact same thing. Is one method more reliable than the other?
Bah, this sucks; I have more questions than answers at this point =( Any ideas, Woodrube, Toast?
maxpeet said:
Ugh, so I've been on vacation for a while, and since being back I've been super freaking busy =(
Finally spent some time with the phone tonight. Took some fiddling to get the right drivers working for the phone on my Win7x64 laptop.
In any case, I checked out that Kernel thread, and extracted the Bali kernel. Since I had flashed successfully(?) with Heimdall at first, and I'm becoming more familiar with it, I used it to flash the Bali_1.8.8-zImage. That appeared to work, as I get a new boot screen/animation with the Bali logo.
However, after the Bali logo disappears, the T-Mobile animation+sound plays, and then gives me a black screen. The screen is on (backlight is on) but all black. Also, if I touch a soft-button, they'll light up and the phone will remain in that state for as long as I can stand to wait. (one episode of Archer)
So, it's doing the same thing as before, but with a new boot logo/animation.
I wonder if something else in the ROM has been messed up? Should I forget trying to save it, and just use ODIN to flash a whole new rom/kernel package? I'll talk to the owner tomorrow and see if he's now willing to do that.
I also wonder if I was wrong to use Heimdall again, instead of using the CWM method. Please correct me if I'm wrong, but I think those two methods end up doing the exact same thing. Is one method more reliable than the other?
Bah, this sucks; I have more questions than answers at this point =( Any ideas, Woodrube, Toast?
Click to expand...
Click to collapse
Wrong they are not the same. cwm can do the work without a PC beside you can erase, back up , restore and flash, which make our life easier, heimdall or Odin ," I prefer odin "are the last option when you can't fix it with cwm
To fix your phone use Odin or heimdall and go back to stock don't worry all your files, photo, music, will be safe. Then
1 get root on you , if you don't how ask
2 get cWm
3 do a nandroid back up
4 have fun flashing all roms you want lol
Sent from my SGH-T989 using xda app-developers app
Yeah, I would just Odin back to stock JFD w/ repartition checked...
Then I'd flash something real stable for him. There are lots of stable ROMs to choose from. I used Bionix V for a long time before moving onto Jelly Bean.
Since the phone belongs to someone else, I'd stick with something lower than JB though. 911 can have/has issues.
Toast6977 said:
Yeah, I would just Odin back to stock JFD w/ repartition checked...
Then I'd flash something real stable for him. There are lots of stable ROMs to choose from. I used Bionix V for a long time before moving onto Jelly Bean.
Since the phone belongs to someone else, I'd stick with something lower than JB though. 911 can have/has issues.
Click to expand...
Click to collapse
do no check de re-partition button and use a .pit file follow this tutorial and you will be fine
http://forum.xda-developers.com/showthread.php?t=848737