Heres the dealio- I have a Charge I want to root and put a custom rom on. I have done this before, with my Inc and my Archos tablet so I'm not a complete idiot.
I did use Odin and thought everything went fine, followed directions to install a zip from the card but the recovery menu never gave me that option. I am unable to get to the sdcard from the recovery menu. I got the option to install the update.zip but thats all. (I followed one of the many thousand "how to root your charge" threads)
Can someone tell me what happened?
Also, the first time I tried to do it, I realized I didn't have the right file, so I pulled the plug on my Charge while in Odin, also because it kept looping. Now Windows XP on that machine won't recognize the phone anymore.
Anyone have any ideas on that?
One more, I read that you need to downgrade the EE4 in order to root? Is that why recovery didn't work the first time, because I have the EE4? (I did see that info AFTER I installed the recovery)
I've been over these threads hundreds of times but I just don't have alot of time and there is alot of redundant information that makes it hard to get anywhere so I'd appreciate if someone could help me out.
willowave said:
Heres the dealio- I have a Charge I want to root and put a custom rom on. I have done this before, with my Inc and my Archos tablet so I'm not a complete idiot.
I did use Odin and thought everything went fine, followed directions to install a zip from the card but the recovery menu never gave me that option. I am unable to get to the sdcard from the recovery menu. I got the option to install the update.zip but thats all. (I followed one of the many thousand "how to root your charge" threads)
Can someone tell me what happened?
Also, the first time I tried to do it, I realized I didn't have the right file, so I pulled the plug on my Charge while in Odin, also because it kept looping. Now Windows XP on that machine won't recognize the phone anymore.
Anyone have any ideas on that?
One more, I read that you need to downgrade the EE4 in order to root? Is that why recovery didn't work the first time, because I have the EE4? (I did see that info AFTER I installed the recovery)
I've been over these threads hundreds of times but I just don't have alot of time and there is alot of redundant information that makes it hard to get anywhere so I'd appreciate if someone could help me out.
Click to expand...
Click to collapse
1) don't choose the option to select 'update.zip', that option doesn't work on the Charge... also it sounds like you were in the stock recover, you do flashing/wiping in ClockWorkMod recovery (CWM)
2) NEVER pull the cord out during an Odin flash unless its been like 30+ minutes and it looks like it froze or nothings happening, this is probably why your phone can't be recognized now (that is a good way to brick your phone and it sounds like you've got one)... now you will need to get the phone into download mode (if it still will) and flash the stock EE4 rom with the Charge PIT file (can't link from phone but these are in the How To Fix Your Phone sticky in Development) and start over
3) I don't quite understand your last question but no you don't need to be on EE4 to root and you can put CWM on any rom with Odin, EE4 at this point is mostly a 'return to stock' rom
blazing through on my 4G Droid Charge
The phone seems to be working fine, but maybe that is why I was in stock recovery mode, because it looks fine, but won't download now. Because I just tried to install a rom and I get an error. I had tried to install CWM, and thought thats what I was going to when I ended up in the stock recovery. I will try the Charge PIT file that you mentioned and see if that fixes anything, and then start over from there. If not I may be returning the phone since it's fairly new.
Thanks for your time
willowave said:
The phone seems to be working fine, but maybe that is why I was in stock recovery mode, because it looks fine, but won't download now. Because I just tried to install a rom and I get an error. I had tried to install CWM, and thought thats what I was going to when I ended up in the stock recovery. I will try the Charge PIT file that you mentioned and see if that fixes anything, and then start over from there. If not I may be returning the phone since it's fairly new.
Thanks for your time
Click to expand...
Click to collapse
when using the pit file be sure to have the repartition box checked in Odin
blazing through on my 4G Droid Charge
I don't have a PIT option on my Odin, or a repartition. It's version 4.13...is there a better version of Odin to work with and stick with? I'm working with 3 different computers here, so I know I have an Odin at home that was working but this one doesn't seem to connect. It's easier to troubleshoot whats going wrong if the proggies I'm using are at least a consistent version number. I DO know I had PIT on the Odin at home but version I'm using (at work) doesn't have it.
willowave said:
I don't have a PIT option on my Odin, or a repartition. It's version 4.13...is there a better version of Odin to work with and stick with? I'm working with 3 different computers here, so I know I have an Odin at home that was working but this one doesn't seem to connect. It's easier to troubleshoot whats going wrong if the proggies I'm using are at least a consistent version number. I DO know I had PIT on the Odin at home but version I'm using (at work) doesn't have it.
Click to expand...
Click to collapse
You need Odin3 1.82 (not just plain Odin). You can get it from http://forum.xda-developers.com/showthread.php?t=1160580
Thanks for the help guys. I got everything back to normal. Drivers and sdcard working properly now. Rooted. Now I just need to get Clockwork back on, and a different rom. Anyone have any fav roms so far? Would love some input on what everyone sees with the different radio builds.
If anyone can answer this, can we get mobile hotspot working on this? Thats a big part of why I need to root and rom this thing.
willowave said:
Thanks for the help guys. I got everything back to normal. Drivers and sdcard working properly now. Rooted. Now I just need to get Clockwork back on, and a different rom. Anyone have any fav roms so far? Would love some input on what everyone sees with the different radio builds.
If anyone can answer this, can we get mobile hotspot working on this? Thats a big part of why I need to root and rom this thing.
Click to expand...
Click to collapse
Everyone will have an opinion on ROM's and radios. My setup is in my sig. As for hotspot, android-wifi-tether works fine on all rooted roms. I've found 3.0pre12 to work the best. 3.1beta6 requires a reboot to get wifi working normally after tethering, but I don't have that issue on 3.0pre12. Be sure to immediately reboot after you install it, and then go in and set your phone type to Samsung Fascinate, and you should be good to go.
I followed the directions of this video on my SGS4G: http://www.youtube.com/watch?v=tR31U0KK2n8
I was trying to flash AOKP and everything went fine until it was finished but the phone went into a boot loop. I went back to "download mode" and attempted to try it again and it didn't work.
I could still get into download mode and flash anything but it wouldn't get past that. Then I decided to give up and I took out the battery and unplugged it (it wasn't downloading at the time). Now I can't even get into download mode, but the phone is would keep booting saying "Vibrant" and then it would go to a pixelated screen.
What should I do? Am I bricked? Can I fix this using Odin or something?
Thanks in advance
http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2
Be mezmerized, and don't ever flash another rom besides the ROM's we have here.
The Vibrant IS NOT the SGS4G. The Vibrant is T959, the SGS4G is the T959V or T959W if you're in Canada. Hopefully 1-click will take you back, but if you flashed a Vibrant bootloader on your SGS4G, you may have bricked it. Hopefully someone with more knowledge can help you, because it seems you flashed the entirely wrong ROM to your phone because it's not for your phone and flashing the wrong bootloader is about the 1 thing that can really brick a phone good.
Looks like I did install the wrong boot loader for my phone which is the sgh-t959v, I used the vibrant instead...is there any way to fix this or am I filly bricked? I can't get into download mode, and the phone is in a boot loop
Try one of the one clicks here in this forum to bring you back to stock
Bhudven's Heimdall One Click and flash with bootloaders. Stay on stock. Read forums. Then keep being on stock ROM. JK... Then try eollie's Heimdall One Click or thomas' Odin Gremlin Remover. With these 2, you should be in a rooted stock ROM. When flashing a custom ROM, check the OP and read the instructions. Make sure it's for your phone.
*I'm tired of giving same instructions over and over again.
Solved
rbedell said:
Solved
Click to expand...
Click to collapse
Is there a tutorial anywhere I can use? Thanks in advance btw...
When I plug my phone into the computer I can get into download mode, I'm guessing from here you just flash back the stock Rom from Odin?
Also, when I use Odin to flash back to stock, do I need to download any other files other than the one specified in this link: http://forum.xda-developers.com/showthread.php?t=1353176
Thanks for everyone's help, I hate to be a bother
@ARsportsfan14
Use bhudven's Heimdall One Click. It's simpler.
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.
Hi all,
for the last three days I've been carrying around a paper weight that looks remarkably like my Galaxy S3...
Anyway, I'm at a point where I don't know what else I could (or should) try. Today I thought I had a winner when I came across this thread: http://forum.xda-developers.com/showthread.php?t=1840030
I thought wrong. Flashing the bootchains works but then when I try flashing the root66.tar in Odin it always fails during NAND Write Start. I have seen people in the above thread with the same problem and then "never mind, I fixed it"-posts without explanations what they actually did... So, if you managed to fix it or know how to fix it, how does it work?
(I can't post in the same thread because I have less than 10 posts..)
Any input would be highly appreciated!
Thanks a lot and happy new year!
Cheers
In detail what did you do before this problem.
ThePagel said:
In detail what did you do before this problem.
Click to expand...
Click to collapse
Hm... a lot of (probably not very wise) things... Let's see...
It all started when I updated CM10.2 to a nightly release. Something went wrong, not sure what. I was talking to someone and when I checked my phone again it was just sitting there in TWPR and wouldn't boot up anymore (stuck in Cyanogen splash screen). I was still able to boot back into recovery and then tried flashing the stable CM10.2, which it didn't do. I factory reset the phone, tried flashing again, to no avail. The error message was that E: data something was missing or not accessible. From then on it's kind of a blur what I actually did, the list includes:
- trying to flash back to stock in Odin
- trying to flash new recovery in Odin
- trying to flash a pit file
- trying to install new firmware in Kies (after downloading the firmware Kies would just quit (PC), or not even download it and tell me that it's not posfible with my phone (Mac))
- trying the method described in the linked thread
At some point I wasn't even able anymore to boot into recovery (I think that was when I tried to flash a new recovery).
Thanks
I had a similar problem a while back: ODIN wouldn't flash anything and I could no longer get to recovery, etc.
I had been running Odin on Windows XP within a Virtual Machine, something that had never been a problem for me in the past. I ran it on native Windows and it flashed fine (root66.tar). If you're running ODIN inside a VM, try that.
http://forum.xda-developers.com/showthread.php?p=47886084#post47886084
-Joe
joeinternet said:
I had a similar problem a while back: ODIN wouldn't flash anything and I could no longer get to recovery, etc.
I had been running Odin on Windows XP within a Virtual Machine, something that had never been a problem for me in the past. I ran it on native Windows and it flashed fine (root66.tar). If you're running ODIN inside a VM, try that.
http://forum.xda-developers.com/showthread.php?p=47886084#post47886084
-Joe
Click to expand...
Click to collapse
Interesting. I am indeed running Windows in a VM... Need to try that later today. I'll report back later in the pm. Thanks!
IT'S BACK ALIVE! Thanks, Joe! Using a native Windows machine did the trick. I didn't use Odin, though, but did a firmware reset in Kies (was easier to do at work). Anyway, phone is up and running again. Next steps are getting CM back...
Thanks again!
Mungo Park said:
IT'S BACK ALIVE! Thanks, Joe! Using a native Windows machine did the trick. I didn't use Odin, though, but did a firmware reset in Kies (was easier to do at work). Anyway, phone is up and running again. Next steps are getting CM back...
Thanks again!
Click to expand...
Click to collapse
Be careful using kies in the future. If they start pushing 4.3 you will be screwed.
Haven't thought about that. It was still 4.1.2 and I'm back on CM10.2.
Thanks!