Related
There is a devil in disguise called Kies, which Samsung has unleashed on its victims (customers).
The internet is full of it! Google 'kies' and you Will find only problems from the first page itself!
Don't know what Samsung had in mind when it was released. Working on it is like a hurdle race and the normal user isn't an athlete! Even if you pass on hurdle somehow, another one is waiting for you with a big grin. There is no alternative. Use Odin and your warranty's in trouble.
I have been trying to upgrade my GT-I9000 to 2.2 for days! First Kies won't detect my phone. I tried deleting files with long extensions but it didn't work. After many more alleged solutions I finally had to hunt down all Kies files and registry keys. Reinstalled Kies and it worked. But this was not the end of the story! It detected the phone but won't upgrade it!
"This device firmware cannot be upgraded!!"
Why??
Even the Samsung people did not have the answer.
Another series of possible solutions and finally one worked!
But again this was not the end. Halfway through the firmware download came the 'Cannot connect to remote server'. Only once it had brought misery but it came again, and again, and again.
And until now the end user still lies in vain.....
You came here to complain about Kies.... ????
Dude, just flash it urself, it's easier and safer ....
I would never use Kies to upgrade, hell NO... But goodluck..... U ginna need it
Sent from my GT-I9000 using Tapatalk
search on here for Kies Reg Hack and spoof the product code as XEU, then re-connect and it will give you the update.
or just do it the odin way as previously suggested.
Odin, definitely
Use Odin. Got Froyo in my GT I9000 yday with it.
Kies is the worst piece of crappy software I've seen.
Cheers,
Roger
1. Begin here
Use this method heimdall
2. Then here
3. Finally here
Hope this helps...
Fremen567 said:
You came here to complain about Kies.... ????
Dude, just flash it urself, it's easier and safer ....
I would never use Kies to upgrade, hell NO... But goodluck..... U ginna need it
Sent from my GT-I9000 using Tapatalk
Click to expand...
Click to collapse
Dude, I'm just highlighting Samsung's deeds. Let it be a warning to all who read to stay away from Kies!
Sent from my GT-I9000 using XDA App
kunjar said:
1. Begin here
Use this method heimdall
2. Then here
3. Finally here
Hope this helps...
Click to expand...
Click to collapse
Thanx kunjar!
That sure helps a lot!!
Sent from my GT-I9000 using XDA App
Turbokat said:
There is a devil in disguise called Kies, which Samsung has unleashed on its victims (customers).
The internet is full of it! Google 'kies' and you Will find only problems from the first page itself!
Don't know what Samsung had in mind when it was released. Working on it is like a hurdle race and the normal user isn't an athlete! Even if you pass on hurdle somehow, another one is waiting for you with a big grin. There is no alternative. Use Odin and your warranty's in trouble.
I have been trying to upgrade my GT-I9000 to 2.2 for days! First Kies won't detect my phone. I tried deleting files with long extensions but it didn't work. After many more alleged solutions I finally had to hunt down all Kies files and registry keys. Reinstalled Kies and it worked. But this was not the end of the story! It detected the phone but won't upgrade it!
"This device firmware cannot be upgraded!!"
Why??
Even the Samsung people did not have the answer.
Another series of possible solutions and finally one worked!
But again this was not the end. Halfway through the firmware download came the 'Cannot connect to remote server'. Only once it had brought misery but it came again, and again, and again.
And until now the end user still lies in vain.....
Click to expand...
Click to collapse
before you move to other method, did you try KIES 2.0?
Kies 2.0 suck.............so iTunes-ish!!!! but it is ok for me...the problem is the system performance!!!
Yes
bsamurai said:
before you move to other method, did you try KIES 2.0?
Click to expand...
Click to collapse
I have an updated version of kies
Funny. It always worked for me.
Sent from my GT-I9000 using XDA App
Same here, never really had any problems with KIES. I've flashed numerous times using the reg hack.
I use ODIN only for kernels and modded ROM's.
However, to use ODIN I always have to use my laptop (WinXP) as it gives errors on my desktop PC (Win7).
No problems with Kies here as well, but rejoice ... with 2.2.1 and higher, you can get OTA updates on your SGS.
Dread using kies.it doesnt work on one computer its bricked my other computer.
rtoussaint said:
No problems with Kies here as well, but rejoice ... with 2.2.1 and higher, you can get OTA updates on your SGS.
Click to expand...
Click to collapse
Didn't know that, any idea on how you should get the updates (when one is available )?
ota = over the air, which means u download with our phone, no need for pc.
now u need 2e recovery to do that now, because the update has to be signed by samsung(i could be wrong with this, as I didn't use it)
Sent from my GT-I9000 using XDA App
Sysiphus1981 said:
ota = over the air, which means u download with our phone, no need for pc.
now u need 2e recovery to do that now, because the update has to be signed by samsung(i could be wrong with this, as I didn't use it)
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Thanks for the info!
.
Those who did not have any problems must be the luckiest people on Earth!
I had problems with every install on all my machines.
Well im using odin to flash stock firmwares on my phone. Just using Kies for samsung drivers, is that ok?
Only problem I've had with KIES is that I have to plug in my phone before I start KIES or it won't find it. My experience with the software has been mostly positive.(That goes for the old and new versions of KIES)
Regards
Hi,
Have searched through the forums, and tried to use drivers from the Snapdragon Toolkit, still can't get pass the last part of the driver installation on Win7 64 bit. Anyone still encounters this issue?
Thanks for your time.
Jack
Bell Mobility SGS3 Rooted
I had a similar issue once. I believe its an issue with not setting windows updates to update automatically. Change this setting to automatic and it should help. I don't remember the exact steps I took so that's as far as I can get u
Sent from my SGH-I747M using xda app-developers app
I get the same thing but the NV backup appears to work fine?
mbh87 said:
I get the same thing but the NV backup appears to work fine?
Click to expand...
Click to collapse
Yup, same here, NV backup works ok even though that last driver install fails.
Will try turning on Windows update tonite and see if it works. I would like to use Kies for official bell update, right now just can't get pass the driver installation part.
Thanks.
Sent from my SGH-I747M using Tapatalk
Turned on Windows update, still no luck. What is this USB RMnet driver? It always says installing driver, but can never succeed.
Sent from my SGH-I747M using Tapatalk
Problem solved!!
Hi All, finally solve the issue! Go into PhoneUti*#7284#, go Qualcomm USB settings, select MTP+ADB, I can connect to KIES now!:cyclops:
It had RMNET+DM+MODEM selected before. Hope this helps.
Cheers.
Jack Bell
jack0131 said:
Hi All, finally solve the issue! Go into PhoneUti*#7284#, go Qualcomm USB settings, select MTP+ADB, I can connect to KIES now!:cyclops:
It had RMNET+DM+MODEM selected before. Hope this helps.
Cheers.
Jack Bell
Click to expand...
Click to collapse
My phone's not have the OS (wiped by mistake), but i can go to recovery mode (twrp) and download mode, due to this usb rmnet issue in my laptop which causing the odin or my laptop cant detect my phone, wht should i do.
Thanks in advance.
bucks_26 said:
My phone's not have the OS (wiped by mistake), but i can go to recovery mode (twrp) and download mode, due to this usb rmnet issue in my laptop which causing the odin or my laptop cant detect my phone, wht should i do.
Thanks in advance.
Click to expand...
Click to collapse
Hi, sorry for the late reply, just saw the notification. Did you resolve it yet? If you can connect to kias, you can probably reinstall the official Rom in download mode. Or you can save the Rom files you need and flash in TWRP recovery. How this helps.
Jack
Sent from my SGH-I747M using Tapatalk
jack0131 said:
Hi, sorry for the late reply, just saw the notification. Did you resolve it yet? If you can connect to kias, you can probably reinstall the official Rom in download mode. Or you can save the Rom files you need and flash in TWRP recovery. How this helps.
Jack
Sent from my SGH-I747M using Tapatalk
Click to expand...
Click to collapse
Do you mean samsung kies sir ? Even samsung kies not recognize my device, i've tried every methods i found through all forums, none is work and solved my device problem. But anyway my device is gone now, hv bought new one
thanks anyway for your reply sir.
Hello Everybody,
I habe a really big Problem with my GNex.
Today I Copied some Files over to my PC. For this I used for the first time "USB Mass Storage". Because I haven't seen some Files wich i can see under my Phone.
It worked really good. I unplugged my phone and to my things. Some minutes later i Heared the "Pling" from superuser. Then my phone was really slowly and need a bunch of time only to open the Launcher. So i deactivated Superuser. Deinstalled USB Mass Storage and MyMobiler.
After this i rebooted my Phone 2 times and the lag on my screen was gone. But now i'm unable to Access the Device under Android booted as MTP.
Even after reinstalling USB Mass Storage i'm unable to Access the Device via MTP or Mass Storage. My Windows PC and Android don't says anything. My Device is only Loading.
So i Unlocked my Bootloader with "BootUnlocker" and updated my System with offical Google Update 4.2 "fastboot update image-yakju-jop40d.zip" .
But i cann't access my Device now. Only fastboot is working.
So i'm unable to backup all my data and do an Factory Reset.
Have anyone out there an Suggestion how i can fix this Problem.
My Device:
Galaxy Nexus
Stock: 4.2
BL: Unlocked
Root: No Root (But with BL unlocked should this be the smallest problem.
Best regards and Thanks
Chris
P.s Sorrry for the really bad English
P.s.s Fastboot is working ... so it don't seems like an HW error
The nexus doesn't have use mass storage
Sent from my Galaxy Nexus using Tapatalk 2
This point i know, thats why i used the App.
But how can i aceess my Phone with MTP?
It's not even reconigzed under Windows ... and Android also don't set an Logo which tells that USB is Connected.
Chris302 said:
This point i know, thats why i used the App.
But how can i aceess my Phone with MTP?
It's not even reconigzed under Windows ... and Android also don't set an Logo which tells that USB is Connected.
Click to expand...
Click to collapse
have you tried a different usb chord?
simms22 said:
have you tried a different usb chord?
Click to expand...
Click to collapse
Yes i tried another USB-Cord.
Same thing -> Phone is Charging but not resposing over ADB.
And also i can't see it in the Explorer.
Same thing at my GF PC (Win Vista)
are you trying to use adb in the bootloader? if so, that will never work. ever.
Zepius said:
are you trying to use adb in the bootloader? if so, that will never work. ever.
Click to expand...
Click to collapse
No i'm using Fastboot when i was in BL to confirm that i have no HW error.
I try to ADB when i booted my Phone.
Or to access the My Device via Explorer
Have you tried removing and re-installing the drivers from your PC?
Have you checked the Android SDK to see if there is a 4.2 specific version of adb?
danger-rat said:
Have you tried removing and re-installing the drivers from your PC?
Have you checked the Android SDK to see if there is a 4.2 specific version of adb?
Click to expand...
Click to collapse
I Don't think hat There is my Problem, because under Windows i can Not even See my device it is not even recognized.
I can test driver uninstalling but i can not see my device under the device manager
:/ it seems like my android is f****ed up because root is also not working :/
When you update to a stock image you over write your/system partition (which is where you enabled root access) - that is most likely how you lost root access.
Also, since you updated your device, it is possible that your PC no longer sees it as the same device, which is why I suggested removing and reinstalling the driver...
danger-rat said:
When you update to a stock image you over write your/system partition (which is where you enabled root access) - that is most likely how you lost root access.
Also, since you updated your device, it is possible that your PC no longer sees it as the same device, which is why I suggested removing and reinstalling the driver...
Click to expand...
Click to collapse
I want to clear some things.
Don't think i want to shame you, i really thankfull for your help . Also it is the Best forum for Android Development and everything around it wo i have ever seen.
I was always on Stock. I updated the Offical 4.2 to 4.2 with an Stock image, it is now working again, i think the Update cleaned the Things up. Only Thing (shame me) i have forgotten to check after update is under-> settings -> storage -> Menu -> USB-Connection -> and check there "MTP".
So now my Device says connecting as "MTP" and my PC also recognize it again.
Before that my Device don't even say connecting as MTP.
I know that i will loose root when i update my Device -> but with my unlocked BL I just Booted to CWM and flashed Superuser.
Maybe (i hope) you are willing to help me again.
I am unable to update my SU binary and also i dont see a Message from Superuser, where i can allow Root access.
Even if i set under Settings -> Security -> Automated Answer -> "Allow"
I don't see the Message where i can say "allow" to Root access. I cannot even install SuperSU.
Have you any idea why it seems like i cannot access Root. For me it's seems like my app's don't recognize root.
When i Start SuperSu he says "Su-binary" must be updated" and next step is "Installation failed".
Have you any Idea where this came from?
But the good thing is at this point i'm abel again to access my Device via Explorer Thank you really really much for your Help You can't belive how glad i'm not to do a Factory reset and loose all my data.
Thank oyu for your great help
Chris
P.s. Root is working from Shell
Please read forum rules before posting
Questions and issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Okay i will read the Rules again.
Thank you for moving the Thread.
I hope in the right section someone can tell my why my Root isn't working ?
P.s. or should i make a new thread for that problem ?
Chris302 said:
Okay i will read the Rules again.
Thank you for moving the Thread.
I hope in the right section someone can tell my why my Root isn't working ?
P.s. or should i make a new thread for that problem ?
Click to expand...
Click to collapse
Use SuperSu instead of Superuser.
Sent from my i9250
bk201doesntexist said:
Use SuperSu instead of Superuser.
Sent from my i9250
Click to expand...
Click to collapse
Sorry for the long delay.
I had no time to check this thread. And also my Email Notification hasen't worked.
So I hope you still look at this and can also suggest something.
I tried SuperSU but supersu says.
He need to install the Binaries.
After roundabout 15 seconds i get an Error message which says: "Installation failed".
My Super user tells me that the Binary is outdated.
And i get this Error Message in SuperSU even when i say "Answer every Permission Request with Allow".
I Even tried to remount the System as RW and the say update. But Both of them Seems to fail to install the Binary.
I flashed Superuser Through Temp Booted CWM.
Is their another Zip that i can try ?! or have i done something wrong while Flashing ?
Or can i theoretically flash SuperSU through CWM and then get Root Access?
Thank you for your help
Chris
Chris302 said:
Or can i theoretically flash SuperSU through CWM and then get Root Access?
Thank you for your help
Chris
Click to expand...
Click to collapse
Correct; you will be rooted again. Just boot a custom recovery and flash.
Sent from my i9250
bk201doesntexist said:
Correct; you will be rooted again. Just boot a custom recovery and flash.
Sent from my i9250
Click to expand...
Click to collapse
Hello
And again a dumb question.
Could you please provide me a download link for a zip. Which is working under 4.2 ?
I have seen zip's around for Superuser but not for SuperSU.
An i only Mention that maybe Superuser have a Problem with 4.2 but i cannot Prove it.
Thanks again
Chris :]
Sent from my ASUS Transformer Pad TF300T using xda app-developers
oasad92 said:
Yeah SuperSU should do the trick
Click to expand...
Click to collapse
Thank you for the Reply.
But how i have written 2 post ago. SuperSU also did not work.
He keeps saying "Installation Failed" thats why i asked for an Flashable Version which is working under 4.2.
I recently reverted back to stock 4.2.1 (just to try it)
My Win7 computer was unable to see my phone when connected in MTP mode. Nothing showed in the computer at all, However when I selected PTP I could acess the DCIM folder.
In the end I couldn't be F**Ked with it so I pushed a custom rom to data/media/ and every thing was normal again.
I spoke to a friend who had the same issue I had, and he just enabled debugging (which a custom rom has enabled by default) to solve the issue.
Chris302 said:
Hello
And again a dumb question.
Could you please provide me a download link for a zip. Which is working under 4.2 ?
I have seen zip's around for Superuser but not for SuperSU.
An i only Mention that maybe Superuser have a Problem with 4.2 but i cannot Prove it.
Thanks again
Chris :]
Sent from my ASUS Transformer Pad TF300T using xda app-developers
Click to expand...
Click to collapse
oasad92 said:
Yeah SuperSU should do the trick
Click to expand...
Click to collapse
I have not tried Superuser again since Chainfire released Supersu and all those issues rose with JB.
Chris302 said:
Thank you for the Reply.
But how i have written 2 post ago. SuperSU also did not work.
He keeps saying "Installation Failed" thats why i asked for an Flashable Version which is working under 4.2.
Click to expand...
Click to collapse
http://www.google.co.uk/search?q=xd...&sugexp=chrome,mod=0&sourceid=chrome&ie=UTF-8
would take you to:
http://forum.xda-developers.com/showthread.php?t=1538053
flash that
p.s: on the supersu thread says you need to be rooted... for us, of course, it's not quite true, rather we need unlocked bootloader and custom recovery.
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.
SOLVED: see post #5 & #8
I've been trying to root my T807T and everyone with one on the forums here has reported that all T805 stuff works just fine on it.
I have installed USB drivers, USB Debugging set to on. Been using Odin 3.07 as well as 3.09.
I tried multiple USB ports and two computers and a whole lot of different wires (including original ones).
I disabled my Anti-virus and do not have Kies installed.
I am not a newbie to flashing and have been rooting Samsungs since the first Galaxy S Vibrant all those years ago. I have never seen anything like this.
Everything I try to flash in Odin comes up with FAIL! after about halfway through flashing. I can restart my tablet and everything works fine, but this is making it impossible to root.
FAIL occurs right after "NAND Write"
Any/all help is very much appreciated. If anyone is NYC local and can give it a shot, that'd be great.
Thanks everyone.
I would suggest taking a look at this thread. http://forum.xda-developers.com/showthread.php?p=54393309
Install kies and reinstall drivers with kies probably would help?
DUHAsianSKILLZ said:
I would suggest taking a look at this thread. http://forum.xda-developers.com/showthread.php?p=54393309
Install kies and reinstall drivers with kies probably would help?
Click to expand...
Click to collapse
I've read that thread before, not the same issue. But thanks for the heads up nevertheless
postulio said:
I've read that thread before, not the same issue. But thanks for the heads up nevertheless
Click to expand...
Click to collapse
I would uninstall the drivers and try to install the drivers from kies. Other than that, Im not sure why it wouldnt work.
I have been digging a lot on the issue. Of course I haven't been able to find a whole lot other then it appears 95 percent of these nand write issues are with samsung devices. Make sure that in settings>general>security reactivation lock is OFF. Also try removing your SIM card and the SD card if you have one. Then proceed to flash. We have the exact same model, firmware, build, etc etc. I can't think of a logical reason why it won't work. I'd be inclined to believe it's a communication issue between tablet and computer at this point. Completely stumped on this one however I will keep digging for you.
DUHAsianSKILLZ said:
I would uninstall the drivers and try to install the drivers from kies. Other than that, Im not sure why it wouldnt work.
Click to expand...
Click to collapse
no go.
postulio said:
no go.
Click to expand...
Click to collapse
Does your tar have .md5 at the end of the filename? I think it should fail earlier if this is the problem but maybe its not being properly verified? Its just a shot in the dark but try removing the .md5 if its there and just flash the straight .tar file. Or retry download maybe you got a corrupt copy.
Sent from my Nexus 7 using XDA Free mobile app
Ripx88 said:
I have been digging a lot on the issue. Of course I haven't been able to find a whole lot other then it appears 95 percent of these nand write issues are with samsung devices. Make sure that in settings>general>security reactivation lock is OFF. Also try removing your SIM card and the SD card if you have one. Then proceed to flash. We have the exact same model, firmware, build, etc etc. I can't think of a logical reason why it won't work. I'd be inclined to believe it's a communication issue between tablet and computer at this point. Completely stumped on this one however I will keep digging for you.
Click to expand...
Click to collapse
HAHAHAHA BINGO!!!!
woooo!
cfautoroot: BAM! worked first try.
everybody dance.
Thank you very much for this genius tidbit. I must've enabled it the first day I got the tablet and forgot all about it as It's never been an option on any of my other devices.
Huge thanks to both of you guys for bending over backwards trying to find a solution as to why the flashing wasn't working. Now we know.
Pretty clever of Samsung to hide an Odin flash lockout switch within the actual OS (as opposed to recovery).