[Q] ROM for AC Ryan VEOLO - Android Q&A, Help & Troubleshooting

Hi All,
Is there anyone busy with a custom ROM for the AC Ryan VEOLO?
A rom with Android 2.3 instead of would already be great. This would make it capable of running XBMC for android.
That could make it a great device!

Let's even hope we get Android 4.0.3 ICS. The mediaplayer division of Huawei made released a new player at the end of August based on the same Hi3716C CPU as the Veolo, the Himedia Q5. The latest firmware is available here : http://v.himedia-tech.cn/Q5/102/update.zip
Some ROM experts around who could help ?

A way to install the firmware you mention woud also be great!

Sorry, don't know how to flash, because some .img files have different sizes compared to the Veolo firmware, so I suppose the nand flash needs to be repartitioned. Also, there is no update_app.zip file, and there are more .img files in the update.zip than in the original firmware.
That's why I asked if some experts know how to do it. If so, I would be happy to try

jefke2 said:
Sorry, don't know how to flash, because some .img files have different sizes compared to the Veolo firmware, so I suppose the nand flash needs to be repartitioned. Also, there is no update_app.zip file, and there are more .img files in the update.zip than in the original firmware.
That's why I asked if some experts know how to do it. If so, I would be happy to try
Click to expand...
Click to collapse
Any news about this question?
There must be a people out there that could help us

Veolo
Hi ,
I was wondering is anybody on to this .
Is there anybody who is trying to fix a recovery and a rom for us ?
I would really appreciete this .
Or someone who can guide me in the right direction on how to do this on my own .
Thanks anyway .
Greetz Tim

Someone has managed to flash the Himedia Q5 ICS firmware on the Pearl Meteorit MMB 422 which is very similar to the Veolo : http://www.android-hilfe.de/pearl-meteorit-mmb-422-hdtv-forum/254851-toolbox-fuer-pearl-meteorit-mmb-422-hdtv-root-google-play-etc-12.html
I tried on the Veolo, but no luck Strange, because i can flash the Veolo with Meteorit MMB 422 firmware and back with no problems at all.
Hopefully someone can create a flashable package for the Veolo based on the Himedia Q5 firmware.
BTW, version 1.0.3 is available : http://v.himedia-tech.cn/Q5/103/update.zip
This firmware would be great because it has native DVD/BD ISO playback, and would also allow us to run XBMC ...
J.

Ac Ryan Veolo
That would be very great i really hope someone with some knowledge and experience can help us out .
I would be able to help with the development of the rom and i would to try compile it myself and test it on my own Veolo .
I just need some help in the right direction .
Someone can help me out please ?
Greetz Tim

Well, i have made a little recap of all godbox platform devices (of which the AC Ryan Veolo is also a clone) :
- AC Ryan Veolo, Android 2.2
- Pearl Meteorit MMB 422, Android 2.2 (info : http://www.pearl.de/a-PX1549-1600.shtml)
- Poppstar MS 40, Android 2.2 (info: http://www.poppstar.eu/poppstar-poppstar-ms40-1080p-android-media-adapter.html)
- Coolech Android Deluxe, Android 2.2 (info : http://en.coupoint.net/ but site seems to be down ATM)
- G-Mini Magicbox Atlas, Android 2.2 (info : http://www.g-mini.ru/products/27)
and then there's:
- Himedia Q5, Android 4.0.3 (info : http://www.himedia-tech.cn/product_show.php?id=37) => They have already published 2 ICS firmware versions, see links in posts above
- eGreat i10, Android 4.0.3 (no info on their website, but available from online shops)
We know the bootloader from the AC Ryan Veolo is not locked, because you can flash Meteorit and G-Mini firmware without any problem. Why can't the ICS firmware be flashed ? Maybe it has something to do with NAND partition sizes ?
My knowledge is really too limited to cook a ROM, but these devices are technically identical, so there's no reason it shouldn't work.
J.

Here's a link for the developers among us : http://blog.sina.com.cn/s/blog_602f87700100qfa1.html
Use Chrome 's built in translate function... It's about how to cook a ROM for the Hi3716C platform.
Good luck ... :good:
J.

http://acryan.com/sg/acr/support/ACR-VE91200/
Under the Other tab, it says Open Source code ? for VEOLO ?

veolo
guys, someone please help with custom Ics firmware for Veolo, there is no hope from the manufacturer...tx :angel:

Yet another update for the Himedia Q5 : http://v.himedia-tech.cn/Q5/104/update.zip
On the other hand, Poppstar has ICS firmware ready (originally released with Froyo), but it can't (yet) be flashed easily. Link: http://www.android-hilfe.de/4646864-post137.html
J.

And now it's russian company G-Mini that has ICS firmware ready for the Atlas (also identical to the Veolo) But as with Himedia and Poppstar firmware it can't be flashed without serial connection to the motherboard.

Any news about this ?

I have flashed the Poppstar MS-40 ICS firmware on the Veolo, using a CP2102 USB to TTL UART programmer. (you can get it here : http://www.android-hilfe.de/pearl-meteorit-mmb-422-hdtv-forum/366851-installationsanleitung-ics-update.html)
Everything was OK (smooth, remote control working great, etc.) I then wanted to try the Himedia firmware, so copied update.zip onto an SD card and started the update from the system settings menu. Everything went fine until the upgrade procedure stopped at the end. After waiting for 30 minutes, i pulled the power plug and tried to flash the Poppstar firmware again, but it failed. Apparently I now have bad NAND flash from 0x4a00000 up to 0x15000000 (the area where the system.img has to be written)
I tried this:
- modified the partition table (it's an XML file) and added the bad NAND flash area to the kernel partition and moved the system partition to 0x15000000. (other partitions modified as well)
- modified the bootargs.bin with these new partition locations and sizes, also modified kernel partition length.
I reflashed successfully but the Veolo does not boot, so does anyone know what i can try next ?
See XML partition table below, and modified bootargs.bin attached.
Code:
<?xml version="1.0" encoding="GB2312" ?>
<Partition_Info>
<Part Sel="1" PartitionName="fastboot" FlashType="Spi" FileSystem="None" Start="0" Length="448K" SelectFile="E:\Backup\acryan\acryan\fastboot-burn.bin" />
<Part Sel="1" PartitionName="bootargs" FlashType="Spi" FileSystem="None" Start="448K" Length="64K" SelectFile="E:\Backup\acryan\acryan\bootargs_mod.bin" />
<Part Sel="1" PartitionName="recovery" FlashType="Spi" FileSystem="None" Start="512k" Length="3520K" SelectFile="E:\Backup\acryan\acryan\recovery.img" />
<Part Sel="0" PartitionName="deviceinfo" FlashType="Spi" FileSystem="None" Start="4032K" Length="64K" SelectFile="" />
<Part Sel="1" PartitionName="baseparam" FlashType="Nand" FileSystem="None" Start="0" Length="6M" SelectFile="E:\Backup\acryan\acryan\base_hi3176c.img" />
<Part Sel="1" PartitionName="logo" FlashType="Nand" FileSystem="None" Start="6M" Length="8M" SelectFile="E:\Backup\acryan\acryan\logo.img" />
<Part Sel="0" PartitionName="fastplay" FlashType="Nand" FileSystem="None" Start="14M" Length="10M" SelectFile="" />
<Part Sel="0" PartitionName="cache" FlashType="Nand" FileSystem="None" Start="24M" Length="30M" SelectFile="" />
<Part Sel="0" PartitionName="misc" FlashType="Nand" FileSystem="None" Start="54M" Length="10M" SelectFile="" />
<Part Sel="1" PartitionName="kernel" FlashType="Nand" FileSystem="None" Start="64M" Length="272M" SelectFile="E:\Backup\acryan\acryan\kernel" />
<Part Sel="1" PartitionName="system" FlashType="Nand" FileSystem="Yaffs" Start="336M" Length="400M" SelectFile="E:\Backup\acryan\acryan\system.ics.yaffs2_8k24bits" />
<Part Sel="1" PartitionName="userdata" FlashType="Nand" FileSystem="Yaffs" Start="736M" Length="234M" SelectFile="E:\Backup\acryan\acryan\userdata.ics.yaffs2_8k24bits" />
<Part Sel="0" PartitionName="blackbox" FlashType="Nand" FileSystem="None" Start="970M" Length="4M" SelectFile="" />
<Part Sel="0" PartitionName="sdcard" FlashType="Nand" FileSystem="None" Start="974M" Length="3122M" SelectFile="" />
</Partition_Info>
Cheers
J.

I apparently did the same thing, I flashed the Himedia firmware but on a different clone of Veolo, the HD For All 900 (http://www.e-boda.ro/media-playere/media-player-mkv-full-hd-1080p-cu-sistem-de-operare-android-e-boda-hd-for-all-900.html).
I used a Nokia CA - 42 Cable and the Fastboot.exe (v 3.1).
Things did not went so well because I ended up with a bricked player since the uboot (aka akaboot) boot-loader 3.2.2 is not working with the HD For All 900's board.It gives me some error message and then it hangs, I cannot give any command through USB - SERIAL -UART (using putty).
The I managed also using the Fasboot.exe to put back the original fastboot 3.0 and it started again, I can give uboot commands but I ended up with wrong NAND partition layout so the kernel cannot start.
I will try to restore the old partition layout and I will come back to you because it seams you experience the same kind of problem with the partion layout.
---------- Post added at 01:55 PM ---------- Previous post was at 01:46 PM ----------
Hello
Can someone please re-upload the Poppstar MS-40 ICS firmware because the link on the German forum does not work anymore (The file was deleted).
Many Tanks

If you have a ttl card you can flash the popstar or atlas firmware even with a bricked player just choose serial instead of network in fastboot
---------- Post added at 03:17 PM ---------- Previous post was at 03:13 PM ----------
jefke2 said:
I have flashed the Poppstar MS-40 ICS firmware on the Veolo, using a CP2102 USB to TTL UART programmer. (you can get it here : http://www.android-hilfe.de/pearl-meteorit-mmb-422-hdtv-forum/366851-installationsanleitung-ics-update.html)
Everything was OK (smooth, remote control working great, etc.) I then wanted to try the Himedia firmware, so copied update.zip onto an SD card and started the update from the system settings menu. Everything went fine until the upgrade procedure stopped at the end. After waiting for 30 minutes, i pulled the power plug and tried to flash the Poppstar firmware again, but it failed. Apparently I now have bad NAND flash from 0x4a00000 up to 0x15000000 (the area where the system.img has to be written)
I tried this:
- modified the partition table (it's an XML file) and added the bad NAND flash area to the kernel partition and moved the system partition to 0x15000000. (other partitions modified as well)
- modified the bootargs.bin with these new partition locations and sizes, also modified kernel partition length.
I reflashed successfully but the Veolo does not boot, so does anyone know what i can try next ?
See XML partition table below, and modified bootargs.bin attached.
Code:
<?xml version="1.0" encoding="GB2312" ?>
<Partition_Info>
<Part Sel="1" PartitionName="fastboot" FlashType="Spi" FileSystem="None" Start="0" Length="448K" SelectFile="E:\Backup\acryan\acryan\fastboot-burn.bin" />
<Part Sel="1" PartitionName="bootargs" FlashType="Spi" FileSystem="None" Start="448K" Length="64K" SelectFile="E:\Backup\acryan\acryan\bootargs_mod.bin" />
<Part Sel="1" PartitionName="recovery" FlashType="Spi" FileSystem="None" Start="512k" Length="3520K" SelectFile="E:\Backup\acryan\acryan\recovery.img" />
<Part Sel="0" PartitionName="deviceinfo" FlashType="Spi" FileSystem="None" Start="4032K" Length="64K" SelectFile="" />
<Part Sel="1" PartitionName="baseparam" FlashType="Nand" FileSystem="None" Start="0" Length="6M" SelectFile="E:\Backup\acryan\acryan\base_hi3176c.img" />
<Part Sel="1" PartitionName="logo" FlashType="Nand" FileSystem="None" Start="6M" Length="8M" SelectFile="E:\Backup\acryan\acryan\logo.img" />
<Part Sel="0" PartitionName="fastplay" FlashType="Nand" FileSystem="None" Start="14M" Length="10M" SelectFile="" />
<Part Sel="0" PartitionName="cache" FlashType="Nand" FileSystem="None" Start="24M" Length="30M" SelectFile="" />
<Part Sel="0" PartitionName="misc" FlashType="Nand" FileSystem="None" Start="54M" Length="10M" SelectFile="" />
<Part Sel="1" PartitionName="kernel" FlashType="Nand" FileSystem="None" Start="64M" Length="272M" SelectFile="E:\Backup\acryan\acryan\kernel" />
<Part Sel="1" PartitionName="system" FlashType="Nand" FileSystem="Yaffs" Start="336M" Length="400M" SelectFile="E:\Backup\acryan\acryan\system.ics.yaffs2_8k24bits" />
<Part Sel="1" PartitionName="userdata" FlashType="Nand" FileSystem="Yaffs" Start="736M" Length="234M" SelectFile="E:\Backup\acryan\acryan\userdata.ics.yaffs2_8k24bits" />
<Part Sel="0" PartitionName="blackbox" FlashType="Nand" FileSystem="None" Start="970M" Length="4M" SelectFile="" />
<Part Sel="0" PartitionName="sdcard" FlashType="Nand" FileSystem="None" Start="974M" Length="3122M" SelectFile="" />
</Partition_Info>
Cheers
J.
Click to expand...
Click to collapse
Hai i am also busy to get the Himedia working on the veolo but do you succeeded or not ?
And how did you edit the bootargs.bin ?

kraakie256 said:
If you have a ttl card you can flash the popstar or atlas firmware even with a bricked player just choose serial instead of network in fastboot
---------- Post added at 03:17 PM ---------- Previous post was at 03:13 PM ----------
Hai i am also busy to get the Himedia working on the veolo but do you succeeded or not ?
And how did you edit the bootargs.bin ?
Click to expand...
Click to collapse
The flashing procedure seemed to go well at first, but did not succeed in the end. I read somewhere that there is a difference in how devices with 512 MB RAM (like the Veolo) and 1 GB RAM (like the Himedia Q5) so be careful At least, I now have a nice Himedia logo showing up at boot, but a bricked device nonetheless ...
I edited the bootargs.bin with Notepad++ in textmode, and used the hexeditor plugin to add (or remove) null bytes, the file has to be 64 KB exactly !
Cheers
J.

Try the Erase button in Fastboot 3.1.8
Hi,
I've an MMB-422 Mediaplayer. It's a copy of the Veolo (also based on Hi3716C). When I bought it 2 weeks ago the box was already upgraded to ICS 4.0.3. It was running nice and smooth. Then I did want to try the Update package for the HiMedia Q5, just as you did Jefke2.
I went with a broken box, it keeps on booting in Recovery. After I tried several things the only solution wich was working for me was the "Erase" button in the Fastboot 3.1 progam. I was a little bit scary because I thought that it would also erase the fastboot partition in the SPI memory. But with a Broken box I had tot do something, I deselected the fastbootpartiotion and hit the Erase button. Indeed......it erases ALL SELCTED PARTITIONS incl. the SPI partitions. But to my surprise the box still connected to fastboot 3.1 once I plugged the power out and directly again in the power socket (within a second).
I succesfully updated tot Meteorit ICS 4.0.3 firmware again and it's running very well!

Related

[Q] Overlapping Layout XML

Hey Everybody!! I searched a lot on this forum and really don't know if I post this in the right section or whatsoever, it's a bit unclear. But I just post it and wait for the respons
For the first time I'm developing an Android application and so far it's going really well except for one thing. I made a webview layout and I wanted to show ads in the app. So I added the AdMob ads and they're working really well. But there's one problem.
The AdMob covers a part of the WebView, so it's not shifting the WebView layout up but it's covering it. And that's annoying because you can't read a part of the webview's text. How can I fix it?
This is my main.xml file:
Code:
<?xml version="1.0" encoding="utf-8"?>
<RelativeLayout xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:ads="http://schemas.android.com/apk/lib/com.google.ads"
android:layout_width="fill_parent" android:id="@+id/rltvLayout01"
android:layout_height="fill_parent" android:background="@color/white">
<ScrollView android:id="@+id/ScrollView01"
android:layout_width="fill_parent"
android:layout_height="wrap_content">
<WebView android:id="@+id/webview"
android:layout_width="fill_parent"
android:layout_height="wrap_content"
android:fitsSystemWindows="true"
android:scrollbars="none" />
</ScrollView>
<LinearLayout android:id="@+id/ad_layout"
android:layout_width="fill_parent"
android:layout_height="wrap_content"
android:gravity="bottom"
android:layout_alignParentBottom="true">
<com.google.ads.AdView android:id="@+id/ad"
android:layout_width="fill_parent"
android:layout_height="wrap_content"
ads:adUnitId="helloworldcode"
ads:loadAdOnCreate="true"
ads:adSize="BANNER" />
</LinearLayout>
</RelativeLayout>
You need to tell your scrollview to align to the top of the linearlayout. Try Adding this to your ScrollView definition:
android:layout_above="@+id/ad_layout"
You may need to change some "wrap_content" to "fill_parent" but without an IDE, I can't tell for sure.
Gene Poole said:
You need to tell your scrollview to align to the top of the linearlayout. Try Adding this to your ScrollView definition:
android:layout_above="@+id/ad_layout"
You may need to change some "wrap_content" to "fill_parent" but without an IDE, I can't tell for sure.
Click to expand...
Click to collapse
Thank you for the answer, but unfortunately for some reason I get a force close when I add the layout_above...

[Q&A] Need help with Admob

Hi,
I have been a part of XDA developers for a long time. I dont post (coz I dont know as much as ou guys). But I visit almost everyday.
I decided to make an App for Android and I have very close to 0 knowledge in programming. I made the app and it works However, I have incorporated the Admob SDK and done exactly like all the tutorials say but the ads dont show up on the device. It shows perfectly on the emulator through...
My "main.xml"
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:ads="http://schemas.android.com/apk/lib/com.google.ads"
androidrientation="vertical"
android:layout_width="fill_parent"
android:layout_height="fill_parent">
<com.google.ads.AdView android:id="@+id/adView"
android:layout_width="wrap_content"
android:layout_height="wrap_content"
ads:adUnitId="<I have put my Publisher ID <-- I hope that is correct"
ads:adSize="BANNER"
ads:loadAdOnCreate="true"/>
my Main Activily has the following
AdView adv = (AdView)findViewById(R.id.adView);
AdRequest re = new AdRequest();
adv.loadAd(re);
My Manifest has the following
<activity android:name="com.google.ads.AdActivity"
android:configChanges="keyboard|keyboardHidden|orientation|screenLayout|uiMode|screenSize|smallestScreenSize"/>
<uses-sdk android:minSdkVersion="8" />
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE"/>
my Project Properties has this
target=android-15
I have added external JAR GoogleAdMobAdsSdk-6.1.0.jar into the LIbrary.
When i run it, i cant see the ad on my device but I can see it if I run it on the emumlator.
https://play.google.com/store/apps/...sMSwxLDEsImNvbS5vdXRnb2luZy5kZXRlY3RjYWxscyJd
That's my app. ( If someone helps me solve this, I will give my app ADD FREE to XDA Developers)
Thanks
If it works on the emulator you have done it correctly. I think it is a "lack of inventory" problem, so you only have to wait, usually this problem disappears when the number of installations increase.
Thank you so much. I can see in AdMob that the number of Requests is increasing so...

Anyway to recovery from Security Error?

I rooted the ATT E970 phone then I deleted Google play music and Google movie apps.
Now the phone shows "Security Error" and stop loading
I can only access "Download Mode" and hardware reset.
I cannot pull out KDZ link from http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=<yourimei> link by using IMEI
<?xml version="1.0" encoding="utf-8" ?>
- <response req_cmd="auth_model_check" status="OK">
- <auth_model_check>
<result>2</result>
<esn>xxxxxxxxxxx9778</esn>
<model>LGE970</model>
<suffix>AATTBK</suffix>
<msn>xxxxxxxxx1977</msn>
<esn_date>20121022</esn_date>
<sw_version />
<sw_url />
<sw_locale_url />
<sw_recommand_uri>GLOBAL/GLOBAL</sw_recommand_uri>
<app_version />
<app_url />
<cs_em_flag>N</cs_em_flag>
<cs_em_uri>N</cs_em_uri>
<chip_type />
<prod_type />
</auth_model_check>
</response>
I have TOT file for E970 but cannot find DLL file for ATT E970
Any suggestion?
piyopiyo81 said:
I rooted the ATT E970 phone then I deleted Google play music and Google movie apps.
Now the phone shows "Security Error" and stop loading
I can only access "Download Mode" and hardware reset.
I cannot pull out KDZ link from http://csmg.lgmobile.com:9002/csmg/b2c/client/auth_model_check2.jsp?esn=<yourimei> link by using IMEI
<?xml version="1.0" encoding="utf-8" ?>
- <response req_cmd="auth_model_check" status="OK">
- <auth_model_check>
<result>2</result>
<esn>xxxxxxxxxxx9778</esn>
<model>LGE970</model>
<suffix>AATTBK</suffix>
<msn>xxxxxxxxx1977</msn>
<esn_date>20121022</esn_date>
<sw_version />
<sw_url />
<sw_locale_url />
<sw_recommand_uri>GLOBAL/GLOBAL</sw_recommand_uri>
<app_version />
<app_url />
<cs_em_flag>N</cs_em_flag>
<cs_em_uri>N</cs_em_uri>
<chip_type />
<prod_type />
</auth_model_check>
</response>
I have TOT file for E970 but cannot find DLL file for ATT E970
Any suggestion?
Click to expand...
Click to collapse
Go to this irc channel and ask for help, you need to use the lgnpst to return to stock. Also if you unlock with freegee after rooting you will not get security error, good luck.
http://webchat.freenode.net/?channels=lg-optimus-g
adfurgerson said:
Go to this irc channel and ask for help, you need to use the lgnpst to return to stock. Also if you unlock with freegee after rooting you will not get security error, good luck.
http://webchat.freenode.net/?channels=lg-optimus-g
Click to expand...
Click to collapse
Thanks and fix problem

How to change and rebuild SystemUI.apk

Hi,
I've read some infos about that and tried different ways but it didn't work.
I try to add volume buttons to my tablets (exotic model: Rockchip M742E) navigation bar.
What I tried:
- pulled original SystemUI.apk
- decompiled it using apktool
- opened res/layout/system_bar.xml and found:
Code:
<LinearLayout android:orientation="horizontal" android:id="@id/navigationArea" android:clipChildren="false" android:clipToPadding="false" android:layout_width="wrap_content" android:layout_height="fill_parent" android:layout_alignParentLeft="true">
<com.android.systemui.statusbar.policy.KeyButtonView android:id="@id/back" android:layout_width="@dimen/navigation_key_width" android:layout_height="fill_parent" android:src="@drawable/ic_sysbar_back" android:contentDescription="@string/accessibility_back" systemui:keyCode="4" systemui:glowBackground="@drawable/ic_sysbar_highlight" />
<com.android.systemui.statusbar.policy.KeyButtonView android:id="@id/home" android:layout_width="@dimen/navigation_key_width" android:layout_height="fill_parent" android:src="@drawable/ic_sysbar_home" android:contentDescription="@string/accessibility_home" systemui:keyCode="3" systemui:glowBackground="@drawable/ic_sysbar_highlight" />
<com.android.systemui.statusbar.policy.KeyButtonView android:id="@id/recent_apps" android:layout_width="@dimen/navigation_key_width" android:layout_height="fill_parent" android:src="@drawable/ic_sysbar_recent" android:contentDescription="@string/accessibility_recent" systemui:glowBackground="@drawable/ic_sysbar_highlight" />
<com.android.systemui.statusbar.policy.KeyButtonView android:layout_gravity="center_vertical" android:id="@id/screenshot" android:layout_width="@dimen/navigation_key_width" android:layout_height="wrap_content" android:src="@drawable/capture" android:contentDescription="@string/accessibility_recent" systemui:glowBackground="@drawable/ic_sysbar_highlight" />
<com.android.systemui.statusbar.policy.KeyButtonView android:id="@id/menu" android:visibility="invisible" android:layout_width="@dimen/navigation_menu_key_width" android:layout_height="fill_parent" android:src="@drawable/ic_sysbar_menu" android:contentDescription="@string/accessibility_menu" systemui:keyCode="82" systemui:glowBackground="@drawable/ic_sysbar_highlight" />
<com.android.systemui.statusbar.policy.KeyButtonView android:id="@id/sub" android:background="@drawable/sub_normal" android:visibility="gone" android:layout_width="@dimen/navigation_menu_key_width" android:layout_height="fill_parent" systemui:keyCode="25" systemui:glowBackground="@drawable/ic_sysbar_highlight" />
<com.android.systemui.statusbar.policy.KeyButtonView android:id="@id/add" android:background="@drawable/add_normal" android:visibility="gone" android:layout_width="@dimen/navigation_menu_key_width" android:layout_height="fill_parent" systemui:keyCode="24" systemui:glowBackground="@drawable/ic_sysbar_highlight" />
</LinearLayout>
OK, there already are hidden volume buttons... great (i thought).
- I removed android:visibility="gone"
- recompiled SystemUI.apk with apktool
- pushed SystemUI.apk to the device
- rebooted... no navbar and other UI elements
I also tried this tutorial but had no luck
Does someone know what I am doing wrong?
I added the original apk to this post.
ponchofiesta said:
- recompiled SystemUI.apk with apktool
- pushed SystemUI.apk to the device
- rebooted... no navbar and other UI elements
Click to expand...
Click to collapse
Did you sign it correctly?
XperienceD said:
Did you sign it correctly?
Click to expand...
Click to collapse
I didn't sign anything. Never read about it. How do I do it?
ponchofiesta said:
I didn't sign anything. Never read about it. How do I do it?
Click to expand...
Click to collapse
Click the image in my sig and learn how.
XperienceD said:
Click the image in my sig and learn how.
Click to expand...
Click to collapse
Thanks. I tried both methods under Signing but both didn't work. After reboot SystemUI FCs
ponchofiesta said:
Thanks. I tried both methods under Signing but both didn't work. After reboot SystemUI FCs
Click to expand...
Click to collapse
You'll just need to experiment with your code then if the guide you followed isn't for your device, I rebooted and flashed my framework about 8 times last week trying to get a mod right, it's what you have to do sometimes. Push a stock SystemUI to your Phone for now and start from scratch.
I used now this simple guide but still the same. SystemUI crashes.
I will now test a unmoddified APK... if it also crashes, the problem is in the procedure itself.
I also tried APK-Multi-Tool now but it still crashes...
logcat shows much of this:
Code:
W/PackageManager( 275): Not granting permission android.permission.INJECT_EVENTS to package com.android.systemui (protectionLevel=2 flags=0x83e0d)
I believe it's still a signature problem or something. But I don't know how to fix it.

XT912 brick

Good day everyone! I would like to ask some help..
I'm actually noob in motorolla droid and this is my first motorolla phone ever. lol
Yesterday my brother gave me this XT912 since he got a new phone.
One of his colleagues rooted and changed the ROM to ECLIPSE 1.5.1 and it's running Android ICS 4.0.4 firmware.
When he gave the phone to me, I couldn't install some applications more specifically google hangouts coz it gives me an error:
E: signature verification failed
I downloaded the ff. firmwares from this site http://sbf.droid-developers.org/phone.php?device=9
Android 4.1.2 Blur_Version.98.72.165.XT912.Verizon.en.US
Android 4.1.2 Blur_Version.98.72.16.XT912.Verizon.en.US
Android 4.0.4 Blur_Version.6.16.211.XT912.Verizon.en.US
flashed them using the custom recovery option from the device (hold vol - & vol + keys while android logo appears) but eventually it gave me an error:
signature verification failed installation aborted
After series of google search I found this post by matt : http://www.droidrzr.com/index.php/t...xt912-jellybean-windows-mac-linux-all-in-one/
But it made my situation worst
Downloaded the latest version, DroidRAZRUtility1.82 Jellybean.
Installed the drivers for 32bit since I'm running W7 32bit OS.
Ran the WindowsUtility.bat and chose option 1 to completely wipe and install JB.
After running the utility I cannot boot up to recovery and normal boot-up anymore. In other words, it bricked my XT912.
It gave me this error:
When in AP Fastboot Mode:
AP Fastboot Flash Mode (S) (Flash Failure)
0A.74
eMMC Info: Size 16G
To return to normal mode - first press power key to power down
Device is LOCKED. Status Code:0
Battery OK
OK to Program
Connect USB
Data Cable
---------------------------
When in Normal Bootup and Recovery:
Invalid Flash Mode (S) (Boot Failure)
0A.74
eMMC Info: Size 16G
To return to normal mode - first press power key to power down
Device is LOCKED. Status Code:0
Invalid CG OTV (CG: system): Invalid SP Data
Invalid CD Version (CG: system)
Invalid CG OTV (CG: system)
As another try, I used Motorola RSD Lite 6.1.5 + MTK Patch and tried using the fastboot files (firmwares) that I downloaded earlier:
Android 4.1.2 Blur_Version.98.72.165.XT912.Verizon.en.US
Android 4.1.2 Blur_Version.98.72.16.XT912.Verizon.en.US
Android 4.0.4 Blur_Version.6.16.211.XT912.Verizon.en.US
But it gave me this error:
Failed flashing process. 6/16 flash motoboot "motoboot.img" -> Phone returned FAIL.
I really don't know how to fix this.. I really need your help guys...
Thanks,
Josh
Hi Josh,
Sorry to hear that....first of all, can you access fastboot mode? or you cant do absolutly anithing with the droid?
joshua3001 said:
Hi Josh,
Sorry to hear that....first of all, can you access fastboot mode? or you cant do absolutly anithing with the droid?
Click to expand...
Click to collapse
Hi joshua3001,
Yes, I could still boot in to fastboot mode.
joswa said:
When in Normal Bootup and Recovery:
Invalid Flash Mode (S) (Boot Failure)
0A.74
eMMC Info: Size 16G
To return to normal mode - first press power key to power down
Device is LOCKED. Status Code:0
Invalid CG OTV (CG: system): Invalid SP Data
Invalid CD Version (CG: system)
Invalid CG OTV (CG: system)
As another try, I used Motorola RSD Lite 6.1.5 + MTK Patch and tried using the fastboot files (firmwares) that I downloaded earlier:
Android 4.1.2 Blur_Version.98.72.165.XT912.Verizon.en.US
Android 4.1.2 Blur_Version.98.72.16.XT912.Verizon.en.US
Android 4.0.4 Blur_Version.6.16.211.XT912.Verizon.en.US
But it gave me this error:
Failed flashing process. 6/16 flash motoboot "motoboot.img" -> Phone returned FAIL.
I really don't know how to fix this.. I really need your help guys...
Thanks,
Josh
Click to expand...
Click to collapse
Are you trying to flash all three of these at the same time?
You won't be able to flash the 4.0.4 firmware, you are obviously already on the JB kernel(4.1.2), so you won't be able to go back to ICS(4.0.4)
That is what the screenshot you provided is telling you. The firmware it is failing on is the 4.0.4
You need to choose ONE of the 4.1.2 firmwares and flash it via RSD lite. Make sure you have plenty of battery when you do it.
Draxin is right dude, you cant flash all of them, i wll recomend you to flash JUST the .165 ...let me now (Y)
have the same problem
Draxin said:
Are you trying to flash all three of these at the same time?
You won't be able to flash the 4.0.4 firmware, you are obviously already on the JB kernel(4.1.2), so you won't be able to go back to ICS(4.0.4)
That is what the screenshot you provided is telling you. The firmware it is failing on is the 4.0.4
You need to choose ONE of the 4.1.2 firmwares and flash it via RSD lite. Make sure you have plenty of battery when you do it.
Click to expand...
Click to collapse
Hi Draxin,
I am having the same problem with my XT912 as well.
I have tried both the 4.1.2 options available at http://sbf.droid-developers.org/phone.php?device=9 and i am getting different errors with both of them.
For one i am getting flashcdt.bin 'cdt.bin_signed' > Phone returned Fail and for the other one i am getting Failed flashing process: 6/16 flash motoboot 'motoboot.img'' Phone returned Fail.
Can you please help?
I have been trying different things now and nothing is really working with my phone
need help please
joshua3001 said:
Draxin is right dude, you cant flash all of them, i wll recomend you to flash JUST the .165 ...let me now (Y)
Click to expand...
Click to collapse
Hi ,
I am having the same problem with my XT912 as well.
I have tried both the 4.1.2 options available at http://sbf.droid-developers.org/phone.php?device=9 and i am getting different errors with both of them.
For one i am getting flashcdt.bin 'cdt.bin_signed' > Phone returned Fail and for the other one i am getting Failed flashing process: 6/16 flash motoboot 'motoboot.img'' Phone returned Fail.
Can you please help?
I have been trying different things now and nothing is really working with my phone
nishanchi said:
Hi Draxin,
I am having the same problem with my XT912 as well.
I have tried both the 4.1.2 options available at http://sbf.droid-developers.org/phone.php?device=9 and i am getting different errors with both of them.
For one i am getting flashcdt.bin 'cdt.bin_signed' > Phone returned Fail and for the other one i am getting Failed flashing process: 6/16 flash motoboot 'motoboot.img'' Phone returned Fail.
Can you please help?
I have been trying different things now and nothing is really working with my phone
Click to expand...
Click to collapse
Hello,
Well regardless I would stick with the .165. Did you make sure debugging was enabled before trying to flash with RSD Lite? Did you make sure your phone was connected as a mass storage device?
Another option is Matt's Utility Make sure to follow his directions and thank him.
Same issue plz help me...
joswa said:
Good day everyone! I would like to ask some help..
I'm actually noob in motorolla droid and this is my first motorolla phone ever. lol
Yesterday my brother gave me this XT912 since he got a new phone.
One of his colleagues rooted and changed the ROM to ECLIPSE 1.5.1 and it's running Android ICS 4.0.4 firmware.
When he gave the phone to me, I couldn't install some applications more specifically google hangouts coz it gives me an error:
E: signature verification failed
I downloaded the ff. firmwares from this site http://sbf.droid-developers.org/phone.php?device=9
Android 4.1.2 Blur_Version.98.72.165.XT912.Verizon.en.US
Android 4.1.2 Blur_Version.98.72.16.XT912.Verizon.en.US
Android 4.0.4 Blur_Version.6.16.211.XT912.Verizon.en.US
flashed them using the custom recovery option from the device (hold vol - & vol + keys while android logo appears) but eventually it gave me an error:
signature verification failed installation aborted
After series of google search I found this post by matt : http://www.droidrzr.com/index.php/t...xt912-jellybean-windows-mac-linux-all-in-one/
But it made my situation worst
Downloaded the latest version, DroidRAZRUtility1.82 Jellybean.
Installed the drivers for 32bit since I'm running W7 32bit OS.
Ran the WindowsUtility.bat and chose option 1 to completely wipe and install JB.
After running the utility I cannot boot up to recovery and normal boot-up anymore. In other words, it bricked my XT912.
It gave me this error:
When in AP Fastboot Mode:
AP Fastboot Flash Mode (S) (Flash Failure)
0A.74
eMMC Info: Size 16G
To return to normal mode - first press power key to power down
Device is LOCKED. Status Code:0
Battery OK
OK to Program
Connect USB
Data Cable
---------------------------
When in Normal Bootup and Recovery:
Invalid Flash Mode (S) (Boot Failure)
0A.74
eMMC Info: Size 16G
To return to normal mode - first press power key to power down
Device is LOCKED. Status Code:0
Invalid CG OTV (CG: system): Invalid SP Data
Invalid CD Version (CG: system)
Invalid CG OTV (CG: system)
As another try, I used Motorola RSD Lite 6.1.5 + MTK Patch and tried using the fastboot files (firmwares) that I downloaded earlier:
Android 4.1.2 Blur_Version.98.72.165.XT912.Verizon.en.US
Android 4.1.2 Blur_Version.98.72.16.XT912.Verizon.en.US
Android 4.0.4 Blur_Version.6.16.211.XT912.Verizon.en.US
But it gave me this error:
Failed flashing process. 6/16 flash motoboot "motoboot.img" -> Phone returned FAIL.
I really don't know how to fix this.. I really need your help guys...
Thanks,
Josh
Click to expand...
Click to collapse
I have same issue in RSD and it always fails in motoboot.img
please give me solution
 @xda -developers @Razr MAXX
NabeelSaleem said:
I have same issue in RSD and it always fails in motoboot.img
please give me solution
@xda -developers @Razr MAXX
Click to expand...
Click to collapse
Windows version?
Rsd lite version?
Firmware version?
Bootloader version?
Sent from my XT894 using Tapatalk
sd_shadow said:
Windows version?
Rsd lite version?
Firmware version?
Bootloader version?
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
Thanks for reply
windows 8.1 pro
RSD 6.1.5
versions is tried:
VRZ_XT912_9.8.2O-72_VZW-16-5_1FF.xml
VRZ_XT912_6.7.2-180_DHD-16_M4-31_1FF.xml
and what is bootloader version? where can i find this?
NabeelSaleem said:
Thanks for reply
windows 8.1 pro
RSD 6.1.5
versions is tried:
VRZ_XT912_9.8.2O-72_VZW-16-5_1FF.xml
VRZ_XT912_6.7.2-180_DHD-16_M4-31_1FF.xml
and what is bootloader version? where can i find this?
Click to expand...
Click to collapse
AP Fastboot screen has bootloader version.
Windows 8 doesn't work well with rsd lite
Sent from my XT894 using Tapatalk
sd_shadow said:
AP Fastboot screen has bootloader version.
Windows 8 doesn't work well with rsd lite
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
It's written
AP Fastboot Flash Mode (S)
0A.77
eMMC Info: size 16g
should i use windows 7?
and what about xml versions? are they ok
NabeelSaleem said:
It's written
AP Fastboot Flash Mode (S)
0A.77
eMMC Info: size 16g
should i use windows 7?
and what about xml versions? are they ok
Click to expand...
Click to collapse
Window 7 is a better option.
verifiy Moto driver are installed.
try RSDLite 6.2.4
0A.77 means only Jellybean firmware can be used.
This is latest
4.1.2 Verizon US 9.8.2O-72_VZW-16-5
614 MB (644,076,403 bytes)
Md5: 410F338706C1AD599E839DDE4FD60A23
cdma_spyder_9.8.2O-72_VZW-16-5_cfc.xml
Verify md5 checksum for firmware
also the DROID RAZR Utility XT912 Jellybean UPDATED is a good option
sd_shadow said:
Window 7 is a better option.
verifiy Moto driver are installed.
try RSDLite 6.2.4
0A.77 means only Jellybean firmware can be used.
This is latest
4.1.2 Verizon US 9.8.2O-72_VZW-16-5
614 MB (644,076,403 bytes)
Md5: 410F338706C1AD599E839DDE4FD60A23
cdma_spyder_9.8.2O-72_VZW-16-5_cfc.xml
Verify md5 checksum for firmware
also the DROID RAZR Utility XT912 Jellybean UPDATED is a good option
Click to expand...
Click to collapse
Can you give me link for this firmware or this one correct > http://motofirmware.center/files/file/44-vrz_xt912_982o-72_vzw-16-5_cfcxmlzip/
size is 614.2MB
and what is Md5 and cdma lines you wrote? how can i check them?
and really thanks for your help... please guide me these things too ...
NabeelSaleem said:
Can you give me link for this firmware or this one correct > http://motofirmware.center/files/file/44-vrz_xt912_982o-72_vzw-16-5_cfcxmlzip/
size is 614.2MB
and what is Md5 and cdma lines you wrote? how can i check them?
and really thanks for your help... please guide me these things too ...
Click to expand...
Click to collapse
See Moto Drivers, RSD Lite, and other Unbricking Tools
http://forum.xda-developers.com/general/rooting-roms/motorola-usb-drivers-rsd-lite-firmware-t3042687
Sent from my XT894 using Tapatalk
sd_shadow said:
See Moto Drivers, RSD Lite, and other Unbricking Tools
http://forum.xda-developers.com/general/rooting-roms/motorola-usb-drivers-rsd-lite-firmware-t3042687
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
I know this and i downloaded RSD lite 6.2.4
Installed moto drivers
also checked razr utility tool
I downloaded firmware as you said but in my laptop its also failed to flash with this firmware > http://motofirmware.center/files/file/44-vrz_xt912_982o-72_vzw-16-5_cfcxmlzip/
and here is XML code
Code:
<?xml version="1.0"?>
<flashing>
<header>
<phone_model model="SPYDER_CFC" />
<software_version version="9.8.2O-72_VZW-16-5" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="flash" partition="cdt.bin" filename="cdt.bin_signed" MD5="D9F76350C7A9694FEA32D84AF1C4AA39" />
<step operation="reboot-bootloader" />
<step operation="flash" partition="emstorage" filename="emstorage.img" MD5="081640654B9F45CD31C3903180A72BD1" />
<step operation="reboot-bootloader" />
<step operation="flash" partition="mbm" filename="allow-mbmloader-flashing-mbm.bin" MD5="55D703D1D8D8631F31BE89A6069AD68E" />
<step operation="reboot-bootloader" />
<step operation="flash" partition="mbmloader" filename="mbmloader.bin" MD5="42F7110DE49D6D28EA0540F1C02F9F1B" />
<step operation="flash" partition="mbm" filename="mbm.bin" MD5="F541F64F56739D65C19557E33F8AEF3C" />
<step operation="oem" var="fb_mode_set" />
<step operation="reboot-bootloader" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="D25F83E68E3BD76AE7F9405581E49B41" />
<step operation="reboot-bootloader" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="erase" partition="userdata" />
<step operation="flash" partition="logo.bin" filename="logo.bin" MD5="CD111CC7B675E62A7D85A50632FB88E8" />
<step operation="flash" partition="devtree" filename="device_tree.bin" MD5="04E2F24447783A0FF32E86E0DCA1D0C0" />
<step operation="flash" partition="system" filename="system.img" MD5="923FC8E9A3848744EACC8E98BE43DABE" />
<step operation="flash" partition="boot" filename="boot.img" MD5="D89B288A78E43CDAAFA55B6545A2FAEA" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="E8CA4889CF1DC7236526F628D2FCF948" />
<step operation="flash" partition="cdrom" filename="cdrom" MD5="FD1D40C2B40F0222EB8EF98AEB3AA87C" />
<step operation="flash" partition="preinstall" filename="preinstall.img" MD5="619C6B45BBB62D13FD272A22DD19D63C" />
<step operation="flash" partition="radio" filename="radio.img" MD5="596BA902DB1F52CD97DC0466B2C88E24" />
<step operation="oem" var="fb_mode_clear" />
</steps>
</flashing>
flash fails on cdt.bin ... please tell me what to do @sd_shadow
NabeelSaleem said:
I know this and i downloaded RSD lite 6.2.4
Installed moto drivers
also checked razr utility tool
I downloaded firmware as you said but in my laptop its also failed to flash with this firmware > http://motofirmware.center/files/file/44-vrz_xt912_982o-72_vzw-16-5_cfcxmlzip/
and here is XML code
Code:
<?xml version="1.0"?>
<flashing>
<header>
<phone_model model="SPYDER_CFC" />
<software_version version="9.8.2O-72_VZW-16-5" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="flash" partition="cdt.bin" filename="cdt.bin_signed" MD5="D9F76350C7A9694FEA32D84AF1C4AA39" />
<step operation="reboot-bootloader" />
<step operation="flash" partition="emstorage" filename="emstorage.img" MD5="081640654B9F45CD31C3903180A72BD1" />
<step operation="reboot-bootloader" />
<step operation="flash" partition="mbm" filename="allow-mbmloader-flashing-mbm.bin" MD5="55D703D1D8D8631F31BE89A6069AD68E" />
<step operation="reboot-bootloader" />
<step operation="flash" partition="mbmloader" filename="mbmloader.bin" MD5="42F7110DE49D6D28EA0540F1C02F9F1B" />
<step operation="flash" partition="mbm" filename="mbm.bin" MD5="F541F64F56739D65C19557E33F8AEF3C" />
<step operation="oem" var="fb_mode_set" />
<step operation="reboot-bootloader" />
<step operation="flash" partition="motoboot" filename="motoboot.img" MD5="D25F83E68E3BD76AE7F9405581E49B41" />
<step operation="reboot-bootloader" />
<step operation="erase" partition="cache" />
<step operation="erase" partition="userdata" />
<step operation="erase" partition="userdata" />
<step operation="flash" partition="logo.bin" filename="logo.bin" MD5="CD111CC7B675E62A7D85A50632FB88E8" />
<step operation="flash" partition="devtree" filename="device_tree.bin" MD5="04E2F24447783A0FF32E86E0DCA1D0C0" />
<step operation="flash" partition="system" filename="system.img" MD5="923FC8E9A3848744EACC8E98BE43DABE" />
<step operation="flash" partition="boot" filename="boot.img" MD5="D89B288A78E43CDAAFA55B6545A2FAEA" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="E8CA4889CF1DC7236526F628D2FCF948" />
<step operation="flash" partition="cdrom" filename="cdrom" MD5="FD1D40C2B40F0222EB8EF98AEB3AA87C" />
<step operation="flash" partition="preinstall" filename="preinstall.img" MD5="619C6B45BBB62D13FD272A22DD19D63C" />
<step operation="flash" partition="radio" filename="radio.img" MD5="596BA902DB1F52CD97DC0466B2C88E24" />
<step operation="oem" var="fb_mode_clear" />
</steps>
</flashing>
flash fails on cdt.bin ... please tell me what to do @sd_shadow
Click to expand...
Click to collapse
Does your device have Verizon on front and back?
Sent from my XT894 using Tapatalk
---------- Post added at 07:36 AM ---------- Previous post was at 07:33 AM ----------
How to use md5
http://forum.xda-developers.com/showthread.php?t=
Sent from my XT894 using Tapatalk
sd_shadow said:
Does your device have Verizon on front and back?
Sent from my XT894 using Tapatalk
---------- Post added at 07:36 AM ---------- Previous post was at 07:33 AM ----------
How to use md5
http://forum.xda-developers.com/showthread.php?t=
Sent from my XT894 using Tapatalk
Click to expand...
Click to collapse
Yes written on both side.
4g LTE verizon
NabeelSaleem said:
Yes written on both side.
4g LTE verizon
Click to expand...
Click to collapse
What is complete text on AP Fastboot Flash Mode screen?

Categories

Resources