Related
Im stupid stuck on the first step and Ive been at it for a week now, I just want to Root, then Ill never need to PC plug the phone again.
The problem is my Evo 4G ONLY connects to the pc to charge. Ive tried fixes, sorry, Ive wasted time on fixes and help posts; I did just successfully install 3.29.651.5IMG.zip from
http://forum.xda-developers.com/showthread.php?t=838448, but that was just been an update.
Anything Terminal Emulator, HBOOT or RECOVERY I can do, thanks for the help, google searching is pulling up all androids, allphone models, all Dates, I keep getting 2009 results.
ALSO, to anyone interested in Metro Flash, the 10 dollar phone flashing service from Metro PCS; in Nevada, found out yesterday, MetroFlash isnt available because the setup or network is/are changing or something. I forgot the specifics, but the rep said that even if I went and did it in CA, it wouldnt work in NV because of that.
Supersonic EVT2-3
Hboot 97
MicroP-041f
Radio 2.15.00.09.01
Build 3.29.651.5 cl252548 release-keys
Hardware v003
PC36IMG
Do you have HTC Sync downloaded to your cpu. IF you don't you need to, so that you will have the drivers that you need to start the process.
I tried versions 2.something and the version on the htc support site, thanks though.
log3an said:
I tried versions 2.something and the version on the htc support site, thanks though.
Click to expand...
Click to collapse
And you are sure you are downloading the correct version. Are you on windows? 32bit? 64bit? Mac? All of that matters so you D/L the correct version otherwise your cpu will not recognize your phone and install the drivers. If its not doing that then it has to be that you aren't having the drivers installed correctly.
I've had a bad USB cable be the culprit of my computer not recognizing my phone. Mine would say "unrecognized USB device" though.
I would try another cable and report back.
Dude i friggin LOVE the help, but the port on the phone is screwed. i actually came back to elaborate on my response; Ive downloaded Most of what I could to ADB if it were working- JDK, Android SDK full, super 1 click, autoroot, unrevoked3, and several RUUs. Initially I followed directions, after nothing working, I experimented. Then I did a faulty usb port search, and all of the suggestions were 'unplug and replug' and such. Its defected.
Spencer my computer isnt responding at all to the USB plug, but thats what posts said, it could be the port or the cord or the pc usb port/hub. its my phone.
log3an said:
Dude i friggin LOVE the help, but the port on the phone is screwed. i actually came back to elaborate on my response; Ive downloaded Most of what I could to ADB if it were working- JDK, Android SDK full, super 1 click, autoroot, unrevoked3, and several RUUs. Initially I followed directions, after nothing working, I experimented. Then I did a faulty usb port search, and all of the suggestions were 'unplug and replug' and such. Its defected.
Click to expand...
Click to collapse
Oooooooh, well you're probably looking for help in the wrong place. You need to take the phone for repair. But I did see a thread on here someone posted about how to root without using a computer, but I didn't actually open it to see what the process was. Maybe that will help you out.
You know what Swaze, Im un and re-installing right now, its HTC Sync SETUP 3.0.551, the other was htc sync2.0.35. Be back after the reboot.
-Went into SERVICES too, Id 'manualed' a few items that I hadnt considered..
I didnt answer either, but I have win7 32 and 64bits installed on this pc, Ive been on the 32bit since the first day.
--And that wasnt it. I was hopeful it was the windows COM thing id disabled.
Try mailing the files to u then use a file explorer to move where u want them. Unless ur using an ruu I don't think u actually need connection.
If I remember right unrevoked has set it up where u can do everything. from your phone using a web site. Maybe I'm wrong.
Sent from my PC36100 using XDA App
Do you have USB Debugging enabled on the phone?
sand thats actually something worth trying, use a root file explorer to copy/paste the flash-image files since I dont have S-Off. Nice, thanks dude.
This will probably sound like the dumbest idea EVER but why can't you just buy a card reader and put the images on the SDCard the old fashioned way? Seems easy enough to me, am I missing something? Also couldn't use just copy the files over using your DropBox? Thats how I do it.
or how about WiFi Explorer? its an app in the market lets you browse and copy files to your SDCard via WiFi.
sand thats actually something worth trying, use a root file explorer to copy/paste the flash-image files since I dont have S-Off. Nice, thanks dude.
Update- Root Manually
Following Sand's suggestion, I began google searches of the manual root processes, supporting information, etc.
Here's where we're at
I began by copying the flash-image to the proper system folders, using Root Explorer, File Expert works too. If you copy files to system/protected folders with an ordinary file manager, the permissions fail.
http://forum.xda-developers.com/archive/index.php/t-918275.html
So, the next step was to learn how to chmod to 775, for those lost READ THIS, its a nice guide on linux permissions and how to set them.
http://forum.xda-developers.com/archive/index.php/t-918275.html
And now Im watching Old Christine, eating a burrito. Ill post more if anyone's interested, if anyone has any tips or shortcuts for me, thatd be awesome.
Update
Just updated another post, and this is what I put
in no particular order,
ADB Over TCP/IP Help
this was the most recent attempt, Android lacks adhoc support though
ADB For Beginners
Commands like 'cp' and 'cat' are used interchangeably it seems, when I find a fuller command list incorporating more, this one will be replaced
Always Up To Date Root Guide
This is a great place for ideas if you're stuck, theyve put all the verified instruct-files on one page. I guess thats what moderators on forum sites do, consolidate information, this was just easy to read without weeding through any unrelated information
Evo 4G Root/Android Root
This was another promising page I came across, but the the 300mb zip failed installation. 'Main Version is Older', all the files in the zip were for like 1.0 and my Evo's radio is 2.15. Changing the Android-info.text in rom .zips to match my devices information was my next idea. Do not do it though, scanning google result lines said it could brick your android.
Visionary, No ADB
This is last because it was a bastard, long story short its not even for the Evo. The jerk.
Updated Again - ADB over Tcp/Ip Works, How to Root?
I was tethering when I found the Adb over wifi so I didnt test it- shouldve though. I connect now cmd tells me, but the 1 step rooters arent working. Before I waste another weeks chasing bad paths, what should I use?
After wasting so much time with your issue, why haven't you used the time to get the phone fixed/replaced?
I had similar issues when I rooted my phone. My phone kept disconnecting while the rooting process was taking place. The issue I found out was my USB cord. I went to the Sprint store and got a new one, then my computer (W7) detected my phone through disk drive.
The new cord worked, using the AutoRoot program found in the rooting section here, and it completed my root.
I hadnt thought of that
SteveGrandRapids said:
After wasting so much time with your issue, why haven't you used the time to get the phone fixed/replaced?
Click to expand...
Click to collapse
SteveGrandRapids, youre a fricken GENIUS. Or an ass; I dont have Sprint. From another of my posts asking the same question:
''Uminchu I wish the problem was the port or plug. Then again if it were, the original owner wouldnt have sold it to me. My friend has had this phone sprint serviced twice, once at best buy when we thought it was the powermat malfunctioning. third time he just got a new phone, now I have this one and metro pcs; an account that Ive had for years now and have flashed two other phones to. ''
Thanks for the pollution.
log3an said:
SteveGrandRapids, youre a fricken GENIUS. Or an ass; I dont have Sprint. From another of my posts asking the same question:
''Uminchu I wish the problem was the port or plug. Then again if it were, the original owner wouldnt have sold it to me. My friend has had this phone sprint serviced twice, once at best buy when we thought it was the powermat malfunctioning. third time he just got a new phone, now I have this one and metro pcs; an account that Ive had for years now and have flashed two other phones to. ''
Thanks for the pollution.
Click to expand...
Click to collapse
wow ever think flashing to another company might be doin something? my phone was a pita to root im a total noob ran unrevoked stopped pulled the bat. red triangle restarted unrev picked up quit third time it restarted the whole process but ran thru and rooted me so i dont know metro pcs..i see their booths but sprints always been good to me
I cant use adb and visionary does not seem to work.
Is there a way to root the Gingerbread rom without having to get adb to work?
Because it will not work for me.
Far as I know you'll need adb. Keep trying. You'll get it. When I had a backflip over a year ago. I went crazy trying to understand how to root. Now adb is easy. Easier with win xp I think.
Sent from my T-Mobile G2 using XDA App
myphonesbetter said:
I cant use adb and visionary does not seem to work.
Is there a way to root the Gingerbread rom without having to get adb to work?
Because it will not work for me.
Click to expand...
Click to collapse
Unfortunately not; there are some "no adb required" guides but they tend to have a high brick rate.
How is adb not working for you?
Sent from my HTC Vision using XDA App
Idk ive always had problems with adb on my computers.
I was having a problem finding a driver but i found one on a youtube video from g2hacks.
Heres the link.
http://g2hacks.com/g2-drivers/g2-phone-windows-drivers-download/
Incase anybody else is loosing their mind clicking all the links in the how to's on this forum. which all just take you in circle. like getting the run around from an insurance company.
I seem to be recognizing ill try to push some files now.
myphonesbetter said:
Idk ive always had problems with adb on my computers.
I was having a problem finding a driver but i found one on a youtube video from g2hacks.
Heres the link.
http://g2hacks.com/g2-drivers/g2-phone-windows-drivers-download/
Incase anybody else is loosing their mind clicking all the links in the how to's on this forum. which all just take you in circle. like getting the run around from an insurance company.
I seem to be recognizing ill try to push some files now.
Click to expand...
Click to collapse
Did you not go to the wiki which has a step by step guide, including links?
Sent from my HTC Vision using XDA App
Yah my problem this time was that i didnt have a driver. but that link worked. none of the ones on this website would though.
Everywhere i read it says i have to downgrade first. i was following the guide but i have to install the original g2 OTA signed.
Now ive ran into the problem that every copy i try to download is corrupt. just my luck. a 30 min process takes 5 hrs. or more.
I got to the point where adb reboot my phone into bootloader after the the temp root and did not realize the update.zip would not work. now im afraid to turn my phone back on. i dont want to have to do everything over again.
Ok figured that out. Windows xp was set to hide file extensions so i was nameing is pc10img.zip.zip
Guess ill see what problem lies ahead. i swear i could write a 100 step write up of what i have to do for a 15 step write up.
Got it rooted. Just took all day. Could not let my phone win. LOL.
Havent spent that long on a phone since i installed android and full WP7 dual boot on my HD2.
I run xp x86 on a computer that came with vista. maybe thats why i was having a problem.
I was able to install the nand backup from my old phone right to this phone. just a million hours of tinkering. I cant imagine how frustrated the developers get trying to make these roms work. i bet there compulsive about it though.
If someone sees this please put these drivers on the how to sticky section.
All the other links either would not work for me or were broken.
myphonesbetter said:
Got it rooted. Just took all day. Could not let my phone win. LOL.
Havent spent that long on a phone since i installed android and full WP7 dual boot on my HD2.
I run xp x86 on a computer that came with vista. maybe thats why i was having a problem.
I was able to install the nand backup from my old phone right to this phone. just a million hours of tinkering. I cant imagine how frustrated the developers get trying to make these roms work. i bet there compulsive about it though.
If someone sees this please put these drivers on the how to sticky section.
All the other links either would not work for me or were broken.
Click to expand...
Click to collapse
XP and vista shouldn't matter with the chip architecture so long as it supports it. But then again if it didn't, it would not install at all, and if it did for some weird reason it would not boot so that wasn't your problem.
Previously I had installed on my phone (I believe, but could be mistaken) a Twilight Kernel and Hurricane v1.6 Rom. Well, I had nothing but problems with the rom, and put up with them for some time, just because I didn't have time to go through and find a rom I liked and flash it. I decided to do just that yesterday.
Apparently my mind broke and I did something wrong (probably numerous things). I had first attempted to put the shiney new CWM9 with Shadow Kernel on, rather, I made the mistake of trying to just put the Shadow Kernel on after having done a full (triple) wipe on my phone. I got the boot loop for the kernel since there was no rom (duh) loaded. Okay, no problem, I'll toss a rom on the SD and boot into CW3 and flash it? Yeah, not so much. I got a short "Samsung" logo boot loop and could not get into CW3 after that.
So, I Odin'd it back to EL30, thinking I'll just start from fresh, right?
Wrong.
Next in the series of mistakes I made, I forgot that I had already downloaded and installed the Samsung drivers (don't ask, my brain was apparently on leave yesterday) and attempted to re-install them. They did not like this and would not progress and I had to End Process the install from Task Manager. I then uninstalled the drivers completely fearing that I may have corrupted them by trying to re-install and then EP'ing them.
I then re-installed them, or so I thought. Plug phone in and start again with One Click Root. Fail. The script couldn't find my device.
Hours of searching and trying different things later, script still couldn't find my device, though I now have both the phone recognizing there is a USB connection, and the computer has stopped yelling at me that there are no drivers (I believe it finally gave up and installed the Windows drivers for it). But still can't get it rooted or do anything but stock stuff.
So..
1:Samsung drivers won't install, running Windows 7-64 Ultimate; error at end of install just states: "The MMS InstallWizard was not successfully installed SAMSUNG USB Driver for Mobile Phones v1.3.450.0."
2hone previously recognized USB Debug mode, but no longer. Will only Recognize standard USB connection, and with the connection made to PC, the script will not recognize the device.
3:adb for all intensive purposes does not appear to be loading..per the message from the script "Root was not obtained after 60 seconds. Make sure the phone is connected and that adb is working. If adb shell isn't root, reboot the phone and try the script again." I've rebooted numerous times, but I'm pretty certain that since it's not going into Debug, it's just not being recognized.
I have even tried Gingerbreak with no luck, just continuously sits on the rooting screen, but never proceeds (upwards 45 minutes I let it go).
Please please please please help me fix all the mistakes I did and get this thing working again and get the damned drivers installed proper.
(Baseband-S: D700.0.55.EL30, Kernel version 2.6.35.7, Build number: Gingerbread.EL30)
Note* I am happy with any root/kernel/rom at this point, I don't care, I just want the damned thing rooted again.
And of course after I finally cave and post for help, I find the thread where it clearly states OneClick Root no longer works for Gingerbread...so we'll add that into the mistakes I made...
Question still stands, how do I get this rooted again?
Qbking77 youtube him...
Or I could do it for you remotely via teamviewer... either way
Sent from my SPH-D700 using xda premium
AtrophiedAnnie said:
And of course after I finally cave and post for help, I find the thread where it clearly states OneClick Root no longer works for Gingerbread...so we'll add that into the mistakes I made...
Question still stands, how do I get this rooted again?
Click to expand...
Click to collapse
If you are up and running EL30 just Google How to Root Samsung Epic on EL30 and a qbking77 youtube video will pop up and all the links are there as well for the files you need. If you are not up and running then you need to go into the Roll Up sticky thread in Development and click on How to Restore a semi-bricked Samsung Epic....all links are there for that including 64bit drivers.
Sent from my SPH-D700 using xda premium
Found it all, getting it working now. Thanks all. We'll chalk this up to ...noobi-ness....(ignoring that I've been rooted and doing this for a year now... >.> )
AtrophiedAnnie said:
Found it all, getting it working now. Thanks all. We'll chalk this up to ...noobi-ness....(ignoring that I've been rooted and doing this for a year now... >.> )
Click to expand...
Click to collapse
Sounds more like serious root rust to me. Gotta keep up...lol. Samsung tries to make it harder to root...that works for 5 minutes around here...LOL.
Sent from my SPH-D700 using xda premium
IT'S DONE!!! Again thank you both so much1
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.
All I want to do is flash back to stock, I feel like I am gonna lose my my mind or go buy a new phone. I have mostly spent a solid 10 hours of time trying to get it to work.
I have been endlessly looking, searching, trying all these different methods to get my ls980 to connect to my pc. So basically everytime I have hooked it up it comes up as unreconized or unknown device doesn't connect.
List of things: Latest LG mobile drivers I have installed them through there exe and tried to install them manually when the ! comes up on the device. I have tried my laptop and my desktop every usb in all of them. I have tried the stock cable, and about 8 other different cables. I have tried it in debugging mode with mtp and without debugging. I tried the support tool as well. Tried composite usb setting.
I guess I am at a loss at this point to what even to try besides sending it to be repaired. Which I don't feel like it's a phone problem and I am just missing something I can't find, I say this because the phone charges perfectly fine and no damage to the usb port at all. If anyone has good information or just a direction I can go will be greatly appericated.
Dirty Grimace said:
All I want to do is flash back to stock, I feel like I am gonna lose my my mind or go buy a new phone. I have mostly spent a solid 10 hours of time trying to get it to work.
I have been endlessly looking, searching, trying all these different methods to get my ls980 to connect to my pc. So basically everytime I have hooked it up it comes up as unreconized or unknown device doesn't connect.
List of things: Latest LG mobile drivers I have installed them through there exe and tried to install them manually when the ! comes up on the device. I have tried my laptop and my desktop every usb in all of them. I have tried the stock cable, and about 8 other different cables. I have tried it in debugging mode with mtp and without debugging. I tried the support tool as well. Tried composite usb setting.
I guess I am at a loss at this point to what even to try besides sending it to be repaired. Which I don't feel like it's a phone problem and I am just missing something I can't find, I say this because the phone charges perfectly fine and no damage to the usb port at all. If anyone has good information or just a direction I can go will be greatly appericated.
Click to expand...
Click to collapse
Is your device functioning normally, besides from this? Also, did you use the T-mobile drivers?
tabp0le said:
Is your device functioning normally, besides from this? Also, did you use the T-mobile drivers?
Click to expand...
Click to collapse
It works just fine, only notable thing that I never figured out was why OTA updates don't ever take, it's still on ZVC. I tried the T-mobile d802 drivers as it was suggested by another post I saw on here.
And you've removed all drivers to android and lg for it.
secret.animal said:
And you've removed all drivers to android and lg for it.
Click to expand...
Click to collapse
Correct, I uninstalled them, tried new ones a couple different ways from other posts, and removed them and tried again. Right now I just have them all uninstalled. Trying to figure out if it's something that's stopping it. In error I did forget that a couple times it reconized it but would :fail to start code 10.
Which version of windows are you running? On both desktop and laptop???
secret.animal said:
Which version of windows are you running? On both desktop and laptop???
Click to expand...
Click to collapse
Windows 7 64-bit home premium on both.
Dirty Grimace said:
Windows 7 64-bit home premium on both.
Click to expand...
Click to collapse
OK, that shouldn't be the problem. Zvc yet updates do not take.
Is it rooted?
And it is running on sprint network?
secret.animal said:
OK, that shouldn't be the problem. Zvc yet updates do not take.
Is it rooted?
And it is running on sprint network?
Click to expand...
Click to collapse
Long story short, it's on ZVC, even with other updates that came up it would never update past it. I took it into sprint several times they didn't know why, I did root it as one guy said that was an option, I used stump root, but then I unrooted as I felt I was getting into something too complicated. It is on the sprint network, about 90% of the time and all the times I tried to update previous to the root/unroot. But I am not trying to update it since the root, mostly trying to restore to stock and start overish.
I'm thinking maybe a virtual machine with Linux might find it. If it can then there is something. And maybe we can redo the partitions and such.
secret.animal said:
I'm thinking maybe a virtual machine with Linux might find it. If it can then there is something. And maybe we can redo the partitions and such.
Click to expand...
Click to collapse
I will check with a couple guys see if I can find someone with a machine with Linux this weekend. Thanks a lot for you on going help.
I have this phone at least for another year. So at least someone out here is still willing to help.
secret.animal said:
I have this phone at least for another year. So at least someone out here is still willing to help.
Click to expand...
Click to collapse
I was unable to find anyone outside local computer store that I know. Kind of problem finding that in rural midwest. I also tried installing drivers in vista compatability as that was suggested no luck..
Dirty Grimace said:
I was unable to find anyone outside local computer store that I know. Kind of problem finding that in rural midwest. I also tried installing drivers in vista compatability as that was suggested no luck..
Click to expand...
Click to collapse
As for driver removal, one thing I remember with the nexus devices. There is wugfresh nrt, nexus root toolkit. Let me see which application or program they loaded for removal before reinstall of drivers. I know they have 2 places you check into.
Dang, I'll have to try to load them via a windows emulator. I'm running Linux right now.
secret.animal said:
As for driver removal, one thing I remember with the nexus devices. There is wugfresh nrt, nexus root toolkit. Let me see which application or program they loaded for removal before reinstall of drivers. I know they have 2 places you check into.
Dang, I'll have to try to load them via a windows emulator. I'm running Linux right now.
Click to expand...
Click to collapse
Let me know.. I am kinda at the point where I might try to find someone to flash it back to stock, and just activated my old phone til it gets back.. like I am past the point of frustration and no legit just don't get why, since all my other devices have zero issues connecting.