Hello,
I have the Galaxy S II T989 (Tmobile) and the screen got broken and is completely black. But The phone is working and i can start it and feel the vibe at start and after it starts, i cant tap the bottom 4 buttons and they light up.
My phone was protected by pattern password. So when i connect the phone to USB and launch Kies , it asks me to unlock it...
But i can't since my screen is broken and doesn't light up.
Is there a way to download the internal contents of the flash memory (not the SD card) to the PC somehow?
I have tons of pictures and video clips that are very important to me.
Please help.
Paul.
Is USB debugging enabled? If so, you may be able to pull the files that way. You may also be able to do it through recovery (hold both volume buttons down at powerup while not USB connected). If you can get adb access, you can use it to pull the pictures that way.
Sent from my Polaroid Tablet using Tapatalk 2
Boot into recovery. Connect USB to PC Mount drives. Success!!
Sent from my SGH-T989 using xda premium
LoopDoGG79 said:
Boot into recovery. Connect USB to PC Mount drives. Success!!
Sent from my SGH-T989 using xda premium
Click to expand...
Click to collapse
When you say to boot into recovery, do you refer to VOL_UP + VOL_DOWN + PWR buttons at boot ? When you get to the menu that you can select between Device reboot, Firmware update using external memory, etc...
Or are you referring to something else?
Thanks much!
laker4ever said:
When you say to boot into recovery, do you refer to VOL_UP + VOL_DOWN + PWR buttons at boot ? When you get to the menu that you can select between Device reboot, Firmware update using external memory, etc...
Or are you referring to something else?
Thanks much!
Click to expand...
Click to collapse
Dont know how broken your screen is or what recovery you have, but yes, that's what I mean. There is an option somewhere in recovery to mount drives.
Sent from my SGH-T989 using xda premium
What recovery you have? Being that your LCD is shattered I could guide you step by step on how many clicks on the volume rocker to access on latest cmw. Since it doesnt work the same on twrp I can you guesstimate the location on touch and maybe your screen could recognize it enough to enable you to mount from recovery..
Sent from my SGH-T989 using xda app-developers app
Best bet is either through ADB access either with USB Developer Mode turned on or using ADB in recovery to pull the files. Neither one of those options requires using the phone more than turning it on. How was the phone set up before the LCD broke? Did you root it? Did you put a new recovery on it? Or was it completely stock. If it was completely stock, go fix the LCD and then access it, there's no way around it... well... actually, you could get into Download Mode, flash a recovery, then access it that way.
h.nocturna said:
Best bet is either through ADB access either with USB Developer Mode turned on or using ADB in recovery to pull the files. Neither one of those options requires using the phone more than turning it on. How was the phone set up before the LCD broke? Did you root it? Did you put a new recovery on it? Or was it completely stock. If it was completely stock, go fix the LCD and then access it, there's no way around it... well... actually, you could get into Download Mode, flash a recovery, then access it that way.
Click to expand...
Click to collapse
I'm able to use the HDMI converter and "SEE" the screen of the phone on my TV. However, i cannot unlock it (it had the pattern lock) because the touch screen is not responding to my touch. I guess the touch sensor is broken.
It is a stock phone. never rooted it.
I was trying to get to recovery mode by pressing POWER and VOL UP and DN, but i wasn't able to see anything on my TV. Could it be that the HDMI converter into TV only works when the phone is booted normal and doesn't work in recovery mode.
How can i get it to download mode and flash the recovery?
datrapstar said:
What recovery you have? Being that your LCD is shattered I could guide you step by step on how many clicks on the volume rocker to access on latest cmw. Since it doesnt work the same on twrp I can you guesstimate the location on touch and maybe your screen could recognize it enough to enable you to mount from recovery..
Sent from my SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
The touch sensor is not working as i was able to see the screen on my TV( with the MHA - hdmi adapter) but touching the screen on the phone did nothing...
laker4ever said:
I'm able to use the HDMI converter and "SEE" the screen of the phone on my TV. However, i cannot unlock it (it had the pattern lock) because the touch screen is not responding to my touch. I guess the touch sensor is broken.
It is a stock phone. never rooted it.
I was trying to get to recovery mode by pressing POWER and VOL UP and DN, but i wasn't able to see anything on my TV. Could it be that the HDMI converter into TV only works when the phone is booted normal and doesn't work in recovery mode.
How can i get it to download mode and flash the recovery?
Click to expand...
Click to collapse
Yeah, I don't think the drivers to show on the TV screen would be loaded while in Download Mode.
There's still hope, you can still install a recovery without actually needing the touchscreen. Once in recovery, you'll be able to access your system files through adb and pull whatever you need onto your computer.
You'll have to do it all blind though because you won't be able to see if the phone has successfully rebooted into recovery. I can walk you through it step-by-step if you feel it's that important to you to recovery whatever data is on the phone.
Buy a new Phone.
h.nocturna said:
Yeah, I don't think the drivers to show on the TV screen would be loaded while in Download Mode.
There's still hope, you can still install a recovery without actually needing the touchscreen. Once in recovery, you'll be able to access your system files through adb and pull whatever you need onto your computer.
You'll have to do it all blind though because you won't be able to see if the phone has successfully rebooted into recovery. I can walk you through it step-by-step if you feel it's that important to you to recovery whatever data is on the phone.
Click to expand...
Click to collapse
Update:
I got a replacement phone and using some youtube clips and info, i swapped the boards between the two phones. So I was able to start the phone (old board, new screen), and simply transferred all data to the computer.
Now, i will put it back together and be all done.
I also enabled USB debug mode...for next time....
Thank you so much for the help.
h.nocturna said:
Yeah, I don't think the drivers to show on the TV screen would be loaded while in Download Mode.
There's still hope, you can still install a recovery without actually needing the touchscreen. Once in recovery, you'll be able to access your system files through adb and pull whatever you need onto your computer.
You'll have to do it all blind though because you won't be able to see if the phone has successfully rebooted into recovery. I can walk you through it step-by-step if you feel it's that important to you to recovery whatever data is on the phone.
Click to expand...
Click to collapse
Hello Senior Member ,
I too have a similiar dilemma. My Note 2 has a cracked screen and its all black . I am not sure the digitizer is in working condition . Although I have alot of files I wish to recover. Its been nearly a year Ive held on to it just to recover data. My phone is stock , NO ROOT and unfortunately USB Debugging has been turned off. Mind you, its a korean version, model SHVE250K . I do not want to chance rooting if I can not see the screen . I am afraid of making a mistake. ANY advice and ideas would be greatly appreciated. I would feel more confident working on it, with someone more experienced guiding me along the way.
Three letters with one word= MHL cable. I do it all the time with one of my t989's.
Now im soo broke, I cant even pay attention!
---------- Post added at 12:52 AM ---------- Previous post was at 12:47 AM ----------
laker4ever said:
I'm able to use the HDMI converter and "SEE" the screen of the phone on my TV. However, i cannot unlock it (it had the pattern lock) because the touch screen is not responding to my touch. I guess the touch sensor is broken.
It is a stock phone. never rooted it.
I was trying to get to recovery mode by pressing POWER and VOL UP and DN, but i wasn't able to see anything on my TV. Could it be that the HDMI converter into TV only works when the phone is booted normal and doesn't work in recovery mode.
How can i get it to download mode and flash the recovery?
Click to expand...
Click to collapse
If the HML cable works but doesn't respond to touch, then both the lcd AND digitizer are broken. Replacement screens have gotten sooo much cheaper than a year ago, they're like $65 now. I fix em all the time.
Now im soo broke, I cant even pay attention!
Related
Searched all over and google yada yada yada. So i end up opening a thread here.
Hello guys/babes/kids/oldfags/ifags in disguise . I have a galaxy nexus here that will only boot into
-download mode,
- fastboot (not working at all, pc wont detect its fastboot and buttons all dead when in recovey/fastboot)
- safe mode - will boot into safe mode if i did combo buttons when attached to charger/pc
The story :
When i booted it from batt pull via only power button press, it will go into download mode straight and if i power off or factory reset in safe mode, it will reboot back into safe mode.
I cant flash anything since fastboot is broken. Ive tried Odin back to factory image of Galaxy Nexus GSM ICS and Jellybean but the prob isnt solved and fastboot is still broken. Tried repartition and bootloader update in ODIN yet still fail. And after every successful flash of repackaged stock, it will directly boot into safe mode (for both ICS and JB factory image). Why i didnt flash using fastboot? Fastboot is broken that is. Lets continue...
Other hardwares are still fine as in safe boot, ive tested all the buttons, display, calls, speaker etc. This is fastboot relate i believe as no matter what pc ive tried and all types of gnex drivers i tried. It wont even fart when connecting to pc(win7 x86). ADB works fine though when i booted into the safe mode. Im able to do adb stuffs but whenever i query it to reboot to fastboot or recovery, a dead end again. OMAPflash the tuna edition for omap4460? Tried yet still the same.
Additional facts : The phone was not unlocked and tempered by any way before the prob happened but now the bootloader is unlocked after i flashed the repackaged ODIN (chainfire posted it)
So XDA Gnex'ers, LET THE HUNT BEGIN!
Sent from my GT-I9100 using xda premium
Reserved for updates
Have you stumbled across this yet?
http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/
iowabowtech said:
Have you stumbled across this yet?
http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/
Click to expand...
Click to collapse
thats omapflash, to be more precise.
op, try that. also, might want to read something more, efrant has a link on it on one of his threads.
sent from my i9250
bk201doesntexist said:
thats omapflash, to be more precise.
op, try that. also, might want to read something more, efrant has a link on it on one of his threads.
sent from my i9250
Click to expand...
Click to collapse
Yup, tried it but its still the same. Fastboot still dosent work and relashing packaged factory images in odin dosent fix the fastboot
Sent from my GT-I9100 using xda premium
Saw a Jtag service nearby and thinking of sending it in. Its roughly after conversion from RM(Malaysian Ringgit) around USD$90. Possible recovery from the issue?
Sent from my GT-I9100 using xda premium
does it try to create an error log? or are you able to pull bug report?
it boots into download mode and safemode so, there's hope.
override182 said:
Searched all over and google yada yada yada. So i end up opening a thread here.
Hello guys/babes/kids/oldfags/ifags in disguise . I have a galaxy nexus here that will only boot into
-download mode,
- fastboot (not working at all, pc wont detect its fastboot and buttons all dead when in recovey/fastboot)
- safe mode - will boot into safe mode if i did combo buttons when attached to charger/pc
The story :
When i booted it from batt pull via only power button press, it will go into download mode straight and if i power off or factory reset in safe mode, it will reboot back into safe mode.
I cant flash anything since fastboot is broken. Ive tried Odin back to factory image of Galaxy Nexus GSM ICS and Jellybean but the prob isnt solved and fastboot is still broken. Tried repartition and bootloader update in ODIN yet still fail. And after every successful flash of repackaged stock, it will directly boot into safe mode (for both ICS and JB factory image). Why i didnt flash using fastboot? Fastboot is broken that is. Lets continue...
Other hardwares are still fine as in safe boot, ive tested all the buttons, display, calls, speaker etc. This is fastboot relate i believe as no matter what pc ive tried and all types of gnex drivers i tried. It wont even fart when connecting to pc(win7 x86). ADB works fine though when i booted into the safe mode. Im able to do adb stuffs but whenever i query it to reboot to fastboot or recovery, a dead end again. OMAPflash the tuna edition for omap4460? Tried yet still the same.
Additional facts : The phone was not unlocked and tempered by any way before the prob happened but now the bootloader is unlocked after i flashed the repackaged ODIN (chainfire posted it)
So XDA Gnex'ers, LET THE HUNT BEGIN!
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
First of all, bricked mean there is nothing beside a black screen. Nowaday device are hard to brick. second, One does not simply flash a gnex with odin. It's simply a big wtf that is shining through my head. 3rd, if fastboot is not working, it's because it need a special driver that i suppose you didnt install. If you can boot your phone in fastboot but can connect to it, it's because you have a broken USB port, which is not the case since you can access adb. 4th, i'm still trying to know how you achieved this. It look to me you were following some instruction and it either ended, tl;dr i will skip a few step, hope it will work which didnt or you missed electricity. Install Kies, get your phone in download and recover your phone from it. Never attempt again to play on custom rom. Man, how can someone derp a galaxy nexus, it is like the easiest device to work with.
chadouming said:
First of all, bricked mean there is nothing beside a black screen. Nowaday device are hard to brick. second, One does not simply flash a gnex with odin. It's simply a big wtf that is shining through my head. 3rd, if fastboot is not working, it's because it need a special driver that i suppose you didnt install. If you can boot your phone in fastboot but can connect to it, it's because you have a broken USB port, which is not the case since you can access adb. 4th, i'm still trying to know how you achieved this. It look to me you were following some instruction and it either ended, tl;dr i will skip a few step, hope it will work which didnt or you missed electricity. Install Kies, get your phone in download and recover your phone from it. Never attempt again to play on custom rom. Man, how can someone derp a galaxy nexus, it is like the easiest device to work with.
Click to expand...
Click to collapse
Thx for the reply.
Some clarification here, im not the owner of this phone. Im using 9100 and im just helping a friend to recovery. Ive tried few pcs and it wont even fart when i plugged in during fastboot or recovery (i read someone that in recovery you can do some commands) but the pc(s) wont even detect a hardware being plugged in.
Plus, in fastboot, i cant press any of the hardware keys. No vol up or vol down and the power button dosent work in recovery. I only got to the 3e stock recovery via 'adb reboot recovery' during in fast mode where it booted into the relaxing chillin android with the triangle + red exclamation mark on its tummy. Pressed all buttons and it went to the 3e recovery.
At the 3e, only power button works. I cant toggle a bit using the vol keys. Note that the vol buttons work to boot the phone into fastboot and download mode and also during safe mode, all the keys works flawlessly.
So, i tried the odin method to recovery this living Gnex but with a faulty heart and kidney but it will still boot to safe mode regardless of ICS or Jellybean.
How did this happen?
I have no idea. The owner of the phone claimed that he has never rooted or tempered it in any way. Plus it was still on ICS when i first got the phone (all data was still intact but it was in safe mode at that time).
Regarding drivers, ive attempted many pcs with almost every drivers available. Shall i list em here:
- KIES
- Naked Nexus drivers
- PDA.net
- the 'official' gnex verizon driver set which is said working on GSM devices etc.
Tried those and adb+download mode works fine. Pcs detect em and tried to install the hardware n search for the drivers but not in fastboot. Its just dead.
killersloth said:
does it try to create an error log? or are you able to pull bug report?
it boots into download mode and safemode so, there's hope.
Click to expand...
Click to collapse
Adb works fine so im able to pull anything when its booted. Im not sure if we can pull anything in download mode. Adb/fastboot didnt work in download mode. Am i correct? Mind to share some light here on this. And in fastboot, none. No vol keys to operate and the 4-5 pc ive tried wont even fart a sound or hint anything saying a hardware connected. Its like its a dead circuit plugged only in fastboot.
This is quite a super rare case here. Most of the dead gnex i found on the next and also in XDA has a working fastboot that only needs drivers to make it working but on this unit, even the vol keys is dead. Awkwarddddd
Sent from my GT-I9100 using xda premium
override182 said:
Thx for the reply.
Some clarification here, im not the owner of this phone. Im using 9100 and im just helping a friend to recovery. Ive tried few pcs and it wont even fart when i plugged in during fastboot or recovery (i read someone that in recovery you can do some commands) but the pc(s) wont even detect a hardware being plugged in.
Plus, in fastboot, i cant press any of the hardware keys. No vol up or vol down and the power button dosent work in recovery. I only got to the 3e stock recovery via 'adb reboot recovery' during in fast mode where it booted into the relaxing chillin android with the triangle + red exclamation mark on its tummy. Pressed all buttons and it went to the 3e recovery.
At the 3e, only power button works. I cant toggle a bit using the vol keys. Note that the vol buttons work to boot the phone into fastboot and download mode and also during safe mode, all the keys works flawlessly.
So, i tried the odin method to recovery this living Gnex but with a faulty heart and kidney but it will still boot to safe mode regardless of ICS or Jellybean.
How did this happen?
I have no idea. The owner of the phone claimed that he has never rooted or tempered it in any way. Plus it was still on ICS when i first got the phone (all data was still intact but it was in safe mode at that time).
Regarding drivers, ive attempted many pcs with almost every drivers available. Shall i list em here:
- KIES
- Naked Nexus drivers
- PDA.net
- the 'official' gnex verizon driver set which is said working on GSM devices etc.
Tried those and adb+download mode works fine. Pcs detect em and tried to install the hardware n search for the drivers but not in fastboot. Its just dead.
Adb works fine so im able to pull anything when its booted. Im not sure if we can pull anything in download mode. Adb/fastboot didnt work in download mode. Am i correct? Mind to share some light here on this. And in fastboot, none. No vol keys to operate and the 4-5 pc ive tried wont even fart a sound or hint anything saying a hardware connected. Its like its a dead circuit plugged only in fastboot.
This is quite a super rare case here. Most of the dead gnex i found on the next and also in XDA has a working fastboot that only needs drivers to make it working but on this unit, even the vol keys is dead. Awkwarddddd
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Great to know you are not the one who did that . So if i understand correctly, you say download mode work ? If yes, flash another stock rom from chainfire using odin. No one wan't to flash with odin, but if fastboot is not working, you shall at least try it. Also, when you are putting the phone in download mode and connecting it to kies, it should detect it has to be restored. i would say the main reason for it to not work is that android debugging is not ticked in developer options. But that would be strange that adb work on safe mode. There is probably a way to that with adb but you will have to google it. Tell your friend to follow instruction next time. And ffs, do not use odin ! (Little idea too, try to get in fastboot not connected on PC and wait a few minutes then see if you can move with the volume button, then try to connect it on pc)
chadouming said:
Great to know you are not the one who did that . So if i understand correctly, you say download mode work ? If yes, flash another stock rom from chainfire using odin. No one wan't to flash with odin, but if fastboot is not working, you shall at least try it.
Click to expand...
Click to collapse
Yes i have already did that few times. Few times of ICS factory image and few with JB. All are repacked version provided by chainfire. Its the full package not the software only with stripped bootloader n recovery. Its still the same
Sent from my GT-I9100 using xda premium
http://forum.xda-developers.com/showthread.php?t=1392310
download and install toolkit from that thread ^^^^^^
uninstall all gnex drivers you installed
reboot pc, open gnex toolkit, with phone unplugged install the drivers
fastboot should work
killersloth said:
http://forum.xda-developers.com/showthread.php?t=1392310
download and install toolkit from that thread ^^^^^^
uninstall all gnex drivers you installed
reboot pc, open gnex toolkit, with phone unplugged install the drivers
fastboot should work
Click to expand...
Click to collapse
Thx, tried it on a few pcs but it still wont work. Even the volkeys in fastboot didnt work :8
Sent from my GT-I9100 using xda premium
override182 said:
Thx, tried it on a few pcs but it still wont work. Even the volkeys in fastboot didnt work :8
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
did you try flashing google's factory image in odin??
my fastboot once was unresponsive, but rebooting into it fixed it
from safemode, if you adb reboot bootloader it is unresponsive?
killersloth said:
did you try flashing google's factory image in odin??
my fastboot once was unresponsive, but rebooting into it fixed it
from safemode, if you adb reboot bootloader it is unresponsive?
Click to expand...
Click to collapse
Yes i had, still boots to safe mode and the fastboot is still dead. Yes ive tried adb reboot bootloader but its dead in fastboot, again.
Sent from my GT-I9100 using xda premium
only suggestion left is to just boot into fastboot, leave it alone for awhile (5-10 mins), then try and plug it in and mess with it.
Try doing the whole driver thing mentioned above but instead of flashing a Google image just do the boot loader portion, what settings are you using to flash in Odin?
Sparx639
killersloth said:
only suggestion left is to just boot into fastboot, leave it alone for awhile (5-10 mins), then try and plug it in and mess with it.
Click to expand...
Click to collapse
Tried yesterday, nothing happened
Sparx639 said:
Try doing the whole driver thing mentioned above but instead of flashing a Google image just do the boot loader portion, what settings are you using to flash in Odin?
Sparx639
Click to expand...
Click to collapse
First tried pda only with auto reboot, no gooding. The i tried with booloader, no good. Then bootloader only, still no good. Then i tested all including pit file, still no good.
Update, sent in for Jtagging few min ago. The phone is not with me now and ill get it back in 3days working or not. I shall report in back after 3 days. Thanks to all by giving suggestion and ideas. See u guys again in 3 days
Sent from my GT-I9100 using xda premium
chadouming said:
Also, when you are putting the phone in download mode and connecting it to kies, it should detect it has to be restored. i would say the main reason for it to not work is that android debugging is not ticked in developer options.
Click to expand...
Click to collapse
adb does not work in download mode/bootloader. adb only works when adbd (adb service) is started, and that happens in android boot process. it means android debug bridge.
sent from my i9250
Sorry for the long delay to anyone waiting for the answer/status.
Jtag cant fix it. Returned the device to a friend. Prolly a mobo replacement is the solution but its damn pricy here in Malaysia. It costs 80% of the price to get a new Gnex.
Hell yeah and thx to everyone supporting this.
Sent from my GT-I9100 using xda premium
Hi There all,
I bricked my device!
I installed multi window manager and ran the patch.
I should have not done this.
After one last message (something like copy binary from SD card) the device was dead.
Any help is highly appreciated
HANSB57 said:
Hi There all,
I bricked my device!
I installed multi window manager and ran the patch.
I should have not done this.
After one last message (something like copy binary from SD card) the device was dead.
Any help is highly appreciated
Click to expand...
Click to collapse
Can you access recovery or download mode?
sefrcoko said:
Can you access recovery or download mode?
Click to expand...
Click to collapse
No I cant.
All combinations (power, volume home etc.. failed)
Removed back cover, disconencted battery
No result.
How did you remove the back cover?
I've been able to get mine out of pickles not involving the /boot partition by holding down the volume down, home and power keys simultaneously. Shortly after the model 5110 message displays, I release power and am asked if I really want to put the device into update mode.
I use Odin to write in the firmware I downloaded from samfirmware a few weeks ago.
I needed to do this last night after trying to disable a few system apps. I'm not sure which, probably a thing called "bubble," but as soon as I had, the device froze. A reboot went all the way through but then locked up after my startups finished.
I also needed to do this after something much closer to a soft brick involving trying to use the Xposed framework to change lcd density.
I reflashed and was able to defrost and I was back in business.
roustabout said:
How did you remove the back cover?
I removed it by gently prying the white back cover of.
I would recommend agains it because its delicate.
But I think you would advice me agains bricking my device. :angel:
I cant get it in download mode.
It wont show the charging again when charging.
It seems dead
Anybody might have a clue??
Click to expand...
Click to collapse
something just occurred to me - you've pulled out your sdcard and set it aside? sometimes a bodgy sdcard can get in the way of boot up, though it seems unlikely here.
It doesn't seem that patching the framework, even if it keeps you from booting past the model # screen, should be able to keep the device from at least powering on.
If you connect it to your PC and try holding in power for ~30 seconds, does any USB device or android device activity occur at all, even if a device appears and disappears again?
I did find that I had a "konawifi" device attached to my PC and needed to update its driver to access the device in CWR mode.
roustabout said:
something just occurred to me - you've pulled out your sdcard and set it aside? sometimes a bodgy sdcard can get in the way of boot up, though it seems unlikely here.
It doesn't seem that patching the framework, even if it keeps you from booting past the model # screen, should be able to keep the device from at least powering on.
If you connect it to your PC and try holding in power for ~30 seconds, does any USB device or android device activity occur at all, even if a device appears and disappears again?
I did find that I had a "konawifi" device attached to my PC and needed to update its driver to access the device in CWR mode.
Click to expand...
Click to collapse
I pulled the SD card
This afternoon I will try your tip (connecting it to the PC)
I also will try a jig although I think this is useless
My last resort is back to Samsung. I have 2 choices, repair or make a frisbee out of it. I prefer the first option especially beacause I was rather pleased with the device
I tried making a jig when I bricked my Galaxy Media Player, and it did not work. Samsung repaired it, eventually.
roustabout said:
I tried making a jig when I bricked my Galaxy Media Player, and it did not work. Samsung repaired it, eventually.
Click to expand...
Click to collapse
Just brought it back to shop. Will sent it back to Samsung.
will take 3 weeks. Luckely I have my trusted tab 10.1 to use.
HANSB57 said:
Hi There all,
I bricked my device!
I installed multi window manager and ran the patch.
I should have not done this.
After one last message (something like copy binary from SD card) the device was dead.
Any help is highly appreciated
Click to expand...
Click to collapse
Its totally impossible that patching the FlashBarService.apk could completely brick your device... A Boot loop is possible, but not a brick.
Sent from my GT-N8013 using Tapatalk HD
Flashed the wrong recovery!
Hi there, Ive soft bricked my Note 8.0 by accidentally flashing Note 2 recovery. Anyone know how I can fix this? Stuck in boot screen. I can get to download mode and Odin recognizes it, but I have no idea what to do from there.
Any advice/help would be greatly appreciated..
no problem flash the note 8 recovery with odin
Sorry but I am new to soft brick. Have 3 rooted devices and never brick before. Can put device in download mode as kennielsen but I'm lost after that. Details on what to do and how to do it would be very nice, please!
Sent from my SM-N900V using XDA Premium 4 mobile app
Hi Folks,
I'm helping my sister's boyfriend to recover what's possible from his AT&T Galaxy S III that fell into a pool when they were on vacation.
When I first got the phone, it would not boot or charge the battery - the red notification light would flicker in a noticeable pattern when power was attached and the battery removed.
After I took it apart following these nice instructions, then soaked+scrubbed its circuit boards, contacts, etc. in rubbing alcohol and ensured everything was dry again, I put it all back together and it booted up but will not respond to touch input on the display. The side and bottom buttons still work fine.
When cleaning the phone, I did notice what appears to be damage on pins for the "display data cable" (according the dis-assembly pages), which might be the LCD and Digitizer connection. Is this also related to touchscreen input?
BTW, I tried a couple ways to get into the phone:
It appears that he never enabled USB Debugging, so I can't get ADB or other programs to access phone storage over USB
I have also tried a USB OTG cable and mouse, but his phone is not showing the mouse pointer or responding to its input - it does show recognition that something was connected, because the display will turn on if already off and I simply connect the OTG cable
So, I'm wondering if anyone has advice on how to get the data off this phone and/or enable the touchscreen input.
SOLVED:
Rooted the phone using CF-Autoroot method for AT&T Galaxy S III phones via Odin. Not sure if this was necessary.
Installed stock drivers from "SAMSUNG_USB_Driver_for_Mobile_Phones_v1.5.18.0.exe" package
Placed the phone into Stock Recovery
Used ADB in Windows to copy media files from the phone onto my PC: adb pull /data/media/DCIM C:/backup
Installed PhilZ Recovery via Odin and copied the phone's /data contents to an external SD card, which then enabled access to txt messages, application settings, etc. on my PC with a card reader
Thanks,
- ooofest
Use this guide
http://forum.xda-developers.com/showthread.php?p=43332821
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
mkfryan said:
Use this guide
http://forum.xda-developers.com/showthread.php?p=43332821
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Thanks, it's a good idea but requires root - this is a stock, unrooted phone I'm dealing with.
Currently looking at the idea of finding a phone frame for sale with just LCD and digitizer, and possibly just replacing the circuit boards with those in this phone. That is, I'm assuming its built-in storage is somewhere on the motherboard.
- ooofest
Why not put the phone in download mode Odin cwm recovery reboot into recovery and adb pull what you need?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
mkfryan said:
Why not put the phone in download mode Odin cwm recovery reboot into recovery and adb pull what you need?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Because I was unfamiliar with that method?
Honestly, I was searching everywhere and came up with that exact same process - the phone is now rooted with CWM (via Odin, as you suggested) and for some reason ADB isn't able to see it when I connect in Recovery mode. Hm.
More work to do.
- ooofest
Do you have another android device to test to see if adb is working on the computer? Otherwise maybe the recovery doesn't have adb enabled
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
mkfryan said:
Do you have another android device to test to see if adb is working on the computer? Otherwise maybe the recovery doesn't have adb enabled
Click to expand...
Click to collapse
To that point, I had adb working with its stock recovery and can communicate with my primary Galaxy S III, so it seems that this CWM is not supporting adb.
I installed CWM 5.5.0.4 from CF-SGS3-CWM-v5.5-v1.2.tar via ODIN, essentially. Perhaps another version would work better with adb?
- ooofest
Upgraded to latest CWM for this phone via Odin by creating a .tar from the latest .img file for AT&T Galaxy S IIIs, but it still doesn't allow adb access :/ .
Need to find a custom recovery that offers adb access, because I hope to pull the data via adb as mentioned above.
Any hints?
- ooofest
At that point of the stock recovery working on your other device possibly try to Odin back to stock and try adb again just tossing out a suggestion
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Installed the AT&T stock recovery back via Odin and ADB was not enabled on the phone - although it worked for my purely stock phone - until I installed the absolute latest Samsung USB drivers. Re-rooted just for the heck of it using the CF-Autoroot method and Odin.
Seeing what's available to pull now . . .
EDIT: Whoo Hoo! adb pull /data/media/DCIM C:/backup is copying all the pictures and videos from the phone!
Thanks for all helpful advice - I've been all over the boards, searching for ways into storage and this finally worked. Seems I didn't need a custom recovery, after all.
- ooofest
I managed to install TWRP and when I tried to flash Furnace Kernel for D803, the phone is stuck on the furnace logo doing nothing. I'd like to come back to the original kernel, but can't push file using ADB sideload cause my ADB don't detect the phone. And, download mode is doing nothing. Helpp !
poudigne said:
I managed to install TWRP and when I tried to flash Furnace Kernel for D803, the phone is stuck on the furnace logo doing nothing. I'd like to come back to the original kernel, but can't push file using ADB sideload cause my ADB don't detect the phone. And, download mode is doing nothing. Helpp !
Click to expand...
Click to collapse
Have you tried this ?
http://forum.xda-developers.com/showthread.php?t=2582142
poudigne said:
I managed to install TWRP and when I tried to flash Furnace Kernel for D803, the phone is stuck on the furnace logo doing nothing. I'd like to come back to the original kernel, but can't push file using ADB sideload cause my ADB don't detect the phone. And, download mode is doing nothing. Helpp !
Click to expand...
Click to collapse
This is not the right forum for this fyi. But you should still be able to get right back into recovery just fine using the button press sequence. Turn off the phone with the power button, now press the power + Volume down button till the screen turns on then once it does, immediately release them both then press them both again til a white recover screen appears. Then just tap the power button two times and it will get you back into TWRP. From here you can flash the old Rom again and it should restore the original kernel. Regardless you should be able to take it from here.
RenderBroken said:
This is not the right forum for this fyi. But you should still be able to get right back into recovery just fine using the button press sequence. Turn off the phone with the power button, now press the power + Volume down button till the screen turns on then once it does, immediately release them both then press them both again til a white recover screen appears. Then just tap the power button two times and it will get you back into TWRP. From here you can flash the old Rom again and it should restore the original kernel. Regardless you should be able to take it from here.
Click to expand...
Click to collapse
I was able to go in recovery, but not transfer file.
Anyway, i managed to transfer file into my phone, and tried to flash another kernel, and it just brick the phone. I went to the service company and they gave a me a new Phone (Galaxy S4) for free since i was still on warranty. So thanks for all your help anyway. I hated that phone, so it's good thing it bricked.
poudigne said:
I was able to go in recovery, but not transfer file.
Anyway, i managed to transfer file into my phone, and tried to flash another kernel, and it just brick the phone. I went to the service company and they gave a me a new Phone (Galaxy S4) for free since i was still on warranty. So thanks for all your help anyway. I hated that phone, so it's good thing it bricked.
Click to expand...
Click to collapse
I'm sorry you had a hard time. The S4 is a decent phone yet not as good as the G2. Hope it gives you less of a head ache.
poudigne said:
I was able to go in recovery, but not transfer file.
Anyway, i managed to transfer file into my phone, and tried to flash another kernel, and it just brick the phone. I went to the service company and they gave a me a new Phone (Galaxy S4) for free since i was still on warranty. So thanks for all your help anyway. I hated that phone, so it's good thing it bricked.
Click to expand...
Click to collapse
- You need OTG cable.
- Copy your ROm in flash disq
- Reboot into Recovery.
- Go to Mount.
- Choose Otg storage.
- Flash your ROM.
:good:
Flashing is not without risks but you can lessen the risks by researching and learning before flashing blindly. If things go badly, 99% of the situations can be salvaged if you don't panick and research the fix before giving up. USB OTG is cheap and provides SD Card flexibility and allows you to back up your phone or rom off-site. Newegg has Kingston microDuo 32gb USB 3.0 right now for $16. http://www.newegg.com/Product/Product.aspx?Item=N82E16820239887
You can also buy a USB OTG cable and use any flashdrive with that cable for about $1 on Epay
I'm quite perplexed. I was using my p600 today, and it worked fine like normal. Tonight I took it out to do some reading, and noticed some flickering streaks across the screen. I thought nothing of it, and did a reboot.
It turned off, but never rebooted. The back and menu buttons flashed once, and then went dark.
I've been trying without success to get it to boot for a half hour, nothing. There is no response to plugging it into a charger, and my computer does not recognize it as being plugged in. (Currently have no access to windows, so unsure of ODIN).
I was running Tamasek's unnoficial 18.1 build at the time.
Any ideas. Would greatly appreciate any help, even just to get some notes off if it is indeed dead.
while plugged into charger (to rule out it hasnt died while youve been messing with it) long hold power button... i forget if its 10 seconds or 30 seconds. same sorta thing happened to me on temasek, flicker screen but then it died itself, and i got a response from my tablet by long power button hold. not sure if we had same cause but thats what worked for me
diabl0w said:
while plugged into charger (to rule out it hasnt died while youve been messing with it) long hold power button... i forget if its 10 seconds or 30 seconds. same sorta thing happened to me on temasek, flicker screen but then it died itself, and i got a response from my tablet by long power button hold. not sure if we had same cause but thats what worked for me
Click to expand...
Click to collapse
Doesn't seem to work for me.
Update:
Holding the power button gives no response, no matter the length of press. However, apparently randomly it will turn on, as the back and menu buttons will light up. If this happens I am able to successfully connect to a computer and view files. I was able to connect to ODIN, however since I am unable to get into download mode I am unable to do anything.
If it is in the state where the buttons are lighting up and I then try to boot it it turns off and is completely unresponsive.
Any ideas? Is there a way to remotely boot into download mode?
Cheers
greenmatrix said:
Update:
Holding the power button gives no response, no matter the length of press. However, apparently randomly it will turn on, as the back and menu buttons will light up. If this happens I am able to successfully connect to a computer and view files. I was able to connect to ODIN, however since I am unable to get into download mode I am unable to do anything.
If it is in the state where the buttons are lighting up and I then try to boot it it turns off and is completely unresponsive.
Any ideas? Is there a way to remotely boot into download mode?
Cheers
Click to expand...
Click to collapse
When lights come on, attach to computer and run the command adb devices... if you dont know about adb then there is plenty of info on the net about it. If adb devices gives you a response (which it will if yoi are able to view files on yoir device then that means you will get and adb response as long as you set up the adb program correctly) then run adb reboot download and then youll be in download mode and flash with odin
diabl0w said:
When lights come on, attach to computer and run the command adb devices... if you dont know about adb then there is plenty of info on the net about it. If adb devices gives you a response (which it will if yoi are able to view files on yoir device then that means you will get and adb response as long as you set up the adb program correctly) then run adb reboot download and then youll be in download mode and flash with odin
Click to expand...
Click to collapse
Thanks, I'll let you know how it goes.
diabl0w said:
When lights come on, attach to computer and run the command adb devices... if you dont know about adb then there is plenty of info on the net about it. If adb devices gives you a response (which it will if yoi are able to view files on yoir device then that means you will get and adb response as long as you set up the adb program correctly) then run adb reboot download and then youll be in download mode and flash with odin
Click to expand...
Click to collapse
I am unable to get the p600 to show under adb devices. However, adb does work successfully for my nexus 6 so it appears to be generally working.
This is on mac, so I don't believe it could be a driver issue. I spent a good while trying to get adb working on windows with no success for either device (killed and restarted adb server, tried reinstalling drivers, different cables, etc).
Frustrating, because the p600 will connect fine to the computer, and I can view files and interact with it. Odin also recognizes it.
I appreciate the help, and any further ideas.
if odin recognizes it then why dont you just try to flash stock again?
diabl0w said:
if odin recognizes it then why dont you just try to flash stock again?
Click to expand...
Click to collapse
I've tried, every time it gets hung up on SetupConnection. Running Odin 3.07. Perhaps a different version of Odin?
greenmatrix said:
I've tried, every time it gets hung up on SetupConnection. Running Odin 3.07. Perhaps a different version of Odin?
Click to expand...
Click to collapse
what version did you use last time... hold on ill get you a link to a dif one you should use 3.07 is kinda old
diabl0w said:
what version did you use last time... hold on ill get you a link to a dif one you should use 3.07 is kinda old
Click to expand...
Click to collapse
Thanks, can't remember what I used when I last flashed with odin, I want to say it was around 1.8x.
greenmatrix said:
Thanks, can't remember what I used when I last flashed with odin, I want to say it was around 1.8x.
Click to expand...
Click to collapse
i meant what did you use to flash twrp so that you were able to flash temasek's? ... use 3.10.7
http://forum.xda-developers.com/showthread.php?t=2711451
diabl0w said:
i meant what did you use to flash twrp so that you were able to flash temasek's? ... use 3.10.7
http://forum.xda-developers.com/showthread.php?t=2711451
Click to expand...
Click to collapse
Yeah, when I flashed TWRP a few weeks ago I believe i used odin 1.8x, can't remember. However I know that it wasn't 3.10.7. I'll see how 3.10.7 works.
It appears to still be hanging on SetupConnection.
greenmatrix said:
It appears to still be hanging on SetupConnection.
Click to expand...
Click to collapse
Hmm i guess its not in download mode then... the only thing i could think of is that for some reason it keeps booting to recovery mode which would make both adb and odin not work. Although idk why youd have a blank screen cuz that doesnt tend to happen for recovery. When the menu buttons light up, do they give you haptic feedback (do they vibrate)? If so, maybe you recently dropped it and the ribbon cable for screen beca,e disloged. Id stilll see if you get any responses from ppl who know more than me before you go pulling your tablet apart tho.
The only other thing i could think of to tell you to do is to keep trying to access download mode by holding the appropriate buttons during boot and then try to flash stock with odin. Sorry, i dont know enough to give any more advice from here
diabl0w said:
Hmm i guess its not in download mode then... the only thing i could think of is that for some reason it keeps booting to recovery mode which would make both adb and odin not work. Although idk why youd have a blank screen cuz that doesnt tend to happen for recovery. When the menu buttons light up, do they give you haptic feedback (do they vibrate)? If so, maybe you recently dropped it and the ribbon cable for screen beca,e disloged. Id stilll see if you get any responses from ppl who know more than me before you go pulling your tablet apart tho.
The only other thing i could think of to tell you to do is to keep trying to access download mode by holding the appropriate buttons during boot and then try to flash stock with odin. Sorry, i dont know enough to give any more advice from here
Click to expand...
Click to collapse
ITS ALIVE!!
Thanks man, you may have just solved it, I feel like an idiot. I hadn't considered that the ribbon cable might be loose, and as I was examining it with a bright light I could see items on the screen. Was successfully able to boot into download mode and flash the stock rom, the screen issue was not solved, but I think it flashed alright.
When I have some time I'm going to take off the back and check out the ribbon cable.
greenmatrix said:
ITS ALIVE!!
Thanks man, you may have just solved it, I feel like an idiot. I hadn't considered that the ribbon cable might be loose, and as I was examining it with a bright light I could see items on the screen. Was successfully able to boot into download mode and flash the stock rom, the screen issue was not solved, but I think it flashed alright.
When I have some time I'm going to take off the back and check out the ribbon cable.
Click to expand...
Click to collapse
im glad you were able to figure it out
greenmatrix said:
ITS ALIVE!!
Thanks man, you may have just solved it, I feel like an idiot. I hadn't considered that the ribbon cable might be loose, and as I was examining it with a bright light I could see items on the screen. Was successfully able to boot into download mode and flash the stock rom, the screen issue was not solved, but I think it flashed alright.
When I have some time I'm going to take off the back and check out the ribbon cable.
Click to expand...
Click to collapse
The ribbon cable coming loose is a very common issue on this tablet (even without dropping it) as it's connected rather poorly. Fortunately it's also relatively easy to fix as per the below:
Fixing Note 10.1 2014 ribbon cable
Especially the screen flickering when it "died" sounds familiar.
epithetic said:
The ribbon cable coming loose is a very common issue on this tablet (even without dropping it) as it's connected rather poorly. Fortunately it's also relatively easy to fix as per the below:
Fixing Note 10.1 2014 ribbon cable
Especially the screen flickering when it "died" sounds familiar.
Click to expand...
Click to collapse
This was exactly it. 15 minute fix and everything was golden.