Develop Bugs

Cannot Mount System as r/w

I have searched the entire forum and haven't found the answer to my problem...I have even asked in the rom specific thread (where other people have had a similar problems) but my question (and theirs) just gets overlooked!!
So here it is.
I have both radio S-off and the End Hboot and have flashed three different custom roms on my HD (the Core Droid, Revolution HD and LeeDroid) all giving me the same problem.....I cannot set the system as r/w using apps such as Root Explorer and SUFBS!
I tried entering the mount command by itself in a terminal on the phone and I get:
# mount
mount: no etc/mtab
I can however mount the system from adb shell by inputting: mount -o remount,rw /dev/block/mmcblk0p25 /system
but that isn't really a solution!
I have a nandroid backup of my original stock rom which I have rooted and I can mount the system fine using root explorer and do not get this 'no etc/mtab' message when I type mount in the terminal.
I find it odd that it occurs with three different custom roms but not on my original stock rom so maybe it could be the way I flash the roms? ...I always use the Full_Wipe.zip with CWM recovery which formats the boot, system, data and cache partitions and then I apply the rom.
I've been pulling my hair out over this...and I know it must be something simple, but I've been stuck with this problem with no solution for a week!
Does anyone have any ideas?
EDIT: It turns out that some of the custom roms have limits in place that prevent editing the system and therefore were causing errors. Have tried the Cyanogen rom and have not encountered the errors/restrictions so it was definitely due to those custom roms. Not really a solution, but found the 'cause' of the problem.

Hmmm....looks like I'm the only one with this problem. Has no one else had anything similar?

your not the only one, i hbave had this too, this prevents you from removing apps doesnt it, now is it the 1.72 rom or the 1.34 rom

try to download Root Tools and go to Extras and then go to MIscellaneous and select "mount system read/write". if it does not work i guess that you have an issue with phone.

if its a 1.72 rom then you wont be able to mount it, i think HTC have decided to change the mount partition or something along that line, there isnt an issue with the phone, its just HTC have plugged up the root boothole that there was.

mariosraptor said:
try to download Root Tools and go to Extras and then go to MIscellaneous and select "mount system read/write". if it does not work i guess that you have an issue with phone.
Click to expand...
Click to collapse
Just tried that option and it does work as it succesfully mounts the system as r/w. However, if I go into root explorer it doesn't allow me to toggle the system as r/o....so the mount commands from my currently installed apps are not working. Could it be something to do with restoring the apps from my old Milestone onto the Desire HD using totanium backup? Actually restoring through titanium backup shouldn't be a problem since it works with the stock rooted rom.
fkofilee said:
if its a 1.72 rom then you wont be able to mount it, i think HTC have decided to change the mount partition or something along that line, there isnt an issue with the phone, its just HTC have plugged up the root boothole that there was.
Click to expand...
Click to collapse
I've heard about that problem too....but my current rom is based on the 1.34 rom (Core Droid V1.5), so its not that...

after doing what you have to do you can go again to Root Explorer and remount as read only.
fl4r3 said:
Just tried that option and it does work as it succesfully mounts the system as r/w. However, if I go into root explorer it doesn't allow me to toggle the system as r/o....so the mount commands from my currently installed apps are not working. Could it be something to do with restoring the apps from my old Milestone onto the Desire HD using totanium backup? Actually restoring through titanium backup shouldn't be a problem since it works with the stock rooted rom.
I've heard about that problem too....but my current rom is based on the 1.34 rom (Core Droid V1.5), so its not that...
Click to expand...
Click to collapse

mariosraptor said:
after doing what you have to do you can go again to Root Explorer and remount as read only.
Click to expand...
Click to collapse
I guess thats the best option for now...not a complete solution, but a work around that doesn't require a pc at least.
Would still be good to find the cause and fix it!

I've got the same issue! Are you sure the error you receive is 'no etc/mtab' and not 'no etc/fstab'?
Anyway I've been using the App 'Mount System (rw/ro)' as my solution for now and it works a treat. Still, as you can imagine it is not a permanent solution!
The only thing I feel may have contributed to the problem was my original root attempy via Visionary failed and I had to wait until the R13 before I could unroot and root again. Possibly something got borked along the way. Did you have any similar issues?
Will be keeping my eye on this thread and if I do find a solution I'll let you know.
Regards.

It’s definitely a ‘no /etc/mtab’ error.
When I rooted I used Visionary r14 and the only hiccup I had was that it didn’t permaroot on the first try so I had to redo it.
It’s odd that my nandroid backup of stock doesn’t give me the error and its only the custom roms that do! I have a feeling it might be something to do with an incorrect/incompatible Busybox installation with the custom roms...

sounds more app related as you can use another app to mount the system, but not with root explore. i know this is obverse an you probably done it ,have you uninstalled root explore and reinstalled from market as you said you used titanium backup.
you could copy /etc/mtab from stock an place on sdcard and paste it in the custom.
not a solution but more see if its just a file that's missing
the only file i could find was vold.fstab and my base rom is 1.72.405.3 and root explore works fine.

cattleprod said:
sounds more app related as you can use another app to mount the system, but not with root explore. i know this is obverse an you probably done it ,have you uninstalled root explore and reinstalled from market as you said you used titanium backup.
you could copy /etc/mtab from stock an place on sdcard and paste it in the custom.
not a solution but more see if its just a file that's missing
the only file i could find was vold.fstab and my base rom is 1.72.405.3 and root explore works fine.
Click to expand...
Click to collapse
I've tried looking for /etc/mtab in my stock rom but its not present..I don't think its a physical file thats why it can't be copied....
But I think you may be right about it being an app based problem...just tried LeeDroid V1.3 (based on 1.72 rom) out of curiosity and root explorer still wasn't working. I then wiped again but installed root explorer fresh from the market instead of titanium backup and it is now working!! YAY!!
However, SUFBS still does not work and returns 'no /etc/mtab' when I type 'mount' in its terminal and reinstalling (either from titanium backup or fresh from the market) does not make a difference. Since root explorer is now working I believe that the dev for SUFBS needs to update his app maybe?..or is there still something wrong with my system?

yes sir !!! that is where your correct !!!
the current custom roms bar... Cyanogenmodm dont allow the current installed apps to be changed due to your error message.
IF YOU ARE CONFIDENT WITH ADB COMMANDS; you can have ago at pushing and pulling and mount it that way using a PC
but be very careful as you can damage your phone by doing this

fkofilee said:
yes sir !!! that is where your correct !!!
the current custom roms bar... Cyanogenmodm dont allow the current installed apps to be changed due to your error message.
IF YOU ARE CONFIDENT WITH ADB COMMANDS; you can have ago at pushing and pulling and mount it that way using a PC
but be very careful as you can damage your phone by doing this
Click to expand...
Click to collapse
Ahhhh, if thats true then it makes sense! Thats why the custom roms were giving me trouble but not my rooted stock rom and why adb commands from a pc work. I guess its a precaution but still an inconvenience...especially when I want to make changes/do something away from the pc.
......the question is: is it true? are you 100% sure the custom roms don't allow changes?

its 100% true, well most of the new ones anyway, CM was built from open source code and is completly there creation BUT
custom roms created from stock are basically modded ROMS

Just tried Cyanogenmod rom 6.1.2 and have had no issues at all! So it seems fkofilee is right...some of the custom roms just don't allow changes to the system.
So not really a solution but atleast found the 'cause' of the problem.

I noticed you said you used the full wipe .zip has everyone else used it ??? As I did not use it the first Rom I flashed was leedroid 1.2 and then 1.3 the only thing I used was cw recovery wipe/factory reset and my root explorer never failed can toggle between the two and when I first booted all my apps synced back via market did not use titanium backup not keen on it also I've read a few posts problems with titanium not restoring apps also read somewhere the full wipe zip doesn't always work right maybe its the wipe and titanium that causing it
Just a thought
Sent from my leedroid v1.3a DhD via xda app

I use full wipe. Zip but I never have problems with root explorer. Been using more than 1 Rom. ( Modaco r 2, leedroid 1. 3, Hd revolution. And also I have modded them a lot to look aosp.
Sent from my LeeDroided Desire HD

Restroring /data Directory

Hi all,
I have been using the GNex V7.4 Toolkit to backup, unlock, root and upgrade my new Nexus. Very cool tool...
I have however been geting some weird error messages when I try to perform a full NANDROID backup, errors such as:
snip
Dumping Boot Partition
/sdcard/clockworkmod/backup/2012-07-16.2.09.57/boot.img: cannot open for write: No such file or directory
Compressing /cache folder to a tar file
su
tar -pcvf /sdcard/clockworkmod/backup/2012-07-16.2.09.57/cache.ext4.tar /cache
exit
exit
[email protected]:/ # su
backup/2012-07-16.2.09.57/cache.ext4.tar /cache <
tar: can't open '/sdcard/clockworkmod/backup/2012-07-16.2.09.57/cache.ext4.tar': No such file or directory
end snip
Looks like an SD Card permission problem of some sort.
As a result, I don't have a full NANDROID backup prior to doing a recent ROM upgrade to Darkpaladin's v2.1 - which I am really enjoying.
What I did do prior to the full wipe was a full backup of all apps, SD Card backup and Data folder backup.
Question 1 - Is there anything obvious aout what's going wrong with my NANDROID backup? I need to get this going in future anyway...
Restoring from the App and sdcard/media backups has been OK (altough I too have suffered from the problem with the Camera not being able to write to the virtual SD Card - you have to rename the DCIM folder and force the phone to recreate the DCIM folder then copy your pix back into it to work), but there is no option to restore the /data folder (and subfolders) from the backup tar file.
Question 2) Is this by design?
Question 3) Is there a relatively easy way to restore all my phone settings from the data tar file? To me it would seem I need to be in recovery to do this, to avoid file-lock issues that may occur when Android is running.
Thanks for any tips.
Cheers,
Martin.

mlindema said:
Hi all,
I have been using the GNex V7.4 Toolkit to backup, unlock, root and upgrade my new Nexus. Very cool tool...
I have however been geting some weird error messages when I try to perform a full NANDROID backup, errors such as:
snip
Dumping Boot Partition
/sdcard/clockworkmod/backup/2012-07-16.2.09.57/boot.img: cannot open for write: No such file or directory
Click to expand...
Click to collapse
I've got the same problem...
This was working fine before I received the OTA of JB.
I told it to reboot with insecure boot image, so I don't think it's that. I also have root and busybox installed and working.
I may know why... The toolkit creates a directory for example:
2012-07-21.18.44.47
and then the errors state it can't write to:
2012-07-21.18.48.01
Looks like it's maybe looking for the wrong directory name...
Did you get the problem sorted on your machine?
(same problem with 7.4 and 7.5 toolkit versions)
Luke
[edited for clarity of the error - and I'm not up the required number of posts to post in the GNex/dev thread.. ]

Follow up info:
I realized that this worked last time I was on my other computer, then I checked the version and it was 7.2 of the Toolkit.
The machine it worked on was windows XP + GNex Toolkit v7.2, when I was running 4.0.4.
It doesn't work on Windows 7 + GNext Toolkit 7.4 (or 7.5) running 4.1.1.
I suspect something may have changed in the toolkit between version 7.2 and 7.4.
Luke
mckennal said:
I've got the same problem...
Click to expand...
Click to collapse

Additional Info
mckennal said:
Follow up info:
I realized that this worked last time I was on my other computer, then I checked the version and it was 7.2 of the Toolkit.
The machine it worked on was windows XP + GNex Toolkit v7.2, when I was running 4.0.4.
It doesn't work on Windows 7 + GNext Toolkit 7.4 (or 7.5) running 4.1.1.
I suspect something may have changed in the toolkit between version 7.2 and 7.4.
Luke
Click to expand...
Click to collapse
Hi Luke,
Glad that I wasn't Robinson Crusoe and the only one having this problem.
Yes, I originally wanted to post this in the Dev thread, where it belongs, and where you re-posted it (thanks for that). I was amazed that this forum wouldn't let me post there, as I had insufficient posts. Bit of a bummer of a system, and sort of treats new members as children. I have 25 years in IT and know how to behave in forums, and to do my homework before I go asking new questions... Anyway, that's just a pet peeve of mine.
Back to the topic - I still have the problem on the latest versions of the Toolkit (7.7 and 7.8 exhibit this problem too), but the Nandroid works if I choose the option that leaves the backup tar file on my phone. If I do this, the backup works every time.
Can you test on yours and update the Dev thread with the results? Hopefully Mark will read it and respond.
Cheers - Martin.

Help with endless nested /0/0/0/0 folders

Hi. I just switched from 1 custom 4.3 rom to a different one and i did a factory reset. However once i rebooted, i noticed that all my internal SD content had gone into 0/0/0/0 etc. i kept clicking but eventually file explorer on widows just froze.
I went into ES file explorer on my phone and saw the content was behind 400 0's!!!!
Anyone have any idea what i could do to recover that info? every time i try copying the files ES explorer either crashes or says that it had copied the files when it hadnt.
Any help would be greatly apreciated. I'm at my wits end... :crying:
Thanks

Bro you need to use a file explorer from recovery. TWRP custom recovery has a built-in file explorer. That should do the trick
Sent from my SGH-T999 using Tapatalk

aussie88 said:
Hi. I just switched from 1 custom 4.3 rom to a different one and i did a factory reset. However once i rebooted, i noticed that all my internal SD content had gone into 0/0/0/0 etc. i kept clicking but eventually file explorer on widows just froze.
I went into ES file explorer on my phone and saw the content was behind 400 0's!!!!
Anyone have any idea what i could do to recover that info? every time i try copying the files ES explorer either crashes or says that it had copied the files when it hadnt.
Any help would be greatly apreciated. I'm at my wits end... :crying:
Thanks
Click to expand...
Click to collapse
Also, you should update your recovery as the more recent versions have fixed that problem. It doesn't happen each time you flash with the new versions.

fingolfin14 said:
Also, you should update your recovery as the more recent versions have fixed that problem. It doesn't happen each time you flash with the new versions.
Click to expand...
Click to collapse
Yep I figured that out the hard way lol. Already upgraded to the latest version of CWM to prevent it from happening anymore. Now to get the files out from down there... :banghead:
Sent from my SGH-T999 using xda app-developers app

On Windoz, You could troll and copy out every 10 deep or 20 deep back to surface and then continue. That'd be better than crashing Explorer.
Dos Prompt is more rugged. You could write a batch script there.

Perseus71 said:
On Windoz, You could troll and copy out every 10 deep or 20 deep back to surface and then continue. That'd be better than crashing Explorer.
Dos Prompt is more rugged. You could write a batch script there.
Click to expand...
Click to collapse
I saw that somewhere and tried that. Doesnt seem to be having any effect. Unless im doing it wrong...
I'm plugging my phone into my computer, accessing the phone section when it comes up, going about 20 0s deep and copying it back to the root. It either crashes my windows explorer, or doesnt seem to be doing anything(i think because its already disconnected itself. i tried making a new folder and it wouldn't let). what am i doing wrong?
PS. how would i access my phones internal SD from DOS?
thanks

Try ADB FileExplorer that should not time out on Windows. I have also tried Android File Manager with success. If that does not work, I will look up other options.

Well i tried android file manager. Im not 100% sure exactly how these programs work, but either way its saying i dont have root access. I do and i also have chainfires adbd insecure app which should give me full root access, but its still not working.
I looked at ADB FileExplorer too, but i didnt really get it and it kept saying it couldnt find my phone and something about an incorrect path.

With the Android File Manager, when it accesses the Phone over ADB, it will ask for Root once. If you don't click SuperSU warning in that time, the File Manager will give this error. Please read its thread carefully. I have connected over ADBWIRELESS and this just fine.

Perseus71 said:
With the Android File Manager, when it accesses the Phone over ADB, it will ask for Root once. If you don't click SuperSU warning in that time, the File Manager will give this error. Please read its thread carefully. I have connected over ADBWIRELESS and this just fine.
Click to expand...
Click to collapse
It never asked for root on my phone. I've tried all the changes and everything else that people have recommended, but im still not having any luck. I guess im too much of a noob for all this lol :crying:

Try Re-mounting internal SD in Recovery and then connect to PC.

nope, still no luck. Its still saying no root and no supersu request is coming up. I guess im missing something....
EDIT: I seem to somehow be "losing" root every time i try to connect to the android file manager. i open an app that requires root and it says i dont have root. I have to reboot my phone to get root to work again. It's weird though, because SuperSU opens fine...

open the last "zero" folder on your computer, drag everything into a folder on your computer desktop, let everything copy (do something else in the mean time), delete your phone memory, copy everything back to your cleared phone memory card

Lieu10ant said:
open the last "zero" folder on your computer, drag everything into a folder on your computer desktop, let everything copy (do something else in the mean time), delete your phone memory, copy everything back to your cleared phone memory card
Click to expand...
Click to collapse
If only it was that easy. its behind 400 nested folders. Windows cant go that deep. it freezes and FC's after about 200.
Im giving my phone in to get my power button repaired, so i guess ill ask the software tech there if he can figure it out. But thank you Perseus for all your help last night. :good:

I also have this problem guys, how do i update my custom recovery please?

[Q] Messed up with platform.xml, help needed

Hello there,
I bought a LG G3 D855 16GB, rooted it and once I tried to backup with Titanium Backup to my external sdcard, I noticed I had no write permission.
I´ve followed this thread to get the permission --> http://forum.xda-developers.com/showthread.php?t=2617921
After reboot, I can no longer save anything to my internal storage (cannot download, can take pictures but they won't save, can't run some apps and so forth).
But...If I use a file manager (root explorer, ES file explorer) I'm able to copy files from external sdcard to internal storage.
Besides that, after messing up with platform.xml, I can't connect my phone to PC with MTP method nor PTP.
What have I tried, so far:
1. restore backed up platform.xml --> problem persists
2. replace platform.xml with original from someone else --> problem persists
3. Hard reset --> problem persists
4. Use LG Flash tool to unroot and replace firmware (.tot + .dll) --> Didn't work. Tried with files from different sources but always ended up with "model information check fail"
5. Use LG Flash tool 2014 to unroot and replace firmware (.kdz method) --> Didn't work. Tried with files from different sources but always ended up with interruption during s/w upgrade.
I've been playing/reading about this issue for around 3 weeks and still haven't figured out the solution. I do think it is something simple that I'm missing and I hope there's someone out here who can point me to the right direction. :fingers-crossed:
Thanks in advance!

anyone?
Come on fellows,
there's no one to help me out?
No clue at all?:crying:

problem solved!
Just to let you guys know, my phone is working again.
First I tried lg support tool but it also did not work. Then I performed (again) a Hard Reset, but this time using buttons combination (vol- and power). After this hard reset, I restore apps with Titanium Backup and everything is working fine!! :victory::victory:
Will play for I while with the phone and on the weekend try the unroot methods (.tot and .kdz) again to see if now they will work.

[Q] Unable to connect to PC properly after rooting

Hello,
I have had my HTC One M8 for a while now but I wasn't really happy with the soundquality while playing through my headphones, so I looked for ways to improve it. I found a few methods and finally decided to give it a try. These methods require a root so yesterday I have rooted my phone for the first time. Unfortunately I am experiencing some problems now.
The rooting process went without too much trouble. I used hasoon2000's toolkit and have TWRP version 2.7.0.2 installed as recovery and used it to install the provided SuperSU, which didn't work at first. On the forums I found a newer version and installed that one, updated it and got it to work.
Now this is where I think I messed up: I read somewhere that when rooted, you are able to delete pre-installed apps from the phone. I downloaded SD maid and deleted Kid Mode, Zoe and 7digital. When I deleted Kid Mode I got an error saying it has crashed. I tapped away the error but from this point I couldn't go back to my homescreen anymore because my launcher kept crashing (com.htc.launcher crashed). I rebooted the phone and the launcher worked again, but the phone still seemed to be buggy.
After this I tried to install the snapdragon audio+ (this was my first choice for an equalizer). I downloaded the apk and moved it to the system folder using ES file manager. I installed but when I tried to use it (through settings in google play music app) my phone would crash. I uninstalled it and tried again, but when I tried to move the apk to the system map like before, my phone would crash everytime. I then found out the file I used doesn't work for lollipop so I figured that's what caused the crashes.
My next move was to try and install viper4android. I downloaded it from the Play Store and opened it. It told me it needed an installation of BusyBox so I downloaded that too. But when I opened the BusyBox app and clicked install my phone would crash again. After some searching I found that the HTC One M8 requires BusyBox to be flashed manually so I downloaded the file but when I tried to load it onto my phone I noticed this wasn't possible anymore.
Now when I connect my phone to my PC the PC recognizes it, but when I open the map in Windows Explorer it only shows three maps; .showme, _nero_sync and Ringtones. I know there should be more as they were there before. It also shows my phone's capacity as a total of 10GB (shouldn't this be 16GB?). Also when I try to connect it with Sync Manager it gives me an error everytime I reconnect the phone; Device unavailable. Please reconnect your device [4].
I have tried to reset the phone through settings, wipe with TWRP and fix permissions with TWRP. I also tried reinstalling Sync Manager and the drivers on my PC. What I'm thinking now is I maybe have done something wrong in the ES file explorer that would make the folders unaccessible.
My phone is running stock android 5.0.1 and my PC Windows 7 64-bit.
I hope someone can help me, Thanks.
P.S: Sorry for the long post, I figured I'd give as much info as possible.

@Steef076 First update recovery to the latest one (2.8.6.0)
Second if you go and delete vital or integrated parts of the stock rom you will get a lot of bugs. Third, viper4android requires to write system and you can't write system with the stock kernel, you need an unsecured kernel or unsecure it yourself.
10GB is right since 6 is eaten by android. At this point I would just revert to a backup or install any custom rom around here. Most are close to stock and with no bloatware and come with root. You can even clean them further using a tool called ROM Cleaner. It will most likely solve all your problems

Did the deleted system apps reappear after reboot, or do they remain "uninstalled"? If the system is write protected like TempestZ states, any deleted system apps should reappear after a reboot.
Revert your nandroid to restore the system apps. And you didn't make a nandroid, you really should before making any system modifications for the very reason that it allows you to revert if you run into problems.
Another good practice, is if you don't know what effect deleting a system app will have (such as "safe to delete" lists that can sometimes be found on XDA) you should first freeze the app with Titanium Backup. If freezing doesn't cause any issues, then go ahead and delete. If you do have issues, just unfreeze the app.
Steef076 said:
Now when I connect my phone to my PC the PC recognizes it, but when I open the map in Windows Explorer it only shows three maps; .showme, _nero_sync and Ringtones. I know there should be more as they were there before. It also shows my phone's capacity as a total of 10GB (shouldn't this be 16GB?). Also when I try to connect it with Sync Manager it gives me an error everytime I reconnect the phone; Device unavailable. Please reconnect your device [4].
Click to expand...
Click to collapse
No, Windows will never show 16 GB. It only shows "internal storage" partition, or the user accessible portion of the storage. A good chunk is reserved for the OS.
Does what is shown in Windows differ from what is shown in ES if you browse to internal storage?

Thanks for the replies. @TempestZ @redpoint73
First of all I managed to update twrp to 2.8.6.0 using adb/fastboot.
To answer your question @redpoint73 the system apps I had deleted indeed reappeared after reboot. Also I didn't make a nandroid before I deleted the files, as I did not even know this was possible. Now I have made a nandroid of my stock ROM that is working decently, except for the TV app keeps crashing (I'm not opening it) and the connection to the PC is not working properly (not sure if this is ROM based?). I have noticed when the phone is in recovery I CAN see the folders through windows explorer. HTC sync manager still doesn't find it though. I am working on finding a proper stock ROM or maybe flash a custom one to see if that will fix it.
I understand now that the OS is taking up the storage space. The space windows is showing is the same as ES file manager so I guess this is fine.

HTC Sync is a hot mess. It often causes more troubles than it solves.
One thing you can try (to see if it fixes the USB connectivity) is uninstall HTC Sync and all HTC drivers. Than connect the phone. Don't let it install HTC Sync. Go to Windows Device Manager, find the device. Then pick the option to manually select the drivers, and pick the generic "Android MTP device" (or something to that effect) drivers.
This doesn't work for everyone. But it worked for me to be able to "see" the internal storage of my M8 on my home PC (Win 7). Annoyingly, it seems to vary from one PC to another. My work laptop (also Win 7) works fine with HTC Sync.

Steef076 said:
So if I understand correctly, 'version-main' is the same as 'firmware' and 'software number' (found in settings)? If so, my current firmware seems to be 4.19.114.2.
Now, what you're saying is I should do an OTA but this isn't possible because I have a custom recovery right?
Also, when I want to flash stock rom and stock recovery or do a nand don't I need the files that fit my cidnum? How would your file work for me?
Click to expand...
Click to collapse
If yours already on 4.19.114.2 then no need to do OTA as that the latest.
and my backup will bring back your device back to stock as you first bought it when restore with a full wipe.
Try to solve your problem first, only when you really need the backup then only I will upload ... let me know

ckpv5 said:
If yours already on 4.19.114.2 then no need to do OTA as that the latest.
and my backup will bring back your device back to stock as you first bought it when restore with a full wipe.
Try to solve your problem first, only when you really need the backup then only I will upload ... let me know
Click to expand...
Click to collapse
Hello, sorry for the late reply.
I have decided to give a custom ROM a try. I now have ARHD 41.0 installed and it seems this took care of my problems. All the maps are showing in windows explorer and HTC sync manager is connecting properly with my phone again. Also no more crashing apps. Your backup would still be of much use for me as I am not sure I want to stick with a custom ROM and therefore would like to have a stock ROM backup.
Thanks in advance.