Database Info

[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.

Help Error Fastboot

Hello I made many research and I've those errors on my atrix2 fastboot
Invalid CG OTV (cg: system) invalid sp data
Invalid CG HAB (cg: system, status: 0X0056)
Invalid CG OTV (cg: system)
I was trying to flash it with 5.5.1-EDEM-27-MEARET_cfc.xml, and saw many links in here and didn't work can anyone help.
and my phone from at&t.
Thanks

I'm in the same boat as you.
http://forum.xda-developers.com/showthread.php?t=1615662

iFalcon said:
I'm in the same boat as you.
http://forum.xda-developers.com/showthread.php?t=1615662
Click to expand...
Click to collapse
I've the original files but didn't work too.

Uploading the InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285 as we speak
It has always worked for me and has gotten me out of so many softbricks in both version 2.3.5 and 2.3.6
Links should be up within the next 2 hours. Hopefully that will help your problems

eL_MeXiCaNo said:
Uploading the InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285 as we speak
It has always worked for me and has gotten me out of so many softbricks in both version 2.3.5 and 2.3.6
Links should be up within the next 2 hours. Hopefully that will help your problems
Click to expand...
Click to collapse
Thank you!!!! Will you post the link to find them?

eL_MeXiCaNo said:
Uploading the InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285 as we speak
It has always worked for me and has gotten me out of so many softbricks in both version 2.3.5 and 2.3.6
Links should be up within the next 2 hours. Hopefully that will help your problems
Click to expand...
Click to collapse
I've the InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID28 5 but didn't flash

Hmmmm....this isn't good news Bryan - .

Bryan. said:
I've the InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID28 5 but didn't flash
Click to expand...
Click to collapse
Were you coming from 2.3.5 or 2.3.6?
If coming from 2.3.6 did you have the modified XML and other files that allowed you to flash the 2.3.5 FXZ? Without that modified XMl ppl would get errors while flashing
Yes, I will post the links here that way you won't look far for them. Like I said, this has worked flawlessly for me, should work for you too.

yes I've the modified XML and was working for me, but after I tried to flash it to 5.5.1-EDEM-27-MEARET_cfc.xml the at&t didn't flash with me at all tried too many times and I don't wanna lose the battery to get low

eL_MeXiCaNo said:
Were you coming from 2.3.5 or 2.3.6?
If coming from 2.3.6 did you have the modified XML and other files that allowed you to flash the 2.3.5 FXZ? Without that modified XMl ppl would get errors while flashing
Yes, I will post the links here that way you won't look far for them. Like I said, this has worked flawlessly for me, should work for you too.
Click to expand...
Click to collapse
I'm on 2.3.5 and attempted to update to 2.3.6, but received the update failed. From what I understand, that can be related to deleting of bloatware. I can only assume at this point since I purchased it from Craigslist.
I attempted to use the .bat flash, but now get a out of system memory error when trying to download the update. A factory reset throws me right back into a fastboot....odd. http://forum.xda-developers.com/showthread.php?t=1539167&page=2
Thanks.

Here you are. Just EXTRACT and point RSD LITE to the XML file inside the extracted folder. Happy flashing
This will restore your atrix 2 back to 2.3.5 even if you are on 2.3.6 it has worked flawlessly for me
MD5 = 2c25abaee9342f37e91d3318d64e2557
http://jumbofiles.com/az0dpni27pfi
http://netload.in/datei9n4tMznje4/InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.xml.zip.htm
http://depositfiles.com/files/gu6lqptbd

Thanks for the information. I was able to flash without issue, but still the same result.
I then attempted to perform the 2.3.6 update and he says not enough system memory and then says to perform a factory reset. I do that and it immediately go into fastboot with an error.
I am just stumped on this one. I especially do not understand the 'not enough system memory'. I've tried everything, but a no go. The phone functions fine after booting up. Just no 2.3.6 update....grrrr.
Any ideas?

eL_MeXiCaNo said:
Here you are. Just EXTRACT and point RSD LITE to the XML file inside the extracted folder. Happy flashing
This will restore your atrix 2 back to 2.3.5 even if you are on 2.3.6 it has worked flawlessly for me
MD5 = 2c25abaee9342f37e91d3318d64e2557
http://jumbofiles.com/az0dpni27pfi
http://netload.in/datei9n4tMznje4/InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.xml.zip.htm
http://depositfiles.com/files/gu6lqptbd
Click to expand...
Click to collapse
{
"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"
}

After flashing the AT&T fxz (that has to be modified as you are downgrading from 2.3.6) try using this fix: http://forum.xda-developers.com/showthread.php?t=1493386

cogeary said:
After flashing the AT&T fxz (that has to be modified as you are downgrading from 2.3.6) try using this fix: http://forum.xda-developers.com/showthread.php?t=1493386
Click to expand...
Click to collapse
I did that I tried everything on the forum didn't work. plus can you help to install 5.5.1-EDEM-27-MEARET_cfc.xml.zip on at and t
and when I flash it with 5.5.1-EDEM-27-MEARET_cfc.xml.zip
someone help me :|

Coming guys someone help me:|

cogeary said:
After flashing the AT&T fxz (that has to be modified as you are downgrading from 2.3.6) try using this fix: http://forum.xda-developers.com/showthread.php?t=1493386
Click to expand...
Click to collapse
Sorry this week has been really busy. Try this:
Unzip the .zip file that you are trying to flash (not the Indian one, the one the eL_MeXiCaNo linked you to). Now use a text editor like Notepad to edit the file "InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.xml" that is inside of the folder you just unzipped. Delete the next four lines after you see "<steps interface="AP">". They should look like this:
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" />
Now save the file and close Notepad. Next, open up RSD. Tell it to flash the .xml file that you just edited and see what happens. It might still error out but just post the screenshot. Good luck!

cogeary said:
Sorry this week has been really busy. Try this:
Unzip the .zip file that you are trying to flash (not the Indian one, the one the eL_MeXiCaNo linked you to). Now use a text editor like Notepad to edit the file "InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.xml" that is inside of the folder you just unzipped. Delete the next four lines after you see "<steps interface="AP">". They should look like this:
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" />
Now save the file and close Notepad. Next, open up RSD. Tell it to flash the .xml file that you just edited and see what happens. It might still error out but just post the screenshot. Good luck!
Click to expand...
Click to collapse
Alright it's work again but can't you help me out to install the 5.5.1-EDEM-27-MEARET_cfc.xml.zip, I do really need this one to be on my phone forever and I'll never change it.

cogeary said:
Sorry this week has been really busy. Try this:
Unzip the .zip file that you are trying to flash (not the Indian one, the one the eL_MeXiCaNo linked you to). Now use a text editor like Notepad to edit the file "InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.xml" that is inside of the folder you just unzipped. Delete the next four lines after you see "<steps interface="AP">". They should look like this:
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" />
Now save the file and close Notepad. Next, open up RSD. Tell it to flash the .xml file that you just edited and see what happens. It might still error out but just post the screenshot. Good luck!
Click to expand...
Click to collapse
haveing the same problem error at step three but the code dint help m i just supposed to delete or is there something else i missed?

Mendy S. said:
haveing the same problem error at step three but the code dint help m i just supposed to delete or is there something else i missed?
Click to expand...
Click to collapse
What system version were you on, and what fxz did you flash on your phone? The more info the better..

[CWM] Updated 9/21/13 All variants CWM recovery

This recovery is CWM for the One SV. It is fully working and has no problems. All variants are supported below
K2_CL (Boost Mobile) -> Boost Download
K2_PLC_CL (Cricket) -> Cricket Download
K2_UL (EU LTE) -> EU LTE Download
K2_U (EU NON-LTE) -> EU Non-LTE Download
Sources:
Boost Mobile Source
Cricket Source
EU LTE Source
EU Non-LTE Source
To build these recoveries on your own, simply follow the directions below:
Clone the CyanogenMod repo. See their wiki at http://wiki.cyanogenmod.org
create a local_manifests file by issuing the command `mkdir -p .repo/local_manifests/` then `gedit .repo/local_manifests/k2.xml`
inside this new document place the following lines
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project path="device/htc/msm8960-common" name="CyanogenMod/android_device_htc_msm8960-common" />
<project path="device/htc/s4-common" name="CyanogenMod/android_device_htc_s4-common" />
<project path="device/htc/k2_cl" name="SimonSickle/android_device_htc_k2_cl" revision="cwm" />
<project path="vendor/htc/k2_cl" name="SimonSickle/android_vendor_htc_k2_cl" revision="jellybean" />
<project path="device/htc/k2_plc_cl" name="SimonSickle/android_device_htc_k2_plc_cl" revision="cwm" />
<project path="vendor/htc/k2_plc_cl" name="SimonSickle/android_vendor_htc_k2_plc_cl" revision="jellybean" />
<project path="device/htc/k2_ul" name="SimonSickle/android_device_htc_k2_ul" revision="cwm" />
<project path="vendor/htc/k2_ul" name="SimonSickle/android_vendor_htc_k2_ul" revision="jellybean" />
<project path="device/htc/k2_u" name="SimonSickle/android_device_htc_k2_u" revision="cwm" />
<project path="vendor/htc/k2_u" name="SimonSickle/android_vendor_htc_k2_u" revision="jellybean" />
<project path="kernel/htc/k2" name="SickleKernels/android_kernel_htc_k2" revision="htc_3.4" />
</manifest>
now run `repo sync` and wait for this to finish. It will take a long time
With any luck, you now have the source. Your computer should already be set up to build so just do the following commands
. build/envsetup.sh
now you will want to lunch the right device (see the download section as a guide)
lunch cm_k2_cl-userdebug
and finally the make command is as follows
make -j5 recoveryimage
at the end you will see a welcoming path to your new recovery. Flash it in fastboot or with dd and enjoy!

simonsimons34 said:
This recovery is CWM for the One SV. It is fully working and has no weird glitchy screen like it had before.
Download for BOOST MOBILE here -> http://downloads.codefi.re/simon/k2cl/CWMrecovery.img
Source at http://github.com/SimonSickle/android_device_htc_k2_cl/tree/cwm
I have applied for official status with Koush. Until he accepts it, enjoy this perfect build
Click to expand...
Click to collapse
Works great Simon! Thanks.

simonsimons34 said:
This recovery is CWM for the One SV. It is fully working and has no weird glitchy screen like it had before.
Download for BOOST MOBILE here -> http://downloads.codefi.re/simon/k2cl/CWMrecovery.img
Source at http://github.com/SimonSickle/android_device_htc_k2_cl/tree/cwm
I have applied for official status with Koush. Until he accepts it, enjoy this perfect build
Click to expand...
Click to collapse
Hi;
The recovery file is not there. Can you reload it?

Sorry Simon, recovery doesn't boot.
Neither the k2u nor the k2ul.
k2u -> boots constantly into android, not recovery.
k2ul -> hangs on splash screen.
bkcokota's cwm works totally fine, but it has the framework bug.
This bug fixed and we have a stable CWM. But i know, devs do not work on others build.

I am going to do twrp then. Once those are confirmed booting ill use the TWRP folder and remove anything non twrp from them
PS- The issue with his build is a lack of source (problem one), the partitions are different (two), the devices have different code names which messes with the flashing of source built roms (problem three) and its not ready for 4.3 (4)

Updated 9/21/13
Sent from my C525c using Tapatalk 4

All of the links are dead. Where else can I get info for the Boost c525c?

[GUIDE] Enabling Apps for Pen Window without ROOT

Hello Friends,
Just want to share another GUIDE/MOD this time for NON-ROOT users - ENABLING Apps for PEN Window without Root.
Without root, the only way to add more apps for Pen Window is modifying the app yourself or getting developers to add pen window support to their apps. But it involves a bit of knowledge in decompiling, editing, recompiling and resigning apps with apktool, jarsigner or some similar tool like Apk Manager, Apk Multitool and a lot others. I won't go into a tutorial about decompilation. I was a noob once and I did my best to search and learn about this stuff so if you are interested then a few google or xda search would give you tons of links on how to decompile/recompile apk files.
TOOLS:
1. Knowledge of modding apk files
2. ApkManager or other similar tools
3. Notepad++ or something similar
GUIDE:
1. Decompile apk file using ApkManager or your tool of choice.
2. Open the AndroidManifest.xml file of the decompiled apk file using Notepad++ or your editor of choice. Below is a sample AndroidManifest.xml file.
Code:
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="mobi.xperiacle.PenWindowTest"
android:versionCode="1"
android:versionName="1.0" >
<uses-sdk
android:minSdkVersion="16"
android:targetSdkVersion="17" />
<application
android:allowBackup="true"
android:icon="@drawable/ic_launcher"
android:label="@string/app_name"
android:theme="@style/AppTheme" >
<activity
android:name="mobi.xperiacle.PenWindowTest.MainActivity"
android:label="@string/app_name" >
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>
</application>
</manifest>
3. Look for the acivity which has "<category android:name="android.intent.category.LAUNCHER" />"
and add "<category android:name="com.samsung.android.intent.category.PENWINDOW_LAUNCHER" />" below it.
Below is the same AndroidManifest.xml above with the change highlighted in RED.
Code:
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="mobi.xperiacle.PenWindowTest"
android:versionCode="1"
android:versionName="1.0" >
<uses-sdk
android:minSdkVersion="16"
android:targetSdkVersion="17" />
<application
android:allowBackup="true"
android:icon="@drawable/ic_launcher"
android:label="@string/app_name"
android:theme="@style/AppTheme" >
<activity
android:name="mobi.xperiacle.PenWindowTest.MainActivity"
android:label="@string/app_name" >
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
[COLOR="Red"]<category android:name="com.samsung.android.intent.category.PENWINDOW_LAUNCHER" />[/COLOR]
</intent-filter>
</activity>
</application>
</manifest>
4. Look for "</application>" which is the closing tag of the <application...> node. Then add
"<meta-data android:name="com.samsung.android.sdk.multiwindow.penwindow.enable" android:value="true" />" above it. Below is the same AndroidManifest.xml file above with the all changes in RED.
Code:
<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
package="mobi.xperiacle.PenWindowTest"
android:versionCode="1"
android:versionName="1.0" >
<uses-sdk
android:minSdkVersion="16"
android:targetSdkVersion="17" />
<application
android:allowBackup="true"
android:icon="@drawable/ic_launcher"
android:label="@string/app_name"
android:theme="@style/AppTheme" >
<activity
android:name="mobi.xperiacle.PenWindowTest.MainActivity"
android:label="@string/app_name" >
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
[COLOR="Red"]<category android:name="com.samsung.android.intent.category.PENWINDOW_LAUNCHER" />[/COLOR]
</intent-filter>
</activity>
[COLOR="Red"]<meta-data android:name="com.samsung.android.sdk.multiwindow.penwindow.enable" android:value="true" />[/COLOR]
</application>
</manifest>
5. Recompile and Resign apk file and push to your phone. If you are using ApkManager that is all done in one go with option 14 while phone is connected.
6. Have FUN! A COFFEE would be Nice. he he
THANKS to @soloilmeglio for testing and making sure it works before I write and share this guide.

Great news for all non-rooted gn3 eh eh.... great work as always
Inviato dal mio SM-N9005 utilizzando Tapatalk

So is it possible for you to do an app that automaticly does the magic?
Like some drag and drop .apk to make it work on penwindow (and why not in multiwindow too?)

Thanks, it works

I got it work only in one app (tried for ~5 apps)
Dunno if the problem is using APK Multi-Tool instead of ApkManager? And I believe problem is in .apk or tool.. Not in your guide
And why I can't find those lines already in app that has multiwindow, pen window or both already? How those are made then?
But thanks anyway very useful guide
ps. Didn't try to only add pen window, but multiwindow too at same time
Sent from my SM-N9005 using XDA Premium HD app

Oh man this is such great news..... if I knew how to decompile and recompile apks.
I've downloaded the tool but it's way above my knowledge.
Will wait to see if some-one can design an app to do it automatically as I'm NOT rooting my N3....

Amdathlonuk said:
Oh man this is such great news..... if I knew how to decompile and recompile apks.
I've downloaded the tool but it's way above my knowledge.
Will wait to see if some-one can design an app to do it automatically as I'm NOT rooting my N3....
Click to expand...
Click to collapse
It's not that hard really, it took a while for me but even I managed to make it work
If you got Java JDK and ADB installed (Google how to install if not)
Google APK Multi-Tool, you'll find a link to some topic on XDA where is download link (and instructions how to use it)
When you got all ready and multi tool running, type 24 and enter, choose your apk file (if you have that apk on computer and moved to Multi-Tool apk edit folder) and enter again. Then type 9 and enter to decompile, go to projects folder and edit AndroidManifest.xml. Then delete that app from your phone if already installed, connect your phone to pc using USB cable and then type 15 in Multi-Tool and hit enter. Now it should compile, sign and install that app to your phone, if everything went right.
Sorry for messy message but I'm at work. Ask if somethings not clear to you
Sent from my SM-N9005 using XDA Premium HD app

Add the red string under penwindow tweak and you unlock Multiwindows too
<category android:name="com.samsung.android.intent.category.PENWINDOW_LAUNCHER" />
<category android:name="android.intent.category.MULTIWINDOW_LAUNCHER" />
Click to expand...
Click to collapse
<meta-data android:name="com.samsung.android.sdk.multiwindow.penwindow.enable" android:value="true" />
<uses-library required="false" name="com.sec.android.app.multiwindow" />
<meta-data android:name="com.sec.android.support.multiwindow" android:value="true" />
<meta-data android:name="com.sec.android.multiwindow.DEFAULT_SIZE_W" android:value="632.0dip" />
<meta-data android:name="com.sec.android.multiwindow.DEFAULT_SIZE_H" android:value="598.0dip" />
<meta-data android:name="com.sec.android.multiwindow.MINIMUM_SIZE_W" android:value="632.0dip" />
<meta-data android:name="com.sec.android.multiwindow.MINIMUM_SIZE_H" android:value="598.0dip" />
Click to expand...
Click to collapse
---------- Post added at 01:43 AM ---------- Previous post was at 01:42 AM ----------
Add the red string under penwindow tweak and you unlock Multiwindows too
<category android:name="com.samsung.android.intent.category.PENWINDOW_LAUNCHER" />
<category android:name="android.intent.category.MULTIWINDOW_LAUNCHER" />
Click to expand...
Click to collapse
<meta-data android:name="com.samsung.android.sdk.multiwindow.penwindow.enable" android:value="true" />
<uses-library required="false" name="com.sec.android.app.multiwindow" />
<meta-data android:name="com.sec.android.support.multiwindow" android:value="true" />
<meta-data android:name="com.sec.android.multiwindow.DEFAULT_SIZE_W" android:value="632.0dip" />
<meta-data android:name="com.sec.android.multiwindow.DEFAULT_SIZE_H" android:value="598.0dip" />
<meta-data android:name="com.sec.android.multiwindow.MINIMUM_SIZE_W" android:value="632.0dip" />
<meta-data android:name="com.sec.android.multiwindow.MINIMUM_SIZE_H" android:value="598.0dip" />
Click to expand...
Click to collapse

erlos said:
Add the red string under penwindow tweak and you unlock Multiwindows too
---------- Post added at 01:43 AM ---------- Previous post was at 01:42 AM ----------
Add the red string under penwindow tweak and you unlock Multiwindows too
Click to expand...
Click to collapse
would anything of this work with Waze?

valtersboze said:
would anything of this work with Waze?
Click to expand...
Click to collapse
?????
I did Not understand...
This is OLD tips on note 1
Inviato dal mio SM-N9005 utilizzando Tapatalk

erlos said:
?????
I did Not understand...
This is OLD tips on note 1
Click to expand...
Click to collapse
before i spend hours trying to figure out the apk tool - i wanted to ask if anyone has applied the penwindow/multiwindow tags to Waze apk and if it works. In city driving waze is critical to be open but it is waste of screen real estate to see just waze. i would like whatsapp or music apps open and visible too.

I Will be try later!
Inviato dal mio SM-N9005 utilizzando Tapatalk

nice work...

itworks thanks

What apps have you all tested this on? I'd like to try it on a confirmed app. I did this with one app already and the app runs normally but it is not showing up in my pen window list when I bring it up. I also tried setting it up for multiwindows but I don't know how to test that feature. Is there a way to bring up multiwindows without having to do it automatically? For example if I'm browsing on chrome and I want to pull up a dictionary app in the second window, is that possible and if so how?

Dewdropkorn said:
What apps have you all tested this on? I'd like to try it on a confirmed app. I did this with one app already and the app runs normally but it is not showing up in my pen window list when I bring it up. I also tried setting it up for multiwindows but I don't know how to test that feature. Is there a way to bring up multiwindows without having to do it automatically? For example if I'm browsing on chrome and I want to pull up a dictionary app in the second window, is that possible and if so how?
Click to expand...
Click to collapse
Allright..
If you made it right, app should show in penwindow menu and for multiwindow in the list when you open "multiwindow bar"
What program you used for editing .apk?
I did it this way (some apps still didn't work, but not sure why is that)
I downloaded APK Multi-Tool from bottom of first post http://forum.xda-developers.com/showthread.php?t=695701
Then: Enter 24 (Set current project) --> 9 (Decompile apk) --> Then I deleted the app from my phone --> Edited the AndroidManifest.xml --> 15 (compile apk / sign apk / install apk)
Now it install the app to phone
Okay then, there is typos in all post in this topic that should enable penwindow (at least didn't work for me before I corrected them)
If you watch close to (example those at first post) they got SPACE between "." and "P" --> "...category.(SPACE HERE)PENWINDOW..."
Same for another line "...multiwindow.(SPACE HERE)penwindow.enable"
APK Multi-Tool gave error to log and app didn't work before those SPACEs were removed.
Hmm.. When I was writing this post, I noticed that SPACE came there in post preview even it really wasn't in post?
It did same when I tried to put those lines in quote tags, so why is that?
Only way to get that one "automatic space" away from line was to put it in code tags
So try copying these to AndroidManifest.xml to enable both Penwindow and Multiwindow
Code:
<category android:name="com.samsung.android.intent.category.PENWINDOW_LAUNCHER" />
<category android:name="android.intent.category.MULTIWINDOW_LAUNCHER" />
Code:
<meta-data android:name="com.samsung.android.sdk.multiwindow.penwindow.enable" android:value="true" />
<uses-library required="false" name="com.sec.android.app.multiwindow" />
<meta-data android:name="com.sec.android.support.multiwindow" android:value="true" />
<meta-data android:name="com.sec.android.multiwindow.DEFAULT_ SIZE_W" android:value="632.0dip" />
<meta-data android:name="com.sec.android.multiwindow.DEFAULT_ SIZE_H" android:value="598.0dip" />
<meta-data android:name="com.sec.android.multiwindow.MINIMUM_ SIZE_W" android:value="632.0dip" />
<meta-data android:name="com.sec.android.multiwindow.MINIMUM_ SIZE_H" android:value="598.0dip" />

Spere said:
Allright..
If you made it right, app should show in penwindow menu and for multiwindow in the list when you open "multiwindow bar"
What program you used for editing .apk?
I did it this way (some apps still didn't work, but not sure why is that)
I downloaded APK Multi-Tool from bottom of first post http://forum.xda-developers.com/showthread.php?t=695701
Then: Enter 24 (Set current project) --> 9 (Decompile apk) --> Then I deleted the app from my phone --> Edited the AndroidManifest.xml --> 15 (compile apk / sign apk / install apk)
Now it install the app to phone
Okay then, there is typos in all post in this topic that should enable penwindow (at least didn't work for me before I corrected them)
If you watch close to (example those at first post) they got SPACE between "." and "P" --> "...category.(SPACE HERE)PENWINDOW..."
Same for another line "...multiwindow.(SPACE HERE)penwindow.enable"
APK Multi-Tool gave error to log and app didn't work before those SPACEs were removed.
Hmm.. When I was writing this post, I noticed that SPACE came there in post preview even it really wasn't in post?
It did same when I tried to put those lines in quote tags, so why is that?
Only way to get that one "automatic space" away from line was to put it in code tags
So try copying these to AndroidManifest.xml to enable both Penwindow and Multiwindow
Code:
<category android:name="com.samsung.android.intent.category.PENWINDOW_LAUNCHER" />
<category android:name="android.intent.category.MULTIWINDOW_LAUNCHER" />
Code:
<meta-data android:name="com.samsung.android.sdk.multiwindow.penwindow.enable" android:value="true" />
<uses-library required="false" name="com.sec.android.app.multiwindow" />
<meta-data android:name="com.sec.android.support.multiwindow" android:value="true" />
<meta-data android:name="com.sec.android.multiwindow.DEFAULT_ SIZE_W" android:value="632.0dip" />
<meta-data android:name="com.sec.android.multiwindow.DEFAULT_ SIZE_H" android:value="598.0dip" />
<meta-data android:name="com.sec.android.multiwindow.MINIMUM_ SIZE_W" android:value="632.0dip" />
<meta-data android:name="com.sec.android.multiwindow.MINIMUM_ SIZE_H" android:value="598.0dip" />
Click to expand...
Click to collapse
That's exactly what my problem was. Fixing the spaces caused the app to show up for both my Penwindow and my multiwindow. Thank you so much. I don't have the luxury of rooting and this was exactly what I needed for doing what I need for this phone for.:good:

Thanks
Sent from my SM-N900 using XDA Premium 4 mobile app

Dewdropkorn said:
That's exactly what my problem was. Fixing the spaces caused the app to show up for both my Penwindow and my multiwindow. Thank you so much. I don't have the luxury of rooting and this was exactly what I needed for doing what I need for this phone for.:good:
Click to expand...
Click to collapse
Nice to hear it works
Sent from my SM-N9005 using XDA Premium HD app

Has anyone done this with Spotify? I've successfully modded about 6 apps now but the .apk I recompiled and signed for Spotify has "parsing" errors when I try to installing it. Anyone else with better luck?

Whatsapp Enable Dark Mode

Whatsapp Enable Dark Mode for rooted device only.
This is for information only. Do it on your own risk.
Make sure you have a file explorer that supports root. If you don’t have much idea about this, suggest you download the*Solid Explorer File Manager*from Play Store. Now when you open the app, grant it root access by tapping Allow in the Magisk pop-up that appears.*
Open File Manager and head over to the root partition.*
Then go to*Data*>*Data*and navigate to the*com.whatsapp*folder.
Go to the*shared_prefs*folder and search for the*com.whatsapp_preferences.xml*file.
Now add the below lines to that xml file, anywhere inside the*<map>*and*</map>*tags. This one line of code is, in fact, responsible for enabling Dark Mode on WhatsApp on rooted Android devices.
<boolean name="dark_mode" value="true" />
Next, tap on the floppy icon to save the file. Now just force close WhatsApp and re-open it.
Finally, head over to*Settings. You could now see the*Theme*option, just beneath Account. Tap on it and select*Dark.
That’s it.
Tested in android 9 and 10.
Example how i added that line
<boolean name="move_media_folder_from_sister_app" value="true" />
<int name="web_service_delay" value="120" />
<boolean name="search_in_storage_usage" value="true" />
<boolean name="third_party_sticker_caching" value="true" />
<boolean name="auth_fingerprint_enabled" value="true" />
<boolean name="dark_mode" value="true" />
</map>
I hv added in last line...
For example

There's already a thread for this here:
https://forum.xda-developers.com/general/general/enable-dark-mode-whatsapp-root-twrp-t4017667
Please search before posting to avoid creating duplicate topics.
Thread closed.