Database Users

Auto Power on when AC plugged in?

When the Nexus 7 battery dies and shuts off, does it turn itself on when you plug it into the charger?
Thanks

The Nexus 7 won't power on by itself from an off state, regardless of the battery level.

No, it stays off and if you click the power button quickly it will display a charge animation. I personally like this feature as mine normally dies very late at night and I like to be able to plug it in and charge it without it booting up just to sit in sleep all night.

Damn, thank you very much!

Is there any way to MAKE the Nexus 7 start up/power up when you plug in the USB? I actually need this as I am planning on installing one in the car to replace the radio. I would like it to power up when the key is switched to accessory and the USB sees power.

I believe that you need a kernel that's modified to do this.

I don't have any answer, but this might get you thinking in the right direction even though it only has in the info for select Samsung phones.
http://forum.xda-developers.com/showthread.php?t=1815131
Post back if you figure it out. I'm also interested.

Nexus 7 Power on when plugging to charge
dmexs said:
I don't have any answer, but this might get you thinking in the right direction even though it only has in the info for select Samsung phones.
http://forum.xda-developers.com/showthread.php?t=1815131
Post back if you figure it out. I'm also interested.
Click to expand...
Click to collapse
Here is the Score: Before I plugin to charge my nexus 7, I turn it Off, once I pug it in, the pad turns itself ON by itself. If I turn it Off by pressing the side button, I have a hell of a time turning it back on, I mean from 15 minutes to one hour. I wonder if the problem is Software or Hardware. I also wonder why not to many people complain about this. You can see only great reviews but I invite you to find a solution to your problem, when you have one. It is impossible with Google !!
I was suggested to return it or replace it with another one, but I want it fixed.

I also search long time till i found the following
Code:
fastboot getvar all
(bootloader) product: herring
(bootloader) version-hardware: REV 51
(bootloader) version-baseband: I9020XXKB1
(bootloader) version-bootloader: I9020XXKA3
(bootloader) secure: yes
(bootloader) unlocked: yes
(bootloader) off-mode-charge: 1
all:
finished. total time: 0.004s
and then
Code:
fastboot oem off-mode-charge 0
Now the system boots, when USB power is plugged in

gschaden said:
I also search long time till i found the following
Code:
fastboot getvar all
(bootloader) product: herring
(bootloader) version-hardware: REV 51
(bootloader) version-baseband: I9020XXKB1
(bootloader) version-bootloader: I9020XXKA3
(bootloader) secure: yes
(bootloader) unlocked: yes
(bootloader) off-mode-charge: 1
all:
finished. total time: 0.004s
and then
Code:
fastboot oem off-mode-charge 0
Now the system boots, when USB power is plugged in
Click to expand...
Click to collapse
Good find. Do you know if it is available to a locked bootloader?

Hi . Where/how do you enter this code? I've tried on an emulator but says not reconised. My nexus 7 is un locked running tumirs rom.
Thanks
QUOTE=gschaden;39633079]I also search long time till i found the following
Code:
fastboot getvar all
(bootloader) product: herring
(bootloader) version-hardware: REV 51
(bootloader) version-baseband: I9020XXKB1
(bootloader) version-bootloader: I9020XXKA3
(bootloader) secure: yes
(bootloader) unlocked: yes
(bootloader) off-mode-charge: 1
all:
finished. total time: 0.004s
and then
Code:
fastboot oem off-mode-charge 0
Now the system boots, when USB power is plugged in[/QUOTE]

thankkkssssss!!!!!!!!!!!!!1

thanks for posting this, mine has been toggled by something and want it turning off

[Q] Oem unlock freezes, unseen error

Hello, so i got a asus nexus 7 wifi model, never seen it working. Recovery says booting failed. The one thing that works is fastboot. So i decided to reflash everything. But when i run fastboot oem unlock after about 6mins i get FAILED (remote: () as i understand no error.
I tried 3 drivers, official, naked and from asus nexus toolkit everytime same result. I tried few different pc's diferent usb ports. So maybe someone had a same problem and knows what to try next.
Bootloader version 4.13
full log:
...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) unlocking...
FAILED (remote: ()
finished. total time: 391.390s
Thx in advance

xz33r0x said:
Hello, so i got a asus nexus 7 wifi model, never seen it working.
Click to expand...
Click to collapse
I hope you didn't pay much for it. At this time there is no known workaround, as APX mode on the N7 has not been cracked with an nvflash-like tool.
You might consider donating it to the folks at androidroot.mobi, or... becoming the person that breaks into APX on the N7.

bftb0 said:
I hope you didn't pay much for it. At this time there is no known workaround, as APX mode on the N7 has not been cracked with an nvflash-like tool.
You might consider donating it to the folks at androidroot.mobi, or... becoming the person that breaks into APX on the N7.
Click to expand...
Click to collapse
I didn't pay for it at all yeah have read about apx. Just was wandering is there any other options, or the nand is dead like a brick

Nexus 7 bootloader issues (unable to update to 4.23)

So this is kind of a long story but basically I had a Nexus 7 8GB model. I bricked it by destroying the bootloader and so I sent it back for RMA.
When the thing came back it worked but was laggy as hell. I did all the normal erases and whatnot, even flashed back to stock, still laggy. I figure the EMMC was toast. So I purchased a used Nexus 7 16GB motherboard from ebay.
The new motherboard worked but came encrypted so it booted and asked for the password. Of course, not knowing the password, I had to get into recovery and do a data reset. After all that I was able to root and a Cyanogen mod based ROM.
The problem I currently have is this: I am unable to flash or update the bootloader which is stuck on 4.13. When I try and push the kitkat bootloader via fastboot I get "BAD PARAMETER" and am unable to get passed this.
In case anyone cares I was able to follow the bricksafe flatline procedure and captured the existing bootloader partition blob which is now saved to my computer. I have tried to push that bootloader back to the device and that works but I CANNOT flash the damn 4.23 (kit kat) bootloader.
Basically my Nexus 7 charges at a snails pace now but works. Any help is very much appreciated!

I don’t think the outdated bootloader is the cause of slow charging. I’m using the latest 4.23 and it charges like a snail too.

possibly you are trying to flash (Google-supplied) trash to your bootloader?
[WARNING][URGENT] N7 grouper (2012 WiFi) bootloader .img files from Google

bftb0 said:
possibly you are trying to flash (Google-supplied) trash to your bootloader?
[WARNING][URGENT] N7 grouper (2012 WiFi) bootloader .img files from Google
Click to expand...
Click to collapse
I've checked the version of the bootloader, should be ok. Also I have tried flashing 4.13, lower versions, higher versions, etc.. all fail with the 'bad parameter'.
Also I get this when I do 'fastboot getvar all'.. note the size of the bootloader, on other devices this is a 0x000.. type number. Not on mine
Code:
(bootloader) version-bootloader: 4.13
(bootloader) version-baseband: N/A
(bootloader) version-hardware: ER3
(bootloader) version-cdma: N/A
(bootloader) variant: grouper
(bootloader) serialno: 015d32205a3cDERP
(bootloader) product: grouper
(bootloader) secure: no
(bootloader) unlocked: yes
(bootloader) uart-on: no
(bootloader) partition-size:bootloader:
(bootloader) partition-type:bootloader: emmc
(bootloader) partition-size:recovery: 0x0000000000c00000
(bootloader) partition-type:recovery: emmc
(bootloader) partition-size:boot: 0x0000000000800000
(bootloader) partition-type:boot: emmc
(bootloader) partition-size:system: 0x0000000028a00000
(bootloader) partition-type:system: ext4
(bootloader) partition-size:cache: 0x000000001bb00000
(bootloader) partition-type:cache: ext4
(bootloader) partition-size:userdata: 0x0000000368f00000
(bootloader) partition-type:userdata: ext4

Well, before we get too far off into the weeds (flashing) I will first have to agree with Lim Wee Haut - it is pretty unlikely that the bootloader has any effect on charging whatsoever. Tablets that are pure stock can pull 1.8-2A from the Asus OEM charger, so it's not obvious that software is ever the problem.
For instance, when the tablet is booted into the regular OS, it is impossible for the bootloader to be active. It's not like a PC BIOS (where software interrupt calls from the OS can be vectored through the BIOS). At most, the bootloader could set some hardware registers (e.g. in the SMB USB/charger chip) prior to loading the Linux kernel, but once the kernel is active, it is free to reprogram the hardware through it's device driver(s).
And what about when the tablet is completely off? This situation is less obvious to me - after all, when you plug the N7 onto the charger, a "charging animation" is displayed, and *something* is painting the screen... but I don't really know if that activity is being run by bootloader code or something in the tegra3 "miniloader".(The Tegra3 has a small ROM area in it for storing a tiny executable that can be programmed by the system designer and then protected by use of private keys)
In any event, the problem could be the charger, the battery, the cable, or any number of other things. Note that it is possible to observe the charging current using the "Current Widget" app plus a kernel that has the bq2745 current monitor patch in it, but you need to crank down the max clock and screen brightness - what you observe via that app is literally the current flowing ONLY in to the battery, not the total current provided by the charger. That means - because you can only get the tablet down to about 300 mA of consumption with the screen on - that the most charging current you will observe that way is about 1400-1500 mA on a charger that can put out 1.8A @ 5V.
OK, back to the flashing thing: I skimmed through two of the threads related to the "bricksafe flatline" hack, and I got the impression that once you have used that hack, there is no going back to fastboot for flashing bootloaders any longer - you are stuck using nvflash/wheelie thereafter. Is that incorrect? Or was it just that using fastboot with that patched bootloader (4.13-hacked?) causes flashing problems? It would be consistent with what you are reporting.
Sorry for the apparent randomness of this reply, just throwing out some ideas.

Stuck on Boot

Hello Guys,
I am currently facing a phone that stopped working after I switched it of for the night.
All I get is the Mi logo when powering on the device. I guess it is a boot-loop???
I have no clue what might have caused it since I did not update the system.
My Problem is that I need the data stored on it like Phone numbers, Pictures and my WhatsApp conversations.
Is there any possibility that I might get them back?
Maybe over Fastboot?
I spend quite some time on this issue but I am totally lost and would really appreciate it if someone would help me out!
This is the device info from fastboot
fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:

Yeah u got bootloop , u need to download ROM from MIUi downloads and then u need to reflash ur ROM with Mi-Flash , I think u have backup contact phone number and pictures from Mi-Cloud and Google account ( hope u not turn off this backup ) .. About WhatsApp , u can login right ? When u login all message will gone but u still member of group if u consider about this ..

Thanks for the answer. Well that's exactly my problem I don't have a backup that is up to date.
Is there any way to get to my data?

Garmetola said:
Hello Guys,
I am currently facing a phone that stopped working after I switched it of for the night.
All I get is the Mi logo when powering on the device. I guess it is a boot-loop???
I have no clue what might have caused it since I did not update the system.
My Problem is that I need the data stored on it like Phone numbers, Pictures and my WhatsApp conversations.
Is there any possibility that I might get them back?
Maybe over Fastboot?
I spend quite some time on this issue but I am totally lost and would really appreciate it if someone would help me out!
This is the device info from fastboot
fastboot oem device-info
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: true
(bootloader) Display panel:
Click to expand...
Click to collapse
As per your fastboot comand detail your bootloader is locked...you can not directly flash with miflash... U need to unlock your bootloader or u can also use deep flash cable to boot into download mode then you can dirty flash with miflash tool i.e. Flash all except data and storage....
Hope this helps to you..

r_rocky07 said:
As per your fastboot comand detail your bootloader is locked...you can not directly flash with miflash... U need to unlock your bootloader or u can also use deep flash cable to boot into download mode then you can dirty flash with miflash tool i.e. Flash all except data and storage....
Hope this helps to you..
Click to expand...
Click to collapse
Yeah .. This is what I mean .. Ur devices must be download mode bcz bootloader is locked , flash with miflash and I think that is good answer for not flash data and storage for devices

Bricked A1. a way to access data?

Hello,
My A1 is bricked since few days.
I've made few trys to get access on the data and i don't find any solution.
I can comunicate with the phone via Fastboot, but did not find a way to do something....
with fastboot oem device-info, i have this result:
(bootloader) Device tampered: false
(bootloader) Device unlocked: false
(bootloader) Device critical unlocked: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.060s]
finished. total time: 0.062s
the oem unlock is not allowed.
With ADB, no success, the USB depuration was not on before the brick so....
Does someone know a way to do something?
is there is a way to load something from a SD card to turn on again the device without erasing everything?
Thank you very much.
Regards
Lebenjb

Nope there is no way. You basically hard brick the device. Did you lock the bootloader after modifying system?
The only way I know of is EDM mode, but it requires opening the phone and short curcuit some contact ponit.

Thanks for your answer.
The A1 get bricked by itself using it with the original rom.
I was so interested to have access to save some files!
I have a new phone, so I'm not in hurry, but if someone knows a way to make a recovery with data or just to have access to the files.
Then I will "wipe and delete" to give it to my son
Regards