[Q] QHSUSB_DLOAD... uh oh. - Nexus 7 (2013) Q&A

ROM: ParanoidAndroid 3.91
Happened after rebooting when attempting to access twrp recovery. Initially the "battery charging" symbol did show up, but after holding power and volume up+down it's now bricked.
So far I've tried holding power while plugged/unplugged and holding power + volume up+down for 20s while plugged into a computer, and using the adb reboot command (even though it doesn't show up in adb devices).
I'm guessing the responses I'm going to get are:
1) You shouldn't have rooted/flashed your tablet
and
2) you should RMA
So yep... realize that's the general consensus for QHSUSB_DLOAD issues but thought maybe the nexus 7 in particular might have a fix. Or I guess I'm just hoping the "it's dead RMA it" solution is outdated now.

Usually that means the bootloader can't be accessed but there was a person earlier who had the problem and was able to recover

sfhub said:
Usually that means the bootloader can't be accessed but there was a person earlier who had the problem and was able to recover
Click to expand...
Click to collapse
Oh wow. Yep I searched the forum for "qhsusb" with no results so I posted a new thread but... yep. Followed the instructions on this thread:
http://forum.xda-developers.com/showthread.php?t=2404297&highlight=brick
Held the power button for ~30-35 seconds and it's working.
... sorry I made a thread!

Qhsusb_dload
The situation is the same on the buttons and not react 30 and 60 seconds.
where to dig further? (translated with help of Google)

help
MasterFISHER said:
The situation is the same on the buttons and not react 30 and 60 seconds.
where to dig further? (translated with help of Google)
Click to expand...
Click to collapse
looking for solution, have the same problem, nexus 7 2013, restarted and than blank screen, When I plug device into PC I get QHSUSB_DLOAD not installed (stock kernel, unroot, everything as from a factory). Holding power on, volume buttons are not helping.
what to do?

arkeyn said:
looking for solution, have the same problem, nexus 7 2013, restarted and than blank screen, When I plug device into PC I get QHSUSB_DLOAD not installed (stock kernel, unroot, everything as from a factory). Holding power on, volume buttons are not helping.
what to do?
Click to expand...
Click to collapse
This is a corrupted bootloader. Some have tried holding the power button down for 20-30 seconds. You will most likely need a new motherboard if you cannot access fastboot.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app

LinearEquation said:
This is a corrupted bootloader. Some have tried holding the power button down for 20-30 seconds. You will most likely need a new motherboard if you cannot access fastboot.
Sent from my Nexus 7 Flo running CM 11 4.4.2 with ElementalX Kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
in local service shop I was told they can't fix this problem. Any suggestions what else can I do?

arkeyn said:
in local service shop I was told they can't fix this problem. Any suggestions what else can I do?
Click to expand...
Click to collapse
I love you got having qhsub_dload in your title.
Had this issue after trying to root Android 6 today and was rather worried I'd bricked it.
So many threads full of people who can actually get into bootloader, but this thread helped me solve it so thanks and bump ahoy.

Related

[Q] Unbelievable Galaxy Nexus problem.

This is my first post on the XDA forum. I registered only 2 try 2 have a reply 2 a problem that in my language (italian) is impossible to find out.
This is the best place for everything concerning android world so I hope to be lucky.
This morning my galaxy nexus, while I was playing @ paradise island, freezed and started to play several times a sound that was like an emergency (almost like the overheat processor beep in the computer cases - never heard that before). After this emergency beep the phone shutted off.
When I turned it on the Google logo appears but it start having gliches and reboot. This infinite times until the battery is removed. Sometimes it arrives to the colorful background but that times also it freeze (without gliches) and reboot.
Tryin 2 find out the problem I had a soft reset (battery off for 10 mins) but nothing.
I tried also an hard reset. The phone anyway after having selected RECOVERY MODE from the apposite menu start the google logo and when reaches the "red alert signal droid" the droid is gliched and the phone freeze and reboot. And start another time infinite reboots.
Someone know what kind of problem the phone have? It enters without problems in odin mode and the (I kind is called) bootload mode but don't start the recovery mode. I'm totally n00b, the phone is in fact stock, and I don't want 2 wait 1 month of assistance time if is a problem that can be resolved also @ home.
Please help me if you can and thanks for gifting me with your time.
- NeX - said:
.... The phone anyway after having selected RECOVERY MODE from the apposite menu start the google logo and when reaches the "red alert signal droid" the droid is gliched and the phone freeze and reboot. And start another time infinite reboots.
....
Click to expand...
Click to collapse
Sorry to ask but I don't understand gliched, can you get in Stock Recovery (the "red alert signal droid" as you call it), push volume up and power at the same time and enter the recovery menu? Or not?
Diger36 said:
Sorry to ask but I don't understand gliched, can you get in Stock Recovery (the "red alert signal droid" as you call it), push volume up and power at the same time and enter the recovery menu? Or not?
Click to expand...
Click to collapse
no I can't. The droid is gliched so the volume up + power combo doesn't work. The phone reboot some times. Some others times (like the trying I had now) the phone freezes.
Try flash the google stock images through fastboot, there are threads with instructions and links to everything you will need.
You should be able to fix whatever is wrong.
nodstuff said:
Try flash the google stock images through fastboot, there are threads with instructions and links to everything you will need.
You should be able to fix whatever is wrong.
Click to expand...
Click to collapse
If doing it I can loose warranty?
No, you can re-lock your bootloader when you are done.
matt2053 said:
No, you can re-lock your bootloader when you are done.
Click to expand...
Click to collapse
And the problem for sure is going 2 be solved? Seems super!
It MAY solve your problems, if they are software related.
If its a hardware problem it won't.
Give it a try anyway.
nodstuff said:
It MAY solve your problems, if they are software related.
If its a hardware problem it won't.
Give it a try anyway.
Click to expand...
Click to collapse
ok i'll search and try it.
to me, sounds like hardware problem.
this is the toolkit you should try - http://forum.xda-developers.com/showthread.php?t=1392310
joshtb86 said:
to me, sounds like hardware problem.
this is the toolkit you should try - http://forum.xda-developers.com/showthread.php?t=1392310
Click to expand...
Click to collapse
He is better off using fastboot and learning something.
Tool kits are the wrong way to do things, it is better to know what is actually happening when you pick an option in a toolkit.
nodstuff said:
He is better off using fastboot and learning something.
Tool kits are the wrong way to do things, it is better to know what is actually happening when you pick an option in a toolkit.
Click to expand...
Click to collapse
the problem is that I don't know anything of this stuff. I don't know how to start.
The toolkit guide is huge and I think i should do only 2 or 3 of the all listed operation...
For now i took only the kit, the pdanet for win 64 and the yakju 4.0.4 from the google page. I don't know how 2 put them on and in which order.
.....
Oh, phone of my colleague has the same issue. We don't know what to do cause we can't connect Nexus to computer. When trying to do this Fastboot 2147483647 error occurs. Adb devices gives empty list.
Sounds like a hardware problem to me
- NeX - said:
the problem is that I don't know anything of this stuff. I don't know how to start.
The toolkit guide is huge and I think i should do only 2 or 3 of the all listed operation...
For now i took only the kit, the pdanet for win 64 and the yakju 4.0.4 from the google page. I don't know how 2 put them on and in which order.
Click to expand...
Click to collapse
Learn.
It looks like rocket science to me at first(Gnex is my first smartphone), do it slowly.
- NeX - said:
no I can't. The droid is gliched so the volume up + power combo doesn't work. The phone reboot some times. Some others times (like the trying I had now) the phone freezes.
Click to expand...
Click to collapse
Not sure if this is different on other phones but for me to get to recovery its not Volume up + Power. Its Volume up + volume down + power (i.e. hold both volume buttons then hold power button until it vibrates or the google logo shows up)
WoodroweBones said:
Not sure if this is different on other phones but for me to get to recovery its not Volume up + Power. Its Volume up + volume down + power (i.e. hold both volume buttons then hold power button until it vibrates or the google logo shows up)
Click to expand...
Click to collapse
This gets you to bootloader, not recovery
Sent from my i9250

[Q] Non-working, rooted and still under warrenty. Nothing I can do?

I've got a dilemma. My rooted Verizon GNex just stopped working today. Yesterday, it was working fine. I plugged it up at night before bed and about an hour ago, I grab it off the charge. Nothing happened when I hit the power button which was strange because I never turn it off and I didn't let the battery die. I pressed and held and "Google" and the little lock on the bottom came up so I set the phone down while it powered on. 5 minutes later, it's still in that state, then a few seconds later, the screen goes black and nothing happened. I took the battery out and put it back in twice and nothing happens. I can't remember downloading any apps other than Zagat and a guide for Ingress in the last few days. A PDF online or two. What do I do with a rooted phone that's still under warranty (just barely so time is a factor)? Can they really check if the phone won't even turn on?
My old roommate sent her unlocked/rooted Gnex back to VZW when her charging port stopped working. They never charged her for it or anything, but it did say something like "you would be responsible to pay $X if rooted blah blah.." Either they are bluffing or she slipped in.
Did you try clearing data, factory reset?
How can I do a factor reset if it won't turn on? All I know is pulling the battery or holding the power and volume buttons at once.
Sent from my Nexus 7 using xda app-developers app
WiredPirate said:
My old roommate sent her unlocked/rooted Gnex back to VZW when her charging port stopped working. They never charged her for it or anything, but it did say something like "you would be responsible to pay $X if rooted blah blah.." Either they are bluffing or she slipped in.
Did you try clearing data, factory reset?
Click to expand...
Click to collapse
I don't think a factory reset wipes root.
If you hold volume (-) and power from a powered off state can you boot to fastboot mode and is it still recognized by your PC?
Sent from my Galaxy Nexus using xda app-developers app
RoyJ said:
I don't think a factory reset wipes root.
If you hold volume (-) and power can you boot to fastboot mode and is it still recognized by your PC?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Unless it's different on the VZW than a GSM phone you need to hold volume up & volume down + power to get to the bootloader (fastboot mode)
LaWolfe said:
How can I do a factor reset if it won't turn on? All I know is pulling the battery or holding the power and volume buttons at once.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
With the phone off hold both volume buttons and the power button, then use the down volume key to navigate to recovery, and power to select the option. Once in recovery you will see wipe data/ factory reset option.
Also if you have a backup you can restore it from recovery.
RoyJ said:
I don't think a factory reset wipes root.
If you hold volume (-) and power can you boot to fastboot mode and is it still recognized by your PC?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
No a factory reset wont wipe root, but if it solves his problem and the phone is functional again he wont need to exchange it through warranty, so no need to unroot.
Holy crud that worked! It's on and it shows the green start arrow pointing toward the power button which does nothing when I press it (I hear some Samsungs have issues with the power button not working). Under the Android bot it says, "Downloading... Do not turn off target!" but my PC (W7) couldn't download whatever driver it needed. And I just realized I do have the Wugs toolkit. Can I unroot if I'm unable to get critical buttons on my phone top act properly?
Try the factory reset first. If that works you get to keep the phone like WiredPirate said. Check out this guide to install drivers and flash stock Google images if you have to.
http://forum.xda-developers.com/showthread.php?p=25477039
Edit: sorry I have been up for a while. Power off the phone. Pull battery if you need to. Power + BOTH volume buttons at the same time. Use the volume keys to navigate to recovery mode and power to select it. If the phone will boot to recovery try a factory reset and reboot. If that works, awesome. If not follow the guide above to flash the phone to stock.
Sent from my Galaxy Nexus using xda app-developers app
Instead of plugging it up to your computer before/after it boots, can you press the volume down key twice for it to display "recovery" on that green arrow?.. Then hit the power button to boot into recovery. No USB, no toolkit or computer. Then do a factory reset and/or restore a backup and see if the phone boots normal.
It wasn't working working without being plugged up to the computer and now the phone is on the lock screen. What I'm going to do is unroot, backup, and decide whether or not to take it to Verizon. I want to but if I can't actually show them anything, I wonder what they'll do. Looks like everything seemss normal for now. Thanks for the help!
Oh okay, well good deal.. Glad everything is back to a more stable state now. :good:
Hey!
I have got the same Problem (though GSM version)! I cant boot up my system. When I turn the device on the Google screen appears along with the unlocked lock.
I have already tried to full whipe it and restore it but it did not work. Bevore that the restore did not work either!
Can someone help me?
Andraxx said:
Hey!
I have got the same Problem (though GSM version)! I cant boot up my system. When I turn the device on the Google screen appears along with the unlocked lock.
I have already tried to full whipe it and restore it but it did not work. Bevore that the restore did not work either!
Can someone help me?
Click to expand...
Click to collapse
This...
RoyJ said:
Try the factory reset first. If that works you get to keep the phone like WiredPirate said. Check out this guide to install drivers and flash stock Google images if you have to.
http://forum.xda-developers.com/showthread.php?p=25477039
Edit: sorry I have been up for a while. Power off the phone. Pull battery if you need to. Power + BOTH volume buttons at the same time. Use the volume keys to navigate to recovery mode and power to select it. If the phone will boot to recovery try a factory reset and reboot. If that works, awesome. If not follow the guide above to flash the phone to stock.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Sent from my Galaxy Nexus using xda app-developers app
RoyJ said:
This...
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
Problem is that my PC does not recognize my device even though I have installed the drivers and in device menager it says: Samsung Android ADB Interface
Andraxx said:
Problem is that my PC does not recognize my device even though I have installed the drivers and in device menager it says: Samsung Android ADB Interface
Click to expand...
Click to collapse
Delete the drivers you see for the phone inside of device manager. Now go back to that topic, scroll all the way up to the very beginning and follow the steps. It tells you exactly how to correctly install the drivers to get your phone recognized.
Sent from my Galaxy Nexus using xda app-developers app
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

[Q] Hard brick

Woke up this morning and my N7 wouldn't turn on. Plugged it in and the charging indicator came up showing at nearly full charge. Holding the power button then turned it on. Went away for an hour or two, came back and it was off. When I turned it back on it was stuck on the X screen. Forcing a reboot with power+vol just led to the tablet turning off. And now I just plugged it into my computer and QHSUSB_DLOAD came up.
Just got the damn thing a couple days ago and it was 100% stock. Any ideas as to what may have caused this?
Just unplugged it and it turned on but is again stuck on the X. Is QHSUSB_DLOAD no longer indicative of a hard brick?
I'm a newbie here, but let's try.
If you can get to the X one, then I think it's not brick yet.
Maybe your should try to press pwer button and volume down to get to fastboot. You press this combination when your Nexus is turned off.
opticaldh said:
I'm a newbie here, but let's try.
If you can get to the X one, then I think it's not brick yet.
Maybe your should try to press pwer button and volume down to get to fastboot. You press this combination when your Nexus is turned off.
Click to expand...
Click to collapse
once I turn it off the whole cycle starts over again. It's sporadically deciding whether or not it wants to boot but I'll keep trying to get into fastboot
herculesgs said:
Woke up this morning and my N7 wouldn't turn on. Plugged it in and the charging indicator came up showing at nearly full charge. Holding the power button then turned it on. Went away for an hour or two, came back and it was off. When I turned it back on it was stuck on the X screen. Forcing a reboot with power+vol just led to the tablet turning off. And now I just plugged it into my computer and QHSUSB_DLOAD came up.
Just got the damn thing a couple days ago and it was 100% stock. Any ideas as to what may have caused this?
Click to expand...
Click to collapse
In doing a little googling it looks to be possibly caused by the update. If you look up the error, you will see a common problem where HTC bricked a bunch of different phones when they pushed an ota a while back. I would say just return it and get a new one . You could do some research and try it yourself. Are you able to get into your bootloader ( vol+ and Vol - when you trun it on)?
uprightbass360 said:
In doing a little googling it looks to be possibly caused by the update. If you look up the error, you will see a common problem where HTC bricked a bunch of different phones when they pushed an ota a while back. I would say just return it and get a new one . You could do some research and try it yourself. Are you able to get into your bootloader ( vol+ and Vol - when you trun it on)?
Click to expand...
Click to collapse
I was able to get into it this morning and I wiped my cache. The next time it decides to turn on/I can get it into the bootloader I'll try a factory reset
herculesgs said:
I was able to get into it this morning and I wiped my cache. The next time it decides to turn on/I can get it into the bootloader I'll try a factory reset
Click to expand...
Click to collapse
Well something got corrupted, but if its booting its not hard bricked (that's good news). Luckily for you as well the aosp images are up so if you want to do a restore you can snag your images, and just do a fastboot install. I hope this isn't indicative of another problem with the device itself, I still maintain that you should probably exchange your device for a new one if you did indeed do nothing to the device. It would be a shame if the same problem happened again because of a faulty component.
uprightbass360 said:
Well something got corrupted, but if its booting its not hard bricked (that's good news). Luckily for you as well the aosp images are up so if you want to do a restore you can snag your images, and just do a fastboot install. I hope this isn't indicative of another problem with the device itself, I still maintain that you should probably exchange your device for a new one if you did indeed do nothing to the device. It would be a shame if the same problem happened again because of a faulty component.
Click to expand...
Click to collapse
Yeah, I most likely will. It'll boot to the X probably once every 25 tries so there's something weird going on and it's probably safer just to return it then find a fix and have it happen again.
herculesgs said:
Yeah, I most likely will. It'll boot to the X probably once every 25 tries so there's something weird going on and it's probably safer just to return it then find a fix and have it happen again.
Click to expand...
Click to collapse
Just out of curiosity, where did you purchase it from? Does the seller recognize a lemon as returnable, would you possibly have to tell them you just didn't like it?
uprightbass360 said:
Just out of curiosity, where did you purchase it from? Does the seller recognize a lemon as returnable, would you possibly have to tell them you just didn't like it?
Click to expand...
Click to collapse
Wally world. afaik they're pretty lax on returns
update
Got into the bootloader and did a factory reset. Everything seems to be working again now
herculesgs said:
Got into the bootloader and did a factory reset. Everything seems to be working again now
Click to expand...
Click to collapse
Awesome! Love a happy ending.
Mine was like that all day. I am unlocked and rooted but stock ROM. Damn thing was on an x all day. I was finally able to get to TWRP and flashed my latest backup. No ideas what happened or why.
Sent from my Nexus 7 using xda app-developers app
AnarchoXen said:
Mine was like that all day. I am unlocked and rooted but stock ROM. Damn thing was on an x all day. I was finally able to get to TWRP and flashed my latest backup. No ideas what happened or why.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Mine is just stuck on Google...... I got into fastboot and flashes stock image but it still will not get past google. I can not boot it to recovery or anything other than fastboot.
What happens when you do vol down and power to try and get into the bootloader? Nothing at all?
Sent from my Nexus 7 using xda app-developers app
kd5dmg said:
Mine is just stuck on Google...... I got into fastboot and flashes stock image but it still will not get past google. I can not boot it to recovery or anything other than fastboot.
Click to expand...
Click to collapse
Follow hercules advice. Vol Down + Power to get to bootloader. Then you should be able to get to recovery. Let us know.
Sent from my Nexus 7 using Tapatalk 4
kd5dmg said:
Mine is just stuck on Google...... I got into fastboot and flashes stock image but it still will not get past google. I can not boot it to recovery or anything other than fastboot.
Click to expand...
Click to collapse
Stuck at Google means /system is corrupted or erased (fastboot to restore system.img)
Stuck at X means something wrong with userdata/cache (factory restore from recovery)
Won't start at all with USB identifying as QHSUSB_DLOAD means either bootloader corrupted or raw partitions corrupted
I suggest you reflash again.

Please help - I fear my Nexus is bricked

Hi,
I'm sorry to trouble you all, but I fear that my lovely new tablet is bricked
I unlocked/rooted 6 days ago using Wug's tool and everything has been fine. Turned the tablet on today and all i get is the white google logo and the unlocked symbol at the bottom.
I can't get to bootloader or recovery by the power/volume buttons. If i hold down power and vol down for long enough I get a picture of a dead android with a red warning triangle over his chest
There is a windows sound when the device is plugged in via USB, but nothing appears in device manager.
As such, I am at a bit of a loss as to what to do, can anyone help please?
Close to impossible to brick a nexus device.
Recommend downloading the factory image, unzip and run the flash all batch file.
Sent from my Nexus 7 using xda app-developers app
spud_work said:
Hi,
I'm sorry to trouble you all, but I fear that my lovely new tablet is bricked
I unlocked/rooted 6 days ago using Wug's tool and everything has been fine. Turned the tablet on today and all i get is the white google logo and the unlocked symbol at the bottom.
I can't get to bootloader or recovery by the power/volume buttons. If i hold down power and vol down for long enough I get a picture of a dead android with a red warning triangle over his chest
There is a windows sound when the device is plugged in via USB, but nothing appears in device manager.
As such, I am at a bit of a loss as to what to do, can anyone help please?
Click to expand...
Click to collapse
Shut down nexus 7. Now hold volume down and power. When you see the next screen you will press up until the you see recovery mode. Now press power and you will see the Android guy and the red exclamation point. Hold the power and the volume up. You should now be in recovery mode. Use fastboot commands to restore.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
LinearEquation said:
Shut down nexus 7. Now hold volume down and power. When you see the next screen you will press up until the you see recovery mode. Now press power and you will see the Android guy and the red exclamation point. Hold the power and the volume up. You should now be in recovery mode. Use fastboot commands to restore.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thank you so much, that has got me back sorted again.
Great instructions and easy to follow/understand - Thank you!
spud_work said:
Thank you so much, that has got me back sorted again.
Great instructions and easy to follow/understand - Thank you!
Click to expand...
Click to collapse
You're welcome. Glad you it working.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
My Nexus 7 gets in this issue often
LinearEquation said:
Shut down nexus 7. Now hold volume down and power. When you see the next screen you will press up until the you see recovery mode. Now press power and you will see the Android guy and the red exclamation point. Hold the power and the volume up. You should now be in recovery mode. Use fastboot commands to restore.
Sent from my Nexus 7 Flo running Odex SinLess ROM 4.4.2 with ElementalX kernel using XDA Premium 4 mobile app
Click to expand...
Click to collapse
My nexus 7 had this issue and my friend told me your eMMC chip is wasted. I gave my little nephew my tablet to play with and i started using it like a mousepad. Just one day i tried pressing these keys at random and my device booted up.
I flashed it so many times unknowgingly this was issue.
Can i ask, why this even happens ?
*deleted*

I can't turn on my nexus 7 (2013)

Hi..
I can't turn on my Nexus 7 (2013) with power button when its turned off. but it can be turned on while charging.
so if i turned off my device & need to turned back on so i have to plug in to my charger or PC, then it can be turned on with no problem.
power button work when it's in sleep mode. this only happened if i turned off my nexus 7
pls help me to fix this problem.
Thanks
djtwinz said:
Hi..
I can't turn on my Nexus 7 (2013) with power button when its turned off. but it can be turned on while charging.
so if i turned off my device & need to turned back on so i have to plug in to my charger or PC, then it can be turned on with no problem.
power button work when it's in sleep mode. this only happened if i turned off my nexus 7
pls help me to fix this problem.
Thanks
Click to expand...
Click to collapse
Hi
Same problem.
No answer yet :http://forum.xda-developers.com/showthread.php?t=2786298
Let's keep in touch.
djtwinz said:
Hi..
I can't turn on my Nexus 7 (2013) with power button when its turned off. but it can be turned on while charging.
so if i turned off my device & need to turned back on so i have to plug in to my charger or PC, then it can be turned on with no problem.
power button work when it's in sleep mode. this only happened if i turned off my nexus 7
pls help me to fix this problem.
Thanks
Click to expand...
Click to collapse
flaviocc said:
Hi
Same problem.
No answer yet :http://forum.xda-developers.com/showthread.php?t=2786298
Let's keep in touch.
Click to expand...
Click to collapse
deb or flo? Stock?
Aerowinder said:
deb or flo? Stock?
Click to expand...
Click to collapse
Mine is:
WiFi model
Rom stock
Kernel stock
Rooted
Unlocked
Running last Google rom.
Problem: power off totally. To power on have to plug at any charger (wall or usb)
Stdby : normally wake up through power button.
Luckily my problem was solved
I just root my N7 using "Nexus Root Toolkit " then it working fine..
I think it happened after i unlocked bootloader
here is the guide I follow
Code:
http://www.wugfresh.com/nrt/
Thanks
djtwinz said:
Luckily my problem was solved
I just root my N7 using "Nexus Root Toolkit " then it working fine..
I think it happened after i unlocked bootloader
here is the guide I follow
Code:
http://www.wugfresh.com/nrt/
Thanks
Click to expand...
Click to collapse
Nothing works for me here...
I usually use wugfresh toolkit....
Sad..
UP, just to confirm....
Nobody here has this issue ???
Thank you.
flaviocc said:
UP, just to confirm....
Nobody here has this issue ???
Thank you.
Click to expand...
Click to collapse
I have it as well, after I shut it down I have to wait several minutes, then I can plug it to the AC and it will respond. Happened after unlocking. Will try to lock it back and let's hope it fix.
EDIT: additional info: if I try access fastboot, it won't work. Let's hope I can fix it.
EDIT2: additional info/2: after flashing stock, I could turn the tablet on normally. It fails when trying to enter fastboot with hardware keys.
EDIT3: I noticed that this actually happens only when I try to enter bootloader with power+vol up + vol down. with only power + vol down I have no problems.
EDIT4: solved by multiple stock ROM flashing and lockink the bootloader. Now I redid the unlock and flashed a cROM, we will see...
lightingcloud said:
I have it as well, after I shut it down I have to wait several minutes, then I can plug it to the AC and it will respond. Happened after unlocking. Will try to lock it back and let's hope it fix.
EDIT: additional info: if I try access fastboot, it won't work. Let's hope I can fix it.
EDIT2: additional info/2: after flashing stock, I could turn the tablet on normally. It fails when trying to enter fastboot with hardware keys.
EDIT3: I noticed that this actually happens only when I try to enter bootloader with power+vol up + vol down. with only power + vol down I have no problems.
EDIT4: solved by multiple stock ROM flashing and lockink the bootloader. Now I redid the unlock and flashed a cROM, we will see...
Click to expand...
Click to collapse
:good:
Thank you for your help.
After the 4.3 upgrade. I reseted N7, but with unlocked bootloader and rooted. I'll try reset again, lock the bootloader and unroot to see.
For me just the power button when N7 is unplugged doesnt work.

Categories

Resources