A little background first. Flashed stock recovery and my original first backup in order to take OTA for Marshmallow. OTA wouldn't take so I downloaded / installed MM update successfully. Currently at 6.0, 3.38.502.12. Then, re-unlocked bootloader (S-ON) and flashed TWRP 3.0.2.0. I then immediately created a full backup successfully before rooting.
Since that point, I've been unable to create another backup. I've also had countless problems trying to flash anything at all like custom ROMs and such. Keep having to revert to my unrooted backup post-MM update. The problem had to occur somewhere after my first successful TWRP backup post-MM update and now. Puzzling part is that I restored this same successful backup then without leaving TWRP, I immediately tried to do another backup and it fails the exact same way.
Recovery.log shows:
* MD5 Created.
Backing up System...
Error opening: '/system/app/Ds' (Not a directory)
I:Error in Generate_TarList!
Error creating backup.
createTarFork() process ended with ERROR: 255
Backup Failed. Cleaning Backup Folder.
I've tracked this down and it does indeed appear to be a directory "Ds". Inside as a sub-directory called 'oat' with Ds.apk inside of that, which is the Dolby Audio service.
I'm completly stumped. Any ideas?
Update, in the /system/app/ (list of apps) it looks like there is an oat subdirectory followed by arm64 then filename.odex:
/system/app/BasicDreams/oat/arm64/BasicDreams.odex
However, when I browse to the problem app "Ds"... oat does not appear as a directory.
This could be a simple fix then?? Coudn't I just obtain root again, somehow change that oat to a directory and hope I see the rest of the subdirectories and files there?
OR... could I find Ds.odex somewhere and re-create the file structure?
Better yet! Would someone out there be able to give me or post a link for Ds.odex? Would it be as easy as me making a sub-directory called oat/arm64 and placing this Ds.odex file in there??
Any help would be much appreciated.
sirvalence said:
Update, in the /system/app/ (list of apps) it looks like there is an oat subdirectory followed by arm64 then filename.odex:
/system/app/BasicDreams/oat/arm64/BasicDreams.odex
However, when I browse to the problem app "Ds"... oat does not appear as a directory.
This could be a simple fix then?? Coudn't I just obtain root again, somehow change that oat to a directory and hope I see the rest of the subdirectories and files there?
OR... could I find Ds.odex somewhere and re-create the file structure?
Better yet! Would someone out there be able to give me or post a link for Ds.odex? Would it be as easy as me making a sub-directory called oat/arm64 and placing this Ds.odex file in there??
Any help would be much appreciated.
Click to expand...
Click to collapse
I don't have any oat directories under /system/app/(app name)/oat/ARM64/...
Only thing that is in the app directory (for me) is the .apk, and at times, a lib subdirectory (webviewgoogle is like that, which has an arm and arm64 directory under that).
I'm running VenomRom which may handle this differently.. it's prerooted and whatnot.
I also disabled boomsound which I think also disabled the Dolby sound system app from running. Viper is better [emoji2]
Id back up your internal storage again, ruu, flash twrp 3.0.0-2, boot into recovery, let it make system writable, reboot into recovery again, and see what happens.
Or flash a pre-rooted sense rom instead of stock.
I honestly couldn't get this stupid AT&T varient working correctly until I s-off'd, updated Sid to developer, then run dev ruu. Works great now.
Sent from my HTC One M9 using XDA-Developers mobile app
grandpajiver said:
I don't have any oat directories under /system/app/(app name)/oat/ARM64/...
Only thing that is in the app directory (for me) is the .apk, and at times, a lib subdirectory (webviewgoogle is like that, which has an arm and arm64 directory under that).
I'm running VenomRom which may handle this differently.. it's prerooted and whatnot.
I also disabled boomsound which I think also disabled the Dolby sound system app from running. Viper is better [emoji2]
Id back up your internal storage again, ruu, flash twrp 3.0.0-2, boot into recovery, let it make system writable, reboot into recovery again, and see what happens.
Or flash a pre-rooted sense rom instead of stock.
I honestly couldn't get this stupid AT&T varient working correctly until I s-off'd, updated Sid to developer, then run dev ruu. Works great now.
Sent from my HTC One M9 using XDA-Developers mobile app
Click to expand...
Click to collapse
Thanks, yeah I'm having nothing but trouble since moving to MM. Each time, I can RUU back to stock ATT US and everything is fine. Not sure if it happens during my first TWRP pre-root backup, or the restore process. I looked at the recovery.log of said backup and nothing looked different regarding the /system/apps. I've since tried a few times and it just seems to throw a few /system/apps into another directory altogether, no rhyme or reason. Last try, there wasn't even a Ds directory as it disappeared. A Ds 0 byte file then appeared at /system level. This happened with 10 or so other random system apps. WEIRD! Maybe I should just S-OFF. I've never done that or changed my MID or SID for that matter. I'm still fairly new to this.
sirvalence said:
Thanks, yeah I'm having nothing but trouble since moving to MM. Each time, I can RUU back to stock ATT US and everything is fine. Not sure if it happens during my first TWRP pre-root backup, or the restore process. I looked at the recovery.log of said backup and nothing looked different regarding the /system/apps. I've since tried a few times and it just seems to throw a few /system/apps into another directory altogether, no rhyme or reason. Last try, there wasn't even a Ds directory as it disappeared. A Ds 0 byte file then appeared at /system level. This happened with 10 or so other random system apps. WEIRD! Maybe I should just S-OFF. I've never done that or changed my MID or SID for that matter. I'm still fairly new to this.
Click to expand...
Click to collapse
So worth the 25 dollars. But you need your system up and rooted for that to work.
But yeah, the dev edition SID 01 worked for me.
Made it way easier to work with and taking that ruu was magic.
Oh, also, do you have an sdcard? There is always the rom.zip method... placing the appropriate 0PJAIMG.ZIP in the root of the sdcard then rebooting into download mode works nicely.
Sent from my HTC One M9 using XDA-Developers mobile app
Related
So, I've used Revolutionary to S-off and root, but now there's a system update (I assume for the security vulnerability that was found a week or two ago). I'd like to install this update, but it just fails when I try... Does anyone know how to turn it into a flashable zip, or will I have to un-s-off/root, update, then re-s-off/root?
A hotfix for the vulnerability is not out yet - you tought HTC is that fast But if you can find it you can remove /system/app/HtcLoggers.apk from your rooted Flyer (with an app like File Expert that can mount partitions like /system).
Since you are still stock you might have been offered an incremental update, but I guess soon you will want to flash a custom ROM that already includes it anyway.
Lucas0511 said:
A hotfix for the vulnerability is not out yet - you tought HTC is that fast But if you can find it you can remove /system/app/HtcLoggers.apk from your rooted Flyer (with an app like File Expert that can mount partitions like /system).
Since you are still stock you might have been offered an incremental update, but I guess soon you will want to flash a custom ROM that already includes it anyway.
Click to expand...
Click to collapse
It appears there's a new update today, and it's only about 4.5 megs - I think HTC may actually be that fast
I really don't want to install a ROM, I just want stock with root (to help with development)... Any suggestions appreciated!
To answer my own question, I downloaded the OTA on the device, then I used adb to copy it to my computer (it's in /sdcard/downloads/). I edited the zip so that it wouldn't flash the recovery (there's a recovery.img in firmware.zip inside the OTA zip - remove it), copied it to the external SD card, then flashed it via ClockworkMod (it won't update via the HTC updater).
Something to make sure of, you MUST be running stock - it patches files rather than reinstalls them, so this will fail if there are any differences. This includes build.prop. You can make any changes you like after flashing of course.
Don't forget to backup before doing anything of course! Another warning, ClockworkMod fails silently if your SD card doesn't have enough room for the backup, so make sure you have plenty of space beforehand too!
Hope this helps someone.
Cwiiis said:
To answer my own question, I downloaded the OTA on the device, then I used adb to copy it to my computer (it's in /sdcard/downloads/). I edited the zip so that it wouldn't flash the recovery (there's a recovery.img in firmware.zip inside the OTA zip - remove it), copied it to the external SD card, then flashed it via ClockworkMod (it won't update via the HTC updater).
Something to make sure of, you MUST be running stock - it patches files rather than reinstalls them, so this will fail if there are any differences. This includes build.prop. You can make any changes you like after flashing of course.
Don't forget to backup before doing anything of course! Another warning, ClockworkMod fails silently if your SD card doesn't have enough room for the backup, so make sure you have plenty of space beforehand too!
Hope this helps someone.
Click to expand...
Click to collapse
Removing the recovery.img? I've rezipped everything and it's only 510kb now, surely that cant be it?
Recovery.img's are large files it was just a minor updat to probably fix a couple internal things nothing major. It was a small file at 4mb already.
Hy
Can you please upload the edit-update?
Thanks
ric242 said:
Hy
Can you please upload the edit-update?
Thanks
Click to expand...
Click to collapse
Will do once i'm home!
adaimespechip said:
Will do once i'm home!
Click to expand...
Click to collapse
Thanks! Might be able to make it into a flash able zip.
Cwiiis said:
To answer my own question, I downloaded the OTA on the device, then I used adb to copy it to my computer (it's in /sdcard/downloads/). I edited the zip so that it wouldn't flash the recovery (there's a recovery.img in firmware.zip inside the OTA zip - remove it), copied it to the external SD card, then flashed it via ClockworkMod (it won't update via the HTC updater).
Something to make sure of, you MUST be running stock - it patches files rather than reinstalls them, so this will fail if there are any differences. This includes build.prop. You can make any changes you like after flashing of course.
Don't forget to backup before doing anything of course! Another warning, ClockworkMod fails silently if your SD card doesn't have enough room for the backup, so make sure you have plenty of space beforehand too!
Hope this helps someone.
Click to expand...
Click to collapse
Thanks for the helpful guidelines...
Just a quick question and pardon me since I am a newcomer to Android universe. What do You mean when You say stock?
Thanks again...
BTY
HTC_Flyer / Revolutionary / CWM
I need the community's help. I have never posted on XDA cause I have always been able to find the answers I was looking for by searching these forums. This time I am stumped. I am not a noob, but I'm also not a dev or programmer. I have managed, thanks to XDA, to unlock, root and flash a dozen different android devices I've owned without bricking any of them (I admit I'm a flash-a-holic and refuse to get treatment ).
I have a TFP (201) that refuses to download anything from anywhere except the Google Play Store. Cannot download via browser, Amazon app store, Goo Manager, Rom Manager or any other means. In each case it almost immediately tells me that the download was unsuccessful or download errored. I have done dozens of searches and have tried an equal number of so-called fixes with no luck. I have tried every custom rom on the forum, have switched between CWM and TWRP. I have flashed previous backups from TWRP. All to no avail.
Two other issues that may be related; 1- when i run the fix permissions script from inside Rom Manager or from Recovery screen, I get a "an error occurred while attempting to run priviliged commands!" 2- in CWM, when I try to flash older nandroid backups, it tells me that the files are not valid because it can't find the checksum (MD5) corresponding file.
I am currently running aokpcb_tf201_r2.1 with the kernel it comes with, everything else works except no downloading.
Any help would be greatly appreciated.
Can you check to see if your internal SdCard folder has the correct permissions using root explorer? I forget the details of exactly where it is, as I dont have my prime with me, however it is a folder within /data partition... something like /data/media/sdcard or something of that nature.
GooglePlay I believe uses the /cache partition for its downloads, thus I believe these are not throwing errors, whilst everything else is done into the internal sdcard folder.
Same oribkem
kokopuphz said:
Can you check to see if your internal SdCard folder has the correct permissions using root explorer? I forget the details of exactly where it is, as I dont have my prime with me, however it is a folder within /data partition... something like /data/media/sdcard or something of that nature.
GooglePlay I believe uses the /cache partition for its downloads, thus I believe these are not throwing errors, whilst everything else is done into the internal sdcard folder.
Click to expand...
Click to collapse
having the same problem , and you solution didn't work man .
kokopuphz said:
Can you check to see if your internal SdCard folder has the correct permissions using root explorer? I forget the details of exactly where it is, as I dont have my prime with me, however it is a folder within /data partition... something like /data/media/sdcard or something of that nature.
GooglePlay I believe uses the /cache partition for its downloads, thus I believe these are not throwing errors, whilst everything else is done into the internal sdcard folder.
Click to expand...
Click to collapse
This seemed to work. If you go to data/media/download and change the permissions this should fix the problem. I was unable to download anything using any browser or an email attachment.
Sent from my Transformer Prime TF201 using xda app-developers app
Hi folks,
The adventures continue. I've been trying to restore my Safestrap backup for ages, and no matter what I try, I continue to get
Code:
Error restoring /data!
at the conclusion of the restoration. I can restore via Fastboot to stock, but no matter what I can't get my full backup restored successfully. Generally unless I restore to stock factory the system ends up in a kind of broken state where there are apps that are installed but have file size 0B, and don't run.
The final error in the recovery log is
Code:
tar: seek failure: Value too large for defined data type
Error while restoring /data!
Of course the first thing I thought was that the backup was corrupt, but it extracts completely fine with plain ole' tar on my Linux laptop.
I have:
Updated Safestrap to 2.11 for Droid Razr
Updated BusyBox via Stericson's BusyBox updater app from Google Play
Attempted restore again after those two steps
Wiped /data and restored to Factory via both Fastboot flash through Matt's Utility and Motorola Recovery menu
Attempted to split the data.ext3.tar file into two, one with my apps directory, one without (since that way, both files are below 2 GB). The first file, the one with the apps directory removed, restored fine. The second one, consisting of just the apps directory, did not (with the same error). It might be a moot point anyway since I think Safestrap formats the partitions before restoring, so it wouldn't "recombine" them anyway.
Bought the XDADevelopers Android Hackers' Toolkit from the bookstore. Haven't finished reading it yet, but hopefully it will give me some ideas.
So I can get access to what my apps directory should look like (I can extract it locally here on my laptop) but I can't get Safestrap to extract it all at once to the correct partition on my phone.
I'm currently almost out of ideas. It seems this is a common problem and that newer versions of CWM Recovery split the tars so to avoid the file size limit imposed by BusyBox, if I'm interpreting what I've read correctly. This might be the case with the newer Safestrap but it doesn't help my old backup, unless I can split it in a way that Safestrap expects and will deal with (is this possible?)
Given that I have the actual files that should be on the phone, and that my phone is rooted, would it make sense to simply attempt to extract the apps-only tar overtop of the apps directory? Would the files be locked when the phone was on normally?
Could this still be a free space issue? Currently I'm showing 1.7 GB free after the latest failed restore. One would think if it was a disk space issue, it would show 0 B free, right? To test this, would it hurt to delete the files in the safestrap directory (i.e. orig and safe, containing a data.ext3.tar in each of about 2.2 GB) since Safestrap is currently in unsafe mode right now anyway?
Also, is there anything I can do to help here? I know C and C++; while I'm not a low-level hardware hacker by any means (I'm a professional web developer) this issue has bugged me enough that I want to try to fix it. I know that Safestrap is on Github but I'm not really sure where to start.
Do you have any other suggestions for ways to get my Safestrap-generated nandroid backup of my data correctly restored to my phone?
Please let me know if I did something wrong in asking this question; I tried to do as much research as I could beforehand. If I haven't done enough, I would appreciate a point in the right direction.
Or maybe the post was too long and drawn out, so I'll try to compact it here.
My phone won't restore a successful Safestrap backup that is 2.2 GB in size. The backup (a tar file) extracts fine on my PC. I'm getting "error restoring /data!". It seems to be the same issue others have had with restoring a CWM backup over 2 GB.
Would it make sense to simply attempt to extract the apps-only tar overtop of the apps directory, or would the files be locked when the phone was on normally?
Could this still be a free space issue?
Do you have any other suggestions for ways to get my Safestrap-generated nandroid backup of my data correctly restored to my phone?
Edit: Could the tar be converted to an image file to be flashed to the data partition with Fastboot?
Final bump. Anyone? Anyone? Bueler?
Is it safe to just grab a root shell through ADB, push the tar containing the apps, and extract over top of my phone's existing apps directory, while the phone is running? Are there risks associated with this?
Edit: Alternatively, is there a native Android GNU tar binary available anywhere, or instructions for cross-compiling one, since this seems to be a problem with BusyBox?
...Answering my own question, apparently yes. I'm going to try replacing the tar symlink to BusyBox with this native version and try again tonight, I'll let you know how it goes.
I had the same problem and the tar from your link worked for me for a 4GB tar extract. Thanks for your tip!
I try update via recovery ( put this file to external strorage only )
1. boot to recovery mode hold Power + Volume Down button
2. Using the Volume buttons to scroll and the Power button to select, choose "Enter
recovery mode
3. Choose apply update from external storage
4. select "reboot system now after finished update
http://fota.asus.com/delta_package/.../WW_PF500KL-12.2.2.43-13.6.5.30-fota-user.zip
This screenshoot from my phone +Station
Error Status 7
I have error:
System partition has unexpected contents
E:Error in /sdcard/UL-ASUS_TOON-WW-13.6.5.30-user.zip
(Status 7)
anyone can help me?!
Same issue as well
Getting the same "System partition has unexpected contents (Status 7 )" any idea whats wrong?
It's most likely because of root, and any changes like installing busybox, or having edited the build.prop . I had to wipe system on my padfone x reinstall lollipop 43 then install the marshmallow ota, then root 2.68 then dd the Xmodem.img I found for USA radio bands and the twrp 3.0.0.0 img to get everything working.
Also I'm not sure if flashing without wiping data partition works the same as well as starting from scratch, but I did do it all in one shot and first without data being wiped and worked fine. But I then wiped everything to see how much space I could recover in app storage. I saved myself about a gigabyte and a half to have a total of 4gb remaining after apps were installed (i have a lot of apps)
Gizoid1337 said:
It's most likely because of root, and any changes like installing busybox, or having edited the build.prop . I had to wipe system on my padfone x reinstall lollipop 43 then install the marshmallow ota, then root 2.68 then dd the Xmodem.img I found for USA radio bands and the twrp 3.0.0.0 img to get everything working.
Also I'm not sure if flashing without wiping data partition works the same as well as starting from scratch, but I did do it all in one shot and first without data being wiped and worked fine. But I then wiped everything to see how much space I could recover in app storage. I saved myself about a gigabyte and a half to have a total of 4gb remaining after apps were installed (i have a lot of apps)
Click to expand...
Click to collapse
Thanks ! It worked for me
I reinstalled ver 12.2.2.43 which really is my current version, and then proceed to install MM 13.6.5.30 with success
Gizoid1337 said:
It's most likely because of root, and any changes like installing busybox, or having edited the build.prop . I had to wipe system on my padfone x reinstall lollipop 43 then install the marshmallow ota, then root 2.68 then dd the Xmodem.img I found for USA radio bands and the twrp 3.0.0.0 img to get everything working.
Also I'm not sure if flashing without wiping data partition works the same as well as starting from scratch, but I did do it all in one shot and first without data being wiped and worked fine. But I then wiped everything to see how much space I could recover in app storage. I saved myself about a gigabyte and a half to have a total of 4gb remaining after apps were installed (i have a lot of apps)
Click to expand...
Click to collapse
Thanks to you I have updated my phone to marshmallow using twrp 3.0.0, which allowed me to re-unlock bootloader, and root my phone.
It can be done, you just need to remove a few lines in the updater-script file.
something with ro.fingerprint (that identifies the recovery, it was originally expecting stock).
Replace it inside the zip. Then transfer update to sd card or internal.
After that wipe system, then reflash .43, right after that flash the mm update.
Will take some time but it should work once everything is verified.
reflash bl unlock and twrp (just a precaution) , then you can leave.
It would say no os but ignore it.
First boot takes around 10-15 mins then presto you finally have it.
Haven't encountered any bugs yet and it freed up a lot of storage space. Makes me wonder why I had to wait for the update to come to me, so glad I'm done with that.
So that concludes the last major update for the padfone s.....
Can u help me pls? I've tried unroot ,wipe system data and reflash .43 which is my current rom but still got signature verification error. any suggestion to fix this? Thx
Justatechie said:
Thanks to you I have updated my phone to marshmallow using twrp 3.0.0, which allowed me to re-unlock bootloader, and root my phone.
It can be done, you just need to remove a few lines in the updater-script file.
something with ro.fingerprint (that identifies the recovery, it was originally expecting stock).
Replace it inside the zip. Then transfer update to sd card or internal.
.
Click to expand...
Click to collapse
which lines exactly ? cause i tried removing mine and im now getting an error in the zip
error 6 or something
dtgo said:
which lines exactly ? cause i tried removing mine and im now getting an error in the zip
error 6 or something
Click to expand...
Click to collapse
On Notepad++: (not sure about notepad, but you must get rid of ro.build.fingerprint lines and the abort command after)
Delete/Remove lines 7 through 9. If left alone or not deleted fully it will not accept the update because its looking at the recovery image.
It expects 5.0 stock recovery but it sees 6.0 twrp. (since it was built off the source of twrp 3.0.0 which is mainly compatable with 6.0+)
Thats about it.
NightbladeSinX said:
Can u help me pls? I've tried unroot ,wipe system data and reflash .43 which is my current rom but still got signature verification error. any suggestion to fix this? Thx
Click to expand...
Click to collapse
Thats odd.
You should probably Re-download or transfer the ww file again. Could just be a bad transfer of data.
Make sure you have twrp 3.0.0 and that system protection off. (it pops up on the first screen, but you can find it under twrp settings)
Justatechie said:
On Notepad++: (not sure about notepad, but you must get rid of ro.build.fingerprint lines and the abort command after)
Delete/Remove lines 7 through 9. If left alone or not deleted fully it will not accept the update because its looking at the recovery image.
It expects 5.0 stock recovery but it sees 6.0 twrp. (since it was built off the source of twrp 3.0.0 which is mainly compatable with 6.0+)
Thats about it.
Click to expand...
Click to collapse
thanks for the reply , i did that and got Error 6 but it just fails right there , no message or anything
dtgo said:
thanks for the reply , i did that and got Error 6 but it just fails right there , no message or anything
Click to expand...
Click to collapse
If it doesn't say anything about identifying the device model or checking system, then something is wrong.
Might be a bad edit or it might have gotten corrupted while transferring back into the zip.
I stick with N++ for the edits, sometimes windows file transfer can be a pain by itself while trying to replace the update script, 7zip might help.
dtgo said:
thanks for the reply , i did that and got Error 6 but it just fails right there , no message or anything
Click to expand...
Click to collapse
got it working thanks again man you've been a big help
Justatechie said:
On Notepad++: (not sure about notepad, but you must get rid of ro.build.fingerprint lines and the abort command after)
Delete/Remove lines 7 through 9. If left alone or not deleted fully it will not accept the update because its looking at the recovery image.
It expects 5.0 stock recovery but it sees 6.0 twrp. (since it was built off the source of twrp 3.0.0 which is mainly compatable with 6.0+)
Thats about it.
Thats odd.
You should probably Re-download or transfer the ww file again. Could just be a bad transfer of data.
Make sure you have twrp 3.0.0 and that system protection off. (it pops up on the first screen, but you can find it under twrp settings)
Click to expand...
Click to collapse
Thx for reply. i manage to get updated to 6.0.1 but now i lost root. i did mistake not flashing twrp before 1st boot n it replace twrp to stock rec. Is there any root method available yet? I've tried latest kingroot but it was unsuccessful. Any way is there any difference between WW and TW firmware version?
NightbladeSinX said:
Thx for reply. i manage to get updated to 6.0.1 but now i lost root. i did mistake not flashing twrp before 1st boot n it replace twrp to stock rec. Is there any root method available yet? I've tried latest kingroot but it was unsuccessful. Any way is there any difference between WW and TW firmware version?
Click to expand...
Click to collapse
You could probably flash recovery through fastboot, only if your bootloader is unlocked. If not it wont allow the flash. it would say FAILED cant flash unsigned image, but theres a chance that it might have been flashed, just check to see if changes have applied.
Assuming that you have went to the fastboot portion of your phone you can check its status.
if its not unlocked, then you have to find another way to root to flash your twrp recovery back on your phone.
Did this, but kept getting errors due to (probably) my use of xposed. Managed to soft brick my phone, and recovered it using http://forum.xda-developers.com/padfone-x/help/guide-restoring-stock-rom-recovery-t3179818
After that, had to edit updater-script to remove all checks.
What tripped me up was just how long the update reboot took. Almost half an hour. I was going to give up but decided to leave it while taking a short nap.
heres the updater script for anyone having issues
Please can someone help me?
I'm trying so hard to get this to work but I'm barely getting anywhere. What I've done (thanks to ninekaw9's guide):
- unlock bootloader
- wiped everything (yet there is still stuff in the file explorer, like the su install folder)
- using fastboot boot recovery:
-- use TWRP 2.8.7.0 to transfer files from sdcard to emmc
-- with TWRP 2.7.1.1:
--- installed WW 99.99.99.0 for KK (works)
--- installed WW 12.2.2.27 for LP & stock recovery (works)
--- installed WW 12.2.2.43 for latest LP (works)
- removed every abort line from updater script to get it to stop complaining about fingerprint/unexpected system contents
- installed modified FOTA WW 13.6.5.30 for MM (no OS change)
So after all that, I'm where I started but with no apps.
Before I found out 2.8.7.0 couldn't flash stock ROMs I flashed 12.2.2.43 after a full wipe and ended up with no System UI...
Outcomes from using different recovery to flash MM update:
2.7.1.1 with unmodified: apparently my phone is TW not WW (incorrect)
2.8.7.0 with unmodified: some weird fingerprint with omni-T00N and 5.1.1, even after wipe and stock 12.2.2.43 flash. Couldn't edit or replace the default.prop file, it would just get overwritten each time
stock with unmodified: couldn't even mount my SD card, so tried ADB sideload, got the unexpected system contents message
stock with modified (no sha1): would no longer allow me to ADB sideload (0.00x message)
TWRP (either) with modified (no prop): unexpected system contents
TWRP (either) with modified (no prop/sha1): seems to work, but upon boot to system, nothing appears to have changed.
I desperately want MM so I have a smaller system partition, then I can stop pushing updates to system to save space, and therefore won't need root so I can play Pokemon GO and use Sky Q.
That or I'm going to try Magisk... Has anyone used this on a Padfone?
If anyone can guide me through which files/folders I can delete from my phone to save space, that would be great. I know most folders are mounting points, but there's a lot of .sh files and other folders that I'm not familiar with.
I've asked in another thread where I can get TWRP 3.x for Padfone S, but nobody has replied!
Please can someone help me?
Nintynuts said:
I'm trying so hard to get this to work but I'm barely getting anywhere. What I've done (thanks to ninekaw9's guide):
- unlock bootloader
- wiped everything (yet there is still stuff in the file explorer, like the su install folder)
- using fastboot boot recovery:
- use TWRP 2.8.7.0 to transfer files from sdcard to emmc
- with TWRP 2.7.1.1:
- installed WW 99.99.99.0 for KK (works)
- installed WW 12.2.2.27 for LP & stock recovery (works)
- installed WW 12.2.2.43 for latest LP (works)
- removed every abort line from updater script to get it to stop complaining about fingerprint/unexpected system contents
- installed modified FOTA WW 13.6.5.30 for MM (no OS change)
So after all that, I'm where I started but with no apps.
Before I found out 2.8.7.0 couldn't flash stock ROMs I flashed 12.2.2.43 after a full wipe and ended up with no SystemUI...
Outcomes from using different recovery to flash MM update:
2.7.1.1 with unmodified: apparently my phone is TW not WW (incorrect)
2.8.7.0 with unmodified: some weird fingerprint with omni-T00N and 5.1.1, even after wipe and stock 12.2.2.43 flash. Couldn't edit or replace the default.prop file, it would just get overwritten each time
stock with unmodified: couldn't even mount my SD card, so tried ADB sideload, got the unexpected system contents messagestock with modified (no sha1): would no longer allow me to ADB sideload (0.00x message)
TWRP (either) with modified (no prop): unexpected system contents
TWRP (either) with modified (no prop/sha1): seems to work, but upon boot to system, nothing appears to have changed.
I desperately want MM so I have a smaller system partition, then I can stop pushing updates to system to save space, and therefore won't need root so I can play Pokemon GO and use Sky Q.
That or I'm going to try hiding root Magisk...
If anyone can guide me through which files/folders I can delete from my phone to save space, that would be great. I know most folders are mounting points, but there's a lot of .sh files and other folders that I'm not familiar with.
I've asked in another thread where I can get TWRP 3.x for Padfone S, but nobody has replied!
Please can someone help me?
Click to expand...
Click to collapse
I used twrp 3.0. Worked like a charm what I ended up doing was reflashing the .43 and then the update after replacing the updater script file here is a link to the thread with the 3.0 twrp http://forum.xda-developers.com/padfone-x/general/padfone-xs-to-stock-lollipop-root-t3263664
xantanion said:
I used twrp 3.0. Worked like a charm what I ended up doing was reflashing the .43 and then the update after replacing the updater script file here is a link to the thread with the 3.0 twrp http://forum.xda-developers.com/padfone-x/general/padfone-xs-to-stock-lollipop-root-t3263664
Click to expand...
Click to collapse
Thanks. No wonder I couldn't find it as it doesn't mention 3.0.0.0 or 3.x or any version number at all.
I have answered my own Q&A thread with a link so hopefully others can find it. Will try it now.
xantanion said:
I used twrp 3.0. Worked like a charm what I ended up doing was reflashing the .43 and then the update after replacing the updater script file here is a link to the thread with the 3.0 twrp http://forum.xda-developers.com/padfone-x/general/padfone-xs-to-stock-lollipop-root-t3263664
Click to expand...
Click to collapse
Thankfully it has worked many thanks. Unfortunately while Sky Q no longer complains about root, it does complain about my Padfone station being an external display, so still won't play videos
I guess I'm a moron and can't figure this out :v
Using stock rooted Oreo, Magisk, edXposed, everything that goes with them. TWRP 3.2.3-7.
Lately, I've been using my headphones while driving to work. I need a touch more volume over stock to deal with wind noise.
The problem is, I absolutely can't get /system/vendor/etc into a writable state.
Attempts to modify mixer_paths_tavil.xml whilst booted up fail, either resulting in an unreadable file (Total Commander) or just not working (Root Explorer).
Trying to flash a modified zip (just grabbed a dual-speaker mod and replaced the xml) in TWRP results in no file being created; it doesn't seem to throw an error, just silently fails.
Manually copying the xml to /system/vendor/etc using TWRP's file manager ~appears~ to work, but attempts to set permissions results in error code 1. The file doesn't exist upon reboot.
Remounting manually as RW in TWRP's terminal doesn't seem to help. And yes, "mount System as read-only" is unchecked.
I can make build.prop changes, so I know /system is writable. The only way I can get anything written to /system/vendor/etc is restoring a full system backup.
I've modified this file before; I manually tweaked the call volume higher and enabled "fake" high-impedance mode.
So I'm sure I'm doing something really stupid here. Help.
Septfox said:
I guess I'm a moron and can't figure this out :v
Using stock rooted Oreo, Magisk, edXposed, everything that goes with them. TWRP 3.2.3-7.
Lately, I've been using my headphones while driving to work. I need a touch more volume over stock to deal with wind noise.
The problem is, I absolutely can't get /system/vendor/etc into a writable state.
Attempts to modify mixer_paths_tavil.xml whilst booted up fail, either resulting in an unreadable file (Total Commander) or just not working (Root Explorer).
Trying to flash a modified zip (just grabbed a dual-speaker mod and replaced the xml) in TWRP results in no file being created; it doesn't seem to throw an error, just silently fails.
Manually copying the xml to /system/vendor/etc using TWRP's file manager ~appears~ to work, but attempts to set permissions results in error code 1. The file doesn't exist upon reboot.
Remounting manually as RW in TWRP's terminal doesn't seem to help. And yes, "mount System as read-only" is unchecked.
I can make build.prop changes, so I know /system is writable. The only way I can get anything written to /system/vendor/etc is restoring a full system backup.
I've modified this file before; I manually tweaked the call volume higher and enabled "fake" high-impedance mode.
So I'm sure I'm doing something really stupid here. Help.
Click to expand...
Click to collapse
Don't know, but tonight or tomorrow I'll shoot you a file to test.
ChazzMatt said:
Don't know, but tonight or tomorrow I'll shoot you a file to test.
Click to expand...
Click to collapse
Appreciated, but I think something's going pear-shaped and I just need to reflash the ROM; setting up for the drive home last night, it seems I've lost the ability to use direct output in Poweramp. I don't know how, since the system+system image backup I restored is known-good and audio is otherwise working.
Good ol' bitrot, I suppose.
Septfox said:
Appreciated, but I think something's going pear-shaped and I just need to reflash the ROM; setting up for the drive home last night, it seems I've lost the ability to use direct output in Poweramp. I don't know how, since the system+system image backup I restored is known-good and audio is otherwise working.
Good ol' bitrot, I suppose.
Click to expand...
Click to collapse
See my PM.