[Q] My nexus 7 2013 died when I tried to change lcd density - Nexus 7 (2013) Q&A

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

Related

[Q] Nexus 7 2013 32GB stuck on google screen

Hi I'm new here, I have a nexus 7 2013 which wont go past the google screen, it just sits there doing nothing. I can still get into recovery mode and do a factory reset using wipe data/factory reset but it comes up with a bunch of errors such as:
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E:Failed closing /dev/block/platform/msm_sdcc.1/by-name/misc (I/O error)
etc.
I have no idea what to do. I've only had the Nexus since October 2013. It has been running the stock Kitkat 4.4.2 with no root or any bootloader mods
I dont know if this has anything to do with it but last night my sister turned the Nexus on but just as it finished booting (it got to the lock screen) she turned it off straight away before things like the notification bar and background had loaded up. We only turned it on about an hour ago and that was when the Nexus got stuck on the Google logo screen. Also the Nexus was plugged into the stock charger that came with it while this was happening.
What do I do from here?
Is the device bricked?
Or is it as simply flashing a ROM?
Many Thanks
Saajan
saajan_b123 said:
Hi I'm new here, I have a nexus 7 2013 which wont go past the google screen, it just sits there doing nothing. I can still get into recovery mode and do a factory reset using wipe data/factory reset but it comes up with a bunch of errors such as:
E: failed to mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E:Failed closing /dev/block/platform/msm_sdcc.1/by-name/misc (I/O error)
etc.
I have no idea what to do. I've only had the Nexus since October 2013. It has been running the stock Kitkat 4.4.2 with no root or any bootloader mods
I dont know if this has anything to do with it but last night my sister turned the Nexus on but just as it finished booting (it got to the lock screen) she turned it off straight away before things like the notification bar and background had loaded up. We only turned it on about an hour ago and that was when the Nexus got stuck on the Google logo screen. Also the Nexus was plugged into the stock charger that came with it while this was happening.
What do I do from here?
Is the device bricked?
Or is it as simply flashing a ROM?
Many Thanks
Saajan
Click to expand...
Click to collapse
I would suggest that you put it into fastboot mode (aka get to the bootloader), and fastboot flash the factory image. However, you do have to unlock the bootloader first.
Follow Post #2 from this thread: http://forum.xda-developers.com/showthread.php?t=2382051
charesa39 said:
I would suggest that you put it into fastboot mode (aka get to the bootloader), and fastboot flash the factory image. However, you do have to unlock the bootloader first.
Follow Post #2 from this thread: http://forum.xda-developers.com/showthread.php?t=2382051
Click to expand...
Click to collapse
Thank you, it worked great. I didnt know you could flash the image using fast boot
saajan_b123 said:
Thank you, it worked great. I didnt know you could flash the image using fast boot
Click to expand...
Click to collapse
Awesome. Glad it worked out for you. As far as I know, fastboot is the only way to flash the factory image. Well, I suppose toolkits can flash it as well, but I, personally, am not a huge fan of them. Plus, it's the same process in fastboot as well, just automated. They're convenient for someone that already knows what they're doing, but for "nooks," they can often do more harm than good.
Sent from my Nexus 5 using xda app-developers app
hello guys,
I have the same problem with my nexus 7 2013 (wifi), and i am trying real hard to fix it, but i cannot.
When i try to unlock the boodloader in ADB, the screen freezes, and it will not respond anymore to commands. I have to reset the tablet manually, and boot into recovery mysefl, where the bootloader state is locked..
Running stock android, no root, bootloader locked, no usb debugging!
I think the problem is that the usb debuging is off, and i cannot write on the tablet in adb trough a usb connection.
Can someone help me?
Thank you in advance!
:sasquatch: said:
hello guys,
I have the same problem with my nexus 7 2013 (wifi), and i am trying real hard to fix it, but i cannot.
When i try to unlock the boodloader in ADB, the screen freezes, and it will not respond anymore to commands. I have to reset the tablet manually, and boot into recovery mysefl, where the bootloader state is locked..
Running stock android, no root, bootloader locked, no usb debugging!
I think the problem is that the usb debuging is off, and i cannot write on the tablet in adb trough a usb connection.
Can someone help me?
Thank you in advance!
Click to expand...
Click to collapse
You should be unlocking the bootloader with fastboot, not adb. Once unlocked, flash the factory image with fastboot.
I tried with fastboot, and it works perfect until i select (yes) option from the tablet. After selecting (yea) the tablet freezes and the bootloader remains locked! I have to hard reset the tablet to acces recovery mode again...
Any ideeas?
In fastboot mode, when i try fastboot oem unlock and select yes in tablet. tablet freezes and the bootloader remains locked!
Can someone help me out
It can be an hardware issue, someone say to massage the back of the tablet ( on the X) maybe it work, should be a flat off position.
Btw look at this thread where hundreds of peoples have the same issue... Nexus 7 stuck on Google screen

[Q] Help! - Rooted Zenfone 2 (ZE551ML) bricked after OTA accidently

followed a tutorial (Cnncted's youtube clip - How to root the ASUS ZenFone 2 ) to root
Accidentally (very stupid) pressed the update option when an OTA update showed up yesterday (Jul 8 2015), and after that the phone won't start properly - stopped at in search of incredible...
No luck with trying to boot into recovery mode (power + volume up). It just vibrates once and the screen is black. Trying to flash recovery image with ADB and flashtool etc, but the MTP usb connection failed. If I connect it to the PC using the USB cable and then press the power button to turn it on (stuck in that ..."incredible" screen), device manager shows the Z200AD name with a yellow exclamation mark beside, and Asus ZenUI software will automatically start. But it's not really recognized by the PC.
So...if you have any suggestions for me to try, please let me know and that would be greatly appreciated!
Harry
p.s. This is a US version, so the it's the WW sku?
Same problem here. I have a rooted 551ML and on July 6th I received an OTA update. I installed it and I'm stuck in boot loop. I have hundreds of family pictures in the internal memory.
The good news is that I have access to boot loader and recovery.
I could not find any custom recovery for Zenfone 2. They are not out yet, right? Is there any way to copy the internal memory of the phone (that doesnt load the OS) to the SD card? Or to paste a file img.boot taken from a downloaded official rom and copy it over the corrupted one on the phone's memory?
If you can access the bootloader, you can do this:
http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
Btw, there is a custom recovery out there (TWRP, check the Development section), but you will need an unlocked bootloader to use it in your state (I think).
US version is the WW SKU btw. Hope this helps.
joel.maxuel said:
If you can access the bootloader, you can do this:
http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
Btw, there is a custom recovery out there (TWRP, check the Development section), but you will need an unlocked bootloader to use it in your state (I think).
US version is the WW SKU btw. Hope this helps.
Click to expand...
Click to collapse
Joel, thanks a lot! I will give it a try.
fingers and toes crossed...
I faced this problem too. All I did was to flash the boot.img of my version using fastboot,
Then I flashed the firmware, without factory reset I started the phone.
I was continiously getting an error "com.android.process has stopped". Ignoring that, I just backed up my whole data. Did a factory reset. Updated
Boom!! Everything was normal... I hope this helps
Just a quick update - followed the method in the link that Joel referred to, and everything worked beautifully. I did get two error messages like “the contact stopped working..." “The process android.process.acore has stopped working.” I fixed this problem by clearing the data/cache from the "contact" app, and that did the trick without a factory reset etc.
I unrooted the device using SuperSU. The fastboot screen, however, still shows a random serial number 0123456789ABCDEF. Is there a way to revert it back to the real one? I do see the real one from settings - about - status.
xxmmx said:
Joel, thanks a lot! I will give it a try.
fingers and toes crossed...
Click to expand...
Click to collapse
xxmmx said:
Just a quick update - followed the method in the link that Joel referred to, and everything worked beautifully. I did get two error messages like “the contact stopped working..." “The process android.process.acore has stopped working.” I fixed this problem by clearing the data/cache from the "contact" app, and that did the trick without a factory reset etc.
I unrooted the device using SuperSU. The fastboot screen, however, still shows a random serial number 0123456789ABCDEF. Is there a way to revert it back to the real one? I do see the real one from settings - about - status.
Click to expand...
Click to collapse
Isn't everyone serial number the same? mine is.
This is something that I am not sure of. Yours has been rooted as well?
I would like to know what the fastboot screen looks like before rooting.
GGL-Daz said:
Isn't everyone serial number the same? mine is.
Click to expand...
Click to collapse
xxmmx said:
This is something that I am not sure of. Yours has been rooted as well?
I would like to know what the fastboot screen looks like before rooting.
Click to expand...
Click to collapse
Pretty sure rooting didn't affect my fastboot screen at all.
actually i rooted my zenfone 2 and there was an OTA and i tried to install it without un-rooting my phone. the phone would not turn on and it gets stuck in the boot animation.
the phone wasn't detected by the ADB in my pc so i thought of installing some custom recovery, thought that could help.
i tried installing TWRP but i did not unlock the bootloader and now i am not able to enter in recovery mode either, everytime i try to get in the recovery modethe phone restarts and goes to fastboot mode.
please help.
dip_anker said:
actually i rooted my zenfone 2 and there was an OTA and i tried to install it without un-rooting my phone. the phone would not turn on and it gets stuck in the boot animation.
the phone wasn't detected by the ADB in my pc so i thought of installing some custom recovery, thought that could help.
i tried installing TWRP but i did not unlock the bootloader and now i am not able to enter in recovery mode either, everytime i try to get in the recovery modethe phone restarts and goes to fastboot mode.
please help.
Click to expand...
Click to collapse
I was having a similar issue where adb wouldn't recognize my phone but fastboot was detecting it. What I ended up doing was grabbing the latest stock firmware zip from asus, transferring it to my external sd card via adapter and renamed it to MOFD_SDUPDATE.zip. Then go into fastboot (restart with volume up key) and proceed to recovery. It should automatically update your system from there. The only bummer is having to re-configure everything.
5ifty1 said:
I was having a similar issue where adb wouldn't recognize my phone but fastboot was detecting it. What I ended up doing was grabbing the latest stock firmware zip from asus, transferring it to my external sd card via adapter and renamed it to MOFD_SDUPDATE.zip. Then go into fastboot (restart with volume up key) and proceed to recovery. It should automatically update your system from there. The only bummer is having to re-configure everything.
Click to expand...
Click to collapse
i tried it with prerooted as well as the stock rom, it did not work for me. isn't there any way to flash CM12.1 using the fastboot ?

bricked phone

So,in my stupidity to install an ota update after rooting my phone,I managed to get it stuck in a bootloop. Now I followed some guides on the internet,downloaded the pre-rooted images,but fastboot doesnt want to flash system.img. I tried to download the img from different sources,none worked. The error just says cannot load system.img.I installed fastboot with the 15 second installer,I havent done any other modifications besides rooting and I cant even access recovery mode,it just shows me error in red text.Is there anything I can do myself or do I need to send my phone in service? Thanks! btw the model is ZE551ML
thehappyface said:
So,in my stupidity to install an ota update after rooting my phone,I managed to get it stuck in a bootloop. Now I followed some guides on the internet,downloaded the pre-rooted images,but fastboot doesnt want to flash system.img. I tried to download the img from different sources,none worked. The error just says cannot load system.img.I installed fastboot with the 15 second installer,I havent done any other modifications besides rooting and I cant even access recovery mode,it just shows me error in red text.Is there anything I can do myself or do I need to send my phone in service? Thanks! btw the model is ZE551ML
Click to expand...
Click to collapse
Hello guys what is the error in red text please??
You can go to your recovery or not?
Thank
quadeur06 said:
Hello guys what is the error in red text please??
You can go to your recovery or not?
Thank
Click to expand...
Click to collapse
It just shows me a dead android with the words Error! written in red text
thehappyface said:
It just shows me a dead android with the words Error! written in red text
Click to expand...
Click to collapse
For pass this error ..It's just a security ..Tap in the volume + and in the same time to the power button very fast And it's work !!
thehappyface said:
So,in my stupidity to install an ota update after rooting my phone,I managed to get it stuck in a bootloop. Now I followed some guides on the internet,downloaded the pre-rooted images,but fastboot doesnt want to flash system.img. I tried to download the img from different sources,none worked. The error just says cannot load system.img.I installed fastboot with the 15 second installer,I havent done any other modifications besides rooting and I cant even access recovery mode,it just shows me error in red text.Is there anything I can do myself or do I need to send my phone in service? Thanks! btw the model is ZE551ML
Click to expand...
Click to collapse
Hello there,
Few days ago, I had the same problem. But luckly I found a way to fix it. I was so desperate.
1) Download "CWM Zenfone_2_Intel"
https://www.mediafire.com/folder/w70...5840/Zenfone_2
Then unzip
2) Go in fastboot mode in your Zenfone 2, and connect it to your PC
3) In the downloaded folder, run "cai_dat_CWM.bat"
4) Type ACCEPT
Then Enter
5) Then if the script is blue, that's perfect. Type T4, Enter, and normally your Zenfone will reboot in CWM Recovery Mode.
6) If that worked, download the ROM stock on the Asus Website, copy it on the SD Card, then flash it from the CWM Recovery Mode.
This method fix my bootloop, but a brick I don't know...
If it didn't work, try to install "15 seconds adb installer"

i need help

i hope someone could help me i rooted my device and had issue with battery i got that fixed but now for some reason my tablet is stuck on bootloader screen and it seems theres no back up or im not rooted it just keeps saying booting failed is there any way to flash it back to stock or get my tablet back to its working properly
Have you tried the Nexus Root Toolkit by Wugfresh?
Nexus Root Toolkit has a Soft-Bricked/Bootloop mode this may be what you are looking for.
dlkile said:
Nexus Root Toolkit has a Soft-Bricked/Bootloop mode this may be what you are looking for.
Click to expand...
Click to collapse
i did its stuck on google screen with start button showing it seems theres not backup on it or recovery all i can do is get google screen with either start, recovery mode, restart bootloader, and power off showing i cant seem to get it to flash anything on wug . could it be i have windows 10 on my computer now
I have only had my Nexus for a couple weeks now so more experienced users please feel free to jump in. Sometimes is best to just flash a fresh factory image and start over.
Prerequisites - Have ADB and Fastboot installed and configured
- extract the factory image that's linked
- Reboot into your bootloader and unlock it if you haven't already done so
- while in booltloader flash the factory image using fastboot by running the flash-all script
- tablet will reboot and you should be back to stock
Factory image- https://dl.dropboxusercontent.com/u/51961442/razor-mmb29k-factory-a39e7047.tgz
MD5 Checksum - https://dl.dropboxusercontent.com/u/51961442/Razor-MD5 Checksum

Question attempted to sideload android 13. failed..bricked?

attempted to sideload android 13. i downloaded the ota files for my phone. downloaded platform tools. did the adb reboot recovery. apply update from adb. it made it to 53% then failed. said failed to read command no error. i tried to apply update from adb again right away. it made it to 1% then started saying failed to read file something something over and over and over on my phone screen. i tried to reboot it. probably a bad idea i know. now its stuck on the G with a bar under it that just keeps scrolling but it cant seem to boot up. please help!
seems like a soft brick, use the Android Flash Tool to reflash the os
hxudsh said:
seems like a soft brick, use the Android Flash Tool to reflash the os
Click to expand...
Click to collapse
Not sure if that will work. i cant get into my phone to get to developer options so i cannot unlock the bootloader.
ytsurX said:
attempted to sideload android 13. i downloaded the ota files for my phone. downloaded platform tools. did the adb reboot recovery. apply update from adb. it made it to 53% then failed. said failed to read command no error. i tried to apply update from adb again right away. it made it to 1% then started saying failed to read file something something over and over and over on my phone screen. i tried to reboot it. probably a bad idea i know. now its stuck on the G with a bar under it that just keeps scrolling but it cant seem to boot up. please help!
Click to expand...
Click to collapse
Try using different cables and ports when sideloading. Also use A to C rather than C to C.
ytsurX said:
Not sure if that will work. i cant get into my phone to get to developer options so i cannot unlock the bootloader.
Click to expand...
Click to collapse
it should work, as it flashes the original software it shouldn't matter if you have the bootloader unlocked or not
hxudsh said:
it should work, as it flashes the original software it shouldn't matter if you have the bootloader unlocked or not
Click to expand...
Click to collapse
You don't need the bootloader to actually be unlocked to use Android Flash Tool, but you do need to have OEM Unlocking enabled in Developer Options. If you do, the Flash Tool will unlock the bootloader itself before flashing the images.
ytsurX said:
attempted to sideload android 13. i downloaded the ota files for my phone. downloaded platform tools. did the adb reboot recovery. apply update from adb. it made it to 53% then failed. said failed to read command no error. i tried to apply update from adb again right away. it made it to 1% then started saying failed to read file something something over and over and over on my phone screen. i tried to reboot it. probably a bad idea i know. now its stuck on the G with a bar under it that just keeps scrolling but it cant seem to boot up. please help!
Click to expand...
Click to collapse
Try USB 2.0. I have 9 different random percentage stops over two different PCs and my phone was soft bricked. I grabbed an adapter that downed my USB 3 to 2 and ran again. First shot on a USB 2.0 the OTA went through and brought my phone back to how it was.

Categories

Resources