Does anyone know where the ASUS FOTA zip files get downloaded to? I need to know because the buggy TWRP always hangs when booted via FOTA, so I want to try to install the zip manually.
Related
Hi! I'm trying to help a friend of mine who's phone is stuck on a bootloop. Problem was she flashed Pimp My Rom stuffs but she did not download the uninstall flashable zip as well. She does not even have any clockworkmod recovery. The phone's manufacturer is totally not mainstream and does not have any update.zip available. What I'm trying to do for her is to create a flashable update.zip that's flashable via stock recovery. We have a system.img and I'm aware that we can create an updater-script. The problem is, I don't know where the system partition is. Any way we can do cat proc/partitions or mount via recovery to find out where it is? TIA!
UPDATE:
I found it! It turns out to be at dev/block/mmcblk0p12. The problem that I'm having now is I'm getting errors whenever I attempt to sign it. I tried different tools--sign em, auto signer, Sign+...all to no avail. Any ideas?
Hi guys!
I was hoping one of you could help me.
Yesterday i modified a build.prop file on my NextBook EBM8000ND (Next800T) tablet, causing it to get stuck in a bootloop every time it's turned on. I've been searching the Internet all day long but it's hard to find support when you have a device which no one in the world uses . It was rooted but I did a factory reset hoping that it would fix it. It didn't and now it's also unrooted. I tried to make a custom update.zip with the backup of the original build.prop file but the stock recovery simply refuses to load any update file. It always stops at verification. I used 7zip with store option. I tried signing the zip, I even edited the updater script to only print some text on the screen but the recovery still wouldn't load it. I tried to find a way to install CWM using sdcard but with no luck. When i tried to use ADB in recovery the device says: "failed to open driver control: No such file or directory". It might be worth mentioning that I found my device's ROM online with boot.img and recovery.img files and a .tar file which contains the original system folder.
Is there any way to make the stock recovery (since installing CWM or TWRP seems impossible) read my update file? Or is there another way to fix this? I only need to replace that single file.
Hoping to get help soon.
Cheers!
Hey me again.
So I just got an OTA update notification, but since I'm on a custom recovery, I can't install it. Don't suppose anyone would go to the trouble to re-package it as a flashable zip file for TWRP/clockworkmod?
Thanks.
flash recovery on OTA pack
There isn't any recovery and the firmware.zip can't be extracted
I'll have access to a full stock Asia phone that's had the update applied tomorrow. As long as the recovery.log is still in cache I should be able to work out which files where updated and create a TWRP update zip file from it.(If its just stagefright libs being replaced it should be compatible across regional roms)
I can provide the ota from Poland play version
porozex said:
I can provide the ota from Poland play version
Click to expand...
Click to collapse
Have you installed the update? Last time i tried i couldn't do anyrhing with a ota_update zip. But with a twrp /system backup and hopefully a recovery.log file from an updated rom, i think I can work out which files were updated and create twrp compatible update.zip based on that. The asia ota_update was only 87Mb in size and trying to address the stagefright bug from what I've seen. Is that the same for you?
No, I can't install it. Mine was around 38mb
edit: ok i found a solution, if you have a backup of your rom (i got it after got installed twp for first time) open it with winzip or 7zip then navigate to sytem>bin>bebuggerd and copy it to the phone. then with a filemanager with root privileges replace the current one and give proper permissions. thats it
1. My Redmi 5 Plus/Redmi Note 5 India is rooted, using TWRP and Magisk
2. I would like to know if there is a way that recent updates under downloaded_ROM can be flashed using a third party application such as Flashify?
3. I have come to this decision because when I tried to reboot device for installing recently updates, my device enters the TWRP recovery only find nothing in there, which is annoying. Root cause for this mess is that Xiaomi's fastboot rom downloads page is download, which would usually be my go to method after all. Using Mi Flash Tool, and then a few command types re-root the recently updated mobile phone.
Please guide me!
If I understood well if twrp it´s not recognicing (not really, only it can´t access) your data partition you need to format data at first time after to unlock and install a custom recovery in order that twrp can access to your storage directory.
Flashify just is capable to install boot and recovery images. Maybe you meant FlashFire, then to install it tap on + button and a menu will display with some options like Flash ZIP or OTA.
SubwayChamp said:
If I understood well if twrp it´s not recognicing (not really, only it can´t access) your data partition you need to format data at first time after to unlock and install a custom recovery in order that twrp can access to your storage directory.
Flashify just is capable to install boot and recovery images. Maybe you meant FlashFire, then to install it tap on + button and a menu will display with some options like Flash ZIP or OTA.
Click to expand...
Click to collapse
you're right, brother. I meant FlashFire, when I typed Flashfire. My bad.
I have the OTA downloaded from the official website, since the file I had in the downloaded ROM folder always returned an error as corrupt file when tried to open using Winrar. So I had to go the official site and get the same downloaded to see the contents inside.
But now, having copied the file to the downloaded ROM folder on my phone, I do not see any option as how I can choose the file to get installed. I mean there is no file explorer option given to me, rather Google Drive option. Perhaps I have to have the file uploaded once again on to my Google Drive on my device?
sengottuvel said:
you're right, brother. I meant FlashFire, when I typed Flashfire. My bad.
I have the OTA downloaded from the official website, since the file I had in the downloaded ROM folder always returned an error as corrupt file when tried to open using Winrar. So I had to go the official site and get the same downloaded to see the contents inside.
But now, having copied the file to the downloaded ROM folder on my phone, I do not see any option as how I can choose the file to get installed. I mean there is no file explorer option given to me, rather Google Drive option. Perhaps I have to have the file uploaded once again on to my Google Drive on my device?
Click to expand...
Click to collapse
Download again the file from the same site, maybe downloaded to your Google Drive is corrupted and check that the extension didn´t change from .zip to .rar or FlashFire won´t recognice it. Winrar have to be capable to open it otherway the file is corrupted.
When you are sure that is the correct file If you had a stock recovery then you can install it through update option in settings/about device/updates from miui menu
anyone have any idea how to install incremental updates manually? i have an ota incremental package, have even dumped the contents and have the .img files inside but not sure what to do with them as they are not full partition images just the increments(i guess just the parts that need to be changed of the actual partitions) is there any way to merge them or how else should they be used? i tried to use payload dumper with --diff but that just keeps giving me an error that boot image type isnt supported so i can get all the other files and no boot image with it. if anyone has any ideas i would greatly appreciate it. i downloaded the oneplus software updater to try the local upgrade/update and it just keeps telling to put it in the root directory and i have put the zip and the extracted contents in every directory i can think of to no avail. oxygen updater also doesnt support this device (yet)
nvm i found the answer thanks to someone on tg..
encrypt the incremental with ofpflasher and update