Related
Hi,
I have searched in the forums but i couldnt find any solution to my problem.
My phone is a LG Optimus 7 unbranded on mango.
I want to backup my phone, update it to the latest rom with tethering enabled and after that i want to restore from backup.
How can i do that?
Thanks in advance!
There is no tool that can do that right now. The backup only happens when a new updates come in and Zune does that. It cannot be done manually.
Thanks for the fast answer!
So do i have to wait for the tethering update to appear in Zune or do i have to flash another firmware?
xtrcentral said:
Thanks for the fast answer!
So do i have to wait for the tethering update to appear in Zune or do i have to flash another firmware?
Click to expand...
Click to collapse
Only Zune will be able to do it. So I guess unless they do you have no choice. And No Firmware can enable it.
wpxbox is actually incorrect, there is a tool to create an image-based backup (like Zune does when updating) on demand. Search the Development and Hacking sub-forum, and you can find it. Note that it requires a program, updatewp.exe, that was once distributed by Microsoft and no longer is, so you'll need to find a copy of it (and the version for that copy must exactly match your Zune version).
However, what you're asking for isn't actually useful anyhow, unless you want to install the update and then immediately remove it. A WP7 backup is really more properly called a restore point - it's a full image of the phone's entire storage, including the parts that are normally read-only (the ROM). Restoring that image overwrites everything, including the ROM. Updates are modifications to the ROM, and restoring a backup will therefore remove the update.
That cleared the things... Thanks.
Thanks for correcting me. Apprciate that.
Yes there is a tool which you can find here but to make it work you need to use Old version of Zune and replace couple of DLL.
I personally have tried it but for some reason it did not work for and hence I was not recommending it. But thats me.
Go ahead and give it a shot to see if it works for you. If yes let me know how you did.
--wpxbox
GoodDayToDie said:
wpxbox is actually incorrect, there is a tool to create an image-based backup (like Zune does when updating) on demand. Search the Development and Hacking sub-forum, and you can find it. Note that it requires a program, updatewp.exe, that was once distributed by Microsoft and no longer is, so you'll need to find a copy of it (and the version for that copy must exactly match your Zune version).
However, what you're asking for isn't actually useful anyhow, unless you want to install the update and then immediately remove it. A WP7 backup is really more properly called a restore point - it's a full image of the phone's entire storage, including the parts that are normally read-only (the ROM). Restoring that image overwrites everything, including the ROM. Updates are modifications to the ROM, and restoring a backup will therefore remove the update.
Click to expand...
Click to collapse
Thanks for providing the direct link. I was able to get it working, although it took a lot of work to find matching versions of the tool installer (v1, not v2) and Zune software. It's possible, though. Take a look at the Backup header in this thread: http://forum.xda-developers.com/showthread.php?t=1271963. It has instructions and links that you may be able to use to make the tool work.
Hi,
I finally poured in one complete day figuring out what was in that thread and made it work. I have written my version of making it work here
And Have also created a Video Demo as a Proof that How I made it work. Any feedback is appreciated.
The video is like 11:28 Minutes long. Where I have :
First showed what is my phone
Then created a Backup
Showed where the backup is actually stored i.e. Zune Default restore point
Reset my Phone
Used the Backup to bring it normal state.
Here's the deal. I'm trying to update Android on my Touch Pro 2 (this issue isn't TP2 specific, so don't stop here if you don't own one ) I cant boot into the build I just installed (It hangs on the "XDANDROID" screen) I think my problem is happening because I did not do a clean install. I figured it would work if I simply replaced the old files with the now ones from this thread now I'm at work and do not have the file available. My work has the downloads blocked from XDA Developers, so here's my question:
Can someone go download the zip/rar file in the first post of this thread and tell me which files are included in the zip or post a screen shot so I can delete all the extra stuff I have.
I'm also open to other helpful suggestions if you have any.
TIA
So I got my self this nice tab ASUS Memo Pad HD 7 (ME173x), rooted the thing as soon as I got home, removed some bloatware and then after few hours a notification for an OTA upgrade hits me (wich ofc was not available manually).
You are obviously reading this 'couse the upgrade fails, just a broken droid when it tries to flash the upgrade.
Maybe the upgrade is like of a patch (it's just 56MB) and it fails me because I have removed some (well lots actually...) of those nice installed apps?
What to do? Wait for a maybe more substantial upgrade? Look for a full factory image? Just swap the tablet with a new one claiming that "OMG doesn-t-work" (hmm and what after I root the new one, de-bloat, and an other new upgrade hits the air...).
Thanks!
I found the upgrade, wich is cached in /cache/dlpkgfile (and it's a *.zip).
If I browse it I found a lot of apps patches in system/app : would it be safe to erase just those I've disinstalled, re-zip and try to upgrade?
Well the whole upgrade has a checksum, which is not easy to recreate as the script makepatch works (I guess) with a full source / dest combo. Nor it would be simply to re-install some of the apps from market as the versions could mismatch with those provided in the base.
This means that we should need backups from a original un-upgraded device, and see if that would get through the patching.
A factory image would be useful actually.
Hey, ea_.
Sorry that I can't really help you with the update or anything, but I was wondering if you could upload that dlpkg file somewhere for me.
A friend of mine has a MeMO Pad 7 HD here, and he messed up when (improperly) installing Chainfire 3D, rendering the device soft-bricked. Now it's all cool, because I can still access the system and manipulate it, and it's rooted on top of that, so I'm still in control. The problem is as you've mentioned: those idiots at ASUS don't have any upgrade/recovery images posted, so while I am capable of restoring the stupid thing, there's absolutely nowhere [that I can see] to restore FROM!
I was hoping to find someone with a tablet like this, who could share his system files or a recovery image of some sort from which I could recover the device...
IceDrake said:
Hey, ea_.
Sorry that I can't really help you with the update or anything, but I was wondering if you could upload that dlpkg file somewhere for me.
Click to expand...
Click to collapse
Too bad: I gave back my unit yesterday for a replacement (so I could back-up the whole thing as stock) but my shop was out of stock.
They say maybe they'll get some more by 9 August.
IceDrake said:
Hey, ea_.
Sorry that I can't really help you with the update or anything, but I was wondering if you could upload that dlpkg file somewhere for me.
A friend of mine has a MeMO Pad 7 HD here, and he messed up when (improperly) installing Chainfire 3D, rendering the device soft-bricked. Now it's all cool, because I can still access the system and manipulate it, and it's rooted on top of that, so I'm still in control. The problem is as you've mentioned: those idiots at ASUS don't have any upgrade/recovery images posted, so while I am capable of restoring the stupid thing, there's absolutely nowhere [that I can see] to restore FROM!
I was hoping to find someone with a tablet like this, who could share his system files or a recovery image of some sort from which I could recover the device...
Click to expand...
Click to collapse
I have one unit. Let me know what files you need, and I'll help you out.
ericmaxman said:
I have one unit. Let me know what files you need, and I'll help you out.
Click to expand...
Click to collapse
Sweet!
Essentially, I wanted the entire /system (/system/*) so I could compare all the files and find the ones that were modified, or in the worst case: replace them all with the working ones and keep the image for future recovery.
Seeing that the /system partition here is nearly 700MB in .tar.gz form, it might be a bit cumbersome to upload, so if there's a problem with that, these seem more essential to me than the rest:
/system/bin
/system/etc
/system/lib
/system/vendor
/system/build.prop
Click to expand...
Click to collapse
Also, /system/usr seems like it may contain device-specific/personal stuff, so you might want to skip this one either way.
Many thanks!
P.S. Sorry for shamelessly hijacking and derailing the thread. The one I created is here and may be more appropriate.
2 options:
1) restore the removed "bloatware" to its original location
I had the same problem. You can check the update log on the device after the update. I believe it is in /cache/recovery/last_log and you will find the problem.
In Android 4.2 you can better disable bloatware via app manager and disable apps you don't need. Or just rename .apk to .apk.ORG in /system/app (after used stop command and then rm /data/dalvik-cache/* and reboot)
2) restore complete firmware with these tools:
http://4pda.ru/forum/index.php?showtopic=486532
Latest full firmware is ME173X_WW_user_4.2.4.06716_20130918
If you use flash_tool.exe from ULK173_20130618_2123_CSC then load scatter file (MT6589_Android_scatter_emmc.txt) from the main firmware, then flash it.
See attached picture. It is a factory reset process!
Pandawill also has a section in the forum describing flash process: http://www.pandawillforum.com/showt...er-PX2-MTK8389-Quad-Core-(update-Sep-6th-2013)
I had just received a fresh new Galaxy SIII from Asurion and eagerly rooted and flashed my favorite AOSP ROM and found out my camera wasn't working. I search through these forums like a mad man trying to find a solution and I tried EVERYTHING but then I read someone's reply to troubleshooting and I admit I may have been overlooking the wording in some of these guides as to the path of my camera files but I fixed it and I want to share my findings so someone who is having a similar issue can get it fixed too. I'm also going to add the methods that didn't work but may work in other cases.
This fix ultimately replaces bad or missing firmware files. If you haven't tried Odin back to stock, re-rooting, or wiping data and getting a fresh start, I would recommend that first. This is more or less if sh** hits the fan.
THIS IS ONLY FOR THE GALAXY SIII
***MY FIX***
BACKUP ANYTHING IMPORTANT JUST IN CASE
Download this zip https://dl.dropboxusercontent.com/u/91693945/CameraFiles-signed.zip
Flash using Recovery
Wipe Cache & Dalvik (optional)
Fix Permissions
Reboot into Android
Start the camera app and cross your fingers
***MY FIX (Old Way)***
Download any TouchWiz based ROM to your phone or computer.
Unzip the ROM
Goto /system/cameradata and copy all the SlimISP files to your phone.
Goto /data and there should be another SlimISP bin file, copy that but don't mix it up.
Move these to the files to the corresponding areas of your phone.
Check permissions, I granted full access to Root, and User
Start the camera app and cross your fingers
Reboot if it didn't work immediately
I recommend keeping a copy of these on your ExtSD if you have one because you will have to do this if you flash a new ROM.
***Other Guides***
Same sort of directions also contains files you can download.
http://forum.xda-developers.com/showthread.php?p=40409206#post40409206
This is an explanation to what I put above and the guide that ultimately fixed my problems (Single-Post rest of thread is helpful too).
http://forum.xda-developers.com/showpost.php?p=37257851&postcount=11
For all you TouchWiz lovers, this might not be as relevant anymore but I'm putting it here anyway.
http://forum.xda-developers.com/showthread.php?t=2006128
SlimSnoopOS posted this below and I'll add it here.
http://rootzwiki.com/topic/100194-cant-connect-to-the-camera-again/page-2
If people have questions post them here or PM me I want to help anyone having this issue. Being as attached to my phone as I am I was really put out by all the trial and error.
Appreciate the guide, hope it helps someone down the road. I'm in the camp that has no issues going back and forth between AOSP 4.3 or TW. I'll add this Rootz link as well which provides some additional information and might be making its way into roms via Github. Seems like as good an opportunity to spread the wealth.
Zophone i5 v8?
dwibbles33 said:
I had just received a fresh new Galaxy SIII from Asurion and eagerly rooted and flashed my favorite AOSP ROM and found out my camera wasn't working. I search through these forums like a mad man trying to find a solution and I tried EVERYTHING but then I read someone's reply to troubleshooting and I admit I may have been overlooking the wording in some of these guides as to the path of my camera files but I fixed it and I want to share my findings so someone who is having a similar issue can get it fixed too. I'm also going to add the methods that didn't work but may work in other cases.
This fix ultimately replaces bad or missing firmware files. If you haven't tried Odin back to stock, re-rooting, or wiping data and getting a fresh start, I would recommend that first. This is more or less if sh** hits the fan.
***MY FIX***
Download any TouchWiz based ROM to your phone or computer.
Unzip the ROM
Goto /system/cameradata and copy all the SlimISP files to your phone.
Goto /data and there should be another SlimISP bin file, copy that but don't mix it up.
Move these to the files to the corresponding areas of your phone.
Check permissions, I granted full access to Root, and User
Start the camera app and cross your fingers
Reboot if it didn't work immediately
I recommend keeping a copy of these on your ExtSD if you have one because you will have to do this if you flash a new ROM.
***Other Guides***
Same sort of directions also contains files you can download.
http://forum.xda-developers.com/showthread.php?p=40409206#post40409206
This is an explanation to what I put above and the guide that ultimately fixed my problems (Single-Post rest of thread is helpful too).
http://forum.xda-developers.com/showpost.php?p=37257851&postcount=11
For all you TouchWiz lovers, this might not be as relevant anymore but I'm putting it here anyway.
http://forum.xda-developers.com/showthread.php?t=2006128
SlimSnoopOS posted this below and I'll add it here.
http://rootzwiki.com/topic/100194-cant-connect-to-the-camera-again/page-2
If people have questions post them here or PM me I want to help anyone having this issue. Being as attached to my phone as I am I was really put out by all the trial and error.
Click to expand...
Click to collapse
I am facing the same problem on my iphone clone - zophone i5 v8. These models do not have a "cameradata" folder in /system. Do you have a fix for these MTK phones?
shailendrachimade said:
I am facing the same problem on my iphone clone - zophone i5 v8. These models do not have a "cameradata" folder in /system. Do you have a fix for these MTK phones?
Click to expand...
Click to collapse
Me too had problem with camera, but it seems like i got fixed it finally... I have a Cubot One MTK6589 with Miui rom. The steps are:
1. http://d-h.st/BKA download this file and flash it. It will install jb camera for your mobile.
2. check it
3. if it works delete the old camera app with titanium backup because if u run the old bad camera app the problem will come back and u have to flash again.
4. install some good camera app like camera awesome because for me the jb camera doesn't detected my front camera.
I hope this will help you!
Will Try
papp-david said:
Me too had problem with camera, but it seems like i got fixed it finally... I have a Cubot One MTK6589 with Miui rom. The steps are:
1. http://d-h.st/BKA download this file and flash it. It will install jb camera for your mobile.
2. check it
3. if it works delete the old camera app with titanium backup because if u run the old bad camera app the problem will come back and u have to flash again.
4. install some good camera app like camera awesome because for me the jb camera doesn't detected my front camera.
I hope this will help you!
Click to expand...
Click to collapse
Let me try..thanks!
---------- Post added at 05:33 PM ---------- Previous post was at 04:58 PM ----------
shailendrachimade said:
Let me try..thanks!
Click to expand...
Click to collapse
I flashed successfully...but I do not see any camera app installed? I can see the Galary app. Even tried deleting original camera app by Titanium, still same issue.
Thank you. I also had this problem with any aosp ROM but the fix stopped working for me with the kk ROMs did you have the same problem?
Uou need to patch the shared objects using your stock tom files
Sent from my SM-N9006 using xda app-developers app
remzej said:
Uou need to patch the shared objects using your stock tom files
Sent from my SM-N9006 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply.. Bit could you explain a little more?
evertking said:
Thanks for the reply.. Bit could you explain a little more?
Click to expand...
Click to collapse
shailendrachimade said:
Let me try..thanks!
---------- Post added at 05:33 PM ---------- Previous post was at 04:58 PM ----------
I flashed successfully...but I do not see any camera app installed? I can see the Galary app. Even tried deleting original camera app by Titanium, still same issue.
Click to expand...
Click to collapse
dwibbles33 said:
I had just received a fresh new Galaxy SIII from Asurion and eagerly rooted and flashed my favorite AOSP ROM and found out my camera wasn't working. I search through these forums like a mad man trying to find a solution and I tried EVERYTHING but then I read someone's reply to troubleshooting and I admit I may have been overlooking the wording in some of these guides as to the path of my camera files but I fixed it and I want to share my findings so someone who is having a similar issue can get it fixed too. I'm also going to add the methods that didn't work but may work in other cases.
This fix ultimately replaces bad or missing firmware files. If you haven't tried Odin back to stock, re-rooting, or wiping data and getting a fresh start, I would recommend that first. This is more or less if sh** hits the fan.
THIS IS ONLY FOR THE GALAXY SIII
***MY FIX***
BACKUP ANYTHING IMPORTANT JUST IN CASE
Download this zip https://www.dropbox.com/s/bt1ucpgb9xfmjbi/CameraFiles-signed.zip
Flash using Recovery
Wipe Cache & Dalvik (optional)
Fix Permissions
Reboot into Android
Start the camera app and cross your fingers
***MY FIX (Old Way)***
Download any TouchWiz based ROM to your phone or computer.
Unzip the ROM
Goto /system/cameradata and copy all the SlimISP files to your phone.
Goto /data and there should be another SlimISP bin file, copy that but don't mix it up.
Move these to the files to the corresponding areas of your phone.
Check permissions, I granted full access to Root, and User
Start the camera app and cross your fingers
Reboot if it didn't work immediately
I recommend keeping a copy of these on your ExtSD if you have one because you will have to do this if you flash a new ROM.
***Other Guides***
Same sort of directions also contains files you can download.
http://forum.xda-developers.com/showthread.php?p=40409206#post40409206
This is an explanation to what I put above and the guide that ultimately fixed my problems (Single-Post rest of thread is helpful too).
http://forum.xda-developers.com/showpost.php?p=37257851&postcount=11
For all you TouchWiz lovers, this might not be as relevant anymore but I'm putting it here anyway.
http://forum.xda-developers.com/showthread.php?t=2006128
SlimSnoopOS posted this below and I'll add it here.
http://rootzwiki.com/topic/100194-cant-connect-to-the-camera-again/page-2
If people have questions post them here or PM me I want to help anyone having this issue. Being as attached to my phone as I am I was really put out by all the trial and error.
Click to expand...
Click to collapse
The file is not available on dropbox for download , i am using AOKP on SG3 and the camera stops working if i open through whatsapp or any other app and when i go back to the camera it gives that error
Try the One+ One or AOSP modded cameras in the Apps and Themes section. One+ One camera is awesome!
Ahmadqatei said:
The file is not available on dropbox for download , i am using AOKP on SG3 and the camera stops working if i open through whatsapp or any other app and when i go back to the camera it gives that error
Click to expand...
Click to collapse
Link fixed, sorry I don't really keep up with this anymore, my bad
fix front camera
work for my mtk device
edit builtprop, open the editor and change or add
hw.cameras=1
ro.camera.dcim=1
explanation
# hw cameras
hw.cameras = 2 (1 only for the Front, 2 for the Front & Back)
# camera DCIM dir. 0: sd only; 1: nand only; 2, sd first
ro.camera.dcim = 1
This is likely to occur due to the use of internal memory is converted into ROM
while the external sdcard memory is converted into internal
hopefully work
:cyclops:
Just sharing:
flashing didn't work, used servicely and added camera service to hitlist.
can i use it on galaxy core
HI, after a long saga trying to fix my camera issue (nioght shot mode getting stuck on "processing") I made a clean flash of MHA-L09C432B156.
All was well - camera issue gone and rooted etc. however I noticed that themes weren't applying. I transferred over the hw_int.zip contents to /data folder, which solved the theme issue but now my camera (night shot mode) doesn't work again!?
So good news is that the issue is ot hardware, though I must have used the wrong hw_int.zip
Can anyone link me to the correct hw_int.zip to use for my MHA-L09C432, with MHA-L09C432B156 if needed?
These are for L09C432B156
First flash public: http://update.hicloud.com:8180/TDS/...69/f2/full/public/update_data_full_public.zip
Then flash HW: http://update.hicloud.com:8180/TDS/...04/v75969/f2/full/hw/eu/update_full_hw_eu.zip
It's important that you flash public first because it deletes everything in the hw_init folder, unless you edit the script.
The reason... When you flash a full firmware using Funky or Firmware Finder both of those files get downloaded and flashed automatically.
When you format data all of that gets removed, that's why you have to flash them.
I have checked both actually for something related to camera and couldn't find anything...
But something obviously breaks it. Might just not be named camera or nightmode xD
Actually. If you did flash HW/Public for another phone the file dataversion.txt would be incorrect.
Not sure if that does much though.
If it doesn't work, try adb logcat while opening camera - nightmode and pastebin the log