Related
Hi, im on the DK28 version of froyo, i cant update to ec05 because the phone will no longer mount to any pc, i have tried multiple pc's and multiple cords and cannot get the phone to mount.
When i try to flash the an update.zip other than the dk28 version i get errors. The phone used to have root but when i reflashed DK28 thinking it would fix the sd card issue, i lost root. I cant 0ne click it, i cant odin a rom. It left the Superuser application behind (Which I cant uninstall). Also I tried a wipe data/factory. When i try updating to EC05 i was getting an error 2. Basically im completely stuck on DK28.
At the very least i need to get the superuser application off the phone so i can return it since i believe the mounting issue is a hardware failure.
Does anyone have an update.zip that will not give me a signature error? Or have something i can try to get this fixed enough to return it to sprint.
I am on my phone so can't search for you right now but you are looking for that Samsung.exe file whichb was an Odin-like executable with EB13 stock files. I can look tonight if someone doesn't give you a link before then.
Do you BONSAI?
kennyglass123 said:
I am on my phone so can't search for you right now but you are looking for that Samsung.exe file whichb was an Odin-like executable with EB13 stock files. I can look tonight if someone doesn't give you a link before then.
Do you BONSAI?
Click to expand...
Click to collapse
That sounds like i would have to run the file from a pc, which at the moment, no pc is seeing this phone in either download mode nor via odin, one click or just plain ole mounting.
IzzyRios said:
That sounds like i would have to run the file from a pc, which at the moment, no pc is seeing this phone in either download mode nor via odin, one click or just plain ole mounting.
Click to expand...
Click to collapse
Bro try different t ports on the computer try restarting the phone and computer also if none of that works try different USB cords different computer as well if non of that works u need to get a new USB cable...
Sent from my Epic 4.1g bonsai plant
davidrules7778 said:
Bro try different t ports on the computer try restarting the phone and computer also if none of that works try different USB cords different computer as well if non of that works u need to get a new USB cable...
Sent from my Epic 4.1g bonsai plant
Click to expand...
Click to collapse
Unfortunatly ive tried 3 different cables as well as different computers and different usb ports on each one of them. What i need is a Non-pc involved solution for this. I can live without mounting the phone to the pc, if i could just get upgraded to Sprints official EC05 rom. I know it has its problems, but at least it wont lock me out of ota like DK28 has, and then i can at least take the phone bak to the store at my liesure.
Have you tried removing and reinserting the SD card? When you 3 finger the phone you only get stock recovery? Does the charge light come on with the data cable in the USB port?
kennyglass123 said:
Have you tried removing and reinserting the SD card? When you 3 finger the phone you only get stock recovery? Does the charge light come on with the data cable in the USB port?
Click to expand...
Click to collapse
The charging portion works fine, also i have 2 diff micro sd's tried with either one in and with neither in. didnt work. 3 finger only gives me stock and not Cwm anymore since i reflashed DK28
IzzyRios said:
The charging portion works fine, also i have 2 diff micro sd's tried with either one in and with neither in. didnt work. 3 finger only gives me stock and not Cwm anymore since i reflashed DK28
Click to expand...
Click to collapse
Have you tried toggling the USB debugging mode? Also try download mode (power on holding "1" key) then see if Odin recognizes your phone.
kennyglass123 said:
Have you tried toggling the USB debugging mode? Also try download mode (power on holding "1" key) then see if Odin recognizes your phone.
Click to expand...
Click to collapse
yes to both. odin does not see the phone. Im certain that its a hardware problem at this point, which is why im looking for an update zip i can manually put on the card that will let me flash ec05 on to the phone and erase super user. at the very least i want to remove super user.
IzzyRios said:
yes to both. odin does not see the phone. Im certain that its a hardware problem at this point, which is why im looking for an update zip i can manually put on the card that will let me flash ec05 on to the phone and erase super user. at the very least i want to remove super user.
Click to expand...
Click to collapse
I thought the sd cards won't mount? If they do then it will have to be a signed update zip that doesn't check for the stock apps and previous modem version.
kennyglass123 said:
I thought the sd cards won't mount? If they do then it will have to be a signed update zip that doesn't check for the stock apps and previous modem version.
Click to expand...
Click to collapse
Im Sorry i should have clarified this. The phone can see the SD cards just fine..Internally. But when i connect a cable (any cable, i have 4) to the pc (any pc, i tried on 3 dif pc's one xp, two windows 7), i cannot see the cards from the PC, odin does not see the phone, etc, basically interfacing between the 2 is nil. I am currently taking the micro sd card out of the phone, putting it into a usb adaptor and copying files to it from the pc that way, then returning the card to the phone in order to try to update it. My problem is, i need a Rom that will update without trying to verify the signature since it thinks my phone is rooted, even though it isnt anymore. At this point i wouldnt even mind a wipe since i did that yesterday anyway, just going back to DK28 Stock. Problem with Dk28 is it doesnt allow the OTA of Ec05 to come in.
Ok got it for you. Try this for update.zip to get you to DI18:
http://forum.xda-developers.com/showthread.php?t=786266
Do you BONSAI?
kennyglass123 said:
Ok got it for you. Try this for update.zip to get you to DI18:
http://forum.xda-developers.com/showthread.php?t=786266
Do you BONSAI?
Click to expand...
Click to collapse
Yeah this didnt work. the first link is broken, but once i found the rom much further in the thread i got it. Trying to install it produces this error...E:Signature Verification Failed. Installation abouted.
IzzyRios said:
Yeah this didnt work. the first link is broken, but once i found the rom much further in the thread i got it. Trying to install it produces this error...E:Signature Verification Failed. Installation abouted.
Click to expand...
Click to collapse
Look further in the thread to see if someone put up a signed version. Amend2edify will create a signed zip, it may convert the one you downloaded. I found that thread by googling "update.zip for dk28 samsung epic" there were a lot more results I didn't check out.
Do you BONSAI?
kennyglass123 said:
Look further in the thread to see if someone put up a signed version. Amend2edify will create a signed zip, it may convert the one you downloaded. I found that thread by googling "update.zip for dk28 samsung epic" there were a lot more results I didn't check out.
Do you BONSAI?
Click to expand...
Click to collapse
The rom i downloaded had signed in the name and its what gave me the signature error.
stock.di18.deodexed.updatev3.signed.zip
IzzyRios said:
The rom i downloaded had signed in the name and its what gave me the signature error.
stock.di18.deodexed.updatev3.signed.zip
Click to expand...
Click to collapse
D'OH! There is a thead with flashable stock ec05 roms. Maybe you can ask the dev to make it work as a signed flash from stock recovery.
Do you BONSAI?
Dial ##8778## and make sure that PDA is checked under the USB setting
stir fry a lot said:
Dial ##8778## and make sure that PDA is checked under the USB setting
Click to expand...
Click to collapse
What does that do?
Well for one it can cause your USB not to mount..
There is a guy named drockstar in the development section that has stock roms posted they might be able to help you
Sent from my SPH-D700 using XDA Premium App
Hello all I am in a bit of a situation.
This is the second time I have posted regarding me causing my galaxy note 2 to be out of order. Today I used TWRP to wipe my OS then also deleted all of my data wiping the os's I had downloaded. I only have a Mac thus the help for Mac's and Android is very limited thus I am wondering if there would be any way to get this fixed without using a Windows computer right now my phone is stuck rebooting.
Sorry to bother you all again,
Max
I don't know if I understand your post fully, but... It sounds like you wiped the device, and wiped the ROM that you downloaded? I've seen this increasingly lately.
Anyways..
Download another ROM and place it on an external SD card. You'll need an adapter to be able to hook the SD up to the computer. Or just borrow someone's SD. (just don't wipe it too)
Put the SD in and flash the ROM. just shut the phone off and when you're ready, use the three button combo to get back to TWRP.
Please hit the triangle on the side of your post and report it for thread maintenance to be moved. This thread (A question thread) belongs in the Q&A section.
Brad.S. said:
I don't know if I understand your post fully, but... It sounds like you wiped the device, and wiped the ROM that you downloaded? I've seen this increasingly lately.
Anyways..
Download another ROM and place it on an external SD card. You'll need an adapter to be able to hook the SD up to the computer. Or just borrow someone's SD. (just don't wipe it too)
Put the SD in and flash the ROM. just shut the phone off and when you're ready, use the three button combo to get back to TWRP.
Please hit the triangle on the side of your post and report it for thread maintenance to be moved. This thread (A question thread) belongs in the Q&A section.
Click to expand...
Click to collapse
Is there any way I could do it without an SDcard?
mmckenna11 said:
Is there any way I could do it without an SDcard?
Click to expand...
Click to collapse
With a Mac, not that I know of.
Give it a few hours and maybe someone with higher knowledge of mac+android will chime in.
The phone is blank right now, I would hesitate to even try to turn it on. You could use windows and Odin. You might be able to adb the files to the device..But that is more learning/hassle than the SD. Using the SD is really the easiest.
I'd let you borrow mine but shipping would take a while (haha)
I have an iMac and have the same problem. Android file transfer doesn't even recognize my device for MTP transfer. But I have four other windows machines here, so no biggie for me.
How would you go about doing it using windows?
mmckenna11 said:
How would you go about doing it using windows?
Click to expand...
Click to collapse
Install Odin and grab the stock OS files
Place the phone into download
And push the stock os to the phone
It would be as if you were going back to full stock.
There are numerous guides on how to do it.
Here are a bunch of resources:
http://forum.xda-developers.com/showthread.php?t=1987541
if you install a VM on your mac, or if you have one already installed, then just run it, install Odin on it, and install the stock ROM that way..
wase4711 said:
if you install a VM on your mac, or if you have one already installed, then just run it, install Odin on it, and install the stock ROM that way..
Click to expand...
Click to collapse
Exactly what I do! Parallels 7 does the trick for me if my windows box has a non specific color screen of death.
Sent from my SGH-I317 using xda app-developers app
For ATT they all seem to be in .zip file format yet you cant use that with odin so how would i go about doing this?
How do you place a file directly into a directory so i can use recovery to flash it on?!
I just inherited a t-mobile phone that was rooted. I installed the latest version of TWRP and tried to re-root it but now it's in a boot loop and on top of that I can't connect the phone to a computer b/c I get the "USB Device Not Recognized" message. I've re-installed the drivers and I've tried the toothpick trick. Nothing is working. What are my options?
jconway1968 said:
I just inherited a t-mobile phone that was rooted. I installed the latest version of TWRP and tried to re-root it but now it's in a boot loop and on top of that I can't connect the phone to a computer b/c I get the "USB Device Not Recognized" message. I've re-installed the drivers and I've tried the toothpick trick. Nothing is working. What are my options?
Click to expand...
Click to collapse
First wrong section...second I'd say flash a different Rom/kernel pair... or redo your recovery from Odin
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
bmg002 said:
First wrong section...second I'd say flash a different Rom/kernel pair... or redo your recovery from Odin
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
First, I believe this is the correct section - the phone I am working with is a T-Mobile Galaxy S II... Second, I can't Odin because I don't have a working usb connection. I've tried several different ROMS from this fine section and I get the same result... Boot Loop
If you flashed TWRP 2.6.3, that's your problem.
Flash 2.6.1
This is the wrong section because it has nothing to do with ROM development.
With that being said if you can still boot into twrp you still have hope. Try loading a different ROM into an SD card using a converter and slide back in the phone to properly wipe first then re flash.
I don't understand why you can't get a proper USB connection going but above suggestion may solve it.
Sent from my SGH-T989 using xda app-developers app
You could always get a SD card reader, connect t to ur PC, DL a flashable twrp 2.6.1.0 and flash the recovery, then flash a ROM an u should be back in action, but above mentioned is right this is the wrong forum u need q&a
Sent from my -T989 using XDA Premium 4 mobile app
jconway1968 said:
First, I believe this is the correct section - the phone I am working with is a T-Mobile Galaxy S II... Second, I can't Odin because I don't have a working usb connection. I've tried several different ROMS from this fine section and I get the same result... Boot Loop
Click to expand...
Click to collapse
Just to confirm a few things: where do you not have the working USB connection? in download mode? If so, I'd try reinstalling the drivers.
Also, I see in your sig that you state your phones are:
Asus Nexus 7
Sprint Galaxy Note 2
Neither of which is a SGH-T989. Are you sure you are flashing the correct ROM/Kernel for your device?
also you said it came rooted but you re-rooted it. What process did you use to re-root it?
One last thing: you say you got it second hand, are you sure it is a T-Mobile galaxy S 2? May want to check under the battery for a "T989" or "i9100". The i9100 is NOT a T-Mobile galaxy S 2. It should be SGH-T989 if they didn't give you incorect info about the phone.
You could also try a different USB cable or hub. I've had USB extension cables give me grief and the front ports on my PC don't like my phone.
bmg002 said:
Just to confirm a few things: where do you not have the working USB connection? in download mode? If so, I'd try reinstalling the drivers.
Also, I see in your sig that you state your phones are:
Asus Nexus 7
Sprint Galaxy Note 2
Neither of which is a SGH-T989. Are you sure you are flashing the correct ROM/Kernel for your device?
also you said it came rooted but you re-rooted it. What process did you use to re-root it?
One last thing: you say you got it second hand, are you sure it is a T-Mobile galaxy S 2? May want to check under the battery for a "T989" or "i9100". The i9100 is NOT a T-Mobile galaxy S 2. It should be SGH-T989 if they didn't give you incorect info about the phone.
You could also try a different USB cable or hub. I've had USB extension cables give me grief and the front ports on my PC don't like my phone.
Click to expand...
Click to collapse
Thanks for your help. Here are the answers to your questions:
I think there is something wrong with the micro USB input on the phone. I have reinstalled the drivers several times. I have tried different cables and different computers. I even tried the toothpick trick. No luck.
I do have a GN2. The SG2 is for my daughter...
It is a genuine SGH-T989 I checked under the battery.
soupysoup said:
You could always get a SD card reader, connect t to ur PC, DL a flashable twrp 2.6.1.0 and flash the recovery, then flash a ROM an u should be back in action, but above mentioned is right this is the wrong forum u need q&a
Sent from my -T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Where do I find and how do I put a flashable twrp 2.6.1.0 on my micro sd card? I've always used goomanager in the past but obviously that won't work in this case...
jconway1968 said:
Where do I find and how do I put a flashable twrp 2.6.1.0 on my micro sd card? I've always used goomanager in the past but obviously that won't work in this case...
Click to expand...
Click to collapse
Everything I've found requires a computer connection. I need to be able to flash it back from v2.6.3.1 using TWRP to do it. Is that possible?
soupysoup said:
You could always get a SD card reader, connect t to ur PC, DL a flashable twrp 2.6.1.0 and flash the recovery, then flash a ROM an u should be back in action, but above mentioned is right this is the wrong forum u need q&a
Sent from my -T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
One more piece of information that might be helpful... When I try to wipe the cache I get this message "Formatting Data using make_ext4fs function" and it stays stuck there. I've left it for over 30 minutes and it doesn't ever move from that screen. Hope that helps... I really need some help here.
jconway1968 said:
One more piece of information that might be helpful... When I try to wipe the cache I get this message "Formatting Data using make_ext4fs function" and it stays stuck there. I've left it for over 30 minutes and it doesn't ever move from that screen. Hope that helps... I really need some help here.
Click to expand...
Click to collapse
In twrp settings change it to use rm instead of formatting
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
jconway1968 said:
Everything I've found requires a computer connection. I need to be able to flash it back from v2.6.3.1 using TWRP to do it. Is that possible?
Click to expand...
Click to collapse
If u go to the dev section on this phone and look around a bit, u will find the twrp thread, in that thread is a flashabke copy of 2.6.1.0, if u can't find it pm me, I have a copy, all u would need to do is put the zip file on any micro SD card then put it in the phone and flash it with the twrp u have now, it will revert it back to 2.6.1.0 and that should fix ur prob, but like I said of u can't find it pm me and I'll shoot u a copy
Sent from my -T989 using XDA Premium 4 mobile app
soupysoup said:
If u go to the dev section on this phone and look around a bit, u will find the twrp thread, in that thread is a flashabke copy of 2.6.1.0, if u can't find it pm me, I have a copy, all u would need to do is put the zip file on any micro SD card then put it in the phone and flash it with the twrp u have now, it will revert it back to 2.6.1.0 and that should fix ur prob, but like I said of u can't find it pm me and I'll shoot u a copy
Sent from my -T989 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok so I Flashed it and now it's stuck on the Blue Teamwin screen???
jconway1968 said:
Ok so I Flashed it and now it's stuck on the Blue Teamwin screen???
Click to expand...
Click to collapse
Let it sit on the TeamWin screen for a minute or so... I find it sometimes takes a little bit.
If it doesn't ever get past there, try hooking it up to a PC and see if you can get ADB to load (presuming you have ADB installed and ADB drivers installed). If you can, try to do an "adb pull /proc/last_kmsg" and a "adb logcat > logcat.txt" and zip those up and toss them on here.
If you CAN'T get into adb, I would try hooking the phone up to Kies and see if it will do anything for you.
Or you could try following this guide as you have the T-Mobile SGH-T989 (not the Telus SGH-T989D):
http://forum.xda-developers.com/showthread.php?t=1513359
BUT make sure to grab the correct stock image file for whatever version your android currently is (ie if you are on Android 2.3.6, then make sure to get the T-mobile KL1 2.3.6 stock image).
Also, what ROM did you flash? was it a 4.3 ROM? If so, did you update your radio before you flashed the ROM? I think 4.1+ needs the updated radio to function properly.
I know you said you can't connect through ODIN, but I'm hoping it is because of some odd driver or odd ODIN version. That thread has the stuff to make it all work I believe.
I'm really hoping you can get ADB to work. If you can pull a logcat of your bootup process, it will be much easier to figure out what went wrong.
bmg002 said:
Let it sit on the TeamWin screen for a minute or so... I find it sometimes takes a little bit.
If it doesn't ever get past there, try hooking it up to a PC and see if you can get ADB to load (presuming you have ADB installed and ADB drivers installed). If you can, try to do an "adb pull /proc/last_kmsg" and a "adb logcat > logcat.txt" and zip those up and toss them on here.
If you CAN'T get into adb, I would try hooking the phone up to Kies and see if it will do anything for you.
Or you could try following this guide as you have the T-Mobile SGH-T989 (not the Telus SGH-T989D):
http://forum.xda-developers.com/showthread.php?t=1513359
BUT make sure to grab the correct stock image file for whatever version your android currently is (ie if you are on Android 2.3.6, then make sure to get the T-mobile KL1 2.3.6 stock image).
Also, what ROM did you flash? was it a 4.3 ROM? If so, did you update your radio before you flashed the ROM? I think 4.1+ needs the updated radio to function properly.
I know you said you can't connect through ODIN, but I'm hoping it is because of some odd driver or odd ODIN version. That thread has the stuff to make it all work I believe.
I'm really hoping you can get ADB to work. If you can pull a logcat of your bootup process, it will be much easier to figure out what went wrong.
Click to expand...
Click to collapse
You guys are great!!! I really appreciate all the help. No matter what I do, ADB, Kies, different cables, different computers, nothing gets past the "USB Device Not Recognized" pop up. I let it sit for 15 minutes, twice. Still no love... I loaded TWRP_2.6.1.0_Hercules and then reboot and that's when it got stuck. Prior to that I had loaded TMobileT989UVMC6RootedDeodexed Rom. I forget where I got it. I'm pretty sure it was a 4.1.2 based rom.
jconway1968 said:
You guys are great!!! I really appreciate all the help. No matter what I do, ADB, Kies, different cables, different computers, nothing gets past the "USB Device Not Recognized" pop up. I let it sit for 15 minutes, twice. Still no love... I loaded TWRP_2.6.1.0_Hercules and then reboot and that's when it got stuck. Prior to that I had loaded TMobileT989UVMC6RootedDeodexed Rom. I forget where I got it. I'm pretty sure it was a 4.1.2 based rom.
Click to expand...
Click to collapse
weird... I am not sure why it is being so fussy with your phone.
Hopefully somebody has a better suggestion than I do, but my next thought is to try ebay-ing the phone in hopes that somebody gives you a few bucks for it. It sounds to me like the internal memory module is dying and the USB port is shot.
Is your water damage sticker pink/red or missing? It should be under the battery.
I hate thinking that the phone is just dead, but without being able to connect it to the PC in either recovery or download mode and not being able to boot into a ROM or recovery, I think the next step is to scrap it and hope somebody can send you a few bucks... or if you have experience soldering, maybe try replacing the USB connector?
I could be wrong mind you... The only time I had issues like that it was due to a badly flashed recovery and I needed to use ODIN to get back up and running. As a thought, do you have a Windows XP 32-bit computer you could try plugging the phone into? And while the phone is plugged in, can you check device manager for all devices? maybe try installing the drivers manually? I suggest windows XP 32bit because that is what I use the majority of the time with my phone. I've also used Windows 7 64-bit and it worked.
bmg002 said:
weird... I am not sure why it is being so fussy with your phone.
Hopefully somebody has a better suggestion than I do, but my next thought is to try ebay-ing the phone in hopes that somebody gives you a few bucks for it. It sounds to me like the internal memory module is dying and the USB port is shot.
Is your water damage sticker pink/red or missing? It should be under the battery.
I hate thinking that the phone is just dead, but without being able to connect it to the PC in either recovery or download mode and not being able to boot into a ROM or recovery, I think the next step is to scrap it and hope somebody can send you a few bucks... or if you have experience soldering, maybe try replacing the USB connector?
I could be wrong mind you... The only time I had issues like that it was due to a badly flashed recovery and I needed to use ODIN to get back up and running. As a thought, do you have a Windows XP 32-bit computer you could try plugging the phone into? And while the phone is plugged in, can you check device manager for all devices? maybe try installing the drivers manually? I suggest windows XP 32bit because that is what I use the majority of the time with my phone. I've also used Windows 7 64-bit and it worked.
Click to expand...
Click to collapse
Thanks again for your time and suggestions... I've always been very impressed with the xda community. I actually got this phone, used, from Swappa. And I am in the process of returning it for a refund. But the seller is being difficult and is trying to stick me with the phone. I was just trying to salvage it on my own, just in case... Thanks again.
jconway1968 said:
Thanks again for your time and suggestions... I've always been very impressed with the xda community. I actually got this phone, used, from Swappa. And I am in the process of returning it for a refund. But the seller is being difficult and is trying to stick me with the phone. I was just trying to salvage it on my own, just in case... Thanks again.
Click to expand...
Click to collapse
that sucks. I've heard good things about Swappa, but living in Canada I can't use it. My opinion it sounds like you got a dud and based on how hard the guy is fighting to not give you a refund, I wouldn't be surprised if he knew it was doa and just fluked out and get it running before he sold it. Or maybe it got water damaged and he knew it would fail soon so he sold it before it completely quit.
I hope you get it all sorted out.
Good luck and sorry I couldn't be more helpful.
bmg002 said:
that sucks. I've heard good things about Swappa, but living in Canada I can't use it. My opinion it sounds like you got a dud and based on how hard the guy is fighting to not give you a refund, I wouldn't be surprised if he knew it was doa and just fluked out and get it running before he sold it. Or maybe it got water damaged and he knew it would fail soon so he sold it before it completely quit.
I hope you get it all sorted out.
Good luck and sorry I couldn't be more helpful.
Click to expand...
Click to collapse
You were great!!! Thanks again...
UPDATE:Thanks to the hard work and diligence of XDA members @noobtoob, @ecs87, and recognized contributor @DocHoliday77, recognized developer @shabbypenguin, and others who will be added to this list after I go through some threads for their names -
It is my pleasure to announce that owners of the T-Mobile Samsung Galaxy Note 3 who have unfortunately hard-bricked
their device, (will not turn on, no led light, qhusb_download mode as device status when plugged into pc) are NOW able to boot their device using sd card mode, instead of expensive JTAG repair!!
noobtoob has been so kind as to ship me the sd card that he successfully flashed, with uncorrupted files from a working tmobile note 3, using odin! Thank you! These files contain all of the prerequisite files needed to boot in this state, to download mode! Once there, a stock firmware flash with ODIN will totally restore your device, just as the SM-N900A variant (at&t), and tmobile and sprint galaxy s3 hard-unbrick methods right here on XDA, can accomplish as I type!
Now, owners of this device can flash with alot more ease, and also this could not only lead to discovery of this method for the entire Note 3 series, perhaps other devices as well!
Read the thread! Why just look for a quick fix when you can actually learn more about the way file systems in android work - and what to avoid doing so that the chances of this happening in the future are less likely? I conducted quite a bit of research, and spoke to some very talented people to get this thread where it is - and to learn some new things myself. This thread contains alot of good insight and discussion about how to solve this issue. Perhaps you could learn something. Either way, all of what you need to fix a hard brick for these two devices is here.
[Update] 12/17/13]
I do in fact now have the sd card. Thanks @noobtoob! The device will not boot still.
I'm going to try a jig also.
[UPDATE] 12-21-13
Thanks to time, guidance, and commands from @shabbypenguin, we found the reason why the sd card noobtoob wrote the umbrick.img to will not boot. It is simply not large enough! So now thanks to proper guidance and this is from shabbypenguin, Tmobile Note 3 users are almost safe from a hard-brick!
If anyone deserves credit for this all, it is @shabbypenguin and @KAsp3rd, and ultimately Samsung, for at least programming their phones to be virtually fail-safe! Special thanks @zinnium to be the first to report this working for them! Thank You!
We have the new .img , so the proper method, and files will be in this post for all to use. For now, they are in this thread. Of course all contributors will be thanked. Give me a little time to get myself together here in the real world, this has happened so fast I've barely had time to keep up!!!!!
Pm me, or post if this method works for you. Now, I mean this only if you first are aware that **IF YOU FLASH ANYTHING OR USE THIS METHOD IT IS AT YOUR OWN RISK - I OR NO ONE ELSE IS RESPONSIBLE BUT YOU!!**
Also, only if you are simply using the very last unbrick.img posted by noobtoob, in this thread. It is ONLY FOR THE TMOBILE NOTE 3 SM-N900T VARIANT!!!! USING IT FOR ANY OTHER MODEL WILL NOT WORK!! THERE IS AN UNBRICK.IMG FOR THE SM-N9005 ALSO AT THE BOTTOM OF THIS POST! **AGAIN - ONLY USE THE .IMG THAT IS FOR YOUR SPECIFIC DEVICE!!!! YOU HAVE BEEN WARNED AND IT IS NOT MY RESPONSIBILITY IF ANYTHING GOES BAD!!!**
The file is 165mb in size, and needs to be written to a 32 or 64 gig sd card with Linux or another image writing tool, even using a CORRECT dd command in terminal emulator, with a rooted device. It has also been confirmed by XDA member zinnium to work with a 310mb system dump from of course - a WORKING T-Mobile Note 3. Also, XDA member aiti1980 has confirmed success with hard-unbricking the SM-N9005 model. The slimmer file does however, also contain all of the necessary partitions to correctly re-write improperly overwritten ones, including recovery!
Do not try to start a new thread and take credit for this!! This is the thread where this method started specifically for the t-mobile note 3 , and I take no credit for this method!!!! The real thanks should go to @shabbypenguin, and @KAsp3rd, who have brought this method, from unknown origins of my knowledge at the time of writing this - to XDA. @shabbypenguin has been kind enough to lend his expertise and time here in this thread, for the t-mobile note 3!! YAY Just in time for Christmas! Merry Christmas All!
UPDATE: 12/24/13 - Here's a Christmas gift for all SM-N9005 owners with a hard-bricked device...
aiti1980 said:
ooo! Thanks!!!
I use adb driver
into cmd win 7 i run:
ADB SHell
su
and you command and get unbrick.img
waiting for result...
I writting *.img on adata Microsd card from win 32 Disk Image
Update: WOW!!! My hard bricked phone power up!
Many thanks from RussiaĐ–)))
Where me put unbrick.img: dropbox, or another service?
Click to expand...
Click to collapse
This method works for the SM-N9005 variant too! CONFIRMED!
One step closer for a universal hard-unbrick method for ALL
Galaxy Note 3 Models! HURRAH Special thanks to aiti1980 for being the first to try and succeed! Congrats!
MERRY CHRISTMAS!*
Note 3 SM-N900T unbrick.img
http://www.mediafire.com/?6nu61z43y51v3k4
Thanks to noobtoob for the above SM-N900T unbrick.img
https://mega.co.nz/#!UtNhgAja!XLL6Xy7qxW0L9t4ZgXgowHFNlSsLuz5RIQ-fQc5Ctxk
Thanks to aiti1980 for the above SM-N9005 Unbrick.img upload! ENJOY
Try using ODIN to flash back to stock. Then root using one of the available ways on XDA. Normally you install TWRP using Goo manager after root. It's that simple.
Sent from my SM-N900T using Tapatalk 2
NeoAndroid said:
Try using ODIN to flash back to stock. Then root using one of the available ways on XDA. Normally you install TWRP using Goo manager after root. It's that simple.
Sent from my SM-N900T using Tapatalk 2
Click to expand...
Click to collapse
I know that. I don't have a pc so I noticed on the twrp page that terminal emulator was an option, so I tried it.
Odin will not recognize the phone, how exactly do I use your method?
msmercy42 said:
I know that. I don't have a pc so I noticed on the twrp page that terminal emulator was an option, so I tried it.
Odin will not recognize the phone, how exactly do I use your method?
Click to expand...
Click to collapse
Recovery on the note 3 is actually on mmcblk0p15. So the issue is thankfully the partition you were trying to write to didn't have enough space to write.
If you change it to mmcblk0p15 you should be good. Or just install goo manager and install that way which is simplest. Should be option to install open recovery script.
Sent from my SM-N900T using xda app-developers app
chstewart said:
Recovery on the note 3 is actually on mmcblk0p15. So the issue is thankfully the partition you were trying to write to didn't have enough space to write.
If you change it to mmcblk0p15 you should be good. Or just install goo manager and install that way which is simplest. Should be option to install open recovery script.
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
The help is much appreciated, however I cannot turn on the phone at all...
msmercy42 said:
The help is much appreciated, however I cannot turn on the phone at all...
Click to expand...
Click to collapse
You should be able to get into download mode still. Try pushing a new recovery with Odin. If still having issues Odin stock or you can also use kies to restore your phone....
Sent from my SM-N900T using xda app-developers app
Thanks for the help, I can't get the phone on at all though... it doesn't even recognize my device other than windows stating that it cannot recognize it, as it
malfunctioned.
Kies, will recognize it, even in this case?
Lastly, are you telling me that there is a way to push recovery with Odin even though the device is off, will not go into download mode, or recovery? If so, that's great!
Try with kies, best option as it will firmware reset your device back to stock.
Sent from my SM-N900T using xda premium
d12unk13astard said:
Try with kies, best option as it will firmware reset your device back to stock.
Sent from my SM-N900T using xda premium
Click to expand...
Click to collapse
Thanks for the assist... will try kies as soon as I get to a PC in the morning. I honestly hope kies does the trick, PC stated it didn't recognize my device due to a malfunction.
I'll check the drivers also. Do you have any other suggestions? I just want to try every avenue avaiable. Again, thanks a lot.
msmercy42 said:
Thanks for the assist... will try kies as soon as I get to a PC in the morning. I honestly hope kies does the trick, PC stated it didn't recognize my device due to a malfunction.
I'll check the drivers also. Do you have any other suggestions? I just want to try every avenue available. Again, thanks a lot.
Click to expand...
Click to collapse
Update - I tried using Odin 1.85. I see the device being recognized in one of the ports, but flashing the stock firmware, or twrp yielded no results.
I tried reinstalling the Samsung drivers, nothing. I even tried Odin 3.07, and 3.09. Since the device will not power on, I guess that is why it will not work.
I then tried an emergency firmware recovery using kies. It did not detect the device, which is normal, so I disconnected and reconnected the device repeatedly,
with no success. I uninstalled an reinstalled kies, and that did nothing either.
I installed the android 4.3 sdk, and used adb in an attempt to recognize the device using commands like adb reboot recovery.
Adb replied with : no devices found.
I attempted through windows, to examine the ports, and found that there were different drivers present. The drivers installed on the PC were named QHUSB_DOWNLOAD 9008. When I first plugged the device to the PC, I noticed the device named as QHUSB_BULK, before changing to the above name, the same as the name for the drivers.
So my device is still alive.
Any advice? Can anyone help me get my phone on, at least into download mode? From there I can get it going. Please help if possible.
Sorry been busy with work. Are you sure you can't get into download mode? I originally wrote twrp to the wrong partition as you did and could still get download mode.
Theoretically it shouldn't have done anything that would prevent download mode from working....
Manual method for getting into download mode.
Volume-down+home+power
Sent from my SM-N900T using xda app-developers app
chstewart said:
Sorry been busy with work. Are you sure you can't get into download mode? I originally wrote twrp to the wrong partition as you did and could still get download mode.
Theoretically it shouldn't have done anything that would prevent download mode from working....
Manual method for getting into download mode.
Volume-down+home+power
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
I tried everything. No, download mode is not working, though I agree that it should theoretically still. I am still trying the three button method.
Would a jig work? I am working on one. Any ideas besides that?
i was going to suggest a jig actually. if that doesn't work you're probably out of a phone. could try warranty since it's REALLY bricked they probably won't be able to tell, did it with T-Mo on my G1, said it stopped turning on.
Have you tried removing the battery and holding down all the buttons before reinserting the battery again. My phone wouldn't turn on once and this helped. If not call tmobile tell them all kinds of funky things are happening with your phone and it keeps turning off. Once they tell you to factroy reset your phone, act like you are following their instructions, then when they tell you to turn it back on, tell them it will now not even turn back on. They are so slow there & will send you out a new one you'll have in 24hrs. Trust me Ive had to do this numerous times due to ocd when it comes to phones and having to have reasons to return them for the slightest flaw. I returned my galaxy note 2 before i got this note 3 like 8x's & even returned it the wk before i bought my note 3 just to get 1 with all new parts if not maybe even a new phone so the note 2 i sold would be in practically new condition if not like i said brand new,lol. im sure someones gonna get all butt hurt and start talking about fraud,lol
In the future you can flash Twr using Goo on your phone with No computer. Use JRummy 's rom Toolbox pro.
Sent from my Nexus 4 using xda app-developers app
chstewart said:
Sorry been busy with work. Are you sure you can't get into download mode? I originally wrote twrp to the wrong partition as you did and could still get download mode.
Theoretically it shouldn't have done anything that would prevent download mode from working....
Manual method for getting into download mode.
Volume-down+home+power
Sent from my SM-N900T using xda app-developers app
Click to expand...
Click to collapse
I agree, I simply followed the instructions on the twrp site, to flash recovery through terminal emulator.. I might have been off with the last number, and it obviously messed up my partitions... how did you get into recovery? The three button combo isnt working at all , no variation of it or battery pulls, or inserts have worked yet..
Also this is the place to get answers. Yet almost a thousand views but not even 20 posts. I know there is a way to fix this, can anyone share the fix?
msmercy42 said:
I agree, I simply followed the instructions on the twrp site, to flash recovery through terminal emulator.. I might have been off with the last number, and it obviously messed up my partitions... how did you get into recovery? The three button combo isnt working at all , no variation of it or battery pulls, or inserts have worked yet..
Also this is the place to get answers. Yet almost a thousand views but not even 20 posts. I know there is a way to fix this, can anyone share the fix?
Click to expand...
Click to collapse
It doesnt look good. I sent my vzw dev note 3 to Samsung with the same reboot problems and not being able to flash anything, and even they couldn't fix it.
Sent from my SCH-I535 using Tapatalk
msmercy42 said:
I used a command like : adb push*openrecovery-twrp-2.6.3.x-hltetmo.img*/sdcardadb shell dd if=/sdcard/openrecovery-twrp-2.6.3.x-hltetmo.img*of=dev/block/platform/msm_sdcc.1/by-name/recovery, in terminal emulator to flash twrp. "Mmkblk0ps9" was at the end.
26081 files sent
26081filews recieved
write error : no space left
That is what I saw next. I tried it again, three times, but noticed that write error was not there, so I assumed it was successful.
I rebooted, as instructed, and now a totally bricked device. I saw " qhusb_download " plugging it into one pc. A laptop with windows 8 stated that windows cannot recognize the device because it has malfunctioned.
Can someone please help? This is a disaster... the sm-900a has a method here on xda that fixes this problem... is there a way to fix this on a tmobile note 3?
Click to expand...
Click to collapse
Sorry to hear! I'll save you a whole bunch of time, I did the same thing to my galaxy s3 while trying to upgrade my installed clockworkmod. Long story short the commands I entered into terminal emulator we're fine its just that I put the wrong memory block which apparently flashed the image to the wrong area of the chip. I rebooted the phone and nothing happened. When I plugged it into the PC I would get the same thing you're getting. After a ridiculous amount of time I managed to get my hands on the correct drivers and installed them and found that flashing a stock firmware through Odin was a waste of time.
You need to send your phone into Samsung and the only solution is a motherboard replacement. Or you can find someone locally who can do a JTAG mod for you. But doing so will definitely void your warranty. When I shipped my phone into Samsung I told them I was using the phone and all of a sudden it got very hot and turned off and wouldn't turn on. Back in the S3 days I had to wait 3 weeks to get my phone back repaired. But these days there now Samsung service centers everywhere so you can probably get replaced phone on the spot.
Sent from my SM-N900W8 using Tapatalk 4
Qhusb_bulk drivers??
msmercy42 said:
I used a command like : adb push*openrecovery-twrp-2.6.3.x-hltetmo.img*/sdcardadb shell dd if=/sdcard/openrecovery-twrp-2.6.3.x-hltetmo.img*of=dev/block/platform/msm_sdcc.1/by-name/recovery, in terminal emulator to flash twrp. "Mmkblk0ps9" was at the end.
26081 files sent
26081filews recieved
write error : no space left
That is what I saw next. I tried it again, three times, but noticed that write error was not there, so I assumed it was successful.
I rebooted, as instructed, and now a totally bricked device. I saw " qhusb_download " plugging it into one pc. A laptop with windows 8 stated that windows cannot recognize the device because it has malfunctioned.
Can someone please help? This is a disaster... the sm-900a has a method here on xda that fixes this problem... is there a way to fix this on a tmobile note 3?
Click to expand...
Click to collapse
Hey, Any luck with restoring your device, at all?
I'm in a somewhat similar predicament, myself... I accidently Wrote a backup of my NV Data to the EFS... 0_o
The log of the process showed everything seemingly going well... After rebooting, however... Well, it never did...
Now I can't get into Recovery, ODIN, Normal boot, nor will plugging it in even charge the battery(No screen/led response)...
I see QHUSB_BULK under Unknown Devices (Win7-Ult-SP1_x32)... Can't for the Life of me find the drivers, though...
In fact, reliable old Google even only returns 5 results relevant to said driver, each of which being a post in this thread =D lmao... (so prolly will be 6 results, once I submit this post) But yeah, I'm at a complete loss....
I hope you were able to find a solution for your device. And I hope someone can help discover/produce one for mine as well...
Thank you, XDA and all it's Dev's/Members...
M1k3Carson1369 said:
Hey, Any luck with restoring your device, at all?
I'm in a somewhat similar predicament, myself... I accidently Wrote a backup of my NV Data to the EFS... 0_o
The log of the process showed everything seemingly going well... After rebooting, however... Well, it never did...
Now I can't get into Recovery, ODIN, Normal boot, nor will plugging it in even charge the battery(No screen/led response)...
I see QHUSB_BULK under Unknown Devices (Win7-Ult-SP1_x32)... Can't for the Life of me find the drivers, though...
In fact, reliable old Google even only returns 5 results relevant to said driver, each of which being a post in this thread =D lmao... (so prolly will be 6 results, once I submit this post) But yeah, I'm at a complete loss....
I hope you were able to find a solution for your device. And I hope someone can help discover/produce one for mine as well...
Thank you, XDA and all it's Dev's/Members...
Click to expand...
Click to collapse
Nothing yet....and I'm looking everywhere
for a system dump of the T-Mobile note 3, so I can maybe find the files needed for the fix.
This is practically a cry for help after i searched for hours.
Model: Sm-n910P
Software version : Unknown
Android : 4.4.4
Baseband: Unknown
build: PVPU1ANK2
Stock recovery
(if anything else helps just ask)
Problem first: My note 4 has no network of any kind (wifi doesnt start , doesnt recognize sim card )
When i try attaching a usb cable i get Device is not recognized (checked drivers, cables so its software and it's the mobile)
The only communication with the device is via the SD Card.
Tried flashing a stock 4.4.4 via stock recovery. Nope! It says Update from external card is disabled.
I'm looking for a way to root , or flash anything.
Every thought, suggestion, idea is welcomed.
armandomulla said:
This is practically a cry for help after i searched for hours.
Model: Sm-n910P
Software version : Unknown
Android : 4.4.4
Baseband: Unknown
build: PVPU1ANK2
Stock recovery
(if anything else helps just ask)
Problem first: My note 4 has no network of any kind (wifi doesnt start , doesnt recognize sim card )
When i try attaching a usb cable i get Device is not recognized (checked drivers, cables so its software and it's the mobile)
The only communication with the device is via the SD Card.
Tried flashing a stock 4.4.4 via stock recovery. Nope! It says Update from external card is disabled.
I'm looking for a way to root , or flash anything.
Every thought, suggestion, idea is welcomed.
Click to expand...
Click to collapse
Never been OTA updated to lollipop OE1? That one doesn't allow downgrading to older versions.
Device not recognized with USB in what mode and operation? Security protocols for KitKat and Lollipop are restricted. Device should be recognized in custom recovery or download mode. Did you try Odin? Power down, download mode and flash the NK2 stock tar. If you're still having problems ##786#. Still having issues, try the NIE stock tar. Make sure you power down before flashing stock tars. Link to KitKat tars mentioned above; follow OP, post 1 for instructions.
http://forum.xda-developers.com/showthread.php?p=56853341
For root, you need CF Auto Root for Note 4. You can also try TWRP Manager for custom recovery. It's in Google Play. But you don't have to root to flash in Odin. Samsung KIES is alternate method for restoring factory firmware or updates but some are confused by the serial number request; not recognized. Haven't tried it myself.
Sent from my SM-N910P using Tapatalk
Tx for the reply.
Device is not recognized in neither mode (normal, download or recovery).
I tried ##786# but i dont know my msl and i cant find a wy to get it (im outside the US so the phone is not activated). I tried some "msl reader find my msl" programs but they cant get it. Any1 has some apk that may work in my case?
As for the flashing as I stated all I need is a way to flash stock but i cant get the PC to recognize the phone so im stuck.
EDIT 1 As far as I know never been updated (bought the phone in ebay)
I don't know if there's anything that can be done but get a refund. Sounds like you bought a brick. Was it always a brick?
Did you try another USB port? Try the rear port. If not, try a hard reset: wipe cache and dalvik and factory reset and try to reboot. Long shot would be a hard reset and OB7 update.zip; unless it's completely stock, the update will be rejected. But I'm thinking that can no longer just be placed on external sdcard. That may have to placed on the file system as if the phone downloaded it, itself.
It's safer to hard reset. If not rebooting to normal operation, time to pursue a refund.
Sent from my SM-N910P using Tapatalk
So I was thinking about the situation you're in. I recalled the phone can be unlocked to use internationally on 3G only. Is it unlocked? It would also
need to set your carrier APN/Access points to get data.
If you own the phone, Sprint will give you the MSL number. Sprint can help unlock it and there's also this method but I don't know much about about it. There's also the hard reset method that can be done within settings.
Here's a method that was requested with a pledged bounty. But try Sprint first.
http://forum.xda-developers.com/spr...print-samsung-unlocker-unlock-sprint-t2928250
My initial impression was phone is bricked but not sure if a locked phone's WiFi is bound to regional USA that would cause WiFi connection issues? It's still possible the USB issue is not using a USB 2.0 port or a bad cable. It may not be bricked. Try reinstalling driver and/or another PC.
Sent from my SM-N910P using Tapatalk
Well I tried everything u mentioned , full factory restore, wipe everything. I even tried update from external (since stock has no option for updating from the internal sd) but i get an error (update from external storage is disabled). The phone is practically a brick for the network part but I'm not sure I can return it back in the states as I'm in Europe. Any way i can root via some apk ?
armandomulla said:
Well I tried everything u mentioned , full factory restore, wipe everything. I even tried update from external (since stock has no option for updating from the internal sd) but i get an error (update from external storage is disabled). The phone is practically a brick for the network part but I'm not sure I can return it back in the states as I'm in Europe. Any way i can root via some apk ?
Click to expand...
Click to collapse
I didn't think the root is possible without Odin for either the custom recovery or root.
eBay return practice would be to notify seller of issue. If no response, contact eBay.
Sent from my SM-N910P using Tapatalk
armandomulla said:
Well I tried everything u mentioned , full factory restore, wipe everything. I even tried update from external (since stock has no option for updating from the internal sd) but i get an error (update from external storage is disabled). The phone is practically a brick for the network part but I'm not sure I can return it back in the states as I'm in Europe. Any way i can root via some apk ?
Click to expand...
Click to collapse
Wouldnt the entire phone be soft-bricked (not just the network part) if you did the factory reset and wiped your phone but cant get the cable to recognize your phone on your pc ???
Or is that your current situation?
Well everything but network works. I can install apk's from sdcard, open apps etc. Next thing is the screen just got black and is not giving signs of life (didn't do anything it was charging) so it's going in a repair shop. Thanks everyone for the efforts. Case may be considered closed.
armandomulla said:
Well everything but network works. I can install apk's from sdcard, open apps etc. Next thing is the screen just got black and is not giving signs of life (didn't do anything it was charging) so it's going in a repair shop. Thanks everyone for the efforts. Case may be considered closed.
Click to expand...
Click to collapse
Well, good luck. Hope it works out for you.
As an after thought, have you tried connecting another Samsung phone to the computer?
jhill110 said:
Well, good luck. Hope it works out for you.
As an after thought, have you tried connecting another Samsung phone to the computer?
Click to expand...
Click to collapse
Thanks and yes my other Note 4 connects just fine