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.
Related
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
Title speaks for itself.
I've been lurking the forums for a few months, so... Hi! My tech vocab is limited, but I catch on quickly. Please bare with me.
Anyways, Kies wanted me to upgrade my firmware on my 7.0, so like... Yeah. Stupid me didn't remember that the device was sitting in my lap and connected to my computer WHILE going through the upgrade, and I was feeling uncomfortable, and moved. By doing that, the USB unplugged from the device. I've tried going through with the upgrade via Kies after, but... Just no. Now my device is stuck on the "Firmware upgrade encountered an issue" screen, and no matter how many times I try to reboot it, soft reboot, entering download mode, it always, ALWAYS, goes back to that screen.
So, I plug it in again, and connect it to Odin. But... Wait! I don't have any of the files I need. So I look around and download files instructed by several people for my specific device, but I don't think I need them for this specific problem.
What exactly do I need to get, and how to I put it all together in Odin to make my device work again? I don't really care if all my files get deleted (although it would be great if I could keep them), I just need to get this resolved before Tuesday, since I have textbooks on it that I need for classes.
tl;dr I'm lost, and I need a push in the right direction.
Thanks in advanced!
First, I know how nerve racking this is so I am going to try, and help. I am new to Samsung, but I would think that a stock firmware flash from Odin would fix it. Look in the development forums for officials firmware, and download it. I would give you a link, but you forgot to post what model you have. It can be important. Good luck.
P.S. congrats on joining xda. Sorry it took this o bring you onboard.
Sent from my ADR6425LVW using Tapatalk 2
JeramyEggs said:
First, I know how nerve racking this is so I am going to try, and help. I am new to Samsung, but I would think that a stock firmware flash from Odin would fix it. Look in the development forums for officials firmware, and download it. I would give you a link, but you forgot to post what model you have. It can be important. Good luck.
P.S. congrats on joining xda. Sorry it took this o bring you onboard.
Sent from my ADR6425LVW using Tapatalk 2
Click to expand...
Click to collapse
Ah! Thanks! I can't believe I forgot to post my model ahaha;
p3113.
I'll go ahead and look in that thread. If I come across any other problems, I'll post them here.
Update: I've clarified that I can't enter download mode. How do I go about flashing with Odin if I can't do that?
I got that screen before. Flash again using ODIN and a full charged laptop, do not load any pit file.
churuchu said:
Ah! Thanks! I can't believe I forgot to post my model ahaha;
p3113.
I'll go ahead and look in that thread. If I come across any other problems, I'll post them here.
Update: I've clarified that I can't enter download mode. How do I go about flashing with Odin if I can't do that?
Click to expand...
Click to collapse
looks strange
switch off your device completely, now just press power button and volume "DOWN" button simultaneously and dont leave them.
well, it should not show the "SAMSUNG GALAXY TAB 2 7.0" thing and directly boots the screen into the download mode.
do you mean that, even on doing this too u get the error message as prescribed by you in your above comments--->"error updating firmwire" or something like that??? cz manufacturers first check your device is under warranty or not by entering into download mode(by checking the binary counter) and then booting and checking for root apps(some manufacturers dont check this thing, they just check binary counter)
well for entering into recovery mode u ve to do the reverse----->power button+volume "UP" button, but in this case you it should show that "SAMSUNG GALAXY TAB 2 7.0" thing, as soon as it display you should leave your power button but keep pressing your volume"UP" button.
do you mean even on doing this too you get the same error message?????
if yes, then it is likely that your device is permanently bricked(well, NOT SURE), but then you should consult to samsung for a replacement if its within warranty, else there may be some advanced users or software developers in this forum who may help you, i am just an amateur, sharing my experience with such devices.
Hello, all. I hope someone can help me with my SGH-T959W. Right now I'm at the point where the phone has CWM installed, but will only boot into recovery no matter what I do. I've followed the N00b guide to Flashing/Fixing the SGS4G, but clearly I'm missing something.
I tried to follow the Windows-based procedure for the SGH-T959W, but was unable to get version 1.40 to execute, and was unable to locate version 1.31.
So, given that the SGH-T959W and SGH-T959V are the same phone except for the bootloader, I tried the Java-based Stock KJ-6 + Root. The first time I tried it, the upload failed after the PIT, and the phone was no longer able to boot into anything other than download mode. I eventually managed to get it to the point where it tried to flash the modem, but I was never able to get the modem to flash successfully. I tried both under Windows and Linux, using two different PCs and every USB cable I could find, since I know those tend to be dodgy. Still, I've never gotten past flashing the modem, though sometimes it's done worse.
But at this point, I had a phone that would dutifully boot into CWM, so I could change strategy anyway. So I grabbed the unofficial Cyanogenmod 10.1, copied it to the root of the SD card, and tried to load that via CWM. It failed the hardware check.
That's problem #1. Is it possible to modify Cyanogenmod to check for the 959W instead of only the 959V?
Now, problem #2. I decided to give Slim ICS a whirl, since it's light on requirements and a 512MB/1GHz device would probably appreciate a lighter load. The two packages claim to install, but the progress bar never reaches 100%, and when I try to boot the phone, it just boots into CWM. It's a newer version of CWM now, and the startup logo is different, so something worked, but clearly not everything.
When installing, I did mount UMMU, factory reset, wipe the cache and the Davlik cache, mount UMMU, install, then fix perms. But I still get that loop back to CWM.
So something critical didn’t take, however many times I tried (I've lost count, but I think I'm going on 10), and I don't know the architecture well enough to know where to start looking. I'm pretty comfortable with other operating systems, but this is only the second Android device I've tried to customize.
I suspect I can’t solve any other problem until I solve problem #2, regardless of which distro I end up wanting to run.
Sorry for the long-winded post, but I figured the more questions I answered up front, the better the chances of fixing this would be.
Thanks for any help you're willing to offer a n00b.
Dave F.
I think what you were doing with heimdall is the way to go except the t959w doesn't like modems and I think there's some way to leave out the modem part but eh.. I'm not that well versed. Anyway here's a link that may or may not be relevant
http://forum.xda-developers.com/showthread.php?t=1956025
Please read forum rules before posting.
Questions and request for assistance go in the Q&A section.
Thread has been moved.
Thank you for your future attention to this.
Have a great day!
dfarquhar said:
Hello, all. I hope someone can help me with my SGH-T959W. Right now I'm at the point where the phone has CWM installed, but will only boot into recovery no matter what I do. I've followed the N00b guide to Flashing/Fixing the SGS4G, but clearly I'm missing something.
I tried to follow the Windows-based procedure for the SGH-T959W, but was unable to get version 1.40 to execute, and was unable to locate version 1.31.
Click to expand...
Click to collapse
Look here for 1.3.1.
dfarquhar said:
So, given that the SGH-T959W and SGH-T959V are the same phone except for the bootloader, I tried the Java-based Stock KJ-6 + Root. The first time I tried it, the upload failed after the PIT, and the phone was no longer able to boot into anything other than download mode. I eventually managed to get it to the point where it tried to flash the modem, but I was never able to get the modem to flash successfully. I tried both under Windows and Linux, using two different PCs and every USB cable I could find, since I know those tend to be dodgy. Still, I've never gotten past flashing the modem, though sometimes it's done worse.
But at this point, I had a phone that would dutifully boot into CWM, so I could change strategy anyway. So I grabbed the unofficial Cyanogenmod 10.1, copied it to the root of the SD card, and tried to load that via CWM. It failed the hardware check.
That's problem #1. Is it possible to modify Cyanogenmod to check for the 959W instead of only the 959V?
Click to expand...
Click to collapse
Nope, not a CWM issue. Ever since TeamAcid and I started on CM9 (and I believe the last few CM7 builds) added support for T959W. Almost everyone (thankfully! ) has kanged those device trees and also support T959W. I'm sure other T959W users will chime in to tell you that 97% of all roms here work on T959W. (GB and forward)
dfarquhar said:
Now, problem #2. I decided to give Slim ICS a whirl, since it's light on requirements and a 512MB/1GHz device would probably appreciate a lighter load. The two packages claim to install, but the progress bar never reaches 100%, and when I try to boot the phone, it just boots into CWM. It's a newer version of CWM now, and the startup logo is different, so something worked, but clearly not everything.
When installing, I did mount UMMU, factory reset, wipe the cache and the Davlik cache, mount UMMU, install, then fix perms. But I still get that loop back to CWM.
Click to expand...
Click to collapse
Crazy mount setups shouldn't matter anymore. That was an oldschool Froyo/Early GB thing. Almost all new CWM install scripts do the right thing now.
dfarquhar said:
So something critical didn’t take, however many times I tried (I've lost count, but I think I'm going on 10), and I don't know the architecture well enough to know where to start looking. I'm pretty comfortable with other operating systems, but this is only the second Android device I've tried to customize.
I suspect I can’t solve any other problem until I solve problem #2, regardless of which distro I end up wanting to run.
Sorry for the long-winded post, but I figured the more questions I answered up front, the better the chances of fixing this would be.
Thanks for any help you're willing to offer a n00b.
Dave F.
Click to expand...
Click to collapse
I like the long posts! Especially when then they contain more detail for me to help you figure out your problem with. I'm also partial to the short posts that include logs!
TwitchyEye said:
I think what you were doing with heimdall is the way to go except the t959w doesn't like modems and I think there's some way to leave out the modem part but eh.. I'm not that well versed. Anyway here's a link that may or may not be relevant
http://forum.xda-developers.com/showthread.php?t=1956025
Click to expand...
Click to collapse
@TwitchyEye you're right That is the heimdall oneclick that should be used.
@dfarquhar I think using the heimdall oneclick that @getochkn made should be the right path for you. Make sure you use the right version of heimdall. Make sure you completely remove the old version (software and drivers), use zdiag to make absolutely sure!
If all else fails, post here again! (maybe with logs )
Thanks everyone. I grabbed v 1.3.1, so I'm getting ready to try it now.
If anything goes wrong, I'll look into where the logs are stored and how to retrieve them, and I'll be back. Assuming I can't use the logs to figure it out on my own of course.
dfarquhar said:
Thanks everyone. I grabbed v 1.3.1, so I'm getting ready to try it now.
If anything goes wrong, I'll look into where the logs are stored and how to retrieve them, and I'll be back. Assuming I can't use the logs to figure it out on my own of course.
Click to expand...
Click to collapse
Sometimes, it's just the output you see on your screen is a good enough log
bhundven said:
Sometimes, it's just the output you see on your screen is a good enough log
Click to expand...
Click to collapse
Got it working! Heimdall 1.3.1 was the key. I then turned around and flashed Slim ICS since I had it on the SD card already, and it worked. I'm debating whether to move on to Slim Bean, but maybe I need to leave well enough alone for a few days now that I have a working phone.
Thanks again,
Dave
Please, for the love of god, someone help me!!
I have spent the past 2 days trying to root my brand new Tab 2 (verizon) p3100 (android 4.1.2). I've tried every tutorial that I can find. I've tried various versions of Odin, various versions of heimdall, various versions of CWM and other rooting files. I get error after error. The device still works fine but it WILL NOT ROOT!!
I am currently trying to use Odin3 and CF Auto Root (my 100th attempt probably). Every time I use Odin, any version, any tar file, it fails with a "Fail! (Auth)" error. The message in download mode says "SECURE CHECK FAIL: recovery".
I've done a factory reset of the Tab. I've cleared cache. I've tried running Odin is an admin. I've tried different usb ports on my PC (Windows 7, 64bit).
It doesn't matter what I try, it always results in an error. This thing just WILL NOT ROOT!
Can anybody tell me what the problem is? Or another way to root? Please. This is driving me crazy!!
Thank you!!
Try this.
Huge problem
I found these instructions:
droidviews.com/how-to-root-and-install-cwm-twrp-recovery-verizon-galaxy-tab-2-sch-i705-on-ics-jelly-bean/
And finally got it to root. Then I got to the part where I installed the terminal emulator, granted it root access, and followed the instructions to install aboot.img. Then the Tab shut down, I thought it was going to reboot but it never started back up. Now I can't get it to turn on or go into recovery or download mode. Nothing. Everything was fine up to that point. Now nothing at all. How do I fix this??
ninasmith said:
I found these instructions:
droidviews.com/how-to-root-and-install-cwm-twrp-recovery-verizon-galaxy-tab-2-sch-i705-on-ics-jelly-bean/
And finally got it to root. Then I got to the part where I installed the terminal emulator, granted it root access, and followed the instructions to install aboot.img. Then the Tab shut down, I thought it was going to reboot but it never started back up. Now I can't get it to turn on or go into recovery or download mode. Nothing. Everything was fine up to that point. Now nothing at all. How do I fix this??
Click to expand...
Click to collapse
<facepalm>
Oh boy... WHY the heck did you flash a bootloader (totally unnecessary step to begin with) from a completely different device?!?! There is so much info on rooting P31xx here on XDA, describing several different methods in details, and yet you managed not only to find a way that is not even intended for your device, but to proceed with no understanding of the process whatsoever...
I would suggest to take a deep breath, and try again (and again) to get your tab started in download mode (hold Volume DOWN + Power until you see a warning screen). If you can do that, flash the proper ROM with Odin -- whatever version you can find, but the one for your device. Then promise yourself to NEVER do anything without at least a basic understanding of what you are doing.
If you can't get the download mode working, then look up the service centre. You have an option to play dumb and just say it suddenly died on you -- maybe, you get lucky and could claim the warranty.
EDIT: OK, I am really confused now... You specifically said you have a P3100, but you also mentioned Verizon. So, which one is it that you have -- GT-P3100, or SGH-i705??? These are very different devices! If you indeed have an i705, disregard what I said above (it's relevant to P3110), and start with this thread. It may not be as bad after all...
kt-Froggy said:
<facepalm>
Oh boy... WHY the heck did you flash a bootloader (totally unnecessary step to begin with) from a completely different device?!?! There is so much info on rooting P31xx here on XDA, describing several different methods in details, and yet you managed not only to find a way that is not even intended for your device, but to proceed with no understanding of the process whatsoever...
I would suggest to take a deep breath, and try again (and again) to get your tab started in download mode (hold Volume DOWN + Power until you see a warning screen. If you can do that, flash the proper ROM -- whatever version you can find, but the one for your device. Then promise yourself to NEVER do anything without at least a basic understanding of what you are doing.
If you can't get the download mode working, then look up the service centre. You have an option to play dumb and just say it suddenly died on you -- maybe, you get lucky and could claim the warranty.
Click to expand...
Click to collapse
It's not a different device. I have the Tab 2 from Verizon, which is the i705. I thought it was the same as a p3100 but I guess it's not because verizon locks it down more. The model number, listed in settings, is the i705. So I found these instructions and actually rooted it just fine using odin (finally). When it rebooted, I had super user and all was good. Until the part where it told me to do the aboot.img with the terminal emulator.
I have been trying for the past half hour and cannot get it to do ANYTHING. I've held down every combination of buttons and nothing at all. It will not turn on. It will not go into recovery. It will not go into download mode. Nothing. I plug it into the computer and it's not recognized by the PC (because it's not on). I've plugged it into the wall. Nothing. It will not do anything! I don't know what will happen if I try to take this back to Verizon.
ninasmith said:
It's not a different device. I have the Tab 2 from Verizon, which is the i705. I thought it was the same as a p3100 but I guess it's not because verizon locks it down more.
Click to expand...
Click to collapse
It's more clear now, thanks! I updated my post above, before I read your reply. i705 and P3100 are very different, not just because of customizations by VZW, but technically -- different CPU, chipset, radio module, everything.
One thing I can think of is to just leave it plugged in to the wall charger overnight, and try again. You might also want to ask your question in the respective thread that I linked above. But if you really can't get your tab to show any signs of life, you are out of luck, I guess...
BTW, here is another thread for you, related to unlocking the bootloader on i705.
kt-Froggy said:
It's more clear now, thanks! I updated my post above, before I read your reply. i705 and P3100 are very different, not just because of customizations by VZW, but technically -- different CPU, chipset, radio module, everything.
One thing I can think of is to just leave it plugged in to the wall charger overnight, and try again. You might also want to ask your question in the respective thread that I linked above. But if you really can't get your tab to show any signs of life, you are out of luck, I guess...
BTW, here is another thread for you, related to unlocking the bootloader on i705.
Click to expand...
Click to collapse
Thanks. Yeah I tried for about an hour. I had it plugged into the wall. It would not do ANYTHING at all. I took it back to Verizon and exchanged it. Now I just cross my fingers and hope they don't figure it out.
ninasmith said:
Thanks. Yeah I tried for about an hour. I had it plugged into the wall. It would not do ANYTHING at all. I took it back to Verizon and exchanged it. Now I just cross my fingers and hope they don't figure it out.
Click to expand...
Click to collapse
Good that they exchanged it for you. Better luck next time! Read those two threads I linked, it should give you enough info.
BTW, my apologies if I sounded like an a$$. To be fair, you said you had a P3100, and I didn't realize it was actually a different device until I noticed that you also mentioned Verizon. Looks like you tried to do the right thing, but somehow it went sideways. Well, sh!t happens...
Yep so I tried to install CM11
and the last thing was to:
fastboot flash boot boot.img
and that was it. Cannot restore my Nandroid backup - it doesn't boot back up.
Just gets stuck at the HTC page with "This build is for development purposes".
I think I need the stock boot.img but it is no where to be found.
Any help??
Just paid someone to get the RUU and restore then phone. I have no idea how he found the RUU since no one else here has it. If they have it they are not sharing it.
Who did you find to restore your phone?
808phone said:
Just paid someone to get the RUU and restore then phone. I have no idea how he found the RUU since no one else here has it. If they have it they are not sharing it.
Click to expand...
Click to collapse
I have the same problem. Who did you find to restore your phone? Is it possible that I could contact them?
so basically you paid a guy to google the right RUU???
all you had to do is check your CID (its written on fastboot) and search for that, they really arent that hard to find!!
http://forum.xda-developers.com/showthread.php?t=2140967
also if you're going to keep flashing different roms its also a good idea to keep that RUU on your pc somewhere!!
There was no matching ruu. What no one told me was that you could use a newer ruu than the one you have. Another thing, before you judge, there were no replies to help me so I had no choice. Since then look how many times I have helped others.
chrons6 said:
I have the same problem. Who did you find to restore your phone? Is it possible that I could contact them?
Click to expand...
Click to collapse
As I previously posted, you can use a newer ruu than the version you have installed. That's what the guy did.
In not judging at all man, i just couldnt understand as to why you couldnt fine the info... They guy you paid is no different to you or me, che just searched harder... As for the ruu the name itself tells you its an update... No biggie im glad you got it worked out in the end
Sent from my One S using xda app-developers app
zubeedubs said:
In not judging at all man, i just couldnt understand as to why you couldnt fine the info... They guy you paid is no different to you or me, che just searched harder... As for the ruu the name itself tells you its an update... No biggie im glad you got it worked out in the end
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Did you not read what I said? THERE WAS NO MATCHING RUU! Read OK????
No one told me you could use a NEWER RUU.
If someone - perhaps you had told me, yeah fine, I could have done it. No one helped ok?
BTW: I did a nandroid backup, I had installed custom recovery, rooted with superSU etc... I had adb, fastboot working too. Because I couldn't get an answer I paid someone.
If you have a JTAG machine and you were running a business then maybe you are just like him.
808phone said:
Did you not read what I said? THERE WAS NO MATCHING RUU! Read OK????
No one told me you could use a NEWER RUU.
If someone - perhaps you had told me, yeah fine, I could have done it. No one helped ok?
BTW: I did a nandroid backup, I had installed custom recovery, rooted with superSU etc... I had adb, fastboot working too. Because I couldn't get an answer I paid someone.
If you have a JTAG machine and you were running a business then maybe you are just like him.
Click to expand...
Click to collapse
dude theres no need to get fassy about anything... unless your one s is knock off means that there is a RUU for your device and that you simply couldnt find one in the small amount of time that you searched for one...
and just to gnaw a little more at your flawed logic and sour attitude RUU means "ROM UPDATE UTILITY" so i guess your right in not being able to use a newer one... :good:
AND BTW.. i dont have a jtag but i do run a business and in my line of work we see folk like you everyday, ever so quick to get pi**ed at someone for THEIR OWN mistakes!!!
and maybe if youre that impatient and wound up for your own calamities it serves you right to have paid for a simple task..
---------- Post added at 08:21 PM ---------- Previous post was at 08:14 PM ----------
chrons6 said:
I have the same problem. Who did you find to restore your phone? Is it possible that I could contact them?
Click to expand...
Click to collapse
have a peek at the RUU thread in the dev section and follow the instructions... it really isnt that difficult!!!
? and in my line of work we see folk like you everyday
Right and that's why I have more thanks and posts than you for helping people.
Yes, I know that a RUU has a version number too. I know what it means. If you even took the time to realize that after having to pay, I helped out other people after that so they wouldn't have to pay.
I guess you don't read. I said you COULD use a newer version of the RUU but no one told me.
Where were you when I asked for help? Never mind, you go about yourself and I will continue helping.
In my line of work I know people like you too. You are the type of person people avoid so create your own thread and stop jumping in with unhelpful info.
808phone said:
? and in my line of work we see folk like you everyday
Right and that's why I have more thanks and posts than you for helping people.
Yes, I know that a RUU has a version number too. I know what it means. If you even took the time to realize that after having to pay, I helped out other people after that so they wouldn't have to pay.
I guess you don't read. I said you COULD use a newer version of the RUU but no one told me.
Where were you when I asked for help? Never mind, you go about yourself and I will continue helping.
In my line of work I know people like you too. You are the type of person people avoid so create your own thread and stop jumping in with unhelpful info.
Click to expand...
Click to collapse
about your deluded logic: paying a guy to fix your mistakes is the right info??? seriously?? and thats supposed to help the next guy more than directing him towards the right RUU??? boy you really are a contribution to the comunity...
about your thanks rating: i signed up last month and youve been here since january if youve ever contributed anything on here then you should have more thanks than me, its basic math, also i think i should point out that its a forum and not "thank marathon" nobody wins a prize for them...
as far as helping people: i suppose you have, i dont really care that much either..
lastly: i came on your thread infact to lend a hand, until i saw that youre actually lazy and ready to fire off your mouth at strangers for nothing apart from stating the obvious truth...
so as of now you can take your all your thanks and try and cash them in for the next phone you softbrick and "need" to pay someone else to fix...or maybe not!!!
as for me this discussion is closed as i can only feed a troll so much!!!
808phone said:
As I previously posted, you can use a newer ruu than the version you have installed. That's what the guy did.
Click to expand...
Click to collapse
I understand how the RUU works and how to use it. My problem, though I hope not, may be slightly more unique?
I had previously rooted by ONE S T-Mobile version and it had been working fine. I then decided to try out another rom. I likely flashed an incorrect boot img because it would only reboot into fastboot, but would still allow me to go into recovery. I went to recovery and restored my nandroid backup; however, now the phone will get stuck on the opening HTC screen the red language on the bottom, "this build is for development purposes only." It will hang on this screen for about 20 seconds and then turn off. No loop. When I attempt to power up again, I get a quick horizontal flash of light across my screen and then the orange LED comes on in the top left corner indicating the phone is charging. I then hold down power and again the phone gets stuck on the opening HTC screen with the red language.
My problem is that I cannot get the phone into fastboot
I've received advice on how to enter the bootloader: power off the phone manually by pressing power for 10+ seconds. Then I' should be able to enter the bootloader and fastboot. (Vol down + power)
Unfortunately, no matter how many times I try, using the above method and a variety of other methods, I still can't get past "HTC developmental purposes only" screen. I'm not new to android and have experience with a number of phones, but this is my first HTC. Pretty frustrating thus far. Rather than spend many more hours pulling out my hair and continually going in circles with no progress to show for my efforts, I'd rather pay someone to make the necessary fixes for me.
Any additional advice would be much appreciated.
same problem
zubeedubs said:
about your deluded logic: paying a guy to fix your mistakes is the right info??? seriously?? and thats supposed to help the next guy more than directing him towards the right RUU??? boy you really are a contribution to the comunity...
about your thanks rating: i signed up last month and youve been here since january if youve ever contributed anything on here then you should have more thanks than me, its basic math, also i think i should point out that its a forum and not "thank marathon" nobody wins a prize for them...
as far as helping people: i suppose you have, i dont really care that much either..
lastly: i came on your thread infact to lend a hand, until i saw that youre actually lazy and ready to fire off your mouth at strangers for nothing apart from stating the obvious truth...
so as of now you can take your all your thanks and try and cash them in for the next phone you softbrick and "need" to pay someone else to fix...or maybe not!!!
as for me this discussion is closed as i can only feed a troll so much!!!
Click to expand...
Click to collapse
Just to say that I
chrons6 said:
I understand how the RUU works and how to use it. My problem, though I hope not, may be slightly more unique?
I had previously rooted by ONE S T-Mobile version and it had been working fine. I then decided to try out another rom. I likely flashed an incorrect boot img because it would only reboot into fastboot, but would still allow me to go into recovery. I went to recovery and restored my nandroid backup; however, now the phone will get stuck on the opening HTC screen the red language on the bottom, "this build is for development purposes only." It will hang on this screen for about 20 seconds and then turn off. No loop. When I attempt to power up again, I get a quick horizontal flash of light across my screen and then the orange LED comes on in the top left corner indicating the phone is charging. I then hold down power and again the phone gets stuck on the opening HTC screen with the red language.
My problem is that I cannot get the phone into fastboot
I've received advice on how to enter the bootloader: power off the phone manually by pressing power for 10+ seconds. Then I' should be able to enter the bootloader and fastboot. (Vol down + power)
Unfortunately, no matter how many times I try, using the above method and a variety of other methods, I still can't get past "HTC developmental purposes only" screen. I'm not new to android and have experience with a number of phones, but this is my first HTC. Pretty frustrating thus far. Rather than spend many more hours pulling out my hair and continually going in circles with no progress to show for my efforts, I'd rather pay someone to make the necessary fixes for me.
Any additional advice would be much appreciated.
Click to expand...
Click to collapse
Thankfully I finally figured out how to consistently get my phone to enter into Fastboot; however, no the trouble I'm having is finding the proper RUU. I've tried the 3 T-mobile varients available in the RUU depository found here
http://forum.xda-developers.com/showthread.php?t=2094414
But alas, while I am able to run the RUU program, which enters my phone into a mode where the screen is all black expect for the HTC logo in the middle, I keep on getting error codes. Are there more than 3 RUU varients identified in the depository?
Oh, I should note that I was also able to get into recovery, but my SD was unable to mount so I can't find my Nandroid
Youre at least half Way there, what recovery are you using?? If you can get your PC to see the device try and format the memory to fat32 from PC...
Sent from my One S using xda app-developers app
zubeedubs said:
Youre at least half Way there, what recovery are you using?? If you can get your PC to see the device try and format the memory to fat32 from PC...
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
I believe I'm using TWRP 6.3.0...I'm at work right now and without the phone, but I'm fairly confident that's the recovery. I'll to get the phone into USB mode and see if I'm offered the opportunity to format the memory.
By the way, thanks for the help...it's much appreciated.
chrons6 said:
I believe I'm using TWRP 6.3.0...I'm at work right now and without the phone, but I'm fairly confident that's the recovery. I'll to get the phone into USB mode and see if I'm offered the opportunity to format the memory.
By the way, thanks for the help...it's much appreciated.
Click to expand...
Click to collapse
That won't help. You can fix the sdcrad bug by flashing stock recovery via fastbot and preform "factory reset + clear storage"