Develop Bugs

[Q] Samsung galaxy SIII hard bricked will not boot but ODIN can recognize it

Samsung galaxy SIII hard bricked will not boot no power, but ODIN 1.85 can recognize it, (not the new Odins), when I try to re-flash it with Odin I get stuck at setupConnection..
any help? can I use the small USB mod

If you don't mind me asking, how you brick your phone?
Sent from my SGH-T999 using xda app-developers app

i have the same problem i used the Odin3 v1.85 and installed CF-Root-SGS3-v6.4 zip but it failed. so then i tried to reboot it and said firmware update encountered an issue and something else. then i looked up how to unbrick and the post said to downloaded the zip CF-Insecure-SGS3_XX_NEE_ALE8-v1.2 and used Odin to install now i got nothing but a black screen buy it will go into download mode and Odin read it

You're not hard bricked if Odin can read your phone. Reboot your computer then reconnect and flash a stock rom to be safe.

chubby1_8888 said:
i have the same problem i used the Odin3 v1.85 and installed CF-Root-SGS3-v6.4 zip but it failed. so then i tried to reboot it and said firmware update encountered an issue and something else. then i looked up how to unbrick and the post said to downloaded the zip CF-Insecure-SGS3_XX_NEE_ALE8-v1.2 and used Odin to install now i got nothing but a black screen buy it will go into download mode and Odin read it
Click to expand...
Click to collapse
If I'm not wrong ODIN uses TAR files and not ZIP files. Try unziping and see if there is a TAR file if there is then thats what you have to use in ODIN.

Same as OP's phone
Sprint s3 flash pacman JB and google apps the went to reboot recovery ask to reflash su yes phone powered off and no coming back on Odin does detect it on com05 when I plug it in but anything I try to do just says waiting on connection, will not go into recovery or download modes. is there anything I can do to fix it? kies or anything? and I edited the updater scripts to be able to flash pacman because every rom I tried would fail with error 7............ please help

Kevinreid1 said:
Sprint s3 flash pacman JB and google apps the went to reboot recovery ask to reflash su yes phone powered off and no coming back on Odin does detect it on com05 when I plug it in but anything I try to do just says waiting on connection, will not go into recovery or download modes. is there anything I can do to fix it? kies or anything? and I edited the updater scripts to be able to flash pacman because every rom I tried would fail with error 7............ please help
Click to expand...
Click to collapse
Do you get a message when you plug it into your computer? Does the red LED turn on? Editing the scripts is dangerous if you don't know what you are doing!

serio22 said:
Do you get a message when you plug it into your computer? Does the red LED turn on? Editing the scripts is dangerous if you don't know what you are doing!
Click to expand...
Click to collapse
followed the guides about it just removed from top to quotes dealing with checking versions of device.

Kevinreid1 said:
followed the guides about it just removed from top to quotes dealing with checking versions of device.
Click to expand...
Click to collapse
I'm not saying that was the problem or that you did it wrong, but maybe the ROM was forced to flash and was truly not compatible or was corrupt, bricks are highly likely to occur in this case

serio22 said:
I'm not saying that was the problem or that you did it wrong, but maybe the ROM was forced to flash and was truly not compatible or was corrupt, bricks are highly likely to occur in this case
Click to expand...
Click to collapse
The roms I have downloaded are supposed to be for Sprint s3 I was running stock JB 4.3 if that makes any difference, any help on what to do know, thinking of trying the unbrick mmc card trick .... idk what else to do... thanks : ) and something went wrong somewhere for sure... lol I also found out my exact model number if that helps. SPH-L710MBBSPR again thanks for you responses..

Ok, a few things I noticed....
1. You are using a very old version of Odin. I recommend only using 3.07 or 3.09.
2. The COM port box is yellow, which probably was trying to caution you about something.
3. You have a Sprint model S3. This is the T-Mobile S3 forum.
4. You have a Sprint S3, but were trying to flash old T999 firmware! This simply will not work, and if it were to flash, insta-brick!
What you need to do is start using the Sprint forums. Only flash items you find in those forums, and nothing else. While some of our roms might flash and boot on yours, they will never function very well. This is one of the things the asserts in an updater script are intended to protect against.
Finally, just a bit of posting advice. Please use proper punctuation. Small mistakes are ok, but posting with no punctuation at all just makes it difficult for people to read, and many will just close the thread and move to the next without bothering to help.
---------- Post added at 02:28 AM ---------- Previous post was at 02:25 AM ----------
Oops! Just realized the pic in the op wasn't yours! But still, theyre all good points you should check before flashing. Also make sure kies is uninstalled or disabled on your computer.
But most importantly, you need to be in the Sprint forums. We can help a bit here, but you need to ONLY use stuff from your devices forum. And a lot of it we simply may not be familiar with.
Good luck!

DocHoliday77 said:
Ok, a few things I noticed....
1. You are using a very old version of Odin. I recommend only using 3.07 or 3.09.
2. The COM port box is yellow, which probably was trying to caution you about something.
3. You have a Sprint model S3. This is the T-Mobile S3 forum.
4. You have a Sprint S3, but were trying to flash old T999 firmware! This simply will not work, and if it were to flash, insta-brick!
What you need to do is start using the Sprint forums. Only flash items you find in those forums, and nothing else. While some of our roms might flash and boot on yours, they will never function very well. This is one of the things the asserts in an updater script are intended to protect against.
Finally, just a bit of posting advice. Please use proper punctuation. Small mistakes are ok, but posting with no punctuation at all just makes it difficult for people to read, and many will just close the thread and move to the next without bothering to help.
---------- Post added at 02:28 AM ---------- Previous post was at 02:25 AM ----------
Oops! Just realized the pic in the op wasn't yours! But still, theyre all good points you should check before flashing. Also make sure kies is uninstalled or disabled on your computer.
But most importantly, you need to be in the Sprint forums. We can help a bit here, but you need to ONLY use stuff from your devices forum. And a lot of it we simply may not be familiar with.
Good luck!
Click to expand...
Click to collapse
Thank you.. I knew I was in the wrong forum and that is why I said my s3 was a Sprint device... My problem however was the same exact problem. I got it fixed with file from another forum, while follow info from yet another forum, the file that worked for me was HomefixSprint_S3_L710.img the debrick_sph_l710.img would not work for me. I used win32diskimager and burned .img file to class 10 32gb card, stuck it in went in to download mode and used odin to write firmware file... Anyway back up any running.. I didn't download any t-mobile roms or anything that wasn't for the Sprint S3, what I did do was try and load an older JB rom that was under V4.3, it wasn't that long ago when a person could flash any android version one wished, it looks like Samsung is getting as bad as Apple you can move up but not back. Any tips on how to safely downgrade? Anyway thanks for taking the time to respond. : ) Cause no one has in the Sprint S3 forum yet.

Kevinreid1 said:
it wasn't that long ago when a person could flash any android version one wished, it looks like Samsung is getting as bad as Apple you can move up but not back. Any tips on how to safely downgrade?
Click to expand...
Click to collapse
No, Samsung is not turning into apple, there is a reason you cannot downgrade from a Knox bootloader. And to downgrade, with this device we can just flash an older ROM and it will work, maybe its different with the Sprint variant? Try to search in their forums if you haven't already

[Q] Odin doesn't detect my N7100 in download mode!

Yes I done the research and didn't find a working solution.
My Note 2 experienced SDS and had the motherboard replaced under warranty by the Samsung service center. Before repairs there was no issue and I flashed a couple things with PC Odin. After getting my note back I intended to flash an international 4.1.2 version to get rid of the Arabic based ROM and to minimize the chance of another SDS. Upon checking found out I still have the insane chip.
Unfortunately when I connected my note to PC, Odin didn't recognize it. I tried:
another Odin version
reinstalling drivers
another USB cable
and quite a few other things i found in other threads
To make it more confusing there is no issue connecting the note in any other mode to the PC. I shows up in explorer as GT-N7100 and it connects to Kies without issues giving all the sync, backup etc...... options.
As a last resort I hope I missed something somewhere and maybe somebody can point out where........

MutantWizard said:
Yes I done the research and didn't find a working solution.
My Note 2 experienced SDS and had the motherboard replaced under warranty by the Samsung service center. Before repairs there was no issue and I flashed a couple things with PC Odin. After getting my note back I intended to flash an international 4.1.2 version to get rid of the Arabic based ROM and to minimize the chance of another SDS. Upon checking found out I still have the insane chip.
Unfortunately when I connected my note to PC, Odin didn't recognize it. I tried:
another Odin version
reinstalling drivers
another USB cable
and quite a few other things i found in other threads
To make it more confusing there is no issue connecting the note in any other mode to the PC. I shows up in explorer as GT-N7100 and it connects to Kies without issues giving all the sync, backup etc...... options.
As a last resort I hope I missed something somewhere and maybe somebody can point out where........
Click to expand...
Click to collapse
This may help..
http://forum.xda-developers.com/showthread.php?t=1687590
GT N7105 with XDA Premium......that is all......

bearusa said:
This may help..
http://forum.xda-developers.com/showthread.php?t=1687590
GT N7105 with XDA Premium......that is all......
Click to expand...
Click to collapse
Thanks mate, read a good portion of the thread and have to admit its way over my head so couldnt figure out how it relates but it did remind me of mskip's Toolkit. So I:
unisntalled Kies
uninstalled Samsung drivers
ran CC cleaner
ran registry cleaner
rebooted
Then I started from scratch with the Toolkit and got lucky. Rooted and twrp installed. Tonight or tomorrow will continue with the flashing a non-Arabic 4.1.2 ROM. Got to buy a beer for mskip!!!
SOLUTION
By the way just figured out something that in all the searching I have not seen anybody mention. I probably missed it! All this time I am following instructions to start Odin then boot the phone into download mode and then connect to PC and it still doesn't work even after I managed to do some flashing through the Toolkit. Then I had an idea. With note still in download mode and connected to the PC I shut down Odin and restarted it, guess what there is light and it's blue, it worked!!!

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

[Q]SM-T520 Rooted for Firewall but no Screen mirroring anymore :(

Hi there Guys
I´m total new on Android.Have my SM-T520 since two Weeks know.My last Boyfriend teached me alot into
the Computer-things.BtW, if you think Im writing stupid ... im from Germany LoL ... My english has
rotten a little bit. So sorry ... have merci please with me.
So ... I was told: Every Computer online needs a Firewall.I searched for an APP for my new Tablet ...
... found one, but it want´s a root? Searched for ROOT and find:
androidpulp.blogspot.de/2014/03/how-to-root-samsung-galaxy-tab-pro-101
I did everything exactly written ... was very nervous " should I? Or better not? Uhhh ... This WARNINGS
My new sweet Tablet! But I did it !! and it WORKS !!! My biggest Computer-thing I ever done. :laugh: :good:
So, I put this CF-Auto-Root-picassowifi-picassowifixx-smt520.tar.md5 File onto my Tablet.The "Root-Test"
was the installing of the AFWall+ Friewall ... It works! Great ! I rooted my Tab! Alone by myself !!
Told everyone from my Adventure the next Days.
But, I brought the Tab for relaxed surfing on my Sofa? (Couch?) and or streaming Movies from Sites to my
Samsung Smart TV.This SCREEN MIRRORING thing.I tested it a little BEFORE my rooting.I worked great.Now
it breaks up with a "Hardware Error" in the end of the connecting process.
So, searched again for that and found out that this Error came from the Root ... from the "Root-Counter",
I think? Searched again ... TRIANGLE AWAY app was found and installed.When I press RESET FLASH COUNTER
the app told me its resseting.But the counter dont go to zero ?? The last message told me
"... make sure you dont running a custom kernel ?? or custom recovery ..." ??
The TRIANGLE AWAY Flash Counter Status show to me:
Cuurent status:
Counter 1
Binary Custom
Device SM-t520
System Offical
When I put my Tab in this Download Mode? It says "ODIN Mode" itself?
ODIN MODE
PRODUCT NAME: SM-T520
CURRENT BINARY: Custom
SYSTEM STATUS: Offical
KNOX WARRENTY VOID: 1
AP SWREV: A1
I searched nearly a week ... landing a lot in this community here ... register on SAMMOBILE ...
thought that this File here is original:
sammobile.com/firmwares/3/?download=32752
Model: SM-T520
Model name: GALAXY TabPRO 10.1 Wi-Fi
Country: Germany
Version: Android 4.4.2
Changelist: 1977750
Build date: Tue, 24 Jun 2014 08:31:35 +0000
Product Code: DBT
PDA: T520XXUANF4
CSC: T520DBTANF1
MODEM: T520XXUANF4
But ... the File CF-Auto-Root-picassowifi ... was 21 MB big the File on SamMobile is 1,2 GB!! big.
I think I not right here.Im totaly confused now.Want to do this thing alone with no help from my Workmates.
It starts so good but now Im out of order.
ROM, Kernel, Firmware, Recovery ... all that I found with Google ?? I think I reached my Limit here.
SO, the Binary is the thing to do? Or ?? Is that a Kernel, ROM, Firmware or Recovery ??? This thing must be
original? Original to be able to reset the Counter to Zero and can do that SCREEN MIORRORING again?
My wish would be:
Keep the Root and the Firewall and also put the Counter to zero to be able to see the picture of my Tab on
my Samsung TV again.
PLEASE ... what kind of File do I need now?What I have to do with that?Is it possible to keep Firewall working
and ScreenMirroring?
Please does someone of you have a LINK that help me? What is a BINARY, please?
I THANK YOU all for reading my looong Story :good::good: Maybe someone knows what I have do do?
Greeting from Germany
Your Nina

too loong ? XD
Hmmmm .... to put it in short ...
Is it possible to have a rooted Tab AND use the
Samsung ScreenMirroring Funktion?
Please, how can I replace the custom BINARY with a stock Binary that
runs with my rooted system?
A Link or a good Searchword for Mrs.Google would help me so much.
Have a nice Evening
Greeting from Nina

AndroidNeuling said:
Hmmmm .... to put it in short ...
Is it possible to have a rooted Tab AND use the
Samsung ScreenMirroring Funktion?
Please, how can I replace the custom BINARY with a stock Binary that
runs with my rooted system?
A Link or a good Searchword for Mrs.Google would help me so much.
Have a nice Evening
Greeting from Nina
Click to expand...
Click to collapse
based on my experience with my other Smasung phones, yes it should work, as long as you are still running Stock firmware.

THANK YOU
xdm9mm said:
based on my experience with my other Smasung phones, yes it should work, as long as you are still running Stock firmware.
Click to expand...
Click to collapse
Thank you for your Answering
So,it may possible to keep root and firewall AND
use the screen-mirroring?
My problem is, what file do i need for that?
LoL ... I dont know the exactly name of and sadly l cant find out what kind of File?
A kernel, a firmware, a recovery or a rom?
I need a binary right? Or not?
What is a binary ... a rom kernel firmware or recovery?
I searched for hours now but cound find a Answer. :crying:
So, you mean I need a Firmware?
Please, do you have a Link? For the file and a how to do,maybe?
The Data is posted in my looong Story in my first post.
It starts so well and ended in a mission impossible for me now.
I thought someone here did it before with a sm-t520 10.0 pro tab.
Maybe ??
Have a Nice Day
your Nina

AndroidNeuling said:
Thank you for your Answering
So,it may possible to keep root and firewall AND
use the screen-mirroring?
My problem is, what file do i need for that?
LoL ... I dont know the exactly name of and sadly l cant find out what kind of File?
A kernel, a firmware, a recovery or a rom?
I need a binary right? Or not?
What is a binary ... a rom kernel firmware or recovery?
I searched for hours now but cound find a Answer. :crying:
So, you mean I need a Firmware?
Please, do you have a Link? For the file and a how to do,maybe?
The Data is posted in my looong Story in my first post.
It starts so well and ended in a mission impossible for me now.
I thought someone here did it before with a sm-t520 10.0 pro tab.
Maybe ??
Have a Nice Day
your Nina
Click to expand...
Click to collapse
1. Unfortunately, the Knox counter cannot be reset at this time.
2. If you have not installed any recovery, or other ROMs, Kernel, then you are running STOCK firmware.
3. Have you tried to reset your device and see if mirroring works? This is what I did with my S4 before and it worked, but I don't really know with the Tab pro because i have not rooted it as I want to use Knox.
4. If after you have reset your device, and screen mirroring does not work, try to download a STOCk firmware from www.samfirmware.com or www.samsung-updates.com and flash it to your device using ODIN - this is run on your COMPUTER with your Tab pro connected via USB cable. This will UNROOT your device. Then try to use screen mirroring again and see if it works. If screen mirroring works, then it means you can't root your devic if you want to use screen mirroring.
5. There are free firewalls on google play, but I have not used any of them so i cannot comment which one is the best.
I suggest before you make changes to your Tab Pro from now on, go and read more about rooting, flashing ROMs, flashing RECOVERY... it is best NOT to RUSH what you want to do as an ERROR on your part might cause more problems.

a lot of THANKS
xdm9mm said:
1. Unfortunately, the Knox counter cannot be reset at this time.
2. If you have not installed any recovery, or other ROMs, Kernel, then you are running STOCK firmware.
3. Have you tried to reset your device and see if mirroring works? This is what I did with my S4 before and it worked, but I don't really know with the Tab pro because i have not rooted it as I want to use Knox.
4. If after you have reset your device, and screen mirroring does not work, try to download a STOCk firmware from or and flash it to your device using ODIN - this is run on your COMPUTER with your Tab pro connected via USB cable. This will UNROOT your device. Then try to use screen mirroring again and see if it works. If screen mirroring works, then it means you can't root your devic if you want to use screen mirroring.
5. There are free firewalls on google play, but I have not used any of them so i cannot comment which one is the best.
I suggest before you make changes to your Tab Pro from now on, go and read more about rooting, flashing ROMs, flashing RECOVERY... it is best NOT to RUSH what you want to do as an ERROR on your part might cause more problems.
Click to expand...
Click to collapse
Thank you !
I will test that RESET with TriangleAway and then test ScreenMirroring this afternoon. Nice Idea :good: Hope it works.
I only put CF-Auto-Root-picassowifi-picassowifixx-smt520.tar.md5 one Time to my Tablet and it was the only
thing I put on with Odin.
My Problem with this Firmware-Download-Sites samfirmwar is, that my File:
Model: SM-T520 PDA: T520XXUANF4
(I cant put a Link in my Postings)
is too big!! It´s 1,2GB big and the File i did (CF-Auto-Root-picassowifi-picassowifixx-smt520.tar.md5) is only
21MB.Could that be right?? My only nonStock-File on my Tab is the BINARY, as TriangleAway and
the Download Page said.
I read a lot last two weeks ... i looked for me like theres no solution at that Time.
Couldn't find a Posting like "rooted SM-T520 WITH SreenMirroring"
Maybe my Tab its to new? Read from Lib-Files that must be changed but not for the SM-T520.
Thanks for your help !! I will test your Point 3 a little later. Hope ...
Have a nice Day
Greetz from Nina

AndroidNeuling said:
Thank you !
I will test that RESET with TriangleAway and then test ScreenMirroring this afternoon. Nice Idea :good: Hope it works.
I only put CF-Auto-Root-picassowifi-picassowifixx-smt520.tar.md5 one Time to my Tablet and it was the only
thing I put on with Odin.
My Problem with this Firmware-Download-Sites samfirmwar is, that my File:
Model: SM-T520 PDA: T520XXUANF4
(I cant put a Link in my Postings)
is too big!! It´s 1,2GB big and the File i did (CF-Auto-Root-picassowifi-picassowifixx-smt520.tar.md5) is only
21MB.Could that be right?? My only nonStock-File on my Tab is the BINARY, as TriangleAway and
the Download Page said.
I read a lot last two weeks ... i looked for me like theres no solution at that Time.
Couldn't find a Posting like "rooted SM-T520 WITH SreenMirroring"
Maybe my Tab its to new? Read from Lib-Files that must be changed but not for the SM-T520.
Thanks for your help !! I will test your Point 3 a little later. Hope ...
Have a nice Day
Greetz from Nina
Click to expand...
Click to collapse
Chainfire doesn't flash a new system. It replaces your recovery, then adds some files to root your existing /system, and then replaces your recovery with a stock version (which may be different than the stock version your started with, but is a Samsung recovery at least).
That's why it is so much smaller.
I'm guessing here because I have not entirely figured out what Samsung has done with their Digital Rights Management stack. But, screen mirroring may have issues because it may require DRM keys (probably hdcp keys) and by tripping Knox it may be going from DRM level 1 for which it has keys to DRM level 3 for which the device may not have usable keys.
I agree with the recommendation to try using Odin to undo everything except tripping the Knox counter. That's your best shot.

crpalmer said:
Chainfire doesn't flash a new system. It replaces your recovery, then adds some files to root your existing /system, and then replaces your recovery with a stock version (which may be different than the stock version your started with, but is a Samsung recovery at least).
That's why it is so much smaller.
I'm guessing here because I have not entirely figured out what Samsung has done with their Digital Rights Management stack. But, screen mirroring may have issues because it may require DRM keys (probably hdcp keys) and by tripping Knox it may be going from DRM level 1 for which it has keys to DRM level 3 for which the device may not have usable keys.
I agree with the recommendation to try using Odin to undo everything except tripping the Knox counter. That's your best shot.
Click to expand...
Click to collapse
LoL
Sounds like you are much into it.
But I understand nearly half what you write about DRM and so. But THANKS for your Time.
Because of you I know now why it is so big.
I started the 1.2GB Download at the End of my last Posting ... still 6 hours left :silly: to finish. 30kb sec
So, when Download is ready and I put it with Odin on my Pad ... is the complete System new then?
The Binary is then Stock or offical and I can put the Counter with TriangleAway to zero?
Read this morning that this wont go because its now Hardware based. a fuse or so.
So I do the big File on my Pad to get the complete stock System back and the ScreenMirroring option running?
Sorry for my stupid ... I read really a lot ... but its also a lot of "ways" and "to do" written out there.
The Test resetting with TriangleAway and test the ScreenMirroring didn't worked here.
The Pad is scanning long Time but couldn't find the TV.Yes ... it´s in the allowed List in Menu.
Did the same as before the root.But the Idea was good.
In all the "how to root" Sites in the Internet should written that some functions wound´t work after root as Warning ... ... maybe ... special for rooters like me
I read we can unroot the Pad with SU.Looked in the Menu ... there´s really a Point called unroot.
But that wound´t bring ScreenMirroring back or? Sounds to easy, or?
So, see you next Time
Bye for now your Nina

This ****ty DownloadSites!
Started the "little" GB-Download ... twice.
After Hours ! the Download interrupted ...
It's so slow and takes so looong.
Hope I will get it together ... maybe the Day will come. :fingers-crossed:
Maybe ....
... someone finds out a HowToDo in this Time. L o L
Have a nice one , Bye,Nina

Wow 350 KB sec
AndroidNeuling said:
This ****ty DownloadSites!
Started the "little" GB-Download ... twice.
After Hours ! the Download interrupted ...
It's so slow and takes so looong.
Hope I will get it together ... maybe the Day will come. :fingers-crossed:
Maybe ....
... someone finds out a HowToDo in this Time. L o L
Have a nice one , Bye,Nina
Click to expand...
Click to collapse
Holla die WaldFee ... now I can download 10 Times faster.
Samsung Tv we come
CU Nina

xdm9mm said:
1. Unfortunately, the Knox counter cannot be reset at this time.
2. If you have not installed any recovery, or other ROMs, Kernel, then you are running STOCK firmware.
3. Have you tried to reset your device and see if mirroring works? This is what I did with my S4 before and it worked, but I don't really know with the Tab pro because i have not rooted it as I want to use Knox.
4. If after you have reset your device, and screen mirroring does not work, try to download a STOCk firm... and flash it to your device using ODIN - this is run on your COMPUTER with your Tab pro connected via USB cable. This will UNROOT your device. Then try to use screen mirroring again and see if it works. If screen mirroring works, then it means you can't root your devic if you want to use screen mirroring.
5. There are free firewalls on google play, but I have not used any of them so i cannot comment which one is the best.
I suggest before you make changes to your Tab Pro from now on, go and read more about rooting, flashing ROMs, flashing RECOVERY... it is best NOT to RUSH what you want to do as an ERROR on your part might cause more problems.
Click to expand...
Click to collapse
totally agree
i think our german girl must have stuffed something up during flashing
flash back it to the original stock rom using odin and keep it as unrooted. my wife has an unrooted p600 and to honest, i cant see any point to root her device at all. based on what she or probably this girl wants to use it for.

Note 7 SM-N930F bricked / / need help!

I flashed TWRP with odin.
After that I was not able to boot or start recovery.
Only download mode is possible.
In download mode it shows
warranty void 1 (0x030c)
I also cannot flash anything in odin anymore.
After initializing, it immidiatly stops with the error:
<ID:0/004> FAIL! (DeviceInfo)
Can anybody help me, how to get this beautiful phone running again?
Thanks so much!
MOD EDIT:
This member is talking about this.
TEKHD

bill340 said:
I flashed TWRP with odin.
After that I was not able to boot or start recovery.
Only download mode is possible.
In download mode it shows
warranty void 1 (0x030c)
I also cannot flash anything in odin anymore.
After initializing, it immidiatly stops with the error:
<ID:0/004> FAIL! (DeviceInfo)
Can anybody help me, how to get this beautiful phone running again?
Thanks so much!
MOD EDIT:
This member is talking about this.
TEKHD
Click to expand...
Click to collapse
try to download the firmware from http://samfirm.net/threads/official-rom-full-galaxy-note-7-sm-n930f-n930fxxu1apg7-xxv-23-07-2016.98/ and try to flash via odin.
Never ever try to flash anything till the time there is no evidence of success.

I tried that, but the problem is that I always get this error in Odin when trying to flash...

Did you check OEM unlock before you flash as per the instructions? not doing so will result in a boot loop.

Try different cable and USB port. I had trouble with both that had me running in circles.
Sent from my SM-N910T using Tapatalk

Yes, I did OEM unlock before the flash.
Different cable and USB port makes no difference...

Usually when I have issues I try to uninstall all drivers related to phones and only install the one I need. Then after a restart and forcing the phone into Odin I'm able to flash without issues.

It might be failing because of a Partition size error. Have you tried the Samfirm Tool to download a firmware from your region?
Have you tried Emergency Device Recovery from SmartSwitch PC ?
Also, I'm doubtful whether this is a new trick up from Samsung's sleeve. This Phone is still new, so it's quite a learning process. Maybe Samsung has implemented something to block these unofficial flash attempts. However I thank you taking the risk and trying the recovery first.

Can you help me, where I can get this?
Have you tried Emergency Device Recovery from SmartSwitch PC ?

bill340 said:
Can you help me, where I can get this?
Have you tried Emergency Device Recovery from SmartSwitch PC ?
Click to expand...
Click to collapse
Download and install SmartSwitch for PC. Then follow this Video.

I really have no luck here...
Any idea?
Googled already, but did not really find anything besides reinstalling...

I dont think theres a fix for this issue yet. There's also no subtantiated literature in the larger cummunity pertaining to rooting the Note 7.
I am guessing this is an additional precaution taken by Samsung therefore the rooting process needs a very specific set of steps in order to circumnavigate the systems Sammy has put in place. The thread itself says WIP, so I applaud you for your courage.
Nonetheless my suggestion is to instead of waiting for an answer which no one can provide, go to Sammy and bull**** to them that u plugged in the computer and it became a brick.
Theres is no possible senario whereby the internet can help you because we know next to nothing about Note 7.
I sincerely hope that you can come out of the situation with a working Note 7 in your hands whilst not burning a hole in your wallet due to the repairs. God-speed my friend, God-speed.

bill340 said:
I really have no luck here...
Any idea?
Googled already, but did not really find anything besides reinstalling...
Click to expand...
Click to collapse
This seems to be an issue in your drivers, Please uninstall all samsung related and flash box related (if exists) in your PC and try installing it again.
Alternatively, you can just walk into a Samsung Care store and get it done while you wait.

I did that already... No luck. I will try on a different pm next.

Bill sad to see this happened to you
I am exactly coming for the same forum and was following the same steps thought u were, but u took one more step forward and flashed the vitanamese firmware, your phone just messed up there. Was actually about to do the same thing but then read your comments. My phone starts but with errors and has battery drainage , i havent lost anything as it is still virgin and havent transfered anything to it yet. Will wait probably 4 to 5 days more for the official firmwares to release and fire it in.
Sorry to say but u had become the test subject...
---------- Post added at 11:07 AM ---------- Previous post was at 11:03 AM ----------
The recovery mode cannot be accessed, no matter how hard you try
Sent from my SM-N920C using XDA Free mobile app

I just was in the Samsung Care Center in Singapore with my bricked phone.
After 1 hour waiting time, a Samsung guy explained me, that they cannot do anything about it, because they don't have parts ? for this phone in Singapore because it was not launched yet and also there is no international warranty on it.
He had no idea about any software recovery or anything and suggested to get back to Dubai, where I got the phone from.
Really a bad Customerservice experience.
I also want to thank all of you for your great help and suggestions!
I think I will send the phone back to the store in Dubai now.

Well tht will be a good choice
But if u give it three more days and wait for the official firmwares to release would save you some time.
I am still following up with it.
Sent from my SM-N920C using XDA Free mobile app

I really doubt, that this will help, since I cannot flash anything in odin. After initialization I always get the error "FAIL (DeviceInfo)"

bill340 said:
I just was in the Samsung Care Center in Singapore with my bricked phone.
After 1 hour waiting time, a Samsung guy explained me, that they cannot do anything about it, because they don't have parts ? for this phone in Singapore because it was not launched yet and also there is no international warranty on it.
He had no idea about any software recovery or anything and suggested to get back to Dubai, where I got the phone from.
Really a bad Customerservice experience.
I also want to thank all of you for your great help and suggestions!
I think I will send the phone back to the store in Dubai now.
Click to expand...
Click to collapse
Same here in (Dubai) Mate, They don't even have the parts, or Tools to open the device up. If you remember me, I screwed up my Note 7 a week back, Just after two days from launch, and I still didn't receive it. They are still unable to sort it out.
I'm sure when a proper firmware for XSG (Dubai - Same as your device) and a proper ODIN is released to flash the Note 7, this will be a piece of a cake. Just hope for the best, As just like you - I too took a leap of faith and did something stupid.
Anyway, Wishing you luck !

I am not sure if this will help....
What happens when you try a older version of Odin?
Its worked for me in the past, with my s6 edge.