[q] please help me!!! - Fascinate Q&A, Help & Troubleshooting

i have a samsung fascinate on verizon. now i used to have fun with roms and themes and what not on my phone.... since the update of the clockwork mod, it has been impossible. i have tried everything, amend2edify programs, odin, and every superclean rom seems to have the same thing, nothing differs and my phone goes right back to a new superclean rom i used and it is impossible to theme it or do anything different other than use it. this is boring and extremely frustrating. with no customization, what good is the phone?
if it helps.. my firmware is 2.2.1 / eb01 / dl09
im lost. everytime i try to flash anything from cwm i get an error, it takes my phone 4 mins to boot and then nothing. every time!
I know i am rooted successfully, seems once they switched from amend scrpts i lost my talent? and the cwm i have is orange screen (latest one dl from market and flashed) and i STILL boot to blue recovery and have to run update.zip to get to orange, without fail every time. it will not load on its own when i boot to recovery. crazy. maybe i am missing something here? someone please help me!
thank you.

phil4c said:
i have a samsung fascinate on verizon. now i used to have fun with roms and themes and what not on my phone.... since the update of the clockwork mod, it has been impossible. i have tried everything, amend2edify programs, odin, and every superclean rom seems to have the same thing, nothing differs and my phone goes right back to a new superclean rom i used and it is impossible to theme it or do anything different other than use it. this is boring and extremely frustrating. with no customization, what good is the phone?
if it helps.. my firmware is 2.2.1 / eb01 / dl09
im lost. everytime i try to flash anything from cwm i get an error, it takes my phone 4 mins to boot and then nothing. every time!
I know i am rooted successfully, seems once they switched from amend scrpts i lost my talent? and the cwm i have is orange screen (latest one dl from market and flashed) and i STILL boot to blue recovery and have to run update.zip to get to orange, without fail every time. it will not load on its own when i boot to recovery. crazy. maybe i am missing something here? someone please help me!
thank you.
Click to expand...
Click to collapse
I believe u need to odin a stock rom/kernal/radio package before switching roms. Look up the official verizon ed05 pacakage in the development section. Also read the stickies in there aswell.
Odin ed05.tar w/ pit
Boot up once
Odin cwm that's required by rom
Boot into recovery
Wipe data
Install rom.zip

i am trying this now. thank you in advance!

ok now, forgive me for sounding like an idiot (cuz i am) when you say odin cwm required by rom, am i sideloading cwm basically thru odin? and where would i find a download for cwm? im stock ed05 across the board now. thanks!

phil4c said:
ok now, forgive me for sounding like an idiot (cuz i am) when you say odin cwm required by rom, am i sideloading cwm basically thru odin? and where would i find a download for cwm? im stock ed05 across the board now. thanks!
Click to expand...
Click to collapse
yep here ya go
http://dl.dropbox.com/u/25089906/cwm-recovery-ALL.tar
odin this after you have booted up on ed05 once
boot into cwm by holding both volume up/dow and power buttons until the samsung logo appears twice
wipe data
install powerwashED05.zip from sd card
reboot and enjoy your rooted/debloated/de touchwized/ deodexed/zip aligned rom!

thank you for all of your help. i am now back to enjoying my phone everything works perfect and it is just the way i want it. now all i need to do is start to keep up with the changes so i dont lose track of how to do stuff.
thanks again!

Glad that it worked...enjoy!

Related

Can't figure it out.

Tried to flash a custom ROM for the 15th time or so, with the same result. E: Can't Symlink /system/bin/su
Failure at line 16
Have researched this error, thought I had it figured out. Obviously not. Feel like an idiot. I never had any problems loading custom ROM's on 2.1.
BTW, I am rooted thru S1Click, have backed up thru nandroid and Titanium, have installed 3e custom recovery, everything I have read I could be doing wrong I have changed. I have tried different makers- Bionix, Axura, Eugene, all with hte same errors, so I know it's not just the ROM file.
What am I doing wrong here?
I don't know.. but let's save everyone the trouble of answering this and let you odin back to stock.
It might be something you flashed etc..
tried that too. tried loading these ROM's right after rooting and adding ROM manager. It's just weird that know one can answer a specific problem like "failure at line 16". Surprised there isn't an answer to look up based on the Line 16 error.
I'm not pointing any fingers, because I don't know the answer either. Just know that if you you give me one of the basic replies, like try ODIN to stock, I've probably tried it.
What are you odining to? I've always had success going to back to jfd. Doesn't seem to be any issues with rooting or rom manager.
Trigger + Overstock = Awesomeness
yep. Odining to jfd.
One thing is that I always install 2.2 via mini-kies before attempting to install custom ROM. Reason being that for whatever reason, the super one click just does not want to install on 2.1. Could that be part of the problem?
Here's what I do and it works every time for me.
1. Odin to jfd
2. Root then install rom manager
3. Flash clockwork recovery
4. Download rom of choice to internal sd
5. Flash rom thru clockwork
6. Enjoy
That has never failed me.
Trigger + Overstock = Awesomeness
Check This Out....Tell me If It Helped You
http://forum.xda-developers.com/showthread.php?t=848737
I did it. FINALLY.
Loaded Simply Honey 2.5, and this thing is FAST and awesome. Such a cool ROM. I was so pumped when it actually worked. Thanks for all the help, guys. And all the great developers that put in hte time and work to make our phones what they should be. Good job, guys.
Glad you got it working. The first flash is pretty awesome.
Trigger + Overstock = Awesomeness
I had this happening yesterday, find and Odin Eugene's froyo that doesn't brick, followed by a stock Odin flash with checking repartition the second time to fully clear the problem, or it will happen again probably the next time you go to flash a rom.
Sent from my Loki powered Vibrant via the XDA App
Br1cK'd said:
I had this happening yesterday, find and Odin Eugene's froyo that doesn't brick, followed by a stock Odin flash with checking repartition the second time to fully clear the problem, or it will happen again probably the next time you go to flash a rom.
Sent from my Loki powered Vibrant via the XDA App
Click to expand...
Click to collapse
This is the safest way and the best way.

[Q] Need help getting a custom ROM, cant get passed E3 to use clockwork

Hi, Ok, so I am new at this and I have a samsung galaxy vibrant on tmobile...i got it and it was running eclair 2.1, I figured out how to root it and then upgraded to froyo 2.2. Now I am wanting to get either Bionix ROM or Nero V3. I have followed all the steps, got rommanager, did the flash clockworkmod recovery, dowloaded the zip file and put it in the root of my sd, but when i go to reboot, it wont run as clockwork, no matter how many times i try!
I read that it is because 2.2 has recovery e3 and i need e2...so it says t download a kernal that contains clockwork recovery but the problem is i cannot find one. I can find stuff all day long about the galaxy I9000 but nothing on the vibrant!
I have Odin and was wondering can I flash the rom straight to the phone?
My model number is SGH-T959, Kernel is 2.6.32.9, and build is FROYO.UVKB5.
Please help me, I really have no clue what I am doing, I just want my phone to run fast, get a nice looking theme for it, and not have to worry about it messing up and from what i have read the only way to that is to get a custom ROM and the only way to get themes is thru a custom ROM....
So if anyone can tell me how to go about getting my phone to recover using clockwork and any links i need to download the stuff I would greatly appreciate it! Thanks!!!
Just bricked my phone i think!!!
Ok so i just followed all of the directions on this sight on how to do it, i backed up my apps with titanium then put my phone in download mode with odin and tried to flash the kernal for my phone to upgrade it and on odin it just said on the screen part, modem, it was green and nothing else happened so i unplugged it because it wouldnt reboot even after waiting a while (10min) and then the screen just showed a broken link between phone and comp and wouldnt change, so i looked at how to restore it with odin and did that and now it will go to the download screen again but nothing else! PLEASE HELP!!!!
follow this guide it will solve all your problems press the thanks button

Questions from a Vibrant newb

Hello, all!
I've purchased a vibrant for my wife over the weekend (i'm on sensation), and have several questions.
The guy i bought it from did a hard-reset supposedly, and said that it reverted it back to the stock android build. Seemed weird, but the first thing i did was update it via kies mini to the froyo build. It's been working fine, except for the camera started messing up last night. Going into black screens, showing "camera failed" errors. It also takes some time (2-3 secs of black screen) to process a picture after it has been taken. I don't remember it doing that on the stock build. I did update it to the latest firmware.
Should i root the phone and flash a different rom? (which rom would you recommend?) A short google search revealed a lot of people having slow-downs after the froyo update.
Appreciate your help!
just to follow-up. wife's been having problems with the music player app hanging, then the phone shut down while she was installing something.... i'm going to wipe everything first to see if it helps any, but will end up rooting it and flashing something else, most likely.
Before rooting make sure you odin back to stock 2.1. That should het rid of the problems
Sent from my SGH-T959 using xda premium
Definitely do what the above poster suggested. Go to the development section and get the AIO toolbox. It has everything you need to get back to stock and get you rooted. If your looking for a good stable rom I'd recommend bi-winning v3. Good luck.
thank you, guys! ended up using the aio toolbox, like suggested. smooth sailing
i've put ultimate rom on it for now, see how she likes it. i'll check the bi-winning (lol) one also. anything else that you'd recommend for now? thank you!
WORD OF IMPORTANT CAUTION!!!!
DON'T EVER USE KIES AGAIN OR YOU WILL BRICK THE PHONE!!! THIS IS A GIVEN, YOU JUST GOT LUCKY, BUT ITS LIKE PLAYING RUSSIAN ROULETTE!! And when it corrupts the Primary and Secondary Boot loader files you'll be bricked hard for sure!!!
KIES IS NOTORIOUS FOR BRICKING VIBRANTS, IT DID IT TO MY PHONE AND MANY OTHERS HERE!! I WAS NOT AWARE OF THIS UNTIL IT WAS TOO LATE FOR ME!!
Odin or Heimdal are the only programs I would use to do restores other than Baywolfs AIO which is very friendly and has the JFD Rom in it and the Mapping Pit file known as the 512.
You could also use Eugenes No brick Froyo using Odin which has the 2E update file in it, so when you root it and Flash CW recovery, and then re-install packages it will give you the 2E green recovery menu you'll need to successfully flash other ROMS in the future you want.
RussianBear said:
thank you, guys! ended up using the aio toolbox, like suggested. smooth sailing
i've put ultimate rom on it for now, see how she likes it. i'll check the bi-winning (lol) one also. anything else that you'd recommend for now? thank you!
Click to expand...
Click to collapse
Theres a GB ROM out by Hercules that is a Galaxy S II port...its pretty sweet
dseldown said:
WORD OF IMPORTANT CAUTION!!!!
DON'T EVER USE KIES AGAIN OR YOU WILL BRICK THE PHONE!!! THIS IS A GIVEN, YOU JUST GOT LUCKY, BUT ITS LIKE PLAYING RUSSIAN ROULETTE!! And when it corrupts the Primary and Secondary Boot loader files you'll be bricked hard for sure!!!
KIES IS NOTORIOUS FOR BRICKING VIBRANTS, IT DID IT TO MY PHONE AND MANY OTHERS HERE!! I WAS NOT AWARE OF THIS UNTIL IT WAS TOO LATE FOR ME!!
Odin or Heimdal are the only programs I would use to do restores other than Baywolfs AIO which is very friendly and has the JFD Rom in it and the Mapping Pit file known as the 512.
You could also use Eugenes No brick Froyo using Odin which has the 2E update file in it, so when you root it and Flash CW recovery, and then re-install packages it will give you the 2E green recovery menu you'll need to successfully flash other ROMS in the future you want.
Click to expand...
Click to collapse
Wow, didn't know this. Will delete kies asap. btw, this rom that i've flashed has a custom kernel (bionix? + voodoo). i did a backup of the stock rom via recovery. do i need to flash the stock kernel first before rolling back to stock?
hereeny said:
Theres a GB ROM out by Hercules that is a Galaxy S II port...its pretty sweet
Click to expand...
Click to collapse
thank you, will check it out!
Project-V is a Great 2.2 ROM, I made a few themes for it too: Blar and WP7 Style

[SOLVED]Cannot install ICS ROM--please HELP

hi,
I am sorry if this is a dumb question. But i have failed several attempts while shifting to ICS (RC 5 by team-nyx). Every time when i install ROM & kernel via CWM and boot the device (vibrant t959) it freezes on the screen with VIBRANT and SAMSUNG displaying WHITE on BLACK back ground.
i have gone back to JFD and tried several times BUT same result.
I was on froyo 2.2 (build UVKB5) updated via kies and did it but no luck. I followed wiki.cyanogenmod.com/wiki/Samsung_Vibrant:_Full_Update_Guide and did starting from No. 03 --
downloaded Cmenard's Kernel with the ClockworkMod Recovery 2.5
Heimdall Suite 1.3.2 for windows
AND upto No. 9 under Windows ONLY: section
the CWM installs as it says (A blue transfer bar will appear on the phone showing the kernel being transferred. The device will reboot automatically. )
after that i cleared factory, cache and dalvik cache.
then I select install Zip from SD card and chose the ROM (which is from team-nyx.com/index.php/releases).
after 3% it says rebooting and vibrant shuts down and reboots.. when after I clicked the combo (vol+vol-power) to enter the CWM its not there.. so I reinstall using [heimdall flash --kernel zImage] command in PC's cmd. then after i redid the same to select from SD and then ROM installed ok.
then I selected the kerenel which was taken by same source and installation went normal..
after I select reboot from CWM it reboots and hangs on vibrant screen.
I cannot figure OUT WHAT IM doing WRONG..
Please HELP ME..!!!
thank you for your time
I am moving to 2.2 via kies after going back to stock JFD. then i will root my vibrant. after that i will install ROM manager from market. THEN i will try to FLASH to ICS RC 5 + kernel from nyx TEAM.
I dont know what is wrong.. please HELP
From what you told us it sounds right. Have you tried a different ICS rom? Give ICS slim a try. When you Odin back did you checked re-partition?
Sent from my SGH-T959 using Tapatalk 2
You should try flashing the Gingerbread bootloaders using Odin after you flash back to stock. Those bootloaders can run a Froyo ROM as well as ICS so it wouldn't hurt to do either way. After you flash the bootloader then try flashing the ROM.
And try a different ROM like iwillkillyou suggested. Slim is good, but ICZen is very solid if you're tipping your toes into ICS.
iwillkillyou said:
From what you told us it sounds right. Have you tried a different ICS rom? Give ICS slim a try. When you Odin back did you checked re-partition?
Sent from my SGH-T959 using Tapatalk 2
Click to expand...
Click to collapse
hi,
thank you for the reply. No i havent tried a different ROM. yes I checked repartiton when ODin Y this is happening.. I have Flashed this ROM once.. but then when someone calls me they cudnt hear me clearly.. when i initiate the call its ok.. so I moved back to JFD..:/
kaiser_bun said:
You should try flashing the Gingerbread bootloaders using Odin after you flash back to stock. Those bootloaders can run a Froyo ROM as well as ICS so it wouldn't hurt to do either way. After you flash the bootloader then try flashing the ROM.
And try a different ROM like iwillkillyou suggested. Slim is good, but ICZen is very solid if you're tipping your toes into ICS.
Click to expand...
Click to collapse
thank you for the reply.. I jz finished Updating to 2.2 via kies..ok I will flash Gingerbread bootloaders using Odin. I will try I think it wont be necessary to ROOT the vibrant..to Flash Bootloaders.. I am going to Flash the ICS ROM via ROM manager (after rooting via SuperOneclick root2.3.3)..
haarsh said:
thank you for the reply.. I jz finished Updating to 2.2 via kies..ok I will flash Gingerbread bootloaders using Odin. I will try I think it wont be necessary to ROOT the vibrant..to Flash Bootloaders.. I am going to Flash the ICS ROM via ROM manager (after rooting via SuperOneclick root2.3.3)..
Click to expand...
Click to collapse
Just so that you know, everytime you are using Kies, you are running the risk of hardbricking your device. It is notorius for that and in fact someone last week got HBricked with it.
I don't use ROM Manager and probably won't as long as I have a Vibrant. All you need to do is go back to JFD and pull the CWR from my signature and put it on your internal_sd and label it as Update.zip. Then boot into recovery and hit Reinstall PAckages (might have to do this twice) and your stock recovery (blue) will go to CWR (green) and you can flash away.
Also for more detailed instructions, se my ICS install giude also in my signature.
Woodrube said:
Just so that you know, everytime you are using Kies, you are running the risk of hardbricking your device. It is notorius for that and in fact someone last week got HBricked with it.
I don't use ROM Manager and probably won't as long as I have a Vibrant. All you need to do is go back to JFD and pull the CWR from my signature and put it on your internal_sd and label it as Update.zip. Then boot into recovery and hit Reinstall PAckages (might have to do this twice) and your stock recovery (blue) will go to CWR (green) and you can flash away.
Also for more detailed instructions, se my ICS install giude also in my signature.
Click to expand...
Click to collapse
Thank you for the links.. I downloaded and place CWR inside SD. Without kies can we install official releases via Odin.. is there any way.. im sorry if that is a stupid question
No stupid questions. That is why we are here. I am pretty sure there is a flashable 2.2 stock floating aroung here. I personally don't have it though. Custom 2.2's are at this point tweaked so completely out, that they will blow the doors off any 2.2 stock ROM out there. I usggest Moped_Ryder's ROMs and Fishman's Bionix-redux ROMs. Quality, fast and stable. Not ICS, but everything works and no fear of the dreaded Encryption Bug.
PM incoming btw.
Woodrube said:
No stupid questions. That is why we are here. I am pretty sure there is a flashable 2.2 stock floating aroung here. I personally don't have it though. Custom 2.2's are at this point tweaked so completely out, that they will blow the doors off any 2.2 stock ROM out there. I usggest Moped_Ryder's ROMs and Fishman's Bionix-redux ROMs. Quality, fast and stable. Not ICS, but everything works and no fear of the dreaded Encryption Bug.
PM incoming btw.
Click to expand...
Click to collapse
thank you. btw can we Flash to 2.2 via CWM .. directly selecting the ROM from SD .. without Odin
If you can find it, you should be able to. Just put on your card and flash away, taking care to wipe accordingly.
A note on flow though:
2.1, 2.2 -can go into and out of any 2.2 there is laterally.
2.3-4.0 -will need to Odin to stock before going back to a 2.2 ROM. Can move laterally from 4.0 to 4.0 though.
(i.e DO NOT try to restore a 2.2 nandroid or flash a 2.2 ROM when you are on an ICS variant. the /system is completely changed and reformatted. You need to Odin to get it back.)
Moped Ryder uploaded a semi tweaked version of the stock 2.2 build. It's a zip that you can just flash using CWR:
http://forum.xda-developers.com/showthread.php?t=1674519
It comes rooted with busybox and some other goodies, but it's the stock kernel and whatnot. I'd highly recommend Fishman's Bionix-V Mod or Moped Ryder's Slim_Ryder ROMs if you're going to be on Froyo though. They're both great, but I went with Fishman's latest Bionix Mod since I couldn't get bluetooth to work on Moped Ryder's ROM. Which is really unfortunate because I loved Moped Ryder's otherwise.
And you don't have to Odin back to stock if you're just bouncing around Froyo or Eclair builds; only if you're coming from Gingerbread or ICS (2.3 or 4.0).
Keep us updated. I'm curious to see what worked. It's probably the gingerbread loaders. But, who knows.
Sent from my SGH-T959 using Tapatalk 2
Is your Samsung Vibrant (T959) Rooted.?
iwillkillyou said:
Keep us updated. I'm curious to see what worked. It's probably the gingerbread loaders. But, who knows.
Sent from my SGH-T959 using Tapatalk 2
Click to expand...
Click to collapse
hi.. I tried again with flashing semaphore kernel through Odin installed CWM version higher than 2.5 to install ICS RC5 by nyx --sorry i need that soo badly so didnt checked anything else ..
@that time I was on vibrant 2.2 UVKB5 (stock)
NOT rooted
I didnt had so called
bootloaders
Click to expand...
Click to collapse
(i dunno what it means though--have to search )
BUT it didnt worked for me instead freezes at Vibrant start-up screen. So i Couldnt switch back to CWM. I Odin back to JFD with repartition clicked and my vibrant was locked (network lock). Finally, I got it cleared by application named Galaxy_S Unlock by Helroz from the market.
Now I am at the very beginning again. I am now on 2.1 JFD. I dont know WHY this happening to me .. :crying:
gonna try again with GB bootloaders.. BUT Im sick of failing and going back to 2.1 (my friends who are having captivate had no problem)
Speedy5150 said:
Is your Samsung Vibrant (T959) Rooted.?
Click to expand...
Click to collapse
At the time i was trying it was NOT rooted.. But now i have it rooted because i needed to unlock the network . which happened me for the very first time after flashing back to JFD using Odin..
Thank you guys for the links and thoughts on 2.2 ROMs.. I am not that expert . Thats why i was updating to 2.2 via KIES -- which is not a good idea as it seems with the ability 2 brick the device. I am going to get Bionix-V FishmanMod V4 FULL and install as http://forum.xda-developers.com/showthread.php?t=1441976 says..
It says Boot into clockwork recovery and i think i found something to do that in this thread http://forum.xda-developers.com/showthread.php?t=734164
I have to get ROM manager from market and go through it..
BUT Im damn upset with the RC5 ICS update by nyx being unable to installed into my device.. I will try with GB bootloaders flashed ..
If you are going to go with Fish's ROM, then all you need to do is Odin back to JFD and pull the CWR from my signature and put it on your internal_sd and label it as Update.zip. Then boot into recovery and hit Reinstall Packages (might have to do this twice) and your stock recovery (blue) will go to CWR (green) and you can flash away.
Fish also has a Odin package that you can flash his ROM through Odin and not have to deal with CWR.
ROM Manager is no longer supporting 2.1, so if you do go back to JFD, then it will be hard to get RM. It is out there somewhere but really all you need is the Update.zip from above to do it. I suggest that you stay on Fish's ROM for awhile and read about ICS installs and all the little things that are involved. If you do flash Fish's ROM, you don't need to mess with the bootloaders.
Btw, aside from Kies, messing with Bootloaders is one of the sure fire ways to hardbrick your device. It only takes seconds to flash them, but do it wrong and, well you know.
Good luck and ask if you have any.
Woodrube said:
If you are going to go with Fish's ROM, then all you need to do is Odin back to JFD and pull the CWR from my signature and put it on your internal_sd and label it as Update.zip. Then boot into recovery and hit Reinstall Packages (might have to do this twice) and your stock recovery (blue) will go to CWR (green) and you can flash away.
Fish also has a Odin package that you can flash his ROM through Odin and not have to deal with CWR.
ROM Manager is no longer supporting 2.1, so if you do go back to JFD, then it will be hard to get RM. It is out there somewhere but really all you need is the Update.zip from above to do it. I suggest that you stay on Fish's ROM for awhile and read about ICS installs and all the little things that are involved. If you do flash Fish's ROM, you don't need to mess with the bootloaders.
Btw, aside from Kies, messing with Bootloaders is one of the sure fire ways to hardbrick your device. It only takes seconds to flash them, but do it wrong and, well you know.
Good luck and ask if you have any.
Click to expand...
Click to collapse
thanks alot for the info brother.. some guys told me STUPID.. but YOU guys are awesome.. I am a newbie to this flashing and stuff.. but learned a lot from XDA . Thanks again for the reply. now I have stock 2.1 with ROOT . (rooted cuz i had to unlock the vibrant). I will flash to Fish's 2.2 ROM soon. BTW may i ask you after moving to Fish's ROM and later if i need to move to ICS still can I do it without messing with Bootloaders..
Thank you
That is what we are here for in the Q&A/General sections.
Regaring your question about Gingerbread bootloaders being needed:::Yes and No.
Gingerbread bootloaders were required in the infancy of ICS ROMs bc they prevented what is called "Rainbows" in your clockwork where you couldn't see anything. The options were there but you just couldn't see them. Then as ICS evolved, the need for GB bl's lessened and now you don't need them at all.
But...There's always a but...Gingerbread bl's are recommended by most of the devs for ICS builds because they seem to work better with the custom recoveries that come with some of the kernels. There is more to it but in short, GB bl's are not required but recommended.
If you go to my ICS install guide, in the middle pages and more again at the end, Yosup (highly respected user) and I have a detailed conversation about bootloaders and their installation. Once he got over the fear and did it, he was hooked and flashing ICS ROMs weekly if not more. It is a very informative section of that thread.

Q: blank screen after T-Mo splash animation, possible to fix without wiping?

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

Categories

Resources