I'm a LG 2X user, a few days ago, I found LGExtract by @navossoc.
http://forum.xda-developers.com/showthread.php?t=1566532
It's really an excellent tool. In the past I copied img files from C:\ProgramData\LGMOBILEAX\Phone, replaced recovery.img with CWM recovery when flashing KDZ. now I can extract img from KDZ without flashing KDZ, it's mush easier to flash system.img and boot.img with CWM recovery. (thanks navossoc!)
I still have a question, is it possible to build a custom KDZ now?
Hi guys,
I can't find a clear explanation of this. So I would like your help. For the time being, I'm primarily interested in rooting and not so much in a custom ROM. I'll just tell you what I do and we could take it from there. Assume an unlocked boot loader.
1. I flash the HTC recovery partition with CWM or TRWP
2. I root the phone.
3. I enjoy apps that require root.
When a HTC OTA update arrives:
1. I extract recovery.img from the OTA zip (and I use OTA-root keeper too to regain root after the OTA-update has been applied)
2. I flash HTC's recovery.img to the recovery partition (just stating the obvious)so that the phone again has the stock recovery
3. I update the phone
4. I reflash TRWP or CWM to the recovery partition
5. I use OTA-rootkeeper to regain root.
Now with Sony, I've read there is no separate recovery partition. So the bootloader does NOT load the recovery directly when asked to. Instead it loads the regular kernel which in turn loads the recovery. So it appears the kernel needs to be modified and the recovery image needs to be stored somewhere. I've picked up some terms like ELF and Ramdisk but I'm not getting the bigger picture here.
Could you please tell me what the implication are? With HTC, I can easly apply the OTA-updates using my above method and not loose any apps or data. With Sony, it appears I need to do much more?
http://forum.xda-developers.com/showthread.php?t=2439328
Basically
Download flashtool from flashtool.net
Use it to flash a .534 FW (Download any one of them from the megacollection thread in the general section)
Google Bin4ry root many android to root the phone
Let the phone update OTA
Install Dual recovery from here then update it using the package in post #321 of that thread
Dear D958 users,
I badly need stock boot.img for 4.2.2
or a method of how i can extract kdz file to get boot.img from the Stock Rom.
i get irritating CDC serial driver failure in Windows 7 due to wich i guess the Stock Rom is refuse to flash. it simply fails in download mode.
only option i have is unroot the device, download OTA and flash OTA but before all this got to push stock boot.img as while flashing OTA it restarts on custom recovery screen.
if any body else have a better suggestion, I'm all ears.
To start: 5.1.1 (LMY48M), rooted, with TWRP for recovery
For every 5.x update so far, this has been my procedure using fastboot:
Flash boot.img
Flash radio.img
Flash system.img
After successfully updated, I'd use WugFresh's Nexus toolkit to root and flash TWRP.
I'm a fan of not needing to flash userdata.img, as I don't think that should be necessary given that the OTA wouldn't wipe installed apps and such.
I've read other threads about using fastboot to upgrade and am concerned about the boot warnings, which seem to require a custom kernel to circumvent. My question is: will the above approach still work? Do I need to flash any other files? If I need to flash a custom kernel, where do I get it, how do I flash it (is it just a custom boot.img?), and at which point in the flash sequence should I apply it?
Secondly, has anyone tried gaining root through the Nexus toolkit once upgraded to 6.0?
I'm looking for recommendations so I don't spend hours trying to unbrick my device. Thanks!
You'll also want to flash the 6.0 bootloader and why are you using the toolkit to flash twrp when you can flash it in fastboot along with the rest of the files?
Ah OK, I'll flash the bootloader image as well. Anything else to be concerned with? The toolkit has a feature to root + flash twrp as a feature, so I just use that.
Do the bootloader first, then reboot the bootloader before you flash anything else. There are instructions floating around here some where or you can google nexus 6 flash factory images. You don't have to flash user data as this will format all you data/ apps.
Just download the latest SuperSu zip (2.50) and put it on your SDcard. If you flash as you suggested and then boot directly into recovery, you will still have TWRP. If you don't flash the stock recovery.img to replace TWRP, it will replace on first boot anyway, unless you root imeediately, but you are probably booting to use the toolkit, which replaces recovery only to have to use the toolkit to flash recovery anwyay.
So do your flashes, boot straight into recovery, flash the supersu zip on your sdcard. Done.
i have flashed via odin about a hundred times by now. today i downloaded the new android 10 update because before i was flashing 9 still.
but updating doesn't help, let me tell you what my problem is. whenever i patch the AP file in magisk manager then flash via odin to my then stocked phone i get rooted but am not able to flash anything to recovery. for example:
FLASHING TWRP from the phone never works and hasn't worked a single time.
u can flash the default twrp from the official app which results in a boot loop.
u can flash the magisk_patched.img (after having put official twrp.img through magisk manager)
by entering this into a SU terminal: # f=/storage/emulated/0/Download/magisk_patched.img; dd if=$f of=/dev/block/sda15 bs=$(stat -c%s $f)
but that also results in a boot loop.
flashing default twrp tar via odin does work however it isn't patched via magisk because that AGAIN doesn't work, not even with odin (for those asking "how do you flash .img through odin" i heard success stories from others that executing tar command in linux just archives the .img and if it's named recovery.img inside the tar archive odin has no problem flashing... this is what i did)
anyway i wanted twrp so i could flash my favorite custom rom onto the device, but i'l have to do with rooted stock rom for now