Is there anyway to deodex the Infuse yet?
probably the same as a galaxy s. gtg465x posted one but we are haveing trouble getting a successful odin package to fix the phone when things go wrong so people were not willing to try it.
Thank you for the fast respond, are we gonna lose the phone if something goes wrong. or if something goes wrong is there a way to fix it.
sinan2010 said:
Thank you for the fast respond, are we gonna lose the phone if something goes wrong. or if something goes wrong is there a way to fix it.
Click to expand...
Click to collapse
well with samsung we are lucky enough to have odin which is a factory flash tool. unfortunately it is not working on the infuse 100%, there may be a new build of it just for the infuse but it hasnt been leaked yet as far as we know. there is also an opensource application called heimdall that works in place of odin. there has been some success with heimdall but the one user that restored with it is having random vibrate issues.
there are still things to figure out, but there is no reason you cant flash with cwm, there are just no proven roms or reliable methods to restore if it goes wrong.
Thanks again. I'll just wait since I'm not good in doing these kind of things.
Just to chime in, you can definitely softbrick the phone if you try to deodex the rom and something goes wrong. I know from experience (happened to me yesterday ) As far as I know, I'm the only one who has successfully flashed back to stock using h8rift's original test tar but now there's confusion about whether it's reliable or not due to other testers' experiences. We're gonna get there just hang tight.
beatblaster said:
Just to chime in, you can definitely softbrick the phone if you try to deodex the rom and something goes wrong. I know from experience (happened to me yesterday ) As far as I know, I'm the only one who has successfully flashed back to stock using h8rift's original test tar but now there's confusion about whether it's reliable or not due to other testers' experiences. We're gonna get there just hang tight.
Click to expand...
Click to collapse
So there are already some people brick their devices and good to know that you have successfully flashed it back.
I just have no idea how to do these kind of things this is my first Android device. I had HD2 and was so easy to do anything. I'm just afraid to brick my infuse, so I'll just wait
I just need to deodex it so I can be able to read and write in Arabic.
Thanks
Hi, I have a motorola milestone xt720.
I recently flashed dext3r's Motoblur on it and it is running fine but it has many bugs and I just want to return to froyo.. Which is my problem.
There are a few problems I am running into
-RSD Lite 4.9 doesn't recognize my phone
-Booting in recovery mode doesn't work (It shows a triangle with yellow exclamation with a phone laying down next to it)
I just can't find a guide that solves my problem, if any one could PLEASE help it would be awesome, i'm sick of the bugs on MOTOBLUR (which by the way was downloaded for XT720)
bmm1893 said:
Hi, I have a motorola milestone xt720.
I recently flashed dext3r's Motoblur on it and it is running fine but it has many bugs and I just want to return to froyo.. Which is my problem.
There are a few problems I am running into
-RSD Lite 4.9 doesn't recognize my phone
-Booting in recovery mode doesn't work (It shows a triangle with yellow exclamation with a phone laying down next to it)
I just can't find a guide that solves my problem, if any one could PLEASE help it would be awesome, i'm sick of the bugs on MOTOBLUR (which by the way was downloaded for XT720)
Click to expand...
Click to collapse
So to solve the rsdlite thing, make sure you have USB debugging on and then it should recognize your phone.
For the recovery issue, what happens after your triangle goes away? How many options do you have? If it is only 4 then you are in stock recovery and not a custom recovery like Androidiani or Mioze's. Both these and their guides are on this General forum.
Now for the "stock" ROM part. Look in the Development threads. There are plenty of options in there from CM6/7, Hellmonger's ROM,...gotta look though. When you say return to froyo, it is cryptic bc aside from Korean, there is no froyo to return too. They are all custom.
Woodrube said:
So to solve the rsdlite thing, make sure you have USB debugging on and then it should recognize your phone.
For the recovery issue, what happens after your triangle goes away? How many options do you have? If it is only 4 then you are in stock recovery and not a custom recovery like Androidiani or Mioze's. Both these and their guides are on this General forum.
Now for the "stock" ROM part. Look in the Development threads. There are plenty of options in there from CM6/7, Hellmonger's ROM,...gotta look though. When you say return to froyo, it is cryptic bc aside from Korean, there is no froyo to return too. They are all custom.
Click to expand...
Click to collapse
-Yes the phone is in debugging mode and it doesn't recognize my phone.
-The triangle doesn't go away, it stays there until i take out the battery again
-I will try those mods but knowing my luck they won't work.. I will use dext3r's froyo is what I mean to return to froyo, go through the whole process of flashing it to my phone again
Thanks for the reply
Put on Mio's CM6 RC3. Best ROM created yet for the XT720 in my opinion, really good stuff.
Definitely don't bother with Dexter's stuff at this point, what with all the amazing ROMs that have been created since Feb of 2010.
I will try that! IF I can get this to work without bricking my phone or anything :'(.
I've about given up on this phone, it has SO many problems and it's just slow in regards to processor speed and internet, 4G is out..
Don't give up on it yet. In the last 4 months we have gotten 4 really incredible ROMs. If you can boot up fully, install Mioze's recovery (I was mistaken before, it is in the Dev threads not General). The install CM6 or Hellmongers and never look back.
Most of us got this phone with a fresh 2.1. Now look what we have, thanks to some very talented people.
Good luck. Bedtime for now.
Edit: Aside from screwing with the bootloader, it is almost impossible to actually "brick" your phone. Get it to be unresponsive, yes. You can flash back to stock sbf and redo everything, but bricking is a tough thing to do.
You can overclock your CPU with Milestone Overclock from the market. Good starting point is 1000/66. Now I am going to bed.
Yeah it can boot fine, I can send messages and everything, it just has numerous bugs.
My god I figured it out....
I had to reinstall the Moto USB Driver because I completely forgot that I had to swipe my computer about a month ago and it uninstalled!
Much stress and anger lifted off of my shoulder !!!!!!!!! I can get it from here!
Woodrube said:
Edit: Aside from screwing with the bootloader, it is almost impossible to actually "brick" your phone. Get it to be unresponsive, yes. You can flash back to stock sbf and redo everything, but bricking is a tough thing to do.
Click to expand...
Click to collapse
Lol, yeah that is so true. I remember how scared I was when I first flashed dexters the very first time. New to ubuntu, new to android yipe. Its actually pretty close to impossible to brick a phone unless you tamper with bootloaders like you mentioned.
My father in law bought a new phone SGS on O2 and I offered to unlock it as I have unlocked my husbands last week (he's was on O2 as well but in 2.1 or 2.2.1 version I think-froyo?)
Before I continue may I say I know you guys out there know so much more than me and I really need your help. I really tried to help unlocking this phone and for hours I searched and read things like reboot, download mode, recovery mode, flashing, JKV and so many other words and letter that I could not understand. Very few I understood in the end but may have messed up badly (?).
Please, I need help and please treat me as if I were your mum or even grandma. Step by step in simple normal English please.
My father in law's version is 2.3.3
I tried unlocking it the way I unlocked my husband's but didn't work after looking for hours I thought that the best way to do it would be to downgrade from 2.3.3 (gingerbread (?)) to 2.2.1 (froyo (?)) and then unlock it.
I found this:
http://forum.xda-developers.com/showthread.php?t=1089989
and tried to follow it.
I downloaded EZRom and EZboot-Froyo-1.0.tar.md5 from the same post.
I followed:
•Download the right version from section above
•Reboot your phone into Download mode
•Connect your phone to computer
•Run EZOdin
•Select EZboot-Froyo-1.0.tar.md5 or EZboot-GingerBread-1.0.tar.md5as a PDA file in EZOdin
•Check the "Phone Bootloader Update" checkbox
•Click Start
I waited for the phone to turn off and feel the little vibration but didn't. Instead it just froze at the first screen when you turn on the phone. The black background with white letters: Samsung Galaxy...
I waited and waited and as nothing was happening I then I took the battery out. Put it back in and tried turning it on. I wouldn't it would just stop and that same screen, the black and white one.
I reread
•Wait until phone reboots and make it reboot into Recovery
SO then I remembered in the many threads I read about the recovery mode so 3 clicked vol up + button at them bottom and turn on bottom.
It gives me a few options. When I click on reboot all it does is show me the black and white screen again and nothing else. ah!!!
I took the battery off and put it back on may times, also selected the fatory reset option and tried different buttons but nothing. Please help me.
I'm happy to phone any of you guys to help me and guide me even if it's just to put the phone back to what it was before, turning on normally, etc. (I can't even turn it on!) I'm feeling really sad and a bit stressed as these days are supposed to be a nice time to spend with my little ones and family.
Anyway, please ask me anything.
Thank you so much in advance. I really hope I didn't do anything wrong and I'm just stuck because I'm ignorant in this matter. Thank you
Well, I have no skill in this area. But I wish you good luck, and this post is acting as a bump! Double goal!
After a little rethinking: (I don't have a SGS and never touched one) You can try re-stocking the phone. Not sure how you do that. I'll check.
From http://forum.xda-developers.com/showthread.php?t=723596 :
Darkstriker said:
(E) Recovery:
1.WHAAAA! I think I bricked my phone. My flash was unsuccessful/My device boots to a black screen/similar scenarios. Can I still save my device?
1.WHAAAA! I think I bricked my phone. My flash was unsuccessful/My device boots to a black screen/similar scenarios. Can I still save my device?
Most likely: YES! In almost any case, you should still be able to turn off the device (if necessary by removing the battery) and start into download-mode (VolumeDown+Home+Power) or recovery-mode (VolumeUp+Home+Power). After (for example) an unsuccessful flash, you can retry the flash in download-mode (same steps as when flashing a functioning device). If a flash to a functioning f/w (without applying any update.zip) doesn't help or you cannot get your PC to flash at all, you can ask for help here.
If you see a symbol asking you to connect to the PC, depending on how you arrived at this point, it may be sufficient to connect to the PC and run Odin (i.e. press "start" when the phone is recognized) without adding any files. This may, however, leave some residual issues if (for example) had an incorrect/incomplete flash so you may want to do a normal flash after this!
If you do not have download mode and for some ludicrous reason felt the need to go ahead and modify your firmware regardless of this lacking, there is now a guide on creating a home-made JIG which will force your device into download mode without the actual button combo here.
Click to expand...
Click to collapse
If you need any extra help, I'll try.
Im somewhat of a rookie user too but I do know this, If you can still go into recovery/download mode (using the 3 button combo) then you havent bricked the phone and you can fix it! so dont stress too much .
EDIT: Im guessing you can download a stock ROM and flash it via odin.
[/QUOTE]
After a little rethinking: (I don't have a SGS and never touched one) You can try re-stocking the phone. Not sure how you do that. [/QUOTE]
Thank u so much for your reply. O don't know what re stocking is, but i will look into it. Thank u!
I don't know how to re stock it.
Sorry to seem so dumb.
Can anyone help me step by step? If at all possible could I phone someone to help me with this? Send me phone number via private message
Thank you sooo much.
anaki11 said:
I don't know how to re stock it.
Sorry to seem so dumb.
Can anyone help me step by step? If at all possible could I phone someone to help me with this? Send me phone number via private message
Thank you sooo much.
Click to expand...
Click to collapse
Well, no problem, I guess. I don't think it needs to come to voice support, to be honest. I think text is enough for the issue in matter. I'll look a bit into this, I'll have to go soon from my computer. I'm sorry if I can't be of any greater help.
moses992 said:
Im somewhat of a rookie user too but I do know this, If you can still go into recovery/download mode (using the 3 button combo) then you havent bricked the phone and you can fix it! so dont stress too much .
EDIT: Im guessing you can download a stock ROM and flash it via odin.
Click to expand...
Click to collapse
Your post helped me not to stress too much.
I'd like to download a stock rom and flash it but I don't know how to.
Here's where I am. I found a list of firmware. This is the last one on Samfirmware.com.
Europe Samsung I9000 Firmwares.
I9000XXJVS ##
512.PIT
2.3.5
2011 September 8
CSC = I9000OXAJVS
DOWNLOAD
Things I need: (I think)
-Download a firmware (should I use the lastest one?) or 2.2 or 2.3.3? . Is there one better than the other? or is it my choice? How can I choose the best one for me?
-Odin. I have OdinMultiDownloader v4.03 in my desktop. Is that the best thing to use or should I use Ezodin. I don't know what the difference is.
-(Do I need to download or do anything else?)
Things I should do:
-Put phone in download mode
-Plug it to the laptop
-Open Odin (or Exodin?)
-click PDA. Choose the fie I downloaded-firmware.
(-after this I don't know what else I should do or tick or untick)
Am I in the right track or completely off it?
Thank you again to anyone taking the time to read this.
anaki11 said:
Your post helped me not to stress too much.
I'd like to download a stock rom and flash it but I don't know how to.
Here's where I am. I found a list of firmware. This is the last one on Samfirmware.com.
Europe Samsung I9000 Firmwares.
I9000XXJVS ##
512.PIT
2.3.5
2011 September 8
CSC = I9000OXAJVS
DOWNLOAD
Things I need: (I think)
-Download a firmware (should I use the lastest one?) or 2.2 or 2.3.3? . Is there one better than the other? or is it my choice? How can I choose the best one for me?
-Odin. I have OdinMultiDownloader v4.03 in my desktop. Is that the best thing to use or should I use Ezodin. I don't know what the difference is.
-(Do I need to download or do anything else?)
Things I should do:
-Put phone in download mode
-Plug it to the laptop
-Open Odin (or Exodin?)
-click PDA. Choose the fie I downloaded-firmware.
(-after this I don't know what else I should do or tick or untick)
Am I in the right track or completely off it?
Thank you again to anyone taking the time to read this.
Click to expand...
Click to collapse
In my thoughts, I believe that should be what you need. You can try, if that doesn't solve the issue, it's because you need something else as well.
And the think you should make the file a PDA file, I believe. Don't take my answer too direct. I'm almost unknown with Samsung devices on that matter, but I can say a couple of things, like, that, I'm pretty sure it is on PDA files.
And no problem, always pleasing to help someone in trouble. I was/am a rookie too Ignore the Senior Member thingie. Still a noob in pretty much everything. And don't panic, no need for that.
Thank you. I should try that tonight unless someone stops me before to tell me I'm about to make another mistake.
anaki11 said:
Thank you. I should try that tonight unless someone stops me before to tell me I'm about to make another mistake.
Click to expand...
Click to collapse
Haha. I doubt it. 99,99% of actions are reversible, really. And I have severe doubts that this is one of the remaining 0,01%.
Well, I wish you good luck. If you ever need any more help, you can post here. I'll look into here time to time.
BTW. Just wait a second. You know that link you give on the first post? There's also a Gingerbread file. You can *try* flashing that one, to see if it reverses the problem. Sounds legit to me.
Youtube.com/qbking77
He has tons of tutorials
Sent from my SPH-D700 using Tapatalk
I don't know where to post this, I'm coming here all panicked and retarded, so I'm apologizing in advance.
I literally bought my Galaxy S 4G from WIND (Canada) this morning. From what I understood, upgrading the OS was dangerous, all I wanted to do was root... I followed this guide: ht tp ://w ww.gal axyforum s.ne t/forum/off-topic-forum/5053-rooting-tutorial-here-posted-permission-t-mobile-galaxy-s-4g-gingerbread.html (remove spaces)
which I found in a post on these forums. Someone who also was on WIND said it worked fine for them... They were rooted. I foolishly tried it, everything seemed FINE. When I load CWM it can't mount my SD card. I don't know what to do, it's stuck in T-Mobile boot screen loop if I try to exit.. I literally just stopped crying. My dad is going to KILL me if he finds out I ****ed up the new phone I just bought HOURS ago. I don't know what the **** to do, I don't know what's wrong. I need help, please. Anybody know what I can do? I don't care about rooting, I just need my device to work. Please, someone, anyone with any idea, what should I do? I can get back into download mode, and CWM. Is there anything I can do there? There's a recovery guide pinned but it says it's for the T-Mobile version, which I read is the same, can I use that to fix my phone?
This is my first Android device, I've never owned one before. I don't know ****, I shouldn't have tried anything... I just got cocky and made a mistake. I'm usually very good with this kind of stuff. Please someone tell me if there's something I can do to fix this, please!
I'm sorry if I sound stupid, I'm trying not to, I'm just really panicky and stressed right now.
I've tried searching through the forums - I still am searching through them, I'm sorry if I missed a post that can help me.
EDIT: I found someone who is also stuck in a boot loop... He seems to have SD Card issues as well, but doesn't speak English very well, so I don't thing he was able to communicate what his issue was...
Quote:
Originally Posted by GMK63
.......(---------THAT WHAT I FOLLOWED .
But I did the first part and They said i should get the stuff I store on my SD Card to pull out a file (``12) In CWM, use your volume up/down positions to navigate, scroll down to "Install Zip From SDcard". Select with a click of the power button. Navigate to where you put sms-T959V-KJ6-v0.1.1-rc1-unsigned-update.zip (in the root of your SDcard) and select with the power button. Confirm you want to install.
``)
but it doesn't give me the option to go get it on my SDcard and Now my Phone just turns on and off with the samsung galaxy S logo plus T-mobile exclusive logo . The only possitive thing about all the damage is that I can still put my phone on dowload mode and I just think if someone knows how to get my phone back to it state they will need me to put it on download mode.
Thank you in advance for your Help, for replying and offering to help.
I appriciate it. My phone is Mobillicity carrier just like wind .[/B]
Then, user bhundven replies to him saying:
Ok, this is really simple. I've explained it in quite a few threads in the Galaxy S 4G forums in General, Q&A, and the Dev forum. I'm going to explain this, but in a way to be more general. So I'm being verbose in case anyone else with a T959W happens to run across this and has not tried anything yet.
Again, I'm not good with windows at all, and I prefer it that way.
If you're on windows, check out our wiki:
http://forum.xda-developers.com/wiki...xy_S/SGH-T959V
There is tons of help there for setting up heimdall on windows with all the right drivers and such.
Once you have heimdall setup get AntonX's latest cwm zip for his kernel.
This kernel is a BML kernel, and this guide I am giving you right now will help you get cm9 installed which is an MTD kernel. You can find out more about BML vs. MTD here.
Once you have downloaded AntonX's kernel, extract the zImage from it and open up the terminal/cmd prompt and navigate to the directory you extracted the zImage to.
Put your phone into Download Mode and type the following in the command prompt:
Code:
heimdall flash --kernel zImage
The heimdall program will flash this kernel+initramfs to the kernel partition and reboot the phone. Do not unplug the usb cable until you see the "Galaxy S" screen. When you see that screen, unplug the usb cable and remove the battery from the back.
Assuming you downloaded CM9 and put it on your sdcard already, you can get into recovery by holding the vol+ and vol-, then pressing the power button to turn the phone on. When you see the "Galaxy S" screen, let go of the buttons, and you should be in the recovery now.
This is where things get a little tricky. If you have not tried to do anything to your phone yet. This would be a great time to use the "Backup and Recovery" menu on CWM. Do a full backup.
The "assert 7" error that the previous person got was because the cwm install script (the updater-script) checks the already installed /system/build.prop's data against the "to be installed" build.prop to verify this rom can be installed. If it doesn't exist, then it moves forward.
So the first order of business is to wipe the /system partition. Go to "Mounts and Storage" and format the system partition.
Now go back to the main screen and do "Factory Reset/Wipe Data".
Now go "Install zip from sdcard" -> "choose zip from sdcard" -> and use the volume keys to select the zip file.
After the rom is installed, navigate back to the main screen and "Reboot the system now" if it doesn't reboot by itself.
When the phone reboots, because it is going from BML to MTD, it obviously can't just install the files to what would be an MTD partition if the kernel knows nothing about MTD. So it boots into the newly installed MTD kernel and continues the installation, which in the end will also reboot again.
The first boot is very slow. It is building a cache of all the pre-installed system applications. Let it sit for a while. I know it's tempting to go play with your phone right away, but resist if you can.
The next CM9 release will be on a different kernel, and albeit a much better rom.
I will also be adding OTA Asserts for SGH-T959W so that you will not have to wipe /system before installing the rom, but I do that still just for good measure. But this also means that your phone will work properly with the google play store.
If this still does not work, please let me know what went wrong and I will be happy to assist!
-Bryan
Is what Bryan is saying my solution? I don't think he understood the SD Card mount issue. Does anyone know how to fix that? I really hope to hear from you guys ASAP before my dad catches on... Please. I really need help. I'll search more in the morning, it's 1 AM here.
Okay well first of all.. GET A GRIP OF YOUR SELF
*slaps twice across the face
This phone is unbrickable so can you get in to download mode? (power off phone then when it's off hold the volume up and down buttons at the same time, while holding them down connect your phone to a usb cable)
A green android digging thing should show on your screen. Tell me when you get this far.
Sent from my HTC VLE_U using xda app-developers app
As a matter of fact, you don't entirely need a download mode screen to recover your device too. I've gotten to a pixelized colorful screen and thought my phone was done for, but Odin/Heimdall still recognized it, so I was able to recover my phone.
Calm down and as long as your phone can still be detected on your computer, you will be fine. Odin or Heimdall should be able to show that he device was "added" when you plug it in.
bkoon1218 said:
As a matter of fact, you don't entirely need a download mode screen to recover your device too. I've gotten to a pixelized colorful screen and thought my phone was done for, but Odin/Heimdall still recognized it, so I was able to recover my phone.
Calm down and as long as your phone can still be detected on your computer, you will be fine. Odin or Heimdall should be able to show that he device was "added" when you plug it in.
Click to expand...
Click to collapse
That's true, just make sure you have the drivers installed for the phone first and for the purpose of my method of recovery download Odin. If you did everything correctly you'll see a green light in Odin under recognized devices once you're in download mode
Sent from my HTC VLE_U using xda app-developers app
lonoguge said:
Okay well first of all.. GET A GRIP OF YOUR SELF
*slaps twice across the face
This phone is unbrickable so can you get in to download mode? (power off phone then when it's off hold the volume up and down buttons at the same time, while holding them down connect your phone to a usb cable)
A green android digging thing should show on your screen. Tell me when you get this far.
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Thanks for the slaps, I needed them!
Yes! I think I am still able to get into download mode, atleast I was able to last night (After the loop issue). Also, I formatted (factory reset option or something?) my settings when I was in CWM last night assuming that would change it back to the way it was, or atleast fix the SD mount problem..I hope this doesn't cause any issues.
What should I do when I'm in download mode?
bkoon1218 said:
As a matter of fact, you don't entirely need a download mode screen to recover your device too. I've gotten to a pixelized colorful screen and thought my phone was done for, but Odin/Heimdall still recognized it, so I was able to recover my phone.
Calm down and as long as your phone can still be detected on your computer, you will be fine. Odin or Heimdall should be able to show that he device was "added" when you plug it in.
Click to expand...
Click to collapse
That's great news! It's nice to hear that someone who's phone was also messed was able to repair it.
lonoguge said:
That's true, *just make sure you have the drivers installed for the phone first and for the purpose of my method of recovery download Odin. *If you did everything correctly you'll see a green light in Odin under recognized devices once you're in download mode
Click to expand...
Click to collapse
Where can I get these drivers? Should I download the latest version of Odin?
I'll try this as soon as I get back from taking my little sister to school.
I just want to say again, this is the SGH-T959W from WIND in Canada. It's apparently the same hardware as the SGS4G from T-Mobile, just different software. I hope this isn't a problem.
Thank you both for replying so soon. After tossing and turning in bed for the last 5 hours, barely getting any sleep, it's such a relief to read these posts!
Obviously you didn't read too much if you bought the phone and tried to mess with it the same day. You would have seen if you went to the 2nd page of here and actually read something like this, http://forum.xda-developers.com/showthread.php?t=1552119 where I clearly say, it is it different, you will get boot looped, I am working on a package to fix it, and for anyone on a wind phone to hold on and wait.
I don't have time to try and help and fix every single wind phone in the world because people get too impatient and start flashing everything in the world from the first post they read. Odin and Heimdall fail at certain parts of flashing this phone. I am trying to give the Heimdall creator as much as I can to help fix this, so everyone telling to flash this or that package, it's not going to work, it will fail. I have verified this 100 times with Heimdall.
I can't put together a 1click package that fails flashing, that's why people are ending up in this position in the first place.
I can get your phone fixed but not right this second. There is no permanant damage done, and the less you just keep flashing random stuff, the more likely the chance I can help you fix it, but I'm busy, I run my own business and my paying customers come first as does my mortgage and bills before spending an hour teamviewed into someones pc to fix this.
So hang tight, I will try later to get this fixed, it's not screwed, quit flashing anything you find.
Past what getochkn just said (and please do ignore the "advice" given by people who don't experience with a T-959W), next time you see a "helpful" post on some site that starts off "get this from [the original source]" -- please, please take the time to read the original source.
Secondly, just because your phone has the a similar "trade name" as another phone doesn't mean they are even close to the same inside. Even the model numbers don't mean much. Firmware from a T-959 generally won't work on a T-959V, and, as you have found out, T-969V firmware can make a T-959W a nice paperweight for a while.
Thirdly, I just don't "get" why people even consider flashing their phone on the first day they own it, before they have any idea what it came with and what it can do, not to mention voiding their warranty before even the buyer's remorse period has expired.
While you're waiting for someone to bail you out, you might want to take the time to download Java, the Microsoft C++ executables, and a full version of Heimdall.
getochkn said:
Obviously you didn't read too much if you bought the phone and tried to mess with it the same day. You would have seen if you went to the 2nd page of here and actually read something like this, http://forum.xda-developers.com/showthread.php?t=1552119 where I clearly say, it is it different, you will get boot looped, I am working on a package to fix it, and for anyone on a wind phone to hold on and wait.
I don't have time to try and help and fix every single wind phone in the world because people get too impatient and start flashing everything in the world from the first post they read. Odin and Heimdall fail at certain parts of flashing this phone. I am trying to give the Heimdall creator as much as I can to help fix this, so everyone telling to flash this or that package, it's not going to work, it will fail. I have verified this 100 times with Heimdall.
I can't put together a 1click package that fails flashing, that's why people are ending up in this position in the first place.
I can get your phone fixed but not right this second. There is no permanant damage done, and the less you just keep flashing random stuff, the more likely the chance I can help you fix it, but I'm busy, I run my own business and my paying customers come first as does my mortgage and bills before spending an hour teamviewed into someones pc to fix this.
So hang tight, I will try later to get this fixed, it's not screwed, quit flashing anything you find.
Click to expand...
Click to collapse
THANK YOU THANK YOU THANK YOU THANK YOU THANK YOU!
I really didn't read enough, big mistake, I was just really cocky because I've modded almost every device I own (Wii, PSP, PS3, PS2 various and iDevices [mine, and friends]). Of course, they're all different (Not saying it's all the same thing! ), I just felt very confident because I've never had issues with anything before. At least this is a good learning experience, I've really been put in my pace. I always felt that bricking was something that happened to other people, it doesn't happen to me. I know that sounds stupid, but idk, that's just how I felt. I physically feel sick over this 'whole ordeal (Seriously), I'm such an idiot. >.<'
Thanks for the warning, I won't flash anything! I'm so relieved to hear that there's no permanent damage done, and to be able to speak to someone who's familiar with this specific problem and this specific model of the SGS4G, AND is willing to help me!
Do you know when you'll be able to help me? Of course, take your time, I completely understand that you have other stuff going on, I'm just wondering to see if I can maybe think of some cover up so my dad doesn't find out.
Also, I have a 14 day warranty, is it void now even though the root didn't work? I'm assuming it is.
Edit: Yup, if what jeffsf says is true, it's void.
jeffsf said:
Past what getochkn just said (and please do ignore the "advice" given by people who don't experience with a T-959W), next time you see a "helpful" post on some site that starts off "get this from [the original source]" -- please, please take the time to read the original source.
Secondly, just because your phone has the a similar "trade name" as another phone doesn't mean they are even close to the same inside. Even the model numbers don't mean much. Firmware from a T-959 generally won't work on a T-959V, and, as you have found out, T-969V firmware can make a T-959W a nice paperweight for a while.
Thirdly, I just don't "get" why people even consider flashing their phone on the first day they own it, before they have any idea what it came with and what it can do, not to mention voiding their warranty before even the buyer's remorse period has expired.
While you're waiting for someone to bail you out, you might want to take the time to download Java, the Microsoft C++ executables, and a full version of Heimdall.
Click to expand...
Click to collapse
I'm just very impatient sometimes. I really do enjoy doing this kind of stuff, it's fun for me. I just got really excited and wasn't thinking straight and just went out and tried rooting it. I've wanted an Android for a while now, and have always planned to root it to unlock it's full potential. I've never modded anything else day 1 (and never will again), this is the first time I've done this. I feel terrible about it.
Will do, thanks for helping, jeffsf.
If your still under 14 days return it with a stupid I don't know what happened look. If its stuck just on the tmob screen they most likely will never know what you did. Your other choice is to be a man and own up to it. Tell your dad and take your lumps. That choice is yours. Give it serious thought before you choose as it might define what type of person you end up becoming.
hechoen said:
If your still under 14 days return it with a stupid I don't know what happened look. If its stuck just on the tmob screen they most likely will never know what you did. Your other choice is to be a man and own up to it. Tell your dad and take your lumps. That choice is yours. Give it serious thought before you choose as it might define what type of person you end up becoming.
Click to expand...
Click to collapse
I feel like they might know. I'm willing to try it as a last resort, I'd like to give getochkn a shot first.
I'll tell my dad what happened after it's fixed. I just can't deal with him stressing me out about it more than I already am.
I will have a package probably tomorrow that will provide as detailed instructions as I can.
getochkn said:
I will have a package probably tomorrow that will provide as detailed instructions as I can.
Click to expand...
Click to collapse
Oh, wow! That's much sooner than I was expecting! Thanks for taking the time to do this for me, it really means a lot. Thank you so much getochkn!
Package and instructions here.
http://forum.xda-developers.com/showthread.php?t=1956025
getochkn said:
Package and instructions here.
http://forum.xda-developers.com/showthread.php?t=1956025
Click to expand...
Click to collapse
Thank you so much getochkn!
I read all the instructions before attempting this. But, I have a problem. Heimdall failed to flash. It said something about failing to retrieve the PIT or something? So, I tried again. Didn't work. So, I restarted my computer, and my phone.
Phone doesn't go into download mode, instead, I end up on a screen saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
What should I do?
BagelBreath said:
Thank you so much getochkn!
I read all the instructions before attempting this. But, I have a problem. Heimdall failed to flash. It said something about failing to retrieve the PIT or something? So, I tried again. Didn't work. So, I restarted my computer, and my phone.
Phone doesn't go into download mode, instead, I end up on a screen saying "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
What should I do?
Click to expand...
Click to collapse
That firmware screen should detect as download mode still in Heimdall. I have gotten that and reflashed from Heimdall before. Not sure why it's trying to download the pit, it should only do that when you tell it to download pit. Flashing shouldn't trigger that. See if Heimdall will detect it in that firmware recovery mode and I guess try again, otherwise your phone is really borked.
getochkn said:
That firmware screen should detect as download mode still in Heimdall. I have gotten that and reflashed from Heimdall before. Not sure why it's trying to download the pit, it should only do that when you tell it to download pit. Flashing shouldn't trigger that. See if Heimdall will detect it in that firmware recovery mode and I guess try again, otherwise your phone is really borked.
Click to expand...
Click to collapse
Thank you for the quick reply!
It worked! I really can't thank you enough! Thanks again for taking the time to do this!
I think it may have said "Uploading Pit" because it said it again this time, but it didn't encounter a problem when it did that.
I know I have 3 choices, the one I would like to choose is ICS. Would mind pointing me in the direction of an ICS ROM that's compatible with my device? I'm afraid to use something that may not work and mess up my phone again.
EDIT: Actually, I think I'll just stick with this. I just installed the twist kernal and the modem, everything works, I'm rooted and have recovery. I'd rather not mess with it until I'm more experienced with droids.
Thanks again everyone, especially you getochkn! I'm so relieved that my phone is working again! My dad didn't notice that I wasn't using the new phone I got, so I didn't have to cover up or anything.