Attend XDA's Second Annual Developer Conference, XDA:DevCon 2014!
5,731,698 Members 49,369 Now Online
XDA Developers Android and Mobile Development Forum

[UPDATE 12/24/13 ] SOLVED! Hard-bricked? Un-hard brick using sd card SM-N900T/N9005

Tip us?
 
msmercy42
Old
(Last edited by msmercy42; 25th December 2013 at 10:48 AM.)
#1  
Senior Member - OP
Thanks Meter 24
Posts: 140
Join Date: Nov 2013

 
DONATE TO ME
Post [UPDATE 12/24/13 ] SOLVED! Hard-bricked? Un-hard brick using sd card SM-N900T/N9005

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...

Quote:
Originally Posted by aiti1980 View Post
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?
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!XLL6Xy...z5RIQ-fQc5Ctxk

Thanks to aiti1980 for the above SM-N9005 Unbrick.img upload! ENJOY
The Following 15 Users Say Thank You to msmercy42 For This Useful Post: [ Click to Expand ]
 
NeoAndroid
Old
#2  
NeoAndroid's Avatar
Senior Member
Thanks Meter 74
Posts: 352
Join Date: Jun 2010
Location: Chandler
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
 
msmercy42
Old
#3  
Senior Member - OP
Thanks Meter 24
Posts: 140
Join Date: Nov 2013

 
DONATE TO ME
Quote:
Originally Posted by NeoAndroid View Post
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
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?
 
chstewart
Old
#4  
chstewart's Avatar
Member
Thanks Meter 16
Posts: 46
Join Date: Mar 2012
Location: Lehi

 
DONATE TO ME
Quote:
Originally Posted by msmercy42 View Post
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?
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
 
msmercy42
Old
#5  
Senior Member - OP
Thanks Meter 24
Posts: 140
Join Date: Nov 2013

 
DONATE TO ME
Quote:
Originally Posted by chstewart View Post
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

The help is much appreciated, however I cannot turn on the phone at all...
 
chstewart
Old
#6  
chstewart's Avatar
Member
Thanks Meter 16
Posts: 46
Join Date: Mar 2012
Location: Lehi

 
DONATE TO ME
Quote:
Originally Posted by msmercy42 View Post
The help is much appreciated, however I cannot turn on the phone at all...
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
The Following User Says Thank You to chstewart For This Useful Post: [ Click to Expand ]
 
msmercy42
Old
(Last edited by msmercy42; 17th November 2013 at 10:42 PM.)
#7  
Senior Member - OP
Thanks Meter 24
Posts: 140
Join Date: Nov 2013

 
DONATE TO ME
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!
 
d12unk13astard
Old
#8  
d12unk13astard's Avatar
Senior Member
Thanks Meter 603
Posts: 2,180
Join Date: Aug 2010
Location: Bakersucks
Try with kies, best option as it will firmware reset your device back to stock.

Sent from my SM-N900T using xda premium
Current Device: T-Mobile Note 3 (SM-N900T)

Past Devices:

Sprint Note 2 (L900) - Hanging on to
Sprint Galaxy S2 - Sold
T-Mobile G2X (P-999) - Sold
T-Mobile Mytouch4G - Sold
T-Mobile G1 (Dream) - Sold
The Following User Says Thank You to d12unk13astard For This Useful Post: [ Click to Expand ]
 
msmercy42
Old
#9  
Senior Member - OP
Thanks Meter 24
Posts: 140
Join Date: Nov 2013

 
DONATE TO ME
Quote:
Originally Posted by d12unk13astard View Post
Try with kies, best option as it will firmware reset your device back to stock.

Sent from my SM-N900T using xda premium
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
Old
(Last edited by msmercy42; 14th December 2013 at 07:28 AM.)
#10  
Senior Member - OP
Thanks Meter 24
Posts: 140
Join Date: Nov 2013

 
DONATE TO ME
Quote:
Originally Posted by msmercy42 View Post
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.

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.

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes