Develop Bugs

Can somebody explain how to update to 4.0.2

i just unlocked the bootloader and downloaded the firmware from google (4.0.2 (ICL53F)). As detailed as you can be for a noob, now what? lol, thanks!
Also i have the gsm version, "yakju" for Galaxy Nexus "maguro".

As far as I know, you simply have to unzip the archive and flash the bootloader, radio, recovery, and system images

Extract the tgz
fastboot flash bootloader bootloader-maguro-primekk15.img
fastboot flash radio radio-maguro-i9250xxkk6.img
fastboot reboot-bootloader
fastboot update image-yakju-icl53f.zip
Note no -w on the update. Adding -w will wipe the device before applying the update

ok where exactly do i unzip this file, and how do i flash? i need details!

EDIT: Unzip the files to the same directory as fastboot and open a terminal session in that folder/or CD to that folder.

ok cool, one last question.. when i extract the file it creates a folder in the directory with the files in it. do i take the files and put it in the directory where the folder was created or leave it

Will this lock my bootloader again if I've unlocked it before?

Proyoyo said:
Will this lock my bootloader again if I've unlocked it before?
Click to expand...
Click to collapse
No
10 chars

So those codes are what I type into terminal correct?
and to enter into fastboot its volume up & volume down and power key
i guess i cant just do flash all? if so whats the command?
Sent from my Nexus One using XDA App

krohnjw said:
Extract the tgz
fastboot flash bootloader bootloader-maguro-primekk15.img
fastboot flash radio radio-maguro-i9250xxkk6.img
fastboot reboot-bootloader
fastboot update image-yakju-icl53f.zip
Note no -w on the update. Adding -w will wipe the device before applying the update
Click to expand...
Click to collapse
1. All settings/apps/data will be preserved when using this method right?
2. Also will this preserve root?

Thanks for the guide. Just flashed mine. Everything went perfect.
Sendt fra min Galaxy Nexus med Tapatalk

gabster21 said:
1. All settings/apps/data will be preserved when using this method right?
2. Also will this preserve root?
Click to expand...
Click to collapse
ok i just used fastboot to unlock the bootloader... but when i type in fastboot flash bootloader bootloader-maguro-primekk15.img it says 'fastboot' is not recognized as an internal or external command, operable program or batch file.... what now! i extracted the 4.0.2 update to the root of my hard drive

Please Help Me Phone Wont Boot

I tried to Update my GSM GN to Ver 4.0.2 using the manual instructions.
I first downloaded the image for my build (ITL42F). I placed the files in the same folder as the fastboot. then followed the instructions below.
fastboot flash bootloader bootloader-maguro-primekk15.img except file name was primekj10
fastboot reboot-bootloader
(wait for bootloader to reboot)
fastboot flash radio radio-maguro-i9250xxkk6.img except file name was i9250xxkk1.img
fastboot reboot-bootloader
(wait for bootloader to reboot)
fastboot update image-yakju-icl53f.zip except file name was itl41f.img.
Shows everything was ok and the phone started to reboot. I get the animation screen for 10 minutes but the phone wouldn't boot into the system screen. Please help me.
Joe

Are you sure you had the correct version? ICL53F is 4.0.2. Try using the images here.

Thanks going to try and report.

Reflash with ICL53F
Used the right image file now, the only thing I noticed was when I used the last command "update image-yakju-icl53f.zip" i got
archive does not contain "boot.sig"
archive does not contain "recovery.sig"
archive does not contain "system.sig"
Bootloader Version rimekk15
Baseband Version: I9250kk6
Serial Number:,,,,,,,,,,
Afterwards it run the image and show okay on the bottom and the phone reboot, but still just the animation is on and the phone is not booting to the system.
Any ideas please.
Joe.

From what you wrote it seems like you didn't wipe data.
Your final command should be:
Code:
fastboot -w update image-yakju-icl53f.zip

That was my lsat command and the above showed up. It seems to have ran everything but still not booting.

OK. Because your original post didn't have the -w flag before the "update image-yakju-icl53f.zip" so I assumed you didn't wipe.
Are you currently trying to flash the 4.0.2 build? If so, follow these commands exactly:
Code:
fastboot flash bootloader bootloader-maguro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-maguro-i9250xxkk6.img
fastboot reboot-bootloader
fastboot -w update image-yakju-icl53f.zip

Workssssssss
You are the man, thank you so much. The -w is what I was missing, now it's working again. I have 4.0.2.....
Thanks again
Joe

No problem man.

error on ascend P6

i have a error on ascend P6 its stuck on android logo and in recovery its shows the error i attached a pic. i tried the dload option for software but it doesnt work , please help . i got this phone like this condition only . i dont know history .

missime said:
i have a error on ascend P6 its stuck on android logo and in recovery its shows the error i attached a pic. i tried the dload option for software but it doesnt work , please help . i got this phone like this condition only . i dont know history .
Click to expand...
Click to collapse
Does it have an SDcard in it with a rom in /dload? It sounds like it may be looking for this. Get a card in it and do a force reset (volume up/down pressed and power button pressed .

stuartggray said:
Does it have an SDcard in it with a rom in /dload? It sounds like it may be looking for this. Get a card in it and do a force reset (volume up/down pressed and power button pressed .
Click to expand...
Click to collapse
yeah its loaded in . it just goes to recovery .
P6_firmware(P6-U06,Android_4.2,Emtion_UI,V100R001C00B107,Normal,05011RJP)
this is the zip i have extracted it dload/update.app
is there any other way to load it ?

any adb command to psh the update.app file atleast . coz in recovery its taking adb drivers .

missime said:
any adb command to psh the update.app file atleast . coz in recovery its taking adb drivers .
Click to expand...
Click to collapse
any solution for this error?

in fast boot mode, using adb to flash every *.img file to phone.
Code:
adb wait-for-device
adb.exe reboot bootloader
fastboot.exe flash fastboot fastboot.img
fastboot.exe flash boot boot.img
fastboot.exe flash recovery recovery.img
fastboot.exe flash batt batt.img
fastboot.exe flash cache cache.img
fastboot.exe flash crc crc.img
fastboot.exe flash curver curver.img
fastboot.exe flash efi efi.img
fastboot.exe flash md5rsa md5rsa.img
fastboot.exe flash modemimage modemimage.img
fastboot.exe flash userdata userdata.img
fastboot.exe flash verlist verlist.img
fastboot.exe flash system system.img
fastboot.exe flash cust cust.img
fastboot reboot

vagraxy said:
in fast boot mode, using adb to flash every *.img file to phone.
Code:
adb wait-for-device
adb.exe reboot bootloader
fastboot.exe flash fastboot fastboot.img
fastboot.exe flash boot boot.img
fastboot.exe flash recovery recovery.img
fastboot.exe flash batt batt.img
fastboot.exe flash cache cache.img
fastboot.exe flash crc crc.img
fastboot.exe flash curver curver.img
fastboot.exe flash efi efi.img
fastboot.exe flash md5rsa md5rsa.img
fastboot.exe flash modemimage modemimage.img
fastboot.exe flash userdata userdata.img
fastboot.exe flash verlist verlist.img
fastboot.exe flash system system.img
fastboot.exe flash cust cust.img
fastboot reboot
Click to expand...
Click to collapse
how did u flash the system img...it say its too big..any suggestion please

[Flashing STOCK ROM from Custom Rom] [No Recovery Mode, Fastboot accessible]

I followed these steps and now my Asus zf2 (ze551ml) is back alive! For the issue mentioned below, I didn't find much anywhere so I thought I'd put here what helped me.
Issue: Only fastboot mode accessible, can't enter recovery. (Also my bootloader was locked, MM bootloader, No OS). After selecting recovery mode from bootloader, again it enters fastboot, i.e the process in video above couldn't install the recovery (This must be because my bootloader was locked). I tried unlocking the bootloader by the .bat files available on XDA but since I'd not enabled OEM unlocking, unlocking failed everytime. My OS got wiped out, so only fastboot mode was accessible.
Solution:
I believe you have installed Minimal ADB and fastboot on your PC.
Download the raw file from the XDA thread.
Now first of all, change extention of the .raw firmware file to .zip.
Then just extract all files from it into adb and fastboot folder.
Now in folder (where you placed files from raw firmware and adb and fastboot tool folder) at empty place anywhere in folder hold Shift on computer keyboard and right click with mouse. Now click open command window here.
Perform the following commands one after another:
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again, if USB debugging was on then this will definitely work)
2. fastboot oem erase_osip_header
3. fastboot oem start_partitioning
4. fastboot flash /tmp/partition.tbl partition.tbl
5. fastboot oem partition /tmp/partition.tbl
6. fastboot erase system
7. fastboot erase cache
8. fastboot erase data
9. fastboot erase APD
10. fastboot erase ADF
11. fastboot oem wipe splashscreen
12. fastboot oem stop_partitioning
13. fastboot flash splashscreen splash_sign.bin
14. fastboot flash token MFG_BOM_Full.bin
15. fastboot flash ifwi ifwi-prod.bin
16. fastboot flash boot boot_sign.bin
17. fastboot flash recovery recovery_sign.bin
18. fastboot flash fastboot droidboot_sign.bin
19. fastboot flash APD APD.img
20. fastboot flash system system.img
21. fastboot reboot
Phone will successfully reboot into system. Don't worry, first boot gonna take a little longer time.

Download raw file
Hello,
From where I can download raw file? Can you please provide a link?
Thanks in advance

bb04 said:
Hello,
From where I can download raw file? Can you please provide a link?
Thanks in advance
Click to expand...
Click to collapse
OP forgot to post link from he copied commands.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785

sukhwant717 said:
OP forgot to post link from he copied commands.
https://forum.xda-developers.com/zenfone2/help/thead-bricked-phone-updating-to-mm-tips-t3452785
Click to expand...
Click to collapse
FYI, I didn't add the links because one can't add external links in their first posts.

mukunds11 said:
FYI, I didn't add the links because one can't add external links in their first posts.
Click to expand...
Click to collapse
it could be better if you would have removed or edited last line while copying commands

help. my phone condition is just like this. at first when i connected my phone to computer, powershell detected it, but then after a while, my phone disappeared from powershell. can someone help me ?
edit, i just did the thing and its doing fine even though my phone look like it is not detected

Question Does anyone have FULL Fastboot Flashing steps?

Does anyone have the full fastboot flashing steps from the Bootloader to everyfile in the image file.zip?

I'm not sure exactly what you're asking. To be rooted? To merely flash full stock firmware? If the latter, just extract the full firmware zip and the latest Platform Tools into the same folder. If you don't want to wipe your phone, edit the Flash-All.bat with Notepad (assuming you're running Windows) and remove the "-w ", and save the file. Then open a command prompt in that folder, type Flash-All.bat and press enter. That's it.
If you're asking what are the steps the Flash-All.bat takes to flash everything that's in the inner zip file that's unextracted, just open the Flash-All.bat with Notepad and take a look.
If you're wanting to be rooted, [GUIDE] Root Pixel 6 Pro with Magisk.
If none of my guesses are correct, please be more specific of what exactly you're asking.

Wouldn't it be just fastboot flash filename "file location" for each file?

spart0n said:
Wouldn't it be just fastboot flash filename "file location" for each file?
Click to expand...
Click to collapse
Every device is different, with Motorola we started with :
fastboot gat-var
and flashed each image seperately.

The "flash-all.bat" only does a "fastboot update <update.zip>" - so no individual flashing of image files.....

s3axel said:
The "flash-all.bat" only does a "fastboot update <update.zip>" - so no individual flashing of image files.....
Click to expand...
Click to collapse
Yea, but i cannot tell where the image.zip is getting hung up at if i run that.

AndroidAddict420 said:
Yea, but i cannot tell where the image.zip is getting hung up at if i run that.
Click to expand...
Click to collapse
You could open a command shell and run the flash-all.bat from there - then you at least see the output of the command.
Or you can enter the commands from the flash-all.bat manually in a commandline window (everything starting with "fastboot..." )....

s3axel said:
You could open a command shell and run the flash-all.bat from there - then you at least see the output of the command.
Or you can enter the commands from the flash-all.bat manually in a commandline window (everything starting with "fastboot..." )....
Click to expand...
Click to collapse
I am using LIX

AndroidAddict420 said:
I am using LIX
Click to expand...
Click to collapse
OK, I don't know LIX - is that some kind of Linux ?
I would still assume you can execute the dividual fastboot commands from the flash-all.bat (flash-all.sh) manually ?!

s3axel said:
OK, I don't know LIX - is that some kind of Linux ?
I would still assume you can execute the dividual fastboot commands from the flash-all.bat (flash-all.sh) manually ?!
Click to expand...
Click to collapse
LIX is short for Linux

I'm not sure if fastboot would work in a Linux terminal window as I've always used Windows... Best of luck finding a solution!
Oh, and by the way, you can use fastboot in CMD and flash individual partitions with it. An example command of flashing the bootloader file would be:
"fastboot flash bootloader bootloaderfilename.img"
You essentially just have to change the last word before the filename to flash different partitions (aside from when you're flashing the update image, as it's a little bit different then).
Also note that the bootloader.img file would have to be in the exact same location as your adb and fastboot files. But again, I'm not at all sure how it would work on Linux...

NippleSauce said:
I'm not sure if fastboot would work in a Linux terminal window as I've always used Windows... Best of luck finding a solution!
Oh, and by the way, you can use fastboot in CMD and flash individual partitions with it. An example command of flashing the bootloader file would be:
"fastboot flash bootloader bootloaderfilename.img"
You essentially just have to change the last word before the filename to flash different partitions (aside from when you're flashing the update image, as it's a little bit different then).
Also note that the bootloader.img file would have to be in the exact same location as your adb and fastboot files. But again, I'm not at all sure how it would work on Linux...
Click to expand...
Click to collapse
Why would anyone ever change their bootloader?

spart0n said:
Why would anyone ever change their bootloader?
Click to expand...
Click to collapse
To update it.

If you want to flash each image separately, you can follow these steps (for some images, sequence is important, so I suggest following the sequence below to avoid issues)
Code:
################################################
### Files from the root of the factory image zip
################################################
# bootloader (replace <version> with the bootloader file version)
fastboot flash bootloader bootloader-raven-slider-<version>.img
# reboot to bootloader
fastboot reboot bootloader
# radio (replace <version> with the radio file version)
fastboot flash radio radio-raven-<version>.img
# reboot to bootloader
fastboot reboot bootloader
#####################################################
### Files from the image zip in the factory image zip
#####################################################
# boot
fastboot flash boot boot.img
# dtbo
fastboot flash dtbo dtbo.img
# vbmeta
fastboot flash vbmeta vbmeta.img
# vbmeta_system
fastboot flash vbmeta_system vbmeta_system.img
# vbmeta_vendor
fastboot flash vbmeta_vendor vbmeta_vendor.img
# vendor_boot
fastboot flash vendor_boot vendor_boot.img
# reboot to fastboot
fastboot reboot fastboot
# super
fastboot flash super super_empty.img
# product
fastboot flash product product.img
# system
fastboot flash system system.img
# system_ext
fastboot flash system_ext system_ext.img
# system_other (replace <other> with the inactive slot)
fastboot flash system_<other> system_other.img
# vendor
fastboot flash vendor vendor.img
# vendor_dlkm
fastboot flash vendor_dlkm vendor_dlkm.img
# reboot
fastboot reboot