Develop Bugs

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.

Problems flashing system images for the Pixel XL

So I'm pretty accustomed to flashing system images and sideloading OTAs, but for some reason things are just not working for me on my Pixel XL.
Every time I run the "flash-all.bat" script (with the -w removed to preserve data) I can never seem to update properly, I get the following:
Code:
target reported max download size of 536870912 bytes
sending 'bootloadera' (32820 KB)...
OKAY [ 0.776s]
writing 'bootloadera'...
(bootloader) Valid bootloader version.
OKAY [ 1.064s]
finished. total time: 1.844s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 5.009s
target reported max download size of 536870912 bytes
sending 'radioa' (57048 KB)...
OKAY [ 1.356s]
writing 'radioa'...
OKAY [ 0.952s]
finished. total time: 2.322s
rebooting into bootloader...
OKAY [ 0.014s]
finished. total time: 0.015s
< waiting for any device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
--------------------------------------------
Bootloader Version...: 8996-012001-1608281716
Baseband Version.....: 8996-012511-1609191801
Serial Number........: [removed]
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.049s]
checking version-baseband...
OKAY [ 0.048s]
sending 'boota' (26405 KB)...
OKAY [ 0.680s]
writing 'boota'...
(bootloader) Flashing active slot "_a"
FAILED (remote: partition [boota] doesn't exist)
finished. total time: 1.139s
Press any key to exit...
I am on the original stock NDE63L, and I have had failures trying to flash both NDE63P (a few weeks ago) and NDE63X (today's build).
Additionally, ever since this process has failed for me, I am unable to boot into recovery, I just get the picture of the dead Android guy. So because of this I can't adb sideload the OTA as an alternative.
My bootloader is unlocked and I have rooted just fine, boot_a is listed as my active boot slot, but I have no idea why the system flash keeps failing.
Any thoughts as to why this is happening? Alternatively, is there a way to restore my recovery so I can try adb sideloading the OTA?

ChrisG683 said:
So I'm pretty accustomed to flashing system images and sideloading OTAs, but for some reason things are just not working for me on my Pixel XL.
Every time I run the "flash-all.bat" script (with the -w removed to preserve data) I can never seem to update properly, I get the following:
Code:
target reported max download size of 536870912 bytes
sending 'bootloadera' (32820 KB)...
OKAY [ 0.776s]
writing 'bootloadera'...
(bootloader) Valid bootloader version.
OKAY [ 1.064s]
finished. total time: 1.844s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 5.009s
target reported max download size of 536870912 bytes
sending 'radioa' (57048 KB)...
OKAY [ 1.356s]
writing 'radioa'...
OKAY [ 0.952s]
finished. total time: 2.322s
rebooting into bootloader...
OKAY [ 0.014s]
finished. total time: 0.015s
< waiting for any device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
--------------------------------------------
Bootloader Version...: 8996-012001-1608281716
Baseband Version.....: 8996-012511-1609191801
Serial Number........: [removed]
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.049s]
checking version-baseband...
OKAY [ 0.048s]
sending 'boota' (26405 KB)...
OKAY [ 0.680s]
writing 'boota'...
(bootloader) Flashing active slot "_a"
FAILED (remote: partition [boota] doesn't exist)
finished. total time: 1.139s
Press any key to exit...
I am on the original stock NDE63L, and I have had failures trying to flash both NDE63P (a few weeks ago) and NDE63X (today's build).
Additionally, ever since this process has failed for me, I am unable to boot into recovery, I just get the picture of the dead Android guy. So because of this I can't adb sideload the OTA as an alternative.
My bootloader is unlocked and I have rooted just fine, boot_a is listed as my active boot slot, but I have no idea why the system flash keeps failing.
Any thoughts as to why this is happening? Alternatively, is there a way to restore my recovery so I can try adb sideloading the OTA?
Click to expand...
Click to collapse
update ADB and Fastboot to latest version 1.0.3.6 release

Try the steps in my restore-to-stock thread?
I've used these steps twice for "L" and once for "V" builds.
No issues yet.
http://forum.xda-developers.com/pix...stock-soft-t3494478/post69476498#post69476498
---------- Post added at 03:09 PM ---------- Previous post was at 03:07 PM ----------
Oh, I remember getting that "boota does not exist".
I think I edited the script file somehow to fix that.
Can't remember what it was just now.
---------- Post added at 03:10 PM ---------- Previous post was at 03:09 PM ----------
Yours says "sending 'bootloadera'"
But mine that work says "sending 'bootloader_a'".
That may be the edit I did at one point.
But I have not had to edit anything while using the steps listed in my thread I linked to.

Taebom said:
update ADB and Fastboot to latest version 1.0.3.6 release
Click to expand...
Click to collapse
That seems to have done the trick, thank you so much!

Nexus 7 2013 LTE bootloop, can't enter Recovery mode; flash write failure

My Nexus 7 2013 LTE was rooted and updated to stock Android 6.0 a year ago, no 3rd party ROM/recovery is installed. Last week while checking emails, it rebooted suddenly then remained at Google letters and unlock icon, I can enter fastboot mode by pressing power and volume- buttons together, the last line shows status unlocked; then if select "Recovery mode", it reboots then shows a dead robot with an exclamation mark only. I downloaded the latest factory image "razorg-mob30x", connect it to my PC and enter adb command "flash-all.bat" (I modified the bat file by removing -w, so it won't wipe the user data), then it shows: FAILED (remote: flash write failure)
sending 'bootloader' (3915 KB)...
OKAY [ 0.135s]
writing 'bootloader' ...
FAILED (remote: flash write failure)
finished. total time 90.811s
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time 0.012s
sending 'radio' (76038 KB)...
OKAY [ 2.393s]
writing 'radio' ...
FAILED (remote: flash write failure)
finished. total time 92.549s
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time 0.013s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
----------------------------------------------------
Bootloader Version...: FLO-04.08
Basedband Version...: DEB-Z00_2.44.0_0213
Serial Number................: 0879222a
----------------------------------------------------
checking product...
OKAY [ 0.005s]
checking version-bootloader...
OKAY [ 0.006s]
checking version-baseband...
OKAY [ 0.006s]
sending 'boot' (7422 KB)
OKAY [ 0.243s]
writing 'boot' ...
FAILED (remote: flash write failure)
finished. total time 90.151s
Press any key to exit...
Click to expand...
Click to collapse
What else I can do to resuce my pad? Does this mean the memory is physically damaged?
Please advise. Your help is much appreciated.

Bad motherboard, just had to replace mine with exact issue.

My Robin Completely Bricked

Hi All
I bought this phone 3 months ago, and started to use it last week. I started the phone up got the notification of Nougat update and started the upgrade this is before even signing in . In the middle of one of the updates the phone shut down, started it back up and it booted into recovery. I have tried to boot into the system about 3 times and same thing it boots into recovery. Tried to factory reset it and reboot into system bad luck.
Downloaded the firmware 6.xx and 7.xx tried to flash both of them, but I was going no where, spent few hours trying to do that till I realised that.
1- USB Debugging was disabled.
2- Bootloader was still locked.
So I am completely screwed. I have tried the Unbrick Tool and still no luck the phone has been stuck on "sending segment 1 of 'system' (2475972 KB)..." for over an hour. What is surprising it shows in the logs below that it has successfully flashed recovery.
HTML:
C:\Users\Mahmoud\Downloads\Compressed\1350\1350>flash-all.bat
Do you wish to wipe the device when flashing?(Y/N): Y
sending 'partition' (34 KB)...
OKAY [ 0.020s]
writing 'partition'...
OKAY [ 0.021s]
finished. total time: 0.049s
sending 'sbl1' (479 KB)...
OKAY [ 0.030s]
writing 'sbl1'...
OKAY [ 0.021s]
finished. total time: 0.057s
sending 'sbl1bak' (479 KB)...
OKAY [ 0.030s]
writing 'sbl1bak'...
OKAY [ 0.021s]
finished. total time: 0.059s
sending 'aboot' (701 KB)...
OKAY [ 0.030s]
writing 'aboot'...
OKAY [ 0.021s]
finished. total time: 0.055s
sending 'abootbak' (701 KB)...
OKAY [ 0.030s]
writing 'abootbak'...
OKAY [ 0.021s]
finished. total time: 0.056s
sending 'rpm' (188 KB)...
OKAY [ 0.020s]
writing 'rpm'...
OKAY [ 0.021s]
finished. total time: 0.045s
sending 'rpmbak' (188 KB)...
OKAY [ 0.020s]
writing 'rpmbak'...
OKAY [ 0.021s]
finished. total time: 0.047s
sending 'tz' (561 KB)...
OKAY [ 0.030s]
writing 'tz'...
OKAY [ 0.020s]
finished. total time: 0.056s
sending 'tzbak' (561 KB)...
OKAY [ 0.030s]
writing 'tzbak'...
OKAY [ 0.020s]
finished. total time: 0.055s
sending 'hyp' (93 KB)...
OKAY [ 0.020s]
writing 'hyp'...
OKAY [ 0.021s]
finished. total time: 0.049s
sending 'hypbak' (93 KB)...
OKAY [ 0.020s]
writing 'hypbak'...
OKAY [ 0.021s]
finished. total time: 0.045s
sending 'sdi' (28 KB)...
OKAY [ 0.020s]
writing 'sdi'...
OKAY [ 0.021s]
finished. total time: 0.046s
sending 'pmic' (37 KB)...
OKAY [ 0.020s]
writing 'pmic'...
OKAY [ 0.021s]
finished. total time: 0.046s
sending 'pmicbak' (37 KB)...
OKAY [ 0.020s]
writing 'pmicbak'...
OKAY [ 0.021s]
finished. total time: 0.046s
sending 'hwcfg' (1 KB)...
OKAY [ 0.020s]
writing 'hwcfg'...
OKAY [ 0.021s]
finished. total time: 0.045s
sending 'bluetooth' (450 KB)...
OKAY [ 0.020s]
writing 'bluetooth'...
OKAY [ 0.021s]
finished. total time: 0.046s
sending 'keymaster' (148 KB)...
OKAY [ 0.020s]
writing 'keymaster'...
OKAY [ 0.021s]
finished. total time: 0.046s
sending 'cmnlib' (165 KB)...
OKAY [ 0.020s]
writing 'cmnlib'...
OKAY [ 0.021s]
finished. total time: 0.045s
sending 'splash' (6075 KB)...
OKAY [ 0.141s]
writing 'splash'...
OKAY [ 0.020s]
finished. total time: 0.166s
sending 'splash2' (6075 KB)...
OKAY [ 0.141s]
writing 'splash2'...
OKAY [ 0.020s]
finished. total time: 0.167s
sending 'persist' (4673 KB)...
OKAY [ 0.120s]
writing 'persist'...
OKAY [ 0.020s]
finished. total time: 0.144s
sending 'modem' (78615 KB)...
OKAY [ 1.729s]
writing 'modem'...
OKAY [ 0.013s]
finished. total time: 1.746s
sending 'cust_nv' (301 KB)...
OKAY [ 0.030s]
writing 'cust_nv'...
OKAY [ 0.021s]
finished. total time: 0.053s
sending 'systeminfo' (4 KB)...
OKAY [ 0.020s]
writing 'systeminfo'...
OKAY [ 0.021s]
finished. total time: 0.043s
sending 'KEY_INFO' (1 KB)...
OKAY [ 0.020s]
writing 'KEY_INFO'...
OKAY [ 0.021s]
finished. total time: 0.045s
sending 'hidden' (9319 KB)...
OKAY [ 0.211s]
writing 'hidden'...
OKAY [ 0.020s]
finished. total time: 0.235s
sending 'sutinfo' (1 KB)...
OKAY [ 0.020s]
writing 'sutinfo'...
OKAY [ 0.021s]
finished. total time: 0.044s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
< waiting for device >
sending 'recovery' (12794 KB)...
OKAY [ 0.291s]
writing 'recovery'...
OKAY [ 0.020s]
finished. total time: 0.320s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.003s
< waiting for device >
sending 'boot' (11746 KB)...
OKAY [ 0.281s]
writing 'boot'...
OKAY [ 0.019s]
finished. total time: 0.306s
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time: 0.011s
< waiting for device >
simu_flash:971f0dec:system
sending segment 1 of 'system' (2475972 KB)...
I tried to fool the device and downloaded twrp and named it recovery.img and placed within the same directory and again it said it was flashed as you see above, and when I tried to boot into recovery it was still the stock one.
Sadly I can't return my phone and Amazon is refusing to take it back since it was past the 30 days so I can't file an A-Z claim. I hope someone can help and giving me an idea of how to unlock the bootloader so at least I can flash stock again.
Cheers

vampire_8_7 said:
Hi All
I bought this phone 3 months ago, and started to use it last week. I started the phone up got the notification of Nougat update and started the upgrade this is before even signing in . In the middle of one of the updates the phone shut down, started it back up and it booted into recovery. I have tried to boot into the system about 3 times and same thing it boots into recovery. Tried to factory reset it and reboot into system bad luck.
Downloaded the firmware 6.xx and 7.xx tried to flash both of them, but I was going no where, spent few hours trying to do that till I realised that.
1- USB Debugging was disabled.
2- Bootloader was still locked.
So I am completely screwed. I have tried the Unbrick Tool and still no luck the phone has been stuck on "sending segment 1 of 'system' (2475972 KB)..." for over an hour. What is surprising it shows in the logs below that it has successfully flashed recovery.
C:\Users\Mahmoud\Downloads\Compressed\1350\1350>flash-all.batDo you wish to wipe the device when flashing?(Y/N): Ysending 'partition' (34 KB)...OKAY [ 0.020s]writing 'partition'...OKAY [ 0.021s]finished. total time: 0.049ssending 'sbl1' (479 KB)...OKAY [ 0.030s]writing 'sbl1'...OKAY [ 0.021s]finished. total time: 0.057ssending 'sbl1bak' (479 KB)...OKAY [ 0.030s]writing 'sbl1bak'...OKAY [ 0.021s]finished. total time: 0.059ssending 'aboot' (701 KB)...OKAY [ 0.030s]writing 'aboot'...OKAY [ 0.021s]finished. total time: 0.055ssending 'abootbak' (701 KB)...OKAY [ 0.030s]writing 'abootbak'...OKAY [ 0.021s]finished. total time: 0.056ssending 'rpm' (188 KB)...OKAY [ 0.020s]writing 'rpm'...OKAY [ 0.021s]finished. total time: 0.045ssending 'rpmbak' (188 KB)...OKAY [ 0.020s]writing 'rpmbak'...OKAY [ 0.021s]finished. total time: 0.047ssending 'tz' (561 KB)...OKAY [ 0.030s]writing 'tz'...OKAY [ 0.020s]finished. total time: 0.056ssending 'tzbak' (561 KB)...OKAY [ 0.030s]writing 'tzbak'...OKAY [ 0.020s]finished. total time: 0.055ssending 'hyp' (93 KB)...OKAY [ 0.020s]writing 'hyp'...OKAY [ 0.021s]finished. total time: 0.049ssending 'hypbak' (93 KB)...OKAY [ 0.020s]writing 'hypbak'...OKAY [ 0.021s]finished. total time: 0.045ssending 'sdi' (28 KB)...OKAY [ 0.020s]writing 'sdi'...OKAY [ 0.021s]finished. total time: 0.046ssending 'pmic' (37 KB)...OKAY [ 0.020s]writing 'pmic'...OKAY [ 0.021s]finished. total time: 0.046ssending 'pmicbak' (37 KB)...OKAY [ 0.020s]writing 'pmicbak'...OKAY [ 0.021s]finished. total time: 0.046ssending 'hwcfg' (1 KB)...OKAY [ 0.020s]writing 'hwcfg'...OKAY [ 0.021s]finished. total time: 0.045ssending 'bluetooth' (450 KB)...OKAY [ 0.020s]writing 'bluetooth'...OKAY [ 0.021s]finished. total time: 0.046ssending 'keymaster' (148 KB)...OKAY [ 0.020s]writing 'keymaster'...OKAY [ 0.021s]finished. total time: 0.046ssending 'cmnlib' (165 KB)...OKAY [ 0.020s]writing 'cmnlib'...OKAY [ 0.021s]finished. total time: 0.045ssending 'splash' (6075 KB)...OKAY [ 0.141s]writing 'splash'...OKAY [ 0.020s]finished. total time: 0.166ssending 'splash2' (6075 KB)...OKAY [ 0.141s]writing 'splash2'...OKAY [ 0.020s]finished. total time: 0.167ssending 'persist' (4673 KB)...OKAY [ 0.120s]writing 'persist'...OKAY [ 0.020s]finished. total time: 0.144ssending 'modem' (78615 KB)...OKAY [ 1.729s]writing 'modem'...OKAY [ 0.013s]finished. total time: 1.746ssending 'cust_nv' (301 KB)...OKAY [ 0.030s]writing 'cust_nv'...OKAY [ 0.021s]finished. total time: 0.053ssending 'systeminfo' (4 KB)...OKAY [ 0.020s]writing 'systeminfo'...OKAY [ 0.021s]finished. total time: 0.043ssending 'KEY_INFO' (1 KB)...OKAY [ 0.020s]writing 'KEY_INFO'...OKAY [ 0.021s]finished. total time: 0.045ssending 'hidden' (9319 KB)...OKAY [ 0.211s]writing 'hidden'...OKAY [ 0.020s]finished. total time: 0.235ssending 'sutinfo' (1 KB)...OKAY [ 0.020s]writing 'sutinfo'...OKAY [ 0.021s]finished. total time: 0.044srebooting into bootloader...OKAY [ 0.006s]finished. total time: 0.006s< waiting for device >sending 'recovery' (12794 KB)...OKAY [ 0.291s]writing 'recovery'...OKAY [ 0.020s]finished. total time: 0.320srebooting into bootloader...OKAY [ 0.003s]finished. total time: 0.003s< waiting for device >sending 'boot' (11746 KB)...OKAY [ 0.281s]writing 'boot'...OKAY [ 0.019s]finished. total time: 0.306srebooting into bootloader...OKAY [ 0.010s]finished. total time: 0.011s< waiting for device >simu_flash:971f0dec:systemsending segment 1 of 'system' (2475972 KB)...
I tried to fool the device and downloaded twrp and named it recovery.img and placed within the same directory and again it said it was flashed as you see above, and when I tried to boot into recovery it was still the stock one.
Sadly I can't return my phone and Amazon is refusing to take it back since it was past the 30 days so I can't file an A-Z claim. I hope someone can help and giving me an idea of how to unlock the bootloader so at least I can flash stock again.
Cheers
Click to expand...
Click to collapse
Have you tried using the oem unlock bootloader CMD via fast boot?
You need your bootloader unlocked to use the factory images in this first place so that's why recovery isn't sticking and I bet everything else isn't as well. Pretty stumped on this to be honest.
I recently bought a new Robin and I'm almost certain I never used stock or even booted it before unlocking my boot loader

AnierinB said:
Have you tried using the oem unlock bootloader CMD via fast boot?
You need your bootloader unlocked to use the factory images in this first place so that's why recovery isn't sticking and I bet everything else isn't as well. Pretty stumped on this to be honest.
I recently bought a new Robin and I'm almost certain I never used stock or even booted it before unlocking my boot loader
Click to expand...
Click to collapse
Hey mate yeah tried to unlock the oem and said something like bootloader is locked. I didn't get the chance to sign in once I hooked up the phone to wifi the updates started and I have proceeded, till it shut down and all fell a part. Funny enough I bought 2 Robins one for myself and one for my misses. Hers we used it on the same day it arrived and still working fine, but mine had all of this dramas.
I know it's very tough one and I am hoping that someone can help.

vampire_8_7 said:
Hey mate yeah tried to unlock the oem and said something like bootloader is locked. I didn't get the chance to sign in once I hooked up the phone to wifi the updates started and I have proceeded, till it shut down and all fell a part. Funny enough I bought 2 Robins one for myself and one for my misses. Hers we used it on the same day it arrived and still working fine, but mine had all of this dramas.
I know it's very tough one and I am hoping that someone can help.
Click to expand...
Click to collapse
Try "fastboot reboot-system (or fastboot reboot system)", if you after that load in recovery, try to see partitions via adb shell and "df" command. I have some trouble with flashing on locked bootloader, and in process - phone don't erase /system.

HeaDekBatHblu said:
Try "fastboot reboot-system (or fastboot reboot system)", if you after that load in recovery, try to see partitions via adb shell and "df" command. I have some trouble with flashing on locked bootloader, and in process - phone don't erase /system.
Click to expand...
Click to collapse
hey mate these 2 commands don't exist in the fastboot
fastboot reboot system
fastboot reboot-system
I have also tried the adb shell and it gave me "error : no devices found". I had to reboot in recovery and choose apply update via adb so I can see the listed devices.
HTML:
E:\Programs\Phones\Android\Rooting Apps\fastboot>adb.exe devices -l
List of devices attached
NBQGLMB660203876 sideload product:ether model:Robin device:ether
E:\Programs\Phones\Android\Rooting Apps\fastboot>adb.exe reboot-bootloader
error: closed
E:\Programs\Phones\Android\Rooting Apps\fastboot>adb.exe reboot-bootloader -i 0x2c3f
error: closed
No luck bro.

This should be recoverable.. Do you still need some help?
From what i think i understand of the circumstances:
-- You had a new phone.
-- You booted the phone, and started to download and apply the OS update over a network (for some reason.. flashing via usb would have been faster and more simple but..)
-- The update failed before it could finish, leaving you without an OS to boot into, however fastboot and stock recovery are fine
*** Everything else mentioned i believe is irrelevant.. Based on what you said happened, there shouldn't be any reason you can't recover.. It's a new phone with healthy hardware, your fastboot and recovery are intact, and It worked until the update broke the system. So if that is definitely the cause, i see no reason why this couldn't be fixed.. So just lmk if you want some additional advice before i type up a how-to for no reason, lol

soulife said:
This should be recoverable.. Do you still need some help?
From what i think i understand of the circumstances:
-- You had a new phone.
-- You booted the phone, and started to download and apply the OS update over a network (for some reason.. flashing via usb would have been faster and more simple but..)
-- The update failed before it could finish, leaving you without an OS to boot into, however fastboot and stock recovery are fine
*** Everything else mentioned i believe is irrelevant.. Based on what you said happened, there shouldn't be any reason you can't recover.. It's a new phone with healthy hardware, your fastboot and recovery are intact, and It worked until the update broke the system. So if that is definitely the cause, i see no reason why this couldn't be fixed.. So just lmk if you want some additional advice before i type up a how-to for no reason, lol
Click to expand...
Click to collapse
Hey mate so sorry for the late reply, for some reason I didn't see the notification of your reply.
Yeah fastboot and Stock recovery are working fine, but remember bootloader is still locked and the USB debugging isn't enabled. I thought it should be recoverable but I am not able to recover it and tried too many ways but they all have failed. I will appreciate some advise/help to sort this phone. Thanks

That's what I don't understand, the "bootloader is still locked" part..
You're saying that "fastboot -i 0x2c3f oem unlock" doesn't work because the "oem unlocked" setting in developer settings wasn't checked..
The robin is the first phone I owned since the extra oem bootloader security feature was introduced.. I understand now how it works and why it's there, but I didn't at the time I powered on my phone and flashed it for the first time..
When I first used the device, I powered on, skipped setup, started the system updates over wifi, and realized I was wasting time since I was gonna setup adb, fastboot, download factory images, root, unencrypt, etc.. So in the middle of the ota update I force rebooted using volume down + power, got everything setup on the laptop, and then fastboot oem unlocked and updated everything to nougat.. It wasn't until some time shortly after that I learned that it could have bricked my device, but luckily it seemed that oem unlocked is on by default.. Since I'm obviously not bricked, and also when I finally got around to enabling developer options, it was already checked without my interaction..
So that's what I'm unsure of, it's apparently already unlocked out of the box..
But fwiw, I stumbled onto an article on the razor forum about someone who bricked their phone by turning oem option off and then doing a full wipe.. One of the nextbit employees said he needed a new phone, but a user suggested a sequence of things to flash in some particular order, something like "first flash android 6, then 7" and it worked, he unbricked despite nextbit themselves telling him he was screwed..
I'll see if I can find the article again when I get some spare time. But again, from my experience, oem unlock was already on on my brand new robin.. I've never checked it once and have flashed my device several times already without issue

soulife said:
That's what I don't understand, the "bootloader is still locked" part..
You're saying that "fastboot -i 0x2c3f oem unlock" doesn't work because the "oem unlocked" setting in developer settings wasn't checked..
The robin is the first phone I owned since the extra oem bootloader security feature was introduced.. I understand now how it works and why it's there, but I didn't at the time I powered on my phone and flashed it for the first time..
When I first used the device, I powered on, skipped setup, started the system updates over wifi, and realized I was wasting time since I was gonna setup adb, fastboot, download factory images, root, unencrypt, etc.. So in the middle of the ota update I force rebooted using volume down + power, got everything setup on the laptop, and then fastboot oem unlocked and updated everything to nougat.. It wasn't until some time shortly after that I learned that it could have bricked my device, but luckily it seemed that oem unlocked is on by default.. Since I'm obviously not bricked, and also when I finally got around to enabling developer options, it was already checked without my interaction..
So that's what I'm unsure of, it's apparently already unlocked out of the box..
But fwiw, I stumbled onto an article on the razor forum about someone who bricked their phone by turning oem option off and then doing a full wipe.. One of the nextbit employees said he needed a new phone, but a user suggested a sequence of things to flash in some particular order, something like "first flash android 6, then 7" and it worked, he unbricked despite nextbit themselves telling him he was screwed..
I'll see if I can find the article again when I get some spare time. But again, from my experience, oem unlock was already on on my brand new robin.. I've never checked it once and have flashed my device several times already without issue
Click to expand...
Click to collapse
I bought 2 Robins at the time, 1 I used straight away and the other is the 1 that had the issue and I started using it like 3 months later. By default the OEM isn't toggled on I have confirmed that 100%, after the 2nd Robin got bricked. I picked up the working one and looked at it and sure enough the OEM toggle was off so I had to turn it on myself also enabled USB debugging in case this one breaks for some reason.
So yeah, basically if I tried to flash anything via fastboot it says "remote device is locked" and can't sideload anything via ADB also because USB debugging isn't enabled.
I managed to get the OTA.zip for Robin, Nougat update and half way through updating around 47% to 51% it fails, because the boot image is different off course, cause my phone still running 6.0.1, and the OTA find unmatched release keys. I think if I can find a full signed 6.0.1.zip for Robin I might be able to sideload it.
Literally I have tried everything I came across with this phone, pretty frustrating.
Thanks for your help, if you have more suggestions please let me know.

Find 6.0.1?
If you can find? It's there:
https://insider.razerzone.com/index.php?threads/robin-factory-images-and-usb-driver.21487/
And that is strange then.. My oem unlocked is checked my default and yours isn't.. Maybe my Amazon seller sold me a return lol..
Edit: ahh, I guess you meant a flashable zip? What if you pull the images, sideload them, and flash the images individually?
vampire_8_7 said:
I think if I can find a full signed 6.0.1.zip for Robin I might be able to sideload it.
Literally I have tried everything I came across with this phone, pretty frustrating.
Thanks for your help, if you have more suggestions please let me know.
Click to expand...
Click to collapse

soulife said:
If you can find? It's there:
https://insider.razerzone.com/index.php?threads/robin-factory-images-and-usb-driver.21487/
And that is strange then.. My oem unlocked is checked my default and yours isn't.. Maybe my Amazon seller sold me a return lol..
Edit: ahh, I guess you meant a flashable zip? What if you pull the images, sideload them, and flash the images individually?
Click to expand...
Click to collapse
Hey mate yeah I meant flashable.zip, and nope the images won't work via sideload. Definitely the OEM wasn't checked I got 2 Robins and both weren't toggole on.

BRICKED?. Can't figure out how to update bootloader. Can't flash flash-all.bat

I have a google Pixel Xl running android Pie. I am trying to flash it back to stock. I am getting this error after flashing flash-all.bat.
This what I get after running the batch file:
fastboot: error: cannot load 'bootloader-marlin-8996-012001-1811131534.img': No such file or directory
rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
Sending 'radio_a' (57140 KB) OKAY [ 1.698s]
Writing 'radio_a' OKAY [ 0.500s]
Finished. Total time: 2.338s
rebooting into bootloader OKAY [ 0.016s]
Finished. Total time: 0.016s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: 8996-012001-1808030001
Baseband Version.....: 8996-130181-1808270817
Serial Number........: HT76L0200289
--------------------------------------------
Checking product OKAY [ 0.059s]
Checking version-bootloader FAILED
Device version-bootloader is '8996-012001-1808030001'.
Update requires '8996-012001-1811131534'.
fastboot: error: requirements not met!
Press any key to exit...
I am Unlocked and my bootloader version is 8996-012001-1808030001. How can I update the bootloader?I did the flash wipe (fastboot -w) and think I wiped the os and internal SD. . When I flash boot into twrp I cannot see any of my files. Nothing is on the SD card. Even after mounting system nothing shows up in twrp after clicking install.
tl ;dr
All zips and roms dissapeared off my SD card. Can't boot into OS or revert to stock.....Need to somehow update bootloader
Any suggestions?!

glachance0 said:
I have a google Pixel Xl running android Pie. I am trying to flash it back to stock. I am getting this error after flashing flash-all.bat...
Click to expand...
Click to collapse
Deleted

Figured it out.

glachance0 said:
Figured it out.
Click to expand...
Click to collapse
I have the same issue, less or more, my bootloader is locked. but how did you update your bootloader? Thanks.

glachance0 said:
Figured it out.
Click to expand...
Click to collapse
What did you do to fix it?