Related
Hey everyone.
I recently rooted my Hero GSM phone and tried to play around with some Custom Roms.. I'm currently running FroydVillain with a 691 kernel and I like it a lot, but want to know if there's any other Roms running smoother on the Hero packing Froyo..
I used to have the official eclair (2.1) with launcherpro installed, but wanted to try Froyo out because I heard that it runs 450 % faster than eclair. And since I went over to Custom Roms my batterytime has been lowered significantly..
Also if anyone could tell me what RADIO's are I would be very happy
Sorry for all the questions, but I have just one more..does updating the recovery software help on performance? I have an old version I think.. can anyone please link the newest?
I find the market of available Roms so large and wanted to know if anyone could recommend some Roms and include some links on where to get..
Froyo prefered since I just got used to how it works.
Thanks in advance
Sent from my HTC Hero using XDA App
Hammerbak said:
Hey everyone.
I recently rooted my Hero GSM phone and tried to play around with some Custom Roms.. I'm currently running FroydVillain with a 691 kernel and I like it a lot, but want to know if there's any other Roms running smoother on the Hero packing Froyo..
I used to have the official eclair (2.1) with launcherpro installed, but wanted to try Froyo out because I heard that it runs 450 % faster than eclair. And since I went over to Custom Roms my batterytime has been lowered significantly..
Also if anyone could tell me what RADIO's are I would be very happy
Sorry for all the questions, but I have just one more..does updating the recovery software help on performance? I have an old version I think.. can anyone please link the newest?
I find the market of available Roms so large and wanted to know if anyone could recommend some Roms and include some links on where to get..
Froyo prefered since I just got used to how it works.
Thanks in advance
Sent from my HTC Hero using XDA App
Click to expand...
Click to collapse
Latest Recovery: http://forum.xda-developers.com/showthread.php?t=561124
The radio I recommend is the latest GSM one at http://www.villainrom.co.uk/forum/showthread.php?307-radio-roms-download-links
Are you using latest Froyd, as we've got reports of 2 full days of battery life.
But 450% is an exaggeration, as it's based on a nexus 1 without vs. with JIT. You should get > 5 Mflops though in linpack using froyo.
Regarding the question in the title. You could search around here a little on Q&A since it has been asked a lot of times But mostly you'll get the answer that it's different from person to person and everyone has their favourite ROM for instance my favourite ROM is Cronos (anything) but I'm guessing pulser_g2's would be VillainROM (LOL)
Lol. Yeah it depends on what you want. I mentioned Froyd as you're on it already, but sense 2.1 roms do still exist, though you might try disappointed with performance.
I used a sense rom recently and had to remove it as I couldn't bear the slowness, even with oc.
But yeah, search is your friend. Decide what you want, and you'll find it here.
Thanks for the links.
Yeah well, I spent almost an hour reading about different Roms here and there and I see that it's kinda up to one self what you like about the different Roms. I've been very happy with FroydVillain so far, but I guess I should go ahead and give some of the others a try.
I've just backed up my current phone settings with "Titanium Backup" but is this enough if I decide to try a new Rom and want to go back later on? or should I do a nandroid backup?
And again when I flash over the new recovery.img.. Do I need to backup anything beforehand?
My Froyd version is the latest and I've kept on updating whenever I saw new updates. And yeah, two days is in my opinion not much. Beforehand, on the official 2.1, I could easely tweak 4-5 days out of my standard Hero battery, but I guess this has something to do with the kernel?
Sorry.. I'm really a newbie on this
Hammerbak said:
Thanks for the links.
Yeah well, I spent almost an hour reading about different Roms here and there and I see that it's kinda up to one self what you like about the different Roms. I've been very happy with FroydVillain so far, but I guess I should go ahead and give some of the others a try.
I've just backed up my current phone settings with "Titanium Backup" but is this enough if I decide to try a new Rom and want to go back later on? or should I do a nandroid backup?
And again when I flash over the new recovery.img.. Do I need to backup anything beforehand?
My Froyd version is the latest and I've kept on updating whenever I saw new updates. And yeah, two days is in my opinion not much. Beforehand, on the official 2.1, I could easely tweak 4-5 days out of my standard Hero battery, but I guess this has something to do with the kernel?
Sorry.. I'm really a newbie on this
Click to expand...
Click to collapse
If you want to go back you need a nandroid backup yes. If your talking about updating your recovery image (lol I'm guessing) no you don't. Just flash it. And the battery has something (everything ) to do with the kernel but if you want better battery set you min freq of your CPU lower or you can lower the max freq.
I see..
Thank you very much for answering.
I have just one minor problem..
How the heck do I flash over the recovery image? Don't I use the FlashRec-thingy? Might have deleted it at some point :S
Hammerbak said:
I see..
Thank you very much for answering.
I have just one minor problem..
How the heck do I flash over the recovery image? Don't I use the FlashRec-thingy? Might have deleted it at some point :S
Click to expand...
Click to collapse
I reccomend you flashing Amon-RA. There is a guide in his thread on how to flash it But if you want the ultimate easy noob thing you can download ROM manager from the market which will alow you to download and flash a pretty descent recovery in one click
Yeah.. Flashing Amon-RA is what I'm trying to. It seems I have the 1.5.2 version installed and I just downloaded the 1.7.0 one..
The first time I flashed "Amon-RA" did it with the help of a program called FlashRec. I followed the guide on theunlockr.com and I now end up with a message: "Backup FAILED: Could not run command." when I try to "Backup Recovery Image" through that FlashRec program.
I have an idea of how to work around this but I'm not 100% sure this is what's needed..?
Could I run the phone into recovery mode (through that 1.5.2 Amon-RA thingy) and then flash the never version right onto it or is this the wrong procedure?
Hammerbak said:
Yeah.. Flashing Amon-RA is what I'm trying to. It seems I have the 1.5.2 version installed and I just downloaded the 1.7.0 one..
The first time I flashed "Amon-RA" did it with the help of a program called FlashRec. I followed the guide on theunlockr.com and I now end up with a message: "Backup FAILED: Could not run command." when I try to "Backup Recovery Image" through that FlashRec program.
I have an idea of how to work around this but I'm not 100% sure this is what's needed..?
Could I run the phone into recovery mode (through that 1.5.2 Amon-RA thingy) and then flash the never version right onto it or is this the wrong procedure?
Click to expand...
Click to collapse
Lol thats excatly how I rooted my phone too (same recovery and website even) Look in the thread it's described how you flash the new recovery via ADB
Yeah ehm... I'm kinda new to this so all his "code" or whatever it is doesn't give me a hell lot of clues..
Install
There are several ways to install a custom recovery, choose the one that suits you most (I probably forgot a few).
via adb -> Requires a custom recovery (with test-keys) like Cyanogen's v1.4 or my previous recovery
Code:
Copy recovery-RA-hero-v1.7.0.1.img to the root of your sdcard
Boot into your current custom recovery (boot while holding HOME)
Connect your Hero via usb to your pc/mac/...
adb shell
$su (not required if you have root already)
#mount -a
#flash_image recovery /sdcard/recovery-RA-hero-v1.7.0.1.img
Click to expand...
Click to collapse
I fixed the steps underlined but after that I kinda went cold on what the **** to do :S
I boot into my recovery and what I get from his "guide" is that I my Hero should do something when I plug in the USB cable.. but nothing happends.. anyone who can put it down in baby-steps for me? :O
There's another way to do this it seems (2nd guide in his thread) but it seems to involve even more "code" so I guess I'll settle with this if it's possible.. :S
Hammerbak said:
Yeah ehm... I'm kinda new to this so all his "code" or whatever it is doesn't give me a hell lot of clues..
I fixed the steps underlined but after that I kinda went cold on what the **** to do :S
I boot into my recovery and what I get from his "guide" is that I my Hero should do something when I plug in the USB cable.. but nothing happends.. anyone who can put it down in baby-steps for me? :O
There's another way to do this it seems (2nd guide in his thread) but it seems to involve even more "code" so I guess I'll settle with this if it's possible.. :S
Click to expand...
Click to collapse
For you I would just recommend installing "ROM manager" from the market and then let it install ClockworkMod recovery that should do for you
EDIT: There seems to be an issue with ROM manager at the moment. It wont flash...
Yeah.. Might as well try this out since no one wants to point out on how to it the "geeky"-way
EDIT:
I seem to get an error when trying to flash the ClorkworkMod Recovery.. Any idea why?
Nvm.. Some dude (erasmux) has made an update.zip and uploaded to the Amon-RA post.. it did the trick
I'm one of the unlucky individuals for whom the hardware volume keys to get into recovery don't work. This hasn't been a problem for me so far since it's so easy to root in other ways, and I'd really like to try out CM7.
The CM7 thread specifically says
Make SURE you can get into Download mode using only buttons (no other method, Download mode from just buttons is essential).
Click to expand...
Click to collapse
which base on the red/bold makes me think this is a serious issue... but looking through the installation instructions I can't figure out why. It looks to me like installing CM7 is exactly the same process as the one I've already used successfully to flash Onyx, then Bionix, and now Axura.
What is the reason for this loud disclaimer, does anyone know? Doesn't CM7 now come with Clockworkmod Recovery included so I should be able to use it to get into recovery mode again in the future?
Blindsight51 said:
I'm one of the unlucky individuals for whom the hardware volume keys to get into recovery don't work. This hasn't been a problem for me so far since it's so easy to root in other ways, and I'd really like to try out CM7.
The CM7 thread specifically says
which base on the red/bold makes me think this is a serious issue... but looking through the installation instructions I can't figure out why. It looks to me like installing CM7 is exactly the same process as the one I've already used successfully to flash Onyx, then Bionix, and now Axura.
What is the reason for this loud disclaimer, does anyone know? Doesn't CM7 now come with Clockworkmod Recovery included so I should be able to use it to get into recovery mode again in the future?
Click to expand...
Click to collapse
if your phone breaks (because CM7 is unstable right now) how do you expect to go to another ROM? "adb reboot recovery" won't help you because restoring a nandroid of another ROM won't do *anything*. "adb reboot download" doesn't work so you'll never make it to download mode.
so if your phone suddenly stops working, you're screwed and we're trying to protect people who lack the foresight to think about potential problems. basically, you'll be setting yourself up to be stuck in a very bad position and there's just no reason for it.
Kaik541 said:
if your phone breaks (because CM7 is unstable right now) how do you expect to go to another ROM? "adb reboot recovery" won't help you because restoring a nandroid of another ROM won't do *anything*. "adb reboot download" doesn't work so you'll never make it to download mode.
so if your phone suddenly stops working, you're screwed and we're trying to protect people who lack the foresight to think about potential problems. basically, you'll be setting yourself up to be stuck in a very bad position and there's just no reason for it.
Click to expand...
Click to collapse
Okay, so the reason is due to stability concerns with the ROM, then? That makes sense... but that risk would apply any time I flash my phone with anything, not just CM.
I guess I'll just go back to waiting until a "stable" CM ROM comes out. Thanks for the quick reply, I appreciate it.
Now I know this question, in general, has been asked a lot. I've literally searched and tried the solutions in other threads, but this phone might be beyond help. I just want to know if someone has another solution as to how to revive this phone. I honestly think my situation is different than most....I downloaded and installed Team Hacksung's ICS 4.0.3 Build 6.1 ROM and I was using it just fine for a couple of months. Everything was working the whole time. Today, I am browsing through my local news station's app and my phone freezes on me! I pulled the battery and restarted the phone. It boots up fine and gets to the startup screen with the time and the screen lock. I did notice right away that the digitizer screen was not responding to my touch because I could not slide my lock over to get into my phone. I tried a few more soft resets and still nothing. I did notice, however, that the soft keys at the bottom did respond to my touch and they blinked and provided haptic feedback, so at this point I'm thinking it shouldn't be a problem with my digitizer. So I took the battery out then put the phone into recovery and wiped data, cache and dalvik. Then I rebooted the phone once again and still no response to touch at the home/lock screen. I then proceeded to try to reflash the same ICS ROM all over again and that's where the problem started. I can get into download mode and I've already tried to load stock froyo and stock gingerbread, but nothing works. My phone will not go past the "Samsung" boot-up screen. I've already tried several other forums' threads on how to recover a bricked Fascinate, but no matter what I try to load with Odin, Heimdall or anything else, my phone won't load past the Samsung screen. I can get into Download mode and that's it. My phone will not go into recovery using the 3-finger method. When I run odin I get a success message each time. I've even tried to heimdall the files individually and even tried to reload the stock kernel. The other problem I am running into is a lot of the links on these sites are all broken so I am unable to get the files I need. Has anyone else ever had this problem?
Edit: P.S. When the phone is off and on the charger, the grey battery shows the "loading" circle (whatever you call it) in the middle of it, but never converts to showing the green bars moving up and down indicating the battery is being charged. The loading circle is also frozen and does not spin.
im dizzy after reading a few sentences lol...check out my guide in the general section.
droidstyle said:
im dizzy after reading a few sentences lol...check out my guide in the general section.
Click to expand...
Click to collapse
Are you referring to http://forum.xda-developers.com/showthread.php?t=1238070?
If so, I just did it and it won't go past "Samsung."
Did you do check repartition and use the atlas pit file? That would be key, I believe, in returning you properly to stock.
Droidstyle's guide has all the working links you'll ever need.
http://forum.xda-developers.com/showthread.php?t=1238070
jawman27 said:
Did you do check repartition and use the atlas pit file? That would be key, I believe, in returning you properly to stock.
Droidstyle's guide has all the working links you'll ever need.
http://forum.xda-developers.com/showthread.php?t=1238070
Click to expand...
Click to collapse
I did check re-partition and yes I did load the atlas pit file. Still nothing.
e
So you tried heimdall? What commands did you do? and what rom?
also which links were dead that you needed?
mvmacd said:
So you tried heimdall? What commands did you do? and what rom?
also which links were dead that you needed?
Click to expand...
Click to collapse
I used heimdall front end to load DI01 files, I didn't use any commands. Also, I was just referring to "Unbrick your samsung fascinate" threads on other websites. A lot of the links I found were outdated or broken.
yea unfortunately not many guides have working links these days...Mine is about the only one left that is kept up to date. Im very suprised a full odin session did not fix your issues. One thing left to try is to odin a older stock package like DL09
Found here:
http://forum.xda-developers.com/showthread.php?t=1526488
Just tried pushing the DL09 file in odin AND in heimdall and neither worked. I still get stuck on the "Samsung" boot and it goes no further. Can't even get into recovery....
I think I truly have a brick...
kinna long shot
but why not try a different PC and a new or different cable.
believe me a faulty cable did me in, a week back and i was sure at the time that my phone is gone, but then it wasn't as bad as the impression i am getting from your description.
all the best with this , and hoping that something solves this issue.
god bless
haoleflip said:
Now I know this question, in general, has been asked a lot. I've literally searched and tried the solutions in other threads, but this phone might be beyond help. I just want to know if someone has another solution as to how to revive this phone. I honestly think my situation is different than most....I downloaded and installed Team Hacksung's ICS 4.0.3 Build 6.1 ROM and I was using it just fine for a couple of months.....
Click to expand...
Click to collapse
I am having a similiar problem now. I was able to odin an older CWM (3.0 blue I got somewhere). From there I mounted usb and loaded ext4_formatter_all.zip. I ran this script and odin'd dh03 and finally got back to stock. That's where I am now.
Hope this helps
kduffman said:
I am having a similiar problem now. I was able to odin an older CWM (3.0 blue I got somewhere). From there I mounted usb and loaded ext4_formatter_all.zip. I ran this script and odin'd dh03 and finally got back to stock. That's where I am now.
Hope this helps
Click to expand...
Click to collapse
I have a blue recovery [3.x, voodoo], here it is if the OP wishes to try it.
[Use Heimdall and select recovery]
cwm3_voodoo-blue.bin http://www.mediafire.com/?4ls06x8gha88vtp
cwm4-bml-i500-fascinate.bin http://www.mediafire.com/?2ny1ql66yh69bn3
35c31418dbe9a9db70de954cdf7369ef cwm3_voodoo-blue.bin
05f3e376ca697fd0fb8700dea05254aa cwm4-bml-i500-fascinate.bin
I threw in an extra 4.x cwm for good measure, lol. [I saved these in a folder in case I ever needed them..I was going to delete the folder since I upgraded to THS ICS rom (build 7.1), but I decided not to delete them for some reason]
it seems OP sounds like he knows what he is talking about, but lets start simple.
Have you tried going all the way back to 100% stock?
In droidstlyes FANTASTIC guide
do section 5, perhaps try with out repartition or the atlas....that has worked for me in the past.
I know on my THS ICS 7.1 build i had a "sleep of death" (wouldnt wake up) and i was lazy and did the 3 finger salute and it would ONLY boot into CWM. a battery pop would have been fine but like i said i was lazy. i had to Odin back to stock in order to re-flash everything. [luckily i had a nandroid from a few days earlier]
Good Luck
Edit: I have never seen or heard of a fassy that CAN get into Download mode and not be recovered to 100% functional.
I'm just thinking out loud here, but here are two things to consider. Perhaps the senior members will comment.
1. Have you considered flashing a different bootloader?
2. Is it possible you have a corrupt stock and/or pit file? Have you tried re-downloading them and giving it another go?
OP, can you post the md5sums of the files, along with the filenames that you are using in Odin/Heimdall?
thanks
Well, I ended up getting a droid bionic from a friend, so I will turn this fassy into a project phone. If I can get it to work I will sell it or keep it for backup. Anyway...
I have not tried the older blue recovery yet. I will try that when I get back to my computer. It seems like I've gone beyond anything I've ever had to try with this phone. I read on one thread that if odin did not work, keep trying heimdall over and over until the phone boots up. I must have tried at least 8 times on one run. It still won't go past samsung screen. I can get into download just fine. No matter how many different cwms I try, I can't get into recovery using the three finger method. Im pretty knowledgeable when it comes to this stuff and I didn't flash the wrong rom or kernel or anything like that. I was running smoothly on an ics rom until my phone froze. I did have it overclocked with ns tools, but not at the time the phone froze. I honestly don't think its hardware related, but merely a glitch in the software or a bad kernel that does not want to come out? I have no clue....help me revive this baby lol...
Sent from my DROID BIONIC using Tapatalk
jawman27 said:
I'm just thinking out loud here, but here are two things to consider. Perhaps the senior members will comment.
1. Have you considered flashing a different bootloader?
2. Is it possible you have a corrupt stock and/or pit file? Have you tried re-downloading them and giving it another go?
Click to expand...
Click to collapse
I've tried different pit files from different threads. Even the one from droidstyle's thread. I've also tried different versions of the following stock files from different "known" and trusted sites: DI01, DL09, ED01, EB01, EH03, CM7, CM9 other ICS roms and different kernels that suit each both voodoo and non voodoo. And excuse my newbness on the terms, but what do you mean by flashing a new bootloader?
Sent from my DROID BIONIC using Tapatalk
haoleflip said:
... but what do you mean by flashing a new bootloader?
Sent from my DROID BIONIC using Tapatalk
Click to expand...
Click to collapse
Bootloaders can be flashed in Odin the same way a ROM can. A bootloader is the rudimentary software that gets the other software up and running. When Glitch's kernel started requiring Gingerbread bootloaders for complete functionality, a lot of us realized that just having GB didn't mean you had GB bootloaders.
http://www.mediafire.com/?fqojvsynkff93hc
Hopefully this link will work. It's certainly worth a try. It doesn't seem like you have much to lose. I'd recommend flashing it the exact same way you do a ROM. There's a bootloader section in Odin, but most people avoid it. Good luck.
Hello, at the start i wanted to install some new ICS rom for my Vibrant..i try to root it with one click and i couldn't do that coz i had froyo(2.2update)..so i read some forums and found solution in odin...i used that to turn back to stock eclair where i rooted the phone ...but the problem is that now i can't install any application on the device(i need ROM manager)..i get to android market and ,click on application but nothing is happening, no download at all...than i try to use android injection with apks that i found on the net , but nothing, i always get INSTALL_FAILED_OLDER_SDK...so now i am stuck i have: fimware version-2.1 update 1,baseband T959UVJFD, kernel 2.6.29 can you tall me should i do?? thx
Read the guide in my signature on how to install ICS ROMs. It has an update.zip that you can use for CWR.
ROM manager no longer supports 2.1 (Eclair), so that is why you can't see it in the market.
Download the clockwork mod recovery file (update.zip) and save it to the internal storage on the phone. Then reboot into recovery and install packages. Might have to do it twice. Then you'll be in CWM recovery. Install from from there.
Sent from my SGH-T959 using XDA
The AIO Vibrant toolbox might be something you need to look at. you can find it here http://forum.xda-developers.com/showthread.php?t=954509
guide
i followed your guide...flashed CM7, than i try to flash Euphoria RM2.1(ICS) and flashing is starting all ok , than after 30 secs i see message 'Random offset 0x302' and it's not going forward with flashing,i pulled out battery and try 2 more times,and there is always the same problem, i'm on CM7 now(and i don't have google play what should i do? can you recoommand me some good and stable gingerbread ROM for Vibrant(if i goona be unable to install ICS Rom) thx
Woodrube said:
Read the guide in my signature on how to install ICS ROMs. It has an update.zip that you can use for CWR.
ROM manager no longer supports 2.1 (Eclair), so that is why you can't see it in the market.
Click to expand...
Click to collapse
FWIW, and this is not a knock on Team Passion (they do excellent work but few updates), but Euphoria is somewhat outdated. There are plenty of ICS ROMs out there that are more up-to-date and when ICS went from 4.0.3 to 4.0.4 there were significant code changes that were done. I suggest ICZen, or Slim or CM9.
But if you want to stay on Euphoria (AOKP based), this is from my guide:
If you get the RANDOM OFFSET error.
Don't freak out. This is an ICS security feature (as posted in Passion's FAQ post). All you have to do is pull your battery and boot back into recovery and reflash ICS over itself (just like you did with the initial CM7 bootloop) and it should push through. You may need to do this multiple times. I have read of people having to do it up to 5x. YMMV though.
Click to expand...
Click to collapse
Edit:
***----> I am having all kinds of trouble with my browser today at work, so if I don't respond right quick, that is why. But I'll get back to you or some others out there can help.
stack
man, now i am completly stack, i try to flash slim ics, found the file for vibrant, but it culdn't flash , in the middle it just stoped..and phone is just rebooting it self when i enter cw mod i can't install any other ROM from internal sd, it says no files found ffs now i can't even use phone, i need help emergently
Woodrube said:
FWIW, and this is not a knock on Team Passion (they do excellent work but few updates), but Euphoria is somewhat outdated. There are plenty of ICS ROMs out there that are more up-to-date and when ICS went from 4.0.3 to 4.0.4 there were significant code changes that were done. I suggest ICZen, or Slim or CM9.
But if you want to stay on Euphoria (AOKP based), this is from my guide:
Edit:
***----> I am having all kinds of trouble with my browser today at work, so if I don't respond right quick, that is why. But I'll get back to you or some others out there can help.
Click to expand...
Click to collapse
I suggest you Odin immediately. I fear that the next screen you will see is the Encryption Unsuccessful screen. Make sure you hit repartition in Odin though since you reformatted your system from RFS/Ext4 to MTD when you went to CM7.
odin
ok i get into odin , marked repartiton but is sais fail ??? what should i do now?
Woodrube said:
I suggest you Odin immediately. I fear that the next screen you will see is the Encryption Unsuccessful screen. Make sure you hit repartition in Odin though since you reformatted your system from RFS/Ext4 to MTD when you went to CM7.
Click to expand...
Click to collapse
If you do get past all of these, but this is unlikely for a normal flash, get either Iczen or chimera.
Sent from my SGH-T959 using xda app-developers app
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