Database Info

Trying to flash a ROM to a7272 phone

Hello all,
I have a7272 Chinese phone and I accidentally deleted Google Contacts. Since I cannot reinstall it, I have to flash a new ROM.
Although the members here are brilliant, and I could find a lot of information here, I've been sitting a day and a half trying to solve my problem.
I managed to install CWMR by following this guide http://forum.xda-developers.com/archive/index.php/t-1825722.html- worked perfect.
I tried to flash this ROM http://forum.xda-developers.com/showpost.php?p=25575846&postcount=88 (I also need Hebrew in my phone), but I get error 16008 in SP Flash Tool, something about the partitions size.
Where can I find a suitable ROM for my phone?
I'm really frustrated :crying:.
Can someone help me please?

Wait isn't it just and android phone? How come you just don't find the APK file for Google Contacts?
Anyways with some research it seems that the partition tables are different in your phone or the recovery image isn't the right size. In the comments of the post Leonid says to do this "pressing the ::: (Format) * Auto Format Nand Flash -> Format whole flash except Bootloader and NVRAM Bin Region => OK
information is from here
http://bm-smartphone-reviews.blogspot.com/2011/10/mt65x3-flashing-tutorial.html
and if that doesn't work go here http://bm-smartphone-reviews.blogspot.com/2012/04/creating-rom-dump-of-your-mt65x3-device.html
Hope it helps, but try to find the APK File first.

obscuresword said:
Wait isn't it just and android phone? How come you just don't find the APK file for Google Contacts?
Anyways with some research it seems that the partition tables are different in your phone or the recovery image isn't the right size. In the comments of the post Leonid says to do this "pressing the ::: (Format) * Auto Format Nand Flash -> Format whole flash except Bootloader and NVRAM Bin Region => OK
information is from here
and if that doesn't work go here
Hope it helps, but try to find the APK File first.
Click to expand...
Click to collapse
It's not just contacts.apk, but maybe ContactsSynch and so. I still haven't found a proper way to reinstall this app, nor to flash my phone.
I saw that remark of Leonid, but I'm afraid that forcing this flash will do more harm than it is now. I didn't find any approval of this method anywhere.
MTK_Rom_Studio, for some odd reason, generating the scatter file with MT6516 in it's name, while my phone is 6573. This is strange.

PODLi said:
It's not just contacts.apk, but maybe ContactsSynch and so. I still haven't found a proper way to reinstall this app, nor to flash my phone.
I saw that remark of Leonid, but I'm afraid that forcing this flash will do more harm than it is now. I didn't find any approval of this method anywhere.
MTK_Rom_Studio, for some odd reason, generating the scatter file with MT6516 in it's name, while my phone is 6573. This is strange.
Click to expand...
Click to collapse
That sucks, but do you know the exact name of what you deleted, and did you every make like backups of your files.

PODLi said:
It's not just contacts.apk, but maybe ContactsSynch and so. I still haven't found a proper way to reinstall this app, nor to flash my phone.
I saw that remark of Leonid, but I'm afraid that forcing this flash will do more harm than it is now. I didn't find any approval of this method anywhere.
MTK_Rom_Studio, for some odd reason, generating the scatter file with MT6516 in it's name, while my phone is 6573. This is strange.
Click to expand...
Click to collapse
Did you check the posts on here? Try these suggestions:
http://forum.xda-developers.com/showthread.php?t=1409267

jhpianist said:
Did you check the posts on here? Try these suggestions:
http://forum.xda-developers.com/showthread.php?t=1409267
Click to expand...
Click to collapse
I gave up on the flashing idea. I said to myself I'll try to replace the missing apk's. Jhpianist, I saw that solution somewhere else already, and it somehow got to me that I can find the missing system apk's in one of the cooked ROMs I downloaded here.
Anyway, now I can sync my contacts and I'm able to dial or getting into my contacts, only through a third party app I had to install. Once I click on the original Contacts or Dial, I get the error "The process android.process.acore has stopped unexpectedly". No matter what I did, clearing the app cash, restore to default... nothing helped.
The guy who posted the solution, for reinstalling Contats.apk, said that one need to install the app once it's in system/app folder, in addition to changing its attributes. But I got a massage that the application wasn't installed once I tried.
How can I get rid of the stupid error? I feel I'm really close...
Thanks everyone :good:

[HOW-TO] [GUIDE] Fix "Cannot Connect To Camera" Error

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

Camera Crashes

I do not use my camera a lot, so, I can't 100% pinpoint when it broke (force closes/crashes/will not open).
I did recently flash a decrypt .img & immediately made a full backup & it's also broke in the earliest backup I could make.
I'm hoping installing the stock camera .apk will remedy this.
If someone could extract a copy & post in this thread, it'd be greatly appreciated.
Also, if anyone is certain that this likely won't fix it, I'm open to suggestions.

AdAway and Viper not working

Hi all
I recently unlocked my phone, installed twrp, all that good stuff. On stock firmware atm
However, when I try to download and apply inside AdAway it doesn't work, and it says something about not being able to copy the host files. I'd attach a link to a picture but my account is new so I'll write it out. Here it is-
Code:
Copy failed
Copy of hosts file failed!
Please read Help for more information.
And when I flash viper it installs, however it doesn't actually work, as in the audio doesn't sound any different.
Also I forgot to put in the title, magisk doesn't work either. It has an error code 1 or something, once again I'd attach a picture but I can't.
By the way I have root through flashing supersu
Has anyone else run into these issues, and if so were you able to fix them? Thanks in advance.
Additional thing I just remembered to add- I tried AICP yesterday, however the headphone jack didn't work, regardless of if I was using viper or not. I'm gonna reflash it now and post my results see if that was just a fluke.

[h910] rooted Oreo stock-based - get fingerprints AND radio working (if one isnt)

Hello everyone, I'm a total noob but I solved a problem which I couldn't find the answer to, so I thought I'd share. Please take care following my noob advice, I'm not responsible for anything which goes wrong with your phone (and if it gets complex, I probably don't have the skills to help)!!
What was my problem?
When I went from Nougat to Oreo, my radio broke (no cell reception). However I had the files from LGUP, so I could flash "fsg" "modem" "modemst1" and "modemst2" in fastboot (as explained here) which did indeed fix my modem problem, giving me back radio and data. However, this also made the fingerprint scanner disappear from my phone's settings menu. As far as I could tell, this wasn't a problem related to encryption (as discussed in AO ROM thread a lot, which is what I'm now running), rather 'twas a problem with the firmware! So I was loving Alpha Omega, but left without fingerprint scanner since radio isn't really optional on a phone.
Solution?
Please remember, I'm a noob and have only done this for my own phone, a h910, I don't know if i will work for you or on other models!!
Basically, I mish-mashed the two modem files from Oreo and Nougat, to get both things working!
Steps I took:
1) Use Linux - I couldn't get the files to open properly in windows, and didn't find a way to write to the image files.
2) Find a stock "modem.img" file from Oreo (i searched on google "stock oreo h910 modem and it came straight up) - I think I am too new on this forum to post outside links so you'll have to search for it.
3) Find a stock modem file from nougat (I used my original LGUP dump file from nougat, renamed to .img) I'm not sure if it is important that this came from your phone or not, if you followed all the instructions on the dirtysanta root guide, you'll have this as part of your LGUP backup.
NOTE: both of these files were 86 Mb (helped me feel confident I'd found the right thing on google)
4) Create backup copies of both, and append ".img" to your LGUP "modem" file. Call the backup of your OREO modem (the one you got off of google) "MyModem.img", just to keep it clear for later.
5) Mount the NOUGAT img first in a terminal (might have to make a mount point first), for me this was like this:
Code:
sudo mkdir /mnt/modemfiles
mount -o loop /path/to/your/nougat-modem-file.img /mnt/modemfiles
You obviously have to put the file path to where you saved your NOUGAT modem image - the one from LGUP!
6) You should now be able to see the nougat modem .img mounted as a disk in "places" on your file explorer. Go there, and copy the contents into a new folder somewhere easy to find (make a folder on your desktop called NougatModem.) There are two folders iniside, one called "image" and one called "verinfo".
7) Now you can un-mount, as we have what we need from it, easiest to do by just right-clicking it in file explorer and select unmount.
8) Next we will mount the image which will become your new (hopefully working!) modem, but it has to be writeable, so using the same mount point we would do
Code:
sudo mount -o loop,rw /path/to/MyModem.img /mnt/modemfiles
Remember that "MyModem.img" should be your backup OREO image - where all the firmware works but you don't get radio.
9) Now basically comes replacing a few files in the OREO modem (which we have mounted) with ones from your original NOUGAT backup (which are in that folder on your desktop). I couldn't remember if cp command replaced things with the same name, so I used rm to remove files, and then cp to replace them once they were gone.
a) first it is the folder called modem_pr, inside image
Code:
sudo rm -R /mnt/modemfiles/image/modem_pr/
b)next were all the files in the image directory which were modem.SOMETHING
Code:
sudo rm /mnt/modemfiles/image/modem.*
10) Finally we have to replace those files and the folder with the same things from our NOUGAT folder which is on our desktop, using the copy command. I will put the commands as if you did name that folder NougatModem
a) so first the folder which we removed
Code:
sudo cp -r ~/Desktop/NougatModem/image/modem_pr/ /mnt/modemfiles/image/
b) now all the files again, using the wildcard for the different extensions
Code:
sudo cp ~/Desktop/NougatModem/image/modem.* /mnt/modemfiles/image/
So if all went to plan, you now have an image (which you can unmount), called MyModem.img, which you can flash in fastboot to the modem parition (fastboot flash modem /path/to/MyModem.img) and if it works for you like it did for me, you have cell reception, data (after putting in APN if it's needed) and fingerprint scanner all working on OREO. Again, I'm on Alpha Omega, loving the rom and now going to go play a bit.
I've not been on the forum long, but have just gained a HUGE insight into how much time people put into making guides and helping others learn (this has taken me ages haha). Thanks to everyone for your hard work and community spirit, please let me know if this works for you or if it provides any interesting insight as I really did it blind (I had no idea if it would work, and was just making some slightly educated guesses - I got lucky!). Also, if the instructions are hard to follow and you have a hint, I'm happy to edit them to make them clearer.
ENJOY!!
PS - I know the linux commands could be better haha, using more than one mount point too might have been easier, but I figured that I'd just keep it exactly the same as how I did it since I'm a noob and would be more likely to screw something up in the instructions, if I changed it without trying at the same time!
EDIT: I could also upload my "patched" modem image, but not sure if it will work for other people's phones, or if it has "personal" or unique info in it (basically if it would be safe to do so) - If someone who knows tells me it'd be good to go, I'm happy to share it if it would save people from having to go through the whole process. I guess I hope posting all this will be a learning thing for others too Gotta have some justification haha!!

You are to be commended on your well presented write up. But I'm sure there is an easier way to get data and fingerprint working without going through all of that.
I don't have an original H910 device but I did flash H910 oreo kdz on my device and data did not work at all. Didn't test fingerprint. All I did was flash modem using lgup patched from another variant and that solved it.

ezzony said:
You are to be commended on your well presented write up. But I'm sure there is an easier way to get data and fingerprint working without going through all of that.
I don't have an original H910 device but I did flash H910 oreo kdz on my device and data did not work at all. Didn't test fingerprint. All I did was flash modem using lgup patched from another variant and that solved it.
Click to expand...
Click to collapse
Thank you for the commendation haha! What a mission!
So I'm guessing you flashed a different version's KDZ?? As far as I'm aware from lots of reading here on xda, there are no KDZ files for the h910. For me the kdz from h915 worked perfectly for example, apart from data. And that was the story with a few things I flashed, KDZ or ZIPs, they would break data, I'd flash the modem, and that would break the fingerprint scanner. Hence this long-winded solution lol.
If you have an original h910 kdz that people don't know about that'd be interesting in itself!!

No, I flashed a H910 ZIP that someone kindly uploaded here somewhere. Then I flashed back the modem from a Verizon kdz.

You are the best, I have been trying to solve this for a long time, I tried flashing many things it thanks to you I now have a working fingerprint and data. Although I am a complete noob for using linux I just used it for the first time using live boot. This is a challenge for noobs but worth it at the end and big thanks.

Why not just cross flash to us996 and walk away? 0_o You get a newer modem this way. I think you have to enable bands on some devices but on h910 I don't think even this matters. You are just downgrading the modem and keeping the new bootstrap. Still from what I read this is encryption issue. There was a supposedly a rsa key change during the update... without them matching the bootstrap will not will not load fingerprint software as it's not trusted unless it matches.

Vortell said:
Why not just cross flash to us996 and walk away? 0_o You get a newer modem this way. I think you have to enable bands on some devices but on h910 I don't think even this matters. You are just downgrading the modem and keeping the new bootstrap. Still from what I read this is encryption issue. There was a supposedly a rsa key change during the update... without them matching the bootstrap will not will not load fingerprint software as it's not trusted unless it matches.
Click to expand...
Click to collapse
So should I flash the whole ROM or just the modem of us996 to have both working?

DesrtSailor said:
You are the best, I have been trying to solve this for a long time, I tried flashing many things it thanks to you I now have a working fingerprint and data. Although I am a complete noob for using linux I just used it for the first time using live boot. This is a challenge for noobs but worth it at the end and big thanks.
Click to expand...
Click to collapse
Just wanted to say that made my day when I read that the original post had helped you out Cheers for letting me know

Awesome!! Thanks for this. Where did you get the idea of what files to change? Just curious.
I am still tinkering. I have an LGUP dump from:
ATT Stock
A-O Nougat install
A-O Oreo install
I was mix and matching the modem files with various modemst1 and modemst2 files. I did this because it seemed that I got better signal strength with the A-O Nougat install... but I got the kernel panic/modem crash whenever I lost signal on the phone. But with this hand made modem file - no crash. But now I am going to continue mix/match and see what crashes and what gives the best signal strength.
Anyway thanks a bunch!!

Please give me the patched modem file, please send it to [email protected]

I would root then try activity launcher or some sort if hidden menu launcher to get band menu. Alternatively get Network signal guru and lock bands. That how i did it in los 17.1 not sure if it would work on stock. I went from hspa to lte doing it in h915(it's a Canadian h910). I even crossflashed to us996 and left it that way. Says it even says band 66 was unlocked in the app but it has not been tested yet. Either way I got band 4 and 12 once I did this.