Is it possible to extract a copy of a system image from an updated G4+? Like the boot.img, recovery.img, system.img, etc? To be flashed in fastboot
Yep. You have to flash TWRP and backup all img's. They'll appear with 'win' extension, so just change them to 'img'.
PocketGorgon said:
Is it possible to extract a copy of a system image from an updated G4+? Like the boot.img, recovery.img, system.img, etc? To be flashed in fastboot
Click to expand...
Click to collapse
Flashfire app has a fastboot compatible image backup feature.
I need the files to fix my g4
Related
after unzip factory image
it have bootloader.img, boot.img, recovery.img, system.img, userdata.img
userdata.img size is about 100M
but even i do not flash userdata.img, my nexus still can boot to the android 4.1.2
i don't know this userdata.img contain which data?
is it contain any Gapp which is not in the system?
anyone know?
ygvuhb said:
after unzip factory image
it have bootloader.img, boot.img, recovery.img, system.img, userdata.img
userdata.img size is about 100M
but even i do not flash userdata.img, my nexus still can boot to the android 4.1.2
i don't know this userdata.img contain which data?
is it contain any Gapp which is not in the system?
anyone know?
Click to expand...
Click to collapse
The userdata.img file is a blank partition. It is used to reset the userdata partition to its factory state (completely empty) and is not needed if you're just using the stock images (boot.img, system.img) to update to 4.1.2
comminus said:
The userdata.img file is a blank partition. It is used to reset the userdata partition to its factory state (completely empty) and is not needed if you're just using the stock images (boot.img, system.img) to update to 4.1.2
Click to expand...
Click to collapse
Okay, that's what I thought it was too, but then why is it 140MB? I mean I could see it being a few kilobytes for a directory table, or the size of the partition if it was an uncompressed image, but 104286KB for the Nexu7 and 137555KB for the Galaxy Nexus seems pretty arbitrary to me.
comminus said:
The userdata.img file is a blank partition. It is used to reset the userdata partition to its factory state (completely empty) and is not needed if you're just using the stock images (boot.img, system.img) to update to 4.1.2
Click to expand...
Click to collapse
Found this out the hard way.
Sent from my Galaxy Nexus using Tapatalk 2
Hi there
I've built Firefox OS for the Galaxy Nexus but I'm struggling to find a way of creating a flashable zip to distribute.
This is my first ROM that I have successfully compiled, but everything seems to be working so I wouldn't mind sharing it with the rest of the internet. Any tips?
Thanks!
ojdon said:
Hi there
I've built Firefox OS for the Galaxy Nexus but I'm struggling to find a way of creating a flashable zip to distribute.
This is my first ROM that I have successfully compiled, but everything seems to be working so I wouldn't mind sharing it with the rest of the internet. Any tips?
Thanks!
Click to expand...
Click to collapse
After building from the B2G directory (the folder from where you run ./config.sh and ./build.sh) you should locate boot.img, userdata.img and system.img and copy them over to a folder, then you can flash using fastboot via:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot erase cache
fastboot reboot
janjongboom said:
After building from the B2G directory (the folder from where you run ./config.sh and ./build.sh) you should locate boot.img, userdata.img and system.img and copy them over to a folder, then you can flash using fastboot via:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
Firefox OS in Galaxy Nexus, I want to take a look! Keep us up to date man!
janjongboom said:
After building from the B2G directory (the folder from where you run ./config.sh and ./build.sh) you should locate boot.img, userdata.img and system.img and copy them over to a folder, then you can flash using fastboot via:
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash userdata userdata.img
fastboot flash system system.img
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
Ah didn't know this thread had replies so sorry for a bit of a bump. I was kind of after directions on how to create a flashable zip? It's just that I was aiming to avoid end users from using adb and fastboot. Do you know how to create a flashable zip instead?
Thanks for the guidance!
Hello, I'm looking for a Nandroid Backup for Nova CL 01 , car after intallation of Twrp to test the lineage Version System and Cust Partitions are decreases , and I can't reinstall the Firmware car system and cust are so larger than their partitions ,
I have another probleme , in lineage os I have not Data , lte ........just wifi ?
Help Please
In TWRP reboot into bootloader and flash stock recovery via fastboot command. Then the memory card to copy into folter DLOAD file update.app stock firmware version of you phone L01 and run phone with press button volume down,up.
Updates starts and the phone should then work again.
Sorry my english.
testous3 said:
Hello, I'm looking for a Nandroid Backup for Nova CL 01 , car after intallation of Twrp to test the lineage Version System and Cust Partitions are decreases , and I can't reinstall the Firmware car system and cust are so larger than their partitions ,
I have another probleme , in lineage os I have not Data , lte ........just wifi ?
Help Please
Click to expand...
Click to collapse
https://forum.xda-developers.com/nova-plus/help/l01-cust-failed-t3537415/page4
mArIuS% said:
https://forum.xda-developers.com/nova-plus/help/l01-cust-failed-t3537415/page4
Click to expand...
Click to collapse
I can't flash Cust.img and System.img because partition is no larger than files , its my main problem
testous3 said:
I can't flash Cust.img and System.img because partition is no larger than files , its my main problem
Click to expand...
Click to collapse
I got the same problem. Flash firmweare with fastboot, download ota with firmweare finder, copy update.app on your pc, extract with huawei extract tool boot.img, recovery.img and system.img(put the extracted images in the root of fastboot folder on your pc) and flash them with fastboot.
Open comand promt and write:
1.cd /adb (hit enter) between cd and /and hit space
2.fastboot flash boot boot.img
3.fastboot flash recovery recovery.img
4.fastboot flash system system.img
5.fastboot reboot
and then wait the phone to reboot.
You have installed android nougat and now you cannot go back to marsmallow cuz partition size is different.
mArIuS% said:
I got the same problem. Flash firmweare with fastboot, download ota with firmweare finder, copy update.app on your pc, extract with huawei extract tool boot.img, recovery.img and system.img(put the extracted images in the root of fastboot folder on your pc) and flash them with fastboot.
Open comand promt and write:
1.cd /adb (hit enter) between cd and /and hit space
2.fastboot flash boot boot.img
3.fastboot flash recovery recovery.img
4.fastboot flash system system.img
5.fastboot reboot
and then wait the phone reboot.
You have installed android nougat and now you cannot go back to marsmallow cuz partition size is different.
Click to expand...
Click to collapse
I Think the solution is tu restore a full Backup from another Device , anyone has a full backup or Can do a backup please ?
A friend accidentally erased system partition. Phone enters TWRP and fastboot but I can't update with update.App so I'm looking for a dumped system.img (or a way to make a system.img from the unsparse files (unsparse joiner didn't work) to try to revive the phone.
Thank you
Hi everyone,may some of you need to back to stock Emui here some simple method which working fine, and i've try myself.
Things needed:
-Download these 4 images files, you can get it here
https://mega.nz/#!0s9y0QJA!dqtNYSObqGXZvx-z4z6c4W6Az4_kRS7rnvzKzkgQpms
-Make sure you have adb&fastboot working, you guys really know what's this really well.
-Download and extract the files, make it easier folder/dir.
-Flash each files as its named
Fastboot flash recovery_ramdisk recovery_ramdisk.img
Fastboot flash ramdisk ramdisk.img
Fastboot flash cust cust.img
Fastboot erase system
Lets wait till process done
Fastboot Flash system system.img
When you need to re-lock bootloader use Huawei Multi-Tool
And all those files extracted using Huawei MT, based on latest Oreo HW_eu.
Don't try to use the files on other model, when you do..do it with your own risk.
I decided to type and flash it manualy after faced some error on system partition using Huawei MT.