Related
Good evening everyone,
I am hoping someone can help me. Last night i was in the middle of flashing a Rom (Green Lighting 3.0) and wanted to repartition my SD card. I have flash this ROM and repartition my SD many times and had no issue. I moved my info from my SD card to my computer, wiped and partitioned the SD like normal and no problem. I started putting the info back onto the SD and still no problem. I then tried to flash my rom back onto my phone and when I went to my sd card it said "Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory)" I then noticed that I couldnt do anything with my SD card. I have tried different SD cards and they do not show in my phone and I get the same msg still. I have put the card into PC and I can see everything there just cant access it.
To make things stranger, When trying to figure out whats going on, I notice that when I go to bootlader I see S-ON. I know I had S-OFF (Got my EVO last Christmas and rooted it then). Any else have this issue? Im not sure what caused this or what I can do to resolve the issue i was thinking about reflashing back to stock but I cant even put the img back onto my sd card which means im not sure how i would take it back to sprint....Thanks in advance.
Anyone? Can anyone at least help me get to the point where I can take it in to sprint and they cant tell that its been rooted?
Thanks
Would say fastboot but your also saying you don't have root not either.
Sent from my PC36100 using xda premium
lithid-cm said:
Would say fastboot but your also saying you don't have root not either.
Sent from my PC36100 using xda premium
Click to expand...
Click to collapse
Might need to reroot then use fastboot
Sent from my PC36100 using xda premium
Or if you want to get really snazy you can symlink the block device for the sdcard to a folder on data then use adb to push files to it. Then in reviving you can flash a new image.
Sent from my PC36100 using xda premium
Happened to me first thing you are rooted second thing what I did is format data on card and phone ( backup files on card) via fastboot then you would need to get to adb and type some code to be able to use the card then boot phone and flash a custom recovery I used rom manager if any questions I will try my hardest to help I wish I had help when this happened to me (took exactly 9 straight hours to fix)
sent from my HTC evolution running a freshly baked gingerbread with the 4gs in it
Thanks Cesarcerros and Lithid-cm for responding! Do either of you have the necessary steps to preform these steps or a link? Im not really familiar with adb (heck i have tried to get into it again but its not working) And for the rerooting option, would i use the new gingerbread root? Also, i cant get back into the rom so im not sure if that will affect things....again thanks!
elosogrande7076 said:
Thanks Cesarcerros and Lithid-cm for responding! Do either of you have the necessary steps to preform these steps or a link? Im not really familiar with adb (heck i have tried to get into it again but its not working) And for the rerooting option, would i use the new gingerbread root? Also, i cant get back into the rom so im not sure if that will affect things....again thanks!
Click to expand...
Click to collapse
Yeah wont affect my method I'm on my way to school but first thing I do is post up links and adb tutorials but you can always search meanwhile I get back
sent from my HTC evolution running a freshly baked gingerbread with the 4gs in it
cesarcerros31 said:
Yeah wont affect my method I'm on my way to school but first thing I do is post up links and adb tutorials but you can always search meanwhile I get back
sent from my HTC evolution running a freshly baked gingerbread with the 4gs in it
Click to expand...
Click to collapse
Thanks....i have been searching and trying a lot but no luck....hope im not making things worse
elosogrande7076 said:
Thanks....i have been searching and trying a lot but no luck....hope im not making things worse
Click to expand...
Click to collapse
I have scripts for setting up just about everything for android, sadly this only working in linux.I have not used windows in over 7 years. When I have helped people before they have always been able to get adb working following this guide here:
http://htcevohacks.com/htc-evo-hacks/how-to-install-android-sdk-and-adb-drivers-for-htc-evo-4g/
You will be able to use the new root method, but without an sdcard to flash anything might be pointless to focus on that. I would look into a decent disk utility and run a scan on the sdcard mounted to your pc somehow (Does the sdcard work when connecting it to a pc and only doesn't work while connected to the evo?). Might be able to simply reformat the sdcard to solve the issue. If there are bad blocks, try to repair them. I know that this all sounds like another language, but now you have some more information when looking up errors for your sdcard.
Thank you both for your help with this. I was able to get this working by downloading Hausx's auto root 2.5 tools and putting that in a folder on my c drive and using the dos prompt to get me into using fastboot. I then used the following commands and I was able to see the sdcard again:
SELECT "FASTBOOT"
PLUG USB
type in the "dos"
fastboot oem rebootRUU
fastboot oem enableqxdm 0
fastboot reboot
Again thank you both for your help and attention on this.
cesarcerros31, you said you had this happen before, do you know what casued it? I dont remember doing anything out of the normal so i was curious if it might be a hardware issues or something else u were able to figure out?
On a side note, Lithid-cm was learning Linuix easy or did it take some time? Im interested in networking and seeing that a lot of people in networking are familiar with linuix so i figured i should look into it.
Some of the Linux distros like ubuntu or mint are pretty easy for a windows user to get used to. U can always dual boot.
elosogrande7076 said:
On a side note, Lithid-cm was learning Linuix easy or did it take some time? Im interested in networking and seeing that a lot of people in networking are familiar with linuix so i figured i should look into it.
Click to expand...
Click to collapse
Honestly I am not really sure, I grew up kinda poor and was forced to use linux as we couldn't afford a brand new windows pc. I would find pc parts that people would throw out, and searching the internet I was only able to find linux that was free. Been using it ever since.
I think its easy, its just something to get used to.
Thanks for the advice Fitz. Thats how I learned about building and working on PC's....thanks again everyone.
elosogrande7076 said:
Thank you both for your help with this. I was able to get this working by downloading Hausx's auto root 2.5 tools and putting that in a folder on my c drive and using the dos prompt to get me into using fastboot. I then used the following commands and I was able to see the sdcard again:
SELECT "FASTBOOT"
PLUG USB
type in the "dos"
fastboot oem rebootRUU
fastboot oem enableqxdm 0
fastboot reboot
Again thank you both for your help and attention on this.
cesarcerros31, you said you had this happen before, do you know what casued it? I dont remember doing anything out of the normal so i was curious if it might be a hardware issues or something else u were able to figure out?
On a side note, Lithid-cm was learning Linuix easy or did it take some time? Im interested in networking and seeing that a lot of people in networking are familiar with linuix so i figured i should look into it.
Click to expand...
Click to collapse
I'm guessing my SD card died out I rebooted once and wouldn't turn on and would go to white screen then shut black and vibrate 5 times but that same command I typed and worked like a charm after good to see your back to work
sent from my HTC evolution running a freshly baked gingerbread with the 4gs in it
cesarcerros31 said:
I'm guessing my SD card died out I rebooted once and wouldn't turn on and would go to white screen then shut black and vibrate 5 times but that same command I typed and worked like a charm after good to see your back to work
sent from my HTC evolution running a freshly baked gingerbread with the 4gs in it
Click to expand...
Click to collapse
That is strange, i have noticed that my phone vibrates 4 or 5 times now when i reboot it and sometimes it wont start up till i remove the battery....hope its not dying...thanks again
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.
So about two weeks ago, while installing a new rom, I managed to format my storage before flashing the rom. After doing that, there obviously was no rom to flash. Or anything else for that matter. My phone now can only boot into recovery mode. When trying to turn it on, it goes as far as the google screen showing the unlock icon. I would surely appreciate any help from you guys. Thank you in advance and I apologize for anything noobish i have or undoubtedly will say in the future.
By the way, here is my set up:
Verizon Galaxy Nexus
Windows Vista 32 bit PC
Again, Thank you
I am not near my PC but you have to enter into fast boot mode and push your ROM.zip to your phone using adb
Sent from my Nexus 4 using xda app-developers app
When i last tried that, ADB would not recognize my phone
jaysondasher said:
When i last tried that, ADB would not recognize my phone
Click to expand...
Click to collapse
If you are running a custom recovery, ADB should work. You probably are having driver issues.
Fastboot, flash stock. If you're phone isn't being recognized, install drivers.
Sent from my Galaxy Nexus using xda app-developers app
cupfulloflol said:
If you are running a custom recovery, ADB should work. You probably are having driver issues.
Click to expand...
Click to collapse
ADB does work on a custom recovery. You're right, he's having driver issues, he's just too lazy to search. THIS QUESTION has been answered a zillion times and is well documented in efrant 101 stickied on General section.
a manta wrote this.
---------- Post added at 04:42 AM ---------- Previous post was at 04:39 AM ----------
peikojose said:
I am not near my PC but you have to enter into fast boot mode and push your ROM.zip to your phone using adb
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Go read efrant 101 sticked on General section, please.
jaysondasher said:
When i last tried that, ADB would not recognize my phone
Click to expand...
Click to collapse
Of course, fastboot mode doesn't have ADB. Only fastboot.
a manta wrote this.
I don't think it's a problem of me being "lazy". I have been searching for over 2 weeks to find a post that helped me, and I wasn't able to because people on here seem to assume you know exactly what you're talking about, and throw around fancy android lingo that I'm unfamiliar with.
But I have uninstalled the drivers I previously had for my nexus and am going to try again. I also deleted ADB I think, so I'll have to get that again.
So, I installed Samsung's drivers, then went to adb and tried to sideload a rom, but was given the error: "device not found". I had my phone plugged in and booted into the recovery mode. I dont know what I'm doing wrong.
To the OP i really hope you get things sorted out. But some advice if you really do not know anything about your device, about rooting or how to use your device in conjunction with a computer then you need to do a lot more reading and research. Using ADB, Fastboot and being able to have your computer recognize your Gnex is all the first essential part of beginning to unlock the bootloader and rooting the device. So you should be very familiar with this unless you either had someone else root your phone or you used a root toolkit which is the reason why you don't understand what the steps may be or the wording. Toolkit are the worst to use just because of that reason. Also the fact that you wiped your internal memory also leads me to believe you don't know what you where doing because before it deleted it it asked you 'are you sure'. Please spend some time reading and learning educate yourself, do not expect anyone to solve it for you. Every rom, every guide and post on here always starts off by warning you that you are solely responsible for what you are about to do. Read, read and read again.
Sent from the future via Tapatalk 4
jaysondasher said:
I don't think it's a problem of me being "lazy". I have been searching for over 2 weeks to find a post that helped me, and I wasn't able to because people on here seem to assume you know exactly what you're talking about, and throw around fancy android lingo that I'm unfamiliar with.
But I have uninstalled the drivers I previously had for my nexus and am going to try again. I also deleted ADB I think, so I'll have to get that again.
Click to expand...
Click to collapse
fancy android lingo?
This 'lingo' that gets tossed around is the basic knowledge one should know when customizing (rooting/flashing/modifying) their Android device.
Would you go and start modifying the engine in your car without some basic understanding of how it works, or what the parts are called and located?
Why would you treat your electronic devices any other way?
That post tells me you didn't even read the damn sticky I was talking about.
If you had read this, you would understand the "fancy android lingo" by now. And @jaysondasher, I have another link for you, here.
Have a nice day.
Don't boot into recovery. Boot into boot loader mode. Power and both volume buttons. Then, using fastboot flash stock.
Sent from my Galaxy Nexus using xda app-developers app
was able to get it figured out. Sorry if I frustrated any of you, but thank you for your help.
Sent from my Galaxy Nexus using xda app-developers app
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.
So with my wake up automatic update message this morning I decided to use Rumrunner and finally root. Couldn't have worked better honestly. Got in through Root Explorer, killed off the stuff I didn't want from the bloat and then got rid of the sounds and wallpapers I never use. Perfect, just as good as an experience as I had when I did the DInc2. Then I decided to make it even 'better' by getting rid of those annoying .odex files. I wiped them all, I don't know what I was thinking, I'm an idiot. I have a great phone that now can't get past the Verizon screen. How can I fix this as my wife is not amused with the cost associated with my stupidity. The laptop doesn't recognize the phone as even being there anymore. Is this a lost cause?
mySStery_machine said:
So with my wake up automatic update message this morning I decided to use Rumrunner and finally root. Couldn't have worked better honestly. Got in through Root Explorer, killed off the stuff I didn't want from the bloat and then got rid of the sounds and wallpapers I never use. Perfect, just as good as an experience as I had when I did the DInc2. Then I decided to make it even 'better' by getting rid of those annoying .odex files. I wiped them all, I don't know what I was thinking, I'm an idiot. I have a great phone that now can't get past the Verizon screen. How can I fix this as my wife is not amused with the cost associated with my stupidity. The laptop doesn't recognize the phone as even being there anymore. Is this a lost cause?
Click to expand...
Click to collapse
Can you boot in to recovery or bootloader (holding power+vol down)?
Sent from my HTC6500LVW using XDA Premium 4 mobile app
That I can
mySStery_machine said:
So with my wake up automatic update message this morning I decided to use Rumrunner and finally root. Couldn't have worked better honestly. Got in through Root Explorer, killed off the stuff I didn't want from the bloat and then got rid of the sounds and wallpapers I never use. Perfect, just as good as an experience as I had when I did the DInc2. Then I decided to make it even 'better' by getting rid of those annoying .odex files. I wiped them all, I don't know what I was thinking, I'm an idiot. I have a great phone that now can't get past the Verizon screen. How can I fix this as my wife is not amused with the cost associated with my stupidity. The laptop doesn't recognize the phone as even being there anymore. Is this a lost cause?
Click to expand...
Click to collapse
Put the stock odexed rom from my thread in development section in your adb/fastboot directory on your PC.
Enter Recovery, assuming you installed a custom recovery.
If not, do that first, using the links in Flyhalfs threads in our Verizon One Original Dev section.
In Recovery go to Advanced in TWRP I believe and do adb sideload > swipe to sideload.
Then you will need to enter in terminal: adb sideload filename.zip from within the fastboot directory with the stock file in that same directory.
Use the filename of the zip you are sideloading. Once its done pushing, it will flash the rom and then you can reboot.
I had tried straight off after the root to install CWM and it gave the option to do TWRP. I had a blank black screen and then kind of stalled so I forced it into the bootloader screen and just reset. In the present time if I attempt the recovery selection it just stalls again, a black yet obviously backlit screen. My new download of ADB does not look the same as it had when I did the last phone either. I don't know what I've fouled up here.
I'll send it out at this point to make the pain go away and have someone undo it.
mySStery_machine said:
I'll send it out at this point to make the pain go away and have someone undo it.
Click to expand...
Click to collapse
I can try and walk you through getting fastboot or adb set up so that you can try fixing it on your end.
It's also pretty well laid out in guides on Google.
If you really wanted to have it fixed for you, I'm about 12 hours or so south of where you are if you wanted to mail it here and back.
Up to you, hit me up via PM if you decide you wanna mail it.
Otherwise, myself and/or others will gladly help you undo it I'm sure man.
Then you wouldn't have to be without it for a few days.
You must be near my wife's family then in Santa Cruz. I can't be down without a phone long and I run a repair facility (NOT PHONES OBVIOUSLY) so my days smoke me mentally, today was case in point. I will try to collect myself get the DInc2 running and charged (which was the only reason I traded) and see about tackling it tomorrow night. If you would, please send me a PM with your number and I will call if I have need of adult supervision when attempting it once again. Funny thing is, is that I had already downloaded and dropped your .15 debloated into ADB for flash before even posting here.
mySStery_machine said:
You must be near my wife's family then in Santa Cruz. I can't be down without a phone long and I run a repair facility (NOT PHONES OBVIOUSLY) so my days smoke me mentally, today was case in point. I will try to collect myself get the DInc2 running and charged (which was the only reason I traded) and see about tackling it tomorrow night. If you would, please send me a PM with your number and I will call if I have need of adult supervision when attempting it once again. Funny thing is, is that I had already downloaded and dropped your .15 debloated into ADB for flash before even posting here.
Click to expand...
Click to collapse
Sounds good, I'll shoot you my gmail/Hangout info and we can get you squared away I'm sure.
Yeah, I'm up above there just a little, about 2 and a half hours or so from there.
Sounds good, I'm ready to tackle tonight whenever and for however long it takes.
Ok, have deleted and redownloaded the ADB files, yours as well as the TWRP. I have the recovery and your file chilling out in C:\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools . What now my new found savior?
Ok, knocked out the TWRP stuff myself and can get it to sideload screen but the command promp screen shows this when trying to push it over: C:\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb sideload 1.10.605.15_M7_WL_JB_50_VZW_Deodex_Full.zip
* cannot read '1.10.605.15_M7_WL_JB_50_VZW_Deodex_Full.zip' *
mySStery_machine said:
Ok, knocked out the TWRP stuff myself and can get it to sideload screen but the command promp screen shows this when trying to push it over: C:\Android\adt-bundle-windows-x86_64-20131030\sdk\platform-tools>adb sideload 1.10.605.15_M7_WL_JB_50_VZW_Deodex_Full.zip
* cannot read '1.10.605.15_M7_WL_JB_50_VZW_Deodex_Full.zip' *
Click to expand...
Click to collapse
Double check the md5 of the downloaded file.
Also shorten the path to the file, at least the folder names leading up to it, so that it's more direct.
Less chance of error or too deep of a path.
Something Like:
C:\Android\sdk\sdk\platform-tools>adb sideload 1.10.605.15_Deodex_Full.zip
Click to expand...
Click to collapse
You will have to rename a directory and a file or so to get it like that and this may not be the issue, but should certainly eliminate potential for issues.
Getting a 'device not found' error and the HTC driver when rebooting says did not load. I see on the MOUNT tab in TWRP different options, one of which is System which was not ticked should I click that and let it go try?
mySStery_machine said:
Getting a 'device not found' error and the HTC driver when rebooting says did not load. I see on the MOUNT tab in TWRP different options, one of which is System which was not ticked should I click that and let it go try?
Click to expand...
Click to collapse
Yeah try that, you may need to grab HTC Sync and install it if you haven't if your existing drivers aren't cooperating.
MD5 was corrupt, I finally got it to push.
Used pdaNet for drivers.
mySStery_machine said:
Used pdaNet for drivers.
Click to expand...
Click to collapse
Cool, glad that worked.
If you have any further issues or success, let me know.
Sounds like you should be good to go though.
Downloading another version to see if I can get the info across and get this One cooking again!
So should I do the other .zips below the post with your links for the firmware?