Phone Bricked - Help Appreciated - T-Mobile Samsung Galaxy S II SGH-T989

Okay long story short, I was flashing Kang's Bullet kernel to my phone without the battery cover on (I know, I'm a dumb ass) and go figure, the battery pops out. I put the battery back in, and the phone doesn't boot as I sorta expected.
When I plug my phone into the computer it shows up as a qhs_usb device but it didn't have drivers. I searched around, found the drivers I needed here - http://forum.xda-developers.com/showpost.php?p=14909282&postcount=19 . So now my computer and Odin recognize my phone, but when I try to flash the stock kernel back on the phone it gets stuck on "Setup Connection". I'm having the exact same issue as this guy - http://forum.xda-developers.com/showpost.php?p=19091572&postcount=7
Does anyone have any insight as to how to get around this problem? While doing some more searching, I read that a USB jig may work. Will that work with our phones or is that only for the first gen Galaxy phones? Thanks in advance for any help.

ghettoc401 said:
Okay long story short, I was flashing Kang's Bullet kernel to my phone without the battery cover on (I know, I'm a dumb ass) and go figure, the battery pops out. I put the battery back in, and the phone doesn't boot as I sorta expected.
When I plug my phone into the computer it shows up as a qhs_usb device but it didn't have drivers. I searched around, found the drivers I needed here - http://forum.xda-developers.com/showpost.php?p=14909282&postcount=19 . So now my computer and Odin recognize my phone, but when I try to flash the stock kernel back on the phone it gets stuck on "Setup Connection". I'm having the exact same issue as this guy - http://forum.xda-developers.com/showpost.php?p=19091572&postcount=7
Does anyone have any insight as to how to get around this problem? While doing some more searching, I read that a USB jig may work. Will that work with our phones or is that only for the first gen Galaxy phones? Thanks in advance for any help.
Click to expand...
Click to collapse
Ha. Don't worry. I bricked my phone on my first try too. What I did was connect my phone to odin again, but just rooted it all over again. It worked too. Download the files you need and use odin to root it again. It should work.

yup, just boot into the Download mode, and flash back to stock via ODIN, then you can go from there
a USB jig will definitely make it easier

Thanks for the help so far guys. Okay unfortunately I can't get into download mode. My phone doesn't show anything on the display, make any sounds or anything. I've tried different combinations of pressing the volume up/down key and inserting the USB cable, but Odin still freezes at the "Setup Connection" step. I think its fully bricked because even when I don't press any keys when plugging in my phone my computer still recognizes it as the same device and Odin still freezes. I've attached a pic to show what I mean. The "Qualcomm HS-USB QDLoader device I have expanded in device manager is what my computer sees the phone as, no matter what I do.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

*Take the battery out and place it back
*Hold both Vol up + Vol down, and plug the USB cable in.
That will bring you to download mode
or leave the batt. out for a min. or 2. Also try a different port see if that helps.

Thanks for all the help guys. Unfortunately I can't get it into download mode. I even tried with my friends jig - http://www.youtube.com/watch?v=Rdn5GoRjhn0&noredirect=1 but it doesn't work. I'm just going to consider this a loss and see if I can get another phone used on CraigsList or eBay.

How I unbricked mine....
I was having a hard time as well after bricking my phone. In desperation, this is what I did....
I went to another pc, my work laptop, and installed the drivers and installed odin on it. Simply plugged the phone in and flashed via Odin back to stock firmware. All it took was swapping pc's. I was having the same issue............
My guess is that somehow since the original pc "knew" the phone, it couldn't decipher the phone in a different state, but it did prove to work on another pc.
I hope this helps you!

wait until unbrickable mod comes out..lol

You can also trya different usb on your PC. I could always find Odin. Good luck
Sent from my G Sexy II using XDA App

take it to tmobile and say u dont know what happened and get another one??? just dont say you were rooting/flashing/anything to it. im sure they'll take it back if there's no sign of any modding on it.

clemsonboyz said:
I was having a hard time as well after bricking my phone. In desperation, this is what I did....
I went to another pc, my work laptop, and installed the drivers and installed odin on it. Simply plugged the phone in and flashed via Odin back to stock firmware. All it took was swapping pc's. I was having the same issue............
My guess is that somehow since the original pc "knew" the phone, it couldn't decipher the phone in a different state, but it did prove to work on another pc.
I hope this helps you!
Click to expand...
Click to collapse
Thanks, I did try this one last time, but it didn't work :\ . I've already given up hope because I did some more reading and when the phone gets in this mode, it means the eMMC (or something like that) needs to be re-flashed and that's something they have to do at the factory.
unknownnoob said:
take it to tmobile and say u dont know what happened and get another one??? just dont say you were rooting/flashing/anything to it. im sure they'll take it back if there's no sign of any modding on it.
Click to expand...
Click to collapse
Yea but I bought it the first day it came out, not sure they would take it back if I tried to return it. Also it's 100% my fault, so I would feel bad trying to return it. But thanks for the advice though.

I know that it's been a while since your last post, but you might want to take up this service;
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-ii-skyrocket-jtag-brick-repair/
I had my Galaxy S2 i777 revived not too long ago by these guys after an accidental repartition with an incorrect .pit.

ghettoc401 said:
Thanks, I did try this one last time, but it didn't work :\ . I've already given up hope because I did some more reading and when the phone gets in this mode, it means the eMMC (or something like that) needs to be re-flashed and that's something they have to do at the factory.
Yea but I bought it the first day it came out, not sure they would take it back if I tried to return it. Also it's 100% my fault, so I would feel bad trying to return it. But thanks for the advice though.
Click to expand...
Click to collapse
Edit
Sent from my HTC One S using xda premium

hi
i dont know how to install the driver. please help me

Related

[GUIDE] SoftBricked?? I'll Show You How to UnBrick It!

HELLO EVERYONE!
This is how to UnBrick the T-Mobile Samsung Galaxy S II.
Make Sure you Never UnPlug the USB Cable While Flashing!
YOU WILL NEED:
Odin 1.85
USB Drivers
T-Mobile Stock 2.3.6
T-Mobile Stock 4.0.3
You must be really nervous right now. DON'T WORRY! THE MORE YOU STRESS, THE MOST LIKELY YOU WILL MESS UP!
Let's get down to business!
1. Relax, and focus on what you are doing.
2. Now try to put your phone to Download Mode.
A. Take out and put back in the battery. Then, hold Vol + and Vol - , now plug in USB and you will get to this screen.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Then, you must press Vol +, and your in Download Mode!
B. Find a G2x USB and check if it puts in download mode while its off. If it doesn't, you will need to use a USB JIG.
IF NON OF THIS OPTIONS WORK, AND YOUR PHONE DOESN'T BOOT, YOU HAVE HARD BRICKED YOUR DEVICE. TO PROVE THIS HAPPENED, PLUG IN YOUR DEVICE AND SEE WHAT THE DEVICE NAME IS ON YOUR PC. SHOULD SAY SOMETHING ABOUT QUALCOMM BOOTLOADERS.
2. Once your in Download Mode, open up Odin 1.85 (Make sure you installed the drivers!) Once in Odin 1.85, Check PDA and look for the downloaded:
T989UVKL1_HOME_SGH-T989user_CL799405_REV00.tar.md5 for 2.3.6.
Tmobile LE1 ICS FULL ROM for 4.0.3.
3. Press Start!
4. Once it's done, it should look like this.
Now, it should reboot to recovery and delete cache and data. Then, it will boot.
Your now on stock, if this didn't work for you, write in the comments, What device you have (T989D or T989) if it went to Download Mode, and what didn't work!
HOW TO ROOT YOUR PHONE
1) Download This Recovery : ClockworkMod TOUCH 5.5.0.4
2) Download The SU Files : SU Files + Superuser
3) Flash SU Files In Recovery.
4) ENJOY
Thanks for your time, this useful. Maybe they could check the battery, before anything. For a real noob guide, add in download links for drivers, odin, and files, etc.
Thanks for this good job.If I can suggest also putting 2.3.5 stock zip up.It is easy to root with superonclick.Then flash a 2.3.6 ROM of your choosing.thanks again.
Edit:Or I guess you can just flash recovery then flash a 2.3.6 rooted ROM to get your root.
From a glaxay better than yours.
asapelectric said:
Thanks for your time, this useful. Maybe they could check the battery, before anything. For a real noob guide, add in download links for drivers, odin, and files, etc.
Click to expand...
Click to collapse
ummmmm... check the download links ! xD
This should be stickied.
Sent from my SGH-T989 using XDA App
jordanishere said:
This should be stickied.
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
Yay!
10 char
Unfortunately none of these methods here work if you are unfortunate enough to have the black screen and it won't go into download mode, recovery or boot. That my friends is a true brick.
raycaster3 said:
Unfortunately none of these methods here work if you are unfortunate enough to have the black screen and it won't go into download mode, recovery or boot. That my friends is a true brick.
Click to expand...
Click to collapse
That happened to me, somehow the G2x USB saved my phone.
alphadog32 said:
That happened to me, somehow the G2x USB saved my phone.
Click to expand...
Click to collapse
Know of where to buy a real oem usb cable?
——————————
Deebo took your bike too?
The odin pix you have is Odin 3. (Android+SLP) but the the odin 1.85 that is in OP is not the same, after downloading, it shows EPIC 4G and not the same on the op. the pix in the op is the odin i use for vibrant. did i dl the the right odin 1.85?
jay661972 said:
The odin pix you have is Odin 3. (Android+SLP) but the the odin 1.85 that is in OP is not the same, after downloading, it shows EPIC 4G and not the same on the op. the pix in the op is the odin i use for vibrant. did i dl the the right odin 1.85?
Click to expand...
Click to collapse
Its not supposed to look the same, just to show you how it kinda lloks
Exactly what I was thinking...this just fixes a "soft" brick
Did you guys not already have "soft" brick how to in the Dev section
..
raycaster3 said:
Unfortunately none of these methods here work if you are unfortunate enough to have the black screen and it won't go into download mode, recovery or boot. That my friends is a true brick.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I727 using XDA App
what are my options for hard bricked device ?
it hangs on black screen, no download mode no CWM no nothing.
Only when i connect it to the pc in device manager shows qualcomm HS-USB QDLoader9008 ?
Thanks this really helped me.
This worked great after the damn forced OTA locked my phone on the white loading screen. I was so worried I had lost all my xmas pics I just took of my 1 and 2 year old daughters. I followed these instructions exactly and after a reboot all of my data, pics, video are still there. Nothing was lost
Now I just have to reroot, remove readded bloat, etc and can enjoy my phone again. Thanks sooo much.
You welcome!
Sent from my SGH-T989 using XDA App
eniac325ix said:
This worked great after the damn forced OTA locked my phone on the white loading screen. I was so worried I had lost all my xmas pics I just took of my 1 and 2 year old daughters. I followed these instructions exactly and after a reboot all of my data, pics, video are still there. Nothing was lost
Now I just have to reroot, remove readded bloat, etc and can enjoy my phone again. Thanks sooo much.
Click to expand...
Click to collapse
BTW, Try to save your photos on your EXTERNAL SDCard, not your internal. It would save you from important things like this!!
Sent from my SGH-T989 using XDA App
omegaart said:
what are my options for hard bricked device ?
it hangs on black screen, no download mode no CWM no nothing.
Only when i connect it to the pc in device manager shows qualcomm HS-USB QDLoader9008 ?
Click to expand...
Click to collapse
You can call tmobile and see if they'll replace it, and/or buy a new one?
I called T-Mobile meself.
omegaart said:
what are my options for hard bricked device ?
it hangs on black screen, no download mode no CWM no nothing.
Only when i connect it to the pc in device manager shows qualcomm HS-USB QDLoader9008 ?
Click to expand...
Click to collapse
Try to connect my device with no battery with both volume buttons pressed
Sent from my SGH-T989 using XDA App
alphadog32 said:
Try to connect my device with no battery with both volume buttons pressed
Sent from my SGH-T989 using XDA App
Click to expand...
Click to collapse
im stuck at setupconnection..

I think I need a "Hey You are Stupid Thread" just for me

First of all, forgive me for my language for I am upset with myself and hope someone can help me. I did not know where to post this, so I figured this was best place. There was not a Dumb ### (edited by VeNuM) Thread or I would have posted there.
I did some dumb stuff and used the Galaxy S2 GT-9100 forums to alter my phone. CWM, KERNEL, and Reset whole phone to GT-9100 cause things were not working lol. I did not realize there are so many versions of the Galaxy s2. Well after all the garbage I did. I am still able to go into ODIN, but I am not able to get my computer to recognize my phone now. There is no ping/notification nothing, no prompt about wrong drivers. After all of this I looked under battery and it was model Model SPH-D710, now in Odin it shows samsung gt-i9100.
Anyone have any advice?
I should have slept before doing all this...
2ndComing said:
I should have slept before doing all this...
Click to expand...
Click to collapse
If you do have a SGS2 Epic 4G Touch this is the right place to be but Q n A would be the right place...... http://forum.xda-developers.com/showthread.php?t=1953783I Download a one click of any of the roms for your version of phone, SGS2 epic 4g touch if thats what you have. If you can get into download mode, hold power and volume down. Once in Dl mode connect to pc via usb and see if one of the com ports light up in the one click. If it does you are in luck and press start. If it doesnt, try downloading the drivers. You can get them and all one clicks here........ http://forum.xda-developers.com/showthread.php?t=1903252. Hope you get it fixed.
ty
cerj said:
Q n A would be the right place...... http://forum.xda-developers.com/showthread.php?t=1953783
Click to expand...
Click to collapse
ty
cerj said:
If you do have a SGS2 Epic 4G Touch this is the right place to be but Q n A would be the right place...... http://forum.xda-developers.com/showthread.php?t=1953783I Download a one click of any of the roms for your version of phone, SGS2 epic 4g touch if thats what you have. If you can get into download mode, hold power and volume down. Once in Dl mode connect to pc via usb and see if one of the com ports light up in the one click. If it does you are in luck and press start. If it doesnt, try downloading the drivers. You can get them and all one clicks here........ http://forum.xda-developers.com/showthread.php?t=1903252. Hope you get it fixed.
Click to expand...
Click to collapse
thank you I will try the one click. I have redone the drivers so many times. The computer is not recognizing my phone at all now, like its a dead usb lol. I will see if a com will open up. It used to in ODIN but wont anymore
2ndComing said:
thank you I will try the one click. I have redone the drivers so many times. The computer is not recognizing my phone at all now, like its a dead usb lol. I will see if a com will open up. It used to in ODIN but wont anymore
Click to expand...
Click to collapse
Try different usb port in your PC and a Different cable. The stock usb cable is good, aBlackBerry one is good too. Bad cables cause probs
cerj said:
Try different usb port in your PC and a Different cable. The stock usb cable is good, aBlackBerry one is good too. Bad cables cause probs
Click to expand...
Click to collapse
I plug my atrix 4g in with the same cable adn it works fine. I do not have another cable I will have to get one and try.
Thank you all for trying to help me I really appreciate it. I will keep trying.
Uninstall all your phone drivers through the device manager or add/remove software. REBOOT. Then start from scratch. It's sometimes easier to put the phone in download mode. I'm not sure why but when I have problems connecting to my phone that always works. And yes... This should have been in q&a.
Sent from my SPH-D710 using xda premium
abadasstanker69 said:
Uninstall all your phone drivers through the device manager or add/remove software. REBOOT. Then start from scratch. It's sometimes easier to put the phone in download mode. I'm not sure why but when I have problems connecting to my phone that always works. And yes... This should have been in q&a.
Sent from my SPH-D710 using xda premium
Click to expand...
Click to collapse
Agreed. Move this thread! :banghead:
Sent from my SPH-D710 using xda premium
I'm sorry to tell you this buddy, and it looks like people here do not have enough experience with bricks either. If you've flashed a rom from the international GS2, the only way to fix it is J-TAG. Flashing international GS2 Roms, disable your usb port regardless of Odin functionality.
Thanks for the input xstatik, think a whole group of people moved on to newer phones.Dont know if there are many that know, Thanks for bringing your knowledge
In before the lock.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Galaxy Nexus LTE using Tapatalk pro
Jtag service can be found here http://mobiletechvideos.mybigcommerce.com/samsung-epic-4g-touch-jtag-brick-repair/
Ok, I know your computer has the drivers, now, download a one click ROM and a kernel tar. Make sure you have a good USB Cable.. Ive had this exact same problem. With a new USB Cable...
open ODIN and find your kernel.Tar for this device. Have it loaded in ODIN BUT the phone disconnected.
Pop out the battery and put it back in
Now put it in DL mode holding power and vol dwn, press vol up to go into Odin mode
With the new cable connect your device
Look at the odin window and you should have a yellow COM port.
Flash the kernel. After it passes, and reboots, follow the same steps above and now flash your stock ROM
Reason being, if you don't have the proper kernel for this device, the ONE CLICK ROM will most likely fail. If you follow this exactly it should work. Good luck.
Yes the phone is bricked (when I developed for this phone I bricked it so I know). Either try the jtag or get another phone. This isssue has been covered in the q and a (where this SHOULD have been. NOT development. I am moving it though...). Also, theres no reason for the language you used. Please read the rules again and follow them. Good luck.
Closed.

[Q] Bricked Arc s - SEUS/Flashtool/Pc doesn't recognise device

Greetings.
I have been surfing through and through the internets for the past three days, reading other people's posts with similar problems and still haven't been able to find a solution. I'm probably doing a single detail the wrong way and that's what's keeping me from enjoying my phone.
Background:
Rooted Arc s, Locked Bootloader. I've been using Ultimate HD 2.0.3. for 3 months now and it has started to be a little buggy and it would auto-reboot out of no particular reason. Anyhow, I saw that there's a newer version of the Ultimate HD, so i followed Jared's steps on how to apply the update, hoping that the update would fix my problems.
So, I've downloaded the zip file, placed it on my SDcard, backed up my data.
Rebooted into Clockworkmod recovery. Installed new mod from zipfile - haven't rebooted at the end of installation - went back into CWM, wiped dalvik cache, wiped Cache Partition. Whoa, that was nice and easy, time to reboot. Turned off the phone. Turned on - stuck at SONY logo.
This all seemed to me very fixable. But I can't find a way to get into CWM so that I could just return to one of my backups, nor can I flash a new firmware over the existing. (The LED doesn't blink the signal for CWM).
Out of, lets say, 20 times I've tried connecting my phone to my PC, only 3 times have I gotten the solid green light (And then Flashtool would ask me to re-plug the phone, and then, when I re-plug it, he doesn't recognize it). Most of the time it's just a fade-greenish blink and then the phone turns itself on and stays at SONY. (I always plug in the USB cable first in the phone, then hold the -back- button and then plug the USB in the PC)
Any ideas? Perhaps I need an older flashtool version to flash over GB firmware? Or is there an easier way to solve this?
Every bit of help will be most appreciated!
Thanks in advance!
DUnderline said:
Greetings.
I have been surfing through and through the internets for the past three days, reading other people's posts with similar problems and still haven't been able to find a solution. I'm probably doing a single detail the wrong way and that's what's keeping me from enjoying my phone.
Background:
Rooted Arc s, Locked Bootloader. I've been using Ultimate HD 2.0.3. for 3 months now and it has started to be a little buggy and it would auto-reboot out of no particular reason. Anyhow, I saw that there's a newer version of the Ultimate HD, so i followed Jared's steps on how to apply the update, hoping that the update would fix my problems.
So, I've downloaded the zip file, placed it on my SDcard, backed up my data.
Rebooted into Clockworkmod recovery. Installed new mod from zipfile - haven't rebooted at the end of installation - went back into CWM, wiped dalvik cache, wiped Cache Partition. Whoa, that was nice and easy, time to reboot. Turned off the phone. Turned on - stuck at SONY logo.
This all seemed to me very fixable. But I can't find a way to get into CWM so that I could just return to one of my backups, nor can I flash a new firmware over the existing. (The LED doesn't blink the signal for CWM).
Out of, lets say, 20 times I've tried connecting my phone to my PC, only 3 times have I gotten the solid green light (And then Flashtool would ask me to re-plug the phone, and then, when I re-plug it, he doesn't recognize it). Most of the time it's just a fade-greenish blink and then the phone turns itself on and stays at SONY. (I always plug in the USB cable first in the phone, then hold the -back- button and then plug the USB in the PC)
Any ideas? Perhaps I need an older flashtool version to flash over GB firmware? Or is there an easier way to solve this?
Every bit of help will be most appreciated!
Thanks in advance!
Click to expand...
Click to collapse
CWM via x-Parts right?? It is stored in system files so when you wipe everything even CWM wipes off.
You got to use SEUS. Update your device and search for the repair link. This will bring you back to stock rom.
Cheers!!
rohan170890 said:
CWM via x-Parts right?? It is stored in system files so when you wipe everything even CWM wipes off.
You got to use SEUS. Update your device and search for the repair link. This will bring you back to stock rom.
Cheers!!
Click to expand...
Click to collapse
I've tried it, but with a slightly cleaner approach. I DL'd and installed SEUS on my laptop (which hasn't been used to this kind of purpose before).
Started SEUS, connected the device for the first time, as explained, laptop recognised it as a SEMC device, SEUS recognised it, checked it and said the software was up to date. I'm not certain if this should have happened, anyho, I've tried connecting the device again for the newly installed Flashtool, but now it's back to the fade-green blink and SONY routine.
Maybe I need a different driver for the device? Perhaps my laptop has marked the device as "problematic" and doesn't want to cooperate with it or sth?
DUnderline said:
I've tried it, but with a slightly cleaner approach. I DL'd and installed SEUS on my laptop (which hasn't been used to this kind of purpose before).
Started SEUS, connected the device for the first time, as explained, laptop recognised it as a SEMC device, SEUS recognised it, checked it and said the software was up to date. I'm not certain if this should have happened, anyho, I've tried connecting the device again for the newly installed Flashtool, but now it's back to the fade-green blink and SONY routine.
Maybe I need a different driver for the device? Perhaps my laptop has marked the device as "problematic" and doesn't want to cooperate with it or sth?
Click to expand...
Click to collapse
It will say on latest firmware
Just select repair the firmware
Also in flash mode the phone disconnects after a while
U shud open flashtool and select the firmware u want to install and wait for it to load, then connect phone when u get the popup that says to connect phone
Btw this is callrd bootloop and will be pretty commen with locked bootloader(i hv the same problem XD, basically use flashtool daily)
Edit: jst reinstall the UHD 3.0.2 firmware, it has CWM pre installed on it
Idk if the beta firmware does
Sent from my LT18i using xda app-developers app
Sahaab said:
It will say on latest firmware
Just select repair the firmware
Also in flash mode the phone disconnects after a while
U shud open flashtool and select the firmware u want to install and wait for it to load, then connect phone when u get the popup that says to connect phone
Btw this is callrd bootloop and will be pretty commen with locked bootloader(i hv the same problem XD, basically use flashtool daily)
Edit: jst reinstall the UHD 3.0.2 firmware, it has CWM pre installed on it
Idk if the beta firmware does
Sent from my LT18i using xda app-developers app
Click to expand...
Click to collapse
My main problem is that I cannot connect the phone properly. I hold the back button, plug the USB in, and the PC doesn't recognise the device. I think that, after the first time i plugged it in, something went wrong.
EDIT: I don't get the solid-green light i should be getting, but instead a flash of green and boot till SONY logo.
DUnderline said:
My main problem is that I cannot connect the phone properly. I hold the back button, plug the USB in, and the PC doesn't recognise the device. I think that, after the first time i plugged it in, something went wrong.
EDIT: I don't get the solid-green light i should be getting, but instead a flash of green and boot till SONY logo.
Click to expand...
Click to collapse
You have to keep trying because flashtool does not recognise the device 100% of the time. Try restarting your computer or removing the battery from your phone before trying to connect your phone to your computer.
僕のLT18iから送られてきた
And only connect your device when you're prompted to by flashtool... Not before.
Sent from my PAC-ed LT18i.
Press the thanks button if I helped.
popthosegaskets said:
You have to keep trying because flashtool does not recognise the device 100% of the time. Try restarting your computer or removing the battery from your phone before trying to connect your phone to your computer.
僕のLT18iから送られてきた
Click to expand...
Click to collapse
I've tried deleting the "unknown device" drivers (that's how the PC recognises it), and replugging afterwards, but nothing happened.
Although, i've started up SEUS, came to the "plug in" step, and instead of pluging in the USB in the PC, i plugged it in the phone and then in the PC: I got a solid green light, PC installed and verified the device as SEMC device, but SEUS didn't move a muscle.
I'll try on a fresh PC, might just do the trick.
Thanks all for the help, keep the advices coming, very much appreciated
I've been deleting the "unknown device" 's drivers and replugging my arc and, well, it was mostly luck. On one attempt SEUS recognised the device, ran it's check procedure, and gave me a "everything's up to date" answer. There was no 'repair' button. Image included in post.
While i was at it, i decided to try my luck with flashtool aswell. after a series of no-recognition at all, i got some attempts through, but no flashing occured. and then once i got a 15-20% of flashing done, before it was interrupted by dont-know-what. image included aswell.
Any ideas? My bootloader is locked I think, i've found a post to fix it with an unlocked bootloader, but i've got no idea how to unlock it if i can't access my phone.
P.s: my SEUS is in my native language. the translations would be:
Finished! There is no new software available for your phone. Your phone already has the newest available software installed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
PC Companion also has the option to repair firmware. Try it.
FIXED. Hate it when someone posts an issue, solves it, and then doesn't explain how he did it.
Anyho, this is all about patience and determination. I've installed an older version of the Flashtool (0.6.) on my laptop and i was getting about 5% of the flashing procedure completed. From time to time i'd get more than 5%, until eventually i got to 100%, now my device is working on a so-far stable GB.
Details: I would first plug in the USB in the PC, then hold the back button, then plug in the phone. I kept the back button pressed during the entire flashing procedure, not sure if it helped, but hey, it worked.
I've also used a stock GB firmware, link was found on this website somewhere on the internets.

Nexus Dead?!

So, basically I downloaded cm10.1 nightly and it was rebooting every some hour, this morning when i turned it on it immediately started rebooting and it kept rebooting until i pulled the battery.
so i went to the cwm recovery and tried to flash a backup, but whenever i tried to flash the backup it also rebooted..
then i downloaded the google nexus toolkit and thought i could restore my nexus with it, but since i can't boot into android, i can't get adb access...
i'm really lost right now, does anyone know what i can do?
thanks in advance :crying:
error i get in the toolkit
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Too many links I believe is usually a USB issue, either port on PC, port on phone, USB cable, or even drivers issues on your PC (as in USB driver issues). I could be mistaken on this, but I seem to remember reading that was the solution to this problem a while back.
cupfulloflol said:
Too many links I believe is usually a USB issue, either port on PC, port on phone, USB cable, or even drivers issues on your PC (as in USB driver issues). I could be mistaken on this, but I seem to remember reading that was the solution to this problem a while back.
Click to expand...
Click to collapse
drivers are fine i guess, since i used the toolkit some days ago and everything worked fine..
also i tried to use this guide to start my gnex : http://rootzwiki.com/topic/12069-gu...able-bootloopingpseudo-brickedbricked-phones/
but i get this error again...
Toxina said:
drivers are fine i guess, since i used the toolkit some days ago and everything worked fine..
also i tried to use this guide to start my gnex : http://rootzwiki.com/topic/12069-gu...able-bootloopingpseudo-brickedbricked-phones/
but i get this error again...
Click to expand...
Click to collapse
just change your usb cable or usb port
samersh72 said:
just change your usb cable or usb port
Click to expand...
Click to collapse
doesnt help at all x.x
Do you have kies installed? Just probing an idea.
a manta wrote this.
beekay201 said:
Do you have kies installed? Just probing an idea.
a manta wrote this.
Click to expand...
Click to collapse
i dont, also now i have a weird symbol, its like "phone then two dots then a big yellow exclamation mark followed by two dots and then a computer"
edit : got a picture for the symbol i get upon start.. : http://i.imgur.com/RI9lxWO.jpg
can't boot into fastboot anymore..
edit :
kay tried to do it with odin and odin hangs at system too..
Try my odin package (see my sig) and use odin 1.85
sent from my Galaxy
samersh72 said:
Try my odin package (see my sig) and use odin 1.85
sent from my Galaxy
Click to expand...
Click to collapse
didn't help in any way :/
ugh im getting frustrated :crying:
any ideas are welcome at this point ._.!
Toxina said:
any ideas are welcome at this point ._.!
Click to expand...
Click to collapse
"Odin flashing is like taking a lottery ticket! U never know when u hit the jackpot!"
retry with odin + pit file
samersh72 said:
"Odin flashing is like taking a lottery ticket! U never know when u hit the jackpot!"
retry with odin + pit file
Click to expand...
Click to collapse
tried it but im still stuck at system..
ugh push ;-;
Toxina said:
ugh push ;-;
Click to expand...
Click to collapse
Don't "push" threads, take it easy. It's not going to help if you're stressing about it, believe me. What's your platform-tools version? R16?
http://forum.xda-developers.com/showthread.php?t=1760787
beekay201 said:
Don't "push" threads, take it easy. It's not going to help if you're stressing about it, believe me. What's your platform-tools version? R16?
http://forum.xda-developers.com/showthread.php?t=1760787
Click to expand...
Click to collapse
dont know what version but the date is : 2013 05 22
btw i got my nexus to boot to stock with a sideloaded zip BUT every time i wanna take a photo it freezes and reboots, and when i try to record a video it'll also freeze and reboot, it'll also freeze and reboot if i try to put something into the sd-card through usb, it also makes a loud popping voice everytime it reboots..
edit : it also sometimes freezes on reboot, i think there's something wrong when writing/reading/deleting/saving data with my gnex...
pushing this cause i still need help v.v
still need help.

Galaxy Tab s 10.5 SM-800 (wifi) No boot

I have been searching and reading quite a bit here on the forums trying to find an answer to this problem. I haven't found a thread that answers my question, though I've seen many threads with different things I can try. I explain the problem and what I've tried to do to fix the problem here.
The problem:
I decided to give IronRom a try on my tablet. I installed the following:
http://forum.xda-developers.com/galaxy-tab-s/development/prerooted-stock-touchwiz-rom-t2973107
Everything worked great for about 2 weeks. However, one day I went to turn on the tablet and I was stuck in a boot loop. I could get to the Samsung Galaxy Tab S screen but no further before the tablet would reboot.
Here is what I've tried to fix the problem:
1. First I tried going into TWRP to do a full wipe. I cannot get the tablet to enter recovery mode. Power/Home/Volume Up does nothing. I can get the tablet to enter download mode through Power/Home/Volume Down.
2. Using Odin I tried reflashing TWRP but no matter what I did, I couldn't get into recovery.
3. Using Odin I went over to SamMobile and got my stock rom. I flashed it and according to Odin, it was a success. But when it auto rebooted, it brought up the Samsung screen once, rebooted and now I'm stuck with the logo screen on all the time. Holding the power button does not turn the tablet off. I can still get into download mode though.
Pic of Odin:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Video of what the tablet is doing:
https://youtu.be/_hFiEhtQtZs
At this point I need suggestions. I'm not seeing any .pit errors but am not sure that would be worth pursuing. If I do, I'll need a little help learning how to do that.
QUOTE=Drschplatt;69922876]I have been searching and reading quite a bit here on the forums trying to find an answer to this problem. I haven't found a thread that answers my question, though I've seen many threads with different things I can try. I explain the problem and what I've tried to do to fix the problem here.
The problem:
I decided to give IronRom a try on my tablet. I installed the following:
http://forum.xda-developers.com/galaxy-tab-s/development/prerooted-stock-touchwiz-rom-t2973107
Everything worked great for about 2 weeks. However, one day I went to turn on the tablet and I was stuck in a boot loop. I could get to the Samsung Galaxy Tab S screen but no further before the tablet would reboot.
Here is what I've tried to fix the problem:
1. First I tried going into TWRP to do a full wipe. I cannot get the tablet to enter recovery mode. Power/Home/Volume Up does nothing. I can get the tablet to enter download mode through Power/Home/Volume Down.
2. Using Odin I tried reflashing TWRP but no matter what I did, I couldn't get into recovery.
3. Using Odin I went over to SamMobile and got my stock rom. I flashed it and according to Odin, it was a success. But when it auto rebooted, it brought up the Samsung screen once, rebooted and now I'm stuck with the logo screen on all the time. Holding the power button does not turn the tablet off. I can still get into download mode though.
Pic of Odin:
Video of what the tablet is doing:
https://youtu.be/_hFiEhtQtZs
At this point I need suggestions. I'm not seeing any .pit errors but am not sure that would be worth pursuing. If I do, I'll need a little help learning how to do that.[/QUOTE]
hi, just buy a micro USB JIG on eBay and you will get into the download mode to flash a stock rom with Odin... I did have the same problem and I solve it with the JIG !:good:
http://www.ebay.de/itm/151703102753
sorry for my English
---------- Post added at 06:22 PM ---------- Previous post was at 06:09 PM ----------
I have been searching and reading quite a bit here on the forums trying to find an answer to this problem. I haven't found a thread that answers my question, though I've seen many threads with different things I can try. I explain the problem and what I've tried to do to fix the problem here.
The problem:
I decided to give IronRom a try on my tablet. I installed the following:
http://forum.xda-developers.com/galaxy-tab-s/development/prerooted-stock-touchwiz-rom-t2973107
Everything worked great for about 2 weeks. However, one day I went to turn on the tablet and I was stuck in a boot loop. I could get to the Samsung Galaxy Tab S screen but no further before the tablet would reboot.
Here is what I've tried to fix the problem:
1. First I tried going into TWRP to do a full wipe. I cannot get the tablet to enter recovery mode. Power/Home/Volume Up does nothing. I can get the tablet to enter download mode through Power/Home/Volume Down.
2. Using Odin I tried reflashing TWRP but no matter what I did, I couldn't get into recovery.
3. Using Odin I went over to SamMobile and got my stock rom. I flashed it and according to Odin, it was a success. But when it auto rebooted, it brought up the Samsung screen once, rebooted and now I'm stuck with the logo screen on all the time. Holding the power button does not turn the tablet off. I can still get into download mode though.
Pic of Odin:
Video of what the tablet is doing:
https://youtu.be/_hFiEhtQtZs
At this point I need suggestions. I'm not seeing any .pit errors but am not sure that would be worth pursuing. If I do, I'll need a little help learning how to do that.
Click to expand...
Click to collapse
hi, just buy a micro USB JIG on eBay and you will get into the download mode to flash a stock rom with Odin... I did have the same problem and I solve it with the JIG !:good:
http://www.ebay.de/itm/151703102753
sorry for my English
I appreciate the reply, but I am already able to get into download mode and can connect my tablet using Odin. I was even able to flash the stock rom as the photo in my post showed. So I'm a little confused. How is a jig going to help me? Isn't that just for accessing download mode?
What I cannot access is recovery.
Drschplatt said:
I have been searching and reading quite a bit here on the forums trying to find an answer to this problem. I haven't found a thread that answers my question, though I've seen many threads with different things I can try. I explain the problem and what I've tried to do to fix the problem here.
Click to expand...
Click to collapse
Do you have android SDK tools installed on your PC? If you do you can connect your tablet to your PC via USB and enter in the command prompt, "adb reboot recovery". If it reboots to recovery you can try doing a factory reset.
Sent from my SM-T800 using XDA-Developers mobile app
Eddie Hicks said:
Do you have android SDK tools installed on your PC? If you do you can connect your tablet to your PC via USB and enter in the command prompt, "adb reboot recovery". If it reboots to recovery you can try doing a factory reset.
Sent from my SM-T800 using XDA-Developers mobile app
Click to expand...
Click to collapse
I don't, but I'd be very happy for a little info on how that process works. Do you know of a guide for that off hand? I can google it course .
Drschplatt said:
I don't, but I'd be very happy for a little info on how that process works. Do you know of a guide for that off hand? I can google it course .
Click to expand...
Click to collapse
If you're new to it, it may seem a little complicated at first but really isn't. Here is a good start on XDA that explains a lot. http://forum.xda-developers.com/showthread.php?t=2317790 There are links there for the software. One tip, if you know how to add a folder to your Window's path, add the folder with the sdk files to it. That way you can run the command anywhere on your PC. If not, open the folder with the files, hold the shift key and right click in the folder and choose "open command window here" I was able to fix an ASUS tablet that I almost threw away because of a similar issue. Good luck.
Eddie Hicks said:
If you're new to it, it may seem a little complicated at first but really isn't. Here is a good start on XDA that explains a lot. http://forum.xda-developers.com/showthread.php?t=2317790 There are links there for the software. One tip, if you know how to add a folder to your Window's path, add the folder with the sdk files to it. That way you can run the command anywhere on your PC. If not, open the folder with the files, hold the shift key and right click in the folder and choose "open command window here" I was able to fix an ASUS tablet that I almost threw away because of a similar issue. Good luck.
Click to expand...
Click to collapse
Just a question. If I cannot get the device to boot past the samsung screen, and I can only get into download mode on the device, how am I supposed to get the SDK tools to connect to my device?
Odin will connect, but my computer doesn't recognize the tablet as a storage device or anything. Maybe I'm just not understanding how SDK works. All I'm getting are errors saying no device was found.
Drschplatt said:
Just a question. If I cannot get the device to boot past the samsung screen, and I can only get into download mode on the device, how am I supposed to get the SDK tools to connect to my device?
Odin will connect, but my computer doesn't recognize the tablet as a storage device or anything. Maybe I'm just not understanding how SDK works. All I'm getting are errors saying no device was found.
Click to expand...
Click to collapse
I haven't been using ADB for awhile and I forgot the particulars. I just tried ADB rebooting to recovery from download mode and it doesn't work. Did you enable USB debugging in Developers options? If not in setting go to about device, tap on build number about 7 times and it will let you access Developers options, there you can enable USB debugging. You may also need to install drivers for your tablet if you already haven't. I forgot did you say your tablet reboots to download mode or you use your buttons? If you can get to any screen besides download you can try ADB reboot to recovery from there. There is a lot of things you can do like install recoveries if you can only get ADB and fastboot to recognize your tablet. There are other people who are way more knowledgeable with ADB than I am. Maybe you can search around for advice. Sorry if I got your hopes up and it doesn't work but I guess it never hurts to try.

Categories

Resources