Related
So today i discovered that my month old Nexus 4 did not want to boot again.
Last night the phone was off, so i assumed the battery was dead, after putting it in the charger and asking it to boot i went to sleep.
when i woke up i was still looking at the multicoloured pulsating X.
since then it keeps getting stuck at the X screen, powering it down will make the phone power up again for no reason.
The phone was running a OTA version of 4.2.2
When powering it on with ON & vol - I get the boot menu, though navigating to the recovery mode resulted in a "No command." line with a red triangle on a android.
Currently i have no experience with either rooting/flashing, neither am i aware if this is the only option to fix this semi bricked phone.
How would i best go about fixing this issue?
Thanks.
MissStabby said:
So today i discovered that my month old Nexus 4 did not want to boot again.
Last night the phone was off, so i assumed the battery was dead, after putting it in the charger and asking it to boot i went to sleep.
when i woke up i was still looking at the multicoloured pulsating X.
since then it keeps getting stuck at the X screen, powering it down will make the phone power up again for no reason.
The phone was running a OTA version of 4.2.2
When powering it on with ON & vol - I get the boot menu, though navigating to the recovery mode resulted in a "No command." line with a red triangle on a android.
Currently i have no experience with either rooting/flashing, neither am i aware if this is the only option to fix this semi bricked phone.
How would i best go about fixing this issue?
Thanks.
Click to expand...
Click to collapse
Try to get in bootloader mode then go to recovery and wipe cache /do a data factory reset and reboot.
Okay. Get back into recovery by holding Vol-/pow.
Then scroll to recovery.
When in recovery reveal the menu by pressing vol+/pow
Once there wipe data and reset cache.
Sent from my Nexus 4 using xda premium
gee2012 said:
Try to get in bootloader mode then go to recovery
Click to expand...
Click to collapse
When i try to get into recovery mode i am greeted with this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and a "No command." message.
There is no interface there to work with.
Try vol+/pow to reveal recovery menu once on that screen
Sent from my Nexus 4 using xda premium
elliot.newnham said:
Try vol+/pow
Click to expand...
Click to collapse
Tried that at the recovery screen but nothing responded.
also tried vol+- and +- and vol- no response from any combinations.
ah i got it to appear, it turns out that pressing the power button first instead of the volume button was an issue...
also if i do the wipedata+reset will i lose all 16 gb's of onboard storage?
and would there be a way to write/backup that data before doing so?
Here is googles support page for reset: http://support.google.com/nexus/bin/answer.py?hl=en&answer=2936226
follow these steps:
If your phone is on, power it off.
Press and hold Volume Down, and then press Power until the device turns on (while still pressing Power). You will see the word Start with an arrow drawn around it.
Press Volume Down twice to designate Recovery mode.
Press Power to restart into Recovery mode. You will see an image of an Android robot with a red exclamation mark.
While holding down Power, press Volume Up.
Use the volume keys to scroll to "wipe data/factory reset" and press Power to select it.
Scroll down to "Yes - erase all user data" and press Power to select it.
Note: If at any point during the above steps your phone becomes unresponsive, you can restart it by holding down the power button for several seconds.
hepatiit i got that to work, though what i am wondering is, will this erase all 16GB's of onboard data?
MissStabby said:
hepatiit i got that to work, though what i am wondering is, will this erase all 16GB's of onboard data?
Click to expand...
Click to collapse
Yes.
Would there be a way to backup all data over USB, from the recovery menu?
I have my photos and agenda automatically backed up, but im not sure about my contacts or installed apps.
MissStabby said:
Would there be a way to backup all data over USB, from the recovery menu?
I have my photos and agenda automatically backed up, but im not sure about my contacts or installed apps.
Click to expand...
Click to collapse
Contacts are backed up to the google servers. (can check them through GMail). Apps are also backed up to play.google.com... Note, sometimes the data isn't backed up though. Just what you've installed.
I believe a factory reset will NOT erase SDCard though. I could be wrong.
I'd say your out of luck on getting the data off. You can through recovery and ADB I think. I tried searching for the commands but I couldn't find them.
elliot.newnham said:
I believe a factory reset will NOT erase SDCard though. I could be wrong.
I'd say your out of luck on getting the data off. You can through recovery and ADB I think. I tried searching for the commands but I couldn't find them.
Click to expand...
Click to collapse
ahw shucks, the Nexus doesnt have any extended storage, it just has 16GB onboard storage, though im not sure if that is somehow a seperate entity or joined in, i looked into ADB but it requires you to have usb debugging set in advance from android.
aaaaaand now i get to also replay all the games since those savegames are gone too.... good times...
And then my phone got bricked....
after it completed the wipe i inserted the SIM card (it was in another phone)
after that the phone turned off, but now it wont respond to the power button....
now what.....
After applying some USB (charger) power and holding the on switch for a long time it finally woke up.
Now i have a blanco phone again.
Thanks for the support anyways
I had the same exact issue with my Nexus 4. When I flashed the stock image it got stuck on the X. I flashed a custom recovery and erased chase and data and it worked just fine.
I'm not sure why this is "necessary" step now when I didn't have to do do this with my Gnex but oh well.
Sent from my Nexus 4 using xda app-developers app
Hi I've been an avid flasher for years without problems but today I have a huge problem!!
I flashed xenon s latest and flashed gapps via Cwm but it wouldn't boot so when I rebooted it just goes into a bootloop into recovery but it only loads the recovery slightly before rebooting again.
I've tried entering the bootloader by powering off etc and holding volume +&- and power but still can't enter
I've also tried pulling the battery and trying but still no luck
Please can anyone help
Sent from my GT-I9505 using Tapatalk
Solved
Sent from my GT-I9505 using Tapatalk
Can you share how you solved? I've been seeing this problem reported all over the forum and no one has yet posted any solution aside from replacing the main board or RMA.
I will post the solution tonight with step by step and images but out atm but I will post
Sent from my GT-I9505 using Tapatalk
1eyedmonster said:
I will post the solution tonight with step by step and images but out atm but I will post
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
Here is my solution step by step.
1 install 'wugs root toolkit & skipsoft android toolkit
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2 install USB drivers from skipsoft as its easier - select option 1 after entering the main menu
3 you need to select the build of your custom ROM in wugsfresh toolkit 4.1/4.2/4.4 etc (this is important as if you choose the wrong build it won't work straight away and you will have to try each build individually).
4.in wugsfresh select "soft bricked" and select "launch advanced Utilities"
5.select (boot temporary _ custom Recovery) and execute
now connect your n7 with the usb
6 you will see prompts on the screen saying Rebooting into bootloader and at this point press the volume down button constantly if you get a prompt "device not found......" Just press OK and follow the procedure again until your bootloader starts( of it doesn't work try a different build
7 once you bootloader starts unplug your USB instantly and then scroll down using the volume keys and select "reboot bootloader"
8 close wugsfresh "Ctrl+alt &del and end process" and restart your computer
9 after pc reboot enter the skipsoft toolkit and you can connect your n7 (still in bootloader mode) via usb
10 select your build and download the recoveries when prompted
11 when in the main menu select option 6 "flash custom recovery" and select twrp only
12 flash away (if it doesn't detect your n7 (reboot bootloader on your n7) and try again
13 once you've flashed successfully (on your n7 scroll down and select reboot into recovery and twrp should load.
14 from here you can install your desired ROM with a otg cable or from a ROM on you devices storage but if you don't have a otg cable or a rom on your storage go to the next step
15 download your desired ROM and place it on your PCs hard drive. Open wugsfresh toolkit and select launch utilities again
16 select "flash zip -file is on the computer"and press OK when prompted and select your downloaded ROM /enable wipe selected partitions and select data cache and dalvic and then confirm operation
17 you will see a prompt stating "sending ROM.......to device" this will take sometime be patient once it's completed it will reboot your device back into twrp recovery and the file will be on your devices storage in a folder called "ready to flash" and the rest is up to you.
18 once your booted into your device os you can reflash your desired recovery with the toolkit of your choice
Hope this helps
Wow, did you just trial and error your way through that?
Interesting that you needed to use both toolkits, but whatever works...
Hopefully this will help some folks that were otherwise SOL with a bricked tablet. :good:
1eyedmonster said:
Here is my solution step by step.
1 install 'wugs root toolkit & skipsoft android toolkit
2 install USB drivers from skipsoft as its easier - select option 1 after entering the main menu
3 you need to select the build of your custom ROM in wugsfresh toolkit 4.1/4.2/4.4 etc (this is important as if you choose the wrong build it won't work straight away and you will have to try each build individually).
4.in wugsfresh select "soft bricked" and select "launch advanced Utilities"
5.select (boot temporary _ custom Recovery) and execute
now connect your n7 with the usb
6 you will see prompts on the screen saying Rebooting into bootloader and at this point press the volume down button constantly if you get a prompt "device not found......" Just press OK and follow the procedure again until your bootloader starts( of it doesn't work try a different build
7 once you bootloader starts unplug your USB instantly and then scroll down using the volume keys and select "reboot bootloader"
8 close wugsfresh "Ctrl+alt &del and end process" and restart your computer
9 after pc reboot enter the skipsoft toolkit and you can connect your n7 (still in bootloader mode) via usb
10 select your build and download the recoveries when prompted
11 when in the main menu select option 6 "flash custom recovery" and select twrp only
12 flash away (if it doesn't detect your n7 (reboot bootloader on your n7) and try again
13 once you've flashed successfully (on your n7 scroll down and select reboot into recovery and twrp should load.
14 from here you can install your desired ROM with a otg cable or from a ROM on you devices storage but if you don't have a otg cable or a rom on your storage go to the next step
15 download your desired ROM and place it on your PCs hard drive. Open wugsfresh toolkit and select launch utilities again
16 select "flash zip -file is on the computer"and press OK when prompted and select your downloaded ROM /enable wipe selected partitions and select data cache and dalvic and then confirm operation
17 you will see a prompt stating "sending ROM.......to device" this will take sometime be patient once it's completed it will reboot your device back into twrp recovery and the file will be on your devices storage in a folder called "ready to flash" and the rest is up to you.
18 once your booted into your device os you can reflash your desired recovery with the toolkit of your choice
Hope this helps
Click to expand...
Click to collapse
Will give it a try later today & post results...
Fingers crossed!
Thanks,
Shabby.
PrizmaticSmoke said:
Wow, did you just trial and error your way through that?
Interesting that you needed to use both toolkits, but whatever works...
Hopefully this will help some folks that were otherwise SOL with a bricked tablet. :good:
Click to expand...
Click to collapse
Yes had to use both toolkits as you can't flash recovery in bootloader mode in wugfresh but you can in the other
Sent from my GT-I9505 using Tapatalk
Recovery Bootloop Nexus 7
1eyedmonster said:
Yes had to use both toolkits as you can't flash recovery in bootloader mode in wugfresh but you can in the other
Sent from my GT-I9505 using Tapatalk
Click to expand...
Click to collapse
Wow, I was hoping someone would find a solution to this unstoppable boot loop. Awesome work 1eyedmonster!
I gave this a try since I like many others flashed XenonHD with CWM as my recovery and fell into the boot loop too, but how were you able to get step 6? I been trying to get the tablet into the bootloader when the message appears in wugfresh while pressing volume down, but then fails to reboot into it and the status will then show checking fastboot and fails. So I try it again but still having trouble and it just keeps going from the google logo then to CWM and then back to the google logo. Checked the drivers and it shows as ADB in the device manager when CWM pops up so drivers seem good.
Since my build was 4.4.2 I tried custom rom KK and standard 4.4.2 when selecting the build, but not sure what I might be doing wrong.
Any help will be greatly appreciated.
xdarkstar13x said:
Wow, I was hoping someone would find a solution to this unstoppable boot loop. Awesome work 1eyedmonster!
I gave this a try since I like many others flashed XenonHD with CWM as my recovery and fell into the boot loop too, but how were you able to get step 6? I been trying to get the tablet into the bootloader when the message appears in wugfresh while pressing volume down, but then fails to reboot into it and the status will then show checking fastboot and fails. So I try it again but still having trouble and it just keeps going from the google logo then to CWM and then back to the google logo. Checked the drivers and it shows as ADB in the device manager when CWM pops up so drivers seem good.
Since my build was 4.4.2 I tried custom rom KK and standard 4.4.2 when selecting the build, but not sure what I might be doing wrong.
Any help will be greatly appreciated.
Click to expand...
Click to collapse
firstly if your in the bootloop due to xennon then you need to take the back off the nexus7 and unplug the battery. once its been off for 10 seconds plug the battery back in (not the usb) below is a screenshot of the wugsfresh toolkit make sure you highlight the same boxes as me
if you installed xennon then you need to install 4.4.2 KOT49H.
1eyedmonster said:
firstly if your in the bootloop due to xennon then you need to take the back off the nexus7 and unplug the battery. once its been off for 10 seconds plug the battery back in (not the usb) below is a screenshot of the wugsfresh toolkit make sure you highlight the same boxes as me
if you installed xennon then you need to install 4.4.2 KOT49H.
Click to expand...
Click to collapse
once you clicked the 'Boot tempory custom recovery' button plug your n7 via the usb and press the volume down button erratically (do not hold down) before powering the n7 on
1eyedmonster said:
firstly if your in the bootloop due to xennon then you need to take the back off the nexus7 and unplug the battery. once its been off for 10 seconds plug the battery back in (not the usb) below is a screenshot of the wugsfresh toolkit make sure you highlight the same boxes as me
if you installed xennon then you need to install 4.4.2 KOT49H.
Click to expand...
Click to collapse
1eyedmonster said:
once you clicked the 'Boot tempory custom recovery' button plug your n7 via the usb and press the volume down button erratically (do not hold down) before powering the n7 on
Click to expand...
Click to collapse
once bootloader boots up you must unplug the usb immediately
another thing I forgot to add is once in wugfresh you need to go to options /custom recovery/utilize open recovery by team wi......
Sent from my Satellite Pro A300 using Tapatalk
1eyedmonster said:
firstly if your in the bootloop due to xennon then you need to take the back off the nexus7 and unplug the battery. once its been off for 10 seconds plug the battery back in (not the usb) below is a screenshot of the wugsfresh toolkit make sure you highlight the same boxes as me
if you installed xennon then you need to install 4.4.2 KOT49H.
Click to expand...
Click to collapse
Same prob as xdarkstar...
I know this might sound a bit stupid, but what is the best way to get the back off? [I'm asking this because all I'm doing at the moment is chewing in to the sides of the device with no results...]
TIA,
Shabby.
SHABBYLEA said:
Same prob as xdarkstar...
I know this might sound a bit stupid, but what is the best way to get the back off? [I'm asking this because all I'm doing at the moment is chewing in to the sides of the device with no results...]
TIA,
Shabby.
Click to expand...
Click to collapse
Hi, Shabby...
I've found the easiest way of removing the back, is to begin at the top (opposite end to the USB port)... slide a fingernail under the plastic back and gently prise it away. Then slowly work your way around both left and right edges with your fingernails. You shouldn't need to use any real force; once you've got the process started, the back should pretty much just 'pop' off.
To put it back on... reverse the process... begin at the bottom (USB end)... and apply gentle pressure, equally on both right and left hand sides... slowly working your way up to the top. You should 'feel' it begin to snap back into place.
-----------------------------------------------
Incidentally, I really hope this method discovered by @1eyedmonster works for you... and anybody else afflicted by the decidedly toxic combination of Xenon and CWM.
Rgrds,
Ged.
GedBlake said:
Hi, Shabby...
I've found the easiest way of removing the back, is to begin at the top (opposite end to the USB port)... slide a fingernail under the plastic back and gently prise it away. Then slowly work your way around both left and right edges with your fingernails. You shouldn't need to use any real force; once you've got the process started, the back should pretty much just 'pop' off.
To put it back on... reverse the process... begin at the bottom (USB end)... and apply gentle pressure, equally on both right and left hand sides... slowly working your way up to the top. You should 'feel' it begin to snap back into place.
-----------------------------------------------
Incidentally, I really hope this method discovered by @1eyedmonster works for you... and anybody else afflicted by the decidedly toxic combination of Xenon and CWM.
Rgrds,
Ged.
Click to expand...
Click to collapse
For future reference don't attempt to install xennon with philz recovery either as this causes the bootloop also
Sent from my GT-I9505 using Tapatalk
This isn't working for me. Maybe Im doing something wrong but I cant get it to work.
Found a fix to restore to stock!
timmytim said:
This isn't working for me. Maybe Im doing something wrong but I cant get it to work.
Click to expand...
Click to collapse
Warning! This method will restore your tablet to factory defaults. I did not try to flash a custom recovery while in Fastboot Mode though Im sure that will work too if you just want to write a Recovery (TWRP... hint hint) and reflash a different ROM.
I'm convinced. This tablet must truly be unbrickable!!
I have found another fix and it was as easy as pie! Here's what I did... results may vary. Please post here if you had success or not. Also, you will need working adb for this to work as well as the ADB drivers installed and working.
For starters, this is the Epic Fail after flashing a ROM with CWM or Philz Recovery
What I found is that while on this screen you can still run adb commands. Eureka I thought! Here's the simplest way to recover your tablet from this vicious cycle. Again, you will need either need the Android SDK installed on your PC or you will need the adb executable with libs at minimum....
1. Download the Nakasi Nexus Factory Image of your choice from HERE
2. Plug your tablet into your computer while it's bootlooping. You will have to have the ADB drivers installed for this to work.
3. Open a command prompt on your PC and type in adb reboot bootloader and press Enter on your keyboard.
4. If you happened to catch it at the right moment, which is between the Google splash screen and the f*cked Recovery screen seen above, congrats! If not, keep pressing the Up Arrow and Enter keys simultaneously on your keyboard starting at the Google splash screen until it reboots into Fastboot mode
5. Extract the Nakasi factory image that you downloaded and run flash-all.bat and wait for the script to finish. It will reboot your tablet into Fastboot Mode a few times while it executes. When done, it will boot the tablet and it will be factory restored
Win!
timmytim said:
Warning! This method will restore your tablet to factory defaults. I did not try to flash a custom recovery while in Fastboot Mode though Im sure that will work too if you just want to write a Recovery (TWRP... hint hint) and reflash a different ROM.
I'm convinced. This tablet must truly be unbrickable!!
I have found another fix and it was as easy as pie! Here's what I did... results may vary. Please post here if you had success or not. Also, you will need working adb for this to work as well as the ADB drivers installed and working.
For starters, this is the Epic Fail after flashing a ROM with CWM or Philz Recovery
What I found is that while on this screen you can still run adb commands. Eureka I thought! Here's the simplest way to recover your tablet from this vicious cycle. Again, you will need either need the Android SDK installed on your PC or you will need the adb executable with libs at minimum....
1. Download the Nakasi Nexus Factory Image of your choice from HERE
2. Plug your tablet into your computer while it's bootlooping. You will have to have the ADB drivers installed for this to work.
3. Open a command prompt on your PC and type in adb reboot bootloader and press Enter on your keyboard.
4. If you happened to catch it at the right moment, which is between the Google splash screen and the f*cked Recovery screen seen above, congrats! If not, keep pressing the Up Arrow and Enter keys simultaneously on your keyboard starting at the Google splash screen until it reboots into Fastboot mode
5. Extract the Nakasi factory image that you downloaded and run flash-all.bat and wait for the script to finish. It will reboot your tablet into Fastboot Mode a few times while it executes. When done, it will boot the tablet and it will be factory restored
Win!
Click to expand...
Click to collapse
Using this method, do you have to disconnect the battery?
Thanks,
Shabby.
No
Sent from my GT-I9505 using Tapatalk
How to rollback to KitKat from LollipopFIRST OF ALL:
Make sure that ADB Asus drivers and Intel USB Drivers are installed on your computer
Download this archive with all required files
IMPORTANT!
IF YOU HAVE UNLOCKED BOOTLOADER AND PERMANENT TWRP - RECOVER STOCK ESP AND RECOVERY
I'm not responsible for all problems, if they will happen with your tablet
Instruction:
Unpack WW_ME176C_V12.10.1.17-userdebug-201505051557-rawdata.zip from archive
Connect via USB-cable, press and hold Volume Up + Volume Down + Power Key for 3-5 seconds, you'll get smth like "Fastboot starting..."
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If Android robot doesn't appears - launch debrick-flashall-FW-no_wipe.cmd
If Android robot appears - launch debrick-flashall-no_wipe.cmd
Check firmware version in setting, it must be like here
Unpack FWI_to_UEFI_ME176C.7z
Launch flash_ME176C_IFWI.cmd
After completing plug off USB-cable and turn off tablet
Press and hold Volume Up + Volume Down + Power Key for 3-5 seconds, you'll get ASUS logo
Plug in USB-cable, copy debrick-flashall-FW-no_wipe.cmd from FWI_to_UEFI_ME176C.7z
to WW-ME176C-3.2.23.201-release-user-20150115-signed.zip. Launch .cmd
Done...
Credits to AKASer and Skyrimus from 4pda
IF YOU HAVE GOOGLE SERVICES CRASHES - DELETE 9.9.56 VERSION AND INSTALL 9.9.55
I want to help here. I made the process a little bit diferent. To connecting the tablet to the pc i enter fastbot mode. Press power+Vol down until the robot appear.
Then launch 4- not 3-.
In the same way launched every step that the tablet needed to be connected to pc, like 7-.
In step 9- pressed Vol up+ power to enter droidboot then do 10, were it sais launch cmd you have to launch debrick-flashall-FW-no_wipe.cmd in the new location.
The tablet works excelent, very happy here, thanks!!
---------- Post added at 08:09 AM ---------- Previous post was at 08:00 AM ----------
Ok, it was not easy to root .201, stuck in demo mode like 3 times. This is the correct way:
-Download this version of root zenfone:https://cloudup.com/files/ivrnLUAwMDS/download
-Download supersu from the playstore and install it.
-Install and open root zenfone, let the app run and don't put OK when it enter demo mode. Let it run for 15 seconds and just restart the tablet without pressing anything.
-If everything is ok you will be rooted.
-In case things go wrong and you enter demo mode, you have to press back button for 10 seconds, then it will ask you for a code, put 741603 and confirm. It will factory reset your tablet and demo will be gone. In case it not enter factory reset you will need to do it manually, after puting de code.
For me google play service bug dissapear when disabled google as device administrator of the device.
This tablet work 10 times better with Kitkat, it doesn't restart, it is stable, a lot better ram manager. The only problem i figure out ia battery stats, it's very buggie. I can use the tablet 1 hour with 1% of the battery, it happen to me with this tablet in all version since i buy it, maybe my battery is wrong...
Please. I lost the stock ESP and recovery. can someone upload the two files here? I have me176c ww version. I do not want to suffer more random reboots.
HELP!
I did all that and it stuck in the bootloop. Can't get in to fastboot or boot menu either.
OK... The only thing seems to be working is droidboot. When I try to go in to recovery then it will show belly up droid.
-------------------------------------
Edit: Alrighty mighty... I did it.
I consider my self and Android idiot cuz I've managed to f*ed up 2 devices beyond repair and even I am able to do this.
My K013 was latest Lollipop update .36, rooted, exposed, striped off system apps to bare minimum.
Here's what I did, step by step.
0. Pre-flight check.
Install ASUS_Android_USB_drivers_for_Windows downloaded from here> https://www.asus.com/support/Download/39/1/0/6/32/
Once you got the zip, unzip it then go to extracted folder > Windows_XP_VISTA_7_8_8.1 > Android, right click on android_winusb and click Install.
Install Intel USB Driver for Android downloaded from here> https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
This one is install shell, easy.
1. Turn off the tablet.
2. Hold volume down and power until you see Asus logo, now you can release power button but sill hold the volume down button. This will get you in to fastboot.
3. Plug in the USB cable.
4. Unpack WW_ME176C_V12.10.1.17-userdebug-201505051557-rawdata.zip then do #4 in tutorial.
5. When finished, unplug the USB and let it boot. Go and check as step 5.
6. Turn on developer mode by go to Settings > About > Software Information and rapidly tap "Build number" until you see the message "You are now a developer!".
7. Go to Developer options and turn on USB debugging. Then plug in the USB cable.
8. Do step 6 and 7.
9. When finished, unplug the USB cable and turn off the tablet.
From here on are what I find tricky-----------------------------------
10. Unpack WW-ME176C-3.2.23.201-release-user-20150115-signed then copy debrick-flashall-FW-no_wipe.cmd from from FWI_to_UEFI_ME176C folder and put it in the extracted folder.
11. Hold volume up and power buttons until you see Asus logo then release both buttons. It will enter droidboot like in this picture.
12. Plug in USB cable, run debrick-flashall-FW-no_wipe.cmd from WW-ME176C-3.2.23.201-release-user-20150115-signed folder.
13. When it reach this part
Do not close this window yet. You have to go in to droidboot again (otherwise it will go in to bootloop just as mine did).
What I did was unplug it, turn it off and repeat my step 11. Then plug in the USB and it will resume installing new.... old.... I mean 4.4.2. This will take some time, just don't let you PC go in to sleep or accidentally disconnect the USB.
Once it finish, unplug the USB cable and let it boot up. Now, go enjoy your K013 running 4.4.2.
Thanks
thegreatn_ said:
How to rollback to KitKat from LollipopFIRST OF ALL:
Make sure that ADB Asus drivers and Intel USB Drivers are installed on your computer
Download this archive with all required files
IMPORTANT!
IF YOU HAVE UNLOCKED BOOTLOADER AND PERMANENT TWRP - RECOVER STOCK ESP AND RECOVERY
I'm not responsible for all problems, if they will happen with your tablet
Instruction:
Unpack WW_ME176C_V12.10.1.17-userdebug-201505051557-rawdata.zip from archive
Connect via USB-cable, press and hold Volume Up + Volume Down + Power Key for 3-5 seconds, you'll get smth like "Fastboot starting..."
If Android robot doesn't appears - launch debrick-flashall-FW-no_wipe.cmd
If Android robot appears - launch debrick-flashall-no_wipe.cmd
Check firmware version in setting, it must be like here
Unpack FWI_to_UEFI_ME176C.7z
Launch flash_ME176C_IFWI.cmd
After completing plug off USB-cable and turn off tablet
Press and hold Volume Up + Volume Down + Power Key for 3-5 seconds, you'll get ASUS logo
Plug in USB-cable, copy debrick-flashall-FW-no_wipe.cmd from FWI_to_UEFI_ME176C.7z
to WW-ME176C-3.2.23.201-release-user-20150115-signed.zip. Launch .cmd
Done...
Credits to AKASer and Skyrimus from 4pda
IF YOU HAVE GOOGLE SERVICES CRASHES - DELETE 9.9.56 VERSION AND INSTALL 9.9.55
Click to expand...
Click to collapse
Thanks dude, this helped a lot! Now I don't have to use sluggish Lollipop
Are really necesary the stock esp and recovery? I missed that.
Ok. I take the esp.img and recovery.img from WW_ME176C_V12.10.1.17-userdebug-201505051557-rawdata.zip and flash this like in the bootloader unlock tutorial.
---------- Post added at 04:32 PM ---------- Previous post was at 04:28 PM ----------
Beaver_XT said:
HELP!
I did all that and it stuck in the bootloop. Can't get in to fastboot or boot menu either.
OK... The only thing seems to be working is droidboot. When I try to go in to recovery then it will show belly up droid.
-------------------------------------
Edit: Alrighty mighty... I did it.
I consider my self and Android idiot cuz I've managed to f*ed up 2 devices beyond repair and even I am able to do this.
My K013 was latest Lollipop update .36, rooted, exposed, striped off system apps to bare minimum.
Here's what I did, step by step.
0. Pre-flight check.
Install ASUS_Android_USB_drivers_for_Windows downloaded from here> https://www.asus.com/support/Download/39/1/0/6/32/
Once you got the zip, unzip it then go to extracted folder > Windows_XP_VISTA_7_8_8.1 > Android, right click on android_winusb and click Install.
Install Intel USB Driver for Android downloaded from here> https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
This one is install shell, easy.
1. Turn off the tablet.
2. Hold volume down and power until you see Asus logo, now you can release power button but sill hold the volume down button. This will get you in to fastboot.
3. Plug in the USB cable.
4. Unpack WW_ME176C_V12.10.1.17-userdebug-201505051557-rawdata.zip then do #4 in tutorial.
5. When finished, unplug the USB and let it boot. Go and check as step 5.
6. Turn on developer mode by go to Settings > About > Software Information and rapidly tap "Build number" until you see the message "You are now a developer!".
7. Go to Developer options and turn on USB debugging. Then plug in the USB cable.
8. Do step 6 and 7.
9. When finished, unplug the USB cable and turn off the tablet.
From here on are what I find tricky-----------------------------------
10. Unpack WW-ME176C-3.2.23.201-release-user-20150115-signed then copy debrick-flashall-FW-no_wipe.cmd from from FWI_to_UEFI_ME176C folder and put it in the extracted folder.
11. Hold power up and power buttons until you see Asus logo then release both buttons. It will enter droidboot like in this picture.
12. Plug in USB cable, run debrick-flashall-FW-no_wipe.cmd from WW-ME176C-3.2.23.201-release-user-20150115-signed folder.
13. When it reach this part
Do not close this window yet. You have to go in to droidboot again (otherwise it will go in to bootloop just as mine did).
What I did was unplug it, turn it off and repeat my step 11. Then plug in the USB and it will resume installing new.... old.... I mean 4.4.2. This will take some time, just don't let you PC go in to sleep or accidentally disconnect the USB.
Once it finish, unplug the USB cable and let it boot up. Now, go enjoy your K013 running 4.4.2.
Click to expand...
Click to collapse
This works for me. Thanks!!!
*in step 11. is Hold volume up...
Oops. Thanks for correction.
at step 7 (flash_ME176C_IFWI.cmd) i can't go further, error 123 when trying to start demon, but i have usb debogging activated, what am i missing (i am on windows 10 anniversary update , i have disactivated drivers signature verification but i can't download intel drivers, the url can't seem to allow me the download).
I had this error too.... You must copy the extracted folders on a other place! On the Desktop works for me... I think theres read/write restrictions from the system....
I flashed succesfully with windows 10....
idoetzchen said:
I had this error too.... You must copy the extracted folders on a other place! On the Desktop works for me... I think theres read/write restrictions from the system....
I flashed succesfully with windows 10....
Click to expand...
Click to collapse
thought so but wasn't sure, i tried from the download folder in a folder with russian caracters on a french windows 10 x64, so i was thinking it was a name issue, will retry from another folder on root and use a simpler folder name.
moving and renaming the folder did the trick, my me176cx just did it's first 4.4.2 boot in a while.
NahuelMS said:
I want to help here. I made the process a little bit diferent. To connecting the tablet to the pc i enter fastbot mode. Press power+Vol down until the robot appear.
Then launch 4- not 3-.
In the same way launched every step that the tablet needed to be connected to pc, like 7-.
In step 9- pressed Vol up+ power to enter droidboot then do 10, were it sais launch cmd you have to launch debrick-flashall-FW-no_wipe.cmd in the new location.
The tablet works excelent, very happy here, thanks!!
---------- Post added at 08:09 AM ---------- Previous post was at 08:00 AM ----------
Ok, it was not easy to root .201, stuck in demo mode like 3 times. This is the correct way:
-Download this version of root zenfone:https://cloudup.com/files/ivrnLUAwMDS/download
-Download supersu from the playstore and install it.
-Install and open root zenfone, let the app run and don't put OK when it enter demo mode. Let it run for 15 seconds and just restart the tablet without pressing anything.
-If everything is ok you will be rooted.
-In case things go wrong and you enter demo mode, you have to press back button for 10 seconds, then it will ask you for a code, put 741603 and confirm. It will factory reset your tablet and demo will be gone. In case it not enter factory reset you will need to do it manually, after puting de code.
For me google play service bug dissapear when disabled google as device administrator of the device.
This tablet work 10 times better with Kitkat, it doesn't restart, it is stable, a lot better ram manager. The only problem i figure out ia battery stats, it's very buggie. I can use the tablet 1 hour with 1% of the battery, it happen to me with this tablet in all version since i buy it, maybe my battery is wrong...
Click to expand...
Click to collapse
A way easyer (and definitive) solution to root the tab is to use the tethered recovery and flash supersu, worked for me
Well new problem, i don't remember how to properly install xposed on kitkat on this tab. Tried the official installer but the settings in gravity box for kitkat are ignored.
@Saarge
Hi,
i use the 2.7 experimental version but gravity box won't work but hk theme engine works good for changing icons and other theme stuff but it doesn't change the homescreen/settings screen backgrounds for this i use holo background themer.
To change the softbar buttons i use another theme engine mod.So with this three modules one can customize the tab pretty well.But i didn't found a mod to change the quick menu settings yet.
can i do this for the android 5.1.1 version? quote me so i know someone replied to me
Kennii said:
can i do this for the android 5.1.1 version? quote me so i know someone replied to me
Click to expand...
Click to collapse
There is no 5.1.1 for this tablet. Last firmware is 5.0.1 lollipop .36 and you can rollback to kitkay in any lollipop version.
Hello,
Thanks for your great post !
I have a problem after step 4, my tablet reboot but after ASUS LOGO, my screen still black !
Thanks, i did it in my Linux box, everything worked fine. Now the tablet is usable again!
black screen
im getting black screen after step 4
To sum it up quickly, I put my Axon 7 up for sale on ebay. 5 day listing. It currently has ~24 hours left on it and plenty of bidders. ZTE Gladly offered a replacement but it would take 10 or more days. I had previously rooted the phone, and wanted to send it as though it came from the factory. I went into fastboot, did 'fastboot oem lock' over the fastboot shell, and it said successful. The device "rebooted" into a black screen. The device now appears to be bricked. It will show a ZTE logo for about a second when I hold the power button and then no more. I cannot seem to get it respond to a charge, go into fastboot, recovery, or anything else except what I described. It sounds hopeless to me, but maybe someone here is a miracle worker. Thank you very much.
for starters which model to you have?
You were completely stock, not rooted before locking?
lafester said:
You were completely stock, not rooted before locking?
Click to expand...
Click to collapse
I had flashed CM to it previously but when I did a relock I had reflashed stock MiFavor found here on XDA.
Edit: TWRP official a2017u was on the device, and I may have flashed supersu as well during the stock reflash. It was almost a week ago, I can't remember.
DrakenFX said:
for starters which model to you have?
Click to expand...
Click to collapse
A2017U
erer1243 said:
I had flashed CM to it previously but when I did a relock I had reflashed stock MiFavor found here on XDA.
A2017U
Click to expand...
Click to collapse
If you can boot to recovery you can try using ZTE B20 file, look here https://www.zteusa.com/axon-7#support under SOFTWARE UPDATES
* Move that file to your SDCard ,
* Boot to your recovery and flash that file.
DrakenFX said:
If you can boot to recovery you can try using ZTE B20 file, look here https://www.zteusa.com/axon-7#support under SOFTWARE UPDATES
* Move that file to your SDCard ,
* Boot to your recovery and flash that file.
Click to expand...
Click to collapse
I cannot boot into recovery. I cannot do anything except what I described, the quick ZTE logo, and then nothing. The computer does recognize that there is a device plugged in though, but ADB and fastboot will not see it.
erer1243 said:
I cannot boot into recovery. I cannot do anything except what I described, the quick ZTE logo, and then nothing. The computer does recognize that there is a device plugged in though, but ADB and fastboot will not see it.
Click to expand...
Click to collapse
not even Manual boot to recovery?
Press & Hold Volume Up + Power till menu kicks in.
you other option booting to EDL and use @tennear or tenfar tool to flash TWRP ONLY and flash that file or my B29.MergeBootstack and StockSystem files
DrakenFX said:
not even Manual boot to recovery?
Press & Hold Volume Up + Power till menu kicks in.
you other option booting to EDL and use @tennear or tenfar tool to flash TWRP ONLY and flash that file or my B29.MergeBootstack and StockSystem files
Click to expand...
Click to collapse
Nothing happens. It will not go into fastboot or recovery, no matter what I hold, for how long, anything. I believe it is either trying to display the "Your device cannot be trusted" screen and fails or is trying to do some other thing during pre-boot and is stuck in a loop. I don't know what EDL is but I'd be willing to tear this phone a new asshole if I can fix it within 24 hours. Happy to try anything, it seems like it can't get any worse than this.
erer1243 said:
I believe it is either trying to display the "Your device cannot be trusted"
Click to expand...
Click to collapse
this means, you still UNLOCK, when you are there and i mean when that message shows up, press any of the volume key and will give you a menu, from there you can boot to recovery - fastboot - bootloader.
if you see that menu, BOOT to BOOTLOADER and tell me the status.
DrakenFX said:
this means, you still UNLOCK, when you are there and i mean when that message shows up, press any of the volume key and will give you a menu, from there you can boot to recovery - fastboot - bootloader.
if you see that menu, BOOT to BOOTLOADER and tell me the status.
Click to expand...
Click to collapse
Well I just successfully locked it before making the thread... So it is not unlocked any longer. That was just speculation. I have no menus, holding down volume buttons and power does not do anything, I cannot get into fastboot, recovery, etc at all.
erer1243 said:
Well I just successfully locked it before making the thread... So it is not unlocked any longer. That was just speculation. I have no menus, holding down volume buttons and power does not do anything, I cannot get into fastboot, recovery, etc at all.
Click to expand...
Click to collapse
you know how to manually boot to EDL? so you can use any of the tool to flash TWRP.
manually booting to EDL and to make sure is in EDL mode CONNECT your device to your PC/Laptop and open DEVICE MANAGER now just Hold & Press Vol. Up and Down and make sure you are pressing both , if you are using case take the phone out of the case so you can really do it. Once you are pressing and holding both volume keys, press Power and check Device Manager for Qualcomm Port your device is using.
after that just proceed with the rest.
Just to make it a little clearer, to go to EDL mode. Phone must be off when you connect to PC, you hold both volume up/down and then touch power. It will still remain off BUT should now be recognized by the PC's device Manager.
I was in the same situation before. Using tenfar's tool to flash tenfar's TWRP (not official TWRP) the phone will boot TWRP with a locked bootloader. Then, go https://www.zteusa.com/axon-7 there and click the Support tab, then the Software Updates subsection. Download that, it could take a while though.
Once that's done, open the update.zip in something like 7-Zip and navigate to META-INF\com\google\android and extract the file updater-script. Open it with Notepad++ (not Notepad) or, if you're not on Windows, the text editor of your choice.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
On line 2, which is highlighted, delete that line. If you don't do this, it won't flash in TWRP. Don't worry though, it won't mess anything up. After saving, drag the extracted updater-script back into the zip file and confirm that you want to replace it.
Then, once your phone is in TWRP, copy the update.zip to your phone and flash it. For me, it took about 7 or 8 minutes to flash.
This part is the most important, absolutely do not skip this:
Before you reboot go back to the main TWRP menu and open the Mount menu. Uncheck system and then reboot. This is because TWRP installs a survival script in /system if it can, because otherwise TWRP will be changed to stock recovery. In this case though, it's what we want. This way OTA updates will successfully install. Stock recovery checks for any changes to /system and refuses to work if it sees any change at all, like the one TWRP makes unless you unmount system before you reboot.
After rebooting, you should update your phone from B20 to B27 and then from B27 to B29 to be up to date.
Also, this will re-lock your bootloader!
If you have any questions please ask, hopefully that helped you and maybe others too
RainofOranges said:
I was in the same situation before. Using tenfar's tool to flash tenfar's TWRP (not official TWRP) the phone will boot TWRP with a locked bootloader.
Click to expand...
Click to collapse
Maybe I just haven't looked hard enough... but I can't find any working instructions on how to flash/boot to a recovery. When I go by his instructions, nothing seems to work. I have, in the same folder as axon7root.exe, a recovery.img that is tenfar's twrp release. I have installed the driver he linked. I run axon7root -p 4 -r (yes, my phone is connected to the COM4 port) and the program just prints his little copyright splash screen and nothing happens. I have left it for ~half an hour, so it's obviously not just taking it's time. When I unplug the phone, it tells me my horse is dead (lmao someone get on translation) so it obviously knows the phone is there, but it just cannot do anything. Also, I cancelled the ebay listing a few minutes before seeing your post, disappointingly. Hopefully I can revive my horse and relist it.
erer1243 said:
Maybe I just haven't looked hard enough....
Click to expand...
Click to collapse
Are you sure your phone is in EDL mode? Did you try running it through a command promp as Administrator?
RainofOranges said:
Are you sure your phone is in EDL mode? Did you try running it through a command promp as Administrator?
Click to expand...
Click to collapse
I will try running it as admin. I am unsure how to tell if my phone is in EDL mode. I have reason to believe that it is stuck in a silent boot loop and maybe I can't get it into EDL/any other mode but I am just speculating there. I think that because 1, it won't respond to a charge and 2, I have to hold down the power button much longer than usual to make the ZTE logo pop up; It's as though I had to force shut down the phone and then boot it again in the 1 press.
erer1243 said:
Maybe I just haven't looked hard enough... but I can't find any working instructions on how to flash/boot to a recovery. When I go by his instructions, nothing seems to work. I have, in the same folder as axon7root.exe, a recovery.img that is tenfar's twrp release. I have installed the driver he linked. I run axon7root -p 4 -r (yes, my phone is connected to the COM4 port) and the program just prints his little copyright splash screen and nothing happens. I have left it for ~half an hour, so it's obviously not just taking it's time. When I unplug the phone, it tells me my horse is dead (lmao someone get on translation) so it obviously knows the phone is there, but it just cannot do anything. Also, I cancelled the ebay listing a few minutes before seeing your post, disappointingly. Hopefully I can revive my horse and relist it.
Click to expand...
Click to collapse
Mine did that - unplug phone, restart computer, hold both volume buttons and plug phone back in.
erer1243 said:
I will try running it as admin. I am unsure how to tell if my phone is in EDL mode. I have reason to believe that it is stuck in a silent boot loop and maybe I can't get it into EDL/any other mode but I am just speculating there. I think that because 1, it won't respond to a charge and 2, I have to hold down the power button much longer than usual to make the ZTE logo pop up; It's as though I had to force shut down the phone and then boot it again in the 1 press.
Click to expand...
Click to collapse
You can't tell that the phone is in EDL mode on the phone itself. You can only tell by trying the tool. If I remember right the button combination to get into EDL mode is both volume buttons held down and the power button also held down for 2 seconds or so at the same time.
tabletalker7 said:
Mine did that - unplug phone, restart computer, hold both volume buttons and plug phone back in.
Click to expand...
Click to collapse
No dice. As admin, computer restarted, I tried holding both volume buttons while plugging in.
update from my last post: I got tenfar's tool to upload his TWRP to the phone (sent it to the horse o.o) but it still will not boot anywhere. The phone has not changed at all.
So I'm getting stuck on the nexus boot screen and the OS will not load. Decided to to just flash the stock image and start from scratch. I'm able to get into stock recovery but unable to boot into Fastboot/bootloader from there. It just kicks me back to try and start the OS. When I get to the loading screen it shows dead Andy with a triangle and "no command" instead of being able to select recovery/bootloader/start system normal. I am unlocked and was running the stock image 8.0.0 before all this happened. No root. I've been reading that asus or nexus screwed something up. So am I bricked? I've tried to adb sideload from recovery but in getting a verification error.
Edit: Problem solved. I'm an idiot. There is a lag for when the NP Google logo comes on till the screen actually recognizes and shows up. Therefore, I was holding the button too long and it passing fastboot and going directly into recovery.
I'm stuck at the same point and thinking that i am just holding the reset button too long.
Got any idea on how long you held it for? I just seem to go directly into recovery and get no access to fastboot to do anything...
pegaxs said:
I'm stuck at the same point and thinking that i am just holding the reset button too long.
Got any idea on how long you held it for? I just seem to go directly into recovery and get no access to fastboot to do anything...
Click to expand...
Click to collapse
I honestly cannot remember, Maybe 3 to 5 seconds? As soon as I see that there is a signal yo the TV I let go. I know that if you do hold the button to long that it will go directly into recovery. Just start timing it at a point when you plug the power cord in and start working from there.
Hold the button / watch the LED
pegaxs said:
I'm stuck at the same point and thinking that i am just holding the reset button too long.
Got any idea on how long you held it for? I just seem to go directly into recovery and get no access to fastboot to do anything...
Click to expand...
Click to collapse
When you apply power the tiny led lights up solid. You should hold the button down until you see the light change to a blinking response, then let go. After that you will see the Google unlock and then you will get the fastboot screen.
I wish it was that easy. I have tried that. I can get the device into the recovery menu, but not into fastboot.
From the recovery menu, I can select “reboot into fastboot” but it just goes back into the bootloop “Google” screen.
The other issue is that the light never flashes. If I hold the button down, it just either reboots, or never flashes.
If I release the button when the Google logo comes up, it will go to the laying down Android with open chest and red exclamation mark in a triangle and the words “no command” under it.
If I press and hold the reset button for 5 seconds, then release it, it will boot into recovery, where I can select a few things.
When in recovery, the only thing I can get to connect to my PC is “sideload”. If I try and side load anything, such as magisk, I just get verification errors.
I cannot get the device to connect as a device. I cannot get it into fastboot. I have done nothing else too it. It was working last week when I turned it on, albeit YouTube wasn’t, and on the weekend I went to use it and it was dead and showing the “Google” logo screen.
So, unfortunately, due to there not being a “flashing” led, there seems to be no way of getting into fastboot.
I have even tried OP’s suggestion of timing the button hold and resetting at intervals of seconds, and this has also not worked, from 1 second all the way to 30 seconds...
let me add a "me too" Can't get into fastboot...even using adb reboot bootloader just reboots to recovery.
SOLVED
bigworm50 said:
let me add a "me too" Can't get into fastboot...even using adb reboot bootloader just reboots to recovery.
Click to expand...
Click to collapse
Can't you do an OTA image using recovery mode? Solution for me was to reflash using android 8 with the full google tool kit, doesn't work with a partial toolkit.
Same story here. Can't do OTA update either. I have a full kit too. I'm getting an error saying this update is for "fungu" devices. This is "". This probably means that it can't read even the device type. This is really horrible what Google has done! I tried loading different OTA versions as well. Same error.
Ideas?
CVZAYIN said:
Can't you do an OTA image using recovery mode? Solution for me was to reflash using android 8 with the full google tool kit, doesn't work with a partial toolkit.
Click to expand...
Click to collapse
SOLVED
nonamer88 said:
Same story here. Can't do OTA update either. I have a full kit too. I'm getting an error saying this update is for "fungu" devices. This is "". This probably means that it can't read even the device type. This is really horrible what Google has done! I tried loading different OTA versions as well. Same error.
Ideas?
Click to expand...
Click to collapse
NEXUS PLAYER IS THE FUGU OS
Went to the google Nexus images download page to get Android 8 OS and the platform tools (factory img). Installed the Win10 USB driver and then unzipped only the main first img zip file into the platform tools root folder. Enabled NP developer mode and enabled USB debugging according to google NP image download page instructions. Then restart NP into fastboot mode by holding the button down while plugging it in, holding button only until you see fast flashing LED will put you into fastboot mode. On PC, open command prompt and navigate to platform tools folder, then unlocked the device and ran the flash-all.bat file (see instructions). Bingo. If fastboot mode not available, you may want to see some of the youtube nexus bootloop videos on how to get into recovery mode and flash the OTA img instead. Flashing with Android 8 should free up about a gig of disk space. I relocked mine afterwards. Hope this helps.
CVZAYIN said:
Then restart NP into fastboot mode by holding the button down while plugging it in, holding button only until you see fast flashing LED will put you into fastboot mode.
Click to expand...
Click to collapse
NOT SOLVED
Did you not read the part where I and other users said there is no flashing LED and there is no fastboot?
I got my old NP out today to follow your solution and I am still at my original problem. I cannot even get into fastboot. I can get to stock recovery, but that’s it. I cannot even use that to reboot into fastboot, as it just goes back to the bootlooping google logo screen.
I can get very limited ADB access to sideload, but that is it. No root. No fastboot commands.
I solved the issue by putting it in a box, forgetting about it and buying an Apple TV box.
pegaxs said:
NOT SOLVED
Did you not read the part where I and other users said there is no flashing LED and there is no fastboot? I got my old NP out today to follow your solution and I am still at my original problem. I cannot even get into fastboot. I can get to stock recovery, but that’s it. I cannot even use that to reboot into fastboot, as it just goes back to the bootlooping google logo screen. I can get very limited ADB access to sideload, but that is it. No root. No fastboot commands. I solved the issue by putting it in a box, forgetting about it and buying an Apple TV box.
Click to expand...
Click to collapse
Wasn't my issue, but I'd mentioned earlier having seen where OTA images can be installed using recovery mode to resolve the bootlooping.
https://www.youtube.com/watch?v=Vscps1gNn0U
https://www.theandroidsoul.com/ota-bootloop-fix-nexus-6-6p-5x-9-9g-and-player/
Anyone else able to get past this? I get the following when i try to sideload the ota through the recovery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
https://drive.google.com/file/d/1KglLdXeyOdPqm8ktKe8jAZzz0X6-uNsL/view?usp=drivesdk
CVZAYIN said:
Wasn't my issue, but I'd mentioned earlier having seen where OTA images can be installed using recovery mode to resolve the bootlooping.
https://www.youtube.com/watch?v=Vscps1gNn0U
https://www.theandroidsoul.com/ota-bootloop-fix-nexus-6-6p-5x-9-9g-and-player/
Click to expand...
Click to collapse