Related
Before I begin, this is my first post here. I've used XDA before for help and love you guys. Now I need you more than ever. Thanks in advance for the help!
At first, my phone started to act all weird. By that I mean the Espier launcher wouldn't even load. It kept crashing. So I decided to unroot my phone. I used Odin to attempt to put the factory firmware and stuff on my phone but ended up prematurely ending the install, thus bricking my phone. When I turn my phone on I see the "Firmware upgrade encountered an issue" screen. So I did some research and attempted to fix the problem myself. After downloading and installing Kies (on three computers) I attempted to connect my phone to Kies. The USB port works, but none of my computers sees my phone. I've tried different USB ports, reinstalling Kies, using the connection debugging tool within Kies, changed the USB cable, taking the battery out, everything. If I am able to connect my phone to my computer I'll be able to fix the problem. If anyone could help me, that'd be lovely.
Can you get to download mode?
Sent from my SAMSUNG-SGH-T989 using xda premium
The only USB cable I've been able to use Odin or Kies with is the original cable that came with the phone. I have a ton of other micro USB cables, they all will charge but nothing else will do any sort of data transfer. Even then, I sometimes have to change USB ports and have encountered two PCs with won't recognize the phone no matter what. Keep trying.
It's odd, because my old HTC Hero was happy to connect and charge with any cable that fit.
rdsnyder said:
The only USB cable I've been able to use Odin or Kies with is the original cable that came with the phone. I have a ton of other micro USB cables, they all will charge but nothing else will do any sort of data transfer. Even then, I sometimes have to change USB ports and have encountered two PCs with won't recognize the phone no matter what. Keep trying.
It's odd, because my old HTC Hero was happy to connect and charge with any cable that fit.
Click to expand...
Click to collapse
Maxed22a said:
Can you get to download mode?
Sent from my SAMSUNG-SGH-T989 using xda premium
Click to expand...
Click to collapse
Yeah, I'm able to get into download mode. And I've also used the original cable that has provided with the phone.
Id try to odin the stock rooted kernel with what you have. I assume you still have a copy of what you rooted with... if not
http://forum.xda-developers.com/showthread.php?t=1433101
There you go.
Sent from my SPH-D710 using XDA
drinxtir said:
Id try to odin the stock rooted kernel with what you have. I assume you still have a copy of what you rooted with... if not
http://forum.xda-developers.com/showthread.php?t=1433101
There you go.
Sent from my SPH-D710 using XDA
Click to expand...
Click to collapse
The problem is none of my computers will detect my phone when I plug in the USB. I can't do anything else unless I can plug in my phone. I've tried installing the drivers, everything. Nothing works.
Ayotom said:
The problem is none of my computers will detect my phone when I plug in the USB. I can't do anything else unless I can plug in my phone. I've tried installing the drivers, everything. Nothing works.
Click to expand...
Click to collapse
Try a brand new high quality USB cable. Once in download mode try the new cable and Odin back to stock - sfhubs one-clicks are the life saver here.
Also. Have you tried 'stock' recovery/factory reset? This may get you to a good place. Then you can install a good stock ROM with root and recovery (again check out sfhub's posts)
Factory reset via stock recovery:
Hold down the Volume Up and Power buttons simultaneously.
Continue holding the Volume Up and Power buttons until the Samsung Galaxy S II logo screen is displayed.
When the Galaxy S II logo screen is displayed, release the Power button but continue holding the Volume Up button until the Android System Recovery menu is displayed.
Once you are on the Android System Recovery menu, select the wipe data/factory reset option. Moving the selection up and down is done with the Volume Up and Volume Down buttons. Once you have the wipe data/factory reset option highlighted, you select it by touching the Home button.
Once you have chosen the factory reset option, you will see a confirmation screen. Highlight the Yes — delete all user data option and touch the Home button to select it.
The procees of wiping the phone should only take a few seconds and when it is finished, you will be returned to the Android System Recovery menu.
Highlight and select the reboot system now option.
I sound like a broken record on the USB cable thing in many of my posts but that has been a cause for so much frustration for me and countless others. And the stock cable from Sammy sucks ass too.
Good luck.
leaderbuilder said:
Try a brand new high quality USB cable. Once in download mode try the new cable and Odin back to stock - sfhubs one-clicks are the life saver here.
Also. Have you tried 'stock' recovery/factory reset? This may get you to a good place. Then you can install a good stock ROM with root and recovery (again check out sfhub's posts)
Factory reset via stock recovery:
Hold down the Volume Up and Power buttons simultaneously.
Continue holding the Volume Up and Power buttons until the Samsung Galaxy S II logo screen is displayed.
When the Galaxy S II logo screen is displayed, release the Power button but continue holding the Volume Up button until the Android System Recovery menu is displayed.
Once you are on the Android System Recovery menu, select the wipe data/factory reset option. Moving the selection up and down is done with the Volume Up and Volume Down buttons. Once you have the wipe data/factory reset option highlighted, you select it by touching the Home button.
Once you have chosen the factory reset option, you will see a confirmation screen. Highlight the Yes — delete all user data option and touch the Home button to select it.
The procees of wiping the phone should only take a few seconds and when it is finished, you will be returned to the Android System Recovery menu.
Highlight and select the reboot system now option.
I sound like a broken record on the USB cable thing in many of my posts but that has been a cause for so much frustration for me and countless others. And the stock cable from Sammy sucks ass too.
Good luck.
Click to expand...
Click to collapse
All the help is appreciated, I just wanted to let you know that. If my tone is bitter, I apologize. I use this phone for emergencies. I have indeed tried a high quality USB cable (just bought it) and it will not connect. I attempted to use Odin to restore my phone back to normal but the process was interrupted and caused my phone to be in the phone....!....computer screen with the message "firmware upgrade has encountered a problem" etc. I have attempted to plug in my phone while Odin opened. Nada. I've tried this in download mode using the button commands you have listed. I hope I'm not getting too annoying, I just feel so lost without my phone. Had everything on it. Sorry.
Ayotom said:
All the help is appreciated, I just wanted to let you know that. If my tone is bitter, I apologize. I use this phone for emergencies. I have indeed tried a high quality USB cable (just bought it) and it will not connect. I attempted to use Odin to restore my phone back to normal but the process was interrupted and caused my phone to be in the phone....!....computer screen with the message "firmware upgrade has encountered a problem" etc. I have attempted to plug in my phone while Odin opened. Nada. I've tried this in download mode using the button commands you have listed. I hope I'm not getting too annoying, I just feel so lost without my phone. Had everything on it. Sorry.
Click to expand...
Click to collapse
Are you sure you were installing the right firmware? If you flashed an international verion then you did kill the device and will need to get it jtag'd or replaced.
And exactly how did it 'get interupted? Did it just 'stop' or was it interupted by a power outage, or impatience of quiting the appolication?
How did you get root? Did you use sfhub's autoroot?
And what ROM did you use? Again sfhub's Stock One-Clicks are the safest and only way to go in my book.
Not trying to be a **** just trying to get a better understanding of what happened.
leaderbuilder said:
Are you sure you were installing the right firmware? If you flashed an international verion then you did kill the device and will need to get it jtag'd or replaced.
And exactly how did it 'get interupted? Did it just 'stop' or was it interupted by a power outage, or impatience of quiting the appolication?
How did you get root? Did you use sfhub's autoroot?
And what ROM did you use? Again sfhub's Stock One-Clicks are the safest and only way to go in my book.
Not trying to be a **** just trying to get a better understanding of what happened.
Click to expand...
Click to collapse
I might have accidentally installed the wrong firmware while attempting to repair it. Unless the different SII model firmware wouldn't hurt my phone, such as the AT&T SII.
And battery laptop died.
I had my brother root it. It used Syndicate.
And no worries dude, I'm just glad you're helping!
I am not sure if anyone specifically tried the att gs2 firmware, but since att is gsm, chances are it is the same as flashing the intl gs2 firmware. Flashing the latter would basically disable your usb port. It does sound like that is what happened.
If you still had cwm or root you could flash from the phone, but i think you mentioned you lost those too.
Your remaining options are probably jtag or return to sprint.
Thank you very much for your help. It seriously means a lot. Next time I'll pay more attention so I won't end up screwing things up again.
Well if you tried to use the AT&T SG II (SGH-I777) firmware you did probably kill it for sure. These phones are very specific and individual when it comes to the actual hardware and base firmwares. Kind of like putting diesel into a gas engine - good things don't happen. If you can't get it recognized at all no matter what you do a jtag service or simply taking it back and playing dumb might help. Here is a post with almost the same issue, just a different but still wrong firmware: http://forum.xda-developers.com/showthread.php?t=1506630 As for the guys at ACS they are very good too (most of them are around here too by the way). Spend some time and read a whole lot and you will learn what you need. Best bet if you simply can't get it recognized by Odin is to take it back to Sprint and play dumb and see if they get you a replacement. With insurance you should get it free without I think you pay $35.
This might sound a little crazy... But have you tried heimdall to see if you get dirrerent results?
Update
So I decided to check out the JTAG service. Guess what I found out? The dude that repairs phones lives 20 minutes away from me! I went over to his place yesterday and he fixed my phone right in front of me. It was totally worth the $50! His service is amazing, and he's friendly also. I would highly recommend him! Read my review (I'm John Montoya): http://mobiletechvideos.mybigcommerce.com/samsung-epic-4g-touch-jtag-brick-repair/
Thanks everyone for the help. Next time I'll be sure not to put in the wrong firmware!
LOL that's pretty funny having the mobiletechvideos guy living in your town, and getting to watch the JTAG repair in person. Not many people can say they've seen that in person, myself included. Glad you got it resolved.
Sent from my SPH-D710 using Tapatalk 2
Ayotom said:
So I decided to check out the JTAG service. Guess what I found out? The dude that repairs phones lives 20 minutes away from me! I went over to his place yesterday and he fixed my phone right in front of me. It was totally worth the $50! His service is amazing, and he's friendly also. I would highly recommend him! Read my review (I'm John Montoya): http://mobiletechvideos.mybigcommerce.com/samsung-epic-4g-touch-jtag-brick-repair/
Thanks everyone for the help. Next time I'll be sure not to put in the wrong firmware!
Click to expand...
Click to collapse
Glad to see you got it resolved! I've recommended that service to a few. Thanks for posting. Many don't so we never know the final outcome. This helps the whole community. Enjoy your great phone.
I downloaded the Jedi Mind Trick JB 2 ROM and installed it via clocwork mod recovery .. That went fine but it took me a few days to realize I didnt have a working video camera anymore on my phone.. so I thought to flash a stock ROOTed rom instead...
Then I found this threat about an updated version of Jedi Mind Trick's ROM labled JB 3.. So I wiped as much as I could in recovery and chose to format all the options it gave me in recover , Format system , data , cache , emms(or something) .. and now when I boot the phone , it shows the first flash screen , and the samsung logo starts to shimmer then it reboots back to the splash screen and repeats this process everal times before just going black and sitting there..
So I've successfully bootlooped my phone doing this..
MY PROBLEM -- I don't know how to charge my phone or connect to it to install anything else..
Is this a serious problem? How can I charge my phone to continue troubleshooting it? It still has some battery to try some things but I don't know how to hook it up to transfer any other roms to it via USB cable and PC in it's current state..
I'm very computer savvy but I'm trying to learn this phone modding stuff and I realy hope I didn't brick my phone in this process.
Can someone please help me out here? I'll be on the forums religiously until I figure this out.
What should I start doing first??
Any help would be greatly appreciated!! Thanks!
still working at it
I think I'm at the point of having to use ODIN to flash a new rom since i cannot simply copy this rom to the sdcard to use clockwork to flash it .. Am I correct on this ?
For some reason this rom I found (should be stock rooted tmobile gSII rom) does not want to open from ODIN's PDA button cause its in .zip and not .tar or anything... I'm not sure how to flash this rom with ODIN ( I'm not even 100% sure this is how its supposed to go) Any suggestions ?
phew
UPDATE - So I managed to research enough to find out that there is no way to flash a CUSTOM rom with ODIN.. SO I had to download a stock (presumably rooted) t-mobile rom and flash THAT ...
Now I'm back up with a rooted rom and will begin re-installing clockwork and then my custom deodexed rooted rom afterward.
Thanks for all who almost kinda tried to care to reply in this past 2 hours =) -- As previously mentioned.. I am a nerd.. I just suck at phone modding. Haha
So , looks like I'm in the clear now and don't need any more support on this particular topic yet.
zarklon said:
UPDATE - So I managed to research enough to find out that there is no way to flash a CUSTOM rom with ODIN.. SO I had to download a stock (presumably rooted) t-mobile rom and flash THAT ...
Now I'm back up with a rooted rom and will begin re-installing clockwork and then my custom deodexed rooted rom afterward.
Thanks for all who almost kinda tried to care to reply in this past 2 hours =) -- As previously mentioned.. I am a nerd.. I just suck at phone modding. Haha
So , looks like I'm in the clear now and don't need any more support on this particular topic yet.
Click to expand...
Click to collapse
Is this true? Through a recommendation (haven't done anything to my phone from rooting/flashing KANGSJUGGERNAUT2 years ago), I tried to flash CM10 and ended up with a bootloop myself. Tried flashing through ODIN but it kept crashing; does anyone know why?
Afterward, I tried to reflash it through CWM and from then on bootloops into a installation process that never completes.
For some reason my CWM turned super slow, freezes/hangs and reboots after a few minutes.
I gave the phone to a friend who does this stuff on the regular but he said my initial flash wasn't complete cause in download mode says I'm still running official? No clue.
I was told this via email/chat: "No luck, it won't even boot anymore, I think I'll just bring it back tmrw morn
10:43 PM
Sorry I'm at a wedding (yea I know random) I left my phone with coat check
OK I've narrowed down the reason but not the solution, you had an AOKP based ROM which fundamentally is based on CyanogenMod, but it wasn't correctly flashed as the phone still thought it has factory ROMs still running
11:10 PM
Clockworkmod(even though it was working before) wasn't accessing the partitions of the phone correctly so it wasn't properly wiping or flashing properly.
11:12 PM
So basically from the first time you flashed cwm it didn't flash properly then the next time you flashed using the new recovery it didn't flash anything it was supposed to do itself properly , so basically it was a chain of events in addition to a bad boot loader, that's why it never went to recovery or download mode correctly
11:13 PM
That's something that had to do with the way the phone was built meaning you may of had a bad bootloader from the very begin and are now feeling the synptoms
Basically, and I would hate to be the reason or partially the reason you have a dead phone, basically it was a matter of coincedencr that it happened as this could of happened at anytime, once you have a bad boot loader its pretty much down hill from there"
Any helpful insight as how I can rectify this? is my phone truly dead? Sorry about the quoted format, it was copied and pasted.
If I were in your boat, I'd use Odin and flash the stock 4.1.2 ROM.
Sent from my Nexus 7 using Tapatalk 4 Beta
tronmech said:
If I were in your boat, I'd use Odin and flash the stock 4.1.2 ROM.
Sent from my Nexus 7 using Tapatalk 4 Beta
Click to expand...
Click to collapse
The phone won't turn on, unable to go into recovery and download mode; plugged in usb (hear connection beep but pressing power button plays disconnect button) to no avail. What can I do to unbrick?
Stock 4.1.2? Possible over a hardbricked T989 with old 2.3.6?
JahJahLoO said:
The phone won't turn on, unable to go into recovery and download mode; plugged in usb (hear connection beep but pressing power button plays disconnect button) to no avail. What can I do to unbrick?
Stock 4.1.2? Possible over a hardbricked T989 with old 2.3.6?
Click to expand...
Click to collapse
sorry but i have to assume that you are not doing the 3 button recovery or download mode right.
Pull battery, put battery back in, hold power button & Vol +/- untill you see SAMSUNG on the screen ---> let go off power button(keep holding
Vol +/- button) .....u will see recovery. (assuming you did flash cwm before).
Let me know.
hit thanks.
sam.balia1012 said:
sorry but i have to assume that you are not doing the 3 button recovery or download mode right.
Pull battery, put battery back in, hold power button & Vol +/- untill you see SAMSUNG on the screen ---> let go off power button(keep holding
Vol +/- button) .....u will see recovery. (assuming you did flash cwm before).
Let me know.
hit thanks.
Click to expand...
Click to collapse
I believe I am doing it correct, I have been entering recovery and download mode many times, right before I soft bricked it.
And sorry, no, I've tried many times, many methods and my phone is confirmed as entirely hard bricked.
SUPAR SAD, but thank you!
dont give up
JahJahLoO said:
I believe I am doing it correct, I have been entering recovery and download mode many times, right before I soft bricked it.
And sorry, no, I've tried many times, many methods and my phone is confirmed as entirely hard bricked.
SUPAR SAD, but thank you!
Click to expand...
Click to collapse
you can try using adb and put the phone in dl mode.
sometimes its as easy as pull battery and wait awhile (20 min or more) and try again.
if you've exhausted all possibilities, you can use a jig to force a dl mode.
let me know
sam.balia1012 said:
you can try using adb and put the phone in dl mode.
sometimes its as easy as pull battery and wait awhile (20 min or more) and try again.
if you've exhausted all possibilities, you can use a jig to force a dl mode.
let me know
Click to expand...
Click to collapse
I don't know what adb is, or how to use it; I have, however seen my friend RDP to my desktop and do something and used the term 'adb' in his attempt to code through the phone.
I've done that battery waiting period, for nearly an hour and still no result.
After doing some researching, I have found that many people have stated a USB JIG would not be applicable to a 'hard bricked' phone. I really wanted to try as it looked like the most, simple and inexpensive solution.
JahJahLoO said:
I don't know what adb is, or how to use it; I have, however seen my friend RDP to my desktop and do something and used the term 'adb' in his attempt to code through the phone.
I've done that battery waiting period, for nearly an hour and still no result.
After doing some researching, I have found that many people have stated a USB JIG would not be applicable to a 'hard bricked' phone. I really wanted to try as it looked like the most, simple and inexpensive solution.
Click to expand...
Click to collapse
If you know for a fact that you bricked your s2, maybe wrong rom or kernel that u flashed by accident then.....
contact these guys.... http://brickedmyphone.com/contact-me/
good like and click thanks if you agree.
sam.balia1012 said:
If you know for a fact that you bricked your s2, maybe wrong rom or kernel that u flashed by accident then.....
contact these guys.... http://brickedmyphone.com/contact-me/
good like and click thanks if you agree.
Click to expand...
Click to collapse
Lols, you're really fishing for them "Thanks"; you got it buddy. Very swift responses. :cyclops:
Anyway, I'm still searching the net for anymore possible solutions.
Thanks.
JahJahLoO said:
Lols, you're really fishing for them "Thanks"; you got it buddy. Very swift responses. :cyclops:
Anyway, I'm still searching the net for anymore possible solutions.
Thanks.
Click to expand...
Click to collapse
fishing for them ???????
what the hell does that even mean? it seems that brick did hit u in the head!!!
sam.balia1012 said:
fishing for them ???????
what the hell does that even mean? it seems that brick did hit u in the head!!!
Click to expand...
Click to collapse
It might as well have... :crying:
hello, i followed the tutorial from this site to increase my memory on my ace 2 x, and now it bootloops and i cant get it to go into recovery or download mode... it either just turns on for a sec and reboots, or if i hold vol up it loads the "samsung gt-s7560m" screen for a sec, and thats about it... could someone please help, thanks
slickwidnick said:
hello, i followed the tutorial from this site to increase my memory on my ace 2 x, and now it bootloops and i cant get it to go into recovery or download mode... it either just turns on for a sec and reboots, or if i hold vol up it loads the "samsung gt-s7560m" screen for a sec, and thats about it... could someone please help, thanks
Click to expand...
Click to collapse
swapping kills memory card brother
also try to flash stock rom through odin
also try flashing stock rom without any sd card in slot
if you are not able to do so then i think your ace 2 is bricked
slickwidnick said:
hello, i followed the tutorial from this site to increase my memory on my ace 2 x, and now it bootloops and i cant get it to go into recovery or download mode... it either just turns on for a sec and reboots, or if i hold vol up it loads the "samsung gt-s7560m" screen for a sec, and thats about it... could someone please help, thanks
Click to expand...
Click to collapse
Hm, you can use download mode as long as the SBL is booting (as you can see by the boot logo)...
Maybe try factory mode (usb jig)?
Ryccardo said:
Hm, you can use download mode as long as the SBL is booting (as you can see by the boot logo)...
Maybe try factory mode (usb jig)?
Click to expand...
Click to collapse
Yeah, I've ordered a USB jig, so I'll try that when it comes if I don't find a solution before..
I can't get it to boot into download mode or recovery, so I don't know how I'd be able to flash with Odin..
I have been able to get odin to recognize it once in a while by messing around with different 3 button combinations, but when I press start on Odin, it just sits at "setup connection"
slickwidnick said:
Yeah, I've ordered a USB jig, so I'll try that when it comes if I don't find a solution before..
I can't get it to boot into download mode or recovery, so I don't know how I'd be able to flash with Odin..
I have been able to get odin to recognize it once in a while by messing around with different 3 button combinations, but when I press start on Odin, it just sits at "setup connection"
Click to expand...
Click to collapse
i am still waiting on these usb jigs to show up in the mail... frustruating...
the jig
slickwidnick said:
i am still waiting on these usb jigs to show up in the mail... frustruating...
Click to expand...
Click to collapse
okay, so i finally got the usb jigs in the mail, and so i put a battery in the phone, plug in the jig, and all it does is light up the screen for a few seconds then shuts off and repeats endlessly. but i noticed that if i plug the jig in for a quick second, i see the samsung screen where it says the model number but then it shuts off. now if i press power agian without removing the battery, the samsung screen with the model number comes up again, but the phone still shuts off after a couple of seconds... i dont know what to make of it...
Hard bricked, send back to Samsung and play dumb or see if one of those "we unlock all phones - international sim cards - cheap accessories" places can reflash it with JTAG
Ryccardo said:
Hard bricked, send back to Samsung and play dumb or see if one of those "we unlock all phones - international sim cards - cheap accessories" places can reflash it with JTAG
Click to expand...
Click to collapse
Okay, thanks a lot, I appreciate the help. Any idea how much one of those jtag systems cost, and which system I would need to get? I mess around with phones all the time and if it's not too expensive, it'd be handy to have around in case of future hard bricks...
slickwidnick said:
Okay, thanks a lot, I appreciate the help. Any idea how much one of those jtag systems cost, and which system I would need to get? I mess around with phones all the time and if it's not too expensive, it'd be handy to have around in case of future hard bricks...
Click to expand...
Click to collapse
I've quicky googled them a month ago and they appear to be about 70 € IIRC, and if you're serious about them remember that having a complete dump of the exact phone you have will make it 100% unbrickable
Ryccardo said:
I've quicky googled them a month ago and they appear to be about 70 € IIRC, and if you're serious about them remember that having a complete dump of the exact phone you have will make it 100% unbrickable
Click to expand...
Click to collapse
By unbrickable you mean that I'll always be able to reflash it and revive it? Or that it won't be able to be bricked again? And I noticed many different jtag systems on eBay, which one would you suggest that I get?
slickwidnick said:
By unbrickable you mean that I'll always be able to reflash it and revive it? Or that it won't be able to be bricked again? And I noticed many different jtag systems on eBay, which one would you suggest that I get?
Click to expand...
Click to collapse
Oh, the first
Basically, since you can read and write all the flash through it, just create a full dump when it's working and restore it when you hardbrick or... uh, get no display in recovery and want to fix it quickly :laugh: (for anything else flashing with Odin is probably quicker)
From what I've read RIFFBox is one of the most popular ones https://www.youtube.com/watch?v=5TTjZgQYRfw, it's probably a little overpriced for what it is but it's aimed at the "professional" market of those independent service shops...
I have a Hard bricked Samsung Galaxy Note 4 Sprint sm-n910p all stock carrying the Qualcomm 805 Snapdragon processor. Like a week after it updated OTA to the Lollipop 5.1.1 it just died in my hands one day after i rebooted it because it kept freezing up. It's a relatively new phone, i had it for about 9 months. I can't get it to boot in download mode nor recovery mode. I tried a USB Jig to get it into download mode but it did not help. Odin does not recognize it, my computer only recognizes it as QHSUSB_BULK 9008. I have another Note 4 same model and carrier as mine running the same Lolipop 5.1.1. I swapped the battery and it still did not boot. I was wondering if anyone on here happens to have a debrick image file for this model that they can assist me with. I have researched on here but so far i have only encountered debrick files and debrick methods for most other models except for the sm-n910p model. I have also tried using my other note 4 to create a debrick file but i was unsuccessful with the create debrick program i tried to run on the second note 4. No one seems to be able to JTAG the note 4 well at least not just yet. The second note 4 i have is not rooted nor do i have any custom roms or custom recovery installed on it, i don't really want to void my warranty or have that second phone bricked as well. Is there anyone on here who may have a debrick image for this model or is there a way i can create a working debrick file from my working note 4 so i can write it to an SDcard to revive my dead note 4? Any assistance given would be greatly appreciated!
I am having the same issue http://forum.xda-developers.com/note-4-sprint/help/note-4-boot-t3423362 My device will not boot into any mode and my computer does not recognize the device the only thing it does(my computer) is play the sound notification when a device is plugged in and taken out. Does anyone have suggestions on how to solve this problem?
http://forum.xda-developers.com/note-4-sprint/help/sprint-note-4-n910p-boot-failure-t3431069 might help.
ME too !!!!!
BrightSoundz said:
I am having the same issue http://forum.xda-developers.com/note-4-sprint/help/note-4-boot-t3423362 My device will not boot into any mode and my computer does not recognize the device the only thing it does(my computer) is play the sound notification when a device is plugged in and taken out. Does anyone have suggestions on how to solve this problem?
Click to expand...
Click to collapse
ME too bro , exactly like you , i don't know what to do
Will the debrick img work for it ? i downloaded it already.
---------- Post added at 11:26 PM ---------- Previous post was at 11:19 PM ----------
i think this thread may help you
---------- Post added at 11:38 PM ---------- Previous post was at 11:26 PM ----------
BrightSoundz said:
I am having the same issue http://forum.xda-developers.com/note-4-sprint/help/note-4-boot-t3423362 My device will not boot into any mode and my computer does not recognize the device the only thing it does(my computer) is play the sound notification when a device is plugged in and taken out. Does anyone have suggestions on how to solve this problem?
Click to expand...
Click to collapse
does it show on your pc device manager under disk drives this : (QHUSB 9008 mode) ???
---------- Post added at 11:48 PM ---------- Previous post was at 11:38 PM ----------
BrightSoundz said:
I am having the same issue http://forum.xda-developers.com/note-4-sprint/help/note-4-boot-t3423362 My device will not boot into any mode and my computer does not recognize the device the only thing it does(my computer) is play the sound notification when a device is plugged in and taken out. Does anyone have suggestions on how to solve this problem?
Click to expand...
Click to collapse
does it show on your pc device manager under disk drives this : (QHUSB 9008 mode) ???
Try going here
Hey i updated my note 4 spirit version using wi fi and then installed it but after the installation the phone never rebooted. And now aftr removing the battery for sometime and pressing power button for a min i.e soft bricking it. It starts but again goes to the same installation thing and the same thing happens.What should i do can ny1 suggest ? Thank you
vihitshah said:
Hey i updated my note 4 spirit version using wi fi and then installed it but after the installation the phone never rebooted. And now aftr removing the battery for sometime and pressing power button for a min i.e soft bricking it. It starts but again goes to the same installation thing and the same thing happens.What should i do can ny1 suggest ? Thank you
Click to expand...
Click to collapse
Not sure what installation screen you're seeing but hopefully it's either booting to system and going through the update prompts or booting to download or recovery modes(?)
Since you're trying to update over the air (OTA), can I properly guess you're not rooted? If you're unsure why it rebooted during the update, ask yourself, did it go back to recovery or did it try to boot as usual?
Without specifics of error, I'm not sure if your phone boots to system OS or not? It's possible the update file was corrupt or rejected for some reason. Reasons that should be included in your request for help.
But there is a simple solution for OTA not cooperating. Rather than trying to remedy that, you could try to update with Smart Switch or KIES or even Odin.
If it's more serious than that, you could include actual screen shots or message(s) you see on phone and PC if using one of the programs above to flash update.
If the phone doesn't boot, you can try this with KIES emergency recovery:
https://forum.xda-developers.com/showpost.php?p=40966346&postcount=1
If that doesn't work, you'll need to learn Odin. But you need to be able to boot to download mode. You can find what you need to get started with here:
https://forum.xda-developers.com/showpost.php?p=63868221&postcount=1
Sent from my SM-N920P using Tapatalk
samep said:
Not sure what installation screen you're seeing but hopefully it's either booting to system and going through the update prompts or booting to download or recovery modes(?)
Since you're trying to update over the air (OTA), can I properly guess you're not rooted? If you're unsure why it rebooted during the update, ask yourself, did it go back to recovery or did it try to boot as usual?
Without specifics of error, I'm not sure if your phone boots to system OS or not? It's possible the update file was corrupt or rejected for some reason. Reasons that should be included in your request for help.
But there is a simple solution for OTA not cooperating. Rather than trying to remedy that, you could try to update with Smart Switch or KIES or even Odin.
If it's more serious than that, you could include actual screen shots or message(s) you see on phone and PC if using one of the programs above to flash update.
If the phone doesn't boot, you can try this with KIES emergency recovery:
https://forum.xda-developers.com/showpost.php?p=40966346&postcount=1
If that doesn't work, you'll need to learn Odin. But you need to be able to boot to download mode. You can find what you need to get started with here:
https://forum.xda-developers.com/showpost.php?p=63868221&postcount=1
Click to expand...
Click to collapse
No the device isnt rooted. It shows that screen in which its written loading recovery or something in blue on top left corner and then it automatically starts installing he update and then it doesn't start at all. It just acts likr a dead phone. Well the phone doesnt respond to any keys now i guess its just dead.
I have attatched a pic showin the error which was displayed earlier mayb it cn help
vihitshah said:
No the device isnt rooted. It shows that screen in which its written loading recovery or something in blue on top left corner and then it automatically starts installing he update and then it doesn't start at all. It just acts likr a dead phone. Well the phone doesnt respond to any keys now i guess its just dead.
I have attatched a pic showin the error which was displayed earlier mayb it cn help
Click to expand...
Click to collapse
mmc_read error is troubling but I'm not sure if the problem is corrupt download or failure to read properly, TBH. I haven't seen that issue in person and from what you describe, I've never heard of the phone continually try to load the same update? But I'm not thinking it's dead just yet.
What condition is your battery? Over 12 months old? Fully charged or at least 80%? Your battery could be a contributing factor here.
Can you get to recovery by pulling battery, discharging power circuit by holding power button down for a minute, reinstalling battery and holding power + vol-up + home together until it vibrates? Try deleting the cache partitions first and try to reboot. If not try factory reset next and try to reboot.
You'll have to decide if you want to wipe data or not but if you get that far, you may consider just flashing with one of the programs I mentioned earlier.
If you want to skip that, I think you can boot into download manually without it trying to flash that update. If it boots to download mode (hold power + vol-down + home until it boots) and waits for you to install something with prompt to press volume up if proceeding to flash, then Smart Switch, KIES or Odin are alternatives to try. Since you're not rooted, you could try the first two and save Odin for last if you prefer less interaction. I'm not sure but maybe Odin is the only alternative unless the other 2 can recognize phone in those states (recovery or download).
The troubling part is that it could be your internal memory failing (eMMC). If that's the issue, you may not succeed in recovering it but possibly temporarily restoring function. I think it may too early to say component failure. Best to try the least invasive, least risky things to give a fair chance of recovery before everything at it.
Give that a try, deciding what steps are applicable. Ask if you have additional questions. I'll need to know what works, what didn't, and what you tried so taking notes is best.
Edit: If you do decide to go with Odin, make sure your PC's task manager doesn't show any open sessions of KIES or Smart Switch, install the Samsung driver from Samsung support for Note 4 and unless you have Windows 10, launch Odin as administrator only.
Sent from my SM-N920P using Tapatalk
samep said:
mmc_read error is troubling but I'm not sure if the problem is corrupt download or failure to read properly, TBH. I haven't seen that issue in person and from what you describe, I've never heard of the phone continually try to load the same update? But I'm not thinking it's dead just yet.
What condition is your battery? Over 12 months old? Fully charged or at least 80%? Your battery could be a contributing factor here.
Can you get to recovery by pulling battery, discharging power circuit by holding power button down for a minute, reinstalling battery and holding power + vol-up + home together until it vibrates? Try deleting the cache partitions first and try to reboot. If not try factory reset next and try to reboot.
You'll have to decide if you want to wipe data or not but if you get that far, you may consider just flashing with one of the programs I mentioned earlier.
If you want to skip that, I think you can boot into download manually without it trying to flash that update. If it boots to download mode (hold power + vol-down + home until it boots) and waits for you to install something with prompt to press volume up if proceeding to flash, then Smart Switch, KIES or Odin are alternatives to try. Since you're not rooted, you could try the first two and save Odin for last if you prefer less interaction. I'm not sure but maybe Odin is the only alternative unless the other 2 can recognize phone in those states (recovery or download).
The troubling part is that it could be your internal memory failing (eMMC). If that's the issue, you may not succeed in recovering it but possibly temporarily restoring function. I think it may too early to say component failure. Best to try the least invasive, least risky things to give a fair chance of recovery before everything at it.
Give that a try, deciding what steps are applicable. Ask if you have additional questions. I'll need to know what works, what didn't, and what you tried so taking notes is best.
Edit: If you do decide to go with Odin, make sure your PC's task manager doesn't show any open sessions of KIES or Smart Switch, install the Samsung driver from Samsung support for Note 4 and unless you have Windows 10, launch Odin as administrator only.
Click to expand...
Click to collapse
Yes until yest i was able to get to recovery by draining the starting circuit by removing battery and pushing power button bt idk nw i m nt able to. Battery is like 1.5 yr old mayb. I hd charged it to 100%
vihitshah said:
Yes until yest i was able to get to recovery by draining the starting circuit by removing battery and pushing power button bt idk nw i m nt able to. Battery is like 1.5 yr old mayb. I hd charged it to 100%
Click to expand...
Click to collapse
I'd advise replacing that battery before trying to recover the phone.
If you were having to pull battery to get to recovery before, I would not have attempted to update with an old and defective battery. It seems that is a symptom of either bad battery or failing eMMC.
I can't say if your eMMC is defective or even if the battery could have contributed to its potential demise.
Hopefully with a new battery fully charged, it flashes and doesn't exhibit such behavior again. Do you have the original USB cable fully functional? If not, consider original replacement for it as well while you're finding replacement battery. As for battery, I'm not sure of a good replacement but others here recommend original or Anker. I wish you success.
I'm interested to hear of your outcome so hopefully the OP doesn't mind the updates; the original failure posted isn't quite the same as yours.
Sent from my SM-N920P using Tapatalk
The battery wasnt working properly earlier and so while updating it mst hv stopped. Inalready replaced it with new original battery
---------- Post added at 06:28 AM ---------- Previous post was at 06:24 AM ----------
hello i have samsung galaxy note 4 version SM-N910P Whenever i turn on the phone it automatically boots into recovery mode and starts installing system update and then after 100 % it switches off and never turns on back. Please Suggest me some remedy. Thank you
---------- Post added at 06:30 AM ---------- Previous post was at 06:28 AM ----------
samep said:
I'd advise replacing that battery before trying to recover the phone.
If you were having to pull battery to get to recovery before, I would not have attempted to update with an old and defective battery. It seems that is a symptom of either bad battery or failing eMMC.
I can't say if your eMMC is defective or even if the battery could have contributed to its potential demise.
Hopefully with a new battery fully charged, it flashes and doesn't exhibit such behavior again. Do you have the original USB cable fully functional? If not, consider original replacement for it as well while you're finding replacement battery. As for battery, I'm not sure of a good replacement but others here recommend original or Anker. I wish you success.
I'm interested to hear of your outcome so hopefully the OP doesn't mind the updates; the original failure posted isn't quite the same as yours.
Click to expand...
Click to collapse
Hey thank you i replaced my battery and now i am facing an issue of installing system update boot loop. The phone automatically keeps on doing that. Please suggest me some remedy
Thank you
vihitshah said:
The battery wasnt working properly earlier and so while updating it mst hv stopped. Inalready replaced it with new original battery
---------- Post added at 06:28 AM ---------- Previous post was at 06:24 AM ----------
hello i have samsung galaxy note 4 version SM-N910P Whenever i turn on the phone it automatically boots into recovery mode and starts installing system update and then after 100 % it switches off and never turns on back. Please Suggest me some remedy. Thank you
---------- Post added at 06:30 AM ---------- Previous post was at 06:28 AM ----------
Hey thank you i replaced my battery and now i am facing an issue of installing system update boot loop. The phone automatically keeps on doing that. Please suggest me some remedy
Thank you
Click to expand...
Click to collapse
If you're not rooted, you may be able to recover it with KIES or Smart Switch on your PC. Google these if you need them. These offer more automation and convenience than Odin but these also may only work on a phone that's not rooted or modified.
Otherwise, close those sessions on PC's task manager and download Odin and stock tar and flash firmware with that. You would also need to install the USB driver for your phone. You can find stock tar and Odin in a thread in this forum's general thread. Samsung USB driver can be found on Samsung support for Note 4.
Have you had failure to boot that booted into download and mentioned abnormal boot with eMMC read or write failure? Hopefully not; you just need to flash with one of those utilities.
eMMC failures are too often inevitable hardware failure but some manage to continue unlocking phone without having to pull battery using a wake lock app from Google Play. Any reboot, forced or not may duplicate the issue so they avoid reboots to avoid the frustration of trying to boot without flashing again. Ultimately, a reboot or flash could possibly end the life of a failing eMMC. Some have come back days or hours after removing battery. With a sufficient charge, phone may boot again after being in the battery removed state for long periods.
As far as I know, there's only theories about why eMMC fails. I've often thought heat and having shutdowns with old defective battery may speed the failure before it's life expectancy. Others believe that flashing a lot will reach an early demise but I've also read posts of phones never rooted to fail eMMC; these phones may not have been flashed so much.
Sent from my SM-N920P using Tapatalk
no its not rooted pr modified . so i should try with kies right ?
vihitshah said:
no its not rooted pr modified . so i should try with kies right ?
Click to expand...
Click to collapse
I would say yes to KIES unless you're comfortable with Odin. There's an emergency recovery mode in KIES that may just be as close to plug and play you could hope for. You still have to find it in the UI. It's been a while but I thought it was on a middle tab, middle of screen when launching KIES.
KIES may offer a prompt to recover and will download the firmware automatically. Just read and verify the prompt to ensure it properly recognized your phone model and suggested firmware.
Or do it manually and less convenient with Odin.
Sent from my SM-N920P using Tapatalk
thanks man i did it using emergency software recovery using samsung smart switch. kies is for phones before note 3
vihitshah said:
thanks man i did it using emergency software recovery using samsung smart switch. kies is for phones before note 3
Click to expand...
Click to collapse
You're welcome. And thanks for clarifying.
It boots now?
Sent from my SM-N920P using Tapatalk
samep said:
You're welcome. And thanks for clarifying.
It boots now?
Click to expand...
Click to collapse
yes fit and fine
samep said:
I would say yes to KIES unless you're comfortable with Odin. There's an emergency recovery mode in KIES that may just be as close to plug and play you could hope for. You still have to find it in the UI. It's been a while but I thought it was on a middle tab, middle of screen when launching KIES.
KIES may offer a prompt to recover and will download the firmware automatically. Just read and verify the prompt to ensure it properly recognized your phone model and suggested firmware.
Or do it manually and less convenient with Odin.
Sent from my SM-N920P using Tapatalk
Click to expand...
Click to collapse
I am still facing the issue and the issue is even greater as i am not able to go to download mode. The phone i guess goes into deep sleep mode whenever i try to restart it. I want to flash new firmware using odin as i think as per as some thread here .IS there any way i can go to download mode now ? i think it took place due to inturupted software update .
It used to show eMMC failed. But sometimes the phone boots normally
vihitshah said:
I am still facing the issue and the issue is even greater as i am not able to go to download mode. The phone i guess goes into deep sleep mode whenever i try to restart it. I want to flash new firmware using odin as i think as per as some thread here .IS there any way i can go to download mode now ? i think it took place due to inturupted software update .
It used to show eMMC failed. But sometimes the phone boots normally
Click to expand...
Click to collapse
The only suggestion I can give is pulling the battery for longer periods may temporarily help to get to download mode or boot. Some suggest also discharging the power circuit with battery pulled (hold power button) may decrease these extended battery pulls but I don't know if that helps.
The eMMC needs replacing. Samsung Support can do this fairly economically but there's about a week turnaround.
Battery pull and wake lock app is just a bandaid. Flashing firmware is likely the same.
Wish there were better solutions but I think replacement or repair is your best option.
Sent from my SM-N920P using Tapatalk
ok so bottom line is, I was in the middle of flashing official rom when at about 25% it failed. Don't ask why! (i still had recovery at this point) so I went ahead and cleaned absolutely everything thinking i'll just try and reflash as before. Now with power lead out it won't switch on at all and when power is supplied it shows message "An error has occured while udating the device software." loops at approx 3 sec intervals cant do anything with it.
Ive tried everything I can think of all to no avail! yes its my own fault bla bla bla just wondering if i act have f***** it.
Thanks to anyone with any ideas
You probably going to get a better help at TAB S2 board this is for the tab S1.
If it is hard bricked there is JTAG methods that can help, just need to find one for your device, not easy though.
But all I can do is share my experience with something like this, in a more "cheap" way than JTAGs, dunno if it helps:
I never had a similar problem on the tab S. But in the past a galaxy player 5.0 of mine had a very similar problem (as far I remember the screen just powered the back light but without any letters or simbols)
in 2012, I bricked it trying to mount a swap partition (280mb RAM ftw) accidentally pointing the wrong partition, and got the entire internal storage corrupted.. everything.. system, bootloader, recovery etc
My player was turning on only connected to a USB or charger, like yours. in fact It was hard bricked
I was able to recover it using Linux (because it is the only system able to communicate with the bricked device I had)
The problem is that everything need to be very specific, for example I used a software made for the galaxy s1 to "revive" my player 5 (both have the same hardware) it just made the device be detected via ADB. So I needed to prepare a SD with the same size as the internal storage (in this case 8gb) using the Linux terminal to mount in the SD an exactly schematic of the internal memory using a dump of another device that a xda user shared, (the dump was empty only with the bootloader, recovery etc) but it still had 8gb decompressed. So after that I used ADB to push the SD card content to the internal memory. And it get back to life \○/
Well.. it took me 1 week with a guide!! On the trial and error method. But it worked.. not perfectly, I get bootloops every time I try to flash a rom via Odin, but recovery works, and I have the device working until today
Hi, I Greatly appreciate your reply and advice. Think tho that your solution is a bit beyond my know how I know a little about ADB etc but i would have difficulties in compiling necessary files to sideload. Also many tanks for the link din't realise. Thanks Pal!
Alpha1BA said:
ok so bottom line is, I was in the middle of flashing official rom when at about 25% it failed. Don't ask why! (i still had recovery at this point) so I went ahead and cleaned absolutely everything thinking i'll just try and reflash as before. Now with power lead out it won't switch on at all and when power is supplied it shows message "An error has occured while udating the device software." loops at approx 3 sec intervals cant do anything with it.
Ive tried everything I can think of all to no avail! yes its my own fault bla bla bla just wondering if i act have f***** it.
Thanks to anyone with any ideas
Click to expand...
Click to collapse
If you can get it in to download mode you can flash stock rom back on it.......refer to xda samsung tab s2 for more details on this........
thx for reply but it reboots approx every 3 seconds so I dont have enough time to do anything with it :/
Alpha1BA said:
thx for reply but it reboots approx every 3 seconds so I dont have enough time to do anything with it :/
Click to expand...
Click to collapse
Plug in changer and push power and volume up and down all together and you will see the battery charger icon then you can get it in to download mode from there.....
stinka318 said:
Plug in changer and push power and volume up and down all together and you will see the battery charger icon then you can get it in to download mode from there.....
Click to expand...
Click to collapse
Stinka ure a superstar (atm!) I did as you suggest to no avail but I noticed a slight increase in the time it took to start rebooting again. I do not know which buttons did this but some 20 later it lasted long enough for me to be able to flash twrp. Now i havent actually tried that as yet as i wanted to check with you first... I have the battery logo on screen, i tried recovery and it started as it should but then rebooted, now im unsure at this time whether the battery is almost dead or not so i got it on charge and have the grey battery with a white flash inside... is this what i want for now until its charged? if so i'll keep you informed thamnks more than u know if uve helped me fix this, the reason i was flashing was because when i received it (no warranty!!) the screen sometimes flickered and it would constaly end up rebboting after digging around re that im lead to believe it need a new battery and for the connecting wires to be resoldered. Anyways thanks again n as I say i'll keep this updated
Cheers
Tony
one of the probs i hab/have with this unit is that it takes approx a day to fully charge!!! when i received it the screen flickered on the odd occasion but it was rebooting much more frequently. It came with stock n not messed with previously (i new this prior to purchase so got it for right price thinking it only needed flashing, how wrong was I!!!) so I flashed and encountered the above mentioned problems! thanks to stinka I surprisingly managed to flash a recovery... now provided all goes to plan, which rom would one suggest for stability and generally hassle free and prusuming the aforementioned probs, rebooting etc are still there what could i try to stop that? other than a debloated stock I found Lineage an excellent rom but still the problems got so bad the unit became unusable and was lucky not to go out the window. Im thinking do i start with a replacement battery and check the wires etc or could this still be a software issue??
if i endevoured to do the hardware myself would I attempt it by removing screen or the base for access to battery/connector??
Thanks again
In the tab s1 the best way is removing the back cover, but for some reason tab s2 seen to be the screen... at least in this guide: https://www.ifixit.com/Guide/Samsung+Galaxy+Tab+S2+Battery+Replacement/56616
Look like alot more complex than the s1 :/
RoIlingThunder said:
In the tab s1 the best way is removing the back cover, but for some reason tab s2 seen to be the screen... at least in this guide: https://www.ifixit.com/Guide/Samsung+Galaxy+Tab+S2+Battery+Replacement/56616
Look like alot more complex than the s1 :/
Click to expand...
Click to collapse
Thanks for that!!!
Tony
does look somewhat OTT!!!
will i have to odin stock first then flash rom i want or will it go straight from first flash via twrp considering there is absolutely nothing on phone at mo apart from twrp.
Alpha1BA said:
if i endevoured to do the hardware myself would I attempt it by removing screen or the base for access to battery/connector??
Thanks again
Click to expand...
Click to collapse
My guess is your issue is lack of charge in the device. That's the reason for the flashing failure and the reboot loop with the firmware error.
Bang it on charge for a while then irrespective of what it's doing, whether it's looping or not, hold POWER + HOME + VOL DOWN until download mode appears.
Reflash the stock firmware with odin.
swapped battery and reflashed stock via odin. It has helped although the issues are all still there its just they happen less frequently which doesnt mean its any less frustrating.