Related
yes i have searched endlessly.
no i am not in anyway new to rooting (not claiming to be on the level of probably most here)
i have tried everything to get my replacement DInc to root. one confusing issue is that the error i get seems to bounce around all over the place. from back CID missing, to failed to gain root, to failed to flash recovery and is your firmware too new. i have tried:
* multiple versions of unrevoked.
* with and without sd card
* on charge only and on disk drive
* with and without firewalls enabled.
* did factory resets
* flashed a new RUU
i am almost sure i am forgetting something here but cant think offhand as i am about to go crazy with this thing. please if you have any suggestions then i will try anything. i know it may sound childish but if i cant root this thing after being used to it then i almost assume go back to my old razor.
thanks in advance
Sure you have the correct drivers (for windows machines)? Sometimes people have had to use different computers, couldn't hurt if you have access to another machine.
Sent from my ADR6300 using XDA App
k_nivesout said:
Sure you have the correct drivers (for windows machines)? Sometimes people have had to use different computers, couldn't hurt if you have access to another machine.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
well yes i am sure that i have the correct drivers cause i broke out the other device that i havent sent back yet and it rooted using the same items that i have been attempting with this one for 2 days now. i can attempt the root on a different machine shortly when my parents are up, will post results.
any one else have any thoughts care to share?
shorty1993 said:
well yes i am sure that i have the correct drivers cause i broke out the other device that i havent sent back yet and it rooted using the same items that i have been attempting with this one for 2 days now. i can attempt the root on a different machine shortly when my parents are up, will post results.
any one else have any thoughts care to share?
Click to expand...
Click to collapse
Try setting up the drivers from scratch for you new device. The same drivers worked when I rooted my buddies phone, but I had to re-download them from scratch to get it to work.
trickster2369 said:
Try setting up the drivers from scratch for you new device. The same drivers worked when I rooted my buddies phone, but I had to re-download them from scratch to get it to work.
Click to expand...
Click to collapse
already tried this. actually i just installed windows 7 ultimate on my laptop just a few days ago so it was completely clean. did everything from square one with no changes in issues. i called verizon today and told them that the replacement device i received was doing alot a odd things (no mention of real issue obviously) so without hesitation he said he would send me another out. so hopefully there is just something about this particular device that is abnormal. i would still like to keep hearing opinions and trying solutions tho. who knows that something in the refurbish methods arent causing this currently. thanks to all.
anymore guesses.
I had problems using Unrevoked on windows. I put it on my Mac, and it worked the first time, no drivers or anything needed. Probably not the most helpful advice, but if you have access to a Mac, might as well give it a try.
Uninstall dropbox and PDA net if present. SD is fat32? Using stock USB for device? Launching unrevoked as admin? Right click on the exploit before running, see if properties show it from unknown computer, and unblock it if needed. Same story with the drivers, check and unblock from properties, then reinstall as admin.
Tried a different USB port on the PC?
Sent from my ADR6300 using XDA Premium App
Did you get this resolved?
Sent from my ADR6300 using XDA Premium App
wanted to post back the outcome which hopefully at some point will help someone. i made sure every possible combination of drivers, programs, menu options enabled/disabled appropriately. nothing fixed this. verizon sent me a new device out (obviously they werent told my reasoning), powered it up, plugged it into the same computer and 2 minutes later was rooted with not the first issue. thus i have concluded that there had to be something in the programming that would not accept root. unsure how considering i even ran the RUU multiple times. thankfully they sent me a replacement for my replacement cause dealing with a stock phone after being rooted just would not work out.
thanks all
Yea if that phone was having that much trouble getting root then it probably could have bricked in the long run. Good thing you did get a replacement and were able to root in the end.
Greetings:
I have an SGH-T999 SGS3. It was running ICS.
When using Kies, I was offered the upgrade to Jellybean (LJA). The Kies update hung at 23%, for hours, repeatedly, and never exited.
I've now downloaded the root66 LJA system, and am trying to flash with ODIN. ODIN has now been stuck for an hour at system.img.ext4.
Can anyone help me get *anything* flashed to this phone, so I can get out of recovery mode please?
Thanks in advance!
Click to expand...
Click to collapse
To anyone having this problem, I fixed it by:
1. Using Odin307 instead of Odin185 AND
2. Using a different USB cable.
I don't know which of those two things fixed it, since I tried both at once, but that fixed it.
The entire update took 6 minutes once I changed those two things.
Thanks!
Glen
It takes a lot of time to flash system.img.ext4. I think it may take less or more time based on your computer and other factors. Just let it flash and wait. Mine took about 1.5 hour.
Sent from my frozen SGH-T999
Still waiting after one hour so far...
HajmeR said:
It takes a lot of time to flash system.img.ext4. I think it may take less or more time based on your computer and other factors. Just let it flash and wait. Mine took about 1.5 hour.
Sent from my frozen SGH-T999
Click to expand...
Click to collapse
Okay, started at 3:34 PM Pacific time. Still stuck (but not failed, interesting) at 4:37 PM (one hour so far.) I will advise.
This is on an HP Pavilion dv7-2173cl with a fresh load of Windows 8, no bloatware other than the stock stuff. (A similar attempt on an HP dv7-2043cl running Windows 7 also appeared to stick at the same point, but I only waited 30 minutes before giving up.)
By comparison, and just for interest, my international SGS3, I9300, updated over Kies in about 4 minutes, on the same computer. So I would be interested to know why an I9300 goes so fast, and a T999 goes so slow, if there are any ideas...
SOLVED!
glenbarney said:
Okay, started at 3:34 PM Pacific time. Still stuck (but not failed, interesting) at 4:37 PM (one hour so far.) I will advise.
This is on an HP Pavilion dv7-2173cl with a fresh load of Windows 8, no bloatware other than the stock stuff. (A similar attempt on an HP dv7-2043cl running Windows 7 also appeared to stick at the same point, but I only waited 30 minutes before giving up.)
By comparison, and just for interest, my international SGS3, I9300, updated over Kies in about 4 minutes, on the same computer. So I would be interested to know why an I9300 goes so fast, and a T999 goes so slow, if there are any ideas...
Click to expand...
Click to collapse
To anyone having this problem, I fixed it by:
1. Using Odin307 instead of Odin185 AND
2. Using a different USB cable.
I don't know which of those two things fixed it, since I tried both at once, but that fixed it.
The entire update took 6 minutes once I changed those two things.
Thanks!
Glen
glenbarney said:
To anyone having this problem, I fixed it by:
1. Using Odin307 instead of Odin185 AND
2. Using a different USB cable.
I don't know which of those two things fixed it, since I tried both at once, but that fixed it.
The entire update took 6 minutes once I changed those two things.
Thanks!
Glen
Click to expand...
Click to collapse
I experience this problem when I use a non-samsung usb cable(Vibrant and S3). It would always freak me out, because it would stay for hours and would usually end up in a soft brick.
all I've used on any of my Android phones is a cheap Blackberry-brand usb cable from Amazon. I think it was $2.00 or so. Hasn't failed me yet :good:
I would bet that it was probably just your very old version of Odin, honestly.
Kalm_Traveler said:
all I've used on any of my Android phones is a cheap Blackberry-brand usb cable from Amazon. I think it was $2.00 or so. Hasn't failed me yet :good:
I would bet that it was probably just your very old version of Odin, honestly.
Click to expand...
Click to collapse
I would bet that it is the USB cable. I tried flashing stock on my Verizon Note 2 and nothing happened after 90 minutes. I spent three hours flashing nothing happened. I was using the box included Samsung cable, then I read this thread so I might as well try it. I got my sister's HTC Incredible 2 cable and what would you know it was done in under 5 minutes. :laugh: Next time i flash i am going to have a tower of cables next to me
Kalm_Traveler said:
all I've used on any of my Android phones is a cheap Blackberry-brand usb cable from Amazon. I think it was $2.00 or so. Hasn't failed me yet :good:
Click to expand...
Click to collapse
Me too!
Flashing a full image through Odin should take 10-15 minutes tops. Is the phone connected as a USB 2.0 device? Sometimes the buggy drivers will put it into 1.0 mode.
mattedwards2686 said:
I experience this problem when I use a non-samsung usb cable(Vibrant and S3). It would always freak me out, because it would stay for hours and would usually end up in a soft brick.
Click to expand...
Click to collapse
thanks for the help man it really helped me !!
:good:
SCH-I605 Flash Fails with Odin
I am having a similar issue with my Note II. I tried to flash a new bootloader to facilitate the installation of the KitKat based Ditto Note 3 rom. I, in my failure to read 6 posts down, used mobileOdin to try and accomplish this. My phone is now a plush, soft brick. I can get into download mode. Given this, I have been trying to flash my phone using Odin for windows only to have it fail every time. I have tried different roms, partitions, bootloaders, versions of Odin, PCs, cables and even a couple of different poses. I am not new to rooting and roms, every android device I own is rooted and running custom roms. Any help from those who are definitely more knowledgeable than myself (the XDA community) would be GREATLY appreciated.
Phone Information:
Was running MeanBeanICE
Verizon phone
In download (Odin) mode:
Product Name: GT-N7100
Custome Binary Download: no
Current Binary: Official
System Status: Custom
Warranty Bit: 0
talonzme said:
In download (Odin) mode:
Product Name: GT-N7100
Custome Binary Download: no
Current Binary: Official
System Status: Custom
Warranty Bit: 0
Click to expand...
Click to collapse
Wrong Device Forum bud. This is T Mobile Galaxy S3 Only. You are Looking for Note II on Verizon I believe. Here's the correct Forum,
Yup, you'll get better, more specific help there. But just fyi, if kies is on your computer, uninstall it. Also, when trying different version drivers, make sure you first uninstall old ones through device manager. See my sig for drivers. They should work for any sammy device.
Sent from my SGH-T999 using Tapatalk
Apologies
DocHoliday77 said:
Yup, you'll get better, more specific help there. But just fyi, if kies is on your computer, uninstall it. Also, when trying different version drivers, make sure you first uninstall old ones through device manager. See my sig for drivers. They should work for any sammy device.
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
Sorry for the erroneous post. I do have the latest Samsung driver and I have uninstalled Kies. Thank you for your time. I have made a post in the Note II section. Hopefully I will find some joy soon!
talonzme said:
Sorry for the erroneous post. I do have the latest Samsung driver and I have uninstalled Kies. Thank you for your time. I have made a post in the Note II section. Hopefully I will find some joy soon!
Click to expand...
Click to collapse
Actually, dont use the latest. Try a few versions back. The latest, while it should still work, was built for the S5/Note3/Gear. It included significant changes as I understand it. Also in your case driver version doesn't matter. Some have had to try several before getting it to work. Sometimes the original works better than any newer ones.
Good luck with it though!
Sent from my SGH-T999 using Tapatalk
DocHoliday77 said:
Actually, dont use the latest. Try a few versions back. The latest, while it should still work, was built for the S5/Note3/Gear. It included significant changes as I understand it. Also in your case driver version doesn't matter. Some have had to try several before getting it to work. Sometimes the original works better than any newer ones.
Good luck with it though!
Sent from my SGH-T999 using Tapatalk
Click to expand...
Click to collapse
I will give that a go.
talonzme said:
I will give that a go.
Click to expand...
Click to collapse
Did you ever solve this?
mrdunlop said:
Did you ever solve this?
Click to expand...
Click to collapse
I did it involved the out jtag repair. It that where i was unrecoverable by standard means.
life saver
glenbarney said:
To anyone having this problem, I fixed it by:
1. Using Odin307 instead of Odin185 AND
2. Using a different USB cable.
I don't know which of those two things fixed it, since I tried both at once, but that fixed it.
The entire update took 6 minutes once I changed those two things.
Thanks!
Glen
Click to expand...
Click to collapse
thanks bro
i used a different USB Cable it worked.........
thanks alot
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.
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.
Hi, just got my note 4 3 days ago and I'm not new to rooting, however I can not get Odin to recognize, I've tried several Odin versions, 3 computers and 4 cables. I also just finished the last update to PL1 today. What gives, I need trwp to root, not unless there's an adb method.
ddarkone said:
Hi, just got my note 4 3 days ago and I'm not new to rooting, however I can not get Odin to recognize, I've tried several Odin versions, 3 computers and 4 cables. I also just finished the last update to PL1 today. What gives, I need trwp to root, not unless there's an adb method.
Click to expand...
Click to collapse
Install samsung usb drivers.
If you already have installed then uninstall them and install new again then reboot pc.
See if it fix the issue
I've tried that, thanks for the suggestion
ddarkone said:
I've tried that, thanks for the suggestion
Click to expand...
Click to collapse
Cheap hackers number one attack is to uninstall drivers. Once you get rooted I suggest you chown your USB settings to no where. I have to reinstall by samsung drivers before I use Odin every time. There's some great apps like pdanet that will fix your windows drivers but in some cases to well. You basically got a debugging bridge for the world. As far as the drivers in your note the scam is to get you to pay for remote help. I chowned the drivers in it and it's good but I can't get them to let up on my son's S4. Here's the trick - it they don't stay inactive in recovery or dl mode. When you boot into dl they default disable (this may even be Samsung). Pull the battery and wait for about 30 seconds - replace the battery and boot straight to dl. This works for me every time.
Sent from my SM-N910P using Tapatalk
---------- Post added at 02:38 AM ---------- Previous post was at 02:32 AM ----------
ddarkone said:
I've tried that, thanks for the suggestion
Click to expand...
Click to collapse
Sorry if this is redundant, I can't see that my first reply posted. To get your usb too work in DL mode you have to give it a cooling period from the time you shut it of. The more I think off it it is a samsung thing on new firmware. All though when it happens too me I always get a link from people wanting money to fix it. Pull the battery, wait 30 seconds then boot straight to dl = volume down + home + power. The USB resets after the cool down.
Sent from my SM-N910P using Tapatalk
ddarkone said:
I've tried that, thanks for the suggestion
Click to expand...
Click to collapse
Are you using stock usb cord? I've heard of people having problems with cheap cords.
finally, got it just now, I have never went through this before, I had to remove driver and disable driver about 8 times, and Odin finally did it's thing for me. Now to get rid of those ads!, thanks
ddarkone said:
finally, got it just now, I have never went through this before, I had to remove driver and disable driver about 8 times, and Odin finally did it's thing for me. Now to get rid of those ads!, thanks
Click to expand...
Click to collapse
It has been getting way bad for my Note 4 S4 and puter. My S4 got so it wouldn't even charge after cold boot. If I didn't have extra batteries and a wall charger I probably would have never figured it out. My pc updated to a invalid copy of sevice pack one and when I plugged my note in to it a note popped up saying this device can not communicate with the device it is connected to. It said that you have to make windows like Mac for it to work right and a bunch of other absuuird stuff. It gave me a link to androidfilesystems.com and said I'll find it there. I downloaded a package called android drivers to check it out. This app says you have to fet your ADB drivers for windows from your android. I was lauging my ass the whole time but I had to check it out. This app opens and it prtends to be pulling stuff from your device. Once out it tries to install and then says it failed becuase my device has been tampered with but they can fix it for me remotely for $200. It seems to have come with stalk firmware from SamM##### They haven't been watching me as closely as I thought. Because the would have noticed the APK decompiler the PDAnet (which has a straight awesome ADB for windows driver. The fast ADB, the android SDK and all of the other things that show that not only do I know windows drivers don't come from android, I will also be taking their app apart to figure out if they are infecting me worse. I pulled it a part and it does have a pretty good driver package for windows and the only malice had to come pre installation and the lie about what they are doing. I still have the apk. it gves me a good laugh when I'm down.
If you had this issue it will persist. Your going to have to fix your driver issues every time you adjust your firmware, unless your straight change all of it. The first step is to not install busy box. A couple of apps will refuse to try but for the most part will run better. It makes way to many sym links to ever break them all. Another is in recovery use the terminal to go to /sbin/recovery chmod the dev files and then chown the usb file -Rwith -L. They are all ready set. There is no reason for it to be sym linked other than for malicious outsiders to turn it off. When you go to sbin you are going to notice TW home has been given down load capabilities and crypto files. Neither of those serve a purpose for the user. I don't know how to break the download on the tw other than to freeze and/or uninstall it and use a differnt driver. You can lose the crypto files with chmod 0755 and cmd wipe_data_crypto. Good luck.