[XT925] Advanced Reboot Menu for JB 4.1.2 Motorola ROM

Orphee · Aug 22, 2013

Hello,

I wanted to add Advanced Reboot Menu on my RAZR HD.

Max_choco did it for the RAZR I (+ some other stuffs) http://xdaforums.com/showthread.php?t=2393777

I used his work to build my own framework-res.apk and android.policy.jar

I made a flashable zip for CWM Recovery.

I SUGGEST YOU TO MAKE A FULL NANDROID BACKUP BEFORE DOING ANYTHING. I'M NOT RESPONSIBLE OF ANY DAMAGE YOU COULD DO TO YOU OR YOUR PHONE. USE IT AT YOUR OWN RISK.

Modified files are (make a backup at least) :

/system/framework/framework-res.apk
/system/framework/android.policy.jar
/system/framework/android.policy.odex (original deleted with flashable zip)

My ROM is DEODEXED, It should work on ODEXED ROM too, but I can't be sure.

Built with Retail FR 4.1.2 based ROM.

Thanks to max_choco for his work on the Razr I.

mentose457 · Aug 22, 2013

Right on. I've been planning on doing this for the 926. This ought to be a big help. Thanks for the hard work.

Sent from my DROID RAZR HD using Tapatalk 4

esok44 · Aug 26, 2013

unfortunately didnt work on odexed o2 Rom.

Got a bootloop right now, now i got some work to do, to fix it

Hope, i can fix it, without installing backup

Orphee · Aug 26, 2013

esok44 said:
unfortunately didnt work on odexed o2 Rom.

Got a bootloop right now, now i got some work to do, to fix it

Hope, i can fix it, without installing backup

erf, sorry...

Did you try wipe cache & dalvik ?

esok44 · Aug 26, 2013

Orphee said:
erf, sorry...

Did you try wipe cache & dalvik ?

Yepp did, but it seems like my odex files for android policy and framework-res are lost...

Orphee · Aug 26, 2013

esok44 said:
Yepp did, but it seems like my odex files for android policy and framework-res are lost...

Yes, the flashable zip must delete android.policy.odex as there are deodexed (framework-res.apk does not have odex).
I should had odex to the #1 list

esok44 · Aug 26, 2013

Orphee said:
Yes, the flashable zip must delete android.policy.odex as there are deodexed (framework-res.apk does not have odex).
I should had odex to the #1 list

Well alright, so i need to get a hand on the .odex file, do you have it or do you now how to get it

Orphee · Aug 26, 2013

Hope it will help you.
All files come from Retail FR original ROM.

esok44 · Aug 26, 2013

Orphee said:
Hope it will help you.
All files come from Retail FR original ROM.

I will let you know

Have you any idea, how to extract stuff from the motorola OTA-updates.

Orphee · Aug 26, 2013

Maybe I'm wrong, but OTA updates are only patch files modifiyng the original from the ROM.
Because of this you must have original ROM to update OTA, any modified file will fail the update.
You need to find the full RSD Lite flashable ROM.

esok44 · Aug 26, 2013

Orphee said:
Hope it will help you.
All files come from Retail FR original ROM.

I'm not sure, should i set permissions to 0644?

Cause it's still not booting up

Anyone got an idea??

---------- Post added at 02:23 PM ---------- Previous post was at 02:20 PM ----------

Orphee said:
Maybe I'm wrong, but OTA updates are only patch files modifiyng the original from the ROM.
Because of this you must have original ROM to update OTA, any modified file will fail the update.
You need to find the full RSD Lite flashable ROM.

I got the Flashable RSD-Lite .zip, i managed to get the system_signed, but i cant do nothing with it oO

Orphee · Aug 26, 2013

Yes the files should be 644, but maybe O2 and RTFR aren't compatible... Did you make a nandroid backup ?

esok44 · Aug 26, 2013

Orphee said:
Yes the files should be 644, but maybe O2 and RTFR aren't compatible... Did you make a nandroid backup ?

Of course not, you now the deal, it always goes wrong when u dont make a backup.

is it possible to compile the odex files from the apk's?
Then i would just pull the apk and make a new one

Orphee · Aug 26, 2013

You have your original O2 rom for RSD Lite ?

If yes, unzip it, open XML file

Here a exemple :

Code:

<?xml version="1.0" encoding="UTF-8"?>
<flashing>
        <header>
                <phone_model model="VANQUISH_U" />
                <software_version version="XT925_vffr-user 4.1.2 9.8.2Q-8-XT925_VQUL-16 1354498168 release-keysVANQUISH_U_BP_100700.250.66.01P" />
        <interfaces>
                <interface name="AP" />
        </interfaces>
        </header>
        <steps interface="AP">
		<step operation="getvar" var="max-download-size" />
		<step operation="oem" var="fb_mode_set" />
		<step operation="flash" partition="partition" filename="partition_signed" MD5="374c5ce95704791927c2b72543cc7f16" />
                <step operation="flash" partition="sbl1" filename="sbl1_signed" MD5="04faedb3ac5e2401f233856b801eab73" />
                <step operation="flash" partition="sbl2" filename="sbl2_signed" MD5="131ff66e7d861bfedfd2c7b5ca428381" />
                <step operation="flash" partition="sbl3" filename="sbl3_signed" MD5="52bafe485a64f12ed2fda312c60f0a34" />
                <step operation="flash" partition="rpm" filename="rpm_signed" MD5="919d0b340cfdd5fc7c541803db65c2d6" />
                <step operation="flash" partition="tz" filename="tz_signed" MD5="ed1c505e36e769ccf0bb3c10e46dd62b" />
                <step operation="flash" partition="aboot" filename="aboot_signed" MD5="61ddd4c78a3d1ff64567740446f803fd" />
                <step operation="flash" partition="modem" filename="modem_signed" MD5="af7fa6a2a496fe4d89778829bf40bb4a" />
                <step operation="flash" partition="fsg" filename="fsg_signed" MD5="74031834280d2e5cec7f40d620c4024d" />
                <step operation="erase" partition="modemst1" />
                <step operation="erase" partition="modemst2" />
		<step operation="flash" partition="logo" filename="logo" MD5="6463dc057abf889f3b83a4d3da4cdd1e" />
		<step operation="flash" partition="devtree" filename="devtree_signed" MD5="7d0c02350ac2b47bc17aa963f8cafcd9" />
		<step operation="flash" partition="boot" filename="boot_signed" MD5="5d27060578eca132919570e9208885e4" />
                <step operation="flash" partition="recovery" filename="recovery_signed" MD5="21cdb4fd40b8d9ebb9aa9565c68eeb5f" />
                <step operation="flash" partition="system" filename="system_signed" MD5="fd6b6dc463e2a03b8d507eb51e7eda8b" />
		<step operation="flash" partition="cdrom" filename="cdrom_signed" MD5="db97fe7f66377bf706e8263007ca4a53" />
		<step operation="erase" partition="tombstones" />
                <step operation="erase" partition="cache" />
		<step operation="erase" partition="userdata" />
		<step operation="oem" var="fb_mode_clear" />
         </steps>
</flashing>

Remove from it the following lines :

<step operation="getvar" var="max-download-size" />
<step operation="flash" partition="logo" filename="logo" MD5="6463dc057abf889f3b83a4d3da4cdd1e" /> (if your bootloader is unlocked and you flashed custom boot logo. And don't want it to be restored to WARNING UNLOCKED BOOTLOADER)
<step operation="flash" partition="recovery" filename="recovery_signed" MD5="21cdb4fd40b8d9ebb9aa9565c68eeb5f" /> (Remove if if you are unlocked and have a custom recovery like CWM)
<step operation="erase" partition="userdata" /> (VERY IMPORTANT, WITHOUT REMOVING THIS LINE, YOU LOST ALL YOUR DATA)

Exemple when all stuff removed :

Code:

<?xml version="1.0" encoding="UTF-8"?>
<flashing>
        <header>
                <phone_model model="VANQUISH_U" />
                <software_version version="XT925_vffr-user 4.1.2 9.8.2Q-8-XT925_VQUL-16 1354498168 release-keysVANQUISH_U_BP_100700.250.66.01P" />
        <interfaces>
                <interface name="AP" />
        </interfaces>
        </header>
        <steps interface="AP">
		<step operation="oem" var="fb_mode_set" />
		<step operation="flash" partition="partition" filename="partition_signed" MD5="374c5ce95704791927c2b72543cc7f16" />
                <step operation="flash" partition="sbl1" filename="sbl1_signed" MD5="04faedb3ac5e2401f233856b801eab73" />
                <step operation="flash" partition="sbl2" filename="sbl2_signed" MD5="131ff66e7d861bfedfd2c7b5ca428381" />
                <step operation="flash" partition="sbl3" filename="sbl3_signed" MD5="52bafe485a64f12ed2fda312c60f0a34" />
                <step operation="flash" partition="rpm" filename="rpm_signed" MD5="919d0b340cfdd5fc7c541803db65c2d6" />
                <step operation="flash" partition="tz" filename="tz_signed" MD5="ed1c505e36e769ccf0bb3c10e46dd62b" />
                <step operation="flash" partition="aboot" filename="aboot_signed" MD5="61ddd4c78a3d1ff64567740446f803fd" />
                <step operation="flash" partition="modem" filename="modem_signed" MD5="af7fa6a2a496fe4d89778829bf40bb4a" />
                <step operation="flash" partition="fsg" filename="fsg_signed" MD5="74031834280d2e5cec7f40d620c4024d" />
                <step operation="erase" partition="modemst1" />
                <step operation="erase" partition="modemst2" />
		<step operation="flash" partition="devtree" filename="devtree_signed" MD5="7d0c02350ac2b47bc17aa963f8cafcd9" />
		<step operation="flash" partition="boot" filename="boot_signed" MD5="5d27060578eca132919570e9208885e4" />
                <step operation="flash" partition="system" filename="system_signed" MD5="fd6b6dc463e2a03b8d507eb51e7eda8b" />
		<step operation="flash" partition="cdrom" filename="cdrom_signed" MD5="db97fe7f66377bf706e8263007ca4a53" />
		<step operation="erase" partition="tombstones" />
                <step operation="erase" partition="cache" />
		<step operation="oem" var="fb_mode_clear" />
         </steps>
</flashing>

Now flash it with RSD lite (point XML file with RSD Lite) and cross fingers.

Edit : Or you can do the minimum :
Take system_signed file and flash it with fastboot in AP :

fastboot.exe flash system system_signed

esok44 · Aug 26, 2013

Orphee said:
Edit : Or you can do the minimum :
Take system_signed file and flash it with fastboot in AP :

fastboot.exe flash system system_signed

This didnt work, it told me something about, errors and so on...

'load_file: could not read 775675996 bytes from 'system_signed'
error: cannot load 'system_signed''

Thats the error i get

Edit: Flashing via RSD Lite, doesn't work because: "Unknown Fastboot command. (oem); phone connected"

Edit2: Got it, just had to delete the line with the oem oO

Edit3: "Failed to flash System: Phone returned False" thats strange oO

Edit4: Maybe it works when i wipe /system oO

Orphee · Aug 26, 2013

Don't know, search for a fastboot for motorola ? seems some guys need this one...

My fastboot comes from android sdk http://dl.google.com/android/android-sdk_r22.0.5-windows.zip

Launch SDK manager and download Android SDK Plateform-tools

esok44 · Aug 26, 2013

Orphee said:
Don't know, search for a fastboot for motorola ? seems some guys need this one...

Didn't work either, tried this one before...

well i guess its time to flash a custom rom then oO

thanks for your try dude, but reflash seems to be the better option for me now

---------- Post added at 04:05 PM ---------- Previous post was at 03:41 PM ----------

Orphee said:
Don't know, search for a fastboot for motorola ? seems some guys need this one...

My fastboot comes from android sdk http://dl.google.com/android/android-sdk_r22.0.5-windows.zip

Launch SDK manager and download Android SDK Plateform-tools

Thats the one i use too...

have heard, that there may be some kind of problem because of bootloader-stuf and so on oO

as i said, i try to just install a custom rom now, thought about it for a long time, so this is a good option...

Edit:

It needed RSD 6.x that worked really really good

chiquito3 · Feb 28, 2014

Is this actually working on xt925 4.1,2, or is there any Xposed Framework apk that works with the motorola xt925?

[XT925] Advanced Reboot Menu for JB 4.1.2 Motorola ROM

Senior Member

Attachments

mentose457

Guest

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Attachments

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Senior Member

Similar threads

Top Liked Posts