Develop Bugs

[Q] LTE Won't boot despite efforts to flash back to factory

So I ran into trouble while trying to root and am having trouble flashing the stock images. I downloaded the factory images (4.3 (JLS36C)) from google. Flashing the bootloader image(bootloader-deb-flo-03.14.img) seems to work just fine but when I try to update to the provided "image-razorg-JLS36C.zip" I have trouble. I read that the radio included (radio-deb-deb-g00_1.23.0_0720.img) is the wrong one but then found conflicting information that it is just mis-named. I tried renaming the file to the the baseband that is being requested (DEB-G00_2.25.1_0802) but that didn't work either and I can't locate that specific file to add to the directory.
Below is the log from terminal, I highlighted everything that throws errors. I also tried using the WugFresh tool through parallels and got the same issues. Is it something simple I'm missing? It feels really close to working. Please let me know how I can fix this, thanks for your time.
**Edit: I also tried flashing only the baseband radio ./fastboot flash radio "file" to the file that was included in the google download but it still threw the same errors.**
Code:
Last login: Fri Sep 27 23:44:48 on ttys000
cpe-75-85-155-82:~ kyler$ cd Downloads
cpe-75-85-155-82:Downloads kyler$ cd "android tools"
cpe-75-85-155-82:android tools kyler$ ./fastboot flash bootloader bootloader-deb-flo-03.14.img
sending 'bootloader' (3911 KB)...
OKAY [ 0.134s]
writing 'bootloader'...
OKAY [ 1.334s]
finished. total time: 1.469s
cpe-75-85-155-82:android tools kyler$ ./fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.005s]
finished. total time: 0.005s
cpe-75-85-155-82:android tools kyler$ ./fastboot -w update image-razorg-JLS36C.zip
[B]archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'[/B]
--------------------------------------------
Bootloader Version...: FLO-03.14
[B]Baseband Version.....: DEB-[/B]
Serial Number........: 08664aa9
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
[B]checking version-baseband...
FAILED
Device version-baseband is 'DEB-'.
Update requires 'DEB-G00_2.25.1_0802'.[/B]
finished. total time: 0.024s
cpe-75-85-155-82:android tools kyler$

Might want to try using the flashall.sh script (I think that is the name, but should be in the main directory of image). Have not tried it on my deb yet, but has always worked for my other nexus devices, including flo.
Sent from my Nexus 7 using Tapatalk 4

pudgewack said:
Might want to try using the flashall.sh script (I think that is the name, but should be in the main directory of image). Have not tried it on my deb yet, but has always worked for my other nexus devices, including flo.
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
Wow thanks, that worked great. Strange though because as I looked at the commands earlier in the script they were the same as the ones I was trying to use manually to fix it in the first place.
From flash-all.sh:
Code:
./fastboot flash bootloader bootloader-deb-flo-03.14.img
./fastboot reboot-bootloader
sleep 5
./fastboot flash radio radio-deb-deb-g00_1.23.0_0720.img
./fastboot reboot-bootloader
sleep 5
./fastboot -w update image-razorg-JLS36C.zip
Well I guess there must be something I'm missing... The log is still throwing the errors:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
So if you know how I could fix that it would be great, otherwise the device seems to be working properly.

[email protected] said:
Wow thanks, that worked great. Strange though because as I looked at the commands earlier in the script they were the same as the ones I was trying to use manually to fix it in the first place.
From flash-all.sh:
Code:
./fastboot flash bootloader bootloader-deb-flo-03.14.img
./fastboot reboot-bootloader
sleep 5
./fastboot flash radio radio-deb-deb-g00_1.23.0_0720.img
./fastboot reboot-bootloader
sleep 5
./fastboot -w update image-razorg-JLS36C.zip
Well I guess there must be something I'm missing... The log is still throwing the errors:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
So if you know how I could fix that it would be great, otherwise the device seems to be working properly.
Click to expand...
Click to collapse
Earlier you didn't flash in the same sequence.
Earlier you flashed
bootloader-deb-flo-03.14.img
image-razorg-JLS36C.zip
The script flashes
bootloader-deb-flo-03.14.img
radio-deb-deb-g00_1.23.0_0720.img
image-razorg-JLS36C.zip
When you flash image-razorg-JLS36C.zip, it verifies the radio you have *installed* on the tablet is the version required. Since you never flashed the radio earlier, the check failed. Later you tried to rename it, which does no good because renaming it isn't installing it, and the version check to see what you have installed failed again.
I am only commenting on the log you posted. You mention in the edit that you flashed the radio but didn't post the log, so I can not be sure what you did achieved what you intended.
The missing .sig errors are normal. Google didn't sign their factory images, which is why you need to be bootloader unlocked to factory restore.

Unable to flash to restock

I softbricked my N7. Can still get to flashboot. However, I have tried following so many guides to flash back to stock to recover from this that I'm going a little manic about it. I just recently tried the Nexus Root Toolkit and it's method. But I get this:
*******Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [6.617s]
finished. total time: 6.617s
sending 'bootloader' <2100 KB>...
OKAY [0.070s]
writing 'bootloader'...
FAILED <remote: SIgnature mismatched!!!>
finished. total time: 0.090s
rebooting into bootloader...
OKAY [0.010s]
finished. total time: 0.010s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
______________________________
Bootloader version...: FLO-03.14
Baseband Version...: none
Serial Number...: 0584c016
______________________________
checking product...
FAILED
Device product is 'flo'/
Update requires 'grouper'.
finished. total time: 0.020s
Booting up your freshly flashed stock device...
_______________________________
and a paragraph about what to do if it doesnt work. i did what it requested and the same thing. Please help me.

usefuladjective said:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
______________________________
Bootloader version...: FLO-03.14
Baseband Version...: none
Serial Number...: 0584c016
______________________________
checking product...
FAILED
Device product is 'flo'/
Update requires 'grouper'..
Click to expand...
Click to collapse
You are trying to flash grouper files on a flo. Get the flo files.

meekrawb said:
You are trying to flash grouper files on a flo. Get the flo files.
Click to expand...
Click to collapse
I've tried flashing just about every image that is available. Each attempt says the same thing.

I'm still having issues.
I've flashed every image that the toolkit gives me a prompt for and it still won't do anything.
Please help me. I'm desperate.

Download the 4.4.2 image from Google site for flo, boot into recovery mode and side load the image.
Sent from my Nexus 7 using XDA Premium 4 mobile app

(Q) Think I got a damaged Internal SD Card; how to replace it?

My device is soft bricked I think (SD Card damaged, bootloader is fine; can't write anything on it; bootloader, etc etc); so anyone knows of a guide on how to replace your internal SD Card? If there's any help about it I would appreciate it. Thanks.

ReDXfiRe said:
My device is soft bricked I think (SD Card damaged, bootloader is fine; can't write anything on it; bootloader, etc etc); so anyone knows of a guide on how to replace your internal SD Card? If there's any help about it I would appreciate it. Thanks.
Click to expand...
Click to collapse
I'll try to sort this out. Soft bricked essentially means your device won't boot. At that point you should revert to a current backup. I wouldn't go so far as replacing your internal memory as i would adb'ing the factory images. Do some more reading the answers are there!

Beezer80 said:
I'll try to sort this out. Soft bricked essentially means your device won't boot. At that point you should revert to a current backup. I wouldn't go so far as replacing your internal memory as i would adb'ing the factory images. Do some more reading the answers are there!
Click to expand...
Click to collapse
Already did try factory image won't let it write; seems something wrong with hardware already big contributors have told me its hardware.

Can you unlock the bootloader, or is it unlocked already?

ReDXfiRe said:
Already did try factory image won't let it write; seems something wrong with hardware already big contributors have told me its hardware.
Click to expand...
Click to collapse
Replace the motherboard or warranty.

ReDXfiRe said:
Already did try factory image won't let it write; seems something wrong with hardware already big contributors have told me its hardware.
Click to expand...
Click to collapse
What are you using to try to flash it, Wug's?

Pandae said:
Can you unlock the bootloader, or is it unlocked already?
Click to expand...
Click to collapse
It's unlocked already. Been in many forums they say its hardware :\

skrypj said:
What are you using to try to flash it, Wug's?
Click to expand...
Click to collapse
C:\ADB>flash-all.bat
sending 'bootloader' (3911 KB)...
OKAY [ 0.130s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.912s
rebooting into bootloader...
OKAY [ 0.009s]
finished. total time: 0.010s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-03.15
Baseband Version.....: none
Serial Number........: 05fa05a1
--------------------------------------------
checking product...
OKAY [ 0.004s]
checking version-bootloader...
FAILED
Device version-bootloader is 'FLO-03.15'.
Update requires 'FLO-04.02'.
finished. total time: 0.046s
Press any key to exit...
No just regular fastboot flash bootloader method; done with .bat and manually and nothing

ReDXfiRe said:
C:\ADB>flash-all.bat
sending 'bootloader' (3911 KB)...
OKAY [ 0.130s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.912s
rebooting into bootloader...
OKAY [ 0.009s]
finished. total time: 0.010s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-03.15
Baseband Version.....: none
Serial Number........: 05fa05a1
--------------------------------------------
checking product...
OKAY [ 0.004s]
checking version-bootloader...
FAILED
Device version-bootloader is 'FLO-03.15'.
Update requires 'FLO-04.02'.
finished. total time: 0.046s
Press any key to exit...
No just regular fastboot flash bootloader method; done with .bat and manually and nothing
Click to expand...
Click to collapse
Try wugs program, but go to Options Menu>Flash Stock Tab>Check "Enable 'Force Flash Mode' . . . " Then try to flash stock + unroot again with the soft-bricked option selected. This basically makes Wug's ignore the check process at the beginning of the flash. It almost sounds like it was not passing the check. This will erase your entire tablet though.
I also had an issue with my fastboot drivers where it wouldn't work properly with my n7 but were fine with my nexus 5. I had a bunch of failures similar to yours. I full uninstalled all android associated drivers, whether they were Samsung, lg, asus , whatever and reinstalled. This worked.

ReDXfiRe said:
My device is soft bricked I think (SD Card damaged, bootloader is fine; can't write anything on it; bootloader, etc etc); so anyone knows of a guide on how to replace your internal SD Card? If there's any help about it I would appreciate it. Thanks.
Click to expand...
Click to collapse
Better hope that one of those suggestions would work for you, 'cause the internal nand is not replaceable, unless you have some quite hi-tech equipment. If need be, you have to replace the whole motherboard. True, when the nand cannot be physically written on anymore, it would show those symptoms. Yet imputing fault to hardware is a guess in most cases. Because I don't hear people complaining about the Nexus 7's NAND being a dud much(compared to the Acer A500, for instance). You should try every solution you can dig up from forums first.

Flashing Android P Dev Image

I am not able to flash the Android P Developer image.
I was under the impression this could be done without having to unlock the bootloader by editing the script to remove -w
Clearly I must be missing something here.
Code:
bob$ ./flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloader_b' (36344 KB)...
OKAY [ 0.775s]
writing 'bootloader_b'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.776s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
target reported max download size of 536870912 bytes
sending 'radio_b' (60428 KB)...
OKAY [ 1.610s]
writing 'radio_b'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 1.611s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
extracting android-info.txt (0 MB) to RAM...
extracting boot.img (40 MB) to disk... took 0.251s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'boot_other.img'
extracting dtbo.img (8 MB) to disk... took 0.031s
archive does not contain 'dtbo.sig'
archive does not contain 'dt.img'
archive does not contain 'recovery.img'
extracting system.img (2152 MB) to disk... took 13.216s
archive does not contain 'system.sig'
extracting system_other.img (332 MB) to disk... took 2.352s
archive does not contain 'system.sig'
extracting vbmeta.img (0 MB) to disk... took 0.000s
archive does not contain 'vbmeta.sig'
extracting vendor.img (366 MB) to disk... took 2.367s
archive does not contain 'vendor.sig'
archive does not contain 'vendor_other.img'
--------------------------------------------
Bootloader Version...: TMZ12bb
Baseband Version.....: g8998-00164-1710262031
Serial Number........:
--------------------------------------------
checking product...
OKAY [ 0.001s]
checking version-bootloader...
FAILED
Device version-bootloader is 'TMZ12bb'.
Update requires 'TMZ20f'.
finished. total time: 0.004s
bob$
OK fine try each of the components with fastboot in the image:
Code:
fastboot flash bootloader bootloader-taimen-tmz20f.img
target reported max download size of 536870912 bytes
sending 'bootloader_b' (36344 KB)...
OKAY [ 0.957s]
writing 'bootloader_b'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.958s
bob$
So whats happening here?

You do need to unlock your bootloader in order to flash factory images. Removing -W from flash-all.bat file is just going to keep your data. Nothing else.

Obviously it's because your boot loader is locked
People like you brick systems because you don't read

You CANNOT flash a system image without unlocking your bootloader.
You CAN sideload an OTA update without unlocking your bootloader.
You can sideload the OTA for P via adb.
But, there is no OTA update for going back to O. That will happen when the public beta starts in May.
To go back before the public beta starts, you will have to flash the system image for which you will need to unlock your bootloader.

flex360 said:
Obviously it's because your boot loader is locked
People like you brick systems because you don't read
Click to expand...
Click to collapse
Flashing a stock ROM on an android phone should not require an unlocked bootloader to be fair. It's people like Google that force people to brick their systems using stupid systems. It's also people like you who offer zero help on forums.

Thanks Jonathan-H. I didn't see a OTA for Android P. I had been flashing OTA's in the past and that had me a bit confused. ("I swear I did this before, why not now"). Been a while as I had not flashed anything onto my N6P while I had it. The problem I have run into with my Pixel is that it happens to be one of those Google shipped out that can't be bootloader unlocked. My understanding is that I can do this by doing a factory reset, but I didn't want to loose all the apps and data, and go through the process of re-downloading every single one. I know its generally recommended to start clean.

Jonathan-H said:
Flashing a stock ROM on an android phone should not require an unlocked bootloader to be fair. It's people like Google that force people to brick their systems using stupid systems. It's also people like you who offer zero help on forums.
Click to expand...
Click to collapse
To be fair... Google isn't forcing anybody to unlock their bootloaders. That's up to you. Anyone who knows what they are doing flashing system images will be just fine. You don't appear to be one of those people.

borillion_star said:
Thanks Jonathan-H. I didn't see a OTA for Android P. I had been flashing OTA's in the past and that had me a bit confused. ("I swear I did this before, why not now"). Been a while as I had not flashed anything onto my N6P while I had it. The problem I have run into with my Pixel is that it happens to be one of those Google shipped out that can't be bootloader unlocked. My understanding is that I can do this by doing a factory reset, but I didn't want to loose all the apps and data, and go through the process of re-downloading every single one. I know its generally recommended to start clean.
Click to expand...
Click to collapse
https://developer.android.com/preview/download-ota.html
Be aware, while generally speaking, you should be fine doing OTA. However, with a locked bootloader, if you have any issue and something goes awry, you will have a brick.

Jonathan-H said:
Flashing a stock ROM on an android phone should not require an unlocked bootloader to be fair. It's people like Google that force people to brick their systems using stupid systems. It's also people like you who offer zero help on forums.
Click to expand...
Click to collapse
No, it's people like the OP of this thread who expect to be spoon fed information that is already covered extensively in other threads. Including the thread dedicated to this EXACT situation of trying to flash Android P. A very small amount of reading in the below thread would have quickly answered the OP's questions.
[ROM NEWS] Android P - Root+Theme Support
Quite frankly, the fact that he thinks he can flash a factory image without unlocking the bootloader shows that he shouldn't be messing with his phone at all. Absolutely none of this is Google's fault.

sn0warmy said:
No, it's people like the OP of this thread who expect to be spoon fed information that is already covered extensively in other threads. Including the thread dedicated to this EXACT situation of trying to flash Android P. A very small amount of reading in the below thread would have quickly answered the OP's questions.
[ROM NEWS] Android P - Root+Theme Support
Quite frankly, the fact that he thinks he can flash a factory image without unlocking the bootloader shows that he shouldn't be messing with his phone at all. Absolutely none of this is Google's fault.
Click to expand...
Click to collapse
Also from the official website where you download the images it has instruction which include needing to unlock the bootloader for full images. And also tells you that OTA do not require unlocking the bootloader.

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?