Related
Hello.
I used the Toolkit to root my Note 2, and I had to use option 4 on the rooting menu, Install Custom Recovery, Install via Recovery to get it to work. I tried several times via the Odin tool and Twrp recovery, and the phone kept booting into Android Recovery instead of Twrp recovery.
I finally used Odin to flash back to stock ROM that I got here, but, along the way, even though the Toolkit was able to connect to my Note 2, I get the Hardware ID missing, and I cannot connect to it any longer like I could after I installed the initial drivers.
Anything I can do and stay rooted?
Change usb ports or restart your device. Mine did it last night and I fixed it by doing both..
I have the same problem.
Changing ports and restarting in most cases didn't help and only in few cases I managed to access files on the phone via USB.
Any other suggestion how to solve this?
don't use windows..
Ditto
dstenc said:
I have the same problem.
Changing ports and restarting in most cases didn't help and only in few cases I managed to access files on the phone via USB.
Any other suggestion how to solve this?
Click to expand...
Click to collapse
glen4cindy said:
Hello.
I used the Toolkit to root my Note 2, and I had to use option 4 on the rooting menu, Install Custom Recovery, Install via Recovery to get it to work. I tried several times via the Odin tool and Twrp recovery, and the phone kept booting into Android Recovery instead of Twrp recovery.
I finally used Odin to flash back to stock ROM that I got here, but, along the way, even though the Toolkit was able to connect to my Note 2, I get the Hardware ID missing, and I cannot connect to it any longer like I could after I installed the initial drivers.
Anything I can do and stay rooted?
Click to expand...
Click to collapse
I was able to gain root back using the toolkit. I flashed stock rom image I believe the ROM from the factory then flashed back stock recovery. Went back in after I updated and re-rooted to flash the triangle away. Now I need to unroot and after speaking with Sprint Rep on phone and trying a few things they advised me to take it to store to let them try it. I believe ALL of my problems started when I tried to use Mobile Odin Pro to flash the latest update to LJC (should I have been on stock recovery?). It started to flash then stopped and went into CWM recovery which is the recovery that the toolkit flashed. I for some strange reason was going to flash the update from there except I didn't have it in the right place on my sd card (couldn't access it GOD I'm a Dumbass!). God help me cause I'm too stupid to even understand what side loading is let alone how to do it. If some kind soul would take pity on me and pm me I could get a handle on the differences between HTC and Samsung. Anyway need to unroot now. Oh I keep seeing in the flash counter saying 1 but I'm on stock rom with stock kernel and stock recovery how do I get it to zero. Using triangle away. Anyway to check counter with stock recovery?
OH yeah does anyone keep getting "Internal Error Code 1500" in addition to the hardware id is missing?
Thanks to everyone that takes time to help idiots like me. I promise I CAN learn.
Charles
chrisc627 said:
Change usb ports or restart your device. Mine did it last night and I fixed it by doing both..
Click to expand...
Click to collapse
Thank you...Unlike user: dstenc, the above procedure fixed my issue. As has been the case many times, XDA helpful users to the rescue!
:laugh: :good:
Just to report that for now I've found woraround. I've installed old drivers 1.4.103.0 and now both Kies and file access works.
Still looking for final solution with latest drivers.
Could you walk me through your fix?
dstenc said:
Just to report that for now I've found woraround. I've installed old drivers 1.4.103.0 and now both Kies and file access works.
Still looking for final solution with latest drivers.
Click to expand...
Click to collapse
Hi dstenc,
Would you be so kind as too help me do what you did? I don't have kies on my pc, did you get the old drivers from the s3 forum? I would love to give it a shot.
Thanks for any help
Charles
Could you walk me through your fix?
Mods please delete double post sorry
ceabbott2 said:
Hi dstenc,
Would you be so kind as too help me do what you did? I don't have kies on my pc, did you get the old drivers from the s3 forum? I would love to give it a shot.
Thanks for any help
Charles
Click to expand...
Click to collapse
I don't remember link. I googled so you might try that way.
Just FYI, even with older drivers I have sporadic Hardware ID Missing error, but far too less than with the latest version.
I'm posting this to keep it to the top of this board.
This is my second Note 2 in 2 weeks. I returned the first one because it stated Hardware ID missing, so within my first 2 weeks Sprint gave me a new one thinking that it was my phone. While at the Sprint store, and not yet rooted, we installed the unit and removed the unit 15 times to see if we could get it to have the Missing Hardware ID to pop up, it DIDN'T pop up once, so I thought I was good to go.
I came home and did the common root method that uses Galaxy Note 2 Toolbox. I IMMEDIATELY started getting the Missing Hardware ID again.
So now that we have it localized, what could be missing or creating a problem from the root procedure from the Galaxy Note Toolbox 2???
What I find really strange is that many are not experiencing this problem or they are just living with it.
I even tried the USB Switcher that appeared to install and does switch between Mass Storage and MTP, but although my PC makes the upward noise that sounds like it is installing and recognizing the USB Mass Storage, it doesn't end up recognizing it. It was ZATTA's build but he said it didn't work for his Galaxy 3 or Note 2 either.
Will anyone find a cure????
This will be no fun to have to deal with for the next 2 years.
Chime in PLEASE!!!!!! Even if it's only to insult me, I don't care if you have a cure.
Regards
Dave
if you do Google search, it's a known issue. From what I read, it's a driver issue. Some have had luck using the older Samsung USB drivers. You have downloand them, and install, and have your PC completely disconnected from the internet before plugging in your GN2 after the install. Appaarently the drivers on Microsoft's servers are bad; may be the wrong device.
I've done this, and still have the issue. I just find I don't have plug and unplug the USB cable as much.
What I have seen, the PC does connect to the GN2. It just doesn't recognize it as a storage device. It wants to use it as a modem, probably from the tethering capabilities with a USB OTG cable.
It may not be so much that it's not wide spread, but more that not everyone uses the GN2 as storage device or connects it their PC.
I dont think this is all due to Windows issue. This is what i notice before and after root.
If you have restore to Original Stock ROM, you will notice that your device doesnt encounter this issue.
If you have rooted your device Custom ROM or Flash CMW (this resulted as Binary Counter increased), you would have Hardware Missing Id issue. Somehow the MTP is not working.
If you have Flash your device with a pre rooted stock rom, there is no issue at all until you flash CMW where flashing increase counter.
How i notice this, i have root/unroot my device like 20 times since i got my device.
The issue is here is more of where Binary Counter Increase, in Windows 7 you would face Hardware ID Missing issue. Restart and connect to other USB port will not work.
Some how we need to no let the Binary Counter changed and Triangle Away is only useful if you want to return you device to original state.
knightfox said:
I dont think this is all due to Windows issue. This is what i notice before and after root.
If you have restore to Original Stock ROM, you will notice that your device doesnt encounter this issue.
If you have rooted your device Custom ROM or Flash CMW (this resulted as Binary Counter increased), you would have Hardware Missing Id issue. Somehow the MTP is not working.
If you have Flash your device with a pre rooted stock rom, there is no issue at all until you flash CMW where flashing increase counter.
How i notice this, i have root/unroot my device like 20 times since i got my device.
The issue is here is more of where Binary Counter Increase, in Windows 7 you would face Hardware ID Missing issue. Restart and connect to other USB port will not work.
Some how we need to no let the Binary Counter changed and Triangle Away is only useful if you want to return you device to original state.
Click to expand...
Click to collapse
Yep I think you may be on to something. Because when I rooted I tried both TWRP and CWM and then I had to go back to stock to get to apply the LJC update. Ever since I have had the chameleon error and Handsfree activation issues. Oh my counter always says 1 and I can't remove it with triangle away. I think it says custom binary yes and the counter says 1. I am using a laptop with Windows 7 and it now recognizes the device just can't stop the errors on start up.
Charles
Sent from my SPH-L900 using xda premium
Samsungs older drivers: uploaded.net/file/hdh0f1xd
I'm having problems completing a firmware upgrade on my wife's Galaxy S2. It's at ICS and I want to get it to Jelly Bean. We're using the horrible Samsung program Kies, which is hosting the update to us. It sees the S2 fine... No problems there. It identifies the phone and tells us there's a newer firmware version we can download. Every time I perform the update, it downloads the firmware and when it reboots the phone, I get an error that the device can't be found and I should try again. When I go in device manager, I see an exclamation point on Samsung Mobile USB CDC Composite Device and it says the device couldn't be started.
It looks as thought, when the phone reboots to download the firmware from the laptop after the laptop has the firmware, Kies isn't seeing the phone. So I did vol-up-down to get it in programming mode and then reinitiated the download. That little trick doesn't work since Kies isn't identifying the device.
I've checked that I have the most current drivers, which I do. I've uninstalled them and reinstalled them and uninstalled Kies and reinstalled Kies and still get the error. I've also already updated the firmware on my Galaxy S3 using Kies on this computer and it worked fine. Now when I do it on my wife's S2, it bombs.
I then loaded Kies on another laptop and it's even worse. It downloads the firmware update and the entire application totally crashes.
I've gone to T-Mobile and they can't help with anything. They suggested turning USB Debugging on in the Developer Options on the phone, which I did. Still, nothing.
I located the hooks in the registry editor for the CDC composite device driver and everything *looks* good, as far as I can tell. Driver is dated 1/23/2013. As I said, it updated the firmware on my S3 fine... It just won't do it on my wife's S2. I don't know what to do.
Can anyone provide any advice or help? I've spent about 11 hours on this over two days and am running out of ideas.
-Paul
premington said:
I'm having problems completing a firmware upgrade on my wife's Galaxy S2. It's at ICS and I want to get it to Jelly Bean. We're using the horrible Samsung program Kies, which is hosting the update to us. It sees the S2 fine... No problems there. It identifies the phone and tells us there's a newer firmware version we can download. Every time I perform the update, it downloads the firmware and when it reboots the phone, I get an error that the device can't be found and I should try again. When I go in device manager, I see an exclamation point on Samsung Mobile USB CDC Composite Device and it says the device couldn't be started.
It looks as thought, when the phone reboots to download the firmware from the laptop after the laptop has the firmware, Kies isn't seeing the phone. So I did vol-up-down to get it in programming mode and then reinitiated the download. That little trick doesn't work since Kies isn't identifying the device.
I've checked that I have the most current drivers, which I do. I've uninstalled them and reinstalled them and uninstalled Kies and reinstalled Kies and still get the error. I've also already updated the firmware on my Galaxy S3 using Kies on this computer and it worked fine. Now when I do it on my wife's S2, it bombs.
I then loaded Kies on another laptop and it's even worse. It downloads the firmware update and the entire application totally crashes.
I've gone to T-Mobile and they can't help with anything. They suggested turning USB Debugging on in the Developer Options on the phone, which I did. Still, nothing.
I located the hooks in the registry editor for the CDC composite device driver and everything *looks* good, as far as I can tell. Driver is dated 1/23/2013. As I said, it updated the firmware on my S3 fine... It just won't do it on my wife's S2. I don't know what to do.
Can anyone provide any advice or help? I've spent about 11 hours on this over two days and am running out of ideas.
-Paul
Click to expand...
Click to collapse
First u got check USB debugging ON (on the phone)
disable anti virus on the pc/laptop
kies will put your phone into download mode and will take awhile (Kies is super slow) for good reasons
Also consider rooting your phone and install custom recovery (CWM) and flash all the rom(s) you wish [if that's an option]
hit Thanks if i helped
Thanks for the help, Sam.
I'll try it again with the virus protection off. I disabled the Windows firewall and that did nothing. I've tried it about 12 to 15 times, which takes a long time because Kies takes so long to download what it needs.
Can I root a T-Mobile phone? I used to have a Motorola Atrix 2 and rooted that and did manual firmware and ROM upgrades, but that was an unlocked and rooted phone. I'm afraid I may screw up the phone or my T-Mobile service by rooting it and doing custom installs. Does anyone have experience with this on a T-Mobile phone they purchased at T-Mobile? I don't want to mess the phone up.
At this point, I think that's the only way I'm going to go Jelly Bean on my wife's phone.
-Paul
Rooting your s2 is simple and easy to do. Go to the dev section and look at the threads on how to do it.
You will use Odin to flash a custom recovery such a TWRP whick will install supersu. At that point you can flash the ROM of your choice and not have to deal with Kies anymore.
Hope this helps
Sent from my SAMSUNG-SGH-T989 using xda premium
use this as a ref. http://galaxys2root.com/galaxy-s2-root/how-to-root-t-mobile-galaxy-s2-sgh-t989/
make sure to backup your current ROM as soon as your get root& cwm
after that u can flash any rom here is a list :http://www.androidmodmarket.com/ModMarket/Devices/Device-XDA-F-1332.html
i think u will like a clean fast 4.2.2 (jb) rom like slimbean....
try 'em & see which one u like......xda is your best bet for help & just about anything ROM
hit thanks if u like
sam.balia1012 said:
use this as a ref. http://galaxys2root.com/galaxy-s2-root/how-to-root-t-mobile-galaxy-s2-sgh-t989/
make sure to backup your current ROM as soon as your get root& cwm
after that u can flash any rom here is a list :http://www.androidmodmarket.com/ModMarket/Devices/Device-XDA-F-1332.html
i think u will like a clean fast 4.2.2 (jb) rom like slimbean....
try 'em & see which one u like......xda is your best bet for help & just about anything ROM
hit thanks if u like
Click to expand...
Click to collapse
This is all great information... Thanks so much. I've pressed "Thanks" to each of you. :good:
-Paul
Hi,
I have rooted by Note 2 N7100 in the past using the ODIN tool and CWM. But I had issues with some apps that were being closed at random etc. So I got tired and unrooted. But now I wanted to root it again using the ODIN. But ODIN is not able to detect my phone at all.
Please someone help me. Now that my note 2 got the 4.3, it is bloated with all kinds of crap from Samsung. I need to root to remove all the crap.
Thanks n Regards,
Harsha Puttagunta
puttagunta_h said:
Hi,
I have rooted by Note 2 N7100 in the past using the ODIN tool and CWM. But I had issues with some apps that were being closed at random etc. So I got tired and unrooted. But now I wanted to root it again using the ODIN. But ODIN is not able to detect my phone at all.
Please someone help me. Now that my note 2 got the 4.3, it is bloated with all kinds of crap from Samsung. I need to root to remove all the crap.
Thanks n Regards,
Harsha Puttagunta
Click to expand...
Click to collapse
Remove samsung usb drivers and reinstall them,that might work
Doesn't Help
singhpratik87 said:
Remove samsung usb drivers and reinstall them,that might work
Click to expand...
Click to collapse
Naa... this is a new laptop. So all new. still deleted the drivers and reinstalled. No luck.
puttagunta_h said:
Naa... this is a new laptop. So all new. still deleted the drivers and reinstalled. No luck.
Click to expand...
Click to collapse
i did google this issue and people have come up with various possibilities what could be wrong right from faulty usb cable to re installing drivers to factory resetting their device 3x for ODIN to be able to detect their device, i am a newbie too at these things so i am not really sure what could possibly be stopping from ODIN detecting your phone but i'll be on the look out and see if i can refer to you a solution if you haven't solved it already but if you do fix it somehow please post what exactly you did to make it work so it could help future users in case they run into the same issue.
EDIT: follow this word to word ,might work for you,let me know http://forum.xda-developers.com/showpost.php?p=34625034&postcount=7
Crazy
singhpratik87 said:
i did google this issue and people have come up with various possibilities what could be wrong right from faulty usb cable to re installing drivers to factory resetting their device 3x for ODIN to be able to detect their device, i am a newbie too at these things so i am not really sure what could possibly be stopping from ODIN detecting your phone but i'll be on the look out and see if i can refer to you a solution if you haven't solved it already but if you do fix it somehow please post what exactly you did to make it work so it could help future users in case they run into the same issue
Click to expand...
Click to collapse
It can't be the issue with the cable as I am able to use the cable for other things like backups and moving data from phone to PC etc. The issue with the Factory reset is that i dont have a spare phone at the moment. So if this device screws i am dead without a mobile to use.
Let me search some more and if I can find a solution i will post it here. Else I am going for the Cyanogenmod installer. I am tired of this.
puttagunta_h said:
It can't be the issue with the cable as I am able to use the cable for other things like backups and moving data from phone to PC etc. The issue with the Factory reset is that i dont have a spare phone at the moment. So if this device screws i am dead without a mobile to use.
Let me search some more and if I can find a solution i will post it here. Else I am going for the Cyanogenmod installer. I am tired of this.
Click to expand...
Click to collapse
Alright goodluck dude,hope you can fix it
I am at my wits end to try to repair my phone. It is softbricked and responds to download mode only.
I've had chat with xda members and read threads on it:
http://forum.xda-developers.com/chef-central/android/nand-write-start-fail-odin-soluction-t2851096
http://forum.xda-developers.com/galaxy-note-10-1/help/help-help-unbricking-galaxy-note-10-1-t2872125
and many others. in the end, my phone is still stuck with the NAND Write Start error with odin.
I know it happened after i tried creating a backup of my phone in recovery mode (phone was rooted with cf auto root and had a version of CWM on it). CWM gave me a warning about possibly bricking the phone, i agreed to the warning beacuse it always worked in the past, but when i rebooted, it was bricked this time.
this phone is not dead but samsung won't fix it beacuse it is rooted. I refuse to throw it away. I have read many people have it this error since kitkat 4.4 so surely there is a fix somewhere. I am hoping somebody will be more resourceful/experienced than i am.
I have tried changing to several different USB ports, without a hub, using original cables (bunch of different ones too) in many many different order and fashion. I tried enough variation to be convinced it is statistically impossible that all my hardware that was previously working for flashing has stopped working all at once. aka - it is not a usb port or data cable problem
may be related to data charging port on the phone though I highly suspect it given how it started.
I tried different roms, different versions of odin, i tried depackaging and repackaging roms, i simply do not know what to do anymore.
i tried reflashing with kies but kies just dies on me.
i tried flashing it with adb but adb won't even connect. when i plug the phone windows recognizes it and usb driver seems to work ok (not getting an error)
I have uninstalled and reinstalled drivers several times, rebooting in between installs. no difference.
i tried flashing different bootloaders as well as entire roms, no difference
I tried changing the pit file but that failed as well (odin couldn't even write the pit so my phone is not dead even if i failed pitting it)
i have access to both windows and ubuntu linux if it makes a difference.
Here are the terms of the bounty:
Price : 100$ (payable by paypal from eniac0 @ "some google mail domain starting with gm"
goal : find a fix that works on the latest firmware for SGH-i317M (Rogers, Canada)
how : i don't know but i need to be able to reproduce it. I am not new to flashing but anything advanced will need to be explained clearly.
I don't really know how this sorts of request usually turns out but i am serious. you even got my google mail address to bill me up if i fail to pay.
have you given a look at this thread? http://forum.xda-developers.com/showthread.php?t=2711825 it might give you some ideas to help you out. also did you try flashing a new recovery to see if you could at least get it to boot to that?
dont care about the bounty just trying to toss something out there that may help you
Did you ever try flashing the stock recovery - JUST the stock recovery - through Odin?
If not, grab the recovery.img and make your own tarball for Odin in Linux.
Hopefully that will flash and get you closer.
eniac0 said:
I am at my wits end to try to repair my phone. It is softbricked and responds to download mode only.
...
i have access to both windows and ubuntu linux if it makes a difference.
Click to expand...
Click to collapse
Since you mentioned Ubuntu, you can also try using heimdall instead of odin... http://glassechidna.com.au/heimdall/ . Unfortunately, I think it may be a hardware problem?
Since you are willing to pay to have it fixed, if all else fails, you can always send it off to http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-note-jtag-brick-repair/. It will actually be cheaper than what you are offering to pay ~$40 + shipping
good luck
Thanks all for your help, I've messed around and gotten no closer. I'm beginning to lean on a hardware failure, perhaps from the usb data port either that or the way bootloaders are packaged in kitkat 4.4 is different. which is why initially this thread gave me hope: http://forum.xda-developers.com/chef-central/android/nand-write-start-fail-odin-soluction-t2851096 but i tried far too many times now to believe I'm going to succeed. In fact, I've gotten confused as to what i tried, in which order, with which rom. I'm basically trying anything and that's a recipe for bricking the phone for good. so i've stopped.
I'll also thank kozmo21 for the link to the repair shop. i was unaware this existed, as a last resort I'll be sending them my phone. If it turns out they are able to repair it, I'll honor my word and give you something for having been part of the solution.
eniac0 said:
I am at my wits end to try to repair my phone. It is softbricked and responds to download mode only.
I've had chat with xda members and read threads on it:
http://forum.xda-developers.com/chef-central/android/nand-write-start-fail-odin-soluction-t2851096
http://forum.xda-developers.com/galaxy-note-10-1/help/help-help-unbricking-galaxy-note-10-1-t2872125
and many others. in the end, my phone is still stuck with the NAND Write Start error with odin.
I know it happened after i tried creating a backup of my phone in recovery mode (phone was rooted with cf auto root and had a version of CWM on it). CWM gave me a warning about possibly bricking the phone, i agreed to the warning beacuse it always worked in the past, but when i rebooted, it was bricked this time.
this phone is not dead but samsung won't fix it beacuse it is rooted. I refuse to throw it away. I have read many people have it this error since kitkat 4.4 so surely there is a fix somewhere. I am hoping somebody will be more resourceful/experienced than i am.
I have tried changing to several different USB ports, without a hub, using original cables (bunch of different ones too) in many many different order and fashion. I tried enough variation to be convinced it is statistically impossible that all my hardware that was previously working for flashing has stopped working all at once. aka - it is not a usb port or data cable problem
may be related to data charging port on the phone though I highly suspect it given how it started.
I tried different roms, different versions of odin, i tried depackaging and repackaging roms, i simply do not know what to do anymore.
i tried reflashing with kies but kies just dies on me.
i tried flashing it with adb but adb won't even connect. when i plug the phone windows recognizes it and usb driver seems to work ok (not getting an error)
I have uninstalled and reinstalled drivers several times, rebooting in between installs. no difference.
i tried flashing different bootloaders as well as entire roms, no difference
I tried changing the pit file but that failed as well (odin couldn't even write the pit so my phone is not dead even if i failed pitting it)
i have access to both windows and ubuntu linux if it makes a difference.
Here are the terms of the bounty:
Price : 100$ (payable by paypal from eniac0 @ "some google mail domain starting with gm"
goal : find a fix that works on the latest firmware for SGH-i317M (Rogers, Canada)
how : i don't know but i need to be able to reproduce it. I am not new to flashing but anything advanced will need to be explained clearly.
I don't really know how this sorts of request usually turns out but i am serious. you even got my google mail address to bill me up if i fail to pay.
Click to expand...
Click to collapse
Have you tried going to sammobile and download the newest firmware and only flashing that in odin?
Use CF auto root. Put the phone in download mode and flash it in Odin. I soft bricked my phone and it fixed it.
Also this guy had great walk through videos on how to do everything you need.
http://www.rootjunky.com/samsung/samsung-galaxy-note-2/
If it works to fix your phone. Keep your money. I'll take the karma points for putting you on the correct path.
Sent from my SHIELD Tablet using XDA Free mobile app
ShrekOpher said:
Use CF auto root. Put the phone in download mode and flash it in Odin. I soft bricked my phone and it fixed it.
Also this guy had great walk through videos on how to do everything you need.
http://www.rootjunky.com/samsung/samsung-galaxy-note-2/
If it works to fix your phone. Keep your money. I'll take the karma points for putting you on the correct path.
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
More than likely its a bootloader issue my phone did that and all i did was flash the bootloader then it worked again but hes done so much idk what he needs now that's y i said to try a firmware to see if that helps
Download toolkit and select option to push file into phone.
Download a ROM of your choosing, push it into your phone, restart in recovery mode and select file.
Update?
Did you get it fixed? Just my two cents, in case you didnt, I had a similar problem and alll I did to fix it was flash the JediMasterX2 ROM with CWM and everything worked out.
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.