Database Users

[Q] [Help please] Nexus 7 3G can't flash radio and therefore no stock rom!!

Hello,
I have an untouched Nexus 7 3G (tilapia) and started today the update to Android 4.3 (normal system update).
The update failed and Android couldn't boot.
So I tried to flash with the Nexus 7 Toolkit 5.0.0. Failed also with the following message:
sending 'radio' (16384 KB)...
OKAY [ 2.128s]
writing 'radio'...
FAILED (remote: (BadParameter))
Click to expand...
Click to collapse
In FASTBOOT I have the following informations:
PRODUCT NAME - tilapia
VARIANT - tilapia
HW Version - PR
BOOTLOADER VERSION - 4.23
BASEBAND VERSION - N/A
SERIAL NUMBER - [...]
SIGNING - not defined yet
LOCK STATE - UNLOCKED
Click to expand...
Click to collapse
(I've unlocked the bootloader for recovery purpose.)
I've installed then TWRP and tried a factory reset but it complains:
E:Unable to mount '/system'
[and]
E:Unable to mount '/radio'
Click to expand...
Click to collapse
After manipulating "androidinfo.txt" (changing the value for "require version-baseband" to "N/A"), I was able to install Android 4.3 manually (with the SDK). In Android I've got the following baseband information: "radio-tilapia-1231_0.17.0_1205.img" and I can register with my mobile provider. But I have still "BASEBAND VERSION - N/A" in FASTBOOT and can't update the radio (same error).
I've installed again TWRP and performed a factory reset (to try to install CyanogenMod) and have still the error:
E:Unable to mount '/radio'
Click to expand...
Click to collapse
'/system' seems to be OK now.
What's wrong with my Nexus 7 and what can I do about it?
I would like to be able to use my Nexus 7 with the required radio for Android 4.3 but can't update it (or any other radio).
Can someone help me, please?
Thank you very much!
With best regards,
another_sonny

another_sonny said:
I have an untouched Nexus 7 3G (tilapia) and started today the update to Android 4.3 (normal system update).
The update failed and Android couldn't boot.
Click to expand...
Click to collapse
another_sonny said:
What's wrong with my Nexus 7 and what can I do about it?
I would like to be able to use my Nexus 7 with the required radio for Android 4.3 but can't update it (or any other radio).
Can someone help me, please?
Thank you very much!
With best regards,
another_sonny
Click to expand...
Click to collapse
Hi!
Same problem with my brand new Nexus 7 3G.
Still trying to work it out.
Code:
c:\ADB>fastboot flash radio radio-tilapia-1231_0.18.0_0409.img
sending 'radio' (16384 KB)...
OKAY [ 2.047s]
writing 'radio'...
FAILED (remote: (BadParameter))
finished. total time: 2.073s

Exact the same Problem here.

Same issue, but the idea is that in theory you should be able to sideload the radio also using adb, the problem is that i just dumped all the stuff from the tablet and no partition has exactly 16mb, the size of the radio.
What i want to try is to sideload the radio via adb, if it does not work, format the radio partition, and try to sideload again, but i can do this only if i can find out which mmcblk is the radio
[email protected]:/ # ls /dev/block/mmcblk*
ls /dev/block/mmcblk*
/dev/block/mmcblk0 TO BIG
/dev/block/mmcblk0boot0 2.048KB (bootloader)
/dev/block/mmcblk0boot1 2.048KB (bootloader backup)
/dev/block/mmcblk0p1 12.288KB (boot or recovery)
/dev/block/mmcblk0p2 8.192 KB
/dev/block/mmcblk0p3 TO BIG
/dev/block/mmcblk0p4 TO BIG
/dev/block/mmcblk0p5 512KB
/dev/block/mmcblk0p6 10.240KB (boot or recovery)
/dev/block/mmcblk0p7 5.120KB
/dev/block/mmcblk0p8 512KB
/dev/block/mmcblk0p9 TO BIG
Inside the radio-tilapia-1231_0.18.0_0409.img there is a radio_image.zip file

I managed to partially fix the issue
What I did.
1) Mounted radio-tilapia-1231_0.18.0_0409.img in Linux (sudo mount -o loop radio-tilapia-1231_0.18.0_0409.img radio/ i previosly created the directory radio)
2) Copied the radio_update.zip
3) Rebooted the Tablet in RECOVERY
4) Pressed Power Key and Volume Key Plus (first power key, while you keep the power pressed, press the volume key for 2 seconds, release, this will enable the stock recovery menu)
5) Select "Apply Update From ADB"
6) Issue the command "adb sideload radio_update.zip
7) Wait till the update goes to end,, and select Reboot system now.
Now when you check in Settings/About Tablet/Baseband, you should have the Baseband which you applied via adb sideload
Here is a link towards the radio_update.zip for those in need
http://globula.arctablet.com/Nexus7/radio_update.zip
LE: YOU NEED TO BE ON STOCK RECOVERY TO APPLY THIS FIX

globula_neagra said:
I managed to partially fix the issue
Click to expand...
Click to collapse
Apologize for some questions, but i am not familiar with adb sideload commands.
- Does your procedure require a Linux installation over a PC or can be performed directly using TWRP recovery or a Windows PC?
- What are the commands to create the directory /radio ?
- Once the procedure is fully executed, if you start Nexus in fastboot mode, do you still see BASEBAND label with N/A or do you see the correct identifier of the Radio installed (i.e. 1231_0.18.0_0409)?
Thanks a lot in advance

flaps1970 said:
Apologize for some questions, but i am not familiar with adb sideload commands.
- Does your procedure require a Linux installation over a PC or can be performed directly using TWRP recovery or a Windows PC?
- What are the commands to create the directory /radio ?
- Once the procedure is fully executed, if you start Nexus in fastboot mode, do you still see BASEBAND label with N/A or do you see the correct identifier of the Radio installed (i.e. 1231_0.18.0_0409)?
Thanks a lot in advance
Click to expand...
Click to collapse
"- Does your procedure require a Linux installation over a PC or can be performed directly using TWRP recovery or a Windows PC?"
No, it does not require Linux, for future radio updates, yes it may require some Linux if you want to mount radio and extract the file.
You cannot use custom recovery, NO CWM, NO TWRP, JUST PLAIN STOCK
"- What are the commands to create the directory /radio ?"
The command is mkdir radio, but it is usable only in linux when you want to extract the radio_update.zip from the image
"- Once the procedure is fully executed, if you start Nexus in fastboot mode, do you still see BASEBAND label with N/A or do you see the correct identifier of the Radio installed (i.e. 1231_0.18.0_0409)?"
-No, this issue will still remain, but in settings/about tablet/ Will be updated correctly.
I still want to find out on which partition is the radio stored, and maybe someone will have the good will and dump his radio, so i can flash it back on mine to see if it fixes the display in the bootloader.
But until that man appears, we have to pray for a miracle .

Ok clear, so you mounted the radio via linux in order to get the zip file that you are sharing in your link.
Now we can start with that zip file and "push" it to the nexus via adb sideload.
I provide some additional infos hoping they will help the analysis.
I started to experiment this issue after tablet came back from ASUS technical support with the mother board replaced.
Before the MB replacement i was able to flash any radio. After the replacement i wasn't able anymore to flash the radio.
I read about some other guys that had the same behaviour (MB replacement --> issue to flash radio).
Maybe some configurations have been missed during the repair or the new motherboard has compatibility issues.....
I tried to restore via TWRP an old backup that i did before the MB replacement. When TWRP tried to restore the radio, an error like "unable to wipe radio" happened and the restore failed.

flaps1970 said:
Ok clear, so you mounted the radio via linux in order to get the zip file that you are sharing in your link.
Now we can start with that zip file and "push" it to the nexus via adb sideload.
I provide some additional infos hoping they will help the analysis.
I started to experiment this issue after tablet came back from ASUS technical support with the mother board replaced.
Before the MB replacement i was able to flash any radio. After the replacement i wasn't able anymore to flash the radio.
I read about some other guys that had the same behaviour (MB replacement --> issue to flash radio).
Maybe some configurations have been missed during the repair or the new motherboard has compatibility issues.....
I tried to restore via TWRP an old backup that i did before the MB replacement. When TWRP tried to restore the radio, an error like "unable to wipe radio" happened and the restore failed.
Click to expand...
Click to collapse
It happens because:
1) The radio is corrupted or the fs is different from ext4 (the recovery.fstab says the the radio partition is ext4)
1) The OTA screws up the radio partition upon update.

[Q] Help: No OS installed message after lastest OTA update

Hi,
Following a tutorial on this site, I managed to root and install TWRP 2.6 on my nexus 4 and I had Android 4.3 running. After a notification about an OTA update (I believe the second very small security update), I'm now stuck on the Google name at boot. No coloured animation or anything.
I can still get into TWRP but it shows the "No OS installed" message (rebooting anyway gets me the white Google name).
It seems that fastboot is no longer working either.
adb devices works but fastboot devices does not.
I tried the TWRP sideload feature to install the latest OTA 4.3 image but that did not work either.
I searched for this error and one thread required fastboot, which does not work and the other suggested using adb push. I pushed the latest 4.3 OTA but the installation failed. I then pushed the stock 4.3 image but its installation failed as well. (the error was : "No MD5 file found" and "unable to mount /system"
I don't know much more about adb so I really need help to get my nexus 4 working again
Any suggestions?

Double_U said:
Hi,
Following a tutorial on this site, I managed to root and install TWRP 2.6 on my nexus 4 and I had Android 4.3 running. After a notification about an OTA update (I believe the second very small security update), I'm now stuck on the Google name at boot. No coloured animation or anything.
I can still get into TWRP but it shows the "No OS installed" message (rebooting anyway gets me the white Google name).
It seems that fastboot is no longer working either.
adb devices works but fastboot devices does not.
I tried the TWRP sideload feature to install the latest OTA 4.3 image but that did not work either.
I searched for this error and one thread required fastboot, which does not work and the other suggested using adb push. I pushed the latest 4.3 OTA but the installation failed. I then pushed the stock 4.3 image but its installation failed as well. (the error was : "No MD5 file found" and "unable to mount /system"
I don't know much more about adb so I really need help to get my nexus 4 working again
Any suggestions?
Click to expand...
Click to collapse
download a nexus 4 toolkit and try to adb sideload a rom. then flash it through twrp. had similar issue and the toolkit adb sideload option resolved my problem.

blankit said:
download a nexus 4 toolkit and try to adb sideload a rom. then flash it through twrp. had similar issue and the toolkit adb sideload option resolved my problem.
Click to expand...
Click to collapse
Wow, followed your advice and am now running CM 10.1.3.. Will see whether I keep it or try to return to stock but I'm so relieved that at least my phone is working again. Thanks ever so much!!

Your welcome.
Sent from my Nexus 4 using XDA Premium 4 mobile app

Not Able To Install Freshly Built Cm Code On Nexus 7

Hi, I have built cm code for my nexus 7 wifi model. $OUT directory did not generate any .zip file.I tried to install each image file individually but nexus 7 did not boot it gets stuck on Google text screen.
I issued fastboot -w flashall command also . But still not working.
Someone please tell some method to get my fresh build working.Thanks.

Problem is that i am unable to generate cm<blah>.zip file.
Sent from my Moto G using Tapatalk

adb sideload "Zip signature verification failed!"

I'm on a Nexus 6p with resurrection remix (for android 6.0.1) trying to flash back to stock 6.0.1. I've been attempting to sideload angler-ota-mtc20l-095e81f7.zip on TWRP (After wiping Dalvik, system, data, and cache) but it keeps saying "Zip signature verification failed!" in my phone and "total xfer: 1.00x" on cmd. I had a backup which I attempted to restore after this failed several times but this left me in a bootloop. Any solution would be appreciated. If you need more information just ask.

Hskom said:
I'm on a Nexus 6p with resurrection remix (for android 6.0.1) trying to flash back to stock 6.0.1. I've been attempting to sideload angler-ota-mtc20l-095e81f7.zip on TWRP (After wiping Dalvik, system, data, and cache) but it keeps saying "Zip signature verification failed!" in my phone and "total xfer: 1.00x" on cmd. I had a backup which I attempted to restore after this failed several times but this left me in a bootloop. Any solution would be appreciated. If you need more information just ask.
Click to expand...
Click to collapse
You'll have to flash the full factory image, not an OTA. You won't be able to side load or flash from recovery. You can either use ADB to flash the full image with the included flash-all.bat, or a toolkit like NRT.

v12xke said:
You'll have to flash the full factory image, not an OTA. You won't be able to side load or flash from recovery. You can either use ADB to flash the full image with the included flash-all.bat, or a toolkit like NRT.
Click to expand...
Click to collapse
I exactly have the same issue but, if I understand correctly, because my device is locked I'm unable to flash the factory image. My phone got bricked during a system update. I had this issue once and I was able to recover it with OTA sideload. But this time it doesn't work: when I do the OTA sideload it gives me the signature verification error.
How could I overcome it?

D4rkFloors said:
I exactly have the same issue but, if I understand correctly, because my device is locked I'm unable to flash the factory image. My phone got bricked during a system update. I had this issue once and I was able to recover it with OTA sideload. But this time it doesn't work: when I do the OTA sideload it gives me the signature verification error.
How could I overcome it?
Click to expand...
Click to collapse
Hi... More infos would help troubleshooting the issue more efficiently.
What was the initial build before the device got bricked?
What was the build "system update" that bricked your phone? Did you update manually or through a pushed OTA? If manually, how did you flash it /bricked your phone?
Finally, which build did you try to Sideload?

5.1 said:
Hi... More infos would help troubleshooting the issue more efficiently.
What was the initial build before the device got bricked?
What was the build "system update" that bricked your phone? Did you update manually or through a pushed OTA? If manually, how did you flash it /bricked your phone?
Finally, which build did you try to Sideload?
Click to expand...
Click to collapse
Thanks for your help.
My current build before the phone got bricked is N4F26I .
I think the update that bricked my phone was N4F26O.
I applied the OTA from the recovery system by selecting "Apply update from ADB" and then doing an adb sideload.
More info:
– I have tried to sideload the OTA images for N4F26I, N4F26J, N4F26O but for all of them I get the error above (I downloaded the OTA image files from Google page)
– Re-downloaded the files, but no joy.
– Phone is not rooted. It had the stock image
- Device shows as LOCKED. If I understand correctly, when device is locked it's not possible to flash the factory image
- USB debugging is enabled
this is the error which happens when I reach 47% of the sideload:
E: failed to verify whole file signature
E: signature verification failed
E: error 21
Installation aborted.

D4rkFloors said:
Thanks for your help.
My current build before the phone got bricked is N4F26I .
I think the update that bricked my phone was N4F26O.
I applied the OTA from the recovery system by selecting "Apply update from ADB" and then doing an adb sideload.
More info:
– I have tried to sideload the OTA images for N4F26I, N4F26J, N4F26O but for all of them I get the error above (I downloaded the OTA image files from Google page)
– Re-downloaded the files, but no joy.
– Phone is not rooted. It had the stock image
- Device shows as LOCKED. If I understand correctly, when device is locked it's not possible to flash the factory image
- USB debugging is enabled
this is the error which happens when I reach 47% of the sideload:
E: failed to verify whole file signature
E: signature verification failed
E: error 21
Installation aborted.
Click to expand...
Click to collapse
Did anyone ever figure out this situation. I'm in exactly same situation. Can't sideload full ota image, quits in middle with signature verification. Bootloader is locked and device wont boot up to enable oem unlocking.

How to get past
adb sideload "Zip signature verification failed!"​Disable signature verification

xinulhacker said:
Come superare
adb sideload "Verifica firma zip fallita!"​Disabilita la verifica della firma
Click to expand...
Click to collapse
How?

Asus Zenfone 5 t00j a500cg | fastboot works I can not install stock or custom rom

A blessed day to all who read and many thanks to those who will help.
I will not confuse you with a long back story. My goal is to update to lollipop but this is where I am at:
fastboot works but I have no OS (having wiped out system folder)
i can install TWRP-2870_Zenfone5.img or recovery_philz_t00f.img. The stock recovery image from UL-ASUS_T00F-WW-2.22.40.53-user.zip only results in a dead droidboot logo (with red exclamation mark)
installing from firmware.zip SD card doesnt work, I will recreate the error messages
E: Unknown File System: 'osip'
E: Unknown File System: 'osip'
E: Unknown File System: 'osip'
E: Unable to find partition size for '/misc'
E: Unable to find partition size for '/splashscreen'
Updating partition details . . .
. . . done
Full SELinux support is present.
E: Unable to set bootloader message.
MTP Enabled
Installing '/external_sd/UL_ASUS_T00F-WW-2.22.40.53-user.zip'. . .
Checking for MD5 file . . .
Skipping MD5 check: no MD5 file found
Error flashing zip '/external_sd/UL_ASUS_T00F-WW-2.22.40.53-user.zip'
Updating partition details . . .
. . . done
Click to expand...
Click to collapse
installing from adb sideload doesnt work. error: closed
I need your help, I have spent 2 days in Google, Asus.com Zentalk and this amazing forum. I need to install the stock ROM and upgrade to Lollipop.
Thanks in advance.
ASUS Zenfone 5 t00j a500cg WW
IFWI 59.A1
Droidboot 2.1

UPDATE
I finally got an OS by following this: link
Quote:
Originally Posted by dgadelha
Hello,
There can be a way to solve your problem
(this solution also can be useful for any other broken systems)
ZENFONE 5 (T00F, T00J) ONLY!
Required downloads:
Jelly Bean Firmware
Intel USB Drivers
ADB+Fastboot
Offline Update Image Script
Steps:
Install the Intel USB Drivers
Rename the Jelly Bean Firmware file, changing the extension from .raw to .zip
Create a directory for all the files (e.g.: C:\zenfone)
Extract the contents of the Jelly Bean Firmware and ADB+Fastboot on the directory you just created
Copy the file of Offline Update Image Script (sec_offline_update_image.cmd) to the same directory
Shutdown your phone and start in droidboot mode (Power + Vol. Up)
Plug the USB
Assert that your device is connected, check by running the command fastboot devices on a Command Prompt
Go to the directory you created before and run the file sec_offline_update_image.cmd as administrator
When your device reboot again into bootloader, check if there was no errors (the userdata erase error can be ignored with no problems). If there was any error, I recommend you to go back and check if you done all steps correctly. If not, just use the volume buttons to select the option 'Reboot' and activate it by pressing the Power key
After this is done, you can upgrade to KitKat or Lollipop via recovery, just download the update from Asus site and sideload it via ADB.
Thanks!
Click to expand...
Click to collapse
adb sideload works
SD card to internal memory copying of stock firmware UL-ASUS_T00F-WW-2.22.40.53-user.zip works when I restart the phone, it detects the system update
but now I get the following error
E:end of footer from data/media/0/UL-ASUS_T00F-WW-2.22.40.53-user.zip failed not 0xFFFF (file exists)
E:signature verification failed
E:Install of data/media/0/UL-ASUS_T00F-WW-2.22.40.53-user.zip failed with status 2
Installation aborted.
E:Installation failed with status 2
E:Can't open tmp/update-script.log
E:Can't load volume/misc!
Click to expand...
Click to collapse
Any ideas how I can get past this?

UPDATE #2 [SOLVED]
I initially thought of going ladder steps up but then out of curiosity searched for ASUS Zenfone 5 Marshmallow and came across this.
Here is what I did:
1. Unlocked bootloader (cause it was initially locked)
fastboot flash fastboot fastboot_unlocker.img
fastboot reboot-bootloader
fastboot flash dnx dnx_fwr_ctp_a500cg.bin
fastboot flash ifwi ifwi_ctp_a500cg_unlock.bin
fastboot reboot-bootloader
Click to expand...
Click to collapse
2. Downloaded and flashed boot image. I used cm13-zenfone5-kernel.img
fastboot flash boot cm13-zenfone5-kernel.img
Click to expand...
Click to collapse
3. Downloaded and flashed recovery image. I used TWRP.img
fastboot flash recovery TWRP.img
Click to expand...
Click to collapse
4. Downloaded and flashed system image. I used cm13-zenfone5-system.img
fastboot flash system cm13-zenfone5-system.img
Click to expand...
Click to collapse
5. Erased unneeded files
fastboot erase data
fastboot erase userdata
fastboot erase cache
Click to expand...
Click to collapse
6. I installed open_gapps-x86-6.0-pico-20200207.zip (Open Google Apps Pico version)
7. I did some memory cleaning factory reset then dalvik cache and cache wipe
8. My TWRP froze on reboot system so I unplugged/replugged the USB cable then I did an adb reboot which is the same thing as Power+Volume Up button.
Click to expand...
Click to collapse
And voila! A running marshmallow OS on Asus Zenfone 5 t00j a500cg.
Overall, I spent 2 days trying to do this but it was well worth it. My son is very happy he can now play his MOBA faster than the original bloated KitKat OS. Same hardware, better software. Overall, I enjoyed the learning experience and the joy of being appreciated by my son.