Guest Ian-C Posted September 13, 2015 Report Posted September 13, 2015 In trying to allow access to sdcard by editing platform.xml in /etc/permissions I have it seems managed to lose all permissions for apps - though I don't know how I can check for sure.Like an idiot I don't have a backup copy of the platform.xml - adding one line I thought would be easy enough. Oh boy was I wrong.So now my rooted hudl2 boots, but will not run an apps that need access to sdcard/storage, and although wifi connects no apps can't use it (I guess due to permission problems too).I attach my platform.xml - I've check and re-checked and can't see anything wrong with the content, but it appears not to load.ls -l /etc/permissions/platform.xml gives:-rw-r--r-- root root 6044 2015-09-13 09:44 platform.xmlSo far I can transfer files back and forward to the hudl using adb pull / push - BUT can only push into /mnt/asec folder.On the hudl I have es file explorer - so can navigate and change files - except that it won't access /sdcard or anything in the /storage directory - it can see folders and subfolders, but all show as empty.I have a terminal emulator app installed, so can issue shell commands. As root I can access /sdcard and /storage (with sub directories).As it does boot, and even runs some apps (like angry birds) I would have thought this fixable, but I can't think of what else to try.I have to admit I'm stuck and would like to ask if any kind person could give me some help - maybe post their platform.xml and permissions (ls -l) for me to copy - or give me any other pointers on how I can fix this.The alternative may be to re-flash the system using system.hudl2.rooted.20150106.154003.ONLY.r1.zip - however my system is KOT49H.rel.android-build.20150519.110309 release-keysWould flashing back to an earlier rom brick the device? Has anyone tried - or have a rom for my version they could share?I would be really grateful for any help.Many thanks Ian platform.xml
Guest dennissingh99 Posted September 13, 2015 Report Posted September 13, 2015 You can flash the older rom to the device and wouldn't really have any problems, only until you get an ota. Because when the ota checks for the file versions, everything inside the system partition would have changed but not inside the boot partition. so you will need to modify the update script to not check for the boot image version and the fastboot version. You will only need to do this once though. P.S when flashing the modified ota zip, you will need to make sure to flash it using the tethered recovery. I hope this helps
Guest djnw Posted September 14, 2015 Report Posted September 14, 2015 I rolled back my meddled-with, rooted, Xposed-installed, platform.xml edited 20150519 H2 back using that very image from Paul and the standard instructions in his thread.There were no issues with OTA after doing it. I un-rooted it before doing the OTA, however, with an eye to the upcoming 5.1 update.
Guest Ian-C Posted September 14, 2015 Report Posted September 14, 2015 Thank you for helping. Fixed it now eventually - summary below just in case anyone else finds it useful.1st I tried extracting and copying over file platform.xml from Paul's image - didn't fix the permissions problem.2nd Tried "Fix permissions" option in TWRP recovery - didn't solve the problem either.3rd backed up partitions using TWRP and checked MD5 (had corrupt files with previous backup using CWM)4nd Then I flashed the entire 20150106 rom, but didn't do factory reset - this also didn't fix the permissions problem.5th Restored by original 20150519 system from backup using TWRP and cleared data (factory reset from recovery menu) - now working.Clearly something in data or cache was causing the problem with permissions - though I still don't know how this happened.I didn't initially do a factory reset as I was worried that if permissions errors were caused by something I had done in the system, then I would end up in a worse situation with the phone getting stuck on first run setup due to lack of permissions. Hence I chose this convoluted route of first restoring a rom.It's a really nuisance not being able to load a custom recovery or enter fastboot - it makes me nervous knowing how easily I can brick it.So many thanks once again dennissingh99 and djnw for giving me the confidence to flash back to an earlier rom.
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now