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!
Related
My biggest issue that's bugging me right now is my home key(select) inside CWM is not working after flasshing VillainRom 3.0 . Has anyone ever had this happen to them? I've been browsing the forums for hours and can't find anyone with the same issue. I'm still searching.
I have been toying with my new SGS2 and I rooted it and tried out a few roms. I was anxious to try out VillainROM 3.0 for sgs2. I flashed the rom in CWM recovery. It booted up just fine. But now I can't make calls, connect to my carrier network/home network. My Menu/Home buttons don't work, back button works, search button brings up the menu... I've tried a few other roms and got the yellow triangle and was able to fix it by reflashing my backup in CWM using http://forum.xda-developers.com/showthread.php?t=1342728 .
I decided to stop looking for people with the same issue and try to get back to stock, I found this thread http://forum.xda-developers.com/showthread.php?t=1409634 . I'm crossing my fingers and hoping for the best.
That you can´t use the home button inside CMW, depends on the version you are using. The standard CWM version, does not support the homekey, therefore you can use the power putton.
You are in the wrong forum. You can't use I9100 roms on a Epic touch 4g device. Flash only roms for your device. That's why you can't make calls en buttons don't work anymore.
Thank you Lennyz1988. Anywho anyone who is dumb enough to try what I did can fix their problem with the link I posted in my first reply. I managed to get everything back up and running. I need to double check to make sure everything will work right next time I try out a new rom. I have had some success in flashing roms so far.
I've spent a couple days searching, but there doesn't appear to be a relevant enough thread to help me here, so I've resorted to asking for help, hopefully you guys can help me figure this out.
I got my girlfriend a used Telus SGH-T959D (same thing as the T-mobile version pretty well) several months back. It was on stock 2.1 and worked fine but was very laggy compared to my rooted HTC Desire on oxygen 2.3.2. So I rooted it and installed a 2.2 rom with Voodoo sound control (but no lagfix), and she's been using it this way for months now. It was better than stock but still laggy. I can't remember what rom it was but it was based on Samsuck firmware, hence why it's still laggy I guess.
For some reason, when I originally rooted it I had trouble with CWM recovery not installing, I can't even remember now what exactly was happening, but I managed to get the rom installed without a proper custom recovery, so when I go into recovery it's just the stock Samsung recovery, with no options for nandroid backup, restore, flash zip from sd card, etc. Basically I can't do anything useful in recovery.
Anyways lately, worse and worse she has been getting the Android text message to wrong recipient bug. If you aren't aware of it, it causes messages you sent to go to a different person in your text message message list. No it is not user error.
So I decided to try and data wipe. After this there is basically no launcher when it boots up. The notification pulldown is there and working, and it shows the phone has a signal and wifi is turning on and working, capacitive buttons light up when you press them, but you can't do anything except grab the pulldown.
It won't connect to USB when booted up, phone shows a message that you must close running processes first, or something like that. But I cannot flash a rom from recovery anyways, since it only brings up a stock recovery.
I can get it into download mode, if I hold my tongue just right and try several times, but not sure what to try to flash with Odin. I already downloaded an ICS Passion rom, but then reading the tutorial saw that I must first download CM7 and install that, then upgrade the bootloaders to the GB ones, then flash the ICS rom. I would really like to at least upgrade to 2.3 and something not based on Samsung fw, but the main priority is to get it working again.
Anyways, whatever you guys can suggest to try would be greatly appreciated. Thanks.
Honestly bro, everything I'm seeing in Google makes it seem like that phone is more on par with the Galaxy S Fascinate than with our Vibrant. Although on the exterior they all look so similar... I dunno, maybe check out their forums and see if you get anymore help there?
Here's the link:http://forum.xda-developers.com/forumdisplay.php?f=718
Goodluck!
The title of this thread looks similar to my problem with my Samsung Vibrant. So I would ask it here, too.
I'm not sure if I bricked my vibrant, it's still power up, only to to first screen, which has the words Vibrant (and) Samsung and stay there forever.
I first rooted my Vibrant successfully.
Then, I've followed the instructions below:
1. Download the latest version of the ROM from the original development page.
2. Transfer the downloaded zip file to the root of the internal SD card on your phone.
3. Turn off your phone and wait for complete shutdown (wait for capacitive button lights to go off).
4. Then, boot into Clockworkmod (CWM) recovery. To do so, press and hold these 3 buttons together: Volume Up, Volume Down, & the Power button till the screen turns on, then let go of the buttons. In recovery, use Volume keys to scroll up and down and power key to select an option.
5. Perform a full Wipe (this will not wipe your SD cards)
a. Wipe data / factory reset –> then Select Yes - Wipe data/Factory reset on the next screen.
b. Select “mounts and storage“, then select “format system” -> select “Yes” on next screen to confirm. Then, select “go back” to go back to the main recovery menu.
6. Now scroll to “Install zip from sdcard” and select it.
7. Select “Choose zip from sdcard”. Scroll to the file you transferred in Step 2 and select it.
8. Now confirm installation by selecting “Yes — Install **your_rom_file_name**.zip – The ROM will start installing.
9. The phone will reboot to recovery in the middle of the installation, then continue installing the ROM.
When I got to step 7, instead of running the zip file downloaded on step 1. I run the update.zip (something like that). And I couldn't get back to the CWM recovery screen anymore. Only I can boot it to the regular recovery screen, where it let you:
reboot the system
reinstall packages
delete all user data
delete cache data.
Or boot up to the screen described at the beginning of this post.
So what should/can do to fix this problem?
I think my phone is t959 (it's t-mobile Samsung Vibrant)
Thanks for the reply. As far as I thought the only similarity between this and the at t fascinate was the name fascinate. There's is the i5000 and mine is the t959d? Should this post be moved over there? I found a thread there with someone having partly. the same issue as mine not being able to install cwm but its been there for days and likely will not be replied to.
I've spent a lot of time trying to fix messed-up installs. Seems to me that if for any reason you can't rrflash the rom, or reflashing and wiping doesn't work, just Odin-ing back to JFD and going from there is the best bet.
Well I was about to go ahead and download stock JFD and try flashing that but it appears that Mega upload has been shutdown by the FBI for fraudulent activity, and Rapid share is not working either. Maybe they're too busy because of the mega Upload shutdown or they were owned by the same people and have also been shut down. So now I'm not sure where to even find files that are safe to flash.
I just spent another hour on here and Android forums, and basically all the the threads are one or two posts, with no resolution to the OP, and none of the downloads links anywhere are working. I'm pretty patient but I'm ready to give up. Does anyone want to trade a soft bricked T959D in mint condition for any old beatup HTC that works? I've had my fill of Samsung's now.
No trade sorry but if you want to donate shoot me a pm.
Before you dump it, give me some time to look into this and I'll see if I can get you up and running with some files. Sammys are way user friendly unless you aren't doing something right, then you could always go back to stock.
Hold the phone. Haha. I'll get back to you.
You too ciditin
Thanks Woodrube, I will definitely wait patiently as long as I know I'm going to be able to sort it out eventually. I'm busy with schoolwork so even though I enjoy this kind of thing I hate spending hours upon hours on it just trying to get the phone operational again.
I've been spoiled by my htc desire, it's been almost foolproof to do anything after spending a short time reading a few FAQ's and there have been no close calls. Soon I'll probably try an ICS rom once they get a bit more stable.
I will definitely do a donate if you can help me get it going with a decent rom. I would love to have lag fix on it since my girlfriend is a bit annoyed at the lag.
Since I got my first Android phone in August 2010, I've rooted and rom'd an LG Shine Plus, LG Optimus One, HTC Desire, the T959D and Galaxy S2 T989D (sold after I got it on an early renewal). I also had to fix my sisters I9000M after a failed 2.3 update operation. So I'm no expert on this, but I've got a little bit of experience messing around with stuff. Just they all require different processes, different programs to do the job, so you have to relearn it for every new phone.
The Samsung's have been the biggest pain compared to the others, but I think it's mostly because the Canadian versions are always slightly different than the Tmobile version, but besides that Samsung always has several different versions of the same.
If I get this thing up and running again I will probably check out your GPS fix thread, cause the GPS on this phone would lock on but it was way out to lunch. Like 6 streets away from us out to lunch.
I found the way to fix my problem, hopefully it'll fix yours.
I was able to restore my stock.
Here is what you have to do.
WARNING!!! THIS WILL WIPE ANY DATA ON YOUR DEVICE, IT WILL REPLACE YOUR BASEBAND, KERNEL, RECOVERY AND OS.
DOWNLOADS:
ODIN application
512 PIT file - I can't post link so pm me
T-Mobile Vibrant JFD Image – I can't post link so pm me
USB Drivers from the Samsung Galaxy S – 32 Bit Windows Download \ 64 Bit Windows Download (again I can't post link, yet)
INSTRUCTIONS:
1. Turn off your phone (remove battery, and usb cable to pc).
2. Plug usb cable to your phone (this is just for easy to connect to the PC in the next step), do NOT connect it to your pc just yet.
3. Get your phone into DOWNLOAD mode by holding the Volume Up, Volume down, and plug your usb cable to your PC. A yellow digging Android sign should be on the screen of your phone. This may take a few tries to get it right.
3. Launch ODIN.The third box dow from the top-left box should then say a COM port (the box under the top-left box should be yellow).
4. In ODIN, load each file with its corresponding field:
___a. Click PIT and select *.pit file extracting from the 512 PIT file above.
___b. Click PDA and select the *.tar, stock JFD file.
5. Don’t check anything else, the other two boxes should be checked by default (Auto Reboot and Reset Time)
6. Hit “start.” Be patient for a couple minutes! (The bar under the top left box should show the progress, and on you phone, too)
7. You should have your Vibrant back in with stock configuration.
Good luck!
NOTE: COM3 worked fine for me. COM should not matter as long as you are using the correct drivers.
350Rocket said:
I will definitely do a donate if you can help me get it going with a decent rom. I would love to have lag fix on it since my girlfriend is a bit annoyed at the lag.
Click to expand...
Click to collapse
Ok. I wasn't soliciting for a monetary donation, I was just going off that you wanted to trade. I can't trade but if you ever want to donate your phone then just PM me.
I have to agree with kawika that everything I have read has been that your model number is for the Fascinate. Easy tip off would be; does your phone have a sim card? It is probably a CDMA phone with no sim slot. I suggest getting the files you need from the Fascinate forums as I am almost positive that the T959 files will not work on the T959d. Since you have modded a I-9000m you know that they are slightly different than the I-9000. Same thing goes with this circumstance.
Good luck and sorry that there wasn't more I could do but it is just a different phone.
@Citidin - Good to see you got yours solved. If you have questions, please ask (in the correct thread for your question a this one will probably be closed out).
It definitely has a sim card and it's HSPA, I pulled the Sim card out and put it in my HTC Desire for her to use, and put my SIM card in this crappy little LG Optimus One that's too small for me to type on. So I guarantee it has a sim card and is nothing like the Verizon phones which will not work on any of the Canadian carriers AFAIK. I think nobody understands what the phone is, and that's why almost every thread with a problem like this ends in 0 replies. I think from now on I will stay away from Samsung's abortion phones that they sell in Canada. Or at least I will research community support before getting one.
Ours is called the Fascinate, but its completely different model # than theirs, it is the T959D. Just like how the new Telus galaxy S2x is the T989D, same phone as the T mobile T989_.
For some reason there seems to be a few posts in the Fascinate section, for Telus only, I think that only started because of confusion about what the phone was, but the phone has nothing in common with the Verizon CDMA version. Actually I think if you look up, just about every phone that Telus or Bell (same network basically) gets, is a phone that T mobile got first. HTC Amaze being another one. HTC Desire Z is the same as the Tmobile G2.
Sorry I misunderstood you about donating the phone itself. My last effort will be the JFD file that Citidin sent me a link to. Hopefully that gets it going. If not I will stash it away until I have extra time to try again.
Well once I got the JFD file downloaded and put phone in download mode, turned on Odin, realized the PC recognizes the device attached and being malfunctioned, so I cannot flash with Odin.
I tried Heimdall which I downloaded yesterday, but the program won't load as it says I'm missing a DLL file.
I tried Android flasher which I downloaded who knows when, and tried to just install a recovery image with it, but it gets stuck while pushing recovery image and the program locks up.
I decided to try my girlfriends Laptop instead of mine after maybe 40 failed attempts to get Odin to communicate on mine, and to my surprise it recognized it right away. I transferred my files, with the JFD to this computer and then flashed with Odin. It took about 2 minutes and it was up and running. I checked about phone and it said 2.3.3 firmware. Really confused I looked back at odin and realized I flashed the I9000M stock 2.3.3 firmware (KG3) that I flashed on my sisters phone back around xmas. I forgot I did that on this laptop.
Anyways it is working as it should except for the home button not working (which I had already read about in a thread about using I9000M or Vibrant roms on the T959D).
While it is unfortunately stock again, the 2.3.3 should fix the original problem of sending to texts to the wrong recipient, and it also seems a lot less laggy. I think I'll just let her try it as is and hope she is happy.
If you use the JFD file from the link I sent you, it should be the stock Tmobile Vibrant.
Similar problem
Sorry dont mean to hijack your thread but I think I am having a similar problem - posted in the wrong spot before so hopefully I am ok here...
Have a Vibrant and some how got crossed up on it.
I have been able to use Odin to update the phone, however after it says its done, it does a reboot as it supposed to, shows the samsung screen then just shuts down.
After about a hundred tries, someone pointed me to Eugene's no brick. I tried that and it will fix it so it will boot and go into recovery, but I can't seem to do much once I get there. My only options are to update, wide data and wipe cache. Can't get to the point where I can load an update onto the unit.
I tried wide data and reset, then reboot. It shows the samsung vibrant logo, then the splash screen, then the big S and then screen goes black and the cap buttons stay lit.
If I try to go back and load the stock pit and jfd file, it just goes back to not booting at all and shutting down after the logo
I cant seem to get it into recovery unless I do Eugene's fix
In one of my earlier attempts, I did check to repartition as direct in one of the other threads - been chasing this a while now!
Edit: It was originally a bell phone - does this matter?
If it was a Bell phone than it should be the I9000M. It sounds like your problem is a bit different than mine was. I was able to get into recovery mode and download mode just fine. I just didn't know which files to flash with.
I intended to flash the JFD that citidin sent me, but I accidentally use the KJ3 (latest I9000M 2.3.3 firmware). The I9000 and Vibrant roms are compatible with the T959D Telus Fascinate though, only problem being no home or search button.
It sounds like the Eugene thing (whatever that is, I'm not familiar) gets you into stock recovery. Like my original issue, you cannot flash or mount the sd card, or much of anything with the stock recovery.
Do you know that the file your flashing is compatible with your phone (the I9000M I assume)? More info that would probably help, is what firmware did you have on it before, was it JFD? What update did you try on it? Bootloader version - there are gingerbread bootloaders, and froyo bootloaders I think?
Have you tried different files other than the one that doesn't seem to boot up for you? I think most of the tutorials I've looked at, said not to check repartition. When i finally got this T959D working with the I9000 rom I did not check repartition and did not select a pit file, just the PDA, phone, CSC.
Yes it is a I9000M - I was trying to load the JFD tar file along with the 512 pit file. I followed a thread in the I9000 section and loaded a JPD tar file onto it, now it shows up as a I9000B - maybe I should stop
I can now get into recovery and or download (i think the steps are differant than hold both volume buttons - mine is holding the volume one way for recovery and the other way for download, along with home and power)
Wondering if I am in this bind because it isnt really what most are calling a Vibrant - maybe under Bell it is something else.
Bootloader? didn't know I had to do anything there
I just picked up the phone used from someone - I assumed it was stock and didn't do a good check to see what was on it.
I9000m is not the Vibrate but rather the Bell version of the Captivate. There is a dev section for the I9000m in the I9000 group.
I would definately stop what you are doing and read over there.
******
Also 350 you can re-map your keys to work but I am mobile now and cant search it for you. Reason being that the. Vibrant keys are laid out differently in, ahh can't think right niece where they are, but it is fixable. Just search key remap or remapping.
Thanks very much for the help - have to wonder why they cant call them the same names regardless of where they are sold - guess thats why they get the big bucks
Hi
There is no specific forum related to this device so I am posting it over here.
I bought LG VU II (F200L) in perfectly working condition, it almost new. After installing LG PC suite and connecting it said new firmware update is available so I proceeded which was done successfully but since then touch screen is not working properly.
Usually it responds ok but main issue is back button is not working anymore, and sometimes when I press power button to unlock screen it responds very weird and not so responsive as well as sometimes doesnt responds or opens apps that I havent even clicked.
I tried to restore, emergency restore, LG Flash tools and used correct KDZ files to flash roms successfully but nothing seems to resolve this issue.
I made some research and the only thing I could find related was Mirror screen which I am not even sure if its the same thing.
Any help will be highly appreciated.
Do a downgrade if you can. If you can't take the phone to a service, much better if you have a warranty.
omega96 said:
Do a downgrade if you can. If you can't take the phone to a service, much better if you have a warranty.
Click to expand...
Click to collapse
The ROM which was running properly before was also JB updated but strangely it was for F200S. I restored its cwm backup but still same problem.
Cant find any KDZ of ICS for VU II or F200 all over internet, all are JB. So I am unable to find any tutorial or files to downgrade it.
Hi there , after soft bricking my phone intentionally because i wanted to downgrade form O to MM which i thought it would be relatively easy to find a stock firmware(the full one) well ...(i was wrong), Xda is not as content rich as you may think, and no one seems to offer any advice or answer for that matter, compared to other forums it lacks a lot.
After flashing more than 5 corrupted firmwares i found one that is working perfectly fine.
Steps:
1-Enter fastboot ( power + vol up)
2- Run (flashall_AFT.cmd) , download link below.... (this is the full firmware no bull**** no missing files) .
That's it... piece of cake
First impression: the bass is more rich and vibrant as many have said so cause the O version was an absolute rubbish like it's battery life , i'm yet to see the battery performance on this MM and i'll be updating the thread with SOT SS after flashing Magisk and installing debloater module.
Download link :
<Mod edit: Link removed>
There are some other newer N full versions but i haven't tested them.
[
i already had that file which i got a few months ago but never used it. i was a noob about this zenfone.
but ur title says its mm, its not , its nougat, 7.11. its the last nougat b4 oreo was released, it uses the same base fw, iirc, as my post about manually flashing 7.11 but without the radios, https://forum.xda-developers.com/zenfone-3-zoom/how-to/manually-update-to-7-11-t3815703
my memory could be wrong though, but file name suggests its 7.11
- [firmware27]WW_ZE553KL_71.60.139.30_MR4_user_20180306173656_release.zip
long story short i eventually flashed it a couple of weeks ago, it does flash successfully, well most of the time, and looks legit, i just wish i knew its original source, i think it was someone named marco, as theres lots of files within that zip.....but it seems legit.
but why are u hosting it on the clickbait site. i might up it to androidfilehost which is a no bs hosting site.
i did create a twrp flashable full stock 6.01 mm firmware, im still testing it as it doesnt always flash completely in twrp, about 8 out of 10 times it flashes correctly. but its hard to test on a dead no display/no touch screen phone
edit: correction, not clickbait, but need to signup
vincom said:
[
i already had that file which i got a few months ago but never used it. i was a noob about this zenfone.
but ur title says its mm, its not , its nougat, 7.11. its the last nougat b4 oreo was released, it uses the same base fw, iirc, as my post about manually flashing 7.11 but without the radios, https://forum.xda-developers.com/zenfone-3-zoom/how-to/manually-update-to-7-11-t3815703
my memory could be wrong though, but file name suggests its 7.11
- [firmware27]WW_ZE553KL_71.60.139.30_MR4_user_20180306173656_release.zip
long story short i eventually flashed it a couple of weeks ago, it does flash successfully, well most of the time, and looks legit, i just wish i knew its original source, i think it was someone named marco, as theres lots of files within that zip.....but it seems legit.
but why are u hosting it on the clickbait site. i might up it to androidfilehost which is a no bs hosting site.
i did create a twrp flashable full stock 6.01 mm firmware, im still testing it as it doesnt always flash completely in twrp, about 8 out of 10 times it flashes correctly. but its hard to test on a dead no display/no touch screen phone
Click to expand...
Click to collapse
Yeah i saw your post a couple of days ago and it is legit , about the file hosting it's not clickbait it's just 4shared and this little guy is older than the xda :laugh::laugh: , i agree that the androidfilehost is faster and more convenient but i'm not the uploader , i just copied it from another source, it would be great if you re-upload it for others and i will update the link.
Now we come to testing: i tested this myself and it is 6.0.1 for sure but i don't remember which release it was cause i updated to 7.1.1 20.32.67.25 release for various reasons, mainly for battery life (spoiler: not much difference and it's still poor) and i will keep flashing / debloating apparently in (in search of incredible) but i'm quite sure this phone is hopeless without a custom ROM from scratch as the amount of services and wakelocks are enormous.
Why don't you participate and use your knowledge in the "allegedly upcoming" Lineage 15.1 hopefully we get a working build before the end of the year :cyclops: i'm sure you are aware of the situation.
And if you're into kernels then kernelwise this phone's kernel was made by noobs ,ASUS put an AMOLED display and they are not using it's features as the blacks are lit and power consumption by the screen is well above an LCD one of the same size.
Long story short buying this phone was/is a mistake.
I actually found the site firmware27 that was hosting 8 ww fw and a couple of cn and jp sku fw.
I tested all 8 ww skus, only 2 work without effort, 6.0.1 dated deb 2017, and the 7.1.1 which I had from a couple of months ago and use the img files in my other thread and which i though u linked here.
Ill be posting a thread and links to both of these files that i ul to afh, and my usage of them, I came to the conclusion that they are asus's fw given to their authorized service centers, they include everything not even available through asus's fw from their site.
Too bad he got most of the files corrupted when he ul'd them to g-drive, my guess
at least now we got 2 fw files to work with, but its a pia to make it a twrp non wipe flashable zip, beyond my skills at this point in time.
edit: i have the one u have linked here which i got a couple of months ago, WW-ZE553KL-11.40.86.71-MR0-user-20170410214554-release.zip,
but firmware27 doesnt have it, and i cant remember where i got it, and by its date youre correct it must be 6.0.1, nougat fw starts with "V20".
so there are actually 3 working fastboot flashable FW out in the wild, boy arent we lucky
i have this phone because a couple of months ago i helped my friend flash fw on it because he was getting poor data signal, i soft bricked and had to learn how to unbrick it, which i did.
its mine as a couple of weeks ago, he dropped it a few feet onto ceramic floor and the screen is dead, no display, no touch, lcd is cracked under the top glass which actually has no cracks, and thats how im using it lol.
i was going to use it as a security camera but i had to learn how to control it remotely, which i did, that was a flashing adventure w/out a working screen
vincom said:
I actually found the site firmware27 that was hosting 8 ww fw and a couple of cn and jp sku fw.
I tested all 8 ww skus, only 2 work without effort, 6.0.1 dated deb 2017, and the 7.1.1 which I had from a couple of months ago and use the img files in my other thread and which i though u linked here.
Ill be posting a thread and links to both of these files that i ul to afh, and my usage of them, I came to the conclusion that they are asus's fw given to their authorized service centers, they include everything not even available through asus's fw from their site.
Too bad he got most of the files corrupted when he ul'd them to g-drive, my guess
at least now we got 2 fw files to work with, but its a pia to make it a twrp non wipe flashable zip, beyond my skills at this point in time.
edit: i have the one u have linked here which i got a couple of months ago, WW-ZE553KL-11.40.86.71-MR0-user-20170410214554-release.zip,
but firmware27 doesnt have it, and i cant remember where i got it, and by its date youre correct it must be 6.0.1, nougat fw starts with "V20".
so there are actually 3 working fastboot flashable FW out in the wild, boy arent we lucky
i have this phone because a couple of months ago i helped my friend flash fw on it because he was getting poor data signal, i soft bricked and had to learn how to unbrick it, which i did.
its mine as a couple of weeks ago, he dropped it a few feet onto ceramic floor and the screen is dead, no display, no touch, lcd is cracked under the top glass which actually has no cracks, and thats how im using it lol.
i was going to use it as a security camera but i had to learn how to control it remotely, which i did, that was a flashing adventure w/out a working screen
Click to expand...
Click to collapse
All you need is one fw to start with and after that you can update to whichever release you want without any problem , strait forward from asus site and update via sd card even if it's rooted or bootloader unlocked, you can do anything and even get updates as FOTA app works as soon as you boot cause asus update procedure is very primitive HOWEVER it should be on stock recovery and honestly twrp is pretty much useless here and i didn't seem to need it in anything with this device!! (i use magisk to root), it's not like there's half a dozen of custom ROMs to flashed , the only possible modification is within the stock fw and that's our limit.
If you find a screen replacement under 50$ it is worth it , i knew that 2.5D glass is poor engineering and very fragile, so screen protector and case was crucial since day 1.
Notes:
Don't trust asus download center's description cause i downloaded the latest nougat release before the Oreo (as described in their section) and it turned out to be the first release of their lousy O fw.
cheapest on ebay is over $70can for aftermarket from china. cheap clone? idk
i'll stick w/my note 4 can version as my dd.
i'll upload the working fw i found for redundancy and to give users more options, 4 fw as of now.
i do have the last 7.1.1 b4 oreo
these are actual service tech fw's available to them for restoring phones. supposedly can be use by asus flash tool which i haven't used yet.
they dont change the bootloader lock status or the frp/google account status (to do that use fastboot wipe config)
since it is in a raw format the individual files can be flashed via fastboot for those that would need it.
fyi all fw are exactly the same except for the recovery, boot, system and , emmc_appsboot_8953.mbn(bootloader ?), the radios and other files are the same
i cant use the builtin updater because i cant seem to get the right button combo to work in stock recovery to flash the update and thats after i reinstall the stock recovery and remove root, flashing from bootloader is a breeze.
the only one i can't get adb enabled so i can mirror the screen is the mm 11.40.86.71, the same one you have linked here
when i try to make a custom stock flashable rom it always fails to boot, would u know why?,
vincom said:
cheapest on ebay is over $70can for aftermarket from china. cheap clone? idk
i'll stick w/my note 4 can version as my dd.
i'll upload the working fw i found for redundancy and to give users more options, 4 fw as of now.
i do have the last 7.1.1 b4 oreo
these are actual service tech fw's available to them for restoring phones. supposedly can be use by asus flash tool which i haven't used yet.
they dont change the bootloader lock status or the frp/google account status (to do that use fastboot wipe config)
since it is in a raw format the individual files can be flashed via fastboot for those that would need it.
fyi all fw are exactly the same except for the recovery, boot, system and , emmc_appsboot_8953.mbn(bootloader ?), the radios and other files are the same
i cant use the builtin updater because i cant seem to get the right button combo to work in stock recovery to flash the update and thats after i reinstall the stock recovery and remove root, flashing from bootloader is a breeze.
when i try to make a custom stock flashable rom it always fails to boot, would u know why?,
Click to expand...
Click to collapse
I would say let's find a solution to the easy problem and not the to hard one, you want to take 2 blurry steps instead of 2 obvious ones !! i can help you with stock ones just explain more what's the exact problem ? i didn't understand so correct me if i'm wrong : you have no visual indication as the screen is dead right ? or can't boot into the stock recovery at all ?
if you have the bootloader unlocked and no screen indication :
power up wait for the vibration and press volume down 4 times then press power to boot into recovery
wait 10 sec and press volume down 2 times to (update form sd card)
rename the fw .zip file to A so it can be sorted first and it should be in root directory and alone to prevent any miss hits and press volume down 1 time.
and if that didn't work just flash the fw that's provided and redo the steps if you want to update , congratulations now you have a working internals and up to date phone that you can't even boot into it's home screen cause the boot confirmation by email and password is near impossible to bypass without a working display. (there is some methods though )
I don't see the point of a phone without a display at least temporary.
This phone is a joke in it's normal condition let alone in the non , don't waste your time and sell it as parts, if you get 40$ take it.
sam.fisher190 said:
I would say let's find a solution to the easy problem and not the to hard one, you want to take 2 blurry steps instead of 2 obvious ones !! i can help you with stock ones just explain more what's the exact problem ? i didn't understand so correct me if i'm wrong : you have no visual indication as the screen is dead right ? or can't boot into the stock recovery at all ?
if you have the bootloader unlocked and no screen indication :
power up wait for the vibration and press volume down 4 times then press power to boot into recovery
wait 10 sec and press volume down 2 times to (update form sd card)
rename the fw .zip file to A so it can be sorted first and it should be in root directory and alone to prevent any miss hits and press volume down 1 time.
and if that didn't work just flash the fw that's provided and redo the steps if you want to update , congratulations now you have a working internals and up to date phone that you can't even boot into it's home screen cause the boot confirmation by email and password is near impossible to bypass without a working display. (there is some methods though )
I don't see the point of a phone without a display at least temporary.
This phone is a joke in it's normal condition let alone in the non , don't waste your time and sell it as parts, if you get 40$ take it.
Click to expand...
Click to collapse
not impossible, very doable to use a phone even with a dead screen.
after alot of trials and error ...from a new flashed stock thats was completely wiped, i can get to a remotely controlled/viewed phone in about 10mins .
i will write up a tut on that.
i can get that done with all the availabe working raw fw except with the mm 2017/04 release
yes, i have a completely dead screen, no display, no touch. all other phone functions work.
the reason for stock recovery procedure was to update to oreo, but i really dont care if i get it. just seeing if its doable.
playing with it for giggles, going to be a security camera as the cam is vg, useless as a phone that has no working screen.
i can be the sacrificial tester if need be, pretty hard to hardbrick this phone as i also have the back cover off so to disconnect the battery connector for those hard soft brick occasions and/or to make sure phone was completely off b4 doing something
I think I killed my phone please help Asus ze553kl
This was happened my phone is Asus ze553kl android Oreo NOTE: I already rooted my phone unlocked bootloader using Asus tool installed twrp and magisk...
when I was using whatapp suddenly my screen got frozen and I restarted my phone it stuck in Asus logo I tried does it goes into twrp even twrp also stuck in logo then I tried flashing using adb and fastboot while doing that I entered this COMMAND fastboot format or erase boot after I flashed everything I rebooted this time it gone worse there is no logo I see only powered by android then no hope after I saw this thread and planned to downgrade downloaded 2gb file and I made clean flashing manually no use i don't see the logo again then I went for auto flashall command when I clicked that something happens it said searching for your device but
After waited for so long I unplugged the cable try to on the phone it's fully blank no sign of power pls help guys I'm begging you all please reply and give me a solution
Nikido2930 said:
This was happened my phone is Asus ze553kl android Oreo NOTE: I already rooted my phone unlocked bootloader using Asus tool installed twrp and magisk...
when I was using whatapp suddenly my screen got frozen and I restarted my phone it stuck in Asus logo I tried does it goes into twrp even twrp also stuck in logo then I tried flashing using adb and fastboot while doing that I entered this COMMAND fastboot format or erase boot after I flashed everything I rebooted this time it gone worse there is no logo I see only powered by android then no hope after I saw this thread and planned to downgrade downloaded 2gb file and I made clean flashing manually no use i don't see the logo again then I went for auto flashall command when I clicked that something happens it said searching for your device but
After waited for so long I unplugged the cable try to on the phone it's fully blank no sign of power pls help guys I'm begging you all please reply and give me a solution
Click to expand...
Click to collapse
sounds like a hardware failure not a software/firmware problem, let it rip, time for another phone, phone not worth getting it repaired even if u do it yourself
vincom said:
sounds like a hardware failure not a software/firmware problem, let it rip, time for another phone, phone not worth getting it repaired even if u do it yourself
Click to expand...
Click to collapse
sam.fisher190 said:
Hi there , after soft bricking my phone intentionally because i wanted to downgrade form O to MM which i thought it would be relatively easy to find a stock firmware(the full one) well ...(i was wrong), Xda is not as content rich as you may think, and no one seems to offer any advice or answer for that matter, compared to other forums it lacks a lot.
After flashing more than 5 corrupted firmwares i found one that is working perfectly fine.
Steps:
1-Enter fastboot ( power + vol up)
2- Run (flashall_AFT.cmd) , download link below.... (this is the full firmware no bull**** no missing files) .
That's it... piece of cake
First impression: the bass is more rich and vibrant as many have said so cause the O version was an absolute rubbish like it's battery life , i'm yet to see the battery performance on this MM and i'll be updating the thread with SOT SS after flashing Magisk and installing debloater module.
Download link :
<Mod edit: Link removed>
There are some other newer N full versions but i haven't tested them.
Click to expand...
Click to collapse
THREAD CLOSED and download link removed. 4shared.com requires to have an account for downloading i.e. not accepted as file host on XDA.
Please advise the moderators' team when ready to provide a download link from an accepted file host.
Hello forum people, I need help to revive my S3 i9300, if you could help me I would really appreciate it.
I tell what I remember about the problem:
The phone was rooteado to be able to use it with any company since it was of movistar. a year ago with the rootking (we sent it to root), the phone was my dad and now has a new one, and it stopped using about 2-3 months.
Then I lent it to a friend who had just broken his cell, so I gave it to him so he has something until he buys one, but he told me that it did not work because he did not load and unload very quickly. He gave it back to me and I stopped using it until about 1 month ago, that I was left without a cell phone and I want to use it to have something.
The same thing happens as it does not load and it is very easy to download, BUT if you use the charger and cable of the Huawei ascend Mate 7 that my dad has, it charges perfectly and the cargo is not cut at all.
Well, seeing that this happened, I restarted it from the factory (I guess the root will be removed with that).
It was still branded and only loaded with the charger and the Huawei cable ...
Well now I tell what happened with what I did.
I install the samsung drivers for the compu, install odin 3.10.6 and under the recovery file that I put up, well I install everything but when I realized instead I read fast and instead of saying PDA said AP in the odin.
Well I try to turn it on and it does not turn on, I try to enter into recovery mode and it does not start.
Then I install another odin, version 1.30 and have a PDA, I do everything as I say start the phone in download mode, home odin, connect the phone to the computer, put the file in pda and give start.
He tells me that everything went well but still does not turn on and without going into recovery mode.
Say that when I do recovery mode (volume up, home and power) I see the logo of samsung and like that desinstegra, then it appears again and blinks in blue but as if it were broken and the logo moves. In short broken.
Then then install another recovery, https://dl.twrp.me/i9300/twrp-3.0.2-...0.img.tar.html
Now I want to enter into recovery mode but this appears and I want to touch some option that appears but nothing, as if the touch was dead.
And after that, it seems to me that I tried to change the Kernel and I put any but the one of my model by mistake.
Current status of the s3:
It lights normally but it takes a long time.
Enter DOWNLOAD mode (vol down, home and Power)
The screen touch does not work but it does show an image.
The buttons work, also the easy button of back and home.
DO NOT enter RECOVER mode (vol up, home and power) is frozen in the Samsung logo.
I want to make it work with any other rom that is functional except the STOCK. And that transforms into unlocekd
It does not matter if when I install a new ROM the files are deleted, I do not have anything in the phone.
Thank you very much to those who respond.
Only to get sure, that I understood you right:
after flashing the wrong kernel, your touch in twrp is not working anymore?
Will say the device is not reacting when you press a button on the screen with your fingers? If so than, I am afraid that your touch is broken. What kernel did you use? Can you post the name of the zip or tar file?
Beside of that, after flashing samsung stock, the reboot will last quite long. Maybe around 15 min till up to 25 or 30. And after flashing and before reboot, go to recovery and make a factory reset. Cross my fingers... :fingers-crossed:
rodman01 said:
Only to get sure, that I understood you right:
after flashing the wrong kernel, your touch in twrp is not working anymore?
Will say the device is not reacting when you press a button on the screen with your fingers? If so than, I am afraid that your touch is broken. What kernel did you use? Can you post the name of the zip or tar file?
Beside of that, after flashing samsung stock, the reboot will last quite long. Maybe around 15 min till up to 25 or 30. And after flashing and before reboot, go to recovery and make a factory reset. Cross my fingers... :fingers-crossed:
Click to expand...
Click to collapse
Hello, if I think that the Kernel had changed I do not remember exactly what it was because I downloaded it on a page written in Asian language by mistake and the Google translator confused the words and he said it was from the s3 but I think it was from the note 3.
The tactile does not respond exactly.
I did not understand him completely, he wants me to enter RECOVERY mode (it takes about 15-20 min to enter) and then do a factory reset?
I almost forgot to clarify that I had tried to do this from the video: https://www.youtube.com/watch?v=fA86_HFGx_w
Everything was installed perfect and I did it as is, except to delete.
Or reinstall the factory rom to see if it worked again.
If you flashed a kernel from note3 that the touch will be most probably minimum damaged and does not work proper anymore. I flashed mistakenly the kernel from the note2 and touch was broken, but maybe you were lucky and your touch is still working. No, passing into recovery should take only a few seconds, but rebooting into system after flashing samsung stock, then in recovery, then wiping and factory reset, could take a rather long time.
rodman01 said:
If you flashed a kernel from note3 that the touch will be most probably minimum damaged and does not work proper anymore. I flashed mistakenly the kernel from the note2 and touch was broken, but maybe you were lucky and your touch is still working. No, passing into recovery should take only a few seconds, but rebooting into system after flashing samsung stock, then in recovery, then wiping and factory reset, could take a rather long time.
Click to expand...
Click to collapse
Could you tell me how to do it please? I'm not an expert at all in changing ROM.
but you wrote that you already flashed something (?) via odin? I understood that you flashed samsung stock rom, beside kernel and twrp to proof, whether phone is working with original sw? If not than please check and search the i9300 forum section, there are a few of howtos and todo threads and posts which explains it even more better, that I could ever do
Edit: for example:
https://forum.xda-developers.com/galaxy-s3/general/samsung-galaxy-s3-sticky-roll-thread-t2344125 and from there for example
https://forum.xda-developers.com/galaxy-s3/help/guide-odin-flash-guide-t1671969
rodman01 said:
but you wrote that you already flashed something (?) via odin? I understood that you flashed samsung stock rom, beside kernel and twrp to proof, whether phone is working with original sw? If not than please check and search the i9300 forum section, there are a few of howtos and todo threads and posts which explains it even more better, that I could ever do
Click to expand...
Click to collapse
I used odin but I forgot how I had done and had followed the steps of a tutorial that I lost the link.
check my edited post above, now with links to guides and one of the best feature here on xda is the search button and that we have many things to read
rodman01 said:
check my edited post above, now with links to guides and one of the best feature here on xda is the search button and that we have many things to read
Click to expand...
Click to collapse
Hello, thank you very much for the links that you have passed me. They will be very useful, excuse me but I do not want to be irritating at all but I am really lost.
My only question is to know how to start reliving it?
I start installing CWN and then change the ROM?
I would recommend to start with flashing the original samsung stock sw via odin. To see that everything is working as it should. If it is so, especially your touch, than you can go ahead with routing, flashing an alternative recovery and testing custom roms, like leo or pie as you posted in the other thread. The time you are spending with writing here and in the second thread you could have already finished the sw flash and reboot to system to check the health of your device. Others than that procedure is a waste of time in my opinion. But thats your decision. On the other hand, we, or better I wouldn't spoon feed you further, because you can find almost everything for that years old device here with search, read read and read.
rodman01 said:
I would recommend to start with flashing the original samsung stock sw via odin. To see that everything is working as it should. If it is so, especially your touch, than you can go ahead with routing, flashing an alternative recovery and testing custom roms, like leo or pie as you posted in the other thread. The time you are spending with writing here and in the second thread you could have already finished the sw flash and reboot to system to check the health of your device. Others than that procedure is a waste of time in my opinion. But thats your decision. On the other hand, we, or better I wouldn't spoon feed you further, because you can find almost everything for that years old device here with search, read read and read.
Click to expand...
Click to collapse
Hello, I did the following, I had tried to re-install the stock stock a few days ago and it did not work, I did it for odin.
So what I did today was, install the recovery mode of ClockWorkMod and probe with the rom of MIUI 8 and that of Linage16, no installation. Then try with this: https://forum.xda-developers.com/galaxy-s3/development/rom-t3442868 And install correctly but it does not work, pass the Samsung logo but then when the ROM logo appears it stays there frozen and restarts ... it seems to me that officially the phone is dead.
Again: the right stock samsung sw should work if flash via odin didn't fail and, what I already mentioned, after flashing you did a factory reset in recovery. After that the reboot into system could take several minutes. Otherwise you can try it with repartition efs backup restore etc etc etc.
btw: newer custom roms, like leo-16, cannot be flashed with the old cwm recovery and cwm touch recovery, as you mentioned in the related thread, would not make much sense, if your touch is broken!?! If you do not want to go via samsung stock sw, then get a newer twrp, search for info which one is suitable, and guides how to flash custom roms, and flash the preferred one of your choice.