I have a T999 that is locked up. I would like to try and restore this phone if I can. The buttons do nothing anymore. I cant get it into recovery (was TWRP) or download.
I found someone who had made a debrick image to boot from the SDcard. I have it on a 32G sdcard and can kind of get it to boot with the sdcard. Usually it only stays in recovery or download for a few seconds. I cant get Odin to connect to the T999. Odin sees my Galaxy S4 fine though.
Any ideas of how to recover this phone or should I just forget it? I am about sick of Windows 7 (64) so I am about to go back to Linux if that would help. Thanks for any tips.
I was able to get TWRP installed, kind of. Im not sure which TWRP. It was on another debrick image. Now it is working with the buttons though. It just wont make it past the logos on recovery, boot, or download. I was able to make it to the TWRP rom image install one time but, I didnt have any roms on an sdcard. By the time I got a rom loaded on a card the phone rebooted.
Any ideas on what is so messed up on this phone or how I can get the correct TWRP or CWM installed correctly?
Getting Close
I have TWRP 2.8.6.0 installed and kind of working. I have a T999TMBEMJC rom installed that kind of works. Random reboots though. I do get errors in recovery about writing to /data even after formatting in TWRP. I even installed Docs PIT.
Im starting to wonder if it isn't because I replaced the glass with a cheap replacement that floats over the display? It seems to be working a little better if I don't touch it.
Update: I think its the power button. If I so much as brush it (no click), the screen goes off or it tries to reboot. Only took 56 recovery installs and 6 sdcard debrick recovers.
Any ideas on how to fix the power button?
Update 2: Got it. It was the small piece of felt between the power button and the frame. Removed that and it works fine now. TWRP, Download and custom Rom all work fine now.
Hope this might help someone else. I think this can be closed. Thanks.
Related
Try to flash to JH2 (and repartition 512) - the stock B model firmware.
If it fails - try to push one of complete roms (doc_kalpik) and install it using clockwork.
Otherwise have no idea what is wrong.
.....
I will download the firmware files now,
any instructions on how to use clockwork? and install the complete rom?
Did you perform a repartition when you reflashed ?
ignore me wrong thread!
inshadesofgrey said:
I will download the firmware files now,
any instructions on how to use clockwork? and install the complete rom?
Click to expand...
Click to collapse
isnt there a install guide in doc-kaplik topic? In clockwork (might need to push update.zip and rom manually - dont remember how) choose install zip from sdcard and navigate to file you need.
i did......still didnt work
Sounds like what mine was doing when the internal SD died.
dupel said:
isnt there a install guide in doc-kaplik topic? In clockwork (might need to push update.zip and rom manually - dont remember how) choose install zip from sdcard and navigate to file you need.
Click to expand...
Click to collapse
will this work even if i didnt have clockwork on my phone?
I flashed the stock JH2 with 512.pit and reparition checked, but the phone goes to the samsung logo, and flash animation and to a blank screen with only the buttons lit up........ah, am losing all hopes really fast.
Now that you are on jh2 take out sim leave external sd inside charge it til full, turn on while and it will boot, saying no memory going internal or external.
So far that would be doa, unless someone found a way to fix or reformat external card but most people that sent it for repair with these symptoms had done doa exchange like me twice or samsung replaced external module meaning it was hardware issue. Sorry.
Sent from my i9000M
it's a long shot, but can I buy an external SD card and run android from there?
I am guessing the only hope is to buy a new phone then?
inshadesofgrey said:
Hi guys, I have been a silent observer of XDA for a while now and you guys have helped through the past 4-5 phones that I've had - but now, I am stuck, so I thought I'll ask for help.
I have a galaxy S (i90000-GT) - originally from Bell, Canada but unlocked. I was running the XJPH with lag-fix and two days ago, when the phone rebooted, it got stuck in a boot loop, samsung logo with black screen comes on, and it starts all over again. Now, I can get into download mode and I followed the process to install JM8, and the stock file (the US Vibrant stock file) and I tried this as well:howto-froyo-fw-i9000xxjpm-upgrade-via-odin-root-recovery-2e-lagfix/[
But to no avail. The boot loop is still there. With JM8, the phone boots up and the goes beyond the flash samsung logo (with the music) but loads to a black screen, with the lights on.
Am really frustrated as this is my only work phone (and I go back to work tomorrow). Without the phone, I am pretty much screwed. I dont care about the Data on the phone (have performed 3-4 data wipes during installing the above mentioned roms) . So anything you can advise, will help!
any ideas?
Click to expand...
Click to collapse
Have you wiped your data/factory reset & wiped your cache? Many phones get stuck at startup because of them.
So I looked in the bricked section and the bootup sections and couldn't find my answer. I am sure it is somewhere but my search didn't turn it up. I have been using the sprint SII for about 8 months now, no real problems. I rooted it and flashed over using Odin an older version of Calkin's EG4T rom, it worked fine, I updated it about 3 months ago to the newest version (honestly I forget which but it was right before ICS started coming out). Today I come home from work and find my phone black screen off when I hadn't turned it off. I try and turn it on and nothing. So I pop out the battery and restart it, it loads up but everytime I try something it comes up with provider error and crashes the program, even when calling. So I boot into recovery and delete the cache and try again, same problem. Try to reinstall using recovery from the old update.zip file, it goes through but now it only boots into recovery, no booting into a new ROM at all. I check to see if I can still enter the download option and I can but I haven't gotten the newest tar file to push from odin so I quit. I try one last time to use android commander to copy over a new ROM, it appears to copy and I try the install and it claims it completed and now my phone only boots to the Samsung Galaxy SII screen. It won't go any further, I can't enter recovery OR download screen. I have tried leaving the battery out for 5 minutes and still stuck at the same screen. I can reboot from the screen but nothing else. Odin is unable to push the newest rom onto the system. Anyone who has any ideas I welcome it as I really do need this phone tomorrow.
thanks and I do hope I didn't miss an obvious thread covering this exact problem, but I do not believe i did.
you say you can't get into recovery or download, but also say that odin won't push newest rom onto system. Are you sure you're holding right buttons to get into download mode? (power+vol dwn, then volume up once the screen comes up to bootloader)
Well update, still fun. I pulled the battery for 10 minutes and now am able to get to the download screen (I was clicking for it correctly before I swear), and I pushed the newest Calkin's rom and it went through. But I am still stuck on load at the samsung screen. And what is even more fun is it won't actually turn off. I hold the power button for power off and it just restarts the sucker. I am going to try and push the stock rom next. Any other ideas?
thanks
If you can't get into download you're bricked. What update.zip did you flash? Usually that only works if you flash an authentic sprint/Samsung update or created a signed update.zip on your own. Also, did you flash it from stock recovery or clockwork mod?
Sent from my SPH-D710 using XDA
dante32278 said:
If you can't get into download you're bricked. What update.zip did you flash? Usually that only works if you flash an authentic sprint/Samsung update or created a signed update.zip on your own. Also, did you flash it from stock recovery or clockwork mod?
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
I did the update through cwm just as I had done previously so I figured it would work, but it seems I figured wrong
I am now able to get back into CWM but still unable to actually load past the samsung screen (yes I have left it going for a while), any ideas? Also trying to determine which specific kernal is the newest stock kernol for the sprint s II, any links? I am seeing lots of modified but nothing stock (in tar format).
thanks
edit- When I access the phone through android commander (it finds it) the folders it shows as being on the phone are all incorrect. Some of the titles are correct but the actual files within are missing or it is claiming the folders were made in 2000. I know I have not wiped the SD card as I can see it via cwm but can't seem to edit it on commander.
Also I am unable to actually view the phone when in cwm through android, only finding it in commander when it is stuck in the loading samsung screen
Final edit:
Finally got a stock one click to fully complete through Odin! back to stock, now to reroot and get my old stock on there
I have Cyanogenmod 10.1 (stable) installed; the other day it crashed while I was on Instagram, rebooted itself, and wouldn't go past the spinning circle screen. Tried rebooting it, now it won't go past the screen before that, with the blue Cyanogenmod man and the Samsung logo.
I have TWRP 2.5.0.0 installed with it, which I don't know how is possible being that the file systems are incompatible, so unless I used Odin to install CM10.1, I don't know how I did it without installing Clockworkmod Recovery over TWRP.
I've been trying to fix it for a couple days now (I'm kicking myself for not getting around to posting here sooner). When I go into TWRP it asks me for a password (which I've never set, I assume it's asking me because that's all it knows to do when the file system is incompatible), which I click cancel at every time, and when I try to do just about anything (including installing new ROMs or recoveries from within TWRP) it gets errors when trying to mount any partitions on the device, so I can't change anything on the phone at all.
I've tried re-installing TWRP AND Clockworkmod Recovery with Odin, and they succeed, but when the phone tries to reboot, the screen just turns off and nothing happens, and I have to take the battery out to do anything else.
So right now I'm totally screwed unless I can fix this thing. I'd like to not have to drop 200 on a Nexus 4 after only a year or having this phone I bought brand new, especially with the Nexus 5 already coming out later this year...can somebody help me???
EDIT: I should clarify that I can access recovery and download mode
If you can get into download mode you can flash a stock image to your phone and restart from scratch. Download the proper stock image from here http://forum.xda-developers.com/showthread.php?t=1968625 and flash it in odin.
FoxTrotz said:
If you can get into download mode you can flash a stock image to your phone and restart from scratch. Download the proper stock image from here http://forum.xda-developers.com/showthread.php?t=1968625 and flash it in odin.
Click to expand...
Click to collapse
I should've clarified that I've tried this with a bunch of roms, and it just shows SBA2 in the status box forever. I left it for a full hour before and it never changed.
According to this page http://www.alliance-rom.com/community/wiki/bricked-android/ reformating your external sd card may help. It also links to something I personally have never heard of but apparently this: http://forum.xda-developers.com/showthread.php?p=15330252 can help unbrick any samsung phone that's flashable with odin.
I need some serious help here! I own a sim unlocked i317 (I bought it second hand and it was already unlocked-1 year back). It was working fine (except it used to get restarted itelf 4-5 times a day since past month) and then last night after completing charging it was working fine and I slept then. When I woke up, to my horror, the phone was stuck at "Samsung Galaxy Note II" screen. I tried after removing SIM and mSD, and then restarting it but to no avail!
So the phone is stuck in Bootloop, it had latest jellybean rom from AT&T that had been sim unlocked. Recovery menu shows Philz Touch 6 with some errors like:
"Can't mount system/recovery"
"Cant load system/command" etc.
I am here seeking help in retrieving my stuff on internal memory and, if possible, all app and phone data before I try a factory reset or install fresh rom!
Any kind of help would be highly appreciated! Thank You!
PS: I'm not a proper programmer as my field is DBMS, but since I have basic know how of programming, I would manage to try your suggestions!
ok this should be a fairly easy fix. I would stop using Philz recovery as a first step. You should be able to flash the newest version of TWRP without losing any internal data or storage. go here to get twrp and flash in ODIN. https://twrp.me/devices/samsunggalaxynote2att.html
Once you have this one your device boot into recovery and you can use the file manager to move and folders you want to save to an external Sd card. You may also be able to get a computer to recognize the device and copy your files that way.
Hello XDA,
Recently, a Samsung Captivate Glide was given to me to see if I could repair it. They told me the phone wouldn't turn on anymore, the screen remained black. Although they said they had just replaced the battery, I insisted that the battery was the problem. Upon hooking it up to a multimeter it became apparent that the battery was in deep sleep so I recovered it with a sliced USB cable. The phone then turned on to charge, but since I didn't feel like waiting for it to charge I inserted my S2 battery to boot it up.
Upon booting up the phone the Rogers screen came up (it's the Rogers model - sch-i927r), it adjust the brightness a bit and then proceeded to sit there forever. Since it wouldn't boot up I tried checking if Download Mode was still working. And it was! Same goes for the Android Recovery. Since this phone was never rooted or had a custom recovery it still had Gingerbread. Since the owner needed some files that were still on the phone I decided to flash TWRP, the CM11 compiled one, copy all the files to my PC and proceed to flash CM11 after making a backup.
However the phone refused to flash TWRP. I also tried CWM and going back to Stock but had no positive results. I even tried different Odin versions and different PCs. All of them gave out the same error that I have attached as a Picture. Upon googling it it seems like the storage is in read only mode, which I learnt from the Galaxy Tab 10.1 forums and also that the only solution would be to go back to Samsung.
Lastly I attempted to wipe from the built in recovery It asked for a password, however the original owner claimed he never had one. Upon forcing the flash by entering the wrong password the phone said it completed successfully but looking at the internal storage proves otherwise as all the files are still there. Trying to reboot to the system makes it either go to a black screen or corrupt the GPU memory (possibly - see attached pics.).
Looking around on the XDA forums I stumbled upon a thread by @steadfasterX which made a mod to boot the phone from an SD card. Since the eMMC of the phone is likely corrupt and causing this, could we use an SD card as the internal storage and boot up from there?
I am out of ideas. I don't have a backup of the EFS so I am being really cautious and fixing it wouldn't be worth it. So please help me! Any help is very much appreciated!
Thanks in advance!
chrismin13 said:
Hello XDA,
Recently, a Samsung Captivate Glide was given to me to see if I could repair it. They told me the phone wouldn't turn on anymore, the screen remained black. Although they said they had just replaced the battery, I insisted that the battery was the problem. Upon hooking it up to a multimeter it became apparent that the battery was in deep sleep so I recovered it with a sliced USB cable. The phone then turned on to charge, but since I didn't feel like waiting for it to charge I inserted my S2 battery to boot it up.
Upon booting up the phone the Rogers screen came up (it's the Rogers model - sch-i927r), it adjust the brightness a bit and then proceeded to sit there forever. Since it wouldn't boot up I tried checking if Download Mode was still working. And it was! Same goes for the Android Recovery. Since this phone was never rooted or had a custom recovery it still had Gingerbread. Since the owner needed some files that were still on the phone I decided to flash TWRP, the CM11 compiled one, copy all the files to my PC and proceed to flash CM11 after making a backup.
However the phone refused to flash TWRP. I also tried CWM and going back to Stock but had no positive results. I even tried different Odin versions and different PCs. All of them gave out the same error that I have attached as a Picture. Upon googling it it seems like the storage is in read only mode, which I learnt from the Galaxy Tab 10.1 forums and also that the only solution would be to go back to Samsung.
Lastly I attempted to wipe from the built in recovery It asked for a password, however the original owner claimed he never had one. Upon forcing the flash by entering the wrong password the phone said it completed successfully but looking at the internal storage proves otherwise as all the files are still there. Trying to reboot to the system makes it either go to a black screen or corrupt the GPU memory (possibly - see attached pics.).
Looking around on the XDA forums I stumbled upon a thread by @steadfasterX which made a mod to boot the phone from an SD card. Since the eMMC of the phone is likely corrupt and causing this, could we use an SD card as the internal storage and boot up from there?
I am out of ideas. I don't have a backup of the EFS so I am being really cautious and fixing it wouldn't be worth it. So please help me! Any help is very much appreciated!
Thanks in advance!
Click to expand...
Click to collapse
you can not boot from sd card, you can use sd card as system partition, but you still need place kernel+ramdisk on internal flash.
You can try to replace bootloader
bubor said:
you can not boot from sd card, you can use sd card as system partition, but you still need place kernel+ramdisk on internal flash.
You can try to replace bootloader
Click to expand...
Click to collapse
Thanks for the reply, I'll try updating the bootloader. Would it be risky though? I couldn't flash anything else and have no nandroid backup. Also, how would I go about using the SD Card as system?
EDIT: Risked it, flashed correctly but I still get the same error and I still have the Rogers bootloader. Any other ideas?
chrismin13 said:
Thanks for the reply, I'll try updating the bootloader. Would it be risky though? I couldn't flash anything else and have no nandroid backup. Also, how would I go about using the SD Card as system?
EDIT: Risked it, flashed correctly but I still get the same error and I still have the Rogers bootloader. Any other ideas?
Click to expand...
Click to collapse
maybe check "phone bootloader update" on the left side, I think I didnt check when I did update, and it worked without checking.
First try this pack: http://dualhoki.vim.hu/bubor/dev/I927UCLG9_OneClick.exe
Try to repartition with pit file ( put pit file in pit box, no other files, and check re-partition)
You can find an alternative of odin http://glassechidna.com.au/heimdall/ . I remember there are many other options in heimdall, maybe you can find usefull error messages.
bubor said:
maybe check "phone bootloader update" on the left side, I think I didnt check when I did update, and it worked without checking.
First try this pack: http://dualhoki.vim.hu/bubor/dev/I927UCLG9_OneClick.exe
Try to repartition with pit file ( put pit file in pit box, no other files, and check re-partition)
You can find an alternative of odin http://glassechidna.com.au/heimdall/ . I remember there are many other options in heimdall, maybe you can find usefull error messages.
Click to expand...
Click to collapse
Hello,
Sorry for the late response. I got around to trying most of that. First off the PIT File was something that I was looking forward to since it seemed the most likely solution. However it didn't work, giving out a similar message as everything else. The OneClick also failed with a similar message. As for heimdall I couldn't get the drivers to work but even if I had it wouldn't have helped anymore most likely.
I am out of ideas. I highly doubt this phone is recoverable at this point.
Thank you for all the help so far!
Anyone got any other ideas? I think it's safe to call it dead at this point, but I am willing to try anything to fix it!
Thanks.