I am at wits end. Got it rooted and everything, but used the wrong kernal. I had good sucess with my Captivate, so I tried a similar procedure. Unfortunetly, when I boot the phone I end up with "Can't acess to '/system/csc/ATT/system/'. I'm not sure if this is the right spot to post but at the risk of looking like an idiot, I'll beg
Edit: I do have access to download mode, and Odin.
Im sorry i cant help you, im not good enough, but i guess we (who's able to help) need more informations.
Model of your S2? i9100 or 9100g?
What kind of wrong kernel you flashed?
Is your phone a standard or a AT&T S2?
I think this infos can be very helpfull
It's the i777, the kernal was the XWKDD, and it's an AT&T. It worked fine, rooted, got Busybox and everything to work. But I noticed the back button didn't work, and the home button backed me up. To I attempted to install a ROM, and then it won't start. I got one installed, but it sits at the clockwork recovery screen. The power button won't function as OK, so I can't qipe the data.
Designgears has started a ATT sgs2 ROM. you can use that. http://forum.xda-developers.com/showthread.php?t=1286939
I discovered the 3-file way to do it in another thread, but this unfortunately leaves me back and my search button not functioning.
Edit: Fairly certain I turned it into the european version of the phone, since the 2 buttons don't work and the default clock is 24 hour.
As an update, I can get most things to work except I can't get the button configuration correct...which isn't an issue until I try to use CWM or something of that sort...any help to get the button config back to standard I777 would be GREATLY appreciated
Wrong forum!!!
Try here: http://forum.xda-developers.com/forumdisplay.php?f=1301
My apologies, I don't know my way around here like I do at OCN.
I was working on rooting my SG2 and while doing and reading the simple steps to root, I got ahead of myself. My phone was sitting with the "Download - do not turn off target" warning and I was still looking for the insecured kernel. After several tries I couldn't get the insecured to extract the .tar. It said it was encrypted. I'm using WinRar. even after trying different insecured ones. Sooo. Thinking I may be screwed, I used the PDA function in Odin to download the "original" kernel this my phone accepted, it was in .tar format. Now my Home key seems to be remapped to back button and back and search don't work.
What is next to do?
I have tried to go back to the download screen but the home key won't work. Also when I try to, phone goes to Android system recovery <3E> but again the power button doesn't select what I put the highlighting bar on.
BTW, also tried the factory reset.
If you can get to download mode flash stock rom via Odin rom not kernel .
That fails its a service centre for a possible non warranty repair .
Stock Roms .and csc
http://forum.xda-developers.com/showthread.php?t=1075278
jje
Thank you so much for your reply. I took some time to read through the link you sent me. LOTS of INFO! After taking a patient approach, I made sure that USB debugging was on and I pressed the correct key combo (flashes of street fighter) and presto I was given the 'Are you sure about changing your OS' screen. SUCCESS. Well almost where do I go for the stock ROM? I have flashed custom ROM's on my captivate but where do I get the At&t one?
I will keep rereading that link. I'm sure it will make more sense as I digest it.
Thank you again.
So I am now a happy superuser! I found out that if your usb is not connected you can't get into download mode. Because I had install an incorrect kernel it had a slight remapping issue because it was for a Galaxy S 2 I9100, I have the US version I777. So by noticing the ability change while being connected I took advantage and flashed a clorkworkmod kernel for my phone I777. Then following the instructions for the super-one-click worked too. Thank you again for your patience. Perhaps this might help others.
Continuing on from my earlier post on how to make the Korean Galaxy Note work in Canada, I'll continue on some troubleshooting you can do with a custom firmware I found on KOXDA.
First, make sure you have a nandroid backup, if not I'd recommend following the guide I made here to install CWM Recovery and use it to make your nandroid backup, it's not ABSOLUTELY necessary, but it will make things a hell of a lot easier for you.
(my previous post: http://forum.xda-developers.com/showthread.php?p=28899883)
After you've made your backup, download this firmware:
http://www.sharebees.com/6lvyjdfv8tv8.html
This is a custom SHV-E160L firmware that has international features enabled and made by a really talented programmer on koxda who goes by the username teamleader, he also made an custom AT&T ROM for the galaxy note which I cannot find as of yet, so if someone finds that one, let me know.
Anyways, once you've downloaded the firmware from sharebees, flash it onto your phone using Odin in the same way as you've flashed other firmwares. Once that is done, you'll have access to a gingerbread build of the ROM working on your phone. From here, you'll need the secret menus.
Open up the phone dialpad and type in *#*#2663#*#*
(Codes courtesy of this thread here on xda note they're for the i9000 but lots of codes are reused for different Samsung products: http://forum.xda-developers.com/showthread.php?p=7882964&postcount=42)
As soon as you finish typing that last * in, the phone should open up a secret menu with two options. One button to upgrade touch screen firmware and another to upgrade the touch key firmware.
**WARNING**
IF YOUR TOUCH KEYS ARE WORKING FINE, DO NOT TOUCH ANYTHING JUST LEAVE THAT SCREEN NOW!
Please note that perfectly working touch keys (the menu and back buttons beside your home button) can be ruined by updating the firmware, not sure about the touch screen but hey, don't mess around with something that isn't broken (should've taken that advice for myself but I wouldn't have learned anything to share if I hadn't, anyways you've been warned).
Once in this screen, press the button to upgrade your touch key and wait. Eventually it'll finish, you can try rebooting the phone (though mine worked immediately after I believe) and test out your touch keys.
If they work, congratulations, but the reason why I don't use the teamleader ROM with all its useful features will become readily apparent. First, it does not have google market and I was never successful in installing it properly. Secondly of all, it tends to be rather unstable, at least for me and crashed like crazy.
So now you're going to want your old ICS system and all its novelties back. You can at this point flash the stock ROM I posted in my previous link and go through the entire process of rooting and getting the SMS to work.
~~OOORRR~~~
If you have a nandroid backup, just boot into recovery and restore that backup.
The touch key firmware update will survive the restoration if it started working already and should remain working with your restored backup image.
If all goes well, then congratulations you now have a working phone once again.
I hope the hours I spent in frustration trying to fix my damn phone helps someone and feel free to pm me if you have any questions, please note I am very bad at responding.
Good luck everyone
OMG it worked like a charm ^^
thank you soo much man! XD
I almost gave up hope!!
just a small comment:
in order to enter touchkey firmware i typed : *#2663#
the KOXDA rom is working with me without lagging until now so I will give it a run for a while ^^
sure hope they release an ICS international rom soon ^^
thanks again for the awsome thread! XD
Congrats
No problem, glad it worked for you, if you figure out some new tricks for your phone, be sure to let me know.
njthenj said:
OMG it worked like a charm ^^
thank you soo much man! XD
I almost gave up hope!!
just a small comment:
in order to enter touchkey firmware i typed : *#2663#
the KOXDA rom is working with me without lagging until now so I will give it a run for a while ^^
sure hope they release an ICS international rom soon ^^
thanks again for the awsome thread! XD
Click to expand...
Click to collapse
I have ICS upgraded one, and after flash it doesn't load the rom. Did you guys have gb? meaning i have to downgrade firmware before installing this teamleader rom to work?
edit:
No worries! I downloaded a wrong version from koxda. This version works perfect, touch key updated by *#2663# function. works instant.
njthenj said:
OMG it worked like a charm ^^
thank you soo much man! XD
I almost gave up hope!!
just a small comment:
in order to enter touchkey firmware i typed : *#2663#
the KOXDA rom is working with me without lagging until now so I will give it a run for a while ^^
sure hope they release an ICS international rom soon ^^
thanks again for the awsome thread! XD
Click to expand...
Click to collapse
Hey. Thanks Gods I found it. My E160L's menu and back button disabled when I flash wrong version of CMW in ROM Manager (I chose Phone Model i717). Could I use this way to recover my button??? Would you please Reupload file SHV-E160L-PDA_V1.0.tar to another host, such as mediafire or 4shared.com or dropbox? In my country loading from Sharebees is very difficult.
Thanks for everything. Really Grateful.
mycatisether said:
Continuing on from my earlier post on how to make the Korean Galaxy Note work in Canada, I'll continue on some troubleshooting you can do with a custom firmware I found on KOXDA.
First, make sure you have a nandroid backup, if not I'd recommend following the guide I made here to install CWM Recovery and use it to make your nandroid backup, it's not ABSOLUTELY necessary, but it will make things a hell of a lot easier for you.
(my previous post: http://forum.xda-developers.com/showthread.php?p=28899883)
After you've made your backup, download this firmware:
http://www.sharebees.com/6lvyjdfv8tv8.html
This is a custom SHV-E160L firmware that has international features enabled and made by a really talented programmer on koxda who goes by the username teamleader, he also made an custom AT&T ROM for the galaxy note which I cannot find as of yet, so if someone finds that one, let me know.
Anyways, once you've downloaded the firmware from sharebees, flash it onto your phone using Odin in the same way as you've flashed other firmwares. Once that is done, you'll have access to a gingerbread build of the ROM working on your phone. From here, you'll need the secret menus.
Open up the phone dialpad and type in *#*#2663#*#*
(Codes courtesy of this thread here on xda note they're for the i9000 but lots of codes are reused for different Samsung products: http://forum.xda-developers.com/showthread.php?p=7882964&postcount=42)
As soon as you finish typing that last * in, the phone should open up a secret menu with two options. One button to upgrade touch screen firmware and another to upgrade the touch key firmware.
**WARNING**
IF YOUR TOUCH KEYS ARE WORKING FINE, DO NOT TOUCH ANYTHING JUST LEAVE THAT SCREEN NOW!
Please note that perfectly working touch keys (the menu and back buttons beside your home button) can be ruined by updating the firmware, not sure about the touch screen but hey, don't mess around with something that isn't broken (should've taken that advice for myself but I wouldn't have learned anything to share if I hadn't, anyways you've been warned).
Once in this screen, press the button to upgrade your touch key and wait. Eventually it'll finish, you can try rebooting the phone (though mine worked immediately after I believe) and test out your touch keys.
If they work, congratulations, but the reason why I don't use the teamleader ROM with all its useful features will become readily apparent. First, it does not have google market and I was never successful in installing it properly. Secondly of all, it tends to be rather unstable, at least for me and crashed like crazy.
So now you're going to want your old ICS system and all its novelties back. You can at this point flash the stock ROM I posted in my previous link and go through the entire process of rooting and getting the SMS to work.
~~OOORRR~~~
If you have a nandroid backup, just boot into recovery and restore that backup.
The touch key firmware update will survive the restoration if it started working already and should remain working with your restored backup image.
If all goes well, then congratulations you now have a working phone once again.
I hope the hours I spent in frustration trying to fix my damn phone helps someone and feel free to pm me if you have any questions, please note I am very bad at responding.
Good luck everyone
Click to expand...
Click to collapse
I had downloaded this ROM from 115.com and Upload it to my account.
Here you are.
http://www.fshare.vn/file/TS0925X8DT
i tried to flash the rom its went well for about an hour but suddenly i cant receive any text message..
plsss guide me to fix this..i like the rom its good but i cant receive any text...thanks
Hello Mycatisether
Thank u for sharing a lot of useful working posts and guides.
i Followed "Using the SHV-E160L in Canada [ICS][Root][CWM][SMS]" Guide and made it good. But after rooted i inserted micro-sim and calling and other service is working Perfect, But only one thing is not work that is NOT SMS SENT.
so i googling and Found your new Post, if Your first post is not work 100% and this is working 100%, i suggest u Delete previous post. if u do that Users will Following One perfect working Guide of yours. . i am trying this method on my E160L after few hours after downloaded the 823MB file.
So i report any of result. Please be keep in touch us :good:
Best wishes man!
No Service after flash by This ROM LOL. . So i am trying another Chine ROM
God bless you
mycatisether said:
continuing on from my earlier post on how to make the korean galaxy note work in canada, i'll continue on some troubleshooting you can do with a custom firmware i found on koxda.
First, make sure you have a nandroid backup, if not i'd recommend following the guide i made here to install cwm recovery and use it to make your nandroid backup, it's not absolutely necessary, but it will make things a hell of a lot easier for you.
(my previous post: http://forum.xda-developers.com/showthread.php?p=28899883)
after you've made your backup, download this firmware:
http://www.sharebees.com/6lvyjdfv8tv8.html
this is a custom shv-e160l firmware that has international features enabled and made by a really talented programmer on koxda who goes by the username teamleader, he also made an custom at&t rom for the galaxy note which i cannot find as of yet, so if someone finds that one, let me know.
Anyways, once you've downloaded the firmware from sharebees, flash it onto your phone using odin in the same way as you've flashed other firmwares. Once that is done, you'll have access to a gingerbread build of the rom working on your phone. From here, you'll need the secret menus.
Open up the phone dialpad and type in *#*#2663#*#*
(codes courtesy of this thread here on xda note they're for the i9000 but lots of codes are reused for different samsung products: http://forum.xda-developers.com/showthread.php?p=7882964&postcount=42)
as soon as you finish typing that last * in, the phone should open up a secret menu with two options. One button to upgrade touch screen firmware and another to upgrade the touch key firmware.
**warning**
if your touch keys are working fine, do not touch anything just leave that screen now!
Please note that perfectly working touch keys (the menu and back buttons beside your home button) can be ruined by updating the firmware, not sure about the touch screen but hey, don't mess around with something that isn't broken (should've taken that advice for myself but i wouldn't have learned anything to share if i hadn't, anyways you've been warned).
Once in this screen, press the button to upgrade your touch key and wait. Eventually it'll finish, you can try rebooting the phone (though mine worked immediately after i believe) and test out your touch keys.
If they work, congratulations, but the reason why i don't use the teamleader rom with all its useful features will become readily apparent. First, it does not have google market and i was never successful in installing it properly. Secondly of all, it tends to be rather unstable, at least for me and crashed like crazy.
So now you're going to want your old ics system and all its novelties back. You can at this point flash the stock rom i posted in my previous link and go through the entire process of rooting and getting the sms to work.
~~ooorrr~~~
if you have a nandroid backup, just boot into recovery and restore that backup.
The touch key firmware update will survive the restoration if it started working already and should remain working with your restored backup image.
If all goes well, then congratulations you now have a working phone once again.
I hope the hours i spent in frustration trying to fix my damn phone helps someone and feel free to pm me if you have any questions, please note i am very bad at responding.
Good luck everyone
Click to expand...
Click to collapse
god bless you. Everything worked for my e160l.
I want to thank you again and again.
You are genius. You are the real man!!!
mycatisether said:
Continuing on from my earlier post on how to make the Korean Galaxy Note work in Canada, I'll continue on some troubleshooting you can do with a custom firmware I found on KOXDA.........
Anyways, once you've downloaded the firmware from sharebees, flash it onto your phone using Odin in the same way as you've flashed other firmwares. Once that is done, you'll have access to a gingerbread build of the ROM working on your phone. From here, you'll need the secret menus.
Open up the phone dialpad and type in *#*#2663#*#*
(Codes courtesy of this thread here on xda note they're for the i9000 but lots of codes are reused for different Samsung products: http://forum.xda-developers.com/showthread.php?p=7882964&postcount=42)
As soon as you finish typing that last * in, the phone should open up a secret menu with two options. One button to upgrade touch screen firmware and another to upgrade the touch key firmware.
**WARNING**
IF YOUR TOUCH KEYS ARE WORKING FINE, DO NOT TOUCH ANYTHING JUST LEAVE THAT SCREEN NOW!
Please note that perfectly working touch keys (the menu and back buttons beside your home button) can be ruined by updating the firmware, not sure about the touch screen but hey, don't mess around with something that isn't broken (should've taken that advice for myself but I wouldn't have learned anything to share if I hadn't, anyways you've been warned).
Once in this screen, press the button to upgrade your touch key and wait. Eventually it'll finish, you can try rebooting the phone (though mine worked immediately after I believe) and test out your touch keys.
Good luck everyone
Click to expand...
Click to collapse
Thanks Dude for this awesome work...
m having the issue, messed up with touch keys, bcoz of using wrong firmware i717...
well, wanna know how much time its taking to update touch firmware..
bcoz i tried last night n its almost 14 hours, still phone showing me " Now Updating...Warning! Do not turn off! "
thank you @mycatisether you are a real life saver!
at the begining the code *#*#2663#*#* had not worked and i was begining to lose hope... but after trying many combination i got it to work by using *#2663#* maby because I have a SHV-E160S (JB rom)
@crazy_kamal if is not to late.. for me the update procedure lastet 10-30 seconds (conected to a router with the speed of 10 Mbps if it counts)
sir
mycatisether said:
Continuing on from my earlier post on how to make the Korean Galaxy Note work in Canada, I'll continue on some troubleshooting you can do with a custom firmware I found on KOXDA.
First, make sure you have a nandroid backup, if not I'd recommend following the guide I made here to install CWM Recovery and use it to make your nandroid backup, it's not ABSOLUTELY necessary, but it will make things a hell of a lot easier for you.
(my previous post: http://forum.xda-developers.com/showthread.php?p=28899883)
After you've made your backup, download this firmware:
http://www.sharebees.com/6lvyjdfv8tv8.html
This is a custom SHV-E160L firmware that has international features enabled and made by a really talented programmer on koxda who goes by the username teamleader, he also made an custom AT&T ROM for the galaxy note which I cannot find as of yet, so if someone finds that one, let me know.
Anyways, once you've downloaded the firmware from sharebees, flash it onto your phone using Odin in the same way as you've flashed other firmwares. Once that is done, you'll have access to a gingerbread build of the ROM working on your phone. From here, you'll need the secret menus.
Open up the phone dialpad and type in *#*#2663#*#*
(Codes courtesy of this thread here on xda note they're for the i9000 but lots of codes are reused for different Samsung products: http://forum.xda-developers.com/showthread.php?p=7882964&postcount=42)
As soon as you finish typing that last * in, the phone should open up a secret menu with two options. One button to upgrade touch screen firmware and another to upgrade the touch key firmware.
**WARNING**
IF YOUR TOUCH KEYS ARE WORKING FINE, DO NOT TOUCH ANYTHING JUST LEAVE THAT SCREEN NOW!
Please note that perfectly working touch keys (the menu and back buttons beside your home button) can be ruined by updating the firmware, not sure about the touch screen but hey, don't mess around with something that isn't broken (should've taken that advice for myself but I wouldn't have learned anything to share if I hadn't, anyways you've been warned).
Once in this screen, press the button to upgrade your touch key and wait. Eventually it'll finish, you can try rebooting the phone (though mine worked immediately after I believe) and test out your touch keys.
If they work, congratulations, but the reason why I don't use the teamleader ROM with all its useful features will become readily apparent. First, it does not have google market and I was never successful in installing it properly. Secondly of all, it tends to be rather unstable, at least for me and crashed like crazy.
So now you're going to want your old ICS system and all its novelties back. You can at this point flash the stock ROM I posted in my previous link and go through the entire process of rooting and getting the SMS to work.
~~OOORRR~~~
If you have a nandroid backup, just boot into recovery and restore that backup.
The touch key firmware update will survive the restoration if it started working already and should remain working with your restored backup image.
If all goes well, then congratulations you now have a working phone once again.
I hope the hours I spent in frustration trying to fix my damn phone helps someone and feel free to pm me if you have any questions, please note I am very bad at responding.
Good luck everyone
Click to expand...
Click to collapse
sir can i have another link.. i cant download it/
will this work with galaxy note shv-160k pls help
mycatisether said:
Continuing on from my earlier post on how to make the Korean Galaxy Note work in Canada, I'll continue on some troubleshooting you can do with a custom firmware I found on KOXDA.
First, make sure you have a nandroid backup, if not I'd recommend following the guide I made here to install CWM Recovery and use it to make your nandroid backup, it's not ABSOLUTELY necessary, but it will make things a hell of a lot easier for you.
(my previous post: http://forum.xda-developers.com/showthread.php?p=28899883)
After you've made your backup, download this firmware:
http://www.sharebees.com/6lvyjdfv8tv8.html
This is a custom SHV-E160L firmware that has international features enabled and made by a really talented programmer on koxda who goes by the username teamleader, he also made an custom AT&T ROM for the galaxy note which I cannot find as of yet, so if someone finds that one, let me know.
Anyways, once you've downloaded the firmware from sharebees, flash it onto your phone using Odin in the same way as you've flashed other firmwares. Once that is done, you'll have access to a gingerbread build of the ROM working on your phone. From here, you'll need the secret menus.
Open up the phone dialpad and type in *#*#2663#*#*
(Codes courtesy of this thread here on xda note they're for the i9000 but lots of codes are reused for different Samsung products: http://forum.xda-developers.com/showthread.php?p=7882964&postcount=42)
As soon as you finish typing that last * in, the phone should open up a secret menu with two options. One button to upgrade touch screen firmware and another to upgrade the touch key firmware.
**WARNING**
IF YOUR TOUCH KEYS ARE WORKING FINE, DO NOT TOUCH ANYTHING JUST LEAVE THAT SCREEN NOW!
Please note that perfectly working touch keys (the menu and back buttons beside your home button) can be ruined by updating the firmware, not sure about the touch screen but hey, don't mess around with something that isn't broken (should've taken that advice for myself but I wouldn't have learned anything to share if I hadn't, anyways you've been warned).
Once in this screen, press the button to upgrade your touch key and wait. Eventually it'll finish, you can try rebooting the phone (though mine worked immediately after I believe) and test out your touch keys.
If they work, congratulations, but the reason why I don't use the teamleader ROM with all its useful features will become readily apparent. First, it does not have google market and I was never successful in installing it properly. Secondly of all, it tends to be rather unstable, at least for me and crashed like crazy.
So now you're going to want your old ICS system and all its novelties back. You can at this point flash the stock ROM I posted in my previous link and go through the entire process of rooting and getting the SMS to work.
~~OOORRR~~~
If you have a nandroid backup, just boot into recovery and restore that backup.
The touch key firmware update will survive the restoration if it started working already and should remain working with your restored backup image.
If all goes well, then congratulations you now have a working phone once again.
I hope the hours I spent in frustration trying to fix my damn phone helps someone and feel free to pm me if you have any questions, please note I am very bad at responding.
Good luck everyone
Click to expand...
Click to collapse
will this work with galaxy note shv-160k pls help
just the code *#2663# worked for me to fix the touchkey issue of shv-e160k. i just flashed different custom rom and when i see the keys does not work, i came here. i mean you do not have to install any firmware just try the code and update. thanks friend!
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!