Nexus 7 flo stuck in bootloop - Nexus 7 (2013) Q&A

Hi all,
My nexus 7 2013 wifi edition got stuck in bootloop. The tablet just crashed when I went in the apps section in the settings menu. Since then it is stuck in a bootloop and can't boot anymore. The tablet was running a kitkat version of android and was rooted.
I tried wiping cache/dalvik/data, nothing works and nothing is able to mount. It also shows the 0mb internal memory. Wiping doesn't work so I can't get rid of the 0mb. With the nexus toolkit it doesn't let me flash anything or return it to stock
I had TWRP 2.6.3 installed and tried updating it to 2.8.4 but the flashing failed.
It was able to send the recovery file to the tablet but then I got a "remote: flash write failure".
I am running out of options here. What can I do. TWRP flash seems to have failed and if I try to enter recovery now it also gets stuck in the bootlogo.
I hope someone can help me further.

Hello, and thanks for using XDA Assist.
There is a one click factory restore tool that you can find here, that has helped me in the past when I hard bricked my Nexus 7 a couple of years ago. It should work for you too.
Good luck!

Thank you for your reply. I tried the tool.
What I get, when using the bricked NEXUS.bat:
Code:
08e80e7d fastboot
sending 'bootloader' <3911 KB>...
OKAY [ 0.202s ]
writing 'bootloader'...
FAILED <remote: flash write failure>
finished. total time: 90.748s
rebootin into bootloader...
OKAY [ 0.009s ]
finished. Total time: 0.011s
erasing 'system'...
It will stick on erasing system.

Also after performing these steps, I can not boot into recovery anymore. TWRP does not start and there is also no android puppet on its back

Wrong advice. Emmc problem for which there is no remedy yet.

Th same issue happened to me tonight using my 7. I'm getting the same message when I try to flash the stock image isingbthe "flash-all" command.
Rick

Memke said:
Thank you for your reply. I tried the tool.
What I get, when using the bricked NEXUS.bat:
Code:
08e80e7d fastboot
sending 'bootloader' <3911 KB>...
OKAY [ 0.202s ]
writing 'bootloader'...
FAILED <remote: flash write failure>
finished. total time: 90.748s
rebootin into bootloader...
OKAY [ 0.009s ]
finished. Total time: 0.011s
erasing 'system'...
It will stick on erasing system.
Click to expand...
Click to collapse
I copied your log to my thread as an example of symptoms of failed, unwritable eMMC flash memory.

Today I contacted Asus and was given an RMA #. I believe this to be a hardware failure also because it happened out of no where on me. I was watching a video fine, went to reboot the tablet and it went to bootloader loop.

C5Longhorn said:
Today I contacted Asus and was given an RMA #. I believe this to be a hardware failure also because it happened out of no where on me. I was watching a video fine, went to reboot the tablet and it went to bootloader loop.
Click to expand...
Click to collapse
May I ask you to post eMMC brand when you get a replacement from ASUS?

Yes, I will if I go through with it and get it back.
Sent from my Nexus 6P using Tapatalk

k23m said:
May I ask you to post eMMC brand when you get a replacement from ASUS?
Click to expand...
Click to collapse
I posted in the other thread, but I got a tablet back from ASUS this week. I got the following chip info from SD Insight.
Hynix
HBG4e
31 GB
Jun 2013

Finally Found a Fix
So Basically below are the steps that I have followed to fix this issue on my TAB.
**NOTE: Replace ****?? with www
Hardware fix (In case due to internal wire contact issues .. this may happen due to drops )
Fix 1: (Temp)
- Follow the instructions provided by ****??.youtube.com/watch?v=0C5tpeNA4xg
Fix 2: ( Depend on analysis from Fix1.. this could be a more permanent fix)
- Is Fix 1 works then there is a high probability that you had dropped the device @ least once. I guess build quality by ASUS is kind of dodgy for Nexus 7 2013 Model.
For me this was caused due to Touchscreen Digitizer Cable, this could be due to frequent drops of Tab (Refer: ****??.ifixit.com/Store/Parts/Nexus-7-2nd-Gen-Wi-Fi-LCD-Screen-and-Digitizer-Assembly-/IF235-039-1 The Cable is Silver Color)
Power off the TAB, Disconnect and reconnect the cable (this also fixed other issue for me... gyro was not working properly in my device) . Now power ON the device.
Software Fix
Fix 3( If the issue is not related to HW, Note, Following below instruction will wipe your device Data)
- Download the latest Rom image from ****??developers.google.com/android/images#razor (for Wifi Version)
- Follow the Steps ****??developers.google.com/android/images#instructions
PS: There are many tutorials in youtube for flashing ROM/Recovering Data from TAB. Please search and Refer . Please add Https for all the link as I can post full link here.
HOPE This works for you

Related

[Q&A] Kindle Fire 2 7" Stock Restore

Q&A for Kindle Fire 2 7" Stock Restore
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for Kindle Fire 2 7" Stock Restore. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Gen2 Kindle stock restore - stuck in a boot loop - following overlode's doc
Overlode - Huge thank you for the simple list for us NOOBS of how to get a stock Kindle stuck in a boot loop back up and running. I am having some problems though and was hoping for some help.
I am running Win7 on my PC. I've installed Android SDK, I have a factory cable and my gen 2 Kindle has the pretty "Fastboot" logo with the flashing green light and a non-flashing red light. When I go into my devices manager and see the "Otter2-***.***" it does have the yellow triangle. This is where I deviate from your instructions (in your .doc file). When I right click I do not see the simple "update driver software". I have to go through several windows to finally reach that option. No big deal. But... I clicked the option to "browse my computer for driver software" then "Let me pick from a list of device drivers on my computer". I do not have the option to select "Kindle". I went to have it list ALL DRIVERS and it is not in that list either.
I'm stuck. I don't know how to get the drivers up and working so I can continue with your instruction sheet. I REALLY appreciate all your efforts (with the drop box and everything). I've been fighting this boot loop for a month now and I'm scared to make a bigger mistake. I can build a pc from scratch- no problem... programming and mobile devices just make my brain hurt. Be kind. Everyone seems to throw around abbreviations like Halloween candy and this just makes me want to run for the hills. I'm learning but please don't just assume I know what you're talking about. Thanks in Advance!!
Myth421 said:
Overlode - Huge thank you for the simple list for us NOOBS of how to get a stock Kindle stuck in a boot loop back up and running. I am having some problems though and was hoping for some help.
I am running Win7 on my PC. I've installed Android SDK, I have a factory cable and my gen 2 Kindle has the pretty "Fastboot" logo with the flashing green light and a non-flashing red light. When I go into my devices manager and see the "Otter2-***.***" it does have the yellow triangle. This is where I deviate from your instructions (in your .doc file). When I right click I do not see the simple "update driver software". I have to go through several windows to finally reach that option. No big deal. But... I clicked the option to "browse my computer for driver software" then "Let me pick from a list of device drivers on my computer". I do not have the option to select "Kindle". I went to have it list ALL DRIVERS and it is not in that list either.
I'm stuck. I don't know how to get the drivers up and working so I can continue with your instruction sheet. I REALLY appreciate all your efforts (with the drop box and everything). I've been fighting this boot loop for a month now and I'm scared to make a bigger mistake. I can build a pc from scratch- no problem... programming and mobile devices just make my brain hurt. Be kind. Everyone seems to throw around abbreviations like Halloween candy and this just makes me want to run for the hills. I'm learning but please don't just assume I know what you're talking about. Thanks in Advance!!
Click to expand...
Click to collapse
EDIT: (a day or so later) Hey.. Nevermind. I was able to finally figure things out and downloaded KindleFireFirstAid and was able to wipe it out back to stock using my factory cable. The boot loop was limiting my options. Thanks Anyway.
Fastboot
What would be stopping Fastboot from recognizing my device? I have a fastboot cable for my kindle fire 2, I plug it into my computer then into the kf2, the kf2 boots up into fastboot mode my computer see the kindle and it has the proper drivers installed, but fastboot can't see it for some reason.
I had this problem before when I installed CM10 onto my kf2 but that was a year ago and for the life of me I don't remember how I got fastboot to see my kf2.
All i want to do is downgrade my kf2 back to stock and sell it on ebay. PLEASE HELP! I'm dying here
Any other options?
Overlode-My wife;s KF2 was stuck in boot loop so I tried your stock restore method with a factory cable. Everything seemed to work fine. The drivers were installed, fastboot commands worked on the device, etc. When I did the last reboot step, the device never turned back on. Now the device will not power up with the factory cable or USB cable. Is there anything I can do to fix this KF2 or is it permanently screwed? Thanks.
Kindle Fire 2 - Bricked
Today I tried the procedure in post http://forum.xda-developers.com/kindle-fire-hd/fire-2-development/kindle-fire-2-7-stock-restore-t2840987 but as I use Linux and have the SDK installed I entered the commands from console.
A couple of days ago I flashed Cyanogenmod using very similar steps.
Here is my log for the attempt to restore the stock ROM:
Code:
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
sending 'bootloader' (227 KB)...
OKAY [ 0.060s]
writing 'bootloader'...
OKAY [ 0.060s]
finished. total time: 0.120s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash boot boot.img
sending 'boot' (4310 KB)...
OKAY [ 1.082s]
writing 'boot'...
OKAY [ 1.053s]
finished. total time: 2.134s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash recovery recovery.img
sending 'recovery' (4828 KB)...
OKAY [ 1.211s]
writing 'recovery'...
OKAY [ 0.954s]
finished. total time: 2.165s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 -w
erasing 'userdata'...
OKAY [114.081s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.000s]
erasing 'cache'...
OKAY [ 28.939s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.000s]
finished. total time: 143.021s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash system system.img
sending 'system' (777953 KB)...
FAILED (remote: data too large)
finished. total time: 0.004s
(1)
What is worse, after the failure I rebooted in order to restart with the procedure that worked a couple of days ago and leave Cyanogenmod in the Kindle...
but...
No reboot, no lights, no USB detected....
It seems that the tablet is hard bricked.
Is there anything that can be done except using it as a paperweight?
Thanks in advance
KF2 - hardbricked and restored.......almost!!!
Hi,
I have a KF2, which I had previously rooted and installed CM10 custom ROM. Had no problems with it, but decided to try a few more custom ROMS. Forgot about NOT using the KFU program as it was for KF1 devices, and for some stupid reason went ahead and flashed the wrong bootloader.
Result is fairly predictable - HARD BRICKED KF2!!
Thought that was it - searched the forums and everyone was saying the same - no way back from that! Then I came across Kurohyou's post and brilliant guide about hacking a card reader and attaching direct to motherboard. Followed his guide and voila - managed to boot up into recovery (TWRP). However after pushing the ROM files etc to try and install CM ROM again just kept getting "error flashing ROM" . I left the thing after trying various methods and different PC's etc to push the files across and gave up. When I went back to it this morning I couldn't get it to boot into recovery - which I thought was a bit strange. However FASTBOOT mode is ok - I have made a fastboot cable myself which works fine. Kindle was booting up with orange logo, quick flash, orange kindle logo again and repeat. It would not boot into recovery even though I had flashed the correct files via fastboot.
Again almost giving up when I came across Overlode's instructions. Followed them to the letter, and what I am left with now is the standard Kindle Fire logo (orange) which blinks after about 5 seconds and just stays there - left it for about an hour just in case....
I can post screenshots of me flashing the files as per Overlode's instructions if it helps. I get a few errors when using the wipe command, response is "erase successful, but not automatically formatting. File system type not supported" everything else is ok.
I still have the hacked card reader attached which through Ubuntu can see the EMMC directly so don't know if might be worth copying the files directly instead of flashing via fastboot?
Any suggestions gratefully received...... I'm at my wits end with this thing - I know I should have left well alone!!! but I feel like I have run a marathon with this thing only to have fallen flat on my face 5 metres from the finish line!!
Thanks in advance for any help.
lmayala said:
Today I tried the procedure in post http://forum.xda-developers.com/kin...opment/kindle-fire-2-7-stock-restore-t2840987 but as I use Linux and have the SDK installed I entered the commands from console.
A couple of days ago I flashed Cyanogenmod using very similar steps.
Here is my log for the attempt to restore the stock ROM:
Code:
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash bootloader otter2-u-boot-prod-10.2.4.bin
sending 'bootloader' (227 KB)...
OKAY [ 0.060s]
writing 'bootloader'...
OKAY [ 0.060s]
finished. total time: 0.120s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash boot boot.img
sending 'boot' (4310 KB)...
OKAY [ 1.082s]
writing 'boot'...
OKAY [ 1.053s]
finished. total time: 2.134s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash recovery recovery.img
sending 'recovery' (4828 KB)...
OKAY [ 1.211s]
writing 'recovery'...
OKAY [ 0.954s]
finished. total time: 2.165s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 -w
erasing 'userdata'...
OKAY [114.081s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.000s]
erasing 'cache'...
OKAY [ 28.939s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.000s]
finished. total time: 143.021s
(0)
[email protected]:/home/lmendez/Descargas# fastboot -i 0x1949 flash system system.img
sending 'system' (777953 KB)...
FAILED (remote: data too large)
finished. total time: 0.004s
(1)
What is worse, after the failure I rebooted in order to restart with the procedure that worked a couple of days ago and leave Cyanogenmod in the Kindle...
but...
No reboot, no lights, no USB detected....
It seems that the tablet is hard bricked.
Is there anything that can be done except using it as a paperweight?
Thanks in advance
Click to expand...
Click to collapse
Hi - see my last post - I too have a hard bricked kindle. if you're handy with a soldering iron you can try it - I can confirm it does work.
details here -
http://forum.xda-developers.com/showthread.php?t=2415870
I managed to get my kindle from nothing (not even charging light) to back up and running with TWRP installed. I couldn't get a custom ROM installed, kept getting errors - but I think my board has other issues. While I was putting it back together I managed to stick my screwdriver through the battery (don't ask!!!) Since then I think I have caused other damage and it was never the same again I think I may have damaged the memory or the EMMC..... on the hunt for new motherboard at present!
Good luck!
registered an account just to thank you. You saved my KF2.

[Q] Please help, P6 stuck at boot screen

A friend of mine as the same phone as me, the Huawei Ascend P6, and when she said hers was broken I said I would take a look. I have played around with flashing Android Roms etcetera, but I am totally stuck with this problem.
The problem is as follows: when booting the phone it shows the Huawei Ascend logo (as it should) for a couple of seconds, but then instead of the Huawei animation it shows the name "android" and gets stuck there (see attachment).
After some researching I put the UPDATE.APP file from the Huawei website in the dload folder on the root of the SD-card and tried rebooting. I tried a several times, but nothing happened.
Next I successfully booted in recovery mode but even when starting recovery the screen shows errors (see attachment):
Code:
E:failed to mount /cache (Invalid argument)
E:failed to mount /cache (Invalid argument)
ensure_path_mounted Failed
E:failed to mount /cache (Invalid argument
Installing a ZIP file, wipe cache and wipe data give even more errors.
So I thought I would try flashing through ADB/fastboot, and used the HuaweiUpdateExtractor tool to get the images. I can get manually in fastboot mode, but when I try to flash an image get the error
Code:
FAILED (remote: flash failure, ErrNo:2)
I tried using different files, USB ports, cables, linux and windows but nothing seems to help. Has anyone an idea what to do next?
it would help much to know what fw is / was flashed as last..
this android screen means to me that it should be a chinese / non international version..
if you enter fastboot mode and connect your phone to the pc make sure your pc recognizes the phone (for checking: fastboot devices - it should show you many "????")..if so try to install twrp (there are many threads about it)..then you might be able to install (through twrp) a repack of b513 or another version (but it has to be a repack)..
after that (and hopefully successful) you can try (use search) to change to an official fw again..
just my suggestion
hope you get a solution..
blueIBI said:
it would help much to know what fw is / was flashed as last..
this android screen means to me that it should be a chinese / non international version..
if you enter fastboot mode and connect your phone to the pc make sure your pc recognizes the phone (for checking: fastboot devices - it should show you many "????")..if so try to install twrp (there are many threads about it)..then you might be able to install (through twrp) a repack of b513 or another version (but it has to be a repack)..
after that (and hopefully successful) you can try (use search) to change to an official fw again..
just my suggestion
hope you get a solution..
Click to expand...
Click to collapse
Since I can not boot and it's not my own phone I have no clue what the version is
Luckily my PC recognizes the phone in fastboot (indeed with a weird name with a lot of ?), but I am not able to flash twrp because every time I try I get a FAILED response... Maybe the file I have is wrong. Could you point me to a thread about falshing twrp?
here is a guide for unlocking bootloader: http://forum.xda-developers.com/showthread.php?p=50724517
here is a twrp for JB roms: http://forum.xda-developers.com/showthread.php?p=47633501
here for KK roms: http://forum.xda-developers.com/showthread.php?p=51718302
maybe you need to unlock your bootloader at first
changes not working
Thanks for the links! I am able to flash an image, but for some reason my changes won't stick. When I boot in fastboot it says it is locked and I am able to unlock it, but everytime I reboot it is locked again. The same happens with twrp, I am able to flash the image but for some reason when I boot back into recovery nothing has changed.
My fastboot commands and output:
Code:
C:\Android>fastboot oem get-bootinfo
...
(bootloader) locked
OKAY [ 1.952s]
finished. total time: 1.952s
C:\Android>fastboot oem unlock UUUUUUUUUUUUUUUU
...
OKAY [ 0.012s]
finished. total time: 0.012s
C:\Android>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.001s]
finished. total time: 0.001s
C:\Android>fastboot flash recovery twrp_2_6_3_3_recovery.img
sending 'recovery' (8690 KB)...
OKAY [ 0.259s]
writing 'recovery'...
OKAY [ 0.390s]
finished. total time: 0.650s
Any idea?
hm..
in this case no..
i'm sorry..your friend should bring it to the service..that's the best advice for now..
blueIBI said:
hm..
in this case no..
i'm sorry..your friend should bring it to the service..that's the best advice for now..
Click to expand...
Click to collapse
That's what I was afraid of..
I think the unlock code doesn't work correctly on this phone for some reason, but I don't think I'll be able to get an unlock code specific for my device from Huawei, without serial number and such which I can't get since the phone doesn't boot.
I hope there is some warranty left...
Results
If anyone is interested (perhaps in the future), the phone was sent for repairs and is working again. They probably replaced the motherboard, but luckily it all fell under the warranty.
Thanks to blueIBI for trying to help!!

Stuck in bootloop, can't flash

Posted in the general thread, but no replies.
I seem to have softbricked my phone by rooting then applying the OTA update. I've tried re-rooting, wiping cache, factory resetting, etc., and nothing seems to work. Following the steps in http://forum.xda-developers.com/zenf...d-zf2-t3127835 I can get to step 7, but when I submit any of the commands I get this:
Code:
C:\Users\Elliott\Downloads\CWM_Zenfone_2_Intel>fastboot flash fastboot droidboot.img
target reported max download size of 536870912 bytes
sending 'fastboot' (14822 KB)...
OKAY [ 0.666s]
writing 'fastboot'...
FAILED (remote: Permission denied
)
finished. total time: 0.839s
C:\Users\Elliott\Downloads\CWM_Zenfone_2_Intel>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (11882 KB)...
OKAY [ 0.545s]
writing 'recovery'...
FAILED (remote: Permission denied
)
finished. total time: 0.716s
C:\Users\Elliott\Downloads\CWM_Zenfone_2_Intel>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (11868 KB)...
OKAY [ 0.522s]
writing 'boot'...
FAILED (remote: Permission denied
)
finished. total time: 0.694s
C:\Users\Elliott\Downloads\CWM_Zenfone_2_Intel>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
FAILED (remote: Permission denied)
finished. total time: 125.564s
It wasn't clear if it was a windows permission error or an android permission error, so I tried an admin command prompt but that didn't change anything.
Any suggestions? Thanks in advance
Bump in hopes of a solution
And another bump, any help would be greatly appreciated
I'm wondering if it has to do with having a bootloader installed being over a certain version. I had 2 Asus Zenfone 2s and I get the same error messages. I can't remember what my first ZF2 had for firmware to start, but I was a dummy and updated it all the way to 2.20.40.90 stock. Everytime I tried to write via fastboot, Permission Denied. My new ZF2 on 2.20.40.59 also has the same problem. I feel like Asus patched the ability to fastboot these files or something. Running CMD as Administrator doesn't help the situation.
bumping because I'm having the same issue, coming back to stock after having CM12.1
As easy as it sounds, the solution was just flashing the newest software from the ASUS website, using adb sideload UL-Z00A-WW-2.20.40.97-user.zip
I can't imagine why I wouldn't have done that sooner, but it fixed it. Whether that worked due to something else I did, i have no idea, but my phone is now working
I had that before but fortunately I was able to fix it.
Get a microsd, but a firmware from Asus website, make sure that it is the correct one if you have WW then download WW, download it from Asus website or it will not work.
Then put the micro sd on the phone., rename the file MOFD_UPDATE don't put zip cause it will be doubled.
Boot to bootloader then boot to recovery. Automatically the phone will restore itself.
Hi I'm currently facing a similar problem. Connected the phone via USB to a laptop and it rebooted all of a sudden and is in bootloop. It was not rooted and it was on 2.19.40.23, the phone is ZE550ML or Z008. There are 6 gigs of photos on internal memory which I want to recover.
I tried fastboot flashing preroot images and recovery boot and bootdroid images. Didn't work
I tried sideloading stock image from the Asus website. Didn't work
When I go into recovery the message - failed to map file /sdcard/MOFD_SDUPDATE comes up, last post said MOFD_UPDATE on my phone comes up different.
I also tried "adb pull / " - started pulling stuff but stops at some point.
I also tried flashing CWM and trying to mounts the internal storage as external device, didn't work.
I was also unable to mount the SD card, might have something to do with MOFD not being mapped.
Don't know if TWRP has any similar functionality but when I tried flashing any other recovery, after the process when I go into recovery itself the stock one takes over...
Any help would be greatly appreciated.
KylarBStern said:
Hi I'm currently facing a similar problem. Connected the phone via USB to a laptop and it rebooted all of a sudden and is in bootloop. It was not rooted and it was on 2.19.40.23, the phone is ZE550ML or Z008. There are 6 gigs of photos on internal memory which I want to recover.
I tried fastboot flashing preroot images and recovery boot and bootdroid images. Didn't work
I tried sideloading stock image from the Asus website. Didn't work
When I go into recovery the message - failed to map file /sdcard/MOFD_SDUPDATE comes up, last post said MOFD_UPDATE on my phone comes up different.
I also tried "adb pull / " - started pulling stuff but stops at some point.
I also tried flashing CWM and trying to mounts the internal storage as external device, didn't work.
Don't know if TWRP has any similar functionality but when I tried flashing any other recovery, after the process when I go into recovery itself the stock one takes over...
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Do what i have posted above
Sent from my ONE A2001 using Tapatalk
ebanreb37 said:
Do what i have posted above
Sent from my ONE A2001 using Tapatalk
Click to expand...
Click to collapse
I already tried it, I wrote in my post that I tried it. And it didn't work.
KylarBStern said:
I already tried it, I wrote in my post that I tried it. And it didn't work.
Click to expand...
Click to collapse
SD card MUST be FAT32 or 32gb or less. If you are using anything else it won't detect the sd card.
Cheers...
Ok it's been a while since I've tried anything with this phone and just now I did what you said, copied the firmware file which I downloaded from ASUS to a 2GB sd card formatted in fat32, rebooted to recovery phone applied the update sucessfully and restarted but I am still stuck in bootloop ? I tried every method so I asume the phone is ****ed and I should send it back for RMA ?

[TOOL] Deuces Bootloop-Recovery & Flashing Script v4.4/v4.5 [06-13-2018]

Download script: HERE
Download Factory Images: HERE
Download ADB/Fastboot: Platform Tools
Download USB Drivers: USB Drivers -- Driver Installation Video
-----------------------------------------------------------------------------------------------------------------------------------------------------------
This script is for the UNLOCKED BOOTLOADER pixel2 / pixel2 XL, and will help:
Fix Bootloops
Flash both Slots A and B
Work with any Google-provided factory image
Detect bootloader and radio special *.img names automagically
(Optional): Unlock Bootloader and Critical
(Optional): Format Userdata
-----------------------------------------------------------------------------------------------------------------------------------------------------------
Instructions:
Extract factory image zip file, as well as the image zip file within it!
This will lead to ~21 .img files in the same folder, with the deuce-flash-all script!
SEE SCREENSHOT!!.
Once you have all these together, run the Deuce-Flash-All script. ( .bat for Windows, .sh for Linux)
-----------------------------------------------------------------------------------------------------------------------------------------------------------
If you are having issues with this script:
Verify you have the environment variable (path) set for adb and fastboot
Try a different USB port
Try a different cable (preferably USB A -> USB C)
Format Userdata in Stock Recovery
Boot plain factory image before doing mods like Locking Bootloader / Kernel / TWRP / Magisk
​
This was built for the 2 xl but I have modified it to work with the pixel 2.
The main thread, which has lots of troubleshooting Q/A is here:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Changelog:
06-13-2018: Added support for latest platform tools
01-14-2018: Fixed bug. Made unlocking optional to speed it up, combined scripts for taimen & walleye
01-09-2018: Removed support for locking bootloader, added hard-coded slot selections
12-26-2017: Added support for Pixel 2 (Walleye)
I have been using this on my walleye since v4, guess now we no longer get the errors for the critical unlock status.
Makes sense, thanks as always most beneficial tool besides adb itself for a pixel device!
Hey. When I boot my Pixel 2 XL I get a can’t find valid OS. Will this fix it?
It's possible ton unlock bootloader, install magisk / root without wipe the phone ?
Anyway, thanks for your great work !
Matt17000 said:
It's possible ton unlock bootloader, install magisk / root without wipe the phone ?
Anyway, thanks for your great work !
Click to expand...
Click to collapse
Unlocking the bootloader always wipes. Magisk, recovery, and other things will not.
You've saved me twice from a brick. Thank you.
Dude you are a freaking god send! THANK YOU!
Had anyone tested this with January 8.1 release? Just asking so I can update the top post. Working fine on XL
Deuces said:
Had anyone tested this with January 8.1 release? Just asking so I can update the top post. Working fine on XL
Click to expand...
Click to collapse
I am about to use it in 3 hrs. I am currently running dec patch with twrp and magisk. Ill try to sideload january patch soon.
I used it to recover from a softbrick, had an error on mac address 02:00 etc and fingerprint hardware, not sure if related to your Tool, but it did let me Boot back into system after everything else failed, all working again after factory flash with wipe
I modified the script to take away the locking section, as people can't seem to RTFM
Also included changes to hard-select the slot A/B and further warnings on relocking bootloader
Deuces said:
I modified the script to take away the locking section, as people can't seem to RTFM
Also included changes to hard-select the slot A/B and further warnings on relocking bootloader
Click to expand...
Click to collapse
Hi @Deuces, I wonder if you could take a look at this. I just tried running your script (third time so far). I used the latest Walleye script, made sure I had the latest fastboot and adb. Please see below...it looks like the script got as far as trying to write bootloader_b...then it got stuck at "waiting for any device" with the display blank. Eventually (after a long time) I gave up and unplugged the phone. I can't get it to turn on at ALL. Not by holding down power, not by using the key combo to get into fastboot...the phone just seems DEAD. I plug it into a charger, and nothing happens. Plug it back into PC, and the computer doesn't know that the phone has been plugged in. It's just not there in the Device Manager.
I tried following Google's steps to troubleshoot a phone that doesn't turn on. I did find that if I hold the power button down for about 30 seconds, I do feel the phone vibrate, and see a line across the display, like the few times that I've had to hard reboot. But that was it. Trying to get into fastboot mode, even holding the buttons for a long time, doesn't work.
Any idea what could have happened, or what I can do? The battery wasn't 100% full when I started, but it was at least at 85%. I'm sure the battery didn't die. I'm a bit freaked out, as I can't even get it to power on. Thanks in advance.
Deuces-flash-all-script-V4.3-Windows
for Walleye - Google Pixel 2
USE AT YOUR OWN RISK
Press any key to continue . . .
Make Sure your Device is in Fastboot Mode
(Power off, hold Volume-Down, hold Power)
Once you are in fastboot,
Press any key to continue . . .
Running Unlock
Look at your device,
press up arrow and Power to confirm
...
FAILED (remote: Device already : unlocked!)
finished. total time: 0.006s
This will say "failed" if already unlocked - ignore
Locating Bootloader and Radio Filenames
Flashing...
Setting current slot to 'a'...
OKAY [ 0.012s]
finished. total time: 0.014s
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38644 KB)...
OKAY [ 1.189s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 1.206s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
target reported max download size of 536870912 bytes
sending 'radio_a' (60428 KB)...
OKAY [ 1.851s]
writing 'radio_a'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.690s]
finished. total time: 2.545s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
Setting current slot to 'b'...
OKAY [ 0.015s]
finished. total time: 0.017s
target reported max download size of 536870912 bytes
sending 'bootloader_b' (38644 KB)...
OKAY [ 1.051s]
writing 'bootloader_b'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 1.069s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.005s
< waiting for any device >
JayBlack_686 said:
Hi @Deuces, I wonder if you could take a look at this. I just tried running your script (third time so far). I used the latest Walleye script, made sure I had the latest fastboot and adb. Please see below...it looks like the script got as far as trying to write bootloader_b...then it got stuck at "waiting for any device" with the display blank. Eventually (after a long time) I gave up and unplugged the phone. I can't get it to turn on at ALL. Not by holding down power, not by using the key combo to get into fastboot...the phone just seems DEAD. I plug it into a charger, and nothing happens. Plug it back into PC, and the computer doesn't know that the phone has been plugged in. It's just not there in the Device Manager.
I tried following Google's steps to troubleshoot a phone that doesn't turn on. I did find that if I hold the power button down for about 30 seconds, I do feel the phone vibrate, and see a line across the display, like the few times that I've had to hard reboot. But that was it. Trying to get into fastboot mode, even holding the buttons for a long time, doesn't work.
Any idea what could have happened, or what I can do? The battery wasn't 100% full when I started, but it was at least at 85%. I'm sure the battery didn't die. I'm a bit freaked out, as I can't even get it to power on. Thanks in advance.
Deuces-flash-all-script-V4.3-Windows
for Walleye - Google Pixel 2
USE AT YOUR OWN RISK
Press any key to continue . . .
Make Sure your Device is in Fastboot Mode
(Power off, hold Volume-Down, hold Power)
Once you are in fastboot,
Press any key to continue . . .
Running Unlock
Look at your device,
press up arrow and Power to confirm
...
FAILED (remote: Device already : unlocked!)
finished. total time: 0.006s
This will say "failed" if already unlocked - ignore
Locating Bootloader and Radio Filenames
Flashing...
Setting current slot to 'a'...
OKAY [ 0.012s]
finished. total time: 0.014s
target reported max download size of 536870912 bytes
sending 'bootloader_a' (38644 KB)...
OKAY [ 1.189s]
writing 'bootloader_a'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 1.206s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
target reported max download size of 536870912 bytes
sending 'radio_a' (60428 KB)...
OKAY [ 1.851s]
writing 'radio_a'...
(bootloader) Updating: modem @00001000 sz=03B01000
OKAY [ 0.690s]
finished. total time: 2.545s
rebooting into bootloader...
OKAY [ 0.004s]
finished. total time: 0.005s
Setting current slot to 'b'...
OKAY [ 0.015s]
finished. total time: 0.017s
target reported max download size of 536870912 bytes
sending 'bootloader_b' (38644 KB)...
OKAY [ 1.051s]
writing 'bootloader_b'...
(bootloader) Updating: partition:0 @00002000 sz=0000B000
FAILED (remote: Command Flash Error)
finished. total time: 1.069s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.005s
< waiting for any device >
Click to expand...
Click to collapse
I've seen something similar as far as the phone not powering on. Technically tho, it was on but with a black screen.
Try holding VOL- and POWER for 30+ seconds to see if it powers off, then again to see if it comes back on.
I did read thoroughly and read that you've kinda tried this already, but after you get it to "power on" - do you get any return on the command:
fastboot devices
or
adb devices
?
Then, maybe try the new script i just updated - or tell me what OS you are running? if it's MAC / OSX, might wanna hold off.
Deuces said:
I've seen something similar as far as the phone not powering on. Technically tho, it was on but with a black screen.
Try holding VOL- and POWER for 30+ seconds to see if it powers off, then again to see if it comes back on.
I did read thoroughly and read that you've kinda tried this already, but after you get it to "power on" - do you get any return on the command:
fastboot devices
or
adb devices
?
Then, maybe try the new script i just updated - or tell me what OS you are running? if it's MAC / OSX, might wanna hold off.
Click to expand...
Click to collapse
Hi, thanks. I did try holding VOL - and power down for 30 seconds+. Actually, I did feel a vibration, but...nothing after. Couldn't get it to act like it was turning back on. Now that you mention it...I wonder if I did get it to turn on at some point during trying this over and over, because at times I saw the "scan line" appear across the screen briefly, like when I hard power off the device. But I've never seen the display light up at all, and nothing I've done has shown a device when issuing the "devices" command, either via fastboot or adb. I guess I need to screw around until I see that scan line, then it's "off." Then I've gotta get the thing to vibrate again, so it's "on." Then try seeing if I can run your script.
Boy am I glad I didn't try this late at night.
Oh, sorry, I'm on Windows 10.
Based on the return it looks like your bootloader got jacked up. I haven't seen that issue before. May want to get on chat with Google about an RMA.
Deuces said:
Based on the return it looks like your bootloader got jacked up. I haven't seen that issue before. May want to get on chat with Google about an RMA.
Click to expand...
Click to collapse
Sheeeeeeeit, just did that. Man...honestly, I might just go stock when I get this new one. Too much risk of mishaps, since I only keep the one phone around. Was just hoping to recover this one, as I'll be phone-less for a few days.
Side question - let's say I get the new phone, unlock the bootloader just in case, then don't do anything else, no rooting, etc. Do you know if that'll affect my ability to get OTAs actually over the air? I'm just bummed that every time there's an update, I've gotta go manually flash stuff and risk some shenanigans like this (and there's that persistent notification that doesn't go away unless I do so!). Should be easy, but I never had any luck with Google's flash-all script and always had to use yours to recover. Your script worked great...except for this time, something clearly went wrong (not pointing fingers, it's just how it goes).
Anyway, if you've got any other ideas, I'd try them out. Thanks for the responses thus far.
JayBlack_686 said:
Sheeeeeeeit, just did that. Man...honestly, I might just go stock when I get this new one. Too much risk of mishaps, since I only keep the one phone around. Was just hoping to recover this one, as I'll be phone-less for a few days.
Side question - let's say I get the new phone, unlock the bootloader just in case, then don't do anything else, no rooting, etc. Do you know if that'll affect my ability to get OTAs actually over the air? I'm just bummed that every time there's an update, I've gotta go manually flash stuff and risk some shenanigans like this (and there's that persistent notification that doesn't go away unless I do so!). Should be easy, but I never had any luck with Google's flash-all script and always had to use yours to recover. Your script worked great...except for this time, something clearly went wrong (not pointing fingers, it's just how it goes).
Anyway, if you've got any other ideas, I'd try them out. Thanks for the responses thus far.
Click to expand...
Click to collapse
If you can't get into bootloader, there's nothing I can do. There's some talk about using LG's downloader mode but LG has not released an image for it that I know of.
You can see this download mode by: Powered Off. Hold Vol+, insert USB cable connected from laptop.
If you have an unlocked bootloader, play store knows it - and some apps (netflix for example) - won't allow you to download their app from the play store. You could sideload the apk and it works fine, but still no updates from play store.. All of the apps I have work fine unlocked, minus Netflix.
You could disable OTA updates via developer options so that the notification goes away.
If you decide to stay stock, you could technically leave the bootloader locked, but the "allow oem unlocking" enabled in developer options. However, if something corrupts your OS, it's unlikely you'd be able to issue the unlocking commands from bootloader. That's the main reason I stay unlocked.
I've got the process down for upgrades myself. Download image, unzip, unzip the image within that, run my deuce-flash-all script. Boot up to Android once. Reboot to bootloader, fastboot boot twrp img, install magisk, reboot.
I do not flash twrp zip b/c it has been problematic for touchscreen drivers, and I'm around a computer anyway when doing these things.
The only reason I root is to use adaway. Every time I try to get used to stock, I hate using my phone because of ads.
I've tried the no-root-required VPN adblockers, but they drain battery.
Deuces said:
If you can't get into bootloader, there's nothing I can do.
...
If you have an unlocked bootloader, play store knows it - and some apps (netflix for example) - won't allow you to download their app from the play store. You could sideload the apk and it works fine, but still no updates from play store.. All of the apps I have work fine unlocked, minus Netflix.
...
The only reason I root is to use adaway. Every time I try to get used to stock, I hate using my phone because of ads.
I've tried the no-root-required VPN adblockers, but they drain battery.
Click to expand...
Click to collapse
Hey, thanks. I hear you. Oddly, I could've sworn that I had Netflix installed and updating on my bootloader-unlocked Pixel 2. Can't verify, sadly!
JayBlack_686 said:
Hey, thanks. I hear you. Oddly, I could've sworn that I had Netflix installed and updating on my bootloader-unlocked Pixel 2. Can't verify, sadly!
Click to expand...
Click to collapse
I can verify! I watch Netflix on my phone at work, downloaded from the play store on a pixel 2 unlocked, twrp installed and rooted with magisk. Not sure why everyone is having problems with it.

Can't Flash Factory Image.

Hey everyone,
So my Pixel 2 XL is kinda stuck at the moment. I'm having problems getting stock back up on my Pixel 2 XL, When I click onto flash-all command it does the job till it gets near the end of the process and then comes up with the error as 'Target didn't report max-download-size' I've used other factory images for the Pixel 2 XL CMD and the phone isn't having it at all. I really don't know what to do at this point. I need some kind of fix to this. Any advice would be really great.
** NEW ERROR **
target reported max download size of 536870912 bytes
sending 'bootloader' (36356 KB)...
OKAY [ 0.799s]
writing 'bootloader'...
OKAY [ 0.370s]
finished. total time: 1.169s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (60388 KB)...
OKAY [ 1.341s]
writing 'radio'...
OKAY [ 0.570s]
finished. total time: 1.911s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
error: failed to load 'image-taimen-pq2a.190405.003.zip': Not enough space
Press any key to exit...
When you say you flashed others and all was ok, what month are those images from? What I'm wondering is if you have out dated fastboot. Did you already update your platform tools? If not, do that and see if it works.
I usually run into this issue if I don't have enough free space on my C drive (at least 4 GBs; the system partition image is around 2 GBs...). And if it's not the free space issue, usually it's merely just a change/re-initialization of the USB cord. Make sure you have the latest platform-tools (r28.0.2 is the most up-to-date version) as well as using a USB-C to USB-A cord (USB-C to USB-C seems to cause endless amount of issues and is usually the root cause for random unknown reasons...)...it usually sets things up right to work the next time around.
But, if making sure of all the previous things, and you restarted your phone and computer already, then you might try re-downloading the Full Factory image and extracting it once again (don't forget to re-edit the .bat/.sh file to not include the "-w" attribute); and consider even going through the trouble of comparing checksums to make sure you are getting/using the exact proper copy of the factory image...
good luck to you and hope this helps...
Fe Mike said:
When you say you flashed others and all was ok, what month are those images from? What I'm wondering is if you have out dated fastboot. Did you already update your platform tools? If not, do that and see if it works.
Click to expand...
Click to collapse
I uninstalled and reinstalled fastboot, re-downloaded platform tools and reinstalled all drivers. I downloaded the factory file straight from google which was the android 9.0 April 2019 update. Yet I'm still having this problem. It was working fine yesterday as I went to reboot it, it just went straight into a bootloop. The phone was rooted via magisk.
So I got a new error now and fastboot is telling me that there is not enough space to load the zip file. Everything is extracted out of the image zip file and moved into the adb folder
Finally Solved the problem! So I booted the phone into its stock recovery and pushed the adb zip file through and then after waiting for 20 minutes I rebooted the phone and its booted into its stock rom. Thanks everyone!
Knxed_ said:
Finally Solved the problem! So I booted the phone into its stock recovery and pushed the adb zip file through and then after waiting for 20 minutes I rebooted the phone and its booted into its stock rom. Thanks everyone!
Click to expand...
Click to collapse
You can boot twrp and flash the ota as well

Categories

Resources