Hello,
I just downloaded a rom and it's in .img form, specifically, this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I really want to flash it, but I'm clueless how to do that on a modern TWRP on a Z1.
Yeah yeah fastboot flash boot boot.img etc. I know I can do that, the case here is that I'm using multirom and having the rom in a flashable rom would get the rom to work with multirom, flashing with fastboot will overwrite my stock rom that I'd rather keep.
Thank you for any info. Most of the guides are weird or outdated, that's why I posted this.
BUMP
olokos said:
BUMP
Click to expand...
Click to collapse
In ubuntu take the img and do
mkdir system
mount -o loop -t ext4 system.img system
This should mount the system.img in the system folder which lets you get all the files.
From there you can make a flashable zip (easiest way is to probably copy a zip that flashes system)
ChrisJ951 said:
In ubuntu take the img and do
mkdir system
mount -o loop -t ext4 system.img system
This should mount the system.img in the system folder which lets you get all the files.
From there you can make a flashable zip (easiest way is to probably copy a zip that flashes system)
Click to expand...
Click to collapse
I already have the system.img I want to flash it with either fastboot or zip. Thanks for that though.
olokos said:
I already have the system.img I want to flash it with either fastboot or zip. Thanks for that though.
Click to expand...
Click to collapse
There is plenty of info on Google for doing this, just search for "how to convert .IMG to flashable zip" and you'll find several ways to do this.
Related
I've spent the past 4 hours flashing roms to my phone just to see what works and what doesn't. I could easily say that 30% of that time could be added to productivity if I could ODIN into a semi-stock rom that has a custom recovery file already in /./system/bin. How do I do this?
You would get your phone to the state that you want, and then pull system images using DD, and package them using tar.
http://androidforums.com/behold-2-all-things-root/54424-creating-custom-roms-backups-odin.html
I would suggest that you just use the custom system instructions on that page, and then use the rest of the parts from Ayoteddy's original KG2 odin post, just to be sure that nothing goes wrong with the bootloader. the system part is factoryfs.rfs
sduvick said:
You would get your phone to the state that you want, and then pull system images using DD, and package them using tar.
http://androidforums.com/behold-2-all-things-root/54424-creating-custom-roms-backups-odin.html
I would suggest that you just use the custom system instructions on that page, and then use the rest of the parts from Ayoteddy's original KG2 odin post, just to be sure that nothing goes wrong with the bootloader. the system part is factoryfs.rfs
Click to expand...
Click to collapse
Legit dude. Thanks for the heads up. Might make my own rom pretty soon.
No prob, hope to see it up here.
The only file I am modifying resides in /./system/bin, thus the only partition I have to dump is bml9. Is this correct?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The sizes. Did he do an
Code:
$ ls -l
then take the size in bits and just add a plus sign for the tail command? If this is something I should do for myself do not respond.
Yes, only worry about bml9. Don't worry about the kernel piece in there, that's irrelevant. If you just root it and add the modded recovery, make sure that it works, then pull the bml9 (or stl9, can't remember which is in that thread), that will add root and CWM
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
nico000 said:
https://imgur.com/a/TuGwEiA
Click to expand...
Click to collapse
System,Cust,Boot and Recovery
letschky said:
System,Cust,Boot and Recovery
Click to expand...
Click to collapse
yes, what I do not understand and in those images that I mentioned, which files are to be taken
nico000 said:
yes, what I do not understand and in those images that I mentioned, which files are to be taken
Click to expand...
Click to collapse
You can flash via fastboot:Ramdisk,Cust,Ramdisk_Recovery and System.
Install Adb Drivers.https://forum.xda-developers.com/showthread.php?t=2588979
Install Huawei Hisuite http://consumer.huawei.com/minisite/HiSuite_en/
Reboot into Bootloader and type in Cmd:
fastboot flash ramdisk RAMDISK.img
fastboot flash system SYSTEM.img
fastboot flash cust CUST.img
fastboot flash recovery_ramdisk RECOVERY.img
Your Bootloader must be Unlocked!
letschky said:
You can flash via fastboot:Ramdisk,Cust,Ramdisk_Recovery and System.
Install Adb Drivers.https://forum.xda-developers.com/showthread.php?t=2588979
Install Huawei Hisuite http://consumer.huawei.com/minisite/HiSuite_en/
Reboot into Bootloader and type in Cmd:
fastboot flash ramdisk RAMDISK.img
fastboot flash system SYSTEM.img
fastboot flash cust CUST.img
fastboot flash recovery_ramdisk RECOVERY.img
Your Bootloader must be Unlocked!
Click to expand...
Click to collapse
so in my UPDATE.APP file I have to extract the following files, right
ramdisk_a.img
system_a.img
cust_a.img
recovery_ramdisk_a.img
SmartPhonesFan said:
What the heck u trying to do?
Click to expand...
Click to collapse
and only as a precaution, if my phone should have problems at least reset everything so, and can also be useful to other people
so in my UPDATE.APP file I have to extract the following files, right
ramdisk_a.img
system_a.img
cust_a.img
recovery_ramdisk_a.img
Hello
i have a 4G modem and it has stuck on welcome problem and i want to flash it but i have only found a update.zip file (it's OTA update).
it's contents are like the attached picture.
it has fastboot mode and go to it without problem.
how can i flash this zip file or it's contents to have a fresh devices?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
any idea?
x23are said:
Hello
i have a 4G modem and it has stuck on welcome problem and i want to flash it but i have only found a update.zip file (it's OTA update).
it's contents are like the attached picture.
it has fastboot mode and go to it without problem.
how can i flash this zip file or it's contents to have a fresh devices?
View attachment 4706463
Click to expand...
Click to collapse
The stock update.zip(or any other OTA update) is meant to be flashed using stock recovery.
Store the update.zip on your device's internal sdcard then boot into stock recovery and choose the update from sdcard option then choose your update file and flash it.
Sent from my LGL84VL using Tapatalk
Droidriven said:
The stock update.zip(or any other OTA update) is meant to be flashed using stock recovery.
Store the update.zip on your device's internal sdcard then boot into stock recovery and choose the update from sdcard option then choose your update file and flash it.
Sent from my LGL84VL using Tapatalk
Click to expand...
Click to collapse
IT is a modem and dont has recovery.
it has only fastboot mode.
is there a way to flash files one by one ?
in update.zip file there are some mbn files and a boot.img but system and userdata and data are .7z like the picture i uploaded.
I tried to install Micro-g and still can't figure out if is it possible to mount system as read-write on OxygenOs 10. Standart command to do this
Code:
mount -o rw,remount /system
and many others from internet dont work. Is it possible to do this on OxygenOs 10?
Odalric said:
I tried to install Micro-g and still can't figure out if is it possible to mount system as read-write on OxygenOs 10. Standart command to do this
Code:
mount -o rw,remount /system
and many others from internet dont work. Is it possible to do this on OxygenOs 10?
Click to expand...
Click to collapse
No, OOS is read only. I gave up and installed PixelExperince 10.0 , removed all google stuff, installed microg, patched services.jar and all set .
Here is the solution to your problem my friends. Enjoy!
Works like a charm in Android 10 and later. Now my system, vendor and product partitions are read-write!
Use at your own risk!
https://forum.xda-developers.com/t/script-mount-system-as-read-write-android-10.4240703/
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
While the above might work, you don't need to extract the whole super partitions. You can do it manually on whatever partition you wish.
Make Dynamic Partition Read/Write (github.com)
@Lossyx that's interesting thanks for the feedback. Yes you're right it should be possible to do the whole process directly on the device without having to pull the whole super.img first. But it shouldn't really matter if you do it with the help of your computer or directly on the device itself.
However people decide to do it, what's important is that the Android 10+ users get write access to all their partitions again so we can customize our device to fit our needs and remove all that bloatware and then some.
It seems that I did everything right, I installed the custom rainbow kernel on the stock firmware, the kernel worked, there only at startup it gave out the message "SSHL Warning" like so.
When I decided to install GSI, a bootloup occurred. You can write the reason or guesses.
I have only one screenshot left from TWRP.
Thanks in advance!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
what model do you have? If it is an A127F then use chondoe flasher, if it is an A125F, maybe try using a kernel if that doesn't work maybe chondoe flasher will work.
ChonDoe Flasher is below (For me ChonDoe always worked)
TheWorldYT said:
what model do you have? If it is an A127F then use chondoe flasher, if it is an A125F, maybe try using a kernel if that doesn't work maybe chondoe flasher will work.
ChonDoe Flasher is below (For me ChonDoe always worked)
Click to expand...
Click to collapse
i have A125F i used rainbow kernel
Test Superior
lil_kyrick said:
i have A125F i used rainbow kernel
Click to expand...
Click to collapse
Try to flash a new version of lineage (BgS) with ChonDoe Flasher (Like Lineage 19 or 20)
here are how you install the gsi with chondoe flasher:
Rename the .img file to system.img then copy the ChonDoe_Flasher.zip file at post #2 in the directory where the .img file is, then flash the ChonDoe_Flasher.zip as a zip file. Then, flash the kernel, and format data, then reboot your phone!
Here is a link to lineage 19 BgS: https://sourceforge.net/projects/an...2-UNOFFICIAL-arm64_bgN-secure.img.xz/download (Unzip to get the image)