So I soft bricked my phone last night, the "[TUTORIAL][ROM] How to fix your phone and apply the update" helped me get everything back to normal. But now when I go to connect my phone to my computer with the USB cable it doesn't wanna connect. It charges the phone, but there's no "USB connected" notification on the phone OR the computer. I've tried putting the phone in USB debugging mode which gets me a "USB connected" notification on the phone, but nothing on the computer, and I can't access any files. I've tried using different USB ports on the computer and still nothing. Any ideas?
Edit: Neeeeevvermind! I should just stop posting questions because I seem to find the answer right after!
What was the answer?
same thing happened to me (sort of) im fully stock not rooted, and for some reason the usb wouldnt connect to computer only charged never game me option to mount sd card. i tried everything, dl'ing drivers from samsung and tmo, nothing worked, spent 2 hours going over the exact same steps between tmo and samsung tech support, **** is busted bro, the more and more i read about problems with the galaxy s the more i feel pissed. just call tmo and tell them you have tried everything from dl'ing drivers to resetting phone and nothing works. i guarantee they will send you a replacement like they did for me. the best part of our phones is the storage (internal, and sd card) w/out access to those the phone is as good as a motorola razor (useless)
Well I'm not sure if I just didn't notice it, or it actually wasn't there, But I put the phone in USB debugging mode and connected it to the computer. Usually I can access files just by plugging it in, but I had to select "Mount" for the computer to recognize it. Pretty obvious solution I know!
@erhan82
That is annoying that you had stock everything and it still didn't work. Usually the solution is really simple though, like a soft reset or something.
I just hate when people complain about the Vibrant having problems when they modify a bunch of stuff. The manufacturers didn't intend for us to root and hack our devices, (as much as we would have liked them to) so when something goes wrong, you can't really blame Samsung or T-Mobile. Well...you can, but when you modify stuff it's usually your fault. And there is definitely exceptions!!! I'm just saying... And Samsung is really slow with rolling out updates, which is very annoying! Anyway.
@Xianku i tried soft reset (i tried that before i even called tech support), i tried everything. And knowing what a pain in the ass it is calling tech support (between waiting to speak to sum1, and having them ask me to do steps i've already done). To be honest i havent seen any crazy development for the vibrant yet. At least not on the level of g1 development. But in all fairness samsung hasnt released kernels yet so once they are here then i'll root.
Xianku said:
So I soft bricked my phone last night, the "[TUTORIAL][ROM] How to fix your phone and apply the update" helped me get everything back to normal. But now when I go to connect my phone to my computer with the USB cable it doesn't wanna connect. It charges the phone, but there's no "USB connected" notification on the phone OR the computer. I've tried putting the phone in USB debugging mode which gets me a "USB connected" notification on the phone, but nothing on the computer, and I can't access any files. I've tried using different USB ports on the computer and still nothing. Any ideas?
Edit: Neeeeevvermind! I should just stop posting questions because I seem to find the answer right after!
Click to expand...
Click to collapse
Where can i view the tutorial because my phone got into bootloop and wont connect to computer properly and i need help Thanks!
I received a Nook Tablet 8GB from a friend that has it messed up pretty badly.
I have tried option 1 on the thread below and was able to boot into CWR and install the partition zip, then i used MiniTool Partition wizard to setup microsd as described, then place the update zip onto microsd.
http://forum.xda-developers.com/showthread.php?p=36492731
Once i put back into nook and boot up it goes to call customer service.
I also tried the following method here
http://forum.xda-developers.com/show....php?t=1663836
I get the green check mark and after reboot i get call customer service.
Again, im not sure what was done to this device before. Just trying to fix it for a friend. Is there anything else i can do?
Should i be using this method?
http://forum.xda-developers.com/show....php?t=1570022
So im assuming there is no hope since there is no response? I see many threads of bricked NT's so im assuming this sort of this is quite common and thats the reason for the lack of response to this thread.
I have worked with android for 2 years now and never bricked a device. I just find it hard to believe this nook tablet cannot be repaired. But again, i have no idea what was done to it.
"Bricked" is a very loose term: without knowing more what's wrong and/or what was done with a tablet it's hard to suggest how to really fix it. Applying a wrong fix often makes the problem worse rather than better.
But it's not necessarily a total loss: until you can figure how to fix it you might try to run CM10 off an SDcard: see http://iamafanof.wordpress.com/2012/11/18/cm10-0-jellybean-sdcard-img-for-nook-tablet/, or http://forum.xda-developers.com/showthread.php?t=2061536.
Not sure how i missed that thread but that worked great!
i was about to throw in the towel and you blessed me with that great info. Thank you so much!
I do have one question. got everything setup but when i start the tablet without usb cable plugged in it won't boot. gives me the call customer service msg. Do i have to have usb plugged in everytime i want to boot up now?
Try holding the "n" button when you power up. Press power and at that very first flicker after a few seconds, press and hold n.
bignadad said:
I do have one question. got everything setup but when i start the tablet without usb cable plugged in it won't boot. gives me the call customer service msg. Do i have to have usb plugged in everytime i want to boot up now?
Click to expand...
Click to collapse
Try what Asa suggested above, if it doesn't work then your friend's NT is like mine and many others' -- they only boot into SD with a cold boot and using a powered USB cable. Some people deem this "USB-tethered boot" behavior a manufacturing defect, but it might very well be by design by B&N to discourage people from venturing outside their content wall-garden with easy-to-use 3rd-party ROMs.
Hello everyone,
I seem to be facing a singular issue, but I imagine it is much my fault, and just wanted a confirmation from those more experienced with the device...
I bought an Incredible 4G from eBay, that already had the a copy of Avatar on it, I believe almost the latest update. So when I confirmed the device worked after charging the battery, I flashed the latest copy of Avatar and the JB Gapps, and everything seemed hunkydory.
So, after that, I put in my old SIM, deactivated as I was using a non-4g device, and put it in the Incredible 4G. I started the activation process on the phone, following prompts to reboot the phone (Note: I did not know about CM10.1's issue regarding activation at the time, so one of the possible problems.)
After seemingly failing to activate after the first reboot, I "tried again" and it went down for another reboot. And it stayed down. Completely. I cannot get the phone to start, after charging the battery separately, cannot get into bootloader, nothing. I get QHSUSB_DLOAD when plugged into a computer using USB, but that's it.
A few notes: first time I started up, the screen went to recovery. I didn't think that was an issue; I factory reset from there, and rebooted into Avatar. Second issue: I used ROM updater on the phone to download and install the recovery, as I imagined that there was an automatic checksum done in the process (perhaps it was imagined?), and so when it went to flash, it had some issue, which didn't seem like a problem with the download, and I went through flashing it normally through recovery. Sorry I can't provide more details on that, but everything seemed to work all right after rebooting.
Finally, and this may be irrelevant, I put a 64GB SDXC card in the phone, I had already realized that it could not natively support exFAT, and so left the card in the device until the next time I could boot to recovery to partition it, and went through the activation process with the card inserted and not recognized.
So, I imagine that I have a hard brick, but can't tell if it's completely my fault, because it bricked in a peculiar fashion, at least from what I can tell, as no one seems to have encountered a similar issue after searching for the last 5 days.
If there's any hope for recovery, I would really appreciate some help regarding the device. I'm willing to provide some more info if necessary, and I'd like to find out sooner rather than later if it's a lost cause.
Thanks for any help you guys can give. XDA devs are awesome.
Quite the predicament. Just to clarify, have you tried the following?
1) Remove that super-big MicroSD
2) Remove SIM
3) Remove battery and wait a few minutes; also press the power button while phone is off
4) Only re-inserting the battery, hold vol-down and then hold power until screen comes on (then release power but keep holding vol-down)
I have tried them all; no SIM or SD card has been in there since the issue started. I hadn't tried pushing the power button while the battery was out, but it doesn't seem to change anything. So far, no reaction whatsoever even when holding power + vol down for a few minutes.
ChiqOmar said:
I have tried them all; no SIM or SD card has been in there since the issue started. I hadn't tried pushing the power button while the battery was out, but it doesn't seem to change anything. So far, no reaction whatsoever even when holding power + vol down for a few minutes.
Click to expand...
Click to collapse
Looks like you have a very hard to solve brick, I would like to help, have you tried using fastboot, I mean connected to pc and on that screen issue a fastboot command, also upload a picture of it please since this is new kind of brick, also I found this, our device is supported,
http://unlimited.io/qhsusbdload.htm
Sent from my ADR6410LVW using xda app-developers app
jose51197 said:
Looks like you have a very hard to solve brick, I would like to help, have you tried using fastboot, I mean connected to pc and on that screen issue a fastboot command, also upload a picture of it please since this is new kind of brick, also I found this, our device is supported,
http://unlimited.io/qhsusbdload.htm
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
You can't do fastboot if you can't reach the bootloader, and I've been assured the unlimited.io tool will not help for DLOAD resulting from non-racun related procedures.
Reading forum posts about QHSUSB_DLOAD suggest either jtag is necessary (which might not be worth it considering the phone can be purchased for $150 on ebay) or some strange strokes of luck after letting the phone sit for a bit. ChiqOmar, sorry I don't have great advice; do all the reading you can about QHSUSB_DLOAD mode.
jose51197 said:
Looks like you have a very hard to solve brick, I would like to help, have you tried using fastboot, I mean connected to pc and on that screen issue a fastboot command, also upload a picture of it please since this is new kind of brick, also I found this, our device is supported,
http://unlimited.io/qhsusbdload.htm
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
yes sounds like he is stuck in QSHUSB_DLOAD mode, but i don't know if the resolutiion on unlimited.io will help him or not.they say it's not supported for other reasons other than from running their exploit. it might work though.
mdmower said:
You can't do fastboot if you can't reach the bootloader, and I've been assured the unlimited.io tool will not help for DLOAD resulting from non-racun related procedures.
Reading forum posts about QHSUSB_DLOAD suggest either jtag is necessary (which might not be worth it considering the phone can be purchased for $150 on ebay) or some strange strokes of luck after letting the phone sit for a bit. ChiqOmar, sorry I don't have great advice; do all the reading you can about QHSUSB_DLOAD mode.
Click to expand...
Click to collapse
Maybe port HTC unbricking project to our device, and try to help him using it, since he can't do nothing about it right now, ChiqOmar, you ok with testing it ?, btw download ubuntu connect phone and see if the partitions get mounted, btw looks like you need to flash hboot from that mode, that's all then ruu, I have all the tools to do it if you want to
Sent from my ADR6410LVW using xda app-developers app
mdmower said:
You can't do fastboot if you can't reach the bootloader, and I've been assured the unlimited.io tool will not help for DLOAD resulting from non-racun related procedures.
Reading forum posts about QHSUSB_DLOAD suggest either jtag is necessary (which might not be worth it considering the phone can be purchased for $150 on ebay) or some strange strokes of luck after letting the phone sit for a bit. ChiqOmar, sorry I don't have great advice; do all the reading you can about QHSUSB_DLOAD mode.
Click to expand...
Click to collapse
i was able to bring my rezound back after a hard brick with a hex edited hboot that went bad with this tool but ported for rezound. its worth a try?
Thanks for the help everyone. Yes, although it states quite clearly that the Unlimited.io tool is only meant for devices bricked using their tool, I tried it anyway; obviously, nothing changed.
Though JTAG sounds interesting, I have no idea how to get started with that...nor do I really know if I want to travel down that route just now.
The HTC Unbricking Project sounds promising, but also no idea how to get started as it has not been ported for our device. The partitions don't get mounted in Ubuntu, as I connected it to the computer to use the Unlimited.io tool.
Finally, regarding the nature of the brick itself, I really wish I could pinpoint the issue better to help others if a similar issue happens in the future.
I am actually waiting on a battery, (ordered before I got the phone) and so will try that to see if anything changes.
Thanks again everyone. I've got a feeling I might have to write this one off pretty soon.
ChiqOmar said:
Hello everyone,
I seem to be facing a singular issue, but I imagine it is much my fault, and just wanted a confirmation from those more experienced with the device...
I bought an Incredible 4G from eBay, that already had the a copy of Avatar on it, I believe almost the latest update. So when I confirmed the device worked after charging the battery, I flashed the latest copy of Avatar and the JB Gapps, and everything seemed hunkydory.
So, after that, I put in my old SIM, deactivated as I was using a non-4g device, and put it in the Incredible 4G. I started the activation process on the phone, following prompts to reboot the phone (Note: I did not know about CM10.1's issue regarding activation at the time, so one of the possible problems.)
After seemingly failing to activate after the first reboot, I "tried again" and it went down for another reboot. And it stayed down. Completely. I cannot get the phone to start, after charging the battery separately, cannot get into bootloader, nothing. I get QHSUSB_DLOAD when plugged into a computer using USB, but that's it.
A few notes: first time I started up, the screen went to recovery. I didn't think that was an issue; I factory reset from there, and rebooted into Avatar. Second issue: I used ROM updater on the phone to download and install the recovery, as I imagined that there was an automatic checksum done in the process (perhaps it was imagined?), and so when it went to flash, it had some issue, which didn't seem like a problem with the download, and I went through flashing it normally through recovery. Sorry I can't provide more details on that, but everything seemed to work all right after rebooting.
Finally, and this may be irrelevant, I put a 64GB SDXC card in the phone, I had already realized that it could not natively support exFAT, and so left the card in the device until the next time I could boot to recovery to partition it, and went through the activation process with the card inserted and not recognized.
So, I imagine that I have a hard brick, but can't tell if it's completely my fault, because it bricked in a peculiar fashion, at least from what I can tell, as no one seems to have encountered a similar issue after searching for the last 5 days.
If there's any hope for recovery, I would really appreciate some help regarding the device. I'm willing to provide some more info if necessary, and I'd like to find out sooner rather than later if it's a lost cause.
Thanks for any help you guys can give. XDA devs are awesome.
Click to expand...
Click to collapse
Just got same issue, though for me I installed avatar rom, then rebooted at some point, but instead it hard bricked, can't charge pull battery out/in boot back up removed sim sd card didn't help me either. Any progress yet, or help?
Ill try to get a working htc unbriking Project soon for you guys to try, both please use ubuntu and have a working USB cable, I'm gonna try to reinstall hboot, also have teamviewr installed, also please tell me if you guys are supercid, also no usb 3.0 cable or port please
Sent from my ADR6410LVW using xda app-developers app
Some Information
jose51197 said:
Ill try to get a working htc unbriking Project soon for you guys to try, both please use ubuntu and have a working USB cable, I'm gonna try to reinstall hboot, also have teamviewr installed, also please tell me if you guys are supercid, also no usb 3.0 cable or port please
Sent from my ADR6410LVW using xda app-developers app
Click to expand...
Click to collapse
I'm on Ubuntu 13.04 64 Bit, I have a usb cable, Anker Battery Expert separate battery charger. And my Phone is S-OFF DirtyRacun Currently still hard bricked (Not by the Racun though) don't have any 3.0's, i have a onn usb cable and the stock, I also have a Ubuntu 12.04.2 LTS 32 Bit Live DVD. Battery Charging using a battery pack charger. Won't charge through USB
OldNut5 said:
I'm on Ubuntu 13.04 64 Bit, I have a usb cable, Anker Battery Expert separate battery charger. And my Phone is S-OFF DirtyRacun Currently still hard bricked (Not by the Racun though) don't have any 3.0's, i have a onn usb cable and the stock, I also have a Ubuntu 12.04.2 LTS 32 Bit Live DVD.
Click to expand...
Click to collapse
pm me with gtalk email and ill see what i can do, also install teamviewr
OldNut5 said:
I'm on Ubuntu 13.04 64 Bit, I have a usb cable, Anker Battery Expert separate battery charger. And my Phone is S-OFF DirtyRacun Currently still hard bricked (Not by the Racun though) don't have any 3.0's, i have a onn usb cable and the stock, I also have a Ubuntu 12.04.2 LTS 32 Bit Live DVD. Battery Charging using a battery pack charger. Won't charge through USB
Click to expand...
Click to collapse
I lost my first Dinc 4G LTE after I installed CM10.1, was working great for a while and just blinked off, never to recover. No charge light, no response to power button. I also had an aftermarket battery (Hyperion), but it would get so hot charging I replaced it with an OEM HTC battery. I think that damaged the phone.
Since I work with analog electronics, I assume something in the power path physically burned out. I never tried to talk to it via USB, but just cabling it to a computer generates no response.
I went back to the Stock RUU.zip from the unlimited.io site to get the firmware update. During the update it just sort of died. Now I can't get it to charge or get into the bootloader. Help! Please!:crying:
Hi all,
I thought this might help ppl, it certainly helped me.
So as I reported earlier mine NT was one of those which wont boot off of the sd unless tethered. I did many things but I THINK (can't be certain) that I did what is mentioned my the guy PHIL here in the below link and it solved it (for until now, for my last 3-4 boots)
Basically, just remove the cord once you see the N sign, timing might be important I don't know.
For reference: http://www.androidfornook.com/forum/thread-98.html
P.S. : Making a separate thread so that ppl can see and get benefited. Sorry if thats against forum rules. Just trying to help
Cheers !
I'm sorry, but I don't really get how this is a solution to the problem that you need to be thethered to boot from sd. In order for you to "remove the cord" it has to be inserted in the first place = you are thethered. Or am I missing something?
Normally what you do with those troublesome ones that needs to be tethered to boot from sd is you turn it off (wich of course you do anyway!), and instead of pressing "power" you insert the powered cable. Once the boot process starts you can either leave the chord in or remove it. It doesn't matter.
Is this something different where you don't need the chord to be connected to the charger? Or is it for a number of Tablets that doesn't boot from sd even when thethered the "normal" way (with the powered chord)?
Sorry, don't mean to be difficult, but I honestly don't get it! I have only had one of the 10 or so NT:s that has passed through my hands with this problem, so I really have very little experience of it and want to learn more!
Edit: I think I maybe get it now. There is a lot of talk about sleep mode and turning off the device and this supposedly allows you to turn on and off the device and it boots into SD until you need to charge it again. Personally I never turn off my devices unless for example on an airplane. It hardly looses any battery in standby as long as wifi is off. A good ROM will not require you to turn it for battery conservation!
asawi said:
I'm sorry, but I don't really get how this is a solution to the problem that you need to be thethered to boot from sd. In order for you to "remove the cord" it has to be inserted in the first place = you are thethered. Or am I missing something?
Normally what you do with those troublesome ones that needs to be tethered to boot from sd is you turn it off (wich of course you do anyway!), and instead of pressing "power" you insert the powered cable. Once the boot process starts you can either leave the chord in or remove it. It doesn't matter.
Is this something different where you don't need the chord to be connected to the charger? Or is it for a number of Tablets that doesn't boot from sd even when thethered the "normal" way (with the powered chord)?
Sorry, don't mean to be difficult, but I honestly don't get it! I have only had one of the 10 or so NT:s that has passed through my hands with this problem, so I really have very little experience of it and want to learn more!
Edit: I think I maybe get it now. There is a lot of talk about sleep mode and turning off the device and this supposedly allows you to turn on and off the device and it boots into SD until you need to charge it again. Personally I never turn off my devices unless for example on an airplane. It hardly looses any battery in standby as long as wifi is off. A good ROM will not require you to turn it for battery conservation!
Click to expand...
Click to collapse
Hi, I see the confusion, what I meant (at least worked for me) is to that as a one time thing.. after that if I switch off switch on it can boot from sd card by pressing the n key on startup, no more need of tethering. I don't know if it'll work with everyone, don't have more such tablets to try on. Give it a shot. Worked for me, I hope this helps
firstdavis said:
Hi all,
I thought this might help ppl, it certainly helped me.
...
Basically, just remove the cord once you see the N sign, timing might be important I don't know.
For reference: http://www.androidfornook.com/forum/thread-98.html
...
Click to expand...
Click to collapse
The "remove the cord on the first boot-screen flash" was identified/posted on XDA at http://forum.xda-developers.com/showpost.php?p=25668292&postcount=13. I had used it successfully when I was running CM7-beta, but I have not been able to get it to work with any CM9 and CM10 SD ROM builds.
digixmax said:
The "remove the cord on the first boot-screen flash" was identified/posted on XDA at http://forum.xda-developers.com/showpost.php?p=25668292&postcount=13. I had used it successfully when I was running CM7-beta, but I have not been able to get it to work when with any CM9 and CM10 SD ROM builds.
Click to expand...
Click to collapse
I didn't know about that thread, still reading all of it.. but just fyi, this method worked for me for CM10.2 (android 4.3 latest ROM)
Sorry if this is in the wrong subforum, and I'm sorry to cause trouble if you have to move it. I've been a google-searching lurker for years now, but I made an account just to ask this question so again, I'm sorry if I placed it wrong.
Yes, I have a good old Pantech Pocket P9060, good ol' 2.3. I love the little thing but like always, I want to get this thing rooted. I've rooted before, but it definitely wasn't as difficult as this thing.
Every website I've been to, and my google searches are all purple links now I've been at this for hours, make it look so fracking easy (it's such an older model, after all), but for some reason mine just won't budge.
I downloaded and installed JDK, I've got the ADT bundle, I've downloaded the packs, I've got the drivers, I've got SuperOneClick, I've unmounted the SD card, I have it in USB debugging mode, I've followed all these webpages to the letter and for some reason it just won't work for me. I've done literally everything, but obviously there's gotta be something I'm not doing hidden in the void that is the steps to get this thing rooted.
I've tried having the SD mounted, I've toggled a few options, I've reset the phone while it was plugged in, I've manually updated the drivers...nothing.
There was even one page that said to dial some #*#* number but it wouldn't let me type in the whole thing, it was one * character too long. I just can't do it.
S1C keeps freezing at "starting adb server" which I see is a common problem, except they usually end up getting it resolved by doing something that, in the end, doesn't work for me. I'm past the point of pulling my hair out. What is this things problem? What am I missing?
Again, sorry if this is out of place.