Related
Hi, I've read through quite a few pages but have no luck finding anyone resolving this issue. It's probably a fairly simple fix but I havn't figured it out yet.
Everytime I install an app through .cab file and choose to install it in my 4gb "external storage" it will not run properly. Everything installs perfectly fine but when I try to run it, it tells me something about not certified or some sort. I can't give the exact wording that WinMo said because I'm running chinese version. If anyone has a fix to this it is much appreciated. Thanks.
Search for sdkcert.cab and install it
MarcLandis said:
Search for sdkcert.cab and install it
Click to expand...
Click to collapse
Hi, I've installed the sdkcert.cab but it still does not work... What do I do now?
bump
so can someone on the forum tell me what I need to do for programs running off my 4gb to work? it seems everything I install on the 4gb will show up saying a trusted cert is missing or one of the file is missing. I'm pretty sure one of you guys out there already figured out how to fix this. Thanks in advance.
P.S.- I already installed the sdkcert.cab but it didn't do me anything or I don't know how to set it up.
Hi, I've found out the exact problem but I still need some help. This is the issue: after installation completes, if I run the program within my program list it will show up with a message that says I'm missing a trusted certificate or some sort. However, if I try to run the program from the folder I installed in, it will work, so I'm pretty sure I need to adjust something within the registry to adjust where my shortcuts are directing to. I believe this is an issue due to my Diamond being the chinese version. Anyone ran into similar problems or know how to fix this? Thanks.
I cann't recall since which build that I can not send SMS by Android correctly, which will display in strange codes. So far, Chinese, Japanese, Arabic have been tested and non of one seems to be normal. But it was working perfectly in era of kernel builds that doesn't enable speakers.
In days of searching, I found solutions on a Chinese forum discusing Android customize on Raphel. One of the guys released a modified version based on the builds orignaled here:
http://forum.xda-developers.com/showthread.php?t=601751
With a single rootfs.img replacement that the SMS problem solved, and SMS can be sent correctly and recieving correctly.
The modified rootfs.img file can be downloaded by this link:
http://www.multiupload.com/NEVY10ZCW5
The guy also released his source code at:
http://www.panshisoft.cn/bbs/viewFile.asp?BoardID=3&ID=19
and the compiled file "libhtcgeneric-ril.so":
http://www.panshisoft.cn/bbs/viewFile.asp?BoardID=3&ID=35
BUT, since this rootfs.img is dedicated to Raphel not Kovsky, while testing, I found it slow, not really stable and not enabled swapfile. And for the latest Kovsky, we can use out hardware keyboard.
I tried to port the libhtcgeneric-ril.so to rootfs.img of Kovsky owned, which comes from fatsal and the build of 20100221. But I failed.
So, please, can any one help me or giving me some tips of how to apply this patch on kovsky build correctly? There was a large amount of users with eastern character usage, and I think all of those will show their sincerely thankful like me to those who would wanna help.
Thx, B.rgds.
neock said:
it was possible to send sms through out system's built-in sms program in unicode, but some how i don't know why it couldn't now. some time ago i sent sms in chinese and it was ok, but now only strange characters, symbols instead.
i tried wiping out data.img swapfile, deleting cache folder, but no hope. and i turned to search for options or settings relate to sms characters or coding, and found nothing. i also tried third party sms program and still no luck. and google returns no useful infomations about "unicode sms", "character sms" and "android 短信 乱码".
any tips or solutions?
PS: using the latest zimage that enable speaker, not the one in topic of HERO build.
Click to expand...
Click to collapse
I can't surf the internet now………………
neock said:
it was possible to send sms through out system's built-in sms program in unicode, but some how i don't know why it couldn't now. some time ago i sent sms in chinese and it was ok, but now only strange characters, symbols instead.
i tried wiping out data.img swapfile, deleting cache folder, but no hope. and i turned to search for options or settings relate to sms characters or coding, and found nothing. i also tried third party sms program and still no luck. and google returns no useful infomations about "unicode sms", "character sms" and "android 短信 乱码".
any tips or solutions?
PS: using the latest zimage that enable speaker, not the one in topic of HERO build.
Click to expand...
Click to collapse
are you chinese?
no one knows how? or no one using non-english characters encounters problem but me?
@likuncheng1987
yes
NO IDEA!! aLTHOUGH I MYSELF WOULD LIKE URDU OR ARABIC KEYBOARD
哥们你不错了~~我根本就发不了短信`.....
每次都是发送失败
a little break through, but still not appliable. i faild my modding, and may need some help/
neock said:
...
I tried to port the libhtcgeneric-ril.so to rootfs.img of Kovsky owned, which comes from fatsal and the build of 20100221. But I failed.
So, please, can any one help me or giving me some tips of how to apply this patch on kovsky build correctly? There was a large amount of users with eastern character usage, and I think all of those will show their sincerely thankful like me to those who would wanna help.
Thx, B.rgds.
Click to expand...
Click to collapse
I'm not linux user but hope this could help How to make my own rootfs.img, some hints on post2
The libhtcgeneric-ril.so is a android library, so the direct way would be to put it into the system.sqsh (unsquash, copy to /lib, then squash it).
I took a quick look into the rootfs.img you mentioned. The init script does use the mount --bind command to "link over" existing files/dirs in the mounted system.sqsh, effectivly replacing them during boot with files from the rootfs.img. Quite clever. I did not find the part where your libhtcgeneric-ril.so is linked or copied, but i assume, that it is done.
So another way can be putting the libhtcgeneric-ril.so in the fatsal-rootfs.img and modifying the init script adding something like mount --bind /path/to/libhtcgeneric-ril.so /lib/libhtcgeneric-ril.so. Not sure about the command, i never tried that
Hope this helps.
good 支持你、、、
Hey folks,
This is a completely new build, with all the new changes baked in. We wanted to do a semi-official test release to collect bugs and hopefully do a formal official release with everything settled. The main pain point is the CSV files (see pre-install prep).
So a brief overview:
New acoustic routing code baked in. Should fix most if not all audio routing problems, and will provide more debugging if stuff does go wrong. Also allows for more granular tweaking, see the CSV files.
GPS fixes for GB - GPS not only works in GB now, but it doesn't kill sleep! I was able to use GPS, get a solid lock, and put the device to sleep no problem.
BT should work & well with the new acoustic code. Post results.
RHOD users now have a choice of kernels. .35+ all have the new acoustic - so .35, .39, 3.0 and 3.1 are all fair game now... This is bundled with .27!!
Keep in mind, autobuild .27 kernels will produce no audio in this build... Obviously the bundled kernel will work, and the absolute newest .27 autobuild kernel does work now - Feb.27 2012 or newer.
rootfs tweaks - first, it will detect which kernel you're on (.27 or .35+) and automatically apply the correct firmware. Second, is it will always copy/extract the modules... failures there were getting annoying, and this is surefire if brute-force...
Few Easter egg apk's...
Probably a lot I'm forgetting, this might change
Pre-Install Prep REQUIRED!!!
This step is crucial, and I forgot all about it! You must copy all of the *.CSV file from your WinMo ROM - these are in the \Windows\ directory. There's a very easy way to do this. It involves the Total Commander app for WinMo (Direct Link for the perpetually lazy...) (included in EnergyROM and others probably).
Now you're in Total Commander looking at your \Windows\ directory. Whew... lots of files. Fear not! Hit the "CTRL" button, then the green "Plus" button. This opens the Select/Unselect files dialog. Put in *.csv, press "select" and voila. All CSV files are selected. Now - File -> Copy/Move -> I want you to copy these (should be 10) files to the ROOT of your SD card. No folders!!! This is hardset right now, until we get it all implemented into the build properly. Thanks!
Install
Assuming you've done the pre-install prep; this is installed just like the other XDAndroid builds - grab your startup.txt (don't forget rel_path= if you don't have it at the root of the SD!), ts-calibration and boot!
Download
Caveat List
CDMA users might get a crash in phone.apk and no service on boot. If waiting doesn't resolve the issue, then reboot. Should come up fine...
BT might still be flaky
The CSV files from my TOPA100 are attached for the lazy. I'd like to gather CSV's from each RHOD, I'm curious if any ROM devs have changed them out either... This could get interesting. If you folks don't mind, post up your CSV's, point out differences with mine, etc... We're trying to figure out how to unify these, if possible! Thanks!
Please post back any issues, enjoy!
GBX0C Changelog
Camcorder: Now works (tested on rhodium).
Acoustic: Bug-fix : correct random loss of dual(rear)-mic.
MMS: Bug-fix: Slides with zero duration on Sprint.
Gps: Bug-fix: Init/de-init sequence fix (correct gps not starting up after being unchecked in Settings).
Gps: Bug-fix: End gps session with a correct rpc call (relevant to amss6125 devices).
Gps: Bug-fix: Don't send delayed position requests after session has ended (possibly relevant to Navigation issues).
Gps: New feature: Xtra (aGPS) -> verified to work on rhodium/cdma raph.
X1 specific: Screen rotation patch.
Added tytung's GPS injector app to AndroidApps\Other as well as updating/cleaning up some apps in AndroidApps.
Modified rootfs for newest apsta firmware & wifi firmware - wifi tethering now works flawlessly in the newest kernels! .27 is still bundled for the record...
not works for me (Topa100) stock on boot=(
doma999 said:
not works for me (Topa100) stock on boot=(
Click to expand...
Click to collapse
Any information you'd like to provide? I can't really help you, you've given me nothing to go on.
I assume you mean "stuck" on boot. So stuck on the haret loading bar? Stuck on the flying text? Stuck on the boot animation? C'mon.
sorry, of course, I install like you write above...in console it can't detect build type...install on root of sd all std startup for topaz, no changes...if it help I'll can take a photo of console
doma999 said:
sorry, of course, I install like you write above...in console it can't detect build type...install on root of sd all std startup for topaz, no changes...if it help I'll can take a photo of console
Click to expand...
Click to collapse
Can't detect build type... I had that yesterday, and forgot no_partitions in my startup. Perhaps same issue for you? Obviously this setup runs without a partitioned card, and if your card is partitioned you must tell the system that you want to ignore the partitions and just boot looped.
Yes, I have partitioned sd...can you post me right startup, please?
(or I have to add 'no_partitions' to my startup.txt?)
doma999 said:
Yes, I have partitioned sd...can you post me right startup, please?
(or I have to add 'no_partitions' to my startup.txt?)
Click to expand...
Click to collapse
Sigh.
Yes, you have to add "no_partitions" to your startup.txt, as below.
Code:
set ramsize 0x10000000
set ramaddr 0x10000000
set mtype 2293
set KERNEL zImage
set initrd initrd.gz
set initrd_offset 0x00a00000
set cmdline "lcd.density=240 msmvkeyb_toggle=off sensor=topaz pm.sleep_mode=1 no_partitions"
boot
Hi,
First of all thanks for your hard work and i'm so impressed by the way that XDAndroid changed my phone. But in this new version i remarqued that i have some missed applications in Android Market like "Tunis Radar" who is working in FRX07. There is a solution for this problem please ?
Thanks for respanding and sorry for my bad english
Poucet_OO7 said:
Hi,
First of all thanks for your hard work and i'm so impressed by the way that XDAndroid changed my phone. But in this new version i remarqued that i have some missed applications in Android Market like "Tunis Radar" who is working in FRX07. There is a solution for this problem please ?
Thanks for respanding and sorry for my bad english
Click to expand...
Click to collapse
Uhm.
From what I gather, there's apps that work in FRX07 that don't work here. Tunis Radar? Is that a GPS app..? Any other apps that don't work?
Logs please.
...Or are you saying they don't show up in the Market?
Hello,
Yes it's a GPS application and i can't see it in android market (it display that they are 15 results but i can see only Sygic (GPS App)).
What about to make this build in CWM?
Poucet_OO7 said:
Hello,
Yes it's a GPS application and i can't see it in android market (it display that they are 15 results but i can see only Sygic (GPS App)).
Click to expand...
Click to collapse
Perhaps it doesn't work for your device? I don't know, try to get an apk.
doma999 said:
What about to make this build in CWM?
Click to expand...
Click to collapse
Why? It runs off the SD card, full-blown recovery is ridiculous overkill.
wifi not working
wifi not working,topa100 device
edit1: ok fixed if i open it before booting haret
scarface5323 said:
wifi not working,topa100 device
edit1: ok fixed if i open it before booting haret
Click to expand...
Click to collapse
This bug has existed forever. Probably since wifi was enabled for you guys. C'mon.
hi, first of all thanks and happy new year
i was testing it and i can not run "my backup pro" in order to restore all my apps. i have tried versions 2.66 and 3.01 of this app.
anybody with success in this stuff? thanks a lot
maybe with titanium backup?
i know...my backup is from froyo frx07 version but i think it is possible if the app can run and not force closes itself at the begining
what about battery? any longer results in batt life? maybe not...
lmemperador said:
hi, first of all thanks and happy new year
i was testing it and i can not run "my backup pro" in order to restore all my apps. i have tried versions 2.66 and 3.01 of this app.
anybody with success in this stuff? thanks a lot
maybe with titanium backup?
i know...my backup is from froyo frx07 version but i think it is possible if the app can run and not force closes itself at the begining
what about battery? any longer results in batt life? maybe not...
Click to expand...
Click to collapse
Battery hasn't really changed.
Titanium Backup works great, I use it almost every day.
arrrghhh said:
Battery hasn't really changed.
Titanium Backup works great, I use it almost every day.
Click to expand...
Click to collapse
thanks a lot, i will try it
sorry if i post in wrong section, but i found no topic about GBX0B for HTC Raphael.
i use this GBX0B for my HTC Raphael 100, and the micro doesn't work.
how can i use it?
p/s: sorry for my bad english.
williamsnyder said:
sorry if i post in wrong section, but i found no topic about GBX0B for HTC Raphael.
i use this GBX0B for my HTC Raphael 100, and the micro doesn't work.
how can i use it?
p/s: sorry for my bad english.
Click to expand...
Click to collapse
What the hell is the micro?
I assume you mean the extUSB dongle?
Hello,
Today I tried Justin Case's Rooting method. Seen HERE
But like 1 other person on that thread. I Get the mkdir failed for /data/local/tmp/dalvik-cache, File exists error.
How can i fix that? It's obvious that dalvik-cache exists but what can I do next?
Didn´t you see that the 1 other person on that thread had 2 posts direct side by side?
In the second post he said he was on 4.0.4! So, maybe thats also your problem.
@jcase
Maybe you can please add a Info in your "TwerkMyMoto" OP if it is only for JB 4.1.2 ?
thx
That error just means the directory already exists, ie you already ran it once. No worries on that error.
I dont have the device or anything like it, so I dont have time to debug issues. I suggest updating to latest firmware, or taking a peak at teh exploit source code
https://github.com/CunningLogic/TwerkMyMoto
@KennyDB
i had a look at the exploit source code and there is a Info from jcase himself that it is designed for 4.1.2.
"TwerkMyMoto 1.0 for Razr I (x86) 4.1.2"
Maybe it could help to modify the rootme.sh that it doesn´t make the directory "/data/local/tmp/dalvik-cache" if that directory already exist?
If you are on ICS and want to root your phone use djbliss method, for JB use twerkmymoto.
Hello gentlemen,
I'm back, with a what I hope is a minor issue. I hope someone can help me.
I have the following head unit (Universal Model):
KLD Universal model S07 - RK3181 (quadcore)
800x480 resolution - KK 4.4.4_23072015
MCU version MTCB-KLD2-V2.67 (Jul 09 2015 19:15:51)
Kernal version 3.0.36+ [email protected] #396 (Wed Jul 22 17:40:16 CST 2015)
Build number RK3188-ENG4.4.4 23072015.09:09:11
CPU ARMv7 1.6Ghz (x4)
It is rooted via the factory settings method. But other than that it is pretty much still stock (I added a cooling fan). The only other apps I add where PowerAmp, PowerAmp Toast, Xposed Framework, XposedMTC, and Lucky Patcher (I believe this app fully unlocks the PowerAmp app). I have had no issue with it for the last 7 months.
However, the other day it took a long time to bootup. Now I have some google service errors: "the process com.google.process.gapps has stopped"
I have to keep on clicking "OK" in order for the error pop-ups to close. I have to repeat this several times until all the pop-ups finally stop. Other than that, everything else is working properly. Although I notices that Xposed and PowerAmp Toast do not start (no icons on the top notice bar).
I tried going to Settings/App Manager/Google Service Framework - and then I click Forces Stopped it, Disable, Clear Data, Clear Cache, Enable. Then I reboot, but I still get the same google service errors.
Can someone please help me fix this? Any help will be greatly appreciated.
Thanks,
Galo
PS - One other thing. This is related to the XDA website in general. How can I get rid of that stupid side panel (Analysis & Opinion / More XDA New). It keeps on automatically scolling and gets in the way of reading and typing. It is really annoying. Can someone tell me how to switch this off. Thanks again
Lucky Patcher has a "clear cache" option. Maybe try that? Should force all the Android apps to optimize at boot and maybe fix your issues.
Hello BullGawd,
I already tried that. I also tried going into Settings/App Manager and clearing the cache for Google Services Framework.
I even tried by pressing the small reset botton on the face of the head unit. I am trying to avoid doing a factory reset from the recovery screen.
Has anyone had this issue with this these head units? How did you get this error fixed.
Thanks,
ggee
Hi guys,
My unit is stock. But I think I am just going to flash a newer version of the factory firmware (kitkat 4.4.4). In the old threads there used to be two repositories. One was the huifei-fileserver, and the other was a Google Drive site. Now I only see the huifei-fileserver.
Anyways, I downloaded the latest KLD RK3188 800x480 firmware:
http://huifei.fs-fileserver.de/cont...D 4.4.4/800x480/KLD 800x480 20150820 Factory/
However, it looks like the firmware .img file is made up of two parts. Both are zip files and each one contains a .img file.
-Am I supposed to merge both of these files into one .img file? If so, how do I do this?
-Or am I supposed to put both of these .img files into the root of the sd card (then insert to the gps slot)?
I know how to flash and update the firmware. However, I have only ever seen this process done using one .img file - not two. Can someone please clarify what to do with these two files in order to flash them properly. I do not want to gamble and brick my unit.
Thanks,
ggee
is one an mcu.img file? If so, remote that and only flash update.img
Dave
TT_Vert said:
is one an mcu.img file? If so, remote that and only flash update.img
Click to expand...
Click to collapse
Hello,
The first zip file says Part1 and its 204MB in size. This zip contains one update.img (634MB when extracted). The second zip file says Part2 and its 91MB in size. This zip also contains one update.img (yet it is the same size when extracted - 634MB). This is confusing and should be something easy and straight forward.
I am not sure if both of these files need to be merged. If they are supposed to be merged, how would you do this (what app does this).
-OR-
I am not sure if both update.img files need to be copied to the root of the sd card. However, both files cannot have the same name within the same directory, otherwise one file will overwrite the other. One file name will need to be changed. But I believe once you change the name, the head unit will not recognize it as a firmware image anymore.
Can someone please clarify this.
Thanks,
ggee
ok you need to use winrar first to combine the two. Are you sure these weren't rar files NOT zip files?
Dave
TT_Vert said:
ok you need to use winrar first to combine the two. Are you sure these weren't rar files NOT zip files?
Dave
Click to expand...
Click to collapse
Hello,
Yes, these are winrar files and I also use the winrar software. Sorry, I tend to use the word "zip" when talking about compressed file formats in general. Both files I am speaking about are winrar (Part1 and Part2). And each has an update.img file. How do I combine the files? Is there a special function within winrar?
BTW - do you have any idea about my original problem (google services stopped working)? Since I have not gotten a definitive answer, I was thinking about either doing a factory resetting, or just updating the firmware and mcu. I decided to update and that is why I'm stuck on these two "winrar" files, and how to combine them.
Thanks,
ggee
if you search that is a very common problem. Resetting won't fix it. Open first rar and extract. It will then combine the two into one update.img file.
Dave
TT_Vert said:
if you search that is a very common problem. Resetting won't fix it. Open first rar and extract. It will then combine the two into one update.img file.
Click to expand...
Click to collapse
Hello Dave,
Thanks for pointing this out. I honestly have never had to merge two winrar files together before. I was definitely overthinking this process. I guess this happens when dealing with the more complex issues here, and not wanting to brick the unit. I really appreciate it.
As for my google services problem. I have done several searches on this topic. I do see lots of people asking how to fix it. But I do not see posts answering them back with a fix. The only other answer I was able to search out is on the Old Threat Q&A sticky (Problems and Solutions Found by Users):
http://forum.xda-developers.com/showthread.php?p=56791126#post56791126
This is a very vague answer and does not give much detail. I tried what they mentioned and it does not work for me. I think after the Old Threat was split, the answers are probably scattered around in partial chunks. If you have a the link to an answer/solution to this, I would be greatly appreciative. Otherwise, I am forced to have to update/flash the firmware on an issue that probably could have been easily solved. If it is a very common issue, maybe it should be its own sticky so that people can easily see it.
Thanks again.
ggee
There is no fix but myself and another person did try a bunch of different versions so search for it to find the most stable version.
gguevara said:
Hello Dave,
Thanks for pointing this out. I honestly have never had to merge two winrar files together before. I was definitely overthinking this process. I guess this happens when dealing with the more complex issues here, and not wanting to brick the unit. I really appreciate it.
As for my google services problem. I have done several searches on this topic. I do see lots of people asking how to fix it. But I do not see posts answering them back with a fix. The only other answer I was able to search out is on the Old Threat Q&A sticky (Problems and Solutions Found by Users):
http://forum.xda-developers.com/showthread.php?p=56791126#post56791126
This is a very vague answer and does not give much detail. I tried what they mentioned and it does not work for me. I think after the Old Threat was split, the answers are probably scattered around in partial chunks. If you have a the link to an answer/solution to this, I would be greatly appreciative. Otherwise, I am forced to have to update/flash the firmware on an issue that probably could have been easily solved. If it is a very common issue, maybe it should be its own sticky so that people can easily see it.
Thanks again.
ggee
Click to expand...
Click to collapse
Hi @gguevara,
I have the same problem on my unit (...gapps has stopped popups).
Did you find a solution ?
Thanks
Same here, recently my head unit started giving me this error message and also sygic seems to just freeze up... Haven't quite searched anything yet, but last night managed to root it so will go from there
Sent from my Nexus 6P using XDA-Developers mobile app
vinpee said:
Hi @gguevara,
I have the same problem on my unit (...gapps has stopped popups).
Did you find a solution ?
Thanks
Click to expand...
Click to collapse
sciux said:
Same here, recently my head unit started giving me this error message and also sygic seems to just freeze up... Haven't quite searched anything yet, but last night managed to root it so will go from there
Sent from my Nexus 6P using XDA-Developers mobile app
Click to expand...
Click to collapse
Hello guys,
Yes. I was able to correct the problem.
All I did was re-flash the stock firmware rom. You can either re-flash your current version (if you have the update.img file for your head unit model). Or you can find the post in the Android Auto forum that lists most of the stock firmware roms. Make sure you select and download the correct one for your head unit type and model. I simply went back to the seller and asked them to send me the latest official stock firmware rom.
If you have certain apps and setting that you want to keep, make sure you make a back up before re-flashing the rom. Otherwise you will have to reinstall the apps and setting. Since I am basically keeping my head unit in a stock status (except for normal root), I just skipped the back up step and re-flashed the rom.
Extract the .zip or .rar of the firmware rom image. Then copy it to an SD card and insert it into you head unit. Reboot the head unit into recovery mode. Make sure to clear caches while you are in the recover mode, before re-flashing the rom. Then follow the menus for flashing the rom.
Later,
ggee