Related
I'm completely new to the android experience, this is my first smartphone, ever. I recently purchased an unlocked myTouch 4G and from time to time I would plug my phone into it's charger and it would just cut off and reboot, and stay in this reboot cycle anywhere from 1 - 15mins.
I'm not sure what the issue could be, I don't have a warranty for the phone. I factory reset it using the software since i can't hard reset it from the bootloader. If I try to do that from the bootloader it will just take me through the rebooting cycle again. When I boot into the bootloader it's frozen for about 5 seconds and shows some error about a ZIP file on my SD card not being found (I'm assuming it's looking for an Android image).
This reboot cycle mostly happens when I'm dealing with plugging it in a charger, rarely it will do this when I power off the phone or reboot it from the software (the proper way). Unless I take the battery out, while the phone is off, I never pulled the battery while the phone is running.
What are some options available to me?
Go here
http://forum.xda-developers.com/showthread.php?t=1244018
and follow the instuctions. It will give you a link to the zip file the bootloader is looking for.
Sent from my HTC Glacier using XDA
dead links
Megaupload is dead, I can't use that post. I'm not even sure what the poster is informing people to do, looks like a downgrading. I'm not trying to downgrade, my phone is stock (as far as I know, it's running froyo 2.2.1).
Also I have no clue how to go into adb.
Here is Froyo http://www.4shared.com/zip/xa6viHf-/PD15IMG_221_.html
You won't be downgrading. Just download and flash the file. Its froyo.
jjbadd385 said:
Here is Froyo: 4shared.com/zip/xa6viHf-/PD15IMG_221_.html
Click to expand...
Click to collapse
^I'll try this.
Does anyone know a specific reason why this happens to the phone? is it the hardware or software/apps?
Also, is there a valid link to a Gingebread update from HTC/Tmobile? (valid please, megaupload doesn't exist anymore.)
Here is Gingerbread, although you may want to consider rooting and using a flashable Gingerbread Rom, unless you are trying to keep it Stock. http://www.4shared.com/zip/OrXR0864/PD15IMG_234_.html
Sent from my HTC Glacier using XDA Premium.
Scared
I'm still thinking about whether or not to flash these, I just did an OTA update and thought the issue was fixed until after a few reboots the issue started happening again.
I have questions I would like answered because I don't know what's going on:
Is this a hardware or software issue? Because if it's hardware I think I'll just send the phone back for a refund. If it's software then I'm sure I can just flash a completly different version of android and it'll go away (although not 100% sure)
I snooped around these forums and Google and failed to find a solid answer.
jjbadd385 are these links you're sending me ROMs from tmobile, stock android, or another source??
I don't want to cause any damage to the phone when I could just send it back and buy another, only reason I don't want to send it back just yet is beause if I can find a fix on these forums then id be happy.
Might be hardware just send it back and don't deal with non of this specially if u can still return it u might regret it later when u can no longer get a refund or exchange it for a different one just my .02$
Sent from my My Touch 4G using XDA
Sooo it seems I have now bricked my beloved G2x. I have tried every recovery method on xda I can find (a few times), but still no luck.
I was trying to restore stock on my phone to catch the new OTA update, and it has failed...miserably.
Now, my phone gets to the little T-Mobile G2x splash screen and then reboots. I've tried NVflash'ing the firmware, I've tried kdz (which I absolutely cannot get to work right), I've tried sacrificing a chicken to the LG powers-that-be (okay, haven't tried that...YET), but nothing has worked.
Does anybody know of an absolute "unbrick" method?
Thanks in advance for the help!
Also, every now and then, the phone will actually make it to the initial "Touch the android to begin." screen, but my battery (which was 100% charged before this started) now says 0%, even when plugged in.
these links were in the first page of me searching "brick help"
http://forum.xda-developers.com/showthread.php?t=1611968&highlight=brick+help
http://forum.xda-developers.com/showthread.php?t=1180331&highlight=brick+help
http://forum.xda-developers.com/showthread.php?t=1619893&highlight=brick+help
I've tried those methods, and almost every other I could find. I've searched this forum for hours today before posting this, and no matter what I use, I get stuck in either a bootloop or i get a reboot after a minute of being booted. I've tried different recoveries, different ROMs, different flashing methods, and it all ends up the same way.
if you've actually tried things you might want to post exactly what you have tried what were the outcomes and so on and so on. I'm not going to assume what you have tried and assume what the process you did and where you might have messed up. I'm sure neither is anyone else. So unless you help me help you we together are not going to get anywhere.
To the best of my recollection, here's how it went down:
Started off with running Genesis v1 Beta 6.
Ran G2x batch clean up tool w/ CWM Touch
Flashed cyanogen_p999-ota.eng.feli.zip in CWM
* At this point my phone would not make it past more than 1 minute after booting. It would boot up, but after approx. 1 minute, it would reboot, no matter what I did w/ it. This happened several times
Wiped everything through CWM, flashed Genesis again (default install)
*Had same reboot issues listed above
Used NVFlash to push stock V21e firmware http://forum.xda-developers.com/showthread.php?t=1248644
*After this, My phone would not make it past the "T-Mobile G2x with Google" splash screen. You would hear the T-mobile jingle, then the screen would "get stuck" for about one minute, and then the phone would reboot and go through the LG logos to the splash screen and repeat endlessly until I performed a battery pull
Restored stock recovery using NVFlash
*Did a reboot and suddenly saw the boot animation from Genesis!? Not sure how that happened, but it never made it past the boot animation
Ran G2x batch clean up again to try to "clean" the phone, and pushed the V21e firmware again
*Same boot problem
Flashed stock recovery again, then attempted to use KDZ. KDZ will continue to force close midway through the operation, and I cannot get it to work
Pushed V21e yet again
*Now it started making it to the initial set-up "Touch the android..." dialog. I could actually make it through this part, and then the phone would reboot again
*Somewhere in the middle of this, my battery went from reading 95%(The few times it would actually boot) to reading 0%. I wiped battery stats in CWM, but it didn't fix it. "Hey, maybe my battery actually died," I thought, so it's now on the wall charger, waiting for me to try to rescue it again.
I'm going to *attempt* to install a nandroid in CWM, and pray that it fixes things, but if that does not work, I'm at a complete loss
mt3g said:
if you've actually tried things you might want to post exactly what you have tried what were the outcomes and so on and so on. I'm not going to assume what you have tried and assume what the process you did and where you might have messed up. I'm sure neither is anyone else. So unless you help me help you we together are not going to get anywhere.
Click to expand...
Click to collapse
+1
More info would be great!
If I were you, would give a shot of mansa_noob's clean up tool:
http://forum.xda-developers.com/showthread.php?t=1590523
It will reorganize your partitions. Then you just need to flash CWM recovery, then the stock ROM.
Edit:
Just saw your new post, wow that's interesting. I'm not too sure if the touch CWM has anything to do with it, how about to try the normal recovery version of the clean up tool, then maybe a different stock ROM?
Sent from my LG-P999 using xda premium
the only thing I can think of will get me flamed lol, don't use those clean up tools unless it is a last resort! I can say I've never had an issue with just flashing after going through mounts and storage (data, system,cache) and wiping the main things.
The fact that the phone can be booted and it is showing images on the screen means you are not bricked. On the other hand, I've yet to read the issues you are describing, ever. You got quite mess on your hands.
KDZ is your best bet, what do you mean it just "continues to force close"
DupleX01 said:
+1
Just saw your new post, wow that's interesting. I'm not too sure if the touch CWM has anything to do with it, how about to try the normal recovery version of the clean up tool, then maybe a different stock ROM?
Sent from my LG-P999 using xda premium
Click to expand...
Click to collapse
Tried CWM 5.0.2.0, also. I've tried both the stock ROM and the basic cyanogen ROM (Sorry, can't remember exactly where in the cycle those fell...I've repeated several steps several times)
Alright, so It's fixed! Thanks for the interest.
Just for the sake of somebody who (somehow) might have something similar, here's what fixed it....and be warned, this is QUITE unorthodox:
My phone was fully charged (turned off, showing the charged battery icon). I removed the battery, the SIM, and the SD card, and stuck my phone in the fridge for about 10 minutes...That's right, the fridge. I read somewhere that this may help when writing to the disk, and I figured "why not?"
I then pushed V21e using NVflash again, and, lo and behold, it works like a champ! Now just to get the latest OTA update, sit back, and wait for the latest and greatest ROMs to trickle down.
Also, sorry about the original post being kind of vague...It was posted after literal hours of searching and trying different things, and the frustration clouded my brain.
that is crazy lol, but glad something worked for you...
mt3g said:
the only thing I can think of will get me flamed lol, don't use those clean up tools unless it is a last resort! I can say I've never had an issue with just flashing after going through mounts and storage (data, system,cache) and wiping the main things.
The fact that the phone can be booted and it is showing images on the screen means you are not bricked. On the other hand, I've yet to read the issues you are describing, ever. You got quite mess on your hands.
KDZ is your best bet, what do you mean it just "continues to force close"
Click to expand...
Click to collapse
Hey buddy. I won't flame. You are absolutely right. I don't use the cleanup tool a lot either but then since my bluetooth issue is fixed I am slacking .
I am curious though why it did not work but will respond to op in a minute.
Sent from my LG-P999 using XDA
rtotheichie said:
Alright, so It's fixed! Thanks for the interest.
Just for the sake of somebody who (somehow) might have something similar, here's what fixed it....and be warned, this is QUITE unorthodox:
My phone was fully charged (turned off, showing the charged battery icon). I removed the battery, the SIM, and the SD card, and stuck my phone in the fridge for about 10 minutes...That's right, the fridge. I read somewhere that this may help when writing to the disk, and I figured "why not?"
I then pushed V21e using NVflash again, and, lo and behold, it works like a champ! Now just to get the latest OTA update, sit back, and wait for the latest and greatest ROMs to trickle down.
Also, sorry about the original post being kind of vague...It was posted after literal hours of searching and trying different things, and the frustration clouded my brain.
Click to expand...
Click to collapse
I am afraid if my theory is correct your flash (memory) may be going. The symptoms you have described and the fix you mention would suggest a data retention problem. If it breaks again (i hope that I am wrong and it won't) you may have to stick it in the fridge again but if that happens get rid of it fast!
Sent from my LG-P999 using XDA
rtotheichie said:
Alright, so It's fixed! Thanks for the interest.
Just for the sake of somebody who (somehow) might have something similar, here's what fixed it....and be warned, this is QUITE unorthodox:
My phone was fully charged (turned off, showing the charged battery icon). I removed the battery, the SIM, and the SD card, and stuck my phone in the fridge for about 10 minutes...That's right, the fridge. I read somewhere that this may help when writing to the disk, and I figured "why not?"
I then pushed V21e using NVflash again, and, lo and behold, it works like a champ! Now just to get the latest OTA update, sit back, and wait for the latest and greatest ROMs to trickle down.
Also, sorry about the original post being kind of vague...It was posted after literal hours of searching and trying different things, and the frustration clouded my brain.
Click to expand...
Click to collapse
Yet another proof of G2X's unbrickable fame with a happy ending.
Happy for you!
Sent from my LG-P999 using xda premium
I've tried searching for the solutions to this, but some of them are difficult to search and I'm struggling to get relevant results. So I apologize if any of this has been covered elsewhere.
Anyhow, I just installed the ParanoidAndroid ROM last night, and it all went very smoothly, and I was pleased. But, there seem to be a couple issues that either I need to iron out, or that the devs need to. And I'm fully willing to believe it's an issue on my end and not theirs, so, here we go:
1) In CWM, the top half of the screen or so has the rainbow glitch going on and there's a de-centered kind of effect happening that makes it very difficult to use.
2) I'm unable to get my external SD card to mount. I've seen plenty of threads about this similar issue, and I've tried tweaking the build.prop entry regarding this, but nothing I'm doing is helping.
3) The flash only works once per boot, even with included flashlight app. I haven't tested the flash's functionality in the camera yet. But in the flashlight app, the flash will turn on, and when I turn it off, it won't come back on until after a reboot.
4) I now have two installations of the stock Gallery app (com.android.gallery3d and com.google.android.gallery3d). I'm sure I can just uninstall one, but is there one that would be wiser to uninstall?
Otherwise, everything else seems to be working just fine. Thank you all very much in advance.
I've since discovered and fixed a new problem. My phone was apparently not sending or receiving any MMS messages, over WiFi or otherwise. But the APNs described in this post fixed that entirely:
http://forum.xda-developers.com/showthread.php?p=23806717#post23806717
As problem #4 from above goes, I deleted the com.android.gallery3d app and kept the com.google.android.gallery3d app as there were internet and syncing features that were omitted or nonfunctional from the former one.
Just so you know, if you read through the paranoid thread in the dev section or any of the ics ROM threads actually, all of your questions r covered. I cangive you answered/jumping off points for your questions.
1. The rainbow distortion comes from having Froyo bootloaders instead of GB. To fix this you will need to use Odin or Heimdall to flash the GB bootloaders. Look in the ISET Super Everything thread that's stickied in the dev section. BE SURE to flash something else with Odin or Heimdall (whichever you choose) before you try flashing the bootloaders. If you lose your connection while trying to flash bootloaders, you can hard brick your phone which basically means you have a shiny coaster.
2. Your external sd card is found in the emmc folder on ics ROMs. You need a root enabled file explorer to open it.
3. Using your camera flash as a flashlight which I believe is referred to as torch is one of the few known remaining bugs on Infuse ics ROMs. The flashlight app that is included is currently the only way to get it working. The flashlight should turn on everytime you open the app but it won't turn back on if you turn it off while in the app.
4. MMS is an issue with the APN settings. Look at the last few pages in the dev section. I know it was recently covered on a couple different ics ROMs threads. To get to the APN settings, go through the following path in the settings.
More (under data usage) > Mobile Networks > Access Point Names, click on the AT&T listing, then change MMS Proxy to 66.209.11.32
I'm pretty sure that is all you have to do to fix MMS but read some dev threads for more info. I think you can also try to look in the Dev Tools app if it is included with the ROM. In the app, click connectivity then start MMS. Again, further reading should give you more info.
Boz™
Sent from my SGH-I997 using xda app-developers app
Yeah, the flashlight thing, I knew was a known bug. But the latest update claiming that "all bugs squashed" misled me, I guess. Because that bug obviously persists. But, c'est la vie.
As the rainbow glitch goes, I never installed Froyo on here, I went from stock to Gingerbread to... actually, here's specifically what happened:
•Initially, I installed 3e Recovery and CWM on my stock Android 2.2 per the instructions here, http://www.youtube.com/watch?v=Y09p-J_g_Rg, and everything went fine.
•Then I flashed Gingerbread UCLB3 per this thread, http://forum.xda-developers.com/showthread.php?t=1508619, but unfortunately, I made a dumb mistake. I neglected to disable Voodoo Lagfix first and softbricked my phone.
•So, I went back to the Infuse Super Everything Thread and found this fix, http://forum.xda-developers.com/showthread.php?t=1092021, brought my phone back to stock, just fine.
•Then I flashed to UCLB3 the same way as before, only this time disabling Voodoo and it all worked perfectly.
•Then I immediately flashed to ParanoidAndroid and everything went as described in the thread and now here I am with the CWM glitch.
So I've only been stock or Gingerbread ever before on my phone.
Anyone know how to simply change the font or install a new one?
Sent from my SGH-I997 using xda premium
I use ROM Toolbox Pro.
Edit: Check the Paranoid Android dev thread end of page 32 and beginning of page 33. The guy that maintains the PA port just posted a link and instructions for the fix to rainbow recovery.
I'm no expert so I may b wrong but I'm pretty sure that if you had a stock AT&T infuse then it most likely came with Froyo originally. Just bc you flashed a GB ROM doesn't mean you got the bootloaders. To get the GB bootloaders, you need to run Heimdall a second time with the "Install Bootloaders" checkbox checked. I'm not exactly sure how it works in Odin but I think you have to have a file in the PDA slot in order to get the bootloaders installed.
I do know that if you have rainbows, it is bc you have Froyo bootloaders. Our at least that is the only reason I've ever heard of and I've read of people with the issue numerous times. I would just read through some of the dev ics threads bc there have been a few times in the last week that I've seen people pay steep by step instructions explaining exactly which Heimdall or Odin to use. I just know that you have to take extra steps to install GB bootloaders. With Heimdall that means checking the flash bootloaders checkbox. They do this bc it can hard brick your phone so they don't want you to install them unless absolutely necessary.
Boz™
Sent from my SGH-I997 using xda app-developers app
Ah-ha! Very good, someone else is having my same problems, lol. I'll definitely be using Odin, as that's how I fixed my softbrick issue and I could never get Heimdall to install on my computer properly (Java issues or something, couldn't figure it out and Odin worked anyway).
Do you know if flashing the bootloader will cause any loss of information or settings? Or will it affect nothing else?
I'm not 100% sure on that one. When I did it, I was using Heimdall to fix my soft bricked phone at the same time so I was basically starting fresh. I'm not sure if it is possible to just flash bootloaders in the Odin PDA slot and keep everything else. I would assume that you would lose everything and have to reflash the ROM from recovery but that's just an assumption.
I would get titanium backup (if u don't already have it) and backup everything and sync with your Gmail account just in case. That way u can save it apps and their settings.
You may b able to ask that question on the PA dev thread and get a better answer.
Boz™
Sent from my SGH-I997 using xda app-developers app
There's an XDA Forum restriction on newbies. I can't post in any Dev forums until I've... done something, I forget. Ten posts or ten thanks. I forget what. Either way, I'm not allowed in there yet. lol
Anyhow, based on some threads I've found, it seems possible to flash only the bootloader in Odin. I'm still just waiting to find out how much information is lost in the process before I dive into it.
But yeah, I do have Titanium, and now that I have everything installed and set up just the way I like it, it is time for a backup anyway.
Supposing I need to, is there any problem restoring system apps and data once I do this? Because everything will be identical, minus the bootloader. I just know I've read enough about the dangers of restoring system data on the threads here to be cautious. Even though I'll just be going from ParanoidAndroid to the same flash of ParanoidAndroid, plus a new bootloader, but better safe than sorry.
Thanks for all your help, man.
Appears as though that question's already been answered here:
http://forum.xda-developers.com/showthread.php?t=1603220&page=5
Bottom of page 5 states somewhat affirmatively that no data will be lost. So, lovely. Now I've just got to flash the bootloader, and then work on my forum searching skills. I can never find ****, when clearly it's somewhere. lol
dstarr3 said:
2) I'm unable to get my external SD card to mount. I've seen plenty of threads about this similar issue, and I've tried tweaking the build.prop entry regarding this, but nothing I'm doing is helping.
Click to expand...
Click to collapse
Figured out the emmc part but how do you actually open the external SD on your pc?
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.
Alright, so I need a little help here deciding what to do next.
My girlfriend has the SGH-T959v with android 2.2.1 on it.
It had been randomly shutting down when the screen turned off. It was much the same as the Samsung Captivate had its issues.
It also wouldn't charge sometimes and would also not turn on unless the battery was removed.
Well, I replaced the battery with an OEM one from a mobile store.
Now there are no more random shutdowns but there's a whole slew of different issues.
If the phone is turned off you have to remove the battery, put it back in, plug it in quickly, and then turn it on.
If the phone charges too long all the signal stops working until a reboot.
The phone always thinks it's charging even when the battery is draining.
It's a pretty irritating problem especially with the reboot issue because if we're out and away from electricity and it gets turned off accidentally then there's nothing we can do till we get back to the charger.
Has anyone had these issues and solved them with a new ROM?
I had the random shutdowns on my Captivate and solved it with CyanogenMod. I'm thinking about flashing but I don't want to wipe it all and then have it not work or brick the thing (it is unlocked on Straight Talk so I also don't want to relock it to T-Mobile)
Some foresight would be appreciated before I move forward with it.
Thanks
Why don't you try a ROM and find out if it does anything? Questions like this are pointless because you can answer them yourself by just trying it.
Yes, flashing a better ROM will help in certain cases
pisherthefisher said:
Why don't you try a ROM and find out if it does anything? Questions like this are pointless because you can answer them yourself by just trying it.
Click to expand...
Click to collapse
Actually my question was whether or not anyone has had this issue.
I'm trying to see if it's a known firmware problem or a known hardware problem so I don't waste my time.
I don't have all day everyday to backup the phone and flash and test and then reinstall all the apps.
Thanks for the contribution though.
That being said would anyone suggest a TW ROM for this? I don't want to change the functionality because she's used to TouchWiz and not tech savvy
Now I must throw in, you should search around for a TW styled ROM. I don't know if we have one or not, but I can tell you that looking yourself will be a lot quicker then waiting for somebody to feel sorry for you, search for it, and give you a link to it.
Ignore those guys. Dont flash a custom rom YET.
http://forum.xda-developers.com/showthread.php?t=1822626
Read that post follow the directions. I suggest reading the thread it links to while backing up the phone. Then while actually doing the flashing with heimdal follow it.
Now be sure to follow eollies directions of flashing the kernel after the initial boot or wifi will be broken.
This will wipe her phone out and reflash everything plus give you root access to remove bloat and add things like titanium backup.
---------- Post added at 07:49 PM ---------- Previous post was at 07:37 PM ----------
Whoops looks like eollies pulled the file from dropbox.
Just follow the directions in the thread by lumin30 that eollie links too.
I forgot to say why I suggest using a one click. This device sometimes just needs to be reset to factory. And Using a one click will remove all stuff not suppose to be hanging around.
Here's another one that I find much more simple.
Heimdall One Click back to Stock for the T959V
I have the grimlin remover one click on my computer I can upload it later
Cooptx said:
I have the grimlin remover one click on my computer I can upload it later
Click to expand...
Click to collapse
I have it also, but cant get it to upload for whatever reason. So.....
Here's the link: http://forum.xda-developers.com/showthread.php?t=1500427 Post #41 has a working DL. get it, unzip, run it. Maybe it helps him.
Use the heimdall one clicks they are 2.3.3 stock touchwiz. Like I said follow lumin30's guide to the letter. He is a recognized contributor for a damn good reason. That guide has also been featured on the portal. I would flash the antonx kernel after for root and then flash bhundvens latest kernel. This will allow just a bit more control and troubleshooting if something happens.
Alright, I was just throwing it out there xD
Really guys? You're not even answering his question and linking him to old guides that are complicated. If someone needs to go to a stock KJ6 rom just link them to lumin's guide!
Anyway, I doubt you will find anyone on these forums who are still running the 2.2.1 stock rom, I personally haven't run it in over 2 years when I first bought my phone.
Samsung has released an official update from Froyo (what her phone is running) to Gingerbread (the last officially released version for this phone).
I recommend you try that, but know that there is a long-sms bug. If you go over 140 characters the message will get cut off and you will get a "message sending failed" notice when you try to send it. You can instead try to use a 3rd party app like handcent or gosms that will split the message for you if it goes beyond 140 characters.
If you would like an easy to follow, reliable guide WITH PICTURES, then go ahead and follow lumins' guide:
http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2
Just remember that everything on her phone will get wiped, but you can use google to back up contacts. It sounds like it'll be worth it.
Again, lumin's guide will allow you to upgrade her phone to the last official rom Samsung released for our phone.
Good luck!
I wonder if Samsung kies is still upgrading.