So I built the android source and got the system.img (and userdata.img, ramdisk.img, boot.img, etc.) files, but I can't use fastboot to flash them because I have a rogers branded phone.
Is it possible to get .sin files from these so I use FlashTool to flash them instead?
Related
Hey!
So I unpacked and repacked the boot.img 8 MB on Linux and it made two .img files boot.img-kernel 3,9 MB and rooted.img 4,3 MB So Do I have to use both of them? can I just repack them to one file boot.img?
I followed this guide to make insecure boot.img:
http://www.mydroidworld.com/topic/9778-how-to-create-an-insecure-boot-image/
what to do? how to flash both of them? (via CWM)
Please help!
Ok, back in my HTC Desire HD days I could rename a prepared radio zip file to PD98IMG.zip, move the file to my SD-card root, then go to fastboot and the file was immediately recognized as flashable and I could choose to flash it, without going through adb.
Is there any similar method in Gnex?
For instance, I would like to flash a ClockworkMod Recovery update file straight from fastboot, without adb commands (i.e. a PC).
Thanks.
no. HTC phones use hboot which is their own bootloader written to look for that file name.
Thanks!:good:
In the Nexus, you flash raw images through fastboot.
'fastboot flash <partition_name> filename.img'
Partition names available: system, boot, recovery, userdata, logo.bin
Edit: read the stickies
http://forum.xda-developers.com/showthread.php?t=1812959
Sent from my i9250
After moving my Mi6 from EU ROM to Global Stable 8.2.2.0, I realised that MIUI has now programmed either the boot.img or system.img to overwrite recovery partition on every "normal"/system boot.
So much for unlocking the bootloader...
Although the source system.img has a recovery-from-boot.p file, but it appears to be different from the stock recovery.img file. Attempting to replace it with the TWRP image or removing it entirely (and flashing the rebuilt system.img) results in boot failure (see below for more information).
Does anyone know:
where the "protected" recovery image may be found? and/or
how to repack/rebuild a system.img which will not cause a boot hang?
Note that I have rebuilt it "correctly" (as "correct" as I know) using the properly extracted file_contexts (as extracted from the file_contexts.bin) from the initrd.img from inside the boot.img using the command:
Code:
make_ext4fs -s -T -1 -S file_contents -L system -l <size of partition> -a system system.img <mount point>
I have tried both a blind fastboot flash system system.img, and also a standard "clean" flash using the MiFlash tool (after ensuring that the correct MD5, CRC and sparse CRC strings are edited in the various files, of course).
Thanks!
fastboot flash recovery TWRP.img
That's the solution.
And if you flash a MIUI rom with TWRP simply flash twrp.img without Reboot under TWRP, after rom.zip flash. That's all
reb00tz said:
After moving my Mi6 from EU ROM to Global Stable 8.2.2.0, I realised that MIUI has now programmed either the boot.img or system.img to overwrite recovery partition on every "normal"/system boot.
Click to expand...
Click to collapse
dennis46419 said:
fastboot flash recovery TWRP.img
That's the solution.
And if you flash a MIUI rom with TWRP simply flash twrp.img without Reboot under TWRP, after rom.zip flash. That's all
Click to expand...
Click to collapse
Hi @dennis46419,
Thanks for replying. I have always done that upon forced reboot by the MiFlash tool (i.e. the moment it powers off for a reboot, I put it right back into fastboot mode to flash TWRP again, then directly boot with the TWRP.img).
As mentioned, I believe the new global stable ROM actually overwrites recovery on every boot.
Have you experienced this (i.e. when using the global stable ROM)?
OK, seems I missed the solution as already provided by @TheStrix:
https://forum.xda-developers.com/showpost.php?p=72620133&postcount=2
But the instruction (which I missed because I downloaded directly from the TWRP site) was already here: https://forum.xda-developers.com/showpost.php?p=72620133&postcount=2
Hi all,
I'm sorry to ask this question, but I'm really struggling to get my Nexus 5X to boot into stock rom. The install seems to go ok, but there was error when flashing.. See below...
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
The phone now boots to the google boot logo, then loops back to either the "Unlocked Bootloader" or the Custom OS message. (depending on the locked state of the bootloader)
I cannot get into recovery, as the phone just loops back as described above when selecting it from the bootloader option.
Can anyone advise me on how to restore the phone back to stock os. I've tried flashing version 7.1.2 8.0.0 and 8.1.0, using either the flash-all.bat or manually typing the commands. I'm 110% sure this is not to do with over heating on CPU/RAM, I have another nexus 5x that has the bootloop of death and it's bootloop is very different from what I'm seeing on this Nexus 5x.
Thanks in advance
First, the .sig errors are normal so you can ignore those. I would make sure your booloader is unlocked then manually flash the bootloader.img. Then boot back into the bootloader. Then manually flash the remainder of the partitions. Use the 8.1.0 os.
Sent from my [device_name] using XDA-Developers Legacy app
Ok here's what I've done.
1) Downloaded bullhead-opm2.171019.029.zip from Google factory images.
2) Extracted the zip to a folder and extracted image-bullhead-opm2.171019.029.zip to the same folder to get the boot.img | system.img | vendor.img and recovery.img file. (there was no userdata.img nor cache.img within the zip, so I downloaded 7.1.1 version and extracted those files too)
3) Using SDK tools ADB /Fastboot version 1.0.38, I flashed the following:-
fastboot flash bootloader C:\bullhead\images\bootloader-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\bullhead\images\radio-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\bullhead\images\boot.img
fastboot erase cache
fastboot flash cache C:\bullhead\images\cache.img
fastboot flash recovery C:\bullhead\images\recovery.img
fastboot flash system C:\bullhead\images\system.img
fastboot flash vendor C:\bullhead\images\vendor.img
fastboot flash userdata C:\bullhead\images\userdata.img
fastboot oem lock
Everything flashed without a problem, no error. However the phone still does not boot into the OS nor can I get it to boot into recovery mode.
I cannot understand what I am doing wrong. I think it has something to do with the installation of copperhead I tried. Does anyone know whether copperhead os restricts going back to stock rom due to its additional security features?
I'm stuck!!!
Thanks in advance.
pinkstink said:
Ok here's what I've done.
1) Downloaded bullhead-opm2.171019.029.zip from Google factory images.
2) Extracted the zip to a folder and extracted image-bullhead-opm2.171019.029.zip to the same folder to get the boot.img | system.img | vendor.img and recovery.img file. (there was no userdata.img nor cache.img within the zip, so I downloaded 7.1.1 version and extracted those files too)
3) Using SDK tools ADB /Fastboot version 1.0.38, I flashed the following:-
fastboot flash bootloader C:\bullhead\images\bootloader-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash radio C:\bullhead\images\radio-bullhead-bullhead-xx.xx.img
fastboot reboot-bootloader
fastboot flash boot C:\bullhead\images\boot.img
fastboot erase cache
fastboot flash cache C:\bullhead\images\cache.img
fastboot flash recovery C:\bullhead\images\recovery.img
fastboot flash system C:\bullhead\images\system.img
fastboot flash vendor C:\bullhead\images\vendor.img
fastboot flash userdata C:\bullhead\images\userdata.img
fastboot oem lock
Everything flashed without a problem, no error. However the phone still does not boot into the OS nor can I get it to boot into recovery mode.
I cannot understand what I am doing wrong. I think it has something to do with the installation of copperhead I tried. Does anyone know whether copperhead os restricts going back to stock rom due to its additional security features?
I'm stuck!!!
Thanks in advance.
Click to expand...
Click to collapse
Why don't you use the "flash-all.bat" file? I'm pretty sure you're not wiping your system partition in the process you use.
i.adrian said:
Why don't you use the "flash-all.bat" file? I'm pretty sure you're not wiping your system partition in the process you use.
Click to expand...
Click to collapse
Hiya,
I have also tried using the .bat script, it leads to the same place. A phone that does not boot.
thanks in advance.
Can you boot into twrp, fastboot boot twrp.img? If you can try formatting, not wiping, the data partition. It also gives you the option to repairing some other partitions, I don't remember which ones. You could try that.
Sent from my [device_name] using XDA-Developers Legacy app
I extracted the system sparsechunk img's and vendor.img
"dump" zips can be found here.
hi how did you dump systems in sparsechunks? did you use dd?