I am trying to find the CSC files for my US 6210 to hopefully alleviate some problems. I am trying to fix an error in recovery that is bugging me while also trying to figure out battery drain but that is in another thread.
So if someone could point me to the CSC file that would be great as I have been searching for quite some time.
Also is it even possible to find such a file?
Is the error in recovery something like this: "Can't access to /system/csc/XAR/system" ?
Sent from my GT-P6210
That is pretty much the error if not the exact error I am getting.
Zadeis said:
That is pretty much the error if not the exact error I am getting.
Click to expand...
Click to collapse
Ok, I have that too and have wondered what it is. At least it doesn't cause any problems for me, and I don't remember having seen the recovery without that error.
Here is a thread about the error on S II, and some seem to consider it normal...
http://forum.xda-developers.com/showthread.php?t=1154109
Sent from my GT-P6210
Well, now that I think about it... What if someone packaged up this XAR folder (if they even have it) and maybe we could try putting it on our Tabs to see if it makes any difference? Or does every owner have this error and it's nothing to worry about
This is one of my two problems currently with this Tablet. I sent it into Samsung for them to fix two other problems only for them to fix one of them and ignore the other.
Zadeis said:
Well, now that I think about it... What if someone packaged up this XAR folder (if they even have it) and maybe we could try putting it on our Tabs to see if it makes any difference? Or does every owner have this error and it's nothing to worry about
Click to expand...
Click to collapse
I read that some just made empty folders with file explorer to the path it wants and that fixed it, so copying the XAR folder could at least remove the error text in recovery.
I don't know if every owner has this or does the error even cause anything bad...
Sent from my GT-P6210
Well you could be correct and it may not be anything bad. I am just trying to diagnose another problem ( seen here )
Getting this one problem fixed may help my other problem, it may not but it's worth a try in my mind.
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:
Hey guys,
followed every single word from all the threads concerning Data2SD, and still can't get it to work...
I keep on getting an error message as soon as the device is done booting.
I then get a "unsuccesful encryption" message stating that I should do a factory reset etc.
However, even after trying like all the possible combinations of .zip orders, I still keep getting that message.
I'd appreciate if someone could give me a hand
(PS: I did try to do the disabling journaling, but it seems the problem should be found there!
Let me show you in the attached screenshot of my adb commands! )
adelancker said:
Hey guys,
followed every single word from all the threads concerning Data2SD, and still can't get it to work...
I keep on getting an error message as soon as the device is done booting.
I then get a "unsuccesful encryption" message stating that I should do a factory reset etc.
However, even after trying like all the possible combinations of .zip orders, I still keep getting that message.
I'd appreciate if someone could give me a hand
(PS: I did try to do the disabling journaling, but it seems the problem should be found there!
Let me show you in the attached screenshot of my adb commands! )
Click to expand...
Click to collapse
I believe the issue is with your SDcard. Your device did not see the second partition ext4.
After an extensive search of both this site and using google for the error, I am stuck at a crossroads in terms of trying to install the GPE DigitalHigh edition on my HTC One M8.
The issue is as follows:
Installed RUU of GPE 5.1 (this is the only RUU I have at present)
Did all the various system & cache wipes etc using TWRP
Did the filesize repair on System
Tried to install the above ROM using the installer and got the following error:
failed to mkdir /system/etc/firmware/wcd9320/wcd9320_mbhc.bin: No space left on device
And then the various symlink errors associated and an Installation Status 7 Failed
Now I get the issue, in that the /system folder is clearly not big enough, an issue with the GPE RUU from what I have read. However, the only advice I can find to rectify this is to use the RESIZE option in Advanced Wipe in TWRP. However, I have done this, I've even done it a few times in succession in case it is like the RUU process and doesn't necessarily work first time. However, another run of the installer and I get the exact same error. Looking at my system (in Wipe) after a failed install, I can even see that the system partition is full, but I don't know how else I can resize it to avoid this error.
As I said, trawled through almost 500+ posts trying to find answers, from where I gleaned the above information, but no other way to resize the system partition than the method I tried. Therefore, I would genuinely appreciate any help anyone could give in overcoming this error, by whatever method is best/works best.
I have full log file from my failed install and can also explain the steps I took / files I used in more detail too if necessary. At present, it's just a case of another RUU of the GPE 5.1 at the moment until I can find a solution Purely wanting to install so I have the M8 camera functionality back if anybody has any other tips for achieving this other than the above (again, searches etc have led me to the camera.apk, I've had it installed etc but the editor still goes to the FX editor, without any of the HTC sense camera functions (like Duo, U-Focus etc) that I am keen to get back.
Again, apologies if this is answered elsewhere, but it's not for the want of looking, and as a new user not allowed to post directly on the ROM post yet. I would appreciate any help.
Thanks,
Sie
siepod said:
After an extensive search of both this site and using google for the error, I am stuck at a crossroads in terms of trying to install the GPE DigitalHigh edition on my HTC One M8.
The issue is as follows:
Installed RUU of GPE 5.1 (this is the only RUU I have at present)
Did all the various system & cache wipes etc using TWRP
Did the filesize repair on System
Tried to install the above ROM using the installer and got the following error:
failed to mkdir /system/etc/firmware/wcd9320/wcd9320_mbhc.bin: No space left on device
And then the various symlink errors associated and an Installation Status 7 Failed
Now I get the issue, in that the /system folder is clearly not big enough, an issue with the GPE RUU from what I have read. However, the only advice I can find to rectify this is to use the RESIZE option in Advanced Wipe in TWRP. However, I have done this, I've even done it a few times in succession in case it is like the RUU process and doesn't necessarily work first time. However, another run of the installer and I get the exact same error. Looking at my system (in Wipe) after a failed install, I can even see that the system partition is full, but I don't know how else I can resize it to avoid this error.
As I said, trawled through almost 500+ posts trying to find answers, from where I gleaned the above information, but no other way to resize the system partition than the method I tried. Therefore, I would genuinely appreciate any help anyone could give in overcoming this error, by whatever method is best/works best.
I have full log file from my failed install and can also explain the steps I took / files I used in more detail too if necessary. At present, it's just a case of another RUU of the GPE 5.1 at the moment until I can find a solution Purely wanting to install so I have the M8 camera functionality back if anybody has any other tips for achieving this other than the above (again, searches etc have led me to the camera.apk, I've had it installed etc but the editor still goes to the FX editor, without any of the HTC sense camera functions (like Duo, U-Focus etc) that I am keen to get back.
Again, apologies if this is answered elsewhere, but it's not for the want of looking, and as a new user not allowed to post directly on the ROM post yet. I would appreciate any help.
Thanks,
Sie
Click to expand...
Click to collapse
You would have a better chance of finding a working solution if you go to the M8 forum.
I'll bet @xunholyx can get you straight, he's pretty experienced with the M8 I think.
siepod said:
After an extensive search of both this site and using google for the error, I am stuck at a crossroads in terms of trying to install the GPE DigitalHigh edition on my HTC One M8.
The issue is as follows:
Installed RUU of GPE 5.1 (this is the only RUU I have at present)
Did all the various system & cache wipes etc using TWRP
Did the filesize repair on System
Tried to install the above ROM using the installer and got the following error:
failed to mkdir /system/etc/firmware/wcd9320/wcd9320_mbhc.bin: No space left on device
And then the various symlink errors associated and an Installation Status 7 Failed
Now I get the issue, in that the /system folder is clearly not big enough, an issue with the GPE RUU from what I have read. However, the only advice I can find to rectify this is to use the RESIZE option in Advanced Wipe in TWRP. However, I have done this, I've even done it a few times in succession in case it is like the RUU process and doesn't necessarily work first time. However, another run of the installer and I get the exact same error. Looking at my system (in Wipe) after a failed install, I can even see that the system partition is full, but I don't know how else I can resize it to avoid this error.
As I said, trawled through almost 500+ posts trying to find answers, from where I gleaned the above information, but no other way to resize the system partition than the method I tried. Therefore, I would genuinely appreciate any help anyone could give in overcoming this error, by whatever method is best/works best.
I have full log file from my failed install and can also explain the steps I took / files I used in more detail too if necessary. At present, it's just a case of another RUU of the GPE 5.1 at the moment until I can find a solution Purely wanting to install so I have the M8 camera functionality back if anybody has any other tips for achieving this other than the above (again, searches etc have led me to the camera.apk, I've had it installed etc but the editor still goes to the FX editor, without any of the HTC sense camera functions (like Duo, U-Focus etc) that I am keen to get back.
Again, apologies if this is answered elsewhere, but it's not for the want of looking, and as a new user not allowed to post directly on the ROM post yet. I would appreciate any help.
Thanks,
Sie
Click to expand...
Click to collapse
You need to run a Sense RUU to resize your partitions. The GPE system partition is too small for Sense based ROMs and RUU is how you fix it. Just like you ran a GPE RUU to resize your partitions for that.
---------- Post added at 06:17 PM ---------- Previous post was at 06:11 PM ----------
If you don't know where to get the RUU, or if you need instructions, post/reply here and I'll give you complete directions on how to do it.
xunholyx said:
You need to run a Sense RUU to resize your partitions. The GPE system partition is too small for Sense based ROMs and RUU is how you fix it. Just like you ran a GPE RUU to resize your partitions for that.
---------- Post added at 06:17 PM ---------- Previous post was at 06:11 PM ----------
If you don't know where to get the RUU, or if you need instructions, post/reply here and I'll give you complete directions on how to do it.
Click to expand...
Click to collapse
Thanks for your reply. Really appreciate your help. I think I'm ok with the RUU process itself, as I ran it to get to this point, however I'm not sure where to locate the RUU I would need to effectively "roll back" to stock, so any help with that, and directing me in which of the plethora to choose would be greatly appreciated! Perhaps if you could give me simple instructions, so it's not too time consuming for you, but to ensure I'm not missing anything in the RUU process that could lead to further complications, that would be a big help too!
siepod said:
Thanks for your reply. Really appreciate your help. I think I'm ok with the RUU process itself, as I ran it to get to this point, however I'm not sure where to locate the RUU I would need to effectively "roll back" to stock, so any help with that, and directing me in which of the plethora to choose would be greatly appreciated! Perhaps if you could give me simple instructions, so it's not too time consuming for you, but to ensure I'm not missing anything in the RUU process that could lead to further complications, that would be a big help too!
Click to expand...
Click to collapse
Download this splash.zip, rename it to 0P6BIMG.zip and place it onto your extSD. Boot into bootloader and select hboot if it doesn't automatically. Vol up to flash, power to reboot. That'll repartition your phone, but with old firmware. Delete the renamed zip from extSD, otherwise every time you boot to hboot it'll try to update again.
Next, download this RUU onto your PC to update to Lollipop. Hook up your phone and double click on the download, then follow the prompts. You'll probably get a "fail hboot pre-update" (or something like that). The first run updates the hboot with old firmware. Just run the RUU a second time without disconnecting, and the conversion back to Sense will be complete.
xunholyx said:
, rename it to 0P6BIMG.zip and place it onto your extSD. Boot into bootloader and select hboot if it doesn't automatically. Vol up to flash, power to reboot. That'll repartition your phone, but with old firmware. Delete the renamed zip from extSD, otherwise every time you boot to hboot it'll try to update again.
Click to expand...
Click to collapse
You are an absolute star, thank you. Will give this a bash when I get home from football later today, and let you know how I get on or if I have any problems. Great written instructions though, thanks!
xunholyx said:
, rename it to 0P6BIMG.zip and place it onto your extSD. Boot into bootloader and select hboot if it doesn't automatically. Vol up to flash, power to reboot. That'll repartition your phone, but with old firmware. Delete the renamed zip from extSD, otherwise every time you boot to hboot it'll try to update again.
Click to expand...
Click to collapse
Just had a try, get Update Fail! in red text when I try to do the Hboot. Not sure why?
Thanks,
Sie
siepod said:
Just had a try, get Update Fail! in red text when I try to do the Hboot. Not sure why?
Thanks,
Sie
Click to expand...
Click to collapse
I'm not sure.
Try the splash.zip download and instructions from here. It should be the same file, but trying another download and flashing from your PC might work better for you.
xunholyx said:
I'm not sure.
Try the splash.zip download and instructions . It should be the same file, but trying another download and flashing from your PC might work better for you.
Click to expand...
Click to collapse
Brilliant, tried those and it worked a treat. Then installed using the RUU you gave me, and as promised I was greeted with a full back to stock Sense version, and have been able to install the ROM I wanted. Thanks once again for all your help, truly appreciated!
I'm guessing it was the CID that was causing the error, if anybody has the same problem in the future and ends up on this thread. I'm guessing if I'd have changed the CID your method with the HBOOT would probably have worked too (as out of curiosity I tried the HBOOT method with your file and it then worked).
Thanks again, great to know there are people out there willing to try and help each other. :highfive: