Related
Hello all,
Some time ago, i decided to try and root and put in a custom rom on my htc hero, i followed a guide from this forum and it worked, no problems what so ever.
i flashed the floyo 1.something rom, and had it on there for a few days, maybe a week then one day after work i forgot to charge the phone so it ran out of power.
when i hooked it up to the the usb for charging and turned the phone on, it said Safe Mode in the lower left corner. i was kinda like 'what'?
so i did some searching and found out it might have entered safe mode cause of one of the buttons being held down while i was powering it on, so i tried turning it off and on, and not holding and holding differnet buttons, and eventually i got it out of safe mode, not allways with the same key combo, but then i noticed it starting have a bad battery life, about 10 hours on a full charge.
so i found a guide and put stock rom on it, and everything worked again, good battery life etc, and i did the ota, and got back to how it was before i started playing with custom roms.
i had it running for a few days like that, and decided to try the villain rom, i got recovery flashed, the rom flashed, and boom it was in safe mode again.
i was like even more 'what!?'
and the bad battery life was back too, so i tried some stuff, tried another rom, same deal, tried going back to stock rom, using the ruu files i find on here, and from then things went really wierd.
went back to stock rom, everything seemed to work, did the ota, to get newest upgrades, and in stock rom with ota updates the safe mode returned, i couldnt suddenly install apps from the market, or anything. i used to be able to do that in safe mode in the custom roms.
after a few days of trying stuff, i was finally able to get the recovery flashed, and villainrom back on there, cause i like that one the best, but the safe mode persists, and no matter what i try i cant get the safe mode to go away.
i did alot of searching on the web, and different forums and on this forum, but i cant find any clues to how i can fix this.
only time i can get it out of safe mode, and run normally
is if i apply this
RUU_Hero_HTC_WWE_1.76.405.1_R3_WWE_release_signed_NoDriver.exe
any help would be greatly appreciated.
ps. yes i dont really know what i am doing.
I have a fascinate and have successfully rooted it, flashed the cricket info (i got talk and text) and had 3g at one point. All of the sudden 3G went out. I put CYANOGEN on there, latest 7.1 i believe for the fascinate.
Upon trying to revert back to the original ROM so I can get in there with PST and CDMA WS, I encountered a very strange set of problems and now I am just stumped. I tried to ask a couple of other people and no one seems to know what is happening.
Here is what happens, I try to put the original ROM on there, by using ODIN and doing the atlasv2.2 pit file, and the original ROM, froyo, and the other one eclair i think.
When I use odin it gets to the system part, then right after it goes to the part that would take the longest, and I forgot what its called, dataFS? it has FS at the end, and then the phone (while odin is still going) will go to either a blue screen or a green screen with no words. If you look closely, it appears there is a clock at the top right just like if the phone was on.
I have not overclocked this device at all so thats one thing that can be ruled out.
I've tried odin using both battery in and battery out method as different guides have stated different things. When the battery is out, I get a blue screen. When its in, i get a green screen.
The screen appears right after the normal odin screen, with the status bar, but it will dissapear when it comes to the dataFS part (right after system) then it will take about 20 - 45 minutes and I will get an error screen on odin.
Funny thing is i've used odin and that method and it worked the last time. It works fine if I need to flash a clockwork recovery. However, upon booting into recovery, half the time I will get an error that has to do with BUILD.prop and SCH-I500. This is when I try to flash any rom except MIUI. For some reason, MIUI kicks this phone around and its the only rom that works. CM7 wont work, stock won't and every other rom wont.
So, to sum it up, my main problem is ODIN and its funky behavior, and not being able to go back to stock so I can see if my 3g settings are correct. If you have any information, even if its just something to help get my wheels turning, then please post it up, any and all help is greatly appreciated folks, thanks.
I dont know if this would work but if u think the problem is Odin then I would uninstall odin and reinstall the newest version available. Also, make sure the phone driver software get done the same.
Then after that I would try odin again. Phone off, battery out. Open odin. Plug in usb. Make sure phone set usb to debug. Hold vol down button. Odin should see your phone.
Im sure u know all the steps up to this point but try again.
Good luck
Or u can try running odin as Admin on the comp.
Also if the problem persits I saw a user had a similar problem and of turned out to be his usb cable so try a different one if you can't fix it.
Sent from my ADR6350 using Tapatalk
See, thats what I thought too, but I will give it a shot and see. I doubt its the drivers, odin or the program, file or anything else because it does work with clockwork, and i've downloaded it several thousand times, plus it works great when I do anything but flash the original rom, odin will go fine. Drivers seem fine, it communicates and all that perfectly so I also highly doubt that.
I will get another cable and just try it on a whole different PC to see what happens. I was really hoping someone had this happen and had a fix but I might have to do some heavy delving. THANKS GUYS! I will try this and report back.
It was the cables, used a brand new USB cable and it worked, strangest thing that a cable can work but not work and its just a bunch of wires, but almost all my audio cables have to be bent or else you will loose a channel. I guess its just poor quality materials. So thank you, it works now and it was just the USB cables.
So, heres my problem. I have 2 samsung fascinates. I screwed one up a while back and was able to pull it back together and get it into ICS on CM9 with all the proper files using Odin.
I recently got a second samsung fascinate and was attempting to flash the same files, through Odin, but was having trouble.
I was able to get CWR (I believe it was voodoo) onto the phone, but once in recovery mode and having cleared all cache's, wiped files, and factory reset, I still could not successfully instal the files from the SD card (the same ones that worked on the 1st fascinate)
SO
I downloaded another version (or so I thought), Pushed it through Odin, Odin said it passed and auto restarts the phone. The phone never comes back on.
In hindsight think that CWR somehow ended up being deleted from the phone (if thats possible without doing it on purpose) before what was pushed by Odin was actually pushed. The file might have been wrong, im not sure, I will post up the exact file name when I get home.
At this point, the phone is completely unresponsive,. No holding the volume, plugging it in, putting the battery in. Jig doesnt work, Heimdall Doesnt work, Fastboot doesnt work. No download mode, period. No lights, no vibration. Tried multiple batteries, tried assuming the screen was bad, tried multiple cables, tried plugging into wall and computer. Nothing.
Mac will not notice the device at all once its plugged in, however, PC notices and starts to wig out. I have to hold the power button down, while its plugged into the computer to allow for it to search for drivers
The driver is SEC S5PC110 TEST B/D notification.....I feel like this is for a phone other than the fascinate.
Either way, I try to download fascinate drives, or the driver its calling for, both being unresponsive.
Am I completely screwed? Or is the questions more that I found myself at the point the I have either deleted what was deemed "Un-deleteable" or do I need to take the board out and get a soldering iron?
Also, I know a developer, I have taken it to him and he looked at it and scratched his head......hopefully someone has some sort of solution. Thanks
What file did you try to flash?
I9100_APBOOT_I9100XXKP2_CL17109_REV02_eng_mid_ship.tar
This was the file I flashed. Again, in hindsight and based on what I was reading in the forum, it looked good. I have no idea what it actually is, and therfore should not have flashed it. But I was in read and repeat mode, so I didnt question much. If I can track down the exact thread I was in I will post it up as well.
Philveatch said:
I9100_APBOOT_I9100XXKP2_CL17109_REV02_eng_mid_ship.tar
This was the file I flashed. Again, in hindsight and based on what I was reading in the forum, it looked good. I have no idea what it actually is, and therfore should not have flashed it. But I was in read and repeat mode, so I didnt question much. If I can track down the exact thread I was in I will post it up as well.
Click to expand...
Click to collapse
thats what happens when you flash files for another
device to this one. there is a guide in the general section that has everything you needed. hopefully next time you do a bit more research before you get flash happy. at this point unbrickable mod is your only way out and that requires some microscopic soldering skills.
It looks like you flashed a bootloader for the Galaxy S2.
Interesting. It was in a fascinate forum talking about how to add ics to a fascinate phone.....hmm.
Greetings!
I have a T-Mobile SGH-T959, purchased new several years ago. Early on, I upgraded from the stock Android v2.1 to 2.2. The device worked great, no problems.
About a year ago, I decided to switch carriers. My new carrier uses CDMA, so I could not use the Vibrant (GSM), and purchased a PCD Venture, which I still use today.
Figuring I had nothing to lose, I decided to flash the SGH-T959 to Ice Cream Sandwich and rooted it. It seemed to work, and although I had no real use for the phone, it was a learning experience. I'm a System Admin. I love to tinker!
A few months ago, my fiance broke the screen on her HTC. Since she is still with T-Mobile, instead of spending what little extra cash we had, we simply put her SIM card in my Vibrant. Seemed to work fine, although she complained about a few features, and was confused by the root apps. I decided to make things easier for her, I would just flash the phone back to stock.
So, this is where I believe I messed things up. Not sure which instructions I followed, but when you first turn on the phone, you immediately see a black screen with white lettering: "GT-I9000" and immediately after: "Vibrant". From there, the normal boot animation sequence runs, the T-Mobile jingle, etc. Strange, but whatever, I thought.
Other issues: 1) Constantly get certificate errors in the web browser. I've double-checked date/time settings. 2) The Google Market does not update to the Play Store, some of the installed apps do not show in "my apps." 3) Facebook app does not work. My fiance has to use the web browser, which is frustrating with the cert errors.
So, tonight, I thought I'd give it another try. I found a HOWTO on androidspin.com (I would link the page but I'm new here) using ODIN which I followed, and the flash went perfectly. When the phone restarted, same exact issues.
I've been trying to read up some on the boot process, and the differences between PDA, PIT, etc. to see where I may have gone wrong, but I am at a loss. It seems there is some part of the phone that the flash is not touching?
I appreciate in advance any feedback/help. I'd be happy to supply any additional information about the phone that's requested as well.
Ok, android market will not upgrade while on stock JFD (2.1). The GT I9000 logo means you have somehow flashed Gingerbread bootloaders, which gives you easier button combos. Volume up + power will put you in download mode and volume down + power will now boot you into recovery. I would recommend you use this guide to go back to stock JFD http://forum.xda-developers.com/showthread.php?t=849028 (steps 2-4). Let me know if you have trouble.
Sent from my SGH-T959 using Tapatalk 2
iTz KeeFy said:
Ok, android market will not upgrade while on stock JFD (2.1). The GT I9000 logo means you have somehow flashed Gingerbread bootloaders, which gives you easier button combos. Volume up + power will put you in download mode and volume down + power will now boot you into recovery. I would recommend you use this guide to go back to stock JFD http://forum.xda-developers.com/showthread.php?t=849028 (steps 2-4). Let me know if you have trouble.
Sent from my SGH-T959 using Tapatalk 2
Click to expand...
Click to collapse
Thanks for the reply. I followed the instructions exactly. Downloaded ODIN, the PIT file, and the TAR file. I verified the MD5 hashes of each. Put the phone in download mode (vol up + power), selected the files as instructed, ran ODIN, everything went OK.
Still getting the "Vibrant" and "I9000" logo. Can't download apps. Browser won't load anything. I'm thinking there's something ODIN isn't getting, maybe the bootloader you mentioned or the modem?? I'm going to do more reading, see what I can find, but feel free to drop me any hints if you have them, since this is all new to me. :good:
Update: Followed these instructions (http://forum.xda-developers.com/showthread.php?t=1117990) and used ODIN with "Phone Bootloader Update" selected. Phone now seems to be working better. Just shows "Vibrant" when first powered on and not "I9000" anymore. Google Market is still a little strange. Many common apps like Tumblr, Instagram, etc., don't show up but I think that's because most everything needs 2.2 minimum, so my next step is to go from 2.1 stock to 2.2, and see if I can get Play Store and other apps to work normally. Browser is loading pages normally now.
Making progress!! :victory:
Update
Wasn't having any luck updating from 2.1 to 2.2 with Kies. Kept having driver issues, so decided to go the ODIN route. Downloaded the 2.2 ODIN on this link: http://forum.xda-developers.com/showthread.php?t=833024&page=49
Used ODIN to flash, and all is OK. Normal "Vibrant" load on power on, Google Play and all normal apps work perfectly!!
Just wanted to extend my thanks to the XDA forums and everyone here who contributes. Thank you!!
When I tried to flash cyan fox in cmw it gave me a status 0 error can anyone fix?
We need more info like what did it specifically say. Be as specific as possible
Sent from my Nexus 4 using xda app-developers app
RedJack117 said:
When I tried to flash cyan fox in cmw it gave me a status 0 error can anyone fix?
Click to expand...
Click to collapse
that's "usually" an error you get when the zip is corrupted.
but occasionally you'll get it if your running an i9000 roms (I've had it interchangeably with status 7 before)
I would try re-downloading and flashing the zip again.
if that doesn't work try downloading and flashing fluid kernel
then go to "advanced" and select "reboot recovery".
then try flashing the rom again.
Status 0 error on anything I try to flash using CWM
My friend gave me the Vibrant last year after getting a new phone. He gave it to me so that I could try mess around with it and try to fix it. The back and home buttons were not working. All 4 buttons light up, but only the Menu and Search responds. Phone was on stock ROM (JFD) and was not rooted - it even had the external SD that came with it. I immediately thought that re-flashing it would be a quick fix. Formatted everything and used Odin to put it back on. But, to my surprise, both buttons still did not work. It would sometimes work when I tried them on key test in CWM. Anyway, I thought that maybe a different or better ROM might do the trick. I wanted it to be more of a gaming console so I tried to put CyanAOSP on it. Got a lot of errors, but eventually, I managed to put it on. The buttons still doesn't work but at least I could navigate better using the on-screen shortcuts.
After about a month, it started to freeze and crash a lot so I decided to re-flash it again. This time, got no errors but another problem arose - it became tethered. The device always think that the USB is connected (it's always up on the notification bar) to the point that I can't even turn it back on without really attaching it to one. It was a spare phone which I use more for gaming so I was able to live with it.
A month ago, it began to freeze and crash a lot again so I thought of trying a different ROM. To my surprise, anything I try to flash using CWM gives me an error - packages would seem to load for about a quarter of the way then gives me the 'status 0' error. I get this even when I tried the ones that worked before.
I have several update.zips (1 is only 632KB while the rest are 1.7MB) and at least 2 copies of the ROMS (CyanAOSP, L-Droid and Ressurection) KERNELS (fluid, mackay, and neat), GAPPS, and MODEMS which I try to flash. I've re-visited all of the rooting threads again to cover my bases. I'm waiting for woody to respond so that I could try the files that he has because I've pretty much tried everything that I could get my hands on. (some files were pretty promising, but DL links were already down)
Regarding the update.zips that I have, I noticed that only the 632KB would root it and the others would only give me CWM 2.5.1.2 on JFD. The only way I could upgrade is by using mini kies and none of the update.zips work once I'm on KB5. (root removed and can't put it back on)
jvrey5 said:
My friend gave me the Vibrant last year after getting a new phone. He gave it to me so that I could try mess around with it and try to fix it. The back and home buttons were not working. All 4 buttons light up, but only the Menu and Search responds. Phone was on stock ROM (JFD) and was not rooted - it even had the external SD that came with it. I immediately thought that re-flashing it would be a quick fix. Formatted everything and used Odin to put it back on. But, to my surprise, both buttons still did not work. It would sometimes work when I tried them on key test in CWM. Anyway, I thought that maybe a different or better ROM might do the trick. I wanted it to be more of a gaming console so I tried to put CyanAOSP on it. Got a lot of errors, but eventually, I managed to put it on. The buttons still doesn't work but at least I could navigate better using the on-screen shortcuts.
After about a month, it started to freeze and crash a lot so I decided to re-flash it again. This time, got no errors but another problem arose - it became tethered. The device always think that the USB is connected (it's always up on the notification bar) to the point that I can't even turn it back on without really attaching it to one. It was a spare phone which I use more for gaming so I was able to live with it.
I would make sure that you realize that this phone is older and may not be up to the challenge of some of the newer games out there. Based on your PM to me, I understand that this is a secondary phone for you, so if you wanted to play some of the more graphic intensive games, I would do it on your DD.
A month ago, it began to freeze and crash a lot again so I thought of trying a different ROM. To my surprise, anything I try to flash using CWM gives me an error - packages would seem to load for about a quarter of the way then gives me the 'status 0' error. I get this even when I tried the ones that worked before.
After you PM'd me, I started looking around about the Status 0 error being thrown. All signs point to the Updater Script that in the ROMs that you are flashing. My hunch is that once you flashed the CyanAOSP, that changed your build.prop from T959 to i9000 and that is why you are getting the error. I'm pretty sure there is a way to fix it (see below)
I have several update.zips (1 is only 632KB while the rest are 1.7MB) and at least 2 copies of the ROMS (CyanAOSP, L-Droid and Ressurection) KERNELS (fluid, mackay, and neat), GAPPS, and MODEMS which I try to flash. I've re-visited all of the rooting threads again to cover my bases. I'm waiting for woody to respond so that I could try the files that he has because I've pretty much tried everything that I could get my hands on. (some files were pretty promising, but DL links were already down)
Regarding the update.zips that I have, I noticed that only the 632KB would root it and the others would only give me CWM 2.5.1.2 on JFD. The only way I could upgrade is by using mini kies and none of the update.zips work once I'm on KB5. (root removed and can't put it back on)
You should stay as far away from Kies as possible with this specific phone. It had a tendenacy to brick the Vibrants. It worked on my wife's SGS2 back when, but even then I was hesitant to use Kies on it and grinding my teath the whole time.
The zips that you mentioned are probably the standard Root.zip and the CWM zip from s15274n's thread stickied at the top of the Q&A section. Keep those handy.
Click to expand...
Click to collapse
Some answers in-line above.
**********************************
Let's get a few things straight before we start. I am still looking for the Heimdall JFD package, but I think that I know where it is. Pretty sure I put it on one of the external HDDs that I have. I'll try to upload it tonight or tomorrow night, as I am away all weekend with the family. I really don't think that you'll need it, but best to have it and not need it, than need it and not have it.
Theoretically, once you Odin'd back to JFD, I would think that it would've reset your device ID back to T959, but I guess that it didn't. This is what I would do. Odin to stock JFD and then boot it up and let it settle. Root it using the Root.zip that you have already used before. At some point you'll need to pick a ROM to settle on, even if only to get past this hump. (I use Sada's CM11 for my sons' Vibrants. Not that there is anything wrong with any of the others, but I just basically set it and forget it for my boys. I think though that he may have stopped development for it though, so I guess I'll be looking through the dev section myself here in the near future.) Take a look at this thread starting with my post #3 and the response from @nirogu325. I am thinking that if you do the same as he instructed, you will boot past the Status 0 error (since everything that I have seen in searches leads me to believe it is an Updater Script issue). My issue was a Status 7 because of the device ID being changed and the Recovery/Kernel combo weren't letting me flash. I basically opened up the ROM.zip and deleted those line and re-zipped it up and then flashed it (did it all on the phone and no PC, but I'm crazy like that).
Let's let a few of the current device Devs weigh in and see what they think. Already mentioned nirogu325 above, but let's try @epicboy and @dzee206 and @sada23. If they are inclined to come and help, it would be much appreciated.
jvrey5 said:
My friend gave me the Vibrant last year after getting a new phone. He gave it to me so that I could try mess around with it and try to fix it. The back and home buttons were not working. All 4 buttons light up, but only the Menu and Search responds. Phone was on stock ROM (JFD) and was not rooted - it even had the external SD that came with it. I immediately thought that re-flashing it would be a quick fix. Formatted everything and used Odin to put it back on. But, to my surprise, both buttons still did not work. It would sometimes work when I tried them on key test in CWM. Anyway, I thought that maybe a different or better ROM might do the trick. I wanted it to be more of a gaming console so I tried to put CyanAOSP on it. Got a lot of errors, but eventually, I managed to put it on. The buttons still doesn't work but at least I could navigate better using the on-screen shortcuts.
After about a month, it started to freeze and crash a lot so I decided to re-flash it again. This time, got no errors but another problem arose - it became tethered. The device always think that the USB is connected (it's always up on the notification bar) to the point that I can't even turn it back on without really attaching it to one. It was a spare phone which I use more for gaming so I was able to live with it.
A month ago, it began to freeze and crash a lot again so I thought of trying a different ROM. To my surprise, anything I try to flash using CWM gives me an error - packages would seem to load for about a quarter of the way then gives me the 'status 0' error. I get this even when I tried the ones that worked before.
I have several update.zips (1 is only 632KB while the rest are 1.7MB) and at least 2 copies of the ROMS (CyanAOSP, L-Droid and Ressurection) KERNELS (fluid, mackay, and neat), GAPPS, and MODEMS which I try to flash. I've re-visited all of the rooting threads again to cover my bases. I'm waiting for woody to respond so that I could try the files that he has because I've pretty much tried everything that I could get my hands on. (some files were pretty promising, but DL links were already down)
Regarding the update.zips that I have, I noticed that only the 632KB would root it and the others would only give me CWM 2.5.1.2 on JFD. The only way I could upgrade is by using mini kies and none of the update.zips work once I'm on KB5. (root removed and can't put it back on)
Click to expand...
Click to collapse
As Woody already said, you should odin back to stock 2.1. From there root and go to Jellybean and then KitKat. I'd recommend you stay away from ports that are old and haven't been updated for a while. Not trying to say that the rom I built is the best or anything but so far I haven't ran into any issues and neither has anyone that's used SpiritRom. I say try Spirit Rom 1.5 combined with iyahman's semaphore kernel that was built using linaro 4.9 as it's been stable. If you still run into these issues again I think it may be some software that you use.
The phone only had one major issue before I started messing with it - back & home buttons not working. I honestly can't remember how and what I did to put CyanAOSP on it but I ended up with 2 issues after putting it on. Only the Menu button works (eventhough all 4 lights up) and the USB seems to be grounded. I managed to work with it the past year up until I Odin-ed it back to JFD. When the phone is off and battery still has charge, the loading button would come up followed by the empty batt image at the background. This will loop until the batt dies. The only way to turn it on is by connecting the USB to a power source. Accessing download is easier because all I needed to do is remove batt then press and hold the vol up & down before putting the batt back in. Getting into recovery is a bit trickier. You'll need to wait until you actually see the phone charging before doing the 3-button combo.
Last Saturday, my daughter had a school event and I brought this along because it took better pictures than my S3 knock-off. During the parade, after shooting a video, it would automatically take me to the preview. Since, both back and home buttons were not working, I was stuck. Only option was to reboot it. What makes it interesting is that there is no reboot option on the JFD. It was a good thing that I had my power bank with me. I really did not want to constantly reboot it so I thought of installing one of those virtual button apps. I managed to install ToucherPRO before their presentation which made it much easier. To my surprise, it somehow revived the back button on the device itself - I noticed it when I got home that night to transfer the photos and vids.
I mentioned this so that you guys will have an idea on what I need to go through to get it fixed - somewhat, at least to a more tolerable state. (you won't believe it but the tips of my fingers hurt due to the number of times I have to go into recovery or download)
@Woody
Woody said:
I would make sure that you realize that this phone is older and may not be up to the challenge of some of the newer games out there. Based on your PM to me, I understand that this is a secondary phone for you, so if you wanted to play some of the more graphic intensive games, I would do it on your DD.
Click to expand...
Click to collapse
Yup. I actually find it both weird and interesting - which games work and how they work.
Woody said:
You should stay as far away from Kies as possible with this specific phone. It had a tendenacy to brick the Vibrants. It worked on my wife's SGS2 back when, but even then I was hesitant to use Kies on it and grinding my teath the whole time.
Click to expand...
Click to collapse
Remember I mentioned my hesitation using Heimdall and Bay_wolf's AIO toolkit regarding hijacking drivers and stuff, Kies on this PC is now useless. It won't even recognize the phone after I tried the toolkit - which is good, I guess.
Woody said:
... Take a look at this thread starting with my post #3 and the response from @nirogu325. I am thinking that if you do the same as he instructed, you will boot past the Status 0 error (since everything that I have seen in searches leads me to believe it is an Updater Script issue). ...
Click to expand...
Click to collapse
I read about this when I started going back through the threads. As you mentioned, this is an old phone. Old phone = old threads. What I do is I read everything on page 1 then skip over to the last page, going back. Seems to be more effective specially for DL links.
I was actually reserving this one as part of my 'last option' fix. From experience, editing scripts is far more dangerous than flashing a 'working' one. I managed to root my other DD this way, but went downhill from there - ended up bricking it 3 times.
Anyway, I think I got it - or at least, the correct way of doing it. It took me 3 days....
After day 1, I ended up with 8 update.zips (7 CWM and one ROOT) and at least 2 copies of ROMS, GAPPS, MODEMS, and KERNELS on my SD card - only the update.zips worked, the rest either gave me status 0 or leave me with the 'Vibrant Samsung' bootloop. I had some progress on DAY 2. I read something like what epicboy said:
epicboy said:
As Woody already said, you should odin back to stock 2.1. From there root and go to Jellybean and then KitKat. I'd recommend you stay away from ports that are old and haven't been updated for a while. Not trying to say that the rom I built is the best or anything but so far I haven't ran into any issues and neither has anyone that's used SpiritRom. I say try Spirit Rom 1.5 combined with iyahman's semaphore kernel that was built using linaro 4.9 as it's been stable. If you still run into these issues again I think it may be some software that you use.
Click to expand...
Click to collapse
I tried several JB ROMS listed on the Bible but, the problem was, I can't get into recovery - it was all 'blurry'. When I tried a different JB ROM, it also worked but was still 'blurry' during start up and on recovery. That's when I remembered Woody's post regarding rainbows and bootloaders.
DAY 3: For some reason, everything was flawless. I was able to install JB then KK. EFFORTLESSLY, if I may add.
@epicboy
I'm planning to spend a couple of days more on this Vibrant before I mess with my other phone - a knock-off SGS3. I was drawn to L-Droid because the screenshots and contents of page 1 of their thread was specifically for the T959 and not the I9000. I know it's not really a big deal because the ROM will work and changing the build.prop for 'cosmetic purposes is easy. What really concerns me is the camera. Sadly, the T959 only has only one camera and if the camera app that you're using (stock or otherwise) has a feature to switch from back-to-front and you accidentally press that, it messes it up to the point that you can't use it anymore. I have downloaded the ROM and will try it out in a couple of days. Will send you a PM or reply on the thread regarding my feedback. I've flashed it several times but really haven't been able to do it flawlessly like in DAY 3 - which I find really weird.
Tnx peeps!