I have the RUU installer for the AT&T One X, but the automated flashing isn't working too well for me. Is there a way I can unpack it and access the boot.img, recovery.img, and system.img so I can flash them myself?
Related
i just get flash a leedroid boot.img before trafer the rom zip file to the phone.
so phone won't boot up or let me trafer the zip file to the phone either.
if you have a problem like me just to http://d-h.st/69P(thanks to torxx)
so just use fastboot and flash this boot.ing in this file and you can recover you brick T-mobile one s (this boot.ing is for t-mobile one s only)
Hey guys,
so right now I am trying to flash a new rom (currently on trickdroid) and was considering axiom but one of the steps is to flash the boot.img but i am having trouble figuring out how to flash the boot.img through fastboot. I have installed the sdk manager and htc sync according to the how to in the development thread. But i don't know where to get the file for the boot.img and what to do after that I have watched the video and read through the how to several times. Is there an easier way to go about flashing roms, or do I have to use the boot.img process?
If you flash via TWRP, you won't have to flash boot.img.
boot.img is found in the .zip package that you flash. It should be one of the first items you see when you open the zip. This is the .zip that you install when you're in CWM. Extract that boot.img for the fastboot method, but like I said, with TWRP you won't have to flash it.
Some people have said that their boot.img's didn't flash on TWRP, but worse comes to worst is you get stuck in a boot loop and you just flash the boot.img in fastboot or restore your phone in CWM.
ShensMobile said:
If you flash via TWRP, you won't have to flash boot.img.
boot.img is found in the .zip package that you flash. It should be one of the first items you see when you open the zip. This is the .zip that you install when you're in CWM. Extract that boot.img for the fastboot method, but like I said, with TWRP you won't have to flash it.
Some people have said that their boot.img's didn't flash on TWRP, but worse comes to worst is you get stuck in a boot loop and you just flash the boot.img in fastboot or restore your phone in CWM.
Click to expand...
Click to collapse
Okay perfect this is exactly what I was looking for, thank you!
Well I need to send in the Chacha because of some Hardware issues, so I'd like to restore the original ROM.
What's the easiest way getting it back (maybe with the option not having to root it again afterwards, or restoring the Clockwork-Backup)?
The best way is to download RUU, extract from it rom.zip and from that zip extract system.img, boot.img and recovery.img. Then flash those three via fastboot using these commands:
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
And reboot your phone and you will have stock rom with stock recovery on it. Then you can use OTA update if available.
At the root file system on my Android phone, there's a file called default.prop. Right now that's a non-standard file because of CF-Auto-Root, but I want that file to be the stock version (1).
After what I have understood, /default.prop file is overwritten on every boot from a default.prop file within the boot partition.
My phone is rooted with CF-Auto-Root, but I've replaced the boot and bootloader partitions with factory image versions:
$ fastboot flash bootloader bootloader.img
$ fastboot flash boot boot.img
But still I get the non-stock default.prop file. What am I doing wrong?
(1) This is because I'm trying to upgrade to Android 5.1, and right now I'm getting an error because "this device has google/omni_hammerhead/hammerhead:4.4.4/KTU84P/eng.dees_troy.20150214.172938:eng/test-keys".
neu242 said:
(1) This is because I'm trying to upgrade to Android 5.1, and right now I'm getting an error because "this device has google/omni_hammerhead/hammerhead:4.4.4/KTU84P/eng.dees_troy.20150214.172938:eng/test-keys".
Click to expand...
Click to collapse
Don't bother messing with reverting everything just to update, it is extremely unlikely to work since as of Lollipop Google has changed the OTA method to check the sum of the entire partition rather than only what it cares about.
Download the 5.1 factory images, and flash system.img, boot.img, cache.img, radio.img and bootloader.img (don't flash userdata.img unless you want to wipe all your data), then boot into a custom recovery and flash the latest SuperSU (http://download.chainfire.eu/supersu).
Elluel said:
Download the 5.1 factory images, and flash system.img, boot.img, cache.img, radio.img and bootloader.img (don't flash userdata.img unless you want to wipe all your data), then boot into a custom recovery and flash the latest SuperSU (http://download.chainfire.eu/supersu).
Click to expand...
Click to collapse
Perfect, just what the doctor ordered. Thanks Elluel!
I can't seem to get TWRP or Cyanogen Recovery to flash succesfully CM12.1. They refuse to flash ROM zips, but do flash Gapps. I've tried ADB sideload to flash CM12.1, but ADB doesn't find my E3 no matter what I do. I go to recovery, and choose ADB sideload. Then I do adb devices and it just says "List of devices attached", but no devices. I can only use fastboot succesfully, which that made me think that I could decompress the zip and make the boot.img, system.img, and userdata.img out of it to flash through fastboot. I got all the required filesfrom the zip to make userdata.img and system.img (boot.img was already in there). I only have one problem: I haven't found a way to re-pack the files into the correct img format to be able to flash it through fastboot.
So, back to my question:
Has anyone managed to flash the CM12.1 zip successfully? If so, how?
Or, can someone show me how to repack the system files into system.img and the userdata files into userdata.img?