Database Info

Tmobile Wing Won't turn on after Rom update attempt.

Tmobile Wing Won't turn on after Rom update attempt. No reset workers. Can't charge can't do anything, its just dead. I really don't want to wait until the wing 2 comes out, is there anything i am doing wrong?? I guess i should add that i used hypercore

It turns out that i think something when wrong( i don't see why?) but i put it into bootloader thing(camera + reset)

Wrong Section to post in. Also your phone is probably bricked.

Go to the xda wiki and search for Goldcard. Even if it's for the elf, it was copied from the Herald. I haven't tried it myself, though.

just hold down the camera button and press the reset button on the side
then connect usb cable
then download the official stock t-mobile rom (google it)
and it should work again

Rim1Flex said:
Tmobile Wing Won't turn on after Rom update attempt. No reset workers. Can't charge can't do anything, its just dead. I really don't want to wait until the wing 2 comes out, is there anything i am doing wrong?? I guess i should add that i used hypercore
Click to expand...
Click to collapse
turn on in bootloader mode
(camera+reset button on side below the volume)
then download the official stock rom and run it and you should have ur old rom back
just search on google for t-mobile stock rom

Another brick
I was installing the customized ROM from thewingster (WM6.5) on my Wing. I did not include MS voice recognition, and I think I included all the other software. The progress bar was humming along on my wing, then the flash program said that the file was corrupt, and my phone went blank.
Now I cant turn it on, it wont light up at all when I plug in a charger or a computer USB (activesync wont notice anything is attached to the computer, and wont turn on at all). I tried a charged up battery from another wing, nothing changed...
I tried hard resets with the soft keys and reset button, and camera and reset button. Cant access it through my computer using any program (herald-uspl or activsync)
I have nothing at all.
Any ideas other than throwing it off a bridge?

routine8 said:
I was installing the customized ROM from thewingster (WM6.5) on my Wing. I did not include MS voice recognition, and I think I included all the other software. The progress bar was humming along on my wing, then the flash program said that the file was corrupt, and my phone went blank.
Now I cant turn it on, it wont light up at all when I plug in a charger or a computer USB (activesync wont notice anything is attached to the computer, and wont turn on at all). I tried a charged up battery from another wing, nothing changed...
I tried hard resets with the soft keys and reset button, and camera and reset button. Cant access it through my computer using any program (herald-uspl or activsync)
I have nothing at all.
Any ideas other than throwing it off a bridge?
Click to expand...
Click to collapse
You tried pressing the camera button ONLY while pressing the power button? (or the soft reset button.) The ROMs don't stop the phone from turning on unless the installation was botched.

botched install
ivanmmj said:
You tried pressing the camera button ONLY while pressing the power button? (or the soft reset button.) The ROMs don't stop the phone from turning on unless the installation was botched.
Click to expand...
Click to collapse
Yes my install was botched. Computer went into standby mode during flash. Phone was still on (just in the bootloader mode? with 3 colors on the screen). From there I figured I could just re-install the ROM, so I tried. Then the progress bar appeared on my phone and I figured it was all gravy. Then the ROM flasher program on my computer said the file is corrupt and the phone went black.
Now its totally dead wont respond to any combination of button pushes or battery replacements....
Anyone had this problem before?

What does this have to do with Rom development?

routine8 said:
Yes my install was botched. Computer went into standby mode during flash. Phone was still on (just in the bootloader mode? with 3 colors on the screen). From there I figured I could just re-install the ROM, so I tried. Then the progress bar appeared on my phone and I figured it was all gravy. Then the ROM flasher program on my computer said the file is corrupt and the phone went black.
Now its totally dead wont respond to any combination of button pushes or battery replacements....
Anyone had this problem before?
Click to expand...
Click to collapse
If it won't turn on by holding the camera button and then pressing the power button nor the reset button, then it might be gone. Sorry. Although, I've always seen it be recoverable.

"Converting data partition..." Problem

Alright, allow me to summerize to you guys the series of screw ups that happened in the day that I've had my captivate.
Basically, it's like this. I got this phone from my brother (it used to be his). Now when I got it, I began basically erasing his contents and setting up mine. The Phone is on the Cognition OS and everything seemed fine.
Now, when I tried to set up my google account, it said I had to do a factory reset, I did that. Then I realized the market place app was no longer there :/
I did another factory reset, still didn't help, and started looking around for info.
I told my buddy this and he said he could fix it. So he get's the update.zip for rooting the phone, sets it up on the SD card, and goes to root the phone normally. Except when he restarts the phone after, it doesn't go to the set up screen, so he just starts it normally and enters the setup screen by holding home+volume up+power.
Then he presses the reinstall packages, and the phone seems to get to work on the update pack...
Now, every time I turn on the phone the voice says "converting data partition to optimize extension four", turns off, then repeats.
I've looked up this problem and it seems to have something to do with voodoo, but the causes in the other cases the causes were different.
Can someone please help me out here? I've also tried doing a hard reset by holding the volume down button and pressing power, but nothing seems to take me to the recovery mode.
HELP.

Did you pull the battery during this our did you let it run? Should let it run.
Does your phone boot up at all?
At&t or rogers?
Do you have a windows pc with usb drivers installed?
What its your build number, located under battery, something like 1008?
Answer these questions and we can get you back up and running

-Well after he did the reinstall thing we let it run for like 15 minutes, then he pulled the battery out.
-The phone only shows the AT&T screen, say's the "converting data partition..." thing, then goes blank and does it again. I've let it run for like 10-15 minutes before having to turn it off because I couldn't have the speech going off.
-I have a windows PC, and but I'm not sure if I have the drivers installed. I have Kies installed and when I plugged the phone in before Kies could recognize the phone (though it wouldn't fully connect, it would just say "connecting" on the kies screen).
-The Model is SGH-I897, that's the only relevant thing I see under the battery, that good enough?
Thanks a lot.

No, your phone has a build, on phone under battery, the word build is not listed. Something between 1006-1012
If we are going to do this you need to be active, I can not wait 20 minutes in between responses

Sorry the internet kinda crapped out actually.
And I see a 1007 between the bar codes, that it?

Yes
Before we get started try this
Take battery, sim, ext sd our of phone
Plug usb into pc but not phone
Put battery back in
Hold volume up and down, while holding plug in usb
Screen should come on with android with shovel
You can pull the battery again
Confirm this happened

Yep, it happened.

It may be easier if we use gtalk, log in on your pc using google id, send me an invite [email protected]. This way we know when each other respond

Just sent u the inv

I am having the same issue.. Chairchair did your problem get resolved?
Can anyone help?
James

liquorsh0tz said:
I am having the same issue.. Chairchair did your problem get resolved?
Can anyone help?
James
Click to expand...
Click to collapse
Have you gone back to stock and then reflashed? Seems like some files are getting corrupted. Because you have a voodoo kernel I would follow these steps. Make sure to back up.
1. Use Odin to flash a non vodoo kernel.
2. Flash stock rom and master clear
3. Reflash rom of choice if it is 2.2
3a. If you want 2.3 follow the tut on it.
4. Breath a sigh of releive lol

[Q] Nexus S i9020A Bricked due to failing power button - Odin seems the last hope?

Hi everyone,
INTRO:
So the power button on my Nexus S broke. No big deal, I remapped it to the search button and used the volume rocker to wake the device; an option that was embedded in Cyanogenmod9.
Then I upgraded to CM10... since I did that on top of CM9, my volume rocker option was still enabled, but the option is no longer in CM10's GUI.
I had some annoying issue and thought maybe I should wipe my phone; which I did.
Sadly, I realized that my "wake using volume rocker" option was no longer enabled, and there is no GUI to turn it back on.
I then found a .zip package that was supposed to enable the option but, I guess I went too fast, now my phone is stuck on a bootloop.
THE PROBLEM:
Since my power button is broken, I cannot navigate in the fastboot menu to recovery and fix the ROM.
Worst, since the power button is somehow shorted (i.e.: it powers on automatically when I insert the battery) Fastboot is not working properly and my PC never sees my phone, so you can forget about fastboot boot recovery.img
So: boot loop, power button broke, no recovery, no fastboot. =(
I searched quite a bit and found out you could get the Nexus S in download mode and get it to work with ODIN using a USB JIG.
I made myself such a JIG and successfully put the phone in some kind of download mode where my PC sees it, fastboot devices yields nothing *but* ODIN sees the phone!
So a glimmer of hope except for the fact that finding the .tar files for the Nexus S seems impossible...
Thoughts? Suggestion? TIA!
Francis // XC3N

Oh BTW:
-Yes I saw the other posts, but none of them mention the odin files
-Yes, I know fastboot is better; but it's not working and:
-No, I can't see the device on 3 different PCs using 3 different OSes and 3 Different cables when in fastboot mode
I mean by that last line that *nothing* shows in device manager in Win7 or XP and *nothing* shows in lsusb on ubuntu
So unless someone has an idea it looks like Download mode is the only way my PC sees my phone...

My power button done the same thing, I googled around and found a solution that worked for me.
It's somewhere here on xda but I don't got the link, basically everytime I booted into the bootloader I couldn't move the cursor with the volume button because the phone thought I was holding the power button, so I carefully tapped the casing around the power button and rebooted the bootloader and eventually I had control, it took 5-6 attempts to get it going but it did fix the power button for me.
I think it's something to do with the micro switches giving out after a certain number of uses.
Also it started screwing about recently so I just blew into the casing through the power button and it's behaved ever since.
In short, tap it until it works, once you have control of fastboot plug the usb in and your pc should detect it
Hope this helps, Good Luck
Sent from my U20i using xda app-developers app

Muckyfox said:
My power button done the same thing, I googled around and found a solution that worked for me.
It's somewhere here on xda but I don't got the link, basically everytime I booted into the bootloader I couldn't move the cursor with the volume button because the phone thought I was holding the power button, so I carefully tapped the casing around the power button and rebooted the bootloader and eventually I had control, it took 5-6 attempts to get it going but it did fix the power button for me.
Also it started screwing about recently so I just blew into the casing through the power button and it's behaved ever since.
Click to expand...
Click to collapse
Hey MuckyFox thanks for your reply!
Unfortunately, that would've worked back when the power button was flimsy and still working once in a while... I did try the tapping thing but really nothing works... the button seems entirely dead and shorted. I guess at this point I might've to bring it in for repair... if the power button isn't broken then I'll be able to easily fix everything in recovery or fastboot. Sucks because I feel like I'm so close to getting it to work without spending money XD I just can't find the files for odin even though they really do seem to exist.

Allright so I found some odin files which were said to work with the i9020a
I flashed them... at some point it said "RESET!" and then odin no longer saw the device. The device is now not booting at all. FML

So this thread is going to end up like every other similar thread: I went and bought a Galaxy Nexus ;P
For posterity, these are the files you shouldn't flash on i9020A:
BOOTLOADER : Bootloader_I9020XXJK1.tar
PDA : PDA_SOJU_GRH78_85442_SIGNED.tar
PHONE:
CSC : CSC_I9020_EUR.tar

My power button started failing over the last couple of days. First when I would set the phone to standby it would ask me if I wanted to switch off the device, then later on it wouldnt respond at all.
Really weird solution - boot into recovery, factory restore, clear dalvik cache, voila, works good as new! (aside from losing all my settings)
Note, I barely managed to get into recovery. The power button fully stopped working halfway through and I had to take the battery out and try it a couple of times.
Oddly, even during this uber-broken phase, the power button would always switch on the device when fully switched off (not just standby) indicating to me that it wasnt just a physical broken connection.

I've mentioned this before, but a full casing for the phone with all the buttons is around $10 on eBay
Sent from my Nexus S using xda app-developers app

XC3N said:
So this thread is going to end up like every other similar thread: I went and bought a Galaxy Nexus ;P
For posterity, these are the files you shouldn't flash on i9020A:
BOOTLOADER : Bootloader_I9020XXJK1.tar
PDA : PDA_SOJU_GRH78_85442_SIGNED.tar
PHONE:
CSC : CSC_I9020_EUR.tar
Click to expand...
Click to collapse
You need stuff for SOJUA, and just the fact CSC has EUR meaning Europe in it would scare the crap out of me. Possible you just flashed stuff meant for i9020T and not i9020A.

In case anybody comes back here, I'm just gonna drop this in.

Lights won't turn off and other stuff..

Thanks in advance for looking at this thread..
Just restored my old shift 4g which had a dead battery. I thought the thing was bricked because it was boot looping. I stuffed it in a drawer and forgot about it. The other day I was rummaging through the drawer and decided to give it a go again only to realize that the battery had all but exploded.. I got a new battery and restored from a nandroid backup and there seem to be a couple of things awry..
The hardware buttons won't turn off, even when the screen is off they're still on and remain on until I power down..
My evo 3d has the htc diagnostic utility installed where you press *#*#3424#*#* and you can run all kinds of tests. Does anyone know if the shift has the same sort of utility or how to run these diagnostics another way?
Thanks again.

If it's acting strange like that, the best thing to do is Un-Root it. Then start the Root process all over. It should resolve the issue. BTW ##3424# will lead you into DM Command Service.

I had a feeling someone was gonna say that.. thanks.

RUU back to 2.2. Then use THIS tool to Root again.

found old Samsung S2 Plus, Cyanogenmod Stuck on boot

Hello guys, im a total newbie with android/cyanogenmod/recovery etc. so sry for any dumb mistakes.
I have an old Samsung S2 Plus that a friend of mine installed cyanogenmod and some other stuff on some years ago for me.
I think it was Cyanogenmod 12.1 but im not completely sure.
My problem today is that when i boot the phone i get stuck on some bootscreen (the one with the blue cyanogenmod "alien"). Just nothing happens, had it blinking for 1 hour and more just to test it.
I tried getting into any of these recovery modes (searched online for some key combinations), tried a lot of combinations(volume up + power etc. but no recovery is showing up, just always the white samsung galaxy s2 text and the blue alien thingy afterwards. I think back then my friend installed cwrm recovery mode, but again not 100% sure.
Im thankful for every help and sry again for any dumb questions.

No mistake is a dumb mistake, unless youve already made that mistake several times and you repeat it, expecting the outcome to change. The more you mess something up and you fear youve messed up big time, the more you will figure out a way to fix it and gain knowledge.. embrace it..
On most Samsung phones, you have key combinations that are all the same.. very specific how you do it though..
Im going to use keys below, to simplify things a bit
[H] = home button, bottom center of screen
[P] = power button, usually top right edge
= volume up button
[D] = volume down button
If your phone is in boot loop* or not responding to power button, you will first have to completely restart all the system fresh.
* boot loop: an error that cause a device to start to load and at a certain point restarts, and repeats without ever getting past the point of restart
Two ways I know of to manually do it:
- You can take the battery out, and then press and hold power for 30 seconds. Then release power and insert battery.. leaving it in a dead state.. not powering it on, not charging, or even plugged into laptop..
OR
- Press and hold [D] + [P] *ONLY* for 45 secs or until the phone cuts off, careful to not accidentally restart
Once device is in that dead state, use key combos listed below:
..........☆ RECOVERY MODE ☆..........
press and hold
+ [H] + [P]
when the splash logo* appears,
release all of them
*splash logo: the first thing you see when powering on your device. Usually will say like samsung s2 and powered by android. You usually only see it for a few seconds
..........☆ DOWNLOAD OR ODIN MODE ☆..........
press and hold
[D] + [H] + [P]
when you see a blue screen,
quickly release them all.
then it will have instructions
typically to confirm into download mode,
or [D] to cancel and reboot
Straight Talk phones are known to have these taken out, so you cant free the phone from the grasps they have on it..
If those dont work, and your phone isnt straight talk or verizon, you can download these programs to windows OS pc, and they have buttons that will send a call to your device, and put them into download, fastboot, sideload, adb, or even recovery mode.. not all those modes are available on all samsung devices..
ME PERSONALLY, I HAD MOST LUCK WITH "D P TOOLS" AND "WINDROID"
ODIN IS A MUST HAVE IF YOUR GOING TO BE INSTALLING ROMS. ODIN WILL GET YOU BACK TO BONE STOCK FIRMWARE
Stock firmware can be found on multiple sites and here on XDA. Firmware is device specific and android version specific.
Heres a couple of the latest android versions
6.x.x = marshmallow
7.x.x = nougat
8.x.x = oreo
X/// STOCK FIRMWARE LINKS ///X
you would use the model number which can be found under the battery, and android version. since you may not know which one your running. I suggest google search for " your phone model + release date + release specs" that will get you in the ballpark
SAM MOBILE FIRMWARE
https://www.sammobile.com/
UPDATO
http://updato.com/firmware-archive-select-model
X/// ODIN INFO ///X
-- HERE IS A IN DEPTH ODIN TUTORIAL --
https://forum.xda-developers.com/note5/general/guide-odin-flashing-stock-firmwares-t3634256
Thanks to Gr3atGeek for this tutorial
X/// MOBILE TOOLS I MENTIONED ///X
run antivirus!!
-All in one flasher
CANNOT FIND
-D P tools
http://dp-tools.en.lo4d.com/
-Minimal ADB and fastboot
http://minimal-adb-and-fastboot.en.lo4d.com/
-Windroid
1 ) http://windroid-universal-android-toolkit.en.lo4d.com/
2 ) http://windroid-toolkit.en.lo4d.com/
-Android Ultimate
http://android-ultimate-toolbox-pro.en.lo4d.com/
**GENERAL TIPS AND TRICKS**
THESE IVE HAD THE MOST LUCK WITH. IM PRETTY SURE THIS IS THE ACTUAL URLS WHERE I DOWNLOADED ALSO.. NOW SOME WORK WITH THIS PHONE BUT NOT THAT PHONE. SOME WILL WORK WHEN ATTEMPTING TO PUT INTO RECOVERY MODE BUT WONT PUT INTO DOWNLOAD MODE.
**USE OF SOFTWARE HINTS AND SUGGESTIONS*
I HIGHLY SUGGEST NOT TO RUN MORE THAN ONE OF THESE PROGRAMS AT ONCE. SOME USE ADB.EXE AND IVE FOUND MULTIPLE ADB.EXE WILL CAUSE SILENT PROBLEMS.. IF YOUR UNSURE HOW MANY INSTANCES OF ADB.EXE ARE RUNNING, CLICK (CTRL) + (ALT) + (DEL) ALL AT ONCE. THEN CLICK TASK MANAGER. ONCE TASK MANAGER IS LOADED, CLICK THE PROCESSES TAB AND FIND ADB.EXE
** USB TRICKS AND SUGGESTIONS **
USE IF POSSIBLE YOUR ORIGINAL USB CABLE AND DONT USE ONE THAT HAS ANY HINT OF A PROBLEM, USUALLY THE THICKER THE WIRE THE FASTER AND SAFER IT IS.. OEM WORK THE BEST.. AND IF AT ALL POSSIBLE, MINIMIZE THE AMOUNT OF USB PORTS BEING USED TO PREFERABLY JUST THE CHARGER WIRE. SOMETIMES USB 2.0 AND USB 3.0 WILL EFFECT THINGS. DO NOT HAVE MORE THAN ONE PHONE CONNECTED AT A TIME.
GO INTO DEVICE MANAGER AND UPDATE USB DEVICE DRIVERS AND MAKE SURE SAMSUNG DRIVERS ARE UP TO DATE
Hope this has helped.. Sometimes the buttons on a phone will quit working but when you press it, it feels like it worked, made the sound and all.. thats when these programs come in handy.. im guessing you charged your phone until it came on, and when you were trying button combos, the phone was still on. It has to be off first. ADB and fastboot are powerful tools if you know some terminal knowledge, you can also start a shell and usually terminal will tell you if deamon* started successfully or not.. sorry about the mass confusion.. go run around XDA forums just searching and reading and now that youve heard me mention some of the lingo and terms used.. Google search everything.. the resources are there, and i just gave you a good bit of direction.. good luck
*daemon: to be brief, a word that symbolizes a connection between your device and another system
$$ IF IVE HELPED, OR YOU FEEL I MADE AN HONEST ATTEMPT TO HELP, HIT THE THUMBS UP, THATS THE BUTTON FOR "THANKS" HERE IN XDA
IM NOT RESPONSIBLE FOR ANY BROKEN, DAMAGED, OR MYSTERIES THAT HAPPEN TO YOUR DEVICE OR COMPUTER USING ANY INFORMATION OR TOOLS IN THE ABOVE TUTORIAL. BE SAFE