Develop Bugs

[Q] My nexus 7 2013 died when I tried to change lcd density

I rooted my nexus 7 2013 yesterday with towel root and it worked just fine for 24h and today I went to build.prop and changed the lcd density from 320 to 220 and now my nexus wont reboot it just says GOOGLE and then the screen sits on for few seconds and then it goes off . i can get to the bootloader and recovery mode normally but the software wont start up. Im using the stock rom ,bootloader and recovery . I tried to go with fartory reset and it didnt help and neither did adb sideload installation of the stock rom. In the sideload mode it just says someting about the footer is wrong or something. Is anyone able to help me or in same situation ?

Im a n00b
It wont let anythin to be installed from the sideload is it because of i farctory wiped it or somthing and now it isnt on debugging mode or is that because i didnt unloc the bootloader when i rooted my nexus?

Phone breaker 3000 said:
It wont let anythin to be installed from the sideload is it because of i farctory wiped it or somthing and now it isnt on debugging mode or is that because i didnt unloc the bootloader when i rooted my nexus?
Click to expand...
Click to collapse
It's a nexus device. Just download the original image files from Google and flash them in fastboot mode.

E:verification failed :C
mindmajick said:
It's a nexus device. Just download the original image files from Google and flash them in fastboot mode.
Click to expand...
Click to collapse
tryed to use sideload and it just says E:footer is wrong
E:signature verification failed
installation aborted

fastbootmode?
when i open my bootloader it says FASTBOOTMODE on red font and then product number etc and secure boot -- enabled Lock state -- enabled
and adb wont recognize it in this mode but it recognizes it in therecovery mode

I cant do anything cuz the bootloader is locked :CC
Is there a way to unlock the booloader with the software compeletely dead

fastboot oem unlock

im just a noob who cant use google XDD
Phone breaker 3000 said:
Is there a way to unlock the booloader with the software compeletely dead
Click to expand...
Click to collapse
fixed it and ewerything is fine now but6 i lost all my data tough :C

[Q] Nexus 7 stuck at Google logo and can't unlock bootloader

Hi all
Interesting issue that I've searched here and Google for and not getting far, my searching skills may not be the best though as I'm fairly new to this.
My Nexus 7 was working fine, put it on the side, came back and it's turned off. Thinking it's flat I charge it and try to boot it with no success. Pressing the power for a while does get it to turn on but it gets as far as the Google logo and stays there.
I've factory reset it in the recovery and nothing
I've tried to flash the stock image from Google but when unlocking the bootloader it just sticks on "yes" forever and nothing happens.
What can I do at this point?
Cheers

Acksaw said:
Hi all
Interesting issue that I've searched here and Google for and not getting far, my searching skills may not be the best though as I'm fairly new to this.
My Nexus 7 was working fine, put it on the side, came back and it's turned off. Thinking it's flat I charge it and try to boot it with no success. Pressing the power for a while does get it to turn on but it gets as far as the Google logo and stays there.
I've factory reset it in the recovery and nothing
I've tried to flash the stock image from Google but when unlocking the bootloader it just sticks on "yes" forever and nothing happens.
What can I do at this point?
Cheers
Click to expand...
Click to collapse
Have you heard of Wugfresh Tool kit ? (aka Nexus Tool Kit) It is in the development section or you can google it. It is quite famous.
It will do anything actually from drivers to repair a device stuck on google logo. Just make sure you select the correct option.
You will need unlocked bootloader to flash stock images. And to do either of those, you will need drivers!
Install drivers and use it to recover your device. If you still have trouble, quote me back and I will help you to my best of ability.
Look into the forum before posting your questions. There are so many similar problems and you can easily find a solution by reading their questions and their possible solution.
Good Luck!

I'm having issues with my nexus 7 (2013). It will not boot up,it's stuck on Google logo. I am able to put in fastboot mode. I'd like to do a hard reset/wipe but I cannot enter recovery mode; it just goes to the Google logo and doesn't show me the recovery menu. I thought I could try doing it through adb but bootloader is locked. Downloaded WugFresh toolkit but it requires correct build number, which I do not know. I tried different ones but everything fails. AND USB debugging is not enabled, but I cannot do it through my tablet because it won't pass bootloop. I haven't been able to enable it remotely. So, any help with getting this tablet up and awake?! It's not rooted BTW, its running stock 6.0 marshmallow

MGreen1216 said:
... issues with my nexus 7 (2013) ... stuck on Google logo. I am able to put in fastboot mode ... doesn't show me the recovery menu ... bootloader is locked. Downloaded WugFresh toolkit but it requires correct build number, which I do not know. I tried different ones but everything fails. AND USB debugging is not enabled, but I cannot do it through my tablet because it won't pass bootloop. I haven't been able to enable it remotely. So, any help with getting this tablet up and awake?! It's not rooted BTW, its running stock 6.0 marshmallow
Click to expand...
Click to collapse
Interesting, and troubling for you, I'm sure.
-- What do you mean, in fastboot it doesn't show you the recovery menu? If you are into (more properly) bootloader mode, the Recovery option has to be there. Do you mean you just can't select it, or that it won't work when you do select it?
-- Using fastboot, you might be able to boot into custom recovery without flashing it. (e.g. "fastboot boot twrp.img", not "fastboot flash recovery twrp.img".
-- Have you tried unlocking the bootloader via fastboot? Is it possible OEM Unlock is already/still enabled somehow?
-- Also.... Wug's NRT doesn't need the correct verion/build. The last option in the drop-down menu on the NRT is this: << Android *.*.* - Any Build >>
HTH

-- When i go into bootloader/fastboot mode, the option is there for recovery mode along with 'start' and 'power off',etc.. However, when I select it,it just hangs on Google logo and never shows me the Android man and recovery options.
-- Sorry, not sure what you mean by this: "Using fastboot, you might be able to boot into custom recovery without flashing it. (e.g. "fastboot boot twrp.img", not "fastboot flash recovery twrp.img"."
I may need some instructions on how to do this please.
-- I have tried unlocking bootloader via WugFresh and Nexus toolkit and via adb but it hangs on erasing user data and also hangs on 'unlock bootloader's screen (left it for over 12 hrs). I doubt anything is unlocked.
--Yes, I tried the "any build" option and nothing works.
Thank you
I'm open to any suggestions.

MGreen1216 said:
--- not sure what you mean by this: "Using fastboot, you might be able to boot into custom recovery without flashing it. (e.g. "fastboot boot twrp.img", not "fastboot flash recovery twrp.img"."
I may need some instructions on how to do this please.
Click to expand...
Click to collapse
Ah, right. I didn't read closely, and didn't realize you might not have used fastboot tools... and please, I'm no expert, so if I'm saying somthing inaccurate, I very much hope someone will correct me.
I'm never sure how much a poster knows, so I'm not sure if you meant you don't know fastboot commands at all, or just the specific ones I mentioned .. fastboot commands are like ADB commands, but run in the bootloader environment. We know you have fastboot commands installed and fastboot drivers installed on your computer because you have adb installed - which includes fastboot, and you said WugFresh's tool was able to run, which means you also have the right fastboot drivers (the NRT uses the same fastboot commands).
fastboot can be used to flash/install custom recovery packages, among a whole lot of other things. So what I mentioned in that command was a possible way to maybe get into a custom recovery if you have to do things like wipes or whatever, even if you can't actually fully install the custom recovery. You might need to do this stuff, if you can't unlock your bootloader and flash the whole official Google Factory Image from their website (which is what I'd try - simple instructions are right there, too).
Flashing the full factory image will wipe your device, of course, but there are simple ways around that, which you can find on this very forum. Good luck.
Let us know how you get on.
<<< Any device that's bootable at all is recoverable...... usually... >>>

Stuck in boot loop and can't get into fastboot mode to use adb, need help

I followed this tutorial: http://forum.xda-developers.com/g4/general/unlock-bootloader-install-twrp-root-t3128241
Here's what I did:
Unlocked bootloader
Booted into TWRP (version 3.0) (didn't install, just booted into)
Flashed SuperSU
Rebooted into system
Now whenever I boot the device I'm stuck in a boot loop.
So I can't boot the device up or get into fastboot mode (what should fastboot mode look like? I got into download mode at some point), not sure what to do?

I had same problem once, managed to handle it with LGUP and refubrish full stock rom

ashensii said:
I had same problem once, managed to handle it with LGUP and refubrish full stock rom
Click to expand...
Click to collapse
I tried LGUP but it says the Model is "unknown" so when I select my phone it says "You have to select a known model, please." Can someone help?

I also tried flashing a stock kdz using LG flash tool but I got an error. Does anyone know what I can do? I can get my phone into download mode but don't know what to do on my computer.
I'll give someone $20 if they can help fix my phone for me

Paul397 said:
I also tried flashing a stock kdz using LG flash tool but I got an error. Does anyone know what I can do? I can get my phone into download mode but don't know what to do on my computer.
I'll give someone $20 if they can help fix my phone for me
Click to expand...
Click to collapse
With LG up if it comes up with device unknow with usb cable still pluged in pull battery out then put it back.

Paul397 said:
I also tried flashing a stock kdz using LG flash tool but I got an error. Does anyone know what I can do? I can get my phone into download mode but don't know what to do on my computer.
I'll give someone $20 if they can help fix my phone for me
Click to expand...
Click to collapse
I had the same problem.
If you can get your phone in the download mode, than try this.
1: Install LGBridge,
2: Boot your phone in download mode & start LGBridge,
3: Than on Software Update tab, on the bottom right corner, you will see an option saying "Update Error Recovery"
4: Click on it and your phone will be flashed to latest firmware. Make sure you are connected to net as it will need to download it.
Once the update it complete, Your phone should reboot normally.
Give it a try and let me know how it goes.

M9 bootloop and no downlaod mode - unbrick possible?

Hi guys,
my father's M9 was on the newest ViperOne for some time now.
Now a few problems popped up:
1. If the device is turned off and you plug it in to charger, it boots into bootloader
2.booting to download mode results in "failed to boot to download mode"
3.Every ROM i install via TWRP is ending in a boot loop (The boot-animation is visible for about a second)
4. i tried other TWRP version, other ROMs and other Kernels and also wiped the complete device.
As I dont get into downlaod mode, I dont know how to recover the device to stock ROM via RUU at least.
Any help is appreciated! Thanks!

download RUU your correct current *os/sku number* installed version, you can find it at
https://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698
Click to expand...
Click to collapse
you should have thanks to mr flippy498
**download adb universal driver and adb debugger or htc driver.
1. plug your phone to pc/laptop and install on** desrciptions above
2.open RUU and follow the rules and wait until finish *cafully if your cable is disconnect/unlpug or your phone force reboot by your own hands it will cause abnormal problem or your phone will never boot

I can't because, like I said, I cannot boot into download mode (black screen saying "failed to boot to download mode").

LeErdnuss said:
Hi guys,
my father's M9 was on the newest ViperOne for some time now.
Now a few problems popped up:
1. If the device is turned off and you plug it in to charger, it boots into bootloader
2.booting to download mode results in "failed to boot to download mode"
3.Every ROM i install via TWRP is ending in a boot loop (The boot-animation is visible for about a second)
4. i tried other TWRP version, other ROMs and other Kernels and also wiped the complete device.
As I dont get into downlaod mode, I dont know how to recover the device to stock ROM via RUU at least.
Any help is appreciated! Thanks!
Click to expand...
Click to collapse
What os are you currently running? And what version of twrp are you on?
I know you've said you've installed other twrp versions/roms/kernels but to know which is most compatible, your firmware and a bit more info is needed.

I'm willing to bet it's an s-on device too.
If you can't get to download mode, what modes CAN you get it to?.
Beamed in by telepathy.

C.f. Q7

[SOLVED] Hardbricked, but bootloops instead of "System got destroyed" text error.

so my ginkgo got hardbricked today.. i couldn't access fastboot and recovery mode. but it does bootloop instead of getting the text "System got destroyed"...
Anybody got a solution for this? I tried to flash TWRP to wipe my data, and use MiFlashTool to relock the bootloader as well as flash MIUI stock rom.

hellohell0 said:
so my ginkgo got hardbricked today.. i couldn't access fastboot and recovery mode. but it does bootloop instead of getting the text "System got destroyed"...
Click to expand...
Click to collapse
"System got destroyed" does not display on all types of bricks
hellohell0 said:
Anybody got a solution for this? I tried to flash TWRP to wipe my data, and use MiFlashTool to relock the bootloader as well as flash MIUI stock rom.
Click to expand...
Click to collapse
make sure the power button is not stuck
do not relock your bootloader (you have no chance of fixing it while locked,beside EDL)
try flashing VBMETA first, then see with a custom recovery

loopypalm said:
"System got destroyed" does not display on all types of bricks
make sure the power button is not stuck
do not relock your bootloader (you have no chance of fixing it while locked,beside EDL)
try flashing VBMETA first, then see with a custom recovery
Click to expand...
Click to collapse
Hello. Sorry I couldn't reply quicker due to busy week. I tried to flash TWRP through fastboot mode but no luck. So, flashing VBMETA would be useless too, Since fastboot couldn't recognize my phone (
Code:
fastboot devices
). Please note that I've had the USB driver installed for my phone.

hellohell0 said:
Hello. Sorry I couldn't reply quicker due to busy week. I tried to flash TWRP through fastboot mode but no luck. So, flashing VBMETA would be useless too, Since fastboot couldn't recognize my phone (
Code:
fastboot devices
). Please note that I've had the USB driver installed for my phone.
Click to expand...
Click to collapse
i'm not sure what could be the problem here (no enough data)
could be the usb cable
could be the usb port
could be the windows version/drivers ...
if you are 100% sure those are not the cause then your only left option is EDL

loopypalm said:
i'm not sure what could be the problem here (no enough data)
could be the usb cable
could be the usb port
could be the windows version/drivers ...
if you are 100% sure those are not the cause then your only left option is EDL
Click to expand...
Click to collapse
Just got back from my friend's house. Yes, the solution is EDL
My phone is back to normal now, but this would happen again since my friend told me that the eMMC might be corrupted.
Thank you for the help! I thought it was impossible since my phone won't fully recognized in the PC (It was called Android but with question mark)
Case closed.