Database Info

[HOW-TO] How To Make a Custom Bootscreen

This is a tutorial on how to make a custom bootscreen for HTC ROMS ONLY. This will NOT work on AOSP roms. First, get the images you want to make your bootscreen out of, minimum requirement is two. Next, get the bootsound you want. Now, name the image you want to appear first "boot1.gif". Name the second image you want to appear "boot2.gif". Repeat this process for as many images you have. Now, rename the sound boot.mp3. Push them all to /system/media/bootscreen and reboot. There you go, your own custom bootscreen.

Now I'm new to this but do you ish each boot image it the file that you put them in?
Thanks for the write up!

I tried to do what you said, but it tells me that it cant copy because it's a read only file system, should I be trying this in some other mode (ie: fastboot or recovery) instead of just having the phone on as normal and connected to the computer?
PS: I'm running Fresh 1.1 with gbhil's kernel

wow, worst howto ever... you left so much stuff out. remounting, properties of the files, the fact that they actually need to be gifs, the size, the color depth, the mode and finally there is another file called boot_animation.xml...

djsplitimage said:
I tried to do what you said, but it tells me that it cant copy because it's a read only file system, should I be trying this in some other mode (ie: fastboot or recovery) instead of just having the phone on as normal and connected to the computer?
PS: I'm running Fresh 1.1 with gbhil's kernel
Click to expand...
Click to collapse
You need to do adb remount to get rid of the read-only filesystem warning.

kendong2 said:
wow, worst howto ever... you left so much stuff out. remounting, properties of the files, the fact that they actually need to be gifs, the size, the color depth, the mode and finally there is another file called boot_animation.xml...
Click to expand...
Click to collapse
Can you provide all the needed information?

This is a howto to keep it simple. For my custom Souffle boot, I had a lot of gifs and had to edit the XML, but this is a basic tutorial.

I'll post a more extensive tutorial up later, a bit lazy right now; since I'm working on actually making a boot screen. Anyways, here's a preview.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I cannot make this work using the method in the first post. I have tried placing the files in a custom rom, pushing through adb, and replacing files in a zip, resigning and flashing. Worst case: nothing happened at all. Occaisionally, the image would be there, but not in the right place and all staticy. The closest I've come was replacing the boot1.gif in an update.zip with my own boot1.gif. This had the image in the right place, but there was no animation and it was completely staticy, like a bad tv signal ota. And I've not had ANY luck replacing the boot.mp3 file. Not getting any sound ever. Any ideas?

tejasrichard said:
I cannot make this work using the method in the first post. I have tried placing the files in a custom rom, pushing through adb, and replacing files in a zip, resigning and flashing. Worst case: nothing happened at all. Occaisionally, the image would be there, but not in the right place and all staticy. The closest I've come was replacing the boot1.gif in an update.zip with my own boot1.gif. This had the image in the right place, but there was no animation and it was completely staticy, like a bad tv signal ota. And I've not had ANY luck replacing the boot.mp3 file. Not getting any sound ever. Any ideas?
Click to expand...
Click to collapse
Email me your files and I'll make an update.zip for you. kevinstech AT gmail DOT com

Awesome, man! Thanks! I'll shoot it to you later tonight.

Figured it out, lol! After doing some more reading (and getting my hands on a gif editor), I figured out the problem:
my animation xml had the volume set to 0, and the gif had a transparent background. It still would load properly if I pushed it, but after hacking an update.zip I had saved, it works fine! I need to chop the mp3 down some, but other than that, it looks fantastic! If it wasn't completely full of copywrited material, i would post it up.

tejasrichard said:
Figured it out, lol! After doing some more reading (and getting my hands on a gif editor), I figured out the problem:
my animation xml had the volume set to 0, and the gif had a transparent background. It still would load properly if I pushed it, but after hacking an update.zip I had saved, it works fine! I need to chop the mp3 down some, but other than that, it looks fantastic! If it wasn't completely full of copywrited material, i would post it up.
Click to expand...
Click to collapse
Mind posting or sending it to me so I could take a look. I'm trying to create a boot screen myself and I have the .gif made and what not, but when I flash it -- the boot screen I made gets really big and I see green lines and everything. So the boot screen works, but not the right way.

I certainly don't mind sending it to you, but I'm not sure how much help it will be. I literally just removed the files from an update.zip that I downloaded from here (the hero/horizontal nexus hybrid with sound) and replaced the files with my own files named the same thing. It does work, but I feel like a big ol' cheater, lol!

tejasrichard said:
I certainly don't mind sending it to you, but I'm not sure how much help it will be. I literally just removed the files from an update.zip that I downloaded from here (the hero/horizontal nexus hybrid with sound) and replaced the files with my own files named the same thing. It does work, but I feel like a big ol' cheater, lol!
Click to expand...
Click to collapse
Work smarter -- not harder.

sound
Is there a way to set the audio so that it begins when the second boot.gif starts? Here is the xml file I've been using:
<?xml version="1.0" encoding="utf-8" ?>
- <!--
* Copyright (C) 2008 HTC Inc.
*
-->
- <!-- For new bootup animation
<BootConfiguration>
<BootAnimation
image="/system/media/bootscreen/boot.gif"
audio="/system/media/bootscreen/boot.mp3"
image2="/system/media/bootscreen/boot2.gif" (optional)
image3="/system/media/bootscreen/boot3.gif" (optional)
screenX="100" (optional)
screenY="130" (optional)
image_bg = "/system/media/bootscreen/boot_bg.gif" (optional)
useAudio="0" // 1: true ; 0:false (optional)
/>
</BootConfiguration>
-->
- <!-- For cropped version
-->
- <BootConfiguration>
<BootAnimation image="/system/media/bootscreen/boot1.gif" image2="/system/media/bootscreen/boot2.gif" loopimage="/system/media/bootscreen/boot2.gif" image_bg="/system/media/bootscreen/boot_bg.gif" audio="/system/media/bootscreen/boot.mp3" screenX="0" screenY="90" useAudio="1" />
</BootConfiguration>
- <!-- For full screen version
-->
- <!-- BootConfiguration>
<BootAnimation
image="/system/media/bootscreen/boot1.gif"
image2="/system/media/bootscreen/boot2.gif"
loopimage="/system/media/bootscreen/boot2.gif"
audio="/system/media/bootscreen/boot.mp3"
useAudio="0"
/>
</BootConfiguration
-->
I believe the part in bold is the part working on our phone, correct?
edit: just realised something. This isn't actually controlling anything, is it? If I am right, all this does is point the loader to the correct files, right? So, any ideas what I would need to edit and where I would find it?

tejasrichard said:
Is there a way to set the audio so that it begins when the second boot.gif starts? Here is the xml file I've been using:
- <!-- For cropped version
-->
- <BootConfiguration>
<BootAnimation image="/system/media/bootscreen/boot1.gif" image2="/system/media/bootscreen/boot2.gif" loopimage="/system/media/bootscreen/boot2.gif" image_bg="/system/media/bootscreen/boot_bg.gif" audio="/system/media/bootscreen/boot.mp3" screenX="0" screenY="90" useAudio="1" />
</BootConfiguration>
I believe the part in bold is the part working on our phone, correct?
edit: just realised something. This isn't actually controlling anything, is it? If I am right, all this does is point the loader to the correct files, right? So, any ideas what I would need to edit and where I would find it?
Click to expand...
Click to collapse
Correct. The .xml file points to where the files are and there respective file names. The "useAudio" variable has either on or off (1 or 0) -- in order to do what you want, you'll have to trim the audio down to where you want it to play. Otherwise, you could try inserting another audio file (useAudio2) and set it to "1" and see if it boots properly, if it does, then all you have to do is trim it down, set it, and you should be good to go. I've never tried the secondly audio file -- so you could have problems, good luck though.

Yeah, I'm getting a funny error message. I can't post links yet, but I'll throw a couple of attachments of the diff. xml files up here. here is the error message I'm getting:
"
The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.
--------------------------------------------------------------------------------
Duplicate attribute. Error processing resource 'file:///C:/Android/Themes/Bootscreens/Work/system/media/bootscreen/revised....
/>
"
Any ideas? Or does this just mean it won't work?
edit: sorry for the .zip's, it wouldn't let me upload straight .xml's

I managed to flash my own custom boot but the only problem is that my sound comes through fine, but the animation I use shows up on the screen slanted
/ <~~~ like that, the pic is literally slanted, though it still runs.
Any ideas?

can you guys post a preview and the zips for your bootscreens? Or maybe on the themes sticky?

[Q] Need help, bricked my Atrix 2

OK so I pulled a stupid move and flashed my phone with this data:
p3droid
Chief Of Staff
--------------------------------------------------------------------------------
Join Date: Dec 2009
Location: Arizona
Posts: 1,329
Device: Motorola DroidThanks: 9Thanked 1,369 Times in 119 PostsDownloads:0 Uploads:0
How to get your phone back on the upgrade path...
If you have been flashing things (and who hasn't) when the official update comes out you will want to be on the correct builds so that you can take it. I present you with the method that will get you back and allow you to take any update.
This has only been tested on Windows 7 (32/64)
1) Download this fastboot file moto-fastboot-win32.zip
2) Download this Zip (Contains both System and webtop images) Download Now
3) Create a folder on Desktop named "Stock" <----- can be anything you want
4) Place the contents of both zip files in the folder named Stock
5) Put phone in Fastboot mode, connect to computer
6) Open a command terminal and go to the Stock folder (cd Desktop/Stock)
7) type this command in the terminal window and wait for the flashing to finish before going to the next line.
----> moto-fastboot.exe flash webtop grfs.img (This file will be flashed in 4 parts)
----> moto-fastboot.exe flash system system.img (This file will be flashed in 2 parts)
----> moto-fastboot.exe reboot
************************************************** ****************
Your boot image (kernel) and radio files will never go back to stock !!!
************************************************** ****************
Your phone is now back on stock (well the parts that matter anyways) Congratulations.
Next post will tell you how to root your device!!
Now I get this:
fastboot flash mode (s) (boot failure)
battery is low
cannot program
transfer mode:
USB Connected
invalid cg otv (cg: system): Invalid sp data
invalid cg hab (cg system, status: 0x0035)
invalid cg otv (cg: system)
Looks like I need a proper webtop.img and system.img?

Perfect example of why you should read the whole thread before trying to apply a mod/tweak/update to your phone if you don't know what you're doing. Or did you not realize the forum that thread was posted in was for the Droid Bionic? That site doesn't even have an Atrix 2 forum so why you would attempt any of the mods for those other devices to yours is beyond me. Bet you won't do that again

Nope wont do that again. Thought I got there from an A2 link saying the root worked. Anyways, any help would be great.

msumrell said:
Nope wont do that again. Thought I got there from an A2 link saying the root worked. Anyways, any help would be great.
Click to expand...
Click to collapse
Like I said, perfect example of why you should read the whole thread first! The very last comment in that posts says "the next post will tell you how to root your device." That should have been a hint that what you were about to do was not what you wanted to do.

Sorry bud, no way to recover the phone at this point.

Ao there are no system images available? Is it something that will come available with time maybe?

msumrell said:
Ao there are no system images available? Is it something that will come available with time maybe?
Click to expand...
Click to collapse
No sir, that's one of the things we're waiting for to start flashing stuff.....the other is the actual ability to flash stuff, lol.

msumrell said:
Ao there are no system images available? Is it something that will come available with time maybe?
Click to expand...
Click to collapse
If you bought it at Best Buy in the last 30 days run, don't walk, to Best Buy and give them $9.95 for a month of coverage. Then they will replace the phone, even bricked

Unless you take it in and return it you have a paper weight for the time being. I would take it in myself, the worst they can do is say no.

There's sbf leak from china. It's worth trying to flash it with RSD Lite 5.6
http://forum.xda-developers.com/showthread.php?p=19745460#post19745460

Semseddin said:
There's sbf leak from china. It's worth trying to flash it with RSD Lite 5.6
http://forum.xda-developers.com/showthread.php?p=19745460#post19745460
Click to expand...
Click to collapse
Please! You have nothing to lose. Is the bootloader unlocked on the chinese version?
Sent from my MB865 using XDA App

916x10 said:
Please! You have nothing to lose. Is the bootloader unlocked on the chinese version?
Sent from my MB865 using XDA App
Click to expand...
Click to collapse
are you not able to get into the boot menu and select factory reset at this point?

razholio said:
are you not able to get into the boot menu and select factory reset at this point?
Click to expand...
Click to collapse
I can, my phone is fine.
Sent from my MB865 using XDA App

when I try to load this file 'edison_china_5.5.1-1_GC-86_EDSCHN-6_cfc.xml' on RSD Lite 5.6 it says .xml wrong format or missing files. this is the contents of the .xml I need help on how to use it I guess.
--------------------------------------------
<?xml version="1.0" encoding="UTF-8"?>
<flashing>
<header>
<phone_model model="EDISON" />
<software_version version="edison-user 2.3.5 5.5.1-1_GC-86_EDSCHN-6 6 release-keys2011-10-25 16:56 Off.Bld LUD_EDISON_R1E_PATCH_10_111025_1636 crh1090280_M570_PC_CARD_RAINB" />
<interfaces>
<interface name="AP" />
</interfaces>
</header>
<steps interface="AP">
<step operation="reboot-bootloader" />
<step operation="flash" partition="cdt.bin" filename="cdt.bin" MD5="baca44d9b608e6c1cce61d535377ad78" />
<step operation="erase" partition="userdata" />
<step operation="flash" partition="lbl" filename="lbl" MD5="517bf626d45934f8fbb75c448f6dc711" />
<step operation="flash" partition="logo.bin" filename="logo.bin" MD5="06c07c2970460a4e656a3206859a3617" />
<step operation="flash" partition="ebr" filename="ebr" MD5="99bd0461bf959c636b087afd7768868f" />
<step operation="flash" partition="mbr" filename="mbr" MD5="8e89b3905532099d0a0a11f2ea7bedce" />
<step operation="flash" partition="devtree" filename="device_tree.bin" MD5="1c0acd25a4de4074d572f6baf877df5d" />
<step operation="flash" partition="system" filename="system.img" MD5="b1901a6d1e944befb83dd7549669a352" />
<step operation="flash" partition="boot" filename="boot.img" MD5="3d898516a4d226f1b138fa231a91d225" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="029c71633dbb8f1f92523250d7d325bc" />
<step operation="erase" partition="cache" />
<step operation="flash" partition="cdrom" filename="cdrom" MD5="9a470c15978f2d6e22bb606849574a7a" />
<step operation="flash" partition="radio" filename="radio.img" MD5="530c92abd1c2e4650e65106a4bf9dddf" />
<step operation="flash" partition="webtop" filename="grfs.img" MD5="dabfc21a52e4034333ed5a8501b2e02b" />
</steps>
</flashing>

OK so I got the xml file to load in RSD Lite after redownloading it. However it will not flash on the phone. I get this message.
Failed flashing process 2/15 flash cdt.bin "cdt.bin" ->Phone returned FAIL ;phone connected

How are you getting the phone into RSD protocol mode? I tried doing it the same way as my OG ATRIX and don't get the option?
Nevermind I take it you're using AP fastboot mode? Went and dug around the RZR forums to see how they were doing it. You do have all the current Motorola drivers installed? I had problems with my OG ATRIX and had to uninstall them and reinstall them before getting it to work properly.

Null 10 char

Should be the same steps as the bionic.
Pretty cut and dry, make sure you're plugging it directly into your motherboard's usb ports.
It could simply not be compatible or signed with different keys...
Installation
1.Install the Motorola Mobile Drivers
2.Install RSD Lite 5.5
3.Make sure your Motorola Droid Bionic is powered on and backed up.
◦Alternatively, boot into AP Fastboot mode by powering down (or pulling battery), then press and hold the volume down button while powering on. From there, continue with Step 4.
4.Plug your Motorola Droid Bionic into a back USB port on your computer.
◦Front USB ports are often unreliable when it comes to power levels. They should not be used for flashing.
5.Run “RSD Lite” on your computer
6.Press the “. . .” button next to the box labeled “Filename”
7.Browse and open the FXZ file
8.Wait for the program to read the file, then choose “Uncompress And Start Flashing”
9.Now, the device will slowly flash the FXZ file.
10.When flashing completes, the device will reboot into recovery and install the two radio images.
11.Congratulations! You’ve restored your Motorola Droid Bionic
Click to expand...
Click to collapse

Msumrell, i hope this works then atleast we have something to fall back on if somebody brick's there phone. Good luck!
Sent from my MB865 using xda premium

at this point I have to say it does not work. I have tried from different usbs and get the same results. failed. It is certainly an easy enough process. A am guessing it is not a compatable image? dont know. I also tried just loading teh system.img and grfs.img with moto-fastboot in a dos window and no go their either. Keep waiting for good image I guess.

[OFICIAL OTA] Gingerbread 2.3.6!

Hi all, I know that there are a couple of threads about the OTA already but they're all fragmented and not quite helpful, so I thought I'd pitch in.
Today an OTA of 2.3.6 was publicly released for the A2. Although it's not ICS, or even 2.3.7, it's still much more stable and faster. Here's some of the details:
-Much improved camera app! (The original was pretty faulty)
-Enhanced keyboard
-Possibly the first AT&T bloatware to ever be useful, with visual voicemail and ---Syncing of texts/calls to the cloud
-Improved Hotspot and Webtop
-Fixes to any problems with haptic feedback
-Call ending does not lag! (as much)
-Uses MUCH less RAM
For all the details check out this link.
At the moment no one has discovered a root protocol for our version of 2.3.6... i.e. it can't be rooted. I personally have tried flashing/reflashing the fxz, updating, and trying different exploits, all of which has failed. I doubt that we will find a way to root this 2.3.6 any time soon. However, the devs here are working hard at implementing 2.3.6 with root in their ROMs. (The latest Supercharged ROM is based off of 2.3.6!) If you want to have your device rooted with 2.3.6 and you're currently on 2.3.5 (rooted), follow these instructions:
With a root explorer, navigate to /system/bin/ and edit the mount_ext3.sh file. If you used a 1-click root method, then add the following lines to the end of the file (if you manually rooted then you might want to omit the 1st/2nd line):
Code:
chmod 4755 /system/bin/su
chmod 4755 /system/xbin/su
chmod 4755 /system/app/Superuser.apk
To apply the update, go to Settings->About Phone->System update and it should prompt you to update. Make sure you're connected to wifi and then hit "OK". If you have heavily modified your phone then I suggest that you flash the fxz first, then root it, then apply the hack above, then update. Also, although the A2 has the ability to uninstall most bloatware without rooting, the update requires that ALL BLOATWARE MUST BE INSTALLED. If you uninstalled any bloatware then you will have to flash the fxz first.
NOTE: once you apply the update you will NEVER be able to flash the 2.3.5 fxz! You need to replace some files first! To flash the fxz, follow these directions:
-Download this file: View attachment replace.zip
-Unzip it and move all the the items in it to the stock fxz. You might get a warning about replacing files, just click OK. NOTE that Windows might not be able to handle the size of the fxz. I have 6 GB RAM but Windows still wasn't able to perform a drag-and-drop through the fxz's zip. I recommend that you just unzip the fxz and then put the files in. (You don't have to rezip it either, RSD Lite will still recognize it and will flash faster).
-You should be able to use RSD Lite to flash the file.
Please note that this is not a support thread, it is an info/how-to thread... if you have any problems then make a thread about it, and be as detailed as possible.
Enjoy!

cogeary said:
Hi all, I know that there are a couple of threads about the OTA already but they're all fragmented and not quite helpful, so I thought I'd pitch in.
Today an OTA of 2.3.6 was publicly released for the A2. Although it's not ICS, or even 2.3.7, it's still much more stable and faster. Here's some of the details:
-Much improved camera app! (The original was pretty faulty)
-Enhanced keyboard
-Possibly the first AT&T bloatware to ever be useful, with visual voicemail and ---Syncing of texts/calls to the cloud
-Improved Hotspot and Webtop
-Fixes to any problems with haptic feedback
-Uses MUCH less RAM
For all the details check out this link.
At the moment no one has discovered a root protocol for our version of 2.3.6... i.e. it can't be rooted. However, the devs at XDA are working hard at implementing 2.3.6 with root in their ROMs. If you want to have your device rooted with 2.3.6 and you're currently on 2.3.5 (rooted), follow these instructions:
With a root explorer, navigate to /system/bin/ and edit the mount_ex3.sh file. Add these three lines to the end of it the file:
Code:
chmod 4755 /system/bin/su
chmod 4755 /system/xbin/su
chmod 4755 /system/app/Superuser.apk
To apply the update, go to Settings->About Phone->System update and it should prompt you to update. Make sure you're connected to wifi and then hit "OK". If you have heavily modified your phone then I suggest that you flash the fxz first, then root it, then apply the hack above, then update.
NOTE: once you apply the update you will have problems flashing the 2.3.5 fxz! If you want to flash the fxz then follow these instructions:
First you need to get access of the downloaded OTA file. It should be somewhere in /cache if you have already downloaded it.
-Replace the following files from the fxz with the files found in the OTA download: cdt.bin and device_tree.bin
-Now edit the xml file found in the fxz. Delete the following lines:
Code:
<step operation="flash" partition="boot" filename="boot.img" MD5="8E9D7DD161180EC898E4F2BA5395B29E" />
<step operation="flash" partition="recovery" filename="recovery.img" MD5="E0F3D8A778ECE612869E8200F0C21B26" />
-You should be able to use RSD Lite to flash the file.
Enjoy!
Click to expand...
Click to collapse
I recommend closing this thread so that is doesn't turn in to another OTA support thread.

Does anybody have cdt.bin and device_tree.bin from 2.3.6? I think that my /cache was erased by FXZ so I can't pull it using ADB.
edit: Thanks So Much to Jim!!!!
Default Re: quick question
Originally Posted by guapinoy
Do you have cdt.bin, lbl, and device_tree.bin from 2.3.6? I upgraded with OTA update, lost root, and then tried to Flash 2.3.5 fastboot. It had a flash fail so now when it boots up it only goes to Fastboot, they only way is to do the recovery boot up (hold up and down) then choosing normal. I don't have root on my device is there anyway I can extract the OTA update using ADB?
Here you go:
cdt.bin:
http://dl.dropbox.com/u/45576654/cdt.bin
device_tree.bin:
http://dl.dropbox.com/u/45576654/device_tree.bin
lbl:
http://dl.dropbox.com/u/45576654/lbl
Jim
__________________
_________________________________________
"Microsoft is the Evil Empire"
"I *nix UNIX we all scream for Linux"
If you don't have dropbox, go sign up here:
http://db.tt/SorT4X6q
You will get an extra 250MB, and so will I.
Jim

farshad525hou said:
I recommend closing this thread so that is doesn't turn in to another OTA support thread.
Click to expand...
Click to collapse
I think I've just about covered it for any noobs, and anybody with a real problem will probably post a new thread about it.

I also noticed that it ends calls much quicker now.

Thanks cogeary
HAS BEEN ADDED TO THE BEGINNERS THREAD , under rooting and flashing the FXZ

Full details of update: http://www.motorola.com/staticfiles...65/ATT/RN_ATRIX2_55.13.25.MB865.ATT.en.US.htm
Oh, and...
NO CARRIER IQ!!! http://imgur.com/5k0js
This is on a rooted, but not modded phone running 2.3.6 (will post phone info if asked for verification). Haven't frozen any apps either. YAY!

Do apps installed on SD card still go missing?

Sharpshooterrr said:
Do apps installed on SD card still go missing?
Click to expand...
Click to collapse
Good question . I am wondering too?
Sent from my MB865 using XDA App

My battery life is better as well..
Placebo?!

alcatel444 said:
Good question . I am wondering too?
Sent from my MB865 using XDA App
Click to expand...
Click to collapse
The issue appears to be resolved with this update.

Major improvement in battery life

I noticed an oddity with my update. I shelled in to apply the forever_root hack and thought I'd watch /cache/ for the update file. (btw, in the absence of vi, echo "yer text" >>' works quite well) I started the update download and watched a new file show up in /cache. There were two:
Blur_Version.55.11.16.MB865.ATT.en.US.crc
Blur_Version.55.11.16.MB865.ATT.en.US.zip
but these have the old MB865 OS version, what gives?
the update completed and says I have the new 55.13.25 OS.
btw, root was preserved and the update went fine after unfreezing all bloatware.

nickyb03 said:
Major improvement in battery life
Click to expand...
Click to collapse
I knew i wasnt the only one. It really is better.
Keyboard seems more accurate. The vibration feedback is much less intense now.
I really like this update. Makes the almost perfect phone that much more perfect.
Since the app install issue is gone, memory card issue gone (i had to buy a new card), better battery life. I cant think of anything id change.

mic_crispy said:
I cant think of anything id change.
Click to expand...
Click to collapse
Except ICS would be nice...

Surprising to see you having battery life improvements. My battery life has actually significantly decreased....

Good to hear the SDCard problem is finally solved.
toastthemost said:
NO CARRIER IQ!!! http://imgur.com/5k0js
Click to expand...
Click to collapse
Awesome, thanks for pointing that out! No CIQ for me as well!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my MB865 using Tapatalk

I just attempted to upgrade to 2.3.6 today, and it seems to be in a boot loop. It does the M logo with the ripples and proceeds to the AT&T thing, but then restarts? Is this normal? What should I do?
edit: i pulled the battery, but it doesn't fix anything
edit2: I'm reflashing the 2.3.5 fxz through RSD Lite, I hope this works

souvik1997 said:
I just attempted to upgrade to 2.3.6 today, and it seems to be in a boot loop. It does the M logo with the ripples and proceeds to the AT&T thing, but then restarts? Is this normal? What should I do?
edit: i pulled the battery, but it doesn't fix anything
edit2: I'm reflashing the 2.3.5 fxz through RSD Lite, I hope this works
Click to expand...
Click to collapse
Your on the right track. My guess is you were rooted and removed something the patch affects. Likely one of the bloatware apks. Good luck!

souvik1997 said:
I just attempted to upgrade to 2.3.6 today, and it seems to be in a boot loop. It does the M logo with the ripples and proceeds to the AT&T thing, but then restarts? Is this normal? What should I do?
edit: i pulled the battery, but it doesn't fix anything
edit2: I'm reflashing the 2.3.5 fxz through RSD Lite, I hope this works
Click to expand...
Click to collapse
If the update failed at the beginning then flashing the stock fxz is what you should do. If the stock fxz fails to flash then that means that your phone was at least partly updated, so follow the instructions for flashing the fxz from 2.3.6 in the OP.
Either way you are on the right track.

FXZ?

I want to flash an FXZ, but the download links are down. Anyone have a mirror?

hotweels258 said:
I want to flash an FXZ, but the download links are down. Anyone have a mirror?
Click to expand...
Click to collapse
http://sbf.droid-developers.org/edison/list.php
Sent from my MB865 using XDA

Warning !!!
Only flash ATT version if yours is AT&T

farshad525hou said:
http://sbf.droid-developers.org/edison/list.php
Sent from my MB865 using XDA
Click to expand...
Click to collapse
Awesome link bookmarked never know when I could loose my copy on hard drive.....

Flash error
Hi guys,
i'm trying to flash my atrix 2.3.6, i downloaded the files in this post (the ATT ones since i have an ATT phone), i replaced the files, downloaded the usb driver and then procceded to flash it with RSD lite 5.6 and it showed me this error on the status: "Failed flashing process. Failed flashing process. 3/18 flash mbmloader "mbmloader.bin" -> Phone returned FAIL.; phone connected"
Also, in the device properties it shows me this:
ESN:
Technology: N/A
Software Version: N/A
Flex Version: N/A
DRM Version: N/A
Can anybody help me please?

cal8 said:
Hi guys,
i'm trying to flash my atrix 2.3.6, i downloaded the files in this post (the ATT ones since i have an ATT phone), i replaced the files, downloaded the usb driver and then procceded to flash it with RSD lite 5.6 and it showed me this error on the status: "Failed flashing process. Failed flashing process. 3/18 flash mbmloader "mbmloader.bin" -> Phone returned FAIL.; phone connected"
Also, in the device properties it shows me this:
ESN:
Technology: N/A
Software Version: N/A
Flex Version: N/A
DRM Version: N/A
Can anybody help me please?
Click to expand...
Click to collapse
It sounds like you tried to flash an international version previous to this.
What you need to do is make sure you've unzipped the fxz, then open the "
InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.xml" file with notepad, and delete the following lines:
Code:
<step operation="flash" partition="mbm" filename="allow-mbmloader-flashing-mbm.bin" MD5="2F5211B8011CBA58290D7B51B56F8DFB" />
<step operation="reboot-bootloader" />
<step operation="flash" partition="mbmloader" filename="mbmloader.bin" MD5="9D1958ED3F5E971FF079B195E338BA86" />
<step operation="flash" partition="mbm" filename="mbm.bin" MD5="DA1A78B87D8FE6D8DA6DE7CA2C5B0A7E" />
Save and close, then try and reflash.

still not working
cogeary said:
It sounds like you tried to flash an international version previous to this.
What you need to do is make sure you've unzipped the fxz, then open the "
InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.xml" file with notepad, and delete the following lines:
Code:
<step operation="flash" partition="mbm" filename="allow-mbmloader-flashing-mbm.bin" MD5="2F5211B8011CBA58290D7B51B56F8DFB" />
<step operation="reboot-bootloader" />
<step operation="flash" partition="mbmloader" filename="mbmloader.bin" MD5="9D1958ED3F5E971FF079B195E338BA86" />
<step operation="flash" partition="mbm" filename="mbm.bin" MD5="DA1A78B87D8FE6D8DA6DE7CA2C5B0A7E" />
Save and close, then try and reflash.
Click to expand...
Click to collapse
Ok, i did that and it worked. But after the flash process it sends me to the recovery image (the one with the triangle where you do the fatory reset). After it went to bootloop, in the status bar it said "please power up manually this device" even when the c/p where on. So i turned it off, and then turned it on again to the fastboot screen. The status screen changed sayng the process was finished and the resul bar said "PASS". But nothing changed.
P.S: i have the american version of this cellphone and nothing works, i cant delete aplications and the cellphone reboots randomly and factory resets doesn't work with my device

cogeary said:
It sounds like you tried to flash an international version previous to this.
What you need to do is make sure you've unzipped the fxz, then open the "
InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.xml" file with notepad, and delete the following lines:
Code:
<step operation="flash" partition="mbm" filename="allow-mbmloader-flashing-mbm.bin" MD5="2F5211B8011CBA58290D7B51B56F8DFB" />
<step operation="reboot-bootloader" />
<step operation="flash" partition="mbmloader" filename="mbmloader.bin" MD5="9D1958ED3F5E971FF079B195E338BA86" />
<step operation="flash" partition="mbm" filename="mbm.bin" MD5="DA1A78B87D8FE6D8DA6DE7CA2C5B0A7E" />
Save and close, then try and reflash.
Click to expand...
Click to collapse
It worked very well all functions are restored, later updaed to 2.3.6 using OTA over wifi.
I only have a question that what part will not be flashed after deleting those lines and what effect it may have on the phone?

OpenDelta OTA for all phones

Hi i have tested a lot of OTA apps and configs and they are very annoying until i stop thinking for a moment and I find a solution for having true OTAS updates and not depending from other users just like Nexus Devices OTAS.
Ok we started:
First of all we need to download Android Bundle with contains SDK and Eclipse
Here it is:
http://developer.android.com/sdk/index.html?hl=sk#download
After it is download and installed.
You are going to download my fixed source for supporting from Android 4.1.2 to 4.4.2.
https://github.com/werty100/OpenDelta
And Click on:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Them open Eclipse...
Go to file/Import:
Next and locate were is the download source
Then Finish...
Wait until it is import....
Go to res folder, values and open config.xml:
Here are the important values for making work your OTA in your phone.
Code:
<!-- Property to read for ROM version -->
<string name="property_version">ro.delta.version</string>
<!-- Property to read for device identifier -->
<string name="property_device">ro.delta.device</string>
This should be put in build.prop:
Ex:
ro.delta.version=1.0.2
ro.delta.device=i9000
You can modificated all values but you should modificate this ones:
Code:
<!-- URL base to find .delta files, %s is expanded to property_device value. Path is suffixed by (expanded) filename_base -->
<string name="url_base_delta">https://delta.omnirom.org/nightlies/%s/</string>
<!-- URL base to find .update and .sign files, %s is expanded to property_device value. Path is suffixed by (expanded) filename_base -->
<string name="url_base_update">http://delta.omnirom.org/nightlies/%s/</string>
<!-- URL base to find the full zip files, %s is expanded to property_device value. Path is suffixed by (expanded) filename_base -->
<string name="url_base_full">http://dl.omnirom.org/%s/</string>
Indicates where to find the ZIP for your phone...
Also you can modificate all UI and values....
After the essentials modifications you will need to compile APK:
Go here and click on selected item..
You will need to create your own KeyStores
Rellenate also this:
https://dl.dropboxusercontent.com/u/26870831/rellenate.png
Them just put destination and click finish:
After all of this you have to modificate the Settings.apk of your rom:
Decompile with the script/tool you like more and go to:
In res/values:
String.xml
Add this:
Code:
<string name="system_update_settings_list_item_title">System updates</string>
<string name="system_update_settings_list_item_summary" />
Paste it near baseband_version string kernel_version string etc...
Then go to public and paste this near device_info_settings:
Code:
<public type="string" name="system_update_settings_list_item_title" id="0x7f0c06d7" />
<public type="string" name="system_update_settings_list_item_summary" id="0x7f0c06d8" />
Then go to xml/device_info_settings.xml:
And copy this in the firs lines after:
Code:
<?xml version="1.0" encoding="utf-8"?>
<PreferenceScreen android:title="@string/about_settings"
xmlns:android="http://schemas.android.com/apk/res/android">
Paste this:
Code:
<PreferenceScreen android:title="@string/system_update_settings_list_item_title" android:key="system_update_settings" android:summary="@string/system_update_settings_list_item_summary">
<intent android:action="android.settings.SYSTEM_UPDATE_SETTINGS" />
</PreferenceScreen>
<PreferenceScreen android:title="@string/additional_system_update_settings_list_item_title" android:key="additional_system_update_settings">
<intent android:targetPackage="@string/additional_system_update" android:action="android.intent.action.MAIN" android:targetClass="@string/additional_system_update_menu" />
</PreferenceScreen>
After Compiling Settings.apk you will have full OTAS

Tomorrow More

Today more
Publish on HTCMania haha

Update New settings for OTA

Just a quick question:
Code:
[B] <!-- URL base to find .delta files, %s is expanded to property_device value. Path is suffixed by (expanded) filename_base -->
<string name="url_base_delta">https://delta.omnirom.org/nightlies/%s/</string>
<!-- URL base to find .update and .sign files, %s is expanded to property_device value. Path is suffixed by (expanded) filename_base -->
<string name="url_base_update"http://delta.omnirom.org/nightlies/%s/</string>[/B]
<!-- URL base to find the full zip files, %s is expanded to property_device value. Path is suffixed by (expanded) filename_base -->
<string name="url_base_full">http://dl.omnirom.org/%s/</string>
If we want to configure it to our directory, what should we inclue on .delta files & .update and .sing files?

With this OTA guide will I have to boot into recovery to flash a OTA?

You can't use this for any other ROM because we don't know what we should had on .delta & .update & .sign files

Howdy! Some general stuff:
You should credit original developer of OpenDelta (that's Chainfire @ OmniROM)
Proper way to make own, patched version is Pulling the original repository (easiest way is using "Pull" button on GitHub there: https://github.com/omnirom/android_packages_apps_OpenDelta) and then patching it - this way you preserve all the commits history (and credits to original authors)
_MarcoMarinho_ said:
You can't use this for any other ROM because we don't know what we should had on .delta & .update & .sign files
Click to expand...
Click to collapse
There we got with an example:
https://delta.omnirom.org/nightlies/i9300/omni-4.4.3-20140605-i9300-NIGHTLY.sign
https://delta.omnirom.org/nightlies/i9300/omni-4.4.3-20140605-i9300-NIGHTLY.update
https://delta.omnirom.org/nightlies/i9300/omni-4.4.3-20140605-i9300-NIGHTLY.delta
.delta file is JSON
.sign is binary signature
.delta is binary delta data
...and
GUESS WHAT! There's an opensource stuff to generate ALL of the above.
Completely! Automagically!
https://github.com/omnirom/android_packages_apps_OpenDelta/tree/android-4.4/server/

Rebellos said:
Howdy! Some general stuff:
You should credit original developer of OpenDelta (that's Chainfire @ OmniROM)
Proper way to make own, patched version is Pulling the original repository (easiest way is using "Pull" button on GitHub there: https://github.com/omnirom/android_packages_apps_OpenDelta) and then patching it - this way you preserve all the commits history (and credits to original authors)
There we got with an example:
https://delta.omnirom.org/nightlies/i9300/omni-4.4.3-20140605-i9300-NIGHTLY.sign
https://delta.omnirom.org/nightlies/i9300/omni-4.4.3-20140605-i9300-NIGHTLY.update
https://delta.omnirom.org/nightlies/i9300/omni-4.4.3-20140605-i9300-NIGHTLY.delta
.delta file is JSON
.sign is binary signature
.delta is binary delta data
...and
GUESS WHAT! There's an opensource stuff to generate ALL of the above.
Completely! Automagically!
https://github.com/omnirom/android_packages_apps_OpenDelta/tree/android-4.4/server/
Click to expand...
Click to collapse
Thanks so much :highfive:
So I just need to modify few things, generate ALL stuff and then upload it to my server right?

Yup. Looks like. I'm not really experienced with OpenDelta but knowing Chainfire it's all easy to work with.

Post for subscription

when it comes to these stuff (git with coding and xml and OH MY GOD!) i am a total noob.
i still don't know how do i generate these files. I understand .zip is the whole ROM, but i have no idea how i can make .update .sign and .delta and what should i put in them and all.
hehe, to me, all i see is three beautiful files here https://github.com/omnirom/android_packages_apps_OpenDelta/tree/android-4.4/server/ which i know nothing about how i can use them to get the files.
i guess i'll wait for the "tomorrow more"

@_MarcoMarinho_ you can find on the github readme how to generate the Delta files.
Server-side
To create the delta files on the server, you need several things, some of which can be found in the server directory. The main thing is the opendelta.sh script. It contains a configuration section which you can edit with the correct file locations on your own system. Quite likely you will need to create a wrapper script that pulls in your previous release and your current release, and pushes out the created delta files.
The script depends on xdelta3, zipadjust and minsignapk.
For the builds on your server, make a copy of the jni directory - do not compile inside jni because you may mess up the build of libopendelta.
xdelta3 can be built in (the copy of) jni/xdelta3-3.0.7 by calling ./configure and make.
zipadjust can be built in (the copy of) jni by calling:
gcc -o zipadjust zipadjust.c zipadjust_run.c -lz
dedelta (not used by the script, but maybe helpful when debugging) can be built in (the copy of) jni by calling:
gcc -o dedelta xdelta3-3.0.7/xdelta3.c delta.c delta_run.c
minsignapk Java source is in the server directory, as well as a prebuilt minsignapk.jar file that should work on most systems.
Click to expand...
Click to collapse
If you are however to lazy to set up all that stuff check my script on github you can find here:
https://github.com/Myself5/CarbonDelta_server_software/
(I used it for my unofficials and when we tested CarbonDelta (which is based on OpenDelta))
Check the readme on how to install it and use it.

Myself5 said:
@_MarcoMarinho_ you can find on the github readme how to generate the Delta files.
If you are however to lazy to set up all that stuff check my script on github you can find here:
https://github.com/Myself5/CarbonDelta_server_software/
(I used it for my unofficials and when we tested CarbonDelta (which is based on OpenDelta))
Check the readme on how to install it and use it.
Click to expand...
Click to collapse
Thank, thanks so much, now I understand
-----
When I should put your repo? inside pakcages/apps?

_MarcoMarinho_ said:
Thank, thanks so much, now I understand
-----
When I should put your repo? inside pakcages/apps?
Click to expand...
Click to collapse
In any folder where you want it. It must not be inside your Roms Sourcecode. To create the delta update and sign files just follow the readme

Code:
<?xml version="1.0" encoding="utf-8"?>
<resources>
<!-- Output some debug strings -->
<item type="bool" name="debug_output">false</item>
<!-- Property to read for ROM version -->
<string name="property_version">ro.euclidean.version</string>
<!-- Property to read for device identifier -->
<string name="property_device">ro.euclidean.device</string>
<!-- %s is expanded to property_version value. .zip, .delta, .update, .sign extensions added when needed -->
<string name="filename_base">euclidean_%s</string>
<!-- Path deltas are stored, relative to sdcard root -->
<string name="path_base">EuclideanDelta</string>
<!-- URL base to find .delta files, %s is expanded to property_device value. Path is suffixed by (expanded) filename_base -->
<string name="url_base_delta">http://euclideanrom.grn.cc/downloads/%s/delta/</string>
<!-- URL base to find .update and .sign files, %s is expanded to property_device value. Path is suffixed by (expanded) filename_base -->
<string name="url_base_update">http://euclideanrom.grn.cc/downloads/%s/delta/</string>
<!-- URL base to find the full zip files, %s is expanded to property_device value. Path is suffixed by (expanded) filename_base -->
<string name="url_base_full">http://euclideanrom.grn.cc/downloads/%s/</string>
This is my setup.
I can't figure it out why I don't receive the updates

@werty100 will this work for lollipop?

gcng said:
@werty100 will this work for lollipop?
Click to expand...
Click to collapse
You need the new app source code.

Hey guys. I want add support OTA in my builds. I'm fully understand what need to be changed on client side and how generate *.delta and *.update files, but what i need for server side?
Just place files at some path, and somehow mystical way the application will find it.. or need some json script, which protocol need to use, how app retrieve list of files/information from server...
Thanks in advance.

ElArchibald said:
Hey guys. I want add support OTA in my builds. I'm fully understand what need to be changed on client side and how generate *.delta and *.update files, but what i need for server side?
Just place files at some path, and somehow mystical way the application will find it.. or need some json script, which protocol need to use, how app retrieve list of files/information from server...
Thanks in advance.
Click to expand...
Click to collapse
just add them to web server.