Related
Well to make it simple, the newest twrp is very buggy and to make a long story short i installed a new rom, and while it was restoring my data, my n7 shut off. its done this before so naturaly i held the power+volume down buttons too boot into the bootloader but it wont turn on. Any help/ suggestions?
Put it on the power supply and let it there for some time ... Then start again.
Sent from my Nexus 7 using xda app-developers app
AndDiSa said:
Put it on the power supply and let it there for some time ... Then start again.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thank you ill try that. it was at 33% battery when this happened though
Um... It probably didn't shutoff. There's a screen timeout.
Sent from my Nexus 7 using Tapatalk HD
korockinout13 said:
Um... It probably didn't shutoff. There's a screen timeout.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
i know about the screen time out, i tapped the screen for it to rewake and it didnt work, then i tried pressing the sleep button once for it to unlock and that didnt work. so it indeed shutoff
frap129 said:
Well to make it simple, the newest twrp is very buggy and to make a long story short i installed a new rom, and while it was restoring my data, my n7 shut off. its done this before so naturaly i held the power+volume down buttons too boot into the bootloader but it wont turn on. Any help/ suggestions?
Click to expand...
Click to collapse
I'm confused. It's a little off-topic, but what does "restoring my data" have to do with TWRP in the context of flashing a new ROM?
Anyway, I would proceed with a dead battery or loose battery connector hypothesis first. It's not obvious why writes to /boot, /cache, /data, or /system would affect the bootloader.
Anything is possible at a low enough probability I suppose, but you should start troubleshooting operations with the high-probability scenarios first.
For instance - with the power off, will the "charging screen" display when you plug the tab in? How about APX** mode? (Plug in to PC and start with Power+Vol-up). If you didn't see either of those, it's likely a power supply or hardware problem.
good luck
** make sure you exit APX mode by holding down the power button for at least 20 seconds. I'm not sure if it shuts itself down after an inactivity timeout - you don't want to be draining power while trying to charge the tab.
bftb0 said:
I'm confused. It's a little off-topic, but what does "restoring my data" have to do with TWRP in the context of flashing a new ROM?
Click to expand...
Click to collapse
Well, you backup your data, Wipe data and cache, flash the rom, gapps, ect. then restore data, the charging screen wont dispaly, apx mode doesnt work, but the whole story: went to flash a newer version of my rom, install faills due to error in updater binary so i go to reboot and it says "No OS Installed! Are you sure you want to reboot?" i press dont reboot, go to install the older version of the rom, go to restore data and then it shut off.
frap129 said:
Well, you backup your data, Wipe data and cache, flash the rom, gapps, ect. then restore data, the charging screen wont dispaly, apx mode doesnt work, but the whole story: went to flash a newer version of my rom, install faills due to error in updater binary so i go to reboot and it says "No OS Installed! Are you sure you want to reboot?" i press dont reboot, go to install the older version of the rom, go to restore data and then it shut off.
Click to expand...
Click to collapse
The lack of APX mode or the charger screen suggests a battery problem or a hardware failure, not a software problem. APX mode will be present even if the tablet has absolutely nothing in flash memory.
Having nothing in /system (no OS or even no filesystem) will not affect bootability of either the bootloader or the recovery.
I don't know why you would wipe data only to restore it after flashing a ROM. Usually wiping cache & dalvik-cache is sufficient for "dirty-flashing" a ROM upgrade as it is very unusual for ROM installs to diddle with the /data partition. (But making full backups is always a good idea.)
I would check (carefully) to see if the battery connector came loose before you decide to throw the tablet away.
good luck
bftb0 said:
The lack of APX mode or the charger screen suggests a battery problem or a hardware failure, not a software problem. APX mode will be present even if the tablet has absolutely nothing in flash memory.
Having nothing in /system (no OS or even no filesystem) will not affect bootability of either the bootloader or the recovery.
I don't know why you would wipe data only to restore it after flashing a ROM. Usually wiping cache & dalvik-cache is sufficient for "dirty-flashing" a ROM upgrade as it is very unusual for ROM installs to diddle with the /data partition. (But making full backups is always a good idea.)
I would check (carefully) to see if the battery connector came loose before you decide to throw the tablet away.
good luck
Click to expand...
Click to collapse
Battery connector didnt come loose, still dosent work. guess it might just be broken
EDIT: I plugged it in to my pc and the google screen came up for about 20 sec then it shut back off. havent been able to get anything since
frap129 said:
Battery connector didnt come loose, still dosent work. guess it might just be broken
EDIT: I plugged it in to my pc and the google screen came up for about 20 sec then it shut back off. havent been able to get anything since
Click to expand...
Click to collapse
Is it possible to enter Odin on the n7?
Sent from my Galaxy Nexus using xda premium
Soldier 2.0 said:
Is it possible to enter Odin on the n7?
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
Odin is Samsung only
Sent from my Galaxy Nexus
You can hold the power button for 10 seconds and wait till you see the Google logo. Then release and hold it 10 seconds again, when the screen turns off hold the volume down button and wait for it till it automatically boots again. You'll enter bootloader mode. Download wugfresh' nexus root toolkit and install it. When the program is loaded there is a flash stock option on the right side of the program. Select the soft brick / boot loop option under the flash button. While in boot loader mode connect your nexus and press the flash button.
This is all I know!
Sent from my Nexus 7 using xda premium
NEXUS 7 Bricked - NO OS - tried everything but...
It's a catch 22 here. I can't get drivers installed and the nexus recognized and so when it comes to flashing/restoring via cmd prompt the PC won't recognize my device and so I can go only get so far. I have no OS installed as I wiped all like an idiot in twrp so how the hell can I get drivers installed on a nexus that has no OS installed? I can't enable usb debugging etc because, well, I have no way of getting the nexus to work so can't get into the settings to do so.
I have tried everything in twrp but there is nothing to restore - i can't get roms pushed onto it - God I give up. All I need is the PC to recognize my device and I know I can crack this. What do I have to do? Please help this idiot.
CarlKirshner1989 said:
It's a catch 22 here. I can't get drivers installed and the nexus recognized and so when it comes to flashing/restoring via cmd prompt the PC won't recognize my device and so I can go only get so far. I have no OS installed as I wiped all like an idiot in twrp so how the hell can I get drivers installed on a nexus that has no OS installed? I can't enable usb debugging etc because, well, I have no way of getting the nexus to work so can't get into the settings to do so.
I have tried everything in twrp but there is nothing to restore - i can't get roms pushed onto it - God I give up. All I need is the PC to recognize my device and I know I can crack this. What do I have to do? Please help this idiot.
Click to expand...
Click to collapse
USB debugging doesn't mean **** when you are in a custom recovery. It has adb already. Your problem is your computer. Fix your computer by following one of the bajillion threads and posts about the nexus 7 drivers issues.
Installing drivers does not need android to be booted.
Your best bet is to put it in fast boot mode and follow Google's own instructions to flash it back to stock.
Sent from my Galaxy Nexus
CarlKirshner1989 said:
It's a catch 22 here. I can't get drivers installed and the nexus recognized and so when it comes to flashing/restoring via cmd prompt the PC won't recognize my device and so I can go only get so far. I have no OS installed as I wiped all like an idiot in twrp so how the hell can I get drivers installed on a nexus that has no OS installed? I can't enable usb debugging etc because, well, I have no way of getting the nexus to work so can't get into the settings to do so.
I have tried everything in twrp but there is nothing to restore - i can't get roms pushed onto it - God I give up. All I need is the PC to recognize my device and I know I can crack this. What do I have to do? Please help this idiot.
Click to expand...
Click to collapse
I must admit I'm a little 'hazy' myself when it comes to ADB related issues... I've never had much cause to use ADB. (Think I've used 'adb pull' on a couple of occasions). And I've never been in the invidious position of not having a bootable Android OS on my Nexus 7 either - which does seems to happen a quite lot with TWRP users, less so with CWM users.
Anyway... just had a tinker... and you could try the following workaround... this seemed to work to for me.
----------------------
Locate the folder on your PC where you keep your FASTBOOT and ADB .exe files...
Copy whatever ROM .zip you want into this folder.
The following example uses SmoothROM-v5.0.zip ... There is nothing to stop you from renaming this to something shorter, for ease of typing later... so, in my case, just smooth.zip.
Boot your Nexus 7 into the BOOTLOADER (Vol down [hold] + Power button), and then into RECOVERY (TWRP) and hook it up your PC.
Open a command prompt window on the aforementioned folder... and type...
Code:
adb devices
...which should yield something like the following...
Code:
List of devices attached
012345679ABCDEF recovery
(If you don't see a serial number... then you definitely have a driver problem...)
Otherwise, it's just...
Code:
adb push smooth.zip /sdcard
Or whatever ROM you wish to 'push' to the emulated SD card.
This will likely take a fair few minutes for a 300Mb+ size file (typically the size of your average ROM)... on my Windows XP box it took 4 minutes (1328 KB/s, 32565894 bytes in 239.486s) to copy over. And there are no 'progress gauges' of any kind, either... So season your patience a liitle. You can always pull up another command prompt window and type adb devices again to ensure you still have an ongoing ADB connection.
Once copied over, and still in TWRP, you can just flash it.
Good luck.
Rgrds,
Ged.
Still nothing on mine. im just about to give up and wait to see if google releases the N7 second generation at the i/o
If You familiar with Linux, You can try to understand the logic of
changing the modes.
You need to run udevadm monitor in one terminal. Then press some
combinations of key/s and look for changes with usb-devices.
The better, if You run wireshark and sniff USB interface with your device.
Put attachment here, with a comments what was pressed.
since it seems to be a hardware problem, not software, im just going to send it to asus and see what they can do.
I got a serious problem with the N4 of a friend.
First thing to know: his display was broken and he got it repaired. Afterwards, his phone was running fine. Then, he got the Android 4.3 OTA. He accepted the update, but since then in keeps bootlooping (I won't go past the Nexus-X). As far as I know, everything was stock!
Here are the things I tried:
- first I checked the recovery. Indeed it was the stock one, so nothing to do here.
- I wanted to wipe or flash the stock rom using fastboot but i wasn't able to get a connection. First I thought of driver issues, but my N4 works fine (adb & fastboot) on the same computer.
- Establishing a connection failed on two other computers too (my N4 worked)
- Even the device manager in Windows 7 dosen't even recognize anything when plugging in the usb cable (normally you see the ADB whatever device listed in the device manager)
- Right now I tried to get a connection using Ubuntu. Again, no usb device was recognized when plugging in the cable.
So right now, I'm a bit lost. It seems, that the usb port is broken since I can not establish a connection. And without that, I won't be able to wipe or flash anything using fastboot.
Does anyone have an idea what could have gone wrong? I'm still able to boot into the bootloader and see the information:
Bootloader version: MakoZ20i
Radio: .84
HW Version 11
16GB version
According to these information, it seems that the 4.3 Update finished at least the bootloader and radio. But it won't boot into the rom. Could the download mode be of any help?
I appreciate any help.
Thanks.
Since you are in the bootloader scroll up to recovery and select it.
Now you will see a android opened up with "No command." written below the android.
Press volume up and power until it unlocks the recovery and try to wipe the data and cache partition followed by dalvik cache.
Sent from my Nexus 4 using Tapatalk 4
Thanks for your idea, but it turned out to be hardware problem!
I took the device to the lab and had a look at the usb connector. The contact in the middle was teared of the carrier and was stuck to the back and thus no data connection could be established! I was able to to bend it back (more ore less) to its initial position and now its working. Though I'm wondering how long it will last until its pushed back again.
Fact is, that i was able to connect via fastboot. I tried to flash 4.3 again but it still didn't boot. Its back to 4.2.2 and its working now.
Again - thanks for your idea.
Thread can be closed!
A bit of an SOS situation if anyone knows the right steps please
Well, I restored a Titanium Backup and mistakenly toggled the "restore system apk". It ran fine, all restored and then when I rebooted got stuck.
By "stuck", it re-boots constantly. It shows the LG animation, then all I can see is two messages before it starts booting again:
1) "Unfortunately, Google Play Services Has Stopped"
2) "Unfortunately, System UI has stopped
... and then it does the entire boot sequence, animation, again, and again.
Here is what I can do:
* It is in USB debug mode.
* I have drivers on laptop
* I am able to connect with adb and also shell into phone.
* With adb, I have output to the file an "adb bugreport" as well as an "adb logcat".
* I have several backups:
a) The modemsst1.img and modemsst2.img created by Titanium Backup
b) Titanium backups (full apps and data)
c) an "adb backup - all" backup
* I managed to get it into firmware update mode by pressing the volume up button and the power button and then when it flashed red a few times, just the up button. So, I can get it into Firmware update mode.
Of course, I have never really used adb before, except to dabble a bit. So, I am encouraged that I can somehow get into with shell.
I am not unplugging it until I know what to do!
Since then I have been able to turn the phone off and also put it into charging on USB.
This is what worked:
* Hold down power and volume down button until booting stops and phone turns off completely.
When it does shut down, I kept buttons down until it flashes logo again and then shuts down again. Then I let go. Phone is off and when I plugged in the charger it shows charging animation.
Now, after inspecting the bugreport, I noticed a lot of these messages for all the system apps like this one:
"I/PackageManager(21318): Expecting better updatd system app for com.lge.sizech"
I think the cause of all this shralp is this, I did a LG Mobile Support Tool "Upgrade Recovery" and then in Titanium Backup I restored an older backup (incl system apks). At least that makes sense seeing all the "Expecting better apdat system app" messages in the bugreport.
Still not sure what to do next
I tried the very good instructions here:
[Guide] Unroot/Unbrick - flash official factory firmware with LG Launche
http://forum.xda-developers.com/showthread.php?t=2471370
The update succeeded. However, when I rebooted the phone it is in the same boot-loop with message that it was before.
I used the BELL D803B10D_00.kdz file. Now I will try with the earlier version BELL D803BA_00.kdz file.
We will see what happens ...
do you have nandroid backup from previous rom?
I have three backups:
1) Titanium Backup (full)
* This was my first backup performed right after rooting device and installing Titanium Backup.
2) Titanium Backup (full)
* Did this 2 days ago. Device was working OK and did as precaution.
3) ADB BACKUP. I did this one before my Titanium restore.
I restored the first titanium backup and that (ooooppps!) was after I did an LG Firmware update.
ALSO:
I am on Windows 7 64 and although adb works fine, fastboot does not. I understand that might be a problem with windows 7 64.
So, unless anyone objects, I am going to redo on my windows 32 machine and also "fastbook oem unlock".
Since firmware is OK, if I do the fastboot oem unlock, that will wipe everything. But I can still boot and re-setip the phone, right?
Just checking before I fudge everything up here ..
ALSO ALSO:
I had antivirus/theft security installed and I disabled it partway through last restore.
Maybe that has somethng to do with this all .
But I am still cool because I can ADB and also firmware install seems ok.
ADB works and that is the one good sign.
or you can follow ADB Sideload method
http://forum.xda-developers.com/showthread.php?t=2318497
zekurosu said:
or you can follow ADB Sideload method
http://forum.xda-developers.com/showthread.php?t=2318497
Click to expand...
Click to collapse
I don't (didn't) have TWRP installed. How can I sideload without it?
Also, should I adb oem unlock to get it wiped at this point?
I'm having a similar problem on a Bell D803. Just happened very randomly today. I turned my phone off for an exam, then turned it back on after.. initially had no signal and a black background. Settings for factory reset wouldn't work. My phone is rooted and has TWRP. I went into recovery and formatted.
Bootloop.
Bootloop.
Bootloop x 20.
I however, don't get the same two messages. I just keep bootlooping.
Got home, tried to go through download mode to unbrick it, but for some reason my computer isn't picking it up. I have all the drivers, and before this incident, it was recognized.
Any solutions?
I'm thinking of buying an OTG USB and then just flashing a stock zip from recovery. Would that be a possible viable solution?
asdfvtn said:
I'm having a similar problem on a Bell D803. Just happened very randomly today. I turned my phone off for an exam, then turned it back on after.. initially had no signal and a black background. Settings for factory reset wouldn't work. My phone is rooted and has TWRP. I went into recovery and formatted.
Bootloop.
Bootloop.
Bootloop x 20.
I however, don't get the same two messages. I just keep bootlooping.
Got home, tried to go through download mode to unbrick it, but for some reason my computer isn't picking it up. I have all the drivers, and before this incident, it was recognized.
Any solutions?
I'm thinking of buying an OTG USB and then just flashing a stock zip from recovery. Would that be a possible viable solution?
Click to expand...
Click to collapse
Well, I am able to connect with adb fine on my laptop (Win 7 64) but not on my desktop (Win 7 32)
But on my Win 7 64 I cannot get into fastboot.
I am wondering if the driver install on my desktop went foo-bar and needs reinstall. Also, I noticed that the website drivers are more recent USB drivers than some of the ones linked on this site.
I used adb uninstall package for many user packages and it was success. But I still see the packages listed in the bugreport?
For example: I already uninstalled "com.benhirashima.skiplock" and also "com.lookout".
Why? What to do to really zap them for good?
Sorry, I posted the wrong link earlier.
This was the guide I used which succeeded but made no difference to the boot-loop.
LG G2 Stock Firmware (Go Back to Stock)
http://forum.xda-developers.com/showthread.php?t=2432476&highlight=d803
Just figured out how to do a factory reset.
http://www.youtube.com/watch?v=3ogBvzbPikc
The hard reset worked and now I am configuring the phone settings!
So, again, this is what I did:
1) http://forum.xda-developers.com/showthread.php?p=45293512
2) http://www.youtube.com/watch?v=3ogBvzbPikc
Not sure if it all worked but I am setting the phone up as we speak (or as I type)
natureburger said:
Well, I am able to connect with adb fine on my laptop (Win 7 64) but not on my desktop (Win 7 32)
But on my Win 7 64 I cannot get into fastboot.
I am wondering if the driver install on my desktop went foo-bar and needs reinstall. Also, I noticed that the website drivers are more recent USB drivers than some of the ones linked on this site.
Click to expand...
Click to collapse
Hmm that's strange. Unfortunately for me, I'm already on 64-bit and it still isn't picking it up.
ALL FIXED UP
WORKING 110%
:good:
natureburger said:
ALL FIXED UP
WORKING 110%
:good:
Click to expand...
Click to collapse
I have followed this to a t.
Succesfully flashed the stock firmware that came with the phone when sold.
Did hard reset using the the power button and volume down
= phone rebooting every 10 seconds, no wifi, imei = null
adb devices = offline.
Really depressed right now. If anybody can help me I would appreciate it.
zprovo said:
I have followed this to a t.
Succesfully flashed the stock firmware that came with the phone when sold.
Did hard reset using the the power button and volume down
= phone rebooting every 10 seconds, no wifi, imei = null
adb devices = offline.
Really depressed right now. If anybody can help me I would appreciate it.
Click to expand...
Click to collapse
Press the power button down and hold it.
It should turn off, then look like it is turning on, (flash logo very briefly) and then turn off.
Let go of power button and it should stay off.
Do that. Now, does it work to turn off completely?
Let's see if you can do that first.
Then .. do hard reset, exactly like this:
http://www.youtube.com/watch?v=3ogBvzbPikc
Does the hard reset screen show and give you hard reset options?
natureburger said:
Press the power button down and hold it.
It should turn off, then look like it is turning on, (flash logo very briefly) and then turn off.
Let go of power button and it should stay off.
Do that. Now, does it work to turn off completely?
Let's see if you can do that first.
Click to expand...
Click to collapse
Yup. I totally understand what you are saying and have done it many times. I had to use that method to get into download mode and also had to use it to do hard reset.
I just reflashed the phone all over again a second time succesfully.
Reboots every 5 seconds. Keyboard came up for a few seconds for the first time in 48 hours during the initial setup phase. 5 seconds later as I was trying to input a wifi code it would not appear. then it rebooted as usual.
I really appreciate any input right now. :cyclops::crying:
zprovo said:
Yup. I totally understand what you are saying and have done it many times. I had to use that method to get into download mode and also had to use it to do hard reset.
I just reflashed the phone all over again a second time succesfully.
Reboots every 5 seconds. Keyboard came up for a few seconds for the first time in 48 hours during the initial setup phase. 5 seconds later as I was trying to input a wifi code it would not appear. then it rebooted as usual.
I really appreciate any input right now. :cyclops::crying:
Click to expand...
Click to collapse
1) Are you able to completely turn it off using my instructions?
2) When you hard reset (2nd half of this video), http://www.youtube.com/watch?v=3ogBvzbPikc
a) Does the hard reset screen show?
b) Does it give you the hard reset options?
3) Before it was bricked, was it in 'usb debug mode' in developer options?
4) Which kpz version did you restore to?
5) Did your "adb devices" ever work? Did your "adb shell" ever work?
natureburger said:
1) Are you able to completely turn it off using my instructions?
2) When you hard reset (2nd half of this video), http://www.youtube.com/watch?v=3ogBvzbPikc
a) Does the hard reset screen show?
b) Does it give you the hard reset options?
3) Before it was bricked, was it in 'usb debug mode' in developer options?
Click to expand...
Click to collapse
1) Yes absolutely. It is sitting next to me right now doing nothing at all because I turn it off when I am not trying to fix it, otherwise it keeps rebooting relentlessly.
2) a) Yes, same as the video. b) Yes it says the same exact thing as the video. I press power key twice and it begins. The stock recovery android appears with a loading bar on the bottom for ~1 minute then it goes to the boot "lg animation".
3) Yes it was. Before it was bricked I essentially always had it in debug mode because I successfully rooted it and simply left it on debugging mode after having to activate it to root.
4) D801V11B_00.kdz The EXACT same as the original. This is a Videotron (canadian) phone. I can clearly remember without a doubt going into about phone and this is what it was running before all of this happened.
5) I am having a bit of memory strain here, but I do believe it also said adb devices before any of the issues came. It is a good point I will try "adb device" from another trusted computer.
Other notes: I can browse the android os for a few seconds. Sometimes sound does not work, wifi is non functional (even though the keyboard never appears, I managed to have a security free wifi in my proximity and it would not connect (was saying: temporarily avoiding bad signal)) and also I do have modemstat1.img and modemstat2.img backups for EFS.
adb devices consistently shows "offline" but it is definitely recognizing the phone. I have also tried using usb debugging activated and still "offline". Drivers are up to date and all.
The upper drawer in the usual g2 user interface is strange now. it doesnt have anything except for the date (1970 something...) and a "gear" icon for system settings. I am talking the drawer you drag down from the top of the screen.
This phone was working with absolutely no problems 2 days ago.
Thank you so much for looking into this. I have certainly exhausted my repairing capacities. I am entirely dependent upon the knowledgeable individuals in here from here on out.
zprovo said:
1) Yes absolutely. It is sitting next to me right now doing nothing at all because I turn it off when I am not trying to fix it, otherwise it keeps rebooting relentlessly.
2) a) Yes, same as the video. b) Yes it says the same exact thing as the video. I press power key twice and it begins. The stock recovery android appears with a loading bar on the bottom for ~1 minute then it goes to the boot "lg animation".
3) Yes it was. Before it was bricked I essentially always had it in debug mode because I successfully rooted it and simply left it on debugging mode after having to activate it to root.
4) D801V11B_00.kdz The EXACT same as the original. This is a Videotron (canadian) phone. I can clearly remember without a doubt going into about phone and this is what it was running before all of this happened.
5) I am having a bit of memory strain here, but I do believe it also said adb devices before any of the issues came. It is a good point I will try "adb device" from another trusted computer.
Other notes: I can browse the android os for a few seconds. Sometimes sound does not work, wifi is non functional (even though the keyboard never appears, I managed to have a security free wifi in my proximity and it would not connect (was saying: temporarily avoiding bad signal)) and also I do have modemstat1.img and modemstat2.img backups for EFS.
adb devices consistently shows "offline" but it is definitely recognizing the phone. I have also tried using usb debugging activated and still "offline". Drivers are up to date and all.
The upper drawer in the usual g2 user interface is strange now. it doesnt have anything except for the date (1970 something...) and a "gear" icon for system settings. I am talking the drawer you drag down from the top of the screen.
This phone was working with absolutely no problems 2 days ago.
Thank you so much for looking into this. I have certainly exhausted my repairing capacities. I am entirely dependent upon the knowledgeable individuals in here from here on out.
Click to expand...
Click to collapse
Hmmmm..... why your adb devices is not working? But the re-pair works and you can then do hard reset.
But that is good information you shared.
Maybe someone else can chime in.
From my experience:
1) adb usb access seems spotty. My win 7 64 connected fine and it even kept the shell through the reboot cycle. But on my win 7 32 machine it was only detecting device and then not able to shell.
2) I was also able to use from the LG website LG MOBILE SUPPORT TOOLS.
Download the LG MOBILE SUPPORT TOOL
I downloaded the most recent one from the LG website and make sure to select your options >> country and then the correct phone model at the upper right hand corner of the tool.
Then install USB driver for correct phone model.
Then see if USB works, "adb device" should return the device code.
"adb shell" should show the shell prompt.
3) There is always fastboot. But I an noob and know 0% about how to properly connect and use it.
Some others please chime in and help this droid bro!
I don't know where to start with my problem.
Firstly my Nexus 7, 2012 , 5.1.1 android , nakasi- grouper version tablet was very slow. Tried all the known recovery mode options etc. but nothing really changed. So I decided to Root it .
In order to root it properly I download the wugfresh root toolkit. I knew that my USB port was quite unstable but I thought I could risk it, since I didn't have anything serious in there, and at the end of the day I was trying a clean re-installation.
Before doing anything I decided to flash the stock rom and unroot it (since I didn't know if the device was at a correct- clean factory state.... Just for the sake of it) Unfortunatelly I might also have chosen the 2013 version because I didn't really know the differences)...
Everything went well, up to the point that a cmd said that there was no device and stuck there. It was in the bootloader mode and couldn't move. I disconnected the device from the USB, pressed hard and for more than 30 secs the power button, it switched off. Then I pressed hard the power button for a long time (and after that many more times) but it never came back to life.
I tried to press any combination of buttons many times. Disconnected the battery. Actually measured it for voltage and current (everything's fine). Charged it in an alternative way. Reconnected it (several times). To no result. Dead device. I can call it hard-bricked, but to me, it's more like dead.
Any idea what went wrong and if there's any chance for this tablet to come back to life? Is it worth it? No serious data in there. Haven't backed up anything related to it.
Thanks in advance.
Take the back off of thr device and carefully disconnect the battery. Wait 5 minutes, then plug battery back in and replace the back.
If you can get a pogo cable you can charge without using the USB. Either way, kust let it charge for a few hours, then try to power up.
The Root Kit has a recover from boot loop option you should use. It will download the last official rom and flash it unrooting your system. Just make sure you choose the right model of nexus when you start.
Good luck
Sent from my LGLS992 using Tapatalk
psiphi said:
Take the back off of thr device and carefully disconnect the battery. Wait 5 minutes, then plug battery back in and replace the back.
If you can get a pogo cable you can charge without using the USB. Either way, kust let it charge for a few hours, then try to power up.
The Root Kit has a recover from boot loop option you should use. It will download the last official rom and flash it unrooting your system. Just make sure you choose the right model of nexus when you start.
Good luck
Sent from my LGLS992 using Tapatalk
Click to expand...
Click to collapse
Thanks for the reply.
No chance with solution number one.
As I said I 've left it charge for more than 10 hours. Measured the battery's poles.
Around4 volts, 2.7 amps. Everything's fine with the battery.
The tab won't boot at all. Can't enter bootloader, can't be recognised by the USB, can't use the Root Kit.
tedsorvino said:
I don't know where to start with my problem.
Firstly my Nexus 7, 2012 , 5.1.1 android , nakasi- grouper version tablet was very slow. Tried all the known recovery mode options etc. but nothing really changed. So I decided to Root it .
In order to root it properly I download the wugfresh root toolkit. I knew that my USB port was quite unstable but I thought I could risk it, since I didn't have anything serious in there, and at the end of the day I was trying a clean re-installation.
Before doing anything I decided to flash the stock rom and unroot it (since I didn't know if the device was at a correct- clean factory state.... Just for the sake of it) Unfortunatelly I might also have chosen the 2013 version because I didn't really know the differences)...
Everything went well, up to the point that a cmd said that there was no device and stuck there. It was in the bootloader mode and couldn't move. I disconnected the device from the USB, pressed hard and for more than 30 secs the power button, it switched off. Then I pressed hard the power button for a long time (and after that many more times) but it never came back to life.
I tried to press any combination of buttons many times. Disconnected the battery. Actually measured it for voltage and current (everything's fine). Charged it in an alternative way. Reconnected it (several times). To no result. Dead device. I can call it hard-bricked, but to me, it's more like dead.
Any idea what went wrong and if there's any chance for this tablet to come back to life? Is it worth it? No serious data in there. Haven't backed up anything related to it.
Thanks in advance.
Click to expand...
Click to collapse
Hi, tedsorvino...
I hate to be the bearer of bad news, but I suspect your Nexus 7's bootloader has become corrupted (possibly due to a faulty USB connection during your wugfresh reflash), or overwritten with an incompatible bootloader for your specific device type, vis-a-vis your reference to flashing the wrong ROM.
Either way, without a valid bootloader, your Nexus 7 will likely never boot again.
Or at least, not without a motherboard replacement, which is probably not worth the hassle or the cost for such an old device.
Flashing the bootloader (either on its own or as part of a full device reflash) was always one of the most risky aspects of reflashing the Nexus 7; it required a healthy battery charge and a solid, stable USB cable connection. It was something I approached with trepidation on my old Nexus 7, and if at all possible, it was something I tried to avoid.
The bootloader is a device critical component for booting the device and also for reflashing it with fastboot commands, because it's the bootloader that accepts and handles those fastboot commands, either directly via a Window's command prompt or with something like Wugresh's toolkit.
And when it gets corrupted or overwritten with something other than a valid bootloader image file, the Nexus 7 is hardbricked, and the only solution is a motherboard replacement.
Ged.
GedBlake said:
Hi, tedsorvino...
I hate to be the bearer of bad news, but I suspect your Nexus 7's bootloader has become corrupted (possibly due to a faulty USB connection during your wugfresh reflash), or overwritten with an incompatible bootloader for your specific device type, vis-a-vis your reference to flashing the wrong ROM.
Either way, without a valid bootloader, your Nexus 7 will likely never boot again.
Or at least, not without a motherboard replacement, which is probably not worth the hassle or the cost for such an old device.
Flashing the bootloader (either on its own or as part of a full device reflash) was always one of the most risky aspects of reflashing the Nexus 7; it required a healthy battery charge and a solid, stable USB cable connection. It was something I approached with trepidation on my old Nexus 7, and if at all possible, it was something I tried to avoid.
The bootloader is a device critical component for booting the device and also for reflashing it with fastboot commands, because it's the bootloader that accepts and handles those fastboot commands, either directly via a Window's command prompt or with something like Wugresh's toolkit.
And when it gets corrupted or overwritten with something other than a valid bootloader image file, the Nexus 7 is hardbricked, and the only solution is a motherboard replacement.
Ged.
Click to expand...
Click to collapse
Thank you. Even if the news are bad, it's a really valuable piece of information. At least now I know.
Hello Guys, beforehand, sorry for bad formatting and some english mistakes.
Let me explain what happened.
I was trying to unlock my Nexus 7 bootloader, but I couldn´t get to the Fastboot mode via adb, so I decided to enter fastboot mode by pressing Power + Volume Down button, but I did this while my tablet was connected to the PC, and after that, it shut down and just don´t turned on anymore. (Never got to fastboot mode)
Now when I connect to windows it only show as an AXP Device and it disconnects and connects when i hold Power button, but never starts.
Also I want to note that.
I didn´t manage to get into fastboot mode.
I didn´t manage to unlock the bootloader.
Didn´t install any Custom Rom.
The device is technically 100% stock, so I don´t expect it to be a Hard Brick, but at the same time, I tried all the button combinations and it still wont turn on.
This happened to anyone? Do you guys have any idea what it could be? Any Sollutions for this?
Thank you.
(Edit: I don´t have the Blobs.bin file in case i need to use the Nvflash.)
Gabu1405 said:
Hello Guys, beforehand, sorry for bad formatting and some english mistakes.
Let me explain what happened.
I was trying to unlock my Nexus 7 bootloader, but I couldn´t get to the Fastboot mode via adb, so I decided to enter fastboot mode by pressing Power + Volume Down button, but I did this while my tablet was connected to the PC, and after that, it shut down and just don´t turned on anymore. (Never got to fastboot mode)
Now when I connect to windows it only show as an AXP Device and it disconnects and connects when i hold Power button, but never starts.
Also I want to note that.
I didn´t manage to get into fastboot mode.
I didn´t manage to unlock the bootloader.
Didn´t install any Custom Rom.
The device is technically 100% stock, so I don´t expect it to be a Hard Brick, but at the same time, I tried all the button combinations and it still wont turn on.
This happened to anyone? Do you guys have any idea what it could be? Any Sollutions for this?
Thank you.
(Edit: I don´t have the Blobs.bin file in case i need to use the Nvflash.)
Click to expand...
Click to collapse
Take a look at this comprehensive listing of Nexus 7 button presses/interrupts. They may be of some use...
https://forum.xda-developers.com/showthread.php?p=37606945#post37606945
Hi, Gabu1405...
APX mode is never a good sign with the Nexus 7. It usually indicates that the bootloader has become corrupted, erased or overwritten (by something that is not a valid bootloader). When this occurs, the device is hardbricked and usually requires a motherboard replacement to resurrect the device, although there is a procedure called 'flatline', but this requires previously generated device unique 'blob' files, which you mention in your post.
Having said all of that though, nothing in your description should have caused the bootloader to have become 'damaged'. In order to erase, corrupt or overwrite the bootloader, your device would need to be bootloader unlocked in the first place, because a locked bootloader prohibits any unauthorised write access - bootloader locked devices can only be system 'modified' by official digitally signed updates from Google, which are flashed via the stock recovery.
Are you certain the Nexus 7 is showing as an APX device in Windows device manager?
What was the battery status/percentage when you attempted to unlock the bootloader? Maybe the tablet just needs a good charge, maybe for several hours!
You don't unlock the bootloader with ADB. Android Debug Bridge only works in fully booted Android and with the stock factory recovery. You need to use fastboot to unlock the bootloader, the command being fastboot oem unlock, whilst the device is in fastboot mode, which you boot into via the Volume Down+Power Button key press combo, as you mention in your post.
How it (may have) got into APX mode is certainly strange, because as I've said, this isn't something that normally happens spontaneously - when it happens, it's often due to people mistakenly flashing an incorrect .IMG file to the bootloader partition, causing the bootloader to be overwritten. A possible explanation is hardware failure, and that the emmc/NAND chip storage has developed a fault, and caused the bootloader to become corrupted. It's worth bearing in mind that the Nexus 7 is now seven years old, and with the best will in the world, these things don't last forever, unfortunately. Components fail and data corruptions occur.
If your Nexus 7 is truly in APX mode, for whatever reason, then I'm afraid it's likely hardbricked, and a motherboard replacement is the only realistic way of resurrecting it.
I can only suggest you try charging your Nexus 7, maybe overnight, or for several hours at least, and maybe try the button presses referenced via the link at the top of this post, and see if you can coax life back into your Nexus 7. It does happen sometimes; a seemingly dead device will suddenly spring back to life, through a combination of serendipity and hitting on doing the right things, in the right order, and at the right time
Good luck, Gabu1405...
Rgrds,
Ged.
GedBlake said:
Take a look at this comprehensive listing of Nexus 7 button presses/interrupts. They may be of some use...
https://forum.xda-developers.com/showthread.php?p=37606945#post37606945
Hi, Gabu1405...
APX mode is never a good sign with the Nexus 7. It usually indicates that the bootloader has become corrupted, erased or overwritten (by something that is not a valid bootloader). When this occurs, the device is hardbricked and usually requires a motherboard replacement to resurrect the device, although there is a procedure called 'flatline', but this requires previously generated device unique 'blob' files, which you mention in your post.
Having said all of that though, nothing in your description should have caused the bootloader to have become 'damaged'. In order to erase, corrupt or overwrite the bootloader, your device would need to be bootloader unlocked in the first place, because a locked bootloader prohibits any unauthorised write access - bootloader locked devices can only be system 'modified' by official digitally signed updates from Google, which are flashed via the stock recovery.
Are you certain the Nexus 7 is showing as an APX device in Windows device manager?
What was the battery status/percentage when you attempted to unlock the bootloader? Maybe the tablet just needs a good charge, maybe for several hours!
You don't unlock the bootloader with ADB. Android Debug Bridge only works in fully booted Android and with the stock factory recovery. You need to use fastboot to unlock the bootloader, the command being fastboot oem unlock, whilst the device is in fastboot mode, which you boot into via the Volume Down+Power Button key press combo, as you mention in your post.
How it (may have) got into APX mode is certainly strange, because as I've said, this isn't something that normally happens spontaneously - when it happens, it's often due to people mistakenly flashing an incorrect .IMG file to the bootloader partition, causing the bootloader to be overwritten. A possible explanation is hardware failure, and that the emmc/NAND chip storage has developed a fault, and caused the bootloader to become corrupted. It's worth bearing in mind that the Nexus 7 is now seven years old, and with the best will in the world, these things don't last forever, unfortunately. Components fail and data corruptions occur.
If your Nexus 7 is truly in APX mode, for whatever reason, then I'm afraid it's likely hardbricked, and a motherboard replacement is the only realistic way of resurrecting it.
I can only suggest you try charging your Nexus 7, maybe overnight, or for several hours at least, and maybe try the button presses referenced via the link at the top of this post, and see if you can coax life back into your Nexus 7. It does happen sometimes; a seemingly dead device will suddenly spring back to life, through a combination of serendipity and hitting on doing the right things, in the right order, and at the right time
Good luck, Gabu1405...
Rgrds,
Ged.
Click to expand...
Click to collapse
Sorry, I expressed myself wrongly, I ran the same command as you said, it was fastboot oem unlock and it just said, "waiting for device..." then I tried fastboot oem unlock-go, also the same thing "waiting for device" so I just disconnected the tablet and restarted it and it was working pretty fine, then I connected to the PC and tried to enter fastboot mode manually, and this is when it shut down and never turned back on.
Also, my battery was at 70% at that time and yes, It's clearly on APX mode.
Well, thank you for your reply, now the only thing I got to do is recharge it and hope for the best.
Regards.
Gabu1405 said:
Sorry, I expressed myself wrongly, I ran the same command as you said, it was fastboot oem unlock and it just said, "waiting for device..." then I tried fastboot oem unlock-go, also the same thing "waiting for device" so I just disconnected the tablet and restarted it and it was working pretty fine, then I connected to the PC and tried to enter fastboot mode manually, and this is when it shut down and never turned back on.
Also, my battery was at 70% at that time and yes, It's clearly on APX mode.
Well, thank you for your reply, now the only thing I got to do is recharge it and hope for the best.
Regards.
Click to expand...
Click to collapse
Probably not much use until, or indeed if, you can get out of APX Mode... But the 'waiting for device' message is usually an indicator of a Windows driver problem - Windows is not able to communicate with the Nexus 7.
The way you'd normally do things is by first running the command fastboot devices
This command does nothing, except to confirm you have a viable fastboot connection, by displaying your Nexus 7's unique serial number in your Windows Command/DOS box. If this serial number fails to appear, you have a driver/connectivity problem and proceeding on to fastboot oem unlock would be pointless until the driver/connectivity problem is resolved.
Anyway, I hope charging the device helps. I'm still inclined to think that your device is recoverable - it would certainly be very unusual for the bootloader to be borked when it hasn't even been unlocked yet. In the seven years I've been a Nexus 7 owner, and being active on these forums for many of those years, I haven't encountered any reports by other XDA members where a locked bootloader has simply quit working... As I say, it'd be very unusual, but I suppose not wholly impossible.
Rgrds,
GB.
GedBlake said:
Probably not much use until, or indeed if, you can get out of APX Mode... But the 'waiting for device' message is usually an indicator of a Windows driver problem - Windows is not able to communicate with the Nexus 7.
The way you'd normally do things is by first running the command fastboot devices
This command does nothing, except to confirm you have a viable fastboot connection, by displaying your Nexus 7's unique serial number in your Windows Command/DOS box. If this serial number fails to appear, you have a driver/connectivity problem and proceeding on to fastboot oem unlock would be pointless until the driver/connectivity problem is resolved.
Anyway, I hope charging the device helps. I'm still inclined to think that your device is recoverable - it would certainly be very unusual for the bootloader to be borked when it hasn't even been unlocked yet. In the seven years I've been a Nexus 7 owner, and being active on these forums for many of those years, I haven't encountered any reports by other XDA members where a locked bootloader has simply quit working... As I say, it'd be very unusual, but I suppose not wholly impossible.
Rgrds,
GB.
Click to expand...
Click to collapse
Well, charged my device for a whole day, and now I tried to do the button combinations which you sent the link, nothing happened.
I thought that my battery could be unplugged or the cable was loose or something, so I opened the tablet and it was fine.
So, I just decided to do the button combinations while plugged into my PC, and I noticed that doesn´t matter which combination I try, the tablet disconnects from the PC and instantly reconnects, but still in APX mode.
I guess it is Game Over for me, gonna recharge it again, and try again tomorrow.
Thanks again.
Gabu1405 said:
Hello Guys, beforehand, sorry for bad formatting and some english mistakes.
Let me explain what happened.
I was trying to unlock my Nexus 7 bootloader, but I couldn´t get to the Fastboot mode via adb, so I decided to enter fastboot mode by pressing Power + Volume Down button, but I did this while my tablet was connected to the PC, and after that, it shut down and just don´t turned on anymore. (Never got to fastboot mode)
Now when I connect to windows it only show as an AXP Device and it disconnects and connects when i hold Power button, but never starts.
Also I want to note that.
I didn´t manage to get into fastboot mode.
I didn´t manage to unlock the bootloader.
Didn´t install any Custom Rom.
The device is technically 100% stock, so I don´t expect it to be a Hard Brick, but at the same time, I tried all the button combinations and it still wont turn on.
This happened to anyone? Do you guys have any idea what it could be? Any Sollutions for this?
Thank you.
(Edit: I don´t have the Blobs.bin file in case i need to use the Nvflash.)
Click to expand...
Click to collapse
Hi!
I had a Nexus 7 stuck in APX mode as well. Without the blobs saved you can't do anything. I tried a lot of thigs but nothing really helped. I ended up searching for an another N7 with a broken screen but with a working motherboard online. I was lucky and find one around $15. I swapped the boards and it was good to go.
Zsolti
Gabu1405 said:
Hello Guys, beforehand, sorry for bad formatting and some english mistakes.
Let me explain what happened.
I was trying to unlock my Nexus 7 bootloader, but I couldn´t get to the Fastboot mode via adb, so I decided to enter fastboot mode by pressing Power + Volume Down button, but I did this while my tablet was connected to the PC, and after that, it shut down and just don´t turned on anymore. (Never got to fastboot mode)
Now when I connect to windows it only show as an AXP Device and it disconnects and connects when i hold Power button, but never starts.
Also I want to note that.
I didn´t manage to get into fastboot mode.
I didn´t manage to unlock the bootloader.
Didn´t install any Custom Rom.
The device is technically 100% stock, so I don´t expect it to be a Hard Brick, but at the same time, I tried all the button combinations and it still wont turn on.
This happened to anyone? Do you guys have any idea what it could be? Any Sollutions for this?
Thank you.
(Edit: I don´t have the Blobs.bin file in case i need to use the Nvflash.)
Click to expand...
Click to collapse
Check out my guide.