Develop Bugs

[Q] Nexus 7 stuck on Google Logo! Confused

I realize this has been discussed ad nauseam and after searching through all the posts on it I am a little confused about what my options are. My Nexus 7 2013 mobile is stuck on the Google logo. Here's what I have done..
First, I tried to simply wipe the cache partition to no avail.
Second, using the WugFresh Nexus toolkit I tried to unroot and flash stock to no avail. It would get to the point of flashing I would get remote failure error messages when trying to flash the radio etc,
Basically, all I have at this point, is the Google screen and access to fastboot and it's options and the Nexus is recognized by my computer through fastboot.
What are my options now?
Should I relock the bootloader and request Google repair it?
Or should I try to flash 4.4.4 manually through fastboot without a toolkit. If so, can you refresh my memory on how to do this?
I would appreciate any help you could provide. Thanks!

Try flashing 4.4.4 manually in fastboot. There are instructions on the page where you download the firmware. Did you flash 5.0 on a LTE model?

I did not flash 5.0. It froze during usage and I restarted it and then it suddenly would not boot past the Google logo. I did nothing to it.
I downloaded the factory image for 4.4.4 and followed instructions and ran the flash-all.bat and here is what the command prompt returns:
< waiting for device >
sending 'bootloader' (3911 KB)...
OKAY [ 0.152s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.709s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
sending 'radio' (76038 KB)...
OKAY [ 3.034s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 174.608s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
Is it time to relock the bootloader and hope Google will repair it?

Flashing stock 5.0.2, boot.img "missing"

I'm trying to flash the stock ROM for 5.0.2, and when I try to run the flash-all script, I get an error saying that boot.img is missing. I looked into the zip file where the bat file is looking, and there is definitely a boot.img there. I just updated platform-tools through the SDK manager a few hours ago, so I'm using the newest version.
Full output from flash-all:
Code:
sending 'bootloader' (3911 KB)...
OKAY [ 0.132s]
writing 'bootloader'...
OKAY [ 1.553s]
finished. total time: 1.685s
rebooting into bootloader...
OKAY [ 0.008s]
finished. total time: 0.009s
error: update package missing boot.img
Press any key to exit...

Flash the files manually?

nhizzat said:
Flash the files manually?
Click to expand...
Click to collapse
Sorry for abandoning this thread. I flashed the boot and system images manually and it seemed to work. Thanks!

Boot loop after flashing 5.1

Guy Hi. I *really* need help....
I have a rooted nexus 7 2013 running stock 4.4.4. 1 tried flashing the 5.1 factory image and now have what I think is a bootloop. Here's what I did :
1. Downloaded the razor 5.1.1 factory image (LMY47V) from
https://developers.google.com/android/nexus/images
to my windows 8.1 laptop
2. Modified the flash-all.bat to remove the -w so it says "fastboot update image-&.zip"
3. I already had adb and fastboot installed on my windows laptop
4. I restarted my nexus 7 2013 into recovery, fastboot mode
5. Connected the N7 to the laptop
6. Ran the modified flash-all.bat.
Here's what appeared in the command window:
........
sending 'bootloader' (3911 KB)...
OKAY [ 0.132s]
writing 'bootloader'...
OKAY [ 1.421s]
finished. total time: 1.556s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Bootloader Version...: FLO-04.05
Baseband Version.....: none
Serial Number........: 0865c8bf
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
sending 'boot' (7204 KB)...
OKAY [ 0.232s]
writing 'boot'...
OKAY [ 0.414s]
sending 'recovery' (7810 KB)...
OKAY [ 0.252s]
writing 'recovery'...
OKAY [ 0.298s]
erasing 'system'...
OKAY [ 1.362s]
sending 'system' (822862*KB)...
OKAY [ 25.772s]
writing 'system'...
OKAY [ 37.979s]
rebooting...
finished. total time: 66.351s
Press any key to exit...
...........
The nexus 7 2013 went into the Google boot up image sequence with the rotating flashing lights, but they are different from the kitkat lights.
Trouble is they keep repeating forever without fully booting.
I can exit by pressing "power down + power" and I can reenter recovery mode by again pressing "power down + power", but I cannot fully bootup and cannot enter my TWRP.
What should I do to finish flashing 5.1.1?
And then to regain root? What did I do wrong?
Please help. Thank you.

Anderson2 said:
Guy Hi. I *really* need help....
I have a rooted nexus 7 2013 running stock 4.4.4. 1 tried flashing the 5.1 factory image and now have what I think is a bootloop. Here's what I did :
1. Downloaded the razor 5.1.1 factory image (LMY47V) from
https://developers.google.com/android/nexus/images
to my windows 8.1 laptop
2. Modified the flash-all.bat to remove the -w so it says "fastboot update image-&.zip"
3. I already had adb and fastboot installed on my windows laptop
4. I restarted my nexus 7 2013 into recovery, fastboot mode
5. Connected the N7 to the laptop
6. Ran the modified flash-all.bat.
Here's what appeared in the command window:
........
sending 'bootloader' (3911 KB)...
OKAY [ 0.132s]
writing 'bootloader'...
OKAY [ 1.421s]
finished. total time: 1.556s
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.007s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Bootloader Version...: FLO-04.05
Baseband Version.....: none
Serial Number........: 0865c8bf
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
sending 'boot' (7204 KB)...
OKAY [ 0.232s]
writing 'boot'...
OKAY [ 0.414s]
sending 'recovery' (7810 KB)...
OKAY [ 0.252s]
writing 'recovery'...
OKAY [ 0.298s]
erasing 'system'...
OKAY [ 1.362s]
sending 'system' (822862*KB)...
OKAY [ 25.772s]
writing 'system'...
OKAY [ 37.979s]
rebooting...
finished. total time: 66.351s
Press any key to exit...
...........
The nexus 7 2013 went into the Google boot up image sequence with the rotating flashing lights, but they are different from the kitkat lights.
Trouble is they keep repeating forever without fully booting.
I can exit by pressing "power down + power" and I can reenter recovery mode by again pressing "power down + power", but I cannot fully bootup and cannot enter my TWRP.
What should I do to finish flashing 5.1.1?
And then to regain root? What did I do wrong?
Please help. Thank you.
Click to expand...
Click to collapse
Go into stock recovery and perform a factory reset. If it still doesn't boot, flash the factory image one part at a time. Flash all scripts can act wonky sometimes.
Sent from my SPH-L720 using Tapatalk

Thank you. Will do a factory reset.
Can you explain what you mean by "flash the factory image one part at a time"? How do I do that?
Thanks again.

OK. Got to the factory reset screen and wiped all data. Reflashed 5.1.1 and now booted up.

Anderson2 said:
OK. Got to the factory reset screen and wiped all data. Reflashed 5.1.1 and now booted up.
Click to expand...
Click to collapse
I'm experiencing this or at least a very similar issue and factory reset doesn't help. I flashed the factory 4.4.4 image and it boots up OK. I then allowed the OTA to upgrade 5.02 and yet when that completed flashing and rebooted I get the same thing, boots to 4 spinning colored globes and hangs. Any way to see what's happening here or other suggestions? Thanks!
Edit to add: I first flashed 5.1.1 and get the 4 spinning globes. Factory reset, same. Flash to 4.4.4 and it works. Upgrade to 5.02, back to spinning balls.

HELP Can't flash system.img

Hey
when i want to flash the factory image from google with the "flash-all.bat" i got this Error.
failed to allocate 2008772888 bytes
error: update package missing system.img
i tried to flash manualy dosent work too.
J:\fastboot\bullhead-mmb29p>fastboot flash system system.img
load_file: could not allocate 2008772888 bytes
error: cannot load 'system.img'
this comes when i run the "flash-all.bat"
sending 'bootloader' (4382 KB)...
OKAY [ 0.213s]
writing 'bootloader'...
OKAY [ 0.137s]
finished. total time: 0.352s
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.012s
sending 'radio' (56614 KB)...
OKAY [ 1.807s]
writing 'radio'...
OKAY [ 0.506s]
finished. total time: 2.315s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.004s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 2008772888 bytes
error: update package missing system.img
Press any key to exit...
please help me:crying:

use newest fastboot. Had the same failure on Nexus 9 - flounder.

Donald Nice said:
use newest fastboot. Had the same failure on Nexus 9 - flounder.
Click to expand...
Click to collapse
many many thanks :good:
you safed the life from my 5x ♥

Donald Nice said:
use newest fastboot. Had the same failure on Nexus 9 - flounder.
Click to expand...
Click to collapse
Hello, sorry for my English, i've download the Minimal fastboot and adb file and i've installated it. but it styll doesn't work, when i try to type te command: fastboot flash system system.img, the result is error: cannot load system.img. what can i try to do?

Download and install SDK Manager. Later, install SDK tools, SDK Platform Tools, Android support library and Google USB driver. Then try again.

Stuck on TWRP after accidental factory reset

I was about to manually install the lineageOS update, but I accidentally swiped factory restore. Is there anyway I can get the update file online? I tried starting from the top by wiping everything and reinstalling the rom but it only boots me into TWRP. I also tried restoring backup files but is also boots me into TWRP. I am stuck.
PS: I tried the "fastboot continue" method but it boots me into TWRP.

reboot to fastboot mode. flash stock bootloader and recovery. reboot in stock recovery and then factory reset device and sideload firmware. alternatively you can flash raw firmware manually

sukhwant717 said:
reboot to fastboot mode. flash stock bootloader and recovery. reboot in stock recovery and then factory reset device and sideload firmware. alternatively you can flash raw firmware manually
Click to expand...
Click to collapse
Thank you for your response, Sir. I really appreciate it. Where do I get the stock bootloader and recovery, and how do I flash them? On the alternative method, do you mean I should install the stock rom? I'm sorry. I'm really not good at this; I'm just good at following tutorials. Is this what you're suggesting me to do? (XDA is now allowing me to write outside links. But here is the title of the tutorial from Asus Zentalk)
"[Experience Sharing] How to Relock Bootloader on ZenFone 2(ZE551ML ONLY)"
I have made a backup before I intalled the Lineage OS custom Rom. Can I use that instead of downloading new files, because the internet here is really bad. My problem is how I am going to install it. I tried restoring it but I keep on coming back to the TWRP.
Edit: I am now downloading the stock boot.img and recovery.img. I will be flashing them with ADB the ADB tool. Is this what you want to tell me? Then I will reboot in stock recovery, select factory reset and sideload firmware. I honestly don't get the "sideload firmware" part but can I use the one that I have backed up? How?

lemuelermita said:
Thank you for your response, Sir. I really appreciate it. Where do I get the stock bootloader and recovery, and how do I flash them? On the alternative method, do you mean I should install the stock rom? I'm sorry. I'm really not good at this; I'm just good at following tutorials. Is this what you're suggesting me to do? (XDA is now allowing me to write outside links. But here is the title of the tutorial from Asus Zentalk)
"[Experience Sharing] How to Relock Bootloader on ZenFone 2(ZE551ML ONLY)"
I have made a backup before I intalled the Lineage OS custom Rom. Can I use that instead of downloading new files, because the internet here is really bad. My problem is how I am going to install it. I tried restoring it but I keep on coming back to the TWRP.
Edit: I am now downloading the stock boot.img and recovery.img. I will be flashing them with ADB the ADB tool. Is this what you want to tell me? Then I will reboot in stock recovery, select factory reset and sideload firmware. I honestly don't get the "sideload firmware" part but can I use the one that I have backed up? How?
Click to expand...
Click to collapse
the backup you made you can flash only via twrp. if you have backup simply install it in twrp. but if still bootloops then you have to download firmware either from asus website or raw firmware from any other source. first try to flash backup in twrp. if you are unable to get into system them report back here. i will send you link to download raw firmware and instructions how to flash

sukhwant717 said:
the backup you made you can flash only via twrp. if you have backup simply install it in twrp. but if still bootloops then you have to download firmware either from asus website or raw firmware from any other source. first try to flash backup in twrp. if you are unable to get into system them report back here. i will send you link to download raw firmware and instructions how to flash
Click to expand...
Click to collapse
I tried to flash the backup but still no luck. Yes, please. Thank you very much!
I'm currently downloading the "CleanSTOCK-MM.223-v3.8[STABLE][Z00A]-6 May". I hope this will fix the problem. Do you think this will work 100%? I am afraid that it will boot again to TWRP after installing another rom. Which do you think is more efficient, installing a new rom or installing raw firmware?

lemuelermita said:
I tried to flash the backup but still no luck. Yes, please. Thank you very much!
I'm currently downloading the "CleanSTOCK-MM.223-v3.8[STABLE][Z00A]-6 May". I hope this will fix the problem. Do you think this will work 100%? I am afraid that it will boot again to TWRP after installing another rom. Which do you think is more efficient, installing a new rom or installing raw firmware?
Click to expand...
Click to collapse
raw is definitely best option. are you able to mount data and cache partition in TWRP

sukhwant717 said:
raw is definitely best option. are you able to mount data and cache partition in TWRP
Click to expand...
Click to collapse
I haven't tried that yet. How do I do that? Can you send me the links and instructions needed?

sukhwant717 said:
raw is definitely best option. are you able to mount data and cache partition in TWRP
Click to expand...
Click to collapse
Defensively smartest guy about phones in the world!!! ahaha <3

lemuelermita said:
I haven't tried that yet. How do I do that? Can you send me the links and instructions needed?
Click to expand...
Click to collapse
go to the following guide. see the section flash firmware without AFT and follow the instructions. keep in mind run each and every command even if any of them fails.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785

sukhwant717 said:
go to the following guide. see the section flash firmware without AFT and follow the instructions. keep in mind run each and every command even if any of them fails.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
Thank you very much, Sir! I will give you an update soon.

lemuelermita said:
Thank you very much, Sir! I will give you an update soon.
Click to expand...
Click to collapse
Followed the instructions on the link but my phone boots up on a blinking screen with an android saying "Error". The command prompt failed at steps 4,5, and 11.
C:\Users\Lemuel\Documents\RESTOCK>fastboot devices
F5AZFG14A156 fastboot
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem erase_osip_header
...
OKAY [ 0.217s]
finished. total time: 0.219s
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem start_partitioning
...
(bootloader) Start partitioning
OKAY [ 0.228s]
finished. total time: 0.231s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash /tmp/partition.tbl partition.tbl
target reported max download size of 536870912 bytes
sending '/tmp/partition.tbl' (2 KB)...
OKAY [ 0.194s]
writing '/tmp/partition.tbl'...
FAILED (remote: not allowed to flash this partition)
finished. total time: 0.384s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash /tmp/partition.tbl partition.tbl
target reported max download size of 536870912 bytes
sending '/tmp/partition.tbl' (2 KB)...
OKAY [ 0.205s]
writing '/tmp/partition.tbl'...
FAILED (remote: not allowed to flash this partition)
finished. total time: 0.394s
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem partition /tmp/partition.tbl
...
FAILED (remote: unknown OEM command)
finished. total time: 0.127s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase system
******** Did you mean to fastboot format this ext4 partition?
erasing 'system'...
OKAY [ 0.560s]
finished. total time: 0.561s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase cache
******** Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
OKAY [ 0.232s]
finished. total time: 0.234s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase data
******** Did you mean to fastboot format this ext4 partition?
erasing 'data'...
OKAY [ 1.447s]
finished. total time: 1.448s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase APD
******** Did you mean to fastboot format this ext4 partition?
erasing 'APD'...
OKAY [ 0.290s]
finished. total time: 0.294s
C:\Users\Lemuel\Documents\RESTOCK>fastboot erase ADF
******** Did you mean to fastboot format this ext4 partition?
erasing 'ADF'...
OKAY [ 0.232s]
finished. total time: 0.234s
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem wipe splashscreen
...
FAILED (remote: unknown OEM command)
finished. total time: 0.127s
C:\Users\Lemuel\Documents\RESTOCK>fastboot oem stop_partitioning
...
(bootloader) Stop partitioning
OKAY [ 0.210s]
finished. total time: 0.212s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash splashscreen splash_sign.bin
target reported max download size of 536870912 bytes
sending 'splashscreen' (270 KB)...
OKAY [ 0.192s]
writing 'splashscreen'...
OKAY [ 0.236s]
finished. total time: 0.431s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash token MFG_BOM_Full.bin
target reported max download size of 536870912 bytes
sending 'token' (3 KB)...
OKAY [ 0.194s]
writing 'token'...
OKAY [ 0.370s]
finished. total time: 0.566s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash ifwi ifwi-prod.bin
target reported max download size of 536870912 bytes
sending 'ifwi' (4096 KB)...
OKAY [ 0.294s]
writing 'ifwi'...
OKAY [ 1.027s]
finished. total time: 1.326s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash boot boot_sign.bin
target reported max download size of 536870912 bytes
sending 'boot' (11870 KB)...
OKAY [ 0.531s]
writing 'boot'...
OKAY [ 0.648s]
finished. total time: 1.182s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash recovery recovery_sign.bin
target reported max download size of 536870912 bytes
sending 'recovery' (11882 KB)...
OKAY [ 0.520s]
writing 'recovery'...
OKAY [ 0.636s]
finished. total time: 1.163s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash fastboot droidboot_sign.bin
target reported max download size of 536870912 bytes
sending 'fastboot' (14824 KB)...
OKAY [ 0.558s]
writing 'fastboot'...
OKAY [ 0.739s]
finished. total time: 1.302s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash APD APD.img
target reported max download size of 536870912 bytes
erasing 'APD'...
OKAY [ 0.204s]
sending 'APD' (183963 KB)...
OKAY [ 4.927s]
writing 'APD'...
OKAY [ 0.912s]
finished. total time: 6.049s
C:\Users\Lemuel\Documents\RESTOCK>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.233s]
sending sparse 'system' 1/5 (518551 KB)...
OKAY [ 27.274s]
writing 'system' 1/5...
OKAY [ 5.563s]
sending sparse 'system' 2/5 (523662 KB)...
OKAY [ 22.886s]
writing 'system' 2/5...
OKAY [ 6.964s]
sending sparse 'system' 3/5 (520607 KB)...
OKAY [ 24.630s]
writing 'system' 3/5...
OKAY [ 8.077s]
sending sparse 'system' 4/5 (500735 KB)...
OKAY [ 23.704s]
writing 'system' 4/5...
OKAY [ 7.983s]
sending sparse 'system' 5/5 (188368 KB)...
OKAY [ 8.849s]
writing 'system' 5/5...
OKAY [ 1.187s]
finished. total time: 137.827s
C:\Users\Lemuel\Documents\RESTOCK>
C:\Users\Lemuel\Documents\RESTOCK>
C:\Users\Lemuel\Documents\RESTOCK>fastboot reboot
rebooting...
finished. total time: 0.126s

lemuelermita said:
Thank you very much, Sir! I will give you an update soon.
Click to expand...
Click to collapse
The command prompt failed at steps 4,5, and 11. It only boots in a blinking screen with an android saying, "Error". Tried it again for the second time but still boots in same screen. I tried to manually boot up the phone without the commands and worked. Thank you very much!

lemuelermita said:
The command prompt failed at steps 4,5, and 11. It only boots in a blinking screen with an android saying, "Error". Tried it again for the second time but still boots in same screen. I tried to manually boot up the phone without the commands and worked. Thank you very much!
Click to expand...
Click to collapse
hmm good to know device working again. strongly recommend you to perform a factory reset even device working perfectly.