Related
Okay, this might not be the place to get some divine intervention to start (or stop) happening, but I'm really starting to get a nervous breakdown and I desperately need some help. I'm going to tell you my story, because it's my last resort before throwing this phone in a fire and never buy anything Samsung related ever.
So the phone came out of the box and for some magic reason I got the bootloader unlocked and phone rooted. It all started with installing CWM I think. This stopped my phone from taking OTA updates. Of course I could have known, but for some reason I installed CWM. I don't know why! I regret it, I don't even want a different ROM installed, I thought it was necessary to root the phone. So when I got the OTA, at first I was like YEAH YEAH, but then the on the back laying android with the exclamation mark turned up and I felt like I wanted to kill someone. It was 2 in the morning and I had to get up early to go to Dublin for two weeks. This was really not the time...
So after trying a few times of getting the OTA update message again and failing every time I got it, I started searching. Yes, CWM is installed so you can't OTA they all said. Nice, now I hate on the back laying androids AND CWM. Of course the one to hate is me, but I already hate myself so that's no use. Anyway I used the Galaxy Nexus Toolkit 5.6 to put back stock recovery. Now I had to wait a few weeks again before the update turned up again... By this time the phone started to be REALLY slow when scrolling through the home screen(s). It also is empty before the day is done, but I don't know if that's because of the phone being f'ed up or because I'm too demanding.
Anyway, back to the story. Finally the update came about a week ago, and again I was like YEAH YEAH! But then the on the back laying android with the exclamation mark turned up and I felt like I wanted to kill someone. To make things more fun it did a reset of my Go Launcher, 7 screens of widgets and autistic arranged shortcuts gone... Of course I wanted to try again, so this morning the OTA came again and had the same result. By now I killed quite a few, so this has to end, but don't worry there is more torment ahead.
I can't figure out what is wrong now, so I thought, f~ this s~, this phone deserves a full undress and back to the womb operation. So installing all Galaxy Nexus Toolkit v6.0 stuff and drivers. Connect phone, start toolkit, choose 3 (GSM 4.0.2. build ICL53F), phone turns up in main menu, try to put back recovery, -waiting for device-...
It stopped... Or it didn't really stop, it just stood there saying, -waiting for device-... So again a few innocent people died. Tried a different choice, (relock bootloader, just to give the phone a good beating) -waiting for device-...
I raged, pulled my hair, again killed a few, silently cried in a corner and finally started typing this eulogy...
Please kind sirs and madams, help me get this phone back to stock 4.0.4, accepting OTA, bootloader unlocked and rooted, I'm really desperate...
Why did you even root it? If u have root and cwm, you should be able to flash the rooted version of whatever stock os update you want. OTA's are a waste, you just wait a few hours for xda devs to root it and make it flash able.
Sent from my Galaxy Nexus using xda premium
How do you proceed?
First you need the SDK for you system
http://developer.android.com/sdk/index.html
After this you have to start the SDK manager and install "Android SDK Tools" and "Android SDK Plattform-tools" if you are using Windows you have to install USB drivers too. You could find this under the point "Extras".
After that you have to download the factory image to clean your device, once.
(Notice your SD-Card gets wiped)
https://developers.google.com/android/nexus/images
Look for right version, which fits to your device.
Now you have to bring your telefon into the bootloader by pressing all 3 buttons at the same time Volume+/Volume-/Power. After this you have to unlock your bootloader if you don't already done this.
Now plug in your phone into your computer an go into the unpacked folder from your factory image. There would be an file called flash-all. You have to run this file. Now your phone is flashed with stock rom, stock kernel newest baseband and stock recovery. Now you get ota updates from google. After this you should look for an howto root your phone in the developer section. You don't have to install clockworkmod recovery for rooting. But clockworkmod isn't change the ota. You get OTA with cwm.
Hope i understand your problem an you could understand my bad english. But i want to help. If some questions ask here into the thread.
regards
theSlack said:
Why did you even root it? If u have root and cwm, you should be able to flash the rooted version of whatever stock os update you want. OTA's are a waste, you just wait a few hours for xda devs to root it and make it flash able.
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I'm out of the house a lot, leaving for Brussels in a couple of hours. I don't want the hassle anymore. I just want to be able to leave the house to go to another hotel and update OTA. I don't have time for all this flashing stuff.
Sent from my Galaxy Nexus using XDA
When the Galaxy Nexus Toolkit says "-waiting for device-..." you need to turn off your phone, press the volume down then the volume up then the power button together. Once you have done that the Galaxy Nexus Toolkit will continue.
There is also tutorials on youtube on how to use the Galaxy Nexus Toolkit.
I hope that helps.
If you want to head back to stock ROM, then one of the ways to do it would be to install Android SDK & then follow the instructions from Google developers site.
Else you can try using the Galaxy Nexus Toolkit to do this for you. I think the latest version is 5.7.
Android SDK - http://developer.android.com/sdk/installing.html
Android Images - https://developers.google.com/android/nexus/images#yakju
Galaxy Nexus Toolkit - http://windows.podnova.com/software/5996358.htm
smsmad said:
When the Galaxy Nexus Toolkit says "-waiting for device-..." you need to turn off your phone, press the volume down then the volume up then the power button together. Once you have done that the Galaxy Nexus Toolkit will continue.
There is also tutorials on youtube on how to use the Galaxy Nexus Toolkit.
I hope that helps.
Click to expand...
Click to collapse
Ah yes, I now see where I went wrong with the toolkit, I didn't put the phone in fastboot. Stupid...
How is the stock recovery supposed to look like? After putting back stock recovery with the GN Toolkit, I press 'vol+/vol-/power' and choose recovery. It then displays the belly up android with exclamation mark. Is that the way it should be? Am I doin' it wrong?
yes it is the stock recovery. But you dont need it. Flashing everything into fastboot mode(bootloader)
So, I'm currently running a stock phone, but OTA won't update my phone...? Why is OTA constantly failing if I'm running everything stock? Is my bootloader supposed to be locked? Is a rooted phone not updated OTA?
If you flashed the latest Factory-Image there is no OTA out there. It is the newest version of ICS for your Device.
Maybe i don't understand what you mean with failing OTA. Could you explain it a little bit more?
As I said in the long story, I'm currently 4.0.2. and every time when my phone says, "You have update 4.0.4. standing by, please reboot" it fails.
i would prefer to flash the factory image and root your phone again
then you have a cleaned phone and OTA should work but you don't need them because you are at latest version.
https://developers.google.com/android/nexus/images
i wrote how you could flash it page before, remeber you wipe your data from sdcard
Lex_Michdeandroid said:
So, I'm currently running a stock phone, but OTA won't update my phone...? Why is OTA constantly failing if I'm running everything stock? Is my bootloader supposed to be locked? Is a rooted phone not updated OTA?
Click to expand...
Click to collapse
I don't know if I can answer why the OTA isn't working (I'll leave that to smarter men than I), but having an unlocked bootloader and root access won't stop the OTA. I had my phone in that state when the 4.0.4 update came out and all was fine, just had to run the command to get root of my phone again as OTA removes root.
Ah great! S~ has just hit the fan, it's bootlooping after trying option 8 (flash stock rom from google). Oh I really am going to kill myself sooner or later...
Edit: not killing myself yet, just had to pull the battery... Let's see what I f~ up next...
Very strange you problems i don't know the Toolkit and don't know how it flash the stock rom. But i could imagin that it only flash rom and not the other things like recovery and so on.
Try out the hard way without toolkit and use sdk and included batch file into the factory image. it is the clean way and you see whats done.
Ok, I now rebooted the phone after option 8 in the toolkit and it seems I'm running 4.0.4. I have to go to Brussels now for two weeks, but I'll try to post some screenshots later. I'll also be back to thank all of you for holding my hand, I just don't have the time right now. Of course this won't be my last problem (I still have a TF101 that needs some RMA action), but I hope I won't be needing too much time consuming support anymore.
Just got in the hotel, and unable to use my phone in Belgium. No available network... Wifi works, 2G/3G works in The Netherlands, 2G/3G unavailable in Belgium...
Screenshot of my device: http://oi46.tinypic.com/34xp89y.jpg
Sent from my Galaxy Nexus using XDA
Just tried my SIM in a different phone, problems are with my network. Phone works with different SIM, so false alarm.
Sent from my Galaxy Nexus using XDA
If you dont want to root and or flash roms, and knowing android its buggy and you gotta be stuffing with the phone all time to be able to be up to date, cuz even google releases updates oftem and even with OTA things can go wrong, meaning you have to do stuff again...
Dont blame Samsung or google the whole system needs some fixes all time.. I was devoted to stock but after i tried AOKP (Milestones) i wont ever go back to stock and or another rom, these guys has loads of features for a better user experience, stable as hell, and great support, but as you show with your very active/traveling life and those killer instints (poor innocent people), why dont you just go Iphone?
No need to flash anything and will plain work... Thats it no need to worry about anything but being an apple fan boy xDD
Cheers
Sent from my Galaxy Nexus using xda premium
msedek said:
If you dont want to root and or flash roms, and knowing android its buggy and you gotta be stuffing with the phone all time to be able to be up to date, cuz even google releases updates oftem and even with OTA things can go wrong, meaning you have to do stuff again...
Dont blame Samsung or google the whole system needs some fixes all time.. I was devoted to stock but after i tried AOKP (Milestones) i wont ever go back to stock and or another rom, these guys has loads of features for a better user experience, stable as hell, and great support, but as you show with your very active/traveling life and those killer instints (poor innocent people), why dont you just go Iphone?
No need to flash anything and will plain work... Thats it no need to worry about anything but being an apple fan boy xDD
Cheers
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
I rather eat my own shhhhh... shorts than buy something with an apple on it. With the help of you guys it always works out fine, it just takes a life or two.
Sent from my Transformer TF101 using XDA
Hello,
I tried to root my new Nexus 7 (2013). I am not able to post the link of the tutorial which I followed (from androidrootz). I tried contacting the author of that tutorial - he did try his best but was not able to change the state.
When about to complete the entire process, close to the finish - I am not able to get inside the "Recovery Mode" to install Super User SU. i.e. When I press recovery mode in the bootloader I get the Google logo and it stays there till battery runs out.
Now when I start the tablet normally, I get the Google logo and the nexus logo. Then nexus logo stays there till the battery runs out.
I am a developer and I kinda need the tablet to run. My main purpose of rooting the tablet is to use certain admin feature and install a custom ROM.
If I could straighten up my tablet to work the way it does - that would really great. I am not bothered about the loss of data at all.
I could use both Windows and Mac to get things in order. At this moment I am not sure what the problem is nor do I know what to do.
If someone could guide me thro' to get the tablet up and running the normal, I highly appreciate it.
Thank you and regards,
Karsnen.
karsnen said:
Hello,
I tried to root my new Nexus 7 (2013). I am not able to post the link of the tutorial which I followed (from androidrootz). I tried contacting the author of that tutorial - he did try his best but was not able to change the state.
When about to complete the entire process, close to the finish - I am not able to get inside the "Recovery Mode" to install Super User SU. i.e. When I press recovery mode in the bootloader I get the Google logo and it stays there till battery runs out.
Now when I start the tablet normally, I get the Google logo and the nexus logo. Then nexus logo stays there till the battery runs out.
I am a developer and I kinda need the tablet to run. My main purpose of rooting the tablet is to use certain admin feature and install a custom ROM.
If I could straighten up my tablet to work the way it does - that would really great. I am not bothered about the loss of data at all.
I could use both Windows and Mac to get things in order. At this moment I am not sure what the problem is nor do I know what to do.
If someone could guide me thro' to get the tablet up and running the normal, I highly appreciate it.
Thank you and regards,
Karsnen.
Click to expand...
Click to collapse
If you can get into bootloader, you should be able to recovery. I suggest you follow the guide here:
http://forum.xda-developers.com/showthread.php?p=44888268#post44888268
and choose the flash-all option which will wipe user data and start fresh.
sfhub said:
If you can get into bootloader, you should be able to recovery. I suggest you follow the guide here:
http://forum.xda-developers.com/showthread.php?p=44888268#post44888268
and choose the flash-all option which will wipe user data and start fresh.
Click to expand...
Click to collapse
It worked. Thank you so much.
I just want to know, if you could recommend a guide for rooting the new nexus 7 on windows machine, what would that be?
Thank you once again.
Check in the stickies for detailed instructions. If you just want a simple summary:
http://forum.xda-developers.com/showthread.php?p=44597339#post44597339
sfhub said:
If you can get into bootloader, you should be able to recovery. I suggest you follow the guide here:
http://forum.xda-developers.com/showthread.php?p=44888268#post44888268
and choose the flash-all option which will wipe user data and start fresh.
Click to expand...
Click to collapse
So I'm using a Mac OSX 10.8.4, and the new Nexus 7 (2013) version. I unlocked my bootloader, but I cannot get it into recovery mode, and I'm a little nervous. This is my first android device, but I've been an avid iOS jailbreaker since the OG iPhone. Can any of you point me to an extremely thorough guide on how to both fix my current issues, and then properly Unlock, Recovery, Root, and Flash Custom ROMs to this tablet?
Thank you so much.
tr00gle said:
So I'm using a Mac OSX 10.8.4, and the new Nexus 7 (2013) version. I unlocked my bootloader, but I cannot get it into recovery mode, and I'm a little nervous. This is my first android device, but I've been an avid iOS jailbreaker since the OG iPhone. Can any of you point me to an extremely thorough guide on how to both fix my current issues, and then properly Unlock, Recovery, Root, and Flash Custom ROMs to this tablet?
Thank you so much.
Click to expand...
Click to collapse
Buddy,
I was in the exact similar position as you are. Do not fear. Just follow the response I got above. It will help you.
Just follow it.
regards,
Karsnen.
karsnen said:
Buddy,
I was in the exact similar position as you are. Do not fear. Just follow the response I got above. It will help you.
Just follow it.
regards,
Karsnen.
Click to expand...
Click to collapse
Are the commands the same in terminal, or should I run windows in a VM to use the command line?
The only cmd in that post is flash-all
It is the same. Get into the directory and enter flash-all when you have to, in the terminal.
When I'm in the VM in windows, I go to the directory, but then it says "flash-all" is not a valid command. What am I doing wrong? It won't work in Terminal either. Can you please walk me through it. I feel so stupid as is, but I can't figure out what I'm doing wrong.
tr00gle said:
When I'm in the VM in windows, I go to the directory, but then it says "flash-all" is not a valid command. What am I doing wrong? It won't work in Terminal either. Can you please walk me through it. I feel so stupid as is, but I can't figure out what I'm doing wrong.
Click to expand...
Click to collapse
Did you unpack the google image download twice? (per the instructions) Once to get the tar from the tgz and a second to get the files from the tar.
sfhub said:
Did you unpack the google image download twice? (per the instructions) Once to get the tar from the tgz and a second to get the files from the tar.
Click to expand...
Click to collapse
Ok, I MUST be using the wrong guide or something, because I don't have any files with a .tar extension. I promise I'm not this dumb, but I can feel my frustration making me dumber. Halp
course ndighdl
tr00gle said:
Ok, I MUST be using the wrong guide or something, because I don't have any files with a .tar extension. I promise I'm not this dumb, but I can feel my frustration making me dumber. Halp
Click to expand...
Click to collapse
OK, i forgot to download the image files from google. Now I'm doing it, and it says fastboot is not a valid command, and nothing is happening.
tr00gle said:
OK, i forgot to download the image files from google. Now I'm doing it, and it says fastboot is not a valid command, and nothing is happening.
Click to expand...
Click to collapse
Did you do step #3 in the guide?
http://forum.xda-developers.com/showthread.php?t=2428194
sfhub said:
Did you do step #3 in the guide?
http://forum.xda-developers.com/showthread.php?t=2428194
Click to expand...
Click to collapse
Is that link to the guide? there wasn't one on that link. I appreciate you replying this many times already, but I just need one set of steps to follow, that are clear and detailed. That's all. Do I need to use windows, mac or linux? I have a macbook pro, but I can run windows or linux in parallels if necessary. I just need to KNOW. Please.
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.
Hello everyone! I really need some help here I just got my brand new nexus 7, and I am trying to update from 4.3 to 4.4. I have a problem though, because it keeps getting stuck at about where the letter "A" is on the screen. The bar will sit there for hours and not go any further. I have tried restarting, two factory resets, and I have no idea what else to do. Please someone help? Thanks so much!
Since it's new, I highly recommend downloading the full stock 4.2.2, rather than spending time trying to update. The "flash-all.bat" file will do a full wipe and install 4.2.2 completely, with no need to get updates.
https://developers.google.com/android/nexus/images#razor
You will need to "unlock" first, which can be done easily through the Nexus Root Toolkit. After that, the same Toolkit can root your new N7, if you so desire.
http://www.wugfresh.com/nrt/
JakeReis said:
Hello everyone! I really need some help here I just got my brand new nexus 7, and I am trying to update from 4.3 to 4.4. I have a problem though, because it keeps getting stuck at about where the letter "A" is on the screen. The bar will sit there for hours and not go any further. I have tried restarting, two factory resets, and I have no idea what else to do. Please someone help? Thanks so much!
Click to expand...
Click to collapse
Don't rely on tools. Do it manually, it's easy. Watch the tutorials.
Unlock bootloader and install custom recovery http://www.youtube.com/watch?v=6k4rCaMPSQ8
Root http://www.youtube.com/watch?v=yTdUd-jlbP0&feature=youtu.be
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
I also do everything manually, but for the sake of newer owners getting used to the device, I'll refer them to the kit.
Hello, I am aware that I am a noob, but the issue I have is important to me.
When the android L developer preview came out I was thrilled, and thus proceeded to install it. I will spare you the details, but I ended up having everything on my Nexus 7 wiped except for TWRP. Now, me and my brother have attempted an adb push to get a rom on the tablet, but adb can't find the Nexus 7. Also, the Windows USB drivers refuse to be installed for the device (the process I used to do so was fully correct.) To actually post on XDA was my last resort after hours of research and attempting to revive my Nexus. Any willing advice would be great. Thanks!
doublewhamy said:
Hello, I am aware that I am a noob, but the issue I have is important to me.
When the android L developer preview came out I was thrilled, and thus proceeded to install it. I will spare you the details, but I ended up having everything on my Nexus 7 wiped except for TWRP. Now, me and my brother have attempted an adb push to get a rom on the tablet, but adb can't find the Nexus 7. Also, the Windows USB drivers refuse to be installed for the device (the process I used to do so was fully correct.) To actually post on XDA was my last resort after hours of research and attempting to revive my Nexus. Any willing advice would be great. Thanks!
Click to expand...
Click to collapse
Reboot to bootloader.
fastboot devices
If device shows up, flash stock firmware. Link in siggy.
Aerowinder said:
Reboot to bootloader.
fastboot devices
If device shows up, flash stock firmware. Link in siggy.
Click to expand...
Click to collapse
I appreciate the assistance!